Re: Issue with LimitRequestBody

[Kalyana sundaram <kalyanceg@xxxxxxxxx>]

access_status is -3 and r->status is 413. But I am not getting why in ap_process_request r->status is set to HTTP_OK before calling ap_die. This seems like causing the issue

On Mon, Jan 20, 2014 at 6:49 PM, Eric Covener <covener@xxxxxxxxx> wrote:

On Mon, Jan 20, 2014 at 8:13 AM, Kalyana sundaram <kalyanceg@xxxxxxxxx> wrote:
> If ap_die is called
> 413 is the response code on header sent to client
> 200 is the response code on logs
> body has the error document and the response appended
>
> If ap_finalize_request_protocol is called
> 413 is response code on header
> 413 is logged
> response is not appended to error document

I don't think Apache can just chuck the response when the handler did
not return an error (the "access_status" return value) vs. succesfully
generating a non-200 response (returning OK with r->status set to 413
during the course of execution).  I think the error document has been
queued up under the assumption that whoever sees that request-reading
error will surely return an error.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx

--
Kalyanasundaram
http://blogs.eskratch.com/

https://github.com/kalyanceg/