• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue 400 Bad Request

nisamudeen97

Regular Pleskian
Hi,

I am getting "Bad Request" error on browser with below error while trying to edit the cookie and send large cookie via cookie manager.

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

I have the below values in /etc/httpd/conf/httpd.conf

LimitRequestBody 2147483647
LimitRequestFieldSize 16380

Can some one help me to resolve this?
 
Hi Maarten,

Thank you very much for responding. I have already mentioned that I have added LimitRequestFieldSize limit to max value and it is still showing error
 
Did you restart Apache after you changed the limit?

Can you tell us the exact steps you took when the error occurred? Where did you edit the cookie, and in what cookie manager?
 
Hi Rhand,

I think you have mis-understood my last update.

1. I had restarted good via shell
2. I am editing cookie via browser extension.
 
Interesting concept to edit a cookie on the browser-side. I have never heard about that. What is the purpose? And what cookie can be so large that it exceeds all limits? How do you edit it, e.g. by a text editor? Do you add control characters that could prevent the server from receiving and interpreting the file correctly? I have strong doubts that this issue is in any way related to the server. It rather seems to be related to the change applied to the cookie file on the client.
 
Hi,

With CMP (consent mngm platform )happen often to have big cookies. The Page refresh Is Just a way to create a request of more than 8 kB
It must be possible to have the website working with a request of 9-10 kB

Because since last week we had a different CMP all users have the old big cookies that expires in 1 year
The new cookies as soon as they are sent to the browser make requests exceed the limit of 8Kb
 
Well, sometimes it may happen because of browser caches and cookies. You can retry it after clearing the browser cache and cookies. If it still doesn't work, then you can temporarily disable your firewall and security software and then try again, and I am sure one of these methods can work for you.
Thanks
 
Hi,
got the same problem width the LimitRequestFieldSize in apache2.
We are testing with cURL. Neither the serverwide settings in the config-file, nor the additional directives in the domain setting have any effect.
service httpd restart via CLI was successful.
Do you have any more suggestions where to debug the error 400?
Thanks
 
Back
Top