You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Michael Smith <mj...@iii.co.uk> on 1998/03/27 11:25:08 UTC
Something broke on the way to 1.3 ...
Just upgraded most of our servers from 1.2.6 to 1.3b6-dev. This went
smoothly with just one little exception. To try to cut a long
httpd.conf short I had something like the following
ProxyPass /proxy/foo http://foo/
<Location ~ "/register|/admin">
require valid-user
</Location>
A user asking for
/proxy/foo/register
would need to authenticate themself before the proxy request took
place. This all worked fine!
Under 1.3 however, a user asking for the same URL gets a 407 (Proxy
authentication required) error - which the browser (Communicator in this
case) doesn't take to mean that it should pop up a username/password
box. Hence the request never gets to the proxy server
I'm not sure what behaviour is "correct", but figured it was worth
reporting.
Mike
Re: Something broke on the way to 1.3 ...
Posted by Dean Gaudet <dg...@arctic.org>.
Was there resolution on this?
Dean
On Fri, 27 Mar 1998, Michael Smith wrote:
> Just upgraded most of our servers from 1.2.6 to 1.3b6-dev. This went
> smoothly with just one little exception. To try to cut a long
> httpd.conf short I had something like the following
>
> ProxyPass /proxy/foo http://foo/
> <Location ~ "/register|/admin">
> require valid-user
> </Location>
>
> A user asking for
>
> /proxy/foo/register
>
> would need to authenticate themself before the proxy request took
> place. This all worked fine!
>
> Under 1.3 however, a user asking for the same URL gets a 407 (Proxy
> authentication required) error - which the browser (Communicator in this
> case) doesn't take to mean that it should pop up a username/password
> box. Hence the request never gets to the proxy server
>
> I'm not sure what behaviour is "correct", but figured it was worth
> reporting.
>
> Mike
>
>
>