Hi,
The '417- Expectation failed error' occurs again for me while updating
status. I am using the Yedda Twitter library. I have already added
'System.Net.ServicePointManager.Expect100Continue = false;' to my
Posting function:
protected string ExecutePostCommand(string url, string userName,
Hi,
thanxs for replying, i have tried as per you mention.
But no success, still getting (417) error.
Vivek Shrivastav
Invitratech India
On Jan 6, 7:01 pm, Maxfield Pool maxfield.p...@gmail.com wrote:
Try moving your System.Net.ServicePointManager.Expect100Continue = false
higher in your
Try moving your System.Net.ServicePointManager.Expect100Continue = false
higher in your method before you create your WebRequest object, that should
help.
On Tue, Jan 6, 2009 at 6:49 AM, Vivek vivek.shrivas...@gmail.com wrote:
Hi,
We are getting same (417) error back in our website.
Thanks for posting this information. We've applied these changes and
our application is back to normal.
Regards;
-Wayne
On Dec 23 2008, 8:31 pm, JakeS jakesteven...@gmail.com wrote:
Looks like twitter is updating something and their servers are
returning error 417 for a lot of requests. I
From the doc on MSDN Changing the value of this property does not
affect existing ServicePoint objects. Only new ServicePoint objects
created after the change are affected.
Make sure the statement
System.Net.ServicePointManager.Expect100Continue = false; is called in
the service contrutor and
Thanks Jake, I was getting the same errors.
Is this expected behavior now for Twitter or is this a bug in the new
Twitter release (Not supporting the Expect: Continue header). I'm
writing a multi-service Windows Mobile application and I'd prefer not
changing global http connection settings if I
Is this expected behavior now for Twitter or is this a bug in the new
Twitter release (Not supporting the Expect: Continue header). I'm
writing a multi-service Windows Mobile application and I'd prefer not
changing global http connection settings if I don't have to.
Strictly speaking,
On Dec 24, 4:31 am, JakeS jakesteven...@gmail.com wrote:
Looks like twitter is updating something and their servers are
returning error 417 for a lot of requests. I looked into it and found
that .NET automatically includes an Expect header containing 100-
continue on every request unless you
Started getting reports from users yesterday that they couldn't login
to hahlo.com.
Turns out that the check I run against verify credentials was also
returning code 417 instead of the usual/expected 200, so even though
the check was working to hahlo is looked like it was failing, changed
my
I'm currently getting 417 as well on my php from script using curl
Sent from my iPhone
On 24 Dec 2008, at 23:50, dean.j.robinson
dean.j.robin...@gmail.com wrote:
Started getting reports from users yesterday that they couldn't login
to hahlo.com.
Turns out that the check I run against
After investigating further it appears this only occurs for .NET
applications which post using form data instead of using URL
parameters. Here's a sample:
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(url);
request.Credentials = new NetworkCredential(AccountInfo.UserName,
Looks like twitter is updating something and their servers are
returning error 417 for a lot of requests. I looked into it and found
that .NET automatically includes an Expect header containing 100-
continue on every request unless you specifically tell it not to.
So for any .NET devs having
12 matches
Mail list logo
