Nginx 0.8.14 - cookie / proxy_pass issue

Payam Chychi pchychi at gmail.com
Tue Sep 22 10:37:11 MSD 2009


Hey Igor,

Yes, here is the last bits:
      proxy_pass              http://LB_HTTP_x.x.x.x;
        proxy_intercept_errors on;
        proxy_cache             one;
        proxy_cache_key         x.x.x.x$request_uri;
        proxy_cache_valid       200  1h;
        proxy_cache_valid       404 5m;
        proxy_cache_use_stale   error timeout invalid_header;

under the new 8.14 and 7.62 version, what would i need to do in order
to accept those cookies and not strip them?

Thanks
Payam T Chychi


2009/9/19 Igor Sysoev <is at rambler-co.ru>:
> On Thu, Sep 17, 2009 at 06:19:14PM -0700, Payam Chychi wrote:
>
>> versions verified the issue with:
>>
>> nginx-0.8.14 - down to 8.05
>> nginx-0.7.62
>> nginx-0.7.61
>> nginx-0.7.60
>>
>> confirmed working versions:
>> nginx-0.7.54 - to up nginx-0.7.59
>> nginx-0.8.0
>
> Have you proxy_cache in this locations ?
>
> Changes with nginx 0.8.1                                         08 Jun 2009
>
> Changes with nginx 0.7.60                                        15 Jun 2009
>
>    *) Bugfix: the "Set-Cookie" and "P3P" response header lines were not
>       hidden while caching if no "proxy_hide_header/fastcgi_hide_header"
>       directives were used with any parameters.
>
>
>> working example:
>> UnclePiemanss-MacBook-2:~ payam$ wget -S -v http://69.172.200.17/
>> --18:16:38--  http://69.172.200.17/
>>            => `index.html.119'
>> Connecting to 69.172.200.17:80... connected.
>> HTTP request sent, awaiting response...
>>   HTTP/1.1 200 OK
>>   Server: nginx/0.7.59
>>   Date: Fri, 18 Sep 2009 01:19:03 GMT
>>   Content-Type: text/html; charset=UTF-8
>>   Connection: close
>>   X-Powered-By: PHP/5.2.0-8+etch15
>>   Set-Cookie: GCD=URTDQW4I; expires=Tue, 17-Nov-2009 01:16:39 GMT; path=/
>>   Set-Cookie: PHPSESSID=45f6fdf9e53cfa9fe415a949501c088a; path=/
>>   Expires: Sat, 26 Jul 1997 05:00:00 GMT
>>   Cache-Control: no-cache, must-revalidate
>>   Pragma: no-cache
>>   Set-Cookie: session2=8c0e63311310a925e3c5cc59349cef25; expires=Wed,
>> 18-Sep-2019 13:16:39 GMT; path=/
>> Length: unspecified [text/html]
>>
>>     [ <=>
>>                                     ] 16,081        --.--K/s
>>
>> 18:16:39 (168.53 KB/s) - `index.html.119' saved [16081]
>>
>>
>> non-working example:
>> UnclePiemanss-MacBook-2:~ payam$ wget -S -v http://69.172.200.17/
>> --18:16:20--  http://69.172.200.17/
>>            => `index.html.118'
>> Connecting to 69.172.200.17:80... connected.
>> HTTP request sent, awaiting response...
>>   HTTP/1.1 200 OK
>>   Server: nginx/0.7.60
>>   Date: Fri, 18 Sep 2009 01:18:45 GMT
>>   Content-Type: text/html; charset=UTF-8
>>   Connection: close
>>   X-Powered-By: PHP/5.2.0-8+etch15
>>   Expires: Sat, 26 Jul 1997 05:00:00 GMT
>>   Cache-Control: no-cache, must-revalidate
>>   Pragma: no-cache
>> Length: unspecified [text/html]
>>
>>     [ <=>
>>                                     ] 16,081        --.--K/s
>>
>> 18:16:21 (136.66 KB/s) - `index.html.118' saved [16081]
>>
>>
>> Perhaps something has changed in the versions that the testing failed
>> in... not too sure
>>
>> Thanks,
>> --
>> Payam Tarverdyan Chychi
>> Network Security Specialist / Network Engineer
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
>
>

Hey Igor,

let me check my configs tomorrow,

-- 
Payam Tarverdyan Chychi
Network Security Specialist / Network Engineer





More information about the nginx mailing list