Hello,
I've noticed that certain movie posters are being returned as WebP instead of jpg although thats what the URL is requesting. This happens specifically in the w500 size. Some Examples
Rings 3 https://image.tmdb.org/t/p/w500/bbxtz5V0vvnTDA2qWbiiRC77Ok9.jpg John Wick: Chapter 2 https://image.tmdb.org/t/p/w500/zkXnKIwX5pYorKJp2fjFSfNyKT0.jpg Resident Evil The Final Chapter https://image.tmdb.org/t/p/w500/7XlaaMzQUz5EqTY0m07hn3PbGu7.jpg Kong: Skull Island https://image.tmdb.org/t/p/w500/aoUyphk4nwffrwlZRaOa0eijgpr.jpg
[Edited] I've also noticed that this happens in the w780 size also for a few movies like this Beauty and the Beast https://image.tmdb.org/t/p/w780/b9QJr2oblOu1grgOMUZF1xkUJdh.jpg La La Land https://image.tmdb.org/t/p/w780/ylXCdC106IKiarftHkcacasaAcb.jpg Arrival https://image.tmdb.org/t/p/w780/hLudzvGfpi6JlwUnsNhXwKKg4j.jpg
[Edited] This also seems to happen for movies in the w342 sizes like these Rock Dog https://image.tmdb.org/t/p/w342/1RSPgm5AzLv7BYEZSYXJsOM3eRZ.jpg Lion https://image.tmdb.org/t/p/w342/dVrpKogkQCNgRjvWrXqW4ZGmPjB.jpg The Salesman https://image.tmdb.org/t/p/w342/55yxwuTsbbmYuUQVdvnE7kVlsS4.jpg Ezra https://image.tmdb.org/t/p/w342/9HqpA6EvX9Ua8bxSpsMxCZgagBR.jpg The Last Face https://image.tmdb.org/t/p/w342/i0l3FWzQNe48TYhy4dPVsexigF4.jpg Rings 3 https://image.tmdb.org/t/p/w342/bbxtz5V0vvnTDA2qWbiiRC77Ok9.jpg
Can this be fixed?
Can't find a movie or TV show? Login to create it.
Want to rate or add this item to a list?
Not a member?
Reply by Mathew Foscarini
on February 18, 2017 at 6:21 PM
How do you tell if it's WebP?
I'm opening the images in Chrome, but can't see how to tell it's not jpeg.
Reply by Travis Bell
on February 18, 2017 at 8:00 PM
Our CDN should only be sending the webp versions if you're requesting them. Chrome is really the only popular client in the world today that will request webp by default though. In any case, this can be illustrated by looking at these 3 cURL requests (first one is webp, the last 2 are both JPEG's):
Content type: image/webp
Content type: image/jpeg
Content type: image/jpeg
Reply by letss
on February 19, 2017 at 1:29 AM
@travisbell Thanks for replying. Our requests are not matching. When I try the requests you've mentioned above that are supposed to return jpeg, they all return webp to me. I'm trying this url: https://image.tmdb.org/t/p/w500/bbxtz5V0vvnTDA2qWbiiRC77Ok9.jpg
When I try a request without any Headers
You can see that both requests are returning WebP. I'm using safari's JS engine and I guess it is making requests without any headers (unfortunately I can't confirm this) but in all cases it is returning WebP for me. Is it because of the Dubai region of your CDN that is behaving this way?
PS: I am unable to format the curl response as code? How did you do it ?
Reply by LucusNon
on February 19, 2017 at 2:32 AM
@letss::
@dormouse7 told me how to make a code-block:
Start with a line of 3 consecutive backquote
(a.k.a. backtick, a.k.a. "grave accent") characters: ```
followed by the code you want to display,
followed by another line of 3 backquote characters.
Example:
```
... code here ...
```
Result:
(Note: Another way is to use HTML <pre>...</pre> tags.
But there is a problem with that method in some cases
when the code that we want to display contains HTML tags.
So, the backtick method seems to be the more reliable way.)
Reply by letss
on February 19, 2017 at 6:44 AM
@LucusNon thanks for your help. I was placing the code on the same line as the back-tick. Let me try and format my comment above to be more readable
Reply by LucusNon
on February 19, 2017 at 7:39 AM
@letss:
Oops! Due to an unfortunate limitation of the quote-function,
your quotation corrupted my examples and text (not your fault).
To anyone reading the above:
Please refer to the examples in my original reply above,
not the corrupted quoted version in the reply from @letss.
Reply by Travis Bell
on February 19, 2017 at 12:29 PM
@thinkingmedia @letss I'll submit a support ticket to our CDN. This should not be happening. I will update this thread when I have an update.
Reply by temptsr
on February 20, 2017 at 6:58 AM
Hi, i've got the same problem:
The problem detected at Moscow region (russia). @travisbell do I need to provide any additional information for considering my issue too?
Reply by Travis Bell
on February 20, 2017 at 8:39 AM
I've just heard back from Cloudflare about this, they confirmed a bug on their side and advised me to disable webp until they figure out what's going on.
You should see these requests start working properly in the next 10 or so minutes.
Thanks for your patience guys!
Reply by letss
on February 20, 2017 at 9:52 PM
@travisbell thanks for your help! But unfortunately the requests are still returning webp. Did something not work in turning off webp?
Reply by Travis Bell
on February 20, 2017 at 10:04 PM
Not sure, they said disabling it should stop it completely. Can you give me a cURL request like one above for an image that is still returning webp?
Reply by temptsr
on February 21, 2017 at 3:04 AM
Reply by letss
on February 21, 2017 at 3:33 AM
@temptsr @travisbell interestingly even if you specifically accept only image/jpg, it still only returns image/webp
Reply by temptsr
on February 23, 2017 at 4:53 AM
@travisbell Hi!
Do you have any news about the problem? It's still continue to return webp content-type format :(
Reply by Travis Bell
on February 23, 2017 at 11:07 AM
Only that the ones stuck returning webp are stuck for good. The only solution we have is to purge the entire cache but we don't have the resources to do that (it would cost us a small fortune to do this, it's pretty much a hard not going to happen).
The best option I can come up with is to build a little end point for you guys to submit the URL of bad images as you come across them to purge the files individually. Cloudflare has no way of purging by content type or by edge (we could have in theory rolled each edge to limit our origin traffic).
I don't know when I'll have time for this but I'll try today/tomorrow. Thanks for your patience.