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

Make combine work for XMLHttpRequest and WebSocket #501

Closed
wants to merge 1 commit into from

Conversation

annevk
Copy link
Member

@annevk annevk commented Mar 7, 2017

Unfortunately as established in whatwg/xhr#108 setRequestHeader() uses , whereas fetch() uses , as value separator. This introduces a legacySpaceFlag for combine that XMLHttpRequest and WebSocket can use. New code and CORS (in Access-Control-Request-Headers) can continue not passing this flag.

Tests were fixed in web-platform-tests/wpt#5008.


Preview | Diff

Unfortunately as established in whatwg/xhr#108 setRequestHeader() uses `, ` whereas fetch() uses `,` as value separator. This introduces a legacySpaceFlag for combine that XMLHttpRequest and WebSocket can use. New code and CORS (in Access-Control-Request-Headers) can continue not passing this flag.

Tests were fixed in web-platform-tests/wpt#5008.
annevk added a commit to whatwg/xhr that referenced this pull request Mar 7, 2017
Depends on whatwg/fetch#501. Tests have been
updated already.

Fixes #108.
@annevk
Copy link
Member Author

annevk commented Mar 10, 2017

Closing this in favor of #504. We're going to try to get unified behavior between Fetch and XMLHttpRequest, even if that's currently not the case, favoring XMLHttpRequest over Fetch due to its long legacy.

@annevk annevk closed this Mar 10, 2017
@annevk annevk deleted the annevk/legacy-space branch March 10, 2017 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant