upload filename with double quote failure

Maxim Dounin mdounin at mdounin.ru
Wed Apr 24 17:36:36 UTC 2013


On Wed, Apr 24, 2013 at 11:57:03AM -0400, motto wrote:

> as for nginx backend for debug purpose I use python-tornado script, which
> will just give back params, which nginx pass to it.
> so here it is:
> upload under Chrome:
> {u'upfile.path': ['/usr/local/apps/Opus/temp/upload/6/0009495446'],
> u'upfile.size': ['51'], u'upfile.name': ['test%22try.txt'], u'note': [''],
> u'upfile.md5': ['5a089ad5ea93048b0d492d53626bf76b'], u'upfile.content_type':
> ['text/plain']}
> upload under Firefox:
> {u'note': [''], u'upfile':
> ['erthtyjt\nrthy\ntrh\nrt\nh\nrt\nh\nrt\nh\nrth\nr\nth\nr\nth\n\nt\n\n']}
> Chrome does character encoding, but Firefox - just backspace double quote
> sign.

What Firefox does is actually correct per RFC, as handling of 
multipart/form-data forms should be done per MIME encoding rules.  
See http://tools.ietf.org/html/rfc2388 for more details.

Though anyway it's not related to nginx - it doesn't do anything 
with a request body provided by a browser, it just passes it as is 
to a backend.

Maxim Dounin

More information about the nginx mailing list