You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey,
I saw recently that the library return an error with 302,meaning 'Found' and this is a common way of performing URL redirection.
Is this library support such response from gcm?
Thanks, guy
The text was updated successfully, but these errors were encountered:
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests.
[...]
If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
We send POST requests, so I am assuming that we shouldn't use the alternate URL (given in the Location header).
I have not experienced this issue, but I would be very interested in details on how to handle it.
I don't see any documentation on how to handle it. I assume we could just re-run the request to the provided (temporary, alternate) URL, but I would like confirmation of this.
Hey,
I saw recently that the library return an error with 302,meaning 'Found' and this is a common way of performing URL redirection.
Is this library support such response from gcm?
Thanks, guy
The text was updated successfully, but these errors were encountered: