I've seen 302 errors come from API calls to GAE apps where I accessed the origin page with http://, and sent the API call relative to the page (thus also using http://), but the API endpoint requires https://. Could this be related?
- Kris
PS. I've been pondering whether this is a bug, since 302 implies that the caller should continue to use the original URL, and in my case the https protection is permanent. I might have expected 403 or 404 instead.
On Thursday, July 26, 2012 7:39:16 AM UTC-7, John Kelvie wrote:
We are getting, on occasion, 302 errors in communicating from a backend to another app via the remote API. Once the errors start, they occur continuously until we stop and start the backend. Has anyone else encountered this? Is there a way to resolve it that does not involve restarting the backend instance?
-John