|
This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] I've got a lawson application that we have setup for port 8080 (http server) When I set it up for http traffic it works just fine. I got a certificate from verisign and installed it. Then I set that http instance to only use 8080 for ssl traffic only (https) It does not function anymore....just locks up and in the http error logs I get a SSL handshake failure RC -11. Which when I go into QSYSINC/H(SSL) QSYSINC library H file SSL member And do a search on -11 it says "bad message" As I am not a webmaster (or even close to it) I am assuming that any web application is both ssl/non-ssl compatible (it's just a matter of adding the certificate into the mix) right ? Now...to add some fun into the mix I have another web instance using this same application But just pointing to a different welcome page using the same certificate And it works fine...so I really don't think it's the certificate. I assume a communications trace would be beneficial to start off with. What other sort of questions should I ask IBM when I call them? Jim Norbut Systems Administrator Grubb & Ellis Company (847) 753-7620
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.