-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Comments
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) |
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). |
It should stay in http. |
So |
Yep. |
This can be closed. See #7085 |
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 toMIME::Multipart
(theMIME
namespace has been added in #5765).Similarly,
HTTP::Formdata
as an implementation ofmultipart/formdata
should also be renamed toMIME::Formdata
.The text was updated successfully, but these errors were encountered: