How do I fix Bad request size for request header field exceeds server limit

Version 18.0.27 Update #1 / Ubuntu 18.04.5 LTS

Inhaltsverzeichnis Show

Bad Request
Bad Request - Size of a request header field exceeds server limit
Information
What does it mean when size of a request header field exceeds server limit?
How do I fix bad request header field too long?
How do I fix this HTTP error 400 the size of the request headers is too long?
How do I fix request header or cookie too large?

I have been running RSS server scripts for some time without issues. I often have a page or two up relating to the script that I come back to and can refresh just fine. however lately when go back to such an open open tab in Chrome and refresh I get this error:

Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.
Apache Server at default-x_x_x_x Port 443

After some searching I updated the domains Apache & nginx Settings and Additional directives for HTTP + for HTTPS:
LimitRequestLine 16380
LimitRequestFieldSize 16380

However this did not resolve the issue, so I am now rather confused on the next steps. I can sometimes bypass the issue by simply visiting the Plesk logon page and then go back to refresh strange enough. Anyone got some tips?

Chris

Please apply the steps below to troubleshoot the issue:

1. Backup the Apache configuration file:

# cp -a /etc/apache2/apache2.conf /root/apache2.conf.backup

2. Add the following line to the Apache configuration file:

LimitRequestFieldSize 16000

3. Restart apache2 service with the command:

# systemctl restart apache2

In case the issue persists, please double the value from 16000 to 32000 and restart apache2 service.

Thanks will try it out: might takes a day or more to see if it works though as the error is far apart. That aside, is this not what those Additional directives are supposed to do? I was thinking to go up to 32000, it might of course be that the error consisted due to 16k also not being enough in my case.

My suggestion is server-wide, but in Additional directives you apply settings only for one domain.

Bad Request - Size of a request header field exceeds server limit

Information

A user connects to a Fabasoft Folio Webservice running under a Linux operating system and get the following error message as response:

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

Authorization : Negotiate

This indicates that the Kerberos Token Size of the users Kerberos token exceeds the limit of the Apache web server. This token is sent as request header field "Authorization" in every web request.

Solution

To increase Apache's limit for the Request Header Size, add the following line to every WebService_*.conf in the /etc/fabasoft/web directory (for example, : WebService_100.conf, WebService_101.conf etc.)

LimitRequestFieldSize 16384

Default value is 8190.

For further details, see the Apache documentation at http://httpd.apache.org/docs/2.2/de/mod/core.html#limitrequestfieldsize

Applies to

Fabasoft Folio under Linux (all versions)

Topics Map > OS and Desktop Applications > Applications > Browsers

This document describes what to do if you receive a 400 Bad Request error message upon loading a website.

Problem

When you attempt to access a website, you may sometimes instead receive a "Bad Request" error message where the website content should have loaded. This error often contains the number "400" and may include additional text, such as "Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit."

Solution

First, check the website URL you entered to make sure it is correct. If the web address appears to be entered correctly, then the issue can usually be resolved by clearing your browser's cache and cookies.

For instructions on performing these steps, click on the appropriate link for the web browser you are using:

Clearing the browser cache prevents you from using old/out-of-date versions of websites and protects your personal information. It also helps running some applications better on your computer by freeing up space.

Table with browser name and links to Windows documents and macOS documents.

Browser	Windows Document Link	macOS Document Link
Google Chrome	Chrome (Win) - Clearing Cache and Cookies	Chrome (Mac) - Clearing Cache and Cookies
Firefox	Firefox 57+ (Win) - Clearing Cache and Cookies	Firefox 21+ (Mac) - Clearing Cache and Cookies
Safari	Safari (Win) - Clearing Cache and Cookies	Safari 10.0.1+ (Mac) - Clearing Cache and Cookies
Internet Explorer 9, 10, & 11	Internet Explorer 9, 10 and 11 (Win) - Clearing Cache and Cookies	None
Microsoft Edge	Edge (Win) - Clearing Cache and Cookies	None
Opera	Opera (Win) - Clearing Cache and Cookies	Opera 28.0 (Mac) - Clearing Cache and Cookies
New Microsoft Edge	New Edge (Win 10, 8, 7, MacOS) - Clearing Cache and Cookies	New Edge (Win 10, 8, 7, MacOS) - Clearing Cache and Cookies

Table with mobile Operating System and corresponding documents on clearing cache and cookies.

Operating System	Document Link
Android	Android (Jellybean) - Clearing Cache and Cookies on Google Chrome
iOS	iOS - Clearing Cache and Cookies
webOS	HP webOS 2.x - Clearing Cache and Cookies
Windows Phone	Internet Explorer (Windows Phone) - Clearing Cache and Cookies

Windows

MacOS

What does it mean when size of a request header field exceeds server limit?

Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. This indicates that the Kerberos Token Size of the users Kerberos token exceeds the limit of the Apache web server.

How do I fix bad request header field too long?

The typical solution is to clear the cache and cookies in your browser..

Open Chrome..

At the top right, select More. or..

Select Settings..

Scroll to “Privacy and security,”.

Click "Clear Browsing data",.

On Time settings, select "All time"..

Click Clear Data..

Select Cookies and other site data..

How do I fix this HTTP error 400 the size of the request headers is too long?

Chosen solution This issues is usually caused by a corrupted cookie that is too long. Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences). If clearing cookies didn't help then it is possible that the cookies.

To fix it delete all the cookies and try visiting the particular website. Cookies too large or corrupted – another possible reason why you are seeing the error on your screen is the cookies for the particular website is too large or the cookies gets corrupted. Clearing the cache data and cookies may work for you.