httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@locus.apache.org
Subject cvs commit: httpd-docs-1.3/htdocs/manual/misc FAQ-E.html
Date Thu, 03 Aug 2000 11:10:39 GMT
coar        00/08/03 04:10:38

  Modified:    htdocs/manual install.html
               htdocs/manual/misc FAQ-E.html
  Log:
  	Some updates from Joshua Slive.  I lost the message describing
  	the FAQ change, but concerning install.html he says:
  
  	"It seems strange that the installation docs for apache don't
  	even mention the method that most people use to install apache.
  	(I know, it was a political issue).  This provides a reference."
  
  Submitted by:	Joshua Slive <slive@finance.commerce.ubc.ca>
  Reviewed by:	Ken Coar
  
  Revision  Changes    Path
  1.28      +5 -2      httpd-docs-1.3/htdocs/manual/install.html
  
  Index: install.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/install.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -u -r1.27 -r1.28
  --- install.html	1999/11/28 11:38:58	1.27
  +++ install.html	2000/08/03 11:10:33	1.28
  @@ -16,8 +16,11 @@
   
   <H1 ALIGN="CENTER">Compiling and Installing Apache 1.3</H1>
   
  -This document covers compilation and installation of Apache on Unix
  -systems only. For compiling and installation on Windows, see <A
  +<P>This document covers compilation and installation of Apache on Unix
  +systems, using the manual build and install method. If you wish to
  +use the autoconf-style configure interface, you should instead
  +read the INSTALL file in the root directory of the Apache source
  +distribution. For compiling and installation on Windows, see <A
   HREF="windows.html">Using Apache with Microsoft Windows</A> and for
   TPF see <A HREF="install-tpf.html">Installing the Apache 1.3 HTTP
   Server on TPF</A>.
  
  
  
  1.6       +12 -8     httpd-docs-1.3/htdocs/manual/misc/FAQ-E.html
  
  Index: FAQ-E.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/misc/FAQ-E.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -u -r1.5 -r1.6
  --- FAQ-E.html	2000/04/18 17:21:26	1.5
  +++ FAQ-E.html	2000/08/03 11:10:36	1.6
  @@ -31,7 +31,7 @@
     <!--#include virtual="header.html" -->
     <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
     <P>
  -  $Revision: 1.5 $ ($Date: 2000/04/18 17:21:26 $)
  +  $Revision: 1.6 $ ($Date: 2000/08/03 11:10:36 $)
     </P>
     <P>
     The latest version of this FAQ is always available from the main
  @@ -594,14 +594,18 @@
          Explorer, but show up as source or trigger a save window
          with Netscape?</STRONG></A> 
      <P>
  -   Internet Explorer is ignoring the mime-type you have configured for
  -   the file and guessing the file type based on the filename
  -   extension.  IE does this for any file which the web server marks as
  -   application/octet-stream or text/plain.  Netscape, on the other
  -   hand, properly follows the directions of the web server and treats
  -   the file as text/plain (displays it in the browser window as-is) or
  -   application/octet-stream (pops up a download window).
  +   Internet Explorer (IE) and Netscape handle mime type detection in different
  +   ways, and therefore will display the document differently.  In particular,
  +   IE sometimes relies on the file extension to determine the mime type.  This
  +   can happen when the server specifies a mime type of
  +   <CODE>application/octet-stream</CODE> or <CODE>text/plain</CODE>.
  +   (Unfortunately, this behavior makes it impossible to properly send plain
  +   text in some situations unless the file extension is <CODE>txt</CODE>.)
  +   There are more details available on IE's mime type detection behavior in an
  +   <A HREF="http://msdn.microsoft.com/workshop/networking/moniker/overview/appendix_a.asp">MSDN
  +   article</A>.
      </P>
  +
      <P>
      In order to make all browsers work correctly, you should assure
      that Apache sends the correct mime type for the file.  This is
  
  
  

Mime
View raw message