Closed Bug 62652 Opened 25 years ago Closed 14 years ago

"secure" should be included in statustext when dealing with https

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: bugzilla, Unassigned)

Details

If you go to hotmail.com and try to log in, the browser with try to contact a https:// server. It could be nice if the status bar would say: "Resolving secure host" instead of just: "Resolving host" this way you would be able to tell if there's gonna be problems because of the missing psm.exe...
Yeah.. there are a bunch of things that we could do to better inform the user about PSM. This is one of them. Thanks!
A more general bug now: "Sending request to" should also be changed to: "Sending secure request to" etc...
Summary: "Resolving host" should be "Resolving secure host" when dealing with https → "secure" should be included in statustext when dealing with https
Target Milestone: --- → Future
-> default owner
Assignee: darin → nobody
QA Contact: tever → networking.http
Target Milestone: Future → ---
(DNS) Resolving is independent from the used protocol. Why should we add it ?
HTTPS isn't necessarily secure, because transport-layer security is only one aspect of security. Consequently, we can't call something "secure" just because it is using TLS. Also, comment 4 is correct; DNS is independent of TLS.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.