Hey Justin,

Thanks for the update. If it does happen again let us know with the
headers and response body. We can then try and find out what happened.
It's very odd for us to not return any body content on error.

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris



On Fri, Oct 1, 2010 at 2:27 PM, Justin <justin.carl...@gmail.com> wrote:
> I log the status code and the full response if available, which in
> this case it came back null.
>
> It is likely that it was either friends/ids, or followers/ids.
>
> I checked my logs and I don't believe this has ever happened before
> (backend has been in use for 14 months).
>
> Everything has been working fine sense.
>
> I've added additional logging, including the full headers and the
> method called when it happens so if it does happen again I'll have
> more info.
>
>
>
>
> On Oct 1, 3:46 pm, Taylor Singletary <taylorsinglet...@twitter.com>
> wrote:
>> Hi Justin,
>>
>> Do you know the exact method call you were making when you got this? Was it
>> friends/ids ?
>>
>> Have you seen the error again since?
>>
>> Are you logging the status message in addition to the code itself?
>>
>> Taylor
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Oct 1, 2010 at 12:45 PM, Justin <justin.carl...@gmail.com> wrote:
>> > Just noticed this in my log:
>>
>> > Oct 01/2010 12:20:05 pm : process 25236 -> response NULL
>> > Oct 01/2010 12:20:05 pm : process 25236 -> caught http status 403,
>> > backing off. EXITED
>>
>> > When I get any status other than 200 I back off and log the response,
>> > in this case the response was null.
>>
>> > My rate limit is also logged and I was well under 20k
>>
>> > The process that caught that 403 handles friendships, and seemed to be
>> > pulling my list for cache at the time.
>>
>> > This is the only time I've seen this in at least 7 days. Any thoughts?
>> > Temp glitch?
>>
>> > I noticed there have been about several back-offs with 500 listed as
>> > well. Just a choppy day? (it is Friday I guess).
>>
>> > --
>> > Twitter developer documentation and resources:http://dev.twitter.com/doc
>> > API updates via Twitter:http://twitter.com/twitterapi
>> > Issues/Enhancements Tracker:
>> >http://code.google.com/p/twitter-api/issues/list
>> > Change your membership to this group:
>> >http://groups.google.com/group/twitter-development-talk
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to