summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDan Winship <danw@gnome.org>2010-04-06 12:42:33 -0400
committerDan Winship <danw@gnome.org>2010-04-09 19:51:33 -0400
commitd557ea0359301beb62c194ddb4a0222512cae842 (patch)
treeac12b0818cf47020aa3ff53bdd3529db9f6e2673
parent8569d007dbffc7096b1eb47004381deb8397426f (diff)
downloadlibsoup-d557ea0359301beb62c194ddb4a0222512cae842.tar.gz
soup-multipart: don't use Content-Transfer-Encoding in multipart/form-data
The HTML 4.01 spec says you have to, but apparently no one else does, and it confuses some servers. https://bugzilla.gnome.org/show_bug.cgi?id=614198
-rw-r--r--libsoup/soup-multipart.c14
1 files changed, 0 insertions, 14 deletions
diff --git a/libsoup/soup-multipart.c b/libsoup/soup-multipart.c
index 9223f1df..45deed6e 100644
--- a/libsoup/soup-multipart.c
+++ b/libsoup/soup-multipart.c
@@ -385,20 +385,6 @@ soup_multipart_append_form_file (SoupMultipart *multipart,
content_type);
}
- /* The HTML spec says we need to set Content-Transfer-Encoding
- * if the data is not 7bit. It probably doesn't actually
- * matter...
- */
- if (content_type && strncmp (content_type, "text/", 5) != 0) {
- soup_message_headers_append (headers,
- "Content-Transfer-Encoding",
- "binary");
- } else {
- soup_message_headers_append (headers,
- "Content-Transfer-Encoding",
- "8bit");
- }
-
g_ptr_array_add (multipart->headers, headers);
g_ptr_array_add (multipart->bodies, soup_buffer_copy (body));
}