After further investigation, I think I've found the problem: I'm not
signing the body properly, sorry for the false alarm.


On Apr 14, 12:30 am, ""
<> wrote:
> Hi there,
> I'm working on a ruby client for the streaming API and am getting hung
> up on OAuth.  When making requests to /1/statuses/filter.json with an
> OAuth authorization header via a POST, I immediately receive a 401
> Unauthorized.  GET requests with an OAuth authorization header are
> working however.  This behavior appears to contradict the streaming
> documentation which says that the request method for statuses/filter
> should be a POST.
> Is this a known issue or am I missing something here?
> Thanks,
> Steve

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to