<div dir="ltr">Hi Matthew,<div><br></div><div style>If you are referring to an upload and the example in chapter 'pushToVoSpace' (<a href="http://www.ivoa.net/documents/VOSpace/20130329/REC-VOSpace-2.0-20130329.html#sec5_4_1">here</a>), 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.</div><div style><br></div><div style>Cheers,</div><div style>Brian</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 17, 2014 at 2:26 PM, Matthew Graham <span dir="ltr"><<a href="mailto:drmjgraham@gmail.com" target="_blank">drmjgraham@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
<br>
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?<br>
<br>
Cheers,<br>
<br>
Matthew</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><font color="#999999">Brian Major<br><br>Canadian Astronomy Data Centre<br>Centre canadien de données astronomiques<br><br>National Research Council Canada<br>Conseil national de recherches Canada</font></div>
</div></div>