Upstream software project

ghc-http-media

Processing HTTP Content-Type and Accept headers

About ghc-http-media

Processing HTTP Content-Type and Accept headers

This project links 18 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 4 package records; Fedora 44: 4 package records; openSUSE Leap 15.6: 2 package records; openSUSE Leap 16.0: 4 package records; openSUSE Tumbleweed: 4 package records. Catalog coverage diagram, not an application screenshot.ghc-http-media: recorded package coverageFedora 434 recordsFedora 444 recordsopenSUSE Leap 15.62 recordsopenSUSE Leap 16.04 recordsopenSUSE Tumbleweed4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ghc-http-media
Publisher
Not authoritatively mapped
Native package records
18
Operating systems
fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
MIT
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This library is intended to be a comprehensive solution to parsing and selecting quality-indexed values in HTTP headers. It is capable of parsing both media types and language parameters from the Accept and Content header families, and can be extended to match against other accept headers as well. Selecting the appropriate header value is achieved by comparing a list of server options against the quality-indexed values supplied by the client. In the following example, the Accept header is parsed and then matched against a list of server options to serve the appropriate media using 'mapAcceptMedia': > getHeader >>= maybe send406Error sendResourceWith . mapAcceptMedia > [ ("text/html", asHtml) > , ("application/json", asJson) > ] Similarly, the Content-Type header can be used to produce a parser for request bodies based on the given content type with 'mapContentMedia': > getContentType >>= maybe send415Error readRequestBodyWith . mapContentMedia > [ ("application/json", parseJson) > , ("text/plain", parseText) > ] The API is agnostic to your choice of server.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package ghc-http-media

    43 (Fedora 43) (Unspecified): Processing HTTP Content-Type and Accept headers

    0.8.1.1-6.fc43: aarch64 x86_64

    Source: ghc-http-media

  2. Package ghc-http-media-devel

    43 (Fedora 43) (Unspecified): Haskell http-media library development files

    0.8.1.1-6.fc43: aarch64 x86_64

    Source: ghc-http-media

  3. Package ghc-http-media-doc

    43 (Fedora 43) (Unspecified): Haskell http-media library documentation

    0.8.1.1-6.fc43: noarch

    Source: ghc-http-media

  4. Package ghc-http-media-prof

    43 (Fedora 43) (Unspecified): Haskell http-media profiling library

    0.8.1.1-6.fc43: aarch64 x86_64

    Source: ghc-http-media

Fedora 44

  1. Package ghc-http-media

    44 (Fedora 44) (Unspecified): Processing HTTP Content-Type and Accept headers

    0.8.1.1-8.fc44: aarch64 x86_64

    Source: ghc-http-media

  2. Package ghc-http-media-devel

    44 (Fedora 44) (Unspecified): Haskell http-media library development files

    0.8.1.1-8.fc44: aarch64 x86_64

    Source: ghc-http-media

  3. Package ghc-http-media-doc

    44 (Fedora 44) (Unspecified): Haskell http-media library documentation

    0.8.1.1-8.fc44: noarch

    Source: ghc-http-media

  4. Package ghc-http-media-prof

    44 (Fedora 44) (Unspecified): Haskell http-media profiling library

    0.8.1.1-8.fc44: aarch64 x86_64

    Source: ghc-http-media

openSUSE Leap 15.6

  1. Package ghc-http-media

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Processing HTTP Content-Type and Accept headers

    0.8.1.1-150500.11.3.2: aarch64 ppc64le s390x x86_64

    Source: ghc-http-media

  2. Package ghc-http-media-devel

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Haskell http-media library development files

    0.8.1.1-150500.11.3.2: aarch64 ppc64le s390x x86_64

    Source: ghc-http-media

openSUSE Leap 16.0

  1. Package ghc-http-media

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Processing HTTP Content-Type and Accept headers

    0.8.1.1-bp160.1.10: aarch64 ppc64le x86_64

    Source: ghc-http-media

  2. Package ghc-http-media-devel

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Haskell http-media library development files

    0.8.1.1-bp160.1.10: aarch64 ppc64le x86_64

    Source: ghc-http-media

  3. Package ghc-http-media-doc

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Haskell http-media library documentation

    0.8.1.1-bp160.1.10: noarch

    Source: ghc-http-media

  4. Package ghc-http-media-prof

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): Haskell http-media profiling library

    0.8.1.1-bp160.1.10: aarch64 ppc64le x86_64

    Source: ghc-http-media

openSUSE Tumbleweed

  1. Package ghc-http-media

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Processing HTTP Content-Type and Accept headers

    0.8.1.1-3.15: x86_64

    Source: ghc-http-media

  2. Package ghc-http-media-devel

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Haskell http-media library development files

    0.8.1.1-3.15: x86_64

    Source: ghc-http-media

  3. Package ghc-http-media-doc

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Haskell http-media library documentation

    0.8.1.1-3.15: noarch

    Source: ghc-http-media

  4. Package ghc-http-media-prof

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Haskell http-media profiling library

    0.8.1.1-3.15: x86_64

    Source: ghc-http-media

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.