> On 20 Jan 2017, at 20:49, 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 ?
>
> Removing what, precisely? Content-MD5 headers aren't implemented in trunk.
That is odd. I have in
Repository Root: http://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1779019
Quite a few:
> ./modules/cache/mod_cache.c: "Content-MD5",
> ./modules/filters/mod_brotli.c: apr_table_unset(r->headers_out,
> "Content-MD5");
> ./modules/filters/mod_deflate.c: apr_table_unset(r->headers_out,
> "Content-MD5");
> ./modules/filters/mod_deflate.c:
> apr_table_unset(r->headers_in, "Content-MD5");
> ./modules/filters/mod_deflate.c: apr_table_unset(r->headers_out,
> "Content-MD5");
> ./modules/filters/mod_filter.c:
> apr_table_unset(r->headers_out, "Content-MD5");
> ./modules/lua/mod_lua.c: apr_table_unset(r->headers_out,
> "Content-MD5");
> ./server/core.c: apr_table_setn(r->headers_out, "Content-MD5",
> ./server/protocol.c: apr_table_unset(rnew->headers_in, "Content-MD5");
Did I fuck up my repo in an epic way?
Dw
