Skip to content

Header value validation #100

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

Closed
annevk opened this issue Aug 4, 2015 · 0 comments
Closed

Header value validation #100

annevk opened this issue Aug 4, 2015 · 0 comments

Comments

@annevk
Copy link
Member

annevk commented Aug 4, 2015

Per @youennf in web-platform-tests/wpt#2045 WebKit changed how they validate header values based on a new set of HTTP RFCs that are backwards incompatible. Somewhat unexpected from the IETF, but I guess it's a "bigger than browsers" thing.

So now we need to decide what to do with whitespace in various APIs. It seems the sanest solution is to just strip whitespace, especially for XMLHttpRequest, but also for the Headers object, since there's no semantic difference anyway.

Unless someone proposes a different design I will get this changed for both specifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant