Hi Greg,
Thanks for the insights. While I know everyone who tracks this issue would
really appreciate an estimate of any kind, the lack of one raises the
priority for implementing a custom domain SSL work around for some users.
Given the discussion in this thread about CloudFlare and reverse
Hey Guys,
I'll try to answer as directly as possible. We want SSL on custom domains
to work. We are working on getting it to work. We've been working on it
for a very long time now. Amit, you said you feel as if there have been
conflicting messages, while the timeframe has taken longer than
Try this out:
http://blog.cloudflare.com/ssl-on-custom-domains-for-appengine-and-other
When our business is ready to launch, this is our intended plan for
always-SSL for our app. Cloudflare does edge caching for all content
too - possibly better than Google's (wholly undocumented and not
Hi
(I apologize, it's a long one).
I'm calling out the app engine team on how they've handled issue
792http://code.google.com/p/googleappengine/issues/detail?id=792colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log
-
ssl/https support on google apps
Amir,
While I can certainly relate that a Lack Of SSL is a severe limitation of
GAE, I also (not being a Google Employee) can say it is likely not GAE's
fault. Google as a whole likely, but I very much suspect that because SSL
works on appspot.com domains. When working in a large company
Hi Brandon,
Regarding your resolution of setting up a squid/proxy that forwards requests
to https://*.appspot.com somewhere:
Having all your traffic go through a single server on AWS or other VPS to
proxy requests for google app engine is equivalent to buying a top of the
line super-car,
I disagree. I would bet money that Putting a Squid in front of your app
would make it faster. Page Level Caching and the ability to put your Image
assets in cache are going to make things faster.
Also I didn't say single there are plenty of solutions that would do PLC
from multiple
