fixes #1434

Open ehsan2003 opened this issue 4 years ago • 2 comments

Jan 10 '22 12:01 ehsan2003

cc @pfernie

Jan 10 '22 17:01 seanmonstar

Thanks for the issue & PR! I am not sure the proposed behavior is consistent with the spec. It states:

   Servers SHOULD NOT include more than one Set-Cookie header field in
   the same response with the same cookie-name.  (See Section 5.2 for
   how user agents handle this case.)

Following the steps referenced Section 5.2, though, the current behavior of taking the last seen value for a given cookie-name seems to be consistent with the steps outlined.

So I do not think the default behavior should change here. Some simple tests in Firefox seem to also be consistent with the existing behavior of taking the last seen value.

Jan 12 '22 02:01 pfernie