topic Re: 400 Bad Request error sometimes after session timeout in Management & Governance

400 Bad Request error sometimes after session timeout

mountaindude — Sat, 16 Nov 2024 00:47:45 GMT

This is a tricky one.

I have a QSEoW 2020-Nov-patch1 environment from which I am getting strange timeout errors.
A couple of different virtual proxies: Azure SSO via SAML, and standard Windows auth from the login page provided by Sense.

Session length is 30 minutes and an idle timeout will result in the user being sent to the login screen. All good.

Most times a click on the "Login" button will result in the username/password (for Windows login endpoint) or the Azure login (for Azure SSO) flow being shown.

Sometimes users get this though:

I've been unable to pinpoint what's causing it and cannot reproduce it.
Those 400 errors come in various shapes and forms (for example: if a user is arriving with a URL that's not whitelisted in the virtual proxy settings that will give a 400 error), but I've never seen one with "Bad Request" twice like this.

Also, I can't find anything in the logs. Zero.

Usually these kind of errors result in proxy log entries, not this time though.
I've searched all logs from all services, no luck.
I might of course have missed something... Hopefully I've missed something.

So: The issue happens often enough to be an annoyance and it's definitely a loose end.
And loose ends aren't any good.

Any ideas, anyone?

-----------
Edit:

Some additional context. There is a Traefik 2.3 reverse proxy in front of the Qlik Sense server, meaning that traffic to Sense pass through Traefik. The root cause of the issue may be in Sense, in Traefik, in Azure - or any combination thereof.

BUT: Given that the 400 error obviously is served by Sense, I figure there should an error entry somewhere in some log. In the best of worlds it would give a hint to what's going on.

Re: 400 Bad Request error sometimes after session timeout

lucienorrin — Thu, 28 Jan 2021 21:57:21 GMT

Finally someone else with the same issue!

We have the exact same problem except we have an F5 load balancer in front of the hub. Been having it randomly for years. It's been a random issue since at least the early Month/Year versions.

I can't find anything in the logs either, but the error pages are definitely Qlik branded.

Sometimes we will also get the 'stop sign' 404 error. Though the 404 errors are less common since upgrading to Feb 2020

Re: 400 Bad Request error sometimes after session timeout

mountaindude — Wed, 03 Feb 2021 12:53:25 GMT

Interesting.

For what it's worth, I am also sometimes seeing this when connecting directly to the Qlike Sense Enterprise on Windows (Nov 2020, sp1) without any load balancer or reverse proxy in front of it.

I am pretty sure it's related to sessions timing out and that something then - sometimes - goes wrong when the user reconnects by refreshing the browser window.

Increasing the session timeout of course makes this less of a problem, but... not always a good option.

I've looked through the support site too, the best match so far is this article:
https://support.qlik.com/articles/000098524

That issue involves using iFrames and older Senses versions - both of which don't apply to my situation.

Re: 400 Bad Request error sometimes after session timeout

Damien_V — Tue, 23 Feb 2021 14:52:34 GMT

Hello @mountaindude

This is a known defect (QB-2992) that Qlik R&D is currently investigating.

There is no ETA yet on when a fix will be released for it.

Re: 400 Bad Request error sometimes after session timeout

mountaindude — Wed, 24 Feb 2021 07:02:55 GMT

Thank you @Damien_V for confirming this is a bug - I've been pulling my hair (not much left to begin with..) on this one!

Ok, I'll put this one on hold for now, hoping for a solution up ahead.

Bte, do you know of any workarounds?
We've increased the session timeout value and that of course does the trick, but it also comes with obvious drawbacks.

Re: 400 Bad Request error sometimes after session timeout

Damien_V — Wed, 03 Mar 2021 12:23:02 GMT

Hello @mountaindude

You've already tried

From the article you've found, right ?
If that is the case and you're still seeing the issue, then you're probably encountering one of the corner cases where the workaround doesn't work.

Re: 400 Bad Request error sometimes after session timeout

lucienorrin — Wed, 14 Jul 2021 12:37:42 GMT

Hi @Damien_V

We just upgraded to Feb 2021 and still have this exact 'bad request' issue.

Did the fix for Bug QB-1116 get implemented for June 2020 and higher?

Re: 400 Bad Request error sometimes after session timeout

Damien_V — Thu, 15 Jul 2021 14:59:07 GMT

Hello @lucienorrin

Just to clarify, you're getting an error 400 after the session timing out or after logging out ?
As Error 400 is a generic error, it could also happen for many different reasons.

Re: 400 Bad Request error sometimes after session timeout

lucienorrin — Thu, 15 Jul 2021 15:05:23 GMT

@Damien_V

Timing out.

After a timeout, we see the ‘You have been logged out… Your session has expired…’ screen.

Then when clicking log in, we get the "Bad Request Bad Request" exactly like the screenshot in the op.

Re: 400 Bad Request error sometimes after session timeout

mountaindude — Thu, 15 Jul 2021 15:09:22 GMT

I also see this happening on QSEoW Feb 2021, on several different Sense clusters using various authentication solutions. So the issue is still there. Have not tested May 2021 yet.

Re: 400 Bad Request error sometimes after session timeout

Damien_V — Fri, 16 Jul 2021 10:14:26 GMT

QB-2992 was still in process at the time February 2021 was released, so it's not been included.

It's not clear though from our system in which exact release it's included.

As it was closed beginning of march, I expect that it's included in May 2021, but I need to double-check with our R&D

Re: 400 Bad Request error sometimes after session timeout

Anil_Babu_Samineni — Sat, 17 Jul 2021 11:43:54 GMT

@Damien_V I have checked in May 2021 Patch 2, Still that occurs.

Re: 400 Bad Request error sometimes after session timeout

schmidtj — Thu, 17 Feb 2022 10:09:27 GMT

Hi Damien,

can you confirm that the error was patched on May 2021?
We are running Patch 4 and we are still experiencing that problem.

Moreover, i am not able to find these 400 errors in the logs even though we frequently get reports of them happening. Our logging configuration is set up correctly i think so they should be logged. This is really making it difficult to monitor that problem.

Would be very glad for a feedback.

Thanks a lot!

Re: 400 Bad Request error sometimes after session timeout

mountaindude — Thu, 17 Feb 2022 10:48:14 GMT

Those errors are still very much around, I'd say.

Running QSEoW Nov-2021 and those errors occur more often than not when a session times out.

Re: 400 Bad Request error sometimes after session timeout

mountaindude — Thu, 17 Feb 2022 10:51:01 GMT

...and I've really looked through the logs for clues as to what's going on, haven't found anything at all.

Given that we're looking at something that's sent as an error to the client I would expect at least a warning or error in the Sense logs. But can't find anything.

Maybe there would be clues in the debug logs, but that's a whole other level of investigation..

Re: 400 Bad Request error sometimes after session timeout

schmidtj — Thu, 17 Feb 2022 11:31:49 GMT

Yes i agree, the situation is not really satisfactory.
Especially when you display Qlik charts in widgets in 3rd party systems and all you see is a 400 error message ...

Re: 400 Bad Request error sometimes after session timeout

Frank_S — Wed, 08 Jun 2022 22:31:03 GMT

Team

This issue has been resolved in May 2021 GA (initial) release.

If you are experience this or similar issue, with this or later versions, it is requested that a new support request is started.

Kind regards...