Re: [Zope-dev] SiteRoot and VHM
On Apr 7, 2005, at 1:45, Florent Guillaume wrote: After spending an hour helping someone debug a site that had an hidden SiteRoot somewhere that prevented a virtual host monster from working, it was suggested to me that if there's a virtual host monster, it should take precedence (and deactivates) any further SiteRoot. I think it's a good idea. Wouldn't that fall under Unexpected new behavior? VHMs have always been inert objects that don't do anything unless you specifically use the Mappings tab or you hand them magic URL path elements. That was their beauty as opposed to the dangerous SiteRoot. Now you propose adding magic. Magic is BAD, IMHO. -0 on the trunk, but -1 for any maintenance branch. jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SiteRoot and VHM
Am Donnerstag, den 07.04.2005, 01:45 +0200 schrieb Florent Guillaume: After spending an hour helping someone debug a site that had an hidden SiteRoot somewhere that prevented a virtual host monster from working, it was suggested to me that if there's a virtual host monster, it should take precedence (and deactivates) any further SiteRoot. I think it's a good idea. Better yet, it should just display a warning (and change its icon/title or so) to display the problem and let the user decide the action to take. Regards Tino ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SiteRoot and VHM
On Apr 7, 2005, at 9:08, Tino Wildenhain wrote: Am Donnerstag, den 07.04.2005, 01:45 +0200 schrieb Florent Guillaume: After spending an hour helping someone debug a site that had an hidden SiteRoot somewhere that prevented a virtual host monster from working, it was suggested to me that if there's a virtual host monster, it should take precedence (and deactivates) any further SiteRoot. I think it's a good idea. Better yet, it should just display a warning (and change its icon/title or so) to display the problem and let the user decide the action to take. That's an excellent idea, and one that I would +1 on all branches ;) jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] SiteRoot and VHM
After spending an hour helping someone debug a site that had an hidden SiteRoot somewhere that prevented a virtual host monster from working, it was suggested to me that if there's a virtual host monster, it should take precedence (and deactivates) any further SiteRoot. I think it's a good idea. Should I create a patch ? Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of RD +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
