2025-01-24, 06:10 PM
(This post was last modified: 2025-01-24, 06:23 PM by theguymadmax. Edited 2 times in total.)
(2025-01-24, 05:58 PM)rkulagow Wrote:(2025-01-24, 02:59 PM)TheDreadPirate Wrote: My understanding of that error is that the client tried to retrieve an image from the server, but the server didn't have one.
(I'm the SchedulesDirect JSON service developer)
That particular image ("9b398ced31be09445ec12974e0e3b4a193d9134d5038ff99a310bfb71c893449.jpg") does exist on our servers; you can generate a token and retrieve it by using the URL that's in the error message.
If you do retrieve it, it's showing the cast of "WaPo Bodensee"
So the image not existing on our side isn't the cause of the warning message.
Thanks for clarifying that point.
That pre-cache warning happens when the system can't read the Content-Type header of the file to determine its image type. This issue also affects other guide data images. There is now a fallback mechanism that uses the file's URL extension to determine the image type, which is available in the master branch. You can find the relevant PR I linked above.