Bug 43853 - rng include resolving does not work with proxy
Summary: rng include resolving does not work with proxy
Status: NEW
Alias: None
Product: Lenya
Classification: Unclassified
Component: Bitflux Integration (show other bugs)
Version: Trunk
Hardware: Other other
: P2 major
Target Milestone: 2.0.1
Assignee: Lenya Developers
Depends on:
Reported: 2007-11-13 10:49 UTC by J
Modified: 2007-11-13 12:27 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description J 2007-11-13 10:49:52 UTC
client-side rng validation (as used by bxe) currently fails in proxied
environments, because the include hrefs are not correctly resolved.
we have a strange re-implementation of a fallback resolver in
src/webapp/lenya/xslt/resources/translate-rng-includes.xsl that just knows
contexts, not proxies. it really needs to go away rsn.
for now, i'm removing the context prefix and apply a proxy transform later on
(which means the proxy transformer has to be re-configured to include

we should really be more careful with using cocoon-internal protocols in files
that will potentially be parsed on clients (currently, these are rngs and xslt -
mozEdit anyone?). imnsho, they should not be served from files at all but via
the module sitemaps, with proper proxy transforms applied.
Comment 1 J 2007-11-13 12:27:50 UTC
fixed with a workaround as of r594629
i'm moving this to 2.0.1 to remind us to eliminate the transform...