[users@httpd] RequestHeader question

I am having an issue with the below configuration I can confirm that X-Remote-User get set by watching the rewrite log\\ However the following directive that inserts a request header "Authorization" how can I confirm that that is happening This is the website itself so how would it write to the

[users@httpd] If statement evaluating an http header against a pattern is always true even though it should not

Hi all, I am running an apache 2.4.7 on CentOS 6.7 I am trying to perform request routing within a reverse proxy based on the x-auth header, but for some reasons the if and elseif statements are alwyas evalutaing to true. Here is the part from the config. This is contained in the virtual

AW: [users@httpd] If statement evaluating an http header against a pattern is always true even though it should not

Hi Eric, et all this would explain the issue I am having. I am not that familiar with apache. Do you have any suggestion how I can perform the reverse proxying based on the X-auth header? or any suggestion how to use another kind of variable which will set conditionally? Including the

Re: [users@httpd] If statement evaluating an http header against a pattern is always true even though it should not

I think your problem is that Define is executed immediately when it's read, at startup. It's a rare special case like e.g. Include. It cannot be processeed per-request, which is what is for. I vaguelly recall a later discussion/patch blocking that Context for Define. On Wed, Nov 4, 2015 at 7:41

Re: [users@httpd] If statement evaluating an http header against a pattern is always true even though it should not

On Wed, Nov 4, 2015 at 8:23 AM, Christian Georg wrote: > Hi Eric, et all > > this would explain the issue I am having. I am not that familiar with apache. > Do you have any suggestion how I can perform the reverse proxying based on > the X-auth header? or any suggestion

Re: [users@httpd] prefork vs worker mpm in apache

> On Nov 3, 2015, at 2:53 PM, Rose, John B wrote: > > On 11/3/15 2:21 PM, "Jim Jagielski" wrote: > >> >>> On Nov 3, 2015, at 10:43 AM, Tim Dunphy wrote: >>> >>> >>> Hey guys, >>> >>> We had to recompile apache 2.4.12 because we