> On 30 September 2015 at 02:20, Valentin V. Bartenev
wrote:
> The code was already broken, it was a coincidence that it worked.
I can now confirm that fixing code fixed the issue. Thank you. HTTP/2 works
like a charm!
___
nginx mailing list
nginx@nginx
On 30 September 2015 at 02:20, Valentin V. Bartenev wrote:
> The code was already broken, it was a coincidence that it worked.
Thanks for the patience. Case closed. I just wanted to be sure. It seems
like Chrome is more demanding on HTTP/2 headers than others.
Regards
Aapo
__
On Tuesday 29 September 2015 13:34:46 Aapo Talvensaari wrote:
> On 29 September 2015 at 12:25, Francis Daly 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
On Tuesday 29 September 2015 14:14:44 Aapo Talvensaari wrote:
> On 29 September 2015 at 13:38, Sergey Kandaurov wrote:
> > So, the header field name output as generated with php
> > (and previously guessed by Valentin),
> > is invalid as per 7230, which is in turn referenced in 7540.
> >
> > : f
On 29 September 2015 at 13:38, Sergey Kandaurov wrote:
> So, the header field name output as generated with php
> (and previously guessed by Valentin),
> is invalid as per 7230, which is in turn referenced in 7540.
>
> : field-name = token
> : token = 1*tchar
> : tchar = "!" / "#" / "quot; /
On Sep 29, 2015, at 12:25 PM, Francis Daly wrote:
> On Tue, Sep 29, 2015 at 01:06:50AM +0300, Aapo Talvensaari wrote:
>> On 29 September 2015 at 00:01, Valentin V. Bartenev wrote:
On Monday 28 September 2015 20:59:23 Aapo Talvensaari wrote:
>
> header(':', true, 403);
> die
On 29 September 2015 at 12:25, Francis Daly 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
On Tue, Sep 29, 2015 at 01:06:50AM +0300, Aapo Talvensaari wrote:
> On 29 September 2015 at 00:01, Valentin V. Bartenev wrote:
> > >On Monday 28 September 2015 20:59:23 Aapo Talvensaari wrote:
> > >> On 28 September 2015 at 19:44, Valentin V. Bartenev
> > wrote:
Hi there,
> > >> > >> header(':
On 29 September 2015 at 01:06, Aapo Talvensaari
wrote:
> On 29 September 2015 at 00:01, Valentin V. Bartenev
wrote:
>> What does ":" mean in the header() function?
>> If it returns ":" as a header, then it's the cause of the error.
>>
> It just sets the status code. It is normal PHP 5.3 code.
I
On 29 September 2015 at 00:01, Valentin V. Bartenev wrote:
> >On Monday 28 September 2015 20:59:23 Aapo Talvensaari wrote:
> >> On 28 September 2015 at 19:44, Valentin V. Bartenev
> wrote:
> >> If Ajax request sends a PUT request with XmlHtttpRequest I do get:
> >> net::ERR_SPDY_COMPRESSION_ERRO
On Monday 28 September 2015 20:59:23 Aapo Talvensaari wrote:
> On 28 September 2015 at 19:44, Valentin V. Bartenev wrote:
>
> > On Wednesday 23 September 2015 06:28:37 Aapo Talvensaari wrote:
> > >> I did get errors like:
> > >> net::ERR_SPDY_COMPRESSION_ERROR
> > > Could you provide a debug log
On 28 September 2015 at 19:44, Valentin V. Bartenev wrote:
> On Wednesday 23 September 2015 06:28:37 Aapo Talvensaari wrote:
> >> I did get errors like:
> >> net::ERR_SPDY_COMPRESSION_ERROR
> > Could you provide a debug log with problematic request?
>
I tried to debug this further. And now I'm c
On Wednesday 23 September 2015 06:28:37 Aapo Talvensaari wrote:
> I tried the 1.9.5 release with http2 and it worked fine, but Ajax request
> especially were problematic.
>
> I did get errors like:
> net::ERR_SPDY_COMPRESSION_ERROR
>
> And the status code was 0. With the former spdy support I did
On 23 September 2015 at 11:48, itpp2012 wrote:
> Have you seen this one
> http://forum.nginx.org/read.php?29,261735,261737#msg-261737
> Have you completely removed the spdy module ?
I have seen that, but I'm using the official Ubuntu precise packages from
nginx.org, so I kinda think it should be
Have you seen this one
http://forum.nginx.org/read.php?29,261735,261737#msg-261737
Have you completely removed the spdy module ?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,261745,261750#msg-261750
___
nginx mailing list
nginx@nginx.org
ht
I tried the 1.9.5 release with http2 and it worked fine, but Ajax request
especially were problematic.
I did get errors like:
net::ERR_SPDY_COMPRESSION_ERROR
And the status code was 0. With the former spdy support I didn't have any
problems. I'm also using fastcgi and PHP5 in this server where I
16 matches
Mail list logo