You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HAProxy may emit the following status codes by itself :
....
410 when the requested resource is no longer available and will not
be available again
500 when HAProxy encounters an unrecoverable internal error, such as a
memory allocation failure, which should never happen
....
And information when 413 is generated is not provided. However haproxy can and will return 413 in some cases:
The only way to find more about 413 code is to look at source code of haproxy where more information is provided with configuration option for potential fix:
/* Reject HTTP/1.0 GET/HEAD/DELETE requests with a payload except if
* accept_payload_with_any_method global option is set.
*There is a payload if the c-l is not null or the the payload is
* chunk-encoded. A parsing error is reported but a A
* 413-Payload-Too-Large is returned instead of a 400-Bad-Request.
*/
if (!accept_payload_with_any_method &&
!(h1m->flags & (H1_MF_RESP|H1_MF_VER_11)) &&
(((h1m->flags & H1_MF_CLEN) && h1m->body_len) || (h1m->flags & H1_MF_CHNK)) &&
(h1sl.rq.meth == HTTP_METH_GET || h1sl.rq.meth == HTTP_METH_HEAD || h1sl.rq.meth == HTTP_METH_DELETE)) {
h1s->flags |= H1S_F_PARSING_ERROR;
htx->flags |= HTX_FL_PARSING_ERROR;
h1s->h1c->errcode = 413;
Can you add information about 413 code into documentation?
The text was updated successfully, but these errors were encountered:
In haproxy documentation it is specified that:
But further down in https://www.haproxy.com/documentation/haproxy-configuration-manual/latest/#1.4.1 it is specified only:
And information when 413 is generated is not provided. However haproxy can and will return 413 in some cases:
2024 IP https~ https/<NOSRV> -1/-1/-1/-1/0 413 0 - - PR-- 10/10/0/0/0 0/0 "<BADREQ>"
The only way to find more about 413 code is to look at source code of haproxy where more information is provided with configuration option for potential fix:
Can you add information about 413 code into documentation?
The text was updated successfully, but these errors were encountered: