Login/Register
  • Home
  • Community
  • Knowledge
  • Technical Docs
  • RWS Support Policy
  • Trados Studio Licensing Help
  • Login for Support
Back to Search Results

WorldServer - HTTP Status 400 - Bad request 'Request header is too large' when trying to navigate Projects or performing other actions

000012216 |5/19/2022 5:24 PM
Scope/Environment
WorldServer
Question
When trying to reach a Projects page in WorldServer using the ws-legacy User Interface or completing a human step, a user receives the error below. 

HTTP Status 400 – Bad Request
Type Exception Report

Message Request header is too large

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Request header is too large


404Error

Note: another user logs in with the same credentials and does not receive the error.

The error can also be found on the server in W:\WorldServer\tomcat\logs\catalina.xxxx.log. (Note: path might vary on environment that are not hosted by SDL).
Answer
This issue happens mostly using the Chrome browser. These are the resolutions:

1- Clear the browser cache resolves the issue. Follow these steps:
  1. In Chrome, go to the top right with the three dots and select Settings->Privacy and Security->Clear browsing data
  2. Select at least Browsing history, cookies, other site data and cached images and files. 
  3. Select at least the last 24 hours for Time range, if that doesn't work, try a longer period of time.
  4. Once the cache has been cleared, close Chrome, re-open it and attempt to reach WorldServer again.
  5. If the above doesn't work, go back to the Clear browsing data page, only select the cookies, and delete going back to all time.  Then try #4 again.
User-added image

If it happens with another Browser such as Mozilla Firefox, try to clear the Cache and restart the Browser.

2- In Chrome, another workaround is to open a New Incognito window and log in to WorldServer in "incognito" mode. Once logged in, repeate the actions that led to the error. You won't encounter the error anymore.

User-added image


 
Reference
Send Article Feedback
RWS Machine Translation Translation Software Language Services Content Management
All Contents Copyright © RWS.
COPYRIGHT PRIVACY POLICY COOKIE POLICY TERMS AND CONDITIONS