title: ZAP seems to incorrectly report path traversal vulnerability in Angular app
body: <p>I'm running OWASP ZAP as part of an automated CI/CD process.  I am doing a spider and active scan.  The report showed that there is a Path Traversal error.</p>
  
  <p>First, this is an Angular 2 site so there wouldn't be anything revealed on the server.  Second, when I view the URL in question with and without the "attack", the results are the same.  This URL just downloads a JavaScript file to the browser and the querystring is ignored.  We are using webpack to do the bundling.</p>
  
  <p><a href="https://mysite/js/vendor.ece5bf651436a14bea3e.bundle.js?query=c%3A%2F" rel="nofollow noreferrer">https://mysite/js/vendor.ece5bf651436a14bea3e.bundle.js?query=c%3A%2F</a></p>
  
  <p>If it is a false positive, how can we flag this so subsequent runs don't continue to flag this as an issue? We are using the weekly docker image for this automated process.</p>