Apache filesize limit?
 

I have a directory on my server containing ISO files for random linux distros. All of the CD ISOs show up (less than 800mb), but all of the DVD ISOs are hidden (over 1gb). Well, actually not even hidden - its like they are not there at all (even direct linking fails to find these files).

I have googled around and asked a few fellow geeks, and no one seems to know what I am talking about or doesn't have an answer.

What I want to know, is how do I get apache to list these huge files in the directory listing?

Are the files larger than 2gb?

Apache 2.2 has large file support built-in for files greater than 2gb, but I do not believe previous versions included large file support by default. What version of apache are you using?

Apache/2.2.3 (Debian) PHP/5.2.0-8+etch7 Server at houston.pl3x.net Port 80

Yes about the 2gb size. I have ISOs that are about 600-800mb and then some around 4.7gb and nothing in between so I honestly do not know where the 'limit' is set at. All I know is my huge 4.7gb files do not show up.

Is your Debian install 32 or 64 bit? Apache docs mention that large file support is built in, but specifies 32 bit modern Unix systems.

It's only 32 bit. :(

Hmm... Apache docs mention large file support is supposed to work with 32 bit unix type OS by default. I wonder what we're missing...

I'm stumped at the moment.

I read an article a while back about Lighttpd being good (and supposedly faster than Apache as well) with handling very large file downloads. That might be something to look into. If you have a spare IP address on the same server you should be able to run it alongside apache.

Another option is using the split command to make the file smaller. Although, anyone who downloads the pieces will need to know how to reassemble them back into the original file.

Well, poop. I like apache :/ I guess I could use RAR to create chunks if I ever need to. Everyone and their dog knows how to extract from RAR chunks.

I wonder if there might be an option in one of Apache's config files to turn LFS on/off. That might be worth looking into.

You wouldn't need to switch from using apache, just install lighttpd to run on another IP address alongside of apache. It shouldn't interfere at all. You would need to configure Apache not to listen to the IP that you allocate to lighttpd.

I like apache as well and use it for my hosting. Although, I have read some very good things about other linux web servers as well. Apache seems to be the most configurable, most compatible and has the most features - but there are some web server programs that can do some things much better than apache.

I'm not sure if this is about lighttpd or one of the others, but I read an article a few weeks back about how some company dropped their load from maxing out 3 servers with apache to using a single server for the same traffic levels with another program. But that was for a very specific purpose, I think it was either a very busy image hosting or downloads type website.