-
-
Notifications
You must be signed in to change notification settings - Fork 212
mod_filter issue #5015
Comments
As far as I remember (it is in the other ticket somewhere), the code we have now is compatible with all Apache versions, because some of the legacy things have not been removed although they were said to be. Do we need this change then? |
This could very well be true, however, for (legacy) server environments without the |
So how should the whole code block look like then? Isn't |
That's true as well. Perhaps we should only provide a comment to explain the problem. |
Right now we are pretty much using the HTML5Boilerplate solution and if they are happy with it, I am too :) |
Should we consider adding a
<IfModule !mod_filter.c>
condition to our.htaccess.default
to address "legacy" Apache versions, too?The
AddOutputFilterByType
directive was moved into themod_filter
module for Apache ≥ 2.3.7. Before, this directive was available directly from the Apache core module. That said, if we have a server environment running e.g. Apache 2.2.x and nomod_filter.c
available (or enabled), the entire condition is skipped and thus noAddOutputFilterByType
directives are applied.https://github.com/contao/core/blob/master/.htaccess.default#L72
http://uberspace.de/dokuwiki/webserver:htaccess#kompression
h5bp/html5-boilerplate#1173
http://httpd.apache.org/docs/2.0/mod/core.html#addoutputfilterbytype
http://httpd.apache.org/docs/2.4/mod/mod_filter.html#addoutputfilterbytype
The text was updated successfully, but these errors were encountered: