camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Servet Componnet HttpSession
Date Sat, 22 Jun 2013 17:05:29 GMT
On Wed, Jun 19, 2013 at 12:11 AM, ramrubio <ramrubio@yahoo.com> wrote:
> It looks like Camel caches the client connection as long as URL is exactly
> the same.
>
> This causes multiple requests by different browser clients to use same
> session id.
>
> Is this expected behavior?  It does not seem correct to me for two different
> clients to have the same session id on server simply because they use the
> same URL.
>

I would assume that the cookies for the session id's from the "real
target" needs to be propagated,
and then on the Camel side, there shouldn't really be any session in
use, as its just a proxy.

So can you see if the session id cookies returned from the "real
target" gets returned to Camel, and that Camel sends those back to the
client.



>
> Use case is that Camel is acting as a proxy with a slip configuration that
> routes the request to a servlet component.
>
> /Ramon
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Servet-Componnet-HttpSession-tp5734314p5734320.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



--
Claus Ibsen
-----------------
www.camelone.org: The open source integration conference.

Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
View raw message