[twitter-dev] Re: Stream API responds with 401 when multiple keywords are used

2010-11-04 Thread Andrew McCloud
I'm also having the same issue. Though it's only when using a space (e.g. hello world) to separate keywords. I've tried urlencoding spaces as a '+' and as '%20'... no luck. On Oct 15, 4:31 pm, Tom van der Woerdt i...@tvdw.eu wrote: If I am not mistaken, 'value1,value2' URLencodes to

[twitter-dev] Re: Stream API responds with 401 when multiple keywords are used

2010-10-15 Thread Corey Wallis
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

[twitter-dev] Re: Stream API responds with 401 when multiple keywords are used

2010-10-15 Thread Corey Wallis
Hi John, Is there any documentation on the way values should be encoded? With thanks. -Corey On Oct 15, 11:20 pm, John Kalucki j...@twitter.com wrote: There's at least one OAuth library out there that doesn't encode the comma correctly. Search back in this group for details. -John

Re: [twitter-dev] Re: Stream API responds with 401 when multiple keywords are used

2010-10-15 Thread Tom van der Woerdt
If I am not mistaken, 'value1,value2' URLencodes to 'value1%2Cvalue2' Tom On 10/16/10 1:25 AM, Corey Wallis wrote: 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