Hi,
On Sun, Oct 03, 2010 at 08:56:06PM +0200, Carlos Soto wrote:
> If a server is configured with auth-user-pass-optional and
> username-as-common-name it is possible that the auth-user-pass-verify script
> will validate a connection with no username as it is optional. It that case
> the common_na
Author: Carlos Soto mailto:carlos.s...@terra.es> >
Variable common_name can be blank in client-connect script
If a server is configured with auth-user-pass-optional and
username-as-common-name it is possible that the auth-user-pass-verify script
will validate a connection with no username as
> Have you been able to figure out how Apache handles this? Is it using
> the Host: header in CONNECT requests for anything, and if yes, what should
> be in there? Is that documented anywhere?
I made a test, but it was inconclusive. I couldn't find any pattern in
the results I got. My configurat
Hi,
On Thu, Sep 30, 2010 at 02:38:40AM +0200, Peter Stuge wrote:
> Acked-by: Peter Stuge
Acked-by: Gert Doering
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany
Hi,
On Thu, Sep 30, 2010 at 03:55:55PM +0100, Lars Hupel wrote:
> My expectation would be that the proxy server uses the host name given
> after GET (or CONNECT) to regulate access control (and to forward it as
> 'new' Host header) and the Host header to disambiguate between multiple
> virtual hos
