On Thu, Sep 2, 2010 at 12:24 AM, Marc Chamberlin
<[email protected]> wrote:
> On 9/1/2010 1:46 PM, Wesley Acheson wrote:
>>
>> On Wed, Sep 1, 2010 at 10:13 PM, Marc Chamberlin
>> <[email protected]> wrote:
>> Have you tried modifying this section?
>>
>> <filter-mapping>
>> <filter-name>ssi</filter-name>
>> <url-pattern>*.shtml</url-pattern>
>> </filter-mapping>
>>
>>
>> To look more like this
>>
>> <filter-mapping>
>> <filter-name>ssi</filter-name>
>> <url-pattern>*</url-pattern>
>> </filter-mapping>
>
> Thanks Wesley for taking the time to answer, much appreciated! Yes, I have
> tried this filter mapping / url-pattern with no joy. Also have tried a
> url-pattern of *.html and no joy either....
>>
>> Also change the section
>> <init-param>
>> <param-name>contentType</param-name>
>> <param-value>text/x-server-parsed-html(;.*)?</param-value>
>> </init-param>
>>
>> The param-value must be a regular expression that will meet the
>> following mime types
>> text/x-server-parsed-html or text/html. My regular expressions aren't
>> great so I'll leave that for an exercise.
Hi Marc,
Okay the suggestion was to do these two changes in conjunction with
one another as I understand it the mapping says what URLS this is
applied on and the init-param says what the mime type has to be.
To test simply, just to see if we are on the right track try chaning
the filter-mapping as above, but change
<init-param>
<param-name>contentType</param-name>
<param-value>text/x-server-parsed-html(;.*)?</param-value>
</init-param>
to
<init-param>
<param-name>contentType</param-name>
<param-value>text/html(;.*)?</param-value>
</init-param>
And test it on a html page. If I'm right it will work but shtml won't.
Really need a regularexpression writer.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
