Cookies specification compatibility issues

External Issue #7151935

Details

Created
Apr 8, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

In context of discussion in https://github.com/whatwg/html/issues/804 I've made a research of cookie RFC 6265 compatibility in major browsers: http://inikulin.github.io/cookie-compat.
Tests that fail in all or majority of browsers are considered de facto standard. Related spec change was suggested: https://github.com/httpwg/http-extensions/issues/159.
Here are the test cases that fails only in IE and Edge or test result differs from de facto standard:


DOMAIN0023
Set cookie:
“foo2=bar2; domain=.example.org”
“foo=bar; domain=home.example.org”
Results URL:
http://home.example.org:8888/cookie-parser-result?domain0023
Expected: “foo2=bar2; foo=bar”
Actual: “foo=bar; foo2=bar2”
RFC 6265 S 5.4.2:
The user agent SHOULD sort the cookie-list in the following order:
* Cookies with longer paths are listed before cookies with
shorter paths.
* Among cookies that have equal-length path fields, cookies with
earlier creation-times are listed before cookies with later
creation-times.


PATH0027
Set cookie:
“foo=bar; path="/cookie-parser-result/foo/qux;"”
Results URL:
/cookie-parser-result/foo/qux?path0027
Expected: “foo=bar”
Actual: “”


CHARSET0001 (and other charset tests)
Set cookie:
“foo=春节回家路·春运完全手册”
Expected: “foo=春节回家路·春运完全手册”
Actual: “foo=???�???”


PATH0025
Set cookie:
“foo=bar; path=/cookie-parser-result/foo/qux#”
Results URL:
/cookie-parser-result/foo/qux?path0025
Expected: “”
Actual: “foo=bar”


OPTIONAL_DOMAIN0030 (and other optional domain tests)
Set cookie:
“foo=bar; domain=”
Results URL:
http://home.example.org:8888/cookie-parser-result?optional-domain0030
Expected: “foo=bar”
Actual: “”


MOZILLA0013 (and other zero or negative max-age tests)
Set cookie:
“test=kill; max-age=0”
“five; max-age=0”
Expected: “”
Actual: “test=kill; five”


DOMAIN0029#
Set cookie:
“foo=bar”
Results URL:
http://subdomain.home.example.org:8888/cookie-parser-result?domain0029
Expected: “”
Actual: “foo=bar”


DISABLED_CHROMIUM0023#
Setting long cookie (e.g. ‘a’ x 4097 times) fails (no cookie set).


PATH0024#
Minority - possible bug (2 : 3)
Set cookie:
“foo=bar; path=/cookie-parser-result/foo/qux?”
Results URL:
/cookie-parser-result/foo/qux?path0024
Expected: “”
Actual: “foo=bar”

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Christian F.”

      Changed Assigned To from “Christian F.” to “Ibrahim O.”

      Changed Assigned To to “Christian F.”

      Changed Assigned To to “Sermet I.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Ivan P.”

      Changed Assigned To from “Ivan P.” to “Matthew C.”

      Changed Status to “External”

    • Hello,

      Thank you for providing this information about the issue. We have confirmed the problem, and we are working on a solution for a future build of Edge.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in