-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR : exposing Retry-After header #386
Comments
SDK automatically does that so no additional handling is necessary. But if you really wish to access the headers, the v4 SDK provides the necessary APIs: https://pkg.go.dev/firebase.google.com/go/v4/errorutils?tab=doc#HTTPResponse |
Thanks!
How long is long here. I am asking cause a while ago we encountered a case where gcm/fcm was down for an hour or more. And our queues were stacked up with thousands of messages. Will SDK handle that case aswell ? |
SDK retires are intended to help recover from transient network and backend errors that are short-lived (in the order of seconds). Therefore the SDK does not retry if the backend server sends an error with firebase-admin-go/internal/http_client.go Lines 69 to 89 in cef91ac
|
As per the documentation, seems like we have to honor the retry after header. But the golang sdk doesn't seem to be exposing it.
The text was updated successfully, but these errors were encountered: