Exception handling loses HTTP errors

[TurqW]

The exception handling (or rather, printing) code in BaseClient.issueGet() and BaseClient.issueDelete() invariably ends up throwing IOExceptions, obscuring the actual exception that occurred.

Sequence of events looks something like:

• readFromConnection gets response code higher than 400
• readFromConnection constructs StringBuilder with message from connection
• readFromConnection's finally block closes the InputStreamReader
• • Closing an InputStreamReader closes the underlying stream.
• readFromConnection throws newly constructed IOException with helpful message
• issueGet (or issueDelete) catches the IOException
• issueGet tries to read from the connection's error stream (which is already closed)
• issueGet throws new IOException with no information except "stream is closed"

[TurqW]

My bad, this has been fixed since the version I'm using.