本文探讨了经典书籍《servlet与jsp核心编程》中提及的InvokerServlet技术，并解释了为何该技术不再适用于Tomcat 7。文章详细介绍了InvokerServlet的历史背景、存在的安全隐患及其在Tomcat 5.0版本中的弃用过程。此外，还介绍了如何在现代Servlet容器如Tomcat 7.0中使用@WebServlet注解或通过web.xml文件来映射Servlet。
今天看
《servlet与jsp核心编程》，很老的书了，但却是servlet最经典的书籍，里面介绍了一种InvokerServlet的技术，想在tomcat 7中应用，一直没发现为什么，直到在stackOverflow上找到答案：
You're probably confusing with the legacy Tomcat-builtin InvokerServlet which was present in older versions of Apache Tomcat (and still mentioned in poor and outdated tutorials/books). It indeed allowed to invoke servlets like that without the need to map anything. However, it was later confirmed that it was a security hole and vulrenable to attacks. It was disabled and deprecated on Tomcat 5.0 and removed on Tomcat 7.0. In such case, you really need to map your servlet in web.xml (and put it in a package!).
Another source of confusion may be the new Servlet 3.0 @WebServlet annotation. When you're already using a Servlet 3.0 container like Tomcat 7.0, then you could use this annotation to map the servlet without the need to fiddle with web.xml.
《servlet与jsp核心编程》，很老的书了，但却是servlet最经典的书籍，里面介绍了一种InvokerServlet的技术，想在tomcat 7中应用，一直没发现为什么，直到在stackOverflow上找到答案：
You're probably confusing with the legacy Tomcat-builtin InvokerServlet which was present in older versions of Apache Tomcat (and still mentioned in poor and outdated tutorials/books). It indeed allowed to invoke servlets like that without the need to map anything. However, it was later confirmed that it was a security hole and vulrenable to attacks. It was disabled and deprecated on Tomcat 5.0 and removed on Tomcat 7.0. In such case, you really need to map your servlet in web.xml (and put it in a package!).
Another source of confusion may be the new Servlet 3.0 @WebServlet annotation. When you're already using a Servlet 3.0 container like Tomcat 7.0, then you could use this annotation to map the servlet without the need to fiddle with web.xml.
扫一扫
2880
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
