Folks, In the HttpClient extension on trunk, HttpMethodCall.getResponseStream() should return null when the underlying response body stream is null. However, as currently written, this method will return a non-null FilterInputStream wrapper, even when the underlying response body stream is null.
Having a non-null input stream in this case leads to incorrect calculation of Representation.isAvailable() which causes further cascading problems such as NullPointerException when the any attempt is made to read from the stream. AFAICT, this looks like a bug, so I created a patch to resolve the issue. Let me know if I should file a new issue in the tracker and attach the patch. Kind Regards, John Fallows
