Browser indirect crash server 400 error troubleshooting analysis

1. Description of the problem phenomenon

Recently, Google Chrome crashed indirectly, the server 400 error, the livebos-tomcat used is 6.5

2. Troubleshooting process

I recorded the date of the error many times, searched the context, and found no error message from the server;
it happened to be planned to upgrade tomcat to livebos-tomcat8.5, so the priority was to upgrade tomcat to 8.5;
after that, the error still occurred, but there was an error message: java.lang.IllegalArgumentException: Request header is too large
Think of the recently developed new function rest method to call the oa interface, the process passes the json string, which may be caused by the long json string;

3. Solutions

Ordinary tomcat

in server.xml

<Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443" maxPostSize="0" maxHttpHeaderSize ="102400"/> 

Add maxHttpHeaderSize="102400"

SpringBoot

Add in the application.properties fileserver.max-http-header-size=102400