NetManiac

Witold Rugowski on web20 wave with Ruby on Rails

Firefox 2.0 and non standard ports

Posted on December 15, 2006 - Filed Under Other, Tech

Today I was very surprised (unpleasantly) with FireFox 2.0 behavior. I would not expect, that I would have to use IE because of some stupid FireFox limitation. Try to go to this link http://nhw.pl:95/wp/ (there is no service on this port). But that was normally domain for IE, which try to know better than user what is good for him.

This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.

Very annoying. And especially this Try Again button ;-)) well URL won’t change with another click.

I say that worst is there is no workaround (at least known for me, but I did not Google a long time, and no network.security.ports.banned.override does not work in FF 2.0).

Popularity: 4% [?]

Hits for this post: 4875

Similar Posts

Comments

4 Responses to “Firefox 2.0 and non standard ports”

  1. Tomek's DS World on December 16th, 2006 22:56

    links from Technoratican have it also for Firefox users. This is important as key success for wide adoption will be possibility to use it on multiple platforms and clients. This plugin is step in good direction. If we are talking about Firefox – my friend Witek Rugowski posted on his blog about annoyance in Firefox. This browser won’t allow connection to sites on non-standard port if this port is one of well known services ports. No workaround at this moment.[IMG]

  2. W2K.PL on December 16th, 2006 22:05

    links from Technoratiidea tego typu uwierzytelnienia – patrz Identity 2.0) rozpowszechniła się w Internecie musi być ona dostępna dla jak największej liczby użytkowników. Ten plugin to krok w dobrą stronę. Jeżeli już jesteśmy przy FireFox – Witek Rugowski na swoim blogu opisał problem jaki napotkał w FF 2.0. Przeglądarka ta blokuje dostęp do witryn WWW umieszczonych na niestandardowych portach, jeżeli port ten jest znanym i zarejestrowanym portem usługi.

  3. SpiritGeek on August 2nd, 2007 3:42

    Actually, network.security.ports.banned.override does work in 2. It’s just not there by default, so you have to create it. If you go to about:config, then context-click, go under New, and then select String, you can add it. I just did this in 2.0.0.6 and it worked like a charm.

  4. SteveB on December 10th, 2007 14:14

    In firefox’s address line enter

    about:config

    This will bring up the configuration pages.
    -Right click in the list and select NEW – STRING
    -Type the following for the preference name

    network.security.ports.banned.override

    -Type the port number you want to be able to browse on in the next input box and you shoud be all set to go!
    No restart of Firefox is necessary.

    This has worked in previous versions of Firefox and recently tested on a brand new machine with 2.0.0.11 installed.

Leave a Reply