Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of toby.collett@gmail.com
 designates 209.85.218.165 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=kxevBQLxCXACkRCL2qBfcnIhpRzJS95QOFS262dCKJK6NMCxFfGVFCWEt45eCLfN1t
         uLZltimnTELyXr/FkEJq636MTJ7YYjzSAqs51539HLhGQagtYcBA4/Mcies4ijSehmAT
         xmJFGahRM6k7R4a/E/r6YXDjeUi/oXrzSustg=
MIME-Version: 1.0
Sender: toby.collett@gmail.com
Date: Sun, 24 May 2009 11:53:36 +0200
Message-ID: <97b8070e0905240253n49dc43f4x3918ef5483473191@mail.gmail.com>
Subject: Changing the HTTP response code in a proxy response
From: Toby Collett <tcollett+lists@plan9.net.nz>
To: modules-dev@httpd.apache.org
Content-Type: multipart/alternative; boundary=001636b4320fb2b477046aa577fb

--001636b4320fb2b477046aa577fb
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi all,
I am writing a proxy module that supports a custom extension to the mostly
unimplemented 'Delta coding' RFC. The original standard uses a 226 http
status code for its responses to help deal with HTTP 1.0 web caches
(although this does not completely solve the caching problem).

To be compatible with the delta coding standard I need to be able to set the
226 status code on my responses, but I have having trouble working out how I
would do this in the apache module framework. From what I understand this
needs to be done during header parsing, as the headers are sent to the
downstream server before the body is processed, but I have been unable to
find the right mechanism to do this.

Regards,
Toby Collett

--001636b4320fb2b477046aa577fb--