Guys, We actually found the problem. The problem was actually in a javascript file. It was referring to it's parent directory as mycompanyStore. So once I noticed that, I went into that directory and created a symlink. ln -s . mycompanyStore from within that directory. That let the java script know that the directory it was in was actually the one that it wanted. Before that was done Apache was looking for the image files in /var/www/mycompanyStore/mycompanyStore/images/foo.img Once I put that symlink in place, that actually corrected the problem. So I told the developer what I'd done and she fixed the JS to end up with the same effect. So now the problem is fixed! Anyway, I really do appreciate the support you guys are always ready with on the list!! Thanks, Tim On Fri, Aug 28, 2015 at 1:06 PM, Tony Mountifield <tony at softins.co.uk> wrote: > In article <0F55E883640C125375C75506 at ritz.innovate.net>, > Richard <lists-centos at listmail.innovate.net> wrote: > > > > Also need to see the error_log entries from the back-end httpd > > server that's serving from the documentroot. The proxy server's logs > > (whether it should be there or not) only show the proxy issues, not > > the issues that are causing the 404s, so aren't really relevant to > > the 404 issue. The back-end server's logs will indicate why the file > > can't be found, or generally at least pretty good hints. > > The first question is: are there even a separate back-end and front-end, > or is it just a single server that is misconfigured and is trying to do > proxy operations when it shouldn't? It sounds to me like the latter. > > Cheers > Tony > -- > Tony Mountifield > Work: tony at softins.co.uk - http://www.softins.co.uk > Play: tony at mountifield.org - http://tony.mountifield.org > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B