On Jun 4, 10:37 pm, Chris Seberino <[email protected]> wrote: > Notebook documentation mentions a boolean switch called "secure" for > SSL. > > When I try to turn it on my notebook server, I get an error about a > domain Sage needs. > > How exactly does this switch work and how does Sage want to do SSL?
If you turn it on for the first time, sage make its own SSL certificate. The domain name on which the notebook is served (the domain name that the client browser needs to connect to!) is part of that certificate, so that is why Sage asks for the domain. You then just connect to https://... If you already have a certificate that you want Sage to use, hopefully the manual will tell you how to point Sage to the pre-existing cert. > In my limited experience, when I want SSL protection, I set up an > Apache proxy (mod_proxy) in front of my app running on localhost. > Obviously, if Sage's SSL worked that way then Sage would need more > info that just toggling a boolean called "secure" so it must be doing > things differently. That is probably possible too, but then you should let Apache take care of the SSL and run the notebook with secure=false behind it. The proxying for connections that are already SSL end-to-end must be very limited, since at that point your Apache proxy is basically a man- in-the-middle. -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
