You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the example here, I have the scanner running successfully with a targeted scan on a azure deployed site, produces the report.html and report.json
I noticed in the scan report that it is showing a low level warning on the site at http even though I have the site to auto redirect to https
This then causes issues for me when trying to import the xml file from the handlebars template into Nunit as it now has two root elements, one for the site at http and another for https
In the script to generate the handlebars template it uses {{#each site}} which will iterate over the sites in report.json file, so if there are more than one the resulting Nunit xml file is invalid
How can I force the scanner to stop trying the site at http? I'm not even sure how it got to it in the first place as I'm auto redirected to https when I try the url that it is reporting in a browser
Or... since the script itself is liable to create an invalid nunit xml file, what are the proper modifications needed to create multiple xml files per site?
The text was updated successfully, but these errors were encountered:
@Eldorados - can you verify whether the updated details in the documentation enables you to create a valid report? The updated documentation can be found in Zap/README.md
Following the example here, I have the scanner running successfully with a targeted scan on a azure deployed site, produces the report.html and report.json
- task: owaspzap@1 inputs: scantype: 'targetedScan' url: 'https://mytestsite.azurewebsites.net/' aggressivemode: true
I noticed in the scan report that it is showing a low level warning on the site at http even though I have the site to auto redirect to https
This then causes issues for me when trying to import the xml file from the handlebars template into Nunit as it now has two root elements, one for the site at http and another for https
In the script to generate the handlebars template it uses {{#each site}} which will iterate over the sites in report.json file, so if there are more than one the resulting Nunit xml file is invalid
How can I force the scanner to stop trying the site at http? I'm not even sure how it got to it in the first place as I'm auto redirected to https when I try the url that it is reporting in a browser
Or... since the script itself is liable to create an invalid nunit xml file, what are the proper modifications needed to create multiple xml files per site?
The text was updated successfully, but these errors were encountered: