3 HTTP Client

The HTTP client default profile will be started when the inets
application is started and is then available to all processes on
that erlang node. Other profiles may also be started at
application startup, or profiles can be started and stopped
dynamically in runtime. Each client profile will spawn a new
process to handle each request unless there is a possibility to use
a persistent connection with or without pipelining.
The client will add a host header and an empty
te header if there are no such headers present in the request.

The client supports ipv6 as long as the underlying mechanisms also do
so.