-
Notifications
You must be signed in to change notification settings - Fork 278
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
No match on .google.com
cookie domain against www.google.com
#499
Comments
@rubengmurray I'm going to rephrase your question just to make sure I'm understanding you (please correct me if I've misunderstood):
If so, I think you're correct that this is a regression bug. The comparison against performed here should be against the canonicalized |
That's a clearer way of putting it yes. Thanks for checking this out. |
@rubengmurray this fix should now be available in https://www.npmjs.com/package/tough-cookie/v/5.1.2 |
Perfect. Latest version works in chrome-cookies-secure tests 👍 |
Hi,
Is this behaviour expected?
bertrandom/chrome-cookies-secure#66 (comment)
.google.com
(extracted from cookie)www.google.com
This used to work back in
[email protected]
tough-cookie/lib/cookie.js
Line 301 in e4dfb0a
Quote from issue in
chrome-cookies-secure
The text was updated successfully, but these errors were encountered: