HTTP Content-type for VOSpace 2.1

[Matthew Graham]

Hi,

I was actually thinking of createNode which is a PUT. Is "text/xml" correct? What about "application/xml"?

	Cheers,

	Matthew

On Oct 23, 2014, at 4:05 PM, Brian Major wrote:

> Hi Matthew,
> 
> If you are referring to an upload and the example in chapter 'pushToVoSpace' (here), then it is actually a POST to the VOSpace UWS endpoint for the creation of the transfer that uses content-type 'application/x-www-form-urlencoded'.  It should be 'text/xml'.  I'd say correcting it in the document would be sufficient.  I'll make a note to fix these examples in 2.1.
> 
> Cheers,
> Brian
> 
> On Fri, Oct 17, 2014 at 2:26 PM, Matthew Graham <drmjgraham at gmail.com> wrote:
> 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
> 
> 
> 
> -- 
> Brian Major
> 
> Canadian Astronomy Data Centre
> Centre canadien de données astronomiques
> 
> National Research Council Canada
> Conseil national de recherches Canada

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/grid/attachments/20141023/02ddc997/attachment.html>