Insecure call.

Hi @jezzaz,

We do not hardcode http for our form requests – they all come from the website’s protocol. Can you send me a URL to your form so I can check it out? Also, make sure you’ve cleared your API cache in the plugin and your browsers cache.

Cheers,
Kevin.

Hi @jezzaz,

Are you able to do Kevin’s suggestions above or provide a link?

Let us know.

Thank you!
-Tracy

Hi Tracy and Kevin, thank you for your repsonses i did clear the API cache (its greyed in now ) and the website cache, the lock is showing on the site in the browser , its just when i run it through https://www.whynopadlock.com/ it says Insecure <form> call.
Found on line # 32 in file: mindfulness-healing.co.uk/index.html
(Note: Chrome will show a security error for any secure page with an insecure <form> call on the page), i am not sure where the index.html is coming from, the site is https://mindfulness-healing.co.uk/

Hi @jezzaz,

The index.html is referring to the homepage of your website – the URL you linked. I am not sure what’s triggering the alarm as there are only two forms on the site and neither are going through HTTP. However, do you have about 4 different links to HTTP versions of your site:
https://mindfulness-healing.co.uk/mindfulness-as-a-life-skill-course/
https://mindfulness-healing.co.uk/mindfulness-retreat-days-london/
https://mindfulness-healing.co.uk/mindfulness-based-cognitive-therapy-course/
https://mindfulness-healing.co.uk/mindfulness-practice-london/

Additionally, the majority of your website is “minified” to a single line – line 32 -and I’m wondering if whynopadlock is getting an incorrect reading of the code due to this (possibly seeing a <form> element and an http link on the same line is throwing it off).

Thank you for taking the time to look into this , i am going to change the links and see if that fixes it

its the minification by the looks of it , i turned it of for HTML and I’m not seeing that issue on why no padlock, when i turn it back on it shows up again, thanks again

No problem!

We’re always interested in a potential security issue so thank you for bringing it to our attention. Fortunately in this case I do not believe it’s a real security issue.

Cheers,
Kevin.