Well what do you know - disabling SELinux did the trick. Running as the 'apache' user under sudo vs. a daemon process must have a different SELinux security context.
Thanks! From: Wilda, Jet [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 11:24 AM To: users@httpd.apache.org; [EMAIL PROTECTED] Subject: RE: [EMAIL PROTECTED] problem serving large files Could it be that you have SELinux enabled and it is messing with you? ~Jet _____ From: John LaCour [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2008 10:03 AM To: users@httpd.apache.org Subject: [EMAIL PROTECTED] problem serving large files I'd like to make some very large files available for HTTP download from my Apache v2.2.3 server on RHEL5, but it's not working. I get the following error message: [error] [client 10.1.1.1] (13)Permission denied: access to /Very_Large_File.rar denied It would appear to be a file permission problem, but the directory paths to the document root are all 755 or better: / /var /var/www/ /var/www/html and the permissions on the file itself I've set to 777 for testing purposes. The same client can download small .rar files from the same directory with the same file permissions. The only difference that I can discern is that the file is smaller in size. I've further tested access to the file with "sudo -u apache cat Very_Large_file.rar" which can open the file fine. So I've pretty much ruled out permissions issues. I've also enabled 'debug' LogLevel but there's nothing generated that is helpful. I don't see anything in my .conf files that enforce any file sizes. I didn't even see such an option in the document, there appears to be configuration options only for limiting the size of the HTTP request *sent* by the client. Any insight into what's happen would be appreciated! Thanks, John ---------- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer.
