File: templates

package info (click to toggle)
squid 2.6.5-6etch5
  • links: PTS
  • area: main
  • in suites: etch
  • size: 12,540 kB
  • ctags: 13,801
  • sloc: ansic: 105,278; sh: 6,083; makefile: 1,297; perl: 1,245; awk: 40
file content (88 lines) | stat: -rw-r--r-- 4,066 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
Template: squid/http_anonymizer
Type: note
_Description: The http_anonymizer directive has been replaced with header_replace and header_access.
 The http_anonymizer directive that was present in squid 2.1 and 2.2
 doesn't exist anymore in squid 2.3 and up. It has been replaced with
 header_replace and header_access that provide more fine-grained control over
 HTTP headers. Right now, your squid doesn't anonymize the HTTP
 headers anymore so you probably want to fix this. The new format is
 explained in the new 2.5 config file, of which you probably have a copy in
 /usr/share/doc/squid/examples/squid.conf.

Template: squid/anonymize_headers
Type: note
_Description: The anonymize_headers and fake_user_agent directives have been replaced with header_access and header_replace.
 The anonymize_headers and fake_user_agent directives that were present in squid 2.3 and 2.4 don't exist anymore in squid 2.5 and up. They have been replaced 
 with header_replace and header_access that provide more fine-grained control 
 over HTTP headers. Right now, your squid doesn't anonymize the HTTP
 headers anymore so you probably want to fix this. The new format is
 explained in the new 2.5 config file, of which you probably have a copy in
 /usr/share/doc/squid/examples/squid.conf.

Template: squid/old_version
Type: boolean
Default: false
_Description: There is no automatic upgrade path to squid 2.5.
              SQUID 2.5 INSTALLATION WARNING
 .
 You are upgrading squid from an 1.x version to the 2.5 version. The 1.x
 and 2.5 versions are NOT compatible. The structure of the cache directory
 is different and the configuration file "squid.conf" is not entirely
 compatible.
 .
 If you have an old cache directory, please quit NOW and remove the old
 cache by hand (in /var/spool/squid). Then re-install this squid version.
 .
 Also, please accept the new configuration file. After upgrading your old
 configuration file can be found in "/etc/squid.conf.dpkg-old". Then you
 have to edit the new configuration file by hand to match your old
 configuration.
 .
 Do you want to quit now?

Template: squid-cgi/cachemgr
Type: note
_Description: squid-cgi now uses config file for target ACL
 squid-cgi now checks a configuration file before connecting to the target
 host. Only allowed target will be contacted. Please add hosts you want to
 access to the file /etc/squid/cachemgr.conf, one per line in the form
 .
   hostname:port

Template: squid/fix_lines
Type: boolean
Default: true
_Description: Upgrade squid.conf automatically?
 Incompatible settings have been found in the existing squid.conf file;
 they will prevent squid from starting or working correctly. However, this
 setup can try to modify them to work again. Do you want to apply the
 changes?

Template: squid/authenticate_program
Type: note
_Description: The authenticate_program directive has been replaced with auth_param.
 The authenticate_program directive that was present in squid <= 2.4
 doesn't exist anymore in squid 2.5 and up. All authentication directives
 have been replaced with auth_param. Right now, your squid doesn't
 authenticate users anymore so you probably want to fix this. The new
 format is explained in the new 2.5 config file, of which you probably have
 a copy in /usr/share/doc/squid/examples/squid.conf.

Template: squid/largefiles_warning
Type: note
_Description: Warning: squid may crash when logfiles size is bigger than 2GB.
 Squid may crash if any of the logfiles grows bigger than 2GB. Please
 configure /etc/logrotate.d/squid accordingly to your site's traffic.

Template: squid/fix_cachedir_perms
Type: boolean
Default: false
_Description: Fix permissions of cache_dir?
 Values for cache_effective_user and/or cache_effective_group in config file 
 are incompatible with owner/group of cache directories. Do you want to
 automatically fix permissions on cache directory?
 .
 WARNING: If you specified a cache directory different from /var/spool/squid
 and selected some other directory used by other programs (e.g. /tmp), this
 could affect those programs.