Just using the dev console , an api call search was done like this (search for tweaks "stackoverflow" in Russian):
https:
... and everything went fine. Less likely, but this may be a bug in twitter4j. Try debugging it and see what actual api call is made. This should give you some clues.
About the second question. See the Search Operators section of this document . what you want is the default behavior, so just list your keywords with spaces in between, and this should do the trick.
source share