You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2019. It is now read-only.
I'd like to share a cookie between multiple services, some of which make cross domain requests using JS. Currently, HttpOnly is set to true when the cookie is set and cleared. It'd be great to provide an option to disable this.
Instinctively, I'd set this using a -cookie-httponly flag, but there's already a -cookie-https-only flag. I'd be inclined to rename this to -cookie-secure, which I think would be closer to the expected naming, but it's a breaking change.
I'm happy to submit a PR to do this, but I wanted to check your thoughts on renaming the https flag.
The text was updated successfully, but these errors were encountered:
I'd like to share a cookie between multiple services, some of which make cross domain requests using JS. Currently, HttpOnly is set to true when the cookie is set and cleared. It'd be great to provide an option to disable this.
Instinctively, I'd set this using a
-cookie-httponly
flag, but there's already a-cookie-https-only
flag. I'd be inclined to rename this to-cookie-secure
, which I think would be closer to the expected naming, but it's a breaking change.I'm happy to submit a PR to do this, but I wanted to check your thoughts on renaming the https flag.
The text was updated successfully, but these errors were encountered: