How do I get rid of the attached security warning?

  • Profile Image
    Homeappraisalsinc
    Asked on July 02, 2013 at 03:14 PM

    Hi, I thought it was because my thank you page was not secure but then I made the thank you page secure. Please advise. Thank you.

  • Profile Image
    jonathan
    Answered on July 02, 2013 at 04:47 PM

    Hi,

    May I suggest that you re-embed  the form using again the iframe code and enable the SSL feature.

    Here are the guides to do them.

    1. Getting-the-Form-iFrame-Code

    2. How-can-I-receive-SSL-Submissions

    Also, I have checked your website html code. It is highly possible that the security warning you get on the page is not being caused by the form.
    Because you have other URL in your secure page that is not using https like this one

    Please try to correct also all the non https URL in the website page and test again.

    Inform us if the issues still persist after correcting them already.

    Thanks.

  • Profile Image
    odtechgrp
    Answered on August 26, 2016 at 02:34 PM

    Make note, that your CSS can also contain the "hidden code" which is causing the Security Warning message to display (as reported above.)  In my example, I was using one of the Jotform provided templates to create a form and making customizations to it. My user's were submitting their form (in IE) and when they would get to the Thank You page, they would then receive the same security warning message as outlined above. 

    To resolve this issue, I opened my form, clicked the Preferences tool/Form Styles/Custom CSS and changed all HTTP entries in the Inject Custom CSS source code area to HTTPS and clicked Save Changes.  This then kept the warning message from displaying to my IE 11 end users after they click the form submit button.

     

    Thanks.

  • Profile Image
    Jim_R
    Answered on August 26, 2016 at 03:42 PM

    Thanks for the input @odtechgrp - Indeed this security warning appears when there's a resource being loaded over plain HTTP while the form is running on HTTPS. So ensuring everything is being loaded from an https source should do the trick :)