We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
workers-rs
0.0.18
wrangler
When calling a cloudflare worker in workers-rs, the set-cookie header "folds" and creates a single set-cookie = cookie1=value1, cookie2=value2.
set-cookie
set-cookie = cookie1=value1, cookie2=value2
According to cloudflare docs and the IETF RFC, the set-cookie header should not fold.
We do not have the same behaviour in our javascript workers.
It's a tricky case when looking at the headers interface, but maybe a similar getAll interface is needed here?
getAll
This makes it slightly more tricky to act as a reverse-proxy and forward requests from our worker.
curl -H "Set-Cookie: cookie1=value1" -H "Set-Cookie: cookie2=value2" http://0.0.0.0:8787
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing issue for this?
What version of
workers-rs
are you using?0.0.18
What version of
wrangler
are you using?0.0.18
Describe the bug
When calling a cloudflare worker in
workers-rs
, theset-cookie
header "folds" and creates a singleset-cookie = cookie1=value1, cookie2=value2
.According to cloudflare docs and the IETF RFC, the set-cookie header should not fold.
We do not have the same behaviour in our javascript workers.
It's a tricky case when looking at the headers interface, but maybe a similar
getAll
interface is needed here?This makes it slightly more tricky to act as a reverse-proxy and forward requests from our worker.
Steps To Reproduce
curl -H "Set-Cookie: cookie1=value1" -H "Set-Cookie: cookie2=value2" http://0.0.0.0:8787
set-cookie = cookie1=value1, cookie2=value2
The text was updated successfully, but these errors were encountered: