A HEAD request may contain a Content-Length with a number that would be the size of a GET response, but no actual body to read. It may also contain no such header, but not close the connection when done (web.archive.org does this, for example).
In general, when issuing a request of type HEAD the client should not even try to read a body and should just return an empty InputStream to the handler. Currently the client often hangs when handling such a request.
I'm trying to work around this locally, but since none of the internal modules are exported it's very hard to do, even by copying a lot of the internal code out into my application since I don't have access to data constructors I cannot reimplement receiveResponse for example.
A
HEADrequest may contain aContent-Lengthwith a number that would be the size of aGETresponse, but no actual body to read. It may also contain no such header, but not close the connection when done (web.archive.orgdoes this, for example).In general, when issuing a request of type
HEADthe client should not even try to read a body and should just return an emptyInputStreamto the handler. Currently the client often hangs when handling such a request.I'm trying to work around this locally, but since none of the internal modules are exported it's very hard to do, even by copying a lot of the internal code out into my application since I don't have access to data constructors I cannot reimplement
receiveResponsefor example.