I guess it depends on what you mean by "client related". If Safari is the only browser exhibiting this behavior I think it's safe to assume that the web server is doing OK. This assumption is only strengthened by the fact that only a change of the name the server is accessed through changes the behavior of the browser.
Your guess about DNS vs. hosts-file seems reasonable to me, and the reason Safari is different could be because it uses a different resolver library. I guess it interprets the cookie as a third-party cookie when accessed through a name defined in the hosts file or something like that. It's not really surprising that it works with other browsers, since it really should work. Obviously, Safari is misbehaving here, so I still don't really see how you can say it isn't client related (although it could possibly be fixed by using a proper DNS entry instead of using the hosts file). /Emil 2008/6/25 Pieter Claerhout <[EMAIL PROTECTED]>: > > I think I got closer to the source of the problem. > > First of all, it's not client related. > > What I tried was the following: > - Removed all the virtual hosting stuff and defined the complete web > server to serve the django app. > - Included django_test.local pointing to 127.0.0.1 in the hosts file. > > If I then browse to http://localhost/admin/ using Safari, I can > properly log in. However, if I try to browse to > http://django_test.local/admin/, I get the cookie error problem again. > > So, I guess it must have something to do with the fact that define the > hostname using the hosts file on Mac OS X instead of doing it via the > DNS server. > > What's even more strange is that Safari is the only browser having > problems with this... > > Cheers, > > > pieter > > 2008/6/24 Emil Styrke <[EMAIL PROTECTED]>: > > It certainly looks to me like it is a client and not a server problem. > Have > > you tried running the development server on the mac and accessing it with > > that exact same install of Safari? Have you tried accessing the site > from a > > different mac with safari? > > > > As a next step in tracing the error I'd install wireshark or a similar > tool > > and look at exactly what HTTP traffic passes between Safari and Django - > > this would probably reveal for certain whether it's the server or the > client > > messing up. > > > > Hope that helps, > > /Emil > > > > 2008/6/24 Pieter Claerhout <[EMAIL PROTECTED]>: > >> > >> Anyone an idea? I've also disabled PHP on the server as that might > >> cause some troubles, but that didn't make a difference. > >> > >> pieter > >> > >> 2008/6/23 Pieter Claerhout <[EMAIL PROTECTED]>: > >> > Absolutely, that was the first thing I checked ;-) > >> > > >> > pieter > >> > > >> > 2008/6/23 TiNo <[EMAIL PROTECTED]>: > >> >> > >> >> > >> >>> Looks like your browser isn't configured to accept cookies. Please > >> >>> enable cookies, reload this page, and try again. > >> >>> > >> >> > >> >> Well, are cookies enabled in Safari? (Prefs > Security > accept > >> >> cookies)... > >> >> >> > >> >> > >> >> > >> > > >> > > >> > > >> > -- > >> > pieter claerhout . [EMAIL PROTECTED] . http://www.yellowduck.be/ > >> > > >> > >> > >> > >> -- > >> pieter claerhout . [EMAIL PROTECTED] . http://www.yellowduck.be/ > >> > >> > > > > > > > > > > > > > -- > pieter claerhout . [EMAIL PROTECTED] . http://www.yellowduck.be/ > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
