Re: Apache, mod_perl and content type handlers

If your content type handler runs as a PerlTypeHandler then you run the risk that the content-type is overruled by some later (Apache or your own) odd mechanism. The ModPerl documentation specifically warns against such:

Of course later phases may override the mime type set in this phase

Alternatively maybe you can run your handler as a PerlFixupHandler? That's likely to put you in better 'type' control.

Comment on Re: Apache, mod_perl and content type handlers

Replies are listed 'Best First'.
Re^2: Apache, mod_perl and content type handlers by Mutant (Priest) on Apr 27, 2007 at 08:09 UTC
Good point, altho there's certainly nothing in my code that sets the content type. I wouldn't have thought Apache (or mod_perl) would do it anywhere else, and it certainly doesn't in most cases.	[reply]
Re^3: Apache, mod_perl and content type handlers by varian (Chaplain) on Apr 27, 2007 at 10:40 UTC
An example is configuration directives that are set in .htaccess and that define typehandlers for a directory. Other handlers would be mod-autoindex etc.	[reply]