Views |
|
InformationTechnology:Web:Proxy
[edit] Navigation[edit] Related categories[edit] About this pageWe apologize for the little information we provide, this page is still under construction. Please stay tuned.
[edit] Web proxy resources[edit] Reverse Proxies
[edit] Web-content filteringSquid is a caching Web proxy supporting, among other protocols, HTTP/HTTPS and FTP.Through content-caching,i.e. serving data locally, Squid allows reduction of bandwidth and faster download speeds with frequently-used content.The SquidGuard URL redirector works with Squid for blocking unwanted web contenths through use of blacklists. Compared to SquidGuard, DansGuardian, a web-content filter working with Squid, allows blocking and filtering the actual content of pages based on phrase matching, PICS and URL filtering, beside "standard" filtering based on a banned-site list. While the "standard" web filters such as Cyber Patrol, squidGuard and Net Nanny rely on large bad-site lists. By contrast, content-filtering checks every accessed page for 'bad' subjects it if it's not suitable. More information on installing and configuring DansGuardian is available here. DansGuardian features as companion tools:
DansGuardian is included in the SOHO-grade SmoothWall Express open-source network firewall. Privoxy, another content-filtering is a non-caching web proxy with content-filtering capabilities like web-page rewrite, HTTP-cookie management, access control, and ad/banners/pop-up removal. [edit] URL rewriting with Apache
[edit] Microsoft RSProxy appletMany web applications running on Microsoft IIS server take advantage of the functionality offered by the Microsoft RSProxy applet - namely remote execution of scripts using a Microsoft proprietary mechanism. Incidentally the Cisco Call Manager web-based administration interface is heavily using the RSProxy mechanism. As a result of the RSProxy mechanism the remote-proxying with Apache of the Cisco CCM interface does not work properly.References: [edit] Reverse proxying a Tomcat server - mod_jk and the AJP protocolTomcat does not have the rich set of web-server-specific functions one can find in Apache, nor it has the advanced security mechanisms and URL filtering facilities that Apache has. The Apache Java Protocol (AJP) allows an Apache server to act as a front-end for a Tomcat server, using an AJP-specific reverse-proxying mechanism implemented by mod_jk using the concept of AJP workers However, it has been noticed that firewalls might disconnect the AJP tunnel between Apache and Tomcat due to inactivity timeouts. To send keep-alives the interval is being controlled by sysctl parameter "net.ipv4.tcp_keepalive_time" in /etc/sysctl.conf On the mod_jk configuration side add "worker.apg.socket_keepalive=1" and "worker.apg.connection_pool_timeout=30" to the worker configuration Once done modifying /etc/sysctl.conf issue the following two commands to commit and activate changes:
References:
[edit] Other resources
|
|
| This page was last modified 01:38, 15 March 2008. |