tinyproxy(8) [debian man page]
TINYPROXY(8) Tinyproxy manual TINYPROXY(8) NAME
tinyproxy - A light-weight HTTP proxy daemon SYNOPSIS
tinyproxy [-vldch] DESCRIPTION
tinyproxy is a light-weight HTTP proxy daemon designed to consume a minimum amount of system resources. It listens on a given TCP port and handles HTTP proxy requests. 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. OPTIONS
tinyproxy accepts the following options: -c <config-file> Use an alternate configuration file. -d Don't daemonize and stay in the foreground. Useful for debugging purposes. -h Display a short help screen of command line arguments and exit. -l Display the licensing agreement. -v Display version information and exit. SIGNALS
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. SIGHUP Force Tinyproxy to do a garbage collection on the current connections linked list. This is usually done automatically after a certain number of connections have been handled. TEMPLATE FILES
There are two occasions when Tinyproxy delivers HTML pages to the client on it's own right: 1. When an error occurred, a corresponding error page is returned. 2. When a request for the stathost is made, a page summarizing the connection statistics is returned. (See STATHOST below.) 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. TEMPLATE VARIABLES
There are several standard HTML variables that are available in every template file: request The full HTTP request line. cause The abbreviated cause of the error condition. clientip The IP address of the client making the request. clienthost The hostname of the client making the request. version The version of Tinyproxy. package The package name. Presently, resolves to tinyproxy. date The current date/time in HTTP format. In addition, almost all templates support: detail A detailed, plain English explanation of the error and possible causes. When Tinyproxy finds a variable name enclosed in braces, e.g. "{request}", then this is replaced by the value of the corresponding variable before delivery of the page. STATHOST
Tinyproxy returns a HTML page with connection statistics when it receives a HTTP request for a certain host -- the stathost. The stathost name defaults to tinyproxy.stats and can be changed at runtime to any name or IP address with the configuration variable StatHost. The stat file template can be changed at runtime through the configuration variable StatFile. FILES
/etc/tinyproxy/tinyproxy.conf, /var/run/tinyproxy/tinyproxy.pid, /var/log/tinyproxy/tinyproxy.log BUGS
To report bugs in Tinyproxy, please visit <https://www.banu.com/tinyproxy/>. SEE ALSO
tinyproxy.conf(5) AUTHOR
Written by the Tinyproxy project team. COPYRIGHT
Copyright (c) 1998-2000 Steven Young; Copyright (c) 2000-2001 Robert James Kaes; Copyright (c) 2009-2010 Mukund Sivaraman; Copyright (c) 2009-2010 Michael Adam. This program is distributed under the terms of the GNU General Public License version 2 or above. See the COPYING file for additional information. Version 1.8.3 09/30/2012 TINYPROXY(8)
Check Out this Related Man Page
XMLRPC::Transport::HTTP(3) User Contributed Perl Documentation XMLRPC::Transport::HTTP(3) NAME
XMLRPC::Transport::HTTP - Server/Client side HTTP support for XMLRPC::Lite SYNOPSIS
Client use XMLRPC::Lite proxy => 'http://localhost/', # proxy => 'http://localhost/cgi-bin/xmlrpc.cgi', # local CGI server # proxy => 'http://localhost/', # local daemon server # proxy => 'http://login:password@localhost/cgi-bin/xmlrpc.cgi', # local CGI server with authentication ; print getStateName(1); CGI server use XMLRPC::Transport::HTTP; my $server = XMLRPC::Transport::HTTP::CGI -> dispatch_to('methodName') -> handle ; Daemon server use XMLRPC::Transport::HTTP; my $daemon = XMLRPC::Transport::HTTP::Daemon -> new (LocalPort => 80) -> dispatch_to('methodName') ; print "Contact to XMLRPC server at ", $daemon->url, " "; $daemon->handle; DESCRIPTION
This class encapsulates all HTTP related logic for a XMLRPC server, independent of what web server it's attached to. If you want to use this class you should follow simple guideline mentioned above. PROXY SETTINGS You can use any proxy setting you use with LWP::UserAgent modules: XMLRPC::Lite->proxy('http://endpoint.server/', proxy => ['http' => 'http://my.proxy.server']); or $xmlrpc->transport->proxy('http' => 'http://my.proxy.server'); should specify proxy server for you. And if you use "HTTP_proxy_user" and "HTTP_proxy_pass" for proxy authorization SOAP::Lite should know how to handle it properly. COOKIE-BASED AUTHENTICATION use HTTP::Cookies; my $cookies = HTTP::Cookies->new(ignore_discard => 1); # you may also add 'file' if you want to keep them between sessions my $xmlrpc = XMLRPC::Lite->proxy('http://localhost/'); $xmlrpc->transport->cookie_jar($cookies); Cookies will be taken from response and provided for request. You may always add another cookie (or extract what you need after response) with HTTP::Cookies interface. You may also do it in one line: $xmlrpc->proxy('http://localhost/', cookie_jar => HTTP::Cookies->new(ignore_discard => 1)); COMPRESSION XMLRPC::Lite provides you option for enabling compression on wire (for HTTP transport only). Both server and client should support this capability, but this logic should be absolutely transparent for your application. Server will respond with encoded message only if client can accept it (client sends Accept-Encoding with 'deflate' or '*' values) and client has fallback logic, so if server doesn't understand specified encoding (Content-Encoding: deflate) and returns proper error code (415 NOT ACCEPTABLE) client will repeat the same request not encoded and will store this server in per-session cache, so all other requests will go there without encoding. Having options on client and server side that let you specify threshold for compression you can safely enable this feature on both client and server side. Compression will be enabled on client side IF: threshold is specified AND size of current message is bigger than threshold AND module Compress::Zlib is available. Client will send header 'Accept-Encoding' with value 'deflate' if threshold is specified AND module Compress::Zlib is available. Server will accept compressed message if module Compress::Zlib is available, and will respond with compressed message ONLY IF: threshold is specified AND size of current message is bigger than threshold AND module Compress::Zlib is available AND header 'Accept-Encoding' is presented in request. DEPENDENCIES
Crypt::SSLeay for HTTPS/SSL HTTP::Daemon for XMLRPC::Transport::HTTP::Daemon Apache, Apache::Constants for XMLRPC::Transport::HTTP::Apache SEE ALSO
See ::CGI, ::Daemon and ::Apache for implementation details. See examples/XMLRPC/* for examples. COPYRIGHT
Copyright (C) 2000-2001 Paul Kulchenko. All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. AUTHOR
Paul Kulchenko (paulclinger@yahoo.com) perl v5.12.1 2010-03-18 XMLRPC::Transport::HTTP(3)