By ui-encoding you mean percent-encoding?

On Nov 10, 3:38 am, Ciaran <ciar...@gmail.com> wrote:
> Try ui-encoding them first, my understanding of the Twitter OAuth
> signature validation is that it is non-standard (although there
> appears to be debate about this) I suspect if you encode them first
> before signing the url it will start to work
> -cj.
>
> On Tue, Nov 9, 2010 at 6:11 PM, dan <dfran...@gmail.com> wrote:
> > I've been having trouble connecting to the streaming API using oauth
> > if my tracks have spaces. I get 401s (unauthorized). In all cases, the
> > same code works if the tracks don't have spaces.
>
> > In Java: tried twitter4j (http://twitter4j.org/jira/browse/TFJ-420)
> > and tweetstream4j (http://stackoverflow.com/questions/4129622/
> > connecting-to-twitter-streaming-api-with-tracks-with-spaces-using-
> > apache-httpclie)
>
> > In Python: tried tweepy (https://github.com/joshthecoder/tweepy/
> > issues#issue/64)
>
> > The Twitter example using curl (http://dev.twitter.com/pages/
> > streaming_api_methods#track) works with tracks that have spaces, but
> > it's basic auth.
>
> > I am wondering if some oauth encoding versus POST param encoding is
> > not working out.
>
> > Can someone point me to a code example in Java or Python that is known
> > to work connecting to the Twitter streaming API using oauth that has
> > spaces in its tracks?
>
> > Thanks in advance.
>
> > --
> > 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