-fixed action header for soap12 requests to contain action rather than operation;
-added namespace registry to allow for wsdl inline schemas in different namespaces
-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
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
Make the mime types mappings configurable

Now, it possible to customize the global mime types mappings and to overload
it for each virtual server. It can be done using following directives in the
global part or the server part of the configuration:

* default_type: Defines the default mime type to be used where Yaws cannot
  determine it by its mime types mappings (default: text/plain).
  In the server part, this directive overloads the global one.

* default_charset: Defines the default charset to be added when a response
  content-type is text/* (default: none). In the server part, this directive
  overloads the global one.

* mime_types_file: Overrides the default mime.types file included with Yaws
  (default: ${PREFIX}/lib/yaws/priv/mime.types). In the server part, this
  directive overloads the global one but mappings defined in this file will
  not overload those defined by add_types directives in the global part.

* add_types: Specifies one or more mappings between mime types and file
  extensions. More than one extension can be assigned to a mime type. If a
  mapping is defined in the global part and redefined in a server part using
  this directive, then the later is used. Else the global one is kept.

* add_charsets: Specifies one or more mappings between charsets and file
  extensions. More than one extension can be assigned to a charset. If a
  mapping is defined in the global part and redefined in a server part using
  this directive, then the later is used. Else the global one is kept.

Here is an example:

  default_type = text/html

  <server localhost>
      port = 8000
      listen = 0.0.0.0
      docroot = /var/www
      # nothing is overloaded in the vhost
  </server>

  <server localhost>
      port = 8001
      listen = 0.0.0.0
      docroot = /var/www

      # overload global configuration:
      default_type    = text/plain
      mime_types_file = /etc/mime.types
      add_types       = <text/xhtml, yaws> <application/x-test, tst test>
      default_charset = UTF-8
      add_charsets    = <ISO-8859-1, php html yaws> <US-ASCII, tst>
  </server>

During Yaws compilation, a default module 'mime_types' is created using the
default mime.types file. Then, when yaws starts up, this module is
re-generated, re-compiled and loaded dynamically. The new module replaces the
default one but the .beam file is unchanged. So if one of these steps failed,
we fall back on the default module.
Check missing fields in yaws_config:eq_sconfs/2
Improve how Yaws is started in embedded mode

The main change concerns the function yaws:create_sconf/2. Now, this function
relies on yaws_config:make_default_sconf/2 to create a default #sconf record.
Add basic websocket test.

It performs the handshake, then sends one text message and checks
that it is echoed back correctly.
fix setting of yawsid_opts variable in OS X startup script
support Raspberry Pi in configure.in (Anders Nygren)
Merge pull request #121 from jbothma/master

Add basic websocket test.