bug with response read timeout flag

[zerokeeper]

Hello, there is a bug with the -response-read-timeout (-rrt) flag. it doesn't work.

if the response time more than 5s.It can't receive response successfully.
Even though I set the time and rrt to a longer time, it still has no effect.
nuclei -u url -t test.yaml -dast -timeout 10 -rrt 10

I still think that the rrt flag and the timeout flag are duplicated and bring new bugs.
Even if this bug is fixed, it seems that these two flags need to be set when setting timeout in the future. Can I cancel it?

The similar issues:
#5111

[tarunKoyalwar]

@zerokeeper , currently -rrt flag is specific to network protocol templates and does not affect templates , as for http response body read timeout it is 3 x timeout flag value , since there have been recent changes related to timeouts we are trying to derive timeouts from a single flag see #5214

[tarunKoyalwar]

i am converting this to discussion, we have implemented various fixes directly related to nuclei and speed as well as error related improvements #5148

If suggest you wait for nuclei release ( which most probably be today), and check if you are still facing the issue , if so then share more details including target , template the actual error as well as error log -elog file.log output

if it is private target/template , feel free to dm us in discord and we will reproduce this behaviour and triage

[zerokeeper]

Thank you!
I update nuclei with the latest release version. It can work successfully.
It seems that response-read-timeout 5 second timeout issue don't affect templates any more.