The way we handled this was making a custom virtualURIFilter that handles responses of the type moved: as well as redirect: and forward:. This opened up the whole power of things like regexp-virtualurimappings. It turned out the SEO-guys gave us a big list of pages that had moved though, and I couldn't be bothered to put them all in as separate virtualurimappings. The way I solved this was by making my own virtualurimapping that took a big white-space-separated chunk of text(the list i got from the SEO-guys) and mapped based on that. Works quite well actually, and I even bothered to make a simple GUI for this for the editors. In case more of those pop up.
20 nov 2009 kl. 15.27 skrev Matteo Pelucco: > > Hi all, > I have a question for a custom extension to Magnolia. > > We have the need to move an existing Coldfusion based website to Magnolia and > we want to maintain the same page structure (almost the same...). > > We don't want to loose Google index popularity, so we would like to handle > all www.domain.it/page.cfm ---> ERROR 301 Moved Permanently ---> > www.domain.it/magnoliaPage.cfm > > My first idea was to introduce a custom 301 Virtual Uri Mapping, but I > thought a log on it and I came out to realize a filter. > > Does it make sense? > > In that filter, can I close the response breaking the filter chain with a > simple response.flush? > > Thanks a lot.. > Matteo > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
