You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Oscar Picasso <os...@yahoo.com> on 2004/02/27 19:06:06 UTC
Mount and session propagation problem.
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: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Mount and session propagation problem.
Posted by Joerg Heinicke <jo...@gmx.de>.
On 27.02.2004 20:46, Oscar Picasso wrote:
> 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.
Cocoon does not discard anything. The servlet container handles this.
Just for clarification ...
> - 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.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Mount and session propagation problem.
Posted by Oscar Picasso <os...@yahoo.com>.
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 <os...@yahoo.com> 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: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org