<div dir="ltr">From what I can tell, the difference between text/xml and application/xml is that, if using application/xml, browsers will try to interpret and format the document, while with text/xml it will show up as plain text. I think historically there were encoding problems with text/xml, but I think those have been addressed. Unless someone disagrees, I'll put application/xml in the examples for version 2.1.<div><br></div><div>Brian</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 23, 2014 at 4:07 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi,<div><br></div><div>I was actually thinking of createNode which is a PUT. Is "text/xml" correct? What about "application/xml"?</div><div><br></div><div><span style="white-space:pre-wrap"> </span>Cheers,</div><div><br></div><div><span style="white-space:pre-wrap"> </span>Matthew</div><div><div class="h5"><div><br><div><div><div>On Oct 23, 2014, at 4:05 PM, Brian Major wrote:</div><br><blockquote type="cite"><div dir="ltr">Hi Matthew,<div><br></div><div>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" target="_blank">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><br></div><div>Cheers,</div><div>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>
</blockquote></div><br></div></div></div></div></div></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>