> I believe it is important - kindof. RFC2616 says, in summary, that the > response to a HEAD request should be the same as for a GET, but without the > body. So I *think* this means couch is free to not supply a content-length > (as it doesn't for a GET), but should still include the transfer-encoding: > chunked header the GET returns.
Doh! I managed to get all confused and think we returned a Content-Length for views. /ignore me.
