Home › Forums › Feature Requests / Enhancements

browse intranet IP range in direct

Fri, 06/13/2008 - 08:31 — Anonymous

Hello

It seems that we can only specify URL and not IP ranges in the patterns rules.
I would like to specify that the 159.50.* should browse directly.
It works fine with the *.intranet pattern but I am forced to select manualy "Direct browsing" for internal IP ranges.

Coudl you please implement IP ranges pattern as well or explain me how to do?

Thanks for your help!
Isidore.

‹ Support For Sea Monkey Questions ... ›
Sat, 06/14/2008 - 23:29 — ericjung

Hi Isidore, IP ranges are

Hi Isidore,

IP ranges are supported. You aren't writing the patterns correctly. 159.50.* is not going to match http://159.50.* or https://159.50.*. You need to specify one of these:

http://159.50.*
or
https://159.50.*
or
*://159.50.* [covers all protocols]

Regards,
Eric

Tue, 07/15/2008 - 08:13 — Jan-Willem (not verified)

Yes, Nice that IP-address

Yes,

Nice that IP-address ranges are supported, but the request here is simpler.

When connected to a corp net you want to Blacklist all Intranet sites (typically on Private IP-addresses). To access an intranet site you typically browse an internally resolved name such as http://helpdesk.yourcompany.com/. That allows a filter of *yourcompany.com*, but often these servers are resolved internally by shorter names such as http://helpdesk/

Blacklisting everything that was resolved by the browser as being in the intranet IP-address range would be helpful.

Jan-Willem

Thu, 07/17/2008 - 14:07 — ericjung

Firefox has no access to the

Firefox has no access to the subnet mask info of the connection providing internet access, so I don't know how to do what you want.

Mon, 07/28/2008 - 04:52 — AH (not verified)

Workaround

Some patterns will mostly do what you want. I had the same issue a while ago and got away with the following three:

  • localhost - Matches the local host optionally prefixed by a user:passwd auth string and optionally suffixed by a port number. Note that the entire local subnet (127.0.0.0/8) matches.
    ^https?://(?:[^:@/]+(?::[^@/]+)?@)?(?:localhost|127\.\d+\.\d+\.\d+)(?::\d+)?/.*
  • local subnets (IANA reserved address space)
    ^https?://(?:[^:@/]+(?::[^@/]+)?@)?(?:192\.168\.\d+\.\d+|10\.\d+\.\d+\.\d+|172\.(?:1[6789]|2[0-9]|3[12]))(?::\d+)?/.*
  • local hostnames (usually no dots in the name)
    ^https?://(?:[^:@/]+(?::[^@/]+)?@)?[\w-]+(?::\d+)?/.*

Took some time to get them right but they also take into account authentication information and an alternate port number in the URL. Hope this helps.

-AH

Thu, 07/31/2008 - 21:39 — Luke (not verified)

The RegExp sets provided by

The RegExp sets provided by AH are great, but adding another option to simply list Subnets using CIDR notation would be terrific.