Re: [users@httpd] Patch for CVE-2016-1546 on httpd 2.4.18

2016-07-19 Thread Mike Rumph
Hello Srini, Try the following link: - http://svn.apache.org/viewvc?view=revision&revision=1733727 Thanks, Mike On 7/17/2016 10:26 AM, srinivasan sarangarajan wrote: Hi, Can anyone please point me to the link for the patch on 2.4.18 for CVE-2016-1546. Thanks Srini ---

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Amlaan Kar
What the example5-handler does is that it parses the url entered and if the url does not satisfy the given conditions, displays a message. However, if the conditions are satisfied by the url entered the example5-handler returns DECLINED. This is where the example1-handler is called and executed.

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Yann Ylavic
On Tue, Jul 19, 2016 at 4:21 PM, Yann Ylavic wrote: > > There are other ways to do this (by setting an environment variable > with for example SetEnvIf, and checking it in your handler), in any > case a DECLINing handler should not have to deal with r->handler > unless it knows which handler to fo

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Yann Ylavic
On Tue, Jul 19, 2016 at 2:42 PM, Amlaan Kar wrote: > example1_handler is as given below: > module AP_MODULE_DECLARE_DATA example1_module; > > static int example1_handler(request_rec *r) > { > if (!r->handler || strcmp(r->handler, "example1-handler")) return > (DECLINED); So it does nothing un

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Amlaan Kar
example1_handler is as given below: module AP_MODULE_DECLARE_DATA example1_module; static int example1_handler(request_rec *r) { if (!r->handler || strcmp(r->handler, "example1-handler")) return (DECLINED); ap_set_content_type(r, "text/html"); ap_rprintf(r, "Hello, world!"); return

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Yann Ylavic
On Tue, Jul 19, 2016 at 2:15 PM, Amlaan Kar wrote: > static void register_hooks(apr_pool_t *pool) > { > static const char *const succs[] = {"mod_example1.c", NULL }; > ap_hook_handler(example5_handler, NULL, succs, APR_HOOK_FIRST); > } > AP_DECLARE_MODULE(example5) = > { > STANDARD20_M

Re: [users@httpd] mod_proxy: When does a backend be considered as failed?

2016-07-19 Thread Yann Ylavic
Hello, On Sun, Jul 17, 2016 at 9:41 AM, dE wrote: > It appears that mod_proxy considers a backend as failed only when the > transport layer connection to that backend fails. Is this expected? Unless failonstatus/failontimeout is used, usually. Which httpd version are you using? Could you pl

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Amlaan Kar
static void register_hooks(apr_pool_t *pool) { static const char *const succs[] = {"mod_example1.c", NULL }; ap_hook_handler(example5_handler, NULL, succs, APR_HOOK_FIRST); } AP_DECLARE_MODULE(example5) = { STANDARD20_MODULE_STUFF, NULL, NULL, NULL, NULL, NULL, r

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Amlaan Kar
The first handler runs properly. However, the successor does not run. The module I am using has been written by me and is not a built-in one. Is there any separate method for httpd built-in handlers? On Tue, Jul 19, 2016 at 5:37 PM, Yann Ylavic wrote: > On Tue, Jul 19, 2016 at 1:58 PM, Amlaan

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Yann Ylavic
On Tue, Jul 19, 2016 at 1:58 PM, Amlaan Kar wrote: > Thank You for answering. The method described above is not working. Please describe not working.. Your handler does not run before the one you specified as successor ? > Do I > have to make any changes before using the above given code? > PS:

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Amlaan Kar
Thank You for answering. The method described above is not working. Do I have to make any changes before using the above given code? PS: Both the handlers work properly individually On Tue, Jul 19, 2016 at 4:44 PM, Yann Ylavic wrote: > On Tue, Jul 19, 2016 at 12:29 PM, Amlaan Kar wrote: > > I h

Re: [users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Yann Ylavic
On Tue, Jul 19, 2016 at 12:29 PM, Amlaan Kar wrote: > I have two handlers to be accessed. My motive is to use the second handler > if the first handler returns DECLINED. > > I have tried various combinations of SetHandler, AddHandler and AddType but > none has worked as overriding takes place in a

[users@httpd] Use an Apache handler after declining another

2016-07-19 Thread Amlaan Kar
I have two handlers to be accessed. My motive is to use the second handler if the first handler returns DECLINED. I have tried various combinations of SetHandler, AddHandler and AddType but none has worked as overriding takes place in all of these combinations. Is there any method in Apache to us

Re: [users@httpd] Run PHP Handler after running my handler Apache

2016-07-19 Thread Amlaan Kar
, and mod_rewrite do not work here as I am reading the query string parameter from a xml file and thus cannot declare it in the configuration file. However, it would be really helpful if you would help me understand how a module's processing can be hooked up earlier in the cycle as this seems to

Re: [users@httpd] Run PHP Handler after running my handler Apache

2016-07-19 Thread Amlaan Kar
Sir, it would be great if you could elaborate on how to hook up the module's processing earlier in the cycle. I am parsing the query string and checking if the parameter's value is alphanumeric or not. So what do I use as condition in the clause? Besides, does not work. On Tue, Jul 19, 2016 at 1

[users@httpd] Re: mod_proxy: When does a backend be considered as failed?

2016-07-19 Thread dE
Looks like this module is deprecated. On 07/17/16 13:11, dE wrote: Hi, It appears that mod_proxy considers a backend as failed only when the transport layer connection to that backend fails. Is this expected? The backends are VMs and only when I SIGSTOP the VMs, the backend is considere