This repository has been archived by the owner on Nov 20, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 193
WebSockets does not have support for extensions #711
Comments
Depends on upstream support in Depends on issue dotnet/corefx#11874. |
Did you have any specific extensions you want to use? |
No, this exposes to the server the extension(s) that the client requests. Then any extension has to be implemented by the client and the server on top of this which only exposes the requested extension. |
Note this hasn't been done yet because there has been little interest expressed for any websocket extensions. We're unlikely to add the the property if we don't think it will actually get used. |
muratg
changed the title
WebSocket does not have support for extensions
WebSockets does not have support for extensions
Sep 23, 2016
This issue was moved to dotnet/aspnetcore#2715 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
WebSocket
class does not have support for extensions. Which is part of the rfc6455 standard:https://tools.ietf.org/html/rfc6455#section-9
It should read the
Sec-WebSocket-Extensions
HTTP header from the client.The
WebSocket
class does not expose aExtensions
property.The text was updated successfully, but these errors were encountered: