
From nobody Thu Jun  5 01:56:39 2014
Return-Path: <yhirano@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61441A01C0 for <hybi@ietfa.amsl.com>; Thu,  5 Jun 2014 01:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.629
X-Spam-Level: 
X-Spam-Status: No, score=-0.629 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRb6dwzm0OP8 for <hybi@ietfa.amsl.com>; Thu,  5 Jun 2014 01:56:33 -0700 (PDT)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29F201A0102 for <hybi@ietf.org>; Thu,  5 Jun 2014 01:56:33 -0700 (PDT)
Received: by mail-yk0-f179.google.com with SMTP id 19so541611ykq.38 for <hybi@ietf.org>; Thu, 05 Jun 2014 01:56:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=8NgJm4TRULLry3oWKxhWzCB51yrmahWYoKq7bIB60ME=; b=fPoVtJqyHl0r5wldzG6zLswYC5soVv9BLIV78dsCHc539TLqn5GBptydgl8oliVKwb /bUJxIDhlpAHCYS/epQYINbgQFHI5M3uZYeJ90vlM/hA8te+d81lDItAUljQpiRQBev5 6gtiln0I86zkv3v6VsKwhtRmS4axvPY9eizSnZfVJX5PRRCKBTojHimGRH+OVmaA45c5 5FZfishVps+vs42DCYgJhud+BkyIwWprGs0XWgMT3FRLMH1ig1xuRBw+wiPJXhWx8wg8 TwwCEwjbi2uB4TR1gpKIQZ4K4kjNrAvRw+hbsQuIYXSoiw8APEn7ddvCGdTirha/LFJa UurQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=8NgJm4TRULLry3oWKxhWzCB51yrmahWYoKq7bIB60ME=; b=aJs0tPkLDl6ctoK+x1PG7pmgavBX8IhN6ZV/cHCjzexDjh3KPwXO/vQNYe8bX6PmaG omXnCIDpWntHb+Ceixbdg+MsxDfm43xuP4VCD+NwW6+bGqPAZafZHXmjAQ2E6qwe4UfX ZJcBzVpRmITzDCgzsEdOGy6HRpAbo1JpiQmqM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8NgJm4TRULLry3oWKxhWzCB51yrmahWYoKq7bIB60ME=; b=PsnXbBSdkjKDcdgVaOxs0lqhxtfeVvbAm8Xi7LNl0+V0CQbOKzLxUnLqixNeNvpu8u q2Fceb97OfntMuG4tmGPLHUn2Ws4pyYxSZ8xFiGP63d4iKXtqYE4V5I/Qwzwn9/KtPt5 HDAXHtC8Ja6H5BNTmF/ab0VLmfbt8XfszQxNVR0Pq54WxOlV0FEADM26yItrP6LGoZEZ 5v/mjzUmTIHlO8W15Vm71/dtRKyz8kzoxSspkKvd1EJtQ7UYUEHguK02EPHG0awP+x3i FxonacVB5I9rSY4d2btoD0zjkhCNhF85ZV+g7ADSDKtT0VgiUzhsYEQQ9OPC7vI/RcGy uuiA==
X-Gm-Message-State: ALoCoQmJrOtaL/+PPRP2ddKFRmzXm/dCga+IpaQwFCMYRyvrjTZfIVIi3vffzZhTCS8QtYYMOZvk
MIME-Version: 1.0
X-Received: by 10.236.113.69 with SMTP id z45mr83245649yhg.0.1401958586374; Thu, 05 Jun 2014 01:56:26 -0700 (PDT)
Sender: yhirano@google.com
Received: by 10.170.78.214 with HTTP; Thu, 5 Jun 2014 01:56:26 -0700 (PDT)
In-Reply-To: <CAG4zZZBcaYJRqZOo1yOP3qovRJTpqFZwauHcCz_+Pb00DoLpFg@mail.gmail.com>
References: <CAG4zZZAkfCgWKSiy6XP3eKggCnDR0upC5tsM6i15ZUUHwvis6g@mail.gmail.com> <634914A010D0B943A035D226786325D444758070B4@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJbkfSMa+-8RZ8ERteT=6qHzvRk0xZbsbHKKOF2kKoxMKQ@mail.gmail.com> <CAG4zZZBcaYJRqZOo1yOP3qovRJTpqFZwauHcCz_+Pb00DoLpFg@mail.gmail.com>
Date: Thu, 5 Jun 2014 17:56:26 +0900
X-Google-Sender-Auth: 4ffPXJlSjsgWRyX_alnvbj93Xps
Message-ID: <CABihn6G-BhHzvBd6gCGoo=EFxa7-z0ii0fOPzU2TcXLb35LBUA@mail.gmail.com>
From: Yutaka Hirano <yhirano@chromium.org>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary=20cf3010eb1187f47504fb12eb9f
Archived-At: http://mailarchive.ietf.org/arch/msg/hybi/IuzFgerPjRl6HbQ-hT9mnhzFV5A
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] status of real world permessage-deflate implementations?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jun 2014 08:56:37 -0000

--20cf3010eb1187f47504fb12eb9f
Content-Type: text/plain; charset=UTF-8

Sorry for the very late response.

I implemented permessage-deflate in Chrome so that it inserts
\x00\x00\xff\xff only at the end of the last frame of each message.
I have tested both the new and the old implementation in Chrome (ToT), but
it accepts your "by-spec-32k" data.
Please feel free to file a bug to http://crbug.com/.

Thanks,



On Fri, May 16, 2014 at 5:03 AM, Joakim Erdfelt <joakim@intalio.com> wrote:

> Some more updates...
>
> This is looking like more and more like a *VERY SPECIFIC* chrome bug.
> Would be happy to migrate this to a chrome specific bug tracker, but I
> just wanted to update the rest of the group first on these results.
>
> My test data:
> http://joakim.erdfelt.com/jetty/websocket-intratail/
>
> These are all from server, not masked, destined for client that is being
> tested.
> Each file is a single, complete, frame.
> Each directory represents a single overall message.
> Every message is the same...
>  UTF8 e-book -> "A Connecticut Yankee in King Arthur's Court, Complete, by
> Mark Twain"
>  From Project Gutenberg: http://www.gutenberg.org/ebooks/86.txt.utf-8
>
> Extension Negotiation:
>
>   There were 2 overall client offer styles seen.
>    a) permessage-deflate; client_max_window_bits, x-webkit-deflate-frame
>    b) permessage-deflate; client_max_window_bits
>
>   Server always negotiated as: permessage-deflate
>
> Once the connection is established, these raw frames are sent to the
> client, as-is, with no extra interpretation by the server.
> Connection is plain, http -> ws:// not https or wss:// or spdy.
>
>   /by-spec-*/        - intra-frame tail is present (per spec)
>   /by-spec-32k/      - fragmented, 20 frames,  32k max frame size
>   /by-spec-128k/     - fragmented,  5 frames, 128k max frame size
>   /by-spec-1-frame/  - not fragmented, 1 frame
>
>   /strip-intratails-*/        - intra-frame tail is removed (in violation
> of spec)
>   /strip-intratails-32k/      - fragmented, 20 frames,  32k max frame size
>   /strip-intratails-128k/     - fragmented,  5 frames, 128k max frame size
>   /strip-intratails-1-frame/  - not fragmented, 1 frame
>
> Tested Clients:
>
>   A) PyWebSocket Trunk (@revision 798) - echo_client.py - Python 2.7.5
>   B) Chrome 34.0.1847.132 - on Fedora 20 - Javascript/HTML
>   C) Chromium 34.0.1847.132-1.fc20 - on Fedora 20 - Javascript/HTML
>   D) Chrome 34.0.1847.131 - on OSX/10.9.2 (older MBP) - Javascript/HTML
>   E) Chrome Canary 37.0.1991.0 - on OSX/10.9.2 (older MBP) -
> Javascript/HTML
>   F) Chrome 34.0.1847.137 - on OSX/10.9.2 (first gen rMBP) -
> Javascript/HTML
>   G) Chrome Canary 37.0.1991.0 - on OSX/10.9.2 (first gen rMBP) -
> Javascript/HTML
>   H) Chrome Canary 37.0.1994.2 - on OSX/10.9.2 (first gen rMBP) -
> Javascript/HTML
>   I) Chrome 34.0.1847.137 m - Windows 7 SP1 (x64) - Javascript/HTML
>   J) Chrome 34.0.1847.131 m - Windows 8.1 (x64) - Javascript/HTML
>
> Results:
>
>   /by-spec-1-frame/          - all clients pass
>   /by-spec-32k/              - B fails, all of the rest are successful.
>   /by-spec-128k/             - all clients pass
>   /strip-intratails-1-frame/ - all clients pass
>   /strip-intratails-32k/     - only B passes, all other clients fail
>   /strip-intratails-128k/    - all clients fail.
>
> When a failure occurs, its always on the second frame sent.
>
> As these results are just mind-boggling, I went ahead and installed a
> fresh copy of fedora 20 in a vm (oracle virtualbox), updated all of the
> packages and tried again with Chrome 34.0.1847.132.  Same results.
> Important note! - When upgrading to stable version 34.0.1847.137-1 then
> chrome behaves properly again.
>
> As for the Fedora 20 main machine, it has a disabled firewall and selinux
> (so those can be ruled out as the cause).
>
>
> --
> Joakim Erdfelt <joakim@intalio.com>
> webtide.com <http://www.webtide.com/> - intalio.com/jetty
> Expert advice, services and support from from the Jetty & CometD experts
> eclipse.org/jetty - cometd.org
>
>
> On Thu, May 15, 2014 at 6:15 AM, Takeshi Yoshino <tyoshino@google.com>
> wrote:
>
>> Hi Joakim, Tobias,
>>
>>
>> On Wed, May 14, 2014 at 9:22 PM, Tobias Oberstein <
>> tobias.oberstein@tavendo.de> wrote:
>>
>>> Hi Joakim,
>>>
>>>
>>>
>>> couple of thoughts ..
>>>
>>>
>>>
>>> 1)
>>>
>>> The latest Autobahn testsuite did include testing of various deflate
>>> parameter sets (section 12)
>>>
>>>
>>>
>>> http://autobahn.ws/testsuite/reports_20140314/clients/index.html
>>>
>>>
>>>
>>> but does NOT yet include testing permessage-deflate combined with
>>> fragmentation and/or multiple deflate blocks.
>>>
>>>
>>>
>>> That is missing. I guess we need it.
>>>
>>>
>>>
>>> 2)
>>>
>>> FWIW, AutobahnPython allows to set auto-fragmentation of outgoing
>>> messages via
>>>
>>>
>>>
>>> WebSocketClientFactory.setProtocolOptions(autoFragmentSize = 1024)
>>>
>>> WebSocketServerFactory.setProtocolOptions(autoFragmentSize = 1024)
>>>
>>>
>>>
>>> However, this works like this: first compress the complete message in
>>> one go and _then_ fragment.
>>>
>>>
>>>
>>> This means, there will only be a _single_ deflate block that is then
>>> splitted between mulitple frames (see (B) below)
>>>
>>>
>>>
>>> 3)
>>>
>>> In other words, there is another dimension: multiple deflate blocks in
>>> one or multiple frames  (see (C) below).
>>>
>>>
>>>
>>> (A)
>>>
>>> [FRAME 1 : DEFLATE BLOCK 1 - without tail bytes]
>>>
>>>
>>>
>>> (B)
>>>
>>> [FRAME 1 : DEFLATE BLOCK 1 (Part 1/2)] [FRAME 2 : DEFLATE BLOCK 1 (Part
>>> 2/2)- without tail bytes]
>>>
>>>
>>>
>>> (C)
>>>
>>> [FRAME 1 : DEFLATE BLOCK 1 with tail bytes] [FRAME 2 : DEFLATE BLOCK 2
>>> without tail bytes]
>>>
>>>
>>>
>>> Regarding the spec:
>>>
>>>
>>>
>>> """
>>>
>>> Note that for non-final fragments, the removal of 0x00 0x00 0xff 0xff must not be done.
>>>
>>> """
>>>
>>>
>>>
>>> I am now wondering which of the following would be valid:
>>>
>>>
>>>
>>> (D)
>>>
>>> [FRAME 1 : DEFLATE BLOCK 1 with tail bytes] [FRAME 2 : empty payload]
>>>
>>
>> This doesn't work since the concatenation of payloads ends with the tail
>> bytes. On the receiver, it adds the tail bytes and decodes and sees an
>> error. FRAME 2 must include 0x00. Please see
>> https://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-18#section-8.2.3.6
>>
>>
>>>
>>>
>>> (E)
>>>
>>> [FRAME 1 : DEFLATE BLOCK 1 (Part 1/2)] [FRAME 2 : DEFLATE BLOCK 1 (Part
>>> 2/2) with tail bytes | DEFLATE BLOCK 2 without tail bytes]
>>>
>>>
>>>
>>
>> This is fine.
>>
>>
>>> (F)
>>>
>>> [FRAME 1 : DEFLATE BLOCK 1 with tail bytes | DEFLATE BLOCK 2 without
>>> tail bytes]
>>>
>>>
>>>
>>
>> This is also fine.
>>
>>
>>> and whether the intention of the spec was more like
>>>
>>>
>>>
>>> """
>>>
>>> The tail bytes of the last (and only the last) deflate block must be
>>> stripped.
>>>
>>> """
>>>
>>
>> Correct.
>>
>>
>>>
>>>
>>> That is: no reference to frames at all, only to deflate blocks (last or
>>> non-last).
>>>
>>
>> Thanks for suggestion. I'll review my texts about this.
>>
>>
>>>
>>>
>>> Anyway: which of (A) - (F) is intended to be valid/invalid?
>>>
>>>
>>>
>>> My current understanding: all but (D) are valid.
>>>
>>
>> Right.
>>
>>
>>>
>>>
>>> /Tobias
>>>
>>>
>>>
>>>
>>>
>>> *Von:* hybi [mailto:hybi-bounces@ietf.org] *Im Auftrag von *Joakim
>>> Erdfelt
>>> *Gesendet:* Mittwoch, 14. Mai 2014 20:12
>>> *An:* hybi@ietf.org
>>> *Betreff:* [hybi] status of real world permessage-deflate
>>> implementations?
>>>
>>>
>>>
>>> So, I've been testing the server and client side implementations of
>>> various permessage-deflate implementations and come to realize that there
>>> is no consistency (yet).
>>>
>>>
>>>
>>> In Chrome 34, its client side decompress (received frames) is different
>>> than pywebsocket client decompress (received frames) which is different
>>> from autobahn testsuite's handling.
>>>
>>>
>>>
>>> Been testing our Jetty side implementation, and for large compressed
>>> messages (been using the Gutenberg project's text of "A Connecticut Yankee
>>> in King Arthur's Court, Complete, by Mark Twain" as my data).
>>>
>>> http://www.gutenberg.org/ebooks/86.txt.utf-8
>>>
>>>
>>>
>>> All tests are done with client upgrading to Jetty side using ..
>>>
>>>
>>>
>>> offer: permessage-deflate; client_max_window_bits, x-webkit-deflate-frame
>>>
>>> negotiated: permessage-deflate
>>>
>>>
>>>
>>> I can make pywebsocket client happy, and it can send/receive single
>>> frame messages or fragmented messages (using either 16k and 32k max frame
>>> sizes) just fine.
>>>
>>> However, Chrome 34 errors out consistently if it receives a large
>>> fragmented message that is compressed.
>>>
>>> The inter-frame handling of the tail bytes (0x00, 0x00, 0xFF, 0xFF)
>>> appears to be different.
>>>
>>> In the last spec document,
>>> http://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-18
>>> its clear that we must include the tail bytes.
>>>
>>> However, Chrome doesn't like that and fails the decompress w/abnormal
>>> closure.
>>>
>>> Inspection says:  failed to inflate a frame
>>>
>>> If I strip the tail bytes for Chrome 34, then its happy and pywebsocket
>>> is now broken.
>>>
>>> autobahn apparently doesn't care, one way or another, it accepts
>>> (happily) both with and without tail bytes between frames.
>>>
>>>
>>>
>>> --
>>>
>>> Joakim Erdfelt <joakim@intalio.com>
>>>
>>> webtide.com <http://www.webtide.com/> - intalio.com/jetty
>>>
>>> Expert advice, services and support from from the Jetty & CometD experts
>>>
>>> eclipse.org/jetty - cometd.org
>>>
>>> _______________________________________________
>>> hybi mailing list
>>> hybi@ietf.org
>>> https://www.ietf.org/mailman/listinfo/hybi
>>>
>>>
>>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

--20cf3010eb1187f47504fb12eb9f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sorry for the very late response.<div><br></div><div>I imp=
lemented permessage-deflate in Chrome so that it inserts \x00\x00\xff\xff o=
nly at the end of the last frame of each message.</div><div>I have tested b=
oth the new and the old implementation in Chrome (ToT), but it accepts your=
 &quot;by-spec-32k&quot; data.</div>
<div>Please feel free to file a bug to <a href=3D"http://crbug.com/">http:/=
/crbug.com/</a>.</div><div><br></div><div>Thanks,</div><div><br></div></div=
><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, May =
16, 2014 at 5:03 AM, Joakim Erdfelt <span dir=3D"ltr">&lt;<a href=3D"mailto=
:joakim@intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Some more updates...</=
div><div><br></div><div>This is looking like more and more like a *VERY SPE=
CIFIC* chrome bug.</div>
<div>Would be happy to migrate this to a chrome specific bug tracker, but I=
 just wanted to update the rest of the group first on these results.</div>
<div><br></div><div>My test data:</div><div><a href=3D"http://joakim.erdfel=
t.com/jetty/websocket-intratail/" target=3D"_blank">http://joakim.erdfelt.c=
om/jetty/websocket-intratail/</a></div><div><br></div><div>These are all fr=
om server, not masked, destined for client that is being tested.</div>

<div>Each file is a single, complete, frame.</div><div>Each directory repre=
sents a single overall message.</div><div>Every message is the same...</div=
><div>=C2=A0UTF8 e-book -&gt; &quot;A Connecticut Yankee in King Arthur&#39=
;s Court, Complete, by Mark Twain&quot;</div>

<div>=C2=A0From Project Gutenberg: <a href=3D"http://www.gutenberg.org/eboo=
ks/86.txt.utf-8" target=3D"_blank">http://www.gutenberg.org/ebooks/86.txt.u=
tf-8</a></div><div><br></div><div>Extension Negotiation:</div><div><br></di=
v><div>
<div><font face=3D"courier new, monospace">=C2=A0 There were 2 overall clie=
nt offer styles seen.</font></div>
<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0a) permessage-defla=
te; client_max_window_bits, x-webkit-deflate-frame</font></div><div><font f=
ace=3D"courier new, monospace">=C2=A0 =C2=A0b) permessage-deflate; client_m=
ax_window_bits</font></div>

<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=C2=A0 Server always negotiated as: permessage-=
deflate</font></div></div><div><br></div><div>Once the connection is establ=
ished, these raw frames are sent to the client, as-is, with no extra interp=
retation by the server.</div>

<div>Connection is plain, http -&gt; ws:// not https or wss:// or spdy.</di=
v><div><br></div><div><font face=3D"courier new, monospace">=C2=A0 /by-spec=
-*/ =C2=A0 =C2=A0 =C2=A0 =C2=A0- intra-frame tail is present (per spec)</fo=
nt></div><div><font face=3D"courier new, monospace">=C2=A0 /by-spec-32k/ =
=C2=A0 =C2=A0 =C2=A0- fragmented, 20 frames, =C2=A032k max frame size</font=
></div>

<div><font face=3D"courier new, monospace">=C2=A0 /by-spec-128k/ =C2=A0 =C2=
=A0 - fragmented, =C2=A05 frames, 128k max frame size</font></div><div><fon=
t face=3D"courier new, monospace">=C2=A0 /by-spec-1-frame/ =C2=A0- not frag=
mented, 1 frame</font></div><div>

<font face=3D"courier new, monospace"><br></font></div><div><font face=3D"c=
ourier new, monospace">=C2=A0 /strip-intratails-*/ =C2=A0 =C2=A0 =C2=A0 =C2=
=A0- intra-frame tail is removed (in violation of spec)</font></div><div><f=
ont face=3D"courier new, monospace">=C2=A0 /strip-intratails-32k/ =C2=A0 =
=C2=A0 =C2=A0- fragmented, 20 frames, =C2=A032k max frame size</font></div>

<div><font face=3D"courier new, monospace">=C2=A0 /strip-intratails-128k/ =
=C2=A0 =C2=A0 - fragmented, =C2=A05 frames, 128k max frame size</font></div=
><div><font face=3D"courier new, monospace">=C2=A0 /strip-intratails-1-fram=
e/ =C2=A0- not fragmented, 1 frame</font></div>

<div><br></div><div>Tested Clients:</div><div><br></div><div>=C2=A0 A) PyWe=
bSocket Trunk (@revision 798) - echo_client.py - Python 2.7.5</div><div>=C2=
=A0 B) Chrome 34.0.1847.132 - on Fedora 20 - Javascript/HTML</div><div>=C2=
=A0 C) Chromium 34.0.1847.132-1.fc20 - on Fedora 20 - Javascript/HTML</div>

<div>=C2=A0 D) Chrome 34.0.1847.131 - on OSX/10.9.2 (older MBP) - Javascrip=
t/HTML</div><div>=C2=A0 E) Chrome Canary 37.0.1991.0 - on OSX/10.9.2 (older=
 MBP) - Javascript/HTML</div><div>=C2=A0 F) Chrome 34.0.1847.137 - on OSX/1=
0.9.2 (first gen rMBP) - Javascript/HTML</div>

<div>=C2=A0 G) Chrome Canary 37.0.1991.0 - on OSX/10.9.2 (first gen rMBP) -=
 Javascript/HTML</div><div>=C2=A0 H) Chrome Canary 37.0.1994.2 - on OSX/10.=
9.2 (first gen rMBP) - Javascript/HTML</div><div>=C2=A0 I) Chrome 34.0.1847=
.137 m - Windows 7 SP1 (x64) - Javascript/HTML</div>

<div>=C2=A0 J) Chrome 34.0.1847.131 m - Windows 8.1 (x64) - Javascript/HTML=
</div><div><br></div><div>Results:</div><div><br></div><div><font face=3D"c=
ourier new, monospace">=C2=A0 /by-spec-1-frame/ =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0- all clients pass</font></div>

<div><font face=3D"courier new, monospace">=C2=A0 /by-spec-32k/ =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0- B fails, all of the rest are succes=
sful.</font></div><div><font face=3D"courier new, monospace">=C2=A0 /by-spe=
c-128k/ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - all clients pass</font>=
</div>

<div><font face=3D"courier new, monospace">=C2=A0 /strip-intratails-1-frame=
/ - all clients pass</font></div><div><font face=3D"courier new, monospace"=
>=C2=A0 /strip-intratails-32k/ =C2=A0 =C2=A0 - only B passes, all other cli=
ents fail</font></div>

<div><font face=3D"courier new, monospace">=C2=A0 /strip-intratails-128k/ =
=C2=A0 =C2=A0- all clients fail.</font></div><div><br></div><div>When a fai=
lure occurs, its always on the second frame sent.</div><div><br></div><div>=
As these results are just mind-boggling, I went ahead and installed a fresh=
 copy of fedora 20 in a vm (oracle virtualbox), updated all of the packages=
 and tried again with Chrome 34.0.1847.132. =C2=A0Same results.</div>

<div>Important note! - When upgrading to stable version 34.0.1847.137-1 the=
n chrome behaves properly again.</div><div><br></div><div>As for the Fedora=
 20 main machine, it has a disabled firewall and selinux (so those can be r=
uled out as the cause).</div>

<div><br></div></div><div class=3D"gmail_extra"><div class=3D""><br clear=
=3D"all"><div><div dir=3D"ltr"><div>--</div><div>Joakim Erdfelt &lt;<a href=
=3D"mailto:joakim@intalio.com" target=3D"_blank">joakim@intalio.com</a>&gt;=
</div><div>
<a href=3D"http://www.webtide.com/" target=3D"_blank">webtide.com</a>=C2=A0=
- <a href=3D"http://intalio.com/jetty" target=3D"_blank">intalio.com/jetty<=
/a></div>
<div><span>Expert advice, services and support from=C2=A0</span><span>from =
the Jetty &amp; CometD experts</span></div><div><a href=3D"http://eclipse.o=
rg/jetty/" target=3D"_blank">eclipse.org/jetty</a>=C2=A0-=C2=A0<a href=3D"h=
ttp://cometd.org/" target=3D"_blank">cometd.org</a></div>

</div></div>
<br><br></div><div><div class=3D"h5"><div class=3D"gmail_quote">On Thu, May=
 15, 2014 at 6:15 AM, Takeshi Yoshino <span dir=3D"ltr">&lt;<a href=3D"mail=
to:tyoshino@google.com" target=3D"_blank">tyoshino@google.com</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Hi Joakim, Tobias,<br><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote"><div><div>On Wed, May 14, 2014 at 9:22 PM, Tobias=
 Oberstein <span dir=3D"ltr">&lt;<a href=3D"mailto:tobias.oberstein@tavendo=
.de" target=3D"_blank">tobias.oberstein@tavendo.de</a>&gt;</span> wrote:<br=
>



<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div lang=3D"DE" link=3D"blue" vlink=3D"purple"><div><p cl=
ass=3D"MsoNormal">



<span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,7=
3,125)">Hi Joakim,<u></u><u></u></span></p><p class=3D"MsoNormal"><span sty=
le=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><=
u></u>=C2=A0<u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">couple of thoughts ..<u></u><u></u></span></=
p><p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,=
sans-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">1)<u></u><u></u></span></p><p class=3D"MsoNo=
rmal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rg=
b(31,73,125)">The latest Autobahn testsuite did include testing of various =
deflate parameter sets (section 12)<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)"><a href=3D"http://autobahn.ws/testsuite/reports_20140314/=
clients/index.html" target=3D"_blank">http://autobahn.ws/testsuite/reports_=
20140314/clients/index.html</a><u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">but does NOT yet include testing permessage-deflate combi=
ned with fragmentation and/or multiple deflate blocks.<u></u><u></u></span>=
</p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">That is missing. I guess we need it.<u></u><u></u></span>=
</p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">2)<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">FWIW, AutobahnPython allows to set auto-frag=
mentation of outgoing messages via<u></u><u></u></span></p><p class=3D"MsoN=
ormal">



<span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,7=
3,125)"><u></u>=C2=A0<u></u></span></p><pre>WebSocketClientFactory.<span>se=
tProtocolOptions(</span><span>autoFragmentSize =3D 1024)</span><u></u><u></=
u></pre>



<pre>WebSocketServerFactory.<span>setProtocolOptions(</span><span>autoFragm=
entSize =3D 1024)</span><u></u><u></u></pre><pre><u></u>=C2=A0<u></u></pre>=
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">However, this works like this: first compres=
s the complete message in one go and _then_ fragment.<u></u><u></u></span><=
/p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">This means, there will only be a _single_ deflate block t=
hat is then splitted between mulitple frames (see (B) below)<u></u><u></u><=
/span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">3)<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">In other words, there is another dimension: =
multiple deflate blocks in one or multiple frames =C2=A0(see (C) below).<u>=
</u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">(A)<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">[FRAME 1 : DEFLATE BLOCK 1 - without tail by=
tes]<u></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-siz=
e:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u=
></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">(B)<u></u><u></u></span></p><p class=3D"MsoN=
ormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:r=
gb(31,73,125)">[FRAME 1 : DEFLATE BLOCK 1 (Part 1/2)] [FRAME 2 : DEFLATE BL=
OCK 1 (Part 2/2)- without tail bytes]<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">(C)<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">[FRAME 1 : DEFLATE BLOCK 1 with tail bytes] =
[FRAME 2 : DEFLATE BLOCK 2 without tail bytes]<u></u><u></u></span></p><p c=
lass=3D"MsoNormal">



<span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,7=
3,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Reg=
arding the spec:<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">&quot;&quot;&quot;<u></u><u></u></span></p>



<pre>Note that for non-final fragments, the removal of 0x00 0x00 0xff 0xff =
must not be done.<u></u><u></u></pre><p class=3D"MsoNormal"><span style=3D"=
font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">&quot;&=
quot;&quot;<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">I am now wondering which of the following would be valid:=
<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">(D)<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">[FRAME 1 : DEFLATE BLOCK 1 with tail bytes] =
[FRAME 2 : empty payload]</span></p></div></div></blockquote><div><br></div=
>



</div></div><div>This doesn&#39;t work since the concatenation of payloads =
ends with the tail bytes. On the receiver, it adds the tail bytes and decod=
es and sees an error. FRAME 2 must include 0x00. Please see=C2=A0<a href=3D=
"https://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-18#sect=
ion-8.2.3.6" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-hybi-=
permessage-compression-18#section-8.2.3.6</a></div>

<div>

<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex"><div lang=3D"DE" link=3D"blue" vlink=3D"p=
urple"><div>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u><u></u></span></p><p class=3D"MsoNorm=
al"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(=
31,73,125)"><u></u>=C2=A0<u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">(E)<u></u><u></u></span></p><p class=3D"MsoN=
ormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:r=
gb(31,73,125)">[FRAME 1 : DEFLATE BLOCK 1 (Part 1/2)] [FRAME 2 : DEFLATE BL=
OCK 1 (Part 2/2) with tail bytes | DEFLATE BLOCK 2 without tail bytes]<u></=
u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0</span></p></div></div></blockq=
uote><div><br></div></div><div>This is fine.</div><div><div>=C2=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padd=
ing-left:1ex">



<div lang=3D"DE" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"=
><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,=
73,125)"><u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:=
11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">(F)<u></u><u></u>=
</span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">[FRAME 1 : DEFLATE BLOCK 1 with tail bytes |=
 DEFLATE BLOCK 2 without tail bytes]<u></u><u></u></span></p><p class=3D"Ms=
oNormal">



<span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,7=
3,125)"><u></u>=C2=A0</span></p></div></div></blockquote><div><br></div></d=
iv><div>This is also fine.</div><div><div>=C2=A0</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border=
-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">



<div lang=3D"DE" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"=
><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,=
73,125)"><u></u></span></p><p class=3D"MsoNormal"><span style=3D"font-size:=
11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">and whether the i=
ntention of the spec was more like<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><p class=3D"M=
soNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;colo=
r:rgb(31,73,125)">&quot;&quot;&quot;<u></u><u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">The tail bytes of the last (and only the las=
t) deflate block must be stripped.<u></u><u></u></span></p><p class=3D"MsoN=
ormal">



<span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,7=
3,125)">&quot;&quot;&quot;</span></p></div></div></blockquote><div><br></di=
v></div><div>Correct.</div><div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left=
-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">



<div lang=3D"DE" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"=
><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,=
73,125)"><u></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"fon=
t-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u>=C2=
=A0<u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">That is: no reference to frames at all, only=
 to deflate blocks (last or non-last).</span></p></div></div></blockquote>


<div>
<br></div></div><div>Thanks for suggestion. I&#39;ll review my texts about =
this.<br></div><div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(2=
04,204,204);border-left-style:solid;padding-left:1ex">



<div lang=3D"DE" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"=
><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,=
73,125)"><u></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"fon=
t-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u>=C2=
=A0<u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Anyway: which of (A) - (F) is intended to be=
 valid/invalid?<u></u><u></u></span></p><p class=3D"MsoNormal"><span style=
=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u>=
</u>=C2=A0<u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">My current understanding: all but (D) are va=
lid.</span></p></div></div></blockquote><div><br></div></div><div>Right.</d=
iv>

<div>

=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-s=
tyle:solid;padding-left:1ex"><div><div><div lang=3D"DE" link=3D"blue" vlink=
=3D"purple">

<div><p class=3D"MsoNormal">

<span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,7=
3,125)"><u></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"font=
-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u>=C2=
=A0<u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">/Tobias<u></u><u></u></span></p><p class=3D"=
MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;col=
or:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>



<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p><div style=3D=
"border-style:none none none solid;border-left-color:blue;border-left-width=
:1.5pt;padding:0cm 0cm 0cm 4pt">



<div><div style=3D"border-style:solid none none;border-top-color:rgb(225,22=
5,225);border-top-width:1pt;padding:3pt 0cm 0cm"><p class=3D"MsoNormal"><b>=
<span style=3D"font-size:11pt;font-family:Calibri,sans-serif">Von:</span></=
b><span style=3D"font-size:11pt;font-family:Calibri,sans-serif"> hybi [mail=
to:<a href=3D"mailto:hybi-bounces@ietf.org" target=3D"_blank">hybi-bounces@=
ietf.org</a>] <b>Im Auftrag von </b>Joakim Erdfelt<br>



<b>Gesendet:</b> Mittwoch, 14. Mai 2014 20:12<br><b>An:</b> <a href=3D"mail=
to:hybi@ietf.org" target=3D"_blank">hybi@ietf.org</a><br><b>Betreff:</b> [h=
ybi] status of real world permessage-deflate implementations?<u></u><u></u>=
</span></p>



</div></div><div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><div><=
div><p class=3D"MsoNormal">So, I&#39;ve been testing the server and client =
side implementations of various permessage-deflate implementations and come=
 to realize that there is no consistency (yet).<u></u><u></u></p>



</div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p cla=
ss=3D"MsoNormal">In Chrome 34, its client side decompress (received frames)=
 is different than pywebsocket client decompress (received frames) which is=
 different from autobahn testsuite&#39;s handling.<u></u><u></u></p>



</div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p cla=
ss=3D"MsoNormal">Been testing our Jetty side implementation, and for large =
compressed messages (been using the Gutenberg project&#39;s text of &quot;A=
 Connecticut Yankee in King Arthur&#39;s Court, Complete, by Mark Twain&quo=
t; as my data).<u></u><u></u></p>



</div><div><p class=3D"MsoNormal"><a href=3D"http://www.gutenberg.org/ebook=
s/86.txt.utf-8" target=3D"_blank">http://www.gutenberg.org/ebooks/86.txt.ut=
f-8</a><u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u>=
</u></p>


</div>
<div><p class=3D"MsoNormal">All tests are done with client upgrading to Jet=
ty side using ..<u></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=
=C2=A0<u></u></p></div><div><p class=3D"MsoNormal">offer:=C2=A0permessage-d=
eflate; client_max_window_bits, x-webkit-deflate-frame<u></u><u></u></p>



</div><div><p class=3D"MsoNormal">negotiated:=C2=A0permessage-deflate<u></u=
><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div=
><div><p class=3D"MsoNormal">I can make pywebsocket client happy, and it ca=
n send/receive single frame messages or fragmented messages (using either 1=
6k and 32k max frame sizes) just fine.<u></u><u></u></p>



</div><div><p class=3D"MsoNormal">However, Chrome 34 errors out consistentl=
y if it receives a large fragmented message that is compressed.<u></u><u></=
u></p></div><div><p class=3D"MsoNormal">The inter-frame handling of the tai=
l bytes (0x00, 0x00, 0xFF, 0xFF) appears to be different.<u></u><u></u></p>



</div><div><p class=3D"MsoNormal">In the last spec document, <a href=3D"htt=
p://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-18" target=
=3D"_blank">http://tools.ietf.org/html/draft-ietf-hybi-permessage-compressi=
on-18</a> its clear that we must include the tail bytes.<u></u><u></u></p>



</div><div><p class=3D"MsoNormal">However, Chrome doesn&#39;t like that and=
 fails the decompress w/abnormal closure.=C2=A0<u></u><u></u></p></div><div=
><p class=3D"MsoNormal">Inspection says: =C2=A0failed to inflate a frame<u>=
</u><u></u></p>



</div><div><p class=3D"MsoNormal">If I strip the tail bytes for Chrome 34, =
then its happy and pywebsocket is now broken.<u></u><u></u></p></div><div><=
p class=3D"MsoNormal">autobahn apparently doesn&#39;t care, one way or anot=
her, it accepts (happily) both with and without tail bytes between frames.<=
u></u><u></u></p>



</div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><div><=
div><p class=3D"MsoNormal">--<u></u><u></u></p></div><div><p class=3D"MsoNo=
rmal">Joakim Erdfelt &lt;<a href=3D"mailto:joakim@intalio.com" target=3D"_b=
lank">joakim@intalio.com</a>&gt;<u></u><u></u></p>



</div><div><p class=3D"MsoNormal"><a href=3D"http://www.webtide.com/" targe=
t=3D"_blank">webtide.com</a>=C2=A0- <a href=3D"http://intalio.com/jetty" ta=
rget=3D"_blank">intalio.com/jetty</a><u></u><u></u></p></div><div><p class=
=3D"MsoNormal">



Expert advice, services and support from=C2=A0from the Jetty &amp; CometD e=
xperts<u></u><u></u></p></div><div><p class=3D"MsoNormal"><a href=3D"http:/=
/eclipse.org/jetty/" target=3D"_blank">eclipse.org/jetty</a>=C2=A0-=C2=A0<a=
 href=3D"http://cometd.org/" target=3D"_blank">cometd.org</a><u></u><u></u>=
</p>



</div></div></div></div></div></div></div></div></div><br></div></div><div>=
_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org" target=3D"_blank">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
<br></div></blockquote></div><br></div></div>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
<br></blockquote></div><br></div>

--20cf3010eb1187f47504fb12eb9f--


From nobody Thu Jun  5 20:50:31 2014
Return-Path: <ricea@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5FF1A0149 for <hybi@ietfa.amsl.com>; Thu,  5 Jun 2014 20:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.429
X-Spam-Level: 
X-Spam-Status: No, score=-1.429 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6utbiQK3NEEj for <hybi@ietfa.amsl.com>; Thu,  5 Jun 2014 20:50:27 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86E3D1A019D for <hybi@ietf.org>; Thu,  5 Jun 2014 20:50:27 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id n16so2176224oag.24 for <hybi@ietf.org>; Thu, 05 Jun 2014 20:50:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/lNbrrtkECOZLPEdScGckyKZNfA1fO14WDtwXoalnvM=; b=QBuA6ppKzHdxZ8R0c0m7A0YUACl5T/CSDQ8Pjl/fDv5cr2vzwpGHl4sevv34Fk3+Q5 a2+zYl0cTie9n4uEjwnzxYWvmnug6maqexmMYju2/JK5ek+HlDh04/4DAbOlKvj9+oiK FIrrpHwvuticHk//wtcAgR0o439/4ufHrOySnXzreGxl+2rrwZ3hMcjjYOzf4TQ71VeR mUdH4Mro3xyxySUehbbdWxwWjbIdYLo2cYbFzgpFQDhMETytFulMsyHr5R/1ofp1qzht RJumOVoTJAaEGB2hGqvZ3/UC3bL6pPUWMG7a3JlY5rKJPhVcPO4T+CSuNNK0JO+8t8yl OBqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=/lNbrrtkECOZLPEdScGckyKZNfA1fO14WDtwXoalnvM=; b=AvMRSI1H6rvIYY3XxZ77TxYtDTdn1f0WGO5lG4DGXGvJ7aPni0r8n04aZSogHvzAN9 yLzs9g3J9e1zS6GTyw7r6Z2Pkqcc7G91WQLhVv/ONxkQbLXB3ft4AP7r4RRj9yi3nMnh wsyuaQJO7Kd0U+pu87jHDQP4IGlQJoie6j3tDod8Lzod4mQYS9sEz9yd0xMIgZSbeu4K TVE9kLo/ZZxEH3mCdZ9AjxTV6rw57NTSTy6gdJpBsbWlGSUPfqX1RrSnba9JMULwBHDQ yFFSJth+86Ic9cfaMzi0bjM8yHYklQaPUEnp8n5hbixFJs3nWwMU/dvrfS3JDevAl28x yFPA==
X-Gm-Message-State: ALoCoQk1mvrBAUNqqPQ6hfHZbZtUsld66d02zCnpmQ3dv/sD7yE2Rb+Lu8oOnGmvqslpY5GkEBSX
MIME-Version: 1.0
X-Received: by 10.182.216.236 with SMTP id ot12mr972385obc.21.1402026620789; Thu, 05 Jun 2014 20:50:20 -0700 (PDT)
Received: by 10.182.193.8 with HTTP; Thu, 5 Jun 2014 20:50:20 -0700 (PDT)
In-Reply-To: <CAPwYjpnd+B7f-Mk3RXTGLZFHXwvpMJPebDtWs_u1T+SXB7WPJA@mail.gmail.com>
References: <CAPwYjp=uVdPLS4dq4xeuRXFN5di6x=ydv=agPPdBO82pMd6pDA@mail.gmail.com> <CAHixhFo3n_yc_kVqOoNOFqrDmrsAMDp4K7HVcztRuxu_4VBYqw@mail.gmail.com> <CAPwYjpnd+B7f-Mk3RXTGLZFHXwvpMJPebDtWs_u1T+SXB7WPJA@mail.gmail.com>
Date: Fri, 6 Jun 2014 12:50:20 +0900
Message-ID: <CAHixhFrVQ2g4cswv8NqdLG0vcN1dUOmPa_XQHnTfX-uZyOa=ZQ@mail.gmail.com>
From: Adam Rice <ricea@google.com>
To: Dario Crivelli <dario.crivelli@lightstreamer.com>
Content-Type: multipart/alternative; boundary=001a1134b2bcb2c0a104fb22c27d
Archived-At: http://mailarchive.ietf.org/arch/msg/hybi/umP3_rWOLKCC7TBRaCxQD8LZU1A
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] New Chrome WebSocket implementation: testers wanted
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jun 2014 03:50:29 -0000

--001a1134b2bcb2c0a104fb22c27d
Content-Type: text/plain; charset=UTF-8

Sorry for the delay in responding. This turned out to be more complicated
than I expected, but the fix landed on Chromium trunk yesterday (
https://codereview.chromium.org/304093003 ). It should be available in a
dev build some time soon.


On 17 April 2014 16:33, Dario Crivelli <dario.crivelli@lightstreamer.com>
wrote:

> Yes, Adam.
> And this is furtherly confirmed by the fact that from the viewpoint of my
> server (which leverages Java's SSLEngine) the handskake completes
> successfully and only when the server waits for a request to come is the
> socket broken.
> Then, for some reason, Chrome seems to recover when it has to do a normal
> https request, whereas it doesn't when it has to do a wss interaction.
> I can try to provide you with more details; please advise if I can keep
> doing that legitimately through this mailing list.
>
> Dario
>
>
>
>
> On Thu, Apr 17, 2014 at 5:41 AM, Adam Rice <ricea@google.com> wrote:
>
>> Dario,
>>
>> Thank you for the feedback. I will check this scenario.
>>
>> I assume you have already instructed the browser to accept the
>> certificate? Otherwise it should fail with either implementation.
>>
>> Thanks,
>> Adam
>>
>>
>>
>> On 16 April 2014 20:09, Dario Crivelli <dario.crivelli@lightstreamer.com>
>> wrote:
>>
>>> Hi Adam,
>>>
>>> We have tried the extended version of Chrome against our Lightstreamer
>>> Server and we have noticed that, with the new implementation enabled, the
>>> browser can't open a WebSocket towards Lightstreamer Server in the
>>> following conditions:
>>> - wss: is used
>>> - the server certificate is self-signed
>>> (on the other hand, when using either plain ws: or a valid certificate
>>> we found no issue).
>>>
>>> The failure seems to be related not with the WebSocket protocol itself,
>>> but with the failure to establish a SSL connection.
>>> However, the same does not happen with the new implementation disabled.
>>>
>>> In particular, we have noticed small differences in the way the browser
>>> opens the sockets for SSL.
>>> When the certificate is self-signed, the browser sometimes seems to need
>>> two attempts in order to establish a connection:
>>> in the first attempt, the handshake succeeds but, after that, the
>>> browser immediately closes the socket;
>>> then the second attempt succeeds fully.
>>> We see the above pattern also when the new implementation is not
>>> enabled, but when it is enabled we see more occurrences of the pattern and
>>> this seems correlated with the failure in WebSocket establishment.
>>>
>>> Dario Crivelli
>>>
>>>
>>>
>>>> Message: 1
>>>> Date: Tue, 15 Apr 2014 15:11:49 +0900
>>>> From: Adam Rice <ricea@google.com>
>>>> To: "hybi@ietf.org" <hybi@ietf.org>
>>>> Subject: [hybi] New Chrome WebSocket implementation: testers wanted
>>>> Message-ID:
>>>>         <
>>>> CAHixhFrA2FH6JOOFkd9sjBtgvBKEO6CZ9K9T-NdKf8PvXTiG2A@mail.gmail.com>
>>>> Content-Type: text/plain; charset="utf-8"
>>>>
>>>>
>>>> The latest dev build of Chrome includes a new WebSocket implementation
>>>> behind an experimental flag. If you have version 36.0.1933.0 or greater,
>>>> you can enable it using the "Enable experimental Web Platform features"
>>>> flag in about:flags.
>>>>
>>>> An easy way to distinguish the different implementations is that the
>>>> stable
>>>> implementation does not set the "Accept-Language:" header, whereas the
>>>> new
>>>> implementation does. You can examine the headers by opening the Network
>>>> panel in "Developer Tools" before creating the WebSocket connection.
>>>>
>>>> A known issue with the new implementation is that RFC6455 connection
>>>> throttling is not implemented yet. This will be done Real Soon Now.
>>>>
>>>> We are interested in hearing about any compatibility problems you might
>>>> encounter, either server side or in client libraries.
>>>>
>>>> Feedback welcome.
>>>>
>>>> Adam Rice
>>>>
>>>
>>>
>>> _______________________________________________
>>> hybi mailing list
>>> hybi@ietf.org
>>> https://www.ietf.org/mailman/listinfo/hybi
>>>
>>>
>>
>

--001a1134b2bcb2c0a104fb22c27d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sorry for the delay in responding. This turned out to be m=
ore complicated than I expected, but the fix landed on Chromium trunk yeste=
rday (=C2=A0<a href=3D"https://codereview.chromium.org/304093003">https://c=
odereview.chromium.org/304093003</a> ). It should be available in a dev bui=
ld some time soon.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 17 April 2=
014 16:33, Dario Crivelli <span dir=3D"ltr">&lt;<a href=3D"mailto:dario.cri=
velli@lightstreamer.com" target=3D"_blank">dario.crivelli@lightstreamer.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Yes, Adam.</div><div>A=
nd this is furtherly confirmed by the fact that from the viewpoint of my se=
rver (which leverages Java&#39;s SSLEngine) the handskake completes success=
fully and only when the server waits for a request to come is the socket br=
oken.</div>


<div>Then, for some reason, Chrome seems to recover when it has to do a nor=
mal https request, whereas it doesn&#39;t when it has to do a wss interacti=
on.</div><div>I can try to provide you with more details; please advise if =
I can keep doing that legitimately through this mailing list.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">

<div><br></div><div>Dario<br></div></font></span><div><div class=3D"h5"><br=
><div class=3D"gmail_extra"><br clear=3D"all"><div><div><br></div></div><br=
><div class=3D"gmail_quote">On Thu, Apr 17, 2014 at 5:41 AM, Adam Rice <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:ricea@google.com" target=3D"_blank">ric=
ea@google.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Dario,<div><br></div><div>T=
hank you for the feedback. I will check this scenario.</div><div><br></div>=
<div>


I assume you have already instructed the browser to accept the certificate?=
 Otherwise it should fail with either implementation.</div>
<div><br></div><div>Thanks,</div><div>Adam</div><div><br></div></div><div c=
lass=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 16 April 2014 20=
:09, Dario Crivelli <span dir=3D"ltr">&lt;<a href=3D"mailto:dario.crivelli@=
lightstreamer.com" target=3D"_blank">dario.crivelli@lightstreamer.com</a>&g=
t;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi Adam,<div><br></div><div=
>We have tried the extended version of Chrome against our Lightstreamer Ser=
ver and we have noticed that, with the new implementation enabled, the brow=
ser can&#39;t open a WebSocket towards Lightstreamer Server in the followin=
g conditions:</div>





<div>- wss: is used</div><div>- the server certificate is self-signed</div>=
<div>(on the other hand, when using either plain ws: or a valid certificate=
 we found no issue).</div><div><br></div><div>The failure seems to be relat=
ed not with the WebSocket protocol itself, but with the failure to establis=
h a SSL connection.</div>





<div>However, the same does not happen with the new implementation disabled=
.</div><div><br></div><div>In particular, we have noticed small differences=
 in the way the browser opens the sockets for SSL.</div><div>When the certi=
ficate is self-signed, the browser sometimes seems to need two attempts in =
order to establish a connection:<br>





in the first attempt, the handshake succeeds but, after that, the browser i=
mmediately closes the socket;</div><div>then the second attempt succeeds fu=
lly.</div><div>We see the above pattern also when the new implementation is=
 not enabled, but when it is enabled we see more occurrences of the pattern=
 and this seems correlated with the failure in WebSocket establishment.</di=
v>





<div><br></div><div>Dario Crivelli<br></div><div><div class=3D"gmail_extra"=
><br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding=
-left:1ex">





<br>
Message: 1<br>
Date: Tue, 15 Apr 2014 15:11:49 +0900<br>
From: Adam Rice &lt;<a href=3D"mailto:ricea@google.com" target=3D"_blank">r=
icea@google.com</a>&gt;<br>
To: &quot;<a href=3D"mailto:hybi@ietf.org" target=3D"_blank">hybi@ietf.org<=
/a>&quot; &lt;<a href=3D"mailto:hybi@ietf.org" target=3D"_blank">hybi@ietf.=
org</a>&gt;<br>
Subject: [hybi] New Chrome WebSocket implementation: testers wanted<br>
Message-ID:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"mailto:CAHixhFrA2FH6JOOFkd9sjBtg=
vBKEO6CZ9K9T-NdKf8PvXTiG2A@mail.gmail.com" target=3D"_blank">CAHixhFrA2FH6J=
OOFkd9sjBtgvBKEO6CZ9K9T-NdKf8PvXTiG2A@mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=3D&quot;utf-8&quot;<div><div><br>
<br>
The latest dev build of Chrome includes a new WebSocket implementation<br>
behind an experimental flag. If you have version 36.0.1933.0 or greater,<br=
>
you can enable it using the &quot;Enable experimental Web Platform features=
&quot;<br>
flag in about:flags.<br>
<br>
An easy way to distinguish the different implementations is that the stable=
<br>
implementation does not set the &quot;Accept-Language:&quot; header, wherea=
s the new<br>
implementation does. You can examine the headers by opening the Network<br>
panel in &quot;Developer Tools&quot; before creating the WebSocket connecti=
on.<br>
<br>
A known issue with the new implementation is that RFC6455 connection<br>
throttling is not implemented yet. This will be done Real Soon Now.<br>
<br>
We are interested in hearing about any compatibility problems you might<br>
encounter, either server side or in client libraries.<br>
<br>
Feedback welcome.<br>
<br>
Adam Rice<br></div></div></blockquote><div>=C2=A0</div></div></div></div></=
div>
<br>_______________________________________________<br>
hybi mailing list<br>
<a href=3D"mailto:hybi@ietf.org" target=3D"_blank">hybi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/hybi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/hybi</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>

--001a1134b2bcb2c0a104fb22c27d--

