Some of our experiences as well as hints for implementing an https reverse proxy are documented here: http://wp.me/poqXr-5I. The performance numbers are from measurements done this past weekend. There is room for improvement and we hope to be able to report on them in the future. Suggestions for improvements are welcome.
TL, thanks for the caution. Gave me the idea to access static files using by using abc.appspot.com as the host URL instead of www.abc.com. So those accesses still use https but not the reverse proxy. On Jul 19, 9:29 pm, TL <[email protected]> wrote: > 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”http://code.google.com/appengine/docs/java/gettingstarted/staticfiles... > Now its your proxy that is serving those static files, unless you use > different URL schemes for files. So if app engine has edge caching or > a CDN for those files, you will not benefit from it. > > It is also unclear whether DOS attack will take into account proxied > IPs (set in X-Forwarded-For header). Whether it is or not, you need to > handle DOS attacks on your proxy yourself. > > In other words, proxying diminishes some of the advantages of using > app engine over other hosting options. So the real solution is that > google supportsHTTPSby allocating IPs to customers that opt in (as > opposed to TLS). -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. 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.
