>Number:         3395
>Category:       general
>Synopsis:       Problem with ProxyPass and authentification
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Nov 12 14:10:00 PST 1998
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.3
>Environment:
Unixware 2.1.2
UNIX_SV a2k 4.2MP 2.1.2 i386 x86at
>Description:
I have two webservers. Server1 uses ProxyPass to let clients access server2.
This works just fine. But when I restrict access to server1 and the client tries
to access server2, the client gets "407 Proxy Authentification required" 
What is wrong??? This worked just fine with Apache 1.2.5. I use the following 
configuration:
ServerType standalone
HostnameLookups off
User nobody
Group nobody
ServerAdmin [EMAIL PROTECTED]
ServerRoot "/usr/htroot"
DocumentRoot "/usr/htdocs"
ErrorLog logs/error_log
CustomLog logs/access_log common
ScoreBoardFile logs/apache_runtime_status
ServerName web.wide.world.se
ServerSignature on
UseCanonicalName on
KeepAlive On
ProxyRequests Off
ProxyPass /web2 http://web2.wide.world.se
<Location ~ ".*">
   Options FollowSymLinks Includes MultiViews ExecCGI
   AllowOverride None
   AuthType Basic
   AuthName "OnLine"
   AuthUserFile /usr/etc/passwd
   <Limit GET POST>
      require valid-user
   </Limit>
</Location>
>How-To-Repeat:
Set up 2 web servers.  Have one proxy the other using the above configuration. 
Netscape reports 407 Proxy Authentification required.
>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]



Reply via email to