Add Options::additional_headers and subprotocols

[Its-Just-Nans]

Hello,

In the native app, the Websocket protocol can lead to error because it doesn't act like the web interface.

When we are using the WebSocket API (in the browser), it add automatically some headers - like the Origin header.

In fact this header is mandatory, as explained in the RFC :

• https://datatracker.ietf.org/doc/html/rfc6455

8.   The request MUST include a header field with the name |Origin|
        [[RFC6454](https://datatracker.ietf.org/doc/html/rfc6454)] if the request is coming from a browser client.  If
        the connection is from a non-browser client, the request MAY
        include this header field if the semantics of that client match
        the use-case described here for browser clients.  The value of
        this header field is the ASCII serialization of origin of the
        context in which the code establishing the connection is
        running.  See [[RFC6454](https://datatracker.ietf.org/doc/html/rfc6454)] for the details of how this header field
        value is constructed.

However, if we don't set the Origin header in the native app, the app "could" not act the same as in the browser

In this PR, I had the Origin header to the client.

Note that

• the PR to add a header in tungstenite is quite new : Add builder for additional header values snapview/tungstenite-rs#400
• a new version of tungstenite has not been released yet (so this PR is kind of a draft)

Thanks

[emilk]

this needs to be set to the version number of the first tungstenite release with the with_header function

[Its-Just-Nans]

Yes you're right !
I'm waiting for the new version. I'm tagging the PR as DRAFT to wait for it

[Its-Just-Nans]

When tungstenite 0.22.0 will be out, this PR should fix

• custom header addition
• Add protocols option #31
• Update eframe, add trunk setup #11
• some TODOs

Now waiting for the version bump

[Its-Just-Nans]

Hi

tungstenite is now at 0.22

Note that when the 0.23 will be out, it could be more convenient to use it (see snapview/tungstenite-rs#427)

[Its-Just-Nans]

There migth be a problem with tokio-tungstenite right now snapview/tokio-tungstenite#334

(that's breaking my local CI/CD on my repo https://github.com/Its-Just-Nans/ewebsock/actions/runs/9337202702)

[Its-Just-Nans]

tungstenite and tokio-tungstenite are now at 0.23 !

I think this is mergeable now (local CI/CD pass: https://github.com/Its-Just-Nans/ewebsock/actions/runs/9338012481)

[Its-Just-Nans]

Fixed the typo @emilk

not sure if I can fix the label https://github.com/rerun-io/ewebsock/actions/runs/9338753874/job/25722267954

[emilk]

Thanks for the PR, but this PR now does three very different things:

A) replaces shell scripts with trunk
B) updates to tungstenite to 0.23
C) add default headers to the options

I would be thankful if you could break it into three PRs because

• it would be a lot easier to review
• it would be easier to revert one thing if we regret it
• it would be easier to git-bisect bugs in the future

[Its-Just-Nans]

okay, here my next steps:

• fix the current pr according to review
• create 3 PRs

[Its-Just-Nans]

@emilk I've done the PR for

• A) replaces shell scripts with trunk
• B) updates to tungstenite to 0.23

I'm waiting for B) to be merge to edit this PR to make C)

• C) add default headers to the options

[emilk]

Please revert all changes to Cargo.lock