Credentials support?

[nezed]

On client-side we can deal with cookies specifying credentials option.
https://fetch.spec.whatwg.org/#concept-request-credentials-mode
But, have any idea about cookies on server-side (node-fetch)?

[XeeD]

You should add them manually as headers. You can in fact use the same code for server and for client, because on client the Cookie headers are ignored and credentials: 'include' works instead.

fetch('/', {
  credentials: 'include',
  headers: {'Cookie': 'foo=bar;bar=foo'}
})

[nezed]

@XeeD not great, but works.
Thanks!

[coverslide]

Hi, I'm having an issue where cookies that are set in between redirects are not persisted. With the request module, this is handled much more cleanly, but I would love to use the fetch spec if I can. In the browser it works perfectly fine, but since node-fetch requires cookies to be handled manually it doesn't perform the same way as on the browser, and breaks in my case.

[bitinn]

@coverslide this question finally comes, the short answer is: node-fetch doesn't have a concept of cookies at the moment. If you are facing a POST then redirect then GET request, it breaks.

Any library (request for example) implementing such support use custom cookie store, which is not trivial in server-side context.

[bitinn]

closing this issue as the main problem has a workaround.

(added coverslide's suggestion to #8, it's something we would like to provide a workaround, possibly by implementing redirect header extraction)

[lillem4n]

Why close this when it still is an issue? The "real" solution must be to add the same support server side as client side, no?

[itskibo]

I agree with @lillem4n, this issue is far from being solved.

I cannot set cookies through HTTP, and then later on use them in fetch requests that require these cookies.
This is regardless of whether the credentials header is set or not.

Edit: manually getting and setting the cookies as headers sort of works, as mentioned in #49 (comment), but this works around the purpose of credentials, as you have to manually keep track of these cookies.

This limit is mentioned in LIMITS.md, but there is no mention of solving this in the v3 roadmap, so this does raise some concern for me.

[xxczaki]

@lillem4n @itskibo Reopening this, as it is indeed still an issue.

[AlenToma]

Same problem here, works greet with regular fetch but not with node-fetch and not with axios either sadly