Hi,
Not sure if this could be considered a bug but here goes.
OS: Oracle Linux 6.4
Apache: 2.2.15
Apache being used as a reverse-proxy sitting in front of multiple web
servers.
We are currently using the Allow From directive to restrict access by IP
Address to virtual hosts. Each virtual host
On 12/11/13, 9:26 AM, Eric Covener wrote:
> If you can run in translate_name, just do what mod_alias does.
> If you have to run as a handler, maybe look at how mod_rewrite does
> its internal redirect.
I would stay away from duplicating what mod_rewrite does in translate_name for
internal redirect
On 12/22/13, 3:13 PM, Allasso Travesser wrote:
> Thank you, Ben, very informative. So I get from this that unmodified,
> mod_auth_digest behaves as I said, though it could be modified to force the
> browser to do a prompt.
Yes, sorry if I wasn't very clear about that.
> I note that in any case
Thank you, Ben, very informative. So I get from this that unmodified,
mod_auth_digest behaves as I said, though it could be modified to force the
browser to do a prompt.
I note that in any case though, the module has no knowledge of what the user is
doing with the browser, such as shut-down/re
On 12/22/13 6:07 AM, Allasso Travesser wrote:
> So I believe that mod_auth_digest has no and uses no mechanism for tracking
> sessions, and always operates in a stateless context. In essence, for each
> request it checks the request header for proper login metadata, and if and
> only
> if it qual
Hello,
I have been studying mod_auth_digest to determine how it knows when when a
browser has ended its session, thinking it sends metadata to tell the browser
to prompt the user again for login/password at the beginning of a new session.
I was interested in the behavior which I observed for d
