upstream sent too big header.

[Igor Sysoev]

On Wed, Sep 05, 2007 at 01:49:44AM +0800, hshh wrote:

> proxy_buffers 64 8k; is not work for me.
> The error detail is "upstream sent too big header while reading
> response header from upstream". I don't know how to repeat this
> problem, but sometimes. I think it is cause by setcookie, not sure
> very much.
> I made a test, use PHP to setcookie for more than 1k header. After add
> "large_client_header_buffers 4 8k;", it work fine, but not for solve
> "upstream sent too big header while reading response header from
> upstream".

large_client_header_buffers sets buffers to read client request header lines.

proxy_buffer_size and fastgci_buffer_size set buffer to read the whole of
response header from backend or fastcgi server.

> 
> On 9/4/07, Denis F. Latypoff <denis at gostats.ru> wrote:
> > Hello hshh,
> >
> > Tuesday, September 4, 2007, 4:59:20 PM, you wrote:
> >
> > > Hi all,
> > > I am running Nginx with PHP. In some case, there is large header
> > > included big cookie sent from client to server, and I got 502 Gateway
> > > error. After checked nginx-error.log, it said "upstream sent too big
> > > header".
> >
> > > How can I adjust header size for fastcgi?
> >
> > > I tried setting client_header_buffer_size 4k; not work, tried
> > > large_client_header_buffers 4 8k; fastcgi_buffer_size 4k;
> > > proxy_buffer_size 4k; not work either.
> >
> > try proxy_buffers 64 8k;
> >
> > --
> > Best regards,
> >  Denis                            mailto:denis at gostats.ru
> >
> >
> >
> 

-- 
Igor Sysoev
http://sysoev.ru/en/