You could just try disabling the SELinux just to see if it is really the culprit. They also have a page that tells you where the "Access denied" messages go at http://docs.fedoraproject.org/en-US/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html .
The correct solution would probably be to set a extended file attribute allowing apache to write to it. The description of the policies and extended file attributes is at: http://fedoraproject.org/wiki/SELinux/apache . God knows which one it is.