cvs commit: apache-1.3/htdocs/manual ebcdic.html
martin 98/09/08 14:06:20 Modified:htdocs/manual ebcdic.html Log: Updates, and announce that php3 is running perfectly Revision ChangesPath 1.5 +11 -11apache-1.3/htdocs/manual/ebcdic.html Index: ebcdic.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/ebcdic.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- ebcdic.html 1998/05/20 14:22:30 1.4 +++ ebcdic.html 1998/09/08 21:06:19 1.5 @@ -253,7 +253,7 @@ mod_actions - ? + + @@ -265,7 +265,7 @@ mod_asis - ? + + @@ -313,8 +313,8 @@ mod_digest - - - MD5 not ported yet + + + @@ -324,7 +324,7 @@ - mod_dld + mod_so - no shared libs @@ -338,7 +338,7 @@ mod_example - - not tried yet + (test bed only) @@ -398,7 +398,7 @@ mod_mime_magic - - not tried yet + not ported yet @@ -415,7 +415,7 @@ mod_rewrite - ? + + untested @@ -471,9 +471,9 @@ - http://www.php.net/";>mod_php - - - not ported yet + http://www.php.net/";>mod_php3 + + + mod_php3 runs fine
cvs commit: apache-1.3/htdocs/manual ebcdic.html
martin 98/04/01 06:03:58 Modified:htdocs/manual ebcdic.html Log: Update EBCDIC document, add Status table Revision ChangesPath 1.3 +307 -13 apache-1.3/htdocs/manual/ebcdic.html Index: ebcdic.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/ebcdic.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -u -r1.2 -r1.3 --- ebcdic.html 1998/03/26 16:19:47 1.2 +++ ebcdic.html 1998/04/01 14:03:58 1.3 @@ -45,6 +45,7 @@ decisions of the port to this machine. + Design Goals One objective of the EBCDIC port was to maintain enough backwards compatibility with the (EBCDIC) CERN server to make the transition to @@ -60,6 +61,7 @@ documents which must be converted. + Technical Solution Since all Apache input and output is based upon the BUFF data type and its methods, the easiest solution was to add the conversion to @@ -85,7 +87,7 @@ -Porting Notes +Porting Notes @@ -94,7 +96,7 @@ #ifdef CHARSET_EBCDIC Code which is needed for any EBCDIC based machine. This - includes character translations, differences in in + includes character translations, differences in contiguity of the two character sets, flags which indicate which part of the HTTP protocol has to be converted and which part doesn't etc. @@ -115,14 +117,14 @@ raw file data. HTTP protocol strings are always encoded in ASCII (the GET request, any Header: lines, the chunking information etc.) whereas the file transfer parts (i.e., GIF -images, CGI output etc.) should usually be just "passed thru" +images, CGI output etc.) should usually be just "passed through" by the server. This separation between "protocol string" and "raw data" is reflected in the server code by functions like bgets() or rvputs() for strings, and functions like bwrite() for binary data. A global translation of everything would therefore be inadequate. (In the case of text files of course, provisions must be made so -that the documents are always served in ASCII format) +that EBCDIC documents are always served in ASCII) @@ -134,8 +136,7 @@ already the binary encoding of the ASCII \n and \r and must not be converted to ASCII a second time. This exception is only relevant for server-generated strings; and external -EBCDIC documents always go through a bijective EBCDIC <-> ASCII -translation table. +EBCDIC documents are not expected to contain ASCII newline characters. @@ -143,16 +144,19 @@ routines, I added an "ebcdic/ascii conversion layer" which would be crossed on every puts/write/get/gets, and a conversion flag which allowed enabling/disabling the -conversions on-the-fly. It is now possible to read the header +conversions on-the-fly. Usually, a document crosses this +layer twice from its origin source (a file or CGI output) to +its destination (the requesting client): file -> +Apache, and Apache -> client. +The server can now read the header lines of a CGI-script output in EBCDIC format, and then find out that the remainder of the script's output is in ASCII (like in the case of the output of a WWW Counter program: the -document body contains a GIF image). Likewise, the server -always generates its header lines in EBCDIC (and with ASCII -conversion enabled) and determines, based on the type of -document being served, whether the document body (except for -the chunking information, of course) is in ASCII already or -is converted from EBCDIC. +document body contains a GIF image). All header processing is +done in the native EBCDIC format; the server then determines, +based on the type of document being served, whether the +document body (except for the chunking information, of +course) is in ASCII already or must be converted from EBCDIC. @@ -195,6 +199,296 @@ + + Document Storage Notes + Binary Files + +All files with a Content-Type: which does not +start with text/ are regarded as binary files +by the server and are not subject to any conversion. +Examples for binary files are GIF images, gzip-compressed +files and the like. + + +When exchanging binary files between the mainframe host and a +Unix machine or Windows PC, be sure to use the ftp "binary" +(TYPE I) command, or use the +rcp -b command from the mainframe host +(the -b switch is not supported in unix rcp's). + + + Text Documents + +The default assumption of the server is that Text
cvs commit: apache-1.3/htdocs/manual ebcdic.html
martin 98/03/26 08:19:48 Modified:htdocs/manual ebcdic.html Log: typo Revision ChangesPath 1.2 +1 -1 apache-1.3/htdocs/manual/ebcdic.html Index: ebcdic.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/ebcdic.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -u -r1.1 -r1.2 --- ebcdic.html 1998/03/26 15:48:49 1.1 +++ ebcdic.html 1998/03/26 16:19:47 1.2 @@ -13,7 +13,7 @@ ALINK="#FF" > -Overview of Apache EBCDIC Port +Overview of the Apache EBCDIC Port Version 1.3 of the Apache HTTP Server is the first version which
cvs commit: apache-1.3/htdocs/manual ebcdic.html
martin 98/03/26 07:48:50 Added: htdocs/manual ebcdic.html Log: Add a preliminary EBCDIC porting paper (derived from README.EBCDIC) Revision ChangesPath 1.1 apache-1.3/htdocs/manual/ebcdic.html Index: ebcdic.html === The Apache EBCDIC Port Overview of Apache EBCDIC Port Version 1.3 of the Apache HTTP Server is the first version which includes a port to a (non-ASCII) mainframe machine which uses the EBCDIC character set as its native codeset. (It is the SIEMENS NIXDORF family of mainframes running the http://www.sni.de/servers/bs2osd/osdbc_us.htm";>BS2000/OSD operating system. This mainframe OS nowadays features a SVR4-derived POSIX subsystem). The port was started initially to prove the feasibility of porting http://dev.apache.org/";>the Apache HTTP server to this platform find a "worthy and capable" successor for the venerable http://www.w3.org/Daemon/";>CERN-3.0 daemon (which was ported a couple of years ago), and to prove that Apache's preforking process model can on this platform easily outperform the accept-fork-serve model used by CERN by a factor of 5 or more. This document serves as a rationale to describe some of the design decisions of the port to this machine. One objective of the EBCDIC port was to maintain enough backwards compatibility with the (EBCDIC) CERN server to make the transition to the new server attractive and easy. This required the addition of a configurable method to define whether a HTML document was stored in ASCII (the only format accepted by the old server) or in EBCDIC (the native document format in the POSIX subsystem, and therefore the only realistic format in which the other POSIX tools like grep or sed could operate on the documents). The current solution to this is a "pseudo-MIME-format" which is intercepted and interpreted by the Apache server (see below). Future versions might solve the problem by defining an "ebcdic-handler" for all documents which must be converted. Since all Apache input and output is based upon the BUFF data type and its methods, the easiest solution was to add the conversion to the BUFF handling routines. The conversion must be settable at any time, so a BUFF flag was added which defines whether a BUFF object has currently enabled conversion or not. This flag is modified at several points in the HTTP protocol: set before a request is received (because the request and the request header lines are always in ASCII format) set/unset when the request body is received - depending on the content type of the request body (because the request body may contain ASCII text or a binary file) set before a reply header is sent (because the response header lines are always in ASCII format) set/unset when the response body is sent - depending on the content type of the response body (because the response body may contain text or a binary file) Porting Notes The relevant changes in the source are #ifdef'ed into two categories: #ifdef CHARSET_EBCDIC Code which is needed for any EBCDIC based machine. This includes character translations, differences in in contiguity of the two character sets, flags which indicate which part of the HTTP protocol has to be converted and which part doesn't etc. #ifdef _OSD_POSIX Code which is needed for the BS2000 SIEMENS NIXDORF mainframe platform only. This deals with include file differences and socket implementations topics which are only required on the BS2000/OSD platform. The possibility to translate between ASCII and EBCDIC at the socket level (on BS2000 POSIX, there is a socket option which supports this) was intentionally not chosen, because the byte stream at the HTTP protocol level consists of a mixture of protocol related strings and non-protocol related raw file data. HTTP protocol strings are always encoded in ASCII (the GET request, any Header: lines, the chunking information etc.) whereas the file transfer parts (i.e., GIF images, CGI output etc.) should usually be just "passed thru" by the server. This separation between "protocol string" and "raw data" is reflected in the server code by functions like bgets() or rvputs() for strings, and functions like bwrite() for binary data. A global translation of everything would therefore be inadequate. (In the case of text files of course, provisions must be made so
