Bug 117959 - Apache autoindex corrupt when > 2GB file in tree
Apache autoindex corrupt when > 2GB file in tree
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: httpd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
Depends On:
Blocks: 116727
  Show dependency treegraph
Reported: 2004-03-10 08:47 EST by Lance Davis
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-17 21:53:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lance Davis 2004-03-10 08:47:24 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20040228

Description of problem:
Apache doesnt display the index properly when there is a > 2GB file in
the directory. It doesnt display the file at all, and seems to stop
displaying anything else when it comes across it.

There is no warning or error , just a randomly shortened directory tree.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.put >2GB file in directory
2.no index.html etc and mod_autoindex

Actual Results:  as described above

Expected Results:  full tree displayed

Additional info:

Bug #109332 refers
Comment 1 Joe Orton 2004-03-10 09:14:10 EST
Thanks for the report.

Since the server can neither stat() the large file to discover its
size, nor serve it to clients, I think the expected behaviour is that
it is omitted from the directory listing.  Do you agree?
Comment 2 Lance Davis 2004-03-10 09:22:40 EST
Yes - maybe with a warning to the error log, so people can see why it
isnt there if they look - or display in the index with a '>2GB
unknown' type ebtry.
Comment 3 Jay Turner 2004-08-17 21:53:54 EDT
Fix confirmed with httpd-2.0.46-38.ent.
Comment 4 Josh Bressers 2004-09-01 14:55:39 EDT
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.