7 ms·
Send no Accept-Encoding leads to an uncompessed response, so I don't think that is the parents issue.
by SahAssar 3y ago
Send no Accept-Encoding leads to an uncompessed response, so I don't think that is the parents issue.
- lolinder 3y agoHmm, I got br when I dropped the header (see below). Either way, the server's behavior matches the spec, so there's something up with the client if they're seeing nonsense. Request: GET https://jakearchibald.com/2023/against-self-closing-tags-in-html/ Accept: text/html Response: HTTP/1.1 200 OK Date: Thu, 06 Jul 2023 17:01:20 GMT Content-Type: text/html; charset=UTF-8 ... Content-Encoding: br
- SahAssar 3y agoHuh. curl https://jakearchibald.com/2023/against-self-closing-tags-in-html/ -v > /dev/null gave me: > GET /2023/against-self-closing-tags-in-html/ HTTP/2 > Host: jakearchibald.com > user-agent: curl/7.88.1 > accept: */* > < HTTP/2 200 < date: Thu, 06 Jul 2023 17:21:26 GMT < content-type: text/html; charset=UTF-8 < access-control-allow-origin: * < cache-control: max-age=180 < strict-transport-security: max-age=31536000 < vary: Accept-Encoding < x-frame-options: DENY < x-nf-request-id: 01H4P36X7YHZQC8TEVXAN3AXX7 < cf-cache-status: REVALIDATED < report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=fcIbfNmFx0qEwjSBofViCahSkzz4vTSZ5tyXZpF7TEvuRsGJ8mkqo5PCX7pG1jYCJuV4a9bA%2FlJ4BA4F0dY2mLORDO%2F67OPRKT0TOaW5by%2FoUyjVIOI1Bh9pplcDXymLbgSp9Q%3D%3D"}],"group":"cf-nel","max_age":604800} < nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} < server: cloudflare < cf-ray: 7e29862aaea23a8a-FRA < alt-svc: h3=":443"; ma=86400 (I also tried over http1.1, gave me the same result)
- lolinder 3y agoAh, you know what, IntelliJ automatically adds an Accept-Encoding header if I leave it off, I didn't realize that until just now. Curl is a better test because it doesn't try to be clever. There's still definitely something wrong with OP's client, because the server does exactly what it's supposed to.