How does this affect modules? I see the modules
documentationhttps://developers.google.com/appengine/docs/python/modules/
says
they can be accessed by
http[s]://mobile-frontend.simple-sample.appspot.com for example. However
if I access a module with https I get an invalid certificate error.
I wrote a longer and quite critical comment on Friday, because we had not
been informed of this change, and the consequences for us have been pretty
bad until today. So far the comment has not been released or replied to.
Where is it?
On Friday, January 11, 2013 12:47:15 AM UTC+1, Christina
We were one of the applications using the described logic. However, we
didn't receive an email from you. Since this morning our app with several
thousands of users is offline, and we have already received hundreds of
complaints. To fix the issue we need to update our client and go through
the
Tobias,
Our apologies that this impacted your application and customers. The
initial communication was sent our several months ago with suggested
changes that developers should make to transition off of double wildcard
certs. I realize that this may have missed your inbox. Moving forward,
Chris,
thanks for your email.
This morning we were able to implement a fix by offering a new version of our
app. This is not a comfortable fix and we will loose some users, because
everyone needs to update, but after all the trouble of the last days at least
our service works again.
I just
We have completed sunsetting of the double wildcard SSL certificates. This
email is to remind you to check that you do not have any clients that are
sending requests to URLs with the pattern https://*.*.appspot.com/. For
more details, see https://developers.google.com/appengine/docs/ssl.
On
Hi Christina
Will this -dot- solution work for public backends as well?
Br, Marcel
--
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/-/q_OHUpMeCBIJ.
Somehow, my email notice of this policy landed in my gmail spam folder. ;)
*pats the eager to please spam filter algorithm on the head*
Perhaps feeding the spam filter less sugar before bedtime?
On Thursday, January 10, 2013 3:47:15 PM UTC-8, Christina Ilvento wrote:
*Hi All,*
*
*
*As part
