Joern Nettingsmeier wrote:
Richard Frovarp wrote:
Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
[...]
i think this is a really fundamental issue with lenya, and fixing it
requires very intrusive changes (see my other post)... the way i
see it,
we should do something half-assed and non-intrusive for the RC and aim
for a clean solution by the time of the hackathon.
OK, that sounds reasonable. What changes are necessary to make it
(kind-of) work for the moment? Do you have the time to take care
of it? I don't have a proxied setup running ATM.
-- Andreas
It does kind of work at the moment. The only caveat is if you have
the editing under SSL you have to base it at the root level
https://example.com/default/authoring
which is a bummer, because, as remarked in another thread, you cannot
use name-based virtual hosting together with ssl.
I am not sure I understand correctly what you mean.
I think one can setup a name based vhost for 80 and another name based
vhost for 443 (with the same name but different port) and then point
from these two vhosts to the same Tomcat either pointing
80 -> 8080 and 443 -> 8080
or
80 -> 8080 and 443 ->8443
for instance. Or do I misunderstand something?
Cheers
Michael
which means the lenya deployment will interfere with existing stuff....
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
