From 19046978cc7eacd11bfe940a0bef62abdd300b7a Mon Sep 17 00:00:00 2001 From: sta Date: Sat, 18 Jan 2014 17:31:00 +0900 Subject: [PATCH] Fix a few --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ac3d085d..c4f6380f 100644 --- a/README.md +++ b/README.md @@ -416,7 +416,7 @@ wssv.Certificate = new X509Certificate2 ("/path/to/cert.pfx", "password for cert ### HTTP Authentication ### -**websocket-sharp** supports the HTTP Authentication (Basic/Digest). +websocket-sharp supports the **HTTP Authentication (Basic/Digest)**. As a **WebSocket Client**, you should set a pair of user name and password for the HTTP Authentication, using the `WebSocket.SetCredentials (username, password, preAuth)` method. @@ -426,7 +426,7 @@ ws.SetCredentials ("nobita", "password", true); If `preAuth` is `true`, the `WebSocket` sends the Basic authentication credentials in the first connection request. -And if `preAuth` is `false`, the `WebSocket` sends the Basic or Digest authentication credentials depend on the unauthorized response, in the second connection request. +And if `preAuth` is `false`, the `WebSocket` sends the Basic or Digest authentication credentials depend on the unauthorized response to the first connection request, in the second connection request. As a **WebSocket Server**, you should set an HTTP authentication scheme, a realm, and any function to find the user credentials. It's like the following.