Regarding the new .htaccess Optimization feature, if this is set to DocumentRoot doesn't this interfere with the Optimize Website feature in users cPanels?
The Optimize Website (mod_deflate) adds a .htaccess file into the user's home directory. If AllowOverride is only permitted into individual DocumentRoots, then .htaccess file in the user's home directory will never be read, correct?
Of course, if you use the recommended setting of per home directory, this is not an issue. And that may be the best solution here, just note that if you use per DocumentRoot AllowOverride then you won't be able to use The Optimize Website feature in end-user's cPanels. Otherwise, you would need to revamp the Optimize Website to be enabled per VirtualHost or a flag would have to be set so that subsequent VirtualHosts created under the end-user's account get the appropriate mod_deflate directives set in their .htaccess file.
Would a better solution be to avoid .htaccess files completely? I believe this is what nginx does. Per VirtualHosts directives could be added to /etc/apache2/conf.d/userdata/(std|ssl)/2_4/<user>/<virtualhost> directory structure. The nginx argument is that each web-server request generates more file-system hits as it has to look for .htaccess files every where. I don't know how much of a performance hit this really is, but it makes sense that it would at least take some performance hit.
The Optimize Website (mod_deflate) adds a .htaccess file into the user's home directory. If AllowOverride is only permitted into individual DocumentRoots, then .htaccess file in the user's home directory will never be read, correct?
Of course, if you use the recommended setting of per home directory, this is not an issue. And that may be the best solution here, just note that if you use per DocumentRoot AllowOverride then you won't be able to use The Optimize Website feature in end-user's cPanels. Otherwise, you would need to revamp the Optimize Website to be enabled per VirtualHost or a flag would have to be set so that subsequent VirtualHosts created under the end-user's account get the appropriate mod_deflate directives set in their .htaccess file.
Would a better solution be to avoid .htaccess files completely? I believe this is what nginx does. Per VirtualHosts directives could be added to /etc/apache2/conf.d/userdata/(std|ssl)/2_4/<user>/<virtualhost> directory structure. The nginx argument is that each web-server request generates more file-system hits as it has to look for .htaccess files every where. I don't know how much of a performance hit this really is, but it makes sense that it would at least take some performance hit.
