Fairly serious weakness -- at the moment we rely on the user to set Content-Length: if PUTing or POSTing because we haven't implemented chunked transfer-encoding for sending.
The convenience APIs run the OutputStream to calculate the length and set it appropriately, so they are correct at least.
The library should probably just send chunked unless a length is explicitly provided, though working out a sensible public API taking this into account might take a little doing.
Fairly serious weakness -- at the moment we rely on the user to set
Content-Length:
if PUTing or POSTing because we haven't implemented chunked transfer-encoding for sending.The convenience APIs run the OutputStream to calculate the length and set it appropriately, so they are correct at least.
The library should probably just send chunked unless a length is explicitly provided, though working out a sensible public API taking this into account might take a little doing.
AfC