Eric Covener wrote:
I'll note I even put in the following, to no avail: <FilesMatch "^/(.*).ram$"> ForceType audio/x-pn-realaudio </FilesMatch>I wonder if on the 2nd system the files are not really served by the "default handler" and somehow end up pumped through e.g. PHP?
We've noted that NO MATTER WHERE this FilesMatch stanza appears
in the file, it never seems to be imposing the ForceType on .ram
files that clearly SHOULD be matching.
Have changed the spelling of the FilesMatch pattern several times
to no avail. Latest try is simply "\.ram$"
Moved it all around, deep into the virtual host definition and out
in the overal common configuration. Even down into the very directory
where the SetHandler directive citing the 3rd-party handler that
secures the .ram files from their repository on behalf of Apache is.
Is ForceType failing, or is it our regular expression or something
else?
Again, happy to kick LogLevel to 64 or more if that'll help.
--
J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@xxxxxxx
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/jlw12@xxxxxxx?fmt=freebusy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|