This is the WebSocket Protocol which is defined here: http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-76#section-1.2
Chrome sends the request exactly as defined in in this document, there is nothing I can do to change the handshake request from the client side. wiwo On Sunday 31 October 2010 22:21:36 you wrote: > On Sun, Oct 31, 2010 at 7:36 PM, <[email protected]> wrote: > > I tried this as well, but ns_conn contentlength returns 0. > > Your client sent > > > GET /demo HTTP/1.1 > > Host: example.com > > Connection: Upgrade > > Sec-WebSocket-Key2: 12998 5 Y3 1 .P00 > > Sec-WebSocket-Protocol: sample > > Upgrade: WebSocket > > Sec-WebSocket-Key1: 4 @1 46546xW%0l 1 5 > > Origin: http://example.com > > > > ^n:ds[4U > > But I guess you should be doing a POST instead of a GET. > > > On Sunday 31 October 2010 19:24:18 you wrote: > >> How about this: > >> > >> set chan [ns_conn contentchannel] > >> fconfigure $chan -translation binary > >> puts -nonewline [read $chan [ns_conn contentlength]] > > > > -- > > AOLserver - http://www.aolserver.com/ > > > > To Remove yourself from this list, simply send an email to > > <[email protected]> with the body of "SIGNOFF AOLSERVER" in the > > email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[email protected]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
