<also posted in the win2k3 forum>
I want to force the application that we are building under asp.net to use port 443 (SSL) for a specific page.
That, in itself is no problem. Here is what I did:
Install Certificate services, and configure it correctly.
Install a certificate for the website
Select port 443 for secure comms.
On the page that must be secure I selected the "require secure..."
Change the 403-4 custom error page for that particular page to redirect to the page but with https:// in front of it.
Easy - done this many times before on Win2k servers.
However, am I missing something on win2k3? If I go
I get either the redirection (if in place) or the error 403-4 page (if I have left that in place). Which is expected
So I now go:
and I get error
Which, whilst it is not 404, it seems to be the SSL equivilent of 404.
Any clues folks?
M.
Hollingside Technologies, Making Technology work for you.
I want to force the application that we are building under asp.net to use port 443 (SSL) for a specific page.
That, in itself is no problem. Here is what I did:
Install Certificate services, and configure it correctly.
Install a certificate for the website
Select port 443 for secure comms.
On the page that must be secure I selected the "require secure..."
Change the 403-4 custom error page for that particular page to redirect to the page but with https:// in front of it.
Easy - done this many times before on Win2k servers.
However, am I missing something on win2k3? If I go
I get either the redirection (if in place) or the error 403-4 page (if I have left that in place). Which is expected
So I now go:
and I get error
Code:
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.Which, whilst it is not 404, it seems to be the SSL equivilent of 404.
Any clues folks?
M.
Hollingside Technologies, Making Technology work for you.