InformAction Forums

All the rules involving poking holes into LOCAL must be placed in the SYSTEM section and also BEFORE the existing global rule. Since the rules are enforced in the order they are seen, saying don't allow anyone will override your exception allow pretty girls :) So you want to put allow pretty girls exemption first and THEN don't let anyone else in.

[quote="barbaz"]try inserting on the very beginning of SYSTEM (above the default rule)
[code]# samsung link exception
Site http://127.0.0.1:16716/
Accept GET from link.samsung.com
[/code][/quote]

Thank you barbaz. Putting it in SYSTEM rather than USER works. :)

# samsung link exception
Site http://127.0.0.1:16716/
Accept GET from link.samsung.com

try inserting on the very beginning of SYSTEM (above the default rule)
[code]# samsung link exception
Site http://127.0.0.1:16716/
Accept GET from link.samsung.com
[/code]

Trying to open link.samsung.com I get the following noscript message:

Request {GET http://127.0.0.1:16716/cross/cors/index ... _e=http%3A%F%2Flink.samsung.com&xdm_c=default[b]6198[/b]&xdm_p=1 <<<http://link.samsung.com/ - 7} filtered by ABE: <LOCAL> Deny

The number [b]6198[/b] seems to change every time, to four different numbers whenever I try to re-open link.samsung.com

I experimented with ABE USER rules and rules like the following do not work. Can anyone help with a valid rule or should I simply disable noscript temporarily?

# User-defined rules. Feel free to experiment here.
#Samsung Link rules
Site 127.0.0.1:16716
Accept from http://link.samsung.com
Deny

OR

#Samsung Link rules
Site LOCAL
Accept from LOCAL
Accept GET from link.samsung.com
Deny

OR

#Samsung Link rules
Site 127.0.0.1:16716
Accept GET from http://link.samsung.com
Deny