There are several filter init parameters which can be used to configure the behaviour of the SSI filter.<\/p>\n
contentType – <\/strong>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(;.*)?”.<\/p>\n debug –<\/strong> Debugging detail level for messages logged by this servlet. Default 0.<\/p>\n expires – <\/strong>The number of seconds before a page with SSI directives will expire. Default behaviour is for all SSI directives to be evaluated for every request.<\/p>\n isVirtualWebappRelative –<\/strong> Should “virtual” SSI directive paths be interpreted as relative to the context root, instead of the server root? Default false.<\/p>\n allowExec – <\/strong>Is the exec command enabled? Default is false.<\/p>\n","protected":false},"excerpt":{"rendered":" There are several filter init parameters which can be used to configure the behaviour of the SSI filter. 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…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"categories":[8678],"tags":[8763],"class_list":["post-75652","page","type-page","status-publish","hentry","category-tomcat","tag-filter-configuration"],"acf":[],"yoast_head":"\n