On 10-04-2012 17:49, Daniel Gruno wrote:
> On 10-04-2012 17:36, Pierre-Rudolf Gerlach wrote:
>> My bad for the missing quote, I changed the values in the exemple
>> without re-testing it, sorry.
>>
>> You example works for a deny. However, if I slightly modify it,
>> replacing "Require all denied" by a variable setting, like this
>>
>> SetEnvIf dummy .* myvar=value
>> <If "env('myvar') == 'value'">
>> SetEnvIf dummy .* myothervar=othervalue
>> </If>
>> Header set myvar %{myvar}e
>> Header set myothervar %{myothervar}e
>>
>> I get the problem : "myothervar" is not set. (null in the response
>> headers). I don't really get what difference it would make ?
>>
>> Thanks, regards
>>
I obviously needed to think outside the box for a bit before it hit me:
This is 2.4, we can use SetEnv!
SetEnvIf dummy .* myvar=value
<If "env('myvar') == 'value'">
SetEnv myothervar othervalue
</If>
Header set myvar %{myvar}e
Header set myothervar %{myothervar}e
This should work very well within a .htaccess context.
What's probably best, for future reference, is if you try to solve
things using <If> to match a criteria,
followed by SetEnv to set the variables, so you don't have to rely on
SetEnvIf.
With regards,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|