Code: Select all
Site */omniture/s_code.js
Accept from *.fnfg.com fnfg.com
Deny
Site */s_code.js
Deny
Code: Select all
https://myservices.timewarnercable.com/js/omniture/s_code.js
Code: Select all
Site */js/omniture/s_code.js
Accept from *.fnfg.com fnfg.com
Deny
Site */omniture/s_code.js
Accept from *.fnfg.com fnfg.com
Deny
Site */s_code.js
Deny
Code: Select all
[ABE] <*/js/omniture/s_code.js> Deny on {GET https://myservices.timewarnercable.com/js/omniture/s_code.js <<< https://myservices.timewarnercable.com/, https://myservices.timewarnercable.com/ - 2}
USER rule:
Site */js/omniture/s_code.js
Deny
Was I incorrect in my understanding of the leading "*/" in the ruleset ? I had understood that "*/s_code.js" would block any URL not specifically allowed, using right-to-left priorities ("s_code.js" would be blocked regardless of the depth of sub-directory nesting. Should that not be the case, my ABE ruleset would need to be updated for the various forms of this code used in different sites.