Skip to content
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

Running over HTTPS #47

Open
markwynter opened this issue Mar 10, 2016 · 3 comments
Open

Running over HTTPS #47

markwynter opened this issue Mar 10, 2016 · 3 comments

Comments

@markwynter
Copy link

Hi there! We're wanting to deploy nanocubes through iframe in web portal(s) - we've implement a replace rule on application nginx server http://" and "https://" to just "//" (so protocol independent URL) - but this doesn't appear sufficient as nanocube server side JavaScript is making http requests which breaks if front end portal is https. Equally if we hard code https URLs in the nanocube backend, we can't support portals running over http. Is there a protocol independent solution we can implement on nanocube server side? Any guidance would be most appreciated. Kind regards, Mark

@markwynter
Copy link
Author

Just to clarify, the issue is with nc_web_viewer, and our requirement is to make the nanocube application server protocol agnostic so we can embed the nc_web_viewer in iframes that may be served independently over http or https.

@laurolins
Copy link
Owner

Nanocube uses the Mongoose Embedded Web Server Library for its web communication infra structure. The master branch version of the nanocube server allows you to pass an SSL certificate file .pem with the option --sslfile <pem-file> which triggers the mongoose option "ssl_certificate". Here is the code for that on line 160 of src/Server.cc
mg_set_option(srv, "ssl_certificate", pemfile.c_str());

Here is the template of the call:
nanocube-leaf -q <query-port> --sslfile <ssl-certificate> < <dataset-file>

@markwynter
Copy link
Author

Thanks Lauro - we're still grappling with this - I've asked my developers to clearly layout the issue, which I'll share with you shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants