Click here to Skip to main content
14,029,616 members
Click here to Skip to main content
Add your own
alternative version

Tagged as


8 bookmarked
Posted 15 Jul 2010
Licenced CPOL

The request failed with HTTP status 417: Expectation failed

, 15 Jul 2010
Rate this:
Please Sign up or sign in to vote.
The request failed with HTTP status 417: Expectation failed

When using WebServices and calling some Web Methods, you may come across this exception:

The request failed with HTTP status 417: Expectation failed.

When Expect 100-Continue property is set to true (this is actually set within part of the .NET Framework, which makes this a difficult problem to overcome. You have to override this in more than one place), this 417 error occurs when the proxy server doesn't support 100-Continue.

In the case of expect 100-Continue, the client will expect to receive a 100-Continue response from the server to indicate that the client should send the data to be posted. This mechanism allows clients to avoid sending large amounts of data over the network when the server, based on the request headers, intends to reject the request.

The Expect 100-Continue behavior is fully described in IETF RFC 2616 Section 10.1.1.

You can also read more about it in MSDN.

To work around this exception, you can do a simple thing: Disable expect 100 continue.

So you may ask how to disable expect 100 continue?

Warning: When you disable Expect 100-Continues and your application sends a large amount of data on the network, if for any reason the server rejects your request, you have to re-send the entire data again, this may cause some extra traffic in your network. Also multiple calls to a server will take longer, since each call will wait until the prior call's response is received.

It is easy. Here are two alternative ways:

  1. We need to have this line of code before making any web requests:
    System.Net.ServicePointManager.Expect100Continue = false; 
  2. Add these lines to the application's configuration file (between <configuration> and </configuration>):
      <servicePointManager expect100Continue="false" />

While this workaround is nice, I think a better long term solution is to upgrade/replace the proxy server to handle 100-continue calls.

So far in this short tip, we've learned what is Expect 100, how it is caused and how to workaround this expectation.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

United Kingdom United Kingdom
No Biography provided

You may also be interested in...

Comments and Discussions

QuestionWorked great Pin
Member 236155412-Jun-15 4:07
memberMember 236155412-Jun-15 4:07 
QuestionExpect100Continue default value Pin
rafp612-Jun-14 7:44
memberrafp612-Jun-14 7:44 
GeneralMy vote of 5 Pin
erSitzt27-Dec-12 0:54
membererSitzt27-Dec-12 0:54 
QuestionWebservice integration Exception Pin
d87manish31-Oct-12 21:27
memberd87manish31-Oct-12 21:27 
GeneralMy vote of 5 Pin
Nuno Agapito20-Sep-12 6:04
memberNuno Agapito20-Sep-12 6:04 
GeneralRe: My vote of 5 Pin
mrt_doulaty20-Sep-12 6:11
membermrt_doulaty20-Sep-12 6:11 
GeneralRe: My vote of 5 Pin
mrt_doulaty20-Sep-12 6:12
membermrt_doulaty20-Sep-12 6:12 
Questionapplication's configuration file Pin
aishar12-Sep-11 7:59
memberaishar12-Sep-11 7:59 
AnswerRe: application's configuration file Pin
mrt_doulaty13-Sep-11 2:58
membermrt_doulaty13-Sep-11 2:58 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Cookies | Terms of Use | Mobile
Web04 | 2.8.190419.4 | Last Updated 15 Jul 2010
Article Copyright 2010 by mrt_doulaty
Everything else Copyright © CodeProject, 1999-2019
Layout: fixed | fluid