Skip to content

Consider updating HTTP references to RFC 7230. #99

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.

Sign up for GitHub

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

Jump to bottom
Closed
Ms2ger opened this issue Jul 31, 2015 · 3 comments
Closed

Consider updating HTTP references to RFC 7230. #99

Ms2ger opened this issue Jul 31, 2015 · 3 comments

Comments

@Ms2ger
Copy link
Member

Ms2ger commented Jul 31, 2015

I was looking at field-value in particular, but note https://www.rfc-editor.org/errata_search.php?rfc=7230&eid=4189.
@annevk
Copy link
Member

annevk commented Jul 31, 2015

See https://www.w3.org/Bugs/Public/show_bug.cgi?id=27797 for a problem.

@annevk
Copy link
Member

annevk commented Aug 6, 2015

And #100.

@annevk
Copy link
Member

annevk commented Aug 10, 2015

  • Method -> method (otherwise same)
  • field-name (same)
  • field-value (same, though we should strip HTTP whitespace (not ASCII whitespace) on both sides)
  • delta-seconds (same, but defined in https://tools.ietf.org/html/rfc7234)
  • Reason-Phrase -> reason-phrase (otherwise same)

A bunch of bytes are called "obsolete" but will nevertheless be supported.

@annevk annevk closed this as completed in 6c00fe2 Aug 10, 2015
@hiroshige-g hiroshige-g mentioned this issue Sep 1, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ms2ger @annevk