On Jul 10, 2008, at 6:47 AM, andrew wrote:
On Thu, 2008-07-10 at 02:44 +0200, Roger Ineichen wrote:
I guess bypass the authentication process is not supported for
zope.Public protected objects.
Zope does authenticate the user. And later it checks security
for the object based on that user
On Tuesday 08 July 2008, andrew wrote:
I've got a web application that uses pluggable authentication, but I
don't want the overhead of authentication for public resources like CSS,
javascript, images, etc. Is it possible to just disable authentication
for a given resource ? I tried just
Hi All,
On Tue, 2008-07-08 at 22:52 -0700, Shailesh Kumar wrote:
Did you try the resourceDirecotry ZCML directive?
browser:resourceDirectory
name=js
directory=resource/js
layer=.interfaces.IBatonSkin
/
that way they don't need the authentication overhead.
Thanks for the
Hi Andrew
Betreff: Re: [Zope3-Users] Disabling authentication for resources
[...]
I guess bypass the authentication process is not supported for
zope.Public protected objects.
Zope does authenticate the user. And later it checks security
for the object based on that user (authorization
, 2008 at 5:44 PM, Roger Ineichen [EMAIL PROTECTED] wrote:
Hi Andrew
Betreff: Re: [Zope3-Users] Disabling authentication for resources
[...]
I guess bypass the authentication process is not supported for
zope.Public protected objects.
Zope does authenticate the user. And later it checks
On Thu, 2008-07-10 at 02:44 +0200, Roger Ineichen wrote:
I guess bypass the authentication process is not supported for
zope.Public protected objects.
Zope does authenticate the user. And later it checks security
for the object based on that user (authorization).
zope.Public is correct
Did you try the resourceDirecotry ZCML directive?
browser:resourceDirectory
name=js
directory=resource/js
layer=.interfaces.IBatonSkin
/
that way they don't need the authentication overhead.
On 7/8/08, andrew [EMAIL PROTECTED] wrote:
Hi All,
I've got a web application that uses
