W3C home > Mailing lists > Public > www-jigsaw@w3.org > July to August 1997

Client Authorization Request & More General Mechanisms

From: Anselm Baird_Smith <Anselm.Baird_Smith@sophia.inria.fr>
Date: Wed, 27 Aug 1997 11:43:19 +0200 (MET DST)
Message-Id: <199708270943.LAA01148@www43.inria.fr>
To: pazandak@OBJS.com
Cc: www-jigsaw@w3.org
Paul Pazandak writes:
 > Hello,
 > What portion of code causes the authorization screen to be displayed on
 > the client asking for username & password?  (I am assuming that this
 > mechanism
 > is supported by HTTP). I have had a hard time tracking this down.
 > In addition, is there a more general mechanism available to request
 > information
 > from the user, _after_ the request is made but _prior_ to sending the
 > reply?  E.g. the
 > user asks for document foo.html & the server responds first with "what's
 > your favorite
 > color?"  Selecting "blue" from a list results a reply containing the
 > document foo.html
 > whose text is now blue. ...it's the mechanism that's important here,
 > this is just an
 > illustrative example!

You may want to check cookie support in Jigsaw (along with server side
include it allows to do that kind of things). I wrote an example of
that which will be (if not already) in w3c.jigsaw.filters

Received on Wednesday, 27 August 1997 05:43:38 UTC

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