#36905: Remove safe parameter from JsonResponse
-------------------------------------+-------------------------------------
Reporter: Tim Schilling | Owner: Tim
Type: | Harris
Cleanup/optimization | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: fixed
Keywords: security | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"6e15ac8066312328de279e3e072667416c205bfc" 6e15ac80]:
{{{#!CommitTicketReference repository=""
revision="6e15ac8066312328de279e3e072667416c205bfc"
Fixed #36905 -- Deprecated the safe parameter of JSONResponse.
Peer frameworks have long since dropped their analogous checks for this
vulnerability that was fixed in ES5.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36905#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019e6a197388-b56659ef-4b97-462d-a0fd-726784572887-000000%40eu-central-1.amazonses.com.
