Checks send no Referer header, so Hetzner answers (closes #191)

Each check now sets referrerPolicy: "no-referrer". The Hetzner speed-test servers close the connection without an answer when the request has a Referer header, and the browser sent one unless the page came with the image's Referrer-Policy: no-referrer header, as from a static host or make dev. The checks now send none wherever the page is served from. s3.me-south-1.amazonaws.com still times out from this machine; curl gets no answer from it either. Model: opus-5-5
2026-10-26 02:10:43 +01:00
parent db5eb507c1
commit a72797a403
4 changed files with 29 additions and 8 deletions
@@ -23,6 +23,12 @@ Run `make frontend-viewport-test` in CI as its own step; it is not part of

 # Completed Steps

+- 2026-10-26: the six Hetzner targets answer wherever the page is served from
+  ([#191](https://git.eeqj.de/sneak/netwatch/issues/191)). They close the
+  connection without an answer when the request has a `Referer` header. The
+  browser sent one unless the page came with the image's
+  `Referrer-Policy: no-referrer` header, which a static host and `make dev` do
+  not send. Each check now sets `referrerPolicy: 'no-referrer'`
 - 2026-10-19: the server's `OnStart` hook in `internal/server/server.go` starts
  `listenAndServe` with `go func() { s.listenAndServe() }()`, as the Go style
  guide asks ([#162](https://git.eeqj.de/sneak/netwatch/issues/162)); it was