sif-server-proxy-api-config

Server proxy configuration mismatches are diagnosed by verifying /api paths and PUBLIC_PATH frontend paths against environment variables and nais.json. The workflow checks reverseProxy.ts and initApiClients.ts to produce an actionable report of inconsistencies and fixes.

Frontend path routing fails when PUBLIC_PATH and *_FRONTEND_PATH variables do not align with nais.json configurations across dev and prod. Diagnose these environment schema mismatches to identify incorrect ingoingUrl path mappings and resolve deployment issues.

The best way to verify API client initialization is to cross-check initApiClients.ts against server reverseProxy.ts. Ensure *_API_SCOPE and *_API_URL variables map correctly to the reverse proxy rules to prevent misrouted requests before deployment.

Yes, the diagnostic workflow supports verifying nais.json configurations across both dev and prod environments. It checks consistency between app initialization, environment schemas, and reverse proxy mappings to ensure correct routing in each deployment target.

Fix misrouted API requests by running a diagnostic pass to verify app init, env schemas, and reverse proxy mappings. The resulting diagnostic report records mismatches between *_API_URL variables and proxy rules, providing concrete fixes to correct the routing.

Run a server proxy configuration diagnostic check before deployment when updating environment variables, nais.json files, or reverse proxy rules. This prevents misrouted requests by verifying path consistency across initApiClients.ts, frontendPath mappings, and reverseProxy.ts.