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

Whitespace requirement might be too harsh #131

Closed
yoavweiss opened this issue Sep 2, 2015 · 1 comment
Closed

Whitespace requirement might be too harsh #131

yoavweiss opened this issue Sep 2, 2015 · 1 comment
Labels

Comments

@yoavweiss
Copy link

Whitespace is not allowed in the field-value between each field-name and its parameter set.

As a potential implementor it makes the parsing algorithm simpler, but I'm also afraid it'd create a subtle way in which people would fail to deploy this syntax in real life.

Since supporting whitespace won't add significant complexity to the parsing algorithm, can we allow it?

@mnot
Copy link
Owner

mnot commented Oct 19, 2015

Moving to http-extensions repo.

@mnot mnot closed this as completed Oct 19, 2015
Repository owner locked and limited conversation to collaborators Oct 19, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants