Closed ghost closed 9 years ago
What is the Accept-Encoding field you supply with curl?
Hi,
full output of curl -v, using HTTP/1.1:
* Trying 127.0.0.1...
* Connected to remote.host (127.0.0.1) port 443 (#0)
* found 180 certificates in /etc/ssl/certs/ca-certificates.crt
* found 724 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: remote.host (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* [...]
* compression: NULL
* ALPN, server accepted to use http/1.1
> GET /http2/ HTTP/1.1
> Host: remote.host
> User-Agent: curl/7.45.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 21 Oct 2015 13:53:38 GMT
< Content-Type: text/html; charset=utf-8
< Transfer-Encoding: chunked
< Vary: Accept-Encoding
< Vary: Accept-Encoding
< Public-Key-Pins: pin-sha256="sggymnso4MC+EGK/CjpEYzpHqNYgFoT+3AxbPG/06LM="; pin-sha256="qWRoFIB2OK8l7M4/nAKetrygsdoqgA5MgQpGKeKgVi0="; max-age=15768000
< Server: nghttpx nghttp2/1.3.4
< Via: 1.1 nghttpx
< X-Content-Type-Options: nosniff
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1; mode=block
< Strict-Transport-Security: max-age=31536000; preload
< Front-End-Https: on
< X-UA-Compatible: IE=Edge,chrome=1
Looking at the gdb output, #1, could this be an issue when using quotes in the http headers? (pin-sha256="")? Not sure why brotli would care for this, but not sure why this would be in the core either if it's not related?
I pushed a possible fix, can you check and tell me if it worked?
confirmed, no crash with both h1 and h2, thanks!
Thank you
Hi,
not sure, if this an upstream google/brotli issue, but since I'm using cloudflare's bundle I'll put it here first, maybe you guys have an idea what's going on:
I packaged nginx 1.9.5 for debian, with ngx_brotli_module-master.
nginx sits behind nghttpx, a tls offloader and http2 proxy, communicating over http/1.1/no-tls with the nginx backend. When opening a page with multiple png images (rand() generated) with chrome or firefox, everything's fine, using gzip though. Opening the same page with curl, both HTTP/1.1 and HTTP2, nginx crashes immediately.