Ignas Damunskis
Ignas Damunskis

Reputation: 1504

Debugging HTTP/2 with curl gives different responses from different places

Context

I try to enable HTTP/2 through my nginx configurations:

server {
  listen 443 ssl http2;
  listen [::]:443 ssl http2;
  server_name stg.grozissaviems.lt;
  ssl_certificate /etc/nginx/certs/stg.grozissaviems.lt.crt;
  ssl_certificate_key /etc/nginx/certs/stg.grozissaviems.lt.key;
  ssl_protocols TLSv1.2;
}

Issue

When I run curl -I -L https://stg.grozissaviems.lt to debug HTTP/2:

When I debug it using this KeyCDN tool I see:

HTTP/2 protocol is supported.

ALPN extension is supported.

When I access the website using Google Chrome, in the Network tab I see:

stg.grozissaviems.lt 200 http/1.1

Quicksand-Bold.ttf 200 http/1.1

Why does it differ?

Upvotes: 1

Views: 422

Answers (1)

Ignas Damunskis
Ignas Damunskis

Reputation: 1504

I finally found the issue. According to this answer:

You are using anti-virus software and it is MITM your traffic and so downgrading you to HTTP/1.1. ...

I did turn my anti-virus off and I could finally see HTTP/2 in the Networks tab!

In case someone stumbles upon my question and turning anti-virus software does not help, check this answer for more solutions.

Upvotes: 1

Related Questions