The change to GAE urlfetch in Apr 2015

Skip to first unread message

Anthony Kong

Mar 26, 2015, 11:02:08 PM3/26/15

I don't know if simpleauth users received this email sent out by the Google Cloud Team about a change to urlfetch behahviour. I will reproduce the content here for your reference:

Dear URL Fetch users,
We’re contacting you because you’re listed as the administrator for your organization’s App Engine application, which uses the URL Fetch service. During the phased rollout of an update to this service, we determined that your application may be affected by the change described below.
Currently, the URL Fetch service preserves your original HTTP method (e.g., GET, POST) when it receives and responds to a 302 Moved Temporarily response. Modern user agents typically issue a GET request in response to a 302. After the update, URL Fetch will only issue a GET request after receiving a 302 response, rather than preserving the original method. This may cause requests to be routed differently and/or return 404s or other errors, and will drop the message body from POST requests.
To avoid being affected by this change, please verify that either:
Your app sends non-GET requests (such as POST) directly to the final URL that will handle the request rather than to one that redirects. Some common services, including App Engine, use 302 to redirect HTTP connections to HTTPS and vice versa, so it’s important to check that your protocol is correct as well. You can use the final_url field of the Response object (or a similar object in other APIs) to determine if your fetches are being redirected.
The destination server sends a 303 or 307 HTTP code, each of which specifies the redirect behavior with respect to HTTP methods, rather than a 302.
We will apply the update to your affected application’s URL Fetch usage on April 25, 2015.
If you have any questions, please contact our support team - even if you do not have a support contract.
Google Cloud Platform team 

 Apparently urlfetch is used by the simpleauth library. I wonder if the change outlined in the email will have any impact on oauth.

Thanks, Tony
Reply all
Reply to author
0 new messages