superagent doesn't return set-cookie header

Question

I am using superagent to POST login data to my external endpoint (at a different origin). This external endpoint returns a JWT, as well as a set-header cookie with the JWT inside it as well. I use this cookie to render pages server-side if a user is already logged in.

However, when I check

request.end((err, res) => { console.log(res) }

I do not see any set-header cookie. What am I doing wrong? If it helps, I am using this boilerplate's ApiClient.js.

Knu · Accepted Answer · 2016-11-23 06:38:16Z

0

That's because set-cookie is one of the two forbidden response header names.

answered Nov 23, 2016 at 6:38

Knu

15.2k6 gold badges60 silver badges93 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

j_d Over a year ago

Any idea why? Seems very strange.

Matthew Over a year ago

The link that @Knu posted contains an explanation.

Collectives™ on Stack Overflow

superagent doesn't return set-cookie header

1 Answer 1

2 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Linked

Related