0.02
Low commit activity in last 3 years
No release in over a year
HTTP ContentType header parser
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 2.0

Runtime

~> 2.0
 Project Readme

ContentType

Last Release MIT License CI Status

RFC-compliant HTTP Content-Type parser.

Warning
I’ve started this project simply to play with parslet. It’s fully functional, but because of using parslet under the hood, it works less efficient than it could.

Installation

Add this line to your application’s Gemfile:

gem "content-type"

And then execute:

$ bundle

Or install it yourself as:

$ gem install content-type

Usage

content_type = ContentType.parse "application/JSON; charset=utf-8; foo=bar"
content_type.mime_type              # => "application/json"
content_type.type                   # => "application"
content_type.subtype                # => "json"
content_type.charset                # => "utf-8"
content_type.parameters["charset"]  # => "utf-8"
content_type.parameters["foo"]      # => "bar"

Supported Ruby Versions

This library aims to support and is tested against the following Ruby versions:

  • Ruby 2.6

  • Ruby 2.7

  • Ruby 3.0

  • Ruby 3.1

If something doesn’t work on one of these versions, it’s a bug.

This library may inadvertently work (or seem to work) on other Ruby versions, however support will only be provided for the versions listed above.

If you would like this library to support another Ruby version or implementation, you may volunteer to be a maintainer. Being a maintainer entails making sure all tests run and pass on that implementation. When something breaks on your implementation, you will be responsible for providing patches in a timely fashion. If critical issues for a particular implementation exist at the time of a major release, support for that Ruby version may be dropped.

Contributing

  1. Fork it ( http://github.com/httprb/content-type/fork )

  2. Create your feature branch (git checkout -b my-new-feature)

  3. Commit your changes (git commit -am 'Add some feature')

  4. Push to the branch (git push origin my-new-feature)

  5. Create new Pull Request

Copyright © 2015-2022 Alexey Zapparov. See LICENSE.txt for further details.