Jörn Nettingsmeier wrote:
my feelings about that are mixed. on the one hand i'm pretty frustrated
that it does not work as is, otoh a clean solution looks like a major
rewrite, and i'd hate to see the RC delayed again...
i wonder: should we declare that feature as broken, remove the ssl
checkboxes for now, ignore the proxy settings and provide documentation
on how to hack in a global link rewriter xslt for people who need
proxying now?
i'm working on such a beast atm, and while it cannot offer granular ssl
like the checkboxes would, it will hopefully work and be self-contained
so that it can easily be thrown away when we have a better solution.
the basic functionality is there. all you need to do is add
<map:transform src="fallback://lenya/xslt/util/proxy-hack.xsl">
<map:parameter name="proxy" value="https://stackingdwarves.net/cms/"/>
</map:transform>
to your publication's sitemap.xmap.
but there is a showstopper: css links need to be rewritten as well.
which means that this stupid hack gets spread all over the place. bad.
if ssl proxying is just needed for authoring, it's not too bad. i'd
rather we live with ugly-looking menus than muck up our code in several
places.
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.
wdyt?
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
Kurt is up in Heaven now.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
