Re: [Zope-dev] Etag support in page templates
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 removed, but I'd say don't provide any way to add it back (apart from maybe some textual instructions in the doc directory or something). The thing that continues to baffle me is why people add braindamage like this to Zope at all. Some controversial checkins have not been discussed beforehand. I watch the checkins, and I see things that I don't like, but I don't pipe up unless I consider the checkin dangerous. I usually give people the benefit of the doubt. 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 before checking it in. Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Etag support in page templates
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 before checking it in. Shane +1 Along with that the MS Author Via header garbage should at least be governed by some configuration flag. jens ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Etag support in page templates
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 the protocol to make their clients work then they should do so with another filter program. In zserver's case thats going to be the proxy HTTP daemon that it talks to. -- Jamie Heilman http://audible.transient.net/~jamie/ Most people wouldn't know music if it came up and bit them on the ass. -Frank Zappa ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Etag support in page templates
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 the protocol to make their clients work then they should do so with another filter program. In zserver's case thats going to be the proxy HTTP daemon that it talks to. 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. jens ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Etag support in page templates
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 server responses to placate # buggy Microsoft DAV clients. # # Default: off # # Example: # # send-empty-etag on # Directive: send-ms-author-via # # Description: # Add 'MS-Author-Via: DAV' HTTP header to server responses to # placate buggy Microsoft DAV clients. # # Default: off # # Example: # # send-ms-author-via on add, all the supporting code for this configuration and its implementation add, maintenance of said support code Result: The users will ask, Why doesn't my Office application work with Zope? The zope oracle will respond, It can, but you have to enable the send-empty-etag and send-ms-author-via directives in your zope.conf. The user will respond, OK, thanks. Solution B) in doc/WebDAV.txt or similar: Some Microsoft DAV clients are broken and need special coddling to work with Zope. In particular, extra headers need to be added to the HTTP responses. This can be done by configuring the HTTP proxy server to include these extra headers during conversations with known buggy clients. For example, using Apache's mod_headers: Headers set MS-Author-Via DAV Headers set Etag add, maintenance of said document Result: The users will ask, Why doesn't my Office application work with Zope? The zope oracle will respond, It can, but you have to configure your HTTP proxy to overcome Microsofts buggy DAV implementation, read doc/WebDAV.txt for more information. The user will respond, OK, thanks. Now... which of these scenarios do you think is in Zope's best interest? -- Jamie Heilman http://audible.transient.net/~jamie/ ...thats the metaphorical equivalent of flopping your wedding tackle into a lion's mouth and flicking his lovespuds with a wet towel, pure insanity... -Rimmer ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
