and
the core sitemaps completely fail to use the base-url module, which is
apparently the only one that is proxy-aware...)
That's because the core sitemaps are much older than the base-url
module.
Is there something particular I could help you with?
A test case / setup description would be great. I'll take a look
at the docs and wiki pages.
well, after 2 days of digging around, i've come to the conclusion that
lenya proxying support is broken beyond repair, at least for $area !=
live. which is ok, since we can provide our customers with sane urls
most of the time. they will just have to provide a dedicated ssl server
where lenya runs in the root context. oh well.
it's not worth trying for a quick fix. nothing short of a complete
rewrite will do.
Thanks for diving into the details. I have to admit that I'm not
familiar enough with the proxying to judge this ATM.
What do the others think?
Like you said, the live side is fine, so long as you don't try to
protect anything behind SSL. It is unfortunate that for authoring Lenya
has to run in the root context, but it is at least a solution. One could
work with the Apache config to support other items on the ssl server. I
am not familiar with the code, but I know from my experience there is a
ton of stuff that needs to be changed.
i'd say we should document proxying as currently unsupported
IMO this sends a wrong message. There are many 1.2.x sites running
behind a proxy. We should support at least a certain level of proxying
in 1.4.
From my experience, proxying the live side works just fine under HTTP.
Proxying the authoring side under SSL is limited to being the root
context on the ssl server. This is unfortunate, but it does work. We
might want to strip out the SSL checkbox option from the pages, as this
isn't going to do anything and will just be confusing.
Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
