Fix typo.
Update readme after dropping node 0.6 support
hasBody() should return false if Content-Length: 0

Some clients will set Content-Length: 0 when there is no content (and shouldn't be, e.g. on a GET). This can cause other parts of connect to be confused. For instance, if the client also sets Content-Type: application/json, the json middleware will try to parse an empty string and blow up.

Of course, such clients are unhelpful at best, but connect should not blow up.
Fix status code in documentation

Fix a mismatch between the documented status code (408) and the one set by the middleware
update send
Release 2.7.11
Remove other "static" function name. Fixes #794
Merge pull request #817 from xtian/static-strict

Remove other "static" function name. Fixes #794
Merge pull request #816 from loris/patch-1

Fix status code in documentation
Merge pull request #815 from darobin/patch-2

hasBody() should return false if Content-Length: 0
refactor hasBody util
compress; threshold option
cookie session: add support for multipl x-forwarded-proto values
add a test to check that connect properly survives content-length=0 and content-type=application/json (see https://github.com/senchalabs/connect/pull/815)
replace utils.uid() with uid2 lib
remove unnecessary `secured` variable

replace its use with the `tls` variable that it was using itself
Don't use octal escape sequences as they cause syntax errors in strict mode
change static redirect to 303
add support for vendor JSON mime types in json()
Merge pull request #825 from jamesallardice/fix-strict-mode

Don't use octal escape sequences as they cause syntax errors in strict mode