Set-Cookie-trouble

[Maxim Dounin]

Hello!

On Wed, Dec 15, 2010 at 11:34:49AM +0100, "Anton Müller" wrote:

> we are switching from Pound to nginx. Now we have problems with 
> cookies. The backend systems we are using are Apache-Servers.
> 
> It seems that nginx is cutting off the "Set-Cookie:"-Line. Is 
> there a limitation?
> 
> With nginx:

[...]

> Set-Cookie: SESSa7268882c426ab7fd6b8629065f996c3=f31753f1d7deba884d3e9e1f72fd6cd                                                                             b; expires=Fri, 07 Jan 2011 12:53:35 GMT; path=/

[...]

> With Pound:

[...]

> Set-Cookie: SESSa7268882c426ab7fd6b8629065f996c3=c5da927bd7fe6bce8ffdb8aa03f0eee                                                                             5; expires=Fri, 07 Jan 2011 12:54:04 GMT; path=/; domain=.xxx.de

[...]

> Any Solutions?

There are no limits expect total limit on headers from backend 
server (proxy_buffer_size, see [1]).  Header must fit into 
proxy_buffer_size, or nginx won't be able to parse backend 
response (and will return an error).

In your case most likely reason is different behaviour of your 
backend in your nginx setup and your Pound setup.  E.g. nginx by 
default uses backend name as Host header in request to backend, 
see [2].

You may want to use tcpdump to find out what actually happens on 
wire between nginx and your backend, and compare how it's 
different from your Pound setup.

[1] http://wiki.nginx.org/HttpProxyModule#proxy_buffer_size
[2] http://wiki.nginx.org/HttpProxyModule#proxy_set_header

Maxim Dounin