zaproxy: No Way to Specify Custom 404

What steps will reproduce the problem?
1. Scan something that returns custom a 302 to a custom 404 error message.

What is the expected output? What do you see instead?
Lots of False positives, especially when it comes to default files.

What version of the product are you using? On what operating system?
1.0.0. OS doesn't matter.

Please provide any additional information below.

Original issue reported on code.google.com by logicalgambit on 2010-10-06 16:13:56


Part 1

Part 2

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Comments: 17 (16 by maintainers)

Commits related to this issue

Most upvoted comments

The user guide will have to be updated to document the new functionality, added a task.