Skip to content

fix(dev-admin): gate the AI proxy and service probes like /__dev - #237

Merged
tina4stack merged 1 commit into
v3from
fix/dev-ai-proxy-gate
Oct 19, 2026
Merged

tina4stack merged 1 commit into
v3from
fix/dev-ai-proxy-gate

Conversation

@M1gael

@M1gael M1gael commented Oct 15, 2026

Copy link
Copy Markdown
Collaborator

The dev-admin routes that sit outside /__dev — the AI gateway proxy and the service probes the dashboard calls — were not covered by the dev-admin gate (Host allow-list, same-origin, loopback peer) that every /__dev route takes. They now go through the same gate, so they behave exactly like the rest of the dev admin. The dashboard's own same-origin calls keep working.

Tests: a new suite drives the real front controller and asserts refused callers never reach the gateway, plus a positive control for the dashboard. It fails on the current tip and passes with this change. Full suite shows no new failures.

The dev-admin routes that live outside /__dev (/ai/api/chat and the /ai, /vision, /embed, /image, /rag probes) skipped the Host, same-origin and loopback-peer checks every /__dev route takes. They now pass through the same gate. The dashboard's own same-origin calls are unaffected.

Signed-off-by: Michael <michael@codeinfinity.co.za>
@M1gael

M1gael commented Oct 15, 2026

Copy link
Copy Markdown
Collaborator Author

I have read the Tina4 Contributor Licence Agreement and I agree to it.

@M1gael M1gael closed this Oct 15, 2026
@M1gael M1gael reopened this Oct 15, 2026
@tina4stack
tina4stack merged commit 970f22d into v3 Oct 19, 2026
21 of 23 checks passed
@tina4stack
tina4stack deleted the fix/dev-ai-proxy-gate branch October 19, 2026 06:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants