A word of caution:
When using your own proxy, some of the performance advantages and
features of app engine will not be available.
For example, static files: “App Engine serves static files from
separate servers than those that invoke servlets”
Thanks.
Do people have an estimate of the increased cost of using HTTPS over
HTTP (due to more CPU cycles)?
On Jul 2, 11:28 am, J j.si...@earlystageit.com wrote:
We don't use any cookies until the user logs in and once they log in,
we stay on https for all traffic. Hopefully we don't run into
I didn't. Too afraid of cookie hijacking.
See http://en.wikipedia.org/wiki/HTTP_cookie#Cookie_hijacking. To
quote, However a large number of websites, although using encrypted
https communication for user authentication (i.e. the login page),
subsequently send session cookies and other data over
You would need to set this HTTP proxy outside of app engine. For
example, Squid on amazon EC2. The proxy would be set as reverse proxy,
and should point to your appspot secure domain (to ensure that you
have HTTPS connection all the way to your app). I imagine you would
also need to tell app
I tried it last year using Squid on EC2 as a proof of concept. It
worked well.
Now I'm in the process of putting it in production. Phil, I'd be happy
to compare notes next week or so if you wish.
On Jul 1, 2:52 am, TL twl.e...@gmail.com wrote:
You would need to set this HTTP proxy outside of
How did you do the session cookie transfer from the HTTPS domain to
the HTTP domain? Is this something you can configure in app engine?
Was it possible to log in using HTTPS all the way to app engine and
then transfer the session to the HTTP server using a redirect?
On Jul 1, 3:50 am, J
Does anyone have experience setting up an https capable proxy? I
don't even know where to start. Searching found a number of proxy
lists and instructions to setup a regular http proxy. Maybe I'm not
looking for the right thing here?
Thanks!
Phil
On Jun 14, 5:26 am, Barry Hunter
