Skip to content

/ superagent

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

Jump to bottom

Why can't we get set-cookie header? #1091

Closed
ceremcem opened this issue Oct 23, 2016 · 1 comment
Closed

Why can't we get set-cookie header? #1091

ceremcem opened this issue Oct 23, 2016 · 1 comment

Comments

@ceremcem
Copy link

@ceremcem ceremcem commented Oct 23, 2016

I'm using superagent in the browser and I can not get set-cookie header field in the response. It's dropped in somewhere. Is it on purpose, or is it a bug?
@focusaurus
Copy link
Collaborator

@focusaurus focusaurus commented Oct 24, 2016

I believe the Set-Cookie response header is explicitly not exposed to javascript on the page by the browser itself. There's mention of this in the MDN getAllResponseHeaders documentation but I couldn't quickly find any additional detail.
@kornelski kornelski closed this Nov 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@kornelski @focusaurus @ceremcem
You can’t perform that action at this time.