sachin shinde

Hi @joshforbes, thanks for raising the issue! I have some questions before this issue is resolved 1. ably-go version 2. go version 3. Which type of auth mechanism are you...

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

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...

Expression to calculate upper and lower bounds for generated values using `getRetryTime` ``` upper = min((retryCount + 2) / 3, 2) *initialTimeout lower = 0.8 * upper ``` if x...

Reference test file -> https://github.com/ably/ably-dotnet/blob/ab1142594d3a689069f15ef137bfa3ba06891da3/src/IO.Ably.Tests.Shared/Utils/ReconnectionStrategyTest.cs

Reference impl https://github.com/ably/ably-dotnet/pull/1176

Yeah, I think we should close this issue. @marto83 you can check again if the issue is resolved.

Hi @honeyhead, we will look into this. We should be able to support this with some config. changes? Can I ask what is a priority for you to support this...

@honeyhead we will be adding this feature soon! Optional but you can also a raise a ticket on https://ably.com/support adding all necessary details.