Actually that's a good, simple idea.

It occurred to me that a 'redirect' statement in htaccess should also be able to fix this. If I redirect all calls to cgi-bin/images to /images, shouldn't this do it too?

I'm partly asking because I've tried it and the server doesn't seem to be able to follow through the redirection and find the file. Htaccess is working, because if I put garbage in the file the server chokes on it.

Here's the line I've used in the .htaccess file that I've put in the /cgi-bin folder:

Redirect /images http://www.mysite.com/images/

I believe this should redirect any calls to cgi-bin/images (which doesn't exist) to the correct folder.

I've experimented with different arrangements of slashes, and with putting the full website address in the first parameter too - no success. The webpages that I've read which describe the use of this line make it sound like this is all it requires.

Is it possible the server is disallowing a http call to the cgi-bin folder, since it is not a folder for web-browsing? Can my htaccess file overcome this too?