-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Delete client cookie with a domain scope #951
Comments
I'm not sure. Then you also kinda need to add |
@erikdubbelboer I've tested path which isn't counted as a scope(I don't know why). |
Hmm I didn't know that. In that case a pull request to add |
I will test all cookie fields, and if only domain affects deletion, I will make a pull request. |
@erikdubbelboer Bad luck, both |
Thanks for the research. Yes let's document it. Can you make a pull? |
Sure. |
See: #956 |
* Improve documentation about DelClientCookie which related with #951. * Fix ms cleaner in Client
* Improve documentation about DelClientCookie which related with #951. * Add DisableHeaderNamesNormalizing to PipelineClient
* Improve documentation about DelClientCookie which related with #951. * use proxy.FromURL to support auth
* Improve documentation about DelClientCookie which related with #951. * Add pipeline name
Related with gofiber/fiber#1127
Once a cookie is set with a domain scope,
c.Response.Header.DelClientCookie
won't work anymore. Browser still keeps the cookie.I made a runnable demo to elaborate this issue(should append
127.0.0.1 a.example.com
to local host):How about adding another function to delete client cookie like
Any ideas?
The text was updated successfully, but these errors were encountered: