This is a reply to the (already closed) thread at http://groups.google.com/group/google-appengine/browse_thread/thread/4c93c01f75ee3ce4
This problem still exists and somehow conflicts with the security options described at http://code.google.com/appengine/docs/python/tools/configuration.html#Secure_URLs At least this is how I understood it. You have two exclusive options for a restricted/secure application a) Serve the application at myapp.example.com (with Google Apps) and have it restricted to users from this domain during the registration setup for this application. b) Serve the application from myapp.appspot.com and provide secure connections via HTTPs. Variations: you could use a (fragile) hybrid approach for applications on (b) and check whether the user's email address has the same domain you planned to restrict to. I just want to verify what others think about that, or whether there is ongoing discussion on this subject, or even a feature request or defect that I haven't found with a primitive selection of search terms. Thank you, Kariem --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
