Fix option to enable/disable sendfile support in the configure script

Now it is possible to disable sendfile in yaws passing the option
'--disable-senfile' (or '--enable-sendfile=no') to the configure script.
It is also possible to choose between the erlang implementation (the default)
and the yaws implementation.
Make the #gconf.large_file_chunk_size value be configurable
Add support of many options for tcp/ssl sockets

By adding a "<listen_opts> ... </listen_opts>" block in vhosts
configuration, it is possible to define some options to be set on listen
sockets and, by inheritance, on accepted sockets. Supported options are
(see inet:setopts for details):

  * buffer
  * delay_send
  * linger
  * nodelay
  * priority
  * sndbuf
  * recbuf
  * send_timeout
  * send_timeout_close

send_timeout / send_timeout_close options could be very useful to handle
unresponsive clients and thus avoid some sorts of DoS.
Add the way to configure the version of sendfile method to use

Now, at compile time, we only check if sendfile syscall and file:sendfile/5
are supported. Then, dynamically, we can configure which version to use.
This can be done using the directive large_file_sendfile. Supported values
are:

 * erlang: if supported, use file:sendfile/5
 * yaws: if supported, use the Yaws sendfile linked-in driver
 * disable: do not use any sendfile method, but gen_tcp:send/2

If an unsupported method is configured, we fall back on gen_tcp:send/2.

file:sendfile/5 implementation is buggy (in R15 & R16). When async-threads
are enabled, in efile driver, the tcp socket is set in blocking mode and the
sendfile syscall is executed on an async-thread. So an unresponsive client
could block it for a very long time and therefore block the async-thread.
In this way, all async-threads could be easily blocked.
So, by default, the use of sendfile is disable.
Adjust line numbers in known_dialyzer_warnings file
Add note about running rebar get-deps before rebar compile

I was trying to install with rebar compile and kept getting the failure
that the ibrowse dependency wasn't available. Once I did a rebar get-deps,
the rebar compile seemed to have gone through.
Add README.osx for instructions on installing on OSX using Homebrew
Fix typo in yaws_sendfile module
Fix mime_types.erl generation for a local installation of Yaws

Without this fix, at the Yaws startup, the mime_types.erl generation fails
on windows when Yaws is installed using the installer. It also fails for
Yaws releases built with reltool (using rebar or autotools).

Fix issue #161.
Remove authmod_gssapi from the module list in src/Makefile

This module was moved a long time ago in example/src.
preparing for yaws 1.97
fix rebar.config.script for YAWS_SOAP build
Use Yaws linked-in driver by default to send large file

In a previous commit (c887a374), the use of sendfile (OTP and Yaws versions)
was disabled. The OTP version is buggy, so we recommand to not use
it. But the Yaws linked-in driver can safely be used. So, there is no reason
to not use it. Now, it is the default method.
rebar compile eunit compile_only=true fails for yaws

Changes to allow yaws to be compiled by rebar for eunit testing.  This
change is helpful when embedding yaws as a dependency of an Erlang
application.
Bad HTTP 3.0 message sent to yaws, crashed the server entirely
prepare for 1.98
change use of sendfile flag macros for Erlang R13

Change the use of the macros used to set sendfile configuration flags in
yaws_config.erl so the code works on older versions of Erlang/OTP,
specifically the R13 versions. Tested with R13B04.
enhance "tests passed" messages to include test dir
generate empty priv/charset.def for rebar builds
fix broken srcdir tests

Commit a04e38a fixed building the tests with rebar, but broke the
test/t11/srcdir tests when built and run with make. This commit reworks the
approach to allow the tests to run correctly and also build correctly with
rebar.