1. 27 Nov, 2012 1 commit
    • Renderer negotiation: media_type specificty evaluation weak · 731443b7
      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
      Fabian Büchler committed
  2. 23 Nov, 2012 4 commits
  3. 22 Nov, 2012 10 commits
  4. 21 Nov, 2012 13 commits
  5. 20 Nov, 2012 12 commits