httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <wr...@rowe-clan.net>
Subject [RE-VOTE] adoption of mod_firehose MODULE
Date Thu, 01 Mar 2012 18:11:08 GMT
Let's simply reset this whole mess.

A proposal to adopt mod_firehose is attached.

  [ ] Option 1: adopt as trunk module
  [ ] Option 2: adopt only as subproject
  [ ] Option 3: do not adopt




[Prior to this vote, option 2 had previously passed with minfrin, issac,
sctemme, jim in support.  Subsequently, wrowe endorsed option 2, while
minfrin, jim introduced option 1.  Please vote.]

On 12/13/2011 9:19 AM, Graham Leggett wrote:
> Hi all,
> 
> I have concluded negotiation with the BBC to open source some httpd modules that I wrote
under the AL, and the BBC have very kindly agreed to donate the code to the ASF[1], which
I believe would fit well as subprojects of httpd, and would like to know whether httpd would
accept these.
> 
> To be clear, this isn't a "code dump", my intention is to continue to develop and support
this moving forward, and hopefully expand the community around them.
> 
> - mod_firehose: "tcpdump for httpd"
> 
> Based originally on mod_dumpio.c, mod_firehose is an httpd filter that writes the contents
of a request and/or a response to a file or pipe in such a way that the requests can be reconstructed
later using a second dedicated tool called "firehose".
> 
> It was initially developed to help debug restful services that were secured with client
certificates and therefore opaque to other tools like tcpdump or tcpflow, but was then subsequently
used to record "dirty traffic" for subsequent replay for the purposes of testing.
> 
> The module and the corresponding firehose demultiplexer was used to uncover some of the
more tricky bugs in mod_cache, as well as protocol inconsistencies in backend services, and
would prove very useful to anyone deploying restful services. We have also intended it to
be used to create a "dark live" environment, where live traffic can be split off and diverted
to a staging environment to test whether a software update works correctly.
> 
> The code is currently packaged as an RPM, wrapped in autotools, and a snapshot is available
here:
> 
> http://people.apache.org/~minfrin/bbc-donated/mod_firehose/
> http://people.apache.org/~minfrin/bbc-donated/firehose/
> 
> The corresponding README documenting in more detail is here:
> 
> http://people.apache.org/~minfrin/bbc-donated/mod_firehose/README
> 
> The code itself is here:
> 
> http://people.apache.org/~minfrin/bbc-donated/mod_firehose/mod_firehose.c
> http://people.apache.org/~minfrin/bbc-donated/firehose/firehose.c
> 
> Obviously the expectation is for the documentation to be completed and fleshed out.
> 
> [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=52322
> 
> Regards,
> Graham
> --
> 
> 


Mime
View raw message