1. 程式人生 > >解決:Invalid character found in method name. HTTP method names must be tokens

解決:Invalid character found in method name. HTTP method names must be tokens

養成的一個好習慣是,每天早上到公司後都會檢視專案日誌,看看有無異常資料資訊等,今天忽然發現日誌中拋了個這個錯誤(此伺服器上安裝的是Tomcat8):

06-Jul-2018 03:10:34.029 INFO [http-nio-8080-exec-6] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
 java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
	at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:428)
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:684)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:800)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1471)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:748)

這個專案日誌是我開發微信公眾號時部署在伺服器上的,第一次見這個錯誤,百度了下說tomcat的server.xml檔案中加入:

maxHttpHeaderSize="8192"
 <Connector 
     port="8080" 
     protocol="HTTP/1.1"
     connectionTimeout="20000"
     redirectPort="8443" 
     maxHttpHeaderSize="8192"
     URIEncoding="UTF-8" />
奈何無效,發現在我的介面請求(呼叫第三方服務)時是https開頭的,豁然開朗,把https換成http即可。如果你的第三方服務部署的本身就是https的,那你可以通過nginx設定個https代理,或者如果使用HttpClient的方式呼叫的介面,則通過設定SSL證書來支援https請求。這個錯誤也可能是你的jar包衝突引起的,導致不知道載入哪個方法到記憶體中。

相關推薦

解決Invalid character found in method name. HTTP method names must be tokens

養成的一個好習慣是,每天早上到公司後都會檢視專案日誌,看看有無異常資料資訊等,今天忽然發現日誌中拋了個這個錯誤(此伺服器上安裝的是Tomcat8):06-Jul-2018 03:10:34.029 IN

解決Invalid character found in the request target.The valid characters are defined in RFC 7230 and RF

背景 在將tomcat升級到7版後,發現系統的有些功能不能使用了,查詢日誌發現是有些地址直接被tomcat認為存在不合法字元,返回HTTP 400錯誤響應,錯入資訊如下: java.lang.IllegalArgumentException: Invalid c

Tomcat報錯Invalid character found in method name. HTTP method names must be tokens

問題: 報錯資訊:Invalid character found in method name. HTTP method names must be tokens 原因:Tomcat的header緩衝區大小不夠 解決方法:只需要在server.xml中增加maxHt

SpringBootInvalid character found in method name. HTTP method names must be tokens

org pre 應用 設置 http1 sdn pool tor 聲明 問題背景 關於SpringBoot應用掛了很久之後,會發生Invalid character found in method name. HTTP method names must be token

Tomcat 8.5 400錯誤Invalid character found in the request target. 問題解決方法

最近部署專案的時候,由於MIS配置的是Tomcat 8.5的服務端,導致Web應用不正常,報HTTP 400錯誤(Chrome無異常、IE報錯)。問題原因初步判斷為8.5版本的服務端接收請求不會對符號進行轉義,Chrome不異常的原因或許是瀏覽器自身轉義了。具

異常Invalid character found in the request target. The valid characters are defined in RFC 3986

RFC 3986 文件 RFC 3986文件規定,Url中只允許包含英文字母(a-z,A-Z)、數字(0-9)、- _ . ~ 4個特殊字元以及所有保留字元。 RFC3986中指定了以下字元為保留字

URL傳輸異常Invalid character found in the request target

1.異常詳情java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and

解決 Invalid character found in method name. HTTP method names must be tokens 異常信息

img cte rac 9.png tom cat 解決方法 ica ade 一個線上環境出現異常,不是spring boot。 解決方法: server.xml中加上maxHttpHeaderSize="8192" springBoot 1.x則是在appli

Invalid character found in method name. HTTP method names must be tokens

error 緩沖 pan img cut ade odi port col o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header Note: furt

如何在同一臺電腦上同時執行兩個Tomcat(關於Invalid character found in method name.HTTP method names must be token.錯誤資訊)

今天在學習一個專案的時候需要用到Tomcat8,而我的Tomcat版本是7,因為Tomcat7用的久了比較習慣又不想解除安裝,所以打算兩個一起用,在網上查了同一臺電腦上可以執行兩個Tomcat後,就開始部署Tomcat8. 在看了一篇前輩的經驗後將Tomcat8的start

關於Invalid character found in method name. HTTP method names must be tokens

關於這個問題網上的資料很少,估計是很少人遇到這種情況,我遇到的這個情況應該是個神奇的存在。 java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method nam

springboot專案請求報錯Invalid character found in method name. HTTP method names must be tokens

2018-01-26 09:57:23.845 INFO 12872 — [nio-8080-exec-7] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request heade

專案半夜凌晨宕機,報錯Invalid character found in method name. HTTP method names must be tokens|the HTTP protoco

這幾天專案總是在凌晨掛機,檢視日誌發現以下錯誤:Http11Processor - Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will

解決Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 問題

== number keyword 解決辦法 class rac ref request 反斜杠 通過這裏的回答,我們可以知道: Tomcat在 7.0.73, 8.0.39, 8.5.7 版本後,添加了對於http頭的驗證。 具體來說,就是添加了些規則去限制HTTP頭

tomcat請求引數問題解決: Invalid character found in the request target. The valid characters are defined in

背景:研發的同事在測試環境的tomcat發現了一個問題, ‘Note: further occurrences of HTTP header parsing errors will be logg

Invalid character found in the request target , 在SpringBoot2.0.3中的異常解決

異常一:     Invalid character found in method name. HTTP method names must be token 原因:    產生這個問題的原因是頁面表單提交了大量的資料,而這些資料量可能超過了Tomcat 定

問題java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

使用帶有 '[]' 的引數請求介面時,返回如下錯誤 java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230

tomcat7.0.70升級為7.0.76後異常 Invalid character found in the request target. 解決

solr5.3部署在tomcat7.0.70上執行正常,升級為7.0.76之後啟動正常,訪問solr控制檯異常: 三月 28, 2017 2:29:42 下午 org.apache.coyote.http11.AbstractHttp11Processor

java.lang.IllegalArgumentException: Invalid character found in the request target.

bsp exce lan character java invalid nco script follow java.lang.IllegalArgumentException: Invalid character found in the request target.

Invalid character found in the request target The valid cha

分享一下我老師大神的人工智慧教程!零基礎,通俗易懂!http://blog.csdn.net/jiangjunshow 也歡迎大家轉載本篇文章。分享知識,造福人民,實現我們中華民族偉大復興!