Martin Langhoff wrote: > >>I will try as you suggest. However, /var/www/blobs and all its > >>contents are owned by apache:apache on my system, so that is > >>unlikely to be the problem. > > > > > > True. > > I disagree. See below...
Ah, well, even though you'll get me later in your mail, I was still right here: file permissions had nothing to do with it :) > Midgard always has problems serving its "root" page in a properly > locked-down apache. I always found it rather odd that the file was > placed in the libexec dir. But the fact is that the default apache > config is quite lax. Right, and that would indeed be the issue. I'm not entirely certain why the libexecdir was chosen, but my guess is that it was 'just there'. apxs doesn't provide many hints as to where to put data like this, so it just went with the module. The only vars apxs discloses are TARGET, CC, CFLAGS, CFLAGS_SHLIB, LD_SHLIB, LDFLAGS_SHLIB, LIBS_SHLIB, PREFIX, SBINDIR, INCLUDEDIR, LIBEXECDIR and SYSCONFDIR; of these, I think only LIBEXECDIR and SYSCONFDIR are candidates. And I don't really think you want SYSCONFDIR serveable either, I guess. Another option would be to install it in a midgard-lib location. > On the other hand, we could change policy and drop the root file > somewhere where it makes more sense (/cgi-bin?)... as locked-down apache > configs become the norm. cgi-bin is another option, but not one we'll be able to find at configure time. > Also, if any of the directories cannot be accessed, it also makes sense > to check that the full path (every parent directory) allows 'others' to > 'read'. Sometimes someone with the best of intentions tightens the > permissions on /var and ... poof! But that'd add overhead to each and every request. > cheers and happy 2003, I for one hope for better luck skydiving this year :) You know (or might not) what they say: If at first you don't succeed, maybe skydiving is not the sport for you :) Blue ones, and all the best to everyone, Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
