I've just created an essay *cough* I mean ticket about the way Django silently mangles POST data that is incorrectly encoded, and how this can send someone (like me) down the rabbit hole trying to debug it, thanks to "current transaction aborted" database errors.
This shouldn't normally happen, but it seems that I am unlucky and someone somewhere is able to get their browser to submit POST data that is encoded incorrectly. I don't want to repeat myself too much and end up writing another essay here, so I'll just link to the ticket. Just wanted to post this here as well because jezdez said it might be better suited to discussion on django-developers. https://code.djangoproject.com/ticket/18004 Cheers. Tai. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/ByLiu7RzHtIJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
