eclipse-vertx/vert.x · error

406 Not Acceptable

Error message

406 Not Acceptable

What it means

Constant defining the 406 Not Acceptable response expectation: applying expecting(SC_NOT_ACCEPTABLE) turns a 406 response into a failed request future. The server cannot produce a representation matching the request's Accept headers; the 'message' is the reason on the failure.

Source

Thrown at vertx-core/src/main/java/io/vertx/core/http/HttpResponseExpectation.java:180

  /**
   * 403 Forbidden
   */
  HttpResponseExpectation SC_FORBIDDEN = status(403);

  /**
   * 404 Not Found
   */
  HttpResponseExpectation SC_NOT_FOUND = status(404);

  /**
   * 405 Method Not Allowed
   */
  HttpResponseExpectation SC_METHOD_NOT_ALLOWED = status(405);

  /**
   * 406 Not Acceptable
   */
  HttpResponseExpectation SC_NOT_ACCEPTABLE = status(406);

  /**
   * 407 Proxy Authentication Required
   */
  HttpResponseExpectation SC_PROXY_AUTHENTICATION_REQUIRED = status(407);

  /**
   * 408 Request Timeout
   */
  HttpResponseExpectation SC_REQUEST_TIMEOUT = status(408);

  /**
   * 409 Conflict
   */
  HttpResponseExpectation SC_CONFLICT = status(409);

  /**
   * 410 Gone

View on GitHub (pinned to fb308bd8c3)

Solutions

1. Adjust Accept headers to content types the server supports
2. Handle the failed future in content-negotiation logic

When it happens

Trigger: Thrown at vertx-core/src/main/java/io/vertx/core/http/HttpResponseExpectation.java:180 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of eclipse-vertx/vert.x@fb308bd8c3 (2026-09-06). Data as JSON: /api/errors/9074d3c5bd8e0c80. Report an issue: GitHub.