How to serve 410 from Apache rather than a 404

apache-2.2mod-rewrite

On our site, we tend to remove pages a lot where the content has expired, and we want to return http status 410 rather than 404 for requests to pages (physical files) that don't exist on our server (the entire site is made up of static files).

We have tried

RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^.*$ - [G,L]

from this blog post but that just breaks our entire site, serving a 410 for every request.

We are using Apache 2.2.3

Best Answer

    Redirect gone /path/to/resource

Is the correct way to do it. If that's causing errors for you, make sure you have mod_alias loaded in the server.

Related Solutions

Centos – Tomcat with virtual hosts – 404

It smells like maybe it's running into a mod_rewrite or alias before it's getting to your virtual host definition. Everything you've posted looks correct, but you can try adding a few extra options:

JkWorkersFile  /explicit/path/to/workers.properties
JkLogFile      /var/log/mod_jk.log
JkLogLevel     debug

That first setting will make sure you're using the actual properties file you think you are, maybe something in your multi-tomcat environment is loading the wrong one. You might also check this specific instance's TOMCAT_HOME to ensure it's loading the right server.xml; you can actually pass that as well as a parameter to $TOMCAT_HOME with -config:

cd $TOMCAT_HOME
./bin/startup.sh -config /direct/path/to/server.xml

See where that takes you...

Apache cache serving partial content 206 responses to requests for the full content

This is apache bug 49113 and has been fixed in the trunk but not in 2.2.19.

Best Answer

Related Solutions

Centos – Tomcat with virtual hosts – 404

Apache cache serving partial content 206 responses to requests for the full content

Related Topic