Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have some ISOs that need to be available across a WAN, so we are using an http server to host them (allows for non-authenticated, read-only access (beyond being on the VPN) to the data store).

The server the ISOs reside on is running CentOS 4, and Apache 2.0.58.

Is there a way around the 2GB filesize limit with Apache 2.0 without using the split utility to chunk the ISOs down to a less-than-2GB size?

share|improve this question
up vote 1 down vote accepted

If you can upgrade the Apache install to 2.2.x then larger files should work by default (as 2.2 uses 64 bit file position offsets by default if supported by the OS).

I believe similar support is possible directly in Apache 2.0.x, at least in later minor versions there-of, but generally only if you compile your own custom version.

share|improve this answer
Thanks, David - that was what I was afraid I'd hear... unfortunately, upgrading is not an option at the moment. – warren May 20 '10 at 13:13
Would it be possible to do you own compile of the Apache package? I know Debian has good support for grabbing a package's source (with their back-ported patches), compiling with different options, and making your own package that will work in place their standard one - I'm sire CentOS (being based on RHEL) will have similar support in its package management arrangement. Obviously the compiling and testing must be done on another (perhaps virtual) machine, and it isn't a hands-free-simple process, but it might be a useful stop-gap for you. – David Spillett May 20 '10 at 21:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.