Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3FABE43E.9070700@virbus.de>
Date: Fri, 07 Nov 2003 19:28:14 +0100
From: Joerg Heinicke <jheinicke@virbus.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.5) Gecko/20031007
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: DO NOT REPLY [Bug 17370]  -     Wrong HTTP Content Length for
 Reader when "show-time"
References: <20031107100031.21964.qmail@nagoya.betaversion.org>
 <3FAB9417.4050801@verizon.net> <bogksl$gvg$1@sea.gmane.org>
 <A282C12A-114D-11D8-9943-000393D2CB02@apache.org>
In-Reply-To: <A282C12A-114D-11D8-9943-000393D2CB02@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

On 07.11.2003 19:10, Stefano Mazzocchi wrote:

>>> But it might not worth the trouble adding all this complexity just to
>>> implement some debug feature
>>
>>
>> Well, it obviously is a debug feature. But you probably
>> might want to look at it as a small, discreet marketing
>> feature also. I suppose some IT-oriented people view
>> the page source to see the quality of html code
>> or to find out "how" was the page construted/generated.
>> And don't forget the show-time feature prints not only
>> the processing time, but also the Apache Cocoon mark.
>>
>> (<!-- Processed by Apache Cocoon 2.2... -->)
>>
>> That's a common practice used in many frameworks/producs
>> ex Vignette products etc.
> 
> 
> FYI, cocoon already outputs a "X-cocoon:" HTTP header that "markets" our 
> presence in every request it handles. So, if we really want to know if 
> cocoon handles that resource look at the HTTP headers, they don't break 
> content length and are much more "REST"-ish.

But this can be shadowed/hidden by a web server. I never investigated 
why, but our applications running on Cocoon don't have this header. So I 
guess it's the web server (Apache in this case).

Joerg