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?
On both systems, the files in question are only accessible thru
a specific handler, the Adobe CQ Dispatcher. The fact we're getting
anything (in fact the 53 bytes of text we're seeing in the text/html or
text/plain [we tried dropping the DefaultType directive for a while]
are showing exactly the expected contents OF that 53-byte .ram file)
confirms that handler is being accessed to secure the content).
The handler involved IS a single point upgrade on Linux (v4.0.9) from
its Solaris counterpart (v4.0.8). So we're considering backpedalling
that if possible on the odd chance there's a difference in Content-Type
coming out of that handler.
--
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
