InformAction Forums

Posted: **Mon Mar 23, 2009 1:16 am**

IIUC, the following line of noscriptService.js is responsible for * in force-HTTPS glob patterns:

return '^' + p.replace(/^([^\/:]+:\/*)\*/, "$1[^/]*").replace(/\*/g, '.*?');

The first replacement appears to make the * in *.mattmccutchen.net not match slashes. But this doesn't work, because its output is affected by the second replacement. E.g., with *.mattmccutchen.net in the force-HTTPS list, http://a/.mattmccutchen.net is forced to HTTPS. Reversing the order of the replacements should fix the problem.

Posted: **Mon Mar 23, 2009 8:40 am**

Ouch!

Reversing the order of the replacements should fix the problem.

It's not enough, actually.
Changed into

Code: Select all

return '^' + p.replace(/\*/g, '.*?').replace(/^([^\/:]+:\/*)\.\*/, "$1[^/]*");

(notice the extra dot being elided).
Fixed in latest development build, thanks.

Posted: **Thu Apr 09, 2009 7:41 am**

I had missed this, wow such a subtle but incredible difference. Sweet.

InformAction Forums

URIPatternList.parse mishandles * in domain

URIPatternList.parse mishandles * in domain

Re: URIPatternList.parse mishandles * in domain

Re: URIPatternList.parse mishandles * in domain