| Age | Commit message (Collapse) | Author |
|---|
|
1.6.3 is a recommended update. It may become a required update in the future.
- Added experimental proxy support for backend image server requests. This allows you to use a SOCKS (v4 or v5) or HTTP proxy if connectivity to the image servers is unreliable, which is mostly relevant in regions with heavy internet censorship.
This adds three arguments that can be passed on startup:
--image-proxy-host=<host> - hostname or IP address for the proxy
--image-proxy-type=<type> - can be "socks" or "http". defaults to "socks" if not provided
--image-proxy-port=<port> - the port of the proxy. defaults to 1080 for SOCKS and 8080 for HTTP if not provided
It does not support proxies that require authentication.
While it will technically work to use Tor as a SOCKS proxy, this should be avoided as Tor is too slow for this purpose.
- The currently selected RPC server will no longer reset when the server list is refreshed, as long as the current server is still in the list. This should make the --rpc-server-ip argument more useful.
- Improved reliability of reading HTTP request headers with some browser/locale combinations.
- Corrected a potential resource exhaustion issue.
|
|
|
|
1. A sanity check for certificate expiry has been added. If a client does not successfully refresh the certificate for whatever reason, it will now shut down gracefully 24 hours before the certificate actually expires instead of failing silently.
2. If the system time is off by more than 24 hours, a warning advising you to correct it will now be printed regularly. Failure to do so might make the certificate check trigger prematurely or fail to trigger at all.
3. During proxy requests, when a file is requested but not found in cache, the backend will now provide an alternative source link in addition to the primary one. If the client is unable to connect to the primary source, it will automatically fall back to the secondary one.
4. H@H now makes a best-effort attempt to include filesystem overhead for slack space in its cache size calculations. By default this calculation assumes a filesystem block size of 4kB which is by far the most common, adding an estimated overhead of 2 GB per 1 million files - roughly 0.5% for your average H@H cache.
https://forums.e-hentai.org/index.php?showtopic=234458
|
|
1. Standard content format.
2. Modify the content of the service unit and run it as the hath user.
3. Add hath.sysusers to deploy hath users and user groups.
4. Add hath.tmpfiles to deploy the folder structure required at runtime.
|
|
|
|
|