Support reverse proxy path prefixes - #783
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
1|## Summary
2|
3|- add fail-closed base-path configuration and explicit trusted-prefix handling for mounted deployments
4|- make server-rendered, browser, module, manifest, and service-worker URLs path-prefix aware
5|- add real proxy and browser coverage for mounted application journeys
6|- simplify maintenance and test infrastructure while retaining the built-in registry and complete Windows artifact checks
7|- harden browser rendering, internal redirects, and the real-prefix test proxy; update the
pypdfsecurity floor8|- document the supported reverse-proxy and platform-wrapper contracts
9|
10|## Validation
11|
12|- real Home Assistant Supervisor Ingress validation by @lennard0711 on commit
3cc2b4d: setup/login, dashboard, logout/login, Settings, module navigation, assets, redirects, and console/network checks passed through direct and externally proxied Home Assistant access13|- corrected-head full browser E2E suite:
526 passed14|- corrected-head complete non-E2E suite:
3532 passed, 2 skipped15|- corrected-head focused security and contract suite:
254 passed16|- corrected-head real-proxy, prefix, BNetzA, and SmokePing browser regressions:
7 passed17|-
pip-auditreported no known vulnerabilities after updatingpypdfto6.15.018|- hash-pinned Linux and Windows runtime locks reproduced byte-for-byte
19|- all 69 locale files remained synchronized
20|
21|Closes #781
22|