Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Error logging of unresolved variables #3386

Open
tarunKoyalwar opened this issue Mar 3, 2023 · 2 comments · May be fixed by #4447
Open

Improve Error logging of unresolved variables #3386

tarunKoyalwar opened this issue Mar 3, 2023 · 2 comments · May be fixed by #4447
Assignees
Labels
Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@tarunKoyalwar
Copy link
Member

Please describe your feature request:

  • nuclei by default skips requests whose variables are not resolvable (i.e variable value is not given/empty) while this is good it creates lot of noise whenever nuclei is run in versbose mode

Describe the use case of this feature:

Possible Bug

Investigate if variables are evaluated before/after parsing request

[WRN] [bdsmlr] Could not execute request for : [self-contained:RUNTIME] failed to parse https://{{user}}.bdsmlr.com in self contained request <- [:RUNTIME] failed to parse url <- parse "https://{{user}}.bdsmlr.com": invalid character "{" in host name
@tarunKoyalwar tarunKoyalwar added the Type: Enhancement Most issues will probably ask for additions or changes. label Mar 3, 2023
@tarunKoyalwar tarunKoyalwar self-assigned this Mar 3, 2023
@tarunKoyalwar
Copy link
Member Author

TODO

@RamanaReddy0M RamanaReddy0M linked a pull request Nov 30, 2023 that will close this issue
4 tasks
@RamanaReddy0M RamanaReddy0M linked a pull request Nov 30, 2023 that will close this issue
4 tasks
@mastercho
Copy link

Why this still not implemented?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants