Can't run with Ajax spider about action-baseline

[kingthorin]

If that's not the case, I'm at a loss for what to do to appease Zap with regards to 10109.

It's an informational message. " If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one."

[kingthorin]

10109 has nothing to do with the Ajax Spider.

Is this a big in the action or in ZAP?

A what?

[kingthorin]

Please don't ask questions as issues - the ZAP User Group is a much better place for questions.

If you’re asking about a third party components such as the Jenkins plugin or VSTS plugin please look for their preferred support mechanism as these were not created by and are not supported by the core team.

[daniel-ac-martin]

Hi @kingthorin.

Thanks for the response. Apologies for posting here. The user group said I didn't have permissions to post, I was also wondering if this might be a bug of some sort.

Is this a big in the action or in ZAP?

A what?

Sorry, that should have said 'bug' not 'big'.

10109 has nothing to do with the Ajax Spider.

Oh, the description in the ZAP report says the following:

The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.

I interpreted this to mean that you will get the notice when you are not running the Ajax spider.
If that's not the case, I'm at a loss for what to do to appease Zap with regards to 10109.
Perhaps the message could be updated to be more clear?