HydraIssues

hydrareverseproxy strips Authorization header from proxied requests
open bug Project: hydrareverseproxy Reporter: 22 Mar 2026 16:17

Description

## Problem

hydrareverseproxy v0.1.1 on the dashboard server (78.47.174.83) does not forward the Authorization header to backend services. This means all API calls that require Bearer token authentication fail with 401 when going through the reverse proxy.

## Impact

- issues.experiencenet.com API is unreachable externally (all authenticated endpoints return 401)
- books.experiencenet.com API likely affected too
- Any service behind hydrareverseproxy that uses Authorization headers for auth
- Workaround: SSH into the server and curl localhost directly

## Expected behavior

hydrareverseproxy should forward all request headers (including Authorization) to the backend unmodified.

## Reproduction