Hi Tom,

Would you have an example of some values before and after they are
encoded?

It would help me in looking for where the error is.

With thanks.

-Corey

On Oct 15, 11:20 pm, Tom van der Woerdt <i...@tvdw.eu> wrote:
> I'd assume that there would be an error in your signature generation.
> Make sure that you properly url-encode all values before putting them in
> your base string. Make sure to encode only the correct ones.
>
> If you've checked this and it still does not work, please show us the
> Base String which you use to generate the signature.
>
> Tom
>
> On 10/15/10 3:40 AM, Corey Wallis wrote:
>
>
>
> > Hi All,
>
> > I have working code that uses OAuth to connect to the Stream API and
> > filter using keywords. When I supply a single keyword the API works as
> > expected and tweets are returned. What is odd is that when I specify
> > multiple keywords, or keywords that include a # symbol I get a 401
> > UNAUTHORIZED error.
>
> > Has anyone seen this before and come up with a successful resolution?
>
> > I've captured the HTTP headers of both a successful and unsuccessful
> > call and I can't see anything that is different other than the list of
> > tracks contains multiple entries. Samples of the headers is below.
>
> > This works:
>
> > POST /1/statuses/filter.json HTTP/1.1
> > Authorization: OAuth oauth_token="###", oauth_consumer_key="###",
> > oauth_version="1.0", oauth_signature_method="HMAC-SHA1",
> > oauth_timestamp="1287106462", oauth_nonce="-1686656262164231601",
> > oauth_signature="###"
> > Content-Length: 13
> > Content-Type: application/x-www-form-urlencoded
> > Host: stream.twitter.com
> > Connection: Keep-Alive
> > User-Agent: Apache-HttpClient/4.0.1 (java 1.5)
> > Expect: 100-Continue
>
> > HTTP/1.1 100 Continue
>
> > track=twitter
>
> > This does not:
>
> > POST /1/statuses/filter.json HTTP/1.1
> > Authorization: OAuth oauth_token="###", oauth_consumer_key="###",
> > oauth_version="1.0", oauth_signature_method="HMAC-SHA1",
> > oauth_timestamp="1287105193", oauth_nonce="-3374947181315671264",
> > oauth_signature="###"
> > Content-Length: 20
> > Content-Type: application/x-www-form-urlencoded
> > Host: stream.twitter.com
> > Connection: Keep-Alive
> > User-Agent: Apache-HttpClient/4.0.1 (java 1.5)
> > Expect: 100-Continue
>
> > HTTP/1.1 100 Continue
>
> > track=twitter,lolcat
>
> > Any thoughts would be gratefully received.
>
> > With thanks.
>
> > -Corey

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