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

[www-jigsaw] <none>

From: Zahid Ahmed <zahid.ahmed@commerceone.com>
Date: Wed, 1 Sep 1999 00:28:46 -0400 (EDT)
Message-ID: <F289FD995459D311BBCF00A0C9E91ABF02335C@ip5-13.5.20.172.in-addr.arpa>
To: www-jigsaw@w3c.org

would it be OK, to add a 3rd field as a authentication parameter in the
client-side HTTPCredential and send as part of the basic cookie? It seems to
be received by the Jigsaw Web Server fine
(in addition to userId/password)? Obviously, this would mean that
we will need to write our own custom auth handler on server side.
E.g., 
 HTTPBasic decoded cookie: 3rdAuthfield:userId:password

Will the 3rd field added to HttpCredential as part of basic cookie
impact any standard WWW proxy authentication? E.g., should the
3rd field order be at the end s.t. proxies continue to process
the first two field according as userId/password?
Received on Wednesday, 1 September 1999 04:25:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:33 GMT