421 Misdirected Request

Bug #1587419 reported by Giovanni on 2016-05-31
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nginx (Ubuntu)
Undecided
Unassigned

Bug Description

In the current stable version, nginx rejects with the 400 error any attempts of requesting different host over the same connection, if the relevant virtual server requires verification of a client certificate.
While requesting hosts other than negotiated isn't something legal in HTTP/1.x, the HTTP/2 specification explicitly permits such requests for connection reuse and has introduced a special response code 421.
According to RFC 7540 Section 9.1.2 this code can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI. And the client may retry the request over a different connection.
Now this code is used for requests that aren't authorized in current connection, but is used only in the current mainline version of nginx.
I ask to amend this bug so HTTP/2 can be used with optional client certificates, otherwise users like me are forced to turn it off.

All relevant changes to files are reported here:
http://hg.nginx.org/nginx/rev/654d2dae97d3

Thanks for your help

Joshua Powers (powersj) wrote :

Greetings,

Apologies for the rather late response. I took a look at the changes you mentioned and can confirm that all those changes exist and are live in Zesty. It seems the latest merge was able to pull these changes in. As a result I am going to mark this as "Fix Released". If you disagree or think some additional work is required please reply with that information and mark this bug as "New" so it can be looked at again.

Thanks!

Changed in nginx (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers