http-grammar: Attoparsec-based parsers for the RFC-2616 HTTP grammar rules.

[ apache, library, web ] [ Propose Tags ]

The purpose of this package is to provide a faithful implementation of the RFC-2616 HTTP grammar rules without concession to popular deviations that "happen in the wild". The implementation is far from complete. My development plan for this package is to add various productions from time to time as I need them in other work I'm doing. Contributions are most welcome and highly encouraged.


[Skip to Readme]

Modules

[Index]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.1.0.0
Change log ChangeLog.md
Dependencies attoparsec (>=0.12.1.6 && <0.14), base (>=4.7.0.2 && <4.10), bytestring (>=0.10.4.0 && <0.11) [details]
License Apache-2.0
Copyright 2017 Owens Murray LLC
Author Rick Owens
Maintainer rowens@owensmurray.com
Category Web
Home page https://github.com/owensmurray/http-grammar
Source repo head: git clone https://github.com/owensmurray/http-grammar.git
Uploaded by taphu at 2017-03-01T00:35:18Z
Distributions
Reverse Dependencies 1 direct, 0 indirect [details]
Downloads 905 total (3 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs uploaded by user
Build status unknown [no reports yet]

Readme for http-grammar-0.1.0.0

[back to package description]

http-grammar

http-grammar is a Haskell package that provides Attoparsec-based productions that are faithful to the HTTP grammar specified in RFC-2616.

The guiding philosophy of this package is to prioritize precision and faithfulness to RFC-2616 over all other considerations.

Contributions are welcome and encouraged! The development plan for this package is to add productions from time to time as they are needed in my other work, and to solicit the contributions of productions from you as they are needed in your other work.

I'm also willing to take requests. If there is a production you need but for whatever reason can't or don't want to implement, just submit a github issue.

Thanks!