Add information about cookie storage details

[o-alexandre-felipe]

using System.Net.WebSockets;
using System.Net.Http;

What is the default ClientWebsocket.Options.Cookies?

At which level is the default storage shared?

• per instance?
• per application?
• per domain?
• global?

What is the persistence?

• until connection is destructed?
• until applicaiton is closed?
• until OS is shutdown?
• other?

Also, how are cookies handled when using HttpClient? It is stated that cookie storage can be controlled by HttpClientHandler.UseCookies, again is not clear (to me, at the moment) what is the scope of those cookies?

[ManickaP]

@CarnaViire

[ManickaP]

For HttpClient, it's per the instance of the client.

[CarnaViire]

What is the default ClientWebsocket.Options.Cookies?

null

At which level is the default storage shared?

The default storage is not shared, because there's no storage by default. If you do specify ClientWebSocket.Options.Cookies, then they would be used only for this specific WebSocket handshake request. Technically, you can say it's "per instance".

However, there's an option to pass in a custom HttpClient (HttpMessageInvoker) to the ClientWebSocket.ConnectAsync(Uri, HttpMessageInvoker, CancellationToken) overload. This overload is not compatible with any HttpClient-related properties in ClientWebsocket.Options, as it is expected for the user to set them up directly on the to-be-passed HttpClient (and/or on the HttpMessageHandler instance used to create HttpClient).

This would include a CookieContainer, that, as @ManickaP mentioned, is per HttpClient (to be more precise, per HttpClientHandler or SocketsHttpHandler) instance, so if you reuse the HttpClient for multiple ClientWebSockets, you will end up reusing the CookieContainer as well.

[ManickaP]

Hope your question got answered. I'll close this.