Re: strange behaviour of Readme postamble

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/09/07 13:19, Jason Keltz wrote:
On 04/09/07 12:56, Joshua Slive wrote:
On 4/9/07, Jason Keltz <jas@xxxxxxxxxxxx> wrote:
Hi.

I'm experiencing some strange behaviour with the Header/Readme
pre/postamble directives on our Apache 2.2.X server.

One of our users was complaining that he had placed two totally text
README files in two separate directories on our server.  When he visited
the first directory in his web browser, he saw the directory contents
followed by his "README" file.  However, when he visited the second
directory, the contents of the README file was not displayed.
File/directory permission was not an issue.  When I looked into the
problem, I found that if a README (or HEADER) file contains html, it
works great.  However, if the file is plain text and does not include
the word "the" that the file would not be displayed.  For example, if I
create a README file containing only the word "the", the file is
displayed when I visit the directory.  However, if I remove any one
letters from "the", the file is not displayed.  This seems really really
weird, and I'm probably missing something very silly here.  It looks
like this is handled by the "emit_tail" function which should display
anything text/*.  The question is, how do I determine what the web
server considers the content as?  Anyone have any experience with this
weird behaviour?

Sounds like mod_mime_magic might be getting in the way.

To see what content-type apache is seeing, simply request the README
file directly (ie http://yoursite.example.com/dir/README) and examine
the Content-Type http response header.

Hi.

The web browser says that "Content type" is "text/plain" whether I have "the" in the file or not!

As it happens, mod_mime_magic code maps "The" and "the" to L_ENG. There's a table that says "English text" -> "text/plain". As a result, if you don't have the word "the" in the file, and the file is not html, there doesn't seem to be anything else that would distinguish this file as "text/plain". There *is* a "DefaultType" directive which is by default set to "text/plain", and this does indeed work since the web browser gets served the file as text/plain when called directly, but this looks like it is done "after" mod_mime_magic has returned a "declined" status and hence has not displayed the file. It seems like an underlying bug.

Jason.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux