friendlyhaser.blogg.se - Tinyproxy config

#Tinyproxy config full#

etc/tinyproxy/nf, /var/run/tinyproxy/tinyproxy.pid, /var/log/tinyproxy/tinyproxy.log Bugs The stat file template can be changed at runtime through the configuration variable StatFile. The stathost name defaults to tinyproxy.stats and can be changed at runtime to any name or IP address with the configuration variable StatHost. Tinyproxy returns a HTML page with connection statistics when it receives a HTTP request for a certain host - the stathost. "", then this is replaced by the value of the corresponding variable before delivery of the page. When Tinyproxy finds a variable name enclosed in braces, e.g. In addition, almost all templates support: detailĪ detailed, plain English explanation of the error and possible causes. The hostname of the client making the request.

The IP address of the client making the request. The abbreviated cause of the error condition. There are several standard HTML variables that are available in every template file: request The layout of both error pages and the statistics page can be controlled via configurable HTML template files that are plain HTML files that additionally understand a few template variables.

When a request for the stathost is made, a page summarizing the connection statistics is returned.

When an error occurred, a corresponding error page is returned.

There are two occasions when Tinyproxy delivers HTML pages to the client on it’s own right: This is usually done automatically after a certain number of connections have been handled. SIGHUPįorce Tinyproxy to do a garbage collection on the current connections linked list. In addition to command-line options, there are also several signals that can be sent to tinyproxy while it is running to generate debugging information and to force certain events.

hĭisplay a short help screen of command line arguments and exit. Tinyproxy accepts the following options: -c ĭon’t daemonize and stay in the foreground.

#Tinyproxy config full#

Designed from the ground up to be fast and yet small, it is an ideal solution for use cases such as embedded deployments where a full featured HTTP proxy is required, but the system resources for a larger proxy are unavailable. It listens on a given TCP port and handles HTTP proxy requests. Tinyproxy is a light-weight HTTP proxy daemon designed to consume a minimum amount of system resources. A light-weight HTTP proxy daemon Synopsis