Hi Travis!
I've noticed recently (in the past week or so) that the poster_path in some of the requests of the movie search endpoint has the full path e.g. https://image.tmdb.org/t/p/w150//pes2HCVX60MNZZdUrKtgVNlv1ig.jpg
Because of this I am ending up with the following URI https://image.tmdb.org/t/p/w150/https://image.tmdb.org/t/p/w150//pes2HCVX60MNZZdUrKtgVNlv1ig.jpg
Any idea why? I'm not the only person having this issue.
Kan ’n rolprent of TV-program nie vind nie? Teken aan om dit te skep.
Wil u hierdie item gradeer of tot ’n lys toevoeg?
Nie ’n lid nie?
Antwoord deur Travis Bell
op 26 Oktober 2016 om 10:49 VM
Hi @tidusjar,
The app that runs the search service has no idea of the full image URL (it's not even added to that codebase) so that's not what's happening... how are you building your URLs? All of my tests show the standard file path being returned:
Etc, etc...
That image URL is definitely wrong and will of course error. I'd take a look at how you're building the URL, it looks like its doubling up somehow.