~statik/ubuntu/maverick/erlang/erlang-merge-testing

<?xml version="1.0" encoding="latin1" ?>

<!DOCTYPE chapter SYSTEM "chapter.dtd">

<chapter>

  <header>

    <copyright>

      <year>2004</year><year>2010</year>

      <holder>Ericsson AB. All Rights Reserved.</holder>

    </copyright>

    <legalnotice>

      The contents of this file are subject to the Erlang Public License,

      Version 1.1, (the "License"); you may not use this file except in

      compliance with the License. You should have received a copy of the

      Erlang Public License along with this software. If not, it can be

      retrieved online at http://www.erlang.org/.

      Software distributed under the License is distributed on an "AS IS"

      basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See

      the License for the specific language governing rights and limitations

      under the License.

    </legalnotice>

    <title>Inets Release Notes History</title>

    <prepared></prepared>

    <responsible></responsible>

    <docno></docno>

    <approved></approved>

    <checked></checked>

    <date>04-09-30</date>

    <rev>A</rev>

    <file>notes_history.sgml</file>

  </header>

  <section>

  <title>Inets 4.7.17</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[HTTP client] - Could fail in retry_pipeline/2 due to an

	  incorrect assumption of an internal returnvalue.</p>

	<p>Own Id: OTP-6791</p>

      </item>

      <item>

	<p>[HTTP client] - The check of the value of the transfer

	  encoding has been updated so that it is case insensitive.</p>

	<p>Own Id: OTP-6807</p>

      </item>

      <item>

	<p>[HTTP client] - When receiving a 304 "Not Modified"

	  reply, the httpc_handler will no longer expect to receive

	  a HTTP body.</p>

	<p>Own Id: OTP-6821</p>

      </item>

      <item>

	<p>[HTTP client] - Parsing of the HTTP response failed when

	  there was no headers fields in the response.</p>

	<p>Own Id: OTP-6830</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[HTTP server] - Started clean up of code so that it uses

	  stdlib functions instead of reinventing them.</p>

	<p>Own Id: OTP-6808</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.16</title>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>Minor Makefile changes.</p>

	<p>Own Id: OTP-6689</p>

      </item>

      <item>

	<p>http_base_64:encode/decode and

	  httpd_util:to_upper/to_lower are now deprecated, as these

	  functions has been moved to stdlib, using them will now

	  cause an compiler warning and the documentation of them

	  has been removed.</p>

	<p>Own Id: OTP-6716</p>

      </item>

      <item>

	<p>When making an asynchronous HTTP request and the

	  underlying gen_tcp:connect failed with timeout (not a

	  very common case) the return of the asynchronous HTTP

	  request was delayed for "timeout" seconds. This happened

	  due to the fact that when spawning a gen_server process

	  the spawn will wait for the init function to complete.

	  This is now avoided using proc_lib and

	  gen_server:enter_loop/3, hence the asynchronous HTTP

	  request return will not be delayed. Also the request

	  timeout value is now propagated to gen_tcp rather that

	  relying on the system default.</p>

	<p>Own Id: OTP-6735</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.15</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[tftp] The TFTP client/server implements now a more

	  relaxed interpretation of the RFC 1350 regarding

	  re-receive of acknowledgments. If multiple copies of the

	  same acknowledgments is received the spurious ones are

	  silently ignored. This fix was intended for inets-4.7.14

	  but accidentaly it was not included in that release.</p>

	<p>Own Id: OTP-6706 Aux Id: OTP-6691 </p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>Minor Makefile changes.</p>

	<p>Own Id: OTP-6689</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.14</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[tftp] The TFTP client/server implements now a more

	  relaxed interpretation of the RFC 1350 regarding

	  re-receive of acknowledgments. If multiple copies of the

	  same acknowledgments is received the spurious ones are

	  silently ignored.</p>

	<p>Own Id: OTP-6691</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.13</title>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[tftp] The TFTP client/server implements now a more

	  relaxed interpretation of the RFC 1350 regarding

	  re-receive of data packets. If multiple copies of the

	  same data packet is received the spurious ones are

	  silently ignored.</p>

	<p>Own Id: OTP-6642</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.12</title>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[httpd] - When calling httpd:restart there was a file

	  descriptor and ets table leek due to the fact that the

	  semantics of the function restart is not restart but

	  reload.</p>

	<p>Own Id: OTP-6573 Aux Id: seq10607 </p>

      </item>

      <item>

	<p>[tftp] Crash in tftp_engine:terminate/3 caused big crash

	  report. The file was however transferred as normal, but

	  the ugly printout is now gone.</p>

	<p>Own Id: OTP-6596 Aux Id: seq10618 </p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.11</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[http] - Chunked encoding updated to handle the empty

	  chunk.</p>

	<p>Own Id: OTP-6511</p>

      </item>

      <item>

	<p>[http] - Removed minor bugs and dead code found by

	  dialyzer.</p>

	<p>Own Id: OTP-6522</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.10</title>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[httpd] - The server no longer produces error messages

	  when the client resets the the connection. This is not an

	  error as far as the server is concerned.</p>

	<p>Own Id: OTP-6484 Aux Id: seq10568 </p>

      </item>

      <item>

	<p>[tftp] The server is now silent by default. Error

	  messages can however be displayed by setting the debug

	  level to 'error' (new) or higher.</p>

	<p>Own Id: OTP-6498</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.9</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>Bug in in handling of request timers has been corrected.</p>

	<p>Own Id: OTP-6476</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[tftp] - Daemon was only able to process one request when

	  fd option was given.</p>

	<p>Own Id: OTP-6480</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.8</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[ftp, httpc] - Updated the internal ensure_started

	  functions to handle that inets was started as an included

	  application.</p>

	<p>Own Id: OTP-6409 Aux Id: seq10546 </p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[httpd] - Guard added to API function

	  httpd_util:integer_to_hexlist/1.</p>

	<p>Own Id: OTP-6397</p>

      </item>

      <item>

	<p>[tftp] - Introduced ability to use prebound ports (see

	  the option {port, Port} for more info). Added peer info

	  (host and port) as new optional argument to prepare and

	  open functions in tftp callback modules.</p>

	<p>Own Id: OTP-6413</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.7</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[httpd] - The http server could throw away pipelined

	  requests leaving the client hanging.</p>

	<p>Own Id: OTP-6310</p>

      </item>

      <item>

	<p>[ftp] - Code for handling fallback to ipv4 was not

	  exhaustive.</p>

	<p>Own Id: OTP-6312</p>

      </item>

      <item>

	<p>[httpd] - Incorrect handling of ipv6 address would crash

	  the loading of the BindAddress parameter, which had the

	  consequence that you could not start more than one HTTP

	  server on an erlang node.</p>

	<p>Own Id: OTP-6323</p>

      </item>

      <item>

	<p>[httpc] - Some 30X codes, as for instance 302, should not

	  always be automatically redirected but in inets-4.7.6 some

	  restrictions where made too hard, never allowing an

	  automatic redirection. (Automatic redirect should be

	  allowed for get and head.)</p>

	<p>Own Id: OTP-6332</p>

      </item>

      <item>

	<p>[ftp] - The mode flag that could be used to force ftp

	  active mode was ignored. Only the deprecated function

	  force_active/1 works for prior releases to this one.</p>

	<p>Own Id: OTP-6342</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[httpc] - Added debug feature to turn on/off some basic

	  erlang tracing on client processes.</p>

	<p>Own Id: OTP-6326</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.6</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[httpc] - The parsing of uri's was rewritten so that it

	  should handle all types of uri's including ipv6 uri's.</p>

	<p>Own Id: OTP-5677</p>

      </item>

      <item>

	<p>[httpc, httpd] - Extensions and trailers where not

	  properly handled by the chunk decoding implementation.</p>

	<p>Own Id: OTP-6005 Aux Id: OTP-6264 </p>

      </item>

      <item>

	<p>[httpc] - A request resulting in an empty body is now

	  returned without any delays.</p>

	<p>Own Id: OTP-6243</p>

      </item>

      <item>

	<p>[httpc] - When http:request/4 was used with a configured

	  proxy, and the webserver returns 3XX code, http:request/4

	  entered an endless loop. Two problems was solved in this

	  area, the absolute uri is now updated when a redirect is

	  issued, so that the problem in this case will not arise,

	  and the redirection endless loop detection was fixed so

	  that will actually detect potential endless loops.</p>

	<p>Own Id: OTP-6244</p>

      </item>

      <item>

	<p>[httpc, httpd] - In some cases if a body contained the

	  sequence "\r\n0" and was chunked encoded this sequence

	  was incorrectly interpreted as the last chunk.</p>

	<p>Own Id: OTP-6264 Aux Id: OTP-6005 </p>

      </item>

      <item>

	<p>[httpc, httpd] - http_request.erl didn't handle https

	  URIs, which meant that redirects from ESI did not work.</p>

	<p>Own Id: OTP-6274</p>

      </item>

      <item>

	<p>[httpc, httpd] - The base 64 decoder was missing a guard

	  so that invalid input lead to an emulator crash instead

	  of a function clause as expected. Also the http server

	  has been improved to handle the function clause error

	  returning a bad credentials reply to the client.</p>

	<p>Own Id: OTP-6279</p>

      </item>

      <item>

	<p>[httpc] - Changed internal default value as it sometimes

	  would be interpreted incorrectly causing the client to

	  return an incomplete body.</p>

	<p>Own Id: OTP-6283</p>

      </item>

      <item>

	<p>[httpc] - Handling of 30X codes was changed so that it

	  works according to the documentation. For instance 301

	  and 302 codes will not be automatically redirected.</p>

	<p>Own Id: OTP-6297</p>

      </item>

      <item>

	<p>[httpc] - A bug in the pipeline-handling code could cause

	  a response to be sent to the client with an incorrect

	  request id.</p>

	<p>Own Id: OTP-6303</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[httpc] - Added feature to send header values as they

	  where typed by the user of the client. Note that the http

	  standard requires them to be case insensitive. This

	  feature should only be used if there is no other way to

	  communicate with the server or for testing purpose.</p>

	<p>Own Id: OTP-5527</p>

      </item>

      <item>

	<p>[httpc] - When using asynchronous HTTP-request it is now

	  possible to receive "200-responses" as streams instead of

	  having to wait until the whole response has been

	  delivered. It also possible to stream "200-response

	  bodys" to a file both for synchronous and asynchronous

	  requests.</p>

	<p>Own Id: OTP-6263</p>

      </item>

      <item>

	<p>[httpc] - Added option to generate Proxy-Authorization

	  header from provided proxy username and password.</p>

	<p>Own Id: OTP-6280</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.5</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[FTP] Change documentation so that it agrees with the

	  default behaviour of the code regarding the use of

	  transfer type, which is right according to rfc959.</p>

	<p>Own Id: OTP-6018</p>

      </item>

      <item>

	<p>[ftp] The application handles the case if the owning

	  process terminates with the reason 'shutdown'.</p>

	<p>Own Id: OTP-6035</p>

      </item>

      <item>

	<p>[ftp] Handle file errors from the FTP server.</p>

	<p>Own Id: OTP-6036</p>

      </item>

      <item>

	<p>[httpd] Header parsing of reply from cgi script incorrect.</p>

	<p>Own Id: OTP-6145</p>

      </item>

      <item>

	<p>[ftp] The timeout given in the ftp:open call was not

	  properly used, which could leave the caller hanging

	  forever.</p>

	<p>Own Id: OTP-6184</p>

	<p>Aux Id: seq10388</p>

      </item>

      <item>

	<p>[httpd] HTTPD request handler does not handle unexpected info

	  properly, which causes an unnecessarily obscure error 

	  message.</p>

	<p>Own Id: OTP-6189</p>

	<p>Aux Id: seq10395</p>

      </item>

      <item>

	<p>[http] Misc fixes in the URI parsing module.</p>

	<p>Igor Goryachev</p>

	<p>Own Id: OTP-6191</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>Added application interface module: <c>inets</c>.</p>

	<p>Own Id: OTP-6135</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.4</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>Removed code generating compiler warnings</p>

	<p>Own Id: OTP-6069</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[tftp] Added documentation (manual page) for 

	  <seealso marker="tftp">TFTP</seealso>.</p>

	<p>Own Id: OTP-6082</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.3</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[http,server] started dbg even though no debugging was

	  desired.</p>

	<p>Own Id: OTP-5984 Aux Id: seq10290 </p>

      </item>

      <item>

	<p>[http,server] request handler process died ugly due to a

	  parse error when validating a bad request.</p>

	<p>Own Id: OTP-6003 Aux Id: seq10260 </p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7.2</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[http,server] Server falsely sets ipv6 enabled when it

	  gets an ipv4-mapped ipv6 address.</p>

	<p>Own Id: OTP-5941 Aux Id: seq10221 </p>

      </item>

      <item>

	<p>[http,server] In case http version is unknown of client

	  use HTTP1.0 to send status.</p>

	<p>Own Id: OTP-5943 Aux Id: seq10198 </p>

      </item>

      <item>

	<p>[http,server] The process handling a request now ignores

	  garbage messages.</p>

	<p>Own Id: OTP-5961 Aux Id: seq10198 </p>

      </item>

      <item>

	<p>[http,server] Changed some actions taken if config data

	  in httpd services was faulty.</p>

	<p>Own Id: OTP-5962 Aux Id: seq10198 </p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>inets 4.7.1</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[http,server] It was possible to read arbitrary files on

	  server by prepending ././ and ../../ in front of the file

	  name.</p>

	<p>Own Id: OTP-5938</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.7</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[http,server] Handling of undefined file times (e.g.

	  modification time: the mtime field on the file_info

	  record).</p>

	<p>Own Id: OTP-5865 Aux Id: OTP-5844 </p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[http,server]It is now possible to set the wanted timeout

	  for the server to setup a request connection. A new

	  syntax for inets.config is provided in the users guide

	  documentation. This syntax also allows to set tracing of

	  the server for debug purposes.</p>

	<p>Own Id: OTP-5913 Aux Id: seq10198 </p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.6.2</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[http,server] Had earlier forgot to convert a value in

	  entity_body to a binary.</p>

	<p>Own Id: OTP-5796</p>

      </item>

      <item>

	<p>[http,server] Now application checks whether the

	  necessary directives under directive Directory exist.</p>

	<p>Own Id: OTP-5821</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.6.1</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[http, client] If an Ipv4-mapped ipv6 address is used the

	  client now falls back on ipv4.</p>

	<p>Own Id: OTP-5773 Aux Id: OTP-5765, OTP-5764 </p>

      </item>

      <item>

	<p>[http,server] Content-length may got a too low value,

	  causing loss of data in clients.</p>

	<p>Own Id: OTP-5775 Aux Id: seq10110 </p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[http, client] The verbose mode prints what was sent and

	  received during a request. Added a <c>verbose</c> option

	  that can be used by <c>http:set_options/1</c></p>

	<p>Own Id: OTP-5766</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.6</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[ftp, client] - Improvement of error handling if

	  something goes wrong while handling the option list in

	  ftp:open/[1,2,3].</p>

	<p>Own Id: OTP-5711</p>

      </item>

      <item>

	<p>[ftp, client] - Error when parsing a multiple FTP

	  response line. The last line in a multiple response must

	  be the response code followed by a space. A server may

	  have intermediate lines that start with the response code

	  even if this is not recommended. The parsing missed to

	  make sure that that space was present in what it

	  considered to be the last line.</p>

	<p>Own Id: OTP-5712</p>

      </item>

      <item>

	<p>[http, client] - The HTTP client will now retry a

	  pipelined request that was unsuccessful due to the fact

	  that the server unexpectedly closed the pipeline

	  connection.</p>

	<p>Own Id: OTP-5728</p>

      </item>

      <item>

	<p>[http, server, esi] - Under some circumstances mod_esi

	  would send a corrupted content-length header.</p>

	<p>Own Id: OTP-5735</p>

      </item>

      <item>

	<p>[http, server, get] - Removed debug printout which 

	  caused a confusing "Socket closed"-printout at high

	  load.</p>

	<p>Own Id: OTP-5762 Aux Id: seq10101 </p>

      </item>

      <item>

	<p>FTP: a data connection setup to the ftp server that

	  failed caused a crash of the client. Now it is handled

	  smoothly.</p>

	<p>Own Id: OTP-5738</p>

      </item>

      <item>

	<p>[ftp] If host name is a ipv4 tuple ftp erroneous tries to

	  connect as a ipv6 address with the ipv4 address.</p>

	<p>Own Id: OTP-5764</p>

      </item>

      <item>

	<p>[ftp] Handles connect to ipv6/ipv4 address differently

	  according to a change in <c>inet:getaddr</c>.</p>

	<p>Own Id: OTP-5765</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[http, server] - The HTTP request handling was remoduled

	  to have a more straight forward error-handling. And the

	  internal debug strategy was changed to use tracing

	  instead of debug macros, which means we do not have to

	  write special debug code.</p>

	<p>Own Id: OTP-5729</p>

      </item>

      <item>

	<p>ftp:ls towards different ftp servers resulted in

	  different return results. E.g. the solaris 9 default

	  server caused <c>{ok,[]}</c> while older servers caused

	  <c>{error,epath}</c> as the result. For backwards

	  compatibility the behaviour has been changed to the old

	  result.</p>

	<p>Own Id: OTP-5731</p>

      </item>

      <item>

	<p>[http, server] - The documentation for the HTTP server

	  has been partly rewritten and very restructured too

	  provide a better overall picture. Lots of information

	  provided by "semi manual pages" has been moved to the

	  Users Guide.</p>

	<p>Own Id: OTP-5752</p>

      </item>

      <item>

	<p>FTP: verbose mode now also prints what the client sends

	  on the control channel.</p>

	<p>Own Id: OTP-5753</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.5.4</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[ftp, client] - Timing related issues could sometimes

	  cause the ftp response to be delayed.</p>

	<p>Own Id: OTP-5705 Aux Id: seq10055 </p>

      </item>

      <item>

	<p>[http, server, esi] - The dispatching of the post body to

	  the esi callback function was broken.</p>

	<p>Own Id: OTP-5706</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.5.3</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[ftp, client] - The FTP error code 550 was handled in an

	  unexpected way. Some earlier versions of inets had a

	  workaround for this in ftp:recv_bin/2 that was eliminated

	  during restructuring of the ftp module while implementing

	  ipv6 capabilities. The problem is now fixed.</p>

	<p>Own Id: OTP-5682 Aux Id: seq10048 </p>

      </item>

      <item>

	<p>[http, client] Post request with a body in binary format

	  failed as length was used instead of size.</p>

	<p>Own Id: OTP-5686</p>

      </item>

      <item>

	<p>[ftp, client] - For some FTP commands the FTP server will

	  send more than one reply on the FTP control channel. In

	  the case of a fast FTP server the client would sometimes

	  wrongly disregard the second answer as trailing garbage

	  attached to the first reply.</p>

	<p>Own Id: OTP-5690 Aux Id: seq10055 </p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[ftp, client] - A new option {progress, {CBmodule,

	  CBFunction, InitProgressTerm} has been added to allow

	  users to create things such as progress bars in there

	  GUI's. The option affects ftp:send/[3,4] and

	  ftp:recv/[3,4].</p>

	<p>Own Id: OTP-5680</p>

      </item>

      <item>

	<p>[http, client] - Added new API function http:request/1</p>

	<p>Own Id: OTP-5691</p>

      </item>

      <item>

	<p>[httpd, server] - mod_cgi is implemented according to

	  CGI-1.1 RFC 3875, an early implementation was based on

	  some draft that is not totally compliant to the RFC.

	  Documentation was updated. Also some code was

	  restructured to facilitate testing and maintenance of the

	  server.</p>

	<p>Own Id: OTP-5694</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.5.2</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[ftp, client] Calling ftp:recv/2 twice on the same

	  connection failed due to that the last message on the

	  ctrl channel was not appropriately taken care of. This

	  could potentially cause a problem for any operation

	  performed on the same connection where there had

	  previously been an ftp:recv/2 call. Also, in some cases,

	  when the process tries to close the data connection, it

	  does not take into account that the data connection may

	  actually not have been established.</p>

	<p>Own Id: OTP-5662 Aux Id: seq10004, seq9988 </p>

      </item>

      <item>

	<p>[ftp, client] Enhanced error handling, mainly so the ftp

	  client behaves gracefully when the user does strange

	  things such as violate the user API.</p>

	<p>Own Id: OTP-5665</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>[ftp, client] Added open option: mode.Deprecates

	  function force_active/1.</p>

	<p>Own Id: OTP-5663</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.5.1</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>[http, server] The server did not handle the config 

	  directive BindAddress value "*" properly. 

	  When creating the option list for the listen call, 

	  everything beside the atom undefined (if BindAddress 

	  was never given) and an 4-tuple (e.g. BindAddress

	  value is 192.168.0.30) was incorrectly assumed to be 

	  an ipv6 address. 

	  For undefined (no BindAddress), Inets attempts to 

	  figure out if it is running on a ipv6-machine, and if

	  so, add the inet6 option when calling listen. The 

	  same approach should be used when BindAddress is 

	  assigned the value "*".</p>

	<p>Own Id: OTP-5642</p>

      </item>

      <item>

	<p>Some data doesn't pass through http_base_64:decode/1 correctly.

	  The decoding routine fails whenever a 4-character group of the 

	  encoding ends with "9" or "99". If it ends with 99, two bytes 

	  will be lost in the decode routine. If it ends with a single 9, 

	  one byte will be lost in the decode.</p>

	<p>Own Id: OTP-5635 Aux Id: seq9971</p>

      </item>

      <item>

	<p>[http, server,esi] Web server does not handle status-code 

	  returned by an esi function. I.e. the esi-function 

	  can no longer control the status code.</p>

	<p>Own Id: OTP-5648 Aux Id: seq9982</p>

      </item>

      <item>

	<p>[http, server,esi] Corrected header format. First character 

	  was lower case, and there where no space after the ":"

	  character, example: content-length:0. Now, first character 

	  was upper case, and a space after the ":" character, 

	  example: Content-Length: 0 (To preserve

	  backward compatibility with the de-facto standard as the

	  new way does not break the HTTP standard!)</p>

	<p>Own Id: OTP-5649 Aux Id: seq9982</p>

      </item>

      <item>

	<p>[http, server, cgi] Parsing of the status header field could

	  cause a crash.</p>

	<p>Own Id: OTP-5650 Aux Id: seq9982</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.5</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>The internal design of using blocking gen_tcp:recv with a

	  timeout and retries resulted in code that was hard to get

	  a good overview of, and ultimate led to situations where

	  the client got the wrong answer or no answer at all. The

	  errors where many times very timing dependent and mainly

	  effected the chunk-related functions, so if you where

	  lucky you probably would not have noticed. The internal

	  design was changed to use gen_tcp active once semantics.

	  The API is not effected except for the function

	  ftp:quote/2 which now returns a list of strings (ftp

	  result lines) where the line endings "\r\n" has been

	  removed. This was the original intention for the return

	  value of ftp:quote/2 but it was non trivial to make a

	  good such solution with the old design and a compromise

	  was made.</p>

	<p>*** POTENTIAL INCOMPATIBILITY ***</p>

	<p>Own Id: OTP-5623</p>

      </item>

      <item>

	<p>The new implementation of pipelining in inets-4.1 alas

	  was slightly broken and unfortunately not caught by the

	  test suite that apparently needs some additions. The

	  result was that requests that ought to have been

	  pipelined where not, this has now been fixed.</p>

	<p>Own Id: OTP-5624</p>

      </item>

      <item>

	<p>When using the latest esi interface with the callback

	  interface of arity 3, HTTP Content-Type headers where

	  ignored, this due to a subtle difference between this

	  interface and the old one in how they viewed HTTP

	  delimiters.</p>

	<p>Own Id: OTP-5627</p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>The HTTP server now supports ipv6 in the case that the

	  underlying mechanisms also do so. (ssl does not yet

	  support ipv6.)</p>

	<p>Own Id: OTP-5141</p>

      </item>

      <item>

	<p>The FTP client now supports ipv6 in the case that the

	  underlying mechanisms also do so.</p>

	<p>Own Id: OTP-5142</p>

      </item>

      <item>

	<p>An option was added to disable the ipv6 support in the

	  HTTP client. This to provide a workaround possibility for

	  buggy ipv6-stacks.</p>

	<p>Own Id: OTP-5625 Aux Id: seq9872</p>

      </item>

      <item>

	<p>When generating dynamic HTTP response bodies the the

	  default content-type is now set to "text/html" instead of

	  "text/plain" which is more intuitive.</p>

	<p>*** POTENTIAL INCOMPATIBILITY ***</p>

	<p>Own Id: OTP-5626</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.4.1</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>Wrapper function http_transport:accept/3 did

	  error-handling that it should not do because only the

	  caller of the wrapper can determine what action to take.

	  So timeouts where handled twice, once in http_transport

	  and once in httpd_acceptor. Clean up of the wrapper

	  module http_transport changed the action of the wrapper

	  module and made the unwanted behavior noticeable in in

	  OTP error logs. And now the unwanted error handling has

	  been removed. The cleanup helped us find bad code but

	  alas it also generates a lot of log printouts that are

	  quite disturbing to the user of the HTTP-server.</p>

	<p>Own Id: OTP-5549 Aux Id: seq9851 </p>

      </item>

      <item>

	<p>In the rewrite for 4.4 some mod_esi-environment values

	  where mistaken for ordinary header values and where

	  incorrectly transformed to strings. They are now atoms

	  again.</p>

	<p>Own Id: OTP-5551 Aux Id: seq9854 </p>

      </item>

      <item>

	<p>The HTTP server now handles 

          "GET /\r\n\r\n"

	  as well as

	  "GET / \r\n\r\n". 

          According to the RFC the whitespace is not needed.</p>

	<p>Own Id: OTP-5552 Aux Id: seq8426 </p>

      </item>

    </list>

  </section>

  <section>

    <title>Improvements and New Features</title>

    <list type="bulleted">

      <item>

	<p>The ftp client now supports passive mode. Actually the

	  ftp client will always try to use passive mode and if it

	  fails it will use active mode instead. It is also

	  possible to force the ftp-client to use active mode, if

	  that is desired, by calling ftp:force_active/1 this way

	  you can get the old behavior.</p>

	<p>*** POTENTIAL INCOMPATIBILITY ***</p>

	<p>Own Id: OTP-5148</p>

      </item>

    </list>

  </section>

  </section>

  <section>

  <title>Inets 4.4</title>

  <section>

    <title>Fixed Bugs and Malfunctions</title>

    <list type="bulleted">

      <item>

	<p>The server did not handle HTTP-0.9 messages with an

	  implicit version.</p>

	<p>Own Id: OTP-5513</p>

      </item>

      <item>

	<p>An internal server timeout killed the request handling

	  process without sending a message back to the client. As

	  this timeout only affects a single request it has been