As observed in the other thread and confirmed independently on my end, testing seems to work, indicating that the standards are met. Urllib2 will not use SHA256, although UrlFetch does, so it's important to use UrlFetch. More documentation on UrlFetch is a current goal of the product team, so expect that updates to the docs which elaborate these details to come in the short-to-medium term.
On Saturday, June 6, 2015 at 3:05:09 PM UTC-4, Iron Mountain Foundry wrote: > > Cross-referencing another thread discussing this same topic: > > https://groups.google.com/forum/#!topic/google-appengine/YyTC6PBgYxw > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/e5517fa8-c967-4660-8086-26df962f866e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
