Apache reverse proxy AH01597: could not open mime types config file

apache-2.4mime-typereverse-proxy

I'm trying to configure Apache HTTP server 2.4 as a reverse proxy on RHEL 7 server. When Apache starts up it complains in its log file (/var/log/httpd/error_log):

 AH01597: could not open mime types config file /etc/httpd/conf/mime.types.

I'm surprised it cares about MIME types, as I do not want it to serve files from the file-system at all. How can I configure Apache HTTP server so it does not demand a mime types configuration or which additional packages (RPMs) do I need to install to provide correct MIME types information.

Best Answer

I had based my Apache configuration file on the example that Red Hat provided. I included the command

 Include conf.modules.d/00-base.conf

as I thought leaving out any base modules would lead to Bad Things.

But the Red Hat supplied conf.modules.d/00-base.conf files loads numerous modules, few of which are required for a reverse proxy. In particular, it loads the mod_mime module, which needs a MIME types configuration file.

Replacing that Include command with individual LoadModule commands for the few modules I need eliminated the problem.

Related Solutions

Linux – WordPress and Apache 2.4 installation troubles: Cannot Serve Directory

It looks like you have forgotten DirectoryIndex.

This should be added to the <VirtualHost> serving WordPress.

DirectoryIndex index.php

Logging response headers in Apache reverse proxy without sending them to the client

In the past I have used a intermediate VirtualHost entry as a work-around for similar situations when certain directives didn't play well together:

Your current configuration may look like:

<VirtualHost *:80>
   ServerName www.example.com
   ProxyPass /app http://app.example.com/app
   ProxyPassReverse /app http://app.example.com/app
</VirtualHost>

Modify that to point to the intermediate virtual host and strip your header from the responses:

<VirtualHost *:80>
   ServerName www.example.com
   ProxyPass /app http://localhost:8000/app
   ProxyPassReverse /app http://localhost:8000/app
   Header unset Cast
</VirtualHost>

and a new virtual host where you can still log your Cast headers:

Listen 127.0.0.1:8000
<VirtualHost 127.0.0.1:8000>
   ServerName localhost
   ProxyPass /app http://app.example.com/app
   ProxyPassReverse /app http://app.example.com/appp
   LogFormat %{X-Forwarded-For}o %{Cast}o ...
</VirtualHost>

Best Answer

Related Solutions

Linux – WordPress and Apache 2.4 installation troubles: Cannot Serve Directory

Logging response headers in Apache reverse proxy without sending them to the client

Related Topic