Nikolaus Schlemm wrote: >> I've heard that the problem might be related to md5 hashing (someone >> just recently posted it here in the groups with the same error >> message). I looked at the django code and that where that error message >> is thrown and it seemed to confirm that, but I don't know why this >> happens. > simply try generating the reference hashes provided at the end of the md5 > rfc[1] within a django-view - if they are not calculated correctly, you might > want to switch from md5 to sha for a quick workaround and possibly follow the > thread on the modpy mailinglist[2]. > > another solution might be something along the lines of the patch I posted > earlier[3] - but of course, I don't know whether or when this will make it in > into django ;) > > [1] http://www.ietf.org/rfc/rfc1321.txt > [2] http://modpython.org/pipermail/mod_python/2006-June/021482.html > [3] > http://groups.google.com/group/django-users/browse_thread/thread/eeb44c894342d6f7/4b951b6d3a8644dd
Hmm, I don't want to modify the framework code and start creating this sort of workarounds since I use django-trunk... I guess I'll have to wait until this problem is resolved, though I thought Django was for developers with deadlines :) Well, this makes me a little cautious in using the framework for my web development. Sad, 'cause I liked it. But I'll dig for more info and try to find a solution --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
