Fix handling of multipart boundary markers at input boundaries
optimized ssi code by storing binaries as the data chunks instead of lists of chars
Keep the original request in #arg{} and check it against auth rules

Because the request can be rewritten, it could be useful to backup the
original one. Appmods or Yaws scripts could access it by reading the field
orig_reg in #arg{}. For CGI scripts, the variable REQUEST_URI is now built
using the original request (SCRIPT_NAME, PATH_INFO and QUERY_STRING could
be used to know the info about the rewritten request, if needed).

The original request is also checked against the authorization rules. So, if
the request is rewritten, Yaws will check the original request and the
rewritten one. Access must be granted for both urls to accept the request.
Support message body in DELETE requests

The HTTP/1.1 specification does not explicitly forbid message body in
DELETE requests.
In fact, it is only forbidden in TRACE requests (rfc2616 - section 9.8).
So GET, HEAD and OPTION requests could contain message body. But it needs
more work to support message body in these requests.
Group automatically the server configurations in embedded mode

Now, Yaws groups the server configurations by itself when it is started
in embedded mode. This is done when yaws_api:setconf/2 is called.
Use crypto:hash instead of crypto:sha to be compatible with R16B1.
Merge pull request #146 from kape1395/master

Yaws cannot be compiled with R16B1.
rel: sync files with upstream templates
changes for R16B01

In R16B01, crypto:sha/1 is deprecated in favor of crypto:hash/2, but the
latter is not available prior to R15B02. Change the configure script and
rebar support to look for crypto:hash/2 and use it if found, otherwise fall
back to crypto:sha/1.

Also in R16B01 the public_key application, used by some of the tests, now
requires the asn1 application to be started first. Change the tests to
accommodate that.
Merge pull request #147 from tuncer/rel

rel: sync files with upstream templates
Fix configure checks requiring module loading

After 98db40b the check outputs:

    $ erl -noshell -eval 'code:load_file(file), io:format("~p~n",[[erlang:function_exported(file,sendfile,5)]]), erlang:halt().'
    [true]

    =ERROR REPORT==== 25-Jun-2013::09:40:51 ===
    Can't load module that resides in sticky dir

Use code:ensure_loaded/1 instead as suggested by Tuncer Ayaz. Fix similar
module loading check in rebar.config.script.
Use proper linker command for drivers on OpenBSD

This fixes the "Cannot load specified object" / setuid_drv.so: undefined symbol '__guard_local' error that occurs on OpenBSD 5.3. It changes the LD_SHARED variable to use gcc rather than ld. A similar issue is documented here: http://erlang.org/pipermail/erlang-questions/2013-May/073837.html. Tested on OpenBSD 5.3 and FreeBSD 9.
Merge pull request #151 from fjoanis/master

Fix runtime error on OpenBSD 5.3
Try to make the log directory if it doesn't exist

This uses @capflam's patch from https://github.com/klacke/yaws/pull/145
to create the log directory if specified like

    logdir = +path/to/log

in the configuration file.
Merge remote-tracking branch 'MrStaticVoid/yaws-1.96/try-to-create...

...-log-dir-if-specified-in-config'
export yaws:setup_sconf/2 for yapp

The yapp application relies on the yaws:setup_sconf/2 function, but at some
point it was made private to yaws.erl. Export it so yapp works properly
again.
yaws_session_server:print_sessions/0 not working due incorrect message
Merge pull request #155 from mdaguete/session_server_fixes

yaws_session_server:print_sessions/0 not working due incorrect message
When max connections were reached and we attempt to close the socket, it was assumed we had a TCP socket, crashed on SSL sockets
Merge branch 'master' of github.com:klacke/yaws