On Tuesday 06 July 2010, Edward Welbourne wrote: > The web-server succeeded > in displaying the contents *usually*, but one of my colleagues > noticed that, on reload, he got 403'd. > > The fact that this (mostly) worked at all suggests that apache is > sometimes accessing content as root, instead of as the unprivileged > user www-data. The problem might be that Linux (the underlying > O/S) is being flaky about enforcing permissions.
It sounds much more likely that a browser or proxy server was caching the pages. When reloading, apache gave the 403. Can you rule that out? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
