On Tue, Sep 28, 2010 at 10:02 AM, David (Dave) Donnan <david.donnan@xxxxxxxxxxxxxxx> wrote: > RewriteEngine on > > RewriteRule .* - [E=SMUSER:%{$REMOTE_USER}] > RequestHeader set my_new_header %{SMUSER}e > > Result from my browser (setenv.pl): > > SMUSER="" I think the $ is extraneous and causing problems. Another potential problem -- See the "lookahead" feature to figure out REMOTE_USER when your RewriteRules are running in a phase before REMOTE_USER is set! You may be able to wrap your rules in <Directory>, which makes the Rewrite occur a little bit later, and might let some rules like this work better. Finally, why do you want to set the environment variable in a request header? Is this just some debug you added along the way, or your ultimate goal? > > Question 1: The syntax is incredibly cryptic. Where might I look to help me > understand the %, e, {} etc. The variable syntax for RequestHeader is defined in a table at the bottom of the Header directive: http://httpd.apache.org/docs/current/mod/mod_headers.html#header The syntax for mod_rewrite is midway down in the doc for RewriteRule: http://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewriterule > Mind you, it works for simple text: > > RewriteRule .* - [E=SMUSER:test] > > Result: SMUSER="test" > > 2. Technique 2: setenv DAVESETENV "text" > ---------------------------------------------- > > Result: DAVESETENV="text" > > But, I've read that this is only a static string. > > http://www.usenet-forums.com/apache-web-server/10179-setenv-dynamic-variable.html setenvif is a bit more flexible: http://httpd.apache.org/docs/current/mod/mod_setenvif.html#setenvif -- 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