I'm doing this:
RewriteEngine On
RewriteCond %{REMOTE_USER} .
RewriteRule ^.*$ - [S=1]
RewriteRule ^.*$ http://domain/logged_out.html?%{N} [R]
AuthType Digest
AuthName "account"
AuthUserFile /path/.htpasswd
Require valid-user
1) The user is logged in.
2) The user logs out.
3) In ff, the user hits the backpage button.
4) The user gets a dialog box to login rather than being redirected.
Michele
-----Original Message-----
From: Eric Covener [mailto:cove...@gmail.com]
Sent: Thursday, February 12, 2009 3:44 PM
To: modules-dev@httpd.apache.org
Subject: Re: Making mod_auth_digest mysql
On Thu, Feb 12, 2009 at 3:27 PM, Michele Waldman <mmwald...@nyc.rr.com>
wrote:
>>> RewriteCond ${REMOTE_USER} . does not seem to work when the REMOTE_USER
is
>>> not defined. The statement evaluates to true.
>>
>> What happens when you use the proper syntax, %{REMOTE_USER}?
> Lol. I'm using the proper syntax on the server. Just checked.
Works for me: http://apache.pastebin.ca/1335270
.htaccess:
RewriteEngine on
RewriteCond %{REMOTE_USER} .
RewriteRule .* - [G]
127.0.0.1 - - [12/Feb/2009:15:40:42 --0500]
[localhost/sid#954fc98][rid#9578328/initial] (4) RewriteCond: input=''
pattern='.' => not-matched
--
Eric Covener
cove...@gmail.com
