Is it possible to keep what amount to 301s out of my apache error_log?
My website has hundreds of thousands of photos, and due to costs I've recently moved half of them to a cheaper host.  I can split them into frequently-accessed and infrequently-accessed, and it works out cheapest to keep the frequent ones at my main webhost, and the less frequent ones (lower bandwidth) on Rackspace Cloudfiles.

Anyway, after moving 100,000 files across, I set up a database table with all of the "before" and "afters" in it.

If a search engine etc requests a file on the old URL, it gets bounced to my 404 page, which then does a lookup in the database to find the new URL, where possible.  I then serve it up with a 301 header, so hopefully they'll get the message in the end and stop looking in the wrong place.

The problem is, all of these then get logged as "file does not exist" in my error_log.  Which annoys the OCD in me, and makes it harder to spot genuine errors.

I can understand why they end up there, what would you suggest I do to better solve this problem?

I'd prefer not to compromise the performance of the images that DO exist on my server.  So I don't want to mod_rewrite the entire images folder to be passed to a php script, as for most requests it's an unnecessary step.

Any suggestions?


Is it possible to keep what amount to 301s out of my apache error_log?
===

My website has hundreds of thousands of photos, and due to costs I've recently moved half of them to a cheaper host.  I can split them into frequently-accessed and infrequently-accessed, and it works out cheapest to keep the frequent ones at my main webhost, and the less frequent ones (lower bandwidth) on Rackspace Cloudfiles.

Anyway, after moving 100,000 files across, I set up a database table with all of the "before" and "afters" in it.

If a search engine etc requests a file on the old URL, it gets bounced to my 404 page, which then does a lookup in the database to find the new URL, where possible.  I then serve it up with a 301 header, so hopefully they'll get the message in the end and stop looking in the wrong place.

The problem is, all of these then get logged as "file does not exist" in my error_log.  Which annoys the OCD in me, and makes it harder to spot genuine errors.

I can understand why they end up there, what would you suggest I do to better solve this problem?

I'd prefer not to compromise the performance of the images that DO exist on my server.  So I don't want to mod_rewrite the entire images folder to be passed to a php script, as for most requests it's an unnecessary step.

Any suggestions?

