Connection reuse for RFC compliant HTTP requests

[ehsandeep]

Please describe your feature request:

For HTTP protocol excluding unsafe requests, connection reuse could be used for performance improvements.

[Mzack9999]

Enabling connection reuse (Enabling keep-alive, disabling request.Close, removing Connection: close header, reading all the body) for RFC compliant HTTP requests doesn't speed up elaboration towards a single target Normal Execution:

$ time echo https://192.168.1.1 | go run . -silent -t /Users/user/go/src/github.com/projectdiscovery/nuclei-templates/technologies/
real    1m28.692s
user    0m4.909s
sys     0m2.004s

Connection Reuse:

$ time echo https://192.168.1.1 | go run . -silent -t /Users/user/go/src/github.com/projectdiscovery/nuclei-templates/technologies/
real    1m25.623s
user    0m5.803s
sys     0m1.980s

[brenocss]

Were speed tests done only on local networks? I think this kind of improvement shouldn't have as much impact on local networks as on external ones. Another suggestion would be to investigate the possibility of implementing using http pipelining.

https://youtu.be/vCpIAsxESFY?t=264

[Mzack9999]

This will be reworked as part of https://github.com/projectdiscovery/nuclei/issues/3077