Closed
Bug 249976
Opened 22 years ago
Closed 21 years ago
no timeout when SSL negotiation broken
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: hauser, Assigned: darin.moz)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040614
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040614
with recent tomcat versions, it happens that SSL is broken
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29907), Mozilla, however only
says in the status bar "Connected to hostname.domain.tld..."
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Actual Results:
nothing - hanging
Expected Results:
a reasonable timeout that indicates where in the SSL negotiation, the protocol
failed...
| Reporter | ||
Comment 1•22 years ago
|
||
starting mozilla with the "-debug" option didn't provide any further insight...
| Reporter | ||
Comment 2•22 years ago
|
||
when killing tomcat, then one gets the error "connection refused"
| Assignee | ||
Comment 3•22 years ago
|
||
Ralf: Can you please provide a Mozilla HTTP log using the steps given here:
http://www.mozilla.org/projects/netlib/http/http-debugging.html
Thanks!
| Reporter | ||
Comment 4•22 years ago
|
||
two snapshots of the log:
1) while it was hanging
2) after I pressed the stop button
| Reporter | ||
Comment 5•22 years ago
|
||
attached the dump with ethereal.
openssl stopped pretty soon:
Ralf:~> openssl s_client -state -connect bugs.privasphere.com:8443
CONNECTED(00000003)
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
| Reporter | ||
Comment 6•22 years ago
|
||
perhaps BC will help finding the problem
(http://www.bouncycastle.org/devmailarchive/msg03267.html)?
| Reporter | ||
Comment 7•22 years ago
|
||
A recent version opera says also "Setting up secure connection..." and hangs
[root@host ~]# wget http://host.mydomain.com:8443
--10:52:23-- http://host.mydomain.com:8443/
=> `index.html'
Resolving host.mydomain.com... done.
Connecting to host.mydomain.com[194.236.119.150]:8443... connected.
HTTP request sent, awaiting response...
What is the specific expected behavior here? Even if the negotiation is fails,
not all protocols specify timeouts for these situations (they should, but they
don't always).
If the network connection were dropped, I'm pretty sure docshell & necko would
handle this correctly. If this is still in SSL, then we need to know what state
it is in, and whether or not PSM should be doing some kind of disconnection event.
Comment 9•21 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 10•21 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•