Form conditions only working under HTTPS

I have a few forms that have conditions on them to hide certain elements unless a hidden field is filled.  I use a form with a PHP script on the front end to automatically populate the hidden fields based on the input to that form.  That has worked for some time, but now the conditions seem to have broke.  When you use the form over port 80 (HTTP) it doesn't work, but using the form over 443 (HTTPS) works fine.

Here's one of the forms for example: http://form.jotformpro.com/form/32784382063962

and with http://form.jotformpro.com/form/32784382063962?mpmnetId=t as a fake should allow you entry.  But it doesn't.

However, https://secure.jotformpro.com/form/32784382063962 works and locks you out, and with the fake address https://secure.jotformpro.com/form/32784382063962?mpmnetId=t it bypasses you into the form like it should.

Why is the form now only working with HTTPS?

Hi,

Thank you for contacting us.After testing your form I was unable to replicate the problem you are experiencing.The form works with both HTTP and HTTPS.See the screenshot below

http://form.jotformpro.com/form/32784382063962?mpmnetId=t

 and

http://form.jotformpro.com/form/32784382063962

if you still experience the  issues  please Let us know so that we can be able to give further assistance.

Still not working on my end.  I've tried several different browsers on both Windows and Mac.  I'm also getting the issues both in the school and at home.

I can't replicate this problem either.

Non-Secure:

Secure:

I've cleared your forms cache. Please kindly do the same your browser(s). If it still not working, then please try clearing your browser cookies as well.

Thank you!

Found the problem.  I pulled up the live log for our web filter and then tried to access the forms.  For some reason Jotform is being blocked by our web filter.  I just white listed all the various jotform domains (and allowed subdomains).  Everything works now.  Our filter only uses URL filtering for SSL traffic so hence why it worked on 443 only.

Hello DPoorman,

I am glad to know that you were able to figure out the issue and resolve it.

Do get back to us if you have any questions.

Thank you!