Closed Bug 67203 Opened 24 years ago Closed 24 years ago

browser not opening secure site

Categories

(Core Graveyard :: Security: UI, defect, P1)

1.0 Branch
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: tracy, Assigned: gagan)

References

()

Details

Attachments

(2 files)

seen on commercial builds:

windows 2001-01-31-06-mtrunk
linux 2001-01-31-06-mtrunk

-attempt to go to the secure site above.

the browser does nothing.
Reassigning
Assignee: ddrinan → javi
Priority: -- → P1
psm starts up fine... and IMAP/S works, so this is a browser problem. gagan?
I just re-built on Mac and whenever I type https://, the following line asserts
http://lxr.mozilla.org/mozilla/source/netwerk/protocol/http/src/nsHTTPHandler.cpp#273

This looks like a necko problem.
Assignee: javi → gagan
adding self to cc list.
*** Bug 67249 has been marked as a duplicate of this bug. ***
I've got a slightly better fix, I think.  It lets us not put any HTTPS stuff in
nsHTTPHandler.  Patch coming up.
Attached patch patch #2Splinter Review
r=dbaron, although perhaps this is a case where it would be better to skip the
optimization (maybe ask gagan once this is less urgent)?
Checked in fix.  gagan, feel free to comment regarding what the "right fix" here is.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
I completely agree with bryner here. we should keep HTTPS stuff out of HTTP as 
much as possible and his fix is the right one. 
Verified on the 2/1 Win, Mac and Linux builds.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: