Type Exception Report
Message Invalid character found in the request target [/index.php?eID=tx_cms_showpic&file=fileadmin%2Fuser_upload%2Fdownloads_de_graphics%2F2010_11_Konzernumsatz_nach_Regionen.jpg&md5=c5cd5aa0be4a0d00a80422bc66c14650992b24f7¶meters[0]=YTozOntzOjU6IndpZHRoIjtzOjQ6IjYwMG0iO3M6NjoiaGVpZ2h0IjtzOjQ6IjYw¶meters[1]=MG0iO3M6NDoid3JhcCI7czo0NDoiPGEgaHJlZj0iamF2YXNjcmlwdDogd2luZG93¶meters[2]=LmNsb3NlKCk7Ij4gfDwvYT4iO30%3D ]. 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 [/index.php?eID=tx_cms_showpic&file=fileadmin%2Fuser_upload%2Fdownloads_de_graphics%2F2010_11_Konzernumsatz_nach_Regionen.jpg&md5=c5cd5aa0be4a0d00a80422bc66c14650992b24f7¶meters[0]=YTozOntzOjU6IndpZHRoIjtzOjQ6IjYwMG0iO3M6NjoiaGVpZ2h0IjtzOjQ6IjYw¶meters[1]=MG0iO3M6NDoid3JhcCI7czo0NDoiPGEgaHJlZj0iamF2YXNjcmlwdDogd2luZG93¶meters[2]=LmNsb3NlKCk7Ij4gfDwvYT4iO30%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:269) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:895) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1732) 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)
Note The full stack trace of the root cause is available in the server logs.