in reply to Re: Passing a 401 header with CGI.pm ?
in thread Passing a 401 header with CGI.pm ?

From what I recall, Digest authentication works just like Basic, with the exception that the CLIENT makes an MD5 hash of the password string (and perhaps other session data)before it sends the authentication data over the wire; w/ basic authentication, the password is sent in cleartext. Also, Netscape 4.x does not support Digest authentication. But again, I'd advise reading the RFCs.

Philosophy can be made out of anything. Or less -- Jerry A. Fodor

  • Comment on Re: Re: Passing a 401 header with CGI.pm ?

Replies are listed 'Best First'.
Re: Re: Re: Passing a 401 header with CGI.pm ?
by swiftone (Curate) on Dec 02, 2000 at 02:21 UTC
    Right...but I'm talking about the possibility that information can be sent from server to client for use in the next client to server discussion...which the redirect header already does for URI. The question is
    1. How do we construct an Authorization header to pass back to the client (with the intention of the client using it)
      This is my attempt to find that info.

    2. Does it work, or does the client discard such data?
      Someone will have to test that.
[reply]

In Section Seekers of Perl Wisdom