search.module using GET, rather than POST?

I'm moving my old home page into drupal.  I'd like to retire the old
content.  This will (obviously) break links from other websites.

I've considered a database of (old page, new page), but it seems like quite
a lot of work.  I've also thought about placing redirect pages in each of
the old locations.  I don't fancy doing that either.

So, I thought that I might write a custom 404 page, using Apache's
ErrorDocument directive.  This page would be written in PHP.  I thought that
I could break up the REDIRECT_URL and REDIRECT_QUERY_STRING environment
variables and then feed them to drupal's search page.  This would provide
the user with a list of pages, hopefully containing the one that they
wanted.

Unfortunately, the search page uses POST to do its magic.  Can I drive it
with GET instead?  Alternatively, is there another way that I can present
the user with a list of possible results?  Is this approach sensible?

Any other suggestions for solving this problem?

Cheers,
Roger.

--
[ Drupal support list | http://list.drupal.org/ ]