21-Apr-2024 01:06:39.504 INFO [http-nio-8080-exec-5] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in method name [0x160x030x010x000xea0x010x000x000xe60x030x03X0x8f30xa3$0xbc~0x920xd70xa70x1e0xa350xf2ml0xba0x0a`0xd10xcaM0xe2cuJ0xa00x180x7f]0xb50x02 ]. HTTP method names must be tokens
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:422)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:06:43.137 INFO [http-nio-8080-exec-9] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in the request target [/index.php?m=&c=AjaxPersonal&a=company_focus&company_id[0]=match&company_id[1][0]=aaaaaaa")%20and%20extractvalue(1,concat(0x7e,md5(99999999)))%20--%20a ]. The valid characters are defined in RFC 7230 and RFC 3986
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:497)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:06:43.138 INFO [http-nio-8080-exec-10] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in the request target [/plus/ajax_officebuilding.php?act=key&key=0xe90x8c0xa6%27%20a<>nd%201=2%20un<>ion%20sel<>ect%201,2,3,md5(203353816),5,6,7,8,9%23 ]. The valid characters are defined in RFC 7230 and RFC 3986
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:497)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:07:07.452 WARNING [http-nio-8080-exec-5] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:07:51.912 INFO [http-nio-8080-exec-5] org.apache.tomcat.util.http.parser.Cookie.logInvalidHeader A cookie header was received [publicinquiryurls=http://www-3.ibm.com/services/uddi/inquiryapi!IBM|http://www-3.ibm.com/services/uddi/v2beta/inquiryapi!IBM V2|http://uddi.rte.microsoft.com/inquire!Microsoft|http://services.xmethods.net/glue/inquire/uddi!XMethods|;] that contained an invalid cookie. That cookie will be ignored.
 Note: further occurrences of this error will be logged at DEBUG level.
21-Apr-2024 01:08:39.387 WARNING [http-nio-8080-exec-9] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:09:26.694 WARNING [http-nio-8080-exec-7] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:41:35.077 INFO [http-nio-8080-exec-3] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in the request target [/?id=goby%25{128*128} ]. The valid characters are defined in RFC 7230 and RFC 3986
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:497)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:42:44.422 WARNING [http-nio-8080-exec-3] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:43:12.685 INFO [http-nio-8080-exec-7] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in the request target [/catalog-portal/ui/oauth/verify?error=&deviceUdid=%24%7b"freemarker%2etemplate%2eutility%2eExecute"%3fnew%28%29%28"id"%29%7d ]. The valid characters are defined in RFC 7230 and RFC 3986
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:497)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:43:33.741 WARNING [http-nio-8080-exec-8] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:45:24.524 WARNING [http-nio-8080-exec-5] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:45:35.008 WARNING [http-nio-8080-exec-2] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:46:30.846 WARNING [http-nio-8080-exec-10] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:48:05.526 WARNING [http-nio-8080-exec-6] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:49:28.727 WARNING [http-nio-8080-exec-13] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:50:41.428 INFO [http-nio-8080-exec-3] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in method name [0x160x030x010x000xea0x010x000x000xe60x030x030xcb0xfaTe0xe00x17B0xe30xeb*0xce ]. HTTP method names must be tokens
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:422)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:50:48.300 INFO [http-nio-8080-exec-7] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in the request target [/index.php?m=&c=AjaxPersonal&a=company_focus&company_id[0]=match&company_id[1][0]=aaaaaaa")%20and%20extractvalue(1,concat(0x7e,md5(99999999)))%20--%20a ]. The valid characters are defined in RFC 7230 and RFC 3986
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:497)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:50:48.301 INFO [http-nio-8080-exec-12] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in the request target [/plus/weixin.php?signature=da39a3ee5e6b4b0d3255bfef95601890afd80709\xc3\x97tamp=&nonce= ]. The valid characters are defined in RFC 7230 and RFC 3986
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:497)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:51:24.969 WARNING [http-nio-8080-exec-7] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:51:54.076 INFO [http-nio-8080-exec-6] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
	java.lang.IllegalArgumentException: Invalid character found in the request target [/?id=goby%25{128*128} ]. The valid characters are defined in RFC 7230 and RFC 3986
		at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:497)
		at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:492)
		at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
		at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:934)
		at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1698)
		at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
		at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
		at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63)
		at java.lang.Thread.run(Thread.java:750)
21-Apr-2024 01:52:35.537 WARNING [http-nio-8080-exec-13] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 01:54:05.414 WARNING [http-nio-8080-exec-4] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 02:00:56.684 WARNING [http-nio-8080-exec-9] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 02:03:00.861 WARNING [http-nio-8080-exec-3] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 02:04:49.971 WARNING [http-nio-8080-exec-7] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 02:06:36.556 WARNING [http-nio-8080-exec-13] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
21-Apr-2024 02:06:46.982 WARNING [http-nio-8080-exec-9] org.apache.catalina.webresources.AbstractFileResourceSet.logIgnoredSymlink Resource for web application [] at path [/theme/META-INF/����/META-INF/MANIFEST.MF] was not loaded as the canonical path [/theme/META-INF/????/META-INF/MANIFEST.MF] did not match. Use of symlinks is one possible cause.
