OK, So, upon further investigation I think we can close this one. It seems that it was the caching in Chrome that was the problem. Firefox did not exhibit the same problem and when I tried to access the dud URLs through Chrome, apache2 was not even contacted.
It seems that when PHP was disabled for the userdirs Chrome cached the files that were served up as ascii downloads and kept giving me the same thing even when I changed the apache2 config. I flushed the Chrome cache and now all is good. Incidentaly, the disabling of userdir PHP in this way was confusing for me as I am not actually using the userdir mod. I have just changed the DocumentRoot to be off my home directory to make local development easier. Thanks for all your efforts guys, sorry about the run around. A. On Mon, Apr 5, 2010 at 6:31 PM, Stefan Fritsch <s...@sfritsch.de> wrote: > Kenneth: Enabling php in the userdirs is a security hazard: It allows > every local user on a machine to execute arbitrary code as user www- > data. As this is non-obvious to most admins, the default was changed. > > In any case, this is not Zalzadore's problem: > > > http://localhost/bean/index.php the page will render correctly but not > if I visit http://localhost/bean/ > > I have no idea what could be causing this. Zalzadore, can you post more > details about your configuration? > > -- > apache2 with mod php5 does not execute index.php > https://bugs.launchpad.net/bugs/554903 > You received this bug notification because you are a direct subscriber > of the bug. > -- apache2 with mod php5 does not execute index.php https://bugs.launchpad.net/bugs/554903 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
