subdomains temporarily allowed automatically bug

[username]

go to http://bundles.bittorrent.com, allow it temporarily, after the reload, check the tooltip of 'revoke temporary permissions', you will see 'localhost.bittorent.com:'

[therube]

I'm not seeing that.
Are you using an anti-virus (software proxy) or something of the sort, that ties into localhost?

[username]

it happens with connections to domains on ports other than 80 and 443

[username]

no, i don't

[barbaz]

The tooltip may be unreliable. Is that site actually listed in NS Options -> Whitelist (temporary permissions are listed in italics)?

[username]

it seems to be caused when a connection is redirected to another port

go to http://www.oftc.net/WebChat/, allow temporarily, then go to https://webirc.oftc.net:8443/, after it redirects to port 443, check the revoke temporary permissions tooltip, you should see that the subdomain was temporarily allowed on its own followed by a colon without a port number

[barbaz]

it seems to be caused when a connection is redirected to another port

go to http://www.oftc.net/WebChat/, allow temporarily, then go to https://webirc.oftc.net:8443/, after it redirects to port 443, check the revoke temporary permissions tooltip, you should see that the subdomain was temporarily allowed on its own followed by a colon without a port number

OK, I've reproduced that with a local server. Apparently when you temp-allow a (sub-)domain, NoScript assumes you want that temp-allowed on all ports, so in the whitelist tab you'll see something like

Code: Select all

http://the-server:8080

if you visited the-server on port 8080 after temp-allowing it on a normal port.

Expected behavior IMO.

[username]

giorgio didn't say anything about it. it could be or it could become a problem.