X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=templates%2Fedit-actions-for-url;h=3c11ade8234a5ca83922f4669e14a10cf19c7ac0;hb=4e2c6db9354f8f98c67de8a5940c6e4a6bccbe46;hp=9d35a40da20bc5f875fae63d97dad8450201abed;hpb=f5baceb8341f2f78130f9f592358c40fb1d71697;p=privoxy.git diff --git a/templates/edit-actions-for-url b/templates/edit-actions-for-url index 9d35a40d..3c11ade8 100644 --- a/templates/edit-actions-for-url +++ b/templates/edit-actions-for-url @@ -6,7 +6,7 @@ # particular section in an actions file. # # -# Copyright : Written by and Copyright (C) 2001-2007 the SourceForge +# Copyright : Written by and Copyright (C) 2001-2008 the SourceForge # Privoxy team. http://www.privoxy.org/ # # Original Author: Copyright (C) 2001 Jonathan Foster @@ -32,6 +32,39 @@ # # Revisions : # $Log: edit-actions-for-url,v $ +# Revision 1.55 2008/09/19 15:26:29 fabiankeil +# Add change-x-forwarded-for{} action to block or add +# X-Forwarded-For headers. Mostly based on code removed +# before 3.0.7. +# +# Revision 1.54 2008/03/29 12:14:27 fabiankeil +# Remove send-wafer and send-vanilla-wafer actions. +# +# Revision 1.53 2008/03/28 15:13:45 fabiankeil +# Remove inspect-jpegs action. +# +# Revision 1.52 2008/03/15 14:52:36 fabiankeil +# Add CGI editor support for the "disable all filters of this type" +# directives "-client-header-filter", "-server-header-filter", +# "-client-header-tagger" and "-server-header-tagger". +# +# Revision 1.51 2008/03/07 16:46:49 fabiankeil +# Reword limit-connect{} entry. +# +# Revision 1.50 2008/03/04 18:30:44 fabiankeil +# Remove the treat-forbidden-connects-like-blocks action. We now +# use the "blocked" page for forbidden CONNECT requests by default. +# +# Revision 1.49 2008/03/01 14:00:47 fabiankeil +# Let the block action take the reason for the block +# as argument and show it on the "blocked" page. +# +# Revision 1.48 2007/12/11 21:18:55 fabiankeil +# Make forward-override accessible through the CGI editor. +# +# Revision 1.47 2007/12/06 18:21:55 fabiankeil +# Update hide-forwarded-for-headers description. +# # Revision 1.46 2007/11/10 15:06:10 fabiankeil # - Add support for +hide-referrer{conditional-forge}. # - Minor rewordings. @@ -419,18 +452,6 @@ function show_limit_connect_opts(tf) target.style.display = (tf ? "" : "none"); } -function show_send_wafer_opts(tf) -{ - if (document.getElementById) { - target = document.getElementById("send_wafer_opts"); - } else if (document.all) { - target = document.send_wafer_opts; - } else { - return; - } - target.style.display = (tf ? "" : "none"); -} - //--> @@ -529,10 +550,66 @@ function show_send_wafer_opts(tf) block Block the request. - + +   +   +   +   + Block reason to tell the user:
+ + + + + + + + change-x-forwarded-for + Specifies whether to block or add X-Forwarded-For headers. + + +   +   +   +   +
+
+ + +   + + + client-header-filter * + Filter the client headers. + You can use the radio buttons on this line to disable + all client-header filters applied by previous rules, and/or + you can enable or disable the filters individually below. + @client-header-filter-params@ + +   + + + client-header-tagger * + Create tags based on the client headers. + You can use the radio buttons on this line to disable + all client-header taggers applied by previous rules, and/or + you can enable or disable the taggers individually below. + @client-header-tagger-params@ - + + + + + forward-override + Override forward directives in the configuration file. + Note that the parameter syntax + isn't checked until the action is used. Syntax errors + will cause Privoxy to exit. + + +   +   +   +   + + Overriding forward directive:
+
+ +
- - - - - - hide-forwarded-for-headers - Remove any existing X-Forwarded-for header. - - - - - - inspect-jpegs - Checks jpeg images for malicious content. - - - - - - kill-popups - Filter the website through a built-in filter to disable many JavaScript - pop-up windows. Not recommended. - limit-connect - Specify which ports are allowed for SSL (HTTP CONNECT) access. - Note that this allows arbitrary tunnelling. + Limit which ports are allowed in HTTP CONNECT requests. These requests are + used to tunnel SSL and other protocols through HTTP proxies.         - Legal SSL ports (comma separated, ranges allowed):
+ Legal ports (comma separated, ranges allowed):
@@ -1184,44 +1248,31 @@ function show_send_wafer_opts(tf) - +   + name="server_header_filter_all" id="server_header_filter_all_n" value="N" @server-header-filter-all-n@ > - send-vanilla-wafer - Adds a special wafer (standard cookie) to all your requests. Not recommended. + name="server_header_filter_all" id="server_header_filter_all_x" value="X" @server-header-filter-all-x@ > + server-header-filter * + Filter the server headers. + You can use the radio buttons on this line to disable + all server-header filters applied by previous rules, and/or + you can enable or disable the filters individually below. +@server-header-filter-params@ - +   + name="server_header_tagger_all" id="server_header_tagger_all_n" value="N" @server-header-tagger-all-n@ > - send-wafer - Adds user-specified cookies. - - -   -   -   -   - Editing the settings for this option, or turning - it on if it was off, is not yet supported using this web-based - editor. + name="server_header_tagger_all" id="server_header_tagger_all_x" value="X" @server-header-tagger-all-x@ > + server-header-tagger * + Create tags based on the server headers. + You can use the radio buttons on this line to disable + all server-header taggers applied by previous rules, and/or + you can enable or disable the taggers individually below. - -@server-header-filter-params@ @server-header-tagger-params@ - - - - - - treat-forbidden-connects-like-blocks - - Answer forbidden Connect requests with the usual block message. - Makes unblocking easier, but the go there anyway link will not work - as expected. - -