Closed Bug 34810 Opened 26 years ago Closed 26 years ago

Secure section not accessable

Categories

(Core :: JavaScript Engine, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: nathan, Assigned: security-bugs)

References

()

Details

(Whiteboard: [nsbeta2+][dogfood-])

Windows NT 4 SP5 Build 2000033112 Go to the main page of www.equitable.co.uk. Click on Client Service Logon image button at the top. It says you are now entering a secure area message, but gets no further. The process then seems to go into a loop, and takes up large amounts of the processing usage. Expected It should show the standard browser authorisation dialog with username and password. I can't tell if it is bad HTML because the link is a HTTPS and the w3c validator doesn't work with them.
reassign to crypto.
Assignee: norris → dougt
Component: Security: General → Security: Crypto
Reassigning to javascript and mstoltz. Clicking on "Client Service Login" locks up the browser. Clicking on the link attempts to call up javascript:parent.login('services.nsf/services?openform',"Y")
Assignee: dougt → mstoltz
Component: Security: Crypto → Javascript Engine
Target Milestone: --- → M17
Keywords: dogfood
[nsbeta2+]
Whiteboard: [nsbeta2+]
Confirming. Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
The link mentioned is a javascript URL. This might be related to the javascript URL referrer problem, that's my first impression. Otherwise it might be a bug in the JS crypto API.
Status: NEW → ASSIGNED
Putting on [dogfood-] radar since [nsbeta2+] already indicated.
Keywords: nsbeta2
Whiteboard: [nsbeta2+] → [nsbeta2+][dogfood-]
The behavior I saw when running this testcase was different. Filed bug 42773 on that issue. I'll leave this one open since 42773 may be covering this one.
Depends on: 42773
Changing QA to czhang
QA Contact: junruh → czhang
This works now, with the fix to bug 42773. I see the SSL login dialog, which seems to work fine. If there's still a problem accessing this site, please open a new bug and assign it to the Security:Crypto component. Marking FIXED.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.