Closed
Bug 154616
Opened 23 years ago
Closed 12 years ago
No redirect warning as in Nav 4.79
Categories
(Core Graveyard :: Security: UI, defect, P1)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: junruh, Unassigned)
References
()
Details
(Whiteboard: [kerh-coz])
6/26 branch. 1.) Visit http://finance.yahoo.com/fundstransfer
2.) Click on the Get Started Now button.
What happens: I get a warning that I am sending unencrypted data.
What is expected: As with 4.79 "Warning! Your connection has been redirected to
a different site. You may not be connected to the site that you originally
tried to reach."
Updated•23 years ago
|
Severity: normal → major
Priority: -- → P1
Target Milestone: --- → Future
Comment 2•22 years ago
|
||
I agree, but showing the different warning is not enough.
4.x also allowed you to cancel the connection when you are being redirected to a
different site.
We need to implement 62178 before we can fix this one.
Comment 4•21 years ago
|
||
Mass change "Future" target milestone to "--" on bugs that now are assigned to
nobody. Those targets reflected the prioritization of past PSM management.
Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---
Updated•19 years ago
|
Whiteboard: [kerh-coz]
Updated•18 years ago
|
QA Contact: junruh → ui
Comment 6•12 years ago
|
||
I suggest WONTFIX. If this has been the behavior for over 10 years there's probably too many backward-compatibility issues. We've gotten rid of all active HTTPS-related security prompts like this (e.g. the ones that warn about switching from HTTPS to HTTP and vice versa via clicking on links), and I'm not keen to add one back without a clear explanation of why it is necessary.
Comment 7•12 years ago
|
||
Agreed. At the very least, if someone feels super strongly about this, open a new bug (feel free to refer to this one) with a compelling rationale for why this is relevant on the modern web.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•