This screen allows you to configure the applications that
can be invoked.
By default there are no applications available, you need to add
all of the applications that you want to use.
O nome que será usado para esta aplicação no ZAP.
The full path of the application you want to invoke.
Only one command can be specified. If you want to run multiple commands in one
go, or set up environmental variables, then you should create a script or batch file and
then invoke this from ZAP.
| %url% | a url completa - por exemplo, 'http://localhost/test?a=b' | |
| %site% | o site - por exemplo, ' http://localhost:8080/ /' | |
| %host% | o nome do host - por exemplo, 'localhost' | |
| %port% | a porta - por exemplo, '80' | |
| %cookie% | o primeiro campo de cookie do cabeçalho da solicitação (se houver) | |
| %postdata% | os dados de postagem enviados, caso existam, com newlines substituídas por "\n" | |
| %msgid% | the HTTP message id to fetch data from the API (/JSON/core/view/message/?id=$msgid), does not alway exist, will return -1 if no message id | |
| %header-{{ header }}% | the request header by name (if any), e.g. %header-user-agent% would return the value of the User-Agent header |
If checked then the command run and any output it generates will be displayed on the
Output tab.
You should always use this option when running scripts or commands that do not
have a UI.
You can also use this option for troubleshooting - if an application does not
run as expected then copy the command run and try it from a command line prompt.
If checked then any output will be appended to a
Note attached to the relevant
History tab record.
Note that some nodes in the
Sites tab do not have associated
History tab records - for those nodes this option will have no effect.