Hi William,
> > Many people access websites from behind corporate firewalls (or personal
> > firewall software) which is only configured to allow traffic from ports
80
> > and 443. I have been behind such firewalls (and proxys) and when the
website
> > is on a different port I simply cannot load it at all!
>
> This is rare though.
Not from what I have seen :-) Actually right NOW I am behind one at my
daytime work...
How do you explain to your customers that they cannot visit that website
cause of their firewall and they have to wait till they get home to look at
the site? ugh!
> > What SSL cert would you serve on that port? I cannot see how you
wouldn't
> > get the browser complaining that the cert doesnt match the requested
domain.
>
> Create a "default" one. Yes, the warning will come up, but that's
> not a big issue really.
It is when you you are hosting secure sites for customers and the supposed
secure sites pop up browser dialog boxes complaining about the certificates.
*YOU* know it is not a problem, *I* know it is not a problem, but the average
person does not, not to mention it doesn't look very professional having
warnings boxes pop up everywhere...
I absolutely *HATE* websites that are on non-standard ports for these very
reasons, but then that is my $0.02 worth (hmm, given the Aussie dollar
exchange rates it's probably only worth $0.01 hehehee)
--
Regards,
+-----------------------+---------------------------------+
| Peter Kiem | E-Mail : <[EMAIL PROTECTED]> |
| Zordah IT | Mobile : +61 0414 724 766 |
| IT Consultancy & | WWW : www.zordah.net |
| Internet Hosting | ICQ : "Zordah" 866661 |
+-----------------------+---------------------------------+
