Content-type encoding for HTTP PUT and POST
Matthew Graham
mjg at cacr.caltech.edu
Thu Oct 30 20:06:48 CET 2014
Hi,
I think that we need some text in the VOSpace 2.1 spec about Content-type encoding for HTTP POST and PUT, at least from a best practices perspective. Different clients will almost certainly apply different default behaviours - compare curl with Python httplib2, for example - and so implementors need to be aware of what to expect.
Cheers,
Matthew
More information about the grid
mailing list