Type Exception Report
Message Invalid character found in the request target [/search/node?field_writer_name_tag_tid=%ED%98%84%EC%A7%84%EA%B1%B4,%EC%9D%B4%ED%9A%A8%EC%84%9D,%EA%B9%80%EB%8F%99%EB%A6%AC,%EC%86%90%EC%86%8C%ED%9D%AC,%ED%95%9C%EB%AC%B4%EC%84%9D,%EA%B0%95%EC%8B%A0%EC%9E%AC,%EC%84%9C%EA%B8%B0%EC%9B%90,%EC%98%A4%EC%83%81%EC%9B%90,%EC%B5%9C%EC%9D%B8%ED%9B%88,%EB%B0%95%EC%99%84%EC%84%9C,%ED%99%A9%EC%84%9D%EC%98%81&type[]=abroad_news ]. 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_writer_name_tag_tid=%ED%98%84%EC%A7%84%EA%B1%B4,%EC%9D%B4%ED%9A%A8%EC%84%9D,%EA%B9%80%EB%8F%99%EB%A6%AC,%EC%86%90%EC%86%8C%ED%9D%AC,%ED%95%9C%EB%AC%B4%EC%84%9D,%EA%B0%95%EC%8B%A0%EC%9E%AC,%EC%84%9C%EA%B8%B0%EC%9B%90,%EC%98%A4%EC%83%81%EC%9B%90,%EC%B5%9C%EC%9D%B8%ED%9B%88,%EB%B0%95%EC%99%84%EC%84%9C,%ED%99%A9%EC%84%9D%EC%98%81&type[]=abroad_news ]. 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.