sta

Hello, there. Well, Your 'pull request' is similar to the issue #15. I think it's possible to do too many and it's not safe. So, I ask you, Which HTTP...

websocket-sharp supports the HTTP Basic/Digest auth as a client. ``` cs ws.SetCredentials ("name", "password", true); // 'true' if Basic auth ``` Is your "Authorization" header used for neither Basic or...

I've understood your situation at your app. (I think it's more usual to use Cookie... Well, There is unique situation at your app?) But, I don't plan to merge your...

@maqdev Huh? What do you mean? Necessary means necessary for the WebSocket protocol defined in RFC 6455. I've never said to support Every HTTP header.

First of all, i don't plan to support user defined custom header. > what do you suggest for those who need custom headers? to not use your library? I suggest...

Hmm,,, It's an exaggerated story. > every possible WS server that requires custom headers from its clients is bad-designed That's just user defined custom matter, and it's not related to...

> WS spec claims that "custom headers are ALLOWED" Huh? Which section of RFC 6455 is it described in?

@thomaslevesque My position is very clear. I follow [RFC 6455](http://tools.ietf.org/html/rfc6455). And **RFC 6455** describes like the following in [4.1. Client Requirements](http://tools.ietf.org/html/rfc6455#section-4.1): > The request MAY include any other header fields,...

I think: > The request may include any other header fields, ..., WHICH ARE PROCESSED ACCORDING TO DOCUMENTS THAT DEFINE THEM. And @dallonf wrote: > ..., especially because the WebSocket...

> Nothing says these documents have to be public RFCs. They can be internal design documents that describe the application's API. How does many people see such INTERNAL design documents?...