This does not work cleanly with Sage because the css and js refer to each other and the paths aren't just simple relative paths. You need to run mod_proxy_html and rewrite css, js and some of the html pages on the fly. At least that was my experience when trying to have ssl in front. I never tried using it for straight unencrypted reverse proxy, which in my experience is a little easier.
On Feb 11, 4:04 pm, Michael Orlitzky <mich...@orlitzky.com> wrote: > On 02/11/2012 04:37 PM, Jonathan wrote: > > > Making Sage work well with a proxy is no simple matter. I run a > > number of web sites where we proxy through Apache to get SSL and > > generally more robust web services facing the outside world. For this > > to work well your backend needs to be proxy aware, or the proxy has to > > know a lot about the backend and do deep rewriting of js and css. The > > backend that is probably most applicable to Sage is the Plone CMS, > > which is written in python and uses a package called > > VirtualHostMonster to handle getting proper URLs in things that go > > through a proxy. This does work well, but might be difficult to get > > working in the Sage notebook. There is also a significant learning > > curve associated with setting up these proxys even with > > VirtualHostMonster. > > I was being loose with the terminology; the type of proxy I was > referring to is called a reverse proxy. > > You can do fancier stuff (like load balancing) with them, but > essentially, *this* reverse proxy would just send data back and forth > unaltered between the sage notebook and a web browser. > > Forward proxies are another beast. -- 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
