[GH-ISSUE #2789] Custom headers not applied / working #11002

Closed
opened 2026-05-06 15:41:41 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @Root-Core on GitHub (Apr 4, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2789

Describe the Bug

Custom headers on public resources are not applied or working in Pangolin 1.17.0.
I think it was working on 1.16.x, not sure though.

Environment

  • OS Type & Version: Ubuntu 24.04.4 LTS
  • Pangolin Version: 1.17.0
  • Gerbil Version: 1.3.0
  • Traefik Version: v3.6
  • Newt Version: N/A

To Reproduce

  • Create resource
  • Add custom headers, eg
    • Access-Control-Allow-Origin: *
  • Check headers of resource, eg
    • curl -X HEAD -I https://example.com/

Expected Behavior

The custom header is expected to be present in the response.

Originally created by @Root-Core on GitHub (Apr 4, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2789 ### Describe the Bug Custom headers on public resources are not applied or working in Pangolin 1.17.0. I *think* it was working on 1.16.x, not sure though. ### Environment - OS Type & Version: Ubuntu 24.04.4 LTS - Pangolin Version: 1.17.0 - Gerbil Version: 1.3.0 - Traefik Version: v3.6 - Newt Version: N/A ### To Reproduce - Create resource - Add custom headers, eg - `Access-Control-Allow-Origin: *` - Check headers of resource, eg - `curl -X HEAD -I https://example.com/` ### Expected Behavior The custom header is expected to be present in the response.
Author
Owner

@oschwartz10612 commented on GitHub (Apr 5, 2026):

Hello! Headers are sent to the downstream target in the request and not in the response to the user. You should see the header if you use something like the traefik whoami container that will show you the request headers. If that is broken please reopen and LMK!

<!-- gh-comment-id:4188189705 --> @oschwartz10612 commented on GitHub (Apr 5, 2026): Hello! Headers are sent to the downstream target in the request and not in the response to the user. You should see the header if you use something like the traefik whoami container that will show you the request headers. If that is broken please reopen and LMK!
Author
Owner

@Root-Core commented on GitHub (Apr 5, 2026):

@oschwartz10612 My bad, I misunderstood the setting. The initial feature request also asked for response headers, did you omit this by purpose?

I think Traefik supports both kinds of header (customRequestHeaders / customResponseHeaders).

CC #1446
CC #1449
CC https://github.com/orgs/fosrl/discussions/455

There is also a newer feature request: https://github.com/orgs/fosrl/discussions/1939

<!-- gh-comment-id:4188972735 --> @Root-Core commented on GitHub (Apr 5, 2026): @oschwartz10612 My bad, I misunderstood the setting. The [initial feature request](https://github.com/orgs/fosrl/discussions/455) also asked for response headers, did you omit this by purpose? I think Traefik supports both kinds of header (`customRequestHeaders` / `customResponseHeaders`). CC #1446 CC #1449 CC https://github.com/orgs/fosrl/discussions/455 There is also a newer feature request: https://github.com/orgs/fosrl/discussions/1939
Author
Owner

@oschwartz10612 commented on GitHub (Apr 6, 2026):

I agree I think we should implement!

<!-- gh-comment-id:4190174598 --> @oschwartz10612 commented on GitHub (Apr 6, 2026): I agree I think we should implement!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#11002