Skip to content

Fix: use image proxy for external logos in admin and guide modules to prevent mixed content issues on HTTPS deployments - #114

Open
ashishraj09 wants to merge 2 commits into
ardoviniandrea:mainfrom
ashishraj09:fix/image-proxy-mixed-content-admin-guide
Open

ashishraj09 wants to merge 2 commits into
ardoviniandrea:mainfrom
ashishraj09:fix/image-proxy-mixed-content-admin-guide

Conversation

@ashishraj09

Copy link
Copy Markdown

Updated the admin and guide modules to always use the backend image proxy for external (http/https) channel logos and posters.

This prevents mixed content errors when the site is served over HTTPS, ensuring all images load securely.
Local or relative image paths are not proxied, so internal assets continue to load directly.

The fix applies to all places where channel logos are rendered in the admin dashboard (live activity, watch history) and the TV guide.

This makes the frontend robust for HTTPS deployments and improves compatibility with external sources.

… prevent mixed content issues on HTTPS deployments
@ashishraj09
ashishraj09 force-pushed the fix/image-proxy-mixed-content-admin-guide branch from 3eb38d7 to f9b42bf Compare February 1, 2026 03:08
- Change DATA_DIR and DVR_DIR to use env vars with local fallbacks
- Add DATA_DIR and DVR_DIR environment variables to Dockerfile
- Add redirect following (301/302/307/308) to image proxy
- Add User-Agent header to image proxy for Wikipedia/CDN compatibility
- Add .gitignore for node_modules, data/, dvr/, and common files
@Sellierm

Copy link
Copy Markdown

Seems legit,
would be nice to have that pull request merged !

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.

2 participants