<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 6, 2013 at 6:56 PM, Cal Leeming [Simplicity Media Ltd] <span dir="ltr"><<a href="mailto:cal.leeming@simplicitymedialtd.co.uk" target="_blank">cal.leeming@simplicitymedialtd.co.uk</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">The docs says this;<div><br>curl url [headers|json] [get|head|post [url_encode_data]]</div>
</blockquote><div><br></div><div style>The [headers|json] is all about the response format. Just to make sure that is clear.</div><div style><br></div><div style>get/head/post should be self-evident</div><div style><br></div>
<div style>url_encode_data is supposed to be the url encoded version of what you want to send to the server. It is encoded on purpose (so that we don't have to worry about embedded spaces or other special chars).</div>
<div style><br></div><div style>So, you really just need to do:</div><div style><br></div><div style>curl <a href="http://example.com/" target="_blank">http://example.com/</a> post encodedxmlhere</div><div style><br></div>
<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"><div><br></div><div>So, I assume you'd just do.</div><div>
<br></div><div>curl <a href="http://example.com/" target="_blank">http://example.com/</a> post xml=encodedxmlhere</div>
<div><br></div></blockquote><div><br></div><div style>This will result in www-url-encoded with key/value pair with xml as key and the encoded xml as the value. This may be what the OP wants, but I think what he wants is just XML.</div>
<div style><br></div><div style><br></div><div style>Note that the content-type will still be <span style="color:rgb(0,0,0);font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:13px;line-height:17px">application/x-www-form-urlencoded which is "wrong". I've written xml service endpoints that behave differently based on the content-type. Depending on how your service is written this may be ok or not. There is an open ticket to address the content-type issue.</span></div>
<div style><br></div><div style><a href="http://jira.freeswitch.org/browse/FS-4714">http://jira.freeswitch.org/browse/FS-4714</a><br></div><div style><br></div><div style> <br></div><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">
<div></div><div>Taken from here;</div><div><a href="http://wiki.freeswitch.org/wiki/Mod_curl" target="_blank">http://wiki.freeswitch.org/wiki/Mod_curl</a></div><div><br></div><div>Hope this helps, apologies if I misunderstood the question</div>
<div><br></div><div>Cal</div><div><br></div></blockquote></div><div><br></div>-- <br>-Rupa
</div></div>