On Fri, Jan 8, 2010 at 15:03, Michel Servaes <[email protected]> wrote: > Also, the machine is acting as a Secure Gateway for Citrix - so I don't want > to tamper a lot on a (for the rest) working config... > I just want to avoid the obligation to let my users type 'https' :-)
The problem is that 'https' doesn't just specify the port, it also tells the browser whether it needs to negotiate SSL/TLS or not. If a browser is pointed at http://something, it's not going to expect the SSL negotiation and your user will see garbage. The proper way to do this is to have a minimal service running on port 80 providing 302's for every request to https://<request>. This is trivial to do in Apache, and I'd be surprised if it wasn't trivial in IIS. RB --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
