|
Proper order for URL Match parameters
|
|
Jan. 19, 2013, 12:37 AM
Post: #3
|
|||
|
|||
|
RE: Proper order for URL Match parameters
Thanks. I tried it with the $TYPE restriction before and after the URL and it seems to work both ways as long as it's enclosed in ().
So am I to conclude that order doesn't matter? I wonder about the URL rules also because I'm running into similar issues with another filter. Code: Name = "font family new 1"When the above filter is applied to this css: http://graphics8.nytimes.com/css/0.1/scr.../forms.css it's triggered no matter whether the () encloses the $TYPE restrictions or not. But if I add ^www.cnn.com to the end of it, the filter no longer works when the $TYPEs are enclosed with (). I don't see why asking it not to filter a certain site would disable it on others. |
|||
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Proper order for URL Match parameters - zoltan - Jan. 17, 2013, 08:21 PM
RE: Proper order for URL Match parameters - whenever - Jan. 18, 2013, 03:12 AM
RE: Proper order for URL Match parameters - zoltan - Jan. 19, 2013 12:37 AM
RE: Proper order for URL Match parameters - JJoe - Jan. 19, 2013, 05:44 PM
RE: Proper order for URL Match parameters - zoltan - Jan. 20, 2013, 01:55 AM
|

Search
Member List
Calendar
Help





![[-]](images/ONi/collapse.gif)