Don't have double content-length headers snoyberg/keter#52

Pinging @kazu-yamamoto. Can you review this patch? The issue is that,
currently, any responseFile respone which sets content-length ends up
with two content-length headers. I'm also going to patch wai-app-static
to not provide a content-length header, since it's incorrect in the case
of range requests.
Don't send content-length from wai-app-static snoyberg/keter#52
Version bump
Revert "Don't have double content-length headers snoyberg/keter#52"

This reverts commit 76d474873e777a65649dcec295116e4b7a430506.
refactoring warp-tls by flattening.
Allow reading cert and key from memory #301
removing SSLv3 (#300).
Make this compilable on GHC HEAD (v7.9)
wai-extra: Consolidate test suite
wai-extra: Remove redundant liftIOs
wai-extra: Rely on OverloadedStrings instead of using pack explicitly
wai-extra: Move specs for Network.Wai.Parse to Network.Wai.ParseSpec
wai-extra: Split caseParseRequestBody into separate spec items

(one assertion per test)
wai-extra: Remove specs for parseSimpleQuery

(parseSimpleQuery has been moved to http-types + we have QC properties
their)
hlint suggestion
time 1.5 support
README.md and ChangeLog.md
Modify request body flushing behavior.

See explanation in ChangeLog.md. Pinging @kazu-yamamoto: do you see any
problems with this change?
setMaximumBodyFlush settings

Pinging @kazu-yamamoto @meteficha. This should be the last commit in
this request body flushing saga.
warp with bound threads #308