diff --git a/CHANGES b/CHANGES index bcf4833200..5bf0e7145f 100644 --- a/CHANGES +++ b/CHANGES @@ -1,6 +1,10 @@ -*- coding: utf-8 -*- Changes with Apache 2.5.1 + *) core: Remove support for the Content-MD5 header, removed in RFC7231. + Functions ap_md5digest() and ap_md5contextTo64() removed, and + ContentDigest directive. [Graham Leggett] + *) mod_dav: Allow other DAV modules to use dav_get_resource(). [Graham Leggett] diff --git a/docs/manual/developer/new_api_2_6.xml b/docs/manual/developer/new_api_2_6.xml index 3c87831031..898c26f77f 100644 --- a/docs/manual/developer/new_api_2_6.xml +++ b/docs/manual/developer/new_api_2_6.xml @@ -71,8 +71,9 @@
ap_fillmein()
ap_md5digest()
/ ap_md5contextTo64
Content-MD5
HTTP Response
-headersThis directive enables the generation of
- Content-MD5
headers as defined in RFC1864
- respectively RFC2616.
MD5 is an algorithm for computing a "message digest" - (sometimes called "fingerprint") of arbitrary-length data, with - a high degree of confidence that any alterations in the data - will be reflected in alterations in the message digest.
- -The Content-MD5
header provides an end-to-end
- message integrity check (MIC) of the entity-body. A proxy or
- client may check this header for detecting accidental
- modification of the entity-body in transit. Example header:
Note that this can cause performance problems on your server - since the message digest is computed on every request (the - values are not cached).
- -Content-MD5
is only sent for documents served
- by the
ContentDigest
directive and support for the the
+ Content-MD5
header has been removed from the server,
+ corresponding with the removal of this header from
+
+ RFC7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and
+ Content.