HTTP/2 服务器推送现在不适用于 Zeit答案

【问题标题】：HTTP/2 Server Push Not working with Zeit NowHTTP/2 服务器推送现在不适用于 Zeit
【发布时间】：2020-02-24 01:31:19
【问题描述】：

在我的项目中，我正在尝试做 HTTP/2 服务器推送，因为 Zeit 支持 HTTP/2。

所以，我在请求中添加了必要的链接头。

但是当我检查网络选项卡时，initiator 显示为Other 而不是Push/Other。

然后我检查了另一个站点：https://http2-server-push-demo.keksi.io/，这里的 Push 很明显。

这里发生了什么？我不理解。我正在使用 Now CLI v16.4.4。有人可以帮忙吗？

一些调试信息

以防万一，这里有一些命令输出：

命令： curl --http2 -v https://example.com

curl --http2 -v https://ccrewards.in
 * Rebuilt URL to: https://ccrewards.in/
 *   Trying 13.234.90.190...
 * TCP_NODELAY set
 * Connected to ccrewards.in (13.234.90.190) 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.2 (OUT), TLS handshake, Client hello (1):
 * TLSv1.2 (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, Client hello (1):
 * TLSv1.2 (OUT), TLS handshake, Finished (20):
 * TLSv1.2 (IN), TLS handshake, Finished (20):
 * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
 * ALPN, server accepted to use h2
 * Server certificate:
 *  subject: CN=ccrewards.in
 *  start date: Oct 25 06:44:21 2019 GMT
 *  expire date: Jan 23 06:44:21 2020 GMT
 *  subjectAltName: host "ccrewards.in" matched cert's "ccrewards.in"
 *  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
 *  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 0x7fffe6a71b70)
> GET / HTTP/2
> Host: ccrewards.in
> User-Agent: curl/7.58.0
> Accept: */*
>
 * Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200
< content-type: text/html; charset=utf-8
< link: </css/bootstrap.min.css>; rel=preload; as=style, </css/placeholder-loading.min.css>; rel=preload; as=style
< date: Mon, 28 Oct 2019 18:06:54 GMT
< vary: User-Agent, Accept-Encoding
< content-encoding: gzip
< content-length: 28149
< etag: "4eadf-E5nKTWVXCBjTRiqdEed4eCgcd6A"
< accept-ranges: none
< cache-control: public, max-age=0, must-revalidate
< x-now-cache: STALE
< x-now-trace: bom1
< server: now
< x-now-id: bom1:bom1:48cbv-1572288058858-8bf8eca0e432
< strict-transport-security: max-age=63072000
<
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 != 15963)
 * Connection #0 to host ccrewards.in left intact

【问题讨论】：

标签： nuxt.js http2 server-push vercel

【解决方案1】：

服务器支持 HTTP/2 并不意味着它支持 HTTP/2 的所有功能。即使是这样，也并不意味着它使用链接头启动推送——这在HTTP/2 spec 中没有定义，而是许多（但不是所有）服务器用来启动 HTTP/2 推送的方法。

使用 nghttp 检查您的网站（比 curl 更好地进行 HTTP/2 调试），我看不到正在推送和来自服务器的帧。

我不熟悉 Zeit-now，但快速的 Google 建议它可能构建在不支持链接头作为推送方法的 Node 之上，而您必须使用 http2stream.pushStream 到 explicitly initiate an HTTP/2 push。

【讨论】：