#34709: charset should be ignored for the application/x-www-form-urlencoded content type. -------------------------------------+------------------------------------- Reporter: Mariusz Felisiak | Owner: Mariusz | Felisiak Type: Bug | Status: assigned Component: HTTP handling | Version: 4.2 Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak): Replying to [comment:10 Claude Paroz]: > Indeed, by default `parse_sql` is calling `decode()` with `errors='replace'`, which will produce � (U+FFFD, the official REPLACEMENT CHARACTER) for invalid UTF-8 sequences. I'm still not convinced it will be a real improvement over the current situation… We could raise 400 instead of silently ignoring a custom charset. -- Ticket URL: <https://code.djangoproject.com/ticket/34709#comment:11> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/0107018964e79437-d7c51f4d-66af-44a4-9fcd-e06861139cfa-000000%40eu-central-1.amazonses.com.