Hi, I'm actually working on the implementation of a new website, moving from Zope 3 to Pyramid (using ZODB). When the new site will be ready, old contents will be gradually reorganized, rewritten and moved from the old site to the new one; both sites will be handled by different physical platforms using different domain names. In this context, a "redirection plan" has to be implemented, and I'm wondering about the best efficient way to implement it with Pyramid, given the following elements: - all input requests will be handled by Pyramid, which will check if the requested content has to be handled internally (if the requested page is a new one), by sending a proxy request to the old site (if a redirection is defined for requested URL), by sending an HTTP redirect or by sending an HTTP "NotFound"; - the number of redirection rules may be quite large! Some will match a whole subtree, some only one page; - the configuration of the redirection plan has to be available to a webmaster which is not a system administrator (so defining it at the Apache level doesn't seems to be an option), so typically into the CMS; - the Pyramid's website will be deployed into a cluster configuration (with at least three servers).
I suppose that the redirection has to be handled "as soon as possible" during request lifetime, so could using tweens be an option (database access has to be opened during this process)? Any advise would be greatly appreciated! ;) Best regards, Thierry -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAPX_VWCP3LTfRKzxeB%3Dv8EEuoLZJNYJo6A7758f2vW1%3D5jU_mQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
