HTTP Status 400 – Bad Request


Type Exception Report

Message Invalid character found in the request target [/search/node?field_author_korean_tid=%EC%9C%A4%EB%8C%80%EB%85%95,%EA%B9%80%EC%A4%91%ED%98%81,%EC%A0%95%EC%A7%80%EC%95%84,%EA%B0%95%EC%98%81%EC%88%99,%EA%B9%80%EC%9D%B8%EC%88%99,%EA%B9%80%EC%9E%AC%EC%98%81,%EC%9E%A5%EB%AF%B8%EA%B2%BD,%EC%A0%84%EC%84%B1%ED%83%9C,%EB%82%98%ED%9D%AC%EB%8D%95,%ED%99%A9%EB%B3%91%EC%8A%B9,%EA%B3%A0%ED%98%95%EB%A0%AC,%EA%B9%80%EC%8B%A0%EC%9A%A9,%EA%B9%80%ED%96%89%EC%88%99,%EA%B9%80%EA%B7%BC,%EC%86%A1%EC%B0%AC%ED%98%B8,%EC%B5%9C%EC%A0%95%EB%A1%80,%EC%9D%B4%EB%AC%B8%EC%9E%AC,%EC%9E%A5%EC%84%9D%EB%82%A8,%EB%AC%B8%ED%83%9C%EC%A4%80,%EA%B9%80%EA%B2%BD%EC%A3%BC,%EC%95%88%ED%98%84%EB%AF%B8,%EA%B9%80%EC%82%AC%EC%9D%B8&type[]=bibliography ]. 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 [/search/node?field_author_korean_tid=%EC%9C%A4%EB%8C%80%EB%85%95,%EA%B9%80%EC%A4%91%ED%98%81,%EC%A0%95%EC%A7%80%EC%95%84,%EA%B0%95%EC%98%81%EC%88%99,%EA%B9%80%EC%9D%B8%EC%88%99,%EA%B9%80%EC%9E%AC%EC%98%81,%EC%9E%A5%EB%AF%B8%EA%B2%BD,%EC%A0%84%EC%84%B1%ED%83%9C,%EB%82%98%ED%9D%AC%EB%8D%95,%ED%99%A9%EB%B3%91%EC%8A%B9,%EA%B3%A0%ED%98%95%EB%A0%AC,%EA%B9%80%EC%8B%A0%EC%9A%A9,%EA%B9%80%ED%96%89%EC%88%99,%EA%B9%80%EA%B7%BC,%EC%86%A1%EC%B0%AC%ED%98%B8,%EC%B5%9C%EC%A0%95%EB%A1%80,%EC%9D%B4%EB%AC%B8%EC%9E%AC,%EC%9E%A5%EC%84%9D%EB%82%A8,%EB%AC%B8%ED%83%9C%EC%A4%80,%EA%B9%80%EA%B2%BD%EC%A3%BC,%EC%95%88%ED%98%84%EB%AF%B8,%EA%B9%80%EC%82%AC%EC%9D%B8&type[]=bibliography ]. 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.lang.Thread.run(Thread.java:748)

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


Apache Tomcat/9.0.62