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
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
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
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
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
