| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2014-09-26 | request.data attribute | Tom Christie | |
| 2014-08-19 | Code linting and added runtests.py | Tom Christie | |
| 2013-05-18 | Added proper charset support | Tom Christie | |
| 2013-05-18 | charset param gets now appended to response's Content-Type. Closes #807 | Karol Majta | |
| 2013-04-25 | Cleanup docstrings | Tom Christie | |
| 2013-02-04 | Cleanup imports | Tom Christie | |
| Mostly adding `from __future__ import unicode_literals` everywhere. | |||
| 2013-02-04 | Use request.QUERY_PARAMS internally | Tom Christie | |
| (instead of request.GET) | |||
| 2012-11-27 | Renderer negotiation: media_type specificty evaluation weak | Fabian Büchler | |
| The `DefaultContentNegotiation` handler uses For example: Google Chrome sends an Accept-header of `Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8`, when I request a *.png URL. After matching the media-types with the available renderers (in my case only a custom `PNGRenderer` with a `media_type='image/png'`), only `*/*;q=0.8` is left, which happens to have the same length as the "image/png" media-type defined by the renderer (9 characters). The specificity of the renderer's media-type over the Accept-header's one is only determined by length. Using your `_MediaType.precedence` would be preferable in my eyes. Regards, Fabian | |||
| 2012-10-29 | Fixes for urls with suffixes | Tom Christie | |
| 2012-10-17 | Negotiation API finalized. .select_renderers and .select_parsers | Tom Christie | |
| 2012-10-05 | Remove Parser.can_handle_request() | Tom Christie | |
| 2012-10-05 | Accepted media type uses most specific of client/renderer media types. | Tom Christie | |
| 2012-09-20 | Change package name: djangorestframework -> rest_framework | Tom Christie | |
