Recent problems with 1.1/search/tweets when q=#anythin -- it doesn't like the # (after url encoding)


#1

Our app has been running for years problem free using Oauth 1.0.
We’ve implemented the 1.1 api several months ago.
All API calls from v1.1 appear to be are working fine except for the v1.1 search.

Here’s an example of a q value that odesn’t work.
q=#anythin

This translates to:
https://api.twitter.com/1.1/search/tweets.json?q=%23anythin&count=100&include_entities=true

And we get back this: “error: The remote server returned an error: (401) Unauthorized.”

Any other q=value seems to work fine, only values which have a # in them do not work.