Generic method for adding multiple filtering commands on same url?

[leecovuk]

Hello,

First, am I correct in understanding that a url can only appear once as a matching url in either Bypass List.txt or IncludeExclude-U.ptxt?
I've believed that for years from reading bits and pieces.

If so, is there a generic method or syntax that can be used, to apply multiple filters/commands to one matching url?
eg, can something like
*sitename.com*
be followed by multiple filtering commands all in one line?
If so, does this however depend on which filtering commands are involved, rather than there being a generic syntax for use with any combination of filters?

(I'm not talking here about making separate entries to get around multiple url matching issues, which is essentially what I'm trying to avoid. This is because my grasp of making a manual exception entry is pretty much limited to use of the * for the matching partial url, then copy/pasting after it what seems to be an appropriate filtering command from IncludeExclude-U)

Thanks very much,
Lee

[ProxRocks]

i'm not sure if i follow your question...

we already can match one url but have that one match bypass any number of filters by use of "keywords" that are $SET...

[leecovuk]

Hello ProxRocks and thanks for replying.

Well, to conjure up an example, let's imagine we have the site domain:
sitename.com
and I want to make several filter exceptions on that one domain, presumably by making an entry/entries in IncludeExclude-U.ptxt

Now, I've certainly seen and read Sidki's advice on (I'm paraphrasing:) 'matching a url more than once' at the top of that file, but my question is, can you somehow get them all on one line? ie just using one entry in IncludeExclude-U.ptxt
?
I assume not, hence Sidki's advice there at the top of the file, but I'd like to check to be sure there isn't a way.

If you indeed do need to make individual entries for each required exception, I assume I then need to learn the ways to vary a url expression, in order to be able to essentially repeat it but make it so it doesn't match twice in the file.
Do you see what I mean?
In which case, can you or somebody else kindly tell me/us a few ways to vary a url so that it doesn't 'match' more than once in the file, but does 'match' the same url thereby allowing multiple exceptions? I think this would involve use of things such as
^
as well as my favourite
*

I've read Scott's help files on this many times as well as other bits and pieces, but generally I just end up confused and none the wiser when it comes to applying it.

I hope the above made sense; I tried hard to explain as clearly as I can.

Thanks again,
Lee

[JJoe]

Proxo only looks for one match. Odds are that Proxo will find the same match every time. Other matches won't be used.

As for Sidki's set,
there are some working examples in $LST(IncludeExclude).

HTH

[lnminente]

I think is like this... but have in mind i don't have experience with it.

Well if you want to match one a few times, you should rewrite the matching lines abobe the last matching one, to get false while the $SET function is set in the truth/parsed part of the code.
Example to see it better:

prxbx.com $SET(some=some)prxfail$TST()
prxbx.com $TST(...)$SET(...)prxfail$TST()
prxbx.com $TST(...)$SET(...)prxfail$TST()
...
prxbx.com $TST(...)$SET(same=same)

but this could be confusing, so better use one line in that way:
prxbx.com ($TST(...)$URL()$SET(some=some)prxfail$TST()|...|...|$SET(same=same))

I'm creating a list similar to inc-exc for the base config right now, but it will be based on the uDom (not the url) to see easier what keywords are applied in the same uDom to join them easily. Sometimes it will require some extra code like $URL() but i think it worth it. This is the moment for any suggestions 'cause i am at the beginning of its development

edited at 14:55 UMT

[sidki3003]

I think Lee is asking about applying multiple exceptions (usually filter bypasses) to the very same URL (what you see in your browser's address bar).

For Scott's general bypass list, "Bypass List.txt", the question doesn't apply, because for each entry Proxomitron is completely turned off, so all filters are bypassed.


For the IncludeExclude list you can simply concatenate the exceptions you like to apply, each exception keyword followed by a dot.

Say you want to allow all popups on http://www.dummysoftware.com/popupdummy_testpage.html : Keyword -> i_popup_b:0
But you also want to allow Flash there (no toggle): Keyword -> a_flash

So you would add this entry to your IncludeExclude-U list:

Code:

www.dummysoftware.com/popupdummy_testpage.html    $SET(0=i_popup_b:0.a_flash.)

If you want to have these exceptions applied to the entire site, you would add www.dummysoftware.com/ instead.
And for the whole domain: ([^/]++.|)dummysoftware.com/

As JJoe indicated, if you're unsure about how to add a certain combination of exception keywords (or a certain URL expression) to your user list, you'll most probably find an example in the general IncludeExclude list, "IncludeExclude.ptxt".

[leecovuk]

Thanks all and yes Sidki, you hit the nail on the head. I should be able to apply that.

Thanks also for your further reply on the other topic.

Whilst I'm here;
I know IncludeExclude-U has many examples and keywords, but sometimes I feel I need to 'reverse' one. By that I mean, the given keyword may be to 'allow' something but I need in fact to 'block' it.
Is there a generic syntax for changing a keyword in this way?
I have dabbled and guessed a little by using either
a
in place of
b
or vice versa
but it _appears_ to be more subtle/complex than that.

As an aside, I do feel my occasional queries may annoy you all a little as I never seem to make any significant progress in grasping Prox and the Sidki config. I apologise for that but am grateful for the help regardless.
I am not a 'stupid' person generally, although certainly not much more than a mere user, but even though I have now been using Prox for several years, its workings and logic usually continue to escape my grasp when it comes to manually tweaking it.

Again, thanks for the help and advice.

Lee

[sidki3003]

(Apr. 28, 2009 06:32 PM)leecovuk Wrote:  Is there a generic syntax for changing a keyword in this way?
I have dabbled and guessed a little by using either
a
in place of
b
or vice versa
but it _appears_ to be more subtle/complex than that.

Quote:As an aside, I do feel my occasional queries may annoy you all a little as I never seem to make any significant progress in grasping Prox and the Sidki config.

Regarding sidki configs, i think it's more that you wouldn't have to ask many basic questions, if you would read the documents in the sidki-etc folder on your local hard drive.

For instance, regarding your previous question:
- You would learn about the syntax of allow/block pairs in sidki-etc\Abbreviations.txt (2nd chapter, "Keyword Prefixes").
- You would check for the existence of a block keyword in sidki-etc\IncludeExclude.html (3rd section, "INCLUDE (BLOCK, FAKE, SITE-SPECIFIC)").

[leecovuk]

Thanks Sidki,

I have _looked_ at all the docs and files many times, but maybe I haven't really _read_ them. I will look again and try to read, understand and absorb.

Lee