troubleshoot (log blocked sites)

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: troubleshoot (log blocked sites)

Re: troubleshoot (log blocked sites)

by Pansa » Sat Jan 27, 2018 7:52 pm

lawson23 wrote:So the issue is the site is it is during the redirection I believe a script is being executed and then that redirects to another site which is already allowed. Allowing scripts globally should allow the site to work but would defeat the purpose of finding out what might be the site issue.

I'm going to load firefox in safe mode and do a test to make for sure it is not firefox causing the problem. I can get to the site using Chrome without script blocking.
The point was using it to check if it actually does the same kind of redirect if it ISN'T blocked.

Many pages only do this kind of "rerouting" if something FAILS, rather than if it works.
Take twitter for instance.
If you haven't allowed twitter, it will reroute to m.twitter. so you will never get the chance to make a specific www.twitter rule, but only either the m.twitter rule or the one that allows both.
But if you stop the rule enforcing, it won't redirect, giving you the chance to make the rule, and than turning the enforcement back on.

So I don't really understand the "might" in your sentence. Just try it.
Turn on globally allow scripts, and log in.
Then create the rules and turn global allow back off.

then check.
If they actually do the same kind of redirecting on success as they do on fail, the only thing else I can think of is trying to check if you can glimpse where in the script on the login page it is sending you to to begin with, and try to manually add that direction in the hopes that this "jump point" is that source.

Re: troubleshoot (log blocked sites)

by lawson23 » Sat Jan 27, 2018 3:56 pm

Well firefox in safemode does the same thing so it is not a NoScript issue but this is still a needed feature request. I have had these redirection issues with NoScript in the past.

Thanks for everyone's support.

Re: troubleshoot (log blocked sites)

by lawson23 » Sat Jan 27, 2018 3:50 pm

So the issue is the site is it is during the redirection I believe a script is being executed and then that redirects to another site which is already allowed. Allowing scripts globally should allow the site to work but would defeat the purpose of finding out what might be the site issue.

I'm going to load firefox in safe mode and do a test to make for sure it is not firefox causing the problem. I can get to the site using Chrome without script blocking.

Re: troubleshoot (log blocked sites)

by Pansa » Wed Jan 24, 2018 2:28 pm

lawson23 wrote:Ok I have a site from my bank that all of a sudden stopped working. It is going from my account to my pay bills website and every time I click this it ends up redirecting back to the login page and I have to relogin and back at the accounts page. I do see noscript quickly flash red like it blocked something during this process but I'm not quick enough to be able to see this and test allowing certain pages.

Ideas on how I review what and fix what is possibly going on here. Of course this may not even be a noscript issue but I can't rule it out without testing.

Have you tried using the "Scripts Globally Allowed (dangerous)" options to allow the page regardless of your settings, just to create the rules you need?

That option basically deactivates the "rule enforcing" and lets the page run as if there were no restrictions.
Alternatively you could temporarily change the permissions for the "default" set to allow all executions, to do the same (created trusted rules for those domains that cause the redirect when blocked)

Once you have created the trusted rules the page requires, you revert those changes.

Re: troubleshoot (log blocked sites)

by lawson23 » Wed Jan 24, 2018 2:16 pm

What I'm saying is I need something some way to see what was blocked during the page change. It does change domains and the ending domain is allowed so something happens in the middle and I'm guessing it is some kind of oauth switch with another domain but it happens so fast I can't see it to try and resolve.

No way to currently do some sort of logging in version 10?

So just for clarification the bank I use is CapitalOne360 for clarification. Has always worked but about two weeks ago I can no longer get into bill pay.

Re: troubleshoot (log blocked sites)

by barbaz » Tue Jan 23, 2018 9:09 pm

So, if I understand you right, basically you would like to see "Recently Blocked Sites" brought back in NoScript 10?

troubleshoot (log blocked sites)

by lawson23 » Tue Jan 23, 2018 7:38 pm

Ok I have a site from my bank that all of a sudden stopped working. It is going from my account to my pay bills website and every time I click this it ends up redirecting back to the login page and I have to relogin and back at the accounts page. I do see noscript quickly flash red like it blocked something during this process but I'm not quick enough to be able to see this and test allowing certain pages.

Ideas on how I review what and fix what is possibly going on here. Of course this may not even be a noscript issue but I can't rule it out without testing.

Top