mirror of
https://github.com/projectdiscovery/nuclei.git
synced 2025-12-17 17:56:56 +00:00
13af7ccd49
* test(flow): update outdated test cases
Signed-off-by: Dwi Siswanto <git@dw1.io>
* test(multiproto): update outdated test cases
Signed-off-by: Dwi Siswanto <git@dw1.io>
* feat: fixed failing tests
* fixed data race
* fixed memgaurdian race conditiong
* test(customtemplates): use test repo
Signed-off-by: Dwi Siswanto <git@dw1.io>
* feat(customtemplates): add more `{Clone,Pull}Options`
Signed-off-by: Dwi Siswanto <git@dw1.io>
* feat(customtemplates): validate `{Clone,Pull}Options`
Signed-off-by: Dwi Siswanto <git@dw1.io>
* bugfix: fixed failing integration tests for flow and multi
* chore: either 1 or 2 results in interactsh
---------
Signed-off-by: Dwi Siswanto <git@dw1.io>
Co-authored-by: Ice3man <nizamulrana@gmail.com>
tmplexec
tmplexec also known as template executer executes template it is different from protocols package which only contains logic within the scope of one protocol. tmplexec is resposible for executing Template with defined logic. with introduction of multi protocol and flow templates (deprecated package protocols/common/executer) did not seem appropriate/helpful anymore as it is outside of protocol scope and deals with execution of template which can contain 1 requests , or multiple requests of same protocol or multiple requests of different protocols. tmplexec is responsible for executing template and handling all logic related to it.
Engine/Backends
Currently there are 3 engines for template execution
Generic=> executes request[s] of same/one protocolMultiProtocol=> executes requests of multiple protocols with shared logic between protocol requests see multiprotocolFlow=> executes requests of one or multiple protocol requests as specified by template in javascript (aka flow) flow