Closed Bug 435726 Opened 17 years ago Closed 16 years ago

Cannot view source code for page under phishing protection

Categories

(Toolkit :: Safe Browsing, defect)

3.0 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: bugzilla, Assigned: Unfocused)

References

()

Details

(Whiteboard: workaround in comment 10)

Steps to reproduce: 1) Load page http://www.mozilla.com/firefox/its-an-attack.html 2) Click Ignore link so you can see "It’s an Attack!" page. 3) Now press CTRL+U to see its HTML source code Results: HTML souce code is inaccessible. In the source code window is Antiphishing warning again and you cannot pass through it.
Confirming with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008052506 Minefield/3.0pre
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.9.0.1?
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
This isn't quite the same bug as bug 397937, given step 2), but it seems likely that any solution to it would depend on the a fix for bug 397937.
Status: RESOLVED → REOPENED
Depends on: 397937
Resolution: DUPLICATE → ---
I agree, bug 397937 is not duplicate of this bug. In fact, bug 397937 is not actually a bug. But this one definitely is. If I agree to view malicious page as is, why can't I view its source?
Flags: wanted1.9.0.x?
Flags: blocking1.9.0.1?
Flags: blocking1.9.0.1-
This isn't really wanted1.9.0.x, though I agree it sucks. Let's try and get it in 1.9.1.
Flags: wanted1.9.0.x?
Flags: wanted1.9.0.x-
Flags: wanted-firefox3.1?
Flags: blocking-firefox3.1?
This is really annoying as it ends up protecting the phishers source code, that makes it harder to track down and warn the ISP hosting the criminal's drop box. I could turn the protection off but that means I can't tell whether a phishing page has already been reported.
Not blocking, but would take a patch ...
Flags: blocking-firefox3.1? → blocking-firefox3.1-
Flags: wanted-firefox3.6?
Flags: blocking-firefox3.6?
tweaking summary to catch dupes better. You can get around this bug with the web developer toolbar's "View Source" or by manually prepending "view-source:" to the blocked URI, eg: view-source:http://www.mozilla.com/firefox/its-a-trap.html Either way will get you the malware block but since it's in a normal tab/window you'll have a working "Ignore Warning" link. Since none of the buttons work on a malware block in the view-source popup I'm guessing it's simply not got the event-handling code for them (it's not a normal browser popup window, note how the menu is different and there's no location bar).
Summary: Cannot access HTML source code for page under phishing protection → Cannot view source code for page under phishing protection
Whiteboard: workaround in comment 10
Status: REOPENED → NEW
OS: Windows XP → All
Hardware: x86 → All
Not worth focusing on this for Firefox 3.6, cc'ing ddahl who's starting to transition into owning these issues.
Flags: wanted-firefox3.6?
Flags: wanted-firefox3.6-
Flags: wanted-firefox3.5?
Flags: blocking-firefox3.6?
Flags: blocking-firefox3.6-
Assignee: nobody → bmcbride
Status: NEW → RESOLVED
Closed: 17 years ago16 years ago
Resolution: --- → FIXED
Has Blair McBride's patch been included in a release yet? How would I find this information out?
(In reply to comment #17) > Has Blair McBride's patch been included in a release yet? How would I find this > information out? comment 15 has a link to the moz-central changese, so I assume this change is in the minefield nightly build
(In reply to comment #18) > comment 15 has a link to the moz-central changese, so I assume this change is > in the minefield nightly build Yes, in nightlies, but not in 3.6.x.
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.