remove unnecessary inet:setopts from server-sent events example
remove duplicate entry from 1.94 news
Fix parse_set_cookie/1 and format_set_cookie/1 functions

1. According to the RFCs 2109 and 2965, multiple cookies can be set in a
single 'Set-Cookie' header. So, yaws_api:parse_set_cookie/1 now returns a
list of #setcookie{} records. If no cookie was found or if an error occurred,
it returns []. The parsing is also improved.
Note that this fix breaks the compatibility with previous versions.

2. In yaws_api:format_set_cookie/1, options are now always formated as
quoted-strings.

3. 2 new functions are added, yaws_api:parse_cookie/1 and
yaws_api:format_cookie/1, to parse and format 'Cookie' headers. To let these
functions to work, the #cookie{} record was introduced.

Documentation and testsuite are updated accordingly.
-fixed action header for soap12 requests to contain action rather than operation;
-added namespace registry to allow for wsdl inline schemas in different namespaces
Sync with upstream rebar node template
Merge pull request #113 from tuncer/reltool-update

Sync with upstream rebar node template
minor changes to server-sent events

Change yaws_sse to send close connection header by default, and change the
example to return an Allow header if anything other than GET is requested.
-enabled http client library options customization
added export for the newly introduced call/8
added customization for ibrowse timeout parameter since it is not overridable
Refactor Set-Cookie/Cookie header parsing to follow RFC6265

RFC6265 obsoletes RFC2965 and RFC2109. #setcookie{} and #cookie{} are
changed to reflect this new RFC. So, yaws_api:parse_set_cookie/1 and
yaws_api:parse_cookie/1 are refactored accordingly:

* yaws_api:parse_set_cookie/1: Because RFC2109 and RFC2965 are still used,
  we try to be backward compatible with these old RFCs. So this function
  returns a #setcookie{} record when only one cookie is found else it returns
  a list of #setcookie{} records.
  in RFC2109 and RFC2965, cookies are separated by comma. So, comma is
  forbidden in 'path-av' and 'extension-av' except for double-quoted value.
  The parsing are not really strict because of the compatibility and can lead
  to unwanted behaviors.
  Old attributes (like 'Comment' or 'Port') are still parsed and can be
  found into #setcookie.extensions field.

* yaws_api:parse_cookie/1: This function follows the RFC6265, so all cookie
  attributes (like '$Domain' or '$Path') are parsed like any other cookie.
Fix test on the return value of peername/2 in close_accepted_if_max/2
minor changes to server-sent events

Change yaws_sse to send close connection header by default, and change the
example to return an Allow header if anything other than GET is requested.
wrap SSL sockets in tuple

Yaws previously internally used details of an SSL socket representation
that's supposed to be private/opaque to Erlang's SSL support. Encapsulate
SSL sockets within a {ssl, SslSocket} tuple and add the
yaws_api:get_sslsocket/1 function that returns a socket for SSL sockets or
undefined for non-SSL sockets. Also document the new get_sslsocket/1
function and other minor tweaks to SSL areas of the documentation.
Add index_files directive into the server part configuration

This directive sets the list of resources to look for, when a directory is
requested by the client. If the last entry begins with a "/", and none of
the earlier resources are found, Yaws will perform a redirect to this uri.

Default is:
  index_files = index.yaws index.html index.php
server_sent_events: end gen_server process if send fails
Merge pull request #116 from sumup/feature/soap12_imports_namespaces

Feature/soap12 imports namespaces
Sync rel/files/yaws with upstream template
Merge pull request #117 from tuncer/noderunner

Sync rel/files/yaws with upstream template
Fix return value of yaws_server:is_auth/2 when no auth structure is found