Option to choose the query parameter used for redirects

When executing a filter rule, in the case when a request URL has multiple query parameters that are valid URLs, RequestControl currently picks the first one as the URL to redirect to. I’d like to have a way to specify that a particular named parameter is the one to use.

For example, the outbound links on vulture.com articles (example), when clicked, take you through a go.redirectingat.com URL that includes an sref parameter which contains the URL of the article you’re coming from, as well as a url parameter that contains the URL I’d like to be able to redirect to. But since sref precedes url, a filter redirect would just dump me back to where I came from.

[tumpio]

These should work too:

1. Allow search parameters in redirect rule substitutions ({search.url} or some other syntax)
2. Trimming unwanted parameters before choosing a filter redirect

Improvements are always welcome! 😃

[rhendric]

It seems a shame to make people write a manual regex parser like {search/.*[?&]url=([^&]*).*/decodeURIComponent($1)} instead of {search.url}. The URL class already parses search parameters into a Map called searchParams; it would be easy for you to parse {search.whatever} into a redirect pattern that resolves requestURL.searchParams.get('whatever'). Why ask users to do that work with regexes?