[libsoup] 2.44.1
- From: Dan Winship <danw src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [libsoup] 2.44.1
- Date: Tue, 15 Oct 2013 14:10:05 +0000 (UTC)
commit 5acf257bb82d25cc821417aefda506e581117232
Author: Dan Winship <danw gnome org>
Date: Tue Oct 15 09:57:44 2013 -0400
2.44.1
NEWS | 42 ++++++++++++++++++++++++++++++++++++++++++
configure.ac | 2 +-
2 files changed, 43 insertions(+), 1 deletions(-)
---
diff --git a/NEWS b/NEWS
index a339beb..aa7606e 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,45 @@
+Changes in libsoup from 2.44.0 to 2.44.1:
+
+ * If you called g_input_stream_close() on SoupMessage or
+ SoupRequests's GInputStream before you finished reading it,
+ it would block until the rest of the response had been read
+ (which in the case of, eg, an infinite audio stream, meant
+ that it would block forever). This was an unintended change
+ from 2.42 and is now fixed. [#695652, Dan]
+
+ * soup_session_queue_message() on a plain SoupSession (not
+ SoupSessionAsync) was operating synchronously rather than
+ asynchronously as it should have. [#707711, Dan]
+
+ * soup-form methods now use the HTML5 x-www-form-urlencoded
+ rules rather than the HTML4 ones. (In particular, they leave
+ "-", "_", and "." unencoded.) [#708621, Alban Browaeys]
+
+ * The test programs now explicitly request the "memory"
+ GSettings backend, meaning they won't print a warning if
+ they get it accidentally, and they won't accidentally use
+ the dconf proxy settings if the dconf backend is available.
+ [Dan]
+
+ * Fix SoupSession so that if you override the proxy
+ configuration at construct time, it doesn't try to resolve
+ the default GProxyResolver. (This is important in particular
+ for programs that expect to run outside a user session,
+ which would otherwise spew errors from the dconf GSettings
+ backend about not being able to connect to dconf.) Likewise
+ with TLS settings and the TLS backend. [#708696, Dan]
+
+ * Fix the SoupServer:tls-certificate property;
+ soup_server_is_https() had not been updated to recognize it,
+ and so would return FALSE, which in turn meant that the
+ server would return 400 Bad Request in response to https
+ requests. [#709647, Fabiano FidĂȘncio]
+
+ * Fixed a sporadic failure in tests/connection-test. [Dan]
+
+ * Updated translations:
+ Tajik
+
Changes in libsoup from 2.43.92 to 2.44.0:
* New/updated translations:
diff --git a/configure.ac b/configure.ac
index 9eee7a8..5dd28f4 100644
--- a/configure.ac
+++ b/configure.ac
@@ -4,7 +4,7 @@ dnl *******************************************
m4_define([soup_major_version], [2])
m4_define([soup_minor_version], [44])
-m4_define([soup_micro_version], [0])
+m4_define([soup_micro_version], [1])
AC_PREREQ(2.63)
AC_INIT([libsoup],[soup_major_version.soup_minor_version.soup_micro_version],[http://bugzilla.gnome.org/enter_bug.cgi?product=libsoup])
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]