This topic has not yet been rated - Rate this topic

HttpWebRequest.Expect Property

Gets or sets the value of the Expect HTTP header.

Namespace:  System.Net
Assembly:  System (in System.dll)
public string Expect { get; set; }

Property Value

Type: System.String
The contents of the Expect HTTP header. The default value is null.
NoteNote

The value for this property is stored in WebHeaderCollection. If WebHeaderCollection is set, the property value is lost.

Exception Condition
ArgumentException

Expect is set to a string that contains "100-continue" as a substring.

.NET Framework

Supported in: 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
So apparently this is why the argument exception...
http://haacked.com/archive/2004/05/15/http-web-request-expect-100-continue.aspx

Bottom line is that HttpWebRequest does automatic adding of 100 continue headers for you. And it's unobvious how to turn off. But apparently it involves System.Net.ServicePointManager.Expect100Continue. Just read the blog?
Why? Why is 100-continue special?
I'm referring to

"throws ArgumentException: Expect is set to a string that contains "100-continue" as a substring. "