2. 程式人生 > 其它 >Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

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

阿新 • • 發佈：2021-10-19

INFO: 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 the request target. The valid characters are defined in RFC 7230 and RFC 3986
at org.apache.coyote.http11.InternalAprInputBuffer.parseRequestLine(InternalAprInputBuffer.java:240)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1049)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2555)
at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2544)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:722)

解決方案
在tomcat目錄 /conf/catalina.properties 檔案末尾新增下列內容
tomcat.util.http.parser.HttpParser.requestTargetAllow=|{}
org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true

相關推薦

Springboot 報錯 Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

今天看專案日誌，發現報這個異常。 是tomcat容器的問題，因為出現了特殊字元，所以報異常了。Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

SpringBoot 專案遇到錯誤: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

SpringBoot專案腦袋憨憨的遇到了如下報錯， 14:36:42 [http-nio-8691-exec-1] INFOo.a.coyote.http11.Http11Processor - Error parsing HTTP request header

java.lang.IllegalArgumentException: Invalid character found in the request target [請求url].The valid characters are defined in RFC 7230 and RFC 3986 異常處理

java.lang.IllegalArgumentException: Invalid character found in the request target [/wo/insert?id=8&workOrderNo=20200008&workOrderStatus=Status8&creator=zhang&otherFields={name:%22zgx%2

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

INFO: 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 the reques

【解決】The valid characters are defined in RFC 7230 and RFC 3986

【我的問題】使用tomcat-7.0.104版本啟動war包，通過Postman傳送get請求，後臺報錯無效字元

springboot-The valid characters are defined in RFC 7230 and RFC 3986

技術標籤：bugjava 環境 springboot 自帶tomcat 報錯資訊 : java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Bug記錄-Invalid character found in the request target. The valid characters are defined ...

技術標籤：Bug Springboot版本升級2.0以上後 錯誤資訊：Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Invalid character found in the request target [/expert/deleteExpert?idList[]=10&idList[]=11].

技術標籤：vue.jsspring boot 做練習時，遇到個錯誤，記一下 問題 java.lang.IllegalArgumentException: Invalid character found in the request target [/expert/deleteExpert?idList[]=10&idList[]=11].

SpringBoot Undertow/Tomcat報錯：Invalid character | in request-target

本問題核心原因是http協議升級，因為網路安全問題日益嚴峻，RFC組織決定將RFC2616拆分並進行升級。

An invalid character [32] was present in the Cookie value（cookie中的空格問題）

技術標籤：每天的新問題cookie 睡覺前遇bug，真是個好兆頭。。。問題： 程式碼：

瀏覽器報`The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. `問題的解決方案

歡迎訪問moshuying.top檢視更多資訊 詳細錯誤資訊 Access to XMLHttpRequest at \'http://localhost:7894/Login\' from origin \'http://localhost:8080\' has been blocked by CORS policy: Response to preflight

Django REST Framwork 使用 HyperlinkedModelSerializer 報錯： `HyperlinkedIdentityField` requires the request in the serializer context

背景 在專案中使用 Django 的 ORM 功能時，免不了涉及到序列化與反序列化的操作（例如：python物件轉為可用於網路傳輸的位元組序列；HTTP請求中的位元組序列資料轉為python物件）。在Django REST Framwork （以下簡

python 關於request模組post方法上傳檔案報錯"the request was rejected because no multipart boundary was found"

python-關於request模組post方法上傳檔案報錯\"the request was rejected because no multipart boundary was found\"

記一次ElementUI上傳檔案，Current request is not a multipart request與the request was rejected because no multipart boundary was found

1.前端程式碼（ElementUI） <template> <el-upload class=\"upload-demo\" ref=\"upload\" drag action=\"\"

【已解決】前端到後端400錯誤（The server cannot or will not process the request due to...）

看到400錯誤，一般是請求無效。出現該異常一般有三種情況： 第一種情況： 前端提交的內容在後端一般都用String型別來接收，用Date型別接收會報錯。

visual studio (window10) dark主題下修改游標粗細 （visual studio change the thickness of the cursor in dark theme for window10）

本人電腦配置：window10系統， Microsoft Visual Studio 2019 本來在visual studio中設定了 dark 的主題，想說使電腦亮度小點，但是發現游標強度太小，經常看不到，既浪費了尋找游標的時間，又不利於眼睛，所以上網

net core 3 報An unhandled exception occurred while processing the request錯誤

使用net core 開發時報以下錯誤 An unhandled exception occurred while processing the request. Exception: Correlation failed.

【解決】Error from server (ServiceUnavailable): the server is currently unable to handle the request

【問題】部署kube-prometheus使用一段時間，apiserver呼叫特別卡（響應達到15秒），檢視v1beta1.metrics.k8s.io發現無法請求apiserver

Error-IIS-ASP.NET：Unable to make the session state request to the session state server. Please ensure that the ASP.NET State service is started and that the client and server ports are the same.

ylbtech-Error-IIS-ASP.NET：Unable to make the session state request to the session state server. Please ensure that the ASP.NET State service is started and that the client and server ports are the

Fielddata is disabled on text fields by default. Set fielddata=true on [XXX] in order to load fielddata in memory by uninverting the inverted index.

1、報錯資訊： Fielddata is disabled on text fields by default. Set fielddata=true on [createTime] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use