Make Content-MD5 response behave like S3

The code now differentiates between a malformed digest and a digest
mismatch.
Add support for setting bucket via subdomain

This is what most s3 clients use. It maps container1.localhost to
localhost/container1. Requires setting config.host to the hostname used
in requests, without the port.
Add support for SSL

No tests for now, because the tests all use a single config.
Merge branch 'fix-vows-exception'
Merge branch 'fix-deprecations'
Merge branch 'ssl-support'
Merge branch 'fix-etag-quoting'
Merge branch 'bucket-in-subdomain'

Conflicts:
	server.js
Merge branch 'fix-content-md5-reponse'