I think you are misunderstanding what I'm saying. On the Java 8 runtime you can do without URLFetch because the limitations that were in effect on the older runtimes are lifted. Because of that I can work around it by using any other http library, which is what the documentation is referring to. I'm glad that this is possible but it's still a workaround.
>From the errors I was encountering, I still believe the actual URLFetch service has an issue and has flaky behaviour (as Joshua also mentions), which should be resolved by Google as it may affect other apps using that service, especially older App Engine apps migrating from the previous runtime(s). On Thursday, March 29, 2018 at 10:42:18 PM UTC+2, George (Cloud Platform Support) wrote: > > In the "Issuing an HTTP request" sub-chapter of the "Issuing HTTP(S) > Requests" document > <https://cloud.google.com/appengine/docs/standard/python/issue-requests>, > this possibility is indicated: "You can also use the third-party requests > library as long as you configure it to use URLFetch." There is no doubt > that other people will be interested in details about your successful > implementation. > -- 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 https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/00547d40-4b24-42a4-bf6b-a410093dea79%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
