possible parsing bug?
Posted: Fri May 03, 2019 10:17 am
Hi!
during navigation to a site, my attention has been catched by a "blocked site" that was showing a domain with name "https".
Looking at the web page source I found that noscript figured the name out from an embedded script section where it found the following code:
......
function() {
var u='//https://www.maskedname.com/';
_paq.push(['setTrackerUrl', u+'piwik.php']);
......
I'd expect that noscript should only report the domain "www.maskedname.com" and not the "https" part of the string.
I'm not sure if the right domain was found or not as it also appears everywhere in the page source.
Thanks for your attention
Andrea
during navigation to a site, my attention has been catched by a "blocked site" that was showing a domain with name "https".
Looking at the web page source I found that noscript figured the name out from an embedded script section where it found the following code:
......
function() {
var u='//https://www.maskedname.com/';
_paq.push(['setTrackerUrl', u+'piwik.php']);
......
I'd expect that noscript should only report the domain "www.maskedname.com" and not the "https" part of the string.
I'm not sure if the right domain was found or not as it also appears everywhere in the page source.
Thanks for your attention
Andrea