Hi Alfonso,<br><br><div class="gmail_quote">On 30 June 2011 11:39, Alfonso Pantoja <span dir="ltr"><<a href="mailto:alfonso.pantoja@gmail.com">alfonso.pantoja@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I've found a problem using the HTTP API. Using .NET you should use<br>
sockets or a hack to make a webrequest using the character %2F<br>
because .NET replaces that %2F by "/"<br>
so <a href="http://server/api/%2F/queues" target="_blank">http://server/api/%2F/queues</a> becomes always <a href="http://server/api///queues" target="_blank">http://server/api///queues</a><br>
and a not found is get.<br></blockquote><div><br>I recommend avoiding the broken Microsoft HTTP client library, and using a better third-party library. A few minutes googling produced <a href="http://www.codescales.com/">http://www.codescales.com/</a>, which looks plausible.<br>
<br>(It seems that MS have actually willfully crippled their client: see, for instance, <a href="http://connect.microsoft.com/VisualStudio/feedback/details/94109/system-uri-constructor-evaluates-escaped-slashes-and-removes-double-slashes">this bug report</a>. "We are not aware of any such real world scenarios currently."�good grief!)<br>
<br>Regards,<br>� Tony<br><br></div></div>