Jörn Nettingsmeier wrote:
Thorsten Scherler wrote:
On Tue, 2007-05-15 at 13:12 +0200, Andreas Hartmann wrote:
What does that mean about the proxying issue?
Do we already have a decent documentation what can be done and how?
Actually the recent threads make a nice document but someone needs to
hack it together (be it in the wiki or preferable in our documentation).
As I understood the problematic there is no easy fix for this issue
meaning we should not risk anything and state clearly about the limited
support as recommend by Richard and others.
proxy support in lenya is broken and not fixable for 1.4.0.
it *is* possible to use external means (mod_rewite + mod_proxy) to at
least pipe apache requests through to a jetty on localhost, but the
following is not possible (or at least i haven't been able to do it):
* present the authoring interface via an ssl-enabled vhost without
using the root context (i.e. no other services can easily be used on
that host)
* hide the lenya-specific <pubid>/<area>/ path components of the URLs.
even when using the authoring interface in the root context of an ssl
proxy, some things are subtly broken (user management etc.). i could
not reproduce these issues on a default installation yet, but my
custom publications show them...
I agree with this. I have found a few mixed content problems that
probably should be fixed. My technology release office is still dragging
their feet on my CLA.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
