3 ms·
I think you may have misunderstood the conclusion of the article and so hence my question: When requesting an image chrome sends: Accept:/ Accept-Encoding:gzi
by thomseddon 14y ago
I think you may have misunderstood the conclusion of the article and so hence my question: When requesting an image chrome sends:
Accept:/
Accept-Encoding:gzip,deflate,sdch
But if you abide by this and send it gzip'ed it fails...why?
- hobbit_longon 14y agoI'm not misunderstanding anything. Your very last point contains: "We still don’t quite understand why nobody sends gzip’ed images"
- thomseddon 14y agoQuite right, I have corrected that part of the conclusion, my question referred to the latter part, which I paraphrased above.
- hobbit_longon 14y agoYeah I was right, bitch.
- markhemmings 14y agoGood question. Why doesn't chrome decompress it when their header suggests they will? Yes it's unneeded and discouraged, but if developers do send gzipped content such as images (which as we all (including the blogger) know, they definitely shouldn't!) surely chrome should just go ahead and decompress it as normal?
- haldean 14y agoWhen the request is sent Chrome doesn't know the content type of the response, so it can't know that what it's requesting is an already-encrypted file.
- hobbit_longon 14y agoWho said anything about encryption?
- deleted 14y ago[deleted]