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

Move HTTP::Multipart and HTTP::Formdata to MIME namespace #7078

Closed
straight-shoota opened this issue Nov 13, 2018 · 6 comments
Closed

Move HTTP::Multipart and HTTP::Formdata to MIME namespace #7078

straight-shoota opened this issue Nov 13, 2018 · 6 comments

Comments

@straight-shoota
Copy link
Member

The multipart message format is part of the MIME standard and used by a variaty of applications, not just HTTP. I suggest to rename the HTTP::Multipart type to MIME::Multipart (the MIME namespace has been added in #5765).

Similarly, HTTP::Formdata as an implementation of multipart/formdata should also be renamed to MIME::Formdata.

@RX14
Copy link
Contributor

RX14 commented Nov 21, 2018

formdata is an HTTP spec, multipart is a MIME (originally used in email) spec.

formdata originally started out as https://tools.ietf.org/html/rfc1867, as HTTP specific

multipart started out in https://tools.ietf.org/html/rfc1341#page-29, as a MIME spec (MIME was originally email specific)

@straight-shoota
Copy link
Member Author

More recent RFCs for multipart/formdata are https://tools.ietf.org/html/rfc2388 and https://tools.ietf.org/html/rfc7578 and they specifically state that it "can be used by a wide variety of applications and transported by a wide variety of protocols". It's not specific to HTTP (although it started with HTTP/HTML and that's the most prominent use case).

@RX14
Copy link
Contributor

RX14 commented Nov 23, 2018

It should stay in http.

@straight-shoota
Copy link
Member Author

So MIME::Multipart and HTTP::Formdata?

@RX14
Copy link
Contributor

RX14 commented Dec 7, 2018

Yep.

@Indribell
Copy link

This can be closed. See #7085

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

3 participants