directories password protected are caching credentials

[stjulian]

Well, thats what it looks like anyway.

Here's what happens:

A text file is generated and stored within a directory (a virtual directory)
within our website. The directory has permissions set (on the server) to
cause the username/password dialog to pop up once the text file URL or the
directory URL is clicked. Once you provide your credentials, the file or
directory is displayed in your browser.

The problem is, when you hit "back", the username/password dialog box keeps
popping up even though you are going back to a page which does not require a
username/password. And, no amount of influencing will convince the dialog
otherwise!

The server is Windows Server 2003 running IIS 6.0.

I am using IE 7. This seems to have cropped up recently.

Is there a fix for this behavior?

Is there a proper way to allow HTTP access to a directory and still require
the username and password?

Julian

 

[Bob Milutinovic]

Well, thats what it looks like anyway.

Here's what happens:

A text file is generated and stored within a directory (a virtual
directory)
within our website. The directory has permissions set (on the server) to
cause the username/password dialog to pop up once the text file URL or the
directory URL is clicked. Once you provide your credentials, the file or
directory is displayed in your browser.

The problem is, when you hit "back", the username/password dialog box
keeps
popping up even though you are going back to a page which does not require
a
username/password. And, no amount of influencing will convince the dialog
otherwise!

The server is Windows Server 2003 running IIS 6.0.

I am using IE 7. This seems to have cropped up recently.

Is there a fix for this behavior?

Is there a proper way to allow HTTP access to a directory and still
require
the username and password?

Have you tried it from other machines with different browsers? IE6? FF?
Opera?

If it was working as intended previously, and has now failed with now
programmatical intervention on your part, you can virtually guarantee it'll
be due to a tweak in a Microsoft upgrade that's just come through. Whether
that tweak was to IIS or to IE is what you need to determine - hence my
suggestion of trying it with other browsers.

--
Bob Milutinovic
Cognicom - "Australia's Web Presence Specialists"
http://www.cognicom.net.au/
telephone (0417) 45-77-66
facsimile (02) 9824-2240