What you describe is not a NoScript issue. It's a website bug.
The URL of the blocked resource is -
Code: Select all
https://https://www.maskedname.com/piwik.php
Which the browser interprets as -
Code: Select all
https://https//www.maskedname.com/piwik.php
As you can see, the domain of that URL is indeed "https".
The webmaster needs to change the second line of that code snippet, either to this...
Code: Select all
var u='https://www.maskedname.com/';
... or this -
(aside: NoScript 10's behavior in this situation is not what I would expect. I would think NoScript should *not* display "...https" in the popup, instead showing that entry as "https://https", because the domain "https" has no dots and is not a TLD. NoScript Classic behaves as expected.)
What you describe is not a NoScript issue. It's a website bug.
The URL of the blocked resource is -
[code]https://https://www.maskedname.com/piwik.php[/code]
Which the browser interprets as -
[code]https://https//www.maskedname.com/piwik.php[/code]
As you can see, the domain of that URL is indeed "https".
The webmaster needs to change the second line of that code snippet, either to this...
[code] var u='https://www.maskedname.com/';[/code]
... or this -
[code] var u='//www.maskedname.com/';[/code]
(aside: NoScript 10's behavior in this situation is not what I would expect. I would think NoScript should *not* display "...https" in the popup, instead showing that entry as "https://https", because the domain "https" has no dots and is not a TLD. NoScript Classic behaves as expected.)