Re:Why Use Nginx?
by needcaffeine on Sunday March 24, 2013 @10:43PM
(#5435032)
Adding one more to that list-- you can host different domains on different ports (but your load balancer will need to for example direct :443 to :8443). This is common practice for people that use Amazon's ELB, for example.
Nginx can (and according to wikipedia Apache can too), I have been doing so until my old certificate expired. It's called SNI (https://en.wikipedia.org/wiki/Server_Name_Indication) and if your openSSL version has support compiled in, it works without any additional configuration (Beyond just normally specifying the correct certificate and key for the correct server)
Yes, that's why I mentioned SNI in my post.
Re:Why Use Nginx?
by AaronBBrown on Monday March 25, 2013 @08:51AM
(#5436678)
SNI has the problem that it's not supported on all browsers or operating systems, so even if it worked without configuration it doesn't solve the problem for most use cases. Assuming multiple subdomains on the same domain the only viable alternative to multiple IPs is to use a wildcard certificate.
Re:Why Use Nginx?
by bpatrianakos on Sunday March 24, 2013 @06:55PM
(#5434187)
My mistake. I was always told Nginx can serve multiple SSL sites with no extra work required besides the usual configuration you'd change for a single SSL site.
So you said you "love being able" to do something that you have not tried (since you didn't know it was impossible you must not have tried it)? I think you should evaluate systems based on how they work for your use case, not by how they might work if you wanted to do something later.
Re:Why Use Nginx?
by icebraining on Sunday March 24, 2013 @09:09PM
(#5434695)
It can; it's just using SNI without explicitly asking you to enable anything.
What? Neither Apache nor nginx can serve multiple SSL sites off a single IP without a UCC certificate, SNI, or multiple IPs. SSL requests have their Host header encrypted, which means the server doesn't know which SSL certificate to present until after encryption.