-
- <p>Sometimes, there are even multiple consecutive redirects
- encoded in the URL. These redirections via scripts make your
- web browsing more traceable, since the server from which you
- follow such a link can see where you go to. Apart from that,
- valuable bandwidth and time is wasted, while your browser asks
- the server for one redirect after the other. Plus, it feeds the
- advertisers.</p>
-
- <p>This feature is currently not very smart and is scheduled
- for improvement. If it is enabled by default, you will have to
- create some exceptions to this action. It can lead to failures
- in several ways:</p>
-
- <p>Not every URLs with other URLs as parameters is evil. Some
- sites offer a real service that requires this information to
- work. For example a validation service needs to know, which
- document to validate. <tt class="LITERAL">fast-redirects</tt>
- assumes that every URL parameter that looks like another URL is
- a redirection target, and will always redirect to the last one.
- Most of the time the assumption is correct, but if it isn't,
- the user gets redirected anyway.</p>
-
- <p>Another failure occurs if the URL contains other parameters
- after the URL parameter. The URL: <span class=
- "QUOTE">"http://www.example.org/?redirect=http%3a//www.example.net/&foo=bar"</span>.
- contains the redirection URL <span class=
- "QUOTE">"http://www.example.net/"</span>, followed by another
- parameter. <tt class="LITERAL">fast-redirects</tt> doesn't know
- that and will cause a redirect to <span class=
- "QUOTE">"http://www.example.net/&foo=bar"</span>. Depending
- on the target server configuration, the parameter will be
- silently ignored or lead to a <span class="QUOTE">"page not
- found"</span> error. You can prevent this problem by first
- using the <tt class="LITERAL"><a href=
- "actions-file.html#REDIRECT">redirect</a></tt> action to remove
- the last part of the URL, but it requires a little effort.</p>
-
- <p>To detect a redirection URL, <tt class=
- "LITERAL">fast-redirects</tt> only looks for the string
- <span class="QUOTE">"http://"</span>, either in plain text
- (invalid but often used) or encoded as <span class=
- "QUOTE">"http%3a//"</span>. Some sites use their own URL
- encoding scheme, encrypt the address of the target server or
- replace it with a database id. In theses cases <tt class=
- "LITERAL">fast-redirects</tt> is fooled and the request reaches
- the redirection server where it probably gets logged.</p>
+ <p>Sometimes, there are even multiple consecutive redirects encoded in the URL. These redirections via
+ scripts make your web browsing more traceable, since the server from which you follow such a link can see
+ where you go to. Apart from that, valuable bandwidth and time is wasted, while your browser asks the
+ server for one redirect after the other. Plus, it feeds the advertisers.</p>
+ <p>This feature is currently not very smart and is scheduled for improvement. If it is enabled by
+ default, you will have to create some exceptions to this action. It can lead to failures in several
+ ways:</p>
+ <p>Not every URLs with other URLs as parameters is evil. Some sites offer a real service that requires
+ this information to work. For example a validation service needs to know, which document to validate.
+ <tt class="LITERAL">fast-redirects</tt> assumes that every URL parameter that looks like another URL is a
+ redirection target, and will always redirect to the last one. Most of the time the assumption is correct,
+ but if it isn't, the user gets redirected anyway.</p>
+ <p>Another failure occurs if the URL contains other parameters after the URL parameter. The URL:
+ <span class="QUOTE">"http://www.example.org/?redirect=http%3a//www.example.net/&foo=bar"</span>.
+ contains the redirection URL <span class="QUOTE">"http://www.example.net/"</span>, followed by another
+ parameter. <tt class="LITERAL">fast-redirects</tt> doesn't know that and will cause a redirect to
+ <span class="QUOTE">"http://www.example.net/&foo=bar"</span>. Depending on the target server
+ configuration, the parameter will be silently ignored or lead to a <span class="QUOTE">"page not
+ found"</span> error. You can prevent this problem by first using the <tt class="LITERAL"><a href=
+ "actions-file.html#REDIRECT">redirect</a></tt> action to remove the last part of the URL, but it requires
+ a little effort.</p>
+ <p>To detect a redirection URL, <tt class="LITERAL">fast-redirects</tt> only looks for the string
+ <span class="QUOTE">"http://"</span>, either in plain text (invalid but often used) or encoded as
+ <span class="QUOTE">"http%3a//"</span>. Some sites use their own URL encoding scheme, encrypt the address
+ of the target server or replace it with a database id. In theses cases <tt class=
+ "LITERAL">fast-redirects</tt> is fooled and the request reaches the redirection server where it probably
+ gets logged.</p>