T
Tyler Robbins
I am seeing that IE will not always sent the
Authentication header for
files protected with Basic Authentication. This causes
some of my
users to get repeatedly prompted for their username and
password.
Using HTTPWatch (great tool), I can easily watch the
Authentication
header get passed for every file. Then, on some files
(fairly
consistent which ones), it won't pass the Authentication
header, and
the browser prompts for a password. You can easily enter
the same
username/password and it will accept it and pass the
header. I have
double- and triple-checked that the security on this file
is the same.
My configuration: I have an IIS 5.0/Win2K server with
Basic
Authentication on all the files. On the client I have
Win2k with IE6.
Not all machines have this problem, even ones that
seemingly have the
same configuration. But we have seen it on NT, Win2K and
XP running
IE6.
Why is this happening? Anyone else dealing with this?
Authentication header for
files protected with Basic Authentication. This causes
some of my
users to get repeatedly prompted for their username and
password.
Using HTTPWatch (great tool), I can easily watch the
Authentication
header get passed for every file. Then, on some files
(fairly
consistent which ones), it won't pass the Authentication
header, and
the browser prompts for a password. You can easily enter
the same
username/password and it will accept it and pass the
header. I have
double- and triple-checked that the security on this file
is the same.
My configuration: I have an IIS 5.0/Win2K server with
Basic
Authentication on all the files. On the client I have
Win2k with IE6.
Not all machines have this problem, even ones that
seemingly have the
same configuration. But we have seen it on NT, Win2K and
XP running
IE6.
Why is this happening? Anyone else dealing with this?