- heirloomAsked on November 22, 2011 at 09:20 PM
...makes insecure http callbacks? Any option for https?
- JotForm SupportliyamAnswered on November 23, 2011 at 01:59 AM
Let me forward your concern to our development team, Gary. They will respond to this as soon as they're available.
- JotForm SupportliyamAnswered on November 23, 2011 at 03:14 AM
I also forgot to mention, you can manually change the URL of your wishbox from http://www.jotform... to https://www...
formId : "xxxxxxxxxxx",
buttonText : "Wishbox Beta",
base : "https://www.jotform.com/",
background : "#F59202",
fontColor : "#FFFFFF",
buttonSide : "bottom",
buttonAlign : "right",
type : false,
width : 380,
height : 457,
instant : true
- heirloomAnswered on November 23, 2011 at 10:35 AM
Hi Liyam. Yes, I had already done as above before sending the question in (sorry, I should have mentioned that). Problem is, as Wishbox executes, it's own calls/callbacks are done over http (and so the website becomes "untrusted").
- paoloumaliAnswered on November 23, 2011 at 02:57 PM
Thank you for the details. As advised, we shall have the updates on this thread.
Thank you for using JotForm and in helping us through these reports.
- jeffcmohrAnswered on January 05, 2012 at 08:33 PM
Has there been any update as to whether the submissions via jot form are secure?
- JotForm SupportmlizAnswered on January 05, 2012 at 09:17 PM
As of the moment this is being checked on by our developers once we have any information on the progress we will let you know. Thank you for the patience and understanding as we work on this.
Sorry for the inconvenience.
- serkanAnswered on March 12, 2012 at 05:46 AM
This issue should be fixed now. Thanks for reporting.
- nodespotAnswered on June 23, 2012 at 04:54 AM
Hi, just got Wishbox and it's not working properly on HTTPS. Same issue as mentioned above, it's calling non secure pages and Chrome is throwing warnings.
- JotForm SupportliyamAnswered on June 23, 2012 at 07:13 AM
Hello, nodespot. Can you give us the URL where this wishbox is installed?
- lighthousepatternsAnswered on July 14, 2012 at 04:05 PM
I really like this feature too but as reported above, there are many things later in the pipeline that are unsecured, causing warnings. But worse still, I actually get three different errors before it halts and never comes up. So as much as I like this product and was going to use it for support help, this will only lead to more support frustration. So we have to pull it.
Background. This is on Chrome as one test. This worked flawlessly while on HTTP. I have confirmed that the only difference between it working and not, is enabling it over HTTPS. And yes, I converted all the links to HTTPS on my end. Unfortunately I am not able to share the URL of the application at this time. I do however have a screenshot of the three errors in Chrome and a capture of the request details of each one, as reported by Chrome. Please let me know if you would like this info.
- JotForm SupportliyamAnswered on July 15, 2012 at 01:46 PM
Hello Mike. It would be great if you have a sample page that you can share with us so that we can try replicating the issue. This way, we can also check the source code if there is anything in there that might be causing the error you're experiencing. But nonetheless, I have forwarded this to the developers.
Thank you for your patience.
- lighthousepatternsAnswered on July 15, 2012 at 01:56 PM
I don't think that would be necessary. I found this recent support thread which as of a couple days, is still open. This post is very similar to the issues I am having. I actually have three errors but this one is in common and based on the responses, it would seem HTTPS just isn't fully supported yet.
- JotForm SupportliyamAnswered on July 15, 2012 at 02:07 PM
Thank you for pointing the other thread out, Mike. Indeed, the other topic is of the same issue so what I did was I indicated this thread to the other one for reference.