geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan" <>
Subject Re: Geronimo and Cookies-code snippet
Date Wed, 04 Oct 2006 13:06:49 GMT
I can think of two possibilities.  The first (more likely) is that you
need to explicitly set the cookie's domain.  The second is that for
some reason the container isn't allowing a cookie to be added during
filter processing.  In any case I recommend turning on cookie
prompting in your web browser to see if a cookie is actually sent and
if so what it looks like.  Since you're seeing the jsession cookie I
doubt cookies are getting blocked altogether.


On 10/3/06, sreepriya ramakrishnan <> wrote:
> Hi Paul,
> This is waht I am trying to achieve.
> I have a servlet Filter and  in the filter I try to
> read the Authorization header in the request headers .
> If I dont find it I send a response with
> www-authenticate so that it pops up a window to enter
> the username/password .Now at the same time I set a
> cookie. Now after this when I receive the username/pwd
> I check the cookie. Its then that I cant see the
> cookie.
> when we send back a www-authenticate response header
> message to teh browser and set the client , why cant I
> see the cookie I added?
> Thanks for your help.
> -Priya

View raw message