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

rfc6266 should not raise on unsafe lws #5

Open
homm opened this issue Nov 12, 2014 · 0 comments
Open

rfc6266 should not raise on unsafe lws #5

homm opened this issue Nov 12, 2014 · 0 comments

Comments

@homm
Copy link

homm commented Nov 12, 2014

RFC 6266 section 3 "Conformance and Error Handling"

Recipients MAY take steps to recover a usable field value from an
invalid header field, but SHOULD NOT reject the message outright,
unless this is explicitly desirable behavior (e.g., the
implementation is a validator). As such, the default handling of
invalid fields is to ignore them.

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

No branches or pull requests

1 participant