Hi Pablo, The OAuth implementations on streaming.twitter.com and api.twitter.com are slightly different -- the api.twitter.com implementation likely being more lenient to things like unencoded spaces.
Spaces in POST bodies and query strings should always be encoded, regardless, as %20 whether used as criteria for a streaming filter or posting a status update on the REST API -- it's invalid otherwise whether one of our implementations accepts it or not :) As a library developer, it's up to you on whether you want to put the onus of proper parameter encoding on the end-developer or if you want to handle transposing space characters to %20 (or "+" if you're feeling brave and/or reckless) -- there are trade-offs in either approach. @episod <http://twitter.com/episod> - Taylor Singletary On Mon, May 9, 2011 at 2:51 PM, Pablo Fernandez <fernandezpabl...@gmail.com>wrote: > Hello Twitter :) > > I'm the developer of an OAuth library for java. I recently tested it > on the streaming API and found a little quirk. > > When making a query to: > > http://stream.twitter.com/1/statuses/filter.json > > with a 'track' parameter with whitespace on it, I get a jetty 404 html > page as a response. > > Some important notes: > > * The problem disappears when the 'track' value has no whitespace > (which led me to think that my whitespace-encoding-fu was weak... > but..) > > * The library works great while posting tweets with 'status' parameter > with whitespace > > Thanks a lot. > > Pablo Fernandez > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk