From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530 BuildID: 2002053012 Accessing a so-called banned port results in a pop up box which states a security violation has occurred. This makes no sense at all for ports banned on systems which dont run those services. Why is the X server port banned by default for windows IIS systems not running X at all ? Please alter it so that one preference and a simple check box in the security settings can disable this banned port "security feature" permanently or disable it by default. It causes great inconvenience to those of us deploying mozilla on embedded systems which *have* to make use of "banned" ports for various reasons. A 50-60 port listing when setting pref("network.security.ports.banned.overide",port1,port2...port50); is NOT a good solution. Reproducible: Always Steps to Reproduce: 1. access the link. 2. 3. Actual Results: security block pops up a warning. this adds extra headaches when deploying mozilla on embedded systems. Expected Results: have a checkbox to disable it or disable it by default.

this is NEVER a blocker ! *** This bug has been marked as a duplicate of 85601 ***

v.

->security

I filed bug 240116 for you about supporting port ranges.