RE: Pulling up instructions for authentication

> From: Espen Lyngaas [SMTP:Espen.Lyngaas@colorline.no]
>
> When the browser requests a page that Squid discovers needs
> authentication,
> all Squid needs to do is send out an instructions page, (let's call it
> ERR_AUTH_INSTRUCTIONS for instance), directly followed by the HTTP
> Authentication Required code.
>
        It can only send one page because the browser has only asked
        for one page. The page is sent with a "proxy authentication
        required" status code rather than an "OK" status code; it is
        that difference in status code that causes browsers to put up
        dialogue boxes. The page still contains the explanation of the
        rejection and the browser could choose to display that, but none
        do until the login fails or is cancelled.

        THIS IS A PROBLEM TO TAKE UP WITH THE BROWSER WRITER. SQUID is
        behaving correctly; the browser is also behaving correctly, but
        apparently its user interface design confuses the users; that
        user interface is not specified by the protocol, so could be
changed,
        but only by the browser supplier.
Received on Tue Nov 02 1999 - 05:07:53 MST