httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Havlak" <>
Subject [users@httpd] Apache configuration on Fedora 5
Date Wed, 29 Nov 2006 08:31:45 GMT
I'm trying to configure Apache 2.2.2 on Fedora Core 5.  I've been
getting unexpected behavior for HTML files and images (.jpg and .gif)
when viewed in Mozilla  I'm connected on static IP to a
netgear Router

First symptom I'm experiencing is that HTML files bring up a dialog
asking whether to download or save.  In MSIE they display normally
(with the exception of symptom 3 noted below).  From what I have read,
this is usually an indication that my server is not sending correct
content types (since MSIE ignores content types anyway), but I have
checked my mime.types file and it includes the line:
text/html              html htm
which I believe to be correct.  I'm not using any .htaccess files.
I've checked my httpd.conf which does have the right path for

Symptom number two is that both .gif and .jpg images consistently
display a 403 Forbidden error, which shows up in the error log as
"(13)Permission denied: access to /paradise.jpg denied" .  The
permissions for paradise.jpg in this case are set the same as for a
text file in the same directory which displays normally (read
permissions allowed to everyone).  The entries in mime.types for .gif
and .jpg also appear to be normal.

Symptom number three is that requesting a directory from Mozilla
displays the directory contents when no index.html file exists (I have
my DirectoryIndex directive set to index.html index.html.var) BUT when
there is an index.html Mozilla brings up the same "download or open?"
dialog, but with a blank or apparently random (e.g. kesp6g7b)
filename.  If downloaded or forced to view as HTML, this file turns
out have the same content as the index.html file.  In the same
scenario MSIE complains that it doesn't know how to handle the file
type.  I have the Indexes option specifed for my document root in the
httpd.conf file.

To me it seems like at least the first two symptoms are related to my
server somehow failing to communicate the proper content types.  Does
anyone have any suggestions for where to look for the problem?  I'd
also appreciate any advice on dealing with symptom 3 (indexes).



The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message