I wonder if another workaround for the IP-based limitations of SSL is to dynamically assign a port for SSL for each app. So, I've got www.myapp.com and when my app is started up, you assign www.myapp.com:7520 for SSL. Another app on the server might get 7521, etc. The assignment is only while the app is running. If the app is killed off that server, the port is freed up for another app. So, as long as you have a larger block of potential IP addresses than the number of apps running simultaneously on a server, you should be fine (and there should be plenty of available ports).
One disadvantage of this is that the special port will require a special redirect, but I think that's manageable. On Oct 16, 3:03 pm, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote: > You may be wondering why we're only supporting appspot.com right now, and > not arbitrary Google Apps domains. This has to do with fundamental > limitations in the SSL protocol > (see:http://en.wikipedia.org/wiki/Https#Limitations). We're currently > investigating workarounds for this using e.g. > <http://en.wikipedia.org/wiki/Server_Name_Indication>SNI > (http://en.wikipedia.org/wiki/Server_Name_Indication), which provides a > viable solution for newer browsers--we'll keep you posted! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
