* Roger <rno...@gmail.com> [2009-12-14 17:47]: > The situation that I was talking about is that if someone access > http://example.com or http://www.example.com > then redirect to either https://www.example.com OR https://example.com.
Sure. > But of course, you cannot stop someone for trying to access > https://www.example.com when you only have SSL for > https://example.com or the other way around. Given that hardly anyone ever types complete URLs including the schema, sticking with a single SSL vhost and redirecting to that from all the plain HTTP vhosts is very probably "good enough". > But sometimes multiple public IPs are not an option. http://markmail.org/message/yr52ptnpgbocgvad But we should just push for SNI, I guess. -peter --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org " from the digest: users-digest-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
