Re: [twitter-dev] error 406 - unparseable

2010-10-22 Thread Taylor Singletary
Can you share the executed URL you used for the request, the POST body, and
the OAuth authorization headers and signature base string? It's possible
there's an encoding issue with your commas or otherwise.

Thanks,
Taylor

On Fri, Oct 22, 2010 at 11:18 AM, AdamW13  wrote:

> attempting to use streaming API - with Phirehose ...
>
> Twitter is throwing back the following error:
>
> ERROR 406: Not Acceptable (Parameter follow has unparseable items
> 140501028).
>
> That ID is the first in my list - but doesn't seem to have anything
> wrong with it. ... The list is about 70 long - separated by commas, as
> it's supposed to be ...
>
> I cannot make sense of that error message.  What is unparseable about
> a comma-separated list of integers?
>
> --
> 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-dev] error 406 - unparseable

2010-10-22 Thread AdamW13
attempting to use streaming API - with Phirehose ...

Twitter is throwing back the following error:

ERROR 406: Not Acceptable (Parameter follow has unparseable items
140501028).

That ID is the first in my list - but doesn't seem to have anything
wrong with it. ... The list is about 70 long - separated by commas, as
it's supposed to be ...

I cannot make sense of that error message.  What is unparseable about
a comma-separated list of integers?

-- 
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