[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modproxy-dev
Subject:    Re: Question regarding changes for mod_proxy  on apache 1.3.X to
From:       Ian Holsman <Ian.Holsman () cnet ! com>
Date:       2003-03-11 19:38:44
[Download RAW message or body]

sounds like a bug to me.

a quick workaround:
maybe you change the proxypass to use a hostname instead of an IP #.
It could also be that you haven't got your reverse IP set up for that 
machine. and it can't create the x-forwarded-for line.

cheers
ian

you should probably raise a bugzilla via nagoya.apache.org


Jorge Reyes wrote:
> Thanks I will try to post on that mailing list.
> PS
> 
> "No Longer Works" means:
> On Apache 1.3.x the user who type http://www.zyx.com/admin would be presented with \
> an authetication window, on apache 2.0 the request fails and the log file (error \
> log) reads: 
> [Tue Mar 11 00:06:18 2003] [error] [client 111.111.111.111] proxy: DNS lookup \
> failure for: 10.5.10.51error returned by /error/HTTP_UNAUTHORIZED.html.var 
> I have read the doc's regarding the new settings and directives however I still can \
> not find and adequate solution. 
> -----Original Message-----
> From: Graham Leggett [mailto:minfrin@sharp.fm]
> Sent: Tuesday, March 11, 2003 1:56 AM
> To: modproxy-dev@apache.org
> Subject: Re: Question regarding changes for mod_proxy on apache 1.3.X to
> 2.0X
> 
> 
> Jorge Reyes wrote:
> 
> 
> > I hope this is the right mailing list to request information regarding 
> > the changes on mod_proxy from Apache 1.3 to apache 2.0
> 
> 
> A better place to post this would be the main dev@httpd.apache.org 
> mailing list, as your question has to do with authentication.
> 
> 
> > The configuration that works under 1.3 but no longer does on 2.0 is:
> 
> 
> Define "no longer works".
> 
> Regards,
> Graham


[prev in list] [next in list] [prev in thread] [next in thread]