This is related to this discussion  , but regarding the path in the URL, not the sub(domain).
After reading the docs I thought “foo” would not match “www.example.com/foo/bar”, but according to “Streaming API keyword matching”  it does:
Terms that would match this tweet: (the tracking terms are made lowercase before comparison, fullwidth and halfwith are considered different) www.example.com/foo/bar www example com foo bar example.com/foo/bar
I also think see this in practice with tweets matching “post” because a link contains “…tumblr.com/post/…”, but I’ts hard to be sure.
Did I misunderstand or are the docs wrong?