[PATCH] HTTP/2: reject HTTP/2 requests without ":scheme" pseudo-header

Valentin V. Bartenev vbart at nginx.com
Thu Mar 30 13:57:22 UTC 2017

On Wednesday 29 March 2017 20:01:55 Piotr Sikora via nginx-devel wrote:
> Hey Valentin,
> > IMHO it's not a good idea to combine style fixes with behavior changes.
> > Behavior changing commits are occasionally reverted.
> Fair enough, I'll update both patches shortly.
> > That's why it's still TODO (in other words intentionally skipped).
> > We discussed it with QA and decided to be more tolerant here.
> I disagree. Forgiving implementations that allow broken clients to
> seemingly "work", even when said clients are not obeying the
> specification, are the reason why we have broken clients in the first
> place.

One of the broken clients (not in this place particularly, but in a few
others) is Google Chrome.

Sometimes it takes year to convince devs to do something about that, even
if the issue is obvious.  Here is an example:

And if something isn't working in browser-webserver combination then this
is usually us who will be blamed for.  Because people need their services
working in the first place.  As a result, you can see such commits:

I agree with your arguments about the positive side in enforcing strict
validation.  On the other hand, the main goal is to keep our users setups
working with any clients.  The world isn't perfect and neither us, nor our
users can fix it.

As the 1.11 branch is going to be stable soon, it's a good idea to postpone
any changes that explicitly affect interoperability (at least till 1.13).

  wbr, Valentin V. Bartenev

More information about the nginx-devel mailing list