-
Notifications
You must be signed in to change notification settings - Fork 362
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
Consider sending unquoted boundary in multipart requests #61
Comments
nex3
added a commit
that referenced
this issue
Mar 6, 2017
This is be more broadly compatible than the quoted version, although the quoted version is what's described by the spec. curl and browsers send unquoted boundaries, so we can safely assume that any server will support them. Closes #61
yjbanov
pushed a commit
to yjbanov/http
that referenced
this issue
Mar 30, 2017
This is be more broadly compatible than the quoted version, although the quoted version is what's described by the spec. curl and browsers send unquoted boundaries, so we can safely assume that any server will support them. Closes dart-lang#61
donny-dont
added a commit
to donny-dont/http
that referenced
this issue
Jun 24, 2017
This is be more broadly compatible than the quoted version, although the quoted version is what's described by the spec. curl and browsers send unquoted boundaries, so we can safely assume that any server will support them. Closes dart-lang#61
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some naive back-ends are unable to handle quoted boundary values, specifically those implemented based on RFC 1867, which, while refers to RFC 1521, does not itself call out the rules for encoding the boundary property.
The text was updated successfully, but these errors were encountered: