Hi,
>> >>> I found a local version which maybe did the trick
>> >>>
>> >>> redirector_pattern
>> >>>
>> >>> m'^https?:/*(?:\w+\.)?google(?:\.\w{2,3}){1,2}/url\?.*?(?<=[?&])q=(.*?)(?:$|[&\#])'i
>> >>
>
>> Yes, but I don't understand how that equates to an eventual score.
>
> I haven't used these, but by the look of it it's trying to identify
> the encoded URI so that other rules can see it.
>
>> Perhaps I don't understand regex's well enough, but I don't understand
>> what it does with the redirector site portion and the target portion.
>
> In rules you often see ?: used in brackets to prevent the matching
> text being captured as this makes it more efficient, e.g. (?:\w+\.)
> in the above. Towards the end of the pattern is (.*?) which is
> used to capture the target uri.
>
> .*? is like .*, but matches the shortest run of characters it can,
> rather than the longest.
Am I understanding correctly that redirector_pattern breaks up the one
encoded URI into multiple URIs that are available for rules to be
written using them, instead of ?
In other words, if I were to write a uri rule that includes
www.googleapis.com, it would match in this case? How does it differ
had I not had a redirector pattern and just wrote a rule matching the
pattern directly?
May 5 21:32:22.768 [5533] dbg: uri: parsed uri found:
https://www.googleapis.com/auth/contacts&immediate=false&include_granted_scopes=true&response_type=token&redirect_uri=https://googledocs.g-docs.pro/g.php&customparam=customparam
in hard-coded redirector
Initially I thought it was hitting the redirector_pattern supplied by
Axb a few days ago, but it looks like it matches one of the patterns
included in 72_scores.cf already.
