topic Re: Strange browser behavior. in Management & Governance

Strange browser behavior.

M_B — Wed, 28 Aug 2024 08:14:06 GMT

Recently, when using our external link, after entering credentials we receive a blank page with the ticket number stuck in the URL (https://sub.domain.com/hub/?qlikTicket=<number>).

If using Edge, doing a full refresh (Shift+left-clicking refresh) bypasses the issue and redirects to hub/my/work.

If using Firefox, nothing works until a captcha shows up from somewhere:

After validation, everything works properly. Even if you logout and log back in. After some time passes, the issue returns for all browsers but force refreshing Edge bypasses it every time. It seems at the first attempt, something is stopping the redirection. I would like to know if someone has come across this issue before or if someone could estimate the cause of the issue.

Re: Strange browser behavior.

M_B — Wed, 28 Aug 2024 11:27:01 GMT

After speaking with the cybersecurity team, it seems that the issue was caused by a WAF (web application firewall). After adding an exception the link is redirecting properly and not blanking at first sign-in.

Re: Strange browser behavior.

M_B — Thu, 29 Aug 2024 06:40:06 GMT

Issue still persists.

Re: Strange browser behavior.

M_B — Thu, 29 Aug 2024 08:55:54 GMT

Interesting development, if I first sign in through Firefox and get stuck at the blank page, I can open Edge, sign in, bypass the problem, and then if I go back to Firefox and shift+refresh, it works...

Why is Edge fixing the problem between Firefox and the address? What information is being passed through Edge that is allowing the session to be greenlit between the client and server? Keep in mind I have to do the cache disable refresh (shift+refresh) every first time to get it work.

Re: Strange browser behavior.

M_B — Wed, 11 Sep 2024 12:31:34 GMT

Issue was resolved after a session with the WAF support.