privoxy.config 31 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073
  1. # Sample Configuration File for Privoxy v3.0.x
  2. #
  3. # Copyright (C) 2001-2004 Privoxy Developers http://privoxy.org
  4. #
  5. # $Id$
  6. #
  7. ####################################################################
  8. # #
  9. # Table of Contents #
  10. # #
  11. # I. INTRODUCTION #
  12. # II. FORMAT OF THE CONFIGURATION FILE #
  13. # #
  14. # 1. CONFIGURATION AND LOG FILE LOCATIONS #
  15. # 2. LOCAL SET-UP DOCUMENTATION #
  16. # 3. DEBUGGING #
  17. # 4. ACCESS CONTROL AND SECURITY #
  18. # 5. FORWARDING #
  19. # 6. WINDOWS GUI OPTIONS #
  20. # #
  21. ####################################################################
  22. #
  23. #
  24. # I. INTRODUCTION
  25. # ===============
  26. #
  27. # This file holds the Privoxy configuration. If you modify this file,
  28. # you will need to send a couple of requests to the proxy before any
  29. # changes take effect.
  30. #
  31. # When starting Privoxy on Unix systems, give the name of this file as
  32. # an argument. On Windows systems, Privoxy will look for this file
  33. # with the name 'config.txt' in the same directory where Privoxy
  34. # is installed.
  35. #
  36. #
  37. # II. FORMAT OF THE CONFIGURATION FILE
  38. # ====================================
  39. #
  40. # Configuration lines consist of an initial keyword followed by a
  41. # list of values, all separated by whitespace (any number of spaces
  42. # or tabs). For example,
  43. #
  44. # actionsfile default.action
  45. #
  46. # Indicates that the actionsfile is named 'default.action'.
  47. #
  48. # The '#' indicates a comment. Any part of a line following a '#'
  49. # is ignored, except if the '#' is preceded by a '\'.
  50. #
  51. # Thus, by placing a # at the start of an existing configuration line,
  52. # you can make it a comment and it will be treated as if it weren't
  53. # there. This is called "commenting out" an option and can be useful.
  54. #
  55. # Note that commenting out and option and leaving it at its default
  56. # are two completely different things! Most options behave very
  57. # differently when unset. See the the "Effect if unset" explanation
  58. # in each option's description for details.
  59. #
  60. # Long lines can be continued on the next line by using a `\' as the
  61. # last character.
  62. #
  63. #
  64. # 1. CONFIGURATION AND LOG FILE LOCATIONS
  65. # =======================================
  66. #
  67. # Privoxy can (and normally does) use a number of other files for
  68. # additional configuration, help and logging. This section of the
  69. # configuration file tells Privoxy where to find those other files.
  70. #
  71. # The user running Privoxy, must have read permission for all
  72. # configuration files, and write permission to any files that would
  73. # be modified, such as log files and actions files.
  74. #
  75. #
  76. # 1.1. confdir
  77. # ============
  78. #
  79. # Specifies:
  80. #
  81. # The directory where the other configuration files are located
  82. #
  83. # Type of value:
  84. #
  85. # Path name
  86. #
  87. # Default value:
  88. #
  89. # /etc/privoxy (Unix) or Privoxy installation dir (Windows)
  90. #
  91. # Effect if unset:
  92. #
  93. # Mandatory
  94. #
  95. # Notes:
  96. #
  97. # No trailing "/", please
  98. #
  99. # When development goes modular and multi-user, the blocker,
  100. # filter, and per-user config will be stored in subdirectories of
  101. # "confdir". For now, the configuration directory structure is
  102. # flat, except for confdir/templates, where the HTML templates
  103. # for CGI output reside (e.g. Privoxy's 404 error page).
  104. #
  105. confdir .
  106. #
  107. # 1.2. logdir
  108. # ===========
  109. #
  110. # Specifies:
  111. #
  112. # The directory where all logging takes place (i.e. where logfile
  113. # and jarfile are located)
  114. #
  115. # Type of value:
  116. #
  117. # Path name
  118. #
  119. # Default value:
  120. #
  121. # /var/log/privoxy (Unix) or Privoxy installation dir (Windows)
  122. #
  123. # Effect if unset:
  124. #
  125. # Mandatory
  126. #
  127. # Notes:
  128. #
  129. # No trailing "/", please
  130. #
  131. logdir .
  132. #
  133. # 1.3. actionsfile
  134. # ================
  135. #
  136. # Specifies:
  137. #
  138. # The actions file(s) to use
  139. #
  140. # Type of value:
  141. #
  142. # File name, relative to confdir, without the .action suffix
  143. #
  144. # Default values:
  145. #
  146. # standard # Internal purposes, no editing recommended
  147. #
  148. # default # Main actions file
  149. #
  150. # user # User customizations
  151. #
  152. # Effect if unset:
  153. #
  154. # No actions are taken at all. Simple neutral proxying.
  155. #
  156. # Notes:
  157. #
  158. # Multiple actionsfile lines are permitted, and are in fact
  159. # recommended!
  160. #
  161. # The default values include standard.action, which is used
  162. # for internal purposes and should be loaded, default.action,
  163. # which is the "main" actions file maintained by the developers,
  164. # and user.action, where you can make your personal additions.
  165. #
  166. # Actions files are where all the per site and per URL
  167. # configuration is done for ad blocking, cookie management,
  168. # privacy considerations, etc. There is no point in using Privoxy
  169. # without at least one actions file.
  170. #
  171. actionsfile standard # Internal purpose, recommended
  172. actionsfile default # Main actions file
  173. actionsfile user # User customizations
  174. #
  175. # 1.4. filterfile
  176. # ===============
  177. #
  178. # Specifies:
  179. #
  180. # The filter file to use
  181. #
  182. # Type of value:
  183. #
  184. # File name, relative to confdir
  185. #
  186. # Default value:
  187. #
  188. # default.filter (Unix) or default.filter.txt (Windows)
  189. #
  190. # Effect if unset:
  191. #
  192. # No textual content filtering takes place, i.e. all +filter{name}
  193. # actions in the actions files are turned neutral.
  194. #
  195. # Notes:
  196. #
  197. # The filter file contains content modification rules that use
  198. # regular expressions. These rules permit powerful changes on the
  199. # content of Web pages, e.g., you could disable your favorite
  200. # JavaScript annoyances, re-write the actual displayed text,
  201. # or just have some fun replacing "Microsoft" with "MicroSuck"
  202. # wherever it appears on a Web page.
  203. #
  204. # The +filter{name} actions rely on the relevant filter (name)
  205. # to be defined in the filter file!
  206. #
  207. # A pre-defined filter file called default.filter that contains
  208. # a bunch of handy filters for common problems is included in the
  209. # distribution. See the section on the filter action for a list.
  210. #
  211. filterfile default.filter
  212. #
  213. # 1.5. logfile
  214. # ============
  215. #
  216. # Specifies:
  217. #
  218. # The log file to use
  219. #
  220. # Type of value:
  221. #
  222. # File name, relative to logdir
  223. #
  224. # Default value:
  225. #
  226. # logfile (Unix) or privoxy.log (Windows)
  227. #
  228. # Effect if unset:
  229. #
  230. # No log file is used, all log messages go to the console (STDERR).
  231. #
  232. # Notes:
  233. #
  234. # The windows version will additionally log to the console.
  235. #
  236. # The logfile is where all logging and error messages are
  237. # written. The level of detail and number of messages are set with
  238. # the debug option (see below). The logfile can be useful for
  239. # tracking down a problem with Privoxy (e.g., it's not blocking
  240. # an ad you think it should block) but in most cases you probably
  241. # will never look at it.
  242. #
  243. # Your logfile will grow indefinitely, and you will probably
  244. # want to periodically remove it. On Unix systems, you can do
  245. # this with a cron job (see "man cron"). For Red Hat, a logrotate
  246. # script has been included.
  247. #
  248. # On SuSE Linux systems, you can place a line like
  249. # "/var/log/privoxy.* +1024k 644 nobody.nogroup" in /etc/logfiles,
  250. # with the effect that cron.daily will automatically archive,
  251. # gzip, and empty the log, when it exceeds 1M size.
  252. #
  253. # Any log files must be writable by whatever user Privoxy is
  254. # being run as (default on UNIX, user id is "privoxy").
  255. #
  256. #logfile logfile
  257. #
  258. # 1.6. jarfile
  259. # ============
  260. #
  261. # Specifies:
  262. #
  263. # The file to store intercepted cookies in
  264. #
  265. # Type of value:
  266. #
  267. # File name, relative to logdir
  268. #
  269. # Default value:
  270. #
  271. # jarfile (Unix) or privoxy.jar (Windows)
  272. #
  273. # Effect if unset:
  274. #
  275. # Intercepted cookies are not stored at all.
  276. #
  277. # Notes:
  278. #
  279. # The jarfile may grow to ridiculous sizes over time.
  280. #
  281. #jarfile jarfile
  282. #
  283. # 1.7. trustfile
  284. # ==============
  285. #
  286. # Specifies:
  287. #
  288. # The trust file to use
  289. #
  290. # Type of value:
  291. #
  292. # File name, relative to confdir
  293. #
  294. # Default value:
  295. #
  296. # Unset (commented out). When activated: trust (Unix) or trust.txt
  297. # (Windows)
  298. #
  299. # Effect if unset:
  300. #
  301. # The entire trust mechanism is turned off.
  302. #
  303. # Notes:
  304. #
  305. # The trust mechanism is an experimental feature for building
  306. # white-lists and should be used with care. It is NOT recommended
  307. # for the casual user.
  308. #
  309. # If you specify a trust file, Privoxy will only allow access to
  310. # sites that are specified in the trustfile. Sites can be listed
  311. # in one of two ways:
  312. #
  313. # Prepending a ~ character limits access to this site only (and
  314. # any sub-paths within this site), e.g. ~www.example.com.
  315. #
  316. # Or, you can designate sites as trusted referrers, by prepending
  317. # the name with a + character. The effect is that access to
  318. # untrusted sites will be granted -- but only if a link from this
  319. # trusted referrer was used. The link target will then be added
  320. # to the "trustfile" so that future, direct accesses will be
  321. # granted. Sites added via this mechanism do not become trusted
  322. # referrers themselves (i.e. they are added with a ~ designation).
  323. #
  324. # If you use the + operator in the trust file, it may grow
  325. # considerably over time.
  326. #
  327. # It is recommended that Privoxy be compiled with the
  328. # --disable-force, --disable-toggle and --disable-editor options,
  329. # if this feature is to be used.
  330. #
  331. # Possible applications include limiting Internet access for
  332. # children.
  333. #
  334. #trustfile trust
  335. #
  336. # 2. LOCAL SET-UP DOCUMENTATION
  337. # =============================
  338. #
  339. # If you intend to operate Privoxy for more users than just yourself,
  340. # it might be a good idea to let them know how to reach you, what
  341. # you block and why you do that, your policies, etc.
  342. #
  343. #
  344. # 2.1. user-manual
  345. # ================
  346. #
  347. # Specifies:
  348. #
  349. # Location of the Privoxy User Manual.
  350. #
  351. # Type of value:
  352. #
  353. # A fully qualified URI
  354. #
  355. # Default value:
  356. #
  357. # Unset
  358. #
  359. # Effect if unset:
  360. #
  361. # http://www.privoxy.org/version/user-manual/ will be used,
  362. # where version is the Privoxy version.
  363. #
  364. # Notes:
  365. #
  366. # The User Manual URI is used for help links from some of the
  367. # internal CGI pages. The manual itself is normally packaged
  368. # with the binary distributions, so you probably want to set this
  369. # to a locally installed copy. For multi-user setups, you could
  370. # provide a copy on a local webserver for all your users and use
  371. # the corresponding URL here.
  372. #
  373. # Examples:
  374. #
  375. # Unix, in local filesystem:
  376. #
  377. # user-manual file:///usr/share/doc/privoxy-3.0.1/user-manual/index.html
  378. #
  379. # Windows, in local filesystem, must use forward slash notation,
  380. # and %20 to denote spaces in path names:
  381. #
  382. # user-manual file:///c:/some%20dir/privoxy/user-manual/index.html
  383. #
  384. # Windows, UNC notation (forward slashes required again):
  385. #
  386. # user-manual file://///some-server/some-path/privoxy/user-manual/index.html
  387. #
  388. # Any platform, on local webserver (called "local-webserver"):
  389. #
  390. # user-manual http://local-webserver/privoxy-user-manual/
  391. #
  392. # WARNING!!!
  393. #
  394. # If set, this option should be the first option in the config
  395. # file, because it is used while the config file is being read.
  396. #
  397. #user-manual http://www.privoxy.org/user-manual/
  398. #
  399. # 2.2. trust-info-url
  400. # ===================
  401. #
  402. # Specifies:
  403. #
  404. # A URL to be displayed in the error page that users will see if
  405. # access to an untrusted page is denied.
  406. #
  407. # Type of value:
  408. #
  409. # URL
  410. #
  411. # Default value:
  412. #
  413. # Two example URL are provided
  414. #
  415. # Effect if unset:
  416. #
  417. # No links are displayed on the "untrusted" error page.
  418. #
  419. # Notes:
  420. #
  421. # The value of this option only matters if the experimental trust
  422. # mechanism has been activated. (See trustfile above.)
  423. #
  424. # If you use the trust mechanism, it is a good idea to write
  425. # up some on-line documentation about your trust policy and to
  426. # specify the URL(s) here. Use multiple times for multiple URLs.
  427. #
  428. # The URL(s) should be added to the trustfile as well, so users
  429. # don't end up locked out from the information on why they were
  430. # locked out in the first place!
  431. #
  432. trust-info-url http://www.example.com/why_we_block.html
  433. trust-info-url http://www.example.com/what_we_allow.html
  434. #
  435. # 2.3. admin-address
  436. # ==================
  437. #
  438. # Specifies:
  439. #
  440. # An email address to reach the proxy administrator.
  441. #
  442. # Type of value:
  443. #
  444. # Email address
  445. #
  446. # Default value:
  447. #
  448. # Unset
  449. #
  450. # Effect if unset:
  451. #
  452. # No email address is displayed on error pages and the CGI user
  453. # interface.
  454. #
  455. # Notes:
  456. #
  457. # If both admin-address and proxy-info-url are unset, the whole
  458. # "Local Privoxy Support" box on all generated pages will not
  459. # be shown.
  460. #
  461. #admin-address privoxy-admin@example.com
  462. #
  463. # 2.4. proxy-info-url
  464. # ===================
  465. #
  466. # Specifies:
  467. #
  468. # A URL to documentation about the local Privoxy setup,
  469. # configuration or policies.
  470. #
  471. # Type of value:
  472. #
  473. # URL
  474. #
  475. # Default value:
  476. #
  477. # Unset
  478. #
  479. # Effect if unset:
  480. #
  481. # No link to local documentation is displayed on error pages and
  482. # the CGI user interface.
  483. #
  484. # Notes:
  485. #
  486. # If both admin-address and proxy-info-url are unset, the whole
  487. # "Local Privoxy Support" box on all generated pages will not
  488. # be shown.
  489. #
  490. # This URL shouldn't be blocked ;-)
  491. #
  492. #proxy-info-url http://www.example.com/proxy-service.html
  493. #
  494. # 3. DEBUGGING
  495. # ============
  496. #
  497. # These options are mainly useful when tracing a problem. Note that
  498. # you might also want to invoke Privoxy with the --no-daemon command
  499. # line option when debugging.
  500. #
  501. #
  502. # 3.1. debug
  503. # ==========
  504. #
  505. # Specifies:
  506. #
  507. # Key values that determine what information gets logged to
  508. # the logfile.
  509. #
  510. # Type of value:
  511. #
  512. # Integer values
  513. #
  514. # Default value:
  515. #
  516. # 12289 (i.e.: URLs plus informational and warning messages)
  517. #
  518. # Effect if unset:
  519. #
  520. # Nothing gets logged.
  521. #
  522. # Notes:
  523. #
  524. # The available debug levels are:
  525. #
  526. # debug 1 # show each GET/POST/CONNECT request
  527. # debug 2 # show each connection status
  528. # debug 4 # show I/O status
  529. # debug 8 # show header parsing
  530. # debug 16 # log all data into the logfile
  531. # debug 32 # debug force feature
  532. # debug 64 # debug regular expression filter
  533. # debug 128 # debug fast redirects
  534. # debug 256 # debug GIF de-animation
  535. # debug 512 # Common Log Format
  536. # debug 1024 # debug kill pop-ups
  537. # debug 2048 # CGI user interface
  538. # debug 4096 # Startup banner and warnings.
  539. # debug 8192 # Non-fatal errors
  540. #
  541. # To select multiple debug levels, you can either add them or
  542. # use multiple debug lines.
  543. #
  544. # A debug level of 1 is informative because it will show you each
  545. # request as it happens. 1, 4096 and 8192 are highly recommended
  546. # so that you will notice when things go wrong. The other levels
  547. # are probably only of interest if you are hunting down a specific
  548. # problem. They can produce a hell of an output (especially 16).
  549. #
  550. # The reporting of fatal errors (i.e. ones which crash Privoxy)
  551. # is always on and cannot be disabled.
  552. #
  553. # If you want to use CLF (Common Log Format), you should set
  554. # "debug 512" ONLY and not enable anything else.
  555. #
  556. #debug 1 # show each GET/POST/CONNECT request
  557. debug 4096 # Startup banner and warnings
  558. debug 8192 # Errors - *we highly recommended enabling this*
  559. #
  560. # 3.2. single-threaded
  561. # ====================
  562. #
  563. # Specifies:
  564. #
  565. # Whether to run only one server thread
  566. #
  567. # Type of value:
  568. #
  569. # None
  570. #
  571. # Default value:
  572. #
  573. # Unset
  574. #
  575. # Effect if unset:
  576. #
  577. # Multi-threaded (or, where unavailable: forked) operation,
  578. # i.e. the ability to serve multiple requests simultaneously.
  579. #
  580. # Notes:
  581. #
  582. # This option is only there for debug purposes and you should
  583. # never need to use it. It will drastically reduce performance.
  584. #
  585. #single-threaded
  586. #
  587. # 4. ACCESS CONTROL AND SECURITY
  588. # ==============================
  589. #
  590. # This section of the config file controls the security-relevant
  591. # aspects of Privoxy's configuration.
  592. #
  593. #
  594. # 4.1. listen-address
  595. # ===================
  596. #
  597. # Specifies:
  598. #
  599. # The IP address and TCP port on which Privoxy will listen for
  600. # client requests.
  601. #
  602. # Type of value:
  603. #
  604. # [IP-Address]:Port
  605. #
  606. # Default value:
  607. #
  608. # 127.0.0.1:8118
  609. #
  610. # Effect if unset:
  611. #
  612. # Bind to 127.0.0.1 (localhost), port 8118. This is suitable and
  613. # recommended for home users who run Privoxy on the same machine
  614. # as their browser.
  615. #
  616. # Notes:
  617. #
  618. # You will need to configure your browser(s) to this proxy address
  619. # and port.
  620. #
  621. # If you already have another service running on port 8118, or
  622. # if you want to serve requests from other machines (e.g. on your
  623. # local network) as well, you will need to override the default.
  624. #
  625. # If you leave out the IP address, Privoxy will bind to all
  626. # interfaces (addresses) on your machine and may become reachable
  627. # from the Internet. In that case, consider using access control
  628. # lists (ACL's, see below), and/or a firewall.
  629. #
  630. # If you open Privoxy to untrusted users, you will also want
  631. # to turn off the enable-edit-actions and enable-remote-toggle
  632. # options!
  633. #
  634. # Example:
  635. #
  636. # Suppose you are running Privoxy on a machine which has the
  637. # address 192.168.0.1 on your local private network (192.168.0.0)
  638. # and has another outside connection with a different address. You
  639. # want it to serve requests from inside only:
  640. #
  641. # listen-address 192.168.0.1:8118
  642. #
  643. listen-address 127.0.0.1:8118
  644. #
  645. # 4.2. toggle
  646. # ===========
  647. #
  648. # Specifies:
  649. #
  650. # Initial state of "toggle" status
  651. #
  652. # Type of value:
  653. #
  654. # 1 or 0
  655. #
  656. # Default value:
  657. #
  658. # 1
  659. #
  660. # Effect if unset:
  661. #
  662. # Act as if toggled on
  663. #
  664. # Notes:
  665. #
  666. # If set to 0, Privoxy will start in "toggled off" mode,
  667. # i.e. behave like a normal, content-neutral proxy where all ad
  668. # blocking, filtering, etc are disabled. See enable-remote-toggle
  669. # below. This is not really useful anymore, since toggling is
  670. # much easier via the web interface than via editing the conf file.
  671. #
  672. # The windows version will only display the toggle icon in the
  673. # system tray if this option is present.
  674. #
  675. toggle 1
  676. #
  677. # 4.3. enable-remote-toggle
  678. # =========================
  679. #
  680. # Specifies:
  681. #
  682. # Whether or not the web-based toggle feature may be used
  683. #
  684. # Type of value:
  685. #
  686. # 0 or 1
  687. #
  688. # Default value:
  689. #
  690. # 1
  691. #
  692. # Effect if unset:
  693. #
  694. # The web-based toggle feature is disabled.
  695. #
  696. # Notes:
  697. #
  698. # When toggled off, Privoxy acts like a normal, content-neutral
  699. # proxy, i.e. it acts as if none of the actions applied to
  700. # any URL.
  701. #
  702. # For the time being, access to the toggle feature can not be
  703. # controlled separately by "ACLs" or HTTP authentication, so that
  704. # everybody who can access Privoxy (see "ACLs" and listen-address
  705. # above) can toggle it for all users. So this option is not
  706. # recommended for multi-user environments with untrusted users.
  707. #
  708. # Note that you must have compiled Privoxy with support for this
  709. # feature, otherwise this option has no effect.
  710. #
  711. enable-remote-toggle 1
  712. #
  713. # 4.4. enable-edit-actions
  714. # ========================
  715. #
  716. # Specifies:
  717. #
  718. # Whether or not the web-based actions file editor may be used
  719. #
  720. # Type of value:
  721. #
  722. # 0 or 1
  723. #
  724. # Default value:
  725. #
  726. # 1
  727. #
  728. # Effect if unset:
  729. #
  730. # The web-based actions file editor is disabled.
  731. #
  732. # Notes:
  733. #
  734. # For the time being, access to the editor can not be controlled
  735. # separately by "ACLs" or HTTP authentication, so that everybody
  736. # who can access Privoxy (see "ACLs" and listen-address above)
  737. # can modify its configuration for all users. So this option is
  738. # not recommended for multi-user environments with untrusted users.
  739. #
  740. # Note that you must have compiled Privoxy with support for this
  741. # feature, otherwise this option has no effect.
  742. #
  743. enable-edit-actions 1
  744. #
  745. # 4.5. ACLs: permit-access and deny-access
  746. # ========================================
  747. #
  748. # Specifies:
  749. #
  750. # Who can access what.
  751. #
  752. # Type of value:
  753. #
  754. # src_addr[/src_masklen] [dst_addr[/dst_masklen]]
  755. #
  756. # Where src_addr and dst_addr are IP addresses in dotted decimal
  757. # notation or valid DNS names, and src_masklen and dst_masklen are
  758. # subnet masks in CIDR notation, i.e. integer values from 2 to 30
  759. # representing the length (in bits) of the network address. The
  760. # masks and the whole destination part are optional.
  761. #
  762. # Default value:
  763. #
  764. # Unset
  765. #
  766. # Effect if unset:
  767. #
  768. # Don't restrict access further than implied by listen-address
  769. #
  770. # Notes:
  771. #
  772. # Access controls are included at the request of ISPs and systems
  773. # administrators, and are not usually needed by individual
  774. # users. For a typical home user, it will normally suffice to
  775. # ensure that Privoxy only listens on the localhost (127.0.0.1)
  776. # or internal (home) network address by means of the listen-address
  777. # option.
  778. #
  779. # Please see the warnings in the FAQ that this proxy is not
  780. # intended to be a substitute for a firewall or to encourage
  781. # anyone to defer addressing basic security weaknesses.
  782. #
  783. # Multiple ACL lines are OK. If any ACLs are specified, then
  784. # the Privoxy talks only to IP addresses that match at least one
  785. # permit-access line and don't match any subsequent deny-access
  786. # line. In other words, the last match wins, with the default
  787. # being deny-access.
  788. #
  789. # If Privoxy is using a forwarder (see forward below) for a
  790. # particular destination URL, the dst_addr that is examined is
  791. # the address of the forwarder and NOT the address of the ultimate
  792. # target. This is necessary because it may be impossible for the
  793. # local Privoxy to determine the IP address of the ultimate target
  794. # (that's often what gateways are used for).
  795. #
  796. # You should prefer using IP addresses over DNS names, because
  797. # the address lookups take time. All DNS names must resolve! You
  798. # can not use domain patterns like "*.org" or partial domain
  799. # names. If a DNS name resolves to multiple IP addresses, only
  800. # the first one is used.
  801. #
  802. # Denying access to particular sites by ACL may have undesired
  803. # side effects if the site in question is hosted on a machine
  804. # which also hosts other sites.
  805. #
  806. # Examples:
  807. #
  808. # Explicitly define the default behavior if no ACL and
  809. # listen-address are set: "localhost" is OK. The absence of a
  810. # dst_addr implies that all destination addresses are OK:
  811. #
  812. # permit-access localhost
  813. #
  814. # Allow any host on the same class C subnet as www.privoxy.org
  815. # access to nothing but www.example.com:
  816. #
  817. # permit-access www.privoxy.org/24 www.example.com/32
  818. #
  819. # Allow access from any host on the 26-bit subnet 192.168.45.64
  820. # to anywhere, with the exception that 192.168.45.73 may not
  821. # access www.dirty-stuff.example.com:
  822. #
  823. # permit-access 192.168.45.64/26
  824. # deny-access 192.168.45.73 www.dirty-stuff.example.com
  825. #
  826. #
  827. # 4.6. buffer-limit
  828. # =================
  829. #
  830. # Specifies:
  831. #
  832. # Maximum size of the buffer for content filtering.
  833. #
  834. # Type of value:
  835. #
  836. # Size in Kbytes
  837. #
  838. # Default value:
  839. #
  840. # 4096
  841. #
  842. # Effect if unset:
  843. #
  844. # Use a 4MB (4096 KB) limit.
  845. #
  846. # Notes:
  847. #
  848. # For content filtering, i.e. the +filter and +deanimate-gif
  849. # actions, it is necessary that Privoxy buffers the entire document
  850. # body. This can be potentially dangerous, since a server could
  851. # just keep sending data indefinitely and wait for your RAM to
  852. # exhaust -- with nasty consequences. Hence this option.
  853. #
  854. # When a document buffer size reaches the buffer-limit, it is
  855. # flushed to the client unfiltered and no further attempt to filter
  856. # the rest of the document is made. Remember that there may be
  857. # multiple threads running, which might require up to buffer-limit
  858. # Kbytes each, unless you have enabled "single-threaded" above.
  859. #
  860. buffer-limit 4096
  861. #
  862. # 5. FORWARDING
  863. # =============
  864. #
  865. # This feature allows routing of HTTP requests through a chain
  866. # of multiple proxies. It can be used to better protect privacy
  867. # and confidentiality when accessing specific domains by routing
  868. # requests to those domains through an anonymous public proxy (see
  869. # e.g. http://www.multiproxy.org/anon_list.htm) Or to use a caching
  870. # proxy to speed up browsing. Or chaining to a parent proxy may be
  871. # necessary because the machine that Privoxy runs on has no direct
  872. # Internet access.
  873. #
  874. # Also specified here are SOCKS proxies. Privoxy supports the SOCKS
  875. # 4 and SOCKS 4A protocols.
  876. #
  877. #
  878. # 5.1. forward
  879. # ============
  880. #
  881. # Specifies:
  882. #
  883. # To which parent HTTP proxy specific requests should be routed.
  884. #
  885. # Type of value:
  886. #
  887. # target_pattern http_parent[:port]
  888. #
  889. # where target_pattern is a URL pattern that specifies to which
  890. # requests (i.e. URLs) this forward rule shall apply. Use /
  891. # to denote "all URLs". http_parent[:port] is the DNS name or
  892. # IP address of the parent HTTP proxy through which the requests
  893. # should be forwarded, optionally followed by its listening port
  894. # (default: 8080). Use a single dot (.) to denote "no forwarding".
  895. #
  896. # Default value:
  897. #
  898. # Unset
  899. #
  900. # Effect if unset:
  901. #
  902. # Don't use parent HTTP proxies.
  903. #
  904. # Notes:
  905. #
  906. # If http_parent is ".", then requests are not forwarded to
  907. # another HTTP proxy but are made directly to the web servers.
  908. #
  909. # Multiple lines are OK, they are checked in sequence, and the
  910. # last match wins.
  911. #
  912. # Examples:
  913. #
  914. # Everything goes to an example anonymizing proxy, except SSL on
  915. # port 443 (which it doesn't handle):
  916. #
  917. # forward / anon-proxy.example.org:8080
  918. # forward :443 .
  919. #
  920. # Everything goes to our example ISP's caching proxy, except for
  921. # requests to that ISP's sites:
  922. #
  923. # forward / caching-proxy.example-isp.net:8000
  924. # forward .example-isp.net .
  925. #
  926. #
  927. # 5.2. forward-socks4 and forward-socks4a
  928. # =======================================
  929. #
  930. # Specifies:
  931. #
  932. # Through which SOCKS proxy (and to which parent HTTP proxy)
  933. # specific requests should be routed.
  934. #
  935. # Type of value:
  936. #
  937. # target_pattern socks_proxy[:port] http_parent[:port]
  938. #
  939. # where target_pattern is a URL pattern that specifies to which
  940. # requests (i.e. URLs) this forward rule shall apply. Use / to
  941. # denote "all URLs". http_parent and socks_proxy are IP addresses
  942. # in dotted decimal notation or valid DNS names (http_parent may
  943. # be "." to denote "no HTTP forwarding"), and the optional port
  944. # parameters are TCP ports, i.e. integer values from 1 to 64535
  945. #
  946. # Default value:
  947. #
  948. # Unset
  949. #
  950. # Effect if unset:
  951. #
  952. # Don't use SOCKS proxies.
  953. #
  954. # Notes:
  955. #
  956. # Multiple lines are OK, they are checked in sequence, and the
  957. # last match wins.
  958. #
  959. # The difference between forward-socks4 and forward-socks4a
  960. # is that in the SOCKS 4A protocol, the DNS resolution of the
  961. # target hostname happens on the SOCKS server, while in SOCKS 4
  962. # it happens locally.
  963. #
  964. # If http_parent is ".", then requests are not forwarded to another
  965. # HTTP proxy but are made (HTTP-wise) directly to the web servers,
  966. # albeit through a SOCKS proxy.
  967. #
  968. # Examples:
  969. #
  970. # From the company example.com, direct connections are made to all
  971. # "internal" domains, but everything outbound goes through their
  972. # ISP's proxy by way of example.com's corporate SOCKS 4A gateway
  973. # to the Internet.
  974. #
  975. # forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
  976. # forward .example.com .
  977. #
  978. # A rule that uses a SOCKS 4 gateway for all destinations but no
  979. # HTTP parent looks like this:
  980. #
  981. # forward-socks4 / socks-gw.example.com:1080 .
  982. #
  983. forward-socks4a / localhost:9050 .
  984. #
  985. # 6. WINDOWS GUI OPTIONS
  986. # ======================
  987. #
  988. # Privoxy has a number of options specific to the Windows GUI
  989. # interface:
  990. #
  991. # If "activity-animation" is set to 1, the Privoxy icon will animate
  992. # when "Privoxy" is active. To turn off, set to 0.
  993. #
  994. #activity-animation 1
  995. # If "log-messages" is set to 1, Privoxy will log messages to the
  996. # console window:
  997. #
  998. #log-messages 1
  999. # If "log-buffer-size" is set to 1, the size of the log buffer,
  1000. # i.e. the amount of memory used for the log messages displayed in
  1001. # the console window, will be limited to "log-max-lines" (see below).
  1002. #
  1003. # Warning: Setting this to 0 will result in the buffer to grow
  1004. # infinitely and eat up all your memory!
  1005. #
  1006. #log-buffer-size 1
  1007. # log-max-lines is the maximum number of lines held in the log
  1008. # buffer. See above.
  1009. #
  1010. #log-max-lines 200
  1011. # If "log-highlight-messages" is set to 1, Privoxy will highlight
  1012. # portions of the log messages with a bold-faced font:
  1013. #
  1014. #log-highlight-messages 1
  1015. # The font used in the console window:
  1016. #
  1017. #log-font-name Comic Sans MS
  1018. # Font size used in the console window:
  1019. #
  1020. #log-font-size 8
  1021. # "show-on-task-bar" controls whether or not Privoxy will appear as
  1022. # a button on the Task bar when minimized:
  1023. #
  1024. #show-on-task-bar 0
  1025. # If "close-button-minimizes" is set to 1, the Windows close button
  1026. # will minimize Privoxy instead of closing the program (close with
  1027. # the exit option on the File menu).
  1028. #
  1029. #close-button-minimizes 1
  1030. # The "hide-console" option is specific to the MS-Win console version
  1031. # of Privoxy. If this option is used, Privoxy will disconnect from
  1032. # and hide the command console.
  1033. #
  1034. #hide-console
  1035. #