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

Reference RFC 7578 instead of RFC 2388 #710

Merged
merged 1 commit into from Feb 19, 2016
Merged

Conversation

cvrebert
Copy link
Member

Fixes #398.
Submitted per #398 (comment)

RFC 2388 has been obsoleted by RFC 7578.
Fixes whatwg#398

* Remove note about non-usage of multipart/mixed, since the new RFC no longer recommends it either:
  > § 4.3. Multiple Files for One Form Field
  > [...] [RFC2388] suggested that multiple files for a single form field be
  > transmitted using a nested "multipart/mixed" part.  This usage is
  > deprecated.
* Remove remark about field names not using RFC 2047's 7-bit-safe "encoded-word" encoding method,
  since the new RFC no longer recommends it:
  > § 5.1. Non-ASCII Field Names and Values
  > [...] While [RFC2388] suggested that non-ASCII field names be encoded according
  > to the method in [RFC2047], this practice doesn't seem to have been
  > followed widely.
* Remove requirement about not using RFC 2231 encoding for filenames, since the new RFC
  no longer recommends that encoding.
@domenic
Copy link
Member

domenic commented Feb 19, 2016

This LGTM. @annevk, do you want to give it a quick look, since I believe you were looking at nearby stuff in your encoding changes?

@domenic domenic added the clarification Standard could be clearer label Feb 19, 2016
@domenic domenic self-assigned this Feb 19, 2016
@annevk
Copy link
Member

annevk commented Feb 19, 2016

I think this is probably a net improvement, though this new RFC still doesn't give us everything we need. We might have to just write our own algorithms at some point to cater for Fetch and encoding handling in the fringes.

@domenic domenic merged commit dc34d9f into whatwg:master Feb 19, 2016
@domenic
Copy link
Member

domenic commented Feb 19, 2016

Thanks very much @cvrebert! We really appreciate this kind of cleanup <3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer
Development

Successfully merging this pull request may close these issues.

None yet

3 participants