Relevant spec:
(RSC7d2) Where possible, the Agent library identifier should be included in all HTTP and WebSocket requests to the Ably endpoint via an Ably-Agent HTTP header.
(RSC7d3) Where the library is unable to specify a header when making a request (such as for JSONP requests), the Agent library identifier should be sent via an agent query param whose value is the URI-encoded Agent library identifier.
AFAICT - this library puts Ably-Agent into the query params when making a websocket connection, which isn't compliant. It either needs to be agent in the query params or Ably-Agent as an HTTP header.
┆Issue is synchronized with this Jira Task by Unito
Relevant spec:
AFAICT - this library puts
Ably-Agentinto the query params when making a websocket connection, which isn't compliant. It either needs to beagentin the query params orAbly-Agentas an HTTP header.┆Issue is synchronized with this Jira Task by Unito