blog/ link saying "too many links" #5

New issue

Open

opened 2026-06-26 13:44:23 +02:00 by jeremiah · 1 comment

jeremiah commented

2026-06-26 13:44:23 +02:00

Owner

Claude says this is the fix:

error_page 404 /404.html;
location = /404.html { internal; }

Claude says this is the fix: ``` error_page 404 /404.html; location = /404.html { internal; } ```

claude-bot referenced this issue from a commit

2026-06-26 14:16:51 +02:00

Add root 404 page to break nginx redirect loop

claude-bot commented

2026-06-26 14:18:24 +02:00

Collaborator

Symptom fixed in repo (deployed). Added a root /404.html (commit 94f64ef, live on production).

The loop happened because nginx 404s issue 302 Location: 404.html (relative). With no file at the web root, that target itself 404'd and re-triggered the handler — an infinite loop. With a real /404.html present, the relative target now resolves to an actual page.

Verified live:

$ curl -sIL --max-redirs 10 https://sverige.email/blogg
HTTP/1.1 302 Moved Temporarily   ->  Location: 404.html
HTTP/1.1 200 OK                  ->  /404.html
# 1 redirect, terminates (was looping indefinitely)

Follow-up needed (server-side, on suomalainen)

The repo fix stops the loop, but nginx still returns a 302 then 200 for missing paths. The correct behaviour is a real 404 status served internally. Apply this in the server {} block and reload nginx:

error_page 404 /404.html;
location = /404.html { internal; }

After that, missing paths return 404 directly with no redirect. This is the only remaining action — once nginx is reloaded and confirmed (curl -sI https://sverige.email/blogg should show HTTP/1.1 404), this issue can be closed.

— claude-bot

**Symptom fixed in repo (deployed).** Added a root `/404.html` (commit `94f64ef`, live on production). The loop happened because nginx 404s issue `302 Location: 404.html` (relative). With no file at the web root, that target itself 404'd and re-triggered the handler — an infinite loop. With a real `/404.html` present, the relative target now resolves to an actual page. Verified live: ``` $ curl -sIL --max-redirs 10 https://sverige.email/blogg HTTP/1.1 302 Moved Temporarily -> Location: 404.html HTTP/1.1 200 OK -> /404.html # 1 redirect, terminates (was looping indefinitely) ``` --- ### Follow-up needed (server-side, on suomalainen) The repo fix stops the loop, but nginx still returns a **302 then 200** for missing paths. The correct behaviour is a real **404 status** served internally. Apply this in the `server {}` block and reload nginx: ```nginx error_page 404 /404.html; location = /404.html { internal; } ``` After that, missing paths return `404` directly with no redirect. This is the only remaining action — once nginx is reloaded and confirmed (`curl -sI https://sverige.email/blogg` should show `HTTP/1.1 404`), this issue can be closed. — claude-bot