Description of case: Send 1000 compressed messages each of payload size 4096, auto-fragment to 0 octets. Use default permessage-deflate offer.
The very first frame send on this testcase sends 300 bytes of payload.
Its a text frame, with fin=true.
The server receives the 300 bytes, and inflates it to 4096 bytes of text.
The sha1 checksum for this 4096 bytes is 66976578abf9a7f1fc653c2bf9dcd40a9a8a19e2
However, the testcase assumes the sha1 checksum is 0c128dcadfd58d297bdb0e65946c1837c6acf9af
A raw capture of the autobahn sent frame in wireshark and a manual inflate of those raw bytes show the same sha1sum as the implementation as I'm testing.
I can provide the wireshark captured frame payload (300 bytes deflated), and the resulting inflated frame payload (4096 bytes) as examples of this result.
joakime
commented
9 years ago
Description of case: Send 1000 compressed messages each of payload size 4096, auto-fragment to 0 octets. Use default permessage-deflate offer.
The very first frame send on this testcase sends 300 bytes of payload. Its a text frame, with fin=true.
The server receives the 300 bytes, and inflates it to 4096 bytes of text. The sha1 checksum for this 4096 bytes is
66976578abf9a7f1fc653c2bf9dcd40a9a8a19e2However, the testcase assumes the sha1 checksum is
0c128dcadfd58d297bdb0e65946c1837c6acf9afA raw capture of the autobahn sent frame in wireshark and a manual inflate of those raw bytes show the same sha1sum as the implementation as I'm testing.
I can provide the wireshark captured frame payload (300 bytes deflated), and the resulting inflated frame payload (4096 bytes) as examples of this result.