Closed GoogleCodeExporter closed 9 years ago
Could you tell us which Chrome version do you use and which web pages do not
work?
Original comment by jerzyglowacki
on 23 Dec 2014 at 11:07
Chrome Ver.: 39.0.2171.95 m
Page: http://www.alalam.ir/news/1659865
Original comment by kha...@gmail.com
on 23 Dec 2014 at 12:29
Same here. I'm on Windows 8.1 running Chrome: Version 39.0.2171.95 m (64-bit)
It seems instead of the proxy being auto-disabled like it did for a couple of
weeks when it didn't work, it's PRETENDING to be working by staying green, but
the data saved is zero.
Session Total
Original (KB) 7222.7 4954221.5
Received (KB) 7222.7 4142240.8
Savings (KB) 0.0 811980.7
Savings (%) 0.0 16.4
Original comment by jayz...@gmail.com
on 23 Dec 2014 at 7:18
As per Issue #5, the stats are unreliable and you should not count on them.
Always look at the Via header.
The web page you provided works for me in Chrome Stable 39.0.2171.95. Here are
the response headers (mind the Via header):
HTTP/1.1 200 OK
Accept-Ranges: bytes
Age: 472
Cache-Control: private,max-age=3185
Content-Encoding: gzip
Content-Length: 15673
Content-Type: text/html; charset=utf-8
Date: Sat, 27 Dec 2014 13:37:39 GMT
Etag: ""
Expires: Sat, 27 Dec 2014 14:33:30 GMT
Last-Modified: Sat, 27 Dec 2014 13:33:30 GMT
Server: Microsoft-IIS/7.5
Vary: Accept-Encoding
Via: WebCelerate, 1.1 Chrome-Compression-Proxy
X-Aspnet-Version: 4.0.30319
X-Cache: HIT
X-Cacheable: YES
X-Original-Content-Length: 15673
X-Powered-By: ASP.NET
Original comment by jerzyglowacki
on 27 Dec 2014 at 1:41
Ok so statistics not right, proxied sites does not work using it, how will we
know it's really working?
Original comment by kha...@gmail.com
on 27 Dec 2014 at 7:03
Just open Dev Tools, go to the Network tab and you will see WebP images instead
of JPEGs and response headers will contain "Via: 1.1 Chrome..." If the proxy is
working.
Original comment by jerzyglowacki
on 27 Dec 2014 at 8:02
Original issue reported on code.google.com by
kha...@gmail.com
on 23 Dec 2014 at 7:14Attachments: