We haven't changed anything with the API. Our operations team is currently rolling out a new version of Apache, and perhaps this new version is stricter about client-supplied headers. But I'd double-check your code first.
On Tue, Dec 23, 2008 at 17:51, Cameron Kaiser <[email protected]> wrote: > >> > > curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:')); >> >> Would be really interestingt though to know, what the guys at twitter >> changed on the api. > > I still haven't seen a Charles trace on what the client is actually sending. > If the client is indeed sending a bogus Expect: header, then all this line is > doing is suppressing it. > > -- > ------------------------------------ personal: http://www.cameronkaiser.com/ > -- > Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] > -- To err is human -- to forgive is not company policy. > ----------------------- > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
