Skip to content
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

fix(proxy): split cookie headers properly with native node fetch #408

Merged
merged 2 commits into from
Jun 20, 2023

Conversation

pi0
Copy link
Member

@pi0 pi0 commented Jun 20, 2023

Proxy on Node.js >= 18, uses native fetch (which already splits set-cookie headers). Because of this, we need to merge/split all cookie headers and set it once otherwise (currently) only first cookie(s) will be added.

@codecov
Copy link

codecov bot commented Jun 20, 2023

Codecov Report

Merging #408 (bd152f0) into main (bb59c69) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #408      +/-   ##
==========================================
+ Coverage   76.08%   76.15%   +0.06%     
==========================================
  Files          26       26              
  Lines        2438     2445       +7     
  Branches      338      339       +1     
==========================================
+ Hits         1855     1862       +7     
  Misses        583      583              
Impacted Files Coverage Δ
src/utils/proxy.ts 83.50% <100.00%> (+0.61%) ⬆️

@pi0 pi0 marked this pull request as ready for review June 20, 2023 20:41
@pi0 pi0 changed the title fix(proxy): split cookie headers properly with native fetch (node 18+) fix(proxy): split cookie headers properly with native node fetch Jun 20, 2023
@pi0 pi0 merged commit eeaf03b into main Jun 20, 2023
5 checks passed
@pi0 pi0 deleted the fix/proxy-cookie branch June 20, 2023 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant