Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type;
  b=zLSTrBKKWh45Oe11Y/ovJfv/5XWXCBG+Vc52kGuTmVorSQzF164EP388ob4tXbXxBXFaBn0gkG1jPdBHM58JcblnhIBhVP0hXYIIwzC/rawX/3DHMHqfrnLFtq/PrKxHPDZYHxJQySS4GsRBMIFRbhN/HxCdZQZ0YtMIvOurCFw=;
Message-ID: <892935.30955.qm@web31807.mail.mud.yahoo.com>
Date: Sat, 21 Mar 2009 20:22:52 -0700 (PDT)
From: Erik Westland <erikwestland@yahoo.com>
Subject: Input filter to process POST variables (e.g. mod_form)
To: modules-dev@httpd.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


I am writing an output filter that needs to record request (headers and POST/GET vars) and response data (status and content-length). I was planning to write an input filter to capture/relay the POST/GET data (via "r->notes") to an output filter for processing.

It seems that "mod_form" (see: http://apache.webthing.com/mod_form/) does the parameter processing, but comes with the following ominous caveat:
"mod_form works with GET but is largely untested under POST, and appears to have problems with POST and HTTP Keepalive. That will be fixed, but it's not currently a priority."

Q: Does anyone know if this is safe to use? Their support page lists mod_form as: "unlikely to represent value to you."

Q: Is there another alternative to writing my own? If not, any idea what the keepalive issue was?

Q:  Apache processes variables in the URL (parses into r->args) during POST requests, but the mod_form implementation doesn't look for r->args when handling POST requests. Is this disallowed/discouraged in the spec or an oversight in the implementation?

Thanks,
Erik