- shaunnaylorAsked on June 05, 2011 at 09:11 AM
I have a secure server with globalsign, when i embedd a jotform with https, the page indcates insecure content, is this because jotform is classed as a 3rd party?
- allanftdAnswered on June 05, 2011 at 11:15 AM
May we ask from which application/program did you get the message that the page has insecure content? Kindly provide a screenshot of the message if possible. May we also ask for the URL of your website where the form is currently embedded so thatwe canperfrm further checking from our end?
We appreciate your cooperation and prompt response. Thank you for using JotForm!
- shaunnaylorAnswered on June 05, 2011 at 11:25 AM
this is the url
I really hope you can help me as i dont want to redirect people to another page, plus using paypal pro, means people wont enter credit or debit info
- JotForm SupportNeilVicenteAnswered on June 05, 2011 at 02:37 PM
Is this the message you were talking about?
This message means that there is an element on your page that is not using https. Upon checking your source codes, I can see that you have used your form's secure URL. I believe that the fact that it the form is called using secure (https) embed codes puts the form out of question.
I have a feeling that the unsecure element is something else beside from the form, although I am having a hard time figuring it out because I do not have a domain with ssl certificate to test your page in.
Can you try removing the form from your page and then see if the message still comes up? Thank you. I am looking forward to your response.
- shaunnaylorAnswered on June 05, 2011 at 03:58 PM
Hi Neil thanks for your advice,
When i remove the form the green https shows ok, and when i send the form via email jotforms https shows ok.
Could it be because i'm using globalsign and jotform use godaddy, do they clash?
- allanftdAnswered on June 05, 2011 at 05:55 PM
Thanks for the update. Google Chrome provides additional information about the SSL certificate issue:
It falls short in identifying which particular resource(s) on your website is causing the problem. You have a good guess there about having two different issuers of the certificate, but I'm also thinking it might be because we're using 256-bit SSL security certificate, and Globalsign is using 128-bit SSL hence causing some conflict between the two.
For now, you may need to settle with the workaround you mentioned in your latest post using JotForm just to eliminate the error message and avoid bringing the negative impression to your visitors.
Thank you for using JotForm and have a great week ahead!