Accessible useragent name for client?

[CornCakePie]

Could you make the user agent property accessible so we can change it at wish for what the client will send as user agent?

using (var ws = new WebSocket ("wss://example.com"))
{
    ws.UserAgent = "something I can define easily with this accessible property";
}

[sta]

For what do you change the value of User-Agent header?

[CornCakePie]

Some sockets and sites do not accept unknown user-agents for several purposes

[ChangePlaces]

:+1: This is a huge issue. Especially when wanting to monitor websockets and look as inconspicious as possible. It leaves a genuine trail you may not want to.

[KoalaBear84]

I would also like this function! Now it's impossible to pretend the request is done by a browser, which is needed sometimes.

[KoalaBear84]

It's too bad to make your own version and stop using NuGet for this simple change. But if that is needed..

[LordBunny]

This would be great, I need it too

[LordBunny]

@sta

[KatDevsGames]

It's a damn embarrassment that this still isn't implemented. There are endless endpoints that only accept specific user agents.