From ae9e80d9f3065b73de19ab01db27bd0b4860233a Mon Sep 17 00:00:00 2001 From: Jeffrey Stedfast Date: Fri, 19 Apr 2002 22:02:13 +0000 Subject: Don't g_return_val_if_fail here if the boundary is an empty string. See 2002-04-19 Jeffrey Stedfast * camel-multipart.c (write_to_stream): Don't g_return_val_if_fail here if the boundary is an empty string. See bug #23676 for details. The way I see it, we have 2 options: 1) leave this fix the way it is, thus allowing multipart boundaries to be empty-strings; or 2) make camel_multipart_get_boundary() change the boundary to something legal if the boundary is an empty-string. Since the parser should be able to handle an empty-string boundary *and* more importantly because we want to keep the same boundaries as the original raw message so as to be able to verify multipart/signed parts, I vote for solution #1. svn path=/trunk/; revision=16539 --- camel/ChangeLog | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'camel/ChangeLog') diff --git a/camel/ChangeLog b/camel/ChangeLog index fbfe9c60ce..a4ee868465 100644 --- a/camel/ChangeLog +++ b/camel/ChangeLog @@ -1,3 +1,16 @@ +2002-04-19 Jeffrey Stedfast + + * camel-multipart.c (write_to_stream): Don't g_return_val_if_fail + here if the boundary is an empty string. See bug #23676 for + details. The way I see it, we have 2 options: 1) leave this fix + the way it is, thus allowing multipart boundaries to be + empty-strings; or 2) make camel_multipart_get_boundary() change + the boundary to something legal if the boundary is an + empty-string. Since the parser should be able to handle an + empty-string boundary *and* more importantly because we want to + keep the same boundaries as the original raw message so as to be + able to verify multipart/signed parts, I vote for solution #1. + 2002-04-19 Not Zed * devel-docs/camel-index.txt: Start of a white-paperish document -- cgit v1.2.3