GET /api/v2/video/58
HTTP 200 OK Vary: Accept Content-Type: text/html; charset=utf-8 Allow: GET, PUT, PATCH, HEAD, OPTIONS
{ "category": "DjangoCon 2010", "language": "English", "slug": "djangocon-2010--pony-pwning", "speakers": [], "tags": [ "djangocon", "djangocon2010", "security" ], "id": 58, "state": 1, "title": "Pony Pwning", "summary": "", "description": "Pony Pwning\n\nAdam Baldwin\n\nDjango's awesomeness unfortunately doesn't make it impenetrable. This talk\nwill cover common pitfalls of the Django developer as seen through the eyes of\na hacker or malicious user.\n\nAbstract\n\nDjango is arguably the most secure web framework. The Django team have done an\nexcellent job making secure-by-default decisions for our web applications in\nmany situations. Still, the last mile in development is where the bulk of\nsecurity vulnerabilities can be introduced and Django's powerful flexibility\nallows for plenty of rope for developers to hang themselves. Understanding the\nvulnerabilities that can be created by common mistakes or misconceptions and\noverlooked details in development will be useful for any Django user.\n\n", "quality_notes": "", "copyright_text": "Creative Commons Attribution-NonCommercial-ShareAlike 3.0", "embed": "", "thumbnail_url": "", "duration": null, "video_ogv_length": 155465560, "video_ogv_url": null, "video_ogv_download_only": false, "video_mp4_length": null, "video_mp4_url": null, "video_mp4_download_only": false, "video_webm_length": null, "video_webm_url": null, "video_webm_download_only": false, "video_flv_length": null, "video_flv_url": "", "video_flv_download_only": false, "source_url": "", "whiteboard": "", "recorded": null, "added": "2012-02-23T04:20:00", "updated": "2014-04-08T20:28:25.611" }