]>
Commit | Line | Data |
---|---|---|
4ac4a490 | 1 | ## Copyright (C) 1996-2017 The Squid Software Foundation and contributors |
5d28d44b AJ |
2 | ## |
3 | ## Squid software is distributed under GPLv2+ license and includes | |
4 | ## contributions from numerous individuals and organizations. | |
5 | ## Please see the COPYING and CONTRIBUTORS files for details. | |
6 | ## | |
9cef6668 | 7 | |
0f74202c | 8 | COMMENT_START |
ad12fb4b | 9 | WELCOME TO @SQUID@ |
cccac0a2 | 10 | ---------------------------- |
5945964d AJ |
11 | |
12 | This is the documentation for the Squid configuration file. | |
13 | This documentation can also be found online at: | |
14 | http://www.squid-cache.org/Doc/config/ | |
15 | ||
16 | You may wish to look at the Squid home page and wiki for the | |
17 | FAQ and other documentation: | |
18 | http://www.squid-cache.org/ | |
19 | http://wiki.squid-cache.org/SquidFaq | |
20 | http://wiki.squid-cache.org/ConfigExamples | |
21 | ||
22 | This documentation shows what the defaults for various directives | |
23 | happen to be. If you don't need to change the default, you should | |
24 | leave the line out of your squid.conf in most cases. | |
25 | ||
26 | In some cases "none" refers to no default setting at all, | |
27 | while in other cases it refers to the value of the option | |
28 | - the comments for that keyword indicate if this is the case. | |
debd9a31 | 29 | |
cccac0a2 | 30 | COMMENT_END |
3a278cb8 | 31 | |
592a09dc | 32 | COMMENT_START |
33 | Configuration options can be included using the "include" directive. | |
5945964d | 34 | Include takes a list of files to include. Quoting and wildcards are |
592a09dc | 35 | supported. |
36 | ||
37 | For example, | |
38 | ||
39 | include /path/to/included/file/squid.acl.config | |
40 | ||
41 | Includes can be nested up to a hard-coded depth of 16 levels. | |
42 | This arbitrary restriction is to prevent recursive include references | |
43 | from causing Squid entering an infinite loop whilst trying to load | |
44 | configuration files. | |
d4a3e179 | 45 | |
a345387f AJ |
46 | Values with byte units |
47 | ||
a01a87d9 AJ |
48 | Squid accepts size units on some size related directives. All |
49 | such directives are documented with a default value displaying | |
50 | a unit. | |
a345387f AJ |
51 | |
52 | Units accepted by Squid are: | |
a01a87d9 AJ |
53 | bytes - byte |
54 | KB - Kilobyte (1024 bytes) | |
a345387f AJ |
55 | MB - Megabyte |
56 | GB - Gigabyte | |
d4a3e179 | 57 | |
2eceb328 CT |
58 | Values with spaces, quotes, and other special characters |
59 | ||
60 | Squid supports directive parameters with spaces, quotes, and other | |
61 | special characters. Surround such parameters with "double quotes". Use | |
62 | the configuration_includes_quoted_values directive to enable or | |
63 | disable that support. | |
64 | ||
65 | Squid supports reading configuration option parameters from external | |
66 | files using the syntax: | |
67 | parameters("/path/filename") | |
68 | For example: | |
69 | acl whitelist dstdomain parameters("/etc/squid/whitelist.txt") | |
70 | ||
5735d30b AR |
71 | Conditional configuration |
72 | ||
73 | If-statements can be used to make configuration directives | |
74 | depend on conditions: | |
75 | ||
76 | if <CONDITION> | |
77 | ... regular configuration directives ... | |
78 | [else | |
79 | ... regular configuration directives ...] | |
80 | endif | |
81 | ||
82 | The else part is optional. The keywords "if", "else", and "endif" | |
83 | must be typed on their own lines, as if they were regular | |
84 | configuration directives. | |
85 | ||
5945964d AJ |
86 | NOTE: An else-if condition is not supported. |
87 | ||
5735d30b AR |
88 | These individual conditions types are supported: |
89 | ||
90 | true | |
91 | Always evaluates to true. | |
92 | false | |
93 | Always evaluates to false. | |
94 | <integer> = <integer> | |
95 | Equality comparison of two integer numbers. | |
96 | ||
97 | ||
d4a3e179 AR |
98 | SMP-Related Macros |
99 | ||
100 | The following SMP-related preprocessor macros can be used. | |
101 | ||
102 | ${process_name} expands to the current Squid process "name" | |
103 | (e.g., squid1, squid2, or cache1). | |
104 | ||
105 | ${process_number} expands to the current Squid process | |
106 | identifier, which is an integer number (e.g., 1, 2, 3) unique | |
6fe8c876 AJ |
107 | across all Squid processes of the current service instance. |
108 | ||
109 | ${service_name} expands into the current Squid service instance | |
110 | name identifier which is provided by -n on the command line. | |
111 | ||
cde8f31b NH |
112 | Logformat Macros |
113 | ||
114 | Logformat macros can be used in many places outside of the logformat | |
115 | directive. In theory, all of the logformat codes can be used as %macros, | |
116 | where they are supported. In practice, a %macro expands as a dash (-) when | |
117 | the transaction does not yet have enough information and a value is needed. | |
118 | ||
119 | There is no definitive list of what tokens are available at the various | |
120 | stages of the transaction. | |
121 | ||
122 | And some information may already be available to Squid but not yet | |
123 | committed where the macro expansion code can access it (report | |
124 | such instances!). The macro will be expanded into a single dash | |
125 | ('-') in such cases. Not all macros have been tested. | |
126 | ||
592a09dc | 127 | COMMENT_END |
128 | ||
25234ebd AJ |
129 | # options still not yet ported from 2.7 to 3.x |
130 | NAME: broken_vary_encoding | |
131 | TYPE: obsolete | |
132 | DOC_START | |
133 | This option is not yet supported by Squid-3. | |
134 | DOC_END | |
135 | ||
136 | NAME: cache_vary | |
137 | TYPE: obsolete | |
138 | DOC_START | |
139 | This option is not yet supported by Squid-3. | |
140 | DOC_END | |
141 | ||
25234ebd AJ |
142 | NAME: error_map |
143 | TYPE: obsolete | |
144 | DOC_START | |
145 | This option is not yet supported by Squid-3. | |
146 | DOC_END | |
147 | ||
148 | NAME: external_refresh_check | |
149 | TYPE: obsolete | |
150 | DOC_START | |
151 | This option is not yet supported by Squid-3. | |
152 | DOC_END | |
153 | ||
96598f93 | 154 | NAME: location_rewrite_program location_rewrite_access location_rewrite_children location_rewrite_concurrency |
25234ebd AJ |
155 | TYPE: obsolete |
156 | DOC_START | |
157 | This option is not yet supported by Squid-3. | |
158 | DOC_END | |
159 | ||
96598f93 | 160 | NAME: refresh_stale_hit |
25234ebd AJ |
161 | TYPE: obsolete |
162 | DOC_START | |
163 | This option is not yet supported by Squid-3. | |
164 | DOC_END | |
165 | ||
6eb545bc | 166 | # Options removed in 4.x |
f1a5d071 AJ |
167 | NAME: cache_peer_domain cache_host_domain |
168 | TYPE: obsolete | |
169 | DOC_START | |
170 | Replace with dstdomain ACLs and cache_peer_access. | |
171 | DOC_END | |
172 | ||
6eb545bc AJ |
173 | NAME: ie_refresh |
174 | TYPE: obsolete | |
175 | DOC_START | |
176 | Remove this line. The behaviour enabled by this is no longer needed. | |
177 | DOC_END | |
178 | ||
7e62a74f AJ |
179 | NAME: sslproxy_cafile |
180 | TYPE: obsolete | |
181 | DOC_START | |
182 | Remove this line. Use tls_outgoing_options cafile= instead. | |
183 | DOC_END | |
184 | ||
185 | NAME: sslproxy_capath | |
186 | TYPE: obsolete | |
187 | DOC_START | |
188 | Remove this line. Use tls_outgoing_options capath= instead. | |
189 | DOC_END | |
190 | ||
191 | NAME: sslproxy_cipher | |
192 | TYPE: obsolete | |
193 | DOC_START | |
194 | Remove this line. Use tls_outgoing_options cipher= instead. | |
195 | DOC_END | |
196 | ||
197 | NAME: sslproxy_client_certificate | |
198 | TYPE: obsolete | |
199 | DOC_START | |
200 | Remove this line. Use tls_outgoing_options cert= instead. | |
201 | DOC_END | |
202 | ||
203 | NAME: sslproxy_client_key | |
204 | TYPE: obsolete | |
205 | DOC_START | |
206 | Remove this line. Use tls_outgoing_options key= instead. | |
207 | DOC_END | |
208 | ||
209 | NAME: sslproxy_flags | |
210 | TYPE: obsolete | |
211 | DOC_START | |
212 | Remove this line. Use tls_outgoing_options flags= instead. | |
213 | DOC_END | |
214 | ||
215 | NAME: sslproxy_options | |
216 | TYPE: obsolete | |
217 | DOC_START | |
218 | Remove this line. Use tls_outgoing_options options= instead. | |
219 | DOC_END | |
220 | ||
221 | NAME: sslproxy_version | |
222 | TYPE: obsolete | |
223 | DOC_START | |
1cc44095 | 224 | Remove this line. Use tls_outgoing_options options= instead. |
7e62a74f AJ |
225 | DOC_END |
226 | ||
9967aef6 AJ |
227 | # Options removed in 3.5 |
228 | NAME: hierarchy_stoplist | |
229 | TYPE: obsolete | |
230 | DOC_START | |
231 | Remove this line. Use always_direct or cache_peer_access ACLs instead if you need to prevent cache_peer use. | |
232 | DOC_END | |
233 | ||
a8f70484 | 234 | # Options removed in 3.4 |
74d81220 AJ |
235 | NAME: log_access |
236 | TYPE: obsolete | |
237 | DOC_START | |
238 | Remove this line. Use acls with access_log directives to control access logging | |
239 | DOC_END | |
240 | ||
241 | NAME: log_icap | |
242 | TYPE: obsolete | |
243 | DOC_START | |
244 | Remove this line. Use acls with icap_log directives to control icap logging | |
245 | DOC_END | |
246 | ||
96598f93 AJ |
247 | # Options Removed in 3.3 |
248 | NAME: ignore_ims_on_miss | |
25234ebd AJ |
249 | TYPE: obsolete |
250 | DOC_START | |
2d4eefd9 | 251 | Remove this line. The HTTP/1.1 feature is now configured by 'cache_miss_revalidate'. |
25234ebd AJ |
252 | DOC_END |
253 | ||
76f44481 | 254 | # Options Removed in 3.2 |
16cd62b7 AJ |
255 | NAME: chunked_request_body_max_size |
256 | TYPE: obsolete | |
257 | DOC_START | |
258 | Remove this line. Squid is now HTTP/1.1 compliant. | |
259 | DOC_END | |
260 | ||
74d81220 | 261 | NAME: dns_v4_fallback |
76f44481 AJ |
262 | TYPE: obsolete |
263 | DOC_START | |
74d81220 | 264 | Remove this line. Squid performs a 'Happy Eyeballs' algorithm, the 'fallback' algorithm is no longer relevant. |
76f44481 AJ |
265 | DOC_END |
266 | ||
74d81220 | 267 | NAME: emulate_httpd_log |
6e095b46 AJ |
268 | TYPE: obsolete |
269 | DOC_START | |
74d81220 AJ |
270 | Replace this with an access_log directive using the format 'common' or 'combined'. |
271 | DOC_END | |
272 | ||
273 | NAME: forward_log | |
274 | TYPE: obsolete | |
275 | DOC_START | |
276 | Use a regular access.log with ACL limiting it to MISS events. | |
6e095b46 AJ |
277 | DOC_END |
278 | ||
76f44481 AJ |
279 | NAME: ftp_list_width |
280 | TYPE: obsolete | |
281 | DOC_START | |
282 | Remove this line. Configure FTP page display using the CSS controls in errorpages.css instead. | |
283 | DOC_END | |
284 | ||
74d81220 AJ |
285 | NAME: ignore_expect_100 |
286 | TYPE: obsolete | |
287 | DOC_START | |
288 | Remove this line. The HTTP/1.1 feature is now fully supported by default. | |
289 | DOC_END | |
290 | ||
291 | NAME: log_fqdn | |
292 | TYPE: obsolete | |
293 | DOC_START | |
294 | Remove this option from your config. To log FQDN use %>A in the log format. | |
295 | DOC_END | |
296 | ||
297 | NAME: log_ip_on_direct | |
298 | TYPE: obsolete | |
299 | DOC_START | |
300 | Remove this option from your config. To log server or peer names use %<A in the log format. | |
301 | DOC_END | |
302 | ||
38493d67 AJ |
303 | NAME: maximum_single_addr_tries |
304 | TYPE: obsolete | |
305 | DOC_START | |
306 | Replaced by connect_retries. The behaviour has changed, please read the documentation before altering. | |
307 | DOC_END | |
308 | ||
74d81220 AJ |
309 | NAME: referer_log referrer_log |
310 | TYPE: obsolete | |
311 | DOC_START | |
312 | Replace this with an access_log directive using the format 'referrer'. | |
313 | DOC_END | |
314 | ||
4ded749e AJ |
315 | NAME: update_headers |
316 | TYPE: obsolete | |
317 | DOC_START | |
318 | Remove this line. The feature is supported by default in storage types where update is implemented. | |
319 | DOC_END | |
320 | ||
76f44481 AJ |
321 | NAME: url_rewrite_concurrency |
322 | TYPE: obsolete | |
323 | DOC_START | |
324 | Remove this line. Set the 'concurrency=' option of url_rewrite_children instead. | |
325 | DOC_END | |
326 | ||
74d81220 AJ |
327 | NAME: useragent_log |
328 | TYPE: obsolete | |
329 | DOC_START | |
330 | Replace this with an access_log directive using the format 'useragent'. | |
331 | DOC_END | |
332 | ||
76f44481 AJ |
333 | # Options Removed in 3.1 |
334 | NAME: dns_testnames | |
335 | TYPE: obsolete | |
336 | DOC_START | |
337 | Remove this line. DNS is no longer tested on startup. | |
338 | DOC_END | |
339 | ||
340 | NAME: extension_methods | |
341 | TYPE: obsolete | |
342 | DOC_START | |
343 | Remove this line. All valid methods for HTTP are accepted by default. | |
344 | DOC_END | |
345 | ||
c72a2049 AJ |
346 | # 2.7 Options Removed/Replaced in 3.2 |
347 | NAME: zero_buffers | |
348 | TYPE: obsolete | |
349 | DOC_NONE | |
350 | ||
76f44481 AJ |
351 | # 2.7 Options Removed/Replaced in 3.1 |
352 | NAME: incoming_rate | |
353 | TYPE: obsolete | |
354 | DOC_NONE | |
355 | ||
356 | NAME: server_http11 | |
357 | TYPE: obsolete | |
358 | DOC_START | |
359 | Remove this line. HTTP/1.1 is supported by default. | |
360 | DOC_END | |
361 | ||
362 | NAME: upgrade_http0.9 | |
363 | TYPE: obsolete | |
364 | DOC_START | |
365 | Remove this line. ICY/1.0 streaming protocol is supported by default. | |
366 | DOC_END | |
367 | ||
368 | NAME: zph_local zph_mode zph_option zph_parent zph_sibling | |
369 | TYPE: obsolete | |
370 | DOC_START | |
371 | Alter these entries. Use the qos_flows directive instead. | |
372 | DOC_END | |
373 | ||
374 | # Options Removed in 3.0 | |
375 | NAME: header_access | |
376 | TYPE: obsolete | |
377 | DOC_START | |
378 | Since squid-3.0 replace with request_header_access or reply_header_access | |
379 | depending on whether you wish to match client requests or server replies. | |
380 | DOC_END | |
381 | ||
382 | NAME: httpd_accel_no_pmtu_disc | |
383 | TYPE: obsolete | |
384 | DOC_START | |
385 | Since squid-3.0 use the 'disable-pmtu-discovery' flag on http_port instead. | |
386 | DOC_END | |
387 | ||
3b31a711 AJ |
388 | NAME: wais_relay_host |
389 | TYPE: obsolete | |
390 | DOC_START | |
391 | Replace this line with 'cache_peer' configuration. | |
392 | DOC_END | |
393 | ||
394 | NAME: wais_relay_port | |
395 | TYPE: obsolete | |
396 | DOC_START | |
397 | Replace this line with 'cache_peer' configuration. | |
398 | DOC_END | |
399 | ||
50ff42a2 AJ |
400 | COMMENT_START |
401 | OPTIONS FOR SMP | |
402 | ----------------------------------------------------------------------------- | |
403 | COMMENT_END | |
404 | ||
405 | NAME: workers | |
406 | TYPE: int | |
407 | LOC: Config.workers | |
408 | DEFAULT: 1 | |
409 | DEFAULT_DOC: SMP support disabled. | |
410 | DOC_START | |
411 | Number of main Squid processes or "workers" to fork and maintain. | |
412 | 0: "no daemon" mode, like running "squid -N ..." | |
413 | 1: "no SMP" mode, start one main Squid process daemon (default) | |
414 | N: start N main Squid process daemons (i.e., SMP mode) | |
415 | ||
416 | In SMP mode, each worker does nearly all what a single Squid daemon | |
417 | does (e.g., listen on http_port and forward HTTP requests). | |
418 | DOC_END | |
419 | ||
420 | NAME: cpu_affinity_map | |
421 | TYPE: CpuAffinityMap | |
422 | LOC: Config.cpuAffinityMap | |
423 | DEFAULT: none | |
424 | DEFAULT_DOC: Let operating system decide. | |
425 | DOC_START | |
426 | Usage: cpu_affinity_map process_numbers=P1,P2,... cores=C1,C2,... | |
427 | ||
428 | Sets 1:1 mapping between Squid processes and CPU cores. For example, | |
429 | ||
430 | cpu_affinity_map process_numbers=1,2,3,4 cores=1,3,5,7 | |
431 | ||
432 | affects processes 1 through 4 only and places them on the first | |
433 | four even cores, starting with core #1. | |
434 | ||
435 | CPU cores are numbered starting from 1. Requires support for | |
436 | sched_getaffinity(2) and sched_setaffinity(2) system calls. | |
437 | ||
438 | Multiple cpu_affinity_map options are merged. | |
439 | ||
440 | See also: workers | |
441 | DOC_END | |
442 | ||
c756d517 AR |
443 | NAME: shared_memory_locking |
444 | TYPE: YesNoNone | |
445 | COMMENT: on|off | |
446 | LOC: Config.shmLocking | |
447 | DEFAULT: off | |
448 | DOC_START | |
449 | Whether to ensure that all required shared memory is available by | |
450 | "locking" that shared memory into RAM when Squid starts. The | |
451 | alternative is faster startup time followed by slightly slower | |
452 | performance and, if not enough RAM is actually available during | |
453 | runtime, mysterious crashes. | |
454 | ||
455 | SMP Squid uses many shared memory segments. These segments are | |
456 | brought into Squid memory space using an mmap(2) system call. During | |
457 | Squid startup, the mmap() call often succeeds regardless of whether | |
458 | the system has enough RAM. In general, Squid cannot tell whether the | |
459 | kernel applies this "optimistic" memory allocation policy (but | |
460 | popular modern kernels usually use it). | |
461 | ||
462 | Later, if Squid attempts to actually access the mapped memory | |
463 | regions beyond what the kernel is willing to allocate, the | |
464 | "optimistic" kernel simply kills Squid kid with a SIGBUS signal. | |
465 | Some of the memory limits enforced by the kernel are currently | |
466 | poorly understood: We do not know how to detect and check them. This | |
467 | option ensures that the mapped memory will be available. | |
468 | ||
469 | This option may have a positive performance side-effect: Locking | |
470 | memory at start avoids runtime paging I/O. Paging slows Squid down. | |
471 | ||
472 | Locking memory may require a large enough RLIMIT_MEMLOCK OS limit, | |
473 | CAP_IPC_LOCK capability, or equivalent. | |
474 | DOC_END | |
475 | ||
00e2479d AR |
476 | NAME: hopeless_kid_revival_delay |
477 | COMMENT: time-units | |
478 | TYPE: time_t | |
479 | LOC: Config.hopelessKidRevivalDelay | |
480 | DEFAULT: 1 hour | |
481 | DOC_START | |
482 | Normally, when a kid process dies, Squid immediately restarts the | |
483 | kid. A kid experiencing frequent deaths is marked as "hopeless" for | |
484 | the duration specified by this directive. Hopeless kids are not | |
485 | automatically restarted. | |
486 | ||
487 | Currently, zero values are not supported because they result in | |
488 | misconfigured SMP Squid instances running forever, endlessly | |
489 | restarting each dying kid. To effectively disable hopeless kids | |
490 | revival, set the delay to a huge value (e.g., 1 year). | |
491 | ||
492 | Reconfiguration also clears all hopeless kids designations, allowing | |
493 | for manual revival of hopeless kids. | |
494 | DOC_END | |
495 | ||
5473c134 | 496 | COMMENT_START |
41bd17a4 | 497 | OPTIONS FOR AUTHENTICATION |
5473c134 | 498 | ----------------------------------------------------------------------------- |
499 | COMMENT_END | |
500 | ||
41bd17a4 | 501 | NAME: auth_param |
502 | TYPE: authparam | |
2f1431ea | 503 | IFDEF: USE_AUTH |
5c112575 | 504 | LOC: Auth::TheConfig.schemes |
cccac0a2 | 505 | DEFAULT: none |
506 | DOC_START | |
41bd17a4 | 507 | This is used to define parameters for the various authentication |
508 | schemes supported by Squid. | |
cccac0a2 | 509 | |
66c583dc | 510 | format: auth_param scheme parameter [setting] |
cccac0a2 | 511 | |
41bd17a4 | 512 | The order in which authentication schemes are presented to the client is |
513 | dependent on the order the scheme first appears in config file. IE | |
514 | has a bug (it's not RFC 2617 compliant) in that it will use the basic | |
515 | scheme if basic is the first entry presented, even if more secure | |
516 | schemes are presented. For now use the order in the recommended | |
517 | settings section below. If other browsers have difficulties (don't | |
518 | recognize the schemes offered even if you are using basic) either | |
519 | put basic first, or disable the other schemes (by commenting out their | |
520 | program entry). | |
cccac0a2 | 521 | |
41bd17a4 | 522 | Once an authentication scheme is fully configured, it can only be |
523 | shutdown by shutting squid down and restarting. Changes can be made on | |
524 | the fly and activated with a reconfigure. I.E. You can change to a | |
525 | different helper, but not unconfigure the helper completely. | |
cccac0a2 | 526 | |
41bd17a4 | 527 | Please note that while this directive defines how Squid processes |
528 | authentication it does not automatically activate authentication. | |
529 | To use authentication you must in addition make use of ACLs based | |
530 | on login name in http_access (proxy_auth, proxy_auth_regex or | |
531 | external with %LOGIN used in the format tag). The browser will be | |
532 | challenged for authentication on the first such acl encountered | |
533 | in http_access processing and will also be re-challenged for new | |
534 | login credentials if the request is being denied by a proxy_auth | |
535 | type acl. | |
cccac0a2 | 536 | |
41bd17a4 | 537 | WARNING: authentication can't be used in a transparently intercepting |
538 | proxy as the client then thinks it is talking to an origin server and | |
539 | not the proxy. This is a limitation of bending the TCP/IP protocol to | |
540 | transparently intercepting port 80, not a limitation in Squid. | |
b3567eb5 FC |
541 | Ports flagged 'transparent', 'intercept', or 'tproxy' have |
542 | authentication disabled. | |
cccac0a2 | 543 | |
d4806c91 CT |
544 | === Parameters common to all schemes. === |
545 | ||
546 | "program" cmdline | |
66c583dc | 547 | Specifies the command for the external authenticator. |
d4806c91 | 548 | |
66c583dc AJ |
549 | By default, each authentication scheme is not used unless a |
550 | program is specified. | |
cccac0a2 | 551 | |
66c583dc AJ |
552 | See http://wiki.squid-cache.org/Features/AddonHelpers for |
553 | more details on helper operations and creating your own. | |
5269ec0e | 554 | |
66c583dc AJ |
555 | "key_extras" format |
556 | Specifies a string to be append to request line format for | |
557 | the authentication helper. "Quoted" format values may contain | |
558 | spaces and logformat %macros. In theory, any logformat %macro | |
559 | can be used. In practice, a %macro expands as a dash (-) if | |
560 | the helper request is sent before the required macro | |
561 | information is available to Squid. | |
562 | ||
563 | By default, Squid uses request formats provided in | |
564 | scheme-specific examples below (search for %credentials). | |
565 | ||
566 | The expanded key_extras value is added to the Squid credentials | |
567 | cache and, hence, will affect authentication. It can be used to | |
568 | autenticate different users with identical user names (e.g., | |
569 | when user authentication depends on http_port). | |
570 | ||
571 | Avoid adding frequently changing information to key_extras. For | |
572 | example, if you add user source IP, and it changes frequently | |
573 | in your environment, then max_user_ip ACL is going to treat | |
574 | every user+IP combination as a unique "user", breaking the ACL | |
575 | and wasting a lot of memory on those user records. It will also | |
576 | force users to authenticate from scratch whenever their IP | |
577 | changes. | |
578 | ||
579 | "realm" string | |
580 | Specifies the protection scope (aka realm name) which is to be | |
581 | reported to the client for the authentication scheme. It is | |
582 | commonly part of the text the user will see when prompted for | |
583 | their username and password. | |
584 | ||
585 | For Basic the default is "Squid proxy-caching web server". | |
586 | For Digest there is no default, this parameter is mandatory. | |
587 | For NTLM and Negotiate this parameter is ignored. | |
5269ec0e | 588 | |
6082a0e2 EB |
589 | "children" numberofchildren [startup=N] [idle=N] [concurrency=N] |
590 | [queue-size=N] [on-persistent-overload=action] | |
5269ec0e | 591 | |
66c583dc AJ |
592 | The maximum number of authenticator processes to spawn. If |
593 | you start too few Squid will have to wait for them to process | |
594 | a backlog of credential verifications, slowing it down. When | |
595 | password verifications are done via a (slow) network you are | |
596 | likely to need lots of authenticator processes. | |
5269ec0e | 597 | |
66c583dc AJ |
598 | The startup= and idle= options permit some skew in the exact |
599 | amount run. A minimum of startup=N will begin during startup | |
600 | and reconfigure. Squid will start more in groups of up to | |
601 | idle=N in an attempt to meet traffic needs and to keep idle=N | |
602 | free above those traffic needs up to the maximum. | |
5269ec0e | 603 | |
66c583dc AJ |
604 | The concurrency= option sets the number of concurrent requests |
605 | the helper can process. The default of 0 is used for helpers | |
606 | who only supports one request at a time. Setting this to a | |
607 | number greater than 0 changes the protocol used to include a | |
608 | channel ID field first on the request/response line, allowing | |
609 | multiple requests to be sent to the same helper in parallel | |
610 | without waiting for the response. | |
cccac0a2 | 611 | |
66c583dc AJ |
612 | Concurrency must not be set unless it's known the helper |
613 | supports the input format with channel-ID fields. | |
cccac0a2 | 614 | |
6082a0e2 EB |
615 | The queue-size=N option sets the maximum number of queued |
616 | requests to N. The default maximum is 2*numberofchildren. Squid | |
617 | is allowed to temporarily exceed the configured maximum, marking | |
618 | the affected helper as "overloaded". If the helper overload | |
619 | lasts more than 3 minutes, the action prescribed by the | |
620 | on-persistent-overload option applies. | |
621 | ||
622 | The on-persistent-overload=action option specifies Squid | |
623 | reaction to a new helper request arriving when the helper | |
624 | has been overloaded for more that 3 minutes already. The number | |
625 | of queued requests determines whether the helper is overloaded | |
626 | (see the queue-size option). | |
627 | ||
628 | Two actions are supported: | |
629 | ||
630 | die Squid worker quits. This is the default behavior. | |
631 | ||
632 | ERR Squid treats the helper request as if it was | |
633 | immediately submitted, and the helper immediately | |
634 | replied with an ERR response. This action has no effect | |
635 | on the already queued and in-progress helper requests. | |
6825b101 | 636 | |
66c583dc AJ |
637 | NOTE: NTLM and Negotiate schemes do not support concurrency |
638 | in the Squid code module even though some helpers can. | |
307b83b7 | 639 | |
b2b09838 AJ |
640 | "keep_alive" on|off |
641 | If you experience problems with PUT/POST requests when using | |
642 | the NTLM or Negotiate schemes then you can try setting this | |
643 | to off. This will cause Squid to forcibly close the connection | |
644 | on the initial request where the browser asks which schemes | |
645 | are supported by the proxy. | |
9e7dbc51 | 646 | |
b2b09838 | 647 | For Basic and Digest this parameter is ignored. |
d2a89ac1 | 648 | |
66c583dc AJ |
649 | "utf8" on|off |
650 | HTTP uses iso-latin-1 as character set, while some | |
651 | authentication backends such as LDAP expects UTF-8. If this is | |
652 | set to on Squid will translate the HTTP iso-latin-1 charset to | |
653 | UTF-8 before sending the username and password to the helper. | |
d1b63fc8 | 654 | |
b2b09838 AJ |
655 | For NTLM and Negotiate this parameter is ignored. |
656 | ||
657 | IF HAVE_AUTH_MODULE_BASIC | |
658 | === Basic authentication parameters === | |
659 | ||
41bd17a4 | 660 | "credentialsttl" timetolive |
66c583dc AJ |
661 | Specifies how long squid assumes an externally validated |
662 | username:password pair is valid for - in other words how | |
663 | often the helper program is called for that user. Set this | |
664 | low to force revalidation with short lived passwords. | |
cccac0a2 | 665 | |
66c583dc AJ |
666 | NOTE: setting this high does not impact your susceptibility |
667 | to replay attacks unless you are using an one-time password | |
668 | system (such as SecureID). If you are using such a system, | |
669 | you will be vulnerable to replay attacks unless you also | |
670 | use the max_user_ip ACL in an http_access rule. | |
cccac0a2 | 671 | |
66c583dc AJ |
672 | "casesensitive" on|off |
673 | Specifies if usernames are case sensitive. Most user databases | |
674 | are case insensitive allowing the same username to be spelled | |
675 | using both lower and upper case letters, but some are case | |
676 | sensitive. This makes a big difference for user_max_ip ACL | |
677 | processing and similar. | |
cccac0a2 | 678 | |
66c583dc AJ |
679 | ENDIF |
680 | IF HAVE_AUTH_MODULE_DIGEST | |
681 | === Digest authentication parameters === | |
cccac0a2 | 682 | |
41bd17a4 | 683 | "nonce_garbage_interval" timeinterval |
66c583dc AJ |
684 | Specifies the interval that nonces that have been issued |
685 | to client_agent's are checked for validity. | |
cccac0a2 | 686 | |
41bd17a4 | 687 | "nonce_max_duration" timeinterval |
66c583dc AJ |
688 | Specifies the maximum length of time a given nonce will be |
689 | valid for. | |
cccac0a2 | 690 | |
41bd17a4 | 691 | "nonce_max_count" number |
66c583dc AJ |
692 | Specifies the maximum number of times a given nonce can be |
693 | used. | |
cccac0a2 | 694 | |
41bd17a4 | 695 | "nonce_strictness" on|off |
66c583dc AJ |
696 | Determines if squid requires strict increment-by-1 behavior |
697 | for nonce counts, or just incrementing (off - for use when | |
698 | user agents generate nonce counts that occasionally miss 1 | |
699 | (ie, 1,2,4,6)). Default off. | |
cccac0a2 | 700 | |
41bd17a4 | 701 | "check_nonce_count" on|off |
66c583dc AJ |
702 | This directive if set to off can disable the nonce count check |
703 | completely to work around buggy digest qop implementations in | |
704 | certain mainstream browser versions. Default on to check the | |
705 | nonce count to protect from authentication replay attacks. | |
cccac0a2 | 706 | |
41bd17a4 | 707 | "post_workaround" on|off |
66c583dc AJ |
708 | This is a workaround to certain buggy browsers who send an |
709 | incorrect request digest in POST requests when reusing the | |
710 | same nonce as acquired earlier on a GET request. | |
cccac0a2 | 711 | |
66c583dc | 712 | ENDIF |
527ee50d | 713 | |
66c583dc AJ |
714 | === Example Configuration === |
715 | ||
716 | This configuration displays the recommended authentication scheme | |
717 | order from most to least secure with recommended minimum configuration | |
718 | settings for each scheme: | |
e0855596 | 719 | |
41bd17a4 | 720 | #auth_param negotiate program <uncomment and complete this line to activate> |
48d54e4d | 721 | #auth_param negotiate children 20 startup=0 idle=1 |
e0855596 | 722 | # |
66c583dc | 723 | #auth_param digest program <uncomment and complete this line to activate> |
48d54e4d | 724 | #auth_param digest children 20 startup=0 idle=1 |
41bd17a4 | 725 | #auth_param digest realm Squid proxy-caching web server |
726 | #auth_param digest nonce_garbage_interval 5 minutes | |
727 | #auth_param digest nonce_max_duration 30 minutes | |
728 | #auth_param digest nonce_max_count 50 | |
e0855596 | 729 | # |
66c583dc AJ |
730 | #auth_param ntlm program <uncomment and complete this line to activate> |
731 | #auth_param ntlm children 20 startup=0 idle=1 | |
66c583dc | 732 | # |
41bd17a4 | 733 | #auth_param basic program <uncomment and complete this line> |
6f4d3ed6 | 734 | #auth_param basic children 5 startup=5 idle=1 |
41bd17a4 | 735 | #auth_param basic credentialsttl 2 hours |
41bd17a4 | 736 | DOC_END |
cccac0a2 | 737 | |
41bd17a4 | 738 | NAME: authenticate_cache_garbage_interval |
5db226c8 | 739 | IFDEF: USE_AUTH |
41bd17a4 | 740 | TYPE: time_t |
741 | DEFAULT: 1 hour | |
00ef8d82 | 742 | LOC: Auth::TheConfig.garbageCollectInterval |
41bd17a4 | 743 | DOC_START |
744 | The time period between garbage collection across the username cache. | |
4ded749e | 745 | This is a trade-off between memory utilization (long intervals - say |
41bd17a4 | 746 | 2 days) and CPU (short intervals - say 1 minute). Only change if you |
747 | have good reason to. | |
748 | DOC_END | |
cccac0a2 | 749 | |
41bd17a4 | 750 | NAME: authenticate_ttl |
5db226c8 | 751 | IFDEF: USE_AUTH |
41bd17a4 | 752 | TYPE: time_t |
753 | DEFAULT: 1 hour | |
00ef8d82 | 754 | LOC: Auth::TheConfig.credentialsTtl |
41bd17a4 | 755 | DOC_START |
756 | The time a user & their credentials stay in the logged in | |
757 | user cache since their last request. When the garbage | |
758 | interval passes, all user credentials that have passed their | |
759 | TTL are removed from memory. | |
760 | DOC_END | |
cccac0a2 | 761 | |
41bd17a4 | 762 | NAME: authenticate_ip_ttl |
5db226c8 | 763 | IFDEF: USE_AUTH |
41bd17a4 | 764 | TYPE: time_t |
00ef8d82 | 765 | LOC: Auth::TheConfig.ipTtl |
c35dd848 | 766 | DEFAULT: 1 second |
41bd17a4 | 767 | DOC_START |
768 | If you use proxy authentication and the 'max_user_ip' ACL, | |
769 | this directive controls how long Squid remembers the IP | |
770 | addresses associated with each user. Use a small value | |
771 | (e.g., 60 seconds) if your users might change addresses | |
4ded749e | 772 | quickly, as is the case with dialup. You might be safe |
41bd17a4 | 773 | using a larger value (e.g., 2 hours) in a corporate LAN |
774 | environment with relatively static address assignments. | |
775 | DOC_END | |
cccac0a2 | 776 | |
3d1e3e43 | 777 | COMMENT_START |
778 | ACCESS CONTROLS | |
779 | ----------------------------------------------------------------------------- | |
780 | COMMENT_END | |
781 | ||
41bd17a4 | 782 | NAME: external_acl_type |
783 | TYPE: externalAclHelper | |
784 | LOC: Config.externalAclHelperList | |
cccac0a2 | 785 | DEFAULT: none |
cccac0a2 | 786 | DOC_START |
41bd17a4 | 787 | This option defines external acl classes using a helper program |
788 | to look up the status | |
cccac0a2 | 789 | |
262eaf9a | 790 | external_acl_type name [options] FORMAT /path/to/helper [helper arguments] |
cccac0a2 | 791 | |
41bd17a4 | 792 | Options: |
cccac0a2 | 793 | |
41bd17a4 | 794 | ttl=n TTL in seconds for cached results (defaults to 3600 |
cd0fd8a9 | 795 | for 1 hour) |
4f8d0a65 | 796 | |
41bd17a4 | 797 | negative_ttl=n |
cd0fd8a9 AJ |
798 | TTL for cached negative lookups (default same |
799 | as ttl) | |
4f8d0a65 AJ |
800 | |
801 | grace=n Percentage remaining of TTL where a refresh of a | |
802 | cached entry should be initiated without needing to | |
803 | wait for a new reply. (default is for no grace period) | |
804 | ||
eef8bf2d AR |
805 | cache=n The maximum number of entries in the result cache. The |
806 | default limit is 262144 entries. Each cache entry usually | |
807 | consumes at least 256 bytes. Squid currently does not remove | |
808 | expired cache entries until the limit is reached, so a proxy | |
809 | will sooner or later reach the limit. The expanded FORMAT | |
810 | value is used as the cache key, so if the details in FORMAT | |
811 | are highly variable, a larger cache may be needed to produce | |
812 | reduction in helper load. | |
4f8d0a65 | 813 | |
48d54e4d AJ |
814 | children-max=n |
815 | Maximum number of acl helper processes spawned to service | |
2ccfb9a7 | 816 | external acl lookups of this type. (default 5) |
4f8d0a65 | 817 | |
48d54e4d AJ |
818 | children-startup=n |
819 | Minimum number of acl helper processes to spawn during | |
820 | startup and reconfigure to service external acl lookups | |
821 | of this type. (default 0) | |
4f8d0a65 | 822 | |
48d54e4d AJ |
823 | children-idle=n |
824 | Number of acl helper processes to keep ahead of traffic | |
825 | loads. Squid will spawn this many at once whenever load | |
826 | rises above the capabilities of existing processes. | |
827 | Up to the value of children-max. (default 1) | |
4f8d0a65 | 828 | |
41bd17a4 | 829 | concurrency=n concurrency level per process. Only used with helpers |
830 | capable of processing more than one query at a time. | |
4f8d0a65 | 831 | |
6825b101 CT |
832 | queue-size=N The queue-size= option sets the maximum number of queued |
833 | requests. If the queued requests exceed queue size | |
4f8d0a65 | 834 | the acl is ignored. |
6825b101 | 835 | The default value is set to 2*children-max. |
4f8d0a65 AJ |
836 | |
837 | protocol=2.5 Compatibility mode for Squid-2.5 external acl helpers. | |
838 | ||
91e64de9 AJ |
839 | ipv4 / ipv6 IP protocol used to communicate with this helper. |
840 | The default is to auto-detect IPv6 and use it when available. | |
cccac0a2 | 841 | |
4f8d0a65 | 842 | |
cd0fd8a9 AJ |
843 | FORMAT is a series of %macro codes. See logformat directive for a full list |
844 | of the accepted codes. Although note that at the time of any external ACL | |
845 | being tested data may not be available and thus some %macro expand to '-'. | |
846 | ||
847 | In addition to the logformat codes; when processing external ACLs these | |
848 | additional macros are made available: | |
7b0ca1e8 | 849 | |
ec2d5242 | 850 | %ACL The name of the ACL being tested. |
ec2d5242 | 851 | |
0638f4a2 AJ |
852 | %DATA The ACL arguments specified in the referencing config |
853 | 'acl ... external' line, separated by spaces (an | |
854 | "argument string"). see acl external. | |
855 | ||
856 | If there are no ACL arguments %DATA expands to '-'. | |
857 | ||
858 | If you do not specify a DATA macro inside FORMAT, | |
859 | Squid automatically appends %DATA to your FORMAT. | |
cd0fd8a9 | 860 | |
262eaf9a CT |
861 | By default, Squid applies URL-encoding to each ACL |
862 | argument inside the argument string. If an explicit | |
863 | encoding modifier is used (e.g., %#DATA), then Squid | |
864 | encodes the whole argument string as a single token | |
865 | (e.g., with %#DATA, spaces between arguments become | |
866 | %20). | |
867 | ||
cd0fd8a9 AJ |
868 | If SSL is enabled, the following formating codes become available: |
869 | ||
870 | %USER_CERT SSL User certificate in PEM format | |
871 | %USER_CERTCHAIN SSL User certificate chain in PEM format | |
872 | %USER_CERT_xx SSL User certificate subject attribute xx | |
873 | %USER_CA_CERT_xx SSL User certificate issuer attribute xx | |
874 | ||
875 | ||
876 | NOTE: all other format codes accepted by older Squid versions | |
877 | are deprecated. | |
0db8942f | 878 | |
cccac0a2 | 879 | |
5269ec0e AJ |
880 | General request syntax: |
881 | ||
0638f4a2 | 882 | [channel-ID] FORMAT-values |
5269ec0e AJ |
883 | |
884 | ||
885 | FORMAT-values consists of transaction details expanded with | |
886 | whitespace separation per the config file FORMAT specification | |
887 | using the FORMAT macros listed above. | |
888 | ||
5269ec0e AJ |
889 | Request values sent to the helper are URL escaped to protect |
890 | each value in requests against whitespaces. | |
891 | ||
892 | If using protocol=2.5 then the request sent to the helper is not | |
893 | URL escaped to protect against whitespace. | |
894 | ||
895 | NOTE: protocol=3.0 is deprecated as no longer necessary. | |
896 | ||
897 | When using the concurrency= option the protocol is changed by | |
898 | introducing a query channel tag in front of the request/response. | |
899 | The query channel tag is a number between 0 and concurrency-1. | |
900 | This value must be echoed back unchanged to Squid as the first part | |
901 | of the response relating to its request. | |
902 | ||
903 | ||
904 | The helper receives lines expanded per the above format specification | |
905 | and for each input line returns 1 line starting with OK/ERR/BH result | |
906 | code and optionally followed by additional keywords with more details. | |
907 | ||
cccac0a2 | 908 | |
41bd17a4 | 909 | General result syntax: |
cccac0a2 | 910 | |
5269ec0e AJ |
911 | [channel-ID] result keyword=value ... |
912 | ||
913 | Result consists of one of the codes: | |
914 | ||
915 | OK | |
916 | the ACL test produced a match. | |
917 | ||
918 | ERR | |
919 | the ACL test does not produce a match. | |
920 | ||
921 | BH | |
4ded749e | 922 | An internal error occurred in the helper, preventing |
5269ec0e AJ |
923 | a result being identified. |
924 | ||
925 | The meaning of 'a match' is determined by your squid.conf | |
926 | access control configuration. See the Squid wiki for details. | |
cccac0a2 | 927 | |
41bd17a4 | 928 | Defined keywords: |
cccac0a2 | 929 | |
41bd17a4 | 930 | user= The users name (login) |
5269ec0e | 931 | |
41bd17a4 | 932 | password= The users password (for login= cache_peer option) |
5269ec0e | 933 | |
05e52854 | 934 | message= Message describing the reason for this response. |
5269ec0e AJ |
935 | Available as %o in error pages. |
936 | Useful on (ERR and BH results). | |
937 | ||
05e52854 AJ |
938 | tag= Apply a tag to a request. Only sets a tag once, |
939 | does not alter existing tags. | |
5269ec0e | 940 | |
41bd17a4 | 941 | log= String to be logged in access.log. Available as |
cd0fd8a9 | 942 | %ea in logformat specifications. |
934b03fc | 943 | |
cd0fd8a9 | 944 | clt_conn_tag= Associates a TAG with the client TCP connection. |
4f8d0a65 AJ |
945 | Please see url_rewrite_program related documentation |
946 | for this kv-pair. | |
457857fe | 947 | |
05e52854 | 948 | Any keywords may be sent on any response whether OK, ERR or BH. |
6a566b9c | 949 | |
05e52854 AJ |
950 | All response keyword values need to be a single token with URL |
951 | escaping, or enclosed in double quotes (") and escaped using \ on | |
24eac830 AJ |
952 | any double quotes or \ characters within the value. The wrapping |
953 | double quotes are removed before the value is interpreted by Squid. | |
954 | \r and \n are also replace by CR and LF. | |
1e5562e3 | 955 | |
24eac830 AJ |
956 | Some example key values: |
957 | ||
5269ec0e | 958 | user=John%20Smith |
24eac830 AJ |
959 | user="John Smith" |
960 | user="J. \"Bob\" Smith" | |
cccac0a2 | 961 | DOC_END |
962 | ||
41bd17a4 | 963 | NAME: acl |
964 | TYPE: acl | |
965 | LOC: Config.aclList | |
cb4f4424 | 966 | IF USE_OPENSSL |
cf1c09f6 CT |
967 | DEFAULT: ssl::certHasExpired ssl_error X509_V_ERR_CERT_HAS_EXPIRED |
968 | DEFAULT: ssl::certNotYetValid ssl_error X509_V_ERR_CERT_NOT_YET_VALID | |
969 | DEFAULT: ssl::certDomainMismatch ssl_error SQUID_X509_V_ERR_DOMAIN_MISMATCH | |
970 | DEFAULT: ssl::certUntrusted ssl_error X509_V_ERR_INVALID_CA X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY X509_V_ERR_CERT_UNTRUSTED | |
971 | DEFAULT: ssl::certSelfSigned ssl_error X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT | |
972 | ENDIF | |
1f5bd0a4 | 973 | DEFAULT: all src all |
b8a25eaa AJ |
974 | DEFAULT: manager url_regex -i ^cache_object:// +i ^https?://[^/]+/squid-internal-mgr/ |
975 | DEFAULT: localhost src 127.0.0.1/32 ::1 | |
976 | DEFAULT: to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1 | |
2c56ee3c | 977 | DEFAULT: CONNECT method CONNECT |
29503899 | 978 | DEFAULT_DOC: ACLs all, manager, localhost, to_localhost, and CONNECT are predefined. |
cccac0a2 | 979 | DOC_START |
41bd17a4 | 980 | Defining an Access List |
cccac0a2 | 981 | |
375eeb3b AJ |
982 | Every access list definition must begin with an aclname and acltype, |
983 | followed by either type-specific arguments or a quoted filename that | |
984 | they are read from. | |
cccac0a2 | 985 | |
375eeb3b AJ |
986 | acl aclname acltype argument ... |
987 | acl aclname acltype "file" ... | |
cccac0a2 | 988 | |
375eeb3b | 989 | When using "file", the file should contain one item per line. |
cccac0a2 | 990 | |
76ee67ac CT |
991 | |
992 | ACL Options | |
993 | ||
994 | Some acl types supports options which changes their default behaviour: | |
0f987978 CT |
995 | |
996 | -i,+i By default, regular expressions are CASE-SENSITIVE. To make them | |
997 | case-insensitive, use the -i option. To return case-sensitive | |
998 | use the +i option between patterns, or make a new ACL line | |
999 | without -i. | |
1000 | ||
1001 | -n Disable lookups and address type conversions. If lookup or | |
1002 | conversion is required because the parameter type (IP or | |
1003 | domain name) does not match the message address type (domain | |
1004 | name or IP), then the ACL would immediately declare a mismatch | |
1005 | without any warnings or lookups. | |
1006 | ||
76ee67ac CT |
1007 | -m[=delimiters] |
1008 | Perform a list membership test, interpreting values as | |
1009 | comma-separated token lists and matching against individual | |
1010 | tokens instead of whole values. | |
1011 | The optional "delimiters" parameter specifies one or more | |
1012 | alternative non-alphanumeric delimiter characters. | |
1013 | non-alphanumeric delimiter characters. | |
1014 | ||
0f987978 CT |
1015 | -- Used to stop processing all options, in the case the first acl |
1016 | value has '-' character as first character (for example the '-' | |
1017 | is a valid domain name) | |
cccac0a2 | 1018 | |
b3567eb5 FC |
1019 | Some acl types require suspending the current request in order |
1020 | to access some external data source. | |
1021 | Those which do are marked with the tag [slow], those which | |
1022 | don't are marked as [fast]. | |
1023 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl | |
1024 | for further information | |
e988aa40 AJ |
1025 | |
1026 | ***** ACL TYPES AVAILABLE ***** | |
1027 | ||
1e40905d AJ |
1028 | acl aclname src ip-address/mask ... # clients IP address [fast] |
1029 | acl aclname src addr1-addr2/mask ... # range of addresses [fast] | |
0f987978 | 1030 | acl aclname dst [-n] ip-address/mask ... # URL host's IP address [slow] |
1e40905d | 1031 | acl aclname localip ip-address/mask ... # IP address the client connected to [fast] |
cccac0a2 | 1032 | |
41bd17a4 | 1033 | acl aclname arp mac-address ... (xx:xx:xx:xx:xx:xx notation) |
b3567eb5 | 1034 | # [fast] |
abe01913 AJ |
1035 | # The 'arp' ACL code is not portable to all operating systems. |
1036 | # It works on Linux, Solaris, Windows, FreeBSD, and some other | |
1037 | # BSD variants. | |
41bd17a4 | 1038 | # |
abe01913 AJ |
1039 | # NOTE: Squid can only determine the MAC/EUI address for IPv4 |
1040 | # clients that are on the same subnet. If the client is on a | |
1041 | # different subnet, then Squid cannot find out its address. | |
1042 | # | |
1043 | # NOTE 2: IPv6 protocol does not contain ARP. MAC/EUI is either | |
1044 | # encoded directly in the IPv6 address or not available. | |
b3567eb5 FC |
1045 | |
1046 | acl aclname srcdomain .foo.com ... | |
1047 | # reverse lookup, from client IP [slow] | |
0f987978 | 1048 | acl aclname dstdomain [-n] .foo.com ... |
e38c7724 | 1049 | # Destination server from URL [fast] |
b3567eb5 FC |
1050 | acl aclname srcdom_regex [-i] \.foo\.com ... |
1051 | # regex matching client name [slow] | |
0f987978 | 1052 | acl aclname dstdom_regex [-n] [-i] \.foo\.com ... |
e38c7724 | 1053 | # regex matching server [fast] |
b3567eb5 | 1054 | # |
41bd17a4 | 1055 | # For dstdomain and dstdom_regex a reverse lookup is tried if a IP |
1056 | # based URL is used and no match is found. The name "none" is used | |
1057 | # if the reverse lookup fails. | |
9bc73deb | 1058 | |
375eeb3b AJ |
1059 | acl aclname src_as number ... |
1060 | acl aclname dst_as number ... | |
b3567eb5 | 1061 | # [fast] |
e988aa40 AJ |
1062 | # Except for access control, AS numbers can be used for |
1063 | # routing of requests to specific caches. Here's an | |
1064 | # example for routing all requests for AS#1241 and only | |
1065 | # those to mycache.mydomain.net: | |
1066 | # acl asexample dst_as 1241 | |
1067 | # cache_peer_access mycache.mydomain.net allow asexample | |
1068 | # cache_peer_access mycache_mydomain.net deny all | |
7f7db318 | 1069 | |
6db78a1a | 1070 | acl aclname peername myPeer ... |
b3567eb5 | 1071 | # [fast] |
6db78a1a AJ |
1072 | # match against a named cache_peer entry |
1073 | # set unique name= on cache_peer lines for reliable use. | |
1074 | ||
375eeb3b | 1075 | acl aclname time [day-abbrevs] [h1:m1-h2:m2] |
b3567eb5 | 1076 | # [fast] |
375eeb3b AJ |
1077 | # day-abbrevs: |
1078 | # S - Sunday | |
1079 | # M - Monday | |
1080 | # T - Tuesday | |
1081 | # W - Wednesday | |
1082 | # H - Thursday | |
1083 | # F - Friday | |
1084 | # A - Saturday | |
1085 | # h1:m1 must be less than h2:m2 | |
1086 | ||
b3567eb5 FC |
1087 | acl aclname url_regex [-i] ^http:// ... |
1088 | # regex matching on whole URL [fast] | |
9d35fe37 AJ |
1089 | acl aclname urllogin [-i] [^a-zA-Z0-9] ... |
1090 | # regex matching on URL login field | |
b3567eb5 FC |
1091 | acl aclname urlpath_regex [-i] \.gif$ ... |
1092 | # regex matching on URL path [fast] | |
e988aa40 | 1093 | |
b3567eb5 FC |
1094 | acl aclname port 80 70 21 0-1024... # destination TCP port [fast] |
1095 | # ranges are alloed | |
1e40905d AJ |
1096 | acl aclname localport 3128 ... # TCP port the client connected to [fast] |
1097 | # NP: for interception mode this is usually '80' | |
1098 | ||
3cc0f4e7 | 1099 | acl aclname myportname 3128 ... # *_port name [fast] |
e988aa40 | 1100 | |
b3567eb5 FC |
1101 | acl aclname proto HTTP FTP ... # request protocol [fast] |
1102 | ||
1103 | acl aclname method GET POST ... # HTTP request method [fast] | |
e988aa40 | 1104 | |
b3567eb5 FC |
1105 | acl aclname http_status 200 301 500- 400-403 ... |
1106 | # status code in reply [fast] | |
e988aa40 | 1107 | |
375eeb3b | 1108 | acl aclname browser [-i] regexp ... |
b3567eb5 | 1109 | # pattern match on User-Agent header (see also req_header below) [fast] |
e988aa40 | 1110 | |
375eeb3b | 1111 | acl aclname referer_regex [-i] regexp ... |
b3567eb5 | 1112 | # pattern match on Referer header [fast] |
41bd17a4 | 1113 | # Referer is highly unreliable, so use with care |
e988aa40 | 1114 | |
375eeb3b | 1115 | acl aclname ident username ... |
41bd17a4 | 1116 | acl aclname ident_regex [-i] pattern ... |
b3567eb5 | 1117 | # string match on ident output [slow] |
41bd17a4 | 1118 | # use REQUIRED to accept any non-null ident. |
cf5cc17e | 1119 | |
41bd17a4 | 1120 | acl aclname proxy_auth [-i] username ... |
1121 | acl aclname proxy_auth_regex [-i] pattern ... | |
b3567eb5 FC |
1122 | # perform http authentication challenge to the client and match against |
1123 | # supplied credentials [slow] | |
1124 | # | |
1125 | # takes a list of allowed usernames. | |
41bd17a4 | 1126 | # use REQUIRED to accept any valid username. |
1127 | # | |
b3567eb5 FC |
1128 | # Will use proxy authentication in forward-proxy scenarios, and plain |
1129 | # http authenticaiton in reverse-proxy scenarios | |
1130 | # | |
41bd17a4 | 1131 | # NOTE: when a Proxy-Authentication header is sent but it is not |
1132 | # needed during ACL checking the username is NOT logged | |
1133 | # in access.log. | |
1134 | # | |
1135 | # NOTE: proxy_auth requires a EXTERNAL authentication program | |
1136 | # to check username/password combinations (see | |
1137 | # auth_param directive). | |
1138 | # | |
e988aa40 AJ |
1139 | # NOTE: proxy_auth can't be used in a transparent/intercepting proxy |
1140 | # as the browser needs to be configured for using a proxy in order | |
41bd17a4 | 1141 | # to respond to proxy authentication. |
8e8d4f30 | 1142 | |
41bd17a4 | 1143 | acl aclname snmp_community string ... |
b3567eb5 | 1144 | # A community string to limit access to your SNMP Agent [fast] |
41bd17a4 | 1145 | # Example: |
1146 | # | |
1147 | # acl snmppublic snmp_community public | |
934b03fc | 1148 | |
41bd17a4 | 1149 | acl aclname maxconn number |
1150 | # This will be matched when the client's IP address has | |
55d0fae8 AJ |
1151 | # more than <number> TCP connections established. [fast] |
1152 | # NOTE: This only measures direct TCP links so X-Forwarded-For | |
1153 | # indirect clients are not counted. | |
1e5562e3 | 1154 | |
41bd17a4 | 1155 | acl aclname max_user_ip [-s] number |
1156 | # This will be matched when the user attempts to log in from more | |
1157 | # than <number> different ip addresses. The authenticate_ip_ttl | |
b3567eb5 | 1158 | # parameter controls the timeout on the ip entries. [fast] |
41bd17a4 | 1159 | # If -s is specified the limit is strict, denying browsing |
1160 | # from any further IP addresses until the ttl has expired. Without | |
1161 | # -s Squid will just annoy the user by "randomly" denying requests. | |
1162 | # (the counter is reset each time the limit is reached and a | |
1163 | # request is denied) | |
1164 | # NOTE: in acceleration mode or where there is mesh of child proxies, | |
1165 | # clients may appear to come from multiple addresses if they are | |
1166 | # going through proxy farms, so a limit of 1 may cause user problems. | |
cccac0a2 | 1167 | |
cb1b906f AJ |
1168 | acl aclname random probability |
1169 | # Pseudo-randomly match requests. Based on the probability given. | |
1170 | # Probability may be written as a decimal (0.333), fraction (1/3) | |
1171 | # or ratio of matches:non-matches (3:5). | |
1172 | ||
375eeb3b | 1173 | acl aclname req_mime_type [-i] mime-type ... |
41bd17a4 | 1174 | # regex match against the mime type of the request generated |
1175 | # by the client. Can be used to detect file upload or some | |
b3567eb5 | 1176 | # types HTTP tunneling requests [fast] |
41bd17a4 | 1177 | # NOTE: This does NOT match the reply. You cannot use this |
1178 | # to match the returned file type. | |
cccac0a2 | 1179 | |
41bd17a4 | 1180 | acl aclname req_header header-name [-i] any\.regex\.here |
1181 | # regex match against any of the known request headers. May be | |
1182 | # thought of as a superset of "browser", "referer" and "mime-type" | |
b3567eb5 | 1183 | # ACL [fast] |
cccac0a2 | 1184 | |
375eeb3b | 1185 | acl aclname rep_mime_type [-i] mime-type ... |
41bd17a4 | 1186 | # regex match against the mime type of the reply received by |
1187 | # squid. Can be used to detect file download or some | |
b3567eb5 | 1188 | # types HTTP tunneling requests. [fast] |
41bd17a4 | 1189 | # NOTE: This has no effect in http_access rules. It only has |
1190 | # effect in rules that affect the reply data stream such as | |
1191 | # http_reply_access. | |
cccac0a2 | 1192 | |
41bd17a4 | 1193 | acl aclname rep_header header-name [-i] any\.regex\.here |
1194 | # regex match against any of the known reply headers. May be | |
1195 | # thought of as a superset of "browser", "referer" and "mime-type" | |
b3567eb5 | 1196 | # ACLs [fast] |
cccac0a2 | 1197 | |
375eeb3b | 1198 | acl aclname external class_name [arguments...] |
41bd17a4 | 1199 | # external ACL lookup via a helper class defined by the |
b3567eb5 | 1200 | # external_acl_type directive [slow] |
cccac0a2 | 1201 | |
41bd17a4 | 1202 | acl aclname user_cert attribute values... |
1203 | # match against attributes in a user SSL certificate | |
2927ae41 | 1204 | # attribute is one of DN/C/O/CN/L/ST or a numerical OID [fast] |
cccac0a2 | 1205 | |
41bd17a4 | 1206 | acl aclname ca_cert attribute values... |
1207 | # match against attributes a users issuing CA SSL certificate | |
2927ae41 | 1208 | # attribute is one of DN/C/O/CN/L/ST or a numerical OID [fast] |
cccac0a2 | 1209 | |
41bd17a4 | 1210 | acl aclname ext_user username ... |
1211 | acl aclname ext_user_regex [-i] pattern ... | |
b3567eb5 | 1212 | # string match on username returned by external acl helper [slow] |
41bd17a4 | 1213 | # use REQUIRED to accept any non-null user name. |
b3567eb5 | 1214 | |
0ab50441 | 1215 | acl aclname tag tagvalue ... |
94da12c8 AJ |
1216 | # string match on tag returned by external acl helper [fast] |
1217 | # DEPRECATED. Only the first tag will match with this ACL. | |
1218 | # Use the 'note' ACL instead for handling multiple tag values. | |
cccac0a2 | 1219 | |
bbaf2685 AJ |
1220 | acl aclname hier_code codename ... |
1221 | # string match against squid hierarchy code(s); [fast] | |
1222 | # e.g., DIRECT, PARENT_HIT, NONE, etc. | |
1223 | # | |
1224 | # NOTE: This has no effect in http_access rules. It only has | |
1225 | # effect in rules that affect the reply data stream such as | |
1226 | # http_reply_access. | |
1227 | ||
76ee67ac | 1228 | acl aclname note [-m[=delimiters]] name [value ...] |
39baccc8 CT |
1229 | # match transaction annotation [fast] |
1230 | # Without values, matches any annotation with a given name. | |
1231 | # With value(s), matches any annotation with a given name that | |
1232 | # also has one of the given values. | |
76ee67ac CT |
1233 | # If the -m flag is used, then the value of the named |
1234 | # annotation is interpreted as a list of tokens, and the ACL | |
1235 | # matches individual name=token pairs rather than whole | |
1236 | # name=value pairs. See "ACL Options" above for more info. | |
39baccc8 CT |
1237 | # Annotation sources include note and adaptation_meta directives |
1238 | # as well as helper and eCAP responses. | |
1239 | ||
589aab05 CT |
1240 | acl aclname annotate_transaction [-m[=delimiters]] key=value ... |
1241 | acl aclname annotate_transaction [-m[=delimiters]] key+=value ... | |
75d47340 CT |
1242 | # Always matches. [fast] |
1243 | # Used for its side effect: This ACL immediately adds a | |
1244 | # key=value annotation to the current master transaction. | |
1245 | # The added annotation can then be tested using note ACL and | |
1246 | # logged (or sent to helpers) using %note format code. | |
1247 | # | |
1248 | # Annotations can be specified using replacement and addition | |
1249 | # formats. The key=value form replaces old same-key annotation | |
1250 | # value(s). The key+=value form appends a new value to the old | |
1251 | # same-key annotation. Both forms create a new key=value | |
1252 | # annotation if no same-key annotation exists already. If | |
1253 | # -m flag is used, then the value is interpreted as a list | |
1254 | # and the annotation will contain key=token pair(s) instead of the | |
1255 | # whole key=value pair. | |
1256 | # | |
1257 | # This ACL is especially useful for recording complex multi-step | |
1258 | # ACL-driven decisions. For example, the following configuration | |
1259 | # avoids logging transactions accepted after aclX matched: | |
1260 | # | |
1261 | # # First, mark transactions accepted after aclX matched | |
1262 | # acl markSpecial annotate_transaction special=true | |
1263 | # http_access allow acl001 | |
1264 | # ... | |
1265 | # http_access deny acl100 | |
1266 | # http_access allow aclX markSpecial | |
1267 | # | |
1268 | # # Second, do not log marked transactions: | |
1269 | # acl markedSpecial note special true | |
1270 | # access_log ... deny markedSpecial | |
1271 | # | |
1272 | # # Note that the following would not have worked because aclX | |
1273 | # # alone does not determine whether the transaction was allowed: | |
1274 | # access_log ... deny aclX # Wrong! | |
1275 | # | |
1276 | # Warning: This ACL annotates the transaction even when negated | |
1277 | # and even if subsequent ACLs fail to match. For example, the | |
1278 | # following three rules will have exactly the same effect as far | |
1279 | # as annotations set by the "mark" ACL are concerned: | |
1280 | # | |
1281 | # some_directive acl1 ... mark # rule matches if mark is reached | |
1282 | # some_directive acl1 ... !mark # rule never matches | |
1283 | # some_directive acl1 ... mark !all # rule never matches | |
1284 | ||
589aab05 CT |
1285 | acl aclname annotate_client [-m[=delimiters]] key=value ... |
1286 | acl aclname annotate_client [-m[=delimiters]] key+=value ... | |
75d47340 | 1287 | # |
589aab05 CT |
1288 | # Always matches. [fast] |
1289 | # Used for its side effect: This ACL immediately adds a | |
1290 | # key=value annotation to the current client-to-Squid | |
75d47340 CT |
1291 | # connection. Connection annotations are propagated to the current |
1292 | # and all future master transactions on the annotated connection. | |
1293 | # See the annotate_transaction ACL for details. | |
1294 | # | |
1295 | # For example, the following configuration avoids rewriting URLs | |
1296 | # of transactions bumped by SslBump: | |
1297 | # | |
1298 | # # First, mark bumped connections: | |
1299 | # acl markBumped annotate_client bumped=true | |
1300 | # ssl_bump peek acl1 | |
1301 | # ssl_bump stare acl2 | |
1302 | # ssl_bump bump acl3 markBumped | |
1303 | # ssl_bump splice all | |
1304 | # | |
1305 | # # Second, do not send marked transactions to the redirector: | |
1306 | # acl markedBumped note bumped true | |
1307 | # url_rewrite_access deny markedBumped | |
1308 | # | |
1309 | # # Note that the following would not have worked because acl3 alone | |
1310 | # # does not determine whether the connection is going to be bumped: | |
1311 | # url_rewrite_access deny acl3 # Wrong! | |
1312 | ||
c302ddb5 CT |
1313 | acl aclname adaptation_service service ... |
1314 | # Matches the name of any icap_service, ecap_service, | |
1315 | # adaptation_service_set, or adaptation_service_chain that Squid | |
1316 | # has used (or attempted to use) for the master transaction. | |
1317 | # This ACL must be defined after the corresponding adaptation | |
1318 | # service is named in squid.conf. This ACL is usable with | |
1319 | # adaptation_meta because it starts matching immediately after | |
1320 | # the service has been selected for adaptation. | |
1321 | ||
5ceaee75 CT |
1322 | acl aclname transaction_initiator initiator ... |
1323 | # Matches transaction's initiator [fast] | |
1324 | # | |
1325 | # Supported initiators are: | |
1326 | # esi: matches transactions fetching ESI resources | |
1327 | # certificate-fetching: matches transactions fetching | |
1328 | # a missing intermediate TLS certificate | |
1329 | # cache-digest: matches transactions fetching Cache Digests | |
1330 | # from a cache_peer | |
1331 | # htcp: matches HTCP requests from peers | |
1332 | # icp: matches ICP requests to peers | |
1333 | # icmp: matches ICMP RTT database (NetDB) requests to peers | |
1334 | # asn: matches asns db requests | |
1335 | # internal: matches any of the above | |
1336 | # client: matches transactions containing an HTTP or FTP | |
1337 | # client request received at a Squid *_port | |
1338 | # all: matches any transaction, including internal transactions | |
1339 | # without a configurable initiator and hopefully rare | |
1340 | # transactions without a known-to-Squid initiator | |
1341 | # | |
1342 | # Multiple initiators are ORed. | |
1343 | ||
5ec4cffe EB |
1344 | acl aclname has component |
1345 | # matches a transaction "component" [fast] | |
1346 | # | |
1347 | # Supported transaction components are: | |
1348 | # request: transaction has a request header (at least) | |
1349 | # response: transaction has a response header (at least) | |
1350 | # ALE: transaction has an internally-generated Access Log Entry | |
1351 | # structure; bugs notwithstanding, all transaction have it | |
1352 | # | |
1353 | # For example, the following configuration helps when dealing with HTTP | |
1354 | # clients that close connections without sending a request header: | |
1355 | # | |
1356 | # acl hasRequest has request | |
1357 | # acl logMe note important_transaction | |
1358 | # # avoid "logMe ACL is used in context without an HTTP request" warnings | |
1359 | # access_log ... logformat=detailed hasRequest logMe | |
1360 | # # log request-less transactions, instead of ignoring them | |
1361 | # access_log ... logformat=brief !hasRequest | |
1362 | # | |
1363 | # Multiple components are not supported for one "acl" rule, but | |
1364 | # can be specified (and are ORed) using multiple same-name rules: | |
1365 | # | |
1366 | # # OK, this strange logging daemon needs request or response, | |
1367 | # # but can work without either a request or a response: | |
1368 | # acl hasWhatMyLoggingDaemonNeeds has request | |
1369 | # acl hasWhatMyLoggingDaemonNeeds has response | |
1370 | ||
cb4f4424 | 1371 | IF USE_OPENSSL |
cf1c09f6 CT |
1372 | acl aclname ssl_error errorname |
1373 | # match against SSL certificate validation error [fast] | |
cf1c09f6 | 1374 | # |
7a957a93 AR |
1375 | # For valid error names see in @DEFAULT_ERROR_DIR@/templates/error-details.txt |
1376 | # template file. | |
cf1c09f6 | 1377 | # |
7a957a93 AR |
1378 | # The following can be used as shortcuts for certificate properties: |
1379 | # [ssl::]certHasExpired: the "not after" field is in the past | |
1380 | # [ssl::]certNotYetValid: the "not before" field is in the future | |
1381 | # [ssl::]certUntrusted: The certificate issuer is not to be trusted. | |
1382 | # [ssl::]certSelfSigned: The certificate is self signed. | |
1383 | # [ssl::]certDomainMismatch: The certificate CN domain does not | |
1384 | # match the name the name of the host we are connecting to. | |
1385 | # | |
1386 | # The ssl::certHasExpired, ssl::certNotYetValid, ssl::certDomainMismatch, | |
1387 | # ssl::certUntrusted, and ssl::certSelfSigned can also be used as | |
1388 | # predefined ACLs, just like the 'all' ACL. | |
1389 | # | |
1390 | # NOTE: The ssl_error ACL is only supported with sslproxy_cert_error, | |
1391 | # sslproxy_cert_sign, and sslproxy_cert_adapt options. | |
00352183 | 1392 | |
72b12f9e | 1393 | acl aclname server_cert_fingerprint [-sha1] fingerprint |
00352183 AR |
1394 | # match against server SSL certificate fingerprint [fast] |
1395 | # | |
1396 | # The fingerprint is the digest of the DER encoded version | |
1397 | # of the whole certificate. The user should use the form: XX:XX:... | |
1398 | # Optional argument specifies the digest algorithm to use. | |
1399 | # The SHA1 digest algorithm is the default and is currently | |
1400 | # the only algorithm supported (-sha1). | |
5d65362c | 1401 | |
652fcffd | 1402 | acl aclname at_step step |
8f165829 AR |
1403 | # match against the current step during ssl_bump evaluation [fast] |
1404 | # Never matches and should not be used outside the ssl_bump context. | |
1405 | # | |
1406 | # At each SslBump step, Squid evaluates ssl_bump directives to find | |
1407 | # the next bumping action (e.g., peek or splice). Valid SslBump step | |
1408 | # values and the corresponding ssl_bump evaluation moments are: | |
1110989a CT |
1409 | # SslBump1: After getting TCP-level and HTTP CONNECT info. |
1410 | # SslBump2: After getting SSL Client Hello info. | |
1411 | # SslBump3: After getting SSL Server Hello info. | |
69f69080 | 1412 | |
4f6990ec | 1413 | acl aclname ssl::server_name [option] .foo.com ... |
69f69080 CT |
1414 | # matches server name obtained from various sources [fast] |
1415 | # | |
4f6990ec CT |
1416 | # The ACL computes server name(s) using such information sources as |
1417 | # CONNECT request URI, TLS client SNI, and TLS server certificate | |
1418 | # subject (CN and SubjectAltName). The computed server name(s) usually | |
1419 | # change with each SslBump step, as more info becomes available: | |
1420 | # * SNI is used as the server name instead of the request URI, | |
1421 | # * subject name(s) from the server certificate (CN and | |
1422 | # SubjectAltName) are used as the server names instead of SNI. | |
1423 | # | |
1424 | # When the ACL computes multiple server names, matching any single | |
1425 | # computed name is sufficient for the ACL to match. | |
1426 | # | |
1427 | # The "none" name can be used to match transactions where the ACL | |
8d9e6d7f | 1428 | # could not compute the server name using any information source |
4f6990ec CT |
1429 | # that was both available and allowed to be used by the ACL options at |
1430 | # the ACL evaluation time. | |
1431 | # | |
1432 | # Unlike dstdomain, this ACL does not perform DNS lookups. | |
1433 | # | |
1434 | # An ACL option below may be used to restrict what information | |
1435 | # sources are used to extract the server names from: | |
1436 | # | |
1437 | # --client-requested | |
1438 | # The server name is SNI regardless of what the server says. | |
1439 | # --server-provided | |
1440 | # The server name(s) are the certificate subject name(s), regardless | |
1441 | # of what the client has requested. If the server certificate is | |
1442 | # unavailable, then the name is "none". | |
1443 | # --consensus | |
1444 | # The server name is either SNI (if SNI matches at least one of the | |
1445 | # certificate subject names) or "none" (otherwise). When the server | |
1446 | # certificate is unavailable, the consensus server name is SNI. | |
1447 | # | |
1448 | # Combining multiple options in one ACL is a fatal configuration | |
1449 | # error. | |
1450 | # | |
1451 | # For all options: If no SNI is available, then the CONNECT request | |
1452 | # target (a.k.a. URI) is used instead of SNI (for an intercepted | |
1453 | # connection, this target is the destination IP address). | |
69f69080 CT |
1454 | |
1455 | acl aclname ssl::server_name_regex [-i] \.foo\.com ... | |
1456 | # regex matches server name obtained from various sources [fast] | |
88df846b CT |
1457 | |
1458 | acl aclname connections_encrypted | |
1459 | # matches transactions with all HTTP messages received over TLS | |
1460 | # transport connections. [fast] | |
1461 | # | |
1462 | # The master transaction deals with HTTP messages received from | |
1463 | # various sources. All sources used by the master transaction in the | |
1464 | # past are considered by the ACL. The following rules define whether | |
1465 | # a given message source taints the entire master transaction, | |
1466 | # resulting in ACL mismatches: | |
1467 | # | |
1468 | # * The HTTP client transport connection is not TLS. | |
1469 | # * An adaptation service connection-encryption flag is off. | |
1470 | # * The peer or origin server transport connection is not TLS. | |
1471 | # | |
1472 | # Caching currently does not affect these rules. This cache ignorance | |
1473 | # implies that only the current HTTP client transport and REQMOD | |
1474 | # services status determine whether this ACL matches a from-cache | |
1475 | # transaction. The source of the cached response does not have any | |
1476 | # effect on future transaction that use the cached response without | |
1477 | # revalidation. This may change. | |
1478 | # | |
1479 | # DNS, ICP, and HTCP exchanges during the master transaction do not | |
1480 | # affect these rules. | |
cf1c09f6 | 1481 | ENDIF |
6f58d7d7 AR |
1482 | acl aclname any-of acl1 acl2 ... |
1483 | # match any one of the acls [fast or slow] | |
1484 | # The first matching ACL stops further ACL evaluation. | |
1485 | # | |
1486 | # ACLs from multiple any-of lines with the same name are ORed. | |
1487 | # For example, A = (a1 or a2) or (a3 or a4) can be written as | |
1488 | # acl A any-of a1 a2 | |
1489 | # acl A any-of a3 a4 | |
1490 | # | |
1491 | # This group ACL is fast if all evaluated ACLs in the group are fast | |
1492 | # and slow otherwise. | |
1493 | ||
1494 | acl aclname all-of acl1 acl2 ... | |
1495 | # match all of the acls [fast or slow] | |
1496 | # The first mismatching ACL stops further ACL evaluation. | |
1497 | # | |
1498 | # ACLs from multiple all-of lines with the same name are ORed. | |
1499 | # For example, B = (b1 and b2) or (b3 and b4) can be written as | |
1500 | # acl B all-of b1 b2 | |
1501 | # acl B all-of b3 b4 | |
1502 | # | |
1503 | # This group ACL is fast if all evaluated ACLs in the group are fast | |
1504 | # and slow otherwise. | |
cf1c09f6 | 1505 | |
e0855596 AJ |
1506 | Examples: |
1507 | acl macaddress arp 09:00:2b:23:45:67 | |
1508 | acl myexample dst_as 1241 | |
1509 | acl password proxy_auth REQUIRED | |
1510 | acl fileupload req_mime_type -i ^multipart/form-data$ | |
1511 | acl javascript rep_mime_type -i ^application/x-javascript$ | |
cccac0a2 | 1512 | |
41bd17a4 | 1513 | NOCOMMENT_START |
e0855596 AJ |
1514 | # |
1515 | # Recommended minimum configuration: | |
1516 | # | |
e0855596 | 1517 | |
ee776778 | 1518 | # Example rule allowing access from your local networks. |
1519 | # Adapt to list your (internal) IP networks from where browsing | |
1520 | # should be allowed | |
fe204e1d AJ |
1521 | acl localnet src 0.0.0.1-0.255.255.255 # RFC 1122 "this" network (LAN) |
1522 | acl localnet src 10.0.0.0/8 # RFC 1918 local private network (LAN) | |
1523 | acl localnet src 100.64.0.0/10 # RFC 6598 shared address space (CGN) | |
1524 | acl localhet src 169.254.0.0/16 # RFC 3927 link-local (directly plugged) machines | |
1525 | acl localnet src 172.16.0.0/12 # RFC 1918 local private network (LAN) | |
1526 | acl localnet src 192.168.0.0/16 # RFC 1918 local private network (LAN) | |
1527 | acl localnet src fc00::/7 # RFC 4193 local private network range | |
1528 | acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines | |
e0855596 | 1529 | |
41bd17a4 | 1530 | acl SSL_ports port 443 |
1531 | acl Safe_ports port 80 # http | |
1532 | acl Safe_ports port 21 # ftp | |
1533 | acl Safe_ports port 443 # https | |
1534 | acl Safe_ports port 70 # gopher | |
1535 | acl Safe_ports port 210 # wais | |
1536 | acl Safe_ports port 1025-65535 # unregistered ports | |
1537 | acl Safe_ports port 280 # http-mgmt | |
1538 | acl Safe_ports port 488 # gss-http | |
1539 | acl Safe_ports port 591 # filemaker | |
1540 | acl Safe_ports port 777 # multiling http | |
41bd17a4 | 1541 | NOCOMMENT_END |
1542 | DOC_END | |
cccac0a2 | 1543 | |
d3d92daa | 1544 | NAME: proxy_protocol_access |
3d674977 | 1545 | TYPE: acl_access |
d3d92daa AJ |
1546 | LOC: Config.accessList.proxyProtocol |
1547 | DEFAULT: none | |
c390580b | 1548 | DEFAULT_DOC: all TCP connections to ports with require-proxy-header will be denied |
d3d92daa AJ |
1549 | DOC_START |
1550 | Determine which client proxies can be trusted to provide correct | |
1551 | information regarding real client IP address using PROXY protocol. | |
1552 | ||
1553 | Requests may pass through a chain of several other proxies | |
1554 | before reaching us. The original source details may by sent in: | |
1555 | * HTTP message Forwarded header, or | |
1556 | * HTTP message X-Forwarded-For header, or | |
1557 | * PROXY protocol connection header. | |
1558 | ||
1559 | This directive is solely for validating new PROXY protocol | |
1560 | connections received from a port flagged with require-proxy-header. | |
1561 | It is checked only once after TCP connection setup. | |
1562 | ||
1563 | A deny match results in TCP connection closure. | |
1564 | ||
1565 | An allow match is required for Squid to permit the corresponding | |
1566 | TCP connection, before Squid even looks for HTTP request headers. | |
1567 | If there is an allow match, Squid starts using PROXY header information | |
1568 | to determine the source address of the connection for all future ACL | |
1569 | checks, logging, etc. | |
1570 | ||
1571 | SECURITY CONSIDERATIONS: | |
1572 | ||
c390580b | 1573 | Any host from which we accept client IP details can place |
d3d92daa AJ |
1574 | incorrect information in the relevant header, and Squid |
1575 | will use the incorrect information as if it were the | |
1576 | source address of the request. This may enable remote | |
1577 | hosts to bypass any access control restrictions that are | |
1578 | based on the client's source addresses. | |
1579 | ||
1580 | This clause only supports fast acl types. | |
1581 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
1582 | DOC_END | |
1583 | ||
1584 | NAME: follow_x_forwarded_for | |
1585 | TYPE: acl_access | |
1586 | IFDEF: FOLLOW_X_FORWARDED_FOR | |
3d674977 | 1587 | LOC: Config.accessList.followXFF |
3d674977 | 1588 | DEFAULT_IF_NONE: deny all |
9353df52 | 1589 | DEFAULT_DOC: X-Forwarded-For header will be ignored. |
3d674977 | 1590 | DOC_START |
00d0ce87 AJ |
1591 | Determine which client proxies can be trusted to provide correct |
1592 | information regarding real client IP address. | |
1593 | ||
3d674977 | 1594 | Requests may pass through a chain of several other proxies |
70a16fea AJ |
1595 | before reaching us. The original source details may by sent in: |
1596 | * HTTP message Forwarded header, or | |
1597 | * HTTP message X-Forwarded-For header, or | |
1598 | * PROXY protocol connection header. | |
3d674977 | 1599 | |
d3d92daa AJ |
1600 | PROXY protocol connections are controlled by the proxy_protocol_access |
1601 | directive which is checked before this. | |
1602 | ||
3d674977 | 1603 | If a request reaches us from a source that is allowed by this |
70a16fea AJ |
1604 | directive, then we trust the information it provides regarding |
1605 | the IP of the client it received from (if any). | |
1606 | ||
1607 | For the purpose of ACLs used in this directive the src ACL type always | |
1608 | matches the address we are testing and srcdomain matches its rDNS. | |
1609 | ||
70a16fea AJ |
1610 | On each HTTP request Squid checks for X-Forwarded-For header fields. |
1611 | If found the header values are iterated in reverse order and an allow | |
1612 | match is required for Squid to continue on to the next value. | |
1613 | The verification ends when a value receives a deny match, cannot be | |
1614 | tested, or there are no more values to test. | |
1615 | NOTE: Squid does not yet follow the Forwarded HTTP header. | |
3d674977 AJ |
1616 | |
1617 | The end result of this process is an IP address that we will | |
1618 | refer to as the indirect client address. This address may | |
57d76dd4 | 1619 | be treated as the client address for access control, ICAP, delay |
3d674977 | 1620 | pools and logging, depending on the acl_uses_indirect_client, |
96d64448 AJ |
1621 | icap_uses_indirect_client, delay_pool_uses_indirect_client, |
1622 | log_uses_indirect_client and tproxy_uses_indirect_client options. | |
3d674977 | 1623 | |
b3567eb5 FC |
1624 | This clause only supports fast acl types. |
1625 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
1626 | ||
3d674977 AJ |
1627 | SECURITY CONSIDERATIONS: |
1628 | ||
c390580b | 1629 | Any host from which we accept client IP details can place |
70a16fea | 1630 | incorrect information in the relevant header, and Squid |
3d674977 AJ |
1631 | will use the incorrect information as if it were the |
1632 | source address of the request. This may enable remote | |
1633 | hosts to bypass any access control restrictions that are | |
1634 | based on the client's source addresses. | |
1635 | ||
1636 | For example: | |
1637 | ||
1638 | acl localhost src 127.0.0.1 | |
1639 | acl my_other_proxy srcdomain .proxy.example.com | |
1640 | follow_x_forwarded_for allow localhost | |
1641 | follow_x_forwarded_for allow my_other_proxy | |
1642 | DOC_END | |
1643 | ||
1644 | NAME: acl_uses_indirect_client | |
1645 | COMMENT: on|off | |
1646 | TYPE: onoff | |
1647 | IFDEF: FOLLOW_X_FORWARDED_FOR | |
1648 | DEFAULT: on | |
1649 | LOC: Config.onoff.acl_uses_indirect_client | |
1650 | DOC_START | |
1651 | Controls whether the indirect client address | |
1652 | (see follow_x_forwarded_for) is used instead of the | |
1653 | direct client address in acl matching. | |
55d0fae8 AJ |
1654 | |
1655 | NOTE: maxconn ACL considers direct TCP links and indirect | |
1656 | clients will always have zero. So no match. | |
3d674977 AJ |
1657 | DOC_END |
1658 | ||
1659 | NAME: delay_pool_uses_indirect_client | |
1660 | COMMENT: on|off | |
1661 | TYPE: onoff | |
9a0a18de | 1662 | IFDEF: FOLLOW_X_FORWARDED_FOR&&USE_DELAY_POOLS |
3d674977 AJ |
1663 | DEFAULT: on |
1664 | LOC: Config.onoff.delay_pool_uses_indirect_client | |
1665 | DOC_START | |
1666 | Controls whether the indirect client address | |
1667 | (see follow_x_forwarded_for) is used instead of the | |
1668 | direct client address in delay pools. | |
1669 | DOC_END | |
1670 | ||
1671 | NAME: log_uses_indirect_client | |
1672 | COMMENT: on|off | |
1673 | TYPE: onoff | |
1674 | IFDEF: FOLLOW_X_FORWARDED_FOR | |
1675 | DEFAULT: on | |
1676 | LOC: Config.onoff.log_uses_indirect_client | |
1677 | DOC_START | |
1678 | Controls whether the indirect client address | |
1679 | (see follow_x_forwarded_for) is used instead of the | |
1680 | direct client address in the access log. | |
1681 | DOC_END | |
1682 | ||
96d64448 AJ |
1683 | NAME: tproxy_uses_indirect_client |
1684 | COMMENT: on|off | |
1685 | TYPE: onoff | |
1686 | IFDEF: FOLLOW_X_FORWARDED_FOR&&LINUX_NETFILTER | |
4d7ab5a2 | 1687 | DEFAULT: off |
96d64448 AJ |
1688 | LOC: Config.onoff.tproxy_uses_indirect_client |
1689 | DOC_START | |
1690 | Controls whether the indirect client address | |
1691 | (see follow_x_forwarded_for) is used instead of the | |
1692 | direct client address when spoofing the outgoing client. | |
4d7ab5a2 AJ |
1693 | |
1694 | This has no effect on requests arriving in non-tproxy | |
1695 | mode ports. | |
1696 | ||
1697 | SECURITY WARNING: Usage of this option is dangerous | |
1698 | and should not be used trivially. Correct configuration | |
16ae256c | 1699 | of follow_x_forwarded_for with a limited set of trusted |
4d7ab5a2 | 1700 | sources is required to prevent abuse of your proxy. |
96d64448 AJ |
1701 | DOC_END |
1702 | ||
0d901ef4 SH |
1703 | NAME: spoof_client_ip |
1704 | TYPE: acl_access | |
1705 | LOC: Config.accessList.spoof_client_ip | |
1706 | DEFAULT: none | |
1707 | DEFAULT_DOC: Allow spoofing on all TPROXY traffic. | |
1708 | DOC_START | |
1709 | Control client IP address spoofing of TPROXY traffic based on | |
1710 | defined access lists. | |
1711 | ||
1712 | spoof_client_ip allow|deny [!]aclname ... | |
1713 | ||
1714 | If there are no "spoof_client_ip" lines present, the default | |
1715 | is to "allow" spoofing of any suitable request. | |
1716 | ||
1717 | Note that the cache_peer "no-tproxy" option overrides this ACL. | |
1718 | ||
1719 | This clause supports fast acl types. | |
1720 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
1721 | DOC_END | |
1722 | ||
41bd17a4 | 1723 | NAME: http_access |
1724 | TYPE: acl_access | |
1725 | LOC: Config.accessList.http | |
41bd17a4 | 1726 | DEFAULT_IF_NONE: deny all |
638402dd | 1727 | DEFAULT_DOC: Deny, unless rules exist in squid.conf. |
41bd17a4 | 1728 | DOC_START |
1729 | Allowing or Denying access based on defined access lists | |
cccac0a2 | 1730 | |
8a2f40dd | 1731 | To allow or deny a message received on an HTTP, HTTPS, or FTP port: |
41bd17a4 | 1732 | http_access allow|deny [!]aclname ... |
cccac0a2 | 1733 | |
41bd17a4 | 1734 | NOTE on default values: |
cccac0a2 | 1735 | |
41bd17a4 | 1736 | If there are no "access" lines present, the default is to deny |
1737 | the request. | |
cccac0a2 | 1738 | |
41bd17a4 | 1739 | If none of the "access" lines cause a match, the default is the |
1740 | opposite of the last line in the list. If the last line was | |
1741 | deny, the default is allow. Conversely, if the last line | |
1742 | is allow, the default will be deny. For these reasons, it is a | |
51ae86b2 HN |
1743 | good idea to have an "deny all" entry at the end of your access |
1744 | lists to avoid potential confusion. | |
cccac0a2 | 1745 | |
b3567eb5 FC |
1746 | This clause supports both fast and slow acl types. |
1747 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
1748 | ||
41bd17a4 | 1749 | NOCOMMENT_START |
e0855596 AJ |
1750 | |
1751 | # | |
1752 | # Recommended minimum Access Permission configuration: | |
41bd17a4 | 1753 | # |
e0855596 | 1754 | # Deny requests to certain unsafe ports |
41bd17a4 | 1755 | http_access deny !Safe_ports |
e0855596 AJ |
1756 | |
1757 | # Deny CONNECT to other than secure SSL ports | |
41bd17a4 | 1758 | http_access deny CONNECT !SSL_ports |
e0855596 | 1759 | |
baa3ea7e AJ |
1760 | # Only allow cachemgr access from localhost |
1761 | http_access allow localhost manager | |
1762 | http_access deny manager | |
1763 | ||
41bd17a4 | 1764 | # We strongly recommend the following be uncommented to protect innocent |
1765 | # web applications running on the proxy server who think the only | |
1766 | # one who can access services on "localhost" is a local user | |
1767 | #http_access deny to_localhost | |
e0855596 | 1768 | |
41bd17a4 | 1769 | # |
1770 | # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS | |
e0855596 | 1771 | # |
c8f4eac4 | 1772 | |
ee776778 | 1773 | # Example rule allowing access from your local networks. |
1774 | # Adapt localnet in the ACL section to list your (internal) IP networks | |
1775 | # from where browsing should be allowed | |
1776 | http_access allow localnet | |
afb33856 | 1777 | http_access allow localhost |
7d90757b | 1778 | |
41bd17a4 | 1779 | # And finally deny all other access to this proxy |
1780 | http_access deny all | |
1781 | NOCOMMENT_END | |
1782 | DOC_END | |
7d90757b | 1783 | |
533493da AJ |
1784 | NAME: adapted_http_access http_access2 |
1785 | TYPE: acl_access | |
1786 | LOC: Config.accessList.adapted_http | |
1787 | DEFAULT: none | |
638402dd | 1788 | DEFAULT_DOC: Allow, unless rules exist in squid.conf. |
533493da AJ |
1789 | DOC_START |
1790 | Allowing or Denying access based on defined access lists | |
1791 | ||
1792 | Essentially identical to http_access, but runs after redirectors | |
1793 | and ICAP/eCAP adaptation. Allowing access control based on their | |
1794 | output. | |
1795 | ||
1796 | If not set then only http_access is used. | |
1797 | DOC_END | |
1798 | ||
41bd17a4 | 1799 | NAME: http_reply_access |
1800 | TYPE: acl_access | |
1801 | LOC: Config.accessList.reply | |
1802 | DEFAULT: none | |
638402dd | 1803 | DEFAULT_DOC: Allow, unless rules exist in squid.conf. |
41bd17a4 | 1804 | DOC_START |
1805 | Allow replies to client requests. This is complementary to http_access. | |
cccac0a2 | 1806 | |
41bd17a4 | 1807 | http_reply_access allow|deny [!] aclname ... |
cccac0a2 | 1808 | |
41bd17a4 | 1809 | NOTE: if there are no access lines present, the default is to allow |
638402dd | 1810 | all replies. |
1a224843 | 1811 | |
41bd17a4 | 1812 | If none of the access lines cause a match the opposite of the |
1813 | last line will apply. Thus it is good practice to end the rules | |
1814 | with an "allow all" or "deny all" entry. | |
b3567eb5 FC |
1815 | |
1816 | This clause supports both fast and slow acl types. | |
1817 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
cccac0a2 | 1818 | DOC_END |
1819 | ||
41bd17a4 | 1820 | NAME: icp_access |
1821 | TYPE: acl_access | |
1822 | LOC: Config.accessList.icp | |
638402dd AJ |
1823 | DEFAULT: none |
1824 | DEFAULT_DOC: Deny, unless rules exist in squid.conf. | |
5473c134 | 1825 | DOC_START |
41bd17a4 | 1826 | Allowing or Denying access to the ICP port based on defined |
1827 | access lists | |
5473c134 | 1828 | |
41bd17a4 | 1829 | icp_access allow|deny [!]aclname ... |
5473c134 | 1830 | |
638402dd AJ |
1831 | NOTE: The default if no icp_access lines are present is to |
1832 | deny all traffic. This default may cause problems with peers | |
1833 | using ICP. | |
41bd17a4 | 1834 | |
b3567eb5 FC |
1835 | This clause only supports fast acl types. |
1836 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
e0855596 AJ |
1837 | |
1838 | # Allow ICP queries from local networks only | |
df2eec10 AJ |
1839 | #icp_access allow localnet |
1840 | #icp_access deny all | |
5473c134 | 1841 | DOC_END |
1842 | ||
41bd17a4 | 1843 | NAME: htcp_access |
1844 | IFDEF: USE_HTCP | |
1845 | TYPE: acl_access | |
1846 | LOC: Config.accessList.htcp | |
638402dd AJ |
1847 | DEFAULT: none |
1848 | DEFAULT_DOC: Deny, unless rules exist in squid.conf. | |
5473c134 | 1849 | DOC_START |
41bd17a4 | 1850 | Allowing or Denying access to the HTCP port based on defined |
1851 | access lists | |
5473c134 | 1852 | |
41bd17a4 | 1853 | htcp_access allow|deny [!]aclname ... |
5473c134 | 1854 | |
638402dd AJ |
1855 | See also htcp_clr_access for details on access control for |
1856 | cache purge (CLR) HTCP messages. | |
5473c134 | 1857 | |
0b48417e | 1858 | NOTE: The default if no htcp_access lines are present is to |
1859 | deny all traffic. This default may cause problems with peers | |
18191440 | 1860 | using the htcp option. |
0b48417e | 1861 | |
b3567eb5 FC |
1862 | This clause only supports fast acl types. |
1863 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
e0855596 AJ |
1864 | |
1865 | # Allow HTCP queries from local networks only | |
df2eec10 AJ |
1866 | #htcp_access allow localnet |
1867 | #htcp_access deny all | |
41bd17a4 | 1868 | DOC_END |
5473c134 | 1869 | |
41bd17a4 | 1870 | NAME: htcp_clr_access |
1871 | IFDEF: USE_HTCP | |
1872 | TYPE: acl_access | |
1873 | LOC: Config.accessList.htcp_clr | |
638402dd AJ |
1874 | DEFAULT: none |
1875 | DEFAULT_DOC: Deny, unless rules exist in squid.conf. | |
41bd17a4 | 1876 | DOC_START |
1877 | Allowing or Denying access to purge content using HTCP based | |
638402dd AJ |
1878 | on defined access lists. |
1879 | See htcp_access for details on general HTCP access control. | |
5473c134 | 1880 | |
41bd17a4 | 1881 | htcp_clr_access allow|deny [!]aclname ... |
5473c134 | 1882 | |
b3567eb5 FC |
1883 | This clause only supports fast acl types. |
1884 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
e0855596 AJ |
1885 | |
1886 | # Allow HTCP CLR requests from trusted peers | |
638402dd | 1887 | acl htcp_clr_peer src 192.0.2.2 2001:DB8::2 |
41bd17a4 | 1888 | htcp_clr_access allow htcp_clr_peer |
638402dd | 1889 | htcp_clr_access deny all |
5473c134 | 1890 | DOC_END |
1891 | ||
41bd17a4 | 1892 | NAME: miss_access |
1893 | TYPE: acl_access | |
1894 | LOC: Config.accessList.miss | |
b8a25eaa | 1895 | DEFAULT: none |
638402dd | 1896 | DEFAULT_DOC: Allow, unless rules exist in squid.conf. |
5473c134 | 1897 | DOC_START |
18d1eddf | 1898 | Determines whether network access is permitted when satisfying a request. |
0b4fb91a AJ |
1899 | |
1900 | For example; | |
1901 | to force your neighbors to use you as a sibling instead of | |
1902 | a parent. | |
5473c134 | 1903 | |
638402dd | 1904 | acl localclients src 192.0.2.0/24 2001:DB8::a:0/64 |
41bd17a4 | 1905 | miss_access deny !localclients |
638402dd | 1906 | miss_access allow all |
5473c134 | 1907 | |
0b4fb91a AJ |
1908 | This means only your local clients are allowed to fetch relayed/MISS |
1909 | replies from the network and all other clients can only fetch cached | |
1910 | objects (HITs). | |
1911 | ||
0b4fb91a AJ |
1912 | The default for this setting allows all clients who passed the |
1913 | http_access rules to relay via this proxy. | |
b3567eb5 FC |
1914 | |
1915 | This clause only supports fast acl types. | |
1916 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
41bd17a4 | 1917 | DOC_END |
1918 | ||
1919 | NAME: ident_lookup_access | |
1920 | TYPE: acl_access | |
1921 | IFDEF: USE_IDENT | |
638402dd AJ |
1922 | DEFAULT: none |
1923 | DEFAULT_DOC: Unless rules exist in squid.conf, IDENT is not fetched. | |
4daaf3cb | 1924 | LOC: Ident::TheConfig.identLookup |
5473c134 | 1925 | DOC_START |
41bd17a4 | 1926 | A list of ACL elements which, if matched, cause an ident |
1927 | (RFC 931) lookup to be performed for this request. For | |
1928 | example, you might choose to always perform ident lookups | |
1929 | for your main multi-user Unix boxes, but not for your Macs | |
1930 | and PCs. By default, ident lookups are not performed for | |
1931 | any requests. | |
5473c134 | 1932 | |
41bd17a4 | 1933 | To enable ident lookups for specific client addresses, you |
1934 | can follow this example: | |
5473c134 | 1935 | |
4daaf3cb | 1936 | acl ident_aware_hosts src 198.168.1.0/24 |
41bd17a4 | 1937 | ident_lookup_access allow ident_aware_hosts |
1938 | ident_lookup_access deny all | |
5473c134 | 1939 | |
4daaf3cb | 1940 | Only src type ACL checks are fully supported. A srcdomain |
41bd17a4 | 1941 | ACL might work at times, but it will not always provide |
1942 | the correct result. | |
b3567eb5 FC |
1943 | |
1944 | This clause only supports fast acl types. | |
1945 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
41bd17a4 | 1946 | DOC_END |
5473c134 | 1947 | |
5b0f5383 | 1948 | NAME: reply_body_max_size |
1949 | COMMENT: size [acl acl...] | |
1950 | TYPE: acl_b_size_t | |
1951 | DEFAULT: none | |
638402dd | 1952 | DEFAULT_DOC: No limit is applied. |
5b0f5383 | 1953 | LOC: Config.ReplyBodySize |
1954 | DOC_START | |
1955 | This option specifies the maximum size of a reply body. It can be | |
1956 | used to prevent users from downloading very large files, such as | |
1957 | MP3's and movies. When the reply headers are received, the | |
1958 | reply_body_max_size lines are processed, and the first line where | |
1959 | all (if any) listed ACLs are true is used as the maximum body size | |
1960 | for this reply. | |
1961 | ||
1962 | This size is checked twice. First when we get the reply headers, | |
1963 | we check the content-length value. If the content length value exists | |
1964 | and is larger than the allowed size, the request is denied and the | |
1965 | user receives an error message that says "the request or reply | |
1966 | is too large." If there is no content-length, and the reply | |
1967 | size exceeds this limit, the client's connection is just closed | |
1968 | and they will receive a partial reply. | |
1969 | ||
1970 | WARNING: downstream caches probably can not detect a partial reply | |
1971 | if there is no content-length header, so they will cache | |
1972 | partial responses and give them out as hits. You should NOT | |
1973 | use this option if you have downstream caches. | |
1974 | ||
1975 | WARNING: A maximum size smaller than the size of squid's error messages | |
1976 | will cause an infinite loop and crash squid. Ensure that the smallest | |
1977 | non-zero value you use is greater that the maximum header size plus | |
1978 | the size of your largest error page. | |
1979 | ||
1980 | If you set this parameter none (the default), there will be | |
1981 | no limit imposed. | |
3bc32f2f AJ |
1982 | |
1983 | Configuration Format is: | |
1984 | reply_body_max_size SIZE UNITS [acl ...] | |
1985 | ie. | |
1986 | reply_body_max_size 10 MB | |
1987 | ||
5b0f5383 | 1988 | DOC_END |
1989 | ||
3248e962 CT |
1990 | NAME: on_unsupported_protocol |
1991 | TYPE: on_unsupported_protocol | |
1992 | LOC: Config.accessList.on_unsupported_protocol | |
1993 | DEFAULT: none | |
1994 | DEFAULT_DOC: Respond with an error message to unidentifiable traffic | |
1995 | DOC_START | |
1996 | Determines Squid behavior when encountering strange requests at the | |
56d089f3 CT |
1997 | beginning of an accepted TCP connection or the beginning of a bumped |
1998 | CONNECT tunnel. Controlling Squid reaction to unexpected traffic is | |
1999 | especially useful in interception environments where Squid is likely | |
2000 | to see connections for unsupported protocols that Squid should either | |
2001 | terminate or tunnel at TCP level. | |
3248e962 CT |
2002 | |
2003 | on_unsupported_protocol <action> [!]acl ... | |
2004 | ||
56d089f3 | 2005 | The first matching action wins. Only fast ACLs are supported. |
3248e962 CT |
2006 | |
2007 | Supported actions are: | |
2008 | ||
2009 | tunnel: Establish a TCP connection with the intended server and | |
2010 | blindly shovel TCP packets between the client and server. | |
2011 | ||
2012 | respond: Respond with an error message, using the transfer protocol | |
2013 | for the Squid port that received the request (e.g., HTTP | |
2014 | for connections intercepted at the http_port). This is the | |
2015 | default. | |
56d089f3 CT |
2016 | |
2017 | Squid expects the following traffic patterns: | |
2018 | ||
2019 | http_port: a plain HTTP request | |
2020 | https_port: SSL/TLS handshake followed by an [encrypted] HTTP request | |
2021 | ftp_port: a plain FTP command (no on_unsupported_protocol support yet!) | |
2022 | CONNECT tunnel on http_port: same as https_port | |
2023 | CONNECT tunnel on https_port: same as https_port | |
2024 | ||
9155253a | 2025 | Currently, this directive has effect on intercepted connections and |
56d089f3 CT |
2026 | bumped tunnels only. Other cases are not supported because Squid |
2027 | cannot know the intended destination of other traffic. | |
3248e962 CT |
2028 | |
2029 | For example: | |
2030 | # define what Squid errors indicate receiving non-HTTP traffic: | |
2031 | acl foreignProtocol squid_error ERR_PROTOCOL_UNKNOWN ERR_TOO_BIG | |
2032 | # define what Squid errors indicate receiving nothing: | |
2033 | acl serverTalksFirstProtocol squid_error ERR_REQUEST_START_TIMEOUT | |
2034 | # tunnel everything that does not look like HTTP: | |
2035 | on_unsupported_protocol tunnel foreignProtocol | |
2036 | # tunnel if we think the client waits for the server to talk first: | |
2037 | on_unsupported_protocol tunnel serverTalksFirstProtocol | |
2038 | # in all other error cases, just send an HTTP "error page" response: | |
2039 | on_unsupported_protocol respond all | |
2040 | ||
2041 | See also: squid_error ACL | |
2042 | DOC_END | |
2043 | ||
d6e94bda AJ |
2044 | NAME: auth_schemes |
2045 | TYPE: AuthSchemes | |
2046 | IFDEF: USE_AUTH | |
2047 | LOC: Auth::TheConfig.schemeAccess | |
2048 | DEFAULT: none | |
2049 | DEFAULT_DOC: use all auth_param schemes in their configuration order | |
2050 | DOC_START | |
2051 | Use this directive to customize authentication schemes presence and | |
2052 | order in Squid's Unauthorized and Authentication Required responses. | |
2053 | ||
2054 | auth_schemes scheme1,scheme2,... [!]aclname ... | |
2055 | ||
2056 | where schemeN is the name of one of the authentication schemes | |
2057 | configured using auth_param directives. At least one scheme name is | |
2058 | required. Multiple scheme names are separated by commas. Either | |
2059 | avoid whitespace or quote the entire schemes list. | |
2060 | ||
2061 | A special "ALL" scheme name expands to all auth_param-configured | |
2062 | schemes in their configuration order. This directive cannot be used | |
2063 | to configure Squid to offer no authentication schemes at all. | |
2064 | ||
2065 | The first matching auth_schemes rule determines the schemes order | |
2066 | for the current Authentication Required transaction. Note that the | |
2067 | future response is not yet available during auth_schemes evaluation. | |
2068 | ||
2069 | If this directive is not used or none of its rules match, then Squid | |
2070 | responds with all configured authentication schemes in the order of | |
2071 | auth_param directives in the configuration file. | |
2072 | ||
2073 | This directive does not determine when authentication is used or | |
2074 | how each authentication scheme authenticates clients. | |
2075 | ||
2076 | The following example sends basic and negotiate authentication | |
2077 | schemes, in that order, when requesting authentication of HTTP | |
2078 | requests matching the isIE ACL (not shown) while sending all | |
2079 | auth_param schemes in their configuration order to other clients: | |
2080 | ||
2081 | auth_schemes basic,negotiate isIE | |
2082 | auth_schemes ALL all # explicit default | |
2083 | ||
2084 | This directive supports fast ACLs only. | |
2085 | ||
2086 | See also: auth_param. | |
2087 | DOC_END | |
2088 | ||
5b0f5383 | 2089 | COMMENT_START |
2090 | NETWORK OPTIONS | |
2091 | ----------------------------------------------------------------------------- | |
2092 | COMMENT_END | |
2093 | ||
2094 | NAME: http_port ascii_port | |
65d448bc | 2095 | TYPE: PortCfg |
5b0f5383 | 2096 | DEFAULT: none |
fa720bfb | 2097 | LOC: HttpPortList |
5b0f5383 | 2098 | DOC_START |
c7b1dd5d AJ |
2099 | Usage: port [mode] [options] |
2100 | hostname:port [mode] [options] | |
2101 | 1.2.3.4:port [mode] [options] | |
5b0f5383 | 2102 | |
2103 | The socket addresses where Squid will listen for HTTP client | |
2104 | requests. You may specify multiple socket addresses. | |
2105 | There are three forms: port alone, hostname with port, and | |
2106 | IP address with port. If you specify a hostname or IP | |
2107 | address, Squid binds the socket to that specific | |
c7b1dd5d | 2108 | address. Most likely, you do not need to bind to a specific |
5b0f5383 | 2109 | address, so you can use the port number alone. |
2110 | ||
2111 | If you are running Squid in accelerator mode, you | |
2112 | probably want to listen on port 80 also, or instead. | |
2113 | ||
2114 | The -a command line option may be used to specify additional | |
2115 | port(s) where Squid listens for proxy request. Such ports will | |
2116 | be plain proxy ports with no options. | |
2117 | ||
2118 | You may specify multiple socket addresses on multiple lines. | |
2119 | ||
c7b1dd5d | 2120 | Modes: |
5b0f5383 | 2121 | |
16ae256c AJ |
2122 | intercept Support for IP-Layer NAT interception delivering |
2123 | traffic to this Squid port. | |
2124 | NP: disables authentication on the port. | |
5b0f5383 | 2125 | |
16ae256c AJ |
2126 | tproxy Support Linux TPROXY (or BSD divert-to) with spoofing |
2127 | of outgoing connections using the client IP address. | |
2128 | NP: disables authentication on the port. | |
5b0f5383 | 2129 | |
7f45065d | 2130 | accel Accelerator / reverse proxy mode |
5b0f5383 | 2131 | |
caf3666d | 2132 | ssl-bump For each CONNECT request allowed by ssl_bump ACLs, |
c7b1dd5d | 2133 | establish secure connection with the client and with |
caf3666d | 2134 | the server, decrypt HTTPS messages as they pass through |
c7b1dd5d AJ |
2135 | Squid, and treat them as unencrypted HTTP messages, |
2136 | becoming the man-in-the-middle. | |
2137 | ||
7a957a93 | 2138 | The ssl_bump option is required to fully enable |
caf3666d | 2139 | bumping of CONNECT requests. |
c7b1dd5d AJ |
2140 | |
2141 | Omitting the mode flag causes default forward proxy mode to be used. | |
2142 | ||
2143 | ||
2144 | Accelerator Mode Options: | |
2145 | ||
5b0f5383 | 2146 | defaultsite=domainname |
2147 | What to use for the Host: header if it is not present | |
2148 | in a request. Determines what site (not origin server) | |
2149 | accelerators should consider the default. | |
5b0f5383 | 2150 | |
cf673853 | 2151 | no-vhost Disable using HTTP/1.1 Host header for virtual domain support. |
5b0f5383 | 2152 | |
a9f60805 AJ |
2153 | protocol= Protocol to reconstruct accelerated and intercepted |
2154 | requests with. Defaults to HTTP/1.1 for http_port and | |
2155 | HTTPS/1.1 for https_port. | |
2156 | When an unsupported value is configured Squid will | |
2157 | produce a FATAL error. | |
2158 | Values: HTTP or HTTP/1.1, HTTPS or HTTPS/1.1 | |
5b0f5383 | 2159 | |
cf673853 AJ |
2160 | vport Virtual host port support. Using the http_port number |
2161 | instead of the port passed on Host: headers. | |
5b0f5383 | 2162 | |
cf673853 AJ |
2163 | vport=NN Virtual host port support. Using the specified port |
2164 | number instead of the port passed on Host: headers. | |
5b0f5383 | 2165 | |
7f45065d HN |
2166 | act-as-origin |
2167 | Act as if this Squid is the origin server. | |
2168 | This currently means generate new Date: and Expires: | |
2169 | headers on HIT instead of adding Age:. | |
5b0f5383 | 2170 | |
432bc83c HN |
2171 | ignore-cc Ignore request Cache-Control headers. |
2172 | ||
7f45065d | 2173 | WARNING: This option violates HTTP specifications if |
432bc83c HN |
2174 | used in non-accelerator setups. |
2175 | ||
7f45065d HN |
2176 | allow-direct Allow direct forwarding in accelerator mode. Normally |
2177 | accelerated requests are denied direct forwarding as if | |
2178 | never_direct was used. | |
2179 | ||
2180 | WARNING: this option opens accelerator mode to security | |
2181 | vulnerabilities usually only affecting in interception | |
2182 | mode. Make sure to protect forwarding with suitable | |
2183 | http_access rules when using this. | |
2184 | ||
c7b1dd5d AJ |
2185 | |
2186 | SSL Bump Mode Options: | |
859741ed AJ |
2187 | In addition to these options ssl-bump requires TLS/SSL options. |
2188 | ||
2189 | generate-host-certificates[=<on|off>] | |
2190 | Dynamically create SSL server certificates for the | |
2191 | destination hosts of bumped CONNECT requests.When | |
2192 | enabled, the cert and key options are used to sign | |
2193 | generated certificates. Otherwise generated | |
2194 | certificate will be selfsigned. | |
2195 | If there is a CA certificate lifetime of the generated | |
2196 | certificate equals lifetime of the CA certificate. If | |
2197 | generated certificate is selfsigned lifetime is three | |
2198 | years. | |
2199 | This option is enabled by default when ssl-bump is used. | |
2200 | See the ssl-bump option above for more information. | |
2201 | ||
2202 | dynamic_cert_mem_cache_size=SIZE | |
2203 | Approximate total RAM size spent on cached generated | |
2204 | certificates. If set to zero, caching is disabled. The | |
23bb0ebf | 2205 | default value is 4MB. |
859741ed AJ |
2206 | |
2207 | TLS / SSL Options: | |
c7b1dd5d AJ |
2208 | |
2209 | cert= Path to SSL certificate (PEM format). | |
2210 | ||
2211 | key= Path to SSL private key file (PEM format) | |
2212 | if not specified, the certificate file is | |
2213 | assumed to be a combined certificate and | |
2214 | key file. | |
2215 | ||
c7b1dd5d | 2216 | cipher= Colon separated list of supported ciphers. |
bebdc6fb AJ |
2217 | NOTE: some ciphers such as EDH ciphers depend on |
2218 | additional settings. If those settings are | |
2219 | omitted the ciphers may be silently ignored | |
2220 | by the OpenSSL library. | |
c7b1dd5d | 2221 | |
943c5f16 | 2222 | options= Various SSL implementation options. The most important |
c7b1dd5d | 2223 | being: |
7905e7be | 2224 | |
3d96b0e8 | 2225 | NO_SSLv3 Disallow the use of SSLv3 |
1f1f29e8 | 2226 | |
3d96b0e8 | 2227 | NO_TLSv1 Disallow the use of TLSv1.0 |
1f1f29e8 | 2228 | |
3d96b0e8 | 2229 | NO_TLSv1_1 Disallow the use of TLSv1.1 |
1f1f29e8 | 2230 | |
3d96b0e8 | 2231 | NO_TLSv1_2 Disallow the use of TLSv1.2 |
1f1f29e8 | 2232 | |
7905e7be AJ |
2233 | SINGLE_DH_USE |
2234 | Always create a new key when using | |
c7b1dd5d | 2235 | temporary/ephemeral DH key exchanges |
1f1f29e8 | 2236 | |
54fbe371 PM |
2237 | SINGLE_ECDH_USE |
2238 | Enable ephemeral ECDH key exchange. | |
2239 | The adopted curve should be specified | |
2240 | using the tls-dh option. | |
2241 | ||
36092741 | 2242 | NO_TICKET |
1f1f29e8 AJ |
2243 | Disable use of RFC5077 session tickets. |
2244 | Some servers may have problems | |
2245 | understanding the TLS extension due | |
2246 | to ambiguous specification in RFC4507. | |
2247 | ||
943c5f16 HN |
2248 | ALL Enable various bug workarounds |
2249 | suggested as "harmless" by OpenSSL | |
2250 | Be warned that this reduces SSL/TLS | |
2251 | strength to some attacks. | |
7905e7be AJ |
2252 | |
2253 | See the OpenSSL SSL_CTX_set_options documentation for a | |
2254 | more complete list. | |
c7b1dd5d AJ |
2255 | |
2256 | clientca= File containing the list of CAs to use when | |
2257 | requesting a client certificate. | |
2258 | ||
86a84cc0 AJ |
2259 | tls-cafile= PEM file containing CA certificates to use when verifying |
2260 | client certificates. If not configured clientca will be | |
2261 | used. May be repeated to load multiple files. | |
c7b1dd5d AJ |
2262 | |
2263 | capath= Directory containing additional CA certificates | |
2264 | and CRL lists to use when verifying client certificates. | |
86a84cc0 | 2265 | Requires OpenSSL or LibreSSL. |
c7b1dd5d AJ |
2266 | |
2267 | crlfile= File of additional CRL lists to use when verifying | |
2268 | the client certificate, in addition to CRLs stored in | |
2269 | the capath. Implies VERIFY_CRL flag below. | |
2270 | ||
54fbe371 PM |
2271 | tls-dh=[curve:]file |
2272 | File containing DH parameters for temporary/ephemeral DH key | |
2273 | exchanges, optionally prefixed by a curve for ephemeral ECDH | |
2274 | key exchanges. | |
2275 | See OpenSSL documentation for details on how to create the | |
2276 | DH parameter file. Supported curves for ECDH can be listed | |
2277 | using the "openssl ecparam -list_curves" command. | |
2278 | WARNING: EDH and EECDH ciphers will be silently disabled if | |
2279 | this option is not set. | |
c7b1dd5d AJ |
2280 | |
2281 | sslflags= Various flags modifying the use of SSL: | |
2282 | DELAYED_AUTH | |
2283 | Don't request client certificates | |
2284 | immediately, but wait until acl processing | |
2285 | requires a certificate (not yet implemented). | |
c7b1dd5d AJ |
2286 | NO_SESSION_REUSE |
2287 | Don't allow for session reuse. Each connection | |
2288 | will result in a new SSL session. | |
2289 | VERIFY_CRL | |
2290 | Verify CRL lists when accepting client | |
2291 | certificates. | |
2292 | VERIFY_CRL_ALL | |
2293 | Verify CRL lists for all certificates in the | |
2294 | client certificate chain. | |
2295 | ||
435c72b0 AJ |
2296 | tls-default-ca[=off] |
2297 | Whether to use the system Trusted CAs. Default is OFF. | |
8b253b83 | 2298 | |
b05d749d AJ |
2299 | tls-no-npn Do not use the TLS NPN extension to advertise HTTP/1.1. |
2300 | ||
c7b1dd5d AJ |
2301 | sslcontext= SSL session ID context identifier. |
2302 | ||
c7b1dd5d AJ |
2303 | Other Options: |
2304 | ||
6b185b50 AJ |
2305 | connection-auth[=on|off] |
2306 | use connection-auth=off to tell Squid to prevent | |
2307 | forwarding Microsoft connection oriented authentication | |
d67acb4e AJ |
2308 | (NTLM, Negotiate and Kerberos) |
2309 | ||
5b0f5383 | 2310 | disable-pmtu-discovery= |
2311 | Control Path-MTU discovery usage: | |
2312 | off lets OS decide on what to do (default). | |
2313 | transparent disable PMTU discovery when transparent | |
2314 | support is enabled. | |
2315 | always disable always PMTU discovery. | |
2316 | ||
2317 | In many setups of transparently intercepting proxies | |
2318 | Path-MTU discovery can not work on traffic towards the | |
2319 | clients. This is the case when the intercepting device | |
2320 | does not fully track connections and fails to forward | |
2321 | ICMP must fragment messages to the cache server. If you | |
2322 | have such setup and experience that certain clients | |
2323 | sporadically hang or never complete requests set | |
2324 | disable-pmtu-discovery option to 'transparent'. | |
2325 | ||
81b6e9a7 | 2326 | name= Specifies a internal name for the port. Defaults to |
2327 | the port specification (port or addr:port) | |
2328 | ||
68924b6d | 2329 | tcpkeepalive[=idle,interval,timeout] |
fb6c6dbe AJ |
2330 | Enable TCP keepalive probes of idle connections. |
2331 | In seconds; idle is the initial time before TCP starts | |
2332 | probing the connection, interval how often to probe, and | |
b2130d58 | 2333 | timeout the time before giving up. |
2334 | ||
d3d92daa | 2335 | require-proxy-header |
151ba0d4 | 2336 | Require PROXY protocol version 1 or 2 connections. |
d3d92daa | 2337 | The proxy_protocol_access is required to whitelist |
151ba0d4 AJ |
2338 | downstream proxies which can be trusted. |
2339 | ||
5b0f5383 | 2340 | If you run Squid on a dual-homed machine with an internal |
2341 | and an external interface we recommend you to specify the | |
2342 | internal address:port in http_port. This way Squid will only be | |
2343 | visible on the internal address. | |
2344 | ||
2345 | NOCOMMENT_START | |
e0855596 | 2346 | |
5b0f5383 | 2347 | # Squid normally listens to port 3128 |
2348 | http_port @DEFAULT_HTTP_PORT@ | |
2349 | NOCOMMENT_END | |
2350 | DOC_END | |
2351 | ||
2352 | NAME: https_port | |
339e4d7a | 2353 | IFDEF: USE_GNUTLS||USE_OPENSSL |
65d448bc | 2354 | TYPE: PortCfg |
5b0f5383 | 2355 | DEFAULT: none |
339e4d7a | 2356 | LOC: HttpPortList |
5b0f5383 | 2357 | DOC_START |
9155253a | 2358 | Usage: [ip:]port [mode] cert=certificate.pem [options] |
5b0f5383 | 2359 | |
859741ed AJ |
2360 | The socket address where Squid will listen for client requests made |
2361 | over TLS or SSL connections. Commonly referred to as HTTPS. | |
5b0f5383 | 2362 | |
859741ed | 2363 | This is most useful for situations where you are running squid in |
9155253a | 2364 | accelerator mode and you want to do the TLS work at the accelerator level. |
5b0f5383 | 2365 | |
2366 | You may specify multiple socket addresses on multiple lines, | |
9155253a | 2367 | each with their own certificate and/or options. |
5b0f5383 | 2368 | |
9155253a | 2369 | The TLS cert= option is mandatory on HTTPS ports. |
379e8c1c | 2370 | |
9155253a | 2371 | See http_port for a list of modes and options. |
5b0f5383 | 2372 | DOC_END |
2373 | ||
434a79b0 DK |
2374 | NAME: ftp_port |
2375 | TYPE: PortCfg | |
2376 | DEFAULT: none | |
8ea0d847 | 2377 | LOC: FtpPortList |
434a79b0 | 2378 | DOC_START |
8a2f40dd AR |
2379 | Enables Native FTP proxy by specifying the socket address where Squid |
2380 | listens for FTP client requests. See http_port directive for various | |
2381 | ways to specify the listening address and mode. | |
2382 | ||
2383 | Usage: ftp_port address [mode] [options] | |
2384 | ||
2385 | WARNING: This is a new, experimental, complex feature that has seen | |
2386 | limited production exposure. Some Squid modules (e.g., caching) do not | |
2387 | currently work with native FTP proxying, and many features have not | |
2388 | even been tested for compatibility. Test well before deploying! | |
2389 | ||
2390 | Native FTP proxying differs substantially from proxying HTTP requests | |
2391 | with ftp:// URIs because Squid works as an FTP server and receives | |
2392 | actual FTP commands (rather than HTTP requests with FTP URLs). | |
2393 | ||
2394 | Native FTP commands accepted at ftp_port are internally converted or | |
2395 | wrapped into HTTP-like messages. The same happens to Native FTP | |
2396 | responses received from FTP origin servers. Those HTTP-like messages | |
2397 | are shoveled through regular access control and adaptation layers | |
2398 | between the FTP client and the FTP origin server. This allows Squid to | |
2399 | examine, adapt, block, and log FTP exchanges. Squid reuses most HTTP | |
2400 | mechanisms when shoveling wrapped FTP messages. For example, | |
2401 | http_access and adaptation_access directives are used. | |
2402 | ||
2403 | Modes: | |
2404 | ||
3cc0f4e7 | 2405 | intercept Same as http_port intercept. The FTP origin address is |
8a2f40dd AR |
2406 | determined based on the intended destination of the |
2407 | intercepted connection. | |
2408 | ||
3cc0f4e7 AR |
2409 | tproxy Support Linux TPROXY for spoofing outgoing |
2410 | connections using the client IP address. | |
2411 | NP: disables authentication and maybe IPv6 on the port. | |
2412 | ||
8a2f40dd AR |
2413 | By default (i.e., without an explicit mode option), Squid extracts the |
2414 | FTP origin address from the login@origin parameter of the FTP USER | |
2415 | command. Many popular FTP clients support such native FTP proxying. | |
2416 | ||
2417 | Options: | |
2418 | ||
3cc0f4e7 AR |
2419 | name=token Specifies an internal name for the port. Defaults to |
2420 | the port address. Usable with myportname ACL. | |
2421 | ||
aea65fec | 2422 | ftp-track-dirs |
8a2f40dd AR |
2423 | Enables tracking of FTP directories by injecting extra |
2424 | PWD commands and adjusting Request-URI (in wrapping | |
2425 | HTTP requests) to reflect the current FTP server | |
aea65fec | 2426 | directory. Tracking is disabled by default. |
8a2f40dd | 2427 | |
3cc0f4e7 AR |
2428 | protocol=FTP Protocol to reconstruct accelerated and intercepted |
2429 | requests with. Defaults to FTP. No other accepted | |
2430 | values have been tested with. An unsupported value | |
2431 | results in a FATAL error. Accepted values are FTP, | |
2432 | HTTP (or HTTP/1.1), and HTTPS (or HTTPS/1.1). | |
2433 | ||
8a2f40dd AR |
2434 | Other http_port modes and options that are not specific to HTTP and |
2435 | HTTPS may also work. | |
2436 | DOC_END | |
434a79b0 | 2437 | |
41bd17a4 | 2438 | NAME: tcp_outgoing_tos tcp_outgoing_ds tcp_outgoing_dscp |
2439 | TYPE: acl_tos | |
5473c134 | 2440 | DEFAULT: none |
425de4c8 | 2441 | LOC: Ip::Qos::TheConfig.tosToServer |
5473c134 | 2442 | DOC_START |
425de4c8 AJ |
2443 | Allows you to select a TOS/Diffserv value for packets outgoing |
2444 | on the server side, based on an ACL. | |
5473c134 | 2445 | |
41bd17a4 | 2446 | tcp_outgoing_tos ds-field [!]aclname ... |
cccac0a2 | 2447 | |
41bd17a4 | 2448 | Example where normal_service_net uses the TOS value 0x00 |
7def7206 | 2449 | and good_service_net uses 0x20 |
cccac0a2 | 2450 | |
864a62b5 AJ |
2451 | acl normal_service_net src 10.0.0.0/24 |
2452 | acl good_service_net src 10.0.1.0/24 | |
2c73de90 | 2453 | tcp_outgoing_tos 0x00 normal_service_net |
41bd17a4 | 2454 | tcp_outgoing_tos 0x20 good_service_net |
fa38076e | 2455 | |
41bd17a4 | 2456 | TOS/DSCP values really only have local significance - so you should |
575cb927 AJ |
2457 | know what you're specifying. For more information, see RFC2474, |
2458 | RFC2475, and RFC3260. | |
cccac0a2 | 2459 | |
41bd17a4 | 2460 | The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or |
5f53baab SM |
2461 | "default" to use whatever default your host has. |
2462 | Note that only multiples of 4 are usable as the two rightmost bits have | |
2463 | been redefined for use by ECN (RFC 3168 section 23.1). | |
2464 | The squid parser will enforce this by masking away the ECN bits. | |
cccac0a2 | 2465 | |
41bd17a4 | 2466 | Processing proceeds in the order specified, and stops at first fully |
2467 | matching line. | |
c6f168c1 CT |
2468 | |
2469 | Only fast ACLs are supported. | |
cccac0a2 | 2470 | DOC_END |
2471 | ||
41bd17a4 | 2472 | NAME: clientside_tos |
2473 | TYPE: acl_tos | |
cccac0a2 | 2474 | DEFAULT: none |
425de4c8 AJ |
2475 | LOC: Ip::Qos::TheConfig.tosToClient |
2476 | DOC_START | |
5f53baab | 2477 | Allows you to select a TOS/DSCP value for packets being transmitted |
425de4c8 AJ |
2478 | on the client-side, based on an ACL. |
2479 | ||
2480 | clientside_tos ds-field [!]aclname ... | |
2481 | ||
2482 | Example where normal_service_net uses the TOS value 0x00 | |
2483 | and good_service_net uses 0x20 | |
2484 | ||
2485 | acl normal_service_net src 10.0.0.0/24 | |
2486 | acl good_service_net src 10.0.1.0/24 | |
2487 | clientside_tos 0x00 normal_service_net | |
2488 | clientside_tos 0x20 good_service_net | |
2489 | ||
2490 | Note: This feature is incompatible with qos_flows. Any TOS values set here | |
2491 | will be overwritten by TOS values in qos_flows. | |
5f53baab SM |
2492 | |
2493 | The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or | |
2494 | "default" to use whatever default your host has. | |
2495 | Note that only multiples of 4 are usable as the two rightmost bits have | |
2496 | been redefined for use by ECN (RFC 3168 section 23.1). | |
2497 | The squid parser will enforce this by masking away the ECN bits. | |
2498 | ||
83a846a3 AR |
2499 | This clause only supports fast acl types. |
2500 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
425de4c8 AJ |
2501 | DOC_END |
2502 | ||
2503 | NAME: tcp_outgoing_mark | |
2504 | TYPE: acl_nfmark | |
11e8cfe3 | 2505 | IFDEF: SO_MARK&&USE_LIBCAP |
425de4c8 AJ |
2506 | DEFAULT: none |
2507 | LOC: Ip::Qos::TheConfig.nfmarkToServer | |
2508 | DOC_START | |
2509 | Allows you to apply a Netfilter mark value to outgoing packets | |
2510 | on the server side, based on an ACL. | |
2511 | ||
2512 | tcp_outgoing_mark mark-value [!]aclname ... | |
2513 | ||
2514 | Example where normal_service_net uses the mark value 0x00 | |
2515 | and good_service_net uses 0x20 | |
2516 | ||
2517 | acl normal_service_net src 10.0.0.0/24 | |
2518 | acl good_service_net src 10.0.1.0/24 | |
2519 | tcp_outgoing_mark 0x00 normal_service_net | |
2520 | tcp_outgoing_mark 0x20 good_service_net | |
c6f168c1 CT |
2521 | |
2522 | Only fast ACLs are supported. | |
425de4c8 AJ |
2523 | DOC_END |
2524 | ||
2525 | NAME: clientside_mark | |
2526 | TYPE: acl_nfmark | |
11e8cfe3 | 2527 | IFDEF: SO_MARK&&USE_LIBCAP |
425de4c8 AJ |
2528 | DEFAULT: none |
2529 | LOC: Ip::Qos::TheConfig.nfmarkToClient | |
cccac0a2 | 2530 | DOC_START |
425de4c8 AJ |
2531 | Allows you to apply a Netfilter mark value to packets being transmitted |
2532 | on the client-side, based on an ACL. | |
2533 | ||
2534 | clientside_mark mark-value [!]aclname ... | |
2535 | ||
2536 | Example where normal_service_net uses the mark value 0x00 | |
2537 | and good_service_net uses 0x20 | |
2538 | ||
2539 | acl normal_service_net src 10.0.0.0/24 | |
2540 | acl good_service_net src 10.0.1.0/24 | |
2541 | clientside_mark 0x00 normal_service_net | |
2542 | clientside_mark 0x20 good_service_net | |
2543 | ||
2544 | Note: This feature is incompatible with qos_flows. Any mark values set here | |
2545 | will be overwritten by mark values in qos_flows. | |
83a846a3 AR |
2546 | |
2547 | This clause only supports fast acl types. | |
2548 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
41bd17a4 | 2549 | DOC_END |
cccac0a2 | 2550 | |
575cb927 AJ |
2551 | NAME: qos_flows |
2552 | TYPE: QosConfig | |
425de4c8 | 2553 | IFDEF: USE_QOS_TOS |
575cb927 | 2554 | DEFAULT: none |
b7ac5457 | 2555 | LOC: Ip::Qos::TheConfig |
7172612f | 2556 | DOC_START |
575cb927 | 2557 | Allows you to select a TOS/DSCP value to mark outgoing |
196a7776 AB |
2558 | connections to the client, based on where the reply was sourced. |
2559 | For platforms using netfilter, allows you to set a netfilter mark | |
425de4c8 | 2560 | value instead of, or in addition to, a TOS value. |
7172612f | 2561 | |
196a7776 AB |
2562 | By default this functionality is disabled. To enable it with the default |
2563 | settings simply use "qos_flows mark" or "qos_flows tos". Default | |
2564 | settings will result in the netfilter mark or TOS value being copied | |
2565 | from the upstream connection to the client. Note that it is the connection | |
2566 | CONNMARK value not the packet MARK value that is copied. | |
2567 | ||
2568 | It is not currently possible to copy the mark or TOS value from the | |
2569 | client to the upstream connection request. | |
2570 | ||
575cb927 AJ |
2571 | TOS values really only have local significance - so you should |
2572 | know what you're specifying. For more information, see RFC2474, | |
2573 | RFC2475, and RFC3260. | |
7172612f | 2574 | |
5f53baab SM |
2575 | The TOS/DSCP byte must be exactly that - a octet value 0 - 255. |
2576 | Note that only multiples of 4 are usable as the two rightmost bits have | |
2577 | been redefined for use by ECN (RFC 3168 section 23.1). | |
2578 | The squid parser will enforce this by masking away the ECN bits. | |
425de4c8 AJ |
2579 | |
2580 | Mark values can be any unsigned 32-bit integer value. | |
7172612f | 2581 | |
425de4c8 AJ |
2582 | This setting is configured by setting the following values: |
2583 | ||
2584 | tos|mark Whether to set TOS or netfilter mark values | |
575cb927 AJ |
2585 | |
2586 | local-hit=0xFF Value to mark local cache hits. | |
2587 | ||
2588 | sibling-hit=0xFF Value to mark hits from sibling peers. | |
2589 | ||
2590 | parent-hit=0xFF Value to mark hits from parent peers. | |
2591 | ||
a29d2a95 AB |
2592 | miss=0xFF[/mask] Value to mark cache misses. Takes precedence |
2593 | over the preserve-miss feature (see below), unless | |
2594 | mask is specified, in which case only the bits | |
2595 | specified in the mask are written. | |
575cb927 | 2596 | |
425de4c8 AJ |
2597 | The TOS variant of the following features are only possible on Linux |
2598 | and require your kernel to be patched with the TOS preserving ZPH | |
2599 | patch, available from http://zph.bratcheda.org | |
2600 | No patch is needed to preserve the netfilter mark, which will work | |
2601 | with all variants of netfilter. | |
575cb927 | 2602 | |
575cb927 | 2603 | disable-preserve-miss |
425de4c8 AJ |
2604 | This option disables the preservation of the TOS or netfilter |
2605 | mark. By default, the existing TOS or netfilter mark value of | |
2606 | the response coming from the remote server will be retained | |
2607 | and masked with miss-mark. | |
2608 | NOTE: in the case of a netfilter mark, the mark must be set on | |
2609 | the connection (using the CONNMARK target) not on the packet | |
2610 | (MARK target). | |
575cb927 AJ |
2611 | |
2612 | miss-mask=0xFF | |
425de4c8 AJ |
2613 | Allows you to mask certain bits in the TOS or mark value |
2614 | received from the remote server, before copying the value to | |
2615 | the TOS sent towards clients. | |
2616 | Default for tos: 0xFF (TOS from server is not changed). | |
2617 | Default for mark: 0xFFFFFFFF (mark from server is not changed). | |
2618 | ||
2619 | All of these features require the --enable-zph-qos compilation flag | |
2620 | (enabled by default). Netfilter marking also requires the | |
2621 | libnetfilter_conntrack libraries (--with-netfilter-conntrack) and | |
2622 | libcap 2.09+ (--with-libcap). | |
7172612f | 2623 | |
7172612f AJ |
2624 | DOC_END |
2625 | ||
41bd17a4 | 2626 | NAME: tcp_outgoing_address |
2627 | TYPE: acl_address | |
2628 | DEFAULT: none | |
638402dd | 2629 | DEFAULT_DOC: Address selection is performed by the operating system. |
41bd17a4 | 2630 | LOC: Config.accessList.outgoing_address |
2631 | DOC_START | |
2632 | Allows you to map requests to different outgoing IP addresses | |
2633 | based on the username or source address of the user making | |
2634 | the request. | |
7f7db318 | 2635 | |
41bd17a4 | 2636 | tcp_outgoing_address ipaddr [[!]aclname] ... |
c33aa074 | 2637 | |
2dd51400 AJ |
2638 | For example; |
2639 | Forwarding clients with dedicated IPs for certain subnets. | |
9197cd13 | 2640 | |
2dd51400 AJ |
2641 | acl normal_service_net src 10.0.0.0/24 |
2642 | acl good_service_net src 10.0.2.0/24 | |
2643 | ||
2644 | tcp_outgoing_address 2001:db8::c001 good_service_net | |
2645 | tcp_outgoing_address 10.1.0.2 good_service_net | |
2646 | ||
2647 | tcp_outgoing_address 2001:db8::beef normal_service_net | |
2648 | tcp_outgoing_address 10.1.0.1 normal_service_net | |
2649 | ||
2650 | tcp_outgoing_address 2001:db8::1 | |
2651 | tcp_outgoing_address 10.1.0.3 | |
9197cd13 | 2652 | |
41bd17a4 | 2653 | Processing proceeds in the order specified, and stops at first fully |
2654 | matching line. | |
cccac0a2 | 2655 | |
2dd51400 AJ |
2656 | Squid will add an implicit IP version test to each line. |
2657 | Requests going to IPv4 websites will use the outgoing 10.1.0.* addresses. | |
2658 | Requests going to IPv6 websites will use the outgoing 2001:db8:* addresses. | |
2659 | ||
2660 | ||
2661 | NOTE: The use of this directive using client dependent ACLs is | |
41bd17a4 | 2662 | incompatible with the use of server side persistent connections. To |
2663 | ensure correct results it is best to set server_persistent_connections | |
2664 | to off when using this directive in such configurations. | |
cc192b50 | 2665 | |
2dd51400 | 2666 | NOTE: The use of this directive to set a local IP on outgoing TCP links |
4ed968be | 2667 | is incompatible with using TPROXY to set client IP out outbound TCP links. |
2dd51400 AJ |
2668 | When needing to contact peers use the no-tproxy cache_peer option and the |
2669 | client_dst_passthru directive re-enable normal forwarding such as this. | |
cc192b50 | 2670 | |
83a846a3 AR |
2671 | This clause only supports fast acl types. |
2672 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
cccac0a2 | 2673 | DOC_END |
6db78a1a | 2674 | |
90529125 AJ |
2675 | NAME: host_verify_strict |
2676 | TYPE: onoff | |
2677 | DEFAULT: off | |
2678 | LOC: Config.onoff.hostStrictVerify | |
2679 | DOC_START | |
d8821934 AR |
2680 | Regardless of this option setting, when dealing with intercepted |
2681 | traffic, Squid always verifies that the destination IP address matches | |
2962f8b8 | 2682 | the Host header domain or IP (called 'authority form URL'). |
d8821934 AR |
2683 | |
2684 | This enforcement is performed to satisfy a MUST-level requirement in | |
2685 | RFC 2616 section 14.23: "The Host field value MUST represent the naming | |
2686 | authority of the origin server or gateway given by the original URL". | |
2962f8b8 AJ |
2687 | |
2688 | When set to ON: | |
2689 | Squid always responds with an HTTP 409 (Conflict) error | |
2690 | page and logs a security warning if there is no match. | |
2691 | ||
2692 | Squid verifies that the destination IP address matches | |
2693 | the Host header for forward-proxy and reverse-proxy traffic | |
2694 | as well. For those traffic types, Squid also enables the | |
2695 | following checks, comparing the corresponding Host header | |
2696 | and Request-URI components: | |
2697 | ||
2698 | * The host names (domain or IP) must be identical, | |
2699 | but valueless or missing Host header disables all checks. | |
2700 | For the two host names to match, both must be either IP | |
2701 | or FQDN. | |
2702 | ||
2703 | * Port numbers must be identical, but if a port is missing | |
2704 | the scheme-default port is assumed. | |
2705 | ||
2706 | ||
2707 | When set to OFF (the default): | |
2708 | Squid allows suspicious requests to continue but logs a | |
2709 | security warning and blocks caching of the response. | |
2710 | ||
2711 | * Forward-proxy traffic is not checked at all. | |
2712 | ||
2713 | * Reverse-proxy traffic is not checked at all. | |
2714 | ||
2715 | * Intercepted traffic which passes verification is handled | |
32c32865 | 2716 | according to client_dst_passthru. |
2962f8b8 | 2717 | |
7177edfb AJ |
2718 | * Intercepted requests which fail verification are sent |
2719 | to the client original destination instead of DIRECT. | |
2720 | This overrides 'client_dst_passthru off'. | |
2962f8b8 AJ |
2721 | |
2722 | For now suspicious intercepted CONNECT requests are always | |
2723 | responded to with an HTTP 409 (Conflict) error page. | |
bfe4e2fe | 2724 | |
bfe4e2fe | 2725 | |
7177edfb | 2726 | SECURITY NOTE: |
bfe4e2fe AJ |
2727 | |
2728 | As described in CVE-2009-0801 when the Host: header alone is used | |
2729 | to determine the destination of a request it becomes trivial for | |
2730 | malicious scripts on remote websites to bypass browser same-origin | |
2731 | security policy and sandboxing protections. | |
2732 | ||
2733 | The cause of this is that such applets are allowed to perform their | |
2734 | own HTTP stack, in which case the same-origin policy of the browser | |
2735 | sandbox only verifies that the applet tries to contact the same IP | |
2736 | as from where it was loaded at the IP level. The Host: header may | |
2737 | be different from the connected IP and approved origin. | |
7177edfb AJ |
2738 | |
2739 | DOC_END | |
6b185b50 | 2740 | |
7177edfb AJ |
2741 | NAME: client_dst_passthru |
2742 | TYPE: onoff | |
2743 | DEFAULT: on | |
2744 | LOC: Config.onoff.client_dst_passthru | |
2745 | DOC_START | |
2746 | With NAT or TPROXY intercepted traffic Squid may pass the request | |
2747 | directly to the original client destination IP or seek a faster | |
2748 | source using the HTTP Host header. | |
2749 | ||
2750 | Using Host to locate alternative servers can provide faster | |
2751 | connectivity with a range of failure recovery options. | |
2752 | But can also lead to connectivity trouble when the client and | |
2753 | server are attempting stateful interactions unaware of the proxy. | |
2754 | ||
2755 | This option (on by default) prevents alternative DNS entries being | |
2756 | located to send intercepted traffic DIRECT to an origin server. | |
2757 | The clients original destination IP and port will be used instead. | |
2758 | ||
2759 | Regardless of this option setting, when dealing with intercepted | |
2760 | traffic Squid will verify the Host: header and any traffic which | |
2761 | fails Host verification will be treated as if this option were ON. | |
2762 | ||
2763 | see host_verify_strict for details on the verification process. | |
cccac0a2 | 2764 | DOC_END |
2765 | ||
195f8adb AJ |
2766 | COMMENT_START |
2767 | TLS OPTIONS | |
2768 | ----------------------------------------------------------------------------- | |
2769 | COMMENT_END | |
2770 | ||
2771 | NAME: tls_outgoing_options | |
2772 | IFDEF: USE_GNUTLS||USE_OPENSSL | |
2773 | TYPE: securePeerOptions | |
2fbb02b1 | 2774 | DEFAULT: min-version=1.0 |
7e62a74f | 2775 | LOC: Security::ProxyOutgoingConfig |
195f8adb AJ |
2776 | DOC_START |
2777 | disable Do not support https:// URLs. | |
2778 | ||
2779 | cert=/path/to/client/certificate | |
2780 | A client TLS certificate to use when connecting. | |
2781 | ||
2782 | key=/path/to/client/private_key | |
2783 | The private TLS key corresponding to the cert= above. | |
2784 | If key= is not specified cert= is assumed to reference | |
2785 | a PEM file containing both the certificate and the key. | |
2786 | ||
195f8adb | 2787 | cipher=... The list of valid TLS ciphers to use. |
1cc44095 AJ |
2788 | |
2789 | min-version=1.N | |
2fbb02b1 AJ |
2790 | The minimum TLS protocol version to permit. |
2791 | To control SSLv3 use the options= parameter. | |
1cc44095 AJ |
2792 | Supported Values: 1.0 (default), 1.1, 1.2 |
2793 | ||
3f5b28fe | 2794 | options=... Specify various TLS/SSL implementation options. |
195f8adb | 2795 | |
3f5b28fe | 2796 | OpenSSL options most important are: |
7905e7be | 2797 | |
3f5b28fe | 2798 | NO_SSLv3 Disallow the use of SSLv3 |
7905e7be | 2799 | |
195f8adb AJ |
2800 | SINGLE_DH_USE |
2801 | Always create a new key when using | |
2802 | temporary/ephemeral DH key exchanges | |
7905e7be | 2803 | |
ce0adf1a | 2804 | NO_TICKET |
7905e7be AJ |
2805 | Disable use of RFC5077 session tickets. |
2806 | Some servers may have problems | |
2807 | understanding the TLS extension due | |
2808 | to ambiguous specification in RFC4507. | |
2809 | ||
195f8adb AJ |
2810 | ALL Enable various bug workarounds |
2811 | suggested as "harmless" by OpenSSL | |
7905e7be | 2812 | Be warned that this reduces SSL/TLS |
195f8adb AJ |
2813 | strength to some attacks. |
2814 | ||
3f5b28fe AJ |
2815 | See the OpenSSL SSL_CTX_set_options documentation |
2816 | for a more complete list. | |
2817 | ||
2818 | GnuTLS options most important are: | |
2819 | ||
2820 | %NO_TICKETS | |
2821 | Disable use of RFC5077 session tickets. | |
2822 | Some servers may have problems | |
2823 | understanding the TLS extension due | |
2824 | to ambiguous specification in RFC4507. | |
2825 | ||
2826 | See the GnuTLS Priority Strings documentation | |
2827 | for a more complete list. | |
2828 | http://www.gnutls.org/manual/gnutls.html#Priority-Strings | |
2829 | ||
195f8adb | 2830 | |
86a84cc0 AJ |
2831 | cafile= PEM file containing CA certificates to use when verifying |
2832 | the peer certificate. May be repeated to load multiple files. | |
2833 | ||
2834 | capath= A directory containing additional CA certificates to | |
195f8adb | 2835 | use when verifying the peer certificate. |
86a84cc0 | 2836 | Requires OpenSSL or LibreSSL. |
195f8adb AJ |
2837 | |
2838 | crlfile=... A certificate revocation list file to use when | |
2839 | verifying the peer certificate. | |
2840 | ||
2841 | flags=... Specify various flags modifying the TLS implementation: | |
2842 | ||
2843 | DONT_VERIFY_PEER | |
2844 | Accept certificates even if they fail to | |
2845 | verify. | |
195f8adb AJ |
2846 | DONT_VERIFY_DOMAIN |
2847 | Don't verify the peer certificate | |
2848 | matches the server name | |
2849 | ||
435c72b0 AJ |
2850 | default-ca[=off] |
2851 | Whether to use the system Trusted CAs. Default is ON. | |
8b253b83 | 2852 | |
195f8adb AJ |
2853 | domain= The peer name as advertised in its certificate. |
2854 | Used for verifying the correctness of the received peer | |
2855 | certificate. If not specified the peer hostname will be | |
2856 | used. | |
2857 | DOC_END | |
2858 | ||
41bd17a4 | 2859 | COMMENT_START |
2860 | SSL OPTIONS | |
2861 | ----------------------------------------------------------------------------- | |
2862 | COMMENT_END | |
2863 | ||
2864 | NAME: ssl_unclean_shutdown | |
cb4f4424 | 2865 | IFDEF: USE_OPENSSL |
cccac0a2 | 2866 | TYPE: onoff |
2867 | DEFAULT: off | |
41bd17a4 | 2868 | LOC: Config.SSL.unclean_shutdown |
cccac0a2 | 2869 | DOC_START |
41bd17a4 | 2870 | Some browsers (especially MSIE) bugs out on SSL shutdown |
2871 | messages. | |
cccac0a2 | 2872 | DOC_END |
2873 | ||
41bd17a4 | 2874 | NAME: ssl_engine |
cb4f4424 | 2875 | IFDEF: USE_OPENSSL |
cccac0a2 | 2876 | TYPE: string |
41bd17a4 | 2877 | LOC: Config.SSL.ssl_engine |
2878 | DEFAULT: none | |
cccac0a2 | 2879 | DOC_START |
41bd17a4 | 2880 | The OpenSSL engine to use. You will need to set this if you |
2881 | would like to use hardware SSL acceleration for example. | |
cccac0a2 | 2882 | DOC_END |
2883 | ||
10a69fc0 | 2884 | NAME: sslproxy_session_ttl |
cb4f4424 | 2885 | IFDEF: USE_OPENSSL |
10a69fc0 CT |
2886 | DEFAULT: 300 |
2887 | LOC: Config.SSL.session_ttl | |
2888 | TYPE: int | |
2889 | DOC_START | |
2890 | Sets the timeout value for SSL sessions | |
2891 | DOC_END | |
2892 | ||
2893 | NAME: sslproxy_session_cache_size | |
cb4f4424 | 2894 | IFDEF: USE_OPENSSL |
10a69fc0 CT |
2895 | DEFAULT: 2 MB |
2896 | LOC: Config.SSL.sessionCacheSize | |
2897 | TYPE: b_size_t | |
2898 | DOC_START | |
2899 | Sets the cache size to use for ssl session | |
2900 | DOC_END | |
2901 | ||
866be11c CT |
2902 | NAME: sslproxy_foreign_intermediate_certs |
2903 | IFDEF: USE_OPENSSL | |
2904 | DEFAULT: none | |
2905 | LOC: Config.ssl_client.foreignIntermediateCertsPath | |
2906 | TYPE: string | |
2907 | DOC_START | |
2908 | Many origin servers fail to send their full server certificate | |
2909 | chain for verification, assuming the client already has or can | |
2910 | easily locate any missing intermediate certificates. | |
2911 | ||
2912 | Squid uses the certificates from the specified file to fill in | |
2913 | these missing chains when trying to validate origin server | |
2914 | certificate chains. | |
2915 | ||
2916 | The file is expected to contain zero or more PEM-encoded | |
2917 | intermediate certificates. These certificates are not treated | |
2918 | as trusted root certificates, and any self-signed certificate in | |
2919 | this file will be ignored. | |
866be11c CT |
2920 | DOC_END |
2921 | ||
3c26b00a CT |
2922 | NAME: sslproxy_cert_sign_hash |
2923 | IFDEF: USE_OPENSSL | |
2924 | DEFAULT: none | |
2925 | LOC: Config.SSL.certSignHash | |
2926 | TYPE: string | |
2927 | DOC_START | |
2928 | Sets the hashing algorithm to use when signing generated certificates. | |
2929 | Valid algorithm names depend on the OpenSSL library used. The following | |
2930 | names are usually available: sha1, sha256, sha512, and md5. Please see | |
2931 | your OpenSSL library manual for the available hashes. By default, Squids | |
2932 | that support this option use sha256 hashes. | |
2933 | ||
2934 | Squid does not forcefully purge cached certificates that were generated | |
2935 | with an algorithm other than the currently configured one. They remain | |
2936 | in the cache, subject to the regular cache eviction policy, and become | |
2937 | useful if the algorithm changes again. | |
2938 | DOC_END | |
2939 | ||
4c9da963 | 2940 | NAME: ssl_bump |
cb4f4424 | 2941 | IFDEF: USE_OPENSSL |
caf3666d | 2942 | TYPE: sslproxy_ssl_bump |
4c9da963 | 2943 | LOC: Config.accessList.ssl_bump |
8f165829 | 2944 | DEFAULT_DOC: Become a TCP tunnel without decrypting proxied traffic. |
4c9da963 | 2945 | DEFAULT: none |
2946 | DOC_START | |
caf3666d AR |
2947 | This option is consulted when a CONNECT request is received on |
2948 | an http_port (or a new connection is intercepted at an | |
2949 | https_port), provided that port was configured with an ssl-bump | |
2950 | flag. The subsequent data on the connection is either treated as | |
2951 | HTTPS and decrypted OR tunneled at TCP level without decryption, | |
8f165829 AR |
2952 | depending on the first matching bumping "action". |
2953 | ||
2954 | ssl_bump <action> [!]acl ... | |
caf3666d | 2955 | |
8f165829 | 2956 | The following bumping actions are currently supported: |
caf3666d | 2957 | |
5d65362c | 2958 | splice |
8f165829 AR |
2959 | Become a TCP tunnel without decrypting proxied traffic. |
2960 | This is the default action. | |
5d65362c CT |
2961 | |
2962 | bump | |
6e0516b3 CT |
2963 | When used on step SslBump1, establishes a secure connection |
2964 | with the client first, then connect to the server. | |
2965 | When used on step SslBump2 or SslBump3, establishes a secure | |
2966 | connection with the server and, using a mimicked server | |
2967 | certificate, with the client. | |
caf3666d | 2968 | |
5d65362c | 2969 | peek |
1110989a | 2970 | Receive client (step SslBump1) or server (step SslBump2) |
8f165829 AR |
2971 | certificate while preserving the possibility of splicing the |
2972 | connection. Peeking at the server certificate (during step 2) | |
2973 | usually precludes bumping of the connection at step 3. | |
caf3666d | 2974 | |
5d65362c | 2975 | stare |
1110989a | 2976 | Receive client (step SslBump1) or server (step SslBump2) |
8f165829 AR |
2977 | certificate while preserving the possibility of bumping the |
2978 | connection. Staring at the server certificate (during step 2) | |
2979 | usually precludes splicing of the connection at step 3. | |
5d65362c CT |
2980 | |
2981 | terminate | |
2982 | Close client and server connections. | |
2983 | ||
1110989a | 2984 | Backward compatibility actions available at step SslBump1: |
caf3666d AR |
2985 | |
2986 | client-first | |
8f165829 AR |
2987 | Bump the connection. Establish a secure connection with the |
2988 | client first, then connect to the server. This old mode does | |
2989 | not allow Squid to mimic server SSL certificate and does not | |
2990 | work with intercepted SSL connections. | |
caf3666d AR |
2991 | |
2992 | server-first | |
8f165829 AR |
2993 | Bump the connection. Establish a secure connection with the |
2994 | server first, then establish a secure connection with the | |
2995 | client, using a mimicked server certificate. Works with both | |
2996 | CONNECT requests and intercepted SSL connections, but does | |
2997 | not allow to make decisions based on SSL handshake info. | |
caf3666d | 2998 | |
8f165829 AR |
2999 | peek-and-splice |
3000 | Decide whether to bump or splice the connection based on | |
d620ae0e | 3001 | client-to-squid and server-to-squid SSL hello messages. |
8f165829 | 3002 | XXX: Remove. |
caf3666d | 3003 | |
caf3666d | 3004 | none |
8f165829 | 3005 | Same as the "splice" action. |
caf3666d | 3006 | |
8f165829 AR |
3007 | All ssl_bump rules are evaluated at each of the supported bumping |
3008 | steps. Rules with actions that are impossible at the current step are | |
3009 | ignored. The first matching ssl_bump action wins and is applied at the | |
3010 | end of the current step. If no rules match, the splice action is used. | |
652fcffd | 3011 | See the at_step ACL for a list of the supported SslBump steps. |
4c9da963 | 3012 | |
e0c0d54c | 3013 | This clause supports both fast and slow acl types. |
b3567eb5 | 3014 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. |
e0855596 | 3015 | |
652fcffd | 3016 | See also: http_port ssl-bump, https_port ssl-bump, and acl at_step. |
caf3666d | 3017 | |
e0855596 | 3018 | |
f3fece95 | 3019 | # Example: Bump all TLS connections except those originating from |
638402dd | 3020 | # localhost or those going to example.com. |
e0855596 | 3021 | |
f3fece95 | 3022 | acl broken_sites ssl::server_name .example.com |
8f165829 AR |
3023 | ssl_bump splice localhost |
3024 | ssl_bump splice broken_sites | |
3025 | ssl_bump bump all | |
4c9da963 | 3026 | DOC_END |
3027 | ||
4c9da963 | 3028 | NAME: sslproxy_cert_error |
cb4f4424 | 3029 | IFDEF: USE_OPENSSL |
4c9da963 | 3030 | DEFAULT: none |
638402dd | 3031 | DEFAULT_DOC: Server certificate errors terminate the transaction. |
4c9da963 | 3032 | LOC: Config.ssl_client.cert_error |
3033 | TYPE: acl_access | |
3034 | DOC_START | |
3035 | Use this ACL to bypass server certificate validation errors. | |
3036 | ||
3037 | For example, the following lines will bypass all validation errors | |
3b8f558c | 3038 | when talking to servers for example.com. All other |
4c9da963 | 3039 | validation errors will result in ERR_SECURE_CONNECT_FAIL error. |
3040 | ||
a87bfd3b AR |
3041 | acl BrokenButTrustedServers dstdomain example.com |
3042 | sslproxy_cert_error allow BrokenButTrustedServers | |
4c9da963 | 3043 | sslproxy_cert_error deny all |
3044 | ||
b3567eb5 FC |
3045 | This clause only supports fast acl types. |
3046 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
3047 | Using slow acl types may result in server crashes | |
4c9da963 | 3048 | |
3049 | Without this option, all server certificate validation errors | |
638402dd | 3050 | terminate the transaction to protect Squid and the client. |
4c9da963 | 3051 | |
0ad3ff51 CT |
3052 | SQUID_X509_V_ERR_INFINITE_VALIDATION error cannot be bypassed |
3053 | but should not happen unless your OpenSSL library is buggy. | |
3054 | ||
638402dd AJ |
3055 | SECURITY WARNING: |
3056 | Bypassing validation errors is dangerous because an | |
3057 | error usually implies that the server cannot be trusted | |
3058 | and the connection may be insecure. | |
4c9da963 | 3059 | |
638402dd | 3060 | See also: sslproxy_flags and DONT_VERIFY_PEER. |
4c9da963 | 3061 | DOC_END |
3062 | ||
aebe6888 | 3063 | NAME: sslproxy_cert_sign |
cb4f4424 | 3064 | IFDEF: USE_OPENSSL |
aebe6888 | 3065 | DEFAULT: none |
10d914f6 CT |
3066 | POSTSCRIPTUM: signUntrusted ssl::certUntrusted |
3067 | POSTSCRIPTUM: signSelf ssl::certSelfSigned | |
3068 | POSTSCRIPTUM: signTrusted all | |
aebe6888 CT |
3069 | TYPE: sslproxy_cert_sign |
3070 | LOC: Config.ssl_client.cert_sign | |
3071 | DOC_START | |
3072 | ||
69742b76 | 3073 | sslproxy_cert_sign <signing algorithm> acl ... |
aebe6888 | 3074 | |
69742b76 | 3075 | The following certificate signing algorithms are supported: |
638402dd | 3076 | |
aebe6888 | 3077 | signTrusted |
69742b76 AR |
3078 | Sign using the configured CA certificate which is usually |
3079 | placed in and trusted by end-user browsers. This is the | |
3080 | default for trusted origin server certificates. | |
638402dd | 3081 | |
aebe6888 | 3082 | signUntrusted |
69742b76 AR |
3083 | Sign to guarantee an X509_V_ERR_CERT_UNTRUSTED browser error. |
3084 | This is the default for untrusted origin server certificates | |
3085 | that are not self-signed (see ssl::certUntrusted). | |
638402dd | 3086 | |
aebe6888 | 3087 | signSelf |
69742b76 | 3088 | Sign using a self-signed certificate with the right CN to |
aebe6888 | 3089 | generate a X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT error in the |
69742b76 AR |
3090 | browser. This is the default for self-signed origin server |
3091 | certificates (see ssl::certSelfSigned). | |
aebe6888 | 3092 | |
cf1c09f6 CT |
3093 | This clause only supports fast acl types. |
3094 | ||
69742b76 AR |
3095 | When sslproxy_cert_sign acl(s) match, Squid uses the corresponding |
3096 | signing algorithm to generate the certificate and ignores all | |
3097 | subsequent sslproxy_cert_sign options (the first match wins). If no | |
3098 | acl(s) match, the default signing algorithm is determined by errors | |
3099 | detected when obtaining and validating the origin server certificate. | |
cf1c09f6 | 3100 | |
4b0d23b7 CT |
3101 | WARNING: SQUID_X509_V_ERR_DOMAIN_MISMATCH and ssl:certDomainMismatch can |
3102 | be used with sslproxy_cert_adapt, but if and only if Squid is bumping a | |
3103 | CONNECT request that carries a domain name. In all other cases (CONNECT | |
3104 | to an IP address or an intercepted SSL connection), Squid cannot detect | |
3105 | the domain mismatch at certificate generation time when | |
3106 | bump-server-first is used. | |
aebe6888 CT |
3107 | DOC_END |
3108 | ||
638402dd | 3109 | NAME: sslproxy_cert_adapt |
cb4f4424 | 3110 | IFDEF: USE_OPENSSL |
fb2178bb CT |
3111 | DEFAULT: none |
3112 | TYPE: sslproxy_cert_adapt | |
3113 | LOC: Config.ssl_client.cert_adapt | |
3114 | DOC_START | |
3115 | ||
3116 | sslproxy_cert_adapt <adaptation algorithm> acl ... | |
3117 | ||
69742b76 | 3118 | The following certificate adaptation algorithms are supported: |
638402dd | 3119 | |
fb2178bb | 3120 | setValidAfter |
69742b76 AR |
3121 | Sets the "Not After" property to the "Not After" property of |
3122 | the CA certificate used to sign generated certificates. | |
638402dd | 3123 | |
fb2178bb | 3124 | setValidBefore |
69742b76 AR |
3125 | Sets the "Not Before" property to the "Not Before" property of |
3126 | the CA certificate used to sign generated certificates. | |
638402dd | 3127 | |
69742b76 AR |
3128 | setCommonName or setCommonName{CN} |
3129 | Sets Subject.CN property to the host name specified as a | |
3130 | CN parameter or, if no explicit CN parameter was specified, | |
3131 | extracted from the CONNECT request. It is a misconfiguration | |
3132 | to use setCommonName without an explicit parameter for | |
3133 | intercepted or tproxied SSL connections. | |
fb2178bb | 3134 | |
cf1c09f6 CT |
3135 | This clause only supports fast acl types. |
3136 | ||
69742b76 AR |
3137 | Squid first groups sslproxy_cert_adapt options by adaptation algorithm. |
3138 | Within a group, when sslproxy_cert_adapt acl(s) match, Squid uses the | |
3139 | corresponding adaptation algorithm to generate the certificate and | |
3140 | ignores all subsequent sslproxy_cert_adapt options in that algorithm's | |
3141 | group (i.e., the first match wins within each algorithm group). If no | |
3142 | acl(s) match, the default mimicking action takes place. | |
cf1c09f6 | 3143 | |
4b0d23b7 CT |
3144 | WARNING: SQUID_X509_V_ERR_DOMAIN_MISMATCH and ssl:certDomainMismatch can |
3145 | be used with sslproxy_cert_adapt, but if and only if Squid is bumping a | |
3146 | CONNECT request that carries a domain name. In all other cases (CONNECT | |
3147 | to an IP address or an intercepted SSL connection), Squid cannot detect | |
3148 | the domain mismatch at certificate generation time when | |
3149 | bump-server-first is used. | |
fb2178bb CT |
3150 | DOC_END |
3151 | ||
41bd17a4 | 3152 | NAME: sslpassword_program |
cb4f4424 | 3153 | IFDEF: USE_OPENSSL |
41bd17a4 | 3154 | DEFAULT: none |
3155 | LOC: Config.Program.ssl_password | |
3156 | TYPE: string | |
5473c134 | 3157 | DOC_START |
41bd17a4 | 3158 | Specify a program used for entering SSL key passphrases |
3159 | when using encrypted SSL certificate keys. If not specified | |
3160 | keys must either be unencrypted, or Squid started with the -N | |
3161 | option to allow it to query interactively for the passphrase. | |
7acb9ddd HN |
3162 | |
3163 | The key file name is given as argument to the program allowing | |
3164 | selection of the right password if you have multiple encrypted | |
3165 | keys. | |
5473c134 | 3166 | DOC_END |
3167 | ||
95d2589c CT |
3168 | COMMENT_START |
3169 | OPTIONS RELATING TO EXTERNAL SSL_CRTD | |
3170 | ----------------------------------------------------------------------------- | |
3171 | COMMENT_END | |
3172 | ||
3173 | NAME: sslcrtd_program | |
3174 | TYPE: eol | |
3175 | IFDEF: USE_SSL_CRTD | |
3176 | DEFAULT: @DEFAULT_SSL_CRTD@ -s @DEFAULT_SSL_DB_DIR@ -M 4MB | |
3177 | LOC: Ssl::TheConfig.ssl_crtd | |
3178 | DOC_START | |
cb0b3d63 AJ |
3179 | Specify the location and options of the executable for certificate |
3180 | generator. | |
95d2589c CT |
3181 | @DEFAULT_SSL_CRTD@ program requires -s and -M parameters |
3182 | For more information use: | |
3183 | @DEFAULT_SSL_CRTD@ -h | |
3184 | DOC_END | |
3185 | ||
3186 | NAME: sslcrtd_children | |
3187 | TYPE: HelperChildConfig | |
3188 | IFDEF: USE_SSL_CRTD | |
3189 | DEFAULT: 32 startup=5 idle=1 | |
3190 | LOC: Ssl::TheConfig.ssl_crtdChildren | |
3191 | DOC_START | |
3192 | The maximum number of processes spawn to service ssl server. | |
3193 | The maximum this may be safely set to is 32. | |
3194 | ||
3195 | The startup= and idle= options allow some measure of skew in your | |
3196 | tuning. | |
3197 | ||
3198 | startup=N | |
3199 | ||
3200 | Sets the minimum number of processes to spawn when Squid | |
3201 | starts or reconfigures. When set to zero the first request will | |
3202 | cause spawning of the first child process to handle it. | |
3203 | ||
3204 | Starting too few children temporary slows Squid under load while it | |
3205 | tries to spawn enough additional processes to cope with traffic. | |
3206 | ||
3207 | idle=N | |
3208 | ||
3209 | Sets a minimum of how many processes Squid is to try and keep available | |
3210 | at all times. When traffic begins to rise above what the existing | |
3211 | processes can handle this many more will be spawned up to the maximum | |
3212 | configured. A minimum setting of 1 is required. | |
6825b101 CT |
3213 | |
3214 | queue-size=N | |
3215 | ||
3216 | Sets the maximum number of queued requests. | |
3217 | If the queued requests exceed queue size for more than 3 minutes | |
3218 | squid aborts its operation. | |
3219 | The default value is set to 2*numberofchildren. | |
95d2589c CT |
3220 | |
3221 | You must have at least one ssl_crtd process. | |
3222 | DOC_END | |
3223 | ||
2cef0ca6 AR |
3224 | NAME: sslcrtvalidator_program |
3225 | TYPE: eol | |
cb4f4424 | 3226 | IFDEF: USE_OPENSSL |
2cef0ca6 AR |
3227 | DEFAULT: none |
3228 | LOC: Ssl::TheConfig.ssl_crt_validator | |
3229 | DOC_START | |
3230 | Specify the location and options of the executable for ssl_crt_validator | |
638402dd AJ |
3231 | process. |
3232 | ||
3233 | Usage: sslcrtvalidator_program [ttl=n] [cache=n] path ... | |
14798e73 CT |
3234 | |
3235 | Options: | |
638402dd | 3236 | ttl=n TTL in seconds for cached results. The default is 60 secs |
14798e73 | 3237 | cache=n limit the result cache size. The default value is 2048 |
2cef0ca6 AR |
3238 | DOC_END |
3239 | ||
3240 | NAME: sslcrtvalidator_children | |
3241 | TYPE: HelperChildConfig | |
cb4f4424 | 3242 | IFDEF: USE_OPENSSL |
413bb969 | 3243 | DEFAULT: 32 startup=5 idle=1 concurrency=1 |
2cef0ca6 AR |
3244 | LOC: Ssl::TheConfig.ssl_crt_validator_Children |
3245 | DOC_START | |
638402dd | 3246 | The maximum number of processes spawn to service SSL server. |
2cef0ca6 AR |
3247 | The maximum this may be safely set to is 32. |
3248 | ||
3249 | The startup= and idle= options allow some measure of skew in your | |
3250 | tuning. | |
3251 | ||
3252 | startup=N | |
3253 | ||
3254 | Sets the minimum number of processes to spawn when Squid | |
3255 | starts or reconfigures. When set to zero the first request will | |
3256 | cause spawning of the first child process to handle it. | |
3257 | ||
3258 | Starting too few children temporary slows Squid under load while it | |
3259 | tries to spawn enough additional processes to cope with traffic. | |
3260 | ||
3261 | idle=N | |
3262 | ||
3263 | Sets a minimum of how many processes Squid is to try and keep available | |
3264 | at all times. When traffic begins to rise above what the existing | |
3265 | processes can handle this many more will be spawned up to the maximum | |
3266 | configured. A minimum setting of 1 is required. | |
4a77bb4e CT |
3267 | |
3268 | concurrency= | |
3269 | ||
3270 | The number of requests each certificate validator helper can handle in | |
dffc462a CT |
3271 | parallel. A value of 0 indicates the certficate validator does not |
3272 | support concurrency. Defaults to 1. | |
4a77bb4e CT |
3273 | |
3274 | When this directive is set to a value >= 1 then the protocol | |
3275 | used to communicate with the helper is modified to include | |
3276 | a request ID in front of the request/response. The request | |
3277 | ID from the request must be echoed back with the response | |
3278 | to that request. | |
6825b101 CT |
3279 | |
3280 | queue-size=N | |
3281 | ||
3282 | Sets the maximum number of queued requests. | |
3283 | If the queued requests exceed queue size for more than 3 minutes | |
3284 | squid aborts its operation. | |
3285 | The default value is set to 2*numberofchildren. | |
2cef0ca6 AR |
3286 | |
3287 | You must have at least one ssl_crt_validator process. | |
3288 | DOC_END | |
3289 | ||
cccac0a2 | 3290 | COMMENT_START |
41bd17a4 | 3291 | OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM |
cccac0a2 | 3292 | ----------------------------------------------------------------------------- |
3293 | COMMENT_END | |
3294 | ||
41bd17a4 | 3295 | NAME: cache_peer |
3296 | TYPE: peer | |
3297 | DEFAULT: none | |
3298 | LOC: Config.peers | |
cccac0a2 | 3299 | DOC_START |
41bd17a4 | 3300 | To specify other caches in a hierarchy, use the format: |
2b94f655 | 3301 | |
41bd17a4 | 3302 | cache_peer hostname type http-port icp-port [options] |
2b94f655 | 3303 | |
41bd17a4 | 3304 | For example, |
2b94f655 | 3305 | |
41bd17a4 | 3306 | # proxy icp |
3307 | # hostname type port port options | |
3308 | # -------------------- -------- ----- ----- ----------- | |
2b94f655 | 3309 | cache_peer parent.foo.net parent 3128 3130 default |
41bd17a4 | 3310 | cache_peer sib1.foo.net sibling 3128 3130 proxy-only |
3311 | cache_peer sib2.foo.net sibling 3128 3130 proxy-only | |
2e9993e1 | 3312 | cache_peer example.com parent 80 0 default |
2b94f655 AJ |
3313 | cache_peer cdn.example.com sibling 3128 0 |
3314 | ||
3315 | type: either 'parent', 'sibling', or 'multicast'. | |
3316 | ||
3317 | proxy-port: The port number where the peer accept HTTP requests. | |
3318 | For other Squid proxies this is usually 3128 | |
3319 | For web servers this is usually 80 | |
3320 | ||
3321 | icp-port: Used for querying neighbor caches about objects. | |
3322 | Set to 0 if the peer does not support ICP or HTCP. | |
3323 | See ICP and HTCP options below for additional details. | |
3324 | ||
3325 | ||
3326 | ==== ICP OPTIONS ==== | |
3327 | ||
3328 | You MUST also set icp_port and icp_access explicitly when using these options. | |
3329 | The defaults will prevent peer traffic using ICP. | |
3330 | ||
3331 | ||
3332 | no-query Disable ICP queries to this neighbor. | |
3333 | ||
3334 | multicast-responder | |
3335 | Indicates the named peer is a member of a multicast group. | |
3336 | ICP queries will not be sent directly to the peer, but ICP | |
3337 | replies will be accepted from it. | |
3338 | ||
3339 | closest-only Indicates that, for ICP_OP_MISS replies, we'll only forward | |
3340 | CLOSEST_PARENT_MISSes and never FIRST_PARENT_MISSes. | |
3341 | ||
3342 | background-ping | |
3343 | To only send ICP queries to this neighbor infrequently. | |
3344 | This is used to keep the neighbor round trip time updated | |
3345 | and is usually used in conjunction with weighted-round-robin. | |
3346 | ||
3347 | ||
3348 | ==== HTCP OPTIONS ==== | |
3349 | ||
3350 | You MUST also set htcp_port and htcp_access explicitly when using these options. | |
3351 | The defaults will prevent peer traffic using HTCP. | |
3352 | ||
3353 | ||
3354 | htcp Send HTCP, instead of ICP, queries to the neighbor. | |
3355 | You probably also want to set the "icp-port" to 4827 | |
18191440 AJ |
3356 | instead of 3130. This directive accepts a comma separated |
3357 | list of options described below. | |
2b94f655 | 3358 | |
18191440 | 3359 | htcp=oldsquid Send HTCP to old Squid versions (2.5 or earlier). |
2b94f655 | 3360 | |
18191440 | 3361 | htcp=no-clr Send HTCP to the neighbor but without |
2b94f655 | 3362 | sending any CLR requests. This cannot be used with |
18191440 | 3363 | only-clr. |
2b94f655 | 3364 | |
18191440 AJ |
3365 | htcp=only-clr Send HTCP to the neighbor but ONLY CLR requests. |
3366 | This cannot be used with no-clr. | |
2b94f655 | 3367 | |
18191440 | 3368 | htcp=no-purge-clr |
2b94f655 AJ |
3369 | Send HTCP to the neighbor including CLRs but only when |
3370 | they do not result from PURGE requests. | |
3371 | ||
18191440 | 3372 | htcp=forward-clr |
2b94f655 AJ |
3373 | Forward any HTCP CLR requests this proxy receives to the peer. |
3374 | ||
3375 | ||
3376 | ==== PEER SELECTION METHODS ==== | |
3377 | ||
3378 | The default peer selection method is ICP, with the first responding peer | |
3379 | being used as source. These options can be used for better load balancing. | |
3380 | ||
3381 | ||
3382 | default This is a parent cache which can be used as a "last-resort" | |
3383 | if a peer cannot be located by any of the peer-selection methods. | |
3384 | If specified more than once, only the first is used. | |
3385 | ||
3386 | round-robin Load-Balance parents which should be used in a round-robin | |
3387 | fashion in the absence of any ICP queries. | |
3388 | weight=N can be used to add bias. | |
3389 | ||
3390 | weighted-round-robin | |
3391 | Load-Balance parents which should be used in a round-robin | |
3392 | fashion with the frequency of each parent being based on the | |
3393 | round trip time. Closer parents are used more often. | |
3394 | Usually used for background-ping parents. | |
3395 | weight=N can be used to add bias. | |
3396 | ||
3397 | carp Load-Balance parents which should be used as a CARP array. | |
3398 | The requests will be distributed among the parents based on the | |
3399 | CARP load balancing hash function based on their weight. | |
3400 | ||
3401 | userhash Load-balance parents based on the client proxy_auth or ident username. | |
3402 | ||
3403 | sourcehash Load-balance parents based on the client source IP. | |
8a368316 AJ |
3404 | |
3405 | multicast-siblings | |
3406 | To be used only for cache peers of type "multicast". | |
3407 | ALL members of this multicast group have "sibling" | |
2e9993e1 | 3408 | relationship with it, not "parent". This is to a multicast |
8a368316 AJ |
3409 | group when the requested object would be fetched only from |
3410 | a "parent" cache, anyway. It's useful, e.g., when | |
3411 | configuring a pool of redundant Squid proxies, being | |
3412 | members of the same multicast group. | |
2b94f655 AJ |
3413 | |
3414 | ||
3415 | ==== PEER SELECTION OPTIONS ==== | |
3416 | ||
3417 | weight=N use to affect the selection of a peer during any weighted | |
3418 | peer-selection mechanisms. | |
3419 | The weight must be an integer; default is 1, | |
3420 | larger weights are favored more. | |
3421 | This option does not affect parent selection if a peering | |
3422 | protocol is not in use. | |
3423 | ||
3424 | basetime=N Specify a base amount to be subtracted from round trip | |
3425 | times of parents. | |
3426 | It is subtracted before division by weight in calculating | |
3427 | which parent to fectch from. If the rtt is less than the | |
3428 | base time the rtt is set to a minimal value. | |
3429 | ||
3c72389f AJ |
3430 | ttl=N Specify a TTL to use when sending multicast ICP queries |
3431 | to this address. | |
2b94f655 AJ |
3432 | Only useful when sending to a multicast group. |
3433 | Because we don't accept ICP replies from random | |
3434 | hosts, you must configure other group members as | |
3435 | peers with the 'multicast-responder' option. | |
3436 | ||
3437 | no-delay To prevent access to this neighbor from influencing the | |
3438 | delay pools. | |
3439 | ||
3440 | digest-url=URL Tell Squid to fetch the cache digest (if digests are | |
3441 | enabled) for this host from the specified URL rather | |
3442 | than the Squid default location. | |
3443 | ||
3444 | ||
de03b596 FC |
3445 | ==== CARP OPTIONS ==== |
3446 | ||
3447 | carp-key=key-specification | |
3448 | use a different key than the full URL to hash against the peer. | |
3449 | the key-specification is a comma-separated list of the keywords | |
3450 | scheme, host, port, path, params | |
3451 | Order is not important. | |
3452 | ||
2b94f655 AJ |
3453 | ==== ACCELERATOR / REVERSE-PROXY OPTIONS ==== |
3454 | ||
3455 | originserver Causes this parent to be contacted as an origin server. | |
3456 | Meant to be used in accelerator setups when the peer | |
3457 | is a web server. | |
3458 | ||
3459 | forceddomain=name | |
3460 | Set the Host header of requests forwarded to this peer. | |
3461 | Useful in accelerator setups where the server (peer) | |
3462 | expects a certain domain name but clients may request | |
3463 | others. ie example.com or www.example.com | |
3464 | ||
3465 | no-digest Disable request of cache digests. | |
3466 | ||
3467 | no-netdb-exchange | |
3468 | Disables requesting ICMP RTT database (NetDB). | |
3469 | ||
3470 | ||
3471 | ==== AUTHENTICATION OPTIONS ==== | |
3472 | ||
3473 | login=user:password | |
3474 | If this is a personal/workgroup proxy and your parent | |
3475 | requires proxy authentication. | |
3476 | ||
3477 | Note: The string can include URL escapes (i.e. %20 for | |
3478 | spaces). This also means % must be written as %%. | |
3479 | ||
11e4c5e5 AJ |
3480 | login=PASSTHRU |
3481 | Send login details received from client to this peer. | |
3482 | Both Proxy- and WWW-Authorization headers are passed | |
3483 | without alteration to the peer. | |
3484 | Authentication is not required by Squid for this to work. | |
3485 | ||
3486 | Note: This will pass any form of authentication but | |
3487 | only Basic auth will work through a proxy unless the | |
3488 | connection-auth options are also used. | |
ee0b94f4 | 3489 | |
2b94f655 AJ |
3490 | login=PASS Send login details received from client to this peer. |
3491 | Authentication is not required by this option. | |
11e4c5e5 | 3492 | |
2b94f655 AJ |
3493 | If there are no client-provided authentication headers |
3494 | to pass on, but username and password are available | |
ee0b94f4 HN |
3495 | from an external ACL user= and password= result tags |
3496 | they may be sent instead. | |
2b94f655 AJ |
3497 | |
3498 | Note: To combine this with proxy_auth both proxies must | |
3499 | share the same user database as HTTP only allows for | |
3500 | a single login (one for proxy, one for origin server). | |
3501 | Also be warned this will expose your users proxy | |
3502 | password to the peer. USE WITH CAUTION | |
3503 | ||
3504 | login=*:password | |
3505 | Send the username to the upstream cache, but with a | |
3506 | fixed password. This is meant to be used when the peer | |
3507 | is in another administrative domain, but it is still | |
3508 | needed to identify each user. | |
3509 | The star can optionally be followed by some extra | |
3510 | information which is added to the username. This can | |
3511 | be used to identify this proxy to the peer, similar to | |
3512 | the login=username:password option above. | |
3513 | ||
9ca29d23 AJ |
3514 | login=NEGOTIATE |
3515 | If this is a personal/workgroup proxy and your parent | |
3516 | requires a secure proxy authentication. | |
3517 | The first principal from the default keytab or defined by | |
3518 | the environment variable KRB5_KTNAME will be used. | |
3519 | ||
63f03f79 PL |
3520 | WARNING: The connection may transmit requests from multiple |
3521 | clients. Negotiate often assumes end-to-end authentication | |
3522 | and a single-client. Which is not strictly true here. | |
3523 | ||
9ca29d23 AJ |
3524 | login=NEGOTIATE:principal_name |
3525 | If this is a personal/workgroup proxy and your parent | |
3526 | requires a secure proxy authentication. | |
3527 | The principal principal_name from the default keytab or | |
3528 | defined by the environment variable KRB5_KTNAME will be | |
3529 | used. | |
3530 | ||
63f03f79 PL |
3531 | WARNING: The connection may transmit requests from multiple |
3532 | clients. Negotiate often assumes end-to-end authentication | |
3533 | and a single-client. Which is not strictly true here. | |
3534 | ||
2b94f655 AJ |
3535 | connection-auth=on|off |
3536 | Tell Squid that this peer does or not support Microsoft | |
3537 | connection oriented authentication, and any such | |
3538 | challenges received from there should be ignored. | |
3539 | Default is auto to automatically determine the status | |
3540 | of the peer. | |
3541 | ||
9825b398 AJ |
3542 | auth-no-keytab |
3543 | Do not use a keytab to authenticate to a peer when | |
3544 | login=NEGOTIATE is specified. Let the GSSAPI | |
3545 | implementation determine which already existing | |
3546 | credentials cache to use instead. | |
3547 | ||
2b94f655 AJ |
3548 | |
3549 | ==== SSL / HTTPS / TLS OPTIONS ==== | |
3550 | ||
0ff7e52d | 3551 | tls Encrypt connections to this peer with TLS. |
2b94f655 AJ |
3552 | |
3553 | sslcert=/path/to/ssl/certificate | |
3554 | A client SSL certificate to use when connecting to | |
3555 | this peer. | |
3556 | ||
3557 | sslkey=/path/to/ssl/key | |
3558 | The private SSL key corresponding to sslcert above. | |
3559 | If 'sslkey' is not specified 'sslcert' is assumed to | |
3560 | reference a combined file containing both the | |
3561 | certificate and the key. | |
3562 | ||
2b94f655 AJ |
3563 | sslcipher=... The list of valid SSL ciphers to use when connecting |
3564 | to this peer. | |
1cc44095 AJ |
3565 | |
3566 | tls-min-version=1.N | |
3567 | The minimum TLS protocol version to permit. To control | |
3f5b28fe | 3568 | SSLv3 use the tls-options= parameter. |
1cc44095 AJ |
3569 | Supported Values: 1.0 (default), 1.1, 1.2 |
3570 | ||
3f5b28fe | 3571 | tls-options=... Specify various TLS implementation options. |
943c5f16 | 3572 | |
3f5b28fe | 3573 | OpenSSL options most important are: |
1f1f29e8 | 3574 | |
3f5b28fe | 3575 | NO_SSLv3 Disallow the use of SSLv3 |
1f1f29e8 | 3576 | |
943c5f16 HN |
3577 | SINGLE_DH_USE |
3578 | Always create a new key when using | |
3579 | temporary/ephemeral DH key exchanges | |
1f1f29e8 | 3580 | |
ce0adf1a | 3581 | NO_TICKET |
1f1f29e8 AJ |
3582 | Disable use of RFC5077 session tickets. |
3583 | Some servers may have problems | |
3584 | understanding the TLS extension due | |
3585 | to ambiguous specification in RFC4507. | |
3586 | ||
943c5f16 HN |
3587 | ALL Enable various bug workarounds |
3588 | suggested as "harmless" by OpenSSL | |
3589 | Be warned that this reduces SSL/TLS | |
3590 | strength to some attacks. | |
3591 | ||
3592 | See the OpenSSL SSL_CTX_set_options documentation for a | |
3593 | more complete list. | |
3f5b28fe AJ |
3594 | |
3595 | GnuTLS options most important are: | |
3596 | ||
3597 | %NO_TICKETS | |
3598 | Disable use of RFC5077 session tickets. | |
3599 | Some servers may have problems | |
3600 | understanding the TLS extension due | |
3601 | to ambiguous specification in RFC4507. | |
3602 | ||
3603 | See the GnuTLS Priority Strings documentation | |
3604 | for a more complete list. | |
3605 | http://www.gnutls.org/manual/gnutls.html#Priority-Strings | |
3606 | ||
86a84cc0 AJ |
3607 | tls-cafile= PEM file containing CA certificates to use when verifying |
3608 | the peer certificate. May be repeated to load multiple files. | |
2b94f655 AJ |
3609 | |
3610 | sslcapath=... A directory containing additional CA certificates to | |
3611 | use when verifying the peer certificate. | |
86a84cc0 | 3612 | Requires OpenSSL or LibreSSL. |
2b94f655 AJ |
3613 | |
3614 | sslcrlfile=... A certificate revocation list file to use when | |
3615 | verifying the peer certificate. | |
3616 | ||
3617 | sslflags=... Specify various flags modifying the SSL implementation: | |
3618 | ||
41bd17a4 | 3619 | DONT_VERIFY_PEER |
3620 | Accept certificates even if they fail to | |
3621 | verify. | |
1f1f29e8 | 3622 | |
41bd17a4 | 3623 | DONT_VERIFY_DOMAIN |
3624 | Don't verify the peer certificate | |
3625 | matches the server name | |
2b94f655 AJ |
3626 | |
3627 | ssldomain= The peer name as advertised in it's certificate. | |
3628 | Used for verifying the correctness of the received peer | |
3629 | certificate. If not specified the peer hostname will be | |
3630 | used. | |
3631 | ||
bad9c5e4 | 3632 | front-end-https[=off|on|auto] |
2b94f655 AJ |
3633 | Enable the "Front-End-Https: On" header needed when |
3634 | using Squid as a SSL frontend in front of Microsoft OWA. | |
3635 | See MS KB document Q307347 for details on this header. | |
3636 | If set to auto the header will only be added if the | |
3637 | request is forwarded as a https:// URL. | |
435c72b0 AJ |
3638 | |
3639 | tls-default-ca[=off] | |
3640 | Whether to use the system Trusted CAs. Default is ON. | |
2b94f655 | 3641 | |
b05d749d AJ |
3642 | tls-no-npn Do not use the TLS NPN extension to advertise HTTP/1.1. |
3643 | ||
2b94f655 AJ |
3644 | ==== GENERAL OPTIONS ==== |
3645 | ||
3646 | connect-timeout=N | |
3647 | A peer-specific connect timeout. | |
3648 | Also see the peer_connect_timeout directive. | |
3649 | ||
3650 | connect-fail-limit=N | |
3651 | How many times connecting to a peer must fail before | |
e8dca475 CT |
3652 | it is marked as down. Standby connection failures |
3653 | count towards this limit. Default is 10. | |
2b94f655 AJ |
3654 | |
3655 | allow-miss Disable Squid's use of only-if-cached when forwarding | |
3656 | requests to siblings. This is primarily useful when | |
a5bb0c26 AR |
3657 | icp_hit_stale is used by the sibling. Excessive use |
3658 | of this option may result in forwarding loops. One way | |
3659 | to prevent peering loops when using this option, is to | |
3660 | deny cache peer usage on requests from a peer: | |
3661 | acl fromPeer ... | |
3662 | cache_peer_access peerName deny fromPeer | |
2b94f655 | 3663 | |
e8dca475 CT |
3664 | max-conn=N Limit the number of concurrent connections the Squid |
3665 | may open to this peer, including already opened idle | |
3666 | and standby connections. There is no peer-specific | |
3667 | connection limit by default. | |
3668 | ||
3669 | A peer exceeding the limit is not used for new | |
3670 | requests unless a standby connection is available. | |
3671 | ||
3672 | max-conn currently works poorly with idle persistent | |
3673 | connections: When a peer reaches its max-conn limit, | |
3674 | and there are idle persistent connections to the peer, | |
3675 | the peer may not be selected because the limiting code | |
3676 | does not know whether Squid can reuse those idle | |
3677 | connections. | |
3678 | ||
3679 | standby=N Maintain a pool of N "hot standby" connections to an | |
3680 | UP peer, available for requests when no idle | |
3681 | persistent connection is available (or safe) to use. | |
3682 | By default and with zero N, no such pool is maintained. | |
3683 | N must not exceed the max-conn limit (if any). | |
3684 | ||
3685 | At start or after reconfiguration, Squid opens new TCP | |
3686 | standby connections until there are N connections | |
3687 | available and then replenishes the standby pool as | |
3688 | opened connections are used up for requests. A used | |
3689 | connection never goes back to the standby pool, but | |
3690 | may go to the regular idle persistent connection pool | |
3691 | shared by all peers and origin servers. | |
3692 | ||
3693 | Squid never opens multiple new standby connections | |
3694 | concurrently. This one-at-a-time approach minimizes | |
3695 | flooding-like effect on peers. Furthermore, just a few | |
3696 | standby connections should be sufficient in most cases | |
3697 | to supply most new requests with a ready-to-use | |
3698 | connection. | |
3699 | ||
3700 | Standby connections obey server_idle_pconn_timeout. | |
3701 | For the feature to work as intended, the peer must be | |
3702 | configured to accept and keep them open longer than | |
3703 | the idle timeout at the connecting Squid, to minimize | |
3704 | race conditions typical to idle used persistent | |
3705 | connections. Default request_timeout and | |
3706 | server_idle_pconn_timeout values ensure such a | |
3707 | configuration. | |
2b94f655 AJ |
3708 | |
3709 | name=xxx Unique name for the peer. | |
3710 | Required if you have multiple peers on the same host | |
3711 | but different ports. | |
3712 | This name can be used in cache_peer_access and similar | |
a5bb0c26 | 3713 | directives to identify the peer. |
2b94f655 AJ |
3714 | Can be used by outgoing access controls through the |
3715 | peername ACL type. | |
3716 | ||
b0758e04 AJ |
3717 | no-tproxy Do not use the client-spoof TPROXY support when forwarding |
3718 | requests to this peer. Use normal address selection instead. | |
0d901ef4 | 3719 | This overrides the spoof_client_ip ACL. |
b0758e04 | 3720 | |
2b94f655 AJ |
3721 | proxy-only objects fetched from the peer will not be stored locally. |
3722 | ||
41bd17a4 | 3723 | DOC_END |
cccac0a2 | 3724 | |
41bd17a4 | 3725 | NAME: cache_peer_access |
3726 | TYPE: peer_access | |
3727 | DEFAULT: none | |
a5bb0c26 | 3728 | DEFAULT_DOC: No peer usage restrictions. |
41bd17a4 | 3729 | LOC: none |
3730 | DOC_START | |
a5bb0c26 | 3731 | Restricts usage of cache_peer proxies. |
cccac0a2 | 3732 | |
638402dd | 3733 | Usage: |
a5bb0c26 AR |
3734 | cache_peer_access peer-name allow|deny [!]aclname ... |
3735 | ||
3736 | For the required peer-name parameter, use either the value of the | |
3737 | cache_peer name=value parameter or, if name=value is missing, the | |
3738 | cache_peer hostname parameter. | |
3739 | ||
3740 | This directive narrows down the selection of peering candidates, but | |
3741 | does not determine the order in which the selected candidates are | |
3742 | contacted. That order is determined by the peer selection algorithms | |
3743 | (see PEER SELECTION sections in the cache_peer documentation). | |
3744 | ||
3745 | If a deny rule matches, the corresponding peer will not be contacted | |
3746 | for the current transaction -- Squid will not send ICP queries and | |
3747 | will not forward HTTP requests to that peer. An allow match leaves | |
3748 | the corresponding peer in the selection. The first match for a given | |
3749 | peer wins for that peer. | |
3750 | ||
3751 | The relative order of cache_peer_access directives for the same peer | |
3752 | matters. The relative order of any two cache_peer_access directives | |
3753 | for different peers does not matter. To ease interpretation, it is a | |
3754 | good idea to group cache_peer_access directives for the same peer | |
3755 | together. | |
3756 | ||
3757 | A single cache_peer_access directive may be evaluated multiple times | |
3758 | for a given transaction because individual peer selection algorithms | |
3759 | may check it independently from each other. These redundant checks | |
3760 | may be optimized away in future Squid versions. | |
3761 | ||
3762 | This clause only supports fast acl types. | |
3763 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
dd9b1776 | 3764 | |
41bd17a4 | 3765 | DOC_END |
dd9b1776 | 3766 | |
41bd17a4 | 3767 | NAME: neighbor_type_domain |
3768 | TYPE: hostdomaintype | |
3769 | DEFAULT: none | |
638402dd | 3770 | DEFAULT_DOC: The peer type from cache_peer directive is used for all requests to that peer. |
41bd17a4 | 3771 | LOC: none |
3772 | DOC_START | |
638402dd AJ |
3773 | Modify the cache_peer neighbor type when passing requests |
3774 | about specific domains to the peer. | |
cccac0a2 | 3775 | |
638402dd AJ |
3776 | Usage: |
3777 | neighbor_type_domain neighbor parent|sibling domain domain ... | |
6bf4f823 | 3778 | |
638402dd AJ |
3779 | For example: |
3780 | cache_peer foo.example.com parent 3128 3130 | |
3781 | neighbor_type_domain foo.example.com sibling .au .de | |
6bf4f823 | 3782 | |
638402dd AJ |
3783 | The above configuration treats all requests to foo.example.com as a |
3784 | parent proxy unless the request is for a .au or .de ccTLD domain name. | |
41bd17a4 | 3785 | DOC_END |
6bf4f823 | 3786 | |
41bd17a4 | 3787 | NAME: dead_peer_timeout |
3788 | COMMENT: (seconds) | |
3789 | DEFAULT: 10 seconds | |
3790 | TYPE: time_t | |
3791 | LOC: Config.Timeout.deadPeer | |
3792 | DOC_START | |
3793 | This controls how long Squid waits to declare a peer cache | |
3794 | as "dead." If there are no ICP replies received in this | |
3795 | amount of time, Squid will declare the peer dead and not | |
3796 | expect to receive any further ICP replies. However, it | |
3797 | continues to send ICP queries, and will mark the peer as | |
3798 | alive upon receipt of the first subsequent ICP reply. | |
699acd19 | 3799 | |
41bd17a4 | 3800 | This timeout also affects when Squid expects to receive ICP |
3801 | replies from peers. If more than 'dead_peer' seconds have | |
3802 | passed since the last ICP reply was received, Squid will not | |
3803 | expect to receive an ICP reply on the next query. Thus, if | |
3804 | your time between requests is greater than this timeout, you | |
3805 | will see a lot of requests sent DIRECT to origin servers | |
3806 | instead of to your parents. | |
3807 | DOC_END | |
cccac0a2 | 3808 | |
437823b4 | 3809 | NAME: forward_max_tries |
6c367206 | 3810 | DEFAULT: 25 |
437823b4 AJ |
3811 | TYPE: int |
3812 | LOC: Config.forward_max_tries | |
3813 | DOC_START | |
3814 | Controls how many different forward paths Squid will try | |
3815 | before giving up. See also forward_timeout. | |
31ef19cd AJ |
3816 | |
3817 | NOTE: connect_retries (default: none) can make each of these | |
3818 | possible forwarding paths be tried multiple times. | |
437823b4 AJ |
3819 | DOC_END |
3820 | ||
41bd17a4 | 3821 | COMMENT_START |
3822 | MEMORY CACHE OPTIONS | |
3823 | ----------------------------------------------------------------------------- | |
3824 | COMMENT_END | |
3825 | ||
3826 | NAME: cache_mem | |
3827 | COMMENT: (bytes) | |
3828 | TYPE: b_size_t | |
df2eec10 | 3829 | DEFAULT: 256 MB |
41bd17a4 | 3830 | LOC: Config.memMaxSize |
6b698a21 | 3831 | DOC_START |
41bd17a4 | 3832 | NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS SIZE. |
3833 | IT ONLY PLACES A LIMIT ON HOW MUCH ADDITIONAL MEMORY SQUID WILL | |
3834 | USE AS A MEMORY CACHE OF OBJECTS. SQUID USES MEMORY FOR OTHER | |
3835 | THINGS AS WELL. SEE THE SQUID FAQ SECTION 8 FOR DETAILS. | |
3836 | ||
3837 | 'cache_mem' specifies the ideal amount of memory to be used | |
3838 | for: | |
3839 | * In-Transit objects | |
3840 | * Hot Objects | |
3841 | * Negative-Cached objects | |
3842 | ||
3843 | Data for these objects are stored in 4 KB blocks. This | |
3844 | parameter specifies the ideal upper limit on the total size of | |
3845 | 4 KB blocks allocated. In-Transit objects take the highest | |
3846 | priority. | |
3847 | ||
3848 | In-transit objects have priority over the others. When | |
3849 | additional space is needed for incoming data, negative-cached | |
3850 | and hot objects will be released. In other words, the | |
3851 | negative-cached and hot objects will fill up any unused space | |
3852 | not needed for in-transit objects. | |
3853 | ||
3854 | If circumstances require, this limit will be exceeded. | |
3855 | Specifically, if your incoming request rate requires more than | |
3856 | 'cache_mem' of memory to hold in-transit objects, Squid will | |
3857 | exceed this limit to satisfy the new requests. When the load | |
3858 | decreases, blocks will be freed until the high-water mark is | |
3859 | reached. Thereafter, blocks will be used to store hot | |
3860 | objects. | |
29f35ca5 AR |
3861 | |
3862 | If shared memory caching is enabled, Squid does not use the shared | |
3863 | cache space for in-transit objects, but they still consume as much | |
3864 | local memory as they need. For more details about the shared memory | |
3865 | cache, see memory_cache_shared. | |
6b698a21 | 3866 | DOC_END |
0976f8db | 3867 | |
41bd17a4 | 3868 | NAME: maximum_object_size_in_memory |
3869 | COMMENT: (bytes) | |
3870 | TYPE: b_size_t | |
df2eec10 | 3871 | DEFAULT: 512 KB |
41bd17a4 | 3872 | LOC: Config.Store.maxInMemObjSize |
6b698a21 | 3873 | DOC_START |
41bd17a4 | 3874 | Objects greater than this size will not be attempted to kept in |
3875 | the memory cache. This should be set high enough to keep objects | |
3876 | accessed frequently in memory to improve performance whilst low | |
3877 | enough to keep larger objects from hoarding cache_mem. | |
6b698a21 | 3878 | DOC_END |
0976f8db | 3879 | |
57af1e3f AR |
3880 | NAME: memory_cache_shared |
3881 | COMMENT: on|off | |
3882 | TYPE: YesNoNone | |
3883 | LOC: Config.memShared | |
3884 | DEFAULT: none | |
70f856bc | 3885 | DEFAULT_DOC: "on" where supported if doing memory caching with multiple SMP workers. |
57af1e3f AR |
3886 | DOC_START |
3887 | Controls whether the memory cache is shared among SMP workers. | |
3888 | ||
70f856bc AR |
3889 | The shared memory cache is meant to occupy cache_mem bytes and replace |
3890 | the non-shared memory cache, although some entities may still be | |
3891 | cached locally by workers for now (e.g., internal and in-transit | |
3892 | objects may be served from a local memory cache even if shared memory | |
3893 | caching is enabled). | |
3894 | ||
65b81b27 | 3895 | By default, the memory cache is shared if and only if all of the |
70f856bc AR |
3896 | following conditions are satisfied: Squid runs in SMP mode with |
3897 | multiple workers, cache_mem is positive, and Squid environment | |
3898 | supports required IPC primitives (e.g., POSIX shared memory segments | |
3899 | and GCC-style atomic operations). | |
3900 | ||
3901 | To avoid blocking locks, shared memory uses opportunistic algorithms | |
3902 | that do not guarantee that every cachable entity that could have been | |
3903 | shared among SMP workers will actually be shared. | |
57af1e3f AR |
3904 | DOC_END |
3905 | ||
ea21d497 HN |
3906 | NAME: memory_cache_mode |
3907 | TYPE: memcachemode | |
3908 | LOC: Config | |
3909 | DEFAULT: always | |
638402dd | 3910 | DEFAULT_DOC: Keep the most recently fetched objects in memory |
ff4b33f4 | 3911 | DOC_START |
ea21d497 | 3912 | Controls which objects to keep in the memory cache (cache_mem) |
ff4b33f4 | 3913 | |
ea21d497 HN |
3914 | always Keep most recently fetched objects in memory (default) |
3915 | ||
3916 | disk Only disk cache hits are kept in memory, which means | |
3917 | an object must first be cached on disk and then hit | |
3918 | a second time before cached in memory. | |
3919 | ||
3920 | network Only objects fetched from network is kept in memory | |
ff4b33f4 HN |
3921 | DOC_END |
3922 | ||
41bd17a4 | 3923 | NAME: memory_replacement_policy |
3924 | TYPE: removalpolicy | |
3925 | LOC: Config.memPolicy | |
3926 | DEFAULT: lru | |
6b698a21 | 3927 | DOC_START |
41bd17a4 | 3928 | The memory replacement policy parameter determines which |
3929 | objects are purged from memory when memory space is needed. | |
7f7db318 | 3930 | |
638402dd | 3931 | See cache_replacement_policy for details on algorithms. |
41bd17a4 | 3932 | DOC_END |
6b698a21 | 3933 | |
41bd17a4 | 3934 | COMMENT_START |
3935 | DISK CACHE OPTIONS | |
3936 | ----------------------------------------------------------------------------- | |
3937 | COMMENT_END | |
6b698a21 | 3938 | |
41bd17a4 | 3939 | NAME: cache_replacement_policy |
3940 | TYPE: removalpolicy | |
3941 | LOC: Config.replPolicy | |
3942 | DEFAULT: lru | |
3943 | DOC_START | |
3944 | The cache replacement policy parameter determines which | |
3945 | objects are evicted (replaced) when disk space is needed. | |
6b698a21 | 3946 | |
41bd17a4 | 3947 | lru : Squid's original list based LRU policy |
3948 | heap GDSF : Greedy-Dual Size Frequency | |
3949 | heap LFUDA: Least Frequently Used with Dynamic Aging | |
3950 | heap LRU : LRU policy implemented using a heap | |
6b698a21 | 3951 | |
638402dd | 3952 | Applies to any cache_dir lines listed below this directive. |
7f7db318 | 3953 | |
41bd17a4 | 3954 | The LRU policies keeps recently referenced objects. |
0976f8db | 3955 | |
41bd17a4 | 3956 | The heap GDSF policy optimizes object hit rate by keeping smaller |
3957 | popular objects in cache so it has a better chance of getting a | |
3958 | hit. It achieves a lower byte hit rate than LFUDA though since | |
3959 | it evicts larger (possibly popular) objects. | |
0976f8db | 3960 | |
41bd17a4 | 3961 | The heap LFUDA policy keeps popular objects in cache regardless of |
3962 | their size and thus optimizes byte hit rate at the expense of | |
3963 | hit rate since one large, popular object will prevent many | |
3964 | smaller, slightly less popular objects from being cached. | |
0976f8db | 3965 | |
41bd17a4 | 3966 | Both policies utilize a dynamic aging mechanism that prevents |
3967 | cache pollution that can otherwise occur with frequency-based | |
3968 | replacement policies. | |
7d90757b | 3969 | |
41bd17a4 | 3970 | NOTE: if using the LFUDA replacement policy you should increase |
b51ec8c8 | 3971 | the value of maximum_object_size above its default of 4 MB to |
41bd17a4 | 3972 | to maximize the potential byte hit rate improvement of LFUDA. |
dc1af3cf | 3973 | |
41bd17a4 | 3974 | For more information about the GDSF and LFUDA cache replacement |
3975 | policies see http://www.hpl.hp.com/techreports/1999/HPL-1999-69.html | |
3976 | and http://fog.hpl.external.hp.com/techreports/98/HPL-98-173.html. | |
6b698a21 | 3977 | DOC_END |
0976f8db | 3978 | |
a345387f AJ |
3979 | NAME: minimum_object_size |
3980 | COMMENT: (bytes) | |
3981 | TYPE: b_int64_t | |
3982 | DEFAULT: 0 KB | |
3983 | DEFAULT_DOC: no limit | |
3984 | LOC: Config.Store.minObjectSize | |
3985 | DOC_START | |
3986 | Objects smaller than this size will NOT be saved on disk. The | |
3987 | value is specified in bytes, and the default is 0 KB, which | |
3988 | means all responses can be stored. | |
3989 | DOC_END | |
3990 | ||
3991 | NAME: maximum_object_size | |
3992 | COMMENT: (bytes) | |
3993 | TYPE: b_int64_t | |
3994 | DEFAULT: 4 MB | |
3995 | LOC: Config.Store.maxObjectSize | |
3996 | DOC_START | |
499f852c | 3997 | Set the default value for max-size parameter on any cache_dir. |
a345387f AJ |
3998 | The value is specified in bytes, and the default is 4 MB. |
3999 | ||
4000 | If you wish to get a high BYTES hit ratio, you should probably | |
4001 | increase this (one 32 MB object hit counts for 3200 10KB | |
4002 | hits). | |
4003 | ||
4004 | If you wish to increase hit ratio more than you want to | |
4005 | save bandwidth you should leave this low. | |
4006 | ||
4007 | NOTE: if using the LFUDA replacement policy you should increase | |
4008 | this value to maximize the byte hit rate improvement of LFUDA! | |
4009 | See cache_replacement_policy for a discussion of this policy. | |
4010 | DOC_END | |
4011 | ||
41bd17a4 | 4012 | NAME: cache_dir |
4013 | TYPE: cachedir | |
4014 | DEFAULT: none | |
638402dd | 4015 | DEFAULT_DOC: No disk cache. Store cache ojects only in memory. |
41bd17a4 | 4016 | LOC: Config.cacheSwap |
6b698a21 | 4017 | DOC_START |
638402dd AJ |
4018 | Format: |
4019 | cache_dir Type Directory-Name Fs-specific-data [options] | |
0976f8db | 4020 | |
41bd17a4 | 4021 | You can specify multiple cache_dir lines to spread the |
4022 | cache among different disk partitions. | |
0976f8db | 4023 | |
41bd17a4 | 4024 | Type specifies the kind of storage system to use. Only "ufs" |
4025 | is built by default. To enable any of the other storage systems | |
4026 | see the --enable-storeio configure option. | |
0976f8db | 4027 | |
41bd17a4 | 4028 | 'Directory' is a top-level directory where cache swap |
4029 | files will be stored. If you want to use an entire disk | |
4030 | for caching, this can be the mount-point directory. | |
4031 | The directory must exist and be writable by the Squid | |
4032 | process. Squid will NOT create this directory for you. | |
0976f8db | 4033 | |
acf69d74 AJ |
4034 | In SMP configurations, cache_dir must not precede the workers option |
4035 | and should use configuration macros or conditionals to give each | |
4036 | worker interested in disk caching a dedicated cache directory. | |
4037 | ||
638402dd AJ |
4038 | |
4039 | ==== The ufs store type ==== | |
0976f8db | 4040 | |
41bd17a4 | 4041 | "ufs" is the old well-known Squid storage format that has always |
4042 | been there. | |
0976f8db | 4043 | |
638402dd AJ |
4044 | Usage: |
4045 | cache_dir ufs Directory-Name Mbytes L1 L2 [options] | |
0976f8db | 4046 | |
41bd17a4 | 4047 | 'Mbytes' is the amount of disk space (MB) to use under this |
4048 | directory. The default is 100 MB. Change this to suit your | |
4049 | configuration. Do NOT put the size of your disk drive here. | |
4050 | Instead, if you want Squid to use the entire disk drive, | |
4051 | subtract 20% and use that value. | |
0976f8db | 4052 | |
56fba4d0 | 4053 | 'L1' is the number of first-level subdirectories which |
41bd17a4 | 4054 | will be created under the 'Directory'. The default is 16. |
0976f8db | 4055 | |
56fba4d0 | 4056 | 'L2' is the number of second-level subdirectories which |
41bd17a4 | 4057 | will be created under each first-level directory. The default |
4058 | is 256. | |
0976f8db | 4059 | |
638402dd AJ |
4060 | |
4061 | ==== The aufs store type ==== | |
7f7db318 | 4062 | |
41bd17a4 | 4063 | "aufs" uses the same storage format as "ufs", utilizing |
4064 | POSIX-threads to avoid blocking the main Squid process on | |
4065 | disk-I/O. This was formerly known in Squid as async-io. | |
38f9c547 | 4066 | |
638402dd AJ |
4067 | Usage: |
4068 | cache_dir aufs Directory-Name Mbytes L1 L2 [options] | |
38f9c547 | 4069 | |
41bd17a4 | 4070 | see argument descriptions under ufs above |
38f9c547 | 4071 | |
638402dd AJ |
4072 | |
4073 | ==== The diskd store type ==== | |
38f9c547 | 4074 | |
41bd17a4 | 4075 | "diskd" uses the same storage format as "ufs", utilizing a |
4076 | separate process to avoid blocking the main Squid process on | |
4077 | disk-I/O. | |
4c3ef9b2 | 4078 | |
638402dd AJ |
4079 | Usage: |
4080 | cache_dir diskd Directory-Name Mbytes L1 L2 [options] [Q1=n] [Q2=n] | |
0976f8db | 4081 | |
41bd17a4 | 4082 | see argument descriptions under ufs above |
0976f8db | 4083 | |
41bd17a4 | 4084 | Q1 specifies the number of unacknowledged I/O requests when Squid |
4085 | stops opening new files. If this many messages are in the queues, | |
4086 | Squid won't open new files. Default is 64 | |
0976f8db | 4087 | |
41bd17a4 | 4088 | Q2 specifies the number of unacknowledged messages when Squid |
4089 | starts blocking. If this many messages are in the queues, | |
4090 | Squid blocks until it receives some replies. Default is 72 | |
0976f8db | 4091 | |
41bd17a4 | 4092 | When Q1 < Q2 (the default), the cache directory is optimized |
4093 | for lower response time at the expense of a decrease in hit | |
4094 | ratio. If Q1 > Q2, the cache directory is optimized for | |
4095 | higher hit ratio at the expense of an increase in response | |
4096 | time. | |
0976f8db | 4097 | |
e2851fe7 | 4098 | |
638402dd AJ |
4099 | ==== The rock store type ==== |
4100 | ||
4101 | Usage: | |
e51ce7da | 4102 | cache_dir rock Directory-Name Mbytes [options] |
e2851fe7 | 4103 | |
2e55f083 | 4104 | The Rock Store type is a database-style storage. All cached |
e51ce7da AR |
4105 | entries are stored in a "database" file, using fixed-size slots. |
4106 | A single entry occupies one or more slots. | |
e2851fe7 | 4107 | |
3e1dfe3d AR |
4108 | If possible, Squid using Rock Store creates a dedicated kid |
4109 | process called "disker" to avoid blocking Squid worker(s) on disk | |
4110 | I/O. One disker kid is created for each rock cache_dir. Diskers | |
4111 | are created only when Squid, running in daemon mode, has support | |
4112 | for the IpcIo disk I/O module. | |
4113 | ||
43ebbac3 AR |
4114 | swap-timeout=msec: Squid will not start writing a miss to or |
4115 | reading a hit from disk if it estimates that the swap operation | |
4116 | will take more than the specified number of milliseconds. By | |
4117 | default and when set to zero, disables the disk I/O time limit | |
4118 | enforcement. Ignored when using blocking I/O module because | |
4119 | blocking synchronous I/O does not allow Squid to estimate the | |
4120 | expected swap wait time. | |
4121 | ||
df881a0f | 4122 | max-swap-rate=swaps/sec: Artificially limits disk access using |
1e614370 | 4123 | the specified I/O rate limit. Swap out requests that |
df881a0f | 4124 | would cause the average I/O rate to exceed the limit are |
1e614370 DK |
4125 | delayed. Individual swap in requests (i.e., hits or reads) are |
4126 | not delayed, but they do contribute to measured swap rate and | |
4127 | since they are placed in the same FIFO queue as swap out | |
4128 | requests, they may wait longer if max-swap-rate is smaller. | |
4129 | This is necessary on file systems that buffer "too | |
df881a0f AR |
4130 | many" writes and then start blocking Squid and other processes |
4131 | while committing those writes to disk. Usually used together | |
4132 | with swap-timeout to avoid excessive delays and queue overflows | |
4133 | when disk demand exceeds available disk "bandwidth". By default | |
4134 | and when set to zero, disables the disk I/O rate limit | |
4135 | enforcement. Currently supported by IpcIo module only. | |
4136 | ||
e51ce7da AR |
4137 | slot-size=bytes: The size of a database "record" used for |
4138 | storing cached responses. A cached response occupies at least | |
4139 | one slot and all database I/O is done using individual slots so | |
4140 | increasing this parameter leads to more disk space waste while | |
4141 | decreasing it leads to more disk I/O overheads. Should be a | |
4142 | multiple of your operating system I/O page size. Defaults to | |
4143 | 16KBytes. A housekeeping header is stored with each slot and | |
4144 | smaller slot-sizes will be rejected. The header is smaller than | |
4145 | 100 bytes. | |
4146 | ||
df881a0f | 4147 | |
638402dd | 4148 | ==== COMMON OPTIONS ==== |
0976f8db | 4149 | |
638402dd AJ |
4150 | no-store no new objects should be stored to this cache_dir. |
4151 | ||
4152 | min-size=n the minimum object size in bytes this cache_dir | |
4153 | will accept. It's used to restrict a cache_dir | |
4154 | to only store large objects (e.g. AUFS) while | |
4155 | other stores are optimized for smaller objects | |
73656056 | 4156 | (e.g. Rock). |
638402dd | 4157 | Defaults to 0. |
0976f8db | 4158 | |
638402dd AJ |
4159 | max-size=n the maximum object size in bytes this cache_dir |
4160 | supports. | |
499f852c A |
4161 | The value in maximum_object_size directive sets |
4162 | the default unless more specific details are | |
4163 | available (ie a small store capacity). | |
b6662ffd | 4164 | |
41bd17a4 | 4165 | Note: To make optimal use of the max-size limits you should order |
638402dd | 4166 | the cache_dir lines with the smallest max-size value first. |
0976f8db | 4167 | |
bebc043b | 4168 | NOCOMMENT_START |
e0855596 AJ |
4169 | |
4170 | # Uncomment and adjust the following to add a disk cache directory. | |
4171 | #cache_dir ufs @DEFAULT_SWAP_DIR@ 100 16 256 | |
bebc043b | 4172 | NOCOMMENT_END |
6b698a21 | 4173 | DOC_END |
0976f8db | 4174 | |
41bd17a4 | 4175 | NAME: store_dir_select_algorithm |
4176 | TYPE: string | |
4177 | LOC: Config.store_dir_select_algorithm | |
4178 | DEFAULT: least-load | |
6b698a21 | 4179 | DOC_START |
638402dd AJ |
4180 | How Squid selects which cache_dir to use when the response |
4181 | object will fit into more than one. | |
4182 | ||
4183 | Regardless of which algorithm is used the cache_dir min-size | |
4184 | and max-size parameters are obeyed. As such they can affect | |
4185 | the selection algorithm by limiting the set of considered | |
4186 | cache_dir. | |
4187 | ||
4188 | Algorithms: | |
4189 | ||
4190 | least-load | |
4191 | ||
4192 | This algorithm is suited to caches with similar cache_dir | |
4193 | sizes and disk speeds. | |
4194 | ||
4195 | The disk with the least I/O pending is selected. | |
4196 | When there are multiple disks with the same I/O load ranking | |
4197 | the cache_dir with most available capacity is selected. | |
4198 | ||
4199 | When a mix of cache_dir sizes are configured the faster disks | |
4200 | have a naturally lower I/O loading and larger disks have more | |
4201 | capacity. So space used to store objects and data throughput | |
4202 | may be very unbalanced towards larger disks. | |
4203 | ||
4204 | ||
4205 | round-robin | |
4206 | ||
4207 | This algorithm is suited to caches with unequal cache_dir | |
4208 | disk sizes. | |
4209 | ||
4210 | Each cache_dir is selected in a rotation. The next suitable | |
4211 | cache_dir is used. | |
4212 | ||
4213 | Available cache_dir capacity is only considered in relation | |
4214 | to whether the object will fit and meets the min-size and | |
4215 | max-size parameters. | |
4216 | ||
4217 | Disk I/O loading is only considered to prevent overload on slow | |
4218 | disks. This algorithm does not spread objects by size, so any | |
4219 | I/O loading per-disk may appear very unbalanced and volatile. | |
4220 | ||
29a238a3 AR |
4221 | If several cache_dirs use similar min-size, max-size, or other |
4222 | limits to to reject certain responses, then do not group such | |
4223 | cache_dir lines together, to avoid round-robin selection bias | |
4224 | towards the first cache_dir after the group. Instead, interleave | |
4225 | cache_dir lines from different groups. For example: | |
4226 | ||
4227 | store_dir_select_algorithm round-robin | |
4228 | cache_dir rock /hdd1 ... min-size=100000 | |
4229 | cache_dir rock /ssd1 ... max-size=99999 | |
4230 | cache_dir rock /hdd2 ... min-size=100000 | |
4231 | cache_dir rock /ssd2 ... max-size=99999 | |
4232 | cache_dir rock /hdd3 ... min-size=100000 | |
4233 | cache_dir rock /ssd3 ... max-size=99999 | |
6b698a21 | 4234 | DOC_END |
0976f8db | 4235 | |
41bd17a4 | 4236 | NAME: max_open_disk_fds |
4237 | TYPE: int | |
4238 | LOC: Config.max_open_disk_fds | |
4239 | DEFAULT: 0 | |
638402dd | 4240 | DEFAULT_DOC: no limit |
6b698a21 | 4241 | DOC_START |
41bd17a4 | 4242 | To avoid having disk as the I/O bottleneck Squid can optionally |
4243 | bypass the on-disk cache if more than this amount of disk file | |
4244 | descriptors are open. | |
4245 | ||
4246 | A value of 0 indicates no limit. | |
6b698a21 | 4247 | DOC_END |
0976f8db | 4248 | |
41bd17a4 | 4249 | NAME: cache_swap_low |
4250 | COMMENT: (percent, 0-100) | |
5473c134 | 4251 | TYPE: int |
41bd17a4 | 4252 | DEFAULT: 90 |
4253 | LOC: Config.Swap.lowWaterMark | |
638402dd | 4254 | DOC_START |
5f662601 AJ |
4255 | The low-water mark for AUFS/UFS/diskd cache object eviction by |
4256 | the cache_replacement_policy algorithm. | |
4257 | ||
4258 | Removal begins when the swap (disk) usage of a cache_dir is | |
4259 | above this low-water mark and attempts to maintain utilization | |
4260 | near the low-water mark. | |
4261 | ||
4262 | As swap utilization increases towards the high-water mark set | |
4263 | by cache_swap_high object eviction becomes more agressive. | |
4264 | ||
4265 | The value difference in percentages between low- and high-water | |
7bcaf76f | 4266 | marks represent an eviction rate of 300 objects per second and |
5f662601 AJ |
4267 | the rate continues to scale in agressiveness by multiples of |
4268 | this above the high-water mark. | |
638402dd AJ |
4269 | |
4270 | Defaults are 90% and 95%. If you have a large cache, 5% could be | |
4271 | hundreds of MB. If this is the case you may wish to set these | |
4272 | numbers closer together. | |
4273 | ||
5f662601 | 4274 | See also cache_swap_high and cache_replacement_policy |
638402dd | 4275 | DOC_END |
41bd17a4 | 4276 | |
4277 | NAME: cache_swap_high | |
4278 | COMMENT: (percent, 0-100) | |
4279 | TYPE: int | |
4280 | DEFAULT: 95 | |
4281 | LOC: Config.Swap.highWaterMark | |
6b698a21 | 4282 | DOC_START |
5f662601 AJ |
4283 | The high-water mark for AUFS/UFS/diskd cache object eviction by |
4284 | the cache_replacement_policy algorithm. | |
4285 | ||
4286 | Removal begins when the swap (disk) usage of a cache_dir is | |
4287 | above the low-water mark set by cache_swap_low and attempts to | |
4288 | maintain utilization near the low-water mark. | |
4289 | ||
4290 | As swap utilization increases towards this high-water mark object | |
4291 | eviction becomes more agressive. | |
4292 | ||
4293 | The value difference in percentages between low- and high-water | |
7bcaf76f | 4294 | marks represent an eviction rate of 300 objects per second and |
5f662601 AJ |
4295 | the rate continues to scale in agressiveness by multiples of |
4296 | this above the high-water mark. | |
41bd17a4 | 4297 | |
4298 | Defaults are 90% and 95%. If you have a large cache, 5% could be | |
4299 | hundreds of MB. If this is the case you may wish to set these | |
4300 | numbers closer together. | |
638402dd | 4301 | |
5f662601 | 4302 | See also cache_swap_low and cache_replacement_policy |
6b698a21 | 4303 | DOC_END |
0976f8db | 4304 | |
5473c134 | 4305 | COMMENT_START |
41bd17a4 | 4306 | LOGFILE OPTIONS |
5473c134 | 4307 | ----------------------------------------------------------------------------- |
4308 | COMMENT_END | |
0976f8db | 4309 | |
41bd17a4 | 4310 | NAME: logformat |
4311 | TYPE: logformat | |
20efa1c2 | 4312 | LOC: Log::TheConfig |
5473c134 | 4313 | DEFAULT: none |
638402dd | 4314 | DEFAULT_DOC: The format definitions squid, common, combined, referrer, useragent are built in. |
6b698a21 | 4315 | DOC_START |
41bd17a4 | 4316 | Usage: |
0976f8db | 4317 | |
41bd17a4 | 4318 | logformat <name> <format specification> |
0976f8db | 4319 | |
41bd17a4 | 4320 | Defines an access log format. |
6b698a21 | 4321 | |
41bd17a4 | 4322 | The <format specification> is a string with embedded % format codes |
5473c134 | 4323 | |
41bd17a4 | 4324 | % format codes all follow the same basic structure where all but |
4325 | the formatcode is optional. Output strings are automatically escaped | |
4326 | as required according to their context and the output format | |
4327 | modifiers are usually not needed, but can be specified if an explicit | |
4328 | output format is desired. | |
6b698a21 | 4329 | |
95d78f10 | 4330 | % ["|[|'|#|/] [-] [[0]width] [{arg}] formatcode [{arg}] |
0976f8db | 4331 | |
41bd17a4 | 4332 | " output in quoted string format |
4333 | [ output in squid text log format as used by log_mime_hdrs | |
4334 | # output in URL quoted format | |
95d78f10 | 4335 | / output in shell \-escaped format |
41bd17a4 | 4336 | ' output as-is |
5473c134 | 4337 | |
41bd17a4 | 4338 | - left aligned |
c32c6db7 AR |
4339 | |
4340 | width minimum and/or maximum field width: | |
4341 | [width_min][.width_max] | |
e2851fe7 AR |
4342 | When minimum starts with 0, the field is zero-padded. |
4343 | String values exceeding maximum width are truncated. | |
c32c6db7 | 4344 | |
4e56d7f6 AJ |
4345 | {arg} argument such as header name etc. This field may be |
4346 | placed before or after the token, but not both at once. | |
5473c134 | 4347 | |
41bd17a4 | 4348 | Format codes: |
5473c134 | 4349 | |
3ff65596 | 4350 | % a literal % character |
f4b68e1a AJ |
4351 | sn Unique sequence number per log line entry |
4352 | err_code The ID of an error response served by Squid or | |
4353 | a similar internal error identifier. | |
4354 | err_detail Additional err_code-dependent error information. | |
c7bcf010 | 4355 | note The annotation specified by the argument. Also |
d7f4a0b7 CT |
4356 | logs the adaptation meta headers set by the |
4357 | adaptation_meta configuration parameter. | |
c7bcf010 CT |
4358 | If no argument given all annotations logged. |
4359 | The argument may include a separator to use with | |
4360 | annotation values: | |
4361 | name[:separator] | |
4362 | By default, multiple note values are separated with "," | |
4363 | and multiple notes are separated with "\r\n". | |
4364 | When logging named notes with %{name}note, the | |
4365 | explicitly configured separator is used between note | |
4366 | values. When logging all notes with %note, the | |
4367 | explicitly configured separator is used between | |
4368 | individual notes. There is currently no way to | |
4369 | specify both value and notes separators when logging | |
4370 | all notes with %note. | |
f4b68e1a AJ |
4371 | |
4372 | Connection related format codes: | |
4373 | ||
41bd17a4 | 4374 | >a Client source IP address |
4375 | >A Client FQDN | |
4376 | >p Client source port | |
8652f8e7 AJ |
4377 | >eui Client source EUI (MAC address, EUI-48 or EUI-64 identifier) |
4378 | >la Local IP address the client connected to | |
4379 | >lp Local port number the client connected to | |
f123f5e9 CT |
4380 | >qos Client connection TOS/DSCP value set by Squid |
4381 | >nfmark Client connection netfilter mark set by Squid | |
8652f8e7 | 4382 | |
28417506 CT |
4383 | la Local listening IP address the client connection was connected to. |
4384 | lp Local listening port number the client connection was connected to. | |
4385 | ||
8652f8e7 AJ |
4386 | <a Server IP address of the last server or peer connection |
4387 | <A Server FQDN or peer name | |
4388 | <p Server port number of the last server or peer connection | |
c3a082ae | 4389 | <la Local IP address of the last server or peer connection |
152e24b3 | 4390 | <lp Local port number of the last server or peer connection |
f123f5e9 CT |
4391 | <qos Server connection TOS/DSCP value set by Squid |
4392 | <nfmark Server connection netfilter mark set by Squid | |
f4b68e1a AJ |
4393 | |
4394 | Time related format codes: | |
4395 | ||
41bd17a4 | 4396 | ts Seconds since epoch |
4397 | tu subsecond time (milliseconds) | |
4398 | tl Local time. Optional strftime format argument | |
3ff65596 | 4399 | default %d/%b/%Y:%H:%M:%S %z |
41bd17a4 | 4400 | tg GMT time. Optional strftime format argument |
3ff65596 | 4401 | default %d/%b/%Y:%H:%M:%S %z |
41bd17a4 | 4402 | tr Response time (milliseconds) |
3ff65596 | 4403 | dt Total time spent making DNS lookups (milliseconds) |
af0ded40 CT |
4404 | tS Approximate master transaction start time in |
4405 | <full seconds since epoch>.<fractional seconds> format. | |
4406 | Currently, Squid considers the master transaction | |
4407 | started when a complete HTTP request header initiating | |
4408 | the transaction is received from the client. This is | |
4409 | the same value that Squid uses to calculate transaction | |
4410 | response time when logging %tr to access.log. Currently, | |
4411 | Squid uses millisecond resolution for %tS values, | |
4412 | similar to the default access.log "current time" field | |
4413 | (%ts.%03tu). | |
3ff65596 | 4414 | |
8652f8e7 AJ |
4415 | Access Control related format codes: |
4416 | ||
4417 | et Tag returned by external acl | |
4418 | ea Log string returned by external acl | |
4419 | un User name (any available) | |
4420 | ul User name from authentication | |
4421 | ue User name from external acl helper | |
4422 | ui User name from ident | |
50b5c983 AJ |
4423 | un A user name. Expands to the first available name |
4424 | from the following list of information sources: | |
4425 | - authenticated user name, like %ul | |
4426 | - user name supplied by an external ACL, like %ue | |
4427 | - SSL client name, like %us | |
4428 | - ident user name, like %ui | |
d4806c91 CT |
4429 | credentials Client credentials. The exact meaning depends on |
4430 | the authentication scheme: For Basic authentication, | |
4431 | it is the password; for Digest, the realm sent by the | |
4432 | client; for NTLM and Negotiate, the client challenge | |
4433 | or client credentials prefixed with "YR " or "KK ". | |
8652f8e7 AJ |
4434 | |
4435 | HTTP related format codes: | |
3ff65596 | 4436 | |
d6df21d2 AJ |
4437 | REQUEST |
4438 | ||
4439 | [http::]rm Request method (GET/POST etc) | |
4440 | [http::]>rm Request method from client | |
4441 | [http::]<rm Request method sent to server or peer | |
4442 | [http::]ru Request URL from client (historic, filtered for logging) | |
4443 | [http::]>ru Request URL from client | |
4444 | [http::]<ru Request URL sent to server or peer | |
5aca9cf2 AJ |
4445 | [http::]>rs Request URL scheme from client |
4446 | [http::]<rs Request URL scheme sent to server or peer | |
fa450988 | 4447 | [http::]>rd Request URL domain from client |
f42ac6e6 | 4448 | [http::]<rd Request URL domain sent to server or peer |
5aca9cf2 AJ |
4449 | [http::]>rP Request URL port from client |
4450 | [http::]<rP Request URL port sent to server or peer | |
4451 | [http::]rp Request URL path excluding hostname | |
4452 | [http::]>rp Request URL path excluding hostname from client | |
4453 | [http::]<rp Request URL path excluding hostname sent to server or peer | |
d6df21d2 AJ |
4454 | [http::]rv Request protocol version |
4455 | [http::]>rv Request protocol version from client | |
4456 | [http::]<rv Request protocol version sent to server or peer | |
4457 | ||
5aca9cf2 | 4458 | [http::]>h Original received request header. |
19483c50 AR |
4459 | Usually differs from the request header sent by |
4460 | Squid, although most fields are often preserved. | |
4461 | Accepts optional header field name/value filter | |
4462 | argument using name[:[separator]element] format. | |
4463 | [http::]>ha Received request header after adaptation and | |
4464 | redirection (pre-cache REQMOD vectoring point). | |
4465 | Usually differs from the request header sent by | |
4466 | Squid, although most fields are often preserved. | |
6fca33e0 | 4467 | Optional header name argument as for >h |
d6df21d2 | 4468 | |
d6df21d2 AJ |
4469 | RESPONSE |
4470 | ||
4471 | [http::]<Hs HTTP status code received from the next hop | |
4472 | [http::]>Hs HTTP status code sent to the client | |
4473 | ||
3ff65596 AR |
4474 | [http::]<h Reply header. Optional header name argument |
4475 | as for >h | |
d6df21d2 AJ |
4476 | |
4477 | [http::]mt MIME content type | |
4478 | ||
4479 | ||
4480 | SIZE COUNTERS | |
4481 | ||
4482 | [http::]st Total size of request + reply traffic with client | |
4483 | [http::]>st Total size of request received from client. | |
4484 | Excluding chunked encoding bytes. | |
4485 | [http::]<st Total size of reply sent to client (after adaptation) | |
4486 | ||
4487 | [http::]>sh Size of request headers received from client | |
4488 | [http::]<sh Size of reply headers sent to client (after adaptation) | |
4489 | ||
4490 | [http::]<sH Reply high offset sent | |
4491 | [http::]<sS Upstream object size | |
4492 | ||
bae917ac CT |
4493 | [http::]<bs Number of HTTP-equivalent message body bytes |
4494 | received from the next hop, excluding chunked | |
4495 | transfer encoding and control messages. | |
4496 | Generated FTP/Gopher listings are treated as | |
4497 | received bodies. | |
d6df21d2 | 4498 | |
d6df21d2 AJ |
4499 | TIMING |
4500 | ||
3ff65596 AR |
4501 | [http::]<pt Peer response time in milliseconds. The timer starts |
4502 | when the last request byte is sent to the next hop | |
4503 | and stops when the last response byte is received. | |
d5430dc8 | 4504 | [http::]<tt Total time in milliseconds. The timer |
3ff65596 AR |
4505 | starts with the first connect request (or write I/O) |
4506 | sent to the first selected peer. The timer stops | |
4507 | with the last I/O with the last peer. | |
4508 | ||
8652f8e7 AJ |
4509 | Squid handling related format codes: |
4510 | ||
4511 | Ss Squid request status (TCP_MISS etc) | |
4512 | Sh Squid hierarchy status (DEFAULT_PARENT etc) | |
4513 | ||
08097970 AR |
4514 | SSL-related format codes: |
4515 | ||
4516 | ssl::bump_mode SslBump decision for the transaction: | |
4517 | ||
4518 | For CONNECT requests that initiated bumping of | |
4519 | a connection and for any request received on | |
4520 | an already bumped connection, Squid logs the | |
bf352fb2 CT |
4521 | corresponding SslBump mode ("splice", "bump", |
4522 | "peek", "stare", "terminate", "server-first" | |
4523 | or "client-first"). See the ssl_bump option | |
4524 | for more information about these modes. | |
08097970 AR |
4525 | |
4526 | A "none" token is logged for requests that | |
4527 | triggered "ssl_bump" ACL evaluation matching | |
bf352fb2 | 4528 | a "none" rule. |
08097970 AR |
4529 | |
4530 | In all other cases, a single dash ("-") is | |
4531 | logged. | |
4532 | ||
4f6990ec | 4533 | ssl::>sni SSL client SNI sent to Squid. |
cedca6e7 | 4534 | |
c28b9a0e AJ |
4535 | ssl::>cert_subject |
4536 | The Subject field of the received client | |
4537 | SSL certificate or a dash ('-') if Squid has | |
4538 | received an invalid/malformed certificate or | |
4539 | no certificate at all. Consider encoding the | |
4540 | logged value because Subject often has spaces. | |
4541 | ||
4542 | ssl::>cert_issuer | |
4543 | The Issuer field of the received client | |
4544 | SSL certificate or a dash ('-') if Squid has | |
4545 | received an invalid/malformed certificate or | |
4546 | no certificate at all. Consider encoding the | |
4547 | logged value because Issuer often has spaces. | |
4548 | ||
4549 | ssl::<cert_errors | |
4550 | The list of certificate validation errors | |
4551 | detected by Squid (including OpenSSL and | |
4552 | certificate validation helper components). The | |
4553 | errors are listed in the discovery order. By | |
4554 | default, the error codes are separated by ':'. | |
4555 | Accepts an optional separator argument. | |
4556 | ||
2bcab852 CT |
4557 | %ssl::>negotiated_version The negotiated TLS version of the |
4558 | client connection. | |
4559 | ||
4560 | %ssl::<negotiated_version The negotiated TLS version of the | |
4561 | last server or peer connection. | |
4562 | ||
4563 | %ssl::>received_hello_version The TLS version of the Hello | |
4564 | message received from TLS client. | |
4565 | ||
4566 | %ssl::<received_hello_version The TLS version of the Hello | |
4567 | message received from TLS server. | |
4568 | ||
4569 | %ssl::>received_supported_version The maximum TLS version | |
4570 | supported by the TLS client. | |
4571 | ||
4572 | %ssl::<received_supported_version The maximum TLS version | |
4573 | supported by the TLS server. | |
4574 | ||
4575 | %ssl::>negotiated_cipher The negotiated cipher of the | |
4576 | client connection. | |
4577 | ||
4578 | %ssl::<negotiated_cipher The negotiated cipher of the | |
4579 | last server or peer connection. | |
4580 | ||
5038f9d8 | 4581 | If ICAP is enabled, the following code becomes available (as |
3ff65596 AR |
4582 | well as ICAP log codes documented with the icap_log option): |
4583 | ||
4584 | icap::tt Total ICAP processing time for the HTTP | |
4585 | transaction. The timer ticks when ICAP | |
4586 | ACLs are checked and when ICAP | |
4587 | transaction is in progress. | |
4588 | ||
c28b9a0e | 4589 | If adaptation is enabled the following codes become available: |
3ff65596 | 4590 | |
5038f9d8 AR |
4591 | adapt::<last_h The header of the last ICAP response or |
4592 | meta-information from the last eCAP | |
4593 | transaction related to the HTTP transaction. | |
4594 | Like <h, accepts an optional header name | |
4595 | argument. | |
3ff65596 AR |
4596 | |
4597 | adapt::sum_trs Summed adaptation transaction response | |
4598 | times recorded as a comma-separated list in | |
4599 | the order of transaction start time. Each time | |
4600 | value is recorded as an integer number, | |
4601 | representing response time of one or more | |
4602 | adaptation (ICAP or eCAP) transaction in | |
4603 | milliseconds. When a failed transaction is | |
4604 | being retried or repeated, its time is not | |
4605 | logged individually but added to the | |
4606 | replacement (next) transaction. See also: | |
4607 | adapt::all_trs. | |
4608 | ||
4609 | adapt::all_trs All adaptation transaction response times. | |
4610 | Same as adaptation_strs but response times of | |
4611 | individual transactions are never added | |
4612 | together. Instead, all transaction response | |
4613 | times are recorded individually. | |
4614 | ||
4615 | You can prefix adapt::*_trs format codes with adaptation | |
4616 | service name in curly braces to record response time(s) specific | |
4617 | to that service. For example: %{my_service}adapt::sum_trs | |
5473c134 | 4618 | |
7d9acc3c AJ |
4619 | The default formats available (which do not need re-defining) are: |
4620 | ||
bd85ea1f AJ |
4621 | logformat squid %ts.%03tu %6tr %>a %Ss/%03>Hs %<st %rm %ru %[un %Sh/%<a %mt |
4622 | logformat common %>a %[ui %[un [%tl] "%rm %ru HTTP/%rv" %>Hs %<st %Ss:%Sh | |
4623 | logformat combined %>a %[ui %[un [%tl] "%rm %ru HTTP/%rv" %>Hs %<st "%{Referer}>h" "%{User-Agent}>h" %Ss:%Sh | |
20efa1c2 AJ |
4624 | logformat referrer %ts.%03tu %>a %{Referer}>h %ru |
4625 | logformat useragent %>a [%tl] "%{User-Agent}>h" | |
4626 | ||
8652f8e7 AJ |
4627 | NOTE: When the log_mime_hdrs directive is set to ON. |
4628 | The squid, common and combined formats have a safely encoded copy | |
4629 | of the mime headers appended to each line within a pair of brackets. | |
4630 | ||
4631 | NOTE: The common and combined formats are not quite true to the Apache definition. | |
4632 | The logs from Squid contain an extra status and hierarchy code appended. | |
20efa1c2 | 4633 | |
5473c134 | 4634 | DOC_END |
4635 | ||
41bd17a4 | 4636 | NAME: access_log cache_access_log |
4637 | TYPE: access_log | |
4638 | LOC: Config.Log.accesslogs | |
82b7abe3 | 4639 | DEFAULT_IF_NONE: daemon:@DEFAULT_ACCESS_LOG@ squid |
5473c134 | 4640 | DOC_START |
fb0c2f17 NH |
4641 | Configures whether and how Squid logs HTTP and ICP transactions. |
4642 | If access logging is enabled, a single line is logged for every | |
4643 | matching HTTP or ICP request. The recommended directive formats are: | |
4644 | ||
4645 | access_log <module>:<place> [option ...] [acl acl ...] | |
4646 | access_log none [acl acl ...] | |
4647 | ||
4648 | The following directive format is accepted but may be deprecated: | |
82b7abe3 | 4649 | access_log <module>:<place> [<logformat name> [acl acl ...]] |
fb0c2f17 NH |
4650 | |
4651 | In most cases, the first ACL name must not contain the '=' character | |
4652 | and should not be equal to an existing logformat name. You can always | |
4653 | start with an 'all' ACL to work around those restrictions. | |
82b7abe3 AJ |
4654 | |
4655 | Will log to the specified module:place using the specified format (which | |
41bd17a4 | 4656 | must be defined in a logformat directive) those entries which match |
4657 | ALL the acl's specified (which must be defined in acl clauses). | |
82b7abe3 AJ |
4658 | If no acl is specified, all requests will be logged to this destination. |
4659 | ||
fb0c2f17 NH |
4660 | ===== Available options for the recommended directive format ===== |
4661 | ||
4662 | logformat=name Names log line format (either built-in or | |
4663 | defined by a logformat directive). Defaults | |
4664 | to 'squid'. | |
4665 | ||
4666 | buffer-size=64KB Defines approximate buffering limit for log | |
4667 | records (see buffered_logs). Squid should not | |
4668 | keep more than the specified size and, hence, | |
4669 | should flush records before the buffer becomes | |
4670 | full to avoid overflows under normal | |
4671 | conditions (the exact flushing algorithm is | |
4672 | module-dependent though). The on-error option | |
4673 | controls overflow handling. | |
4674 | ||
4675 | on-error=die|drop Defines action on unrecoverable errors. The | |
4676 | 'drop' action ignores (i.e., does not log) | |
4677 | affected log records. The default 'die' action | |
4678 | kills the affected worker. The drop action | |
4679 | support has not been tested for modules other | |
4680 | than tcp. | |
4681 | ||
efc23871 AJ |
4682 | rotate=N Specifies the number of log file rotations to |
4683 | make when you run 'squid -k rotate'. The default | |
4684 | is to obey the logfile_rotate directive. Setting | |
4685 | rotate=0 will disable the file name rotation, | |
4686 | but the log files are still closed and re-opened. | |
4687 | This will enable you to rename the logfiles | |
4688 | yourself just before sending the rotate signal. | |
4689 | Only supported by the stdio module. | |
4690 | ||
82b7abe3 AJ |
4691 | ===== Modules Currently available ===== |
4692 | ||
bb7a1781 | 4693 | none Do not log any requests matching these ACL. |
82b7abe3 AJ |
4694 | Do not specify Place or logformat name. |
4695 | ||
4696 | stdio Write each log line to disk immediately at the completion of | |
4697 | each request. | |
4698 | Place: the filename and path to be written. | |
4699 | ||
4700 | daemon Very similar to stdio. But instead of writing to disk the log | |
4701 | line is passed to a daemon helper for asychronous handling instead. | |
4702 | Place: varies depending on the daemon. | |
4703 | ||
4704 | log_file_daemon Place: the file name and path to be written. | |
4705 | ||
4706 | syslog To log each request via syslog facility. | |
4707 | Place: The syslog facility and priority level for these entries. | |
4708 | Place Format: facility.priority | |
5473c134 | 4709 | |
82b7abe3 AJ |
4710 | where facility could be any of: |
4711 | authpriv, daemon, local0 ... local7 or user. | |
5473c134 | 4712 | |
82b7abe3 AJ |
4713 | And priority could be any of: |
4714 | err, warning, notice, info, debug. | |
4715 | ||
4716 | udp To send each log line as text data to a UDP receiver. | |
4717 | Place: The destination host name or IP and port. | |
f4fc8610 | 4718 | Place Format: //host:port |
df2eec10 | 4719 | |
2bf4e8fa | 4720 | tcp To send each log line as text data to a TCP receiver. |
fb0c2f17 | 4721 | Lines may be accumulated before sending (see buffered_logs). |
2bf4e8fa | 4722 | Place: The destination host name or IP and port. |
f4fc8610 | 4723 | Place Format: //host:port |
df2eec10 AJ |
4724 | |
4725 | Default: | |
82b7abe3 | 4726 | access_log daemon:@DEFAULT_ACCESS_LOG@ squid |
41bd17a4 | 4727 | DOC_END |
5473c134 | 4728 | |
3ff65596 AR |
4729 | NAME: icap_log |
4730 | TYPE: access_log | |
4731 | IFDEF: ICAP_CLIENT | |
4732 | LOC: Config.Log.icaplogs | |
4733 | DEFAULT: none | |
4734 | DOC_START | |
4735 | ICAP log files record ICAP transaction summaries, one line per | |
4736 | transaction. | |
4737 | ||
4738 | The icap_log option format is: | |
4739 | icap_log <filepath> [<logformat name> [acl acl ...]] | |
4740 | icap_log none [acl acl ...]] | |
4741 | ||
4742 | Please see access_log option documentation for details. The two | |
4743 | kinds of logs share the overall configuration approach and many | |
4744 | features. | |
4745 | ||
4746 | ICAP processing of a single HTTP message or transaction may | |
4747 | require multiple ICAP transactions. In such cases, multiple | |
4748 | ICAP transaction log lines will correspond to a single access | |
4749 | log line. | |
4750 | ||
bd59d61c EB |
4751 | ICAP log supports many access.log logformat %codes. In ICAP context, |
4752 | HTTP message-related %codes are applied to the HTTP message embedded | |
4753 | in an ICAP message. Logformat "%http::>..." codes are used for HTTP | |
4754 | messages embedded in ICAP requests while "%http::<..." codes are used | |
4755 | for HTTP messages embedded in ICAP responses. For example: | |
4756 | ||
4757 | http::>h To-be-adapted HTTP message headers sent by Squid to | |
4758 | the ICAP service. For REQMOD transactions, these are | |
4759 | HTTP request headers. For RESPMOD, these are HTTP | |
4760 | response headers, but Squid currently cannot log them | |
4761 | (i.e., %http::>h will expand to "-" for RESPMOD). | |
4762 | ||
4763 | http::<h Adapted HTTP message headers sent by the ICAP | |
4764 | service to Squid (i.e., HTTP request headers in regular | |
4765 | REQMOD; HTTP response headers in RESPMOD and during | |
4766 | request satisfaction in REQMOD). | |
4767 | ||
4768 | ICAP OPTIONS transactions do not embed HTTP messages. | |
4769 | ||
4770 | Several logformat codes below deal with ICAP message bodies. An ICAP | |
4771 | message body, if any, typically includes a complete HTTP message | |
4772 | (required HTTP headers plus optional HTTP message body). When | |
4773 | computing HTTP message body size for these logformat codes, Squid | |
4774 | either includes or excludes chunked encoding overheads; see | |
4775 | code-specific documentation for details. | |
4776 | ||
4777 | For Secure ICAP services, all size-related information is currently | |
4778 | computed before/after TLS encryption/decryption, as if TLS was not | |
4779 | in use at all. | |
3ff65596 AR |
4780 | |
4781 | The following format codes are also available for ICAP logs: | |
4782 | ||
4783 | icap::<A ICAP server IP address. Similar to <A. | |
4784 | ||
4785 | icap::<service_name ICAP service name from the icap_service | |
4786 | option in Squid configuration file. | |
4787 | ||
4788 | icap::ru ICAP Request-URI. Similar to ru. | |
4789 | ||
4790 | icap::rm ICAP request method (REQMOD, RESPMOD, or | |
4791 | OPTIONS). Similar to existing rm. | |
4792 | ||
bd59d61c EB |
4793 | icap::>st The total size of the ICAP request sent to the ICAP |
4794 | server (ICAP headers + ICAP body), including chunking | |
4795 | metadata (if any). | |
3ff65596 | 4796 | |
bd59d61c EB |
4797 | icap::<st The total size of the ICAP response received from the |
4798 | ICAP server (ICAP headers + ICAP body), including | |
4799 | chunking metadata (if any). | |
3ff65596 | 4800 | |
bd59d61c EB |
4801 | icap::<bs The size of the ICAP response body received from the |
4802 | ICAP server, excluding chunking metadata (if any). | |
bae917ac | 4803 | |
3ff65596 AR |
4804 | icap::tr Transaction response time (in |
4805 | milliseconds). The timer starts when | |
4806 | the ICAP transaction is created and | |
4807 | stops when the transaction is completed. | |
4808 | Similar to tr. | |
4809 | ||
4810 | icap::tio Transaction I/O time (in milliseconds). The | |
4811 | timer starts when the first ICAP request | |
4812 | byte is scheduled for sending. The timers | |
4813 | stops when the last byte of the ICAP response | |
4814 | is received. | |
4815 | ||
4816 | icap::to Transaction outcome: ICAP_ERR* for all | |
4817 | transaction errors, ICAP_OPT for OPTION | |
4818 | transactions, ICAP_ECHO for 204 | |
4819 | responses, ICAP_MOD for message | |
4820 | modification, and ICAP_SAT for request | |
4821 | satisfaction. Similar to Ss. | |
4822 | ||
4823 | icap::Hs ICAP response status code. Similar to Hs. | |
4824 | ||
4825 | icap::>h ICAP request header(s). Similar to >h. | |
4826 | ||
4827 | icap::<h ICAP response header(s). Similar to <h. | |
4828 | ||
4829 | The default ICAP log format, which can be used without an explicit | |
4830 | definition, is called icap_squid: | |
4831 | ||
bd59d61c | 4832 | logformat icap_squid %ts.%03tu %6icap::tr %>A %icap::to/%03icap::Hs %icap::<st %icap::rm %icap::ru %un -/%icap::<A - |
3ff65596 | 4833 | |
bd59d61c | 4834 | See also: logformat and %adapt::<last_h |
3ff65596 AR |
4835 | DOC_END |
4836 | ||
82b7abe3 AJ |
4837 | NAME: logfile_daemon |
4838 | TYPE: string | |
4839 | DEFAULT: @DEFAULT_LOGFILED@ | |
4840 | LOC: Log::TheConfig.logfile_daemon | |
4841 | DOC_START | |
4842 | Specify the path to the logfile-writing daemon. This daemon is | |
4843 | used to write the access and store logs, if configured. | |
14b24caf HN |
4844 | |
4845 | Squid sends a number of commands to the log daemon: | |
4846 | L<data>\n - logfile data | |
4847 | R\n - rotate file | |
4848 | T\n - truncate file | |
dd68402f | 4849 | O\n - reopen file |
14b24caf HN |
4850 | F\n - flush file |
4851 | r<n>\n - set rotate count to <n> | |
4852 | b<n>\n - 1 = buffer output, 0 = don't buffer output | |
4853 | ||
4854 | No responses is expected. | |
82b7abe3 AJ |
4855 | DOC_END |
4856 | ||
8ebad780 | 4857 | NAME: stats_collection |
3ff65596 | 4858 | TYPE: acl_access |
8ebad780 | 4859 | LOC: Config.accessList.stats_collection |
3ff65596 | 4860 | DEFAULT: none |
638402dd | 4861 | DEFAULT_DOC: Allow logging for all transactions. |
5b0f5383 | 4862 | COMMENT: allow|deny acl acl... |
3ff65596 | 4863 | DOC_START |
8ebad780 CT |
4864 | This options allows you to control which requests gets accounted |
4865 | in performance counters. | |
b3567eb5 FC |
4866 | |
4867 | This clause only supports fast acl types. | |
4868 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
3ff65596 AR |
4869 | DOC_END |
4870 | ||
41bd17a4 | 4871 | NAME: cache_store_log |
4872 | TYPE: string | |
df2eec10 | 4873 | DEFAULT: none |
41bd17a4 | 4874 | LOC: Config.Log.store |
4875 | DOC_START | |
4876 | Logs the activities of the storage manager. Shows which | |
4877 | objects are ejected from the cache, and which objects are | |
6d1dfcfc | 4878 | saved and for how long. |
df2eec10 | 4879 | There are not really utilities to analyze this data, so you can safely |
6d1dfcfc AJ |
4880 | disable it (the default). |
4881 | ||
4882 | Store log uses modular logging outputs. See access_log for the list | |
4883 | of modules supported. | |
4884 | ||
e0855596 | 4885 | Example: |
6d1dfcfc AJ |
4886 | cache_store_log stdio:@DEFAULT_STORE_LOG@ |
4887 | cache_store_log daemon:@DEFAULT_STORE_LOG@ | |
5473c134 | 4888 | DOC_END |
4889 | ||
41bd17a4 | 4890 | NAME: cache_swap_state cache_swap_log |
4891 | TYPE: string | |
4892 | LOC: Config.Log.swap | |
5473c134 | 4893 | DEFAULT: none |
638402dd | 4894 | DEFAULT_DOC: Store the journal inside its cache_dir |
5473c134 | 4895 | DOC_START |
41bd17a4 | 4896 | Location for the cache "swap.state" file. This index file holds |
4897 | the metadata of objects saved on disk. It is used to rebuild | |
4898 | the cache during startup. Normally this file resides in each | |
4899 | 'cache_dir' directory, but you may specify an alternate | |
4900 | pathname here. Note you must give a full filename, not just | |
4901 | a directory. Since this is the index for the whole object | |
4902 | list you CANNOT periodically rotate it! | |
5473c134 | 4903 | |
41bd17a4 | 4904 | If %s can be used in the file name it will be replaced with a |
4905 | a representation of the cache_dir name where each / is replaced | |
4906 | with '.'. This is needed to allow adding/removing cache_dir | |
4907 | lines when cache_swap_log is being used. | |
5473c134 | 4908 | |
41bd17a4 | 4909 | If have more than one 'cache_dir', and %s is not used in the name |
4910 | these swap logs will have names such as: | |
5473c134 | 4911 | |
41bd17a4 | 4912 | cache_swap_log.00 |
4913 | cache_swap_log.01 | |
4914 | cache_swap_log.02 | |
5473c134 | 4915 | |
41bd17a4 | 4916 | The numbered extension (which is added automatically) |
4917 | corresponds to the order of the 'cache_dir' lines in this | |
4918 | configuration file. If you change the order of the 'cache_dir' | |
4919 | lines in this file, these index files will NOT correspond to | |
4920 | the correct 'cache_dir' entry (unless you manually rename | |
4921 | them). We recommend you do NOT use this option. It is | |
4922 | better to keep these index files in each 'cache_dir' directory. | |
5473c134 | 4923 | DOC_END |
4924 | ||
41bd17a4 | 4925 | NAME: logfile_rotate |
4926 | TYPE: int | |
4927 | DEFAULT: 10 | |
4928 | LOC: Config.Log.rotateNumber | |
5473c134 | 4929 | DOC_START |
efc23871 | 4930 | Specifies the default number of logfile rotations to make when you |
41bd17a4 | 4931 | type 'squid -k rotate'. The default is 10, which will rotate |
4932 | with extensions 0 through 9. Setting logfile_rotate to 0 will | |
4933 | disable the file name rotation, but the logfiles are still closed | |
4934 | and re-opened. This will enable you to rename the logfiles | |
4935 | yourself just before sending the rotate signal. | |
5473c134 | 4936 | |
efc23871 AJ |
4937 | Note, from Squid-3.1 this option is only a default for cache.log, |
4938 | that log can be rotated separately by using debug_options. | |
4939 | ||
4940 | Note, from Squid-3.6 this option is only a default for access.log | |
4941 | recorded by stdio: module. Those logs can be rotated separately by | |
4942 | using the rotate=N option on their access_log directive. | |
4943 | ||
41bd17a4 | 4944 | Note, the 'squid -k rotate' command normally sends a USR1 |
4945 | signal to the running squid process. In certain situations | |
4946 | (e.g. on Linux with Async I/O), USR1 is used for other | |
4947 | purposes, so -k rotate uses another signal. It is best to get | |
4948 | in the habit of using 'squid -k rotate' instead of 'kill -USR1 | |
4949 | <pid>'. | |
62493678 | 4950 | |
41bd17a4 | 4951 | DOC_END |
5473c134 | 4952 | |
41bd17a4 | 4953 | NAME: mime_table |
4954 | TYPE: string | |
4955 | DEFAULT: @DEFAULT_MIME_TABLE@ | |
4956 | LOC: Config.mimeTablePathname | |
4957 | DOC_START | |
638402dd AJ |
4958 | Path to Squid's icon configuration file. |
4959 | ||
4960 | You shouldn't need to change this, but the default file contains | |
4961 | examples and formatting information if you do. | |
5473c134 | 4962 | DOC_END |
4963 | ||
41bd17a4 | 4964 | NAME: log_mime_hdrs |
4965 | COMMENT: on|off | |
4966 | TYPE: onoff | |
4967 | LOC: Config.onoff.log_mime_hdrs | |
4968 | DEFAULT: off | |
4969 | DOC_START | |
4970 | The Cache can record both the request and the response MIME | |
4971 | headers for each HTTP transaction. The headers are encoded | |
4972 | safely and will appear as two bracketed fields at the end of | |
4973 | the access log (for either the native or httpd-emulated log | |
4974 | formats). To enable this logging set log_mime_hdrs to 'on'. | |
4975 | DOC_END | |
5473c134 | 4976 | |
41bd17a4 | 4977 | NAME: pid_filename |
4978 | TYPE: string | |
4979 | DEFAULT: @DEFAULT_PID_FILE@ | |
4980 | LOC: Config.pidFilename | |
5473c134 | 4981 | DOC_START |
41bd17a4 | 4982 | A filename to write the process-id to. To disable, enter "none". |
5473c134 | 4983 | DOC_END |
4984 | ||
41bd17a4 | 4985 | NAME: client_netmask |
4986 | TYPE: address | |
4987 | LOC: Config.Addrs.client_netmask | |
0eb08770 | 4988 | DEFAULT: no_addr |
638402dd | 4989 | DEFAULT_DOC: Log full client IP address |
5473c134 | 4990 | DOC_START |
41bd17a4 | 4991 | A netmask for client addresses in logfiles and cachemgr output. |
4992 | Change this to protect the privacy of your cache clients. | |
4993 | A netmask of 255.255.255.0 will log all IP's in that range with | |
4994 | the last digit set to '0'. | |
5473c134 | 4995 | DOC_END |
4996 | ||
41bd17a4 | 4997 | NAME: strip_query_terms |
5473c134 | 4998 | TYPE: onoff |
41bd17a4 | 4999 | LOC: Config.onoff.strip_query_terms |
5473c134 | 5000 | DEFAULT: on |
5001 | DOC_START | |
41bd17a4 | 5002 | By default, Squid strips query terms from requested URLs before |
638402dd AJ |
5003 | logging. This protects your user's privacy and reduces log size. |
5004 | ||
5005 | When investigating HIT/MISS or other caching behaviour you | |
5006 | will need to disable this to see the full URL used by Squid. | |
5473c134 | 5007 | DOC_END |
5008 | ||
41bd17a4 | 5009 | NAME: buffered_logs |
5010 | COMMENT: on|off | |
5011 | TYPE: onoff | |
5012 | DEFAULT: off | |
5013 | LOC: Config.onoff.buffered_logs | |
5473c134 | 5014 | DOC_START |
638402dd AJ |
5015 | Whether to write/send access_log records ASAP or accumulate them and |
5016 | then write/send them in larger chunks. Buffering may improve | |
5017 | performance because it decreases the number of I/Os. However, | |
5018 | buffering increases the delay before log records become available to | |
5019 | the final recipient (e.g., a disk file or logging daemon) and, | |
5020 | hence, increases the risk of log records loss. | |
5021 | ||
5022 | Note that even when buffered_logs are off, Squid may have to buffer | |
5023 | records if it cannot write/send them immediately due to pending I/Os | |
5024 | (e.g., the I/O writing the previous log record) or connectivity loss. | |
5025 | ||
fb0c2f17 | 5026 | Currently honored by 'daemon' and 'tcp' access_log modules only. |
6b698a21 | 5027 | DOC_END |
0976f8db | 5028 | |
2b753521 | 5029 | NAME: netdb_filename |
5030 | TYPE: string | |
221faecb | 5031 | DEFAULT: stdio:@DEFAULT_NETDB_FILE@ |
2b753521 | 5032 | LOC: Config.netdbFilename |
fb6a61d1 | 5033 | IFDEF: USE_ICMP |
2b753521 | 5034 | DOC_START |
638402dd AJ |
5035 | Where Squid stores it's netdb journal. |
5036 | When enabled this journal preserves netdb state between restarts. | |
5037 | ||
2b753521 | 5038 | To disable, enter "none". |
5039 | DOC_END | |
5040 | ||
62493678 AJ |
5041 | COMMENT_START |
5042 | OPTIONS FOR TROUBLESHOOTING | |
5043 | ----------------------------------------------------------------------------- | |
5044 | COMMENT_END | |
5045 | ||
5046 | NAME: cache_log | |
5047 | TYPE: string | |
62493678 AJ |
5048 | DEFAULT_IF_NONE: @DEFAULT_CACHE_LOG@ |
5049 | LOC: Debug::cache_log | |
5050 | DOC_START | |
638402dd AJ |
5051 | Squid administrative logging file. |
5052 | ||
5053 | This is where general information about Squid behavior goes. You can | |
5054 | increase the amount of data logged to this file and how often it is | |
5055 | rotated with "debug_options" | |
62493678 AJ |
5056 | DOC_END |
5057 | ||
5058 | NAME: debug_options | |
5059 | TYPE: eol | |
47df1aa7 | 5060 | DEFAULT: ALL,1 |
638402dd | 5061 | DEFAULT_DOC: Log all critical and important messages. |
62493678 AJ |
5062 | LOC: Debug::debugOptions |
5063 | DOC_START | |
5064 | Logging options are set as section,level where each source file | |
5065 | is assigned a unique section. Lower levels result in less | |
5066 | output, Full debugging (level 9) can result in a very large | |
5067 | log file, so be careful. | |
5068 | ||
5069 | The magic word "ALL" sets debugging levels for all sections. | |
638402dd | 5070 | The default is to run with "ALL,1" to record important warnings. |
62493678 | 5071 | |
47df1aa7 AJ |
5072 | The rotate=N option can be used to keep more or less of these logs |
5073 | than would otherwise be kept by logfile_rotate. | |
62493678 AJ |
5074 | For most uses a single log should be enough to monitor current |
5075 | events affecting Squid. | |
5076 | DOC_END | |
5077 | ||
5078 | NAME: coredump_dir | |
5079 | TYPE: string | |
5080 | LOC: Config.coredump_dir | |
62493678 | 5081 | DEFAULT_IF_NONE: none |
638402dd | 5082 | DEFAULT_DOC: Use the directory from where Squid was started. |
62493678 AJ |
5083 | DOC_START |
5084 | By default Squid leaves core files in the directory from where | |
5085 | it was started. If you set 'coredump_dir' to a directory | |
5086 | that exists, Squid will chdir() to that directory at startup | |
5087 | and coredump files will be left there. | |
5088 | ||
5089 | NOCOMMENT_START | |
e0855596 | 5090 | |
62493678 AJ |
5091 | # Leave coredumps in the first cache dir |
5092 | coredump_dir @DEFAULT_SWAP_DIR@ | |
5093 | NOCOMMENT_END | |
5094 | DOC_END | |
5095 | ||
5096 | ||
41bd17a4 | 5097 | COMMENT_START |
5098 | OPTIONS FOR FTP GATEWAYING | |
5099 | ----------------------------------------------------------------------------- | |
5100 | COMMENT_END | |
5101 | ||
5102 | NAME: ftp_user | |
5103 | TYPE: string | |
5104 | DEFAULT: Squid@ | |
5105 | LOC: Config.Ftp.anon_user | |
6b698a21 | 5106 | DOC_START |
41bd17a4 | 5107 | If you want the anonymous login password to be more informative |
638402dd | 5108 | (and enable the use of picky FTP servers), set this to something |
41bd17a4 | 5109 | reasonable for your domain, like wwwuser@somewhere.net |
7f7db318 | 5110 | |
41bd17a4 | 5111 | The reason why this is domainless by default is the |
5112 | request can be made on the behalf of a user in any domain, | |
5113 | depending on how the cache is used. | |
638402dd | 5114 | Some FTP server also validate the email address is valid |
41bd17a4 | 5115 | (for example perl.com). |
6b698a21 | 5116 | DOC_END |
0976f8db | 5117 | |
41bd17a4 | 5118 | NAME: ftp_passive |
5119 | TYPE: onoff | |
5120 | DEFAULT: on | |
5121 | LOC: Config.Ftp.passive | |
6b698a21 | 5122 | DOC_START |
41bd17a4 | 5123 | If your firewall does not allow Squid to use passive |
5124 | connections, turn off this option. | |
a689bd4e | 5125 | |
5126 | Use of ftp_epsv_all option requires this to be ON. | |
5127 | DOC_END | |
5128 | ||
5129 | NAME: ftp_epsv_all | |
5130 | TYPE: onoff | |
5131 | DEFAULT: off | |
5132 | LOC: Config.Ftp.epsv_all | |
5133 | DOC_START | |
5134 | FTP Protocol extensions permit the use of a special "EPSV ALL" command. | |
5135 | ||
5136 | NATs may be able to put the connection on a "fast path" through the | |
5137 | translator, as the EPRT command will never be used and therefore, | |
5138 | translation of the data portion of the segments will never be needed. | |
5139 | ||
b3567eb5 FC |
5140 | When a client only expects to do two-way FTP transfers this may be |
5141 | useful. | |
a689bd4e | 5142 | If squid finds that it must do a three-way FTP transfer after issuing |
5143 | an EPSV ALL command, the FTP session will fail. | |
5144 | ||
5145 | If you have any doubts about this option do not use it. | |
5146 | Squid will nicely attempt all other connection methods. | |
5147 | ||
51ee534d AJ |
5148 | Requires ftp_passive to be ON (default) for any effect. |
5149 | DOC_END | |
5150 | ||
5151 | NAME: ftp_epsv | |
ddf5aa2b CT |
5152 | TYPE: ftp_epsv |
5153 | DEFAULT: none | |
5154 | LOC: Config.accessList.ftp_epsv | |
51ee534d AJ |
5155 | DOC_START |
5156 | FTP Protocol extensions permit the use of a special "EPSV" command. | |
5157 | ||
5158 | NATs may be able to put the connection on a "fast path" through the | |
b3567eb5 FC |
5159 | translator using EPSV, as the EPRT command will never be used |
5160 | and therefore, translation of the data portion of the segments | |
5161 | will never be needed. | |
51ee534d | 5162 | |
ddf5aa2b CT |
5163 | EPSV is often required to interoperate with FTP servers on IPv6 |
5164 | networks. On the other hand, it may break some IPv4 servers. | |
5165 | ||
5166 | By default, EPSV may try EPSV with any FTP server. To fine tune | |
5167 | that decision, you may restrict EPSV to certain clients or servers | |
5168 | using ACLs: | |
5169 | ||
5170 | ftp_epsv allow|deny al1 acl2 ... | |
5171 | ||
5172 | WARNING: Disabling EPSV may cause problems with external NAT and IPv6. | |
51ee534d | 5173 | |
ddf5aa2b | 5174 | Only fast ACLs are supported. |
51ee534d | 5175 | Requires ftp_passive to be ON (default) for any effect. |
41bd17a4 | 5176 | DOC_END |
9e7dbc51 | 5177 | |
63ee5443 AJ |
5178 | NAME: ftp_eprt |
5179 | TYPE: onoff | |
5180 | DEFAULT: on | |
5181 | LOC: Config.Ftp.eprt | |
5182 | DOC_START | |
5183 | FTP Protocol extensions permit the use of a special "EPRT" command. | |
5184 | ||
5185 | This extension provides a protocol neutral alternative to the | |
5186 | IPv4-only PORT command. When supported it enables active FTP data | |
5187 | channels over IPv6 and efficient NAT handling. | |
5188 | ||
5189 | Turning this OFF will prevent EPRT being attempted and will skip | |
5190 | straight to using PORT for IPv4 servers. | |
5191 | ||
5192 | Some devices are known to not handle this extension correctly and | |
5193 | may result in crashes. Devices which suport EPRT enough to fail | |
5194 | cleanly will result in Squid attempting PORT anyway. This directive | |
5195 | should only be disabled when EPRT results in device failures. | |
5196 | ||
5197 | WARNING: Doing so will convert Squid back to the old behavior with all | |
5198 | the related problems with external NAT devices/layers and IPv4-only FTP. | |
5199 | DOC_END | |
5200 | ||
41bd17a4 | 5201 | NAME: ftp_sanitycheck |
5202 | TYPE: onoff | |
5203 | DEFAULT: on | |
5204 | LOC: Config.Ftp.sanitycheck | |
5205 | DOC_START | |
5206 | For security and data integrity reasons Squid by default performs | |
5207 | sanity checks of the addresses of FTP data connections ensure the | |
5208 | data connection is to the requested server. If you need to allow | |
5209 | FTP connections to servers using another IP address for the data | |
5210 | connection turn this off. | |
5211 | DOC_END | |
9e7dbc51 | 5212 | |
41bd17a4 | 5213 | NAME: ftp_telnet_protocol |
5214 | TYPE: onoff | |
5215 | DEFAULT: on | |
5216 | LOC: Config.Ftp.telnet | |
5217 | DOC_START | |
5218 | The FTP protocol is officially defined to use the telnet protocol | |
5219 | as transport channel for the control connection. However, many | |
5220 | implementations are broken and does not respect this aspect of | |
5221 | the FTP protocol. | |
5222 | ||
5223 | If you have trouble accessing files with ASCII code 255 in the | |
5224 | path or similar problems involving this ASCII code you can | |
5225 | try setting this directive to off. If that helps, report to the | |
5226 | operator of the FTP server in question that their FTP server | |
5227 | is broken and does not follow the FTP standard. | |
5228 | DOC_END | |
5229 | ||
5230 | COMMENT_START | |
5231 | OPTIONS FOR EXTERNAL SUPPORT PROGRAMS | |
5232 | ----------------------------------------------------------------------------- | |
5233 | COMMENT_END | |
5234 | ||
5235 | NAME: diskd_program | |
5236 | TYPE: string | |
5237 | DEFAULT: @DEFAULT_DISKD@ | |
5238 | LOC: Config.Program.diskd | |
5239 | DOC_START | |
5240 | Specify the location of the diskd executable. | |
5241 | Note this is only useful if you have compiled in | |
5242 | diskd as one of the store io modules. | |
5243 | DOC_END | |
5244 | ||
5245 | NAME: unlinkd_program | |
5246 | IFDEF: USE_UNLINKD | |
5247 | TYPE: string | |
5248 | DEFAULT: @DEFAULT_UNLINKD@ | |
5249 | LOC: Config.Program.unlinkd | |
5250 | DOC_START | |
5251 | Specify the location of the executable for file deletion process. | |
5252 | DOC_END | |
5253 | ||
5254 | NAME: pinger_program | |
41bd17a4 | 5255 | IFDEF: USE_ICMP |
7a9d36e3 AJ |
5256 | TYPE: icmp |
5257 | DEFAULT: @DEFAULT_PINGER@ | |
5258 | LOC: IcmpCfg | |
41bd17a4 | 5259 | DOC_START |
5260 | Specify the location of the executable for the pinger process. | |
5261 | DOC_END | |
5262 | ||
cc192b50 | 5263 | NAME: pinger_enable |
5264 | TYPE: onoff | |
5265 | DEFAULT: on | |
7a9d36e3 | 5266 | LOC: IcmpCfg.enable |
cc192b50 | 5267 | IFDEF: USE_ICMP |
5268 | DOC_START | |
5269 | Control whether the pinger is active at run-time. | |
b3567eb5 FC |
5270 | Enables turning ICMP pinger on and off with a simple |
5271 | squid -k reconfigure. | |
cc192b50 | 5272 | DOC_END |
5273 | ||
5274 | ||
41bd17a4 | 5275 | COMMENT_START |
5276 | OPTIONS FOR URL REWRITING | |
5277 | ----------------------------------------------------------------------------- | |
5278 | COMMENT_END | |
5279 | ||
5280 | NAME: url_rewrite_program redirect_program | |
5281 | TYPE: wordlist | |
5282 | LOC: Config.Program.redirect | |
5283 | DEFAULT: none | |
5284 | DOC_START | |
2c7aad89 | 5285 | Specify the location of the executable URL rewriter to use. |
41bd17a4 | 5286 | Since they can perform almost any function there isn't one included. |
5287 | ||
2c7aad89 | 5288 | For each requested URL, the rewriter will receive on line with the format |
41bd17a4 | 5289 | |
b11724bb | 5290 | [channel-ID <SP>] URL [<SP> extras]<NL> |
5269ec0e | 5291 | |
457857fe CT |
5292 | See url_rewrite_extras on how to send "extras" with optional values to |
5293 | the helper. | |
5269ec0e AJ |
5294 | After processing the request the helper must reply using the following format: |
5295 | ||
24eac830 | 5296 | [channel-ID <SP>] result [<SP> kv-pairs] |
5269ec0e AJ |
5297 | |
5298 | The result code can be: | |
5299 | ||
5300 | OK status=30N url="..." | |
5301 | Redirect the URL to the one supplied in 'url='. | |
5302 | 'status=' is optional and contains the status code to send | |
5303 | the client in Squids HTTP response. It must be one of the | |
5304 | HTTP redirect status codes: 301, 302, 303, 307, 308. | |
5305 | When no status is given Squid will use 302. | |
c71adec1 | 5306 | |
5269ec0e AJ |
5307 | OK rewrite-url="..." |
5308 | Rewrite the URL to the one supplied in 'rewrite-url='. | |
5309 | The new URL is fetched directly by Squid and returned to | |
5310 | the client as the response to its request. | |
5311 | ||
c2cbbb02 AJ |
5312 | OK |
5313 | When neither of url= and rewrite-url= are sent Squid does | |
5314 | not change the URL. | |
5315 | ||
5269ec0e AJ |
5316 | ERR |
5317 | Do not change the URL. | |
5318 | ||
5319 | BH | |
4ded749e | 5320 | An internal error occurred in the helper, preventing |
c2cbbb02 AJ |
5321 | a result being identified. The 'message=' key name is |
5322 | reserved for delivering a log message. | |
5269ec0e AJ |
5323 | |
5324 | ||
457857fe CT |
5325 | In addition to the above kv-pairs Squid also understands the following |
5326 | optional kv-pairs received from URL rewriters: | |
5327 | clt_conn_tag=TAG | |
5328 | Associates a TAG with the client TCP connection. | |
5329 | The TAG is treated as a regular annotation but persists across | |
5330 | future requests on the client connection rather than just the | |
5331 | current request. A helper may update the TAG during subsequent | |
5332 | requests be returning a new kv-pair. | |
41bd17a4 | 5333 | |
5269ec0e AJ |
5334 | When using the concurrency= option the protocol is changed by |
5335 | introducing a query channel tag in front of the request/response. | |
5336 | The query channel tag is a number between 0 and concurrency-1. | |
5337 | This value must be echoed back unchanged to Squid as the first part | |
5338 | of the response relating to its request. | |
5339 | ||
5340 | WARNING: URL re-writing ability should be avoided whenever possible. | |
5341 | Use the URL redirect form of response instead. | |
41bd17a4 | 5342 | |
5269ec0e AJ |
5343 | Re-write creates a difference in the state held by the client |
5344 | and server. Possibly causing confusion when the server response | |
5345 | contains snippets of its view state. Embeded URLs, response | |
5346 | and content Location headers, etc. are not re-written by this | |
5347 | interface. | |
41bd17a4 | 5348 | |
5349 | By default, a URL rewriter is not used. | |
5350 | DOC_END | |
5351 | ||
5352 | NAME: url_rewrite_children redirect_children | |
48d54e4d | 5353 | TYPE: HelperChildConfig |
5b708d95 | 5354 | DEFAULT: 20 startup=0 idle=1 concurrency=0 |
41bd17a4 | 5355 | LOC: Config.redirectChildren |
5356 | DOC_START | |
48d54e4d AJ |
5357 | The maximum number of redirector processes to spawn. If you limit |
5358 | it too few Squid will have to wait for them to process a backlog of | |
5359 | URLs, slowing it down. If you allow too many they will use RAM | |
5360 | and other system resources noticably. | |
5361 | ||
5362 | The startup= and idle= options allow some measure of skew in your | |
5363 | tuning. | |
5364 | ||
5365 | startup= | |
5366 | ||
5367 | Sets a minimum of how many processes are to be spawned when Squid | |
5368 | starts or reconfigures. When set to zero the first request will | |
5369 | cause spawning of the first child process to handle it. | |
5370 | ||
5371 | Starting too few will cause an initial slowdown in traffic as Squid | |
5372 | attempts to simultaneously spawn enough processes to cope. | |
5373 | ||
5374 | idle= | |
5375 | ||
5376 | Sets a minimum of how many processes Squid is to try and keep available | |
5377 | at all times. When traffic begins to rise above what the existing | |
5378 | processes can handle this many more will be spawned up to the maximum | |
5379 | configured. A minimum setting of 1 is required. | |
5380 | ||
5381 | concurrency= | |
41bd17a4 | 5382 | |
41bd17a4 | 5383 | The number of requests each redirector helper can handle in |
5384 | parallel. Defaults to 0 which indicates the redirector | |
5385 | is a old-style single threaded redirector. | |
6a171502 AJ |
5386 | |
5387 | When this directive is set to a value >= 1 then the protocol | |
5388 | used to communicate with the helper is modified to include | |
9bef05b1 AJ |
5389 | an ID in front of the request/response. The ID from the request |
5390 | must be echoed back with the response to that request. | |
6825b101 CT |
5391 | |
5392 | queue-size=N | |
5393 | ||
6082a0e2 EB |
5394 | Sets the maximum number of queued requests to N. The default maximum |
5395 | is 2*numberofchildren. If the queued requests exceed queue size and | |
5396 | redirector_bypass configuration option is set, then redirector is bypassed. | |
5397 | Otherwise, Squid is allowed to temporarily exceed the configured maximum, | |
5398 | marking the affected helper as "overloaded". If the helper overload lasts | |
5399 | more than 3 minutes, the action prescribed by the on-persistent-overload | |
5400 | option applies. | |
5401 | ||
5402 | on-persistent-overload=action | |
5403 | ||
5404 | Specifies Squid reaction to a new helper request arriving when the helper | |
5405 | has been overloaded for more that 3 minutes already. The number of queued | |
5406 | requests determines whether the helper is overloaded (see the queue-size | |
5407 | option). | |
5408 | ||
5409 | Two actions are supported: | |
5410 | ||
5411 | die Squid worker quits. This is the default behavior. | |
5412 | ||
5413 | ERR Squid treats the helper request as if it was | |
5414 | immediately submitted, and the helper immediately | |
5415 | replied with an ERR response. This action has no effect | |
5416 | on the already queued and in-progress helper requests. | |
41bd17a4 | 5417 | DOC_END |
5418 | ||
5419 | NAME: url_rewrite_host_header redirect_rewrites_host_header | |
5420 | TYPE: onoff | |
5421 | DEFAULT: on | |
5422 | LOC: Config.onoff.redir_rewrites_host | |
5423 | DOC_START | |
3ce33807 AJ |
5424 | To preserve same-origin security policies in browsers and |
5425 | prevent Host: header forgery by redirectors Squid rewrites | |
5426 | any Host: header in redirected requests. | |
5427 | ||
5428 | If you are running an accelerator this may not be a wanted | |
5429 | effect of a redirector. This directive enables you disable | |
5430 | Host: alteration in reverse-proxy traffic. | |
5431 | ||
41bd17a4 | 5432 | WARNING: Entries are cached on the result of the URL rewriting |
5433 | process, so be careful if you have domain-virtual hosts. | |
3ce33807 AJ |
5434 | |
5435 | WARNING: Squid and other software verifies the URL and Host | |
5436 | are matching, so be careful not to relay through other proxies | |
5437 | or inspecting firewalls with this disabled. | |
41bd17a4 | 5438 | DOC_END |
5439 | ||
5440 | NAME: url_rewrite_access redirector_access | |
5441 | TYPE: acl_access | |
5442 | DEFAULT: none | |
638402dd | 5443 | DEFAULT_DOC: Allow, unless rules exist in squid.conf. |
41bd17a4 | 5444 | LOC: Config.accessList.redirector |
5445 | DOC_START | |
5446 | If defined, this access list specifies which requests are | |
638402dd | 5447 | sent to the redirector processes. |
b3567eb5 FC |
5448 | |
5449 | This clause supports both fast and slow acl types. | |
5450 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
41bd17a4 | 5451 | DOC_END |
5452 | ||
5453 | NAME: url_rewrite_bypass redirector_bypass | |
5454 | TYPE: onoff | |
5455 | LOC: Config.onoff.redirector_bypass | |
5456 | DEFAULT: off | |
5457 | DOC_START | |
5458 | When this is 'on', a request will not go through the | |
6082a0e2 EB |
5459 | redirector if all the helpers are busy. If this is 'off' and the |
5460 | redirector queue grows too large, the action is prescribed by the | |
5461 | on-persistent-overload option. You should only enable this if the | |
5462 | redirectors are not critical to your caching system. If you use | |
41bd17a4 | 5463 | redirectors for access control, and you enable this option, |
5464 | users may have access to pages they should not | |
5465 | be allowed to request. | |
6825b101 CT |
5466 | This options sets default queue-size option of the url_rewrite_children |
5467 | to 0. | |
41bd17a4 | 5468 | DOC_END |
5469 | ||
fe7966ec | 5470 | NAME: url_rewrite_extras |
b11724bb CT |
5471 | TYPE: TokenOrQuotedString |
5472 | LOC: Config.redirector_extras | |
5473 | DEFAULT: "%>a/%>A %un %>rm myip=%la myport=%lp" | |
5474 | DOC_START | |
5475 | Specifies a string to be append to request line format for the | |
5476 | rewriter helper. "Quoted" format values may contain spaces and | |
5477 | logformat %macros. In theory, any logformat %macro can be used. | |
5478 | In practice, a %macro expands as a dash (-) if the helper request is | |
5479 | sent before the required macro information is available to Squid. | |
5480 | DOC_END | |
5481 | ||
32fd6d8a | 5482 | NAME: url_rewrite_timeout |
ced8def3 AJ |
5483 | TYPE: UrlHelperTimeout |
5484 | LOC: Config.onUrlRewriteTimeout | |
32fd6d8a CT |
5485 | DEFAULT: none |
5486 | DEFAULT_DOC: Squid waits for the helper response forever | |
5487 | DOC_START | |
5488 | Squid times active requests to redirector. The timeout value and Squid | |
5489 | reaction to a timed out request are configurable using the following | |
5490 | format: | |
5491 | ||
ced8def3 | 5492 | url_rewrite_timeout timeout time-units on_timeout=<action> [response=<quoted-response>] |
32fd6d8a CT |
5493 | |
5494 | supported timeout actions: | |
ced8def3 | 5495 | fail Squid return a ERR_GATEWAY_FAILURE error page |
32fd6d8a | 5496 | |
ced8def3 | 5497 | bypass Do not re-write the URL |
32fd6d8a | 5498 | |
ced8def3 | 5499 | retry Send the lookup to the helper again |
32fd6d8a | 5500 | |
ced8def3 AJ |
5501 | use_configured_response |
5502 | Use the <quoted-response> as helper response | |
32fd6d8a CT |
5503 | DOC_END |
5504 | ||
a8a0b1c2 EC |
5505 | COMMENT_START |
5506 | OPTIONS FOR STORE ID | |
5507 | ----------------------------------------------------------------------------- | |
5508 | COMMENT_END | |
5509 | ||
5510 | NAME: store_id_program storeurl_rewrite_program | |
5511 | TYPE: wordlist | |
5512 | LOC: Config.Program.store_id | |
5513 | DEFAULT: none | |
5514 | DOC_START | |
5515 | Specify the location of the executable StoreID helper to use. | |
5516 | Since they can perform almost any function there isn't one included. | |
5517 | ||
5518 | For each requested URL, the helper will receive one line with the format | |
5519 | ||
b11724bb | 5520 | [channel-ID <SP>] URL [<SP> extras]<NL> |
a8a0b1c2 EC |
5521 | |
5522 | ||
5523 | After processing the request the helper must reply using the following format: | |
5524 | ||
5525 | [channel-ID <SP>] result [<SP> kv-pairs] | |
5526 | ||
5527 | The result code can be: | |
5528 | ||
5529 | OK store-id="..." | |
5530 | Use the StoreID supplied in 'store-id='. | |
5531 | ||
5532 | ERR | |
5533 | The default is to use HTTP request URL as the store ID. | |
5534 | ||
5535 | BH | |
5536 | An internal error occured in the helper, preventing | |
5537 | a result being identified. | |
5538 | ||
457857fe CT |
5539 | In addition to the above kv-pairs Squid also understands the following |
5540 | optional kv-pairs received from URL rewriters: | |
5541 | clt_conn_tag=TAG | |
5542 | Associates a TAG with the client TCP connection. | |
5543 | Please see url_rewrite_program related documentation for this | |
5544 | kv-pair | |
a8a0b1c2 | 5545 | |
b11724bb CT |
5546 | Helper programs should be prepared to receive and possibly ignore |
5547 | additional whitespace-separated tokens on each input line. | |
a8a0b1c2 EC |
5548 | |
5549 | When using the concurrency= option the protocol is changed by | |
5550 | introducing a query channel tag in front of the request/response. | |
5551 | The query channel tag is a number between 0 and concurrency-1. | |
5552 | This value must be echoed back unchanged to Squid as the first part | |
5553 | of the response relating to its request. | |
5554 | ||
5555 | NOTE: when using StoreID refresh_pattern will apply to the StoreID | |
5556 | returned from the helper and not the URL. | |
5557 | ||
5558 | WARNING: Wrong StoreID value returned by a careless helper may result | |
5559 | in the wrong cached response returned to the user. | |
5560 | ||
5561 | By default, a StoreID helper is not used. | |
5562 | DOC_END | |
5563 | ||
fe7966ec | 5564 | NAME: store_id_extras |
b11724bb CT |
5565 | TYPE: TokenOrQuotedString |
5566 | LOC: Config.storeId_extras | |
5567 | DEFAULT: "%>a/%>A %un %>rm myip=%la myport=%lp" | |
5568 | DOC_START | |
5569 | Specifies a string to be append to request line format for the | |
5570 | StoreId helper. "Quoted" format values may contain spaces and | |
5571 | logformat %macros. In theory, any logformat %macro can be used. | |
5572 | In practice, a %macro expands as a dash (-) if the helper request is | |
5573 | sent before the required macro information is available to Squid. | |
5574 | DOC_END | |
5575 | ||
a8a0b1c2 EC |
5576 | NAME: store_id_children storeurl_rewrite_children |
5577 | TYPE: HelperChildConfig | |
5578 | DEFAULT: 20 startup=0 idle=1 concurrency=0 | |
5579 | LOC: Config.storeIdChildren | |
5580 | DOC_START | |
5581 | The maximum number of StoreID helper processes to spawn. If you limit | |
5582 | it too few Squid will have to wait for them to process a backlog of | |
5583 | requests, slowing it down. If you allow too many they will use RAM | |
5584 | and other system resources noticably. | |
5585 | ||
5586 | The startup= and idle= options allow some measure of skew in your | |
5587 | tuning. | |
5588 | ||
5589 | startup= | |
5590 | ||
5591 | Sets a minimum of how many processes are to be spawned when Squid | |
5592 | starts or reconfigures. When set to zero the first request will | |
5593 | cause spawning of the first child process to handle it. | |
5594 | ||
5595 | Starting too few will cause an initial slowdown in traffic as Squid | |
5596 | attempts to simultaneously spawn enough processes to cope. | |
5597 | ||
5598 | idle= | |
5599 | ||
5600 | Sets a minimum of how many processes Squid is to try and keep available | |
5601 | at all times. When traffic begins to rise above what the existing | |
5602 | processes can handle this many more will be spawned up to the maximum | |
5603 | configured. A minimum setting of 1 is required. | |
5604 | ||
5605 | concurrency= | |
5606 | ||
5607 | The number of requests each storeID helper can handle in | |
5608 | parallel. Defaults to 0 which indicates the helper | |
5609 | is a old-style single threaded program. | |
5610 | ||
5611 | When this directive is set to a value >= 1 then the protocol | |
5612 | used to communicate with the helper is modified to include | |
5613 | an ID in front of the request/response. The ID from the request | |
5614 | must be echoed back with the response to that request. | |
6825b101 CT |
5615 | |
5616 | queue-size=N | |
5617 | ||
6082a0e2 EB |
5618 | Sets the maximum number of queued requests to N. The default maximum |
5619 | is 2*numberofchildren. If the queued requests exceed queue size and | |
5620 | redirector_bypass configuration option is set, then redirector is bypassed. | |
5621 | Otherwise, Squid is allowed to temporarily exceed the configured maximum, | |
5622 | marking the affected helper as "overloaded". If the helper overload lasts | |
5623 | more than 3 minutes, the action prescribed by the on-persistent-overload | |
5624 | option applies. | |
5625 | ||
5626 | on-persistent-overload=action | |
5627 | ||
5628 | Specifies Squid reaction to a new helper request arriving when the helper | |
5629 | has been overloaded for more that 3 minutes already. The number of queued | |
5630 | requests determines whether the helper is overloaded (see the queue-size | |
5631 | option). | |
5632 | ||
5633 | Two actions are supported: | |
5634 | ||
5635 | die Squid worker quits. This is the default behavior. | |
5636 | ||
5637 | ERR Squid treats the helper request as if it was | |
5638 | immediately submitted, and the helper immediately | |
5639 | replied with an ERR response. This action has no effect | |
5640 | on the already queued and in-progress helper requests. | |
a8a0b1c2 EC |
5641 | DOC_END |
5642 | ||
5643 | NAME: store_id_access storeurl_rewrite_access | |
5644 | TYPE: acl_access | |
5645 | DEFAULT: none | |
638402dd | 5646 | DEFAULT_DOC: Allow, unless rules exist in squid.conf. |
a8a0b1c2 EC |
5647 | LOC: Config.accessList.store_id |
5648 | DOC_START | |
5649 | If defined, this access list specifies which requests are | |
5650 | sent to the StoreID processes. By default all requests | |
5651 | are sent. | |
5652 | ||
5653 | This clause supports both fast and slow acl types. | |
5654 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
5655 | DOC_END | |
5656 | ||
5657 | NAME: store_id_bypass storeurl_rewrite_bypass | |
5658 | TYPE: onoff | |
5659 | LOC: Config.onoff.store_id_bypass | |
5660 | DEFAULT: on | |
5661 | DOC_START | |
5662 | When this is 'on', a request will not go through the | |
6082a0e2 EB |
5663 | helper if all helpers are busy. If this is 'off' and the helper |
5664 | queue grows too large, the action is prescribed by the | |
5665 | on-persistent-overload option. You should only enable this if the | |
5666 | helpers are not critical to your caching system. If you use | |
a8a0b1c2 EC |
5667 | helpers for critical caching components, and you enable this |
5668 | option, users may not get objects from cache. | |
6825b101 CT |
5669 | This options sets default queue-size option of the store_id_children |
5670 | to 0. | |
a8a0b1c2 EC |
5671 | DOC_END |
5672 | ||
41bd17a4 | 5673 | COMMENT_START |
5674 | OPTIONS FOR TUNING THE CACHE | |
5675 | ----------------------------------------------------------------------------- | |
5676 | COMMENT_END | |
5677 | ||
f04b37d8 | 5678 | NAME: cache no_cache |
5679 | TYPE: acl_access | |
5680 | DEFAULT: none | |
70706149 | 5681 | DEFAULT_DOC: By default, this directive is unused and has no effect. |
f04b37d8 | 5682 | LOC: Config.accessList.noCache |
41bd17a4 | 5683 | DOC_START |
70706149 AR |
5684 | Requests denied by this directive will not be served from the cache |
5685 | and their responses will not be stored in the cache. This directive | |
5686 | has no effect on other transactions and on already cached responses. | |
f04b37d8 | 5687 | |
b3567eb5 FC |
5688 | This clause supports both fast and slow acl types. |
5689 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
70706149 AR |
5690 | |
5691 | This and the two other similar caching directives listed below are | |
5692 | checked at different transaction processing stages, have different | |
5693 | access to response information, affect different cache operations, | |
5694 | and differ in slow ACLs support: | |
5695 | ||
5696 | * cache: Checked before Squid makes a hit/miss determination. | |
5697 | No access to reply information! | |
5698 | Denies both serving a hit and storing a miss. | |
5699 | Supports both fast and slow ACLs. | |
5700 | * send_hit: Checked after a hit was detected. | |
5701 | Has access to reply (hit) information. | |
5702 | Denies serving a hit only. | |
5703 | Supports fast ACLs only. | |
5704 | * store_miss: Checked before storing a cachable miss. | |
5705 | Has access to reply (miss) information. | |
5706 | Denies storing a miss only. | |
5707 | Supports fast ACLs only. | |
5708 | ||
5709 | If you are not sure which of the three directives to use, apply the | |
5710 | following decision logic: | |
5711 | ||
5712 | * If your ACL(s) are of slow type _and_ need response info, redesign. | |
5713 | Squid does not support that particular combination at this time. | |
5714 | Otherwise: | |
5715 | * If your directive ACL(s) are of slow type, use "cache"; and/or | |
5716 | * if your directive ACL(s) need no response info, use "cache". | |
5717 | Otherwise: | |
5718 | * If you do not want the response cached, use store_miss; and/or | |
5719 | * if you do not want a hit on a cached response, use send_hit. | |
5720 | DOC_END | |
5721 | ||
5722 | NAME: send_hit | |
5723 | TYPE: acl_access | |
5724 | DEFAULT: none | |
5725 | DEFAULT_DOC: By default, this directive is unused and has no effect. | |
5726 | LOC: Config.accessList.sendHit | |
5727 | DOC_START | |
5728 | Responses denied by this directive will not be served from the cache | |
5729 | (but may still be cached, see store_miss). This directive has no | |
5730 | effect on the responses it allows and on the cached objects. | |
5731 | ||
5732 | Please see the "cache" directive for a summary of differences among | |
5733 | store_miss, send_hit, and cache directives. | |
5734 | ||
5735 | Unlike the "cache" directive, send_hit only supports fast acl | |
5736 | types. See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
5737 | ||
5738 | For example: | |
5739 | ||
5740 | # apply custom Store ID mapping to some URLs | |
5741 | acl MapMe dstdomain .c.example.com | |
5742 | store_id_program ... | |
5743 | store_id_access allow MapMe | |
5744 | ||
5745 | # but prevent caching of special responses | |
5746 | # such as 302 redirects that cause StoreID loops | |
5747 | acl Ordinary http_status 200-299 | |
5748 | store_miss deny MapMe !Ordinary | |
5749 | ||
5750 | # and do not serve any previously stored special responses | |
5751 | # from the cache (in case they were already cached before | |
5752 | # the above store_miss rule was in effect). | |
5753 | send_hit deny MapMe !Ordinary | |
5754 | DOC_END | |
5755 | ||
5756 | NAME: store_miss | |
5757 | TYPE: acl_access | |
5758 | DEFAULT: none | |
5759 | DEFAULT_DOC: By default, this directive is unused and has no effect. | |
5760 | LOC: Config.accessList.storeMiss | |
5761 | DOC_START | |
5762 | Responses denied by this directive will not be cached (but may still | |
5763 | be served from the cache, see send_hit). This directive has no | |
5764 | effect on the responses it allows and on the already cached responses. | |
5765 | ||
5766 | Please see the "cache" directive for a summary of differences among | |
5767 | store_miss, send_hit, and cache directives. See the | |
5768 | send_hit directive for a usage example. | |
5769 | ||
5770 | Unlike the "cache" directive, store_miss only supports fast acl | |
5771 | types. See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
41bd17a4 | 5772 | DOC_END |
5773 | ||
570d3f75 AJ |
5774 | NAME: max_stale |
5775 | COMMENT: time-units | |
5776 | TYPE: time_t | |
5777 | LOC: Config.maxStale | |
5778 | DEFAULT: 1 week | |
5779 | DOC_START | |
5780 | This option puts an upper limit on how stale content Squid | |
5781 | will serve from the cache if cache validation fails. | |
5782 | Can be overriden by the refresh_pattern max-stale option. | |
5783 | DOC_END | |
5784 | ||
41bd17a4 | 5785 | NAME: refresh_pattern |
5786 | TYPE: refreshpattern | |
5787 | LOC: Config.Refresh | |
5788 | DEFAULT: none | |
5789 | DOC_START | |
5790 | usage: refresh_pattern [-i] regex min percent max [options] | |
9e7dbc51 | 5791 | |
6b698a21 | 5792 | By default, regular expressions are CASE-SENSITIVE. To make |
5793 | them case-insensitive, use the -i option. | |
9e7dbc51 | 5794 | |
41bd17a4 | 5795 | 'Min' is the time (in minutes) an object without an explicit |
5796 | expiry time should be considered fresh. The recommended | |
5797 | value is 0, any higher values may cause dynamic applications | |
5798 | to be erroneously cached unless the application designer | |
5799 | has taken the appropriate actions. | |
9e7dbc51 | 5800 | |
41bd17a4 | 5801 | 'Percent' is a percentage of the objects age (time since last |
5802 | modification age) an object without explicit expiry time | |
5803 | will be considered fresh. | |
5b807763 | 5804 | |
41bd17a4 | 5805 | 'Max' is an upper limit on how long objects without an explicit |
6d612a9d GD |
5806 | expiry time will be considered fresh. The value is also used |
5807 | to form Cache-Control: max-age header for a request sent from | |
5808 | Squid to origin/parent. | |
9e7dbc51 | 5809 | |
41bd17a4 | 5810 | options: override-expire |
5811 | override-lastmod | |
5812 | reload-into-ims | |
5813 | ignore-reload | |
41bd17a4 | 5814 | ignore-no-store |
5815 | ignore-private | |
570d3f75 | 5816 | max-stale=NN |
41bd17a4 | 5817 | refresh-ims |
3d8b6ba4 | 5818 | store-stale |
a0ec9f68 | 5819 | |
41bd17a4 | 5820 | override-expire enforces min age even if the server |
9b2ad080 HN |
5821 | sent an explicit expiry time (e.g., with the |
5822 | Expires: header or Cache-Control: max-age). Doing this | |
5823 | VIOLATES the HTTP standard. Enabling this feature | |
5824 | could make you liable for problems which it causes. | |
6468fe10 | 5825 | |
04925576 AJ |
5826 | Note: override-expire does not enforce staleness - it only extends |
5827 | freshness / min. If the server returns a Expires time which | |
5828 | is longer than your max time, Squid will still consider | |
5829 | the object fresh for that period of time. | |
5830 | ||
41bd17a4 | 5831 | override-lastmod enforces min age even on objects |
5832 | that were modified recently. | |
934b03fc | 5833 | |
46017fdd CT |
5834 | reload-into-ims changes a client no-cache or ``reload'' |
5835 | request for a cached entry into a conditional request using | |
5836 | If-Modified-Since and/or If-None-Match headers, provided the | |
5837 | cached entry has a Last-Modified and/or a strong ETag header. | |
5838 | Doing this VIOLATES the HTTP standard. Enabling this feature | |
5839 | could make you liable for problems which it causes. | |
dba79ac5 | 5840 | |
41bd17a4 | 5841 | ignore-reload ignores a client no-cache or ``reload'' |
5842 | header. Doing this VIOLATES the HTTP standard. Enabling | |
5843 | this feature could make you liable for problems which | |
5844 | it causes. | |
9bc73deb | 5845 | |
41bd17a4 | 5846 | ignore-no-store ignores any ``Cache-control: no-store'' |
5847 | headers received from a server. Doing this VIOLATES | |
5848 | the HTTP standard. Enabling this feature could make you | |
5849 | liable for problems which it causes. | |
5850 | ||
5851 | ignore-private ignores any ``Cache-control: private'' | |
5852 | headers received from a server. Doing this VIOLATES | |
5853 | the HTTP standard. Enabling this feature could make you | |
5854 | liable for problems which it causes. | |
5855 | ||
41bd17a4 | 5856 | refresh-ims causes squid to contact the origin server |
5857 | when a client issues an If-Modified-Since request. This | |
5858 | ensures that the client will receive an updated version | |
5859 | if one is available. | |
5860 | ||
3d8b6ba4 AJ |
5861 | store-stale stores responses even if they don't have explicit |
5862 | freshness or a validator (i.e., Last-Modified or an ETag) | |
5863 | present, or if they're already stale. By default, Squid will | |
5864 | not cache such responses because they usually can't be | |
5865 | reused. Note that such responses will be stale by default. | |
5866 | ||
570d3f75 AJ |
5867 | max-stale=NN provide a maximum staleness factor. Squid won't |
5868 | serve objects more stale than this even if it failed to | |
5869 | validate the object. Default: use the max_stale global limit. | |
5870 | ||
41bd17a4 | 5871 | Basically a cached object is: |
5872 | ||
fb41bbb2 | 5873 | FRESH if expire > now, else STALE |
41bd17a4 | 5874 | STALE if age > max |
5875 | FRESH if lm-factor < percent, else STALE | |
5876 | FRESH if age < min | |
5877 | else STALE | |
5878 | ||
5879 | The refresh_pattern lines are checked in the order listed here. | |
5880 | The first entry which matches is used. If none of the entries | |
5881 | match the default will be used. | |
5882 | ||
5883 | Note, you must uncomment all the default lines if you want | |
5884 | to change one. The default setting is only active if none is | |
5885 | used. | |
5886 | ||
41bd17a4 | 5887 | NOCOMMENT_START |
e0855596 | 5888 | |
638402dd | 5889 | # |
e0855596 | 5890 | # Add any of your own refresh_pattern entries above these. |
638402dd | 5891 | # |
41bd17a4 | 5892 | refresh_pattern ^ftp: 1440 20% 10080 |
5893 | refresh_pattern ^gopher: 1440 0% 1440 | |
89db45fa | 5894 | refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 |
41bd17a4 | 5895 | refresh_pattern . 0 20% 4320 |
5896 | NOCOMMENT_END | |
5897 | DOC_END | |
5898 | ||
5899 | NAME: quick_abort_min | |
5900 | COMMENT: (KB) | |
5901 | TYPE: kb_int64_t | |
5902 | DEFAULT: 16 KB | |
5903 | LOC: Config.quickAbort.min | |
5904 | DOC_NONE | |
5905 | ||
5906 | NAME: quick_abort_max | |
5907 | COMMENT: (KB) | |
5908 | TYPE: kb_int64_t | |
5909 | DEFAULT: 16 KB | |
5910 | LOC: Config.quickAbort.max | |
5911 | DOC_NONE | |
5912 | ||
5913 | NAME: quick_abort_pct | |
5914 | COMMENT: (percent) | |
5915 | TYPE: int | |
5916 | DEFAULT: 95 | |
5917 | LOC: Config.quickAbort.pct | |
5918 | DOC_START | |
5919 | The cache by default continues downloading aborted requests | |
5920 | which are almost completed (less than 16 KB remaining). This | |
5921 | may be undesirable on slow (e.g. SLIP) links and/or very busy | |
5922 | caches. Impatient users may tie up file descriptors and | |
5923 | bandwidth by repeatedly requesting and immediately aborting | |
5924 | downloads. | |
5925 | ||
5926 | When the user aborts a request, Squid will check the | |
2d4eefd9 | 5927 | quick_abort values to the amount of data transferred until |
41bd17a4 | 5928 | then. |
5929 | ||
5930 | If the transfer has less than 'quick_abort_min' KB remaining, | |
5931 | it will finish the retrieval. | |
5932 | ||
5933 | If the transfer has more than 'quick_abort_max' KB remaining, | |
5934 | it will abort the retrieval. | |
5935 | ||
5936 | If more than 'quick_abort_pct' of the transfer has completed, | |
5937 | it will finish the retrieval. | |
5938 | ||
5939 | If you do not want any retrieval to continue after the client | |
5940 | has aborted, set both 'quick_abort_min' and 'quick_abort_max' | |
5941 | to '0 KB'. | |
5942 | ||
5943 | If you want retrievals to always continue if they are being | |
5944 | cached set 'quick_abort_min' to '-1 KB'. | |
5945 | DOC_END | |
60d096f4 | 5946 | |
41bd17a4 | 5947 | NAME: read_ahead_gap |
5948 | COMMENT: buffer-size | |
5949 | TYPE: b_int64_t | |
5950 | LOC: Config.readAheadGap | |
5951 | DEFAULT: 16 KB | |
5952 | DOC_START | |
5953 | The amount of data the cache will buffer ahead of what has been | |
5954 | sent to the client when retrieving an object from another server. | |
5955 | DOC_END | |
53e738c6 | 5956 | |
41bd17a4 | 5957 | NAME: negative_ttl |
626096be | 5958 | IFDEF: USE_HTTP_VIOLATIONS |
41bd17a4 | 5959 | COMMENT: time-units |
5960 | TYPE: time_t | |
5961 | LOC: Config.negativeTtl | |
ac9cc053 | 5962 | DEFAULT: 0 seconds |
41bd17a4 | 5963 | DOC_START |
ac9cc053 AJ |
5964 | Set the Default Time-to-Live (TTL) for failed requests. |
5965 | Certain types of failures (such as "connection refused" and | |
5966 | "404 Not Found") are able to be negatively-cached for a short time. | |
5967 | Modern web servers should provide Expires: header, however if they | |
5968 | do not this can provide a minimum TTL. | |
5969 | The default is not to cache errors with unknown expiry details. | |
5970 | ||
5971 | Note that this is different from negative caching of DNS lookups. | |
39956c7c AJ |
5972 | |
5973 | WARNING: Doing this VIOLATES the HTTP standard. Enabling | |
5974 | this feature could make you liable for problems which it | |
5975 | causes. | |
41bd17a4 | 5976 | DOC_END |
53e738c6 | 5977 | |
41bd17a4 | 5978 | NAME: positive_dns_ttl |
5979 | COMMENT: time-units | |
5980 | TYPE: time_t | |
5981 | LOC: Config.positiveDnsTtl | |
5982 | DEFAULT: 6 hours | |
5983 | DOC_START | |
5984 | Upper limit on how long Squid will cache positive DNS responses. | |
5985 | Default is 6 hours (360 minutes). This directive must be set | |
5986 | larger than negative_dns_ttl. | |
5987 | DOC_END | |
c4ab8329 | 5988 | |
41bd17a4 | 5989 | NAME: negative_dns_ttl |
5990 | COMMENT: time-units | |
5991 | TYPE: time_t | |
5992 | LOC: Config.negativeDnsTtl | |
5993 | DEFAULT: 1 minutes | |
5994 | DOC_START | |
5995 | Time-to-Live (TTL) for negative caching of failed DNS lookups. | |
5996 | This also sets the lower cache limit on positive lookups. | |
5997 | Minimum value is 1 second, and it is not recommendable to go | |
5998 | much below 10 seconds. | |
5999 | DOC_END | |
7df0bfd7 | 6000 | |
41bd17a4 | 6001 | NAME: range_offset_limit |
11e3fa1c AJ |
6002 | COMMENT: size [acl acl...] |
6003 | TYPE: acl_b_size_t | |
41bd17a4 | 6004 | LOC: Config.rangeOffsetLimit |
11e3fa1c | 6005 | DEFAULT: none |
41bd17a4 | 6006 | DOC_START |
11e3fa1c AJ |
6007 | usage: (size) [units] [[!]aclname] |
6008 | ||
6009 | Sets an upper limit on how far (number of bytes) into the file | |
6010 | a Range request may be to cause Squid to prefetch the whole file. | |
6011 | If beyond this limit, Squid forwards the Range request as it is and | |
6012 | the result is NOT cached. | |
6013 | ||
41bd17a4 | 6014 | This is to stop a far ahead range request (lets say start at 17MB) |
6015 | from making Squid fetch the whole object up to that point before | |
6016 | sending anything to the client. | |
11e3fa1c AJ |
6017 | |
6018 | Multiple range_offset_limit lines may be specified, and they will | |
6019 | be searched from top to bottom on each request until a match is found. | |
6020 | The first match found will be used. If no line matches a request, the | |
6021 | default limit of 0 bytes will be used. | |
6022 | ||
6023 | 'size' is the limit specified as a number of units. | |
6024 | ||
6025 | 'units' specifies whether to use bytes, KB, MB, etc. | |
6026 | If no units are specified bytes are assumed. | |
6027 | ||
6028 | A size of 0 causes Squid to never fetch more than the | |
ab275c7b | 6029 | client requested. (default) |
11e3fa1c AJ |
6030 | |
6031 | A size of 'none' causes Squid to always fetch the object from the | |
41bd17a4 | 6032 | beginning so it may cache the result. (2.0 style) |
11e3fa1c AJ |
6033 | |
6034 | 'aclname' is the name of a defined ACL. | |
6035 | ||
6036 | NP: Using 'none' as the byte value here will override any quick_abort settings | |
6037 | that may otherwise apply to the range request. The range request will | |
ab275c7b AJ |
6038 | be fully fetched from start to finish regardless of the client |
6039 | actions. This affects bandwidth usage. | |
41bd17a4 | 6040 | DOC_END |
d95b862f | 6041 | |
41bd17a4 | 6042 | NAME: minimum_expiry_time |
6043 | COMMENT: (seconds) | |
6044 | TYPE: time_t | |
6045 | LOC: Config.minimum_expiry_time | |
6046 | DEFAULT: 60 seconds | |
6047 | DOC_START | |
6048 | The minimum caching time according to (Expires - Date) | |
638402dd AJ |
6049 | headers Squid honors if the object can't be revalidated. |
6050 | The default is 60 seconds. | |
6051 | ||
6052 | In reverse proxy environments it might be desirable to honor | |
6053 | shorter object lifetimes. It is most likely better to make | |
6054 | your server return a meaningful Last-Modified header however. | |
6055 | ||
6056 | In ESI environments where page fragments often have short | |
6057 | lifetimes, this will often be best set to 0. | |
41bd17a4 | 6058 | DOC_END |
c68e9c6b | 6059 | |
41bd17a4 | 6060 | NAME: store_avg_object_size |
58d5c5dd DK |
6061 | COMMENT: (bytes) |
6062 | TYPE: b_int64_t | |
41bd17a4 | 6063 | DEFAULT: 13 KB |
6064 | LOC: Config.Store.avgObjectSize | |
6065 | DOC_START | |
6066 | Average object size, used to estimate number of objects your | |
6067 | cache can hold. The default is 13 KB. | |
638402dd AJ |
6068 | |
6069 | This is used to pre-seed the cache index memory allocation to | |
6070 | reduce expensive reallocate operations while handling clients | |
6071 | traffic. Too-large values may result in memory allocation during | |
6072 | peak traffic, too-small values will result in wasted memory. | |
6073 | ||
6074 | Check the cache manager 'info' report metrics for the real | |
6075 | object sizes seen by your Squid before tuning this. | |
cccac0a2 | 6076 | DOC_END |
6077 | ||
41bd17a4 | 6078 | NAME: store_objects_per_bucket |
6079 | TYPE: int | |
6080 | DEFAULT: 20 | |
6081 | LOC: Config.Store.objectsPerBucket | |
6082 | DOC_START | |
6083 | Target number of objects per bucket in the store hash table. | |
6084 | Lowering this value increases the total number of buckets and | |
6085 | also the storage maintenance rate. The default is 20. | |
6086 | DOC_END | |
6087 | ||
6088 | COMMENT_START | |
6089 | HTTP OPTIONS | |
6090 | ----------------------------------------------------------------------------- | |
6091 | COMMENT_END | |
6092 | ||
f04b37d8 | 6093 | NAME: request_header_max_size |
6094 | COMMENT: (KB) | |
6095 | TYPE: b_size_t | |
df2eec10 | 6096 | DEFAULT: 64 KB |
f04b37d8 | 6097 | LOC: Config.maxRequestHeaderSize |
6098 | DOC_START | |
6099 | This specifies the maximum size for HTTP headers in a request. | |
6100 | Request headers are usually relatively small (about 512 bytes). | |
6101 | Placing a limit on the request header size will catch certain | |
6102 | bugs (for example with persistent connections) and possibly | |
6103 | buffer-overflow or denial-of-service attacks. | |
6104 | DOC_END | |
6105 | ||
6106 | NAME: reply_header_max_size | |
6107 | COMMENT: (KB) | |
6108 | TYPE: b_size_t | |
df2eec10 | 6109 | DEFAULT: 64 KB |
f04b37d8 | 6110 | LOC: Config.maxReplyHeaderSize |
6111 | DOC_START | |
6112 | This specifies the maximum size for HTTP headers in a reply. | |
6113 | Reply headers are usually relatively small (about 512 bytes). | |
6114 | Placing a limit on the reply header size will catch certain | |
6115 | bugs (for example with persistent connections) and possibly | |
6116 | buffer-overflow or denial-of-service attacks. | |
6117 | DOC_END | |
6118 | ||
6119 | NAME: request_body_max_size | |
6120 | COMMENT: (bytes) | |
6121 | TYPE: b_int64_t | |
6122 | DEFAULT: 0 KB | |
638402dd | 6123 | DEFAULT_DOC: No limit. |
f04b37d8 | 6124 | LOC: Config.maxRequestBodySize |
6125 | DOC_START | |
6126 | This specifies the maximum size for an HTTP request body. | |
6127 | In other words, the maximum size of a PUT/POST request. | |
6128 | A user who attempts to send a request with a body larger | |
6129 | than this limit receives an "Invalid Request" error message. | |
6130 | If you set this parameter to a zero (the default), there will | |
6131 | be no limit imposed. | |
638402dd AJ |
6132 | |
6133 | See also client_request_buffer_max_size for an alternative | |
6134 | limitation on client uploads which can be configured. | |
f04b37d8 | 6135 | DOC_END |
6136 | ||
1368d115 CT |
6137 | NAME: client_request_buffer_max_size |
6138 | COMMENT: (bytes) | |
6139 | TYPE: b_size_t | |
6140 | DEFAULT: 512 KB | |
6141 | LOC: Config.maxRequestBufferSize | |
6142 | DOC_START | |
6143 | This specifies the maximum buffer size of a client request. | |
6144 | It prevents squid eating too much memory when somebody uploads | |
6145 | a large file. | |
6146 | DOC_END | |
6147 | ||
41bd17a4 | 6148 | NAME: broken_posts |
626096be | 6149 | IFDEF: USE_HTTP_VIOLATIONS |
cccac0a2 | 6150 | TYPE: acl_access |
cccac0a2 | 6151 | DEFAULT: none |
638402dd | 6152 | DEFAULT_DOC: Obey RFC 2616. |
41bd17a4 | 6153 | LOC: Config.accessList.brokenPosts |
cccac0a2 | 6154 | DOC_START |
41bd17a4 | 6155 | A list of ACL elements which, if matched, causes Squid to send |
6156 | an extra CRLF pair after the body of a PUT/POST request. | |
cccac0a2 | 6157 | |
41bd17a4 | 6158 | Some HTTP servers has broken implementations of PUT/POST, |
6159 | and rely on an extra CRLF pair sent by some WWW clients. | |
cccac0a2 | 6160 | |
41bd17a4 | 6161 | Quote from RFC2616 section 4.1 on this matter: |
cccac0a2 | 6162 | |
41bd17a4 | 6163 | Note: certain buggy HTTP/1.0 client implementations generate an |
6164 | extra CRLF's after a POST request. To restate what is explicitly | |
6165 | forbidden by the BNF, an HTTP/1.1 client must not preface or follow | |
6166 | a request with an extra CRLF. | |
cccac0a2 | 6167 | |
b3567eb5 FC |
6168 | This clause only supports fast acl types. |
6169 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
6170 | ||
41bd17a4 | 6171 | Example: |
6172 | acl buggy_server url_regex ^http://.... | |
6173 | broken_posts allow buggy_server | |
6174 | DOC_END | |
cccac0a2 | 6175 | |
22fff3bf | 6176 | NAME: adaptation_uses_indirect_client icap_uses_indirect_client |
57d76dd4 AJ |
6177 | COMMENT: on|off |
6178 | TYPE: onoff | |
22fff3bf | 6179 | IFDEF: FOLLOW_X_FORWARDED_FOR&&USE_ADAPTATION |
57d76dd4 | 6180 | DEFAULT: on |
22fff3bf | 6181 | LOC: Adaptation::Config::use_indirect_client |
57d76dd4 | 6182 | DOC_START |
ea3ae478 AR |
6183 | Controls whether the indirect client IP address (instead of the direct |
6184 | client IP address) is passed to adaptation services. | |
6185 | ||
6186 | See also: follow_x_forwarded_for adaptation_send_client_ip | |
57d76dd4 AJ |
6187 | DOC_END |
6188 | ||
41bd17a4 | 6189 | NAME: via |
626096be | 6190 | IFDEF: USE_HTTP_VIOLATIONS |
41bd17a4 | 6191 | COMMENT: on|off |
6192 | TYPE: onoff | |
6193 | DEFAULT: on | |
6194 | LOC: Config.onoff.via | |
6195 | DOC_START | |
6196 | If set (default), Squid will include a Via header in requests and | |
6197 | replies as required by RFC2616. | |
6198 | DOC_END | |
4cc6eb12 | 6199 | |
41bd17a4 | 6200 | NAME: vary_ignore_expire |
6201 | COMMENT: on|off | |
6202 | TYPE: onoff | |
6203 | LOC: Config.onoff.vary_ignore_expire | |
6204 | DEFAULT: off | |
6205 | DOC_START | |
6206 | Many HTTP servers supporting Vary gives such objects | |
6207 | immediate expiry time with no cache-control header | |
6208 | when requested by a HTTP/1.0 client. This option | |
6209 | enables Squid to ignore such expiry times until | |
6210 | HTTP/1.1 is fully implemented. | |
7e73cd78 AJ |
6211 | |
6212 | WARNING: If turned on this may eventually cause some | |
6213 | varying objects not intended for caching to get cached. | |
cccac0a2 | 6214 | DOC_END |
c4ab8329 | 6215 | |
41bd17a4 | 6216 | NAME: request_entities |
6217 | TYPE: onoff | |
6218 | LOC: Config.onoff.request_entities | |
6219 | DEFAULT: off | |
6220 | DOC_START | |
6221 | Squid defaults to deny GET and HEAD requests with request entities, | |
6222 | as the meaning of such requests are undefined in the HTTP standard | |
6223 | even if not explicitly forbidden. | |
0976f8db | 6224 | |
41bd17a4 | 6225 | Set this directive to on if you have clients which insists |
6226 | on sending request entities in GET or HEAD requests. But be warned | |
6227 | that there is server software (both proxies and web servers) which | |
6228 | can fail to properly process this kind of request which may make you | |
6229 | vulnerable to cache pollution attacks if enabled. | |
cccac0a2 | 6230 | DOC_END |
6b53c392 | 6231 | |
41bd17a4 | 6232 | NAME: request_header_access |
626096be | 6233 | IFDEF: USE_HTTP_VIOLATIONS |
3b07476b | 6234 | TYPE: http_header_access |
41bd17a4 | 6235 | LOC: Config.request_header_access |
cccac0a2 | 6236 | DEFAULT: none |
638402dd | 6237 | DEFAULT_DOC: No limits. |
cccac0a2 | 6238 | DOC_START |
41bd17a4 | 6239 | Usage: request_header_access header_name allow|deny [!]aclname ... |
0976f8db | 6240 | |
41bd17a4 | 6241 | WARNING: Doing this VIOLATES the HTTP standard. Enabling |
6242 | this feature could make you liable for problems which it | |
6243 | causes. | |
0976f8db | 6244 | |
41bd17a4 | 6245 | This option replaces the old 'anonymize_headers' and the |
6246 | older 'http_anonymizer' option with something that is much | |
3b07476b CT |
6247 | more configurable. A list of ACLs for each header name allows |
6248 | removal of specific header fields under specific conditions. | |
6249 | ||
6250 | This option only applies to outgoing HTTP request headers (i.e., | |
6251 | headers sent by Squid to the next HTTP hop such as a cache peer | |
6252 | or an origin server). The option has no effect during cache hit | |
6253 | detection. The equivalent adaptation vectoring point in ICAP | |
6254 | terminology is post-cache REQMOD. | |
6255 | ||
6256 | The option is applied to individual outgoing request header | |
6257 | fields. For each request header field F, Squid uses the first | |
6258 | qualifying sets of request_header_access rules: | |
6259 | ||
6260 | 1. Rules with header_name equal to F's name. | |
6261 | 2. Rules with header_name 'Other', provided F's name is not | |
6262 | on the hard-coded list of commonly used HTTP header names. | |
6263 | 3. Rules with header_name 'All'. | |
6264 | ||
6265 | Within that qualifying rule set, rule ACLs are checked as usual. | |
6266 | If ACLs of an "allow" rule match, the header field is allowed to | |
6267 | go through as is. If ACLs of a "deny" rule match, the header is | |
6268 | removed and request_header_replace is then checked to identify | |
6269 | if the removed header has a replacement. If no rules within the | |
6270 | set have matching ACLs, the header field is left as is. | |
5401aa8d | 6271 | |
41bd17a4 | 6272 | For example, to achieve the same behavior as the old |
6273 | 'http_anonymizer standard' option, you should use: | |
5401aa8d | 6274 | |
41bd17a4 | 6275 | request_header_access From deny all |
6276 | request_header_access Referer deny all | |
41bd17a4 | 6277 | request_header_access User-Agent deny all |
5401aa8d | 6278 | |
41bd17a4 | 6279 | Or, to reproduce the old 'http_anonymizer paranoid' feature |
6280 | you should use: | |
5401aa8d | 6281 | |
41bd17a4 | 6282 | request_header_access Authorization allow all |
41bd17a4 | 6283 | request_header_access Proxy-Authorization allow all |
41bd17a4 | 6284 | request_header_access Cache-Control allow all |
41bd17a4 | 6285 | request_header_access Content-Length allow all |
6286 | request_header_access Content-Type allow all | |
6287 | request_header_access Date allow all | |
41bd17a4 | 6288 | request_header_access Host allow all |
6289 | request_header_access If-Modified-Since allow all | |
41bd17a4 | 6290 | request_header_access Pragma allow all |
6291 | request_header_access Accept allow all | |
6292 | request_header_access Accept-Charset allow all | |
6293 | request_header_access Accept-Encoding allow all | |
6294 | request_header_access Accept-Language allow all | |
41bd17a4 | 6295 | request_header_access Connection allow all |
41bd17a4 | 6296 | request_header_access All deny all |
5401aa8d | 6297 | |
638402dd | 6298 | HTTP reply headers are controlled with the reply_header_access directive. |
5401aa8d | 6299 | |
638402dd | 6300 | By default, all headers are allowed (no anonymizing is performed). |
5401aa8d | 6301 | DOC_END |
6302 | ||
41bd17a4 | 6303 | NAME: reply_header_access |
626096be | 6304 | IFDEF: USE_HTTP_VIOLATIONS |
3b07476b | 6305 | TYPE: http_header_access |
41bd17a4 | 6306 | LOC: Config.reply_header_access |
cccac0a2 | 6307 | DEFAULT: none |
638402dd | 6308 | DEFAULT_DOC: No limits. |
cccac0a2 | 6309 | DOC_START |
41bd17a4 | 6310 | Usage: reply_header_access header_name allow|deny [!]aclname ... |
934b03fc | 6311 | |
41bd17a4 | 6312 | WARNING: Doing this VIOLATES the HTTP standard. Enabling |
6313 | this feature could make you liable for problems which it | |
6314 | causes. | |
934b03fc | 6315 | |
41bd17a4 | 6316 | This option only applies to reply headers, i.e., from the |
6317 | server to the client. | |
934b03fc | 6318 | |
41bd17a4 | 6319 | This is the same as request_header_access, but in the other |
3b07476b CT |
6320 | direction. Please see request_header_access for detailed |
6321 | documentation. | |
cccac0a2 | 6322 | |
41bd17a4 | 6323 | For example, to achieve the same behavior as the old |
6324 | 'http_anonymizer standard' option, you should use: | |
cccac0a2 | 6325 | |
41bd17a4 | 6326 | reply_header_access Server deny all |
41bd17a4 | 6327 | reply_header_access WWW-Authenticate deny all |
6328 | reply_header_access Link deny all | |
cccac0a2 | 6329 | |
41bd17a4 | 6330 | Or, to reproduce the old 'http_anonymizer paranoid' feature |
6331 | you should use: | |
cccac0a2 | 6332 | |
41bd17a4 | 6333 | reply_header_access Allow allow all |
41bd17a4 | 6334 | reply_header_access WWW-Authenticate allow all |
41bd17a4 | 6335 | reply_header_access Proxy-Authenticate allow all |
6336 | reply_header_access Cache-Control allow all | |
6337 | reply_header_access Content-Encoding allow all | |
6338 | reply_header_access Content-Length allow all | |
6339 | reply_header_access Content-Type allow all | |
6340 | reply_header_access Date allow all | |
6341 | reply_header_access Expires allow all | |
41bd17a4 | 6342 | reply_header_access Last-Modified allow all |
6343 | reply_header_access Location allow all | |
6344 | reply_header_access Pragma allow all | |
41bd17a4 | 6345 | reply_header_access Content-Language allow all |
41bd17a4 | 6346 | reply_header_access Retry-After allow all |
6347 | reply_header_access Title allow all | |
638402dd | 6348 | reply_header_access Content-Disposition allow all |
41bd17a4 | 6349 | reply_header_access Connection allow all |
41bd17a4 | 6350 | reply_header_access All deny all |
cccac0a2 | 6351 | |
638402dd | 6352 | HTTP request headers are controlled with the request_header_access directive. |
cccac0a2 | 6353 | |
41bd17a4 | 6354 | By default, all headers are allowed (no anonymizing is |
6355 | performed). | |
cccac0a2 | 6356 | DOC_END |
6357 | ||
75e4f2ea | 6358 | NAME: request_header_replace header_replace |
626096be | 6359 | IFDEF: USE_HTTP_VIOLATIONS |
3b07476b | 6360 | TYPE: http_header_replace |
41bd17a4 | 6361 | LOC: Config.request_header_access |
cccac0a2 | 6362 | DEFAULT: none |
41bd17a4 | 6363 | DOC_START |
75e4f2ea MB |
6364 | Usage: request_header_replace header_name message |
6365 | Example: request_header_replace User-Agent Nutscrape/1.0 (CP/M; 8-bit) | |
cccac0a2 | 6366 | |
41bd17a4 | 6367 | This option allows you to change the contents of headers |
75e4f2ea | 6368 | denied with request_header_access above, by replacing them |
638402dd | 6369 | with some fixed string. |
cccac0a2 | 6370 | |
41bd17a4 | 6371 | This only applies to request headers, not reply headers. |
cccac0a2 | 6372 | |
41bd17a4 | 6373 | By default, headers are removed if denied. |
6374 | DOC_END | |
cccac0a2 | 6375 | |
75e4f2ea MB |
6376 | NAME: reply_header_replace |
6377 | IFDEF: USE_HTTP_VIOLATIONS | |
3b07476b | 6378 | TYPE: http_header_replace |
75e4f2ea MB |
6379 | LOC: Config.reply_header_access |
6380 | DEFAULT: none | |
6381 | DOC_START | |
6382 | Usage: reply_header_replace header_name message | |
6383 | Example: reply_header_replace Server Foo/1.0 | |
6384 | ||
6385 | This option allows you to change the contents of headers | |
6386 | denied with reply_header_access above, by replacing them | |
6387 | with some fixed string. | |
6388 | ||
6389 | This only applies to reply headers, not request headers. | |
6390 | ||
6391 | By default, headers are removed if denied. | |
6392 | DOC_END | |
6393 | ||
f4698e0b CT |
6394 | NAME: request_header_add |
6395 | TYPE: HeaderWithAclList | |
6396 | LOC: Config.request_header_add | |
6397 | DEFAULT: none | |
6398 | DOC_START | |
cde8f31b | 6399 | Usage: request_header_add field-name field-value [ acl ... ] |
f4698e0b CT |
6400 | Example: request_header_add X-Client-CA "CA=%ssl::>cert_issuer" all |
6401 | ||
6402 | This option adds header fields to outgoing HTTP requests (i.e., | |
6403 | request headers sent by Squid to the next HTTP hop such as a | |
6404 | cache peer or an origin server). The option has no effect during | |
6405 | cache hit detection. The equivalent adaptation vectoring point | |
6406 | in ICAP terminology is post-cache REQMOD. | |
6407 | ||
6408 | Field-name is a token specifying an HTTP header name. If a | |
6409 | standard HTTP header name is used, Squid does not check whether | |
6410 | the new header conflicts with any existing headers or violates | |
6411 | HTTP rules. If the request to be modified already contains a | |
6412 | field with the same name, the old field is preserved but the | |
6413 | header field values are not merged. | |
6414 | ||
6415 | Field-value is either a token or a quoted string. If quoted | |
6416 | string format is used, then the surrounding quotes are removed | |
6417 | while escape sequences and %macros are processed. | |
6418 | ||
f4698e0b CT |
6419 | One or more Squid ACLs may be specified to restrict header |
6420 | injection to matching requests. As always in squid.conf, all | |
cde8f31b NH |
6421 | ACLs in the ACL list must be satisfied for the insertion to |
6422 | happen. The request_header_add supports fast ACLs only. | |
6423 | ||
6424 | See also: reply_header_add. | |
6425 | DOC_END | |
6426 | ||
6427 | NAME: reply_header_add | |
6428 | TYPE: HeaderWithAclList | |
6429 | LOC: Config.reply_header_add | |
6430 | DEFAULT: none | |
6431 | DOC_START | |
6432 | Usage: reply_header_add field-name field-value [ acl ... ] | |
6433 | Example: reply_header_add X-Client-CA "CA=%ssl::>cert_issuer" all | |
6434 | ||
6435 | This option adds header fields to outgoing HTTP responses (i.e., response | |
6436 | headers delivered by Squid to the client). This option has no effect on | |
6437 | cache hit detection. The equivalent adaptation vectoring point in | |
6438 | ICAP terminology is post-cache RESPMOD. This option does not apply to | |
6439 | successful CONNECT replies. | |
6440 | ||
6441 | Field-name is a token specifying an HTTP header name. If a | |
6442 | standard HTTP header name is used, Squid does not check whether | |
6443 | the new header conflicts with any existing headers or violates | |
6444 | HTTP rules. If the response to be modified already contains a | |
6445 | field with the same name, the old field is preserved but the | |
6446 | header field values are not merged. | |
6447 | ||
6448 | Field-value is either a token or a quoted string. If quoted | |
6449 | string format is used, then the surrounding quotes are removed | |
6450 | while escape sequences and %macros are processed. | |
6451 | ||
6452 | One or more Squid ACLs may be specified to restrict header | |
6453 | injection to matching responses. As always in squid.conf, all | |
6454 | ACLs in the ACL list must be satisfied for the insertion to | |
6455 | happen. The reply_header_add option supports fast ACLs only. | |
6456 | ||
6457 | See also: request_header_add. | |
f4698e0b CT |
6458 | DOC_END |
6459 | ||
d7f4a0b7 CT |
6460 | NAME: note |
6461 | TYPE: note | |
6462 | LOC: Config.notes | |
6463 | DEFAULT: none | |
6464 | DOC_START | |
6465 | This option used to log custom information about the master | |
6466 | transaction. For example, an admin may configure Squid to log | |
6467 | which "user group" the transaction belongs to, where "user group" | |
6468 | will be determined based on a set of ACLs and not [just] | |
6469 | authentication information. | |
6470 | Values of key/value pairs can be logged using %{key}note macros: | |
6471 | ||
6472 | note key value acl ... | |
6473 | logformat myFormat ... %{key}note ... | |
6474 | DOC_END | |
6475 | ||
41bd17a4 | 6476 | NAME: relaxed_header_parser |
6477 | COMMENT: on|off|warn | |
6478 | TYPE: tristate | |
6479 | LOC: Config.onoff.relaxed_header_parser | |
6480 | DEFAULT: on | |
6481 | DOC_START | |
6482 | In the default "on" setting Squid accepts certain forms | |
6483 | of non-compliant HTTP messages where it is unambiguous | |
6484 | what the sending application intended even if the message | |
6485 | is not correctly formatted. The messages is then normalized | |
6486 | to the correct form when forwarded by Squid. | |
cccac0a2 | 6487 | |
41bd17a4 | 6488 | If set to "warn" then a warning will be emitted in cache.log |
6489 | each time such HTTP error is encountered. | |
cccac0a2 | 6490 | |
41bd17a4 | 6491 | If set to "off" then such HTTP errors will cause the request |
6492 | or response to be rejected. | |
6493 | DOC_END | |
7d90757b | 6494 | |
55eae904 AR |
6495 | NAME: collapsed_forwarding |
6496 | COMMENT: (on|off) | |
6497 | TYPE: onoff | |
6498 | LOC: Config.onoff.collapsed_forwarding | |
6499 | DEFAULT: off | |
6500 | DOC_START | |
6501 | This option controls whether Squid is allowed to merge multiple | |
6502 | potentially cachable requests for the same URI before Squid knows | |
6503 | whether the response is going to be cachable. | |
6504 | ||
1a210de4 EB |
6505 | When enabled, instead of forwarding each concurrent request for |
6506 | the same URL, Squid just sends the first of them. The other, so | |
6507 | called "collapsed" requests, wait for the response to the first | |
6508 | request and, if it happens to be cachable, use that response. | |
6509 | Here, "concurrent requests" means "received after the first | |
6510 | request headers were parsed and before the corresponding response | |
6511 | headers were parsed". | |
6512 | ||
6513 | This feature is disabled by default: enabling collapsed | |
6514 | forwarding needlessly delays forwarding requests that look | |
6515 | cachable (when they are collapsed) but then need to be forwarded | |
6516 | individually anyway because they end up being for uncachable | |
6517 | content. However, in some cases, such as acceleration of highly | |
6518 | cachable content with periodic or grouped expiration times, the | |
6519 | gains from collapsing [large volumes of simultaneous refresh | |
6520 | requests] outweigh losses from such delays. | |
6521 | ||
6522 | Squid collapses two kinds of requests: regular client requests | |
6523 | received on one of the listening ports and internal "cache | |
6524 | revalidation" requests which are triggered by those regular | |
6525 | requests hitting a stale cached object. Revalidation collapsing | |
6526 | is currently disabled for Squid instances containing SMP-aware | |
6527 | disk or memory caches and for Vary-controlled cached objects. | |
55eae904 AR |
6528 | DOC_END |
6529 | ||
8f7dbf74 DD |
6530 | NAME: collapsed_forwarding_shared_entries_limit |
6531 | COMMENT: (number of entries) | |
6532 | TYPE: int64_t | |
6533 | LOC: Config.collapsed_forwarding_shared_entries_limit | |
6534 | DEFAULT: 16384 | |
6535 | DOC_START | |
6536 | This limits the size of a table used for sharing information | |
6537 | about collapsible entries among SMP workers. Limiting sharing | |
6538 | too much results in cache content duplication and missed | |
6539 | collapsing opportunities. Using excessively large values | |
6540 | wastes shared memory. | |
6541 | ||
6542 | The limit should be significantly larger then the number of | |
6543 | concurrent collapsible entries one wants to share. For a cache | |
6544 | that handles less than 5000 concurrent requests, the default | |
6545 | setting of 16384 should be plenty. | |
6546 | ||
6547 | If the limit is set to zero, it disables sharing of collapsed | |
6548 | forwarding between SMP workers. | |
6549 | DOC_END | |
6550 | ||
41bd17a4 | 6551 | COMMENT_START |
6552 | TIMEOUTS | |
6553 | ----------------------------------------------------------------------------- | |
6554 | COMMENT_END | |
6555 | ||
6556 | NAME: forward_timeout | |
6557 | COMMENT: time-units | |
6558 | TYPE: time_t | |
6559 | LOC: Config.Timeout.forward | |
6560 | DEFAULT: 4 minutes | |
6561 | DOC_START | |
6562 | This parameter specifies how long Squid should at most attempt in | |
6563 | finding a forwarding path for the request before giving up. | |
cccac0a2 | 6564 | DOC_END |
6565 | ||
41bd17a4 | 6566 | NAME: connect_timeout |
6567 | COMMENT: time-units | |
6568 | TYPE: time_t | |
6569 | LOC: Config.Timeout.connect | |
6570 | DEFAULT: 1 minute | |
057f5854 | 6571 | DOC_START |
41bd17a4 | 6572 | This parameter specifies how long to wait for the TCP connect to |
6573 | the requested server or peer to complete before Squid should | |
6574 | attempt to find another path where to forward the request. | |
057f5854 | 6575 | DOC_END |
6576 | ||
41bd17a4 | 6577 | NAME: peer_connect_timeout |
6578 | COMMENT: time-units | |
6579 | TYPE: time_t | |
6580 | LOC: Config.Timeout.peer_connect | |
6581 | DEFAULT: 30 seconds | |
cccac0a2 | 6582 | DOC_START |
41bd17a4 | 6583 | This parameter specifies how long to wait for a pending TCP |
6584 | connection to a peer cache. The default is 30 seconds. You | |
6585 | may also set different timeout values for individual neighbors | |
6586 | with the 'connect-timeout' option on a 'cache_peer' line. | |
6587 | DOC_END | |
7f7db318 | 6588 | |
41bd17a4 | 6589 | NAME: read_timeout |
6590 | COMMENT: time-units | |
6591 | TYPE: time_t | |
6592 | LOC: Config.Timeout.read | |
6593 | DEFAULT: 15 minutes | |
6594 | DOC_START | |
d5430dc8 AJ |
6595 | Applied on peer server connections. |
6596 | ||
6597 | After each successful read(), the timeout will be extended by this | |
41bd17a4 | 6598 | amount. If no data is read again after this amount of time, |
d5430dc8 AJ |
6599 | the request is aborted and logged with ERR_READ_TIMEOUT. |
6600 | ||
6601 | The default is 15 minutes. | |
41bd17a4 | 6602 | DOC_END |
cccac0a2 | 6603 | |
5ef5e5cc AJ |
6604 | NAME: write_timeout |
6605 | COMMENT: time-units | |
6606 | TYPE: time_t | |
6607 | LOC: Config.Timeout.write | |
6608 | DEFAULT: 15 minutes | |
6609 | DOC_START | |
6610 | This timeout is tracked for all connections that have data | |
6611 | available for writing and are waiting for the socket to become | |
6612 | ready. After each successful write, the timeout is extended by | |
6613 | the configured amount. If Squid has data to write but the | |
6614 | connection is not ready for the configured duration, the | |
6615 | transaction associated with the connection is terminated. The | |
6616 | default is 15 minutes. | |
6617 | DOC_END | |
6618 | ||
41bd17a4 | 6619 | NAME: request_timeout |
6620 | TYPE: time_t | |
6621 | LOC: Config.Timeout.request | |
6622 | DEFAULT: 5 minutes | |
6623 | DOC_START | |
6b2a2108 | 6624 | How long to wait for complete HTTP request headers after initial |
41bd17a4 | 6625 | connection establishment. |
6626 | DOC_END | |
cccac0a2 | 6627 | |
3248e962 CT |
6628 | NAME: request_start_timeout |
6629 | TYPE: time_t | |
6630 | LOC: Config.Timeout.request_start_timeout | |
6631 | DEFAULT: 5 minutes | |
6632 | DOC_START | |
6633 | How long to wait for the first request byte after initial | |
6634 | connection establishment. | |
6635 | DOC_END | |
6636 | ||
97b32442 | 6637 | NAME: client_idle_pconn_timeout persistent_request_timeout |
41bd17a4 | 6638 | TYPE: time_t |
97b32442 | 6639 | LOC: Config.Timeout.clientIdlePconn |
41bd17a4 | 6640 | DEFAULT: 2 minutes |
6641 | DOC_START | |
6642 | How long to wait for the next HTTP request on a persistent | |
97b32442 | 6643 | client connection after the previous request completes. |
41bd17a4 | 6644 | DOC_END |
cccac0a2 | 6645 | |
f6e8754a AR |
6646 | NAME: ftp_client_idle_timeout |
6647 | TYPE: time_t | |
6648 | LOC: Config.Timeout.ftpClientIdle | |
6649 | DEFAULT: 30 minutes | |
6650 | DOC_START | |
6651 | How long to wait for an FTP request on a connection to Squid ftp_port. | |
6652 | Many FTP clients do not deal with idle connection closures well, | |
6653 | necessitating a longer default timeout than client_idle_pconn_timeout | |
6654 | used for incoming HTTP requests. | |
6655 | DOC_END | |
6656 | ||
41bd17a4 | 6657 | NAME: client_lifetime |
6658 | COMMENT: time-units | |
6659 | TYPE: time_t | |
6660 | LOC: Config.Timeout.lifetime | |
6661 | DEFAULT: 1 day | |
6662 | DOC_START | |
6663 | The maximum amount of time a client (browser) is allowed to | |
6664 | remain connected to the cache process. This protects the Cache | |
6665 | from having a lot of sockets (and hence file descriptors) tied up | |
6666 | in a CLOSE_WAIT state from remote clients that go away without | |
6667 | properly shutting down (either because of a network failure or | |
6668 | because of a poor client implementation). The default is one | |
6669 | day, 1440 minutes. | |
7d90757b | 6670 | |
41bd17a4 | 6671 | NOTE: The default value is intended to be much larger than any |
6672 | client would ever need to be connected to your cache. You | |
6673 | should probably change client_lifetime only as a last resort. | |
6674 | If you seem to have many client connections tying up | |
6675 | filedescriptors, we recommend first tuning the read_timeout, | |
6676 | request_timeout, persistent_request_timeout and quick_abort values. | |
cccac0a2 | 6677 | DOC_END |
6678 | ||
c5c06f02 CT |
6679 | NAME: pconn_lifetime |
6680 | COMMENT: time-units | |
6681 | TYPE: time_t | |
6682 | LOC: Config.Timeout.pconnLifetime | |
6683 | DEFAULT: 0 seconds | |
6684 | DOC_START | |
6685 | Desired maximum lifetime of a persistent connection. | |
6686 | When set, Squid will close a now-idle persistent connection that | |
6687 | exceeded configured lifetime instead of moving the connection into | |
6688 | the idle connection pool (or equivalent). No effect on ongoing/active | |
6689 | transactions. Connection lifetime is the time period from the | |
6690 | connection acceptance or opening time until "now". | |
6691 | ||
6692 | This limit is useful in environments with long-lived connections | |
6693 | where Squid configuration or environmental factors change during a | |
6694 | single connection lifetime. If unrestricted, some connections may | |
6695 | last for hours and even days, ignoring those changes that should | |
6696 | have affected their behavior or their existence. | |
6697 | ||
6698 | Currently, a new lifetime value supplied via Squid reconfiguration | |
6699 | has no effect on already idle connections unless they become busy. | |
6700 | ||
6701 | When set to '0' this limit is not used. | |
6702 | DOC_END | |
6703 | ||
41bd17a4 | 6704 | NAME: half_closed_clients |
6705 | TYPE: onoff | |
6706 | LOC: Config.onoff.half_closed_clients | |
0c2f5c4f | 6707 | DEFAULT: off |
4eb368f9 | 6708 | DOC_START |
41bd17a4 | 6709 | Some clients may shutdown the sending side of their TCP |
6710 | connections, while leaving their receiving sides open. Sometimes, | |
6711 | Squid can not tell the difference between a half-closed and a | |
0c2f5c4f AJ |
6712 | fully-closed TCP connection. |
6713 | ||
6714 | By default, Squid will immediately close client connections when | |
6715 | read(2) returns "no more data to read." | |
6716 | ||
abdf1651 | 6717 | Change this option to 'on' and Squid will keep open connections |
0c2f5c4f AJ |
6718 | until a read(2) or write(2) on the socket returns an error. |
6719 | This may show some benefits for reverse proxies. But if not | |
6720 | it is recommended to leave OFF. | |
4eb368f9 | 6721 | DOC_END |
6722 | ||
97b32442 | 6723 | NAME: server_idle_pconn_timeout pconn_timeout |
41bd17a4 | 6724 | TYPE: time_t |
97b32442 | 6725 | LOC: Config.Timeout.serverIdlePconn |
41bd17a4 | 6726 | DEFAULT: 1 minute |
cccac0a2 | 6727 | DOC_START |
41bd17a4 | 6728 | Timeout for idle persistent connections to servers and other |
6729 | proxies. | |
6730 | DOC_END | |
cccac0a2 | 6731 | |
41bd17a4 | 6732 | NAME: ident_timeout |
6733 | TYPE: time_t | |
6734 | IFDEF: USE_IDENT | |
4daaf3cb | 6735 | LOC: Ident::TheConfig.timeout |
41bd17a4 | 6736 | DEFAULT: 10 seconds |
6737 | DOC_START | |
6738 | Maximum time to wait for IDENT lookups to complete. | |
cccac0a2 | 6739 | |
41bd17a4 | 6740 | If this is too high, and you enabled IDENT lookups from untrusted |
6741 | users, you might be susceptible to denial-of-service by having | |
6742 | many ident requests going at once. | |
cccac0a2 | 6743 | DOC_END |
6744 | ||
41bd17a4 | 6745 | NAME: shutdown_lifetime |
6746 | COMMENT: time-units | |
6747 | TYPE: time_t | |
6748 | LOC: Config.shutdownLifetime | |
6749 | DEFAULT: 30 seconds | |
cccac0a2 | 6750 | DOC_START |
41bd17a4 | 6751 | When SIGTERM or SIGHUP is received, the cache is put into |
6752 | "shutdown pending" mode until all active sockets are closed. | |
6753 | This value is the lifetime to set for all open descriptors | |
6754 | during shutdown mode. Any active clients after this many | |
6755 | seconds will receive a 'timeout' message. | |
cccac0a2 | 6756 | DOC_END |
0976f8db | 6757 | |
cccac0a2 | 6758 | COMMENT_START |
6759 | ADMINISTRATIVE PARAMETERS | |
6760 | ----------------------------------------------------------------------------- | |
6761 | COMMENT_END | |
6762 | ||
6763 | NAME: cache_mgr | |
6764 | TYPE: string | |
6765 | DEFAULT: webmaster | |
6766 | LOC: Config.adminEmail | |
6767 | DOC_START | |
6768 | Email-address of local cache manager who will receive | |
638402dd | 6769 | mail if the cache dies. The default is "webmaster". |
cccac0a2 | 6770 | DOC_END |
6771 | ||
abacf776 | 6772 | NAME: mail_from |
6773 | TYPE: string | |
6774 | DEFAULT: none | |
6775 | LOC: Config.EmailFrom | |
6776 | DOC_START | |
6777 | From: email-address for mail sent when the cache dies. | |
638402dd AJ |
6778 | The default is to use 'squid@unique_hostname'. |
6779 | ||
6780 | See also: unique_hostname directive. | |
abacf776 | 6781 | DOC_END |
6782 | ||
d084bf20 | 6783 | NAME: mail_program |
6784 | TYPE: eol | |
6785 | DEFAULT: mail | |
6786 | LOC: Config.EmailProgram | |
6787 | DOC_START | |
6788 | Email program used to send mail if the cache dies. | |
846a5e31 | 6789 | The default is "mail". The specified program must comply |
d084bf20 | 6790 | with the standard Unix mail syntax: |
846a5e31 | 6791 | mail-program recipient < mailfile |
6792 | ||
d084bf20 | 6793 | Optional command line options can be specified. |
6794 | DOC_END | |
6795 | ||
cccac0a2 | 6796 | NAME: cache_effective_user |
6797 | TYPE: string | |
5483d916 | 6798 | DEFAULT: @DEFAULT_CACHE_EFFECTIVE_USER@ |
cccac0a2 | 6799 | LOC: Config.effectiveUser |
e3d74828 | 6800 | DOC_START |
6801 | If you start Squid as root, it will change its effective/real | |
6802 | UID/GID to the user specified below. The default is to change | |
5483d916 | 6803 | to UID of @DEFAULT_CACHE_EFFECTIVE_USER@. |
64e288bd | 6804 | see also; cache_effective_group |
e3d74828 | 6805 | DOC_END |
6806 | ||
cccac0a2 | 6807 | NAME: cache_effective_group |
6808 | TYPE: string | |
6809 | DEFAULT: none | |
638402dd | 6810 | DEFAULT_DOC: Use system group memberships of the cache_effective_user account |
cccac0a2 | 6811 | LOC: Config.effectiveGroup |
6812 | DOC_START | |
64e288bd | 6813 | Squid sets the GID to the effective user's default group ID |
6814 | (taken from the password file) and supplementary group list | |
6815 | from the groups membership. | |
6816 | ||
e3d74828 | 6817 | If you want Squid to run with a specific GID regardless of |
6818 | the group memberships of the effective user then set this | |
6819 | to the group (or GID) you want Squid to run as. When set | |
64e288bd | 6820 | all other group privileges of the effective user are ignored |
e3d74828 | 6821 | and only this GID is effective. If Squid is not started as |
64e288bd | 6822 | root the user starting Squid MUST be member of the specified |
e3d74828 | 6823 | group. |
64e288bd | 6824 | |
6825 | This option is not recommended by the Squid Team. | |
6826 | Our preference is for administrators to configure a secure | |
6827 | user account for squid with UID/GID matching system policies. | |
cccac0a2 | 6828 | DOC_END |
6829 | ||
d3caee79 | 6830 | NAME: httpd_suppress_version_string |
6831 | COMMENT: on|off | |
6832 | TYPE: onoff | |
6833 | DEFAULT: off | |
6834 | LOC: Config.onoff.httpd_suppress_version_string | |
6835 | DOC_START | |
6836 | Suppress Squid version string info in HTTP headers and HTML error pages. | |
6837 | DOC_END | |
6838 | ||
cccac0a2 | 6839 | NAME: visible_hostname |
6840 | TYPE: string | |
6841 | LOC: Config.visibleHostname | |
6842 | DEFAULT: none | |
638402dd | 6843 | DEFAULT_DOC: Automatically detect the system host name |
cccac0a2 | 6844 | DOC_START |
6845 | If you want to present a special hostname in error messages, etc, | |
7f7db318 | 6846 | define this. Otherwise, the return value of gethostname() |
cccac0a2 | 6847 | will be used. If you have multiple caches in a cluster and |
6848 | get errors about IP-forwarding you must set them to have individual | |
6849 | names with this setting. | |
6850 | DOC_END | |
6851 | ||
cccac0a2 | 6852 | NAME: unique_hostname |
6853 | TYPE: string | |
6854 | LOC: Config.uniqueHostname | |
6855 | DEFAULT: none | |
638402dd | 6856 | DEFAULT_DOC: Copy the value from visible_hostname |
cccac0a2 | 6857 | DOC_START |
6858 | If you want to have multiple machines with the same | |
7f7db318 | 6859 | 'visible_hostname' you must give each machine a different |
6860 | 'unique_hostname' so forwarding loops can be detected. | |
cccac0a2 | 6861 | DOC_END |
6862 | ||
cccac0a2 | 6863 | NAME: hostname_aliases |
6864 | TYPE: wordlist | |
6865 | LOC: Config.hostnameAliases | |
6866 | DEFAULT: none | |
6867 | DOC_START | |
7f7db318 | 6868 | A list of other DNS names your cache has. |
cccac0a2 | 6869 | DOC_END |
0976f8db | 6870 | |
c642c141 AJ |
6871 | NAME: umask |
6872 | TYPE: int | |
6873 | LOC: Config.umask | |
6874 | DEFAULT: 027 | |
6875 | DOC_START | |
6876 | Minimum umask which should be enforced while the proxy | |
6877 | is running, in addition to the umask set at startup. | |
6878 | ||
6879 | For a traditional octal representation of umasks, start | |
6880 | your value with 0. | |
6881 | DOC_END | |
6882 | ||
cccac0a2 | 6883 | COMMENT_START |
6884 | OPTIONS FOR THE CACHE REGISTRATION SERVICE | |
6885 | ----------------------------------------------------------------------------- | |
6886 | ||
6887 | This section contains parameters for the (optional) cache | |
6888 | announcement service. This service is provided to help | |
6889 | cache administrators locate one another in order to join or | |
6890 | create cache hierarchies. | |
6891 | ||
6892 | An 'announcement' message is sent (via UDP) to the registration | |
6893 | service by Squid. By default, the announcement message is NOT | |
6894 | SENT unless you enable it with 'announce_period' below. | |
6895 | ||
6896 | The announcement message includes your hostname, plus the | |
6897 | following information from this configuration file: | |
6898 | ||
6899 | http_port | |
6900 | icp_port | |
6901 | cache_mgr | |
6902 | ||
6903 | All current information is processed regularly and made | |
6904 | available on the Web at http://www.ircache.net/Cache/Tracker/. | |
6905 | COMMENT_END | |
6906 | ||
6907 | NAME: announce_period | |
6908 | TYPE: time_t | |
6909 | LOC: Config.Announce.period | |
6910 | DEFAULT: 0 | |
638402dd | 6911 | DEFAULT_DOC: Announcement messages disabled. |
cccac0a2 | 6912 | DOC_START |
638402dd | 6913 | This is how frequently to send cache announcements. |
cccac0a2 | 6914 | |
e0855596 | 6915 | To enable announcing your cache, just set an announce period. |
cccac0a2 | 6916 | |
e0855596 AJ |
6917 | Example: |
6918 | announce_period 1 day | |
cccac0a2 | 6919 | DOC_END |
6920 | ||
cccac0a2 | 6921 | NAME: announce_host |
6922 | TYPE: string | |
6923 | DEFAULT: tracker.ircache.net | |
6924 | LOC: Config.Announce.host | |
638402dd AJ |
6925 | DOC_START |
6926 | Set the hostname where announce registration messages will be sent. | |
6927 | ||
6928 | See also announce_port and announce_file | |
6929 | DOC_END | |
cccac0a2 | 6930 | |
6931 | NAME: announce_file | |
6932 | TYPE: string | |
6933 | DEFAULT: none | |
6934 | LOC: Config.Announce.file | |
638402dd AJ |
6935 | DOC_START |
6936 | The contents of this file will be included in the announce | |
6937 | registration messages. | |
6938 | DOC_END | |
cccac0a2 | 6939 | |
6940 | NAME: announce_port | |
ae870270 | 6941 | TYPE: u_short |
cccac0a2 | 6942 | DEFAULT: 3131 |
6943 | LOC: Config.Announce.port | |
6944 | DOC_START | |
638402dd | 6945 | Set the port where announce registration messages will be sent. |
cccac0a2 | 6946 | |
638402dd | 6947 | See also announce_host and announce_file |
cccac0a2 | 6948 | DOC_END |
6949 | ||
8d6275c0 | 6950 | COMMENT_START |
6951 | HTTPD-ACCELERATOR OPTIONS | |
6952 | ----------------------------------------------------------------------------- | |
6953 | COMMENT_END | |
6954 | ||
cccac0a2 | 6955 | NAME: httpd_accel_surrogate_id |
cccac0a2 | 6956 | TYPE: string |
b2b40d8c | 6957 | DEFAULT: none |
638402dd | 6958 | DEFAULT_DOC: visible_hostname is used if no specific ID is set. |
cccac0a2 | 6959 | LOC: Config.Accel.surrogate_id |
cccac0a2 | 6960 | DOC_START |
6961 | Surrogates (http://www.esi.org/architecture_spec_1.0.html) | |
6962 | need an identification token to allow control targeting. Because | |
6963 | a farm of surrogates may all perform the same tasks, they may share | |
6964 | an identification token. | |
6965 | DOC_END | |
6966 | ||
6967 | NAME: http_accel_surrogate_remote | |
cccac0a2 | 6968 | COMMENT: on|off |
6969 | TYPE: onoff | |
6970 | DEFAULT: off | |
6971 | LOC: Config.onoff.surrogate_is_remote | |
6972 | DOC_START | |
638402dd AJ |
6973 | Remote surrogates (such as those in a CDN) honour the header |
6974 | "Surrogate-Control: no-store-remote". | |
6975 | ||
cccac0a2 | 6976 | Set this to on to have squid behave as a remote surrogate. |
6977 | DOC_END | |
6978 | ||
6979 | NAME: esi_parser | |
f41735ea | 6980 | IFDEF: USE_SQUID_ESI |
964b44c3 | 6981 | COMMENT: libxml2|expat|custom |
cccac0a2 | 6982 | TYPE: string |
6983 | LOC: ESIParser::Type | |
6984 | DEFAULT: custom | |
6985 | DOC_START | |
6986 | ESI markup is not strictly XML compatible. The custom ESI parser | |
6987 | will give higher performance, but cannot handle non ASCII character | |
6988 | encodings. | |
6989 | DOC_END | |
0976f8db | 6990 | |
9edd9041 | 6991 | COMMENT_START |
8d6275c0 | 6992 | DELAY POOL PARAMETERS |
9edd9041 | 6993 | ----------------------------------------------------------------------------- |
6994 | COMMENT_END | |
6995 | ||
6996 | NAME: delay_pools | |
6997 | TYPE: delay_pool_count | |
6998 | DEFAULT: 0 | |
9a0a18de | 6999 | IFDEF: USE_DELAY_POOLS |
9edd9041 | 7000 | LOC: Config.Delay |
7001 | DOC_START | |
7002 | This represents the number of delay pools to be used. For example, | |
7003 | if you have one class 2 delay pool and one class 3 delays pool, you | |
7004 | have a total of 2 delay pools. | |
638402dd AJ |
7005 | |
7006 | See also delay_parameters, delay_class, delay_access for pool | |
7007 | configuration details. | |
9edd9041 | 7008 | DOC_END |
7009 | ||
7010 | NAME: delay_class | |
7011 | TYPE: delay_pool_class | |
7012 | DEFAULT: none | |
9a0a18de | 7013 | IFDEF: USE_DELAY_POOLS |
9edd9041 | 7014 | LOC: Config.Delay |
7015 | DOC_START | |
7016 | This defines the class of each delay pool. There must be exactly one | |
7017 | delay_class line for each delay pool. For example, to define two | |
7018 | delay pools, one of class 2 and one of class 3, the settings above | |
7019 | and here would be: | |
7020 | ||
b1fb3348 AJ |
7021 | Example: |
7022 | delay_pools 4 # 4 delay pools | |
7023 | delay_class 1 2 # pool 1 is a class 2 pool | |
7024 | delay_class 2 3 # pool 2 is a class 3 pool | |
7025 | delay_class 3 4 # pool 3 is a class 4 pool | |
7026 | delay_class 4 5 # pool 4 is a class 5 pool | |
9edd9041 | 7027 | |
7028 | The delay pool classes are: | |
7029 | ||
7030 | class 1 Everything is limited by a single aggregate | |
7031 | bucket. | |
7032 | ||
7033 | class 2 Everything is limited by a single aggregate | |
7034 | bucket as well as an "individual" bucket chosen | |
b1fb3348 | 7035 | from bits 25 through 32 of the IPv4 address. |
9edd9041 | 7036 | |
7037 | class 3 Everything is limited by a single aggregate | |
7038 | bucket as well as a "network" bucket chosen | |
7039 | from bits 17 through 24 of the IP address and a | |
7040 | "individual" bucket chosen from bits 17 through | |
b1fb3348 | 7041 | 32 of the IPv4 address. |
9edd9041 | 7042 | |
7043 | class 4 Everything in a class 3 delay pool, with an | |
7044 | additional limit on a per user basis. This | |
7045 | only takes effect if the username is established | |
7046 | in advance - by forcing authentication in your | |
7047 | http_access rules. | |
7048 | ||
7049 | class 5 Requests are grouped according their tag (see | |
7050 | external_acl's tag= reply). | |
7051 | ||
0b68481a AJ |
7052 | |
7053 | Each pool also requires a delay_parameters directive to configure the pool size | |
7054 | and speed limits used whenever the pool is applied to a request. Along with | |
7055 | a set of delay_access directives to determine when it is used. | |
7056 | ||
9edd9041 | 7057 | NOTE: If an IP address is a.b.c.d |
7058 | -> bits 25 through 32 are "d" | |
7059 | -> bits 17 through 24 are "c" | |
7060 | -> bits 17 through 32 are "c * 256 + d" | |
b1fb3348 AJ |
7061 | |
7062 | NOTE-2: Due to the use of bitmasks in class 2,3,4 pools they only apply to | |
7063 | IPv4 traffic. Class 1 and 5 pools may be used with IPv6 traffic. | |
638402dd AJ |
7064 | |
7065 | This clause only supports fast acl types. | |
7066 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
7067 | ||
7068 | See also delay_parameters and delay_access. | |
9edd9041 | 7069 | DOC_END |
7070 | ||
7071 | NAME: delay_access | |
7072 | TYPE: delay_pool_access | |
7073 | DEFAULT: none | |
638402dd | 7074 | DEFAULT_DOC: Deny using the pool, unless allow rules exist in squid.conf for the pool. |
9a0a18de | 7075 | IFDEF: USE_DELAY_POOLS |
9edd9041 | 7076 | LOC: Config.Delay |
7077 | DOC_START | |
7078 | This is used to determine which delay pool a request falls into. | |
7079 | ||
7080 | delay_access is sorted per pool and the matching starts with pool 1, | |
7081 | then pool 2, ..., and finally pool N. The first delay pool where the | |
7082 | request is allowed is selected for the request. If it does not allow | |
7083 | the request to any pool then the request is not delayed (default). | |
7084 | ||
7085 | For example, if you want some_big_clients in delay | |
7086 | pool 1 and lotsa_little_clients in delay pool 2: | |
7087 | ||
638402dd AJ |
7088 | delay_access 1 allow some_big_clients |
7089 | delay_access 1 deny all | |
7090 | delay_access 2 allow lotsa_little_clients | |
7091 | delay_access 2 deny all | |
7092 | delay_access 3 allow authenticated_clients | |
7093 | ||
7094 | See also delay_parameters and delay_class. | |
7095 | ||
9edd9041 | 7096 | DOC_END |
7097 | ||
7098 | NAME: delay_parameters | |
7099 | TYPE: delay_pool_rates | |
7100 | DEFAULT: none | |
9a0a18de | 7101 | IFDEF: USE_DELAY_POOLS |
9edd9041 | 7102 | LOC: Config.Delay |
7103 | DOC_START | |
7104 | This defines the parameters for a delay pool. Each delay pool has | |
7105 | a number of "buckets" associated with it, as explained in the | |
0b68481a | 7106 | description of delay_class. |
9edd9041 | 7107 | |
0b68481a | 7108 | For a class 1 delay pool, the syntax is: |
6e7502cc | 7109 | delay_class pool 1 |
0b68481a | 7110 | delay_parameters pool aggregate |
9edd9041 | 7111 | |
7112 | For a class 2 delay pool: | |
6e7502cc | 7113 | delay_class pool 2 |
0b68481a | 7114 | delay_parameters pool aggregate individual |
9edd9041 | 7115 | |
7116 | For a class 3 delay pool: | |
6e7502cc | 7117 | delay_class pool 3 |
0b68481a | 7118 | delay_parameters pool aggregate network individual |
9edd9041 | 7119 | |
7120 | For a class 4 delay pool: | |
6e7502cc | 7121 | delay_class pool 4 |
0b68481a | 7122 | delay_parameters pool aggregate network individual user |
9edd9041 | 7123 | |
7124 | For a class 5 delay pool: | |
6e7502cc | 7125 | delay_class pool 5 |
0b68481a | 7126 | delay_parameters pool tagrate |
9edd9041 | 7127 | |
0b68481a | 7128 | The option variables are: |
9edd9041 | 7129 | |
7130 | pool a pool number - ie, a number between 1 and the | |
7131 | number specified in delay_pools as used in | |
7132 | delay_class lines. | |
7133 | ||
fdb47ac6 | 7134 | aggregate the speed limit parameters for the aggregate bucket |
9edd9041 | 7135 | (class 1, 2, 3). |
7136 | ||
fdb47ac6 | 7137 | individual the speed limit parameters for the individual |
9edd9041 | 7138 | buckets (class 2, 3). |
7139 | ||
fdb47ac6 | 7140 | network the speed limit parameters for the network buckets |
9edd9041 | 7141 | (class 3). |
7142 | ||
fdb47ac6 | 7143 | user the speed limit parameters for the user buckets |
9edd9041 | 7144 | (class 4). |
7145 | ||
fdb47ac6 | 7146 | tagrate the speed limit parameters for the tag buckets |
9edd9041 | 7147 | (class 5). |
7148 | ||
7149 | A pair of delay parameters is written restore/maximum, where restore is | |
7150 | the number of bytes (not bits - modem and network speeds are usually | |
7151 | quoted in bits) per second placed into the bucket, and maximum is the | |
7152 | maximum number of bytes which can be in the bucket at any time. | |
7153 | ||
0b68481a AJ |
7154 | There must be one delay_parameters line for each delay pool. |
7155 | ||
7156 | ||
9edd9041 | 7157 | For example, if delay pool number 1 is a class 2 delay pool as in the |
0b68481a | 7158 | above example, and is being used to strictly limit each host to 64Kbit/sec |
9edd9041 | 7159 | (plus overheads), with no overall limit, the line is: |
7160 | ||
6e7502cc | 7161 | delay_parameters 1 none 8000/8000 |
0b68481a | 7162 | |
c3e31a3a | 7163 | Note that 8 x 8K Byte/sec -> 64K bit/sec. |
9edd9041 | 7164 | |
6e7502cc | 7165 | Note that the word 'none' is used to represent no limit. |
9edd9041 | 7166 | |
0b68481a | 7167 | |
9edd9041 | 7168 | And, if delay pool number 2 is a class 3 delay pool as in the above |
0b68481a AJ |
7169 | example, and you want to limit it to a total of 256Kbit/sec (strict limit) |
7170 | with each 8-bit network permitted 64Kbit/sec (strict limit) and each | |
7171 | individual host permitted 4800bit/sec with a bucket maximum size of 64Kbits | |
9edd9041 | 7172 | to permit a decent web page to be downloaded at a decent speed |
7173 | (if the network is not being limited due to overuse) but slow down | |
7174 | large downloads more significantly: | |
7175 | ||
0b68481a AJ |
7176 | delay_parameters 2 32000/32000 8000/8000 600/8000 |
7177 | ||
c3e31a3a AJ |
7178 | Note that 8 x 32K Byte/sec -> 256K bit/sec. |
7179 | 8 x 8K Byte/sec -> 64K bit/sec. | |
7180 | 8 x 600 Byte/sec -> 4800 bit/sec. | |
9edd9041 | 7181 | |
9edd9041 | 7182 | |
7183 | Finally, for a class 4 delay pool as in the example - each user will | |
0b68481a | 7184 | be limited to 128Kbits/sec no matter how many workstations they are logged into.: |
9edd9041 | 7185 | |
0b68481a | 7186 | delay_parameters 4 32000/32000 8000/8000 600/64000 16000/16000 |
638402dd AJ |
7187 | |
7188 | ||
7189 | See also delay_class and delay_access. | |
7190 | ||
9edd9041 | 7191 | DOC_END |
7192 | ||
7193 | NAME: delay_initial_bucket_level | |
7194 | COMMENT: (percent, 0-100) | |
ae870270 | 7195 | TYPE: u_short |
9edd9041 | 7196 | DEFAULT: 50 |
9a0a18de | 7197 | IFDEF: USE_DELAY_POOLS |
9edd9041 | 7198 | LOC: Config.Delay.initial |
7199 | DOC_START | |
7200 | The initial bucket percentage is used to determine how much is put | |
7201 | in each bucket when squid starts, is reconfigured, or first notices | |
7202 | a host accessing it (in class 2 and class 3, individual hosts and | |
7203 | networks only have buckets associated with them once they have been | |
7204 | "seen" by squid). | |
7205 | DOC_END | |
7206 | ||
b4cd430a CT |
7207 | COMMENT_START |
7208 | CLIENT DELAY POOL PARAMETERS | |
7209 | ----------------------------------------------------------------------------- | |
7210 | COMMENT_END | |
7211 | ||
7212 | NAME: client_delay_pools | |
7213 | TYPE: client_delay_pool_count | |
7214 | DEFAULT: 0 | |
9a0a18de | 7215 | IFDEF: USE_DELAY_POOLS |
b4cd430a CT |
7216 | LOC: Config.ClientDelay |
7217 | DOC_START | |
7218 | This option specifies the number of client delay pools used. It must | |
7219 | preceed other client_delay_* options. | |
7220 | ||
638402dd AJ |
7221 | Example: |
7222 | client_delay_pools 2 | |
7223 | ||
7224 | See also client_delay_parameters and client_delay_access. | |
b4cd430a CT |
7225 | DOC_END |
7226 | ||
7227 | NAME: client_delay_initial_bucket_level | |
7228 | COMMENT: (percent, 0-no_limit) | |
ae870270 | 7229 | TYPE: u_short |
b4cd430a | 7230 | DEFAULT: 50 |
9a0a18de | 7231 | IFDEF: USE_DELAY_POOLS |
b4cd430a CT |
7232 | LOC: Config.ClientDelay.initial |
7233 | DOC_START | |
7234 | This option determines the initial bucket size as a percentage of | |
7235 | max_bucket_size from client_delay_parameters. Buckets are created | |
7236 | at the time of the "first" connection from the matching IP. Idle | |
7237 | buckets are periodically deleted up. | |
7238 | ||
7239 | You can specify more than 100 percent but note that such "oversized" | |
7240 | buckets are not refilled until their size goes down to max_bucket_size | |
7241 | from client_delay_parameters. | |
7242 | ||
638402dd AJ |
7243 | Example: |
7244 | client_delay_initial_bucket_level 50 | |
b4cd430a CT |
7245 | DOC_END |
7246 | ||
7247 | NAME: client_delay_parameters | |
7248 | TYPE: client_delay_pool_rates | |
7249 | DEFAULT: none | |
9a0a18de | 7250 | IFDEF: USE_DELAY_POOLS |
b4cd430a CT |
7251 | LOC: Config.ClientDelay |
7252 | DOC_START | |
7253 | ||
7254 | This option configures client-side bandwidth limits using the | |
7255 | following format: | |
7256 | ||
7257 | client_delay_parameters pool speed_limit max_bucket_size | |
7258 | ||
7259 | pool is an integer ID used for client_delay_access matching. | |
7260 | ||
7261 | speed_limit is bytes added to the bucket per second. | |
7262 | ||
7263 | max_bucket_size is the maximum size of a bucket, enforced after any | |
7264 | speed_limit additions. | |
7265 | ||
7266 | Please see the delay_parameters option for more information and | |
7267 | examples. | |
7268 | ||
638402dd AJ |
7269 | Example: |
7270 | client_delay_parameters 1 1024 2048 | |
7271 | client_delay_parameters 2 51200 16384 | |
7272 | ||
7273 | See also client_delay_access. | |
7274 | ||
b4cd430a CT |
7275 | DOC_END |
7276 | ||
7277 | NAME: client_delay_access | |
7278 | TYPE: client_delay_pool_access | |
7279 | DEFAULT: none | |
638402dd | 7280 | DEFAULT_DOC: Deny use of the pool, unless allow rules exist in squid.conf for the pool. |
9a0a18de | 7281 | IFDEF: USE_DELAY_POOLS |
b4cd430a CT |
7282 | LOC: Config.ClientDelay |
7283 | DOC_START | |
b4cd430a CT |
7284 | This option determines the client-side delay pool for the |
7285 | request: | |
7286 | ||
7287 | client_delay_access pool_ID allow|deny acl_name | |
7288 | ||
7289 | All client_delay_access options are checked in their pool ID | |
7290 | order, starting with pool 1. The first checked pool with allowed | |
7291 | request is selected for the request. If no ACL matches or there | |
7292 | are no client_delay_access options, the request bandwidth is not | |
7293 | limited. | |
7294 | ||
7295 | The ACL-selected pool is then used to find the | |
7296 | client_delay_parameters for the request. Client-side pools are | |
7297 | not used to aggregate clients. Clients are always aggregated | |
7298 | based on their source IP addresses (one bucket per source IP). | |
7299 | ||
638402dd AJ |
7300 | This clause only supports fast acl types. |
7301 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
7302 | Additionally, only the client TCP connection details are available. | |
7303 | ACLs testing HTTP properties will not work. | |
7304 | ||
b4cd430a CT |
7305 | Please see delay_access for more examples. |
7306 | ||
638402dd AJ |
7307 | Example: |
7308 | client_delay_access 1 allow low_rate_network | |
7309 | client_delay_access 2 allow vips_network | |
7310 | ||
7311 | ||
7312 | See also client_delay_parameters and client_delay_pools. | |
b4cd430a CT |
7313 | DOC_END |
7314 | ||
b27668ec EB |
7315 | NAME: response_delay_pool |
7316 | TYPE: response_delay_pool_parameters | |
7317 | DEFAULT: none | |
7318 | IFDEF: USE_DELAY_POOLS | |
7319 | LOC: Config.MessageDelay | |
7320 | DOC_START | |
7321 | This option configures client response bandwidth limits using the | |
7322 | following format: | |
7323 | ||
7324 | response_delay_pool name [option=value] ... | |
7325 | ||
7326 | name the response delay pool name | |
7327 | ||
7328 | available options: | |
7329 | ||
7330 | individual-restore The speed limit of an individual | |
7331 | bucket(bytes/s). To be used in conjunction | |
7332 | with 'individual-maximum'. | |
7333 | ||
7334 | individual-maximum The maximum number of bytes which can | |
7335 | be placed into the individual bucket. To be used | |
7336 | in conjunction with 'individual-restore'. | |
7337 | ||
7338 | aggregate-restore The speed limit for the aggregate | |
7339 | bucket(bytes/s). To be used in conjunction with | |
7340 | 'aggregate-maximum'. | |
7341 | ||
7342 | aggregate-maximum The maximum number of bytes which can | |
7343 | be placed into the aggregate bucket. To be used | |
7344 | in conjunction with 'aggregate-restore'. | |
7345 | ||
7346 | initial-bucket-level The initial bucket size as a percentage | |
7347 | of individual-maximum. | |
7348 | ||
7349 | Individual and(or) aggregate bucket options may not be specified, | |
7350 | meaning no individual and(or) aggregate speed limitation. | |
7351 | See also response_delay_pool_access and delay_parameters for | |
7352 | terminology details. | |
7353 | DOC_END | |
7354 | ||
7355 | NAME: response_delay_pool_access | |
7356 | TYPE: response_delay_pool_access | |
7357 | DEFAULT: none | |
7358 | DEFAULT_DOC: Deny use of the pool, unless allow rules exist in squid.conf for the pool. | |
7359 | IFDEF: USE_DELAY_POOLS | |
7360 | LOC: Config.MessageDelay | |
7361 | DOC_START | |
7362 | Determines whether a specific named response delay pool is used | |
7363 | for the transaction. The syntax for this directive is: | |
7364 | ||
7365 | response_delay_pool_access pool_name allow|deny acl_name | |
7366 | ||
7367 | All response_delay_pool_access options are checked in the order | |
7368 | they appear in this configuration file. The first rule with a | |
7369 | matching ACL wins. If (and only if) an "allow" rule won, Squid | |
7370 | assigns the response to the corresponding named delay pool. | |
7371 | DOC_END | |
7372 | ||
cccac0a2 | 7373 | COMMENT_START |
8d6275c0 | 7374 | WCCPv1 AND WCCPv2 CONFIGURATION OPTIONS |
cccac0a2 | 7375 | ----------------------------------------------------------------------------- |
7376 | COMMENT_END | |
7377 | ||
8d6275c0 | 7378 | NAME: wccp_router |
7379 | TYPE: address | |
7380 | LOC: Config.Wccp.router | |
0eb08770 | 7381 | DEFAULT: any_addr |
638402dd | 7382 | DEFAULT_DOC: WCCP disabled. |
8d6275c0 | 7383 | IFDEF: USE_WCCP |
e313ab0a AJ |
7384 | DOC_START |
7385 | Use this option to define your WCCP ``home'' router for | |
7386 | Squid. | |
7387 | ||
7388 | wccp_router supports a single WCCP(v1) router | |
7389 | ||
7390 | wccp2_router supports multiple WCCPv2 routers | |
7391 | ||
7392 | only one of the two may be used at the same time and defines | |
7393 | which version of WCCP to use. | |
7394 | DOC_END | |
df2eec10 | 7395 | |
8d6275c0 | 7396 | NAME: wccp2_router |
9fb4efad | 7397 | TYPE: IpAddress_list |
8d6275c0 | 7398 | LOC: Config.Wccp2.router |
cccac0a2 | 7399 | DEFAULT: none |
638402dd | 7400 | DEFAULT_DOC: WCCPv2 disabled. |
8d6275c0 | 7401 | IFDEF: USE_WCCPv2 |
cccac0a2 | 7402 | DOC_START |
8d6275c0 | 7403 | Use this option to define your WCCP ``home'' router for |
7404 | Squid. | |
cccac0a2 | 7405 | |
8d6275c0 | 7406 | wccp_router supports a single WCCP(v1) router |
cccac0a2 | 7407 | |
8d6275c0 | 7408 | wccp2_router supports multiple WCCPv2 routers |
cccac0a2 | 7409 | |
8d6275c0 | 7410 | only one of the two may be used at the same time and defines |
7411 | which version of WCCP to use. | |
7412 | DOC_END | |
7413 | ||
7414 | NAME: wccp_version | |
cccac0a2 | 7415 | TYPE: int |
8d6275c0 | 7416 | LOC: Config.Wccp.version |
7417 | DEFAULT: 4 | |
7418 | IFDEF: USE_WCCP | |
cccac0a2 | 7419 | DOC_START |
8d6275c0 | 7420 | This directive is only relevant if you need to set up WCCP(v1) |
7421 | to some very old and end-of-life Cisco routers. In all other | |
7422 | setups it must be left unset or at the default setting. | |
7423 | It defines an internal version in the WCCP(v1) protocol, | |
7424 | with version 4 being the officially documented protocol. | |
cccac0a2 | 7425 | |
8d6275c0 | 7426 | According to some users, Cisco IOS 11.2 and earlier only |
7427 | support WCCP version 3. If you're using that or an earlier | |
7428 | version of IOS, you may need to change this value to 3, otherwise | |
7429 | do not specify this parameter. | |
cccac0a2 | 7430 | DOC_END |
7431 | ||
8d6275c0 | 7432 | NAME: wccp2_rebuild_wait |
7433 | TYPE: onoff | |
7434 | LOC: Config.Wccp2.rebuildwait | |
7435 | DEFAULT: on | |
7436 | IFDEF: USE_WCCPv2 | |
7437 | DOC_START | |
7438 | If this is enabled Squid will wait for the cache dir rebuild to finish | |
7439 | before sending the first wccp2 HereIAm packet | |
7440 | DOC_END | |
cccac0a2 | 7441 | |
8d6275c0 | 7442 | NAME: wccp2_forwarding_method |
e313ab0a | 7443 | TYPE: wccp2_method |
8d6275c0 | 7444 | LOC: Config.Wccp2.forwarding_method |
451c4786 | 7445 | DEFAULT: gre |
8d6275c0 | 7446 | IFDEF: USE_WCCPv2 |
cccac0a2 | 7447 | DOC_START |
699acd19 | 7448 | WCCP2 allows the setting of forwarding methods between the |
8d6275c0 | 7449 | router/switch and the cache. Valid values are as follows: |
cccac0a2 | 7450 | |
451c4786 AJ |
7451 | gre - GRE encapsulation (forward the packet in a GRE/WCCP tunnel) |
7452 | l2 - L2 redirect (forward the packet using Layer 2/MAC rewriting) | |
cccac0a2 | 7453 | |
8d6275c0 | 7454 | Currently (as of IOS 12.4) cisco routers only support GRE. |
7455 | Cisco switches only support the L2 redirect assignment method. | |
cccac0a2 | 7456 | DOC_END |
7457 | ||
8d6275c0 | 7458 | NAME: wccp2_return_method |
e313ab0a | 7459 | TYPE: wccp2_method |
8d6275c0 | 7460 | LOC: Config.Wccp2.return_method |
451c4786 | 7461 | DEFAULT: gre |
8d6275c0 | 7462 | IFDEF: USE_WCCPv2 |
cccac0a2 | 7463 | DOC_START |
699acd19 | 7464 | WCCP2 allows the setting of return methods between the |
8d6275c0 | 7465 | router/switch and the cache for packets that the cache |
7466 | decides not to handle. Valid values are as follows: | |
cccac0a2 | 7467 | |
451c4786 AJ |
7468 | gre - GRE encapsulation (forward the packet in a GRE/WCCP tunnel) |
7469 | l2 - L2 redirect (forward the packet using Layer 2/MAC rewriting) | |
cccac0a2 | 7470 | |
8d6275c0 | 7471 | Currently (as of IOS 12.4) cisco routers only support GRE. |
7472 | Cisco switches only support the L2 redirect assignment. | |
cccac0a2 | 7473 | |
699acd19 | 7474 | If the "ip wccp redirect exclude in" command has been |
8d6275c0 | 7475 | enabled on the cache interface, then it is still safe for |
7476 | the proxy server to use a l2 redirect method even if this | |
7477 | option is set to GRE. | |
cccac0a2 | 7478 | DOC_END |
7479 | ||
8d6275c0 | 7480 | NAME: wccp2_assignment_method |
451c4786 | 7481 | TYPE: wccp2_amethod |
8d6275c0 | 7482 | LOC: Config.Wccp2.assignment_method |
451c4786 | 7483 | DEFAULT: hash |
8d6275c0 | 7484 | IFDEF: USE_WCCPv2 |
cccac0a2 | 7485 | DOC_START |
8d6275c0 | 7486 | WCCP2 allows the setting of methods to assign the WCCP hash |
7487 | Valid values are as follows: | |
cccac0a2 | 7488 | |
451c4786 | 7489 | hash - Hash assignment |
bb7a1781 | 7490 | mask - Mask assignment |
cccac0a2 | 7491 | |
8d6275c0 | 7492 | As a general rule, cisco routers support the hash assignment method |
7493 | and cisco switches support the mask assignment method. | |
7494 | DOC_END | |
cccac0a2 | 7495 | |
8d6275c0 | 7496 | NAME: wccp2_service |
7497 | TYPE: wccp2_service | |
7498 | LOC: Config.Wccp2.info | |
8d6275c0 | 7499 | DEFAULT_IF_NONE: standard 0 |
638402dd | 7500 | DEFAULT_DOC: Use the 'web-cache' standard service. |
8d6275c0 | 7501 | IFDEF: USE_WCCPv2 |
7502 | DOC_START | |
7503 | WCCP2 allows for multiple traffic services. There are two | |
7504 | types: "standard" and "dynamic". The standard type defines | |
7505 | one service id - http (id 0). The dynamic service ids can be from | |
7506 | 51 to 255 inclusive. In order to use a dynamic service id | |
7507 | one must define the type of traffic to be redirected; this is done | |
7508 | using the wccp2_service_info option. | |
7509 | ||
7510 | The "standard" type does not require a wccp2_service_info option, | |
7511 | just specifying the service id will suffice. | |
7512 | ||
7513 | MD5 service authentication can be enabled by adding | |
7514 | "password=<password>" to the end of this service declaration. | |
7515 | ||
7516 | Examples: | |
7517 | ||
7518 | wccp2_service standard 0 # for the 'web-cache' standard service | |
7519 | wccp2_service dynamic 80 # a dynamic service type which will be | |
7520 | # fleshed out with subsequent options. | |
7521 | wccp2_service standard 0 password=foo | |
8d6275c0 | 7522 | DOC_END |
7523 | ||
7524 | NAME: wccp2_service_info | |
7525 | TYPE: wccp2_service_info | |
7526 | LOC: Config.Wccp2.info | |
7527 | DEFAULT: none | |
7528 | IFDEF: USE_WCCPv2 | |
7529 | DOC_START | |
7530 | Dynamic WCCPv2 services require further information to define the | |
7531 | traffic you wish to have diverted. | |
7532 | ||
7533 | The format is: | |
7534 | ||
7535 | wccp2_service_info <id> protocol=<protocol> flags=<flag>,<flag>.. | |
7536 | priority=<priority> ports=<port>,<port>.. | |
7537 | ||
7538 | The relevant WCCPv2 flags: | |
7539 | + src_ip_hash, dst_ip_hash | |
005fe566 | 7540 | + source_port_hash, dst_port_hash |
8d6275c0 | 7541 | + src_ip_alt_hash, dst_ip_alt_hash |
7542 | + src_port_alt_hash, dst_port_alt_hash | |
7543 | + ports_source | |
7544 | ||
7545 | The port list can be one to eight entries. | |
7546 | ||
7547 | Example: | |
7548 | ||
7549 | wccp2_service_info 80 protocol=tcp flags=src_ip_hash,ports_source | |
7550 | priority=240 ports=80 | |
7551 | ||
7552 | Note: the service id must have been defined by a previous | |
7553 | 'wccp2_service dynamic <id>' entry. | |
7554 | DOC_END | |
7555 | ||
7556 | NAME: wccp2_weight | |
7557 | TYPE: int | |
7558 | LOC: Config.Wccp2.weight | |
7559 | DEFAULT: 10000 | |
7560 | IFDEF: USE_WCCPv2 | |
7561 | DOC_START | |
7562 | Each cache server gets assigned a set of the destination | |
7563 | hash proportional to their weight. | |
7564 | DOC_END | |
7565 | ||
7566 | NAME: wccp_address | |
7567 | TYPE: address | |
7568 | LOC: Config.Wccp.address | |
7569 | DEFAULT: 0.0.0.0 | |
638402dd | 7570 | DEFAULT_DOC: Address selected by the operating system. |
8d6275c0 | 7571 | IFDEF: USE_WCCP |
638402dd AJ |
7572 | DOC_START |
7573 | Use this option if you require WCCPv2 to use a specific | |
7574 | interface address. | |
7575 | ||
7576 | The default behavior is to not bind to any specific address. | |
7577 | DOC_END | |
df2eec10 | 7578 | |
8d6275c0 | 7579 | NAME: wccp2_address |
7580 | TYPE: address | |
7581 | LOC: Config.Wccp2.address | |
7582 | DEFAULT: 0.0.0.0 | |
638402dd | 7583 | DEFAULT_DOC: Address selected by the operating system. |
8d6275c0 | 7584 | IFDEF: USE_WCCPv2 |
7585 | DOC_START | |
7586 | Use this option if you require WCCP to use a specific | |
7587 | interface address. | |
7588 | ||
7589 | The default behavior is to not bind to any specific address. | |
7590 | DOC_END | |
7591 | ||
7592 | COMMENT_START | |
7593 | PERSISTENT CONNECTION HANDLING | |
7594 | ----------------------------------------------------------------------------- | |
7595 | ||
7596 | Also see "pconn_timeout" in the TIMEOUTS section | |
7597 | COMMENT_END | |
7598 | ||
7599 | NAME: client_persistent_connections | |
7600 | TYPE: onoff | |
7601 | LOC: Config.onoff.client_pconns | |
7602 | DEFAULT: on | |
638402dd AJ |
7603 | DOC_START |
7604 | Persistent connection support for clients. | |
7605 | Squid uses persistent connections (when allowed). You can use | |
7606 | this option to disable persistent connections with clients. | |
7607 | DOC_END | |
8d6275c0 | 7608 | |
7609 | NAME: server_persistent_connections | |
7610 | TYPE: onoff | |
7611 | LOC: Config.onoff.server_pconns | |
7612 | DEFAULT: on | |
7613 | DOC_START | |
638402dd AJ |
7614 | Persistent connection support for servers. |
7615 | Squid uses persistent connections (when allowed). You can use | |
7616 | this option to disable persistent connections with servers. | |
8d6275c0 | 7617 | DOC_END |
7618 | ||
7619 | NAME: persistent_connection_after_error | |
7620 | TYPE: onoff | |
7621 | LOC: Config.onoff.error_pconns | |
0fccfb7f | 7622 | DEFAULT: on |
8d6275c0 | 7623 | DOC_START |
7624 | With this directive the use of persistent connections after | |
7625 | HTTP errors can be disabled. Useful if you have clients | |
7626 | who fail to handle errors on persistent connections proper. | |
7627 | DOC_END | |
7628 | ||
7629 | NAME: detect_broken_pconn | |
7630 | TYPE: onoff | |
7631 | LOC: Config.onoff.detect_broken_server_pconns | |
7632 | DEFAULT: off | |
7633 | DOC_START | |
7634 | Some servers have been found to incorrectly signal the use | |
7635 | of HTTP/1.0 persistent connections even on replies not | |
7636 | compatible, causing significant delays. This server problem | |
7637 | has mostly been seen on redirects. | |
7638 | ||
7639 | By enabling this directive Squid attempts to detect such | |
7640 | broken replies and automatically assume the reply is finished | |
7641 | after 10 seconds timeout. | |
7642 | DOC_END | |
7643 | ||
7644 | COMMENT_START | |
7645 | CACHE DIGEST OPTIONS | |
7646 | ----------------------------------------------------------------------------- | |
7647 | COMMENT_END | |
7648 | ||
7649 | NAME: digest_generation | |
7650 | IFDEF: USE_CACHE_DIGESTS | |
7651 | TYPE: onoff | |
7652 | LOC: Config.onoff.digest_generation | |
7653 | DEFAULT: on | |
7654 | DOC_START | |
7655 | This controls whether the server will generate a Cache Digest | |
7656 | of its contents. By default, Cache Digest generation is | |
13e917b5 | 7657 | enabled if Squid is compiled with --enable-cache-digests defined. |
8d6275c0 | 7658 | DOC_END |
7659 | ||
7660 | NAME: digest_bits_per_entry | |
7661 | IFDEF: USE_CACHE_DIGESTS | |
7662 | TYPE: int | |
7663 | LOC: Config.digest.bits_per_entry | |
7664 | DEFAULT: 5 | |
7665 | DOC_START | |
7666 | This is the number of bits of the server's Cache Digest which | |
7667 | will be associated with the Digest entry for a given HTTP | |
7668 | Method and URL (public key) combination. The default is 5. | |
7669 | DOC_END | |
7670 | ||
7671 | NAME: digest_rebuild_period | |
7672 | IFDEF: USE_CACHE_DIGESTS | |
7673 | COMMENT: (seconds) | |
7674 | TYPE: time_t | |
7675 | LOC: Config.digest.rebuild_period | |
7676 | DEFAULT: 1 hour | |
7677 | DOC_START | |
749ceff8 | 7678 | This is the wait time between Cache Digest rebuilds. |
8d6275c0 | 7679 | DOC_END |
7680 | ||
7681 | NAME: digest_rewrite_period | |
7682 | COMMENT: (seconds) | |
7683 | IFDEF: USE_CACHE_DIGESTS | |
7684 | TYPE: time_t | |
7685 | LOC: Config.digest.rewrite_period | |
7686 | DEFAULT: 1 hour | |
7687 | DOC_START | |
749ceff8 | 7688 | This is the wait time between Cache Digest writes to |
8d6275c0 | 7689 | disk. |
7690 | DOC_END | |
7691 | ||
7692 | NAME: digest_swapout_chunk_size | |
7693 | COMMENT: (bytes) | |
7694 | TYPE: b_size_t | |
7695 | IFDEF: USE_CACHE_DIGESTS | |
7696 | LOC: Config.digest.swapout_chunk_size | |
7697 | DEFAULT: 4096 bytes | |
7698 | DOC_START | |
7699 | This is the number of bytes of the Cache Digest to write to | |
7700 | disk at a time. It defaults to 4096 bytes (4KB), the Squid | |
7701 | default swap page. | |
7702 | DOC_END | |
7703 | ||
7704 | NAME: digest_rebuild_chunk_percentage | |
7705 | COMMENT: (percent, 0-100) | |
7706 | IFDEF: USE_CACHE_DIGESTS | |
7707 | TYPE: int | |
7708 | LOC: Config.digest.rebuild_chunk_percentage | |
7709 | DEFAULT: 10 | |
7710 | DOC_START | |
7711 | This is the percentage of the Cache Digest to be scanned at a | |
7712 | time. By default it is set to 10% of the Cache Digest. | |
7713 | DOC_END | |
7714 | ||
1db9eacd | 7715 | COMMENT_START |
5473c134 | 7716 | SNMP OPTIONS |
1db9eacd | 7717 | ----------------------------------------------------------------------------- |
7718 | COMMENT_END | |
7719 | ||
5473c134 | 7720 | NAME: snmp_port |
ae870270 | 7721 | TYPE: u_short |
5473c134 | 7722 | LOC: Config.Port.snmp |
87630341 | 7723 | DEFAULT: 0 |
638402dd | 7724 | DEFAULT_DOC: SNMP disabled. |
5473c134 | 7725 | IFDEF: SQUID_SNMP |
8d6275c0 | 7726 | DOC_START |
87630341 | 7727 | The port number where Squid listens for SNMP requests. To enable |
7728 | SNMP support set this to a suitable port number. Port number | |
7729 | 3401 is often used for the Squid SNMP agent. By default it's | |
7730 | set to "0" (disabled) | |
e0855596 AJ |
7731 | |
7732 | Example: | |
7733 | snmp_port 3401 | |
8d6275c0 | 7734 | DOC_END |
7735 | ||
5473c134 | 7736 | NAME: snmp_access |
7737 | TYPE: acl_access | |
7738 | LOC: Config.accessList.snmp | |
638402dd AJ |
7739 | DEFAULT: none |
7740 | DEFAULT_DOC: Deny, unless rules exist in squid.conf. | |
5473c134 | 7741 | IFDEF: SQUID_SNMP |
8d6275c0 | 7742 | DOC_START |
5473c134 | 7743 | Allowing or denying access to the SNMP port. |
8d6275c0 | 7744 | |
5473c134 | 7745 | All access to the agent is denied by default. |
7746 | usage: | |
8d6275c0 | 7747 | |
5473c134 | 7748 | snmp_access allow|deny [!]aclname ... |
8d6275c0 | 7749 | |
b3567eb5 FC |
7750 | This clause only supports fast acl types. |
7751 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
638402dd | 7752 | |
5473c134 | 7753 | Example: |
7754 | snmp_access allow snmppublic localhost | |
7755 | snmp_access deny all | |
cccac0a2 | 7756 | DOC_END |
7757 | ||
5473c134 | 7758 | NAME: snmp_incoming_address |
7759 | TYPE: address | |
7760 | LOC: Config.Addrs.snmp_incoming | |
0eb08770 | 7761 | DEFAULT: any_addr |
638402dd | 7762 | DEFAULT_DOC: Accept SNMP packets from all machine interfaces. |
5473c134 | 7763 | IFDEF: SQUID_SNMP |
638402dd AJ |
7764 | DOC_START |
7765 | Just like 'udp_incoming_address', but for the SNMP port. | |
7766 | ||
7767 | snmp_incoming_address is used for the SNMP socket receiving | |
7768 | messages from SNMP agents. | |
7769 | ||
7770 | The default snmp_incoming_address is to listen on all | |
7771 | available network interfaces. | |
7772 | DOC_END | |
df2eec10 | 7773 | |
5473c134 | 7774 | NAME: snmp_outgoing_address |
7775 | TYPE: address | |
7776 | LOC: Config.Addrs.snmp_outgoing | |
0eb08770 | 7777 | DEFAULT: no_addr |
638402dd | 7778 | DEFAULT_DOC: Use snmp_incoming_address or an address selected by the operating system. |
5473c134 | 7779 | IFDEF: SQUID_SNMP |
cccac0a2 | 7780 | DOC_START |
638402dd | 7781 | Just like 'udp_outgoing_address', but for the SNMP port. |
cccac0a2 | 7782 | |
5473c134 | 7783 | snmp_outgoing_address is used for SNMP packets returned to SNMP |
7784 | agents. | |
cccac0a2 | 7785 | |
0eb08770 HN |
7786 | If snmp_outgoing_address is not set it will use the same socket |
7787 | as snmp_incoming_address. Only change this if you want to have | |
7788 | SNMP replies sent using another address than where this Squid | |
7789 | listens for SNMP queries. | |
cccac0a2 | 7790 | |
5473c134 | 7791 | NOTE, snmp_incoming_address and snmp_outgoing_address can not have |
638402dd | 7792 | the same value since they both use the same port. |
cccac0a2 | 7793 | DOC_END |
7794 | ||
5473c134 | 7795 | COMMENT_START |
7796 | ICP OPTIONS | |
7797 | ----------------------------------------------------------------------------- | |
7798 | COMMENT_END | |
7799 | ||
7800 | NAME: icp_port udp_port | |
ae870270 | 7801 | TYPE: u_short |
5473c134 | 7802 | DEFAULT: 0 |
638402dd | 7803 | DEFAULT_DOC: ICP disabled. |
5473c134 | 7804 | LOC: Config.Port.icp |
cccac0a2 | 7805 | DOC_START |
5473c134 | 7806 | The port number where Squid sends and receives ICP queries to |
7807 | and from neighbor caches. The standard UDP port for ICP is 3130. | |
e0855596 AJ |
7808 | |
7809 | Example: | |
7810 | icp_port @DEFAULT_ICP_PORT@ | |
cccac0a2 | 7811 | DOC_END |
7812 | ||
5473c134 | 7813 | NAME: htcp_port |
7814 | IFDEF: USE_HTCP | |
ae870270 | 7815 | TYPE: u_short |
87630341 | 7816 | DEFAULT: 0 |
638402dd | 7817 | DEFAULT_DOC: HTCP disabled. |
5473c134 | 7818 | LOC: Config.Port.htcp |
cccac0a2 | 7819 | DOC_START |
5473c134 | 7820 | The port number where Squid sends and receives HTCP queries to |
87630341 | 7821 | and from neighbor caches. To turn it on you want to set it to |
638402dd | 7822 | 4827. |
e0855596 AJ |
7823 | |
7824 | Example: | |
7825 | htcp_port 4827 | |
cccac0a2 | 7826 | DOC_END |
7827 | ||
7828 | NAME: log_icp_queries | |
7829 | COMMENT: on|off | |
7830 | TYPE: onoff | |
7831 | DEFAULT: on | |
7832 | LOC: Config.onoff.log_udp | |
7833 | DOC_START | |
7834 | If set, ICP queries are logged to access.log. You may wish | |
7835 | do disable this if your ICP load is VERY high to speed things | |
7836 | up or to simplify log analysis. | |
7837 | DOC_END | |
7838 | ||
5473c134 | 7839 | NAME: udp_incoming_address |
7840 | TYPE: address | |
7841 | LOC:Config.Addrs.udp_incoming | |
0eb08770 | 7842 | DEFAULT: any_addr |
638402dd | 7843 | DEFAULT_DOC: Accept packets from all machine interfaces. |
8524d4b2 | 7844 | DOC_START |
7845 | udp_incoming_address is used for UDP packets received from other | |
7846 | caches. | |
7847 | ||
7848 | The default behavior is to not bind to any specific address. | |
7849 | ||
7850 | Only change this if you want to have all UDP queries received on | |
7851 | a specific interface/address. | |
7852 | ||
7853 | NOTE: udp_incoming_address is used by the ICP, HTCP, and DNS | |
7854 | modules. Altering it will affect all of them in the same manner. | |
7855 | ||
7856 | see also; udp_outgoing_address | |
7857 | ||
7858 | NOTE, udp_incoming_address and udp_outgoing_address can not | |
7859 | have the same value since they both use the same port. | |
7860 | DOC_END | |
cccac0a2 | 7861 | |
5473c134 | 7862 | NAME: udp_outgoing_address |
7863 | TYPE: address | |
7864 | LOC: Config.Addrs.udp_outgoing | |
0eb08770 | 7865 | DEFAULT: no_addr |
638402dd | 7866 | DEFAULT_DOC: Use udp_incoming_address or an address selected by the operating system. |
cccac0a2 | 7867 | DOC_START |
8524d4b2 | 7868 | udp_outgoing_address is used for UDP packets sent out to other |
5473c134 | 7869 | caches. |
cccac0a2 | 7870 | |
5473c134 | 7871 | The default behavior is to not bind to any specific address. |
cccac0a2 | 7872 | |
8524d4b2 | 7873 | Instead it will use the same socket as udp_incoming_address. |
7874 | Only change this if you want to have UDP queries sent using another | |
7875 | address than where this Squid listens for UDP queries from other | |
5473c134 | 7876 | caches. |
7877 | ||
8524d4b2 | 7878 | NOTE: udp_outgoing_address is used by the ICP, HTCP, and DNS |
7879 | modules. Altering it will affect all of them in the same manner. | |
7880 | ||
7881 | see also; udp_incoming_address | |
7882 | ||
5473c134 | 7883 | NOTE, udp_incoming_address and udp_outgoing_address can not |
8524d4b2 | 7884 | have the same value since they both use the same port. |
cccac0a2 | 7885 | DOC_END |
7886 | ||
3d1e3e43 | 7887 | NAME: icp_hit_stale |
7888 | COMMENT: on|off | |
7889 | TYPE: onoff | |
7890 | DEFAULT: off | |
7891 | LOC: Config.onoff.icp_hit_stale | |
7892 | DOC_START | |
7893 | If you want to return ICP_HIT for stale cache objects, set this | |
7894 | option to 'on'. If you have sibling relationships with caches | |
7895 | in other administrative domains, this should be 'off'. If you only | |
7896 | have sibling relationships with caches under your control, | |
7897 | it is probably okay to set this to 'on'. | |
7898 | If set to 'on', your siblings should use the option "allow-miss" | |
7899 | on their cache_peer lines for connecting to you. | |
7900 | DOC_END | |
7901 | ||
5473c134 | 7902 | NAME: minimum_direct_hops |
cccac0a2 | 7903 | TYPE: int |
5473c134 | 7904 | DEFAULT: 4 |
7905 | LOC: Config.minDirectHops | |
cccac0a2 | 7906 | DOC_START |
5473c134 | 7907 | If using the ICMP pinging stuff, do direct fetches for sites |
7908 | which are no more than this many hops away. | |
cccac0a2 | 7909 | DOC_END |
7910 | ||
5473c134 | 7911 | NAME: minimum_direct_rtt |
638402dd | 7912 | COMMENT: (msec) |
5473c134 | 7913 | TYPE: int |
7914 | DEFAULT: 400 | |
7915 | LOC: Config.minDirectRtt | |
cccac0a2 | 7916 | DOC_START |
5473c134 | 7917 | If using the ICMP pinging stuff, do direct fetches for sites |
7918 | which are no more than this many rtt milliseconds away. | |
cccac0a2 | 7919 | DOC_END |
7920 | ||
cccac0a2 | 7921 | NAME: netdb_low |
7922 | TYPE: int | |
7923 | DEFAULT: 900 | |
7924 | LOC: Config.Netdb.low | |
638402dd AJ |
7925 | DOC_START |
7926 | The low water mark for the ICMP measurement database. | |
7927 | ||
7928 | Note: high watermark controlled by netdb_high directive. | |
7929 | ||
7930 | These watermarks are counts, not percents. The defaults are | |
7931 | (low) 900 and (high) 1000. When the high water mark is | |
7932 | reached, database entries will be deleted until the low | |
7933 | mark is reached. | |
7934 | DOC_END | |
cccac0a2 | 7935 | |
7936 | NAME: netdb_high | |
7937 | TYPE: int | |
7938 | DEFAULT: 1000 | |
7939 | LOC: Config.Netdb.high | |
7940 | DOC_START | |
638402dd AJ |
7941 | The high water mark for the ICMP measurement database. |
7942 | ||
7943 | Note: low watermark controlled by netdb_low directive. | |
7944 | ||
7945 | These watermarks are counts, not percents. The defaults are | |
7946 | (low) 900 and (high) 1000. When the high water mark is | |
7947 | reached, database entries will be deleted until the low | |
7948 | mark is reached. | |
cccac0a2 | 7949 | DOC_END |
7950 | ||
cccac0a2 | 7951 | NAME: netdb_ping_period |
7952 | TYPE: time_t | |
7953 | LOC: Config.Netdb.period | |
7954 | DEFAULT: 5 minutes | |
7955 | DOC_START | |
7956 | The minimum period for measuring a site. There will be at | |
7957 | least this much delay between successive pings to the same | |
7958 | network. The default is five minutes. | |
7959 | DOC_END | |
7960 | ||
cccac0a2 | 7961 | NAME: query_icmp |
7962 | COMMENT: on|off | |
7963 | TYPE: onoff | |
7964 | DEFAULT: off | |
7965 | LOC: Config.onoff.query_icmp | |
7966 | DOC_START | |
7967 | If you want to ask your peers to include ICMP data in their ICP | |
7968 | replies, enable this option. | |
7969 | ||
7970 | If your peer has configured Squid (during compilation) with | |
7f7db318 | 7971 | '--enable-icmp' that peer will send ICMP pings to origin server |
7972 | sites of the URLs it receives. If you enable this option the | |
cccac0a2 | 7973 | ICP replies from that peer will include the ICMP data (if available). |
7974 | Then, when choosing a parent cache, Squid will choose the parent with | |
7975 | the minimal RTT to the origin server. When this happens, the | |
7976 | hierarchy field of the access.log will be | |
7977 | "CLOSEST_PARENT_MISS". This option is off by default. | |
7978 | DOC_END | |
7979 | ||
7980 | NAME: test_reachability | |
7981 | COMMENT: on|off | |
7982 | TYPE: onoff | |
7983 | DEFAULT: off | |
7984 | LOC: Config.onoff.test_reachability | |
7985 | DOC_START | |
7986 | When this is 'on', ICP MISS replies will be ICP_MISS_NOFETCH | |
7987 | instead of ICP_MISS if the target host is NOT in the ICMP | |
7988 | database, or has a zero RTT. | |
7989 | DOC_END | |
7990 | ||
5473c134 | 7991 | NAME: icp_query_timeout |
7992 | COMMENT: (msec) | |
7993 | DEFAULT: 0 | |
638402dd | 7994 | DEFAULT_DOC: Dynamic detection. |
5473c134 | 7995 | TYPE: int |
7996 | LOC: Config.Timeout.icp_query | |
4c3ef9b2 | 7997 | DOC_START |
5473c134 | 7998 | Normally Squid will automatically determine an optimal ICP |
7999 | query timeout value based on the round-trip-time of recent ICP | |
8000 | queries. If you want to override the value determined by | |
8001 | Squid, set this 'icp_query_timeout' to a non-zero value. This | |
8002 | value is specified in MILLISECONDS, so, to use a 2-second | |
8003 | timeout (the old default), you would write: | |
4c3ef9b2 | 8004 | |
5473c134 | 8005 | icp_query_timeout 2000 |
4c3ef9b2 | 8006 | DOC_END |
8007 | ||
5473c134 | 8008 | NAME: maximum_icp_query_timeout |
8009 | COMMENT: (msec) | |
8010 | DEFAULT: 2000 | |
8011 | TYPE: int | |
8012 | LOC: Config.Timeout.icp_query_max | |
cccac0a2 | 8013 | DOC_START |
5473c134 | 8014 | Normally the ICP query timeout is determined dynamically. But |
8015 | sometimes it can lead to very large values (say 5 seconds). | |
8016 | Use this option to put an upper limit on the dynamic timeout | |
8017 | value. Do NOT use this option to always use a fixed (instead | |
8018 | of a dynamic) timeout value. To set a fixed timeout see the | |
8019 | 'icp_query_timeout' directive. | |
cccac0a2 | 8020 | DOC_END |
8021 | ||
5473c134 | 8022 | NAME: minimum_icp_query_timeout |
8023 | COMMENT: (msec) | |
8024 | DEFAULT: 5 | |
8025 | TYPE: int | |
8026 | LOC: Config.Timeout.icp_query_min | |
cccac0a2 | 8027 | DOC_START |
5473c134 | 8028 | Normally the ICP query timeout is determined dynamically. But |
8029 | sometimes it can lead to very small timeouts, even lower than | |
8030 | the normal latency variance on your link due to traffic. | |
8031 | Use this option to put an lower limit on the dynamic timeout | |
8032 | value. Do NOT use this option to always use a fixed (instead | |
8033 | of a dynamic) timeout value. To set a fixed timeout see the | |
8034 | 'icp_query_timeout' directive. | |
cccac0a2 | 8035 | DOC_END |
8036 | ||
5473c134 | 8037 | NAME: background_ping_rate |
8038 | COMMENT: time-units | |
8039 | TYPE: time_t | |
8040 | DEFAULT: 10 seconds | |
8041 | LOC: Config.backgroundPingRate | |
cccac0a2 | 8042 | DOC_START |
5473c134 | 8043 | Controls how often the ICP pings are sent to siblings that |
8044 | have background-ping set. | |
cccac0a2 | 8045 | DOC_END |
8046 | ||
5473c134 | 8047 | COMMENT_START |
8048 | MULTICAST ICP OPTIONS | |
8049 | ----------------------------------------------------------------------------- | |
8050 | COMMENT_END | |
8051 | ||
8052 | NAME: mcast_groups | |
8053 | TYPE: wordlist | |
8054 | LOC: Config.mcast_group_list | |
8c01ada0 | 8055 | DEFAULT: none |
8056 | DOC_START | |
5473c134 | 8057 | This tag specifies a list of multicast groups which your server |
8058 | should join to receive multicasted ICP queries. | |
8c01ada0 | 8059 | |
5473c134 | 8060 | NOTE! Be very careful what you put here! Be sure you |
8061 | understand the difference between an ICP _query_ and an ICP | |
8062 | _reply_. This option is to be set only if you want to RECEIVE | |
8063 | multicast queries. Do NOT set this option to SEND multicast | |
8064 | ICP (use cache_peer for that). ICP replies are always sent via | |
8065 | unicast, so this option does not affect whether or not you will | |
8066 | receive replies from multicast group members. | |
8c01ada0 | 8067 | |
5473c134 | 8068 | You must be very careful to NOT use a multicast address which |
8069 | is already in use by another group of caches. | |
8c01ada0 | 8070 | |
5473c134 | 8071 | If you are unsure about multicast, please read the Multicast |
8072 | chapter in the Squid FAQ (http://www.squid-cache.org/FAQ/). | |
8c01ada0 | 8073 | |
5473c134 | 8074 | Usage: mcast_groups 239.128.16.128 224.0.1.20 |
8c01ada0 | 8075 | |
5473c134 | 8076 | By default, Squid doesn't listen on any multicast groups. |
8077 | DOC_END | |
8c01ada0 | 8078 | |
5473c134 | 8079 | NAME: mcast_miss_addr |
8080 | IFDEF: MULTICAST_MISS_STREAM | |
8081 | TYPE: address | |
8082 | LOC: Config.mcast_miss.addr | |
0eb08770 | 8083 | DEFAULT: no_addr |
638402dd | 8084 | DEFAULT_DOC: disabled. |
5473c134 | 8085 | DOC_START |
8086 | If you enable this option, every "cache miss" URL will | |
8087 | be sent out on the specified multicast address. | |
cccac0a2 | 8088 | |
5473c134 | 8089 | Do not enable this option unless you are are absolutely |
8090 | certain you understand what you are doing. | |
cccac0a2 | 8091 | DOC_END |
8092 | ||
5473c134 | 8093 | NAME: mcast_miss_ttl |
8094 | IFDEF: MULTICAST_MISS_STREAM | |
ae870270 | 8095 | TYPE: u_short |
5473c134 | 8096 | LOC: Config.mcast_miss.ttl |
8097 | DEFAULT: 16 | |
cccac0a2 | 8098 | DOC_START |
5473c134 | 8099 | This is the time-to-live value for packets multicasted |
8100 | when multicasting off cache miss URLs is enabled. By | |
8101 | default this is set to 'site scope', i.e. 16. | |
8102 | DOC_END | |
cccac0a2 | 8103 | |
5473c134 | 8104 | NAME: mcast_miss_port |
8105 | IFDEF: MULTICAST_MISS_STREAM | |
ae870270 | 8106 | TYPE: u_short |
5473c134 | 8107 | LOC: Config.mcast_miss.port |
8108 | DEFAULT: 3135 | |
8109 | DOC_START | |
8110 | This is the port number to be used in conjunction with | |
8111 | 'mcast_miss_addr'. | |
8112 | DOC_END | |
cccac0a2 | 8113 | |
5473c134 | 8114 | NAME: mcast_miss_encode_key |
8115 | IFDEF: MULTICAST_MISS_STREAM | |
8116 | TYPE: string | |
8117 | LOC: Config.mcast_miss.encode_key | |
8118 | DEFAULT: XXXXXXXXXXXXXXXX | |
8119 | DOC_START | |
8120 | The URLs that are sent in the multicast miss stream are | |
8121 | encrypted. This is the encryption key. | |
8122 | DOC_END | |
8c01ada0 | 8123 | |
5473c134 | 8124 | NAME: mcast_icp_query_timeout |
8125 | COMMENT: (msec) | |
8126 | DEFAULT: 2000 | |
8127 | TYPE: int | |
8128 | LOC: Config.Timeout.mcast_icp_query | |
8129 | DOC_START | |
8130 | For multicast peers, Squid regularly sends out ICP "probes" to | |
8131 | count how many other peers are listening on the given multicast | |
8132 | address. This value specifies how long Squid should wait to | |
8133 | count all the replies. The default is 2000 msec, or 2 | |
8134 | seconds. | |
cccac0a2 | 8135 | DOC_END |
8136 | ||
5473c134 | 8137 | COMMENT_START |
8138 | INTERNAL ICON OPTIONS | |
8139 | ----------------------------------------------------------------------------- | |
8140 | COMMENT_END | |
8141 | ||
cccac0a2 | 8142 | NAME: icon_directory |
8143 | TYPE: string | |
8144 | LOC: Config.icons.directory | |
8145 | DEFAULT: @DEFAULT_ICON_DIR@ | |
8146 | DOC_START | |
8147 | Where the icons are stored. These are normally kept in | |
8148 | @DEFAULT_ICON_DIR@ | |
8149 | DOC_END | |
8150 | ||
f024c970 | 8151 | NAME: global_internal_static |
8152 | TYPE: onoff | |
8153 | LOC: Config.onoff.global_internal_static | |
8154 | DEFAULT: on | |
8155 | DOC_START | |
8156 | This directive controls is Squid should intercept all requests for | |
8157 | /squid-internal-static/ no matter which host the URL is requesting | |
8158 | (default on setting), or if nothing special should be done for | |
8159 | such URLs (off setting). The purpose of this directive is to make | |
8160 | icons etc work better in complex cache hierarchies where it may | |
8161 | not always be possible for all corners in the cache mesh to reach | |
8162 | the server generating a directory listing. | |
8163 | DOC_END | |
8164 | ||
5473c134 | 8165 | NAME: short_icon_urls |
8166 | TYPE: onoff | |
8167 | LOC: Config.icons.use_short_names | |
8168 | DEFAULT: on | |
8169 | DOC_START | |
8170 | If this is enabled Squid will use short URLs for icons. | |
8171 | If disabled it will revert to the old behavior of including | |
8172 | it's own name and port in the URL. | |
8173 | ||
8174 | If you run a complex cache hierarchy with a mix of Squid and | |
8175 | other proxies you may need to disable this directive. | |
8176 | DOC_END | |
8177 | ||
8178 | COMMENT_START | |
8179 | ERROR PAGE OPTIONS | |
8180 | ----------------------------------------------------------------------------- | |
8181 | COMMENT_END | |
8182 | ||
8183 | NAME: error_directory | |
8184 | TYPE: string | |
8185 | LOC: Config.errorDirectory | |
43000484 | 8186 | DEFAULT: none |
638402dd | 8187 | DEFAULT_DOC: Send error pages in the clients preferred language |
5473c134 | 8188 | DOC_START |
8189 | If you wish to create your own versions of the default | |
43000484 AJ |
8190 | error files to customize them to suit your company copy |
8191 | the error/template files to another directory and point | |
8192 | this tag at them. | |
8193 | ||
8194 | WARNING: This option will disable multi-language support | |
8195 | on error pages if used. | |
5473c134 | 8196 | |
8197 | The squid developers are interested in making squid available in | |
8198 | a wide variety of languages. If you are making translations for a | |
43000484 | 8199 | language that Squid does not currently provide please consider |
5473c134 | 8200 | contributing your translation back to the project. |
43000484 AJ |
8201 | http://wiki.squid-cache.org/Translations |
8202 | ||
8203 | The squid developers working on translations are happy to supply drop-in | |
8204 | translated error files in exchange for any new language contributions. | |
8205 | DOC_END | |
8206 | ||
8207 | NAME: error_default_language | |
8208 | IFDEF: USE_ERR_LOCALES | |
8209 | TYPE: string | |
8210 | LOC: Config.errorDefaultLanguage | |
8211 | DEFAULT: none | |
638402dd | 8212 | DEFAULT_DOC: Generate English language pages. |
43000484 AJ |
8213 | DOC_START |
8214 | Set the default language which squid will send error pages in | |
8215 | if no existing translation matches the clients language | |
8216 | preferences. | |
8217 | ||
8218 | If unset (default) generic English will be used. | |
8219 | ||
8220 | The squid developers are interested in making squid available in | |
8221 | a wide variety of languages. If you are interested in making | |
8222 | translations for any language see the squid wiki for details. | |
8223 | http://wiki.squid-cache.org/Translations | |
5473c134 | 8224 | DOC_END |
8225 | ||
c411820c AJ |
8226 | NAME: error_log_languages |
8227 | IFDEF: USE_ERR_LOCALES | |
8228 | TYPE: onoff | |
8229 | LOC: Config.errorLogMissingLanguages | |
8230 | DEFAULT: on | |
8231 | DOC_START | |
8232 | Log to cache.log what languages users are attempting to | |
8233 | auto-negotiate for translations. | |
8234 | ||
8235 | Successful negotiations are not logged. Only failures | |
8236 | have meaning to indicate that Squid may need an upgrade | |
0c49f10e | 8237 | of its error page translations. |
c411820c AJ |
8238 | DOC_END |
8239 | ||
5b52cb6c AJ |
8240 | NAME: err_page_stylesheet |
8241 | TYPE: string | |
8242 | LOC: Config.errorStylesheet | |
8243 | DEFAULT: @DEFAULT_CONFIG_DIR@/errorpage.css | |
8244 | DOC_START | |
8245 | CSS Stylesheet to pattern the display of Squid default error pages. | |
8246 | ||
8247 | For information on CSS see http://www.w3.org/Style/CSS/ | |
8248 | DOC_END | |
8249 | ||
5473c134 | 8250 | NAME: err_html_text |
8251 | TYPE: eol | |
8252 | LOC: Config.errHtmlText | |
8253 | DEFAULT: none | |
8254 | DOC_START | |
8255 | HTML text to include in error messages. Make this a "mailto" | |
8256 | URL to your admin address, or maybe just a link to your | |
8257 | organizations Web page. | |
8258 | ||
8259 | To include this in your error messages, you must rewrite | |
8260 | the error template files (found in the "errors" directory). | |
8261 | Wherever you want the 'err_html_text' line to appear, | |
8262 | insert a %L tag in the error template file. | |
8263 | DOC_END | |
8264 | ||
8265 | NAME: email_err_data | |
8266 | COMMENT: on|off | |
8267 | TYPE: onoff | |
8268 | LOC: Config.onoff.emailErrData | |
8269 | DEFAULT: on | |
8270 | DOC_START | |
8271 | If enabled, information about the occurred error will be | |
8272 | included in the mailto links of the ERR pages (if %W is set) | |
8273 | so that the email body contains the data. | |
8274 | Syntax is <A HREF="mailto:%w%W">%w</A> | |
8275 | DOC_END | |
8276 | ||
8277 | NAME: deny_info | |
8278 | TYPE: denyinfo | |
8279 | LOC: Config.denyInfoList | |
8280 | DEFAULT: none | |
8281 | DOC_START | |
8282 | Usage: deny_info err_page_name acl | |
8283 | or deny_info http://... acl | |
43000484 | 8284 | or deny_info TCP_RESET acl |
5473c134 | 8285 | |
8286 | This can be used to return a ERR_ page for requests which | |
8287 | do not pass the 'http_access' rules. Squid remembers the last | |
8288 | acl it evaluated in http_access, and if a 'deny_info' line exists | |
8289 | for that ACL Squid returns a corresponding error page. | |
8290 | ||
8291 | The acl is typically the last acl on the http_access deny line which | |
8292 | denied access. The exceptions to this rule are: | |
8293 | - When Squid needs to request authentication credentials. It's then | |
8294 | the first authentication related acl encountered | |
8295 | - When none of the http_access lines matches. It's then the last | |
8296 | acl processed on the last http_access line. | |
3af10ac0 AR |
8297 | - When the decision to deny access was made by an adaptation service, |
8298 | the acl name is the corresponding eCAP or ICAP service_name. | |
5473c134 | 8299 | |
43000484 AJ |
8300 | NP: If providing your own custom error pages with error_directory |
8301 | you may also specify them by your custom file name: | |
8302 | Example: deny_info ERR_CUSTOM_ACCESS_DENIED bad_guys | |
5473c134 | 8303 | |
aed9a15b AJ |
8304 | By defaut Squid will send "403 Forbidden". A different 4xx or 5xx |
8305 | may be specified by prefixing the file name with the code and a colon. | |
8306 | e.g. 404:ERR_CUSTOM_ACCESS_DENIED | |
8307 | ||
5473c134 | 8308 | Alternatively you can tell Squid to reset the TCP connection |
8309 | by specifying TCP_RESET. | |
15b02e9a AJ |
8310 | |
8311 | Or you can specify an error URL or URL pattern. The browsers will | |
aed9a15b AJ |
8312 | get redirected to the specified URL after formatting tags have |
8313 | been replaced. Redirect will be done with 302 or 307 according to | |
8314 | HTTP/1.1 specs. A different 3xx code may be specified by prefixing | |
8315 | the URL. e.g. 303:http://example.com/ | |
15b02e9a AJ |
8316 | |
8317 | URL FORMAT TAGS: | |
8318 | %a - username (if available. Password NOT included) | |
8319 | %B - FTP path URL | |
8320 | %e - Error number | |
8321 | %E - Error description | |
8322 | %h - Squid hostname | |
8323 | %H - Request domain name | |
8324 | %i - Client IP Address | |
8325 | %M - Request Method | |
05dbf66c | 8326 | %O - Unescaped message result from external ACL helper |
15b02e9a AJ |
8327 | %o - Message result from external ACL helper |
8328 | %p - Request Port number | |
8329 | %P - Request Protocol name | |
8330 | %R - Request URL path | |
8331 | %T - Timestamp in RFC 1123 format | |
8332 | %U - Full canonical URL from client | |
8333 | (HTTPS URLs terminate with *) | |
8334 | %u - Full canonical URL from client | |
8335 | %w - Admin email from squid.conf | |
e4a8468d | 8336 | %x - Error name |
15b02e9a AJ |
8337 | %% - Literal percent (%) code |
8338 | ||
5473c134 | 8339 | DOC_END |
8340 | ||
8341 | COMMENT_START | |
8342 | OPTIONS INFLUENCING REQUEST FORWARDING | |
8343 | ----------------------------------------------------------------------------- | |
8344 | COMMENT_END | |
8345 | ||
8346 | NAME: nonhierarchical_direct | |
e72a0ec0 | 8347 | TYPE: onoff |
5473c134 | 8348 | LOC: Config.onoff.nonhierarchical_direct |
e72a0ec0 | 8349 | DEFAULT: on |
8350 | DOC_START | |
5473c134 | 8351 | By default, Squid will send any non-hierarchical requests |
9967aef6 | 8352 | (not cacheable request type) direct to origin servers. |
e72a0ec0 | 8353 | |
638402dd | 8354 | When this is set to "off", Squid will prefer to send these |
5473c134 | 8355 | requests to parents. |
0b0cfcf2 | 8356 | |
5473c134 | 8357 | Note that in most configurations, by turning this off you will only |
8358 | add latency to these request without any improvement in global hit | |
8359 | ratio. | |
0b0cfcf2 | 8360 | |
638402dd AJ |
8361 | This option only sets a preference. If the parent is unavailable a |
8362 | direct connection to the origin server may still be attempted. To | |
8363 | completely prevent direct connections use never_direct. | |
8d6275c0 | 8364 | DOC_END |
0b0cfcf2 | 8365 | |
5473c134 | 8366 | NAME: prefer_direct |
8d6275c0 | 8367 | TYPE: onoff |
5473c134 | 8368 | LOC: Config.onoff.prefer_direct |
8d6275c0 | 8369 | DEFAULT: off |
8370 | DOC_START | |
5473c134 | 8371 | Normally Squid tries to use parents for most requests. If you for some |
8372 | reason like it to first try going direct and only use a parent if | |
8373 | going direct fails set this to on. | |
0b0cfcf2 | 8374 | |
5473c134 | 8375 | By combining nonhierarchical_direct off and prefer_direct on you |
8376 | can set up Squid to use a parent as a backup path if going direct | |
8377 | fails. | |
8378 | ||
8379 | Note: If you want Squid to use parents for all requests see | |
8380 | the never_direct directive. prefer_direct only modifies how Squid | |
8381 | acts on cacheable requests. | |
cccac0a2 | 8382 | DOC_END |
8383 | ||
96598f93 AJ |
8384 | NAME: cache_miss_revalidate |
8385 | COMMENT: on|off | |
8386 | TYPE: onoff | |
8387 | DEFAULT: on | |
8388 | LOC: Config.onoff.cache_miss_revalidate | |
8389 | DOC_START | |
2d4eefd9 AJ |
8390 | RFC 7232 defines a conditional request mechanism to prevent |
8391 | response objects being unnecessarily transferred over the network. | |
8392 | If that mechanism is used by the client and a cache MISS occurs | |
8393 | it can prevent new cache entries being created. | |
8394 | ||
8395 | This option determines whether Squid on cache MISS will pass the | |
8396 | client revalidation request to the server or tries to fetch new | |
8397 | content for caching. It can be useful while the cache is mostly | |
8398 | empty to more quickly have the cache populated by generating | |
8399 | non-conditional GETs. | |
96598f93 AJ |
8400 | |
8401 | When set to 'on' (default), Squid will pass all client If-* headers | |
2d4eefd9 AJ |
8402 | to the server. This permits server responses without a cacheable |
8403 | payload to be delivered and on MISS no new cache entry is created. | |
96598f93 AJ |
8404 | |
8405 | When set to 'off' and if the request is cacheable, Squid will | |
8406 | remove the clients If-Modified-Since and If-None-Match headers from | |
2d4eefd9 AJ |
8407 | the request sent to the server. This requests a 200 status response |
8408 | from the server to create a new cache entry with. | |
96598f93 AJ |
8409 | DOC_END |
8410 | ||
5473c134 | 8411 | NAME: always_direct |
8d6275c0 | 8412 | TYPE: acl_access |
5473c134 | 8413 | LOC: Config.accessList.AlwaysDirect |
0b0cfcf2 | 8414 | DEFAULT: none |
638402dd | 8415 | DEFAULT_DOC: Prevent any cache_peer being used for this request. |
0b0cfcf2 | 8416 | DOC_START |
5473c134 | 8417 | Usage: always_direct allow|deny [!]aclname ... |
0b0cfcf2 | 8418 | |
5473c134 | 8419 | Here you can use ACL elements to specify requests which should |
8420 | ALWAYS be forwarded by Squid to the origin servers without using | |
8421 | any peers. For example, to always directly forward requests for | |
8422 | local servers ignoring any parents or siblings you may have use | |
8423 | something like: | |
0b0cfcf2 | 8424 | |
5473c134 | 8425 | acl local-servers dstdomain my.domain.net |
8426 | always_direct allow local-servers | |
0b0cfcf2 | 8427 | |
5473c134 | 8428 | To always forward FTP requests directly, use |
f16fbc82 | 8429 | |
5473c134 | 8430 | acl FTP proto FTP |
8431 | always_direct allow FTP | |
cccac0a2 | 8432 | |
5473c134 | 8433 | NOTE: There is a similar, but opposite option named |
8434 | 'never_direct'. You need to be aware that "always_direct deny | |
8435 | foo" is NOT the same thing as "never_direct allow foo". You | |
8436 | may need to use a deny rule to exclude a more-specific case of | |
8437 | some other rule. Example: | |
8d6275c0 | 8438 | |
5473c134 | 8439 | acl local-external dstdomain external.foo.net |
8440 | acl local-servers dstdomain .foo.net | |
8441 | always_direct deny local-external | |
8442 | always_direct allow local-servers | |
8d6275c0 | 8443 | |
5473c134 | 8444 | NOTE: If your goal is to make the client forward the request |
8445 | directly to the origin server bypassing Squid then this needs | |
8446 | to be done in the client configuration. Squid configuration | |
8447 | can only tell Squid how Squid should fetch the object. | |
8d6275c0 | 8448 | |
5473c134 | 8449 | NOTE: This directive is not related to caching. The replies |
8450 | is cached as usual even if you use always_direct. To not cache | |
b3567eb5 | 8451 | the replies see the 'cache' directive. |
5473c134 | 8452 | |
b3567eb5 FC |
8453 | This clause supports both fast and slow acl types. |
8454 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
cccac0a2 | 8455 | DOC_END |
0976f8db | 8456 | |
5473c134 | 8457 | NAME: never_direct |
8458 | TYPE: acl_access | |
8459 | LOC: Config.accessList.NeverDirect | |
8460 | DEFAULT: none | |
638402dd | 8461 | DEFAULT_DOC: Allow DNS results to be used for this request. |
8d6275c0 | 8462 | DOC_START |
5473c134 | 8463 | Usage: never_direct allow|deny [!]aclname ... |
8464 | ||
8465 | never_direct is the opposite of always_direct. Please read | |
8466 | the description for always_direct if you have not already. | |
8467 | ||
8468 | With 'never_direct' you can use ACL elements to specify | |
8469 | requests which should NEVER be forwarded directly to origin | |
8470 | servers. For example, to force the use of a proxy for all | |
8471 | requests, except those in your local domain use something like: | |
8472 | ||
8473 | acl local-servers dstdomain .foo.net | |
5473c134 | 8474 | never_direct deny local-servers |
8475 | never_direct allow all | |
8476 | ||
8477 | or if Squid is inside a firewall and there are local intranet | |
8478 | servers inside the firewall use something like: | |
8479 | ||
8480 | acl local-intranet dstdomain .foo.net | |
8481 | acl local-external dstdomain external.foo.net | |
8482 | always_direct deny local-external | |
8483 | always_direct allow local-intranet | |
8484 | never_direct allow all | |
8485 | ||
b3567eb5 FC |
8486 | This clause supports both fast and slow acl types. |
8487 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
8d6275c0 | 8488 | DOC_END |
0976f8db | 8489 | |
5473c134 | 8490 | COMMENT_START |
8491 | ADVANCED NETWORKING OPTIONS | |
8492 | ----------------------------------------------------------------------------- | |
8493 | COMMENT_END | |
8494 | ||
65d448bc | 8495 | NAME: incoming_udp_average incoming_icp_average |
cccac0a2 | 8496 | TYPE: int |
8497 | DEFAULT: 6 | |
65d448bc AJ |
8498 | LOC: Config.comm_incoming.udp.average |
8499 | DOC_START | |
8500 | Heavy voodoo here. I can't even believe you are reading this. | |
8501 | Are you crazy? Don't even think about adjusting these unless | |
8502 | you understand the algorithms in comm_select.c first! | |
8503 | DOC_END | |
cccac0a2 | 8504 | |
65d448bc | 8505 | NAME: incoming_tcp_average incoming_http_average |
cccac0a2 | 8506 | TYPE: int |
8507 | DEFAULT: 4 | |
65d448bc AJ |
8508 | LOC: Config.comm_incoming.tcp.average |
8509 | DOC_START | |
8510 | Heavy voodoo here. I can't even believe you are reading this. | |
8511 | Are you crazy? Don't even think about adjusting these unless | |
8512 | you understand the algorithms in comm_select.c first! | |
8513 | DOC_END | |
cccac0a2 | 8514 | |
8515 | NAME: incoming_dns_average | |
8516 | TYPE: int | |
8517 | DEFAULT: 4 | |
65d448bc AJ |
8518 | LOC: Config.comm_incoming.dns.average |
8519 | DOC_START | |
8520 | Heavy voodoo here. I can't even believe you are reading this. | |
8521 | Are you crazy? Don't even think about adjusting these unless | |
8522 | you understand the algorithms in comm_select.c first! | |
8523 | DOC_END | |
cccac0a2 | 8524 | |
65d448bc | 8525 | NAME: min_udp_poll_cnt min_icp_poll_cnt |
cccac0a2 | 8526 | TYPE: int |
8527 | DEFAULT: 8 | |
65d448bc AJ |
8528 | LOC: Config.comm_incoming.udp.min_poll |
8529 | DOC_START | |
8530 | Heavy voodoo here. I can't even believe you are reading this. | |
8531 | Are you crazy? Don't even think about adjusting these unless | |
8532 | you understand the algorithms in comm_select.c first! | |
8533 | DOC_END | |
cccac0a2 | 8534 | |
8535 | NAME: min_dns_poll_cnt | |
8536 | TYPE: int | |
8537 | DEFAULT: 8 | |
65d448bc AJ |
8538 | LOC: Config.comm_incoming.dns.min_poll |
8539 | DOC_START | |
8540 | Heavy voodoo here. I can't even believe you are reading this. | |
8541 | Are you crazy? Don't even think about adjusting these unless | |
8542 | you understand the algorithms in comm_select.c first! | |
8543 | DOC_END | |
cccac0a2 | 8544 | |
65d448bc | 8545 | NAME: min_tcp_poll_cnt min_http_poll_cnt |
cccac0a2 | 8546 | TYPE: int |
8547 | DEFAULT: 8 | |
65d448bc | 8548 | LOC: Config.comm_incoming.tcp.min_poll |
cccac0a2 | 8549 | DOC_START |
5473c134 | 8550 | Heavy voodoo here. I can't even believe you are reading this. |
8551 | Are you crazy? Don't even think about adjusting these unless | |
8552 | you understand the algorithms in comm_select.c first! | |
8553 | DOC_END | |
8554 | ||
8555 | NAME: accept_filter | |
5473c134 | 8556 | TYPE: string |
8557 | DEFAULT: none | |
8558 | LOC: Config.accept_filter | |
8559 | DOC_START | |
0b4d4be5 | 8560 | FreeBSD: |
8561 | ||
5473c134 | 8562 | The name of an accept(2) filter to install on Squid's |
8563 | listen socket(s). This feature is perhaps specific to | |
8564 | FreeBSD and requires support in the kernel. | |
8565 | ||
8566 | The 'httpready' filter delays delivering new connections | |
2324cda2 | 8567 | to Squid until a full HTTP request has been received. |
0b4d4be5 | 8568 | See the accf_http(9) man page for details. |
8569 | ||
8570 | The 'dataready' filter delays delivering new connections | |
8571 | to Squid until there is some data to process. | |
8572 | See the accf_dataready(9) man page for details. | |
8573 | ||
8574 | Linux: | |
8575 | ||
8576 | The 'data' filter delays delivering of new connections | |
8577 | to Squid until there is some data to process by TCP_ACCEPT_DEFER. | |
8578 | You may optionally specify a number of seconds to wait by | |
8579 | 'data=N' where N is the number of seconds. Defaults to 30 | |
8580 | if not specified. See the tcp(7) man page for details. | |
5473c134 | 8581 | EXAMPLE: |
0b4d4be5 | 8582 | # FreeBSD |
5473c134 | 8583 | accept_filter httpready |
0b4d4be5 | 8584 | # Linux |
8585 | accept_filter data | |
5473c134 | 8586 | DOC_END |
8587 | ||
ab2ecb0e AJ |
8588 | NAME: client_ip_max_connections |
8589 | TYPE: int | |
8590 | LOC: Config.client_ip_max_connections | |
8591 | DEFAULT: -1 | |
638402dd | 8592 | DEFAULT_DOC: No limit. |
ab2ecb0e AJ |
8593 | DOC_START |
8594 | Set an absolute limit on the number of connections a single | |
8595 | client IP can use. Any more than this and Squid will begin to drop | |
8596 | new connections from the client until it closes some links. | |
8597 | ||
8598 | Note that this is a global limit. It affects all HTTP, HTCP, Gopher and FTP | |
8599 | connections from the client. For finer control use the ACL access controls. | |
8600 | ||
8601 | Requires client_db to be enabled (the default). | |
8602 | ||
8603 | WARNING: This may noticably slow down traffic received via external proxies | |
8604 | or NAT devices and cause them to rebound error messages back to their clients. | |
8605 | DOC_END | |
8606 | ||
5473c134 | 8607 | NAME: tcp_recv_bufsize |
8608 | COMMENT: (bytes) | |
8609 | TYPE: b_size_t | |
8610 | DEFAULT: 0 bytes | |
638402dd | 8611 | DEFAULT_DOC: Use operating system TCP defaults. |
5473c134 | 8612 | LOC: Config.tcpRcvBufsz |
8613 | DOC_START | |
8614 | Size of receive buffer to set for TCP sockets. Probably just | |
638402dd AJ |
8615 | as easy to change your kernel's default. |
8616 | Omit from squid.conf to use the default buffer size. | |
5473c134 | 8617 | DOC_END |
8618 | ||
8619 | COMMENT_START | |
8620 | ICAP OPTIONS | |
8621 | ----------------------------------------------------------------------------- | |
8622 | COMMENT_END | |
8623 | ||
8624 | NAME: icap_enable | |
8625 | TYPE: onoff | |
8626 | IFDEF: ICAP_CLIENT | |
8627 | COMMENT: on|off | |
26cc52cb | 8628 | LOC: Adaptation::Icap::TheConfig.onoff |
5473c134 | 8629 | DEFAULT: off |
8630 | DOC_START | |
53e738c6 | 8631 | If you want to enable the ICAP module support, set this to on. |
5473c134 | 8632 | DOC_END |
8633 | ||
8634 | NAME: icap_connect_timeout | |
8635 | TYPE: time_t | |
8636 | DEFAULT: none | |
26cc52cb | 8637 | LOC: Adaptation::Icap::TheConfig.connect_timeout_raw |
5473c134 | 8638 | IFDEF: ICAP_CLIENT |
8639 | DOC_START | |
8640 | This parameter specifies how long to wait for the TCP connect to | |
8641 | the requested ICAP server to complete before giving up and either | |
8642 | terminating the HTTP transaction or bypassing the failure. | |
8643 | ||
8644 | The default for optional services is peer_connect_timeout. | |
8645 | The default for essential services is connect_timeout. | |
8646 | If this option is explicitly set, its value applies to all services. | |
8647 | DOC_END | |
8648 | ||
8649 | NAME: icap_io_timeout | |
8650 | COMMENT: time-units | |
8651 | TYPE: time_t | |
8652 | DEFAULT: none | |
638402dd | 8653 | DEFAULT_DOC: Use read_timeout. |
26cc52cb | 8654 | LOC: Adaptation::Icap::TheConfig.io_timeout_raw |
5473c134 | 8655 | IFDEF: ICAP_CLIENT |
8656 | DOC_START | |
8657 | This parameter specifies how long to wait for an I/O activity on | |
8658 | an established, active ICAP connection before giving up and | |
8659 | either terminating the HTTP transaction or bypassing the | |
8660 | failure. | |
5473c134 | 8661 | DOC_END |
8662 | ||
8663 | NAME: icap_service_failure_limit | |
8277060a CT |
8664 | COMMENT: limit [in memory-depth time-units] |
8665 | TYPE: icap_service_failure_limit | |
5473c134 | 8666 | IFDEF: ICAP_CLIENT |
8277060a | 8667 | LOC: Adaptation::Icap::TheConfig |
5473c134 | 8668 | DEFAULT: 10 |
8669 | DOC_START | |
8670 | The limit specifies the number of failures that Squid tolerates | |
8671 | when establishing a new TCP connection with an ICAP service. If | |
8672 | the number of failures exceeds the limit, the ICAP service is | |
8673 | not used for new ICAP requests until it is time to refresh its | |
8277060a | 8674 | OPTIONS. |
5473c134 | 8675 | |
8676 | A negative value disables the limit. Without the limit, an ICAP | |
8677 | service will not be considered down due to connectivity failures | |
8678 | between ICAP OPTIONS requests. | |
8277060a CT |
8679 | |
8680 | Squid forgets ICAP service failures older than the specified | |
8681 | value of memory-depth. The memory fading algorithm | |
8682 | is approximate because Squid does not remember individual | |
8683 | errors but groups them instead, splitting the option | |
8684 | value into ten time slots of equal length. | |
8685 | ||
8686 | When memory-depth is 0 and by default this option has no | |
8687 | effect on service failure expiration. | |
8688 | ||
8689 | Squid always forgets failures when updating service settings | |
8690 | using an ICAP OPTIONS transaction, regardless of this option | |
8691 | setting. | |
8692 | ||
8693 | For example, | |
8694 | # suspend service usage after 10 failures in 5 seconds: | |
8695 | icap_service_failure_limit 10 in 5 seconds | |
cccac0a2 | 8696 | DOC_END |
8697 | ||
5473c134 | 8698 | NAME: icap_service_revival_delay |
cccac0a2 | 8699 | TYPE: int |
5473c134 | 8700 | IFDEF: ICAP_CLIENT |
26cc52cb | 8701 | LOC: Adaptation::Icap::TheConfig.service_revival_delay |
5473c134 | 8702 | DEFAULT: 180 |
cccac0a2 | 8703 | DOC_START |
5473c134 | 8704 | The delay specifies the number of seconds to wait after an ICAP |
8705 | OPTIONS request failure before requesting the options again. The | |
8706 | failed ICAP service is considered "down" until fresh OPTIONS are | |
8707 | fetched. | |
cccac0a2 | 8708 | |
5473c134 | 8709 | The actual delay cannot be smaller than the hardcoded minimum |
8710 | delay of 30 seconds. | |
cccac0a2 | 8711 | DOC_END |
8712 | ||
5473c134 | 8713 | NAME: icap_preview_enable |
cccac0a2 | 8714 | TYPE: onoff |
5473c134 | 8715 | IFDEF: ICAP_CLIENT |
8716 | COMMENT: on|off | |
26cc52cb | 8717 | LOC: Adaptation::Icap::TheConfig.preview_enable |
ac7a62f9 | 8718 | DEFAULT: on |
cccac0a2 | 8719 | DOC_START |
ac7a62f9 | 8720 | The ICAP Preview feature allows the ICAP server to handle the |
8721 | HTTP message by looking only at the beginning of the message body | |
8722 | or even without receiving the body at all. In some environments, | |
8723 | previews greatly speedup ICAP processing. | |
8724 | ||
8725 | During an ICAP OPTIONS transaction, the server may tell Squid what | |
8726 | HTTP messages should be previewed and how big the preview should be. | |
8727 | Squid will not use Preview if the server did not request one. | |
8728 | ||
8729 | To disable ICAP Preview for all ICAP services, regardless of | |
8730 | individual ICAP server OPTIONS responses, set this option to "off". | |
8731 | Example: | |
8732 | icap_preview_enable off | |
cccac0a2 | 8733 | DOC_END |
8734 | ||
5473c134 | 8735 | NAME: icap_preview_size |
8736 | TYPE: int | |
8737 | IFDEF: ICAP_CLIENT | |
26cc52cb | 8738 | LOC: Adaptation::Icap::TheConfig.preview_size |
5473c134 | 8739 | DEFAULT: -1 |
638402dd | 8740 | DEFAULT_DOC: No preview sent. |
cccac0a2 | 8741 | DOC_START |
53e738c6 | 8742 | The default size of preview data to be sent to the ICAP server. |
638402dd | 8743 | This value might be overwritten on a per server basis by OPTIONS requests. |
cccac0a2 | 8744 | DOC_END |
8745 | ||
83c51da9 CT |
8746 | NAME: icap_206_enable |
8747 | TYPE: onoff | |
8748 | IFDEF: ICAP_CLIENT | |
8749 | COMMENT: on|off | |
8750 | LOC: Adaptation::Icap::TheConfig.allow206_enable | |
8751 | DEFAULT: on | |
8752 | DOC_START | |
8753 | 206 (Partial Content) responses is an ICAP extension that allows the | |
8754 | ICAP agents to optionally combine adapted and original HTTP message | |
8755 | content. The decision to combine is postponed until the end of the | |
8756 | ICAP response. Squid supports Partial Content extension by default. | |
8757 | ||
8758 | Activation of the Partial Content extension is negotiated with each | |
8759 | ICAP service during OPTIONS exchange. Most ICAP servers should handle | |
8760 | negotation correctly even if they do not support the extension, but | |
8761 | some might fail. To disable Partial Content support for all ICAP | |
8762 | services and to avoid any negotiation, set this option to "off". | |
8763 | ||
8764 | Example: | |
8765 | icap_206_enable off | |
8766 | DOC_END | |
8767 | ||
5473c134 | 8768 | NAME: icap_default_options_ttl |
8769 | TYPE: int | |
8770 | IFDEF: ICAP_CLIENT | |
26cc52cb | 8771 | LOC: Adaptation::Icap::TheConfig.default_options_ttl |
5473c134 | 8772 | DEFAULT: 60 |
cccac0a2 | 8773 | DOC_START |
53e738c6 | 8774 | The default TTL value for ICAP OPTIONS responses that don't have |
5473c134 | 8775 | an Options-TTL header. |
cccac0a2 | 8776 | DOC_END |
8777 | ||
5473c134 | 8778 | NAME: icap_persistent_connections |
8779 | TYPE: onoff | |
8780 | IFDEF: ICAP_CLIENT | |
8781 | COMMENT: on|off | |
26cc52cb | 8782 | LOC: Adaptation::Icap::TheConfig.reuse_connections |
5473c134 | 8783 | DEFAULT: on |
cccac0a2 | 8784 | DOC_START |
5473c134 | 8785 | Whether or not Squid should use persistent connections to |
8786 | an ICAP server. | |
cccac0a2 | 8787 | DOC_END |
8788 | ||
22fff3bf | 8789 | NAME: adaptation_send_client_ip icap_send_client_ip |
5473c134 | 8790 | TYPE: onoff |
22fff3bf | 8791 | IFDEF: USE_ADAPTATION |
5473c134 | 8792 | COMMENT: on|off |
22fff3bf | 8793 | LOC: Adaptation::Config::send_client_ip |
5473c134 | 8794 | DEFAULT: off |
cccac0a2 | 8795 | DOC_START |
ea3ae478 AR |
8796 | If enabled, Squid shares HTTP client IP information with adaptation |
8797 | services. For ICAP, Squid adds the X-Client-IP header to ICAP requests. | |
8798 | For eCAP, Squid sets the libecap::metaClientIp transaction option. | |
8799 | ||
8800 | See also: adaptation_uses_indirect_client | |
cccac0a2 | 8801 | DOC_END |
8802 | ||
22fff3bf | 8803 | NAME: adaptation_send_username icap_send_client_username |
5473c134 | 8804 | TYPE: onoff |
22fff3bf | 8805 | IFDEF: USE_ADAPTATION |
5473c134 | 8806 | COMMENT: on|off |
22fff3bf | 8807 | LOC: Adaptation::Config::send_username |
5473c134 | 8808 | DEFAULT: off |
cccac0a2 | 8809 | DOC_START |
5473c134 | 8810 | This sends authenticated HTTP client username (if available) to |
22fff3bf AR |
8811 | the adaptation service. |
8812 | ||
8813 | For ICAP, the username value is encoded based on the | |
5473c134 | 8814 | icap_client_username_encode option and is sent using the header |
8815 | specified by the icap_client_username_header option. | |
cccac0a2 | 8816 | DOC_END |
8817 | ||
5473c134 | 8818 | NAME: icap_client_username_header |
cccac0a2 | 8819 | TYPE: string |
5473c134 | 8820 | IFDEF: ICAP_CLIENT |
26cc52cb | 8821 | LOC: Adaptation::Icap::TheConfig.client_username_header |
5473c134 | 8822 | DEFAULT: X-Client-Username |
cccac0a2 | 8823 | DOC_START |
db49f682 | 8824 | ICAP request header name to use for adaptation_send_username. |
cccac0a2 | 8825 | DOC_END |
8826 | ||
5473c134 | 8827 | NAME: icap_client_username_encode |
cccac0a2 | 8828 | TYPE: onoff |
5473c134 | 8829 | IFDEF: ICAP_CLIENT |
8830 | COMMENT: on|off | |
26cc52cb | 8831 | LOC: Adaptation::Icap::TheConfig.client_username_encode |
5473c134 | 8832 | DEFAULT: off |
cccac0a2 | 8833 | DOC_START |
5473c134 | 8834 | Whether to base64 encode the authenticated client username. |
cccac0a2 | 8835 | DOC_END |
8836 | ||
5473c134 | 8837 | NAME: icap_service |
8838 | TYPE: icap_service_type | |
8839 | IFDEF: ICAP_CLIENT | |
26cc52cb | 8840 | LOC: Adaptation::Icap::TheConfig |
5473c134 | 8841 | DEFAULT: none |
cccac0a2 | 8842 | DOC_START |
a22e6cd3 | 8843 | Defines a single ICAP service using the following format: |
cccac0a2 | 8844 | |
c25c2836 | 8845 | icap_service id vectoring_point uri [option ...] |
7d90757b | 8846 | |
c25c2836 CT |
8847 | id: ID |
8848 | an opaque identifier or name which is used to direct traffic to | |
8849 | this specific service. Must be unique among all adaptation | |
8850 | services in squid.conf. | |
a22e6cd3 AR |
8851 | |
8852 | vectoring_point: reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache | |
f3db09e2 | 8853 | This specifies at which point of transaction processing the |
8854 | ICAP service should be activated. *_postcache vectoring points | |
8855 | are not yet supported. | |
a22e6cd3 | 8856 | |
c25c2836 | 8857 | uri: icap://servername:port/servicepath |
a22e6cd3 | 8858 | ICAP server and service location. |
1b091aec CT |
8859 | icaps://servername:port/servicepath |
8860 | The "icap:" URI scheme is used for traditional ICAP server and | |
8861 | service location (default port is 1344, connections are not | |
8862 | encrypted). The "icaps:" URI scheme is for Secure ICAP | |
8863 | services that use SSL/TLS-encrypted ICAP connections (by | |
8864 | default, on port 11344). | |
a22e6cd3 AR |
8865 | |
8866 | ICAP does not allow a single service to handle both REQMOD and RESPMOD | |
8867 | transactions. Squid does not enforce that requirement. You can specify | |
8868 | services with the same service_url and different vectoring_points. You | |
8869 | can even specify multiple identical services as long as their | |
8870 | service_names differ. | |
8871 | ||
3caa16d2 AR |
8872 | To activate a service, use the adaptation_access directive. To group |
8873 | services, use adaptation_service_chain and adaptation_service_set. | |
a22e6cd3 AR |
8874 | |
8875 | Service options are separated by white space. ICAP services support | |
8876 | the following name=value options: | |
8877 | ||
8878 | bypass=on|off|1|0 | |
8879 | If set to 'on' or '1', the ICAP service is treated as | |
8880 | optional. If the service cannot be reached or malfunctions, | |
8881 | Squid will try to ignore any errors and process the message as | |
8882 | if the service was not enabled. No all ICAP errors can be | |
8883 | bypassed. If set to 0, the ICAP service is treated as | |
8884 | essential and all ICAP errors will result in an error page | |
8885 | returned to the HTTP client. | |
8886 | ||
8887 | Bypass is off by default: services are treated as essential. | |
8888 | ||
8889 | routing=on|off|1|0 | |
8890 | If set to 'on' or '1', the ICAP service is allowed to | |
8891 | dynamically change the current message adaptation plan by | |
8892 | returning a chain of services to be used next. The services | |
8893 | are specified using the X-Next-Services ICAP response header | |
8894 | value, formatted as a comma-separated list of service names. | |
e2851fe7 AR |
8895 | Each named service should be configured in squid.conf. Other |
8896 | services are ignored. An empty X-Next-Services value results | |
8897 | in an empty plan which ends the current adaptation. | |
8898 | ||
8899 | Dynamic adaptation plan may cross or cover multiple supported | |
8900 | vectoring points in their natural processing order. | |
a22e6cd3 AR |
8901 | |
8902 | Routing is not allowed by default: the ICAP X-Next-Services | |
8903 | response header is ignored. | |
8904 | ||
e6713f4e AJ |
8905 | ipv6=on|off |
8906 | Only has effect on split-stack systems. The default on those systems | |
8907 | is to use IPv4-only connections. When set to 'on' this option will | |
8908 | make Squid use IPv6-only connections to contact this ICAP service. | |
8909 | ||
2dba5b8e CT |
8910 | on-overload=block|bypass|wait|force |
8911 | If the service Max-Connections limit has been reached, do | |
8912 | one of the following for each new ICAP transaction: | |
8913 | * block: send an HTTP error response to the client | |
8914 | * bypass: ignore the "over-connected" ICAP service | |
8915 | * wait: wait (in a FIFO queue) for an ICAP connection slot | |
8916 | * force: proceed, ignoring the Max-Connections limit | |
8917 | ||
8918 | In SMP mode with N workers, each worker assumes the service | |
8919 | connection limit is Max-Connections/N, even though not all | |
8920 | workers may use a given service. | |
8921 | ||
8922 | The default value is "bypass" if service is bypassable, | |
8923 | otherwise it is set to "wait". | |
8924 | ||
8925 | ||
8926 | max-conn=number | |
8927 | Use the given number as the Max-Connections limit, regardless | |
8928 | of the Max-Connections value given by the service, if any. | |
8929 | ||
88df846b CT |
8930 | connection-encryption=on|off |
8931 | Determines the ICAP service effect on the connections_encrypted | |
8932 | ACL. | |
8933 | ||
8934 | The default is "on" for Secure ICAP services (i.e., those | |
8935 | with the icaps:// service URIs scheme) and "off" for plain ICAP | |
8936 | services. | |
8937 | ||
8938 | Does not affect ICAP connections (e.g., does not turn Secure | |
8939 | ICAP on or off). | |
8940 | ||
4dd2c9d6 | 8941 | ==== ICAPS / TLS OPTIONS ==== |
1b091aec CT |
8942 | |
8943 | These options are used for Secure ICAP (icaps://....) services only. | |
8944 | ||
4dd2c9d6 | 8945 | tls-cert=/path/to/ssl/certificate |
1b091aec CT |
8946 | A client SSL certificate to use when connecting to |
8947 | this icap server. | |
8948 | ||
4dd2c9d6 AJ |
8949 | tls-key=/path/to/ssl/key |
8950 | The private TLS/SSL key corresponding to sslcert above. | |
8951 | If 'tls-key' is not specified 'tls-cert' is assumed to | |
8952 | reference a combined PEM format file containing both the | |
1b091aec CT |
8953 | certificate and the key. |
8954 | ||
4dd2c9d6 | 8955 | tls-cipher=... The list of valid TLS/SSL ciphers to use when connecting |
1b091aec CT |
8956 | to this icap server. |
8957 | ||
1cc44095 AJ |
8958 | tls-min-version=1.N |
8959 | The minimum TLS protocol version to permit. To control | |
3f5b28fe | 8960 | SSLv3 use the tls-options= parameter. |
1cc44095 AJ |
8961 | Supported Values: 1.0 (default), 1.1, 1.2 |
8962 | ||
4dd2c9d6 | 8963 | tls-options=... Specify various OpenSSL library options: |
1b091aec CT |
8964 | |
8965 | NO_SSLv3 Disallow the use of SSLv3 | |
4dd2c9d6 | 8966 | |
1b091aec CT |
8967 | SINGLE_DH_USE |
8968 | Always create a new key when using | |
8969 | temporary/ephemeral DH key exchanges | |
4dd2c9d6 | 8970 | |
1b091aec | 8971 | ALL Enable various bug workarounds |
4dd2c9d6 AJ |
8972 | suggested as "harmless" by OpenSSL |
8973 | Be warned that this reduces SSL/TLS | |
8974 | strength to some attacks. | |
1b091aec CT |
8975 | |
8976 | See the OpenSSL SSL_CTX_set_options documentation for a | |
4dd2c9d6 AJ |
8977 | more complete list. Options relevant only to SSLv2 are |
8978 | not supported. | |
1b091aec | 8979 | |
86a84cc0 AJ |
8980 | tls-cafile= PEM file containing CA certificates to use when verifying |
8981 | the icap server certificate. | |
8982 | Use to specify intermediate CA certificate(s) if not sent | |
8983 | by the server. Or the full CA chain for the server when | |
435c72b0 | 8984 | using the tls-default-ca=off flag. |
86a84cc0 | 8985 | May be repeated to load multiple files. |
1b091aec | 8986 | |
4dd2c9d6 | 8987 | tls-capath=... A directory containing additional CA certificates to |
1b091aec | 8988 | use when verifying the icap server certificate. |
86a84cc0 | 8989 | Requires OpenSSL or LibreSSL. |
1b091aec | 8990 | |
4dd2c9d6 | 8991 | tls-crlfile=... A certificate revocation list file to use when |
1b091aec CT |
8992 | verifying the icap server certificate. |
8993 | ||
4dd2c9d6 | 8994 | tls-flags=... Specify various flags modifying the Squid TLS implementation: |
1b091aec CT |
8995 | |
8996 | DONT_VERIFY_PEER | |
8997 | Accept certificates even if they fail to | |
8998 | verify. | |
1b091aec CT |
8999 | DONT_VERIFY_DOMAIN |
9000 | Don't verify the icap server certificate | |
9001 | matches the server name | |
9002 | ||
435c72b0 AJ |
9003 | tls-default-ca[=off] |
9004 | Whether to use the system Trusted CAs. Default is ON. | |
8b253b83 | 9005 | |
4dd2c9d6 | 9006 | tls-domain= The icap server name as advertised in it's certificate. |
1b091aec CT |
9007 | Used for verifying the correctness of the received icap |
9008 | server certificate. If not specified the icap server | |
9009 | hostname extracted from ICAP URI will be used. | |
9010 | ||
a22e6cd3 AR |
9011 | Older icap_service format without optional named parameters is |
9012 | deprecated but supported for backward compatibility. | |
5473c134 | 9013 | |
5473c134 | 9014 | Example: |
c25c2836 | 9015 | icap_service svcBlocker reqmod_precache icap://icap1.mydomain.net:1344/reqmod bypass=0 |
1b091aec | 9016 | icap_service svcLogger reqmod_precache icaps://icap2.mydomain.net:11344/reqmod routing=on |
cccac0a2 | 9017 | DOC_END |
9018 | ||
5473c134 | 9019 | NAME: icap_class |
9020 | TYPE: icap_class_type | |
9021 | IFDEF: ICAP_CLIENT | |
21a26d31 | 9022 | LOC: none |
5473c134 | 9023 | DEFAULT: none |
cccac0a2 | 9024 | DOC_START |
a22e6cd3 | 9025 | This deprecated option was documented to define an ICAP service |
62c7f90e AR |
9026 | chain, even though it actually defined a set of similar, redundant |
9027 | services, and the chains were not supported. | |
5473c134 | 9028 | |
62c7f90e | 9029 | To define a set of redundant services, please use the |
a22e6cd3 AR |
9030 | adaptation_service_set directive. For service chains, use |
9031 | adaptation_service_chain. | |
cccac0a2 | 9032 | DOC_END |
9033 | ||
5473c134 | 9034 | NAME: icap_access |
9035 | TYPE: icap_access_type | |
9036 | IFDEF: ICAP_CLIENT | |
21a26d31 | 9037 | LOC: none |
cccac0a2 | 9038 | DEFAULT: none |
cccac0a2 | 9039 | DOC_START |
a22e6cd3 | 9040 | This option is deprecated. Please use adaptation_access, which |
62c7f90e AR |
9041 | has the same ICAP functionality, but comes with better |
9042 | documentation, and eCAP support. | |
cccac0a2 | 9043 | DOC_END |
9044 | ||
57afc994 AR |
9045 | COMMENT_START |
9046 | eCAP OPTIONS | |
9047 | ----------------------------------------------------------------------------- | |
9048 | COMMENT_END | |
9049 | ||
21a26d31 AR |
9050 | NAME: ecap_enable |
9051 | TYPE: onoff | |
9052 | IFDEF: USE_ECAP | |
9053 | COMMENT: on|off | |
574b508c | 9054 | LOC: Adaptation::Ecap::TheConfig.onoff |
21a26d31 AR |
9055 | DEFAULT: off |
9056 | DOC_START | |
9057 | Controls whether eCAP support is enabled. | |
9058 | DOC_END | |
9059 | ||
9060 | NAME: ecap_service | |
9061 | TYPE: ecap_service_type | |
9062 | IFDEF: USE_ECAP | |
574b508c | 9063 | LOC: Adaptation::Ecap::TheConfig |
21a26d31 AR |
9064 | DEFAULT: none |
9065 | DOC_START | |
9066 | Defines a single eCAP service | |
9067 | ||
c25c2836 | 9068 | ecap_service id vectoring_point uri [option ...] |
21a26d31 | 9069 | |
c25c2836 CT |
9070 | id: ID |
9071 | an opaque identifier or name which is used to direct traffic to | |
9072 | this specific service. Must be unique among all adaptation | |
9073 | services in squid.conf. | |
9074 | ||
9075 | vectoring_point: reqmod_precache|reqmod_postcache|respmod_precache|respmod_postcache | |
21a26d31 AR |
9076 | This specifies at which point of transaction processing the |
9077 | eCAP service should be activated. *_postcache vectoring points | |
9078 | are not yet supported. | |
c25c2836 CT |
9079 | |
9080 | uri: ecap://vendor/service_name?custom&cgi=style¶meters=optional | |
9081 | Squid uses the eCAP service URI to match this configuration | |
9082 | line with one of the dynamically loaded services. Each loaded | |
9083 | eCAP service must have a unique URI. Obtain the right URI from | |
9084 | the service provider. | |
9085 | ||
3caa16d2 AR |
9086 | To activate a service, use the adaptation_access directive. To group |
9087 | services, use adaptation_service_chain and adaptation_service_set. | |
c25c2836 CT |
9088 | |
9089 | Service options are separated by white space. eCAP services support | |
9090 | the following name=value options: | |
9091 | ||
9092 | bypass=on|off|1|0 | |
9093 | If set to 'on' or '1', the eCAP service is treated as optional. | |
9094 | If the service cannot be reached or malfunctions, Squid will try | |
9095 | to ignore any errors and process the message as if the service | |
21a26d31 | 9096 | was not enabled. No all eCAP errors can be bypassed. |
c25c2836 CT |
9097 | If set to 'off' or '0', the eCAP service is treated as essential |
9098 | and all eCAP errors will result in an error page returned to the | |
21a26d31 | 9099 | HTTP client. |
c25c2836 CT |
9100 | |
9101 | Bypass is off by default: services are treated as essential. | |
9102 | ||
9103 | routing=on|off|1|0 | |
9104 | If set to 'on' or '1', the eCAP service is allowed to | |
9105 | dynamically change the current message adaptation plan by | |
9106 | returning a chain of services to be used next. | |
9107 | ||
9108 | Dynamic adaptation plan may cross or cover multiple supported | |
9109 | vectoring points in their natural processing order. | |
9110 | ||
9111 | Routing is not allowed by default. | |
9112 | ||
88df846b CT |
9113 | connection-encryption=on|off |
9114 | Determines the eCAP service effect on the connections_encrypted | |
9115 | ACL. | |
9116 | ||
9117 | Defaults to "on", which does not taint the master transaction | |
9118 | w.r.t. that ACL. | |
9119 | ||
9120 | Does not affect eCAP API calls. | |
9121 | ||
c25c2836 CT |
9122 | Older ecap_service format without optional named parameters is |
9123 | deprecated but supported for backward compatibility. | |
9124 | ||
21a26d31 AR |
9125 | |
9126 | Example: | |
c25c2836 CT |
9127 | ecap_service s1 reqmod_precache ecap://filters.R.us/leakDetector?on_error=block bypass=off |
9128 | ecap_service s2 respmod_precache ecap://filters.R.us/virusFilter config=/etc/vf.cfg bypass=on | |
21a26d31 AR |
9129 | DOC_END |
9130 | ||
57afc994 AR |
9131 | NAME: loadable_modules |
9132 | TYPE: wordlist | |
9133 | IFDEF: USE_LOADABLE_MODULES | |
9134 | LOC: Config.loadable_module_names | |
9135 | DEFAULT: none | |
9136 | DOC_START | |
9137 | Instructs Squid to load the specified dynamic module(s) or activate | |
9138 | preloaded module(s). | |
9139 | Example: | |
9140 | loadable_modules @DEFAULT_PREFIX@/lib/MinimalAdapter.so | |
9141 | DOC_END | |
9142 | ||
62c7f90e AR |
9143 | COMMENT_START |
9144 | MESSAGE ADAPTATION OPTIONS | |
9145 | ----------------------------------------------------------------------------- | |
9146 | COMMENT_END | |
9147 | ||
9148 | NAME: adaptation_service_set | |
9149 | TYPE: adaptation_service_set_type | |
9150 | IFDEF: USE_ADAPTATION | |
9151 | LOC: none | |
9152 | DEFAULT: none | |
9153 | DOC_START | |
9154 | ||
a22e6cd3 AR |
9155 | Configures an ordered set of similar, redundant services. This is |
9156 | useful when hot standby or backup adaptation servers are available. | |
9157 | ||
9158 | adaptation_service_set set_name service_name1 service_name2 ... | |
9159 | ||
9160 | The named services are used in the set declaration order. The first | |
9161 | applicable adaptation service from the set is used first. The next | |
9162 | applicable service is tried if and only if the transaction with the | |
9163 | previous service fails and the message waiting to be adapted is still | |
9164 | intact. | |
62c7f90e | 9165 | |
a22e6cd3 AR |
9166 | When adaptation starts, broken services are ignored as if they were |
9167 | not a part of the set. A broken service is a down optional service. | |
62c7f90e | 9168 | |
a22e6cd3 AR |
9169 | The services in a set must be attached to the same vectoring point |
9170 | (e.g., pre-cache) and use the same adaptation method (e.g., REQMOD). | |
9171 | ||
9172 | If all services in a set are optional then adaptation failures are | |
9173 | bypassable. If all services in the set are essential, then a | |
9174 | transaction failure with one service may still be retried using | |
9175 | another service from the set, but when all services fail, the master | |
9176 | transaction fails as well. | |
9177 | ||
9178 | A set may contain a mix of optional and essential services, but that | |
9179 | is likely to lead to surprising results because broken services become | |
9180 | ignored (see above), making previously bypassable failures fatal. | |
9181 | Technically, it is the bypassability of the last failed service that | |
9182 | matters. | |
9183 | ||
9184 | See also: adaptation_access adaptation_service_chain | |
62c7f90e AR |
9185 | |
9186 | Example: | |
9187 | adaptation_service_set svcBlocker urlFilterPrimary urlFilterBackup | |
9188 | adaptation service_set svcLogger loggerLocal loggerRemote | |
9189 | DOC_END | |
9190 | ||
a22e6cd3 AR |
9191 | NAME: adaptation_service_chain |
9192 | TYPE: adaptation_service_chain_type | |
9193 | IFDEF: USE_ADAPTATION | |
9194 | LOC: none | |
9195 | DEFAULT: none | |
9196 | DOC_START | |
9197 | ||
9198 | Configures a list of complementary services that will be applied | |
9199 | one-by-one, forming an adaptation chain or pipeline. This is useful | |
9200 | when Squid must perform different adaptations on the same message. | |
9201 | ||
9202 | adaptation_service_chain chain_name service_name1 svc_name2 ... | |
9203 | ||
9204 | The named services are used in the chain declaration order. The first | |
9205 | applicable adaptation service from the chain is used first. The next | |
9206 | applicable service is applied to the successful adaptation results of | |
9207 | the previous service in the chain. | |
9208 | ||
9209 | When adaptation starts, broken services are ignored as if they were | |
9210 | not a part of the chain. A broken service is a down optional service. | |
9211 | ||
9212 | Request satisfaction terminates the adaptation chain because Squid | |
9213 | does not currently allow declaration of RESPMOD services at the | |
9214 | "reqmod_precache" vectoring point (see icap_service or ecap_service). | |
9215 | ||
9216 | The services in a chain must be attached to the same vectoring point | |
9217 | (e.g., pre-cache) and use the same adaptation method (e.g., REQMOD). | |
9218 | ||
9219 | A chain may contain a mix of optional and essential services. If an | |
9220 | essential adaptation fails (or the failure cannot be bypassed for | |
9221 | other reasons), the master transaction fails. Otherwise, the failure | |
9222 | is bypassed as if the failed adaptation service was not in the chain. | |
9223 | ||
9224 | See also: adaptation_access adaptation_service_set | |
9225 | ||
9226 | Example: | |
9227 | adaptation_service_chain svcRequest requestLogger urlFilter leakDetector | |
9228 | DOC_END | |
9229 | ||
62c7f90e AR |
9230 | NAME: adaptation_access |
9231 | TYPE: adaptation_access_type | |
9232 | IFDEF: USE_ADAPTATION | |
9233 | LOC: none | |
9234 | DEFAULT: none | |
638402dd | 9235 | DEFAULT_DOC: Allow, unless rules exist in squid.conf. |
62c7f90e AR |
9236 | DOC_START |
9237 | Sends an HTTP transaction to an ICAP or eCAP adaptation service. | |
9238 | ||
9239 | adaptation_access service_name allow|deny [!]aclname... | |
9240 | adaptation_access set_name allow|deny [!]aclname... | |
9241 | ||
9242 | At each supported vectoring point, the adaptation_access | |
9243 | statements are processed in the order they appear in this | |
9244 | configuration file. Statements pointing to the following services | |
9245 | are ignored (i.e., skipped without checking their ACL): | |
9246 | ||
9247 | - services serving different vectoring points | |
9248 | - "broken-but-bypassable" services | |
9249 | - "up" services configured to ignore such transactions | |
9250 | (e.g., based on the ICAP Transfer-Ignore header). | |
9251 | ||
9252 | When a set_name is used, all services in the set are checked | |
9253 | using the same rules, to find the first applicable one. See | |
9254 | adaptation_service_set for details. | |
9255 | ||
9256 | If an access list is checked and there is a match, the | |
9257 | processing stops: For an "allow" rule, the corresponding | |
9258 | adaptation service is used for the transaction. For a "deny" | |
9259 | rule, no adaptation service is activated. | |
9260 | ||
9261 | It is currently not possible to apply more than one adaptation | |
9262 | service at the same vectoring point to the same HTTP transaction. | |
9263 | ||
9264 | See also: icap_service and ecap_service | |
9265 | ||
9266 | Example: | |
9267 | adaptation_access service_1 allow all | |
9268 | DOC_END | |
9269 | ||
a22e6cd3 AR |
9270 | NAME: adaptation_service_iteration_limit |
9271 | TYPE: int | |
9272 | IFDEF: USE_ADAPTATION | |
9273 | LOC: Adaptation::Config::service_iteration_limit | |
9274 | DEFAULT: 16 | |
9275 | DOC_START | |
9276 | Limits the number of iterations allowed when applying adaptation | |
9277 | services to a message. If your longest adaptation set or chain | |
9278 | may have more than 16 services, increase the limit beyond its | |
9279 | default value of 16. If detecting infinite iteration loops sooner | |
9280 | is critical, make the iteration limit match the actual number | |
9281 | of services in your longest adaptation set or chain. | |
9282 | ||
9283 | Infinite adaptation loops are most likely with routing services. | |
9284 | ||
9285 | See also: icap_service routing=1 | |
9286 | DOC_END | |
9287 | ||
3ff65596 AR |
9288 | NAME: adaptation_masterx_shared_names |
9289 | TYPE: string | |
9290 | IFDEF: USE_ADAPTATION | |
9291 | LOC: Adaptation::Config::masterx_shared_name | |
9292 | DEFAULT: none | |
9293 | DOC_START | |
9294 | For each master transaction (i.e., the HTTP request and response | |
9295 | sequence, including all related ICAP and eCAP exchanges), Squid | |
9296 | maintains a table of metadata. The table entries are (name, value) | |
9297 | pairs shared among eCAP and ICAP exchanges. The table is destroyed | |
9298 | with the master transaction. | |
9299 | ||
9300 | This option specifies the table entry names that Squid must accept | |
9301 | from and forward to the adaptation transactions. | |
9302 | ||
9303 | An ICAP REQMOD or RESPMOD transaction may set an entry in the | |
9304 | shared table by returning an ICAP header field with a name | |
6666da11 AR |
9305 | specified in adaptation_masterx_shared_names. |
9306 | ||
9307 | An eCAP REQMOD or RESPMOD transaction may set an entry in the | |
9308 | shared table by implementing the libecap::visitEachOption() API | |
9309 | to provide an option with a name specified in | |
9310 | adaptation_masterx_shared_names. | |
5038f9d8 AR |
9311 | |
9312 | Squid will store and forward the set entry to subsequent adaptation | |
3ff65596 AR |
9313 | transactions within the same master transaction scope. |
9314 | ||
9315 | Only one shared entry name is supported at this time. | |
9316 | ||
9317 | Example: | |
9318 | # share authentication information among ICAP services | |
9319 | adaptation_masterx_shared_names X-Subscriber-ID | |
9320 | DOC_END | |
9321 | ||
71be37e0 | 9322 | NAME: adaptation_meta |
d7f4a0b7 | 9323 | TYPE: note |
71be37e0 CT |
9324 | IFDEF: USE_ADAPTATION |
9325 | LOC: Adaptation::Config::metaHeaders | |
9326 | DEFAULT: none | |
9327 | DOC_START | |
9328 | This option allows Squid administrator to add custom ICAP request | |
9329 | headers or eCAP options to Squid ICAP requests or eCAP transactions. | |
9330 | Use it to pass custom authentication tokens and other | |
9331 | transaction-state related meta information to an ICAP/eCAP service. | |
9332 | ||
9333 | The addition of a meta header is ACL-driven: | |
9334 | adaptation_meta name value [!]aclname ... | |
9335 | ||
9336 | Processing for a given header name stops after the first ACL list match. | |
9337 | Thus, it is impossible to add two headers with the same name. If no ACL | |
9338 | lists match for a given header name, no such header is added. For | |
9339 | example: | |
9340 | ||
9341 | # do not debug transactions except for those that need debugging | |
9342 | adaptation_meta X-Debug 1 needs_debugging | |
9343 | ||
9344 | # log all transactions except for those that must remain secret | |
9345 | adaptation_meta X-Log 1 !keep_secret | |
9346 | ||
9347 | # mark transactions from users in the "G 1" group | |
9348 | adaptation_meta X-Authenticated-Groups "G 1" authed_as_G1 | |
9349 | ||
9350 | The "value" parameter may be a regular squid.conf token or a "double | |
9351 | quoted string". Within the quoted string, use backslash (\) to escape | |
9352 | any character, which is currently only useful for escaping backslashes | |
9353 | and double quotes. For example, | |
9354 | "this string has one backslash (\\) and two \"quotes\"" | |
d7f4a0b7 CT |
9355 | |
9356 | Used adaptation_meta header values may be logged via %note | |
9357 | logformat code. If multiple adaptation_meta headers with the same name | |
9358 | are used during master transaction lifetime, the header values are | |
9359 | logged in the order they were used and duplicate values are ignored | |
9360 | (only the first repeated value will be logged). | |
71be37e0 CT |
9361 | DOC_END |
9362 | ||
3ff65596 AR |
9363 | NAME: icap_retry |
9364 | TYPE: acl_access | |
9365 | IFDEF: ICAP_CLIENT | |
9366 | LOC: Adaptation::Icap::TheConfig.repeat | |
3ff65596 AR |
9367 | DEFAULT_IF_NONE: deny all |
9368 | DOC_START | |
9369 | This ACL determines which retriable ICAP transactions are | |
9370 | retried. Transactions that received a complete ICAP response | |
9371 | and did not have to consume or produce HTTP bodies to receive | |
9372 | that response are usually retriable. | |
9373 | ||
9374 | icap_retry allow|deny [!]aclname ... | |
9375 | ||
9376 | Squid automatically retries some ICAP I/O timeouts and errors | |
9377 | due to persistent connection race conditions. | |
9378 | ||
9379 | See also: icap_retry_limit | |
9380 | DOC_END | |
9381 | ||
9382 | NAME: icap_retry_limit | |
9383 | TYPE: int | |
9384 | IFDEF: ICAP_CLIENT | |
9385 | LOC: Adaptation::Icap::TheConfig.repeat_limit | |
9386 | DEFAULT: 0 | |
638402dd | 9387 | DEFAULT_DOC: No retries are allowed. |
3ff65596 | 9388 | DOC_START |
638402dd | 9389 | Limits the number of retries allowed. |
3ff65596 AR |
9390 | |
9391 | Communication errors due to persistent connection race | |
9392 | conditions are unavoidable, automatically retried, and do not | |
9393 | count against this limit. | |
9394 | ||
9395 | See also: icap_retry | |
9396 | DOC_END | |
9397 | ||
9398 | ||
5473c134 | 9399 | COMMENT_START |
9400 | DNS OPTIONS | |
9401 | ----------------------------------------------------------------------------- | |
9402 | COMMENT_END | |
9403 | ||
9404 | NAME: check_hostnames | |
cccac0a2 | 9405 | TYPE: onoff |
cccac0a2 | 9406 | DEFAULT: off |
5473c134 | 9407 | LOC: Config.onoff.check_hostnames |
cccac0a2 | 9408 | DOC_START |
5473c134 | 9409 | For security and stability reasons Squid can check |
9410 | hostnames for Internet standard RFC compliance. If you want | |
9411 | Squid to perform these checks turn this directive on. | |
cccac0a2 | 9412 | DOC_END |
9413 | ||
5473c134 | 9414 | NAME: allow_underscore |
cccac0a2 | 9415 | TYPE: onoff |
cccac0a2 | 9416 | DEFAULT: on |
5473c134 | 9417 | LOC: Config.onoff.allow_underscore |
cccac0a2 | 9418 | DOC_START |
5473c134 | 9419 | Underscore characters is not strictly allowed in Internet hostnames |
9420 | but nevertheless used by many sites. Set this to off if you want | |
9421 | Squid to be strict about the standard. | |
9422 | This check is performed only when check_hostnames is set to on. | |
cccac0a2 | 9423 | DOC_END |
9424 | ||
5473c134 | 9425 | NAME: dns_retransmit_interval |
fd0f51c4 | 9426 | TYPE: time_msec |
5473c134 | 9427 | DEFAULT: 5 seconds |
9428 | LOC: Config.Timeout.idns_retransmit | |
cccac0a2 | 9429 | DOC_START |
5473c134 | 9430 | Initial retransmit interval for DNS queries. The interval is |
9431 | doubled each time all configured DNS servers have been tried. | |
cccac0a2 | 9432 | DOC_END |
9433 | ||
5473c134 | 9434 | NAME: dns_timeout |
fd0f51c4 | 9435 | TYPE: time_msec |
a541c34e | 9436 | DEFAULT: 30 seconds |
5473c134 | 9437 | LOC: Config.Timeout.idns_query |
cccac0a2 | 9438 | DOC_START |
5473c134 | 9439 | DNS Query timeout. If no response is received to a DNS query |
9440 | within this time all DNS servers for the queried domain | |
9441 | are assumed to be unavailable. | |
cccac0a2 | 9442 | DOC_END |
9443 | ||
e210930b AJ |
9444 | NAME: dns_packet_max |
9445 | TYPE: b_ssize_t | |
638402dd | 9446 | DEFAULT_DOC: EDNS disabled |
e210930b AJ |
9447 | DEFAULT: none |
9448 | LOC: Config.dns.packet_max | |
e210930b AJ |
9449 | DOC_START |
9450 | Maximum number of bytes packet size to advertise via EDNS. | |
9451 | Set to "none" to disable EDNS large packet support. | |
9452 | ||
9453 | For legacy reasons DNS UDP replies will default to 512 bytes which | |
9454 | is too small for many responses. EDNS provides a means for Squid to | |
9455 | negotiate receiving larger responses back immediately without having | |
9456 | to failover with repeat requests. Responses larger than this limit | |
9457 | will retain the old behaviour of failover to TCP DNS. | |
9458 | ||
9459 | Squid has no real fixed limit internally, but allowing packet sizes | |
9460 | over 1500 bytes requires network jumbogram support and is usually not | |
9461 | necessary. | |
9462 | ||
9463 | WARNING: The RFC also indicates that some older resolvers will reply | |
9464 | with failure of the whole request if the extension is added. Some | |
9465 | resolvers have already been identified which will reply with mangled | |
9466 | EDNS response on occasion. Usually in response to many-KB jumbogram | |
9467 | sizes being advertised by Squid. | |
9468 | Squid will currently treat these both as an unable-to-resolve domain | |
9469 | even if it would be resolvable without EDNS. | |
9470 | DOC_END | |
9471 | ||
5473c134 | 9472 | NAME: dns_defnames |
9473 | COMMENT: on|off | |
cccac0a2 | 9474 | TYPE: onoff |
cccac0a2 | 9475 | DEFAULT: off |
638402dd | 9476 | DEFAULT_DOC: Search for single-label domain names is disabled. |
5473c134 | 9477 | LOC: Config.onoff.res_defnames |
cccac0a2 | 9478 | DOC_START |
5473c134 | 9479 | Normally the RES_DEFNAMES resolver option is disabled |
9480 | (see res_init(3)). This prevents caches in a hierarchy | |
9481 | from interpreting single-component hostnames locally. To allow | |
9482 | Squid to handle single-component names, enable this option. | |
cccac0a2 | 9483 | DOC_END |
9484 | ||
bce61b00 AJ |
9485 | NAME: dns_multicast_local |
9486 | COMMENT: on|off | |
9487 | TYPE: onoff | |
9488 | DEFAULT: off | |
9489 | DEFAULT_DOC: Search for .local and .arpa names is disabled. | |
9490 | LOC: Config.onoff.dns_mdns | |
9491 | DOC_START | |
9492 | When set to on, Squid sends multicast DNS lookups on the local | |
9493 | network for domains ending in .local and .arpa. | |
9494 | This enables local servers and devices to be contacted in an | |
9495 | ad-hoc or zero-configuration network environment. | |
9496 | DOC_END | |
9497 | ||
5473c134 | 9498 | NAME: dns_nameservers |
5a1098fb | 9499 | TYPE: SBufList |
5473c134 | 9500 | DEFAULT: none |
638402dd | 9501 | DEFAULT_DOC: Use operating system definitions |
5a1098fb | 9502 | LOC: Config.dns.nameservers |
cccac0a2 | 9503 | DOC_START |
5473c134 | 9504 | Use this if you want to specify a list of DNS name servers |
9505 | (IP addresses) to use instead of those given in your | |
9506 | /etc/resolv.conf file. | |
638402dd | 9507 | |
5473c134 | 9508 | On Windows platforms, if no value is specified here or in |
9509 | the /etc/resolv.conf file, the list of DNS name servers are | |
9510 | taken from the Windows registry, both static and dynamic DHCP | |
9511 | configurations are supported. | |
cccac0a2 | 9512 | |
5473c134 | 9513 | Example: dns_nameservers 10.0.0.1 192.172.0.4 |
cccac0a2 | 9514 | DOC_END |
9515 | ||
5473c134 | 9516 | NAME: hosts_file |
cccac0a2 | 9517 | TYPE: string |
5473c134 | 9518 | DEFAULT: @DEFAULT_HOSTS@ |
9519 | LOC: Config.etcHostsPath | |
cccac0a2 | 9520 | DOC_START |
5473c134 | 9521 | Location of the host-local IP name-address associations |
9522 | database. Most Operating Systems have such a file on different | |
9523 | default locations: | |
9524 | - Un*X & Linux: /etc/hosts | |
9525 | - Windows NT/2000: %SystemRoot%\system32\drivers\etc\hosts | |
9526 | (%SystemRoot% value install default is c:\winnt) | |
9527 | - Windows XP/2003: %SystemRoot%\system32\drivers\etc\hosts | |
9528 | (%SystemRoot% value install default is c:\windows) | |
9529 | - Windows 9x/Me: %windir%\hosts | |
9530 | (%windir% value is usually c:\windows) | |
9531 | - Cygwin: /etc/hosts | |
cccac0a2 | 9532 | |
5473c134 | 9533 | The file contains newline-separated definitions, in the |
9534 | form ip_address_in_dotted_form name [name ...] names are | |
9535 | whitespace-separated. Lines beginning with an hash (#) | |
9536 | character are comments. | |
cccac0a2 | 9537 | |
5473c134 | 9538 | The file is checked at startup and upon configuration. |
9539 | If set to 'none', it won't be checked. | |
9540 | If append_domain is used, that domain will be added to | |
9541 | domain-local (i.e. not containing any dot character) host | |
9542 | definitions. | |
cccac0a2 | 9543 | DOC_END |
9544 | ||
5473c134 | 9545 | NAME: append_domain |
9546 | TYPE: string | |
9547 | LOC: Config.appendDomain | |
9548 | DEFAULT: none | |
638402dd | 9549 | DEFAULT_DOC: Use operating system definitions |
6a2f3fcf | 9550 | DOC_START |
5473c134 | 9551 | Appends local domain name to hostnames without any dots in |
9552 | them. append_domain must begin with a period. | |
9553 | ||
9554 | Be warned there are now Internet names with no dots in | |
9555 | them using only top-domain names, so setting this may | |
9556 | cause some Internet sites to become unavailable. | |
9557 | ||
9558 | Example: | |
9559 | append_domain .yourdomain.com | |
6a2f3fcf | 9560 | DOC_END |
9561 | ||
5473c134 | 9562 | NAME: ignore_unknown_nameservers |
9563 | TYPE: onoff | |
9564 | LOC: Config.onoff.ignore_unknown_nameservers | |
df6fd596 | 9565 | DEFAULT: on |
9566 | DOC_START | |
5473c134 | 9567 | By default Squid checks that DNS responses are received |
9568 | from the same IP addresses they are sent to. If they | |
9569 | don't match, Squid ignores the response and writes a warning | |
9570 | message to cache.log. You can allow responses from unknown | |
9571 | nameservers by setting this option to 'off'. | |
df6fd596 | 9572 | DOC_END |
9573 | ||
5a0da9ec AJ |
9574 | NAME: dns_v4_first |
9575 | TYPE: onoff | |
9576 | DEFAULT: off | |
9577 | LOC: Config.dns.v4_first | |
5a0da9ec AJ |
9578 | DOC_START |
9579 | With the IPv6 Internet being as fast or faster than IPv4 Internet | |
9580 | for most networks Squid prefers to contact websites over IPv6. | |
9581 | ||
9582 | This option reverses the order of preference to make Squid contact | |
9583 | dual-stack websites over IPv4 first. Squid will still perform both | |
9584 | IPv6 and IPv4 DNS lookups before connecting. | |
9585 | ||
9586 | WARNING: | |
9587 | This option will restrict the situations under which IPv6 | |
9588 | connectivity is used (and tested). Hiding network problems | |
9589 | which would otherwise be detected and warned about. | |
9590 | DOC_END | |
9591 | ||
6bc15a4f | 9592 | NAME: ipcache_size |
9593 | COMMENT: (number of entries) | |
9594 | TYPE: int | |
9595 | DEFAULT: 1024 | |
9596 | LOC: Config.ipcache.size | |
638402dd AJ |
9597 | DOC_START |
9598 | Maximum number of DNS IP cache entries. | |
9599 | DOC_END | |
6bc15a4f | 9600 | |
9601 | NAME: ipcache_low | |
9602 | COMMENT: (percent) | |
9603 | TYPE: int | |
9604 | DEFAULT: 90 | |
9605 | LOC: Config.ipcache.low | |
9606 | DOC_NONE | |
9607 | ||
9608 | NAME: ipcache_high | |
9609 | COMMENT: (percent) | |
9610 | TYPE: int | |
9611 | DEFAULT: 95 | |
9612 | LOC: Config.ipcache.high | |
9613 | DOC_START | |
9614 | The size, low-, and high-water marks for the IP cache. | |
9615 | DOC_END | |
9616 | ||
9617 | NAME: fqdncache_size | |
9618 | COMMENT: (number of entries) | |
9619 | TYPE: int | |
9620 | DEFAULT: 1024 | |
9621 | LOC: Config.fqdncache.size | |
9622 | DOC_START | |
9623 | Maximum number of FQDN cache entries. | |
9624 | DOC_END | |
9625 | ||
a58ff010 | 9626 | COMMENT_START |
5473c134 | 9627 | MISCELLANEOUS |
a58ff010 | 9628 | ----------------------------------------------------------------------------- |
9629 | COMMENT_END | |
9630 | ||
2eceb328 CT |
9631 | NAME: configuration_includes_quoted_values |
9632 | COMMENT: on|off | |
bde7a8ce CT |
9633 | TYPE: configuration_includes_quoted_values |
9634 | DEFAULT: off | |
2eceb328 CT |
9635 | LOC: ConfigParser::RecognizeQuotedValues |
9636 | DOC_START | |
9637 | If set, Squid will recognize each "quoted string" after a configuration | |
9638 | directive as a single parameter. The quotes are stripped before the | |
9639 | parameter value is interpreted or used. | |
9640 | See "Values with spaces, quotes, and other special characters" | |
9641 | section for more details. | |
9642 | DOC_END | |
9643 | ||
5473c134 | 9644 | NAME: memory_pools |
a58ff010 | 9645 | COMMENT: on|off |
5473c134 | 9646 | TYPE: onoff |
9647 | DEFAULT: on | |
9648 | LOC: Config.onoff.mem_pools | |
a58ff010 | 9649 | DOC_START |
5473c134 | 9650 | If set, Squid will keep pools of allocated (but unused) memory |
9651 | available for future use. If memory is a premium on your | |
9652 | system and you believe your malloc library outperforms Squid | |
9653 | routines, disable this. | |
a58ff010 | 9654 | DOC_END |
9655 | ||
5473c134 | 9656 | NAME: memory_pools_limit |
9657 | COMMENT: (bytes) | |
70be1349 | 9658 | TYPE: b_int64_t |
5473c134 | 9659 | DEFAULT: 5 MB |
9660 | LOC: Config.MemPools.limit | |
ec1245f8 | 9661 | DOC_START |
5473c134 | 9662 | Used only with memory_pools on: |
9663 | memory_pools_limit 50 MB | |
ec1245f8 | 9664 | |
5473c134 | 9665 | If set to a non-zero value, Squid will keep at most the specified |
9666 | limit of allocated (but unused) memory in memory pools. All free() | |
9667 | requests that exceed this limit will be handled by your malloc | |
9668 | library. Squid does not pre-allocate any memory, just safe-keeps | |
9669 | objects that otherwise would be free()d. Thus, it is safe to set | |
9670 | memory_pools_limit to a reasonably high value even if your | |
9671 | configuration will use less memory. | |
ec1245f8 | 9672 | |
89646bd7 | 9673 | If set to none, Squid will keep all memory it can. That is, there |
5473c134 | 9674 | will be no limit on the total amount of memory used for safe-keeping. |
ec1245f8 | 9675 | |
5473c134 | 9676 | To disable memory allocation optimization, do not set |
70be1349 | 9677 | memory_pools_limit to 0 or none. Set memory_pools to "off" instead. |
5473c134 | 9678 | |
9679 | An overhead for maintaining memory pools is not taken into account | |
9680 | when the limit is checked. This overhead is close to four bytes per | |
9681 | object kept. However, pools may actually _save_ memory because of | |
9682 | reduced memory thrashing in your malloc library. | |
ec1245f8 | 9683 | DOC_END |
9684 | ||
5473c134 | 9685 | NAME: forwarded_for |
67c06f0d AJ |
9686 | COMMENT: on|off|transparent|truncate|delete |
9687 | TYPE: string | |
5473c134 | 9688 | DEFAULT: on |
9689 | LOC: opt_forwarded_for | |
5f8252d2 | 9690 | DOC_START |
67c06f0d AJ |
9691 | If set to "on", Squid will append your client's IP address |
9692 | in the HTTP requests it forwards. By default it looks like: | |
5f8252d2 | 9693 | |
5473c134 | 9694 | X-Forwarded-For: 192.1.2.3 |
9695 | ||
67c06f0d | 9696 | If set to "off", it will appear as |
5473c134 | 9697 | |
9698 | X-Forwarded-For: unknown | |
67c06f0d AJ |
9699 | |
9700 | If set to "transparent", Squid will not alter the | |
9701 | X-Forwarded-For header in any way. | |
9702 | ||
9703 | If set to "delete", Squid will delete the entire | |
9704 | X-Forwarded-For header. | |
9705 | ||
9706 | If set to "truncate", Squid will remove all existing | |
dd68402f | 9707 | X-Forwarded-For entries, and place the client IP as the sole entry. |
5f8252d2 | 9708 | DOC_END |
9709 | ||
5473c134 | 9710 | NAME: cachemgr_passwd |
9711 | TYPE: cachemgrpasswd | |
9712 | DEFAULT: none | |
638402dd | 9713 | DEFAULT_DOC: No password. Actions which require password are denied. |
5473c134 | 9714 | LOC: Config.passwd_list |
5f8252d2 | 9715 | DOC_START |
5473c134 | 9716 | Specify passwords for cachemgr operations. |
5f8252d2 | 9717 | |
5473c134 | 9718 | Usage: cachemgr_passwd password action action ... |
9719 | ||
9720 | Some valid actions are (see cache manager menu for a full list): | |
9721 | 5min | |
9722 | 60min | |
9723 | asndb | |
9724 | authenticator | |
9725 | cbdata | |
9726 | client_list | |
9727 | comm_incoming | |
9728 | config * | |
9729 | counters | |
9730 | delay | |
9731 | digest_stats | |
9732 | dns | |
9733 | events | |
9734 | filedescriptors | |
9735 | fqdncache | |
9736 | histograms | |
9737 | http_headers | |
9738 | info | |
9739 | io | |
9740 | ipcache | |
9741 | mem | |
9742 | menu | |
9743 | netdb | |
9744 | non_peers | |
9745 | objects | |
9746 | offline_toggle * | |
9747 | pconn | |
9748 | peer_select | |
b360c477 | 9749 | reconfigure * |
5473c134 | 9750 | redirector |
9751 | refresh | |
9752 | server_list | |
9753 | shutdown * | |
9754 | store_digest | |
9755 | storedir | |
9756 | utilization | |
9757 | via_headers | |
9758 | vm_objects | |
9759 | ||
9760 | * Indicates actions which will not be performed without a | |
9761 | valid password, others can be performed if not listed here. | |
9762 | ||
9763 | To disable an action, set the password to "disable". | |
9764 | To allow performing an action without a password, set the | |
9765 | password to "none". | |
9766 | ||
9767 | Use the keyword "all" to set the same password for all actions. | |
9768 | ||
9769 | Example: | |
9770 | cachemgr_passwd secret shutdown | |
9771 | cachemgr_passwd lesssssssecret info stats/objects | |
9772 | cachemgr_passwd disable all | |
5f8252d2 | 9773 | DOC_END |
9774 | ||
5473c134 | 9775 | NAME: client_db |
a58ff010 | 9776 | COMMENT: on|off |
5473c134 | 9777 | TYPE: onoff |
9778 | DEFAULT: on | |
9779 | LOC: Config.onoff.client_db | |
a58ff010 | 9780 | DOC_START |
5473c134 | 9781 | If you want to disable collecting per-client statistics, |
9782 | turn off client_db here. | |
a58ff010 | 9783 | DOC_END |
9784 | ||
5473c134 | 9785 | NAME: refresh_all_ims |
9786 | COMMENT: on|off | |
9787 | TYPE: onoff | |
9788 | DEFAULT: off | |
9789 | LOC: Config.onoff.refresh_all_ims | |
a58ff010 | 9790 | DOC_START |
5473c134 | 9791 | When you enable this option, squid will always check |
9792 | the origin server for an update when a client sends an | |
9793 | If-Modified-Since request. Many browsers use IMS | |
9794 | requests when the user requests a reload, and this | |
9795 | ensures those clients receive the latest version. | |
a58ff010 | 9796 | |
5473c134 | 9797 | By default (off), squid may return a Not Modified response |
9798 | based on the age of the cached version. | |
78e8cfc4 | 9799 | DOC_END |
9800 | ||
5473c134 | 9801 | NAME: reload_into_ims |
626096be | 9802 | IFDEF: USE_HTTP_VIOLATIONS |
12b91c99 | 9803 | COMMENT: on|off |
5473c134 | 9804 | TYPE: onoff |
9805 | DEFAULT: off | |
9806 | LOC: Config.onoff.reload_into_ims | |
12b91c99 | 9807 | DOC_START |
5473c134 | 9808 | When you enable this option, client no-cache or ``reload'' |
9809 | requests will be changed to If-Modified-Since requests. | |
9810 | Doing this VIOLATES the HTTP standard. Enabling this | |
9811 | feature could make you liable for problems which it | |
9812 | causes. | |
9813 | ||
9814 | see also refresh_pattern for a more selective approach. | |
12b91c99 | 9815 | DOC_END |
9816 | ||
31ef19cd | 9817 | NAME: connect_retries |
5473c134 | 9818 | TYPE: int |
31ef19cd AJ |
9819 | LOC: Config.connect_retries |
9820 | DEFAULT: 0 | |
638402dd | 9821 | DEFAULT_DOC: Do not retry failed connections. |
a58ff010 | 9822 | DOC_START |
aed188fd AJ |
9823 | This sets the maximum number of connection attempts made for each |
9824 | TCP connection. The connect_retries attempts must all still | |
9825 | complete within the connection timeout period. | |
31ef19cd AJ |
9826 | |
9827 | The default is not to re-try if the first connection attempt fails. | |
9828 | The (not recommended) maximum is 10 tries. | |
5473c134 | 9829 | |
31ef19cd AJ |
9830 | A warning message will be generated if it is set to a too-high |
9831 | value and the configured value will be over-ridden. | |
5473c134 | 9832 | |
31ef19cd AJ |
9833 | Note: These re-tries are in addition to forward_max_tries |
9834 | which limit how many different addresses may be tried to find | |
9835 | a useful server. | |
a58ff010 | 9836 | DOC_END |
9837 | ||
5473c134 | 9838 | NAME: retry_on_error |
a58ff010 | 9839 | TYPE: onoff |
5473c134 | 9840 | LOC: Config.retry.onerror |
a58ff010 | 9841 | DEFAULT: off |
9842 | DOC_START | |
aea8548b AJ |
9843 | If set to ON Squid will automatically retry requests when |
9844 | receiving an error response with status 403 (Forbidden), | |
9845 | 500 (Internal Error), 501 or 503 (Service not available). | |
9846 | Status 502 and 504 (Gateway errors) are always retried. | |
9847 | ||
9848 | This is mainly useful if you are in a complex cache hierarchy to | |
9849 | work around access control errors. | |
9850 | ||
9851 | NOTE: This retry will attempt to find another working destination. | |
9852 | Which is different from the server which just failed. | |
5f8252d2 | 9853 | DOC_END |
9854 | ||
5473c134 | 9855 | NAME: as_whois_server |
5f8252d2 | 9856 | TYPE: string |
5473c134 | 9857 | LOC: Config.as_whois_server |
9858 | DEFAULT: whois.ra.net | |
5f8252d2 | 9859 | DOC_START |
5473c134 | 9860 | WHOIS server to query for AS numbers. NOTE: AS numbers are |
9861 | queried only when Squid starts up, not for every request. | |
5f8252d2 | 9862 | DOC_END |
9863 | ||
5473c134 | 9864 | NAME: offline_mode |
5f8252d2 | 9865 | TYPE: onoff |
5473c134 | 9866 | LOC: Config.onoff.offline |
5f8252d2 | 9867 | DEFAULT: off |
9868 | DOC_START | |
5473c134 | 9869 | Enable this option and Squid will never try to validate cached |
9870 | objects. | |
a58ff010 | 9871 | DOC_END |
9872 | ||
5473c134 | 9873 | NAME: uri_whitespace |
9874 | TYPE: uri_whitespace | |
9875 | LOC: Config.uri_whitespace | |
9876 | DEFAULT: strip | |
a58ff010 | 9877 | DOC_START |
5473c134 | 9878 | What to do with requests that have whitespace characters in the |
9879 | URI. Options: | |
a58ff010 | 9880 | |
5473c134 | 9881 | strip: The whitespace characters are stripped out of the URL. |
82806837 AJ |
9882 | This is the behavior recommended by RFC2396 and RFC3986 |
9883 | for tolerant handling of generic URI. | |
9884 | NOTE: This is one difference between generic URI and HTTP URLs. | |
9885 | ||
5473c134 | 9886 | deny: The request is denied. The user receives an "Invalid |
9887 | Request" message. | |
82806837 AJ |
9888 | This is the behaviour recommended by RFC2616 for safe |
9889 | handling of HTTP request URL. | |
9890 | ||
5473c134 | 9891 | allow: The request is allowed and the URI is not changed. The |
9892 | whitespace characters remain in the URI. Note the | |
9893 | whitespace is passed to redirector processes if they | |
9894 | are in use. | |
82806837 AJ |
9895 | Note this may be considered a violation of RFC2616 |
9896 | request parsing where whitespace is prohibited in the | |
9897 | URL field. | |
9898 | ||
5473c134 | 9899 | encode: The request is allowed and the whitespace characters are |
82806837 AJ |
9900 | encoded according to RFC1738. |
9901 | ||
5473c134 | 9902 | chop: The request is allowed and the URI is chopped at the |
82806837 AJ |
9903 | first whitespace. |
9904 | ||
9905 | ||
9906 | NOTE the current Squid implementation of encode and chop violates | |
9907 | RFC2616 by not using a 301 redirect after altering the URL. | |
5473c134 | 9908 | DOC_END |
a58ff010 | 9909 | |
5473c134 | 9910 | NAME: chroot |
9911 | TYPE: string | |
9912 | LOC: Config.chroot_dir | |
a58ff010 | 9913 | DEFAULT: none |
9914 | DOC_START | |
9f37c18a | 9915 | Specifies a directory where Squid should do a chroot() while |
2d89f399 HN |
9916 | initializing. This also causes Squid to fully drop root |
9917 | privileges after initializing. This means, for example, if you | |
9918 | use a HTTP port less than 1024 and try to reconfigure, you may | |
9919 | get an error saying that Squid can not open the port. | |
5473c134 | 9920 | DOC_END |
a58ff010 | 9921 | |
5473c134 | 9922 | NAME: balance_on_multiple_ip |
9923 | TYPE: onoff | |
9924 | LOC: Config.onoff.balance_on_multiple_ip | |
cc192b50 | 9925 | DEFAULT: off |
5473c134 | 9926 | DOC_START |
cc192b50 | 9927 | Modern IP resolvers in squid sort lookup results by preferred access. |
9928 | By default squid will use these IP in order and only rotates to | |
9929 | the next listed when the most preffered fails. | |
9930 | ||
5473c134 | 9931 | Some load balancing servers based on round robin DNS have been |
9932 | found not to preserve user session state across requests | |
9933 | to different IP addresses. | |
a58ff010 | 9934 | |
cc192b50 | 9935 | Enabling this directive Squid rotates IP's per request. |
a58ff010 | 9936 | DOC_END |
9937 | ||
5473c134 | 9938 | NAME: pipeline_prefetch |
079a8480 AJ |
9939 | TYPE: pipelinePrefetch |
9940 | LOC: Config.pipeline_max_prefetch | |
9941 | DEFAULT: 0 | |
9942 | DEFAULT_DOC: Do not pre-parse pipelined requests. | |
a58ff010 | 9943 | DOC_START |
079a8480 AJ |
9944 | HTTP clients may send a pipeline of 1+N requests to Squid using a |
9945 | single connection, without waiting for Squid to respond to the first | |
9946 | of those requests. This option limits the number of concurrent | |
9947 | requests Squid will try to handle in parallel. If set to N, Squid | |
9948 | will try to receive and process up to 1+N requests on the same | |
9949 | connection concurrently. | |
a58ff010 | 9950 | |
079a8480 | 9951 | Defaults to 0 (off) for bandwidth management and access logging |
5473c134 | 9952 | reasons. |
a0e23afd | 9953 | |
079a8480 AJ |
9954 | NOTE: pipelining requires persistent connections to clients. |
9955 | ||
a0e23afd | 9956 | WARNING: pipelining breaks NTLM and Negotiate/Kerberos authentication. |
5473c134 | 9957 | DOC_END |
a58ff010 | 9958 | |
5473c134 | 9959 | NAME: high_response_time_warning |
9960 | TYPE: int | |
9961 | COMMENT: (msec) | |
9962 | LOC: Config.warnings.high_rptm | |
9963 | DEFAULT: 0 | |
638402dd | 9964 | DEFAULT_DOC: disabled. |
5473c134 | 9965 | DOC_START |
9966 | If the one-minute median response time exceeds this value, | |
9967 | Squid prints a WARNING with debug level 0 to get the | |
9968 | administrators attention. The value is in milliseconds. | |
a58ff010 | 9969 | DOC_END |
9970 | ||
5473c134 | 9971 | NAME: high_page_fault_warning |
9972 | TYPE: int | |
9973 | LOC: Config.warnings.high_pf | |
9974 | DEFAULT: 0 | |
638402dd | 9975 | DEFAULT_DOC: disabled. |
cc9f92d4 | 9976 | DOC_START |
5473c134 | 9977 | If the one-minute average page fault rate exceeds this |
9978 | value, Squid prints a WARNING with debug level 0 to get | |
9979 | the administrators attention. The value is in page faults | |
9980 | per second. | |
9981 | DOC_END | |
cc9f92d4 | 9982 | |
5473c134 | 9983 | NAME: high_memory_warning |
9984 | TYPE: b_size_t | |
9985 | LOC: Config.warnings.high_memory | |
f2228f3b | 9986 | IFDEF: HAVE_MSTATS&&HAVE_GNUMALLOC_H |
904971da | 9987 | DEFAULT: 0 KB |
638402dd | 9988 | DEFAULT_DOC: disabled. |
5473c134 | 9989 | DOC_START |
4bf2a476 FC |
9990 | If the memory usage (as determined by gnumalloc, if available and used) |
9991 | exceeds this amount, Squid prints a WARNING with debug level 0 to get | |
5473c134 | 9992 | the administrators attention. |
9993 | DOC_END | |
4bf2a476 | 9994 | # TODO: link high_memory_warning to mempools? |
cc9f92d4 | 9995 | |
5473c134 | 9996 | NAME: sleep_after_fork |
9997 | COMMENT: (microseconds) | |
9998 | TYPE: int | |
9999 | LOC: Config.sleep_after_fork | |
10000 | DEFAULT: 0 | |
10001 | DOC_START | |
10002 | When this is set to a non-zero value, the main Squid process | |
10003 | sleeps the specified number of microseconds after a fork() | |
10004 | system call. This sleep may help the situation where your | |
10005 | system reports fork() failures due to lack of (virtual) | |
10006 | memory. Note, however, if you have a lot of child | |
10007 | processes, these sleep delays will add up and your | |
10008 | Squid will not service requests for some amount of time | |
10009 | until all the child processes have been started. | |
10010 | On Windows value less then 1000 (1 milliseconds) are | |
10011 | rounded to 1000. | |
cc9f92d4 | 10012 | DOC_END |
10013 | ||
b6696974 | 10014 | NAME: windows_ipaddrchangemonitor |
7aa9bb3e | 10015 | IFDEF: _SQUID_WINDOWS_ |
b6696974 GS |
10016 | COMMENT: on|off |
10017 | TYPE: onoff | |
10018 | DEFAULT: on | |
10019 | LOC: Config.onoff.WIN32_IpAddrChangeMonitor | |
10020 | DOC_START | |
10021 | On Windows Squid by default will monitor IP address changes and will | |
10022 | reconfigure itself after any detected event. This is very useful for | |
10023 | proxies connected to internet with dial-up interfaces. | |
10024 | In some cases (a Proxy server acting as VPN gateway is one) it could be | |
10025 | desiderable to disable this behaviour setting this to 'off'. | |
10026 | Note: after changing this, Squid service must be restarted. | |
10027 | DOC_END | |
10028 | ||
a98c2da5 AJ |
10029 | NAME: eui_lookup |
10030 | TYPE: onoff | |
10031 | IFDEF: USE_SQUID_EUI | |
10032 | DEFAULT: on | |
10033 | LOC: Eui::TheConfig.euiLookup | |
10034 | DOC_START | |
10035 | Whether to lookup the EUI or MAC address of a connected client. | |
10036 | DOC_END | |
10037 | ||
f3f0f563 AJ |
10038 | NAME: max_filedescriptors max_filedesc |
10039 | TYPE: int | |
10040 | DEFAULT: 0 | |
638402dd | 10041 | DEFAULT_DOC: Use operating system limits set by ulimit. |
f3f0f563 AJ |
10042 | LOC: Config.max_filedescriptors |
10043 | DOC_START | |
638402dd AJ |
10044 | Reduce the maximum number of filedescriptors supported below |
10045 | the usual operating system defaults. | |
f3f0f563 | 10046 | |
638402dd | 10047 | Remove from squid.conf to inherit the current ulimit setting. |
f3f0f563 AJ |
10048 | |
10049 | Note: Changing this requires a restart of Squid. Also | |
638402dd | 10050 | not all I/O types supports large values (eg on Windows). |
f3f0f563 AJ |
10051 | DOC_END |
10052 | ||
ec69bdb2 CT |
10053 | NAME: force_request_body_continuation |
10054 | TYPE: acl_access | |
10055 | LOC: Config.accessList.forceRequestBodyContinuation | |
10056 | DEFAULT: none | |
10057 | DEFAULT_DOC: Deny, unless rules exist in squid.conf. | |
10058 | DOC_START | |
10059 | This option controls how Squid handles data upload requests from HTTP | |
10060 | and FTP agents that require a "Please Continue" control message response | |
10061 | to actually send the request body to Squid. It is mostly useful in | |
10062 | adaptation environments. | |
10063 | ||
10064 | When Squid receives an HTTP request with an "Expect: 100-continue" | |
10065 | header or an FTP upload command (e.g., STOR), Squid normally sends the | |
10066 | request headers or FTP command information to an adaptation service (or | |
10067 | peer) and waits for a response. Most adaptation services (and some | |
10068 | broken peers) may not respond to Squid at that stage because they may | |
10069 | decide to wait for the HTTP request body or FTP data transfer. However, | |
10070 | that request body or data transfer may never come because Squid has not | |
10071 | responded with the HTTP 100 or FTP 150 (Please Continue) control message | |
10072 | to the request sender yet! | |
10073 | ||
10074 | An allow match tells Squid to respond with the HTTP 100 or FTP 150 | |
10075 | (Please Continue) control message on its own, before forwarding the | |
10076 | request to an adaptation service or peer. Such a response usually forces | |
10077 | the request sender to proceed with sending the body. A deny match tells | |
10078 | Squid to delay that control response until the origin server confirms | |
10079 | that the request body is needed. Delaying is the default behavior. | |
10080 | DOC_END | |
10081 | ||
afc753f3 EB |
10082 | NAME: server_pconn_for_nonretriable |
10083 | TYPE: acl_access | |
10084 | DEFAULT: none | |
10085 | DEFAULT_DOC: Open new connections for forwarding requests Squid cannot retry safely. | |
10086 | LOC: Config.accessList.serverPconnForNonretriable | |
10087 | DOC_START | |
10088 | This option provides fine-grained control over persistent connection | |
10089 | reuse when forwarding HTTP requests that Squid cannot retry. It is useful | |
10090 | in environments where opening new connections is very expensive | |
10091 | (e.g., all connections are secured with TLS with complex client and server | |
10092 | certificate validation) and race conditions associated with persistent | |
10093 | connections are very rare and/or only cause minor problems. | |
10094 | ||
10095 | HTTP prohibits retrying unsafe and non-idempotent requests (e.g., POST). | |
10096 | Squid limitations also prohibit retrying all requests with bodies (e.g., PUT). | |
10097 | By default, when forwarding such "risky" requests, Squid opens a new | |
10098 | connection to the server or cache_peer, even if there is an idle persistent | |
10099 | connection available. When Squid is configured to risk sending a non-retriable | |
10100 | request on a previously used persistent connection, and the server closes | |
10101 | the connection before seeing that risky request, the user gets an error response | |
10102 | from Squid. In most cases, that error response will be HTTP 502 (Bad Gateway) | |
10103 | with ERR_ZERO_SIZE_OBJECT or ERR_WRITE_ERROR (peer connection reset) error detail. | |
10104 | ||
10105 | If an allow rule matches, Squid reuses an available idle persistent connection | |
10106 | (if any) for the request that Squid cannot retry. If a deny rule matches, then | |
10107 | Squid opens a new connection for the request that Squid cannot retry. | |
10108 | ||
10109 | This option does not affect requests that Squid can retry. They will reuse idle | |
10110 | persistent connections (if any). | |
10111 | ||
10112 | This clause only supports fast acl types. | |
10113 | See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details. | |
10114 | ||
10115 | Example: | |
10116 | acl SpeedIsWorthTheRisk method POST | |
10117 | server_pconn_for_nonretriable allow SpeedIsWorthTheRisk | |
10118 | DOC_END | |
10119 | ||
cccac0a2 | 10120 | EOF |