Complexe redirect

Egads, what a mess. The worst thing about it is that it is print somewhere. I suppose that you could write a custom 404 page with all your redirects on it. A couple of questions though.
What server are you using?
How many pages with redirects are we talking about?

approximately 40 pages and we are using Unix
thanks

I assume that you are using Apache with that. You could use the Redirect directive in Apache. I am not sure if there is a limit to the number of Redirects that you could use. The redirect can be used in httpd.conf and also in a htaccess file. The htaccess file can give you a bit of a performance hit since it has to reference the file constantly.

What I would do is start with redirecting one link and work on up to the others. Here is Apache's documentation on Redirect:

Redirect directive
Syntax: Redirect [status] url-path url
Context: server config, virtual host, directory, .htaccess
Override: FileInfo
Status: Base
Module: mod_alias
Compatibility: The directory and .htaccess context's are only available in versions 1.1 and later. The status argument is only available in Apache 1.2 or later.

The Redirect directive maps an old URL into a new one. The new URL is returned to the client which attempts to fetch it again with the new address. Url-path a (%-decoded) path; any requests for documents beginning with this path will be returned a redirect error to a new (%-encoded) url beginning with url.

Example:

Redirect /service http://foo2.bar.com/service
If the client requests http://myserver/service/foo.txt, it will be told to access http://foo2.bar.com/service/foo.txt instead.

Note: Redirect directives take precedence over Alias and ScriptAlias directives, irrespective of their ordering in the configuration file. Also, Url-path must be an absolute path, not a relative path, even when used with .htaccess files or inside of sections.

If no status argument is given, the redirect will be "temporary" (HTTP status 302). This indicates to the client that the resource has moved temporarily. The status argument can be used to return other HTTP status codes:

permanent
Returns a permanent redirect status (301) indicating that the resource has moved permanently.
temp
Returns a temporary redirect status (302). This is the default.
seeother
Returns a "See Other" status (303) indicating that the resource has been replaced.
gone
Returns a "Gone" status (410) indicating that the resource has been permanently removed. When this status is used the url argument should be omitted.
Other status codes can be returned by giving the numeric status code as the value of status. If the status is between 300 and 399, the url argument must be present, otherwise it must be omitted. Note that the status must be known to the Apache code (see the function send_error_response in http_protocol.c).