[hybi] #4: handshake does not work properly with HTTP reverse proxy.

["hybi issue tracker" <[e-mail]>]

#4: handshake does not work properly with HTTP reverse proxy.
-------------------------------------------+--------------------------------
 Reporter:  salvatore.loreto@…             |       Owner:     
     Type:  defect                         |      Status:  new
 Priority:  critical                       |   Milestone:     
Component:  thewebsocketprotocol           |     Version:     
 Severity:  Active WG Document             |    Keywords:     
-------------------------------------------+--------------------------------
 the  handshake in draft-ietf-hybi-thewebsocketprotocol-00 (as in draft 76)
 does not work properly in presence of HTTP reverse proxy.

 The 8-bytes nonce from the client is not advertised as a content-length,
 so it is not forwarded by the reverse proxy as it is either part of a next
 request or pending data for when the handshake completes. Unfortunately,
 the server wants those bytes to complete the handshake, so we have a dirty
 deadlock not even detectable by the end user.

 for more information:
 http://www.ietf.org/mail-archive/web/hybi/current/msg02149.html

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/hybi/trac/ticket/4>
hybi <http://tools.ietf.org/hybi/>
The Hypertext-Bidirectional (HyBi) working group will seek
standardization of one approach to maintain bidirectional
communications between the HTTP client, server and intermediate
entities, which will provide more efficiency compared to the current
use of hanging requests.