[RESOLVED] issue with login page @ Capital One
[RESOLVED] issue with login page @ Capital One
I can login with NS disabled, but when I enable NS, the Continue button won't work. My whitelist includes capitalone.com and capitalone360.com, and I "allowed" all scripts on the page: https://secure.capitalone360.com/myacco ... g/login.vm
Mozilla/5.0 (Windows NT 5.1; rv:42.0) Gecko/20100101 Firefox/42.0
Re: issue with login page @ Capital One
When this issue occurs, do you see anything related in the Browser Console? (Ctrl-Shift-J)
(if you don't know what's related, turn off CSS warnings and post everything else you see)
(if you don't know what's related, turn off CSS warnings and post everything else you see)
*Always* check the changelogs BEFORE updating that important software!
-
Re: issue with login page @ Capital One
Below is what I think you're looking for from the console. Interesting that doubleclick.com is in my forbidden list, but it doesn't show up in the script list for this page. I specifically allow google-analytics and ensighten (temporary for this page) and they show up in the NS menu "Forbid google-analytics.com" and "Forbid ensighten.com. Why would those scripts be denied?
Code: Select all
[ABE] <LOCAL> Deny on {GET https://www.google-analytics.com/analytics.js <<< https://secure.capitalone360.com/myaccount/banking/login.vm - 2}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny
[ABE] <LOCAL> Deny on {GET https://nexus.ensighten.com/capitalone/Bootstrap.js <<< https://secure.capitalone360.com/myaccount/banking/login.vm - 2}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny
[ABE] <LOCAL> Deny on {GET https://fls.doubleclick.net/activityi;src=806653;type=gener917;cat=flood725;ord=7714144721534?;ord=7714144721534? <<< https://secure.capitalone360.com/myaccount/banking/login.vm - 7}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
DenyMozilla/5.0 (Windows NT 5.1; rv:42.0) Gecko/20100101 Firefox/42.0
Re: issue with login page @ Capital One
1) If allowing google-analytics gets it working, that is a NoScript bug.
2) Those domains are definitely not LOCAL. Have you got a custom HOSTS file or the like set up to block them?
Please post here a DNS lookup of one of those ABE-blocked domains. (use nslookup from Command Prompt - e.g. for google-analytics, type this: )
3) No idea if any of this is helpful, viewtopic.php?f=7&t=21630
2) Those domains are definitely not LOCAL. Have you got a custom HOSTS file or the like set up to block them?
Please post here a DNS lookup of one of those ABE-blocked domains. (use nslookup from Command Prompt - e.g. for google-analytics, type this: )
Code: Select all
nslookup www.google-analytics.com*Always* check the changelogs BEFORE updating that important software!
-
Re: issue with login page @ Capital One
(Without using a valid UN/PW, I'm able to enter both UN & PW, with the Continue button working for each.)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
Re: issue with login page @ Capital One
@barbaz, I do have a HOSTS file (from mvp.org), and it does include an entry for google-analytics. However, after reviewing the thread you linked, I upgraded to the latest NS version and it fixed the problem without me having to remove the entry in the HOSTS file. Therefore I didn't bother with nslookup. BTW, I had previously searched this forum for capitalone, so I missed that thread since it had a space between the two words
What I don't understand is why the login page now works with google-analytics blocked by the local HOSTS file. Does 'allowing' a site in NS override the local HOSTS entry?
Anyway, thanks for the assist!
What I don't understand is why the login page now works with google-analytics blocked by the local HOSTS file. Does 'allowing' a site in NS override the local HOSTS entry?
Anyway, thanks for the assist!
Mozilla/5.0 (Windows NT 5.1; rv:42.0) Gecko/20100101 Firefox/42.0
Re: issue with login page @ Capital One
surrogate script run regardless of how the script is blocked
*Always* check the changelogs BEFORE updating that important software!
-