Bosses, save the poor child-CodePudding

Local post upload hasn't any problem, deployed to the server, after the front post upload data, little data is no problem, a point at the wrong

 2020-06-14 00:35:28. 783 INFO - 11996 [nio - 9090 - exec - 1] o.a pache, 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: 416) ~ [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org. Apache. Coyote. Http11. Http11Processor. Service (Http11Processor. Java: 260) ~ [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org. Apache. Coyote. AbstractProcessorLight. Process (AbstractProcessorLight. Java: 65) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org. Apache. Coyote. AbstractProtocol $ConnectionHandler. Process (AbstractProtocol. Java: 868) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun (NioEndpoint. Java: 1639) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org.apache.tomcat.util.net.SocketProcessorBase.run (SocketProcessorBase. Java: 49) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at Java. Util. Concurrent. ThreadPoolExecutor. RunWorker (ThreadPoolExecutor. Java: 1149) [na: 1.8.0 comes with _252] 
The at Java. Util. Concurrent. ThreadPoolExecutor $Worker. The run (ThreadPoolExecutor. Java: 624) [na: 1.8.0 comes with _252] 
At org, apache tomcat. Util. Threads. TaskThread $WrappingRunnable. Run (TaskThread. Java: 61) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at Java. Lang. Thread. The run (Thread. Java: 748) [na: 1.8.0 comes with _252]

Application. The properties configuration below

 
Spring. Servlet. Multipart. Max - file - size=1 
Spring. Servlet. Multipart. Max - request - size=1 
Server. Tomcat. Max - HTTP - form - post - size=1 
Server. The Max - HTTP header - size=10000000 

# HTTPS port number. 
Server port=9090 
# certificate path. 
Server. The SSL. Key - store=/root/springboot/jyc JKS 
# certificate password 
Server. The SSL. Key - store - password=gmk51ng94nh 
# the secret key library type 
Server. The SSL. KeyStoreType=JKS

For a great god, puzzled for several days

CodePudding user response:

How much data is big, big to?

Tomcat front end and what? Tomcat is running on APR mode

CodePudding user response:

A few k data can, almost not more than 10 k,
Tomcat is spring boot built-in
The front is a small program

CodePudding user response:

Dozens of k is washed-up, network and server can be normal use

CodePudding user response:

The HTTPS access HTTP protocol lead to the problems

CodePudding user response:

Magic sword

reference 4th floor dust heart response:

HTTPS access HTTP protocol leads to the question of

That is what little data no problem, and I got in springboot HTTPS ah, small program can only be HTTPS to obtain data

CodePudding user response:

reference 1st floor tianfang response:

data is big, big to?

Tomcat front end and what? Tomcat is running on APR mode

Bosses look at

CodePudding user response:

1. Give it a try in the properties of increasing
Server:
Port: the project port
# this parameter is to solve the problem and new
Tomcat:
Max - HTTP header - size: 8192

2. Change the HTTPS requests to HTTP to give it a try

CodePudding user response:

reference 5 floor @ epicenter of reply:

Quote: magic sword reference 4 floor dust heart response:
HTTPS access HTTP protocol leads to the question of

That why the little data no problem, and I got in springboot HTTPS ah, small program only HTTPS to obtain data

Data size problem caused by the 7th floor

CodePudding user response:

Why don't you take a try catch processing, threw the error message?
Your request is HTTPS???? Try to HTTP,

CodePudding user response:

refer to the original poster @ epicenter of reply:

local post upload hasn't any problem, deployed to the server, after the front post upload data, little data is no problem, a point at the wrong

 2020-06-14 00:35:28. 783 INFO - 11996 [nio - 9090 - exec - 1] o.a pache, 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: 416) ~ [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org. Apache. Coyote. Http11. Http11Processor. Service (Http11Processor. Java: 260) ~ [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org. Apache. Coyote. AbstractProcessorLight. Process (AbstractProcessorLight. Java: 65) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org. Apache. Coyote. AbstractProtocol $ConnectionHandler. Process (AbstractProtocol. Java: 868) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun (NioEndpoint. Java: 1639) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at org.apache.tomcat.util.net.SocketProcessorBase.run (SocketProcessorBase. Java: 49) [tomcat embed - core - 9.0.31. Jar!/: 9.0.31] 
The at Java. Util. Concurrent. ThreadPoolExecutor. RunWorker (ThreadPoolExecutor. Java: 1149) [na: 1.8.0 comes with _252] 
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull