2

I'm trying to grep some curl content however I'm still getting curl output even though I'm piping it via grep.

E.g. 

curl -svo /dev/null <some url>   | grep <some text>

Any idea what I'm doing wrong?

Improve this question
3
  • you mean you're getting output that's not matching the grep? Are they long lines that match somewhere unexpectedly? Commented Mar 13, 2017 at 16:18
  • You're aware that options -s and -v have more or less opposite effects, right? Commented Mar 13, 2017 at 16:22
  • They're misleading but not opposite. -v outputs additional curl output. -s prevents the progress bar header. Commented Mar 14, 2017 at 9:55

1 Answer 1

Reset to default
2

You pipe only the stdout to grep, but your curl puts out errors to stderr which are printed without passing the grep. If you want the stderr to be filtered, too, redirect it to stdout first.

Improve this answer
3
  • Hardly need to take a wild guess. It's pretty obvious how to fill in the blanks. Here's an example if you're struggling: curl -svo /dev/null https://www.google.com | grep google Commented Mar 13, 2017 at 16:28
  • @SnowCrash Thank you. I didn't try. Removed the wild guess from my answer, as I obviously guess right. Commented Mar 13, 2017 at 16:33
  • @SnowCrash If your question is solved, please close it by marking it as answered Commented Mar 14, 2017 at 7:13

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.