Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
FarshadNour
Partner - Contributor II
Partner - Contributor II

Problematic cookie values set in Qlik Sense Enterprise 2023 Patch 2

Hello everyone ,

We've recently completed an upgrade to the latest version of Qlik Sense Enterprise, specifically the November 2023 patch 2 release. However, post-upgrade, we've encountered a set of issues affecting the Qlik Management Console (QMC), stream functionality displaying a "not available" message, and applications continuously loading. It's important to note that the majority of our users utilize Google Chrome.

Upon investigating through Google Chrome's developer tools, a recurring issue emerged - "431 The request header is too long." This error is consistently observed when attempting to access streams and open apps. Additionally, during navigation within the hub, a 431 error occurs with each stream selection.

edited hub navigaition.PNG

QMC Infinity loading:

Edited QMC.PNG

Further exploration into the local cookie storage revealed that the cookies with keys "BNF_STRING_CACHE_DATA_S" and "BNF_CACHE_DATA_S" contain seemingly random values, possibly due to hashing. Notably, the length of these keys is approximately 20,000 characters, which appears to be triggering the "request header too long" problem.

Temporary resolution involves using Incognito mode and clearing the cache. However, it's worth noting that the issue resurfaces once the cache values are reset.

We are curious if this is a version-specific issue, as there is no mention of it in the patch notes. Has anyone else in the community encountered similar problems with the November 2023 patch 2 release?

Kind regards,
F.N

Labels (4)
1 Solution

Accepted Solutions
CK74
Contributor
Contributor

Had the exact same error. Setting Header Size to 65.534 bytes as described in these 2 articles worked for us (don't know which of them though, as I've set them simultaneously ) 

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-HTTP-Header-size-restriction/ta-p...

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Client-Managed-Adjust-the-MaxHttp...

 

View solution in original post

1 Reply
CK74
Contributor
Contributor

Had the exact same error. Setting Header Size to 65.534 bytes as described in these 2 articles worked for us (don't know which of them though, as I've set them simultaneously ) 

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-HTTP-Header-size-restriction/ta-p...

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Client-Managed-Adjust-the-MaxHttp...