Re: rfc7231 - content-md5

2017-01-20 Thread Dirk-Willem van Gulik
> On 20 Jan 2017, at 21:13, William A Rowe Jr wrote: > > On Fri, Jan 20, 2017 at 1:49 PM, William A Rowe Jr > wrote: >> On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik >> wrote: >>> RFC 7231 has retired Content-MD5. >>>

Re: rfc7231 - content-md5

2017-01-20 Thread Dirk-Willem van Gulik
On 20 Jan 2017, at 20:49, William A Rowe Jr wrote: > > Note that https://www.rfc-editor.org/rfc/rfc7616.txt still provides > for MD5 hashed > digest auth keys. So removing this altogether will break mod_auth_digest in a > manner that breaks existing user auth. > > > Note

Re: rfc7231 - content-md5

2017-01-20 Thread Dirk-Willem van Gulik
> On 20 Jan 2017, at 20:49, William A Rowe Jr wrote: > > On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik > wrote: >> RFC 7231 has retired Content-MD5. >> >> Fair game to remove it from -trunk - or make it squeek 'debrecated' at WARN >> or

Re: rfc7231 - content-md5

2017-01-20 Thread William A Rowe Jr
On Fri, Jan 20, 2017 at 1:49 PM, William A Rowe Jr wrote: > On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik > wrote: >> RFC 7231 has retired Content-MD5. >> >> Fair game to remove it from -trunk - or make it squeek 'debrecated' at WARN >> or

Re: rfc7231 - content-md5

2017-01-20 Thread William A Rowe Jr
On Fri, Jan 20, 2017 at 1:21 PM, Dirk-Willem van Gulik 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

rfc7231 - content-md5

2017-01-20 Thread Dirk-Willem van Gulik
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 ? Dw.