mod_proxy
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Mod proxy" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Mod proxy|concern=All citations resolve to the same first-party domain. No third party coverage or evidence of notability.}} ~~~~Timestamp: 20091109064124 06:41, 9 November 2009 (UTC) Administrators: delete |
 |
mod_proxy is an optional module for the Apache HTTP Server [1].
This module implements a proxy/gateway/cache for Apache. It implements proxying capability for or AJP13 (Apache JServ Protocol version 1.3), FTP, CONNECT (for SSL), HTTP/0.9, HTTP/1.0, and (since Apache 1.3.23) HTTP/1.1. The module can be configured to connect to other proxy modules for these and other protocols.
License
See Apache License.
History
This module was experimental in Apache 1.1.x [2].
As of Apache 1.2, mod_proxy stability was greatly improved [3].
Since Apache 2.0 proxy features are divided into several modules in addition to mod_proxy: mod_proxy_http, mod_proxy_ftp and mod_proxy_connect — moreover caching is provided by mod_cache and related modules [4].
Since Apache 2.2 mod_proxy_ajp and mod_proxy_balancer added too [5].
See also
External links
- Apache module mod_proxy — for Apache 1.3.
- Apache module mod_proxy — for Apache 2.0.
- Apache module mod_proxy — for Apache 2.2.