thale-ete.com Open in urlscan Pro
34.203.85.170  Public Scan

URL: http://thale-ete.com/zcredirect?visitid\=39150282-14ad-11ee-89b4-1297c05830e9&type\=js&browserWidth\=1366&browserHeig...
Submission: On June 27 via manual from IN — Scanned from DE

Form analysis 0 forms found in the DOM

Text Content

HTTP STATUS 400 – BAD REQUEST

--------------------------------------------------------------------------------

Type Exception Report

Message Invalid character found in the request target
[/zcredirect?visitid\=39150282-14ad-11ee-89b4-1297c05830e9&type\=js&browserWidth\=1366&browserHeight\=625&iframeDetected\=false&webdriverDetected\=false
]. 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 [/zcredirect?visitid\=39150282-14ad-11ee-89b4-1297c05830e9&type\=js&browserWidth\=1366&browserHeight\=625&iframeDetected\=false&webdriverDetected\=false ]. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:509)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:513)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:882)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1647)
	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:833)


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

--------------------------------------------------------------------------------