HTTP Status 400 – Bad Request


Type Exception Report

Message Invalid character found in the request target [/page-provider/pages/documents/press/release/2017-245-%D0%B1%D0%B0%D0%BD%D0%BA%D0%B0%D1%82%D0%B0-%D0%BE%D1%82-%D0%B5%D1%81-%D0%BE%D1%82%D0%BA%D1%80%D0%B8%D0%B2%D0%B0-%D0%BE%D1%84%D0%B8%D1%81-%D0%B2-%D1%81%D0%BE%D1%84%D0%B8%D1%8F-%D0%B8-%D0%BF%D0%BE%D0%B4%D0%BF%D0%B8%D1%81%D0%B2%D0%B0-%D0%BF%D1%8A%D1%80%D0%B2%D0%B8%D1%8F-%D0%BA%D0%BE%D1%80%D0%BF%D0%BE%D1%80%D0%B0%D1%82%D0%B8%D0%B2%D0%B5%D0%BD-%D0%B7%D0%B0%D0%B5%D0%BC-efsi-%D0%B2-%D0%B1%D1%8A%D0%BB%D0%B3%D0%B0%D1%80%D0%B8%D1%8F?language=en&defaultLanguage=en&url=/en/press/all/2017-245-0xd00xb10xd00xb00xd00xbd0xd00xba0xd00xb00xd10x820xd00xb0-0xd00xbe0xd10x82-0xd00xb50xd10x81-0xd00xbe0xd10x820xd00xba0xd10x800xd00xb80xd00xb20xd00xb0-0xd00xbe0xd10x840xd00xb80xd10x81-0xd00xb2-0xd10x810xd00xbe0xd10x840xd00xb80xd10x8f-0xd00xb8-0xd00xbf0xd00xbe0xd00xb40xd00xbf0xd00xb80xd10x810xd00xb20xd00xb0-0xd00xbf0xd10x8a0xd10x800xd00xb20xd00xb80xd10x8f-0xd00xba0xd00xbe0xd10x800xd00xbf0xd00xbe0xd10x800xd00xb00xd10x820xd00xb80xd00xb20xd00xb50xd00xbd-0xd00xb70xd00xb00xd00xb50xd00xbc-efsi-0xd00xb2-0xd00xb10xd10x8a0xd00xbb0xd00xb30xd00xb00xd10x800xd00xb80xd10x8f ]. 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 [/page-provider/pages/documents/press/release/2017-245-%D0%B1%D0%B0%D0%BD%D0%BA%D0%B0%D1%82%D0%B0-%D0%BE%D1%82-%D0%B5%D1%81-%D0%BE%D1%82%D0%BA%D1%80%D0%B8%D0%B2%D0%B0-%D0%BE%D1%84%D0%B8%D1%81-%D0%B2-%D1%81%D0%BE%D1%84%D0%B8%D1%8F-%D0%B8-%D0%BF%D0%BE%D0%B4%D0%BF%D0%B8%D1%81%D0%B2%D0%B0-%D0%BF%D1%8A%D1%80%D0%B2%D0%B8%D1%8F-%D0%BA%D0%BE%D1%80%D0%BF%D0%BE%D1%80%D0%B0%D1%82%D0%B8%D0%B2%D0%B5%D0%BD-%D0%B7%D0%B0%D0%B5%D0%BC-efsi-%D0%B2-%D0%B1%D1%8A%D0%BB%D0%B3%D0%B0%D1%80%D0%B8%D1%8F?language=en&defaultLanguage=en&url=/en/press/all/2017-245-0xd00xb10xd00xb00xd00xbd0xd00xba0xd00xb00xd10x820xd00xb0-0xd00xbe0xd10x82-0xd00xb50xd10x81-0xd00xbe0xd10x820xd00xba0xd10x800xd00xb80xd00xb20xd00xb0-0xd00xbe0xd10x840xd00xb80xd10x81-0xd00xb2-0xd10x810xd00xbe0xd10x840xd00xb80xd10x8f-0xd00xb8-0xd00xbf0xd00xbe0xd00xb40xd00xbf0xd00xb80xd10x810xd00xb20xd00xb0-0xd00xbf0xd10x8a0xd10x800xd00xb20xd00xb80xd10x8f-0xd00xba0xd00xbe0xd10x800xd00xbf0xd00xbe0xd10x800xd00xb00xd10x820xd00xb80xd00xb20xd00xb50xd00xbd-0xd00xb70xd00xb00xd00xb50xd00xbc-efsi-0xd00xb2-0xd00xb10xd10x8a0xd00xbb0xd00xb30xd00xb00xd10x800xd00xb80xd10x8f ]. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:497)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:932)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1695)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
	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.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.90