brjackbauer / datacompressionproxy

Automatically exported from code.google.com/p/datacompressionproxy
0 stars 0 forks source link

Not Working #36

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I have it on but not working
1- no compression is registered
2- cannot access some locally restricted sites (I usually could access these 
sites with same extension few weeks ago, and still can access these sites using 
data compression proxy on my android using same wifi)

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by kha...@gmail.com on 23 Dec 2014 at 7:14

Attachments:

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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