Eric Covener wrote:
Sure looks like the DefaultType kicking in, which should not happen with an appropriate AddType.
Well, the user checked, did find a DefaultType text/plain in his
configuration. He REMOVED IT, and it still delivers these files with
Content-Type: text/plain.
He had a ForceType also, but that was to force text/html, and it
was conditioned within a <FILEMATCH> stanza and clearly wasn't what
was being triggered since we keep getting text/plain.
The file itself is being genrated not via a CGI but some Oracle
process (this IS an Apache configured by Oracle after all), so he's
trying to figure out now just what might be generated by that
procedure, which DOES seem to generate a Content-Type header. If
we can determine that it gets OMITTED in this case that would explain
the type/plain from the DefaultType, perhaps, even with the DefaultType
directive being removed. Another possibility is the process itself
has no idea what to assign as a Content-Type, and thus it backpedals
and assigns text/plain because it has nothing better to assign
(although application/octet would be better, eh?).
--
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
|