From: short <>
Date: Mon, 19 Sep 2005 02:01:26 +0000 (+0000)
Subject: +Comment regarding RFC 1864 - "Content-MD5" canonalization.
X-Git-Url: https://git.jankratochvil.net/?p=MyWeb.git;a=commitdiff_plain;h=f47655270b5110c9a4180c820899ee7bfadbabe4

+Comment regarding RFC 1864 - "Content-MD5" canonalization.
---

diff --git a/Web.pm b/Web.pm
index 07db01c..bc0b293 100644
--- a/Web.pm
+++ b/Web.pm
@@ -994,6 +994,7 @@ sub cache_finish()
 	# as it will not provide the trailing filling '='s.
 	# RFC 1864 is not clear but the same provides them.
 	# FIXME: Should we somehow provide "\r\n" newlines for the text data? Which content is "text"?
+	#        Maybe it does not apply to HTTP as RFC 1864 targets mail/MIME.
 	# ',""' to avoid breaking the headers by its default "\n".
 	$headers_out{"Content-MD5"}=MIME::Base64::encode_base64($W->{"digest-md5"}->digest(),"");
 	# In fact we could also use MD5 for ETag as if we know ETag we also know MD5.