Qlik Sense Client Managed: Adjust the MaxHttpHeaderSize for the Micro Services run by the ServiceDispatcher

[Sebastian_Linser]

When using SAML or ticket authentication in Qlik Sense, some users belonging to a big number of groups see the error 431 Request header fields too large on the hub and cannot proceed further.

Resolution

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

The default setting will still be a header size of 8192 bytes. The fix adds support for a configurable MaxHttpHeaderSize.

Steps:

1. To configure add it at the top section of the file under [globals] (C:\Program Files\Qlik\Sense\ServiceDispatcher\service.conf)

   [globals]
   LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
   (...)
   MaxHttpHeaderSize=16384

2. Once the change is done, save the file and restart the Qlik Service Dispatcher service.

Note: The above value (16384) is an example. You may need to put more depending on the total number of characters of all the AD groups to which the user belongs. The max value is 65534.

Environment:

Qlik Sense Enterprise on Windows 

[janyf]

This could help also in case when your qlik is on the same domain as your other websites and your cookies have incorrectly set limitation. Therefore they are retained also for qlik and clogging qlik cookie - causing 431 Request header fields too large 

[syedhaque]

Hi @Sonja_Bauernfeind 

Do we need to configure this in all the nodes of Qlik sense

[Sebastian_Linser]

@janyf Hello, yes on all the nodes in every services.conf, then restart the service dispatcher.

[syedhaque]

Hi @Sebastian_Linser  I have done above changes and restarted the service dispatcher but in QMC when I checked the proxy settings it still shows old value. do we need to update it in qmc portal also?

[alexandra_dh]

Hi @syedhaque , did you have an answer to your question ?

I've the same problem as you.

You can configure maxheaderSize in the QMC and in the services.conf files but it seems not related each others ? What is the difference between these parameters ?

What happens if it's different ?

[Sebastian_Linser]

Hello Alexandra,

the one in the QMC is for the proxy service, the one in the services.conf is for the node.js services started by the service dispatcher service.

So if you are different you might allow more/less on dispatcher triggered Services e.g. NotifierService than on the proxy service.

best regards

Sebastian

[peter_turner]

Hello,

You can also see this behaviour when loading the Hub and getting stuck on the loading circles.

To verify the issue, use the browser developer tools, network tab, and look out for messages that have Time = Pending, usually Type = xhr and Name = language?cachebust=1754305972556

Apply the suggested changes to MaxHttpHeaderSize=65534 ,and monitor the results.