Rene Fichtmueller 1d4be52c83 fix: only send HSTS header on HTTPS connections, not HTTP ...

The learning process was failing to communicate with the gateway because:
1. Gateway was sending 'Strict-Transport-Security' header on HTTP responses
2. Node.js fetch respects HSTS and upgrades subsequent requests to HTTPS
3. Gateway only has HTTP listener (localhost:3103), no HTTPS
4. Result: SSL 'packet length too long' error on second request attempt

Solution: Modified registerHSTSMiddleware to only send HSTS header when
the connection is already secure (HTTPS or x-forwarded-proto: https).
HTTP connections will not get the HSTS header, preventing the forced upgrade.

2026-04-26 19:01:41 +02:00

0 lines

0 B

Plaintext

Raw Blame History

The file is empty.