Problem solved The problem described previously only happens when the client browser has its cookies diabled and when consequently the urls are encoded.
Here is my understanding: - when using mount B/**, cocoon treats B like a "pseudo directory B/" that is not supposed to have any attached SESSIONID info or query string. - so if in A I have a link like /B;jsessionid=D5D7D8F2B9F68E514403CA0965583E43?locale=it, on mounting B, cocoon discard the ";jsessionid=D5D7D8F2B9F68E514403CA0965583E43?locale=it" part of the URL. - if I link deeper to B from A, it works fine. Example: /B/some-document;jsessionid=D5D7D8F2B9F68E514403CA0965583E43?locale=it. In this case the session id and the request parameters are rightly propagated. Oscar --- Oscar Picasso <[EMAIL PROTECTED]> wrote: > Let say I have to independent subsitemaps A and B. > > When I follow a link from A to B (or B to A) the session is lost. > > Is this behaviour expected? > > And what would be the way to propagate the session between two independent > subsitmaps? > > Oscar > > __________________________________ > Do you Yahoo!? > Get better spam protection with Yahoo! Mail. > http://antispam.yahoo.com/tools > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
