Hi folks,
I deployed SSL on my web server, and I am trying to enforce the use of SSL.
So, I turned on the "Require secure channel (SSL)" option which can be found under Directory Security/Secure Communications.
Up to this point, I can access any resource using HTTPS without problems. If I use HTTP to access any resource, IIS displays the default HTTP 403.4 page -which is the expected behavior.
Now, this is when the problem happens...
I replaced the default HTTP 403.4 page with an IIS custom error so it will show a fancy HTML page instead -I used the URL option to specify the absolute HTML page path.
Now, when I try to access any resource using HTTP (non secure channel), it challenges me
I put valid domain\username, and password, and it still IIS complains.
If I look at the HTTP headers, I see:
HTTP Error 401.1 - Unauthorized.
NTLM
Any ideas?
Thank you, Alex
I deployed SSL on my web server, and I am trying to enforce the use of SSL.
So, I turned on the "Require secure channel (SSL)" option which can be found under Directory Security/Secure Communications.
Up to this point, I can access any resource using HTTPS without problems. If I use HTTP to access any resource, IIS displays the default HTTP 403.4 page -which is the expected behavior.
Now, this is when the problem happens...
I replaced the default HTTP 403.4 page with an IIS custom error so it will show a fancy HTML page instead -I used the URL option to specify the absolute HTML page path.
Now, when I try to access any resource using HTTP (non secure channel), it challenges me
I put valid domain\username, and password, and it still IIS complains.
If I look at the HTTP headers, I see:
HTTP Error 401.1 - Unauthorized.
NTLM
Any ideas?
Thank you, Alex