DevWiki/websocket-sharp
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added 'Ignoring Sec-WebSocket-Extensions header'

Browse Source
This commit is contained in:
sta 2015-07-30 17:18:04 +09:00
parent 0539311d87
commit 82da4816c4
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -434,6 +434,23 @@ And then your client will send the following header with the connection request
If the server accepts this extension, it will return the same header which has the corresponding value. And when your client receives it, this extension will be available. If the server accepts this extension, it will return the same header which has the corresponding value. And when your client receives it, this extension will be available.
#### Ignoring Sec-WebSocket-Extensions header ####
As a WebSocket server, if you would like to ignore the extensions requested from a client, you should set the `WebSocketBehavior.IgnoreExtensions` property to `true` in your `WebSocketBehavior` constructor or initializing it, such as the following.
```csharp
wssv.AddWebSocketService<Chat> (
"/Chat",
() => new Chat () {
// To ignore the Sec-WebSocket-Extensions header.
IgnoreExtensions = true
});
```
If it's set to `true`, the server doesn't return the Sec-WebSocket-Extensions header in the connection response.
I think that it's useful when you get something error in connecting the server and exclude the extensions as a cause of the error.
### Secure Connection ### ### Secure Connection ###
websocket-sharp supports the **Secure Connection** with **SSL/TLS**. websocket-sharp supports the **Secure Connection** with **SSL/TLS**.