> Date: Tue, 15 Feb 2005 14:19:20 -0800 > From: " Joseph M Dupr? (AVAB Inc.) " <[EMAIL PROTECTED]> > Subject: [Apache-FP] Lost Front Page Access to Webs (solved) > To: apache-fp@lists.joshie.com > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII > > I previously mentioned that I lost all access to FP webs via the FP > editor. When trying to open a FP web, it would appear that the > password was incorrect. No errors would be generated, it would just > keep requesting a password. > > I had recently re-arranged my httpd.conf file, pulling out the > VirtualHost directives into a separate file. I would then load them at > the end of httpd.conf with a "Include conf/vhosts.conf" line. > > This method breaks FrontPage for some reason unknown to me. > When I moved the VirtualHost directives back into the httpd.conf file, > everything works fine. > > Can someone please explain to me why FrontPage requires the > VirtualHost directives to be in httpd.conf, and can not deal when they > are "included" from a different file??? Why is FP accessing httpd.conf > directly anyway??? > > [I am running FP extensions 5.0.2.2634 / Apache 2.0.40 / RedHat > Linux 9] > > - Joe
Date: Thu, 17 Feb 2005 03:38:21 +0000 From: MJ Ray <[EMAIL PROTECTED]> Subject: Re: [Apache-FP] Lost Front Page Access to Webs (solved) To: <apache-fp@lists.joshie.com> Message-ID: <[EMAIL PROTECTED]>
Joe wrote:
Can someone please explain to me why FrontPage requires the VirtualHost directives to be in httpd.conf, and can not deal when they are "included" from a different file??? Why is FP accessing httpd.conf directly anyway???
I think FP is parsing the VirtualHost sections to extract some of the
configuration details. It's very stupid, so Include is beyond it. You
can even write VirtualHost sections to a dummy-httpd.conf and make FP use that instead, if you're sufficiently twisted and the dummy config matches the effect of your main configuration for the FP sites.
That is interesting. I know that FPSE parses the conf file when you add/configure a site, but was not aware that it needed to parse it when you try to publish or browse a site using MS FrontPage.
I was perplexed about the move to directory based config files with Debian's Apache 2.0 because it was making it very difficult to get FPSE installed. I ran out of time and went with Apache 1.3 and am keeping that so that the servers are all configured in a similar fashion.
I documented my experiences here:
http://wiki.debian.net/?SargeApache2FPSE
Later Daniel O'Neill contacted me to get more details about my trouble and then he went ahead to write a shell script that combines all the included files into one big conf file so you can add your site, and then you can run his script again to break it apart into a collection of included files again. He claimed it worked. I never tried it, and you're saying that FPSE doesn't like a broken-up conf file when just publishing to sites. Very interesting.
Some day I'll get around to installing FPSE on Apache 2.0. Hopefully this is all sorted out by then. ;)
Speaking of FPSE on Apache 2.0, I see that Joshua has been doing Apache 2.0 since 2004. What mpm model(s) does it work under? Just mpm-prefork?
http://www.jnux.net/community/apachefp/
-- Jacob _______________________________________________ Apache-FP mailing list Apache-FP@lists.joshie.com http://lists.joshie.com/mailman/listinfo/apache-fp
Donations:
http://www.amazon.com/paypage/PT5LZITM9L227
