There is no error reported after the spirngboot project is started, but when testing the interface with postman, it is found that there will be intermittent (one good and one bad) errors
Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException : Invalid character found in method name. HTTP method names must be tokens
Simple appearance is also very normal, it is a success, a mistake, make me at a loss.
Looking up the online materials, 98% of them said that the configuration change of the maximum header value of Tomcat would be good, but springboot is built-in Tomcat,
The method of modification is as follows: sever.tomcat.max -http-header-size=8192
But this configuration has been abandoned by the boot project of higher version,
It can be changed to: sever.max -http-header-size=8192
Full of joy, thought that good, and then found No.
The other 2% said it might be related to the HTTPS protocol, so it could be changed to http.
But I started it locally. It’s always http.
After struggling for a long time, I found that the culprit actually added content length to the header when requesting and gave it a fixed value, so I would report an error. Stupid cry~~
As for the function of modifying the max HTTP header size, I set this to 1 and request again to find that the error reported is not the same as my previous one, but:
Error processing request
org.apache.coyote .http11.HeadersTooLargeException: An attempt was made to write more data to the response headers than there was room available in the buffer.
Read More:
- Error parsing HTTP request header Note: further occurrences of HTTP header p
- Tomcat error parsing HTTP request header
- Tomcat error: error parsing HTTP request header
- IIS “Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long.”
- Bad Request – Request Too Long. HTTP Error 400. The size of the request headers is too long
- urlopen error unknown url type:httpë/HTTP Error 400:Bad Request
- HTTP 400 error – bad request
- Router DIO network request: dioerror[ DioErrorType.RESPONSE ]: HTTP status error [400] or [500]
- The solution that ioni cannot use HTTP request after packaging apk
- Resolve git clone error fatal: http request failed
- Git error: http request failed
- Spring MVC error HTTP status 400 – bad request
- The request failed with HTTP status 401: Unauthorized. SSRS 2008
- Android API 27 and above use HTTP protocol request mode
- Failed to open stream: http request failed!
- docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled
- Http Error 12057 (Bug Fix Note)
- Flask Request an extension before_request after_request errorhandler
- Git solves the problem of failed: http request failed
- Error resolution: request execution error. Endpoint = defaultendpoint {serviceurl=‘ http://127.0.0.1 :6668/eureka/}