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 --- Paul McMahan <[EMAIL PROTECTED]> wrote: > On 10/3/06, sreepriya ramakrishnan > <[EMAIL PROTECTED]> wrote: > > Geronimo V 1.0 . Is there something else I need to > do? > > I tested in the tomcat version of geronimo-1.0 and > it also works > there. Just to make sure that we're on the same > page here, you're > aware that setting the cookie in the response > doesn't make it > immediately available in the request object, right? > The cookie is not > available in the request until the client receives > it from the server > (via the response object) and then resends it in the > subsequent > request. i.e. it takes a minimum of two requests to > see the cookie. > > Hope this helps, > Paul > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
