Logging for redirects between apache 2.2 and apache 2.4

apache-2.4mod-rewrite

ran into an issue here that I am finding very little information on and I am hoping someone may be able to shed some light on it.

I was upgrading a server from apache 2.2 to apache 2.4. Within that server, there was a setup for redirecting to other locally hosted sites within the apache config. The problem with the setup is that it was using the directive RewriteLog and RewriteLogLevel to redirect output to a separate log other than the usual host logs. Reading up on the changes between the two versions of apache (2.2 vs. 2.4) it looks like RewriteLog and RewriteLogLevel have been deprecated and replaced with mod_rewrite. That is all well and good but I am not finding mention of a function within mod_rewrite that allows me to define a separate log file to write out the rewrite calls for that site within apache. Does anyone have any helpful hints or can point me in a good direction that may explain how to redirect output to a new log within mod_rewrite?

Thanks!

Best Answer

You probably missed the correct parts to read. http://httpd.apache.org/docs/current/mod/mod_rewrite.html#logging

So, the functionality is now replaced by the standard per-module logger. Documentation at https://httpd.apache.org/docs/2.4/mod/core.html#loglevel

In a nutshell, everything goes to the ErrorLog and you'll need to filter the events by yourself using grep or other tools, but it won't really be hard since all of the lines are marked with the name of the module generating the line.

Related Solutions

Apache PHP-FPM – Configure Apache 2.4 with PHP-FPM and ProxyPassMatch

After hours of searching and reading Apache documentation I've come up with a solution that allows to use the pool, and also allow the Rewrite directive in .htaccess to work even when the url contains .php files.

<VirtualHost ...>

 ...

 # This is to forward all PHP to php-fpm.
 <FilesMatch \.php$>
   SetHandler "proxy:unix:/path/to/socket.sock|fcgi://unique-domain-name-string/"
 </FilesMatch>

 # Set some proxy properties (the string "unique-domain-name-string" should match
 # the one set in the FilesMatch directive.
 <Proxy fcgi://unique-domain-name-string>
   ProxySet connectiontimeout=5 timeout=240
 </Proxy>

 # If the php file doesn't exist, disable the proxy handler.
 # This will allow .htaccess rewrite rules to work and 
 # the client will see the default 404 page of Apache
 RewriteCond %{REQUEST_FILENAME} \.php$
 RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_URI} !-f
 RewriteRule (.*) - [H=text/html]

</VirtualHost>

As per Apache documentation, the SetHandler proxy parameter requires Apache HTTP Server 2.4.10.

I hope that this solution will help you too.

Apache 2.4 Virtualhost Blank Screen

if you get blank pages on loading php pages, set display_errors = On in /path-to-your/php.ini and start apache again (e.g.: sudo service apache24 onerestart). This way instead of a blank page, the missing extension(s) will be shown on the page. Chances are that it is commented out or missing in /path-to-your/php/extensions.ini (read on a FreeBSD forum, tip from soulreaver1)

Best Answer

Related Solutions

Apache PHP-FPM – Configure Apache 2.4 with PHP-FPM and ProxyPassMatch

Apache 2.4 Virtualhost Blank Screen

Related Topic