使用 Gzip 头实现文件强制下载

积累知识，胜过积蓄金银！毕竟在Golang开发的过程中，会遇到各种各样的问题，往往都是一些细节知识点还没有掌握好而导致的，因此基础知识点的积累是很重要的。下面本文《使用 Gzip 头实现文件强制下载》，就带大家讲解一下知识点，若是你对本文感兴趣，或者是想搞懂其中某个知识点，就请你继续往下看吧~

我正在尝试压缩所有回复。 在main.go中

mux := mux.newrouter()
mux.use(middlewareheaders)
mux.use(gziphandler)

然后我有中间件：

func gziphandler(next http.handler) http.handler {
    return http.handlerfunc(func(w http.responsewriter, r *http.request) {
        gz := gzip.newwriter(w)
        defer gz.close()
        gzr := gzipresponsewriter{writer: gz, responsewriter: w}
        next.servehttp(gzr, r)
    })
}

func middlewareheaders(next http.handler) http.handler {
    return http.handlerfunc(func(w http.responsewriter, r *http.request) {
        w.header().set("cache-control", "max-age=2592000") // 30 days
        w.header().set("content-encoding", "gzip")
        w.header().set("strict-transport-security", "max-age=63072000; includesubdomains; preload")
        w.header().set("access-control-allow-headers", "content-type,x-amz-date,authorization,x-api-key,x-amz-security-token")
        w.header().set("access-control-allow-methods", "post")
        w.header().set("access-control-allow-origin", "origin")
        w.header().set("access-control-allow-credentials", "true")
        w.header().set("access-control-expose-headers", "amp-access-control-allow-source-origin")
        w.header().set("amp-access-control-allow-source-origin", os.getenv("domain"))
        next.servehttp(w, r)
    })
}

当我卷曲网站时，我得到

curl -v https://example.com
*   Trying 44.234.222.27:443...
* TCP_NODELAY set
* Connected to example.com (XX.XXX.XXX.XX) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=example.com
*  start date: Mar 16 00:00:00 2021 GMT
*  expire date: Apr 16 23:59:59 2022 GMT
*  subjectAltName: host "example.com" matched cert's "example.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55cadcebfe10)
> GET / HTTP/2
> Host: example.com
> user-agent: curl/7.68.0
> accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200 
< date: Mon, 07 Jun 2021 20:13:19 GMT
< access-control-allow-credentials: true
< access-control-allow-headers: Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token
< access-control-allow-methods: POST
< access-control-allow-origin: origin
< access-control-expose-headers: AMP-Access-Control-Allow-Source-Origin
< amp-access-control-allow-source-origin: example.com
< cache-control: max-age=2592000
< content-encoding: gzip
< strict-transport-security: max-age=63072000; includeSubDomains; preload
< vary: Accept-Encoding
< 
Warning: Binary output can mess up your terminal. Use "--output -" to tell 
Warning: curl to output it to your terminal anyway, or consider "--output 
Warning: <FILE>" to save to a file.
* Failed writing body (0 != 3506)
* stopped the pause stream!
* Connection #0 to host example.com left intact

启用 gzip 处理程序和 gzip 标头时，浏览器想要下载文件。

有人能发现我的错误吗？

正确答案

1.仅当客户端请求时，您才应使用 gzip。

accept-encoding：从来没有请求过 gzip，但你还是 gzip 响应。

所以 curl 按原样将其返回给您。

2.考虑到浏览器的行为，这听起来像是双重压缩。也许您有一些 http 反向代理，它已经处理浏览器的压缩，但不压缩后端流量。因此，您可能根本不需要在后端进行任何 gzipping - 尝试 curl --compressed 来确认这一点。

3.您应该从响应中过滤掉 content-length。 content-length是压缩后的http响应的最终大小，因此该值在压缩过程中会发生变化。

4.您不应该盲目地对所有 uri 应用压缩。一些处理程序已经执行 gzip 压缩（例如 prometheus /metrics），而有些处理程序则毫无意义进行压缩（例如 .png、.zip、.gz）。至少在将 accept-encoding: gzip 从请求中删除，然后再将其传递到处理程序链，以避免双重 gzipping。

5. go 中的透明 gzipping 之前已经实现过。快速搜索显示 this gist（根据上面第 4 点进行调整）：

package main

import (
    "compress/gzip"
    "io"
    "io/ioutil"
    "net/http"
    "strings"
    "sync"
)

var gzPool = sync.Pool{
    New: func() interface{} {
        w := gzip.NewWriter(ioutil.Discard)
        return w
    },
}

type gzipResponseWriter struct {
    io.Writer
    http.ResponseWriter
}

func (w *gzipResponseWriter) WriteHeader(status int) {
    w.Header().Del("Content-Length")
    w.ResponseWriter.WriteHeader(status)
}

func (w *gzipResponseWriter) Write(b []byte) (int, error) {
    return w.Writer.Write(b)
}

func Gzip(next http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        if !strings.Contains(r.Header.Get("Accept-Encoding"), "gzip") {
            next.ServeHTTP(w, r)
            return
        }

        w.Header().Set("Content-Encoding", "gzip")

        gz := gzPool.Get().(*gzip.Writer)
        defer gzPool.Put(gz)

        gz.Reset(w)
        defer gz.Close()

        r.Header.Del("Accept-Encoding")
        next.ServeHTTP(&gzipResponseWriter{ResponseWriter: w, Writer: gz}, r)
    })
}

注意 - 以上不支持分块编码和预告片。因此仍有改进的机会。

文中关于的知识介绍，希望对你的学习有所帮助！若是受益匪浅，那就动动鼠标收藏这篇《使用 Gzip 头实现文件强制下载》文章吧，也可关注golang学习网公众号了解相关技术文章。