From: Adam Dickmeiss Date: Mon, 1 May 2006 09:28:00 +0000 (+0000) Subject: Clean up news X-Git-Tag: YAZPROXY.1.2.1 X-Git-Url: http://sru.miketaylor.org.uk/cgi-bin?a=commitdiff_plain;h=c88540fe71bb20a5c023dd9dc77fec74dc90f044;p=yazproxy-moved-to-github.git Clean up news --- diff --git a/NEWS b/NEWS index 1324b4a..2f78795 100644 --- a/NEWS +++ b/NEWS @@ -1,31 +1,30 @@ ---- 1.2.1 2005/05/01 +--- 1.2.1 2006/05/01 Fixed problem with log of session ID when HTTP fowarded was in effect. Fixed a problem with negative numbers in present requests. -Allow client-ip to be logged for each log entry. Speciy +Allow client-ip to be logged for each log entry. Specify client-ip in the configuration. -Added support for limiting the number of initiating connections -from a single IP. limit-connect specifies a limit and if that -is reached a delay is introduced (just as limit-pdu, etc). -Also added a new setting max-connect; if that max value is -reached for a single IP the proxy will terminate the initiating -session/connection immediately. +Added support for limiting the number of initiating connections from +a single IP. limit-connect specifies a limit and if that is reached a +delay is introduced (just as limit-pdu, etc). Also added a new setting +max-connect; if that max value is reached for a single IP the proxy +will terminate the initiating session/connection immediately. -New directive default-client-charset which serves as charset -to be negotiated if client does NOT supports one. +New directive default-client-charset which serves as charset to be +negotiated if client does NOT supports one. Added support for threaded authentication modules. See etc/config-modules.xml + mod_sample.cpp for an example. -Added support for Z39.50 character set negotiation. This allows -the proxy to act as a Z39.50 server supporting character set negotiation +Added support for Z39.50 character set negotiation. This allows the +proxy to act as a Z39.50 server supporting character set negotiation for backends not supporting it. New config element target-charset -specifies encoding for target, and MUST be specified in order -for any conversion to take place. Conversion also takes place for -SRW/SRU clients that are negotiate implicitly to UTF-8. +specifies encoding for target, and MUST be specified in order for +any conversion to take place. Conversion also takes place for SRW/SRU +clients that are negotiate implicitly to UTF-8. --- 1.0.1 2005/05/27