DOCSLIB.ORG

Squid Proxy Server 3.1 Beginner's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Squid Proxy Server 3.1 Beginner's Guide Squid Proxy Server 3.1 Beginner's Guide Improve the performance of your network using the caching and access control capabilities of Squid Kulbir Saini yl open source distilled [i&BSttKte,P- it, I community experience PUBLISHING BIRMINGHAM - MUMBAI Table of Contents Preface 1 Chapter 1: Getting Started with Squid Z Proxy server 7 Reverse proxy 9 Getting Squid 9 Time for action - identifying the right version 10 Methods of obtaining Squid 11 Using source archives 11 Time for action - downloading Squid 11 Obtaining the latest source code from Bazaar VCS 12 Time for action - using Bazaar to obtain source code 13 Using binary packages 14 Installing Squid 14 Installing Squid from source code 14 Compiling Squid 14 Uncompressing the source archive 15 Configure or system check 15 Time for action - running the configure command 25 Time for action - compiling the source 26 Time for action - installing Squid 27 Time for action - exploring Squid files 27 Installing Squid from binary packages 29 Fedora, CentOS or Red Hat 30 Debian or Ubuntu 30 FreeBSD 30 OpenBSD or NetBSD 30 Dragonfly BSD 30 Gentoo 30 Arch Linux 31 Summary 32 Table of Contents Chapter 2: Configuring Squid 33 Quick start 34 Syntax of the configuration file 34 Types of directives 35 HTTP port 37 Time for action - setting the HTTP port 37 Access control lists 38 Time for action - constructing simple ACLs 39 Controlling access to the proxy server 40 HTTP access control 40 Time for action - combining ACLs and HTTP access 41 HTTP reply access 42 ICP access 43 HTCP access 43 HTCP CLR access 43 Miss access 43 Ident lookup access 43 Cache peers or neighbors 44 Declaring cache peers 44 Time for action-adding a cache peer 44 Quickly restricting access to domains using peers 45 Advanced control on access using peers 46 Caching web documents 46 Using main memory (RAM) for caching 46 In-transit objects or current requests 47 Hot or popular objects 47 Negatively cached objects 47 Specifying cache space in RAM 47 Time for action - specifying space for memory caching 48 Maximum object size in memory 48 Memory cache mode 49 Using hard disks for caching 49 Specifying the storage space 49 Time for action - creating a cache directory 51 Configuring the number of sub directories 52 Time for action - adding a cache directory 52 Cache directory selection 53 Cache object size limits 53 Setting limits on object replacement 54 Cache replacement policies 54 Least recently used (LRU) 54 Greedy dual size frequency (GDSF) 54 Least frequently used with dynamic aging (LFUDA) 55 Table of Contents Tuning Squid for enhanced caching 55 Selective caching 55 Time for action - preventing the caching of local content 55 Refresh patterns for cached objects 56 Time for action - calculating the freshness of cached objects 57 Options for refresh pattern 58 Aborting the partial retrievals 60 Caching the failed requests 61 Playing around with HTTP headers 61 Controlling HTTP headers in requests 61 Controlling HTTP headers in responses 62 Replacing the contents of HTTP headers 62 DNS server configuration 62 Specifying the DNS program path 63 Controlling the number of DNS client processes 63 Setting the DNS name servers 63 Time for action - adding DNS name servers 64 Setting the hosts file 64 Default domain name for requests 64 Timeout for DNS queries 64 Caching the DNS responses 65 Setting the size of the DNS cache 65 Logging 66 Log formats 66 Log file rotation or log file backups 66 Log access 66 Buffered logs 66 Strip query terms 67 URL rewriters and redirectors 67 Other configuration directives 67 Setting the effective user for running Squid 68 Configuring hostnames for the proxy server 68 Hostname visible to everyone 68 Unique hostname for the server 68 Controlling the request forwarding 68 Always direct 69 Never direct 69 Hierarchy stoplist 69 Broken posts 70 TCP outgoing address 70 Table of Contents PID filename 71 Client netmask 71 Summary 73 Chapter 3: Running Squid 75 Command line options 75 Getting a list of available options 76 Time for action - listing the options 77 Getting information about our Squid installation 78 Time for action - finding out the Squid version 78 Creating cache or swap directories 78 Time for action - creating cache directories 78 Using a different configuration file 79 Getting verbose output 79 Time for action - debugging output in the console 80 Full debugging output on the terminal 81 Running as a normal process 82 Parsing the Squid configuration file for errors or warnings 82 Time for action - testing our configuration file 82 Sending various signals to a running Squid process 83 Reloading a new configuration file in a running process 83 Shutting down the Squid process 84 Interrupting or killing a running Squid process 84 Checking the status of a running Squid process 84 Sending a running process in to debug mode 85 Rotating the log files 85 Forcing the storage metadata to rebuild 86 Double checking swap during rebuild 86 Automatically starting Squid at system startup 87 Adding Squid command to /etc/rc.local file 87 Adding init script 87 Time for action - adding the init script 87 Summary 89 Chapter 4: Getting Started with Squid's Powerful ACLs and Access Rules 91 Access control lists 92 Fast and slow ACL types 92 Source and destination IP address 92 Time for action - constructing ACL lists using IP addresses 93 Time for action - using a range of IP addresses to build ACL lists 94 Source and destination domain names 96 Time for action - constructing ACL lists using domain names 97 Destination port 98 Table of Contents Time for action - building ACL lists using destination ports 99 HTTP methods 101 Identifying requests using the request protocol 102 Time for action - using a request protocol to construct access rules 102 Time-based ACLs 103 URL and URL path-based identification 104 Matching client usernames 105 Proxy authentication 106 Time for action - enforcing proxy authentication 107 User limits 108 Identification based on various HTTP headers 109 HTTP reply status 111 Identifying random requests 112 Access list rules 112 Access to HTTP protocol 112 Access to other ports 114 Enforcing limited access to neighbors 115 Time for action - denying miss_access to neighbors 115 Requesting neighbor proxy servers 116 Forwarding requests to remote servers 117 Ident lookup access 117 Controlled caching of web documents 118 URL rewrite access 118 HTTP header access 119 Custom error pages 119 Maximum size of the reply body 120 Logging requests selectively 120 Mixing ACL lists and rules - example scenarios 121 Handling caching of local content 121 Time for action - avoiding caching of local content 121 Denying access from external networks 122 Denying access to selective clients 122 Blocking the download of video content 123 Time for action - blocking video content 123 Special access for certain clients 123 Time for action - writing rules for special access 124 Limited access during working hours 124 Allowing some clients to connect to special ports 125 Testing access control with squidclient 126 Table of Contents_ Time for action - testing our access control example with squidclient 128 Time for action - testing a complex access control 129 Summary 132 Chapter 5: Understanding Log Files and Log Formats 133 Log messages 134 Cache log or debug log 134 Time for action - understanding the cache log 134 Access log 137 Understanding the access log 137 Time for action - understanding the access log messages 137 Access log syntax 139 Time for action - analyzing a syntax to specify access log 139 Log format 140 Time for action - learning log format and format codes 140 Log formats provided by Squid 142 Time for action - customizing the access log with a new log format 142 Selective logging of requests 143 Time for action - using accessjog to control logging of requests 144 Referer log 144 Time for action - enabling the referer log 145 Time for action - translating the referer logs to a human-readable format 145 User agent log 146 Time for action - enabling user agent logging 147 Emulating HTTP server-like logs 147 Time for action - enabling HTTP server log emulation 147 Log file rotation 148 Other log related features 148 Cache store log 149 Summary 150 Chapter 6: Managing Squid and Monitoring Traffic 151 Cache manager 151 Installing the Apache Web server 152 Time for action - installing Apache Web server 152 Configuring Apache for providing the cache manager web interface 152 Time for action - configuring Apache to use cachemgr.cgi 153 Accessing the cache manager web interface 153 Configuring Squid 154 Log in to cache manger 154 General Runtime Information 156 IP Cache Stats and Contents 157 FQDN Cache Statistics 158 Table of Contents HTTP Header Statistics 159 Traffic and Resource Counters 160 Request Forwarding Statistics 161 Cache Client List 162 Memory Utilization 163 Internal DNS Statistics 164 Log file analyzers 165 Calamaris 165 Installing Calamaris 166 Time for action - installing Calamaris 166 Using Calamaris to generate statistics 167 Time for action - generating stats in plain text format 167 Time for action - generating graphical reports with Calamaris 168 Summary 171 Chapter 7: Protecting your Squid Proxy Server with Authentication 173 HTTP authentication 174 Basic authentication 174 Time for action - exploring Basic authentication 174 Database authentication 176 Configuring database authentication 177 NCSA authentication 178 Time for action - configuring NCSA authentication 178 NIS authentication 179 LDAP authentication 179 SMB authentication 179 PAM authentication 180 Time for
Load more

Recommended publications
  • Updating Systems and Adding Software in Oracle® Solaris 11.4
    Updating Systems and Adding Software ® in Oracle Solaris 11.4 Part No: E60979 November 2020 Updating Systems and Adding Software in Oracle Solaris 11.4 Part No: E60979 Copyright © 2007, 2020, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
    [Show full text]
  • Linux Tips and Tricks
    Linux Tips and Tricks Chris Karakas Linux Tips and Tricks by Chris Karakas This is a collection of various tips and tricks around Linux. Since they don't fit anywhere else, they are presented here in a more or less loose form. We start on how to get an attractive vi by using syntax highlighting, multiple search and the smartcase, incsearch, scrolloff, wildmode options in the vimrc file. We continue on various configuration subjects regarding Netscape, like positioning and sizing of windows and roaming profiles. Further on, I present a CSS file for HTML documents that were created automatically from DocBook SGML. Also a chapter on transparent proxying with Squid. Copyright © 2002-2003 Chris Karakas. Permission is granted to copy, distribute and/or modify this docu- ment under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license can be found at the Free Software Foundation. Revision History Revision 0.04 04.06..2003 Revised by: CK Added chapter on transparent proxying. Added Index. Alt text and captions for images Revision 0.03 29.05.2003 Revised by: CK Added chapters on Netscape and CSS for DocBook. Revision 0.02 18.12.2002 Revised by: CK first version Table of Contents 1. Introduction......................................................................................................... 1 1.1. Disclaimer .....................................................................................................................1
    [Show full text]
  • The Squid Caching Proxy
    The Squid caching proxy Chris Wichura [email protected] What is Squid? • A caching proxy for – HTTP, HTTPS (tunnel only) –FTP – Gopher – WAIS (requires additional software) – WHOIS (Squid version 2 only) • Supports transparent proxying • Supports proxy hierarchies (ICP protocol) • Squid is not an origin server! Other proxies • Free-ware – Apache 1.2+ proxy support (abysmally bad!) • Commercial – Netscape Proxy – Microsoft Proxy Server – NetAppliance’s NetCache (shares some code history with Squid in the distant past) – CacheFlow (http://www.cacheflow.com/) – Cisco Cache Engine What is a proxy? • Firewall device; internal users communicate with the proxy, which in turn talks to the big bad Internet – Gate private address space (RFC 1918) into publicly routable address space • Allows one to implement policy – Restrict who can access the Internet – Restrict what sites users can access – Provides detailed logs of user activity What is a caching proxy? • Stores a local copy of objects fetched – Subsequent accesses by other users in the organization are served from the local cache, rather than the origin server – Reduces network bandwidth – Users experience faster web access How proxies work (configuration) • User configures web browser to use proxy instead of connecting directly to origin servers – Manual configuration for older PC based browsers, and many UNIX browsers (e.g., Lynx) – Proxy auto-configuration file for Netscape 2.x+ or Internet Explorer 4.x+ • Far more flexible caching policy • Simplifies user configuration, help desk support,
    [Show full text]
  • Installation Guide Supplement for Use with Squid Web Proxy Cache (WWS
    Installation Guide Supplement for use with Squid Web Proxy Cache Websense® Web Security Websense Web Filter v7.5 ©1996 - 2010, Websense, Inc. 10240 Sorrento Valley Rd., San Diego, CA 92121, USA All rights reserved. Published 2010 Printed in the United States of America and Ireland The products and/or methods of use described in this document are covered by U.S. Patent Numbers 5,983,270; 6,606,659; 6,947,985; 7,185,015; 7,194,464 and RE40,187 and other patents pending. This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine- readable form without prior consent in writing from Websense, Inc. Every effort has been made to ensure the accuracy of this manual. However, Websense, Inc., makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose. Websense, Inc., shall not be liable for any error or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual or the examples herein. The information in this documentation is subject to change without notice. Trademarks Websense is a registered trademark of Websense, Inc., in the United States and certain international markets. Websense has numerous other unregistered trademarks in the United States and internationally. All other trademarks are the property of their respective owners. Microsoft, Windows, Windows NT, Windows Server, and Active Directory are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat is a registered trademark of Red Hat, Inc., in the United States and other countries.
    [Show full text]
  • Running SQUID In
    Running SQUIDSQUID in freeBSD Sufi Faruq Ibne Abubakar AKTEL, TMIB What is ? • A full-featured Web proxy cache • Designed to run on Unix systems • Free, open-source software • The result of many contributions by unpaid (and paid) volunteers Why will I use ? • Save 30% Internet Bandwidth • Access Control • Low cost proxy • Proxy keeps database of each request comes from client • Proxy itself goes to get resource from internet to satisfy first time request • Proxy caches resources immediately after obtaining it from internet. • Proxy serves the resource from cache in second request for same resources Consideration for deployment • User calculation • System Memory (Min 256 MB RAM) • Speedy Storage (SCSI Preferred) •Faster CPU • Functionality expectations Supports • Proxying and caching of HTTP, FTP, and other URLs • Proxying for SSL • Cache hierarchies • ICP, HTCP, CARP, Cache Digests • Transparent caching • WCCP (Squid v2.3 and above) • Extensive access controls • HTTP server acceleration • SNMP • caching of DNS lookups Obtaining • Obtain package source from: – http://www.squid-cache.org – Squid Mirror Sites (http://www.squid- cache.org/Mirrors/http-mirrors.html) – Binary download for FreeBSD also available (http://www.squid-cache.org/binaries.html) • “STABLE” releases, suitable for production use • “PRE” releases, suitable for testing Installing • tar zxvf squid-2.4.STABLE6-src.tar.gz • cd squid-2.4.STABLE6 • ./configure --enable-removal-policies --enable-delay-pools --enable-ipf-transparent --enable-snmp --enable-storeio=diskd,ufs --enable-storeio=diskd,ufs
    [Show full text]
  • The Security Considerations with Squid Proxy Server for Windows
    International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 12, December - 2013 The Security Considerations with Squid Proxy Server for Windows Mr.E.Srinivasa Rao 1, Mr.B.Srinu 2 1M.Tech (SE) of IT Department, Gayathri Vidya Parishad College of Engineering, Visakhapatnam. 2Asst.Professor of IT Department, Gayathri Vidya Parishad College of Engineering, Visakhapatnam. Abstract INTRODUCTION Securing and controlling workstation access to the Squid is a Unix-based proxy server that caches web has never been an easy task for security Internet content closer to a requestor than its professionals. Firewalls and access control list on original point of origin. Squid supports caching of routers alone may not bring an acceptable level of many different kinds of Web objects, including security for your organization. Even if their those accessed through HTTP and FTP. Caching primary role is to reduce network traffic and frequently requested Web pages, media files and improve performance, HTTP proxy servers (also other content accelerates response time and called cache servers) are likely to be installed as reduces bandwidth congestion. A Squid proxy an additional security layer and as a web surfing server is generally installed on a separate server monitoring system. Having secure proxy servers is than the Web server with the original files. Squid critical because many users depend on it for their works by tracking object use over the network. work. Several proxy server products are available Squid will initially act as an intermediary, simply nowadays. Since commercial products are very IJERTpassing the client's request on to the server and expensive, alternative products such as openIJERT saving a copy of the requested object.
    [Show full text]
  • User Authentication. SPEC Kit. INSTITUTION Association of Research Libraries, Washington, DC
    DOCUMENT RESUME ED 463 762 IR 058 438 AUTHOR Plum, Terry, Comp.; Bleiler, Richard, Comp. TITLE User Authentication. SPEC Kit. INSTITUTION Association of Research Libraries, Washington, DC. Office of Leadership and Management Services. ISSN ISSN-0160-3582 PUB DATE 2001-12-00 NOTE 103p.; Each SPEC Kit contains an executive summary of the survey results (previously printed as the SPEC Flyer). Published six times per year. AVAILABLE FROM ARL Publications Distribution Center, P.O. Box 531, Annapolis Junction, MD 20701-0531 ($35, ARL member; $45, nonmembers; plus $6 shipping and handling). Tel: 301-362-8196; Fax: 301-206-9789; e-mail: [email protected]; Web site: http://www.arl.org/pubscat/index.html. PUB TYPE Collected Works Serials (022) Reports Research (143) Tests/Questionnaires (160) JOURNAL CIT SPEC Kit; n267 Dec 2001 EDRS PRICE MF01/PC05 Plus Postage. DESCRIPTORS *Academic Libraries; Computer Uses in Education; Electronic Libraries; Foreign Countries; Higher Education; Library Associations; *Library Services; Library Surveys; Online Systems; Questionnaires; *Research Libraries; *Users (Information); World Wide Web IDENTIFIERS Association of Research Libraries; Authenticity; Canada; *Electronic Resources; United States ABSTRACT This SPEC (Systems and Procedures Exchange Center) Kit presents the results of a survey of Association of Research Libraries (ARL) member libraries designed to examine the systems research libraries use to authenticate and authorize the users of their online networked information resources. A total of 52 of 121 ARL
    [Show full text]
  • Traffic Analysis Against Low-Latency Anonymity Networks Using Available Bandwidth Estimation⋆
    Traffic Analysis Against Low-Latency Anonymity Networks Using Available Bandwidth Estimation? Sambuddho Chakravarty1, Angelos Stavrou2, and Angelos D. Keromytis1 1 Columbia University, NY, USA fsc2516,[email protected] 2 George Mason University, VA, USA [email protected] Abstract. We introduce a novel remotely-mounted attack that can ex- pose the network identity of an anonymous client, hidden service, and anonymizing proxies. To achieve this, we employ single-end controlled available bandwidth estimation tools and a colluding network entity that can modulate the traffic destined for the victim. To expose the circuit including the source, we inject a number of short or one large burst of traffic. Although timing attacks have been successful against anonymity networks, they require either a Global Adversary or the compromise of substantial number of anonymity nodes. Our technique does not require compromise of, or collaboration with, any such entity. To validate our attack, we performed a series of experiments using dif- ferent network conditions and locations for the adversaries on both con- trolled and real-world Tor circuits. Our results demonstrate that our attack is successful in controlled environments. In real-world scenarios, even an under-provisioned adversary with only a few network vantage points can, under certain conditions, successfully identify the IP address of both Tor users and Hidden Servers. However, Tor's inherent circuit scheduling results in limited quality of service for its users. This at times leads to increased false negatives and it can degrade the performance of our circuit detection. We believe that as high speed anonymity networks become readily available, a well-provisioned adversary, with a partial or inferred network \map", will be able to partially or fully expose anony- mous users.
    [Show full text]
  • 6.824 Lab 1: a Simple Web Proxy
    6.824 - Fall 2002 6.824 Lab 1: A simple web proxy Introduction Please read "Getting started with 6.824 labs" before starting this assignment. You will also need "Using TCP through sockets" at a later stage. In this lab assignment you will write a simple web proxy. A web proxy is a program that reads a request from a browser, forwards that request to a web server, reads the reply from the web server, and forwards the reply back to the browser. People typically use web proxies to cache pages for better performance, to modify web pages in transit (e.g. to remove annoying advertisements), or for weak anonymity. You'll be writing a web proxy to learn about how to structure servers. For this assignment you'll start simple; in particular your proxy need only handle a single connection at a time. It should accept a new connection from a browser, completely handle the request and response for that browser, and then start work on the next connection. (A real web proxy would be able to handle many connections concurrently.) In this handout, we use client to mean an application program that establishes connections for the purpose of sending requests[3], typically a web browser (e.g., lynx or Netscape). We use server to mean an application program that accepts connections in order to service requests by sending back responses (e.g., the Apache web server)[1]. Note that a proxy acts as both a client and server. Moreover, a proxy could communicate with other proxies (e.g., a cache hierarchy).
    [Show full text]
  • Plugin Hooks – Actions – Views – Page Handlers – Much More
    Elgg Documentation Release master Various Aug 02, 2019 Contents 1 Features 3 2 Examples 5 3 Continue Reading 7 i ii Elgg Documentation, Release master Elgg( pronunciation) is an open source rapid development framework for socially aware web applications. It is a great fit for building any app where users log in and share information. Contents 1 Elgg Documentation, Release master 2 Contents CHAPTER 1 Features • Well-documented core API that allows developers to kick start their new project with a simple learning curve • Composer is the package manager of choice that greatly simplifes installation and maintenance of Elgg core and plugins • Flexible system of hooks and events that allows plugins to extend and modify most aspects of application’s functionality and behavior • Extendable system of views that allows plugins to collaborate on application’s presentation layer and built out complex custom themes • Cacheable system of static assets that allows themes and plugins to serve images, stylesheets, fonts and scripts bypassing the engine • User authentication is powered by pluggable auth modules, which allow applications to implement custom authentication protocols • Security is ensured by built-in anti CSRF validation, strict XSS filters, HMAC signatures, latest cryptographic approaches to password hashing • Client-side API powered by asynchronous JavaScript modules via RequireJS and a build-in Ajax service for easy communication with the server • Flexible entity system that allows applications to prototype new types of content and user interactions
    [Show full text]
  • Open Source Declaration for Extremewing
    Open Source Declaration for ExtremeWiNG Software Release 5.9.1 Release: Release Date: September 29, 2017 This document contains license and notices for free and open source software (collectively, FOSS) used within this product. If you have any questions or wish to receive a copy of any FOSS source code to which you may be entitled, please contact us at [email protected]. Extreme Networks, Inc. 145 Rio Robles San Jose, California 95134 Phone / +1 408.579.2800 Toll-free / +1 888.257.3000 www.extremenetworks.com ©2017 Extreme Networks, Inc. All rights reserved. Extreme Networks, the Extreme Networks logo, and ExtremeWiNG are trademarks or registered trademarks of Extreme Networks, Inc. in the United States and/or other countries. All other names are the property of their respective owners. All other registered trademarks, trademarks, and service marks are property of their respective owners. For additional information on Extreme Networks trademarks, see www.extremenetworks.com/company/legal/trademarks. P/N 9035212 Published Month Year Open Source Declaration for ExtremeWiNG Open Source Software Information General Information This media, software or hardware (“Product”) obtained from Extreme Networks, Inc. (“Extreme Networks”) may include Extreme Networks Software, Third Party Software (defined below), and/or Open Source Software (defined below). The object code or source code (collectively, the “Software”) included with the Product is the exclusive property of Extreme Networks or its licensors, and any use is subject to the terms and conditions of one or more agreements in force between the purchaser of the Extreme Networks Product or licensee of the Extreme Networks Software, and Extreme Networks.
    [Show full text]
  • Implementing Reverse Proxy Using Squid
    Implementing Reverse Proxy Using Squid Prepared By Visolve Squid Team | Introduction | What is Reverse Proxy Cache | About Squid | How Reverse Proxy Cache work | Configuring Squid as Reverse Proxy | Configuring Squid as Reverse Proxy for Multiple Domains | References | Conclusion | | About ViSolve.com | Introduction This document describes reverse proxies, and how they are used to improve Web server performance. Section 1 gives an introduction to reverse proxies, describing what they are and what they are used for. Section 2 compares reverse proxy caches with standard and transparent proxy caches, explaining the different functionality each provides. Section 3 illustrates how the reverse proxy actually caches the content and delivers it to the client. Section 4 describes how to configure Squid as a reverse proxy cache. What is Reverse Proxy Cache Reverse proxy cache, also known as Web Server Acceleration, is a method of reducing the load on a busy web server by using a web cache between the server and the internet. Another benefit that can be gained is improved security. It's one of many ways to improve scalability without increasing the complexity of maintenance too much. A good use of a reverse proxy is to ease the burden on a web server that provides both static and dynamic content. The static content can be cached on the reverse proxy while the web server will be freed up to better handle the dynamic content. By deploying Reverse Proxy Server alongside web servers, sites will: • Avoid the capital expense of purchasing additional web servers by increasing the capacity of existing servers. • Serve more requests for static content from web servers.
    [Show full text]