fix: support HTTPS proxy by using relative API paths #8

Merged

tanyar09 merged 1 commits from fix/https-proxy-api-routing into dev

2026-01-23 14:04:32 -05:00

Author	SHA1	Message	Date
tanyar09	70cfd63ca1	fix: support HTTPS proxy by using relative API paths All checks were successful CI / skip-ci-check (pull_request) Successful in 1m51s Details CI / lint-and-type-check (pull_request) Successful in 2m32s Details CI / python-lint (pull_request) Successful in 2m16s Details CI / test-backend (pull_request) Successful in 4m11s Details CI / build (pull_request) Successful in 4m59s Details CI / secret-scanning (pull_request) Successful in 1m59s Details CI / dependency-scan (pull_request) Successful in 1m58s Details CI / sast-scan (pull_request) Successful in 3m7s Details CI / workflow-summary (pull_request) Successful in 1m50s Details - Update API client to use relative paths when VITE_API_URL is empty - Fix EventSource URLs to use window.location.origin for proxy compatibility - Update image/video URL construction to use relative paths - Add debug logging for API response troubleshooting - All API calls now work correctly when served through HTTPS proxy This fixes mixed content errors and allows the admin frontend to work when accessed via HTTPS domain with reverse proxy (Caddy/nginx).	2026-01-23 18:59:46 +00:00