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

Fix a few

Browse Source
This commit is contained in:
sta 2014-01-18 17:31:00 +09:00
parent 3c8c314026
commit 19046978cc
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -416,7 +416,7 @@ wssv.Certificate = new X509Certificate2 ("/path/to/cert.pfx", "password for cert
### HTTP Authentication ### ### 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. 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. 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. 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.