mail archive Server-Initiated HTTP
hybi.ietf.org
(List home) (Recent threads) (175 other Internet Engineering Task Force (IETF) lists)
Subscription Options
- RSS or Atom: Read-only subscription using a browser or aggregator. This is the recommended way if you don't need to send messages to the list. You can learn more about feed syndication and clients here.
- Conventional: All messages are delivered to your mail address, and you can reply. To subscribe, send an email to the list's subscribe address with "subscribe" in the subject line, or visit the list's homepage here.
- Low traffic list: less than 3 messages per day
- This list contains about 8,806 messages, beginning Oct 2009
- 0 messages added yesterday
Server-Initiated HTTP
Recent threads
Multiplexing extension spec draft 02 (10 Replies)
Takeshi Yoshino — 132856260106 Feb 2012*
http://tools.ietf.org/html/draft-tamplin-hybi... Diff http://tools.ietf.org/rfcdiff?url2=draft-tamp... No semantic change. - some typo fixes - named ...
Per-frame compression extension proposal (2 Replies)
Takeshi Yoshino — 132816420702 Feb 2012*
Hi, Creating a new thread to get attention. I've been working on per-frame compression extension spec based on Patrick's original one<http:...
New charter for HyBi wg (7 Replies)
Salvatore Loreto — 132737793724 Jan 2012*
Hi there, as you know the WebSocket Protocol has been published on December 2011 as RFC 6455. Thanks again to all of you for all your technical and ed...
rfc6455 The websocket protocol (2 Replies)
Greg Wilkins — 132433493519 Dec 2011*
I see rfc6455 is now available!!! Congratulations all! However, one minor nit to pick... 6455 defines the new error code 1011, which is sent over the ...
Nagle status (1 Reply)
David Galeano — 132404916916 Dec 2011*
Hi, What is the status of Nagle on the different browsers? I read a comment from Ian Fette about Chrome disabling it, what about the others? Regards....
Dario Crivelli — 132387427314 Dec 2011
Hi, May anyone provide me with a clarification on the WebSocket protocol? I would like to leverage the "subprotocol" feature to let a client...
Autobahn feedback (2 Replies)
Piotr Kulaga — 132378014713 Dec 2011*
Hi Tobias, I went through the Autobahn client tests and I have some feedback regarding some of them: * 2.10: The test requires to reply to every ping ...
Peter Thorson — 132372503512 Dec 2011*
This issue came up while polishing up the error handling code for my WS implementation. There doesn't seem to be a websocket close code equivalent...
RFC 6455 on The WebSocket Protocol (5 Replies)
rfc-editor — 132367677112 Dec 2011*
A new Request for Comments is now available in online RFC libraries. RFC 6455 Title: The WebSocket Protocol Author: I. Fette, A. Melnikov Status: Stan...
Testsuite update case 7.1.5 (16 Replies)
Arman Djusupov — 132066518307 Nov 2011*
Hello list, hello Tobias, I would like to discuss Autobahn's 7.1.5 test case: Case Description = Send message fragment1 followed by close then fra...
Iñaki Baz Castillo — 132050098905 Nov 2011*
Hi, I'm implementing SIP over WebSocket as I defined in: http://tools.ietf.org/html/draft-ibc-rtcweb-s... Initially I mandated WS frames of type U...
How are Cookies added? (7 Replies)
Iñaki Baz Castillo — 132050071405 Nov 2011*
Hi, WebSocket API says: - Establish a WebSocket connection given the set (host, port, resource name, secure), along with the protocols list, an empty ...
Marc Petit-Huguenin — 132017920601 Nov 2011
Is there anyone currently developing a Wireshark dissector for Websocket? Please CC me on the response. Thanks....
Testsuite update (15 Replies)
Tobias Oberstein — 132008885131 Oct 2011*
New release 0.4.3 of Autobahn WebSockets including updates to test suite: + supports Hybi-17 + detailed tracking of close behavior + initial set of 30...
opening headers: multiplicity / port in host (3 Replies)
Tobias Oberstein — 132006835131 Oct 2011*
Polishing up our WS handshake code, I have 3 short questions regarding headers: 1) The spec is explicit about the allowed header multiplicity in openi...
first draft of WS mux extension (27 Replies)
John Tamplin — 131976186728 Oct 2011*
I have modified the original mux proposal (apologies to those of you who didn't see it) based on feedback from early reviewers and implementation ...
failed TLS handshake: which close code? (18 Replies)
Tobias Oberstein — 131949962424 Oct 2011*
Hybi-17: """ 4. Opening Handshake ... 4.1. Client Requirements ... 5. If /secure/ is true, the client MUST perform a TLS handshake over...
WS URLs (1 Reply)
Tobias Oberstein — 131932063022 Oct 2011*
2 short questions .. first one is part of http://bugs.python.org/issue13244 Which of the following URLs are valid WS URLs? 1. ws://example.com/somethi...
Takeshi Yoshino — 131913067720 Oct 2011*
Hi, The last paragraph of draft 17<http://tools.ietf.org/html/draft-ietf-hybi-th...> 11.3.2. says use of multiple Sec-WebSocket-Extensions is al...
Jason Duell — 131897743118 Oct 2011*
Implementation detail: Am I reading the spec correctly when I say that it implies that at most one "error" event should be dispatched per we...