Closed
Bug 615182
Opened 14 years ago
Closed 12 years ago
can't view source of page in phishing filter (Safe Browsing)
Categories
(Toolkit :: Safe Browsing, defect)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: bugzilla.com, Assigned: mmm)
References
()
Details
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b7) Gecko/20100101 Firefox/4.0b7
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b7) Gecko/20100101 Firefox/4.0b7
A page appearing on Google's Safe Browsing blacklist gives "Reported Attack Page!" warning. When trying to view the source code of the blacklisted page, the same warning appears: 'Ignore this warning' does not work
Reproducible: Always
Steps to Reproduce:
1. Visit a blacklisted page (http://www.lenmiddelbeek.nl/index_bestanden/Page596.htm)
2. Click 'ignore this warning' to view the actual page
3. Click 'page source' (ctrl+u or view->page source)
4. Click 'ignore this warning' in the new window titled: "Source of: Reported Attack Page!"
Actual Results:
"Reported Attack Page!"
Expected Results:
source of said page
NoScript set to "Allow Scripts Globally"
Updated•14 years ago
|
Component: General → Phishing Protection
QA Contact: general → phishing.protection
Version: unspecified → Trunk
| Assignee | ||
Comment 1•14 years ago
|
||
This looks like a fun bug to work on.
The actual result is that interacting with the page from within view-source does not do anything, the user is stuck at the warning page.
Assignee: nobody → mars.martian+bugmail
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
| Assignee | ||
Comment 2•14 years ago
|
||
It also seems the hostname is not shown in the warning displayed. That is, the blurb reads "This web page at has been reported as a...".
Comment 3•14 years ago
|
||
Related bug is bug 397937.
Comment 6•12 years ago
|
||
I don't think this is useful to fix.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Updated•11 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•