Daniel Kontsek skrev: > Hello > > I have a web application with 2 views. The first view checks if the > session dictionary has a 'uid' key - if not it generates an random ID > and puts it into request.session dict. The second view reads the uid > from the session dict and creates a Project DB object with that uid. > This works fine in all browsers (FF, Safari, IE), except Opera. Looks > like Opera (Mac, 9.21.3678) doesn't accept the cookie with the session > info. although cookies are on. Any idea why? > Several possibilities come to mind:
- The cookies may be somehow violating the standard. Other browsers may be more accepting of invalid data. - When receiving a cookie received as part of a redirect, it may not be immediately sent with the new request. It is not clear whether this is allowed by the standard - which talks about cookies which the client has "stored". Opera might not have stored the cookie at that point in time. . Opera may be configured to not accept cookies, or be very strict in what it accepts. - Opera may be caching the page that is supposed to set the cookie. This would probably not be happening consistently, though. I think it would be a good idea to look at what actually goes on in the HTTP communication - perhaps logging the two HttpRequests and corresponding HttpResponses /Nis --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
