Open joshforbes opened 1 year ago
Hi @joshforbes, thanks for raising the issue! I have some questions before this issue is resolved
ably-go
or do previous versions also have the same issue?We're considering replacing the HTTP client in the Ably client to disable HTTP/2.
I appreciate that the Ably client allowed us to so easily replace the HTTP client. We decided to move forward with swapping to an HTTP/1.1 client. I think we'll probably stick with that unless you have some ideas about how to fix the HTTP/2 errors.
Sure, if HTTP/2 is causing errors, you can keep HTTP/1.1 as a default client. We will need to see HTTP2 support for ably-go
Related issue -> https://github.com/olivere/elastic/issues/1443
➤ Automation for Jira commented:
The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-4120
We need to add retry
mechanism to fallback endpoint when this error occurs. More details for the issue given here
https://github.com/connectrpc/connect-go/issues/672
Need to modify canFallback
method to check same error in the response, if it's GOAWAY
then return true
https://github.com/ably/ably-go/blob/dd8236fc301eb078803e83efee7615f3ba133341/ably/rest_client.go#L801-L806
We're getting this error:
Which is stopping the client and leaving our agent in an offline state. The token endpoint is nothing special running behind an nginx server. Not sure if there is something we should change or if something is going on with the client. Any tips appreciated.
Thanks!
┆Issue is synchronized with this Jira Task by Unito