Re: Client Authorization Request & More General Mechanisms

Anselm Baird_Smith wrote:

> 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
>
> Anselm.

The filters now available include:    AccessLimitFilter
    CacheFilter
    CounterFilter
    DebugFilter
    ErrorFilter
    GZIPFilter
    ProcessFilter
    PutFilter
    PutListResource
    PutSizeFilter
    PutedEntry
    SimpleCacheFilter

...by descriptions in the docs, none would _appear_ to do this.  If
possible I would be interested in seeing this example if you could
make it available.

BTW, what generates the client-side authorization dialog?

Regards,

Paul.
 
 

  
--

********************************************************************
Paul Pazandak                                      pazandak@objs.com
Object Services and Consulting, Inc.             http://www.objs.com
Minneapolis, Minnesota 55420-5409                       612-881-6498
********************************************************************

Received on Wednesday, 27 August 1997 10:14:15 UTC