Jolly port matching

[Joe Bloggs]

I've used jolly port matching on the whitelist for the longest time, yet the silly "http://127.0.0.1:*" message keeps showing up on the pop-up menu. Yes, I have Proxomitron and ZoneAlarm, but isn't jolly port matching supposed to fix this problem? By my last count on the whitelist, I've had to allow 27 different ports for the localhost. Any ideas?

[David44]

I want to write "127.0.0.1:0" in the white list, but Noscript doesn't allow it. After typing the colon, the button is greyed out. What's the problem there?

[barbaz]

I want to write "127.0.0.1:0" in the white list, but Noscript doesn't allow it. After typing the colon, the button is greyed out. What's the problem there?

you need to specify a protocol

Jolly port matching - an address with a 0 (zero) port specification will match every site with the same protocol, domain and any non-standard port: if one is met during navigation, it gets temporarily enabled. For instance, http://acme.org:0 matches http://acme.org:8080 and http://acme.org:9999, but not https://acme.org:9999 (different protocol) nor http://acme.org (standard 80 port, omitted). Since *protocol specification is mandatory*, regular subdomain matching with rightmost components comparison couldn't work for multiple subdomain. You can specify subdomain matching patterns using an asterisk in place of the leftmost domain component: for instance, you need to match all the subdomains of acme.org for all ports with the HTTPS protocol, you can whitelist https://*.acme.org:0. This is the ONLY situation where asterisk is considered a wildcard.

(emphasis mine)

[David44]

you need to specify a protocol

Thanks. I tried it also with http://127.0.0.1:0. But the entry cannot be added to the list. After typing the 0, the button is greyed out.

[barbaz]

Weird, WFM...
Check that "http://127.0.0.1:0" isn't already in your whitelist (would be near the bottom, after the about:xyzzy entries), and if not, maybe try NoScript Options -> Reset (just to test, export your NS settings first as backup), see if you can add it then.

[David44]

Check that "http://127.0.0.1:0" isn't already in your whitelist (would be near the bottom, after the about:xyzzy entries),

It isn't.

and if not, maybe try NoScript Options -> Reset (just to test, export your NS settings first as backup), see if you can add it then.

Done, no change. After typing "0", the button is inactive.

[therube]

Are you sure you are including http:// and or https:// ?

(When I first pasted the link in, I too thought Allow was grayed out? [Well something I had done did cause it to be grayed out.] But I'm not sure if I was including http:// or not? [And then, & still now, sometimes, it seems like the Options dialog is not opening?] But since the initial "gray out", I haven't been able to duplicate that, so long as I do include http:// along with the :0.)

[Giorgio Maone]

Weird, WFM...

... because it's yet another Gecko 28 bug, and you're on 29.
Consider the following code:

Code: Select all

Cc["@mozilla.org/network/io-service;1"].getService(Ci.nsIIOService).newURI("http://127.0.0.1:0", null, null)

This works on 29 and above, but fails in 28 (URIs with port 0 are considered malformed).

Worked around in latest development build 2.6.8.19rc1.

[David44]

Thank you, now it works.