X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=844df3a3754b3396083477110834fe6ff828a180;hp=64c5b9b372ef34a405710643429a66aa64338c4b;hb=2a175c54f8556e7408c19fb215560a99de99e54f;hpb=01ef40fc50001c99d8a4457bf6501c72e22e43fc diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index 64c5b9b3..844df3a3 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -156,7 +156,7 @@ CLASS="FILENAME" >

8.1. Finding the Right Mix

8.2. How to Edit

8.4.1. The Domain Pattern

8.4.2. The Path Pattern

filter-server-headers @@ -1835,7 +1835,7 @@ CLASS="SECT3" >8.5.4. crunch-server-header8.5.4. crunch-client-header

filter-client-headers @@ -2280,7 +2280,7 @@ CLASS="LITERAL" filter-server-headers @@ -2746,7 +2746,7 @@ CLASS="QUOTE" requests with filter-client-headers @@ -2842,7 +2842,8 @@ CLASS="VARIABLELIST" CLASS="LITERAL" >text/plain MIME type for all files whose type they - don't know.) + don't know.) By default, filtering works only on the document content + itself, not the headers.

8.5.13. filter-client-headers

Typical use:

To apply filtering to the client's (browser's) headers +

Effect:

Extend filtering capabilities to the client's headers, which + by default applies only to the document itself. +

Type:

Boolean.

Parameter:

N/A +

Notes:

Regular expressions can be used to filter headers as well. Check your + filters closely before activating this action, as it can easily lead to broken + requests. +

+ These filters are applied to each header on its own, not to them + all at once. This makes it easier to diagnose problems, but on the downside + you can't write filters that only change header x if header y's value is + z. +

The filters are used after the other header actions have finished and can + use their output as input. +

Whenever possible one should specify ^, + $, the whole header name and the colon, to make sure + the filter doesn't cause havoc to other headers or the + page itself. For example if you want to transform + Galeon User-Agents to + Firefox User-Agents you + shouldn't use:

s@Galeon/\d\.\d\.\d @@

but:

s@^(User-Agent:.*) Galeon/\d\.\d\.\d (Firefox/\d\.\d\.\d\.\d)$@$1 $2@

Example usage (section):

{+filter-client-headers +filter{test_filter}}
+problem-host.example.com
+
+

8.5.14. filter-server-headers

Typical use:

To apply filtering to the server's headers +

Effect:

Extend filtering capabilities to the server's headers, which + by default applies only to the document itself. +

Type:

Boolean.

Parameter:

N/A +

Notes:

Similar to filter-client-headers, but works on + the server instead. To filter both server and client, use both. +

As with filter-client-headers, check your + filters before activating this action, as it can easily lead to broken + requests. +

+ These filters are applied to each header on its own, not to them + all at once. This makes it easier to diagnose problems, but on the downside + you can't write filters that only change header x if header y's value is + z. +

The filters are used after the other header actions have finished and can + use their output as input. +

Remember too, whenever possible one should specify ^, + $, the whole header name and the colon, to make sure + the filter doesn't cause havoc to other headers or the + page itself. See above for example. +

Example usage (section):

{+filter-server-headers +filter{test_filter}}
+problem-host.example.com
+
+

8.5.13. force-text-mode

8.5.15. force-text-mode

8.5.14. handle-as-empty-document8.5.16. handle-as-empty-document

8.5.15. handle-as-image8.5.17. handle-as-image

8.5.16. hide-accept-language8.5.18. hide-accept-language

8.5.17. hide-content-disposition8.5.19. hide-content-disposition

8.5.18. hide-if-modified-since8.5.20. hide-if-modified-since

8.5.19. hide-forwarded-for-headers8.5.21. hide-forwarded-for-headers

8.5.20. hide-from-header8.5.22. hide-from-header

8.5.21. hide-referrer8.5.23. hide-referrer8.5.22. hide-user-agent8.5.24. hide-user-agent

8.5.23. inspect-jpegs8.5.25. inspect-jpegs

8.5.24. kill-popups8.5.26. kill-popups8.5.25. limit-connect8.5.27. limit-connect

8.5.26. prevent-compression8.5.28. prevent-compression

8.5.27. overwrite-last-modified8.5.29. overwrite-last-modified

8.5.28. redirect8.5.30. redirect

8.5.29. send-vanilla-wafer8.5.31. send-vanilla-wafer

8.5.30. send-wafer8.5.32. send-wafer

8.5.31. session-cookies-only8.5.33. session-cookies-only

8.5.32. set-image-blocker8.5.34. set-image-blocker

8.5.33. treat-forbidden-connects-like-blocks8.5.35. treat-forbidden-connects-like-blocks

8.5.34. Summary

8.5.36. Summary

Note that many of these actions have the potential to cause a page to misbehave, possibly even not to display at all. There are many ways @@ -6402,7 +6645,7 @@ CLASS="SECT3" >

8.7.1. default.action

8.7.2. user.action