mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-08 05:39:49 -05:00
Support for X-Forwarded-Proto Header to Prevent Mixed Content Issues #102
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#102
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kerbymart on GitHub (Feb 24, 2025).
I'm encountering mixed content errors when accessing services through Pangolin. This issue arises because Pangolin, acting as a reverse proxy, doesn't currently set the
X-Forwarded-Protoheader. As a result, backend services are unable to determine the original protocol (HTTP or HTTPS) used by the client, leading to mixed content warnings and blocked resources in browsers.Proposed Solution:
Implement the addition of the
X-Forwarded-Protoheader in Pangolin's reverse proxy functionality. This header should reflect the protocol used by the client to connect to Pangolin (httporhttps). By including this header, backend services can accurately detect the client's protocol and adjust their responses accordingly, thereby preventing mixed content issues.References:
ONLYOFFICE Documentation: Discusses the importance of the
X-Forwarded-Protoheader in proxy setups to prevent mixed content errors.MDN Web Docs: Provides an overview of the
X-Forwarded-Protoheader and its role in identifying the protocol used by the client.Implementing this feature would enhance Pangolin's compatibility with various backend services and improve security by preventing mixed content issues.
@oschwartz10612 commented on GitHub (Feb 24, 2025):
Hi!
Take a look at the following Traefik documentation. Maybe you can try to edit your config files to include the header? Let me know if something prevents you from doing this.
https://doc.traefik.io/traefik/middlewares/http/headers/