Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Eric Covener
On Mon, Jan 20, 2014 at 8:25 AM, Kalyana sundaram wrote: > 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 > -3 is AP_FILTER_ERROR (in 2.2.x). That makes sense for th

Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Kalyana sundaram
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 wrote: > On Mon, Jan 20, 2014 at 8:13 AM, Kalyana sundaram > wrote: > > If

Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Eric Covener
On Mon, Jan 20, 2014 at 8:13 AM, Kalyana sundaram 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 head

Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Kalyana sundaram
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 On Mon,

Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Eric Covener
On Mon, Jan 20, 2014 at 7:29 AM, Kalyana sundaram wrote: > But if I call ap_finalize_request_protocol(r) instead of using else part, > things are fine > Thats why I wish to understand, when mod_php is called Ignoring all of the cases you aren't testing, what's the behavior in that case (headers

Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Kalyana sundaram
But if I call ap_finalize_request_protocol(r) instead of using else part, things are fine Thats why I wish to understand, when mod_php is called On Mon, Jan 20, 2014 at 5:51 PM, Eric Covener wrote: > On Mon, Jan 20, 2014 at 7:11 AM, Kalyana sundaram > wrote: > > ===>php response > > As I

Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Eric Covener
On Mon, Jan 20, 2014 at 7:11 AM, Kalyana sundaram wrote: > ===>php response As I had described, whatever you're using for PHP (probably mod_php) is ignoring errors while reading the request body and allowing your script to run and append output. I suggest you search for / report a bug to the

Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Kalyana sundaram
On Mon, Jan 20, 2014 at 5:21 PM, Eric Covener wrote: > On Mon, Jan 20, 2014 at 5:31 AM, Kalyana sundaram > wrote: > > > > Hi > > I am using httpd-2.2.26. Whenever I use LimitRequestBody directive Apache > > gives 413 to user if content length is greater than the value specified > in > > directiv

Re: [users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Eric Covener
On Mon, Jan 20, 2014 at 5:31 AM, Kalyana sundaram wrote: > > Hi > I am using httpd-2.2.26. Whenever I use LimitRequestBody directive Apache > gives 413 to user if content length is greater than the value specified in > directive but logs as 200. It even appends the response html along with > error

[users@httpd] Issue with LimitRequestBody

2014-01-20 Thread Kalyana sundaram
Hi I am using httpd-2.2.26. Whenever I use LimitRequestBody directive Apache gives 413 to user if content length is greater than the value specified in directive but logs as 200. It even appends the response html along with error document. This problem happens in httpd-2.4.4 also On further debuggi