nginx upload client_max_body_size issue

by

nginx “fails fast” when the client informs it that it’s going to send a body larger than the client_max_body_size by sending a 413 response and closing the connection.

Most clients don’t read responses until the entire request body is sent. Because nginx closes the connection, the client sends data to the closed socket, causing a TCP RST.

If your HTTP client supports it, the best way to handle this is to send an Expect: 100-Continue header. Nginx supports this correctly as of 1.2.7, and will reply with a 413 Request Entity Too Large response rather than 100 Continue if Content-Length exceeds the maximum body size.

More Related Contents:

  1. How does HTTP file upload work?
  2. nginx close upstream connection after request
  3. How do I allow a PUT file request on Nginx server?
  4. Why is an OPTIONS request sent and can I disable it?
  5. Uses of content-disposition in an HTTP response header
  6. How to set HTTP headers (for cache-control)?
  7. What’s the difference between a POST and a PUT HTTP REQUEST?
  8. How to detect server-side whether cookies are disabled
  9. ‘Refresh’ HTTP header
  10. HTTP status code for update and delete?
  11. Why is it common to put CSRF prevention tokens in cookies?
  12. Which status code should I use for failed validations or invalid duplicates?
  13. Easy HTTP requests with gzip/deflate compression
  14. CORS request with Preflight and redirect: disallowed. Workarounds?
  15. PHP_SELF vs PATH_INFO vs SCRIPT_NAME vs REQUEST_URI
  16. How to redirect user’s browser URL to a different page in Nodejs?
  17. Why does my web server software disallow PUT and DELETE requests?
  18. Send request to cURL with post data sourced from a file
  19. What does “pending” mean for request in Chrome Developer Window?
  20. Difference between HTTP redirect codes
  21. Is a slash (“/”) equivalent to an encoded slash (“%2F”) in the path portion of an HTTP URL
  22. Whats Content-Type value within a HTTP-Request when uploading content?
  23. Save cookies between two curl requests
  24. Can I somehow do a synchronous HTTP request via NSURLSession in Swift
  25. Go client program generates a lot a sockets in TIME_WAIT state
  26. CURL Command Line URL Parameters
  27. Is REST DELETE really idempotent?
  28. Is a URL with // in the path-section valid?
  29. What is a connection timeout during a http request
  30. How to set up CORS or OPTIONS for Rocket.rs

Leave a Comment