Closed
Bug 514847
Opened 15 years ago
Closed 15 years ago
"reported attack site" not showing html source
Categories
(Firefox :: General, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 397937
People
(Reporter: marun2, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
The URL (Currently) is a 'reported attack site' as claimed by Google. Now I hit Ctrl+U to see what code they had to be considered 'malicious', and it doesnt show the source code, instead it shows the same warning again, now if I were smart enough to hit Ctrl+U, then I dont need that warning again right? Furthermore, when this warning appears after hitting Ctrl+U, none of the buttons work - the "get me out of here" "Ignore this warning" etc. if none of the buttons work, why show the warning in the first place?
Reproducible: Always
Steps to Reproduce:
1. Go to url
2. Hit Ctrl+U
Actual Results:
Shows Reported attack site warning.
Expected Results:
Show the source code.
I had this problem with a site and I tried using firefox to find what script code has been injected, by using view source. Firefox assumes I am a newbie and shows me the reported attack site warning even in view source mode. Then I had to use IE8 to view source to see the injected source code as it appears in client side - bottom line - if user wants to view source, better show the source, irrespective of attack site or not.
Comment 1•15 years ago
|
||
I think this is intended, so you can't use the malicious code/be attacked by it, looking at the source.
Updated•15 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•15 years ago
|
||
How can I 'be attacked' when I am using view source mode? In that mode, it is not supposed to execute any code at all, if it does, then it is another bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•