Re: Include additional files

2013-04-25 Thread motto
upstream name should be unique per entire config, you could name it in nginx.conf and than reference to its name from different your includes. like: upstream loadbalancer { server 192.168.0.1:8080; server 192.168.0.2:8080; server 192.168.0

Re: upload filename with double quote failure

2013-04-25 Thread motto
Sorry to be annoying, here is part of nginx config: # Upload form should be submitted to this location location /upload_test { upload_pass @test; upload_store /usr/local/apps/Opus/temp/upload 1; upload_store_access user:r; upload_set_form_field $upload_f

Re: upload filename with double quote failure

2013-04-24 Thread motto
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':

upload filename with double quote failure

2013-04-24 Thread motto
Problem uploading file name - test"try.txt (with double quotes inside file name) under firefox browser. It pass to backend file content as a file name. {"note": [""], "upfile": ["erthtyjt\nrthy\ntrh\nrt\nh\nrt\nh\nrt\nh\nrth\nr\nth\nr\nth\n\nt\n\n"]} here is debug from nginx. http://pastebin.com