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
For example, change the test test__091__Connection__Host_Fallback__every_connection_is_first_attempted_to_the_primary_host_realtime_ably_io so that it uses the sandbox environment (i.e. write options.environment = "sandbox"). You will see that the client does not attempt to connect to any fallback hosts. I think that, per RTN17c and RSC15g2, it should do.
Fallback hosts do seem to be working correctly for custom environments for REST connections; see the tests for RSC15g2.
(Note that I'm referring to the pre-1ef8d1a version of the spec, which deprecated the spec points I'm referring to and introduced the endpoint client option, which we haven't implemented yet.)
I considered switching the test to instead use sandbox, but discovered
that fallback hosts for realtime connections with custom environments
are not working; see #2009.
Resolves#2008.
For example, change the test
test__091__Connection__Host_Fallback__every_connection_is_first_attempted_to_the_primary_host_realtime_ably_io
so that it uses the sandbox environment (i.e. writeoptions.environment = "sandbox"
). You will see that the client does not attempt to connect to any fallback hosts. I think that, per RTN17c and RSC15g2, it should do.Fallback hosts do seem to be working correctly for custom environments for REST connections; see the tests for RSC15g2.
(Note that I'm referring to the pre-
1ef8d1a
version of the spec, which deprecated the spec points I'm referring to and introduced theendpoint
client option, which we haven't implemented yet.)┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: