-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.7.0 no longer supports .localhost
domain value
#173
Comments
I'm running into this same issue, reverting back to |
We're running into a similar issue where our leading |
@EvHaus Is that the language you are reading that the leading dot should be allowed, since I don't see your specific phrasing? And then 5.2.3:
So it looks like the dot isn't required and isn't permitted in the spec for |
Correct.
That's surprising to me. How would a cookie target all subdomains with it? |
If you specify the domain, they automatically target all subdomains. It surprised me too. It's part of the |
Domain match: 5.1.3. Building the cookie header is specified here: 5.4. TL;DR: no domain = host-only, domain = send for this domain and any subdomain. The leading dot behavior is from the earlier spec: https://datatracker.ietf.org/doc/html/rfc2109. |
Released a fix in https://github.com/jshttp/cookie/releases/tag/v0.7.1. |
After upgrading from
0.6.0
to0.7.0
this code no longer works:This now throws
option domain is invalid
.According RFC6265 Section 4.1.2.3 a leading
.
(dot) should be allowed for targeting subdomains. Am I doing something wrong, or is this a possible 0.7.0 bug?The text was updated successfully, but these errors were encountered: