I am using Silverstripe 18.104.22.168 and I found a strange behavior with bypassStaticCache cookie.
I don't know the meaning of this cookie but from my analysis, I realized that the SS is deleting the cookie, even when the browser does not send it. On other hand, the Set-Cookie operation is done twice in the same response.
GET http://localhost/mySite/ HTTP/1.1 Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Encoding: gzip,deflate,sdch ... Cookie: PHPSESSID=lt1hsucqgrribkl2kabak09243
HTTP/1.1 200 OK Date: Mon, 05 Dec 2011 13:28:07 GMT Server: Apache/2.2.17 (Win32) mod_ssl/2.2.17 OpenSSL/0.9.8o PHP/5.3.4 mod_perl/2.0.4 Perl/v5.10.1 X-Powered-By: PHP/5.3.5 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Set-Cookie: bypassStaticCache=deleted; expires=Sun, 05-Dec-2010 13:28:07 GMT; path=/; httponly Set-Cookie: bypassStaticCache=deleted; expires=Sun, 05-Dec-2010 13:28:07 GMT; path=/; httponly Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html; charset=utf-8 Content-Length: 41160
As you can see in response headers, there are 2 Set-Cookie instructions with the same value and current date. The referenced cookie was not send previously by the browser.
Is this a known issue? Anyone know a work around?