Join GitHub today
Cookie gets set on 404 responses #2357
On successful responses (status 200) Symphony does not set cookies if it is not necessary (i.e. if there is no session data).
But when a 404 response is sent by Symphony, there will be a cookie set. The corresponding response header will look like:
You can test this in a terminal window using
I verified this issue with the latest integration code and an older Symphony 2.3.6 install — so obviously this behaviour is not new.
added a commit
Feb 22, 2015
Interesting. This is likely because a 404 is raised as an Exception, and thereby handled by the error handler, not the usual launcher. The usual launcher has some code to cleanup cookies and the like, whereas the exception handler does not. It simply outputs the header and exception content.
All fixed now.