Squid nur zum maskieren der eigenen IP, nicht für Webserver auf port 80

Dieses Thema im Forum "Web- & File-Services" wurde erstellt von JackJTP, 09.03.2009.

  1. #1 JackJTP, 09.03.2009
    JackJTP

    JackJTP Grünschnabel

    Dabei seit:
    09.03.2009
    Beiträge:
    4
    Zustimmungen:
    0
    Hallo,

    mein Problem ist schnell erklärt und hoffentlich auch so schnell gelöst... ich bin nicht ganz neu in sachen Linux, aber in sachen Proxy bin ich frisch.

    Also: Ich habe Squid bei mir auf einem Debian Root installiert. Ich wollte erreichen, dass ich mich mit meinem Notebook an meinem Server anmelden kann um so dessen IP zu nutzen. Sinn ist ebenso leicht zu erklären: dann kann ich diverse Services und Dienste auf anderen Servern und meinem Router auf die IP des Roots limitieren wenn ich mal von extern zugreifen möchte. So muss ich nicht alle IP´s zulassen - wegen der dynamischen IP halt...

    Jetzt kann ich das auch problemlos- alles funktioniert bestens für mich. Aber das Problem: man muss jetzt auch an diesem Proxy angemeldet sein, um den Webserver auf port 80 der auf dem Root läuft zu erreichen.

    Wie kann ich es also hinbekommen, dass dieser Webserver auch dannn für Besucher erreichbar ist, wenn diese nicht an meinem Squid angemeldet sind?


    eine schnelle Antwort ist immer schön, aber ich würde mich ergänzend auch über nen link zu einem Toutorial freuen- so lerne ich das wenigstens. Google, um dennen vorzugreifen die immer gerne "wer googlen kann ist klar im vorteil" brüllen, spuckt mir auch nur wirschen Kram aus den ich nocht ganz verstehe- liegt wohl daran, dass ich nicht einmal weiss wonach ich googlen muss.

    Ich hoffe also auf eure Hilfe, danke.

    Anbei die konfig:

    Code:
    
    
    
    http_port 3666
    
    # ssl_unclean_shutdown off
    
    # icp_port 3130
    
    # htcp_port 0
    
    # udp_incoming_address 0.0.0.0
    # udp_outgoing_address 255.255.255.255
    
    # icp_query_timeout 0
    
    
    # maximum_icp_query_timeout 2000
    
    
    # mcast_icp_query_timeout 2000
    
    # dead_peer_timeout 10 seconds
    
    hierarchy_stoplist cgi-bin ?
    
    acl QUERY urlpath_regex cgi-bin \?
    cache deny QUERY
    
    # cache_vary on
    
    acl apache rep_header Server ^Apache
    broken_vary_encoding allow apache
    
    # cache_mem 8 MB
    
    # cache_swap_low 90
    # cache_swap_high 95
    
    # maximum_object_size 4096 KB
    
    # minimum_object_size 0 KB
    
    # maximum_object_size_in_memory 8 KB
    
    # ipcache_size 1024
    # ipcache_low 90
    # ipcache_high 95
    # fqdncache_size 1024
    # cache_replacement_policy lru
    
    # memory_replacement_policy lru
    
    
    # cache_dir ufs /var/spool/squid 100 16 256
    
    
    access_log /var/log/squid/access.log squid
    
    # cache_log /var/log/squid/cache.log
    
    # cache_store_log /var/log/squid/store.log
    
    # emulate_httpd_log off
    
    # log_ip_on_direct on
    
    # mime_table /usr/share/squid/mime.conf
    
    # log_mime_hdrs off
    
    # pid_filename /var/run/squid.pid
    
    # debug_options ALL,1
    
    # log_fqdn off
    
    # client_netmask 255.255.255.255
    
    
    # OPTIONS FOR EXTERNAL SUPPORT PROGRAMS
    # -----------------------------------------------------------------------------
    
    
    # ftp_user Squid@
    
    # ftp_list_width 32
    
    # ftp_passive on
    
    # ftp_sanitycheck on
    
    # ftp_telnet_protocol on
    
    # check_hostnames on
    
    # allow_underscore on
    
    # cache_dns_program /usr/lib/squid/dnsserver
    
    # dns_children 5
    
    # dns_retransmit_interval 5 seconds
    
    # dns_timeout 2 minutes
    
    # dns_defnames off
    
    # hosts_file /etc/hosts
    #
    hosts_file /etc/hosts
    
    # diskd_program /usr/lib/squid/diskd-daemon
    
    # unlinkd_program /usr/lib/squid/unlinkd
    
    # pinger_program /usr/lib/squid/pinger
    
    # url_rewrite_concurrency 0
    
    # url_rewrite_host_header on
    
    # none
    
    # location_rewrite_children 5
    
    # location_rewrite_concurrency 0
    
    #Recommended minimum configuration per scheme:
    #auth_param negotiate program <uncomment and complete this line to activate>
    #auth_param negotiate children 5
    #auth_param negotiate keep_alive on
    #auth_param ntlm program <uncomment and complete this line to activate>
    #auth_param ntlm children 5
    #auth_param ntlm keep_alive on
    #auth_param digest program <uncomment and complete this line>
    #auth_param digest children 5
    #auth_param digest realm Squid proxy-caching web server
    #auth_param digest nonce_garbage_interval 5 minutes
    #auth_param digest nonce_max_duration 30 minutes
    #auth_param digest nonce_max_count 50
    #auth_param basic program <uncomment and complete this line>
    #auth_param basic children 5
    #auth_param basic realm Squid proxy-caching web server
    #auth_param basic credentialsttl 2 hours
    #auth_param basic casesensitive off
    
    #  TAG: authenticate_cache_garbage_interval
    #	The time period between garbage collection across the username cache.
    #	This is a tradeoff between memory utilization (long intervals - say
    #	2 days) and CPU (short intervals - say 1 minute). Only change if you
    #	have good reason to.
    #
    #Default:
    # authenticate_cache_garbage_interval 1 hour
    
    #  TAG: authenticate_ttl
    #	The time a user & their credentials stay in the logged in user cache
    #	since their last request. When the garbage interval passes, all user
    #	credentials that have passed their TTL are removed from memory.
    #
    #Default:
    # authenticate_ttl 1 hour
    
    #  TAG: authenticate_ip_ttl
    #	If you use proxy authentication and the 'max_user_ip' ACL, this
    #	directive controls how long Squid remembers the IP addresses
    #	associated with each user.  Use a small value (e.g., 60 seconds) if
    #	your users might change addresses quickly, as is the case with
    #	dialups. You might be safe using a larger value (e.g., 2 hours) in a
    #	corporate LAN environment with relatively static address assignments.
    #
    #Default:
    # authenticate_ip_ttl 0 seconds
    
    #  TAG: external_acl_type
    #	This option defines external acl classes using a helper program to
    #	look up the status
    #
    #	  external_acl_type name [options] FORMAT.. /path/to/helper [helper arguments..]
    #
    #	Options:
    #
    #	  ttl=n		TTL in seconds for cached results (defaults to 3600
    #			for 1 hour)
    #	  negative_ttl=n
    #			TTL for cached negative lookups (default same
    #			as ttl)
    #	  children=n	number of processes spawn to service external acl
    #			lookups of this type.
    #	  concurrency=n	concurrency level per process. Use 0 for simple helpers
    #			who can only process a single request at a time.
    #			Note: see compatibility note below
    #	  cache=n	result cache size, 0 is unbounded (default)
    #	  grace=	Percentage remaining of TTL where a refresh of a
    #			cached entry should be initiated without needing to
    #			wait for a new reply. (default 0 for no grace period)
    #	  protocol=2.5  Compatibility mode for Squid-2.5 external acl helpers
    #
    #	FORMAT specifications
    #
    #	  %LOGIN	Authenticated user login name
    #	  %IDENT	Ident user name
    #	  %SRC		Client IP
    #	  %SRCPORT	Client source port
    #	  %DST		Requested host
    #	  %PROTO	Requested protocol
    #	  %PORT		Requested port
    #	  %METHOD	Request method
    #	  %MYADDR	Squid interface address
    #	  %MYPORT	Squid http_port number
    #	  %PATH		Requested URL-path (including query-string if any)
    #	  %USER_CERT	SSL User certificate in PEM format
    #	  %USER_CERTCHAIN SSL User certificate chain in PEM format
    #	  %USER_CERT_xx	SSL User certificate subject attribute xx
    #	  %USER_CA_xx	SSL User certificate issuer attribute xx
    #	  %{Header}	HTTP request header
    #	  %{Hdr:member}	HTTP request header list member
    #	  %{Hdr:;member}
    #			HTTP request header list member using ; as
    #			list separator. ; can be any non-alphanumeric
    #			character.
    #	 %ACL		The ACL name
    #	 %DATA		The ACL arguments. If not used then any arguments
    #			is automatically added at the end
    #
    #	In addition, any string specified in the referencing acl will
    #	also be included in the helper request line, after the specified
    #	formats (see the "acl external" directive)
    #
    #	The helper receives lines per the above format specification,
    #	and returns lines starting with OK or ERR indicating the validity
    #	of the request and optionally followed by additional keywords with
    #	more details.
    #
    #	General result syntax:
    #
    #	  OK/ERR keyword=value ...
    #
    #	Defined keywords:
    #
    #	  user=		The users name (login also understood)
    #	  password=	The users password (for PROXYPASS login= cache_peer)
    #	  message=	Error message or similar used as %o in error messages
    #			(error also understood)
    #	  log=		String to be logged in access.log. Available as
    #			%ea in logformat specifications
    #
    #	Keyword values need to be enclosed in quotes if they may contain
    #	whitespace, or the whitespace escaped using \. Any quotes or \
    #	characters within the keyword value must be \ escaped.
    #
    #	If protocol=3.0 then URL escaping of the strings is used instead
    #	of the above described quoting format.
    #
    #	Compatibility Note: The children= option was named concurrency= in
    #	Squid-2.5.STABLE3 and earlier, and was accepted as an alias for the
    #	duration of the Squid-2.5 releases to keep compatibility. However,
    #	the meaning of concurrency= option has changed in Squid-2.6 to match
    #	that of Squid-3 and the old syntax no longer works.
    #
    #Default:
    # none
    
    
    # OPTIONS FOR TUNING THE CACHE
    # -----------------------------------------------------------------------------
    
    #  TAG: wais_relay_host
    #  TAG: wais_relay_port
    #	Relay WAIS request to host (1st arg) at port (2 arg).
    #
    #Default:
    # wais_relay_port 0
    
    #  TAG: request_header_max_size	(KB)
    #	This specifies the maximum size for HTTP headers in a request.
    #	Request headers are usually relatively small (about 512 bytes).
    #	Placing a limit on the request header size will catch certain
    #	bugs (for example with persistent connections) and possibly
    #	buffer-overflow or denial-of-service attacks.
    #
    #Default:
    # request_header_max_size 20 KB
    
    #  TAG: request_body_max_size	(KB)
    #	This specifies the maximum size for an HTTP request body.
    #	In other words, the maximum size of a PUT/POST request.
    #	A user who attempts to send a request with a body larger
    #	than this limit receives an "Invalid Request" error message.
    #	If you set this parameter to a zero (the default), there will
    #	be no limit imposed.
    #
    #Default:
    # request_body_max_size 0 KB
    
    #  TAG: refresh_pattern
    #	usage: refresh_pattern [-i] regex min percent max [options]
    #
    #	By default, regular expressions are CASE-SENSITIVE.  To make
    #	them case-insensitive, use the -i option.
    #
    #	'Min' is the time (in minutes) an object without an explicit
    #	expiry time should be considered fresh. The recommended
    #	value is 0, any higher values may cause dynamic applications
    #	to be erroneously cached unless the application designer
    #	has taken the appropriate actions.
    #
    #	'Percent' is a percentage of the objects age (time since last
    #	modification age) an object without explicit expiry time
    #	will be considered fresh.
    #
    #	'Max' is an upper limit on how long objects without an explicit
    #	expiry time will be considered fresh.
    #
    #	options: override-expire
    #		 override-lastmod
    #		 reload-into-ims
    #		 ignore-reload
    #		 ignore-no-cache
    #		 ignore-private
    #		 ignore-auth
    #
    #		override-expire enforces min age even if the server
    #		sent a Expires: header. Doing this VIOLATES the HTTP
    #		standard.  Enabling this feature could make you liable
    #		for problems which it causes.
    #
    #		override-lastmod enforces min age even on objects
    #		that were modified recently.
    #
    #		reload-into-ims changes client no-cache or ``reload''
    #		to If-Modified-Since requests. Doing this VIOLATES the
    #		HTTP standard. Enabling this feature could make you
    #		liable for problems which it causes.
    #
    #		ignore-reload ignores a client no-cache or ``reload''
    #		header. Doing this VIOLATES the HTTP standard. Enabling
    #		this feature could make you liable for problems which
    #		it causes.
    #
    #		ignore-no-cache ignores any ``Pragma: no-cache'' and
    #		``Cache-control: no-cache'' headers received from a server.
    #		The HTTP RFC never allows the use of this (Pragma) header 
    #		from a server, only a client, though plenty of servers 
    #		send it anyway.
    #		
    #		ignore-private ignores any ``Cache-control: private'' 
    #		headers received from a server. Doing this VIOLATES 
    #		the HTTP standard. Enabling this feature could make you 
    #		liable for problems which it causes.
    #		
    #		ignore-auth caches responses to requests with authorization,
    #		irrespective of ``Cache-control'' headers received from 
    #		a server. Doing this VIOLATES the HTTP standard. Enabling
    #		this feature could make you liable for problems which
    #		it causes.
    #		
    #	Basically a cached object is:
    #
    #		FRESH if expires < now, else STALE
    #		STALE if age > max
    #		FRESH if lm-factor < percent, else STALE
    #		FRESH if age < min
    #		else STALE
    #
    #	The refresh_pattern lines are checked in the order listed here.
    #	The first entry which matches is used.  If none of the entries
    #	match the default will be used.
    #
    #	Note, you must uncomment all the default lines if you want
    #	to change one. The default setting is only active if none is
    #	used.
    #
    #Suggested default:
    refresh_pattern ^ftp:		1440	20%	10080
    refresh_pattern ^gopher:	1440	0%	1440
    refresh_pattern .		0	20%	4320
    
    #  TAG: quick_abort_min	(KB)
    #  TAG: quick_abort_max	(KB)
    #  TAG: quick_abort_pct	(percent)
    #	The cache by default continues downloading aborted requests
    #	which are almost completed (less than 16 KB remaining). This
    #	may be undesirable on slow (e.g. SLIP) links and/or very busy
    #	caches.  Impatient users may tie up file descriptors and
    #	bandwidth by repeatedly requesting and immediately aborting
    #	downloads.
    #
    #	When the user aborts a request, Squid will check the
    #	quick_abort values to the amount of data transfered until
    #	then.
    #
    #	If the transfer has less than 'quick_abort_min' KB remaining,
    #	it will finish the retrieval.
    #
    #	If the transfer has more than 'quick_abort_max' KB remaining,
    #	it will abort the retrieval.
    #
    #	If more than 'quick_abort_pct' of the transfer has completed,
    #	it will finish the retrieval.
    #
    #	If you do not want any retrieval to continue after the client
    #	has aborted, set both 'quick_abort_min' and 'quick_abort_max'
    #	to '0 KB'.
    #
    #	If you want retrievals to always continue if they are being
    #	cached set 'quick_abort_min' to '-1 KB'.
    #
    #Default:
    # quick_abort_min 16 KB
    # quick_abort_max 16 KB
    # quick_abort_pct 95
    
    #  TAG: read_ahead_gap	buffer-size
    #	The amount of data the cache will buffer ahead of what has been
    #	sent to the client when retrieving an object from another server.
    #
    #Default:
    # read_ahead_gap 16 KB
    
    #  TAG: negative_ttl	time-units
    #	Time-to-Live (TTL) for failed requests.  Certain types of
    #	failures (such as "connection refused" and "404 Not Found") are
    #	negatively-cached for a configurable amount of time.  The
    #	default is 5 minutes.  Note that this is different from
    #	negative caching of DNS lookups.
    #
    #Default:
    # negative_ttl 5 minutes
    
    #  TAG: positive_dns_ttl	time-units
    #	Upper limit on how long Squid will cache positive DNS responses.
    #	Default is 6 hours (360 minutes). This directive must be set
    #	larger than negative_dns_ttl.
    #
    #Default:
    # positive_dns_ttl 6 hours
    
    #  TAG: negative_dns_ttl	time-units
    #	Time-to-Live (TTL) for negative caching of failed DNS lookups.
    #	This also makes sets the lower cache limit on positive lookups.
    #	Minimum value is 1 second, and it is not recommendable to go
    #	much below 10 seconds.
    #
    #Default:
    # negative_dns_ttl 1 minute
    
    #  TAG: range_offset_limit	(bytes)
    #	Sets a upper limit on how far into the the file a Range request
    #	may be to cause Squid to prefetch the whole file. If beyond this
    #	limit Squid forwards the Range request as it is and the result
    #	is NOT cached.
    #
    #	This is to stop a far ahead range request (lets say start at 17MB)
    #	from making Squid fetch the whole object up to that point before
    #	sending anything to the client.
    #
    #	A value of -1 causes Squid to always fetch the object from the
    #	beginning so it may cache the result. (2.0 style)
    #
    #	A value of 0 causes Squid to never fetch more than the
    #	client requested. (default)
    #
    #Default:
    # range_offset_limit 0 KB
    
    #  TAG: collapsed_forwarding	(on|off)
    #	This option enables multiple requests for the same URI to be
    #	processed as one request. Normally disabled to avoid increased
    #	latency on dynamic content, but there can be benefit from enabling
    #	this in accelerator setups where the web servers are the bottleneck
    #	and reliable and returns mostly cacheable information.
    #
    #Default:
    # collapsed_forwarding off
    
    #  TAG: refresh_stale_hit	(time)
    #	This option changes the refresh algorithm to allow concurrent
    #	requests while an object is being refreshed to be processed as
    #	cache hits if the object expired less than X seconds ago. Default
    #	is 0 to disable this feature. This option is mostly interesting
    #	in accelerator setups where a few objects is accessed very
    #	frequently.
    #
    #Default:
    # refresh_stale_hit 0 seconds
    
    
    # TIMEOUTS
    # -----------------------------------------------------------------------------
    
    #  TAG: forward_timeout	time-units
    #	This parameter specifies how long Squid should at most attempt in
    #	finding a forwarding path for the request before giving up.
    #
    #Default:
    # forward_timeout 4 minutes
    
    #  TAG: connect_timeout	time-units
    #	This parameter specifies how long to wait for the TCP connect to
    #	the requested server or peer to complete before Squid should
    #	attempt to find another path where to forward the request.
    #
    #Default:
    # connect_timeout 1 minute
    
    #  TAG: peer_connect_timeout	time-units
    #	This parameter specifies how long to wait for a pending TCP
    #	connection to a peer cache.  The default is 30 seconds.   You
    #	may also set different timeout values for individual neighbors
    #	with the 'connect-timeout' option on a 'cache_peer' line.
    #
    #Default:
    # peer_connect_timeout 30 seconds
    
    #  TAG: read_timeout	time-units
    #	The read_timeout is applied on server-side connections.  After
    #	each successful read(), the timeout will be extended by this
    #	amount.  If no data is read again after this amount of time,
    #	the request is aborted and logged with ERR_READ_TIMEOUT.  The
    #	default is 15 minutes.
    #
    #Default:
    # read_timeout 15 minutes
    
    #  TAG: request_timeout
    #	How long to wait for an HTTP request after initial
    #	connection establishment.
    #
    #Default:
    # request_timeout 5 minutes
    
    #  TAG: persistent_request_timeout
    #	How long to wait for the next HTTP request on a persistent
    #	connection after the previous request completes.
    #
    #Default:
    # persistent_request_timeout 1 minute
    
    #  TAG: client_lifetime	time-units
    #	The maximum amount of time a client (browser) is allowed to
    #	remain connected to the cache process.  This protects the Cache
    #	from having a lot of sockets (and hence file descriptors) tied up
    #	in a CLOSE_WAIT state from remote clients that go away without
    #	properly shutting down (either because of a network failure or
    #	because of a poor client implementation).  The default is one
    #	day, 1440 minutes.
    #
    #	NOTE:  The default value is intended to be much larger than any
    #	client would ever need to be connected to your cache.  You
    #	should probably change client_lifetime only as a last resort.
    #	If you seem to have many client connections tying up
    #	filedescriptors, we recommend first tuning the read_timeout,
    #	request_timeout, persistent_request_timeout and quick_abort values.
    #
    #Default:
    # client_lifetime 1 day
    
    #  TAG: half_closed_clients
    #	Some clients may shutdown the sending side of their TCP
    #	connections, while leaving their receiving sides open.	Sometimes,
    #	Squid can not tell the difference between a half-closed and a
    #	fully-closed TCP connection.  By default, half-closed client
    #	connections are kept open until a read(2) or write(2) on the
    #	socket returns an error.  Change this option to 'off' and Squid
    #	will immediately close client connections when read(2) returns
    #	"no more data to read."
    #
    #Default:
    # half_closed_clients on
    
    #  TAG: pconn_timeout
    #	Timeout for idle persistent connections to servers and other
    #	proxies.
    #
    #Default:
    # pconn_timeout 120 seconds
    
    #  TAG: ident_timeout
    #	Maximum time to wait for IDENT lookups to complete.
    #
    #	If this is too high, and you enabled IDENT lookups from untrusted
    #	users, you might be susceptible to denial-of-service by having
    #	many ident requests going at once.
    #
    #Default:
    # ident_timeout 10 seconds
    
    #  TAG: shutdown_lifetime	time-units
    #	When SIGTERM or SIGHUP is received, the cache is put into
    #	"shutdown pending" mode until all active sockets are closed.
    #	This value is the lifetime to set for all open descriptors
    #	during shutdown mode.  Any active clients after this many
    #	seconds will receive a 'timeout' message.
    #
    #Default:
    # shutdown_lifetime 30 seconds
    
    
    # ACCESS CONTROLS
    # -----------------------------------------------------------------------------
    
    #  TAG: acl
    #	Defining an Access List
    #
    #	acl aclname acltype string1 ...
    #	acl aclname acltype "file" ...
    #
    #	when using "file", the file should contain one item per line
    #
    #	acltype is one of the types described below
    #
    #	By default, regular expressions are CASE-SENSITIVE.  To make
    #	them case-insensitive, use the -i option.
    #
    #	acl aclname src      ip-address/netmask ... (clients IP address)
    #	acl aclname src      addr1-addr2/netmask ... (range of addresses)
    #	acl aclname dst      ip-address/netmask ... (URL host's IP address)
    #	acl aclname myip     ip-address/netmask ... (local socket IP address)
    #
    #	acl aclname arp      mac-address ... (xx:xx:xx:xx:xx:xx notation)
    #	  # The arp ACL requires the special configure option --enable-arp-acl.
    #	  # Furthermore, the arp ACL code is not portable to all operating systems.
    #	  # It works on Linux, Solaris, FreeBSD and some other *BSD variants.
    #	  #
    #	  # NOTE: Squid can only determine the MAC address for clients that are on
    #	  # the same subnet. If the client is on a different subnet, then Squid cannot
    #	  # find out its MAC address.
    #
    #	acl aclname srcdomain   .foo.com ...    # reverse lookup, client IP
    #	acl aclname dstdomain   .foo.com ...    # Destination server from URL
    #	acl aclname srcdom_regex [-i] xxx ...   # regex matching client name
    #	acl aclname dstdom_regex [-i] xxx ...   # regex matching server
    #	  # For dstdomain and dstdom_regex  a reverse lookup is tried if a IP
    #	  # based URL is used and no match is found. The name "none" is used
    #	  # if the reverse lookup fails.
    #
    #	acl aclname time     [day-abbrevs]  [h1:m1-h2:m2]
    #	    day-abbrevs:
    #		S - Sunday
    #		M - Monday
    #		T - Tuesday
    #		W - Wednesday
    #		H - Thursday
    #		F - Friday
    #		A - Saturday
    #	    h1:m1 must be less than h2:m2
    #	acl aclname url_regex [-i] ^http:// ...	# regex matching on whole URL
    #	acl aclname urlpath_regex [-i] \.gif$ ...	# regex matching on URL path
    #	acl aclname urllogin [-i] [^a-zA-Z0-9] ...	# regex matching on URL login field
    #	acl aclname port     80 70 21 ...
    #	acl aclname port     0-1024 ...		# ranges allowed
    #	acl aclname myport   3128 ...		# (local socket TCP port)
    #	acl aclname proto    HTTP FTP ...
    #	acl aclname method   GET POST ...
    #	acl aclname browser  [-i] regexp ...
    #	  # pattern match on User-Agent header (see also req_header below)
    #	acl aclname referer_regex  [-i] regexp ...
    #	  # pattern match on Referer header
    #	  # Referer is highly unreliable, so use with care
    #	acl aclname ident    username ...
    #	acl aclname ident_regex [-i] pattern ...
    #	  # string match on ident output.
    #	  # use REQUIRED to accept any non-null ident.
    #	acl aclname src_as   number ...
    #	acl aclname dst_as   number ...
    #	  # Except for access control, AS numbers can be used for
    #	  # routing of requests to specific caches. Here's an
    #	  # example for routing all requests for AS#1241 and only
    #	  # those to mycache.mydomain.net:
    #	  # acl asexample dst_as 1241
    #	  # cache_peer_access mycache.mydomain.net allow asexample
    #	  # cache_peer_access mycache_mydomain.net deny all
    #
    #	acl aclname proxy_auth username ...
    #	acl aclname proxy_auth_regex [-i] pattern ...
    #	  # list of valid usernames
    #	  # use REQUIRED to accept any valid username.
    #	  #
    #	  # NOTE: when a Proxy-Authentication header is sent but it is not
    #	  # needed during ACL checking the username is NOT logged
    #	  # in access.log.
    #	  #
    #	  # NOTE: proxy_auth requires a EXTERNAL authentication program
    #	  # to check username/password combinations (see
    #	  # auth_param directive).
    #	  #
    #	  # WARNING: proxy_auth can't be used in a transparent proxy. It
    #	  # collides with any authentication done by origin servers. It may
    #	  # seem like it works at first, but it doesn't.
    #
    #	acl aclname snmp_community string ...
    #	  # A community string to limit access to your SNMP Agent
    #	  # Example:
    #	  #
    #	  #	acl snmppublic snmp_community public
    #
    #	acl aclname maxconn number
    #	  # This will be matched when the client's IP address has
    #	  # more than <number> HTTP connections established.
    #
    #	acl aclname max_user_ip [-s] number
    #	  # This will be matched when the user attempts to log in from more
    #	  # than <number> different ip addresses. The authenticate_ip_ttl
    #	  # parameter controls the timeout on the ip entries.
    #	  # If -s is specified the limit is strict, denying browsing
    #	  # from any further IP addresses until the ttl has expired. Without
    #	  # -s Squid will just annoy the user by "randomly" denying requests.
    #	  # (the counter is reset each time the limit is reached and a
    #	  # request is denied)
    #	  # NOTE: in acceleration mode or where there is mesh of child proxies,
    #	  # clients may appear to come from multiple addresses if they are
    #	  # going through proxy farms, so a limit of 1 may cause user problems.
    #
    #	acl aclname req_mime_type mime-type1 ...
    #	  # regex match against the mime type of the request generated
    #	  # by the client. Can be used to detect file upload or some
    #	  # types HTTP tunneling requests.
    #	  # NOTE: This does NOT match the reply. You cannot use this
    #	  # to match the returned file type.
    #
    #	acl aclname req_header header-name [-i] any\.regex\.here
    #	  # regex match against any of the known request headers.  May be
    #	  # thought of as a superset of "browser", "referer" and "mime-type"
    #	  # ACLs.
    #
    #	acl aclname rep_mime_type mime-type1 ...
    #	  # regex match against the mime type of the reply received by
    #	  # squid. Can be used to detect file download or some
    #	  # types HTTP tunneling requests.
    #	  # NOTE: This has no effect in http_access rules. It only has
    #	  # effect in rules that affect the reply data stream such as
    #	  # http_reply_access.
    #
    #	acl aclname rep_header header-name [-i] any\.regex\.here
    #	  # regex match against any of the known response headers.
    #	  # Example:
    #	  #
    #	  # acl many_spaces rep_header Content-Disposition -i [[:space:]]{3,}
    #
    #	acl acl_name external class_name [arguments...]
    #	  # external ACL lookup via a helper class defined by the
    #	  # external_acl_type directive.
    #
    #	acl urlgroup group1 ...
    #	  # match against the urlgroup as indicated by redirectors
    #
    #	acl aclname user_cert attribute values...
    #	  # match against attributes in a user SSL certificate
    #	  # attribute is one of DN/C/O/CN/L/ST
    #
    #	acl aclname ca_cert attribute values...
    #	  # match against attributes a users issuing CA SSL certificate
    #	  # attribute is one of DN/C/O/CN/L/ST
    #
    #	acl aclname ext_user       username ...
    #	acl aclname ext_user_regex [-i] pattern ...
    #	  # string match on username returned by external acl
    #	  # use REQUIRED to accept any user name.
    #Examples:
    #acl macaddress arp 09:00:2b:23:45:67
    #acl myexample dst_as 1241
    #acl password proxy_auth REQUIRED
    #acl fileupload req_mime_type -i ^multipart/form-data$
    #acl javascript rep_mime_type -i ^application/x-javascript$
    #
    #Recommended minimum configuration:
    acl all src 0.0.0.0/0.0.0.0
    acl manager proto cache_object
    acl localhost src 127.0.0.1/255.255.255.255
    acl to_localhost dst 127.0.0.0/8
    acl SSL_ports port 443		# https
    acl SSL_ports port 563		# snews
    acl SSL_ports port 873		# rsync
    acl Safe_ports port 80		# http
    acl Safe_ports port 21		# ftp
    acl Safe_ports port 443		# https
    acl Safe_ports port 70		# gopher
    acl Safe_ports port 210		# wais
    acl Safe_ports port 1025-65535	# unregistered ports
    acl Safe_ports port 280		# http-mgmt
    acl Safe_ports port 488		# gss-http
    acl Safe_ports port 591		# filemaker
    acl Safe_ports port 777		# multiling http
    acl Safe_ports port 631		# cups
    acl Safe_ports port 873		# rsync
    acl Safe_ports port 901		# SWAT
    acl purge method PURGE
    acl CONNECT method CONNECT
    
    #  TAG: follow_x_forwarded_for
    # Note: This option is only available if Squid is rebuilt with the
    #       -DFOLLOW_X_FORWARDED_FOR option
    #
    #	Allowing or Denying the X-Forwarded-For header to be followed to
    #	find the original source of a request.
    #
    #	Requests may pass through a chain of several other proxies
    #	before reaching us.  The X-Forwarded-For header will contain a
    #	comma-separated list of the IP addresses in the chain, with the
    #	rightmost address being the most recent.
    #
    #	If a request reaches us from a source that is allowed by this
    #	configuration item, then we consult the X-Forwarded-For header
    #	to see where that host received the request from.  If the
    #	X-Forwarded-For header contains multiple addresses, and if
    #	acl_uses_indirect_client is on, then we continue backtracking
    #	until we reach an address for which we are not allowed to
    #	follow the X-Forwarded-For header, or until we reach the first
    #	address in the list.  (If acl_uses_indirect_client is off, then
    #	it's impossible to backtrack through more than one level of
    #	X-Forwarded-For addresses.)
    #
    #	The end result of this process is an IP address that we will
    #	refer to as the indirect client address.  This address may
    #	be treated as the client address for access control, delay
    #	pools and logging, depending on the acl_uses_indirect_client,
    #	delay_pool_uses_indirect_client and log_uses_indirect_client
    #	options.
    #
    #	SECURITY CONSIDERATIONS:
    #
    #		Any host for which we follow the X-Forwarded-For header
    #		can place incorrect information in the header, and Squid
    #		will use the incorrect information as if it were the
    #		source address of the request.  This may enable remote
    #		hosts to bypass any access control restrictions that are
    #		based on the client's source addresses.
    #
    #	For example:
    #
    #		acl localhost src 127.0.0.1
    #		acl my_other_proxy srcdomain .proxy.example.com
    #		follow_x_forwarded_for allow localhost
    #		follow_x_forwarded_for allow my_other_proxy
    #
    #Default:
    # follow_x_forwarded_for deny all
    
    #  TAG: acl_uses_indirect_client	on|off
    # Note: This option is only available if Squid is rebuilt with the
    #       -DFOLLOW_X_FORWARDED_FOR option
    #
    #	Controls whether the indirect client address
    #	(see follow_x_forwarded_for) is used instead of the
    #	direct client address in acl matching.
    #
    #Default:
    # acl_uses_indirect_client on
    
    #  TAG: delay_pool_uses_indirect_client	on|off
    # Note: This option is only available if Squid is rebuilt with the
    #       -DFOLLOW_X_FORWARDED_FOR option
    #
    #	Controls whether the indirect client address
    #	(see follow_x_forwarded_for) is used instead of the
    #	direct client address in delay pools.
    #
    #Default:
    # delay_pool_uses_indirect_client on
    
    #  TAG: log_uses_indirect_client	on|off
    # Note: This option is only available if Squid is rebuilt with the
    #       -DFOLLOW_X_FORWARDED_FOR option
    #
    #	Controls whether the indirect client address
    #	(see follow_x_forwarded_for) is used instead of the
    #	direct client address in the access log.
    #
    #Default:
    # log_uses_indirect_client on
    
    #  TAG: http_access
    #	Allowing or Denying access based on defined access lists
    #
    #	Access to the HTTP port:
    #	http_access allow|deny [!]aclname ...
    #
    #	NOTE on default values:
    #
    #	If there are no "access" lines present, the default is to deny
    #	the request.
    #
    #	If none of the "access" lines cause a match, the default is the
    #	opposite of the last line in the list.  If the last line was
    #	deny, the default is allow.  Conversely, if the last line
    #	is allow, the default will be deny.  For these reasons, it is a
    #	good idea to have an "deny all" or "allow all" entry at the end
    #	of your access lists to avoid potential confusion.
    #
    #Default:
    # http_access deny all
    #
    #Recommended minimum configuration:
    #
    # Only allow cachemgr access from localhost
    http_access allow manager localhost
    http_access allow manager
    # Only allow purge requests from localhost
    http_access allow purge localhost
    http_access allow purge
    # Deny requests to unknown ports
    http_access allow !Safe_ports
    # Deny CONNECT to other than SSL ports
    http_access allow CONNECT !SSL_ports
    #
    # We strongly recommend the following be uncommented to protect innocent
    # web applications running on the proxy server who think the only
    # one who can access services on "localhost" is a local user
    #http_access deny to_localhost
    #
    # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
    
    # Example rule allowing access from your local networks. Adapt
    # to list your (internal) IP networks from where browsing should
    # be allowed
    #acl our_networks src 192.168.1.0/24 192.168.2.0/24
    #http_access allow our_networks
    http_access allow localhost
    
    # And finally deny all other access to this proxy
    http_access allow all
    
    #  TAG: http_access2
    #	Allowing or Denying access based on defined access lists
    #
    #	Identical to http_access, but runs after redirectors. If not set
    #	then only http_access is used.
    #
    #Default:
    # none
    
    #  TAG: http_reply_access
    #	Allow replies to client requests. This is complementary to http_access.
    #
    #	http_reply_access allow|deny [!] aclname ...
    #
    #	NOTE: if there are no access lines present, the default is to allow
    #	all replies
    #
    #	If none of the access lines cause a match the opposite of the
    #	last line will apply. Thus it is good practice to end the rules
    #	with an "allow all" or "deny all" entry.
    #
    #Default:
    # http_reply_access allow all
    #
    #Recommended minimum configuration:
    #
    # Insert your own rules here.
    #
    #
    # and finally allow by default
    http_reply_access allow all
    
    #  TAG: icp_access
    #	Allowing or Denying access to the ICP port based on defined
    #	access lists
    #
    #	icp_access  allow|deny [!]aclname ...
    #
    #	See http_access for details
    #
    #Default:
    # icp_access deny all
    #
    #Allow ICP queries from everyone
    icp_access allow all
    
    #  TAG: htcp_access
    #	Allowing or Denying access to the HTCP port based on defined
    #	access lists
    #
    #	htcp_access  allow|deny [!]aclname ...
    #
    #	See http_access for details
    #
    ##Allow HTCP queries from everyone
    #htcp_access allow all
    #
    #Default:
    # htcp_access deny all
    
    #  TAG: htcp_clr_access
    #	Allowing or Denying access to purge content using HTCP based
    #	on defined access lists
    #
    #	htcp_clr_access  allow|deny [!]aclname ...
    #
    #	See http_access for details
    #
    ##Allow HTCP CLR requests from trusted peers
    #acl htcp_clr_peer src 172.16.1.2
    #htcp_clr_access allow htcp_clr_peer
    #
    #Default:
    # htcp_clr_access deny all
    
    #  TAG: miss_access
    #	Use to force your neighbors to use you as a sibling instead of
    #	a parent.  For example:
    #
    #		acl localclients src 172.16.0.0/16
    #		miss_access allow localclients
    #		miss_access deny  !localclients
    #
    #	This means only your local clients are allowed to fetch
    #	MISSES and all other clients can only fetch HITS.
    #
    #	By default, allow all clients who passed the http_access rules
    #	to fetch MISSES from us.
    #
    #Default setting:
    # miss_access allow all
    
    #  TAG: cache_peer_access
    #	Similar to 'cache_peer_domain' but provides more flexibility by
    #	using ACL elements.
    #
    #	cache_peer_access cache-host allow|deny [!]aclname ...
    #
    #	The syntax is identical to 'http_access' and the other lists of
    #	ACL elements.  See the comments for 'http_access' below, or
    #	the Squid FAQ (http://www.squid-cache.org/FAQ/FAQ-10.html).
    #
    #Default:
    # none
    
    #  TAG: ident_lookup_access
    #	A list of ACL elements which, if matched, cause an ident
    #	(RFC931) lookup to be performed for this request.  For
    #	example, you might choose to always perform ident lookups
    #	for your main multi-user Unix boxes, but not for your Macs
    #	and PCs.  By default, ident lookups are not performed for
    #	any requests.
    #
    #	To enable ident lookups for specific client addresses, you
    #	can follow this example:
    #
    #	acl ident_aware_hosts src 198.168.1.0/255.255.255.0
    #	ident_lookup_access allow ident_aware_hosts
    #	ident_lookup_access deny all
    #
    #	Only src type ACL checks are fully supported.  A src_domain
    #	ACL might work at times, but it will not always provide
    #	the correct result.
    #
    #Default:
    # ident_lookup_access deny all
    
    #  TAG: tcp_outgoing_tos
    #	Allows you to select a TOS/Diffserv value to mark outgoing
    #	connections with, based on the username or source address
    #	making the request.
    #
    #	tcp_outgoing_tos ds-field [!]aclname ...
    #
    #	Example where normal_service_net uses the TOS value 0x00
    #	and normal_service_net uses 0x20
    #
    #	acl normal_service_net src 10.0.0.0/255.255.255.0
    #	acl good_service_net src 10.0.1.0/255.255.255.0
    #	tcp_outgoing_tos 0x00 normal_service_net 0x00
    #	tcp_outgoing_tos 0x20 good_service_net
    #
    #	TOS/DSCP values really only have local significance - so you should
    #	know what you're specifying. For more information, see RFC2474 and 
    #	RFC3260.
    #
    #	The TOS/DSCP byte must be exactly that - a octet value  0 - 255, or
    #	"default" to use whatever default your host has. Note that in
    #	practice often only values 0 - 63 is usable as the two highest bits
    #	have been redefined for use by ECN (RFC3168).
    #
    #	Processing proceeds in the order specified, and stops at first fully
    #	matching line.
    #
    #	Note: The use of this directive using client dependent ACLs is
    #	incompatible with the use of server side persistent connections. To
    #	ensure correct results it is best to set server_persisten_connections
    #	to off when using this directive in such configurations.
    #
    #Default:
    # none
    
    #  TAG: tcp_outgoing_address
    #	Allows you to map requests to different outgoing IP addresses
    #	based on the username or source address of the user making
    #	the request.
    #
    #	tcp_outgoing_address ipaddr [[!]aclname] ...
    #
    #	Example where requests from 10.0.0.0/24 will be forwarded
    #	with source address 10.1.0.1, 10.0.2.0/24 forwarded with
    #	source address 10.1.0.2 and the rest will be forwarded with
    #	source address 10.1.0.3.
    #
    #	acl normal_service_net src 10.0.0.0/255.255.255.0
    #	acl good_service_net src 10.0.1.0/255.255.255.0
    #	tcp_outgoing_address 10.0.0.1 normal_service_net
    #	tcp_outgoing_address 10.0.0.2 good_service_net
    #	tcp_outgoing_address 10.0.0.3
    #
    #	Processing proceeds in the order specified, and stops at first fully
    #	matching line.
    #
    #	Note: The use of this directive using client dependent ACLs is
    #	incompatible with the use of server side persistent connections. To
    #	ensure correct results it is best to set server_persistent_connections
    #	to off when using this directive in such configurations.
    #
    #Default:
    # none
    
    #  TAG: reply_header_max_size	(KB)
    #	This specifies the maximum size for HTTP headers in a reply.
    #	Reply headers are usually relatively small (about 512 bytes).
    #	Placing a limit on the reply header size will catch certain
    #	bugs (for example with persistent connections) and possibly
    #	buffer-overflow or denial-of-service attacks.
    #
    #Default:
    # reply_header_max_size 20 KB
    
    #  TAG: reply_body_max_size	bytes allow|deny acl acl...
    #	This option specifies the maximum size of a reply body in bytes.
    #	It can be used to prevent users from downloading very large files,
    #	such as MP3's and movies. When the reply headers are received,
    #	the reply_body_max_size lines are processed, and the first line with
    #	a result of "allow" is used as the maximum body size for this reply.
    #	This size is checked twice. First when we get the reply headers,
    #	we check the content-length value.  If the content length value exists
    #	and is larger than the allowed size, the request is denied and the
    #	user receives an error message that says "the request or reply
    #	is too large." If there is no content-length, and the reply
    #	size exceeds this limit, the client's connection is just closed
    #	and they will receive a partial reply.
    #
    #	WARNING: downstream caches probably can not detect a partial reply
    #	if there is no content-length header, so they will cache
    #	partial responses and give them out as hits.  You should NOT
    #	use this option if you have downstream caches.
    #
    #	If you set this parameter to zero (the default), there will be
    #	no limit imposed.
    #
    #Default:
    # reply_body_max_size 0 allow all
    
    #  TAG: log_access	allow|deny acl acl...
    #	This options allows you to control which requests gets logged
    #	to access.log (see access_log directive). Requests denied for
    #	logging will also not be accounted for in performance counters.
    #
    #Default:
    # none
    
    
    # ADMINISTRATIVE PARAMETERS
    # -----------------------------------------------------------------------------
    
    #  TAG: cache_mgr
    #	Email-address of local cache manager who will receive
    #	mail if the cache dies. The default is "webmaster".
    #
    #Default:
    # cache_mgr webmaster
    
    #  TAG: mail_from
    #	From: email-address for mail sent when the cache dies.
    #	The default is to use 'appname@unique_hostname'.
    #	Default appname value is "squid", can be changed into 
    #	src/globals.h before building squid.
    #
    #Default:
    # none
    
    #  TAG: mail_program
    #	Email program used to send mail if the cache dies.
    #	The default is "mail". The specified program must complain
    #	with the standard Unix mail syntax:
    #	mail_program recipient < mailfile
    #	Optional command line options can be specified.
    #
    #Default:
    # mail_program mail
    
    #  TAG: cache_effective_user
    #	If you start Squid as root, it will change its effective/real
    #	UID/GID to the user specified below.  The default is to change
    #	to UID to proxy.  If you define cache_effective_user, but not
    #	cache_effective_group, Squid sets the GID to the effective
    #	user's default group ID (taken from the password file) and
    #	supplementary group list from the from groups membership of
    #	cache_effective_user.
    #
    #Default:
    # cache_effective_user proxy
    cache_effective_user proxy
    
    #  TAG: cache_effective_group
    #	If you want Squid to run with a specific GID regardless of
    #	the group memberships of the effective user then set this
    #	to the group (or GID) you want Squid to run as. When set
    #	all other group privileges of the effective user is ignored
    #	and only this GID is effective. If Squid is not started as
    #	root the user starting Squid must be member of the specified
    #	group.
    cache_effective_group proxy
    
    #  TAG: httpd_suppress_version_string	on|off
    #	Suppress Squid version string info in HTTP headers and HTML error pages.
    #
    #Default:
    # httpd_suppress_version_string off
    
    #  TAG: visible_hostname
    #	If you want to present a special hostname in error messages, etc,
    #	define this.  Otherwise, the return value of gethostname()
    #	will be used. If you have multiple caches in a cluster and
    #	get errors about IP-forwarding you must set them to have individual
    #	names with this setting.
    #
    #Default:
    # none
    
    #  TAG: unique_hostname
    #	If you want to have multiple machines with the same
    #	'visible_hostname' you must give each machine a different
    #	'unique_hostname' so forwarding loops can be detected.
    #
    #Default:
    # none
    
    visible_hostname SPR-Design
    
    
    #  TAG: hostname_aliases
    #	A list of other DNS names your cache has.
    #
    #Default:
    # none
    
    #  TAG: umask
    #	Minimum umask which should be enforced while the proxy
    #	is running, in addition to the umask set at startup.
    #
    #	Note: Should start with a 0 to indicate the normal octal
    #	representation of umasks
    #
    #Default:
    # umask 027
    
    
    # OPTIONS FOR THE CACHE REGISTRATION SERVICE
    # -----------------------------------------------------------------------------
    #
    #	This section contains parameters for the (optional) cache
    #	announcement service.  This service is provided to help
    #	cache administrators locate one another in order to join or
    #	create cache hierarchies.
    #
    #	An 'announcement' message is sent (via UDP) to the registration
    #	service by Squid.  By default, the announcement message is NOT
    #	SENT unless you enable it with 'announce_period' below.
    #
    #	The announcement message includes your hostname, plus the
    #	following information from this configuration file:
    #
    #		http_port
    #		icp_port
    #		cache_mgr
    #
    #	All current information is processed regularly and made
    #	available on the Web at http://www.ircache.net/Cache/Tracker/.
    
    #  TAG: announce_period
    #	This is how frequently to send cache announcements.  The
    #	default is `0' which disables sending the announcement
    #	messages.
    #
    #	To enable announcing your cache, just uncomment the line
    #	below.
    #
    #Default:
    # announce_period 0
    #
    #To enable announcing your cache, just uncomment the line below.
    #announce_period 1 day
    
    #  TAG: announce_host
    #  TAG: announce_file
    #  TAG: announce_port
    #	announce_host and announce_port set the hostname and port
    #	number where the registration message will be sent.
    #
    #	Hostname will default to 'tracker.ircache.net' and port will
    #	default default to 3131.  If the 'filename' argument is given,
    #	the contents of that file will be included in the announce
    #	message.
    #
    #Default:
    # announce_host tracker.ircache.net
    # announce_port 3131
    
    
    # HTTPD-ACCELERATOR OPTIONS
    # -----------------------------------------------------------------------------
    
    #  TAG: httpd_accel_no_pmtu_disc	on|off
    #	In many setups of transparently intercepting proxies Path-MTU
    #	discovery can not work on traffic towards the clients. This is
    #	the case when the intercepting device does not fully track
    #	connections and fails to forward ICMP must fragment messages
    #	to the cache server. 
    #	
    #	If you have such setup and experience that certain clients
    #	sporadically hang or never complete requests set this to on.
    #
    #Default:
    # httpd_accel_no_pmtu_disc off
    
    
    # MISCELLANEOUS
    # -----------------------------------------------------------------------------
    
    #  TAG: dns_testnames
    #	The DNS tests exit as soon as the first site is successfully looked up
    #
    #	This test can be disabled with the -D command line option.
    #
    #Default:
    # dns_testnames netscape.com internic.net nlanr.net microsoft.com
    
    #  TAG: logfile_rotate
    #	Specifies the number of logfile rotations to make when you
    #	type 'squid -k rotate'.  The default is 10, which will rotate
    #	with extensions 0 through 9.  Setting logfile_rotate to 0 will
    #	disable the rotation, but the logfiles are still closed and
    #	re-opened.  This will enable you to rename the logfiles
    #	yourself just before sending the rotate signal.
    #
    #	Note, the 'squid -k rotate' command normally sends a USR1
    #	signal to the running squid process.  In certain situations
    #	(e.g. on Linux with Async I/O), USR1 is used for other
    #	purposes, so -k rotate uses another signal.  It is best to get
    #	in the habit of using 'squid -k rotate' instead of 'kill -USR1
    #	<pid>'.
    #
    #	Note2, for Debian/Linux the default of logfile_rotate is
    #	zero, since it includes external logfile-rotation methods.
    #
    #Default:
    # logfile_rotate 0
    
    #  TAG: append_domain
    #	Appends local domain name to hostnames without any dots in
    #	them.  append_domain must begin with a period.
    #
    #	Be warned there are now Internet names with no dots in
    #	them using only top-domain names, so setting this may
    #	cause some Internet sites to become unavailable.
    #
    #Example:
    # append_domain .yourdomain.com
    #
    #Default:
    # none
    
    #  TAG: tcp_recv_bufsize	(bytes)
    #	Size of receive buffer to set for TCP sockets.  Probably just
    #	as easy to change your kernel's default.  Set to zero to use
    #	the default buffer size.
    #
    #Default:
    # tcp_recv_bufsize 0 bytes
    
    #  TAG: error_map
    #	Map errors to custom messages
    #
    #	    error_map message_url http_status ...
    #
    #	http_status ... is a list of HTTP status codes or Squid error
    #	messages.
    #
    #	Use in accelerators to substitute the error messages returned
    #	by servers with other custom errors. 
    #
    #	    error_map http://your.server/error/404.shtml 404
    #	
    #	Requests for error messages is a GET request for the configured
    #	URL with the following special headers
    #
    #	    X-Error-Status:	The received HTTP status code (i.e. 404)
    #	    X-Request-URI:	The requested URI where the error occurred
    #	
    #	In Addition the following headers are forwarded from the client
    #	request:
    #	    
    #	    User-Agent, Cookie, X-Forwarded-For, Via, Authorization,
    #	    Accept, Referer
    #	
    #	And the following headers from the server reply:
    #
    #	    Server, Via, Location, Content-Location
    #	
    #	The reply returned to the client will carry the original HTTP
    #	headers from the real error message, but with the reply body
    #	of the configured error message.
    #
    #
    #Default:
    # none
    
    #  TAG: err_html_text
    #	HTML text to include in error messages.  Make this a "mailto"
    #	URL to your admin address, or maybe just a link to your
    #	organizations Web page.
    #
    #	To include this in your error messages, you must rewrite
    #	the error template files (found in the "errors" directory).
    #	Wherever you want the 'err_html_text' line to appear,
    #	insert a %L tag in the error template file.
    #
    #Default:
    # none
    
    #  TAG: deny_info
    #	Usage:   deny_info err_page_name acl
    #	or       deny_info http://... acl
    #	Example: deny_info ERR_CUSTOM_ACCESS_DENIED bad_guys
    #
    #	This can be used to return a ERR_ page for requests which
    #	do not pass the 'http_access' rules.  A single ACL will cause
    #	the http_access check to fail.  If a 'deny_info' line exists
    #	for that ACL Squid returns a corresponding error page.
    #
    #	You may use ERR_ pages that come with Squid or create your own pages
    #	and put them into the configured errors/ directory.
    #
    #	Alternatively you can specify an error URL. The browsers will
    #	get redirected (302) to the specified URL. %s in the redirection
    #	URL will be replaced by the requested URL.
    #
    #	Alternatively you can tell Squid to reset the TCP connection
    #	by specifying TCP_RESET.
    #
    #Default:
    # none
    
    #  TAG: memory_pools	on|off
    #	If set, Squid will keep pools of allocated (but unused) memory
    #	available for future use.  If memory is a premium on your
    #	system and you believe your malloc library outperforms Squid
    #	routines, disable this.
    #
    #Default:
    # memory_pools on
    
    #  TAG: memory_pools_limit	(bytes)
    #	Used only with memory_pools on:
    #	memory_pools_limit 50 MB
    #
    #	If set to a non-zero value, Squid will keep at most the specified
    #	limit of allocated (but unused) memory in memory pools. All free()
    #	requests that exceed this limit will be handled by your malloc
    #	library. Squid does not pre-allocate any memory, just safe-keeps
    #	objects that otherwise would be free()d. Thus, it is safe to set
    #	memory_pools_limit to a reasonably high value even if your
    #	configuration will use less memory.
    #
    #	If set to zero, Squid will keep all memory it can. That is, there
    #	will be no limit on the total amount of memory used for safe-keeping.
    #
    #	To disable memory allocation optimization, do not set
    #	memory_pools_limit to 0. Set memory_pools to "off" instead.
    #
    #	An overhead for maintaining memory pools is not taken into account
    #	when the limit is checked. This overhead is close to four bytes per
    #	object kept. However, pools may actually _save_ memory because of
    #	reduced memory thrashing in your malloc library.
    #
    #Default:
    # memory_pools_limit 5 MB
    
    #  TAG: via	on|off
    #	If set (default), Squid will include a Via header in requests and
    #	replies.
    #
    #Default:
    # via on
    
    #  TAG: forwarded_for	on|off
    #	If set, Squid will include your system's IP address or name
    #	in the HTTP requests it forwards.  By default it looks like
    #	this:
    #
    #		X-Forwarded-For: 192.1.2.3
    #
    #	If you disable this, it will appear as
    #
    #		X-Forwarded-For: unknown
    #
    #Default:
    # forwarded_for on
    
    #  TAG: log_icp_queries	on|off
    #	If set, ICP queries are logged to access.log. You may wish
    #	do disable this if your ICP load is VERY high to speed things
    #	up or to simplify log analysis.
    #
    #Default:
    # log_icp_queries on
    
    #  TAG: icp_hit_stale	on|off
    #	If you want to return ICP_HIT for stale cache objects, set this
    #	option to 'on'.  If you have sibling relationships with caches
    #	in other administrative domains, this should be 'off'.  If you only
    #	have sibling relationships with caches under your control,
    #	it is probably okay to set this to 'on'.
    #	If set to 'on', your siblings should use the option "allow-miss"
    #	on their cache_peer lines for connecting to you.
    #
    #Default:
    # icp_hit_stale off
    
    #  TAG: minimum_direct_hops
    #	If using the ICMP pinging stuff, do direct fetches for sites
    #	which are no more than this many hops away.
    #
    #Default:
    # minimum_direct_hops 4
    
    #  TAG: minimum_direct_rtt
    #	If using the ICMP pinging stuff, do direct fetches for sites
    #	which are no more than this many rtt milliseconds away.
    #
    #Default:
    # minimum_direct_rtt 400
    
    #  TAG: cachemgr_passwd
    #	Specify passwords for cachemgr operations.
    #
    #	Usage: cachemgr_passwd password action action ...
    #
    #	Some valid actions are (see cache manager menu for a full list):
    #		5min
    #		60min
    #		asndb
    #		authenticator
    #		cbdata
    #		client_list
    #		comm_incoming
    #		config *
    #		counters
    #		delay
    #		digest_stats
    #		dns
    #		events
    #		filedescriptors
    #		fqdncache
    #		histograms
    #		http_headers
    #		info
    #		io
    #		ipcache
    #		mem
    #		menu
    #		netdb
    #		non_peers
    #		objects
    #		offline_toggle *
    #		pconn
    #		peer_select
    #		redirector
    #		refresh
    #		server_list
    #		shutdown *
    #		store_digest
    #		storedir
    #		utilization
    #		via_headers
    #		vm_objects
    #
    #	* Indicates actions which will not be performed without a
    #	  valid password, others can be performed if not listed here.
    #
    #	To disable an action, set the password to "disable".
    #	To allow performing an action without a password, set the
    #	password to "none".
    #
    #	Use the keyword "all" to set the same password for all actions.
    #
    #Example:
    # cachemgr_passwd secret shutdown
    # cachemgr_passwd lesssssssecret info stats/objects
    # cachemgr_passwd disable all
    #
    #Default:
    # none
    
    #  TAG: store_avg_object_size	(kbytes)
    #	Average object size, used to estimate number of objects your
    #	cache can hold.  The default is 13 KB.
    #
    #Default:
    # store_avg_object_size 13 KB
    
    #  TAG: store_objects_per_bucket
    #	Target number of objects per bucket in the store hash table.
    #	Lowering this value increases the total number of buckets and
    #	also the storage maintenance rate.  The default is 50.
    #
    #Default:
    # store_objects_per_bucket 20
    
    #  TAG: client_db	on|off
    #	If you want to disable collecting per-client statistics,
    #	turn off client_db here.
    #
    #Default:
    # client_db on
    
    #  TAG: netdb_low
    #  TAG: netdb_high
    #	The low and high water marks for the ICMP measurement
    #	database.  These are counts, not percents.  The defaults are
    #	900 and 1000.  When the high water mark is reached, database
    #	entries will be deleted until the low mark is reached.
    #
    #Default:
    # netdb_low 900
    # netdb_high 1000
    
    #  TAG: netdb_ping_period
    #	The minimum period for measuring a site.  There will be at
    #	least this much delay between successive pings to the same
    #	network.  The default is five minutes.
    #
    #Default:
    # netdb_ping_period 5 minutes
    
    #  TAG: query_icmp	on|off
    #	If you want to ask your peers to include ICMP data in their ICP
    #	replies, enable this option.
    #
    #	If your peer has configured Squid (during compilation) with
    #	'--enable-icmp' that peer will send ICMP pings to origin server
    #	sites of the URLs it receives.  If you enable this option the
    #	ICP replies from that peer will include the ICMP data (if available).
    #	Then, when choosing a parent cache, Squid will choose the parent with
    #	the minimal RTT to the origin server.  When this happens, the
    #	hierarchy field of the access.log will be
    #	"CLOSEST_PARENT_MISS".  This option is off by default.
    #
    #Default:
    # query_icmp off
    
    #  TAG: test_reachability	on|off
    #	When this is 'on', ICP MISS replies will be ICP_MISS_NOFETCH
    #	instead of ICP_MISS if the target host is NOT in the ICMP
    #	database, or has a zero RTT.
    #
    #Default:
    # test_reachability off
    
    #  TAG: buffered_logs	on|off
    #	cache.log log file is written with stdio functions, and as such
    #	it can be buffered or unbuffered. By default it will be unbuffered.
    #	Buffering it can speed up the writing slightly (though you are
    #	unlikely to need to worry unless you run with tons of debugging
    #	enabled in which case performance will suffer badly anyway..).
    #
    #Default:
    # buffered_logs off
    
    #  TAG: reload_into_ims	on|off
    #	When you enable this option, client no-cache or ``reload''
    #	requests will be changed to If-Modified-Since requests.
    #	Doing this VIOLATES the HTTP standard.  Enabling this
    #	feature could make you liable for problems which it
    #	causes.
    #
    #	see also refresh_pattern for a more selective approach.
    #
    #Default:
    # reload_into_ims off
    
    #  TAG: always_direct
    #	Usage: always_direct allow|deny [!]aclname ...
    #
    #	Here you can use ACL elements to specify requests which should
    #	ALWAYS be forwarded by Squid to the origin servers without using
    #	any peers.  For example, to always directly forward requests for
    #	local servers ignoring any parents or siblings you may have use
    #	something like:
    #
    #		acl local-servers dstdomain my.domain.net
    #		always_direct allow local-servers
    #
    #	To always forward FTP requests directly, use
    #
    #		acl FTP proto FTP
    #		always_direct allow FTP
    #
    #	NOTE: There is a similar, but opposite option named
    #	'never_direct'.  You need to be aware that "always_direct deny
    #	foo" is NOT the same thing as "never_direct allow foo".  You
    #	may need to use a deny rule to exclude a more-specific case of
    #	some other rule.  Example:
    #
    #		acl local-external dstdomain external.foo.net
    #		acl local-servers dstdomain  .foo.net
    #		always_direct deny local-external
    #		always_direct allow local-servers
    #
    #	NOTE: If your goal is to make the client forward the request
    #	directly to the origin server bypassing Squid then this needs
    #	to be done in the client configuration. Squid configuration
    #	can only tell Squid how Squid should fetch the object.
    #
    #	NOTE: This directive is not related to caching. The replies
    #	is cached as usual even if you use always_direct. To not cache
    #	the replies see no_cache.
    #
    #	This option replaces some v1.1 options such as local_domain
    #	and local_ip.
    #
    #Default:
    # none
    
    #  TAG: never_direct
    #	Usage: never_direct allow|deny [!]aclname ...
    #
    #	never_direct is the opposite of always_direct.  Please read
    #	the description for always_direct if you have not already.
    #
    #	With 'never_direct' you can use ACL elements to specify
    #	requests which should NEVER be forwarded directly to origin
    #	servers.  For example, to force the use of a proxy for all
    #	requests, except those in your local domain use something like:
    #
    #		acl local-servers dstdomain .foo.net
    #		acl all src 0.0.0.0/0.0.0.0
    #		never_direct deny local-servers
    #		never_direct allow all
    #
    #	or if Squid is inside a firewall and there are local intranet
    #	servers inside the firewall use something like:
    #
    #		acl local-intranet dstdomain .foo.net
    #		acl local-external dstdomain external.foo.net
    #		always_direct deny local-external
    #		always_direct allow local-intranet
    #		never_direct allow all
    #
    #	This option replaces some v1.1 options such as inside_firewall
    #	and firewall_ip.
    #
    #Default:
    # none
    
    #  TAG: header_access
    #	Usage: header_access header_name allow|deny [!]aclname ...
    #
    #	WARNING: Doing this VIOLATES the HTTP standard.  Enabling
    #	this feature could make you liable for problems which it
    #	causes.
    #
    #	This option replaces the old 'anonymize_headers' and the
    #	older 'http_anonymizer' option with something that is much
    #	more configurable. This new method creates a list of ACLs
    #	for each header, allowing you very fine-tuned header
    #	mangling.
    #
    #	You can only specify known headers for the header name.
    #	Other headers are reclassified as 'Other'. You can also
    #	refer to all the headers with 'All'.
    #
    #	For example, to achieve the same behavior as the old
    #	'http_anonymizer standard' option, you should use:
    #
    #		header_access From deny all
    #		header_access Referer deny all
    #		header_access Server deny all
    #		header_access User-Agent deny all
    #		header_access WWW-Authenticate deny all
    #		header_access Link deny all
    #
    #	Or, to reproduce the old 'http_anonymizer paranoid' feature
    #	you should use:
    #
    #		header_access Allow allow all
    #		header_access Authorization allow all
    #		header_access WWW-Authenticate allow all
    #		header_access Proxy-Authorization allow all
    #		header_access Proxy-Authenticate allow all
    #		header_access Cache-Control allow all
    #		header_access Content-Encoding allow all
    #		header_access Content-Length allow all
    #		header_access Content-Type allow all
    #		header_access Date allow all
    #		header_access Expires allow all
    #		header_access Host allow all
    #		header_access If-Modified-Since allow all
    #		header_access Last-Modified allow all
    #		header_access Location allow all
    #		header_access Pragma allow all
    #		header_access Accept allow all
    #		header_access Accept-Charset allow all
    #		header_access Accept-Encoding allow all
    #		header_access Accept-Language allow all
    #		header_access Content-Language allow all
    #		header_access Mime-Version allow all
    #		header_access Retry-After allow all
    #		header_access Title allow all
    #		header_access Connection allow all
    #		header_access Proxy-Connection allow all
    #		header_access All deny all
    #
    #	By default, all headers are allowed (no anonymizing is
    #	performed).
    #
    #Default:
    # none
    
    #  TAG: header_replace
    #	Usage:   header_replace header_name message
    #	Example: header_replace User-Agent Nutscrape/1.0 (CP/M; 8-bit)
    #
    #	This option allows you to change the contents of headers
    #	denied with header_access above, by replacing them with
    #	some fixed string. This replaces the old fake_user_agent
    #	option.
    #
    #	By default, headers are removed if denied.
    #
    #Default:
    # none
    
    #  TAG: icon_directory
    #	Where the icons are stored. These are normally kept in
    #	/usr/share/squid/icons
    #
    #Default:
    # icon_directory /usr/share/squid/icons
    
    #  TAG: global_internal_static
    #	This directive controls is Squid should intercept all requests for
    #	/squid-internal-static/ no matter which host the URL is requesting
    #	(default on setting), or if nothing special should be done for
    #	such URLs (off setting). The purpose of this directive is to make
    #	icons etc work better in complex cache hierarchies where it may
    #	not always be possible for all corners in the cache mesh to reach
    #	the server generating a directory listing.
    #
    #Default:
    # global_internal_static on
    
    #  TAG: short_icon_urls
    #	If this is enabled Squid will use short URLs for icons.
    #
    #	If off the URLs for icons will always be absolute URLs
    #	including the proxy name and port.
    #
    #Default:
    # short_icon_urls off
    
    #  TAG: error_directory
    #	If you wish to create your own versions of the default
    #	(English) error files, either to customize them to suit your
    #	language or company copy the template English files to another
    #	directory and point this tag at them.
    #
    #Default:
    # error_directory /usr/share/squid/errors/English
    
    #  TAG: maximum_single_addr_tries
    #	This sets the maximum number of connection attempts for a
    #	host that only has one address (for multiple-address hosts,
    #	each address is tried once).
    #
    #	The default value is one attempt, the (not recommended)
    #	maximum is 255 tries.  A warning message will be generated
    #	if it is set to a value greater than ten.
    #
    #	Note: This is in addition to the request re-forwarding which
    #	takes place if Squid fails to get a satisfying response.
    #
    #Default:
    # maximum_single_addr_tries 1
    
    #  TAG: retry_on_error
    #	If set to on Squid will automatically retry requests when
    #	receiving an error response. This is mainly useful if you
    #	are in a complex cache hierarchy to work around access
    #	control errors.
    #
    #Default:
    # retry_on_error off
    
    #  TAG: snmp_port
    #	Squid can now serve statistics and status information via SNMP.
    #	By default it listens to port 3401 on the machine. If you don't
    #	wish to use SNMP, set this to "0".
    #
    #	Note: on Debian/Linux, the default is zero - you need to
    #	set it to 3401 to enable it.
    #
    #Default:
    # snmp_port 0
    
    #  TAG: snmp_access
    #	Allowing or denying access to the SNMP port.
    #
    #	All access to the agent is denied by default.
    #	usage:
    #
    #	snmp_access allow|deny [!]aclname ...
    #
    #Example:
    # snmp_access allow snmppublic localhost
    # snmp_access deny all
    #
    #Default:
    # snmp_access deny all
    
    #  TAG: snmp_incoming_address
    #  TAG: snmp_outgoing_address
    #	Just like 'udp_incoming_address' above, but for the SNMP port.
    #
    #	snmp_incoming_address	is used for the SNMP socket receiving
    #				messages from SNMP agents.
    #	snmp_outgoing_address	is used for SNMP packets returned to SNMP
    #				agents.
    #
    #	The default snmp_incoming_address (0.0.0.0) is to listen on all
    #	available network interfaces.
    #
    #	If snmp_outgoing_address is set to 255.255.255.255 (the default)
    #	it will use the same socket as snmp_incoming_address. Only
    #	change this if you want to have SNMP replies sent using another
    #	address than where this Squid listens for SNMP queries.
    #
    #	NOTE, snmp_incoming_address and snmp_outgoing_address can not have
    #	the same value since they both use port 3401.
    #
    #Default:
    # snmp_incoming_address 0.0.0.0
    # snmp_outgoing_address 255.255.255.255
    
    #  TAG: as_whois_server
    #	WHOIS server to query for AS numbers.  NOTE: AS numbers are
    #	queried only when Squid starts up, not for every request.
    #
    #Default:
    # as_whois_server whois.ra.net
    # as_whois_server whois.ra.net
    
    #  TAG: wccp_router
    #  TAG: wccp2_router
    #	Use this option to define your WCCP ``home'' router for
    #	Squid.
    #
    #	wccp_router supports a single WCCP(v1) router
    #
    #	wccp2_router supports multiple WCCPv2 routers
    #
    #	only one of the two may be used at the same time and defines
    #	which version of WCCP to use.
    #
    #Default:
    # wccp_router 0.0.0.0
    
    #  TAG: wccp_version
    #	This directive is only relevant if you need to set up WCCP(v1)
    #	to some very old and end-of-life Cisco routers. In all other
    #	setups it must be left unset or at the default setting.
    #	It defines an internal version in the WCCP(v1) protocol,
    #	with version 4 being the officially documented protocol.
    #
    #	According to some users, Cisco IOS 11.2 and earlier only
    #	support WCCP version 3.  If you're using that or an earlier
    #	version of IOS, you may need to change this value to 3, otherwise
    #	do not specify this parameter.
    #
    #Default:
    # wccp_version 4
    
    #  TAG: wccp2_rebuild_wait
    #	If this is enabled Squid will wait for the cache dir rebuild to finish
    #	before sending the first wccp2 HereIAm packet
    #
    #Default:
    # wccp2_rebuild_wait on
    
    #  TAG: wccp2_forwarding_method
    #	WCCP2 allows the setting of forwarding methods between the 
    #	router/switch and the cache.  Valid values are as follows:
    #
    #	1 - GRE encapsulation (forward the packet in a GRE/WCCP tunnel)
    #	2 - L2 redirect (forward the packet using Layer 2/MAC rewriting)
    #
    #	Currently (as of IOS 12.4) cisco routers only support GRE.
    #	Cisco switches only support the L2 redirect assignment method.
    #
    #Default:
    # wccp2_forwarding_method 1
    
    #  TAG: wccp2_return_method
    #	WCCP2 allows the setting of return methods between the 
    #	router/switch and the cache for packets that the cache
    #	decides not to handle.  Valid values are as follows:
    #
    #	1 - GRE encapsulation (forward the packet in a GRE/WCCP tunnel)
    #	2 - L2 redirect (forward the packet using Layer 2/MAC rewriting)
    #
    #	Currently (as of IOS 12.4) cisco routers only support GRE.
    #	Cisco switches only support the L2 redirect assignment.
    #
    #	If the "ip wccp redirect exclude in" command has been 
    #	enabled on the cache interface, then it is still safe for
    #	the proxy server to use a l2 redirect method even if this
    #	option is set to GRE.
    #
    #Default:
    # wccp2_return_method 1
    
    #  TAG: wccp2_assignment_method
    #	WCCP2 allows the setting of methods to assign the WCCP hash
    #	Valid values are as follows:
    #
    #	1 - Hash assignment
    #	2 - Mask assignment
    #
    #	As a general rule, cisco routers support the hash assignment method
    #	and cisco switches support the mask assignment method.
    #
    #Default:
    # wccp2_assignment_method 1
    
    #  TAG: wccp2_service
    #	WCCP2 allows for multiple traffic services. There are two
    #	types: "standard" and "dynamic". The standard type defines
    #	one service id - http (id 0). The dynamic service ids can be from
    #	51 to 255 inclusive.  In order to use a dynamic service id
    #	one must define the type of traffic to be redirected; this is done
    #	using the wccp2_service_info option.
    #
    #	The "standard" type does not require a wccp2_service_info option,
    #	just specifying the service id will suffice.
    #
    #	MD5 service authentication can be enabled by adding
    #	"password=<password>" to the end of this service declaration.
    #
    #	Examples:
    #
    #	wccp2_service standard 0	# for the 'web-cache' standard service
    #	wccp2_service dynamic 80	# a dynamic service type which will be
    #					# fleshed out with subsequent options.
    #	wccp2_service standard 0 password=foo
    #
    #
    #Default:
    # wccp2_service standard 0
    
    #  TAG: wccp2_service_info
    #	Dynamic WCCPv2 services require further information to define the
    #	traffic you wish to have diverted.
    #
    #	The format is:
    #
    #	wccp2_service_info <id> protocol=<protocol> flags=<flag>,<flag>..
    #	    priority=<priority> ports=<port>,<port>..
    #
    #	The relevant WCCPv2 flags:
    #	+ src_ip_hash, dst_ip_hash
    #	+ source_port_hash, dest_port_hash
    #	+ src_ip_alt_hash, dst_ip_alt_hash
    #	+ src_port_alt_hash, dst_port_alt_hash
    #	+ ports_source
    #
    #	The port list can be one to eight entries.
    #
    #	Example:
    #
    #	wccp2_service_info 80 protocol=tcp flags=src_ip_hash,ports_source
    #	    priority=240 ports=80
    #
    #	Note: the service id must have been defined by a previous
    #	'wccp2_service dynamic <id>' entry.
    #
    #Default:
    # none
    
    #  TAG: wccp2_weight
    #	Each cache server gets assigned a set of the destination
    #	hash proportional to their weight.
    #
    #Default:
    # wccp2_weight 10000
    
    #  TAG: wccp_address
    #  TAG: wccp2_address
    #	Use this option if you require WCCP to use a specific
    #	interface address.
    #
    #	The default behavior is to not bind to any specific address.
    #
    #Default:
    # wccp_address 0.0.0.0
    # wccp2_address 0.0.0.0
    
    
    # DELAY POOL PARAMETERS (all require DELAY_POOLS compilation option)
    # -----------------------------------------------------------------------------
    
    #  TAG: delay_pools
    #	This represents the number of delay pools to be used.  For example,
    #	if you have one class 2 delay pool and one class 3 delays pool, you
    #	have a total of 2 delay pools.
    #
    #Default:
    # delay_pools 0
    
    #  TAG: delay_class
    #	This defines the class of each delay pool.  There must be exactly one
    #	delay_class line for each delay pool.  For example, to define two
    #	delay pools, one of class 2 and one of class 3, the settings above
    #	and here would be:
    #
    #Example:
    # delay_pools 2      # 2 delay pools
    # delay_class 1 2    # pool 1 is a class 2 pool
    # delay_class 2 3    # pool 2 is a class 3 pool
    #
    #	The delay pool classes are:
    #
    #		class 1		Everything is limited by a single aggregate
    #				bucket.
    #
    #		class 2 	Everything is limited by a single aggregate
    #				bucket as well as an "individual" bucket chosen
    #				from bits 25 through 32 of the IP address.
    #
    #		class 3		Everything is limited by a single aggregate
    #				bucket as well as a "network" bucket chosen
    #				from bits 17 through 24 of the IP address and a
    #				"individual" bucket chosen from bits 17 through
    #				32 of the IP address.
    #
    #	NOTE: If an IP address is a.b.c.d
    #		-> bits 25 through 32 are "d"
    #		-> bits 17 through 24 are "c"
    #		-> bits 17 through 32 are "c * 256 + d"
    #
    #Default:
    # none
    
    #  TAG: delay_access
    #	This is used to determine which delay pool a request falls into.
    #
    #	delay_access is sorted per pool and the matching starts with pool 1,
    #	then pool 2, ..., and finally pool N. The first delay pool where the
    #	request is allowed is selected for the request. If it does not allow
    #	the request to any pool then the request is not delayed (default).
    #
    #	For example, if you want some_big_clients in delay
    #	pool 1 and lotsa_little_clients in delay pool 2:
    #
    #Example:
    # delay_access 1 allow some_big_clients
    # delay_access 1 deny all
    # delay_access 2 allow lotsa_little_clients
    # delay_access 2 deny all
    #
    #Default:
    # none
    
    #  TAG: delay_parameters
    #	This defines the parameters for a delay pool.  Each delay pool has
    #	a number of "buckets" associated with it, as explained in the
    #	description of delay_class.  For a class 1 delay pool, the syntax is:
    #
    #delay_parameters pool aggregate
    #
    #	For a class 2 delay pool:
    #
    #delay_parameters pool aggregate individual
    #
    #	For a class 3 delay pool:
    #
    #delay_parameters pool aggregate network individual
    #
    #	The variables here are:
    #
    #		pool		a pool number - ie, a number between 1 and the
    #				number specified in delay_pools as used in
    #				delay_class lines.
    #
    #		aggregate	the "delay parameters" for the aggregate bucket
    #				(class 1, 2, 3).
    #
    #		individual	the "delay parameters" for the individual
    #				buckets (class 2, 3).
    #
    #		network		the "delay parameters" for the network buckets
    #				(class 3).
    #
    #	A pair of delay parameters is written restore/maximum, where restore is
    #	the number of bytes (not bits - modem and network speeds are usually
    #	quoted in bits) per second placed into the bucket, and maximum is the
    #	maximum number of bytes which can be in the bucket at any time.
    #
    #	For example, if delay pool number 1 is a class 2 delay pool as in the
    #	above example, and is being used to strictly limit each host to 64kbps
    #	(plus overheads), with no overall limit, the line is:
    #
    #delay_parameters 1 -1/-1 8000/8000
    #
    #	Note that the figure -1 is used to represent "unlimited".
    #
    #	And, if delay pool number 2 is a class 3 delay pool as in the above
    #	example, and you want to limit it to a total of 256kbps (strict limit)
    #	with each 8-bit network permitted 64kbps (strict limit) and each
    #	individual host permitted 4800bps with a bucket maximum size of 64kb
    #	to permit a decent web page to be downloaded at a decent speed
    #	(if the network is not being limited due to overuse) but slow down
    #	large downloads more significantly:
    #
    #delay_parameters 2 32000/32000 8000/8000 600/8000
    #
    #	There must be one delay_parameters line for each delay pool.
    #
    #Default:
    # none
    
    #  TAG: delay_initial_bucket_level	(percent, 0-100)
    #	The initial bucket percentage is used to determine how much is put
    #	in each bucket when squid starts, is reconfigured, or first notices
    #	a host accessing it (in class 2 and class 3, individual hosts and
    #	networks only have buckets associated with them once they have been
    #	"seen" by squid).
    #
    #Default:
    # delay_initial_bucket_level 50
    
    #  TAG: incoming_icp_average
    #  TAG: incoming_http_average
    #  TAG: incoming_dns_average
    #  TAG: min_icp_poll_cnt
    #  TAG: min_dns_poll_cnt
    #  TAG: min_http_poll_cnt
    #	Heavy voodoo here.  I can't even believe you are reading this.
    #	Are you crazy?  Don't even think about adjusting these unless
    #	you understand the algorithms in comm_select.c first!
    #
    #Default:
    # incoming_icp_average 6
    # incoming_http_average 4
    # incoming_dns_average 4
    # min_icp_poll_cnt 8
    # min_dns_poll_cnt 8
    # min_http_poll_cnt 8
    
    #  TAG: max_open_disk_fds
    #	To avoid having disk as the I/O bottleneck Squid can optionally
    #	bypass the on-disk cache if more than this amount of disk file
    #	descriptors are open.
    #
    #	A value of 0 indicates no limit.
    #
    #Default:
    # max_open_disk_fds 0
    
    #  TAG: offline_mode
    #	Enable this option and Squid will never try to validate cached
    #	objects.
    #
    #Default:
    # offline_mode off
    
    #  TAG: uri_whitespace
    #	What to do with requests that have whitespace characters in the
    #	URI.  Options:
    #
    #	strip:  The whitespace characters are stripped out of the URL.
    #		This is the behavior recommended by RFC2396.
    #	deny:   The request is denied.  The user receives an "Invalid
    #		Request" message.
    #	allow:  The request is allowed and the URI is not changed.  The
    #		whitespace characters remain in the URI.  Note the
    #		whitespace is passed to redirector processes if they
    #		are in use.
    #	encode:	The request is allowed and the whitespace characters are
    #		encoded according to RFC1738.  This could be considered
    #		a violation of the HTTP/1.1
    #		RFC because proxies are not allowed to rewrite URI's.
    #	chop:	The request is allowed and the URI is chopped at the
    #		first whitespace.  This might also be considered a
    #		violation.
    #
    #Default:
    # uri_whitespace strip
    
    #  TAG: broken_posts
    #	A list of ACL elements which, if matched, causes Squid to send
    #	an extra CRLF pair after the body of a PUT/POST request.
    #
    #	Some HTTP servers has broken implementations of PUT/POST,
    #	and rely on an extra CRLF pair sent by some WWW clients.
    #
    #	Quote from RFC2068 section 4.1 on this matter:
    #
    #	  Note: certain buggy HTTP/1.0 client implementations generate an
    #	  extra CRLF's after a POST request. To restate what is explicitly
    #	  forbidden by the BNF, an HTTP/1.1 client must not preface or follow
    #	  a request with an extra CRLF.
    #
    #Example:
    # acl buggy_server url_regex ^http://....
    # broken_posts allow buggy_server
    #
    #Default:
    # none
    
    #  TAG: mcast_miss_addr
    # Note: This option is only available if Squid is rebuilt with the
    #       --enable-multicast-miss option
    #
    #	If you enable this option, every "cache miss" URL will
    #	be sent out on the specified multicast address.
    #
    #	Do not enable this option unless you are are absolutely
    #	certain you understand what you are doing.
    #
    #Default:
    # mcast_miss_addr 255.255.255.255
    
    #  TAG: mcast_miss_ttl
    # Note: This option is only available if Squid is rebuilt with the
    #       --enable-multicast-miss option
    #
    #	This is the time-to-live value for packets multicasted
    #	when multicasting off cache miss URLs is enabled.  By
    #	default this is set to 'site scope', i.e. 16.
    #
    #Default:
    # mcast_miss_ttl 16
    
    #  TAG: mcast_miss_port
    # Note: This option is only available if Squid is rebuilt with the
    #       --enable-multicast-miss option
    #
    #	This is the port number to be used in conjunction with
    #	'mcast_miss_addr'.
    #
    #Default:
    # mcast_miss_port 3135
    
    #  TAG: mcast_miss_encode_key
    # Note: This option is only available if Squid is rebuilt with the
    #       --enable-multicast-miss option
    #
    #	The URLs that are sent in the multicast miss stream are
    #	encrypted.  This is the encryption key.
    #
    #Default:
    # mcast_miss_encode_key XXXXXXXXXXXXXXXX
    
    #  TAG: nonhierarchical_direct
    #	By default, Squid will send any non-hierarchical requests
    #	(matching hierarchy_stoplist or not cacheable request type) direct
    #	to origin servers.
    #
    #	If you set this to off, Squid will prefer to send these
    #	requests to parents.
    #
    #	Note that in most configurations, by turning this off you will only
    #	add latency to these request without any improvement in global hit
    #	ratio.
    #
    #	If you are inside an firewall see never_direct instead of
    #	this directive.
    #
    #Default:
    # nonhierarchical_direct on
    
    #  TAG: prefer_direct
    #	Normally Squid tries to use parents for most requests. If you for some
    #	reason like it to first try going direct and only use a parent if
    #	going direct fails set this to on.
    #
    #	By combining nonhierarchical_direct off and prefer_direct on you
    #	can set up Squid to use a parent as a backup path if going direct
    #	fails.
    #
    #	Note: If you want Squid to use parents for all requests see
    #	the never_direct directive. prefer_direct only modifies how Squid
    #	acts on cacheable requests.
    #
    #Default:
    # prefer_direct off
    
    #  TAG: strip_query_terms
    #	By default, Squid strips query terms from requested URLs before
    #	logging.  This protects your user's privacy.
    #
    #Default:
    # strip_query_terms on
    
    #  TAG: coredump_dir
    #	By default Squid leaves core files in the directory from where
    #	it was started. If you set 'coredump_dir' to a directory
    #	that exists, Squid will chdir() to that directory at startup
    #	and coredump files will be left there.
    #
    #Default:
    # coredump_dir none
    #
    # Leave coredumps in the first cache dir
    coredump_dir /var/spool/squid
    
    #  TAG: redirector_bypass
    #	When this is 'on', a request will not go through the
    #	redirector if all redirectors are busy.  If this is 'off'
    #	and the redirector queue grows too large, Squid will exit
    #	with a FATAL error and ask you to increase the number of
    #	redirectors.  You should only enable this if the redirectors
    #	are not critical to your caching system.  If you use
    #	redirectors for access control, and you enable this option,
    #	users may have access to pages they should not
    #	be allowed to request.
    #
    #Default:
    # redirector_bypass off
    
    #  TAG: ignore_unknown_nameservers
    #	By default Squid checks that DNS responses are received
    #	from the same IP addresses they are sent to.  If they
    #	don't match, Squid ignores the response and writes a warning
    #	message to cache.log.  You can allow responses from unknown
    #	nameservers by setting this option to 'off'.
    #
    #Default:
    # ignore_unknown_nameservers on
    
    #  TAG: digest_generation
    #	This controls whether the server will generate a Cache Digest
    #	of its contents.  By default, Cache Digest generation is
    #	enabled if Squid is compiled with USE_CACHE_DIGESTS defined.
    #
    #Default:
    # digest_generation on
    
    #  TAG: digest_bits_per_entry
    #	This is the number of bits of the server's Cache Digest which
    #	will be associated with the Digest entry for a given HTTP
    #	Method and URL (public key) combination.  The default is 5.
    #
    #Default:
    # digest_bits_per_entry 5
    
    #  TAG: digest_rebuild_period	(seconds)
    #	This is the number of seconds between Cache Digest rebuilds.
    #
    #Default:
    # digest_rebuild_period 1 hour
    
    #  TAG: digest_rewrite_period	(seconds)
    #	This is the number of seconds between Cache Digest writes to
    #	disk.
    #
    #Default:
    # digest_rewrite_period 1 hour
    
    #  TAG: digest_swapout_chunk_size	(bytes)
    #	This is the number of bytes of the Cache Digest to write to
    #	disk at a time.  It defaults to 4096 bytes (4KB), the Squid
    #	default swap page.
    #
    #Default:
    # digest_swapout_chunk_size 4096 bytes
    
    #  TAG: digest_rebuild_chunk_percentage	(percent, 0-100)
    #	This is the percentage of the Cache Digest to be scanned at a
    #	time.  By default it is set to 10% of the Cache Digest.
    #
    #Default:
    # digest_rebuild_chunk_percentage 10
    
    #  TAG: chroot
    #	Use this to have Squid do a chroot() while initializing.  This
    #	also causes Squid to fully drop root privileges after
    #	initializing.  This means, for example, that if you use a HTTP
    #	port less than 1024 and try to reconfigure, you will get an
    #	error.
    #
    #Default:
    # none
    
    #  TAG: client_persistent_connections
    #  TAG: server_persistent_connections
    #	Persistent connection support for clients and servers.  By
    #	default, Squid uses persistent connections (when allowed)
    #	with its clients and servers.  You can use these options to
    #	disable persistent connections with clients and/or servers.
    #
    #Default:
    # client_persistent_connections on
    # server_persistent_connections on
    
    #  TAG: persistent_connection_after_error
    #	With this directive the use of persistent connections after
    #	HTTP errors can be disabled. Useful if you have clients
    #	who fail to handle errors on persistent connections proper.
    #
    #Default:
    # persistent_connection_after_error off
    
    #  TAG: detect_broken_pconn
    #	Some servers have been found to incorrectly signal the use
    #	of HTTP/1.0 persistent connections even on replies not
    #	compatible, causing significant delays. This server problem
    #	has mostly been seen on redirects.
    #
    #	By enabling this directive Squid attempts to detect such
    #	broken replies and automatically assume the reply is finished
    #	after 10 seconds timeout.
    #
    #Default:
    # detect_broken_pconn off
    
    #  TAG: balance_on_multiple_ip
    #	Some load balancing servers based on round robin DNS have been 
    #	found not to preserve user session state across requests
    #	to different IP addresses.
    #
    #	By default Squid rotates IP's per request. By disabling
    #	this directive only connection failure triggers rotation.
    #
    #Default:
    # balance_on_multiple_ip on
    
    #  TAG: pipeline_prefetch
    #	To boost the performance of pipelined requests to closer
    #	match that of a non-proxied environment Squid can try to fetch
    #	up to two requests in parallel from a pipeline.
    #
    #	Defaults to off for bandwidth management and access logging
    #	reasons.
    #
    #Default:
    # pipeline_prefetch off
    
    #  TAG: extension_methods
    #	Squid only knows about standardized HTTP request methods.
    #	You can add up to 20 additional "extension" methods here.
    #
    #Default:
    # none
    
    #  TAG: request_entities
    #	Squid defaults to deny GET and HEAD requests with request entities,
    #	as the meaning of such requests are undefined in the HTTP standard
    #	even if not explicitly forbidden.
    #
    #	Set this directive to on if you have clients which insists
    #	on sending request entities in GET or HEAD requests. But be warned
    #	that there is server software (both proxies and web servers) which
    #	can fail to properly process this kind of request which may make you
    #	vulnerable to cache pollution attacks if enabled.
    #
    #Default:
    # request_entities off
    
    #  TAG: high_response_time_warning	(msec)
    #	If the one-minute median response time exceeds this value,
    #	Squid prints a WARNING with debug level 0 to get the
    #	administrators attention.  The value is in milliseconds.
    #
    #Default:
    # high_response_time_warning 0
    
    #  TAG: high_page_fault_warning
    #	If the one-minute average page fault rate exceeds this
    #	value, Squid prints a WARNING with debug level 0 to get
    #	the administrators attention.  The value is in page faults
    #	per second.
    #
    #Default:
    # high_page_fault_warning 0
    
    #  TAG: high_memory_warning
    #	If the memory usage (as determined by mallinfo) exceeds
    #	value, Squid prints a WARNING with debug level 0 to get
    #	the administrators attention.
    #
    #Default:
    # high_memory_warning 0
    
    #  TAG: store_dir_select_algorithm
    #	Set this to 'round-robin' as an alternative.
    #
    #Default:
    # store_dir_select_algorithm least-load
    
    #  TAG: forward_log
    # Note: This option is only available if Squid is rebuilt with the
    #       --enable-forward-log option
    #
    #	Logs the server-side requests.
    #
    #	This is currently work in progress.
    #
    #Default:
    # none
    
    #  TAG: ie_refresh	on|off
    #	Microsoft Internet Explorer up until version 5.5 Service
    #	Pack 1 has an issue with transparent proxies, wherein it
    #	is impossible to force a refresh.  Turning this on provides
    #	a partial fix to the problem, by causing all IMS-REFRESH
    #	requests from older IE versions to check the origin server
    #	for fresh content.  This reduces hit ratio by some amount
    #	(~10% in my experience), but allows users to actually get
    #	fresh content when they want it.  Note that because Squid
    #	cannot tell if the user is using 5.5 or 5.5SP1, the behavior
    #	of 5.5 is unchanged from old versions of Squid (i.e. a
    #	forced refresh is impossible).  Newer versions of IE will,
    #	hopefully, continue to have the new behavior and will be
    #	handled based on that assumption.  This option defaults to
    #	the old Squid behavior, which is better for hit ratios but
    #	worse for clients using IE, if they need to be able to
    #	force fresh content.
    #
    #Default:
    # ie_refresh off
    
    #  TAG: vary_ignore_expire	on|off
    #	Many HTTP servers supporting Vary gives such objects
    #	immediate expiry time with no cache-control header
    #	when requested by a HTTP/1.0 client. This option
    #	enables Squid to ignore such expiry times until
    #	HTTP/1.1 is fully implemented.
    #	WARNING: This may eventually cause some varying
    #	objects not intended for caching to get cached.
    #
    #Default:
    # vary_ignore_expire off
    
    #  TAG: sleep_after_fork	(microseconds)
    #	When this is set to a non-zero value, the main Squid process
    #	sleeps the specified number of microseconds after a fork()
    #	system call. This sleep may help the situation where your
    #	system reports fork() failures due to lack of (virtual)
    #	memory. Note, however, that if you have a lot of child
    #	processes, these sleep delays will add up and your
    #	Squid will not service requests for some amount of time
    #	until all the child processes have been started.
    #	On Windows value less then 1000 (1 milliseconds) are
    #	rounded to 1000.
    #
    #Default:
    # sleep_after_fork 0
    
    #  TAG: minimum_expiry_time	(seconds)
    #	The minimum caching time according to (Expires - Date)
    #	Headers Squid honors if the object can't be revalidated
    #	defaults to 60 seconds. In reverse proxy enorinments it
    #	might be desirable to honor shorter object lifetimes. It
    #	is most likely better to make your server return a
    #	meaningful Last-Modified header however.
    #
    #Default:
    # minimum_expiry_time 60 seconds
    
    #  TAG: relaxed_header_parser	on|off|warn
    #	In the default "on" setting Squid accepts certain forms
    #	of non-compliant HTTP messages where it is unambiguous
    #	what the sending application intended even if the message
    #	is not correctly formatted. The messages is then normalized
    #	to the correct form when forwarded by Squid.
    #
    #	If set to "warn" then a warning will be emitted in cache.log
    #	each time such HTTP error is encountered.
    #
    #	If set to "off" then such HTTP errors will cause the request
    #	or response to be rejected.
    #
    #Default:
    # relaxed_header_parser on
    
    
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. Dizzy

    Dizzy Brain Damage

    Dabei seit:
    02.05.2007
    Beiträge:
    857
    Zustimmungen:
    0
    Ort:
    Graz
    Hi,

    ich benutze Squid selbst nicht, aber folgende Zeile sieht doch verdächtig aus:

    Code:
    acl Safe_ports port 80
    Kommentier die mal aus.
     
  4. #3 JackJTP, 09.03.2009
    Zuletzt bearbeitet: 09.03.2009
    JackJTP

    JackJTP Grünschnabel

    Dabei seit:
    09.03.2009
    Beiträge:
    4
    Zustimmungen:
    0
    hatte leider keinen effekt auf mein problem. der browser der über den proxy geht bekommt ne verbindung, der andere nicht.
    .
    .
    .
    EDIT (autom. Beitragszusammenführung) :
    .

    Port 80 ist nicht mal mehr ohne proxy erreichbar wenn ich den squid ausschalte. woran bitte kann dass denn nun liegen? ich nutze xampp als webserver
     
  5. #4 codc, 09.03.2009
    Zuletzt bearbeitet: 09.03.2009
    codc

    codc /dev/null

    Dabei seit:
    12.01.2004
    Beiträge:
    607
    Zustimmungen:
    0
    Das ist kein Webserver sondern eine Testumgebung (Apache, MySQL, PHP und noch ein wenig mehr) und soll nicht im Internet und besonders auf einem Rootserver betrieben werden. Glaubst du dass du reif und erfahren genug für einen Root-Server bist? Ich möchte das mal ziemlich bezweifeln.

    http://root-und-kein-plan.ath.cx/ Zum Nachlesen ....
     
  6. #5 JackJTP, 09.03.2009
    Zuletzt bearbeitet: 09.03.2009
    JackJTP

    JackJTP Grünschnabel

    Dabei seit:
    09.03.2009
    Beiträge:
    4
    Zustimmungen:
    0
    vielen dank- genau so eine hilfe erwartet man. unqualifizierte kommentare kann ich mir auch selber posten.

    ich nutze den xampp nur als testumgebung - so als kleine information am rande. und ich nutze auch NUR den apache unter xampp - ftp, mysql, webmin etc unter xampp sind deaktiviert. ebenfalls sind alle redirects zu steuerelementen deaktiviert.

    im grunde könnte ich den apache auch einfach so installieren aber wie schon gesagt- ich nutze es als testumgebung und manchmal teste ich eben auch mit mysql etc. und habe schlicht keine lust für tests alles einzurichten.

    unter normalumständen ist der port 80, also wenn ich nicht gerade etwas TESTE, komplett dicht. wie nahezu alles was ich nicht für den eigentlichen nutzen des servers benötige. sprich: iptables, default action drop.

    wenn du nun etwas hilfreiches zu sagen hast, lass dich nicht aufhalten- andernfalls such dir einen thread in dem jemand keine hilfe sondern spass sucht ;)
     
  7. Anzeige

    Vielleicht findest du HIER Antworten.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  8. #6 codc, 09.03.2009
    Zuletzt bearbeitet: 10.03.2009
    codc

    codc /dev/null

    Dabei seit:
    12.01.2004
    Beiträge:
    607
    Zustimmungen:
    0
    Kleiner Tip wenn du Konfigs postest schick sie vorher mit Pipe durch grep -v '#' dann muss man sich nicht durch die ganzen Kommentare wühlen.
    Also
    Code:
    cat <PathToFile/Filename> | grep -v '#' > ~/<konfig_ohne_#>
    
    Ich lese jedenfalls so einen Müll nicht und versuche den Fehler zu finden.

    Ich weiss oben das ist useless use of pipe
    Code:
    grep -v '#' <PathToFile/Filename> >~/<konfig_ohne_#>
    
    geht natürlich auch
     
  9. #7 JackJTP, 10.03.2009
    JackJTP

    JackJTP Grünschnabel

    Dabei seit:
    09.03.2009
    Beiträge:
    4
    Zustimmungen:
    0
    naja- ich habe den fehler nun auch ohne deine gnaden gefunden- es war allerdings meilenweit von squid entfernt. naja, so weit nun auch nicht. ich habe webmin als standalone auf dem root installiert und squid damit zu konfigurieren versucht- in meinem wlden rumgeklicke auf der suche nach einer bestimmten einstellung habe ich den webmin versehentlich veranlasst, der firewall einen port redirect aufzuzwingen.

    naja- den wieder entfernt und alles funktioniert bestens. die ganze aufregung war also im grunde umsonst- und kostenlos dazu. aber falls jemandem das gleiche passieren sollte kann er/sie ja aus meinen fehlern lernen.

    aber danke für den tip mit grep ... das ist böse nützlich ;)
     
Thema:

Squid nur zum maskieren der eigenen IP, nicht für Webserver auf port 80

Die Seite wird geladen...

Squid nur zum maskieren der eigenen IP, nicht für Webserver auf port 80 - Ähnliche Themen

  1. Ubuntu 14.04 Squid3 zum Webseiten sperren

    Ubuntu 14.04 Squid3 zum Webseiten sperren: Hallo, ich habe mich nun nochmal an ein kleines Projekt rangemacht zum sperren von Webseiten über Squid. Folgende Konfiguration habe ich in...
  2. Squid3 als Reverse Proxy

    Squid3 als Reverse Proxy: Hallo zusammen Ich hoffe, ihr könnt mir hier weiterhelfen, stehe irgendwie was Squid angeht mächtig auf dem Schlauch. Ich möchte Squid3 als...
  3. SquidGuard - urls-Eintraege werden z.T. nicht gefiltert

    SquidGuard - urls-Eintraege werden z.T. nicht gefiltert: Hallo, bei mir läuft Squid + SquidGuard eigentlich ohne Probleme, aber seit ca. zwei Tagen kämpfe ich hier mit einigen Porn-Seiten, die sich...
  4. Squid als RPCoHTTPS Proxy für Outlook Anywhere

    Squid als RPCoHTTPS Proxy für Outlook Anywhere: Hallo Community, ich habe bereits versucht in einem anderen Forum Hilfe zu finden leider ohne Erfolg, darum versuche ich nochmal hier mein...
  5. Squid Ausnahmen für allg. Downloadsperre

    Squid Ausnahmen für allg. Downloadsperre: Hallo zusammen, ich habe im Netzwerk einen Proxy auf dem Squid läuft. Hier wird über eine Textdatei festgelegt, welche Dateiendungen nicht...