HTTP Content-type for VOSpace 2.1

[Matthew Graham]

Hi,

I note from the VOSpace 2.0 spec that there is no specific content-type recommended for HTTP PUT requests (at least). The examples show: application/x-www-form-urlencoded which is what curl defaults to but this may not be true for other clients. Is this something that we should note/address in VOSpace 2.1 or least state that any content type is allowed/must be supported?

	Cheers,

	Matthew