当前位置：首页 » 专业资讯

开发技术指南» 文章正文

    引言： # WELCOME TO SQUID 2 # --------

 

 

squid的配置文件
上一页   ...# welcome to squid 2 # ------------------ # # this is the default squid configuration file. you may wish # to look at the squid home page (http://www.squid-cache.org/) # for the faq and other documentation. # # the default squid config file shows what the defaults for # various options happen to be. if you dont need to change the # default, you shouldnt uncomment the line. doing so may cause # run-time problems. in some cases "none" refers to no default # setting at all, while in other cases it refers to a valid # option - the comments for that keyword indicate if this is the # case. # # network options # ----------------------------------------------------------------------------- # tag: http_port # usage: port # hostname:port # 1.2.3.4:port # # the socket addresses where squid will listen for http client # requests. you may specify multiple socket addresses. # there are three forms: port alone, hostname with port, and # ip address with port. if you specify a hostname or ip # address, then squid binds the socket to that specific # address. this replaces the old tcp_incoming_address # option. most likely, you do not need to bind to a specific # address, so you can use the port number alone. # # the default port number is 3128. # # if you are running squid in accelerator mode, then you # probably want to listen on port 80 also, or instead. # # the -a command line option will override the *first* port # number listed here. that option will not override an ip # address, however. # # you may specify multiple socket addresses on multiple lines. # # if you run squid on a dual-homed machine with an internal # and an external interface then we recommend you to specify the # internal address:port in http_port. this way squid will only be # visible on the internal address. # #default: http_port 3128 # tag: https_port # usage: [ip:]port cert=certificate.pem [key=key.pem] [options...] # # the socket address where squid will listen for https client # requests. # # this is really only useful for situations where you are running # squid in accelerator mode and you want to do the ssl work at the # accelerator level. # # you may specify multiple socket addresses on multiple lines, # each with their own ssl certificate and/or options. # # options: # # cert= path to ssl certificate (pem format) # # key= path to ssl private key file (pem format) # if not specified, the certificate file is # assumed to be a combined certificate and # key file # # version= the version of ssl/tls supported # 1 automatic (default) # 2 sslv2 only # 3 sslv3 only # 4 tlsv1 only # # cipher= colon separated list of supported ciphers # # options= varions ssl engine options. the most important # being: # no_sslv2 disallow the use of sslv2 # no_sslv3 disallow the use of sslv3 # no_tlsv1 disallow the use of tlsv1 # see src/ssl_support.c or openssl documentation # for a more complete list. # #default: # none # tag: ssl_unclean_shutdown # some browsers (especially msie) bugs out on ssl shutdown # messages. # #default: # ssl_unclean_shutdown off # tag: icp_port # the port number where squid sends and receives icp queries to # and from neighbor caches. default is 3130. to disable use # "0". may be overridden with -u on the command line. # #default: icp_port 3130 # tag: htcp_port # note: this option is only available if squid is rebuilt with the # --enable-htcp option # # the port number where squid sends and receives htcp queries to # and from neighbor caches. default is 4827. to disable use # "0". # #default: # htcp_port 4827 # tag: mcast_groups # this tag specifies a list of multicast groups which your server # should join to receive multicasted icp queries. # # note! be very careful what you put here! be sure you # understand the difference between an icp _query_ and an icp # _reply_. this option is to be set only if you want to receive # multicast queries. do not set this option to send multicast # icp (use cache_peer for that). icp replies are always sent via # unicast, so this option does not affect whether or not you will # receive replies from multicast group members. # # you must be very careful to not use a multicast address which # is already in use by another group of caches. # # if you are unsure about multicast, please read the multicast # chapter in the squid faq (http://www.squid-cache.org/faq/). # # usage: mcast_groups 239.128.16.128 224.0.1.20 # # by default, squid doesnt listen on any multicast groups. # #default: # none # tag: udp_incoming_address # tag: udp_outgoing_address # udp_incoming_address is used for the icp socket receiving packets # from other caches. # udp_outgoing_address is used for icp packets sent out to other # caches. # # the default behavior is to not bind to any specific address. # # a udp_incoming_address value of 0.0.0.0 indicates that squid should # listen for udp messages on all available interfaces. # # if udp_outgoing_address is set to 255.255.255.255 (the default) # then it will use the same socket as udp_incoming_address. only # change this if you want to have icp queries sent using another # address than where this squid listens for icp queries from other # caches. # # note, udp_incoming_address and udp_outgoing_address can not # have the same value since they both use port 3130. # #default: # udp_incoming_address 0.0.0.0 # udp_outgoing_address 255.255.255.255 # options which affect the neighbor selection algorithm # ----------------------------------------------------------------------------- # tag: cache_peer # to specify other caches in a hierarchy, use the format: # # cache_peer hostname type http_port icp_port # # for example, # # # proxy icp # # hostname type port port options # # -------------------- -------- ----- ----- ----------- # cache_peer parent.foo.net parent 3128 3130 [proxy-only] # cache_peer sib1.foo.net sibling 3128 3130 [proxy-only] # cache_peer sib2.foo.net sibling 3128 3130 [proxy-only] # # type: either parent, sibling, or multicast. # # proxy_port: the port number where the cache listens for proxy # requests. # # icp_port: used for querying neighbor caches about # objects. to have a non-icp neighbor # specify 7 for the icp port and make sure the # neighbor machine has the udp echo port # enabled in its /etc/inetd.conf file. # # options: proxy-only # weight=n # ttl=n # no-query # default # round-robin # multicast-responder # closest-only # no-digest # no-netdb-exchange # no-delay # login=user:password | pass | *:password # connect-timeout=nn # digest-url=url # allow-miss # max-conn # htcp # carp-load-factor # # use proxy-only to specify that objects fetched # from this cache should not be saved locally. # # use weight=n to specify a weighted parent. # the weight must be an integer. the default weight # is 1, larger weights are favored more. # # use ttl=n to specify a ip multicast ttl to use # when sending an icp queries to this address. # only useful when sending to a multicast group. # because we dont accept icp replies from random # hosts, you must configure other group members as # peers with the multicast-responder option below. # # use no-query to not send icp queries to this # neighbor. # # use default if this is a parent cache which can # be used as a "last-resort." you should probably # only use default in situations where you cannot # use icp with your parent cache(s). # # use round-robin to d
...   下一页

» 本期热门文章：

· 热门栏目：

» 相关精选文章

» 其它相关：