Repository navigation
don't use UrlFetchTransport in App Engine Flex environment #1492
Description
The decision of whether to use UrlFetchTransport instead of NetHttpTransport is currently based on the presence of the com.google.appengine.application.id system property. This can result in UrlFetchTranport being used in the App Engine Flex environment (at least in compat mode).
One possible approach is:
if (System.getProperty("com.google.appengine.application.id") != null
// Rule out App Engine Flex compat mode.
&& System.getenv("GAE_VM") == null
// Rule out App Engine Flex.
&& System.getenv("GCLOUD_PROJECT" ) == null) {
// use UrlFetchTransport
}
Activity
eddavisson commentedon Dec 21, 2016
Note that a customer seems to be hitting this issue in http://stackoverflow.com/questions/40830727/why-does-datastore-produce-timeout-while-fetching-url.
1 remaining item
Don't use `UrlFetchTransport` in App Engine Flex environment (#1893)
vam-google commentedon Apr 11, 2017
Should be fixed by #1893 and will be released with next release (the one after 0.12.0). Please reopen if you keep experiencing the issue after the fix.
Rebase master (#1900)
Don't use `UrlFetchTransport` in App Engine Flex environment (#1893)
Don't use `UrlFetchTransport` in App Engine Flex environment (#1893)
deps: update dependency com.google.cloud:sdk-platform-java-config to …
chore(main): release 2.20.2 (#1503)
deps: update dependency com.google.cloud:google-cloud-shared-dependen…
chore(main): release 2.15.4 (googleapis#1490)
chore(deps): update dependency com.google.cloud:libraries-bom to v26.…
chore(deps): update dependency com.google.cloud:libraries-bom to v26.…
chore: Fix the cloud bigtable link in readme (googleapis#1492)