Problems with HTTP/2

[Aapo Talvensaari]

On 29 September 2015 at 12:25, Francis Daly <francis at daoine.org> wrote:
> On Tue, Sep 29, 2015 at 01:06:50AM +0300, Aapo Talvensaari wrote:
> > It just sets the status code. It is normal PHP 5.3 code [1]. I might
need
> > to compile nginx by hand to get more debug info.
>
> For what it's worth:
>
> when I test with a php 5.1.6 and a php 5.3.3,
>
>   header(':', true, 403);
>
> Using
>
>   header("HTTP/1.1 403 Whatever");
>
> sets the status code and does not add the dubious header.


Thanks. I know this is not probably a best way to set it (and in this case
I can
change it, but it seems like this may cause some problems with user code.
See, the browsers accept it, the Nginx HTTP accepts it, Nginx HTTPS accepts
it, and even Nginx SPDY accepts it. Only Nginx HTTP/2 will not accept it.
And
by accepting I mean, browsers and other Nginx protocols give the correct
status
code as well.

Thanks for debugging this furher. I think everyone now has the knowledge of
what is going on.

Is this a bug or a feature? Because it might break user code running on
Nginx,
I might call it a bug. Because it breaks only when these weird headers are
in
place I might call it a feature.


Regards
Aapo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150929/5a79d2d7/attachment.html>