#255 A timeline's own address fails with a 500 behind an HTTPS proxy
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#255
- issue
- state:closed
Behind a reverse proxy that sends `X-Forwarded-Proto: https` (Caddy does by default), opening a timeline at its own address (`/ / `, #148) answers 500 Internal Server Error. The platform's proxy rewrites the address to `/timelines/ ` with `new URL(…, request.url)`, and `request.url` then has the https scheme while the server itself listens on plain http, so Next.js treats the rewrite as a request to another server and proxies it to `https://localhost:5173`, which fails (`EPROTO … wrong version number`). Seen on timescale.info; worked around there by not sending X-Forwarded-Proto. Plain-http servers are unaffected. https://github.com/openchronology/timeline-app/issues/255
Related
Open #255 A timeline's own address fails with a 500 behind an HTTPS proxy in the timeline