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
Websocket transport is selected based on wss:// vs. https:// scheme in the RelayUrl
This means clients would advertise whether they want to use websockets or not in their tickets, even though clients should decide that for themselves only!
We achieve better compatibility if we announce a single URL
It's weird to have the wss:// prefix, given there's also other endpoints like https://relay.example.org/generate_204
I think the fix is:
Make wss or https selection based on a client-side flag (probably in the ClientBuilder)
Always advertise http(s) relay urls.
The text was updated successfully, but these errors were encountered:
…instead of defined by the relay url scheme (#2446)
## Description
Details in #2442
## Breaking Changes
- `iroh_net::relay::http::ClientBuilder`: Added `.protocol()` function
to the builder for choosing whether to connect to the relay via
websockets or not
## Change checklist
- [X] Self-review.
- [X] Documentation updates if relevant.
- [X] Tests if relevant.
- [X] All breaking changes documented.
@flub correctly pointed out on discord:
wss://
vs.https://
scheme in theRelayUrl
wss://
prefix, given there's also other endpoints likehttps://relay.example.org/generate_204
I think the fix is:
ClientBuilder
)The text was updated successfully, but these errors were encountered: