Mzack9999

@mnd5756242 I tried to build the example that you provided, but there is some syntax error. I would recommend to attempt using the SDK to run nuclei as a library...

This should be now fixed and not reproducible anymore with the new internal architecture using independent dialers with different execution ids. I'm closing the issue and it will be reopened...

Superseded by https://github.com/projectdiscovery/nuclei/pull/6472 - Closing

@geeknik very interesting approach, I'm going to review this soon and compare it with BM25

The preferred syntax is: `{{first_method(second_method(variable))}}`

> > The preferred syntax is: `{{first_method(second_method(variable))}}` > > We need to address all the other points as well. Obviously, the previous comment was a starting point note left to...

## Other corners cases ### Case 1 ```yaml variables: var1: "test value" {{first_method(var1)}} # what if the user wants the string "var1" instead of "test value"? ``` Response: ```yaml {{"var1"}}...

Depends on https://github.com/projectdiscovery/nuclei/pull/2679

Isn't better a nuclei template?

I think a nuclei template like the following one should do the job as internally nuclei already uses httpx for pre-flight: ```yaml id: copyright-year-detector info: name: Copyright Year Detector author:...