Soporte de The Movie Database
Soporte → Soporte de API
image corrupt or truncated.
publicado por tlm2408STAFFMOD el 15 de febrero de 2024 a las 04:32
I have been using the tmdb api for years, but lately (the last month or so) I am getting image corrupt or truncated messages in Firefox 122 console. I also get "blocked by DevTools" errors . In the network tab I get "NS_ERROR_NET_PARTIAL_TRANSFER".
Some images are loaded and I can see them on my page, but are giving me this error, while others are just white with the same error. If I reload the image it loads fine.
This is the image URL path I'm using:
https://image.tmdb.org/t/p/w500/
This is an example of the URL I'm using (also happens with similar and recommended):
https://api.themoviedb.org/3/discover/tv?api_key=KEY&language=en-US&sort_by=first_air_date.desc&page=1&include_null_first_air_dates=false&first_air_date_year=2024&with_genres=10759
Any help would be greatly appreciated.
Contestado por Travis Bell
el 15 de febrero de 2024 a las 11:05
Hi @tlm2408,
Does this problem only happen with Firefox?
Contestado por tlm2408
el 16 de febrero de 2024 a las 01:30
It seems to. I only have Firefox and Microsoft Edge. Edge works okay.
Contestado por tlm2408
el 20 de febrero de 2024 a las 05:24
Hi @travisbell,
Do you have any idea what the problem may be?
Contestado por Travis Bell
el 20 de febrero de 2024 a las 13:16
Hi @tlm2408,
Unfortunately, I do not. Googling this error doesn't yield much either.
One thing I just noticed is that mentioned the image URL you're using is
https://image.tmdb.org/t/p/w500/, which has a trailing slash. And while I don't personally see any issues with that, since all of our image paths have a slash prefixed, you might be building this URL:https://image.tmdb.org/t/p/w500//fbbj3viSUDEGT1fFFMNpHP1iUjw.jpg
Contestado por Travis Bell
el 20 de febrero de 2024 a las 13:16
Hi @tlm2408,
Unfortunately, I do not. Googling this error doesn't yield much either.
One thing I just noticed is that mentioned the image URL you're using is
https://image.tmdb.org/t/p/w500/, which has a trailing slash. And while I don't personally see any issues with that, since all of our image paths have a slash prefixed, you might be building this URL:When it really should be:
Does that make any difference?
Contestado por tlm2408
el 21 de febrero de 2024 a las 00:17
@travisbell,
Yeah, I noticed the incorrect path too when I was going over my code and fixed it, but it didn't fix the problem. I have searched for an answer and came up blank as well. I'll keep trying and if I find a solution I'll post it here. It seems to be intermittent. I've been checking for the last hour and there were no problems, but now it's started playing up again. Thank you for your time.