[MERGE] Don't require Content-Type

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We have bug:
https://launchpad.net/products/bzr/+bug/62473

Where Cherokee doesn't return the 'Content-Type' header if it doesn't
know it. We currently require the Content-Type header, because that is
where you store the 'multipart/bytes' information to distinguish a
multipart response versus a single range response.

Anyway, we need to decide if we want to support a missing
'Content-Type', it doesn't seem to be required by the http spec, and the
only thing we use it for at the moment is checking whether a range
response is a multipart response, or a single-range response.

The attached patch just changes it so that if there is no Content-Type,
then it cannot be multipart.

It is a small change, and comes with tests, so if we decide to support
it, I don't see why it couldn't be merged for bzr-0.12.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFLLPLJdeBCYSNAAMRAiEbAKC2KpYez86rOYFNa6MK9WQVmWNq6QCfQETi
o/us2MUOhBlVfxg3VTITmlc=
=g3WH
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dont_require_content_type.diff
Url: https://lists.ubuntu.com/archives/bazaar/attachments/20061011/a3437512/attachment.diff