Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of covener@gmail.com designates
 209.85.215.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=ThAXJ9dElC+fY619g/4TqkqjXIgmxyrR+TUvxajUsLG1Hk9OUDWYqEMTvQ3ZkUjkSf
         lGCw5d5GZKLdqgCul1zuoOQ8u6pDUY3JSlbu66x8zXVxroXPumj77+OMjwNXrdPwG7zJ
         kwJzKlNv7wBUK/nsIeOKSEjYd2Ng9abdFrG7k=
MIME-Version: 1.0
Date: Fri, 29 Oct 2010 10:14:54 -0400
Message-ID: <AANLkTi=aMAbEBwgghoqAaN0iEg6T7+UV+wEBwCX_y=Fe@mail.gmail.com>
Subject: doc or fix ForceType for not-default-handler?
From: Eric Covener <covener@gmail.com>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Currently ForceType is only really effective for static files, since
it works in a fixup hook and most other generators/handler will
clobber the value in the actual handler by calling ap_set_content_type
themselves.

Should it be documented a bit more directly (a guru can read between
the lines of the doc if you know what you're looking to justify),
moved into calling ap_set_content_type in a filter, or some other
directive be added to do this in a filter?

(IIRC mod_headers can't do this for free since it's before the HTTP
filter turns the r->content_type into a header)

-- 
Eric Covener
covener@gmail.com