Follow When's standard adapter-node protocol/client-address headers and Directory's configured-origin checks. Remove the build-time origin pin, custom Host parsing and repeated loopback-IP restrictions.
Preserve authentication, exact unsafe-request Origin checks, no-store, bounded UTF-8 bodies and native financial/job behavior. Local Vite/mise development and listener bindings are unchanged.
Use When's owned HTTP-boundary pattern for compiled browser fixtures, retaining native adapter lifecycle. The small test-only Compose override changes the entrypoint, not configuration/journal/data isolation.
Include operator documentation and a web patch Changeset.
Trust contract
The proxy must exclusively control upstream access, preserve the public Host and overwrite the selected protocol/address headers. Framework request origins must match YAML url.app. This is compatibility work, not a production deployment/release redesign.
Validation
Code and readability reviews clear; documentation findings resolved.
Web typecheck, lint and build passed.
69 focused auth/request/route tests across 16 files passed.
Three browser journeys passed: sign-in/logout with and without JavaScript, plus a native query/reload.
Personal configuration and journal hashes unchanged.
Not exercised: Docker/private-image pulls, hosted CI, an actual TLS frontend proxy or a live OIDC provider. Unchanged native/storage/worker qualification suites were not rerun.
## Summary
- Follow When's standard adapter-node protocol/client-address headers and Directory's configured-origin checks. Remove the build-time origin pin, custom Host parsing and repeated loopback-IP restrictions.
- Preserve authentication, exact unsafe-request Origin checks, no-store, bounded UTF-8 bodies and native financial/job behavior. Local Vite/mise development and listener bindings are unchanged.
- Use When's owned HTTP-boundary pattern for compiled browser fixtures, retaining native adapter lifecycle. The small test-only Compose override changes the entrypoint, not configuration/journal/data isolation.
- Include operator documentation and a web patch Changeset.
## Trust contract
The proxy must exclusively control upstream access, preserve the public Host and overwrite the selected protocol/address headers. Framework request origins must match YAML `url.app`. This is compatibility work, not a production deployment/release redesign.
## Validation
- Code and readability reviews clear; documentation findings resolved.
- Web typecheck, lint and build passed.
- 69 focused auth/request/route tests across 16 files passed.
- Three browser journeys passed: sign-in/logout with and without JavaScript, plus a native query/reload.
- Private HTTP-upstream probe passed: non-loopback authenticated client, canonical Host/scheme, ignored forwarded-host spoof, exact mutation Origin, secure cookie, no-store and sign-out.
- Personal configuration and journal hashes unchanged.
Not exercised: Docker/private-image pulls, hosted CI, an actual TLS frontend proxy or a live OIDC provider. Unchanged native/storage/worker qualification suites were not rerun.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Trust contract
The proxy must exclusively control upstream access, preserve the public Host and overwrite the selected protocol/address headers. Framework request origins must match YAML
url.app. This is compatibility work, not a production deployment/release redesign.Validation
Not exercised: Docker/private-image pulls, hosted CI, an actual TLS frontend proxy or a live OIDC provider. Unchanged native/storage/worker qualification suites were not rerun.