Skip to content

fix(proxy): preserve external scheme through web proxies - #354

Closed
fit2bot wants to merge 1 commit into
devfrom
pr@dev@fix_proxy_forwarded-proto
Closed

fit2bot wants to merge 1 commit into
devfrom
pr@dev@fix_proxy_forwarded-proto

Conversation

@fit2bot

@fit2bot fit2bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

HTTPS requests were proxied to Core without their original scheme, so generated PAM Agent/SDK materials and copied application connection information could contain HTTP URLs.

Forward the connection scheme at the Web entry point. Under the existing trusted load-balancer mode (USE_LB=0), preserve an upstream http or https value and fall back to the connection scheme for missing or invalid values. Keep the default mode from trusting client-supplied protocol headers.

Validation:

  • bash -n init.sh and git diff --check passed.
  • python3 -m unittest discover -s tests -v: 5 tests passed, including 32 combinations through real Nginx HTTP/HTTPS entry points and the internal Core proxy hop.
  • Local Nginx-to-Django verification with an isolated application fixture: PAM Agent, Python/Go/Java/Node.js SDKs, and copied connection information produced the expected scheme and preserved the host/port in 7 deployment/header scenarios. TLS tests trusted a generated test certificate; certificate verification remained enabled.

Only docker-web changes are included. Live deployment and actual client connections were not performed.

@w940853815 w940853815 closed this Nov 16, 2026
@w940853815
w940853815 deleted the pr@dev@fix_proxy_forwarded-proto branch November 16, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants