circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

Per-address limits count each client's own address behind Next.js

  • github
  • github/openchronology/timeline-app
  • commit
  • main
  • github/athanclark

Route handlers get a web Request without its connection, so the API saw every request through Next.js as coming from 'unknown'. The standalone launcher now starts with server/peer-address.cjs, which writes each request's connecting address into a request header (replacing any a client sent) with a secret made at start; next-handler.mjs believes it only with that secret. X-Forwarded-For is still used only with TRUST_PROXY=1. The server also warns once when a proxy on the same machine sends X-Forwarded-For while TRUST_PROXY is not 1. The docs say what the address is behind a proxy and under Compose, and a platform test checks two addresses get separate sign-in limits. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/ce2f2a6c0a503e2fe080b63663cf1ef8a37437ca

Open Per-address limits count each client's own address behind Next.js in the timeline

Per-address limits count each client's own address behind…