Springboot pack after the release, a while will be the following error
The 2019-07-02 15:35:24. 046 [HTTP - nio - 8081 - exec - 6] INFO org. Apache. Coyote. Http11. Http11Processor - Error parsing the HTTP request header
Note: further occurrences of the HTTP request parsing errors will be logged at the DEBUG level.
Java. Lang. IllegalArgumentException: Invalid character found in method name. The HTTP method names must be tokens
The at org. Apache. Coyote. Http11. Http11InputBuffer. ParseRequestLine (Http11InputBuffer. Java: 414)
At org. Apache. Coyote. Http11. Http11Processor. Service (294) Http11Processor. Java:
The at org. Apache. Coyote. AbstractProcessorLight. Process (AbstractProcessorLight. Java: 66)
The at org. Apache. Coyote. AbstractProtocol $ConnectionHandler. Process (AbstractProtocol. Java: 791)
At org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun NioEndpoint. Java: (1417)
The at org.apache.tomcat.util.net.SocketProcessorBase.run (SocketProcessorBase. Java: 49)
The at Java. Util. Concurrent. ThreadPoolExecutor. RunWorker (ThreadPoolExecutor. Java: 1149)
The at Java. Util. Concurrent. ThreadPoolExecutor $Worker. The run (ThreadPoolExecutor. Java: 624)
At org, apache tomcat. Util. Threads. TaskThread $WrappingRunnable. Run (61) TaskThread. Java:
The at Java. Lang. Thread. The run (Thread. Java: 748)



Online HTTPS speak a lot, or port error, or configuration, in accordance with the relevant solution all tried a lot, not a useful
I didn't use HTTPS requests, port has not been occupied, exactly where the problem is? Look at the great god people out and have a look

CodePudding user response:

Domain names are not SSL certificate

CodePudding user response:

reference 1st floor IsaacOstars response:

if domain name not SSL certification

My domain is not SSL certificate

CodePudding user response:

refer to the original poster yangchun1213 response:

springboot pack after the release, a while will be the following error
The 2019-07-02 15:35:24. 046 [HTTP - nio - 8081 - exec - 6] INFO org. Apache. Coyote. Http11. Http11Processor - Error parsing the HTTP request header
Note: further occurrences of the HTTP request parsing errors will be logged at the DEBUG level.
Java. Lang. IllegalArgumentException: Invalid character found in method name. The HTTP method names must be tokens
The at org. Apache. Coyote. Http11. Http11InputBuffer. ParseRequestLine (Http11InputBuffer. Java: 414)
At org. Apache. Coyote. Http11. Http11Processor. Service (294) Http11Processor. Java:
The at org. Apache. Coyote. AbstractProcessorLight. Process (AbstractProcessorLight. Java: 66)
The at org. Apache. Coyote. AbstractProtocol $ConnectionHandler. Process (AbstractProtocol. Java: 791)
At org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun NioEndpoint. Java: (1417)
The at org.apache.tomcat.util.net.SocketProcessorBase.run (SocketProcessorBase. Java: 49)
The at Java. Util. Concurrent. ThreadPoolExecutor. RunWorker (ThreadPoolExecutor. Java: 1149)
The at Java. Util. Concurrent. ThreadPoolExecutor $Worker. The run (ThreadPoolExecutor. Java: 624)
At org, apache tomcat. Util. Threads. TaskThread $WrappingRunnable. Run (61) TaskThread. Java:
The at Java. Lang. Thread. The run (Thread. Java: 748)



Online HTTPS speak a lot, or port error, or configuration, in accordance with the relevant solution all tried a lot, not a useful
I didn't use HTTPS requests, port has not been occupied, exactly where the problem is? Look at the great god people come out to see

See a problem might be request header is set too small? You can be in the server. The XML Connector label setting of try once more, passing a SSL listener that is commented out,
Can't solve it suggest you change a high version of the tomcat can solve,

CodePudding user response:

Project is released to the outside network? If this can not ignore, a lot of hackers often use software to bump interface

CodePudding user response:

references 4 floor stray yards farmers reply:

project is released to the outside network? If this can not ignore, a lot of hackers often use software to bump interface

Is that so? It is no wonder that a period of time there is no problem, after I modify the port today, look at the appear this situation again

CodePudding user response:

Posts don't sink,,,,

CodePudding user response:

Look at this post very detailed at https://blog.csdn.net/jimiao_xxxx/article/details/115299168