-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marc,
On 9/1/2010 7:16 PM, Marc Chamberlin wrote: > [Changing the content-type regular expression pattern] did the trick, > and yes, shtml does not work... But this should be ok for our needs, > our users don't create .shtml files, and this also worked for .jsp > and .htm files as well as .html... Documentation on the Tomcat site > should be updated to discuss this, IMHO. What should be updated? It seems clear to me from the documentation what will happen: " contentType - A regex pattern that must be matched before SSI processing is applied. When crafting your own pattern, don't forget that a mime content type may be followed by an optional character set in the form "mime/type; charset=set" that you must take into account. Default is "text/x-server-parsed-html(;.*)?". " It clearly specifies the default, and tells you what the value will be used for. If the default won't meet your needs, change it to a value that /will/ meet your needs. Standard regular expressions should be acceptable. > And it might be an interesting exercise to figure out how to make > this work for all files if one is looking for exercises... ;-) Try this: <url-pattern>/*</url-pattern> (should definitely work) or <url-pattern>/</url-pattern> (will probably work) plus: contentType=".*" - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkx/AtAACgkQ9CaO5/Lv0PCubgCfdnlZfEaEPuaVI2JHvkRiR26L K5UAnA3bEfiHBe9HZfESB/RqiDiCbf/R =oIA/ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
