Hi Emanuele, Can you explain what you mean by this statement from your previous post?
> https has started working for us last week on a custom domain, although > with a certificate error. > I had request to be included in the trial but had not notification of > that. Thanks, Cayden Meyer Product Manager, Google App Engine On 25 June 2012 08:31, Emanuele Ziglioli <[email protected]>wrote: > Hi Jeff, > > https has started working for us last week on a custom domain, although > with a certificate error. > I had request to be included in the trial but had not notification of that. > > Previously I had had some success doing secure authentication with > json-rpc and Cors: > > https://groups.google.com/forum/?fromgroups#!topic/vosao-cms-development/cybFCgCvYt0 > > Support from browsers for Cors and cookies is spotty at this point in time > but it almost works. > Basically I've implemented a servlet filter on a subpath and secured that > with https. When I receive requests on that subdomain, I strip the /secure/ > prefix and I redirect that request internally. > There's a useful Cors filter here: > http://software.dzhuvinov.com/cors-filter.html > > Emanuele > > On Wednesday, 20 June 2012 10:36:58 UTC+12, Jeff Schnitzer wrote: >> >> Yes, but - unless someone has rolled out a wonderful new feature >> silently - you cannot make https requests to ghs.google.com. The >> "secure" setting only works on *.appspot.com. >> >> Jeff >> >> On Tue, Jun 19, 2012 at 2:48 PM, Hamilton Carter <[email protected]> >> wrote: >> > Hi, >> > >> > I believe you can cause this to happen in your app.yaml file. If you >> have >> > something like: >> > >> > url: .* >> > script: main.py >> > secure: always >> > >> > it might 'force' all accesses through https. >> > >> > Best Regards, >> > Hamilton >> > >> > >> > On Monday, June 18, 2012 12:41:29 PM UTC-5, emmett9001 wrote: >> >> >> >> I have an appengine app that uses Amazon Route53 as its nameserver. >> I've >> >> used Route53 to create a CNAME record of "ghs.google.com" for the >> desired >> >> subdomain. I've also used the google cpanel to link the subdomain to >> the >> >> app. Currently, the app is accessible at https://subdomain.domain.combut >> >> not http://subdomain.domain.com - that is, it's accessible over HTTPS >> but >> >> not HTTP. Is there some misconfiguration in either Route53, Appengine, >> or >> >> the Google Apps control panel that might be causing this issue? Thanks >> for >> >> any help and insight. >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "Google App Engine" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/**msg/google-appengine/-/**Jlcu0ZEO9UcJ<https://groups.google.com/d/msg/google-appengine/-/Jlcu0ZEO9UcJ>. >> >> > >> > To post to this group, send email to google-appengine@googlegroups.** >> com <[email protected]>. >> > To unsubscribe from this group, send email to >> > google-appengine+unsubscribe@**googlegroups.com<google-appengine%[email protected]>. >> >> > For more options, visit this group at >> > http://groups.google.com/**group/google-appengine?hl=en<http://groups.google.com/group/google-appengine?hl=en>. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/FOyZue1PMvwJ. > > 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. > -- 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.
