HTTP Status 400 – Bad Request


Type Exception Report

Message Invalid character found in the request target [/index.php?eID=tx_cms_showpic&file=uploads%2Ftx_templavoila%2Fwies_sigrid_300.jpg&md5=86bd1d0bca87f62ef892e652df3a64ec9850dd6c&parameters[0]=YToyOntzOjc6ImJvZHlUYWciO3M6Mzc6Ijxib2R5IHN0eWxlPSJiYWNrZ3JvdW5k&parameters[1]=LWNvbG9yOiNmZmY7Ij4iO3M6NDoid3JhcCI7czozNzoiPGEgaHJlZj0iamF2YXNj&parameters[2]=cmlwdDpjbG9zZSgpOyI%2BIHwgPC9hPiI7fQ%3D%3D ]. The valid characters are defined in RFC 7230 and RFC 3986

Beschreibung 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 [/index.php?eID=tx_cms_showpic&file=uploads%2Ftx_templavoila%2Fwies_sigrid_300.jpg&md5=86bd1d0bca87f62ef892e652df3a64ec9850dd6c&parameters[0]=YToyOntzOjc6ImJvZHlUYWciO3M6Mzc6Ijxib2R5IHN0eWxlPSJiYWNrZ3JvdW5k&parameters[1]=LWNvbG9yOiNmZmY7Ij4iO3M6NDoid3JhcCI7czozNzoiPGEgaHJlZj0iamF2YXNj&parameters[2]=cmlwdDpjbG9zZSgpOyI%2BIHwgPC9hPiI7fQ%3D%3D ]. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:494)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:271)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.base/java.lang.Thread.run(Thread.java:829)

Hinweis Der komplette Stacktrace der Ursache ist in den Server logs zu finden


Apache Tomcat/9.0.62