Closed Bug 252992 Opened 21 years ago Closed 20 years ago

SOAP: Mozilla crashes when trying to request an SOAP-service via not certificated SSL

Categories

(Core Graveyard :: Web Services, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: a.dorn, Unassigned)

Details

(Keywords: crash)

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.6) Gecko/20040113 The SOAP-Request e.g soapCall.transportURI = "https://PearServer.php" via not certificated SSL crashs the Mozilla. There is the massage about the missing certification, but even if you accept Mozilla crashs. You can find the files (SOAP-Server, and Soap-Mozilla Client) here: http://www.sitesol.de/MozillaBugSOAP.zip Nevertheless: The SOAP-Implementation is FANTASTIC :-) Thank you! Reproducible: Always Steps to Reproduce: 1. 2. 3.
252992
;-) THE SOAP-SERVERS URL ist soapCall.transportURI = "https://localhost/PearServer.php" BUT THIS DOES NOT CHANGE THE BUG....
Summary: SOAP: Mozilla crashs when trying to request an SOAP-service via not certificated SSL → SOAP: Mozilla crashes when trying to request an SOAP-service via not certificated SSL
Alexis: Could you provide TalkBack incident ID?
Keywords: crash
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/
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: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.