From 82da4816c4bf29a2ddbcc564cb488b743735939f Mon Sep 17 00:00:00 2001
From: sta <sta.blockhead@gmail.com>
Date: Thu, 30 Jul 2015 17:18:04 +0900
Subject: [PATCH] Added 'Ignoring Sec-WebSocket-Extensions header'

---
 README.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/README.md b/README.md
index 21f571c7..196bdcf2 100644
--- a/README.md
+++ b/README.md
@@ -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.
 
+#### 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 ###
 
 websocket-sharp supports the **Secure Connection** with **SSL/TLS**.