Qlik Sense: Error message 400 Bad Request in an iFrame after upgrade to September 2019 or later

[Damien_Villaret]

Error 400 Bad request is randomly happening after upgrade to September 2019 or later.

When using Qlik Sense in an iFrame, this can be consistently replicated after the session times out in the iFrame. In that case, the browser will need to be restarted or the cookie cleared manually in the browser developer tools to be able to use Qlik Sense again.
However, the issue is not specific to iFrames and can also be seen in other scenarios.

Environments:

• Qlik Sense Enterprise on Windows September 2019 or later

Resolution

1. This is due to a known defect QB-1116 due to a problem handling session cookie.
   
   The fix is included in the following releases:
   - April 2020 Patch 1 and subsequent patches on the same branch.
   - June 2020 and higher
   
   
   Workaround:
   
    Modify C:\Program Files\Qlik\Sense\Proxy\Proxy.exe.config file with the following, setting the value to 0, meaning:
   
   <add key="InvalidSessionRequestBurstLimit" value="00:00:00"/> <!-- Minimum value is 0, maximum value is 365 days -->
   
   
2. Restart the Qlik Proxy Service.

[justinvchiang]

Hi Damien,

We recently upgraded to April 2020 Patch 5 because we had a user who was experiencing the "Too many sessions active in parallel" issue and this allowed us to adjust the "InvalidSessionRequestBurstLimit" according to this article https://community.qlik.com/t5/Knowledge-Base/Certain-users-get-quot-too-many-sessions-active-in-para...

This resolved the issue for our end user but now they are receiving the 400 Bad Request error when accessing Apps via an iframe.  Am I to understand that the work around for the 400 Bad Request error when accessing via an iframe is to revert the fix for the "Too many sessions active in parallel" issue?  And can you confirm that both issues are resolved in the June 2020 release?

[Sonja_Bauernfeind]

Hello @justinvchiang 

I can confirm that QB-1116 is flagged as fixed in June 2020, though also for April 2020 Patch 5.

There's a similar defect though that was fixed in April Patch 7 (as well as June Patch 5, September Patch 1, and any later releases):  QB-1995. 

Will check with Damien as well to see if he has additional input on this!

-Sonja 

[ansarikashif2017]

Hi @Sonja_Bauernfeind 

Do you have any update?

We have May 2021 Patch 5. We are getting the iFrame timeout bad Request error. Currently the value set for InvalidSessionRequestBurstLimit is 02. The fix for the iFrame Bad request is to set it to 0.

We are worried setting it to 0 may introduce the Too many sessions active error?

[Sonja_Bauernfeind]

Hello @ansarikashif2017 

Settings this to 0 should not introduce too many session errors. But if you continue to encounter errors, we advise you to contact our support to have a full investigation started as this will require a more direct involvement which we cannot provide through an article.

All the best,
Sonja