W3C home > Mailing lists > Public > www-jigsaw@w3.org > November to December 1998

Re: Cookie handling in JIgsaw.

From: Benoit Mahe <Benoit.Mahe@sophia.inria.fr>
Date: Mon, 16 Nov 1998 09:42:39 +0100
Message-Id: <199811160842.JAA18389@ender.inria.fr>
To: Rajesh Joshi <rjoshi@arsin.com>
cc: "'www-jigsaw@w3.org'" <www-jigsaw@w3.org>
Rajesh Joshi writes:

> Hi!
> 
> The configuration is something like this : Client -> LoginServlet -> Servlet2
> .
> LoginServlet will verify the login information & set a cookie. Do I need to w
> rite the 
> information back to the client, & then redirect the client to Servlet2 so as 
> to make the cookie information available to servlet2?

 Yes, I think it's a solution, In order to make the cookie 
 information available to Servlet2, you need to specify the 
 cookie-path to "/" or something common to the LoginServlet URL and 
 the Serlvet2 URL. If you don't specify the cookie path, the cookie 
 will be sent on all URL of you server (that could be acceptable).
 
> Or, is it ok if I forward the HtttpServletRequest & HttpServletResponse to se
> rvlet2 without sending the information back to client?

 You mean by using the getServlet(...) method? well, why not. With 
 this solution your configuration will works with browser refusing 
 cookies and this should be faster.

 So, the best thing to do is to try, and then choose the better 
 solution.

 Regards, Benoit.


- Benoît Mahé -------------------------------------------------------
                      World Wide Web Consortium (W3C)
                    Architecture domain - Jigsaw Team           

  http://www.w3.org/People/Mahe - bmahe@w3.org - +33.4.92.38.79.89 
---------------------------------------------------------------------
Received on Monday, 16 November 1998 03:42:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:28 GMT