News for hackers. Stuff that matters.
Re:CSRF protection bypass due to Google analytics and weird ... by saurik on Monday May 04, 2015 @08:52PM (#9490288)
It might be interesting to some people that the "peculiarity" noted in some web servers is actually requested by the standard. It is noted in both the grammar and in the text (where it is described as for "future compatibility").

> cookie = "Cookie:" cookie-version 1*((";" | ",") cookie-value)

> Note: For backward compatibility, the separator in the Cookie header is semi-colon (;) everywhere. A server should also accept comma (,) as the separator between cookie-values for future compatibility.

https://www.ietf.org/rfc/rfc2109.txt

(I believe part of the issue was that MIME of headers describes how to deal with multiple headers with the same name, which is by concatenating them with commas, and that spec was the basis for the definition of HTTP headers.)

There are no comments on this comment yet.