kcar features an HTTP parser that will convert a bytestream into a 3-element array suitable for use as a Rack response. It is IO interface agnostic, so it may be used with HTTP streams over Unix domain sockets, regular files, FIFOs, StringIOs as well as traditional TCP sockets.
RFC2616-compliant Ragel+C parser adapted from Mongrel
decodes chunked response bodies with an optional pass-through mode (to avoid rechunking with Rack::Chunked)
handles odd things like trailers and multiline headers
streaming interface for response bodies allows for incremental processing of arbitrarily large responses.
supported under Ruby 1.9 and later.
kcar is only lightly tested and is not yet aware of all quirks found in all real (possibly broken) web servers.
If you're using a packaged Ruby distribution, make sure you have a C compiler and the matching Ruby development libraries and headers.
If you use RubyGems:
gem install kcar
Otherwise grab the latest tarball from:
Unpack it, and run "ruby setup.rb"
While you can use the
Kcar::Parser directly, you'll usually want the higher-level interface of Kcar::Response:
require 'rack' # for Rack::Utils::HeaderHash, which is optional require 'socket' # for TCPSocket require 'kcar' sock = TCPSocket.new('example.com', 80) sock.write("GET / HTTP/1.0\r\n\r\n") # instead of a Rack::Utils::HeaderHash object below, you can also # pass a regular Hash or Array object. response = Kcar::Response.new(sock, Rack::Utils::HeaderHash.new) status, headers, body = response.rack
You can now do further processing on the status, headers, or iterate through the body with body.each.
You can get the latest source via git from the following locations:
https://yhbt.net/kcar.git https://repo.or.cz/kcar.git (mirror)
You may browse the code from the web and download the latest snapshot tarballs here:
Inline patches (from "git format-patch") to the mailing list are preferred because they allow code review and comments in the reply to the patch.
We will adhere to mostly the same conventions for patch submissions as git itself. See the Documentation/SubmittingPatches document distributed with git on on patch submission guidelines to follow. Just don't email the git mailing list or maintainer with kcar patches.
All feedback (bug reports, user/development discussion, patches, pull requests) go to the public mailing list: firstname.lastname@example.org All mail is archived publically at: yhbt.net/kcar-public/ and nntp://news.public-inbox.org/inbox.comp.lang.ruby.kcar
Anonymous posts will always be welcome.
No subscription is necessary to post to the mailing list; but you may subscribe by sending a plain-text mail to:
Keep in mind we suck at delivering email, so using NNTP or Atom feeds might be a better bet. Please remember to Cc: all recipients as subscription is optional.
mail archives: https://yhbt.net/kcar-public/ http://ou63pmih66umazou.onion/kcar-public/ nntp://news.public-inbox.org/inbox.comp.lang.ruby.kcar nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.kcar public: email@example.com source code: git clone https://yhbt.net/kcar.git torsocks git clone http://ou63pmih66umazou.onion/kcar.git