Peter,
On 12/29/23 07:56, Peter Rader wrote:
having a URL like this:
https://localhost:8443/index.html works perfect. This is my mapping:
<servlet-mapping>
<servlet-name>Nano-Nano-Servlet</servlet-name>
<url-pattern>/index.html</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>Nano-Nano-Servlet</servlet-name>
<url-pattern>*.ts</url-pattern>
</servlet-mapping>
Unfortunately this URI does not load (because of the %-sign):
https://localhost:8443/@rm%2fmodel.ts
It gives a http-status:400 having the message "Invalid URI: [noSlash]"
What's the use-case for having a client use a %-encoded / in your URL?
That kind of thing is usually evidence of a hacking attempt, which is
why Tomcat returns a 400 response.
https://stackoverflow.com/questions/19576777/why-does-apache-tomcat-handle-encoded-slashes-2f-as-path-separators
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
