Closed GoogleCodeExporter closed 9 years ago
Stats not shown do not mean that the compression is not working. I am using
Chrome 35.0.1916.27 and it works, I can see the "via: 1.1 Chrome Compression
Proxy" response header in Network tab in Chrome Developer Tools. Could you
please verify that you see the Via header?
Original comment by jerzyglowacki
on 14 May 2014 at 12:43
Weird, I put lots of info on this but it was removed. In summary I chose a
random imgur.com picture and downloaded it with and without the proxy. The
picture was half the size roughly when the proxy was on and opening the picture
in notepad++ showed it was the new JPEG format.
Also using a bandwidth meter showed that I was using roughly half the
bandwidth, but the chrome://net-internals/#bandwidth page showed no savings as
per below
Session Total
Original (KB) 3648.7 5922444.2
Received (KB) 3648.7 5922444.2
Savings (KB) 0.0 0.0
Savings (%) 0.0 0.0
I am using Windows 8.1 x64 and Chrome Version 34.0.1847.137 m
So the proxy is saving bandwidth, but since no stats are showing I expect
people will probably give up and turn it off...
Original comment by ty...@mango.net.nz
on 19 May 2014 at 11:25
I found my comment in the following bug listed as will not fix as per comments
"I can confirm DCP works in Chrome 35.0.1916.27 even if the stats are missing.
Sorry, but there is nothing I can do with them. You have to file the Chromium
bug if the lack of stats makes you sad."
https://code.google.com/p/datacompressionproxy/issues/detail?id=5&can=1
I have no idea how to report this to Chromium but this issue seems to be
repeating.
I did further testing, and it appears a problem with the statistics page which
while 'cosmetic' will put a lot of people off as it appears not to be working.
I used this test page (Home make snickers bars.) http://imgur.com/gallery/qrSFf
Here are the results
OFF Total Data Transferred 0.97 MB
ON Total Data Transferred 495 KB
Also I saved the top image in both modes to my desktop and opened in Notepad++
and confirmed the Compressed one was a WEBPVP8 format (which still saved as
.jpeg but nothing except chrome would open it.)
The original file was a JFIF from the headers.
Original comment by ty...@mango.net.nz
on 19 May 2014 at 11:29
It is a Chromium bug: https://code.google.com/p/chromium/issues/detail?id=374768
Original comment by jerzyglowacki
on 19 May 2014 at 12:55
Original issue reported on code.google.com by
pavelp...@gmail.com
on 13 May 2014 at 11:14