Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Thu, 10 May 2012 17:39:59 +0100
From: Nick Kew <niq@apache.org>
To: modules-dev@httpd.apache.org
Subject: Re: about setting r->headers_out
Message-ID: <20120510173959.4968cb86@baldur>
In-Reply-To: <4FAB9A46.8060307@cord.dk>
References: 
 <CAMCDODcck4=oqXNxXga2=oajzoBypfNF-ei4wCZtsn_homrspw@mail.gmail.com>
	<CAMCDODfRrJyMhkn1MA95=1FmqeF5rkEVd-W1ES-CA=BP=dJ0bQ@mail.gmail.com>
	<4FAB9A46.8060307@cord.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 10 May 2012 12:36:54 +0200
Daniel Gruno <rumble@cord.dk> wrote:

> On 10-05-2012 12:25, Julio Carlos Barrera Juez wrote:
> > Hi!
> > 
> > I have the same problem than you, Rui Hu. I have an output filter that
> > changes the body of the response, but then "content-type" header is
> > changed to "text/plain", and I want to maintain the original
> > "text/html".

Erm, that doesn't sound like an original anything.  More like
the core inserting a default type when none was set.

> Have you tried using ap_set_content_type(r, "text/html") instead?
> I noticed that in its description, it says:

That should be the usual solution.

> "This function must be called to set r->content_type in order for the
> AddOutputFilterByType directive to work correctly.", so it may be
> related to your problem.

Whoops!  That's no longer true since AddOutputFilterByType moved
to mod_filter.  Where do the docs still say that?


-- 
Nick Kew