Eee Jay

Eee Jay

The server will return a 500 error if the Content-Disposition header values are not quoted. So:
Content-Disposition: form-data; name="file_data"; filename="test.m4v"
is accepted, and:
Content-Disposition: form-data; name=file_data; filename=test.m4v
raises an "internal" 500 error.

RFC2231 says that quotes or no quotes are allowed:
"Note that quotes around parameter values are part of the value
syntax; they are NOT part of the value itself. Furthermore, it is
explicitly permitted to have a mixture of quoted and unquoted
continuation fields."

Brad Dougherty

Brad Dougherty Staff

Hi Guys, we actually are sticking to the spec:

Note the examples in section 6:

Content-type: multipart/form-data, boundary=AaB03x

--AaB03x content-disposition: form-data; name="field1"

Joe Blow --AaB03x content-disposition: form-data; name="pics"; filename="file1.txt" Content-Type: text/plain

... contents of file1.txt ... --AaB03x--

This conversation is missing your voice. Please join Vimeo or log in.