RE: [Zope-dev] Etag support in page templates

2003-11-02 Thread Bjorn Stabell
Just FYI. Apache 2.0.48 now honors caching of pages which only have Expires set (no need to include Etag and/or Last-Modified), but the 1.3 team hasn't responded and so 1.3.29 still has the bug. With mod_deflate site-wide compression of text/html etc, I guess it's enough candy there for me to

Re: [Zope-dev] Etag support in page templates

2003-09-17 Thread Chris Withers
Jens Vagelpohl wrote: +1 Along with that the MS Author Via header garbage should at least be governed by some configuration flag. + as many things as I'm allowed ;-) Then I can finally stop patching production servers that serve up MS office files for download... Chris

Re: [Zope-dev] Etag support in page templates

2003-09-17 Thread Chris Withers
Jamie Heilman wrote: Solution A) Solution B) The correct answer, of course, is to do both... Sorry, but not everyone fronts Zope with a proxy (yes, of coruse they should Jamie, but you have to understand not everyone is qutie as godlike as wants to get going as quickly as possible so they

Re: [Zope-dev] Etag support in page templates

2003-09-16 Thread Shane Hathaway
Jamie Heilman wrote: Tres Seaver wrote: The empty E-tag exists to support *very* broken clients (MSOffice over WebFolders); it should be removed, perhaps with a knob which allows re-enabling it for the sites that actually have people editing content using those clients. Yeah it should be

Re: [Zope-dev] Etag support in page templates

2003-09-16 Thread Jens Vagelpohl
In the case of empty Etags, I think that sending an empty header has been shown to be the wrong choice. I suggest it should be removed from the head and the 2_7 branch. For future reference to any committers: if you modify any HTTP headers sent by Zope, you very likely ought to discuss it

Re: [Zope-dev] Etag support in page templates

2003-09-16 Thread Jamie Heilman
Jens Vagelpohl wrote: Along with that the MS Author Via header garbage should at least be governed by some configuration flag. No, no, no, you're not seeing the bigger picture... you don't need configuration flags for any of that stuff. It just shouldn't exist, period. If people need to

Re: [Zope-dev] Etag support in page templates

2003-09-16 Thread Jens Vagelpohl
Jens Vagelpohl wrote: Along with that the MS Author Via header garbage should at least be governed by some configuration flag. No, no, no, you're not seeing the bigger picture... you don't need configuration flags for any of that stuff. It just shouldn't exist, period. If people need to clutter

Re: [Zope-dev] Etag support in page templates

2003-09-16 Thread Jamie Heilman
Jens Vagelpohl wrote: I'm not looking at the big picture. I'm trying to avoid complaints from people that for one reason or another use those broken M$ clients. Think about it: Solution A) # Directive: send-empty-etag # # Description: # Add an empty Etag HTTP header to

Re: [Zope-dev] Etag support in page templates

2003-09-15 Thread Jamie Heilman
Tres Seaver wrote: The empty E-tag exists to support *very* broken clients (MSOffice over WebFolders); it should be removed, perhaps with a knob which allows re-enabling it for the sites that actually have people editing content using those clients. Yeah it should be removed, but I'd say

RE: [Zope-dev] Etag support in page templates

2003-09-15 Thread Dieter Maurer
On Sun, 2003-09-14 at 22:59, Bjorn Stabell wrote: Dieter wrote: Please read the HTTP 1.1 spec... Caching requires either an ETag or Last-Modified header. For good reasons... That would explain why it never got fixed, but that's not how I understand the RFC:

Re: [Zope-dev] Etag support in page templates

2003-09-13 Thread Dieter Maurer
Bjorn Stabell wrote at 2003-9-11 14:45 +0800: ... Also, in most cases, the content of pages doesn't all come from one object, so Last-Modfied doesn't really make sense since it should refer to the whole page. I think the problem is with Apache's inability to cache content with Expires