-
-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/avatarproxy prefer hostname/ip address over external url if provided #1012
Comments
I just re-read this, |
This is how the avatar is loaded. It'd be nice to prefer the hostname if provided. In my case the tld is not resolvable (IPv6).
|
I dont use jellyfin but plex and its the same issue |
🎉 This issue has been resolved in version 2.0.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
* fix: rewrite avatarproxy and CachedImage Avatar proxy was allowing every request to be proxied, no matter the original ressource's origin or filetype. This PR fixes it be allowing only relevant resources to be cached, i.e. Jellyfin/Emby images and TMDB images. fix Fallenbagel#1012, Fallenbagel#1013 * fix: resolve CodeQL error * fix: resolve CodeQL error * fix: resolve review comments * fix: resolve review comment * fix: resolve CodeQL error * fix: update imageproxy path
Description
The user avatar in Jellyfin is retrieved from the path
/avatarproxy/jellyfin.domain.com
Desired Behavior
The user avatar can be retrieved from the hostname/IP address using the following path:
/avatarproxy/http://hostname:port
Additional Context
Tested the path using
/avatarproxy/http://jellyfin:8096/...
for Jellyfin user avatar and it works. This was not an issue in v1.19.2Code of Conduct
The text was updated successfully, but these errors were encountered: