Skip to content

Clarify how browser-based crawling is used

Derek Ferguson requested to merge derekferguson-master-patch-17522 into master

What does this MR do?

There have been a few comments that the paragraph about using browser-based crawling with the existing DAST scanner is confusing and makes it sounds like we are scanning the site twice. Also, since the browser-based crawler is a replacement for the AJAX crawler, it doesn't make sense to say that it doesn't support the AJAX crawler. It supports the same type of crawling, it just does it better. In addition, the existing AJAX crawler doesn't support APIs either, so there's no reason to mention that. The new text should clarify exactly what the new crawler is and how it is used as a direct replacement for the AJAX crawler.

Related issues

Author's checklist

To avoid having this MR be added to code verification QA issues, don't add these labels: feature, frontend, backend, ~"bug", or database

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.

Merge request reports