Need to disable 'Access to the port number given has been disabled' "feature"

VERIFIED INVALID

Status

()

Core
Networking: HTTP
VERIFIED INVALID
15 years ago
14 years ago

People

(Reporter: Wolf, Assigned: Darin Fisher)

Tracking

Trunk
Sun
SunOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.2b) Gecko/20021024
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.2b) Gecko/20021024

When trying to access a number of internal web sites, I get a Mozilla popup
stating "Access to the port number given has been disabled for security reasons"
(it is port 1080).

I can't find anywhere to disable this, but obviouslly I need to in order to be
able to continue working.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

15 years ago
It's in the release notes (http://www.mozilla.org/releases/mozilla1.2b/) how to
do that:

"For security reasons, Mozilla does not allow connections to certain ports. To
override this on a per-port basis, add a comma separated list of ports to
defaults/all.js (in your Mozilla installation directory). Note that this pref
only works in the all.js file in the Mozilla installation directory and it
affects all users of the installation. It does not work if you add it to the
prefs.js or user.js files in your personal profile directory. For example, to
unblock ports 1, 3, and 7, use the following line:

pref("network.security.ports.banned.override", "1,3,7");"
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
v - please don't ask those questions in bugzilla since this is a bug database
and no support database.

You must do this before you file a bug :
a) read the release notes
b) query for existing bugs 

You would find the solution with a + b (search with 1080 in the summary)
Status: RESOLVED → VERIFIED

Comment 3

15 years ago
See http://www.mozilla.org/projects/netlib/PortBanning.html for more explanation
why this was done.

Comment 4

14 years ago
*** Bug 241415 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.