access lists and auth basic
Kingsley Foreman
kingsley at internode.com.au
Sun Jul 8 03:58:13 MSD 2007
----- Original Message -----
From: "Igor Sysoev" <is at rambler-co.ru>
To: <nginx at sysoev.ru>
Sent: Sunday, July 08, 2007 4:05 AM
Subject: Re: access lists and auth basic
> On Sat, Jul 07, 2007 at 08:18:29PM +0930, Kingsley Foreman wrote:
>
>> proxy_buffer_size 32768k;
>> proxy_buffers 4 32768k;
>>
>> 2007/07/07 20:17:08 [info] 32272#0: the configuration file
>> /etc/nginx/nginx.conf syntax is ok
>> 2007/07/07 20:17:08 [info] 32272#0: the configuration file
>> /etc/nginx/nginx.conf was tested successfully
>>
>>
>> the error log printed
>> 2007/07/07 11:21:04 [error] 2197#0: *59969 upstream sent too big header
>> while reading response header from upstream, client: 121.45.170.6,
>> server:
>> games.internode.on.net, URL: "/forums/viewtopic.php?p=1483389", upstream:
>> "fastcgi://127.0.0.1:10005", host: "games.internode.on.net"
>
> It seems it's bug in nginx.
> Try attached patch. The error message then should be:
>
> [alert] ... upstream split a header line in FastCGI records while
> reading response header from upstream, ...
>
> If so, then I on the right way - currently nginx does not support
> HTTP headers split between FastCGI records. The PHP stdout FastCGI records
> are big enough - 8K, so the split is seldom case (large cookies).
>
> This bug/feature could be fixed.
>
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>
The new error message is
2007/07/08 09:27:08 [alert] 19587#0: *83 upstream split a header line in
FastCGI records while reading response header from upstream, client:
150.101.30.226, server: games.internode.on.net, URL:
"/forums/viewtopic.php?t=107964", upstream: "fastcgi://127.0.0.1:10005",
host: "games.internode.on.net", referrer:
"http://games.internode.on.net/forums/viewforum.php?f=2&topicdays=0&start=250"
so it appears you are on the right track.
Kingsley
More information about the nginx
mailing list