Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output failed requests #85

Open
nepohex opened this issue Nov 12, 2020 · 3 comments
Open

Output failed requests #85

nepohex opened this issue Nov 12, 2020 · 3 comments

Comments

@nepohex
Copy link

nepohex commented Nov 12, 2020

Hi! Thank you for awesome tool!
I cant find the way how to output only failed requests in any way.
Using any --filter or output of Full or Short doesnt include totally failed requests, which are very important.

@blechschmidt
Copy link
Owner

I am not sure if this is what you are looking for, but you can use --retry never. Then, packets with any response code are printed. However, there is currently no option to print the requests that timed out, i.e. those for which no resolver returned an acceptable response.

@nepohex
Copy link
Author

nepohex commented Nov 12, 2020

I am not sure if this is what you are looking for, but you can use --retry never. Then, packets with any response code are printed. However, there is currently no option to print the requests that timed out, i.e. those for which no resolver returned an acceptable response.

Returns same answer, only successed.
There are big problem with it, when I need to scrape some domains, I dont know which requests are failed (banned dns or any other issue), so i get only success requests responses.

Now I'm manually filter output after executing, comparing with input file, getting lines which failed and than start script again and again until getting 100% success response. Thats pain.

@blechschmidt
Copy link
Owner

For JSON, this is implemented by the e output format option. (cf60a8e)

I plan to add this feature to the binary and full output modes as well and will leave the issue open until it has been implemented for both modes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants