Ice3man

Hi @mzpqnxow, I will take a look at it.

Hi @mzpqnxow, Actually the result should be in an array. This would make it easy to move through the response and parse it. The response should be something like this...

Yes @mzpqnxow, that's what I had originally intended by creating this issue. BTW, no problem. I was able to use -n flag to get just directories.

TODO - - [x] add profiling support to httpx - [ ] run test scans with different target sizes - [ ] investigate profile data + figure out hotspots -...

Trailer: https://youtu.be/2UNWLgY-wuo IMDB: https://m.imdb.com/title/tt1731141/

@jaikishantulswani thanks for the issue. We are not picking it up as of now but will add it later asap!

Hey @karmi, any updates on this issue? I also came across this issue in my use case. This seems like a much needed fix.

@mzpqnxow this is a very good idea. We were also thinking of providing some way of doing tampers on request to do things like waf-bypass etc. We can use this...

@IfrahIman you can run nuclei with `-profile-mem ` flag and share the profile.pprof file with us which will help us identify the leak.

@IfrahIman can you run with a smaller target list? The profile is empty because it is written at the end of execution and the execution doesn't complete since we OOM...