Here's the response that was returned:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>417 Expectation Failed</title>
</head><body>
<h1>Expectation Failed</h1>
<p>The expectation given in the Expect request-header
field could not be met by this server.</p>
<p>The client sent<pre>
Expect: 100-continue
</pre>
but we only allow the 100-continue expectation.</p>
</body></html>
which apparently manifested itself sometime around Dec. 23rd according
to this site:
http://tinyurl.com/8xm9fz
I added the additional PHP libcurl option call and it fixed the
problem.
On an aside, it appears that this is a Twitter server response and not
an API response?
Anyway, the problem is solved and I posted the solution in the event
that someone else may experience something similar.
Your quick response is always appreciated.
Cheers,
Pat
On Jan 16, 2:52 pm, Alex Payne <[email protected]> wrote:
> I need to see some request/response output before I can determine what's
> going on with your application.
>
> Sailfish wrote:
> > We have two sites (one LIVE, one sandbox) that had been working using
> > the REST API via PHP libcurl calls but that stopped posting updates a
> > few days ago. The API calls have been working for a few months and
> > have not been changed in at least two months.
>
> > The sites are:
>
> >www.twitbacks.com(LIVE) - Fixed IP (208.116.50.124) via Hostnexus
> >www.projectit.com(our sandbox) - via dreamhost.com
>
> > The API method being used are:
>
> > update
> > update_profile_colors
> > update_profile_background_image
>
> > There is no error code detected but now the calls fail.
>
> > Has anything changed in the API over the past week that may have
> > caused this breakage on our system?
>
> > Thanks in advance for any assistance.
>
> > Regards,
> > Patrick Thompson
