You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The primary reason I would like to switch to this tool is the DOM Rendering. Would you be able to incorporate a feature that outputs http.response to ".txt" files after the dom has been rendered? A lot of tools like httpx lack this feature and it would be super nice for indexing.
The text was updated successfully, but these errors were encountered:
The goal of crawlergo is to discover as many attack surfaces as possible, and the rendering process gets so much response data, while begging the question of which content types need to be saved, that it's not a simple feature.
What is the use of this feature for you? How does it help you with subsequent Web vulnerability scans?
First of all thank you @Qianlitp , this is a great tool and I think the best crawling tool ever written according to my research, it will be much popular later.
I would also appreciate this functionality. Maybe not necessarily .txt files but in the output. It would be nice to get responseBody property like OWASP ZAP spider. This way, I can do further analysis on the web page content without needing to send one more request to get the response.
First of all this tool is fantastic!
The primary reason I would like to switch to this tool is the DOM Rendering. Would you be able to incorporate a feature that outputs http.response to ".txt" files after the dom has been rendered? A lot of tools like httpx lack this feature and it would be super nice for indexing.
The text was updated successfully, but these errors were encountered: