ebcdic.html revision 091caae3b2ebdb760c98575d0d5e349cd686f913
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<HTML>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<HEAD>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<TITLE>The Apache EBCDIC Port</TITLE>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek</HEAD>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<BODY
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek BGCOLOR="#FFFFFF"
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek TEXT="#000000"
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek LINK="#0000FF"
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek VLINK="#000080"
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek ALINK="#FF0000"
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<!--#include virtual="header.html" -->
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<H1 ALIGN="CENTER">Overview of the Apache EBCDIC Port</H1>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek Version 1.3 of the Apache HTTP Server is the first version which
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek includes a port to a (non-ASCII) mainframe machine which uses
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek the EBCDIC character set as its native codeset.<BR>
28bf74a613770b649af5dd9c9b6b99625559d6acMarcel Telka (It is the SIEMENS NIXDORF family of mainframes running the
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <A HREF="http://www.sni.de/servers/bs2osd/osdbc_us.htm">BS2000/OSD
28bf74a613770b649af5dd9c9b6b99625559d6acMarcel Telka operating system</A>. This mainframe OS nowadays features a
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek SVR4-derived POSIX subsystem).
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek The port was started initially to
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <UL>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI> prove the feasibility of porting
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <A HREF="http://dev.apache.org/">the Apache HTTP server</A>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek to this platform
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI> find a "worthy and capable" successor for the venerable
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <A HREF="http://www.w3.org/Daemon/">CERN-3.0</A> daemon
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek (which was ported a couple of years ago), and to
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI> prove that Apache's preforking process model can on this platform
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek easily outperform the accept-fork-serve model used by CERN by a
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek factor of 5 or more.
28bf74a613770b649af5dd9c9b6b99625559d6acMarcel Telka </UL>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek This document serves as a rationale to describe some of the design
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek decisions of the port to this machine.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <H2 ALIGN=CENTER>Design Goals</H2>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek One objective of the EBCDIC port was to maintain enough backwards
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek compatibility with the (EBCDIC) CERN server to make the transition to
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek the new server attractive and easy. This required the addition of
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek a configurable method to define whether a HTML document was stored
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek in ASCII (the only format accepted by the old server) or in EBCDIC
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek (the native document format in the POSIX subsystem, and therefore
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek the only realistic format in which the other POSIX tools like grep
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek or sed could operate on the documents). The current solution to
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek this is a "pseudo-MIME-format" which is intercepted and
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek interpreted by the Apache server (see below). Future versions
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek might solve the problem by defining an "ebcdic-handler" for all
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek documents which must be converted.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <H2 ALIGN=CENTER>Technical Solution</H2>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek Since all Apache input and output is based upon the BUFF data type
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek and its methods, the easiest solution was to add the conversion to
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek the BUFF handling routines. The conversion must be settable at any
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek time, so a BUFF flag was added which defines whether a BUFF object
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek has currently enabled conversion or not. This flag is modified at
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek several points in the HTTP protocol:
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <UL>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI><STRONG>set</STRONG> before a request is received (because the
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek request and the request header lines are always in ASCII
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek format)
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI><STRONG>set/unset</STRONG> when the request body is
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek received - depending on the content type of the request body
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek (because the request body may contain ASCII text or a binary file)
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI><STRONG>set</STRONG> before a reply header is sent (because the
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek response header lines are always in ASCII format)
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI><STRONG>set/unset</STRONG> when the response body is
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek sent - depending on the content type of the response body
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek (because the response body may contain text or a binary file)
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </UL>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek<H2 ALIGN=CENTER>Porting Notes</H2>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <P>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <OL>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek The relevant changes in the source are #ifdef'ed into two
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek categories:
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <DL>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <DT><CODE><STRONG>#ifdef CHARSET_EBCDIC</STRONG></CODE>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <DD>Code which is needed for any EBCDIC based machine. This
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek includes character translations, differences in
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek contiguity of the two character sets, flags which
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek indicate which part of the HTTP protocol has to be
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek converted and which part doesn't etc.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <DT><CODE><STRONG>#ifdef _OSD_POSIX</STRONG></CODE>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <DD>Code which is needed for the BS2000 SIEMENS NIXDORF
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek mainframe platform only. This deals with include file
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek differences and socket implementations topics which are
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek only required on the BS2000/OSD platform.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </DL>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </LI><BR>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek The possibility to translate between ASCII and EBCDIC at the
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek socket level (on BS2000 POSIX, there is a socket option which
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek supports this) was intentionally <EM>not</EM> chosen, because
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek the byte stream at the HTTP protocol level consists of a
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek mixture of protocol related strings and non-protocol related
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek raw file data. HTTP protocol strings are always encoded in
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek ASCII (the GET request, any Header: lines, the chunking
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek information etc.) whereas the file transfer parts (i.e., GIF
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek images, CGI output etc.) should usually be just "passed through"
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek by the server. This separation between "protocol string" and
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek "raw data" is reflected in the server code by functions like
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek bgets() or rvputs() for strings, and functions like bwrite()
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek for binary data. A global translation of everything would
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek therefore be inadequate.<BR>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek (In the case of text files of course, provisions must be made so
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek that EBCDIC documents are always served in ASCII)
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </LI><BR>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek This port therefore features a built-in protocol level conversion
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek for the server-internal strings (which the compiler translated to
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek EBCDIC strings) and thus for all server-generated documents.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek The hard coded ASCII escapes \012 and \015 which are
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek ubiquitous in the server code are an exception: they are
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek already the binary encoding of the ASCII \n and \r and must
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek not be converted to ASCII a second time. This exception is
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek only relevant for server-generated strings; and <EM>external</EM>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek EBCDIC documents are not expected to contain ASCII newline characters.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </LI><BR>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek By examining the call hierarchy for the BUFF management
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek routines, I added an "ebcdic/ascii conversion layer" which
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek would be crossed on every puts/write/get/gets, and a
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek conversion flag which allowed enabling/disabling the
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek conversions on-the-fly. Usually, a document crosses this
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek layer twice from its origin source (a file or CGI output) to
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek its destination (the requesting client): <SAMP>file -&gt;
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek Apache</SAMP>, and <SAMP>Apache -&gt; client</SAMP>.<BR>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek The server can now read the header
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek lines of a CGI-script output in EBCDIC format, and then find
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek out that the remainder of the script's output is in ASCII
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek (like in the case of the output of a WWW Counter program: the
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek document body contains a GIF image). All header processing is
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek done in the native EBCDIC format; the server then determines,
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek based on the type of document being served, whether the
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek document body (except for the chunking information, of
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek course) is in ASCII already or must be converted from EBCDIC.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </LI><BR>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek For Text documents (MIME types text/plain, text/html etc.),
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek an implicit translation to ASCII can be used, or (if the
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek users prefer to store some documents in raw ASCII form for
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek faster serving, or because the files reside on a NFS-mounted
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek directory tree) can be served without conversion.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <BR>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <STRONG>Example:</STRONG><BLOCKQUOTE>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek to serve files with the suffix .ahtml as a raw ASCII text/html
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek document without implicit conversion (and suffix .ascii
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek as ASCII text/plain), use the directives:<PRE>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek AddType text/x-ascii-html .ahtml
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek AddType text/x-ascii-plain .ascii
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </PRE></BLOCKQUOTE>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek Similarly, any text/XXXX MIME type can be served as "raw ASCII" by
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek configuring a MIME type "text/x-ascii-XXXX" for it using AddType.
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek </LI><BR>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek <LI>
989f28072d20c73ae0955d6a1e3e2fc74831cb39Jerry Jelinek Non-text documents are always served "binary" without conversion.
This seems to be the most sensible choice for, .e.g., GIF/ZIP/AU
file types. This of course requires the user to copy them to the
mainframe host using the "rcp -b" binary switch.
</LI><BR>
<LI>
Server parsed files are always assumed to be in native (i.e.,
EBCDIC) format as used on the machine, and are converted after
processing.
</LI><BR>
<LI>
For CGI output, the CGI script determines whether a conversion is
needed or not: by setting the appropriate Content-Type, text files
can be converted, or GIF output can be passed through unmodified.
An example for the latter case is the wwwcount program which we ported
as well.
</LI><BR>
</OL>
</P>
<H2 ALIGN=CENTER>Document Storage Notes</H2>
<H3 ALIGN=CENTER>Binary Files</H3>
<P>
All files with a <SAMP>Content-Type:</SAMP> which does not
start with <SAMP>text/</SAMP> are regarded as <EM>binary files</EM>
by the server and are not subject to any conversion.
Examples for binary files are GIF images, gzip-compressed
files and the like.
</P>
<P>
When exchanging binary files between the mainframe host and a
Unix machine or Windows PC, be sure to use the ftp "binary"
(<SAMP>TYPE I</SAMP>) command, or use the
<SAMP>rcp&nbsp;-b</SAMP> command from the mainframe host
(the -b switch is not supported in unix rcp's).
</P>
<H3 ALIGN=CENTER>Text Documents</H3>
<P>
The default assumption of the server is that Text Files
(i.e., all files whose <SAMP>Content-Type:</SAMP> starts with
<SAMP>text/</SAMP>) are stored in the native character
set of the host, EBCDIC.
</P>
<H3 ALIGN=CENTER>Server Side Included Documents</H3>
<P>
SSI documents must currently be stored in EBCDIC only. No
provision is made to convert it from ASCII before processing.
</P>
<H2 ALIGN=CENTER>Apache Modules' Status</H2>
<TABLE BORDER ALIGN=middle>
<TR>
<TH>Module
<TH>Status
<TH>Notes
</TR>
<TR>
<TD ALIGN=LEFT>http_core
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_access
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_actions
<TD ALIGN=CENTER>?
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_alias
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_asis
<TD ALIGN=CENTER>?
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_auth
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_auth_anon
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_auth_db
<TD ALIGN=CENTER>?
<TD>with own libdb.a
</TR>
<TR>
<TD ALIGN=LEFT>mod_auth_dbm
<TD ALIGN=CENTER>?
<TD>with own libdb.a
</TR>
<TR>
<TD ALIGN=LEFT>mod_autoindex
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_cern_meta
<TD ALIGN=CENTER>?
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_cgi
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_digest
<TD ALIGN=CENTER>-
<TD>MD5 not ported yet
</TR>
<TR>
<TD ALIGN=LEFT>mod_dir
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_dld
<TD ALIGN=CENTER>-
<TD>no shared libs
</TR>
<TR>
<TD ALIGN=LEFT>mod_env
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_example
<TD ALIGN=CENTER>-
<TD>not tried yet
</TR>
<TR>
<TD ALIGN=LEFT>mod_expires
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_headers
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_imap
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_include
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_info
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_log_agent
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_log_config
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_log_referer
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_mime
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_mime_magic
<TD ALIGN=CENTER>-
<TD>not tried yet
</TR>
<TR>
<TD ALIGN=LEFT>mod_negotiation
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_proxy
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_rewrite
<TD ALIGN=CENTER>?
<TD>untested
</TR>
<TR>
<TD ALIGN=LEFT>mod_setenvif
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_speling
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_status
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_unique_id
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_userdir
<TD ALIGN=CENTER>+
<TD>
</TR>
<TR>
<TD ALIGN=LEFT>mod_usertrack
<TD ALIGN=CENTER>?
<TD>untested
</TR>
</TABLE>
<H2 ALIGN=CENTER>Third Party Modules' Status</H2>
<TABLE BORDER ALIGN=middle>
<TR>
<TH>Module
<TH>Status
<TH>Notes
</TR>
<TR>
<TD ALIGN=LEFT><A HREF="http://java.apache.org/">mod_jserv</A>
<TD ALIGN=CENTER>-
<TD>JAVA still being ported.
</TR>
<TR>
<TD ALIGN=LEFT><A HREF="http://www.php.net/">mod_php</A>
<TD ALIGN=CENTER>-
<TD>not ported yet
</TR>
<TR>
<TD ALIGN=LEFT
><A HREF="http://hpwww.ec-lyon.fr/~vincent/apache/mod_put.html">mod_put</A>
<TD ALIGN=CENTER>?
<TD>untested
</TR>
<TR>
<TD ALIGN=LEFT
><A HREF="ftp://hachiman.vidya.com/pub/apache/">mod_session</A>
<TD ALIGN=CENTER>-
<TD>untested
</TR>
</TABLE>
<!--#include virtual="footer.html" -->
</BODY>
</HTML>