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
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?
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?
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 Wed, Aug 22, 2012 at 4:26 PM, J.Lance Wilkinson jl...@psu.edu wrote:
Eric Covener wrote:
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
Tom Evans wrote:
On Wed, Aug 22, 2012 at 4:26 PM, J.Lance Wilkinson jl...@psu.edu wrote:
Eric Covener wrote:
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
--On 22 August 2012 13:05:40 -0400 J.Lance Wilkinson jl...@psu.edu
wrote:
ForceType nor the fact the file extension, .ram, has a match for
the mime type of audio\x-pn-realaudio in the cited TypesConfig file
seems to be applying the correct Content-Type header on the
Alex Bligh wrote:
--On 22 August 2012 13:05:40 -0400 J.Lance Wilkinson jl...@psu.edu
wrote:
ForceType nor the fact the file extension, .ram, has a match for
the mime type of audio\x-pn-realaudio in the cited TypesConfig file
seems to be applying the correct Content-Type header
