Thrawn wrote:lakrsrool wrote:
I wasn't using that log-in page (I don't like using a banks "advertising" [marketing] log-in page so to speak). I always find the direct log-in link to banks which is all the URL does as opposed to using the marketing log-in pages that banks tend to use of which is the easiest to find via web-searches.
Well, if you're using a direct login link, then presumably this is something you have visited before and bookmarked. So, looks like you also need to hunt down the appropriate ruleset.
I'm not sure offhand why µMatrix doesn't show the requests until so late in the process. Normally that would happen due to a particular script trying to load them; if you can identify it, then it may be possible to ensure it tries to run (or surrogate it).
Yes, I "bookmark" so to speak, actually add the link to my start-page and always us that same link from then on. Not to beat-a-dead-horse here, but I'll try and explain one more time why I did what I did and why it seems to be to be the simplest approach to solving my unique problem I had ("my unique problem" is key here as I've realized since you posted your log-in link that the link I use is not very likely commonly used, therefore making this topic to a large extent superfluous unfortunately) and is an approach I figured might not be considered since the requests will otherwise never get displayed at any time (see further details below) using the log-in link I use.
It's easiest (easier than doing the other obviously more technical methods involving "rule sets", "surrogates" or whatever that would seem to me to be more confusing than ever) to simply temporarily "disable" µMatrix so the log-in will work and at that point once logged in the requests will display that need to be allowed. The point being, these two circled requests at the point of the log-in prompt (illustrated below) or the next page attempting to actually log-in
will NOT display at any time but the log-in will end up failing to log-in and instead "trap" the issue that is caused by not allowing the requests by rendering either an alternate page from Chase with phone numbers to call the bank or a page will render what the browser requirements are or sometimes a broken page code prompt asking what to do with a bogus file which of course is an anomaly will display, all of which can simply be solved by temporarily "disabling" µMatrix at the log-in page prior to attempting to log-in to allow the two requests circled in red to display in µMatrix that would otherwise
NEVER get displayed (it's not a matter of getting displayed "late" as you characterize it) which can then be set to be allowed and the change saved and enable µMatrix again and the log-in will work fine from then on.
This seems to me to be the easiest (less complicated and less confusing) approach to take.
Again, using this login URL:
https://chaseonline.chase.com/Logon.aspx which renders this log-in webpage
to log-in will NEVER show these two requests and because they will NEVER display at any time after a log-in attempt which fails and generally redirects to another page as a result which again these requests will not get displayed since the redirected pages are not a log-in. Only a successful log-in will display the two circled requests and a successful log-in can only be accomplished by temporarily "disabling" µMatrix to provide access to the requests that would otherwise not display at which time after successfully logged in these two requests can be allowed (unblock, made green) and save the change and then enable µMatrix again solves the problem.
All of this is only the case for this specific log-in link, so because most people in general will likely use the more prevalently used log-in that search engines will tend to bring up more frequently it's an issue more unique to me perhaps and not something the majority of users will run across. When I posted this I didn't take into consideration most users would not need to take this approach but then this is the log-in I've been using for many years (15+ years) so it's not something that crossed my mind. Fact is, I didn't even think about the alternate log-in link that you have posted above until after you had posted it. Point being, the more commonly used log-in page (which you posted) WILL display these (circled) requests that need to be allowed that in my case were not getting displayed with the link I was using as illustrated above, so with that in mind I sort of wish I had never posted this topic as it's more trouble than it's worth.
When I first posted the topic I assumed that since in my case the requests that need to be allowed were not getting displayed it might be helpful to point this out since some people might not think about there being a need to disable µMatrix to be able to see the requests but unfortunately I did this not taking into consideration at the time that the generally more commonly used log-in link would not have this unique requirement.