[Zope-CMF] [dev] Unauthorized handling - a proposal

2010-04-20 Thread yuppie
Hi! Current situation: - By default Zope publishes Unauthorized exceptions as HTTP/1.1 401 Unauthorized responses including a basic authentication challenge. - If the user is not logged in, CMF converts Unauthorized exceptions into redirects. The redirect sends them to the login form and has

Re: [Zope-CMF] [dev] Unauthorized handling - a proposal

2010-04-20 Thread Charlie Clark
Am 20.04.2010, 12:53 Uhr, schrieb yuppie y.2...@wcm-solutions.de: Proposal: Meanwhile a much better hook exists for exception handling: Exception views. I propose to move most of the Unauthorized handling to a new exception view in the ICMFDefaultSkin layer. Please add a separate folder for

Re: [Zope-CMF] [dev] Unauthorized handling - a proposal

2010-04-20 Thread yuppie
Hi! Charlie Clark wrote: Please add a separate folder for these views. We need to separate them from the content ones. Why? 'browser' is a generic name, that folder is usually used for *all* browser views. Which folder names would you propose? BTW. (For pedagogic reason I'm not too keen

Re: [Zope-CMF] [dev] Unauthorized handling - a proposal

2010-04-20 Thread Charlie Clark
Am 20.04.2010, 14:19 Uhr, schrieb yuppie y.2...@wcm-solutions.de: Hi! Charlie Clark wrote: Please add a separate folder for these views. We need to separate them from the content ones. Why? 'browser' is a generic name, that folder is usually used for *all* browser views. Which folder

Re: [Zope-CMF] [dev] Unauthorized handling - a proposal

2010-04-20 Thread Charlie Clark
Am 20.04.2010, 16:21 Uhr, schrieb yuppie y.2...@wcm-solutions.de: You mean subfolders of browser? At the top level I would expect more than just the browser views inside folders with these names. Well, yes. Best practice would be document/browser, etc. but I think it's pragmatic to do