Segment-bound doctor and scheduler frontdoor chunks
This commit is contained in:
@@ -136,8 +136,9 @@ flows, Rekor, and static/platform bootstrap assets).
|
||||
The local route table also carries a small set of explicit precedence rules that must stay ahead of the
|
||||
generic `^/api/v1/{service}` matcher. Platform-owned surfaces such as `/api/v1/aoc/*` and
|
||||
`/api/v1/administration/*` resolve directly to `platform`, and browser compatibility prefixes such as
|
||||
`/doctor/*` and `/scheduler/*` strip the frontdoor prefix before dispatch so the target services still
|
||||
receive their canonical `/api/v1/doctor/*` and `/api/v1/scheduler/*` paths.
|
||||
`/doctor/*` and `/scheduler/*` are segment-bound before they strip the frontdoor prefix for dispatch.
|
||||
That keeps the target services on their canonical `/api/v1/doctor/*` and `/api/v1/scheduler/*` paths
|
||||
without hijacking frontend assets like `doctor.routes-*.js` or `scheduler-ops.routes-*.js`.
|
||||
|
||||
```bash
|
||||
# Default frontdoor route table
|
||||
|
||||
Reference in New Issue
Block a user