Re: [hybi] CONNECT handshake text

[Joe Mason <[e-mail]>]

> -----Original Message-----
> From: Maciej Stachowiak [mailto:[e-mail]]
> Sent: Wednesday, December 08, 2010 5:41 PM
> To: Pat McManus @Mozilla
> Cc: Joe Mason; [e-mail]; [e-mail]
> Subject: Re: [hybi] CONNECT handshake text
> 
> 
> On Dec 8, 2010, at 12:47 PM, Pat McManus @Mozilla wrote:
> 
> > On Wed, 2010-12-08 at 15:42 -0500, Joe Mason wrote:
> >
> >> How about spelling that out specifically in the draft?  "The
> handshake
> >> must send the following bytes, which form a valid HTTP request as
> >> specified by [RFC2616]"
> >
> > you can restrict what bytes the client can send, but you cannot say
> that
> > it is exactly what the WS server will receive. While this is still
> HTTP,
> > an HTTP intermediary can rearrange those bytes in any way that is
> HTTP
> > compliant (and realistically, many that are not - but are normal
> > expected uses of HTTP on today's Internet.).
> 
> The section we were discussing is the description of what the client
> must send. It doesn't talk at all about what the server should expect
> or how the server should process what it receives.

However, we do need to note in the server section that the handshake message may be transformed by intermediaries, so the server MUST (not SHOULD) be more lenient.

Joe

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.