W3C home > Mailing lists > Public > www-jigsaw@w3.org > September to October 1999

RE: Client side use of Basic Authentication, proxy.

From: Yves Lafon <ylafon@w3.org>
Date: Tue, 5 Oct 1999 17:18:35 +0200 (MET DST)
To: Zahid Ahmed <zahid.ahmed@commerceone.com>
cc: www-jigsaw@w3.org
Message-ID: <Pine.GSO.4.10.9910051713540.6268-100000@tarantula.inria.fr>
On Thu, 30 Sep 1999, Zahid Ahmed wrote:

> Is there specific config reqmnts required  w.r.t.
> proxy configuration when a Web client running inside
> one firewall, say FW1 with a proxy#1, and Jigsaw 
> Web server running in another firewall, say FW2 with a
> proxy#2, s.t. the client sends the Basic Authentication 
> data and the Jigsaw Web Server http server completely 
> receives the Basic Auth data for authentication?
> E.g., do the client-side FW proxies authenticate the
> Basic Auth data in addition to the server proxies
> and ultimately the Jigsaw Web Server? 

To authenticate on a proxy, the header used will be Proxy-Authorization,
to authenticate on a server, the header will be "Authorization". As long
as your browser is able to set those two headers, you win :)
Jigsaw configured as a proxy will emit a "Proxy-Autheticate" instead of a
If both proxies needs authorization, there is a problem...
However, it can be solved using the ProxyDispatcher on the first proxy,
using the proxyauth directive.
Hope this helps,

      /\          - Yves Lafon - World Wide Web Consortium - 
  /\ /  \        Architecture Domain - Jigsaw Activity Leader
 /  \    \/\    
/    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org    
Received on Tuesday, 5 October 1999 11:18:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:35 UTC