Richard Frovarp wrote:
So my question for you is this: Is it just cocoon:/ or does it include cocoon:// as well? The code in usecases.js matches cocoon:/ but the subsequent substring will leave the trailing / from cocoon://
iirc, the flow code only deals with a protocol-less string "FOO/BAR/BAZ" that is then fed to the flow sitemap and interpreted as if you had requested "cocoon:/FOO/BAR/BAZ" from the context of that flow sitemap. the leading slash is left intact afaik. does that answer your question? if not, i'd need to dig into the flow code again...
-- Jörn Nettingsmeier "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
