serverlet 区别_Servlet中/和/*的区别

最新推荐文章于 2022-10-23 16:38:31 发布

摔了个呆萌

最新推荐文章于 2022-10-23 16:38:31 发布

阅读量248

点赞数

文章标签： serverlet 区别

本文链接：https://blog.csdn.net/weixin_42114041/article/details/113021656

版权

本文探讨了Servlet中"/"和"/*"作为路径映射时的区别。当使用"/"作为默认Servlet时，请求的路径信息为null，而Servlet路径包含了预期的路径信息。然而，当使用"/*"时，路径信息变为实际路径，Servlet路径为空。这种差异源自Servlet规范中的路径映射规则，使得在同一URL下，Servlet的行为会根据是否是默认Servlet而不同。

摘要由CSDN通过智能技术生成

转自一位国外哥们儿写的分析，写的很不错：

Let's consider this servlet mapping in web.xml that defines "App" as the default servlet:

App

Now call http://server/context/path/to/test.html. Here are the request properties:

getPathInfo() : null

getServletPath() : "/path/to/test.html"

Why is path info null, and why does the servlet path have what we could have expected to see in path info?

Let's change web.xml like this, so that "App" eats the same URLs but is no more the default servlet:

App

And call again the same http://server/context/path/to/test.html:

getPathInfo() : "/path/to/test.html"

getServletPath() : "" (empty string)

WTF? Is it a bug in the servlet engine? Let's check the servlet specification...

In the "Mapping request to servlets" chapter, the specification of mappings is described:

A string beginning with a ‘/’ character and ending with a ‘/*’ postfix is used for path mapping.

A string beginning with a‘*.’ prefix is used as an extension mapping.

A string containing only the ’/’ character indicates the "default" servlet of the application. In this case the servlet path is the request URI minus the context path and the path info is null.

All other strings are used for exact matches only.

When writing the "/" mapping, we use rule 3, whereas when using the "/*" mapping, we use rule 1.

So that means that a servlet that needs to map a resource according to the request URL must behave differently depending on whether it is defined as the default servlet or mounted to a particular location. What's the reason for this?

分享到：