Type Exception Report
Message Invalid character found in the request target [/download/plugin/issuetracker/'.DOKU_URL.'doku.php?id=%27.$ID.%27&do=issuelist_filterlink%27.%27&itl_start=%27.$start.%27&itl_step=%27.$step.%27&itl_next=%27.$next_start.%27&itl_stat_filter=%27.$value[1].%27&itl_sev_filter=%27.$data[%27severity%27].%27&itl__prod_filter=%27.$data[%27product%27].%27&itl_project=%27.$data[%27project%27].%27 ]. 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 [/download/plugin/issuetracker/'.DOKU_URL.'doku.php?id=%27.$ID.%27&do=issuelist_filterlink%27.%27&itl_start=%27.$start.%27&itl_step=%27.$step.%27&itl_next=%27.$next_start.%27&itl_stat_filter=%27.$value[1].%27&itl_sev_filter=%27.$data[%27severity%27].%27&itl__prod_filter=%27.$data[%27product%27].%27&itl_project=%27.$data[%27project%27].%27 ]. 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:867) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1716) 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.