You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Jonathan Bartlett <jo...@wolfram.com> on 1999/07/15 15:54:07 UTC
general/4731: Unable to Authenticate using ProxyPass
>Number: 4731
>Category: general
>Synopsis: Unable to Authenticate using ProxyPass
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Thu Jul 15 09:10:01 PDT 1999
>Last-Modified:
>Originator: johnnyb@wolfram.com
>Organization:
apache
>Release: 1.3.6
>Environment:
Using Red Hat Linux 6.0 w/, but, looking at the source it should occur in all OSs
>Description:
Modern Browsers, even those that claim HTTP/1.1 compliance, do not properly support 407s, Proxy-Authenticate, and Proxy-Authorization headers. When using a proxy connection, Apache always uses these methods for authentication. Therefore, browsers are unable to get authorization.
>How-To-Repeat:
Our setup uses a ProxyPass with Authorization requirements on both sides of the Proxy
>Fix:
I have a patch available at http://members.wri.com/johnnyb/
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database 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! ]