Closed
Bug 358403
Opened 19 years ago
Closed 17 years ago
Session restore: loading wrong content for frames
Categories
(Firefox :: Session Restore, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: apang, Unassigned)
References
()
Details
Attachments
(4 files, 1 obsolete file)
While in a logged in session with this business portal, the OS locked up while on a payment form. The computer/OS was warm-booted. Firefox restored the session by opening two tabs. The first tab was the portal login screen (unexpectedly malformed because FF loaded the wrong content for the frames), while the second (visible, active) tab correctly displayed the same login form. Neither tab restored the previous login session, nor displayed the payment form.
| Reporter | ||
Comment 1•19 years ago
|
||
| Reporter | ||
Comment 2•19 years ago
|
||
| Reporter | ||
Comment 3•19 years ago
|
||
Attachment #243800 -
Attachment is obsolete: true
| Reporter | ||
Comment 4•19 years ago
|
||
| Reporter | ||
Comment 5•19 years ago
|
||
Comment 6•19 years ago
|
||
The problem is that the content of those frames depends on you being logged it, however Firefox doesn't save your log-in information because the site is accessed over a secure connection. While it restores the correct URLs, the site itself redirects you to the log-in page for every non-allowed page access (i.e. in most or all frames).
There's really not much we can do about this issue though, because there no way we could make a difference between URLs which can be restored as expected and the few exceptions where a cookie is needed but not saved/restored because of privacy reasons (note: not all discarded cookies are relevant for login).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•19 years ago
|
Component: General → Session Restore
Updated•19 years ago
|
QA Contact: general → session.restore
Updated•18 years ago
|
Whiteboard: [invalid?]
Comment 7•17 years ago
|
||
INVALID per comment #6.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Whiteboard: [invalid?]
You need to log in
before you can comment on or make changes to this bug.
Description
•