From: Adam Dickmeiss <adam@indexdata.dk>
Date: Wed, 15 May 2013 12:31:59 +0000 (+0200)
Subject: Version 4.2.57
X-Git-Tag: v4.2.57
X-Git-Url: http://jsfdemo.indexdata.com/cgi-bin?a=commitdiff_plain;h=38527b3ceab46772e46551ed0d311c1e3bf082e3;p=yaz-moved-to-github.git

Version 4.2.57
---

diff --git a/IDMETA b/IDMETA
index 5c23176..37a8ce4 100755
--- a/IDMETA
+++ b/IDMETA
@@ -1,4 +1,4 @@
 DEBIAN_DIST="wheezy squeeze"
 UBUNTU_DIST="quantal precise oneiric natty lucid"
 CENTOS_DIST="centos5 centos6"
-VERSION=4.2.56
+VERSION=4.2.57
diff --git a/NEWS b/NEWS
index ce5abab..2bccfcb 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,22 @@
+--- 4.2.57 2013/05/15
+
+COMSTACK: @ uses AF_UNSPEC . But we prefer AF_INET6 over others when
+picking a socket. Problem is that some systems has IPV6 support, but
+we can't create sockets for them, so we pick AF_UNSPEC first.
+
+HTTP encode. Proper Content-Length YAZ-660. For yaz_encode_http_response
+use content_len to determine resulting Content-Length in HTTP response
+and NOT Content-Length supplied in headers by user.
+
+z_HTTP_header_add_basic_auth uses z_HTTP_header_set rather than
+z_HTTP_header_add, to avoid having two Authorization headers by mistake.
+
+Fix problem with HTTP decoding. For HTTP 1XX, 204, 304 assume no
+content-length.
+
+Fix yaz_base64decode to use proper signed. Problem occurred on platforms
+with big endian and unsigned char (by default).
+
 --- 4.2.56 2013/04/26
 
 Fix yaz-client connect (crash in 4.2.55).
diff --git a/debian/changelog b/debian/changelog
index f0042b6..f4db6cf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+yaz (4.2.57-1indexdata) unstable; urgency=low
+
+  * Upstream.
+
+ -- Adam Dickmeiss <adam@indexdata.dk>  Wed, 15 May 2013 14:24:40 +0200
+
 yaz (4.2.56-1indexdata) unstable; urgency=low
 
   * Upstream.