HTTP Status 400 – Bad Request


Type Exception Report

Message Invalid character found in the request target [/fukunavi/controller?actionID=hyk&cmd=hyklstdtldigest&BEF_PRC=hyk&HYK_ID=2017002519&HYK_ID1=&HYK_ID2=&HYK_ID3=&HYK_ID4=&HYK_ID5=&JGY_CD1=&JGY_CD2=&JGY_CD3=&JGY_CD4=&JGY_CD5=&SCHSVCSBRCD=&SVCDBRCD=&PTN_CD=&SVCSBRCDALL=&SVCSBRCD=342&AREA1=&AREA2=&AREA3=&HYK_YR=&SCHHYK_YR=&NAME=&JGY_CD=1311201778&MODE=multi&DVS_CD=&SVCDBR_CD=&SVCSBR_CD=&ROW=0&FROMDT=&SCH_ACTION=hyklst&KOHYO=&GEN=&HYKNEN=&LISTSVC=&ORDER=&HYK_DTL_CHK=&PRMCMT_CHK=&HYK_CHK=&JGY_CHK=&SVC_CHK=&DIG_MOVE_FLG=&MLT_SVCSBR_CD1=&MLT_SVCSBR_CD2=&MLT_SVCSBR_CD3=&MLT_SVCSBR_CD4=&MLT_SVCSBR_CD5=&MLT_SVCSBR_CD6=&MLT_SVCSBR_CD7=&MLT_SVCSBR_CD8=&COLOR_FLG=&COLOR_HYK_ID=&BEFORE_FLG=&MLT_DTL_SVCSBR_CD1=&MLT_DTL_SVCSBR_CD2=&MLT_DTL_SVCSBR_CD3=&MLT_DTL_SVCSBR_CD4=&MLT_DTL_SVCSBR_CD5=&MLT_DTL_SVCSBR_CD6=&MLT_DTL_SVCSBR_CD7=&MLT_DTL_SVCSBR_CD8=&HIKAKU_SVCSBRCD=&TELOPN001_NO1=&TELOPN001_NO2=&TELOPN001_NO3=&TELOPN002_NO1=&TELOPN002_NO2=&TELOPN002_NO3=&TELOPN003_NO1=&TELOPN003_NO2=&TELOPN003_NO3=&S_MODE=name&MLT_AREA=&H_NAME=&J_NAME=%C9N%C9%E5%C9C%C9W%C5[%C9L%C9%C9%C9b%C9c&SVCDBR_CD=&STEP_SVCSBRCD=]. The valid characters are defined in RFC 7230 and RFC 3986

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Invalid character found in the request target [/fukunavi/controller?actionID=hyk&cmd=hyklstdtldigest&BEF_PRC=hyk&HYK_ID=2017002519&HYK_ID1=&HYK_ID2=&HYK_ID3=&HYK_ID4=&HYK_ID5=&JGY_CD1=&JGY_CD2=&JGY_CD3=&JGY_CD4=&JGY_CD5=&SCHSVCSBRCD=&SVCDBRCD=&PTN_CD=&SVCSBRCDALL=&SVCSBRCD=342&AREA1=&AREA2=&AREA3=&HYK_YR=&SCHHYK_YR=&NAME=&JGY_CD=1311201778&MODE=multi&DVS_CD=&SVCDBR_CD=&SVCSBR_CD=&ROW=0&FROMDT=&SCH_ACTION=hyklst&KOHYO=&GEN=&HYKNEN=&LISTSVC=&ORDER=&HYK_DTL_CHK=&PRMCMT_CHK=&HYK_CHK=&JGY_CHK=&SVC_CHK=&DIG_MOVE_FLG=&MLT_SVCSBR_CD1=&MLT_SVCSBR_CD2=&MLT_SVCSBR_CD3=&MLT_SVCSBR_CD4=&MLT_SVCSBR_CD5=&MLT_SVCSBR_CD6=&MLT_SVCSBR_CD7=&MLT_SVCSBR_CD8=&COLOR_FLG=&COLOR_HYK_ID=&BEFORE_FLG=&MLT_DTL_SVCSBR_CD1=&MLT_DTL_SVCSBR_CD2=&MLT_DTL_SVCSBR_CD3=&MLT_DTL_SVCSBR_CD4=&MLT_DTL_SVCSBR_CD5=&MLT_DTL_SVCSBR_CD6=&MLT_DTL_SVCSBR_CD7=&MLT_DTL_SVCSBR_CD8=&HIKAKU_SVCSBRCD=&TELOPN001_NO1=&TELOPN001_NO2=&TELOPN001_NO3=&TELOPN002_NO1=&TELOPN002_NO2=&TELOPN002_NO3=&TELOPN003_NO1=&TELOPN003_NO2=&TELOPN003_NO3=&S_MODE=name&MLT_AREA=&H_NAME=&J_NAME=%C9N%C9%E5%C9C%C9W%C5[%C9L%C9%C9%C9b%C9c&SVCDBR_CD=&STEP_SVCSBRCD=]. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:504)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:503)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1634)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:748)

Note The full stack trace of the root cause is available in the server logs.


Apache Tomcat/8.5.61