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

Load MathJax.js using HTTPS when IPython notebook server is HTTPS #1749

Closed
invisibleroads opened this issue May 21, 2012 · 6 comments
Closed
Milestone

Comments

@invisibleroads
Copy link
Contributor

When IPython notebook server is HTTPS, opening an IPython notebook creates an Insecure Content warning.

To avoid this, it may be useful to load MathJax via HTTPS when the notebook server is HTTPS.
http://www.mathjax.org/docs/2.0/start.html#mathjax-cdn

The current workaround is to install MathJax locally.

@minrk
Copy link
Member

minrk commented May 21, 2012

Are you using 0.12? I believe master already does this.

@fperez
Copy link
Member

fperez commented May 21, 2012

Indeed, that seems to be the case. It looks to me like we can close this, right?

@minrk
Copy link
Member

minrk commented May 21, 2012

Yup. Not only that, this has already been opened and closed as #1450.

@minrk minrk closed this as completed May 21, 2012
@invisibleroads
Copy link
Contributor Author

2012/5/21 Min RK
reply@reply.github.com:

Yup.  Not only that, this has already been opened and closed as #1450.

Hmm. It does seem like you addressed this issue already.

However,

  1. The current fix doesn't work if the IPython notebook server is
    running with HTTP but served behind an HTTPS proxy like
    node-http-proxy, which is my current setup.
  2. Running "pip install ipython==dev" pulls from SVN (
    http://ipython.scipy.org/svn/ipython/ipython/trunk ) rather than from
    GitHub, which is why I initially reported this issue.

At any rate, installing the local MathJax is working fine so thank you
for your work.

@invisibleroads
Copy link
Contributor Author

Actually, I am wrong.

Websockets only seems to work if both the IPython notebook server and node-http-proxy are both running HTTPS in the HTTPS to HTTPS configuration.

So, the current fix does solve the problem and nothing needs to be done here. Thank you for your work.

@invisibleroads
Copy link
Contributor Author

Here is one more tip for anyone else who wants to deploy IPython notebook server with WebSockets behind node-http-proxy:

Don't use connect-gzip middleware.

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

No branches or pull requests

3 participants