If the input is formatted using a "standard" encoding (eg, multipart/form-data or application/x-www-form-urlencoded) which it sounds like you are, you might save yourself by using mod_apreq to parse the input. In Apache2, it's implemented as an input filter, so content can still be seen by filters after it. It's homepage is http://httpd.apache.org/apreq/
Even if it's not what you need (and to me, at least, it sounds like it is), at the very least you'll probably get good sample code for developing input filters. Issac Steve Kemp wrote: > On Fri, Oct 13, 2006 at 08:38:44PM +0100, Nick Kew wrote: > >>> Is there a simple way for my module to read/process the incoming >>> POST data, whilst still allowing the data to be passed on to >>> mod_cgi, etc? >> That's what input filters are for. How best to do it depends on the >> nature and size of the requests you're processing. > > Thanks. > > I'm currently trying to find some decent sample code... The requests > I expect to be parsing are "small" in the sense that they will > typically have less than ten key=value elements. > > > Steve
