Port 87

Discussion of general topics about Mozilla Firefox
Post Reply
csogilvie
Posts: 89
Joined: November 20th, 2002, 6:35 am
Location: Stirling, Scotland, UK
Contact:

Port 87

Post by csogilvie »

I think this is also in Mozilla as well, but is there any particular reason why I can not make HTTP connections to port 87 (eg. http://omega:87)? Is it possible to disable the error popup and just connect regardless?
Colin S. Ogilvie
Balboa
Posts: 35
Joined: November 5th, 2002, 2:04 am

Post by Balboa »

Apparently it's a 'well-known port', used for private terminal links. Not sure why it was blocked though.
http://www.iana.org/assignments/port-numbers
User avatar
alanjstr
Moderator
Posts: 9100
Joined: November 5th, 2002, 4:43 pm
Location: Anywhere but here
Contact:

Re: Port 87

Post by alanjstr »

csogilvie wrote:I think this is also in Mozilla as well, but is there any particular reason why I can not make HTTP connections to port 87 (eg. http://omega:87)? Is it possible to disable the error popup and just connect regardless?


There is a way to override this by putting a line in user.js. Someone else will have to point you to the correct setting.
User avatar
laszlo
Posts: 5225
Joined: November 4th, 2002, 6:13 pm
Location: .de
Contact:

Re: Port 87

Post by laszlo »

alanjstr wrote:
csogilvie wrote:I think this is also in Mozilla as well, but is there any particular reason why I can not make HTTP connections to port 87 (eg. http://omega:87)? Is it possible to disable the error popup and just connect regardless?


There is a way to override this by putting a line in user.js. Someone else will have to point you to the correct setting.

Try this:

user_pref("network.security.ports.banned.override", "87");

No guaranty that it works though. The list of ports is comma-separated, if you want to add more than one.
Post Reply