browser no longer able to access any sites after loging into projectplace

VERIFIED FIXED in psm2.0

Status

Core Graveyard
Security: UI
P2
critical
VERIFIED FIXED
17 years ago
a year ago

People

(Reporter: Vladimir Ermakov, Assigned: David P. Drinan)

Tracking

({regression})

1.0 Branch
psm2.0
x86
Windows 98
regression

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
Browser no longer able to access any sites after loging into projectplace.com
and navigating to one of the sites inside. The secure connection breaks, and
when you go to any site, even if it has nothing to do with project place
(bugzilla, yahoo...) netscape says that it cannot connect to that site. 
 This works on Linux Redhat 2001-07-02-06-trunk build but not on 
2001-07-02-04-windows 98

Steps to reproduce
1) goto URL
2) put in "vladimire@netscape.com" as username, "bugzilla" as password
3) Once inside click on "Bugzilla Test" project, and try to go to "Document Archive"

Expected Results: List of uploaded files
Actual Results: Secure connection is broken (notice the lock ikon in the bottom
right corner is either red, or unlocked) and you are no longer able to go to any
site on the web.

Note: this came out of bug 88814, most likely not related
(Reporter)

Updated

17 years ago
Severity: normal → critical
Target Milestone: --- → mozilla0.9.3
->PSM.

If it involves HTTPS, assign it to the PSM product, not Security:General.
Assignee: mstoltz → ssaux
Component: Security: General → Client Library
Product: Browser → PSM
QA Contact: ckritzer → junruh
Target Milestone: mozilla0.9.3 → ---
Version: other → 2.0

Comment 2

17 years ago
-> ddrinan.
David. Can you try to replicate on windows.  I verified that it works for Linux
buildid 2001070204.
Assignee: ssaux → ddrinan
Priority: -- → P2
Target Milestone: --- → 2.0

Comment 3

17 years ago
Worksforme on WinTN except for being able to view the List of uploaded files, 
probably because the page is using style sheets.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 4

17 years ago
This also works for me on windows 2000. Looks like this is win 98 only.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

Comment 5

17 years ago
junruh: do you have a win98 machine to try this on?

Comment 6

17 years ago
Confirming the reporter's findings on Win98. WinNT is OK.

Comment 7

17 years ago
nsbranch
Keywords: regression
Whiteboard: nsbranch
(Assignee)

Comment 8

17 years ago
I think I know what the problem might be here: the nsNSSSocketInfo object that
is created for each SSL connection maintains a refenence to the necko
nsHttpConnection object. Since nsNSSSocketInfo is cached for lock icon/page info
purposes, the nsHttpConnection object is not being freed and as a result the SSL
socket is not being closed. On win98 this could be very bad over time since
socket resources are limited. I need to talk to the necko people to figure out
how to fix this.
(Assignee)

Comment 9

17 years ago
I have discussed with dougt a possible solution. A patch to follow soon.
(Assignee)

Comment 10

17 years ago
Created attachment 41996 [details] [diff] [review]
Patch. Dougt, please review.

Comment 11

17 years ago
This looks good to me.  r/sr=dougt
(Assignee)

Comment 12

17 years ago
Doug, who else should review this before I check it into the trunk?
(Assignee)

Comment 13

17 years ago
Fix checked into trunk.
Status: REOPENED → RESOLVED
Last Resolved: 17 years ago17 years ago
Resolution: --- → FIXED

Comment 14

17 years ago
r=gagan fwiw...
(Assignee)

Comment 15

17 years ago
Fix checked into branch.

Comment 16

17 years ago
*** Bug 90625 has been marked as a duplicate of this bug. ***

Comment 17

17 years ago
I tested this out on a win98 machine. Seems to be working fine now.

Comment 18

17 years ago
Thanks for fixing this as this is the only reason I'm using IE at the moment. 
Sorry about the duplicate bug 90625.  I did a search for PSM and secure and got
nothing so I assumed it had not been logged yet.
Win98 runs out of TCP connections at about 80 connections.

Comment 19

17 years ago
I just found out at
http://support.microsoft.com/support/kb/articles/Q158/4/74.ASP that it is
possible to increase the number of conncurrent connections via TCP with the
following entry in the win98 registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections
(string type). Default is 100

Although this is not the best way to solve problems that are bugs, but it would
have been a temporary fix but would eventually cause win98 to run out of memory.

Comment 20

17 years ago
Verified on 7/15 win98 branch.
Status: RESOLVED → VERIFIED
Whiteboard: nsbranch

Updated

13 years ago
Component: Security: UI → Security: UI
Product: PSM → Core

Updated

9 years ago
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.