The Apache EBCDIC Port

Available Languages: en | + ko

+ + +

Warning: This document + has not been updated to take into account changes made in + the 2.0 version of the Apache HTTP Server. Some of the + information may still be relevant, but please use it with care. +

+ +

Overview of the Apache EBCDIC Port
Design Goals
Technical Solution
Porting Notes
Document Storage Notes
Apache Modules' Status
Third Party Modules' Status

Overview of the Apache EBCDIC Port

+ + + +

Version 1.3 of the Apache HTTP Server was the first version + which included a port to a (non-ASCII) mainframe machine which + uses the EBCDIC character set as its native codeset.

+ +

(It is the SIEMENS family of mainframes running the 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 the Apache HTTP server to + this platform
find a "worthy and capable" successor for the venerable + 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.

+ +

Design Goals

+ + + +

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.

+ +

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 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 + 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 SIEMENS BS2000/OSD + mainframe platform only. This deals with include file + differences and socket implementation 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 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 EBCDIC documents are always served in + ASCII)
+
+
This port therefore features a built-in protocol level + conversion for the server-internal strings (which the + compiler translated to EBCDIC strings) and thus for all + server-generated documents. The hard coded ASCII escapes + \012 and \015 which are ubiquitous + in the server code are an exception: they are 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 are not expected to + contain ASCII newline characters.
+
+
By examining the call hierarchy for the BUFF management + 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. 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). 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.
+
+
For Text documents (MIME types text/plain, text/html + etc.), an implicit translation to ASCII can be + used, or (if the users prefer to store some documents in + raw ASCII form for faster serving, or because the files + reside on a NFS-mounted directory tree) can be served + without conversion.
+ +
Example:
+ +
to serve files with the suffix .ahtml as a + raw ASCII text/html document without implicit + conversion (and suffix .ascii as ASCII + text/plain), use the directives:
+ +
+ AddType text/x-ascii-html .ahtml + AddType text/x-ascii-plain .ascii +
+ +
Similarly, any text/foo MIME type can be + served as "raw ASCII" by configuring a MIME type + "text/x-ascii-foo" for it using + AddType.
+
+
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.
+
+
Server parsed files are always assumed to be in native + (i.e., EBCDIC) format as used on the machine, and + are converted after processing.
+
+
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.
+

+ +

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 Files + (i.e., all files whose Content-Type: + starts with text/) are stored in the native + character set of the host, EBCDIC.

+ + + +

Server Side Included Documents

+ + + +

SSI documents must currently be stored in EBCDIC only. + No provision is made to convert it from ASCII before + processing.

+ + + +

Apache Modules' Status

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Module	Status	Notes
`core`	+	+
`mod_access`	+	+
`mod_actions`	+	+
`mod_alias`	+	+
`mod_asis`	+	+
`mod_auth`	+	+
`mod_authn_anon`	+	+
`mod_authn_dbm`	?	with own `libdb.a`
`mod_authz_dbm`	?	with own `libdb.a`
`mod_autoindex`	+	+
`mod_cern_meta`	?	+
`mod_cgi`	+	+
`mod_digest`	+	+
`mod_dir`	+	+
`mod_so`	-	no shared libs
`mod_env`	+	+
`mod_example`	-	(test bed only)
`mod_expires`	+	+
`mod_headers`	+	+
`mod_imagemap`	+	+
`mod_include`	+	+
`mod_info`	+	+
`mod_log_agent`	+	+
`mod_log_config`	+	+
`mod_log_referer`	+	+
`mod_mime`	+	+
`mod_mime_magic`	?	not ported yet
`mod_negotiation`	+	+
`mod_proxy`	+	+
`mod_rewrite`	+	untested
`mod_setenvif`	+	+
`mod_speling`	+	+
`mod_status`	+	+
`mod_unique_id`	+	+
`mod_userdir`	+	+
`mod_usertrack`	?	untested

+ +

Third Party Modules' Status

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Module	Status	Notes
`mod_jserv +`	-	JAVA still being ported.
`mod_php3`	+	`mod_php3` runs fine, with LDAP and GD + and FreeType libraries.
`mod_put`	?	untested
`mod_session`	-	untested

+ +

Available Languages: en | + ko

+ \ No newline at end of file diff --git a/docs/manual/platform/ebcdic.html.ko.euc-kr b/docs/manual/platform/ebcdic.html.ko.euc-kr new file mode 100644 index 00000000000..73a411ca653 --- /dev/null +++ b/docs/manual/platform/ebcdic.html.ko.euc-kr @@ -0,0 +1,559 @@ + + + +¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ - Apache HTTP Server + + + + + +

+Apache > HTTP Server > Documentation > Version 2.5 > Platform Specific Notes

¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ

°¡´ÉÇÑ ¾ð¾î: en | + ko

ÀÌ ¹®¼´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼¸¦ Âü°íÇÏ¼¼¿ä.

+ + +

ÀÌ ¹®¼´Â ¾ÆÆÄÄ¡ À¥¼¹ö 2.0 ¹öÀü¿¡¼ + º¯°æµÈ ³»¿ëÀ» ´ã°íÀÖÁö ¾Ê´Ù. ¾ÆÁ÷µµ À¯È¿ÇÑ Á¤º¸°¡ ÀÖÁö¸¸, + ÁÖÀÇÇØ¼ »ç¿ëÇÏ±æ ¹Ù¶õ´Ù. +

+ +

¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ °³¿ä
¼³°è ¸ñÇ¥
±â¼úÀû ÇØ°áÃ¥
Æ÷ÆÃ¿¡ ´ëÇØ¼
¹®¼ ÀúÀå¿¡ ´ëÇØ¼
¾ÆÆÄÄ¡ ¸ðµâÀÇ »óÅÂ
Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀÇ »óÅÂ

¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ °³¿ä

+ + + +

¾ÆÆÄÄ¡ À¥¼¹ö´Â 1.3 ¹öÀü¶§ Ã³À½À¸·Î EBCDIC ¹®ÀÚÁýÇÕÀ» + ±âº» ¹®ÀÚÁýÇÕÀ¸·Î »ç¿ëÇÏ´Â (ºñ-ASCII) ¸ÞÀÎÇÃ·¹ÀÓ ÄÄÇ»ÅÍ·Î + Æ÷ÆÃµÇ¾ú´Ù.

+ +

(BS2000/OSD + ¿î¿µÃ¼Á¦¸¦ »ç¿ëÇÏ´Â SIEMENS °è¿ ¸ÞÀÎÇÃ·¹ÀÓÀ» ¸»ÇÑ´Ù. + ÀÌ ¸ÞÀÎÇÃ·¹ÀÓ ¿î¿µÃ¼Á¦¿¡´Â ÇöÀç SVR4°è¿ÀÇ POSIX ÇÏÀ§½Ã½ºÅÛÀÌ + ÀÖ´Ù).

+ +

Æ÷ÆÃÀº Ã³À½¿¡ ´ÙÀ½°ú °°Àº ¸ñÀû¿¡¼ ½ÃÀÛµÇ¾ú´Ù

+ +

ÀÌ ÇÃ·¹ÆûÀ¸·Îµµ ¾ÆÆÄÄ¡ + À¥¼¹ö¸¦ Æ÷ÆÃÇÒ ¼ö ÀÖ´Ù´Â °¡´É¼ºÀ» º¸ÀÌ±âÀ§ÇØ¼
(¸î³â Àü¿¡ Æ÷ÆÃµÈ) ¿À·¡µÈ CERN-3.0 ¼¹ö¸¦ ´ëÃ¼ÇÒ + "¾µ¸¸ÇÏ°í À¯´ÉÇÑ" ÈÄ°èÀÚ¸¦ Ã£±âÀ§ÇØ
ÀÌ ÇÃ·¹Æû¿¡¼ ¾ÆÆÄÄ¡ÀÇ prefork ÇÁ·Î¼¼½º ¹æ½ÄÀÌ CERNÀÇ + accept-fork-serve ¹æ½Ä º¸´Ù 5¹è ÀÌ»ó ¼º´ÉÀÌ ÁÁÀ½À» + º¸ÀÌ±âÀ§ÇØ¼.

+ +

ÀÌ ¹®¼´Â Æ÷ÆÃ½Ã ¿©·¯ ¼³°è»ó °áÁ¤ÀÇ ÀÌÀ¯¸¦ ¼³¸íÇÑ´Ù.

+ +

¼³°è ¸ñÇ¥

+ + + +

EBCDIC Æ÷ÆÃÀÇ ¸ñÀûÁß ÇÏ³ª´Â »õ·Î¿î ¼¹ö·Î ÀüÈ¯À» À¯µµÇÏ°í + ½±°Ô ÀüÈ¯ÇÒ ¼ö ÀÖµµ·Ï °¡´ÉÇÑ (EBCDIC) CERN ¼¹ö¿Í È£È¯¼ºÀ» + À¯ÁöÇÏ´Â °ÍÀÌ´Ù. ±×·¡¼ HTML ¹®¼°¡ (ÀÌÀü CERN ¼¹ö°¡ ÀÎ½ÄÇÏ´Â + À¯ÀÏÇÑ Çü½ÄÀÎ) ASCII¿Í (POSIX ÇÏÀ§½Ã½ºÅÛÀÇ ±âº» ¹®¼ Çü½Ä. + ±×·¯¹Ç·Î grepÀÌ³ª sed °°Àº POSIX + µµ±¸¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Â Çö½ÇÀûÀÎ Çü½ÄÀÎ) EBCDIC Áß ¾î´À Çü½ÄÀÎÁö + ¼³Á¤ÇÒ ¼ö ÀÖ¾î¾ß ÇÑ´Ù. ÇöÀç ÇØ°áÃ¥Àº ¾ÆÆÄÄ¡ ¼¹ö°¡ Áß°£¿¡¼ + ¹®¼¸¦ °¡·ÎÃ¤¼ ¹®¼ÀÇ Çü½ÄÀ» ÆÄ¾ÇÇÏ´Â "°¡»ó MIME Çü½Ä"ÀÌ´Ù + (¾Æ·¡ Âü°í). ´ÙÀ½ ¹öÀü¿¡¼´Â º¯È¯ÇØ¾ßÇÒ ¸ðµç ¹®¼¿¡ + "ebcdic-handler"¸¦ Á¤ÀÇÇÏ´Â ¹æ¹ýÀ¸·Î ¹®Á¦¸¦ ÇØ°áÇÒ °ÍÀÌ´Ù.

+ +

±â¼úÀû ÇØ°áÃ¥

+ + + +

¾ÆÆÄÄ¡°¡ BUFF ÀÚ·áÇü°ú ¸Þ½áµå¸¦ »ç¿ëÇÏ¿© ¸ðµç ÀÔÃâ·ÂÀ» + ÇÏ¹Ç·Î °¡Àå ½¬¿î ¹æ¹ýÀº BUFF Ã³¸® ÇÔ¼ö¿¡ º¯È¯±â´ÉÀ» Ãß°¡ÇÏ´Â + °ÍÀÌ´Ù. ¾ðÁ¦µçÁö º¯È¯ÇÒ ¼ö ÀÖ¾î¾ß ÇÏ±â¶§¹®¿¡ BUFF °´Ã¼¸¦ + º¯È¯ÇØ¾ß ÇÏ´ÂÁö ¾Ë·ÁÁÖ´Â BUFF Ç¥½Ã¸¦ Ãß°¡Çß´Ù. ÀÌ Ç¥½Ã´Â + HTTP ÇÁ·ÎÅäÄÝÀÇ ¿©·¯ ´Ü°è¿¡¼ º¯°æµÉ ¼ö ÀÖ´Ù:

+ +

¿äÃ»À» ¹Þ±â Àü¿¡ º¯È¯ (¿äÃ»°ú ¿äÃ»Çì´õ°¡ + Ç×»ó ASCII Çü½ÄÀÌ±â ¶§¹®¿¡)
¿äÃ» ³»¿ëÀ» ¹Þ¾ÒÀ»¶§ content type¿¡ µû¶ó + º¯È¯/º¯È¯¾ÈÇÔ (¿äÃ» ³»¿ëÀÌ ASCII ¹®ÀÚ³ª + ¹ÙÀÌ³Ê¸® ÆÄÀÏÀÎ °æ¿ì º¯È¯ÇØ¾ß ÇÏ±â¶§¹®¿¡)
ÀÀ´äÇì´õ¸¦ º¸³»±â Àü¿¡ º¯È¯ (ÀÀ´äÇì´õ´Â + Ç×»ó ASCII Çü½ÄÀÌ±â¶§¹®¿¡)
ÀÀ´ä ³»¿ëÀ» º¸³¾¶§ content type¿¡ µû¶ó + º¯È¯/º¯È¯¾ÈÇÔ (ÀÀ´ä ³»¿ëÀÌ ¹®ÀÚ ÆÄÀÏÀÌ°Å³ª + ¹ÙÀÌ³Ê¸® ÆÄÀÏÀÌ±â¶§¹®¿¡)

+ +

Æ÷ÆÃ¿¡ ´ëÇØ¼

+ + + +

+
¼Ò½ºÀÇ º¯È´Â µÎ°¡Áö #ifdef·Î ±¸ºÐÇÒ + ¼ö ÀÖ´Ù:
+ +
+
#ifdef + CHARSET_EBCDIC
+ +
+
¸ðµç EBCDIC±â¹Ý ÄÄÇ»ÅÍ¿¡ ÇÊ¿äÇÑ ÄÚµå. ¹®ÀÚº¯È¯, + µÎ ¹®ÀÚÁýÇÕ°£ÀÇ ¿¬¼ÓµÈ ¹®ÀÚ°ª Â÷ÀÌ, ¾î¶² HTTP ÇÁ·ÎÅäÄÝ + ºÎºÐÀÌ º¯È¯µÇ¾ß ÇÏ´ÂÁö¸¦ ¾Ë·ÁÁÖ´Â Ç¥½Ã µî.
+
+ +
#ifdef _OSD_POSIX
+ +
+
SIEMENS BS2000/OSD ¸ÞÀÎÇÃ·¹ÀÓ ÇÃ·¹Æû¿¡¸¸ ÇÊ¿äÇÑ + ÄÚµå. BS2000/OSD ÇÃ·¹Æû¿¡¸¸ ÇÊ¿äÇÑ Çì´õÆÄÀÏ Â÷ÀÌ¿Í + ¼ÒÄÏ ±¸Çö ¹®Á¦¸¦ ´Ù·é´Ù.
+
+
+
+
¼ÒÄÏ ¼öÁØ¿¡¼ ASCII¿Í EBCDIC°£ º¯È´Â (BS2000 POSIX¿¡´Â + ÀÌ ±â´ÉÀ» Áö¿øÇÏ´Â ¼ÒÄÏ ¿É¼ÇÀÌ ÀÖ´Ù) HTTP ÇÁ·ÎÅäÄÝ ¼öÁØ¿¡¼ + Àü¼ÛµÇ´Â ÀÚ·á¿¡ ÇÁ·ÎÅäÄÝ°ü·Ã ¹®ÀÚ¿°ú ÇÁ·ÎÅäÄÝ°ú ¹«°üÇÑ + ÀÏ¹ÝÆÄÀÏÀÌ ¼¯¿©ÀÖ±â¶§¹®¿¡ ÀÇµµÀûÀ¸·Î »ç¿ëÇÏÁö + ¾Ê¾Ò´Ù. HTTP ÇÁ·ÎÅäÄÝ ¹®ÀÚ¿Àº (GET + ¿äÃ», Header: ÁÙ, ±âÅ¸ Á¤º¸ µî.) Ç×»ó ASCII + Çü½ÄÀÌ°í, ÆÄÀÏÀü¼Û ºÎºÐÀº (Áï, GIF ±×¸², CGI + Ãâ·Â µî.) ¼¹ö°¡ Ç×»ó "º¯È¯ÇÏÁö¾Ê°í ±×³É" º¸³»¾ß + ÇÑ´Ù. ¼¹ö ÄÚµå´Â "ÇÁ·ÎÅäÄÝ ¹®ÀÚ¿"°ú "ÀÏ¹Ý ÀÚ·á"¸¦, + ¹®ÀÚ¿¿¡´Â bgets()³ª rvputs(), + ¹ÙÀÌ³Ê¸® ÀÚ·á¿¡´Â bgets()³ª + rvputs() ÇÔ¼ö¸¦ »ç¿ëÇÏ¿© ±¸º°ÇÑ´Ù. ±×·¯¹Ç·Î + ¹«Á¶°Ç ¸ðµç °ÍÀ» º¯È¯ÇÏ´Â °ÍÀº ÀûÀýÇÏÁö ¾Ê´Ù.
+ +
(¹°·Ð ¹®ÀÚÆÄÀÏÀÇ °æ¿ì EBCDIC ¹®¼¸¦ Ç×»ó ASCII·Î + ¼ºñ½ºÇÏµµ·Ï ÁØºñÇØ¾ß ÇÑ´Ù)
+
+
±×·¡¼ Æ÷ÆÃ¿¡´Â (ÄÄÆÄÀÏ·¯°¡ EBCDIC ¹®ÀÚ¿·Î º¯È¯ÇÑ) + ¼¹ö ³»ºÎ ¹®ÀÚ¿°ú ¼¹ö°¡ »ý¼ºÇÑ ¹®¼¸¦ ±âº» ÇÁ·ÎÅäÄÝ + ¼öÁØ¿¡¼ º¯È¯ÇÏ´Â ±â´ÉÀÌ ÀÖ´Ù. ¼¹ö ÄÚµå¿¡ »êÀçµÈ ASCII + escape¹®ÀÚ \012¿Í \015´Â ¿¹¿Ü´Ù: + ÀÌµéÀÌ ÀÌ¹Ì ASCII \n°ú \rÀÇ + ¹ÙÀÌ³Ê¸® °ªÀÌ±â¶§¹®¿¡ ASCII·Î µÎ¹ø º¯È¯ÇÏ¸é ¾ÈµÈ´Ù. + ÀÌ ¿¹¿Ü´Â ¼¹ö°¡ »ý¼ºÇÑ ¹®ÀÚ¿¿¡¸¸ Àû¿ëµÈ´Ù; ¿ÜºÎ + EBCDIC ¹®¼´Â ASCII ÁÙ¹Ù²Þ¹®ÀÚ¸¦ Æ÷ÇÔÇÏ¸é ¾ÈµÈ´Ù.
+
+
BUFF °ü¸®ÇÔ¼ö¸¦ »ç¿ëÇÏ´Â ¹æ¹ýÀ» »ìÆìº» ÈÄ ³ª´Â ¸ðµç + puts/write/get/gets°¡ °ÅÄ¡°ÔµÇ´Â "ebcdic/ascii º¯È¯ + °èÃþ"À» Ãß°¡ÇÏ°í, µ¿ÀûÀ¸·Î º¯È¯À¯¹«¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Â + º¯È¯ Ç¥½Ã¸¦ Ãß°¡Çß´Ù. ¹®¼°¡ ¿øº»(ÆÄÀÏÀÌ³ª CGI Ãâ·Â)¿¡¼ + ´ë»ó(¿äÃ»ÇÑ Å¬¶óÀÌ¾ðÆ®)À¸·Î ÀÌµ¿ÇÒ¶§ Ç×»ó ÀÌ °èÃþÀ» + µÎ¹ø Áö³´Ù: ÆÄÀÏ -> ¾ÆÆÄÄ¡, ¾ÆÆÄÄ¡ + -> Å¬¶óÀÌ¾ðÆ®.
+ +
¼¹ö´Â ÀÌÁ¦ EBCDIC Çü½ÄÀ¸·Î µÈ CGI ½ºÅ©¸³Æ® Ãâ·ÂÀÇ + Çì´õÁÙÀ» ÀÐ°í, ³ª¸ÓÁö ½ºÅ©¸³Æ® Ãâ·ÂÀÌ ASCIIÀÓÀ» ¾Ë¾Æ³¾ + ¼ö ÀÖ´Ù (WWW ¹æ¹®ÀÚ¼ö¸¦ ¼¼´Â ÇÁ·Î±×·¥°ú °°Àº °æ¿ì: ¹®¼ + ³»¿ëÀº GIF ±×¸²ÀÌ´Ù). ±âº» EBCDIC Çü½ÄÀ¸·Î ¸ðµç Çì´õ¸¦ + Ã³¸®ÇÑ´Ù; ±×·± ´ÙÀ½ ¼ºñ½ºÇÒ ¹®¼ÀÇ type¿¡ µû¶ó ¼¹ö´Â + ¹®¼ ³»¿ëÀÌ ÀÌ¹Ì ASCIIÀÎÁö È¤Àº EBCDIC¿¡¼ º¯È¯À» ÇØ¾ß + ÇÏ´ÂÁö °áÁ¤ÇÑ´Ù.
+
+
(MIME typeÀÌ text/plain, text/html µî) ³»¿ëÀÌ + ÀÏ¹Ý ¹®ÀÚÀÎ ¹®¼¸¦ ¾Ï¹¬ÀûÀ¸·Î ASCII·Î º¯È¯ÇÏ°Å³ª, (»ç¿ëÀÚ¿¡°Ô + ºü¸£°Ô ¼ºñ½ºÇÏ±âÀ§ÇØ ¹Ì¸® ¹®¼¸¦ ASCII Çü½ÄÀ¸·Î ÀúÀåÇÏ¿´°Å³ª + NFS·Î ¸¶¿îÆ®ÇÑ µð·ºÅä¸®¿¡ ÆÄÀÏÀÌ ÀÖ´Â °æ¿ì) º¯È¯¾øÀÌ + ¼ºñ½ºÇÒ ¼ö ÀÖ´Ù.
+ +
¿¹:
+ +
ÀÌ¸§ÀÌ .ahtml·Î ³¡³ª´Â ÆÄÀÏÀ» ¾Ï¹¬ÀûÀÎ + º¯È¯¾øÀÌ ASCII text/html ¹®¼·Î (±×¸®°í + .ascii È®ÀåÀÚ´Â ASCII + text/plainÀ¸·Î) ¼ºñ½ºÇÏ·Á¸é ´ÙÀ½ Áö½Ã¾î¸¦ + »ç¿ëÇÑ´Ù:
+ +
+ AddType text/x-ascii-html .ahtml + AddType text/x-ascii-plain .ascii +
+ +
¶Ç, text/foo ½ÄÀÇ MIME typeÀ» + AddType "text/x-ascii-foo" + ¼³Á¤ÇÏ¿© "ÀÏ¹Ý ASCII"·Î ¼ºñ½ºÇÒ ¼ö ÀÖ´Ù.
+
+
³»¿ëÀÌ ÀÏ¹Ý ¹®ÀÚ°¡ ¾Æ´Ñ ¹®¼´Â º¯È¯¾øÀÌ Ç×»ó "¹ÙÀÌ³Ê¸®"·Î + ¼ºñ½ºÇÑ´Ù. ¿¹¸¦ µé¾î, GIF/ZIP/AU ÆÄÀÏÇü½Ä¿¡ + °¡Àå ÀûÇÕÇÑ ¼±ÅÃÀÌ´Ù. ¹°·Ð »ç¿ëÀÚ´Â "rcp -b" + ¹ÙÀÌ³Ê¸® ¿É¼ÇÀ» »ç¿ëÇÏ¿© ÆÄÀÏÀ» ¸ÞÀÎÇÃ·¹ÀÓ È£½ºÆ®·Î + º¹»çÇß¾î¾ß ÇÑ´Ù.
+
+
¼¹öÆÄ½Ì ÆÄÀÏÀº Ç×»ó ÄÄÇ»ÅÍ°¡ »ç¿ëÇÏ´Â ±âº» Çü½ÄÀ¸·Î + (Áï, EBCDIC) ÀúÀåµÇ¾ú´Ù°í °¡Á¤ÇÏ°í, Ã³¸®ÈÄ¿¡ + º¯È¯ÇÑ´Ù.
+
+
CGI Ãâ·ÂÀÇ °æ¿ì CGI ½ºÅ©¸³Æ®°¡ º¯È¯ÀÌ ÇÊ¿äÇÑÁö °áÁ¤ÇÑ´Ù: + ÀûÀýÇÑ Content-TypeÀ» ¼³Á¤ÇÏ¿©, ¹®ÀÚÆÄÀÏÀº º¯È¯ÇÏ°í, + GIF Ãâ·ÂÀº º¯È¯¾øÀÌ º¸³¾ ¼ö ÀÖ´Ù. ¿ì¸®°¡ Æ÷ÆÃÇÑ wwwcount + ÇÁ·Î±×·¥ÀÌ ÈÄÀÚÀÇ °æ¿ì´Ù.
+

+ +

¹®¼ ÀúÀå¿¡ ´ëÇØ¼

+ + + +

¹ÙÀÌ³Ê¸® ÆÄÀÏ

+ + + +

¼¹ö´Â Content-Type:ÀÌ text/·Î + ½ÃÀÛÇÏ´Â ¾Ê´Â ÆÄÀÏÀ» ¹ÙÀÌ³Ê¸® ÆÄÀÏ·Î °£ÁÖÇÏ¿© + ¾î¶² º¯È¯µµ ÇÏÁö ¾Ê´Â´Ù. ¹ÙÀÌ³Ê¸® ÆÄÀÏ¿¡´Â GIF ±×¸², gzipÀ¸·Î + ¾ÐÃàÇÑ ÆÄÀÏ µîÀÌ ÀÖ´Ù.

+ +

¸ÞÀÎÇÃ·¹ÀÓ È£½ºÆ®¿Í À¯´Ð½º È¤Àº À©µµ¿ìÁî PC°£¿¡ ¹ÙÀÌ³Ê¸® + ÆÄÀÏÀ» Àü¼ÛÇÒ ¶§´Â ftp "binary" (TYPE I) ¸í·É¾î³ª + ¸ÞÀÎÇÃ·¹ÀÓ È£½ºÆ®¿¡¼ (À¯´Ð½º rcp´Â + -b ¿É¼ÇÀ» Áö¿øÇÏÁö ¾Ê´Â´Ù) rcp -b + ¸í·É¾î¸¦ ¹Ýµå½Ã »ç¿ëÇÏ¶ó.

+ + + +

¹®ÀÚ ¹®¼

+ + + +

±âº»ÀûÀ¸·Î ¼¹ö´Â ¹®ÀÚÆÄÀÏÀÌ (Áï, + Content-Type:ÀÌ text/·Î ½ÃÀÛÇÏ´Â + ¸ðµç ÆÄÀÏ) È£½ºÆ®ÀÇ ±âº» ¹®ÀÚÁýÇÕÀÎ EBCDICÀ¸·Î ÀúÀåµÇ¾ú´Ù°í + °¡Á¤ÇÑ´Ù.

+ + + +

Server Side Include ¹®¼

+ + + +

SSI ¹®¼´Â ÇöÀç EBCDIC Çü½ÄÀ¸·Î¸¸ ÀúÀåÇØ¾ß ÇÑ´Ù. Ã³¸®ÇÏ±â + Àü¿¡ ASCII¸¦ º¯È¯ÇÏÁö ¾Ê´Â´Ù.

+ + + +

¾ÆÆÄÄ¡ ¸ðµâÀÇ »óÅÂ

¸ðµâ	»óÅÂ	ºñ°í
`core`	+	+
`mod_access`	+	+
`mod_actions`	+	+
`mod_alias`	+	+
`mod_asis`	+	+
`mod_auth`	+	+
`mod_auth_anon`	+	+
`mod_auth_dbm`	?	ÀÚÃ¼ `libdb.a`¸¦ »ç¿ëÇÏ¿©
`mod_autoindex`	+	+
`mod_cern_meta`	?	+
`mod_cgi`	+	+
`mod_digest`	+	+
`mod_dir`	+	+
`mod_so`	-	°øÀ¯¶óÀÌºê·¯¸®°¡ ¾øÀ½
`mod_env`	+	+
`mod_example`	-	(½ÃÇè ´Ü°è)
`mod_expires`	+	+
`mod_headers`	+	+
`mod_imagemap`	+	+
`mod_include`	+	+
`mod_info`	+	+
`mod_log_agent`	+	+
`mod_log_config`	+	+
`mod_log_referer`	+	+
`mod_mime`	+	+
`mod_mime_magic`	?	¾ÆÁ÷ Æ÷ÆÃ¾ÈµÊ
`mod_negotiation`	+	+
`mod_proxy`	+	+
`mod_rewrite`	+	Å×½ºÆ®¾ÈµÊ
`mod_setenvif`	+	+
`mod_speling`	+	+
`mod_status`	+	+
`mod_unique_id`	+	+
`mod_userdir`	+	+
`mod_usertrack`	?	Å×½ºÆ®¾ÈµÊ

+ +

Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀÇ »óÅÂ

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

¸ðµâ	»óÅÂ	ºñ°í
`mod_jserv +`	-	JAVA´Â Æ÷ÆÃÁßÀÌ´Ù.
`mod_php3`	+	`mod_php3`´Â LDAP, GD, FreeType ¶óÀÌºê·¯¸®¿Í + ÇÔ²² Àß µ¿ÀÛÇÑ´Ù.
`mod_put`	?	Å×½ºÆ®¾ÈµÊ
`mod_session`	-	Å×½ºÆ®¾ÈµÊ

+ +

°¡´ÉÇÑ ¾ð¾î: en | + ko

+ \ No newline at end of file diff --git a/docs/manual/platform/ebcdic.xml b/docs/manual/platform/ebcdic.xml new file mode 100644 index 00000000000..7a355fb063d --- /dev/null +++ b/docs/manual/platform/ebcdic.xml @@ -0,0 +1,585 @@ + + + + + + + + + Platform Specific Notes + + The Apache EBCDIC Port + +

+ + Warning: This document + has not been updated to take into account changes made in + the 2.0 version of the Apache HTTP Server. Some of the + information may still be relevant, but please use it with care. + + +

+ +

+ + Overview of the Apache EBCDIC Port + +

Version 1.3 of the Apache HTTP Server was the first version + which included a port to a (non-ASCII) mainframe machine which + uses the EBCDIC character set as its native codeset.

+ +

(It is the SIEMENS family of mainframes running the 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 the Apache HTTP server to + this platform
find a "worthy and capable" successor for the venerable + 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.

+ +

+ + Design Goals + +

+ +

+ + Technical Solution + +

+ +

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 + 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 SIEMENS BS2000/OSD + mainframe platform only. This deals with include file + differences and socket implementation 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 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 EBCDIC documents are always served in + ASCII)
+
+
This port therefore features a built-in protocol level + conversion for the server-internal strings (which the + compiler translated to EBCDIC strings) and thus for all + server-generated documents. The hard coded ASCII escapes + \012 and \015 which are ubiquitous + in the server code are an exception: they are 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 are not expected to + contain ASCII newline characters.
+
+
By examining the call hierarchy for the BUFF management + 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. 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). 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.
+
+
For Text documents (MIME types text/plain, text/html + etc.), an implicit translation to ASCII can be + used, or (if the users prefer to store some documents in + raw ASCII form for faster serving, or because the files + reside on a NFS-mounted directory tree) can be served + without conversion.
+ +
Example:
+ +
to serve files with the suffix .ahtml as a + raw ASCII text/html document without implicit + conversion (and suffix .ascii as ASCII + text/plain), use the directives:
+ + + AddType text/x-ascii-html .ahtml
+ AddType text/x-ascii-plain .ascii + + +
Similarly, any text/foo MIME type can be + served as "raw ASCII" by configuring a MIME type + "text/x-ascii-foo" for it using + AddType.
+
+
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.
+
+
Server parsed files are always assumed to be in native + (i.e., EBCDIC) format as used on the machine, and + are converted after processing.
+
+
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.
+

+ +

+ + Document Storage Notes + +

+ + Binary Files + +

+ +

+ + Text Documents + +

The default assumption of the server is that Text Files + (i.e., all files whose Content-Type: + starts with text/) are stored in the native + character set of the host, EBCDIC.

+ +

+ + Server Side Included Documents + +

SSI documents must currently be stored in EBCDIC only. + No provision is made to convert it from ASCII before + processing.

+ +

+ + Apache Modules' Status + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Module	Status	Notes
core	+
mod_access	+
mod_actions	+
mod_alias	+
mod_asis	+
mod_auth	+
mod_authn_anon	+
mod_authn_dbm	?	with own `libdb.a`
mod_authz_dbm	?	with own `libdb.a`
mod_autoindex	+
mod_cern_meta	?
mod_cgi	+
`mod_digest`	+
mod_dir	+
mod_so	-	no shared libs
mod_env	+
mod_example	-	(test bed only)
mod_expires	+
mod_headers	+
mod_imagemap	+
mod_include	+
mod_info	+
`mod_log_agent`	+
`mod_log_config`	+
mod_log_referer	+
mod_mime	+
mod_mime_magic	?	not ported yet
mod_negotiation	+
mod_proxy	+
mod_rewrite	+	untested
mod_setenvif	+
mod_speling	+
mod_status	+
mod_unique_id	+
mod_userdir	+
mod_usertrack	?	untested

+ +

+ + Third Party Modules' Status + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Module	Status	Notes
`mod_jserv +`	-	JAVA still being ported.
`mod_php3`	+	`mod_php3` runs fine, with LDAP and GD + and FreeType libraries.
`mod_put`	?	untested
`mod_session`	-	untested

+ +

+ + diff --git a/docs/manual/platform/ebcdic.xml.ko b/docs/manual/platform/ebcdic.xml.ko new file mode 100644 index 00000000000..1c59685551b --- /dev/null +++ b/docs/manual/platform/ebcdic.xml.ko @@ -0,0 +1,552 @@ + + + + + + + + + Platform Specific Notes + + ¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ + +

+ + ÀÌ ¹®¼´Â ¾ÆÆÄÄ¡ À¥¼¹ö 2.0 ¹öÀü¿¡¼ + º¯°æµÈ ³»¿ëÀ» ´ã°íÀÖÁö ¾Ê´Ù. ¾ÆÁ÷µµ À¯È¿ÇÑ Á¤º¸°¡ ÀÖÁö¸¸, + ÁÖÀÇÇØ¼ »ç¿ëÇÏ±æ ¹Ù¶õ´Ù. + + +

+ +

+ + ¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ °³¿ä + +

+ +

Æ÷ÆÃÀº Ã³À½¿¡ ´ÙÀ½°ú °°Àº ¸ñÀû¿¡¼ ½ÃÀÛµÇ¾ú´Ù

+ +

ÀÌ ÇÃ·¹ÆûÀ¸·Îµµ ¾ÆÆÄÄ¡ + À¥¼¹ö¸¦ Æ÷ÆÃÇÒ ¼ö ÀÖ´Ù´Â °¡´É¼ºÀ» º¸ÀÌ±âÀ§ÇØ¼
(¸î³â Àü¿¡ Æ÷ÆÃµÈ) ¿À·¡µÈ CERN-3.0 ¼¹ö¸¦ ´ëÃ¼ÇÒ + "¾µ¸¸ÇÏ°í À¯´ÉÇÑ" ÈÄ°èÀÚ¸¦ Ã£±âÀ§ÇØ
ÀÌ ÇÃ·¹Æû¿¡¼ ¾ÆÆÄÄ¡ÀÇ prefork ÇÁ·Î¼¼½º ¹æ½ÄÀÌ CERNÀÇ + accept-fork-serve ¹æ½Ä º¸´Ù 5¹è ÀÌ»ó ¼º´ÉÀÌ ÁÁÀ½À» + º¸ÀÌ±âÀ§ÇØ¼.

+ +

+ + ¼³°è ¸ñÇ¥ + +

+ +

+ + ±â¼úÀû ÇØ°áÃ¥ + +

+ +

¿äÃ»À» ¹Þ±â Àü¿¡ º¯È¯ (¿äÃ»°ú ¿äÃ»Çì´õ°¡ + Ç×»ó ASCII Çü½ÄÀÌ±â ¶§¹®¿¡)
¿äÃ» ³»¿ëÀ» ¹Þ¾ÒÀ»¶§ content type¿¡ µû¶ó + º¯È¯/º¯È¯¾ÈÇÔ (¿äÃ» ³»¿ëÀÌ ASCII ¹®ÀÚ³ª + ¹ÙÀÌ³Ê¸® ÆÄÀÏÀÎ °æ¿ì º¯È¯ÇØ¾ß ÇÏ±â¶§¹®¿¡)
ÀÀ´äÇì´õ¸¦ º¸³»±â Àü¿¡ º¯È¯ (ÀÀ´äÇì´õ´Â + Ç×»ó ASCII Çü½ÄÀÌ±â¶§¹®¿¡)
ÀÀ´ä ³»¿ëÀ» º¸³¾¶§ content type¿¡ µû¶ó + º¯È¯/º¯È¯¾ÈÇÔ (ÀÀ´ä ³»¿ëÀÌ ¹®ÀÚ ÆÄÀÏÀÌ°Å³ª + ¹ÙÀÌ³Ê¸® ÆÄÀÏÀÌ±â¶§¹®¿¡)

+ +

+ + Æ÷ÆÃ¿¡ ´ëÇØ¼ + +

+
¼Ò½ºÀÇ º¯È´Â µÎ°¡Áö #ifdef·Î ±¸ºÐÇÒ + ¼ö ÀÖ´Ù:
+ +
+
#ifdef + CHARSET_EBCDIC
+ +
+
¸ðµç EBCDIC±â¹Ý ÄÄÇ»ÅÍ¿¡ ÇÊ¿äÇÑ ÄÚµå. ¹®ÀÚº¯È¯, + µÎ ¹®ÀÚÁýÇÕ°£ÀÇ ¿¬¼ÓµÈ ¹®ÀÚ°ª Â÷ÀÌ, ¾î¶² HTTP ÇÁ·ÎÅäÄÝ + ºÎºÐÀÌ º¯È¯µÇ¾ß ÇÏ´ÂÁö¸¦ ¾Ë·ÁÁÖ´Â Ç¥½Ã µî.
+
+ +
#ifdef _OSD_POSIX
+ +
+
SIEMENS BS2000/OSD ¸ÞÀÎÇÃ·¹ÀÓ ÇÃ·¹Æû¿¡¸¸ ÇÊ¿äÇÑ + ÄÚµå. BS2000/OSD ÇÃ·¹Æû¿¡¸¸ ÇÊ¿äÇÑ Çì´õÆÄÀÏ Â÷ÀÌ¿Í + ¼ÒÄÏ ±¸Çö ¹®Á¦¸¦ ´Ù·é´Ù.
+
+
+
+
¼ÒÄÏ ¼öÁØ¿¡¼ ASCII¿Í EBCDIC°£ º¯È´Â (BS2000 POSIX¿¡´Â + ÀÌ ±â´ÉÀ» Áö¿øÇÏ´Â ¼ÒÄÏ ¿É¼ÇÀÌ ÀÖ´Ù) HTTP ÇÁ·ÎÅäÄÝ ¼öÁØ¿¡¼ + Àü¼ÛµÇ´Â ÀÚ·á¿¡ ÇÁ·ÎÅäÄÝ°ü·Ã ¹®ÀÚ¿°ú ÇÁ·ÎÅäÄÝ°ú ¹«°üÇÑ + ÀÏ¹ÝÆÄÀÏÀÌ ¼¯¿©ÀÖ±â¶§¹®¿¡ ÀÇµµÀûÀ¸·Î »ç¿ëÇÏÁö + ¾Ê¾Ò´Ù. HTTP ÇÁ·ÎÅäÄÝ ¹®ÀÚ¿Àº (GET + ¿äÃ», Header: ÁÙ, ±âÅ¸ Á¤º¸ µî.) Ç×»ó ASCII + Çü½ÄÀÌ°í, ÆÄÀÏÀü¼Û ºÎºÐÀº (Áï, GIF ±×¸², CGI + Ãâ·Â µî.) ¼¹ö°¡ Ç×»ó "º¯È¯ÇÏÁö¾Ê°í ±×³É" º¸³»¾ß + ÇÑ´Ù. ¼¹ö ÄÚµå´Â "ÇÁ·ÎÅäÄÝ ¹®ÀÚ¿"°ú "ÀÏ¹Ý ÀÚ·á"¸¦, + ¹®ÀÚ¿¿¡´Â bgets()³ª rvputs(), + ¹ÙÀÌ³Ê¸® ÀÚ·á¿¡´Â bgets()³ª + rvputs() ÇÔ¼ö¸¦ »ç¿ëÇÏ¿© ±¸º°ÇÑ´Ù. ±×·¯¹Ç·Î + ¹«Á¶°Ç ¸ðµç °ÍÀ» º¯È¯ÇÏ´Â °ÍÀº ÀûÀýÇÏÁö ¾Ê´Ù.
+ +
(¹°·Ð ¹®ÀÚÆÄÀÏÀÇ °æ¿ì EBCDIC ¹®¼¸¦ Ç×»ó ASCII·Î + ¼ºñ½ºÇÏµµ·Ï ÁØºñÇØ¾ß ÇÑ´Ù)
+
+
±×·¡¼ Æ÷ÆÃ¿¡´Â (ÄÄÆÄÀÏ·¯°¡ EBCDIC ¹®ÀÚ¿·Î º¯È¯ÇÑ) + ¼¹ö ³»ºÎ ¹®ÀÚ¿°ú ¼¹ö°¡ »ý¼ºÇÑ ¹®¼¸¦ ±âº» ÇÁ·ÎÅäÄÝ + ¼öÁØ¿¡¼ º¯È¯ÇÏ´Â ±â´ÉÀÌ ÀÖ´Ù. ¼¹ö ÄÚµå¿¡ »êÀçµÈ ASCII + escape¹®ÀÚ \012¿Í \015´Â ¿¹¿Ü´Ù: + ÀÌµéÀÌ ÀÌ¹Ì ASCII \n°ú \rÀÇ + ¹ÙÀÌ³Ê¸® °ªÀÌ±â¶§¹®¿¡ ASCII·Î µÎ¹ø º¯È¯ÇÏ¸é ¾ÈµÈ´Ù. + ÀÌ ¿¹¿Ü´Â ¼¹ö°¡ »ý¼ºÇÑ ¹®ÀÚ¿¿¡¸¸ Àû¿ëµÈ´Ù; ¿ÜºÎ + EBCDIC ¹®¼´Â ASCII ÁÙ¹Ù²Þ¹®ÀÚ¸¦ Æ÷ÇÔÇÏ¸é ¾ÈµÈ´Ù.
+
+
BUFF °ü¸®ÇÔ¼ö¸¦ »ç¿ëÇÏ´Â ¹æ¹ýÀ» »ìÆìº» ÈÄ ³ª´Â ¸ðµç + puts/write/get/gets°¡ °ÅÄ¡°ÔµÇ´Â "ebcdic/ascii º¯È¯ + °èÃþ"À» Ãß°¡ÇÏ°í, µ¿ÀûÀ¸·Î º¯È¯À¯¹«¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Â + º¯È¯ Ç¥½Ã¸¦ Ãß°¡Çß´Ù. ¹®¼°¡ ¿øº»(ÆÄÀÏÀÌ³ª CGI Ãâ·Â)¿¡¼ + ´ë»ó(¿äÃ»ÇÑ Å¬¶óÀÌ¾ðÆ®)À¸·Î ÀÌµ¿ÇÒ¶§ Ç×»ó ÀÌ °èÃþÀ» + µÎ¹ø Áö³´Ù: ÆÄÀÏ -> ¾ÆÆÄÄ¡, ¾ÆÆÄÄ¡ + -> Å¬¶óÀÌ¾ðÆ®.
+ +
¼¹ö´Â ÀÌÁ¦ EBCDIC Çü½ÄÀ¸·Î µÈ CGI ½ºÅ©¸³Æ® Ãâ·ÂÀÇ + Çì´õÁÙÀ» ÀÐ°í, ³ª¸ÓÁö ½ºÅ©¸³Æ® Ãâ·ÂÀÌ ASCIIÀÓÀ» ¾Ë¾Æ³¾ + ¼ö ÀÖ´Ù (WWW ¹æ¹®ÀÚ¼ö¸¦ ¼¼´Â ÇÁ·Î±×·¥°ú °°Àº °æ¿ì: ¹®¼ + ³»¿ëÀº GIF ±×¸²ÀÌ´Ù). ±âº» EBCDIC Çü½ÄÀ¸·Î ¸ðµç Çì´õ¸¦ + Ã³¸®ÇÑ´Ù; ±×·± ´ÙÀ½ ¼ºñ½ºÇÒ ¹®¼ÀÇ type¿¡ µû¶ó ¼¹ö´Â + ¹®¼ ³»¿ëÀÌ ÀÌ¹Ì ASCIIÀÎÁö È¤Àº EBCDIC¿¡¼ º¯È¯À» ÇØ¾ß + ÇÏ´ÂÁö °áÁ¤ÇÑ´Ù.
+
+
(MIME typeÀÌ text/plain, text/html µî) ³»¿ëÀÌ + ÀÏ¹Ý ¹®ÀÚÀÎ ¹®¼¸¦ ¾Ï¹¬ÀûÀ¸·Î ASCII·Î º¯È¯ÇÏ°Å³ª, (»ç¿ëÀÚ¿¡°Ô + ºü¸£°Ô ¼ºñ½ºÇÏ±âÀ§ÇØ ¹Ì¸® ¹®¼¸¦ ASCII Çü½ÄÀ¸·Î ÀúÀåÇÏ¿´°Å³ª + NFS·Î ¸¶¿îÆ®ÇÑ µð·ºÅä¸®¿¡ ÆÄÀÏÀÌ ÀÖ´Â °æ¿ì) º¯È¯¾øÀÌ + ¼ºñ½ºÇÒ ¼ö ÀÖ´Ù.
+ +
¿¹:
+ +
ÀÌ¸§ÀÌ .ahtml·Î ³¡³ª´Â ÆÄÀÏÀ» ¾Ï¹¬ÀûÀÎ + º¯È¯¾øÀÌ ASCII text/html ¹®¼·Î (±×¸®°í + .ascii È®ÀåÀÚ´Â ASCII + text/plainÀ¸·Î) ¼ºñ½ºÇÏ·Á¸é ´ÙÀ½ Áö½Ã¾î¸¦ + »ç¿ëÇÑ´Ù:
+ + + AddType text/x-ascii-html .ahtml
+ AddType text/x-ascii-plain .ascii + + +
¶Ç, text/foo ½ÄÀÇ MIME typeÀ» + AddType "text/x-ascii-foo" + ¼³Á¤ÇÏ¿© "ÀÏ¹Ý ASCII"·Î ¼ºñ½ºÇÒ ¼ö ÀÖ´Ù.
+
+
³»¿ëÀÌ ÀÏ¹Ý ¹®ÀÚ°¡ ¾Æ´Ñ ¹®¼´Â º¯È¯¾øÀÌ Ç×»ó "¹ÙÀÌ³Ê¸®"·Î + ¼ºñ½ºÇÑ´Ù. ¿¹¸¦ µé¾î, GIF/ZIP/AU ÆÄÀÏÇü½Ä¿¡ + °¡Àå ÀûÇÕÇÑ ¼±ÅÃÀÌ´Ù. ¹°·Ð »ç¿ëÀÚ´Â "rcp -b" + ¹ÙÀÌ³Ê¸® ¿É¼ÇÀ» »ç¿ëÇÏ¿© ÆÄÀÏÀ» ¸ÞÀÎÇÃ·¹ÀÓ È£½ºÆ®·Î + º¹»çÇß¾î¾ß ÇÑ´Ù.
+
+
¼¹öÆÄ½Ì ÆÄÀÏÀº Ç×»ó ÄÄÇ»ÅÍ°¡ »ç¿ëÇÏ´Â ±âº» Çü½ÄÀ¸·Î + (Áï, EBCDIC) ÀúÀåµÇ¾ú´Ù°í °¡Á¤ÇÏ°í, Ã³¸®ÈÄ¿¡ + º¯È¯ÇÑ´Ù.
+
+
CGI Ãâ·ÂÀÇ °æ¿ì CGI ½ºÅ©¸³Æ®°¡ º¯È¯ÀÌ ÇÊ¿äÇÑÁö °áÁ¤ÇÑ´Ù: + ÀûÀýÇÑ Content-TypeÀ» ¼³Á¤ÇÏ¿©, ¹®ÀÚÆÄÀÏÀº º¯È¯ÇÏ°í, + GIF Ãâ·ÂÀº º¯È¯¾øÀÌ º¸³¾ ¼ö ÀÖ´Ù. ¿ì¸®°¡ Æ÷ÆÃÇÑ wwwcount + ÇÁ·Î±×·¥ÀÌ ÈÄÀÚÀÇ °æ¿ì´Ù.
+

+ +

+ + ¹®¼ ÀúÀå¿¡ ´ëÇØ¼ + +

+ + ¹ÙÀÌ³Ê¸® ÆÄÀÏ + +

+ +

+ + ¹®ÀÚ ¹®¼ + +

+ +

+ + Server Side Include ¹®¼ + +

SSI ¹®¼´Â ÇöÀç EBCDIC Çü½ÄÀ¸·Î¸¸ ÀúÀåÇØ¾ß ÇÑ´Ù. Ã³¸®ÇÏ±â + Àü¿¡ ASCII¸¦ º¯È¯ÇÏÁö ¾Ê´Â´Ù.

+ +

+ + ¾ÆÆÄÄ¡ ¸ðµâÀÇ »óÅÂ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

¸ðµâ	»óÅÂ	ºñ°í
core	+
mod_access	+
mod_actions	+
mod_alias	+
mod_asis	+
mod_auth	+
mod_auth_anon	+
mod_auth_dbm	?	ÀÚÃ¼ `libdb.a`¸¦ »ç¿ëÇÏ¿©
mod_autoindex	+
mod_cern_meta	?
mod_cgi	+
`mod_digest`	+
mod_dir	+
mod_so	-	°øÀ¯¶óÀÌºê·¯¸®°¡ ¾øÀ½
mod_env	+
mod_example	-	(½ÃÇè ´Ü°è)
mod_expires	+
mod_headers	+
mod_imagemap	+
mod_include	+
mod_info	+
`mod_log_agent`	+
`mod_log_config`	+
mod_log_referer	+
mod_mime	+
mod_mime_magic	?	¾ÆÁ÷ Æ÷ÆÃ¾ÈµÊ
mod_negotiation	+
mod_proxy	+
mod_rewrite	+	Å×½ºÆ®¾ÈµÊ
mod_setenvif	+
mod_speling	+
mod_status	+
mod_unique_id	+
mod_userdir	+
mod_usertrack	?	Å×½ºÆ®¾ÈµÊ

+ +

+ + Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀÇ »óÅÂ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

¸ðµâ	»óÅÂ	ºñ°í
`mod_jserv +`	-	JAVA´Â Æ÷ÆÃÁßÀÌ´Ù.
`mod_php3`	+	`mod_php3`´Â LDAP, GD, FreeType ¶óÀÌºê·¯¸®¿Í + ÇÔ²² Àß µ¿ÀÛÇÑ´Ù.
`mod_put`	?	Å×½ºÆ®¾ÈµÊ
`mod_session`	-	Å×½ºÆ®¾ÈµÊ

+ +

+ + diff --git a/docs/manual/platform/ebcdic.xml.meta b/docs/manual/platform/ebcdic.xml.meta new file mode 100644 index 00000000000..96fc6c47b09 --- /dev/null +++ b/docs/manual/platform/ebcdic.xml.meta @@ -0,0 +1,13 @@ + + + + + ebcdic + /platform/ + .. + + + en + ko + + diff --git a/docs/manual/sitemap.html.de b/docs/manual/sitemap.html.de index d832e4e2fcd..9b3bec4dea1 100644 --- a/docs/manual/sitemap.html.de +++ b/docs/manual/sitemap.html.de @@ -138,6 +138,7 @@ Microsoft Windows

Apache unter Novell NetWare einsetzen

Einen Hochleistungs-Web-Server auf HPUX betreiben

Die Apache EBCDIC-Portierung

Other Topics

The Apache EBCDIC Port

Overview of the Apache EBCDIC Port

Design Goals

Technical Solution

Porting Notes

Document Storage Notes

Binary Files

Text Documents

Server Side Included Documents

Apache Modules' Status

Third Party Modules' Status

¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ

¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ °³¿ä

¼³°è ¸ñÇ¥

±â¼úÀû ÇØ°áÃ¥

Æ÷ÆÃ¿¡ ´ëÇØ¼

¹®¼ ÀúÀå¿¡ ´ëÇØ¼

¹ÙÀÌ³Ê¸® ÆÄÀÏ

¹®ÀÚ ¹®¼

Server Side Include ¹®¼

¾ÆÆÄÄ¡ ¸ðµâÀÇ »óÅÂ

Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀÇ »óÅÂ

Apache HTTP Server und Hilfsprogramme

Apache HTTP Server and Supporting Programs

Programas de soporte y el Servidor HTTP Apache

Le serveur HTTP Apache et ses programmes associés

Apache HTTP ãµã¼ãã¨ãµãã¼ãããã°ã©ã

¾ÆÆÄÄ¡ À¥¼¹ö¿Í Áö¿ø ÇÁ·Î±×·¥

Apache HTTP Sunucusu ve Desteklenen Programlar

Apache HTTP æå¡å¨ä¸æ¯æç¨åº