IIS Server Security - Re: Assigning a Certificate to non standard TCP port 8080 instead

This is Interesting: Free IT Magazines  
Home > Archive > IIS Server Security > December 2004 > Re: Assigning a Certificate to non standard TCP port 8080 instead





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Assigning a Certificate to non standard TCP port 8080 instead
Ralph Devlin

2004-12-15, 6:38 pm

I had TCP and SSL ports as being different entitys, I was able to use the SSL
port 443 and that worked on getting port 443 traffic through to the
certificate.. thanks

"Ralph Devlin" wrote:
[vbcol=seagreen]
> I'm able to specify a different SSL port by doing that, but what I'm trying
> to do is use a different port for web traffic, 8080 instead of having port 80
> traffic. my ceritificates work when using the default TCP port 80, but after
> having it listen in port 8080 the certificate does not load and therefore I
> get the page cannot be displayed
>
> "hal@nospam.com" wrote:
>
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com