Re: mod_rewrite/1687: %{REMOTE_USER} returns empty string during RewriteCond/RewriteRules evaluation
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
Synopsis: %{REMOTE_USER} returns empty string during RewriteCond/RewriteRules
evaluation
State-Changed-From-To: analyzed-closed
State-Changed-By: rse
State-Changed-When: Wed Feb 25 07:47:01 PST 1998
State-Changed-Why:
There _IS_ a clean and elegant workaround for this:
Just use %{LA-U:REMOTE_USER} instead of %{REMOTE_USER}
to look-ahead the variable via sub-request.
No one has noticed this in the past (including myself)
because this %{LA-X:yyy} syntax was totally mis-documented.
The documentation now was corrected.
Re: mod_rewrite/1687: %{REMOTE_USER} returns empty string during RewriteCond/RewriteRules evaluation
[In order for any reply to be added to the PR database, ]
[you need to include [EMAIL PROTECTED] in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
Synopsis: %{REMOTE_USER} returns empty string during RewriteCond/RewriteRules
evaluation
State-Changed-From-To: open-analyzed
State-Changed-By: dgaudet
State-Changed-When: Sat Feb 21 04:11:13 PST 1998
State-Changed-Why:
r-connection-user isn't set until a much later phase in processing.
mod_rewrite runs during the name translation phase and the user
isn't set until the auth phases.
I don't think there's a clean workaround to this one. Maybe we
should just update the docs to remove REMOTE_USER as a value which
can be conditionalized.
Incidentally, apache 1.3 supports proxy authentication.
Dean
