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
- 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).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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