Hey John !

I don't know which code exactly you are using. Try to disable the
setVersion() on the CookieSetting.

I am really looking forward having the Cookie authentication mechanism
included in Restlet because I think it is a important requirement in many
web applications. First benefit in the ability to logout.

Cheers,
Rémi

On Tue, May 5, 2009 at 17:26, John Wismar <[email protected]> wrote:

> Hey, all-
>
> I'm using Restlet 1.1.4 in my project.  I'm working on using cookies to
> create a concept of login sessions.  (Yes, I know about the philosophical
> problems - business requirements dictate this.)
>
> I've been looking at Remi Dewitte's CookieGuard implementation discussed
> on this list last December, and using that for a framework/guideline on
> how to work with cookies in Restlet.
>
> The code I have in place now seems to work fine in Firefox.  It does not
> seem to be working in IE7.  When I log all of the HTTP traffic, it seems
> that my service is sending the Set-Cookie headers in the places that I
> expect to see them, but that IE does not send the cookies back upon any
> request.
>
> I've tried different variations on how the cookies get created (e.g. with
> or without "Access Restricted" flag, using different path and timeout and
> version settings), but nothing has seemed to make a difference.  I have
> also looked at the IE security and privacy settings, but I don't see
> anything that looks relevant.
>
> I have too many variables and unknowns to know where the problem lies. Has
> anyone seen this behavior?  Is there a different way of configuring the
> cookies?  Is this a coding problem on my side, or an IE7 configuration
> issue?
>
> Thanks for any insight!
>
> --------------------------------
> John Wismar
> mailto:[email protected]
>
> ------------------------------------------------------
>
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2070293
>

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2070403

Reply via email to