From owner-freebsd-questions Sun Feb 24 9:52: 4 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.mango-bay.com (mail.mango-bay.com [208.206.15.12]) by hub.freebsd.org (Postfix) with ESMTP id 6572237B405 for ; Sun, 24 Feb 2002 09:51:54 -0800 (PST) Received: from barbish ([63.70.155.115]) by mail.mango-bay.com (Post.Office MTA v3.5.3 release 223 ID# 0-52377U2500L250S0V35) with SMTP id com; Sun, 24 Feb 2002 12:56:20 -0500 From: "Joe & Fhe Barbish" To: "G D McKee" Cc: "FBSDQ" Subject: RE: FrontPage 2020 Port Problems!! Date: Sun, 24 Feb 2002 12:51:49 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <010201c1bd55$fc039e90$c800a8c0@p1000> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yep you just got bit by the FBSD min standards. Don't they just suck. Here is a update I submitted to the maintainer of the mod_frontpage 2 weeks ago and have not received any response. If this works for you then let martin the port maintainer know. Martin How about changing pkg-message to this **************************************************************************** ******** mod_frontpage is now a APXS installation wrapper for frontpage on Apache13. This port is to be installed after the apache13 port is installed. One of the language specific xx-frontpage ports must be installed to complete the apache/frontpage environment. See FreeBSD web site for details. http://www.freebsd.org/cgi/ports.cgi?query=frontpage&stype=all&release=4.5-R ELEASE%2Fi386 The English version of the port does not adhere to the above naming convention, use port named frontpage for the English version. After apache13 & mod_frontpage & frontpage install is completed you must check your /usr/local/etc/apache/httpd.conf file and make the following manual changes. The ResourceConfig and AccessConfig are commented out. Replace them with ResourceConfig /dev/null AccessConfig /dev/null You'll also need to change AllowOverride None to AllowOverride all Under or add AllowOverride AuthConfig Limit Indexes Options There are new key words to turn on/off the frontpage extensions and the frontpage administration web site for apache web site defined in httpd.conf. FrontPageEnable activates the basic frontpage extensions which enables the Microsoft windows frontpage client to publish website content to the apache/frontpage server. FrontPageAdminEnable activates the frontpage web site administration pages which allows the fpadmin person to use a set of predefined admin pages to add, delete, and change the frontpage declaratives in the httpf.conf file from a browser. Any combination of the key words can be used in the httpd.conf file to refine the control of any web site defined in the httpf.conf file. FrontPageEnable # Enable Frontpage Extensions ms/fp client publish FrontPageDisable # Disable Frontpage Extensions ms/fp client publish FrontPageAdminEnable # Enable Frontpage Extensions Admin web site FrontPageAdminDisable # Disable Frontpage Extensions Admin web site You should add FrontPageEnable & FrontPageAdminEnable each on a separate line right after the dso modules list in the httpd.conf file as part of the your initial changes. If no key word options are present in the httpd.conf file the default of FrontPageDisable and FrontPageAdminDisable is used resulting in a working Apache environment where the complete frontpage environment is disabled. After you have made these changes, you'll have to execute: /usr/local/frontpage/version5.0/fp_install.sh to build the base apache/frontpage web site and assign the frontpage administrators ID/PW. You can also run this to add virtual hosts to the apache/frontpage system. You must use /usr/local/etc/rc.d/apache.sh script to manually start or stop the apache/frontpage server. FBSD boot will start apache ok as it uses this script. /usr/local/etc/rc.d/apache.sh start /usr/local/etc/rc.d/apache.sh stop See /var/log/httpd-error.log for error messages. 2/15/2002 This has been tested on FBSD 4.4 & 4.5. This will not work on apache2. **************************************************************************** ******** -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of G D McKee Sent: Sunday, February 24, 2002 12:09 PM To: Freebsd-Questions@Freebsd. Org (E-mail) Subject: FrontPage 2020 Port Problems!! Hi I have got the apache13-modssl port compiled and install and working - then I installed mod_php4 and it is fine. The I want FrontPage 2002 server extensions so I have installed the mod_FrontPage port and the FrontPage port. When I HUP httpd I get the following: [Sun Feb 24 10:10:56 2002] [notice] Apache/1.3.23 (Unix) mod_ssl/2.8.6 OpenSSL/0.9.6a FrontPage/5.0.2.2623 PHP/4.1.1 configured -- resuming normal operations [Sun Feb 24 10:10:56 2002] [notice] Accept mutex: flock (Default: flock) So from this I figures I was pretty close to getting it to work. Then I went through the /usr/local/FrontPage/version5.0/fp_install.sh and configured the default web server and a virtual server. FrontPage on the other hand will not pick up and files from the web server and just error saying The folder may be located in an unavailable location, protected with a password, or the filename contains a / or\. I have a look at the server logs for a server with 2000 extensions on it and the web server gets the same request. The line look as follow - on the 2000 server: 192.168.0.1 - - [24/Feb/2002:10:16:52 +0000] "OPTIONS / HTTP/1.0" 200 - "-" "Microsoft Data Access Internet Publishing Provider Protocol Discovery" 192.168.0.1 - - [24/Feb/2002:10:16:52 +0000] "GET /_vti_inf.html HTTP/1.0" 200 1716 "-" "Mozilla/2.0 (compatible; MS FrontPage 5.0)" 192.168.0.1 - - [24/Feb/2002:10:16:53 +0000] "POST /_vti_bin/shtml.exe/_vti_rpc HTTP/1.0" 200 228 "-" "MSFrontPage/5.0" 192.168.0.1 - - [24/Feb/2002:10:16:53 +0000] "POST /_vti_bin/_vti_aut/author.exe HTTP/1.0" 401 471 "-" "MSFrontPage/5.0" and on the 2002 server that doesn't work: 192.168.0.1 - - [24/Feb/2002:10:12:47 +0000] "GET /_vti_inf.html HTTP/1.0" 200 1754 "-" "Mozilla/2.0 (compatible; MS FrontPage 5.0)" 192.168.0.1 - - [24/Feb/2002:10:12:47 +0000] "POST /_vti_bin/shtml.exe/_vti_rpc HTTP/1.0" 200 139 "-" "MSFrontPage/5.0" 192.168.0.1 - - [24/Feb/2002:10:12:47 +0000] "OPTIONS / HTTP/1.0" 200 - "-" "Microsoft Data Access Internet Publishing Provider Protocol Discovery" I have had a look on both servers and neither server has any of these author.exe or shtml.exe files in the places the logs say. There is no info in the error log either. I also read I needed the following lines in the httpd.conf file #FrontPageEnable On # Enable FrontPage Extensions #FrontPageDisable # Disable FrontPage Extensions #FrontPageAdminEnable On # Enable FrontPage Extensions fpadmcgi.exe #FrontPageAdminDisable # Disable FrontPage Extensions fpadmcgi.exe but ever time I use them, apache comes up with syntax errors. Does anyone have any ideas? Thanks in advance Gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message