Noscript causing MSN to display "Page not found"
Posted: Mon Mar 21, 2016 3:22 pm
Did a search for this and found nothing. This issue started happening around Monday. On MSN.com if I click on an article, any article, I briefly get the article page with no stylesheet, then it immediately redirects to a "This page cannot be found" page.
On Chrome it works fine, and on Firefox where I'm affected, I can get it to load fine by completely disabling NoScript. Needless to say I have do not have MSN blocked and it should be allowed to run whatever scripts it needs to to properly load the page, but it doesn't.
My first thought was they changed something to detect ad blockers, but i also run ghostery and Ad Block Plus. I went through all my add ons, disabling and re enabling then one at a time and I confirmed that it's just NoScript that's causing the issue. I then tried various options, blocking and allowing various parts of MSN.com. I found that blocking MSN.com directly prevents the redirect and breaks the site, but since I'm allowing it and all its parts to execute scripts, why is the redirect being triggered?
Updated Noscript to the latest version, did not fix the issue.
Just updated Firefox to the latest version, also did not fix the issue.
Not sure what else to try.
On Chrome it works fine, and on Firefox where I'm affected, I can get it to load fine by completely disabling NoScript. Needless to say I have do not have MSN blocked and it should be allowed to run whatever scripts it needs to to properly load the page, but it doesn't.
My first thought was they changed something to detect ad blockers, but i also run ghostery and Ad Block Plus. I went through all my add ons, disabling and re enabling then one at a time and I confirmed that it's just NoScript that's causing the issue. I then tried various options, blocking and allowing various parts of MSN.com. I found that blocking MSN.com directly prevents the redirect and breaks the site, but since I'm allowing it and all its parts to execute scripts, why is the redirect being triggered?
Updated Noscript to the latest version, did not fix the issue.
Just updated Firefox to the latest version, also did not fix the issue.
Not sure what else to try.