Hi All,
We are seeing a series of 400 Bad Reqeusts while accessing the site in different environments(Dev, QA, PROD). I'm trying to increase the request header size using LimitRequestFieldSize 16384. Ours is a multi-tenant application and I added this config to a tenant-specific vhost file. It is not picking this configuration and I still see 400 even after making this change.
I tried using LimitRequestLine 16384 but that didn't work as well. Can you please let me know if there's any additional configuration that we need to make to increase the Header size limit?
Below is the tenant-specific vhost file where I added the entry
Solved! Go to Solution.
Views
Replies
Total Likes
If the header size because of any reason is larger then the default one, then the configuration needs to be increased at AEM instance also along with Apache configurations.
You need to increase size "Header Buffer Size" property for "Apache Felix Jetty Based Http Service” in “/system/console/configMgr” for all production publishers.
Hope this helps!
Thanks
Nupur
Can you check the dispatcher log for such request. It will clearly mention which header field you need to update with. Do you have Akamai as well on your instance? If yes try updating it. Normally Akamai has default request header size as 32kb but Apache has 8 kb.
can you check if your tenant specific vhost file is working in your configuration
Hi,
Try to first identify where this limitation is occurring. It could be at the CDN or dispatcher level. Adjust accordingly based on your findings. If this is Apache, it appears that your configuration is set correctly. I would recommend checking the logs as well.
If the header size because of any reason is larger then the default one, then the configuration needs to be increased at AEM instance also along with Apache configurations.
You need to increase size "Header Buffer Size" property for "Apache Felix Jetty Based Http Service” in “/system/console/configMgr” for all production publishers.
Hope this helps!
Thanks
Nupur
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies