Bug #136
Exceptions Fail To Match Correctly
Start date:
04/29/2010
Due date:
% Done:
100%
Description
It appears that exceptions fail to match on some URLs; thus preventing some issues from being excepted.
History
#1
Updated by Luke Murphey over 15 years ago
Updated by - Assignee set to Luke Murphey
#2
Updated by Luke Murphey over 15 years ago
This may occur because the URL is being stored in a different format in the exception than the original. This conclusion was based on the following observations:
- Two of the exceptions that did not work were for URLs with %20 in them (perhaps this is not being replaced by spaces?)
- Exceptions worked when the URL was omitted
#3
Updated by Luke Murphey over 15 years ago
It looks like the application is mixing up the protocol specifier. This occurs when a page forwards to another page. The exception refers to the original URL (non-forwarded) while the exception is checked against the final (forwarded) URL.
#4
Updated by Luke Murphey over 15 years ago
Here are the options:
- Check for exceptions against the original and final URL; consider the URL under exception if either matches
- Save the final URL in the scan result findings
- Save the original URL and the final URL in the scan result findings
#5
Updated by Luke Murphey over 15 years ago
- Status changed from New to Closed
- Priority changed from Normal to High
- % Done changed from 0 to 100
The original and final URLs are now checked to determine if an exception exists. Implemented in r429.