Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Are you sure this is not specific to your browser?
Ok, i’ve just try with other browsers, and it seems that this problem happen “only” on Firefox and Chrome not in IE or Maxthon.
The problem it’s that in some plugin happen only with some image, like in this example: the image number 6 of this
https://wordpress.org/plugins/jetpack/screenshots/
or like in this, where the problem happen with all the images:
https://wordpress.org/plugins/buddypress/screenshots/
it’s very strange, because i tought it was a problem if they are JPEG/PNG but they are all in PNG..
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
yeah, you also have this problem or it’s only mine?
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Yes, maybe it’s the way the file was saved
Here’s your answer:
[alice@localhost ~]$ curl -I http://ps.w.org/jetpack/assets/screenshot-5.png
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: max-age=31536000
Content-Type: image/png
Date: Wed, 10 Dec 2014 13:03:24 GMT
Etag: "640145//jetpack/assets/screenshot-5.png"
Expires: Thu, 10 Dec 2015 13:03:24 GMT
Last-Modified: Sun, 16 Dec 2012 19:59:35 GMT
Server: Apache
Content-Length: 33269
[alice@localhost ~]$ curl -I http://ps.w.org/jetpack/assets/screenshot-6.png
HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Type: application/octet-stream
Date: Wed, 10 Dec 2014 13:03:43 GMT
Etag: "640145//jetpack/assets/screenshot-6.png"
Last-Modified: Sun, 16 Dec 2012 19:59:35 GMT
Server: Apache
Content-Length: 361672
The second is being served with the mime type application/octet-stream.
The server is apache, which usually does mime type based upon extension if served directly by apache – so something else within the wordpress install is actually serving the image and is screwing up the mime type on some occassions.
There’s probably a mod_rewrite directive that sends serving of the files to a script and the script is mis-identifying the file type in the second instance.
The etag is clearly not an etag generated by apache.
The etag looks to be generated by jetpack, so jetpack is probably what is serving the image, and responsible for fracking it up.
May not be jetpack but may be some kind of a caching plugin.
Whatever it is, that’s not an apache etag.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
It’s not a bug of WordPress.ORG, it is because the plugin author’s are uploading the images via the wrong mime type.
Give this a read, it explains what’s going on.
Plugin Screenshots Downloading?
The plugin authors can fix this easily enough and the post explains how to do that via SVN.
