InformAction Forums

1,2,3, Many post all anti spam. try again
new install no script. TwoFiveThree

js web server on my computer mud
white list mud
run http://mud/about
err - 6
Abe LOCAL Deny

Now I have
SiteLocal
Accept from local
Site mud
accept from mud
deny

works. Correct?

No, if mud is local, then:

Site Local Mud
Accept from local mud
deny

if that doesn't work, try:

site local http://mud/
accept from local http://mud/
deny

Thank you, GµårÐïåñ, for your reply,

The first works.

However, I still have, prior to it:
Site LOCAL
Accept from LOCAL
deny
---

I'm not sure of the magic here. Design decision, no doubt.
Additionally, does this mean that when I am testing from a different port (and I will) I need an addition for each port along the following lines?
Site LOCAL mud:81
Accept from LOCAL mud:81
deny

Thank you again for your time.

You are welcome. Yes, the LOCAL is design interpretation that contains a HUGE category of what is considered local. When you start adding domain names, which like it or not mud is in this case, the lines blur on what is local LOCAL and what is local but not necessary LOCAL as its probably for development or intranet.

So yes, the need to keep LOCAL in there is a design necessity. Now yes, if you have various ports, you will add them with :# but not for the usual stuff like web which is interpreted as 80 and is not necessary to indicate but any none standard port like 88, 8080, etc, will need those ports added yes, although you can use an alternative that will loosen that restriction but I would advise against it from a security perspective but still effective.

If you haven't already, give this document a quick read, it might help with understanding a few things regarding the rules: ABE Rules Specifications