[google-appengine] Re: HTTPS as a ranking signal
The only thing I can't do now is map my SSL naked domain to my app but that is likely solvable with a wildcard SSL certificate (that I'm too cheap to pay for). We have a wildcard SSL and we still can't do that. If anyone has succeeded in mapping naked SSL please come forward and share your genius. On Monday, August 11, 2014 4:28:41 PM UTC+1, Doug Anderson wrote: I wanted to share my recent partial success with naked domains... with the new cloud console Custom Domains you can map your naked non-SSL domain to your app. After doing that... I detect the naked domain as part of my 'require SSL' logic in the App and redirect to https://www.mydomain.com. So now if someone types mydomain.com or mydomain.com/anypath in their browser it redirects to https://www.mydomain.com/anypath;. So the cloud console helps plug a hole left by the Google Apps alias domains. The only thing I can't do now is map my SSL naked domain to my app but that is likely solvable with a wildcard SSL certificate (that I'm too cheap to pay for). On Friday, August 8, 2014 4:00:25 PM UTC-4, Jason Collins wrote: Re: http://googlewebmastercentral.blogspot.ca/2014/08/https-as-ranking-signal.html Ok Google, now we most definitely need an API to manage custom domains, mount certificates, and configure HTTPS hosting using an API without a Google account requirement. Our Cloud Platform hosted products are whitelabelled, meaning people can serve them on their own domain. As the world moves towards HTTPS-always, we need a scaleable way for our customers to upload and configure their SSL certificates fronting our products without our involvement - and without requiring our customers to use a Google account. That is, we would like APIs that we can build our own user interfaces over top to help our users through this typically frustrating setup experience. BTW, free SNI-based HTTPS termination was a huge step along the way towards this vision - thanks for that! Thanks, j -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: HTTPS as a ranking signal
I hadn't heard about Google Domains until I read it here... it does look very promising... I would also consider moving away from GoDaddy. I found this particularly encouraging... (I imagine comparable App Engine support for paid Apps is more difficult to implement???) Support With Google Domains, you get phone and email support (M-F, 9am to 9pm EST). On Friday, August 8, 2014 4:00:25 PM UTC-4, Jason Collins wrote: Re: http://googlewebmastercentral.blogspot.ca/2014/08/https-as-ranking-signal.html Ok Google, now we most definitely need an API to manage custom domains, mount certificates, and configure HTTPS hosting using an API without a Google account requirement. Our Cloud Platform hosted products are whitelabelled, meaning people can serve them on their own domain. As the world moves towards HTTPS-always, we need a scaleable way for our customers to upload and configure their SSL certificates fronting our products without our involvement - and without requiring our customers to use a Google account. That is, we would like APIs that we can build our own user interfaces over top to help our users through this typically frustrating setup experience. BTW, free SNI-based HTTPS termination was a huge step along the way towards this vision - thanks for that! Thanks, j -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: HTTPS as a ranking signal
I wanted to share my recent partial success with naked domains... with the new cloud console Custom Domains you can map your naked non-SSL domain to your app. After doing that... I detect the naked domain as part of my 'require SSL' logic in the App and redirect to https://www.mydomain.com. So now if someone types mydomain.com or mydomain.com/anypath in their browser it redirects to https://www.mydomain.com/anypath;. So the cloud console helps plug a hole left by the Google Apps alias domains. The only thing I can't do now is map my SSL naked domain to my app but that is likely solvable with a wildcard SSL certificate (that I'm too cheap to pay for). On Friday, August 8, 2014 4:00:25 PM UTC-4, Jason Collins wrote: Re: http://googlewebmastercentral.blogspot.ca/2014/08/https-as-ranking-signal.html Ok Google, now we most definitely need an API to manage custom domains, mount certificates, and configure HTTPS hosting using an API without a Google account requirement. Our Cloud Platform hosted products are whitelabelled, meaning people can serve them on their own domain. As the world moves towards HTTPS-always, we need a scaleable way for our customers to upload and configure their SSL certificates fronting our products without our involvement - and without requiring our customers to use a Google account. That is, we would like APIs that we can build our own user interfaces over top to help our users through this typically frustrating setup experience. BTW, free SNI-based HTTPS termination was a huge step along the way towards this vision - thanks for that! Thanks, j -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: HTTPS as a ranking signal
On Mon, Aug 11, 2014 at 10:07 AM, Doug Anderson d...@claystreet.com wrote: I hadn't heard about Google Domains until I read it here... it does look very promising... I would also consider moving away from GoDaddy. I found this particularly encouraging... Support With Google Domains, you get phone and email support (M-F, 9am to 9pm EST). +1. Plus GoDaddy charges for additional services such as private domain registration, while Google Domains seems to offer it for free: http://domains.google.com/about/features.html . That alone saves a nice amount of money - -Vinny P Technology Media Consultant Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: HTTPS as a ranking signal
I will also jump in and request simple and automatic SSL integration and improved DNS capabilities to easily redirect naked domains or implement simple rules (cloudflare is great, however appengine should do these things on it's own, using another service to handle these things makes me paranoid, they are extremely crucial) -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
