How can you pass arguments to NSE scripts via --script-args, with an example?

How can you pass arguments to NSE scripts via --script-args, with an example?

• A. Use --script-args 'arg1=value1,arg2=value2'
• B. Use --script-args 'enable=yes'
• C. Use --script-args 'cf=1'
• D. Use --script-args 'http-methods.webdav=yes'

Answer: (D)

Passing arguments to NSE scripts is done with --script-args, and you can target a specific script by prefixing the option with the script’s name and a dot. This per-script namespace lets you configure that particular script without affecting others. For example, http-methods.webdav=yes tells the http-methods script to enable checks related to WebDAV methods. This shows how you can toggle or configure a single script’s behavior directly. Generic key=value pairs (like arg1=value1,arg2=value2) may be accepted if a script defines those keys, but they aren’t specifically targeted to a single script. The per-script form is the precise way to pass a focused option to a chosen NSE script, and http-methods.webdav=yes is a clear illustration of that pattern.

Passing arguments to NSE scripts is done with --script-args, and you can target a specific script by prefixing the option with the script’s name and a dot. This per-script namespace lets you configure that particular script without affecting others. For example, http-methods.webdav=yes tells the http-methods script to enable checks related to WebDAV methods. This shows how you can toggle or configure a single script’s behavior directly.

Generic key=value pairs (like arg1=value1,arg2=value2) may be accepted if a script defines those keys, but they aren’t specifically targeted to a single script. The per-script form is the precise way to pass a focused option to a chosen NSE script, and http-methods.webdav=yes is a clear illustration of that pattern.