[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk 2022-08-31T14:56:22Z 2022-08-31T14:56:22Z taca taca@pkgsrc.org 2022-08-31T14:56:22Z urn:sha1:570f6a4913849212178abcfa9713dc5a2e3927a1 2.2.0 (2022-08-02) * Tidy up specs. * Improve default constructor. * Remove code climate badge. * Merge pull request #14 from socketry/olleolleolle-add-27 * Handle q-values up to 6 decimal places. * Modernize gem. 2020-01-19T08:23:06Z taca taca@pkgsrc.org 2020-01-19T08:23:06Z urn:sha1:77963f6073380ed1f2b2af40f212c55804b4d4ca Add ruby-http-accept version 2.1.1 package. # HTTP::Accept Provides a robust set of parsers for dealing with HTTP Accept, Accept-Language, Accept-Encoding, Accept-Charset headers. ## Motivation I've been developing some tools for building RESTful endpoints and part of that involved versioning. After reviewing the options, I settled on using the Accept: application/json;version=1 method as outlined here. The version=1 part of the media-type is a parameter as defined by RFC7231 Section 3.1.1.1. After reviewing several existing different options for parsing the Accept: header, I noticed a disturbing trend: header.split(','). Because parameters may contain quoted strings which contain commas, this is clearly not an appropriate way to parse the header. I am concerned about correctness, security and performance. As such, I implemented this gem to provide a simple high level interface for both parsing and correctly interpreting these headers.