How Internet browser (IB) and web server (WS) “relate.”
Each has its own perspective of the other.
Each has some data to send.
Each has to consider what is received.
IB sends a request to WS.
WS responds, and may send a cookie back to IB.
IB sends the cookie back to WS.
What WS will then send, depends upon what IB is prepared to send in reply, or not.
If WS keeps trying to send something, with an expectation of what IB will reply . . . but IB does not reply exactly, then . . .
An on-going repetition of WS sending and IB trying to make sense of (and render) what WS has sent, may continue, because
IB realizes that IB keeps failing to render (but keeps trying) with what info it has from WS, while
WS does not send addiitonal info, and instead keeps trying to send the info that it is stuck on sending – because WS continues to NOT get a reply that WS keeps expecting from IB.
There, you be. Seriously.
Usually, you need to relax “Agressive” to Standard
and also figure out whatever is the source or sources of one or more cookies (re website where you sign on), that you need to allow in Brave Browser settings
– and thus, IB will finally send back to WS, what WS has been expecting.
Developer Tools is useful:
“Unable to log on to bank website - #3 by 289wk”
In order to learn, what website sources (of cookies and scripts) may be involved, learn to use the Developer Tools > Network tool for monitoring items, and use the Developer Tools > Application for learning sources of, and examining, Cookies.
How to use Developer Tools
Developer Tools > Network tool is where you search for sources of scripts and other items that will qualify despite their not being obvious scripts.
Developer Tools > Application tool is where you will find the sources of cookies.