-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
saveDataURL / saveData - what type of backend is expected #93
Comments
Note I did find this issue: #10 which talks about a SQL database, but I see no code in the github page related to SQL, authentication, or any other 'usual' things one would expect when connecting to a SQL db. |
Yes, Script will make a POST request with some parameters and values. You need to handle the request at the server side (you need to write your own code at server side). We do not have official support for this feature yet. |
Thank you - do you have a sample of how this POST request is formatted? I set I also tried port 80 to see if it put a log entry in my httpd logs, but it did not. clues to see what it's doing? Looking to see what data is sent to determine if I want to add a simple script to capture results. Thanks! |
Enable it and look at the browser console to view the POST request. 4500 is just an example. You need to replace the URL with your own database handling URL, for example, yourdomain.com/savedata.php. |
I did also look in 'inspect' console but do not see it. per above I did set Console screenshot, the last red error occurs (and continues to loop?) after test is complete. 'Developed by' shows up when one hits start. Looks like the line refers to |
Declare a variable named |
Is the |
// This will match the protocol http or https used by the browser. You can also specify https:// |
In the config elemnts there's references to 'saving data' from a result:
var saveDataURL = "//yourDatabase.Server.com:4500/save?data=
Is this implemented, and if so what type of 'database' is it looking to send to on port 4500? per
/etc/services
this seems to not be a standard port for a known database server.The text was updated successfully, but these errors were encountered: