> well, this is the case for HTTP.
:)
>
>
> Well I am using a non-HTTP protocol (implemented with the
> multiprotocol capability of Apache2) where client and server
> negotiate on an auth mechanism (e.g. CRAM-MD5 or CRAM-SHA1).
>
> These auth mechanisms are impl
Geoffrey,
thanks for the quick reply.
> > When you are implementing your own authentication mechanism e.g.
> > in a server using the multiprotocol feature you have to pass two
> > pieces of information to the Auth handler: the name of the auth
> > mechanism used and the data submi
