Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 98435 invoked by uid 500); 18 Mar 2003 14:47:44 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 98400 invoked from network); 18 Mar 2003 14:47:43 -0000 Received: from nebula.mpn.com (194.72.64.30) by daedalus.apache.org with SMTP; 18 Mar 2003 14:47:43 -0000 Delivered-To: <> Received: from [10.11.155.40] (tashayarr-ext.vnu.co.uk [193.117.79.10]) by nebula.mpn.com (8.8.5/8.8.5) with ESMTP id OAA32482 for ; Tue, 18 Mar 2003 14:47:44 GMT User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Tue, 18 Mar 2003 14:49:59 +0000 Subject: Re: AbstractTextSerializer From: Pier Fumagalli To: Message-ID: In-Reply-To: <3E772AD7.2020604@verizon.net> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N "Vadim Gritsenko" wrote: > Pier Fumagalli wrote: > >> How does "AbstractTextSerializer" sets the content type header in the HTTP >> response? The getMimeType method inherited from AbstractSerializer always >> returns "null"... >> > > See AbstractProcessingPipeline.java, and see also related to this bug > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10277 Aha... Gotcha... As charset is on the same header, they should be fixed together... Pier