Hello! On Tue, Dec 23, 2014 at 02:17:38PM -0500, Guest13778 wrote:
> Sorry, I forgot to post an example: > > # curl -v -F [email protected] -T http:/mydomain.com > * About to connect() to mydomain.com port 80 (#0) > * Trying 192.168.15.1... connected > * Connected to mydomain.com (192.168.15.1) port 80 (#0) > > POST / HTTP/1.1 > > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 > NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > > Host: mydomain.com > > Accept: */* > > Content-Length: 3337675 > > Expect: 100-continue > > Content-Type: multipart/form-data; > boundary=----------------------------a12017330dd6 > > > < HTTP/1.1 100 Continue > < HTTP/1.1 413 Request Entity Too Large The "100 Continue" response before the "413 Request Entity Too Large" suggests that something non-trivial happens in your setup - normally nginx will just return 413, without useless "100 Continue" before it. This may indicate, for example, that double proxying happens, and the error about too large body is returned by second nginx. Try looking into nginx error log, it should have additional information (in particular, it will indicate server block where the error was generated). Note though, that currently in your config logging level is set to "crit", i.e., logging is effectively switched off. You'll have to set some reasonable logging level to see what nginx has to say - at least "error" in this particular case. If still in doubt, a debugging log can be used to find out low-level details, see http://wiki.nginx.org/Debugging. -- Maxim Dounin http://nginx.org/ _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
