I've been digging and I think I think I may have found the answer to both my questions - RFC2616

---------------------------------------------------------------------------
14.8 Authorization

A user agent that wishes to authenticate itself with a server--usually, but not necessarily, after receiving a 401 response--does so by including an Authorization request-header field with the request. The Authorization field value consists of credentials containing the authentication information of the user agent for the realm of  the resource being requested.

Authorization = "Authorization" ":" credentials
HTTP access authentication is described in �HTTP Authentication: Basic and Digest Access Authentication� [43]. If a request is authenticated and a realm specified, the same credentials SHOULD be valid for all other requests within this realm (assuming that the authentication scheme itself does not require otherwise, such as credentials that vary according to a challenge value or using synchronized clocks).
-----------------------------------------------------------------------------

Now all I have to do is work out how to do this - perhaps using ns_respond?

        Steve
At 01/05/01 22:39, you wrote:
Is it possible to obtain authorisation from User Name and Password fields
passed in from a form rather than the network password window (IE5) thrown
up by nsperm?

I've had a go with ns_checkurl et al in a preauth filter & whilst I can
check permission to a URL I can't find a way of setting the authorisation -
it still goes onto the password window when I request the URL.

As always your guidance would be appreciated.

Whilst I'm asking, I assume the password window comes up in response to a
reply from the server to the browser's request for the URL. Does anyone
have a source for documentation on this process (online preferably).

Thanks

        Steve

Reply via email to