Merge branch 'bmk/inets/inets57_integration2' into maint-r14

* bmk/inets/inets57_integration2:
  Fixed non-related test case (ticket_6035).
  Corrected appup-file (missing ',').
  Fixed ipv6 support detection.
  (httpc) test case cleanups.
  Uppdated appup-file.
  Fixed IPv6 test case selection. That is if a IPv6 test case should be run or not.
  Stopping httpc client...
  Added test cases for httpd.
  Clients started stand-alone not properly handled.
  Clients started stand-alone not properly handled.
  Temporary solution for profile_name stuff. What about Pids???
  SSL with IPv6 now works "in principle".
  [httpc] Remove unnecessary usage of iolist_to_binary when processing body (for PUT and POST). Filipe David Manana OTP-9317
  Set proper version (5.7).
  Set proper version (5.7).
  Updated release notes.
  Peer/sockname resolv doesn't work with IPv6 addrs in HTTP. OTP-9343
  OTP-9342: FTP client doesn't work with IPv6 OTP-9342: IpFamily config option was not handled OTP-9342: Release notes remain... OTP-9342: <credit>attila rajmund nohl</credit>

1 files changed, 89 insertions, 91 deletions

diff --git a/lib/inets/doc/src/httpc.xml b/lib/inets/doc/src/httpc.xml
index f6b6827e93..d1671ac9bd 100644
--- a/lib/inets/doc/src/httpc.xml
+++ b/lib/inets/doc/src/httpc.xml
@@ -144,7 +144,7 @@ filename()       = string()
 	<v>Result = {status_line(), headers(), Body} | 
                     {status_code(), Body} | request_id() </v>
 	<v>Body = string() | binary()</v>
-	<v>Profile = profile()</v>
+	<v>Profile = profile() | pid() (when started <c>stand_alone</c>)</v>
 	<v>Reason = term() </v>
       </type>
       <desc>
@@ -194,16 +194,16 @@ filename()       = string()
         <v>Result = {status_line(), headers(), Body} | 
                     {status_code(), Body} | request_id() </v>
         <v>Body = string() | binary()</v>
-        <v>Profile = profile() </v>
+        <v>Profile = profile() | pid() (when started <c>stand_alone</c>)</v>
         <v>Reason = {connect_failed, term()} | 
                     {send_failed, term()} | term() </v>
       </type>
 
       <desc>
         <p>Sends a HTTP-request. The function can be both synchronous
-          and asynchronous. In the later case the function will return
-          <c>{ok, RequestId}</c> and later on the information will be delivered
-          to the <c>receiver</c> depending on that value. </p>
+	and asynchronous. In the later case the function will return
+	<c>{ok, RequestId}</c> and later on the information will be delivered
+	to the <c>receiver</c> depending on that value. </p>
 
         <p>Http option (<c>http_option()</c>) details: </p>
         <taglist>
@@ -211,7 +211,7 @@ filename()       = string()
           <item>
             <p>Timeout time for the request. </p>
             <p>The clock starts ticking as soon as the request has been
-              sent. </p>
+	    sent. </p>
             <p>Time is in milliseconds. </p>
             <p>Defaults to <c>infinity</c>. </p>
 	  </item>
@@ -219,7 +219,7 @@ filename()       = string()
           <tag><c><![CDATA[connect_timeout]]></c></tag>
           <item>
             <p>Connection timeout time, used during the initial request, 
-              when the client is <em>connecting</em> to the server. </p>
+	    when the client is <em>connecting</em> to the server. </p>
             <p>Time is in milliseconds. </p>
             <p>Defaults to the value of the <c>timeout</c> option. </p>
 	  </item>
@@ -227,60 +227,61 @@ filename()       = string()
           <tag><c><![CDATA[ssl]]></c></tag>
           <item>
             <p>This is the default ssl config option, currently defaults to 
-              <c>essl</c>, see below. </p>
+	    <c>essl</c>, see below. </p>
             <p>Defaults to <c>[]</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[ossl]]></c></tag>
           <item>
             <p>If using the OpenSSL based (old) implementation of SSL, 
-              these SSL-specific options are used. </p>
+	    these SSL-specific options are used. </p>
             <p>Defaults to <c>[]</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[essl]]></c></tag>
           <item>
             <p>If using the Erlang based (new) implementation of SSL, 
-              these SSL-specific options are used. </p>
+	    these SSL-specific options are used. </p>
             <p>Defaults to <c>[]</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[autoredirect]]></c></tag>
           <item>
-            <p>Should the client automatically retrieve the information
-              from the new URI and return that as the result instead 
-              of a 30X-result code. </p>
-            <p>Note that for some 30X-result codes automatic redirect 
-              is not allowed. In these cases the 30X-result will always
-              be returned. </p>
-            <p>Defaults to <c>true</c>. </p>
+	    <p>Should the client automatically retrieve the information
+	    from the new URI and return that as the result instead 
+	    of a 30X-result code. </p>
+	    <p>Note that for some 30X-result codes automatic redirect 
+	    is not allowed. In these cases the 30X-result will always
+	    be returned. </p>
+	    <p>Defaults to <c>true</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[proxy_auth]]></c></tag>
           <item>
             <p>A proxy-authorization header using the provided user name and 
-              password will be added to the request. </p>
+	    password will be added to the request. </p>
 	  </item>
 
           <tag><c><![CDATA[version]]></c></tag>
           <item>
             <p>Can be used to make the client act as an <c>HTTP/1.0</c> or
-	      <c>HTTP/0.9</c> client. By default this is an <c>HTTP/1.1</c> 
-              client. When using <c>HTTP/1.0</c> persistent connections will 
-              not be used. </p>
-            <p>Defaults to the string <c>"HTTP/1.1"</c>. </p>
+	    <c>HTTP/0.9</c> client. By default this is an <c>HTTP/1.1</c> 
+	    client. When using <c>HTTP/1.0</c> persistent connections will 
+	    not be used. </p>
+	    <p>Defaults to the string <c>"HTTP/1.1"</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[relaxed]]></c></tag>
           <item>
-            <p>If set to <c>true</c> workarounds for known server deviations from
-	      the HTTP-standard are enabled. </p>
+            <p>If set to <c>true</c> workarounds for known server deviations 
+	    from the HTTP-standard are enabled. </p>
             <p>Defaults to <c>false</c>. </p>
 	  </item>
 
 	  <tag><c><![CDATA[url_encode]]></c></tag>
           <item>
-            <p>Will apply Percent-encoding, also known as URL encoding on the URL.</p>
+            <p>Will apply Percent-encoding, also known as URL encoding on the 
+	    URL.</p>
 	    <p>Defaults to <c>false</c>. </p>
 	  </item>
         </taglist>
@@ -296,77 +297,77 @@ filename()       = string()
           <tag><c><![CDATA[stream]]></c></tag>
           <item>
             <p>Streams the body of a 200 or 206 response to the calling 
-	      process or to a file. When streaming to the calling process 
-	      using the option <c>self</c> the following stream messages
-	      will be sent to that process: <c>{http, {RequestId,
-	      stream_start, Headers}, {http, {RequestId, stream,
-	      BinBodyPart}, {http, {RequestId, stream_end, Headers}</c>. When
-	      streaming to to the calling processes using the option
-	      <c>{self, once}</c> the first message will have an additional
-	      element e.i. <c>{http, {RequestId, stream_start, Headers, Pid}</c>,
-	      this is the process id that should be used as an argument to
-	      <c>http:stream_next/1</c> to trigger the next message to be sent to
-	      the calling process. </p>
+	    process or to a file. When streaming to the calling process 
+	    using the option <c>self</c> the following stream messages
+	    will be sent to that process: <c>{http, {RequestId,
+	    stream_start, Headers}, {http, {RequestId, stream,
+	    BinBodyPart}, {http, {RequestId, stream_end, Headers}</c>. When
+	    streaming to to the calling processes using the option
+	    <c>{self, once}</c> the first message will have an additional
+	    element e.i. <c>{http, {RequestId, stream_start, Headers, Pid}</c>,
+	    this is the process id that should be used as an argument to
+	    <c>http:stream_next/1</c> to trigger the next message to be sent to
+	    the calling process. </p>
 	    <p>Note that it is possible that chunked encoding will add
-	      headers so that there are more headers in the <c>stream_end</c>
-	      message than in the <c>stream_start</c>.
-	      When streaming to a file and the request is asynchronous the
-	      message <c>{http, {RequestId, saved_to_file}}</c> will be sent. </p>
+	    headers so that there are more headers in the <c>stream_end</c>
+	    message than in the <c>stream_start</c>.
+	    When streaming to a file and the request is asynchronous the
+	    message <c>{http, {RequestId, saved_to_file}}</c> will be sent. </p>
             <p>Defaults to <c>none</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[body_format]]></c></tag>
           <item>
             <p>Defines if the body shall be delivered as a string or as a 
-              binary. This option is only valid for the synchronous 
-              request. </p>
+	    binary. This option is only valid for the synchronous 
+	    request. </p>
             <p>Defaults to <c>string</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[full_result]]></c></tag>
           <item>
             <p>Should a "full result" be returned to the caller (that is,
-              the body, the headers and the entire status-line) or not 
-              (the body and the status code). </p>
+	    the body, the headers and the entire status-line) or not 
+	    (the body and the status code). </p>
             <p>Defaults to <c>true</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[header_as_is]]></c></tag>
           <item>
             <p>Shall the headers provided by the user be made 
-              lower case or be regarded as case sensitive. </p>
+	    lower case or be regarded as case sensitive. </p>
             <p>Note that the http standard requires them to be 
-              case insenstive. This feature should only be used if there is 
-              no other way to communicate with the server or for testing 
-              purpose. Also note that when this option is used no headers 
-              will be automatically added, all necessary headers have to be
-              provided by the user. </p>
-            <p>Defaults to <c>false</c>. </p>
+	    case insenstive. This feature should only be used if there is 
+	    no other way to communicate with the server or for testing 
+	    purpose. Also note that when this option is used no headers 
+	    will be automatically added, all necessary headers have to be
+	    provided by the user. </p>
+	    <p>Defaults to <c>false</c>. </p>
 	  </item>
 
           <tag><c><![CDATA[socket_opts]]></c></tag>
           <item>
             <p>Socket options to be used for this and subsequent 
-              request(s). </p>
-            <p>Overrides any value set by the 
-              <seealso marker="#set_options">set_options</seealso>
-              function. </p>
+	    request(s). </p>
+	    <p>Overrides any value set by the 
+	    <seealso marker="#set_options">set_options</seealso>
+	    function. </p>
             <p>Note that the validity of the options are <em>not</em>
-              checked in any way. </p>
+	    checked in any way. </p>
             <p>Note that this may change the socket behaviour 
-              (see <seealso marker="kernel:inet#setopts/2">inet:setopts/2</seealso>) 
-              for an already existing one, and therefore an already connected
-              request handler. </p>
+	    (see <seealso marker="kernel:inet#setopts/2">inet:setopts/2</seealso>) 
+	    for an already existing one, and therefore an already connected
+	    request handler. </p>
             <p>By default the socket options set by the
-              <seealso marker="#set_options">set_options/1,2</seealso> 
-              function are used when establishing a connection. </p>
+	    <seealso marker="#set_options">set_options/1,2</seealso> 
+	    function are used when establishing a connection. </p>
 	  </item>
 
           <tag><c><![CDATA[receiver]]></c></tag>
           <item>
             <p>Defines how the client will deliver the result of an
-              asynchroneous request (<c>sync</c> has the value 
-              <c>false</c>). </p>
+	    asynchroneous request (<c>sync</c> has the value 
+	    <c>false</c>). </p>
 
             <taglist>
               <tag><c><![CDATA[pid()]]></c></tag>
@@ -380,7 +381,7 @@ filename()       = string()
               <tag><c><![CDATA[function/1]]></c></tag>
               <item>
 	        <p>Information will be delivered to the receiver via calls 
-                  to the provided fun: </p>
+		to the provided fun: </p>
 <pre>
 Receiver(ReplyInfo)
 </pre>
@@ -389,7 +390,7 @@ Receiver(ReplyInfo)
               <tag><c><![CDATA[{Module, Funcion, Args}]]></c></tag>
               <item>
 	        <p>Information will be delivered to the receiver via calls 
-                  to the callback function: </p>
+		to the callback function: </p>
 <pre>
 apply(Module, Function, [ReplyInfo | Args])
 </pre>
@@ -410,7 +411,7 @@ apply(Module, Function, [ReplyInfo | Args])
 </pre>
 
             <p>Defaults to the <c>pid()</c> of the process calling the request 
-              function (<c>self()</c>). </p>
+	    function (<c>self()</c>). </p>
 	  </item>
         </taglist>
 
@@ -425,7 +426,7 @@ apply(Module, Function, [ReplyInfo | Args])
       <type>
         <v>RequestId = request_id() - A unique identifier as returned
         by request/4</v>
-	<v>Profile = profile()</v>
+	<v>Profile = profile() | pid() (when started <c>stand_alone</c>)</v>
       </type>
       <desc>
         <p>Cancels an asynchronous HTTP-request. </p>
@@ -514,11 +515,10 @@ apply(Module, Function, [ReplyInfo | Args])
           This option is used to switch on (or off) 
           different levels of erlang trace on the client. 
           It is a debug feature.</d>
-	<v>Profile = profile()</v>
+	<v>Profile = profile() | pid() (when started <c>stand_alone</c>)</v>
       </type>
       <desc>
-        <p>Sets options to be used for subsequent
-          requests.</p>
+        <p>Sets options to be used for subsequent requests.</p>
         <note>
           <p>If possible the client will keep its connections
             alive and use persistent connections
@@ -548,7 +548,7 @@ apply(Module, Function, [ReplyInfo | Args])
       </type>
       <desc>
         <p>Triggers the next message to be streamed, e.i.
-	  same behavior as active once for sockets.</p>
+	same behavior as active once for sockets. </p>
 
         <marker id="verify_cookies"></marker>
         <marker id="store_cookies"></marker>
@@ -562,14 +562,14 @@ apply(Module, Function, [ReplyInfo | Args])
       <type>
         <v>SetCookieHeaders = headers() - where field = "set-cookie"</v>
         <v>Url = url()</v>
-	<v>Profile = profile()</v>
+	<v>Profile = profile() | pid() (when started <c>stand_alone</c>)</v>
       </type>
       <desc>
         <p>Saves the cookies defined in SetCookieHeaders
-          in the client profile's cookie database. You need to
-          call this function if you have set the option <c>cookies</c> to <c>verify</c>.
-	  If no profile is specified the default profile will be used.
-	</p>
+	in the client profile's cookie database. You need to
+	call this function if you have set the option <c>cookies</c> 
+	to <c>verify</c>.
+	If no profile is specified the default profile will be used. </p>
 
         <marker id="cookie_header"></marker>
       </desc>
@@ -582,13 +582,12 @@ apply(Module, Function, [ReplyInfo | Args])
       making a request to Url using the profile <c>Profile</c>.</fsummary>
       <type>
         <v>Url = url()</v>
-	<v>Profile = profile()</v>
+	<v>Profile = profile() | pid() (when started <c>stand_alone</c>)</v>
       </type>
       <desc>
         <p>Returns the cookie header that would be sent
-          when making a request to <c>Url</c> using the profile <c>Profile</c>.
-	  If no profile is specified the default profile will be used.
-	</p>
+	when making a request to <c>Url</c> using the profile <c>Profile</c>.
+	If no profile is specified the default profile will be used. </p>
 
         <marker id="reset_cookies"></marker>
       </desc>
@@ -600,12 +599,12 @@ apply(Module, Function, [ReplyInfo | Args])
       <name>reset_cookies(Profile) -> void()</name>
       <fsummary>Reset the cookie database.</fsummary>
       <type>
-	<v>Profile = profile()</v>
+	<v>Profile = profile() | pid() (when started <c>stand_alone</c>)</v>
       </type>
       <desc>
-        <p>Resets (clears) the cookie database for the specified <c>Profile</c>.
-	  If no profile is specified the default profile will be used.
-	</p>
+        <p>Resets (clears) the cookie database for the specified 
+	<c>Profile</c>. If no profile is specified the default profile 
+	will be used. </p>
       </desc>
     </func>
 
@@ -615,17 +614,16 @@ apply(Module, Function, [ReplyInfo | Args])
       <name>which_cookies(Profile) -> cookies()</name>
       <fsummary>Dumps out the entire cookie database.</fsummary>
       <type>
-	<v>Profile = profile()</v>
-	<v>cookies() = [cooie_stores()]</v>
-	<v>cookie_stores() = {cookies, icookies()} | {session_cookies, icookies()}</v>
-	<v>icookies() = [icookie()]</v>
+	<v>Profile = profile() | pid() (when started <c>stand_alone</c>)</v>
+	<v>cookies() = [cookie_stores()]</v>
+	<v>cookie_stores() = {cookies, cookies()} | {session_cookies, cookies()}</v>
+	<v>cookies() = [cookie()]</v>
 	<v>cookie() = term()</v>
       </type>
       <desc>
         <p>This function produces a list of the entire cookie database.
-          It is intended for debugging/testing purposes. 
-	  If no profile is specified the default profile will be used.
-	</p>
+	It is intended for debugging/testing purposes. 
+	If no profile is specified the default profile will be used. </p>
       </desc>
     </func>
   </funcs>