On 1/11/06, David Hassalevris <[EMAIL PROTECTED]> wrote:
> Can you explain how you are using this?

I am not sure what "this" you are referring to. If you mean
controlling the cache control http response that is done by setting a
property in the CookieCrumbler object.

>  Does cookie crumbler's
> cache-control apply to *all*  authenticated responses?   If so, I didnt
> realize it was so sweeping (I admit i had assumed it applied to the
> authentication cookie).

That is my understanding of how it works in all current versions.

> Have you, for example, considerered branching to different folders (one with
> all object caches set to no-cache) based on a user role?

I am not sure what you mean.

> Its an interesting idea, to cascade cookie crumblers - you might be able to
> fake the login_screen

My preliminary testing seems to indicate that this cascading does what
I want -- unless there is some gotcha there. I suppose it is easy
enough to test -- but I have to first get setup in the proxied
environment with somebody that understands the particular proxy.
Zope maillist  -  Zope@zope.org
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to