Question regarding changes for mod_proxy on apache 1.3.X to 2.0X

This is a multi-part message in MIME format.

------=_NextPartTM-000-416eeae2-5338-45a9-81b2-3810831edc5a
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C2E7AE.34B640CD"

------_=_NextPart_001_01C2E7AE.34B640CD
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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

We used in Apache 1.3.X the followin setup which no loner works under =
apacge 2.0 and I was wondering if any one can help. I have read the =
doc's regarding the new settings and directives however I still can not =
find and adequate solution.

We use Virtual server with mod_proxy and have certain directories =
protected via password files.
The proxy is to a remote server and the password file is on the local =
apache proxy server.

The configuration that works under 1.3 but no longer does on 2.0 is:

<VirtualHost 10.5.21.212:80>
UseCanonicalName off
ProxyRequests off

ProxyPass / <http://10.5.10.51/> http://10.5.10.51
ProxyPassReverse / <http://10.5.10.51/> http://10.5.10.51

<Location /admin/>
AllowOverride AuthConfig
AuthUserFile /etc/httpd/conf/passwd/adminpasswords
AuthName "Live Corp Admin"
AuthType Basic
require valid-user admin
</Location>

ServerName yyy.yyy.com
ServerAlias yyy
ServerAdmin admin [at] localhost
ErrorLog /var/log/httpd/error_log_Virtual_yyy
TransferLog /var/log/httpd/access_log_virtual_yyy
</VirtualHost>


------_=_NextPart_001_01C2E7AE.34B640CD
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D587080409-11032003><FONT face=3DArial size=3D2>I hope =
this is the
right mailing list to request information regarding the changes on <FONT =

size=3D3><FONT face=3D"Courier New">mod_proxy</FONT><FONT face=3D"Times =
New Roman">
</FONT><FONT face=3D"Courier New">from Apache 1.3 to apache
2.0</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D587080409-11032003><FONT
face=3D"Courier New"></FONT></SPAN> </DIV>
<DIV><SPAN class=3D587080409-11032003><FONT face=3D"Courier New">We used =
in Apache
1.3.X the followin setup which no loner works under apacge 2.0 and I was =

wondering if any one can help. I have read the doc's regarding the new =
settings
and directives however I still can not find and adequate
solution.</FONT></SPAN></DIV>
<DIV><SPAN class=3D587080409-11032003><FONT
face=3D"Courier New"></FONT></SPAN> </DIV>
<DIV><SPAN class=3D587080409-11032003><FONT face=3D"Courier New">We use =
Virtual
server with mod_proxy and have certain directories protected via =
password
files.</FONT></SPAN></DIV>
<DIV><SPAN class=3D587080409-11032003><FONT face=3D"Courier New">The =
proxy is to a
remote server and the password file is on the local apache proxy
server.</FONT></SPAN></DIV>
<DIV><SPAN class=3D587080409-11032003><FONT
face=3D"Courier New"></FONT></SPAN> </DIV>
<DIV><SPAN class=3D587080409-11032003><FONT face=3D"Courier New">The =
configuration
that works under 1.3 but no longer does on 2.0 is:</FONT></SPAN></DIV>
<DIV><SPAN class=3D587080409-11032003><FONT
face=3D"Courier New"></FONT></SPAN> </DIV>
<DIV><SPAN class=3D587080409-11032003><FONT face=3D"Courier New"><FONT =
face=3DArial
size=3D2><VirtualHost 10.5.21.212:80><BR>UseCanonicalName
off<BR>ProxyRequests off</FONT>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><SPAN class=3D587080409-11032003><FONT face=3DArial =
size=3D2>ProxyPass /
</FONT><A href=3D"http://10.5.10.51/"><FONT face=3DArial
size=3D2>http://10.5.10.51</FONT></A><BR><FONT face=3DArial =
size=3D2>ProxyPassReverse
/  </FONT><A href=3D"http://10.5.10.51/"><FONT face=3DArial
size=3D2>http://10.5.10.51</FONT></A><BR></SPAN></DIV></FONT></SPAN></DIV=
>
<DIV><SPAN class=3D587080409-11032003><FONT face=3DArial =
size=3D2><Location
/admin/><BR>    AllowOverride 
AuthConfig<BR>    AuthUserFile
/etc/httpd/conf/passwd/adminpasswords<BR>    AuthName =
"Live Corp
Admin"<BR>    AuthType Basic<BR>    =
require
valid-user admin<BR></Location></FONT></SPAN></DIV>
<DIV><SPAN class=3D587080409-11032003><FONT face=3DArial =
size=3D2><BR>ServerName
yyy.yyy.com<BR>ServerAlias yyy<BR>ServerAdmin <A
href=3D"mailto:admin [at] localhost">admin [at] localhost</A><BR>ErrorLog
/var/log/httpd/error_log_Virtual_yyy<BR>TransferLog
/var/log/httpd/access_log_virtual_yyy<BR></VirtualHost>
</FONT></SPAN></DIV>
<DIV><SPAN class=3D587080409-11032003><FONT face=3DArial
size=3D2> </DIV></FONT></SPAN></BODY></HTML>

------_=_NextPart_001_01C2E7AE.34B640CD--

------=_NextPartTM-000-416eeae2-5338-45a9-81b2-3810831edc5a- -
Jorge Reyes [ Di, 11 März 2003 10:11 ] [ ID #12286 ]

Re: Question regarding changes for mod_proxy on apache 1.3.X to2.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 [at] 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
--
-----------------------------------------
minfrin [at] sharp.fm "There's a moon
over Bourbon Street
tonight..."
Graham Leggett [ Di, 11 März 2003 10:55 ] [ ID #12287 ]

RE: Question regarding changes for mod_proxy on apache 1.3.X to 2.0X

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 [at] sharp.fm]
Sent: Tuesday, March 11, 2003 1:56 AM
To: modproxy-dev [at] 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 [at] 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
--
-----------------------------------------
minfrin [at] sharp.fm "There's a moon
over Bourbon Street
tonight..."
Jorge Reyes [ Di, 11 März 2003 17:32 ] [ ID #12290 ]

Re: Question regarding changes for mod_proxy on apache 1.3.X to2.0X

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 [at] sharp.fm]
> Sent: Tuesday, March 11, 2003 1:56 AM
> To: modproxy-dev [at] 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 [at] 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
Ian Holsman [ Di, 11 März 2003 20:38 ] [ ID #12291 ]
Webserver » gmane.comp.apache.mod-proxy » Question regarding changes for mod_proxy on apache 1.3.X to 2.0X

Vorheriges Thema: mod_rewrite/mod_header/mod_proxy problem
Nächstes Thema: [PATCH] mod_proxy handling of chunked requests