HandyCache форум

Basic implementation of Google's Data Compression Proxy.
The proxy only accept HTTP connection, so only HTTP request will be forwarder to Google's proxy.

Using md5 module from https://github.com/kikito/md5.lua.
Just put the module in lua/md5.lua.

Fixed save to cache.

Good afternoon. A small bugreport. Works only when an extension is added. After restarting the HC, the extension is turned on but it does not work, removing and installing the daw does not help, just the push of the reload button does not help. It only helps to remove the extension and re-add.
Добавлено: 24 Июнь 2017, 12:36:33

So with the expansion there were suspicions of the final page load. In the HC monitor, all connections are already closed, there are no pendants, and the browser still hanging the page load, hangs in 3-5 seconds. Without an extension, the same pages are loaded instantly.

I don't have a problem with extension load.
I do have a problem with page hanging tho. Not sure what happen.
Maybe there is some issue with HC and proxy keep-alive.
Try this.
Posted on: 25 June 2017, 05:29:57

Also try to change the proxy host. You can use the ip directly. Google have many server, try to nslookup with different dns server. Maybe you can find the faster one. Most of chrome mobile user enable the data saver. They can choke the server.

I found out the hanging is caused by HC try to repeat the request on error. Usually it is when loading favicon. HC doesn't show this repeated request in connection list when using external proxy, but print it in log window.
Set the repeat request on error in "Loading control" to 0 seems to fix the issue.

Updated to save webp to separated file.

A great script, but is it possible to filter in the script itself for compressible content? I'll explain. Make sure that only content that is compressed by Google is sent to the server. I see on the monitor that the script is trying to send there the ZIP file that I'm trying to download, the servers are disconnected and everything, I have to disable either the extension or the proxy in the browser

Not only zip file, but also large file can't be forwarded. There is obviously some rules applied on chrome, some of them is .php. I don't really know about all this rules. Its also check the availability through check.googlezip.net/connect or within the same persistent connection which is http/2. Doing all of that check would make a latency problem.
I propose to only forward most common compressible content.