使用了urlrewriter,但是发现有些问题,配置如下:
2.4版本的servlet规范在部属描述符中新增加了一个<dispatcher>元素,这个元素有四个可能的值:即REQUEST,FORWARD,INCLUDE和ERROR,可以在一个<filter-mapping>元素中加入任意数目的<dispatcher>,使得filter将会作用于直接从客户端过来的request,通过forward过来的request,通过include过来的request和通过<error-page>过来的request。如果没有指定任何< dispatcher >元素,默认值是REQUEST。
下面几个列子说明一下它的用法:
例1:
这种情况下,过滤器将会作用于直接从客户端发过来的以/person/…开始的请求。因为这里没有制定任何的< dispatcher >元素,默认值是REQUEST。
例2:
截获以request dispatcher的include方法传递过来的对ProductServlet的请求
例3:
在这种情况下,如果请求是以/person/…开头的,并且是通过request dispatcher的forward方法传递过来或者直接从客户端传递过来的,则必须经过这个过滤器。
<!--
Code highlighting produced by Actipro CodeHighlighter (freeware)
http://www.CodeHighlighter.com/
--> < filter >
< filter-name > UrlRewriteFilter </ filter-name >
< filter-class >
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter </ filter-class >
< init-param >
< param-name > logLevel </ param-name >
< param-value > TRACE </ param-value >
</ init-param >
</ filter >
< filter-mapping >
< filter-name > UrlRewriteFilter </ filter-name >
< url-pattern > *.do </ url-pattern >
</ filter-mapping >
Code highlighting produced by Actipro CodeHighlighter (freeware)
http://www.CodeHighlighter.com/
--> < filter >
< filter-name > UrlRewriteFilter </ filter-name >
< filter-class >
org.tuckey.web.filters.urlrewrite.UrlRewriteFilter </ filter-class >
< init-param >
< param-name > logLevel </ param-name >
< param-value > TRACE </ param-value >
</ init-param >
</ filter >
< filter-mapping >
< filter-name > UrlRewriteFilter </ filter-name >
< url-pattern > *.do </ url-pattern >
</ filter-mapping >
2.4版本的servlet规范在部属描述符中新增加了一个<dispatcher>元素,这个元素有四个可能的值:即REQUEST,FORWARD,INCLUDE和ERROR,可以在一个<filter-mapping>元素中加入任意数目的<dispatcher>,使得filter将会作用于直接从客户端过来的request,通过forward过来的request,通过include过来的request和通过<error-page>过来的request。如果没有指定任何< dispatcher >元素,默认值是REQUEST。
下面几个列子说明一下它的用法:
例1:
<!--
Code highlighting produced by Actipro CodeHighlighter (freeware)
http://www.CodeHighlighter.com/
--> < filter-mapping > //过滤器的映射
< filter-name > Logging Filter </ filter-name > //过滤器的名字
< url-pattern > /person/* </ url-pattern > //截获以person为开头的url
</ filter-mapping >
Code highlighting produced by Actipro CodeHighlighter (freeware)
http://www.CodeHighlighter.com/
--> < filter-mapping > //过滤器的映射
< filter-name > Logging Filter </ filter-name > //过滤器的名字
< url-pattern > /person/* </ url-pattern > //截获以person为开头的url
</ filter-mapping >
这种情况下,过滤器将会作用于直接从客户端发过来的以/person/…开始的请求。因为这里没有制定任何的< dispatcher >元素,默认值是REQUEST。
例2:
<!--
Code highlighting produced by Actipro CodeHighlighter (freeware)
http://www.CodeHighlighter.com/
--> < filter-mapping >
< filter-name > Logging Filter </ filter-name > //过滤器的名字
< servlet-name > LogServlet </ servlet-name > //截获名字为LogServlet的servletl
< dispatcher > INCLUDE </ dispatcher >
</filter-mapping>
Code highlighting produced by Actipro CodeHighlighter (freeware)
http://www.CodeHighlighter.com/
--> < filter-mapping >
< filter-name > Logging Filter </ filter-name > //过滤器的名字
< servlet-name > LogServlet </ servlet-name > //截获名字为LogServlet的servletl
< dispatcher > INCLUDE </ dispatcher >
</filter-mapping>
截获以request dispatcher的include方法传递过来的对ProductServlet的请求
例3:
<!--
Code highlighting produced by Actipro CodeHighlighter (freeware)
http://www.CodeHighlighter.com/
--> < filter-mapping >
< filter-name > Logging Filter </ filter-name >
< url-pattern > /person/* </ url-pattern >
< dispatcher > FORWARD </ dispatcher >
< dispatcher > REQUEST </ dispatcher >
</ filter-mapping >
Code highlighting produced by Actipro CodeHighlighter (freeware)
http://www.CodeHighlighter.com/
--> < filter-mapping >
< filter-name > Logging Filter </ filter-name >
< url-pattern > /person/* </ url-pattern >
< dispatcher > FORWARD </ dispatcher >
< dispatcher > REQUEST </ dispatcher >
</ filter-mapping >
在这种情况下,如果请求是以/person/…开头的,并且是通过request dispatcher的forward方法传递过来或者直接从客户端传递过来的,则必须经过这个过滤器。