Stay organized with collectionsSave and categorize content based on your preferences.
Tuesday, March 18, 2014
Google uses a wide range of IP addresses for its different services, and the addresses may change
without notification.Google App Engineis a Platform as a Service offering which hosts a wide variety of 3rd party applications. This
post announces changes in the IP address range and headers used by the Google App EngineURLFetch(outbound HTTP) and outbound sockets APIs.
While we recommend that App Engine IP ranges not be used to filter inbound requests, we are aware
that some services have created filters that rely on specific addresses. Google App Engine will be
changing its IP range beginning this month. Please seethese instructionsto determine App Engine's IP range.
Additionally, the HTTPUser-Agentheader stringthat historically allowed identification of individual App Engine applications should no longer
be relied on to identify the application. With the introduction of outboundsockets for App Engine,
applications may now make HTTP requests without using theURLFetchAPI, and those
requests may set aUser-Agentof their own choosing.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eGoogle App Engine is altering its IP address range, and users who filter inbound requests based on specific addresses should update their filters.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eUser-Agent\u003c/code\u003e header string can no longer be depended upon for identifying individual App Engine applications due to the introduction of outbound sockets.\u003c/p\u003e\n"],["\u003cp\u003eGoogle App Engine's outbound HTTP and sockets APIs will be utilizing a new IP address range and headers.\u003c/p\u003e\n"],["\u003cp\u003eGoogle App Engine hosts many third-party applications and its IP addresses can change, impacting users who rely on filtering by specific addresses.\u003c/p\u003e\n"]]],["Google App Engine is altering its IP address range for `URLFetch` and outbound sockets APIs, with changes beginning this month. Instructions for determining the new IP range are provided. Services relying on specific App Engine IP addresses for filters will need to adjust. Additionally, the `User-Agent` header is no longer a reliable identifier for App Engine applications, as the introduction of outbound sockets permits applications to customize it or send request without using `URLFetch` API.\n"],null,["# App Engine IP Range Change Notice\n\nTuesday, March 18, 2014\n\n\nGoogle uses a wide range of IP addresses for its different services, and the addresses may change\nwithout notification.\n[Google App Engine](https://cloud.google.com/products/app-engine/)\nis a Platform as a Service offering which hosts a wide variety of 3rd party applications. This\npost announces changes in the IP address range and headers used by the Google App Engine\n`URLFetch` (outbound HTTP) and outbound sockets APIs.\n\n\nWhile we recommend that App Engine IP ranges not be used to filter inbound requests, we are aware\nthat some services have created filters that rely on specific addresses. Google App Engine will be\nchanging its IP range beginning this month. Please see\n[these instructions](/appengine/kb/general#static-ip)\nto determine App Engine's IP range.\n\n\nAdditionally, the HTTP\n[`User-Agent` header string](/appengine/docs/python/urlfetch#Python_Request_headers)\nthat historically allowed identification of individual App Engine applications should no longer\nbe relied on to identify the application. With the introduction of outbound\n[sockets for App Engine](/appengine/docs/java/sockets),\napplications may now make HTTP requests without using the `URLFetch` API, and those\nrequests may set a `User-Agent` of their own choosing.\n\nPosted by the Google App Engine Team"]]
