diff options
| author | Tom Christie | 2013-05-20 21:18:17 +0100 | 
|---|---|---|
| committer | Tom Christie | 2013-05-20 21:18:17 +0100 | 
| commit | aef7ac72cc49db0745edcfe083220570abbbe3a7 (patch) | |
| tree | e20b06bad897714f7756f0fd468485d0652c3835 /docs/api-guide/renderers.md | |
| parent | f19e0d544fdcd318c2bde2057d91777beda78915 (diff) | |
| download | django-rest-framework-aef7ac72cc49db0745edcfe083220570abbbe3a7.tar.bz2 | |
content type may be set explicitly on the response
Diffstat (limited to 'docs/api-guide/renderers.md')
| -rw-r--r-- | docs/api-guide/renderers.md | 9 | 
1 files changed, 9 insertions, 0 deletions
| diff --git a/docs/api-guide/renderers.md b/docs/api-guide/renderers.md index fb5a5518..63641d23 100644 --- a/docs/api-guide/renderers.md +++ b/docs/api-guide/renderers.md @@ -300,6 +300,15 @@ For example:          data = serializer.data          return Response(data) +## Underspecifying the media type + +In some cases you might want a renderer to serve a range of media types. +In this case you can underspecify the media types it should respond to, by using a `media_type` value such as `image/*`, or `*/*`. + +If you underspecify the renderer's media type, you should make sure to specify the media type explictly when you return the response, using the `content_type` attribute.  For example: + +    return Response(data, content_type='image/png') +  ## Designing your media types  For the purposes of many Web APIs, simple `JSON` responses with hyperlinked relations may be sufficient.  If you want to fully embrace RESTful design and [HATEOAS] you'll need to consider the design and usage of your media types in more detail. | 
