Closed
Bug 214812
Opened 21 years ago
Closed 21 years ago
Symantec's Security Scan does not start
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 185725
People
(Reporter: erik_coolen, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 Hi, When I go to the above URL and click on 'Start' in order to start Symantec's online Security Scan, I get transferred to another page (http://security.symantec.com/ssc/not_found.asp?j=1&langid=ie&venid=sym&plfid=23&pkj=RZTBYNBRFNJSVSTIVVB) that states: "Sorry! The page you requested is not accessible..". I.e., the test never runs. The same thing happens on Mozilla 1.41, but the test runs fine on IE. Is there anything you guys know about this problem? Thanks, Erik Coolen, The Netherlands Reproducible: Always Steps to Reproduce: 1. Go to "http://security.symantec.com/sscv6/home.asp?j=1&langid=ie&venid=sym&plfid=23&pkj=FBHBWOBWYSHSFVIGMKI" 2. Click on 'Security Scan' or 'Start' 3. I then briefly get to see a screen stating: "Determining browser scripting capabilities" 4. The site redirects me to "http://security.symantec.com/ssc/not_found.asp?j=1&langid=ie&venid=sym&plfid=23&pkj=EYWBQKZWCGZYFVHDYKD" and tells me "Sorry! The page you requested is not accessible" etc. No test is run. Actual Results: No online security test as run Expected Results: Run and complete the test (as IE does)
Comment 1•21 years ago
|
||
*** This bug has been marked as a duplicate of 18575 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Comment 2•21 years ago
|
||
reopening; wrong bug #
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 3•21 years ago
|
||
*** This bug has been marked as a duplicate of 185725 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•