We are using the appliance, with all patches installed as of 4/26/06.
It is my understanding that rewrites in apache that return a response of 301 it tells most search engines that this url has been moved permanently and will index the new url.
If what I am seeing is correct, it looks like webinator does not index the new url.
Currently HTTP responses indicating permanent(301) and temporary(302) redirects are treated the same. The new page is fetched and the new content is stored in the database under the original url.
From best I can tell, the usual practice is that 301 and 302 redirects are handled separately. Would it be possible to modify webinator to do that?
We have migrated a lot of static content in to our dynamic server. Since we did the migration, we decided to do some reorganization. So we wouldn't loose our users that may have bookmarks/links, we wanted to promote the new url.
Have you thought about changing the behavior of 301s?