mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-11-30 15:21:04 +01:00
Code Issues Projects Releases Wiki Activity

DOC: http: document 413 response code

Browse Source 
Considering that we only use a "413 Payload Too Large" response in a single
situation with a specific config toogle (h1-accept-payload-with-any-method),
add some text to make it easier to find.

Should be backported to 2.6.

Link: https://github.com/cbonte/haproxy-dconv/issues/46
Link: https://discourse.haproxy.org/t/haproxy-error-413-paylod-too-large/9831/3
This commit is contained in:
Lukas Tribus 2025-11-20 16:12:48 +00:00 committed by Willy Tarreau
parent 05c409f1be
commit a50c074b74
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/configuration.txt
View File

@ -550,6 +550,8 @@ HAProxy may emit the following status codes by itself :
408 when the request timeout strikes before the request is complete 408 when the request timeout strikes before the request is complete
410 when the requested resource is no longer available and will not 410 when the requested resource is no longer available and will not
be available again be available again
413 when a HTTP/1.0 GET/HEAD/DELETE requests has a payload, also see
the "h1-accept-payload-with-any-method" option
500 when HAProxy encounters an unrecoverable internal error, such as a 500 when HAProxy encounters an unrecoverable internal error, such as a
memory allocation failure, which should never happen memory allocation failure, which should never happen
501 when HAProxy is unable to satisfy a client request because of an 501 when HAProxy is unable to satisfy a client request because of an
@ -2621,7 +2623,8 @@ group <group name>
See also "gid" and "user". See also "gid" and "user".
h1-accept-payload-with-any-method h1-accept-payload-with-any-method
Does not reject HTTP/1.0 GET/HEAD/DELETE requests with a payload. Does not reject HTTP/1.0 GET/HEAD/DELETE requests with a payload with a
413 Payload Too Large HTTP response.
While It is explicitly allowed in HTTP/1.1, HTTP/1.0 is not clear on this While It is explicitly allowed in HTTP/1.1, HTTP/1.0 is not clear on this
point and some old servers don't expect any payload and never look for body point and some old servers don't expect any payload and never look for body