although the VBScript appears to be within the "on page" code, the status code response is actually sent before, or rather in this case instead of, the document. so it appears to be doing the correct thing which is good.
what would concern and is not clear to me is if you are redirecting several legacy pages to a single new location which is usually a bad thing to do.
Msg#: 4202880 posted 10:35 am on Sep 19, 2010 (gmt 0)
redirecting a large number of pages to a single page can cause problems from both the SEO perspective and the user experience. i would approach the problem from the user's perspective. perhaps a few pages representing categories or information silos would work better than a single generic page.
i would also study the inbound links to these urls. one or a few of these urls may actually be well worth the effort of recreating and redirecting or even better, keeping at the original url. in this case it may actually be better to recreate/redirect only the valuable content and letting the rest go 404 or 410, using a custom 404/410 page with some relevant navigation and a search function.
other than the change of ownership issues, this thread has some advice that applies to your situation:
That page did have a good discussion. As Tedster suggested, I could create a separate new page for each of the categories delivered by listings.asp?=category (maybe 15 or so) and redirect the appropriate pages. Many of those old pages had PR2.
That begs one last question: what's the "shelf life" of those old pages in the index. Is two weeks with the new site live too late to try that scheme?