What exactly is an “actions” file?
798 799 Privoxy utilizes the concept of ” actions” that are used to manipulate and 800 control web page data. Actions files are where these actions that Privoxy 801 could take while processing a certain request, are configured. Typically, 802 you would define a set of default actions that apply globally to all URLs, 803 then add exceptions to these defaults where needed. There is a wide array 804 of actions available that give the user a high degree of control and 805 flexibility on how to process each and every web page. 806 807 Actions can be defined on a URL pattern basis, i.e. for single URLs, whole 808 web sites, groups or parts thereof etc. Actions can also be grouped 809 together and then applied to requests matching one or more patterns. There 810 are many possible actions that might apply to any given site. As an 811 example, if you are blocking cookies as one of your default actions, but 812 need to accept cookies from a given site, you would need to define an 813 exception f
• 3.2. The “actions” concept confuses me. Please list some of these “actions”. • 3.3. How are actions files configured? What is the easiest way to do this? • 3.4. There are several different “actions” files. What are the differences? • 3.5. Where can I get updated Actions Files? • 3.6. Can I use my old config files? • 3.7. Why is the configuration so complicated? • 3.8. How can I make my Yahoo/Hotmail/Gmail account work? • 3.9. What’s the difference between the “Cautious”, “Medium” and “Advanced” defaults? • 3.10. Why can I change the configuration with a browser? Does that not raise security issues? • 3.11. What is the default.filter file? What is a “filter”? • 3.12. How can I set up Privoxy to act as a proxy for my LAN? • 3.13. Instead of ads, now I get a checkerboard pattern. I don’t want to see anything. • 3.14. Why would anybody want to see a checkerboard pattern? • 3.15. I see some images being replaced by a text instead of the checkerboard image. Why and how do I get rid of this
Privoxy utilizes the concept of ” actions” that are used to manipulate and control web page data. Actions files are where these actions that Privoxy could take while processing a certain request, are configured. Typically, you would define a set of default actions that apply globally to all URLs, then add exceptions to these defaults where needed. There is a wide array of actions available that give the user a high degree of control and flexibility on how to process each and every web page. Actions can be defined on a URL pattern basis, i.e. for single URLs, whole web sites, groups or parts thereof etc. Actions can also be grouped together and then applied to requests matching one or more patterns. There are many possible actions that might apply to any given site. As an example, if you are blocking cookies as one of your default actions, but need to accept cookies from a given site, you would need to define an exception for this site in one of your actions files, preferably in user.
