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.

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):

curl -I -L -H "Accept: image/webp,image/*,*/*;q=0.8" "https://image.tmdb.org/t/p/w500_and_h281_bestv2/zYFQM9G5j9cRsMNMuZAX64nmUMf.jpg"

Traviss-iMac:~ travisbell$ curl -I -L -H "Accept: image/webp,image/*,*/*;q=0.8" "https://image.tmdb.org/t/p/w500_and_h281_bestv2/zYFQM9G5j9cRsMNMuZAX64nmUMf.jpg"
HTTP/1.1 200 OK
Date: Sun, 19 Feb 2017 00:58:52 GMT
Content-Type: image/webp
Content-Length: 24624
Connection: keep-alive
Set-Cookie: __cfduid=ddc737631787344be1df8a4f2aaf127141487465932; expires=Mon, 19-Feb-18 00:58:52 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=59557
Content-Disposition: inline; filename="zYFQM9G5j9cRsMNMuZAX64nmUMf.webp"
Etag: "806c9841ad78d6cefff4ecdfa0741c72"
Expires: Sun, 18 Feb 2018 00:58:52 GMT
Last-Modified: Sat, 17 Dec 2016 01:19:38 GMT
Vary: Accept
X-Content-Digest: e265659a24ff25126afdbcf2dc1aa27f9f765d3a
X-Rack-Cache: fresh
CF-Cache-Status: HIT
Accept-Ranges: bytes
Server: cloudflare-nginx
CF-RAY: 3335c5db4ed10c4d-SEA

Content type: image/webp

curl -I -L -H "Accept: image/*,*/*;q=0.8" "https://image.tmdb.org/t/p/w500_and_h281_bestv2/zYFQM9G5j9cRsMNMuZAX64nmUMf.jpg"

Traviss-iMac:~ travisbell$ curl -I -L -H "Accept: image/*,*/*;q=0.8" "https://image.tmdb.org/t/p/w500_and_h281_bestv2/zYFQM9G5j9cRsMNMuZAX64nmUMf.jpg"
HTTP/1.1 200 OK
Date: Sun, 19 Feb 2017 00:58:21 GMT
Content-Type: image/jpeg
Content-Length: 31240
Connection: keep-alive
Set-Cookie: __cfduid=d010cb7cca38baa6da87a94e3bd05f8761487465901; expires=Mon, 19-Feb-18 00:58:21 GMT; path=/; domain=.tmdb.org; HttpOnly
Access-Control-Allow-Origin: *
Cache-Control: public, max-age=31449600
Cf-Bgj: imgq:85
Cf-Polished: degrade=85, origSize=59557
Etag: "806c9841ad78d6cefff4ecdfa0741c72"
Expires: Sun, 18 Feb 2018 00:58:21 GMT
Last-Modified: Sat, 17 Dec 2016 01:19:38 GMT
Vary: Accept
X-Content-Digest: e265659a24ff25126afdbcf2dc1aa27f9f765d3a
X-Rack-Cache: fresh
CF-Cache-Status: HIT
Accept-Ranges: bytes
Server: cloudflare-nginx
CF-RAY: 3335c51d1b572a25-SEA

Content type: image/jpeg

curl -I -L "https://image.tmdb.org/t/p/w500_and_h281_bestv2/zYFQM9G5j9cRsMNMuZAX64nmUMf.jpg"

Traviss-iMac:~ travisbell$ curl -I -L "https://image.tmdb.org/t/p/w500_and_h281_bestv2/zYFQM9G5j9cRsMNMuZAX64nmUMf.jpg"
HTTP/1.1 200 OK
Date: Sun, 19 Feb 2017 00:57:18 GMT
Content-Type: image/jpeg
Content-Length: 31240
Connection: keep-alive
Set-Cookie: __cfduid=dc121324f394ee429094048650b63a0b91487465838; expires=Mon, 19-Feb-18 00:57:18 GMT; path=/; domain=.tmdb.org; HttpOnly
Access-Control-Allow-Origin: *
Cache-Control: public, max-age=31449600
Cf-Bgj: imgq:85
Cf-Polished: degrade=85, origSize=59557
Etag: "806c9841ad78d6cefff4ecdfa0741c72"
Expires: Sun, 18 Feb 2018 00:57:18 GMT
Last-Modified: Sat, 17 Dec 2016 01:19:38 GMT
Vary: Accept
X-Content-Digest: e265659a24ff25126afdbcf2dc1aa27f9f765d3a
X-Rack-Cache: fresh
CF-Cache-Status: HIT
Accept-Ranges: bytes
Server: cloudflare-nginx
CF-RAY: 3335c3922eaa1bd3-SEA

Content type: image/jpeg

@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

curl -I -L -H "Accept: image/*,*/*;q=0.8" "https://image.tmdb.org/t/p/w500/bbxtz5V0vvnTDA2qWbiiRC77Ok9.jpg"

HTTP/1.1 200 OK
Date: Sun, 19 Feb 2017 06:27:57 GMT
Content-Type: image/webp
Content-Length: 71976
Connection: keep-alive
Set-Cookie: __cfduid=d962eae09efc2ee22195508434763df0e1487485677; expires=Mon, 19-Feb-18 06:27:57 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=155014
Content-Disposition: inline; filename="bbxtz5V0vvnTDA2qWbiiRC77Ok9.webp"
Etag: "ff516d5c87f567d6fea335664cd0efa1"
Expires: Sun, 18 Feb 2018 06:27:57 GMT
Last-Modified: Fri, 03 Feb 2017 17:46:55 GMT
Vary: Accept
X-Content-Digest: 798ba3f141ff73bd7051a113260f00e86509e278
X-Rack-Cache: fresh
CF-Cache-Status: HIT
CF-RAY: 3337a7edd84428f0-DXB
Accept-Ranges: bytes
Server: cloudflare-nginx

When I try a request without any Headers

 curl -I -L "https://image.tmdb.org/t/p/w500/bbxtz5V0vvnTDA2qWbiiRC77Ok9.jpg"

HTTP/1.1 200 OK
Date: Sun, 19 Feb 2017 06:28:21 GMT
Content-Type: image/webp
Content-Length: 71976
Connection: keep-alive
Set-Cookie: __cfduid=d19d2dda9f87ba3ec138ce6edf5570b1f1487485701; expires=Mon, 19-Feb-18 06:28:21 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=155014
Content-Disposition: inline; filename="bbxtz5V0vvnTDA2qWbiiRC77Ok9.webp"
Etag: "ff516d5c87f567d6fea335664cd0efa1"
Expires: Sun, 18 Feb 2018 06:28:21 GMT
Last-Modified: Fri, 03 Feb 2017 17:46:55 GMT
Vary: Accept
X-Content-Digest: 798ba3f141ff73bd7051a113260f00e86509e278
X-Rack-Cache: fresh
CF-Cache-Status: HIT
CF-RAY: 3337a88089ee28de-DXB
Accept-Ranges: bytes
Server: cloudflare-nginx

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 ?

@letss::

... I am unable to format the curl response as code?

@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:

... code here ...   

(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.)

@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

@LucusNon said:

@letss::

... I am unable to format the curl response as code?

@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:

... code here ...   

(Note:  Another way is to use HTML 

...

  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.)

@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.

@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.

@travisbell said:

@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.

Hi, i've got the same problem:

curl -I -L -H "Accept: image/*,*/*;q=0.8" "https://image.tmdb.org/t/p/w342/bQRtd0rc175c3RiJ2VKEWOgNXyD.jpg"

HTTP/1.1 200 OK
Date: Mon, 20 Feb 2017 11:42:13 GMT
Content-Type: image/webp
Content-Length: 42872
Connection: keep-alive
Set-Cookie: __cfduid=d550ac425b51839a312fef403aff1ba441487590933; expires=Tue, 20-Feb-18 11:42:13 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=64418
Content-Disposition: inline; filename="bQRtd0rc175c3RiJ2VKEWOgNXyD.webp"
Etag: "d237c85fe72595e2b8f545f56bf29747"
Expires: Mon, 19 Feb 2018 11:42:13 GMT
Last-Modified: Thu, 16 Feb 2017 16:29:22 GMT
Vary: Accept
X-Content-Digest: 3e17873c7a8bc2c7d9f49ec80fc4a01cea36de49
X-Rack-Cache: miss, store
CF-Cache-Status: HIT
CF-RAY: 3341b1a6d8d94e06-DME
Accept-Ranges: bytes
Server: cloudflare-nginx

The problem detected at Moscow region (russia). @travisbell do I need to provide any additional information for considering my issue too?

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!

@travisbell thanks for your help! But unfortunately the requests are still returning webp. Did something not work in turning off webp?

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?

@travisbell said:

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?

curl -I -L -H "Accept: image/*,*/*;q=0.8" "https://image.tmdb.org/t/p/w342/bQRtd0rc175c3RiJ2VKEWOgNXyD.jpg"

HTTP/1.1 200 OK
Date: Tue, 21 Feb 2017 07:54:56 GMT
Content-Type: image/webp
Content-Length: 42872
Connection: keep-alive
Set-Cookie: __cfduid=d9384e9ab0dd7a301f63a55416f2327f41487663696; expires=Wed, 21-Feb-18 07:54:56 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=64418
Content-Disposition: inline; filename="bQRtd0rc175c3RiJ2VKEWOgNXyD.webp"
Etag: "d237c85fe72595e2b8f545f56bf29747"
Expires: Tue, 20 Feb 2018 07:54:56 GMT
Last-Modified: Thu, 16 Feb 2017 16:29:22 GMT
Vary: Accept
X-Content-Digest: 3e17873c7a8bc2c7d9f49ec80fc4a01cea36de49
X-Rack-Cache: miss, store
CF-Cache-Status: HIT
CF-RAY: 3348a2146f2a4f38-DME
Accept-Ranges: bytes
Server: cloudflare-nginx

@temptsr @travisbell interestingly even if you specifically accept only image/jpg, it still only returns image/webp

curl -I -L -H "Accept: image/jpg" "https://image.tmdb.org/t/p/w500/bbxtz5V0vvnTDA2qWbiiRC77Ok9.jpg"

HTTP/1.1 200 OK
Date: Tue, 21 Feb 2017 08:32:34 GMT
Content-Type: image/webp
Content-Length: 71976
Connection: keep-alive
Set-Cookie: __cfduid=d32c337b827b7b724d511f57e97ed911d1487665954; expires=Wed, 21-Feb-18 08:32:34 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=155014
Content-Disposition: inline; filename="bbxtz5V0vvnTDA2qWbiiRC77Ok9.webp"
Etag: "ff516d5c87f567d6fea335664cd0efa1"
Expires: Tue, 20 Feb 2018 08:32:34 GMT
Last-Modified: Fri, 03 Feb 2017 17:46:55 GMT
Vary: Accept
X-Content-Digest: 798ba3f141ff73bd7051a113260f00e86509e278
X-Rack-Cache: fresh
CF-Cache-Status: HIT
CF-RAY: 3348d935896328f0-DXB
Accept-Ranges: bytes
Server: cloudflare-nginx

@travisbell Hi!

Do you have any news about the problem? It's still continue to return webp content-type format :(

curl -I -L "https://image.tmdb.org/t/p/w342/bQRtd0rc175c3RiJ2VKEWOgNXyD.jpg"
HTTP/1.1 200 OK
Date: Thu, 23 Feb 2017 09:52:15 GMT
Content-Type: image/webp
Content-Length: 42872
Connection: keep-alive
Set-Cookie: __cfduid=d2c7a26c632b541919449a0e56d3723f71487843535; expires=Fri, 23-Feb-18 09:52:15 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=64418
Content-Disposition: inline; filename="bQRtd0rc175c3RiJ2VKEWOgNXyD.webp"
Etag: "d237c85fe72595e2b8f545f56bf29747"
Expires: Thu, 22 Feb 2018 09:52:15 GMT
Last-Modified: Thu, 16 Feb 2017 16:29:22 GMT
Vary: Accept
X-Content-Digest: 3e17873c7a8bc2c7d9f49ec80fc4a01cea36de49
X-Rack-Cache: miss, store
CF-Cache-Status: HIT
CF-RAY: 3359c8b37be04ed2-DME
Accept-Ranges: bytes
Server: cloudflare-nginx

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.