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
Collaborator

Summary of what's been done:
Fixed API client to use relative paths for HTTPS proxy compatibility
Updated all API URL constructions to work with proxy
Added debug logging for troubleshooting
Created and pushed branch with all changes

Summary of what's been done: Fixed API client to use relative paths for HTTPS proxy compatibility Updated all API URL constructions to work with proxy Added debug logging for troubleshooting Created and pushed branch with all changes
tanyar09 added 1 commit 2026-01-23 14:00:43 -05:00
fix: support HTTPS proxy by using relative API paths
All checks were successful
CI / skip-ci-check (pull_request) Successful in 1m51s
CI / lint-and-type-check (pull_request) Successful in 2m32s
CI / python-lint (pull_request) Successful in 2m16s
CI / test-backend (pull_request) Successful in 4m11s
CI / build (pull_request) Successful in 4m59s
CI / secret-scanning (pull_request) Successful in 1m59s
CI / dependency-scan (pull_request) Successful in 1m58s
CI / sast-scan (pull_request) Successful in 3m7s
CI / workflow-summary (pull_request) Successful in 1m50s
70cfd63ca1
- 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).
tanyar09 merged commit 5b8e22d9d1 into dev 2026-01-23 14:04:32 -05:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ilia/punimtag#8
No description provided.