Bas,
    Thanks. I havent checked this behavior with other browsers. I will. What
do you think is the best solution or approach to this problem?

Fernando

On Fri, Nov 27, 2009 at 7:36 AM, bgooren <b...@iswd.nl> wrote:

>
> Given your detailed explanation, I think the problem is clear: your browser
> (and thus the flash client as well) is protected so it can only use cookies
> _for the same domain_. So if you load a flash movie from .com.ar and have
> it
> connect to a .com, it will not use the cookie(s) it got from the .com.ar;
>
> So what you are seeing is expected behavior.
>
> Bas
>
> Fernando Wermus-2 wrote:
> >
> > Bas,
> >
> >       I will try to explain what it is going on with this scenario
> (anyway
> > I
> > think you understood).
> >
> > 1. an user logs in the site using .com.ar
> > 2. the user gets a flex component in the site's page. The flex component
> > is
> > compiled to point to .com services.
> > 3. the flex component asks a specific service to the back-end which
> > consults
> > if this user has a wicket session, it fails.
> >
> > The user has never change the tab which is using.
> >
> > He has a cookie because he is accessing to the site using the same tab.
> > Thus, it shouldnt have been any problem.
> >
> > On the another hand, I have set up the server with two dns manager, one
> > for
> > each domain.
> >
> > -------------------------------------------
> > |     a page (from .com.ar)      |
> > |                                          |
> > |        ------------------------ ------   |
> > |        |  a flex component |     |
> > |        |  (connects .com)  |     |
> > -------------------------------------------
> >
> > MessageBrokerServlet, flex component back end, which needs
> > wicketSessionFilter to verify user authentication.
> > WicketSessionServletFilter which "injects" the session into
> > MessageBrokerServlet.
> > WicketFilter.
> >
> > flex client   -------> MessageBrokerServlet through .com
> > the page    --------> WicketFilter through .com.ar
> >
> > I know the cookie should be the same because they are in the same tab,
> but
> > it is also truth that they connect using differents domains.
> >
> > The message log4j sends to me it is clear. It couldnt reach the session.
> >
> > Thanks anyway.
>
> --
> View this message in context:
> http://old.nabble.com/WicketSessionFilter-and-several-domains-tp26502429p26539906.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Fernando Wermus.

www.linkedin.com/in/fernandowermus

Reply via email to