Content-Type boundary with double quotes failure about nginx-upload-module HOT 7 CLOSED

no fix for this? RFC2616 clearly allows for the boundary parameter to be quoted here.

from nginx-upload-module.

Can you give an example with a concrete application when it fails?

from nginx-upload-module.

RFC2616 clearly states the quotes are valid. here are the relevant lines:

Content-Type = "Content-Type" ":" media-type
media-type = type "/" subtype *( ";" parameter )
parameter = attribute "=" value
value = token | quoted-string <-- the value can be quoted
quoted-string = ( <"> *(qdtext | quoted-pair ) <"> )
qdtext = <any TEXT except <">>

similarly for the quotes in FILENAME_STRING and FIELDNAME_STRING, except the quotes around those are optional.

any standards-compliant client code (concrete or otherwise) will break it.

i can give you concrete code if you really want, but it will be a bash script piping a POST through netcat. i can't give you my actual code (because lawyers).

from nginx-upload-module.

Well, I think you are the best person to fix this. Standard compliance is good, but usually it comes at a cost. May be I'll have time for that, but since you are one of the few who want it, you are the best person to help yourself so far.

from nginx-upload-module.

probably not. i'm familiar with the standards, but not with this codebase.

from nginx-upload-module.

Windows Phone HttpClient use a quoted boundary, so the windows phone could not be a client of the module. Fix it please.

from nginx-upload-module.

.NET HttpClient (not just Windows Phone) uses quoted boundary.

from nginx-upload-module.