Microsoft Knowledge Base Email Alertz

Microsoft makes the source code of the FrontPage Apache patch file available. To compile an Apache Web server with any custom or non-standard modules along with the FrontPage Apache patch, follow the directions in this article. If you do not want to

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 216039 - Last Review: February 20, 2007 - Revision: 1.1

FP2000: How to Manually Patch an Apache Server

This article was previously published under Q216039

SUMMARY

Microsoft makes the source code of the FrontPage Apache patch file available. To compile an Apache Web server with any custom or non-standard modules along with the FrontPage Apache patch, follow the directions in this article. If you do not want to compile your own Apache Web server, you can patch your server with the Change_server.sh script located in /usr/local/frontpage/version4.0/bin. The instructions for applying Change_server.sh are in the following Knowledge Base article:
202198  (http://kbalertz.com/Feedback.aspx?kbNumber=202198/EN-US/ ) Installing FrontPage Extensions to Apache Web Server

MORE INFORMATION

Use the following steps to manually apply the FrontPage Apache patch to a new Apache server:
  1. Before compiling and installing the Apache patch, you must install the FrontPage Server Extensions. When the setup script untars the FrontPage Server Extensions, it also untars the FrontPage Apache patch source file Fp-patch-apache_1.3.x. If you run Fp_install.sh, let it untar the Fp40.platform.tar.Z without installing a root Web or sub/per user Webs, or virtual Webs.
  2. Copy the Fp-patch-apache_1.3.x into your Apache server build directory (usually /usr/local/Apache_1.3.x). The Fp-patch-apache_1.3.x file is found in/usr/local/frontpage/version4.0/apache-fp/fp-patch-apache_1.3.x.
  3. Using the GNU version of the patch utility, run the patch command on the FrontPage 2000 Apache patch source file:
    patch -p0 <fp-patch-apache_1.3.x
  4. Create the makefile for the patched server. For a server that uses 1.3.0 or later directory structure:
    ./configure --add-module=mod_frontpage.c
    For a server that uses 1.2.x, directory structure:
    ./configure --add-module=mod_frontpage.c --compat
    You can append --prefix=/usr/local/apache to get your install directories the way you want them. For instance, for a install directory of /usr/local/apache:
    ./configure --add-module=mod_frontpage.c --prefix=/usr/local/apache
  5. Build the Apache server: make
  6. Install the server: make Install
  7. After installing the server, you will need to run the Change_server.sh. This file was untarred when you ran the Fp_install.sh script. The Change_server.sh resides in /usr/local/frontpage/version4.0. When you run the Change_server.sh, you will be prompted whether or not to replace the httpd daemon. You should choose not to replace the httpd daemon because you just patched it. If you choose to replace it, your httpd daemon that you just patched will be replaced with a stock version. The main reason for running Change_server.sh in this case is to set permissions.
  8. You can install the Server Extensions using Fp_install making sure when prompted to install to Apache-fp when asked which server you are using.

APPLIES TO
  • Microsoft FrontPage 2000 Server Extensions
Keywords: 
kbinfo KB216039
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate