<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://technolog.nl/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>HttpWebRequest on DotNet 2.0 driving you crazy for a B2B request? Disable ServicePointManager.Expect100Continue first!</title><link>http://technolog.nl/blogs/eprogrammer/archive/2007/07/24/HttpWebRequest-on-DotNet-2.0-driving-you-crazy-for-a-B2B-request_3F00_-Disable-ServicePointManager.Expect100Continue-first_2100_.aspx</link><description>Imagine, you have written a succesfull gateway to say, the European Community to check the validity of a VAT number. It always works, but suddenly it does not work anymore. What&amp;#39;s up? Could it be that some service pack modified the behaviour of the</description><dc:language>en</dc:language><generator>CommunityServer 2.1 (Build: 60809.935)</generator><item><title>re: HttpWebRequest on DotNet 2.0 driving you crazy for a B2B request? Disable ServicePointManager.Expect100Continue first!</title><link>http://technolog.nl/blogs/eprogrammer/archive/2007/07/24/HttpWebRequest-on-DotNet-2.0-driving-you-crazy-for-a-B2B-request_3F00_-Disable-ServicePointManager.Expect100Continue-first_2100_.aspx#1251</link><pubDate>Mon, 17 Dec 2007 16:16:55 GMT</pubDate><guid isPermaLink="false">3420c8e2-8f96-4c4a-9e98-3bc38250dfb6:1251</guid><dc:creator>John</dc:creator><description>This is a tough one -- you can't know a priori whether the server can support Expect100Continue. 

The purpose of this property is to save bandwidth. The default value in the Framework is true, so you'll use it by default. If a request fails, set it to false and try again.

John
</description></item></channel></rss>