EDIT: My question was in reference to the latter part of the final conclusion, Chrome sends:
Accept:/ Accept-Encoding:gzip,deflate,sdch
But doesn't actually support it. Thanks to hobbit_longon for help pointing out the error in the final point.
I guess the browsers figure it's not worth building in support for a feature that's rarely used and creates a sub-optimal UX.
That's not why, that's just a reason why doing so is silly.
> the gzip algorithm isn't optimised as well for images as say, jpeg.
gzip is used in PNG.
Read the article; the reason is because he wasn't sending gzip data, just deflate data.
You want to know why people don't gzip their images? What benefit do you think you get from gziping a jpeg or png stream? Why were you trying it in the first place?
Accept:/
Accept-Encoding:gzip,deflate,sdch
But if you abide by this and send it gzip'ed it fails...why?
"We still don’t quite understand why nobody sends gzip’ed images"
The author wrote up his thoughts as a blog post and took the time to submit it looking for help understanding an issue.
You were unnecessarily rude and condescending in your response. I'm only bringing this up because your account is new. If you're going to take the time to create an account to reply to a post, why would you create an account just to leave this comment?
Read his response again. The author is asking why, if Chrome does not support gzipped images, it sends "Accept:/ Accept-Encoding:gzip,deflate,sdch" (in other words it states that it will accept any Gzipped content). This is the question no one in this thread is actually answering, instead choosing to nitpick on why the author tried to do something.
Also, calling someone an idiot because they lack understanding of a certain field in computer science? Really? Maybe you should lighten up.