Does each apache2.4 child processes maintain their own opcache or is there
a global opcache shared by all children?
--
Kalyanasundaram
http://blogs.eskratch.com/
https://github.com/kalyanceg/
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
, Jan 20, 2014 at 6:36 PM, Eric Covener wrote:
> 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
&g
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
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
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
