"ALPN offers h2,http/1.1" even though only h2 is configured

Hi,

In fly.toml I have this:

[[services.ports]]
  port = 443
  handlers = ["tls"]
  tls_options = { "alpn" = ["h2"] }

And when I do curl -v https://mayu.live I see this:

* Connected to mayu.live (188.93.146.177) port 443 (#0)
* ALPN: offers h2,http/1.1

I assume it shouldn’t offer http/1.1 with my current configuration, but I still get HTTP/1.1-requests from the Google crawler, but the application doesn’t support HTTP/1.1 so it prints an error and Google refuses to index the site.

Any ideas? Thanks in advance.

That is an issue on our side. We’re looking into fixing it.

Thanks for the update! :slight_smile:

Another question, is it possible to do a HTTP check with HTTP/2 Cleartext? With Apps V1 I had a script check that did curl -s --http2-prior-knowledge http://localhost:3000/__mayu/status but with the new HTTP checks it seems like it’s doing a HTTP/1.1 request.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.