Post Reply 
Your browser is no longer supported.
Jan. 14, 2015, 04:53 AM (This post was last modified: Jan. 14, 2015 04:55 AM by JJoe.)
Post: #14
RE: Your browser is no longer supported.
(Jan. 14, 2015 03:05 AM)zoltan Wrote:  Does the "." only apply when there's a www in the URL?

"[^/]+" says blindly match anything that is not a / OR nothing.
In "[^/]++what follows"
"[^/]++" says only match anything that is not a / OR nothing if it precedes "what follows".
So the "." could only be used if "what follows" starts with a ".".

(www.|)somehost.com/ would match
www.somehost.com/
and
somehost.com/
([^/]++.|)somehost.com/ would match those and more.

Remember that https sites may actually be seen as "https://example.com:443/".

(Jan. 14, 2015 03:05 AM)zoltan Wrote:  What if I wanted the exception to apply to all sites, would it be
[^/]++ $SET(0=....etc
or just
$SET(0=....etc (without a url at the beginning)

If it were the only list entry, either would work. $SET(0=....etc is quicker.

Because of the way the lists and cfg work, I use something like

Code:
$SET(keyword=$GET(keyword)f_ua_Ā§Mozilla/5%2e0 (Windows; U; Windows NT 6%2e1; en-US; rv:36%2e0) Gecko/20100101 Firefox/36%2e0.)(^)
~$SET(keyword=$GET(keyword)f_ua_Ā§Mozilla/5%2e0 (Windows; U; Windows NT 6%2e1; en-US; rv:36%2e0) Gecko/20100101 Firefox/36%2e0.)(^)

for all sites.

$SET is executed when found. (^) never matches. So
these two entries should cause the f_ua string to always be added to the keyword variable while allowing other entries to add to the variable.

"~" is the "turtle excluder device". You can read about it in Proxomitron's help under Creating blocklists>>Unmatching a match.

You could also use a header filter.

HTH
Add Thank You Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Your browser is no longer supported. - JJoe - Jan. 14, 2015 04:53 AM

Forum Jump: