first cut at mochiweb rtsp server
remove old default http method clauses
small changes to debug
removed frm because it was unused
removed mochiweb_rtsp*
fix zd864: long HTTP header lines not handled properly

Due to Erlang bug OTP-9389, the handling of HTTP request header lines
that exceed the size of the gen_tcp receive buffer is broken when
using {packet,http} and {packet,httph} modes.

Modify mochiweb to work around this bug by using {packet,line} mode
instead to collect request header lines and then using
erlang:decode_packet to parse them. Using {packet,line} allows us to
avoid reading past the headers into the request body (if present),
since doing that would require us to carry the body data from the
header handling functions over into the body handling functions, which
could be a pretty intrusive and complicated change.

Also add regression unit tests that verify that long HTTP request
lines and long HTTP header lines are handled correctly.
HttpError parses are returned as normal packets, not error tuples.
Merge pull request #2 from basho/bz1291-http-error-packets

BZ1291 HttpError packet parsing fix
Merge branch 'master' of https://github.com/mochi/mochiweb into dev
Lastest from https://github.com/mochi/mochiweb.git as of April 19, 2012
exit with meaningful error messages
Latest from https://github.com/mochi/mochiweb.git as of April 20, 2012
Prevent some unnecessary socket exceptions
Got latest from https://github.com/jdhood1/mochiweb.git
bump to 2.3.2, Case insensitive match for "Connection: close" (#81)
modify mochijson2 to handle and return 'undefined' instead of 'null'
erlang:now() -> os:timestamp

We don't need to use an expensive monotonic clock for calcuating timing
information.
Merge pull request #4 from basho/adt-os-timestamp

erlang:now() -> os:timestamp
The range-header handling does not implement the following:
http://tools.ietf.org/html/rfc2616#section-14.35.1

  If the last-byte-pos value is absent, or if
  the value is greater than or equal to the current
  length of the entity-body, last-byte-pos is taken
  to be equal to one less than the current length of
  the entity-body in bytes.

Specifically, the 'greater than equal to' case.
add ability to handle combined content-length header.