Non-secure SSL submissions?

  • Profile Image
    Asked on May 01, 2013 at 06:40 PM

    I have read through the forum about how to change the embed code to allow non secure submissions. I however did not not embed forms with the security in the url, but still reembedded the form with non secure URL, retested and now I have 2 SSL submission both from tests. Help? If you use captcha, does that automatically make the form secure?

    If it helps, the forms are posted in my google site which is https://  And the form contains an upload file field. But that shouldn't make a difference right? Although I tested with a different form and without file upload field there was no SSL submission. After I added upload file field, there counts another SSL submission. up to 3 now.


    Also, the google site does not allow me to use the specified URL the Jotform support references in the forum (it gives an error message), here is the error message: Unsupported feature: org.apache.shindig.common.xml.XmlException: The element type "input" must be terminated by the matching end-tag "". At: (86,103)

    Google site does not take this code in the screen shot. I have to use the embed code at the bottom of the embed instructions which includes no https or secure in the url... looks like this:

    Is there another way to use the specified link in the nonsecure version of the screenshot in the html or link field of my google site. Basically is there another method to use the the http://secure url besides the method located in the embed form region here?

    Help greatly appreciated!

  • Profile Image
    Answered on May 02, 2013 at 01:40 AM


    I could help you much better if I could at least check on the https website where the form was embedded.

    Can you share to us the URL of your website where the form is?

    Normally, 2 things can happen when you embed a non-secure URL form into a secure(https) page.

    1. Everytime the URL of the secure page is used, the client browsers will be able to detect if there are non-secure content on the page. So, if the regular form is embedded on the page, the browser will usually prompt a message (i.e. certifcate error)

    2. If the browser certificate error is ignored, the page usually get stuck and will stop. Usually, a page browser will "allow" the continuation of the page. When "allow" is chosen, the non-secure content is being included to a secure layer.. this will then result, in the case of the form submissions -- to secure submission.

    Hope this help. Please update us of the URL of your website so we can further check.



  • Profile Image
    Answered on May 02, 2013 at 08:36 PM

    Thanks so much for your response and explanation! Here is the URL:

  • Profile Image
    Answered on May 03, 2013 at 02:47 AM


    I checked your webpage and see that it still submit to "https" url. Refer screenshot below:

    Request you to please delete the existing script and use non-secure embed script to embed your form in your webpage. Please follow these steps to get new non-secure embed script.

    1. Open you form in form builder

    2. Click "Setup & Embed" tab.

    3. Ensure that the Secure checkbox is not checked when you get the embed script.


    Let us know if you continue to have this issue and we will investigate further.