The Content-Type matching uses the HTTP header, not the HTML meta tag.
On Wed, Oct 2, 2013 at 8:59 AM, John Pollard <j...@pollardweb.com> wrote: > Does anyone use the pagespeed apache module with WO apps? > > After installing, this fails to trigger my pages: > > AddOutputFilterByType MOD_PAGESPEED_OUTPUT_FILTER text/html > > despite the following being in the generated pages: > > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> > > replacing the above with: > > SetOutputFilter MOD_PAGESPEED_OUTPUT_FILTER > > works ok, but I can't be indiscriminate with what gets passed through > pagespeed > > I asked a very similar question on this list about a year ago wrt > mod_deflate, but the same workaround is not possible this time > > Does anyone know why apache (2.2) might not trigger based on the text/html > Content-Type directive? > > Many thanks > John > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > > https://lists.apple.com/mailman/options/webobjects-deploy/johnthuss%40gmail.com > > This email sent to johnth...@gmail.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
