<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>POST tunneling in ADO.NET Data Services</title><link>http://blogs.msdn.com/marcelolr/archive/2008/08/20/post-tunneling-in-ado-net-data-services.aspx</link><description>Today's topic is about the UsePostTunneling property on the DataServiceContext type. The ADO.NET Data Services Framework was designed around RESTful principles, so it maps operations on entities to HTTP methods. So for example: To read an entity, we make</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: POST tunneling in ADO.NET Data Services</title><link>http://blogs.msdn.com/marcelolr/archive/2008/08/20/post-tunneling-in-ado-net-data-services.aspx#8887373</link><pubDate>Fri, 22 Aug 2008 13:30:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8887373</guid><dc:creator>Andy</dc:creator><description>&lt;p&gt;What is the custom header? A &amp;quot;_method&amp;quot; value? Thanks for the reminder about this feature. Though its documentation is rather scant. I'd love some samples of using this tunneling with jQuery and Data Services on the web. Blogs and documentation almost assume the only client apps using this would be Silverlight. But Data Services could be very useful for broader usage, in AJAX cases.&lt;/p&gt;
</description></item><item><title>re: POST tunneling in ADO.NET Data Services</title><link>http://blogs.msdn.com/marcelolr/archive/2008/08/20/post-tunneling-in-ado-net-data-services.aspx#8889376</link><pubDate>Sat, 23 Aug 2008 04:11:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8889376</guid><dc:creator>marcelolr</dc:creator><description>&lt;p&gt;Andy, the custom header name is 'X-HTTP-Method'. Just set its value to whichever HTTP method you would have sent if you didn't have to use the workaround.&lt;/p&gt;
&lt;p&gt;IIRC, the server will reject tunneled requests for GET and POST, which should always be available, as a way to provide a further incentive to keep REST semantics aligned with HTTP requests.&lt;/p&gt;
</description></item></channel></rss>