如何在JavaScript中复制GZipStream.Write()?

时间:2019-08-16 09:16:19

标签: javascript c# zlib gzipstream pako

我有这段C#代码:

public static byte[] TestGzip(string text)
    {
        byte[] bytes = Encoding.UTF8.GetBytes(text);
        MemoryStream memoryStream1 = new MemoryStream();

        using (GZipStream gzipStream = new GZipStream(memoryStream1, CompressionMode.Compress, true))
            gzipStream.Write(bytes, 0, bytes.Length);

        memoryStream1.Position = 0L;
        byte[] buffer = new byte[memoryStream1.Length];
        memoryStream1.Read(buffer, 0, buffer.Length);

        return buffer;
    }

,我想在JavaScript中重现这段代码,所以我尝试了pakonode.js zlib
以下是它们的输出与GZipStream和彼此之间的输出稍有不同的方式:

const zlib = require('zlib');
const pako = require('pako');
const cc = str => [...str].map(c => c.charCodeAt(0) & 255);

// C# (this is what I want)
Program.TestGZip("a")                 // [31, 139, 8, 0, 0, 0, 0, 0, 4, 0, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0]

// JS
pako.gzip("a")                        // [31, 139, 8, 0, 0, 0, 0, 0, 0, 3, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0] Uint8Array(21)
pako.gzip([97])                       // same...
pako.gzip(new Uint8Array([97]))       // same...
pako.gzip(cc("a"))                    // same...

zlib.gzipSync("a")                    // [31, 139, 8, 0, 0, 0, 0, 0, 0, 10, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0] Buffer(21)
zlib.gzipSync(new Uint8Array([97]))   // same...

我还尝试了pakozlib的一些不同选项,虽然某些选项的结果不同,但是却从未与C#的结果相匹配:

// different options
zlib.gzipSync("a", {level: 1})        // [31, 139, 8, 0, 0, 0, 0, 0, 4, 10, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0]
zlib.gzipSync("a", {level: 9})        // [31, 139, 8, 0, 0, 0, 0, 0, 2, 10, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0]
zlib.gzipSync("a", {strategy: 2|3})   // [31, 139, 8, 0, 0, 0, 0, 0, 4, 10, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0]

pako.gzip("a", {level: 1})            // [31, 139, 8, 0, 0, 0, 0, 0, 4, 3, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0]
pako.gzip("a", {level: 9})            // [31, 139, 8, 0, 0, 0, 0, 0, 2, 3, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0]
pako.gzip("a", {strategy: 2|3})       // [31, 139, 8, 0, 0, 0, 0, 0, 4, 3, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0]

那我该怎么办?
为什么会有这些细微的差异?
如何获得准确的GZipStream.Write()输出?

修复(感谢@Sebastian):

pako.gzip("a", {strategy: 2, header:{os: 0}})
pako.gzip("a", {strategy: 3, header:{os: 0}})

// weirdly enough, just passing an empty header object works as well:
pako.gzip("a", {strategy: 2, header:{}})
pako.gzip("a", {strategy: 3, header:{}})

// all outputs are exactly like GZipStream.Write():
// [31, 139, 8, 0, 0, 0, 0, 0, 4, 0, 75, 4, 0, 67, 190, 183, 232, 1, 0, 0, 0]

1 个答案:

答案 0 :(得分:1)

看起来这些库对标头的编码方式有所不同:

来自http://www.onicos.com/staff/iz/formats/gzip.html

method

因此,他们只需声明不同的OS类型(TOPS-20?!,Unix,FAT)。 如果确实需要,您可能必须修补JS库以将“ FAT”输出为OS。

查看pako来源,您可能可以根据自己的喜好更改值,并且还暗示“额外标志”的用途是: 来自Github

Offset   Length   Contents
 ...
  8      1 byte   extra flags (depend on compression method)
  9      1 byte   OS type

调整级别和策略以及os标头字段,您应该一切顺利!