You can get the same effect using standard web.xml fragment and
without a 3rd party dependency:
<security-constraint>
<web-resource-collection>
<web-resource-name></web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
On Thu, Apr 28, 2016 at 1:12 PM, Lyallex <lyal...@gmail.com> wrote:
> apache-tomcat-7.0.42
> jdk1.8.0_77
> CentOS Linux 7.2.1511
> urlrewritefilter-4.0.3.jar
>
> I'm using the rewrite filter from http://tuckey.org/urlrewrite/
>
> I have a rule, it's supposed to 301 perm-redirect from http to https
>
> <rule>
> <name>seo redirect</name>
> <condition name="host" operator="notequal">^www.example.com</condition>
> <condition name="host" operator="notequal">^localhost</condition>
> <from>^/(.*)</from>
> <to type="permanent-redirect"
> last="true">https://www.example.com/$1</to>
> </rule>
>
> The problem is despite setting the to-type to permanent-redirect I'm
> actually getting a 302 temporary-redirect.
>
> I know this is probably off topic but if anyone has any experience of
> this I'd be gratefull to hear how you solved it
>
> Thanks
>
> lyallex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
