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.
[quote="lawson23"]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.[/quote]
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.