struts中使用UrlRewriteFilter

最新推荐文章于 2016-10-24 13:31:46 发布

原创最新推荐文章于 2016-10-24 13:31:46 发布 · 984 阅读

0 ·

CC 4.0 BY-SA版权

Struts2 专栏收录该内容

45 篇文章

订阅专栏

本文详细介绍了在配置Struts时如何整合UrlRewriteFilter进行URL重写，并通过实例展示了如何配置过滤器以实现URL重写功能。同时，针对配置错误导致的误解，提供了解决方案，帮助开发者正确理解并避免类似问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

配置struts中要加上

<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>

表示先经过UrlRewriteFilter过滤之后，传到struts

<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" 
	xmlns="http://java.sun.com/xml/ns/javaee" 
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
	xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
	http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
  <welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
  </welcome-file-list>

    <!-- struts2过滤器前配置 -重写Url-->
    
  <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>WARN</param-value>
      </init-param>
  </filter>
  
  <filter-mapping>
      <filter-name>UrlRewriteFilter</filter-name>
      <url-pattern>/*</url-pattern>
  </filter-mapping>
   
   <!-- struts2过滤器-->
  <filter>
    <filter-name>struts2</filter-name>
    <filter-class>org.apache.struts2.dispatcher.FilterDispatcher</filter-class>   
  </filter>
  <filter-mapping>
     <filter-name>struts2</filter-name>
     <url-pattern>/*</url-pattern>
      <dispatcher>REQUEST</dispatcher>  
      <dispatcher>FORWARD</dispatcher>  
      <dispatcher>INCLUDE</dispatcher>
  </filter-mapping>
  
 
</web-app>

之后可以，配置urlrewrite， http://httpd.apache.org/docs/2.0/misc/rewriteguide.html，有好多例子

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE urlrewrite PUBLIC "-//tuckey.org//DTD UrlRewrite 2.6//EN"
        "http://tuckey.org/res/dtds/urlrewrite2.6.dtd">

<urlrewrite>

<!-- 
    <rule>
        <note>
            The rule means that requests to /test/status/ will be redirected to /rewrite-status
            the url will be rewritten.
        </note>
        <from>/test/status/</from>
        <to type="redirect">%{context-path}/rewrite-status</to>
    </rule>
    <outbound-rule>
        <note>
            The outbound-rule specifies that when response.encodeURL is called (if you are using JSTL c:url)
            the url /rewrite-status will be rewritten to /test/status/.

            The above rule and this outbound-rule means that end users should never see the
            url /rewrite-status only /test/status/ both in thier location bar and in hyperlinks
            in your pages.
        </note>
        <from>/rewrite-status</from>
        <to>/test/status/</to>
    </outbound-rule>
 -->

    <!--

    INSTALLATION

        in your web.xml add...

        <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>WARN</param-value>
            </init-param>
        </filter>
        <filter-mapping>
            <filter-name>UrlRewriteFilter</filter-name>
            <url-pattern>/*</url-pattern>
        </filter-mapping>

     EXAMPLES

     Redirect one url
        <rule>
            <from>/some/old/page.html</from>
            <to type="redirect">/very/new/page.html</to>
        </rule>

    Redirect a directory
        <rule>
            <from>/some/olddir/(.*)</from>
            <to type="redirect">/very/newdir/$1</to>
        </rule>

    Clean a url
        <rule>
            <from>/products/([0-9]+)</from>
            <to>/products/index.jsp?product_id=$1</to>
        </rule>
    eg, /products/1234 will be passed on to /products/index.jsp?product_id=1234 without the user noticing.

    Browser detection
        <rule>
            <condition name="user-agent">Mozilla/[1-4]</condition>
            <from>/some/page.html</from>
            <to>/some/page-for-old-browsers.html</to>
        </rule>
    eg, will pass the request for /some/page.html on to /some/page-for-old-browsers.html only for older
    browsers whose user agent srtings match Mozilla/1, Mozilla/2, Mozilla/3 or Mozilla/4.

    -->

<!--  
        <rule>
            <from>/jsp/2$</from>
            <to>/index2.jsp</to>
        </rule>
     -->   
        <rule>
            <from>/page$</from>
            <to>/pageAction!displayHomepage</to>
        </rule>
        <rule>
            <from>/user$</from>
            <to>/pageAction!displayUserHomepage.action</to>
        </rule>

</urlrewrite>

但是有一个地方需要注意的是action配置的时候

<action name="pageAction" class="pageAction" method="displayUserHomepage">
	      <exception-mapping result="error" exception="java.lang.Exception"/>
	      <result name="error">/index3.jsp</result>
	   </action>

如上，会报错 The requested resource (There is no Action mapped for namespace / and action name index3.jsp.) is not available.

找了好久，原来是配置struts时加上了，之后，就把index3.jsp当做是了一个action

<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>

解决的方法是，配置struts时，

将

<filter-mapping>
     <filter-name>struts2</filter-name>
     <url-pattern>/*</url-pattern>
      <dispatcher>REQUEST</dispatcher>  
      <dispatcher>FORWARD</dispatcher>  
      <dispatcher>INCLUDE</dispatcher>
  </filter-mapping>

改成,这样之后过滤action后缀的，不会处理jsp

<filter-mapping>
     <filter-name>struts2</filter-name>
     <url-pattern>/*.action</url-pattern>
      <dispatcher>REQUEST</dispatcher>  
      <dispatcher>FORWARD</dispatcher>  
      <dispatcher>INCLUDE</dispatcher>
  </filter-mapping>