>>>
>>> errorfile 413 /usr/local/etc/haproxy/errors/413.http
>>> http-request deny deny_status 413 if { req.body_size gt 10485760 }
>>>
>>> ... HAProxy complains with:
>>>
>>> [WARNING] 135/001448 (27) : parsing [/etc/haproxy/haproxy.cfg:15] : status
>>> code 413 not handled by 'errorfile', error customization will be ignored.
>>> [WARNING] 135/001448 (27) : parsing [/etc/haproxy/haproxy.cfg:89] : status
>>> code 413 not handled, using default code 403.
>>>
>>> How should I configure HAProxy in order to deny with 413?
>>
>
> In my understanding I should only use a 400badreq.http like message on an
> errorfile 400 config line, otherwise if HAProxy need to issue a 400 status
> code, my 413 status code would be issued instead.
>
> Is this a valid feature request or there are technical reasons why this has
> been done that way?
>
> Hints are welcome.
I think the way to do it is to create a backend to handle deny with the special
message and then use the backend to reject the request. You can have different
backends to handle any special case and not pollute the normal error responses.
frontend http
… normal stuff here
use_backend req_too_big if { req.body_size gt 10485760 }
backend req_too_big
errorfile 400 /path/to/my/error400_req_too_big.http
http-request deny 400
-Bryan
