> On 20 Jan 2017, at 21:13, William A Rowe Jr <wr...@rowe-clan.net> wrote: > > On Fri, Jan 20, 2017 at 1:49 PM, William A Rowe Jr <wr...@rowe-clan.net> > wrote: >> On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik >> <di...@webweaving.org> wrote: >>> RFC 7231 has retired Content-MD5. >>> >>> Fair game to remove it from -trunk - or make it squeek 'debrecated' at WARN >>> or INFO and retire it at the next minor release ? > > +1 > >> Removing what, precisely? Content-MD5 headers aren't implemented in trunk. > > Sorry, I missed a -i arg to grep :) > Ah ok - thanks - I was wondering I had been in Amsterdam for too long (which I had - and it involved shops where they do sell coffee).
> Yes, the default_handler behavior in trunk/server/core.c can simply be > removed, > along with the core.c ContentDigest directive handling. I think it > should also be > removed from modules/cache/mod_cache.c as it is not a valid entity header. > > The many unset Content-MD5 actions must remain IMO to guard against our > sharing this upstream or downstream. > > The http_core.h core flag content_md5 and values AP_CONTENT_MD5_* > should probably remain until 3.0 to avoid unnecessary API changes. a doxygen > /** @deprecated Unused flag */ against that struct member will help us mop > these > up during any 3.0 review. Dw.
