Hi,

I have no problem adding a pinging service to my web application to notify of webp content type.

From my last run (last week) I was able to find about 200+ webp images.

Here's the list in CVS:

http://pastebin.com/dt4JHAjR

Here's the same list but in JSON:

http://pastebin.com/F4YsZj4t

I just dumped this directly from laptop.

If you decide to add a new end-point can it support multiple images per post. It would lang my system to report each URL one at a time.

I'm definitely having this problem as well. I've come across the following images that all return image/webp even when image/jpeg is specifically requested.

https://image.tmdb.org/t/p/w342/225OXhGllrBJ6FWaYyiosxDU1us.jpg
https://image.tmdb.org/t/p/w342/2bdxzUBv6h6gFEcrTO4BUzkBIck.jpg
https://image.tmdb.org/t/p/w342/5740gUYGa18tb79VGj94UNmXZjH.jpg
https://image.tmdb.org/t/p/w342/86iGwYjAcVmrOoLCmU8vsrySoLj.jpg
https://image.tmdb.org/t/p/w342/8TAPuoephNAiRGgBobP4xQl0QGK.jpg
https://image.tmdb.org/t/p/w342/8cDeATXsU7LgLNRIKcL2QEwE8tv.jpg
https://image.tmdb.org/t/p/w342/A2w29kJOow5CYFDOZP5CNmelnEm.jpg
https://image.tmdb.org/t/p/w342/aU1PY270BTBUXwAZhgRR2TMUX4u.jpg
https://image.tmdb.org/t/p/w342/b4kKfthVn6V7U2GwJKiEDlDRgyp.jpg
https://image.tmdb.org/t/p/w342/ddskSEIu1B2PwodOzZNWB5YVQzq.jpg
https://image.tmdb.org/t/p/w342/dmNytzvQTjylI83qrgDoS1KQ0ev.jpg
https://image.tmdb.org/t/p/w342/hauipCFK2iybZqL1JqhdyakrZWO.jpg
https://image.tmdb.org/t/p/w342/hfyCKWEegVSEM40WTLGdJWAVqNU.jpg
https://image.tmdb.org/t/p/w342/hmNzppVQq9Qj8Ai8bLIseB5gY51.jpg
https://image.tmdb.org/t/p/w342/ip2IqmvCqFzvPe8RAHpT1My6XM9.jpg
https://image.tmdb.org/t/p/w342/j9vVQCSyNWvyBU6w9BxExZRlpZZ.jpg
https://image.tmdb.org/t/p/w342/j9xijFBmOSitYXAMnO9X9QXZogD.jpg
https://image.tmdb.org/t/p/w342/jZnaaqc8ngshtuKcqu44rArulHu.jpg
https://image.tmdb.org/t/p/w342/jkcTmZgEVJKWqDID1UJLnVYUgk0.jpg
https://image.tmdb.org/t/p/w342/kJMNRVHqJkumHNT1sW9geSj1m52.jpg
https://image.tmdb.org/t/p/w342/mIk2ferK0lPgTaiAfoI5KvHmUCz.jpg
https://image.tmdb.org/t/p/w342/mwWJuktWk8z5OY4og0z48Jg4u3n.jpg
https://image.tmdb.org/t/p/w342/ndmzaty5aaY6VVw4KtQpcdCHno.jpg
https://image.tmdb.org/t/p/w342/qmDpIHrmpJINaRKAfWQfftjCdyi.jpg
https://image.tmdb.org/t/p/w342/skp6h2el5rsaRmlzBhWZ6ZPyW2i.jpg
https://image.tmdb.org/t/p/w342/vHsNDq4FaNt4XGIjNxcB8fWtCSw.jpg
https://image.tmdb.org/t/p/w342/xhlXnzQRlDab04sUMVR9bzyDPpr.jpg
https://image.tmdb.org/t/p/w342/xz1p33UMrcPPOGP1vzlRwLVR6k0.jpg
https://image.tmdb.org/t/p/w342/yccgwPNVaqtgS1d0U5jjM6Mnza8.jpg
https://image.tmdb.org/t/p/w342/z6yhgEzGUJaBBgAxoyggRzwLnVM.jpg

For example:

curl.exe -I -L -H 'Accept: image/jpeg' https://image.tmdb.org/t/p/w342/225OXhGllrBJ6FWaYyiosxDU1us.jpg

HTTP/2 200
date: Fri, 24 Feb 2017 17:10:03 GMT
content-type: image/webp
content-length: 8058
set-cookie: __cfduid=de39e0e8faf5bc3c7b48e436f1f754e901487956203; expires=Sat, 24-Feb-18 17:10:03 GMT; path=/; domain=.tmdb.org; HttpOnly
access-control-allow-origin: *
cache-control: public, max-age=31449600
cf-bgj: imgq:85
cf-polished: qual=85, origFmt=jpeg, origSize=25409
content-disposition: inline; filename="225OXhGllrBJ6FWaYyiosxDU1us.webp"
etag: "e45dbc95e3db3dc81910a8dce55f3b8d"
expires: Fri, 23 Feb 2018 17:10:03 GMT
last-modified: Sat, 17 Dec 2016 10:22:16 GMT
vary: Accept
x-content-digest: 291ff0283b5a72c8a77dbcf0e324ce57fa14ac51
x-rack-cache: fresh
cf-cache-status: HIT
cf-ray: 3364875edfac5a92-BOS
accept-ranges: bytes
server: cloudflare-nginx

Hi @jeras Yes, this is a confirmed issue.

I'm hoping to find time to get the purge endpoint released later today.

Hey guys,

I ended up purging the entire cache, so if you try now, your should only be getting the proper jpeg assets neck now. The webp's should be completely purged.

Thank you!

I hope this didn't cost you extra CDN fees.

@thinkingmedia said:

Thank you!

I hope this didn't cost you extra CDN fees.

Oh it did! But we didn't really have much of a choice. This bug affected an unknown number of assets on an unknown number of edges. Cloudflare had no way of knowing which, so the only real option was to purge everything and start over.

@travisbell said:

Hey guys,

I ended up purging the entire cache, so if you try now, your should only be getting the proper jpeg assets neck now. The webp's should be completely purged.

Travis, thanks a lot! Looks like it really helped, now it responses by image/jpeg content-type on previous failed images.

@travisbell thanks a lot! Even my failed requests are working perfectly now!! I guess we can go ahead and close this issue?

You bet. Closed.