Can you grab the http conversation from the browser or run tcpdump to show the
difference between curl and the browser? The client sends the different thing
to the server which is confirmed.
-B
> Date: Tue, 14 Oct 2014 12:37:33 +0700
> From: dewangg...@xtremenitro.org
> To: nginx@nginx.org
> Su
mex wrote:
> it is more a performance- than a security-issue (diskspace, i/o, buffering)
> etc
ok
assume no webmail activity in this moment
does this setting affect & impact a static site serving mainly images in
this scenario ?
___
nginx mailing li
The http headers returned to the client are incorrect. It should be
"Connection 'keep-alive'" instead of "Conncetion "close"". Somehow all the
nginx settings for response headers seem to be ignored. The fact that the
application server's name is returned in the response http header instead of
"Serv
it is more a performance- than a security-issue (diskspace, i/o, buffering)
etc
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253959,253960#msg-253960
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
are there any inherent security risks associated with increasing to a
value of, say, 10M to accommodate attachment upload for web mail client
usage ?
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
