Open a timeline's own address behind an HTTPS proxy (#255)
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
Behind a proxy that sends X-Forwarded-Proto: https, the rewrite from / / to /timelines/ had the https scheme, which Next.js took for another server: it proxied the request to https on itself, which failed with a 500. The rewrite is now to this server's own plain http. An address with nothing the visitor may see, missing or private, now has a page of its own: still a 404, so a private timeline's address doesn't say it exists, but one that offers a guest to sign in and come back. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/a12204addb5434ce416cfaf31bc338e29165d21d
Related
Open Open a timeline's own address behind an HTTPS proxy (#255) in the timeline