Re: Conditionally Setting HTTP Response Header

[Anurag Kapur <anuragkapur@xxxxxxxxx>]

I saw it used here http://mail-archives.apache.org/mod_mbox/httpd-dev/200609.mbox/%3C450543D6.80505@xxxxxxxxxxxxxx%3E

I thought it is needed to differentiate a field set in the response header from that in the request header. But after reading the documentation again, I see it says:

An HTTP request header field (see RFC2616 for more information about these); for example: Host, User-Agent, Referer, and Accept-Language. A regular _expression_ may be used to specify a set of request headers.

http://httpd.apache.org/docs/2.0/mod/mod_setenvif.html#setenvif

Which means I can use only request header fields (Am I right?). However, what I am looking to do is conditionally set an environment variable based on the "response" header (not request header), so that I know if I have to append or unset a certain field in the response header.

Unless I am getting this wrong, is there any other way of doing this?

Thanks

Anurag

On Mon, Mar 15, 2010 at 3:02 PM, Eric Covener <covener@xxxxxxxxx> wrote:

On Mon, Mar 15, 2010 at 10:59 AM, Anurag Kapur <anuragkapur@xxxxxxxxx> wrote:
> Below is exactly what I tried:
>    SetEnvIfNoCase response Cache-Control .+ cc_set=123
>    Header append X-ws "test" env=cc_set
> Expected output: If response does not have Cache-Control set, the X-ws field
> should display the text "test".
> Actual output: X-ws field did not display the text "test"
> Note: I realized the problem with the syntax I was using after you pointed
> it out and tried the above after fixing it (I think).
> -Anurag

What is "response" doing there?

SetEnvIfNoCase attribute regex [!]env-variable[=value]
[[!]env-variable[=value]] ...


--

Eric Covener
covener@xxxxxxxxx

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx