e1=valuu1;name2=value2<br/><br/>Ignore SSL Anchor Errors: only for https connections, ignoring such errors leaves the connection open to man-in-the-middle attac... e1=valuu1;name2=value2<br/><br/>Ignore SSL Anchor Errors: only for https connections, ignoring such errors leaves the connection open to man-in-the-middle attac
ication result. Can be <b>success</b> or whatever error there was in case of an error. You will probably use this most of the time.</li>
<li><b>Array</b>: For... then it was you'll have an array with 2 items: an error and success</li>
</ul>
<P>If you want to handle errors use the <b>Continue Task After Error</b> option
stdout) of the command.<br/><br/>Similarly, Store Errors In is for error output (stderr).<br/><br/>A result code of 256 indicates a technical failure executing ... e will cause the task to stop, unless Continue On Error is checked, otherwise the result code will be sto
e1=valuu1;name2=value2<br/><br/>Ignore SSL Anchor Errors: only for https connections, ignoring such errors leaves the connection open to man-in-the-middle attac
e1=valuu1;name2=value2<br/><br/>Ignore SSL Anchor Errors: only for https connections, ignoring such errors leaves the connection open to man-in-the-middle attac
other tasks with the same name).<br/><br/>If With Error is checked, the task(s) are marked as finished due to an error.<br/><br/>Note: to stop a different task will oft