#576 Last redirect blocks preceding redirects


If URL matches the pattern of more than one redirect action only the last one is ever tried, others are ignored i.e. if the following actions are defined in this particular order:



and we are opening example.com/something it is not redirected and all we get in the log is

Redirect: pcrs command "s!anything!anything-at-all" didn't change http://example.com/something

The only way I found to make the first action work is to remove the second one.


  • Fabian Keil

    Fabian Keil - 2014-07-14

    Your examples consistently lack trailing exclamation marks,
    possibly SF's broken bug tracker ate them.

    Anyway, +redirect{} is a "parameterized action" and thus
    expected and documented to behave like this:
    | Note that if the URL matches multiple positive forms of a
    | parameterized action, the last match wins, i.e. the params
    | from earlier matches are simply ignored.

    This is probably mainly for historical reasons, once upon a
    time the action didn't support pcrs commands and thus allowing
    to apply it more than once didn't make sense.

    Are you positive you need more than one pcrs command?
    It's not clear from your example problem which can be
    solved by using a path pattern. As a bonus Privoxy
    would only execute the pcrs command when a redirect
    is wanted.

  • lvm_

    lvm_ - 2014-07-16
    Post awaiting moderation.
  • lvm_

    lvm_ - 2014-10-20

    another way of looking at this issue, consider the following url:


    I want to redirect it to


    i.e. I have to replace two portions of URL and leave the part between them intact. If sequential redirects were allowed it would've been very easy but with this limitation...


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks