convore.json/groups/django-community/csrf-verification-fails-on-one-computer/messages.json

[{"user_id": 2458, "stars": [], "topic_id": 7887, "date_created": 1298319264.8973179, "message": "Any ideas on why this might be happening?", "group_id": 81, "id": 166603}, {"user_id": 2458, "stars": [], "topic_id": 7887, "date_created": 1298319248.3089409, "message": "On my Django web app, CSRF verification fails on one of my computers, giving me a 403 error and the reason \"No CSRF or session cookie.\" I'm just trying to login using the standard contrib.auth login. The CSRF tag is in place and it's actually setting the cookie. I've tried it on multiple browsers with no luck. I'm able to login just fine on my other computer and my phone.", "group_id": 81, "id": 166583}, {"user_id": 13232, "stars": [], "topic_id": 7887, "date_created": 1298319886.1078179, "message": "Nm just saw you said the cookie is being set in your browser on that computer.", "group_id": 81, "id": 167181}, {"user_id": 13232, "stars": [], "topic_id": 7887, "date_created": 1298319865.8683441, "message": "Any kind of virus/malware blockers or personal firewalls that might mangle cookies on that computer?", "group_id": 81, "id": 167163}, {"user_id": 13232, "stars": [], "topic_id": 7887, "date_created": 1298320332.276227, "message": "Presuming you can reproduce locally, you could go petter logger statements all around your local copy of django/middleware/csrf and see if you can run down where its failing ;)", "group_id": 81, "id": 167482}, {"user_id": 13232, "stars": [], "topic_id": 7887, "date_created": 1298320332.663614, "message": "but", "group_id": 81, "id": 167483}, {"user_id": 13232, "stars": [], "topic_id": 7887, "date_created": 1298319972.80954, "message": "I also know a lot of crypto stuff depends on timestamps being in sync (not sure about the CSRF stuff).  Is your time/date set properly on the failing computer?", "group_id": 81, "id": 167202}, {"user_id": 13232, "stars": [], "topic_id": 7887, "date_created": 1298320360.4998529, "message": "and it looks like (erroneously?) here https://github.com/jacobian/django/blob/master/django/middleware/csrf.py#L176", "group_id": 81, "id": 167516}, {"user_id": 13232, "stars": [], "topic_id": 7887, "date_created": 1298320456.2843931, "message": "Doesn't really explain why one computer would error out while another would.", "group_id": 81, "id": 167603}, {"user_id": 2458, "stars": [], "topic_id": 7887, "date_created": 1298320011.0307491, "message": "I even cleared the cookie to ensure a current one was being set, and it was.", "group_id": 81, "id": 167236}, {"user_id": 2458, "stars": [], "topic_id": 7887, "date_created": 1298320059.1722431, "message": "Time / date matches up perfectly with other computer", "group_id": 81, "id": 167276}, {"user_id": 13232, "stars": [], "topic_id": 7887, "date_created": 1298320338.8702359, "message": "It looks like that error is thrown here: https://github.com/jacobian/django/blob/master/django/middleware/csrf.py#L197", "group_id": 81, "id": 167491}, {"user_id": 2458, "stars": [], "topic_id": 7887, "date_created": 1298320669.053196, "message": "I'll try setting up locally on the failing computer and see if I can glean any info from Django.", "group_id": 81, "id": 167781}, {"user_id": 8364, "stars": [], "topic_id": 7887, "date_created": 1298329671.6566, "message": "Yeah, there is an error in that logging call (just fixed it in trunk), so that the error message *logged* is incorrect. But the error message that is returned to the user is correct.", "group_id": 81, "id": 175258}, {"user_id": 8364, "stars": [{"date_created": 1298360166.3587229, "user_id": 214}], "topic_id": 7887, "date_created": 1298329741.325237, "message": "BTW, you are using jacob's fork of Django, which is months out of date and has security vulnerabilities. You should be using a standard release, or django trunk https://github.com/django/django", "group_id": 81, "id": 175267}]