Jens Vagelpohl wrote at 2006-10-11 12:03 -0400:
...
I'm not sure this can be called a bug. It is true (and perfectly
normal) that rendering a filesystem page template will always call
the CPM. You're rendering both here. Since output_page_2 is rendered
last as it's calles from output_page_1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13 Oct 2006, at 14:06, [EMAIL PROTECTED] wrote:
Thus, this *is* the bug. It should distinguish between primary and
nested
rendering.
Unfortunately, the bug is probably deep -- affecting the complete
cache integration. Even more importantly,
Hi,
I'm trying to investigate a problem where the CPM is adding cache
headers to a response for the wrong object. I can reproduce it in plain
CMF as follows:
1. Add two filesystem zpts:
output_page_1:
==
html
head
titletest page/title
/head
h1Here is the title/h1
x
Miles Waller wrote at 2006-10-11 16:34 +0100:
...
output_page_2:
==
h2Here is the subtitle from template 2/h2
2. Add a rule to the cpm as follows:
id: template_test
predicate: view.endswith('_2')
etag: string:template_test
3. Make a request for yoursite/output_page_1
4. Note
Hi,
I'm currently setting up a CMF site for testing purposes. While configuring the
CachingPolicyManager, I discovered that it didn't work for the Image and File
content types. However, it worked perfectly for the Document content
type. I only
got it working for Image and File after I modified
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 Apr 2006, at 14:19, Bert Vanderbauwhede wrote:
I'm currently setting up a CMF site for testing purposes. While
configuring the
CachingPolicyManager, I discovered that it didn't work for the
Image and File
content types. However, it worked
Bert Vanderbauwhede wrote at 2006-4-5 15:19 +0200:
...
I'm currently setting up a CMF site for testing purposes. While configuring the
CachingPolicyManager, I discovered that it didn't work for the Image and File
content types. However, it worked perfectly for the Document content
type. I only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The combining of Zope's HTTPCacheManager and the CMF
CachingPolicyManager is yet another item which really should not be
in some standalone thingy but integrated into the
CachingPolicyManager itself... I hope to do this in time for CMF 2.1.
Title: Re: [Zope-CMF] CachingPolicyManager and Image/File content
The PolicyHTTPCacheManager
is ZPL. I'm willing to donate it's code.
--
Sidnei da Silva
Enfold Systems, Inc.
http://www.enfoldsystems.com
De: [EMAIL PROTECTED] em nome de
Jens VagelpohlEnviada: qua 5/4/2006 17:40Para
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5 Apr 2006, at 21:44, Sidnei da Silva wrote:
The PolicyHTTPCacheManager is ZPL. I'm willing to donate it's code.
-- Sidnei da Silva Enfold Systems, Inc. http://www.enfoldsystems.com
Thanks Sidnei, this is much appreciated. I'm going to update
I have checked my CachingPolicyManager improvements into the
geoffd-cachingpolicymanager-branch. Enjoy!
Geoff
PS Those of you who raised concerns about ZopeTestCase causing test
problems in Zope 2.7 might want to take a look at why test_z3interfaces is
broken when you run the tests with
Hi all--
I have added some useful new functionality to CMFCore's
CachingPolicyManager:
1) Caching policies can now control all the Cache-Control tokens defined
in the HTTP 1.1 spec (s-maxage, public, private, no-transform). To
implement this, I have added some extra keyword arguments to the
12 matches
Mail list logo
