I have a FORMER production system, Sun Solaris 10 running Apache HTTPD v2.2.6,
with a highly customized configuration. It delivers files with the extension
".ram" with the desired Content-Type: audio/x-pn-realaudio, due to the contents
of its TypesConfig specified file, which contains "audio/x-pn-realaudio ram ra".
I have a new installation, RHEL 6 Linux running Apache HTTPD v2.2.15, with *as
far as I can tell* the same highly customized configuration (differences have
mostly to do with different host names, IP addresses, and paths to files,
directories, etc.). It delivers the same files with the extension ".ram" with
an undesired Content-Type: text/html, which seems to be due to the DefaultType
text/html present in the configurations (both of them). The equivalent
TypesConfig specified file on this machine has the same "audio/x-pn-realaudio
ram ra" specification as the Solaris version.
Clearly there's SOMETHING different in the configurations, because if we take
the SAME HTTPD on the same RHEL 6 installation but use a plain, vanilla, out of
the box configuration, it delivers the desired Content-Type correctly, so it's
not some difference between HTTPD versions.
But finding the difference needle in the configuration haystack has baffled me
so far. I'd happily crank up the LogLevel, for example, if I thought it would
get me somewhere. Is there any way to expose the inner musings of the way
HTTPD makes its Content-Type determination, like there is for example with a
RewriteLogLevel 9 for debugging Rewrite Rules, in Apache HTTPD v2.2.15 ?
I'll note I even put in the following, to no avail:
<FilesMatch "^/(.*).ram$">
ForceType audio/x-pn-realaudio
</FilesMatch>
--
J.Lance Wilkinson ("Lance") InterNet: lance.wilkin...@psu.edu
Systems Design Specialist - Lead Phone: (814) 865-4870
Digital Library Technologies FAX: (814) 863-3560
E3 Paterno Library
Penn State University
University Park, PA 16802
http://ucs.psu.edu/home/jl...@psu.edu?fmt=freebusy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
