Hehe. I should have googled before posting. Here is a 4D case that explains how to set up chained certs with 4D's webserver.
<ttp://www.4d.com/knowledgebase?CaseID=34856>
On 2/9/07, Michael Check <[EMAIL PROTECTED]> wrote: > I should have searched the 4D list _before_ suggesting to a client > they get the wildcard chained ssl certificate from godaddy. I just > found a bunch of refs to people having trouble with getting the certs > to work in many browsers, particularly Safari. > > Our client is running A4D 4 on osx.3.9 and we need to install this > certificate to the 4D server in order to run secure A4D sites. Has > anyone done this with 4D and the godaddy chained certificate? It is > basically a wildcard cert that allows foo.bar.com to be the same cert > as foofoo.bar.com > > For 4D's ssl use, you've got the cert.pem and the key.pem > > I'm wondering if I'll have to set up Apache as a proxy, running the > certificates, sending to 4D and A4D.
_______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
