I found my notes on proxying Sage. If you set up Sage as the root of your server (ie proxy "/" to Sage) most of the paths are correct (not all, but most). If you have a server like mine that has legacy pages at "/" you have to proxy something else to Sage (for example "/ Sage"). Anyway, this does not work because paths in Sage to icons, css and js were (and I believe still are) all relative to "/". This means almost nothing works without deep rewriting. Relative paths are much easier to proxy, but are more of a security risk. I think the ideal would be to make Sage proxy aware using VirtualHostMonster. Then all pages would be served with all links being complete well formed http or https addresses. I'm still not sure about proxying applets, but think that could be worked out.
In the meantime as the SSL directly from Sage works, I think people can use that and just have to link to OpenSSL as a system service. Jonathan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
