From 80db94fff6a9620fb469ee911347ed973e3f7735 Mon Sep 17 00:00:00 2001 From: Stefan Fritsch Date: Tue, 27 Dec 2011 19:42:03 +0100 Subject: Upstream tarball 2.2.3 --- docs/manual/LICENSE | 202 ++ docs/manual/bind.html | 19 + docs/manual/bind.html.de | 165 + docs/manual/bind.html.en | 161 + docs/manual/bind.html.fr | 197 ++ docs/manual/bind.html.ja.euc-jp | 175 + docs/manual/bind.html.ko.euc-kr | 151 + docs/manual/caching.html | 3 + docs/manual/caching.html.en | 655 ++++ docs/manual/configuring.html | 15 + docs/manual/configuring.html.de | 183 ++ docs/manual/configuring.html.en | 167 + docs/manual/configuring.html.ja.euc-jp | 171 + docs/manual/configuring.html.ko.euc-kr | 150 + docs/manual/content-negotiation.html | 11 + docs/manual/content-negotiation.html.en | 679 ++++ docs/manual/content-negotiation.html.ja.euc-jp | 729 +++++ docs/manual/content-negotiation.html.ko.euc-kr | 610 ++++ docs/manual/convenience.map | 386 +++ docs/manual/custom-error.html | 15 + docs/manual/custom-error.html.en | 204 ++ docs/manual/custom-error.html.es | 219 ++ docs/manual/custom-error.html.ja.euc-jp | 197 ++ docs/manual/custom-error.html.ko.euc-kr | 198 ++ docs/manual/developer/API.html | 3 + docs/manual/developer/API.html.en | 1222 +++++++ docs/manual/developer/debugging.html | 3 + docs/manual/developer/debugging.html.en | 197 ++ docs/manual/developer/documenting.html | 3 + docs/manual/developer/documenting.html.en | 84 + docs/manual/developer/filters.html | 3 + docs/manual/developer/filters.html.en | 210 ++ docs/manual/developer/hooks.html | 3 + docs/manual/developer/hooks.html.en | 239 ++ docs/manual/developer/index.html | 3 + docs/manual/developer/index.html.en | 82 + docs/manual/developer/modules.html | 7 + docs/manual/developer/modules.html.en | 273 ++ docs/manual/developer/modules.html.ja.euc-jp | 274 ++ docs/manual/developer/request.html | 3 + docs/manual/developer/request.html.en | 260 ++ docs/manual/developer/thread_safety.html | 3 + docs/manual/developer/thread_safety.html.en | 285 ++ docs/manual/dns-caveats.html | 11 + docs/manual/dns-caveats.html.en | 239 ++ docs/manual/dns-caveats.html.ja.euc-jp | 241 ++ docs/manual/dns-caveats.html.ko.euc-kr | 223 ++ docs/manual/dso.html | 11 + docs/manual/dso.html.en | 315 ++ docs/manual/dso.html.ja.euc-jp | 296 ++ docs/manual/dso.html.ko.euc-kr | 276 ++ docs/manual/env.html | 11 + docs/manual/env.html.en | 414 +++ docs/manual/env.html.ja.euc-jp | 403 +++ docs/manual/env.html.ko.euc-kr | 373 +++ docs/manual/faq/all_in_one.html | 11 + docs/manual/faq/all_in_one.html.en | 287 ++ docs/manual/faq/all_in_one.html.ja.euc-jp | 208 ++ docs/manual/faq/all_in_one.html.ko.euc-kr | 209 ++ docs/manual/faq/background.html | 3 + docs/manual/faq/background.html.en | 110 + docs/manual/faq/error.html | 11 + docs/manual/faq/error.html.en | 109 + docs/manual/faq/error.html.ja.euc-jp | 93 + docs/manual/faq/error.html.ko.euc-kr | 86 + docs/manual/faq/index.html | 11 + docs/manual/faq/index.html.en | 49 + docs/manual/faq/index.html.ja.euc-jp | 51 + docs/manual/faq/index.html.ko.euc-kr | 49 + docs/manual/faq/support.html | 11 + docs/manual/faq/support.html.en | 114 + docs/manual/faq/support.html.ja.euc-jp | 134 + docs/manual/faq/support.html.ko.euc-kr | 142 + docs/manual/filter.html | 19 + docs/manual/filter.html.en | 137 + docs/manual/filter.html.es | 81 + docs/manual/filter.html.fr | 84 + docs/manual/filter.html.ja.euc-jp | 141 + docs/manual/filter.html.ko.euc-kr | 80 + docs/manual/glossary.html | 15 + docs/manual/glossary.html.de | 549 ++++ docs/manual/glossary.html.en | 456 +++ docs/manual/glossary.html.es | 395 +++ docs/manual/glossary.html.ko.euc-kr | 364 +++ docs/manual/handler.html | 19 + docs/manual/handler.html.en | 155 + docs/manual/handler.html.es | 168 + docs/manual/handler.html.ja.euc-jp | 161 + docs/manual/handler.html.ko.euc-kr | 151 + docs/manual/handler.html.ru.koi8-r | 167 + docs/manual/howto/access.html | 3 + docs/manual/howto/access.html.en | 189 ++ docs/manual/howto/auth.html | 11 + docs/manual/howto/auth.html.en | 391 +++ docs/manual/howto/auth.html.ja.euc-jp | 386 +++ docs/manual/howto/auth.html.ko.euc-kr | 323 ++ docs/manual/howto/cgi.html | 11 + docs/manual/howto/cgi.html.en | 555 ++++ docs/manual/howto/cgi.html.ja.euc-jp | 549 ++++ docs/manual/howto/cgi.html.ko.euc-kr | 503 +++ docs/manual/howto/htaccess.html | 15 + docs/manual/howto/htaccess.html.en | 385 +++ docs/manual/howto/htaccess.html.ja.euc-jp | 383 +++ docs/manual/howto/htaccess.html.ko.euc-kr | 333 ++ docs/manual/howto/htaccess.html.pt-br | 375 +++ docs/manual/howto/index.html | 11 + docs/manual/howto/index.html.en | 117 + docs/manual/howto/index.html.ja.euc-jp | 104 + docs/manual/howto/index.html.ko.euc-kr | 109 + docs/manual/howto/public_html.html | 11 + docs/manual/howto/public_html.html.en | 161 + docs/manual/howto/public_html.html.ja.euc-jp | 155 + docs/manual/howto/public_html.html.ko.euc-kr | 156 + docs/manual/howto/ssi.html | 11 + docs/manual/howto/ssi.html.en | 486 +++ docs/manual/howto/ssi.html.ja.euc-jp | 481 +++ docs/manual/howto/ssi.html.ko.euc-kr | 426 +++ docs/manual/images/apache_header.gif | Bin 0 -> 4084 bytes docs/manual/images/caching_fig1.gif | Bin 0 -> 16515 bytes docs/manual/images/caching_fig1.png | Bin 0 -> 14262 bytes docs/manual/images/custom_errordocs.png | Bin 0 -> 22907 bytes docs/manual/images/down.gif | Bin 0 -> 56 bytes docs/manual/images/favicon.ico | Bin 0 -> 1078 bytes docs/manual/images/feather.gif | Bin 0 -> 6471 bytes docs/manual/images/feather.png | Bin 0 -> 6345 bytes docs/manual/images/filter_arch.png | Bin 0 -> 2553 bytes docs/manual/images/home.gif | Bin 0 -> 1465 bytes docs/manual/images/index.gif | Bin 0 -> 1540 bytes docs/manual/images/left.gif | Bin 0 -> 60 bytes docs/manual/images/mod_filter_new.gif | Bin 0 -> 2392 bytes docs/manual/images/mod_filter_new.png | Bin 0 -> 1130 bytes docs/manual/images/mod_filter_old.gif | Bin 0 -> 1230 bytes docs/manual/images/mod_rewrite_fig1.gif | Bin 0 -> 3525 bytes docs/manual/images/mod_rewrite_fig1.png | Bin 0 -> 5597 bytes docs/manual/images/mod_rewrite_fig2.gif | Bin 0 -> 2553 bytes docs/manual/images/mod_rewrite_fig2.png | Bin 0 -> 4144 bytes docs/manual/images/pixel.gif | Bin 0 -> 61 bytes docs/manual/images/right.gif | Bin 0 -> 59 bytes docs/manual/images/ssl_intro_fig1.gif | Bin 0 -> 5738 bytes docs/manual/images/ssl_intro_fig1.png | Bin 0 -> 7325 bytes docs/manual/images/ssl_intro_fig2.gif | Bin 0 -> 2700 bytes docs/manual/images/ssl_intro_fig2.png | Bin 0 -> 3190 bytes docs/manual/images/ssl_intro_fig3.gif | Bin 0 -> 4020 bytes docs/manual/images/ssl_intro_fig3.png | Bin 0 -> 5487 bytes docs/manual/images/sub.gif | Bin 0 -> 6083 bytes docs/manual/images/up.gif | Bin 0 -> 57 bytes docs/manual/index.html | 27 + docs/manual/index.html.de | 104 + docs/manual/index.html.en | 103 + docs/manual/index.html.es | 110 + docs/manual/index.html.fr | 103 + docs/manual/index.html.ja.euc-jp | 103 + docs/manual/index.html.ko.euc-kr | 101 + docs/manual/index.html.pt-br | 102 + docs/manual/install.html | 23 + docs/manual/install.html.de | 428 +++ docs/manual/install.html.en | 412 +++ docs/manual/install.html.es | 438 +++ docs/manual/install.html.fr | 430 +++ docs/manual/install.html.ja.euc-jp | 419 +++ docs/manual/install.html.ko.euc-kr | 360 +++ docs/manual/invoking.html | 23 + docs/manual/invoking.html.de | 156 + docs/manual/invoking.html.en | 151 + docs/manual/invoking.html.es | 168 + docs/manual/invoking.html.ja.euc-jp | 161 + docs/manual/invoking.html.ko.euc-kr | 140 + docs/manual/invoking.html.ru.koi8-r | 143 + docs/manual/license.html | 3 + docs/manual/license.html.en | 238 ++ docs/manual/logs.html | 11 + docs/manual/logs.html.en | 602 ++++ docs/manual/logs.html.ja.euc-jp | 571 ++++ docs/manual/logs.html.ko.euc-kr | 521 +++ docs/manual/misc/index.html | 7 + docs/manual/misc/index.html.en | 80 + docs/manual/misc/index.html.ko.euc-kr | 76 + docs/manual/misc/perf-tuning.html | 7 + docs/manual/misc/perf-tuning.html.en | 1056 ++++++ docs/manual/misc/perf-tuning.html.ko.euc-kr | 976 ++++++ docs/manual/misc/relevant_standards.html | 7 + docs/manual/misc/relevant_standards.html.en | 199 ++ docs/manual/misc/relevant_standards.html.ko.euc-kr | 191 ++ docs/manual/misc/rewriteguide.html | 7 + docs/manual/misc/rewriteguide.html.en | 2102 ++++++++++++ docs/manual/misc/rewriteguide.html.ko.euc-kr | 2006 ++++++++++++ docs/manual/misc/security_tips.html | 7 + docs/manual/misc/security_tips.html.en | 350 ++ docs/manual/misc/security_tips.html.ko.euc-kr | 343 ++ docs/manual/mod/beos.html | 15 + docs/manual/mod/beos.html.de | 109 + docs/manual/mod/beos.html.en | 107 + docs/manual/mod/beos.html.es | 115 + docs/manual/mod/beos.html.ko.euc-kr | 105 + docs/manual/mod/core.html | 11 + docs/manual/mod/core.html.de | 3357 +++++++++++++++++++ docs/manual/mod/core.html.en | 3389 ++++++++++++++++++++ docs/manual/mod/core.html.ja.euc-jp | 3373 +++++++++++++++++++ docs/manual/mod/directive-dict.html | 11 + docs/manual/mod/directive-dict.html.en | 291 ++ docs/manual/mod/directive-dict.html.ja.euc-jp | 303 ++ docs/manual/mod/directive-dict.html.ko.euc-kr | 252 ++ docs/manual/mod/directives.html | 23 + docs/manual/mod/directives.html.de | 428 +++ docs/manual/mod/directives.html.en | 434 +++ docs/manual/mod/directives.html.es | 436 +++ docs/manual/mod/directives.html.ja.euc-jp | 429 +++ docs/manual/mod/directives.html.ko.euc-kr | 428 +++ docs/manual/mod/directives.html.ru.koi8-r | 433 +++ docs/manual/mod/event.html | 3 + docs/manual/mod/event.html.en | 146 + docs/manual/mod/index.html | 19 + docs/manual/mod/index.html.de | 193 ++ docs/manual/mod/index.html.en | 191 ++ docs/manual/mod/index.html.es | 194 ++ docs/manual/mod/index.html.ja.euc-jp | 179 ++ docs/manual/mod/index.html.ko.euc-kr | 173 + docs/manual/mod/mod_actions.html | 15 + docs/manual/mod/mod_actions.html.de | 166 + docs/manual/mod/mod_actions.html.en | 164 + docs/manual/mod/mod_actions.html.ja.euc-jp | 175 + docs/manual/mod/mod_actions.html.ko.euc-kr | 166 + docs/manual/mod/mod_alias.html | 11 + docs/manual/mod/mod_alias.html.en | 391 +++ docs/manual/mod/mod_alias.html.ja.euc-jp | 387 +++ docs/manual/mod/mod_alias.html.ko.euc-kr | 356 ++ docs/manual/mod/mod_asis.html | 11 + docs/manual/mod/mod_asis.html.en | 112 + docs/manual/mod/mod_asis.html.ja.euc-jp | 112 + docs/manual/mod/mod_asis.html.ko.euc-kr | 110 + docs/manual/mod/mod_auth_basic.html | 11 + docs/manual/mod/mod_auth_basic.html.en | 127 + docs/manual/mod/mod_auth_basic.html.ja.euc-jp | 135 + docs/manual/mod/mod_auth_basic.html.ko.euc-kr | 130 + docs/manual/mod/mod_auth_digest.html | 7 + docs/manual/mod/mod_auth_digest.html.en | 329 ++ docs/manual/mod/mod_auth_digest.html.ko.euc-kr | 321 ++ docs/manual/mod/mod_authn_alias.html | 3 + docs/manual/mod/mod_authn_alias.html.en | 121 + docs/manual/mod/mod_authn_anon.html | 11 + docs/manual/mod/mod_authn_anon.html.en | 224 ++ docs/manual/mod/mod_authn_anon.html.ja.euc-jp | 224 ++ docs/manual/mod/mod_authn_anon.html.ko.euc-kr | 211 ++ docs/manual/mod/mod_authn_dbd.html | 3 + docs/manual/mod/mod_authn_dbd.html.en | 155 + docs/manual/mod/mod_authn_dbm.html | 11 + docs/manual/mod/mod_authn_dbm.html.en | 136 + docs/manual/mod/mod_authn_dbm.html.ja.euc-jp | 135 + docs/manual/mod/mod_authn_dbm.html.ko.euc-kr | 131 + docs/manual/mod/mod_authn_default.html | 11 + docs/manual/mod/mod_authn_default.html.en | 80 + docs/manual/mod/mod_authn_default.html.ja.euc-jp | 80 + docs/manual/mod/mod_authn_default.html.ko.euc-kr | 76 + docs/manual/mod/mod_authn_file.html | 11 + docs/manual/mod/mod_authn_file.html.en | 132 + docs/manual/mod/mod_authn_file.html.ja.euc-jp | 142 + docs/manual/mod/mod_authn_file.html.ko.euc-kr | 129 + docs/manual/mod/mod_authnz_ldap.html | 3 + docs/manual/mod/mod_authnz_ldap.html.en | 940 ++++++ docs/manual/mod/mod_authz_dbm.html | 7 + docs/manual/mod/mod_authz_dbm.html.en | 185 ++ docs/manual/mod/mod_authz_dbm.html.ko.euc-kr | 170 + docs/manual/mod/mod_authz_default.html | 11 + docs/manual/mod/mod_authz_default.html.en | 80 + docs/manual/mod/mod_authz_default.html.ja.euc-jp | 79 + docs/manual/mod/mod_authz_default.html.ko.euc-kr | 78 + docs/manual/mod/mod_authz_groupfile.html | 11 + docs/manual/mod/mod_authz_groupfile.html.en | 125 + docs/manual/mod/mod_authz_groupfile.html.ja.euc-jp | 132 + docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr | 121 + docs/manual/mod/mod_authz_host.html | 11 + docs/manual/mod/mod_authz_host.html.en | 333 ++ docs/manual/mod/mod_authz_host.html.ja.euc-jp | 347 ++ docs/manual/mod/mod_authz_host.html.ko.euc-kr | 310 ++ docs/manual/mod/mod_authz_owner.html | 11 + docs/manual/mod/mod_authz_owner.html.en | 185 ++ docs/manual/mod/mod_authz_owner.html.ja.euc-jp | 187 ++ docs/manual/mod/mod_authz_owner.html.ko.euc-kr | 182 ++ docs/manual/mod/mod_authz_user.html | 11 + docs/manual/mod/mod_authz_user.html.en | 84 + docs/manual/mod/mod_authz_user.html.ja.euc-jp | 83 + docs/manual/mod/mod_authz_user.html.ko.euc-kr | 81 + docs/manual/mod/mod_autoindex.html | 11 + docs/manual/mod/mod_autoindex.html.en | 893 ++++++ docs/manual/mod/mod_autoindex.html.ja.euc-jp | 985 ++++++ docs/manual/mod/mod_autoindex.html.ko.euc-kr | 835 +++++ docs/manual/mod/mod_cache.html | 11 + docs/manual/mod/mod_cache.html.en | 463 +++ docs/manual/mod/mod_cache.html.ja.euc-jp | 443 +++ docs/manual/mod/mod_cache.html.ko.euc-kr | 347 ++ docs/manual/mod/mod_cern_meta.html | 7 + docs/manual/mod/mod_cern_meta.html.en | 128 + docs/manual/mod/mod_cern_meta.html.ko.euc-kr | 120 + docs/manual/mod/mod_cgi.html | 11 + docs/manual/mod/mod_cgi.html.en | 247 ++ docs/manual/mod/mod_cgi.html.ja.euc-jp | 254 ++ docs/manual/mod/mod_cgi.html.ko.euc-kr | 234 ++ docs/manual/mod/mod_cgid.html | 11 + docs/manual/mod/mod_cgid.html.en | 106 + docs/manual/mod/mod_cgid.html.ja.euc-jp | 100 + docs/manual/mod/mod_cgid.html.ko.euc-kr | 99 + docs/manual/mod/mod_charset_lite.html | 7 + docs/manual/mod/mod_charset_lite.html.en | 210 ++ docs/manual/mod/mod_charset_lite.html.ko.euc-kr | 198 ++ docs/manual/mod/mod_dav.html | 11 + docs/manual/mod/mod_dav.html.en | 270 ++ docs/manual/mod/mod_dav.html.ja.euc-jp | 276 ++ docs/manual/mod/mod_dav.html.ko.euc-kr | 265 ++ docs/manual/mod/mod_dav_fs.html | 11 + docs/manual/mod/mod_dav_fs.html.en | 97 + docs/manual/mod/mod_dav_fs.html.ja.euc-jp | 89 + docs/manual/mod/mod_dav_fs.html.ko.euc-kr | 96 + docs/manual/mod/mod_dav_lock.html | 7 + docs/manual/mod/mod_dav_lock.html.en | 101 + docs/manual/mod/mod_dav_lock.html.ja.euc-jp | 105 + docs/manual/mod/mod_dbd.html | 3 + docs/manual/mod/mod_dbd.html.en | 263 ++ docs/manual/mod/mod_deflate.html | 11 + docs/manual/mod/mod_deflate.html.en | 376 +++ docs/manual/mod/mod_deflate.html.ja.euc-jp | 385 +++ docs/manual/mod/mod_deflate.html.ko.euc-kr | 368 +++ docs/manual/mod/mod_dir.html | 11 + docs/manual/mod/mod_dir.html.en | 169 + docs/manual/mod/mod_dir.html.ja.euc-jp | 182 ++ docs/manual/mod/mod_dir.html.ko.euc-kr | 169 + docs/manual/mod/mod_disk_cache.html | 11 + docs/manual/mod/mod_disk_cache.html.en | 178 + docs/manual/mod/mod_disk_cache.html.ja.euc-jp | 174 + docs/manual/mod/mod_disk_cache.html.ko.euc-kr | 175 + docs/manual/mod/mod_dumpio.html | 7 + docs/manual/mod/mod_dumpio.html.en | 106 + docs/manual/mod/mod_dumpio.html.ja.euc-jp | 105 + docs/manual/mod/mod_echo.html | 11 + docs/manual/mod/mod_echo.html.en | 73 + docs/manual/mod/mod_echo.html.ja.euc-jp | 72 + docs/manual/mod/mod_echo.html.ko.euc-kr | 71 + docs/manual/mod/mod_env.html | 11 + docs/manual/mod/mod_env.html.en | 117 + docs/manual/mod/mod_env.html.ja.euc-jp | 117 + docs/manual/mod/mod_env.html.ko.euc-kr | 114 + docs/manual/mod/mod_example.html | 7 + docs/manual/mod/mod_example.html.en | 156 + docs/manual/mod/mod_example.html.ko.euc-kr | 155 + docs/manual/mod/mod_expires.html | 11 + docs/manual/mod/mod_expires.html.en | 247 ++ docs/manual/mod/mod_expires.html.ja.euc-jp | 233 ++ docs/manual/mod/mod_expires.html.ko.euc-kr | 225 ++ docs/manual/mod/mod_ext_filter.html | 11 + docs/manual/mod/mod_ext_filter.html.en | 376 +++ docs/manual/mod/mod_ext_filter.html.ja.euc-jp | 369 +++ docs/manual/mod/mod_ext_filter.html.ko.euc-kr | 354 ++ docs/manual/mod/mod_file_cache.html | 7 + docs/manual/mod/mod_file_cache.html.en | 212 ++ docs/manual/mod/mod_file_cache.html.ko.euc-kr | 200 ++ docs/manual/mod/mod_filter.html | 3 + docs/manual/mod/mod_filter.html.en | 443 +++ docs/manual/mod/mod_headers.html | 11 + docs/manual/mod/mod_headers.html.en | 356 ++ docs/manual/mod/mod_headers.html.ja.euc-jp | 349 ++ docs/manual/mod/mod_headers.html.ko.euc-kr | 339 ++ docs/manual/mod/mod_ident.html | 7 + docs/manual/mod/mod_ident.html.en | 101 + docs/manual/mod/mod_ident.html.ko.euc-kr | 98 + docs/manual/mod/mod_imagemap.html | 7 + docs/manual/mod/mod_imagemap.html.en | 382 +++ docs/manual/mod/mod_imagemap.html.ko.euc-kr | 363 +++ docs/manual/mod/mod_include.html | 7 + docs/manual/mod/mod_include.html.en | 806 +++++ docs/manual/mod/mod_include.html.ja.euc-jp | 791 +++++ docs/manual/mod/mod_info.html | 11 + docs/manual/mod/mod_info.html.en | 194 ++ docs/manual/mod/mod_info.html.ja.euc-jp | 188 ++ docs/manual/mod/mod_info.html.ko.euc-kr | 169 + docs/manual/mod/mod_isapi.html | 7 + docs/manual/mod/mod_isapi.html.en | 343 ++ docs/manual/mod/mod_isapi.html.ko.euc-kr | 319 ++ docs/manual/mod/mod_ldap.html | 3 + docs/manual/mod/mod_ldap.html.en | 627 ++++ docs/manual/mod/mod_log_config.html | 11 + docs/manual/mod/mod_log_config.html.en | 472 +++ docs/manual/mod/mod_log_config.html.ja.euc-jp | 471 +++ docs/manual/mod/mod_log_config.html.ko.euc-kr | 401 +++ docs/manual/mod/mod_log_forensic.html | 7 + docs/manual/mod/mod_log_forensic.html.en | 162 + docs/manual/mod/mod_log_forensic.html.ja.euc-jp | 163 + docs/manual/mod/mod_logio.html | 11 + docs/manual/mod/mod_logio.html.en | 91 + docs/manual/mod/mod_logio.html.ja.euc-jp | 91 + docs/manual/mod/mod_logio.html.ko.euc-kr | 92 + docs/manual/mod/mod_mem_cache.html | 11 + docs/manual/mod/mod_mem_cache.html.en | 236 ++ docs/manual/mod/mod_mem_cache.html.ja.euc-jp | 234 ++ docs/manual/mod/mod_mem_cache.html.ko.euc-kr | 237 ++ docs/manual/mod/mod_mime.html | 7 + docs/manual/mod/mod_mime.html.en | 943 ++++++ docs/manual/mod/mod_mime.html.ja.euc-jp | 939 ++++++ docs/manual/mod/mod_mime_magic.html | 3 + docs/manual/mod/mod_mime_magic.html.en | 275 ++ docs/manual/mod/mod_negotiation.html | 7 + docs/manual/mod/mod_negotiation.html.en | 307 ++ docs/manual/mod/mod_negotiation.html.ja.euc-jp | 302 ++ docs/manual/mod/mod_nw_ssl.html | 3 + docs/manual/mod/mod_nw_ssl.html.en | 97 + docs/manual/mod/mod_proxy.html | 7 + docs/manual/mod/mod_proxy.html.en | 1131 +++++++ docs/manual/mod/mod_proxy.html.ja.euc-jp | 1204 +++++++ docs/manual/mod/mod_proxy_ajp.html | 7 + docs/manual/mod/mod_proxy_ajp.html.en | 556 ++++ docs/manual/mod/mod_proxy_ajp.html.ja.euc-jp | 542 ++++ docs/manual/mod/mod_proxy_balancer.html | 7 + docs/manual/mod/mod_proxy_balancer.html.en | 316 ++ docs/manual/mod/mod_proxy_balancer.html.ja.euc-jp | 319 ++ docs/manual/mod/mod_proxy_connect.html | 3 + docs/manual/mod/mod_proxy_connect.html.en | 62 + docs/manual/mod/mod_proxy_ftp.html | 3 + docs/manual/mod/mod_proxy_ftp.html.en | 163 + docs/manual/mod/mod_proxy_http.html | 3 + docs/manual/mod/mod_proxy_http.html.en | 65 + docs/manual/mod/mod_rewrite.html | 3 + docs/manual/mod/mod_rewrite.html.en | 1564 +++++++++ docs/manual/mod/mod_setenvif.html | 11 + docs/manual/mod/mod_setenvif.html.en | 285 ++ docs/manual/mod/mod_setenvif.html.ja.euc-jp | 282 ++ docs/manual/mod/mod_setenvif.html.ko.euc-kr | 259 ++ docs/manual/mod/mod_so.html | 11 + docs/manual/mod/mod_so.html.en | 190 ++ docs/manual/mod/mod_so.html.ja.euc-jp | 190 ++ docs/manual/mod/mod_so.html.ko.euc-kr | 174 + docs/manual/mod/mod_speling.html | 11 + docs/manual/mod/mod_speling.html.en | 128 + docs/manual/mod/mod_speling.html.ja.euc-jp | 127 + docs/manual/mod/mod_speling.html.ko.euc-kr | 118 + docs/manual/mod/mod_ssl.html | 3 + docs/manual/mod/mod_ssl.html.en | 1722 ++++++++++ docs/manual/mod/mod_status.html | 11 + docs/manual/mod/mod_status.html.en | 162 + docs/manual/mod/mod_status.html.ja.euc-jp | 154 + docs/manual/mod/mod_status.html.ko.euc-kr | 148 + docs/manual/mod/mod_suexec.html | 11 + docs/manual/mod/mod_suexec.html.en | 80 + docs/manual/mod/mod_suexec.html.ja.euc-jp | 79 + docs/manual/mod/mod_suexec.html.ko.euc-kr | 81 + docs/manual/mod/mod_unique_id.html | 11 + docs/manual/mod/mod_unique_id.html.en | 216 ++ docs/manual/mod/mod_unique_id.html.ja.euc-jp | 214 ++ docs/manual/mod/mod_unique_id.html.ko.euc-kr | 191 ++ docs/manual/mod/mod_userdir.html | 11 + docs/manual/mod/mod_userdir.html.en | 175 + docs/manual/mod/mod_userdir.html.ja.euc-jp | 185 ++ docs/manual/mod/mod_userdir.html.ko.euc-kr | 161 + docs/manual/mod/mod_usertrack.html | 3 + docs/manual/mod/mod_usertrack.html.en | 252 ++ docs/manual/mod/mod_version.html | 11 + docs/manual/mod/mod_version.html.en | 151 + docs/manual/mod/mod_version.html.ja.euc-jp | 150 + docs/manual/mod/mod_version.html.ko.euc-kr | 150 + docs/manual/mod/mod_vhost_alias.html | 3 + docs/manual/mod/mod_vhost_alias.html.en | 312 ++ docs/manual/mod/module-dict.html | 11 + docs/manual/mod/module-dict.html.en | 117 + docs/manual/mod/module-dict.html.ja.euc-jp | 119 + docs/manual/mod/module-dict.html.ko.euc-kr | 109 + docs/manual/mod/mpm_common.html | 11 + docs/manual/mod/mpm_common.html.de | 988 ++++++ docs/manual/mod/mpm_common.html.en | 941 ++++++ docs/manual/mod/mpm_common.html.ja.euc-jp | 997 ++++++ docs/manual/mod/mpm_netware.html | 3 + docs/manual/mod/mpm_netware.html.en | 110 + docs/manual/mod/mpm_winnt.html | 11 + docs/manual/mod/mpm_winnt.html.de | 94 + docs/manual/mod/mpm_winnt.html.en | 94 + docs/manual/mod/mpm_winnt.html.ja.euc-jp | 93 + docs/manual/mod/mpmt_os2.html | 3 + docs/manual/mod/mpmt_os2.html.en | 73 + docs/manual/mod/prefork.html | 11 + docs/manual/mod/prefork.html.de | 191 ++ docs/manual/mod/prefork.html.en | 176 + docs/manual/mod/prefork.html.ja.euc-jp | 189 ++ docs/manual/mod/quickreference.html | 23 + docs/manual/mod/quickreference.html.de | 764 +++++ docs/manual/mod/quickreference.html.en | 753 +++++ docs/manual/mod/quickreference.html.es | 756 +++++ docs/manual/mod/quickreference.html.ja.euc-jp | 684 ++++ docs/manual/mod/quickreference.html.ko.euc-kr | 699 ++++ docs/manual/mod/quickreference.html.ru.koi8-r | 755 +++++ docs/manual/mod/worker.html | 11 + docs/manual/mod/worker.html.de | 170 + docs/manual/mod/worker.html.en | 177 + docs/manual/mod/worker.html.ja.euc-jp | 187 ++ docs/manual/mpm.html | 19 + docs/manual/mpm.html.de | 125 + docs/manual/mpm.html.en | 125 + docs/manual/mpm.html.es | 139 + docs/manual/mpm.html.ja.euc-jp | 130 + docs/manual/mpm.html.ko.euc-kr | 122 + docs/manual/new_features_2_0.html | 27 + docs/manual/new_features_2_0.html.de | 263 ++ docs/manual/new_features_2_0.html.en | 243 ++ docs/manual/new_features_2_0.html.fr | 251 ++ docs/manual/new_features_2_0.html.ja.euc-jp | 253 ++ docs/manual/new_features_2_0.html.ko.euc-kr | 233 ++ docs/manual/new_features_2_0.html.pt-br | 242 ++ docs/manual/new_features_2_0.html.ru.koi8-r | 250 ++ docs/manual/new_features_2_2.html | 11 + docs/manual/new_features_2_2.html.en | 272 ++ docs/manual/new_features_2_2.html.ko.euc-kr | 126 + docs/manual/new_features_2_2.html.pt-br | 135 + docs/manual/platform/ebcdic.html | 7 + docs/manual/platform/ebcdic.html.en | 584 ++++ docs/manual/platform/ebcdic.html.ko.euc-kr | 559 ++++ docs/manual/platform/index.html | 7 + docs/manual/platform/index.html.en | 94 + docs/manual/platform/index.html.ko.euc-kr | 94 + docs/manual/platform/netware.html | 7 + docs/manual/platform/netware.html.en | 655 ++++ docs/manual/platform/netware.html.ko.euc-kr | 581 ++++ docs/manual/platform/perf-hp.html | 7 + docs/manual/platform/perf-hp.html.en | 105 + docs/manual/platform/perf-hp.html.ko.euc-kr | 100 + docs/manual/platform/win_compiling.html | 7 + docs/manual/platform/win_compiling.html.en | 435 +++ docs/manual/platform/win_compiling.html.ko.euc-kr | 423 +++ docs/manual/platform/windows.html | 7 + docs/manual/platform/windows.html.en | 737 +++++ docs/manual/platform/windows.html.ko.euc-kr | 688 ++++ docs/manual/programs/ab.html | 7 + docs/manual/programs/ab.html.en | 198 ++ docs/manual/programs/ab.html.ko.euc-kr | 201 ++ docs/manual/programs/apachectl.html | 7 + docs/manual/programs/apachectl.html.en | 158 + docs/manual/programs/apachectl.html.ko.euc-kr | 144 + docs/manual/programs/apxs.html | 7 + docs/manual/programs/apxs.html.en | 330 ++ docs/manual/programs/apxs.html.ko.euc-kr | 324 ++ docs/manual/programs/configure.html | 7 + docs/manual/programs/configure.html.en | 937 ++++++ docs/manual/programs/configure.html.ko.euc-kr | 930 ++++++ docs/manual/programs/dbmmanage.html | 7 + docs/manual/programs/dbmmanage.html.en | 191 ++ docs/manual/programs/dbmmanage.html.ko.euc-kr | 172 + docs/manual/programs/htcacheclean.html | 7 + docs/manual/programs/htcacheclean.html.en | 120 + docs/manual/programs/htcacheclean.html.ko.euc-kr | 113 + docs/manual/programs/htdbm.html | 3 + docs/manual/programs/htdbm.html.en | 281 ++ docs/manual/programs/htdigest.html | 7 + docs/manual/programs/htdigest.html.en | 72 + docs/manual/programs/htdigest.html.ko.euc-kr | 75 + docs/manual/programs/htpasswd.html | 7 + docs/manual/programs/htpasswd.html.en | 215 ++ docs/manual/programs/htpasswd.html.ko.euc-kr | 217 ++ docs/manual/programs/httpd.html | 7 + docs/manual/programs/httpd.html.en | 193 ++ docs/manual/programs/httpd.html.ko.euc-kr | 188 ++ docs/manual/programs/httxt2dbm.html | 3 + docs/manual/programs/httxt2dbm.html.en | 82 + docs/manual/programs/index.html | 15 + docs/manual/programs/index.html.en | 106 + docs/manual/programs/index.html.es | 102 + docs/manual/programs/index.html.ko.euc-kr | 98 + docs/manual/programs/index.html.ru.koi8-r | 100 + docs/manual/programs/logresolve.html | 7 + docs/manual/programs/logresolve.html.en | 72 + docs/manual/programs/logresolve.html.ko.euc-kr | 69 + docs/manual/programs/other.html | 7 + docs/manual/programs/other.html.en | 59 + docs/manual/programs/other.html.ko.euc-kr | 57 + docs/manual/programs/rotatelogs.html | 7 + docs/manual/programs/rotatelogs.html.en | 146 + docs/manual/programs/rotatelogs.html.ko.euc-kr | 143 + docs/manual/programs/suexec.html | 7 + docs/manual/programs/suexec.html.en | 61 + docs/manual/programs/suexec.html.ko.euc-kr | 62 + docs/manual/rewrite/index.html | 3 + docs/manual/rewrite/index.html.en | 96 + docs/manual/rewrite/rewrite_guide.html | 3 + docs/manual/rewrite/rewrite_guide.html.en | 789 +++++ docs/manual/rewrite/rewrite_guide_advanced.html | 3 + docs/manual/rewrite/rewrite_guide_advanced.html.en | 1289 ++++++++ docs/manual/rewrite/rewrite_intro.html | 3 + docs/manual/rewrite/rewrite_intro.html.en | 196 ++ docs/manual/rewrite/rewrite_tech.html | 3 + docs/manual/rewrite/rewrite_tech.html.en | 167 + docs/manual/sections.html | 11 + docs/manual/sections.html.en | 477 +++ docs/manual/sections.html.ja.euc-jp | 468 +++ docs/manual/sections.html.ko.euc-kr | 422 +++ docs/manual/server-wide.html | 11 + docs/manual/server-wide.html.en | 100 + docs/manual/server-wide.html.ja.euc-jp | 101 + docs/manual/server-wide.html.ko.euc-kr | 95 + docs/manual/sitemap.html | 19 + docs/manual/sitemap.html.de | 266 ++ docs/manual/sitemap.html.en | 264 ++ docs/manual/sitemap.html.es | 269 ++ docs/manual/sitemap.html.ja.euc-jp | 263 ++ docs/manual/sitemap.html.ko.euc-kr | 267 ++ docs/manual/ssl/index.html | 7 + docs/manual/ssl/index.html.en | 57 + docs/manual/ssl/index.html.ja.euc-jp | 59 + docs/manual/ssl/ssl_compat.html | 3 + docs/manual/ssl/ssl_compat.html.en | 226 ++ docs/manual/ssl/ssl_faq.html | 3 + docs/manual/ssl/ssl_faq.html.en | 1044 ++++++ docs/manual/ssl/ssl_howto.html | 3 + docs/manual/ssl/ssl_howto.html.en | 294 ++ docs/manual/ssl/ssl_intro.html | 7 + docs/manual/ssl/ssl_intro.html.en | 650 ++++ docs/manual/ssl/ssl_intro.html.ja.euc-jp | 697 ++++ docs/manual/stopping.html | 19 + docs/manual/stopping.html.de | 306 ++ docs/manual/stopping.html.en | 233 ++ docs/manual/stopping.html.es | 267 ++ docs/manual/stopping.html.ja.euc-jp | 256 ++ docs/manual/stopping.html.ko.euc-kr | 205 ++ docs/manual/style/build.properties | 4 + docs/manual/style/common.dtd | 191 ++ docs/manual/style/css/manual-chm.css | 27 + docs/manual/style/css/manual-loose-100pc.css | 155 + docs/manual/style/css/manual-print.css | 717 +++++ docs/manual/style/css/manual-zip-100pc.css | 23 + docs/manual/style/css/manual-zip.css | 24 + docs/manual/style/css/manual.css | 1026 ++++++ docs/manual/style/faq.dtd | 35 + docs/manual/style/lang.dtd | 24 + docs/manual/style/latex/atbeginend.sty | 80 + docs/manual/style/latex/common.xsl | 244 ++ docs/manual/style/latex/directiveindex.xsl | 61 + docs/manual/style/latex/faq.xsl | 43 + docs/manual/style/latex/html.xsl | 323 ++ docs/manual/style/latex/latex.xsl | 383 +++ docs/manual/style/latex/manualpage.xsl | 35 + docs/manual/style/latex/moduleindex.xsl | 218 ++ docs/manual/style/latex/quickreference.xsl | 140 + docs/manual/style/latex/synopsis.xsl | 346 ++ docs/manual/style/manual.de.xsl | 37 + docs/manual/style/manual.en.xsl | 37 + docs/manual/style/manual.es.xsl | 37 + docs/manual/style/manual.fr.xsl | 37 + docs/manual/style/manual.ja.xsl | 37 + docs/manual/style/manual.ko.xsl | 37 + docs/manual/style/manual.pt-br.xsl | 37 + docs/manual/style/manual.ru.xsl | 37 + docs/manual/style/manualpage.dtd | 27 + docs/manual/style/modulesynopsis.dtd | 76 + docs/manual/style/sitemap.dtd | 38 + docs/manual/style/version.ent | 24 + docs/manual/style/xsl/common.xsl | 1156 +++++++ docs/manual/style/xsl/convmap.xsl | 71 + docs/manual/style/xsl/directiveindex.xsl | 130 + docs/manual/style/xsl/faq.xsl | 199 ++ docs/manual/style/xsl/hhc.xsl | 668 ++++ docs/manual/style/xsl/hhp.xsl | 316 ++ docs/manual/style/xsl/indexpage.xsl | 211 ++ docs/manual/style/xsl/language.xsl | 658 ++++ docs/manual/style/xsl/maf.xsl | 56 + docs/manual/style/xsl/manualpage.xsl | 87 + docs/manual/style/xsl/moduleindex.xsl | 333 ++ docs/manual/style/xsl/nroff.xsl | 448 +++ docs/manual/style/xsl/quickreference.xsl | 210 ++ docs/manual/style/xsl/sitemap.xsl | 242 ++ docs/manual/style/xsl/synopsis.xsl | 508 +++ docs/manual/style/xsl/typemap.xsl | 80 + docs/manual/style/xsl/util/modtrans.xsl | 44 + docs/manual/suexec.html | 11 + docs/manual/suexec.html.en | 608 ++++ docs/manual/suexec.html.ja.euc-jp | 609 ++++ docs/manual/suexec.html.ko.euc-kr | 534 +++ docs/manual/upgrading.html | 23 + docs/manual/upgrading.html.de | 120 + docs/manual/upgrading.html.en | 156 + docs/manual/upgrading.html.ja.euc-jp | 222 ++ docs/manual/upgrading.html.ko.euc-kr | 204 ++ docs/manual/upgrading.html.pt-br | 225 ++ docs/manual/upgrading.html.ru.koi8-r | 202 ++ docs/manual/urlmapping.html | 11 + docs/manual/urlmapping.html.en | 286 ++ docs/manual/urlmapping.html.ja.euc-jp | 286 ++ docs/manual/urlmapping.html.ko.euc-kr | 247 ++ docs/manual/vhosts/details.html | 11 + docs/manual/vhosts/details.html.en | 442 +++ docs/manual/vhosts/details.html.fr | 459 +++ docs/manual/vhosts/details.html.ko.euc-kr | 384 +++ docs/manual/vhosts/examples.html | 15 + docs/manual/vhosts/examples.html.en | 660 ++++ docs/manual/vhosts/examples.html.fr | 679 ++++ docs/manual/vhosts/examples.html.ja.euc-jp | 648 ++++ docs/manual/vhosts/examples.html.ko.euc-kr | 629 ++++ docs/manual/vhosts/fd-limits.html | 15 + docs/manual/vhosts/fd-limits.html.en | 128 + docs/manual/vhosts/fd-limits.html.fr | 141 + docs/manual/vhosts/fd-limits.html.ja.euc-jp | 125 + docs/manual/vhosts/fd-limits.html.ko.euc-kr | 122 + docs/manual/vhosts/index.html | 23 + docs/manual/vhosts/index.html.de | 110 + docs/manual/vhosts/index.html.en | 110 + docs/manual/vhosts/index.html.fr | 111 + docs/manual/vhosts/index.html.ja.euc-jp | 105 + docs/manual/vhosts/index.html.ko.euc-kr | 108 + docs/manual/vhosts/index.html.ru.koi8-r | 105 + docs/manual/vhosts/ip-based.html | 15 + docs/manual/vhosts/ip-based.html.en | 162 + docs/manual/vhosts/ip-based.html.fr | 182 ++ docs/manual/vhosts/ip-based.html.ja.euc-jp | 158 + docs/manual/vhosts/ip-based.html.ko.euc-kr | 152 + docs/manual/vhosts/mass.html | 7 + docs/manual/vhosts/mass.html.en | 445 +++ docs/manual/vhosts/mass.html.ko.euc-kr | 423 +++ docs/manual/vhosts/name-based.html | 19 + docs/manual/vhosts/name-based.html.de | 268 ++ docs/manual/vhosts/name-based.html.en | 246 ++ docs/manual/vhosts/name-based.html.fr | 298 ++ docs/manual/vhosts/name-based.html.ja.euc-jp | 271 ++ docs/manual/vhosts/name-based.html.ko.euc-kr | 236 ++ 714 files changed, 152983 insertions(+) create mode 100644 docs/manual/LICENSE create mode 100644 docs/manual/bind.html create mode 100644 docs/manual/bind.html.de create mode 100644 docs/manual/bind.html.en create mode 100644 docs/manual/bind.html.fr create mode 100644 docs/manual/bind.html.ja.euc-jp create mode 100644 docs/manual/bind.html.ko.euc-kr create mode 100644 docs/manual/caching.html create mode 100644 docs/manual/caching.html.en create mode 100644 docs/manual/configuring.html create mode 100644 docs/manual/configuring.html.de create mode 100644 docs/manual/configuring.html.en create mode 100644 docs/manual/configuring.html.ja.euc-jp create mode 100644 docs/manual/configuring.html.ko.euc-kr create mode 100644 docs/manual/content-negotiation.html create mode 100644 docs/manual/content-negotiation.html.en create mode 100644 docs/manual/content-negotiation.html.ja.euc-jp create mode 100644 docs/manual/content-negotiation.html.ko.euc-kr create mode 100644 docs/manual/convenience.map create mode 100644 docs/manual/custom-error.html create mode 100644 docs/manual/custom-error.html.en create mode 100644 docs/manual/custom-error.html.es create mode 100644 docs/manual/custom-error.html.ja.euc-jp create mode 100644 docs/manual/custom-error.html.ko.euc-kr create mode 100644 docs/manual/developer/API.html create mode 100644 docs/manual/developer/API.html.en create mode 100644 docs/manual/developer/debugging.html create mode 100644 docs/manual/developer/debugging.html.en create mode 100644 docs/manual/developer/documenting.html create mode 100644 docs/manual/developer/documenting.html.en create mode 100644 docs/manual/developer/filters.html create mode 100644 docs/manual/developer/filters.html.en create mode 100644 docs/manual/developer/hooks.html create mode 100644 docs/manual/developer/hooks.html.en create mode 100644 docs/manual/developer/index.html create mode 100644 docs/manual/developer/index.html.en create mode 100644 docs/manual/developer/modules.html create mode 100644 docs/manual/developer/modules.html.en create mode 100644 docs/manual/developer/modules.html.ja.euc-jp create mode 100644 docs/manual/developer/request.html create mode 100644 docs/manual/developer/request.html.en create mode 100644 docs/manual/developer/thread_safety.html create mode 100644 docs/manual/developer/thread_safety.html.en create mode 100644 docs/manual/dns-caveats.html create mode 100644 docs/manual/dns-caveats.html.en create mode 100644 docs/manual/dns-caveats.html.ja.euc-jp create mode 100644 docs/manual/dns-caveats.html.ko.euc-kr create mode 100644 docs/manual/dso.html create mode 100644 docs/manual/dso.html.en create mode 100644 docs/manual/dso.html.ja.euc-jp create mode 100644 docs/manual/dso.html.ko.euc-kr create mode 100644 docs/manual/env.html create mode 100644 docs/manual/env.html.en create mode 100644 docs/manual/env.html.ja.euc-jp create mode 100644 docs/manual/env.html.ko.euc-kr create mode 100644 docs/manual/faq/all_in_one.html create mode 100644 docs/manual/faq/all_in_one.html.en create mode 100644 docs/manual/faq/all_in_one.html.ja.euc-jp create mode 100644 docs/manual/faq/all_in_one.html.ko.euc-kr create mode 100644 docs/manual/faq/background.html create mode 100644 docs/manual/faq/background.html.en create mode 100644 docs/manual/faq/error.html create mode 100644 docs/manual/faq/error.html.en create mode 100644 docs/manual/faq/error.html.ja.euc-jp create mode 100644 docs/manual/faq/error.html.ko.euc-kr create mode 100644 docs/manual/faq/index.html create mode 100644 docs/manual/faq/index.html.en create mode 100644 docs/manual/faq/index.html.ja.euc-jp create mode 100644 docs/manual/faq/index.html.ko.euc-kr create mode 100644 docs/manual/faq/support.html create mode 100644 docs/manual/faq/support.html.en create mode 100644 docs/manual/faq/support.html.ja.euc-jp create mode 100644 docs/manual/faq/support.html.ko.euc-kr create mode 100644 docs/manual/filter.html create mode 100644 docs/manual/filter.html.en create mode 100644 docs/manual/filter.html.es create mode 100644 docs/manual/filter.html.fr create mode 100644 docs/manual/filter.html.ja.euc-jp create mode 100644 docs/manual/filter.html.ko.euc-kr create mode 100644 docs/manual/glossary.html create mode 100644 docs/manual/glossary.html.de create mode 100644 docs/manual/glossary.html.en create mode 100644 docs/manual/glossary.html.es create mode 100644 docs/manual/glossary.html.ko.euc-kr create mode 100644 docs/manual/handler.html create mode 100644 docs/manual/handler.html.en create mode 100644 docs/manual/handler.html.es create mode 100644 docs/manual/handler.html.ja.euc-jp create mode 100644 docs/manual/handler.html.ko.euc-kr create mode 100644 docs/manual/handler.html.ru.koi8-r create mode 100644 docs/manual/howto/access.html create mode 100644 docs/manual/howto/access.html.en create mode 100644 docs/manual/howto/auth.html create mode 100644 docs/manual/howto/auth.html.en create mode 100644 docs/manual/howto/auth.html.ja.euc-jp create mode 100644 docs/manual/howto/auth.html.ko.euc-kr create mode 100644 docs/manual/howto/cgi.html create mode 100644 docs/manual/howto/cgi.html.en create mode 100644 docs/manual/howto/cgi.html.ja.euc-jp create mode 100644 docs/manual/howto/cgi.html.ko.euc-kr create mode 100644 docs/manual/howto/htaccess.html create mode 100644 docs/manual/howto/htaccess.html.en create mode 100644 docs/manual/howto/htaccess.html.ja.euc-jp create mode 100644 docs/manual/howto/htaccess.html.ko.euc-kr create mode 100644 docs/manual/howto/htaccess.html.pt-br create mode 100644 docs/manual/howto/index.html create mode 100644 docs/manual/howto/index.html.en create mode 100644 docs/manual/howto/index.html.ja.euc-jp create mode 100644 docs/manual/howto/index.html.ko.euc-kr create mode 100644 docs/manual/howto/public_html.html create mode 100644 docs/manual/howto/public_html.html.en create mode 100644 docs/manual/howto/public_html.html.ja.euc-jp create mode 100644 docs/manual/howto/public_html.html.ko.euc-kr create mode 100644 docs/manual/howto/ssi.html create mode 100644 docs/manual/howto/ssi.html.en create mode 100644 docs/manual/howto/ssi.html.ja.euc-jp create mode 100644 docs/manual/howto/ssi.html.ko.euc-kr create mode 100644 docs/manual/images/apache_header.gif create mode 100644 docs/manual/images/caching_fig1.gif create mode 100644 docs/manual/images/caching_fig1.png create mode 100644 docs/manual/images/custom_errordocs.png create mode 100644 docs/manual/images/down.gif create mode 100644 docs/manual/images/favicon.ico create mode 100644 docs/manual/images/feather.gif create mode 100644 docs/manual/images/feather.png create mode 100644 docs/manual/images/filter_arch.png create mode 100644 docs/manual/images/home.gif create mode 100644 docs/manual/images/index.gif create mode 100644 docs/manual/images/left.gif create mode 100644 docs/manual/images/mod_filter_new.gif create mode 100644 docs/manual/images/mod_filter_new.png create mode 100644 docs/manual/images/mod_filter_old.gif create mode 100644 docs/manual/images/mod_rewrite_fig1.gif create mode 100644 docs/manual/images/mod_rewrite_fig1.png create mode 100644 docs/manual/images/mod_rewrite_fig2.gif create mode 100644 docs/manual/images/mod_rewrite_fig2.png create mode 100644 docs/manual/images/pixel.gif create mode 100644 docs/manual/images/right.gif create mode 100644 docs/manual/images/ssl_intro_fig1.gif create mode 100644 docs/manual/images/ssl_intro_fig1.png create mode 100644 docs/manual/images/ssl_intro_fig2.gif create mode 100644 docs/manual/images/ssl_intro_fig2.png create mode 100644 docs/manual/images/ssl_intro_fig3.gif create mode 100644 docs/manual/images/ssl_intro_fig3.png create mode 100644 docs/manual/images/sub.gif create mode 100644 docs/manual/images/up.gif create mode 100644 docs/manual/index.html create mode 100644 docs/manual/index.html.de create mode 100644 docs/manual/index.html.en create mode 100644 docs/manual/index.html.es create mode 100644 docs/manual/index.html.fr create mode 100644 docs/manual/index.html.ja.euc-jp create mode 100644 docs/manual/index.html.ko.euc-kr create mode 100644 docs/manual/index.html.pt-br create mode 100644 docs/manual/install.html create mode 100644 docs/manual/install.html.de create mode 100644 docs/manual/install.html.en create mode 100644 docs/manual/install.html.es create mode 100644 docs/manual/install.html.fr create mode 100644 docs/manual/install.html.ja.euc-jp create mode 100644 docs/manual/install.html.ko.euc-kr create mode 100644 docs/manual/invoking.html create mode 100644 docs/manual/invoking.html.de create mode 100644 docs/manual/invoking.html.en create mode 100644 docs/manual/invoking.html.es create mode 100644 docs/manual/invoking.html.ja.euc-jp create mode 100644 docs/manual/invoking.html.ko.euc-kr create mode 100644 docs/manual/invoking.html.ru.koi8-r create mode 100644 docs/manual/license.html create mode 100644 docs/manual/license.html.en create mode 100644 docs/manual/logs.html create mode 100644 docs/manual/logs.html.en create mode 100644 docs/manual/logs.html.ja.euc-jp create mode 100644 docs/manual/logs.html.ko.euc-kr create mode 100644 docs/manual/misc/index.html create mode 100644 docs/manual/misc/index.html.en create mode 100644 docs/manual/misc/index.html.ko.euc-kr create mode 100644 docs/manual/misc/perf-tuning.html create mode 100644 docs/manual/misc/perf-tuning.html.en create mode 100644 docs/manual/misc/perf-tuning.html.ko.euc-kr create mode 100644 docs/manual/misc/relevant_standards.html create mode 100644 docs/manual/misc/relevant_standards.html.en create mode 100644 docs/manual/misc/relevant_standards.html.ko.euc-kr create mode 100644 docs/manual/misc/rewriteguide.html create mode 100644 docs/manual/misc/rewriteguide.html.en create mode 100644 docs/manual/misc/rewriteguide.html.ko.euc-kr create mode 100644 docs/manual/misc/security_tips.html create mode 100644 docs/manual/misc/security_tips.html.en create mode 100644 docs/manual/misc/security_tips.html.ko.euc-kr create mode 100644 docs/manual/mod/beos.html create mode 100644 docs/manual/mod/beos.html.de create mode 100644 docs/manual/mod/beos.html.en create mode 100644 docs/manual/mod/beos.html.es create mode 100644 docs/manual/mod/beos.html.ko.euc-kr create mode 100644 docs/manual/mod/core.html create mode 100644 docs/manual/mod/core.html.de create mode 100644 docs/manual/mod/core.html.en create mode 100644 docs/manual/mod/core.html.ja.euc-jp create mode 100644 docs/manual/mod/directive-dict.html create mode 100644 docs/manual/mod/directive-dict.html.en create mode 100644 docs/manual/mod/directive-dict.html.ja.euc-jp create mode 100644 docs/manual/mod/directive-dict.html.ko.euc-kr create mode 100644 docs/manual/mod/directives.html create mode 100644 docs/manual/mod/directives.html.de create mode 100644 docs/manual/mod/directives.html.en create mode 100644 docs/manual/mod/directives.html.es create mode 100644 docs/manual/mod/directives.html.ja.euc-jp create mode 100644 docs/manual/mod/directives.html.ko.euc-kr create mode 100644 docs/manual/mod/directives.html.ru.koi8-r create mode 100644 docs/manual/mod/event.html create mode 100644 docs/manual/mod/event.html.en create mode 100644 docs/manual/mod/index.html create mode 100644 docs/manual/mod/index.html.de create mode 100644 docs/manual/mod/index.html.en create mode 100644 docs/manual/mod/index.html.es create mode 100644 docs/manual/mod/index.html.ja.euc-jp create mode 100644 docs/manual/mod/index.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_actions.html create mode 100644 docs/manual/mod/mod_actions.html.de create mode 100644 docs/manual/mod/mod_actions.html.en create mode 100644 docs/manual/mod/mod_actions.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_actions.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_alias.html create mode 100644 docs/manual/mod/mod_alias.html.en create mode 100644 docs/manual/mod/mod_alias.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_alias.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_asis.html create mode 100644 docs/manual/mod/mod_asis.html.en create mode 100644 docs/manual/mod/mod_asis.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_asis.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_auth_basic.html create mode 100644 docs/manual/mod/mod_auth_basic.html.en create mode 100644 docs/manual/mod/mod_auth_basic.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_auth_basic.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_auth_digest.html create mode 100644 docs/manual/mod/mod_auth_digest.html.en create mode 100644 docs/manual/mod/mod_auth_digest.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authn_alias.html create mode 100644 docs/manual/mod/mod_authn_alias.html.en create mode 100644 docs/manual/mod/mod_authn_anon.html create mode 100644 docs/manual/mod/mod_authn_anon.html.en create mode 100644 docs/manual/mod/mod_authn_anon.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authn_anon.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authn_dbd.html create mode 100644 docs/manual/mod/mod_authn_dbd.html.en create mode 100644 docs/manual/mod/mod_authn_dbm.html create mode 100644 docs/manual/mod/mod_authn_dbm.html.en create mode 100644 docs/manual/mod/mod_authn_dbm.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authn_dbm.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authn_default.html create mode 100644 docs/manual/mod/mod_authn_default.html.en create mode 100644 docs/manual/mod/mod_authn_default.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authn_default.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authn_file.html create mode 100644 docs/manual/mod/mod_authn_file.html.en create mode 100644 docs/manual/mod/mod_authn_file.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authn_file.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authnz_ldap.html create mode 100644 docs/manual/mod/mod_authnz_ldap.html.en create mode 100644 docs/manual/mod/mod_authz_dbm.html create mode 100644 docs/manual/mod/mod_authz_dbm.html.en create mode 100644 docs/manual/mod/mod_authz_dbm.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authz_default.html create mode 100644 docs/manual/mod/mod_authz_default.html.en create mode 100644 docs/manual/mod/mod_authz_default.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authz_default.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authz_groupfile.html create mode 100644 docs/manual/mod/mod_authz_groupfile.html.en create mode 100644 docs/manual/mod/mod_authz_groupfile.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authz_host.html create mode 100644 docs/manual/mod/mod_authz_host.html.en create mode 100644 docs/manual/mod/mod_authz_host.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authz_host.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authz_owner.html create mode 100644 docs/manual/mod/mod_authz_owner.html.en create mode 100644 docs/manual/mod/mod_authz_owner.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authz_owner.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_authz_user.html create mode 100644 docs/manual/mod/mod_authz_user.html.en create mode 100644 docs/manual/mod/mod_authz_user.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_authz_user.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_autoindex.html create mode 100644 docs/manual/mod/mod_autoindex.html.en create mode 100644 docs/manual/mod/mod_autoindex.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_autoindex.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_cache.html create mode 100644 docs/manual/mod/mod_cache.html.en create mode 100644 docs/manual/mod/mod_cache.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_cache.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_cern_meta.html create mode 100644 docs/manual/mod/mod_cern_meta.html.en create mode 100644 docs/manual/mod/mod_cern_meta.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_cgi.html create mode 100644 docs/manual/mod/mod_cgi.html.en create mode 100644 docs/manual/mod/mod_cgi.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_cgi.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_cgid.html create mode 100644 docs/manual/mod/mod_cgid.html.en create mode 100644 docs/manual/mod/mod_cgid.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_cgid.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_charset_lite.html create mode 100644 docs/manual/mod/mod_charset_lite.html.en create mode 100644 docs/manual/mod/mod_charset_lite.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_dav.html create mode 100644 docs/manual/mod/mod_dav.html.en create mode 100644 docs/manual/mod/mod_dav.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_dav.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_dav_fs.html create mode 100644 docs/manual/mod/mod_dav_fs.html.en create mode 100644 docs/manual/mod/mod_dav_fs.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_dav_fs.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_dav_lock.html create mode 100644 docs/manual/mod/mod_dav_lock.html.en create mode 100644 docs/manual/mod/mod_dav_lock.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_dbd.html create mode 100644 docs/manual/mod/mod_dbd.html.en create mode 100644 docs/manual/mod/mod_deflate.html create mode 100644 docs/manual/mod/mod_deflate.html.en create mode 100644 docs/manual/mod/mod_deflate.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_deflate.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_dir.html create mode 100644 docs/manual/mod/mod_dir.html.en create mode 100644 docs/manual/mod/mod_dir.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_dir.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_disk_cache.html create mode 100644 docs/manual/mod/mod_disk_cache.html.en create mode 100644 docs/manual/mod/mod_disk_cache.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_disk_cache.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_dumpio.html create mode 100644 docs/manual/mod/mod_dumpio.html.en create mode 100644 docs/manual/mod/mod_dumpio.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_echo.html create mode 100644 docs/manual/mod/mod_echo.html.en create mode 100644 docs/manual/mod/mod_echo.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_echo.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_env.html create mode 100644 docs/manual/mod/mod_env.html.en create mode 100644 docs/manual/mod/mod_env.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_env.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_example.html create mode 100644 docs/manual/mod/mod_example.html.en create mode 100644 docs/manual/mod/mod_example.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_expires.html create mode 100644 docs/manual/mod/mod_expires.html.en create mode 100644 docs/manual/mod/mod_expires.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_expires.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_ext_filter.html create mode 100644 docs/manual/mod/mod_ext_filter.html.en create mode 100644 docs/manual/mod/mod_ext_filter.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_ext_filter.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_file_cache.html create mode 100644 docs/manual/mod/mod_file_cache.html.en create mode 100644 docs/manual/mod/mod_file_cache.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_filter.html create mode 100644 docs/manual/mod/mod_filter.html.en create mode 100644 docs/manual/mod/mod_headers.html create mode 100644 docs/manual/mod/mod_headers.html.en create mode 100644 docs/manual/mod/mod_headers.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_headers.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_ident.html create mode 100644 docs/manual/mod/mod_ident.html.en create mode 100644 docs/manual/mod/mod_ident.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_imagemap.html create mode 100644 docs/manual/mod/mod_imagemap.html.en create mode 100644 docs/manual/mod/mod_imagemap.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_include.html create mode 100644 docs/manual/mod/mod_include.html.en create mode 100644 docs/manual/mod/mod_include.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_info.html create mode 100644 docs/manual/mod/mod_info.html.en create mode 100644 docs/manual/mod/mod_info.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_info.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_isapi.html create mode 100644 docs/manual/mod/mod_isapi.html.en create mode 100644 docs/manual/mod/mod_isapi.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_ldap.html create mode 100644 docs/manual/mod/mod_ldap.html.en create mode 100644 docs/manual/mod/mod_log_config.html create mode 100644 docs/manual/mod/mod_log_config.html.en create mode 100644 docs/manual/mod/mod_log_config.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_log_config.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_log_forensic.html create mode 100644 docs/manual/mod/mod_log_forensic.html.en create mode 100644 docs/manual/mod/mod_log_forensic.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_logio.html create mode 100644 docs/manual/mod/mod_logio.html.en create mode 100644 docs/manual/mod/mod_logio.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_logio.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_mem_cache.html create mode 100644 docs/manual/mod/mod_mem_cache.html.en create mode 100644 docs/manual/mod/mod_mem_cache.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_mem_cache.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_mime.html create mode 100644 docs/manual/mod/mod_mime.html.en create mode 100644 docs/manual/mod/mod_mime.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_mime_magic.html create mode 100644 docs/manual/mod/mod_mime_magic.html.en create mode 100644 docs/manual/mod/mod_negotiation.html create mode 100644 docs/manual/mod/mod_negotiation.html.en create mode 100644 docs/manual/mod/mod_negotiation.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_nw_ssl.html create mode 100644 docs/manual/mod/mod_nw_ssl.html.en create mode 100644 docs/manual/mod/mod_proxy.html create mode 100644 docs/manual/mod/mod_proxy.html.en create mode 100644 docs/manual/mod/mod_proxy.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_proxy_ajp.html create mode 100644 docs/manual/mod/mod_proxy_ajp.html.en create mode 100644 docs/manual/mod/mod_proxy_ajp.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_proxy_balancer.html create mode 100644 docs/manual/mod/mod_proxy_balancer.html.en create mode 100644 docs/manual/mod/mod_proxy_balancer.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_proxy_connect.html create mode 100644 docs/manual/mod/mod_proxy_connect.html.en create mode 100644 docs/manual/mod/mod_proxy_ftp.html create mode 100644 docs/manual/mod/mod_proxy_ftp.html.en create mode 100644 docs/manual/mod/mod_proxy_http.html create mode 100644 docs/manual/mod/mod_proxy_http.html.en create mode 100644 docs/manual/mod/mod_rewrite.html create mode 100644 docs/manual/mod/mod_rewrite.html.en create mode 100644 docs/manual/mod/mod_setenvif.html create mode 100644 docs/manual/mod/mod_setenvif.html.en create mode 100644 docs/manual/mod/mod_setenvif.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_setenvif.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_so.html create mode 100644 docs/manual/mod/mod_so.html.en create mode 100644 docs/manual/mod/mod_so.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_so.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_speling.html create mode 100644 docs/manual/mod/mod_speling.html.en create mode 100644 docs/manual/mod/mod_speling.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_speling.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_ssl.html create mode 100644 docs/manual/mod/mod_ssl.html.en create mode 100644 docs/manual/mod/mod_status.html create mode 100644 docs/manual/mod/mod_status.html.en create mode 100644 docs/manual/mod/mod_status.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_status.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_suexec.html create mode 100644 docs/manual/mod/mod_suexec.html.en create mode 100644 docs/manual/mod/mod_suexec.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_suexec.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_unique_id.html create mode 100644 docs/manual/mod/mod_unique_id.html.en create mode 100644 docs/manual/mod/mod_unique_id.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_unique_id.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_userdir.html create mode 100644 docs/manual/mod/mod_userdir.html.en create mode 100644 docs/manual/mod/mod_userdir.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_userdir.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_usertrack.html create mode 100644 docs/manual/mod/mod_usertrack.html.en create mode 100644 docs/manual/mod/mod_version.html create mode 100644 docs/manual/mod/mod_version.html.en create mode 100644 docs/manual/mod/mod_version.html.ja.euc-jp create mode 100644 docs/manual/mod/mod_version.html.ko.euc-kr create mode 100644 docs/manual/mod/mod_vhost_alias.html create mode 100644 docs/manual/mod/mod_vhost_alias.html.en create mode 100644 docs/manual/mod/module-dict.html create mode 100644 docs/manual/mod/module-dict.html.en create mode 100644 docs/manual/mod/module-dict.html.ja.euc-jp create mode 100644 docs/manual/mod/module-dict.html.ko.euc-kr create mode 100644 docs/manual/mod/mpm_common.html create mode 100644 docs/manual/mod/mpm_common.html.de create mode 100644 docs/manual/mod/mpm_common.html.en create mode 100644 docs/manual/mod/mpm_common.html.ja.euc-jp create mode 100644 docs/manual/mod/mpm_netware.html create mode 100644 docs/manual/mod/mpm_netware.html.en create mode 100644 docs/manual/mod/mpm_winnt.html create mode 100644 docs/manual/mod/mpm_winnt.html.de create mode 100644 docs/manual/mod/mpm_winnt.html.en create mode 100644 docs/manual/mod/mpm_winnt.html.ja.euc-jp create mode 100644 docs/manual/mod/mpmt_os2.html create mode 100644 docs/manual/mod/mpmt_os2.html.en create mode 100644 docs/manual/mod/prefork.html create mode 100644 docs/manual/mod/prefork.html.de create mode 100644 docs/manual/mod/prefork.html.en create mode 100644 docs/manual/mod/prefork.html.ja.euc-jp create mode 100644 docs/manual/mod/quickreference.html create mode 100644 docs/manual/mod/quickreference.html.de create mode 100644 docs/manual/mod/quickreference.html.en create mode 100644 docs/manual/mod/quickreference.html.es create mode 100644 docs/manual/mod/quickreference.html.ja.euc-jp create mode 100644 docs/manual/mod/quickreference.html.ko.euc-kr create mode 100644 docs/manual/mod/quickreference.html.ru.koi8-r create mode 100644 docs/manual/mod/worker.html create mode 100644 docs/manual/mod/worker.html.de create mode 100644 docs/manual/mod/worker.html.en create mode 100644 docs/manual/mod/worker.html.ja.euc-jp create mode 100644 docs/manual/mpm.html create mode 100644 docs/manual/mpm.html.de create mode 100644 docs/manual/mpm.html.en create mode 100644 docs/manual/mpm.html.es create mode 100644 docs/manual/mpm.html.ja.euc-jp create mode 100644 docs/manual/mpm.html.ko.euc-kr create mode 100644 docs/manual/new_features_2_0.html create mode 100644 docs/manual/new_features_2_0.html.de create mode 100644 docs/manual/new_features_2_0.html.en create mode 100644 docs/manual/new_features_2_0.html.fr create mode 100644 docs/manual/new_features_2_0.html.ja.euc-jp create mode 100644 docs/manual/new_features_2_0.html.ko.euc-kr create mode 100644 docs/manual/new_features_2_0.html.pt-br create mode 100644 docs/manual/new_features_2_0.html.ru.koi8-r create mode 100644 docs/manual/new_features_2_2.html create mode 100644 docs/manual/new_features_2_2.html.en create mode 100644 docs/manual/new_features_2_2.html.ko.euc-kr create mode 100644 docs/manual/new_features_2_2.html.pt-br create mode 100644 docs/manual/platform/ebcdic.html create mode 100644 docs/manual/platform/ebcdic.html.en create mode 100644 docs/manual/platform/ebcdic.html.ko.euc-kr create mode 100644 docs/manual/platform/index.html create mode 100644 docs/manual/platform/index.html.en create mode 100644 docs/manual/platform/index.html.ko.euc-kr create mode 100644 docs/manual/platform/netware.html create mode 100644 docs/manual/platform/netware.html.en create mode 100644 docs/manual/platform/netware.html.ko.euc-kr create mode 100644 docs/manual/platform/perf-hp.html create mode 100644 docs/manual/platform/perf-hp.html.en create mode 100644 docs/manual/platform/perf-hp.html.ko.euc-kr create mode 100644 docs/manual/platform/win_compiling.html create mode 100644 docs/manual/platform/win_compiling.html.en create mode 100644 docs/manual/platform/win_compiling.html.ko.euc-kr create mode 100644 docs/manual/platform/windows.html create mode 100644 docs/manual/platform/windows.html.en create mode 100644 docs/manual/platform/windows.html.ko.euc-kr create mode 100644 docs/manual/programs/ab.html create mode 100644 docs/manual/programs/ab.html.en create mode 100644 docs/manual/programs/ab.html.ko.euc-kr create mode 100644 docs/manual/programs/apachectl.html create mode 100644 docs/manual/programs/apachectl.html.en create mode 100644 docs/manual/programs/apachectl.html.ko.euc-kr create mode 100644 docs/manual/programs/apxs.html create mode 100644 docs/manual/programs/apxs.html.en create mode 100644 docs/manual/programs/apxs.html.ko.euc-kr create mode 100644 docs/manual/programs/configure.html create mode 100644 docs/manual/programs/configure.html.en create mode 100644 docs/manual/programs/configure.html.ko.euc-kr create mode 100644 docs/manual/programs/dbmmanage.html create mode 100644 docs/manual/programs/dbmmanage.html.en create mode 100644 docs/manual/programs/dbmmanage.html.ko.euc-kr create mode 100644 docs/manual/programs/htcacheclean.html create mode 100644 docs/manual/programs/htcacheclean.html.en create mode 100644 docs/manual/programs/htcacheclean.html.ko.euc-kr create mode 100644 docs/manual/programs/htdbm.html create mode 100644 docs/manual/programs/htdbm.html.en create mode 100644 docs/manual/programs/htdigest.html create mode 100644 docs/manual/programs/htdigest.html.en create mode 100644 docs/manual/programs/htdigest.html.ko.euc-kr create mode 100644 docs/manual/programs/htpasswd.html create mode 100644 docs/manual/programs/htpasswd.html.en create mode 100644 docs/manual/programs/htpasswd.html.ko.euc-kr create mode 100644 docs/manual/programs/httpd.html create mode 100644 docs/manual/programs/httpd.html.en create mode 100644 docs/manual/programs/httpd.html.ko.euc-kr create mode 100644 docs/manual/programs/httxt2dbm.html create mode 100644 docs/manual/programs/httxt2dbm.html.en create mode 100644 docs/manual/programs/index.html create mode 100644 docs/manual/programs/index.html.en create mode 100644 docs/manual/programs/index.html.es create mode 100644 docs/manual/programs/index.html.ko.euc-kr create mode 100644 docs/manual/programs/index.html.ru.koi8-r create mode 100644 docs/manual/programs/logresolve.html create mode 100644 docs/manual/programs/logresolve.html.en create mode 100644 docs/manual/programs/logresolve.html.ko.euc-kr create mode 100644 docs/manual/programs/other.html create mode 100644 docs/manual/programs/other.html.en create mode 100644 docs/manual/programs/other.html.ko.euc-kr create mode 100644 docs/manual/programs/rotatelogs.html create mode 100644 docs/manual/programs/rotatelogs.html.en create mode 100644 docs/manual/programs/rotatelogs.html.ko.euc-kr create mode 100644 docs/manual/programs/suexec.html create mode 100644 docs/manual/programs/suexec.html.en create mode 100644 docs/manual/programs/suexec.html.ko.euc-kr create mode 100644 docs/manual/rewrite/index.html create mode 100644 docs/manual/rewrite/index.html.en create mode 100644 docs/manual/rewrite/rewrite_guide.html create mode 100644 docs/manual/rewrite/rewrite_guide.html.en create mode 100644 docs/manual/rewrite/rewrite_guide_advanced.html create mode 100644 docs/manual/rewrite/rewrite_guide_advanced.html.en create mode 100644 docs/manual/rewrite/rewrite_intro.html create mode 100644 docs/manual/rewrite/rewrite_intro.html.en create mode 100644 docs/manual/rewrite/rewrite_tech.html create mode 100644 docs/manual/rewrite/rewrite_tech.html.en create mode 100644 docs/manual/sections.html create mode 100644 docs/manual/sections.html.en create mode 100644 docs/manual/sections.html.ja.euc-jp create mode 100644 docs/manual/sections.html.ko.euc-kr create mode 100644 docs/manual/server-wide.html create mode 100644 docs/manual/server-wide.html.en create mode 100644 docs/manual/server-wide.html.ja.euc-jp create mode 100644 docs/manual/server-wide.html.ko.euc-kr create mode 100644 docs/manual/sitemap.html create mode 100644 docs/manual/sitemap.html.de create mode 100644 docs/manual/sitemap.html.en create mode 100644 docs/manual/sitemap.html.es create mode 100644 docs/manual/sitemap.html.ja.euc-jp create mode 100644 docs/manual/sitemap.html.ko.euc-kr create mode 100644 docs/manual/ssl/index.html create mode 100644 docs/manual/ssl/index.html.en create mode 100644 docs/manual/ssl/index.html.ja.euc-jp create mode 100644 docs/manual/ssl/ssl_compat.html create mode 100644 docs/manual/ssl/ssl_compat.html.en create mode 100644 docs/manual/ssl/ssl_faq.html create mode 100644 docs/manual/ssl/ssl_faq.html.en create mode 100644 docs/manual/ssl/ssl_howto.html create mode 100644 docs/manual/ssl/ssl_howto.html.en create mode 100644 docs/manual/ssl/ssl_intro.html create mode 100644 docs/manual/ssl/ssl_intro.html.en create mode 100644 docs/manual/ssl/ssl_intro.html.ja.euc-jp create mode 100644 docs/manual/stopping.html create mode 100644 docs/manual/stopping.html.de create mode 100644 docs/manual/stopping.html.en create mode 100644 docs/manual/stopping.html.es create mode 100644 docs/manual/stopping.html.ja.euc-jp create mode 100644 docs/manual/stopping.html.ko.euc-kr create mode 100644 docs/manual/style/build.properties create mode 100644 docs/manual/style/common.dtd create mode 100644 docs/manual/style/css/manual-chm.css create mode 100644 docs/manual/style/css/manual-loose-100pc.css create mode 100644 docs/manual/style/css/manual-print.css create mode 100644 docs/manual/style/css/manual-zip-100pc.css create mode 100644 docs/manual/style/css/manual-zip.css create mode 100644 docs/manual/style/css/manual.css create mode 100644 docs/manual/style/faq.dtd create mode 100644 docs/manual/style/lang.dtd create mode 100644 docs/manual/style/latex/atbeginend.sty create mode 100644 docs/manual/style/latex/common.xsl create mode 100644 docs/manual/style/latex/directiveindex.xsl create mode 100644 docs/manual/style/latex/faq.xsl create mode 100644 docs/manual/style/latex/html.xsl create mode 100644 docs/manual/style/latex/latex.xsl create mode 100644 docs/manual/style/latex/manualpage.xsl create mode 100644 docs/manual/style/latex/moduleindex.xsl create mode 100644 docs/manual/style/latex/quickreference.xsl create mode 100644 docs/manual/style/latex/synopsis.xsl create mode 100644 docs/manual/style/manual.de.xsl create mode 100644 docs/manual/style/manual.en.xsl create mode 100644 docs/manual/style/manual.es.xsl create mode 100644 docs/manual/style/manual.fr.xsl create mode 100644 docs/manual/style/manual.ja.xsl create mode 100644 docs/manual/style/manual.ko.xsl create mode 100644 docs/manual/style/manual.pt-br.xsl create mode 100644 docs/manual/style/manual.ru.xsl create mode 100644 docs/manual/style/manualpage.dtd create mode 100644 docs/manual/style/modulesynopsis.dtd create mode 100644 docs/manual/style/sitemap.dtd create mode 100644 docs/manual/style/version.ent create mode 100644 docs/manual/style/xsl/common.xsl create mode 100644 docs/manual/style/xsl/convmap.xsl create mode 100644 docs/manual/style/xsl/directiveindex.xsl create mode 100644 docs/manual/style/xsl/faq.xsl create mode 100644 docs/manual/style/xsl/hhc.xsl create mode 100644 docs/manual/style/xsl/hhp.xsl create mode 100644 docs/manual/style/xsl/indexpage.xsl create mode 100644 docs/manual/style/xsl/language.xsl create mode 100644 docs/manual/style/xsl/maf.xsl create mode 100644 docs/manual/style/xsl/manualpage.xsl create mode 100644 docs/manual/style/xsl/moduleindex.xsl create mode 100644 docs/manual/style/xsl/nroff.xsl create mode 100644 docs/manual/style/xsl/quickreference.xsl create mode 100644 docs/manual/style/xsl/sitemap.xsl create mode 100644 docs/manual/style/xsl/synopsis.xsl create mode 100644 docs/manual/style/xsl/typemap.xsl create mode 100644 docs/manual/style/xsl/util/modtrans.xsl create mode 100644 docs/manual/suexec.html create mode 100644 docs/manual/suexec.html.en create mode 100644 docs/manual/suexec.html.ja.euc-jp create mode 100644 docs/manual/suexec.html.ko.euc-kr create mode 100644 docs/manual/upgrading.html create mode 100644 docs/manual/upgrading.html.de create mode 100644 docs/manual/upgrading.html.en create mode 100644 docs/manual/upgrading.html.ja.euc-jp create mode 100644 docs/manual/upgrading.html.ko.euc-kr create mode 100644 docs/manual/upgrading.html.pt-br create mode 100644 docs/manual/upgrading.html.ru.koi8-r create mode 100644 docs/manual/urlmapping.html create mode 100644 docs/manual/urlmapping.html.en create mode 100644 docs/manual/urlmapping.html.ja.euc-jp create mode 100644 docs/manual/urlmapping.html.ko.euc-kr create mode 100644 docs/manual/vhosts/details.html create mode 100644 docs/manual/vhosts/details.html.en create mode 100644 docs/manual/vhosts/details.html.fr create mode 100644 docs/manual/vhosts/details.html.ko.euc-kr create mode 100644 docs/manual/vhosts/examples.html create mode 100644 docs/manual/vhosts/examples.html.en create mode 100644 docs/manual/vhosts/examples.html.fr create mode 100644 docs/manual/vhosts/examples.html.ja.euc-jp create mode 100644 docs/manual/vhosts/examples.html.ko.euc-kr create mode 100644 docs/manual/vhosts/fd-limits.html create mode 100644 docs/manual/vhosts/fd-limits.html.en create mode 100644 docs/manual/vhosts/fd-limits.html.fr create mode 100644 docs/manual/vhosts/fd-limits.html.ja.euc-jp create mode 100644 docs/manual/vhosts/fd-limits.html.ko.euc-kr create mode 100644 docs/manual/vhosts/index.html create mode 100644 docs/manual/vhosts/index.html.de create mode 100644 docs/manual/vhosts/index.html.en create mode 100644 docs/manual/vhosts/index.html.fr create mode 100644 docs/manual/vhosts/index.html.ja.euc-jp create mode 100644 docs/manual/vhosts/index.html.ko.euc-kr create mode 100644 docs/manual/vhosts/index.html.ru.koi8-r create mode 100644 docs/manual/vhosts/ip-based.html create mode 100644 docs/manual/vhosts/ip-based.html.en create mode 100644 docs/manual/vhosts/ip-based.html.fr create mode 100644 docs/manual/vhosts/ip-based.html.ja.euc-jp create mode 100644 docs/manual/vhosts/ip-based.html.ko.euc-kr create mode 100644 docs/manual/vhosts/mass.html create mode 100644 docs/manual/vhosts/mass.html.en create mode 100644 docs/manual/vhosts/mass.html.ko.euc-kr create mode 100644 docs/manual/vhosts/name-based.html create mode 100644 docs/manual/vhosts/name-based.html.de create mode 100644 docs/manual/vhosts/name-based.html.en create mode 100644 docs/manual/vhosts/name-based.html.fr create mode 100644 docs/manual/vhosts/name-based.html.ja.euc-jp create mode 100644 docs/manual/vhosts/name-based.html.ko.euc-kr (limited to 'docs/manual') diff --git a/docs/manual/LICENSE b/docs/manual/LICENSE new file mode 100644 index 00000000..57bc88a1 --- /dev/null +++ b/docs/manual/LICENSE @@ -0,0 +1,202 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + diff --git a/docs/manual/bind.html b/docs/manual/bind.html new file mode 100644 index 00000000..c2af6387 --- /dev/null +++ b/docs/manual/bind.html @@ -0,0 +1,19 @@ +URI: bind.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: bind.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: bind.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: bind.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: bind.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/bind.html.de b/docs/manual/bind.html.de new file mode 100644 index 00000000..367296a7 --- /dev/null +++ b/docs/manual/bind.html.de @@ -0,0 +1,165 @@ + + + +Anbindung - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Anbindung

+
+

Verfügbare Sprachen:  de  | + en  | + fr  | + ja  | + ko 

+
+ +

Konfiguration der vom Apache verwendeten Adressen und Ports.

+
+ +
top
+
+

Überblick

+ + +
Referenzierte ModuleReferenzierte Direktiven
+ +

Beim Start bindet sich der Apache an bestimmte Adressen und Ports + der lokalen Maschine und wartet auf eingehende Anfragen. + Standardmäßig lauscht er an allen Adressen des Systems. + Es muss ihm jedoch mitgeteilt werden, an bestimmten Ports zu lauschen + oder nur an ausgewählten Adressen, bzw. einer Kombination aus + beidem. Dies wird oft mit der Funktionalität virtueller Hosts + kombiniert, die bestimmt, wie der Apache auf verschiedene IP-Adressen, + Hostnamen und Ports reagiert.

+ +

Die Direktive Listen + weist den Server an, eingehende Anfragen nur an bestimmten Ports oder + Adress/Port-Kombinationen zu akzeptieren. Wenn bei der Listen-Direktive nur eine Portnummer + angegeben wird, dann lauscht der Server auf allen Netzwerkinterfaces an + dem angegebenen Port. Ist auch eine IP-Adresse angegeben, dann lauscht der + Server an der angegebenen Schnittstelle auf dem angegebenen Port. Es + können mehrere Listen-Anweisungen verwendet werden, um + eine Reihe von Adressen und Ports anzugeben, an denen gelauscht werden + soll. Der Server wird dann auf Anfragen an jeder der abgehörten + Adressen und Ports antworten.

+ +

Um beispielsweise den Server zu veranlassen, sowohl an Port 80, als + auch an Port 8000 Verbindungen zu akzeptieren, geben Sie an:

+ +

+ Listen 80
+ Listen 8000 +

+ +

Um den Server Verbindungen an zwei bestimmten + Netzwerkinterfaces und Ports zu akzeptieren zu lassen, geben Sie an:

+ +

+ Listen 192.170.2.1:80
+ Listen 192.170.2.5:8000 +

+ +

IPv6-Adressen müssen wie im folgenden Beispiel in eckigen + Klammern angegeben werden:

+ +

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

+
top
+
+

Betrachtung von IPv6-Besonderheiten

+ + +

Eine wachsende Anzahl von Plattformen implementiert IPv6. Die + APR unterstützt IPv6 auf den meisten + dieser Plattformen und ermöglicht dem Apache, IPv6-Sockets + zu verwenden und Anfragen zu behandeln, die über IPv6 + gesendet wurden.

+ +

Für Apache-Administratoren kommt erschwerend die Frage hinzu, ob + IPv6-Sockets sowohl IPv4- als auch IPv6-Verbindungen + handhaben können. Zum Betrieb von IPv4-Verbindungen an + IPv6-Sockets werden auf IPv6 abgebildete IPv4-Adressen + (Anm.d.Ü.: so genannete IPv4-gemappte IPv6-Adressen) + verwendet, welche standardmäßig auf den meisten Plattformen + erlaubt sind. Unter FreeBSD, NetBSD und OpenBSD jedoch sind sie + standardmäßig deaktiviert, um den Systemgrundsätzen dieser + Plattformen zu entsprechen. Doch selbst auf Systemen, wo dies + standardmäßig dekativiert ist, kann dieses Verhalten mit einem + speziellen configure-Parameter für den Apache + geändert werden.

+ +

Auf der anderen Seite ist die Verwendung von gemappten Adressen bei + einigen Plattformen wie Linux und True64 der einzige + Weg, sowohl IPv4 wie auch IPv6 zu verwenden. Wenn Sie möchten, dass + der Apache IPv4- und IPv6-Verbindungen mit einem Minimum an Sockets + behandelt, was die Verwendung von IPv4-gemappten IPv6-Adressen + erfordert, dann müssen Sie die configure-Option --enable-v4-mapped angeben.

+ +

--enable-v4-mapped ist die Voreinstellung auf allen + Plattformen außer FreeBSD, NetBSD und OpenBSD, so dass Ihr Apache + wahrscheinlich so übersetzt wurde.

+ +

Geben Sie wie in dem folgenden Beispiel bei allen Listen-Anweisungen eine IPv4-Adresse + an, wenn Sie möchten, dass Ihr Apache lediglich IPv4-Adressen + behandelt, unabhängig davon, was Ihre Plattform und die APR + unterstützen:

+ +

+ Listen 0.0.0.0:80
+ Listen 192.170.2.1:80 +

+ +

Wenn Sie möchten, dass der Apache IPv4- und IPv6-Verbindungen an + separaten Sockets behandelt (d.h. IPv4-gemappte Adressen deaktiviert + werden sollen) und Ihre Plattform es unterstützt, dann müssen + Sie die configure-Option + --disable-v4-mapped angeben. + Unter FreeBSD, NetBSD und OpenBSD ist --disable-v4-mapped + voreingestellt.

+
top
+
+

Das Zusammenspiel mit virtuellen Hosts

+ + +

Listen implementiert keine + virtuellen Hosts. Es teilt dem Hauptserver lediglich mit, an welchen + Adressen und Ports er zu lauschen hat. Werden keine <VirtualHost>-Container + verwendet, verhält sich der Server bei allen angenommenen Anfragen + gleich. <VirtualHost>-Abschnitte können jedoch + dazu verwendet werden, ein unterschiedliches Verhalten für eine oder + mehrere Adressen und Ports festzulegen. Um einen virtuellen Host + einzurichten, muss dem Server zunächst mitgeteilt werden, an den + betreffenden Adressen und Ports zu lauschen. Dann sollte ein <VirtualHost>-Abschnitt für + eine bestimmte Adresse und einen Port erstellt werden, um das Verhalten + dieses virtuellen Hosts festzulegen. Beachten Sie bitte, dass auf einen + <VirtualHost> nicht + zugegriffen werden kann, wenn er für eine Adresse und einen Port + eingerichtet wurde, an dem der Server nicht lauscht.

+
+
+

Verfügbare Sprachen:  de  | + en  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en new file mode 100644 index 00000000..88856302 --- /dev/null +++ b/docs/manual/bind.html.en @@ -0,0 +1,161 @@ + + + +Binding - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Binding

+
+

Available Languages:  de  | + en  | + fr  | + ja  | + ko 

+
+ +

Configuring Apache to listen on specific addresses and ports.

+
+ +
top
+
+

Overview

+ + +
Related ModulesRelated Directives
+ + +

When Apache starts, it binds to some port and address on + the local machine and waits for incoming requests. By default, + it listens to all addresses on the machine. However, it needs to + be told to listen on specific ports, or to listen on only selected + addresses, or a combination. This is often combined with the + Virtual Host feature which determines how Apache responds to + different IP addresses, hostnames and ports.

+ +

The Listen + directive tells the server to accept + incoming requests only on the specified port or + address-and-port combinations. If only a port number is + specified in the Listen + directive, the server + listens to the given port on all interfaces. If an IP address + is given as well as a port, the server will listen on the given + port and interface. Multiple Listen directives may be used to + specify a number of addresses and ports to listen on. The + server will respond to requests from any of the listed + addresses and ports.

+ +

For example, to make the server accept connections on both + port 80 and port 8000, use:

+ +

+ Listen 80
+ Listen 8000 +

+ +

To make the server accept connections on two specified + interfaces and port numbers, use

+ +

+ Listen 192.170.2.1:80
+ Listen 192.170.2.5:8000 +

+ +

IPv6 addresses must be surrounded in square brackets, as in the + following example:

+ +

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

+
top
+
+

Special IPv6 Considerations

+ + +

A growing number of platforms implement IPv6, and + APR supports IPv6 on most of these platforms, + allowing Apache to allocate IPv6 sockets and handle requests which + were sent over IPv6.

+ +

One complicating factor for Apache administrators is whether or + not an IPv6 socket can handle both IPv4 connections and IPv6 + connections. Handling IPv4 connections with an IPv6 socket uses + IPv4-mapped IPv6 addresses, which are allowed by default on most + platforms but are disallowed by default on FreeBSD, NetBSD, and + OpenBSD in order to match the system-wide policy on those + platforms. But even on systems where it is disallowed by default, a + special configure parameter can change this behavior + for Apache.

+ +

On the other hand, on some platforms such as Linux and Tru64 the + only way to handle both IPv6 and IPv4 is to use + mapped addresses. If you want Apache to handle IPv4 and IPv6 connections + with a minimum of sockets, which requires using IPv4-mapped IPv6 + addresses, specify the --enable-v4-mapped configure option.

+ +

--enable-v4-mapped is the default on all platforms but + FreeBSD, NetBSD, and OpenBSD, so this is probably how your Apache was + built.

+ +

If you want Apache to handle IPv4 connections only, regardless of + what your platform and APR will support, specify an IPv4 address on all + Listen directives, as in the + following examples:

+ +

+ Listen 0.0.0.0:80
+ Listen 192.170.2.1:80 +

+ +

If your platform supports it and you want Apache to handle IPv4 and + IPv6 connections on separate sockets (i.e., to disable IPv4-mapped + addresses), specify the --disable-v4-mapped configure option. --disable-v4-mapped is the + default on FreeBSD, NetBSD, and OpenBSD.

+
top
+
+

How This Works With Virtual Hosts

+ + +

Listen does not implement + Virtual Hosts. It only tells the + main server what addresses and ports to listen to. If no + <VirtualHost> + directives are used, the server will behave + the same for all accepted requests. However, + <VirtualHost> + can be used to specify a different behavior + for one or more of the addresses and ports. To implement a + VirtualHost, the server must first be told to listen to the + address and port to be used. Then a + <VirtualHost> section + should be created for a specified address and port to set the + behavior of this virtual host. Note that if the + <VirtualHost> + is set for an address and port that the + server is not listening to, it cannot be accessed.

+
+
+

Available Languages:  de  | + en  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/bind.html.fr b/docs/manual/bind.html.fr new file mode 100644 index 00000000..2e443160 --- /dev/null +++ b/docs/manual/bind.html.fr @@ -0,0 +1,197 @@ + + + +Liaison - Serveur Apache HTTP + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur Apache HTTP Version 2.2

+
+
<-
+
+Apache > Serveur HTTP > Documentation > Version 2.2

Liaison

+
+

Langues Disponibles:  de  | + en  | + fr  | + ja  | + ko 

+
+
Cette traduction peut être périmée. Verifiez la version + Anglaise pour les changements récents.
+ +

Configuration des adresses et ports sur lesquels Apache écoute.

+
+ +
top
+
+

Informations générales

+ + +
Modules ApparentésDirectives Apparentées
+ + +

Au moment de son démarrage, Apache se lie à un port et à une + adresse IP sur la machine locale et se met en attente de requètes. + Par défaut, Apache écoute sur toutes les adresses de la machine. + Apache accepte d'écouter sur un ou plusieurs ports spécifiques, + sur une seule ou plusieurs adresses, ou encore sur une combinaison port-adresse. + Il est fréquent d'utiliser ces possibilités avec les fonctionnalités + de Serveurs Virtuels, qui permettent de faire répondre le serveur de + manière différente en fonction de l'adresse IP, du nom d'hôte ou + du port.

+ +

Le serveur interprète la directive + Listen + en acceptant les requètes seulement sur le port ou la combinaison + adresse IP + port passée en argument. Dans le cas où seul un port + est spécifié avec la directive + Listen, + le serveur se met à l'écoute sur le port spécifié, sur toutes + les interfaces et adresses de la machine. Si une adresse IP est + spécifiée en plus du port, le serveur n'écoute que sur l'adresse + et le port spécifié. Il est possible de configurer plusieurs adresses + et ports avec la directives + Listen + pour écoute par le serveur. Le serveur répond aux requètes faites + à toutes les adresses et ports énumérés.

+ + +

Par exemple, pour que le serveur accepte les connexions sur + les ports 80 et 8000, spécifiez :

+ +

+ Listen 80
+ Listen 8000 +

+ +

Pour qu'Apache accepte les connexions sur deux combinaisons + adresses + ports, spécifiez :

+ +

+ Listen 192.170.2.1:80
+ Listen 192.170.2.5:8000 +

+ +

Les adresses IPv6 sont acceptées, pourvu qu'elles soient spécifiées + entre crochets de la façon suivante :

+ +

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

+
top
+
+

Considérations Spéciales avec IPv6

+ + +

De plus en plus de plate-formes implémentent IPv6. APR + supporte IPv6 sur la plupart d'entre elles, si bien qu'Apache + peut assigner des interfaces de connexions IPv6 et répondre aux + requètes utilisant IPv6.

+ +

Une complication possible pour les administrateurs Apache est de + savoir si une interface de connexion IPv6 peut répondre aux deux types de + connexions IPv4 et IPv6. + Manipuler les connexions IPv4 avec une interface de connexion IPv6 + suppose l'utilisation d'adresses IPv6 mappées en IPv4, ce qui est + le cas par defaut sur la plupart des plate-formes, à l'exeption de FreeBSD, + NetBSD, et OpenBSD, cela en raison des politiques systèmes de ces plate-formes. + Mème sur des systèmes où cette fonctionnalité n'est pas activée par + défaut, une option de compilation permet de changer ce + fonctionnement pour Apache.

+

Pour qu'Apache puisse gérer à la fois les connexions IPv4 et IPv6 + avec un minimum d'interfaces de connexions, il faut permettre l'utilisation + des adresses + IPv6 mappées en IPv4, ce qui est possible en spécifiant l'option + + de compilation --enable-v4-mapped et en utilisant la + directive Listen + comme suit:

+ +

+ Listen 80 +

+ +

Si --enable-v4-mapped a été spécifié à la compilation, + les directives Listen + de la configuration par défaut sont de la forme ci-dessus. + --enable-v4-mapped est l'option de compilation + par défaut sur toutes les plate-formes, sauf FreeBSD, NetBSD, et + OpenBSD.

+ + +

Pour qu'Apache ne manipule que les connexions IPv4, en ignorant l'éventuel + support IPv6 de la plate-forme ou d'APR, une adresse IPv4 peut être + spécifié pour toutes les directives + Listen, + comme dans les exemples suivantss:

+ +

+ Listen 0.0.0.0:80
+ Listen 192.170.2.1:80 +

+ +

Pour qu'Apache manipule les connexions IPv4 et IPv6 sur des interfaces + différentes (c'est-à-dire, pour ne pas accepter les addresse IPv6 mappées + en IPv4), spécifier l'option de compilation --disable-v4-mapped + et utiliser des directives Listen + spécifiques telles que:

+

+ Listen [::]:80
+ Listen 0.0.0.0:80 +

+ +

Avec --disable-v4-mapped, la directive + Listen à l'intérieur + du fichier de configuration par défaut créé par Apache utilise la forme + ci-dessus. + --disable-v4-mapped est l'option de compilation par défaut sous + FreeBSD, NetBSD, et OpenBSD.

+
top
+
+

Faire fonctionner tout ceci avec les Serveurs Virtuels

+ + +

Listen + n'implémente aucun Serveur Virtuel. Cette directive sert simplement + à informer le serveur principal sur quels addresses et ports écouter. + Dans le cas où aucune section + <VirtualHost> + n'est utilisée, le serveur répondra de la mème manière pour toutes + les requètes qu'il acceptera. Cependant des sections + <VirtualHost> + peuvent être utilisées pour qu'Apache réagisse de façon différente à + une requète selon l'adresse ou le port. Avant d'implémenter + un Serveur Virtuel au moyen de la directive + <VirtualHost>, la directive + Listen + doit tre utilisée pour que le serveur écoute sur l'adresse + ou le port spécifié. Une section + <VirtualHost> + peut alors être utilisée pour définir la réaction du Serveur Virtuel pour une + adresse et un port spécifique. À noter que si un Serveur Virtuel est + positionné au moyen de la directive + <VirtualHost> + sur une adresse et un port sur lesquels le serveur n'est pas à l'écoute, + le Serveur Virtuel ne sera pas accessible.

+
+
+

Langues Disponibles:  de  | + en  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/bind.html.ja.euc-jp b/docs/manual/bind.html.ja.euc-jp new file mode 100644 index 00000000..5871f728 --- /dev/null +++ b/docs/manual/bind.html.ja.euc-jp @@ -0,0 +1,175 @@ + + + +¥Ð¥¤¥ó¥É - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥Ð¥¤¥ó¥É

+
+

Available Languages:  de  | + en  | + fr  | + ja  | + ko 

+
+ +

Apache ¤¬»ÈÍѤ¹¤ë¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ÎÀßÄê¤ò¤·¤Þ¤¹¡£

+
+ +
top
+
+

³µÍ×

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ + +

Apache ¤Ïµ¯Æ°»þ¤Ë¡¢¥í¡¼¥«¥ë¥Þ¥·¥ó¤Î¤¢¤ë¥Ý¡¼¥È¤ª¤è¤Ó¥¢¥É¥ì¥¹ + ¤ËÂФ·¤ÆÀܳ¤·¡¢¥ê¥¯¥¨¥¹¥È¤¬Íè¤ë¤Î¤òÂÔ¤Á¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥Þ¥·¥ó¤Î¤¹¤Ù¤Æ¤Î¥¢¥É¥ì¥¹¤ËÂФ·¤Æ listen ¤·¤Þ¤¹¡£ + ¤·¤«¤·¤Ê¤¬¤é¡¢ÆÃÄê¤Î¥Ý¡¼¥È¤«¡¢ÆÃÄê¤Î¥¢¥É¥ì¥¹¤Î¤ß¤«¡¢ + ¤Þ¤¿¤Ï¤½¤ì¤é¤ÎÁȤ߹ç¤ï¤»¤Î¤¤¤º¤ì¤«¤ò listen ¤¹¤ë¤è¤¦¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢°Û¤Ê¤ë IP ¥¢¥É¥ì¥¹¡¢¥Û¥¹¥È̾¡¢¥Ý¡¼¥È¤ËÂФ¹¤ë Apache + ¤Î±þÅúÊýË¡¤ò·èÄꤹ¤ë¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥Èµ¡Ç½¤ÈÁȤ߹ç¤ï¤»¤Æ»È¤ï¤ì¤Þ¤¹¡£

+ +

Listen + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¡¢ÆÃÄê¤Î¥Ý¡¼¥È¤ä¥¢¥É¥ì¥¹¡¦¥Ý¡¼¥È¤ÎÁȤ«¤é¤Î¤ßÆþ¤Ã¤Æ¤¯¤ë + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£ + ¤â¤·¥Ý¡¼¥ÈÈÖ¹æ¤Î¤ß¤¬ Listen + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢ + ¤¹¤Ù¤Æ¤Î¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤ÎÍ¿¤¨¤é¤ì¤¿¥Ý¡¼¥ÈÈÖ¹æ¤ò + listen ¤·¤Þ¤¹¡£ IP ¥¢¥É¥ì¥¹¤¬¥Ý¡¼¥ÈÈÖ¹æ¤ÈƱ»þ¤ËÍ¿¤¨¤é¤ì¤¿¾ì¹ç¤Ï¡¢ + ¥µ¡¼¥Ð¤ÏÍ¿¤¨¤é¤ì¤¿¥Ý¡¼¥È¤È¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤ò listen ¤·¤Þ¤¹¡£ + Ê£¿ô¤Î Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÍѤ¤¤Æ + ¤¤¤¯¤Ä¤«¤Î listen ¤¹¤ë¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤Ï¥ê¥¹¥È¤µ¤ì¤¿¥¢¥É¥ì¥¹¤ä¥Ý¡¼¥È¤«¤é¤Î¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤Ë + ÂФ·¤Æ±þÅú¤·¤Þ¤¹¡£

+ +

¤¿¤È¤¨¤Ð¡¢¥Ý¡¼¥È 80 ¤È 8000 ¤ÎξÊý¤ËÂФ·¤Æ¤ÎÀܳ¤ò¼õ¤±ÉÕ¤±¤ë¤Ë¤Ï

+ +

+ Listen 80
+ Listen 8000 +

+ +

¤È¤·¤Þ¤¹¡£ + Æó¤Ä¤Î»ØÄꤵ¤ì¤¿¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤È¥Ý¡¼¥ÈÈÖ¹æ¤ËÂФ·¤Æ¤ÎÀܳ¤ò¼õ¤±ÉÕ¤±¤ë¤Ë¤Ï¡¢ +

+ +

+ Listen 192.170.2.1:80
+ Listen 192.170.2.5:8000 +

+ +

¤È¤·¤Þ¤¹¡£ + IPv6 ¥¢¥É¥ì¥¹¤Ï¡¢³Ñ³ç¸Ì¤Ç¼¡¤ÎÎã¤Î¤è¤¦¤Ë°Ï¤Þ¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£

+ +

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

+
top
+
+

IPv6 ¤ÎÆõ­»ö¹à

+ + +

¿¤¯¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç IPv6 ¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤­¤Æ¤¤¤Æ¡¢ + APR ¤Ï¤³¤ì¤é¤Î¤Û¤È¤ó¤É¤Ç IPv6 ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤Î¤Ç¡¢ + Apache ¤Ï IPv6 ¥½¥±¥Ã¥È¤ò³ä¤êÅö¤Æ¤Æ IPv6 + ·Ðͳ¤ÇÁ÷¤é¤ì¤Æ¤­¤¿¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

IPv6 ¥½¥±¥Ã¥È¤¬ IPv4 ¤È IPv6 ¥³¥Í¥¯¥·¥ç¥ó¤ÎξÊý¤ò°·¤¦¤³¤È¤¬¤Ç¤­¤ë¤« + ¤É¤¦¤«¤Ï¡¢Apache ´ÉÍý¼Ô¤Ë¤È¤Ã¤ÆÌñ²ð¤ÊÌäÂê¤Ç¤¹¡£ + IPv4 ¥³¥Í¥¯¥·¥ç¥ó¤ò IPv6 ¥½¥±¥Ã¥È¤Ç°·¤¦¾ì¹ç¤Ï¡¢ + IPv4 ¥Þ¥Ã¥×¤µ¤ì¤¿ IPv6 ¥¢¥É¥ì¥¹¤ò»ÈÍѤ·¤Æ¤¤¤Æ¡¢ + ¤Û¤È¤ó¤É¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç»ÈÍѲÄǽ¤Ç¤¹¤¬¡¢ + FreeBSD, NetBSD, OpenBSD ¤Ç¤Ï¡¢¥·¥¹¥Æ¥àÁ´ÂΤȤ·¤Æ¤Î¥Ý¥ê¥·¡¼¤È¤ÎÀ°¹çÀ­¤«¤é¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï»ÈÍÑÉԲĤËÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤³¤ì¤é¤Î¥Ç¥Õ¥©¥ë¥È¤Ç»ÈÍÑÉԲĤΥץé¥Ã¥È¥Û¡¼¥à¤Ç¤¢¤Ã¤Æ¤â¡¢ + ÆÃÊÌ¤Ê configure ¤Î + ÀßÄê¥Ñ¥é¥á¡¼¥¿¤Ç Apache ¤ÎµóÆ°¤òÊѲ½¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

°ìÊý¤Ç¡¢Linux ¤ä Tru64 ¤È¤¤¤Ã¤¿¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç IPv4 ¤È IPv6 + ¤ÎξÊý¤ò°·¤¦¤Ë¤Ï¡¢¥Þ¥Ã¥×¥È¥¢¥É¥ì¥¹¤ò»ÈÍѤ¹¤ë°Ê³°¤ÎÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + IPv4 ¤È IPv6 ¤Î¥³¥Í¥¯¥·¥ç¥ó¤òºÇ¾®¸Â¤Î¥½¥±¥Ã¥È¤Ç°·¤¤¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢ + IPv4 ¥Þ¥Ã¥×¤Î IPv6 ¥¢¥É¥ì¥¹¤ò»ÈÍѤ¹¤ëɬÍפ¬¤¢¤ê¡¢ + --enable-v4-mapped configure + ¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Þ¤¹¡£

+ +

--enable-v4-mapped ¤Ï¡¢ + FreeBSD, NetBSD, OpenBSD °Ê³°¤ÎÁ´¤Æ¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ç¤¹¡£ + ¤Ç¤¹¤«¤é¡¢¤ª¤½¤é¤¯¤ª¼ê¸µ¤Î Apache ¤Ï¤³¤ÎÀßÄê¤Ç¥Ó¥ë¥É¤µ¤ì¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£

+ +

¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤ä APR ¤¬²¿¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤«¤Ë´Ø¤ï¤é¤º¡¢ + IPv4 ¥³¥Í¥¯¥·¥ç¥ó¤Î¤ß¤ò°·¤¦¤è¤¦¤Ë¤·¤¿¤¤¾ì¹ç¤Ï¡¢ + ¼¡¤ÎÎã¤Î¤è¤¦¤ËÁ´¤Æ¤Î + Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + IPv4 ¥¢¥É¥ì¥¹¤ò»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ Listen 0.0.0.0:80
+ Listen 192.170.2.1:80 +

+ +

¾ò·ï¤òËþ¤¿¤¹¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¡¢Apache ¤¬ + IPv4 ¤È IPv6 ¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò¸ÄÊ̤Υ½¥±¥Ã¥È¤Ç°·¤¦¤è¤¦¤Ë¤·¤¿¤¤¾ì¹ç + (¤Ä¤Þ¤ê IPv4 ¥Þ¥Ã¥×¤Î¥¢¥É¥ì¥¹¤ò̵¸ú¤Ë¤·¤¿¤¤¾ì¹ç) + ¤Ï¡¢--disable-v4-mapped + configure + ¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Æ¡¢¼¡¤Î¤è¤¦¤Ë¸ÄÊÌ»ØÄê¤Î + Listen + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£ + --disable-v4-mapped ¤Ï¡¢ + FreeBSD, NetBSD, OpenBSD ¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ç¤¹¡£

+
top
+
+

¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËÂФ·¤Æ¤É¤¦Æ¯¤¯¤Î¤«

+ + +

Listen + ¤Ç¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬¼ÂÁõ¤µ¤ì¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + Listen ¤Ïñ¤Ë¥á¥¤¥ó¥µ¡¼¥Ð¤Ë¤É¤Î¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ò listen ¤¹¤Ù¤­¤«¤ò + ¶µ¤¨¤ë¤À¤±¤Ç¤¹¡£ + <VirtualHost> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬»È¤ï¤ì¤Ê¤¤¾ì¹ç¤Ï¡¢ + ¼õ¤±Æþ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤¹¤Ù¤Æ¤ËÂФ·¤ÆÁ´¤¯Æ±¤¸µóÆ°¤ò¤·¤Þ¤¹¡£ + ¤·¤«¤·¤Ê¤¬¤é + <VirtualHost> + ¤ò»È¤Ã¤Æ¡¢ + °ì¤Ä°Ê¾å¤Î¥¢¥É¥ì¥¹¤ä¥Ý¡¼¥È¤ËÂФ·¤Æ°Û¤Ê¤ëµóÆ°¤ò¤¹¤ë¤è¤¦¤Ë + »ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + VirtualHost ¤ò¼ÂÁõ¤¹¤ë¤Ë¤Ï¡¢»ÈÍѤ¹¤ë¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ò + ¤Þ¤º½é¤á¤Ë¥µ¡¼¥Ð¤ËÄÌÃΤ·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤½¤·¤Æ¡¢¤½¤Î»ØÄꤷ¤¿¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤Ç¤Î + ¤³¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎµóÆ°¤òÀßÄꤹ¤ë¤¿¤á¤Ë¡¢ + <VirtualHost> + ¥»¥¯¥·¥ç¥ó¤òºî¤ê¤Þ¤¹¡£¤â¤· + <VirtualHost> + ¤¬ listen ¤·¤Æ¤¤¤Ê¤¤¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ËÂФ·¤Æ + ÀßÄꤵ¤ì¤Æ¤·¤Þ¤¦¤È¡¢ + ¤½¤ì¤Ë¤Ï¥¢¥¯¥»¥¹¤Ç¤­¤Ê¤¤¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+
+

Available Languages:  de  | + en  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/bind.html.ko.euc-kr b/docs/manual/bind.html.ko.euc-kr new file mode 100644 index 00000000..e0ec2672 --- /dev/null +++ b/docs/manual/bind.html.ko.euc-kr @@ -0,0 +1,151 @@ + + + +ÁÖ¼Ò¿Í Æ÷Æ® ÁöÁ¤ (Binding) - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

ÁÖ¼Ò¿Í Æ÷Æ® ÁöÁ¤ (Binding)

+
+

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

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

¾ÆÆÄÄ¡°¡ ƯÁ¤ ÁÖ¼Ò¿Í Æ÷Æ®¿¡¼­ ¼­ºñ½ºÇϵµ·Ï ¼³Á¤Çϱâ.

+
+ +
top
+
+

°³¿ä

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ + +

¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇÏ¸é ¾ÆÆÄÄ¡´Â ÄÄÇ»ÅÍÀÇ ¾î¶² Æ÷Æ®¿Í ÁÖ¼Ò¿¡ + ¿¬°áÇÏ¿©, µé¾î¿À´Â ¿äûÀ» ±â´Ù¸°´Ù. ±âº»ÀûÀ¸·Î ¾ÆÆÄÄ¡´Â + ÄÄÇ»ÅÍÀÇ ¸ðµç ÁÖ¼Ò¿¡¼­ ±â´Ù¸°´Ù. ±×·¯³ª ¾ÆÆÄÄ¡°¡ ƯÁ¤ Æ÷Æ®³ª + ¼±ÅÃÇÑ ÁÖ¼Ò¸¸À» ±â´Ù¸®°Ô ÇؾßÇÒ °æ¿ì°¡ ÀÖ´Ù. ¶Ç ÀÌ ¹®Á¦´Â + ¾ÆÆÄÄ¡°¡ ¾î¶»°Ô ´Ù¸¥ IP ÁÖ¼Ò, È£½ºÆ®¸í, Æ÷Æ®¿¡ ¹ÝÀÀÇÒÁö¸¦ + °áÁ¤ÇÏ´Â °¡»óÈ£½ºÆ® ±â´É°úµµ °ü·ÃµÇÀÖ´Ù.

+ +

Listen Áö½Ã¾î´Â + ¼­¹ö°¡ ƯÁ¤ Æ÷Æ®³ª ÁÖ¼Ò¿Í Æ÷Æ® Á¶ÇÕ¿¡¼­¸¸ ¿äûÀ» ¹Þ°Ô + ÇÑ´Ù. Listen + Áö½Ã¾î¿¡ Æ÷Æ® ¹øÈ£¸¸ ÁöÁ¤Çϸé, ¼­¹ö´Â ¸ðµç ÀÎÅÍÆäÀ̽º¿¡¼­ + ÁöÁ¤ÇÑ Æ÷Æ®¸¦ ±â´Ù¸°´Ù. ¿©·¯ Listen Áö½Ã¾î·Î ±â´Ù¸± ¿©·¯ + ÁÖ¼Ò¿Í Æ÷Æ®¸¦ ÁöÁ¤ÇÒ ¼öµµ ÀÖ´Ù. ¼­¹ö´Â ¿­°ÅÇÑ ÁÖ¼Ò¿Í Æ÷Æ®·Î + ¿äûÀÌ µé¾î¿À¸é ÀÀ´äÇÑ´Ù.

+ +

¿¹¸¦ µé¾î, ¼­¹ö°¡ 80¹ø°ú 8000¹ø Æ÷Æ® ¸ðµÎ¿¡¼­ ¿¬°áÀ» + ¹Þµµ·Ï ÇÏ·Á¸é:

+ +

+ Listen 80
+ Listen 8000 +

+ +

¼­¹ö°¡ ÁöÁ¤ÇÑ µÎ ÀÎÅÍÆäÀ̽º¿Í Æ÷Æ®¿¡¼­ ¿¬°áÀ» ±â´Ù¸®µµ·Ï + ÇÏ·Á¸é,

+ +

+ Listen 192.170.2.1:80
+ Listen 192.170.2.5:8000 +

+ +

IPv6 ÁÖ¼Ò´Â ´ÙÀ½°ú °°ÀÌ ´ë°ýÈ£·Î ¹­¾î¾ß ÇÑ´Ù:

+ +

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

+
top
+
+

IPv6¿¡¼­ Ưº°È÷ °í·ÁÇÒ Á¡

+ + +

IPv6¸¦ ±¸ÇöÇÑ Ç÷¡ÆûÀÌ ´Ã°í ÀÖ°í APRÀÌ À̵é Ç÷¡Æû ´ëºÎºÐ¿¡¼­ + IPv6¸¦ Áö¿øÇϱ⶧¹®¿¡, ¾ÆÆÄÄ¡´Â IPv6 ¼ÒÄÏÀ» ÇÒ´çÇÏ¿© IPv6·Î + ¹ÞÀº ¿äûÀ» ó¸®ÇÒ ¼ö ÀÖ´Ù.

+ +

¾ÆÆÄÄ¡ °ü¸®ÀÚ¿¡°Ô º¹ÀâÇÑ ºÎºÐÀº IPv6 ¼ÒÄÏÀÌ IPv4 ¿¬°á°ú + IPv6 ¿¬°áÀ» ¸ðµÎ ó¸®ÇÒ ¼ö ÀÖ´À³Ä´Â Á¡ÀÌ´Ù. ´ëºÎºÐÀÇ Ç÷¡Æû¿¡¼­´Â + IPv4-´ëÀÀ(mapped) IPv6 ÁÖ¼Ò¸¦ »ç¿ëÇÏ¿© IPv6 ¼ÒÄÏ¿¡¼­ IPv4 + ¿¬°áÀ» ¹ÞÁö¸¸, FreeBSD¿Í NetBSD¿Í OpenBSDÀº ½Ã½ºÅÛÀüü Á¤Ã¥¶§¹®¿¡ + ±âº»ÀûÀ¸·Î Çã¿ëÇÏÁö ¾Ê´Â´Ù. ±×·¯³ª ±âº»ÀûÀ¸·Î Çã¿ëÇÏÁö¾Ê´Â + ½Ã½ºÅÛÀÌ¶óµµ ¾ÆÆÄÄ¡¸¦ À§ÇØ Æ¯º°ÇÑ ¼³Á¤ ÆĶó¹ÌÅÍ·Î º¯°æÇÒ + ¼ö ÀÖ´Ù.

+ +

¹Ý¸é ¸®´ª½º¿Í Tru64 °°Àº ÀϺΠÇ÷¡Æû¿¡¼­ IPv4¿Í IPv6À» + ¸ðµÎ ó¸®ÇÏ·Á¸é ´ëÀÀ ÁÖ¼Ò¸¦ »ç¿ëÇؾ߸¸ + ÇÑ´Ù. ¾ÆÆÄÄ¡°¡ ÃÖ¼ÒÇÑÀÇ ¼ÒÄÏÀ» »ç¿ëÇÏ¿© IPv4 ¿¬°á°ú IPv6 + ¿¬°áÀ» ¸ðµÎ ¹Þµµ·ÏÇÏ·Á¸é, IPv4-´ëÀÀ IPv6 ÁÖ¼Ò¸¦ »ç¿ëÇÏ°í + configure ¿É¼Ç + --enable-v4-mapped¸¦ ÁöÁ¤ÇÑ´Ù.

+ +

--enable-v4-mapped´Â FreeBSD, NetBSD, OpenBSD¸¦ + Á¦¿ÜÇÑ ¸ðµç Ç÷¡Æû¿¡¼­ ±âº»°ªÀÌ°í, ¾Æ¸¶µµ ´ç½ÅÀÇ ¾ÆÆÄÄ¡µµ + ¸¶Âù°¡ÁöÀÏ °ÍÀÌ´Ù.

+ +

Ç÷¡Æû°ú APRÀÇ Áö¿ø¿©ºÎ¿Í °ü°è¾øÀÌ ¾ÆÆÄÄ¡°¡ IPv4 ¿¬°á¸¸À» + ¹Þµµ·ÏÇÏ·Á¸é, ´ÙÀ½ ¿¹Á¦¿Í °°ÀÌ ¸ðµç Listen Áö½Ã¾î¿¡ IPv4 ÁÖ¼Ò¸¦ + »ç¿ëÇÑ´Ù:

+ +

+ Listen 0.0.0.0:80
+ Listen 192.170.2.1:80 +

+ +

Ç÷¡Æû¿¡¼­ Áö¿øÇÏ¸ç ¾ÆÆÄÄ¡°¡ ¼­·Î ´Ù¸¥ ¼ÒÄÏÀ¸·Î IPv4 + ¿¬°á°ú IPv6 ¿¬°áÀ» ¹Þµµ·ÏÇÏ·Á¸é (Áï IPv4-´ëÀÀ ÁÖ¼Ò¸¦ »ç¿ëÇÏÁö + ¾ÊÀ¸·Á¸é), configure + ¿É¼Ç --disable-v4-mapped¸¦ + ÁöÁ¤ÇÑ´Ù. --disable-v4-mapped´Â FreeBSD, NetBSD, + OpenBSD¿¡¼­ ±âº»°ªÀÌ´Ù.

+ +
top
+
+

°¡»óÈ£½ºÆ®¿Í ¾î¶»°Ô ¿¬°üµÇ³ª

+ + +

ListenÀº + °¡»óÈ£½ºÆ®¸¦ ¸¸µéÁö ¾Ê´Â´Ù. ÀÌ´Â ´ÜÁö ÁÖ¼­¹ö°¡ + ¾î¶² ÁÖ¼Ò¿Í Æ÷Æ®¸¦ ±â´Ù¸±Áö¸¸ ¾Ë·ÁÁØ´Ù. <VirtualHost> Áö½Ã¾î¸¦ + »ç¿ëÇÏÁö ¾ÊÀ¸¸é, ¼­¹ö´Â ¹ÞÀº ¸ðµç ¿äûÀ» ¶È°°ÀÌ Ã³¸®ÇÑ´Ù. + ±×·¯³ª <VirtualHost>·Î ¿©·¯ ÁÖ¼Ò¿Í Æ÷Æ®¿¡ + ´ëÇØ ´Ù¸¥ ÇൿÀ» ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù. °¡»óÈ£½ºÆ®¸¦ ¸¸µé·Á¸é + ¸ÕÀú ¼­¹ö¿¡°Ô »ç¿ëÇÒ ÁÖ¼Ò¿Í Æ÷Æ®¸¦ ¾Ë·ÁÁà¾ß ÇÑ´Ù. ±×¸®°í + ƯÁ¤ ÁÖ¼Ò¿Í Æ÷Æ®¿¡ ´ëÇÑ °¡»óÈ£½ºÆ®ÀÇ ÇൿÀ» ÁöÁ¤ÇÒ + <VirtualHost> + ¼½¼ÇÀÌ ÇÊ¿äÇÏ´Ù. ÁÖ¼­¹ö°¡ ±â´Ù¸®Áö¾Ê´Â ÁÖ¼Ò¿Í Æ÷Æ®¸¦ »ç¿ëÇÏ´Â + <VirtualHost>´Â + Á¢±ÙÇÒ ¼ö ¾øÀ½À» ÁÖÀÇÇ϶ó.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/caching.html b/docs/manual/caching.html new file mode 100644 index 00000000..8506655a --- /dev/null +++ b/docs/manual/caching.html @@ -0,0 +1,3 @@ +URI: caching.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/caching.html.en b/docs/manual/caching.html.en new file mode 100644 index 00000000..1d8259a7 --- /dev/null +++ b/docs/manual/caching.html.en @@ -0,0 +1,655 @@ + + + +Caching Guide - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Caching Guide

+
+

Available Languages:  en 

+
+ +

This document supplements the mod_cache, + mod_disk_cache, mod_mem_cache, + mod_file_cache and htcacheclean reference documentation. + It describes how to use Apache's caching features to accelerate web and + proxy serving, while avoiding common problems and misconfigurations.

+
+ +
top
+
+

Introduction

+ + +

As of Apache HTTP server version 2.2 mod_cache + and mod_file_cache are no longer marked + experimental and are considered suitable for production use. These + caching architectures provide a powerful means to accelerate HTTP + handling, both as an origin webserver and as a proxy.

+ +

mod_cache and its provider modules + mod_mem_cache and mod_disk_cache + provide intelligent, HTTP-aware caching. The content itself is stored + in the cache, and mod_cache aims to honour all of the various HTTP + headers and options that control the cachability of content. It can + handle both local and proxied content. mod_cache + is aimed at both simple and complex caching configurations, where + you are dealing with proxied content, dynamic local content or + have a need to speed up access to local files which change with + time.

+ +

mod_file_cache on the other hand presents a more + basic, but sometimes useful, form of caching. Rather than maintain + the complexity of actively ensuring the cachability of URLs, + mod_file_cache offers file-handle and memory-mapping + tricks to keep a cache of files as they were when Apache was last + started. As such, mod_file_cache is aimed at improving + the access time to local static files which do not change very + often.

+ +

As mod_file_cache presents a relatively simple + caching implementation, apart from the specific sections on CacheFile and MMapStatic, the explanations + in this guide cover the mod_cache caching + architecture.

+ +

To get the most from this document, you should be familiar with + the basics of HTTP, and have read the Users' Guides to + Mapping URLs to the Filesystem and + Content negotiation.

+ +
top
+
+

Caching Overview

+ + + +
Related ModulesRelated Directives
+ +

There are two main stages in mod_cache that can + occur in the lifetime of a request. First, mod_cache + is a URL mapping module, which means that if a URL has been cached, + and the cached version of that URL has not expired, the request will + be served directly by mod_cache.

+ +

This means that any other stages that might ordinarily happen + in the process of serving a request -- for example being handled + by mod_proxy, or mod_rewrite -- + won't happen. But then this is the point of caching content in + the first place.

+ +

If the URL is not found within the cache, mod_cache + will add a filter to the request handling. After + Apache has located the content by the usual means, the filter will be run + as the content is served. If the content is determined to be cacheable, + the content will be saved to the cache for future serving.

+ +

If the URL is found within the cache, but also found to have expired, + the filter is added anyway, but mod_cache will create + a conditional request to the backend, to determine if the cached version + is still current. If the cached version is still current, its + meta-information will be updated and the request will be served from the + cache. If the cached version is no longer current, the cached version + will be deleted and the filter will save the updated content to the cache + as it is served.

+ +

Improving Cache Hits

+ + +

When caching locally generated content, ensuring that + UseCanonicalName is set to + On can dramatically improve the ratio of cache hits. This + is because the hostname of the virtual-host serving the content forms + a part of the cache key. With the setting set to On + virtual-hosts with multiple server names or aliases will not produce + differently cached entities, and instead content will be cached as + per the canonical hostname.

+ +

Because caching is performed within the URL to filename translation + phase, cached documents will only be served in response to URL requests. + Ordinarily this is of little consequence, but there is one circumstance + in which it matters: If you are using Server + Side Includes;

+ + 
+<!-- The following include can be cached -->
+<!--#include virtual="/footer.html" --> 
+
+<!-- The following include can not be cached -->
+<!--#include file="/path/to/footer.html" -->
+ +

If you are using Server Side Includes, and want the benefit of speedy + serves from the cache, you should use virtual include + types.

+ + +

Expiry Periods

+ + +

The default expiry period for cached entities is one hour, however + this can be easily over-ridden by using the CacheDefaultExpire directive. This + default is only used when the original source of the content does not + specify an expire time or time of last modification.

+ +

If a response does not include an Expires header but does + include a Last-Modified header, mod_cache + can infer an expiry period based on the use of the CacheLastModifiedFactor directive.

+ +

For local content, mod_expires may be used to + fine-tune the expiry period.

+ +

The maximum expiry period may also be controlled by using the + CacheMaxExpire.

+ + + +

A Brief Guide to Conditional Requests

+ + +

When content expires from the cache and is re-requested from the + backend or content provider, rather than pass on the original request, + Aoache will use a conditional request instead.

+ +

HTTP offers a number of headers which allow a client, or cache + to discern between different versions of the same content. For + example if a resource was served with an "Etag:" header, it is + possible to make a conditional request with an "If-Match:" + header. If a resource was served with a "Last-Modified:" header + it is possible to make a conditional request with an + "If-Modified-Since:" header, and so on.

+ +

When such a conditional request is made, the response differs + depending on whether the content matches the conditions. If a request is + made with an "If-Modified-Since:" header, and the content has not been + modified since the time indicated in the request then a terse "304 Not + Modified" response is issued.

+ +

If the content has changed, then it is served as if the request were + not conditional to begin with.

+ +

The benefits of conditional requests in relation to caching are + twofold. Firstly, when making such a request to the backend, if the + content from the backend matches the content in the store, this can be + determined easily and without the overhead of transferring the entire + resource.

+ +

Secondly, conditional requests are usually less strenuous on the + backend. For static files, typically all that is involved is a call + to stat() or similar system call, to see if the file has + changed in size or modification time. As such, even if Apache is + caching local content, even expired content may still be served faster + from the cache if it has not changed. As long as reading from the cache + store is faster than reading from the backend (e.g. an in-memory cache + compared to reading from disk).

+ + +

What Can be Cached?

+ + +

As mentioned already, the two styles of caching in Apache work + differently, mod_file_cache caching maintains file + contents as they were when Apache was started. When a request is + made for a file that is cached by this module, it is intercepted + and the cached file is served.

+ +

mod_cache caching on the other hand is more + complex. When serving a request, if it has not been cached + previously, the caching module will determine if the content + is cacheable. The conditions for determining cachability of + a response are;

+ +
    +
  1. Caching must be enabled for this URL. See the CacheEnable and CacheDisable directives.
    2. + +
  2. The response must have a HTTP status code of 200, 203, 300, 301 or + 410.
    3. + +
  3. The request must be a HTTP GET request.
    4. + +
  4. If the request contains an "Authorization:" header, the response + will not be cached.
    5. + +
  5. If the response contains an "Authorization:" header, it must + also contain an "s-maxage", "must-revalidate" or "public" option + in the "Cache-Control:" header.
    6. + +
  6. If the URL included a query string (e.g. from a HTML form GET + method) it will not be cached unless the response includes an + "Expires:" header, as per RFC2616 section 13.9.
    7. + +
  7. If the response has a status of 200 (OK), the response must + also include at least one of the "Etag", "Last-Modified" or + the "Expires" headers, unless the + CacheIgnoreNoLastMod + directive has been used to require otherwise.
    8. + +
  8. If the response includes the "private" option in a "Cache-Control:" + header, it will not be stored unless the + CacheStorePrivate has been + used to require otherwise.
    9. + +
  9. Likewise, if the response includes the "no-store" option in a + "Cache-Control:" header, it will not be stored unless the + CacheStoreNoStore has been + used.
    10. + +
  10. A response will not be stored if it includes a "Vary:" header + containing the match-all "*".
    11. +
+ + +

What Should Not be Cached?

+ + +

In short, any content which is highly time-sensitive, or which varies + depending on the particulars of the request that are not covered by + HTTP negotiation, should not be cached.

+ +

If you have dynamic content which changes depending on the IP address + of the requester, or changes every 5 minutes, it should almost certainly + not be cached.

+ +

If on the other hand, the content served differs depending on the + values of various HTTP headers, it is possible that it might be possible + to cache it intelligently through the use of a "Vary" header.

+ + +

Variable/Negotiated Content

+ + +

If a response with a "Vary" header is received by + mod_cache when requesting content by the backend it + will attempt to handle it intelligently. If possible, + mod_cache will detect the headers attributed in the + "Vary" response in future requests and serve the correct cached + response.

+ +

If for example, a response is received with a vary header such as;

+ +

+Vary: negotiate,accept-language,accept-charset +

+ +

mod_cache will only serve the cached content to + requesters with matching accept-language and accept-charset headers + matching those of the original request.

+ + +
top
+
+

Security Considerations

+ + +

Authorisation, Access & and Control

+ + +

Using mod_cache is very much like having a built + in reverse-proxy. Requests will be served by the caching module unless + it determines that the backend should be queried. When caching local + resources, this drastically changes the security model of Apache.

+ +

As traversing a filesystem hierarchy to examine potential + .htaccess files would be a very expensive operation, + partially defeating the point of caching (to speed up requests), + mod_cache makes no decision about whether a cached + entity is authorised for serving. In other words; if + mod_cache has cached some content, it will be served + from the cache as long as that content has not expired.

+ +

If, for example, your configuration permits access to a resource by IP + address you should ensure that this content is not cached. You can do this by + using the CacheDisable + directive, or mod_expires. Left unchecked, + mod_cache - very much like a reverse proxy - would cache + the content when served and then serve it to any client, on any IP + address.

+ + +

Local exploits

+ + +

As requests to end-users can be served from the cache, the cache + itself can become a target for those wishing to deface or interfere with + content. It is important to bear in mind that the cache must at all + times be writable by the user which Apache is running as. This is in + stark contrast to the usually recommended situation of maintaining + all content unwritable by the Apache user.

+ +

If the Apache user is compromised, for example through a flaw in + a CGI process, it is possible that the cache may be targeted. When + using mod_disk_cache, it is relatively easy to + insert or modify a cached entity.

+ +

This presents a somewhat elevated risk in comparison to the other + types of attack it is possible to make as the Apache user. If you are + using mod_disk_cache you should bear this in mind - + ensure you upgrade Apache when security upgrades are announced and + run CGI processes as a non-Apache user using suEXEC if possible.

+ + + +

Cache Poisoning

+ + +

When running Apache as a caching proxy server, there is also the + potential for so-called cache poisoning. Cache Poisoning is a broad + term for attacks in which an attacker causes the proxy server to + retrieve incorrect (and usually undesirable) content from the backend. +

+ +

For example if the DNS servers used by your system running Apache + are vulnerable to DNS cache poisoning, an attacker may be able to control + where Apache connects to when requesting content from the origin server. + Another example is so-called HTTP request-smuggling attacks.

+ +

This document is not the correct place for an in-depth discussion + of HTTP request smuggling (instead, try your favourite search engine) + however it is important to be aware that it is possible to make + a series of requests, and to exploit a vulnerability on an origin + webserver such that the attacker can entirely control the content + retrieved by the proxy.

+ +
top
+
+

File-Handle Caching

+ + +
Related ModulesRelated Directives
+ +

The act of opening a file can itself be a source of delay, particularly + on network filesystems. By maintaining a cache of open file descriptors + for commonly served files, Apache can avoid this delay. Currently Apache + provides two different implementations of File-Handle Caching.

+ +

CacheFile

+ + +

The most basic form of caching present in Apache is the file-handle + caching provided by mod_file_cache. Rather than caching + file-contents, this cache maintains a table of open file descriptors. Files + to be cached in this manner are specified in the configuration file using + the CacheFile + directive.

+ +

The + CacheFile directive + instructs Apache to open the file when Apache is started and to re-use + this file-handle for all subsequent access to this file.

+ + 
CacheFile /usr/local/apache2/htdocs/index.html
+ +

If you intend to cache a large number of files in this manner, you + must ensure that your operating system's limit for the number of open + files is set appropriately.

+ +

Although using CacheFile + does not cause the file-contents to be cached per-se, it does mean + that if the file changes while Apache is running these changes will + not be picked up. The file will be consistently served as it was + when Apache was started.

+ +

If the file is removed while Apache is running, Apache will continue + to maintain an open file descriptor and serve the file as it was when + Apache was started. This usually also means that although the file + will have been deleted, and not show up on the filesystem, extra free + space will not be recovered until Apache is stopped and the file + descriptor closed.

+ + +

CacheEnable fd

+ + +

mod_mem_cache also provides its own file-handle + caching scheme, which can be enabled via the + CacheEnable directive.

+ + 
CacheEnable fd /
+ +

As with all of mod_cache this type of file-handle + caching is intelligent, and handles will not be maintained beyond + the expiry time of the cached content.

+ +
top
+
+

In-Memory Caching

+ + +
Related ModulesRelated Directives
+ +

Serving directly from system memory is universally the fastest method + of serving content. Reading files from a disk controller or, even worse, + from a remote network is orders of magnitude slower. Disk controllers + usually involve physical processes, and network access is limited by + your available bandwidth. Memory access on the other hand can take mere + nano-seconds.

+ +

System memory isn't cheap though, byte for byte it's by far the most + expensive type of storage and it's important to ensure that it is used + efficiently. By caching files in memory you decrease the amount of + memory available on the system. As we'll see, in the case of operating + system caching, this is not so much of an issue, but when using + Apache's own in-memory caching it is important to make sure that you + do not allocate too much memory to a cache. Otherwise the system + will be forced to swap out memory, which will likely degrade + performance.

+ +

Operating System Caching

+ + +

Almost all modern operating systems cache file-data in memory managed + directly by the kernel. This is a powerful feature, and for the most + part operating systems get it right. For example, on Linux, let's look at + the difference in the time it takes to read a file for the first time + and the second time;

+ + 
+colm@coroebus:~$ time cat testfile > /dev/null
+real    0m0.065s
+user    0m0.000s
+sys     0m0.001s
+colm@coroebus:~$ time cat testfile > /dev/null
+real    0m0.003s
+user    0m0.003s
+sys     0m0.000s
+ +

Even for this small file, there is a huge difference in the amount + of time it takes to read the file. This is because the kernel has cached + the file contents in memory.

+ +

By ensuring there is "spare" memory on your system, you can ensure + that more and more file-contents will be stored in this cache. This + can be a very efficient means of in-memory caching, and involves no + extra configuration of Apache at all.

+ +

Additionally, because the operating system knows when files are + deleted or modified, it can automatically remove file contents from the + cache when neccessary. This is a big advantage over Apache's in-memory + caching which has no way of knowing when a file has changed.

+ + +

Despite the performance and advantages of automatic operating system + caching there are some circumstances in which in-memory caching may be + better performed by Apache.

+ +

Firstly, an operating system can only cache files it knows about. If + you are running Apache as a proxy server, the files you are caching are + not locally stored but remotely served. If you still want the unbeatable + speed of in-memory caching, Apache's own memory caching is needed.

+ +

MMapStatic Caching

+ + +

mod_file_cache provides the + MMapStatic directive, which + allows you to have Apache map a static file's contents into memory at + start time (using the mmap system call). Apache will use the in-memory + contents for all subsequent accesses to this file.

+ + 
MMapStatic /usr/local/apache2/htdocs/index.html
+ +

As with the + CacheFile directive, any + changes in these files will not be picked up by Apache after it has + started.

+ +

The MMapStatic + directive does not keep track of how much memory it allocates, so + you must ensure not to over-use the directive. Each Apache child + process will replicate this memory, so it is critically important + to ensure that the files mapped are not so large as to cause the + system to swap memory.

+ + +

mod_mem_cache Caching

+ + +

mod_mem_cache provides a HTTP-aware intelligent + in-memory cache. It also uses heap memory directly, which means that + even if MMap is not supported on your system, + mod_mem_cache may still be able to perform caching.

+ +

Caching of this type is enabled via;

+ + 
+# Enable memory caching
+CacheEnable mem /
+
+# Limit the size of the cache to 1 Megabyte
+MCacheSize 1024
+ +
top
+
+

Disk-based Caching

+ + +
Related ModulesRelated Directives
+ +

mod_disk_cache provides a disk-based caching mechanism + for mod_cache. As with mod_mem_cache + this cache is intelligent and content will be served from the cache only + as long as it is considered valid.

+ +

Typically the module will be configured as so;

+ + 
+CacheRoot   /var/cache/apache/
+CacheEnable disk /
+CacheDirLevels 2
+CacheDirLength 1
+ +

Importantly, as the cached files are locally stored, operating system + in-memory caching will typically be applied to their access also. So + although the files are stored on disk, if they are frequently accessed + it is likely the operating system will ensure that they are actually + served from memory.

+ +

Understanding the Cache-Store

+ + +

To store items in the cache, mod_disk_cache creates + a 22 character hash of the url being requested. Thie hash incorporates + the hostname, protocol, port, path and any CGI arguments to the URL, + to ensure that multiple URLs do not collide.

+ +

Each character may be any one of 64-different characters, which mean + that overall there are 22^64 possible hashes. For example, a URL might + be hashed to xyTGxSMO2b68mBCykqkp1w. This hash is used + as a prefix for the naming of the files specific to that url within + the cache, however first it is split up into directories as per + the CacheDirLevels and + CacheDirLength + directives.

+ +

CacheDirLevels + specifies how many levels of subdirectory there should be, and + CacheDirLength + specifies how many characters should be in each directory. With + the example settings given above, the hash would be turned into + a filename prefix as + /var/cache/apache/x/y/TGxSMO2b68mBCykqkp1w.

+ +

The overall aim of this technique is to reduce the number of + subdirectories or files that may be in a particular directory, + as most file-systems slow down as this number increases. With + setting of "1" for + CacheDirLength + there can at most be 64 subdirectories at any particular level. + With a setting of 2 there can be 64 * 64 subdirectories, and so on. + Unless you have a good reason not to, using a setting of "1" + for CacheDirLength + is recommended.

+ +

Setting + CacheDirLevels + depends on how many files you anticipate to store in the cache. + With the setting of "2" used in the above example, a grand + total of 4096 subdirectories can ultimately be created. With + 1 million files cached, this works out at roughly 245 cached + urls per directory.

+ +

Each url uses at least two files in the cache-store. Typically + there is a ".header" file, which includes meta-information about + the url, such as when it is due to expire and a ".data" file + which is a verbatim copy of the content to be served.

+ +

In the case of a content negotiated via the "Vary" header, a + ".vary" directory will be created for the url in question. This + directory will have multiple ".data" files corresponding to the + differently negotiated content.

+ + +

Maintaining the Disk Cache

+ + +

Although mod_disk_cache will remove cached content + as it is expired, it does not maintain any information on the total + size of the cache or how little free space may be left.

+ +

Instead, provided with Apache is the htcacheclean tool which, as the name + suggests, allows you to clean the cache periodically. Determining + how frequently to run htcacheclean and what target size to + use for the cache is somewhat complex and trial and error may be needed to + select optimal values.

+ +

htcacheclean has two modes of + operation. It can be run as persistent daemon, or periodically from + cron. htcacheclean can take up to an hour + or more to process very large (tens of gigabytes) caches and if you are + running it from cron it is recommended that you determine how long a typical + run takes, to avoid running more than one instance at a time.

+ +

+
+ Figure 1: Typical + cache growth / clean sequence.

+ +

Because mod_disk_cache does not itself pay attention + to how much space is used you should ensure that + htcacheclean is configured to + leave enough "grow room" following a clean.

+ + +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/configuring.html b/docs/manual/configuring.html new file mode 100644 index 00000000..3ec3186d --- /dev/null +++ b/docs/manual/configuring.html @@ -0,0 +1,15 @@ +URI: configuring.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: configuring.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: configuring.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: configuring.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/configuring.html.de b/docs/manual/configuring.html.de new file mode 100644 index 00000000..a8707672 --- /dev/null +++ b/docs/manual/configuring.html.de @@ -0,0 +1,183 @@ + + + +Konfigurationsdateien - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Konfigurationsdateien

+
+

Verfügbare Sprachen:  de  | + en  | + ja  | + ko 

+
+ +

Dieses Dokument beschreibt die Dateien, die zur Konfiguration des Apache + HTTP Servers verwendet werden.

+
+ +
top
+
+

Hauptkonfigurationsdateien

+ +
Referenzierte ModuleReferenzierte Direktiven
+ +

Der Apache wird konfiguriert, indem Direktiven in einfache Textdateien + eingetragen werden. Die Hauptkonfigurationsdatei heißt + üblicherweise httpd.conf. Der Ablageort dieser Datei + wird bei der Kompilierung festgelegt, kann jedoch mit der + Befehlszeilenoption -f überschrieben werden. Durch + Verwendung der Direktive Include + können außerdem weitere Konfigurationsdateien hinzugefügt + werden. Zum Einfügen von mehreren Konfigurationsdateien können + Platzhalter verwendet werden. Jede Direktive darf in jeder dieser + Konfigurationsdateien angegeben werden. Änderungen in den + Hauptkonfigurationsdateien werden vom Apache nur beim Start oder Neustart + erkannt.

+ +

Der Server liest auch eine Datei mit MIME-Dokumenttypen ein. Der + Name dieser Datei wird durch die Direktive TypesConfig bestimmt. Die Voreinstellung + ist mime.types.

+
top
+
+

Syntax der Konfigurationsdateien

+ + +

Die Konfigurationsdateien des Apache enthalten eine Direktive pro Zeile. + Der Backslash "\" läßt sich als letztes Zeichen in einer Zeile + dazu verwenden, die Fortsetzung der Direktive in der nächsten Zeile + anzuzeigen. Es darf kein weiteres Zeichen oder Whitespace zwischen dem + Backslash und dem Zeilenende folgen.

+ +

In den Konfigurationsdateien wird bei den Direktiven nicht zwischen + Groß- und Kleinschreibung unterschieden. Bei den Argumenten der + Direktiven wird dagegen oftmals zwischen Groß- und Kleinschreibung + differenziert. Zeilen, die mit dem Doppelkreuz "#" beginnen, werden als + Kommentare betrachtet und ignoriert. Kommentare dürfen + nicht am Ende einer Zeile nach der Direktive + eingefügt werden. Leerzeilen und Whitespaces vor einer Direktive + werden ignoriert. Dadurch lassen sich Direktiven zur besseren Lesbarbeit + einrücken.

+ +

Sie können die Syntax Ihrer Konfigurationsdateien auf Fehler + prüfen, ohne den Server zu starten, indem Sie apachectl + configtest oder die Befehlszeilenoption -t + verwenden.

+
top
+
+

Module

+ + +
Referenzierte ModuleReferenzierte Direktiven
+ +

Der Apache ist ein modularer Server. Das bedeutet, dass nur die abolute + Grundfunktionalität im Kernserver enthalten ist. Weitergehende + Fähigkeiten sind mittels Modulen verfügbar, + die in den Apache geladen werden können. Standardmäßig + wird bei der Kompilierung ein Satz von Basismodulen (Anm.d.Ü.: die so + genannten Base-Module) in den Server eingebunden. Wenn der + Server für die Verwendung von dynamisch + ladbaren Modulen kompiliert wurde, dann können Module separat + kompiliert und jederzeit mittels der Direktive LoadModule hinzugefügt werden. + Andernfalls muss der Apache neu kompiliert werden, um Module + hinzuzufügen oder zu entfernen. Konfigurationsanweisungen können + abhängig vom Vorhandensein eines bestimmten Moduls eingesetzt werden, + indem sie in einen <IfModule>-Block eingeschlossen werden.

+ +

Um zu sehen, welche Module momentan in den Server einkompiliert sind, + kann die Befehlszeilenoption -l verwendet werden.

+
top
+
+

Der Gültigkeitsbereich von Direktiven

+ + +
Referenzierte ModuleReferenzierte Direktiven
+ +

Direktiven in den Hauptkonfigurationsdateien gelten für den + gesamten Server. Wenn Sie die Konfiguration nur für einen Teil des + Servers verändern möchten, können Sie den + Gültigkeitsbereich der Direktiven beschränken, indem Sie diese + in <Directory>-, + <DirectoryMatch>-, + <Files>-, + <FilesMatch>-, + <Location>- oder + <LocationMatch>-Abschnitte eingefügen. + Diese Abschnitte begrenzen die Anwendung der umschlossenen Direktiven + auf bestimmte Pfade des Dateisystems oder auf + bestimmte URLs. Sie können für eine fein abgestimmte + Konfiguration auch ineinander verschachtelt werden.

+ + +

Der Apache besitzt die Fähigkeit, mehrere verschiedene Websites + gleichzeitig zu bedienen. Dies wird virtuelles + Hosten genannt. Direktiven können auch in ihrem + Gültigkeitsgereich eingeschränkt werden, indem sie innerhalb + eines <VirtualHost>-Abschnittes angegeben werden. + Sie werden dann nur auf Anfragen für eine bestimmte Website + angewendet.

+ +

Obwohl die meisten Direktiven in jedem dieser Abschnitte platziert + werden können, ergeben einige Direktiven in manchen Kontexten + keinen Sinn. Direktiven zur Prozesssteuerung beispielsweise + dürfen nur im Kontext des Hauptservers angegeben werden. Prüfen + Sie den Kontext der + Direktive, um herauszufinden, welche Direktiven in welche Abschnitte + eingefügt werden können. Weitere Informationen finden Sie unter + "Wie Directory-, Location- und Files-Abschnitte + arbeiten".

+ +
top
+
+

.htaccess-Dateien

+ + +
Referenzierte ModuleReferenzierte Direktiven
+ +

Der Apache ermöglicht die dezentrale Verwaltung der + Konfiguration mittes spezieller Dateien innerhalb des + Web-Verzeichnisbaums. Diese speziellen Dateien heißen + gewöhnlich .htaccess, mit der Direktive AccessFileName kann jedoch auch ein anderer + Name festgelegt werden. In .htaccess-Dateien angegebene + Direktiven werden auf das Verzeichnis und dessen Unterverzeichnisse + angewendet, in dem die Datei abgelegt ist. .htaccess-Dateien + folgen der gleichen Syntax wie die Hauptkonfigurationsdateien. Da + .htaccess-Dateien bei jeder Anfrage eingelesen werden, + werden Änderungen in diesen Dateien sofort wirksam.

+ +

Prüfen Sie den Kontext der Direktive, um + herauszufinden, welche Direktiven in .htaccess-Dateien + angegeben werden können. Darüber hinaus steuert der + Serveradministrator mit der Einstellung der Direktive AllowOverride in den + Hauptkonfigurationsdateien welche Direktiven in + .htaccess-Dateien verwendet werden dürfen.

+ +

Weitere Informationen über .htaccess-Dateien finden + Sie in der .htaccess-Einführung.

+
+
+

Verfügbare Sprachen:  de  | + en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/configuring.html.en b/docs/manual/configuring.html.en new file mode 100644 index 00000000..72104aed --- /dev/null +++ b/docs/manual/configuring.html.en @@ -0,0 +1,167 @@ + + + +Configuration Files - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Configuration Files

+
+

Available Languages:  de  | + en  | + ja  | + ko 

+
+ +

This document describes the files used to configure the Apache +HTTP server.

+
+ +
top
+
+

Main Configuration Files

+ +
Related ModulesRelated Directives
+ +

Apache is configured by placing directives in plain text + configuration files. The main configuration file is usually called + httpd.conf. The location of this file is set at + compile-time, but may be overridden with the -f + command line flag. In addition, other configuration files may be + added using the Include + directive, and wildcards can be used to include many configuration + files. Any directive may be placed in any of these configuration + files. Changes to the main configuration files are only + recognized by Apache when it is started or restarted.

+ +

The server also reads a file containing mime document types; + the filename is set by the TypesConfig directive, + and is mime.types by default.

+
top
+
+

Syntax of the Configuration Files

+ + +

Apache configuration files contain one directive per line. + The back-slash "\" may be used as the last character on a line + to indicate that the directive continues onto the next line. + There must be no other characters or white space between the + back-slash and the end of the line.

+ +

Directives in the configuration files are case-insensitive, + but arguments to directives are often case sensitive. Lines + that begin with the hash character "#" are considered + comments, and are ignored. Comments may not be + included on a line after a configuration directive. Blank lines + and white space occurring before a directive are ignored, so + you may indent directives for clarity.

+ +

You can check your configuration files for syntax errors + without starting the server by using apachectl + configtest or the -t command line + option.

+
top
+
+

Modules

+ + +
Related ModulesRelated Directives
+ +

Apache is a modular server. This implies that only the most + basic functionality is included in the core server. Extended + features are available through modules which can be loaded + into Apache. By default, a base set of modules is + included in the server at compile-time. If the server is + compiled to use dynamically loaded + modules, then modules can be compiled separately and added at + any time using the LoadModule + directive. + Otherwise, Apache must be recompiled to add or remove modules. + Configuration directives may be included conditional on a + presence of a particular module by enclosing them in an <IfModule> block.

+ +

To see which modules are currently compiled into the server, + you can use the -l command line option.

+
top
+
+

Scope of Directives

+ + +
Related ModulesRelated Directives
+ +

Directives placed in the main configuration files apply to + the entire server. If you wish to change the configuration for + only a part of the server, you can scope your directives by + placing them in <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, and <LocationMatch> + sections. These sections limit the application of the + directives which they enclose to particular filesystem + locations or URLs. They can also be nested, allowing for very + fine grained configuration.

+ +

Apache has the capability to serve many different websites + simultaneously. This is called Virtual + Hosting. Directives can also be scoped by placing them + inside <VirtualHost> + sections, so that they will only apply to requests for a + particular website.

+ +

Although most directives can be placed in any of these + sections, some directives do not make sense in some contexts. + For example, directives controlling process creation can only + be placed in the main server context. To find which directives + can be placed in which sections, check the Context of the + directive. For further information, we provide details on How Directory, Location and Files sections + work.

+
top
+
+

.htaccess Files

+ + +
Related ModulesRelated Directives
+ +

Apache allows for decentralized management of configuration + via special files placed inside the web tree. The special files + are usually called .htaccess, but any name can be + specified in the AccessFileName + directive. Directives placed in .htaccess files + apply to the directory where you place the file, and all + sub-directories. The .htaccess files follow the + same syntax as the main configuration files. Since + .htaccess files are read on every request, changes + made in these files take immediate effect.

+ +

To find which directives can be placed in + .htaccess files, check the Context of the + directive. The server administrator further controls what + directives may be placed in .htaccess files by + configuring the AllowOverride + directive in the main configuration files.

+ +

For more information on .htaccess files, see + the .htaccess tutorial.

+
+
+

Available Languages:  de  | + en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/configuring.html.ja.euc-jp b/docs/manual/configuring.html.ja.euc-jp new file mode 100644 index 00000000..d01e3bdd --- /dev/null +++ b/docs/manual/configuring.html.ja.euc-jp @@ -0,0 +1,171 @@ + + + +ÀßÄê¥Õ¥¡¥¤¥ë - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

ÀßÄê¥Õ¥¡¥¤¥ë

+
+

Available Languages:  de  | + en  | + ja  | + ko 

+
+ +

¤³¤Îʸ½ñ¤Ç¤Ï¡¢Apache HTTP ¥µ¡¼¥Ð¤òÀßÄꤹ¤ë¤Î¤Ë»ÈÍѤ¹¤ë¥Õ¥¡¥¤¥ë¤Ë¤Ä¤¤¤Æ +µ­½Ò¤·¤Æ¤¤¤Þ¤¹¡£

+
+ +
top
+
+

¥á¥¤¥ó¤ÎÀßÄê¥Õ¥¡¥¤¥ë

+ +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

Apache ¤Ï ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö ¤òÀßÄê¥Õ¥¡¥¤¥ë¤Ëʿʸ¤Ç½ñ¤¯¤³¤È¤Ë¤è¤êÀßÄꤷ¤Þ¤¹¡£ + ¥á¥¤¥ó¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ÏÉáÄÌ¤Ï httpd.conf ¤È¤¤¤¦Ì¾Á°¤Ç¤¹¡£ + ¤³¤Î¥Õ¥¡¥¤¥ë¤Î°ÌÃ֤ϥ³¥ó¥Ñ¥¤¥ë»þ¤ËÀßÄꤵ¤ì¤Þ¤¹¤¬¡¢¥³¥Þ¥ó¥É¥é¥¤¥ó¤Î + -f ¥Õ¥é¥°¤Ë¤è¤ê¾å½ñ¤­¤Ç¤­¤Þ¤¹¡£ + ¤Þ¤¿¡¢Â¾¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò Include + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤ÆÄɲäǤ­¡¢¥ï¥¤¥ë¥É¥«¡¼¥É¤ò»ÈÍѤ·¤Æ¿¿ô¤Î + ÀßÄê¥Õ¥¡¥¤¥ë¤òÄɲ乤뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤É¤ó¤Ê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤â¡¢¤³¤ì¤é¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤É¤ì¤Ë¤Ç¤âÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + Apache ¤Ïµ¯Æ°»þ¤«ºÆµ¯Æ°»þ¤Î¤ß¥á¥¤¥óÀßÄê¥Õ¥¡¥¤¥ë¤ÎÊѹ¹¤òǧ¼±¤·¤Þ¤¹¡£

+ +

¥µ¡¼¥Ð¤Ï MIME + ¥É¥­¥å¥á¥ó¥È¥¿¥¤¥×¤ò´Þ¤ó¤Ç¤¤¤ë¥Õ¥¡¥¤¥ë¤âÆɤ߹þ¤ß¤Þ¤¹¡£¥Õ¥¡¥¤¥ë̾¤Ï + TypesConfig + ¤ÇÀßÄꤵ¤ì¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï mime.types + ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+
top
+
+

ÀßÄê¥Õ¥¡¥¤¥ë¤Î¹½Ê¸

+ + +

Apache ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ï 1 ¹Ô¤Ë 1 ¤Ä¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤«¤é¤Ê¤ê¤Þ¤¹¡£ + ¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å "\" ¤Ï¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¼¡¤Î¹Ô¤Ë·Ñ³¤·¤Æ¤¤¤ë¤³¤È¤ò + ¼¨¤¹¤¿¤á¤Ë¹Ô¤ÎºÇ¸å¤Îʸ»ú¤È¤·¤Æ»È¤ï¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¹Ô¤ÎºÇ¸å¤È¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Î´Ö¤Ë¾¤Îʸ»ú¤ä¶õÇò¤¬¤¢¤Ã¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ +

+ +

ÀßÄê¥Õ¥¡¥¤¥ë¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¤¬¡¢ + °ú¿ô¤Ë¤Ï¤·¤Ð¤·¤Ð¶èÊ̤¹¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£¥Ï¥Ã¥·¥åʸ»ú "#" + ¤Ç»Ï¤Þ¤ë¹Ô¤Ï¥³¥á¥ó¥È¤È¸«¤Ê¤µ¤ì¤Æ̵»ë¤µ¤ì¤Þ¤¹¡£ + ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¸å¤Î¹Ô¤Ç¤Ï¥³¥á¥ó¥È¤¬´Þ¤Þ¤ì¤Æ¤¤¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÁ°¤Î¶õ¹Ô¤È¶õÇò¤Ï̵»ë¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢ + ¤ï¤«¤ê¤ä¤¹¤¯¤¹¤ë¤¿¤á¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¥¤¥ó¥Ç¥ó¥È¤·¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£ +

+ +

ÀßÄê¥Õ¥¡¥¤¥ë¤Î¹½Ê¸¥¨¥é¡¼¤Ï¡¢ + apachectl configtest + ¤«¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó + -t ¤ò»È¤Ã¤ÆÄ´¤Ù¤é¤ì¤Þ¤¹¡£

+
top
+
+

¥â¥¸¥å¡¼¥ë

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

Apache ¤Ï¥â¥¸¥å¡¼¥ë²½¤µ¤ì¤¿¥µ¡¼¥Ð¤Ç¤¹¡£ + ¥³¥¢¥µ¡¼¥Ð¤Ë¤ÏºÇ¤â´ðËÜŪ¤Êµ¡Ç½¤À¤±¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£³ÈÄ¥µ¡Ç½¤Ï + Apache ¤Ë¥í¡¼¥É¤µ¤ì¤ë¥â¥¸¥å¡¼¥ë¤È¤·¤ÆÍøÍѲÄǽ¤Ç¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥³¥ó¥Ñ¥¤¥ë»þ¤Ë¥â¥¸¥å¡¼¥ë¤Î + Base ¥»¥Ã¥È (´ðËÜ¥»¥Ã¥È) ¤¬ + ¥µ¡¼¥Ð¤Ë´Þ¤Þ¤ì¤Þ¤¹¡£¥µ¡¼¥Ð¤¬Æ°Åª¥í¡¼¥É¥â¥¸¥å¡¼¥ë¤ò»È¤¦¤è¤¦¤Ë¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥â¥¸¥å¡¼¥ë¤òÊ̤˥³¥ó¥Ñ¥¤¥ë¤·¤Æ¡¢¤¤¤Ä¤Ç¤â + LoadModule + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤ÆÄɲäǤ­¤Þ¤¹¡£ + ¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢¥â¥¸¥å¡¼¥ë¤ÎÄɲääºï½ü¤ò¤¹¤ë¤¿¤á¤Ë¤Ï Apache + ¤òºÆ¥³¥ó¥Ñ¥¤¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï <IfModule> + ¥Ö¥í¥Ã¥¯¤ËÆþ¤ì¤ë¤³¤È¤ÇÆÃÄê¤Î¥â¥¸¥å¡¼¥ë¤¬Â¸ºß¤¹¤ë¤È¤­¤À¤± + ÀßÄê¥Õ¥¡¥¤¥ë¤Ë´Þ¤Þ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó -l ¤ò»È¤Ã¤Æ¸½»þÅÀ¤Ç + ¤É¤Î¥â¥¸¥å¡¼¥ë¤¬¥µ¡¼¥Ð¤Ë¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤ë¤«¤òÃΤ뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
top
+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎŬÍÑÈÏ°Ï

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

¥á¥¤¥óÀßÄê¥Õ¥¡¥¤¥ë¤Ë¤¢¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥µ¡¼¥ÐÁ´ÂΤËŬÍѤµ¤ì¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤Î°ìÉôʬ¤ÎÀßÄê¤À¤±¤òÊѹ¹¤·¤¿¤¤¾ì¹ç¤Ï <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, <LocationMatch> + ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤ËÃÖ¤¯¤³¤È¤ÇŬÍÑÈϰϤò·è¤á¤é¤ì¤Þ¤¹¡£ + ¤³¤ì¤é¤Î¥»¥¯¥·¥ç¥ó¤Ï¤½¤ÎÃæ¤Ë¤¢¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎŬÍÑÈϰϤò + ÆÃÄê¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃÖ¤ä URL ¤Ë¸ÂÄꤷ¤Þ¤¹¡£ + Èó¾ï¤ËºÙγÅÙ¤ÎÀßÄê¤ò²Äǽ¤Ë¤¹¤ë¤¿¤á¤Ë¡¢ + ¥»¥¯¥·¥ç¥ó¤òÆþ¤ì»Ò¤Ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

Apache ¤ÏƱ»þ¤Ë¿¤¯¤Î°ã¤¦¥¦¥§¥Ö¥µ¥¤¥È¤ò°·¤¦Ç½ÎϤ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È ¤È¸Æ¤Ð¤ì¤Æ¤¤¤Þ¤¹¡£ + ÆÃÄê¤Î¥¦¥§¥Ö¥µ¥¤¥È¤Ë¤Î¤ßŬÍѤµ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + <VirtualHost> + ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤ËÃÖ¤¯¤³¤È¤Ç¤âŬÍÑÈϰϤòÊѤ¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤Û¤È¤ó¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤É¤Î¥»¥¯¥·¥ç¥ó¤Ë¤Ç¤â½ñ¤±¤Þ¤¹¤¬¡¢ + Ãæ¤Ë¤Ï¥³¥ó¥Æ¥­¥¹¥È¤Ë¤è¤Ã¤Æ¤Ï°ÕÌ£¤ò¤Ê¤µ¤Ê¤¤¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£ + Î㤨¤Ð¡¢¥×¥í¥»¥¹¤ÎºîÀ®¤òÀ©¸æ¤·¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥á¥¤¥ó¥µ¡¼¥Ð¤Î + ¥³¥ó¥Æ¥­¥¹¥È¤Ë¤Î¤ß½ñ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¤É¤Î¥»¥¯¥·¥ç¥ó¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¤ë¤«¤òÃΤ뤿¤á¤Ë¤Ï + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î ¥³¥ó¥Æ¥­¥¹¥È ¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£¾Ü¤·¤¤¾ðÊó¤Ï¡¢ + Directory, Location, Files + ¥»¥¯¥·¥ç¥ó¤ÎÆ°ºîË¡¤Ë¤¢¤ê¤Þ¤¹¡£

+
top
+
+

.htaccess ¥Õ¥¡¥¤¥ë

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

Apache ¤Ç¤Ï¥¦¥§¥Ö¥Ä¥ê¡¼¤ÎÃæ¤ËÃÖ¤«¤ì¤¿ÆÃÊ̤ʥե¡¥¤¥ë¤ò»È¤Ã¤Æ + ÈóÃæ±û½¸¸¢Åª¤ÊÀßÄê´ÉÍý¤ò¤Ç¤­¤Þ¤¹¡£¤½¤ÎÆÃÊ̤ʥե¡¥¤¥ë¤ÏÉáÄÌ¤Ï + .htaccess ¤È¤¤¤¦Ì¾Á°¤Ç¡¢ + AccessFileName + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤É¤ó¤Ê̾Á°¤Ë¤Ç¤â»ØÄê¤Ç¤­¤Þ¤¹¡£ + .htaccess + ¥Õ¥¡¥¤¥ë¤Ë½ñ¤«¤ì¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Õ¥¡¥¤¥ë¤òÃÖ¤¤¤¿ + ¥Ç¥£¥ì¥¯¥È¥ê¤È¤½¤ÎÁ´¤Æ¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ËŬÍѤµ¤ì¤Þ¤¹¡£ + .htaccess ¥Õ¥¡¥¤¥ë¤Ï¡¢¥á¥¤¥ó¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ÈƱ¤¸ + ¹½Ê¸¤ò»È¤¤¤Þ¤¹¡£ + .htaccess + ¥Õ¥¡¥¤¥ë¤Ï¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤ÇÆɤ߹þ¤Þ¤ì¤ë¤¿¤á¡¢ + Êѹ¹¤Ï¤¹¤°¤ËÈ¿±Ç¤µ¤ì¤Þ¤¹¡£

+ +

¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ .htaccess + ¥Õ¥¡¥¤¥ë¤Ë½ñ¤±¤ë¤«¤òÄ´¤Ù¤ë¤Ë¤Ï¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥³¥ó¥Æ¥­¥¹¥È + ¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£¥µ¡¼¥Ð´ÉÍý¼Ô¤Ï¤µ¤é¤Ë¥á¥¤¥óÀßÄê¥Õ¥¡¥¤¥ë¤Î + AllowOverride + ¤òÀßÄꤹ¤ë¤³¤È¤Ç¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò .htaccess + ¥Õ¥¡¥¤¥ë¤Ë½ñ¤±¤ë¤è¤¦¤Ë¤¹¤ë¤«¤òÀ©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

.htaccess ¥Õ¥¡¥¤¥ë¤Ë´Ø¤¹¤ë¾Ü¤·¤¤¾ðÊó¤Ï + .htaccess ¥Á¥å¡¼¥È¥ê¥¢¥ë + ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+
+

Available Languages:  de  | + en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/configuring.html.ko.euc-kr b/docs/manual/configuring.html.ko.euc-kr new file mode 100644 index 00000000..94e13fe2 --- /dev/null +++ b/docs/manual/configuring.html.ko.euc-kr @@ -0,0 +1,150 @@ + + + +¼³Á¤ÆÄÀÏ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¼³Á¤ÆÄÀÏ

+
+

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

+
+ +

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ¼³Á¤ÇÏ´Â ÆÄÀϵéÀ» ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

ÁÖ¼³Á¤ÆÄÀÏ

+ +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

ÀÏ¹Ý ¹®¼­ ÆÄÀÏÀÎ ¼³Á¤ÆÄÀÏ¿¡ Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡¸¦ + ¼³Á¤ÇÑ´Ù. ÁÖ¼³Á¤ÆÄÀÏÀ» º¸Åë httpd.conf¶ó°í + ºÎ¸¥´Ù. ÀÌ ÆÄÀÏÀÇ À§Ä¡´Â ÄÄÆÄÀϽà Á¤ÇØÁö³ª, -f + ¸í·ÉÇà ¿É¼ÇÀ¸·Î ÁöÁ¤ÇØÁÙ ¼ö ÀÖ´Ù. ¶Ç ´Ù¸¥ ¼³Á¤ÆÄÀÏÀ» Include Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© Æ÷ÇÔÇÒ + ¼ö ÀÖ°í, ¿ÍÀϵåÄ«µå¸¦ »ç¿ëÇÏ¿© ¸¹Àº ¼³Á¤ÆÄÀÏÀ» Æ÷ÇÔÇÒ ¼öµµ + ÀÖ´Ù. ÀÌ °æ¿ì Áö½Ã¾î¸¦ ¾î¶² ¼³Á¤ÆÄÀÏ¿¡³ª »ç¿ëÇصµ µÈ´Ù. + ÁÖ¼³Á¤ÆÄÀÏÀ» ¼öÁ¤ÇÏ¸é ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇϰųª Àç½ÃÀÛÇÑ ÀÌÈÄ¿¡ + ¹Ý¿µµÈ´Ù.

+ +

¼­¹ö´Â mime ¹®¼­Å¸ÀÔÀ» ´ãÀº ÆÄÀϵµ Àд´Ù. ÆÄÀϸíÀº + TypesConfig Áö½Ã¾î·Î + ¼³Á¤ÇÏ°í, ±âº»°ªÀº mime.typesÀÌ´Ù.

+
top
+
+

¼³Á¤ÆÄÀÏ ¹®¹ý

+ + +

¾ÆÆÄÄ¡ ¼³Á¤ÆÄÀÏÀº ÇÑÁÙ¿¡ ÇÑ Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. ÁÙ ¸¶Áö¸· + ¹®ÀÚ°¡ ¹é½½·¡½¬ "\"À̸é Áö½Ã¾î°¡ ´ÙÀ½ ÁÙ¿¡¼­ °è¼ÓµÊÀ» ¶æÇÑ´Ù. + ÀÌ °æ¿ì ¹é½½·¡½¬ µÚ¿¡ ¾î¶² ¹®ÀÚ³ª °ø¹éµµ ³ª¿À¸é ¾ÈµÈ´Ù.

+ +

¼³Á¤ÆÄÀÏÀÇ Áö½Ã¾î´Â ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö ¾ÊÁö¸¸, Áö½Ã¾îÀÇ + ¾Æ±Ô¸ÕÆ®´Â ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏ´Â °æ¿ì°¡ ÀÖ´Ù. Çؽ¬¹®ÀÚ "#"·Î + ½ÃÀÛÇÏ´Â ÁÙÀº ÁÖ¼®À¸·Î ¹«½ÃÇÑ´Ù. ÁÖ¼®À» ¼³Á¤ Áö½Ã¾î¿Í °°Àº + ÁÙ¿¡ »ç¿ëÇÒ ¼ö ¾ø´Ù. ºóÁÙ°ú Áö½Ã¾î ¾Õ¿¡ ³ª¿À´Â + °ø¹éÀº ¹«½ÃÇϹǷÎ, °£°áÇÏ°Ô º¸À̵µ·Ï Áö½Ã¾î¸¦ ÁÙµéÀÓÇÒ(indent) + ¼ö ÀÖ´Ù.

+ +

apachectl configtest³ª -t ¸í·ÉÇà + ¿É¼ÇÀ» »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏÁö ¾Ê°íµµ ¼³Á¤ÆÄÀÏÀÇ ¹®¹ý + ¿À·ù¸¦ °Ë»çÇÒ ¼ö ÀÖ´Ù.

+
top
+
+

¸ðµâ

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

¾ÆÆÄÄ¡´Â ¸ðµâÈ­µÈ ¼­¹ö´Ù. ÀÌ´Â ¸Å¿ì ±âº»ÀûÀÎ ±â´É¸¸ÀÌ + ¼­¹ö Çٽɿ¡ Æ÷ÇÔµÇÀÖÀ½À» ¶æÇÑ´Ù. ¾ÆÆÄÄ¡´Â ¸ðµâÀ» Àоîµé¿©¼­ ±â´ÉÀ» + È®ÀåÇÑ´Ù. ±âº»ÀûÀ¸·Î ÄÄÆÄÀÏÇÏ¸é ¼­¹ö¿¡ base ¸ðµâµéÀÌ Æ÷ÇԵȴÙ. + ¼­¹ö¸¦ µ¿ÀûÀ¸·Î ÀоîµéÀÌ´Â ¸ðµâÀ» + »ç¿ëÇÒ ¼ö ÀÖ°Ô ÄÄÆÄÀÏÇÏ¿´´Ù¸é ¸ðµâÀ» µû·Î ÄÄÆÄÀÏÇÏ¿© ¾Æ¹«¶§³ª + LoadModule Áö½Ã¾î·Î + Ãß°¡ÇÒ ¼ö ÀÖ´Ù. ±×·¸Áö ¾ÊÀ¸¸é ¸ðµâÀ» Ãß°¡Çϰųª »©±âÀ§ÇØ + ¾ÆÆÄÄ¡¸¦ ´Ù½Ã ÄÄÆÄÀÏÇØ¾ß ÇÑ´Ù. ¼³Á¤ Áö½Ã¾î¸¦ IfModule ºí·ÏÀ¸·Î °¨½Î¼­ ƯÁ¤ + ¸ðµâÀÌ ÀÖ´Â °æ¿ì¿¡¸¸ ¼±ÅÃÀûÀ¸·Î ó¸®ÇÒ ¼ö ÀÖ´Ù.

+ +

ÇöÀç ¼­¹ö¿¡ ¾î¶² ¸ðµâÀÌ ÄÄÆÄÀϵÇÀÖ´ÂÁö º¸·Á¸é -l + ¸í·ÉÇà ¿É¼ÇÀ» »ç¿ëÇÑ´Ù.

+
top
+
+

Áö½Ã¾î Àû¿ë¹üÀ§

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

ÁÖ¼³Á¤ÆÄÀÏ¿¡ ÀÖ´Â Áö½Ã¾î´Â ¼­¹ö Àüü¿¡ Àû¿ëµÈ´Ù. Áö½Ã¾î°¡ + ¼­¹öÀÇ ÀϺο¡¸¸ Àû¿ëµÇ°Ô ÇÏ·Á¸é Áö½Ã¾î¸¦ <Directory>, <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, <LocationMatch> ¼½¼Ç ¾È¿¡ µÎ¾î¾ßÇÑ´Ù. + ÀÌ ¼½¼ÇµéÀº ±×µéÀÌ °¨½Î´Â Áö½Ã¾îÀÇ Àû¿ë¹üÀ§¸¦ ÆÄÀϽýºÅÛÀ̳ª + URLÀÇ Æ¯Á¤ À§Ä¡·Î ÇÑÁ¤ÇÑ´Ù. ¶Ç, ¼­·Î °ãÃļ­ »ç¿ëÇÒ ¼ö Àֱ⶧¹®¿¡ + ¸Å¿ì ¼¼¹ÐÇÑ ¼³Á¤ÀÌ °¡´ÉÇÏ´Ù.

+ +

¾ÆÆÄÄ¡´Â ¿©·¯ ´Ù¸¥ À¥»çÀÌÆ®¸¦ µ¿½Ã¿¡ ¼­ºñ½ºÇÏ´Â + ´É·ÂÀÌ ÀÖ´Ù. À̸¦ °¡»óÈ£½ºÆ®¶ó°í ÇÑ´Ù. + Áö½Ã¾î¸¦ + <VirtualHost> + ¼½¼Ç ¾È¿¡ µÎ¾î ƯÁ¤ À¥»çÀÌÆ®¿¡¸¸ Áö½Ã¾î¸¦ Àû¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

Áö½Ã¾î´Â ´ëºÎºÐ ¾î¶² ¼½¼Ç¿¡ ³ª¿Íµµ µÇÁö¸¸, ¾î¶² Áö½Ã¾î´Â + ƯÁ¤ Àå¼Ò¿¡¼­ Àǹ̰¡ ¾ø´Ù. ¿¹¸¦ µé¾î ÇÁ·Î¼¼½º »ý¼ºÀ» Á¶ÀýÇÏ´Â + Áö½Ã¾î´Â ÁÖ¼­¹ö¼³Á¤ Àå¼Ò¿¡¼­¸¸ »ç¿ëÇÒ ¼ö ÀÖ´Ù. Áö½Ã¾î°¡ + ¾î¶² ¼½¼Ç¿¡ À§Ä¡ÇÒ ¼ö ÀÖ´ÂÁö ¾Ë·Á¸é Áö½Ã¾îÀÇ »ç¿ëÀå¼Ò¸¦ È®ÀÎÇ϶ó. + ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â ¾î¶»°Ô Directory, + Location, Files ¼½¼ÇÀÌ µ¿ÀÛÇϳª¸¦ Âü°íÇ϶ó.

+
top
+
+

.htaccess ÆÄÀÏ

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

¾ÆÆÄÄ¡´Â Ưº°ÇÑ ÆÄÀÏÀ» »ç¿ëÇÏ¿© ¼³Á¤À» + ³ª´²¼­(ºÐ±ÇÀûÀ¸·Î) °ü¸®ÇÒ ¼ö ÀÖ´Ù. ÀÌ Æ¯º°ÇÑ ÆÄÀÏÀ» º¸Åë + .htaccess¶ó°í ºÎ¸£Áö¸¸, À̸§Àº AccessFileName Áö½Ã¾î·Î + ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù. .htaccess ÆÄÀÏ¿¡ ÀÖ´Â Áö½Ã¾î´Â + ÆÄÀÏÀÌ ÀÖ´Â µð·ºÅ丮¿Í ¸ðµç ÇÏÀ§µð·ºÅ丮¿¡ Àû¿ëµÈ´Ù. + .htaccess ÆÄÀÏÀº ÁÖ¼³Á¤ÆÄÀÏ°ú °°Àº ¹®¹ýÀ» + µû¸¥´Ù. .htaccess ÆÄÀÏÀº ¸Å ¿äû¶§¸¶´Ù Àб⶧¹®¿¡ + ÆÄÀÏÀ» ¼öÁ¤Çϸé Áï½Ã È¿°ú¸¦ º¼ ¼ö ÀÖ´Ù.

+ +

¾î¶² Áö½Ã¾î¸¦ .htaccess ÆÄÀÏ¿¡ »ç¿ëÇÒ ¼ö + ÀÖ´ÂÁö ¾Ë·Á¸é Áö½Ã¾îÀÇ »ç¿ëÀå¼Ò¸¦ + È®ÀÎÇ϶ó. ¼­¹ö °ü¸®ÀÚ´Â ÁÖ¼³Á¤ÆÄÀÏÀÇ AllowOverride Áö½Ã¾î·Î + .htaccess ÆÄÀÏ¿¡ ¾î¶² Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖ´ÂÁö + Á¶ÀýÇÒ ¼ö ÀÖ´Ù.

+ +

.htaccess ÆÄÀÏ¿¡ ´ëÇÑ ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â + .htaccess ÅõÅ丮¾óÀ» + Âü°íÇ϶ó.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/content-negotiation.html b/docs/manual/content-negotiation.html new file mode 100644 index 00000000..3fbf5ee0 --- /dev/null +++ b/docs/manual/content-negotiation.html @@ -0,0 +1,11 @@ +URI: content-negotiation.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: content-negotiation.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: content-negotiation.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/content-negotiation.html.en b/docs/manual/content-negotiation.html.en new file mode 100644 index 00000000..2dfb02e8 --- /dev/null +++ b/docs/manual/content-negotiation.html.en @@ -0,0 +1,679 @@ + + + +Content Negotiation - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Content Negotiation

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + +

Apache supports content negotiation as described in + the HTTP/1.1 specification. It can choose the best + representation of a resource based on the browser-supplied + preferences for media type, languages, character set and + encoding. It also implements a couple of features to give + more intelligent handling of requests from browsers that send + incomplete negotiation information.

+ +

Content negotiation is provided by the + mod_negotiation module, which is compiled in + by default.

+
+ +
top
+
+

About Content Negotiation

+ +

A resource may be available in several different + representations. For example, it might be available in + different languages or different media types, or a combination. + One way of selecting the most appropriate choice is to give the + user an index page, and let them select. However it is often + possible for the server to choose automatically. This works + because browsers can send, as part of each request, information + about what representations they prefer. For example, a browser + could indicate that it would like to see information in French, + if possible, else English will do. Browsers indicate their + preferences by headers in the request. To request only French + representations, the browser would send

+ +

Accept-Language: fr

+ +

Note that this preference will only be applied when there is + a choice of representations and they vary by language.

+ +

As an example of a more complex request, this browser has + been configured to accept French and English, but prefer + French, and to accept various media types, preferring HTML over + plain text or other text types, and preferring GIF or JPEG over + other media types, but also allowing any other media type as a + last resort:

+ +

+ Accept-Language: fr; q=1.0, en; q=0.5
+ Accept: text/html; q=1.0, text/*; q=0.8, image/gif; q=0.6, image/jpeg; q=0.6, image/*; q=0.5, */*; q=0.1 +

+ +

Apache supports 'server driven' content negotiation, as + defined in the HTTP/1.1 specification. It fully supports the + Accept, Accept-Language, + Accept-Charset andAccept-Encoding + request headers. Apache also supports 'transparent' + content negotiation, which is an experimental negotiation + protocol defined in RFC 2295 and RFC 2296. It does not offer + support for 'feature negotiation' as defined in these RFCs.

+ +

A resource is a conceptual entity + identified by a URI (RFC 2396). An HTTP server like Apache + provides access to representations of the + resource(s) within its namespace, with each representation in + the form of a sequence of bytes with a defined media type, + character set, encoding, etc. Each resource may be associated + with zero, one, or more than one representation at any given + time. If multiple representations are available, the resource + is referred to as negotiable and each of its + representations is termed a variant. The ways + in which the variants for a negotiable resource vary are called + the dimensions of negotiation.

+
top
+
+

Negotiation in Apache

+ +

In order to negotiate a resource, the server needs to be + given information about each of the variants. This is done in + one of two ways:

+ +
    +
  • Using a type map (i.e., a *.var + file) which names the files containing the variants + explicitly, or
    • + +
  • Using a 'MultiViews' search, where the server does an + implicit filename pattern match and chooses from among the + results.
    • +
+ +

Using a type-map file

+ +

A type map is a document which is associated with the handler + named type-map (or, for backwards-compatibility with + older Apache configurations, the MIME-type + application/x-type-map). Note that to use this + feature, you must have a handler set in the configuration that + defines a file suffix as type-map; this is best done + with

+ +

AddHandler type-map .var

+ +

in the server configuration file.

+ +

Type map files should have the same name as the resource + which they are describing, and have an entry for each available + variant; these entries consist of contiguous HTTP-format header + lines. Entries for different variants are separated by blank + lines. Blank lines are illegal within an entry. It is + conventional to begin a map file with an entry for the combined + entity as a whole (although this is not required, and if + present will be ignored). An example map file is shown below. + This file would be named foo.var, as it describes + a resource named foo.

+ +

+ URI: foo
+
+ URI: foo.en.html
+ Content-type: text/html
+ Content-language: en
+
+ URI: foo.fr.de.html
+ Content-type: text/html;charset=iso-8859-2
+ Content-language: fr, de
+

+

Note also that a typemap file will take precedence over the + filename's extension, even when Multiviews is on. If the + variants have different source qualities, that may be indicated + by the "qs" parameter to the media type, as in this picture + (available as JPEG, GIF, or ASCII-art):

+ +

+ URI: foo
+
+ URI: foo.jpeg
+ Content-type: image/jpeg; qs=0.8
+
+ URI: foo.gif
+ Content-type: image/gif; qs=0.5
+
+ URI: foo.txt
+ Content-type: text/plain; qs=0.01
+

+ +

qs values can vary in the range 0.000 to 1.000. Note that + any variant with a qs value of 0.000 will never be chosen. + Variants with no 'qs' parameter value are given a qs factor of + 1.0. The qs parameter indicates the relative 'quality' of this + variant compared to the other available variants, independent + of the client's capabilities. For example, a JPEG file is + usually of higher source quality than an ASCII file if it is + attempting to represent a photograph. However, if the resource + being represented is an original ASCII art, then an ASCII + representation would have a higher source quality than a JPEG + representation. A qs value is therefore specific to a given + variant depending on the nature of the resource it + represents.

+ +

The full list of headers recognized is available in the mod_negotation + typemap documentation.

+ + +

Multiviews

+ +

MultiViews is a per-directory option, meaning it + can be set with an Options + directive within a <Directory>, <Location> or <Files> section in + httpd.conf, or (if AllowOverride is properly set) in + .htaccess files. Note that Options All + does not set MultiViews; you have to ask for it by + name.

+ +

The effect of MultiViews is as follows: if the + server receives a request for /some/dir/foo, if + /some/dir has MultiViews enabled, and + /some/dir/foo does not exist, then the + server reads the directory looking for files named foo.*, and + effectively fakes up a type map which names all those files, + assigning them the same media types and content-encodings it + would have if the client had asked for one of them by name. It + then chooses the best match to the client's requirements.

+ +

MultiViews may also apply to searches for the file + named by the DirectoryIndex directive, if the + server is trying to index a directory. If the configuration files + specify

+

DirectoryIndex index

+

then the server will arbitrate between index.html + and index.html3 if both are present. If neither + are present, and index.cgi is there, the server + will run it.

+ +

If one of the files found when reading the directory does not + have an extension recognized by mod_mime to designate + its Charset, Content-Type, Language, or Encoding, then the result + depends on the setting of the MultiViewsMatch directive. This + directive determines whether handlers, filters, and other + extension types can participate in MultiViews negotiation.

+ +
top
+
+

The Negotiation Methods

+ +

After Apache has obtained a list of the variants for a given + resource, either from a type-map file or from the filenames in + the directory, it invokes one of two methods to decide on the + 'best' variant to return, if any. It is not necessary to know + any of the details of how negotiation actually takes place in + order to use Apache's content negotiation features. However the + rest of this document explains the methods used for those + interested.

+ +

There are two negotiation methods:

+ +
    +
  1. Server driven negotiation with the Apache + algorithm is used in the normal case. The Apache + algorithm is explained in more detail below. When this + algorithm is used, Apache can sometimes 'fiddle' the quality + factor of a particular dimension to achieve a better result. + The ways Apache can fiddle quality factors is explained in + more detail below.
    2. + +
  2. Transparent content negotiation is used + when the browser specifically requests this through the + mechanism defined in RFC 2295. This negotiation method gives + the browser full control over deciding on the 'best' variant, + the result is therefore dependent on the specific algorithms + used by the browser. As part of the transparent negotiation + process, the browser can ask Apache to run the 'remote + variant selection algorithm' defined in RFC 2296.
    3. +
+ +

Dimensions of Negotiation

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
DimensionNotes
Media TypeBrowser indicates preferences with the Accept + header field. Each item can have an associated quality factor. + Variant description can also have a quality factor (the "qs" + parameter).
LanguageBrowser indicates preferences with the + Accept-Language header field. Each item can have + a quality factor. Variants can be associated with none, one or + more than one language.
EncodingBrowser indicates preference with the + Accept-Encoding header field. Each item can have + a quality factor.
CharsetBrowser indicates preference with the + Accept-Charset header field. Each item can have a + quality factor. Variants can indicate a charset as a parameter + of the media type.
+ + +

Apache Negotiation Algorithm

+ +

Apache can use the following algorithm to select the 'best' + variant (if any) to return to the browser. This algorithm is + not further configurable. It operates as follows:

+ +
    +
  1. First, for each dimension of the negotiation, check the + appropriate Accept* header field and assign a + quality to each variant. If the Accept* header for + any dimension implies that this variant is not acceptable, + eliminate it. If no variants remain, go to step 4.
    2. + +
  2. + Select the 'best' variant by a process of elimination. Each + of the following tests is applied in order. Any variants + not selected at each test are eliminated. After each test, + if only one variant remains, select it as the best match + and proceed to step 3. If more than one variant remains, + move on to the next test. + +
      +
    1. Multiply the quality factor from the Accept + header with the quality-of-source factor for this variants + media type, and select the variants with the highest + value.
      2. + +
    2. Select the variants with the highest language quality + factor.
      3. + +
    3. Select the variants with the best language match, + using either the order of languages in the + Accept-Language header (if present), or else + the order of languages in the LanguagePriority + directive (if present).
      4. + +
    4. Select the variants with the highest 'level' media + parameter (used to give the version of text/html media + types).
      5. + +
    5. Select variants with the best charset media + parameters, as given on the Accept-Charset + header line. Charset ISO-8859-1 is acceptable unless + explicitly excluded. Variants with a text/* + media type but not explicitly associated with a particular + charset are assumed to be in ISO-8859-1.
      6. + +
    6. Select those variants which have associated charset + media parameters that are not ISO-8859-1. If + there are no such variants, select all variants + instead.
      7. + +
    7. Select the variants with the best encoding. If there + are variants with an encoding that is acceptable to the + user-agent, select only these variants. Otherwise if + there is a mix of encoded and non-encoded variants, + select only the unencoded variants. If either all + variants are encoded or all variants are not encoded, + select all variants.
      8. + +
    8. Select the variants with the smallest content + length.
      9. + +
    9. Select the first variant of those remaining. This + will be either the first listed in the type-map file, or + when variants are read from the directory, the one whose + file name comes first when sorted using ASCII code + order.
      10. +
    +
    3. + +
  3. The algorithm has now selected one 'best' variant, so + return it as the response. The HTTP response header + Vary is set to indicate the dimensions of + negotiation (browsers and caches can use this information when + caching the resource). End.
    4. + +
  4. To get here means no variant was selected (because none + are acceptable to the browser). Return a 406 status (meaning + "No acceptable representation") with a response body + consisting of an HTML document listing the available + variants. Also set the HTTP Vary header to + indicate the dimensions of variance.
    5. +
+ +
top
+
+

Fiddling with Quality + Values

+ +

Apache sometimes changes the quality values from what would + be expected by a strict interpretation of the Apache + negotiation algorithm above. This is to get a better result + from the algorithm for browsers which do not send full or + accurate information. Some of the most popular browsers send + Accept header information which would otherwise + result in the selection of the wrong variant in many cases. If a + browser sends full and correct information these fiddles will not + be applied.

+ +

Media Types and Wildcards

+ +

The Accept: request header indicates preferences + for media types. It can also include 'wildcard' media types, such + as "image/*" or "*/*" where the * matches any string. So a request + including:

+ +

Accept: image/*, */*

+ +

would indicate that any type starting "image/" is acceptable, + as is any other type. + Some browsers routinely send wildcards in addition to explicit + types they can handle. For example:

+ +

+ Accept: text/html, text/plain, image/gif, image/jpeg, */* +

+

The intention of this is to indicate that the explicitly listed + types are preferred, but if a different representation is + available, that is ok too. Using explicit quality values, + what the browser really wants is something like:

+

+ Accept: text/html, text/plain, image/gif, image/jpeg, */*; q=0.01 +

+

The explicit types have no quality factor, so they default to a + preference of 1.0 (the highest). The wildcard */* is given a + low preference of 0.01, so other types will only be returned if + no variant matches an explicitly listed type.

+ +

If the Accept: header contains no q + factors at all, Apache sets the q value of "*/*", if present, to + 0.01 to emulate the desired behavior. It also sets the q value of + wildcards of the format "type/*" to 0.02 (so these are preferred + over matches against "*/*". If any media type on the + Accept: header contains a q factor, these special + values are not applied, so requests from browsers which + send the explicit information to start with work as expected.

+ + +

Language Negotiation Exceptions

+ +

New in Apache 2.0, some exceptions have been added to the + negotiation algorithm to allow graceful fallback when language + negotiation fails to find a match.

+ +

When a client requests a page on your server, but the server + cannot find a single page that matches the + Accept-language sent by + the browser, the server will return either a "No Acceptable + Variant" or "Multiple Choices" response to the client. To avoid + these error messages, it is possible to configure Apache to ignore + the Accept-language in these cases and provide a + document that does not explicitly match the client's request. The + ForceLanguagePriority + directive can be used to override one or both of these error + messages and substitute the servers judgement in the form of the + LanguagePriority + directive.

+ +

The server will also attempt to match language-subsets when no + other match can be found. For example, if a client requests + documents with the language en-GB for British + English, the server is not normally allowed by the HTTP/1.1 + standard to match that against a document that is marked as simply + en. (Note that it is almost surely a configuration + error to include en-GB and not en in the + Accept-Language header, since it is very unlikely + that a reader understands British English, but doesn't understand + English in general. Unfortunately, many current clients have + default configurations that resemble this.) However, if no other + language match is possible and the server is about to return a "No + Acceptable Variants" error or fallback to the LanguagePriority, the server + will ignore the subset specification and match en-GB + against en documents. Implicitly, Apache will add + the parent language to the client's acceptable language list with + a very low quality value. But note that if the client requests + "en-GB; q=0.9, fr; q=0.8", and the server has documents + designated "en" and "fr", then the "fr" document will be returned. + This is necessary to maintain compliance with the HTTP/1.1 + specification and to work effectively with properly configured + clients.

+ +

In order to support advanced techniques (such as cookies or + special URL-paths) to determine the user's preferred language, + since Apache 2.0.47 mod_negotiation recognizes + the environment variable + prefer-language. If it exists and contains an + appropriate language tag, mod_negotiation will + try to select a matching variant. If there's no such variant, + the normal negotiation process applies.

+ +

Example

+ SetEnvIf Cookie "language=(.+)" prefer-language=$1 + Header append Vary cookie +

+ +
top
+
+

Extensions to Transparent Content +Negotiation

+ +

Apache extends the transparent content negotiation protocol (RFC +2295) as follows. A new {encoding ..} element is used in +variant lists to label variants which are available with a specific +content-encoding only. The implementation of the RVSA/1.0 algorithm +(RFC 2296) is extended to recognize encoded variants in the list, and +to use them as candidate variants whenever their encodings are +acceptable according to the Accept-Encoding request +header. The RVSA/1.0 implementation does not round computed quality +factors to 5 decimal places before choosing the best variant.

+
top
+
+

Note on hyperlinks and naming conventions

+ +

If you are using language negotiation you can choose between + different naming conventions, because files can have more than + one extension, and the order of the extensions is normally + irrelevant (see the mod_mime documentation + for details).

+ +

A typical file has a MIME-type extension (e.g., + html), maybe an encoding extension (e.g., + gz), and of course a language extension + (e.g., en) when we have different + language variants of this file.

+ +

Examples:

+ +
    +
  • foo.en.html
    • + +
  • foo.html.en
    • + +
  • foo.en.html.gz
    • +
+ +

Here some more examples of filenames together with valid and + invalid hyperlinks:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FilenameValid hyperlinkInvalid hyperlink
foo.html.enfoo
+ foo.html		-
foo.en.htmlfoofoo.html
foo.html.en.gzfoo
+ foo.html		foo.gz
+ foo.html.gz
foo.en.html.gzfoofoo.html
+ foo.html.gz
+ foo.gz
foo.gz.html.enfoo
+ foo.gz
+ foo.gz.html		foo.html
foo.html.gz.enfoo
+ foo.html
+ foo.html.gz		foo.gz
+ +

Looking at the table above, you will notice that it is always + possible to use the name without any extensions in a hyperlink + (e.g., foo). The advantage is that you + can hide the actual type of a document rsp. file and can change + it later, e.g., from html to + shtml or cgi without changing any + hyperlink references.

+ +

If you want to continue to use a MIME-type in your + hyperlinks (e.g. foo.html) the language + extension (including an encoding extension if there is one) + must be on the right hand side of the MIME-type extension + (e.g., foo.html.en).

+
top
+
+

Note on Caching

+ +

When a cache stores a representation, it associates it with + the request URL. The next time that URL is requested, the cache + can use the stored representation. But, if the resource is + negotiable at the server, this might result in only the first + requested variant being cached and subsequent cache hits might + return the wrong response. To prevent this, Apache normally + marks all responses that are returned after content negotiation + as non-cacheable by HTTP/1.0 clients. Apache also supports the + HTTP/1.1 protocol features to allow caching of negotiated + responses.

+ +

For requests which come from a HTTP/1.0 compliant client + (either a browser or a cache), the directive CacheNegotiatedDocs can be + used to allow caching of responses which were subject to + negotiation. This directive can be given in the server config or + virtual host, and takes no arguments. It has no effect on requests + from HTTP/1.1 clients.

+ +

For HTTP/1.1 clients, Apache sends a Vary HTTP + response header to indicate the negotiation dimensions for the + response. Caches can use this information to determine whether a + subsequent request can be served from the local copy. To + encourage a cache to use the local copy regardless of the + negotiation dimensions, set the force-no-vary environment variable.

+ +
top
+
+

More Information

+ +

For more information about content negotiation, see Alan + J. Flavell's Language + Negotiation Notes. But note that this document may not be + updated to include changes in Apache 2.0.

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/content-negotiation.html.ja.euc-jp b/docs/manual/content-negotiation.html.ja.euc-jp new file mode 100644 index 00000000..27578375 --- /dev/null +++ b/docs/manual/content-negotiation.html.ja.euc-jp @@ -0,0 +1,729 @@ + + + +¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + +

Apache ¤Ï HTTP/1.1 ¤Îµ¬³Ê¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤ë¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò + ¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£ + ¥Ö¥é¥¦¥¶¤Ë¤è¤êÄ󶡤µ¤ì¤¿¥á¥Ç¥£¥¢¥¿¥¤¥×¡¢ + ¸À¸ì¡¢Ê¸»ú¥»¥Ã¥È¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ÎÍ¥Àè·¹¸þ¤Ë´ð¤Å¤¤¤Æ¡¢ + ºÇŬ¤Ê¥ê¥½¡¼¥¹¤Îɽ¸½¤òÁªÂò¤Ç¤­¤Þ¤¹¡£ + ¤Þ¤¿¡¢ÉÔ´°Á´¤Ê¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¾ðÊó¤òÁ÷¤Ã¤Æ¤¯¤ë¥Ö¥é¥¦¥¶¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤ò + ¤â¤Ã¤È¸­¤¯¼è¤ê°·¤¨¤ë¤è¤¦¡¢¤¤¤¯¤Ä¤«µ¡Ç½¤â¼ÂÁõ¤·¤Æ¤¢¤ê¤Þ¤¹¡£

+ +

¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Ï + mod_negotiation + ¥â¥¸¥å¡¼¥ë¤Ë¤è¤Ã¤ÆÄ󶡤µ¤ì¤Æ¤¤¤Æ¡¢¥Ç¥Õ¥©¥ë¥È¤ÇÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£

+
+ +
top
+
+

¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Ë¤Ä¤¤¤Æ

+ +

¥ê¥½¡¼¥¹¤Ï¡¢´ö¤Ä¤«°Û¤Ê¤Ã¤¿É½¸½¤ÇÍøÍѤǤ­¤ë¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£ + Î㤨¤Ð¡¢°Û¤Ê¤ë¸À¸ì¤ä°Û¤Ê¤ë¥á¥Ç¥£¥¢¥¿¥¤¥×¡¢ + ¤Þ¤¿¤Ï¤½¤ì¤é¤ÎÁȤ߹ç¤ï¤»¤ÇÍøÍѤǤ­¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£ + ¤â¤Ã¤È¤âŬ¤·¤¿ÁªÂò¤ò¤¹¤ëÊýË¡¤Î°ì¤Ä¤Ë¤Ï¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¥Ú¡¼¥¸¤ò + ¥æ¡¼¥¶¤Ë¸«¤»¤Æ¡¢¥æ¡¼¥¶¤ËÁª¤ó¤Ç¤â¤é¤¦ÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£ + ¤·¤«¤·¡¢¥µ¡¼¥Ð¤¬¼«Æ°Åª¤ËÁª¤Ö¤³¤È¤¬¤Ç¤­¤ë¾ì¹ç¤¬Â¿¤¯¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥Ö¥é¥¦¥¶¤¬¥ê¥¯¥¨¥¹¥ÈËè¤Ë¡¢ + ¤É¤Îɽ¸½¤òÓϹ¥¤¹¤ë¤«¤È¤¤¤¦¾ðÊó¤òÁ÷¤ë¤³¤È¤ÇÆ°ºî¤·¤Æ¤¤¤Þ¤¹¡£ + Î㤨¤Ð¥Ö¥é¥¦¥¶¤Ï¡¢²Äǽ¤Ê¤é¥Õ¥é¥ó¥¹¸ì¤Ç¾ðÊó¤ò¸«¤¿¤¤¡¢ + ÉÔ²Äǽ¤Ê¤é¤½¤ÎÂå¤ï¤ê¤Ë±Ñ¸ì¤Ç¤â¤è¤¤¤È¡¢ + ¼«Ê¬¤ÎÓϹ¥¤òÃΤ餻¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥Ö¥é¥¦¥¶¤Ï¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¤Ç¼«Ê¬¤ÎÍ¥Àè·¹¸þ¤òÃΤ餻¤Þ¤¹¡£ + ¥Õ¥é¥ó¥¹¸ì¤Î¤ß¤Îɽ¸½¤òÍ׵᤹¤ë¾ì¹ç¤Ï¡¢¥Ö¥é¥¦¥¶¤Ï¼¡¤òÁ÷¤ê¤Þ¤¹¡£

+ +

Accept-Language: fr

+ +

¤³¤ÎÍ¥Àè·¹¸þ¤Ï¡¢ÁªÂò²Äǽ¤Êɽ¸½¤¬Â¸ºß¤·¤Æ¡¢ + ¸À¸ì¤Ë¤è¤Ã¤ÆÍÍ¡¹¤Êɽ¸½¤¬¤¢¤ë¾ì¹ç¤Ë¤Î¤ßŬÍѤµ¤ì¤ë + ¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

¤â¤Ã¤ÈÊ£»¨¤Ê¥ê¥¯¥¨¥¹¥È¤ÎÎã¤òµó¤²¤Þ¤·¤ç¤¦¡£ + ¤³¤Î¥Ö¥é¥¦¥¶¤Ï¥Õ¥é¥ó¥¹¸ì¤È±Ñ¸ì¤ò¼õ¤±ÉÕ¤±¤ë¡¢¤·¤«¤·¥Õ¥é¥ó¥¹¸ì¤ò¹¥¤à¡¢ + ¤½¤·¤ÆÍÍ¡¹¤Ê¥á¥Ç¥£¥¢¥¿¥¤¥×¤ò¼õ¤±ÉÕ¤±¤ë¤¬¡¢ + ¥×¥ì¥¤¥ó¥Æ¥­¥¹¥È¤ä¾¤Î¥¿¥¤¥×¤è¤ê¤Ï HTML ¤ò¹¥¤à¡¢ + ¾¤Î¥á¥Ç¥£¥¢¥¿¥¤¥×¤è¤ê¤Ï GIF ¤ä JPEG ¤ò¹¥¤à¡¢¤·¤«¤·ºÇ½ª¼êÃʤȤ·¤Æ + ¾¤Î¥á¥Ç¥£¥¢¥¿¥¤¥×¤â¼õ¤±ÉÕ¤±¤ë¡¢¤ÈÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

+ Accept-Language: fr; q=1.0, en; q=0.5
+ Accept: text/html; q=1.0, text/*; q=0.8, image/gif; q=0.6, image/jpeg; q=0.6, image/*; q=0.5, */*; q=0.1 +

+ +

Apache ¤Ï HTTP/1.1 µ¬³Ê¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë 'server + driven' ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£ + Accept, Accept-Language, + Accept-Charset, Accept-Encoding + ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤ò´°Á´¤Ë¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£Apache ¤Ï + 'transparent' ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤â¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¤¬¡¢ + ¤³¤ì¤Ï RFC 2295 ¤È RFC 2296 ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë»î¸³Åª¤Ê + ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¥×¥í¥È¥³¥ë¤Ç¤¹¡£ + ¤³¤ì¤é¤Î RFC¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë 'feature negotiation' + ¤Ï¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤»¤ó¡£

+ +

¥ê¥½¡¼¥¹¤È¤Ï URI + ¤ÇÆÃÄꤵ¤ì¤ë³µÇ°¾å¤Î¤â¤Î¤Î¤³¤È¤Ç¤¹ (RFC 2396)¡£ Apache + ¤Î¤è¤¦¤Ê HTTP ¥µ¡¼¥Ð¤Ï¡¢¤½¤Î̾Á°¶õ´Ö¤ÎÃæ¤Ç¤Î + ¥ê¥½¡¼¥¹¤Îɽ¸½¤Ø¤Î¥¢¥¯¥»¥¹¤òÄ󶡤·¤Þ¤¹¡£ + ¤½¤ì¤¾¤ì¤Îɽ¸½¤Ï + ÄêµÁ¤µ¤ì¤¿¥á¥Ç¥£¥¢¥¿¥¤¥×¡¢Ê¸»ú¥»¥Ã¥È¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°Åù¤Î + ÉÕ°¤·¤¿¡¢¥Ð¥¤¥ÈÎó¤Î·Á¼°¤Ç¤¹¡£ + ¤½¤ì¤¾¤ì¤Î¥ê¥½¡¼¥¹¤Ï¤¢¤ë»þÅÀ¤Ç 0 ¸Ä¡¢1 ¸Ä¡¢¤½¤ì°Ê¾å¤Îɽ¸½¤È + ´ØÏ¢ÉÕ¤±¤é¤ì¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£Ê£¿ô¤Îɽ¸½¤¬ÍøÍѤǤ­¤ë¾ì¹ç¤Ï¡¢ + ¥ê¥½¡¼¥¹¤Ï¥Í¥´¥·¥¨¡¼¥·¥ç¥ó²Äǽ¤Ç¤¢¤ë¤È¤µ¤ì¡¢ + ¸Ä¡¹¤Îɽ¸½¤Ï variant ¤È¸Æ¤Ð¤ì¤Þ¤¹¡£ + ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó²Äǽ¤Ê¥ê¥½¡¼¥¹¤Î variant ¤¬°Û¤Ê¤ë¡¢ + ¤½¤Î¾õÂÖ¤ò»Ø¤·¤Æ¡¢ + ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î¼¡¸µ¤È¸Æ¤Ó¤Þ¤¹¡£

+
top
+
+

Apache ¤Ë¤ª¤±¤ë¥Í¥´¥·¥¨¡¼¥·¥ç¥ó

+ +

¥ê¥½¡¼¥¹¤ò¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ + ¥µ¡¼¥Ð¤Ï variant ¤½¤ì¤¾¤ì¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤òÃΤäƤª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï°Ê²¼¤ÎÆó¤Ä¤ÎÊýË¡¤Î¤É¤Á¤é¤«¤Ç¹Ô¤ï¤ì¤Þ¤¹¡£

+ +
    +
  • ¥¿¥¤¥×¥Þ¥Ã¥× + (¤¹¤Ê¤ï¤Á *.var ¥Õ¥¡¥¤¥ë) + ¤ò»È¤¦ÊýË¡¡£ ¤³¤ì¤Ï variant + ¤òÌÀ¼¨Åª¤Ëµó¤²¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤ò»ØÄꤷ¤Þ¤¹¡£
    • + +
  • 'Multiviews' + ¤ò»È¤Ã¤Æ¡¢¥µ¡¼¥Ð¤¬°ÅÌÛ¤ÎÆâ¤Ë¥Õ¥¡¥¤¥ë̾¤Ë¥Ñ¥¿¡¼¥ó¾È¹ç¤ò + ¹Ô¤Ê¤Ã¤Æ¤½¤Î·ë²Ì¤«¤éÁªÂò¤¹¤ëÊýË¡¡£
    • +
+ +

type-map ¥Õ¥¡¥¤¥ë¤ò»È¤¦

+ +

¥¿¥¤¥×¥Þ¥Ã¥×¤Ï type-map ¥Ï¥ó¥É¥é + (¤â¤·¤¯¤Ï¡¢¸Å¤¤ Apache + ¤ÎÀßÄê¤È²¼°Ì¸ß´¹¤Ç¤¢¤ë MIME ¥¿¥¤¥× + application/x-type-map) + ¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¥É¥­¥å¥á¥ó¥È¤Ç¤¹¡£ + ¤³¤Îµ¡Ç½¤ò»È¤¦¤¿¤á¤Ë¤Ï¡¢¤¢¤ë¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤ò + type-map + ¤È¤·¤ÆÄêµÁ¤¹¤ë¤è¤¦¤Ê¥Ï¥ó¥É¥é¤ò¡¢ + ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤ËÃÖ¤¯É¬Íפ¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤ì¤Ï

+ +

AddHandler type-map .var

+ +

¤ò¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Ë½ñ¤¯¤³¤È¤¬°ìÈÖÎɤ¤ÊýË¡¤Ç¤¹¡£

+ +

¥¿¥¤¥×¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤Ïµ­½Ò¤¹¤ë¥ê¥½¡¼¥¹¤ÈƱ¤¸Ì¾Á°¤ò»ý¤Ã¤Æ¤¤¤Æ¡¢ + ÍøÍѲÄǽ¤Ê variant ¤½¤ì¤¾¤ì¤Î¥¨¥ó¥È¥ê¤ò»ý¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤½¤·¤Æ¡¢¤³¤Î¥¨¥ó¥È¥ê¤ÏϢ³¤·¤¿ HTTP ¤Î¥Ø¥Ã¥À¹Ô¤Ç¹½À®¤µ¤ì¤Þ¤¹¡£ + °Û¤Ê¤ë variant ¤Î¤¿¤á¤Î¥¨¥ó¥È¥ê¤Ï¶õ¹Ô¤Ç¶èÀÚ¤é¤ì¤Æ¤¤¤Þ¤¹¡£ + ¥¨¥ó¥È¥êÃæ¤Ë¶õ¹Ô¤¬Ê£¿ô¤¢¤Ã¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ + ½¬´·Åª¤Ë¤Ï¡¢¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤ÏÁ´ÂΤò·ë¹ç¤·¤¿¤â¤Î¤Î¥¨¥ó¥È¥ê¤«¤é»Ï¤Þ¤ê¤Þ¤¹ + (¤·¤«¤·¤³¤ì¤Ïɬ¿Ü¤Ç¤Ï¤Ê¤¯¡¢¤¢¤Ã¤¿¤È¤·¤Æ¤â̵»ë¤µ¤ì¤ë¤â¤Î¤Ç¤¹)¡£ + ¼¡¤ËÎã¤ò¼¨¤·¤Þ¤¹¡£¤³¤Î¥Õ¥¡¥¤¥ë¤Ï¥ê¥½¡¼¥¹ foo + ¤òµ­½Ò¤·¤Æ¤¤¤ë¤Î¤Ç¡¢foo.var ¤È¤¤¤¦Ì¾Á°¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

+ URI: foo
+
+ URI: foo.en.html
+ Content-type: text/html
+ Content-language: en
+
+ URI: foo.fr.de.html
+ Content-type: text/html;charset=iso-8859-2
+ Content-language: fr, de
+

+

¤¿¤È¤¨ MultiViews ¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢ + ¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤è¤ê¥¿¥¤¥×¥Þ¥Ã¥×¤ÎÊý¤¬Í¥À踢¤ò»ý¤Ä¤È¤¤¤¦¤³¤È¤Ë¤â + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + variant ¤ÎÉʼÁ¤¬°ã¤¦¤È¤­¤Ï¡¢¤³¤Î²èÁü¤Î¤è¤¦¤Ë (JPEG, GIF, ASCII + ¥¢¡¼¥È¤¬¤¢¤ê¤Þ¤¹) ¥á¥Ç¥£¥¢¥¿¥¤¥×¤Î "qs" + ¥Ñ¥é¥á¡¼¥¿¤Ç»ØÄꤵ¤ì¤Þ¤¹¡£

+ +

+ URI: foo
+
+ URI: foo.jpeg
+ Content-type: image/jpeg; qs=0.8
+
+ URI: foo.gif
+ Content-type: image/gif; qs=0.5
+
+ URI: foo.txt
+ Content-type: text/plain; qs=0.01
+

+ +

qs ÃͤÎÈÏ°Ï¤Ï 0.000 ¤«¤é 1.000 ¤Ç¤¹¡£qs Ãͤ¬ + 0.000 ¤Î variant ¤Ï·è¤·¤Æ + ÁªÂò¤µ¤ì¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£'qs' ÃͤΤʤ¤ variant + ¤Ï qs ÃÍ 1.0 ¤ò Í¿¤¨¤é¤ì¤Þ¤¹¡£qs + ¥Ñ¥é¥á¡¼¥¿¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ÎǽÎϤ˴ط¸Ìµ¤¯¡¢Â¾¤Î variant ¤È + Èæ³Ó¤·¤¿¤È¤­¤Î variant + ¤ÎÁêÂÐŪ¤Ê¡ÖÉʼÁ¡×¤ò¼¨¤·¤Þ¤¹¡£ + Î㤨¤Ð¡¢¼Ì¿¿¤òɽ¸½¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤È¤­¤Ï JPEG + ¥Õ¥¡¥¤¥ë¤ÎÊý¤¬ÉáÄÌ¤Ï ASCII + ¥Õ¥¡¥¤¥ë¤è¤ê¤â¹â¤¤ÉʼÁ¤Ë¤Ê¤ê¤Þ¤¹¡£¤·¤«¤·¡¢¥ê¥½¡¼¥¹¤¬¸µ¡¹ + ASCII ¥¢¡¼¥È¤Çɽ¸½¤µ¤ì¤Æ¤¤¤ë¤È¤­¤Ï¡¢ASCII ¥Õ¥¡¥¤¥ë¤Î + Êý¤¬ JPEG ¥Õ¥¡¥¤¥ë¤è¤ê¤â¹â¤¤ÉʼÁ¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤Î¤è¤¦¤Ë¡¢qs + ¤Ï ɽ¸½¤µ¤ì¤ë¥ê¥½¡¼¥¹¤ÎÀ­¼Á¤Ë¤è¤Ã¤Æ variant + Ëè¤ËÆÃÍ­¤ÎÃͤò¼è¤ê¤Þ¤¹¡£

+ +

ǧ¼±¤µ¤ì¤ë¥Ø¥Ã¥À¤Î°ìÍ÷¤Ï + mod_negotiation + ¥É¥­¥å¥á¥ó¥È¤Ë¤¢¤ê¤Þ¤¹¡£

+ + +

Multiviews

+ +

MultiViews ¤Ï¥Ç¥£¥ì¥¯¥È¥êËè¤Î¥ª¥×¥·¥ç¥ó¤Ç¡¢ + httpd.conf¥Õ¥¡¥¤¥ë¤Î + <Directory>, + <Location>, + <Files> + ¥»¥¯¥·¥ç¥óÃæ¤ä¡¢(AllowOverride + ¤¬Å¬ÀÚ¤ÊÃÍ¤Ë ÀßÄꤵ¤ì¤Æ¤¤¤ë¤È) .htaccess + ¥Õ¥¡¥¤¥ë¤Ç Options + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤ÆÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + Options All ¤Ï + MultiViews + ¤ò¥»¥Ã¥È¤·¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ÌÀ¼¨Åª¤Ë + ¤½¤Î̾Á°¤ò½ñ¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£

+ +

MultiViews ¤Î¸ú²Ì¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹: + ¥µ¡¼¥Ð¤¬ /some/dir/foo + ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤ê¡¢/some/dir ¤Ç + MultiViews ¤¬Í­¸ú¤Ç¤¢¤Ã¤Æ¡¢ + /some/dir/foo ¤¬Â¸ºß¤·¤Ê¤¤¾ì¹ç¡¢ + ¥µ¡¼¥Ð¤Ï¥Ç¥£¥ì¥¯¥È¥ê¤òÆɤó¤Ç foo.* + ¤Ë¤¢¤Æ¤Ï¤Þ¤ëÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤òõ¤·¡¢ + »ö¼Â¾å¤½¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤ò¥Þ¥Ã¥×¤¹¤ë¥¿¥¤¥×¥Þ¥Ã¥×¤òºî¤ê¤Þ¤¹¡£ + ¤½¤Î¤È¤­¡¢¥á¥Ç¥£¥¢¥¿¥¤¥×¤È¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ï¡¢¤½¤Î¥Õ¥¡¥¤¥ë̾¤ò + ľÀÜ»ØÄꤷ¤¿¤È¤­¤ÈƱ¤¸¤â¤Î¤¬³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£ + ¤½¤ì¤«¤é¥¯¥é¥¤¥¢¥ó¥È¤ÎÍ×µá¤Ë°ìÈֹ礦¤â¤Î¤òÁª¤Ó¤Þ¤¹¡£

+ +

¥µ¡¼¥Ð¤¬¥Ç¥£¥ì¥¯¥È¥ê¤Îº÷°ú¤òºî¤í¤¦¤È¤·¤Æ¤¤¤ë¾ì¹ç¡¢ + MultiViews + ¤Ï DirectoryIndex + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤òõ¤¹²áÄø¤Ë¤â + ŬÍѤµ¤ì¤Þ¤¹¡£ÀßÄê¥Õ¥¡¥¤¥ë¤Ë

+

DirectoryIndex index

+

¤¬½ñ¤«¤ì¤Æ¤¤¤Æ¡¢index.html ¤È + index.html3 ¤¬ + ξÊý¸ºß¤·¤Æ¤¤¤ë¤È¡¢¥µ¡¼¥Ð¤Ï¤½¤ÎÃ椫¤é¤É¤Á¤é¤«¤òŬÅö¤ËÁª¤Ó¤Þ¤¹¡£ + ¤â¤·¤½¤ÎξÊý¤¬Â¸ºß¤»¤º¤Ë index.cgi + ¤¬Â¸ºß¤·¤Æ¤¤¤ë¤È¡¢ ¥µ¡¼¥Ð¤Ï¤½¤ì¤ò¼Â¹Ô¤·¤Þ¤¹¡£

+ +

¤â¤·¥Ç¥£¥ì¥¯¥È¥ê¤òÆɤó¤Ç¤¤¤ëºÝ¤Ë¡¢ + ʸ»ú¥»¥Ã¥È¡¢¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¡¢¸À¸ì¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ò + »ØÄꤹ¤ë¤¿¤á¤Î mod_mime + ¤Çǧ¼±¤Ç¤­¤ë³ÈÄ¥»Ò¤ò»ý¤¿¤Ê¤¤¥Õ¥¡¥¤¥ë¤¬¸«¤Ä¤«¤ë¤È¡¢·ë²Ì¤Ï + MultiViewsMatch + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀßÄê¤Ë°Í¸¤·¤Þ¤¹¡£¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥Ï¥ó¥É¥é¡¢¥Õ¥£¥ë¥¿¡¢Â¾¤Î¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¥¿¥¤¥×¤Î¤É¤ì¤¬ + MultiViews ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Ç»ÈÍѤǤ­¤ë¤«¤ò·èÄꤷ¤Þ¤¹¡£

+ +
top
+
+

¥Í¥´¥·¥¨¡¼¥·¥ç¥óÊýË¡

+ +

Apache ¤Ï¥ê¥½¡¼¥¹¤Î variant ¤Î°ìÍ÷¤ò¡¢¥¿¥¤¥×¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤« + ¥Ç¥£¥ì¥¯¥È¥êÆâ¤Î¥Õ¥¡¥¤¥ë̾¤«¤é¤«¤Ç¼èÆÀ¤·¤¿¸å¡¢ + ¡ÖºÇŬ¤Ê¡× variant ¤ò·èÄꤹ¤ë¤¿¤á¤ËÆó¤Ä¤ÎÊýË¡¤Î + ¤É¤Á¤é¤«¤òµ¯Æ°¤·¤Þ¤¹¡£ + Apache ¤Î¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Îµ¡Ç½¤ò»È¤¦¤¿¤á¤Ë¡¢ + ¤É¤Î¤è¤¦¤Ë¤·¤Æ¤³¤ÎÄ´Ä䤬¹Ô¤ï¤ì¤ë¤«¾ÜºÙ¤òÃΤëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£ + ¤·¤«¤·¤Ê¤¬¤é¡¢¤³¤Îʸ½ñ¤Î»Ä¤ê¤Ç¤Ï´Ø¿´¤Î¤¢¤ë¿Í¤Î¤¿¤á¤Ë¡¢ + »ÈÍѤµ¤ì¤Æ¤¤¤ëÊýË¡¤Ë¤Ä¤¤¤ÆÀâÌÀ¤·¤Æ¤¤¤Þ¤¹¡£

+ +

¥Í¥´¥·¥¨¡¼¥·¥ç¥óÊýË¡¤ÏÆó¤Ä¤¢¤ê¤Þ¤¹¡£

+ +
    +
  1. Ä̾ï¤Ï Apache ¤Î¥¢¥ë¥´¥ê¥º¥à¤òÍѤ¤¤¿ Server + driven negotiation ¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£Apache + ¤Î¥¢¥ë¥´¥ê¥º¥à¤Ï¸å¤Ë¾ÜºÙ¤ËÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¥¢¥ë¥´¥ê¥º¥à¤¬»ÈÍѤµ¤ì¤¿¾ì¹ç¡¢Apache + ¤Ï¤è¤êÎɤ¤·ë²Ì¤Ë¤Ê¤ë¤è¤¦¤Ë¡¢ÆÃÄê¤Î¼¡¸µ¤Ë¤ª¤¤¤ÆÉʼÁ¤ÎÃͤò + ¡ÖÊѤ¨¤ë¡×¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Apache + ¤¬ÉʼÁ¤ÎÃͤòÊѤ¨¤ëÊýË¡¤Ï¸å¤Ç¾ÜºÙ¤ËÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
    2. + +
  2. RFC 2295 + ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ëµ¡¹½¤òÍѤ¤¤Æ¥Ö¥é¥¦¥¶¤¬Æä˻ØÄꤷ¤¿¾ì¹ç¡¢ + transparent content negotiation + ¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£¤³¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥óÊýË¡¤Ç¤Ï¡¢¡ÖºÇŬ¤Ê¡× + variant ¤Î·èÄê¤ò¥Ö¥é¥¦¥¶¤¬´°Á´¤ËÀ©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢·ë²Ì¤Ï¥Ö¥é¥¦¥¶¤¬»ÈÍѤ·¤Æ¤¤¤ë¥¢¥ë¥´¥ê¥º¥à¤Ë°Í¸¤·¤Þ¤¹¡£ + Transparent negotiation ¤Î½èÍý¤Î²áÄø¤Ç¡¢¥Ö¥é¥¦¥¶¤Ï RFC 2296 + ¤Ç ÄêµÁ¤µ¤ì¤Æ¤¤¤ë 'remote variant selection algorithm' + ¤ò¼Â¹Ô¤¹¤ë¤è¤¦¤ËÍê¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
    3. +
+ +

¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î¼¡¸µ

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¼¡¸µÀâÌÀ
¥á¥Ç¥£¥¢¥¿¥¤¥×¥Ö¥é¥¦¥¶¤Ï Accept + ¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤ÇÍ¥Àè·¹¸þ¤ò»ØÄꤷ¤Þ¤¹¡£ + ¥¢¥¤¥Æ¥à¤½¤ì¤¾¤ì¤Ï¡¢´ØÏ¢¤·¤¿ÉʼÁ¿ôÃͤò»ý¤Ä¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + variant ¤ÎÀâÌÀ¤âÉʼÁ¿ôÃͤò»ý¤Ä¤³¤È¤¬¤Ç¤­¤Þ¤¹ + ("qs" ¥Ñ¥é¥á¡¼¥¿¤ò¤´Í÷²¼¤µ¤¤)¡£
¸À¸ì¥Ö¥é¥¦¥¶¤Ï Accept-Language + ¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤ÇÍ¥Àè·¹¸þ¤ò»ØÄꤷ¤Þ¤¹¡£ + Í×ÁǤ½¤ì¤¾¤ì¤ËÉʼÁ¿ôÃͤò»ý¤¿¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + variants ¤Ï 0 ¤« 1 ¤Ä¤«¤½¤ì°Ê¾å¤Î¸À¸ì¤È + ´ØÏ¢¤Å¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¥Ö¥é¥¦¥¶¤Ï Accept-Encoding + ¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤ÇÍ¥Àè·¹¸þ¤ò»ØÄꤷ¤Þ¤¹¡£ + Í×ÁǤ½¤ì¤¾¤ì¤ËÉʼÁ¿ôÃͤò»ý¤¿¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
ʸ»ú¥»¥Ã¥È¥Ö¥é¥¦¥¶¤Ï Accept-Charset + ¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤ÇÍ¥Àè·¹¸þ¤ò»ØÄꤷ¤Þ¤¹¡£ + Í×ÁǤ½¤ì¤¾¤ì¤ËÉʼÁ¿ôÃͤò»ý¤¿¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + variant ¤Ï¥á¥Ç¥£¥¢¥¿¥¤¥×¤Î¥Ñ¥é¥á¡¼¥¿¤È¤·¤Æʸ»ú¥»¥Ã¥È¤ò + »ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
+ + +

Apache ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¥¢¥ë¥´¥ê¥º¥à

+ +

¥Ö¥é¥¦¥¶¤ËÊÖ¤¹¡ÖºÇŬ¤Ê¡×variant ¤ò (¤â¤·¤¢¤ì¤Ð) ÁªÂò¤¹¤ë¤è¤¦¤Ë + Apache ¤Ï¼¡¤Î¥¢¥ë¥´¥ê¥º¥à¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¥¢¥ë¥´¥ê¥º¥à¤òÀßÄê¤Ë¤è¤êÊѹ¹¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ + ¼¡¤Î¤è¤¦¤ËÆ°ºî¤·¤Þ¤¹:

+ +
    +
  1. ¤Þ¤º¤Ï¤¸¤á¤Ë¡¢¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î¼¡¸µ¤½¤ì¤¾¤ì¤Ë¤Ä¤¤¤ÆŬÀÚ¤Ê + Accept* ¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤òÄ´¤Ù¡¢ + variant ¤½¤ì¤¾¤ì¤ËÉʼÁ¤ò³ä¤êÅö¤Æ¤Þ¤¹¡£ + ¤â¤·¤¢¤ë¼¡¸µ¤Î Accept* ¥Ø¥Ã¥À¤Ç¤½¤Î variant + ¤¬µöÍƤǤ­¤Ê¤¤¤³¤È¤¬¼¨¤µ¤ì¤Æ¤¤¤ì¤Ð¡¢¤½¤ì¤òºï½ü¤·¤Þ¤¹¡£ + variant ¤¬°ì¤Ä¤â»Ä¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢¥¹¥Æ¥Ã¥× 4 ¤Ë¹Ô¤­¤Þ¤¹¡£
    2. + +
  2. + ¾ÃµîË¡¤Ç¡ÖºÇŬ¤Ê¡× variant ¤òÁª¤Ó¤Þ¤¹¡£ + ¼¡¤Î¥Æ¥¹¥È¤¬½çÈÖ¤ËŬÍѤµ¤ì¤Þ¤¹¡£ + ¥Æ¥¹¥È¤ÇÁªÂò¤µ¤ì¤Ê¤«¤Ã¤¿ variant ¤Ïºï½ü¤µ¤ì¤Æ¤¤¤­¤Þ¤¹¡£ + ¥Æ¥¹¥È¸å variant ¤¬°ì¤Ä¤À¤±»Ä¤Ã¤Æ¤¤¤ì¤Ð¡¢¤½¤ì¤òºÇŬ¤Ê¤â¤Î¤È¤·¤Æ + ¥¹¥Æ¥Ã¥× 3 ¤Ë¿Ê¤ß¤Þ¤¹¡£ + Ê£¿ô variant ¤¬»Ä¤Ã¤Æ¤¤¤ì¤Ð¡¢¼¡¤Î¥Æ¥¹¥È¤Ë¿Ê¤ß¤Þ¤¹¡£ + +
      +
    1. variant ¤Î¥á¥Ç¥£¥¢¥¿¥¤¥×¤ÎÉʼÁ¿ôÃÍ¤È Accept + ¥Ø¥Ã¥À¤ÎÉʼÁ¿ôÃͤȤÎÀѤò·×»»¤·¤Æ¡¢ºÇ¹âÃͤΠvariant + ¤òÁª¤Ó¤Þ¤¹¡£
      2. + +
    2. ¸À¸ìÉʼÁ¿ôÃͤ¬ºÇ¹â¤Î variant ¤òÁª¤Ó¤Þ¤¹¡£
      3. + +
    3. (¤â¤·¤¢¤ì¤Ð) Accept-Language ¥Ø¥Ã¥À¤Î¸À¸ì½ç¤«¡¢ + (¤â¤·¤¢¤ì¤Ð) + LanguagePriority + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¸À¸ì½ç¤ÇºÇŬ¤Ê¸À¸ì¤Î variant ¤òÁª¤Ó¤Þ¤¹¡£
      4. + +
    4. ºÇ¹â¡Ö¥ì¥Ù¥ë¡×¤Î¥á¥Ç¥£¥¢¥Ñ¥é¥á¡¼¥¿ + (text/html ¥á¥Ç¥£¥¢¥¿¥¤¥×¤Î¥Ð¡¼¥¸¥ç¥ó¤òÍ¿¤¨¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹) + ¤ò»ý¤Ä variant ¤òÁª¤Ó¤Þ¤¹¡£
      5. + +
    5. Accept-Charset ¥Ø¥Ã¥À¹Ô¤ÇÍ¿¤¨¤é¤ì¤Æ¤¤¤ëºÇ¹â¤Îʸ»ú¥»¥Ã¥È + ¥á¥Ç¥£¥¢¥Ñ¥é¥á¡¼¥¿¤ò»ý¤Ä variant ¤òÁª¤Ó¤Þ¤¹¡£ + ÌÀ¼¨Åª¤Ë½ü³°¤µ¤ì¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢ISO-8859-1 + ¤¬µöÍƤµ¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + text/* ¥á¥Ç¥£¥¢¥¿¥¤¥×¤Ç¤¢¤ë¤±¤ì¤É¤â + ÆÃÄê¤Îʸ»ú¥»¥Ã¥È¤ËÌÀ¼¨Åª¤Ë´ØÏ¢¤Å¤±¤é¤ì¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤ + variant ¤Ï ISO-8859-1 ¤Ç¤¢¤ë¤È²¾Äꤵ¤ì¤Þ¤¹¡£
      6. + +
    6. ISO-8859-1 ¤Ç¤Ï¤Ê¤¤Ê¸»ú¥»¥Ã¥È¥á¥Ç¥£¥¢¥Ñ¥é¥á¡¼¥¿¤È + ´ØÏ¢¤Å¤±¤é¤ì¤Æ¤¤¤ë variant ¤òÁª¤Ó¤Þ¤¹¡£ + ¤½¤Î¤è¤¦¤Ê variant ¤¬¤Ê¤¤¾ì¹ç¤Ï¡¢Âå¤ï¤ê¤ËÁ´¤Æ¤Î + variant ¤òÁª¤Ó¤Þ¤¹¡£
      7. + +
    7. ºÇŬ¤Ê¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Î variant ¤òÁª¤Ó¤Þ¤¹¡£ + ¤â¤· user-agent ¤¬µöÍƤ¹¤ë¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤¬¤¢¤ì¤Ð¡¢ + ¤½¤Î variant ¤Î¤ß¤òÁª¤Ó¤Þ¤¹¡£ + ¤½¤¦¤Ç¤Ï¤Ê¤¯¡¢¤â¤·¥¨¥ó¥³¡¼¥É¤µ¤ì¤¿¤â¤Î¤È¤½¤¦¤Ç¤Ê¤¤ + variant ¤¬º®¤¶¤Ã¤Æ¸ºß¤·¤Æ¤¤¤¿¤é¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤Ê¤¤ + variant ¤Î¤ß¤òÁª¤Ó¤Þ¤¹¡£ + variant ¤¬Á´Éô¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë¤« + variant ¤¬Á´Éô¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤Ê¤¤¤È¤¤¤¦¾ì¹ç¤Ï¡¢ + Á´¤Æ¤Î variant ¤òÁª¤Ó¤Þ¤¹¡£
      8. + +
    8. ÆâÍƤκǤâû¤¤ variant ¤òÁª¤Ó¤Þ¤¹¡£
      9. + +
    9. »Ä¤Ã¤Æ¤¤¤ë variant ¤ÎºÇ½é¤Î¤â¤Î¤òÁª¤Ó¤Þ¤¹¡£ + ¥¿¥¤¥×¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤ÎºÇ½é¤Ë¥ê¥¹¥È¤µ¤ì¤Æ¤¤¤ë¤«¡¢ + variant ¤¬¥Ç¥£¥ì¥¯¥È¥ê¤«¤éºÇ½é¤ËÆɤ߹þ¤Þ¤ì¤ë»þ¤Ë + ASCII½ç¤Ç¥½¡¼¥È¤·¤Æ¥Õ¥¡¥¤¥ë̾¤¬ÀèƬ¤Ë¤Ê¤Ã¤¿¤«¡¢¤Î¤É¤Á¤é¤«¤Ç¤¹¡£
      10. +
    +
    3. + +
  3. ¥¢¥ë¥´¥ê¥º¥à¤ò»È¤Ã¤Æ°ì¤Ä¤Î¡ÖºÇŬ¤Ê¡×variant ¤òÁª¤Ó¤Þ¤·¤¿¤Î¤Ç¡¢ + ¤½¤ì¤ò±þÅú¤È¤·¤ÆÊÖ¤·¤Þ¤¹¡£¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î¼¡¸µ¤ò»ØÄꤹ¤ë¤¿¤á¤Ë + HTTP ¥ì¥¹¥Ý¥ó¥¹¥Ø¥Ã¥À Vary ¤¬ÀßÄꤵ¤ì¤Þ¤¹ + (¥ê¥½¡¼¥¹¤Î¥­¥ã¥Ã¥·¥å¤ò¤¹¤ë»þ¤Ë¡¢ + ¥Ö¥é¥¦¥¶¤ä¥­¥ã¥Ã¥·¥å¤Ï¤³¤Î¾ðÊó¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹)¡£ + °Ê¾å¤Ç½ª¤ï¤ê¡£
    4. + +
  4. ¤³¤³¤ËÍ褿¤È¤¤¤¦¤³¤È¤Ï¡¢variant ¤¬°ì¤Ä¤âÁªÂò¤µ¤ì¤Ê¤«¤Ã¤¿ + (¥Ö¥é¥¦¥¶¤¬µöÍƤ¹¤ë¤â¤Î¤¬¤Ê¤«¤Ã¤¿¤¿¤á) ¤È¤¤¤¦¤³¤È¤Ç¤¹¡£ + 406 ¥¹¥Æ¡¼¥¿¥¹ ("No Acceptable representation" ¤ò°ÕÌ£¤¹¤ë) + ¤¬¡¢ÍøÍѲÄǽ¤Ê variant ¤Î¥ê¥¹¥È¤Î¤Ä¤¤¤¿ HTML + ¥É¥­¥å¥á¥ó¥È¤È¤È¤â¤ËÊÖ¤µ¤ì¤Þ¤¹¡£ + Áê°ã¤Î¼¡¸µ¤ò¼¨¤¹ HTTP Vary ¥Ø¥Ã¥À¤âÀßÄꤵ¤ì¤Þ¤¹¡£
    5. +
+ +
top
+
+

ÉʼÁ¤ÎÃͤòÊѤ¨¤ë

+ +

¾åµ­¤Î Apache ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¥¢¥ë¥´¥ê¥º¥à¤Î¸·³Ê¤Ê²ò¼á¤Ç + ÆÀ¤é¤ì¤ë¤Ç¤¢¤í¤¦Ãͤ«¤é¡¢Apache ¤ÏÉʼÁ¿ôÃͤò»þ¡¹ÊѤ¨¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¤³¤Î¥¢¥ë¥´¥ê¥º¥à¤Ç´°Á´¤Ç¤Ï¤Ê¤¤¡¢¤¢¤ë¤¤¤ÏÀµ³Î¤Ç¤Ê¤¤¾ðÊó¤òÁ÷¤ë + ¥Ö¥é¥¦¥¶¸þ¤±¤Ë¤è¤ê¤è¤¤·ë²Ì¤òÆÀ¤ë¤¿¤á¤Ë¹Ô¤ï¤ì¤Þ¤¹¡£ + ¤«¤Ê¤ê¥Ý¥Ô¥å¥é¡¼¤Ê¥Ö¥é¥¦¥¶¤Ç¡¢¤â¤·¤Ê¤¤¤È´Ö°ã¤Ã¤¿ variant + ¤òÁªÂò¤¹¤ë·ë²Ì¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¦¤è¤¦¤Ê Accept + ¥Ø¥Ã¥À¾ðÊó¤òÁ÷¤ë¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£ + ¥Ö¥é¥¦¥¶¤¬´°Á´¤ÇÀµ¤·¤¤¾ðÊó¤òÁ÷¤Ã¤Æ¤¤¤ì¤Ð¡¢ + ¤³¤Î¿ôÃÍÊѲ½¤ÏŬÍѤµ¤ì¤Þ¤»¤ó¡£

+ +

¥á¥Ç¥£¥¢¥¿¥¤¥×¤È¥ï¥¤¥ë¥É¥«¡¼¥É

+ +

Accept: ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Ï¥á¥Ç¥£¥¢¥¿¥¤¥×¤ÎÍ¥Àè·¹¸þ¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤³¤ì¤Ï¤Þ¤¿¡¢"image/*" ¤ä "*/*" + ¤È¤¤¤Ã¤¿¡Ö¥ï¥¤¥ë¥É¥«¡¼¥É¡×¥á¥Ç¥£¥¢¥¿¥¤¥×¤ò´Þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤³¤Ç * ¤ÏǤ°Õ¤Îʸ»úÎó¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢¼¡¤Î:

+ +

Accept: image/*, */*

+ +

¤ò´Þ¤à¥ê¥¯¥¨¥¹¥È¤Ï¡¢"image/" ¤Ç¤Ï¤¸¤Þ¤ë¥¿¥¤¥×Á´¤Æ¤¬µöÍƤǤ­¤ë¡¢ + ¤½¤·¤Æ¾¤Î¤É¤ó¤Ê¥¿¥¤¥×¤âµöÍƤǤ­¤ë + (¤³¤Î¾ì¹ç¤Ï¤¸¤á¤Î "image/*" ¤Ï¾éĹ¤Ë¤Ê¤ê¤Þ¤¹) + ¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ + °·¤¦¤³¤È¤Î¤Ç¤­¤ëÌÀ¼¨Åª¤Ê¥¿¥¤¥×¤Ë²Ã¤¨¤Æ¡¢µ¡³£Åª¤Ë + ¥ï¥¤¥ë¥É¥«¡¼¥É¤òÁ÷¤ë¥Ö¥é¥¦¥¶¤â¤¢¤ê¤Þ¤¹¡£Î㤨¤Ð:

+ +

+ Accept: text/html, text/plain, image/gif, image/jpeg, */* +

+

¤³¤¦¤¹¤ë¤³¤È¤ÎÁÀ¤¤¤Ï¡¢ÌÀ¼¨Åª¤Ë¥ê¥¹¥È¤·¤Æ¤¤¤ë¥¿¥¤¥×¤¬Í¥À褵¤ì¤ë¤±¤ì¤É¤â¡¢ + °Û¤Ê¤ëɽ¸½¤¬ÍøÍѲÄǽ¤Ç¤¢¤ì¤Ð¤½¤ì¤Ç¤âÎɤ¤¡¢¤È¤¤¤¦¤³¤È¤Ç¤¹¡£ + ¤·¤«¤·¤Ê¤¬¤é¡¢¾å¤Î´ðËÜŪ¤Ê¥¢¥ë¥´¥ê¥º¥à¤Ç¤Ï¡¢ + */* ¥ï¥¤¥ë¥É¥«¡¼¥É¤Ï¾¤ÎÁ´¤Æ¤Î¥¿¥¤¥×¤ÈÁ´¤¯Æ±Åù¤Ê¤Î¤ÇÍ¥À褵¤ì¤Þ¤»¤ó¡£ + ¥Ö¥é¥¦¥¶¤Ï */* ¤Ë¤â¤Ã¤ÈÄ㤤ÉʼÁ (Í¥Àè) + ÃͤòÉÕ¤±¤Æ¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ë¤Ù¤­¤Ê¤Î¤Ç¤¹¡£Î㤨¤Ð:

+

+ Accept: text/html, text/plain, image/gif, image/jpeg, */*; q=0.01 +

+

ÌÀ¼¨Åª¤Ê¥¿¥¤¥×¤Ë¤ÏÉʼÁ¿ôÃͤ¬ÉÕ¤±¤é¤ì¤Æ¤¤¤Þ¤»¤ó¤Î¤Ç¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Î 1.0 (ºÇ¹âÃÍ) ¤ÎÍ¥Àè¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¥ï¥¤¥ë¥É¥«¡¼¥É */* ¤ÏÄ㤤ͥÀèÅÙ 0.01 ¤òÍ¿¤¨¤é¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢ + ÌÀ¼¨Åª¤Ë¥ê¥¹¥È¤µ¤ì¤Æ¤¤¤ë¥¿¥¤¥×¤Ë¹çÃפ¹¤ë variant ¤¬¤Ê¤¤¾ì¹ç¤Ë¤Î¤ß¡¢ + ¾¤Î¥¿¥¤¥×¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£

+ +

¤â¤· Accept: ¥Ø¥Ã¥À¤¬ q ÃͤòÁ´¤¯´Þ¤ó¤Ç¤¤¤Ê¤±¤ì¤Ð¡¢ + ˾¤ß¤ÎµóÆ°¤ò¤¹¤ë¤¿¤á¤Ë¡¢ + Apache ¤Ï "*/*" ¤¬¤¢¤ì¤Ð 0.01 ¤Î q ÃͤòÀßÄꤷ¤Þ¤¹¡£ + ¤Þ¤¿¡¢"type/*" ¤Î·Á¤Î¥ï¥¤¥ë¥É¥«¡¼¥É¤Ë¤Ï 0.02 ¤Î q ÃͤòÀßÄꤷ¤Þ¤¹ + (¤Ç¤¹¤«¤é¤³¤ì¤é¤Ï "*/*" ¤Î¥Þ¥Ã¥Á¤è¤ê¤âÍ¥À褵¤ì¤Þ¤¹)¡£ + ¤â¤· Accept: ¥Ø¥Ã¥ÀÃæ¤Î¥á¥Ç¥£¥¢¥¿¥¤¥×¤Î¤É¤ì¤«¤¬ q + Ãͤò´Þ¤ó¤Ç¤¤¤ì¤Ð¡¢¤³¤ì¤é¤ÎÆüì¤ÊÃͤÏŬ±þ¤µ¤ì¤º¡¢ + Àµ¤·¤¤¾ðÊó¤òÁ÷¤ë¥Ö¥é¥¦¥¶¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤Ï´üÂÔÄ̤ê¤Ë + Æ°ºî¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ + +

¸À¸ì¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ÎÎã³°½èÍý

+ +

Apache 2.0 ¤Ç¤Ï¿·¤¿¤Ë¡¢¸À¸ì¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤¬Å¬¹ç¤¹¤ë¤â¤Î¤ò + ¸«¤Ä¤±¤ë¤Î¤Ë¼ºÇÔ¤·¤¿»þ¤Ë¡¢Í¥²í¤Ë¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¤Ç¤­¤ë¤è¤¦¤Ê + ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¥¢¥ë¥´¥ê¥º¥à¤¬´ö¤Ä¤«Äɲ䵤ì¤Þ¤·¤¿¡£

+ +

¥µ¡¼¥Ð¤Î¥Ú¡¼¥¸¤ò¥¯¥é¥¤¥¢¥ó¥È¤¬¥ê¥¯¥¨¥¹¥È¤·¤¿¤±¤ì¤É¤â¡¢ + ¥Ö¥é¥¦¥¶¤ÎÁ÷¤Ã¤Æ¤­¤¿ Accept-Language ¤Ë¹çÃפ¹¤ë¥Ú¡¼¥¸¤¬°ì¤Ä¤â + ¸«¤Ä¤«¤é¤Ê¤«¤Ã¤¿¾ì¹ç¤Ë¡¢¥µ¡¼¥Ð¤Ï "No Acceptable Variant" + ¤« "Multiple Choices" ¥ì¥¹¥Ý¥ó¥¹¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤·¤Þ¤¹¡£ + ¤³¤ì¤é¤Î¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤òÊÖ¤µ¤Ê¤¤¤è¤¦¤Ë¡¢ + ¤³¤Î¤è¤¦¤Ê¾ì¹ç¤Ë¤Ï Apache ¤¬ Accept-Language ¤ò̵»ë¤·¤Æ¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ËÌÀ¼¨Åª¤Ë¤Ï¹çÃפ·¤Ê¤¤¥É¥­¥å¥á¥ó¥È¤ò + Ä󶡤¹¤ë¤è¤¦¤ËÀßÄê¤Ç¤­¤Þ¤¹¡£ + ForceLanguagePriority + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¤³¤ì¤é¤Î¥¨¥é¡¼¤Î°ì¤Ä¤«Î¾Êý¤ò¥ª¡¼¥Ð¡¼¥é¥¤¥É¤¹¤ë¤¿¤á¤Ë + »ÈÍѤǤ­¤Æ¡¢ + LanguagePriority + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÆâÍƤò»È¤Ã¤Æ¥µ¡¼¥Ð¤ÎȽÃǤòÂå¹Ô¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£

+ +

¥µ¡¼¥Ð¤Ï¾¤ËŬ¹ç¤¹¤ë¤â¤Î¤¬¸«¤Ä¤«¤é¤Ê¤±¤ì¤Ð¡¢ + ¸À¸ì¥µ¥Ö¥»¥Ã¥È¤ÇŬ¹ç¤¹¤ë¤â¤Î¤ò»î¤½¤¦¤È¤â¤·¤Þ¤¹¡£ + Î㤨¤Ð¥¯¥é¥¤¥¢¥ó¥È¤¬±Ñ¹ñ±Ñ¸ì¤Ç¤¢¤ë en-GB ¸À¸ì¤Ç + ¥É¥­¥å¥á¥ó¥È¤ò¥ê¥¯¥¨¥¹¥È¤·¤¿¾ì¹ç¡¢¥µ¡¼¥Ð¤Ï HTTP/1.1 + µ¬³Ê¤Ç¤Ï¡¢Ã±¤Ë en ¤È¥Þ¡¼¥¯¤µ¤ì¤Æ¤¤¤ë¥É¥­¥å¥á¥ó¥È¤ò + ¥Þ¥Ã¥Á¤¹¤ë¤â¤Î¤È¤¹¤ë¤³¤È¤ÏÄ̾ï¤Ïµö¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£ + (±Ñ¹ñ±Ñ¸ì¤ÏÍý²ò¤Ç¤­¤ë¤±¤É°ìÈÌŪ¤Ê±Ñ¸ì¤ÏÍý²ò¤Ç¤­¤Ê¤¤¤È¤¤¤¦Æɤ߼ê¤Ï + ¹Í¤¨¤é¤ì¤Ê¤¤¤Î¤Ç¡¢Accept-Language ¥Ø¥Ã¥À¤Ç en-GB + ¤ò´Þ¤ó¤Ç en ¤ò´Þ¤Þ¤Ê¤¤¤Î¤Ï¤Û¤Ü³Î¼Â¤ËÀßÄê¤Î´Ö°ã¤¤¤Ç¤¢¤ë¡¢ + ¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤Ç¤¹¤¬ÉÔ¹¬¤Ê¤³¤È¤Ë¡¢Â¿¤¯¤Î¥¯¥é¥¤¥¢¥ó¥È¤Ç¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç + ¤³¤Î¤è¤¦¤ÊÀßÄê¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£) + ¤·¤«¤·¤Ê¤¬¤é¡¢Â¾¤Î¸À¸ì¤Ë¤Ï¥Þ¥Ã¥Á¤»¤º¡¢"No Acceptable Variants" + ¥¨¥é¡¼¤òÊÖ¤·¤¿¤ê¡¢ + LanguagePriority + ¤Ë¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤È¤­¤Ï¡¢ + ¥µ¥Ö¥»¥Ã¥È»ØÄê¤ò̵»ë¤·¤Æ¡¢en-GB ¤ò en + ¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + Apache ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ÎµöÍƸÀ¸ì¥ê¥¹¥È¤Ë°ÅÌÛ¤Ë + Èó¾ï¤ËÄ㤤ÉʼÁÃͤοƸÀ¸ì¤ò²Ã¤¨¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤·¤«¤·¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬ "en-GB; q=0.9, fr; q=0.8" ¤È¥ê¥¯¥¨¥¹¥È¤·¤Æ¡¢ + ¥µ¡¼¥Ð¤¬ "en" ¤È "fr" ¤ÈÀ߷פµ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + "fr" ¥É¥­¥å¥á¥ó¥È¤¬ÊÖ¤µ¤ì¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤Î¤è¤¦¤Ê½èÍý¤Ï¡¢HTTP 1.1 µ¬³Ê¤È¤ÎÀ°¹çÀ­¤ò°Ý»ý¤·¤Æ¡¢ + ŬÀÚ¤ËÀßÄꤵ¤ì¤¿¥¯¥é¥¤¥¢¥ó¥È¤È¤â¤­¤Á¤ó¤ÈÆ°ºî¤¹¤ë¤¿¤á¤Ë + ɬÍפǤ¹¡£

+ +

¤è¤ê¹âÅ٤ʥƥ¯¥Ë¥Ã¥¯ (Cookie ¤äÆüì¤Ê URL ¥Ñ¥¹Åù) + ¤Ë¤ª¤¤¤Æ¤â¥æ¡¼¥¶¤Î¸À¸ìÁªÂò¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤¿¤á¡¢ + Apache 2.0.47 ¤«¤é¤Ï¡¢mod_negotiation + ¤¬´Ä¶­ÊÑ¿ô prefer-language + ¤òǧ¼±¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + ¤³¤ÎÊÑ¿ô¤¬Â¸ºß¤·¤Æ¡¢Å¬ÀڤʸÀ¸ì¥¿¥°¤¬ÂåÆþ¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + mod_negotiation ¤Ï¹çÃפ¹¤ë variant + ¤òÁªÂò¤·¤è¤¦¤È¤·¤Þ¤¹¡£¹çÃפ¹¤ë¤â¤Î¤¬Ìµ¤±¤ì¤Ð¡¢ + Ä̾ï¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¼ê½ç¤¬Å¬ÍѤµ¤ì¤Þ¤¹¡£

+ +

Example

+ SetEnvIf Cookie "language=(.+)" prefer-language=$1 +

+ +
top
+
+

Transparent Content Negotiation +¤Î³ÈÄ¥

+ +

Apache ¤Ï transparent content negotiation ¥×¥í¥È¥³¥ë +(RFC 2295) ¤ò¼¡¤Î¤è¤¦¤Ë³ÈÄ¥¤·¤Æ¤¤¤Þ¤¹¡£ +ÆÃÄê¤Î¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Î¤ß¤¬ÍøÍѲÄǽ¤Ç¤¢¤ë variant +¤Ë°õ¤òÉÕ¤±¤ë¤¿¤á¤Ë¡¢¿·¤¿¤Ë {encoding ..} +Í×ÁǤò variant ¥ê¥¹¥ÈÃæ¤Ë»È¤Ã¤Æ¤¤¤Þ¤¹¡£ +¥ê¥¹¥ÈÃæ¤Î¥¨¥ó¥³¡¼¥É¤µ¤ì¤¿ variant ¤òǧ¼±¤·¡¢ +Accept-Encoding ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Ë½¾¤Ã¤ÆµöÍƤµ¤ì¤ë +¥¨¥ó¥³¡¼¥É¤ò¤â¤Ã¤¿ variant ¤Ï¡¢¤É¤ì¤Ç¤â¸õÊä variant +¤È¤·¤Æ»ÈÍѤ¹¤ë¤è¤¦¤Ë¡¢ +RVSA/1.0 ¥¢¥ë¥´¥ê¥º¥à (RFC 2296) ¤Î¼ÂÁõ¤¬³ÈÄ¥¤µ¤ì¤Þ¤·¤¿¡£ +RVSA/1.0 ¤Î¼ÂÁõ¤Ç¤Ï¡¢ºÇŬ¤Ê variant ¤¬¸«¤Ä¤«¤ë¤Þ¤Ç¡¢ +·×»»¤·¤¿ÉʼÁ¿ôÃͤϾ®¿ôÅÀ°Ê²¼ 5 ·å¤Þ¤Ç´Ý¤á¤Þ¤»¤ó¡£

+
top
+
+

¥ê¥ó¥¯¤È̾Á°¤ÎÊÑ´¹¤Ë´Ø¤¹¤ëÃí°ÕÅÀ

+ +

¸À¸ì¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥Õ¥¡¥¤¥ë¤¬°ì¤Ä°Ê¾å¤Î³ÈÄ¥»Ò¤ò»ý¤Æ¤Æ¡¢ + ³ÈÄ¥»Ò¤Î½çÈÖ¤ÏÄ̾ï¤Ï¹Í褵¤ì¤Ê¤¤ + (¾ÜºÙ¤Ï mod_mime + ¤ò»²¾È) ¤Î¤Ç¡¢ + ´ö¤Ä¤«¤Î°Û¤Ê¤ë̾Á°¤ÎÊÑ´¹¤òÁª¤Ù¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

ŵ·¿Åª¤Ê¥Õ¥¡¥¤¥ë¤Ç¤Ï¡¢MIME ¥¿¥¤¥×³ÈÄ¥»Ò (Î㤨¤Ð + html) ¤ò»ý¤Ã¤Æ¤¤¤Æ¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°³ÈÄ¥»Ò + (Î㤨¤Ð gz) ¤ò»ý¤Ã¤Æ¤¤¤ë¤«¤â¤·¤ì¤Ê¤¯¤Æ¡¢ + ¤³¤Î¥Õ¥¡¥¤¥ë¤Ë°Û¤Ê¤ë¸À¸ì variant ¤òÍÑ°Õ¤·¤Æ¤¤¤ì¤Ð¡¢ + ¤â¤Á¤í¤ó¸À¸ì³ÈÄ¥»Ò (Î㤨¤Ð en) + ¤ò»ý¤Ã¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£

+ +

Îã:

+ +
    +
  • foo.en.html
    • + +
  • foo.html.en
    • + +
  • foo.en.html.gz
    • +
+ +

¥Õ¥¡¥¤¥ë̾¤È¡¢¤½¤ì¤ËÂФ·¤Æ»È¤¨¤ë¥ê¥ó¥¯¤È»È¤¨¤Ê¤¤¥ê¥ó¥¯¤ÎÎã¤Ç¤¹:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¥Õ¥¡¥¤¥ë̾»È¤¨¤ë¥ê¥ó¥¯»È¤¨¤Ê¤¤¥ê¥ó¥¯
foo.html.enfoo
+ foo.html		-
foo.en.htmlfoofoo.html
foo.html.en.gzfoo
+ foo.html		foo.gz
+ foo.html.gz
foo.en.html.gzfoofoo.html
+ foo.html.gz
+ foo.gz
foo.gz.html.enfoo
+ foo.gz
+ foo.gz.html		foo.html
foo.html.gz.enfoo
+ foo.html
+ foo.html.gz		foo.gz
+ +

¾å¤Îɽ¤ò¸«¤Æ¡¢³ÈÄ¥»Ò¤Ê¤·¤Î¥ê¥ó¥¯ (Î㤨¤Ð foo) + ¤¬¤¤¤Ä¤Ç¤â»È¤¨¤ë¤³¤È¤Ëµ¤¤¬ÉÕ¤¯¤Ç¤·¤ç¤¦¡£ + ¤³¤ÎÍøÅÀ¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤È¤·¤Æ±þÅú¤¹¤ë¥Õ¥¡¥¤¥ë¤Î + ¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤ò±£Ê䷤ơ¢¥ê¥ó¥¯¤Î»²¾È¤òÊѹ¹¤¹¤ë¤³¤È¤Ê¤¯ + ¸å¤«¤é¥Õ¥¡¥¤¥ë¤òÊѹ¹¤Ç¤­¤ë¡¢ + Î㤨¤Ð html ¤«¤é shtml + ¤Ë¡¢¤¢¤ë¤¤¤Ï cgi ¤ËÊѹ¹¤Ç¤­¤ëÅÀ¤Ç¤¹¡£

+ +

¥ê¥ó¥¯¤Ë MIME ¥¿¥¤¥×¤ò»È¤¤Â³¤±¤¿¤¤ (Î㤨¤Ð + foo.html)»þ¤Ï¡¢¸À¸ì³ÈÄ¥»Ò¤Ï + (¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°³ÈÄ¥»Ò¤â¤¢¤ì¤Ð¤½¤ì¤â´Þ¤á¤Æ) + MIME ¥¿¥¤¥×³ÈÄ¥»Ò¤Î±¦Â¦¤Ë¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó + (Î㤨¤Ð foo.html.en)¡£

+
top
+
+

¥­¥ã¥Ã¥·¥å¤Ë´Ø¤¹¤ëÃí°Õ»ö¹à

+ +

¥­¥ã¥Ã¥·¥å¤¬°ì¤Ä¤Îɽ¸½¤òÊݸ¤·¤Æ¤¤¤ë¤È¤­¤Ï¡¢ + ¥ê¥¯¥¨¥¹¥È URL ¤È´ØÏ¢¤Å¤±¤é¤ì¤Æ¤¤¤Þ¤¹¡£ + ¼¡¤Ë¤½¤Î URL ¤¬¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿»þ¤Ë¡¢¥­¥ã¥Ã¥·¥å¤Ï + Êݸ¤µ¤ì¤Æ¤¤¤ëɽ¸½¤ò»ÈÍѤǤ­¤Þ¤¹¡£¤·¤«¤·¡¢ + ¥ê¥½¡¼¥¹¤¬¥µ¡¼¥Ð¤Ç¥Í¥´¥·¥¨¡¼¥·¥ç¥ó²Äǽ¤Ç¤¢¤ì¤Ð¡¢ + ºÇ½é¤Î¥ê¥¯¥¨¥¹¥È¤Ç¥­¥ã¥Ã¥·¥å¤µ¤ì¤Æ³¤¯¥­¥ã¥Ã¥·¥å¥Ò¥Ã¥È¤Ç¤Ï + ´Ö°ã¤Ã¤¿±þÅú¤òÊÖ¤·¤Æ¤·¤Þ¤¦¤È¤¤¤¦¤³¤È¤Ë¤Ê¤ê¤«¤Í¤Þ¤»¤ó¡£ + ¤³¤ì¤òËɤ°¤¿¤á¤Ë¡¢Apache ¤Ï¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î + ¸å¤ËÊÖ¤µ¤ì¤¿±þÅúÁ´¤Æ¤Ë¡¢HTTP/1.0 ¥¯¥é¥¤¥¢¥ó¥È¤Ç¤Ï + ¥­¥ã¥Ã¥·¥åÉÔ²Äǽ¤Î°õ¤ò¤Ä¤±¤Þ¤¹¡£ + ¤Þ¤¿¡¢¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤µ¤ì¤¿±þÅú¤Î¥­¥ã¥Ã¥·¥å¤ò²Äǽ¤Ë¤¹¤ë + HTTP/1.1 ¥×¥í¥È¥³¥ë¤Îµ¡Ç½¤â Apache ¤Ï¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£

+ +

HTTP/1.0 ½àµò¤Î¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¤Ï¡¢ + (¥Ö¥é¥¦¥¶¤Ç¤¢¤í¤¦¤È¥­¥ã¥Ã¥·¥å¤Ç¤¢¤í¤¦¤È) + ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò¼õ¤±¤¿±þÅú¤Î¥­¥ã¥Ã¥·¥å¤òµö¤¹¤¿¤á¤Ë¡¢ + CacheNegotiatedDocs + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤǤ­¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤ä¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¡¢ + °ú¿ô¤ò¤È¤ê¤Þ¤»¤ó¡£ + HTTP/1.1 ¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤Ë¤Ï¸úÎϤò»ý¤Á¤Þ¤»¤ó¡£

+ +

HTTP/1.1 ¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ·¤Æ¤Ï¡¢¥ì¥¹¥Ý¥ó¥¹¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¼¡¸µ + ¤ò¼¨¤¹¤¿¤á¤Ë Vary HTTP ¥ì¥¹¥Ý¥ó¥¹¥Ø¥Ã¥À¤òÁ÷¤ê¤Þ¤¹¡£ + ¥­¥ã¥Ã¥·¥å¤Ï¡¢¤³¤ì¤ò»È¤Ã¤Æ¸å³¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¥í¡¼¥«¥ë¥³¥Ô¡¼¤Ç±þÅú¤Ç¤­¤ë¤« + ¤É¤¦¤«¤ò·èÄê¤Ç¤­¤Þ¤¹¡£ + ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¼¡¸µ¤È¤Ï´Ø·¸¤Ê¤·¤Ë¥í¡¼¥«¥ë¥³¥Ô¡¼¤Î»ÈÍѤòÍ¥À褹¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢ + force-no-vary ´Ä¶­ÊÑ¿ô¤ò + ÀßÄꤷ¤Þ¤¹¡£

+ +
top
+
+

ÄɲþðÊó

+ +

¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Ë´Ø¤¹¤ëÄɲþðÊó¤Ï¡¢ + Alan J. Flavell ¤µ¤ó¤ÎLanguage + Negotiation Notes ¤ò¤´Í÷²¼¤µ¤¤¡£¤Ç¤¹¤¬¡¢ + Apache 2.0 ¤Ç¤ÎÊѹ¹ÅÀ¤ò´Þ¤à¤¿¤á¤Ë¤Ï¹¹¿·¤µ¤ì¤Æ¤¤¤Ê¤¤¤«¤â¤·¤ì¤Ê¤¤ + ¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/content-negotiation.html.ko.euc-kr b/docs/manual/content-negotiation.html.ko.euc-kr new file mode 100644 index 00000000..2c8430cc --- /dev/null +++ b/docs/manual/content-negotiation.html.ko.euc-kr @@ -0,0 +1,610 @@ + + + +³»¿ëÇù»ó (Content Negotiation) - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

³»¿ëÇù»ó (Content Negotiation)

+
+

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

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

¾ÆÆÄÄ¡´Â HTTP/1.1 ±Ô¾à¿¡ ±â¼úµÈ ³»¿ëÇù»ó(content + negotiation)À» Áö¿øÇÑ´Ù. ³»¿ëÇù»óÀº media type, ¾ð¾î, ¹®ÀÚÁýÇÕ, + ÀÎÄÚµù µî¿¡ ´ëÇØ ºê¶ó¿ìÀú°¡ Á¦°øÇÑ ¼±È£µµ¿¡ µû¶ó ÀÚ¿øÀÇ + °¡Àå ÀûÇÕÇÑ Ç¥ÇöÀ» ¼±ÅÃÇÑ´Ù. ¶Ç ºÒ¿ÏÀüÇÑ Çù»ó Á¤º¸¸¦ º¸³»´Â + ºê¶ó¿ìÀúÀÇ ¿äûÀ» Áö´ÉÀûÀ¸·Î ó¸®ÇÏ´Â ±â´Éµµ ÀÖ´Ù.

+ +

±âº»ÀûÀ¸·Î ÄÄÆÄÀϵǴ mod_negotiation + ¸ðµâÀÌ ³»¿ëÇù»ó ±â´ÉÀ» Á¦°øÇÑ´Ù.

+
+ +
top
+
+

³»¿ëÇù»ó¿¡ ´ëÇØ

+ +

ÀÚ¿øÀº ¿©·¯ ´Ù¸¥ Ç¥ÇöÀ» °¡Áú ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, ´Ù¸¥ + ¾ð¾î³ª ´Ù¸¥ media type ȤÀº µÑ ¸ðµÎ°¡ ´Ù¸¥ Ç¥ÇöµéÀÌ ÀÖÀ» + ¼ö ÀÖ´Ù. °¡Àå Àû´çÇÑ Ç¥ÇöÀ» ¼±ÅÃÇÏ´Â ÇÑ°¡Áö ¹æ¹ýÀº »ç¿ëÀÚ¿¡°Ô + ¸ñ·Ï ÆäÀÌÁö¸¦ º¸¿©ÁÖ°í ¼±ÅÃÇÏ°Ô ÇÏ´Â °ÍÀÌ´Ù. ±×·¯³ª ¼­¹ö°¡ + ÀÚµ¿À¸·Î ¼±ÅÃÇÏ´Â °Íµµ °¡´ÉÇÏ´Ù. ÀÌ´Â ºê¶ó¿ìÀú°¡ ¿äûÀÇ + ÀϺηΠ±×µéÀÌ ¼±È£Çϴ ǥÇö¿¡ ´ëÇÑ Á¤º¸¸¦ º¸³»±â¶§¹®¿¡ + °¡´ÉÇÏ´Ù. ¿¹¸¦ µé¾î, ºê¶ó¿ìÀú´Â °¡´ÉÇÑÇÑ ºÒ¾î·Î, ±×·¯³ª + ¾ø´Ù¸é ¿µ¾î·Î Á¤º¸¸¦ º¸°í½Í´Ù°í ¾Ë·ÁÁÙ ¼ö ÀÖ´Ù. ºê¶ó¿ìÀú´Â + ¿äûÀÇ Çì´õ·Î ±×µéÀÇ ±âÈ£¸¦ ³ªÅ¸³½´Ù. ¿ÀÁ÷ ºÒ¾î·ÎµÈ Ç¥Çö¸¸À» + ¿äûÇÑ´Ù¸é ºê¶ó¿ìÀú´Â ´ÙÀ½°ú °°ÀÌ º¸³½´Ù.

+ +

Accept-Language: fr

+ +

ÀÌ·± ±âÈ£´Â Ç¥ÇöÀÌ ¾ð¾îº°·Î ´Ù¸¦ °æ¿ì¿¡¸¸ °í·ÁµÈ´Ù.

+ +

´ÙÀ½Àº ´õ º¹ÀâÇÑ ¿äûÀÇ ¿¹·Î ºê¶ó¿ìÀú°¡ ºÒ¾î¿Í ¿µ¾î¸¦ + ¹ÞÀ» ¼ö ÀÖÁö¸¸, ºÒ¾î¸¦ ´õ ¼±È£ÇÏ°í, ¿©·¯ media typeÀ» ¹ÞÀ» + ¼ö ÀÖÁö¸¸, ÀÏ¹Ý ÅؽºÆ® º¸´Ù´Â HTML, ´Ù¸¥ media type º¸´Ù´Â + GIF¿Í JPEGÀ» ¼±È£ÇÑ´Ù°í ¾Ë·ÁÁØ´Ù.

+ +

+ Accept-Language: fr; q=1.0, en; q=0.5
+ Accept: text/html; q=1.0, text/*; q=0.8, image/gif; q=0.6, image/jpeg; q=0.6, image/*; q=0.5, */*; q=0.1 +

+ +

¾ÆÆÄÄ¡´Â HTTP/1.1 ±Ô¾à¿¡ Á¤ÀÇµÈ '¼­¹ö ÁÖµµ(server driven)' + ³»¿ëÇù»óÀ» Áö¿øÇÑ´Ù. ¾ÆÆÄÄ¡´Â Accept, + Accept-Language, Accept-Charset, + Accept-Encoding ¿äû Çì´õ¸¦ ¸ðµÎ Áö¿øÇÑ´Ù. + ¶Ç, ¾ÆÆÄÄ¡´Â RFC 2295¿Í RFC 2296¿¡ Á¤ÀÇµÈ ½ÇÇèÀûÀÎ ³»¿ëÇù»óÀÎ + 'ÀÚ¿¬½º·¯¿î(transparent)' ¿äû Çì´õµµ Áö¿øÇÑ´Ù. ±×·¯³ª ÀÌ + RFC¿¡ Á¤ÀÇµÈ '±â´É Çù»ó(feature negotiation)'Àº Áö¿øÇÏÁö + ¾Ê´Â´Ù.

+ +

ÀÚ¿ø(resource)Àº (RFC 2396) URI·Î ±¸º°ÇÏ´Â + °³³äÀûÀÎ Á¸Àç´Ù. ¾ÆÆÄÄ¡¿Í °°Àº À¥¼­¹ö´Â ÀÚ¿øÀÇ + Ç¥Çö(representations)À» Á¦°øÇÑ´Ù. Ç¥ÇöÀº + ÁöÁ¤µÈ media type, ¹®ÀÚÁýÇÕ, ÀÎÄÚµù µîÀ» °¡Áø ¹ÙÀÌÆ®µé·Î + µÇÀÖ´Ù. ÀÚ¿øÀº ¿©·¯ Ç¥Çö°ú (¶§·Î´Â ¾øÀ» ¼öµµ ÀÖ´Ù) ¿¬°üµÈ´Ù. + ÀÚ¿ø¿¡ ¿©·¯ Ç¥ÇöÀÌ ÀÖ´Ù¸é ÀÚ¿øÀ» + Çù»ó°¡´ÉÇÏ´Ù°í(negotiable) ºÎ¸£¸ç, À̶§ + °¢ Ç¥ÇöÀ» º¯Çü(variant)À̶ó°í ÇÑ´Ù. + Çù»ó°¡´ÉÇÑ ÀÚ¿øÀÇ º¯Çü Á¾·ù¸¦ Çù»óÀÇ + ¹üÀ§(dimension)¶ó°í ÇÑ´Ù.

+
top
+
+

¾ÆÆÄÄ¡ÀÇ Çù»ó

+ +

ÀÚ¿øÀ» Çù»óÇϱâÀ§ÇØ ¼­¹ö´Â °¢ º¯Çü¿¡ ´ëÇÑ Á¤º¸°¡ ÇÊ¿äÇÏ´Ù. + ´ÙÀ½ µÎ°¡Áö ¹æ¹ýÁß Çϳª·Î Á¤º¸¸¦ ¾ò´Â´Ù:

+ +
    +
  • º¯ÇüÀ» ´ãÀº ÆÄÀϵéÀ» Á÷Á¢ ¿­°ÅÇÑ type mapÀ» (¿¹¸¦ + µé¾î, *.var ÆÄÀÏ) »ç¿ëÇϰųª,
    • + +
  • Á÷Á¢ ÁöÁ¤ÇÏÁö¾Ê¾Æµµ ¼­¹ö°¡ ÆÄÀÏ¸í¿¡¼­ ±ÔÄ¢À» ã¾Æ¼­ + °á°ú¸¦ ¼±ÅÃÇÏ´Â 'MultiViews'¸¦ »ç¿ëÇÑ´Ù.
    • +
+ +

type-map ÆÄÀÏ »ç¿ëÇϱâ

+ +

type mapÀº type-mapÀ̶õ Çڵ鷯¿Í ¿¬°áµÈ + (ȤÀº ÀÌÀü ¾ÆÆÄÄ¡ ¼³Á¤°ú ȣȯÀ» À§ÇØ MIME typeÀÌ + application/x-type-mapÀÎ) ¹®¼­´Ù. ÀÌ ±â´ÉÀ» + »ç¿ëÇÏ·Á¸é ¼³Á¤¿¡¼­ type-map Çڵ鷯¿¡ ´ëÇÑ + ÆÄÀÏ È®ÀåÀÚ¸¦ ÁöÁ¤ÇØ¾ß ÇÑ´Ù. ¼­¹ö ¼³Á¤ÆÄÀÏ¿¡ ´ÙÀ½°ú °°ÀÌ + ¼³Á¤ÇÏ´Â °ÍÀÌ ÁÁ´Ù.

+ +

AddHandler type-map .var

+ +

Type map ÆÄÀÏÀº ÇØ´çÇÏ´Â ÀÚ¿ø°ú À̸§ÀÌ °°¾Æ¾ß ÇÏ°í, + °¢ º¯Çü¿¡ ´ëÇÑ Ç׸ñÀÌ ÀÖ¾î¾ß ÇÑ´Ù. Ç׸ñÀº ¿©·¯ HTTPÇü½Ä + Çì´õ ÁÙ·Î ±¸¼ºµÈ´Ù. º¯Çü¿¡ ´ëÇÑ °¢°¢ÀÇ Ç׸ñµéÀº ºóÁÙ·Î + ±¸ºÐÇÑ´Ù. Ç׸ñ¾È¿¡¼­ ºóÁÙÀ» »ç¿ëÇÒ ¼ö ¾ø´Ù. (ÀÌ·¸°Ô ÇÒ + ÇÊ¿ä°¡ ¾ø°í, À־ ¹«½ÃÇÏÁö¸¸) ¿©·¯ Ç׸ñÀÌ °øÅëÀ¸·Î °¡Áö°í + ÀÖ´Â ³»¿ëÀ¸·Î map ÆÄÀÏÀ» ½ÃÀÛÇÏ´Â °ÍÀÌ º¸ÅëÀÌ´Ù. ´ÙÀ½Àº + map ÆÄÀÏ ¿¹´Ù. ÀÌ ÆÄÀÏÀÇ À̸§Àº foo.var·Î, + foo¶ó´Â ÀÚ¿øÀ» ¼³¸íÇÑ´Ù.

+ +

+ URI: foo
+
+ URI: foo.en.html
+ Content-type: text/html
+ Content-language: en
+
+ URI: foo.fr.de.html
+ Content-type: text/html;charset=iso-8859-2
+ Content-language: fr, de
+

+

typemap ÆÄÀÏÀÌ ÆÄÀϸí È®ÀåÀÚ º¸´Ù, ½ÉÁö¾î Multiviews¸¦ + »ç¿ëÇÏ¿©µµ, ¿ì¼±±ÇÀ» °¡ÁüÀ» ÁÖÀÇÇ϶ó. º¯ÇüÀÌ ¼­·Î ´Ù¸¥ Ç°ÁúÀ» + °¡Áø´Ù¸é, ´ÙÀ½°ú °°ÀÌ (JPEG, GIF, ASCII-art¿¡ ÇØ´çÇÏ´Â) + media type¿¡ "qs" ÆĶó¹ÌÅÍ·Î Ç°Áú(source quality)À» Ç¥½ÃÇÒ + ¼ö ÀÖ´Ù:

+ +

+ URI: foo
+
+ URI: foo.jpeg
+ Content-type: image/jpeg; qs=0.8
+
+ URI: foo.gif
+ Content-type: image/gif; qs=0.5
+
+ URI: foo.txt
+ Content-type: text/plain; qs=0.01
+

+ +

qs °ªÀº 0.000¿¡¼­ 1.000 »çÀÌ´Ù. qs °ªÀÌ 0.000ÀÎ º¯ÇüÀº + Àý´ë ¼±ÅõÇÁö ¾ÊÀ½À» ÁÖÀÇÇ϶ó. 'qs' °ªÀÌ ¾ø´Â º¯ÇüÀº 1.0À¸·Î + Ãë±ÞµÈ´Ù. qs °ªÀº Ŭ¶óÀ̾ðÆ®ÀÇ ´É·Â°ú´Â °ü°è¾øÀÌ ´Ù¸¥ º¯Çüµé°ú + ºñ±³ÇÏ¿© ±× º¯ÇüÀÇ »ó´ëÀûÀÎ 'Ç°Áú'À» ³ªÅ¸³½´Ù. ¿¹¸¦ µé¾î, + »çÁøÀ» ³ªÅ¸³»·Á´Â °æ¿ì JPEG ÆÄÀÏÀÌ ASCII ÆÄÀϺ¸´Ù´Â Ç×»ó + ³ôÀº Ç°ÁúÀ» °¡Áø´Ù. ±×·¯³ª ÀÚ¿øÀÌ ¿ø·¡ ASCII art¿´´Ù¸é + ASCII Ç¥ÇöÀÌ JPEG Ç¥Çöº¸´Ù ´õ ³ôÀº Ç°ÁúÀ» °¡Áú ¼ö ÀÖ´Ù. + ±×·¯¹Ç·Î ¾î¶² º¯ÇüÀÇ qs °ªÀº Ç¥ÇöÇÏ·Á´Â ÀÚ¿øÀÇ ¼ºÁú¿¡ + µû¶ó ´Ù¸£´Ù.

+ +

Áö¿øÇÏ´Â ¸ðµç Çì´õ ¸ñ·ÏÀº mod_negotation + typemap ¹®¼­¸¦ Âü°íÇ϶ó.

+ + +

Multiviews

+ +

MultiViews´Â µð·ºÅ丮º° ¿É¼ÇÀ̹ǷÎ, + httpd.confÀÇ + <Directory>, + <Location>, + <Files> + ¼½¼Ç ȤÀº (AllowOverride°¡ + ÀûÀýÈ÷ ¼³Á¤µÇ¾ú´Ù¸é) .htaccess ÆÄÀÏÀÇ + Options Áö½Ã¾î¿¡ ¼³Á¤ÇÒ + ¼ö ÀÖ´Ù. Options AllÀº MultiViews¸¦ + Æ÷ÇÔÇÏÁö¾ÊÀ½À» ÁÖÀÇÇ϶ó. µû·Î Á÷Á¢ ½áÁà¾ß ÇÑ´Ù.

+ +

MultiViews¸¦ »ç¿ëÇÏ¸é ´ÙÀ½°ú °°Àº ÀÏÀÌ ÀϾ´Ù: + ¼­¹ö°¡ /some/dir/foo¿¡ ´ëÇÑ ¿äûÀ» ¹Þ°í + /some/dir/foo¿¡ MultiViews°¡ µ¿ÀÛÇϸç + /some/dir/foo°¡ Á¸ÀçÇÏÁö ¾ÊÀ» °æ¿ì, + ¼­¹ö´Â µð·ºÅ丮¿¡¼­ À̸§ÀÌ foo.*ÀÎ ÆÄÀϵéÀ» ¸ðµç Æ÷ÇÔÇÏ´Â + °¡»óÀÇ type mapÀ» ¸¸µç´Ù. Ŭ¶óÀ̾ðÆ®°¡ ¿äûÇÑ media type°ú + content-encodingÀ» °¡Áö°í ÀÌÁß¿¡ °¡Àå ÀûÇÕÇÑ °ÍÀ» ¼±ÅÃÇÑ´Ù.

+ +

MultiViews´Â ¼­¹ö°¡ µð·ºÅ丮¸¦ ÂüÁ¶ÇÒ¶§ + ÆÄÀÏÀ» ã´Â DirectoryIndex Áö½Ã¾î¿¡µµ + Àû¿ëµÈ´Ù. ¼³Á¤ÆÄÀÏÀÌ ´ÙÀ½°ú °°´Ù¸é,

+

DirectoryIndex index

+

index.html°ú index.html3ÀÌ + ¸ðµÎ ÀÖ´Ù¸é ¼­¹ö´Â ÀÌµÑ Áß¿¡ Çϳª¸¦ °áÁ¤ÇÑ´Ù. µÑ ¸ðµÎ ¾ø°í + index.cgi°¡ ÀÖ´Ù¸é, ¼­¹ö´Â ±×°ÍÀ» ½ÇÇàÇÑ´Ù.

+ +

µð·ºÅ丮¸¦ ÀÐÀ»¶§ ÆÄÀÏÁß Çϳª°¡ Charset, Content-Type, + Language, Encoding¸¦ ÆÇ´ÜÇÏ´Â mod_mimeÀÌ ¸ð¸£´Â + È®ÀåÀÚ¸¦ °¡Áø´Ù¸é, °á°ú´Â MultiViewsMatch Áö½Ã¾î ¼³Á¤¿¡ + ´Þ·Ç´Ù. ÀÌ Áö½Ã¾î´Â Çڵ鷯, ÇÊÅÍ, ´Ù¸¥ È®ÀåÇüµéÀÌ MultiViews + Çù»ó¿¡ Âü¿©ÇÒÁö ¿©ºÎ¸¦ °áÁ¤ÇÑ´Ù.

+ +
top
+
+

Çù»ó¹æ¹ý

+ +

¾ÆÆÄÄ¡°¡ type-map ÆÄÀÏÀ̳ª µð·ºÅ丮¿¡ ÀÖ´Â ÆÄÀϸíµé·Î + ÁÖ¾îÁø ÀÚ¿ø¿¡ ´ëÇÑ º¯Çü ¸ñ·ÏÀ» ¾ò°ÔµÇ¸é 'ÃÖÀûÀÇ' º¯ÇüÀ» + °áÁ¤ÇϱâÀ§ÇØ µÎ ¹æ¹ýÁß Çϳª¸¦ »ç¿ëÇÑ´Ù. ¾ÆÆÄÄ¡ ³»¿ëÇù»ó + ±â´ÉÀ» »ç¿ëÇϱâÀ§ÇØ Á¤È®È÷ Çù»óÀÌ ¾î¶»°Ô ÀϾ´ÂÁö ÀÚ¼¼È÷ + ¾Ë ÇÊ¿ä´Â ¾ø´Ù. ±×·¯³ª ±Ã±ÝÇÑ »ç¶÷À» À§ÇØ ÀÌ ¹æ¹ýÀ» ¼³¸íÇÑ´Ù.

+ +

µÎ°¡Áö Çù»ó¹æ¹ýÀÌ ÀÖ´Ù:

+ +
    +
  1. ¾ÆÆÄÄ¡ ¾Ë°í¸®ÁòÀ» »ç¿ëÇÏ¿© ¼­¹ö°¡ ÁÖµµÇÏ´Â + Çù»óÀº ÀϹÝÀûÀÎ °æ¿ì¿¡ »ç¿ëÇÑ´Ù. ¾ÆÆÄÄ¡ ¾Ë°í¸®ÁòÀº + ¾Æ·¡¼­ ÀÚ¼¼È÷ ¼³¸íÇÑ´Ù. ÀÌ ¾Ë°í¸®ÁòÀ» »ç¿ëÇÏ¸é ¾ÆÆÄÄ¡´Â + ´õ ³ªÀº °á°ú¸¦ ¾ò±âÀ§ÇØ Á¾Á¾ ƯÁ¤ ¹üÀ§ÀÇ + Ç°Áú°è¼ö(quality factor)¸¦ 'Á¶ÀÛÇÑ´Ù'. ¾ÆÆÄÄ¡°¡ Ç°Áú°è¼ö¸¦ + Á¶ÀÛÇÏ´Â ¹æ¹ýÀº ¾Æ·¡¼­ ÀÚ¼¼È÷ ¼³¸íÇÑ´Ù.
    2. + +
  2. ÀÚ¿¬½º·¯¿î(Transparent) ³»¿ëÇù»óÀº + ºê¶ó¿ìÀú°¡ RFC 2295¿¡ Á¤ÀÇµÈ ¹æ¹ýÀ¸·Î ¿äûÇÒ °æ¿ì¿¡¸¸ + »ç¿ëÇÑ´Ù. ÀÌ Çù»ó¹æ¹ýÀº 'ÃÖÀûÀÇ' º¯ÇüÀ» °áÁ¤ÇÒ ±ÇÇÑÀ» + ºê¶ó¿ìÀú¿¡°Ô ºÎ¿©ÇÑ´Ù. ±×·¡¼­ °á°ú´Â ºê¶ó¿ìÀúÀÇ ¾Ë°í¸®Áò¿¡ + ´Þ·È´Ù. ÀÚ¿¬½º·¯¿î Çù»ó°úÁ¤Áß¿¡ ºê¶ó¿ìÀú´Â ¾ÆÆÄÄ¡¿¡°Ô + RFC 2296¿¡ Á¤ÀÇµÈ '¿ø°Ý º¯Çü¼±Åà ¾Ë°í¸®Áò(remote variant + selection algorithm)'À» ¿äûÇÒ ¼ö ÀÖ´Ù.
    3. +
+ +

Çù»óÀÇ ¹üÀ§

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¹üÀ§¼³¸í
Media Typeºê¶ó¿ìÀú´Â Accept Çì´õ·Î ¼±È£¸¦ ³ªÅ¸³½´Ù. + °¢ Ç׸ñÀº Ç°Áú°è¼ö¸¦ °¡Áú ¼ö ÀÖ´Ù. º¯ÇüÀÇ ¼³¸íµµ Ç°Áú°è¼ö¸¦ + ("qs" ÆĶó¹ÌÅÍ) °¡Áú ¼ö ÀÖ´Ù.
Languageºê¶ó¿ìÀú´Â Accept-Language Çì´õ·Î ¼±È£¸¦ + ³ªÅ¸³½´Ù. °¢ Ç׸ñÀº Ç°Áú°è¼ö¸¦ °¡Áú ¼ö ÀÖ´Ù. º¯ÇüÀº + ¿©·¯ ¾ð¾î¸¦ °¡Áú (ȤÀº ¾Æ¹« ¾ð¾îµµ ¾øÀ») ¼ö ÀÖ´Ù.
Encodingºê¶ó¿ìÀú´Â Accept-Encoding Çì´õ·Î ¼±È£¸¦ + ³ªÅ¸³½´Ù. °¢ Ç׸ñÀº Ç°Áú°è¼ö¸¦ °¡Áú ¼ö ÀÖ´Ù.
Charsetºê¶ó¿ìÀú´Â Accept-Charset Çì´õ·Î ¼±È£¸¦ + ³ªÅ¸³½´Ù. °¢ Ç׸ñÀº Ç°Áú°è¼ö¸¦ °¡Áú ¼ö ÀÖ´Ù. º¯ÇüÀº + media typeÀÇ ÆĶó¹ÌÅÍ·Î ¹®ÀÚÁýÇÕÀ» ³ªÅ¸³¾ ¼ö ÀÖ´Ù.
+ + +

¾ÆÆÄÄ¡ Çù»ó ¾Ë°í¸®Áò

+ +

¾ÆÆÄÄ¡´Â ºê¶ó¿ìÀú¿¡°Ô º¸³¾ 'ÃÖÀûÀÇ' º¯ÇüÀ» (ÀÖ´Ù¸é) + ¼±ÅÃÇϱâÀ§ÇØ ¾Æ·¡ ¾Ë°í¸®ÁòÀ» »ç¿ëÇÑ´Ù. ÀÌ ¾Ë°í¸®ÁòÀº º¯°æÇÒ + ¼ö ¾ø´Ù. ´ÙÀ½¿Í °°ÀÌ µ¿ÀÛÇÑ´Ù:

+ +
    +
  1. ¸ÕÀú, Çù»óÀÇ °¢ ¹üÀ§¿¡ ´ëÇØ ÇØ´çÇÏ´Â Accept* + Çì´õ¸¦ °Ë»çÇÏ°í, °¢ º¯Çü¿¡ Ç°Áú°ªÀ» ¸Å±ä´Ù. ¾î¶² ¹üÀ§ÀÇ + Accept* Çì´õ°¡ ¹Þ¾ÆµéÀÌÁö ¾Ê´Â º¯ÇüÀº Èĺ¸¿¡¼­ + Á¦¿ÜÇÑ´Ù. ¾î¶² º¯Çüµµ ³²Áö¾ÊÀ¸¸é 4 ´Ü°è·Î °£´Ù.
    2. + +
  2. + Èĺ¸¿¡¼­ Çϳª¾¿ Á¦¿ÜÇÏ¿© 'ÃÖÀûÀÇ' º¯ÇüÀ» ã´Â´Ù. ´ÙÀ½ + °¢ °Ë»ç´Â ¼ø¼­´ë·Î ÀϾ´Ù. °¢ °Ë»ç¿¡¼­ ¼±ÅõÇÁö¾ÊÀº + º¯ÇüÀº Á¦¿ÜµÈ´Ù. °¢ °Ë»çÈÄ ÇÑ º¯Çü¸¸ ³²À¸¸é À̸¦ ÃÖÀûÀÇ + º¯ÇüÀ¸·Î ¼±ÅÃÇÏ°í 3 ´Ü°è·Î °£´Ù. ¿©·¯ º¯ÇüÀÌ ³²À¸¸é + ´ÙÀ½ °Ë»ç¸¦ ÁøÇàÇÑ´Ù. + +
      +
    1. Accept Çì´õÀÇ Ç°Áú°è¼ö¿Í º¯ÇüÀÇ + media type¿¡ ´ëÇÑ Ç°Áú°ªÀ» °öÇÏ¿© °¡Àå ³ôÀº °ªÀ» + °¡Áø º¯ÇüÀ» ¼±ÅÃÇÑ´Ù.
      2. + +
    2. °¡Àå ³ôÀº ¾ð¾î(language) Ç°Áú°è¼ö¸¦ °¡Áø º¯ÇüÀ» + ¼±ÅÃÇÑ´Ù.
      3. + +
    3. Accept-Language Çì´õ¿¡ (ÀÖ´Ù¸é) + ³ª¿Â ¾ð¾îÀÇ ¼ø¼­ ȤÀº LanguagePriority + Áö½Ã¾î¿¡ (ÀÖ´Ù¸é) ³ª¿Â ¾ð¾îÀÇ ¼ø¼­¸¦ °¡Áö°í °¡Àå + ÀûÇÕÇÑ ¾ð¾î¸¦ °¡Áø º¯ÇüÀ» ¼±ÅÃÇÑ´Ù.
      4. + +
    4. °¡Àå ³ôÀº (text/html media typeÀÇ ¹öÀüÀ» ³ªÅ¸³»´Â) + 'level' media ÆĶó¹ÌÅ͸¦ °¡Áø º¯ÇüÀ» ¼±ÅÃÇÑ´Ù.
      5. + +
    5. Accept-Charset Çì´õ¸¦ °¡Áö°í °¡Àå + ÀûÇÕÇÑ charset media ÆĶó¹ÌÅ͸¦ °¡Áø º¯ÇüÀ» ã´Â´Ù. + Çì´õ°¡ ¾ø´Ù¸é ISO-8859-1 ¹®ÀÚÁýÇÕÀ» °¡Àå ¼±È£ÇÑ´Ù. + text/* media typeÀ» °¡ÁöÁö¸¸ ¸í½ÃÀûÀ¸·Î + ƯÁ¤ ¹®ÀÚÁýÇÕ°ú ¿¬°áµÇÁö¾ÊÀº º¯ÇüÀº ISO-8859-1·Î + °¡Á¤ÇÑ´Ù.
      6. + +
    6. ISO-8859-1ÀÌ ¾Æ´Ñ charset media ÆĶó¹ÌÅ͸¦ + °¡Áø º¯ÇüµéÀ» ¼±ÅÃÇÑ´Ù. ±×·± º¯ÇüÀÌ ¾ø´Ù¸é, ´ë½Å ¸ðµç + º¯ÇüÀ» ¼±ÅÃÇÑ´Ù.
      7. + +
    7. °¡Àå ÀûÇÕÇÑ ÀÎÄÚµùÀ» °¡Áø º¯ÇüÀ» ¼±ÅÃÇÑ´Ù. + user-agent¿¡ ÀûÇÕÇÑ ÀÎÄÚµùÀ» °¡Áø º¯ÇüÀÌ ÀÖ´Ù¸é ±× + º¯Çü¸¸À» ¼±ÅÃÇÑ´Ù. ±×·¸Áö¾Ê°í ÀÎÄÚµùµÈ º¯Çü°ú ÀÎÄÚµù¾ÈµÈ + º¯ÇüÀÌ °°ÀÌ ÀÖ´Ù¸é ÀÎÄÚµù¾ÈµÊ º¯Çü¸¸À» ¼±ÅÃÇÑ´Ù. º¯ÇüÀÌ + ¸ðµÎ ÀÎÄÚµùµÇ¾ú°Å³ª ¸ðµÎ ÀÎÄÚµù¾ÈµÈ °æ¿ì ¸ðµç º¯ÇüÀ» + ¼±ÅÃÇÑ´Ù.
      8. + +
    8. content length°¡ °¡Àå ÀûÀº º¯ÇüÀ» ¼±ÅÃÇÑ´Ù.
      9. + +
    9. ³²Àº °ÍÁß Ã¹¹øÀç º¯ÇüÀ» ¼±ÅÃÇÑ´Ù. ÀÌ´Â type-map + ÆÄÀÏÀÇ ¾Õ¿¡ ³ª¿Ô°Å³ª, µð·ºÅ丮¿¡¼­ º¯ÇüÀ» ÀÐÀº °æ¿ì + ÆÄÀϸíÀ» ASCII ÄÚµå ¼ø¼­·Î ÇÏ¿© ¾Õ¿¡ ³ª¿À´Â °ÍÀÌ´Ù.
      10. +
    +
    3. + +
  3. ÀÌÁ¦ ¾Ë°í¸®ÁòÀÌ 'ÃÖÀûÀÇ' º¯ÇüÀ» ¼±ÅÃÇß´Ù. ÀÌ°ÍÀ» ÀÀ´äÀ¸·Î + º¸³½´Ù. HTTP ÀÀ´ä Çì´õ Vary´Â Çù»óÀÇ ¹üÀ§¸¦ + ³ªÅ¸³»°Ô µÈ´Ù. (ºê¶ó¿ìÀú¿Í ij½¬´Â ÀÚ¿øÀ» ij½¬ÇÒ¶§ ÀÌ Á¤º¸¸¦ + »ç¿ëÇÒ ¼ö ÀÖ´Ù.) ³¡.
    4. + +
  4. ÀÌ ´Ü°è¿¡ µµ´ÞÇß´Ù¸é (¸ðµÎ ºê¶ó¿ìÀú°¡ ¹ÞÁö¸øÇϱ⠶§¹®¿¡) + ¾î¶² º¯Çüµµ ¼±ÅÃÀÌ ¾ÈµÈ °æ¿ì´Ù. ("No acceptable + representation"¸¦ ¶æÇÏ´Â) »óÅ 406°ú ³»¿ëÀ¸·Î »ç¿ë°¡´ÉÇÑ + º¯ÇüÀÇ ¸ñ·ÏÀ» ´ãÀº HTML ¹®¼­¸¦ ÀÀ´äÀ» º¸³½´Ù. ¶Ç, HTML + Vary Çì´õ´Â º¯ÇüÀÇ ¹üÀ§¸¦ ³ªÅ¸³½´Ù.
    5. +
+ +
top
+
+

Ç°Áú°è¼ö Á¶ÀÛÇϱâ

+ +

¾ÆÆÄÄ¡´Â Á¾Á¾ À§ÀÇ ¾ÆÆÄÄ¡ Çù»ó ¾Ë°í¸®ÁòÀ» ¾ö°ÝÈ÷ ÁöÅ°Áö¾Ê°í + Ç°Áú°è¼ö¸¦ º¯°æÇÑ´Ù. ÀÌÀ¯´Â ¿ÏÀüÇÏ°í Á¤È®ÇÑ Á¤º¸¸¦ º¸³»Áö¾Ê´Â + ºê¶ó¿ìÀú¿¡°Ô (¾Ë°í¸®ÁòÀÇ) ´õ ³ªÀº °á°ú¸¦ º¸³»±â À§Çؼ­´Ù. + ³Î¸® ¾²ÀÌ´Â ºê¶ó¿ìÀúÁß ÀϺδ ÀÚÁÖ À߸øµÈ º¯ÇüÀ» ¼±ÅÃÇϵµ·Ï + Accept Çì´õ¸¦ º¸³½´Ù. ºê¶ó¿ìÀú°¡ ¿ÏÀüÇÏ°í ¿Ã¹Ù¸¥ + Á¤º¸¸¦ º¸³½´Ù¸é, Á¶ÀÛÀ» ÇÏÁö¾Ê´Â´Ù.

+ +

Media Type°ú ¿ÍÀϵåÄ«µå

+ +

Accept: ¿äû Çì´õ´Â media type¿¡ ´ëÇÑ ¼±È£¸¦ + ³ªÅ¸³½´Ù. ¶Ç, *´Â ¾î¶² ¹®ÀÚ¿­ÀÌ¶óµµ °¡´ÉÇϱ⶧¹®¿¡ "image/*"³ª + "*/*" °°ÀÌ '¿ÍÀϵåÄ«µå' media typeÀ» »ç¿ëÇÒ ¼öµµ ÀÖ´Ù. ±×·¡¼­ + ´ÙÀ½°ú °°Àº ¿äûÀº:

+ +

Accept: image/*, */*

+ +

"image/"·Î ½ÃÀÛÇÏ´Â ¾î¶² type°ú ´Ù¸¥ ¾î¶² typeµµ °¡´ÉÇÔÀ» + ÀǹÌÇÑ´Ù. ¾î¶² ºê¶ó¿ìÀú´Â + ÀÚ½ÅÀÌ ½ÇÁ¦·Î ´Ù·ê ¼ö ÀÖ´Â type¿¡ Ãß°¡·Î ¿ÍÀϵåÄ«µå¸¦ º¸³½´Ù. + ¿¹¸¦ µé¸é:

+ +

+ Accept: text/html, text/plain, image/gif, image/jpeg, */* +

+

ÀÌÀ¯´Â Á÷Á¢ ¿­°ÅÇÑ typeÀ» ¼±È£ÇÏÁö¸¸ ´Ù¸¥ Ç¥ÇöÀÌ ÀÖ´Ù¸é + ±×°Íµµ ±¦ÂúÀ½À» ³ªÅ¸³»±â À§Çؼ­´Ù. ºê¶ó¿ìÀú°¡ ½ÇÁ¦·Î ¿øÇÑ + °ÍÀº ´ÙÀ½°ú °°ÀÌ ¸í½ÃÀûÀ¸·Î Ç°Áú°ªÀ» »ç¿ëÇÑ °ÍÀÌ´Ù.

+

+ Accept: text/html, text/plain, image/gif, image/jpeg, */*; q=0.01 +

+

Á÷Á¢ ¿­°ÅÇÑ typeÀº Ç°Áú°è¼ö°¡ ¾ø¾î¼­ ±âº»°ªÀÎ (°¡Àå ³ôÀº) + 1.0À» °¡Áø´Ù. ¿ÍÀϵåÄ«µå */*´Â ³·Àº ¼±È£µµ 0.01À» °¡Áö¹Ç·Î + Á÷Á¢ ¿­°ÅÇÑ type¿¡ ¸Â´Â º¯ÇüÀÌ ¾ø´Â °æ¿ì¿¡¸¸ ´Ù¸¥ typeµéÀÌ + »ç¿ëµÈ´Ù.

+ +

Accept: Çì´õ¿¡ q °è¼ö°¡ ÀüÇô ¾ø°í + "*/*"°¡ ÀÖ´Ù¸é, ¾ÆÆÄÄ¡´Â ¹Ù¶÷Á÷ÇÑ ÇൿÀ» À§ÇØ q °ªÀ¸·Î 0.01À» + ÁöÁ¤ÇÑ´Ù. ¶Ç, "type/*" ÇüÅÂÀÇ ¿ÍÀϵåÄ«µå¿¡´Â ("*/*"º¸´Ù´Â + ´õ ¼±È£Çϵµ·Ï) 0.02¸¦ ÁöÁ¤ÇÑ´Ù. Accept: Çì´õ¿¡¼­ + q °è¼ö¸¦ °¡Áö´Â media typeÀÌ ÀÖ´Ù¸é ÀÌ·± Ưº°ÇÑ °ªÀ» Ãß°¡ÇÏÁö + ¾Ê´Â´Ù. ±×·¡¼­ ¸í½ÃÀûÀÎ Á¤º¸¸¦ º¸³»´Â ºê¶ó¿ìÀúÀÇ + ¿äûÀº ¿äûÇѵ¥·Î ó¸®ÇÑ´Ù.

+ + +

¾ð¾î(language) Çù»óÀÇ ¿¹¿Ü

+ +

¾ÆÆÄÄ¡ 2.0Àº ¾ð¾î Çù»óÀÌ ½ÇÆÐÇÑ °æ¿ì ºÎµå·´°Ô º¹±¸ÇϱâÀ§ÇØ + Çù»ó ¾Ë°í¸®Áò¿¡ »õ·Î ¿¹¿Ü¸¦ ¸î°³ Ãß°¡Çß´Ù.

+ +

Ŭ¶óÀ̾ðÆ®°¡ ¼­¹ö¿¡ ÆäÀÌÁö¸¦ ¿äûÇßÀ»¶§ ¼­¹ö°¡ ºê¶ó¿ìÀú°¡ + º¸³½ Accept-language¿¡ ¸Â´Â ÆäÀÌÁö¸¦ ´Ü ÇÑ°³¸¸ + ãÀ¸¸é ¹®Á¦°¡ ¾øÁö¸¸, ±×·¯Áö ¾ÊÀº °æ¿ì ¼­¹ö´Â Ŭ¶óÀ̾ðÆ®¿¡°Ô + "No Acceptable Variant"³ª "Multiple Choices" ÀÀ´äÀ» º¸³½´Ù. + ÀÌ·± ¿À·ù¹®À» ÇÇÇϱâÀ§ÇØ ÀÌ °æ¿ì Accept-language¸¦ + ¹«½ÃÇÏ°í Ŭ¶óÀ̾ðÆ®ÀÇ ¿äû¿¡ ¸íÈ®È÷ ¸ÂÁö´Â ¾ÊÁö¸¸ ¹®¼­¸¦ + º¸³»µµ·Ï ¾ÆÆÄÄ¡¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ForceLanguagePriority + Áö½Ã¾î´Â ¼­¹ö°¡ ÀÌ·± ¿À·ù¹®Áß Çϳª ȤÀº µÑ´Ù¸¦ ¹«½ÃÇÏ°í + LanguagePriority + Áö½Ã¾î·Î ÆÇ´ÜÇϵµ·Ï ÇÑ´Ù.

+ +

¶Ç, ¼­¹ö´Â ¸Â´Â ¾ð¾î¸¦ ¸øãÀº °æ¿ì ºÎ¸ð¾ð¾î¸¦ ãÀ» ¼öµµ + ÀÖ´Ù. ¿¹¸¦ µé¾î Ŭ¶óÀ̾ðÆ®°¡ ¿µ±¹¿µ¾î¸¦ ¶æÇÏ´Â + en-GB ¾ð¾î·Î ¹®¼­¸¦ ¿äûÇÑ °æ¿ì, HTTP/1.1 Ç¥ÁØ¿¡ + µû¸£¸é ¼­¹ö´Â enÀ¸·Î¸¸ Ç¥½ÃµÈ ¹®¼­¸¦ ÀϹÝÀûÀ¸·Î + ¼±ÅÃÇÏÁö ¸øÇÑ´Ù. (±×·¡¼­ ¿µ±¹¿µ¾î¸¦ ÀÌÇØÇÏ´Â µ¶ÀÚ°¡ ÀϹÝÀûÀÎ + ¿µ¾îµµ ÀÌÇØÇÒ ¼ö ÀÖÀ¸¹Ç·Î Accept-Language Çì´õ¿¡ + en-GB¸¸ Æ÷ÇÔÇÏ°í enÀ» Æ÷ÇÔÇÏÁö¾ÊÀ¸¸é + °ÅÀÇ È®½ÇÈ÷ À߸øµÈ ¼³Á¤ÀÓÀ» À¯ÀÇÇ϶ó. ºÒÇàÈ÷µµ ÇöÀç ¸¹Àº + Ŭ¶óÀ̾ðÆ®µéÀº ÀÌ·± ½ÄÀ¸·Î ±âº»¼³Á¤µÇÀÖ´Ù.) ´Ù¸¥ ¾ð¾î¸¦ + ãÁö ¸øÇÏ¿© ¼­¹ö°¡ "No Acceptable Variants" ¿À·ù¸¦ º¸³»°Å³ª + LanguagePriority·Î + µ¹¾Æ°¡¾ß ÇÑ´Ù¸é, ¼­¹ö´Â ÇÏÀ§¾ð¾î ±Ô¾àÀ» ¹«½ÃÇÏ°í + en-GB¸¦ en ¹®¼­¿¡ ´ëÀÀÇÑ´Ù. + ¾Ï¹¬ÀûÀ¸·Î ¾ÆÆÄÄ¡´Â ºÎ¸ð¾ð¾î¸¦ ¸Å¿ì ³·Àº Ç°Áú°ªÀ¸·Î + Ŭ¶óÀ̾ðÆ®ÀÇ Çã¿ë¾ð¾î ¸ñ·Ï¿¡ Ãß°¡ÇÑ´Ù. ±×·¯³ª Ŭ¶óÀ̾ðÆ®°¡ + "en-GB; q=0.9, fr; q=0.8"À» ¿äûÇÏ°í ¼­¹ö¿¡ "en"°ú "fr" + ¹®¼­°¡ ÀÖ´Ù¸é, "fr" ¹®¼­°¡ ¼±ÅõÊÀ» ÁÖÀÇÇ϶ó. ÀÌ´Â HTTP/1.1 + Ç¥ÁØÀ» ÁöÅ°°í, ¿Ã¹Ù·Î ¼³Á¤µÈ Ŭ¶óÀ̾ðÆ®¿Í È¿À²ÀûÀ¸·Î + µ¿ÀÛÇϱâÀ§ÇÔÀÌ´Ù.

+ +

»ç¿ëÀÚ°¡ ¼±È£ÇÏ´Â ¾ð¾î¸¦ ¾Ë¾Æ³»±âÀ§ÇÑ (ÄíÅ°³ª Ưº°ÇÑ + URL-°æ·Î °°Àº) °í±Þ ±â¹ýÀ» Áö¿øÇϱâÀ§ÇØ ¾ÆÆÄÄ¡ 2.0.47ºÎÅÍ + mod_negotiationÀº prefer-language¶ó´Â + ȯ°æº¯¼ö¸¦ ÀνÄÇÑ´Ù. ÀÌ È¯°æº¯¼ö°¡ + Á¸ÀçÇÏ°í ÀûÀýÇÑ ¾ð¾îű׸¦ Æ÷ÇÔÇÑ´Ù¸é, + mod_negotiationÀº ÇØ´çÇÏ´Â º¯ÇüÀ» ¼±ÅÃÇÏ·Á°í + ½ÃµµÇÑ´Ù. ±×·± º¯ÇüÀÌ ¾ø´Ù¸é ÀϹÝÀûÀÎ Çù»ó°úÁ¤À» ½ÃÀÛÇÑ´Ù.

+ +

¿¹Á¦

+ SetEnvIf Cookie "language=(.+)" prefer-language=$1 +

+ +
top
+
+

ÀÚ¿¬½º·¯¿î(transparent) ³»¿ëÇù»óÀÇ È®Àå

+ +

¾ÆÆÄÄ¡´Â ´ÙÀ½°ú °°ÀÌ ÀÚ¿¬½º·¯¿î ³»¿ëÈ®Àå ÇÁ·ÎÅäÄÝÀ» (RFC 2295) +È®ÀåÇÑ´Ù. º¯Çü ¸ñ·ÏÀÇ »õ·Î¿î {encoding ..}´Â ƯÁ¤ +content-encodingÀ» °¡Áø º¯Çü¸¸À» ÁöĪÇÑ´Ù. RVSA/1.0 ¾Ë°í¸®ÁòÀº +(RFC 2296) ¸ñ·Ï¿¡¼­ ÀÎÄÚµùµÈ º¯ÇüÀ» ÀνÄÇÒ ¼ö ÀÖ°í, ÀÎÄÚµùÀÌ +Accept-Encoding ¿äû Çì´õ¿¡ ¸Â´Â °æ¿ì ÀÎÄÚµùµÈ +º¯Çüµéµµ È帷Π»ç¿ëÇϵµ·Ï È®ÀåµÇ¾ú´Ù. RVSA/1.0 ±¸ÇöÀº ÃÖÀûÀÇ +º¯ÇüÀ» ã±â Àü¿¡ °è»êµÈ Ç°Áú°è¼ö¸¦ ¼Ò¼öÁ¡ 5ÀÚ¸®¿¡¼­ ¹Ý¿Ã¸²ÇÏÁö +¾Ê´Â´Ù.

+
top
+
+

ÇÏÀÌÆÛ¸µÅ©¿Í À̸§±ÔÄ¢¿¡ ´ëÇÏ¿©

+ +

¾ð¾î(language) Çù»óÀ» »ç¿ëÇÑ´Ù¸é ÆÄÀÏÀº ¿©·¯ È®ÀåÀÚ¸¦ + °¡Áö°í È®ÀåÀÚÀÇ ¼ø¼­´Â º¸Åë °ü°è¾øÀ¸¹Ç·Î ÆÄÀÏ¸í¿¡ ¿©·¯ ´Ù¸¥ + À̸§±ÔÄ¢À» »ç¿ëÇÒ ¼ö ÀÖ´Ù. (ÀÚ¼¼ÇÑ ³»¿ëÀº mod_mime ¹®¼­¸¦ + Âü°íÇ϶ó.)

+ +

ÀüÇüÀûÀÎ ÆÄÀÏÀº MIME-type È®ÀåÀÚ (¿¹¸¦ µé¾î, + html), °æ¿ì¿¡ µû¶ó encoding È®ÀåÀÚ (¿¹¸¦ + µé¾î, gz), ÆÄÀÏ¿¡ ¿©·¯ ¾ð¾î º¯ÇüÀÌ ÀÖ´Â + °æ¿ì ¹°·Ð ¾ð¾î È®ÀåÀÚ¸¦ (¿¹¸¦ µé¾î, en) + °¡Áø´Ù.

+ +

¿¹Á¦:

+ +
    +
  • foo.en.html
    • + +
  • foo.html.en
    • + +
  • foo.en.html.gz
    • +
+ +

´ÙÀ½Àº ¸î¸î ÆÄÀϸí°ú ±× ÆÄÀÏ¿¡ ´ëÇÑ À¯È¿ÇÏ°í À¯È¿ÇÏÁö¾ÊÀº + ÇÏÀÌÆÛ¸µÅ©¸¦ º¸ÀδÙ:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ÆÄÀϸíÀ¯È¿ÇÑ ÇÏÀÌÆÛ¸µÅ©À¯È¿ÇÏÁö¾ÊÀº ÇÏÀÌÆÛ¸µÅ©
foo.html.enfoo
+ foo.html		-
foo.en.htmlfoofoo.html
foo.html.en.gzfoo
+ foo.html		foo.gz
+ foo.html.gz
foo.en.html.gzfoofoo.html
+ foo.html.gz
+ foo.gz
foo.gz.html.enfoo
+ foo.gz
+ foo.gz.html		foo.html
foo.html.gz.enfoo
+ foo.html
+ foo.html.gz		foo.gz
+ +

À§ Ç¥¸¦ º¸¸é ÇÏÀÌÆÛ¸µÅ©¿¡ ¾î¶² È®ÀåÀÚµµ ¾ø´Â À̸§À» + (¿¹¸¦ µé¾î, foo) Ç×»ó »ç¿ëÇÒ ¼ö ÀÖÀ½À» + ¾Ë ¼ö ÀÖ´Ù. ÀÌ °æ¿ì ÀåÁ¡Àº ¹®¼­ÀÇ ½ÇÁ¦ Á¾·ù¸¦ ¼û±æ ¼ö À־, + ¿¹¸¦ µé¾î ÇÏÀÌ·¯¸µÅ© ÂüÁ¶¸¦ ¼öÁ¤ÇϾʰí + html ÆÄÀÏÀ» shtmlÀ̳ª + cgi·Î º¯°æÇÒ ¼ö ÀÖ´Ù´Â Á¡ÀÌ´Ù.

+ +

°è¼Ó ÇÏÀÌÆÛ¸µÅ©¿¡ MIME-typeÀ» (¿¹¸¦ µé¾î, + foo.html) »ç¿ëÇÏ°í ½Í´Ù¸é (encoding È®ÀåÀÚ°¡ + ÀÖ´Ù¸é À̰͵µ Æ÷ÇÔÇÏ¿©) ¾ð¾î È®ÀåÀÚ¸¦ MIME-type È®ÀåÀÚº¸´Ù + ¿À¸¥ÂÊ¿¡ (¿¹¸¦ µé¾î, foo.html.en) + µÎ¾î¾ßÇÑ´Ù.

+
top
+
+

ij½¬¿¡ ´ëÇÏ¿©

+ +

ij½¬°¡ Ç¥ÇöÀ» ÀúÀåÇϸé Ç¥Çö°ú ¿äû URLÀ» ¿¬°ü½ÃŲ´Ù. + ´ÙÀ½¹ø ±× URLÀ» ¿äûÇϸé ij½¬´Â ÀúÀåµÈ Ç¥ÇöÀ» »ç¿ëÇÑ´Ù. + ±×·¯³ª ¼­¹ö¿Í Çù»óÀÌ °¡´ÉÇÑ ÀÚ¿øÀÎ °æ¿ì ù¹ø° ¿äûÇÑ º¯Çü¸¸ + ij½¬µÇ¾î ÀÌÈÄ ¿äûÀº ij½¬µÈ À߸øµÈ ÀÀ´äÀ» ¾òÀ» ¼ö ÀÖ´Ù. + À̸¦ ¸·±âÀ§ÇØ ¾ÆÆÄÄ¡´Â º¸Åë ³»¿ëÇù»óÈÄ ¹ÝȯµÇ´Â ¸ðµç ¿äû¿¡ + HTTP/1.0 Ŭ¶óÀ̾ðÆ®°¡ ij½¬¸¦ ¸øÇϵµ·Ï Ç¥½Ã¸¦ ÇÑ´Ù. ¶Ç, ¾ÆÆÄÄ¡´Â + Çù»óÇÑ ÀÀ´äÀÇ Ä³½¬¸¦ Çã¿ëÇÏ´Â HTTP/1.1 ÇÁ·ÎÅäÄÝÀÇ ±â´ÉÀ» + Áö¿øÇÑ´Ù.

+ +

CacheNegotiatedDocs + Áö½Ã¾î´Â HTTP/1.0 ȣȯ Ŭ¶óÀ̾ðÆ®(ºê¶ó¿ìÀú ȤÀº ij½¬)°¡ + º¸³½ ¿äû¿¡ ´ëÇØ Çù»óÇÑ ÀÀ´äÀ» ij½¬ÇÒ ¼ö ÀÖ°Ô ÇÑ´Ù. ÀÌ Áö½Ã¾î´Â + ¼­¹ö³ª °¡»óÈ£½ºÆ® ¼³Á¤¿¡ »ç¿ëÇϸç, ¾Æ±Ô¸ÕÆ®¸¦ ¹ÞÁö¾Ê´Â´Ù. + ÀÌ Áö½Ã¾î´Â HTTP/1.1 Ŭ¶óÀ̾ðÆ®ÀÇ ¿äû°ú´Â °ü°è°¡ ¾ø´Ù.

+ +

HTTP/1.1 Ŭ¶óÀ̾ðÆ®¿¡°Ô ¾ÆÆÄÄ¡´Â ÀÀ´äÀÇ Çù»ó ¹üÀ§¸¦ + ¾Ë·ÁÁÖ´Â Vary HTTP ÀÀ´äÇì´õ¸¦ º¸³½´Ù. ÀÌ Á¤º¸¸¦ + »ç¿ëÇÏ¿© ´ÙÀ½ ¿äûÀ» ij½¬µÈ º¹»çº»À¸·Î ´ëüÇÒ ¼ö ÀÖ´ÂÁö + ÆÇ´ÜÇÒ ¼ö ÀÖ´Ù. Çé»óÀÇ ¹üÀ§¿Í °ü°è¾øÀÌ Ä³½¬µÈ º¹»çº»À» + ±ÇÇÑ´Ù¸é force-no-vary ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù.

+ +
top
+
+

´Ù¸¥ Á¤º¸

+ +

³»¿ëÇù»ó¿¡ ´ëÇÑ ´Ù¸¥ Á¤º¸´Â Alan J. Flavell°¡ ¾´ Language + Negotiation Notes¸¦ Âü°íÇ϶ó. ±×·¯³ª ÀÌ ¹®¼­´Â ¾ÆÁ÷ + ¾ÆÆÄÄ¡ 2.0ÀÇ º¯È­¸¦ ¹Ý¿µÇÏÁö ¾ÊÀ» ¼ö ÀÖ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/convenience.map b/docs/manual/convenience.map new file mode 100644 index 00000000..e1459c2a --- /dev/null +++ b/docs/manual/convenience.map @@ -0,0 +1,386 @@ +# Mapping from directive names to URLs +# GENERATED FROM XML -- DO NOT EDIT +# You may use it as follows: +# RewriteEngine On +# RewriteMap dir2url txt:/path/to/convenience.map +# RewriteCond ${dir2url:$1} (.+) +# RewriteRule ^/+([^/]+)$ /manual/%1 [R=301,NE,L] + +acceptfilter mod/core.html#acceptfilter +acceptmutex mod/mpm_common.html#acceptmutex +acceptpathinfo mod/core.html#acceptpathinfo +accessfilename mod/core.html#accessfilename +action mod/mod_actions.html#action +addalt mod/mod_autoindex.html#addalt +addaltbyencoding mod/mod_autoindex.html#addaltbyencoding +addaltbytype mod/mod_autoindex.html#addaltbytype +addcharset mod/mod_mime.html#addcharset +adddefaultcharset mod/core.html#adddefaultcharset +adddescription mod/mod_autoindex.html#adddescription +addencoding mod/mod_mime.html#addencoding +addhandler mod/mod_mime.html#addhandler +addicon mod/mod_autoindex.html#addicon +addiconbyencoding mod/mod_autoindex.html#addiconbyencoding +addiconbytype mod/mod_autoindex.html#addiconbytype +addinputfilter mod/mod_mime.html#addinputfilter +addlanguage mod/mod_mime.html#addlanguage +addmoduleinfo mod/mod_info.html#addmoduleinfo +addoutputfilter mod/mod_mime.html#addoutputfilter +addoutputfilterbytype mod/core.html#addoutputfilterbytype +addtype mod/mod_mime.html#addtype +alias mod/mod_alias.html#alias +aliasmatch mod/mod_alias.html#aliasmatch +allow mod/mod_authz_host.html#allow +allowconnect mod/mod_proxy.html#allowconnect +allowencodedslashes mod/core.html#allowencodedslashes +allowoverride mod/core.html#allowoverride +anonymous mod/mod_authn_anon.html#anonymous +anonymous_logemail mod/mod_authn_anon.html#anonymous_logemail +anonymous_mustgiveemail mod/mod_authn_anon.html#anonymous_mustgiveemail +anonymous_nouserid mod/mod_authn_anon.html#anonymous_nouserid +anonymous_verifyemail mod/mod_authn_anon.html#anonymous_verifyemail +authbasicauthoritative mod/mod_auth_basic.html#authbasicauthoritative +authbasicprovider mod/mod_auth_basic.html#authbasicprovider +authdbduserpwquery mod/mod_authn_dbd.html#authdbduserpwquery +authdbduserrealmquery mod/mod_authn_dbd.html#authdbduserrealmquery +authdbmgroupfile mod/mod_authz_dbm.html#authdbmgroupfile +authdbmtype mod/mod_authn_dbm.html#authdbmtype +authdbmuserfile mod/mod_authn_dbm.html#authdbmuserfile +authdefaultauthoritative mod/mod_authn_default.html#authdefaultauthoritative +authdigestalgorithm mod/mod_auth_digest.html#authdigestalgorithm +authdigestdomain mod/mod_auth_digest.html#authdigestdomain +authdigestnccheck mod/mod_auth_digest.html#authdigestnccheck +authdigestnonceformat mod/mod_auth_digest.html#authdigestnonceformat +authdigestnoncelifetime mod/mod_auth_digest.html#authdigestnoncelifetime +authdigestprovider mod/mod_auth_digest.html#authdigestprovider +authdigestqop mod/mod_auth_digest.html#authdigestqop +authdigestshmemsize mod/mod_auth_digest.html#authdigestshmemsize +authgroupfile mod/mod_authz_groupfile.html#authgroupfile +authldapbinddn mod/mod_authnz_ldap.html#authldapbinddn +authldapbindpassword mod/mod_authnz_ldap.html#authldapbindpassword +authldapcharsetconfig mod/mod_authnz_ldap.html#authldapcharsetconfig +authldapcomparednonserver mod/mod_authnz_ldap.html#authldapcomparednonserver +authldapdereferencealiases mod/mod_authnz_ldap.html#authldapdereferencealiases +authldapgroupattribute mod/mod_authnz_ldap.html#authldapgroupattribute +authldapgroupattributeisdn mod/mod_authnz_ldap.html#authldapgroupattributeisdn +authldapremoteuserisdn mod/mod_authnz_ldap.html#authldapremoteuserisdn +authldapurl mod/mod_authnz_ldap.html#authldapurl +authname mod/core.html#authname +authnprovideralias mod/mod_authn_alias.html#authnprovideralias +authtype mod/core.html#authtype +authuserfile mod/mod_authn_file.html#authuserfile +authzdbmauthoritative mod/mod_authz_dbm.html#authzdbmauthoritative +authzdbmtype mod/mod_authz_dbm.html#authzdbmtype +authzdefaultauthoritative mod/mod_authz_default.html#authzdefaultauthoritative +authzgroupfileauthoritative mod/mod_authz_groupfile.html#authzgroupfileauthoritative +authzldapauthoritative mod/mod_authnz_ldap.html#authzldapauthoritative +authzownerauthoritative mod/mod_authz_owner.html#authzownerauthoritative +authzuserauthoritative mod/mod_authz_user.html#authzuserauthoritative +browsermatch mod/mod_setenvif.html#browsermatch +browsermatchnocase mod/mod_setenvif.html#browsermatchnocase +bufferedlogs mod/mod_log_config.html#bufferedlogs +cachedefaultexpire mod/mod_cache.html#cachedefaultexpire +cachedirlength mod/mod_disk_cache.html#cachedirlength +cachedirlevels mod/mod_disk_cache.html#cachedirlevels +cachedisable mod/mod_cache.html#cachedisable +cacheenable mod/mod_cache.html#cacheenable +cachefile mod/mod_file_cache.html#cachefile +cacheignorecachecontrol mod/mod_cache.html#cacheignorecachecontrol +cacheignoreheaders mod/mod_cache.html#cacheignoreheaders +cacheignorenolastmod mod/mod_cache.html#cacheignorenolastmod +cachelastmodifiedfactor mod/mod_cache.html#cachelastmodifiedfactor +cachemaxexpire mod/mod_cache.html#cachemaxexpire +cachemaxfilesize mod/mod_disk_cache.html#cachemaxfilesize +cacheminfilesize mod/mod_disk_cache.html#cacheminfilesize +cachenegotiateddocs mod/mod_negotiation.html#cachenegotiateddocs +cacheroot mod/mod_disk_cache.html#cacheroot +cachestorenostore mod/mod_cache.html#cachestorenostore +cachestoreprivate mod/mod_cache.html#cachestoreprivate +cgimapextension mod/core.html#cgimapextension +charsetdefault mod/mod_charset_lite.html#charsetdefault +charsetoptions mod/mod_charset_lite.html#charsetoptions +charsetsourceenc mod/mod_charset_lite.html#charsetsourceenc +checkspelling mod/mod_speling.html#checkspelling +contentdigest mod/core.html#contentdigest +cookiedomain mod/mod_usertrack.html#cookiedomain +cookieexpires mod/mod_usertrack.html#cookieexpires +cookielog mod/mod_log_config.html#cookielog +cookiename mod/mod_usertrack.html#cookiename +cookiestyle mod/mod_usertrack.html#cookiestyle +cookietracking mod/mod_usertrack.html#cookietracking +coredumpdirectory mod/mpm_common.html#coredumpdirectory +customlog mod/mod_log_config.html#customlog +dav mod/mod_dav.html#dav +davdepthinfinity mod/mod_dav.html#davdepthinfinity +davgenericlockdb mod/mod_dav_lock.html#davgenericlockdb +davlockdb mod/mod_dav_fs.html#davlockdb +davmintimeout mod/mod_dav.html#davmintimeout +dbdexptime mod/mod_dbd.html#dbdexptime +dbdkeep mod/mod_dbd.html#dbdkeep +dbdmax mod/mod_dbd.html#dbdmax +dbdmin mod/mod_dbd.html#dbdmin +dbdparams mod/mod_dbd.html#dbdparams +dbdpersist mod/mod_dbd.html#dbdpersist +dbdpreparesql mod/mod_dbd.html#dbdpreparesql +dbdriver mod/mod_dbd.html#dbdriver +defaulticon mod/mod_autoindex.html#defaulticon +defaultlanguage mod/mod_mime.html#defaultlanguage +defaulttype mod/core.html#defaulttype +deflatebuffersize mod/mod_deflate.html#deflatebuffersize +deflatecompressionlevel mod/mod_deflate.html#deflatecompressionlevel +deflatefilternote mod/mod_deflate.html#deflatefilternote +deflatememlevel mod/mod_deflate.html#deflatememlevel +deflatewindowsize mod/mod_deflate.html#deflatewindowsize +deny mod/mod_authz_host.html#deny +directory mod/core.html#directory +directoryindex mod/mod_dir.html#directoryindex +directorymatch mod/core.html#directorymatch +directoryslash mod/mod_dir.html#directoryslash +documentroot mod/core.html#documentroot +dumpioinput mod/mod_dumpio.html#dumpioinput +dumpiooutput mod/mod_dumpio.html#dumpiooutput +enableexceptionhook mod/mpm_common.html#enableexceptionhook +enablemmap mod/core.html#enablemmap +enablesendfile mod/core.html#enablesendfile +errordocument mod/core.html#errordocument +errorlog mod/core.html#errorlog +example mod/mod_example.html#example +expiresactive mod/mod_expires.html#expiresactive +expiresbytype mod/mod_expires.html#expiresbytype +expiresdefault mod/mod_expires.html#expiresdefault +extendedstatus mod/mod_status.html#extendedstatus +extfilterdefine mod/mod_ext_filter.html#extfilterdefine +extfilteroptions mod/mod_ext_filter.html#extfilteroptions +fileetag mod/core.html#fileetag +files mod/core.html#files +filesmatch mod/core.html#filesmatch +filterchain mod/mod_filter.html#filterchain +filterdeclare mod/mod_filter.html#filterdeclare +filterprotocol mod/mod_filter.html#filterprotocol +filterprovider mod/mod_filter.html#filterprovider +filtertrace mod/mod_filter.html#filtertrace +forcelanguagepriority mod/mod_negotiation.html#forcelanguagepriority +forcetype mod/core.html#forcetype +forensiclog mod/mod_log_forensic.html#forensiclog +gracefulshutdowntimeout mod/mpm_common.html#gracefulshutdowntimeout +group mod/mpm_common.html#group +header mod/mod_headers.html#header +headername mod/mod_autoindex.html#headername +hostnamelookups mod/core.html#hostnamelookups +identitycheck mod/mod_ident.html#identitycheck +identitychecktimeout mod/mod_ident.html#identitychecktimeout +ifdefine mod/core.html#ifdefine +ifmodule mod/core.html#ifmodule +ifversion mod/mod_version.html#ifversion +imapbase mod/mod_imagemap.html#imapbase +imapdefault mod/mod_imagemap.html#imapdefault +imapmenu mod/mod_imagemap.html#imapmenu +include mod/core.html#include +indexignore mod/mod_autoindex.html#indexignore +indexoptions mod/mod_autoindex.html#indexoptions +indexorderdefault mod/mod_autoindex.html#indexorderdefault +indexstylesheet mod/mod_autoindex.html#indexstylesheet +isapiappendlogtoerrors mod/mod_isapi.html#isapiappendlogtoerrors +isapiappendlogtoquery mod/mod_isapi.html#isapiappendlogtoquery +isapicachefile mod/mod_isapi.html#isapicachefile +isapifakeasync mod/mod_isapi.html#isapifakeasync +isapilognotsupported mod/mod_isapi.html#isapilognotsupported +isapireadaheadbuffer mod/mod_isapi.html#isapireadaheadbuffer +keepalive mod/core.html#keepalive +keepalivetimeout mod/core.html#keepalivetimeout +languagepriority mod/mod_negotiation.html#languagepriority +ldapcacheentries mod/mod_ldap.html#ldapcacheentries +ldapcachettl mod/mod_ldap.html#ldapcachettl +ldapconnectiontimeout mod/mod_ldap.html#ldapconnectiontimeout +ldapopcacheentries mod/mod_ldap.html#ldapopcacheentries +ldapopcachettl mod/mod_ldap.html#ldapopcachettl +ldapsharedcachefile mod/mod_ldap.html#ldapsharedcachefile +ldapsharedcachesize mod/mod_ldap.html#ldapsharedcachesize +ldaptrustedclientcert mod/mod_ldap.html#ldaptrustedclientcert +ldaptrustedglobalcert mod/mod_ldap.html#ldaptrustedglobalcert +ldaptrustedmode mod/mod_ldap.html#ldaptrustedmode +ldapverifyservercert mod/mod_ldap.html#ldapverifyservercert +limit mod/core.html#limit +limitexcept mod/core.html#limitexcept +limitinternalrecursion mod/core.html#limitinternalrecursion +limitrequestbody mod/core.html#limitrequestbody +limitrequestfields mod/core.html#limitrequestfields +limitrequestfieldsize mod/core.html#limitrequestfieldsize +limitrequestline mod/core.html#limitrequestline +limitxmlrequestbody mod/core.html#limitxmlrequestbody +listen mod/mpm_common.html#listen +listenbacklog mod/mpm_common.html#listenbacklog +loadfile mod/mod_so.html#loadfile +loadmodule mod/mod_so.html#loadmodule +location mod/core.html#location +locationmatch mod/core.html#locationmatch +lockfile mod/mpm_common.html#lockfile +logformat mod/mod_log_config.html#logformat +loglevel mod/core.html#loglevel +maxclients mod/mpm_common.html#maxclients +maxkeepaliverequests mod/core.html#maxkeepaliverequests +maxmemfree mod/mpm_common.html#maxmemfree +maxrequestsperchild mod/mpm_common.html#maxrequestsperchild +maxrequestsperthread mod/beos.html#maxrequestsperthread +maxspareservers mod/prefork.html#maxspareservers +maxsparethreads mod/mpm_common.html#maxsparethreads +maxthreads mod/mpm_netware.html#maxthreads +mcachemaxobjectcount mod/mod_mem_cache.html#mcachemaxobjectcount +mcachemaxobjectsize mod/mod_mem_cache.html#mcachemaxobjectsize +mcachemaxstreamingbuffer mod/mod_mem_cache.html#mcachemaxstreamingbuffer +mcacheminobjectsize mod/mod_mem_cache.html#mcacheminobjectsize +mcacheremovalalgorithm mod/mod_mem_cache.html#mcacheremovalalgorithm +mcachesize mod/mod_mem_cache.html#mcachesize +metadir mod/mod_cern_meta.html#metadir +metafiles mod/mod_cern_meta.html#metafiles +metasuffix mod/mod_cern_meta.html#metasuffix +mimemagicfile mod/mod_mime_magic.html#mimemagicfile +minspareservers mod/prefork.html#minspareservers +minsparethreads mod/mpm_common.html#minsparethreads +mmapfile mod/mod_file_cache.html#mmapfile +modmimeusepathinfo mod/mod_mime.html#modmimeusepathinfo +multiviewsmatch mod/mod_mime.html#multiviewsmatch +namevirtualhost mod/core.html#namevirtualhost +noproxy mod/mod_proxy.html#noproxy +nwssltrustedcerts mod/mod_nw_ssl.html#nwssltrustedcerts +nwsslupgradeable mod/mod_nw_ssl.html#nwsslupgradeable +options mod/core.html#options +order mod/mod_authz_host.html#order +passenv mod/mod_env.html#passenv +pidfile mod/mpm_common.html#pidfile +protocolecho mod/mod_echo.html#protocolecho +proxy mod/mod_proxy.html#proxy +proxybadheader mod/mod_proxy.html#proxybadheader +proxyblock mod/mod_proxy.html#proxyblock +proxydomain mod/mod_proxy.html#proxydomain +proxyerroroverride mod/mod_proxy.html#proxyerroroverride +proxyiobuffersize mod/mod_proxy.html#proxyiobuffersize +proxymatch mod/mod_proxy.html#proxymatch +proxymaxforwards mod/mod_proxy.html#proxymaxforwards +proxypass mod/mod_proxy.html#proxypass +proxypassreverse mod/mod_proxy.html#proxypassreverse +proxypassreversecookiedomain mod/mod_proxy.html#proxypassreversecookiedomain +proxypassreversecookiepath mod/mod_proxy.html#proxypassreversecookiepath +proxypreservehost mod/mod_proxy.html#proxypreservehost +proxyreceivebuffersize mod/mod_proxy.html#proxyreceivebuffersize +proxyremote mod/mod_proxy.html#proxyremote +proxyremotematch mod/mod_proxy.html#proxyremotematch +proxyrequests mod/mod_proxy.html#proxyrequests +proxytimeout mod/mod_proxy.html#proxytimeout +proxyvia mod/mod_proxy.html#proxyvia +readmename mod/mod_autoindex.html#readmename +receivebuffersize mod/mpm_common.html#receivebuffersize +redirect mod/mod_alias.html#redirect +redirectmatch mod/mod_alias.html#redirectmatch +redirectpermanent mod/mod_alias.html#redirectpermanent +redirecttemp mod/mod_alias.html#redirecttemp +removecharset mod/mod_mime.html#removecharset +removeencoding mod/mod_mime.html#removeencoding +removehandler mod/mod_mime.html#removehandler +removeinputfilter mod/mod_mime.html#removeinputfilter +removelanguage mod/mod_mime.html#removelanguage +removeoutputfilter mod/mod_mime.html#removeoutputfilter +removetype mod/mod_mime.html#removetype +requestheader mod/mod_headers.html#requestheader +require mod/core.html#require +rewritebase mod/mod_rewrite.html#rewritebase +rewritecond mod/mod_rewrite.html#rewritecond +rewriteengine mod/mod_rewrite.html#rewriteengine +rewritelock mod/mod_rewrite.html#rewritelock +rewritelog mod/mod_rewrite.html#rewritelog +rewriteloglevel mod/mod_rewrite.html#rewriteloglevel +rewritemap mod/mod_rewrite.html#rewritemap +rewriteoptions mod/mod_rewrite.html#rewriteoptions +rewriterule mod/mod_rewrite.html#rewriterule +rlimitcpu mod/core.html#rlimitcpu +rlimitmem mod/core.html#rlimitmem +rlimitnproc mod/core.html#rlimitnproc +satisfy mod/core.html#satisfy +scoreboardfile mod/mpm_common.html#scoreboardfile +script mod/mod_actions.html#script +scriptalias mod/mod_alias.html#scriptalias +scriptaliasmatch mod/mod_alias.html#scriptaliasmatch +scriptinterpretersource mod/core.html#scriptinterpretersource +scriptlog mod/mod_cgi.html#scriptlog +scriptlogbuffer mod/mod_cgi.html#scriptlogbuffer +scriptloglength mod/mod_cgi.html#scriptloglength +scriptsock mod/mod_cgid.html#scriptsock +securelisten mod/mod_nw_ssl.html#securelisten +sendbuffersize mod/mpm_common.html#sendbuffersize +serveradmin mod/core.html#serveradmin +serveralias mod/core.html#serveralias +serverlimit mod/mpm_common.html#serverlimit +servername mod/core.html#servername +serverpath mod/core.html#serverpath +serverroot mod/core.html#serverroot +serversignature mod/core.html#serversignature +servertokens mod/core.html#servertokens +setenv mod/mod_env.html#setenv +setenvif mod/mod_setenvif.html#setenvif +setenvifnocase mod/mod_setenvif.html#setenvifnocase +sethandler mod/core.html#sethandler +setinputfilter mod/core.html#setinputfilter +setoutputfilter mod/core.html#setoutputfilter +ssiendtag mod/mod_include.html#ssiendtag +ssierrormsg mod/mod_include.html#ssierrormsg +ssistarttag mod/mod_include.html#ssistarttag +ssitimeformat mod/mod_include.html#ssitimeformat +ssiundefinedecho mod/mod_include.html#ssiundefinedecho +sslcacertificatefile mod/mod_ssl.html#sslcacertificatefile +sslcacertificatepath mod/mod_ssl.html#sslcacertificatepath +sslcadnrequestfile mod/mod_ssl.html#sslcadnrequestfile +sslcadnrequestpath mod/mod_ssl.html#sslcadnrequestpath +sslcarevocationfile mod/mod_ssl.html#sslcarevocationfile +sslcarevocationpath mod/mod_ssl.html#sslcarevocationpath +sslcertificatechainfile mod/mod_ssl.html#sslcertificatechainfile +sslcertificatefile mod/mod_ssl.html#sslcertificatefile +sslcertificatekeyfile mod/mod_ssl.html#sslcertificatekeyfile +sslciphersuite mod/mod_ssl.html#sslciphersuite +sslcryptodevice mod/mod_ssl.html#sslcryptodevice +sslengine mod/mod_ssl.html#sslengine +sslhonorcipherorder mod/mod_ssl.html#sslhonorcipherorder +sslmutex mod/mod_ssl.html#sslmutex +ssloptions mod/mod_ssl.html#ssloptions +sslpassphrasedialog mod/mod_ssl.html#sslpassphrasedialog +sslprotocol mod/mod_ssl.html#sslprotocol +sslproxycacertificatefile mod/mod_ssl.html#sslproxycacertificatefile +sslproxycacertificatepath mod/mod_ssl.html#sslproxycacertificatepath +sslproxycarevocationfile mod/mod_ssl.html#sslproxycarevocationfile +sslproxycarevocationpath mod/mod_ssl.html#sslproxycarevocationpath +sslproxyciphersuite mod/mod_ssl.html#sslproxyciphersuite +sslproxyengine mod/mod_ssl.html#sslproxyengine +sslproxymachinecertificatefile mod/mod_ssl.html#sslproxymachinecertificatefile +sslproxymachinecertificatepath mod/mod_ssl.html#sslproxymachinecertificatepath +sslproxyprotocol mod/mod_ssl.html#sslproxyprotocol +sslproxyverify mod/mod_ssl.html#sslproxyverify +sslproxyverifydepth mod/mod_ssl.html#sslproxyverifydepth +sslrandomseed mod/mod_ssl.html#sslrandomseed +sslrequire mod/mod_ssl.html#sslrequire +sslrequiressl mod/mod_ssl.html#sslrequiressl +sslsessioncache mod/mod_ssl.html#sslsessioncache +sslsessioncachetimeout mod/mod_ssl.html#sslsessioncachetimeout +sslusername mod/mod_ssl.html#sslusername +sslverifyclient mod/mod_ssl.html#sslverifyclient +sslverifydepth mod/mod_ssl.html#sslverifydepth +startservers mod/mpm_common.html#startservers +startthreads mod/mpm_common.html#startthreads +suexecusergroup mod/mod_suexec.html#suexecusergroup +threadlimit mod/mpm_common.html#threadlimit +threadsperchild mod/mpm_common.html#threadsperchild +threadstacksize mod/mpm_common.html#threadstacksize +timeout mod/core.html#timeout +traceenable mod/core.html#traceenable +transferlog mod/mod_log_config.html#transferlog +typesconfig mod/mod_mime.html#typesconfig +unsetenv mod/mod_env.html#unsetenv +usecanonicalname mod/core.html#usecanonicalname +usecanonicalphysicalport mod/core.html#usecanonicalphysicalport +user mod/mpm_common.html#user +userdir mod/mod_userdir.html#userdir +virtualdocumentroot mod/mod_vhost_alias.html#virtualdocumentroot +virtualdocumentrootip mod/mod_vhost_alias.html#virtualdocumentrootip +virtualhost mod/core.html#virtualhost +virtualscriptalias mod/mod_vhost_alias.html#virtualscriptalias +virtualscriptaliasip mod/mod_vhost_alias.html#virtualscriptaliasip +win32disableacceptex mod/mpm_winnt.html#win32disableacceptex +xbithack mod/mod_include.html#xbithack diff --git a/docs/manual/custom-error.html b/docs/manual/custom-error.html new file mode 100644 index 00000000..3ee08771 --- /dev/null +++ b/docs/manual/custom-error.html @@ -0,0 +1,15 @@ +URI: custom-error.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: custom-error.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: custom-error.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: custom-error.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/custom-error.html.en b/docs/manual/custom-error.html.en new file mode 100644 index 00000000..dcfdbe9f --- /dev/null +++ b/docs/manual/custom-error.html.en @@ -0,0 +1,204 @@ + + + +Custom Error Responses - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Custom Error Responses

+
+

Available Languages:  en  | + es  | + ja  | + ko 

+
+ +

Additional functionality allows webmasters to configure the response + of Apache to some error or problem.

+ +

Customizable responses can be defined to be activated in the event of + a server detected error or problem.

+ +

If a script crashes and produces a "500 Server Error" response, + then this response can be replaced with either some friendlier text or by + a redirection to another URL (local or external).

+
+ +
top
+
+

Behavior

+ + +

Old Behavior

+ + +

NCSA httpd 1.3 would return some boring old error/problem message + which would often be meaningless to the user, and would provide no + means of logging the symptoms which caused it.

+ + +

New Behavior

+ + +

The server can be asked to:

+ +
    +
  1. Display some other text, instead of the NCSA hard coded + messages, or
    2. + +
  2. redirect to a local URL, or
    3. + +
  3. redirect to an external URL.
    4. +
+ +

Redirecting to another URL can be useful, but only if some + information can be passed which can then be used to explain and/or log + the error/problem more clearly.

+ +

To achieve this, Apache will define new CGI-like environment + variables:

+ +

+ REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap, + image/jpeg
+ REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX A.09.05 + 9000/712)
+ REDIRECT_PATH=.:/bin:/usr/local/bin:/etc
+ REDIRECT_QUERY_STRING=
+ REDIRECT_REMOTE_ADDR=121.345.78.123
+ REDIRECT_REMOTE_HOST=ooh.ahhh.com
+ REDIRECT_SERVER_NAME=crash.bang.edu
+ REDIRECT_SERVER_PORT=80
+ REDIRECT_SERVER_SOFTWARE=Apache/0.8.15
+ REDIRECT_URL=/cgi-bin/buggy.pl +

+ +

Note the REDIRECT_ prefix.

+ +

At least REDIRECT_URL and + REDIRECT_QUERY_STRING will be passed to the + new URL (assuming it's a cgi-script or a cgi-include). The + other variables will exist only if they existed prior to + the error/problem. None of these will be + set if your ErrorDocument is an + external redirect (anything starting with a + scheme name like http:, even if it refers to the same host + as the server).

+ +
top
+
+

Configuration

+ + +

Use of ErrorDocument is enabled + for .htaccess files when the + AllowOverride is set accordingly.

+ +

Here are some examples...

+ +

+ ErrorDocument 500 /cgi-bin/crash-recover
+ ErrorDocument 500 "Sorry, our script crashed. Oh dear"
+ ErrorDocument 500 http://xxx/
+ ErrorDocument 404 /Lame_excuses/not_found.html
+ ErrorDocument 401 /Subscription/how_to_subscribe.html +

+ +

The syntax is,

+ +

+ ErrorDocument <3-digit-code> <action> +

+ +

where the action can be,

+ +
    +
  1. Text to be displayed. Prefix the text with a quote + ("). Whatever follows the quote is displayed. Note: + the (") prefix isn't displayed.
    2. + +
  2. An external URL to redirect to.
    3. + +
  3. A local URL to redirect to.
    4. +
+
top
+
+

Custom Error Responses and Redirects

+ + +

Apache's behavior to redirected URLs has been modified so + that additional environment variables are available to a + script/server-include.

+ +

Old behavior

+ + +

Standard CGI vars were made available to a script which + has been redirected to. No indication of where the + redirection came from was provided.

+ + +

New behavior

+ + +

A new batch of environment variables will be initialized + for use by a script which has been redirected to. Each new + variable will have the prefix REDIRECT_. + REDIRECT_ environment variables are created from + the CGI environment variables which existed prior to the + redirect, they are renamed with a REDIRECT_ + prefix, i.e., HTTP_USER_AGENT becomes + REDIRECT_HTTP_USER_AGENT. In addition to these + new variables, Apache will define REDIRECT_URL + and REDIRECT_STATUS to help the script trace its + origin. Both the original URL and the URL being redirected to + can be logged in the access log.

+ +

If the ErrorDocument specifies a local redirect to a CGI + script, the script should include a "Status:" + header field in its output in order to ensure the propagation + all the way back to the client of the error condition that + caused it to be invoked. For instance, a Perl ErrorDocument + script might include the following:

+ +

+ ...
+ print "Content-type: text/html\n";
+ printf "Status: %s Condition Intercepted\n", $ENV{"REDIRECT_STATUS"};
+ ... +

+ +

If the script is dedicated to handling a particular error + condition, such as 404 Not Found, it can + use the specific code and error text instead.

+ +

Note that the script must emit an appropriate + Status: header (such as 302 Found), if the + response contains a Location: header (in order to issue a + client side redirect). Otherwise the Location: header may + have no effect.

+ +
+
+

Available Languages:  en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/custom-error.html.es b/docs/manual/custom-error.html.es new file mode 100644 index 00000000..217e8cc0 --- /dev/null +++ b/docs/manual/custom-error.html.es @@ -0,0 +1,219 @@ + + + +Respuestas de error personalizadas - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

Respuestas de error personalizadas

+
+

Idiomas disponibles:  en  | + es  | + ja  | + ko 

+
+ +

Apache ofrece la posibilidad de que los webmasters puedan + configurar las respuestas que muestra el servidor Apache cuando se + producen algunos errores o problemas.

+ +

Las respuestas personalizadas pueden definirse para activarse + en caso de que el servidor detecte un error o problema.

+ +

Si un script termina de forma anormal y se produce una respuesta + "500 Server Error", esta respuesta puede ser sustituida por otro + texto de su elección o por una redirección a otra URL + (local o externa).

+
+ +
top
+
+

Comportamiento

+ + +

Comportamiento anterior

+ + +

NCSA httpd 1.3 devolvía mensajes antiguos del error o + problema encontrado que con frecuencia no tenían + significado alguno para el usuario, y que no incluían en + los logs información que diera pistas sobre las causas de + lo sucedido.

+ + +

Comportamiento actual

+ + +

Se puede hacer que el servidor siga uno de los siguientes + comportamientos:

+ +
    +
  1. Desplegar un texto diferente, en lugar de los mensajes de + la NCSA, o
    2. + +
  2. redireccionar la petición a una URL local, o
    3. + +
  3. redireccionar la petición a una URL externa.
    4. +
+ +

Redireccionar a otra URL puede resultar de utilidad, pero + solo si con ello se puede también pasar alguna + información que pueda explicar el error o problema y/o + registrarlo en el log correspondiente más claramente.

+ +

Para conseguir esto, Apache define ahora variables de entorno + similares a las de los CGI:

+ +

+ REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap, + image/jpeg
+ REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX A.09.05 + 9000/712)
+ REDIRECT_PATH=.:/bin:/usr/local/bin:/etc
+ REDIRECT_QUERY_STRING=
+ REDIRECT_REMOTE_ADDR=121.345.78.123
+ REDIRECT_REMOTE_HOST=ooh.ahhh.com
+ REDIRECT_SERVER_NAME=crash.bang.edu
+ REDIRECT_SERVER_PORT=80
+ REDIRECT_SERVER_SOFTWARE=Apache/0.8.15
+ REDIRECT_URL=/cgi-bin/buggy.pl +

+ +

Tenga en cuenta el prefijo REDIRECT_.

+ +

Al menos REDIRECT_URL y + REDIRECT_QUERY_STRING se pasarán a la nueva + URL (asumiendo que es un cgi-script o un cgi-include). Las otras + variables existirán solo si existían antes de aparecer + el error o problema. Ninguna de estas variables + se creará si en la directiva ErrorDocument ha especificado una + redirección externa (cualquier cosa que empiece + por un nombre de esquema del tipo http:, incluso si + se refiere al mismo servidor).

+ +
top
+
+

Configuración

+ + +

El uso de ErrorDocument + está activado para los ficheros .htaccess cuando AllowOverride tiene el valor + adecuado.

+ +

Aquí hay algunos ejemplos más...

+ +

+ ErrorDocument 500 /cgi-bin/crash-recover
+ ErrorDocument 500 "Sorry, our script crashed. Oh dear"
+ ErrorDocument 500 http://xxx/
+ ErrorDocument 404 /Lame_excuses/not_found.html
+ ErrorDocument 401 /Subscription/how_to_subscribe.html +

+ +

La sintaxis es,

+ +

+ ErrorDocument <3-digit-code> <action> +

+ +

donde action puede ser,

+ +
    +
  1. Texto a mostrar. Ponga antes del texto que quiere que se + muestre unas comillas ("). Lo que sea que siga a las comillas se + mostrará. Nota: las comillas (") no se + muestran.
    2. + +
  2. Una URL local a la que se redireccionará la + petición.
    3. + +
  3. Una URL externa a la que se redireccionará la + petición.
    4. +
+
top
+
+

Mesajes de error personalizados y redirecciones

+ + +

El comportamiento de Apache en cuanto a las redirecciones ha + cambiado para que puedan usarse más variables de entorno con + los script/server-include.

+ +

Antiguo comportamiento

+ + +

Las variables CGI estándar estaban disponibles para el + script al que se hacía la redirección. No se incluía + ninguna indicación sobre la precedencia de la + redirección.

+ + +

Nuevo comportamiento

+ + +

Un nuevo grupo de variables de entorno se inicializa para que + las use el script al que ha sido redireccionado. Cada + nueva variable tendrá el prefijo REDIRECT_. + Las variables de entorno REDIRECT_ se crean a + partir de de las variables de entorno CGI que existen antes de + la redirección, se les cambia el nombre + añadiéndoles el prefijo REDIRECT_, por + ejemplo, HTTP_USER_AGENT pasa a ser + REDIRECT_HTTP_USER_AGENT. Además, para esas + nuevas variables, Apache definirá REDIRECT_URL + y REDIRECT_STATUS para ayudar al script a seguir su + origen. Tanto la URL original como la URL a la que es redirigida + la petición pueden almacenarse en los logs de acceso.

+ +

Si ErrorDocument especifica una redirección local a un + script CGI, el script debe incluir una campo de cabeceraa + "Status:" en el resultado final para asegurar que + es posible hacer llegar al cliente de vuelta la condición + de error que lo provocó. Por ejemplo, un script en Perl + para usar con ErrorDocument podría incluir lo + siguiente:

+ +

+ ...
+ print "Content-type: text/html\n";
+ printf "Status: %s Condition Intercepted\n", $ENV{"REDIRECT_STATUS"};
+ ... +

+ +

Si el script tiene como fin tratar una determinada + condición de error, por ejemplo + 404 Not Found, se pueden usar los + códigos de error y textos específicos en su lugar.

+ +

Tenga en cuenta que el script debe incluir un campo + de cabecera Status: apropiado (como + 302 Found), si la respuesta contiene un campo de + cabecera Location: (para poder enviar una + redirección que se interprete en el cliente). De otra + manera, la cabecera + Location: puede que no tenga efecto.

+ +
+
+

Idiomas disponibles:  en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/custom-error.html.ja.euc-jp b/docs/manual/custom-error.html.ja.euc-jp new file mode 100644 index 00000000..7ea2a168 --- /dev/null +++ b/docs/manual/custom-error.html.ja.euc-jp @@ -0,0 +1,197 @@ + + + +¥«¥¹¥¿¥à¥¨¥é¡¼¥ì¥¹¥Ý¥ó¥¹ - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥«¥¹¥¿¥à¥¨¥é¡¼¥ì¥¹¥Ý¥ó¥¹

+
+

Available Languages:  en  | + es  | + ja  | + ko 

+
+ +

¥¦¥§¥Ö¥Þ¥¹¥¿¡¼¤¬²¿¤é¤«¤Î¥¨¥é¡¼¤äÌäÂê¤ËÂФ¹¤ë + Apache ¤ÎÈ¿±þ¤òÀßÄê¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ëÄɲõ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£

+ +

¥µ¡¼¥Ð¤¬¥¨¥é¡¼¤äÌäÂê¤òȯ¸«¤·¤¿¾ì¹ç¤ÎÈ¿±þ¤ò¡¢ + ¥«¥¹¥¿¥Þ¥¤¥º¤·¤ÆÄêµÁ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¥¹¥¯¥ê¥×¥È¤Î¼Â¹Ô¤¬¼ºÇÔ¤·¤Æ "500 Server Error" + ¤òȯÀ¸¤µ¤»¤¿¤È¤·¤Þ¤¹¡£¤³¤Î¾ì¹ç¤ÎÈ¿±þ¤ò¡¢¤è¤ê¹¥¤Þ¤·¤¤¥Æ¥­¥¹¥È¤ä¡¢Ê̤Π+ URL (ÆâÉôµÚ¤Ó³°Éô) ¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥·¥ç¥ó¤ËÃÖ¤­´¹¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +

+
+ +
top
+
+

Æ°ºî

+ + +

¸Å¤¤Æ°ºî

+ + +

NCSA httpd 1.3 ¤Ï¡¢¸Å¤¯¤ÆÂà¶þ¤Ê¥¨¥é¡¼/ÌäÂê¥á¥Ã¥»¡¼¥¸¤ò + ÊÖ¤·¤Æ¤¤¤Þ¤·¤¿¡£¤½¤ì¤Ï¤·¤Ð¤·¤Ð¥æ¡¼¥¶¤Ë¤Ï̵°ÕÌ£¤Ç¤¢¤ê¡¢ + ¤Þ¤¿¤½¤ì¤òȯÀ¸¤µ¤»¤¿¸¶°ø¤òµ­Ï¿¤¹¤ëÊýË¡¤âÄ󶡤·¤Æ¤¤¤Þ¤»¤ó¤Ç¤·¤¿¡£

+ + +

¿·¤·¤¤Æ°ºî

+ + +
    +
  1. NCSA ¤Î¥Ï¡¼¥É¥³¡¼¥É¤µ¤ì¤¿¥á¥Ã¥»¡¼¥¸¤ÎÂå¤ï¤ê¤Ë + ¾¤Î¥Æ¥­¥¹¥È¤òɽ¼¨
    2. + +
  2. ¥í¡¼¥«¥ë¤Î URL ¤Ë¥ê¥À¥¤¥ì¥¯¥È
    3. + +
  3. ³°Éô¤Î URL ¤Ë¥ê¥À¥¤¥ì¥¯¥È
    4. +
+ +

¤¹¤ë¤è¤¦¤Ë¥µ¡¼¥Ð¤òÀßÄê¤Ç¤­¤Þ¤¹¡£

+ +

Ê̤ΠURL ¤Ë¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤³¤È¤ÏÌò¤ËΩ¤Á¤Þ¤¹¤¬¡¢ + ¤½¤ì¤ÏÀâÌÀ¤ò¤·¤¿¤ê¡¢¤è¤êÌÀ³Î¤Ë¸í¤ê/ÌäÂê¤òµ­Ï¿¤·¤¿¤ê¤¹¤ë¤¿¤á¤Ë + ²¿¤«¾ðÊó¤òÅÁ¤¨¤é¤ì¤ë¤È¤­¤Ë¸Â¤ê¤Þ¤¹¡£

+ +

¤³¤ì¤ò¼Â¸½¤¹¤ë¤¿¤á¤Ë¡¢ Apache ¤Ï¿·¤·¤¯ CGI ¤Î¤è¤¦¤Ê´Ä¶­ÊÑ¿ô¤ò + ÄêµÁ¤·¤Þ¤¹:

+ +

+ REDIRECT_HTTP_ACCEPT=*/*, image/gif, + image/x-xbitmap, image/jpeg
+ REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX + A.09.05 9000/712)
+ REDIRECT_PATH=.:/bin:/usr/local/bin:/etc
+ REDIRECT_QUERY_STRING=
+ REDIRECT_REMOTE_ADDR=121.345.78.123
+ REDIRECT_REMOTE_HOST=ooh.ahhh.com
+ REDIRECT_SERVER_NAME=crash.bang.edu
+ REDIRECT_SERVER_PORT=80
+ REDIRECT_SERVER_SOFTWARE=Apache/0.8.15
+ REDIRECT_URL=/cgi-bin/buggy.pl +

+ +

Ƭ¤ËÉÕ¤¯ REDIRECT_ ¤ËÃíÌܤ·¤Æ¤¯¤À¤µ¤¤¡£

+ +

¾¯¤Ê¤¯¤È¤â REDIRECT_URL ¤È + REDIRECT_QUERY_STRING ¤Ï¿·¤·¤¤ URL (CGI ¥¹¥¯¥ê¥×¥È¤« + CGI ¥¤¥ó¥¯¥ë¡¼¥É¤Ç¤¢¤ë¤È²¾Äꤵ¤ì¤Þ¤¹) ¤ËÅϤµ¤ì¤Þ¤¹¡£ + ¾¤ÎÊÑ¿ô¤Ï¡¢¥¨¥é¡¼¤äÌäÂ꤬µ¯¤­¤ëÁ°¤Ë¸ºß¤·¤¿¾ì¹ç¤Ë¤À¤±Â¸ºß¤·¤Þ¤¹¡£ + ¤â¤·¤¢¤Ê¤¿¤ÎÀßÄꤷ¤¿ ErrorDocument ¤¬ ³°Éô¥ê¥À¥¤¥ì¥¯¥È + (¤¹¤Ê¤ï¤Á¡¢http: + ¤Î¤è¤¦¤ÊÂηÏ̾¤«¤é»Ï¤Þ¤ë¤¹¤Ù¤Æ¤Î¤â¤Î¡£¤¿¤È¤¨Æ±¤¸¥Û¥¹¥È¤ò»Ø¤·¤Æ¤¤¤Æ¤â) + ¤Ê¤é¤Ð¡¢¤³¤ì¤é¤Ï¤Þ¤Ã¤¿¤¯ÀßÄꤵ¤ì¤Þ¤»¤ó¡£

+ +
top
+
+

ÀßÄê

+ + +

AllowOverride ¤¬Å¬ÀÚ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢ + .htaccess ¥Õ¥¡¥¤¥ë¤Ç ErrorDocument + ¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤³¤Ë¡¢¤¤¤¯¤Ä¤«¤ÎÎã¤òµó¤²¤Þ¤¹¡£

+ +

+ ErrorDocument 500 /cgi-bin/crash-recover
+ ErrorDocument 500 "Sorry, our script crashed. Oh dear"
+ ErrorDocument 500 http://xxx/
+ ErrorDocument 404 /Lame_excuses/not_found.html
+ ErrorDocument 401 /Subscription/how_to_subscribe.html +

+ +

¹½Ê¸

+ +

+ ErrorDocument <3-digit-code> <action> +

+ +

action (Æ°ºî) ¤Ï¡¢

+ +
    +
  1. ɽ¼¨¤µ¤ì¤ë¤Ù¤­¥Æ¥­¥¹¥È¡£¥Æ¥­¥¹¥È¤Ë¤Ï°úÍÑÉä (") ¤ò¤Ä¤±¤Þ¤¹¡£ + °úÍÑÉä¤Î¸å¤Ë³¤¯¤â¤Î¤¬²¿¤Ç¤âɽ¼¨¤µ¤ì¤Þ¤¹¡£ + Ãí°Õ : (") ¤Ïɽ¼¨¤µ¤ì¤Þ¤»¤ó
    2. + +
  2. ¥ê¥À¥¤¥ì¥¯¥ÈÀè¤Î³°Éô URL
    3. + +
  3. ¥ê¥À¥¤¥ì¥¯¥ÈÀè¤Î¥í¡¼¥«¥ë URL
    4. +
+
top
+
+

¥«¥¹¥¿¥à¥¨¥é¡¼¥ì¥¹¥Ý¥ó¥¹¤È¥ê¥À¥¤¥ì¥¯¥È

+ + +

¥¹¥¯¥ê¥×¥È/SSI ¤ËÄɲäδĶ­ÊÑ¿ô¤¬ÍøÍѲÄǽ¤Ë¤Ê¤ë¤è¤¦¤Ë¡¢ + ¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤¿ URL ¤ËÂФ¹¤ë Apache ¤ÎÆ°ºî¤¬Êѹ¹¤µ¤ì¤Þ¤·¤¿¡£

+ +

¸Å¤¤Æ°ºî

+ + +

¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤¿¥¹¥¯¥ê¥×¥È¤Ïɸ½à¤Î CGI + ´Ä¶­ÊÑ¿ô¤òÍøÍѲÄǽ¤Ç¤·¤¿¡£¤·¤«¤·¡¢¤É¤³¤«¤é¥ê¥À¥¤¥ì¥¯¥È + ¤µ¤ì¤¿¤«¤Î¾ðÊó¤ÏÄ󶡤µ¤ì¤Æ¤¤¤Þ¤»¤ó¤Ç¤·¤¿¡£

+ + +

¿·¤·¤¤Æ°ºî

+ + +

¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤¿Àè¤Î¥¹¥¯¥ê¥×¥È¤¬»ÈÍѲÄǽ¤Ê¤è¤¦¤Ë¡¢ + ¿·¤·¤¤¤¿¤¯¤µ¤ó¤Î´Ä¶­ÊÑ¿ô¤¬½é´ü²½¤µ¤ì¤Þ¤¹¡£¿·¤·¤¤ÊÑ¿ô¤Ï¡¢¤½¤ì¤¾¤ì + REDIRECT_ ¤Ç»Ï¤Þ¤ê¤Þ¤¹¡£ + REDIRECT_ ¤Ç»Ï¤Þ¤ë´Ä¶­ÊÑ¿ô¤Ï¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤ëÁ°¤Ë¸ºß¤·¤Æ¤¤¤¿ + CGI ´Ä¶­ÊÑ¿ô¤ÎƬ¤Ë REDIRECT_ ¤òÉÕ¤±¤ÆºîÀ®¤µ¤ì¤Þ¤¹¡£ + ¤¹¤Ê¤ï¤Á¡¢HTTP_USER_AGENT ¤Ï + REDIRECT_HTTP_USER_AGENT ¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ì¤é¤Î¿·¤·¤¤ÊÑ¿ô¤Ë²Ã¤¨¤Æ¡¢Apache ¤Ï¡¢ + ¥¹¥¯¥ê¥×¥È¤¬¥ê¥À¥¤¥ì¥¯¥È¸µ¤Î¥È¥ì¡¼¥¹¤ò½õ¤±¤ë¤¿¤á¤Ë + REDIRECT_URL ¤È REDIRECT_STATUS + ¤òÄêµÁ¤·¤Þ¤¹¡£¥¢¥¯¥»¥¹¥í¥°¤Ë¤Ï¸µ¤Î URL ¤È¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤¿ URL + ¤ÎξÊý¤¬µ­Ï¿¤µ¤ì¤Þ¤¹¡£

+ +

ErrorDocument ¤¬ CGI ¥¹¥¯¥ê¥×¥È¤Ø¤Î¥í¡¼¥«¥ë¥ê¥À¥¤¥ì¥¯¥È¤ò + »ØÄꤷ¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢¤½¤ì¤òµ¯Æ°¤¹¤ë¤³¤È¤Ë¤Ê¤Ã¤¿¥¨¥é¡¼¤Î¾õÂÖ¤ò + ¥¯¥é¥¤¥¢¥ó¥È¤Þ¤Ç³Î¼Â¤ËÅÁ¤¨¤ë¤¿¤á¤Ë "Status:" + ¥Ø¥Ã¥À¤ò´Þ¤à¤Ù¤­¤Ç¤¹¡£Î㤨¤Ð¡¢ErrorDocument ÍѤΠPerl + ¥¹¥¯¥ê¥×¥È¤Ï°Ê²¼¤Î¤è¤¦¤Ê¤â¤Î¤ò´Þ¤à¤«¤â¤·¤ì¤Þ¤»¤ó¡£ +

+ +

+ ...
+ print "Content-type: text/html\n";
+ printf "Status: %s Condition Intercepted\n", $ENV{"REDIRECT_STATUS"};
+ ... +

+ +

¥¹¥¯¥ê¥×¥È¤¬ 404 Not Found ¤Î¤è¤¦¤Ê + ÆÃÄê¤Î¥¨¥é¡¼¥³¥ó¥Ç¥£¥·¥ç¥ó¤ò°·¤¦¤¿¤á¤À¤±¤Ë»È¤ï¤ì¤ë¾ì¹ç¤Ï¡¢ + Âå¤ï¤ê¤ËÆÃÄê¤Î¥³¡¼¥É¤È¥¨¥é¡¼¥Æ¥­¥¹¥È¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +
+
+

Available Languages:  en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/custom-error.html.ko.euc-kr b/docs/manual/custom-error.html.ko.euc-kr new file mode 100644 index 00000000..98341ad9 --- /dev/null +++ b/docs/manual/custom-error.html.ko.euc-kr @@ -0,0 +1,198 @@ + + + +»ç¿ëÀÚÁ¤ÀÇ ¿À·ù ÀÀ´ä - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

»ç¿ëÀÚÁ¤ÀÇ ¿À·ù ÀÀ´ä

+
+

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

+
+ +

À¥¸¶½ºÅÍ´Â ¿À·ù³ª ¹®Á¦°¡ ¹ß»ýÇßÀ»¶§ ¾ÆÆÄÄ¡ÀÇ ÀÀ´äÀ» + ¼³Á¤ÇÒ ¼ö ÀÖ´Ù.

+ +

¼­¹ö°¡ ¿À·ù³ª ¹®Á¦¸¦ ¹ß°ßÇßÀ»¶§ º¸³¾ »ç¿ëÀÚÁ¤ÀÇ ÀÀ´äÀ» + Á¤ÀÇÇÒ ¼ö ÀÖ´Ù.

+ +

½ºÅ©¸³Æ®°¡ Á×Àº °æ¿ì "500 Server Error" ÀÀ´ä ´ë½Å »ç¿ëÀÚ¿¡°Ô + ´õ Ä£±ÙÇÑ ¹®±¸¸¦ »ç¿ëÇϰųª ´Ù¸¥ (°°Àº »çÀÌÆ®³ª ¿ÜºÎ »çÀÌÆ®ÀÇ) + URL·Î ¸®´ÙÀÌ·º¼ÇÀ» ÇÒ ¼ö ÀÖ´Ù.

+
+ +
top
+
+

Çൿ

+ + +

ÀÌÀü Çൿ

+ + +

NCSA httpd 1.3Àº »ç¿ëÀÚ¿¡°Ô ¹«ÀǹÌÇÏ°í Áö·çÇÑ ¿À·ù¹®À» + º¸³Â´Ù. ¹®Á¦°¡ ¹ß»ýÇÑ ÀÌÀ¯¸¦ ·Î±×¿¡ ³²±æ ¼öµµ ¾ø¾ú´Ù.

+ + +

»õ·Î¿î Çൿ

+ + +

¼­¹ö´Â ´ÙÀ½°ú °°Àº ÀÏÀ» ÇÒ ¼ö ÀÖ´Ù:

+ +
    +
  1. NCSAÀÇ °íÁ¤µÈ ¹®±¸ ´ë½Å ´Ù¸¥ ¹®±¸¸¦ º¸¿©Áְųª
    2. + +
  2. °°Àº »çÀÌÆ®ÀÇ URL·Î ¸®´ÙÀÌ·º¼ÇÇϰųª
    3. + +
  3. ¿ÜºÎ »çÀÌÆ®ÀÇ URL·Î ¸®´ÙÀÌ·º¼ÇÇÑ´Ù.
    4. +
+ +

´Ù¸¥ »çÀÌÆ®ÀÇ URL·Î ¸®´ÙÀÌ·º¼ÇÇÏ´Â °ÍÀÌ À¯¿ëÇÒ ¼ö ÀÖÁö¸¸, + ÀÌ °æ¿ì ¹®Á¦¸¦ ¼³¸íÇϰųª ·Î±×Çϴµ¥ ÇÊ¿äÇÑ Á¤º¸Áß ÀϺθ¸ + Àü´ÞµÈ´Ù.

+ +

¿À·ù¿¡ ´ëÇÑ Á¤º¸¸¦ Àü´ÞÇϱâÀ§ÇØ ¾ÆÆÄÄ¡´Â CGI½ÄÀÇ »õ·Î¿î + ȯ°æº¯¼ö¸¦ Á¤ÀÇÇÑ´Ù:

+ +

+ REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap, + image/jpeg
+ REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX A.09.05 + 9000/712)
+ REDIRECT_PATH=.:/bin:/usr/local/bin:/etc
+ REDIRECT_QUERY_STRING=
+ REDIRECT_REMOTE_ADDR=121.345.78.123
+ REDIRECT_REMOTE_HOST=ooh.ahhh.com
+ REDIRECT_SERVER_NAME=crash.bang.edu
+ REDIRECT_SERVER_PORT=80
+ REDIRECT_SERVER_SOFTWARE=Apache/0.8.15
+ REDIRECT_URL=/cgi-bin/buggy.pl +

+ +

REDIRECT_ Á¢µÎ»ç¿¡ ÁÖ¸ñÇ϶ó.

+ +

ÃÖ¼ÒÇÑ REDIRECT_URL°ú + REDIRECT_QUERY_STRINGÀº (cgi-script³ª + cgi-includeÀÏ) »õ URL·Î ³Ñ°ÜÁø´Ù. ´Ù¸¥ º¯¼ö´Â ¿À·ù°¡ + ¹ß»ýÇϱâ ÀÌÀü¿¡ (¿ªÁÖ; À̸§¿¡¼­ REDIRECT_¸¦ + »« ȯ°æº¯¼ö°¡) Á¸ÀçÇÑ °æ¿ì¿¡¸¸ ÀÖ´Ù. + ErrorDocument°¡ + ¿ÜºÎ·Î (°°Àº ¼­¹ö¶óµµ http:¿Í + °°Àº ½ºÅ´(scheme)À¸·Î ½ÃÀÛÇÑ´Ù¸é) ¸®´ÙÀÌ·º¼ÇÇÑ´Ù¸é + ÀÌÁß ¾î¶² °Íµµ ¼³Á¤µÇÁö ¾Ê´Â´Ù.

+ +
top
+
+

¼³Á¤

+ + +

AllowOverride°¡ + ÀûÀýÈ÷ ¼³Á¤µÇ¾ú´Ù¸é .htaccess ÆÄÀÏ¿¡¼­ + ErrorDocument¸¦ »ç¿ëÇÒ + ¼ö ÀÖ´Ù.

+ +

´ÙÀ½Àº ¿¹ÀÌ´Ù...

+ +

+ ErrorDocument 500 /cgi-bin/crash-recover
+ ErrorDocument 500 "Sorry, our script crashed. Oh dear"
+ ErrorDocument 500 http://xxx/
+ ErrorDocument 404 /Lame_excuses/not_found.html
+ ErrorDocument 401 /Subscription/how_to_subscribe.html +

+ +

¹®¹ýÀº,

+ +

+ ErrorDocument <3-digit-code> <action> +

+ +

°¡´ÉÇÑ actionÀº,

+ +
    +
  1. Ãâ·ÂÇÒ ¹®±¸. µû¿ÈÇ¥ (")¸¦ ¹®±¸ ¾Õ¿¡ ºÙÀδÙ. µÚ¿¡ ³ª¿À´Â + µû¿ÈÇ¥´Â Ãâ·ÂµÈ´Ù. ÁÖÀÇ: ¾Õ¿¡ ºÙÀº µû¿ÈÇ¥ (")´Â Ãâ·ÂµÇÁö + ¾Ê´Â´Ù.
    2. + +
  2. ¸®´ÙÀÌ·º¼ÇÇÒ ¿ÜºÎ URL.
    3. + +
  3. ¸®´ÙÀÌ·º¼ÇÇÒ ³»ºÎ URL.
    4. +
+
top
+
+

»ç¿ëÀÚÁ¤ÀÇ ¿À·ù ÀÀ´ä°ú ¸®´ÙÀÌ·º¼Ç

+ + +

URL·Î ¸®´ÙÀÌ·º¼ÇÇÏ´Â ¾ÆÆÄÄ¡ ÇൿÀº + ½ºÅ©¸³Æ®/server-include¿¡ ȯ°æº¯¼ö¸¦ ´õ ³Ñ°ÜÁÖµµ·Ï º¯°æµÇ¾ú´Ù.

+ +

ÀÌÀü Çൿ

+ + +

¸®´ÙÀÌ·º¼ÇµÇ´Â ½ºÅ©¸³Æ®¿¡ Ç¥ÁØ CGI º¯¼öµéÀÌ ³Ñ¾î°£´Ù. + ¾îµð¿¡¼­ ¸®´ÙÀÌ·º¼ÇÀÌ ÀϾ´ÂÁö ¾Ë ¼ö ¾ø´Ù.

+ + +

»õ·Î¿î Çൿ

+ + +

¸®´ÙÀÌ·º¼ÇµÈ ½ºÅ©¸³Æ®´Â »õ·Î¿î ȯ°æº¯¼öµéÀ» »ç¿ëÇÒ + ¼ö ÀÖ´Ù. ¸ðµÎ ¾Õ¿¡ REDIRECT_°¡ ºÙ¾îÀÖ´Ù. + REDIRECT_ ȯ°æº¯¼ö´Â ¿ø·¡ CGI ȯ°æº¯¼ö¸í + ¾Õ¿¡ REDIRECT_¸¦ ºÙ¿©¼­ ¸¸µç´Ù. ¿¹¸¦ + µé¾î, HTTP_USER_AGENT´Â + REDIRECT_HTTP_USER_AGENT°¡ µÇ¾ú´Ù. ÀÌ·± º¯¼ö¿¡ + Ãß°¡·Î ½ºÅ©¸³Æ®°¡ ¿ø·¡ URLÀ» ¾Ëµµ·Ï ¾ÆÆÄÄ¡´Â + REDIRECT_URL°ú REDIRECT_STATUS¸¦ + Á¤ÀÇÇÑ´Ù. ¿ø·¡ URL°ú ¸®´ÙÀÌ·º¼ÇµÈ URL ¸ðµÎ Á¢±Ù ·Î±×¿¡ + ±â·ÏÇÒ ¼ö ÀÖ´Ù.

+ +

ErrorDocument°¡ °°Àº ¼­¹ö¿¡ ÀÖ´Â CGI ½ºÅ©¸³Æ®·Î + ¸®´ÙÀÌ·º¼ÇÇÑ´Ù¸é, ½ºÅ©¸³Æ®´Â Ŭ¶óÀ̾ðÆ®¿¡°Ô ¿À·ù »óȲÀ» + È®½ÇÈ÷ Àü´ÞÇϱâÀ§ÇØ Ãâ·Â¿¡ "Status:" Çì´õ + Çʵ带 Æ÷ÇÔÇØ¾ß ÇÑ´Ù. ¿¹¸¦ µé¾î, Perl·Î ÀÛ¼ºÇÑ ErrorDocument + ½ºÅ©¸³Æ®´Â ´ÙÀ½°ú °°´Ù:

+ +

+ ...
+ print "Content-type: text/html\n";
+ printf "Status: %s Condition Intercepted\n", $ENV{"REDIRECT_STATUS"};
+ ... +

+ +

404 Not Found¿Í °°Àº ƯÁ¤ ¿À·ù + »óȲ¿¡ ´ëÇÑ ½ºÅ©¸³Æ®¶ó¸é, ´ë½Å (¿ªÁÖ; °íÁ¤µÈ) + ƯÁ¤ »óÅÂÄÚµå¿Í ¿À·ù¹®À» »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

(Ŭ¶óÀ̾ðÆ®¿¡°Ô ¸®´ÙÀÌ·º¼ÇÀ» ¿äûÇϱâÀ§ÇØ) ÀÀ´ä¿¡ + Location: Çì´õ¸¦ Æ÷ÇÔÇÑ´Ù¸é, ½ºÅ©¸³Æ®´Â + ¹Ýµå½Ã (302 Found °°Àº) ÀûÀýÇÑ + Status: Çì´õ¸¦ Ãâ·ÂÇØ¾ß ÇÔÀ» ÁÖÀÇÇ϶ó. ±×·¸Áö¾ÊÀ¸¸é + Location: Çì´õ°¡ ¾Æ¹« ¼Ò¿ë¾ø°Ô µÉ ¼ö ÀÖ´Ù.

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/developer/API.html b/docs/manual/developer/API.html new file mode 100644 index 00000000..a8a3c492 --- /dev/null +++ b/docs/manual/developer/API.html @@ -0,0 +1,3 @@ +URI: API.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/developer/API.html.en b/docs/manual/developer/API.html.en new file mode 100644 index 00000000..25db7a17 --- /dev/null +++ b/docs/manual/developer/API.html.en @@ -0,0 +1,1222 @@ + + + +Apache 1.3 API notes - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation

Apache 1.3 API notes

+
+

Available Languages:  en 

+
+ +

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.

+
+ +

These are some notes on the Apache API and the data structures you have + to deal with, etc. They are not yet nearly complete, but hopefully, + they will help you get your bearings. Keep in mind that the API is still + subject to change as we gain experience with it. (See the TODO file for + what might be coming). However, it will be easy to adapt modules + to any changes that are made. (We have more modules to adapt than you + do).

+ +

A few notes on general pedagogical style here. In the interest of + conciseness, all structure declarations here are incomplete -- the real + ones have more slots that I'm not telling you about. For the most part, + these are reserved to one component of the server core or another, and + should be altered by modules with caution. However, in some cases, they + really are things I just haven't gotten around to yet. Welcome to the + bleeding edge.

+ +

Finally, here's an outline, to give you some bare idea of what's coming + up, and in what order:

+ + +
+ +
top
+
+

Basic concepts

+

We begin with an overview of the basic concepts behind the API, and how + they are manifested in the code.

+ +

Handlers, Modules, and Requests

+

Apache breaks down request handling into a series of steps, more or + less the same way the Netscape server API does (although this API has a + few more stages than NetSite does, as hooks for stuff I thought might be + useful in the future). These are:

+ +
    +
  • URI -> Filename translation
    • +
  • Auth ID checking [is the user who they say they are?]
    • +
  • Auth access checking [is the user authorized here?]
    • +
  • Access checking other than auth
    • +
  • Determining MIME type of the object requested
    • +
  • `Fixups' -- there aren't any of these yet, but the phase is intended + as a hook for possible extensions like SetEnv, which don't really fit well elsewhere.
    • +
  • Actually sending a response back to the client.
    • +
  • Logging the request
    • +
+ +

These phases are handled by looking at each of a succession of + modules, looking to see if each of them has a handler for the + phase, and attempting invoking it if so. The handler can typically do one + of three things:

+ +
    +
  • Handle the request, and indicate that it has done so by + returning the magic constant OK.
    • + +
  • Decline to handle the request, by returning the magic integer + constant DECLINED. In this case, the server behaves in all + respects as if the handler simply hadn't been there.
    • + +
  • Signal an error, by returning one of the HTTP error codes. This + terminates normal handling of the request, although an ErrorDocument may + be invoked to try to mop up, and it will be logged in any case.
    • +
+ +

Most phases are terminated by the first module that handles them; + however, for logging, `fixups', and non-access authentication checking, + all handlers always run (barring an error). Also, the response phase is + unique in that modules may declare multiple handlers for it, via a + dispatch table keyed on the MIME type of the requested object. Modules may + declare a response-phase handler which can handle any request, + by giving it the key */* (i.e., a wildcard MIME type + specification). However, wildcard handlers are only invoked if the server + has already tried and failed to find a more specific response handler for + the MIME type of the requested object (either none existed, or they all + declined).

+ +

The handlers themselves are functions of one argument (a + request_rec structure. vide infra), which returns an integer, + as above.

+ + +

A brief tour of a module

+

At this point, we need to explain the structure of a module. Our + candidate will be one of the messier ones, the CGI module -- this handles + both CGI scripts and the ScriptAlias config file command. It's actually a great deal + more complicated than most modules, but if we're going to have only one + example, it might as well be the one with its fingers in every place.

+ +

Let's begin with handlers. In order to handle the CGI scripts, the + module declares a response handler for them. Because of ScriptAlias, it also has handlers for the + name translation phase (to recognize ScriptAliased URIs), the type-checking phase (any + ScriptAliased request is typed + as a CGI script).

+ +

The module needs to maintain some per (virtual) server information, + namely, the ScriptAliases in + effect; the module structure therefore contains pointers to a functions + which builds these structures, and to another which combines two of them + (in case the main server and a virtual server both have ScriptAliases declared).

+ +

Finally, this module contains code to handle the ScriptAlias command itself. This particular + module only declares one command, but there could be more, so modules have + command tables which declare their commands, and describe where + they are permitted, and how they are to be invoked.

+ +

A final note on the declared types of the arguments of some of these + commands: a pool is a pointer to a resource pool + structure; these are used by the server to keep track of the memory which + has been allocated, files opened, etc., either to service a + particular request, or to handle the process of configuring itself. That + way, when the request is over (or, for the configuration pool, when the + server is restarting), the memory can be freed, and the files closed, + en masse, without anyone having to write explicit code to track + them all down and dispose of them. Also, a cmd_parms + structure contains various information about the config file being read, + and other status information, which is sometimes of use to the function + which processes a config-file command (such as ScriptAlias). With no further ado, the + module itself:

+ +

+ /* Declarations of handlers. */
+
+ int translate_scriptalias (request_rec *);
+ int type_scriptalias (request_rec *);
+ int cgi_handler (request_rec *);
+
+ /* Subsidiary dispatch table for response-phase
+  * handlers, by MIME type */
+
+ handler_rec cgi_handlers[] = {
+ + { "application/x-httpd-cgi", cgi_handler },
+ { NULL }
+ + };
+
+ /* Declarations of routines to manipulate the
+  * module's configuration info. Note that these are
+  * returned, and passed in, as void *'s; the server
+  * core keeps track of them, but it doesn't, and can't,
+  * know their internal structure.
+  */
+
+ void *make_cgi_server_config (pool *);
+ void *merge_cgi_server_config (pool *, void *, void *);
+
+ /* Declarations of routines to handle config-file commands */
+
+ extern char *script_alias(cmd_parms *, void *per_dir_config, char *fake, + char *real);
+
+ command_rec cgi_cmds[] = {
+ + { "ScriptAlias", script_alias, NULL, RSRC_CONF, TAKE2,
+ "a fakename and a realname"},
 + { NULL }
+ + };
+
+ module cgi_module = { +

  STANDARD_MODULE_STUFF,
+  NULL,                     /* initializer */
+  NULL,                     /* dir config creator */
+  NULL,                     /* dir merger */
+  make_cgi_server_config,   /* server config */
+  merge_cgi_server_config,  /* merge server config */
+  cgi_cmds,                 /* command table */
+  cgi_handlers,             /* handlers */
+  translate_scriptalias,    /* filename translation */
+  NULL,                     /* check_user_id */
+  NULL,                     /* check auth */
+  NULL,                     /* check access */
+  type_scriptalias,         /* type_checker */
+  NULL,                     /* fixups */
+  NULL,                     /* logger */
+  NULL                      /* header parser */
+};
+ +
top
+
+

How handlers work

+

The sole argument to handlers is a request_rec structure. + This structure describes a particular request which has been made to the + server, on behalf of a client. In most cases, each connection to the + client generates only one request_rec structure.

+ +

A brief tour of the request_rec

+

The request_rec contains pointers to a resource pool + which will be cleared when the server is finished handling the request; + to structures containing per-server and per-connection information, and + most importantly, information on the request itself.

+ +

The most important such information is a small set of character strings + describing attributes of the object being requested, including its URI, + filename, content-type and content-encoding (these being filled in by the + translation and type-check handlers which handle the request, + respectively).

+ +

Other commonly used data items are tables giving the MIME headers on + the client's original request, MIME headers to be sent back with the + response (which modules can add to at will), and environment variables for + any subprocesses which are spawned off in the course of servicing the + request. These tables are manipulated using the ap_table_get + and ap_table_set routines.

+ +
+

Note that the Content-type header value cannot + be set by module content-handlers using the ap_table_*() + routines. Rather, it is set by pointing the content_type + field in the request_rec structure to an appropriate + string. e.g.,

+

+ r->content_type = "text/html"; +

+
+ +

Finally, there are pointers to two data structures which, in turn, + point to per-module configuration structures. Specifically, these hold + pointers to the data structures which the module has built to describe + the way it has been configured to operate in a given directory (via + .htaccess files or <Directory> sections), for private data it has built in the + course of servicing the request (so modules' handlers for one phase can + pass `notes' to their handlers for other phases). There is another such + configuration vector in the server_rec data structure pointed + to by the request_rec, which contains per (virtual) server + configuration data.

+ +

Here is an abridged declaration, giving the fields most commonly + used:

+ +

+ struct request_rec {
+
+ pool *pool;
+ conn_rec *connection;
+ server_rec *server;
+
+ /* What object is being requested */
+
+ char *uri;
+ char *filename;
+ char *path_info; +

char *args;           /* QUERY_ARGS, if any */
+struct stat finfo;    /* Set by server core;
+                       * st_mode set to zero if no such file */

+ char *content_type;
+ char *content_encoding;
+
+ /* MIME header environments, in and out. Also,
+  * an array containing environment variables to
+  * be passed to subprocesses, so people can write
+  * modules to add to that environment.
+  *
+  * The difference between headers_out and
+  * err_headers_out is that the latter are printed
+  * even on error, and persist across internal
+  * redirects (so the headers printed for
+  * ErrorDocument handlers will have + them).
+  */
+
+ table *headers_in;
+ table *headers_out;
+ table *err_headers_out;
+ table *subprocess_env;
+
+ /* Info about the request itself... */
+
+

int header_only;     /* HEAD request, as opposed to GET */
+char *protocol;      /* Protocol, as given to us, or HTTP/0.9 */
+char *method;        /* GET, HEAD, POST, etc. */
+int method_number;   /* M_GET, M_POST, etc. */
+
+

+ /* Info for logging */
+
+ char *the_request;
+ int bytes_sent;
+
+ /* A flag which modules can set, to indicate that
+  * the data being returned is volatile, and clients
+  * should be told not to cache it.
+  */
+
+ int no_cache;
+
+ /* Various other config info which may change
+  * with .htaccess files
+  * These are config vectors, with one void*
+  * pointer for each module (the thing pointed
+  * to being the module's business).
+  */
+
+

void *per_dir_config;   /* Options set in config files, etc. */
+void *request_config;   /* Notes on *this* request */

+
+ }; +

+ + +

Where request_rec structures come from

+

Most request_rec structures are built by reading an HTTP + request from a client, and filling in the fields. However, there are a + few exceptions:

+ +
    +
  • If the request is to an imagemap, a type map (i.e., a + *.var file), or a CGI script which returned a local + `Location:', then the resource which the user requested is going to be + ultimately located by some URI other than what the client originally + supplied. In this case, the server does an internal redirect, + constructing a new request_rec for the new URI, and + processing it almost exactly as if the client had requested the new URI + directly.
    • + +
  • If some handler signaled an error, and an ErrorDocument + is in scope, the same internal redirect machinery comes into play.
    • + +

  • Finally, a handler occasionally needs to investigate `what would + happen if' some other request were run. For instance, the directory + indexing module needs to know what MIME type would be assigned to a + request for each directory entry, in order to figure out what icon to + use.

    + +

    Such handlers can construct a sub-request, using the + functions ap_sub_req_lookup_file, + ap_sub_req_lookup_uri, and ap_sub_req_method_uri; + these construct a new request_rec structure and processes it + as you would expect, up to but not including the point of actually sending + a response. (These functions skip over the access checks if the + sub-request is for a file in the same directory as the original + request).

    + +

    (Server-side includes work by building sub-requests and then actually + invoking the response handler for them, via the function + ap_run_sub_req).

    +
    • +
+ + +

Handling requests, declining, and returning + error codes

+

As discussed above, each handler, when invoked to handle a particular + request_rec, has to return an int to indicate + what happened. That can either be

+ +
    +
  • OK -- the request was handled successfully. This may or + may not terminate the phase.
    • + +
  • DECLINED -- no erroneous condition exists, but the module + declines to handle the phase; the server tries to find another.
    • + +
  • an HTTP error code, which aborts handling of the request.
    • +
+ +

Note that if the error code returned is REDIRECT, then + the module should put a Location in the request's + headers_out, to indicate where the client should be + redirected to.

+ + +

Special considerations for response + handlers

+

Handlers for most phases do their work by simply setting a few fields + in the request_rec structure (or, in the case of access + checkers, simply by returning the correct error code). However, response + handlers have to actually send a request back to the client.

+ +

They should begin by sending an HTTP response header, using the + function ap_send_http_header. (You don't have to do anything + special to skip sending the header for HTTP/0.9 requests; the function + figures out on its own that it shouldn't do anything). If the request is + marked header_only, that's all they should do; they should + return after that, without attempting any further output.

+ +

Otherwise, they should produce a request body which responds to the + client as appropriate. The primitives for this are ap_rputc + and ap_rprintf, for internally generated output, and + ap_send_fd, to copy the contents of some FILE * + straight to the client.

+ +

At this point, you should more or less understand the following piece + of code, which is the handler which handles GET requests + which have no more specific handler; it also shows how conditional + GETs can be handled, if it's desirable to do so in a + particular response handler -- ap_set_last_modified checks + against the If-modified-since value supplied by the client, + if any, and returns an appropriate code (which will, if nonzero, be + USE_LOCAL_COPY). No similar considerations apply for + ap_set_content_length, but it returns an error code for + symmetry.

+ +

+ int default_handler (request_rec *r)
+ {
+ + int errstatus;
+ FILE *f;
+
+ if (r->method_number != M_GET) return DECLINED;
+ if (r->finfo.st_mode == 0) return NOT_FOUND;
+
+ if ((errstatus = ap_set_content_length (r, r->finfo.st_size))
+     || + (errstatus = ap_set_last_modified (r, r->finfo.st_mtime)))
+ return errstatus;
+
+ f = fopen (r->filename, "r");
+
+ if (f == NULL) {
+ + log_reason("file permissions deny server access", r->filename, r);
+ return FORBIDDEN;
+ + }
+
+ register_timeout ("send", r);
+ ap_send_http_header (r);
+
+ if (!r->header_only) send_fd (f, r);
+ ap_pfclose (r->pool, f);
+ return OK;
+ + } +

+ +

Finally, if all of this is too much of a challenge, there are a few + ways out of it. First off, as shown above, a response handler which has + not yet produced any output can simply return an error code, in which + case the server will automatically produce an error response. Secondly, + it can punt to some other handler by invoking + ap_internal_redirect, which is how the internal redirection + machinery discussed above is invoked. A response handler which has + internally redirected should always return OK.

+ +

(Invoking ap_internal_redirect from handlers which are + not response handlers will lead to serious confusion).

+ + +

Special considerations for authentication + handlers

+

Stuff that should be discussed here in detail:

+ +
    +
  • Authentication-phase handlers not invoked unless auth is + configured for the directory.
    • + +
  • Common auth configuration stored in the core per-dir + configuration; it has accessors ap_auth_type, + ap_auth_name, and ap_requires.
    • + +
  • Common routines, to handle the protocol end of things, at + least for HTTP basic authentication + (ap_get_basic_auth_pw, which sets the + connection->user structure field + automatically, and ap_note_basic_auth_failure, + which arranges for the proper WWW-Authenticate: + header to be sent back).
    • +
+ + +

Special considerations for logging + handlers

+

When a request has internally redirected, there is the question of + what to log. Apache handles this by bundling the entire chain of redirects + into a list of request_rec structures which are threaded + through the r->prev and r->next pointers. + The request_rec which is passed to the logging handlers in + such cases is the one which was originally built for the initial request + from the client; note that the bytes_sent field will only be + correct in the last request in the chain (the one for which a response was + actually sent).

+ +
top
+
+

Resource allocation and resource pools

+

One of the problems of writing and designing a server-pool server is + that of preventing leakage, that is, allocating resources (memory, open + files, etc.), without subsequently releasing them. The resource + pool machinery is designed to make it easy to prevent this from happening, + by allowing resource to be allocated in such a way that they are + automatically released when the server is done with them.

+ +

The way this works is as follows: the memory which is allocated, file + opened, etc., to deal with a particular request are tied to a + resource pool which is allocated for the request. The pool is a + data structure which itself tracks the resources in question.

+ +

When the request has been processed, the pool is cleared. At + that point, all the memory associated with it is released for reuse, all + files associated with it are closed, and any other clean-up functions which + are associated with the pool are run. When this is over, we can be confident + that all the resource tied to the pool have been released, and that none of + them have leaked.

+ +

Server restarts, and allocation of memory and resources for per-server + configuration, are handled in a similar way. There is a configuration + pool, which keeps track of resources which were allocated while reading + the server configuration files, and handling the commands therein (for + instance, the memory that was allocated for per-server module configuration, + log files and other files that were opened, and so forth). When the server + restarts, and has to reread the configuration files, the configuration pool + is cleared, and so the memory and file descriptors which were taken up by + reading them the last time are made available for reuse.

+ +

It should be noted that use of the pool machinery isn't generally + obligatory, except for situations like logging handlers, where you really + need to register cleanups to make sure that the log file gets closed when + the server restarts (this is most easily done by using the function ap_pfopen, which also arranges for the + underlying file descriptor to be closed before any child processes, such as + for CGI scripts, are execed), or in case you are using the + timeout machinery (which isn't yet even documented here). However, there are + two benefits to using it: resources allocated to a pool never leak (even if + you allocate a scratch string, and just forget about it); also, for memory + allocation, ap_palloc is generally faster than + malloc.

+ +

We begin here by describing how memory is allocated to pools, and then + discuss how other resources are tracked by the resource pool machinery.

+ +

Allocation of memory in pools

+

Memory is allocated to pools by calling the function + ap_palloc, which takes two arguments, one being a pointer to + a resource pool structure, and the other being the amount of memory to + allocate (in chars). Within handlers for handling requests, + the most common way of getting a resource pool structure is by looking at + the pool slot of the relevant request_rec; hence + the repeated appearance of the following idiom in module code:

+ +

+ int my_handler(request_rec *r)
+ {
+ + struct my_structure *foo;
+ ...
+
+ foo = (foo *)ap_palloc (r->pool, sizeof(my_structure));
+ + } +

+ +

Note that there is no ap_pfree -- + ap_palloced memory is freed only when the associated resource + pool is cleared. This means that ap_palloc does not have to + do as much accounting as malloc(); all it does in the typical + case is to round up the size, bump a pointer, and do a range check.

+ +

(It also raises the possibility that heavy use of + ap_palloc could cause a server process to grow excessively + large. There are two ways to deal with this, which are dealt with below; + briefly, you can use malloc, and try to be sure that all of + the memory gets explicitly freed, or you can allocate a + sub-pool of the main pool, allocate your memory in the sub-pool, and clear + it out periodically. The latter technique is discussed in the section + on sub-pools below, and is used in the directory-indexing code, in order + to avoid excessive storage allocation when listing directories with + thousands of files).

+ + +

Allocating initialized memory

+

There are functions which allocate initialized memory, and are + frequently useful. The function ap_pcalloc has the same + interface as ap_palloc, but clears out the memory it + allocates before it returns it. The function ap_pstrdup + takes a resource pool and a char * as arguments, and + allocates memory for a copy of the string the pointer points to, returning + a pointer to the copy. Finally ap_pstrcat is a varargs-style + function, which takes a pointer to a resource pool, and at least two + char * arguments, the last of which must be + NULL. It allocates enough memory to fit copies of each of + the strings, as a unit; for instance:

+ +

+ ap_pstrcat (r->pool, "foo", "/", "bar", NULL); +

+ +

returns a pointer to 8 bytes worth of memory, initialized to + "foo/bar".

+ + +

Commonly-used pools in the Apache Web + server

+

A pool is really defined by its lifetime more than anything else. + There are some static pools in http_main which are passed to various + non-http_main functions as arguments at opportune times. Here they + are:

+ +
+
permanent_pool
+
never passed to anything else, this is the ancestor of all pools
+ +
pconf
+
+
    +
  • subpool of permanent_pool
    • + +
  • created at the beginning of a config "cycle"; exists + until the server is terminated or restarts; passed to all + config-time routines, either via cmd->pool, or as the + "pool *p" argument on those which don't take pools
    • + +
  • passed to the module init() functions
    • +
+
+ +
ptemp
+
+
    +
  • sorry I lie, this pool isn't called this currently in + 1.3, I renamed it this in my pthreads development. I'm + referring to the use of ptrans in the parent... contrast + this with the later definition of ptrans in the + child.
    • + +
  • subpool of permanent_pool
    • + +
  • created at the beginning of a config "cycle"; exists + until the end of config parsing; passed to config-time + routines via cmd->temp_pool. Somewhat of a + "bastard child" because it isn't available everywhere. + Used for temporary scratch space which may be needed by + some config routines but which is deleted at the end of + config.
    • +
+
+ +
pchild
+
+
    +
  • subpool of permanent_pool
    • + +
  • created when a child is spawned (or a thread is + created); lives until that child (thread) is + destroyed
    • + +
  • passed to the module child_init functions
    • + +
  • destruction happens right after the child_exit + functions are called... (which may explain why I think + child_exit is redundant and unneeded)
    • +
+
+ +
ptrans
+
+
    +
  • should be a subpool of pchild, but currently is a + subpool of permanent_pool, see above
    • + +
  • cleared by the child before going into the accept() + loop to receive a connection
    • + +
  • used as connection->pool
    • +
+
+ +
r->pool
+
+
    +
  • for the main request this is a subpool of + connection->pool; for subrequests it is a subpool of + the parent request's pool.
    • + +
  • exists until the end of the request (i.e., + ap_destroy_sub_req, or in child_main after + process_request has finished)
    • + +
  • note that r itself is allocated from r->pool; + i.e., r->pool is first created and then r is + the first thing palloc()d from it
    • +
+
+
+ +

For almost everything folks do, r->pool is the pool to + use. But you can see how other lifetimes, such as pchild, are useful to + some modules... such as modules that need to open a database connection + once per child, and wish to clean it up when the child dies.

+ +

You can also see how some bugs have manifested themself, such as + setting connection->user to a value from + r->pool -- in this case connection exists for the + lifetime of ptrans, which is longer than + r->pool (especially if r->pool is a + subrequest!). So the correct thing to do is to allocate from + connection->pool.

+ +

And there was another interesting bug in mod_include + / mod_cgi. You'll see in those that they do this test + to decide if they should use r->pool or + r->main->pool. In this case the resource that they are + registering for cleanup is a child process. If it were registered in + r->pool, then the code would wait() for the + child when the subrequest finishes. With mod_include this + could be any old #include, and the delay can be up to 3 + seconds... and happened quite frequently. Instead the subprocess is + registered in r->main->pool which causes it to be + cleaned up when the entire request is done -- i.e., after the + output has been sent to the client and logging has happened.

+ + +

Tracking open files, etc.

+

As indicated above, resource pools are also used to track other sorts + of resources besides memory. The most common are open files. The routine + which is typically used for this is ap_pfopen, which takes a + resource pool and two strings as arguments; the strings are the same as + the typical arguments to fopen, e.g.,

+ +

+ ...
+ FILE *f = ap_pfopen (r->pool, r->filename, "r");
+
+ if (f == NULL) { ... } else { ... }
+

+ +

There is also a ap_popenf routine, which parallels the + lower-level open system call. Both of these routines arrange + for the file to be closed when the resource pool in question is + cleared.

+ +

Unlike the case for memory, there are functions to close files + allocated with ap_pfopen, and ap_popenf, namely + ap_pfclose and ap_pclosef. (This is because, on + many systems, the number of files which a single process can have open is + quite limited). It is important to use these functions to close files + allocated with ap_pfopen and ap_popenf, since to + do otherwise could cause fatal errors on systems such as Linux, which + react badly if the same FILE* is closed more than once.

+ +

(Using the close functions is not mandatory, since the + file will eventually be closed regardless, but you should consider it in + cases where your module is opening, or could open, a lot of files).

+ + +

Other sorts of resources -- cleanup functions

+

More text goes here. Describe the the cleanup primitives in terms of + which the file stuff is implemented; also, spawn_process.

+ +

Pool cleanups live until clear_pool() is called: + clear_pool(a) recursively calls destroy_pool() + on all subpools of a; then calls all the cleanups for + a; then releases all the memory for a. + destroy_pool(a) calls clear_pool(a) and then + releases the pool structure itself. i.e., + clear_pool(a) doesn't delete a, it just frees + up all the resources and you can start using it again immediately.

+ + +

Fine control -- creating and dealing with sub-pools, with + a note on sub-requests

+

On rare occasions, too-free use of ap_palloc() and the + associated primitives may result in undesirably profligate resource + allocation. You can deal with such a case by creating a sub-pool, + allocating within the sub-pool rather than the main pool, and clearing or + destroying the sub-pool, which releases the resources which were + associated with it. (This really is a rare situation; the only + case in which it comes up in the standard module set is in case of listing + directories, and then only with very large directories. + Unnecessary use of the primitives discussed here can hair up your code + quite a bit, with very little gain).

+ +

The primitive for creating a sub-pool is ap_make_sub_pool, + which takes another pool (the parent pool) as an argument. When the main + pool is cleared, the sub-pool will be destroyed. The sub-pool may also be + cleared or destroyed at any time, by calling the functions + ap_clear_pool and ap_destroy_pool, respectively. + (The difference is that ap_clear_pool frees resources + associated with the pool, while ap_destroy_pool also + deallocates the pool itself. In the former case, you can allocate new + resources within the pool, and clear it again, and so forth; in the + latter case, it is simply gone).

+ +

One final note -- sub-requests have their own resource pools, which are + sub-pools of the resource pool for the main request. The polite way to + reclaim the resources associated with a sub request which you have + allocated (using the ap_sub_req_... functions) is + ap_destroy_sub_req, which frees the resource pool. Before + calling this function, be sure to copy anything that you care about which + might be allocated in the sub-request's resource pool into someplace a + little less volatile (for instance, the filename in its + request_rec structure).

+ +

(Again, under most circumstances, you shouldn't feel obliged to call + this function; only 2K of memory or so are allocated for a typical sub + request, and it will be freed anyway when the main request pool is + cleared. It is only when you are allocating many, many sub-requests for a + single main request that you should seriously consider the + ap_destroy_... functions).

+ +
top
+
+

Configuration, commands and the like

+

One of the design goals for this server was to maintain external + compatibility with the NCSA 1.3 server --- that is, to read the same + configuration files, to process all the directives therein correctly, and + in general to be a drop-in replacement for NCSA. On the other hand, another + design goal was to move as much of the server's functionality into modules + which have as little as possible to do with the monolithic server core. The + only way to reconcile these goals is to move the handling of most commands + from the central server into the modules.

+ +

However, just giving the modules command tables is not enough to divorce + them completely from the server core. The server has to remember the + commands in order to act on them later. That involves maintaining data which + is private to the modules, and which can be either per-server, or + per-directory. Most things are per-directory, including in particular access + control and authorization information, but also information on how to + determine file types from suffixes, which can be modified by + AddType and DefaultType directives, and so forth. In general, + the governing philosophy is that anything which can be made + configurable by directory should be; per-server information is generally + used in the standard set of modules for information like + Aliases and Redirects which come into play before the + request is tied to a particular place in the underlying file system.

+ +

Another requirement for emulating the NCSA server is being able to handle + the per-directory configuration files, generally called + .htaccess files, though even in the NCSA server they can + contain directives which have nothing at all to do with access control. + Accordingly, after URI -> filename translation, but before performing any + other phase, the server walks down the directory hierarchy of the underlying + filesystem, following the translated pathname, to read any + .htaccess files which might be present. The information which + is read in then has to be merged with the applicable information + from the server's own config files (either from the <Directory> sections in + access.conf, or from defaults in srm.conf, which + actually behaves for most purposes almost exactly like <Directory + />).

+ +

Finally, after having served a request which involved reading + .htaccess files, we need to discard the storage allocated for + handling them. That is solved the same way it is solved wherever else + similar problems come up, by tying those structures to the per-transaction + resource pool.

+ +

Per-directory configuration structures

+

Let's look out how all of this plays out in mod_mime.c, + which defines the file typing handler which emulates the NCSA server's + behavior of determining file types from suffixes. What we'll be looking + at, here, is the code which implements the AddType and AddEncoding commands. These commands can appear in + .htaccess files, so they must be handled in the module's + private per-directory data, which in fact, consists of two separate + tables for MIME types and encoding information, and is declared as + follows:

+ + 
typedef struct {
+    table *forced_types;      /* Additional AddTyped stuff */
+    table *encoding_types;    /* Added with AddEncoding... */
+} mime_dir_config;
+ +

When the server is reading a configuration file, or <Directory> section, which includes + one of the MIME module's commands, it needs to create a + mime_dir_config structure, so those commands have something + to act on. It does this by invoking the function it finds in the module's + `create per-dir config slot', with two arguments: the name of the + directory to which this configuration information applies (or + NULL for srm.conf), and a pointer to a + resource pool in which the allocation should happen.

+ +

(If we are reading a .htaccess file, that resource pool + is the per-request resource pool for the request; otherwise it is a + resource pool which is used for configuration data, and cleared on + restarts. Either way, it is important for the structure being created to + vanish when the pool is cleared, by registering a cleanup on the pool if + necessary).

+ +

For the MIME module, the per-dir config creation function just + ap_pallocs the structure above, and a creates a couple of + tables to fill it. That looks like this:

+ +

+ void *create_mime_dir_config (pool *p, char *dummy)
+ {
+ + mime_dir_config *new =
+ + (mime_dir_config *) ap_palloc (p, sizeof(mime_dir_config));
+ +
+ new->forced_types = ap_make_table (p, 4);
+ new->encoding_types = ap_make_table (p, 4);
+
+ return new;
+ + } +

+ +

Now, suppose we've just read in a .htaccess file. We + already have the per-directory configuration structure for the next + directory up in the hierarchy. If the .htaccess file we just + read in didn't have any AddType + or AddEncoding commands, its + per-directory config structure for the MIME module is still valid, and we + can just use it. Otherwise, we need to merge the two structures + somehow.

+ +

To do that, the server invokes the module's per-directory config merge + function, if one is present. That function takes three arguments: the two + structures being merged, and a resource pool in which to allocate the + result. For the MIME module, all that needs to be done is overlay the + tables from the new per-directory config structure with those from the + parent:

+ +

+ void *merge_mime_dir_configs (pool *p, void *parent_dirv, void *subdirv)
+ {
+ + mime_dir_config *parent_dir = (mime_dir_config *)parent_dirv;
+ mime_dir_config *subdir = (mime_dir_config *)subdirv;
+ mime_dir_config *new =
+ + (mime_dir_config *)ap_palloc (p, sizeof(mime_dir_config));
+ +
+ new->forced_types = ap_overlay_tables (p, subdir->forced_types,
+ + parent_dir->forced_types);
+ + new->encoding_types = ap_overlay_tables (p, subdir->encoding_types,
+ + parent_dir->encoding_types);
+ +
+ return new;
+ + } +

+ +

As a note -- if there is no per-directory merge function present, the + server will just use the subdirectory's configuration info, and ignore + the parent's. For some modules, that works just fine (e.g., for + the includes module, whose per-directory configuration information + consists solely of the state of the XBITHACK), and for those + modules, you can just not declare one, and leave the corresponding + structure slot in the module itself NULL.

+ + +

Command handling

+

Now that we have these structures, we need to be able to figure out how + to fill them. That involves processing the actual AddType and AddEncoding commands. To find commands, the server looks in + the module's command table. That table contains information on how many + arguments the commands take, and in what formats, where it is permitted, + and so forth. That information is sufficient to allow the server to invoke + most command-handling functions with pre-parsed arguments. Without further + ado, let's look at the AddType + command handler, which looks like this (the AddEncoding command looks basically the same, and won't be + shown here):

+ +

+ char *add_type(cmd_parms *cmd, mime_dir_config *m, char *ct, char *ext)
+ {
+ + if (*ext == '.') ++ext;
+ ap_table_set (m->forced_types, ext, ct);
+ return NULL;
+ + } +

+ +

This command handler is unusually simple. As you can see, it takes + four arguments, two of which are pre-parsed arguments, the third being the + per-directory configuration structure for the module in question, and the + fourth being a pointer to a cmd_parms structure. That + structure contains a bunch of arguments which are frequently of use to + some, but not all, commands, including a resource pool (from which memory + can be allocated, and to which cleanups should be tied), and the (virtual) + server being configured, from which the module's per-server configuration + data can be obtained if required.

+ +

Another way in which this particular command handler is unusually + simple is that there are no error conditions which it can encounter. If + there were, it could return an error message instead of NULL; + this causes an error to be printed out on the server's + stderr, followed by a quick exit, if it is in the main config + files; for a .htaccess file, the syntax error is logged in + the server error log (along with an indication of where it came from), and + the request is bounced with a server error response (HTTP error status, + code 500).

+ +

The MIME module's command table has entries for these commands, which + look like this:

+ +

+ command_rec mime_cmds[] = {
+ + { "AddType", add_type, NULL, OR_FILEINFO, TAKE2,
+ "a mime type followed by a file extension" },
 + { "AddEncoding", add_encoding, NULL, OR_FILEINFO, TAKE2,
+ + "an encoding (e.g., gzip), followed by a file extension" },
+ + { NULL }
+ + }; +

+ +

The entries in these tables are:

+
    +
  • The name of the command
    • +
  • The function which handles it
    • +
  • a (void *) pointer, which is passed in the + cmd_parms structure to the command handler --- + this is useful in case many similar commands are handled by + the same function.
    • + +
  • A bit mask indicating where the command may appear. There + are mask bits corresponding to each + AllowOverride option, and an additional mask + bit, RSRC_CONF, indicating that the command may + appear in the server's own config files, but not in + any .htaccess file.
    • + +
  • A flag indicating how many arguments the command handler + wants pre-parsed, and how they should be passed in. + TAKE2 indicates two pre-parsed arguments. Other + options are TAKE1, which indicates one + pre-parsed argument, FLAG, which indicates that + the argument should be On or Off, + and is passed in as a boolean flag, RAW_ARGS, + which causes the server to give the command the raw, unparsed + arguments (everything but the command name itself). There is + also ITERATE, which means that the handler looks + the same as TAKE1, but that if multiple + arguments are present, it should be called multiple times, + and finally ITERATE2, which indicates that the + command handler looks like a TAKE2, but if more + arguments are present, then it should be called multiple + times, holding the first argument constant.
    • + +
  • Finally, we have a string which describes the arguments + that should be present. If the arguments in the actual config + file are not as required, this string will be used to help + give a more specific error message. (You can safely leave + this NULL).
    • +
+ +

Finally, having set this all up, we have to use it. This is ultimately + done in the module's handlers, specifically for its file-typing handler, + which looks more or less like this; note that the per-directory + configuration structure is extracted from the request_rec's + per-directory configuration vector by using the + ap_get_module_config function.

+ +

+ int find_ct(request_rec *r)
+ {
+ + int i;
+ char *fn = ap_pstrdup (r->pool, r->filename);
+ mime_dir_config *conf = (mime_dir_config *)
+ + ap_get_module_config(r->per_dir_config, &mime_module);
+ + char *type;
+
+ if (S_ISDIR(r->finfo.st_mode)) {
+ + r->content_type = DIR_MAGIC_TYPE;
+ return OK;
+ + }
+
+ if((i=ap_rind(fn,'.')) < 0) return DECLINED;
+ ++i;
+
+ if ((type = ap_table_get (conf->encoding_types, &fn[i])))
+ {
+ + r->content_encoding = type;
+
+ /* go back to previous extension to try to use it as a type */
+ fn[i-1] = '\0';
+ if((i=ap_rind(fn,'.')) < 0) return OK;
+ ++i;
+ + }
+
+ if ((type = ap_table_get (conf->forced_types, &fn[i])))
+ {
+ + r->content_type = type;
+ + }
+
+ return OK; + + } +

+ + +

Side notes -- per-server configuration, + virtual servers, etc.

+

The basic ideas behind per-server module configuration are basically + the same as those for per-directory configuration; there is a creation + function and a merge function, the latter being invoked where a virtual + server has partially overridden the base server configuration, and a + combined structure must be computed. (As with per-directory configuration, + the default if no merge function is specified, and a module is configured + in some virtual server, is that the base configuration is simply + ignored).

+ +

The only substantial difference is that when a command needs to + configure the per-server private module data, it needs to go to the + cmd_parms data to get at it. Here's an example, from the + alias module, which also indicates how a syntax error can be returned + (note that the per-directory configuration argument to the command + handler is declared as a dummy, since the module doesn't actually have + per-directory config data):

+ +

+ char *add_redirect(cmd_parms *cmd, void *dummy, char *f, char *url)
+ {
+ + server_rec *s = cmd->server;
+ alias_server_conf *conf = (alias_server_conf *)
+ + ap_get_module_config(s->module_config,&alias_module);
+ + alias_entry *new = ap_push_array (conf->redirects);
+
+ if (!ap_is_url (url)) return "Redirect to non-URL";
+
+ new->fake = f; new->real = url;
+ return NULL;
+ + } +

+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/debugging.html b/docs/manual/developer/debugging.html new file mode 100644 index 00000000..f7977f5e --- /dev/null +++ b/docs/manual/developer/debugging.html @@ -0,0 +1,3 @@ +URI: debugging.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/developer/debugging.html.en b/docs/manual/developer/debugging.html.en new file mode 100644 index 00000000..b79b6221 --- /dev/null +++ b/docs/manual/developer/debugging.html.en @@ -0,0 +1,197 @@ + + + +Debugging Memory Allocation in APR - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation

Debugging Memory Allocation in APR

+
+

Available Languages:  en 

+
+ +

The allocation mechanisms within APR have a number of debugging modes + that can be used to assist in finding memory problems. This document + describes the modes available and gives instructions on activating + them.

+
+ +
top
+
+

Available debugging options

+

Allocation Debugging - ALLOC_DEBUG

+ + +
Debugging support: Define this to enable code which + helps detect re-use of free()d memory and other such + nonsense.
+ +

The theory is simple. The FILL_BYTE (0xa5) + is written over all malloc'd memory as we receive it, and + is written over everything that we free up during a + clear_pool. We check that blocks on the free list always + have the FILL_BYTE in them, and we check during + palloc() that the bytes still have FILL_BYTE + in them. If you ever see garbage URLs or whatnot containing lots + of 0xa5s then you know something used data that's been + freed or uninitialized.

+ + +

Malloc Support - ALLOC_USE_MALLOC

+ + +
If defined all allocations will be done with + malloc() and free()d appropriately at the + end.
+ +

This is intended to be used with something like Electric + Fence or Purify to help detect memory problems. Note that if + you're using efence then you should also add in ALLOC_DEBUG. + But don't add in ALLOC_DEBUG if you're using Purify because + ALLOC_DEBUG would hide all the uninitialized read errors + that Purify can diagnose.

+ + +

Pool Debugging - POOL_DEBUG

+
This is intended to detect cases where the wrong pool is + used when assigning data to an object in another pool.
+ +

In particular, it causes the table_{set,add,merge}n + routines to check that their arguments are safe for the + apr_table_t they're being placed in. It currently only works + with the unix multiprocess model, but could be extended to others.

+ + +

Table Debugging - MAKE_TABLE_PROFILE

+ + +
Provide diagnostic information about make_table() calls + which are possibly too small.
+ +

This requires a recent gcc which supports + __builtin_return_address(). The error_log output will be a + message such as:

+

+ table_push: apr_table_t created by 0x804d874 hit limit of 10 +

+ +

Use l *0x804d874 to find the + source that corresponds to. It indicates that a apr_table_t + allocated by a call at that address has possibly too small an + initial apr_table_t size guess.

+ + +

Allocation Statistics - ALLOC_STATS

+ + +
Provide some statistics on the cost of allocations.
+ +

This requires a bit of an understanding of how alloc.c + works.

+ +
top
+
+

Allowable Combinations

+ +

Not all the options outlined above can be activated at the + same time. the following table gives more information.

+ + + + + + + + + + + + + + + + +
+ ALLOC DEBUGALLOC USE MALLOCPOOL DEBUGMAKE TABLE PROFILEALLOC STATS
ALLOC DEBUG-NoYesYesYes
ALLOC USE MALLOCNo-NoNoNo
POOL DEBUGYesNo-YesYes
MAKE TABLE PROFILEYesNoYes-Yes
ALLOC STATSYesNoYesYes-
+ +

Additionally the debugging options are not suitable for + multi-threaded versions of the server. When trying to debug + with these options the server should be started in single + process mode.

+
top
+
+

Activating Debugging Options

+ +

The various options for debugging memory are now enabled in + the apr_general.h header file in APR. The various options are + enabled by uncommenting the define for the option you wish to + use. The section of the code currently looks like this + (contained in srclib/apr/include/apr_pools.h)

+ +

+ /*
+ #define ALLOC_DEBUG
+ #define POOL_DEBUG
+ #define ALLOC_USE_MALLOC
+ #define MAKE_TABLE_PROFILE
+ #define ALLOC_STATS
+ */
+
+ typedef struct ap_pool_t {
+ + union block_hdr *first;
+ union block_hdr *last;
+ struct cleanup *cleanups;
+ struct process_chain *subprocesses;
+ struct ap_pool_t *sub_pools;
+ struct ap_pool_t *sub_next;
+ struct ap_pool_t *sub_prev;
+ struct ap_pool_t *parent;
+ char *free_first_avail;
+ + #ifdef ALLOC_USE_MALLOC
+ + void *allocation_list;
+ + #endif
+ #ifdef POOL_DEBUG
+ + struct ap_pool_t *joined;
+ + #endif
+ + int (*apr_abort)(int retcode);
+ struct datastruct *prog_data;
+ + } ap_pool_t; +

+ +

To enable allocation debugging simply move the #define + ALLOC_DEBUG above the start of the comments block and rebuild + the server.

+ +

Note

+

In order to use the various options the server must + be rebuilt after editing the header file.

+
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/documenting.html b/docs/manual/developer/documenting.html new file mode 100644 index 00000000..0731e2d3 --- /dev/null +++ b/docs/manual/developer/documenting.html @@ -0,0 +1,3 @@ +URI: documenting.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/developer/documenting.html.en b/docs/manual/developer/documenting.html.en new file mode 100644 index 00000000..e8e32595 --- /dev/null +++ b/docs/manual/developer/documenting.html.en @@ -0,0 +1,84 @@ + + + +Documenting Apache 2.0 - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation

Documenting Apache 2.0

+
+

Available Languages:  en 

+
+ +

Apache 2.0 uses Doxygen to + document the APIs and global variables in the the code. This will explain + the basics of how to document using Doxygen.

+
+
top
+
+

Brief Description

+

To start a documentation block, use /**
+ To end a documentation block, use */

+ +

In the middle of the block, there are multiple tags we can + use:

+ +

+ Description of this functions purpose
+ @param parameter_name description
+ @return description
+ @deffunc signature of the function
+

+ +

The deffunc is not always necessary. DoxyGen does not + have a full parser in it, so any prototype that use a macro in the + return type declaration is too complex for scandoc. Those functions + require a deffunc. An example (using &gt; rather + than >):

+ +

+ /**
+  * return the final element of the pathname
+  * @param pathname The path to get the final element of
+  * @return the final element of the path
+  * @tip Examples:
+  * <pre>
+  * "/foo/bar/gum" -&gt; "gum"
+  * "/foo/bar/gum/" -&gt; ""
+  * "gum" -&gt; "gum"
+  * "wi\\n32\\stuff" -&gt; "stuff"
+  * </pre>
+  * @deffunc const char * ap_filename_of_pathname(const char *pathname)
+  */ +

+ +

At the top of the header file, always include:

+

+ /**
+  * @package Name of library header
+  */ +

+ +

Doxygen uses a new HTML file for each package. The HTML files are named + {Name_of_library_header}.html, so try to be concise with your names.

+ +

For a further discussion of the possibilities please refer to + the Doxygen site.

+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/filters.html b/docs/manual/developer/filters.html new file mode 100644 index 00000000..c65dc946 --- /dev/null +++ b/docs/manual/developer/filters.html @@ -0,0 +1,3 @@ +URI: filters.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/developer/filters.html.en b/docs/manual/developer/filters.html.en new file mode 100644 index 00000000..45406dbe --- /dev/null +++ b/docs/manual/developer/filters.html.en @@ -0,0 +1,210 @@ + + + +How filters work in Apache 2.0 - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation

How filters work in Apache 2.0

+
+

Available Languages:  en 

+
+ +

Warning

+

This is a cut 'n paste job from an email + (<022501c1c529$f63a9550$7f00000a@KOJ>) and only reformatted for + better readability. It's not up to date but may be a good start for + further research.

+
+
+ +
top
+
+

Filter Types

+

There are three basic filter types (each of these is actually broken + down into two categories, but that comes later).

+ +
+
CONNECTION
+
Filters of this type are valid for the lifetime of this connection. + (AP_FTYPE_CONNECTION, AP_FTYPE_NETWORK)
+ +
PROTOCOL
+
Filters of this type are valid for the lifetime of this request from + the point of view of the client, this means that the request is valid + from the time that the request is sent until the time that the response + is received. (AP_FTYPE_PROTOCOL, + AP_FTYPE_TRANSCODE)
+ +
RESOURCE
+
Filters of this type are valid for the time that this content is used + to satisfy a request. For simple requests, this is identical to + PROTOCOL, but internal redirects and sub-requests can change + the content without ending the request. (AP_FTYPE_RESOURCE, + AP_FTYPE_CONTENT_SET)
+
+ +

It is important to make the distinction between a protocol and a + resource filter. A resource filter is tied to a specific resource, it + may also be tied to header information, but the main binding is to a + resource. If you are writing a filter and you want to know if it is + resource or protocol, the correct question to ask is: "Can this filter + be removed if the request is redirected to a different resource?" If + the answer is yes, then it is a resource filter. If it is no, then it + is most likely a protocol or connection filter. I won't go into + connection filters, because they seem to be well understood. With this + definition, a few examples might help:

+ +
+
Byterange
+
We have coded it to be inserted for all requests, and it is removed + if not used. Because this filter is active at the beginning of all + requests, it can not be removed if it is redirected, so this is a + protocol filter.
+ +
http_header
+
This filter actually writes the headers to the network. This is + obviously a required filter (except in the asis case which is special + and will be dealt with below) and so it is a protocol filter.
+ +
Deflate
+
The administrator configures this filter based on which file has been + requested. If we do an internal redirect from an autoindex page to an + index.html page, the deflate filter may be added or removed based on + config, so this is a resource filter.
+
+ +

The further breakdown of each category into two more filter types is + strictly for ordering. We could remove it, and only allow for one + filter type, but the order would tend to be wrong, and we would need to + hack things to make it work. Currently, the RESOURCE filters + only have one filter type, but that should change.

+
top
+
+

How are filters inserted?

+

This is actually rather simple in theory, but the code is + complex. First of all, it is important that everybody realize that + there are three filter lists for each request, but they are all + concatenated together. So, the first list is + r->output_filters, then r->proto_output_filters, + and finally r->connection->output_filters. These correspond + to the RESOURCE, PROTOCOL, and + CONNECTION filters respectively. The problem previously, was + that we used a singly linked list to create the filter stack, and we + started from the "correct" location. This means that if I had a + RESOURCE filter on the stack, and I added a + CONNECTION filter, the CONNECTION filter would + be ignored. This should make sense, because we would insert the connection + filter at the top of the c->output_filters list, but the end + of r->output_filters pointed to the filter that used to be + at the front of c->output_filters. This is obviously wrong. + The new insertion code uses a doubly linked list. This has the advantage + that we never lose a filter that has been inserted. Unfortunately, it comes + with a separate set of headaches.

+ +

The problem is that we have two different cases were we use subrequests. + The first is to insert more data into a response. The second is to + replace the existing response with an internal redirect. These are two + different cases and need to be treated as such.

+ +

In the first case, we are creating the subrequest from within a handler + or filter. This means that the next filter should be passed to + make_sub_request function, and the last resource filter in the + sub-request will point to the next filter in the main request. This + makes sense, because the sub-request's data needs to flow through the + same set of filters as the main request. A graphical representation + might help:

+ +
+Default_handler --> includes_filter --> byterange --> ...
+
+ +

If the includes filter creates a sub request, then we don't want the + data from that sub-request to go through the includes filter, because it + might not be SSI data. So, the subrequest adds the following:

+ +
    
+Default_handler --> includes_filter -/-> byterange --> ...
+                                    /
+Default_handler --> sub_request_core
+
+ +

What happens if the subrequest is SSI data? Well, that's easy, the + includes_filter is a resource filter, so it will be added to + the sub request in between the Default_handler and the + sub_request_core filter.

+ +

The second case for sub-requests is when one sub-request is going to + become the real request. This happens whenever a sub-request is created + outside of a handler or filter, and NULL is passed as the next filter to + the make_sub_request function.

+ +

In this case, the resource filters no longer make sense for the new + request, because the resource has changed. So, instead of starting from + scratch, we simply point the front of the resource filters for the + sub-request to the front of the protocol filters for the old request. + This means that we won't lose any of the protocol filters, neither will + we try to send this data through a filter that shouldn't see it.

+ +

The problem is that we are using a doubly-linked list for our filter + stacks now. But, you should notice that it is possible for two lists to + intersect in this model. So, you do you handle the previous pointer? + This is a very difficult question to answer, because there is no "right" + answer, either method is equally valid. I looked at why we use the + previous pointer. The only reason for it is to allow for easier + addition of new servers. With that being said, the solution I chose was + to make the previous pointer always stay on the original request.

+ +

This causes some more complex logic, but it works for all cases. My + concern in having it move to the sub-request, is that for the more + common case (where a sub-request is used to add data to a response), the + main filter chain would be wrong. That didn't seem like a good idea to + me.

+
top
+
+

Asis

+

The final topic. :-) Mod_Asis is a bit of a hack, but the + handler needs to remove all filters except for connection filters, and + send the data. If you are using mod_asis, all other + bets are off.

+
top
+
+

Explanations

+

The absolutely last point is that the reason this code was so hard to + get right, was because we had hacked so much to force it to work. I + wrote most of the hacks originally, so I am very much to blame. + However, now that the code is right, I have started to remove some + hacks. Most people should have seen that the reset_filters + and add_required_filters functions are gone. Those inserted + protocol level filters for error conditions, in fact, both functions did + the same thing, one after the other, it was really strange. Because we + don't lose protocol filters for error cases any more, those hacks went away. + The HTTP_HEADER, Content-length, and + Byterange filters are all added in the + insert_filters phase, because if they were added earlier, we + had some interesting interactions. Now, those could all be moved to be + inserted with the HTTP_IN, CORE, and + CORE_IN filters. That would make the code easier to + follow.

+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/hooks.html b/docs/manual/developer/hooks.html new file mode 100644 index 00000000..49fe68e8 --- /dev/null +++ b/docs/manual/developer/hooks.html @@ -0,0 +1,3 @@ +URI: hooks.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/developer/hooks.html.en b/docs/manual/developer/hooks.html.en new file mode 100644 index 00000000..fee900f6 --- /dev/null +++ b/docs/manual/developer/hooks.html.en @@ -0,0 +1,239 @@ + + + +Apache 2.0 Hook Functions - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation

Apache 2.0 Hook Functions

+
+

Available Languages:  en 

+
+ +

Warning

+

This document is still in development and may be partially out of + date.

+
+ +

In general, a hook function is one that Apache will call at + some point during the processing of a request. Modules can + provide functions that are called, and specify when they get + called in comparison to other modules.

+
+ +
top
+
+

Creating a hook function

+

In order to create a new hook, four things need to be + done:

+ +

Declare the hook function

+

Use the AP_DECLARE_HOOK macro, which needs to be given + the return type of the hook function, the name of the hook, and the + arguments. For example, if the hook returns an int and + takes a request_rec * and an int and is + called do_something, then declare it like this:

+

+ AP_DECLARE_HOOK(int, do_something, (request_rec *r, int n)) +

+ +

This should go in a header which modules will include if + they want to use the hook.

+ + +

Create the hook structure

+

Each source file that exports a hook has a private structure + which is used to record the module functions that use the hook. + This is declared as follows:

+ +

+ APR_HOOK_STRUCT(
+ + APR_HOOK_LINK(do_something)
+ ...
+ + ) +

+ + +

Implement the hook caller

+

The source file that exports the hook has to implement a + function that will call the hook. There are currently three + possible ways to do this. In all cases, the calling function is + called ap_run_hookname().

+ +

Void hooks

+

If the return value of a hook is void, then all the + hooks are called, and the caller is implemented like this:

+ +

+ AP_IMPLEMENT_HOOK_VOID(do_something, (request_rec *r, int n), (r, n)) +

+ +

The second and third arguments are the dummy argument + declaration and the dummy arguments as they will be used when + calling the hook. In other words, this macro expands to + something like this:

+ +

+ void ap_run_do_something(request_rec *r, int n)
+ {
+ + ...
+ do_something(r, n);
+ + } +

+ + +

Hooks that return a value

+

If the hook returns a value, then it can either be run until + the first hook that does something interesting, like so:

+ +

+ AP_IMPLEMENT_HOOK_RUN_FIRST(int, do_something, (request_rec *r, int n), (r, n), DECLINED) +

+ +

The first hook that does not return DECLINED + stops the loop and its return value is returned from the hook + caller. Note that DECLINED is the tradition Apache + hook return meaning "I didn't do anything", but it can be + whatever suits you.

+ +

Alternatively, all hooks can be run until an error occurs. + This boils down to permitting two return values, one of + which means "I did something, and it was OK" and the other + meaning "I did nothing". The first function that returns a + value other than one of those two stops the loop, and its + return is the return value. Declare these like so:

+ +

+ AP_IMPLEMENT_HOOK_RUN_ALL(int, do_something, (request_rec *r, int n), (r, n), OK, DECLINED) +

+ +

Again, OK and DECLINED are the traditional + values. You can use what you want.

+ + + +

Call the hook callers

+

At appropriate moments in the code, call the hook caller, + like so:

+ +

+ int n, ret;
+ request_rec *r;
+
+ ret=ap_run_do_something(r, n); +

+ +
top
+
+

Hooking the hook

+

A module that wants a hook to be called needs to do two + things.

+ +

Implement the hook function

+

Include the appropriate header, and define a static function + of the correct type:

+ +

+ static int my_something_doer(request_rec *r, int n)
+ {
+ + ...
+ return OK;
+ + } +

+ + +

Add a hook registering function

+

During initialisation, Apache will call each modules hook + registering function, which is included in the module + structure:

+ +

+ static void my_register_hooks()
+ {
+ + ap_hook_do_something(my_something_doer, NULL, NULL, APR_HOOK_MIDDLE);
+ + }
+
+ mode MODULE_VAR_EXPORT my_module =
+ {
+ + ...
+ my_register_hooks /* register hooks */
+ + }; +

+ + +

Controlling hook calling order

+

In the example above, we didn't use the three arguments in + the hook registration function that control calling order. + There are two mechanisms for doing this. The first, rather + crude, method, allows us to specify roughly where the hook is + run relative to other modules. The final argument control this. + There are three possible values: APR_HOOK_FIRST, + APR_HOOK_MIDDLE and APR_HOOK_LAST.

+ +

All modules using any particular value may be run in any + order relative to each other, but, of course, all modules using + APR_HOOK_FIRST will be run before APR_HOOK_MIDDLE + which are before APR_HOOK_LAST. Modules that don't care + when they are run should use APR_HOOK_MIDDLE. (I spaced + these out so people could do stuff like APR_HOOK_FIRST-2 + to get in slightly earlier, but is this wise? - Ben)

+ +

Note that there are two more values, + APR_HOOK_REALLY_FIRST and APR_HOOK_REALLY_LAST. These + should only be used by the hook exporter.

+ +

The other method allows finer control. When a module knows + that it must be run before (or after) some other modules, it + can specify them by name. The second (third) argument is a + NULL-terminated array of strings consisting of the names of + modules that must be run before (after) the current module. For + example, suppose we want "mod_xyz.c" and "mod_abc.c" to run + before we do, then we'd hook as follows:

+ +

+ static void register_hooks()
+ {
+ + static const char * const aszPre[] = { "mod_xyz.c", "mod_abc.c", NULL };
+
+ ap_hook_do_something(my_something_doer, aszPre, NULL, APR_HOOK_MIDDLE);
+ + } +

+ +

Note that the sort used to achieve this is stable, so + ordering set by APR_HOOK_ORDER is preserved, as far + as is possible.

+ +

Ben Laurie, 15th August 1999

+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/index.html b/docs/manual/developer/index.html new file mode 100644 index 00000000..5f97bff8 --- /dev/null +++ b/docs/manual/developer/index.html @@ -0,0 +1,3 @@ +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/developer/index.html.en b/docs/manual/developer/index.html.en new file mode 100644 index 00000000..c2e9a2b1 --- /dev/null +++ b/docs/manual/developer/index.html.en @@ -0,0 +1,82 @@ + + + +Developer Documentation for Apache 2.0 - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Developer Documentation for Apache 2.0

+
+

Available Languages:  en 

+
+ +

Many of the documents on these Developer pages are lifted + from Apache 1.3's documentation. While they are all being + updated to Apache 2.0, they are in different stages of + progress. Please be patient, and point out any discrepancies or + errors on the developer/ pages directly to the + dev@httpd.apache.org mailing list.

+
+ +
top
+
+

Topics

+ +
top
+
+

External Resources

+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/modules.html b/docs/manual/developer/modules.html new file mode 100644 index 00000000..cb7b1dbf --- /dev/null +++ b/docs/manual/developer/modules.html @@ -0,0 +1,7 @@ +URI: modules.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: modules.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/developer/modules.html.en b/docs/manual/developer/modules.html.en new file mode 100644 index 00000000..82029060 --- /dev/null +++ b/docs/manual/developer/modules.html.en @@ -0,0 +1,273 @@ + + + +Converting Modules from Apache 1.3 to Apache 2.0 - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation

Converting Modules from Apache 1.3 to Apache 2.0

+
+

Available Languages:  en  | + ja 

+
+ +

This is a first attempt at writing the lessons I learned + when trying to convert the mod_mmap_static module to Apache + 2.0. It's by no means definitive and probably won't even be + correct in some ways, but it's a start.

+
+ +
top
+
+

The easier changes ...

+ +

Cleanup Routines

+

These now need to be of type apr_status_t and return a + value of that type. Normally the return value will be + APR_SUCCESS unless there is some need to signal an error in + the cleanup. Be aware that even though you signal an error not all code + yet checks and acts upon the error.

+ + +

Initialisation Routines

+

These should now be renamed to better signify where they sit + in the overall process. So the name gets a small change from + mmap_init to mmap_post_config. The arguments + passed have undergone a radical change and now look like

+ +
    +
  • apr_pool_t *p
    • +
  • apr_pool_t *plog
    • +
  • apr_pool_t *ptemp
    • +
  • server_rec *s
    • +
+ + +

Data Types

+

A lot of the data types have been moved into the APR. This means that some have had + a name change, such as the one shown above. The following is a brief + list of some of the changes that you are likely to have to make.

+ +
    +
  • pool becomes apr_pool_t
    • +
  • table becomes apr_table_t
    • +
+ +
top
+
+

The messier changes...

+ +

Register Hooks

+

The new architecture uses a series of hooks to provide for + calling your functions. These you'll need to add to your module + by way of a new function, static void register_hooks(void). + The function is really reasonably straightforward once you + understand what needs to be done. Each function that needs + calling at some stage in the processing of a request needs to + be registered, handlers do not. There are a number of phases + where functions can be added, and for each you can specify with + a high degree of control the relative order that the function + will be called in.

+ +

This is the code that was added to mod_mmap_static:

+ 
+static void register_hooks(void)
+{
+    static const char * const aszPre[]={ "http_core.c",NULL };
+    ap_hook_post_config(mmap_post_config,NULL,NULL,HOOK_MIDDLE);
+    ap_hook_translate_name(mmap_static_xlat,aszPre,NULL,HOOK_LAST);
+};
+ +

This registers 2 functions that need to be called, one in + the post_config stage (virtually every module will need this + one) and one for the translate_name phase. note that while + there are different function names the format of each is + identical. So what is the format?

+ +

+ ap_hook_phase_name(function_name, + predecessors, successors, position); +

+ +

There are 3 hook positions defined...

+ +
    +
  • HOOK_FIRST
    • +
  • HOOK_MIDDLE
    • +
  • HOOK_LAST
    • +
+ +

To define the position you use the position and then modify + it with the predecessors and successors. Each of the modifiers + can be a list of functions that should be called, either before + the function is run (predecessors) or after the function has + run (successors).

+ +

In the mod_mmap_static case I didn't care about the + post_config stage, but the mmap_static_xlat + must be called after the core module had done it's name + translation, hence the use of the aszPre to define a modifier to the + position HOOK_LAST.

+ + +

Module Definition

+

There are now a lot fewer stages to worry about when + creating your module definition. The old defintion looked + like

+ + 
+module MODULE_VAR_EXPORT module_name_module =
+{
+    STANDARD_MODULE_STUFF,
+    /* initializer */
+    /* dir config creater */
+    /* dir merger --- default is to override */
+    /* server config */
+    /* merge server config */
+    /* command handlers */
+    /* handlers */
+    /* filename translation */
+    /* check_user_id */
+    /* check auth */
+    /* check access */
+    /* type_checker */
+    /* fixups */
+    /* logger */
+    /* header parser */
+    /* child_init */
+    /* child_exit */
+    /* post read-request */
+};
+ +

The new structure is a great deal simpler...

+ 
+module MODULE_VAR_EXPORT module_name_module =
+{
+    STANDARD20_MODULE_STUFF,
+    /* create per-directory config structures */
+    /* merge per-directory config structures  */
+    /* create per-server config structures    */
+    /* merge per-server config structures     */
+    /* command handlers */
+    /* handlers */
+    /* register hooks */
+};
+ +

Some of these read directly across, some don't. I'll try to + summarise what should be done below.

+ +

The stages that read directly across :

+ +
+
/* dir config creater */
+
/* create per-directory config structures */
+ +
/* server config */
+
/* create per-server config structures */
+ +
/* dir merger */
+
/* merge per-directory config structures */
+ +
/* merge server config */
+
/* merge per-server config structures */
+ +
/* command table */
+
/* command apr_table_t */
+ +
/* handlers */
+
/* handlers */
+
+ +

The remainder of the old functions should be registered as + hooks. There are the following hook stages defined so + far...

+ +
+
ap_hook_post_config
+
this is where the old _init routines get + registered
+ +
ap_hook_http_method
+
retrieve the http method from a request. (legacy)
+ +
ap_hook_open_logs
+
open any specified logs
+ +
ap_hook_auth_checker
+
check if the resource requires authorization
+ +
ap_hook_access_checker
+
check for module-specific restrictions
+ +
ap_hook_check_user_id
+
check the user-id and password
+ +
ap_hook_default_port
+
retrieve the default port for the server
+ +
ap_hook_pre_connection
+
do any setup required just before processing, but after + accepting
+ +
ap_hook_process_connection
+
run the correct protocol
+ +
ap_hook_child_init
+
call as soon as the child is started
+ +
ap_hook_create_request
+
??
+ +
ap_hook_fixups
+
last chance to modify things before generating content
+ +
ap_hook_handler
+
generate the content
+ +
ap_hook_header_parser
+
lets modules look at the headers, not used by most modules, because + they use post_read_request for this
+ +
ap_hook_insert_filter
+
to insert filters into the filter chain
+ +
ap_hook_log_transaction
+
log information about the request
+ +
ap_hook_optional_fn_retrieve
+
retrieve any functions registered as optional
+ +
ap_hook_post_read_request
+
called after reading the request, before any other phase
+ +
ap_hook_quick_handler
+
called before any request processing, used by cache modules.
+ +
ap_hook_translate_name
+
translate the URI into a filename
+ +
ap_hook_type_checker
+
determine and/or set the doc type
+
+ +
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/modules.html.ja.euc-jp b/docs/manual/developer/modules.html.ja.euc-jp new file mode 100644 index 00000000..2fba7754 --- /dev/null +++ b/docs/manual/developer/modules.html.ja.euc-jp @@ -0,0 +1,274 @@ + + + +¥â¥¸¥å¡¼¥ë¤Î Apache 1.3 ¤«¤é Apache 2.0 ¤Ø¤Î°Ü¿¢ - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > Developer Documentation

¥â¥¸¥å¡¼¥ë¤Î Apache 1.3 ¤«¤é Apache 2.0 ¤Ø¤Î°Ü¿¢

+
+

Available Languages:  en  | + ja 

+
+ +

¤³¤Îʸ½ñ¤Ï mod_mmap_static ¥â¥¸¥å¡¼¥ë¤ò Apache 2.0 ÍѤ˰ܿ¢¤·¤¿»þ¤Ë + ³Ø¤ó¤À·Ð¸³¤ò¤â¤È¤Ë½ñ¤¤¤¿¡¢ºÇ½é¤Î¼ê°ú¤­½ñ¤Ç¤¹¡£¤Þ¤À¤Þ¤À´°Á´¤¸¤ã¤Ê¤¤¤·¡¢ + ¤Ò¤ç¤Ã¤È¤¹¤ë¤È´Ö°ã¤Ã¤Æ¤¤¤ëÉôʬ¤â¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢ + ¼è¤Ã³Ý¤ê¤Ë¤Ï¤Ê¤ë¤Ç¤·¤ç¤¦¡£

+
+ +
top
+
+

´Êñ¤ÊÊѹ¹ÅÀ

+ +

¥¯¥ê¡¼¥ó¥Ê¥Ã¥× ¥ë¡¼¥Á¥ó

+

¥¯¥ê¡¼¥ó¥Ê¥Ã¥×¥ë¡¼¥Á¥ó¤Ï apr_status_t ·¿¤Ç¤¢¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤½¤·¤Æ¡¢apr_status_t ·¿¤ÎÃͤòÊÖ¤µ¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£ + ¥¯¥ê¡¼¥ó¥Ê¥Ã¥×Ãæ¤Î¥¨¥é¡¼¤òÄÌÃΤ¹¤ëɬÍפ¬¤Ê¤±¤ì¤Ð¡¢ÊÖ¤êÃͤÏÉáÄÌ¡¢ + ARP_SUCCESS ¤Ç¤¹¡£¤¿¤È¤¨¥¨¥é¡¼¤òÄÌÃΤ·¤¿¤È¤·¤Æ¤â¡¢ + ¤¹¤Ù¤Æ¤Î¥³¡¼¥É¤¬¤½¤ÎÄÌÃΤò¥Á¥§¥Ã¥¯¤·¤¿¤ê¡¢ + ¥¨¥é¡¼¤Ë±þ¤¸¤¿Æ°ºî¤ò¤¹¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¤³¤È¤Ëµ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£

+ + + +

½é´ü²½¥ë¡¼¥Á¥ó

+ +

½é´ü²½¥ë¡¼¥Á¥ó¤Ï½èÍýÁ´ÂΤ«¤é¸«¤Æ¤·¤Ã¤¯¤ê¤¯¤ë¤è¤¦¤Ê°ÕÌ£¤òɽ¤¹¤è¤¦¤Ë¡¢ + ̾Á°¤¬Êѹ¹¤µ¤ì¤Þ¤·¤¿¡£¤Ç¤¹¤«¤é¡¢mmap_init ¤«¤é mmap_post_config + ¤Î¤è¤¦¤Ë¤Á¤ç¤Ã¤ÈÊѹ¹¤µ¤ì¤Þ¤·¤¿¡£ + ÅϤµ¤ì¤ë°ú¿ô¤ÏÂçÉý¤ËÊѹ¹¤µ¤ì¡¢¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£

+ +
    +
  • apr_pool_t *p
    • +
  • apr_pool_t *plog
    • +
  • apr_pool_t *ptemp
    • +
  • server_rec *s
    • +
+ + +

¥Ç¡¼¥¿·¿

+

¥Ç¡¼¥¿·¿¤Î¤Û¤È¤ó¤É¤Ï APR ¤Ë°Ü¤µ¤ì¤Þ¤·¤¿¡£¤Ä¤Þ¤ê¡¢ + ¤¤¤¯¤Ä¤«¤Î̾Á°¤¬Á°½Ò¤Î¤è¤¦¤ËÊѹ¹¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + »Ü¤¹¤Ù¤­Êѹ¹ÅÀ¤Î´Êñ¤Ê°ìÍ÷¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹¡£

+ +
    +
  • pool becomes apr_pool_t
    • +
  • table becomes apr_table_t
    • +
+ +
top
+
+

¤â¤Ã¤ÈÌñ²ð¤ÊÊѹ¹ÅÀ¡Ä

+ +

¥Õ¥Ã¥¯¤ÎÅÐÏ¿

+

¿·¤·¤¤¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ç¤ÏºîÀ®¤·¤¿´Ø¿ô¤ò¸Æ¤Ó½Ð¤¹¤Î¤Ë + °ìÏ¢¤Î¥Õ¥Ã¥¯¤ò»ÈÍѤ·¤Þ¤¹¡£¤³¤Î¥Õ¥Ã¥¯¤Ï¡¢¿·¤·¤¤´Ø¿ô + static void register_hooks(void) ¤ò»È¤Ã¤ÆÅÐÏ¿¤¹¤ë¤è¤¦¡¢ + ¥â¥¸¥å¡¼¥ë¤Ë½ñ¤­Â­¤µ¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£ + ¤³¤Î´Ø¿ô¤Ï¡¢¤Ê¤Ë¤ò¤¹¤Ù¤­¤«°ìöÍý²ò¤·¤Æ¤·¤Þ¤¨¤Ð¡¢ + ½½Ê¬¤Ë¤ï¤«¤ê¤ä¤¹¤¤¤â¤Î¤Ç¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¤Î½èÍý¤Î¤¢¤ë¥¹¥Æ¡¼¥¸¤Ç¸Æ¤Ó½Ð¤µ¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤ + ´Ø¿ô¤ÏÅÐÏ¿¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¥Ï¥ó¥É¥é¤ÏÅÐÏ¿¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£ + ´Ø¿ô¤òÅÐÏ¿¤Ç¤­¤ë¥Õ¥§¡¼¥º¤Ï¤¿¤¯¤µ¤ó¤¢¤ê¤Þ¤¹¡£ + ¤½¤ì¤¾¤ì¤Î¥Õ¥§¡¼¥º¤Ç¡¢´Ø¿ô¤ò¸Æ¤Ó½Ð¤¹ÁêÂÐŪ¤Ê½çÈ֤ϡ¢ + ¤«¤Ê¤ê¤ÎÄøÅÙÀ©¸æ¤Ç¤­¤Þ¤¹¡£

+ +

°Ê²¼¤Ï¡¢mod_mmap_static ¤ËÄɲä·¤¿¥³¡¼¥É¤Ç¤¹:

+ + 
+static void register_hooks(void)
+{
+    static const char * const aszPre[]={ "http_core.c",NULL };
+    ap_hook_post_config(mmap_post_config,NULL,NULL,HOOK_MIDDLE);
+    ap_hook_translate_name(mmap_static_xlat,aszPre,NULL,HOOK_LAST);
+};
+ +

¤³¤³¤Ç¤Ï¸Æ¤Ó¤À¤¹¤Ù¤­Æó¤Ä¤Î´Ø¿ô¤òÅÐÏ¿¤·¤Æ¤¤¤Þ¤¹¡£°ì¤Ä¤Ï + post_config ¥¹¥Æ¡¼¥¸ÍÑ (¤Û¤È¤ó¤É¤¹¤Ù¤Æ¤Î¥â¥¸¥å¡¼¥ë + ¤Ï¤³¤ì¤¬É¬ÍפǤ¹) ¤Ç¡¢¤â¤¦°ì¤Ä¤Ï translate_name ¥Õ¥§¡¼¥ºÍѤǤ¹¡£ + ¤½¤ì¤¾¤ì¤Î´Ø¿ô¤Ï̾Á°¤Ï°ã¤¦¤±¤ì¤É¤â·Á¼°¤ÏƱ¤¸¤Ç¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤½¤ì¤Ç¤Ï¡¢·Á¼°¤Ï¤É¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¤«?

+ +

+ ap_hook_phase_name(function_name, + predecessors, successors, position); +

+ +

»°¤Ä¤Î°ÌÃÖ¤¬ÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹¡Ä

+ +
    +
  • HOOK_FIRST
    • +
  • HOOK_MIDDLE
    • +
  • HOOK_LAST
    • +
+ +

°ÌÃÖ¤òÄêµÁ¤¹¤ë¤Ë¤Ï¡¢¾åµ­¤Î¡Ö°ÌÃ֡פò»ØÄꤷ¡¢ + ½¤¾þ»Ò¤Ç¤¢¤ë¡ÖÀè¹Ô¡×¤È¡Ö¸å¹Ô¡×¤Ç¼ê¤ò²Ã¤¨¤Þ¤¹¡£ + ¡ÖÀè¹Ô¡×¡Ö¸å¹Ô¡×¤Ï¡¢¸Æ¤Ð¤ì¤ë¤Ù¤­´Ø¿ô¤Î¥ê¥¹¥È¤Ç¤¹¡£ + ¡ÖÀè¹Ô¡×¤Ï´Ø¿ô¤Î¼Â¹ÔÁ°¤Ë¸Æ¤Ð¤ì¤ë¤â¤Î¤Ç¡¢ + ¡Ö¸å¹Ô¡×¤Ï¼Â¹Ô¸å¤Ë¸Æ¤Ð¤ì¤ë¤â¤Î¤Ç¤¹¡£

+ +

mod_mmap_static ¤Î¾ì¹ç¡¢post_config + ¥¹¥Æ¡¼¥¸¤Ç¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¤¬¡¢ + mmap_static_xlat ¤¬ core ¥â¥¸¥å¡¼¥ë¤¬Ì¾Á°¤ÎÊÑ´¹¤ò¼Â¹Ô¤·¤¿¸å¤Ë + ¸Æ¤Ð¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤½¤³¤Ç aszPre ¤ò»È¤Ã¤Æ HOOK_LAST ¤Î½¤¾þ»Ò¤òÄêµÁ¤·¤Æ¤¤¤Þ¤¹¡£

+ + +

¥â¥¸¥å¡¼¥ë¤ÎÄêµÁ

+

¥â¥¸¥å¡¼¥ë¤ÎÄêµÁ¤òºîÀ®¤¹¤ëºÝ¤ËÃí°Õ¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤ + ¥¹¥Æ¡¼¥¸¤Î¿ô¤Ï·ã¸º¤·¤Æ¤¤¤Þ¤¹¡£¸Å¤¤ÄêµÁ¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤·¤¿¡£

+ + 
+module MODULE_VAR_EXPORT module_name_module =
+{
+    STANDARD_MODULE_STUFF,
+    /* initializer */
+    /* dir config creater */
+    /* dir merger --- default is to override */
+    /* server config */
+    /* merge server config */
+    /* command handlers */
+    /* handlers */
+    /* filename translation */
+    /* check_user_id */
+    /* check auth */
+    /* check access */
+    /* type_checker */
+    /* fixups */
+    /* logger */
+    /* header parser */
+    /* child_init */
+    /* child_exit */
+    /* post read-request */
+};
+ +

¿·¤·¤¤¹½Â¤ÂΤϤȤäƤ⥷¥ó¥×¥ë¤Ç¤¹¡Ä

+ 
+module MODULE_VAR_EXPORT module_name_module =
+{
+    STANDARD20_MODULE_STUFF,
+    /* create per-directory config structures */
+    /* merge per-directory config structures  */
+    /* create per-server config structures    */
+    /* merge per-server config structures     */
+    /* command handlers */
+    /* handlers */
+    /* register hooks */
+};
+ +

¤³¤Î¤¦¤Á¤Î¤¤¤¯¤Ä¤«¤Ï¸Å¤¤¤â¤Î¤«¤é¿·¤·¤¤¤â¤Î¤ËľÀÜÆɤßÂؤ¨¤é¤ì¤ë¤â¤Î¤Ç¡¢ + ¤¤¤¯¤Ä¤«¤Ï¤½¤¦¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤É¤¦¤¹¤ì¤Ð¤¤¤¤¤Î¤«¤òÍ×Ì󤷤Ƥߤޤ¹¡£

+ +

ľÀÜÆɤßÂؤ¨¤é¤ì¤ë¥¹¥Æ¡¼¥¸:

+ +
+
/* ¥Ç¥£¥ì¥¯¥È¥êÀßÄêºîÀ®´Ø¿ô */
+
/* ¥Ç¥£¥ì¥¯¥È¥êËèÀßÄ깽¤ÂκîÀ® */
+ +
/* ¥µ¡¼¥ÐÀßÄêºîÀ®´Ø¿ô */
+
/* ¥µ¡¼¥ÐËèÀßÄ깽¤ÂκîÀ® */
+ +
/* ¥Ç¥£¥ì¥¯¥È¥êÀßÄê¥Þ¡¼¥¸´Ø¿ô */
+
/* ¥Ç¥£¥ì¥¯¥È¥êËèÀßÄ깽¤ÂÎ¥Þ¡¼¥¸ */
+ +
/* ¥µ¡¼¥ÐÀßÄê¥Þ¡¼¥¸´Ø¿ô */
+
/* ¥µ¡¼¥ÐËèÀßÄ깽¤ÂκîÀ®¥Þ¡¼¥¸ */
+ +
/* ¥³¥Þ¥ó¥É¡¦¥Æ¡¼¥Ö¥ë */
+
/* ¥³¥Þ¥ó¥É apr_table_t */
+ +
/* ¥Ï¥ó¥É¥é */
+
/* ¥Ï¥ó¥É¥é */
+
+ +

¸Å¤¤´Ø¿ô¤Î»Ä¤ê¤Î¤â¤Î¤Ï¥Õ¥Ã¥¯¤È¤·¤ÆÅÐÏ¿¤µ¤ì¤ë¤Ù¤­¤Ç¤¹¡£ + ¸½»þÅÀ¤Ç¼¡¤Î¤è¤¦¤Ê¥Õ¥Ã¥¯¡¦¥¹¥Æ¡¼¥¸¤¬ÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹¡Ä

+ +
+
ap_hook_post_config
+
(°ÊÁ°¤Î _init ¥ë¡¼¥Á¥ó¤¬ÅÐÏ¿¤µ¤ì¤ë¤Ù¤­¾ì½ê¤Ç¤¹)
+ +
ap_hook_http_method
+
(¥ê¥¯¥¨¥¹¥È¤«¤é HTTP ¥á¥½¥Ã¥É¤ò¼èÆÀ¤·¤Þ¤¹ (¸ß´¹ÍÑ))
+ +
ap_hook_open_logs
+
(ÆÃÄê¤Î¥í¥°¤Î¥ª¡¼¥×¥ó)
+ +
ap_hook_auth_checker
+
(¥ê¥½¡¼¥¹¤¬¸¢¸Â¤òɬÍפȤ¹¤ë¤«¤É¤¦¤«¤Î³Îǧ)
+ +
ap_hook_access_checker
+
(¥â¥¸¥å¡¼¥ë¸ÇÍ­¤ÎÀ©Ìó¤Î³Îǧ)
+ +
ap_hook_check_user_id
+
(¥æ¡¼¥¶ ID ¤È¥Ñ¥¹¥ï¡¼¥É¤Î³Îǧ)
+ +
ap_hook_default_port
+
(¥µ¡¼¥Ð¤Î¥Ç¥Õ¥©¥ë¥È¡¦¥Ý¡¼¥È¤Î¼èÆÀ)
+ +
ap_hook_pre_connection
+
(½èÍý¤ÎľÁ°¤ËɬÍפʤ³¤È¤ò¼Â¹Ô¡£¤¿¤À¤· accept ľ¸å¤Ë¸Æ¤Ð¤ì¤ë)
+ +
ap_hook_process_connection
+
(¥×¥í¥È¥³¥ë¤Î½èÍý)
+ +
ap_hook_child_init
+
(»Ò¥×¥í¥»¥¹µ¯Æ°Ä¾¸å)
+ +
ap_hook_create_request
+
(??)
+ +
ap_hook_fixups
+
(±þÅúÆâÍƤÎÀ¸À®¤òÊѹ¹¤¹¤ë¥é¥¹¥È¡¦¥Á¥ã¥ó¥¹)
+ +
ap_hook_handler
+
(±þÅúÆâÍƤÎÀ¸À®)
+ +
ap_hook_header_parser
+
(¥â¥¸¥å¡¼¥ë¤Ë¥Ø¥Ã¥À¤Î¾È²ñ¤ò¤µ¤»¤ë¡£¤Û¤È¤ó¤É¤Î¥â¥¸¥å¡¼¥ë¤Ç¤Ï»È¤ï¤ì¤Þ¤»¤ó¡£post_read_request ¤ò»È¤¤¤Þ¤¹)
+ +
ap_hook_insert_filter
+
(¥Õ¥£¥ë¥¿¡¦¥Á¥§¥¤¥ó¤Ë¥Õ¥£¥ë¥¿¤òÁÞÆþ)
+ +
ap_hook_log_transaction
+
(¥ê¥¯¥¨¥¹¥È¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤òµ­Ï¿¤¹¤ë)
+ +
ap_hook_optional_fn_retrieve
+
(¥ª¥×¥·¥ç¥ó¤È¤·¤ÆÅÐÏ¿¤µ¤ì¤¿´Ø¿ô¤Î¼èÆÀ)
+ +
ap_hook_post_read_request
+
(¥ê¥¯¥¨¥¹¥È¤òÆɤߤ³¤ó¤À¸å¡¢Â¾¤Î¥Õ¥§¡¼¥º¤ÎÁ°¤Ë¸Æ¤Ð¤ì¤ë)
+ +
ap_hook_quick_handler
+
¥ê¥¯¥¨¥¹¥È¤Î½èÍý¤¬»Ï¤Þ¤ëÁ°¤Ë¸Æ¤Ð¤ì¤ë¡£¥­¥ã¥Ã¥·¥å¥â¥¸¥å¡¼¥ë¤¬ + »ÈÍѤ·¤Æ¤¤¤ë
+ +
ap_hook_translate_name
+
(URI ¤ò¥Õ¥¡¥¤¥ë̾¤ËÊÑ´¹¤¹¤ë)
+ +
ap_hook_type_checker
+
(ʸ½ñ·¿¤Î·èÄê¤ÈÀßÄê¡£¤¢¤ë¤¤¤Ï¤½¤ÎÊÒÊý)
+
+ +
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/request.html b/docs/manual/developer/request.html new file mode 100644 index 00000000..54770724 --- /dev/null +++ b/docs/manual/developer/request.html @@ -0,0 +1,3 @@ +URI: request.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/developer/request.html.en b/docs/manual/developer/request.html.en new file mode 100644 index 00000000..aeb6e504 --- /dev/null +++ b/docs/manual/developer/request.html.en @@ -0,0 +1,260 @@ + + + +Request Processing in Apache 2.0 - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation

Request Processing in Apache 2.0

+
+

Available Languages:  en 

+
+ +

Warning

+

Warning - this is a first (fast) draft that needs further + revision!

+
+ +

Several changes in Apache 2.0 affect the internal request + processing mechanics. Module authors need to be aware of these + changes so they may take advantage of the optimizations and + security enhancements.

+ +

The first major change is to the subrequest and redirect + mechanisms. There were a number of different code paths in + Apache 1.3 to attempt to optimize subrequest or redirect + behavior. As patches were introduced to 2.0, these + optimizations (and the server behavior) were quickly broken due + to this duplication of code. All duplicate code has been folded + back into ap_process_request_internal() to prevent + the code from falling out of sync again.

+ +

This means that much of the existing code was 'unoptimized'. + It is the Apache HTTP Project's first goal to create a robust + and correct implementation of the HTTP server RFC. Additional + goals include security, scalability and optimization. New + methods were sought to optimize the server (beyond the + performance of Apache 1.3) without introducing fragile or + insecure code.

+
+ +
top
+
+

The Request Processing Cycle

+

All requests pass through ap_process_request_internal() + in request.c, including subrequests and redirects. If a module + doesn't pass generated requests through this code, the author is cautioned + that the module may be broken by future changes to request + processing.

+ +

To streamline requests, the module author can take advantage + of the hooks offered to drop out of the request cycle early, or + to bypass core Apache hooks which are irrelevant (and costly in + terms of CPU.)

+
top
+
+

The Request Parsing Phase

+

Unescapes the URL

+

The request's parsed_uri path is unescaped, once and only + once, at the beginning of internal request processing.

+ +

This step is bypassed if the proxyreq flag is set, or the + parsed_uri.path element is unset. The module has no further + control of this one-time unescape operation, either failing to + unescape or multiply unescaping the URL leads to security + reprecussions.

+ + +

Strips Parent and This Elements from the + URI

+

All /../ and /./ elements are + removed by ap_getparents(). This helps to ensure + the path is (nearly) absolute before the request processing + continues.

+ +

This step cannot be bypassed.

+ + +

Initial URI Location Walk

+

Every request is subject to an + ap_location_walk() call. This ensures that + <Location> sections + are consistently enforced for all requests. If the request is an internal + redirect or a sub-request, it may borrow some or all of the processing + from the previous or parent request's ap_location_walk, so this step + is generally very efficient after processing the main request.

+ + +

translate_name

+

Modules can determine the file name, or alter the given URI + in this step. For example, mod_vhost_alias will + translate the URI's path into the configured virtual host, + mod_alias will translate the path to an alias path, + and if the request falls back on the core, the DocumentRoot is prepended to the request resource.

+ +

If all modules DECLINE this phase, an error 500 is + returned to the browser, and a "couldn't translate name" error is logged + automatically.

+ + +

Hook: map_to_storage

+

After the file or correct URI was determined, the + appropriate per-dir configurations are merged together. For + example, mod_proxy compares and merges the appropriate + <Proxy> sections. + If the URI is nothing more than a local (non-proxy) TRACE + request, the core handles the request and returns DONE. + If no module answers this hook with OK or DONE, + the core will run the request filename against the <Directory> and <Files> sections. If the request + 'filename' isn't an absolute, legal filename, a note is set for + later termination.

+ + +

URI Location Walk

+

Every request is hardened by a second + ap_location_walk() call. This reassures that a + translated request is still subjected to the configured + <Location> sections. + The request again borrows some or all of the processing from its previous + location_walk above, so this step is almost always very + efficient unless the translated URI mapped to a substantially different + path or Virtual Host.

+ + +

Hook: header_parser

+

The main request then parses the client's headers. This + prepares the remaining request processing steps to better serve + the client's request.

+ +
top
+
+

The Security Phase

+

Needs Documentation. Code is:

+ + 
+switch (ap_satisfies(r)) {
+case SATISFY_ALL:
+case SATISFY_NOSPEC:
+    if ((access_status = ap_run_access_checker(r)) != 0) {
+        return decl_die(access_status, "check access", r);
+    }
+
+    if (ap_some_auth_required(r)) {
+        if (((access_status = ap_run_check_user_id(r)) != 0)
+            || !ap_auth_type(r)) {
+            return decl_die(access_status, ap_auth_type(r)
+                          ? "check user.  No user file?"
+                          : "perform authentication. AuthType not set!",
+                          r);
+        }
+
+        if (((access_status = ap_run_auth_checker(r)) != 0)
+            || !ap_auth_type(r)) {
+            return decl_die(access_status, ap_auth_type(r)
+                          ? "check access.  No groups file?"
+                          : "perform authentication. AuthType not set!",
+                          r);
+        }
+    }
+    break;
+
+case SATISFY_ANY:
+    if (((access_status = ap_run_access_checker(r)) != 0)) {
+        if (!ap_some_auth_required(r)) {
+            return decl_die(access_status, "check access", r);
+        }
+
+        if (((access_status = ap_run_check_user_id(r)) != 0)
+            || !ap_auth_type(r)) {
+            return decl_die(access_status, ap_auth_type(r)
+                          ? "check user.  No user file?"
+                          : "perform authentication. AuthType not set!",
+                          r);
+        }
+
+        if (((access_status = ap_run_auth_checker(r)) != 0)
+            || !ap_auth_type(r)) {
+            return decl_die(access_status, ap_auth_type(r)
+                          ? "check access.  No groups file?"
+                          : "perform authentication. AuthType not set!",
+                          r);
+        }
+    }
+    break;
+}
+
top
+
+

The Preparation Phase

+

Hook: type_checker

+

The modules have an opportunity to test the URI or filename + against the target resource, and set mime information for the + request. Both mod_mime and + mod_mime_magic use this phase to compare the file + name or contents against the administrator's configuration and set the + content type, language, character set and request handler. Some modules + may set up their filters or other request handling parameters at this + time.

+ +

If all modules DECLINE this phase, an error 500 is + returned to the browser, and a "couldn't find types" error is logged + automatically.

+ + +

Hook: fixups

+

Many modules are 'trounced' by some phase above. The fixups + phase is used by modules to 'reassert' their ownership or force + the request's fields to their appropriate values. It isn't + always the cleanest mechanism, but occasionally it's the only + option.

+ +
top
+
+

The Handler Phase

+

This phase is not part of the processing in + ap_process_request_internal(). Many + modules prepare one or more subrequests prior to creating any + content at all. After the core, or a module calls + ap_process_request_internal() it then calls + ap_invoke_handler() to generate the request.

+ +

Hook: insert_filter

+

Modules that transform the content in some way can insert + their values and override existing filters, such that if the + user configured a more advanced filter out-of-order, then the + module can move its order as need be. There is no result code, + so actions in this hook better be trusted to always succeed.

+ + +

Hook: handler

+

The module finally has a chance to serve the request in its + handler hook. Note that not every prepared request is sent to + the handler hook. Many modules, such as mod_autoindex, + will create subrequests for a given URI, and then never serve the + subrequest, but simply lists it for the user. Remember not to + put required teardown from the hooks above into this module, + but register pool cleanups against the request pool to free + resources as required.

+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/developer/thread_safety.html b/docs/manual/developer/thread_safety.html new file mode 100644 index 00000000..02f067e7 --- /dev/null +++ b/docs/manual/developer/thread_safety.html @@ -0,0 +1,3 @@ +URI: thread_safety.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/developer/thread_safety.html.en b/docs/manual/developer/thread_safety.html.en new file mode 100644 index 00000000..9592eb1f --- /dev/null +++ b/docs/manual/developer/thread_safety.html.en @@ -0,0 +1,285 @@ + + + +Apache 2.0 Thread Safety Issues - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Developer Documentation

Apache 2.0 Thread Safety Issues

+
+

Available Languages:  en 

+
+ +

When using any of the threaded mpms in Apache 2.0 it is important + that every function called from Apache be thread safe. When linking in 3rd + party extensions it can be difficult to determine whether the resulting + server will be thread safe. Casual testing generally won't tell you this + either as thread safety problems can lead to subtle race conditons that + may only show up in certain conditions under heavy load.

+
+ +
top
+
+

Global and static variables

+

When writing your module or when trying to determine if a module or + 3rd party library is thread safe there are some common things to keep in + mind.

+ +

First, you need to recognize that in a threaded model each individual + thread has its own program counter, stack and registers. Local variables + live on the stack, so those are fine. You need to watch out for any + static or global variables. This doesn't mean that you are absolutely not + allowed to use static or global variables. There are times when you + actually want something to affect all threads, but generally you need to + avoid using them if you want your code to be thread safe.

+ +

In the case where you have a global variable that needs to be global and + accessed by all threads, be very careful when you update it. If, for + example, it is an incrementing counter, you need to atomically increment + it to avoid race conditions with other threads. You do this using a mutex + (mutual exclusion). Lock the mutex, read the current value, increment it + and write it back and then unlock the mutex. Any other thread that wants + to modify the value has to first check the mutex and block until it is + cleared.

+ +

If you are using APR, have a look + at the apr_atomic_* functions and the + apr_thread_mutex_* functions.

+ +
top
+
+

errno

+

This is a common global variable that holds the error number of the + last error that occurred. If one thread calls a low-level function that + sets errno and then another thread checks it, we are bleeding error + numbers from one thread into another. To solve this, make sure your + module or library defines _REENTRANT or is compiled with + -D_REENTRANT. This will make errno a per-thread variable + and should hopefully be transparent to the code. It does this by doing + something like this:

+ +

+ #define errno (*(__errno_location())) +

+ +

which means that accessing errno will call + __errno_location() which is provided by the libc. Setting + _REENTRANT also forces redefinition of some other functions + to their *_r equivalents and sometimes changes + the common getc/putc macros into safer function + calls. Check your libc documentation for specifics. Instead of, or in + addition to _REENTRANT the symbols that may affect this are + _POSIX_C_SOURCE, _THREAD_SAFE, + _SVID_SOURCE, and _BSD_SOURCE.

+
top
+
+

Common standard troublesome functions

+

Not only do things have to be thread safe, but they also have to be + reentrant. strtok() is an obvious one. You call it the first + time with your delimiter which it then remembers and on each subsequent + call it returns the next token. Obviously if multiple threads are + calling it you will have a problem. Most systems have a reentrant version + of of the function called strtok_r() where you pass in an + extra argument which contains an allocated char * which the + function will use instead of its own static storage for maintaining + the tokenizing state. If you are using APR you can use apr_strtok().

+ +

crypt() is another function that tends to not be reentrant, + so if you run across calls to that function in a library, watch out. On + some systems it is reentrant though, so it is not always a problem. If + your system has crypt_r() chances are you should be using + that, or if possible simply avoid the whole mess by using md5 instead.

+ +
top
+
+

Common 3rd Party Libraries

+

The following is a list of common libraries that are used by 3rd party + Apache modules. You can check to see if your module is using a potentially + unsafe library by using tools such as ldd(1) and + nm(1). For PHP, for example, + try this:

+ +

+ % ldd libphp4.so
+ libsablot.so.0 => /usr/local/lib/libsablot.so.0 (0x401f6000)
+ libexpat.so.0 => /usr/lib/libexpat.so.0 (0x402da000)
+ libsnmp.so.0 => /usr/lib/libsnmp.so.0 (0x402f9000)
+ libpdf.so.1 => /usr/local/lib/libpdf.so.1 (0x40353000)
+ libz.so.1 => /usr/lib/libz.so.1 (0x403e2000)
+ libpng.so.2 => /usr/lib/libpng.so.2 (0x403f0000)
+ libmysqlclient.so.11 => /usr/lib/libmysqlclient.so.11 (0x40411000)
+ libming.so => /usr/lib/libming.so (0x40449000)
+ libm.so.6 => /lib/libm.so.6 (0x40487000)
+ libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x404a8000)
+ libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x404e7000)
+ libcrypt.so.1 => /lib/libcrypt.so.1 (0x40505000)
+ libssl.so.2 => /lib/libssl.so.2 (0x40532000)
+ libcrypto.so.2 => /lib/libcrypto.so.2 (0x40560000)
+ libresolv.so.2 => /lib/libresolv.so.2 (0x40624000)
+ libdl.so.2 => /lib/libdl.so.2 (0x40634000)
+ libnsl.so.1 => /lib/libnsl.so.1 (0x40637000)
+ libc.so.6 => /lib/libc.so.6 (0x4064b000)
+ /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) +

+ +

In addition to these libraries you will need to have a look at any + libraries linked statically into the module. You can use nm(1) + to look for individual symbols in the module.

+
top
+
+

Library List

+

Please drop a note to dev@httpd.apache.org + if you have additions or corrections to this list.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
LibraryVersionThread Safe?Notes
ASpell/PSpell ?
Berkeley DB3.x, 4.xYesBe careful about sharing a connection across threads.
bzip2 YesBoth low-level and high-level APIs are thread-safe. However, + high-level API requires thread-safe access to errno.
cdb ?
C-Client Perhapsc-client uses strtok() and + gethostbyname() which are not thread-safe on most C + library implementations. c-client's static data is meant to be shared + across threads. If strtok() and + gethostbyname() are thread-safe on your OS, c-client + may be thread-safe.
cpdflib ?
libcrypt ?
Expat YesNeed a separate parser instance per thread
FreeTDS ?
FreeType ?
GD 1.8.x ?
GD 2.0.x ?
gdbm NoErrors returned via a static gdbm_error + variable
ImageMagick5.2.2YesImageMagick docs claim it is thread safe since version 5.2.2 (see Change log). +
Imlib2 ?
libjpegv6b?
libmysqlclient YesUse mysqlclient_r library variant to ensure thread-safety. For + more information, please read http://www.mysql.com/doc/en/Threaded_clients.html.
Ming0.2a?
Net-SNMP5.0.x?
OpenLDAP2.1.xYesUse ldap_r library variant to ensure + thread-safety.
OpenSSL0.9.6gYesRequires proper usage of CRYPTO_num_locks, + CRYPTO_set_locking_callback, + CRYPTO_set_id_callback
liboci8 (Oracle 8+)8.x,9.x?
pdflib5.0.xYesPDFLib docs claim it is thread safe; changes.txt indicates it + has been partially thread-safe since V1.91: http://www.pdflib.com/products/pdflib/index.html.
libpng1.0.x?
libpng1.2.x?
libpq (PostgreSQL)7.xYesDon't share connections across threads and watch out for + crypt() calls
Sablotron0.95?
zlib1.1.4YesRelies upon thread-safe zalloc and zfree functions Default is to + use libc's calloc/free which are thread-safe.
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/dns-caveats.html b/docs/manual/dns-caveats.html new file mode 100644 index 00000000..9996161f --- /dev/null +++ b/docs/manual/dns-caveats.html @@ -0,0 +1,11 @@ +URI: dns-caveats.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: dns-caveats.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: dns-caveats.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/dns-caveats.html.en b/docs/manual/dns-caveats.html.en new file mode 100644 index 00000000..763d1a70 --- /dev/null +++ b/docs/manual/dns-caveats.html.en @@ -0,0 +1,239 @@ + + + +Issues Regarding DNS and Apache - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Issues Regarding DNS and Apache

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

This page could be summarized with the statement: don't + configure Apache in such a way that it relies on DNS resolution + for parsing of the configuration files. If Apache requires DNS + resolution to parse the configuration files then your server + may be subject to reliability problems (ie. it might not boot), + or denial and theft of service attacks (including users able + to steal hits from other users).

+
+ +
top
+
+

A Simple Example

+ + +

+ <VirtualHost www.abc.dom>
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+ +

In order for Apache to function properly, it absolutely needs + to have two pieces of information about each virtual host: the + ServerName and at least one + IP address that the server will bind and respond to. The above + example does not include the IP address, so Apache must use DNS + to find the address of www.abc.dom. If for some + reason DNS is not available at the time your server is parsing + its config file, then this virtual host will not be + configured. It won't be able to respond to any hits + to this virtual host (prior to Apache version 1.2 the server + would not even boot).

+ +

Suppose that www.abc.dom has address 10.0.0.1. + Then consider this configuration snippet:

+ +

+ <VirtualHost 10.0.0.1>
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+ +

This time Apache needs to use reverse DNS to find the + ServerName for this virtualhost. If that reverse + lookup fails then it will partially disable the virtualhost + (prior to Apache version 1.2 the server would not even boot). + If the virtual host is name-based then it will effectively be + totally disabled, but if it is IP-based then it will mostly + work. However, if Apache should ever have to generate a full + URL for the server which includes the server name, then it will + fail to generate a valid URL.

+ +

Here is a snippet that avoids both of these problems:

+ +

+ <VirtualHost 10.0.0.1>
+ ServerName www.abc.dom
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+
top
+
+

Denial of Service

+ + +

There are (at least) two forms that denial of service + can come in. If you are running a version of Apache prior to + version 1.2 then your server will not even boot if one of the + two DNS lookups mentioned above fails for any of your virtual + hosts. In some cases this DNS lookup may not even be under your + control; for example, if abc.dom is one of your + customers and they control their own DNS, they can force your + (pre-1.2) server to fail while booting simply by deleting the + www.abc.dom record.

+ +

Another form is far more insidious. Consider this + configuration snippet:

+ +

+ <VirtualHost www.abc.dom>
+   ServerAdmin webgirl@abc.dom
+   DocumentRoot /www/abc
+ </VirtualHost>
+
+ <VirtualHost www.def.dom>
+   ServerAdmin webguy@def.dom
+   DocumentRoot /www/def
+ </VirtualHost> +

+ +

Suppose that you've assigned 10.0.0.1 to + www.abc.dom and 10.0.0.2 to + www.def.dom. Furthermore, suppose that + def.dom has control of their own DNS. With this + config you have put def.dom into a position where + they can steal all traffic destined to abc.dom. To + do so, all they have to do is set www.def.dom to + 10.0.0.1. Since they control their own DNS you can't stop them + from pointing the www.def.dom record wherever they + wish.

+ +

Requests coming in to 10.0.0.1 (including all those where + users typed in URLs of the form + http://www.abc.dom/whatever) will all be served by + the def.dom virtual host. To better understand why + this happens requires a more in-depth discussion of how Apache + matches up incoming requests with the virtual host that will + serve it. A rough document describing this is available.

+
top
+
+

The "main server" Address

+ + +

The addition of name-based + virtual host support in Apache 1.1 requires Apache to know + the IP address(es) of the host that httpd + is running on. To get this address it uses either the global + ServerName + (if present) or calls the C function gethostname + (which should return the same as typing "hostname" at the + command prompt). Then it performs a DNS lookup on this address. + At present there is no way to avoid this lookup.

+ +

If you fear that this lookup might fail because your DNS + server is down then you can insert the hostname in + /etc/hosts (where you probably already have it so + that the machine can boot properly). Then ensure that your + machine is configured to use /etc/hosts in the + event that DNS fails. Depending on what OS you are using this + might be accomplished by editing /etc/resolv.conf, + or maybe /etc/nsswitch.conf.

+ +

If your server doesn't have to perform DNS for any other + reason then you might be able to get away with running Apache + with the HOSTRESORDER environment variable set to + "local". This all depends on what OS and resolver libraries you + are using. It also affects CGIs unless you use + mod_env to control the environment. It's best + to consult the man pages or FAQs for your OS.

+
top
+
+

Tips to Avoid These Problems

+ + +
    +
  • + use IP addresses in + VirtualHost +
    • + +
  • + use IP addresses in + Listen +
    • + +
  • + ensure all virtual hosts have an explicit + ServerName +
    • + +
  • create a <VirtualHost _default_:*> + server that has no pages to serve
    • +
+
top
+
+

Appendix: Future Directions

+ + +

The situation regarding DNS is highly undesirable. For + Apache 1.2 we've attempted to make the server at least continue + booting in the event of failed DNS, but it might not be the + best we can do. In any event, requiring the use of explicit IP + addresses in configuration files is highly undesirable in + today's Internet where renumbering is a necessity.

+ +

A possible work around to the theft of service attack + described above would be to perform a reverse DNS lookup on the + IP address returned by the forward lookup and compare the two + names -- in the event of a mismatch, the virtualhost would be + disabled. This would require reverse DNS to be configured + properly (which is something that most admins are familiar with + because of the common use of "double-reverse" DNS lookups by + FTP servers and TCP wrappers).

+ +

In any event, it doesn't seem possible to reliably boot a + virtual-hosted web server when DNS has failed unless IP + addresses are used. Partial solutions such as disabling + portions of the configuration might be worse than not booting + at all depending on what the webserver is supposed to + accomplish.

+ +

As HTTP/1.1 is deployed and browsers and proxies start + issuing the Host header it will become possible to + avoid the use of IP-based virtual hosts entirely. In this case, + a webserver has no requirement to do DNS lookups during + configuration. But as of March 1997 these features have not + been deployed widely enough to be put into use on critical + webservers.

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/dns-caveats.html.ja.euc-jp b/docs/manual/dns-caveats.html.ja.euc-jp new file mode 100644 index 00000000..17ee62d8 --- /dev/null +++ b/docs/manual/dns-caveats.html.ja.euc-jp @@ -0,0 +1,241 @@ + + + +DNS ¤È Apache ¤Ë¤Þ¤Ä¤ï¤ëÃí°Õ»ö¹à - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

DNS ¤È Apache ¤Ë¤Þ¤Ä¤ï¤ëÃí°Õ»ö¹à

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

ËÜʸ½ñ¤ÎÆâÍƤϼ¡¤Î°ì¸À¤Ë¿Ô¤­¤Þ¤¹¡£¡ÖApache ¤¬ÀßÄê¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤à¤È¤­¤Ë + DNS ¤ò»ÈÍѤ¹¤ëɬÍפ¬¤Ê¤¤¤è¤¦¤Ë¤·¤Æ²¼¤µ¤¤¡×¡£Apache ¤¬ÀßÄê¥Õ¥¡¥¤¥ë¤ò + Æɤ߹þ¤à¤È¤­¤Ë DNS ¤ò»ÈÍѤ¹¤ëɬÍפ¬¤¢¤ë¾ì¹ç¡¢¿®ÍêÀ­¤ÎÌäÂê + (µ¯Æ°¤·¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó) ¤ä¥µ¡¼¥Ó¥¹µñÈݤäÅðÍÑ¥¢¥¿¥Ã¥¯ + (¾¤Î¥æ¡¼¥¶¤«¤é¥Ò¥Ã¥È¤òÅð¤à¤³¤È¤ò´Þ¤ß¤Þ¤¹) + ¤ÎÌäÂê¤ËľÌ̤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+
+ +
top
+
+

´Êñ¤ÊÎã

+ + +

+ <VirtualHost www.abc.dom>
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+ +

Apache ¤¬Àµ¾ï¤Ëµ¡Ç½¤¹¤ë¤Ë¤Ï¡¢¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈËè¤Ëɬ¤ºÆó¤Ä¤Î + ¾ðÊó¤¬É¬Íפˤʤê¤Þ¤¹¡£¤½¤ì¤Ï¡¢ + ServerName + ¤È¡¢¤½¤Î¥µ¡¼¥Ð¤¬±þÅú¤¹¤ë¤¿¤á¤Î IP (ºÇÄã°ì¤Ä) ¤Ç¤¹¡£ + ¾åµ­Îã¤Ç¤Ï IP ¥¢¥É¥ì¥¹¤ò´Þ¤ó¤Ç¤¤¤Þ¤»¤ó¤Î¤Ç¡¢Apache ¤Ï DNS + ¤ò»ÈÍѤ·¤Æ www.abc.dom ¤ò¸«¤Ä¤±¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ²¿¤é¤«¤ÎÍýͳ¤ÇÀßÄê¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤ó¤Ç¤¤¤ë¤È¤­¤Ë DNS + ¤¬ÍøÍѤǤ­¤Ê¤«¤Ã¤¿¾ì¹ç¡¢ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÏÀßÄꤵ¤ì¤Þ¤»¤ó¡£ + ¤½¤·¤Æ¡¢¤½¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËÂФ¹¤ë¥Ò¥Ã¥È¤Ë¤Ï±þÅú¤¬¤Ê¤µ¤ì¤Þ¤»¤ó + (Apache 1.2 °ÊÁ°¤Ç¤Ïµ¯Æ°¤¹¤é¤·¤Þ¤»¤ó)¡£

+ +

www.abc.dom ¤Î¥¢¥É¥ì¥¹¤¬ 10.0.0.1 + ¤À¤È¤·¤Þ¤¹¡£¤Ç¤Ï¡¢¼¡¤ÎÀßÄê¤Ë¤Ä¤¤¤Æ¹Í¤¨¤Æ¤ß¤Þ¤·¤ç¤¦¡£

+ +

+ <VirtualHost 10.0.0.1>
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+ +

¸½ºß¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï Apache ¤Ï DNS µÕ°ú¤­¤ò»ÈÍѤ·¤Æ + ¤³¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î ServerName + ¤ò¸«¤Ä¤±¤Þ¤¹¡£ + ¤½¤ÎµÕ°ú¤­¤¬¼ºÇÔ¤·¤¿¾ì¹ç¤ÏÉôʬŪ¤Ë¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò̵¸ú¤Ë¤·¤Þ¤¹ + (Apache 1.2 ¤è¤êÁ°¤Ç¤Ïµ¯Æ°¤¹¤é¤·¤Þ¤»¤ó)¡£ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬Ì¾Á°¥Ù¡¼¥¹¤Ç¤¢¤ì¤Ð´°Á´¤Ë̵¸ú¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢ + IP ¥Ù¡¼¥¹¤Ç¤¢¤ì¤Ð³µ¤ÍÆ°ºî¤·¤Þ¤¹¡£¤·¤«¤·¤Ê¤¬¤é¡¢¥µ¡¼¥Ð̾¤ò + ´Þ¤à´°Á´¤Ê URL ¤òÀ¸À®¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¾ì¹ç¤Ï¡¢Àµ¤·¤¤ URL + ¤ÎÀ¸À®¤¬¤Ç¤­¤Þ¤»¤ó¡£

+ +

¼¡¤ÎÎã¤Ï¾åµ­¤ÎÌäÂê¤ò²ò·è¤·¤Æ¤¤¤Þ¤¹¡£

+ +

+ <VirtualHost 10.0.0.1>
+ ServerName www.abc.dom
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+
top
+
+

¥µ¡¼¥Ó¥¹µñÈÝ

+ + +

¥µ¡¼¥Ó¥¹µñÈݤ¬µ¯¤³¤ë¾ì¹ç¡¢(¾¯¤Ê¤¯¤È¤â) Æó¤Ä¤Î¥±¡¼¥¹¤¬¤¢¤ê¤Þ¤¹¡£ + Apache 1.2 ¤è¤êÁ°¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¾ì¹ç¡¢¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¤¿¤á¤Î + ¾åµ­¤ÎÆó¤Ä¤Î DNS ¸¡º÷¤Î¤¦¤Á°ì¤Ä¼ºÇÔ¤¹¤ì¤Ðµ¯Æ°¤¹¤é¤·¤Þ¤»¤ó¡£ + ¤½¤·¤Æ¤³¤Î DNS ¸¡º÷¤¬¼«Ê¬¤ÎÀ©¸æ²¼¤Ë¤¹¤é¤Ê¤¤¾ì¹ç¤â¤¢¤ê¤¨¤Þ¤¹¡£ + Î㤨¤Ð¡¢abc.dom ¤¬¸ÜµÒ¤Î¥µ¡¼¥Ð¤Î°ì¤Ä¤Ç¡¢ + DNS ¤Ï¸ÜµÒ¼«¿È¤Ç´ÉÍý¤·¤Æ¤¤¤ë¾ì¹ç¡¢Ã±¤Ë + www.abc.dom ¥ì¥³¡¼¥É¤òºï½ü¤¹¤ë¤À¤±¤Ç¡¢ + (1.2 ¤è¤êÁ°¤Î) ¥µ¡¼¥Ð¤òµ¯Æ°ÉÔǽ¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤â¤¦°ì¤Ä¤Î¥±¡¼¥¹¤Ï¡¢¤è¤êµ¤ÉÕ¤­¤Ë¤¯¤¤¤â¤Î¤Ç¤¹¡£ + ¼¡¤ÎÀßÄê¤Ë¤Ä¤¤¤Æ¹Í¤¨¤Æ¤ß¤Þ¤·¤ç¤¦¡£

+ +

+ <VirtualHost www.abc.dom>
+   ServerAdmin webgirl@abc.dom
+   DocumentRoot /www/abc
+ </VirtualHost>
+
+ <VirtualHost www.def.dom>
+   ServerAdmin webguy@def.dom
+   DocumentRoot /www/def
+ </VirtualHost> +

+ +

10.0.0.1 ¤ò www.abc.dom ¤Ë¡¢ + 10.0.0.2 ¤ò www.def.dom ¤Ë³ä¤êÅö¤Æ¤Æ¤¤¤ë¤È¤·¤Þ¤¹¡£ + ¤Þ¤¿¡¢def.dom ¤Ï¸ÜµÒ¼«¿È¤Î DNS + ¤ÎÀ©¸æ²¼¤Ë¤¢¤ë¤È¤·¤Þ¤¹¡£¤³¤ÎÀßÄê¤Ç¡¢abc.dom + ¤Ë¸þ¤±¤é¤ì¤¿¥È¥é¥Õ¥£¥Ã¥¯Á´¤Æ¤òÃ¥¤¦¤³¤È¤¬¤Ç¤­¤ë°ÌÃÖ¤Ë + def.dom ¤òÀßÃ֤Ǥ­¤Æ¤¤¤Þ¤¹¡£¸å¤Ïñ¤Ë + www.def.dom ¤¬ 10.0.0.1 ¤ò»²¾È¤¹¤ë¤è¤¦¤Ë + ÀßÄꤹ¤ë¤À¤±¤Ç¤¹¡£DNS ¤Ï¸ÜµÒ¦¤Î DNS ¤Ç¥³¥ó¥È¥í¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢ + www.def.dom ¥ì¥³¡¼¥É¤¬¹¥¤­¤Ê¾ì½ê¤ò»Ø¤¹¤è¤¦¤Ë + ÀßÄê¤Ç¤­¤Æ¤·¤Þ¤¦¤Î¤ò»ß¤á¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£

+ +

10.0.0.1 ¤ËÂФ¹¤ë¥ê¥¯¥¨¥¹¥È + (http://www.abc.dom/whatever ·Á¼°¤Î URL + ¤òÆþÎϤ·¤¿¥æ¡¼¥¶¤«¤é¤Î¤â¤ÎÁ´¤Æ¤ò´Þ¤ß¤Þ¤¹) + ¤Ï¡¢def.dom ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ç±þÅú¤µ¤ì¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Ê¤³¤È¤¬²¿¸Îµ¯¤³¤ë¤«¤â¤Ã¤ÈÎɤ¯ÃΤ뤿¤á¤Ë¤Ï¡¢ + ±þÅú¤ÎɬÍפʥС¼¥Á¥ã¥ë¥Û¥¹¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¡¢ + Apache ¤¬¤É¤Î¤è¤¦¤ËÀ°¹çÀ­¤ò³ÎÊݤ¹¤ë¤«¤Ë¤Ä¤¤¤Æ¡¢ + ¿¼¤¤µÄÏÀ¤¬É¬Íפˤʤê¤Þ¤¹¡£¤ª¤ª¤¶¤Ã¤Ñ¤ÊÀâÌÀ¤Ï¤³¤Á¤é¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+
top
+
+

¡Ö¼ç¥µ¡¼¥Ð¡×¥¢¥É¥ì¥¹

+ + +

Apache 1.1 ¤Ç¤Î ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¥µ¥Ý¡¼¥È Äɲäκݤˡ¢ + Apache ¤Ï httpd ¤Î¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¥Û¥¹¥È¤Î IP + ¥¢¥É¥ì¥¹¤òÃΤëɬÍפ¬½Ð¤Æ¤­¤Þ¤·¤¿¡£¤³¤Î¥¢¥É¥ì¥¹¤òÆÀ¤ë¤¿¤á¤Ë¡¢ + (¤â¤·¤¢¤ì¤Ð) ¥°¥í¡¼¥Ð¥ë¤Ê + ServerName ¤ò»ÈÍѤ¹¤ë¤«¡¢ + C ¸À¸ì¤Î´Ø¿ô gethostname (¥³¥Þ¥ó¥É¥×¥í¥ó¥×¥È¤Ç + hostname ¤È¥¿¥¤¥×¤·¤¿¤È¤­¤ÈƱ¤¸¤â¤Î¤òÊÖ¤·¤Þ¤¹) + ¤ò¸Æ¤Ó½Ð¤¹¤«¤ò¤·¤Þ¤¹¡£ + ¤½¤Î¸å¡¢ÆÀ¤é¤ì¤¿¥¢¥É¥ì¥¹¤Ç DNS ¸¡º÷¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£ + ¸½ºß¤Î¤È¤³¤í¡¢¤³¤Î DNS ¸¡º÷¤ò²óÈò¤¹¤ëÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +

DNS ¥µ¡¼¥Ð¤¬¥À¥¦¥ó¤·¤Æ¡¢¤³¤Î¸¡º÷¤¬¤Ç¤­¤Ê¤¤»öÂÖ¤¬µ¯¤³¤ë¤³¤È¤ò + ¶²¤ì¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢/etc/hosts + ¤Ë¥Û¥¹¥È̾¤òµ­½Ò¤·¤Æ¤ª¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹ + (¥Þ¥·¥ó¤¬Àµ¾ï¤Ëµ¯Æ°¤¹¤ë¤è¤¦¤Ë´û¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó)¡£ + ¤½¤Î¾ì¹ç¡¢DNS »²¾È¤¬¼ºÇÔ¤·¤¿¾ì¹ç¤Ë¥Þ¥·¥ó¤¬ /etc/hosts + ¤ò»ÈÍѤ¹¤ë¤è¤¦¤ËÀßÄꤷ¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤½¤ÎÊýË¡¤Ï¡¢¤É¤Î OS ¤ò»ÈÍѤ·¤Æ¤¤¤ë¤«¤Ë°Í¸¤·¤Þ¤¹¤¬¡¢ + /etc/resolv.conf ¤« /etc/nsswitch.conf + ¤òÊÔ½¸¤¹¤ë¤³¤È¤ÇÀßÄê¤Ç¤­¤Þ¤¹¡£

+ +

¤â¤·Â¾¤ÎÍýͳ¤Ç DNS ¤òÍøÍѤ¹¤ëɬÍפ¬¤Ê¤¤¾ì¹ç¤Ï¡¢ + HOSTRESORDER ´Ä¶­ÊÑ¿ô¤ò¡Ö local + ¡×¤ËÀßÄꤹ¤ë¤³¤È¤Ç¤½¤Î¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£°Ê¾å¤³¤ì¤é¤Î»öÊÁ¤Ï¡¢¤É¤ó¤Ê + OS ¡¢¥ì¥¾¥ë¥Ð¥é¥¤¥Ö¥é¥ê¤ò»ÈÍѤ·¤Æ¤¤¤ë¤«¤Ë°Í¸¤·¤Þ¤¹¡£¤Þ¤¿¡¢ + mod_env ¤ò»ÈÍѤ·¤Æ´Ä¶­ÊÑ¿ô¤òÀ©¸æ¤·¤Ê¤¤¸Â¤ê¡¢ + CGI ¤Ë¤â±Æ¶Á¤òÍ¿¤¨¤Þ¤¹¡£man ¥Ú¡¼¥¸¤ä»ÈÍѤ·¤Æ¤¤¤ë OS + ¤Î FAQ ¤ÇÄ´¤Ù¤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£

+
top
+
+

°Ê¾å¤ÎÌäÂê¤ò²ò·è¤¹¤ëÊýË¡

+ + +
    +
  • + VirtualHost + ¤Ç IP ¥¢¥É¥ì¥¹¤ò»ÈÍѤ¹¤ë¡£ +
    • + +
  • + Listen + ¤Ç IP ¥¢¥É¥ì¥¹¤ò»ÈÍѤ¹¤ë¡£ +
    • + +
  • + Á´¤Æ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬ÌÀ¼¨Åª¤Ë + ServerName + ¤ò»ý¤Ä¤è¤¦¤Ë¤¹¤ë¡£ +
    • + +
  • ²¿¤â±þÅú¤·¤Ê¤¤ + <VirtualHost _default_:*> + ¥µ¡¼¥Ð¤òºî¤ë¡£
    • +
+
top
+
+

ÉÕÏ¿: ¾­ÍèŪ¤ÊÊý¸þÀ­

+ + +

DNS ¤Ë´Ø¤·¤Æ¡¢¸½¾õ¤ÏÁ´¤¯µ¹¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£Apache 1.2 ¤Ç¡¢ + DNS ¤Î¥¤¥Ù¥ó¥È¤¬¼ºÇÔ¤·¤Æ¤â¾¯¤Ê¤¯¤È¤âµ¯Æ°¥×¥í¥»¥¹¤¬Â³¤¯¤è¤¦¤Ë¤·¤Þ¤·¤¿¤¬¡¢ + ¤³¤ì¤¬ºÇ¹â¤Î²ò·èÊýË¡¤Ç¤Ï¤Ê¤¤¤Ç¤·¤ç¤¦¡£¥¢¥É¥ì¥¹¤ÎºÆ³ä¤êÅö¤Æ¤¬É¬Í×ÉÔ²ÄÈò + ¤È¤Ê¤Ã¤Æ¤¤¤ëº£Æü¤Î¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Ë¤ª¤¤¤Æ¤Ï¡¢ + ÀßÄê¥Õ¥¡¥¤¥ë¤ÎÃæ¤ÇÌÀ¼¨Åª¤Ê IP ¥¢¥É¥ì¥¹¤òÍ׵᤹¤ë»ÅÍͤϡ¢ + Á´¤¯µ¹¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£

+ +

ÅðÍѤΥµ¡¼¥Ó¥¹¥¢¥¿¥Ã¥¯¤Ë´Ø¤·¤Æ¹Ô¤Ê¤¦¤Ù¤­»ö¤Ï¡¢ + DNS ½ç°ú¤­¤ò¹Ô¤Ê¤Ã¤ÆÆÀ¤é¤ì¤¿¥¢¥É¥ì¥¹¤ËÂФ¹¤ë DNS + µÕ°ú¤­¤ò¹Ô¤Ê¤Ã¤Æ¡¢Æó¤Ä¤Î̾Á°¤òÈæ³Ó¤¹¤ë¤³¤È¤Ç¤¹¡£ + ¤³¤ÎÆó¤Ä¤¬°ìÃפ·¤Ê¤±¤ì¤Ð¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ï̵¸ú¤Ë¤Ê¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ¤³¤¦¤¹¤ë¤¿¤á¤Ë¤ÏµÕ°ú¤­ DNS ¤¬Å¬ÀÚ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹ + (FTP ¥µ¡¼¥Ð¤ä TCP ¥é¥Ã¥Ñ¡¼¤Î¤ª¤«¤²¤Ç¡ÖÆó½ÅµÕ°ú¤­¡×DNS ¤Ï°ìÈÌŪ¤Ë + ¤Ê¤Ã¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢´ÉÍý¼Ô¤Ë¤Ï¤ªÆëÀ÷¤ß¤â¤Î¤Ç¤·¤ç¤¦)¡£

+ +

IP ¥¢¥É¥ì¥¹¤¬»ÈÍѤµ¤ì¤Æ¤¤¤Ê¤¯¤Æ DNS ¤¬¼ºÇÔ¤·¤¿¾ì¹ç¤Ï¡¢ + ¤É¤¦¤·¤Æ¤â¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¿®ÍêÀ­¤ò³ÎÊݤ·¤Æ + µ¯Æ°¤µ¤»¤ë¤³¤È¤ÏÉÔ²Äǽ¤Î¤è¤¦¤Ç¤¹¡£ + ÀßÄê¤Î°ìÉô¤ò̵¸ú¤Ë¤¹¤ë¤È¤¤¤¦¤è¤¦¤ÊÉôʬŪ¤Ê²ò·è¤Ç¤Ï¡¢ + ¥µ¡¼¥Ð¤¬²¿¤ò¤¹¤ë¤è¤¦¤Ë¤¹¤ë¤«¤Ë¤â¤è¤ê¤Þ¤¹¤¬¡¢ + ¤½¤Î¥µ¡¼¥Ð¤¬µ¯Æ°¤·¤Ê¤¤¤è¤ê³Î¼Â¤Ë°­¤¤¾õ¶·¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£

+ +

HTTP/1.1 ¤¬³«È¯¤µ¤ì¡¢¥Ö¥é¥¦¥¶¤ä¥×¥í¥­¥·¤¬ Host + ¥Ø¥Ã¥À¤òȯ¹Ô¤¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤¿¤Î¤Ç¡¢IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò + Á´¤¯»ÈÍѤ·¤Ê¤¯¤Æ¤âºÑ¤à¤è¤¦¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤³¤Î¾ì¹ç¡¢¥¦¥§¥Ö¥µ¡¼¥Ð¤ÏÀßÄêÃæ¤Ë DNS »²¾È¤ò¤·¤Ê¤¯¤Æ¤âºÑ¤ß¤Þ¤¹¡£ + ¤·¤«¤· 1997 ǯ 3 ·î»þÅÀ¤Î¾õ¶·¤Ç¤Ï¡¢ + ¾¦ÍÑ¥ì¥Ù¥ë¤Î¥¦¥§¥Ö¥µ¡¼¥Ð¤Ç»ÈÍѤǤ­¤ë¤Û¤É¤Ë¤Ï¡¢ + ¤³¤ì¤é¤Îµ¡Ç½¤Ï¹­¤¯³«È¯¤¬¿Ê¤ó¤Ç¤¤¤Þ¤»¤ó¡£

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/dns-caveats.html.ko.euc-kr b/docs/manual/dns-caveats.html.ko.euc-kr new file mode 100644 index 00000000..93c7d317 --- /dev/null +++ b/docs/manual/dns-caveats.html.ko.euc-kr @@ -0,0 +1,223 @@ + + + +DNS¿Í ¾ÆÆÄÄ¡¿Í °ü·ÃµÈ »çÇ× - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

DNS¿Í ¾ÆÆÄÄ¡¿Í °ü·ÃµÈ »çÇ×

+
+

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

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

ÀÌ ¹®¼­¸¦ ÇÑ ¹®ÀåÀ¸·Î ¿ä¾àÇÒ ¼ö ÀÖ´Ù. ¾ÆÆÄÄ¡°¡ ¼³Á¤ÆÄÀÏÀ» + ÀÐÀ»¶§ DNS¸¦ ÀÇÁ¸ÇÏÁö¾Êµµ·Ï Ç϶ó. ¾ÆÆÄÄ¡°¡ ¼³Á¤ÆÄÀÏÀ» Àдµ¥ + DNS°¡ ÇÊ¿äÇÏ´Ù¸é ¼­¹ö´Â ½Å·Ú¼º ¹®Á¦ (½ÃÀÛÀÌ ¾ÈµÉ ¼öµµ ÀÖ´Ù) + ȤÀº ¼­ºñ½º°ÅºÎ °ø°Ý°ú (»ç¿ëÀÚ°¡ ´Ù¸¥ »ç¿ëÀÚ¿¡ ´ëÇÑ Á¢±ÙÀ» + °¡·Îä´Â °ÍÀ» Æ÷ÇÔÇÏ¿©) ¼­ºñ½ºµµµÏ(theft of service) °ø°Ý¿¡ + ½Ã´Þ¸± ¼ö ÀÖ´Ù.

+
+ +
top
+
+

°£´ÜÇÑ ¿¹Á¦

+ + +

+ <VirtualHost www.abc.dom>
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+ +

¾ÆÆÄÄ¡°¡ Á¤»óÀûÀ¸·Î µ¿ÀÛÇϱâÀ§Çؼ­´Â °¢ °¡»óÈ£½ºÆ®¿¡ + ´ëÇØ µÎ°¡Áö Á¤º¸°¡ Àý´ëÀûÀ¸·Î ÇÊ¿äÇÏ´Ù. ÀÌ Á¤º¸´Â + ServerName°ú ¼­¹ö°¡ + ±â´Ù¸®°í ÀÀ´äÇÒ ÃÖ¼Ò ÇÑ°³ÀÇ IP ÁÖ¼ÒÀÌ´Ù. ÀÌ ¿¹´Â IP ÁÖ¼Ò°¡ + ¾ø±â¶§¹®¿¡, ¾ÆÆÄÄ¡´Â DNS¸¦ »ç¿ëÇÏ¿© www.abc.domÀÇ + ÁÖ¼Ò¸¦ ã¾Æ¾ß ÇÑ´Ù. ¼­¹ö°¡ ¼³Á¤ÆÄÀÏÀ» ÀÐÀ»¶§ ¾î¶² ÀÌÀ¯¿¡¼­°Ç + DNS¸¦ »ç¿ëÇÒ ¼ö ¾ø´Ù¸é °¡»óÈ£½ºÆ®¸¦ ¸¸µé ¼ö ¾ø´Ù. + ÀÌ °¡»óÈ£½ºÆ®´Â ¿äû¿¡ ÀÀ´äÇÒ ¼ö ¾ø´Ù. (¾ÆÆÄÄ¡ 1.2 ÀÌÀü + ¹öÀü¿¡¼­´Â ½ÉÁö¾î ¼­¹ö°¡ ºÎÆõµ ¾ÈÇÑ´Ù.)

+ +

www.abc.domÀÇ ÁÖ¼Ò°¡ 10.0.0.1À̶ó°í °¡Á¤ÇÏÀÚ. + ±×¸®°í ´ÙÀ½ ¼³Á¤À» º¸¶ó:

+ +

+ <VirtualHost 10.0.0.1>
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+ +

ÀÌÁ¦ ¾ÆÆÄÄ¡´Â ÀÌ °¡»óÈ£½ºÆ®ÀÇ ServerNameÀ» + ã±âÀ§ÇØ ¿ªDNS¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù. ¿ªÃ£±â°¡ ½ÇÆÐÇÏ¸é ¾ÆÆÄÄ¡´Â + °¡»óÈ£½ºÆ®¸¦ ºÎºÐÀûÀ¸·Î ²ö´Ù. (¾ÆÆÄÄ¡ 1.2 ÀÌÀü ¹öÀü¿¡¼­´Â + ½ÉÁö¾î ¼­¹ö°¡ ºÎÆõµ ¾ÈÇÑ´Ù.) Áï, ÀÌ °æ¿ì À̸§±â¹Ý + °¡»óÈ£½ºÆ®¶ó¸é °¡»óÈ£½ºÆ®´Â ¿ÏÀüÈ÷ µ¿ÀÛÇÏÁö¾Ê°í, ip±â¹ÝÀ̶ó¸é + ´ëºÎºÐ µ¿ÀÛÇÑ´Ù. ±×·¯³ª ¾ÆÆÄÄ¡°¡ ¼­¹ö¸íÀ» Æ÷ÇÔÇÏ¿© ¼­¹öÀÇ + Àüü URLÀ» ¸¸µé¾î¾ß ÇÑ´Ù¸é Á¤»óÀûÀÎ URLÀ» ¸¸µéÁö ¸øÇÑ´Ù.

+ +

¾Æ·¡ °æ¿ì ÀÌ µÎ°¡Áö ¹®Á¦°¡ ¾ø´Ù.

+ +

+ <VirtualHost 10.0.0.1>
+ ServerName www.abc.dom
+ ServerAdmin webgirl@abc.dom
+ DocumentRoot /www/abc
+ </VirtualHost> +

+
top
+
+

¼­ºñ½º°ÅºÎ (Denial of Service)

+ + +

(ÃÖ¼ÒÇÑ) µÎ°¡Áö Á¾·ùÀÇ ¼­ºñ½º°ÅºÎ°¡ ¹ß»ýÇÒ ¼ö ÀÖ´Ù. + ¾ÆÆÄÄ¡ 1.2 ÀÌÀü ¹öÀüÀÇ °æ¿ì ¾î¶² °¡»óÈ£½ºÆ®¿¡¼­¶óµµ + À§¿¡¼­ ¸»ÇÑ µÎ DNS °Ë»öÀÌ ½ÇÆÐÇÏ¸é ¼­¹ö°¡ ÄÑÁöÁöµµ ¾Ê´Â´Ù. + DNS°¡ ´ç½ÅÀÇ ±ÇÇÑ ¹ÛÀÇ ¹®Á¦ÀÏ ¼öµµ ÀÖ´Ù. ¿¹¸¦ µé¾î, + abc.domÀÌ °í°´ »çÀÌÆ®ÀÌ°í °í°´ÀÌ ÀÚ½ÅÀÇ DNS¸¦ + °ü¸®ÇÑ´Ù¸é, www.abc.dom ·¹Äڵ带 Áö¿ì±â¸¸ Çصµ + (1.2 ÀÌÀü) ¼­¹ö´Â ½ÃÀÛÇÏÁö ¸øÇÑ´Ù.

+ +

ÈξÀ ´õ ±³È°ÇÑ ¹æ¹ýµµ ÀÖ´Ù. ´ÙÀ½ ¼³Á¤À» »ìÆ캸ÀÚ:

+ +

+ <VirtualHost www.abc.dom>
+   ServerAdmin webgirl@abc.dom
+   DocumentRoot /www/abc
+ </VirtualHost>
+
+ <VirtualHost www.def.dom>
+   ServerAdmin webguy@def.dom
+   DocumentRoot /www/def
+ </VirtualHost> +

+ +

´ç½ÅÀÌ www.abc.dom¿¡ 10.0.0.1, + www.def.dom¿¡ 10.0.0.2¸¦ ÇÒ´çÇß´Ù°í ÇÏÀÚ. + ¶Ç, def.domÀº ÀÚü DNS¸¦ »ç¿ëÇÑ´Ù°í °¡Á¤ÇÏÀÚ. + ÀÌ ¼³Á¤°ú ÇÔ²² def.domÀ» abc.domÀ¸·Î + °¡´Â ¸ðµç Åë½ÅÀ» °¡·Îç ¼ö ÀÖ´Â Àå¼Ò¿¡ µÎ¾ú´Ù. ±×·¸´Ù¸é ±×µéÀº + www.def.domÀ» 10.0.0.1·Î ¼³Á¤Çϱ⸸ ÇÏ¸é µÈ´Ù. + ±×µéÀÌ ÀÚü DNS¸¦ »ç¿ëÇϱ⶧¹®¿¡ ´ç½ÅÀº ±×µéÀÌ ¿øÇϴµ¥·Î + www.def.dom ·¹Äڵ带 ¼³Á¤ÇÏ´Â °ÍÀ» ¸·À» ¼ö + ¾ø´Ù.

+ +

(»ç¿ëÀÚ°¡ http://www.abc.dom/whatever Çü½ÄÀÇ + URLÀ» ÀÔ·ÂÇÏ´Â °æ¿ì¸¦ Æ÷ÇÔÇÏ¿©) 10.0.0.1·Î ¿À´Â ¸ðµç ¿äûÀ» + def.dom °¡»óÈ£½ºÆ®°¡ ¼­ºñ½ºÇÏ°Ô µÈ´Ù. ¿Ö ÀÌ·± + ÀÏÀÌ ÀϾ´ÂÁö ÀÌÇØÇÏ·Á¸é ¾ÆÆÄÄ¡°¡ ¾î¶»°Ô °¡»óÈ£½ºÆ®·Î + ¿À´Â ¿äûÀ» ó¸®ÇÏ´ÂÁö¿¡ ´ëÇÑ ¼³¸íÀÌ ÇÊ¿äÇÏ´Ù. + ¿©±â¿¡ ´ë°­ ¼³¸íµÇÀÖ´Ù.

+
top
+
+

"ÁÖ¼­¹ö" ÁÖ¼Ò

+ + +

¾ÆÆÄÄ¡ 1.1¿¡¼­ À̸§±â¹Ý + °¡»óÈ£½ºÆ® Áö¿øÀÌ Æ÷ÇԵǾú±â¶§¹®¿¡ ¾ÆÆÄÄ¡´Â À¥¼­¹ö¸¦ + ½ÇÇàÇϴ ȣ½ºÆ®ÀÇ IP ÁÖ¼Ò(µé)¸¦ ¾Ë ÇÊ¿ä°¡ »ý°å´Ù. ÀÌ ÁÖ¼Ò´Â + (ÀÖ´Ù¸é) Àü¿ª ServerName + ȤÀº C ÇÔ¼ö gethostnameÀ¸·Î (¸í·ÉÇÁ·ÒÇÁÆ®¿¡ + "hostname"À» ÀÔ·ÂÇßÀ»¶§¿Í °°Àº °á°ú) ¾ò´Â´Ù. ±×·¯¸é ÀÌ ÁÖ¼Ò·Î + DNS °Ë»öÀ» ÇÑ´Ù. ÇöÀç ÀÌ °Ë»öÀº ÇÇÇÒ ¼ö ¾ø´Ù.

+ +

DNS ¼­¹ö°¡ Á׾ ÀÌ °Ë»öÀÌ ½ÇÆÐÇÒ °Í °°´Ù¸é + /etc/hosts¿¡ È£½ºÆ®¸íÀ» Áý¾î³ÖÀ» ¼ö ÀÖ´Ù. + (ÄÄÇ»ÅÍ°¡ Á¤»óÀûÀ¸·Î ºÎÆõǾú´Ù¸é ¾Æ¸¶ ÀÌ¹Ì µé¾îÀÖÀ» °ÍÀÌ´Ù.) + ±×¸®°í DNS°¡ ½ÇÆÐÇÏ¸é ¼­¹ö°¡ /etc/hosts¸¦ + »ç¿ëÇÏ´ÂÁö È®ÀÎÇ϶ó. »ç¿ëÇÏ´Â ¿î¿µÃ¼Á¦¿¡ µû¶ó + /etc/resolv.conf ȤÀº /etc/nsswitch.conf¸¦ + ¼öÁ¤ÇÏ¸é µÉ °ÍÀÌ´Ù.

+ +

¼­¹ö°¡ ¾î¶² ÀÌÀ¯¿¡¼­°Ç DNS¸¦ °Ë»öÇÏ¸é ¾ÈµÈ´Ù¸é + HOSTRESORDER ȯ°æº¯¼ö¸¦ "local"·Î ¼³Á¤ÇÏ°í + ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Ù. mod_env¸¦ + »ç¿ëÇÏ¿© ȯ°æÀ» º¯°æÇÏÁö ¾Ê´Â´Ù¸é ÀÌ È¯°æº¯¼ö´Â + CGI¿¡µµ ¿µÇâÀ» ÁØ´Ù. ¿î¿µÃ¼Á¦ÀÇ manpage³ª FAQ¸¦ Âü°íÇÏ´Â + °ÍÀÌ ÁÁ´Ù.

+
top
+
+

ÀÌ ¹®Á¦¸¦ ÇÇÇϱâÀ§ÇÑ ÆÁ

+ + +
    +
  • + VirtualHost¿¡ IP + ÁÖ¼Ò¸¦ »ç¿ëÇ϶ó +
    • + +
  • + Listen¿¡ + IP ÁÖ¼Ò¸¦ »ç¿ëÇ϶ó +
    • + +
  • + ¸ðµç °¡»óÈ£½ºÆ®´Â ¸í½ÃÀûÀ¸·Î + ServerNameÀ» + °¡Áö°Ô Ç϶ó +
    • + +
  • ¾î¶² ÆäÀÌÁöµµ ¼­ºñ½ºÇÏÁö¾Ê´Â + <VirtualHost _default_:*> ¼­¹ö¸¦ + ¸¸µé¾î¶ó
    • +
+
top
+
+

ºÎ·Ï: ¾ÕÀ¸·Î´Â

+ + +

DNS¿Í °ü·ÃµÈ »óȲÀº ¸Å¿ì ¹Ù¶÷Á÷ÇÏÁö ¸øÇÏ´Ù. ¾ÆÆÄÄ¡ 1.2¿¡¼­ + ¿ì¸®´Â DNS°¡ ½ÇÆÐÇÑ °æ¿ì¿¡µµ ÃÖ¼ÒÇÑ ¼­¹ö°¡ ÄÑÁöµµ·Ï ³ë·ÂÇßÁö¸¸ + °á°ú´Â ³ª»¦´Ù. ¾î·µç ¼³Á¤ÆÄÀÏ¿¡ Á÷Á¢ IP ÁÖ¼Ò¸¦ ¿ä±¸ÇÏ´Â + °ÍÀº ¹øÈ£¸¦ ´Ù½Ã ¼³Á¤ÇؾßÇÒ ¿äÁò ÀÎÅͳݿ¡ ¸Å¿ì ¹Ù¶÷Á÷ÇÏÁö + ¸øÇÏ´Ù.

+ +

À§¿¡¼­ ¼³¸íÇÑ ¼­ºñ½ºµµµÏ °ø°ÝÀ» ¸·´Â ÇÑ°¡Áö ¹æ¹ýÀº °Ë»öÇÑ + IP ÁÖ¼Ò¿¡ ´Ù½Ã ¿ªDNS °Ë»öÀ» ÇÏ¿© µÎ À̸§À» ºñ±³ÇÏ´Â °ÍÀÌ´Ù. + ¼­·Î ´Ù¸¥ °æ¿ì °¡»óÈ£½ºÆ®¸¦ °¡µ¿ÇÏÁö ¾ÊÀ» ¼ö ÀÖ´Ù. ÀÌ ¹æ¹ýÀº + ¿ªDNS°¡ ¿Ã¹Ù·Î ¼³Á¤µÇ¾ß ÇÑ´Ù. (FTP ¼­¹ö³ª TCP wrapper°¡ + "Áߺ¹-¿ª" DNS °Ë»öÀ» ÀÚÁÖ »ç¿ëÇϱ⶧¹®¿¡ ´ëºÎºÐÀÇ °ü¸®ÀÚ¿¡°Ô + Àͼ÷ÇÒ °ÍÀÌ´Ù.)

+ +

¾î·µç IP ÁÖ¼Ò¸¦ »ç¿ëÇÏÁö¾ÊÀ¸¸é DNS°¡ ½ÇÆÐÇÑ °æ¿ì °¡»óÈ£½ºÆ® + À¥¼­¹ö¸¦ ¹ÏÀ» ¼ö ÀÖ°Ô ½ÃÀÛÇÒ ¼ö ¾ø´Ù. ¼³Á¤ÀÇ ÀϺθ¦ ¹«½ÃÇÏ´Â + °Í°ú °°Àº ºÎºÐÀûÀÎ ÇØ°áÃ¥Àº À¥¼­¹ö Àüü¸¦ ½ÃÀÛÇÏÁö¾Ê´Â °Íº¸´Ù + ´õ ³ª»Ü ¼öµµ ÀÖ´Ù.

+ +

HTTP/1.1ÀÌ ³ª¿Ô°í ºê¶ó¿ìÀú¿Í ÇÁ·Ï½Ã°¡ Host + Çì´õ¸¦ º¸³»±â ½ÃÀÛÇßÀ¸¹Ç·Î IP±â¹Ý °¡»óÈ£½ºÆ®¸¦ ¿ÏÀüÈ÷ + »ç¿ëÇÏÁö¾Ê´Â °ÍÀÌ °¡´ÉÇØÁú °ÍÀÌ´Ù. ±×·¯¸é À¥¼­¹ö´Â ¼³Á¤Áß¿¡¼­ + DNS °Ë»öÀ» ÇÒ ÇÊ¿ä°¡ ¾ø¾îÁø´Ù. ±×·¯³ª 1997³â 3¿ù¿¡´Â Áß¿äÇÑ + À¥¼­¹ö¿¡ Æ÷ÇÔÇÒ Á¤µµ·Î À̸§±â¹Ý °¡»óÈ£½ºÆ®°¡ ³Î¸® »ç¿ëµÇÁö + ¾Ê¾Ò´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/dso.html b/docs/manual/dso.html new file mode 100644 index 00000000..3d86148e --- /dev/null +++ b/docs/manual/dso.html @@ -0,0 +1,11 @@ +URI: dso.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: dso.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: dso.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/dso.html.en b/docs/manual/dso.html.en new file mode 100644 index 00000000..9e64d883 --- /dev/null +++ b/docs/manual/dso.html.en @@ -0,0 +1,315 @@ + + + +Dynamic Shared Object (DSO) Support - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Dynamic Shared Object (DSO) Support

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

The Apache HTTP Server is a modular program where the + administrator can choose the functionality to include in the + server by selecting a set of modules. The modules can be + statically compiled into the httpd binary when the + server is built. Alternatively, modules can be compiled as + Dynamic Shared Objects (DSOs) that exist separately from the + main httpd binary file. DSO modules may be + compiled at the time the server is built, or they may be + compiled and added at a later time using the Apache Extension + Tool (apxs).

+ +

This document describes how to use DSO modules as well as + the theory behind their use.

+
+ +
top
+
+

Implementation

+ +
Related ModulesRelated Directives
+ +

The DSO support for loading individual Apache modules is based + on a module named mod_so which must be statically + compiled into the Apache core. It is the only module besides + core which cannot be put into a DSO + itself. Practically all other distributed Apache modules can then + be placed into a DSO by individually enabling the DSO build for + them via configure's + --enable-module=shared option as discussed + in the install documentation. After a + module is compiled into a DSO named mod_foo.so you + can use mod_so's LoadModule command in your + httpd.conf file to load this module at server startup + or restart.

+ +

To simplify this creation of DSO files for Apache modules + (especially for third-party modules) a new support program + named apxs (APache + eXtenSion) is available. It can be used to build DSO based + modules outside of the Apache source tree. The idea is + simple: When installing Apache the configure's + make install procedure installs the Apache C + header files and puts the platform-dependent compiler and + linker flags for building DSO files into the apxs + program. This way the user can use apxs to compile + his Apache module sources without the Apache distribution + source tree and without having to fiddle with the + platform-dependent compiler and linker flags for DSO + support.

+
top
+
+

Usage Summary

+ +

To give you an overview of the DSO features of Apache 2.0, + here is a short and concise summary:

+ +
    +
  1. + Build and install a distributed Apache module, say + mod_foo.c, into its own DSO + mod_foo.so: + +

    +$ ./configure --prefix=/path/to/install --enable-foo=shared
    +$ make install +

    +
    2. + +
  2. + Build and install a third-party Apache module, say + mod_foo.c, into its own DSO + mod_foo.so: + +

    +$ ./configure --add-module=module_type:/path/to/3rdparty/mod_foo.c \
    + + --enable-foo=shared
    +     +$ make install +

    +
    3. + +
  3. + Configure Apache for later installation of shared + modules: + +

    +$ ./configure --enable-so
    +$ make install +

    +
    4. + +
  4. + Build and install a third-party Apache module, say + mod_foo.c, into its own DSO + mod_foo.so outside of the Apache + source tree using apxs: + +

    +$ cd /path/to/3rdparty
    +$ apxs -c mod_foo.c
    +$ apxs -i -a -n foo mod_foo.la +

    +
    5. +
+ +

In all cases, once the shared module is compiled, you must + use a LoadModule + directive in httpd.conf to tell Apache to activate + the module.

+
top
+
+

Background

+ +

On modern Unix derivatives there exists a nifty mechanism + usually called dynamic linking/loading of Dynamic Shared + Objects (DSO) which provides a way to build a piece of + program code in a special format for loading it at run-time + into the address space of an executable program.

+ +

This loading can usually be done in two ways: Automatically + by a system program called ld.so when an + executable program is started or manually from within the + executing program via a programmatic system interface to the + Unix loader through the system calls + dlopen()/dlsym().

+ +

In the first way the DSO's are usually called shared + libraries or DSO libraries and named + libfoo.so or libfoo.so.1.2. They + reside in a system directory (usually /usr/lib) + and the link to the executable program is established at + build-time by specifying -lfoo to the linker + command. This hard-codes library references into the executable + program file so that at start-time the Unix loader is able to + locate libfoo.so in /usr/lib, in + paths hard-coded via linker-options like -R or in + paths configured via the environment variable + LD_LIBRARY_PATH. It then resolves any (yet + unresolved) symbols in the executable program which are + available in the DSO.

+ +

Symbols in the executable program are usually not referenced + by the DSO (because it's a reusable library of general code) + and hence no further resolving has to be done. The executable + program has no need to do anything on its own to use the + symbols from the DSO because the complete resolving is done by + the Unix loader. (In fact, the code to invoke + ld.so is part of the run-time startup code which + is linked into every executable program which has been bound + non-static). The advantage of dynamic loading of common library + code is obvious: the library code needs to be stored only once, + in a system library like libc.so, saving disk + space for every program.

+ +

In the second way the DSO's are usually called shared + objects or DSO files and can be named with an + arbitrary extension (although the canonical name is + foo.so). These files usually stay inside a + program-specific directory and there is no automatically + established link to the executable program where they are used. + Instead the executable program manually loads the DSO at + run-time into its address space via dlopen(). At + this time no resolving of symbols from the DSO for the + executable program is done. But instead the Unix loader + automatically resolves any (yet unresolved) symbols in the DSO + from the set of symbols exported by the executable program and + its already loaded DSO libraries (especially all symbols from + the ubiquitous libc.so). This way the DSO gets + knowledge of the executable program's symbol set as if it had + been statically linked with it in the first place.

+ +

Finally, to take advantage of the DSO's API the executable + program has to resolve particular symbols from the DSO via + dlsym() for later use inside dispatch tables + etc. In other words: The executable program has to + manually resolve every symbol it needs to be able to use it. + The advantage of such a mechanism is that optional program + parts need not be loaded (and thus do not spend memory) until + they are needed by the program in question. When required, + these program parts can be loaded dynamically to extend the + base program's functionality.

+ +

Although this DSO mechanism sounds straightforward there is + at least one difficult step here: The resolving of symbols from + the executable program for the DSO when using a DSO to extend a + program (the second way). Why? Because "reverse resolving" DSO + symbols from the executable program's symbol set is against the + library design (where the library has no knowledge about the + programs it is used by) and is neither available under all + platforms nor standardized. In practice the executable + program's global symbols are often not re-exported and thus not + available for use in a DSO. Finding a way to force the linker + to export all global symbols is the main problem one has to + solve when using DSO for extending a program at run-time.

+ +

The shared library approach is the typical one, because it + is what the DSO mechanism was designed for, hence it is used + for nearly all types of libraries the operating system + provides. On the other hand using shared objects for extending + a program is not used by a lot of programs.

+ +

As of 1998 there are only a few software packages available + which use the DSO mechanism to actually extend their + functionality at run-time: Perl 5 (via its XS mechanism and the + DynaLoader module), Netscape Server, etc. Starting + with version 1.3, Apache joined the crew, because Apache + already uses a module concept to extend its functionality and + internally uses a dispatch-list-based approach to link external + modules into the Apache core functionality. So, Apache is + really predestined for using DSO to load its modules at + run-time.

+
top
+
+

Advantages and Disadvantages

+ +

The above DSO based features have the following + advantages:

+ +
    +
  • The server package is more flexible at run-time because + the actual server process can be assembled at run-time via + LoadModule + httpd.conf configuration commands instead of + configure options at build-time. For instance + this way one is able to run different server instances + (standard & SSL version, minimalistic & powered up + version [mod_perl, PHP3], etc.) with only one Apache + installation.
    • + +
  • The server package can be easily extended with + third-party modules even after installation. This is at least + a great benefit for vendor package maintainers who can create + a Apache core package and additional packages containing + extensions like PHP3, mod_perl, mod_fastcgi, + etc.
    • + +
  • Easier Apache module prototyping because with the + DSO/apxs pair you can both work outside the + Apache source tree and only need an apxs -i + command followed by an apachectl restart to + bring a new version of your currently developed module into + the running Apache server.
    • +
+ +

DSO has the following disadvantages:

+ +
    +
  • The DSO mechanism cannot be used on every platform + because not all operating systems support dynamic loading of + code into the address space of a program.
    • + +
  • The server is approximately 20% slower at startup time + because of the symbol resolving overhead the Unix loader now + has to do.
    • + +
  • The server is approximately 5% slower at execution time + under some platforms because position independent code (PIC) + sometimes needs complicated assembler tricks for relative + addressing which are not necessarily as fast as absolute + addressing.
    • + +
  • Because DSO modules cannot be linked against other + DSO-based libraries (ld -lfoo) on all platforms + (for instance a.out-based platforms usually don't provide + this functionality while ELF-based platforms do) you cannot + use the DSO mechanism for all types of modules. Or in other + words, modules compiled as DSO files are restricted to only + use symbols from the Apache core, from the C library + (libc) and all other dynamic or static libraries + used by the Apache core, or from static library archives + (libfoo.a) containing position independent code. + The only chances to use other code is to either make sure the + Apache core itself already contains a reference to it or + loading the code yourself via dlopen().
    • +
+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/dso.html.ja.euc-jp b/docs/manual/dso.html.ja.euc-jp new file mode 100644 index 00000000..d01d393e --- /dev/null +++ b/docs/manual/dso.html.ja.euc-jp @@ -0,0 +1,296 @@ + + + +ưŪ¶¦Í­¥ª¥Ö¥¸¥§¥¯¥È (DSO) ¥µ¥Ý¡¼¥È - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

ưŪ¶¦Í­¥ª¥Ö¥¸¥§¥¯¥È (DSO) ¥µ¥Ý¡¼¥È

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

Apache HTTP ¥µ¡¼¥Ð¤Ï¥â¥¸¥å¡¼¥ë²½¤µ¤ì¤¿¥×¥í¥°¥é¥à¤Ç¡¢ + ´ÉÍý¼Ô¤¬¥â¥¸¥å¡¼¥ë¤òÁªÂò¤¹¤ë¤³¤È¤Ç¥µ¡¼¥Ð¤ËÁȤ߹þ¤àµ¡Ç½¤òÁª¤Ö¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥â¥¸¥å¡¼¥ë¤Ï¥µ¡¼¥Ð¤¬¥Ó¥ë¥É¤µ¤ì¤ë¤È¤­¤Ë httpd ¥Ð¥¤¥Ê¥ê¤Ë + ÀÅŪ¤ËÁȤ߹þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤â¤·¤¯¤Ï¡¢httpd ¥Ð¥¤¥Ê¥ê¤È¤Ï + Ê̤˸ºß¤¹¤ëưŪ¶¦Í­¥ª¥Ö¥¸¥§¥¯¥È (ÌõÃí: Dynamic Shared Object) + (DSO) ¤È¤·¤Æ¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤³¤È¤â + ¤Ç¤­¤Þ¤¹¡£DSO ¥â¥¸¥å¡¼¥ë¤Ï¥µ¡¼¥Ð¤¬¥Ó¥ë¥É¤µ¤ì¤ë¤È¤­¤Ë¥³¥ó¥Ñ¥¤¥ë¤·¤¿¤ê¡¢ + Apache ³ÈÄ¥¥Ä¡¼¥ë (apxs) ¤ò + »È¤Ã¤Æ¸å¤Ç¥³¥ó¥Ñ¥¤¥ë¤·¤ÆÄɲä·¤¿¤ê¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤Îʸ½ñ¤Ï DSO ¥â¥¸¥å¡¼¥ë¤Î»È¤¤Êý¤È¡¢»ÅÁȤߤˤĤ¤¤Æ + ÀâÌÀ¤·¤Þ¤¹¡£

+
+ +
top
+
+

¼ÂÁõ

+ +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

¸Ä¡¹¤Î Apache ¥â¥¸¥å¡¼¥ë¤ò¥í¡¼¥É¤¹¤ë¤¿¤á¤Î DSO ¥µ¥Ý¡¼¥È¤Ï + mod_so.c ¤È¤¤¤¦¥â¥¸¥å¡¼¥ë¤Îµ¡Ç½¤Ë´ð¤Å¤¤¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¥â¥¸¥å¡¼¥ë ¤Ï Apache ¤Î¥³¥¢¤ËÀÅŪ¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤½¤ì¤Ï core.c °Ê³°¤Ç¤Ï DSO ¤Ë¤Ç¤­¤Ê¤¤Í£°ì¤Î + ¥â¥¸¥å¡¼¥ë¤Ç¤¹¡£»ö¼Â¾å¡¢Â¾¤Î¤¹¤Ù¤Æ¤Î Apache ¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢ + ¥¤¥ó¥¹¥È¡¼¥ë¤Îʸ½ñ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¡¢ + configure ¤Î + --enable-module=shared ¥ª¥×¥·¥ç¥ó¤Ç¤½¤ì¤¾¤ì¤ò + DSO ¥Ó¥ë¥É¤Ë¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢DSO ¥â¥¸¥å¡¼¥ë¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + mod_foo.so ¤Î¤è¤¦¤Ê DSO ¤Ë¥â¥¸¥å¡¼¥ë¤¬¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤ì¤Ð¡¢ + httpd.conf ¥Õ¥¡¥¤¥ëÃæ¤Ç mod_so ¤Î + LoadModule + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤³¤È¤Ç¥µ¡¼¥Ð¤Îµ¯Æ°¤äºÆµ¯Æ°»þ¤Ë¤³¤Î¥â¥¸¥å¡¼¥ë¤ò + ¥í¡¼¥É¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£

+ +

Apache ¥â¥¸¥å¡¼¥ëÍѤΠ(Æä˥µ¡¼¥É¥Ñ¡¼¥Æ¥£¥â¥¸¥å¡¼¥ë¤Î) DSO ¥Õ¥¡¥¤¥ë¤Î + ºîÀ®¤ò´Êñ¤Ë¤¹¤ë¤¿¤á¤Ë¡¢apxs + (APache eXtenSion) ¤È¤¤¤¦¿·¤·¤¤¥µ¥Ý¡¼¥È¥×¥í¥°¥é¥à¤¬¤¢¤ê¤Þ¤¹¡£ + Apache ¤Î¥½¡¼¥¹¥Ä¥ê¡¼¤Î³°¤Ç DSO ¥â¥¸¥å¡¼¥ë¤ò¥Ó¥ë¥É¤¹¤ë¤¿¤á¤Ë + »È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£È¯ÁÛ¤Ïñ½ã¤Ç¤¹: Apache ¤Î¥¤¥ó¥¹¥È¡¼¥ë»þ¤Î + configure¡¢make install ¤Î¤È¤­¤Ë Apache ¤Î + C ¥Ø¥Ã¥À¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢DSO ¥Ó¥ë¥ÉÍѤΥץé¥Ã¥È¥Õ¥©¡¼¥à°Í¸¤Î + ¥³¥ó¥Ñ¥¤¥é¤È¥ê¥ó¥«¤Î¥Õ¥é¥°¤ò apxs ¥×¥í¥°¥é¥à¤ËÄɲä·¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¥æ¡¼¥¶¤¬ Apache ¤ÎÇÛÉÛ¥½¡¼¥¹¥Ä¥ê¡¼¤Ê¤·¤Ç¡¢¤µ¤é¤Ë + DSO ¥µ¥Ý¡¼¥È¤Î¤¿¤á¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à°Í¸¤Î¥³¥ó¥Ñ¥¤¥é¤ä¥ê¥ó¥«¤Î + ¥Õ¥é¥°¤ò¤¤¤¸¤ë¤³¤È¤Ê¤¯ Apache ¤Î¥â¥¸¥å¡¼¥ë¤Î¥½¡¼¥¹¤ò¥³¥ó¥Ñ¥¤¥ë + ¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+
top
+
+

»ÈÍÑË¡¤Î³µÍ×

+ +

Apache 2.0 ¤Î DSO µ¡Ç½¤Î³µÎ¬¤òÃΤ뤳¤È¤¬¤Ç¤­¤ë¤¿¤á¤Î¡¢ + û¤¯´Ê·é¤Ê³µÍפǤ¹:

+ +
    +
  1. + ÇÛÉÛ¤µ¤ì¤Æ¤¤¤ë Apache ¥â¥¸¥å¡¼¥ë¡¢²¾¤Ë mod_foo.c + ¤È¤·¤Æ¡¢¤½¤ì¤ò DSO mod_foo.so ¤Ë¥Ó¥ë¥É¡¢¥¤¥ó¥¹¥È¡¼¥ë: + +

    +$ ./configure --prefix=/path/to/install --enable-foo=shared
    +$ make install +

    +
    2. + +
  2. + ¥µ¡¼¥É¥Ñ¡¼¥Æ¥£ Apache ¥â¥¸¥å¡¼¥ë¡¢²¾¤Ë mod_foo.c + ¤È¤·¤Æ¡¢¤½¤ì¤ò DSO mod_foo.so ¤Ë¥Ó¥ë¥É¡¢¥¤¥ó¥¹¥È¡¼¥ë: + +

    +$ ./configure --add-module=module_type:/path/to/3rdparty/mod_foo.c \
    + + --enable-foo=shared
    +     +$ make install +

    +
    3. + +
  3. + ¶¦Í­¥â¥¸¥å¡¼¥ë¤Î ¸å¡¹¤Î¥¤¥ó¥¹¥È¡¼¥ë ¤Î¤¿¤á¤Ë + Apache ¤òÀßÄê: + +

    +$ ./configure --enable-so
    +$ make install +

    +
    4. + +
  4. + ¥µ¡¼¥É¥Ñ¡¼¥Æ¥£ Apache ¥â¥¸¥å¡¼¥ë¡¢²¾¤Ë mod_foo.c + ¤È¤·¤Æ¡¢¤½¤ì¤ò apxs ¤ò»È¤Ã¤Æ + Apache ¥½¡¼¥¹¥Ä¥ê¡¼¤Î³°¤Ç DSO ¤Ë¥Ó¥ë¥É¡¢¥¤¥ó¥¹¥È¡¼¥ë: + +

    +$ cd /path/to/3rdparty
    +$ apxs -c mod_foo.c
    +$ apxs -i -a -n foo mod_foo.la +

    +
    5. +
+ +

¤É¤Î¾ì¹ç¤Ë¤ª¤¤¤Æ¤â¡¢¶¦Í­¥â¥¸¥å¡¼¥ë¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤¿¸å¤Ç¡¢ + httpd.conf ¤Ç + LoadModule + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ Apache ¤¬¥â¥¸¥å¡¼¥ë¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë + ¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
top
+
+

ÇØ·Ê

+ +

ºÇ¶á¤Î Unix ·Ï¤Î OS ¤Ë¤Ï ưŪ¶¦Í­¥ª¥Ö¥¸¥§¥¯¥È (DSO) + ¤ÎưŪ¥ê¥ó¥¯/¥í¡¼¥É¤È¤¤¤¦µ¤¤Î¤­¤¤¤¿µ¡¹½¤¬ + ¸ºß¤·¤Þ¤¹¡£¤³¤ì¤Ï¡¢¼Â¹Ô»þ¤Ë¥×¥í¥°¥é¥à¤Î¥¢¥É¥ì¥¹¶õ´Ö¤Ë + ¥í¡¼¥É¤Ç¤­¤ë¤è¤¦¤ÊÆÃÊ̤ʷÁ¼°¤Ç¥×¥í¥°¥é¥à¤ò¥Ó¥ë¥É¤¹¤ë¤³¤È¤ò + ²Äǽ¤Ë¤·¤Þ¤¹¡£

+ +

¤³¤Î¥í¡¼¥É¤ÏÆó¤Ä¤ÎÊýË¡¤Ç¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹: ¼Â¹Ô¥×¥í¥°¥é¥à¤¬ + µ¯Æ°¤µ¤ì¤¿¤È¤­¤Ë ld.so ¤È¤¤¤¦¥·¥¹¥Æ¥à¥×¥í¥°¥é¥à + ¤Ë¤è¤ê¼«Æ°Åª¤Ë¹Ô¤Ê¤ï¤ì¤ëÊýË¡¤È¡¢¼Â¹Ô¥×¥í¥°¥é¥àÃ椫¤é¡¢¥·¥¹¥Æ¥à¥³¡¼¥ë + dlopen()/dlsym() ¤Ë¤è¤ë Unix ¥í¡¼¥À¤Ø¤Î + ¥×¥í¥°¥é¥à¥·¥¹¥Æ¥à¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»È¤Ã¤Æ¼êÆ°¤Ç¹Ô¤Ê¤¦ÊýË¡¤È¤¬ + ¤¢¤ê¤Þ¤¹¡£

+ +

ºÇ½é¤ÎÊýË¡¤Ç¤Ï DSO ¤ÏÉáÄ̤϶¦Í­¥é¥¤¥Ö¥é¥ê¤ä DSO + ¥é¥¤¥Ö¥é¥ê ¤È¸Æ¤Ð¤ì¤Æ¤¤¤Æ¡¢DSO ¤Î̾Á°¤Ï + libfoo.so ¤ä libfoo.so.1.2 ¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¤³¤ì¤é¤Ï¥·¥¹¥Æ¥à¥Ç¥£¥ì¥¯¥È¥ê (Ä̾ï /usr/lib) ¤Ë¸ºß¤·¡¢ + ¼Â¹Ô¥×¥í¥°¥é¥à¤Ø¤Î¥ê¥ó¥¯¤Ï¥Ó¥ë¥É»þ¤Ë -lfoo ¤ò¥ê¥ó¥«¤Ë + »ØÄꤹ¤ë¤³¤È¤Ç³ÎΩ¤µ¤ì¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¥é¥¤¥Ö¥é¥ê¤Ø¤Î»²¾È¤¬¼Â¹Ô¥×¥í¥°¥é¥à¤Î + ¥Õ¥¡¥¤¥ë¤Ë½ñ¤­¹þ¤Þ¤ì¤Æ¡¢µ¯Æ°»þ¤Ë Unix ¤Î¥í¡¼¥À¤¬ /usr/lib ¤ä¡¢ + ¥ê¥ó¥«¤Î -R ¤Î¤è¤¦¤Ê¥ª¥×¥·¥ç¥ó¤Ë¤è¤ê¥Ï¡¼¥É¥³¡¼¥É¤µ¤ì¤¿¥Ñ¥¹¡¢ + ´Ä¶­ÊÑ¿ô LD_LIBRARY_PATH ¤Ë¤è¤êÀßÄꤵ¤ì¤¿¥Ñ¥¹¡¢¤ÎÃ椫¤é + libfoo.so ¤Î¾ì½ê¤ò¸«¤Ä¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤½¤ì¤«¤é¡¢ + ¼Â¹Ô¥×¥í¥°¥é¥àÃæ¤Î (¤Þ¤À̤²ò·è¤Î) ¥·¥ó¥Ü¥ë¤ò DSO ¤Ë¤¢¤ë¥·¥ó¥Ü¥ë¤Ç + ²ò·è¤·¤Þ¤¹¡£

+ +

ÉáÄÌ¤Ï¼Â¹Ô¥×¥í¥°¥é¥àÃæ¤Î¥·¥ó¥Ü¥ë¤Ï DSO ¤«¤é¤Ï»²¾È¤µ¤ì¤Þ¤»¤ó + (DSO ¤Ï°ìÈÌŪ¤Ê¥³¡¼¥É¤Ë¤è¤ëºÆÍøÍѲÄǽ¤Ê¥é¥¤¥Ö¥é¥ê¤Ç¤¹¤Î¤Ç)¡£ + ¤Ç¤¹¤«¤é¡¢¤µ¤é¤Ê¤ë¥·¥ó¥Ü¥ë¤Î²ò·è¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£ + ¥·¥ó¥Ü¥ë¤Ï Unix ¥í¡¼¥À¤Ë¤è¤ê´°Á´¤Ê²ò·è¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¤Î¤Ç¡¢¼Â¹Ô¥Õ¥¡¥¤¥ë¼«¿È¤Ï + ²¿¤â¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤»¤ó¡£(¼ÂºÝ¤Î¤È¤³¤í¡¢ÀÅŪ¤Ç¤Ê¤¤ÊýË¡¤Ç¥ê¥ó¥¯¤µ¤ì¤Æ¤¤¤ë + ¤¹¤Ù¤Æ¤Î¼Â¹Ô¥×¥í¥°¥é¥à¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë³«»ÏÍѤΥ³¡¼¥É¤Î°ìÉô¤Ë + ld.so ¤òµ¯Æ°¤¹¤ë¥³¡¼¥É¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹)¡£¤è¤¯»È¤ï¤ì¤ë + ¥é¥¤¥Ö¥é¥ê¤ÎưŪ¥í¡¼¥É¤ÎÍøÅÀ¤ÏÌÀ¤é¤«¤Ç¤¹¡£¥é¥¤¥Ö¥é¥ê¤Î¥³¡¼¥É¤Ï + ¥·¥¹¥Æ¥à¥é¥¤¥Ö¥é¥ê¤Ë libc.so ¤Î¤è¤¦¤Ë¤·¤Æ°ìÅÙÊݸ¤¹¤ë¤À¤±¤Ç¤è¤¯¡¢ + ¥×¥í¥°¥é¥à¤Î¤¿¤á¤ËɬÍפʥǥ£¥¹¥¯¤ÎÎΰè¤òÀáÌ󤹤뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Æó¤Ä¤á¤ÎÊýË¡¤Ç¤Ï DSO ¤ÏÉáÄ̤϶¦Í­¥ª¥Ö¥¸¥§¥¯¥È¤ä + DSO ¥Õ¥¡¥¤¥ë¤È¸Æ¤Ð¤ì¤Æ¤¤¤Æ¡¢Ç¤°Õ¤Î³ÈÄ¥»Ò¤òÉÕ¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹ + (¤¿¤À¤·¡¢É¸½àŪ¤Ê̾Á°¤Ï foo.so ¤Ç¤¹)¡£ + ¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤ÏÄ̾ï¤Ï¥×¥í¥°¥é¥àÀìÍѤΥǥ£¥ì¥¯¥È¥ê¤ËÃÖ¤«¤ì¡¢ + ¤³¤ì¤é¤ò»È¤¦¼Â¹Ô¥×¥í¥°¥é¥à¤Ø¤Î¥ê¥ó¥¯¤Ï¼«Æ°Åª¤Ë¤Ï¤µ¤ì¤Þ¤»¤ó¡£ + ¤Ç¤¹¤Î¤Ç¡¢¼Â¹Ô¥×¥í¥°¥é¥à¤Ï dlopen() ¤ò»È¤Ã¤Æ + ¼Â¹Ô»þ¤Ë¼êÆ°¤Ç DSO ¤ò¥×¥í¥°¥é¥à¤Î¥¢¥É¥ì¥¹¶õ´Ö¤Ë¥í¡¼¥É¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î»þÅÀ¤Ç¤Ï¼Â¹Ô¥×¥í¥°¥é¥à¤ËÂФ·¤Æ DSO ¤Î¥·¥ó¥Ü¥ë¤Î²ò·è¤Ï¹Ô¤Ê¤ï¤ì¤Þ¤»¤ó¡£ + ¤·¤«¤·¡¢¤½¤ÎÂå¤ï¤ê¤Ë Unix ¤Î¥í¡¼¥À¤¬ DSO ¤Î (¤Þ¤À̤²ò·è¤Î) ¥·¥ó¥Ü¥ë¤ò + ¼Â¹Ô¥×¥í¥°¥é¥à¤Ë¤è¤ê¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤¿¥·¥ó¥Ü¥ë¤È´û¤Ë¥í¡¼¥É¤µ¤ì¤¿ + DSO ¥é¥¤¥Ö¥é¥ê¤Ë¤è¤ê¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤¿¥·¥ó¥Ü¥ë (Æäˡ¢¤É¤³¤Ë¤Ç¤â¤¢¤ë + libc.so ¤Î¤¹¤Ù¤Æ¤Î¥·¥ó¥Ü¥ë) ¤Ç¼«Æ°Åª¤Ë²ò·è¤·¤Þ¤¹¡£ + ¤³¤¦¤¹¤ë¤³¤È¤Ç¡¢DSO ¤ÏºÇ½é¤«¤éÀÅŪ¤Ë¥ê¥ó¥¯¤µ¤ì¤Æ¤¤¤¿¤«¤Î¤è¤¦¤Ë¡¢ + ¼Â¹Ô¥×¥í¥°¥é¥à¤Î¥·¥ó¥Ü¥ë¤òÃΤ뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

ºÇ¸å¤Ë¡¢DSO ¤Î API ¤òÍøÅÀ¤òÀ¸¤«¤¹¤¿¤á¤Ë¡¢¥×¥í¥°¥é¥à¤Ï + ¸å¤Ç¥Ç¥£¥¹¥Ñ¥Ã¥Á¥Æ¡¼¥Ö¥ë¤Ê¤É¤Ç¥·¥ó¥Ü¥ë¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¡¢ + dlsym() ¤ò»È¤Ã¤Æ¤¤¤¯¤Ä¤«¤Î¥·¥ó¥Ü¥ë¤ò²ò·è¤·¤Þ¤¹¡£ + ¤¹¤Ê¤ï¤Á: ¼Â¹Ô¥×¥í¥°¥é¥à¤ÏɬÍפʤ¹¤Ù¤Æ¤Î¥·¥ó¥Ü¥ë¤ò¼êÆ°¤Ç²ò·è¤·¤Ê¤±¤ì¤Ð + ¤Ê¤ê¤Þ¤»¤ó¡£¤³¤Îµ¡¹½¤ÎÍøÅÀ¤Ï¥×¥í¥°¥é¥à¤Î¥ª¥×¥·¥ç¥Ê¥ë¤ÊÉôʬ¤Ï + ɬÍפˤʤë¤Þ¤Ç¥í¡¼¥É¤¹¤ëɬÍפ¬¤Ê¤¤ (¤À¤«¤é¥á¥â¥ê¤â¾ÃÈñ¤·¤Ê¤¤) + ¤³¤È¤Ç¤¹¡£É¬Íפʤé¤Ð¡¢´ðËÜ¥×¥í¥°¥é¥à¤Îµ¡Ç½¤ò³ÈÄ¥¤¹¤ë¤¿¤á¤Ë + ¤³¤ì¤é¤ÎÉôʬ¤òưŪ¤Ë¥í¡¼¥É¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤Î DSO µ¡¹½¤Ï´Êñ¤Ê¤è¤¦¤Ë¸«¤¨¤Þ¤¹¤¬¡¢¾¯¤Ê¤¯¤È¤â°ì¤ÄÆñ¤·¤¤ÅÀ¤¬ + ¤¢¤ê¤Þ¤¹: ¥×¥í¥°¥é¥à¤ò³ÈÄ¥¤¹¤ë¤¿¤á¤Ë DSO ¤ò»È¤Ã¤Æ¤¤¤ë¤È¤­¤Ë¡¢ + DSO ¤¬¼Â¹Ô¥×¥í¥°¥é¥à¤«¤é¥·¥ó¥Ü¥ë¤ò²ò·è¤¹¤ëÅÀ¤Ç¤¹ (ÆóÈÖÌܤÎÊýË¡)¡£ + ¤³¤ì¤Ï¤Ê¤¼¤Ç¤·¤ç¤¦¤«¡£¤½¤ì¤Ï¡¢DSO ¤Î¥·¥ó¥Ü¥ë¤ò¼Â¹Ô¥×¥í¥°¥é¥à¤Î + ¥·¥ó¥Ü¥ë¤«¤é¡ÖµÕ²ò·è¡×¤¹¤ë¤È¤¤¤¦¤Î¤Ï¥é¥¤¥Ö¥é¥ê¤ÎÀß·× + (¥é¥¤¥Ö¥é¥ê¤Ï¤½¤ì¤ò»ÈÍѤ¹¤ë¥×¥í¥°¥é¥à¤Î¤³¤È¤Ï²¿¤â + ÃΤé¤Ê¤¤) ¤ËÈ¿¤·¤Æ¤¤¤Æ¡¢¤³¤Îµ¡Ç½¤Ï¤¹¤Ù¤Æ¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ë + ¤¢¤ë¤ï¤±¤Ç¤Ï¤Ê¤¯¡¢É¸½à²½¤â¤µ¤ì¤Æ¤¤¤Ê¤¤¤«¤é¤Ç¤¹¡£ + ¼ÂºÝ¤Ë¤Ï¼Â¹Ô¥×¥í¥°¥é¥à¤Î¥°¥í¡¼¥Ð¥ë¤Ê¥·¥ó¥Ü¥ë¤ÏºÆ¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤ë¤³¤È¤Ï + ¤¢¤Þ¤ê¤Ê¤¯¡¢DSO ¤«¤é»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£¥ê¥ó¥«¤Ë¥°¥í¡¼¥Ð¥ë¥·¥ó¥Ü¥ë¤¹¤Ù¤Æ¤ò + ¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤ë¤è¤¦¤Ë¤µ¤»¤ëÊýË¡¤ò¸«¤Ä¤±¤ë¤³¤È¤¬¡¢¼Â¹Ô»þ¤Ë¥×¥í¥°¥é¥à¤ò + ³ÈÄ¥¤¹¤ë¤¿¤á¤Ë DSO ¤ò»È¤¦¤È¤­¤Î°ìÈÖ¤ÎÌäÂê¤Ç¤¹¡£

+ +

¶¦Í­¥é¥¤¥Ö¥é¥ê¤Î¥¢¥×¥í¡¼¥Á¤¬ÉáÄ̤ÎÊýË¡¤Ç¤¹¡£DSO µ¡¹½¤Ï¤½¤Î¤¿¤á¤Ë + À߷פµ¤ì¤¿¤â¤Î¤Ç¤¹¤«¤é¡£¤·¤¿¤¬¤Ã¤Æ¡¢¤½¤ÎÊýË¡¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬ + Ä󶡤¹¤ë¤Û¤È¤ó¤É¤¹¤Ù¤Æ¤Î¼ïÎà¤Î¥é¥¤¥Ö¥é¥ê¤Ç»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£ + °ìÊý¡¢¥×¥í¥°¥é¥à¤Î³ÈÄ¥¤Î¤¿¤á¤Ë¶¦Í­¥ª¥Ö¥¸¥§¥¯¥È¤ò»ÈÍѤ¹¤ë¡¢¤È¤¤¤¦Êý¤Ï + ¤¢¤Þ¤ê»È¤ï¤ì¤Æ¤¤¤Þ¤»¤ó¡£

+ +

1998 ǯ¤Î»þÅÀ¤Ç¡¢¼Â¹Ô»þ¤Ë¼ÂºÝ¤Ëµ¡Ç½³ÈÄ¥¤Î¤¿¤á¤Ë DSO µ¡¹½¤ò»È¤Ã¤Æ¤¤¤ë + ¥½¥Õ¥È¥¦¥§¥¢¥Ñ¥Ã¥±¡¼¥¸¤Ï¾¯¤·¤À¤±¤Ç¤·¤¿: Perl 5 (XS µ¡¹½¤È DnaLoader ¥â¥¸¥å¡¼¥ë + ¤Ë¤è¤ë¤â¤Î)¡¢Netscape ¥µ¡¼¥Ð¤Ê¤É¤Ç¤¹¡£Apache ¤Ï¤¹¤Ç¤Ë + ¥â¥¸¥å¡¼¥ë¤Î³µÇ°¤ò»È¤Ã¤Æµ¡Ç½³ÈÄ¥¤ò¤·¤Æ¤¤¤Æ¡¢ÆâÉôŪ¤Ë¥Ç¥£¥¹¥Ñ¥Ã¥Á¥ê¥¹¥È¤Ë + ´ð¤Å¤¤¤¿³°Éô¥â¥¸¥å¡¼¥ë¤Î Apache ¥³¥¢µ¡Ç½¤Ø¤Î¥ê¥ó¥¯¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤Þ¤·¤¿¤Î¤Ç¡¢ + ¥Ð¡¼¥¸¥ç¥ó 1.3 ¤«¤é¡¢Apache ¤â DSO µ¡¹½¤ò»È¤¦Ãç´Ö¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + Apache ¤Ï¼Â¹Ô»þ¤Ë DSO ¤ò»È¤Ã¤Æ¥â¥¸¥å¡¼¥ë¤ò¥í¡¼¥É¤¹¤ë¤è¤¦¤Ë¤¹¤Ç¤Ë + ±¿Ì¿ÉÕ¤±¤é¤ì¤Æ¤¤¤¿¤Î¤Ç¤¹¡£

+
top
+
+

ÍøÅÀ¤È·çÅÀ

+ +

¾åµ­¤Î DSO ¤Ë´ð¤Å¤¤¤¿µ¡Ç½¤Ï°Ê²¼¤ÎÍøÅÀ¤¬¤¢¤ê¤Þ¤¹:

+ +
    +
  • ¼ÂºÝ¤Î¥µ¡¼¥Ð¥×¥í¥»¥¹¤òÁȤßΩ¤Æ¤ë¤¿¤á¤Ë¡¢ + ¥Ó¥ë¥É»þ¤Ë configure ¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦Âå¤ï¤ê¤Ë + ¼Â¹Ô»þ¤Ë httpd.conf ¤ÎÀßÄêÍÑ¥³¥Þ¥ó¥É + LoadModule + ¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¤Î¤Ç¡¢¥µ¡¼¥Ð¥Ñ¥Ã¥±¡¼¥¸¤Î½ÀÆðÀ­¤¬¹â¤Þ¤ê¤Þ¤·¤¿¡£ + ¤¿¤È¤¨¤Ð¡¢°ì¤Ä¤Î Apache ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤«¤é + °ã¤¦¹½À®¤Î¥µ¡¼¥Ð (ɸ½àÈÇ¤È SSL ÈÇ¡¢ºÇ¾®¹½À®¤È³ÈÄ¥ÈÇ [mod_perl, PHP3] + ¤Ê¤É) ¤ò¼Â¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
    • + +
  • ¥¤¥ó¥¹¥È¡¼¥ë¤Î¸å¤Ç¤¢¤Ã¤Æ¤â¡¢¥µ¡¼¥Ð¤Î¥Ñ¥Ã¥±¡¼¥¸¤ò¥µ¡¼¥É¥Ñ¡¼¥Æ¥£ + ¥â¥¸¥å¡¼¥ë¤Ç´Êñ¤Ë³ÈÄ¥¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£¤³¤ì¤Ï¡¢Apache ¥³¥¢ + ¥Ñ¥Ã¥±¡¼¥¸¤È¡¢PHP3, mod_perl, mod_fastcgi ¤Ê¤É ¤ÎÄɲäΠ+ ¥Ñ¥Ã¥±¡¼¥¸¤òºîÀ®¤Ç¤­¤ë¤Î¤Ç¡¢¾¯¤Ê¤¯¤È¤â¥Ù¥ó¥À¤Î¥Ñ¥Ã¥±¡¼¥¸´ÉÍý¼Ô¤Ë¤È¤Ã¤Æ + Â礭¤ÊÍøÅÀ¤¬¤¢¤ê¤Þ¤¹¡£
    • + +
  • Apache ¥â¥¸¥å¡¼¥ë¤Î³«È¯¤¬´Êñ¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï DSO ¤È apxs ¤ÎÁȤ߹ç¤ï¤»¤Ë¤è¤ê¡¢Apache ¥½¡¼¥¹¥Ä¥ê¡¼¤Î + ³°¤Çºî¶È¤Ç¤­¡¢³«È¯Ãæ¤Î¥â¥¸¥å¡¼¥ë¤Î¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤ò + ¼Â¹ÔÃæ¤Î Apache ¥µ¡¼¥Ð¤ËÁȤ߹þ¤à¤¿¤á¤Ë apxs -i ¤È + apachectl restart ¤ò¹Ô¤Ê¤¦¤À¤±¤ÇÎɤ¯¤Ê¤ë¤«¤é¤Ç¤¹¡£
    • +
+ +

DSO ¤Ë¤Ï°Ê²¼¤Î·çÅÀ¤¬¤¢¤ê¤Þ¤¹:

+ +
    +
  • ¤¹¤Ù¤Æ¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬¥×¥í¥°¥é¥à¤Î¥¢¥É¥ì¥¹¶õ´Ö¤Ë + ¥³¡¼¥É¤òưŪ¥í¡¼¥É¤¹¤ë¤³¤È¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤ï¤Ç¤Ï¤Ê¤¤¤Î¤Ç¡¢ + ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ë¤è¤Ã¤Æ¤Ï DSO µ¡¹½¤Ï»È¤¨¤Þ¤»¤ó¡£
    • + +
  • Unix ¤Î¥í¡¼¥À¤¬¥·¥ó¥Ü¥ë¤Î²ò·è¤ò¤¹¤ëɬÍפ¬¤Ç¤­¤¿¤Î¤Ç¡¢ + ¤½¤Î¥ª¡¼¥Ð¥Ø¥Ã¥É¤Ë¤è¤ê¥µ¡¼¥Ð¤Îµ¯Æ°»þ´Ö¤¬Ìó 20% ÃÙ¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
    • + +
  • °ÌÃÖÈó°Í¸¥³¡¼¥É (PIC) (ÌõÃí position independent code) ¤Ï + ÁêÂÐ¥¢¥É¥ì¥¹¤Î¤¿¤á¤ËÊ£»¨¤Ê¥¢¥»¥ó¥Ö¥é¤Î¥È¥ê¥Ã¥¯¤¬É¬Íפʤ³¤È¤¬¤¢¤ê¡¢ + ¤½¤ì¤Ïɬ¤º¤·¤âÀäÂÐ¥¢¥É¥ì¥¹¤ÈƱ¤¸¤¯¤é¤¤¤Î®ÅÙ¤¬¤Ç¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤Î¤Ç¡¢ + ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ë¤è¤Ã¤Æ¤Ï¥µ¡¼¥Ð¤Î¼Â¹Ô®ÅÙ¤¬Ìó 5% ÃÙ¤¯¤Ê¤ê¤Þ¤¹¡£
    • + +
  • DSO ¥â¥¸¥å¡¼¥ë¤Ï¤¹¤Ù¤Æ¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¾¤Î DSO ¤Ë´ð¤Å¤¤¤¿ + ¥é¥¤¥Ö¥é¥ê¤ËÂФ·¤Æ¥ê¥ó¥¯¤Ç¤­¤ë (ld -lfoo) + ¤È¤¤¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤Î¤Ç (¤¿¤È¤¨¤Ð¡¢a.out ¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¤Ï + ¤³¤Îµ¡Ç½¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢ELF ¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ë¤Ï¤¢¤ê¤Þ¤¹)¡¢ + ¤¹¤Ù¤Æ¤Î¼ïÎà¤Î¥â¥¸¥å¡¼¥ë¤Ë DSO µ¡¹½¤ò»È¤¨¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¸À¤¤´¹¤¨¤ë¤È¡¢DSO ¥Õ¥¡¥¤¥ë¤È¤·¤Æ¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤¿¥â¥¸¥å¡¼¥ë¤Î + »È¤¨¤ë¥·¥ó¥Ü¥ë¤Ï¡¢ + Apache ¤Î¥³¥¢¤Î¥·¥ó¥Ü¥ë¡¢C ¥é¥¤¥Ö¥é¥ê (libc) ¤È + Apache ¥³¥¢¤¬»È¤Ã¤Æ¤¤¤ë¾¤Î¤¹¤Ù¤Æ¤ÎÀÅŪ¤Ê¥é¥¤¥Ö¥é¥ê¤ÈưŪ¥é¥¤¥Ö¥é¥ê¤Î + ¥·¥ó¥Ü¥ë¡¢PIC ¤Ë¤è¤ëÀÅŪ¤Ê¥é¥¤¥Ö¥é¥ê (libfoo.a) ¤Î + ¥·¥ó¥Ü¥ë¤Î¤ß¤ËÀ©¸Â¤µ¤ì¤Þ¤¹¡£¤½¤Î¾¤Î¥³¡¼¥É¤ò»È¤¦ÊýË¡¤Ï¡¢ + Apache ¥³¥¢¼«¿È¤¬¤¹¤Ç¤Ë¤½¤Î¥³¡¼¥É¤Ø¤Î»²¾È¤¬¤¢¤ë¤è¤¦¤Ë¤¹¤ë¤«¡¢ + dlopen () ¤ò»È¤Ã¤Æ¥³¡¼¥É¤ò¼«Ê¬¼«¿È¤Ç¥í¡¼¥É¤¹¤ë¤«¤Î + ¤É¤Á¤é¤«¤·¤«¤¢¤ê¤Þ¤»¤ó¡£
    • +
+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/dso.html.ko.euc-kr b/docs/manual/dso.html.ko.euc-kr new file mode 100644 index 00000000..99fdbfbe --- /dev/null +++ b/docs/manual/dso.html.ko.euc-kr @@ -0,0 +1,276 @@ + + + +µ¿Àû°øÀ¯°´Ã¼ (DSO) Áö¿ø - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

µ¿Àû°øÀ¯°´Ã¼ (DSO) Áö¿ø

+
+

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

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

¾ÆÆÄÄ¡ À¥¼­¹ö´Â °ü¸®ÀÚ°¡ ¸ðµâµéÀ» ¼±ÅÃÇÏ¿© ¼­¹ö¿¡ Æ÷ÇÔÇÒ + ±â´ÉÀ» °áÁ¤ÇÒ ¼ö ÀÖ´Â ¸ðµâÈ­µÈ ÇÁ·Î±×·¥ÀÌ´Ù. ¼­¹ö¸¦ ÄÄÆÄÇÒ¶§ + httpd ½ÇÇàÆÄÀÏ¿¡ Á¤ÀûÀ¸·Î ¸ðµâÀ» ÄÄÆÄÀÏÇÒ + ¼ö ÀÖ´Ù. ¾Æ´Ï¸é ¸ðµâÀ» httpd ½ÇÇàÆÄÀÏ°ú + ºÐ¸®ÇÏ¿© µ¿Àû°øÀ¯°´Ã¼(Dynamic Shared Objects, DSO)·Î ÄÄÆÄÀÏÇÒ + ¼ö ÀÖ´Ù. DSO ¸ðµâÀº ¼­¹ö¸¦ ÄÄÆÄÀÏÇÒ¶§ ÄÄÆÄÀÏÇϰųª, Apache + Extension Tool (apxs)À» + »ç¿ëÇÏ¿© ³ªÁß¿¡ ÄÄÆÄÀÏÇÏ¿© Ãß°¡ÇÒ ¼ö ÀÖ´Ù.

+ +

ÀÌ ¹®¼­´Â DSO ¸ðµâ »ç¿ë¹ý°ú ¹è°æ ÀÌ·ÐÀ» ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

±¸Çö

+ +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

¾ÆÆÄÄ¡ Çٽɿ¡ Á¤ÀûÀ¸·Î ÄÄÆÄÀÏÇؾßÇÒ + mod_so.c¶ó´Â ¸ðµâÀº ¾ÆÆÄÄ¡ ¸ðµâÀ» + ÀоîµéÀ̱âÀ§ÇÑ DSO¸¦ Áö¿øÇÑ´Ù. + ÀÌ ¸ðµâÀº core¸¦ Á¦¿ÜÇÏ°í DSO°¡ + µÉ ¼ö ¾ø´Â À¯ÀÏÇÑ ¸ðµâÀÌ´Ù. ½ÇÁ¦·Î ´Ù¸¥ ¸ðµç ¾ÆÆÄÄ¡ ¸ðµâÀº + ¼³Ä¡ ¹®¼­¿¡¼­ ¼³¸íÇÑ + configureÀÇ --enable-module=shared + ¿É¼ÇÀ» »ç¿ëÇÏ¿© DSO·Î ÄÄÆÄÀÏÇÒ ¼ö ÀÖ´Ù. ¸ðµâÀ» + mod_foo.so¿Í °°ÀÌ DSO·Î ÄÄÆÄÀÏÇÑÈÄ httpd.conf + ÆÄÀÏ¿¡ mod_soÀÇ + LoadModule ¸í·É¾î¸¦ + »ç¿ëÇÏ¿© ¼­¹ö ½ÃÀ۽à ȤÀº Àç½ÃÀ۽à ±× ¸ðµâÀ» ÀоîµéÀÏ ¼ö + ÀÖ´Ù.

+ +

¾ÆÆÄÄ¡ ¸ðµâ(ƯÈ÷ Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâ)·Î »ç¿ëÇÒ DSO ÆÄÀÏÀ» ½±°Ô + ¸¸µé±âÀ§ÇØ apxs (APache + eXtenSion)¶ó´Â »õ·Î¿î Áö¿ø ÇÁ·Î±×·¥ÀÌ ÀÖ´Ù. ÀÌ ÇÁ·Î±×·¥Àº + ¾ÆÆÄÄ¡ ¼Ò½º Æ®¸® ¹Û¿¡¼­ DSO·Î »ç¿ëÇÒ ¸ðµâÀ» + ÄÄÆÄÀÏÇÒ¶§ »ç¿ëÇÑ´Ù. °³³äÀº ½±´Ù. ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÒ¶§ + configure¿Í make installÀÌ + ¾ÆÆÄÄ¡ C Çì´õÆÄÀÏÀ» ¼³Ä¡ÇÏ°í, DSO ÆÄÀÏÀ» ÄÄÆÄÀÏÇϱâÀ§ÇÑ + Ç÷¡Æû ƯÀ¯ÀÇ ÄÄÆÄÀÏ·¯ ¿É¼Ç°ú ¸µÄ¿ ¿É¼ÇÀ» apxs + ÇÁ·Î±×·¥¿¡ ±â·ÏÇÑ´Ù. ±×·¡¼­ apxs¸¦ »ç¿ëÇÏ´Â »ç¿ëÀÚ´Â + ¾ÆÆÄÄ¡ ¹èÆ÷º» ¼Ò½º Æ®¸®¾øÀÌ, ¶Ç DSO Áö¿øÀ» À§ÇÑ Ç÷¡Æû ƯÀ¯ÀÇ + ÄÄÆÄÀÏ·¯ ¿É¼Ç¿Í ¸µÄ¿ ¿É¼Ç¿¡ ½Å°æÀ» ¾²Áö¾Ê°í ÀÚ½ÅÀÇ ¾ÆÆÄÄ¡ + ¸ðµâ ¼Ò½º¸¦ ÄÄÆÄÀÏÇÒ ¼ö ÀÖ´Ù.

+
top
+
+

»ç¿ë¹ý ¿ä¾à

+ +

Apache 2.0ÀÇ DSO ±â´É¿¡ ´ëÇÑ Âª°í °£·«ÇÑ ¿ä¾àÀÌ´Ù:

+ +
    +
  1. + ¹èÆ÷º»¿¡ ÀÖ´Â ¾ÆÆÄÄ¡ ¸ðµâÀ» ÄÄÆÄÀÏÇÏ°í ¼³Ä¡ÇÏ´Â + °æ¿ì. ¿¹¸¦ µé¾î mod_foo.c¸¦ DSO + mod_foo.so·Î: + +

    +$ ./configure --prefix=/path/to/install --enable-foo=shared
    +$ make install +

    +
    2. + +
  2. + Á¦»ïÀÚ°¡ ¸¸µç ¾ÆÆÄÄ¡ ¸ðµâÀ» ÄÄÆÄÀÏÇÏ°í ¼³Ä¡ÇÏ´Â + °æ¿ì. ¿¹¸¦ µé¾î mod_foo.c¸¦ DSO + mod_foo.so·Î: + +

    +$ ./configure --add-module=module_type:/path/to/3rdparty/mod_foo.c --enable-foo=shared
    +$ make install +

    +
    3. + +
  3. + °øÀ¯ ¸ðµâÀ» ³ªÁß¿¡ »ç¿ëÇϱâÀ§ÇØ ¾ÆÆÄÄ¡¸¦ ±¸¼ºÇÏ´Â + °æ¿ì: + +

    +$ ./configure --enable-so
    +$ make install +

    +
    4. + +
  4. + Á¦»ïÀÚ°¡ ¸¸µç ¾ÆÆÄÄ¡ ¸ðµâÀ» ÄÄÆÄÀÏÇÏ°í ¼³Ä¡ÇÏ´Â + °æ¿ì. apxs¸¦ »ç¿ëÇÏ¿© + ¾ÆÆÄÄ¡ ¼Ò½º Æ®¸® ¹Û¿¡¼­ mod_foo.c¸¦ + DSO mod_foo.so·Î: + +

    +$ cd /path/to/3rdparty
    +$ apxs -c mod_foo.c
    +$ apxs -i -a -n foo mod_foo.la +

    +
    5. +
+ +

¸ðµç °æ¿ì ÀÏ´Ü °øÀ¯ ¸ðµâÀÌ ÄÄÆÄÀϵǸé, httpd.conf¿¡ + LoadModule Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡°¡ ±× ¸ðµâÀ» ÀоîµéÀÌ°Ô ¸¸µç´Ù.

+
top
+
+

¹è°æÁö½Ä

+ +

Çö´ëÀûÀÎ À¯´Ð½º·ù¿¡´Â µ¿Àû°øÀ¯°´Ã¼ (DSO)ÀÇ + µ¿Àû ¸µÅ·/·Îµù(dynamic linking/loading)À̶ó°í ÇÏ¿©, Ưº°ÇÑ + Çü½ÄÀÇ ½ÇÇàÄÚµå Á¶°¢À» ¸¸µé¾î ½ÇÇàÁßÀÎ ½ÇÇàÇÁ·Î±×·¥ÀÇ + ÁÖ¼Ò°ø°£¿¡ ÀоîµéÀÌ´Â ¸ÚÁø ±â´ÉÀÌ ÀÖ´Ù.

+ +

º¸Åë µÎ°¡Áö ¹æ¹ýÀ¸·Î ÀоîµéÀÏ ¼ö ÀÖ´Ù. Çϳª´Â ½ÇÇàÇÁ·Î±×·¥ÀÌ + ½ÃÀÛÇÒ¶§ ld.so¶ó´Â ½Ã½ºÅÛ ÇÁ·Î±×·¥ÀÌ ÀÚµ¿À¸·Î + ÀоîµéÀÌ´Â °æ¿ì°í, ´Ù¸¥ Çϳª´Â ½ÇÇàÁßÀÎ ÇÁ·Î±×·¥ÀÌ + dlopen()/dlsym() ½Ã½ºÅÛÈ£Ãâ·Î À¯´Ð½º ·Î´õ(loader)ÀÇ + ½Ã½ºÅÛ ÀÎÅÍÆäÀ̽ºÀ» »ç¿ëÇÏ¿© Á÷Á¢ ÀоîµéÀÌ´Â °æ¿ì´Ù.

+ +

ù¹ø° °æ¿ì DSO¸¦ º¸Åë °øÀ¯¶óÀ̺귯¸®(shared libraries) + ȤÀº DSO ¶óÀ̺귯¸®¶ó°í ºÎ¸£¸ç, ÆÄÀÏÀº + libfoo.so³ª libfoo.so.1.2 °°Àº + À̸§À» °¡Áø´Ù. À̵éÀº ½Ã½ºÅÛ µð·ºÅ丮(º¸Åë /usr/lib)¿¡ + ÀÖ°í, ÄÄÆÄÀϽà ¸µÄ¿ ¸í·É¾î¿¡ -lfoo¸¦ ÁÖ¾î + ½ÇÇàÆÄÀÏ°ú ¿¬°áÇÑ´Ù. ÀÌ·¸°Ô Á÷Á¢ ½áÁØ ¶óÀ̺귯¸®´Â ½ÇÇàÆÄÀÏ¿¡ + ÂüÁ¶µÇ¿©¼­, ÇÁ·Î±×·¥ÀÌ ½ÃÀÛÇÒ¶§ ¸µÄ¿ ¿É¼Ç -R·Î + Á÷Á¢ ÁöÁ¤ÇÑ °æ·Î, ȯ°æº¯¼ö LD_LIBRARY_PATH·Î + ÁöÁ¤ÇÑ °æ·Î ȤÀº /usr/lib¿¡¼­ À¯´Ð½º ·Î´õ°¡ + libfoo.so¸¦ ãÀ» ¼ö ÀÖ´Ù. ±×·¯¸é ½ÇÇàÇÁ·Î±×·¥ÀÇ + (¾ÆÁ÷ ¸øãÀº(unresolved)) ½Éº¼(symbol)À» DSO¿¡¼­ ã°ÔµÈ´Ù.

+ +

DSO´Â º¸Åë ½ÇÇàÇÁ·Î±×·¥ÀÇ ½Éº¼À» ãÁö¾Ê±â ¶§¹®¿¡ (DSO°¡ + Àç»ç¿ë°¡´ÉÇÑ ÀϹÝÀûÀÎ ÄÚµå ¶óÀ̺귯¸®À̹ǷÎ) ã±â´Â ¿©±â¼­ + ³¡³­´Ù. À¯´Ð½º ·Î´õ°¡ ½Éº¼ ã±â¸¦ ¿ÏÀüÈ÷ ´ã´çÇϹǷΠ½ÇÇàÇÁ·Î±×·¥ÀÌ + Á÷Á¢ DSO¿¡¼­ ½Éº¼À» ãÀ» ÇÊ¿ä°¡ ¾ø´Ù. (»ç½Ç ld.so¸¦ + ºÎ¸£´Â ÄÚµå´Â Á¤ÀûÀÌ ¾Æ´Ñ ¸ðµç ½ÇÇàÇÁ·Î±×·¥¿¡ ¸µÅ©µÇ´Â ½ÇÇà½Ã + ½ÃÀÛÄÚµåÀÇ ÀϺδÙ.) °øÅëµÈ ¶óÀ̺귯¸® Äڵ带 µ¿ÀûÀ¸·Î ÀоîµéÀÌ´Â + ÀåÁ¡Àº ¸íÈ®ÇÏ´Ù. ¶óÀ̺귯¸® Äڵ尡 ¸ðµç ÇÁ·Î±×·¥¿¡ Áߺ¹Çؼ­ + ÀúÀåµÇ´Â ´ë½Å libc.so¿Í °°Àº ½Ã½ºÅÛ ¶óÀ̺귯¸®¿¡ + Çѹø¸¸ ÀúÀåµÇ±â ¶§¹®¿¡ µð½ºÅ© °ø°£ÀÌ Àý¾àµÈ´Ù.

+ +

µÎ¹ø° °æ¿ì DSO¸¦ º¸Åë °øÀ¯°´Ã¼(shared objects) + ȤÀº DSO ÆÄÀÏÀ̶ó°í ºÎ¸£°í, (±ÔÄ¢»ó À̸§Àº + foo.soÀÌÁö¸¸) ÆÄÀÏÀÇ È®ÀåÀÚ´Â ÀÚÀ¯·Ó´Ù. ÀÌ + ÆÄÀϵéÀº º¸Åë ÇÁ·Î±×·¥ ÀÚü µð·ºÅ丮¿¡ À§Ä¡ÇÏ°í ½ÇÇàÇÁ·Î±×·¥¿¡ + ÀÚµ¿À¸·Î ¿¬°áµÇÁö ¾Ê´Â´Ù. ´ë½Å ½ÇÇàÇÁ·Î±×·¥Àº ½ÇÇà½Ã + dlopen()À» »ç¿ëÇÏ¿© DSO¸¦ ÁÖ¼Ò°ø°£¿¡ + Á÷Á¢ Àоîµé¿©¾ß ÇÑ´Ù. À̶§ ½ÇÇàÇÁ·Î±×·¥Àº DSO¿¡¼­ ½Éº¼À» + ãÁö ¾Ê´Â´Ù. ´ë½Å ¾Õ¿¡¼­ º» À¯´Ð½º ·Î´õ´Â ÀÚµ¿À¸·Î ½ÇÇàÆÄÀÏ°ú + ½ÇÇàÆÄÀÏÀÌ ÀÌ¹Ì ÀоîµéÀÎ DSO ¶óÀ̺귯¸®(ƯÈ÷ Ç×»ó Á¸ÀçÇÏ´Â + libc.soÀÇ ¸ðµç ½Éº¼)¿¡¼­ DSOÀÇ (¾ÆÁ÷ ¸øãÀº) + ½Éº¼À» ã´Â´Ù. ±×·¡¼­ DSO´Â ¸¶Ä¡ óÀ½ºÎÅÍ ½ÇÇàÇÁ·Î±×·¥¿¡ + Á¤ÀûÀ¸·Î ¸µÅ©µÈ°Í°ú °°ÀÌ ½ÇÇàÆÄÀÏÀÇ ½Éº¼À» ¾Ë°ÔµÈ´Ù.

+ +

DSOÀÇ API¸¦ ÀÌ¿ëÇϱâÀ§Çؼ­ ¸¶Áö¸·À¸·Î ½ÇÇàÇÁ·Î±×·¥Àº + dlsym()À¸·Î DSO¿¡¼­ ƯÁ¤ ½Éº¼À» ã¾Æ¼­, ¾ÕÀ¸·Î + »ç¿ëÇϱâÀ§ÇØ µð½ºÆÐÄ¡(dispatch) Ç¥ µî¿¡ ÀúÀåÇÑ´Ù. + ´Ù¸¥ ¸»·Î ½ÇÇàÇÁ·Î±×·¥Àº »ç¿ëÇÒ ¸ðµç ½Çº¼À» Á÷Á¢ ã¾Æ¾ßÇÑ´Ù. + ÀÌ·± ±¸Á¶ÀÇ ÀåÁ¡Àº ÇÁ·Î±×·¥ÀÇ ÀϺθ¦ ÇÁ·Î±×·¥ÀÌ + ÇÊ¿äÇÒ¶§±îÁö ÀоîµéÀÌÁö ¾Ê¾Æµµ (±×·¡¼­ ¸Þ¸ð¸®¸¦ ³¶ºñÇÏÁö + ¾Ê°Ô) µÈ´Ù´Â Á¡ÀÌ´Ù. ±âº» ÇÁ·Î±×·¥ÀÇ ±â´ÉÀ» È®ÀåÇϱâÀ§ÇØ + ÇÊ¿äÇÑ °æ¿ì ÀÌ ºÎºÐÀ» µ¿ÀûÀ¸·Î ÀоîµéÀÏ ¼ö ÀÖ´Ù.

+ +

ÀÌ·± DSO ±¸Á¶°¡ ÀÚ¿¬½º·´°Ô º¸ÀÌÁö¸¸, ÃÖ¼ÒÇÑ ¾î·Á¿î Á¡ÀÌ + ÇÑ°¡ÁöÀÖ´Ù. ÇÁ·Î±×·¥À» È®ÀåÇϱâÀ§ÇØ DSO¸¦ »ç¿ëÇÒ¶§ DSO°¡ + ½ÇÇàÇÁ·Î±×·¥ÀÇ ½Éº¼À» ã´Â ÀÏÀÌ´Ù. ¿Ö? DSO°¡ ½ÇÇàÇÁ·Î±×·¥ÀÇ + ½Éº¼À» "¿ªÀ¸·Î ã´Â °Í"Àº (¶óÀ̺귯¸®´Â ÀÚ½ÅÀ» »ç¿ëÇÏ´Â ÇÁ·Î±×·¥¿¡ + ´ëÇØ ¸ð¸¥´Ù´Â) ¶óÀ̺귯¸® ¼³°è¿¡ ¹ÝÇϸç, ¸ðµç Ç÷¡Æû¿¡¼­ + Áö¿øµÇÁö¾Ê°í Ç¥ÁØÈ­µÇÁöµµ ¾Ê¾Ò±â ¶§¹®ÀÌ´Ù. ½ÇÁ¦·Î ½ÇÇàÆÄÀÏÀÇ + Àü¿ª½Éº¼(global symbol)Àº º¸Åë ÀͽºÆ÷Æ®(export)µÇÁö ¾Ê±â¶§¹®¿¡ + DSO°¡ »ç¿ëÇÒ ¼ö ¾ø´Ù. DSO¸¦ »ç¿ëÇÏ¿© ½ÇÇàÁß ÇÁ·Î±×·¥À» È®ÀåÇÏ·Á¸é + ¸µÄ¿¿¡°Ô ¸ðµç Àü¿ª½Éº¼À» ÀͽºÆ÷Æ®Çϵµ·Ï °­Á¦ÇÏ´Â °ÍÀÌ ÁÖµÈ + ÇØ°áÃ¥ÀÌ´Ù.

+ +

°øÀ¯¶óÀ̺귯¸®´Â DSO ¹æ½ÄÀÇ ¼³°è¿øÄ¢´ë·Î ÀüÇüÀûÀ̱⶧¹®¿¡ + ¿î¿µÃ¼Á¦°¡ Á¦°øÇÏ´Â °ÅÀÇ ¸ðµç Á¾·ùÀÇ ¶óÀ̺귯¸®°¡ »ç¿ëÇÑ´Ù. + ¹Ý´ë·Î ¸¹Àº ÇÁ·Î±×·¥Àº ÇÁ·Î±×·¥À» È®ÀåÇϱâÀ§ÇØ °øÀ¯°´Ã¼¸¦ + »ç¿ëÇÏÁö ¾Ê´Â´Ù.

+ +

1998³â ½ÇÇàÁß ½ÇÁ¦·Î ±â´ÉÀ» È®ÀåÇϱâÀ§ÇØ DSO ±¸Á¶¸¦ »ç¿ëÇÑ + ¼ÒÇÁÆ®¿þ¾î ÆÐÅ°Áö´Â (XS ±¸Á¶¿Í DynaLoader ¸ðµâÀ» »ç¿ëÇÑ) + Perl 5, Netscape Server µîÀ¸·Î µå¹°¾ú´Ù. ¾ÆÆÄÄ¡´Â + ÀÌ¹Ì ±â´ÉÀ» È®ÀåÇϱâÀ§ÇØ ¸ðµâ °³³äÀ» »ç¿ëÇß°í ¿ÜºÎ ¸ðµâÀ» + ¾ÆÆÄÄ¡ Çٽɱâ´É¿¡ ¿¬°áÇϱâÀ§ÇØ ³»ºÎÀûÀ¸·Î µð½ºÆÐÄ¡¸ñ·ÏÀ» + ÀÌ¿ëÇÑ Á¢±Ù¹æ¹ýÀ» »ç¿ëÇ߱⶧¹®¿¡ 1.3 ¹öÀüºÎÅÍ ÀÌ ´ë¿­¿¡ ÇÕ·ùÇß´Ù. + ±×·¡¼­ ¾ÆÆÄÄ¡´Â ½ÇÇàÁß ¸ðµâÀ» ÀоîµéÀ̴µ¥ DSO¸¦ »ç¿ëÇϵµ·Ï + ¿î¸íÁö¿öÁ³´Ù.

+
top
+
+

Àå´ÜÁ¡

+ +

¾Õ¿¡¼­ ¸»ÇÑ DSO¸¦ »ç¿ëÇÏ¸é ´ÙÀ½°ú °°Àº ÀåÁ¡ÀÌ ÀÖ´Ù:

+ +
    +
  • ½ÇÁ¦ ¼­¹ö ÇÁ·Î¼¼½º°¡ ÄÄÆÄÀϽà configure + ¿É¼Ç´ë½Å httpd.confÀÇ LoadModuleÀ» »ç¿ëÇÏ¿© ½ÇÇàÁß¿¡ + °áÇյǹǷΠ¼­¹ö ÆÐÅ°Áö ½ÇÇàÀÌ ´õ À¯¿¬ÇÏ´Ù. ¿¹¸¦ µé¾î ÇѹøÀÇ + ¾ÆÆÄÄ¡ ¼³Ä¡¸¸À¸·Î ´Ù¸¥ ¼­¹ö(Ç¥ÁØ ¹öÀü°ú SSL ¹öÀü, ÃÖ¼ÒÈ­ + ¹öÀü°ú ±â´ÉÃß°¡ ¹öÀü [mod_perl, PHP3] µî)¸¦ ½ÇÇàÇÒ + ¼ö ÀÖ´Ù.
    • + +
  • ¼­¹ö´Â ¼³Ä¡ÈÄ¿¡µµ Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀ» »ç¿ëÇÏ¿© ½±°Ô + È®ÀåÇÒ ¼ö ÀÖ´Ù. ÃÖ¼ÒÇÑ ±â¾÷ÀÇ ÆÐÅ°Áö Á¦ÀÛÀÚ´Â ¾ÆÆÄÄ¡ ÇÙ½É + ÆÐÅ°Áö¿Í º°µµ·Î PHP3, mod_perl, mod_fastcgi µîÀ» + Ãß°¡ ÆÐÅ°Áö·Î ¸¸µé ¼ö À־ Å« À̵æÀÌ´Ù.
    • + +
  • DSO¿Í apxs¸¦ °¡Áö°í ¾ÆÆÄÄ¡ ¼Ò½º Æ®¸® ¹Û¿¡¼­ + ÀÛ¾÷ÇÏ°í apxs -i¿Í apachectl restart + ¸í·É¾î¸¸À¸·Î ÇöÀç °³¹ßÇÑ ¸ðµâÀÇ »õ ¹öÀüÀ» ½ÇÇàÁßÀÎ ¾ÆÆÄÄ¡ + ¼­¹ö¿¡ ¹Ý¿µÇÒ ¼ö À־ ´õ ½±°Ô ¾ÆÆÄÄ¡ ¸ðµâÀ» °³¹ßÇÒ ¼ö + ÀÖ´Ù.
    • +
+ +

DSO´Â ´ÙÀ½°ú °°Àº ´ÜÁ¡ÀÌ ÀÖ´Ù:

+ +
    +
  • ÇÁ·Î±×·¥ÀÇ ÁÖ¼Ò°ø°£¿¡ Äڵ带 µ¿ÀûÀ¸·Î ÀоîµéÀÌ´Â ±â´ÉÀ» + Áö¿øÇÏÁö¾Ê´Â ¿î¿µÃ¼Á¦°¡ Àֱ⠶§¹®¿¡ ¸ðµç Ç÷¡Æû¿¡¼­ DSO¸¦ + »ç¿ëÇÒ ¼ö ¾ø´Ù.
    • + +
  • À¯´Ð½º ·Î´õ°¡ ½Éº¼À» ã¾Æ¾ßÇϱ⠶§¹®¿¡ ¼­¹ö ½ÃÀÛÀÌ + ¾à 20% Á¤µµ ´Ê¾îÁø´Ù.
    • + +
  • ¼­¹ö´Â À§Ä¡µ¶¸³ÄÚµå(position independent code, PIC) + ¶§¹®¿¡ Àý´ëÁÖ¼ÒÁöÁ¤(absolute addressing)º¸´Ù ´À¸° + »ó´ëÁÖ¼ÒÁöÁ¤(relative addressing)ÀÇ º¹ÀâÇÑ ¾î¼Àºí·¯ ±â¹ýÀÌ + ÇÊ¿äÇϹǷΠ¾î¶² Ç÷¡Æû¿¡¼­ ½ÇÇà½Ã ¾à 5% Á¤µµ ´Ê´Ù.
    • + +
  • DSO ¸ðµâÀ» ´Ù¸¥ DSO±â¹Ý ¶óÀ̺귯¸®(ld -lfoo)¿¡ + ¸µÅ©ÇÒ ¼ö ¾ø´Â Ç÷¡ÆûÀÌ Àֱ⶧¹®¿¡ (¿¹¸¦ µé¾î ELF±â¹Ý + Ç÷¡ÆûÀº Áö¿øÇÏÁö¸¸ a.out±â¹Ý Ç÷¡ÆûÀº º¸Åë ÀÌ ±â´ÉÀ» + Áö¿øÇÏÁö ¾Ê´Â´Ù) ¸ðµç Á¾·ùÀÇ ¸ðµâ¿¡ DSO¸¦ »ç¿ëÇÒ ¼ö ¾ø´Ù. + ´Ù¸¥ ¸»·Î DSO ÆÄÀÏ·Î ÄÄÆÄÀÏÇÏ´Â ¸ðµâÀº ¾ÆÆÄÄ¡ Çٽɰú ¾ÆÆÄÄ¡ + ÇÙ½ÉÀÌ »ç¿ëÇÏ´Â C ¶óÀ̺귯¸®(libc)¿Í ´Ù¸¥ + µ¿Àû/Á¤Àû ¶óÀ̺귯¸®, À§Ä¡µ¶¸³Äڵ带 ´ã°í ÀÖ´Â Á¤Àû ¶óÀ̺귯¸® + ¾ÆÄ«À̺ê(libfoo.a)ÀÇ ½Éº¼¸¸À» »ç¿ëÇÒ ¼ö ÀÖ´Ù. + ´Ù¸¥ Äڵ带 »ç¿ëÇÏ·Á¸é ¾ÆÆÄÄ¡ ÇÙ½ÉÀÌ ±×°ÍÀ» ÂüÁ¶ÇÏ´øÁö, + dlopen()À¸·Î Á÷Á¢ Äڵ带 Àоîµé¿©¾ß ÇÑ´Ù.
    • +
+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/env.html b/docs/manual/env.html new file mode 100644 index 00000000..1bc45338 --- /dev/null +++ b/docs/manual/env.html @@ -0,0 +1,11 @@ +URI: env.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: env.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: env.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/env.html.en b/docs/manual/env.html.en new file mode 100644 index 00000000..e973c0c5 --- /dev/null +++ b/docs/manual/env.html.en @@ -0,0 +1,414 @@ + + + +Environment Variables in Apache - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Environment Variables in Apache

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

The Apache HTTP Server provides a mechanism for storing + information in named variables that are called environment + variables. This information can be used to control various + operations such as logging or access control. The variables are + also used as a mechanism to communicate with external programs + such as CGI scripts. This document discusses different ways to + manipulate and use these variables.

+ +

Although these variables are referred to as environment + variables, they are not the same as the environment + variables controlled by the underlying operating system. + Instead, these variables are stored and manipulated in an + internal Apache structure. They only become actual operating + system environment variables when they are provided to CGI + scripts and Server Side Include scripts. If you wish to + manipulate the operating system environment under which the + server itself runs, you must use the standard environment + manipulation mechanisms provided by your operating system + shell.

+
+ +
top
+
+

Setting Environment Variables

+ +
Related ModulesRelated Directives
+ +

Basic Environment Manipulation

+ + +

The most basic way to set an environment variable in Apache + is using the unconditional SetEnv directive. Variables may also be passed from + the environment of the shell which started the server using the + PassEnv directive.

+ + +

Conditional Per-Request Settings

+ + +

For additional flexibility, the directives provided by + mod_setenvif allow environment variables to be set on a + per-request basis, conditional on characteristics of particular + requests. For example, a variable could be set only when a + specific browser (User-Agent) is making a request, or only when + a specific Referer [sic] header is found. Even more flexibility + is available through the mod_rewrite's RewriteRule which uses the + [E=...] option to set environment variables.

+ + +

Unique Identifiers

+ + +

Finally, mod_unique_id sets the environment variable + UNIQUE_ID for each request to a value which is + guaranteed to be unique across "all" requests under very + specific conditions.

+ + +

Standard CGI Variables

+ + +

In addition to all environment variables set within the + Apache configuration and passed from the shell, CGI scripts and + SSI pages are provided with a set of environment variables + containing meta-information about the request as required by + the CGI + specification.

+ + +

Some Caveats

+ + +
    +
  • It is not possible to override or change the standard CGI + variables using the environment manipulation directives.
    • + +
  • When suexec is used to launch + CGI scripts, the environment will be cleaned down to a set of + safe variables before CGI scripts are launched. The + list of safe variables is defined at compile-time in + suexec.c.
    • + +
  • For portability reasons, the names of environment + variables may contain only letters, numbers, and the + underscore character. In addition, the first character may + not be a number. Characters which do not match this + restriction will be replaced by an underscore when passed to + CGI scripts and SSI pages.
    • +
+ +
top
+
+

Using Environment Variables

+ + +
Related ModulesRelated Directives
+ +

CGI Scripts

+ + +

One of the primary uses of environment variables is to + communicate information to CGI scripts. As discussed above, the + environment passed to CGI scripts includes standard + meta-information about the request in addition to any variables + set within the Apache configuration. For more details, see the + CGI tutorial.

+ + +

SSI Pages

+ + +

Server-parsed (SSI) documents processed by mod_include's + INCLUDES filter can print environment variables + using the echo element, and can use environment + variables in flow control elements to makes parts of a page + conditional on characteristics of a request. Apache also + provides SSI pages with the standard CGI environment variables + as discussed above. For more details, see the SSI tutorial.

+ + +

Access Control

+ + +

Access to the server can be controlled based on the value of + environment variables using the allow from env= + and deny from env= directives. In combination with + SetEnvIf, this + allows for flexible control of access to the server based on + characteristics of the client. For example, you can use these + directives to deny access to a particular browser (User-Agent). +

+ + +

Conditional Logging

+ + +

Environment variables can be logged in the access log using + the LogFormat + option %e. In addition, the decision on whether + or not to log requests can be made based on the status of + environment variables using the conditional form of the + CustomLog + directive. In combination with SetEnvIf this allows for flexible control of which + requests are logged. For example, you can choose not to log + requests for filenames ending in gif, or you can + choose to only log requests from clients which are outside your + subnet.

+ + +

Conditional Response Headers

+ + +

The Header + directive can use the presence or + absence of an environment variable to determine whether or not + a certain HTTP header will be placed in the response to the + client. This allows, for example, a certain response header to + be sent only if a corresponding header is received in the + request from the client.

+ + + +

External Filter Activation

+ + +

External filters configured by mod_ext_filter + using the ExtFilterDefine directive can + by activated conditional on an environment variable using the + disableenv= and enableenv= options.

+ + +

URL Rewriting

+ + +

The %{ENV:...} form of TestString in + the RewriteCond + allows mod_rewrite's rewrite + engine to make decisions conditional on environment variables. + Note that the variables accessible in mod_rewrite without the + ENV: prefix are not actually environment + variables. Rather, they are variables special to mod_rewrite + which cannot be accessed from other modules.

+ +
top
+
+

Special Purpose Environment Variables

+ + +

Interoperability problems have led to the introduction of + mechanisms to modify the way Apache behaves when talking to + particular clients. To make these mechanisms as flexible as + possible, they are invoked by defining environment variables, + typically with BrowserMatch, though SetEnv and PassEnv could also be used, for example.

+ +

downgrade-1.0

+ + +

This forces the request to be treated as a HTTP/1.0 request + even if it was in a later dialect.

+ + +

force-gzip

+ +

If you have the DEFLATE filter activated, this + environment variable will ignore the accept-encoding setting of + your browser and will send compressed output unconditionally.

+ +

force-no-vary

+ + +

This causes any Vary fields to be removed from + the response header before it is sent back to the client. Some + clients don't interpret this field correctly; setting this + variable can work around this problem. Setting this variable + also implies force-response-1.0.

+ + +

force-response-1.0

+ + +

This forces an HTTP/1.0 response to clients making an HTTP/1.0 + request. It was originally + implemented as a result of a problem with AOL's proxies. Some + HTTP/1.0 clients may not behave correctly when given an HTTP/1.1 + response, and this can be used to interoperate with them.

+ + + +

gzip-only-text/html

+ + +

When set to a value of "1", this variable disables the DEFLATE + output filter provided by mod_deflate for + content-types other than text/html. If you'd rather + use statically compressed files; mod_negotiation + evaluates the variable as well (not only for gzip, but for all + encodings that differ from "identity").

+ + +

no-gzip

+ +

When set, the DEFLATE filter of + mod_deflate will be turned off and + mod_negotiation will refuse to deliver encoded + resources.

+ + + +

nokeepalive

+ + +

This disables KeepAlive + when set.

+ + + +

prefer-language

+ +

This influences mod_negotiation's behaviour. If + it contains a language tag (such as en, ja + or x-klingon), mod_negotiation tries + to deliver a variant with that language. If there's no such variant, + the normal negotiation process + applies.

+ + + +

redirect-carefully

+ + +

This forces the server to be more careful when sending a redirect + to the client. This is typically used when a client has a known + problem handling redirects. This was originally implemented as a + result of a problem with Microsoft's WebFolders software which has + a problem handling redirects on directory resources via DAV + methods.

+ + + +

suppress-error-charset

+ + +

Available in versions after 2.0.54

+ +

When Apache issues a redirect in response to a client request, + the response includes some actual text to be displayed in case + the client can't (or doesn't) automatically follow the redirection. + Apache ordinarily labels this text according to the character set + which it uses, which is ISO-8859-1.

+

However, if the redirection is to a page that uses a different + character set, some broken browser versions will try to use the + character set from the redirection text rather than the actual page. + This can result in Greek, for instance, being incorrectly rendered.

+

Setting this environment variable causes Apache to omit the character + set for the redirection text, and these broken browsers will then correctly + use that of the destination page.

+ + + +

force-proxy-request-1.0, proxy-nokeepalive, proxy-sendchunked, proxy-sendcl

+ +

These directives alter the protocol behavior of + mod_proxy. See the mod_proxy + documentation for more details.

+ + +
top
+
+

Examples

+ + +

Changing protocol behavior with misbehaving clients

+ + +

Earlier versions recommended that the following lines be included in + httpd.conf to deal with known client problems. Since the affected clients + are no longer seen in the wild, this configuration is likely no-longer + necessary.

+
+#
+# The following directives modify normal HTTP response behavior.
+# The first directive disables keepalive for Netscape 2.x and browsers that
+# spoof it. There are known problems with these browser implementations.
+# The second directive is for Microsoft Internet Explorer 4.0b2
+# which has a broken HTTP/1.1 implementation and does not properly
+# support keepalive when it is used on 301 or 302 (redirect) responses.
+#
+BrowserMatch "Mozilla/2" nokeepalive
+BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
+
+#
+# The following directive disables HTTP/1.1 responses to browsers which
+# are in violation of the HTTP/1.0 spec by not being able to grok a
+# basic 1.1 response.
+#
+BrowserMatch "RealPlayer 4\.0" force-response-1.0
+BrowserMatch "Java/1\.0" force-response-1.0
+BrowserMatch "JDK/1\.0" force-response-1.0
+ + +

Do not log requests for images in the access log

+ + +

This example keeps requests for images from appearing in the + access log. It can be easily modified to prevent logging of + particular directories, or to prevent logging of requests + coming from particular hosts.

+ 
+SetEnvIf Request_URI \.gif image-request
+SetEnvIf Request_URI \.jpg image-request
+SetEnvIf Request_URI \.png image-request
+CustomLog logs/access_log common env=!image-request
+ + +

Prevent "Image Theft"

+ + +

This example shows how to keep people not on your server + from using images on your server as inline-images on their + pages. This is not a recommended configuration, but it can work + in limited circumstances. We assume that all your images are in + a directory called /web/images.

+ 
+SetEnvIf Referer "^http://www.example.com/" local_referal
+# Allow browsers that do not send Referer info
+SetEnvIf Referer "^$" local_referal
+<Directory /web/images>
+   Order Deny,Allow
+   Deny from all
+   Allow from env=local_referal
+</Directory>
+ +

For more information about this technique, see the + ApacheToday tutorial " + Keeping Your Images from Adorning Other Sites".

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/env.html.ja.euc-jp b/docs/manual/env.html.ja.euc-jp new file mode 100644 index 00000000..30c9cb87 --- /dev/null +++ b/docs/manual/env.html.ja.euc-jp @@ -0,0 +1,403 @@ + + + +Apache ¤Î´Ä¶­ÊÑ¿ô - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

Apache ¤Î´Ä¶­ÊÑ¿ô

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

Apache HTTP ¥µ¡¼¥Ð¤Ï´Ä¶­ÊÑ¿ô¤È¸Æ¤Ð¤ì¤ë¡¢Ì¾Á°¤Î¤Ä¤¤¤¿ + ÊÑ¿ô¤Ë¾ðÊó¤òµ­²±¤¹¤ë»ÅÁȤߤòÄ󶡤·¤Æ¤¤¤Þ¤¹¡£¤³¤Î¾ðÊó¤Ï¥í¥°¼ý½¸¤ä + ¥¢¥¯¥»¥¹À©¸æ¤Ê¤É¤Î¤¤¤í¤¤¤í¤ÊÁàºî¤òÀ©¸æ¤¹¤ë¤¿¤á¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤é¤ÎÊÑ¿ô¤Ï CGI ¥¹¥¯¥ê¥×¥È¤Ê¤É¤Î³°Éô¥×¥í¥°¥é¥à¤ÈÄÌ¿®¤¹¤ë¤¿¤á¤Ë¤â + »È¤ï¤ì¤Þ¤¹¡£¤³¤Îʸ½ñ¤Ï¤½¤ì¤é¤ÎÊÑ¿ô¤ÎÁàºîÊýË¡¤È»ÈÍÑÊýË¡¤ò¤¤¤¯¤Ä¤« + ¾Ò²ð¤·¤Þ¤¹¡£

+ +

¤³¤ì¤é¤ÎÊÑ¿ô¤Ï´Ä¶­ÊÑ¿ô¤È¸Æ¤Ð¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥° + ¥·¥¹¥Æ¥à¤Ë¤è¤Ã¤ÆÀ©¸æ¤µ¤ì¤Æ¤¤¤ë´Ä¶­ÊÑ¿ô¤ÈƱ¤¸¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¼ÂºÝ¤Ï¡¢¤³¤ì¤é¤ÎÊÑ¿ô¤Ï Apache ¤ÎÆâÉô¹½Â¤¤ÎÃæ¤Ëµ­²±¤µ¤ì¡¢Áàºî¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤½¤ì¤é¤Ï¡¢CGI ¤ä SSI ¥¹¥¯¥ê¥×¥È¤ËÅϤµ¤ì¤¿¤È¤­¤À¤±¡¢¼ÂºÝ¤Î + ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î´Ä¶­ÊÑ¿ô¤Ë¤Ê¤ê¤Þ¤¹¡£¥µ¡¼¥Ð¼«¿È¤¬ + ¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î´Ä¶­¤òÁàºî¤·¤¿¤¤¾ì¹ç¤Ï¡¢ + ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥·¥§¥ë¤¬Ä󶡤·¤Æ¤¤¤ëɸ½à¤Î´Ä¶­ÊÑ¿ô¤Î + ÁàºîÊýË¡¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
+ +
top
+
+

´Ä¶­ÊÑ¿ô¤ÎÀßÄê

+ +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

´ðËÜŪ¤Ê´Ä¶­¤ÎÁàºî

+ + +

Apache ¤Ë¤ª¤¤¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë°ìÈÖ´ðËÜŪ¤ÊÊýË¡¤Ï¡¢ + ̵¾ò·ï¤Ë´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë SetEnv ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¤¹¡£ + PassEnv + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¡¢Apache ¤¬µ¯Æ°¤µ¤ì¤¿¥·¥§¥ë¤Î + ´Ä¶­ÊÑ¿ô¤òÅϤ¹¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ + +

¥ê¥¯¥¨¥¹¥ÈËè¤Ë¾ò·ï¤Ë´ð¤Å¤¤¤ÆÀßÄꤹ¤ë

+ + +

¤è¤ê½ÀÆðÀ­¤ò¹â¤á¤ë¤¿¤á¤Ë¡¢mod_setenvif + ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢¥ê¥¯¥¨¥¹¥È¤Î + ÆÃÀ­¤Ë´ð¤Å¤¤¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¡¢ÆÃÄê¤Î¥Ö¥é¥¦¥¶ + (User-Agent) ¤Î¥ê¥¯¥¨¥¹¥È¤äÆÃÄê¤Î Referer [°Õ¿ÞŪ¤ÊÄÖ¤ê¤Ç¤¹] + (ÌõÃí: Àµ¤·¤¤ÄÖ¤ê¤Ï referrer ¤Ç¤¹¤¬¡¢HTTP ¤Î»ÅÍÍ¤Ç¤Ï Referer + ¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹) ¥Ø¥Ã¥À¤¬¸«¤Ä¤«¤Ã¤¿¤È¤­¤Î¤ßÊÑ¿ô¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + mod_rewrite ¤Î RewriteRule + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤ª¤¤¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë [E=...] + ¥ª¥×¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢ + ¤è¤ê½ÀÆð¤ÊÀßÄê¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ + +

°ì°Õ¤Ê¼±ÊÌ»Ò

+ + +

mod_unique_id ¤Ï¡¢Èó¾ï¤Ë¸Â¤é¤ì¤¿¾ò·ï¤Î²¼¤Ç + ¡Ö¤¹¤Ù¤Æ¡×¤Î¥ê¥¯¥¨¥¹¥È¤Ë¤Ä¤¤¤Æ¡¢°ì°Õ¤Ç¤¢¤ë¤³¤È¤¬Êݾڤµ¤ì¤Æ¤¤¤ëÃͤò´Ä¶­ÊÑ¿ô + UNIQUE_ID ¤ËÀßÄꤷ¤Þ¤¹¡£

+ + +

ɸ½à CGI ÊÑ¿ô

+ + +

Apache ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ÇÀßÄꤵ¤ì¤¿´Ä¶­ÊÑ¿ô¤È¥·¥§¥ë¤«¤éÅϤµ¤ì¤ë + ´Ä¶­ÊÑ¿ô¤Ë²Ã¤¨¤Æ¡¢CGI ¥¹¥¯¥ê¥×¥È¤È SSI ¥Ú¡¼¥¸¤Ë¤Ï CGI ¤Î»ÅÍͤÇÍ׵ᤵ¤ì¤Æ¤¤¤ë¡¢ + ¥ê¥¯¥¨¥¹¥È¤Î¥á¥¿¾ðÊó¤ò»ý¤Ã¤¿´Ä¶­ÊÑ¿ô¤ÎÁȤ¬Ä󶡤µ¤ì¤Þ¤¹¡£

+ + +

¤¤¤¯¤Ä¤«¤ÎÃí°Õ

+ + +
    +
  • ´Ä¶­¤òÁàºî¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æɸ½à CGI + ÊÑ¿ô¤ò¾å½ñ¤­¤·¤¿¤êÊѹ¹¤·¤¿¤ê¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
    • + +
  • CGI ¥¹¥¯¥ê¥×¥È¤òµ¯Æ°¤¹¤ë¤¿¤á¤Ë suexec + ¤¬»ÈÍѤµ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢CGI ¥¹¥¯¥ê¥×¥È¤¬µ¯Æ°¤¹¤ë¤¿¤á¤Ë¡¢´Ä¶­ÊÑ¿ô¤Ï°ÂÁ´¤Ê´Ä¶­ÊÑ¿ô¤ÎÁȤËÀ°Íý¤µ¤ì¤Þ¤¹¡£ + ¤³¤Î°ÂÁ´¤Ê´Ä¶­ÊÑ¿ô¤Î½¸¹ç¤Ï¡¢¥³¥ó¥Ñ¥¤¥ë»þ¤Ë suexec.c + ¤ÇÄêµÁ¤µ¤ì¤Þ¤¹¡£
    • + +
  • °Ü¿¢À­¤Î¤¿¤á¤Ë¡¢´Ä¶­ÊÑ¿ô¤Î̾Á°¤Ï¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È¡¢ + ¿ô»ú¤È¥¢¥ó¥À¡¼¥¹¥³¥¢ (ÌõÃí: '_') ¤À¤±¤«¤éÀ®¤ê¤Þ¤¹¡£ + ¤µ¤é¤Ë¡¢ºÇ½é¤Îʸ»ú¤Ï¿ô»ú¤Ç¤¢¤Ã¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ + ¤³¤ÎÀ©¸Â¤Ë¹ç¤ï¤Ê¤¤Ê¸»ú¤Ï CGI ¥¹¥¯¥ê¥×¥È¤È SSI + ¥Ú¡¼¥¸¤ËÅϤµ¤ì¤ë¤È¤­¤Ë¥¢¥ó¥À¡¼¥¹¥³¥¢¤ËÃÖ´¹¤µ¤ì¤Þ¤¹¡£
    • +
+ +
top
+
+

´Ä¶­ÊÑ¿ô¤Î»ÈÍÑ

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

CGI ¥¹¥¯¥ê¥×¥È

+ + +

´Ä¶­ÊÑ¿ô¤Î¼ç¤ÊÍøÍÑË¡¤Î°ì¤Ä¤Ï¡¢CGI ¥¹¥¯¥ê¥×¥È¤Ë¾ðÊó¤òÅÁ¤¨¤ë¤³¤È¤Ç¤¹¡£ + ¾å¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¡¢CGI ¥¹¥¯¥ê¥×¥È¤ËÅϤµ¤ì¤ë´Ä¶­ÊÑ¿ô¤Ï Apache + ¤ÎÀßÄê¤Ë¤è¤êÀßÄꤵ¤ì¤ëÊÑ¿ô¤Ë²Ã¤¨¤Æ¡¢¥ê¥¯¥¨¥¹¥È¤Îɸ½à¤Î¥á¥¿¾ðÊó¤ò´Þ¤ó¤Ç¤¤¤Þ¤¹¡£ + ¾ÜºÙ¤Ï CGI ¥Á¥å¡¼¥È¥ê¥¢¥ë + ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ + +

SSI ¥Ú¡¼¥¸

+ + +

mod_include ¤Î INCLUDES ¥Õ¥£¥ë¥¿¤Ç½èÍý¤µ¤ì¤ë + server-parsed (SSI) ¥É¥­¥å¥á¥ó¥È¤Ç¤Ï¡¢echo + Í×ÁǤò»ÈÍѤ¹¤ë¤È´Ä¶­ÊÑ¿ô¤¬½ÐÎϤµ¤ì¤Þ¤¹¡£ + ¤Þ¤¿¡¢¥Ú¡¼¥¸¤Î¤¢¤ëÉôʬ¤¬¥ê¥¯¥¨¥¹¥È¤ÎÀ­¼Á¤Ë±þ¤¸¤ÆÊѹ¹¤µ¤ì¤ë¤è¤¦¤Ë¡¢ + ´Ä¶­ÊÑ¿ô¤ò¥Õ¥í¡¼À©¸æÍ×ÁǤǻȤ¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¾ÜºÙ¤Ï + SSI ¥Á¥å¡¼¥È¥ê¥¢¥ë ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ + +

¥¢¥¯¥»¥¹À©¸æ

+ + +

allow from env= ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È deny from env= + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¡¢¥µ¡¼¥Ð¤Ø¤Î¥¢¥¯¥»¥¹¤ò´Ä¶­ÊÑ¿ô¤ÎÃͤÇÀ©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + SetEnvIf + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈÁȤ߹ç¤ï¤»¤ë¤³¤È¤Ç¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÎÆÃÀ­¤Ë´ð¤Å¤¤¤Æ + ¥µ¡¼¥Ð¤Ø¤Î¥¢¥¯¥»¥¹À©¸æ¤ò½ÀÆð¤Ë¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¡¢¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¡¢ÆÃÄê¤Î¥Ö¥é¥¦¥¶ (User-Agent) + ¤«¤é¤Î¥¢¥¯¥»¥¹¤òµñÈݤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ + +

¾ò·ïÉÕ¤­¥í¥°µ­Ï¿

+ + +

LogFormat + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥ª¥×¥·¥ç¥ó %e + ¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢´Ä¶­ÊÑ¿ô¤ò¥¢¥¯¥»¥¹¥í¥°¤Ëµ­Ï¿¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤µ¤é¤Ë¡¢ + CustomLog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¾ò·ïʬ´ô¼°¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢ + ´Ä¶­ÊÑ¿ô¤ÎÃͤˤè¤Ã¤Æ¥ê¥¯¥¨¥¹¥È¤ò¥í¥°¤Ëµ­Ï¿¤¹¤ë¤«¤É¤¦¤«¤ò·è¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + SetEnvIf + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈÁȤ߹ç¤ï¤»¤ë¤³¤È¤Ç¡¢ + ¤É¤Î¥ê¥¯¥¨¥¹¥È¤ò¥í¥°¤Ëµ­Ï¿¤¹¤ë¤«¤ò½ÀÆð¤ËÀ©¸æ¤¹¤ë¤³¤È¤¬²Äǽ¤Ë¤Ê¤ê¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢ + gif ¤Ç½ª¤ï¤ë¥Õ¥¡¥¤¥ë̾¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï¥í¥°¤Ëµ­Ï¿¤·¤Ê¤¤¡¢ + °ã¤¦¥µ¥Ö¥Í¥Ã¥È¤Î¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤À¤±¤ò¥í¥°¤Ëµ­Ï¿¤¹¤ë¡¢ + ¤È¤¤¤¦ÁªÂò¤¬²Äǽ¤Ç¤¹¡£

+ + +

¾ò·ïÉÕ¤­±þÅú¥Ø¥Ã¥À

+ + +

Header + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï´Ä¶­ÊÑ¿ô¤Î¸ºß¤äÉԺߤˤè¤Ã¤Æ¥¯¥é¥¤¥¢¥ó¥È¤Ø¤Î±þÅú¤ËÆÃÄê¤Î + HTTP ¥Ø¥Ã¥À¤òÉÕ¤±¤ë¤«¤É¤¦¤«¤ò·è¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¤¿¤È¤¨¤Ð¡¢¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È + ¤Ë¤¢¤ë¥Ø¥Ã¥À¤¬¤¢¤ë¾ì¹ç¤Ë¤Î¤ßÆÃÄê¤Î±þÅú¥Ø¥Ã¥À¤òÁ÷¤ë¡¢¤È¤¤¤¦¤è¤¦¤Ê¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+ + + +

³°Éô¥Õ¥£¥ë¥¿¤ÎŬÍÑ

+ + +

ExtFilterDefine + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ + mod_ext_filter ¤ÇÀßÄꤵ¤ì¤ë³°Éô¥Õ¥£¥ë¥¿¤Ï¡¢ + disableenv= ¤È enableenv= + ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¡¢´Ä¶­ÊÑ¿ô¤Ë¤è¤ë¾ò·ïÉÕ¤­Å¬ÍѤ¬¤Ç¤­¤Þ¤¹¡£

+ + +

URL ¤Î½ñ¤­´¹¤¨

+ + +

RewriteCond + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Çɾ²Áʸ»úÎó¤È¤·¤Æ + %{ENV:...} ¼°¤ò»ØÄꤹ¤ë¤³¤È¤Ç¡¢mod_rewrite + ¤Î½ñ¤­´¹¤¨¥¨¥ó¥¸¥ó¤¬´Ä¶­ÊÑ¿ô¤Ë´ð¤¤¤Æ¾ò·ïʬ´ô¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + mod_rewrite ¤¬»ÈÍѲÄǽ¤ÊÊÑ¿ô¤Ç ENV: ¤¬Á°¤Ë¤Ä¤¤¤Æ¤¤¤Ê¤¤ÊÑ¿ô¤Ï¡¢ + ¼ÂºÝ¤Ï´Ä¶­ÊÑ¿ô¤Ç¤Ï¤Ê¤¤¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤½¤ì¤é¤Ï¾¤Î¥â¥¸¥å¡¼¥ë¤«¤é¤Ï»ÈÍѤǤ­¤Ê¤¤ mod_rewrite ÍѤÎÆÃÊ̤ÊÊÑ¿ô¤Ç¤¹¡£ +

+ +
top
+
+

ÆÃÊ̤ÊÌÜŪ¤Î´Ä¶­ÊÑ¿ô

+ + +

¸ß´¹À­¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Ë¡¢ÆÃÄê¤Î¥¯¥é¥¤¥¢¥ó¥È¤ÈÄÌ¿®¤·¤Æ¤¤¤ë¤È¤­¤Ï + Apache ¤ÎÆ°ºî¤òÊѹ¹¤Ç¤­¤ëµ¡¹½¤¬Æ³Æþ¤µ¤ì¤Þ¤·¤¿¡£¤Ç¤­¤ë¤À¤±½ÀÆð¤Ë¤¹¤ë¤¿¤á¤Ë¡¢ + ¤³¤ì¤é¤Îµ¡¹½¤Ï´Ä¶­ÊÑ¿ô¤òÄêµÁ¤¹¤ë¤³¤È¤Ç¸Æ¤Ó½Ð¤µ¤ì¤Þ¤¹¡£ÉáÄ̤ϡ¢ + BrowserMatch + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¤¤Þ¤¹¤¬¡¢¤¿¤È¤¨¤Ð SetEnv ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä PassEnv ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤â»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

downgrade-1.0

+ + +

¤³¤ì¤ò»ØÄꤹ¤ë¤³¤È¤Ç¡¢¥ê¥¯¥¨¥¹¥È¤¬ HTTP/1.0 + ¤è¤ê¿·¤·¤¤¥×¥í¥È¥³¥ë¤Î¾ì¹ç¤Ç¤â¡¢HTTP/1.0 ¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£

+ + +

force-gzip

+ +

DEFLATE ¥Õ¥£¥ë¥¿¤¬»ÈÍѤ¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¤­¤Ë¡¢ + ¤³¤Î´Ä¶­ÊÑ¿ô¤Ï¥Ö¥é¥¦¥¶¤Î accept-encoding ¤ÎÀßÄê¤ò̵»ë¤·¤Æ¾ï¤Ë + °µ½Ì¤µ¤ì¤¿½ÐÎϤòÁ÷¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

force-no-vary

+ + +

±þÅú¥Ø¥Ã¥À¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤é¤ì¤ëÁ°¤Ë Vary + ¥Õ¥£¡¼¥ë¥É¤ò¼è¤ê½ü¤­¤Þ¤¹¡£ + ¥¯¥é¥¤¥¢¥ó¥È¤ÎÃæ¤Ë¤Ï¤³¤Î¥Õ¥£¡¼¥ë¥É¤òÀµ¤·¤¯²ò¼á¤·¤Ê¤¤¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ÎÊÑ¿ô¤òÀßÄꤹ¤ë¤³¤È¤Ç¤½¤ÎÌäÂê¤ò²óÈò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ÎÊÑ¿ô¤òÀßÄꤹ¤ë¤È¡¢force-response-1.0 + ¤¬ÀßÄꤵ¤ì¤¿¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ + +

force-response-1.0

+ + +

¤³¤ì¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢HTTP/1.0 ¥ê¥¯¥¨¥¹¥È¤òȯ¹Ô¤¹¤ë¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ·¤Æ¤Ï + ¾ï¤Ë HTTP/1.0 ¤Ç±þÅú¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤Îµ¡Ç½¤Ï¡¢ + ¸µ¡¹¤Ï AOL ¤Î¥×¥í¥­¥·¤ÎÌäÂê¤Î¤¿¤á¤Ë¼ÂÁõ¤µ¤ì¤Þ¤·¤¿¡£HTTP/1.0 ¥¯¥é¥¤¥¢¥ó¥È¤ÎÃæ¤Ë¤Ï¡¢ + HTTP/1.1 ¤Î±þÅú¤òÊÖ¤µ¤ì¤ë¤ÈÀµ¤·¤¯Æ°ºî¤·¤Ê¤¤¤â¤Î¤¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤³¤Îµ¡Ç½¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢¤½¤Î¤è¤¦¤Ê¥¯¥é¥¤¥¢¥ó¥È¤È¤Î´Ö¤Î¸ß´¹À­ÌäÂê¤ò²ò·è¤Ç¤­¤Þ¤¹¡£

+ + +

gzip-only-text/html

+ + +

¤³¤ì¤¬ 1 ¤ËÀßÄꤵ¤ì¤ë¤È¡¢¤³¤ÎÊÑ¿ô¤Ï text/html + °Ê³°¤Î¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ËÂФ¹¤ë¡¢mod_deflate + Ä󶡤ΠDEFLATE ½ÐÎÏ¥Õ¥£¥ë¥¿¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£ + ¤Þ¤¿¡¢ÀÅŪ¤Ë¡¢´û¤Ë°µ½Ì¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤ò»ÈÍѤ·¤¿¤¤¾ì¹ç¡¢ + (gzip ¤À¤±¤Ç¤Ê¤¯¡¢"identity" ¤È°Û¤Ê¤ëÁ´¤Æ¤Î¥¨¥ó¥³¡¼¥É¤ËÂФ·¤Æ) + mod_negotiation ¤âÊÑ¿ô¤òɾ²Á¤·¤Þ¤¹¡£

+ + +

no-gzip

+

¥»¥Ã¥È¤µ¤ì¤ë¤È¡¢mod_deflate ¤Î + DEFLATE ¥Õ¥£¥ë¥¿¤¬¥ª¥Õ¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤½¤·¤Æ mod_negotiation + ¤Ï¥¨¥ó¥³¡¼¥É¤µ¤ì¤¿¥ê¥½¡¼¥¹¤òÁ÷¤é¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ + +

nokeepalive

+ + +

¤³¤ì¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢KeepAlive ¤ò»ÈÍѤ·¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

prefer-language

+ +

mod_negotiation ¤ÎµóÆ°¤Ë±Æ¶Á¤òÍ¿¤¨¤Þ¤¹¡£ + (en, ja, x-klingon¤È¤¤¤Ã¤¿) + ¸À¸ì¥¿¥°¤¬³ÊǼ¤µ¤ì¤Æ¤¤¤ì¤Ð¡¢¤½¤Î¸À¸ì¤Î variant ¤òÁ÷¿®¤·¤è¤¦¤È¤·¤Þ¤¹¡£ + ¤½¤Î¤è¤¦¤Ê variant ¤¬¤Ê¤¤¾ì¹ç¤Ï¡¢ + Ä̾ï¤Î¥Í¥´¥·¥¨¡¼¥·¥ç¥ó½èÍý¤¬ + ŬÍѤµ¤ì¤Þ¤¹¡£

+ + + + +

redirect-carefully

+ + +

¤³¤ì¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤ÎÁ÷¿®¤ò¥µ¡¼¥Ð¤¬¤è¤êÃí°Õ¿¼¤¯ + ¹Ô¤Ê¤¦¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ¤³¤ì¤ÏÄ̾¥ê¥À¥¤¥ì¥¯¥È¤ËºÝ¤·¤Æ¥¯¥é¥¤¥¢¥ó¥È¤Ë + ÌäÂ꤬¤¢¤ë¤³¤È¤¬Ê¬¤«¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë»È¤ï¤ì¤Þ¤¹¡£¤³¤Îµ¡Ç½¤Ï¸µ¡¹¤Ï + ¥Þ¥¤¥¯¥í¥½¥Õ¥È¤Î¥¦¥§¥Ö¥Õ¥©¥ë¥À¤Î¥½¥Õ¥È¤¬ DAV + ¥á¥½¥Ã¥É¤Ë¤è¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Î¥ê¥½¡¼¥¹¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤Î°·¤¤¤Ë + ÌäÂ꤬¤ê¡¢¤½¤ì¤ò²óÈò¤¹¤ë¤¿¤á¤Ë¼ÂÁõ¤µ¤ì¤Þ¤·¤¿¡£

+ + + +

suppress-error-charset

+ + +

Apache 2.2 °Ê¹ß¤ÇÍøÍѲÄǽ

+ +

¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë±þÅú¤È¤·¤Æ¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷¿®¤¹¤ëºÝ¡¢ + ¥ì¥¹¥Ý¥ó¥¹¤Ë¤Ï¥ê¥À¥¤¥ì¥¯¥È¤¬¼«Æ°Åª¤Ë¹Ô¤Ê¤¨¤Ê¤¤ (¹Ô¤Ê¤ï¤ì¤Ê¤¤) + ¾ì¹ç¤Ëɽ¼¨¤¹¤ë¥Æ¥­¥¹¥È¤¬´Þ¤Þ¤ì¤Þ¤¹¡£ + Ä̾¤³¤Î¥Æ¥­¥¹¥È¤Ë¹çÃפ·¤¿¥­¥ã¥é¥¯¥¿¥»¥Ã¥È¡¢ISO-8859-1 + ¤Ç¥é¥Ù¥ëÉÕ¤±¤ò¤·¤Þ¤¹¡£

+

¤·¤«¤·¡¢¥ê¥À¥¤¥ì¥¯¥ÈÀ褬Ê̤Îʸ»ú¥»¥Ã¥È¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢ + ¤¢¤ëÌäÂê¤Î¤¢¤ë¥Ö¥é¥¦¥¶¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢ + ¥ê¥À¥¤¥ì¥¯¥ÈÀè¤Î¼ÂºÝ¤Îʸ»ú¥»¥Ã¥È¤ÎÂå¤ï¤ê¤Ë¡¢ + ¥ê¥À¥¤¥ì¥¯¥È¸µ¤Îʸ»ú¥»¥Ã¥È¤ò»È¤Ã¤Æ¤·¤Þ¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¤½¤Î·ë²Ì¡¢Î㤨¤ÐÊѤÊÉÁ²è¤¬¹Ô¤Ê¤ï¤ì¤¿¤ê¤·¤Æ¡¢Æɤá¤Ê¤¯¤Ê¤Ã¤¿¤ê¤·¤Þ¤¹¡£

+

¤³¤Î´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë¤³¤È¤Ç¡¢¥ê¥À¥¤¥ì¥¯¥·¥ç¥ó¥Æ¥­¥¹¥È¤ËÂФ¹¤ë + ¥­¥ã¥é¥¯¥¿¥»¥Ã¥È¤Î»ØÄê¤ò½üµî¤·¤Þ¤¹¤Î¤Ç¡¢¤½¤ì¤éÌäÂê¤Î¤¢¤ë¥Ö¥é¥¦¥¶¤Ç¤â + ¥ê¥À¥¤¥ì¥¯¥ÈÀè¤Îʸ»ú¥»¥Ã¥È¤òÀµ¤·¤¯»È¤¦¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£

+ + + +

force-proxy-request-1.0, proxy-nokeepalive, proxy-sendchunked, proxy-sendcl

+ +

¤³¤ì¤é¤Î»Ø¼¨»Ò¤Ï mod_proxy ¤ÎµóÆ°¤òÊѹ¹¤·¤Þ¤¹¡£ + ¾ÜºÙ¤Ï mod_proxy ¤Î¥É¥­¥å¥á¥ó¥È¤ò¤´»²¾È¤¯¤À¤µ¤¤¡£

+ + +
top
+
+

Îã

+ + +

¤ª¤«¤·¤ÊµóÆ°¤ò¤¹¤ë¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ·¤Æ¥×¥í¥È¥³¥ë¤ÎÆ°ºî¤òÊѹ¹¤¹¤ë

+ + +

¥¯¥é¥¤¥¢¥ó¥È¤Ë´Ø¤¹¤ë´ûÃΤÎÌäÂê¤ËÂн褹¤ë¤¿¤á¤Ë¡¢°Ê²¼¤Î¹Ô¤ò + httpd.conf ¤ËÆþ¤ì¤ë¤³¤È¤ò¿ä¾©¤·¤Æ¤¤¤Þ¤¹¡£

+

¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤Î Apache ¤Ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÎÌäÂê¤ËÂбþ¤¹¤ë¤¿¤á¤Ë + httpd.conf ¤Ë¼¡¤Î¹Ô¤ò²Ã¤¨¤ë¤è¤¦¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤·¤¿¤¬¡¢ + º£¤È¤Ê¤Ã¤Æ¤Ï¡¢ÌäÂê¤È¤·¤Æ¤¤¤¿¥¯¥é¥¤¥¢¥ó¥È¤Ï¼ÂºÝ¤Ë¤Ï¸«¤«¤±¤ë¤³¤È¤Ï + ¤Ê¤¯¤Ê¤Ã¤Æ¤­¤¿¤Î¤Ç¡¢¤³¤ÎÀßÄê¤Ï¤â¤Ï¤äɬÍפʤ¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+
+#
+# The following directives modify normal HTTP response behavior.
+# The first directive disables keepalive for Netscape 2.x and browsers that
+# spoof it. There are known problems with these browser implementations.
+# The second directive is for Microsoft Internet Explorer 4.0b2
+# which has a broken HTTP/1.1 implementation and does not properly
+# support keepalive when it is used on 301 or 302 (redirect) responses.
+#
+BrowserMatch "Mozilla/2" nokeepalive
+BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
+
+#
+# The following directive disables HTTP/1.1 responses to browsers which
+# are in violation of the HTTP/1.0 spec by not being able to grok a
+# basic 1.1 response.
+#
+BrowserMatch "RealPlayer 4\.0" force-response-1.0
+BrowserMatch "Java/1\.0" force-response-1.0
+BrowserMatch "JDK/1\.0" force-response-1.0
+ + +

²èÁü¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò¥¢¥¯¥»¥¹¥í¥°¤Ëµ­Ï¿¤·¤Ê¤¤

+ + +

¤³¤ÎÎã¤Ç¤Ï¡¢²èÁü¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤¬¥¢¥¯¥»¥¹¥í¥°¤Ë¸½¤ì¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ¤³¤ì¤òÊѹ¹¤¹¤ë¤³¤È¤Ç¡¢ÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î¥í¥°¼ý½¸¤ò¤ä¤á¤¿¤ê¡¢ + ÆÃÄê¤Î¥Û¥¹¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤Î¥í¥°¼ý½¸¤ò¤ä¤á¤¿¤ê¤¹¤ë¤³¤È¤¬´Êñ¤Ë¤Ç¤­¤Þ¤¹¡£ +

+ 
+SetEnvIf Request_URI \.gif image-request
+SetEnvIf Request_URI \.jpg image-request
+SetEnvIf Request_URI \.png image-request
+CustomLog logs/access_log common env=!image-request
+ + +

¡Ö²èÁü¤ÎÅðÍѡפòËɤ°

+ + +

¤³¤ÎÎã¤Ï¡¢Ê̤Υµ¡¼¥Ð¤Ë¤¤¤ë¿Í¤¬¡¢¤¢¤Ê¤¿¤Î¥µ¡¼¥Ð¤Ë¤¢¤ë²èÁü¤ò + inline ²èÁü¤È¤·¤Æ»ÈÍѤ¹¤ë¤³¤È¤òËɤ®¤Þ¤¹¡£ + ¤³¤ì¤Ï¿ä¾©¤µ¤ì¤Æ¤¤¤ëÀßÄê¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢¤¢¤ë¸ÂÄꤵ¤ì¤¿¾õ¶·¤Ç¤ÏÍ­¸ú¤Ç¤¹¡£ + ¤³¤³¤Ç¤Ï¡¢¤¹¤Ù¤Æ¤Î²èÁü¤Ï /web/images + ¤È¤¤¤¦¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë¤È²¾Äꤷ¤Þ¤¹¡£

+ 
+SetEnvIf Referer "^http://www.example.com/" local_referal
+# Allow browsers that do not send Referer info
+SetEnvIf Referer "^$" local_referal
+<Directory /web/images>
+   Order Deny,Allow
+   Deny from all
+   Allow from env=local_referal
+</Directory>
+ +

¤³¤Î¼êË¡¤Ë´Ø¤¹¤ë¾Ü¤·¤¤¾ðÊó¤Ï ApacheToday ¤Î¥Á¥å¡¼¥È¥ê¥¢¥ë¡ÖKeeping Your Images from Adorning Other Sites + ¡×¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/env.html.ko.euc-kr b/docs/manual/env.html.ko.euc-kr new file mode 100644 index 00000000..f8d28a5e --- /dev/null +++ b/docs/manual/env.html.ko.euc-kr @@ -0,0 +1,373 @@ + + + +¾ÆÆÄÄ¡ÀÇ È¯°æº¯¼ö - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¾ÆÆÄÄ¡ÀÇ È¯°æº¯¼ö

+
+

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

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

¾ÆÆÄÄ¡ À¥¼­¹ö´Â ȯ°æº¯¼ö(environment variable)¶ó´Â + º¯¼ö¿¡ Á¤º¸¸¦ ÀúÀåÇÒ ¼ö ÀÖ´Ù. ÀÌ Á¤º¸¸¦ »ç¿ëÇÏ¿© ·Î±×³ª + Á¢±ÙÁ¦¾î µî ¿©·¯ ÀÛ¾÷À» Á¶ÀýÇÑ´Ù. ¶Ç, ȯ°æº¯¼ö´Â CGI ½ºÅ©¸³Æ®¿Í + °°Àº ¿ÜºÎ ÇÁ·Î±×·¥°ú Åë½ÅÇÏ´Â ¼ö´ÜÀÌ µÈ´Ù. ÀÌ ¹®¼­´Â ȯ°æº¯¼ö¸¦ + ´Ù·ç°í »ç¿ëÇÏ´Â ´Ù¾çÇÑ ¹æ¹ýµéÀ» ¼³¸íÇÑ´Ù.

+ +

ÀÌ º¯¼öµéÀ» ȯ°æº¯¼ö¶ó°í ºÎ¸£Áö¸¸, ¿î¿µÃ¼Á¦¿¡¼­ + ¸»Çϴ ȯ°æº¯¼ö¿Í ´Ù¸£´Ù. ÀÌ º¯¼ö´Â ¾ÆÆÄÄ¡ ³»ºÎ¿¡ ÀúÀåµÇ°í + »ç¿ëµÈ´Ù. ȯ°æº¯¼ö´Â CGI ½ºÅ©¸³Æ®³ª Server Side Include + ½ºÅ©¸³Æ®·Î ³Ñ°ÜÁú¶§¸¸ ½ÇÁ¦ ¿î¿µÃ¼Á¦ ȯ°æº¯¼ö°¡ µÈ´Ù. ¼­¹ö¸¦ + ½ÇÇàÇÏ´Â ¿î¿µÃ¼Á¦ ȯ°æÀ» ¼öÁ¤ÇÏ°í ½Í´Ù¸é ¿î¿µÃ¼Á¦ ½©¿¡¼­ + ȯ°æÀ» ¼öÁ¤ÇØ¾ß ÇÑ´Ù.

+
+ +
top
+
+

ȯ°æº¯¼ö ¼³Á¤Çϱâ

+ +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

±âº»ÀûÀΠȯ°æ¼³Á¤

+ + +

¾ÆÆÄÄ¡¿¡¼­ ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÏ´Â °¡Àå ±âº»ÀûÀÎ ¹æ¹ýÀº + ¹«Á¶°ÇÀûÀÎ SetEnv Áö½Ã¾î¸¦ »ç¿ëÇÏ´Â °ÍÀÌ´Ù. PassEnv Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + ¼­¹ö¸¦ ½ÃÀÛÇÑ ½©¿¡¼­ ȯ°æº¯¼ö¸¦ °¡Á®¿Ã ¼öµµ ÀÖ´Ù.

+ + +

¿äû¿¡ µû¸¥ Á¶°ÇºÎ ¼³Á¤

+ + +

´õ À¯¿¬ÇÏ°Ô, mod_setenvif°¡ Á¦°øÇÏ´Â Áö½Ã¾î´Â ¿äû¸¶´Ù + ¿äûÀÇ Æ¯Â¡¿¡ µû¶ó ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù. ¿¹¸¦ µé¾î, ƯÁ¤ + ºê¶ó¿ìÀú·Î (User-Agent) ¿äûÇϰųª ƯÁ¤ Referer (¸ÂÃã¹ýÀÌ + Ʋ¸®Áö ¾Ê¾Ò´Ù) Çì´õ°¡ ÀÖ´Â °æ¿ì¿¡¸¸ º¯¼ö¸¦ ¼³Á¤ÇÒ ¼ö + ÀÖ´Ù. ½ÉÁö¾î mod_rewrite¿¡ ÀÖ´Â RewriteRuleÀÇ + [E=...] ¿É¼ÇÀ» »ç¿ëÇÏ¿© ´õ À¯¿¬ÇÏ°Ô È¯°æº¯¼ö¸¦ + ¼³Á¤ÇÒ ¼öµµ ÀÖ´Ù.

+ + +

À¯ÀÏÇÑ ½Äº°ÀÚ

+ + +

¸¶Áö¸·À¸·Î mod_unique_id´Â °¢ ¿äû¿¡ ´ëÇØ ¾î¶² °æ¿ì¿¡µµ + "¸ðµç" ¿äûÁß¿¡ È®½ÇÈ÷ À¯ÀÏÇÑ(°ãÄ¡Áö¾ÊÀº) °ªÀ¸·Î + UNIQUE_ID ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù.

+ + +

Ç¥ÁØ CGI º¯¼ö

+ + +

CGI ½ºÅ©¸³Æ®¿Í SSI ¹®¼­´Â ¾ÆÆÄÄ¡ ¼³Á¤¿¡¼­ ¼³Á¤ÇÏ¿´°Å³ª + ½©¿¡¼­ °¡Á®¿Â ȯ°æº¯¼ö ¿Ü¿¡ Ãß°¡·Î CGI ±Ô¾àÀÌ ±ÔÁ¤ÇÑ + ¿äû¿¡ ´ëÇÑ Á¤º¸¸¦ ¾Ë·ÁÁִ ȯ°æº¯¼öµéÀ» ¹Þ´Â´Ù.

+ + +

ÁÖÀÇÇÒ Á¡

+ + +
    +
  • ȯ°æ¼³Á¤ Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© Ç¥ÁØ CGI º¯¼ö¸¦ ¹«½ÃÇϰųª + ¼öÁ¤ÇÒ ¼ö ¾ø´Ù.
    • + +
  • suexec°¡ CGI ½ºÅ©¸³Æ®¸¦ + ½ÇÇàÇÏ´Â °æ¿ì, ½ÃÀÛÇϱâÀü¿¡ CGI ½ºÅ©¸³Æ®ÀÇ È¯°æÀº + ¾ÈÀüÇÑ º¯¼öµé¸¸ °¡Áöµµ·Ï û¼ÒµÈ´Ù. + ¾ÈÀüÇÑ º¯¼ö ¸ñ·ÏÀº ÄÄÆÄÀϽà + suexec.c¿¡ Á¤ÀǵȴÙ.
    • + +
  • Æ÷ÆÃÀ» À§ÇØ È¯°æº¯¼ö À̸§¿¡´Â ¿ÀÁ÷ ¹®ÀÚ, ¼ýÀÚ, + ¹ØÁÙ¹®ÀÚ¸¸ »ç¿ëÇÏ´Â °ÍÀÌ ÁÁ´Ù. ¶Ç, ù¹ø° ¹®ÀÚ·Î + ¼ýÀÚ¸¦ »ç¿ëÇÏÁö¾Ê´Â °ÍÀÌ ÁÁ´Ù. CGI ½ºÅ©¸³Æ®³ª SSI + ÆäÀÌÁö¿¡ ³Ñ¾î°¥¶§ ÀÌ¿ÜÀÇ ¹®ÀÚ´Â ¹ØÁÙ·Î ´ëüµÈ´Ù.
    • +
+ +
top
+
+

ȯ°æº¯¼ö »ç¿ëÇϱâ

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

CGI ½ºÅ©¸³Æ®

+ + +

ȯ°æº¯¼öÀÇ ÁÖµÈ ¿ëµµÁß Çϳª´Â CGI ½ºÅ©¸³Æ®¿Í Á¤º¸¸¦ + ±³È¯ÇÏ´Â °ÍÀÌ´Ù. ¾Õ¿¡¼­ ¼³¸íÇßµíÀÌ ¾ÆÆÄÄ¡ ¼³Á¤¿¡¼­ ¼³Á¤ÇÑ + º¯¼ö¿Ü¿¡ ¿äû¿¡ ´ëÇÑ Ç¥ÁØ Á¤º¸¸¦ °¡Áø º¯¼ö°¡ CGI ½ºÅ©¸³Æ®·Î + ³Ñ¾î°£´Ù. ´õ ÀÚ¼¼ÇÑ ³»¿ëÀº CGI + ÅõÅ丮¾óÀ» Âü°íÇ϶ó.

+ + +

SSI ÆäÀÌÁö

+ + +

mod_includeÀÇ INCLUDES ÇÊÅÍ°¡ ó¸®ÇÏ´Â + ¼­¹öÆÄ½Ì (SSI) ¹®¼­´Â echo ¿ä¼Ò¸¦ »ç¿ëÇÏ¿© + ȯ°æº¯¼ö¸¦ Ãâ·ÂÇÒ ¼ö ÀÖ°í, ȯ°æº¯¼ö¸¦ »ç¿ëÇÏ¿© ¿äûÀÇ + Ư¡¿¡ µû¶ó È帧Á¦¾î ¿ä¼Ò·Î ÆäÀÌÁöÀÇ ÀϺθ¦ º¯°æÇÒ ¼ö + ÀÖ´Ù. ¾ÆÆÄÄ¡´Â ¶Ç SSI ¹®¼­¿¡°Ô À§¿¡¼­ ¼³¸íÇÑ Ç¥ÁØ CGI + ȯ°æº¯¼ö¸¦ Á¦°øÇÑ´Ù. ´õ ÀÚ¼¼ÇÑ ³»¿ëÀº SSI ÅõÅ丮¾óÀ» Âü°íÇ϶ó.

+ + +

Á¢±ÙÁ¦¾î

+ + +

allow from env=°ú deny from env= + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ȯ°æº¯¼ö °ª¿¡ µû¶ó ¼­¹ö·ÎÀÇ Á¢±ÙÀ» + Á¶ÀýÇÒ ¼ö ÀÖ´Ù. SetEnvIf¿Í °°ÀÌ »ç¿ëÇϸé + Ŭ¶óÀ̾ðÆ®ÀÇ Æ¯Â¡¿¡ µû¶ó ÀÚÀ¯·Ó°Ô ¼­¹ö·ÎÀÇ Á¢±ÙÀ» Á¦¾îÇÒ + ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, ƯÁ¤ ºê¶ó¿ìÀúÀÇ (User-Agent) Á¢±ÙÀ» + °ÅºÎÇÒ ¼ö ÀÖ´Ù.

+ + +

Á¶°ÇºÎ ·Î±×

+ + +

LogFormatÀÇ + %e ¿É¼ÇÀ» »ç¿ëÇÏ¿© ȯ°æº¯¼ö¸¦ Á¢±Ù ·Î±×¿¡ + ±â·ÏÇÒ ¼ö ÀÖ´Ù. ¶Ç, CustomLog Áö½Ã¾îÀÇ + Á¶°ÇºÎ Çü½ÄÀ» »ç¿ëÇϸé ȯ°æº¯¼öÀÇ »óȲ¿¡ µû¶ó ¿äûÀ» + ·Î±×ÇÒÁö ¿©ºÎ¸¦ °áÁ¤ÇÒ ¼ö ÀÖ´Ù. SetEnvIf¿Í °°ÀÌ »ç¿ëÇÏ¿© + ¾î¶² ¿äûÀ» ·Î±×ÇÒÁö ÀÚÀ¯·Ó°Ô °áÁ¤ÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, + ÆÄÀϸíÀÌ gif·Î ³¡³ª´Â ¿äûÀº ·Î±×ÇÏÁö ¾Ê°Å³ª, + ¿ÜºÎ ³×Æ®¿÷¿¡ Àִ Ŭ¶óÀ̾ðÆ®ÀÇ ¿äû¸¸À» ·Î±×ÇÒ ¼ö ÀÖ´Ù.

+ + +

Á¶°ÇºÎ ÀÀ´ä Çì´õ

+ + +

Header + Áö½Ã¾î´Â Ŭ¶óÀ̾ðÆ®¿¡°Ô ÀÀ´äÀ» º¸³¾¶§ ȯ°æº¯¼öÀÇ À¯¹«¿¡ + µû¶ó ¾î¶² HTTP Çì´õ¸¦ Æ÷ÇÔÇÒÁö °áÁ¤ÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ + µé¾î, Ŭ¶óÀ̾ðÆ®ÀÇ ¿äû¿¡ ƯÁ¤ Çì´õ°¡ ÀÖ´Â °æ¿ì¿¡¸¸ + ¾î¶² ÀÀ´ä Çì´õ¸¦ º¸³¾ ¼ö ÀÖ´Ù.

+ + + +

¿ÜºÎ ÇÊÅÍ ½ÇÇàÇϱâ

+ + +

mod_ext_filterÀÇ ExtFilterDefine + Áö½Ã¾î·Î ¼³Á¤ÇÑ ¿ÜºÎ ÇÊÅ͸¦ disableenv=¿Í + enableenv= ¿É¼ÇÀ» »ç¿ëÇÏ¿© ȯ°æº¯¼ö¿¡ µû¶ó + ¼±ÅÃÀûÀ¸·Î ½ÇÇàÇÒ ¼ö ÀÖ´Ù.

+ + +

URL ÀçÀÛ¼º(Rewriting)

+ + +

RewriteCondÀÇ + TestString¿¡ %{ENV:...} Çü½ÄÀ» + »ç¿ëÇϸé mod_rewriteÀÇ ÀçÀÛ¼º ¿£ÁøÀÌ È¯°æº¯¼ö¿¡ µû¶ó + ´Ù¸£°Ô ÇൿÇÑ´Ù. mod_rewrite¿¡¼­ ¾Õ¿¡ ENV:¸¦ + ºÙÀÌÁö¾Ê°í Á¢±ÙÇÏ´Â º¯¼ö´Â ½ÇÁ¦ ȯ°æº¯¼ö°¡ ¾Æ´ÔÀ» ÁÖÀÇÇ϶ó. + ±×µéÀº ´Ù¸¥ ¸ðµâ¿¡¼­ ÀÐÀ» ¼ö ¾ø´Â mod_rewrite¿¡ ÇÑÁ¤µÈ + º¯¼ö´Ù.

+ +
top
+
+

Ưº°ÇÑ ¸ñÀûÀÇ È¯°æº¯¼ö

+ + +

Ŭ¶óÀ̾ðÆ®¿Í ¿øÈ°ÇÑ µ¿ÀÛÇϱâÀ§ÇØ ¾ÆÆÄÄ¡´Â Ưº°ÇÑ + Ŭ¶óÀ̾ðÆ®¿¡ ´ëÇØ ÀÚ½ÅÀÇ ÇൿÀ» ¼öÁ¤ÇÑ´Ù. º¸Åë BrowserMatch¿¡¼­ + ȯ°æº¯¼ö¸¦ Á¤ÀÇÇÏ¿© ÀÌ·± ¹®Á¦¸¦ ÇØ°áÇÑ´Ù. ±×·¯³ª SetEnv¿Í PassEnv·Îµµ °¡´ÉÇÏ´Ù.

+ +

downgrade-1.0

+ + +

¿äûÀÌ ÀÌÈÄ ¹öÀüÀ» »ç¿ëÇÏ´õ¶óµµ HTTP/1.0 ¿äûÀ¸·Î + ó¸®ÇÑ´Ù.

+ + +

force-gzip

+ +

DEFLATE ÇÊÅ͸¦ »ç¿ëÇÒ¶§ ÀÌ È¯°æº¯¼ö´Â + ºê¶ó¿ìÀúÀÇ accept-encoding ¼³Á¤À» ¹«½ÃÇÏ°í ¹«Á¶°Ç + ¾ÐÃàµÈ °á°ú¸¦ º¸³½´Ù.

+ +

force-no-vary

+ + +

ÀÀ´äÀ» Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³»±â Àü¿¡ ÀÀ´ä Çì´õ¿¡¼­ + Vary Çʵ带 »«´Ù. ¾î¶² Ŭ¶óÀ̾ðÆ®´Â ÀÌ + Çʵ带 Á¦´ë·Î Çؼ®ÇÏÁö ¸øÇÑ´Ù. ÀÌ º¯¼ö´Â ÀÌ·± ¹®Á¦¸¦ + ÇØ°áÇÑ´Ù. ¶ÇÇÑ, ÀÌ º¯¼ö´Â + force-response-1.0À» °¡Á¤ÇÑ´Ù.

+ + +

force-response-1.0

+ + +

HTTP/1.0 ¿äûÀ» Çϴ Ŭ¶óÀ̾ðÆ®¿¡°Ô HTTP/1.0 ÀÀ´äÀ» + °­Á¦ÇÑ´Ù. ¿ø·¡ AOL ÇÁ·Ï½Ã¿¡ ¹®Á¦°¡ À־ ¸¸µé¾îÁ³´Ù. + ¾î¶² HTTP/1.0 Ŭ¶óÀ̾ðÆ®´Â HTTP/1.1 ÀÀ´äÀ» ¹ÞÀ¸¸é Á¦´ë·Î + µ¿ÀÛÇÏÁö ¾ÊÀ¸¹Ç·Î, ÀÌ ¹®Á¦¸¦ ÇØ°áÇϱâÀ§ÇØ »ç¿ëÇÑ´Ù.

+ + +

gzip-only-text/html

+ + +

°ªÀÌ "1"À̸é text/htmlÀÌ ¾Æ´Ñ content-type¿¡ + ´ëÇØ mod_deflateÀÇ DEFLATE Ãâ·ÂÇÊÅ͸¦ + »ç¿ëÇÏÁö ¾Ê´Â´Ù. (gzip »Ó¸¸ ¾Æ´Ï¶ó "identity"°¡ ¾Æ´Ñ ¸ðµç + ÀÎÄÚµùÀÇ) Á¤ÀûÀ¸·Î ¾ÐÃàÇÑ ÆÄÀÏÀÇ °æ¿ì¿¡µµ + mod_negotiationÀº ÀÌ º¯¼ö¸¦ Âü°íÇÑ´Ù.

+ + +

no-gzip

+ +

ÀÌ ¿É¼ÇÀ» ¼³Á¤Çϸé mod_deflateÀÇ + DEFLATE ÇÊÅ͸¦ »ç¿ëÇÏÁö ¾Ê°í, + mod_negotiationÀº ÀÎÄÚµùµÈ ÀÚ¿øÀ» + º¸³»Áö ¾Ê´Â´Ù.

+ + + +

nokeepalive

+ + +

KeepAlive¸¦ + ¹«½ÃÇÑ´Ù.

+ + + +

prefer-language

+ +

ÀÌ º¯¼ö´Â mod_negotiationÀÇ Çൿ¿¡ + ¿µÇâÀ» ¹ÌÄ£´Ù. º¯¼ö°¡ (en, ja, + x-klingon µî) ¾ð¾îű׸¦ ´ã°íÀÖ´Ù¸é, + mod_negotiation´Â ±× ¾ð¾î·Î µÈ º¯ÇüÀ» + º¸³»±æ ½ÃµµÇÑ´Ù. ±×·± º¯ÇüÀÌ ¾ø´Ù¸é ÀϹÝÀûÀÎ Çù»ó °úÁ¤À» ½ÃÀÛÇÑ´Ù.

+ + + +

redirect-carefully

+ + +

¼­¹ö°¡ ´õ Á¶½ÉÈ÷ Ŭ¶óÀ̾ðÆ®¿¡°Ô ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù. + º¸Åë ¸®´ÙÀÌ·º¼ÇÀ» ó¸®Çϴµ¥ ¹®Á¦°¡ Àִ Ŭ¶óÀ̾ðÆ®À» + À§ÇØ »ç¿ëÇÑ´Ù. ¿ø·¡ MicrosoftÀÇ WebFolders ¼ÒÇÁÆ®¿þ¾î°¡ + DAV ¸Þ½áµå¸¦ ÅëÇØ µð·ºÅ丮 ÀÚ¿øÀÇ ¸®´ÙÀÌ·º¼ÇÀ» ó¸®Çϴµ¥ + ¹®Á¦°¡ À־ ¸¸µé¾îÁ³´Ù.

+ + + +

suppress-error-charset

+ + +

2.0.40 ÀÌÈÄ ¹öÀü¿¡ ÀÖ´Ù

+ +

¾ÆÆÄÄ¡°¡ Ŭ¶óÀ̾ðÆ®ÀÇ ¿äû¿¡ ´ëÇÑ ÀÀ´äÀ¸·Î ¸®´ÙÀÌ·º¼ÇÀ» + º¸³¾¶§ Ŭ¶óÀ̾ðÆ®°¡ ÀÚµ¿À¸·Î ¸®´ÙÀÌ·º¼ÇÀ» µû¶ó°¡Áö ¸øÇÏ´Â(ȤÀº + ¾Ê´Â) °æ¿ì¿¡ ´ëºñÇÏ¿© ÀÀ´ä¿¡ »ç¿ëÀÚ¿¡°Ô º¸¿©ÁÙ ¹®±¸¸¦ Æ÷ÇÔÇÑ´Ù. + ¾ÆÆÄÄ¡´Â º¸Åë ÀÌ ±ÛÀ» ¾ÆÆÄÄ¡°¡ »ç¿ëÇÏ´Â ¹®ÀÚÁýÇÕÀÎ ISO-8859-1·Î + Ç¥½ÃÇÑ´Ù.

+

±×·¯³ª ¸®´ÙÀÌ·º¼ÇµÈ ÆäÀÌÁö°¡ ´Ù¸¥ ¹®ÀÚÁýÇÕÀ» »ç¿ëÇÒ °æ¿ì + ¾î¶² ÀÌ»óÇÑ ºê¶ó¿ìÀú ¹öÀüÀº ½ÇÁ¦ ÆäÀÌÁö°¡ ¾Æ´Ï¶ó ¸®´ÙÀÌ·º¼Ç + ÆäÀÌÁöÀÇ ¹®ÀÚÁýÇÕÀ» »ç¿ëÇÏ·Á°í ÇÑ´Ù. ¿¹¸¦ µé¾î, ±×¸®½º¾î°¡ + ÀÌ»óÇÏ°Ô º¸ÀÏ ¼ö ÀÖ´Ù.

+

ÀÌ È¯°æº¯¼ö´Â ¾ÆÆÄÄ¡°¡ ¸®´ÙÀÌ·º¼Ç ÆäÀÌÁö¿¡ ¹®ÀÚÁýÇÕÀ» + ¼³Á¤ÇÏÁö¾Êµµ·Ï ÇÏ¿©, ÀÌ·± ºê¶ó¿ìÀú°¡ ½ÇÁ¦ ÆäÀÌÁöÀÇ ¹®ÀÚÁýÇÕÀ» + ¿Ã¹Ù·Î »ç¿ëÇÏ°Ô ¸¸µç´Ù.

+ + + +
top
+
+

¿¹Á¦

+ + +

À߸ø µ¿ÀÛÇϴ Ŭ¶óÀ̾ðÆ®µéÀ» À§ÇØ ÇÁ·ÎÅäÄÝ Çൿ + º¯°æÇϱâ

+ + +

Ŭ¶óÀ̾ðÆ®µéÀÇ ÀÌ¹Ì ¾Ë·ÁÁø ¹®Á¦¸¦ ÇØ°áÇϱâÀ§ÇØ + httpd.conf¿¡ ´ÙÀ½ ³»¿ëÀ» Æ÷ÇÔÇÏ±æ ¹Ù¶õ´Ù.

+
+#
+# ´ÙÀ½ Áö½Ã¾îµéÀº ÀϹÝÀûÀÎ HTTP ÀÀ´äÀ» º¯°æÇÑ´Ù.
+# ù¹ø° Áö½Ã¾î´Â Netscape 2.x¿Í À̸¦ °¡ÀåÇÑ ºê¶ó¿ìÀú¿¡°Ô
+# keepalive¸¦ »ç¿ëÇÏÁö ¾Ê´Â´Ù. ÀÌµé ºê¶ó¿ìÀú ±¸Çö¿¡ ¹®Á¦°¡ ÀÖ´Ù.
+# µÎ¹ø° Áö½Ã¾î´Â HTTP/1.1 ±¸ÇöÀÌ À߸øµÇ¾ú°í 301À̳ª 302
+# (¸®´ÙÀÌ·º¼Ç) ÀÀ´ä¿¡ »ç¿ëÇÑ keepalive¸¦ Á¦´ë·Î Áö¿øÇÏÁö
+# ¸øÇÏ´Â Microsoft Internet Explorer 4.0b2¸¦ À§ÇÑ °ÍÀÌ´Ù.
+#
+BrowserMatch "Mozilla/2" nokeepalive
+BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
+
+#
+# ´ÙÀ½ Áö½Ã¾î´Â ±âº»ÀûÀÎ HTTP/1.1 ÀÀ´äÀ» ÀÌÇØÇÏÁö ¸øÇÏ¿©
+# HTTP/1.0 ±Ô¾àÀ» ¾î±â´Â ºê¶ó¿ìÀú¿¡°Ô HTTP/1.1 ÀÀ´äÀ» º¸³»Áö ¾Ê´Â´Ù.
+#
+BrowserMatch "RealPlayer 4\.0" force-response-1.0
+BrowserMatch "Java/1\.0" force-response-1.0
+BrowserMatch "JDK/1\.0" force-response-1.0
+ + +

Á¢±Ù ·Î±×¿¡ À̹ÌÁö¿¡ ´ëÇÑ ¿äûÀ» ·Î±×ÇÏÁö ¾Ê±â

+ + +

ÀÌ ¿¹Á¦´Â À̹ÌÁö¿¡ ´ëÇÑ ¿äûÀ» Á¢±Ù ·Î±×¿¡ ±â·ÏÇÏÁö + ¾Ê´Â´Ù. ƯÁ¤ µð·ºÅ丮¿¡ ´ëÇÑ È¤Àº ƯÁ¤ È£½ºÆ®¿¡¼­ ¿Â + ¿äûÀ» ·Î±×ÇÏÁö ¾Êµµ·Ï ½±°Ô ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ 
+SetEnvIf Request_URI \.gif image-request
+SetEnvIf Request_URI \.jpg image-request
+SetEnvIf Request_URI \.png image-request
+CustomLog logs/access_log common env=!image-request
+ + +

"À̹ÌÁö µµµÏ" ¹æÁö

+ + +

ÀÌ ¿¹´Â ÇöÀç ¼­¹ö¿ÜÀÇ »ç¿ëÀÚ°¡ ÆäÀÌÁö¿¡ ¼­¹ö¿¡ ÀÖ´Â + À̹ÌÁö¸¦ Æ÷ÇÔÇÏÁö ¸øÇϵµ·Ï ÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù. ÀÌ + ¼³Á¤À» ±ÇÀåÇÏÁö´Â ¾ÊÀ¸¸ç, Á¦ÇÑµÈ °æ¿ì¿¡¸¸ µ¿ÀÛÇÑ´Ù. + ¿ì¸®´Â ¸ðµç À̹ÌÁö°¡ /web/images µð·ºÅ丮 ¾È¿¡ ÀÖ´Ù°í + °¡Á¤ÇÑ´Ù.

+ 
+SetEnvIf Referer "^http://www.example.com/" local_referal
+# Referer Á¤º¸¸¦ º¸³»Áö ¾Ê´Â ºê¶ó¿ìÀú¸¦ Çã¿ëÇÑ´Ù
+SetEnvIf Referer "^$" local_referal
+<Directory /web/images>
+   Order Deny,Allow
+   Deny from all
+   Allow from env=local_referal
+</Directory>
+ +

ÀÌ ±â¹ý¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸íÀº ApacheToday ÅõÅ丮¾ó " + Keeping Your Images from Adorning Other Sites"¸¦ Âü°íÇ϶ó.

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/faq/all_in_one.html b/docs/manual/faq/all_in_one.html new file mode 100644 index 00000000..b1ee5968 --- /dev/null +++ b/docs/manual/faq/all_in_one.html @@ -0,0 +1,11 @@ +URI: all_in_one.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: all_in_one.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: all_in_one.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/faq/all_in_one.html.en b/docs/manual/faq/all_in_one.html.en new file mode 100644 index 00000000..8082bcd9 --- /dev/null +++ b/docs/manual/faq/all_in_one.html.en @@ -0,0 +1,287 @@ + + + +Frequently Asked Questions - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > FAQ

Frequently Asked Questions

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

The latest version of this FAQ is always available from the main Apache + web site, at <http://httpd.apache.org/docs/2.2/faq/>.

+ +

If you don't find the answer to your question in the below + sections, please also consult the Apache 1.3 + FAQ to see if your question is answered there.

+
+ +
top
+
+

Topics

+
Background
Background information about the Apache HTTP Server.
+
Support
What do I do when I have problems?
+
Error Messages
What does this error message mean?
+
top
+
+

Background

+ + + +

What is Apache?

+ + +

The Apache Software Foundation (ASF) is a 501(c)3 non-profit + organization providing support for the Apache community of + open-sourced software projects. For more details, please see the Apache Software + Foundation FAQ

+ +

The Apache HTTP Server -- sometimes called Apache httpd -- is + a project of the Apache Software foundation aimed at creating a + robust, commercial-grade, featureful, and freely-available + source code implementation of an HTTP (Web) server. For more + information, please see the About + Apache page.

+ + + +

What is the Apache HTTP Server?

+ +
    +
  • is a powerful, flexible, HTTP/1.1 compliant web server
    • +
  • implements the latest protocols, including HTTP/1.1 (RFC2616)
    • +
  • is highly configurable and extensible with third-party modules
    • +
  • can be customised by writing 'modules' using the Apache module + API
    • +
  • provides full source code and comes with an + unrestrictive + license
    • +
  • runs on Windows 2003/XP/2000/NT/9x, Netware 5.x and above, OS/2, + and most versions of Unix, as well as several other operating + systems
    • +
  • is actively being developed
    • +
  • encourages user feedback through new ideas, bug reports and + patches
    • +
+ + +

How thoroughly tested is Apache?

+ +

Apache is run on millions of Internet servers. + It has been tested thoroughly by both developers and users. The Apache + HTTP Server Project maintains rigorous standards before releasing new + versions of our server, and our server runs without a hitch on over + 70% of all WWW servers available on the Internet. When bugs do show + up, we release patches and new versions as soon as they are + available.

+ + +

+ +

You may NOT use any original artwork from the Apache + Software Foundation, nor make or use modified versions of such + artwork, except under the following conditions:

+
    +
  • You may use the 'Powered by Apache' + graphic on a Web site that is being served by the Apache HTTP + server software.
    • +
  • You may use the aforementioned 'Powered by Apache' + graphic or the Apache Software + Foundation logo in product description and promotional material + IF and ONLY IF such use can in no way be interpreted as + anything other than an attribution. Using the Apache name and + artwork in a manner that implies endorsement of a product or + service is strictly forbidden.
    • +
+ +
top
+
+

Support

+ + +

"Why can't I ...? Why won't ... work?" What to do in case of + problems

+ + +

If you are having trouble with your Apache server software, you should + take the following steps:

+ +
+
Check the ErrorLog!
+
Apache tries to be helpful when it encounters a problem. In many + cases, it will provide some details by writing one or more messages to the + server error log. Sometimes this is enough for you to diagnose & fix + the problem yourself (such as file permissions or the like). The default + location of the error log is + /usr/local/apache2/logs/error_log, but see the ErrorLog directive in your config files for the + location on your server.
+ +
Check the ErrorLog again!
+
Nearly all problems can be solved by reading the error log.
+ +
Check the FAQ!
+
The latest version of the Apache Frequently-Asked Questions list can + always be found at the main Apache web site.
+ +
Check the Apache bug database
+
Most problems that get reported to The Apache Group are recorded in + the bug database. + Please check the existing reports, open + and closed, before adding one. If you find that your + issue has already been reported, please don't add a "me, too" + report. If the original report isn't closed yet, we suggest that you + check it periodically. You might also consider contacting the original + submitter, because there may be an email exchange going on about the + issue that isn't getting recorded in the database.
+ +
Ask in a user support forum
+

Apache has an active community of users who are willing to share + their knowledge. Participating in this community is usually the best and + fastest way to get answers to your questions and problems.

+ +

Users + mailing list

+ +

#apache on + Freenode IRC is also available for + user support issues.

+
+ +
Please use the bug database for bugs!
+

If you've gone through those steps above that are appropriate and + have obtained no relief, then please do let the httpd developers + know about the problem by logging a bug + report.

+ +

If your problem involves the server crashing and generating a core + dump, please + include a backtrace (if possible).

+
+
+ + +

Whom do I contact for support?

+

With millions of users and fewer than sixty volunteer developers, + we cannot provide personal support for Apache. For free support, we + suggest participating in a user forum.

+ +

Professional, commercial support for Apache is available from + a number of + companies.

+ +
top
+
+

Error Messages

+ + +

Invalid argument: + core_output_filter: writing data to the network

+ +

Apache uses the sendfile syscall on platforms + where it is available in order to speed sending of responses. + Unfortunately, on some systems, Apache will detect the presence of + sendfile at compile-time, even when it does not work + properly. This happens most frequently when using network or + other non-standard file-system.

+ +

Symptoms of this problem include the above message in the error + log and zero-length responses to non-zero-sized files. The + problem generally occurs only for static files, since dynamic + content usually does not make use of sendfile.

+ +

To fix this problem, simply use the EnableSendfile directive to disable + sendfile for all or part of your server. Also see + the EnableMMAP, which can + help with similar problems.

+ + + +

AcceptEx Failed

+ +

If you get error messages related to the AcceptEx syscall + on win32, see the Win32DisableAcceptEx + directive.

+ + + +

Premature end of script + headers

+ +

Most problems with CGI scripts result in this message written in the + error log together with an Internal Server Error delivered + to the browser. A guide to helping debug this type of problem is + available in the CGI + tutorial.

+ + +

Permission denied

+ +

A Permission denied error in the + error_log, accompanied by a Forbidden + message to the client usually indicates a problem with your + filesystem permissions, rather than a problem in the Apache HTTP + Server configuration files. Check to make sure that the + User and Group running the child processes + has adequate permission to access the files in question. Also + check that the directory and all parent directories are at least + searchable for that user and group (i.e., chmod + +x).

+ +

Recent releases of Fedora Core and other Linux distributions + using SELinux have additional access restrictions beyond those + used by the basic filesystem. Violations of these restrictions + will also result in a Permission denied message. See + the Fedora + SELinux FAQ and Apache + SELinux Policy Document.

+ + + +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/all_in_one.html.ja.euc-jp b/docs/manual/faq/all_in_one.html.ja.euc-jp new file mode 100644 index 00000000..80a7a409 --- /dev/null +++ b/docs/manual/faq/all_in_one.html.ja.euc-jp @@ -0,0 +1,208 @@ + + + +¤è¤¯¤¢¤ë¼ÁÌä - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > FAQ

¤è¤¯¤¢¤ë¼ÁÌä

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +

Apache ¤Î¼ç¥µ¥¤¥È¡¢<http://httpd.apache.org/docs/2.2/faq/> + ¤«¤éºÇ¿·ÈǤΠFAQ ¤ò¾ï¤Ë¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Apache 2.0 ¤Ï¤Þ¤À¿·¤·¤¤¤Î¤Ç¡¢²¿¤¬¤è¤¯¤¢¤ë¼ÁÌä¤Ê¤Î¤« + ¤Þ¤À¤è¤¯¤ï¤«¤Ã¤Æ¤¤¤Þ¤»¤ó¡£¤³¤Î¥»¥¯¥·¥ç¥ó¤¬Ëä¤Þ¤Ã¤Æ¤¤¤¯¤Þ¤Ç¡¢ + ´û¤Ë¼ÁÌ䤬Åú¤¨¤é¤ì¤Æ¤¤¤ë¤«¤É¤¦¤« Apache 1.3 ¤Î FAQ + ¤â¸«¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+ +
top
+
+

¥È¥Ô¥Ã¥¯

+
¥µ¥Ý¡¼¥È
²¿¤«ÌäÂ꤬µ¯¤³¤Ã¤¿¤È¤­¤Ë¤É¤¦¤¹¤ë?
+
¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸
¤³¤Î¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Î°ÕÌ£¤Ï?
+
top
+
+

¥µ¥Ý¡¼¥È

+ + +

¡Ö¤Ê¤ó¤Ç¡Ä? ¤É¤¦¤·¤ÆÆ°ºî¤·¤Ê¤¤¡Ä?¡×ÌäÂ꤬ + µ¯¤­¤¿¤È¤­¤Ë¤É¤¦¤¹¤ë¤«

+ + +

Apache ¤Î¥µ¡¼¥Ð¥½¥Õ¥È¥¦¥§¥¢¤Ë²¿¤«ÌäÂ꤬µ¯¤³¤Ã¤¿¤È¤­¤Ï¡¢°Ê²¼¤Î + ¼ê½ç¤Ë½¾¤Ã¤Æ¤¯¤À¤µ¤¤:

+ +
+
¥¨¥é¡¼¥í¥°¤òÄ´¤Ù¤ë!
+
ÌäÂ꤬ȯÀ¸¤·¤¿¤È¤­¤Ï Apache ¤Ï¤Ê¤ë¤Ù¤¯¼ê½õ¤±¤ò¤·¤è¤¦¤È¤·¤Þ¤¹¡£ + ¿¤¯¤Î¾ì¹ç¡¢Apache ¤Ï¥µ¡¼¥Ð¤Î¥¨¥é¡¼¥í¥°¤Ë¥á¥Ã¥»¡¼¥¸¤ò½ñ¤¯¤³¤È¤Ç¡¢¾ÜºÙ¤Ê + ¾ðÊó¤òÄ󶡤·¤Þ¤¹¡£¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï¡¢¤³¤ì¤À¤±¤ÇÌäÂê¤ò¼«Ê¬¼«¿È¤ÇʬÀϤ·¡¢ + ½¤Àµ¤¹¤ë¤¿¤á¤Ë½½Ê¬¤Ê¾ðÊó¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹ (¥Õ¥¡¥¤¥ë¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤Î + ÌäÂê¤Ê¤É)¡£¥¨¥é¡¼¥í¥°¤Î¥Ç¥Õ¥©¥ë¥È¤Î¾ì½ê¤Ï + /usr/local/apache2/logs/error_log ¤Ç¤¹¤¬¡¢¤¢¤Ê¤¿¤Î¥µ¡¼¥Ð + ¤Ç¤Î¾ì½ê¤òÃΤ뤿¤á¤Ë¤ÏÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î ErrorLog ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
+ +
FAQ ¤òÄ´¤Ù¤ë!
+
Apache ¤Î¤è¤¯¤¢¤ë¼ÁÌä¤ÎºÇ¿·ÈǤϾï¤Ë Apache ¤Î¼ç¥¦¥§¥Ö¥µ¥¤¥È¤Ë + ¤¢¤ê¤Þ¤¹¡£
+ +
Apache ¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÄ´¤Ù¤ë
+
Apache ¥°¥ë¡¼¥×¤ËÊó¹ð¤µ¤ì¤ë¤Û¤È¤ó¤É¤ÎÌäÂê¤Ï¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë + µ­Ï¿¤µ¤ì¤Þ¤¹¡£Open ¤â closed ¤â ´Þ¤á¤Æ¡¢ + ´û¸¤Î¥ì¥Ý¡¼¥È¤Ë¤¢¤ë¤«¤É¤¦¤«¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£ + ´û¤ËÌäÂ꤬Êó¹ð¤µ¤ì¤Æ¤¤¤ë¤È¤­¡¢¡Ö»ä¤â¡×¤È¤¤¤¦Êó¹ð¤ÏÄɲ䷤ʤ¤¤Ç + ¤¯¤À¤µ¤¤¡£¸µ¤ÎÊó¹ð¤¬ close ¤µ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ï¡¢Äê´üŪ¤Ë + ¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÄ´¤Ù¤ë¤³¤È¤ò¤ªÁ¦¤á¤·¤Þ¤¹¡£¤Þ¤¿¡¢¸µ¤ÎÄó½Ð¼Ô¤Ë + Ï¢Íí¤ò¼è¤ë¤³¤È¤â¹Íθ¤ËÆþ¤ì¤Æ¤ª¤¯¤È¤è¤¤¤Ç¤·¤ç¤¦¡£¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë + µ­Ï¿¤µ¤ì¤Æ¤¤¤Ê¤¤ÅŻҥ᡼¥ë¤Î¸ò´¹¤¬¹Ô¤Ê¤ï¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
+ +
¥æ¡¼¥¶¥µ¥Ý¡¼¥È¥Õ¥©¡¼¥é¥à¤Ç¼ÁÌ䤹¤ë
+

Apache ¤Ë¤Ï¤è¤í¤³¤ó¤ÇÃ챤ò¶¦Í­¤µ¤»¤Æ¤¯¤ì¤ë³èȯ¤Ê + ¥æ¡¼¥¶¤Î¥³¥ß¥å¥Ë¥Æ¥£¤¬¤¢¤ê¤Þ¤¹¡£¤³¤Î¥³¥ß¥å¥Ë¥Æ¥£¤Ë»²²Ã¤¹¤ë¤³¤È¤¬¡¢ + ÉáÄ̤ϼÁÌä¤äÌäÂê¤ËÂФ¹¤ë²óÅú¤òÆÀ¤ëºÇÁ±¤ÇºÇ®¤Î¼êÃʤǤ¹¡£

+ +

¥æ¡¼¥¶ + ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È

+ +

USENET ¥Ë¥å¡¼¥¹¥°¥ë¡¼¥×:

+ +
+ +
¤â¤·¡¢Á´Éô¼ºÇÔ¤·¤¿¾ì¹ç¤Ï¡¢ÌäÂê¤ò¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÊó¹ð¤·¤Æ¤¯¤À¤µ¤¤
+

¾åµ­¤Î¼êÃʤÎÃæ¤Ç³ºÅö¤¹¤ë¤â¤Î¤ò¤ò¤¹¤Ù¤Æ¼è¤Ã¤Æ¡¢ + ¤½¤ì¤Ç¤âÌäÂê¤Î²ò·èºö¤òÆÀ¤é¤ì¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï¡¢¥Ð¥°¤ÎÊó¹ð¤ò + ¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢ÌäÂê¤ò¤¼¤Ò httpd ³«È¯¼Ô¤ËÃΤ餻¤Æ¤¯¤À¤µ¤¤¡£

+ +

¥µ¡¼¥Ð¤Î¥¯¥é¥Ã¥·¥å¤ä¥³¥¢¥À¥ó¥×¤ÎȯÀ¸¤¹¤ëÌäÂê¤Ç¤¢¤ì¤Ð¡¢(²Äǽ¤Ç¤¢¤ì¤Ð) + ¥Ð¥Ã¥¯¥È¥ì¡¼¥¹¤òÊó¹ð¤Ë´Þ¤á¤Æ¤¯¤À¤µ¤¤¡£Î㤨¤Ð¡¢

+ +

+ # cd ServerRoot
+ # dbx httpd core
+ (dbx) where +

+ +

(ServerRoot ¤È httpd ¤È core ¥Õ¥¡¥¤¥ë + ¤Î°ÌÃÖ¤òŬÀڤʤâ¤Î¤ËÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£dbx ¤ÎÂå¤ï¤ê¤Ë + gdb ¤ò»È¤¦É¬Íפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£)

+
+
+ + +

ï¤Ë¥µ¥Ý¡¼¥È¤òÍê¤á¤Ð¤è¤¤?

+

¿ôÉ´Ëü¤Î¥æ¡¼¥¶¤ËÂФ·¤Æ¡¢40̤Ëþ¤Î¥Ü¥é¥ó¥Æ¥£¥¢³«È¯¼Ô¤·¤«¤¤¤Ê¤¤¤¿¤á¡¢ + Apache ¤Î¸Ä¿ÍŪ¤Ê¥µ¥Ý¡¼¥È¤òÄ󶡤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ÌµÎÁ¤Î + ¥µ¥Ý¡¼¥È¤Ë¤Ï¡¢¥æ¡¼¥¶¤Î¥Õ¥©¡¼¥é¥à¤Ë»²²Ã¤¹¤ë¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+ +

Apache ¤Î¥×¥í¤Î¡¢¾¦ÍÑ¥µ¥Ý¡¼¥È¤â + ¿¤¯¤Î²ñ¼Ò + ¤«¤éÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +
top
+
+

¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸

+ + +

Invalid argument: + core_output_filter: writing data to the network

+ +

(ÌõÃí: ̵¸ú¤Ê°ú¿ô: core_output_filter: ¥Í¥Ã¥È¥ï¡¼¥¯¤Ø¤Î¥Ç¡¼¥¿¤Î + ½ñ¤­¹þ¤ß)

+ +

Apache ¤Ï±þÅú¤ÎÊÖÁ÷¤ò®¤¯¤¹¤ë¤¿¤á¤Ë¡¢sendfile ¥·¥¹¥Æ¥à + ¥³¡¼¥ë¤¬»ÈÍѲÄǽ¤Ê¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¤Ï¤½¤Î¥·¥¹¥Æ¥à¥³¡¼¥ë¤ò»ÈÍѤ·¤Þ¤¹¡£ + ¤È¤³¤í¤¬¡¢ÅÔ¹ç¤Î°­¤¤¤³¤È¤Ë¡¢sendfile ¤¬Àµ¤·¤¯Æ°ºî¤·¤Ê¤¤¤Ë¤â + ´Ø¤ï¤é¤º¡¢Apache ¤¬¥³¥ó¥Ñ¥¤¥ë»þ¤Ë¸ºß¤ò¸¡ÃΤ·¤Æ¤·¤Þ¤¦¥·¥¹¥Æ¥à¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥Í¥Ã¥È¥ï¡¼¥¯¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ä¾¤ÎÈóɸ½à¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò + »ÈÍѤ·¤Æ¤¤¤ë¤È¤­¤Ë°ìÈ֤褯ȯÀ¸¤·¤Þ¤¹¡£

+ +

¤³¤ÎÌäÂê¤Î¾É¾õ¤Ï¡¢¾åµ­¤Î¥á¥Ã¥»¡¼¥¸¤¬¥¨¥é¡¼¥í¥°¤Ë½ñ¤«¤ì¤ë¤³¤È¤È¡¢ + ¥µ¥¤¥º¤¬¥¼¥í¤Ç¤Ê¤¤¥Õ¥¡¥¤¥ë¤Î±þÅú¤¬¥¼¥í¤Ë¤Ê¤ë¤³¤È¤Ç¤¹¡£ + ưŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤Ï sendfile ¤òÍøÍѤ·¤Ê¤¤¤¿¤á¡¢ + ¤³¤ÎÌäÂê¤ÏÄ̾ï¤ÏÀÅŪ¤Ê¥Õ¥¡¥¤¥ë¤Ç¤Î¤ßȯÀ¸¤·¤Þ¤¹¡£

+ +

¤³¤ÎÌäÂê¤Ï¡¢EnableSendfile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¡¢ + ¥µ¡¼¥Ð¤Î¤¹¤Ù¤Æ¡¢¤â¤·¤¯¤Ï°ìÉôʬ¤ËÂФ·¤Æ sendfile ¤ò + ̵¸ú¤Ë¤¹¤ë¤À¤±¤Ç½¤Àµ¤Ç¤­¤Þ¤¹¡£Æ±ÍͤÎÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Î + EnableMMAP ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤â + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ + + +

AcceptEx Failed

+ +

(ÌõÃí: AcceptEx ¼ºÇÔ)

+ +

Win32 ¤Ç¤Î AcceptEx ¥·¥¹¥Æ¥à¥³¡¼¥ë¤Ë´Ø·¸¤¹¤ë¥¨¥é¡¼ + ¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¼è¤Ã¤¿¤È¤­¤Ï¡¢Win32DisableAcceptEx ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ + + +

Premature end of script + headers

+ +

(ÌõÃí: ¥¹¥¯¥ê¥×¥È¥Ø¥Ã¥À¤ÎÃæÅÓ½ªÎ»)

+ +

CGI ¥¹¥¯¥ê¥×¥È¤Î¤Û¤È¤ó¤É¤ÎÌäÂê¤Ï¥¨¥é¡¼¥í¥°¤Ë¤³¤Î¥á¥Ã¥»¡¼¥¸¤¬½ñ¤«¤ì¡¢ + ¥Ö¥é¥¦¥¶¤Ë¤Ï Internal Server Error ¤¬Á÷¤é¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤Î¼ï¤ÎÌäÂê¤Î¥Ç¥Ð¥Ã¥°ÊýË¡¤Ï CGI + ¥Á¥å¡¼¥È¥ê¥¢¥ë ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ + +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/all_in_one.html.ko.euc-kr b/docs/manual/faq/all_in_one.html.ko.euc-kr new file mode 100644 index 00000000..151d6e6c --- /dev/null +++ b/docs/manual/faq/all_in_one.html.ko.euc-kr @@ -0,0 +1,209 @@ + + + +ÀÚÁÖ ¹°¾îº¸´Â Áú¹® (FAQ) - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > FAQ

ÀÚÁÖ ¹°¾îº¸´Â Áú¹® (FAQ)

+
+

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

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

FAQ ÃÖ½ÅÆÇÀº ¾ÆÆÄÄ¡ À¥»çÀÌÆ® <http://httpd.apache.org/docs/2.2/faq/>¿¡¼­ º¼ ¼ö + ÀÖ´Ù.

+ +

¾ÆÆÄÄ¡ 2.0ÀÌ ³ª¿ÂÁö ¾ó¸¶ ¾ÈµÇ¼­ ¿ì¸®´Â ¾ÆÁ÷ ÀÚÁÖ + ¹°¾îº¸´Â Áú¹® (FAQ)ÀÌ ¹«¾ùÀÎÁö ¸ð¸¥´Ù. ³»¿ëÀÌ Ã¤¿öÁú + ¶§±îÁö ¿©±â¿¡ ÇØ´äÀÌ ¾ø´Ù¸é ¾ÆÆÄÄ¡ + 1.3 FAQµµ Âü°íÇ϶ó.

+
+ +
top
+
+

ÁÖÁ¦

+
Áö¿ø
¹®Á¦°¡ »ý±â¸é ¾î¶»°Ô ÇØ°áÇϳª?
+
¿À·ù¹®
ÀÌ ¿À·ù¹®ÀÌ ¹«½¼ ¶æÀΰ¡?
+
top
+
+

Áö¿ø

+ + +

"¿Ö ... ¾ÈµÇ³ª? ¿Ö ... µ¿ÀÛÇÏÁö ¾Ê´Â°¡?" ¹®Á¦°¡ »ý±â¸é + ÇÒÀÏ

+ + +

¾ÆÆÄÄ¡ ¼­¹ö ¼ÒÇÁÆ®¿þ¾î¿¡ ¹®Á¦°¡ »ý±â¸é ´ÙÀ½°ú °°Àº + ´Ü°è¸¦ µû¸¥´Ù:

+ +
+
¿À·ù ·Î±×(errorlog)¸¦ È®ÀÎÇ϶ó!
+
¾ÆÆÄÄ¡ ¼­¹ö´Â ¹®Á¦°¡ »ý±â¸é µµ¿òÀ» ÁÖ·Á°í ³ë·ÂÇÑ´Ù. + ¸¹Àº °æ¿ì ¼­¹ö ¿À·ù ·Î±×¿¡ ÀÚ¼¼ÇÑ ³»¿ëÀ» ±â·ÏÇÑ´Ù. + À̰͸¸À¸·Îµµ Á÷Á¢ (ÆÄÀϱÇÇÑ µî) ¹®Á¦¸¦ ¹ß°ßÇÏ°í °íÄ¥ ¼ö + ÀÖ´Â °æ¿ì°¡ ¸¹´Ù. ¿À·ù ·Î±×ÀÇ ±âº» À§Ä¡´Â + /usr/local/apache2/logs/error_logÀÌÁö¸¸, + Á¤È®ÇÑ À§Ä¡´Â ¼³Á¤ÆÄÀÏÀÇ ErrorLog Áö½Ã¾î¸¦ Âü°íÇ϶ó.
+ +
FAQ¸¦ + È®ÀÎÇ϶ó!
+
¾ÆÆÄÄ¡ À¥»çÀÌÆ®¿¡¼­ Ç×»ó ¾ÆÆÄÄ¡ FAQ ÃÖ½ÅÆÇÀ» º¼ ¼ö + ÀÖ´Ù.
+ +
¾ÆÆÄÄ¡ ¹ö±× µ¥ÀÌÅͺ£À̽º¸¦ È®ÀÎÇ϶ó
+
¾ÆÆÄÄ¡±×·ì(The Apache Group)¿¡ º¸°íµÈ ´ëºÎºÐÀÇ ¹®Á¦´Â + ¹ö±× + µ¥ÀÌÅͺ£À̽º¿¡ ±â·ÏµÈ´Ù. »õ·Î ¹ö±×¸¦ Ãß°¡Çϱâ Àü¿¡, + ÀÌ¹Ì ¾Ë·ÁÁ³°Å³ª(open) ÇØ°áµÈ(closed) ¹ö±×°¡ ÀÖ´ÂÁö È®ÀÎÇϱæ + ¹Ù¶õ´Ù. ÀÌ¹Ì ¹®Á¦°¡ º¸°íµÇ¾ú´Ù¸é "³ªµµ + ÀÌ·± ¹®Á¦°¡ ÀÖ´Ù°í" º¸°íÇÏÁö ¾Ê±æ ¹Ù¶õ´Ù. ¾ÆÁ÷ + ÇØ°áµÇÁö ¾Ê¾Ò´Ù¸é ÁÖ±âÀûÀ¸·Î »óȲÀ» È®ÀÎÇÏ±æ ¹Ù¶õ´Ù. ¶Ç, + µ¥ÀÌÅͺ£À̽º¿¡ ±â·ÏµÇÁö ¾Ê°í À̸ÞÀÏ ±³È¯À¸·Î ÁøÇàµÈ »çÇ×ÀÌ + ÀÖÀ» ¼ö ÀÖÀ¸´Ï óÀ½ ¹®Á¦¸¦ º¸°íÇÑ »ç¶÷¿¡°Ô ¿¬¶ôÇغ¼ ¼öµµ + ÀÖ´Ù.
+ +
»ç¿ëÀÚ Áö¿ø °ø°£¿¡ + ¹®ÀÇÇÑ´Ù
+

¾ÆÆÄÄ¡¿¡ ´ëÇÑ Áö½ÄÀ» °øÀ¯ÇÏ±æ ¿øÇÏ´Â È°¹ßÇÑ »ç¿ëÀÚ + °øµ¿Ã¼µéÀÌ ÀÖ´Ù. ÀϹÝÀûÀ¸·Î ÀÌ·± °øµ¿Ã¼¿¡ Âü¿©ÇÏ´Â °ÍÀÌ + ¹®Á¦ÀÇ ´äÀ» ¾ò´Â °¡Àå ÁÁ°í ºü¸¥ ¹æ¹ýÀÌ´Ù.

+ +

»ç¿ëÀÚ + ¸ÞÀϸµ¸®½ºÆ®

+ +

USENET ´º½º±×·ì:

+ +
    +
  • comp.infosystems.www.servers.unix + [news] + [google] +
    • + +
  • comp.infosystems.www.servers.ms-windows + [news] + [google] +
    • + +
  • comp.infosystems.www.authoring.cgi + [news] + [google] +
    • +
+ +
À§ÀÇ ¹æ¹ýÀÌ ¸ðµÎ ½ÇÆÐÇÏ¸é ¹ö±× µ¥ÀÌÅͺ£À̽º¿¡ ¹®Á¦¸¦ + º¸°íÇÑ´Ù
+

À§ÀÇ ´Ü°è¸¦ ¸ðµÎ ½ÃµµÇÏ°íµµ ÇØ°áÃ¥ÀÌ ¾ø´Ù¸é, ¹ö±×¸¦ + º¸°íÇÏ¿© À¥¼­¹ö °³¹ßÀڵ鿡°Ô ¹®Á¦¸¦ ¾Ë¸®±æ + ¹Ù¶õ´Ù.

+ +

core dump¸¦ ¸¸µé¸ç ¼­¹ö°¡ Á×´Â °æ¿ì¶ó¸é (°¡´ÉÇϸé) + backtrace(¿ªÁÖ; ¹®Á¦°¡ ½ÇÇàÆÄÀÏÀÇ Á¤È®È÷ ¾î¶² ÁöÁ¡¿¡¼­ + ¹ß»ýÇÏ¿´°í, ÇÁ·Î±×·¥ÀÌ ±× ÁöÁ¡±îÁö ¾î¶² °æ·Î·Î ½ÇÇàµÇ¾ú´ÂÁö¸¦ + ¾Ë·ÁÁÖ´Â Á¤º¸)¸¦ Æ÷ÇÔÇÏ±æ ¹Ù¶õ´Ù. ¿¹¸¦ µé¾î,

+ +

+ # cd ServerRoot
+ # dbx httpd core
+ (dbx) where +

+ +

(ServerRoot, httpd, core + ÆÄÀÏÀÇ ½ÇÁ¦ À§Ä¡¸¦ ´ë½Å »ç¿ëÇ϶ó. dbx ´ë½Å + gdb¸¦ »ç¿ëÇØ¾ß ÇÒ ¼öµµ ÀÖ´Ù.)

+
+
+ + +

µµ¿òÀ» ¾òÀ¸·Á¸é ´©±¸¿¡°Ô + ¿¬¶ôÇϳª?

+

40¸í °¡·®ÀÇ ÀÚ¹ßÀûÀ¸·Î Âü¿©ÇÑ °³¹ßÀÚ¸¸À¸·Î´Â ¼ö¹é¸¸ÀÇ + »ç¿ëÀÚ¿¡°Ô ¾ÆÆÄÄ¡¿¡ ´ëÇØ ÀÏÀÏÀÌ Áö¿øÇÒ ¼ö ¾ø´Ù. ¹«·á Áö¿øÀ» + ¾òÀ¸·Á¸é »ç¿ëÀÚ + °ø°£¿¡ Âü¿©ÇÏ±æ ±ÇÇÑ´Ù.

+ +

¾ÆÆÄÄ¡¿¡ ´ëÇÑ Á÷¾÷ÀûÀÎ À¯·á Áö¿øÀº ¿©·¯ + ȸ»ç¿¡¼­ Á¦°øÇÑ´Ù.

+ +
top
+
+

¿À·ù¹®

+ + +

Invalid argument: + core_output_filter: writing data to the network

+ +

Ç÷¡ÆûÀÌ sendfile ½Ã½ºÅÛÈ£ÃâÀ» Áö¿øÇÑ´Ù¸é, + ¾ÆÆÄÄ¡´Â ÀÀ´äÀÇ ¼Óµµ¸¦ ºü¸£°ÔÇϱâÀ§ÇØ ÀÌ ½Ã½ºÅÛÈ£ÃâÀ» »ç¿ëÇÑ´Ù. + ºÒÇàÈ÷µµ ¾î¶² ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡´Â ÄÄÆÄÀÏÇÒ¶§ + sendfileÀÌ Á¤»óÀûÀ¸·Î ÀÛµ¿ÇÏÁö ¾Ê´Âµ¥µµ Á¤»óÀûÀ¸·Î + ÀÛµ¿ÇÑ´Ù°í ¿ÀÆÇÇÑ´Ù. ÀÌ ¹®Á¦´Â ³×Æ®¿÷ ÆÄÀϽýºÅÛÀ̳ª ºñÇ¥ÁØ + ÆÄÀϽýºÅÛÀ» »ç¿ëÇÒ¶§ ÀÚÁÖ ¹ß»ýÇÑ´Ù.

+ +

ÀÌ ¹®Á¦ÀÇ Áõ»óÀº ¿À·ù ·Î±×(error log)¿¡ À§ÀÇ ¹®±¸¸¦ + ±â·ÏÇϰųª Å©±â°¡ 0ÀÌ ¾Æ´Ñ ÆÄÀÏ¿¡ ´ëÇØ Å©±â°¡ 0ÀÎ ÀÀ´äÀ» + ÇÏ´Â °æ¿ìÀÌ´Ù. µ¿ÀûÀ¸·Î ³»¿ëÀ» »ý¼ºÇÒ¶§´Â + sendfileÀ» »ç¿ëÇÏÁö ¾Ê±â¶§¹®¿¡ ÀϹÝÀûÀ¸·Î Á¤ÀûÀÎ + ÆÄÀÏÀ» ¿äûÇÒ¶§¸¸ ¹®Á¦°¡ ¹ß»ýÇÑ´Ù.

+ +

¹®Á¦¸¦ ÇØ°áÇÏ·Á¸é ¼­¹ö°¡ sendfileÀ» »ç¿ëÇÏÁö + ¾Êµµ·Ï EnableSendfile + Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. ¶Ç, ÀÌ¿Í À¯»çÇÑ ¹®Á¦¿¡ ´ëÇØ EnableMMAPÀ» Âü°íÇ϶ó.

+ + + +

AcceptEx Failed

+ +

win32¿¡¼­ AcceptEx ½Ã½ºÅÛÈ£Ãâ¿¡ ´ëÇÑ ¿À·ù¹®À» + ³ª¿À¸é, Win32DisableAcceptEx + Áö½Ã¾î¸¦ Âü°íÇ϶ó.

+ + + +

Premature end of script + headers

+ +

º¸Åë CGI ½ºÅ©¸³Æ®¿¡ ¹®Á¦°¡ ÀÖÀ¸¸é ºê¶ó¿ìÀú¿¡°Ô Internal + Server Error¸¦ º¸³»°í ¿À·ù·Î±×¿¡ ÀÌ ¹®±¸¸¦ ±â·ÏÇÑ´Ù. + ÀÌ·± ¹®Á¦¸¦ µð¹ö±ëÇÒ¶§ CGI ÅõÅ丮¾óÀÌ + µµ¿òÀÌ µÉ ¼ö ÀÖ´Ù.

+ + +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/faq/background.html b/docs/manual/faq/background.html new file mode 100644 index 00000000..66283baa --- /dev/null +++ b/docs/manual/faq/background.html @@ -0,0 +1,3 @@ +URI: background.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/faq/background.html.en b/docs/manual/faq/background.html.en new file mode 100644 index 00000000..58652966 --- /dev/null +++ b/docs/manual/faq/background.html.en @@ -0,0 +1,110 @@ + + + +Background - Frequently Asked Questions - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > FAQ

Background - Frequently Asked Questions

+
+

Available Languages:  en 

+
+
+
top
+
+

Background

+ + + +

What is Apache?

+ + +

The Apache Software Foundation (ASF) is a 501(c)3 non-profit + organization providing support for the Apache community of + open-sourced software projects. For more details, please see the Apache Software + Foundation FAQ

+ +

The Apache HTTP Server -- sometimes called Apache httpd -- is + a project of the Apache Software foundation aimed at creating a + robust, commercial-grade, featureful, and freely-available + source code implementation of an HTTP (Web) server. For more + information, please see the About + Apache page.

+ + + +

What is the Apache HTTP Server?

+ +
    +
  • is a powerful, flexible, HTTP/1.1 compliant web server
    • +
  • implements the latest protocols, including HTTP/1.1 (RFC2616)
    • +
  • is highly configurable and extensible with third-party modules
    • +
  • can be customised by writing 'modules' using the Apache module + API
    • +
  • provides full source code and comes with an + unrestrictive + license
    • +
  • runs on Windows 2003/XP/2000/NT/9x, Netware 5.x and above, OS/2, + and most versions of Unix, as well as several other operating + systems
    • +
  • is actively being developed
    • +
  • encourages user feedback through new ideas, bug reports and + patches
    • +
+ + +

How thoroughly tested is Apache?

+ +

Apache is run on millions of Internet servers. + It has been tested thoroughly by both developers and users. The Apache + HTTP Server Project maintains rigorous standards before releasing new + versions of our server, and our server runs without a hitch on over + 70% of all WWW servers available on the Internet. When bugs do show + up, we release patches and new versions as soon as they are + available.

+ + +

+ +

You may NOT use any original artwork from the Apache + Software Foundation, nor make or use modified versions of such + artwork, except under the following conditions:

+
    +
  • You may use the 'Powered by Apache' + graphic on a Web site that is being served by the Apache HTTP + server software.
    • +
  • You may use the aforementioned 'Powered by Apache' + graphic or the Apache Software + Foundation logo in product description and promotional material + IF and ONLY IF such use can in no way be interpreted as + anything other than an attribution. Using the Apache name and + artwork in a manner that implies endorsement of a product or + service is strictly forbidden.
    • +
+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/error.html b/docs/manual/faq/error.html new file mode 100644 index 00000000..7bbf1a05 --- /dev/null +++ b/docs/manual/faq/error.html @@ -0,0 +1,11 @@ +URI: error.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: error.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: error.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/faq/error.html.en b/docs/manual/faq/error.html.en new file mode 100644 index 00000000..0ffc42ff --- /dev/null +++ b/docs/manual/faq/error.html.en @@ -0,0 +1,109 @@ + + + +Error Messages - Frequently Asked Questions - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > FAQ

Error Messages - Frequently Asked Questions

+
+

Available Languages:  en  | + ja  | + ko 

+
+
+
top
+
+

Error Messages

+ + +

Invalid argument: + core_output_filter: writing data to the network

+ +

Apache uses the sendfile syscall on platforms + where it is available in order to speed sending of responses. + Unfortunately, on some systems, Apache will detect the presence of + sendfile at compile-time, even when it does not work + properly. This happens most frequently when using network or + other non-standard file-system.

+ +

Symptoms of this problem include the above message in the error + log and zero-length responses to non-zero-sized files. The + problem generally occurs only for static files, since dynamic + content usually does not make use of sendfile.

+ +

To fix this problem, simply use the EnableSendfile directive to disable + sendfile for all or part of your server. Also see + the EnableMMAP, which can + help with similar problems.

+ + + +

AcceptEx Failed

+ +

If you get error messages related to the AcceptEx syscall + on win32, see the Win32DisableAcceptEx + directive.

+ + + +

Premature end of script + headers

+ +

Most problems with CGI scripts result in this message written in the + error log together with an Internal Server Error delivered + to the browser. A guide to helping debug this type of problem is + available in the CGI + tutorial.

+ + +

Permission denied

+ +

A Permission denied error in the + error_log, accompanied by a Forbidden + message to the client usually indicates a problem with your + filesystem permissions, rather than a problem in the Apache HTTP + Server configuration files. Check to make sure that the + User and Group running the child processes + has adequate permission to access the files in question. Also + check that the directory and all parent directories are at least + searchable for that user and group (i.e., chmod + +x).

+ +

Recent releases of Fedora Core and other Linux distributions + using SELinux have additional access restrictions beyond those + used by the basic filesystem. Violations of these restrictions + will also result in a Permission denied message. See + the Fedora + SELinux FAQ and Apache + SELinux Policy Document.

+ + + +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/error.html.ja.euc-jp b/docs/manual/faq/error.html.ja.euc-jp new file mode 100644 index 00000000..0cfa341e --- /dev/null +++ b/docs/manual/faq/error.html.ja.euc-jp @@ -0,0 +1,93 @@ + + + +¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸ ¡½ ¤è¤¯¤¢¤ë¼ÁÌä - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > FAQ

¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸ ¡½ ¤è¤¯¤¢¤ë¼ÁÌä

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+
+
top
+
+

¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸

+ + +

Invalid argument: + core_output_filter: writing data to the network

+ +

(ÌõÃí: ̵¸ú¤Ê°ú¿ô: core_output_filter: ¥Í¥Ã¥È¥ï¡¼¥¯¤Ø¤Î¥Ç¡¼¥¿¤Î + ½ñ¤­¹þ¤ß)

+ +

Apache ¤Ï±þÅú¤ÎÊÖÁ÷¤ò®¤¯¤¹¤ë¤¿¤á¤Ë¡¢sendfile ¥·¥¹¥Æ¥à + ¥³¡¼¥ë¤¬»ÈÍѲÄǽ¤Ê¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¤Ï¤½¤Î¥·¥¹¥Æ¥à¥³¡¼¥ë¤ò»ÈÍѤ·¤Þ¤¹¡£ + ¤È¤³¤í¤¬¡¢ÅÔ¹ç¤Î°­¤¤¤³¤È¤Ë¡¢sendfile ¤¬Àµ¤·¤¯Æ°ºî¤·¤Ê¤¤¤Ë¤â + ´Ø¤ï¤é¤º¡¢Apache ¤¬¥³¥ó¥Ñ¥¤¥ë»þ¤Ë¸ºß¤ò¸¡ÃΤ·¤Æ¤·¤Þ¤¦¥·¥¹¥Æ¥à¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥Í¥Ã¥È¥ï¡¼¥¯¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ä¾¤ÎÈóɸ½à¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò + »ÈÍѤ·¤Æ¤¤¤ë¤È¤­¤Ë°ìÈ֤褯ȯÀ¸¤·¤Þ¤¹¡£

+ +

¤³¤ÎÌäÂê¤Î¾É¾õ¤Ï¡¢¾åµ­¤Î¥á¥Ã¥»¡¼¥¸¤¬¥¨¥é¡¼¥í¥°¤Ë½ñ¤«¤ì¤ë¤³¤È¤È¡¢ + ¥µ¥¤¥º¤¬¥¼¥í¤Ç¤Ê¤¤¥Õ¥¡¥¤¥ë¤Î±þÅú¤¬¥¼¥í¤Ë¤Ê¤ë¤³¤È¤Ç¤¹¡£ + ưŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤Ï sendfile ¤òÍøÍѤ·¤Ê¤¤¤¿¤á¡¢ + ¤³¤ÎÌäÂê¤ÏÄ̾ï¤ÏÀÅŪ¤Ê¥Õ¥¡¥¤¥ë¤Ç¤Î¤ßȯÀ¸¤·¤Þ¤¹¡£

+ +

¤³¤ÎÌäÂê¤Ï¡¢EnableSendfile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¡¢ + ¥µ¡¼¥Ð¤Î¤¹¤Ù¤Æ¡¢¤â¤·¤¯¤Ï°ìÉôʬ¤ËÂФ·¤Æ sendfile ¤ò + ̵¸ú¤Ë¤¹¤ë¤À¤±¤Ç½¤Àµ¤Ç¤­¤Þ¤¹¡£Æ±ÍͤÎÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Î + EnableMMAP ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤â + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ + + +

AcceptEx Failed

+ +

(ÌõÃí: AcceptEx ¼ºÇÔ)

+ +

Win32 ¤Ç¤Î AcceptEx ¥·¥¹¥Æ¥à¥³¡¼¥ë¤Ë´Ø·¸¤¹¤ë¥¨¥é¡¼ + ¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¼è¤Ã¤¿¤È¤­¤Ï¡¢Win32DisableAcceptEx ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ + + +

Premature end of script + headers

+ +

(ÌõÃí: ¥¹¥¯¥ê¥×¥È¥Ø¥Ã¥À¤ÎÃæÅÓ½ªÎ»)

+ +

CGI ¥¹¥¯¥ê¥×¥È¤Î¤Û¤È¤ó¤É¤ÎÌäÂê¤Ï¥¨¥é¡¼¥í¥°¤Ë¤³¤Î¥á¥Ã¥»¡¼¥¸¤¬½ñ¤«¤ì¡¢ + ¥Ö¥é¥¦¥¶¤Ë¤Ï Internal Server Error ¤¬Á÷¤é¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤Î¼ï¤ÎÌäÂê¤Î¥Ç¥Ð¥Ã¥°ÊýË¡¤Ï CGI + ¥Á¥å¡¼¥È¥ê¥¢¥ë ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ + +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/error.html.ko.euc-kr b/docs/manual/faq/error.html.ko.euc-kr new file mode 100644 index 00000000..f3e7a626 --- /dev/null +++ b/docs/manual/faq/error.html.ko.euc-kr @@ -0,0 +1,86 @@ + + + +¿À·ù¹® - ÀÚÁÖ ¹°¾îº¸´Â Áú¹® (FAQ) - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > FAQ

¿À·ù¹® - ÀÚÁÖ ¹°¾îº¸´Â Áú¹® (FAQ)

+
+

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

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

¿À·ù¹®

+ + +

Invalid argument: + core_output_filter: writing data to the network

+ +

Ç÷¡ÆûÀÌ sendfile ½Ã½ºÅÛÈ£ÃâÀ» Áö¿øÇÑ´Ù¸é, + ¾ÆÆÄÄ¡´Â ÀÀ´äÀÇ ¼Óµµ¸¦ ºü¸£°ÔÇϱâÀ§ÇØ ÀÌ ½Ã½ºÅÛÈ£ÃâÀ» »ç¿ëÇÑ´Ù. + ºÒÇàÈ÷µµ ¾î¶² ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡´Â ÄÄÆÄÀÏÇÒ¶§ + sendfileÀÌ Á¤»óÀûÀ¸·Î ÀÛµ¿ÇÏÁö ¾Ê´Âµ¥µµ Á¤»óÀûÀ¸·Î + ÀÛµ¿ÇÑ´Ù°í ¿ÀÆÇÇÑ´Ù. ÀÌ ¹®Á¦´Â ³×Æ®¿÷ ÆÄÀϽýºÅÛÀ̳ª ºñÇ¥ÁØ + ÆÄÀϽýºÅÛÀ» »ç¿ëÇÒ¶§ ÀÚÁÖ ¹ß»ýÇÑ´Ù.

+ +

ÀÌ ¹®Á¦ÀÇ Áõ»óÀº ¿À·ù ·Î±×(error log)¿¡ À§ÀÇ ¹®±¸¸¦ + ±â·ÏÇϰųª Å©±â°¡ 0ÀÌ ¾Æ´Ñ ÆÄÀÏ¿¡ ´ëÇØ Å©±â°¡ 0ÀÎ ÀÀ´äÀ» + ÇÏ´Â °æ¿ìÀÌ´Ù. µ¿ÀûÀ¸·Î ³»¿ëÀ» »ý¼ºÇÒ¶§´Â + sendfileÀ» »ç¿ëÇÏÁö ¾Ê±â¶§¹®¿¡ ÀϹÝÀûÀ¸·Î Á¤ÀûÀÎ + ÆÄÀÏÀ» ¿äûÇÒ¶§¸¸ ¹®Á¦°¡ ¹ß»ýÇÑ´Ù.

+ +

¹®Á¦¸¦ ÇØ°áÇÏ·Á¸é ¼­¹ö°¡ sendfileÀ» »ç¿ëÇÏÁö + ¾Êµµ·Ï EnableSendfile + Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. ¶Ç, ÀÌ¿Í À¯»çÇÑ ¹®Á¦¿¡ ´ëÇØ EnableMMAPÀ» Âü°íÇ϶ó.

+ + + +

AcceptEx Failed

+ +

win32¿¡¼­ AcceptEx ½Ã½ºÅÛÈ£Ãâ¿¡ ´ëÇÑ ¿À·ù¹®À» + ³ª¿À¸é, Win32DisableAcceptEx + Áö½Ã¾î¸¦ Âü°íÇ϶ó.

+ + + +

Premature end of script + headers

+ +

º¸Åë CGI ½ºÅ©¸³Æ®¿¡ ¹®Á¦°¡ ÀÖÀ¸¸é ºê¶ó¿ìÀú¿¡°Ô Internal + Server Error¸¦ º¸³»°í ¿À·ù·Î±×¿¡ ÀÌ ¹®±¸¸¦ ±â·ÏÇÑ´Ù. + ÀÌ·± ¹®Á¦¸¦ µð¹ö±ëÇÒ¶§ CGI ÅõÅ丮¾óÀÌ + µµ¿òÀÌ µÉ ¼ö ÀÖ´Ù.

+ + +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/faq/index.html b/docs/manual/faq/index.html new file mode 100644 index 00000000..9ee33086 --- /dev/null +++ b/docs/manual/faq/index.html @@ -0,0 +1,11 @@ +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/faq/index.html.en b/docs/manual/faq/index.html.en new file mode 100644 index 00000000..a159e102 --- /dev/null +++ b/docs/manual/faq/index.html.en @@ -0,0 +1,49 @@ + + + +Frequently Asked Questions - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Frequently Asked Questions

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

The latest version of this FAQ is always available from the + main Apache web site, at <http://httpd.apache.org/docs/2.2/faq/>. In addition, you + can view this FAQ all in one page for easy + searching and printing.

+ +

If you don't find the answer to your question in the below + sections, please also consult the Apache 1.3 + FAQ to see if your question is answered there.

+
+
top
+
+

Topics

+
Background
Background information about the Apache HTTP Server.
+
Support
What do I do when I have problems?
+
Error Messages
What does this error message mean?
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/index.html.ja.euc-jp b/docs/manual/faq/index.html.ja.euc-jp new file mode 100644 index 00000000..93eda4b4 --- /dev/null +++ b/docs/manual/faq/index.html.ja.euc-jp @@ -0,0 +1,51 @@ + + + +¤è¤¯¤¢¤ë¼ÁÌä - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¤è¤¯¤¢¤ë¼ÁÌä

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +

Apache ¤Î¼ç¥µ¥¤¥È¡¢<http://httpd.apache.org/docs/2.2/faq/> + ¤«¤éºÇ¿·ÈǤΠFAQ ¤ò¾ï¤Ë¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤Þ¤¿¡¢´Êñ¤Ê¸¡º÷¤ä°õºþ¤Î¤¿¤á¤Ë¤³¤Î FAQ ¤Î + °ì¥Ú¡¼¥¸ÈǤ⤢¤ê¤Þ¤¹¡£

+ +

Apache 2.0 ¤Ï¤Þ¤À¿·¤·¤¤¤Î¤Ç¡¢²¿¤¬¤è¤¯¤¢¤ë¼ÁÌä¤Ê¤Î¤« + ¤Þ¤À¤è¤¯¤ï¤«¤Ã¤Æ¤¤¤Þ¤»¤ó¡£¤³¤Î¥»¥¯¥·¥ç¥ó¤¬Ëä¤Þ¤Ã¤Æ¤¤¤¯¤Þ¤Ç¡¢ + ´û¤Ë¼ÁÌ䤬Åú¤¨¤é¤ì¤Æ¤¤¤ë¤«¤É¤¦¤« Apache 1.3 ¤Î FAQ + ¤â¸«¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+
top
+
+

¥È¥Ô¥Ã¥¯

+
¥µ¥Ý¡¼¥È
²¿¤«ÌäÂ꤬µ¯¤³¤Ã¤¿¤È¤­¤Ë¤É¤¦¤¹¤ë?
+
¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸
¤³¤Î¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Î°ÕÌ£¤Ï?
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/index.html.ko.euc-kr b/docs/manual/faq/index.html.ko.euc-kr new file mode 100644 index 00000000..be386b06 --- /dev/null +++ b/docs/manual/faq/index.html.ko.euc-kr @@ -0,0 +1,49 @@ + + + +ÀÚÁÖ ¹°¾îº¸´Â Áú¹® (FAQ) - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

ÀÚÁÖ ¹°¾îº¸´Â Áú¹® (FAQ)

+
+

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

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

FAQ ÃÖ½ÅÆÇÀº ¾ÆÆÄÄ¡ À¥»çÀÌÆ® <http://httpd.apache.org/docs/2.2/faq/>¿¡¼­ º¼ ¼ö + ÀÖ´Ù. ¶Ç, °Ë»öÇÏ°í Ãâ·ÂÇϱâ ÆíÇÏ°Ô FAQ¸¦ ÇÑ ÆäÀÌÁö·Î º¼ ¼ö ÀÖ´Ù.

+ +

¾ÆÆÄÄ¡ 2.0ÀÌ ³ª¿ÂÁö ¾ó¸¶ ¾ÈµÇ¼­ ¿ì¸®´Â ¾ÆÁ÷ ÀÚÁÖ + ¹°¾îº¸´Â Áú¹® (FAQ)ÀÌ ¹«¾ùÀÎÁö ¸ð¸¥´Ù. ³»¿ëÀÌ Ã¤¿öÁú + ¶§±îÁö ¿©±â¿¡ ÇØ´äÀÌ ¾ø´Ù¸é ¾ÆÆÄÄ¡ + 1.3 FAQµµ Âü°íÇ϶ó.

+
+
top
+
+

ÁÖÁ¦

+
Áö¿ø
¹®Á¦°¡ »ý±â¸é ¾î¶»°Ô ÇØ°áÇϳª?
+
¿À·ù¹®
ÀÌ ¿À·ù¹®ÀÌ ¹«½¼ ¶æÀΰ¡?
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/faq/support.html b/docs/manual/faq/support.html new file mode 100644 index 00000000..2af73a38 --- /dev/null +++ b/docs/manual/faq/support.html @@ -0,0 +1,11 @@ +URI: support.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: support.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: support.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/faq/support.html.en b/docs/manual/faq/support.html.en new file mode 100644 index 00000000..1ac12b11 --- /dev/null +++ b/docs/manual/faq/support.html.en @@ -0,0 +1,114 @@ + + + +Support - Frequently Asked Questions - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > FAQ

Support - Frequently Asked Questions

+
+

Available Languages:  en  | + ja  | + ko 

+
+
+
top
+
+

Support

+ + +

"Why can't I ...? Why won't ... work?" What to do in case of + problems

+ + +

If you are having trouble with your Apache server software, you should + take the following steps:

+ +
+
Check the ErrorLog!
+
Apache tries to be helpful when it encounters a problem. In many + cases, it will provide some details by writing one or more messages to the + server error log. Sometimes this is enough for you to diagnose & fix + the problem yourself (such as file permissions or the like). The default + location of the error log is + /usr/local/apache2/logs/error_log, but see the ErrorLog directive in your config files for the + location on your server.
+ +
Check the ErrorLog again!
+
Nearly all problems can be solved by reading the error log.
+ +
Check the FAQ!
+
The latest version of the Apache Frequently-Asked Questions list can + always be found at the main Apache web site.
+ +
Check the Apache bug database
+
Most problems that get reported to The Apache Group are recorded in + the bug database. + Please check the existing reports, open + and closed, before adding one. If you find that your + issue has already been reported, please don't add a "me, too" + report. If the original report isn't closed yet, we suggest that you + check it periodically. You might also consider contacting the original + submitter, because there may be an email exchange going on about the + issue that isn't getting recorded in the database.
+ +
Ask in a user support forum
+

Apache has an active community of users who are willing to share + their knowledge. Participating in this community is usually the best and + fastest way to get answers to your questions and problems.

+ +

Users + mailing list

+ +

#apache on + Freenode IRC is also available for + user support issues.

+
+ +
Please use the bug database for bugs!
+

If you've gone through those steps above that are appropriate and + have obtained no relief, then please do let the httpd developers + know about the problem by logging a bug + report.

+ +

If your problem involves the server crashing and generating a core + dump, please + include a backtrace (if possible).

+
+
+ + +

Whom do I contact for support?

+

With millions of users and fewer than sixty volunteer developers, + we cannot provide personal support for Apache. For free support, we + suggest participating in a user forum.

+ +

Professional, commercial support for Apache is available from + a number of + companies.

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/support.html.ja.euc-jp b/docs/manual/faq/support.html.ja.euc-jp new file mode 100644 index 00000000..fc5f1530 --- /dev/null +++ b/docs/manual/faq/support.html.ja.euc-jp @@ -0,0 +1,134 @@ + + + +¥µ¥Ý¡¼¥È ¡½ ¤è¤¯¤¢¤ë¼ÁÌä - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > FAQ

¥µ¥Ý¡¼¥È ¡½ ¤è¤¯¤¢¤ë¼ÁÌä

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+
+
top
+
+

¥µ¥Ý¡¼¥È

+ + +

¡Ö¤Ê¤ó¤Ç¡Ä? ¤É¤¦¤·¤ÆÆ°ºî¤·¤Ê¤¤¡Ä?¡×ÌäÂ꤬ + µ¯¤­¤¿¤È¤­¤Ë¤É¤¦¤¹¤ë¤«

+ + +

Apache ¤Î¥µ¡¼¥Ð¥½¥Õ¥È¥¦¥§¥¢¤Ë²¿¤«ÌäÂ꤬µ¯¤³¤Ã¤¿¤È¤­¤Ï¡¢°Ê²¼¤Î + ¼ê½ç¤Ë½¾¤Ã¤Æ¤¯¤À¤µ¤¤:

+ +
+
¥¨¥é¡¼¥í¥°¤òÄ´¤Ù¤ë!
+
ÌäÂ꤬ȯÀ¸¤·¤¿¤È¤­¤Ï Apache ¤Ï¤Ê¤ë¤Ù¤¯¼ê½õ¤±¤ò¤·¤è¤¦¤È¤·¤Þ¤¹¡£ + ¿¤¯¤Î¾ì¹ç¡¢Apache ¤Ï¥µ¡¼¥Ð¤Î¥¨¥é¡¼¥í¥°¤Ë¥á¥Ã¥»¡¼¥¸¤ò½ñ¤¯¤³¤È¤Ç¡¢¾ÜºÙ¤Ê + ¾ðÊó¤òÄ󶡤·¤Þ¤¹¡£¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï¡¢¤³¤ì¤À¤±¤ÇÌäÂê¤ò¼«Ê¬¼«¿È¤ÇʬÀϤ·¡¢ + ½¤Àµ¤¹¤ë¤¿¤á¤Ë½½Ê¬¤Ê¾ðÊó¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹ (¥Õ¥¡¥¤¥ë¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤Î + ÌäÂê¤Ê¤É)¡£¥¨¥é¡¼¥í¥°¤Î¥Ç¥Õ¥©¥ë¥È¤Î¾ì½ê¤Ï + /usr/local/apache2/logs/error_log ¤Ç¤¹¤¬¡¢¤¢¤Ê¤¿¤Î¥µ¡¼¥Ð + ¤Ç¤Î¾ì½ê¤òÃΤ뤿¤á¤Ë¤ÏÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î ErrorLog ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
+ +
FAQ ¤òÄ´¤Ù¤ë!
+
Apache ¤Î¤è¤¯¤¢¤ë¼ÁÌä¤ÎºÇ¿·ÈǤϾï¤Ë Apache ¤Î¼ç¥¦¥§¥Ö¥µ¥¤¥È¤Ë + ¤¢¤ê¤Þ¤¹¡£
+ +
Apache ¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÄ´¤Ù¤ë
+
Apache ¥°¥ë¡¼¥×¤ËÊó¹ð¤µ¤ì¤ë¤Û¤È¤ó¤É¤ÎÌäÂê¤Ï¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë + µ­Ï¿¤µ¤ì¤Þ¤¹¡£Open ¤â closed ¤â ´Þ¤á¤Æ¡¢ + ´û¸¤Î¥ì¥Ý¡¼¥È¤Ë¤¢¤ë¤«¤É¤¦¤«¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£ + ´û¤ËÌäÂ꤬Êó¹ð¤µ¤ì¤Æ¤¤¤ë¤È¤­¡¢¡Ö»ä¤â¡×¤È¤¤¤¦Êó¹ð¤ÏÄɲ䷤ʤ¤¤Ç + ¤¯¤À¤µ¤¤¡£¸µ¤ÎÊó¹ð¤¬ close ¤µ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ï¡¢Äê´üŪ¤Ë + ¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÄ´¤Ù¤ë¤³¤È¤ò¤ªÁ¦¤á¤·¤Þ¤¹¡£¤Þ¤¿¡¢¸µ¤ÎÄó½Ð¼Ô¤Ë + Ï¢Íí¤ò¼è¤ë¤³¤È¤â¹Íθ¤ËÆþ¤ì¤Æ¤ª¤¯¤È¤è¤¤¤Ç¤·¤ç¤¦¡£¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë + µ­Ï¿¤µ¤ì¤Æ¤¤¤Ê¤¤ÅŻҥ᡼¥ë¤Î¸ò´¹¤¬¹Ô¤Ê¤ï¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
+ +
¥æ¡¼¥¶¥µ¥Ý¡¼¥È¥Õ¥©¡¼¥é¥à¤Ç¼ÁÌ䤹¤ë
+

Apache ¤Ë¤Ï¤è¤í¤³¤ó¤ÇÃ챤ò¶¦Í­¤µ¤»¤Æ¤¯¤ì¤ë³èȯ¤Ê + ¥æ¡¼¥¶¤Î¥³¥ß¥å¥Ë¥Æ¥£¤¬¤¢¤ê¤Þ¤¹¡£¤³¤Î¥³¥ß¥å¥Ë¥Æ¥£¤Ë»²²Ã¤¹¤ë¤³¤È¤¬¡¢ + ÉáÄ̤ϼÁÌä¤äÌäÂê¤ËÂФ¹¤ë²óÅú¤òÆÀ¤ëºÇÁ±¤ÇºÇ®¤Î¼êÃʤǤ¹¡£

+ +

¥æ¡¼¥¶ + ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È

+ +

USENET ¥Ë¥å¡¼¥¹¥°¥ë¡¼¥×:

+ +
+ +
¤â¤·¡¢Á´Éô¼ºÇÔ¤·¤¿¾ì¹ç¤Ï¡¢ÌäÂê¤ò¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÊó¹ð¤·¤Æ¤¯¤À¤µ¤¤
+

¾åµ­¤Î¼êÃʤÎÃæ¤Ç³ºÅö¤¹¤ë¤â¤Î¤ò¤ò¤¹¤Ù¤Æ¼è¤Ã¤Æ¡¢ + ¤½¤ì¤Ç¤âÌäÂê¤Î²ò·èºö¤òÆÀ¤é¤ì¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï¡¢¥Ð¥°¤ÎÊó¹ð¤ò + ¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢ÌäÂê¤ò¤¼¤Ò httpd ³«È¯¼Ô¤ËÃΤ餻¤Æ¤¯¤À¤µ¤¤¡£

+ +

¥µ¡¼¥Ð¤Î¥¯¥é¥Ã¥·¥å¤ä¥³¥¢¥À¥ó¥×¤ÎȯÀ¸¤¹¤ëÌäÂê¤Ç¤¢¤ì¤Ð¡¢(²Äǽ¤Ç¤¢¤ì¤Ð) + ¥Ð¥Ã¥¯¥È¥ì¡¼¥¹¤òÊó¹ð¤Ë´Þ¤á¤Æ¤¯¤À¤µ¤¤¡£Î㤨¤Ð¡¢

+ +

+ # cd ServerRoot
+ # dbx httpd core
+ (dbx) where +

+ +

(ServerRoot ¤È httpd ¤È core ¥Õ¥¡¥¤¥ë + ¤Î°ÌÃÖ¤òŬÀڤʤâ¤Î¤ËÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£dbx ¤ÎÂå¤ï¤ê¤Ë + gdb ¤ò»È¤¦É¬Íפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£)

+
+
+ + +

ï¤Ë¥µ¥Ý¡¼¥È¤òÍê¤á¤Ð¤è¤¤?

+

¿ôÉ´Ëü¤Î¥æ¡¼¥¶¤ËÂФ·¤Æ¡¢40̤Ëþ¤Î¥Ü¥é¥ó¥Æ¥£¥¢³«È¯¼Ô¤·¤«¤¤¤Ê¤¤¤¿¤á¡¢ + Apache ¤Î¸Ä¿ÍŪ¤Ê¥µ¥Ý¡¼¥È¤òÄ󶡤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ÌµÎÁ¤Î + ¥µ¥Ý¡¼¥È¤Ë¤Ï¡¢¥æ¡¼¥¶¤Î¥Õ¥©¡¼¥é¥à¤Ë»²²Ã¤¹¤ë¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+ +

Apache ¤Î¥×¥í¤Î¡¢¾¦ÍÑ¥µ¥Ý¡¼¥È¤â + ¿¤¯¤Î²ñ¼Ò + ¤«¤éÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/faq/support.html.ko.euc-kr b/docs/manual/faq/support.html.ko.euc-kr new file mode 100644 index 00000000..0bf83003 --- /dev/null +++ b/docs/manual/faq/support.html.ko.euc-kr @@ -0,0 +1,142 @@ + + + +Áö¿ø - ÀÚÁÖ ¹°¾îº¸´Â Áú¹® (FAQ) - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > FAQ

Áö¿ø - ÀÚÁÖ ¹°¾îº¸´Â Áú¹® (FAQ)

+
+

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

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

Áö¿ø

+ + +

"¿Ö ... ¾ÈµÇ³ª? ¿Ö ... µ¿ÀÛÇÏÁö ¾Ê´Â°¡?" ¹®Á¦°¡ »ý±â¸é + ÇÒÀÏ

+ + +

¾ÆÆÄÄ¡ ¼­¹ö ¼ÒÇÁÆ®¿þ¾î¿¡ ¹®Á¦°¡ »ý±â¸é ´ÙÀ½°ú °°Àº + ´Ü°è¸¦ µû¸¥´Ù:

+ +
+
¿À·ù ·Î±×(errorlog)¸¦ È®ÀÎÇ϶ó!
+
¾ÆÆÄÄ¡ ¼­¹ö´Â ¹®Á¦°¡ »ý±â¸é µµ¿òÀ» ÁÖ·Á°í ³ë·ÂÇÑ´Ù. + ¸¹Àº °æ¿ì ¼­¹ö ¿À·ù ·Î±×¿¡ ÀÚ¼¼ÇÑ ³»¿ëÀ» ±â·ÏÇÑ´Ù. + À̰͸¸À¸·Îµµ Á÷Á¢ (ÆÄÀϱÇÇÑ µî) ¹®Á¦¸¦ ¹ß°ßÇÏ°í °íÄ¥ ¼ö + ÀÖ´Â °æ¿ì°¡ ¸¹´Ù. ¿À·ù ·Î±×ÀÇ ±âº» À§Ä¡´Â + /usr/local/apache2/logs/error_logÀÌÁö¸¸, + Á¤È®ÇÑ À§Ä¡´Â ¼³Á¤ÆÄÀÏÀÇ ErrorLog Áö½Ã¾î¸¦ Âü°íÇ϶ó.
+ +
FAQ¸¦ + È®ÀÎÇ϶ó!
+
¾ÆÆÄÄ¡ À¥»çÀÌÆ®¿¡¼­ Ç×»ó ¾ÆÆÄÄ¡ FAQ ÃÖ½ÅÆÇÀ» º¼ ¼ö + ÀÖ´Ù.
+ +
¾ÆÆÄÄ¡ ¹ö±× µ¥ÀÌÅͺ£À̽º¸¦ È®ÀÎÇ϶ó
+
¾ÆÆÄÄ¡±×·ì(The Apache Group)¿¡ º¸°íµÈ ´ëºÎºÐÀÇ ¹®Á¦´Â + ¹ö±× + µ¥ÀÌÅͺ£À̽º¿¡ ±â·ÏµÈ´Ù. »õ·Î ¹ö±×¸¦ Ãß°¡Çϱâ Àü¿¡, + ÀÌ¹Ì ¾Ë·ÁÁ³°Å³ª(open) ÇØ°áµÈ(closed) ¹ö±×°¡ ÀÖ´ÂÁö È®ÀÎÇϱæ + ¹Ù¶õ´Ù. ÀÌ¹Ì ¹®Á¦°¡ º¸°íµÇ¾ú´Ù¸é "³ªµµ + ÀÌ·± ¹®Á¦°¡ ÀÖ´Ù°í" º¸°íÇÏÁö ¾Ê±æ ¹Ù¶õ´Ù. ¾ÆÁ÷ + ÇØ°áµÇÁö ¾Ê¾Ò´Ù¸é ÁÖ±âÀûÀ¸·Î »óȲÀ» È®ÀÎÇÏ±æ ¹Ù¶õ´Ù. ¶Ç, + µ¥ÀÌÅͺ£À̽º¿¡ ±â·ÏµÇÁö ¾Ê°í À̸ÞÀÏ ±³È¯À¸·Î ÁøÇàµÈ »çÇ×ÀÌ + ÀÖÀ» ¼ö ÀÖÀ¸´Ï óÀ½ ¹®Á¦¸¦ º¸°íÇÑ »ç¶÷¿¡°Ô ¿¬¶ôÇغ¼ ¼öµµ + ÀÖ´Ù.
+ +
»ç¿ëÀÚ Áö¿ø °ø°£¿¡ + ¹®ÀÇÇÑ´Ù
+

¾ÆÆÄÄ¡¿¡ ´ëÇÑ Áö½ÄÀ» °øÀ¯ÇÏ±æ ¿øÇÏ´Â È°¹ßÇÑ »ç¿ëÀÚ + °øµ¿Ã¼µéÀÌ ÀÖ´Ù. ÀϹÝÀûÀ¸·Î ÀÌ·± °øµ¿Ã¼¿¡ Âü¿©ÇÏ´Â °ÍÀÌ + ¹®Á¦ÀÇ ´äÀ» ¾ò´Â °¡Àå ÁÁ°í ºü¸¥ ¹æ¹ýÀÌ´Ù.

+ +

»ç¿ëÀÚ + ¸ÞÀϸµ¸®½ºÆ®

+ +

USENET ´º½º±×·ì:

+ +
    +
  • comp.infosystems.www.servers.unix + [news] + [google] +
    • + +
  • comp.infosystems.www.servers.ms-windows + [news] + [google] +
    • + +
  • comp.infosystems.www.authoring.cgi + [news] + [google] +
    • +
+ +
À§ÀÇ ¹æ¹ýÀÌ ¸ðµÎ ½ÇÆÐÇÏ¸é ¹ö±× µ¥ÀÌÅͺ£À̽º¿¡ ¹®Á¦¸¦ + º¸°íÇÑ´Ù
+

À§ÀÇ ´Ü°è¸¦ ¸ðµÎ ½ÃµµÇÏ°íµµ ÇØ°áÃ¥ÀÌ ¾ø´Ù¸é, ¹ö±×¸¦ + º¸°íÇÏ¿© À¥¼­¹ö °³¹ßÀڵ鿡°Ô ¹®Á¦¸¦ ¾Ë¸®±æ + ¹Ù¶õ´Ù.

+ +

core dump¸¦ ¸¸µé¸ç ¼­¹ö°¡ Á×´Â °æ¿ì¶ó¸é (°¡´ÉÇϸé) + backtrace(¿ªÁÖ; ¹®Á¦°¡ ½ÇÇàÆÄÀÏÀÇ Á¤È®È÷ ¾î¶² ÁöÁ¡¿¡¼­ + ¹ß»ýÇÏ¿´°í, ÇÁ·Î±×·¥ÀÌ ±× ÁöÁ¡±îÁö ¾î¶² °æ·Î·Î ½ÇÇàµÇ¾ú´ÂÁö¸¦ + ¾Ë·ÁÁÖ´Â Á¤º¸)¸¦ Æ÷ÇÔÇÏ±æ ¹Ù¶õ´Ù. ¿¹¸¦ µé¾î,

+ +

+ # cd ServerRoot
+ # dbx httpd core
+ (dbx) where +

+ +

(ServerRoot, httpd, core + ÆÄÀÏÀÇ ½ÇÁ¦ À§Ä¡¸¦ ´ë½Å »ç¿ëÇ϶ó. dbx ´ë½Å + gdb¸¦ »ç¿ëÇØ¾ß ÇÒ ¼öµµ ÀÖ´Ù.)

+
+
+ + +

µµ¿òÀ» ¾òÀ¸·Á¸é ´©±¸¿¡°Ô + ¿¬¶ôÇϳª?

+

40¸í °¡·®ÀÇ ÀÚ¹ßÀûÀ¸·Î Âü¿©ÇÑ °³¹ßÀÚ¸¸À¸·Î´Â ¼ö¹é¸¸ÀÇ + »ç¿ëÀÚ¿¡°Ô ¾ÆÆÄÄ¡¿¡ ´ëÇØ ÀÏÀÏÀÌ Áö¿øÇÒ ¼ö ¾ø´Ù. ¹«·á Áö¿øÀ» + ¾òÀ¸·Á¸é »ç¿ëÀÚ + °ø°£¿¡ Âü¿©ÇÏ±æ ±ÇÇÑ´Ù.

+ +

¾ÆÆÄÄ¡¿¡ ´ëÇÑ Á÷¾÷ÀûÀÎ À¯·á Áö¿øÀº ¿©·¯ + ȸ»ç¿¡¼­ Á¦°øÇÑ´Ù.

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/filter.html b/docs/manual/filter.html new file mode 100644 index 00000000..98b9e5c4 --- /dev/null +++ b/docs/manual/filter.html @@ -0,0 +1,19 @@ +URI: filter.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: filter.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: filter.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: filter.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: filter.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/filter.html.en b/docs/manual/filter.html.en new file mode 100644 index 00000000..4f3982d7 --- /dev/null +++ b/docs/manual/filter.html.en @@ -0,0 +1,137 @@ + + + +Filters - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Filters

+
+

Available Languages:  en  | + es  | + fr  | + ja  | + ko 

+
+ +

This document describes the use of filters in Apache.

+
+ +
top
+
+

Filtering in Apache 2

+ +
Related ModulesRelated Directives
+ +

The Filter Chain is available in Apache 2.0 and higher, +and enables applications to process incoming and outgoing data +in a highly flexible and configurable manner, regardless of +where the data comes from. We can pre-process incoming data, +and post-process outgoing data, at will. This is basically +independent of the traditional request processing phases.

+

+Filters can be chained, in a Data Axis orthogonal to request processing +

+

Some examples of filtering in the standard Apache distribution are:

+ +

Apache also uses a number of filters internally to perform +functions like chunking and byte-range handling.

+ +

A wider range of applications are implemented by third-party filter +modules available from modules.apache.org and +elsewhere. A few of these are:

+ +
    +
  • HTML and XML processing and rewriting
    • +
  • XSLT transforms and XIncludes
    • +
  • XML Namespace support
    • +
  • File Upload handling and decoding of HTML Forms
    • +
  • Image processing
    • +
  • Protection of vulnerable applications such as PHP scripts
    • +
  • Text search-and-replace editing
    • +
+
top
+
+

Smart Filtering

+ +

+Smart filtering applies different filter providers according to the state of request processing +

+

mod_filter, included in Apache 2.1 and later, +enables the filter chain to be configured dynamically at run time. +So for example you can set up a proxy to rewrite +HTML with an HTML filter and JPEG images with a completely +separate filter, despite the proxy having no prior information +about what the origin server will send. This works by using a +filter harness, that dispatches to different providers according +to the actual contents at runtime. Any filter may be either +inserted directly in the chain and run unconditionally, or +used as a provider and inserted dynamically. For example,

+
    +
  • an HTML processing filter will only run if the content is +text/html or application/xhtml+xml
    • +
  • A compression filter will only run if the input is a +compressible type and not already compressed
    • +
  • A charset conversion filter will be inserted if a text +document is not already in the desired charset
    • +
+
top
+
+

Using Filters

+ +

There are two ways to use filtering: Simple and Dynamic. +In general, you should use one or the other; mixing them can +have unexpected consequences (although simple Input filtering +can be mixed freely with either simple or dynamic Output filtering).

+

The Simple Way is the only way to configure input filters, and is +sufficient for output filters where you need a static filter chain. +Relevant directives are + SetInputFilter, + SetOutputFilter, + AddInputFilter, + AddOutputFilter, + RemoveInputFilter, and + RemoveOutputFilter.

+ +

The Dynamic Way enables both static and flexible, dynamic configuration +of output filters, as discussed in the mod_filter page. +Relevant directives are + FilterChain, + FilterDeclare, and + FilterProvider.

+ +

One further directive AddOutputFilterByType is still supported, +but may be problematic and is now deprecated. Use dynamic +configuration instead.

+ +
+
+

Available Languages:  en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/filter.html.es b/docs/manual/filter.html.es new file mode 100644 index 00000000..f18d765d --- /dev/null +++ b/docs/manual/filter.html.es @@ -0,0 +1,81 @@ + + + +Filtros - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

Filtros

+
+

Idiomas disponibles:  en  | + es  | + fr  | + ja  | + ko 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ +

Este documento describe cómo usar filtros en Apache.

+
+
top
+
+

Filtros

+ +
Módulos RelacionadosDirectivas Relacionadas
+ +

Un filtro es un proceso que se aplica a los datos que + se reciben o se envían por el servidor. Los datos enviados + por los clientes al servidor son procesados por filtros de + entrada mientras que los datos enviados por el servidor se + procesan por los filtros de salida. A los datos se les + pueden aplicar varios filtros, y el orden en que se aplica cada + filtro puede especificarse explícitamente.

+ +

Los filtros se usan internamente por Apache para llevar a cabo + funciones tales como chunking y servir peticiones de + byte-range. Además, los módulos contienen filtros que se + pueden seleccionar usando directivas de configuración al + iniciar el servidor. El conjunto de filtros que se aplica a los + datos puede manipularse con las directivas SetInputFilter, SetOutputFilter, AddInputFilter, AddOutputFilter, RemoveInputFilter, y RemoveOutputFilter.

+ +

Actualmente, vienen con la distribución de Apache los + siguientes filtros seleccionables por el usuario.

+ +
+
INCLUDES
+
Server-Side Includes procesado por + mod_include
+
DEFLATE
+
Comprime los datos de salida antes de enviarlos al cliente + usando el módulo + mod_deflate +
+
+ +

Además, el módulo mod_ext_filter + permite definir programas externos como filtros.

+
+
+

Idiomas disponibles:  en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/filter.html.fr b/docs/manual/filter.html.fr new file mode 100644 index 00000000..ee4216a3 --- /dev/null +++ b/docs/manual/filter.html.fr @@ -0,0 +1,84 @@ + + + +Filtres - Serveur Apache HTTP + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur Apache HTTP Version 2.2

+
+
<-
+
+Apache > Serveur HTTP > Documentation > Version 2.2

Filtres

+
+

Langues Disponibles:  en  | + es  | + fr  | + ja  | + ko 

+
+
Cette traduction peut être périmée. Verifiez la version + Anglaise pour les changements récents.
+ +

Ce document explique le fonctionnement des filtres avec Apache.

+
+
top
+
+

Filtres

+ +
Modules ApparentésDirectives Apparentées
+ +

On appelle filtre un processus qui s'applique aux données reçues + ou envoyées par le serveur. Les filtres en entrée ("input filters") + servent à filtrer les données envoyées par les clients au serveur, tandis + que les filtres en sortie ("output filters") travaillent sur les + données envoyées par le serveur à un client. Il est possible d'appliquer + plusieurs filtres à un flux de données, et l'ordre de ces filtres peux être + spécifiée de façon explicite.

+ +

Apache utilise des filtres en interne pour par exemple gérer les "grosses" requêtes + (chunked) ou les requêtes partielles (NDT : "byte-range" : requêtes sur seulement une + partie d'un fichier spécifiée par un pointeur de départ, et de fin). + Certains modules permettent en plus d'utiliser des filtres + en utilisant des directives de configuration. Les filtres sont utilisables + au moyen des directives + SetInputFilter, + SetOutputFilter, + AddInputFilter, + AddOutputFilter, + RemoveInputFilter et + RemoveOutputFilter + .

+ +

Les filtres listés ci-dessous sont fournis dans la distribution d'Apache, et + peuvent être utilisés par tout administrateur.

+ +
+
INCLUDES
+
Le module mod_include travaille au moyen de + "Server-Side Includes"
+
DEFLATE
+
Le module mod_deflate compresse les données avant leur envoi au + client (filtre en sortie).
+
+ +

En outre, le module mod_ext_filter permet d'utiliser des + programes externes à Apache en tant que filtres.

+
+
+

Langues Disponibles:  en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/filter.html.ja.euc-jp b/docs/manual/filter.html.ja.euc-jp new file mode 100644 index 00000000..fbdf2b87 --- /dev/null +++ b/docs/manual/filter.html.ja.euc-jp @@ -0,0 +1,141 @@ + + + +¥Õ¥£¥ë¥¿ - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥Õ¥£¥ë¥¿

+
+

Available Languages:  en  | + es  | + fr  | + ja  | + ko 

+
+ +

Apache ¤Ç¤Î¥Õ¥£¥ë¥¿¤Î»È¤¤Êý¤Ë¤Ä¤¤¤Æµ­½Ò¤·¤Æ¤¤¤Þ¤¹¡£

+
+ +
top
+
+

Apache 2 ¤Î¥Õ¥£¥ë¥¿

+ +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

Apache 2.0 °Ê¹ß¤Ç¤Ï¥Õ¥£¥ë¥¿¥Á¥§¥¤¥óµ¡Ç½¤¬»È¤¨¡¢¥Ç¡¼¥¿¤¬ +¤É¤³¤«¤éÍè¤ë¤«¤Ë´Ø¤ï¤é¤º¡¢Èó¾ï¤Ë½ÀÆð¤ÇÄ´À°¤·¤ä¤¹¤¤ÊýË¡¤Ç +Æþ½ÐÎϥǡ¼¥¿¤ò½èÍý¤Ç¤­¤Þ¤¹¡£ +ÆþÎϥǡ¼¥¿¤ò¥×¥ê¥×¥í¥»¥¹¤·¤¿¤ê½ÐÎϥǡ¼¥¿¤ò¥Ý¥¹¥È¥×¥í¥»¥¹¤·¤¿¤ê¤Ç¤­¤Þ¤¹¡£ +¤³¤Î½èÍý¤Ï¡¢¤³¤ì¤Þ¤Ç¤Î¥ê¥¯¥¨¥¹¥È½èÍý¥Õ¥§¡¼¥º¤È¤Ïº¬ËÜŪ¤ËÆÈΩ¤·¤¿ +½èÍý¤Ë¤Ê¤ê¤Þ¤¹¡£

+

+Filters can be chained, in a Data Axis orthogonal to request processing +

+

Apache ¤Îɸ½àŪ¤Ê¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Ç¤Î¥Õ¥£¥ë¥¿Îã¤Ï :

+
    +
  • mod_include ¤Ç¡¢¥µ¡¼¥Ð¥µ¥¤¥É¥¤¥ó¥¯¥ë¡¼¥É SSI ¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹
    • +
  • mod_ssl ¤Ç¡¢SSL °Å¹æ²½ (https) ¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£
    • +
  • mod_deflate ¤Ç¡¢on-the-fly ¤Î¥Ç¡¼¥¿°µ½Ì¡¦Å¸³«µ¡Ç½¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£
    • +
  • mod_charset_lite ¤Ç¡¢°Û¤Ê¤ëʸ»ú¥»¥Ã¥È´Ö¤ÎÊÑ´¹¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£
    • +
  • mod_ext_filter ¤Ç¡¢³°Éô¥×¥í¥°¥é¥à¤ò¥Õ¥£¥ë¥¿¤È¤·¤Æ¼Â¹Ô¤·¤Þ¤¹¡£
    • +
+

¥Á¥ã¥ó¥­¥ó¥°¤ä¥Ð¥¤¥È¥ì¥ó¥¸½èÍý¤È¤¤¤Ã¤¿½èÍý¤ò¹Ô¤¦¤¿¤á¤Ë +Apache ¤Ï¡¢ÆâÉôŪ¤Ë¤¤¤¯¤Ä¤«¤Î¥Õ¥£¥ë¥¿¤ò»È¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

ÍÍ¡¹¤Ê¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤¬¥µ¡¼¥É¥Ñ¡¼¥Æ¥£À½¤Î¥Õ¥£¥ë¥¿¥â¥¸¥å¡¼¥ë¤È¤·¤Æ +¼ÂÁõ¤µ¤ì¤Æ¤¤¤Æ¡¢modules.apache.org +¤Ê¤É¤«¤é¼èÆÀ¤Ç¤­¤Þ¤¹¡£¤¿¤È¤¨¤Ð :

+ +
    +
  • HTML ¤ä XML ¤Î½èÍý¤È½ñ¤­´¹¤¨
    • +
  • XSLT ÊÑ´¹¤È XIncludes
    • +
  • XML ̾Á°¶õ´Ö¤Î¥µ¥Ý¡¼¥È
    • +
  • ¥Õ¥¡¥¤¥ë¥¢¥Ã¥×¥í¡¼¥É½èÍý¤ä HTML ¥Õ¥©¡¼¥à¤Î¥Ç¥³¡¼¥É
    • +
  • ²èÁü½èÍý
    • +
  • PHP ¥¹¥¯¥ê¥×¥È¤Ê¤É¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ËÂФ¹¤ëÊݸǽ
    • +
  • ¥Æ¥­¥¹¥È¤Î¸¡º÷ÃÖ´¹¡¦ÊÔ½¸µ¡Ç½
    • +
+
top
+
+

¥¹¥Þ¡¼¥È¥Õ¥£¥ë¥¿

+ +

+Smart filtering applies different filter providers according to the state of request processing +

+

Apache 2.1 °Ü¹Ô¤Ë´Þ¤Þ¤ì¤ë mod_filter ¤Ç¤Ï¡¢ +¼Â¹Ô»þ¤ËưŪ¤Ë¥Õ¥£¥ë¥¿¥Á¥§¥¤¥ó¤òÍ­¸ú¤Ë¤Ç¤­¤Þ¤¹¡£ +¤Ç¤¹¤«¤é¤¿¤È¤¨¤Ð¡¢HTML ¤ò HTML ¥Õ¥£¥ë¥¿¤Ç¡¢JPEG ²èÁü¤ò¤½¤ì¤È¤Ï +Á´¤¯Ê̤Υե£¥ë¥¿¤Ç¡¢½ñ¤­´¹¤¨¤ë¤è¤¦¤Ê¥×¥í¥¯¥·¤òÀßÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ +¤½¤Î¾å¡¢¤½¤Î¥×¥í¥¯¥·¤Ï¤É¤Î¥ª¥ê¥¸¥ó¥µ¡¼¥Ð¤¬¥³¥ó¥Æ¥ó¥Ä¤òÁ÷¿®¤¹¤ë¤« +»öÁ°¾ðÊó̵¤·¤Ç¤¤¤¤¤è¤¦¤Ë¹½À®¤Ç¤­¤Þ¤¹¡£ +¤³¤ì¤Ï¡¢¼Â¹Ô»þ¤Ë¼ÂºÝ¤Î¥³¥ó¥Æ¥ó¥Ä¤Ë±þ¤¸¤ÆÊÌ¡¹¤Î¥Õ¥£¥ë¥¿¥×¥í¥Ð¥¤¥À¤Ë +¥Ç¥£¥¹¥Ñ¥Ã¥Á¤¹¤ë¥Õ¥£¥ë¥¿¥Ï¡¼¥Í¥¹¤ò»È¤¦¤³¤È¤Ç¼Â¸½¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ +¥Á¥§¥¤¥ó¤ÎÃæ¤ËľÀÜÆþ¤ì¤Æ̵¾ò·ï¤ËŬÍѤ·¤¿¤ê¡¢Æ°Åª¤Ë¥×¥í¥Ð¥¤¥À¤È¤·¤Æ +ŬÍѤ¹¤ë¤è¤¦¤Ë¤·¤¿¤ê¤¹¤ë¤³¤È¤Ï¡¢¤É¤ó¤Ê¥Õ¥£¥ë¥¿¤Ç¤â¤Ç¤­¤Þ¤¹¡£ +¤¿¤È¤¨¤Ð¡¢

+
    +
  • HTML ½èÍý¥Õ¥£¥ë¥¿¤Ï¥³¥ó¥Æ¥ó¥È¤¬ text/html ¤¢¤ë¤¤¤Ï +application/xhtml+xml ¤Î¾ì¹ç¤Ë¤Î¤ß¼Â¹Ô¤µ¤ì¤Þ¤¹
    • +
  • °µ½Ì¥Õ¥£¥ë¥¿¤Ï°µ½Ì²Äǽ¤ÊÆþÎϤǡ¢È󰵽̾õÂ֤Τâ¤Î¤Ë +ÂФ·¤Æ¤Î¤ß¼Â¹Ô¤µ¤ì¤Þ¤¹
    • +
  • ʸ»ú¥»¥Ã¥ÈÊÑ´¹¥Õ¥£¥ë¥¿¤Ï¥Æ¥­¥¹¥Èʸ½ñ¤¬ +´õ˾¤Îʸ»ú¥»¥Ã¥È¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤¤¾ì¹ç¤ËÁÞÆþ¤µ¤ì¤Þ¤¹
    • +
+
top
+
+

¥Õ¥£¥ë¥¿¤Î»È¤¤Êý

+ +

¥Õ¥£¥ë¥¿¤Î»È¤¤Êý¤Ë¤ÏÆó¤Ä¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹: ¥·¥ó¥×¥ë¤È¥À¥¤¥Ê¥ß¥Ã¥¯¡£ +°ìÈÌŪ¤Ë¤Ï¤É¤Á¤é¤«¤Î¤ß¤ò»È¤Ã¤¿¤Û¤¦¤¬¤è¤¤¤Ç¤·¤ç¤¦¡£ +¤³¤ì¤é¤òÁȤ߹ç¤ï¤»¤Æ»ÈÍѤ¹¤ë¤È¡¢Í½´ü¤·¤Ê¤¤·ë²Ì¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ +(¤È¤Ï¤¤¤¨¡¢¥·¥ó¥×¥ë¤ÊÆþÎÏ¥Õ¥£¥ë¥¿¤È¥·¥ó¥×¥ë¤¢¤ë¤¤¤Ï¥À¥¤¥Ê¥ß¥Ã¥¯¤Ê +½ÐÎÏ¥Õ¥£¥ë¥¿¤òÁȤ߹ç¤ï¤»¤ë¤³¤È¤Ï¼«Í³¤Ë½ÐÍè¤Þ¤¹¡£)

+

¥·¥ó¥×¥ë¤ÊÊýË¡¤Ï¡¢ÆþÎÏ¥Õ¥£¥ë¥¿¤Î¤ß¤òÀßÄꤷ¡¢É¬Íפ˱þ¤¸¤Æ +ÀÅŪ¤Ê¥Õ¥£¥ë¥¿¥Á¥§¥¤¥ó¤ò½ÐÎÏ¥Õ¥£¥ë¥¿¤È¤·¤ÆÀßÄꤹ¤ëÊýË¡¤Ç¤¹¡£ +´ØÏ¢¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + SetInputFilter, + SetOutputFilter, + AddInputFilter, + AddOutputFilter, + RemoveInputFilter, + RemoveOutputFilter + ¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¥À¥¤¥Ê¥ß¥Ã¥¯¤ÊÊýË¡¤Ï¡¢ÀÅŪ¤Ê¤â¤Î¤È¥Õ¥ì¥­¥·¥Ö¥ë¤Ê¤â¤Î¤òξÊýÍ­¸ú¤Ë¤¹¤ë +ÊýË¡¤Ç¡¢mod_filter ¤Î¥Ú¡¼¥¸¤Ç½Ò¤Ù¤é¤ì¤Æ¤¤¤Þ¤¹¡£ +´ØÏ¢¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + FilterChain, + FilterDeclare, + FilterProvider + ¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö AddOutputFilterByType +¤Ï¤Þ¤À¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢¼ï¡¹¤ÎÌäÂê¤ò¤Ï¤é¤ó¤Ç¤ª¤ê¡¢Èó¿ä¾©¤Ç¤¹¡£ +¥À¥¤¥Ê¥ß¥Ã¥¯¤ÊÀßÄêÊýË¡¤òÂå¤ï¤ê¤Ë»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
+

Available Languages:  en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/filter.html.ko.euc-kr b/docs/manual/filter.html.ko.euc-kr new file mode 100644 index 00000000..fbc78201 --- /dev/null +++ b/docs/manual/filter.html.ko.euc-kr @@ -0,0 +1,80 @@ + + + +ÇÊÅÍ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

ÇÊÅÍ

+
+

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

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

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡¿¡¼­ ÇÊÅ͸¦ »ç¿ëÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù.

+
+
top
+
+

ÇÊÅÍ

+ +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

ÇÊÅÍ(filter)´Â ¼­¹ö°¡ º¸³»°Å³ª ¹Þ´Â ÀÚ·á¿¡ + Àû¿ëµÇ´Â ÀÛ¾÷ÀÌ´Ù. Ŭ¶óÀ̾ðÆ®°¡ ¼­¹ö¿¡°Ô º¸³»´Â ÀÚ·á´Â + ÀÔ·ÂÇÊÅÍ(input filter)°¡ ó¸®ÇÏ°í, ¼­¹ö°¡ + Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³»´Â ÀÚ·á´Â Ãâ·ÂÇÊÅÍ(output filter)°¡ + ó¸®ÇÑ´Ù. ÀÚ·á¿¡ ¿©·¯ ÇÊÅ͸¦ »ç¿ëÇÒ ¼ö ÀÖ°í, Á÷Á¢ ÇÊÅÍÀÇ + ¼ø¼­¸¦ ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +

¾ÆÆÄÄ¡´Â À̾î¹Þ±â(byte-range) ¿äû µîÀ» ó¸®ÇϱâÀ§ÇØ + ³»ºÎÀûÀ¸·Î ÇÊÅ͸¦ »ç¿ëÇÑ´Ù. ¶Ç, ¼³Á¤ Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© ¼±Åð¡´ÉÇÑ ÇÊÅ͸¦ Á¦°øÇÏ´Â ¸ðµâµµ ÀÖ´Ù. + SetInputFilter, + SetOutputFilter, + AddInputFilter, + AddOutputFilter, + RemoveInputFilter, + RemoveOutputFilter + Áö½Ã¾î·Î ÀڷḦ ó¸®ÇÏ´Â ÇÊÅ͸¦ Á¶ÀýÇÑ´Ù.

+ +

ÇöÀç ¾ÆÆÄÄ¡ À¥¼­¹ö ¹èÆ÷º»Àº »ç¿ëÀÚ°¡ ¼±ÅÃÇÒ ¼ö ÀÖ´Â ´ÙÀ½°ú + °°Àº ÇÊÅ͸¦ Á¦°øÇÑ´Ù.

+ +
+
INCLUDES
+
mod_include°¡ ó¸®ÇÏ´Â Server-Side Includes
+
DEFLATE
+
mod_deflate¸¦ »ç¿ëÇÏ¿© Ãâ·ÂÀ» + Ŭ¶óÀ̾ðÆ®·Î º¸³»±â Àü¿¡ ¾ÐÃà +
+
+ +

¶Ç, mod_ext_filter ¸ðµâÀ» »ç¿ëÇÏ¿© + ¿ÜºÎ ÇÁ·Î±×·¥À» ÇÊÅÍ·Î »ç¿ëÇÒ ¼öµµ ÀÖ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/glossary.html b/docs/manual/glossary.html new file mode 100644 index 00000000..1efee972 --- /dev/null +++ b/docs/manual/glossary.html @@ -0,0 +1,15 @@ +URI: glossary.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: glossary.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: glossary.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: glossary.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/glossary.html.de b/docs/manual/glossary.html.de new file mode 100644 index 00000000..3de21287 --- /dev/null +++ b/docs/manual/glossary.html.de @@ -0,0 +1,549 @@ + + + +Glossar - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Glossar

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ko 

+
+ +

Dieses Glossar erläutert einige gebräuchliche Fachbegriffe im + Zusammenhang mit dem Apache im Speziellen und Web-Diensten im + Allgemeinen. Weitere Informationen zum jeweiligen Begriff erreichen Sie + über die Links.

+
+
top
+
+

Definitionen

+ +
+
Algorithmus
+
Eine eindeutige Formel oder ein Satz von Regeln zur Lösung eines + Problems in einer endlichen Anzahl von Schritten. Algorithmen zur + Verschlüsselung werden üblicherweise Chiffre genannt. +
+ +
APache + eXtension Tool (apxs)
+
Ein Perl-Skript zur Kompilierung von Modul-Quelltexten zu Dynamic-Shared-Objects + (DSOs) und zur Installation dieser zum + Apache-Webserver.
+ Siehe: apxs-Dokumentation +
+ +
Apache Portable Runtime (APR)
+
Eine Menge von Bibliotheken, die viele grundlegende Schnittstellen + zwischen dem Server und dem Betriebssystem anbietet. Die APR + wird parallel zum Apache HTTP Server in einem eigenständigen Projekt + entwickelt.
+ Siehe auch: Apache Portable Runtime + Project +
+ +
Authentifizierung
+
Die positive Identifizierung einer Netzwerkeinheit, wie z.B. + eines Servers, eines Clients oder eines Benutzers.
+ Siehe: Authentisierung, Autorisierung und + Zugriffskontrolle +
+ +
Certification Authority + [səˈtifiˈkeiʃən + ɔːθɔriti] + (CA)
+
(Anm.d.Ü.: die Zertifizierungsstelle) Eine + vertrauenswürdige dritte Partei, deren Zweck es ist, + Zertifikate für Netzwerkeinheiten zu signieren. Andere + Netzwerkeinheiten können die Signatur prüfen, um + sicherzustellen, dass eine CA den Inhaber eines Zertifikats + authentifiziert hat.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Certificate Signing Request + [səˈtifikit sainiŋ + riˈkwest] (CSR)
+
(Anm.d.Ü.: Zertifikats-Signierungsanfrage) Ein unsigniertes + Zertifikat zur Einreichung bei + einer Zertifizierungsstelle, welche + es mit dem privaten Schlüssel + ihres CA-Zertifikats signiert. Durch die Signatur wird ein CSR + zum echten Zertifikat.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Chiffre
+
Die Chiffre ist ein Algorithmus oder System zur + Datenverschlüsselung. Beispiele sind DES, IDEA, RC4 usw. Im + Englischen spricht man von + Cipher [ˈsaifə]
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Chiffretext
+
Das Ergebnis, nachdem ein Klartext + eine Chiffre durchlaufen hat.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Common + Gateway Interface [ˈkɔmən geitwei + ˈintəːfeis] + (CGI)
+
Eine einheitliche Definition einer Schnittstelle zwischen einem + Webserver und einem externen Programm, welcher dem externen Programm die + Behandlung von Anfragen ermöglicht. Die Schnittstelle ist + ursprünglich von der NCSA + definiert worden. Es exisitert jedoch auch ein RFC-Projekt.
+ Siehe: Dynamische Inhalte mit CGI +
+ +
CONNECT + [kənekt]
+
Eine HTTP-Methode zur Weiterleitung + von Rohdaten über HTTP. Sie kann dazu verwendet werden, andere + Protokolle wie zum Beispiel das SSL-Protokoll zu kapseln. +
+ +
Digitale + Signatur
+
Ein chiffrierter Textblock, der die Gültigkeit eines Zertifikats + oder einer anderen Datei bestätigt. Eine Zertifizierungsstelle erstellt + eine digitale Signatur durch Generierung eines Hashs aus dem in einem Zertifikat + enthaltenen öffentlichen Schlüssel und + anschließender Codierung des Hashs mit dem privaten + Schlüssel des Zertifikats. Nur der öffentliche + Schlüssel der CA kann die Signatur decodieren. So wird + sichergestellt, dass die CA die Netwerkeinheit, welche das + Zertifikat besitzt, authentifiziert hat.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Direktive
+
Eine Konfigurationsanweisung, die das Verhalten des Apache in einem + oder mehreren Punkten steuert. Direktiven werden in den Konfigurationsdateien gesetzt.
+ Siehe: Verzeichnis der Direktiven +
+ +
Dynamic + Shared Object + [daiˈnæmik ʃɛəd + ˈɔbdʒikt] (DSO)
+
Separat von der Apache-Binärdatei httpd + kompilierte Module, die bei Bedarf + geladen werden können.
+ Siehe: Unterstützung für + Dynamic-Shared-Objects +
+ +
exportbeschränkt
+
Verminderte kryptografische Stärke (und Sicherheit), um den + Exportbesimmungen der Vereinigten Staaten (Anm.d.Ü.: konkret: United + States' Export Administration Regulations (EAR)) zu + entsprechen. Exportbeschränkte Verschlüsselungssoftware ist + auf eine kurze Schlüssellänge begrenzt, was zu + Chiffretexten führt, die gewöhnlich mittels + Brute-Force dekodiert werden können.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Filter
+
Ein Verfahren, dass auf vom Server empfangene oder zu sendende Daten + angewendet wird. Eingabefilter verarbeiten vom Client an den Server + gesendetet Daten, während Ausgabefilter vom Server an den Client zu + sendende Daten verarbeiten. Der Ausgabefilter INCLUDES + beispielsweise untersucht Dokumente nach Server-Side-Includes und führt sie aus.
+ Siehe: Filter +
+ +
Handler + [ˈhændlə]
+
Eine Apache-interne Darstellung der Aktion, die beim Aufruf einer + Datei auszuführen ist. Im Allgemeinen besitzen Dateien implizite, + auf dem Dateityp basierende Handler. Gewöhnlich werden alle Dateien + vom Server bedient, einige Dateitypen werden jedoch separat "behandelt" + (Anm.d.Ü.: besitzen einen separaten Handler). Der + cgi-script-Handler beispielsweise kennzeichnet Dateien, die + als CGI-Programme ausgeführt werden + sollen.
+ Siehe: Verwendung von Apache-Handlern +
+ +
Hash + [hæʃ]
+
Ein mathematischer, unumkehrbarer Einweg-Algorithmus zur Generierung + einer Zeichenfolge fester Länge aus einer anderen Zeichenfolge + beliebiger Länge. Unterschiedliche Zeichenfolgen bei der Eingabe + ergeben üblischerweise unterschiedliche Hashes (abhängig von + der Hash-Funktion). +
+ +
Header + [hedə]
+
Der Teil der HTTP-Anfrage und -Antwort, + der vor den eigentlichen Daten übermittelt wird und den Inhalt + beschreibende Meta-Informationen enthält. +
+ +
.htaccess
+
Eine Konfigurationsdatei, + die innerhalb des Web-Verzeichnisbaums abgelegt wird und zu dem + Verzeichnis, in dem sie abgelegt ist, sowie allen Unterverzeichnissen + Konfigurationsdirektiven + enthält. Trotz ihres Namens kann diese Datei nahezu alle Arten von + Direktiven enthalten, nicht nur Direktiven zur Zugriffskontrolle.
+ Siehe: Konfigurationsdateien +
+ +
httpd.conf
+
Die Haupt-Konfigurationsdatei ist + /usr/local/apache2/conf/httpd.conf. Dies kann aber zur + Laufzeit oder zur Kompilierungszeit anders konfiguriert werden.
+ Siehe: Konfigurationsdateien +
+ +
HTTPS
+
Das HyperText-Transfer-Protokoll (Secure), der + Standard-Verschlüsselungsmechanismus im World Wide Web. + Tatsächlich handelt es sich hierbei um HTTP über SSL.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
HyperText-Transfer-Protokoll + (HTTP)
+
Das Standard-Übertragungsprotokoll im World Wide Web. Der Apache + implementiert die Protokollversion 1.1, bezeichnet als HTTP/1.1 und + definiert in RFC 2616. +
+ +
Klartext
+
Der unverschlüsselte Text.
+ +
Konfigurationsanweisung
+
Siehe: Direktive
+ +
Konfigurationsdatei
+
Eine Textdatei mit Direktiven, + welche die Konfiguration des Apache steuern.
+ Siehe: Konfigurationsdateien +
+ +
Kontext
+
Ein Bereich in den Konfigurationsdateien, in dem + verschiedene Typen von Direktiven + erlaubt sind.
+ Siehe: Erklärung der + Fachbegriffe zu Apache-Direktiven +
+ +
Message-Digest + [ˈmesidʒ]
+
Ein Hash einer Nachricht, mit dem sich sicherstellen läßt, + dass der Inhalt der Nachricht während der Übertragung nicht + verändert wurde. (Anm.d.Ü.: ein so genannter Extrakt der + Nachricht)
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Methode
+
Im HTTP-Kontext eine in der + Anfrage(zeile) des Clients angegeben Aktion, die auf eine Ressource + angewendet wird. GET, POST und PUT + sind einige der verfügbaren HTTP-Methoden. +
+ +
MIME-Typ + [maim tyːp]
+
Eine Art und Weise, den Typ des übermittelten Dokuments zu + beschreiben. Sein Name leitet sich davon ab, dass sein Format den + Multipurpose Internet Mail Extensions entlehnt wurde. Er besteht aus + einem Haupttyp und einem Untertyp, getrennt durch einen + Schrägstrich. Einige Beispiele sind text/html, + image/gif und application/octet-stream. + Bei HTTP wird der MIME-Typ mit dem Header Content-Type + übermittelt.
+ Siehe: mod_mime +
+ +
Modul
+
Ein selbstständiger Teil eines Programms. Ein Großteil der + Funktionalität des Apache ist in Modulen enthalten, die Sie einbinden + oder entfernen können. In die Apache-Binärdatei httpd einkompilierte Module werden statische Module + genannt, während Module, die separat gespeichert sind und optional + zur Laufzeit geladen werden können, dynamische Module oder + DSOs genannt werden. + Standardmäßig eingebundene Module werden Basismodule + genannt. Für den Apache sind viele Module verfügbar, die nicht + als Bestandteil des Apache-HTTP-Server-Tarballs ausgeliefert + werden. Diese werden als Drittmodule bezeichnet.
+ Siehe: Modulverzeichnis +
+ +
Module-Magic-Number + [ˈmɔjuːl mædʒik + ˈnʌmbə] + (MMN)
+
Die Module-Magic-Number ist eine Konstante, die im Apache-Quelltext + definiert ist und im Zusammenhang mit der Binärkompatibilität + von Modulen steht. Sie wird geändert, wenn sich interne + Apache-Strukturen, -Funktionen oder andere signifikante Teile der API + derart ändern, dass eine Binärkompatibilität nicht mehr + gewährleistet werden kann. Bei einer MMN-Änderung müssen + alle Module von Drittanbietern zumindest neu kompiliert und zuweilen auch + geringfügig angepaßt werden, um mit der neuen Apache-Version zu + funktionieren. +
+ +
Öffentlicher + Schlüssel
+
Der öffentlich verfügbare Schlüssel in einem Public-Key-Kryptographie-System, + mit dem für seinen Eigentümer bestimmte Nachrichten + verschlüsselt und Signaturen von seinem Eigentümer + entschlüsselt werden.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
OpenSSL + [ˈəupənɛsɛsˈɛl] +
+
Das Open-Source-Toolkit für SSL/TLS
+ Siehe: http://www.openssl.org/ +
+ +
Passphrase + [paːfreiz]
+
Das Wort oder die Phrase, welches private Schlüssel-Dateien + schützt. Sie verhindert die Entschlüsselung durch nicht + authorisierte Benutzer. Normalerweise ist dies einfach der geheimen + (De-)Codierungsschlüssel, der für Chiffren verwendet wird.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Privater Schlüssel
+
Der geheime Schlüssel in einem Public-Key-Kryptographie-System, + mit dem hereinkommende Nachrichten decodiert und ausgehende signiert + werden.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Proxy
+
Ein zwischen dem Client und dem ursprünglichen Server + (Anm.d.Ü.: der Server, den der Client tatsächlich erreichen + möchte) liegender Server. Er nimmt Anfragen von + Clients entgegen, übermittelt diese Anfragen dem + ursprünglichen Server und liefert die Antwort des + ursprünglichen Servers an den Client zurück. Wenn mehrere + Clients den gleichen Inhalt abfragen, dann kann der Proxy diesen Inhalt + aus seinem Zwischenspeicher ausliefern, anstatt ihn jedesmal vom + ursprünglichen Server anzufordern, und dadurch die Antwortzeit + verringern.
+ Siehe: mod_proxy +
+ +
Public-Key-Kryptographie + [ˈpʌblik kiː + ˈkyptograˈfiː]
+
Theorie und Anwendung asymmetrischer Verschlüsselungssysteme, + die einen Schlüssel zur Verschlüsselung und einen anderen zur + Entschlüsselung verwenden. Zwei derart zusammengehörende + Schlüssel bilden Schüsselpaar. Man spricht auch von + "Asymetrischer Kryptographie".
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Regulärer + Ausdruck (Regex)
+
Eine Form, ein Muster im Text zu beschreiben - zum Beispiel: "alle + Wörter, die mit dem Buchstaben A beginnen" oder "Jeder Satz mit + zwei Kommata und ohne großes Q". Beim Apache sind reguläre + Ausdrücke hilfreich, da sie auf sehr flexible Art und Weise die + Anwendung bestimmter Eigenschaften auf eine Auswahl von Dateien oder + Ressourcen ermöglichen. - Zum Beispiel können alle .gif- und + .jpg-Dateien eines Verzeichnis "images" mit + "/images/.*(jpg|gif)$" beschrieben werden. Der Apache + verwendet Perl-kompatible reguläre Ausdrücke, wie sie die + PCRE-Bibliothek bereitstellt. +
+ +
Reverse Proxy + [riːvəːs + ˈprɔksi]
+
Ein Proxy-Server, der dem Client + gegenüber als ursprünglicher Server erscheint. Dies + ist nützlich, um den tatsächlichen Server aus + Sicherheitsgründen oder zur Lastverteilung vor dem Client zu + verstecken. +
+ +
Secure Sockets + Layer [siˈkjuə ˈsɔkits + ˈleiə] (SSL)
+
Ein von der Firma Netscape Communications Corporation entwickeltes + Protokoll zur allgemeinen Authentisierung und Verschlüsselung der + Kommunikation über TCP/IP-Netzwerke. Die meistverbreitete Nutzung + ist HTTPS, d.h. HyperText Transfer Protocol (HTTP) über + SSL.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Server Side + Includes [səːə said + inˈkluːds] (SSI)
+
Eine Technik zum Einbetten von weiterverarbeitenden Anweisungen in + HMTL-Dateien.
+ Siehe: Einführung in Server Side + Includes +
+ +
Session + [ˈseʃən]
+
Allgemein der Kontext einer Kommunikation.
+ +
SSLeay
+
Die Bibliothek der Original-SSL/TLS-Implementation von Eric A. + Young
+ +
Symmetrische Kryptographie
+
Die Theorie und Anwendung von Chiffren, die einen einzigen + geheimen Schlüssel sowohl zur Verschlüsswelung als auch zur + Entschlüsselung benutzen.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Tarball + [taːbɔːl]
+
Ein Paket von Dateien, die mit dem Hilfsprogramm tar + zusammengefasst wurden. Apache-Distributionen werden in komprimierten + tar-Archiven oder unter Verwendung von pkzip gespeichert. +
+ +
Transport + Layer Security [trænsˈpɔːt + ˈeiə siˈkjuəriti] + (TLS)
+
Das SSL-Nachfolgeprotokoll, das von der Internet Engineering Task + Force (IETF) zur allgemeinen Authentisierung und Verschlüsselung + einer Kommunikation über TCP/IP-Netzwerke entwickelt worden ist. + TLS Version 1 ist nahezu identisch mit SSL Version 3.
+ Siehe: SSL/TLS-Verschlüsseliung +
+ +
Umgebungsvariable (env-Variable)
+
Benannte, von der Betriebssystem-Shell verwaltete Variablen zur + Speicherung von Informationen und zur Kommunikation zwischen Programmen. + Der Apache beinhaltet auch interne Variablen, die ebenfalls + Umgebungsvariablen genannt werden, die aber statt in der + Shell-Umgebung in internen Apache-Strukturen gespeichert sind.
+ Siehe: Umgebungsvariablen im Apache +
+ +
Uniform + Resource Locator [ˈjuːnifɔːm + riˈsɔːs ləuˈkeitə] + (URL)
+
Der Name bzw. die Adresse einer Ressource im Internet. Dies ist der + allgemein gebräuchliche Audruck für die formale Bezeichnung + Uniform Resource + Identifier. URLs bestehen üblicherweise aus einem + Schema wie http oder https, einem Hostnamen + und einem Pfad. Die URL für diese Seite könnte + http://httpd.apache.org/docs/2.2/glossary.html + lauten. +
+ +
Uniform Resource Identifier + [ˈjuːnifɔːm + riˈsɔːs aiˈdentifaiə] + (URI)
+
Eine kompakte Zeichenfolge zur Identifizierung einer abstrakten oder + physischen Ressource. Er wird in dem RFC 2396 formell + definiert. Im World Wide Web verwendete URIs werden üblicherweise + als URLs bezeichnet. +
+ +
Virtual-Hosting + [vəˈtjuəl + həustiŋ]
+
Die Bedienung mehrere Websites mit einer einzigen Apache-Instanz. + IP-basierte virtuelle Hosts unterscheiden zwischen + verschiedenen Websites aufgrund ihrer IP-Adressen, während + namensbasierte virtuelle Hosts nur den Namen des Hosts + verwenden und daher mehrere Angebote unter der gleichen IP-Adresse + hosten können.
+ Siehe: Apache-Dokumentation zu virtuellen + Hosts +
+ +
Voll-qualifizierter Domainname + (FQDN)
+
Der eindeutige Name einer Netzwerkeinheit, bestehend aus einem + Hostnamen und dem Domainnamen, welcher zu einer IP-Adresse + aufgelöst werden kann. Zum Beispiel ist www ein + Hostname, example.com ein Domainname und + www.example.com ein voll-qualifizierter Domainname. +
+ + +
Website + [websait]
+
Im Gegensatz zur Webseite, die einer konkreten URL entspricht, ist mit + Website ein komplettes Angebot unter einem bestimmten Hostnamen (und Port) + gemeint. Dieses kann aus vielen verschiedenen Webseiten bestehen. +
+ +
X.509
+
Ein von der International Telecommunication Union (ITU-T) empfohlenes + Schema für Authentifizierungszertifikate. Es wird für + SSL/TLS-Authentifizierungen verwendet.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Zertifikat
+
Ein Datensatz zur Authentisierung einer + Nertzwerkeinheit wie Server oder Client. Ein Zertifikat + enthält X.509-Informationen + über seinen Eigentümer (das sogenannte Betreff + (Anm.d.Ü.: engl.: subject)) und die + signierende Certification + Authority (der sogenannte Aussteller (Anm.d.Ü.: engl.: + issuer)) sowie den öffentlichen Schlüssel des + Eigentümers und die Signatur der CA. Netzwerkeinheiten + überprüfen diese Signatur mit Hilfe von CA-Zertifikaten.
+ Siehe: SSL/TLS-Verschlüsselung +
+ +
Zugriffskontrolle
+
Die Beschränkung des Zugriffs auf Netzwerkbereiche. Im + Apache-Kontext in der Regel die Zugriffsbeschränkung auf bestimmte + URLs.
+ Siehe: Authentisierung, Autorisierung und + Zugriffskontrolle +
+
+
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/glossary.html.en b/docs/manual/glossary.html.en new file mode 100644 index 00000000..ee3836f7 --- /dev/null +++ b/docs/manual/glossary.html.en @@ -0,0 +1,456 @@ + + + +Glossary - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Glossary

+
+

Available Languages:  de  | + en  | + es  | + ko 

+
+ +

This glossary defines some of the common terminology related to Apache in + particular, and web serving in general. More information on each concept + is provided in the links.

+
+
top
+
+

Definitions

+ +
+
Access Control
+
The restriction of access to network realms. In an Apache context + usually the restriction of access to certain URLs.
See: Authentication, Authorization, and Access + Control +
+ +
Algorithm
+ +
An unambiguous formula or set of rules for solving a problem in a finite + number of steps. Algorithms for encryption are usually called + Ciphers. +
+ +
APache + eXtension Tool (apxs)
+
A perl script that aids in compiling module sources into Dynamic Shared Objects + (DSOs) and helps install them in the + Apache Web server.
+ See: Manual Page: apxs +
+ +
Apache Portable Runtime (APR)
+
A set of libraries providing many of the basic interfaces + between the server and the operating system. APR is developed + parallel to the Apache HTTP Server as an independent project.
+ See: Apache Portable Runtime + Project +
+ +
Authentication
+
The positive identification of a network entity such as a server, a + client, or a user.
+ See: Authentication, Authorization, and Access + Control +
+ +
Certificate
+
A data record used for authenticating network entities such + as a server or a client. A certificate contains X.509 information pieces + about its owner (called the subject) and the signing Certification Authority (called + the issuer), plus the owner's public + key and the + signature made by the CA. Network entities verify these signatures + using CA certificates.
+ See: SSL/TLS Encryption +
+ +
Certificate Signing Request + (CSR)
+
An unsigned certificate for + submission to a Certification + Authority, which signs it with the Private Key of their CA + Certificate. Once the CSR is signed, it becomes a real + certificate.
+ See: SSL/TLS Encryption +
+ +
Certification Authority + (CA)
+
A trusted third party whose purpose is to sign certificates for network + entities it has authenticated using secure means. Other network entities + can check the signature to verify that a CA has authenticated the bearer + of a certificate.
+ See: SSL/TLS Encryption +
+ +
Cipher
+
An algorithm or system for data encryption. Examples are DES, IDEA, RC4, + etc.
+ See: SSL/TLS Encryption +
+ +
Ciphertext
+
The result after Plaintext is + passed through a Cipher.
See: SSL/TLS Encryption +
+ +
Common + Gateway Interface (CGI)
+
A standard definition for an interface between a web server and an + external program that allows the external program to service requests. + The interface was originally defined by NCSA but there + is also an RFC project.
+ See: Dynamic Content with CGI +
+ +
Configuration Directive
+
See: Directive
+ +
Configuration + File
+
A text file containing Directives + that control the configuration of Apache.
+ See: Configuration Files +
+ +
CONNECT
+
An HTTP method for proxying raw data + channels over HTTP. It can be used to encapsulate other protocols, such as + the SSL protocol. +
+ +
Context
+
An area in the configuration + files where certain types of directives are allowed.
+ See: Terms Used to Describe + Apache Directives +
+ +
Digital + Signature
+
An encrypted text block that validates a certificate or other file. A + Certification Authority + creates a signature by generating a hash of the Public Key + embedded in a Certificate, then encrypting the hash with its own + Private Key. Only the CA's public key can decrypt the signature, + verifying that the CA has authenticated the network entity that owns the + Certificate.
+ See: SSL/TLS Encryption +
+ +
Directive
+
A configuration command that controls one or more aspects of Apache's + behavior. Directives are placed in the Configuration File
+ See: Directive Index +
+ +
Dynamic + Shared Object (DSO)
+
Modules compiled separately from the + Apache httpd binary that can be loaded on-demand.
+ See: Dynamic Shared Object Support +
+ +
Environment + Variable (env-variable)
+
Named variables managed by the operating system shell and used to store + information and communicate between programs. Apache also contains + internal variables that are referred to as environment variables, but are + stored in internal Apache structures, rather than in the shell + environment.
+ See: Environment Variables in Apache +
+ +
Export-Crippled
+
Diminished in cryptographic strength (and security) in order to comply + with the United States' Export Administration Regulations (EAR). + Export-crippled cryptographic software is limited to a small key size, + resulting in Ciphertext which usually can be decrypted by brute + force.
+ See: SSL/TLS Encryption +
+ +
Filter
+
A process that is applied to data that is sent or received by the + server. Input filters process data sent by the client to the server, + while output filters process documents on the server before they are sent + to the client. For example, the INCLUDES output filter + processes documents for Server Side + Includes.
+ See: Filters +
+ +
Fully-Qualified Domain-Name + (FQDN)
+
The unique name of a network entity, consisting of a hostname and a + domain name that can resolve to an IP address. For example, + www is a hostname, example.com is a domain name, + and www.example.com is a fully-qualified domain name. +
+ +
Handler
+
An internal Apache representation of the action to be performed when a + file is called. Generally, files have implicit handlers, based on the file + type. Normally, all files are simply served by the server, but certain + file types are "handled" separately. For example, the + cgi-script handler designates files to be processed as + CGIs.
+ See: Apache's Handler Use +
+ +
Hash
+
A mathematical one-way, irreversable algorithm generating a string with + fixed-length from another string of any length. Different input strings + will usually produce different hashes (depending on the hash function). +
+ +
Header
+
The part of the HTTP request and + response that is sent before the actual content, and that contains + meta-information describing the content. +
+ +
.htaccess
+
A configuration file that + is placed inside the web tree and applies configuration directives to the directory where it is + placed and all sub-directories. Despite its name, this file can hold + almost any type of directive, not just access-control directives.
+ See: Configuration Files +
+ +
httpd.conf
+
The main Apache configuration + file. The default location is + /usr/local/apache2/conf/httpd.conf, but it may be moved using + run-time or compile-time configuration.
+ See: Configuration Files +
+ +
HyperText Transfer Protocol + (HTTP)
+
The standard transmission protocol used on the World Wide Web. Apache + implements version 1.1 of the protocol, referred to as HTTP/1.1 and + defined by RFC 2616. +
+ +
HTTPS
+
The HyperText Transfer Protocol (Secure), the standard encrypted + communication mechanism on the World Wide Web. This is actually just HTTP + over SSL.
+ See: SSL/TLS Encryption +
+ +
Method
+
In the context of HTTP, an action to + perform on a resource, specified on the request line by the client. Some + of the methods available in HTTP are GET, POST, + and PUT. +
+ +
Message Digest
+
A hash of a message, which can be used to verify that the contents of + the message have not been altered in transit.
+ See: SSL/TLS Encryption +
+ +
MIME-type
+
A way to describe the kind of document being transmitted. Its name + comes from that fact that its format is borrowed from the Multipurpose + Internet Mail Extensions. It consists of a major type and a minor type, + separated by a slash. Some examples are text/html, + image/gif, and application/octet-stream. In + HTTP, the MIME-type is transmitted in the Content-Type + header.
+ See: mod_mime +
+ +
Module
+
An independent part of a program. Much of Apache's functionality is + contained in modules that you can choose to include or exclude. Modules + that are compiled into the Apache httpd binary are + called static modules, while modules that are stored + separately and can be optionally loaded at run-time are called + dynamic modules or DSOs. + Modules that are included by default + are called base modules. Many modules are available for Apache + that are not distributed as part of the Apache HTTP Server tarball. These are referred to as + third-party modules.
+ See: Module Index +
+ +
Module Magic + Number (MMN)
+
Module Magic Number is a constant defined in the Apache source code that + is associated with binary compatibility of modules. It is changed when + internal Apache structures, function calls and other significant parts of + API change in such a way that binary compatibility cannot be guaranteed + any more. On MMN change, all third party modules have to be at least + recompiled, sometimes even slightly changed in order to work with the new + version of Apache. +
+ +
OpenSSL
+
The Open Source toolkit for SSL/TLS
+ See http://www.openssl.org/# +
+ +
Pass Phrase
+
The word or phrase that protects private key files. It prevents + unauthorized users from encrypting them. Usually it's just the secret + encryption/decryption key used for Ciphers.
+ See: SSL/TLS Encryption +
+ +
Plaintext
+
The unencrypted text.
+ +
Private Key
+
The secret key in a Public Key + Cryptography system, used to decrypt incoming messages and + sign outgoing ones.
+ See: SSL/TLS Encryption +
+ +
Proxy
+
An intermediate server that sits between the client and the origin + server. It accepts requests from clients, transmits those requests + on to the origin server, and then returns the response from the origin + server to the client. If several clients request the same content, the + proxy can deliver that content from its cache, rather than requesting it + from the origin server each time, thereby reducing response time.
+ See: mod_proxy +
+ +
Public Key
+
The publicly available key in a Public Key Cryptography system, + used to encrypt messages bound for its owner and to decrypt signatures + made by its owner.
+ See: SSL/TLS Encryption +
+ +
Public Key Cryptography
+
The study and application of asymmetric encryption systems, which use + one key for encryption and another for decryption. A corresponding pair of + such keys constitutes a key pair. Also called Asymmetric Cryptography. +
+ See: SSL/TLS Encryption +
+ +
Regular Expression + (Regex)
+
A way of describing a pattern in text - for example, "all the words that + begin with the letter A" or "every 10-digit phone number" or even "Every + sentence with two commas in it, and no capital letter Q". Regular + expressions are useful in Apache because they let you apply certain + attributes against collections of files or resources in very flexible ways + - for example, all .gif and .jpg files under any "images" directory could + be written as "/images/.*(jpg|gif)$". Apache uses Perl + Compatible Regular Expressions provided by the PCRE library. +
+ +
Reverse Proxy
+
A proxy server that appears to the client + as if it is an origin server. This is useful to hide the real + origin server from the client for security reasons, or to load balance. +
+ +
Secure Sockets + Layer (SSL)
+
A protocol created by Netscape Communications Corporation for general + communication authentication and encryption over TCP/IP networks. The most + popular usage is HTTPS, i.e. the HyperText Transfer Protocol (HTTP) + over SSL.
+ See: SSL/TLS Encryption +
+ +
Server Side + Includes (SSI)
+
A technique for embedding processing directives inside HTML files.
+ See: Introduction to Server Side Includes +
+ +
Session
+
The context information of a communication in general.
+ +
SSLeay
+
The original SSL/TLS implementation library developed by Eric A. + Young +
+ +
Symmetric + Cryptography
+
The study and application of Ciphers that use a single secret key + for both encryption and decryption operations.
+ See: SSL/TLS Encryption +
+ +
Tarball
+
A package of files gathered together using the tar utility. + Apache distributions are stored in compressed tar archives or using + pkzip. +
+ +
Transport + Layer Security (TLS)
+
The successor protocol to SSL, created by the Internet Engineering Task + Force (IETF) for general communication authentication and encryption over + TCP/IP networks. TLS version 1 and is nearly identical with SSL version + 3.
+ See: SSL/TLS Encryption +
+ +
Uniform + Resource Locator (URL)
+
The name/address of a resource on the Internet. This is the common + informal term for what is formally called a Uniform Resource Identifier. + URLs are usually made up of a scheme, like http or + https, a hostname, and a path. A URL for this page might + be http://httpd.apache.org/docs/2.2/glossary.html. +
+ +
Uniform Resource Identifier + (URI)
+
A compact string of characters for identifying an abstract or physical + resource. It is formally defined by RFC 2396. URIs used on the + world-wide web are commonly referred to as URLs. +
+ +
Virtual Hosting
+
Serving multiple websites using a single instance of Apache. IP + virtual hosting differentiates between websites based on their IP + address, while name-based virtual hosting uses only the name of the + host and can therefore host many sites on the same IP address.
+ See: Apache Virtual Host documentation +
+ +
X.509
+
An authentication certificate scheme recommended by the International + Telecommunication Union (ITU-T) which is used for SSL/TLS authentication.
See: SSL/TLS Encryption +
+
+
+
+

Available Languages:  de  | + en  | + es  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/glossary.html.es b/docs/manual/glossary.html.es new file mode 100644 index 00000000..3607ae99 --- /dev/null +++ b/docs/manual/glossary.html.es @@ -0,0 +1,395 @@ + + + +Glosario - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

Glosario

+
+

Idiomas disponibles:  de  | + en  | + es  | + ko 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ +

Este glosario define la terminología más común +relacionada con Apache en particular y con los servidores web en +general. En los enlaces que hay asociados a cada término se puede +encontrar información más detallada.

+
+
top
+
+

Definiciones

+ +
+
Autentificación
La +identificación positiva de una entidad de red tal como un +servidor, un cliente, o un usuario.
Consulte: Autentificación, Autorización, y +Control de Acceso
+ +
Control de Acceso
La +restricción en el acceso al entorno de una red. En el contexto de +Apache significa normalmente la restricción en el acceso a +ciertas URLs.
Consulte: Autentificación, Autorización, y +Control de Acceso
+ +
Algoritmo
Un proceso definido sin +ambiguedades o un conjunto de reglas para solucionar un problema en un +número finito de pasos. Los algoritmos para encriptar se llaman +normalmente algoritmos de cifrado.
+ +
Herramienta de extensión de +Apache (apxs)
Es un script escrito en +Perl que ayuda a compilar el código fuente de algunos módulos para convertirlos en Objetos Dinamicos +Compartidos (DSOs) y ayuda a instalarlos en el +servidor web Apache.
Consulte: Paginas de Ayuda: apxs
+ +
Certificado
+ +
Una información que se almacena para autentificar entidades + de red tales como un servidor o un cliente. Un certificado + contiene piezas de información X.509 sobre su poseedor + (llamado sujeto) y sobre la Autoridad Certificadora + (llamada el expendedor) que lo firma, más la clave publica del propietario y la firma de + la AC. Las entidades de red verifican las firmas usando + certificados de las AC.
+ +Consulte: Encriptado SSL/TLS
+ +
Autoridad Certificadora (CA)
Una entidad externa de confianza cuyo fin +es firmar certificados para las entidades de red que ha autentificado +usando medios seguros. Otras entidades de red pueden verificar la +firma para comprobar que una Autoridad Certificadora ha autentificado +al poseedor del certificado.
Consulte: Encriptado +SSL/TLS
+ +
Petición de firma de +Certificado (CSR)
Es la petición a +una Autoridad Certificadora para +que firme un certificado aún sin +firmar. La Autoridad Certificadora firma el Certificado con +la Clave Privada de su certificado de Autoridad Certificadora. Una +vez que el CSR está firmado, se convierte en un auténtico +certificado.
Consulte: Encriptado +SSL/TLS
+ + +
Algoritmo de cifrado
Es un algoritmo +o sistema de encriptado de información. Ejemplos de estos +algoritmos son DES, IDEA, RC4, etc.
Consulte: Encriptado SSL/TLS
+ +
Texto cifrado
El resultado de +haber aplicado a un texto sin cifrar un algoritmo de cifrado.
Consultar: Encriptado SSL/TLS
+ +
Common Gateway Interface (CGI)
Una definición estándar para +un interfaz entre un servidor web y un programa externo que permite +hacer peticiones de servicio a los programas externos. Este interfaz +fue definido originalmente por la NCSA pero +tambien hay un proyecto RFC.
Consulte: Contenido Dinámico con CGI
+ + +
Directivas de +configuración
Consulte: Directivas
+ +
Fichero de Configuración
+
Un fichero de texto que contiene Directivas que controlan la configuración +de Apache.
Consulte: Ficheros de +Configuración
+ +
CONNECT
Un método de HTTP para hacer proxy a canales de +datos sin usar HTTP. Puede usarse para encapsular otros protocolos, +tales como el protocolo SSL.
+ +
Contexto
Un área en los ficheros de configuración donde +están permitidos ciertos tipos de directivas.
Consulte: Terminos usados para describir +las directivas de Apache
+ +
Firma Digital
Un bloque de +texto encriptado que verifica la validez de un certificado o de otro +fichero. Una Autoridad +Certificadora crea una firma generando un hash a partir de la +Clave Pública que lleva incorporada en un +Certificado, después encriptando el hash con su propia +Clave Privada. Solo las claves públicas de las CAs +pueden desencriptar la firma, verificando que la CA ha autentificado a +la entidad de red propietaria del Certificado.
+Consulte: Encriptado SSL/TLS
+ +
Directiva
Un comando de +configuración que controla uno o más aspectos del +comportamiento de Apache. Las directivas se ponen en el Fichero de Configuración
+Consulte: Índice de +Directivas
+ +
Objetos Dinámicos +Compartidos (DSO)
Los Módulos compilados de forma separada al +binario httpd de Apache se pueden cargar según se necesiten.
Consulte: Soporte de Objetos Dinámicos +Compartidos
+ +
Variable de Entorno (env-variable)
Variables que +gestionan el shell del sistema operativo y que se usan para guardar +información y para la comunicación entre programas. Apache +también contiene variables internas que son referidas como +variables de entorno, pero que son almacenadas en las estructuras +internas de Apache, en lugar de en el entorno del shell.
+Consulte: Variables de entorno de Apache
+ +
Export-Crippled
+
Disminución de la fortaleza criptográfica (y seguridad) +para cumplir con las Regulaciones sobre Exportación de la +Administracción de los Estados Unidos (EAR). El software +criptográfico Export-crippled está limitado a una clave de +pequeño tamaño, de tal manera que el texto cifrado +que se consigue con él, puede desencriptarse por fuerza bruta.
Consulte: Encriptado SSL/TLS
+ +
Filtro
Un proceso que se aplica a la +información que es enviada o recibida por el servidor. Los +ficheros de entrada procesan la información enviada por un +cliente al servidor, mientras que los filtros de salida procesan la +información en el servidor antes de enviársela al +cliente. Por ejemplo, el filtro de salida INCLUDES +procesa documentos para Server Side Includes.
+Consulte: Filtros
+ +
Nombre de dominio +completamente qualificado (FQDN)
El +nombre único de una entidad de red, que consiste en un nombre de +host y un nombre de dominio que puede traducirse a una dirección +IP. Por ejemplo, www es un nombre de host, +example.com es un nombre de dominio, y +www.example.com es un nombre de dominio completamente +qualificado.
+ +
Handler
Es una representación +interna de Apache de una acción a ser ejecutada cuando se llama a +un fichero. Generalmente, los ficheros tienen un handler +implícito, basado en el tipo de fichero. Normalmente, todos los +ficheros son simplemente servidos por el servidor, pero sobre algunos +tipos de ficheros se ejecutan acciones complementarias. Por ejemplo, +el handler cgi-script designa los ficheros a ser +procesados como CGIs.
Consulte: Uso de Handlers en Apache
+ +
Cabecera
La parte de la +petición y la respuesta HTTP que se +envía antes del contenido propiamente dicho, y que contiene +meta-información describiendo el contenido.
+ +
.htaccess
Un fichero de configuración que se +pone dentro de la estructura de directorios del sitio web y aplica directivas de configuración al directorio +en el que está y a sus subdirectorios. A pesar de su nombre, este +fichero puede contener cualquier tipo de directivas, no solo +directivas de control de acceso.
Consulte: Ficheros de Configuración
+ +
httpd.conf
Es el fichero de configuración principal +de Apache. Su ubicación por defecto es +/usr/local/apache2/conf/httpd.conf, pero puede moverse +usando opciones de configuración al compilar o al iniciar +Apache.
Consulte: Ficheros de +Configuración
+ +
Protocolo de Tranferencia de +Hipertexto (HTTP)
Es el protocolo de +transmisión estádar usado en la World Wide Web. Apache +implementa la versión 1.1 de este protocolo, al que se hace +referencia como HTTP/1.1 y definido por el RFC 2616.
+ +
HTTPS
Protocolo de transferencia de +Hipertext (Seguro), es el mecanismo de comunicación encriptado +estándar en World Wide Web. En realidad es HTTP sobre SSL.
Consulte: Encriptado +SSL/TLS
+ +
Método
En el contexto de HTTP, es una acción a ejecutar sobre un recurso, +especificado en la líneas de petición por el cliente. +Algunos de los metodos diponibles en HTTP son GET, +POST, y PUT.
+ +
Message Digest
Un hash de un +mensaje, el cual pude ser usado para verificar que el contenido del +mensaje no ha sido alterado durante la transmisión.
+Consulte: Encriptado SSL/TLS
+ +
MIME-type
Una manera de describir +el tipo de documento a ser transmitido. Su nombre viene del hecho de +que su formato se toma de las Extensiones del Multipurpose Internet +Mail. Consiste en dos componentes, uno principal y otro secundario, +separados por una barra. Algunos ejemplos son text/html, +image/gif, y application/octet-stream. En +HTTP, el tipo MIME se transmite en la cabecera +del Tipo Contenido.
Consulte: mod_mime
+ +
Módulo
Una parte independiente +de un programa. La mayor parte de la funcionalidad de Apache +está contenida en módulos que pueden incluirse o excluirse. +Los módulos que se compilan con el binario httpd de Apache se +llaman módulos estáticos, mientras que los que se +almacenan de forma separada y pueden ser cargados de forma opcional, +se llaman módulos dinamicos o DSOs. +Los módulos que están incluidos por sefecto de llaman +módulos base. Hay muchos módulos disponibles para +Apache que no se distribuyen con la tarball del +Servidor HTTP Apache . Estos módulos son llamados +módulos de terceros.
Consulte: Índice de Módulos
+ +
Número Mágico de +Módulo (MMN)
El número +mágico de módulo es una constante definida en el código +fuente de Apache que está asociado con la compatibilidad binaria +de los módulos. Ese número cambia cuando cambian las +estructuras internas de Apache, las llamadas a funciones y otras +partes significativas de la interfaz de programación de manera +que la compatibilidad binaria no puede garantizarse sin cambiarlo. Si +cambia el número mágico de módulo, todos los +módulos de terceros tienen que ser al menos recompilados, y +algunas veces, incluso hay que introducir ligeras modificaciones para +que funcionen con la nueva versión de Apache
+ +
OpenSSL
+
El toolkit Open Source para SSL/TLS
+ see http://www.openssl.org/
+ +
Pass Phrase
La palabra o frase +que protege los archivos de clave privada. Evita que usuarios no +autorizados los encripten. Normalmente es solo la clave de +encriptado/desencriptado usada por los Algoritmos de +Cifrado.
Consulte: Encriptado +SSL/TLS
+ +
Plaintext
+
Un texto no encriptado.
+ +
Clave Privada
La clave secreta +de un sistema criptográfico de +Clave Pública, usada para desencriptar los mensajes entrantes +y firmar los salientes.
Consulte: Encriptado +SSL/TLS
+ +
Proxy
Un servidor intermedio que se +pone entre el cliente y el servidor de origen. Acepta las +peticiones de los clientes, las transmite al servidor de origen, y +después devuelve la respuesta del servidor de origen al +cliente. Si varios clientes piden el mismo contenido, el proxy sirve +el contenido desde su caché, en lugar de pedirlo cada vez que lo +necesita al servidor de origen, reduciendo con esto el tiempo de +respuesta.
Consulte: mod_proxy
+ +
Clave Publica
La clave disponible +públicamente en un sistema +criptográfico de Clave Pública, usado para encriptar +mensajes destinados a su propietario y para desencriptar firmas hechas +por su propietario.
Consulte: Encriptado +SSL/TLS
+ +
Criptográfia de Clave +Pública
El estudio y aplicación de sistemas de +encriptado asimétricos, que usa una clave para encriptar y otra +para desencriptar. Una clave de cada uno de estos tipos constituye un +par de claves. Tambien se llama Criptografia Asimétrica.
+Consulte: Encriptado SSL/TLS
+ +
Expresiones Regulares (Regex)
Una forma de describir un modelo de +texto - por ejemplo, "todas las palabras que empiezan con la letra "A" +o "todos los números de teléfono que contienen 10 +dígitos" o incluso "Todas las frases entre comas, y que no +contengan ninguna letra Q". Las Expresiones Regulares son utiles en +Apache porque permiten aplicar ciertos atributos a colecciones de +ficheros o recursos de una forma flexible - por ejemplo, todos los +archivos .gif y .jpg que estén en un directorio "imágenes" +podrían ser escritos como "/images/.*(jpg|gif)$". +Apache usa Expresiones Regulares compatibles con Perl gracias a la +librería PCRE.
+ +
Reverse Proxy
Es un servidor +proxy que se presenta al cliente como si fuera un +servidor de origen. Es útil para esconder el +auténtico servidor de origen a los clientes por cuestiones de +seguridad, o para equilibrar la carga.
+ +
Secure Sockets Layer (SSL)
Un protocolo creado por Netscape +Communications Corporation para la autentificación en +comunicaciones en general y encriptado sobre redes TCP/IP. Su +aplicación más popular es HTTPS, el Protocolo de +Transferencia de Hipertexto (HTTP) sobre SSL.
Consulte: Encriptado SSL/TLS
+ +
Server Side Includes (SSI)
Una tecnica para incluir directivas de +proceso en archivos HTML.
Consulte: Introducción al Server Side +Includes
+ +
Sesion
Información del +contexto de una comunicación en general.
+ +
SSLeay
La implementación +original de la librería SSL/TLS desarrollada por Eric +A. Young
+ +
Criptografía +Simétrica
El estudio y aplicación de +Algoritmos de Cifrado que usan una solo clave secreta tanto +para encriptar como para desencriptar.
Consulte: Encriptado SSL/TLS
+ +
Tarball
Un grupo de ficheros +puestos en un solo paquete usando la utilidad tar. Las +distribuciones Apache se almacenan en ficheros comprimidos con tar o +con pkzip.
+ +
Transport Layer Security (TLS)
Es el sucesor del protocolo SSL, creado +por el Internet Engineering Task Force (IETF) para la +autentificación en comunicaciones en general y encriptado sobre +redes TCP/IP. La versión 1 de TLS es casi idéntica a la +versión 3 de SSL.
Consulte: Encriptado +SSL/TLS
+ +
Localizador de Recursos +Uniforme (URL)
El nombre de un recurso +en Internet. Es la manera informal de decir lo que formalmente se +llama un Identificador de +Recursos Uniforme. Las URLs están compuestas normalmente por +un esquema, tal como http o https, un nombre +de host, y una ruta. Una URL para esta página es +http://httpd.apache.org/docs/2.2/glossary.html.
+ +
Identificador de Recursos +Uniforme (URI)
Una cadena de caracteres +compacta para identificar un recurso físico o abstracto. Se +define formalmente en la RFC 2396. Los URIs que +se usan en world-wide web se refieren normalmente como URLs.
+ +
Hosting Virtual
Se trata de +servir diferentes sitios web con una sola entidad de Apache. El +hosting virtual de IPs diferencia los sitios web basandose en sus +direcciones IP, mientras que el hosting virtual basado en +nombres usa solo el nombre del host y de esta manera puede alojar +muchos sitios web con la misma dirección IP.
Consulte: Documentación sobre Hosting Virtual en +Apache
+ +
X.509
Un esquema de certificado de +autentificación recomendado por la International +Telecommunication Union (ITU-T) que se usa en la autentificación +SSL/TLS.
Consulte: Encriptado SSL/TLS
+ +
+
+
+

Idiomas disponibles:  de  | + en  | + es  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/glossary.html.ko.euc-kr b/docs/manual/glossary.html.ko.euc-kr new file mode 100644 index 00000000..7892f1dc --- /dev/null +++ b/docs/manual/glossary.html.ko.euc-kr @@ -0,0 +1,364 @@ + + + +¿ë¾î - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¿ë¾î

+
+

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

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

ÀÌ ¹®¼­´Â À¥ ¼­ºñ½º ÀϹݿ¡ ´ëÇÑ, ƯÈ÷ ¾ÆÆÄÄ¡¿Í °ü·ÃµÈ, ¿ë¾îµéÀ» +Á¤ÀÇÇÑ´Ù. °¢ °³³ä¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ Á¤º¸´Â ¸µÅ©¸¦ Âü°íÇ϶ó. +(¿ªÁÖ; ÇöÀç ´Ü¾îÀÇ ¼ø¼­´Â ÇÑ±Û ¼ø¼­°¡ ¾Æ´Ï¶ó, ¿µ¹®ÀÚ +¼ø¼­ÀÔ´Ï´Ù. ¿ë¾î¹ø¿ªÇ¥´Â ¿©±â¸¦ +Âü°íÇÏ±æ ¹Ù¶ø´Ï´Ù.)

+
+
top
+
+

Á¤ÀÇ

+ +
+
Á¢±ÙÁ¦¾î (Access Control)
+
³×Æ®¿÷ ¿µ¿ª¿¡ ´ëÇÑ Á¢±ÙÀ» Á¦ÇÑ. ¾ÆÆÄÄ¡¿¡¼­´Â º¸Åë ƯÁ¤ +URLÀÇ Á¢±ÙÀ» Á¦ÇÑÇϱâÀ§ÇØ »ç¿ëÇÑ´Ù.
Âü°í: ÀÎÁõ, ±ÇÇѺο©, Á¢±ÙÁ¦¾î
+ +
¾Ë°í¸®Áò (Algorithm)
+
À¯ÇÑÇÑ ´Ü°è¸¦ °ÅÃÄ ¹®Á¦¸¦ Ǫ´Â ¸íÈ®ÇÑ °ø½Ä ȤÀº ±ÔÄ¢µé. +¾Ïȣȭ¸¦ À§ÇÑ ¾Ë°í¸®ÁòÀ» º¸Åë ¾ÏÈ£±â(Ciphers)¶ó°í +ºÎ¸¥´Ù.
+ +
APache eXtension Tool +(apxs)
¸ðµâ +(module) ¼Ò½º¸¦ µ¿Àû°øÀ¯°´Ã¼ (DSO)·Î +ÄÄÆÄÀÏÇÏ°í ¾ÆÆÄÄ¡ À¥¼­¹ö¿¡ ¼³Ä¡ÇÏ´Â ÀÛ¾÷À» µ½´Â perl +½ºÅ©¸³Æ®.
Âü°í: Manpage: +apxs
+ +
ÀÎÁõ (Authentication)
+
¼­¹ö, Ŭ¶óÀ̾ðÆ®, »ç¿ëÀÚ µî ³×Æ®¿÷ ½Çü¿¡ ´ëÇÑ +È®ÀÎ.
Âü°í: ÀÎÁõ, ±ÇÇѺο©, +Á¢±ÙÁ¦¾î
+ +
ÀÎÁõ¼­ (Certificate)
+
¼­¹ö³ª Ŭ¶óÀ̾ðÆ®¿Í °°Àº ³×Æ®¿÷ ½Çü¸¦ ÀÎÁõÇÏ´Â ÀÚ·á. + ÀÎÁõ¼­¿¡´Â ¼ÒÀ¯ÀÚ (subject¶ó°í ÇÔ), ¼­¸í ÀÎÁõ±â°ü (Certificate + Authority) (issuer¶ó°í ÇÔ), ¼ÒÀ¯ÀÚÀÇ °ø°³Å°, CA°¡ ¸¸µç ¼­¸í µî¿¡ ´ëÇÑ + X.509 Á¤º¸°¡ ÀÖ´Ù. ³×Æ®¿÷ ½Çü´Â CA ÀÎÁõ¼­¸¦ »ç¿ëÇÏ¿© + ¼­¸íÀ» °Ë»çÇÑ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
ÀÎÁõ ¼­¸í ¿äû (Certificate +Signing Request, CSR)
ÀÎÁõ±â°ü (Certification +Authority)¿¡ Á¦ÃâÇÏ¿© CA ÀÎÁõ¼­ (Certificate)ÀÇ +°³ÀÎÅ° (Private Key)·Î ¼­¸íµÉ ¾ÆÁ÷ +¼­¸íµÇÁö¾ÊÀº ÀÎÁõ¼­. CSRÀÌ ¼­¸íµÇ¸é +½ÇÁ¦ ÀÎÁõ¼­°¡ µÈ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
ÀÎÁõ±â°ü (Certification +Authority, CA)
¾ÈÀüÇÑ ¹æ¹ýÀ¸·Î +³×Æ®¿÷ ½Çü¿¡ ´ëÇÑ ÀÎÁõÀ» ¼­¸íÇÏ´Â ½Å·ÚÇÏ´Â Á¦»ïÀÚ. ´Ù¸¥ ³×Æ®¿÷ +½ÇüµéÀº ¼­¸íÀ¸·Î CA°¡ ÀÎÁõ¼­ ¼ÒÀ¯ÀÚ¸¦ ÀÎÁõÇß´ÂÁö È®ÀÎÇÒ ¼ö +ÀÖ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
¾ÏÈ£±â (Cipher)
ÀڷḦ +¾ÏȣȭÇÏ´Â ¾Ë°í¸®ÁòÀ̳ª ½Ã½ºÅÛ. ¿¹¸¦ µé¾î, DES, IDEA, RC4 µîÀÌ ÀÖ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
¾ÏÈ£¹® (Ciphertext)
Æò¹® (Plaintext)À» ¾ÏÈ£±â +(Cipher)·Î ó¸®ÇÑ °á°ú.
Âü°í: SSL/TLS +¾Ïȣȭ
+ +
°øÅë °ÔÀÌÆ®¿þÀÌ ÀÎÅÍÆäÀ̽º +(Common Gateway Interface, CGI)
+
¿ÜºÎ ÇÁ·Î±×·¥ÀÌ ¿äûÀ» ¼­ºñ½ºÇÒ ¼ö ÀÖµµ·Ï ¸¸µç À¥¼­¹ö¿Í ¿ÜºÎ +ÇÁ·Î±×·¥ »çÀÌÀÇ ÀÎÅÍÆäÀ̽º Ç¥ÁØ. ÀÎÅÍÆäÀ̽º´Â ¿ø·¡ NCSA°¡ +Á¤ÀÇÇßÁö¸¸, RFC +ÇÁ·ÎÁ§Æ®À̱⵵ ÇÏ´Ù.
+Âü°í: CGI·Î µ¿Àû ÆäÀÌÁö »ý¼º
+ + +
¼³Á¤ Áö½Ã¾î (Configuration +Directive)
+
Âü°í: Áö½Ã¾î
+ +
¼³Á¤ÆÄÀÏ (Configuration File)
+
¾ÆÆÄÄ¡¸¦ ¼³Á¤ÇÏ´Â Áö½Ã¾î (directive)¸¦ +Àû¾îµÐ ÅؽºÆ®ÆÄÀÏ.
+Âü°í: ¼³Á¤ÆÄÀÏ
+ +
CONNECT
+
HTTP¸¦ ÅëÇØ ÀÚ·áÈ帧À» ÇÁ·Ï½ÃÇÏ´Â HTTP ¸Þ½áµå +(method). SSL ÇÁ·ÎÅäÄÝ µî ´Ù¸¥ ÇÁ·ÎÅäÄÝÀ» °¨½Î±âÀ§ÇØ »ç¿ëÇÑ´Ù.
+ +
»ç¿ëÀå¼Ò (Context)
¼³Á¤ÆÄÀÏ (configuration file)¿¡¼­ +ƯÁ¤ Áö½Ã¾î (directive)¸¦ »ç¿ëÇÒ ¼ö +ÀÖ´Â Àå¼Ò.
Âü°í: ¾ÆÆÄÄ¡ Áö½Ã¾î¸¦ ¼³¸íÇϴµ¥ +»ç¿ëÇÑ ¿ë¾îÁ¤ÀÇ
+ +
ÀüÀÚ¼­¸í (Digital Signature)
+
ÀÎÁõ¼­³ª ´Ù¸¥ ÆÄÀÏÀ» °Ë»çÇÏ´Â ¾ÏȣȭµÈ ¹®ÀÚµé. ÀÎÁõ±â°ü (Certification + Authority)Àº ÀÎÁõ¼­ (Certificate)¿¡ Æ÷ÇÔµÈ + °ø°³Å° (Public Key)¸¦ Çؽ¬ÇÑ °á°ú¸¦ ÀÚ½ÅÀÇ + °³ÀÎÅ° (Private Key)·Î ¾ÏȣȭÇÏ¿© ¼­¸íÀ» ¸¸µç´Ù. + ¿ÀÁ÷ CAÀÇ °ø°³Å°¸¸ÀÌ ¼­¸íÀ» Ç® ¼ö Àֱ⶧¹®¿¡, CA°¡ ÀÎÁõ¼­ + (Certificate)¸¦ °¡Áø ³×Æ®¿÷ ½Çü¸¦ ÀÎÁõÇßÀ½À» Áõ¸íÇÒ + ¼ö ÀÖ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
Áö½Ã¾î (Directive)
¾ÆÆÄÄ¡ÀÇ +¿©·¯ ±â´ÉÀ» Á¶ÀýÇÏ´Â ¼³Á¤ ¸í·É¾î. Áö½Ã¾î´Â ¼³Á¤ÆÄÀÏ (Configuration File)¿¡¼­ +»ç¿ëÇÑ´Ù.
Âü°í: Áö½Ã¾î ¸ñ·Ï
+ +
µ¿Àû°øÀ¯°´Ã¼ (Dynamic Shared +Object) (DSO)
¾ÆÆÄÄ¡ httpd +½ÇÇàÆÄÀÏ°ú º°µµ·Î ÄÄÆÄÀÏÇÏ¿© ÇÊ¿äÇÒ¶§ ÀоîµéÀÏ ¼ö ÀÖ´Â ¸ðµâ (Module).
+Âü°í: µ¿Àû°øÀ¯°´Ã¼ Áö¿ø
+ +
ȯ°æº¯¼ö (Environment Variable) +(env-variable)
+
Á¤º¸¸¦ ÀúÀåÇÏ°í ÇÁ·Î±×·¥°£¿¡ Åë½ÅÀ» À§ÇØ ¿î¿µÃ¼Á¦ ½©ÀÌ °ü¸®ÇÏ´Â +º¯¼ö. ¾ÆÆÄÄ¡¿¡µµ ȯ°æº¯¼ö¶ó´Â ³»ºÎ º¯¼ö°¡ ÀÖÁö¸¸, ½© ȯ°æÀÌ +¾Æ´Ï¶ó ¾ÆÆÄÄ¡ ³»ºÎ¿¡ ÀúÀåµÈ´Ù.
+Âü°í: ¾ÆÆÄÄ¡ÀÇ È¯°æº¯¼ö
+ +
¼öÃâ¿ë (Export-Crippled)
+
¹Ì±¹ ¼öÃâ°ü¸®±ÔÁ¦(Export Administration Regulations, EAR)¸¦ + ÁؼöÇϱâÀ§ÇØ ¾ÏÈ£(¿Í º¸¾È)ÀÇ °­µµ¸¦ ³·Ãã. ¼öÃâ¿ë ¾Ïȣȭ + ¼ÒÇÁÆ®¿þ¾î´Â Å° Å©±â°¡ ÀÛ°Ô Á¦ÇѵǾî, ¾ÏÈ£¹® + (Ciphertext)À» ¹«½ÄÇÑ ¹æ¹ý(brute force)À¸·Î Ç® ¼ö ÀÖ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ (SSL/TLS Encryption)
+ +
ÇÊÅÍ (Filter)
+
¼­¹ö°¡ º¸³»°Å³ª ¹Þ´Â ÀڷḦ ó¸®ÇÏ´Â °úÁ¤. ÀÔ·ÂÇÊÅÍ´Â +Ŭ¶óÀ̾ðÆ®°¡ ¼­¹ö·Î º¸³»´Â ÀڷḦ ó¸®ÇÏ°í, Ãâ·ÂÇÊÅÍ´Â ¼­¹ö°¡ +Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³¾ ¹®¼­¸¦ ó¸®ÇÑ´Ù. ¿¹¸¦ µé¾î, +INCLUDES Ãâ·ÂÇÊÅÍ´Â ¹®¼­ÀÇ Server +Side Includes¸¦ ó¸®ÇÑ´Ù.
+Âü°í: ÇÊÅÍ
+ +
¿ÏÀüÇÑ µµ¸ÞÀθí +(Fully-Qualified Domain-Name) (FQDN)
+
IP ÁÖ¼Ò¿¡ ´ëÀÀÇÏ´Â, È£½ºÆ®¸í°ú µµ¸ÞÀθíÀ¸·Î ±¸¼ºµÈ ³×Æ®¿÷ +½ÇüÀÇ À¯ÀÏÇÑ À̸§. ¿¹¸¦ µé¾î, www°¡ È£½ºÆ®¸íÀÌ°í +example.comÀÌ µµ¸ÞÀθíÀ϶§, +www.example.comÀº ¿ÏÀüÇÑ µµ¸ÞÀθíÀÌ´Ù.
+ +
Çڵ鷯 (Handler)
+
ÆÄÀÏÀ» ¿äûÇÒ¶§ ¼öÇàÇÏ´Â ÀÛ¾÷¿¡ ´ëÇÑ ¾ÆÆÄÄ¡ ³»ºÎ Ç¥Çö. +ÀϹÝÀûÀ¸·Î ÆÄÀÏÀº ÆÄÀÏ Á¾·ù¿¡ µû¶ó ¾Ï¹¬ÀûÀÎ Çڵ鷯¸¦ °¡Áø´Ù. +º¸Åë ¸ðµç ÆÄÀÏÀº ¼­¹ö°¡ °£´ÜÈ÷ ¼­ºñ½ºÇÏÁö¸¸, ¾î¶² ÆÄÀÏ Á¾·ù´Â +µû·Î "󸮵ȴÙ(handled)". ¿¹¸¦ µé¾î, cgi-script +Çڵ鷯´Â CGI·Î ó¸®ÇÒ ÆÄÀÏÀ» ÁöÁ¤ÇÑ´Ù.
+Âü°í: ¾ÆÆÄÄ¡¿¡¼­ Çڵ鷯 »ç¿ë
+ +
Çì´õ (Header)
+
HTTP ¿äû°ú ÀÀ´ä¿¡¼­ ½ÇÁ¦ ³»¿ë ÀÌÀü¿¡ +º¸³»´Â ºÎºÐÀ¸·Î ³»¿ëÀ» ¼³¸íÇÏ´Â Á¤º¸°¡ ÀÖ´Ù.
+ +
.htaccess
À¥¹®¼­µé ¾È¿¡ ÀÖ´Â +¼³Á¤ÆÄÀÏ (configuration file)·Î, +¼³Á¤ Áö½Ã¾î (directive)¸¦ ÀÚ½ÅÀÌ À§Ä¡ÇÑ +µð·ºÅ丮¿Í ¸ðµç ÇÏÀ§µð·ºÅ丮¿¡ Àû¿ëÇÑ´Ù. À̸§°ú ´Þ¸® ÀÌ +ÆÄÀÏ¿¡¼­´Â ´Ü¼øÇÑ Á¢±ÙÁ¦¾î Áö½Ã¾î¿Ü¿¡ °ÅÀÇ ¸ðµç Á¾·ùÀÇ Áö½Ã¾î¸¦ +»ç¿ëÇÒ ¼ö ÀÖ´Ù.
+Âü°í: ¼³Á¤ÆÄÀÏ
+ +
httpd.conf
+
¾ÆÆÄÄ¡ ÁÖ ¼³Á¤ÆÄÀÏ (configuration +file). ±âº»ÀûÀÎ À§Ä¡´Â +/usr/local/apache2/conf/httpd.confÀÌÁö¸¸, ½ÇÇàÇÒ¶§ +ȤÀº ÄÄÆÄÀ϶§ ¼³Á¤À¸·Î º¯°æÇÒ ¼ö ÀÖ´Ù.
+Âü°í: ¼³Á¤ÆÄÀÏ
+ +
HyperText Transfer +Protocol (HTTP)
+
¿ùµå¿ÍÀ̵åÀ¥¿¡¼­ »ç¿ëÇϴ ǥÁØ Àü¼Û ÇÁ·ÎÅäÄÝ. ¾ÆÆÄÄ¡´Â +RFC 2616¿¡¼­ +Á¤ÀÇÇÑ HTTP/1.1À̶ó´Â ÇÁ·ÎÅäÄÝÀÇ 1.1 ¹öÀüÀ» ±¸ÇöÇÑ´Ù.
+ +
HTTPS
+
¿ùµåÈ­À̵åÀ¥ÀÇ Ç¥ÁØ ¾ÏÈ£Åë½Å ¹æ¹ý, HyperText Transfer + Protocol (Secure). »ç½Ç ¹Ø´Ü¿¡ SSLÀ» + »ç¿ëÇÑ HTTPÀÌ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
¸Þ½áµå (Method)
Ŭ¶óÀ̾ðÆ®°¡ +º¸³»´Â HTTP ¿äûÁÙÀÌ +ÀÚ¿ø¿¡ ¼öÇàÇϵµ·Ï Áö½ÃÇÑ Çൿ. HTTP ¸Þ½áµå¿¡´Â GET, +POST, PUT µîÀÌ ÀÖ´Ù.
+ +
¸Þ½ÃÁö ¿ä¾à (Message Digest)
+
¸Þ½ÃÁö ³»¿ëÀÌ Àü¼ÛÁß º¯°æµÇÁö ¾Ê¾ÒÀ½À» Áõ¸íÇϱâÀ§ÇÑ + ¸Þ½ÃÁöÀÇ Çؽ¬.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
MIME-type
Àü¼ÛÇÒ ¹®¼­ÀÇ +Á¾·ù¸¦ ¼³¸íÇÏ´Â ¹æ½Ä. Multipurpose Internet Mail Extensions +Çü½ÄÀ» ºô·Á¿Ô±â¶§¹®¿¡ ÀÌ·¸°Ô À̸§À» Áö¾ú´Ù. ½½·¡½¬¸¦ »çÀÌ¿¡ +µÐ major type°ú minor typeÀ¸·Î ÀÌ·ç¾îÁø´Ù. ¿¹¸¦ µé¸é, +text/html, image/gif, +application/octet-stream µîÀÌ´Ù. MIME-typeÀº HTTPÀÇ +Content-Type Çì´õ (header)·Î +Àü¼ÛÇÑ´Ù.
Âü°í: mod_mime
+ +
¸ðµâ (Module)
ÇÁ·Î±×·¥ÀÇ µ¶¸³µÈ +ºÎºÐ. ¸¹Àº ¾ÆÆÄÄ¡ ±â´ÉÀº ´ç½ÅÀÌ Æ÷ÇÔ¿©ºÎ¸¦ ¼±ÅÃÇÒ ¼ö ÀÖ´Â ¸ðµâ¿¡ +µé¾îÀÖ´Ù. ¾ÆÆÄÄ¡ httpd ½ÇÇàÆÄÀÏ°ú °°ÀÌ ÄÄÆÄÀÏÇÑ ¸ðµâÀ» Á¤Àû +¸ðµâÀ̶ó°í Çϸç, µû·Î ºÐ¸®µÇ¾î ½ÇÇà½Ã ¼±ÅÃÀûÀ¸·Î ÀоîµéÀÏ +¼ö ÀÖ´Â ¸ðµâÀ» µ¿Àû ¸ðµâ ȤÀº DSO¶ó°í +ÇÑ´Ù. ±âº»ÀûÀ¸·Î Æ÷ÇÔÇÏ´Â ¸ðµâÀ» base ¸ðµâÀ̶ó°í ÇÑ´Ù. +¾ÆÆÄÄ¡ À¥¼­¹ö Ÿº¼ (tarball)°ú °°ÀÌ +¹èÆ÷µÇÁö´Â ¾ÊÁö¸¸ ¾ÆÆÄÄ¡¿¡´Â ¸¹Àº ¸ðµâµéÀÌ ÀÖ´Ù. À̵éÀ» +Á¦»ïÀÚ°¡ ¸¸µç(third-party) ¸ðµâÀ̶ó°í ÇÑ´Ù.
+Âü°í: ¸ðµâ ¸ñ·Ï
+ +
¸ðµâ ¸¶¹ý¼ö (Module Magic Number) +(MMN)
+
¸ðµâ ¸¶¹ý¼ö´Â ¾ÆÆÄÄ¡ ¼Ò½ºÄڵ尡 Á¤ÀÇÇÑ »ó¼ö·Î, ¸ðµâÀÇ +ÀÌÁøȣȯ¼º°ú °ü·ÃÀÌ ÀÖ´Ù. ¸ðµâ ¸¶¹ý¼ö´Â ÀÌÁøȣȯ¼ºÀ» ´õ ÀÌ»ó º¸ÀåÇÒ +¼ö ¾øµµ·Ï ¾ÆÆÄÄ¡ ³»ºÎ ±¸Á¶³ª ÇÔ¼ö È£Ãâ, ´Ù¸¥ API ÀϺΰ¡ º¯°æµÈ +°æ¿ì¿¡ ¹Ù²ï´Ù. MMNÀÌ º¯Çϸé Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀº ¸ðµÎ ÃÖ¼ÒÇÑ ´Ù½Ã +ÄÄÆÄÀÏµÇ¾ß ÇÑ´Ù. »õ ¾ÆÆÄÄ¡ ¹öÀü¿¡ ¸Âµµ·Ï Á¶±Ý ¼öÁ¤ÇؾßÇÒ °æ¿ìµµ +ÀÖ´Ù. +
+ +
OpenSSL
+
SSL/TLS¸¦ À§ÇÑ ¿ÀǼҽº µµ±¸
+ Âü°í http://www.openssl.org/
+ +
Pass Phrase
+
°³ÀÎÅ° ÆÄÀÏÀ» º¸È£ÇÏ´Â ¹®±¸. ÀÎÁõÇÏÁö¾ÊÀº »ç¿ëÀÚ°¡ ÀÌ °³ÀÎÅ° +ÆÄÀÏÀ» »ç¿ëÇÏ¿© ¾ÏȣȭÇÏÁö ¸øÇϵµ·Ï ÇÑ´Ù. º¸Åë ¾ÏÈ£±â +(Ciphers)°¡ »ç¿ëÇÏ´Â ºñ¹Ð½º·± ¾ÏÈ£/Çص¶ Å°ÀÌ´Ù.
Âü°í: SSL/TLS ¾Ïȣȭ
+ +
Æò¹® (Plaintext)
+
¾ÏȣȭÇÏÁö ¾ÊÀº ±Û.
+ +
°³ÀÎÅ° (Private Key)
¹ÞÀº +ÀڷḦ Çص¶ÇÏ°í º¸³»´Â ÀڷḦ ¼­¸íÇϱâÀ§ÇÑ °ø°³Å° ¾Ïȣȭ (Public Key +Cryptography) ½Ã½ºÅÛÀÇ ¾ÏȣŰ.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
ÇÁ·Ï½Ã (Proxy)
Ŭ¶óÀ̾ðÆ®¿Í +½ÇÁ¦ ¼­¹ö »çÀÌ¿¡ ÀÖ´Â Áß°£ ¼­¹ö. Ŭ¶óÀ̾ðÆ®¿¡°Ô ¿äûÀ» +¹Þ¾Æ ½ÇÁ¦ ¼­¹ö·Î º¸³»°í, ½ÇÁ¦ ¼­¹ö¿¡°Ô¼­ ¹ÞÀº ÀÀ´äÀ» ´Ù½Ã +Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³½´Ù. ¿©·¯ Ŭ¶óÀ̾ðÆ®°¡ °°Àº ³»¿ëÀ» ¿äûÇϸé +ÇÁ·Ï½Ã´Â ¸Å¹ø ¼­¹ö¿¡ ¿äûÇÏÁö¾Ê°í ij½¬¿¡ ÀúÀåµÈ ³»¿ëÀ» »ç¿ëÇÏ¿© +ÀÀ´ä½Ã°£À» ÁÙÀÏ ¼ö ÀÖ´Ù.
+Âü°í: mod_proxy
+ +
°ø°³Å° (Public Key)
°ø°³Å° ¾Ïȣȭ (Public Key +Cryptography) ½Ã½ºÅÛ¿¡¼­ Å°ÀÇ ¼ÒÀ¯ÀÚ¿¡°Ô º¸³»´Â ¹®±¸¸¦ ¾ÏȣȭÇϰųª +¼ÒÀ¯ÀÚ°¡ ¸¸µç ¼­¸íÀ» Ç®±âÀ§ÇÑ °ø°³µÈ Å°.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
°ø°³Å° ¾Ïȣȭ (Public Key +Cryptography)
+
¾ÏÈ£¿Í Çص¶¿¡ ¼­·Î ´Ù¸¥ Å°¸¦ »ç¿ëÇÏ´Â ºñ´ëĪ(asymmetric) +¾Ïȣȭ ½Ã½ºÅÛÀÇ ¿¬±¸ ¹× È°¿ë. ¾ÏÈ£¿Í Çص¶¿¡ »ç¿ëÇÏ´Â µÎ°³ÀÇ Å°´Â +Å°½Ö(key pair)À» ÀÌ·é´Ù. ºñ´ëĪ ¾Ïȣȭ¶ó°íµµ ºÎ¸¥´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
Á¤±ÔÇ¥Çö½Ä (Regular Expression) (Regex)
±ÛÀÇ ÆÐÅÏÀ» ±â¼úÇÏ´Â ¹æ½Ä. +¿¹¸¦ µé¾î, "¹®ÀÚ A·Î ½ÃÀÛÇÏ´Â ¸ðµç ´Ü¾î", "¼ýÀÚ 10°³·ÎµÈ ÀüÈ­¹øÈ£", +½ÉÁö¾î "½°Ç¥°¡ µÎ°³ÀÖ°í ´ë¹®ÀÚ Q°¡ ¾ø´Â ¹®Àå" µîÀ» Ç¥ÇöÇÒ ¼ö ÀÖ´Ù. +Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ¸é ¸Å¿ì À¯¿¬ÇÏ°Ô ÆÄÀÏÀ̳ª ÀÚ¿ø¿¡ ¾î¶² ¼ºÁúÀ» Àû¿ëÇÒ +¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, "images"¶õ µð·ºÅ丮 ¾Æ·¡¿¡ ÀÖ´Â ¸ðµç .gif¿Í +.jpg ÆÄÀÏÀº "/images/.*(jpg|gif)$"·Î ÁöĪÇÒ ¼ö +ÀÖ´Ù. ¾ÆÆÄÄ¡´Â PCRE ¶óÀ̺귯¸®¸¦ +»ç¿ëÇÏ¿© Perlȣȯ Á¤±ÔÇ¥Çö½ÄÀ» Áö¿øÇÑ´Ù.
+ +
¿ªÇÁ·Ï½Ã (Reverse Proxy)
+
Ŭ¶óÀ̾ðÆ®¿¡°Ô ½ÇÁ¦ ¼­¹öó·³ º¸ÀÌ´Â ÇÁ·Ï½Ã (proxy) ¼­¹ö. º¸¾È»ó ÀÌÀ¯ ȤÀº ºÎÇϸ¦ +ºÐ»êÇϱâÀ§ÇØ Å¬¶óÀ̾ðÆ®¿¡°Ô ½ÇÁ¦ ¼­¹ö¸¦ ¼û±æ¶§ À¯¿ëÇÏ´Ù.
+ +
Secure Sockets Layer (SSL)
Netscape Communications»ç°¡ TCP/IP +³×Æ®¿÷ÀÇ ÀϹÝÀûÀÎ Åë½Å ÀÎÁõ°ú ¾Ïȣȭ¸¦ À§ÇØ ¸¸µç ÇÁ·ÎÅäÄÝ. +°¡Àå ÀϹÝÀûÀÎ ¿ëµµ´Â HTTPS (HyperText Transfer Protocol +(HTTP) over SSL)ÀÌ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
Server Side Includes (SSI)
HTML ÆÄÀÏ ¾È¿¡ ó¸®Áö½Ã¾î¸¦ Æ÷ÇÔÇÏ´Â +±â¼ú.
Âü°í: Server Side Includes ¼Ò°³
+ +
¼¼¼Ç (Session)
+
ÀϹÝÀûÀ¸·Î Åë½ÅÀÇ »óȲ(context) Á¤º¸.
+ +
SSLeay
+
Eric A. YoungÀÌ °³¹ßÇÑ ¿ø·¡ SSL/TLS ±¸Çö ¶óÀ̺귯¸®
+ +
´ëĪÀû ¾ÏÈ£¹ý (Symmetric +Cryptography)
+
¾ÏÈ£¿Í Çص¶ ÀÛ¾÷¿¡ °°Àº ¾Ïȣ۸¦ »ç¿ëÇÏ´Â ¾ÏÈ£±â + (Ciphers)ÀÇ ¿¬±¸ ¹× È°¿ë.
+Âü°í: SSL/TLS Encryption
+ +
Ÿº¼ (Tarball)
+
tar µµ±¸¸¦ »ç¿ëÇÏ¿© ÆÄÀϵéÀ» ¸ðÀº ¹­À½. ¾ÆÆÄÄ¡´Â +tar ÆÄÀÏÀ» ¾ÐÃàÇϰųª pkzipÀ¸·Î ¾ÐÃàÇÏ¿© ¹èÆ÷µÈ´Ù.
+ +
Transport Layer Security (TLS)
+
ÀÎÅͳݱâ¼ú °ü·Ã ±¹Á¦Ç¥ÁØÈ­±â±¸(Internet Engineering Task +Force, IETF)°¡ TCP/IP ³×Æ®¿÷ÀÇ ÀϹÝÀûÀÎ Åë½Å ÀÎÁõ°ú ¾Ïȣȭ¸¦ +À§ÇØ ¸¸µç SSLÀÇ ÈÄ¼Ó ÇÁ·ÎÅäÄÝ. TLS ¹öÀü 1Àº SSL ¹öÀü 3°ú °ÅÀÇ +À¯»çÇÏ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+ +
Uniform Resource Locator +(URL)
+
ÀÎÅͳݿ¡ ÀÖ´Â ÀÚ¿øÀÇ À̸§/ÁÖ¼Ò. Á¤½ÄÀ¸·Î´Â Uniform Resource +Identifier¶ó°í ÇÏ´Â °ÍÀÇ ÀÏ»óÀûÀÎ ºñ°ø½Ä ¸íĪÀÌ´Ù. º¸Åë URLÀº +http³ª https°°Àº ½ºÅ´(scheme), È£½ºÆ®¸í, +°æ·Î·Î ±¸¼ºµÈ´Ù. ÀÌ ÆäÀÌÁöÀÇ URLÀº +http://httpd.apache.org/docs/2.2/glossary.htmlÀÌ´Ù.
+ +
Uniform Resource Identifier +(URI)
+
Ãß»óÀûÀÎ ÀÚ¿øÀ̳ª ½ÇÁ¦ ÀÚ¿øÀ» ÁöĪÇϱâÀ§ÇÑ °£°áÇÑ ¹®ÀÚ¿­. +°ø½ÄÀûÀ¸·Î RFC +2396¿¡¼­ Á¤ÀÇÇÑ´Ù. ¿ùµå¿ÍÀ̵åÀ¥¿¡¼­ »ç¿ëÇÏ´Â URI¸¦ º¸Åë +URLÀ̶ó°í ºÎ¸¥´Ù.
+ +
°¡»óÈ£½ºÆ® (Virtual Hosting)
+
¾ÆÆÄÄ¡ Çϳª·Î ¿©·¯ À¥»çÀÌÆ®¸¦ ¼­ºñ½ºÇϱâ. IP °¡»óÈ£½ºÆ®´Â +À¥»çÀÌÆ®¸¶´Ù IP ÁÖ¼Ò°¡ ´Ù¸£´Ù. À̸§±â¹Ý(name-based) +°¡»óÈ£½ºÆ®´Â È£½ºÆ®¸í¸¸À» »ç¿ëÇϹǷΠÇÑ IP ÁÖ¼Ò¿¡¼­ ¿©·¯ +»çÀÌÆ®¸¦ ¼­ºñ½ºÇÒ ¼ö ÀÖ´Ù.
+Âü°í: ¾ÆÆÄÄ¡ °¡»óÈ£½ºÆ® ¹®¼­
+ +
X.509
+
±¹Á¦Àü±âÅë½Å¿¬ÇÕ(International Telecommunication Union, +ITU-T)ÀÌ ±ÇÀåÇÏ´Â ÀÎÁõ¼­ ¾ç½Ä. SSL/TLS ÀÎÁõ¿¡¼­ »ç¿ëÇÑ´Ù.
+Âü°í: SSL/TLS ¾Ïȣȭ
+
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/handler.html b/docs/manual/handler.html new file mode 100644 index 00000000..dafdeac0 --- /dev/null +++ b/docs/manual/handler.html @@ -0,0 +1,19 @@ +URI: handler.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: handler.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: handler.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: handler.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: handler.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R diff --git a/docs/manual/handler.html.en b/docs/manual/handler.html.en new file mode 100644 index 00000000..1918c6d5 --- /dev/null +++ b/docs/manual/handler.html.en @@ -0,0 +1,155 @@ + + + +Apache's Handler Use - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Apache's Handler Use

+
+

Available Languages:  en  | + es  | + ja  | + ko  | + ru 

+
+ +

This document describes the use of Apache's Handlers.

+
+ +
top
+
+

What is a Handler

+ +
Related ModulesRelated Directives
+ + +

A "handler" is an internal Apache representation of the + action to be performed when a file is called. Generally, files + have implicit handlers, based on the file type. Normally, all + files are simply served by the server, but certain file types + are "handled" separately.

+ +

Handlers may also be configured explicitly, + based on either filename extensions or on location, + without relation to file type. This is + advantageous both because it is a more elegant solution, and + because it also allows for both a type and a + handler to be associated with a file. (See also Files with Multiple + Extensions.)

+ +

Handlers can either be built into the server or included in + a module, or they can be added with the Action directive. The + built-in handlers in the standard distribution are as + follows:

+ +
    +
  • default-handler: Send the file using the + default_handler(), which is the handler used by + default to handle static content. (core)
    • + +
  • send-as-is: Send file with HTTP headers + as is. (mod_asis)
    • + +
  • cgi-script: Treat the file as a CGI + script. (mod_cgi)
    • + +
  • imap-file: Parse as an imagemap rule + file. (mod_imagemap)
    • + +
  • server-info: Get the server's + configuration information. (mod_info)
    • + +
  • server-status: Get the server's status + report. (mod_status)
    • + +
  • type-map: Parse as a type map file for + content negotiation. (mod_negotiation)
    • +
+
top
+
+

Examples

+ + +

Modifying static content using a CGI script

+ + +

The following directives will cause requests for files with + the html extension to trigger the launch of the + footer.pl CGI script.

+ +

+ Action add-footer /cgi-bin/footer.pl
+ AddHandler add-footer .html +

+ +

Then the CGI script is responsible for sending the + originally requested document (pointed to by the + PATH_TRANSLATED environment variable) and making + whatever modifications or additions are desired.

+ + +

Files with HTTP headers

+ + +

The following directives will enable the + send-as-is handler, which is used for files which + contain their own HTTP headers. All files in the + /web/htdocs/asis/ directory will be processed by + the send-as-is handler, regardless of their + filename extensions.

+ +

+ <Directory /web/htdocs/asis>
+ SetHandler send-as-is
+ </Directory> +

+ + +
top
+
+

Programmer's Note

+ + +

In order to implement the handler features, an addition has + been made to the Apache API that + you may wish to make use of. Specifically, a new record has + been added to the request_rec structure:

+ +

+ char *handler +

+ +

If you wish to have your module engage a handler, you need + only to set r->handler to the name of the + handler at any time prior to the invoke_handler + stage of the request. Handlers are implemented as they were + before, albeit using the handler name instead of a content + type. While it is not necessary, the naming convention for + handlers is to use a dash-separated word, with no slashes, so + as to not invade the media type name-space.

+
+
+

Available Languages:  en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/handler.html.es b/docs/manual/handler.html.es new file mode 100644 index 00000000..330bbe04 --- /dev/null +++ b/docs/manual/handler.html.es @@ -0,0 +1,168 @@ + + + +Uso de los Handlers en Apache - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

Uso de los Handlers en Apache

+
+

Idiomas disponibles:  en  | + es  | + ja  | + ko  | + ru 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ +

Este documento describe el uso de los Handlers en Apache.

+
+ +
top
+
+

¿Qué es un Handler?

+ +
Módulos RelacionadosDirectivas Relacionadas
+ + +

Un "handler" es una representación interna de Apache de + una acción que se va a ejecutar cuando hay una llamada a un + fichero. Generalmente, los ficheros tienen handlers + implícitos, basados en el tipo de fichero de que se + trata. Normalmente, todos los ficheros son simplemente servidos + por el servidor, pero algunos tipos de ficheros se tratan de forma + diferente.

+ +

Apache 1.1 añade la posibilidad de usar handlers + explicitamente. Basándose en la extension del fichero o en + la ubicación en la que este, se pueden especificar handlers + sin tener en cuenta el tipo de fichero de que se trate. Esto es + una ventaja por dos razones. Primero, es una solución + más elegante. Segundo, porque a un fichero se le pueden + asignar tanto un tipo como un handler. (Consulte + también la sección Ficheros y extensiones + múltiples.)

+ +

Los Handlers pueden ser tanto ser compilados con el servidor + como incluidos en un módulo, como añadidos con la + directiva Action. Los + handlers compilados con el servidor de la distribución + estándar de Apache son:

+ +
    +
  • default-handler: Envía el fichero + usando el default_handler(), que es el handler + usado por defecto para tratar contenido + estático. (core)
    • + +
  • send-as-is: Envía el fichero con + cabeceras HTTP tal y como es. (mod_asis)
    • + +
  • cgi-script: Trata el fichero como un sript + CGI. (mod_cgi)
    • + +
  • imap-file: Trata el fichero como un mapa de + imágenes. (mod_imagemap)
    • + +
  • server-info: Extrae la información de + configuración del + servidor. (mod_info)
    • + +
  • server-status: Extrae el informe de estado + del servidor. (mod_status)
    • + +
  • type-map: Trata el fichero como una + correspondencia de tipos para la negociación de contenidos. + (mod_negotiation)
top
+
+

Ejemplos

+ +

Modificar contenido estático usando un script + CGI

+ + +

Las siguientes directivas hacen que cuando haya una + petición de ficheros con la extensión + html se lance el script CGI + footer.pl.

+ +

+ Action add-footer /cgi-bin/footer.pl
+ AddHandler add-footer .html +

+ +

En este caso, el script CGI es el responsable de enviar el + documento originalmente solicitado (contenido en la variable de + entorno PATH_TRANSLATED) y de hacer cualquier + modificación o añadido deseado.

+ + +

Archivos con cabaceras HTTP

+ + +

Las siguientes directivas activan el handler + send-as-is, que se usa para ficheros que contienen + sus propias cabeceras HTTP. Todos los archivos en el directorio + /web/htdocs/asis/ serán procesados por el + handler send-as-is, sin tener en cuenta su + extension.

+ +

+ <Directory /web/htdocs/asis>
+ SetHandler send-as-is
+ </Directory> +

+ + +
top
+
+

Nota para programadores

+ + +

Para implementar las funcionalidades de los handlers, se ha + hecho un añadido a la API de + Apache que puede que quiera usar. Para ser más + específicos, se ha añadido un nuevo registro a la + estructura request_rec:

+ +

+ char *handler +

+ +

Si quiere que su módulo llame a un handler , solo tiene + que añadir r->handler al nombre del handler + en cualquier momento antes de la fase invoke_handler + de la petición. Los handlers se implementan siempre como se + hacía antes, aunque usando el nombre del handler en vez de un + tipo de contenido. Aunque no es de obligado cumplimiento, la + convención de nombres para los handlers es que se usen + palabras separadas por guiones, sin barras, de manera que no se + invada el media type name-space.

+
+
+

Idiomas disponibles:  en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/handler.html.ja.euc-jp b/docs/manual/handler.html.ja.euc-jp new file mode 100644 index 00000000..b43b7535 --- /dev/null +++ b/docs/manual/handler.html.ja.euc-jp @@ -0,0 +1,161 @@ + + + +Apache ¤Î¥Ï¥ó¥É¥é¤Î»ÈÍÑ - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

Apache ¤Î¥Ï¥ó¥É¥é¤Î»ÈÍÑ

+
+

Available Languages:  en  | + es  | + ja  | + ko  | + ru 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +

Apache ¤Î¥Ï¥ó¥É¥é¤Î»ÈÍѤ˴ؤ·¤Æµ­½Ò¤·¤Æ¤¤¤Þ¤¹¡£

+
+ +
top
+
+

¥Ï¥ó¥É¥é¤È¤Ï

+ +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ + +

¡Ö¥Ï¥ó¥É¥é¡×¤È¤Ï¡¢¥Õ¥¡¥¤¥ë¤¬¸Æ¤Ð¤ì¤¿¤È¤­¤Ë¼Â¹Ô¤µ¤ì¤ëÆ°ºî¤Î + Apache ¤Ë¤ª¤±¤ëÆâÉôɽ¸½¤Ç¤¹¡£ + Ä̾¥Õ¥¡¥¤¥ë¤Ï¥Õ¥¡¥¤¥ë·¿¤Ë´ð¤Å¤¤¤¿°ÅÌۤΥϥó¥É¥é¤¬¤¢¤ê¤Þ¤¹¡£ + ÉáÄ̤Ϥ¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤Ïñ¤Ë¥µ¡¼¥Ð¤Ë°·¤ï¤ì¤Þ¤¹¤¬¡¢ + ¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤ÎÃæ¤Ë¤ÏÊ̤ˡ֥ϥó¥É¥ë¡×(ÌõÃí: °·¤¦) + ¤µ¤ì¤ë¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£

+ +

Apache 1.1 ¤Ç¤Ï¡¢¥Ï¥ó¥É¥é¤òÌÀ¼¨Åª¤Ë»ÈÍѤ¹¤ëµ¡Ç½¤¬Äɲ䵤ì¤Þ¤·¤¿¡£ + ¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤äÃÖ¤¤¤Æ¤¤¤ë¾ì½ê¤Ë´ð¤Å¤¤¤Æ¡¢ + ¥Õ¥¡¥¤¥ë·¿¤È´Ø·¸¤Ê¤¯¥Ï¥ó¥É¥é¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ï¤è¤êÍ¥²í¤Ê²ò·èË¡¤È¤¤¤¦ÅÀ¤È¡¢¥Õ¥¡¥¤¥ë¤Ë¥¿¥¤¥×¤È¥Ï¥ó¥É¥é¤ÎξÊý¤ò´ØÏ¢ÉÕ¤±¤ë¤³¤È¤¬¤Ç¤­¤ë¤È¤¤¤¦ÅÀ¤ÇÍ¥¤ì¤Æ¤¤¤Þ¤¹¡£ + (Ê£¿ô¤Î³ÈÄ¥»Ò¤Î¤¢¤ë¥Õ¥¡¥¤¥ë¤â»²¾È¤·¤Æ¤¯¤À¤µ¤¤)¡£

+ +

¥Ï¥ó¥É¥é¤Ï¥µ¡¼¥Ð¤ËÁȤ߹þ¤ó¤À¤ê¡¢¥â¥¸¥å¡¼¥ë¤È¤·¤Æ´Þ¤á¤¿¤ê¡¢ + Action + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤·¤ÆÄɲä·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + °Ê²¼¤Ïɸ½àÇÛÉÛ¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¥Ï¥ó¥É¥é¤Ç¤¹¡£ +

+ +
    +
  • default-handler:default_handelr() + ¤ò»È¤Ã¤Æ¥Õ¥¡¥¤¥ë¤òÁ÷¤ê¤Þ¤¹¡£ + ÀÅŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤ò°·¤¦¤È¤­¤Ë¥Ç¥Õ¥©¥ë¥È¤Ç»ÈÍѤµ¤ì¤ë¥Ï¥ó¥É¥é¤Ç¤¹¡£ + (core)
    • + +
  • send-as-is: + HTTP ¥Ø¥Ã¥À¤Î¤¢¤ë¥Õ¥¡¥¤¥ë¤ò¤½¤Î¤Þ¤ÞÁ÷¤ê¤Þ¤¹¡£ + (mod_asis)
    • + +
  • cgi-script: ¥Õ¥¡¥¤¥ë¤ò CGI + ¥¹¥¯¥ê¥×¥È¤È¤·¤Æ°·¤¤¤Þ¤¹¡£ + (mod_cgi)
    • + +
  • imap-file: + ¥¤¥á¡¼¥¸¥Þ¥Ã¥×¤Î¥ë¡¼¥ë¥Õ¥¡¥¤¥ë¤È¤·¤Æ²òÀϤ·¤Þ¤¹¡£ + (mod_imagemap)
    • + +
  • server-info: ¥µ¡¼¥Ð¤ÎÀßÄê¾ðÊó¤ò¼èÆÀ¤·¤Þ¤¹¡£ + (mod_info)
    • + +
  • server-status: ¥µ¡¼¥Ð¤Î¾õÂÖÊó¹ð¤ò¼èÆÀ¤·¤Þ¤¹¡£ + (mod_status)
    • + +
  • type-map: + ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î¤¿¤á¤Î¥¿¥¤¥×¥Þ¥Ã¥×¤È¤·¤Æ²òÀϤ·¤Þ¤¹¡£ + (mod_negotiation)
    • +
+
top
+
+

Îã

+ + +

CGI ¥¹¥¯¥ê¥×¥È¤òÍѤ¤¤ÆÀÅŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤òÊѹ¹¤¹¤ë

+ + +

°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤Æ¡¢³ÈÄ¥»Ò¤¬ html + ¤Ç¤¢¤ë¥Õ¥¡¥¤¥ë¤Ï footer.pl + CGI ¥¹¥¯¥ê¥×¥È¤òµ¯Æ°¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

+ Action add-footer /cgi-bin/footer.pl
+ AddHandler add-footer .html +

+ +

CGI ¥¹¥¯¥ê¥×¥È¤Ï´õ˾¤Î½¤Àµ¤äÄɲäò¹Ô¤Ê¤Ã¤Æ¡¢¸µ¡¹Í׵ᤵ¤ì¤¿Ê¸½ñ + (´Ä¶­ÊÑ¿ô PATH_TRANSLATED + ¤Ç»Ø¤µ¤ì¤Æ¤¤¤Þ¤¹) ¤òÁ÷¤ëÀÕǤ¤¬¤¢¤ê¤Þ¤¹¡£ +

+ + +

HTTP ¥Ø¥Ã¥À¤Î¤¢¤ë¥Õ¥¡¥¤¥ë

+ + +

°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï send-as-is + ¥Ï¥ó¥É¥é¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë»Ø¼¨¤·¤Þ¤¹¡£¤³¤Î¥Ï¥ó¥É¥é¤Ï¼«Ê¬¼«¿È¤Î HTTP + ¥Ø¥Ã¥À¤ò»ý¤Ã¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£¤³¤³¤Ç¤Ï¡¢³ÈÄ¥»Ò¤Ë´Ø¤ï¤é¤º¡¢ + /web/htdocs/asis ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ëÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤Ï + send-as-is ¥Ï¥ó¥É¥é¤Ë¤è¤Ã¤Æ°·¤ï¤ì¤Þ¤¹¡£

+ +

+ <Directory /web/htdocs/asis>
+ SetHandler send-as-is
+ </Directory> +

+ + +
top
+
+

¥×¥í¥°¥é¥Þ¸þ¤±¤Î¥á¥â

+ + +

¥Ï¥ó¥É¥é¤Îµ¡Ç½¤ò¼ÂÁõ¤¹¤ë¤¿¤á¤Ë¡¢ÍøÍѤ¹¤ë¤ÈÊØÍø¤«¤â¤·¤ì¤Ê¤¤¤â¤Î¤¬ + Apache API + ¤ËÄɲ䵤ì¤Þ¤·¤¿¡£¾Ü¤·¤¯¸À¤¦¤È¡¢request_rec + ¹½Â¤ÂΤ˿·¤·¤¤¥ì¥³¡¼¥É¤¬Äɲ䵤줿¤È¤¤¤¦¤³¤È¤Ç¤¹¡£

+ +

+ char *handler +

+ +

¤â¤·¥â¥¸¥å¡¼¥ë¤¬¥Ï¥ó¥É¥é¤Ë´Ø¤ï¤ê¤¿¤¤¾ì¹ç¡¢ + ¤ä¤é¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤³¤È¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤¬ invoke_handler + ¥¹¥Æ¡¼¥¸¤Ë㤹¤ë°ÊÁ°¤Ë r->handler + ¤òÀßÄꤹ¤ë¤³¤È¤À¤±¤Ç¤¹¡£¥Ï¥ó¥É¥é¤Ï¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ÎÂå¤ï¤ê¤Ë + ¥Ï¥ó¥É¥é̾¤ò»È¤¦¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤³¤È°Ê³°¤Ï¡¢°ÊÁ°¤ÈƱ¤¸¤è¤¦¤Ë¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ɬ¤ºÍ׵ᤵ¤ì¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢¥á¥Ç¥£¥¢¥¿¥¤¥× + ¤Î̾Á°¶õ´Ö¤ò¿¯¤µ¤Ê¤¤¤è¤¦¤Ë¡¢¥Ï¥ó¥É¥é¤Î̾Á°¤Ë¤Ï¥¹¥é¥Ã¥·¥å¤ò´Þ¤Þ¤Ê¤¤¡¢ + ¥À¥Ã¥·¥å (ÌõÃí: "-") ¤ÇʬΥ¤µ¤ì¤¿Ì¾Á°¤òÉÕ¤±¤ë½¬´·¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+
+
+

Available Languages:  en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/handler.html.ko.euc-kr b/docs/manual/handler.html.ko.euc-kr new file mode 100644 index 00000000..e5956382 --- /dev/null +++ b/docs/manual/handler.html.ko.euc-kr @@ -0,0 +1,151 @@ + + + +¾ÆÆÄÄ¡¿¡¼­ Çڵ鷯 »ç¿ë - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¾ÆÆÄÄ¡¿¡¼­ Çڵ鷯 »ç¿ë

+
+

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

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

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡¿¡¼­ Çڵ鷯¸¦ »ç¿ëÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

Çڵ鷯°¡ ¹«¾ùÀΰ¡

+ +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ + +

ÆÄÀÏÀ» ¿äûÇÒ¶§ ¾ÆÆÄÄ¡°¡ ³»ºÎÀûÀ¸·Î ¼öÇàÇÒ ÀÛ¾÷À» + "Çڵ鷯(handler)"¶ó°í ÇÑ´Ù. ÀϹÝÀûÀ¸·Î ÆÄÀÏÀº ÆÄÀÏ Á¾·ù¿¡ + µû¶ó ¾Ï¹¬ÀûÀÎ Çڵ鷯¸¦ °¡Áö°í ÀÖ´Ù. ¸ðµç ÆÄÀÏÀº º¸Åë °£´ÜÈ÷ + ¼­¹ö°¡ ¼­ºñ½ºÇÏÁö¸¸, ¾î¶² ÆÄÀÏ Á¾·ù´Â µû·Î "󸮵ȴÙ(handled)".

+ +

Apache 1.1ºÎÅÍ Çڵ鷯¸¦ ¸í½ÃÀûÀ¸·Î »ç¿ëÇÒ ¼ö ÀÖ°Ô µÇ¾ú´Ù. + ÆÄÀÏ Á¾·ù¿Í °ü°è¾øÀÌ Çڵ鷯¸¦ ÆÄÀÏÀÇ È®ÀåÀÚ³ª À§Ä¡¿¡ µû¶ó + ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù. ÀÌ´Â ´õ ÈǸ¢ÇÑ ¹æ¹ýÀÌ°í ÆÄÀÏÀ» Á¾·ù¿Í Çڵ鷯 + µÑ ¸ðµÎ¿Í ¿¬°èÇÒ ¼ö Àֱ⶧¹®¿¡ ÁÁ´Ù. (¿©·¯ È®ÀåÀÚ¸¦ °¡Áø ÆÄÀϵµ + Âü°í)

+ +

Çڵ鷯´Â ¼­¹ö³ª ¸ðµâ·Î ±¸ÇöÇÏ¿©, Action Áö½Ã¾î·Î Ãß°¡ÇÒ + ¼ö ÀÖ´Ù. Ç¥ÁØ ¹èÆ÷º»¿¡ ÀÖ´Â ±âº» Çڵ鷯´Â ´ÙÀ½°ú °°´Ù:

+ +
    +
  • default-handler: Á¤ÀûÀÎ ³»¿ëÀ» + ó¸®ÇϱâÀ§ÇØ ±âº»ÀûÀ¸·Î »ç¿ëÇÏ´Â Çڵ鷯 + default_handler()¸¦ »ç¿ëÇÏ¿© ÆÄÀÏÀ» º¸³½´Ù. + (core)
    • + +
  • send-as-is: HTTP Çì´õ°¡ ÀÖ´Â ÆÄÀÏÀ» + ±×´ë·Î º¸³½´Ù. (mod_asis)
    • + +
  • cgi-script: ÆÄÀÏÀ» CGI·Î ó¸®ÇÑ´Ù. + (mod_cgi)
    • + +
  • imap-file: imagemap ±ÔÄ¢ ÆÄÀÏ·Î + ó¸®ÇÑ´Ù. (mod_imagemap)
    • + +
  • server-info: ¼­¹öÀÇ ¼³Á¤ Á¤º¸¸¦ + ¾Ë·ÁÁØ´Ù. (mod_info)
    • + +
  • server-status: ¼­¹öÀÇ »óŸ¦ º¸°íÇÑ´Ù. + (mod_status)
    • + +
  • type-map: ³»¿ëÇù»ó¿¡ »ç¿ëÇÒ + type mapÀ¸·Î ó¸®ÇÑ´Ù. + (mod_negotiation)
    • +
+
top
+
+

¿¹Á¦

+ + +

CGI ½ºÅ©¸³Æ®¸¦ »ç¿ëÇÏ¿© Á¤ÀûÀÎ ³»¿ë ¼öÁ¤Çϱâ

+ + +

´ÙÀ½ Áö½Ã¾î´Â È®ÀåÀÚ°¡ htmlÀÎ ÆÄÀÏÀ» + ¿äûÇÒ °æ¿ì footer.pl CGI ½ºÅ©¸³Æ®¸¦ ¶ç¿î´Ù.

+ +

+ Action add-footer /cgi-bin/footer.pl
+ AddHandler add-footer .html +

+ +

CGI ½ºÅ©¸³Æ®´Â + (PATH_TRANSLATED ȯ°æº¯¼ö°¡ ÁöĪÇÏ´Â) ¿ø·¡ + ¿äûÇÑ ¹®¼­¸¦ ÀûÀýÈ÷ ¼öÁ¤ÇÑ ÈÄ º¸³½´Ù.

+ + +

HTTP Çì´õ¸¦ Æ÷ÇÔÇÏ´Â ÆÄÀÏ

+ + +

´ÙÀ½ Áö½Ã¾î´Â HTTP Çì´õ¸¦ Æ÷ÇÔÇÏ´Â ÆÄÀÏ¿¡ + send-as-is Çڵ鷯¸¦ Áö½ÃÇÑ´Ù. + /web/htdocs/asis/ µð·ºÅ丮 ¾È¿¡ ÀÖ´Â ¸ðµç + ÆÄÀÏÀº È®ÀåÀÚ¿Í °ü°è¾øÀÌ send-as-is Çڵ鷯°¡ + ó¸®ÇÑ´Ù.

+ +

+ <Directory /web/htdocs/asis>
+ SetHandler send-as-is
+ </Directory> +

+ + +
top
+
+

ÇÁ·Î±×·¡¸Ó¸¦ À§ÇÑ Á¤º¸

+ + +

Çڵ鷯 ±â´ÉÀ» ±¸ÇöÇϱâÀ§ÇØ »ç¿ëÇÔÁ÷ÇÑ + Apache API°¡ Ãß°¡µÇ¾ú´Ù. + ƯÈ÷ request_rec ±¸Á¶Ã¼¿¡ »õ·Î¿î Çʵ尡 + Ãß°¡µÇ¾ú´Ù:

+ +

+ char *handler +

+ +

¸ðµâÀÌ Çڵ鷯¸¦ »ç¿ëÇÏ·Á¸é, ¿äûÀÇ + invoke_handler ´Ü°è ÀÌÀü¿¡ + r->handler¿¡ Çڵ鷯 À̸§À» ÁöÁ¤ÇØÁֱ⸸ + ÇÏ¸é µÈ´Ù. Çڵ鷯´Â content type ´ë½Å Çڵ鷯 À̸§À» »ç¿ëÇÑ + °ÍÀ» Á¦¿ÜÇÏ°í´Â Àü°ú °°ÀÌ ±¸ÇöµÇ¾ú´Ù. ²À Áöų ÇÊ¿ä´Â ¾øÁö¸¸ + Çڵ鷯 À̸§¿¡ ½½·¡½¬¸¦ »ç¿ëÇÏÁö ¾Ê°í, ´Ü¾îµé »çÀÌ¿¡ »©±â + ±âÈ£¸¦ »ç¿ëÇÏ´Â °ÍÀÌ ÀϹÝÀûÀÌ´Ù. ±×·¡¼­ Çڵ鷯 À̸§ÀÌ + media type°ú °ãÄ¡Áö ¾Ê´Â´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/handler.html.ru.koi8-r b/docs/manual/handler.html.ru.koi8-r new file mode 100644 index 00000000..20eec6cd --- /dev/null +++ b/docs/manual/handler.html.ru.koi8-r @@ -0,0 +1,167 @@ + + + +éÓÐÏÌØÚÏ×ÁÎÉÅ ÏÂÒÁÂÏÔÞÉËÏ× × Apache - HTTP ÓÅÒ×ÅÒ Apache + + + + +
+

íÏÄÕÌÉ | äÉÒÅËÔÉ×Ù | FAQ | çÌÏÓÓÁÒÉÊ | ëÁÒÔÁ ÓÁÊÔÁ

+

HTTP ÓÅÒ×ÅÒ Apache ×ÅÒÓÉÉ 2.2

+
+
<-
+
+Apache > HTTP ÓÅÒ×ÅÒ > äÏËÕÍÅÎÔÁÃÉÑ > ÷ÅÒÓÉÑ 2.2

éÓÐÏÌØÚÏ×ÁÎÉÅ ÏÂÒÁÂÏÔÞÉËÏ× × Apache

+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  en  | + es  | + ja  | + ko  | + ru 

+
+
üÔÏÔ ÐÅÒÅ×ÏÄ ÍÏÖÅÔ ÂÙÔØ ÕÓÔÁÒÅ×ÛÉÍ. óÍÏÔÒÉÔÅ + ÁÎÇÌÉÊÓËÕÀ ×ÅÒÓÉÀ ÄÌÑ ÏÚÎÁËÏÍÌÅÎÉÑ ÓÏ ×ÓÅÍÉ ÐÏÓÌÅÄÎÉÍÉ ÉÚÍÅÎÅÎÉÑÍÉ + × ÄÏËÕÍÅÎÔÅ.
+ +

üÔÏÔ ÄÏËÕÍÅÎÔ ÏÐÉÓÙ×ÁÅÔ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÏÂÒÁÂÏÔÞÉËÏ× (handlers) × Apache.

+
+ +
top
+
+

þÔÏ ÔÁËÏÅ ÏÂÒÁÂÏÔÞÉË

+ +
óÍÏÔÒÉÔÅ ÔÁËÖÅ ÍÏÄÕÌÉóÍÏÔÒÉÔÅ ÔÁËÖÅ ÄÉÒÅËÔÉ×Ù
+ + +

ïÂÒÁÂÏÔÞÉË Ñ×ÌÑÅÔÓÑ ×ÎÕÔÒÅÎÎÅÊ ÓÔÒÕËÔÕÒÏÊ + Apache, ËÏÔÏÒÁÑ ÚÁÄÁ£Ô ÐÏ×ÅÄÅÎÉÅ ÓÅÒ×ÅÒÁ ÐÒÉ ÏÂÒÁÂÏÔËÅ + ÚÁÐÒÁÛÉ×ÁÅÍÏÇÏ ÆÁÊÌÁ. ëÁË ÐÒÁ×ÉÌÏ, ËÁÖÄÏÍÕ ÆÁÊÌÕ ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ + Ó×ÏÊ ×ÎÕÔÒÅÎÎÉÊ ÏÂÒÁÂÏÔÞÉË, ËÏÔÏÒÙÊ ÎÁÚÎÁÞÁÅÔÓÑ ÓÅÒ×ÅÒÏÍ + ÉÓÈÏÄÑ ÉÚ ÔÉÐÁ ÆÁÊÌÁ. ïÂÙÞÎÏ ÆÁÊÌÙ ÐÒÏÓÔÏ ×ÏÚ×ÒÁÝÁÀÔÓÑ + ÐÏÌØÚÏ×ÁÔÅÌÀ, ÎÏ ÎÅËÏÔÏÒÙÅ ÔÉÐÙ ÆÁÊÌÏ× ÐÒÅÄ×ÁÒÉÔÅÌØÎÏ + ÏÂÒÁÂÁÔÙ×ÁÀÔÓÑ (handled) ÓÅÒ×ÅÒÏÍ.

+ +

÷ Apache 1.1 ÄÏÂÁ×ÌÅÎÁ ×ÏÚÍÏÖÎÏÓÔØ ÉÓÐÏÌØÚÏ×ÁÔØ ÏÂÒÁÂÏÔÞÉËÉ + Ñ×ÎÏ. ðÒÉÞ£Í ÏÂÒÁÂÏÔËÁ ÆÁÊÌÏ× ÍÏÖÅÔ ÏÓÎÏ×Ù×ÁÔØÓÑ + ÔÅÐÅÒØ ÎÅ ÔÏÌØËÏ ÎÁ ÉÈ ÔÉÐÅ, ÎÏ É ÎÁ ÒÁÓÛÉÒÅÎÉÉ ÆÁÊÌÏ× ÉÌÉ + ÉÈ ÍÅÓÔÏÎÁÈÏÖÄÅÎÉÉ. üÔÏ ÐÒÅÄÓÔÁ×ÌÑÅÔÓÑ ÎÁÉÂÏÌÅÅ ÕÄÁÞÎÙÍ + ÒÅÛÅÎÉÅÍ, ×Ï-ÐÅÒ×ÙÈ ÐÏÔÏÍÕ, ÞÔÏ ÜÔÏ ÒÅÛÅÎÉÅ ÜÌÅÇÁÎÔÎÏ, Á + ×Ï-×ÔÏÒÙÈ, ÜÔÏ ÐÏÚ×ÏÌÑÅÔ ÁÓÓÏÃÉÉÒÏ×ÁÔØ Ó ÆÁÊÌÏÍ ËÁË + ÔÉÐ, ÔÁË É ÏÂÒÁÂÏÔÞÉË. (óÍ. ÔÁËÖÅ + «æÁÊÌÙ Ó ÎÅÓËÏÌØËÉÍÉ + ÒÁÓÛÉÒÅÎÉÑÍÉ»)

+ +

ïÂÒÁÂÏÔÞÉËÉ ÍÏÇÕÔ ÐÒÅÄÓÔÁ×ÌÑÔØ ÉÚ ÓÅÂÑ ËÁË + ×ËÏÍÐÉÌÉÒÏ×ÁÎÎÙÅ × ÓÅÒ×ÅÒ (ÉÌÉ ÐÏÄËÌÀÞÁÅÍÙÅ Ó ÐÏÍÏÝØÀ + ÍÏÄÕÌÅÊ) ÆÕÎËÃÉÉ, ÉÌÉ ÏÎÉ ÍÏÇÕÔ ÂÙÔØ ÄÏÂÁ×ÌÅÎÙ Ó ÐÏÍÏÝØÀ + ÄÉÒÅËÔÉ×Ù Action. + ÷ ÓÔÁÎÄÁÒÔÎÏÍ ÄÉÓÔÒÉÂÕÔÉ×Å ÓÅÒ×ÅÒÁ ÉÍÅÀÔÓÑ ÓÌÅÄÕÀÝÉÅ ×ÓÔÒÏÅÎÎÙÅ + ÏÂÒÁÂÏÔÞÉËÉ:

+ +
    +
  • default-handler: ðÏÓÙÌÁÅÔ ÆÁÊÌ, ÉÓÐÏÌØÚÕÑ ÆÕÎËÃÉÀ + default_handler(), ËÏÔÏÒÁÑ Ñ×ÌÑÅÔÓÑ ÏÂÒÁÂÏÔÞÉËÏÍ + ÐÏ-ÕÍÏÌÞÁÎÉÀ ÄÌÑ ÓÔÁÔÉÞÅÓËÉÈ ÆÁÊÌÏ×. (ÑÄÒÏ)
    • + +
  • send-as-is: ðÏÓÙÌÁÅÔ ÆÁÊÌ, ÓÏÄÅÒÖÁÝÉÊ × + ÓÅÂÅ HTTP ÚÁÇÏÌÏ×ËÉ, ËÁË ÅÓÔØ. (mod_asis)
    • + +
  • cgi-script: ïÂÒÁÂÁÔÙ×ÁÅÔ ÆÁÊÌ ËÁË CGI-ÓËÒÉÐÔ. + (mod_cgi)
    • + +
  • imap-file: ïÂÒÁÂÁÔÙ×ÁÅÔ ÆÁÊÌ ËÁË ËÁÒÔÕ ÉÚÏÂÒÁÖÅÎÉÑ + (imagemap). (mod_imagemap)
    • + +
  • server-info: ÷ÏÚ×ÒÁÝÁÅÔ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÕÀ + ÉÎÆÏÒÍÁÃÉÀ ÓÅÒ×ÅÒÁ. (mod_info)
    • + +
  • server-status: ÷ÏÚ×ÒÁÝÁÅÔ ÏÔÞÅÔ Ï ÓÏÓÔÏÑÎÉÉ + ÓÅÒ×ÅÒÁ. (mod_status)
    • + +
  • type-map: ïÂÒÁÂÁÔÙ×ÁÅÔ ÆÁÊÌ ËÁË ËÁÒÔÕ ÔÉÐÏ× + (type map). (mod_negotiation)
    • +
+
top
+
+

ðÒÉÍÅÒÙ

+ + +

ïÂÒÁÂÏÔËÁ ÓÔÁÔÉÞÅÓËÏÇÏ ÄÏËÕÍÅÎÔÁ CGI-ÓËÒÉÐÔÏÍ

+ + +

ðÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ ÓÌÅÄÕÀÝÉÈ ÄÉÒÅËÔÉ×, ËÁÖÄÙÊ ÚÁÐÒÏÓ ÆÁÊÌÁ + Ó ÒÁÓÛÉÒÅÎÉÅÍ html ÂÕÄÅÔ ÚÁÐÕÓËÁÔØ ÎÁ ×ÙÐÏÌÎÅÎÉÅ + CGI-ÓËÒÉÐÔ footer.pl ÄÌÑ ÐÒÅÄ×ÁÒÉÔÅÌØÎÏÊ ÏÂÒÁÂÏÔËÉ + ÚÁÐÒÁÛÉ×ÁÅÍÏÇÏ ÆÁÊÌÁ.

+ +

+ Action add-footer /cgi-bin/footer.pl
+ AddHandler add-footer .html +

+ +

÷ ÜÔÏÍ ÓÌÕÞÁÅÔ CGI-ÓËÒÉÐÔ ÏÔ×ÅÔÓÔ×ÅÎÅÎ ÚÁ ÔÏ, ÞÔÏÂÙ + ×ÙÓÌÁÔØ ÐÏÌØÚÏ×ÁÔÅÌÀ ÚÁÐÒÏÛÅÎÎÙÊ ÄÏËÕÍÅÎÔ (ÎÁ ËÏÔÏÒÙÊ ÕËÁÚÙ×ÁÅÔ + ÐÅÒÅÍÅÎÎÁÑ ÏËÒÕÖÅÎÉÑ PATH_TRANSLATED), ÓÄÅÌÁ× + × Î£Í ÐÒÅÄ×ÁÒÉÔÅÌØÎÏ ×ÓÅ ÎÅÏÂÈÏÄÉÍÙÅ ÉÚÍÅÎÅÎÉÑ.

+ + +

æÁÊÌÙ Ó HTTP ÚÁÇÏÌÏ×ËÁÍÉ

+ + +

óÌÅÄÕÀÝÉÅ ÎÅÓËÏÌØËÏ ÄÉÒÅËÔÉ× ÚÁÓÔÁ×ÑÔ ×ÙÐÏÌÎÑÔØÓÑ ÏÂÒÁÂÏÔÞÉË + send-as-is, ËÏÔÏÒÙÊ ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÆÁÊÌÏ×, ÓÏÄÅÒÖÁÝÉÈ + Ó×ÏÉ ÓÏÂÓÔ×ÅÎÎÙÅ HTTP-ÚÁÇÏÌÏ×ËÉ. ÷ÓÅ ÆÁÊÌÙ × ËÁÔÁÌÏÇÅ + /web/htdocs/asis/ ÂÕÄÕÔ ÏÂÒÁÂÁÔÙ×ÁÔØÓÑ ÏÂÒÁÂÏÔÞÉËÏÍ + send-as-is, ÎÅÚÁ×ÉÓÉÍÏ ÏÔ ÉÈ ÒÁÓÛÉÒÅÎÉÑ.

+ +

+ <Directory /web/htdocs/asis>
+ SetHandler send-as-is
+ </Directory> +

+ + +
top
+
+

úÁÍÅÞÁÎÉÅ ÄÌÑ ÐÒÏÇÒÁÍÍÉÓÔÏ×

+ + +

äÌÑ ÔÏÇÏ ÞÔÏÂÙ ÍÏÖÎÏ ÂÙÌÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÏÂÒÁÂÏÔÞÉËÉ, × + Apache API ÂÙÌÉ ×ÎÅÓÅÎÙ + ÎÅËÏÔÏÒÙÅ ÄÏÐÏÌÎÅÎÉÑ. ÷ ÞÁÓÔÎÏÓÔÉ, × ÓÔÒÕËÔÕÒÕ request_rec + ÂÙÌÏ ÄÏÂÁ×ÌÅÎÏ ÎÏ×ÏÅ ÐÏÌÅ:

+ +

+ char *handler +

+ +

åÓÌÉ ×Ù ÈÏÔÉÔÅ × Ó×Ï£Í ÍÏÄÕÌÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÏÂÒÁÂÏÔÞÉË, + ÔÏ ×Ó£, ÞÔÏ ×ÁÍ ÎÁÄÏ ÓÄÅÌÁÔØ, ÜÔÏ ÚÁÐÉÓÁÔØ × r->handler + ÉÍÑ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÇÏ ÏÂÒÁÂÏÔÞÉËÁ, ÐÒÉÞ£Í ÓÄÅÌÁÔØ ÜÔÏ ÎÅÏÂÈÏÄÉÍÏ + ÐÅÒÅÄ ÔÅÍ, ËÁË ÚÁÐÒÏÓ ÄÏÈÏÄÉÔ ÄÏ ÓÔÁÄÉÉ invoke_handler. + ïÂÒÁÂÏÔÞÉËÉ ÒÅÁÌÉÚÕÀÔÓÑ ÔÏÞÎÏ ÔÁË ÖÅ, ËÁË É ÒÁÎØÛÅ, + ÚÁ ÉÓËÌÀÞÅÎÉÅÍ ÌÉÛØ ÔÏÇÏ, ÞÔÏ ÔÅÐÅÒØ ÎÅÏÂÈÏÄÉÍÏ ÕËÁÚÙ×ÁÔØ + ÉÍÑ ÏÂÒÁÂÏÔÞÉËÁ, Á ÎÅ ÔÉÐ ÓÏÄÅÒÖÉÍÏÇÏ (content type). + èÏÔÑ ÜÔÏ É ÎÅ Ñ×ÌÑÅÔÓÑ ÏÂÑÚÁÔÅÌØÎÙÍ, ÎÏ ÓÕÝÅÓÔ×ÕÀÔ ÓÌÅÄÕÀÝÉÅ + ÐÒÁ×ÉÌÁ ÉÍÅÎÏ×ÁÎÉÑ ÏÂÒÁÂÏÔÞÉËÏ× - ÎÅÏÂÈÏÄÉÍÏ ÉÓÐÏÌØÚÏ×ÁÔØ + ÓÌÏ×Á, ÒÁÚÄÅÌ£ÎÎÙÅ ÄÅÆÉÓÏÍ É ÎÅ ÓÏÄÅÒÖÁÝÉÅ ËÏÓÙÈ ÞÅÒÔ - ÜÔÏ + ÐÏÚ×ÏÌÉÔ ÎÅ ÐÅÒÅÓÅËÁÔØÓÑ Ó ÐÒÏÓÔÒÁÎÓÔ×ÏÍ ÉͣΠÍÅÄÉÁ-ÔÉÐÏ× (media type).

+
+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/access.html b/docs/manual/howto/access.html new file mode 100644 index 00000000..e4762a1e --- /dev/null +++ b/docs/manual/howto/access.html @@ -0,0 +1,3 @@ +URI: access.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/howto/access.html.en b/docs/manual/howto/access.html.en new file mode 100644 index 00000000..8b94ac9b --- /dev/null +++ b/docs/manual/howto/access.html.en @@ -0,0 +1,189 @@ + + + +Access Control - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

Access Control

+
+

Available Languages:  en 

+
+ +

Access control refers to any means of controlling access to any + resource. This is separate from authentication and authorization.

+
+ +
top
+
+

Related Modules and Directives

+ +

Access control can be done by several different modules. The most +important of these is mod_authz_host. Other modules +discussed in this document include mod_setenvif and +mod_rewrite.

+ +
top
+
+

Access control by host

+

+ If you wish to restrict access to portions of your site based on the + host address of your visitors, this is most easily done using + mod_authz_host. +

+ +

The Allow and + Deny directives let + you allow and deny access based on the host name, or host + address, of the machine requesting a document. The + Order directive goes + hand-in-hand with these two, and tells Apache in which order to + apply the filters.

+ +

The usage of these directives is:

+ +

+ Allow from address +

+ +

where address is an IP address (or a partial IP + address) or a fully qualified domain name (or a partial domain + name); you may provide multiple addresses or domain names, if + desired.

+ +

For example, if you have someone spamming your message + board, and you want to keep them out, you could do the + following:

+ +

+ Deny from 10.252.46.165 +

+ +

Visitors coming from that address will not be able to see + the content covered by this directive. If, instead, you have a + machine name, rather than an IP address, you can use that.

+ +

+ Deny from host.example.com +

+ +

And, if you'd like to block access from an entire domain, + you can specify just part of an address or domain name:

+ +

+ Deny from 192.168.205
+ Deny from phishers.example.com moreidiots.example
+ Deny from ke +

+ +

Using Order will let you + be sure that you are actually restricting things to the group that you want + to let in, by combining a Deny and an Allow directive:

+ +

+ Order deny,allow
+ Deny from all
+ Allow from dev.example.com +

+ +

Listing just the Allow + directive would not do what you want, because it will let folks from that + host in, in addition to letting everyone in. What you want is to let + only those folks in.

+
top
+
+

Access control by environment variable

+ +

+ mod_authz_host, in conjunction with + mod_setenvif, can be used to restrict access to + your website based on the value of arbitrary environment variables. + This is done with the Allow from env= and Deny + from env= syntax. +

+ +

+ SetEnvIf User-Agent BadBot GoAway=1
+ Order allow,deny
+ Allow from all
+ Deny from env=GoAway +

+ +

Warning:

+

Access control by User-Agent is an unreliable technique, + since the User-Agent header can be set to anything at all, + at the whim of the end user.

+
+ +

+ In the above example, the environment variable GoAway + is set to 1 if the User-Agent matches the + string BadBot. Then we deny access for any request when + this variable is set. This blocks that particular user agent from + the site. +

+ +

An environment variable test can be negated using the =! + syntax:

+ +

+ Allow from env=!GoAway +

+ +
top
+
+

Access control with mod_rewrite

+ +

The [F] RewriteRule flag causes a 403 Forbidden +response to be sent. Using this, you can deny access to a resource based +on arbitrary criteria.

+ +

For example, if you wish to block access to a resource between 8pm +and 6am, you can do this using mod_rewrite.

+ +

+RewriteEngine On
+RewriteCond %{TIME_HOUR} > 20 [OR]
+RewriteCond %{TIME_HOUR} < 07
+RewriteRule ^/fridge - [F] +

+ +

This will return a 403 Forbidden response for any request after 8pm +or before 7am. This technique can be used for any criteria that you wish +to check. You can also redirect, or otherwise rewrite these requests, if +that approach is preferred.

+ +
top
+
+

More information

+

You should also read the documentation for + mod_auth_basic and mod_authz_host which + contain some more information about how this all works. + mod_authn_alias can also help in simplifying certain + authentication configurations.

+ +

See the Authentication and Authorization + howto.

+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/auth.html b/docs/manual/howto/auth.html new file mode 100644 index 00000000..fddd9973 --- /dev/null +++ b/docs/manual/howto/auth.html @@ -0,0 +1,11 @@ +URI: auth.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: auth.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: auth.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/howto/auth.html.en b/docs/manual/howto/auth.html.en new file mode 100644 index 00000000..491abd15 --- /dev/null +++ b/docs/manual/howto/auth.html.en @@ -0,0 +1,391 @@ + + + +Authentication, Authorization and Access Control - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

Authentication, Authorization and Access Control

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

Authentication is any process by which you verify that + someone is who they claim they are. Authorization is any + process by which someone is allowed to be where they want to + go, or to have information that they want to have.

+
+ +
top
+
+

Related Modules and Directives

+ +

There are three types of modules involved in the authentication and +authorization process. You will usually need to choose at least one +module from each group.

+ + + +

The module mod_authnz_ldap is both an + authentication and authorization provider. The module + mod_authn_alias is not an authentication provider + in itself, but allows other authentication providers to be + configured in a flexible manner.

+ +

The module mod_authz_host provides authorization + and access control based on hostname, IP address or characteristics + of the request, but is not part of the authentication provider + system.

+ +

You probably also want to take a look at the Access Control howto, which discusses the + various ways to control access to your server.

+ +
top
+
+

Introduction

+

If you have information on your web site that is sensitive + or intended for only a small group of people, the techniques in + this article will help you make sure that the people that see + those pages are the people that you wanted to see them.

+ +

This article covers the "standard" way of protecting parts + of your web site that most of you are going to use.

+ +

Note:

+

If your data really needs to be secure, consider using + mod_ssl in addition to any authentication.

+
+
top
+
+

The Prerequisites

+

The directives discussed in this article will need to go + either in your main server configuration file (typically in a + <Directory> section), or + in per-directory configuration files (.htaccess files).

+ +

If you plan to use .htaccess files, you will + need to have a server configuration that permits putting + authentication directives in these files. This is done with the + AllowOverride directive, which + specifies which directives, if any, may be put in per-directory + configuration files.

+ +

Since we're talking here about authentication, you will need + an AllowOverride directive like the + following:

+ +

+ AllowOverride AuthConfig +

+ +

Or, if you are just going to put the directives directly in + your main server configuration file, you will of course need to + have write permission to that file.

+ +

And you'll need to know a little bit about the directory + structure of your server, in order to know where some files are + kept. This should not be terribly difficult, and I'll try to + make this clear when we come to that point.

+
top
+
+

Getting it working

+

Here's the basics of password protecting a directory on your + server.

+ +

First, you need to create a password file. Exactly how you do + this will vary depending on what authentication provider you have + chosen. More on that later. To start with, we'll use a text password + file.

+ +

This file should be + placed somewhere not accessible from the web. This is so that + folks cannot download the password file. For example, if your + documents are served out of /usr/local/apache/htdocs you + might want to put the password file(s) in + /usr/local/apache/passwd.

+ +

To create the file, use the htpasswd utility that + came with Apache. This will be located in the bin directory + of wherever you installed Apache. If you have installed Apache from + a third-party package, it may be in your execution path.

+ +

To create the file, type:

+ +

+ htpasswd -c /usr/local/apache/passwd/passwords rbowen +

+ +

htpasswd will ask you for the password, and + then ask you to type it again to confirm it:

+ +

+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen
+ New password: mypassword
+ Re-type new password: mypassword
+ Adding password for user rbowen +

+ +

If htpasswd is not in your path, of course + you'll have to type the full path to the file to get it to run. + With a default installation, it's located at + /usr/local/apache2/bin/htpasswd

+ +

Next, you'll need to configure the server to request a + password and tell the server which users are allowed access. + You can do this either by editing the httpd.conf + file or using an .htaccess file. For example, if + you wish to protect the directory + /usr/local/apache/htdocs/secret, you can use the + following directives, either placed in the file + /usr/local/apache/htdocs/secret/.htaccess, or + placed in httpd.conf inside a <Directory + /usr/local/apache/apache/htdocs/secret> section.

+ +

+ AuthType Basic
+ AuthName "Restricted Files"
+ # (Following line optional)
+ AuthBasicProvider file
+ AuthUserFile /usr/local/apache/passwd/passwords
+ Require user rbowen +

+ +

Let's examine each of those directives individually. The AuthType directive selects + that method that is used to authenticate the user. The most + common method is Basic, and this is the method + implemented by mod_auth_basic. It is important to be aware, + however, that Basic authentication sends the password from the client to + the server unencrypted. This method should therefore not be used for + highly sensitive data, unless accompanied by mod_ssl. + Apache supports one other authentication method: + AuthType Digest. This method is implemented by mod_auth_digest and is much more secure. Most recent + browsers support Digest authentication.

+ +

The AuthName directive sets + the Realm to be used in the authentication. The realm serves + two major functions. First, the client often presents this information to + the user as part of the password dialog box. Second, it is used by the + client to determine what password to send for a given authenticated + area.

+ +

So, for example, once a client has authenticated in the + "Restricted Files" area, it will automatically + retry the same password for any area on the same server that is + marked with the "Restricted Files" Realm. + Therefore, you can prevent a user from being prompted more than + once for a password by letting multiple restricted areas share + the same realm. Of course, for security reasons, the client + will always need to ask again for the password whenever the + hostname of the server changes.

+ +

The AuthBasicProvider is, + in this case, optional, since file is the default value + for this directive. You'll need to use this directive if you are + choosing a different source for authentication, such as + mod_authn_dbm or mod_authn_dbd.

+ +

The AuthUserFile + directive sets the path to the password file that we just + created with htpasswd. If you have a large number + of users, it can be quite slow to search through a plain text + file to authenticate the user on each request. Apache also has + the ability to store user information in fast database files. + The mod_authn_dbm module provides the AuthDBMUserFile directive. These + files can be created and manipulated with the dbmmanage program. Many + other types of authentication options are available from third + party modules in the Apache Modules + Database.

+ +

Finally, the Require + directive provides the authorization part of the process by + setting the user that is allowed to access this region of the + server. In the next section, we discuss various ways to use the + Require directive.

+
top
+
+

Letting more than one +person in

+

The directives above only let one person (specifically + someone with a username of rbowen) into the + directory. In most cases, you'll want to let more than one + person in. This is where the AuthGroupFile comes in.

+ +

If you want to let more than one person in, you'll need to + create a group file that associates group names with a list of + users in that group. The format of this file is pretty simple, + and you can create it with your favorite editor. The contents + of the file will look like this:

+ +

+ GroupName: rbowen dpitts sungo rshersey +

+ +

That's just a list of the members of the group in a long + line separated by spaces.

+ +

To add a user to your already existing password file, + type:

+ +

+ htpasswd /usr/local/apache/passwd/passwords dpitts +

+ +

You'll get the same response as before, but it will be + appended to the existing file, rather than creating a new file. + (It's the -c that makes it create a new password + file).

+ +

Now, you need to modify your .htaccess file to + look like the following:

+ +

+ AuthType Basic
+ AuthName "By Invitation Only"
+ # Optional line: + AuthBasicProvider file + AuthUserFile /usr/local/apache/passwd/passwords
+ AuthGroupFile /usr/local/apache/passwd/groups
+ Require group GroupName +

+ +

Now, anyone that is listed in the group GroupName, + and has an entry in the password file, will be let in, if + they type the correct password.

+ +

There's another way to let multiple users in that is less + specific. Rather than creating a group file, you can just use + the following directive:

+ +

+ Require valid-user +

+ +

Using that rather than the Require user rbowen + line will allow anyone in that is listed in the password file, + and who correctly enters their password. You can even emulate + the group behavior here, by just keeping a separate password + file for each group. The advantage of this approach is that + Apache only has to check one file, rather than two. The + disadvantage is that you have to maintain a bunch of password + files, and remember to reference the right one in the + AuthUserFile directive.

+
top
+
+

Possible problems

+

Because of the way that Basic authentication is specified, + your username and password must be verified every time you + request a document from the server. This is even if you're + reloading the same page, and for every image on the page (if + they come from a protected directory). As you can imagine, this + slows things down a little. The amount that it slows things + down is proportional to the size of the password file, because + it has to open up that file, and go down the list of users + until it gets to your name. And it has to do this every time a + page is loaded.

+ +

A consequence of this is that there's a practical limit to + how many users you can put in one password file. This limit + will vary depending on the performance of your particular + server machine, but you can expect to see slowdowns once you + get above a few hundred entries, and may wish to consider a + different authentication method at that time.

+
top
+
+

Alternate password storage

+ +

Because storing passwords in plain text files has the above + problems, you may wish to store your passwords somewhere else, such + as in a database.

+ +

mod_authn_dbm and mod_authn_dbd + are two modules which make this possible. Rather than selecting + AuthBasicSource file, + instead you can choose dbm or dbd as your + storage format.

+ +

To select a dbd file rather than a text file, for example:

+ +

+ <Directory /www/docs/private>
+ AuthName "Private"
+ AuthType Basic
+ AuthBasicProvider dbm
+ AuthDBMUserFile /www/passwords/passwd.dbm
+ Require valid-user +

+ +

Other options are available. Consult the + mod_authn_dbm documentation for more details.

+
top
+
+

More information

+

You should also read the documentation for + mod_auth_basic and mod_authz_host which + contain some more information about how this all works. + mod_authn_alias can also help in simplifying certain + authentication configurations.

+ +

And you may want to look at the Access + Control howto, which discusses a number of related topics.

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/auth.html.ja.euc-jp b/docs/manual/howto/auth.html.ja.euc-jp new file mode 100644 index 00000000..73e85d12 --- /dev/null +++ b/docs/manual/howto/auth.html.ja.euc-jp @@ -0,0 +1,386 @@ + + + +ǧ¾Ú¡¢¾µÇ§¡¢¥¢¥¯¥»¥¹À©¸æ - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë

ǧ¾Ú¡¢¾µÇ§¡¢¥¢¥¯¥»¥¹À©¸æ

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +

¡Öǧ¾Ú¡×¤È¤Ï¡¢Ã¯¤«¤¬¼«Ê¬¤Ïï¤Ç¤¢¤ë¤«¤ò¼çÄ¥¤·¤¿¾ì¹ç¤Ë¡¢ + ¤½¤ì¤ò³Îǧ¤¹¤ë¤¿¤á¤ÎÁ´²áÄø¤ò»Ø¤·¤Þ¤¹¡£¡Ö¾µÇ§¡×¤È¤Ï¡¢ + 狼¤¬¹Ô¤­¤¿¤¤¾ì½ê¤Ë¹Ô¤±¤ë¤è¤¦¤Ë¡¢¤¢¤ë¤¤¤ÏÍߤ·¤¤¾ðÊó¤ò + ÆÀ¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤ÎÁ´²áÄø¤ò»Ø¤·¤Þ¤¹¡£

+
+ +
top
+
+

´ØÏ¢¤¹¤ë¥â¥¸¥å¡¼¥ë¤È¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+
top
+
+

¤Ï¤¸¤á¤Ë

+

¤â¤·µ¡Ì©¤Î¾ðÊó¤ä¡¢¤´¤¯¤´¤¯¾¯¿ô¥°¥ë¡¼¥×¤Î¿Í¸þ¤±¤Î¾ðÊó¤ò + ¥¦¥§¥Ö¥µ¥¤¥È¤ËÃÖ¤¯¤Î¤Ç¤¢¤ì¤Ð¡¢¤³¤Îʸ½ñ¤Ë½ñ¤«¤ì¤Æ¤¤¤ë + ¥Æ¥¯¥Ë¥Ã¥¯¤ò»È¤¦¤³¤È¤Ç¡¢¤½¤Î¥Ú¡¼¥¸¤ò¸«¤Æ¤¤¤ë¿Í¤¿¤Á¤¬ + ˾¤ß¤Î¿Í¤¿¤Á¤Ç¤¢¤ë¤³¤È¤ò³Î¼Â¤Ë¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£

+ +

¤³¤Îʸ½ñ¤Ç¤Ï¡¢Â¿¤¯¤Î¿Í¤¬ºÎÍѤ¹¤ë¤Ç¤¢¤í¤¦¡¢ + ¥¦¥§¥Ö¥µ¥¤¥È¤Î°ìÉôʬ¤òÊݸ¤ë¡Ö°ìÈÌŪ¤Ê¡× + ÊýË¡¤Ë¤Ä¤¤¤Æ¥«¥Ð¡¼¤·¤Æ¤¤¤Þ¤¹¡£

+
top
+
+

½àÈ÷

+

¤³¤Îʸ½ñ¤Ç¼è¤ê°·¤ï¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥á¥¤¥ó¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë (ÉáÄÌ¤Ï + <Directory> + ¥»¥¯¥·¥ç¥óÃæ) ¤«¡¢¤¢¤ë¤¤¤Ï¥Ç¥£¥ì¥¯¥È¥êËè¤ÎÀßÄê¥Õ¥¡¥¤¥ë + (.htaccess ¥Õ¥¡¥¤¥ë) ¤«¤ÇÍѤ¤¤Þ¤¹¡£

+ +

.htaccess ¥Õ¥¡¥¤¥ë¤òÍѤ¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ëǧ¾ÚÍѤΥǥ£¥ì¥¯¥Æ¥£¥Ö¤òÃÖ¤±¤ë¤è¤¦¤Ë + ¥µ¡¼¥Ð¤ÎÀßÄê¤ò¤·¤Ê¤¤¤È¤¤¤±¤Ê¤¤¤Ç¤·¤ç¤¦¡£¤³¤ì¤Ï + AllowOverride + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç²Äǽ¤Ë¤Ê¤ê¤Þ¤¹¡£ + AllowOverride + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥êËè¤ÎÀßÄê¥Õ¥¡¥¤¥ëÃæ¤ËÃÖ¤¯¤³¤È¤Î¤Ç¤­¤ë + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¡¢¤â¤·¤¢¤ì¤Ð¡¢»ØÄꤷ¤Þ¤¹¡£

+ +

ǧ¾Ú¤Ë¤Ä¤¤¤ÆÏäò¿Ê¤á¤Æ¤¤¤ë¤Î¤Ç¡¢¼¡¤Î¤è¤¦¤Ê + AllowOverride + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬É¬Íפˤʤë¤Ç¤·¤ç¤¦¡£

+ +

+ AllowOverride AuthConfig +

+ +

¤½¤¦¤Ç¤Ê¤¯¡¢¥á¥¤¥ó¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤ÎÃæ¤Ë + ľÀÜÃÖ¤¯¤Î¤Ç¤¢¤ì¤Ð¡¢ÅöÁ³¤Ê¤¬¤é¤½¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î½ñ¤­¹þ¤ß + ¸¢¸Â¤ò»ý¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤Ç¤·¤ç¤¦¡£

+ +

¤Þ¤¿¡¢¤É¤Î¥Õ¥¡¥¤¥ë¤¬¤É¤³¤ËÊݸ¤µ¤ì¤Æ¤¤¤ë¤«ÃΤ뤿¤á¤Ë¡¢ + ¥µ¡¼¥Ð¤Î¥Ç¥£¥ì¥¯¥È¥ê¹½Â¤¤Ë¤Ä¤¤¤Æ¾¯¤·ÃΤäƤª¤¯ + ɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£ + ¤³¤ì¤Ï¤½¤ó¤Ê¤ËÆñ¤·¤¯¤Ê¤¤¤Î¤Ç¡¢¤³¤Îʸ½ñÃæ¤Ç + ¥Ç¥£¥ì¥¯¥È¥ê¹½Â¤¤Ë¤Ä¤¤¤ÆÃΤäƤª¤¯É¬Íפ¬¤¢¤ë¾ìÌ̤Ǥϡ¢ + ÌÀ¤é¤«¤Ë¤Ê¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£

+
top
+
+

Æ°ºî¤µ¤»¤ë

+

¤Ç¤Ï¡¢¥µ¡¼¥Ð¾å¤Î¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ò¥Ñ¥¹¥ï¡¼¥É¤ÇÊݸ¤ë + ´ðËܼê½ç¤ò¼¨¤·¤Þ¤¹¡£

+ +

¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤òºî¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¥Õ¥¡¥¤¥ë¤Ï¡¢¥¦¥§¥Ö¤«¤é¥¢¥¯¥»¥¹¤Ç¤­¤ë¾ì½ê¤Ë + ÃÖ¤¯¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£Â¾¤Î¿Í¤¬¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤ò + ¥À¥¦¥ó¥í¡¼¥É¤Ç¤­¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ç¤¹¡£Î㤨¤Ð¡¢ + /usr/local/apache/htdocs ¤Ç¥É¥­¥å¥á¥ó¥È¤ò + Ä󶡤·¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤Ï + /usr/local/apache/passwd + ¤Ê¤É¤ËÃÖ¤¤¤¿Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+ +

¥Õ¥¡¥¤¥ë¤òºî¤ë¤¿¤á¤Ë¤Ï¡¢Apache ÉÕ°¤Î htpasswd + ¤ò»È¤¤¤Þ¤¹¡£¤³¤Î¥³¥Þ¥ó¥É¤Ï Apache ¤ò¤É¤³¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤·¤è¤¦¤È¤â¡¢ + ¥¤¥ó¥¹¥È¡¼¥ë¥Ç¥£¥ì¥¯¥È¥ê¤Î bin + ¥Ç¥£¥ì¥¯¥È¥ê°Ê²¼¤ËÃÖ¤«¤ì¤Þ¤¹¡£¥Õ¥¡¥¤¥ë¤òºî¤ë¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë + ¥¿¥¤¥×¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ htpasswd -c /usr/local/apache/passwd/passwords rbowen +

+ +

htpasswd ¤Ï¡¢¥Ñ¥¹¥ï¡¼¥É¤òÍ׵ᤷ¡¢¤½¤Î¸å + ³Îǧ¤Î¤¿¤á¤Ë¤â¤¦°ìÅÙÆþÎϤ¹¤ë¤è¤¦¤ËÍ׵ᤷ¤Æ¤­¤Þ¤¹¡£

+ +

+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen
+ New password: mypassword
+ Re-type new password: mypassword
+ Adding password for user rbowen +

+ +

¤â¤· htpasswd ¤¬¥Ñ¥¹¤ÎÃæ¤ËÆþ¤Ã¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ï¡¢ + ¤â¤Á¤í¤ó¡¢¼Â¹Ô¤¹¤ë¤¿¤á¤Ë¥×¥í¥°¥é¥à¤Þ¤Ç¤Î¥Õ¥ë¥Ñ¥¹¤ò + ¥¿¥¤¥×¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£»ä¤Î¥µ¡¼¥Ð¤Ç¤¢¤ì¤Ð¡¢ + /usr/local/apache/bin/htpasswd + ¤Ë¥×¥í¥°¥é¥à¤¬ÃÖ¤«¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

¼¡¤Ë¡¢¥µ¡¼¥Ð¤¬¥Ñ¥¹¥ï¡¼¥É¤òÍ׵᤹¤ë¤è¤¦¤ËÀßÄꤷ¤Æ¡¢ + ¤É¤Î¥æ¡¼¥¶¤¬¥¢¥¯¥»¥¹¤òµö¤µ¤ì¤Æ¤¤¤ë¤«¤ò¥µ¡¼¥Ð¤ËÃΤ餻¤Ê¤±¤ì¤Ð + ¤Ê¤ê¤Þ¤»¤ó¡£ httpd.conf ¤òÊÔ½¸¤¹¤ë¤« + .htaccess ¥Õ¥¡¥¤¥ë¤ò»ÈÍѤ¹¤ë¤«¤Ç + ÀßÄꤷ¤Þ¤¹¡£Î㤨¤Ð¡¢¥Ç¥£¥ì¥¯¥È¥ê + /usr/local/apache/htdocs/secret + ¤òÊݸ¤¿¤¤¾ì¹ç¤Ï¡¢ + /usr/local/apache/htdocs/secret/.htaccess + ¤« httpd.conf Ãæ¤Î <Directory + /usr/local/apache/apache/htdocs/secret> ¥»¥¯¥·¥ç¥ó¤Ë + ÇÛÃÖ¤·¤Æ¡¢¼¡¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ AuthType Basic
+ AuthName "Restricted Files"
+ AuthUserFile /usr/local/apache/passwd/passwords
+ Require user rbowen +

+ +

¸Ä¡¹¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤Ä¤¤¤Æ¸«¤Æ¤ß¤Þ¤·¤ç¤¦¡£ + AuthType + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤É¤¦¤¤¤¦Ç§¾ÚÊýË¡¤Ç¥æ¡¼¥¶¤Îǧ¾Ú¤ò¹Ô¤¦¤«¤ò + ÁªÂò¤·¤Þ¤¹¡£ºÇ¤â°ìÈÌŪ¤ÊÊýË¡¤Ï Basic + ¤Ç¡¢¤³¤ì¤Ï mod_auth_basic + ¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤·¤«¤·¤Ê¤¬¤é¡¢ + ¤³¤ì¤Ïµ¤¤òÉÕ¤±¤ë¤Ù¤­½ÅÍפʥݥ¤¥ó¥È¤Ê¤Î¤Ç¤¹¤¬¡¢ + Basic ǧ¾Ú¤Ï¥¯¥é¥¤¥¢¥ó¥È¤«¤é¥µ¡¼¥Ð¤Ø¡¢ + ¥Ñ¥¹¥ï¡¼¥É¤ò°Å¹æ²½¤»¤º¤ËÁ÷¤ê¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢ + ¤³¤ÎÊýË¡¤ÏÆä˵¡Ì©À­¤Î¹â¤¤¥Ç¡¼¥¿¤ËÂФ·¤Æ¤ÏÍѤ¤¤ë¤Ù¤­¤Ç¤Ï + ¤¢¤ê¤Þ¤»¤ó¡£ Apache ¤Ç¤Ï¤â¤¦°ì¤ÄÊ̤Îǧ¾ÚÊýË¡: + AuthType Digest ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤¹¡£ + ¤³¤ÎÊýË¡¤Ï mod_auth_digest + ¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤Æ¡¢¤â¤Ã¤È°ÂÁ´¤Ç¤¹¡£ + ¤´¤¯¤´¤¯ºÇ¶á¤Î¥¯¥é¥¤¥¢¥ó¥È¤·¤« Digest + ǧ¾Ú¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Ê¤¤¤è¤¦¤Ç¤¹¡£

+ +

AuthName + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï¡¢Ç§¾Ú¤Ë»È¤¦ Realm (ÌõÃí: Îΰè) + ¤òÀßÄꤷ¤Þ¤¹¡£Realm ¤ÏÂ礭¤¯Ê¬¤±¤ÆÆó¤Ä¤Îµ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£ + °ì¤ÄÌܤϡ¢¥¯¥é¥¤¥¢¥ó¥È¤¬¥Ñ¥¹¥ï¡¼¥É¥À¥¤¥¢¥í¥°¥Ü¥Ã¥¯¥¹¤Î + °ìÉô¤È¤·¤Æ¥æ¡¼¥¶¤Ë¤³¤Î¾ðÊó¤ò¤è¤¯Ä󼨤¹¤ë¡¢¤È¤¤¤¦¤â¤Î¤Ç¤¹¡£ + Æó¤ÄÌܤˤϡ¢¥¯¥é¥¤¥¢¥ó¥È¤¬Í¿¤¨¤é¤ì¤¿Ç§¾ÚÎΰè¤ËÂФ·¤Æ¤É¤Î¥Ñ¥¹¥ï¡¼¥É¤ò + Á÷¿®¤¹¤ì¤ÐÎɤ¤¤Î¤«¤ò·èÄꤹ¤ë¤¿¤á¤Ë»È¤ï¤ì¤ë¡¢¤È¤¤¤¦µ¡Ç½¤Ç¤¹¡£

+ +

Î㤨¤Ð¡¢"Restricted Files" ÎΰèÃæ¤Ç + °ìÅÙǧ¾Ú¤µ¤ì¤ì¤Ð¡¢Æ±°ì¥µ¡¼¥Ð¾å¤Ç "Restricted Files" + Realm ¤È¤·¤Æ¥Þ¡¼¥¯¤µ¤ì¤¿¤É¤ó¤ÊÎΰè¤Ç¤â¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï + ¼«Æ°Åª¤ËƱ¤¸¥Ñ¥¹¥ï¡¼¥É¤ò»È¤ª¤¦¤È»î¤ß¤Þ¤¹¡£ + ¤³¤Î¤ª¤«¤²¤Ç¡¢Ê£¿ô¤ÎÀ©¸ÂÎΰè¤ËƱ¤¸ realm ¤ò¶¦Í­¤µ¤»¤Æ¡¢ + ¥æ¡¼¥¶¤¬¥Ñ¥¹¥ï¡¼¥É¤ò²¿ÅÙ¤âÍ׵ᤵ¤ì¤ë»öÂÖ¤ò + Ëɤ°¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤â¤Á¤í¤ó¡¢¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÍýͳ¤«¤é¡¢ + ¥µ¡¼¥Ð¤Î¥Û¥¹¥È̾¤¬ÊѤï¤ì¤Ð¤¤¤Ä¤Ç¤âɬ¤º¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤ÏºÆ¤Ó¥Ñ¥¹¥ï¡¼¥É¤ò¿Ò¤Í¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

AuthUserFile + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï htpasswd ¤Çºî¤Ã¤¿ + ¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤Ø¤Î¥Ñ¥¹¤òÀßÄꤷ¤Þ¤¹¡£ + ¥æ¡¼¥¶¿ô¤¬Â¿¤¤¾ì¹ç¤Ï¡¢¥ê¥¯¥¨¥¹¥ÈËè¤Î¥æ¡¼¥¶¤Îǧ¾Ú¤Î¤¿¤á¤Î + ¥×¥ì¡¼¥ó¥Æ¥­¥¹¥È¤Îõº÷¤¬Èó¾ï¤ËÃÙ¤¯¤Ê¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + Apache ¤Ç¤Ï¥æ¡¼¥¶¾ðÊó¤ò¹â®¤Ê¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤Ë + Êݴɤ¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + mod_authn_dbm ¥â¥¸¥å¡¼¥ë¤¬ + AuthDBMUserFile + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÄ󶡤·¤Þ¤¹¡£¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ï dbmmanage + ¥×¥í¥°¥é¥à¤ÇºîÀ®¤·¤¿¤êÁàºî¤·¤¿¤ê¤Ç¤­¤Þ¤¹¡£ + Apache + ¥â¥¸¥å¡¼¥ë¥Ç¡¼¥¿¥Ù¡¼¥¹Ãæ¤Ë¤¢¤ë¥µ¡¼¥É¥Ñ¡¼¥Æ¥£¡¼À½¤Î + ¥â¥¸¥å¡¼¥ë¤Ç¡¢¤½¤Î¾¿¤¯¤Î¥¿¥¤¥×¤Îǧ¾Ú¥ª¥×¥·¥ç¥ó¤¬ + ÍøÍѲÄǽ¤Ç¤¹¡£

+ +

ºÇ¸å¤Ë¡¢Require + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¡¢¥µ¡¼¥Ð¤Î¤³¤ÎÎΰè¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¥æ¡¼¥¶¤ò + »ØÄꤹ¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢¥×¥í¥»¥¹¤Î¾µÇ§Éôʬ¤òÄ󶡤·¤Þ¤¹¡£ + ¼¡¤Î¥»¥¯¥·¥ç¥ó¤Ç¤Ï¡¢Require + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÍÍ¡¹¤ÊÍÑË¡¤Ë¤Ä¤¤¤Æ½Ò¤Ù¤Þ¤¹¡£

+
top
+
+

+Ê£¿ô¤Î¿Í¤¬Æþ¤ì¤ë¤è¤¦¤Ë¤¹¤ë

+

¾åµ­¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¤¿¤À°ì¿Í (¶ñÂÎŪ¤Ë¤Ï¥æ¡¼¥¶Ì¾ + rbowen ¤Î狼) ¤¬¥Ç¥£¥ì¥¯¥È¥ê¤Ë + Æþ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£Â¿¤¯¤Î¾ì¹ç¤Ï¡¢Ê£¿ô¤Î¿Í¤¬ + Æþ¤ì¤ë¤è¤¦¤Ë¤·¤¿¤¤¤Ç¤·¤ç¤¦¡£¤³¤³¤Ç + AuthGroupFile + ¤ÎÅоì¤Ç¤¹¡£

+ +

¤â¤·Ê£¿ô¤Î¿Í¤¬Æþ¤ì¤ë¤è¤¦¤Ë¤·¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¥°¥ë¡¼¥×¤Ë°¤¹¤ë¥æ¡¼¥¶¤Î°ìÍ÷¤ÎÆþ¤Ã¤Æ¤¤¤ë¡¢¥°¥ë¡¼¥×̾¤Î¤Ä¤¤¤¿ + ¥°¥ë¡¼¥×¥Õ¥¡¥¤¥ë¤òºî¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤³¤Î¥Õ¥¡¥¤¥ë¤Î + ½ñ¼°¤Ï¤­¤ï¤á¤Æñ½ã¤Ç¡¢¤ª¹¥¤ß¤Î¥¨¥Ç¥£¥¿¤ÇÀ¸À®¤Ç¤­¤Þ¤¹¡£ + ¥Õ¥¡¥¤¥ë¤ÎÃæ¿È¤Ï¼¡¤Î¤è¤¦¤Ê¤â¤Î¤Ç¤¹¡£

+ +

+ GroupName: rbowen dpitts sungo rshersey +

+ +

°ì¹Ô¤Ë¥¹¥Ú¡¼¥¹¶èÀÚ¤ê¤Ç¡¢¥°¥ë¡¼¥×¤Ë½ê°¤¹¤ë¥á¥ó¥Ð¡¼¤Î + °ìÍ÷¤ò¤Ê¤é¤Ù¤ë¤À¤±¤Ç¤¹¡£

+ +

´û¤Ë¸ºß¤¹¤ë¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤Ë¥æ¡¼¥¶¤ò²Ã¤¨¤ë¾ì¹ç¤Ï¡¢ + ¼¡¤Î¤è¤¦¤Ë¥¿¥¤¥×¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ htpasswd /usr/local/apache/passwd/passwords dpitts +

+ +

°ÊÁ°¤ÈƱ¤¸±þÅú¤¬ÊÖ¤µ¤ì¤Þ¤¹¤¬¡¢¿·¤·¤¤¥Õ¥¡¥¤¥ë¤ò + ºî¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢´û¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¤ËÄɲ䵤ì¤Æ¤¤¤Þ¤¹¡£ + (¿·¤·¤¤¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤òºî¤ë¤Ë¤Ï -c + ¤ò»È¤¤¤Þ¤¹¡£)

+ +

¤³¤³¤Ç¼¡¤Î¤è¤¦¤Ë¤·¤Æ .htaccess ¥Õ¥¡¥¤¥ë¤ò + ½¤Àµ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

+ AuthType Basic
+ AuthName "By Invitation Only"
+ AuthUserFile /usr/local/apache/passwd/passwords
+ AuthGroupFile /usr/local/apache/passwd/groups
+ Require group GroupName +

+ +

¤³¤ì¤Ç¡¢¥°¥ë¡¼¥× GroupName ¤Ë¥ê¥¹¥È¤µ¤ì¤Æ¤¤¤Æ¡¢ + password ¥Õ¥¡¥¤¥ë¤Ë¥¨¥ó¥È¥ê¤¬¤¢¤ë¿Í¤Ï¡¢ + Àµ¤·¤¤¥Ñ¥¹¥ï¡¼¥É¤ò¥¿¥¤¥×¤¹¤ì¤ÐÆþ¤ë¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£

+ +

¤â¤Ã¤ÈÆÃÄꤻ¤º¤ËÊ£¿ô¤Î¥æ¡¼¥¶¤¬Æþ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¡¢ + ¤â¤¦°ì¤Ä¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£¥°¥ë¡¼¥×¥Õ¥¡¥¤¥ë¤òºî¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢ + ¼¡¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¨¤Ð¤Ç¤­¤Þ¤¹¡£

+ +

+ Require valid-user +

+ +

require user rbowen ¹Ô¤Ç¤Ê¤¯¡¢¾åµ­¤ò»È¤¦¤È¡¢ + ¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤Ë¥ê¥¹¥È¤µ¤ì¤Æ¤¤¤ë¿Í¤Ç¤¢¤ì¤Ðï¤Ç¤â + µö²Ä¤µ¤ì¤Þ¤¹¡£ + ñ¤Ë¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤ò¥°¥ë¡¼¥×Ëè¤Ëʬ¤±¤Æ¤ª¤¯¤³¤È¤Ç¡¢ + ¥°¥ë¡¼¥×¤Î¤è¤¦¤Ê¿¶¤ëÉñ¤¤¤ò¤µ¤»¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¥¢¥×¥í¡¼¥Á¤ÎÍøÅÀ¤Ï¡¢Apache ¤ÏÆó¤Ä¤Ç¤Ï¤Ê¤¯¡¢ + ¤¿¤À°ì¤Ä¤Î¥Õ¥¡¥¤¥ë¤À¤±¤ò¸¡ºº¤¹¤ì¤Ð¤è¤¤¤È¤¤¤¦ÅÀ¤Ç¤¹¡£ + ·çÅÀ¤Ï¡¢¤¿¤¯¤µ¤ó¤Î¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤ò´ÉÍý¤·¤Æ¡¢¤½¤ÎÃ椫¤é + AuthUserFile + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ËÀµ¤·¤¤¥Õ¥¡¥¤¥ë¤ò»²¾È¤µ¤»¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤ÅÀ¤Ç¤¹¡£

+
top
+
+

µ¯¤³¤ê¤¨¤ëÌäÂê

+

Basic ǧ¾Ú¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥µ¡¼¥Ð¤Ë¥É¥­¥å¥á¥ó¥È¤ò¥ê¥¯¥¨¥¹¥È¤¹¤ëÅÙ¤Ë + ¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤ò¸¡ºº¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤³¤ì¤ÏƱ¤¸¥Ú¡¼¥¸¡¢¥Ú¡¼¥¸¤Ë¤¢¤ëÁ´¤Æ¤Î²èÁü¤ò + ¥ê¥í¡¼¥É¤¹¤ë¾ì¹ç¤Ç¤¢¤Ã¤Æ¤â³ºÅö¤·¤Þ¤¹ + (¤â¤·²èÁü¤âÊݸ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤«¤éÍè¤ë¤Î¤Ç¤¢¤ì¤Ð) ¡£ + ͽÁÛ¤µ¤ì¤ëÄ̤ꡢ¤³¤ì¤ÏÆ°ºî¤ò¿¾¯ÃÙ¤¯¤·¤Þ¤¹¡£ + ÃÙ¤¯¤Ê¤ëÄøÅ٤ϥѥ¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤ÎÂ礭¤µ¤ÈÈæÎ㤷¤Þ¤¹¤¬¡¢ + ¤³¤ì¤Ï¡¢¥Õ¥¡¥¤¥ë¤ò³«¤¤¤Æ¤¢¤Ê¤¿¤Î̾Á°¤òȯ¸«¤¹¤ë¤Þ¤Ç + ¥æ¡¼¥¶Ì¾¤Î¥ê¥¹¥È¤òÆɤޤʤ±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤é¤Ç¤¹¡£ + ¤½¤·¤Æ¡¢¥Ú¡¼¥¸¤¬¥í¡¼¥É¤µ¤ì¤ëÅ٤ˤ³¤ì¤ò¹Ô¤ï¤Ê¤±¤ì¤Ð + ¤Ê¤ê¤Þ¤»¤ó¡£

+ +

·ëÏÀ¤È¤·¤Æ¤Ï¡¢°ì¤Ä¤Î¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤ËÃÖ¤¯¤³¤È¤Î¤Ç¤­¤ë + ¥æ¡¼¥¶¿ô¤Ë¤Ï¼Â¼ÁŪ¤Ê¸Â³¦¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¸Â³¦¤Ï¥µ¡¼¥Ð¥Þ¥·¥ó¤ÎÀ­Ç½¤Ë°Í¸¤·¤ÆÊѤï¤ê¤Þ¤¹¤¬¡¢ + ¿ôÉ´¤Î¥¨¥ó¥È¥ê¤ò±Û¤¨¤¿¤¢¤¿¤ê¤«¤é®ÅÙÄã²¼¤¬¸«¤é¤ì¤ë¤Èͽ´ü¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤½¤Î»þ¤Ï¾¤Îǧ¾ÚÊýË¡¤ò¹Íθ¤ËÆþ¤ì¤¿Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+
top
+
+

¤â¤Ã¤È¹ª¤ß¤ËÀ©¸æ¤Ç¤­¤Ê¤¤ +?

+

¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤Ë¤è¤ëǧ¾Ú¤Ïǧ¾Ú¤Î°ì¤Ä¤ÎÊýË¡¤Ë²á¤®¤Þ¤»¤ó¡£ + ¤·¤Ð¤·¤Ðï¤Ç¤¢¤ë¤«¤È¤¤¤¦¤³¤È¤È¤Ï°ã¤¦²¿¤«¤Ë´ð¤Å¤¤¤Æ¡¢ + Æþ¤ì¤ë¤è¤¦¤Ë¤·¤¿¤¯¤Ê¤ë¤³¤È¤â¤¢¤ë¤Ç¤·¤ç¤¦¡£ + Î㤨¤Ð¤½¤Î¿Í¤¬¤É¤³¤«¤éÍè¤Æ¤¤¤ë¤«¤È¤¤¤Ã¤¿¤³¤È¤Ç¤¹¡£

+ +

Allow ¤È + Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¡¢¥É¥­¥å¥á¥ó¥È¤òÍ׵ᤷ¤Æ¤­¤¿¥Þ¥·¥ó¤Î + ¥Û¥¹¥È̾¤ä¥Û¥¹¥È¥¢¥É¥ì¥¹¤Ë´ð¤Å¤¤¤Æµö²ÄÉÔµö²Ä¤òÀ©¸æ¤Ç¤­¤Þ¤¹¡£ + Order + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤³¤ÎÆó¤Ä¤ÈÏ¢·È¤·¤ÆÆ°ºî¤·¡¢Apache + ¤Ë¤É¤Î½çÈ֤ǥե£¥ë¥¿¤òŬÍѤ¹¤ë¤«¤òÃΤ餻¤Þ¤¹¡£

+ +

¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î»È¤¤Êý¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

+ Allow from address +

+ +

¤³¤³¤Ç¡¢address ¤Ï IP ¥¢¥É¥ì¥¹ + (¤Þ¤¿¤Ï IP ¥¢¥É¥ì¥¹¤Î°ìÉô)¡¢¤¢¤ë¤¤¤Ï´°Á´½¤¾þ¥É¥á¥¤¥ó̾ + (¤Þ¤¿¤Ï¥É¥á¥¤¥ó̾¤Î°ìÉô) ¤Ç¤¹¡£ + ɬÍפǤ¢¤ì¤ÐÊ£¿ô¤Î¥¢¥É¥ì¥¹¤ä¥É¥á¥¤¥ó̾¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢¤â¤·Ã¯¤«¤¬·Ç¼¨ÈĤò¹¶·â¤·¤Æ¤¤¤Æ¡¢ + ¤½¤Î¿Í¤òÊĤá½Ð¤·¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¼¡¤Î¤è¤¦¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ Deny from 205.252.46.165 +

+ +

¤³¤Î¥¢¥É¥ì¥¹¤«¤éÍè¤ë¿Í¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÈÏ°ÏÆâ¤Î + ¥³¥ó¥Æ¥ó¥Ä¤ò¸«¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤Þ¤»¤ó¡£¤â¤· IP + ¥¢¥É¥ì¥¹¤ÎÂå¤ï¤ê¤Ë¥Þ¥·¥ó̾¤¬¤¢¤ì¤Ð¡¢¤½¤ì¤ò»È¤¨¤Þ¤¹¡£

+ +

+ Deny from host.example.com +

+ +

¥É¥á¥¤¥óÁ´ÂΤ«¤é¤Î¥¢¥¯¥»¥¹¤òËɤ®¤¿¤±¤ì¤Ð¡¢ + ñ¤Ë¥¢¥É¥ì¥¹¤ä¥É¥á¥¤¥ó̾¤Î°ìÉô¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ Deny from 192.101.205
+ Deny from cyberthugs.com moreidiots.com
+ Deny from ke +

+ +

Order ¤ò»È¤¦¤³¤È¤Ç¡¢ + Deny ¤È + Allow ¤ÎÁȤ߹ç¤ï¤»¤Ç + Æþ¤Ã¤Æ¤âÎɤ¤¥°¥ë¡¼¥×¤¬ËÜÅö¤Ë³Î¼Â¤Ë¸ÂÄê¤Ç¤­¤Æ¤¤¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£

+ +

+ Order deny,allow
+ Deny from all
+ Allow from dev.example.com +

+ +

Allow + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òñ½ã¤ËÎóµó¤¹¤ë¤Î¤Ç¤Ï˾¤ß¤ÎÆ°ºî¤ò¤·¤Ê¤¤¤Ç¤·¤ç¤¦¡£ + ¤Ê¤¼¤Ê¤é¡¢Á´¤Æ¤Î¿Í¤¬Æþ¤ì¤ë¤È¤¤¤¦¤³¤È¤Ë²Ã¤¨¤Æ¡¢ + »ØÄꤷ¤¿¥Û¥¹¥È¤«¤é¤Î¿Í¤¬Æþ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤«¤é¤Ç¤¹¡£ + ¤ä¤ê¤¿¤¤¤³¤È¤Ï¡¢»ØÄꤷ¤¿¿Í¤¿¤Á¤À¤±¤¬Æþ¤ì¤ë¤è¤¦¤Ë + ¤¹¤ë¤³¤È¤Ç¤¹¡£

+
top
+
+

ÄɲþðÊó

+

¤³¤ì¤éÁ´¤Æ¤¬¤É¤Î¤è¤¦¤ËÆ°ºî¤¹¤ë¤«¤Ë¤Ä¤¤¤Æ + ¤â¤Ã¤È¿¤¯¤Î¾ðÊ󤬽ñ¤«¤ì¤Æ¤¤¤ë mod_auth_basic ¤È + mod_authz_host + ¤Îʸ½ñ¤âÆɤà¤È¤è¤¤¤Ç¤·¤ç¤¦¡£

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/auth.html.ko.euc-kr b/docs/manual/howto/auth.html.ko.euc-kr new file mode 100644 index 00000000..b76e5262 --- /dev/null +++ b/docs/manual/howto/auth.html.ko.euc-kr @@ -0,0 +1,323 @@ + + + +ÀÎÁõ(Authentication), ±ÇÇѺο©(Authorization), +Á¢±ÙÁ¦¾î(Access Control) - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

ÀÎÁõ(Authentication), ±ÇÇѺο©(Authorization), +Á¢±ÙÁ¦¾î(Access Control)

+
+

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

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

ÀÎÁõ(authentication)Àº ÀÚ½ÅÀÌ ´©±¸¶ó°í ÁÖÀåÇÏ´Â »ç¶÷À» + È®ÀÎÇÏ´Â ÀýÂ÷ÀÌ´Ù. ±ÇÇѺο©(authorization)´Â °¡°í ½ÍÀº °÷À¸·Î + °¡µµ·Ï ȤÀº ¿øÇÏ´Â Á¤º¸¸¦ ¾òµµ·Ï Çã¿ëÇÏ´Â °úÁ¤ÀÌ´Ù.

+
+ +
top
+
+

°ü·Ã ¸ðµâ°ú Áö½Ã¾î

+
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+
top
+
+

¼Ò°³

+

´ç½ÅÀÇ À¥»çÀÌÆ®¿¡ ÀÖ´Â Á¤º¸°¡ ¼Ò¼öÀÇ »ç¶÷µé¸¸ÀÇ ºñ¹ÐÀ̰ųª + À̵鸸À» À§ÇÑ Á¤º¸¶ó¸é, ÀÌ ±Û¿¡¼­ ¼³¸íÇÏ´Â ±â¹ýÀ» »ç¿ëÇÏ¿© + ´ç½ÅÀÌ º¸±æ ¿øÇÏ´Â »ç¶÷¸¸ ÆäÀÌÁö¸¦ º¸µµ·Ï ÇÒ ¼ö ÀÖ´Ù.

+ +

ÀÌ ±ÛÀº À¥»çÀÌÆ®ÀÇ ÀϺθ¦ º¸È£ÇϱâÀ§ÇØ ¸¹Àº »ç¶÷µéÀÌ + »ç¿ëÇÏ´Â "Ç¥ÁØÀûÀÎ" ¹æ¹ýÀ» ´Ù·é´Ù.

+
top
+
+

±âº» Áö½Ä

+

ÀÌ ±Û¿¡¼­ ´Ù·ç´Â Áö½Ã¾î´Â ¼­¹öÀÇ ÁÖ¼³Á¤ÆÄÀÏ(ÀϹÝÀûÀ¸·Î + <Directory> + ¼½¼Ç)À̳ª µð·ºÅ丮º° ¼³Á¤ÆÄÀÏ(.htaccess ÆÄÀÏ)¿¡¼­ + »ç¿ëÇÑ´Ù.

+ +

.htaccess ÆÄÀÏÀ» »ç¿ëÇÏ·Á¸é ÀÌ ÆÄÀÏ¿¡ ÀÖ´Â + ÀÎÁõ Áö½Ã¾î¸¦ Çã¿ëÇϵµ·Ï ¼­¹ö¸¦ ¼³Á¤ÇØ¾ß ÇÑ´Ù. À̸¦ À§ÇØ + µð·ºÅ丮º° ¼³Á¤ÆÄÀÏ¿¡ ¾î¶² Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖ´ÂÁö¸¦ °áÁ¤ÇÏ´Â + AllowOverride Áö½Ã¾î¸¦ + »ç¿ëÇÑ´Ù.

+ +

¿©±â¼­´Â ÀÎÁõÀ» ´Ù·ç±â ¶§¹®¿¡, ´ÙÀ½°ú °°Àº + AllowOverride Áö½Ã¾î°¡ ÇÊ¿äÇÏ´Ù.

+ +

+ AllowOverride AuthConfig +

+ +

ȤÀº Áö½Ã¾î¸¦ Á÷Á¢ ¼­¹ö ÁÖ¼³Á¤ÆÄÀÏ¿¡ Àû´Â´Ù¸é, ±× ÆÄÀÏ¿¡ + ¾²±â ±ÇÇÑÀÌ ¹°·Ð ÀÖ¾î¾ß ÇÑ´Ù.

+ +

±×¸®°í º¸È£ÇÒ ÆÄÀÏÀÌ ¾îµðÀÖ´ÂÁö ¾Ë±âÀ§ÇØ ¼­¹öÀÇ µð·ºÅ丮 + ±¸Á¶¿¡ ´ëÇØ Á¶±Ý ¾Ë¾Æ¾ßÇÑ´Ù. ÀÌ ÀÏÀº ¾î·ÆÁö¾Ê°í, Àû´çÇÑ + ¶§¿¡ ÀÚ¼¼È÷ ¼³¸íÇÒ °ÍÀÌ´Ù.

+
top
+
+

±âº»ÀûÀÎ ¼³Á¤Çϱâ

+

ÀÌÁ¦ ¼­¹öÀÇ µð·ºÅ丮¸¦ ¾ÏÈ£·Î º¸È£ÇÏ´Â ±âº»ÀûÀÎ ¹æ¹ýÀ» + ¼³¸íÇÑ´Ù.

+ +

¸ÕÀú ¾ÏÈ£ÆÄÀÏÀ» ¸¸µé¾î¾ß ÇÑ´Ù. ÀÌ ÆÄÀÏÀº À¥¿¡¼­ Á¢±ÙÇÒ + ¼ö ¾ø´Â °÷¿¡ ÀÖ¾î¾ß ÇÑ´Ù. ´Ù¸¥»ç¶÷ÀÌ ¾ÏÈ£ÆÄÀÏÀ» ´Ù¿î·ÎµåÇÏÁö + ¸øÇÏ°ÔÇϱâ À§Çؼ­´Ù. ¿¹¸¦ µé¾î, ¹®¼­µéÀÌ + /usr/local/apache/htdocs¿¡ ÀÖ´Ù¸é ¾ÏÈ£ÆÄÀÏ(µé)Àº + /usr/local/apache/passwd¿¡ µÐ´Ù.

+ +

¾ÆÆÄÄ¡¿¡ Æ÷ÇÔµÈ htpasswd µµ±¸¸¦ »ç¿ëÇÏ¿© + ¾ÏÈ£ÆÄÀÏÀ» ¸¸µç´Ù. ÀÌ ÇÁ·Î±×·¥Àº ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÑ °÷ÀÇ + bin µð·ºÅ丮¿¡ ÀÖ´Ù. ÆÄÀÏÀ» ¸¸µé·Á¸é ´ÙÀ½°ú + °°ÀÌ ÀÔ·ÂÇÑ´Ù.

+ +

+ htpasswd -c /usr/local/apache/passwd/passwords rbowen +

+ +

htpasswd´Â ¾ÏÈ£¸¦ ¹°¾îº¸°í, È®ÀÎÀ» À§ÇØ + ¾ÏÈ£¸¦ ´Ù½Ã ÀÔ·ÂÇ϶ó°í ¿äûÇÑ´Ù.

+ +

+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen
+ New password: mypassword
+ Re-type new password: mypassword
+ Adding password for user rbowen +

+ +

¹°·Ð htpasswdÀÌ ½ÇÇàÆÄÀÏ °æ·Î¿¡ ¾ø´Ù¸é + ½ÇÇàÆÄÀÏÀÇ Àüü °æ·Î¸¦ ÀÔ·ÂÇØ¾ß ÇÑ´Ù. ³»°¡ »ç¿ëÇÏ´Â ¼­¹ö¿¡¼­´Â + /usr/local/apache/bin/htpasswd¿¡ ½ÇÇàÆÄÀÏÀÌ + ÀÖ´Ù.

+ +

´ÙÀ½À¸·Î ¼­¹ö°¡ ¾ÏÈ£¸¦ ¿äûÇϵµ·Ï ¼³Á¤ÇÏ°í, ¼­¹ö¿¡°Ô + ¾î¶² »ç¿ëÀÚÀÇ Á¢±ÙÀ» Çã¿ëÇÒÁö ¾Ë·ÁÁà¾ß ÇÑ´Ù. + httpd.conf¸¦ ÆíÁýÇϰųª .htaccess + ÆÄÀÏÀ» »ç¿ëÇÏ¿© ¼³Á¤ÇÑ´Ù. ¿¹¸¦ µé¾î, + /usr/local/apache/htdocs/secret µð·ºÅ丮¸¦ + º¸È£ÇÏ·Á¸é, ¾Æ·¡ Áö½Ã¾î¸¦ + /usr/local/apache/htdocs/secret/.htaccess ÆÄÀÏÀ̳ª + httpd.confÀÇ <Directory + /usr/local/apache/apache/htdocs/secret> ¼½¼Ç¿¡ Àû¾î¾ß + ÇÑ´Ù.

+ +

+ AuthType Basic
+ AuthName "Restricted Files"
+ AuthUserFile /usr/local/apache/passwd/passwords
+ Require user rbowen +

+ +

Áö½Ã¾î¸¦ Çϳª¾¿ »ìÆ캸ÀÚ. AuthType Áö½Ã¾î´Â »ç¿ëÀÚ¸¦ ÀÎÁõÇÒ + ¹æ¹ýÀ» ¼±ÅÃÇÑ´Ù. °¡Àå ÀϹÝÀûÀÎ ¹æ¹ýÀº BasicÀ¸·Î, + mod_auth_basicÀÌ ±¸ÇöÇÑ´Ù. ±×·¯³ª Basic + ÀÎÁõÀº ºê¶ó¿ìÀú°¡ ¼­¹ö·Î ¾ÏÈ£¸¦ ¾ÏȣȭÇÏÁö ¾Ê°í º¸³½´Ù. + ±×·¯¹Ç·Î ±â¹Ð ÀڷḦ º¸È£ÇϱâÀ§ÇØ ÀÌ ¹æ¹ýÀ» »ç¿ëÇÏ¸é ¾ÈµÈ´Ù. + ¾ÆÆÄÄ¡´Â AuthType Digest¶ó´Â ÀÎÁõ ¹æ¹ýµµ Áö¿øÇÑ´Ù. + ÀÌ ¹æ¹ýÀº mod_auth_digest°¡ ±¸ÇöÇϸç, ¸Å¿ì + ¾ÈÀüÇÏ´Ù. °¡Àå Ãֱ٠Ŭ¶óÀ̾ðÆ®µé¸¸ÀÌ Digest ÀÎÁõÀ» Áö¿øÇÑ´Ù°í + ÇÑ´Ù.

+ +

AuthName Áö½Ã¾î´Â + ÀÎÁõ¿¡ »ç¿ëÇÒ ¿µ¿ª(realm)À» ÁöÁ¤ÇÑ´Ù. ¿µ¿ªÀº + µÎ°¡Áö ¿ªÇÒÀ» ÇÑ´Ù. ù¹ø°´Â Ŭ¶óÀ̾ðÆ®°¡ º¸Åë ÀÌ Á¤º¸¸¦ + ¾ÏÈ£ ´ëȭâ¿¡ º¸¿©ÁØ´Ù. µÎ¹ø°´Â ¿µ¿ª Á¤º¸¸¦ »ç¿ëÇÏ¿© + Ŭ¶óÀ̾ðÆ®°¡ ƯÁ¤ ÀÎÁõ±¸¿ª¿¡ ¾î¶² ¾ÏÈ£¸¦ º¸³¾Áö °áÁ¤ÇÑ´Ù.

+ +

¿¹¸¦ µé¾î, ÀÏ´Ü Å¬¶óÀ̾ðÆ®°¡ "Restricted Files" + ¿µ¿ª¿¡ ÀÎÁõÀÌ ¼º°øÇÏ¿´´Ù¸é, Ŭ¶óÀ̾ðÆ®´Â ÀÚµ¿À¸·Î °°Àº ¼­¹ö¿¡¼­ + "Restricted Files" ¿µ¿ªÀ¸·Î Ç¥½ÃµÈ ±¸¿ª¿¡ ´ëÇØ + µ¿ÀÏÇÑ ¾ÏÈ£¸¦ ½ÃµµÇÑ´Ù. ±×·¡¼­ ¿©·¯ Á¦ÇÑ ±¸¿ªÀÌ °°Àº ¿µ¿ªÀ» + °øÀ¯ÇÏ¸é »ç¿ëÀÚ°¡ ¿©·¯¹ø ¾ÏÈ£¸¦ ÀÔ·ÂÇÏÁö ¾Ê¾Æµµ µÈ´Ù. ¹°·Ð + º¸¾È»ó ÀÌÀ¯·Î Ŭ¶óÀ̾ðÆ®´Â ¼­¹öÀÇ È£½ºÆ®¸íÀÌ ´Ù¸£¸é Ç×»ó + »õ·Î ¾ÏÈ£¸¦ ¹°¾îº»´Ù.

+ +

AuthUserFile + Áö½Ã¾î´Â ¿ì¸®°¡ ¹æ±Ý htpasswd·Î ¸¸µç ¾ÏÈ£ÆÄÀÏÀÇ + °æ·Î¸¦ ¼³Á¤ÇÑ´Ù. »ç¿ëÀÚ°¡ ¸¹´Ù¸é ¿äû¸¶´Ù ¸Å¹ø »ç¿ëÀÚ¸¦ + ÀÎÁõÇϱâÀ§ÇØ ÀÏ¹Ý ¹®¼­ÆÄÀÏÀ» °Ë»öÇϴµ¥ ½Ã°£ÀÌ »ó´çÈ÷ ¸¹ÀÌ + °É¸± ¼ö ÀÖ´Ù. ¾ÆÆÄÄ¡´Â ºü¸¥ µ¥ÀÌŸº£À̽º ÆÄÀÏ¿¡ »ç¿ëÀÚ Á¤º¸¸¦ + ÀúÀåÇÒ ¼ö ÀÖ´Ù. mod_authn_dbm ¸ðµâÀº AuthDBMUserFile Áö½Ã¾î¸¦ + Á¦°øÇÑ´Ù. dbmmanage + ÇÁ·Î±×·¥À» »ç¿ëÇÏ¿© ¾ÏÈ£ÆÄÀÏÀ» ¸¸µé°í ´Ù·é´Ù. ¾ÆÆÄÄ¡ ¸ðµâ + µ¥ÀÌŸº£À̽º¿¡´Â ¿©·¯ ´Ù¸¥ ÀÎÁõ ¹æ½ÄÀ» Á¦°øÇÏ´Â Á¦»ïÀÚ°¡ + ¸¸µç ¸ðµâµéÀÌ ÀÖ´Ù.

+ +

¸¶Áö¸·À¸·Î Require + Áö½Ã¾î´Â ¼­¹öÀÇ Æ¯Á¤ ¿µ¿ª¿¡ Á¢±ÙÇÒ ¼ö ÀÖ´Â »ç¿ëÀÚ¸¦ ÁöÁ¤ÇÏ¿© + ±ÇÇѺο©¸¦ ÇÑ´Ù. ´ÙÀ½ ÀýÀº require Áö½Ã¾î¸¦ + »ç¿ëÇÏ´Â ´Ù¾çÇÑ ¹æ¹ýÀ» ¼³¸íÇÑ´Ù.

+
top
+
+

¿©·¯¸íÀ» µé¿©º¸³»±â

+

À§ÀÇ Áö½Ã¾î´Â µð·ºÅ丮·Î (»ç¿ëÀÚ¸íÀÌ rbowenÀÎ) + ÇÑ »ç¶÷¸¸À» µé¿©º¸³½´Ù. ´ëºÎºÐÀÇ °æ¿ì ¿©·¯ »ç¶÷À» µé¿©º¸³»°í + ½ÍÀ» °ÍÀÌ´Ù. ÀÌÁ¦ AuthGroupFileÀ» + »ç¿ëÇÒ ¶§´Ù.

+ +

¿©·¯ »ç¶÷À» µé¿©º¸³»°í ½Í´Ù¸é ±×·ì¸í°ú ±× ±×·ì¿¡ ¾î¶² + »ç¿ëÀÚµéÀÌ ÀÖ´ÂÁö ¾Ë·ÁÁÖ´Â ±×·ìÆÄÀÏÀÌ ÇÊ¿äÇÏ´Ù. ÀÌ ÆÄÀÏÀÇ + Çü½ÄÀº ¸Å¿ì °£´ÜÇÏ¿©, ¾Æ¹« ÆíÁý±â·Î³ª ¸¸µé ¼ö ÀÖ´Ù. ÆÄÀϳ»¿ëÀº + ´ÙÀ½°ú °°´Ù.

+ +

+ GroupName: rbowen dpitts sungo rshersey +

+ +

±×³É °ø¹éÀ¸·Î ±¸ºÐÇÑ ±ä ±×·ì ±¸¼º¿ø ¸ñ·ÏÀÏ »ÓÀÌ´Ù.

+ +

±âÁ¸ÀÇ ¾ÏÈ£ÆÄÀÏ¿¡ »ç¿ëÀÚ¸¦ Ãß°¡ÇÏ·Á¸é ´ÙÀ½°ú °°ÀÌ ÀÔ·ÂÇÑ´Ù

+ +

+ htpasswd /usr/local/apache/passwd/passwords dpitts +

+ +

Àü°ú °°Áö¸¸, »õ·Î ÆÄÀÏÀ» ¸¸µéÁö ¾Ê°í ±âÁ¸ ÆÄÀÏ¿¡ »ç¿ëÀÚ¸¦ + Ãß°¡ÇÑ´Ù. (-c ¿É¼ÇÀº »õ·Î ¾ÏÈ£ÆÄÀÏÀ» ¸¸µç´Ù).

+ +

ÀÌÁ¦ .htaccess ÆÄÀÏÀ» ´ÙÀ½°ú °°ÀÌ ¼öÁ¤ÇÑ´Ù.

+ +

+ AuthType Basic
+ AuthName "By Invitation Only"
+ AuthUserFile /usr/local/apache/passwd/passwords
+ AuthGroupFile /usr/local/apache/passwd/groups
+ Require group GroupName +

+ +

±×·¯¸é GroupName ±×·ì¿¡ ¼ÓÇϸç + password ÆÄÀÏ¿¡ Ç׸ñÀÌ ÀÖ´Â »ç¿ëÀÚ°¡ ¿Ã¹Ù¸¥ + ¾ÏÈ£¸¦ ÀÔ·ÂÇϸé Á¢±ÙÀ» Çã¿ëÇÑ´Ù.

+ +

¿©·¯ ÀÏ¹Ý »ç¿ëÀÚ¸¦ µé¿©º¸³»´Â ´Ù¸¥ ¹æ¹ýÀÌ ÀÖ´Ù. ±×·ìÆÄÀÏÀ» + ¸¸µé ÇÊ¿ä¾øÀÌ ´ÙÀ½ Áö½Ã¾î¸¦ »ç¿ëÇϱ⸸ ÇÏ¸é µÈ´Ù.

+ +

+ Require valid-user +

+ +

Require user rbowen ´ë½Å ÀÌ Áö½Ã¾î¸¦ »ç¿ëÇϸé + ¾ÏÈ£ÆÄÀÏ¿¡ ÀÖ´Â ´©±¸¶óµµ ¿Ã¹Ù¸¥ ¾ÏÈ£¸¦ ÀÔ·ÂÇϱ⸸ Çϸé Á¢±ÙÀ» + Çã¿ëÇÑ´Ù. ±×·ìº°·Î ´Ù¸¥ ¾ÏÈ£ÆÄÀÏÀ» »ç¿ëÇÏ¿© ±×·ì°ú ºñ½ÁÇÑ + È¿°ú¸¦ ¾òÀ» ¼öµµ ÀÖ´Ù. ÀÌ °æ¿ì ¾ÆÆÄÄ¡°¡ ÆÄÀÏ µÎ°³(¾ÏÈ£ÆÄÀÏ°ú + ±×·ìÆÄÀÏ)°¡ ¾Æ´Ñ ÆÄÀÏ ÇÑ°³(¾ÏÈ£ÆÄÀÏ)¸¸ °Ë»çÇÏ¸é µÈ´Ù´Â °ÍÀÌ + ÀåÁ¡ÀÌ´Ù. ±×·¯³ª ¿©·¯ ¾ÏÈ£ÆÄÀÏÀ» °ü¸®ÇØ¾ß ÇÏ°í, AuthUserFile Áö½Ã¾î¿¡ + Á¤È®ÇÑ ¾ÏÈ£ÆÄÀÏÀ» ÁöÁ¤ÇØ¾ß ÇÏ´Â °ÍÀº ´ÜÁ¡ÀÌ´Ù.

+
top
+
+

¹ß»ýÇÒ ¼ö ÀÖ´Â ¹®Á¦Á¡

+

Basic ÀÎÁõ ¹æ½ÄÀº ¼­¹ö¿¡¼­ ¹®¼­¸¦ ¿äûÇÒ ¶§¸¶´Ù »ç¿ëÀÚ¸í°ú + ¾ÏÈ£¸¦ È®ÀÎÇÑ´Ù. ½ÉÁö¾î °°Àº ÆäÀÌÁö¸¦ »õ·Î °íħÇÒ ¶§µµ ÆäÀÌÁö¿Í + (±×¸²ÀÌ ¾ÏÈ£·Î º¸È£ÇÏ´Â µð·ºÅ丮¿¡ ÀÖ´Â °æ¿ì) ÆäÀÌÁö¿¡ ÀÖ´Â + ¸ðµç ±×¸²¿¡ ´ëÇØ ´Ù½Ã È®ÀÎÇÑ´Ù. ÁüÀÛÇϵíÀÌ ¼Óµµ°¡ Á¶±Ý ´À·ÁÁø´Ù. + ¾ÏÈ£ÆÄÀÏÀ» ¿­¾î¼­ »ç¿ëÀÚ¸íÀ» ãÀ» ¶§±îÁö »ç¿ëÀÚ ¸ñ·ÏÀ» »ìÆìºÁ¾ß + Çϱ⶧¹®¿¡ ¾ÏÈ£ÆÄÀÏ Å©±â°¡ Ä¿Áú ¼ö·Ï ´õ ´À·ÁÁø´Ù. ±×¸®°í + ÀÌ ÀÛ¾÷À» ÆäÀÌÁö¸¦ ¿äûÇÒ ¶§¸¶´Ù ÁøÇàÇÑ´Ù.

+ +

±×·¡¼­ Çö½ÇÀûÀ¸·Î ÇÑ ¾ÏÈ£ÆÄÀÏ¿¡ ÀúÀåÇÒ ¼ö ÀÖ´Â »ç¿ëÀÚ¼ö¿¡´Â + ÇÑ°è°¡ ÀÖ´Ù. ÀÌ ÇÑ°è´Â »ç¿ëÇÏ´Â ¼­¹öÀÇ ¼º´É¿¡ µû¶ó ´Ù¸£Áö¸¸, + Ç׸ñÀÌ ¼ö¹é°³°¡ ³Ñ´Â´Ù¸é ´À·ÁÁø´Ù°í »ý°¢ÇÏ°í ´Ù¸¥ ÀÎÁõ ¹æ¹ýÀ» + °í·ÁÇØ¾ß ÇÑ´Ù.

+
top
+
+

´Ù¸¥ ¹æ¹ýµµ °¡´ÉÇÑ°¡?

+

»ç¿ëÀÚ¸í°ú ¾ÏÈ£¸¦ »ç¿ëÇÑ ÀÎÁõÀÌ ´Ù°¡ ¾Æ´Ï´Ù. Á¾Á¾ Á¢¼ÓÇÑ + Àå¼Ò¿Í °°Àº ´Ù¸¥ Á¤º¸¸¦ °¡Áö°í »ç¿ëÀÚ¸¦ µé¿©º¸³»°í ½ÍÀ» + ¶§°¡ ÀÖ´Ù.

+ +

Allow¿Í + Deny Áö½Ã¾î´Â + ¹®¼­¸¦ ¿äûÇÑ ÄÄÇ»ÅÍÀÇ È£½ºÆ®¸í ȤÀº È£½ºÆ® ÁÖ¼Ò¸¦ °¡Áö°í + Á¢±ÙÀ» Çã¿ëÇϰųª °ÅºÎÇÑ´Ù. Order Áö½Ã¾î´Â ÀÌ µÎ + Áö½Ã¾î¿Í °°ÀÌ »ç¿ëÇÏ¿©, ¾ÆÆÄÄ¡¿¡°Ô ¾î¶² ¼ø¼­·Î ±ÔÄ¢À» Àû¿ëÇÒÁö + ¾Ë¸°´Ù.

+ +

À̵é Áö½Ã¾î »ç¿ë¹ýÀº ´ÙÀ½°ú °°´Ù.

+ +

+ Allow from address +

+ +

¿©±â¼­ address´Â IP ÁÖ¼Ò(ȤÀº IP ÁÖ¼Ò ÀϺÎ)³ª + ¿ÏÀüÇÑ µµ¸ÞÀθí(ȤÀº µµ¸ÞÀθí ÀϺÎ)ÀÌ´Ù. ¿øÇÑ´Ù¸é ¿©·¯ ÁÖ¼Ò³ª + µµ¸ÞÀθíÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

¿¹¸¦ µé¾î, ´©±º°¡°¡ °Ô½ÃÆÇ¿¡ ±¤°í¸¦ ¿Ã¸®°í ÀÖ´Ù¸é ´ÙÀ½°ú + °°ÀÌ Á¢±ÙÀ» ¸·À» ¼ö ÀÖ´Ù.

+ +

+ Deny from 205.252.46.165 +

+ +

±× ÁÖ¼Ò¿¡¼­ µé¾î¿À´Â ¹æ¹®ÀÚ´Â ÀÌ Áö½Ã¾î°¡ º¸È£ÇÏ´Â ÆäÀÌÁö¸¦ + º¼ ¼ö ¾ø´Ù. IP ÁÖ¼Ò ´ë½Å ´ÙÀ½°ú °°ÀÌ ÄÄÇ»Å͸íÀ» »ç¿ëÇÒ ¼öµµ + ÀÖ´Ù.

+ +

+ Deny from host.example.com +

+ +

¶Ç, Àüü µµ¸ÞÀÎÀÇ Á¢±ÙÀ» ¸·À¸·Á¸é ÁÖ¼Ò³ª µµ¸ÞÀθíÀÇ ÀϺθ¦ + »ç¿ëÇÑ´Ù.

+ +

+ Deny from 192.101.205
+ Deny from cyberthugs.com moreidiots.com
+ Deny from ke +

+ +

Order¸¦ + Deny¿Í Allow Áö½Ã¾î¿Í °°ÀÌ + »ç¿ëÇÏ¿© ½ÇÁ¦·Î ¿øÇÏ´Â ´ë»óÀ» ¸·À» ¼ö ÀÖ´Ù.

+ +

+ Order deny,allow
+ Deny from all
+ Allow from dev.example.com +

+ +

Allow + Áö½Ã¾î¸¸ »ç¿ëÇϸé, ÇØ´ç È£½ºÆ®ÀÇ »ç¿ëÀÚ¸¦ Çã¿ëÇÏ°í °Å±â¿¡ + Ãß°¡·Î ¸ðµç »ç¶÷À» Çã¿ëÇϹǷΠ¿øÇÏ´Â °á°ú¸¦ ¾òÁö ¸øÇÑ´Ù. + ´ç½ÅÀº ƯÁ¤ »ç¶÷¸¸ Çã¿ëÇÏ±æ ¿øÇÑ´Ù.

+
top
+
+

´õ ¸¹Àº Á¤º¸

+

mod_auth_basic°ú + mod_authz_host ¹®¼­¿¡ Á¢±ÙÁ¦¾î°¡ µ¿ÀÛÇÏ´Â + ¹æ¹ý¿¡ ´ëÇÑ ´õ ¸¹Àº Á¤º¸°¡ ÀÖ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/howto/cgi.html b/docs/manual/howto/cgi.html new file mode 100644 index 00000000..8d3dbcba --- /dev/null +++ b/docs/manual/howto/cgi.html @@ -0,0 +1,11 @@ +URI: cgi.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: cgi.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: cgi.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/howto/cgi.html.en b/docs/manual/howto/cgi.html.en new file mode 100644 index 00000000..42893e6c --- /dev/null +++ b/docs/manual/howto/cgi.html.en @@ -0,0 +1,555 @@ + + + +Apache Tutorial: Dynamic Content with CGI - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

Apache Tutorial: Dynamic Content with CGI

+
+

Available Languages:  en  | + ja  | + ko 

+
+
+ +
top
+
+

Introduction

+ + +
Related ModulesRelated Directives
+ +

The CGI (Common Gateway Interface) defines a way for a web + server to interact with external content-generating programs, + which are often referred to as CGI programs or CGI scripts. It + is the simplest, and most common, way to put dynamic content on + your web site. This document will be an introduction to setting + up CGI on your Apache web server, and getting started writing + CGI programs.

+
top
+
+

Configuring Apache to permit CGI

+ + +

In order to get your CGI programs to work properly, you'll + need to have Apache configured to permit CGI execution. There + are several ways to do this.

+ +

ScriptAlias

+ + +

The + ScriptAlias + + directive tells Apache that a particular directory is set + aside for CGI programs. Apache will assume that every file in + this directory is a CGI program, and will attempt to execute + it, when that particular resource is requested by a + client.

+ +

The ScriptAlias + directive looks like:

+ +

+ ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/ +

+ +

The example shown is from your default httpd.conf + configuration file, if you installed Apache in the default + location. The ScriptAlias + directive is much like the Alias directive, which defines a URL prefix that + is to mapped to a particular directory. Alias + and ScriptAlias are usually used for + directories that are outside of the DocumentRoot directory. The difference between + Alias and ScriptAlias + is that ScriptAlias has the added meaning + that everything under that URL prefix will be considered a CGI + program. So, the example above tells Apache that any request for a + resource beginning with /cgi-bin/ should be served from + the directory /usr/local/apache2/cgi-bin/, and should be + treated as a CGI program.

+ +

For example, if the URL + http://www.example.com/cgi-bin/test.pl + is requested, Apache will attempt to execute the file + /usr/local/apache2/cgi-bin/test.pl + and return the output. Of course, the file will have to + exist, and be executable, and return output in a particular + way, or Apache will return an error message.

+ + +

CGI outside of ScriptAlias directories

+ + +

CGI programs are often restricted to ScriptAlias'ed directories for security reasons. + In this way, administrators can tightly control who is allowed to + use CGI programs. However, if the proper security precautions are + taken, there is no reason why CGI programs cannot be run from + arbitrary directories. For example, you may wish to let users + have web content in their home directories with the + UserDir directive. + If they want to have their own CGI programs, but don't have access to + the main cgi-bin directory, they will need to be able to + run CGI programs elsewhere.

+ +

There are two steps to allowing CGI execution in an arbitrary + directory. First, the cgi-script handler must be + activated using the AddHandler or SetHandler directive. Second, + ExecCGI must be specified in the Options directive.

+ + +

Explicitly using Options to permit CGI execution

+ + +

You could explicitly use the Options directive, inside your main server configuration + file, to specify that CGI execution was permitted in a particular + directory:

+ +

+ <Directory /usr/local/apache2/htdocs/somedir>
+ + Options +ExecCGI
+ + </Directory> +

+ +

The above directive tells Apache to permit the execution + of CGI files. You will also need to tell the server what + files are CGI files. The following AddHandler directive tells the server to treat all + files with the cgi or pl extension as CGI + programs:

+ +

+ AddHandler cgi-script .cgi .pl +

+ + +

.htaccess files

+ + +

The .htaccess tutorial + shows how to activate CGI programs if you do not have + access to httpd.conf.

+ + +

User Directories

+ + +

To allow CGI program execution for any file ending in + .cgi in users' directories, you can use the + following configuration.

+ +

+ <Directory /home/*/public_html>
+ + Options +ExecCGI
+ AddHandler cgi-script .cgi
+ + </Directory> +

+ +

If you wish designate a cgi-bin subdirectory of + a user's directory where everything will be treated as a CGI + program, you can use the following.

+ +

+ <Directory /home/*/public_html/cgi-bin>
+ + Options ExecCGI
+ SetHandler cgi-script
+ + </Directory> +

+ + + +
top
+
+

Writing a CGI program

+ + +

There are two main differences between ``regular'' + programming, and CGI programming.

+ +

First, all output from your CGI program must be preceded by + a MIME-type header. This is HTTP header that tells the client + what sort of content it is receiving. Most of the time, this + will look like:

+ +

+ Content-type: text/html +

+ +

Secondly, your output needs to be in HTML, or some other + format that a browser will be able to display. Most of the + time, this will be HTML, but occasionally you might write a CGI + program that outputs a gif image, or other non-HTML + content.

+ +

Apart from those two things, writing a CGI program will look + a lot like any other program that you might write.

+ +

Your first CGI program

+ + +

The following is an example CGI program that prints one + line to your browser. Type in the following, save it to a + file called first.pl, and put it in your + cgi-bin directory.

+ +

+ #!/usr/bin/perl
+ print "Content-type: text/html\n\n";
+ print "Hello, World."; +

+ +

Even if you are not familiar with Perl, you should be able + to see what is happening here. The first line tells Apache + (or whatever shell you happen to be running under) that this + program can be executed by feeding the file to the + interpreter found at the location /usr/bin/perl. + The second line prints the content-type declaration we + talked about, followed by two carriage-return newline pairs. + This puts a blank line after the header, to indicate the end + of the HTTP headers, and the beginning of the body. The third + line prints the string "Hello, World.". And that's the end + of it.

+ +

If you open your favorite browser and tell it to get the + address

+ +

+ http://www.example.com/cgi-bin/first.pl +

+ +

or wherever you put your file, you will see the one line + Hello, World. appear in your browser window. + It's not very exciting, but once you get that working, you'll + have a good chance of getting just about anything working.

+ +
top
+
+

But it's still not working!

+ + +

There are four basic things that you may see in your browser + when you try to access your CGI program from the web:

+ +
+
The output of your CGI program
+
Great! That means everything worked fine. If the output is correct, + but the browser is not processing it correctly, make sure you have the + correct Content-Type set in your CGI program.
+ +
The source code of your CGI program or a "POST Method Not + Allowed" message
+
That means that you have not properly configured Apache + to process your CGI program. Reread the section on + configuring + Apache and try to find what you missed.
+ +
A message starting with "Forbidden"
+
That means that there is a permissions problem. Check the + Apache error log and the section below on + file permissions.
+ +
A message saying "Internal Server Error"
+
If you check the + Apache error log, you will probably + find that it says "Premature end of + script headers", possibly along with an error message + generated by your CGI program. In this case, you will want to + check each of the below sections to see what might be + preventing your CGI program from emitting the proper HTTP + headers.
+
+ +

File permissions

+ + +

Remember that the server does not run as you. That is, + when the server starts up, it is running with the permissions + of an unprivileged user - usually nobody, or + www - and so it will need extra permissions to + execute files that are owned by you. Usually, the way to give + a file sufficient permissions to be executed by nobody + is to give everyone execute permission on the file:

+ +

+ chmod a+x first.pl +

+ +

Also, if your program reads from, or writes to, any other + files, those files will need to have the correct permissions + to permit this.

+ + + +

Path information and environment

+ + +

When you run a program from your command line, you have + certain information that is passed to the shell without you + thinking about it. For example, you have a PATH, + which tells the shell where it can look for files that you + reference.

+ +

When a program runs through the web server as a CGI program, + it may not have the same PATH. Any programs that you + invoke in your CGI program (like sendmail, for + example) will need to be specified by a full path, so that the + shell can find them when it attempts to execute your CGI + program.

+ +

A common manifestation of this is the path to the script + interpreter (often perl) indicated in the first + line of your CGI program, which will look something like:

+ +

+ #!/usr/bin/perl +

+ +

Make sure that this is in fact the path to the + interpreter.

+ +

In addition, if your CGI program depends on other environment variables, you will need to + assure that those variables are passed by Apache.

+ + + +

Program errors

+ + +

Most of the time when a CGI program fails, it's because of + a problem with the program itself. This is particularly true + once you get the hang of this CGI stuff, and no longer make + the above two mistakes. The first thing to do is to make + sure that your program runs from the command line before + testing it via the web server. For example, try:

+ +

+ cd /usr/local/apache2/cgi-bin
+ ./first.pl +

+ +

(Do not call the perl interpreter. The shell + and Apache should find the interpreter using the path information on the first line of + the script.)

+ +

The first thing you see written by your program should be + a set of HTTP headers, including the Content-Type, + followed by a blank line. If you see anything else, Apache will + return the Premature end of script headers error if + you try to run it through the server. See Writing a CGI program above for more + details.

+ + +

Error logs

+ + +

The error logs are your friend. Anything that goes wrong + generates message in the error log. You should always look + there first. If the place where you are hosting your web site + does not permit you access to the error log, you should + probably host your site somewhere else. Learn to read the + error logs, and you'll find that almost all of your problems + are quickly identified, and quickly solved.

+ + +

Suexec

+ + +

The suexec support program + allows CGI programs to be run under different user permissions, + depending on which virtual host or user home directory they are + located in. Suexec has very strict permission checking, and any + failure in that checking will result in your CGI programs + failing with Premature end of script headers.

+ +

To check if you are using suexec, run apachectl + -V and check for the location of SUEXEC_BIN. + If Apache finds an suexec binary there on startup, + suexec will be activated.

+ +

Unless you fully understand suexec, you should not be using it. + To disable suexec, simply remove (or rename) the suexec + binary pointed to by SUEXEC_BIN and then restart the + server. If, after reading about suexec, + you still wish to use it, then run suexec -V to find + the location of the suexec log file, and use that log file to + find what policy you are violating.

+ +
top
+
+

What's going on behind the scenes?

+ + +

As you become more advanced in CGI programming, it will + become useful to understand more about what's happening behind + the scenes. Specifically, how the browser and server + communicate with one another. Because although it's all very + well to write a program that prints "Hello, World.", it's not + particularly useful.

+ +

Environment variables

+ + +

Environment variables are values that float around you as + you use your computer. They are useful things like your path + (where the computer searches for the actual file + implementing a command when you type it), your username, your + terminal type, and so on. For a full list of your normal, + every day environment variables, type + env at a command prompt.

+ +

During the CGI transaction, the server and the browser + also set environment variables, so that they can communicate + with one another. These are things like the browser type + (Netscape, IE, Lynx), the server type (Apache, IIS, WebSite), + the name of the CGI program that is being run, and so on.

+ +

These variables are available to the CGI programmer, and + are half of the story of the client-server communication. The + complete list of required variables is at + http://hoohoo.ncsa.uiuc.edu/cgi/env.html.

+ +

This simple Perl CGI program will display all of the + environment variables that are being passed around. Two + similar programs are included in the + cgi-bin + + directory of the Apache distribution. Note that some + variables are required, while others are optional, so you may + see some variables listed that were not in the official list. + In addition, Apache provides many different ways for you to + add your own environment variables + to the basic ones provided by default.

+ +

+ #!/usr/bin/perl
+ print "Content-type: text/html\n\n";
+ foreach $key (keys %ENV) {
+ + print "$key --> $ENV{$key}<br>";
+ + } +

+ + +

STDIN and STDOUT

+ + +

Other communication between the server and the client + happens over standard input (STDIN) and standard + output (STDOUT). In normal everyday context, + STDIN means the keyboard, or a file that a + program is given to act on, and STDOUT + usually means the console or screen.

+ +

When you POST a web form to a CGI program, + the data in that form is bundled up into a special format + and gets delivered to your CGI program over STDIN. + The program then can process that data as though it was + coming in from the keyboard, or from a file

+ +

The "special format" is very simple. A field name and + its value are joined together with an equals (=) sign, and + pairs of values are joined together with an ampersand + (&). Inconvenient characters like spaces, ampersands, and + equals signs, are converted into their hex equivalent so that + they don't gum up the works. The whole data string might look + something like:

+ +

+ name=Rich%20Bowen&city=Lexington&state=KY&sidekick=Squirrel%20Monkey +

+ +

You'll sometimes also see this type of string appended to + a URL. When that is done, the server puts that string + into the environment variable called + QUERY_STRING. That's called a GET + request. Your HTML form specifies whether a GET + or a POST is used to deliver the data, by setting the + METHOD attribute in the FORM tag.

+ +

Your program is then responsible for splitting that string + up into useful information. Fortunately, there are libraries + and modules available to help you process this data, as well + as handle other of the aspects of your CGI program.

+ +
top
+
+

CGI modules/libraries

+ + +

When you write CGI programs, you should consider using a + code library, or module, to do most of the grunt work for you. + This leads to fewer errors, and faster development.

+ +

If you're writing CGI programs in Perl, modules are + available on CPAN. The most + popular module for this purpose is CGI.pm. You might + also consider CGI::Lite, which implements a minimal + set of functionality, which is all you need in most programs.

+ +

If you're writing CGI programs in C, there are a variety of + options. One of these is the CGIC library, from + http://www.boutell.com/cgic/.

+
top
+
+

For more information

+ + +

There are a large number of CGI resources on the web. You + can discuss CGI problems with other users on the Usenet group + comp.infosystems.www.authoring.cgi. And the -servers mailing + list from the HTML Writers Guild is a great source of answers + to your questions. You can find out more at + http://www.hwg.org/lists/hwg-servers/.

+ +

And, of course, you should probably read the CGI + specification, which has all the details on the operation of + CGI programs. You can find the original version at the + NCSA and there is an updated draft at the + Common Gateway + Interface RFC project.

+ +

When you post a question about a CGI problem that you're + having, whether to a mailing list, or to a newsgroup, make sure + you provide enough information about what happened, what you + expected to happen, and how what actually happened was + different, what server you're running, what language your CGI + program was in, and, if possible, the offending code. This will + make finding your problem much simpler.

+ +

Note that questions about CGI problems should never + be posted to the Apache bug database unless you are sure you + have found a problem in the Apache source code.

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/cgi.html.ja.euc-jp b/docs/manual/howto/cgi.html.ja.euc-jp new file mode 100644 index 00000000..6740c653 --- /dev/null +++ b/docs/manual/howto/cgi.html.ja.euc-jp @@ -0,0 +1,549 @@ + + + +Apache Tutorial: CGI ¤Ë¤è¤ëưŪ¥³¥ó¥Æ¥ó¥Ä - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë

Apache Tutorial: CGI ¤Ë¤è¤ëưŪ¥³¥ó¥Æ¥ó¥Ä

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+
+ +
top
+
+

¤Ï¤¸¤á¤Ë

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

CGI (Common Gateway Interface) ¤Ï¡¢¥¦¥§¥Ö¥µ¡¼¥Ð¤¬ + ¥³¥ó¥Æ¥ó¥ÄÀ¸À®¤ò¤¹¤ë³°Éô¥×¥í¥°¥é¥à¤È¶¨Ä´¤·¤ÆÆ°ºî¤¹¤ë¤¿¤á¤ÎÊýË¡¤ò + ÄêµÁ¤·¤Æ¤¤¤Þ¤¹¡£¤½¤Î¥×¥í¥°¥é¥à¤Ï¤·¤Ð¤·¤Ð CGI ¥×¥í¥°¥é¥à¤ä + CGI ¥¹¥¯¥ê¥×¥È¤È¸Æ¤Ð¤ì¤Þ¤¹¡£CGI ¤Ï¡¢¥¦¥§¥Ö¥µ¥¤¥È¤ËưŪ¤Ê + ¥³¥ó¥Æ¥ó¥Ä¤òÃÖ¤¯¤¿¤á¤ÎºÇ¤â´Êñ¤Ç°ìÈÌŪ¤ÊÊýË¡¤Ç¤¹¡£¤³¤Î¥É¥­¥å¥á¥ó¥È¤Ï¡¢ + Apache ¥¦¥§¥Ö¥µ¡¼¥Ð¤Ç CGI ¤òÀßÄꤷ¡¢ + CGI ¥×¥í¥°¥é¥à¤ò½ñ¤­»Ï¤á¤ë¤¿¤á¤ÎÆþÌç½ñ¤È¤Ê¤ë¤Ç¤·¤ç¤¦¡£

+
top
+
+

CGI ¤òµö²Ä¤¹¤ë¤è¤¦¤Ë Apache ¤òÀßÄꤹ¤ë

+ + +

CGI ¥×¥í¥°¥é¥à¤òÀµ¤·¤¯Æ°ºî¤µ¤»¤ë¤Ë¤Ï¡¢CGI ¤òµö²Ä¤¹¤ë¤è¤¦¤Ë + Apache ¤ÎÀßÄê¤ò¹Ô¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤ò¹Ô¤Ê¤¦¤¿¤á¤ÎÊýË¡¤¬¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹¡£

+ +

ScriptAlias

+ + +

ScriptAlias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¡¢ + CGI ¥×¥í¥°¥é¥àÍѤÎÆÃÊ̤ÊÊ̥ǥ£¥ì¥¯¥È¥ê¤ò Apache ¤ËÀßÄꤷ¤Þ¤¹¡£ + Apache ¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥È¥êÃæ¤ÎÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò CGI + ¥×¥í¥°¥é¥à¤Ç¤¢¤ë¤È²¾Äꤷ¤Þ¤¹¡£ + ¤½¤·¤Æ¡¢¤³¤ÎÆÃÊ̤ʥ꥽¡¼¥¹¤¬¥¯¥é¥¤¥¢¥ó¥È¤«¤éÍ׵ᤵ¤ì¤ë¤È¡¢ + ¤½¤Î¥×¥í¥°¥é¥à¤Î¼Â¹Ô¤ò»î¤ß¤Þ¤¹¡£

+ +

ScriptAlias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï°Ê²¼¤Î¤è¤¦¤Ë»ÈÍѤ·¤Þ¤¹:

+ +

+ ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/ +

+ +

¥Ç¥Õ¥©¥ë¥È°ÌÃÖ¤Ë Apache ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¤Ê¤é¤Ð¡¢ + ¤³¤ÎÎã¤Ï¥Ç¥Õ¥©¥ë¥È¾õÂ֤Πhttpd.conf + ÀßÄê¥Õ¥¡¥¤¥ë¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ + ScriptAlias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢URL ¤ÎÁ°¤ËÉղ乤ë¥Ç¥£¥ì¥¯¥È¥ê¤òÄêµÁ¤¹¤ë + Alias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤«¤Ê¤ê»÷¤Æ¤¤¤Þ¤¹¡£ + Alias ¤È ScriptAlias + ¤ÏÄ̾DocumentRoot + ¥Ç¥£¥ì¥¯¥È¥ê³°¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î¤¿¤á¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£ + Alias ¤È ScriptAlias + ¤È¤Îº¹¤Ï¡¢ScriptAlias ¤¬ÀÜƬ¼­¤Ç»Ï¤Þ¤ë¤¹¤Ù¤Æ¤Î + URL ¤Ï CGI ¥×¥í¥°¥é¥à¤È¤ß¤Ê¤µ¤ì¤ë¤È¤¤¤¦ÄɲäΰÕÌ£¤ò´Þ¤ó¤Ç¤¤¤ë¤³¤È¤Ç¤¹¡£ + ½¾¤Ã¤Æ¡¢¾åµ­¤ÎÎã¤Ç¤Ï¡¢/cgi-bin/ + ¤Ç»Ï¤Þ¤ë¥ê¥½¡¼¥¹¤Ø¤Î¤¢¤é¤æ¤ë¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¡¢¥Ç¥£¥ì¥¯¥È¥ê + /usr/local/apache2/cgi-bin/ ¤«¤éÄ󶡤·¡¢¤½¤ì¤é¤ò + CGI ¥×¥í¥°¥é¥à¤È¤·¤Æ°·¤¦¤è¤¦ Apache ¤Ë¼¨¤·¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢URL http://www.example.com/cgi-bin/test.pl + ¤¬Í׵ᤵ¤ì¤¿¾ì¹ç¡¢Apache ¤Ï ¥Õ¥¡¥¤¥ë + /usr/local/apache2/cgi-bin/test.pl + ¤ò¼Â¹Ô¤·¡¢¤½¤Î½ÐÎϤòÊÖ¤¹¤³¤È¤ò»î¤ß¤Þ¤¹¡£ + ¤â¤Á¤í¤ó¡¢¥Õ¥¡¥¤¥ë¤¬Â¸ºß¤·¡¢¼Â¹Ô²Äǽ¤Ç¤¢¤ê¡¢·è¤á¤é¤ì¤¿ÊýË¡¤Ç½ÐÎϤòÊÖ¤·¤Þ¤¹¡£ + ¤½¤¦¤Ç¤Ê¤±¤ì¤Ð¡¢Apache ¤Ï¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤òÊÖ¤·¤Þ¤¹¡£

+ + +

ScriptAlias ¥Ç¥£¥ì¥¯¥È¥ê³°¤Î CGI

+ + +

CGI ¥×¥í¥°¥é¥à¤Ï¡¢¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÍýͳ¤«¤é + ScriptAlias + ¤µ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤ËÀ©¸Â¤µ¤ì¤ë¤³¤È¤¬¤·¤Ð¤·¤Ð¤¢¤ê¤Þ¤¹¡£¤³¤ÎÊýË¡¤Ë¤è¤ê¡¢ + CGI ¥×¥í¥°¥é¥à¤ò»ÈÍѤǤ­¤ë¥æ¡¼¥¶¤ò´ÉÍý¼Ô¤¬¸·¤·¤¯À©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤·¤«¤·¤Ê¤¬¤é¡¢Å¬Àڤʥ»¥­¥å¥ê¥Æ¥£»öÁ°Âкö¤¬¤È¤é¤ì¤ë¤Ê¤é¤Ð¡¢CGI + ¥×¥í¥°¥é¥à¤òǤ°Õ¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ç¼Â¹Ô¤Ç¤­¤Ê¤¤¤è¤¦¤Ë¤¹¤ëÍýͳ¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + Î㤨¤Ð¡¢¥æ¡¼¥¶¤Ë UserDir + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÈà¤é¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥êÇÛ²¼¤Ë¥¦¥§¥Ö¥³¥ó¥Æ¥ó¥Ä¤ò»ý¤¿¤»¤¿¤¤¤È¤·¤Þ¤¹¡£ + ¤â¤·¡¢Èà¤é¤¬ CGI ¥×¥í¥°¥é¥à¤ò»ý¤Ä¤³¤È¤ò˾¤ó¤Ç¤¤¤Æ¤â¡¢¥á¥¤¥ó¤Î + cgi-bin ¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¥¢¥¯¥»¥¹¤¬¤Ç¤­¤Ê¤¤¾ì¹ç¡¢ + CGI ¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¾¤Î¾ì½ê¤¬É¬Íפˤʤê¤Þ¤¹¡£

+ +

Ǥ°Õ¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ç CGI ¤Î¼Â¹Ô¤òµö²Ä¤¹¤ë¤Ë¤ÏÆóÃʳ¬¤ÎÀßÄ꤬ɬÍפǤ¹¡£ + ¤Þ¤º¡¢AddHandler ¤ä SetHandler ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤Æ + cgi-script ¥Ï¥ó¥É¥é¤¬²Äǽ¤Ë¤Ê¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¼¡¤Ë¡¢Options ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + ExecCGI ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ + +

CGI ¤Î¼Â¹Ô¤ò²Äǽ¤Ë¤¹¤ë¤¿¤á¤Ë Options ¤òÌÀ¼¨Åª¤Ë»ÈÍѤ¹¤ë

+ + +

¥µ¡¼¥Ð¤Î¥á¥¤¥ó¤ÎÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Ç Options + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÌÀ¼¨Åª¤Ë»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢ÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥êÇÛ²¼¤Ç + CGI ¤Î¼Â¹Ô¤òµö²Ä¤¹¤ë¤è¤¦¤Ë»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ <Directory /usr/local/apache2/htdocs/somedir>
+ + Options +ExecCGI
+ + </Directory> +

+ +

¾åµ­¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢CGI ¥Õ¥¡¥¤¥ë¤Î¼Â¹Ô¤ò²Äǽ¤Ë¤¹¤ë¤è¤¦ + Apache ¤ËÅÁ¤¨¤Þ¤¹¡£¤Þ¤¿¡¢¤É¤Î¥Õ¥¡¥¤¥ë¤¬ CGI ¥Õ¥¡¥¤¥ë¤«¤ò + ¥µ¡¼¥Ð¤ËÅÁ¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¼¡¤Î + AddHandler + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÎã¤Ç¤Ï¡¢cgi ¤Þ¤¿¤Ï pl + ¤ò³ÈÄ¥»Ò¤Ë»ý¤Ä¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò CGI + ¥×¥í¥°¥é¥à¤È¤·¤Æ¤ß¤Ê¤¹¤³¤È¤ò¥µ¡¼¥Ð¤ËÅÁ¤¨¤Þ¤¹:

+ +

+ AddHandler cgi-script .cgi .pl +

+ + +

.htaccess ¥Õ¥¡¥¤¥ë

+ + +

.htaccess ¥Á¥å¡¼¥È¥ê¥¢¥ë + ¤Ï httpd.conf ¤òÊѹ¹¤Ç¤­¤Ê¤¤¾ì¹ç¤Ë¤É¤¦¤ä¤Ã¤Æ CGI ¥×¥í¥°¥é¥à¤ò + »È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤«¤òÀâÌÀ¤·¤Æ¤¤¤Þ¤¹¡£

+ + +

User ¥Ç¥£¥ì¥¯¥È¥ê

+ + +

.cgi ¤Ç½ª¤ï¤ë¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ CGI ¥×¥í¥°¥é¥à¤Î + ¼Â¹Ô¤òµö²Ä¤¹¤ë¤Ë¤Ï¡¢°Ê²¼¤ÎÀßÄê¤ò»ÈÍѤǤ­¤Þ¤¹¡£

+ +

+ <Directory /home/*/public_html>
+ + Options +ExecCGI
+ AddHandler cgi-script .cgi
+ + </Directory> +

+ +

¥æ¡¼¥¶¥Ç¥£¥ì¥¯¥È¥ê¤Î cgi-bin ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Î + ¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò CGI ¥×¥í¥°¥é¥à¤È¤·¤Æ»ØÄꤷ¤¿¤¤¾ì¹ç¤Ë¤Ï + °Ê²¼¤Î¤è¤¦¤Ê¤â¤Î¤ò»È¤¤¤Þ¤¹¡£

+ +

+ <Directory /home/*/public_html/cgi-bin>
+ + Options ExecCGI
+ SetHandler cgi-script
+ + </Directory> +

+ + +
top
+
+

CGI ¥×¥í¥°¥é¥à¤ò½ñ¤¯

+ + +

¡ÖÄ̾ï¤Î¡×¥×¥í¥°¥é¥ß¥ó¥°¤È CGI + ¥×¥í¥°¥é¥ß¥ó¥°¤Î´Ö¤Ë¤Ï¼ç¤ËÆó¤Ä¤Î°ã¤¤¤¬¤¢¤ê¤Þ¤¹¡£

+ +

°ì¤Ä¤Ï¡¢CGI ¥×¥í¥°¥é¥à¤Î¤¹¤Ù¤Æ¤Î½ÐÎÏ¤Ë¤Ï MIME-type + ¥Ø¥Ã¥À¤òÉÕ¤±¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤³¤ì¤Ï¤É¤Î¤è¤¦¤Ê¼ïÎà¤Î¥³¥ó¥Æ¥ó¥Ä¤ò¼õ¤±¼è¤Ã¤Æ¤¤¤ë¤«¤ò¥¯¥é¥¤¥¢¥ó¥È¤Ë¼¨¤¹ + HTTP ¥Ø¥Ã¥À¤Ç¤¹¡£¤Û¤È¤ó¤É¤Î¾ì¹ç¤Ç¤Ï¡¢¼¡¤Î¤è¤¦¤Ë½ÐÎϤ·¤Þ¤¹:

+ +

+ Content-type: text/html +

+ +

¤â¤¦°ì¤Ä¤Ï¡¢½ÐÎϤò HTML + ¤«¡¢¥Ö¥é¥¦¥¶¤¬É½¼¨¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë²¿¤«Â¾¤Î·Á¼°¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ÂçÄñ¤Î¾ì¹ç¤Ï HTML ¤Ç¤·¤ç¤¦¤¬¡¢GIF ¥¤¥á¡¼¥¸¤ä¾¤ÎÈó HTML + ¥³¥ó¥Æ¥ó¥Ä¤ò½ÐÎϤ¹¤ë CGI ¥×¥í¥°¥é¥à¤ò½ñ¤¯¤³¤È¤â¤¢¤ë¤Ç¤·¤ç¤¦¡£

+ +

¤³¤ì¤éÆóÅÀ°Ê³°¤Ç¤Ï¡¢CGI ¥×¥í¥°¥é¥à¤ò½ñ¤¯¤³¤È¤Ï¡¢ + ¤¢¤Ê¤¿¤¬½ñ¤¤¤Æ¤¤¤ë¾¤Î¥×¥í¥°¥é¥à¤È¤è¤¯»÷¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£

+ +

ºÇ½é¤Î CGI ¥×¥í¥°¥é¥à

+ + +

¼¡¤Ë¼¨¤¹¤Î¤Ï¡¢¥Ö¥é¥¦¥¶¤Ë 1 ¹Ô°õ»ú¤¹¤ë CGI + ¥×¥í¥°¥é¥à¤ÎÎã¤Ç¤¹¡£°Ê²¼¤òÆþÎϤ·¡¢first.pl + ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤ËÊݸ¤·¡¢¤½¤ì¤ò cgi-bin + ¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤¤¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ #!/usr/bin/perl
+ print "Content-type: text/html\n\n";
+ print "Hello, World."; +

+ +

Perl ¤ËÀºÄ̤·¤Æ¤¤¤Ê¤¯¤Æ¤â¡¢ + ²¿¤¬µ¯¤³¤ë¤«¤òÍý²ò¤¹¤ë¤³¤È¤Ï¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£1 ¹ÔÌܤϡ¢ + /usr/bin/perl ¤Ç¸«¤Ä¤±¤é¤ì¤ë¥¤¥ó¥¿¥×¥ê¥¿¤Ë + ¤³¤Î¥Õ¥¡¥¤¥ë¤ò¶¡µë¤¹¤ë¤³¤È¤Ç¤³¤Î¥×¥í¥°¥é¥à¤¬¼Â¹Ô¤µ¤ì¤ë¤³¤È¤ò + Apache ¤Ë (¥·¥§¥ë¾å¤Ç¼Â¹Ô¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤Ê¤é¤Ð¡¢¤½¤Î¥·¥§¥ë¤Ë ) + ¼¨¤·¤Þ¤¹¡£2 ¹ÔÌܤϡ¢Á°½Ò¤·¤¿¤È¤ª¤ê content-type ¤ÎÄêµÁ¤ò°õ»ú¤·¤Þ¤¹¡£ + ¤³¤ì¤Ë¤ÏÉüµ¢²þ¹Ô¤ÎÆó¤Ä¤ÎÁȤò¸å¤ËÉղä·¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¥Ø¥Ã¥À¤Î½ª¤ê¤Ë¶õ¹Ô¤¬ÃÖ¤«¤ì¡¢HTTP + ¥Ø¥Ã¥À¤Î½ª¤ê¤È¥Ü¥Ç¥£¤Î»Ï¤Þ¤ê¤ò¼¨¤·¤Þ¤¹¡£3 ¹ÔÌܤϡ¢"Hello, World." + ¤È¤¤¤¦Ê¸»úÎó¤ò°õ»ú¤·¡¢¤³¤ì¤Ç½ª¤ê¤È¤Ê¤ê¤Þ¤¹¡£

+ +

¹¥¤ß¤Î¥Ö¥é¥¦¥¶¤ò³«¤­¡¢¥¢¥É¥ì¥¹

+ +

+ http://www.example.com/cgi-bin/first.pl +

+ +

¤¢¤ë¤¤¤Ï¥Õ¥¡¥¤¥ë¤òÃÖ¤¤¤¿¥í¥±¡¼¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢ + Hello, World. + ¤È¤¤¤¦ 1 ¹Ô¤¬¥Ö¥é¥¦¥¶¥¦¥£¥ó¥É¤Ë¸½¤ì¤ë¤Ç¤·¤ç¤¦¡£ + ¤½¤ì¤Ï¤¢¤Þ¤ê¥¨¥­¥µ¥¤¥Æ¥£¥ó¥°¤Ê¤³¤È¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¤·¤«¤·¡¢¤³¤ì¤¬¤¦¤Þ¤¯Æ°¤±¤Ð¡¢ + ¾¤Î¤É¤Î¤è¤¦¤Ê¤â¤Î¤Ç¤âÆ°¤«¤¹¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +
top
+
+

¤·¤«¤·¡¢¤Þ¤ÀÆ°¤«¤Ê¤¤ !

+ + +

¥¦¥§¥Ö¤«¤é CGI ¥×¥í¥°¥é¥à¤Ø¤Î¥¢¥¯¥»¥¹¤ò¹Ô¤Ê¤Ã¤¿¤È¤­¡¢ + ¥Ö¥é¥¦¥¶¤Ç¸«¤ë²ÄǽÀ­¤¬¤¢¤ë»Í¤Ä¤Î´ðËÜŪ¤Ê¤³¤È¤¬¤¢¤ê¤Þ¤¹:

+ +
+
CGI ¥×¥í¥°¥é¥à¤Î½ÐÎÏ
+
ÁÇÀ²¤é¤·¤¤ ! ¤½¤ì¤Ï¤¹¤Ù¤Æ¤¬¤¦¤Þ¤¯Æ°¤¤¤¿¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ + ½ÐÎϤ¬Àµ¾ï¤À¤±¤ì¤É¤â¡¢¥Ö¥é¥¦¥¶¤¬Àµ¾ï¤Ë½èÍý¤·¤Æ¤¯¤ì¤Ê¤¤¾ì¹ç¤Ï¡¢ + Àµ¤·¤¤ Content-Type ¤ò CGI ¥×¥í¥°¥é¥àÆâ¤Ç + ¥»¥Ã¥È¤·¤¿¤«¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
+ +
CGI ¥×¥í¥°¥é¥à¤Î¥½¡¼¥¹¥³¡¼¥É¡¢¤Þ¤¿¤Ï "POST Method Not Allowed" + ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸
+
¤³¤ì¤Ï¡¢CGI ¥×¥í¥°¥é¥à¤ò½èÍý¤Ç¤­¤ë¤è¤¦ Apache + ¤òŬÀÚ¤ËÀßÄꤷ¤Æ¤¤¤Ê¤«¤Ã¤¿¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£¡ÖCGI ¤òµö²Ä¤¹¤ë¤è¤¦¤Ë + Apache ¤òÀßÄꤹ¤ë¡×¤Î¾Ï¤òÆɤßľ¤·¡¢ + ¤¢¤Ê¤¿¤¬²¿¤ò´Ö°ã¤¨¤¿¤«¤òõ¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£ +
+ +
¥á¥Ã¥»¡¼¥¸¤¬ "Forbidden" ¤Ç»Ï¤Þ¤Ã¤Æ¤¤¤ë
+
¤³¤ì¤Ï¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤ÎÌäÂê¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ + Apache ¤Î¥¨¥é¡¼¥í¥°¤È¡¢¸å½Ò¤Î¡Ö¥Õ¥¡¥¤¥ë¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¡× + ¤Î¾Ï¤ò¥Á¥§¥Ã¥¯¤·¤Æ¤¯¤À¤µ¤¤¡£ +
+ +
"Internal Server Error" ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸
+
Apache + ¤Î¥¨¥é¡¼¥í¥°¤ò¥Á¥§¥Ã¥¯¤¹¤ë¤È¡¢"Premature end of script headers" + ¤È¤¤¤¦¥í¥°¤¬µ­Ï¿¤µ¤ì¤Æ¤¤¤ë¤È»×¤¤¤Þ¤¹¡£¤½¤·¤Æ¡¢¤ª¤½¤é¤¯ CGI + ¥×¥í¥°¥é¥à¤Ë¤è¤Ã¤ÆÀ¸À®¤µ¤ì¤¿¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤âµ­Ï¿¤µ¤ì¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£ + ¤³¤Î¾ì¹ç¡¢CGI ¥×¥í¥°¥é¥à¤¬Å¬ÀÚ¤Ê + HTTP ¥Ø¥Ã¥À¤ò½ÐÎϤǤ­¤Ê¤¤¸¶°ø¤òÃΤ뤿¤á¤Ë¡¢ + °Ê²¼¤Î³Æ¾Ï¤Ç¥Á¥§¥Ã¥¯¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
+
+ +

¥Õ¥¡¥¤¥ë¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó

+ + +

¥µ¡¼¥Ð¤Ï¤¢¤Ê¤¿¤Î¸¢¸Â¤Ç¼Â¹Ô¤µ¤ì¤Æ¤¤¤Ê¤¤¤Î¤ò˺¤ì¤Ê¤¤¤è¤¦¤Ë¡£ + ¤Ä¤Þ¤ê¡¢µ¯Æ°¤¹¤ë¤È¤­¡¢¥µ¡¼¥Ð¤ÏÆø¢¤ò¤â¤¿¤Ê¤¤¥æ¡¼¥¶ - Ä̾ï nobody + ¤ä www ¤Î¸¢¸Â¤Ç¼Â¹Ô¤µ¤ì¤Þ¤¹¡£¤·¤¿¤¬¤Ã¤Æ¡¢¤¢¤Ê¤¿¤¬½êÍ­¤¹¤ë + ¥Õ¥¡¥¤¥ë¤ò¼Â¹Ô¤¹¤ë¤Ë¤ÏÊ̤Υѡ¼¥ß¥Ã¥·¥ç¥ó¤¬É¬ÍפȤʤê¤Þ¤¹¡£ + Ä̾nobody ¤¬¼Â¹Ô¤¹¤ë¤Î¤Ë½½Ê¬¤Ê¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤òÍ¿¤¨¤ëÊýË¡¤Ï¡¢ + ¥Õ¥¡¥¤¥ë¤Ëï¤Ç¤â¼Â¹Ô²Äǽ¤È¤¹¤ë¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤òÍ¿¤¨¤ë¤³¤È¤Ç¤¹:

+ +

+ chmod a+x first.pl +

+ +

¤Þ¤¿¡¢¤â¤·¤¢¤Ê¤¿¤Î¥×¥í¥°¥é¥à¤¬Â¾¤Î¥Õ¥¡¥¤¥ë¤òÆɤ߽ñ¤­¤¹¤ë¤Ê¤é¤Ð¡¢ + ¤½¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ï¡¢¤³¤ì¤¬²Äǽ¤È¤Ê¤ëÀµ¤·¤¤¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó + ¤ò»ý¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ + + +

¥Ñ¥¹¾ðÊó¤È´Ä¶­

+ + +

¥³¥Þ¥ó¥É¥é¥¤¥ó¤«¤é¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ë¤È¤­¡¢ + °Õ¼±¤·¤Ê¤¯¤Æ¤â¥·¥§¥ë¤ËÅϤµ¤ì¤ë¾ðÊ󤬤¢¤ê¤Þ¤¹¡£ + Î㤨¤Ð¡¢»²¾È¤¹¤ë¥Õ¥¡¥¤¥ë¤Î¤¿¤á¤Ë¤É¤³¤ò¸¡º÷¤·¤¿¤é¤è¤¤¤«¤ò + ¥·¥§¥ë¤ËÅÁ¤¨¤ë PATH ¤¬¤¢¤ê¤Þ¤¹¡£

+ +

¥×¥í¥°¥é¥à¤¬ CGI ¥×¥í¥°¥é¥à¤È¤·¤Æ¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë¤è¤Ã¤Æ¼Â¹Ô¤µ¤ì¤ë¤È¤­¡¢ + ¤½¤ì¤ÏƱ¤¸ PATH ¤Ç¤Ï¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + CGI ¥×¥í¥°¥é¥àÆâ¤Ç¸Æ¤Ó½Ð¤¹¤¢¤é¤æ¤ë¥×¥í¥°¥é¥à + (Î㤨¤Ð¡¢sendmail ¤Î¤è¤¦¤Ê¤â¤Î) ¤Ï¡¢ + ¥Õ¥ë¥Ñ¥¹¤Ç»ØÄꤹ¤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£¤½¤ì¤Ë¤è¤ê¡¢CGI + ¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤·¤è¤¦¤È¤·¤¿¤È¤­¡¢ + ¥·¥§¥ë¤Ï¤½¤Î¤è¤¦¤Ê¥×¥í¥°¥é¥à¤ò¸«¤Ä¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

ƱÍͤʤ³¤È¤Ï¡¢¥¹¥¯¥ê¥×¥È¤Î¥¤¥ó¥¿¥×¥ê¥¿ (¤·¤Ð¤·¤Ð perl) + ¤Ø¤Î¥Ñ¥¹¤Ç¡¢CGI ¥×¥í¥°¥é¥à¤Î 1 ¹ÔÌܤ˼¡¤Î¤è¤¦¤Ë¼¨¤µ¤ì¤Þ¤¹:

+ +

+ #!/usr/bin/perl +

+ +

¤³¤ì¤¬¥¤¥ó¥¿¡¼¥×¥ê¥¿¤Ø¤Î¼ÂºÝ¤Î¥Ñ¥¹¤Ç¤¢¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤ª¤­¤Þ¤¹¡£

+ + +

¤Þ¤¿¡¢CGI ¥×¥í¥°¥é¥à¤¬Â¾¤Î´Ä¶­ÊÑ¿ô¤Ë°Í¸¤·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢¤½¤Î´Ä¶­ÊÑ¿ô¤¬ + Apache ¤«¤éÅϤµ¤ì¤ë¤è¤¦¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

¥×¥í¥°¥é¥à¥¨¥é¡¼

+ + +

CGI + ¥×¥í¥°¥é¥à¤¬¼ºÇÔ¤¹¤ë¤Î¤ÏÂçÄñ¡¢¥×¥í¥°¥é¥à¼«¿È¤ËÌäÂ꤬¤¢¤ë¾ì¹ç¤Ç¤¹¡£ + °ìÅÙ CGI ¤Î»È¤¤Êý¤òÍý²ò¤·¡¢Á°½Ò¤ÎÆó¤Ä¤Î¸í¤ê¤òÈȤ·¤Æ¤¤¤Ê¤¤¤Ê¤é¤Ð¡¢ + ¤Þ¤º´Ö°ã¤¤¤Ê¤¯¤½¤¦¤Ç¤·¤ç¤¦¡£¥Ö¥é¥¦¥¶¤ò»È¤Ã¤Æ¥Æ¥¹¥È¤¹¤ëÁ°¤Ë + ¤Þ¤º³Îǧ¤¹¤ë¤³¤È¤Ï¡¢¥³¥Þ¥ó¥É¥é¥¤¥ó¤«¤é¥×¥í¥°¥é¥à¤¬¼Â¹Ô¤Ç¤­¤ë¤³¤È¤Ç¤¹¡£ + Î㤨¤Ð¡¢°Ê²¼¤ò¼Â¹Ô¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤:

+ +

+ cd /usr/local/apache2/cgi-bin
+ ./first.pl +

+ +

(perl ¥¤¥ó¥¿¥×¥ê¥¿¤Ï¸Æ¤Ð¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + ¥·¥§¥ë¤È Apache ¤¬¥¹¥¯¥ê¥×¥È¤ÎºÇ½é¤Î¹Ô¤Î ¥Ñ¥¹¾ðÊó ¤ò»È¤Ã¤Æ¸«¤Ä¤±¤Þ¤¹¡£)

+ +

ºÇ½é¤Ë¥×¥í¥°¥é¥à¤«¤é½ÐÎϤµ¤ì¤ë¤Î¤Ï Content-Type ¤ò´Þ¤ß¡¢ + ¸å¤Ë¶õ¹Ô¤Î³¤¯ HTTP ¥Ø¥Ã¥À¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£Â¾¤Î¤â¤Î¤¬½ÐÎϤµ¤ì¤Æ¤¤¤ë + ¾ì¹ç¤Ï¡¢Apache ¤Ï¤³¤Î¥×¥í¥°¥é¥à¤ò¥µ¡¼¥Ð·Ðͳ¤Ç¼Â¹Ô¤·¤è¤¦¤È¤·¤¿¤È¤­¤Ë¤Ï + Premature end of script headers ¥¨¥é¡¼¤ò½ÐÎϤ·¤Þ¤¹¡£¾ÜºÙ¤Ï + ¾åµ­¤Î CGI ¥×¥í¥°¥é¥à¤ò½ñ¤¯ ¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£

+ + +

¥¨¥é¡¼¥í¥°

+ + +

¥¨¥é¡¼¥í¥°¤Ïͧã¤Ç¤¹¡£ + Á´¤Æ¤Î¤¦¤Þ¤¯¤¤¤«¤Ê¤¤¤³¤È¤Ï¡¢¥¨¥é¡¼¥í¥°¤Ë¥á¥Ã¥»¡¼¥¸¤òÀ¸À®¤·¤Þ¤¹¡£ + ɬ¤º¤½¤ì¤òºÇ½é¤Ë¸«¤ë¤Ù¤­¤Ç¤¹¡£ + ¤â¤·¡¢¤¢¤Ê¤¿¤¬¥¦¥§¥Ö¥µ¥¤¥È¤ò¼çºÅ¤·¤Æ¤¤¤ë¾ì½ê¤¬ + ¥¨¥é¡¼¥í¥°¤Î»²¾È¤òµö¤·¤Æ¤¤¤Ê¤¤¤Ê¤é¤Ð¡¢¤­¤Ã¤È¾¤Î¥µ¥¤¥È¤Ç¼çºÅ¤¹¤ë¤Ù¤­¤Ç¤¹¡£ + ¥¨¥é¡¼¥í¥°¤ÎÆɤßÊý¤ò³Ø¤Ö¤³¤È¤Ç¡¢¤Û¤È¤ó¤ÉÁ´¤Æ¤ÎÌäÂ꤬¿×®¤Ë³Îǧ¤µ¤ì¡¢ + ¿×®¤Ë²ò·è¤µ¤ì¤ë¤È¤¤¤¦¤³¤È¤¬Ê¬¤«¤ë¤Ç¤·¤ç¤¦¡£

+ + +

Suexec

+ + +

suexec ¥µ¥Ý¡¼¥È¥×¥í¥°¥é¥à¤Ï + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ä¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Î¾ì½ê¤Ë°Í¤Ã¤Æ + CGI ¥×¥í¥°¥é¥à¤ò°ã¤¦¥æ¡¼¥¶¸¢¸Â¤Î²¼¤ÇÁö¤é¤»¤ë¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£ + Suexec ¤Î¸¢¸Â¤Î¥Á¥§¥Ã¥¯¤ÏÈó¾ï¤Ë¸·¤·¤¯¡¢¤½¤ì¤òËþ¤¿¤µ¤Ê¤¤¾ì¹ç¤Ï + CGI ¥×¥í¥°¥é¥à¤¬ Premature end of script headers ¥¨¥é¡¼¤Ç + ¼Â¹Ô¤µ¤ì¤Þ¤»¤ó¡£

+ +

suexec ¤ò»È¤Ã¤Æ¤¤¤ë¤«¤É¤¦¤«¤òÄ´¤Ù¤¿¤á¤Ë¤Ï apachectl + -V ¤ò¼Â¹Ô¤·¤Æ¡¢SUEXEC_BIN ¤Î¾ì½ê¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£ + Apache ¤¬¤½¤³¤Ë suexec ¤Î¥Ð¥¤¥Ê¥ê¤òȯ¸«¤·¤¿¾ì¹ç¤Ï¡¢suexec ¤¬ + »ÈÍѤµ¤ì¤Þ¤¹¡£

+ +

suexec ¤ò´°Á´¤ËÍý²ò¤·¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢»È¤¦¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + suexec ¤ò̵¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢SUEXEC_BIN ¤«¤é»Ø¤µ¤ì¤Æ¤¤¤ë + suexec ¥Ð¥¤¥Ê¥ê¤òºï½ü (¤«Ì¾Á°¤òÊѹ¹) ¤¹¤ë¤À¤±¤Ç¤¹¡£ + suexec ¤òÆɤó¤À¸å¤Ç¡¢¤Þ¤À¤½¤ì¤ò + »È¤¤¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢suexec -V ¤ò¼Â¹Ô¤·¤Æ suexec ¤Î + ¥í¥°¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ¤òÄ´¤Ù¡¢¤½¤Î¥í¥°¥Õ¥¡¥¤¥ë¤ò»È¤Ã¤Æ¥Ý¥ê¥·¡¼°ãÈ¿¤ò + ¸«¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£

+ +
top
+
+

΢¤Ç²¿¤¬µ¯¤³¤Ã¤Æ¤¤¤ë¤Î¤«?

+ + +

CGI ¥×¥í¥°¥é¥ß¥ó¥°¤Ë½¬½Ï¤¹¤ë¤È¡¢ + ΢¤Çµ¯¤³¤Ã¤Æ¤¤¤ë¤³¤È¤Ë¤Ä¤¤¤Æ¹¹¤ËÍý²ò¤¹¤ë¤³¤È¤ÎÌò¤ËΩ¤Á¤Þ¤¹¡£ + ¥Ö¥é¥¦¥¶¤È¥µ¡¼¥Ð¤¬¤É¤Î¤è¤¦¤ËÁê¸ßÄÌ¿®¤¹¤ë¤«¤Ë¤Ä¤¤¤Æ¤ÏÆäˤ½¤¦¤Ç¤¹¡£ + ¤Ê¤¼¤Ê¤é¡¢"Hello, World." + ¤ò°õ»ú¤¹¤ë¥×¥í¥°¥é¥à¤ò½ñ¤¯¤³¤È¤Ï¤ª¤ª¤¤¤Ë·ë¹½¤Ç¤¹¤¬¡¢ + ¤½¤ì¤ÏÆäËÍ­±×¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +

´Ä¶­ÊÑ¿ô

+ + +

´Ä¶­ÊÑ¿ô¤Ï¡¢ + ¤¢¤Ê¤¿¤¬¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¦¤È¤­¤ËÊÕ¤ê¤Ë¸ºß¤·¤Æ¤¤¤ëÃͤǤ¹¡£ + ¤½¤ì¤é¤Ï¡¢¥Ñ¥¹ + (¥³¥Þ¥ó¥É¤ò¥¿¥¤¥×¤·¤¿¤È¤­¤Ë¼Â¹Ô¤¹¤ë¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë¤òõ¤·½Ð¤¹¤È¤³¤í)¡¢ + ¥æ¡¼¥¶Ì¾¡¢Ã¼Ëö·¿¤Ê¤É¤Î¤è¤¦¤ÊÊØÍø¤Ê¤â¤Î¤Ç¤¹¡£ + Ä̾ÉáÃÊ»ÈÍѤ·¤Æ¤¤¤ë´Ä¶­ÊÑ¿ô¤Î´°Á´¤Ê¥ê¥¹¥È¤òÄ´¤Ù¤ë¤Ë¤Ï¡¢ + ¥³¥Þ¥ó¥É¥×¥í¥ó¥×¥È¤Ç env ¤òÆþÎϤ·¤Þ¤¹¡£

+ +

CGI ¤Î½èÍýÃæ¡¢¥µ¡¼¥Ð¤È¥Ö¥é¥¦¥¶¤â´Ä¶­ÊÑ¿ô¤òÀßÄꤷ¡¢ + ¤½¤ì¤Ë¤è¤êÁê¸ß¤ËÄÌ¿®¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤½¤Î´Ä¶­ÊÑ¿ô¤Ï¡¢¥Ö¥é¥¦¥¶¥¿¥¤¥× (Netscape, IE, Lynx)¡¢¥µ¡¼¥Ð¥¿¥¤¥× + (Apache, IIS, WebSite)¡¢¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë CGI + ¥×¥í¥°¥é¥à¤Î̾Á°¤Ê¤É¤Ç¤¹¡£

+ +

¤³¤ì¤é¤ÎÊÑ¿ô¤Ï CGI ¥×¥í¥°¥é¥Þ¤¬»ÈÍѤǤ­¤Þ¤¹¡£ + ¤½¤·¤Æ¡¢¤½¤ì¤Ï¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¤ÎÄÌ¿®¤ÎÏäÎȾʬ¤Ç¤¹¡£ + ɬÍפÊÊÑ¿ô¤Î´°Á´¤Ê¥ê¥¹¥È¤Ï http://hoohoo.ncsa.uiuc.edu/cgi/env.html ¤Ë¤¢¤ê¤Þ¤¹¡£

+ +

°Ê²¼¤Îñ½ã¤Ê Perl CGI + ¥×¥í¥°¥é¥à¤Ï¡¢ÅϤµ¤ì¤ëÁ´¤Æ¤Î´Ä¶­ÊÑ¿ô¤òɽ¼¨¤·¤Þ¤¹¡£Æ±ÍÍ¤Î¥×¥í¥°¥é¥à¤Ï¡¢ + Apache ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Î cgi-bin + ¥Ç¥£¥ì¥¯¥È¥ê¤ËÆó¤Ä´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤¤¤¯¤Ä¤«¤ÎÊÑ¿ô¤¬É¬¿Ü¤Ç¤¢¤ê¡¢¤¤¤¯¤Ä¤«¤ÏǤ°Õ¤Ç¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤½¤·¤Æ¡¢¸ø¼°¤Î¥ê¥¹¥È¤Ë¤Ï¤Ê¤¤¤¤¤¯¤Ä¤«¤ÎÊÑ¿ô¤¬É½¼¨¤µ¤ì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤µ¤é¤Ë¡¢Apache ¤Ï¥Ç¥Õ¥©¥ë¥È¤ÇÍÑ°Õ¤µ¤ì¤Æ¤¤¤ë´ðËÜŪ¤Ê¤â¤Î¤Ë + ¤¢¤Ê¤¿¼«¿È¤Î´Ä¶­ÊÑ¿ô¤ò²Ã¤¨¤ë¤¿¤á¤Î¡¢ + ¿¤¯¤Î°Û¤Ê¤ëÊýË¡¤òÍÑ°Õ¤·¤Æ¤·¤Þ¤¹¡£

+ +

+ #!/usr/bin/perl
+ print "Content-type: text/html\n\n";
+ foreach $key (keys %ENV) {
+ + print "$key --> $ENV{$key}<br>";
+ + } +

+ + +

STDIN ¤È STDOUT

+ + +

¥µ¡¼¥Ð¤È¥¯¥é¥¤¥¢¥ó¥È´Ö¤Î¤â¤¦°ì¤Ä¤ÎÄÌ¿®¤Ï¡¢É¸½àÆþÎÏ + (STDIN)¤Èɸ½à½ÐÎÏ (STDOUT) + ¤òÄ̤¸¤Æ¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£Ä̾ï¤Îʸ̮¤Ë¤ª¤¤¤Æ¡¢STDIN + ¤Ï¥­¡¼¥Ü¡¼¥É¤ä¥×¥í¥°¥é¥à¤¬Æ°ºî¤¹¤ë¤¿¤á¤ËÍ¿¤¨¤é¤ì¤ë¥Õ¥¡¥¤¥ë¤ò°ÕÌ£¤·¡¢ + STDOUT ¤ÏÄ̾拾¥ó¥½¡¼¥ë¤Þ¤¿¤Ï¥¹¥¯¥ê¡¼¥ó¤ò°ÕÌ£¤·¤Þ¤¹¡£

+ +

¥¦¥§¥Ö¥Õ¥©¡¼¥à¤«¤é CGI ¥×¥í¥°¥é¥à¤ØPOST + ¤·¤¿¤È¤­¡¢¥Õ¥©¡¼¥à¤Î¥Ç¡¼¥¿¤ÏÆÃÊ̤ʥե©¡¼¥Þ¥Ã¥È¤Ç«¤Í¤é¤ì¡¢ + STDIN ¤òÄ̤·¤Æ¡¢CGI ¥×¥í¥°¥é¥à¤Ë°ú¤­ÅϤµ¤ì¤Þ¤¹¡£ + ¥×¥í¥°¥é¥à¤Ï¥Ç¡¼¥¿¤¬¥­¡¼¥Ü¡¼¥É + ¤â¤·¤¯¤Ï¥Õ¥¡¥¤¥ë¤«¤éÍè¤Æ¤¤¤¿¤«¤Î¤è¤¦¤Ë½èÍý¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¡ÖÆÃÊ̤ʥե©¡¼¥Þ¥Ã¥È¡×¤Ï¤È¤Æ¤âñ½ã¤Ç¤¹¡£¥Õ¥£¡¼¥ë¥É̾¤ÈÃͤϥ¤¥³¡¼¥ë + (=) ¤Ç·ë¤Ð¤ì¤Þ¤¹¡£¤½¤·¤ÆÃͤÎÁȤϥ¢¥ó¥Ñ¥µ¥ó¥É (&) ¤Ç·ë¤Ð¤ì¤Þ¤¹¡£ + ¥¹¥Ú¡¼¥¹¡¢¥¢¥ó¥Ñ¥µ¥ó¥É¡¢¥¤¥³¡¼¥ë¤Î¤è¤¦¤ÊÌÌÅݤÊʸ»ú¤Ï¡¢ + ¤½¤ì¤é¤¬Æ°ºî¤òÂÌÌܤˤ·¤Ê¤¤¤è¤¦¤Ë¤½¤Îʸ»ú¤ËÁêÅö¤¹¤ë 16 ¿Ê¤ËÊÑ´¹¤µ¤ì¤Þ¤¹¡£ + Á´¥Ç¡¼¥¿Ê¸»úÎó¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹: +

+ +

+ name=Rich%20Bowen&city=Lexington&state=KY&sidekick=Squirrel%20Monkey +

+ +

»þ¡¹¡¢¤³¤Î¤è¤¦¤Êʸ»úÎó¤¬ URL + ¤ËÉղ䵤ì¤ë¤Î¤ò¸«¤ë¤Ç¤·¤ç¤¦¡£¤½¤Î¾ì¹ç¡¢¥µ¡¼¥Ð¤Ï + QUERY_STRING ¤È¤¤¤¦´Ä¶­ÊÑ¿ô¤Ë¤½¤Îʸ»úÎó¤òÆþ¤ì¤Þ¤¹¡£¤½¤ì¤Ï + GET ¥ê¥¯¥¨¥¹¥È¤È¸Æ¤Ð¤ì¤Þ¤¹¡£ + HTML ¥Õ¥©¡¼¥à¤Ç¤Ï¡¢¥Ç¡¼¥¿¤òÅϤ¹¤¿¤á¤Ë GET ¤È + POST ¤Î¤É¤Á¤é¤ò»ÈÍѤ¹¤ë¤«¤ò¡¢FORM ¥¿¥°¤Î + METHOD °À­¤ÎÀßÄê¤Ç»ØÄꤷ¤Þ¤¹¡£

+ +

CGI ¥×¥í¥°¥é¥à¤Ï¡¢¤½¤Îʸ»úÎó¤òÌò¤ËΩ¤Ä¾ðÊó¤Ëʬ³ä¤¹¤ëÀÕǤ¤¬¤¢¤ê¤Þ¤¹¡£ + ¹¬¤¤¤Ë¤â¡¢¤½¤Î¥Ç¡¼¥¿½èÍý¤ò½õ¤±¤ë¥é¥¤¥Ö¥é¥ê¤ä¥â¥¸¥å¡¼¥ë¤¬Â¸ºß¤·¤Þ¤¹¡£ + ¤³¤ì¤é¤Ï¡¢CGI ¥×¥í¥°¥é¥à¤Î¾¤ÎÌ̤ǤâƱÍͤËÌò¤ËΩ¤Á¤Þ¤¹¡£

+ +
top
+
+

CGI ¥â¥¸¥å¡¼¥ë/¥é¥¤¥Ö¥é¥ê

+ + +

CGI ¥×¥í¥°¥é¥à¤ò½ñ¤¯¤È¤­¡¢ÌÌÅݤʻŻö¤ÎÂçÉôʬ¤ò¤·¤Æ¤¯¤ì¤ë + ¥³¡¼¥É¥é¥¤¥Ö¥é¥ê¤Þ¤¿¤Ï¥â¥¸¥å¡¼¥ë¤ò»È¤¦¤³¤È¤ò¸¡Æ¤¤¹¤Ù¤­¤Ç¤¹¡£ + ¤³¤ì¤Ï¥¨¥é¡¼¤ò¸º¤é¤·¡¢Áᤤ³«È¯¤Ë¤Ä¤Ê¤¬¤ê¤Þ¤¹¡£

+ +

Perl ¤Ç CGI ¥×¥í¥°¥é¥à¤ò½ñ¤¤¤Æ¤¤¤ë¤Ê¤é¡¢¥â¥¸¥å¡¼¥ë¤Ï CPAN ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤³¤ÎÌÜŪ¤Î¤¿¤á¤ÎºÇ¤âÉáµÚ¤·¤Æ¤¤¤ë¥â¥¸¥å¡¼¥ë¤Ï CGI.pm ¤Ç¤¹¡£ + CGI::Lite ¤â¸¡Æ¤¤·¤Þ¤·¤ç¤¦¡£¤³¤ì¤Ï¡¢¤Û¤È¤ó¤É¤Î¥×¥í¥°¥é¥à + ¤Ë¤ª¤¤¤ÆɬÍפȤ¹¤ë¤¹¤Ù¤Æ¤Îµ¡Ç½¤ÎºÇ¾®¥»¥Ã¥È¤Î¼ÂÁõ¤Ç¤¹¡£

+ +

C ¤Ç CGI ¥×¥í¥°¥é¥à¤ò½ñ¤¤¤Æ¤¤¤ë¤Ê¤é¡¢¤¤¤í¤¤¤í¤Ê + ¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤é¤ÎÆâ¤Î°ì¤Ä¤Ï http://www.boutell.com/cgic/ + ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë CGIC ¥é¥¤¥Ö¥é¥ê¤Ç¤¹¡£

+
top
+
+

¹¹¤Ê¤ë¾ðÊó

+ + +

CGI ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¥¦¥§¥Ö¤Ç¿ô¿¤¯Ä󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£CGI + ¤ÎÌäÂê¤Ë¤Ä¤¤¤Æ¤Ï Usenet ¤Î comp.infosystems.www.authoring.cgi ¤Ç¡¢ + ¾¤Î¥æ¡¼¥¶¤ÈÏÀµÄ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£HTML Writers Guide ¤Î + -servers ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ï¡¢¤¢¤Ê¤¿¤Î¼ÁÌä¤Ë²óÅú¤·¤Æ¤¯¤ì¤ë°ÎÂç¤Ê¥ê¥½¡¼¥¹¤Ç¤¹¡£ + http://www.hwg.org/lists/hwg-servers/ + ¤Ç¹¹¤Ë¿¤¯¤òõ¤·½Ð¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤½¤·¤Æ¤â¤Á¤í¤ó¡¢¤ª¤½¤é¤¯ CGI + ¥×¥í¥°¥é¥à¤ÎÆ°ºî¤Ë´Ø¤¹¤ë¾ÜºÙ¤ÎÁ´¤Æ¤¬µ­½Ò¤µ¤ì¤Æ¤¤¤ë + CGI ¤Î»ÅÍͤòÆɤà¤Ù¤­¤Ç¤¹¡£¥ª¥ê¥¸¥Ê¥ë¥Ð¡¼¥¸¥ç¥ó¤ò + NCSA + ¤Ç¡¢¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿¥É¥é¥Õ¥È¤ò + Common Gateway Interface RFC + ¥×¥í¥¸¥§¥¯¥È¤Ç»²¾È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

CGI ¤ÎÌäÂê¤Ë¤Ä¤¤¤Æ¡¢²Ã¤ï¤Ã¤Æ¤¤¤ë¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Þ¤¿¤Ï¥Ë¥å¡¼¥¹ + ¥°¥ë¡¼¥×¤Ë¼ÁÌä¤òÁ÷¤ë¤È¤­¡¢µ¯¤³¤Ã¤¿¤â¤Î¡¢µ¯¤³¤Ã¤Æ¤Û¤·¤¤¤³¤È¡¢ + ¼ÂºÝ¤Ëµ¯¤³¤Ã¤¿¤³¤È¤¬¤É¤¦°ã¤¦¤«¡¢»ÈÍѤ·¤Æ¤¤¤ë¥µ¡¼¥Ð¡¢ + CGI ¥×¥í¥°¥é¥à¤òµ­½Ò¤·¤Æ¤¤¤ë¸À¸ì¤Ë´Ø¤¹¤ë½½Ê¬¤Ê¾ðÊó¤È¡¢ + ²Äǽ¤Ç¤¢¤ì¤ÐÌäÂê¤Î¥³¡¼¥É¤òÄ󶡤¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤½¤¦¤¹¤ë¤³¤È¤Ç¡¢ÌäÂ꤬¤è¤ê´Öñ¤Ë¸«¤Ä¤«¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Apache ¤Î¥½¡¼¥¹¥³¡¼¥É¤Ë¤ª¤¤¤ÆÌäÂê¤òȯ¸«¤·¤¿¤³¤È¤ò³Î¿®¤·¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢ + CGI ¤ÎÌäÂê¤Ë´Ø¤¹¤ë¼ÁÌä¤ò Apache + ¥Ð¥°¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÁ÷¤ë¤Ù¤­¤Ç¤Ê¤¤ + ¤³¤È¤ËÃíÌܤ·¤Æ¤¯¤À¤µ¤¤¡£

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/cgi.html.ko.euc-kr b/docs/manual/howto/cgi.html.ko.euc-kr new file mode 100644 index 00000000..da8c9bad --- /dev/null +++ b/docs/manual/howto/cgi.html.ko.euc-kr @@ -0,0 +1,503 @@ + + + +¾ÆÆÄÄ¡ ÅõÅ丮¾ó: CGI¸¦ »ç¿ëÇÑ µ¿Àû ÆäÀÌÁö »ý¼º - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

¾ÆÆÄÄ¡ ÅõÅ丮¾ó: CGI¸¦ »ç¿ëÇÑ µ¿Àû ÆäÀÌÁö »ý¼º

+
+

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

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

¼Ò°³

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

CGI (Common Gateway Interface)´Â À¥¼­¹ö°¡ º¸Åë CGI ÇÁ·Î±×·¥ + ȤÀº CGI ½ºÅ©¸³Æ®¶ó°í ºÎ¸£´Â, (À¥ÆäÀÌÁö ³»¿ëÀ» ¸¸µå´Â) ¿ÜºÎ + ÇÁ·Î±×·¥°ú Åë½ÅÇÏ´Â ¹æ¹ýÀ» Á¤ÀÇÇÑ´Ù. À¥»çÀÌÆ®¿¡¼­ µ¿ÀûÀÎ + ÆäÀÌÁö¸¦ ¸¸µå´Â °¡Àå ÈçÇÏ°í °£´ÜÇÑ ¹æ¹ýÀÌ´Ù. ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ + À¥¼­¹ö¿¡ CGI¸¦ ±¸¼ºÇÏ´Â ¹æ¹ýÀ» ¼Ò°³ÇÏ°í, CGI ÇÁ·Î±×·¥À» + ÀÛ¼ºÇغ»´Ù.

+
top
+
+

CGI¸¦ Çã¿ëÇϵµ·Ï ¾ÆÆÄÄ¡ ¼³Á¤Çϱâ

+ + +

CGI ÇÁ·Î±×·¥ÀÌ ¿Ã¹Ù·Î µ¿ÀÛÇÏ·Á¸é CGI ½ÇÇàÀÌ °¡´ÉÇϵµ·Ï + ¾ÆÆÄÄ¡¸¦ ¼³Á¤ÇØ¾ß ÇÑ´Ù. ¼³Á¤ÇÏ´Â ¹æ¹ýÀº ¿©·¯°¡Áö´Ù.

+ +

ScriptAlias

+ + +

ScriptAlias + Áö½Ã¾î¸¦ »ç¿ëÇÏ¸é ¾ÆÆÄÄ¡´Â ƯÁ¤ µð·ºÅ丮¸¦ CGI ÇÁ·Î±×·¥¿ëÀ¸·Î + µÐ´Ù. ¾ÆÆÄÄ¡´Â ÀÌ µð·ºÅ丮¿¡ ÀÖ´Â ¸ðµç ÆÄÀÏÀÌ CGI + ÇÁ·Î±×·¥À̶ó°í °¡Á¤ÇÏ¿© Ŭ¶óÀ̾ðÆ®°¡ ÀÚ¿øÀ» ¿äûÇϸé ÀÚ¿øÀ» + ½ÇÇàÇÏ·Á°í ½ÃµµÇÑ´Ù.

+ +

ScriptAlias + Áö½Ã¾î´Â ´ÙÀ½°ú °°ÀÌ »ç¿ëÇÑ´Ù.

+ +

+ ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/ +

+ +

À§ ¿¹Á¦´Â ¾ÆÆÄÄ¡¸¦ ±âº» Àå¼Ò¿¡ ¼³Ä¡ÇÑ °æ¿ì + httpd.conf ¼³Á¤ÆÄÀÏ¿¡ ÀÖ´Â ³»¿ëÀÌ´Ù. ScriptAlias Áö½Ã¾î´Â Alias Áö½Ã¾î¿Í °°ÀÌ URL + ¾ÕºÎºÐÀ» ƯÁ¤ µð·ºÅ丮·Î ´ëÀÀÇÑ´Ù. + Alias¿Í + ScriptAlias´Â º¸Åë DocumentRoot µð·ºÅ丮 ¹Û¿¡ ÀÖ´Â + µð·ºÅ丮¿¡ »ç¿ëÇÑ´Ù. Alias¿Í + ScriptAliasÀÇ Â÷ÀÌÁ¡Àº + ScriptAlias°¡ Ãß°¡·Î URL ¾ÕºÎºÐÀ¸·Î + ½ÃÀÛÇÏ´Â ¸ðµç ÆÄÀÏÀ» CGI ÇÁ·Î±×·¥À¸·Î Ãë±ÞÇÏ´Â Á¡ÀÌ´Ù. + ±×·¡¼­ À§ÀÇ ¼³Á¤Àº ¾ÆÆÄÄ¡¿¡°Ô /cgi-bin/À¸·Î + ½ÃÀÛÇÏ´Â ÀÚ¿øÀ» ¿äûÇϸé + /usr/local/apache2/cgi-bin/ µð·ºÅ丮¿¡¼­ + ã¾Æ¼­ CGI ÇÁ·Î±×·¥À¸·Î ó¸®Ç϶ó°í ¾Ë¸°´Ù.

+ +

¿¹¸¦ µé¾î, URL + http://www.example.com/cgi-bin/test.plÀ» + ¿äûÇÏ¸é ¾ÆÆÄÄ¡´Â + /usr/local/apache2/cgi-bin/test.pl ÆÄÀÏÀ» + ½ÇÇàÇÏ¿© °á°ú¸¦ ¹ÝȯÇÑ´Ù. ¹°·Ð ÆÄÀÏÀÌ Á¸ÀçÇÏ°í ½ÇÇà°¡´ÉÇϸç + ¾î¶² ¹æ¹ýÀ¸·Îµç Ãâ·ÂÀ» ÇØ¾ß ÇÑ´Ù. ±×·¸Áö ¾ÊÀ¸¸é ¾ÆÆÄÄ¡´Â + ¿À·ù¹®À» º¸³½´Ù.

+ + +

ScriptAlias µð·ºÅ丮 ¹Û¿¡ ÀÖ´Â CGI

+ + +

º¸Åë º¸¾È»ó ÀÌÀ¯¶§¹®¿¡ CGI ÇÁ·Î±×·¥Àº ScriptAliasÇÑ µð·ºÅ丮¿¡ + ÇÑÁ¤ÇÑ´Ù. ±×·¡¼­ °ü¸®ÀÚ´Â ´©°¡ CGI ÇÁ·Î±×·¥À» »ç¿ëÇÒ ¼ö + ÀÖ´ÂÁö ¾ö°ÝÈ÷ °¨µ¶ÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª Àû´çÇÑ º¸¾ÈÁ¶Ä¡¸¦ + ÃëÇß´Ù¸é ¾Æ¹« µð·ºÅ丮¿¡¼­³ª CGI ÇÁ·Î±×·¥À» ½ÇÇàÇÏÁö ¾ÊÀ» + ÀÌÀ¯°¡ ¾ø´Ù. ¿¹¸¦ µé¾î, UserDir Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + »ç¿ëÀÚ°¡ ÀÚ½ÅÀÇ È¨µð·ºÅ丮¿¡ À¥ÆäÀÌÁö¸¦ °¡Áö´Â °æ¿ì¸¦ + °¡Á¤ÇÏÀÚ. »ç¿ëÀÚ°¡ ÀÚ½ÅÀÇ CGI ÇÁ·Î±×·¥À» »ç¿ëÇÏ°í ½ÍÀºµ¥ + cgi-bin µð·ºÅ丮¿¡ Á¢±Ù±ÇÇÑÀÌ ¾ø´Ù¸é, ´Ù¸¥ + °÷¿¡¼­¶óµµ CGI ÇÁ·Î±×·¥À» ½ÇÇàÇÏ°í ½ÍÀ» °ÍÀÌ´Ù.

+ +

¾Æ¹« µð·ºÅ丮¿¡¼­³ª CGI ½ÇÇàÀ» Çã¿ëÇÏ·Á¸é µÎ °úÁ¤ÀÌ + ÇÊ¿äÇÏ´Ù. ¸ÕÀú, AddHandler³ª SetHandler Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + cgi-script Çڵ鷯¸¦ ÀÛµ¿ÇØ¾ß ÇÑ´Ù. µÎ¹ø°·Î, + Options Áö½Ã¾î¿¡ + ExecCGI¸¦ ÁöÁ¤ÇØ¾ß ÇÑ´Ù.

+ + +

Options¸¦ »ç¿ëÇÏ¿© ¸í½ÃÀûÀ¸·Î CGI ½ÇÇàÀ» Çã¿ëÇϱâ

+ + +

¼­¹öÀÇ ÁÖ¼³Á¤ÆÄÀÏ¿¡ Á÷Á¢ Options Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ƯÁ¤ + µð·ºÅ丮¿¡¼­ CGI ½ÇÇàÀ» Çã¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

+ <Directory /usr/local/apache2/htdocs/somedir>
+ + Options +ExecCGI
+ + </Directory> +

+ +

À§ Áö½Ã¾î·Î ¾ÆÆÄÄ¡´Â CGI ÆÄÀÏÀÇ ½ÇÇàÀ» Çã¿ëÇÑ´Ù. ¾î¶² + ÆÄÀÏÀÌ CGI ÆÄÀÏÀÎÁöµµ ¼­¹ö¿¡°Ô ¾Ë·Á¾ß ÇÑ´Ù. ´ÙÀ½ AddHandler Áö½Ã¾î´Â ¼­¹ö¿¡°Ô + È®ÀåÀÚ°¡ cgi³ª plÀÎ ÆÄÀÏÀº ¸ðµÎ + CGI ÇÁ·Î±×·¥À̶ó°í ¾Ë¸°´Ù.

+ +

+ AddHandler cgi-script .cgi .pl +

+ + +

.htaccess ÆÄÀÏ

+ + +

.htaccess ÅõÅ丮¾óÀº + httpd.conf¿¡ Á¢±Ù±ÇÇÑÀÌ ¾ø´Â °æ¿ì¿¡ CGI ÇÁ·Î±×·¥À» + »ç¿ëÇÒ ¼ö ÀÖ´Â ¹æ¹ýÀ» ¾Ë·ÁÁØ´Ù.

+ + +

»ç¿ëÀÚ µð·ºÅ丮

+ + +

¾Æ·¡ ¼³Á¤À» »ç¿ëÇÏ¸é »ç¿ëÀÚ µð·ºÅ丮¿¡¼­ .cgi·Î + ³¡³ª´Â ÆÄÀÏÀ» CGI ÇÁ·Î±×·¥À¸·Î ½ÇÇàÇÑ´Ù.

+ +

+ <Directory /home/*/public_html>
+ + Options +ExecCGI
+ AddHandler cgi-script .cgi
+ + </Directory> +

+ +

´ÙÀ½À» »ç¿ëÇÏ¸é »ç¿ëÀÚ µð·ºÅ丮ÀÇ cgi-bin + ÇÏÀ§µð·ºÅ丮¿¡ ÀÖ´Â ¸ðµç ÆÄÀÏÀ» CGI ÇÁ·Î±×·¥À¸·Î ÀνÄÇÑ´Ù.

+ +

+ <Directory /home/*/public_html/cgi-bin>
+ + Options ExecCGI
+ SetHandler cgi-script
+ + </Directory> +

+ + + +
top
+
+

CGI ÇÁ·Î±×·¥ ÀÛ¼ºÇϱâ

+ + +

``ÀϹÝÀûÀÎ'' ÇÁ·Î±×·¡¹Ö°ú CGI ÇÁ·Î±×·¡¹Ö »çÀÌ¿¡´Â µÎ°¡Áö + ÁÖµÈ Â÷ÀÌÁ¡ÀÌ ÀÖ´Ù.

+ +

ù¹ø° Â÷ÀÌ´Â CGI ÇÁ·Î±×·¥Àº ´Ù¸¥ Ãâ·ÂÀ» ÇϱâÀü¿¡ ¸ÕÀú + MIME-type Çì´õ¸¦ Ãâ·ÂÇØ¾ß ÇÑ´Ù´Â Á¡ÀÌ´Ù. HTTP Çì´õ´Â + Ŭ¶óÀ̾ðÆ®¿¡°Ô Ŭ¶óÀ̾ðÆ®°¡ ¾î¶² ³»¿ëÀ» ¹Þ°ÔµÉÁö ¹Ì¸® ¾Ë¸°´Ù. + º¸Åë ´ÙÀ½°ú °°´Ù.

+ +

+ Content-type: text/html +

+ +

µÎ¹ø° Â÷ÀÌ´Â HTML ȤÀº ºê¶ó¿ìÀú°¡ º¸¿©ÁÙ ¼ö ÀÖ´Â Çü½ÄÀ¸·Î + Ãâ·ÂÇØ¾ß ÇÑ´Ù´Â Á¡ÀÌ´Ù. ´ëºÎºÐÀÇ °æ¿ì HTMLÀ» Ãâ·ÂÇÏÁö¸¸, + ¶§¶§·Î gif ±×¸²°ú °°ÀÌ HTMLÀÌ ¾Æ´Ñ ³»¿ëÀ» Ãâ·ÂÇÏ´Â CGI + ÇÁ·Î±×·¥À» ÀÛ¼ºÇÏ´Â °æ¿ìµµ ÀÖ´Ù.

+ +

µÎ°¡Áö¸¦ Á¦¿ÜÇÏ°í´Â CGI ÇÁ·Î±×·¥ ÀÛ¼ºÀº ÀÌ¹Ì ¸¸µé¾î º¸¾ÒÀ» + ´Ù¸¥ ÇÁ·Î±×·¥µé°ú ¸Å¿ì ºñ½ÁÇÏ´Ù.

+ +

óÀ½À¸·Î ¸¸µç CGI ÇÁ·Î±×·¥

+ + +

´ÙÀ½Àº ºê¶ó¿ìÀú¿¡ ÇÑ ÁÙÀ» Âï´Â CGI ÇÁ·Î±×·¥ ¿¹Á¦´Ù. + ±×´ë·Î first.plÀ̶ó´Â ÆÄÀÏ¿¡ ÀúÀåÇÏ°í, + cgi-bin µð·ºÅ丮¿¡ º¹»çÇÑ´Ù.

+ +

+ #!/usr/bin/perl
+ print "Content-type: text/html\n\n";
+ print "Hello, World."; +

+ +

Perl¿¡ Àͼ÷ÇÏÁö ¾Ê´õ¶óµµ ¹«½¼ ÀÏÀÌ ÀϾ´ÂÁö ¾Ë ¼ö + ÀÖ´Ù. ù¹ø° ÁÙÀº ¾ÆÆÄÄ¡(ȤÀº »ç¿ëÇÏ´Â ½©)¿¡°Ô + /usr/bin/perl À§Ä¡¿¡ ÀÖ´Â ÀÎÅÍÇÁ¸®ÅÍÀ» »ç¿ëÇÏ¿© + ÀÌ ÇÁ·Î±×·¥ ÆÄÀÏÀ» ½ÇÇàÇ϶ó°í ¾Ë¸°´Ù. µÎ¹ø° ÁÙÀº ¹æ±Ý + ¸»ÇÑ content-type ¼±¾ðÀ» Ãâ·ÂÇÏ°í carriage-return ÁٹٲÞÀ» + µÎ¹ø Ãâ·ÂÇÑ´Ù. ±×·¯¸é Çì´õ µÚ¿¡ HTTP Çì´õÀÇ ³¡À» ¶æÇÏ´Â + ºóÁÙÀÌ »ý±â°í, º»¹®ÀÌ ½ÃÀÛÇÑ´Ù. ¼¼¹ø° ÁÙÀº "Hello, World." + ¹®ÀÚ¿­À» Ãâ·ÂÇÑ´Ù. ÀÌ°ÍÀ¸·Î ³¡ÀÌ´Ù.

+ +

ºê¶ó¿ìÀú¸¦ ½ÇÇàÇÏ°í ÁÖ¼Ò¸¦ ÀÔ·ÂÇÑ´Ù

+ +

+ http://www.example.com/cgi-bin/first.pl +

+ +

ÆÄÀÏ Àå¼Ò¸¦ ÀÔ·ÂÇϸé, ºê¶ó¿ìÀúâ¿¡ Hello, World. + ÇÑ ÁÙÀÌ º¸ÀδÙ. ÈïºÐµÇÁö´Â ¾ÊÁö¸¸, Çѹø µ¿ÀÛÇÏ´Â °ÍÀ» + º¸¾ÒÀ¸´Ï ÀÌÁ¦ ´Ù¸¥ °ÍÀ» ½ÃµµÇØ º¼ ¼ö ÀÖ´Ù.

+ +
top
+
+

±×·¯³ª ¾ÆÁ÷ µ¿ÀÛÇÏÁö ¾Ê¾Æ¿ä!

+ + +

À¥¿¡¼­ CGI ÇÁ·Î±×·¥¿¡ Á¢±ÙÇÒ¶§ ºê¶ó¿ìÀú¿¡ ³ª¿Ã ¼ö ÀÖ´Â + ³»¿ëÀº ±âº»ÀûÀ¸·Î ³×°¡Áö´Ù.

+ +
+
CGI ÇÁ·Î±×·¥ÀÇ Ãâ·Â
+
ÁÁ´Ù! ¸ðµç °ÍÀÌ Àß µ¿ÀÛÇÑ´Ù´Â ¶æÀÌ´Ù. Ãâ·ÂÀº Á¤È®ÇÏÁö¸¸ + ºê¶ó¿ìÀú°¡ ¿Ã¹Ù·Î ó¸®ÇÏÁö ¸øÇÑ´Ù¸é, CGI ÇÁ·Î±×·¥¿¡¼­ + ¿Ã¹Ù¸¥ Content-TypeÀ» ¼³Á¤ÇÏ¿´´ÂÁö È®ÀÎÇÑ´Ù.
+ +
CGI ÇÁ·Î±×·¥ ¼Ò½ºÄÚµå ȤÀº "POST Method Not Allowed" + ¹®±¸
+
CGI ÇÁ·Î±×·¥À» ½ÇÇàÇϵµ·Ï ¾ÆÆÄÄ¡¸¦ ÀûÀýÈ÷ ¼³Á¤ÇÏÁö + ¾Ê¾Ò´Ù´Â ¶æÀÌ´Ù. ¾ÆÆÄÄ¡ ¼³Á¤Çϱâ + ÀýÀ» ´Ù½Ã ÀÐ°í »©¸ÔÀº ºÎºÐÀÌ ÀÖ´ÂÁö ã¾ÆºÁ¶ó.
+ +
"Forbidden"À¸·Î ½ÃÀÛÇÏ´Â ¹®±¸
+
±ÇÇÑ ¹®Á¦°¡ ÀÖ´Ù´Â ¶æÀÌ´Ù. ¾ÆÆÄÄ¡ + ¿À·ù ·Î±×¿Í ¾Æ·¡ ÆÄÀϱÇÇÑ + ÀýÀ» È®ÀÎÇ϶ó.
+ +
"Internal Server Error"¶ó´Â ¹®±¸
+
¾ÆÆÄÄ¡ ¿À·ù ·Î±×¸¦ º¸¸é ¾Æ¸¶µµ + CGI ÇÁ·Î±×·¥ÀÌ Ãâ·ÂÇÑ ¿À·ù¹®°ú ÇÔ²² "Premature end of + script headers"°¡ º¸ÀÏ °ÍÀÌ´Ù. ÀÌ °æ¿ì ¾Æ·¡ ³»¿ëµéÀ» Çϳª¾¿ + È®ÀÎÇÏ¿© ¾î¶² ÀÌÀ¯·Î CGI ÇÁ·Î±×·¥ÀÌ ÀûÀýÇÑ HTTP Çì´õ¸¦ + Ãâ·ÂÇÏÁö ¸øÇß´ÂÁö ¾Ë¾Æº»´Ù.
+
+ +

ÆÄÀϱÇÇÑ

+ + +

¼­¹ö´Â ´ç½Å°ú µ¿ÀÏÇÑ °èÁ¤À¸·Î µ¿ÀÛÇÏÁö ¾ÊÀ½À» ¸í½ÉÇ϶ó. + Áï, ¼­¹ö°¡ ½ÃÀÛÇÏ¸é ¼­¹ö´Â ºñƯ±Ç »ç¿ëÀÚ ±ÇÇÑ(º¸Åë + nobody³ª www)À¸·Î µ¿ÀÛÇÑ´Ù. + ±×·¡¼­ ´ç½ÅÀÌ ¼ÒÀ¯ÇÑ ÆÄÀÏÀ» ½ÇÇàÇÏ·Á¸é ±ÇÇÑÀÌ ÇÊ¿äÇÏ´Ù. + ÆÄÀÏ¿¡ nobody°¡ ½ÇÇàÇϱ⿡ ÃæºÐÇÑ ±ÇÇÑÀ» + ÁÖ±âÀ§ÇØ º¸Åë ¸ðµÎ¿¡°Ô ÆÄÀÏÀÇ ½ÇÇà ±ÇÇÑÀ» ÁØ´Ù.

+ +

+ chmod a+x first.pl +

+ +

¶Ç, ÇÁ·Î±×·¥ÀÌ ´Ù¸¥ ÆÄÀÏÀ» Àаųª ¾´´Ù¸é ÀÌ ÆÄÀÏ¿¡µµ + ÀûÀýÇÑ ±ÇÇÑÀÌ ÇÊ¿äÇÏ´Ù.

+ + + +

°æ·Î Á¤º¸¿Í ȯ°æ

+ + +

¸í·ÉÇà¿¡¼­ ÇÁ·Î±×·¥À» ½ÇÇàÇϸé ÀÚµ¿À¸·Î ¾î¶² Á¤º¸°¡ + ½©·Î Àü´ÞµÈ´Ù. ¿¹¸¦ µé¾î, PATH´Â ½©¿¡°Ô ´ç½ÅÀÌ + ¸»ÇÑ ÆÄÀÏÀ» ãÀ» Àå¼Ò¸¦ ¾Ë·ÁÁØ´Ù.

+ +

À¥¼­¹ö°¡ ÇÁ·Î±×·¥À» CGI ÇÁ·Î±×·¥À¸·Î ½ÇÇàÇÒ¶§´Â + PATH°¡ ´Ù¸¦ ¼ö ÀÖ´Ù. (¿¹¸¦ µé¾î, + sendmail °°ÀÌ) CGI ÇÁ·Î±×·¥ ¾È¿¡¼­ ½ÇÇàÇÏ´Â + ¸í·É¾î´Â ¿ÏÀüÇÑ °æ·Î·Î ¸í½ÃÇØ¾ß ½©ÀÌ ¸í·É¾î¸¦ ãÀ» ¼ö + ÀÖ´Ù.

+ +

°æ·Î ¹®Á¦´Â ´ÙÀ½°ú °°ÀÌ CGI ÇÁ·Î±×·¥ ù¹ø° ÁÙ¿¡ ³ª¿À´Â + ½ºÅ©¸³Æ® ÀÎÅÍÇÁ¸®ÅÍ (º¸Åë perl) °æ·Î¿¡¼­ + ÀÚÁÖ ¹ß»ýÇÑ´Ù.

+ +

+ #!/usr/bin/perl +

+ +

½ÇÁ¦·Î ÀÎÅÍÇÁ¸®ÅÍÀÇ °æ·ÎÀÎÁö È®ÀÎÇÑ´Ù.

+ +

¶Ç, CGI ÇÁ·Î±×·¥ÀÌ ´Ù¸¥ ȯ°æº¯¼ö¸¦ + »ç¿ëÇÑ´Ù¸é ¾ÆÆÄÄ¡°¡ ÀÌ º¯¼öµéÀ» ÇÁ·Î±×·¥¿¡°Ô Àü´ÞÇØ¾ß + ÇÑ´Ù.

+ + + +

ÇÁ·Î±×·¥ ¿À·ù

+ + +

CGI ÇÁ·Î±×·¥ÀÌ ½ÇÆÐÇÏ´Â °æ¿ì ´ëºÎºÐ ÇÁ·Î±×·¥ ÀÚü + ¹®Á¦¶§¹®ÀÌ´Ù. ƯÈ÷ À§ÀÇ µÎ°¡Áö ½Ç¼ö¸¦ ÇÏÁö ¾Ê¾Ò°í ÀÌ ±ÛÀ» + °è¼Ó º¸°í ÀÖ´Ù¸é ´õ´õ¿í ±×·¸´Ù. ¸ÕÀú À¥¼­¹ö¿¡¼­ ½ÇÇàÇϱâ + Àü¿¡ ¸í·ÉÇà¿¡¼­ ÇÁ·Î±×·¥À» ½ÇÇàÇغ»´Ù. ¿¹¸¦ µé¾î, ´ÙÀ½°ú + °°ÀÌ ½ÇÇàÇÑ´Ù.

+ +

+ cd /usr/local/apache2/cgi-bin
+ ./first.pl +

+ +

(perl ÀÎÅÍÇÁ¸®Å͸¦ ½ÇÇàÇÏÁö ¸¶¶ó. ½©°ú + ¾ÆÆÄÄ¡´Â ½ºÅ©¸³Æ® ù¹ø° ÁÙ¿¡ ÀÖ´Â °æ·Î Á¤º¸¸¦ »ç¿ëÇÏ¿© ÀÎÅÍÇÁ¸®Å͸¦ + ã¾Æ¾ß ÇÑ´Ù.)

+ +

ÇÁ·Î±×·¥Àº Á¦ÀÏ ¸ÕÀú Content-TypeÀ» Æ÷ÇÔÇÑ + HTTP Çì´õµéÀ» Ãâ·ÂÇÏ°í ºó ÁÙÀ» Ãâ·ÂÇØ¾ß ÇÑ´Ù. ´Ù¸¥ °ÍÀ» + Ãâ·ÂÇÑ´Ù¸é À¥¼­¹ö¿¡¼­ ½ÇÇàÇÒ °æ¿ì ¾ÆÆÄÄ¡´Â Premature + end of script headers¸¦ ¹ÝȯÇÑ´Ù. ÀÚ¼¼ÇÑ ³»¿ëÀº + À§ÀÇ CGI ÇÁ·Î±×·¥ ÀÛ¼ºÇϱ⸦ Âü°íÇ϶ó.

+ + +

¿À·ù ·Î±×

+ + +

¿À·ù ·Î±×´Â ´ç½Å ÆíÀÌ´Ù. ¹«¾ð°¡ À߸øµÇ¸é ¿À·ù ·Î±×¿¡ + ¹®±¸°¡ »ý±ä´Ù. ¿À·ù ·Î±×¸¦ Á¦ÀÏ ¸ÕÀú »ìÆìºÁ¾ß ÇÑ´Ù. À¥»çÀÌÆ®¸¦ + È£½ºÆÃÇÏ´Â °÷¿¡¼­ ¿À·ù ·Î±×¸¦ º¸Áö ¸øÇÏ°Ô ÇÑ´Ù¸é, ¾Æ¸¶µµ + ´Ù¸¥ ¾÷ü¸¦ ¾Ë¾ÆºÁ¾ß ÇÑ´Ù. ¿À·ù ·Î±×¸¦ º¸´Â ¹æ¹ýÀ» ÀÍÈ÷¸é, + ´ëºÎºÐÀÇ ¹®Á¦¸¦ »¡¸® ÆľÇÇÏ¿© ÇØ°áÇÒ ¼ö ÀÖ´Ù.

+ + +

Suexec

+ + +

suexec Áö¿ø ÇÁ·Î±×·¥À» + »ç¿ëÇÏ¸é ¾î¶² °¡»óÈ£½ºÆ® ȤÀº ¾î¶² »ç¿ëÀÚ µð·ºÅ丮¿¡ ÀÖ´ÂÁö¿¡ + µû¶ó CGI ÇÁ·Î±×·¥À» ´Ù¸¥ »ç¿ëÀÚ ±ÇÇÑÀ¸·Î ½ÇÇàÇÒ ¼ö ÀÖ´Ù. + Suexec´Â ¸Å¿ì ¾ö°ÝÇÏ°Ô ±ÇÇÑÀ» °Ë»çÇϸç, °Ë»ç¸¦ Çϳª¶óµµ + Åë°úÇÏÁö ¸øÇϸé CGI ÇÁ·Î±×·¥À» ½ÇÇàÇÏÁö ¾Ê°í Premature + end of script headers¸¦ ¹ÝȯÇÑ´Ù.

+ +

suexec¸¦ »ç¿ëÇÏ°í ÀÖ´ÂÁö ¾Ë·Á¸é apachectl -V¸¦ + ½ÇÇàÇÏ¿© SUEXEC_BIN À§Ä¡¸¦ È®ÀÎÇÑ´Ù. ¾ÆÆÄÄ¡°¡ + ½ÃÀÛÇÒ¶§ ±× Àå¼Ò¿¡¼­ suexec ½ÇÇàÆÄÀÏÀ» ¹ß°ßÇϸé, suexec¸¦ + »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

suexec¸¦ ¿ÏÀüÈ÷ ÀÌÇØÇÏÁö ¸øÇß´Ù¸é »ç¿ëÇؼ­´Â ¾ÈµÈ´Ù. + suexec¸¦ »ç¿ëÇÏÁö ¾ÊÀ¸·Á¸é SUEXEC_BIN À§Ä¡¿¡ + ÀÖ´Â suexec ½ÇÇàÆÄÀÏÀ» Áö¿ì°í (ȤÀº ÆÄÀϸíÀ» + ¹Ù²Ù°í) ¼­¹ö¸¦ Àç½ÃÀÛÇÏ¸é µÈ´Ù. suexec¿¡ ´ëÇØ ÀÐÀº ´ÙÀ½ ±×·¡µµ + »ç¿ëÇÏ°í ½Í´Ù¸é, suexec -V¸¦ ½ÇÇàÇÏ¿© suexec + ·Î±×ÆÄÀÏ À§Ä¡¸¦ ¾Ë¾Æ³»°í ·Î±×ÆÄÀÏ¿¡¼­ ´ç½ÅÀÌ ¾î¶² ±ÔÄ¢À» + ¾î±â°í ÀÖ´ÂÁö ã´Â´Ù.

+ +
top
+
+

µÚ¿¡¼­´Â ¹«½¼ ÀÏÀÌ ¹ú¾îÁö´Â°¡?

+ + +

CGI ÇÁ·Î±×·¡¹Ö¿¡ Àͼ÷ÇØÁú¼ö·Ï µÚ¿¡¼­ ¹ú¾îÁö´Â ÀÏÀ» ÀÌÇØÇϸé + µµ¿òÀÌ µÈ´Ù. ±¸Ã¼ÀûÀ¸·Î ºê¶ó¿ìÀú¿Í ¼­¹ö°¡ ¼­·Î Åë½ÅÇÏ´Â + ¹æ¹ýÀ» ¸»ÇÏ´Â °ÍÀÌ´Ù. ¸ô¶óµµ "Hello, World."¸¦ Ãâ·ÂÇÏ´Â + ÇÁ·Î±×·¥À» ÀÛ¼ºÇÒ ¼ö ÀÖÁö¸¸ ÀÌ·± ÇÁ·Î±×·¥Àº º°·Î ¾µ¸ð°¡ + ¾ø±â¶§¹®ÀÌ´Ù.

+ +

ȯ°æº¯¼ö

+ + +

ȯ°æº¯¼ö´Â ´ç½ÅÀÌ ÄÄÇ»Å͸¦ »ç¿ëÇÏ´Â µ¿¾È ´ç½Å ÁÖÀ§¸¦ + ¶°´Ù´Ï´Â °ªÀÌ´Ù. ȯ°æº¯¼ö´Â path (ÄÄÇ»ÅÍ°¡ ´ç½ÅÀÌ ÀÔ·ÂÇÑ + ¸í·É¾î¿¡ ÇØ´çÇÏ´Â ½ÇÁ¦ ÆÄÀÏÀ» ã´Â Àå¼Ò), »ç¿ëÀÚ¸í, Å͹̳Π+ Á¾·ù¿Í °°ÀÌ À¯¿ëÇÑ Á¤º¸´Ù. ÀϹÝÀûÀΠȯ°æº¯¼ö¸¦ ¸ðµÎ º¸·Á¸é + ¸í·ÉÇà ÇÁ·ÒÇÁÆ®¿¡¼­ env¸¦ ÀÔ·ÂÇÑ´Ù.

+ +

CGI¸¦ ½ÇÇàÇÒ¶§µµ ¼­¹ö¿Í ºê¶ó¿ìÀú´Â °¢ÀÚÀÇ È¯°æº¯¼ö¸¦ + ¼­·Î ±³È¯ÇÑ´Ù. ÀÌ Á¤º¸¿¡´Â ºê¶ó¿ìÀú Á¾·ù (Netscape, IE, + Lynx), ¼­¹ö Á¾·ù (¾ÆÆÄÄ¡, IIS, WebSite), ½ÇÇàÇÏ´Â CGI + ÇÁ·Î±×·¥¸í µîÀÌ ÀÖ´Ù.

+ +

CGI ÇÁ·Î±×·¡¸Ó´Â ÀÌ·± º¯¼öµéÀ» »ç¿ëÇÒ ¼ö ÀÖ°í, + ȯ°æº¯¼ö´Â Ŭ¶óÀ̾ðÆ®-¼­¹ö Åë½Å¿¡´Â ÀϺκÐÀ» Â÷ÁöÇÑ´Ù. + Àüü Çʼö º¯¼ö ¸ñ·ÏÀº http://hoohoo.ncsa.uiuc.edu/cgi/env.html¿¡ ÀÖ´Ù.

+ +

¾Æ·¡ °£´ÜÇÑ Perl CGI ÇÁ·Î±×·¥Àº Àڽſ¡°Ô Àü´ÞµÈ ¸ðµç + ȯ°æº¯¼ö¸¦ º¸¿©ÁØ´Ù. ¾ÆÆÄÄ¡ ¹èÆ÷º»ÀÇ cgi-bin + µð·ºÅ丮¿¡ ÀÌ¿Í ºñ½ÁÇÑ ÇÁ·Î±×·¥ÀÌ µÎ°³ ÀÖ´Ù. ¸î¸î º¯¼ö´Â + ÇʼöÀÌ°í ³ª¸ÓÁö´Â ¼±ÅÃÀûÀÌ´Ù. ±×·¡¼­ °ø½Ä ¸ñ·Ï¿¡ ¾ø´Â + º¯¼öµµ º¸ÀδÙ. ¶Ç, ¾ÆÆÄÄ¡´Â ±âº»ÀûÀ¸·Î Á¦°øÇϴ ȯ°æº¯¼ö + ¿Ü¿¡ ¿©·¯°¡Áö ¹æ¹ýÀ¸·Î Á÷Á¢ ȯ°æº¯¼ö¸¦ + Ãß°¡ÇÒ ¼ö ÀÖ´Ù.

+ +

+ #!/usr/bin/perl
+ print "Content-type: text/html\n\n";
+ foreach $key (keys %ENV) {
+ + print "$key --> $ENV{$key}<br>";
+ + } +

+ + +

STDIN°ú STDOUT

+ + +

¶Ç, ¼­¹ö¿Í Ŭ¶óÀ̾ðÆ®´Â Ç¥ÁØÀÔ·Â(STDIN)°ú + Ç¥ÁØÃâ·Â(STDOUT)À¸·Î Åë½ÅÇÑ´Ù. ÀÏ»óÀûÀÎ °æ¿ì + STDINÀº Å°º¸µå³ª ÇÁ·Î±×·¥ÀÌ Ã³¸®ÇÏ´Â ÆÄÀÏÀ» + ³ªÅ¸³»°í, STDOUTÀº º¸Åë ÄܼÖÀ̳ª È­¸éÀ» ¶æÇÑ´Ù.

+ +

CGI ÇÁ·Î±×·¥¿¡°Ô À¥ ¾ç½Ä(form)À» POSTÇϸé + ¾ç½Ä¿¡ ÀÔ·ÂÇÑ ÀڷḦ Ưº°ÇÑ Çü½ÄÀ¸·Î ¹­¾î¼­ CGI ÇÁ·Î±×·¥ÀÇ + STDINÀ¸·Î Àü´ÞÇÑ´Ù. ±×·¯¸é ÇÁ·Î±×·¥Àº Å°º¸µå³ª + ÆÄÀÏ¿¡¼­ ¾òÀº ÀڷḦ ó¸®ÇϵíÀÌ ÀڷḦ ó¸®ÇÒ ¼ö ÀÖ´Ù.

+ +

"Ưº°ÇÑ Çü½Ä"Àº ¸Å¿ì °£´ÜÇÏ´Ù. Ç׸ñ À̸§°ú °ªÀ» µîÈ£(=)·Î + ¿¬°áÇÏ°í, Ç׸ñ À̸§°ú °ªÀÇ ½ÖµéÀ» ¼­·Î ¾ØÆÛ»÷µå(&)·Î + ¿¬°áÇÑ´Ù. °ø¹é, ¾ÚÆÛ»÷µå, µîÈ£ °°Àº ºÎÀÚ¿¬½º·¯¿î ¹®ÀÚ´Â + È¥µ¿ÇÏÁö ¾Êµµ·Ï 16Áø¼ö·Î º¯È¯ÇÑ´Ù. ¿ÏÀüÇÑ ÀÚ·á ¹®ÀÚ¿­Àº + ´ÙÀ½°ú °°ÀÌ »ý°å´Ù.

+ +

+ name=Rich%20Bowen&city=Lexington&state=KY&sidekick=Squirrel%20Monkey +

+ +

Á¾Á¾ URL µÚ¿¡¼­ ÀÌ·± ¹®ÀÚ¿­À» º¸°Ô µÈ´Ù. ÀÌ °æ¿ì ¼­¹ö´Â + ¹®ÀÚ¿­À» QUERY_STRINGÀ̶ó´Â ȯ°æº¯¼ö¿¡ ÀúÀåÇÑ´Ù. + À̸¦ GET ¿äûÀ̶ó°í ÇÑ´Ù. FORM + ű×ÀÇ METHOD ¼Ó¼ºÀ» ÁöÁ¤ÇÏ¿© HTML ¾ç½Ä(form)ÀÌ + ÀڷḦ GETÇÒÁö POSTÇÒÁö °áÁ¤ÇÑ´Ù.

+ +

ÀÌÁ¦ ÇÁ·Î±×·¥Àº ÀÌ·± ¹®ÀÚ¿­À» À¯¿ëÇÑ Á¤º¸·Î ÂÉ°³¾ß + ÇÑ´Ù. ´ÙÇàÈ÷µµ ÀÌ·± ÀÚ·á 󸮸¦ µ½°í CGI ÇÁ·Î±×·¥ÀÇ ´Ù¸¥ + ¿©·¯ ¸éÀ» »ìÇÇ´Â ¶óÀ̺귯¸®¿Í ¸ðµâµéÀÌ ÀÖ´Ù.

+ +
top
+
+

CGI ¸ðµâ/¶óÀ̺귯¸®

+ + +

CGI ÇÁ·Î±×·¥À» ÀÛ¼ºÇÒ¶§ Áö·çÇÑ ÀÛ¾÷À» ´ë½ÅÇØÁÖ´Â ÄÚµå + ¶óÀ̺귯¸® ȤÀº ¸ðµâÀ» »ç¿ëÇÒÁö °í·ÁÇغÁ¾ß ÇÑ´Ù. ÀÌ·± °ÍÀ» + »ç¿ëÇÏ¸é ¹ö±×°¡ ÁÙ°í ´õ »¡¸® ÇÁ·Î±×·¥À» °³¹ßÇÒ ¼ö ÀÖ´Ù.

+ +

Perl·Î CGI ÇÁ·Î±×·¥À» ÀÛ¼ºÇÑ´Ù¸é CPAN¿¡¼­ °ü·Ã ¸ðµâµéÀ» ãÀ» + ¼ö ÀÖ´Ù. CGI °³¹ß¿¡ °¡Àå ³Î¸® »ç¿ëµÇ´Â ¸ðµâÀº + CGI.pmÀÌ´Ù. ´ëºÎºÐÀÇ ÇÁ·Î±×·¥¿¡ ÃæºÐÇÑ ÃÖ¼Ò + ±â´ÉÀ» ±¸ÇöÇÑ CGI::Liteµµ °í·ÁÇØ º¼ ¼ö ÀÖ´Ù.

+ +

C·Î CGI ÇÁ·Î±×·¥À» ÀÛ¼ºÇÑ´Ù¸é ¼±ÅÃÀÇ ¿©Áö°¡ ¸¹´Ù. ÀÌÁß + Çϳª°¡ http://www.boutell.com/cgic/¿¡ + ÀÖ´Â CGIC ¶óÀ̺귯¸®´Ù.

+
top
+
+

´õ ¸¹Àº Á¤º¸...

+ + +

À¥¿¡ ¸Å¿ì ¸¹Àº CGI Á¤º¸°¡ ÀÖ´Ù. ´º½º±×·ì comp.infosystems.www.authoring.cgi¿¡¼­ ¿©·¯ »ç¶÷µé°ú + CGI ¹®Á¦¸¦ ³íÀÇÇÒ ¼ö ÀÖ´Ù. HTML Writers GuildÀÇ -servers + ¸ÞÀϸµ¸®½ºÆ®´Â Áú¹®¿¡ ´ëÇÑ ´äÀ» ã±â¿¡ ÈǸ¢ÇÑ Àå¼Ò´Ù. http://www.hwg.org/lists/hwg-servers/¿¡¼­ ´õ ¸¹Àº °ÍÀ» + ¾Ë ¼ö ÀÖ´Ù.

+ +

±×¸®°í ¹°·Ð CGI ÇÁ·Î±×·¥ µ¿ÀÛ¿¡ ´ëÇÑ ¸ðµç ³»¿ëÀ» ¼³¸íÇÑ + CGI ±Ô¾àÀ» Àоî¾ß ÇÒÁöµµ ¸ð¸¥´Ù. NCSA¿¡ + ¿øº» ¹®¼­°¡ ÀÖ°í, ¼öÁ¤ÇÑ ÃʾÈÀº Common Gateway Interface + RFC ÇÁ·ÎÁ§Æ®¿¡ ÀÖ´Ù.

+ +

¸ÞÀϸµ¸®½ºÆ®³ª ´º½º±×·ì¿¡ ÇöÀç °Ý°í ÀÖ´Â CGI ¹®Á¦¿¡ ´ëÇØ + Áú¹®ÇÒ¶§´Â ¹ß»ýÇÑ Çö»ó°ú ¿ø·¡ ±â´ëÇÑ °á°ú, ½ÇÁ¦·Î ¹ß»ýÇÑ + Çö»óÀÌ ¾î¶»°Ô ´Ù¸¥Áö, »ç¿ëÇÏ´Â ¼­¹ö, CGI ÇÁ·Î±×·¥À» ÀÛ¼ºÇÑ + ¾ð¾î, °¡´ÉÇϸé ÇØ´ç Äڵ带 ÀÚ¼¼È÷ Àû¾î¶ó. ±×·¯¸é ÇØ°áÃ¥À» + ã±â ½¬¿öÁø´Ù.

+ +

¾ÆÆÄÄ¡ ¼Ò½ºÄڵ尡 À߸øµÇ¾ú´Ù°í È®½ÅÇÏÁö ¾Ê´Â ÇÑ CGI Áú¹®À» + ¾ÆÆÄÄ¡ ¹ö±× µ¥ÀÌÅͺ£À̽º¿¡ ¿Ã¸®¸é Àý´ë·Î + ¾ÈµÈ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/howto/htaccess.html b/docs/manual/howto/htaccess.html new file mode 100644 index 00000000..9c6579d8 --- /dev/null +++ b/docs/manual/howto/htaccess.html @@ -0,0 +1,15 @@ +URI: htaccess.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: htaccess.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: htaccess.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: htaccess.html.pt-br +Content-Language: pt-br +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/howto/htaccess.html.en b/docs/manual/howto/htaccess.html.en new file mode 100644 index 00000000..0ab4f5e9 --- /dev/null +++ b/docs/manual/howto/htaccess.html.en @@ -0,0 +1,385 @@ + + + +Apache Tutorial: .htaccess files - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

Apache Tutorial: .htaccess files

+
+

Available Languages:  en  | + ja  | + ko  | + pt-br 

+
+ +

.htaccess files provide a way to make configuration +changes on a per-directory basis.

+
+ +
top
+
+

.htaccess files

+
Related ModulesRelated Directives
+
top
+
+

What they are/How to use them

+ + +

.htaccess files (or "distributed configuration files") + provide a way to make configuration changes on a per-directory basis. A + file, containing one or more configuration directives, is placed in a + particular document directory, and the directives apply to that + directory, and all subdirectories thereof.

+ +

Note:

+

If you want to call your .htaccess file something + else, you can change the name of the file using the AccessFileName directive. For example, + if you would rather call the file .config then you + can put the following in your server configuration file:

+ +

+ AccessFileName .config +

+
+ +

In general, .htaccess files use the same syntax as + the main configuration + files. What you can put in these files is determined by the + AllowOverride directive. This + directive specifies, in categories, what directives will be + honored if they are found in a .htaccess file. If a + directive is permitted in a .htaccess file, the + documentation for that directive will contain an Override section, + specifying what value must be in AllowOverride in order for that + directive to be permitted.

+ +

For example, if you look at the documentation for the AddDefaultCharset + directive, you will find that it is permitted in .htaccess + files. (See the Context line in the directive summary.) The Override line reads + FileInfo. Thus, you must have at least + AllowOverride FileInfo in order for this directive to be + honored in .htaccess files.

+ +

Example:

+ + + + + + + + + +
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
+ +

If you are unsure whether a particular directive is permitted in a + .htaccess file, look at the documentation for that + directive, and check the Context line for ".htaccess".

+
top
+
+

When (not) to use .htaccess files

+ +

In general, you should never use .htaccess files unless + you don't have access to the main server configuration file. There is, + for example, a prevailing misconception that user authentication should + always be done in .htaccess files. This is simply not the + case. You can put user authentication configurations in the main server + configuration, and this is, in fact, the preferred way to do + things.

+ +

.htaccess files should be used in a case where the + content providers need to make configuration changes to the server on a + per-directory basis, but do not have root access on the server system. + In the event that the server administrator is not willing to make + frequent configuration changes, it might be desirable to permit + individual users to make these changes in .htaccess files + for themselves. This is particularly true, for example, in cases where + ISPs are hosting multiple user sites on a single machine, and want + their users to be able to alter their configuration.

+ +

However, in general, use of .htaccess files should be + avoided when possible. Any configuration that you would consider + putting in a .htaccess file, can just as effectively be + made in a <Directory> section in your main server + configuration file.

+ +

There are two main reasons to avoid the use of + .htaccess files.

+ +

The first of these is performance. When AllowOverride + is set to allow the use of .htaccess files, Apache will + look in every directory for .htaccess files. Thus, + permitting .htaccess files causes a performance hit, + whether or not you actually even use them! Also, the + .htaccess file is loaded every time a document is + requested.

+ +

Further note that Apache must look for .htaccess files + in all higher-level directories, in order to have a full complement of + directives that it must apply. (See section on how + directives are applied.) Thus, if a file is requested out of a + directory /www/htdocs/example, Apache must look for the + following files:

+ +

+ /.htaccess
+ /www/.htaccess
+ /www/htdocs/.htaccess
+ /www/htdocs/example/.htaccess +

+ +

And so, for each file access out of that directory, there are 4 + additional file-system accesses, even if none of those files are + present. (Note that this would only be the case if + .htaccess files were enabled for /, which + is not usually the case.)

+ +

The second consideration is one of security. You are permitting + users to modify server configuration, which may result in changes over + which you have no control. Carefully consider whether you want to give + your users this privilege. Note also that giving users less + privileges than they need will lead to additional technical support + requests. Make sure you clearly tell your users what level of + privileges you have given them. Specifying exactly what you have set + AllowOverride to, and pointing them + to the relevant documentation, will save yourself a lot of confusion + later.

+ +

Note that it is completely equivalent to put a .htaccess + file in a directory /www/htdocs/example containing a + directive, and to put that same directive in a Directory section + <Directory /www/htdocs/example> in your main server + configuration:

+ +

.htaccess file in /www/htdocs/example:

+ +

Contents of .htaccess file in + /www/htdocs/example

+ AddType text/example .exm +

+ +

Section from your httpd.conf + file

+ <Directory /www/htdocs/example>
+ + AddType text/example .exm
+ + </Directory> +

+ +

However, putting this configuration in your server configuration + file will result in less of a performance hit, as the configuration is + loaded once when Apache starts, rather than every time a file is + requested.

+ +

The use of .htaccess files can be disabled completely + by setting the AllowOverride + directive to none:

+ +

+ AllowOverride None +

+
top
+
+

How directives are applied

+ +

The configuration directives found in a .htaccess file + are applied to the directory in which the .htaccess file + is found, and to all subdirectories thereof. However, it is important + to also remember that there may have been .htaccess files + in directories higher up. Directives are applied in the order that they + are found. Therefore, a .htaccess file in a particular + directory may override directives found in .htaccess files + found higher up in the directory tree. And those, in turn, may have + overridden directives found yet higher up, or in the main server + configuration file itself.

+ +

Example:

+ +

In the directory /www/htdocs/example1 we have a + .htaccess file containing the following:

+ +

+ Options +ExecCGI +

+ +

(Note: you must have "AllowOverride Options" in effect + to permit the use of the "Options" directive in + .htaccess files.)

+ +

In the directory /www/htdocs/example1/example2 we have + a .htaccess file containing:

+ +

+ Options Includes +

+ +

Because of this second .htaccess file, in the directory + /www/htdocs/example1/example2, CGI execution is not + permitted, as only Options Includes is in effect, which + completely overrides any earlier setting that may have been in + place.

+ +

Merging of .htaccess with the main + configuration files

+ +

As discussed in the documentation on Configuration Sections, + .htaccess files can override the <Directory> sections for + the corresponding directory, but will be overriden by other types + of configuration sections from the main configuration files. This + fact can be used to enforce certain configurations, even in the + presence of a liberal AllowOverride setting. For example, to + prevent script execution while allowing anything else to be set in + .htaccess you can use:

+ +

+<Directory />
+ +Allowoverride All
+ +</Directory>
+
+<Location />
+ +Options +IncludesNoExec -ExecCGI
+ +</Location> +

+ + +
top
+
+

Authentication example

+ +

If you jumped directly to this part of the document to find out how + to do authentication, it is important to note one thing. There is a + common misconception that you are required to use + .htaccess files in order to implement password + authentication. This is not the case. Putting authentication directives + in a <Directory> + section, in your main server configuration file, is the preferred way + to implement this, and .htaccess files should be used only + if you don't have access to the main server configuration file. See above for a discussion of when you should and should + not use .htaccess files.

+ +

Having said that, if you still think you need to use a + .htaccess file, you may find that a configuration such as + what follows may work for you.

+ +

.htaccess file contents:

+ +

+ AuthType Basic
+ AuthName "Password Required"
+ AuthUserFile /www/passwords/password.file
+ AuthGroupFile /www/passwords/group.file
+ Require Group admins +

+ +

Note that AllowOverride AuthConfig must be in effect + for these directives to have any effect.

+ +

Please see the authentication tutorial for a + more complete discussion of authentication and authorization.

+
top
+
+

Server Side Includes example

+ +

Another common use of .htaccess files is to enable + Server Side Includes for a particular directory. This may be done with + the following configuration directives, placed in a + .htaccess file in the desired directory:

+ +

+ Options +Includes
+ AddType text/html shtml
+ AddHandler server-parsed shtml +

+ +

Note that AllowOverride Options and AllowOverride + FileInfo must both be in effect for these directives to have any + effect.

+ +

Please see the SSI tutorial for a more + complete discussion of server-side includes.

+
top
+
+

CGI example

+ +

Finally, you may wish to use a .htaccess file to permit + the execution of CGI programs in a particular directory. This may be + implemented with the following configuration:

+ +

+ Options +ExecCGI
+ AddHandler cgi-script cgi pl +

+ +

Alternately, if you wish to have all files in the given directory be + considered to be CGI programs, this may be done with the following + configuration:

+ +

+ Options +ExecCGI
+ SetHandler cgi-script +

+ +

Note that AllowOverride Options and AllowOverride + FileInfo must both be in effect for these directives to have any + effect.

+ +

Please see the CGI tutorial for a more + complete discussion of CGI programming and configuration.

+ +
top
+
+

Troubleshooting

+ +

When you put configuration directives in a .htaccess + file, and you don't get the desired effect, there are a number of + things that may be going wrong.

+ +

Most commonly, the problem is that AllowOverride is not + set such that your configuration directives are being honored. Make + sure that you don't have a AllowOverride None in effect + for the file scope in question. A good test for this is to put garbage + in your .htaccess file and reload. If a server error is + not generated, then you almost certainly have AllowOverride + None in effect.

+ +

If, on the other hand, you are getting server errors when trying to + access documents, check your Apache error log. It will likely tell you + that the directive used in your .htaccess file is not + permitted. Alternately, it may tell you that you had a syntax error, + which you will then need to fix.

+ +
+
+

Available Languages:  en  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/htaccess.html.ja.euc-jp b/docs/manual/howto/htaccess.html.ja.euc-jp new file mode 100644 index 00000000..5a93ad8d --- /dev/null +++ b/docs/manual/howto/htaccess.html.ja.euc-jp @@ -0,0 +1,383 @@ + + + +Apache ¥Á¥å¡¼¥È¥ê¥¢¥ë: .htaccess ¥Õ¥¡¥¤¥ë - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë

Apache ¥Á¥å¡¼¥È¥ê¥¢¥ë: .htaccess ¥Õ¥¡¥¤¥ë

+
+

Available Languages:  en  | + ja  | + ko  | + pt-br 

+
+ +

.htaccess ¥Õ¥¡¥¤¥ë¤Ï¥Ç¥£¥ì¥¯¥È¥êËè¤ËÀßÄê¤òÊѹ¹¤¹¤ëÊýË¡¤ò +Ä󶡤·¤Þ¤¹¡£

+
+ +
top
+
+

.htaccess ¥Õ¥¡¥¤¥ë

+
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+
top
+
+

.htaccess ¥Õ¥¡¥¤¥ë¤È¤Ï²¿¤«/¤½¤Î»È¤¤Êý

+ + +

.htaccess ¥Õ¥¡¥¤¥ë (¡Öʬ»¶ÀßÄê¥Õ¥¡¥¤¥ë¡×) ¤Ï + ¥Ç¥£¥ì¥¯¥È¥êËè¤ËÀßÄê¤òÊѹ¹¤¹¤ëÊýË¡¤òÄ󶡤·¤Þ¤¹¡£¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ½ñ¤«¤ì¤¿¥Õ¥¡¥¤¥ë¤ò¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤¯¤³¤È¤Ç¡¢¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤È¤½¤Î + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤¹¤Ù¤Æ¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òŬÍѤµ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Ãí:

+

.htaccess ¥Õ¥¡¥¤¥ë¤òÊ̤Î̾Á°¤Ë¤·¤¿¤¤¾ì¹ç¤Ï¡¢ + AccessFileName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤Ã¤ÆÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¡¢¤½¤Î¥Õ¥¡¥¤¥ë¤ò .config + ¤È¤¤¤¦Ì¾Á°¤Ë¤·¤¿¤¤¾ì¹ç¤Ï¡¢°Ê²¼¤ÎÀßÄê¤ò¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤ËÆþ¤ì¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹:

+ +

+ AccessFileName .config +

+
+ +

°ìÈ̤ˡ¢.htaccess ¥Õ¥¡¥¤¥ë¤Î¹½Ê¸¤Ï + ¼çÀßÄê¥Õ¥¡¥¤¥ë + ¤ÈƱ¤¸¤Ç¤¹¡£¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ë½ñ¤¯¤³¤È¤Î¤Ç¤­¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï AllowOverride ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê·è¤Þ¤ê¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢.htaccess ¥Õ¥¡¥¤¥ë¤Ë + ½ñ¤«¤ì¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃæ¤Ç¡¢¡¢ + ¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Å¬ÍѤµ¤ì¤ë¤«¤ò¥«¥Æ¥´¥ê¡¼Ã±°Ì¤Ç»ØÄꤷ¤Þ¤¹¡£ + .htaccess ¤Ë½ñ¤¯¤³¤È¤Î¤Ç¤­¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤¢¤ì¤Ð¡¢ + ÀâÌÀʸ½ñ¤Ë¤Ï¡Ö¾å½ñ¤­¡×¤È¤¤¤¦¹àÌܤ¬¤¢¤ê¡¢.htaccess ¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë + ¤Ê¤ë¤¿¤á¤Î AllowOverride ¤ÎÃͤ¬»ØÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢AddDefaultCharset ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀâÌÀ¤ò + ¸«¤ë¤È¡¢.htaccess ¥Õ¥¡¥¤¥ë¤Ç¤Î»ÈÍѤ¬µö²Ä¤µ¤ì¤Æ¤¤¤ë¤³¤È¤¬ + ¤ï¤«¤ê¤Þ¤¹¡£ (¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î³µÍפνê¤Ë¤¢¤ë¡Ö¥³¥ó¥Æ¥­¥¹¥È¡×¤È½ñ¤«¤ì¤Æ¤¤¤ë + ¹Ô¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£) ¾å½ñ¤­¤È½ñ¤«¤ì¤Æ¤¤¤ë¹Ô¤Ë¤Ï + FileInfo ¤È¤¢¤ê¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢.htaccess Ãæ¤Î + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Í­¸ú¤Ë¤Ê¤ë¤¿¤á¤Ë¤Ï¡¢¾¯¤Ê¤¯¤È¤â + AllowOverride FileInfo ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

Îã:

+ + + + + + + + + +
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë,¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È,¥Ç¥£¥ì¥¯¥È¥ê,.htaccess
¾å½ñ¤­:FileInfo
+ +

¤¢¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò .htaccess ¥Õ¥¡¥¤¥ë¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¤ë¤« + ¤É¤¦¤«¤ï¤«¤é¤Ê¤¤¤È¤­¤Ï¡¢¤½¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀâÌÀ¤òõ¤·¤Æ¡¢".htaccess" + ¤Î¤¿¤á¤Î¡Ö¥³¥ó¥Æ¥­¥¹¥È¡×¤Î¹Ô¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

¤¤¤Ä .htaccess ¥Õ¥¡¥¤¥ë¤ò»È¤¦(»È¤ï¤Ê¤¤)¤«¡£

+ +

°ìÈÌŪ¤Ë¡¢¥µ¡¼¥Ð¤Î¼çÀßÄê¥Õ¥¡¥¤¥ë¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤Ê¤¤¾ì¹ç¤ò½ü¤¤¤Æ¡¢ + .htaccess ¥Õ¥¡¥¤¥ë¤Î»ÈÍѤ϶ËÎÏÈò¤±¤Æ¤¯¤À¤µ¤¤¡£ + À¤¤ÎÃæ¤Ë¤Ï¡¢Î㤨¤Ð¡¢¥æ¡¼¥¶Ç§¾Ú¤Ï¾ï¤Ë .htaccess ¥Õ¥¡¥¤¥ë¤Ç + ¹Ô¤Ê¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡¢¤È¤¤¤¦¸í²ò¤¬¹­¤Þ¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢¤Þ¤Ã¤¿¤¯¤½¤ó¤Ê¤³¤È¤Ï + ¤¢¤ê¤Þ¤»¤ó¡£¥æ¡¼¥¶Ç§¾Ú¤ÎÀßÄê¤Ï¥µ¡¼¥Ð¼çÀßÄê¥Õ¥¡¥¤¥ë¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¡¢ + ¼ÂºÝ¡¢¤½¤ÎÊý¤¬¤è¤êÎɤ¤ÀßÄêÊýË¡¤Ç¤¹¡£

+ +

.htaccess ¥Õ¥¡¥¤¥ë¤Ï¥³¥ó¥Æ¥ó¥ÄÄ󶡼Ԥ¬¥Ç¥£¥ì¥¯¥È¥êËè¤Î + ÀßÄê¤ò¹Ô¤Ê¤¤¤¿¤¤¤±¤ì¤É¡¢¥µ¡¼¥Ð¥·¥¹¥Æ¥à¤Î root ¥¢¥¯¥»¥¹¸¢¸Â¤ò»ý¤Ã¤Æ¤¤¤Ê¤¤ + ¤È¤¤¤¦¾ì¹ç¤Ë¤Î¤ß»È¤¦¤Ù¤­¤â¤Î¤Ç¤¹¡£¥µ¡¼¥Ð´ÉÍý¼Ô¤¬ÉÑÈˤËÀßÄêÊѹ¹¤ò¹Ô¤Ê¤¤¤¿¤¯¤Ï + ¤Ê¤¤¡¢¤È¤¤¤¦¤È¤­¤Ë¤Ï¸Ä¡¹¤Î¥æ¡¼¥¶¤¬ .htaccess ¥Õ¥¡¥¤¥ë¤ò»È¤Ã¤Æ + ¼«Ê¬¤ÇÀßÄê¤ÎÊѹ¹¤ò¹Ô¤Ê¤¦¤³¤È¤òµö²Ä¤·¤¿Êý¤¬Îɤ¤¤È¤­¤â¤¢¤ë¤Ç¤·¤ç¤¦¡£ + ¤³¤ì¤ÏÆäˡ¢ISP ¤¬Ê£¿ô¤Î¥æ¡¼¥¶¤Î¥µ¥¤¥È¤ò°ì¤Ä¤Î¥Þ¥·¥ó¤Ç¥Û¥¹¥È¤·¤Æ¤¤¤Æ¡¢ + ³Æ¥æ¡¼¥¶¤¬ÀßÄê¤ÎÊѹ¹¤ò¤Ç¤­¤ë¤è¤¦¤Ë¤·¤¿¤¤¤è¤¦¤Ê¤È¤­¤Ë¤¢¤Æ¤Ï¤Þ¤ê¤Þ¤¹¡£

+ +

¤·¤«¤·¡¢ÉáÄ̤ϲÄǽ¤Ç¤¢¤ì¤Ð .htaccess ¥Õ¥¡¥¤¥ë¤Î»ÈÍÑ¤Ï + Èò¤±¤Æ¤¯¤À¤µ¤¤¡£.htaccess ¥Õ¥¡¥¤¥ë¤Ë½ñ¤³¤¦¤È¹Í¤¨¤ë¤è¤¦¤Ê + ¤¹¤Ù¤Æ¤ÎÀßÄê¤Ï¡¢¥µ¡¼¥Ð¤Î¼çÀßÄê¥Õ¥¡¥¤¥ë¤Î <Directory> ¥»¥¯¥·¥ç¥ó¤ÇƱ¤¸¤è¤¦¤Ë¹Ô¤Ê¤¦¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+ +

.htaccess ¥Õ¥¡¥¤¥ë¤Î»ÈÍѤòÈò¤±¤ëÍýͳ¤Ï¼ç¤ËÆó¤Ä¤¢¤ê¤Þ¤¹¡£

+ +

°ì¤ÄÌܤϥµ¡¼¥Ð¤ÎÀ­Ç½¤ÎÌäÂê¤Ç¤¹¡£AllowOverride ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + .htaccess ¥Õ¥¡¥¤¥ë¤ÎÀßÄê¤òµö²Ä¤·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢Apache ¤Ï + ³Æ¥Ç¥£¥ì¥¯¥È¥ê¤Ç .htaccess ¥Õ¥¡¥¤¥ë¤òõ¤·¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢.htaccess ¥Õ¥¡¥¤¥ë¤òµö²Ä¤¹¤ë¤È¡¢¼ÂºÝ¤Ë»ÈÍѤ·¤Æ¤¤¤ë¤« + ¤É¤¦¤«¤Ë´Ø¤ï¤é¤º¡¢À­Ç½¤ÎÄã²¼¤ò¾·¤¯¤³¤È¤Ë¤Ê¤ê¤Þ¤¹! ¤Þ¤¿¡¢.htaccess + ¥Õ¥¡¥¤¥ë¤Ïʸ½ñ¤¬¥ê¥¯¥¨¥¹¥È¤µ¤ì¤ëÅÙ¤ËÆɤ߹þ¤Þ¤ì¤Þ¤¹¡£

+ +

¤µ¤é¤Ë¡¢Apache ¤ÏŬÍѤ¹¤Ù¤­¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½¸¤á¤ë¤¿¤á¤Ë¡¢¤¹¤Ù¤Æ¤Î + ¾å°Ì¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î .htaccess ¥Õ¥¡¥¤¥ë¤òõ¤¹É¬Íפ¬¤¢¤ë¤³¤È¤Ë¤â + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£(¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Å¬ÍѤµ¤ì¤ëÊýË¡¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£)¤Ç¤¹¤«¤é¡¢/www/htdocs/example ¤Ë¤¢¤ë + ¥Õ¥¡¥¤¥ë¤¬¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¤È¤­¤Ï¡¢Apache ¤Ï°Ê²¼¤Î¥Õ¥¡¥¤¥ë¤òÄ´¤Ù¤Þ¤¹¡£

+ +

+ /.htaccess
+ /www/.htaccess
+ /www/htdocs/.htaccess
+ /www/htdocs/example/.htaccess +

+ +

¤Ç¤¹¤«¤é¡¢¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î¤½¤ì¤¾¤ì¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î¥¢¥¯¥»¥¹¤ËÂФ·¤Æ¡¢ + ¾å¤ÎÎã¤Î¥Õ¥¡¥¤¥ë¤¬¤Þ¤Ã¤¿¤¯Â¸ºß¤·¤Ê¤¤¤È¤­¤Ç¤â¡¢ÄɲäΥե¡¥¤¥ë¥·¥¹¥Æ¥à¤Î + ¥¢¥¯¥»¥¹¤¬¹Ô¤Ê¤ï¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£(¤³¤ì¤Ï¡¢.htaccess ¤¬ + / ¤ËÂФ·¤ÆÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤È¤­¤Î¾ì¹ç¤Ç¡¢ÉáÄ̤Ϥ½¤¦¤Ê¤Ã¤Æ + ¤¤¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£)

+ +

Æó¤ÄÌܤϥ»¥­¥å¥ê¥Æ¥£¤Ç¤¹¡£¥æ¡¼¥¶¤Ë¥µ¡¼¥Ð¤ÎÀßÄê¤òÊѹ¹¤¹¤ë¤³¤È¤ò + µö²Ä¤¹¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¤Î¤Ç¡¢¤¢¤Ê¤¿¼«¿È¤¬´ÉÍý¤Ç¤­¤Ê¤¤Êѹ¹¤ò¤µ¤ì¤ë + ¶²¤ì¤¬¤¢¤ê¤Þ¤¹¡£¥æ¡¼¥¶¤Ë¤³¤ÎÆø¢¤òÍ¿¤¨¤ë¤Î¤¬Îɤ¤¤Î¤«¤É¤¦¤«¡¢½½Ê¬ + ¸¡Æ¤¤·¤Æ¤¯¤À¤µ¤¤¡£¤Þ¤¿¡¢¥æ¡¼¥¶¤ËÍ¿¤¨¤ë¸¢¸Â¤¬É¬Íפʤâ¤Î¤è¤ê¤â¾¯¤Ê¤¹¤®¤ë¤È¡¢ + ;ʬ¤Êµ»½Ñ¥µ¥Ý¡¼¥ÈÊó¹ð¤ò¼õ¤±¼è¤ë¤è¤¦¤Ë¤Ê¤ë²ÄǽÀ­¤¬¹â¤¤¤³¤È¤Ë¤â + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£³Î¼Â¤Ë¡¢¥æ¡¼¥¶¤Ë¤É¤ÎÄøÅ٤θ¢¸Â¤òÍ¿¤¨¤¿¤«ÌÀ³Î¤Ë¹ð¤²¤ë¤è¤¦¤Ë + ¤·¤Æ¤¯¤À¤µ¤¤¡£AllowOverride ¤Ë + ²¿¤òÀßÄꤷ¤¿¤«¤È¤¤¤¦¤³¤È¤È¡¢´ØÏ¢¤¹¤ëʸ½ñ¤ò¼¨¤¹¤³¤È¤Ç¡¢ + ¸å¡¹¤Îº®Íð¤ò¤°¤Ã¤È¸º¤é¤¹¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+ +

¤È¤³¤í¤Ç¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î½ñ¤«¤ì¤¿ .htaccess ¤ò + /www/htdocs/example ¤ËÃÖ¤¯¤³¤È¤È¡¢Æ±¤¸¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ¼ç¥µ¡¼¥ÐÀßÄê¤Î Directory ¥»¥¯¥·¥ç¥ó + <Directory /www/htdocs/example> ¤Ë½ñ¤¯¤³¤È¤Ï + ´°Á´¤ËÅù²Á¤Ç¤¹:

+ +

/www/htdocs/example ¤Î .htaccess ¥Õ¥¡¥¤¥ë:

+ +

/www/htdocs/example ¤Î .htaccess ¥Õ¥¡¥¤¥ë¤Î + ÆâÍÆ

+ AddType text/example .exm +

+ +

httpd.conf ¤Î¥»¥¯¥·¥ç¥ó + file

+ <Directory /www/htdocs/example>
+ + AddType text/example .exm
+ + </Directory> +

+ +

¤·¤«¤·¡¢¤³¤ÎÀßÄê¤Ï¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤Ë½ñ¤¤¤¿Êý¤¬¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤Î + Äã²¼¤¬¾¯¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£¥Õ¥¡¥¤¥ë¤¬¥ê¥¯¥¨¥¹¥È¤µ¤ì¤ëÅÙ¤Ë + Æɤ߹þ¤Þ¤ì¤ëÂå¤ï¤ê¤Ë¡¢Apache ¤Îµ¯Æ°»þ¤Ë 1 ²ó¤À¤±Æɤ߹þ¤á¤Ð + ¤è¤¯¤Ê¤ë¤«¤é¤Ç¤¹¡£

+ +

AllowOverride ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + Ãͤò none ¤ËÀßÄꤹ¤ë¤³¤È¤Ç .htaccess ¥Õ¥¡¥¤¥ë + ¤Î»ÈÍѤò´°Á´¤Ë̵¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ AllowOverride None +

+
top
+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎŬÍѤΤµ¤ìÊý

+ +

.htaccess ¥Õ¥¡¥¤¥ë¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï .htaccess + ¥Õ¥¡¥¤¥ë¤Î¸ºß¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤È¡¢¤½¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤¹¤Ù¤Æ¤ËŬÍѤµ¤ì¤Þ¤¹¡£ + ¤·¤«¤·¡¢¾å¤Î³¬ÁؤΥǥ£¥ì¥¯¥È¥ê¤Ë¤â .htaccess ¥Õ¥¡¥¤¥ë¤¬ + ¸ºß¤¹¤ë¤«¤â¤·¤ì¤Ê¤¤¤³¤È¤ò³Ð¤¨¤Æ¤ª¤¯¤³¤È¤ÏÂçÀڤǤ¹¡£¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¸½¤ì¤ë + ½çÈÖ¤ËŬÍѤµ¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Î .htaccess ¤Ï + ¥Ç¥£¥ì¥¯¥È¥ê¥Ä¥ê¡¼¤Î¤è¤ê¾å¤Î³¬ÁؤΠ.htaccess ¥Õ¥¡¥¤¥ë¤Î + ÀßÄê¤ò¾å½ñ¤­¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¤½¤·¤Æ¡¢¤½¤Î .htaccess ¤â + ¤è¤ê¾å¤Î³¬Áؤǽñ¤«¤ì¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¾å½ñ¤­¤·¤¿¤ê¡¢¼ç¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë + ¤½¤Î¤â¤Î¤ÎÀßÄê¤ò¾å½ñ¤­¤·¤¿¤ê¤·¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ +

Îã:

+ +

¥Ç¥£¥ì¥¯¥È¥ê /www/htdocs/example1 ¤Ë°Ê²¼¤ÎÆâÍƤΠ+ .htaccess ¥Õ¥¡¥¤¥ë¤¬¤¢¤ê¤Þ¤¹:

+ +

+ Options +ExecCGI +

+ +

(Ãí: .htaccess + ¥Õ¥¡¥¤¥ë¤Ç "Options" ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Í­¸ú¤Ë¤Ê¤ë¤¿¤á¤Ë¤Ï¡¢ + "AllowOverride Options" ¤òÍ­¸ú¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£)

+ +

¥Ç¥£¥ì¥¯¥È¥ê /www/htdocs/example1/example2 ¤Ë¤Ï + °Ê²¼¤Î¤è¤¦¤Ê .htaccess ¥Õ¥¡¥¤¥ë¤¬¤¢¤ê¤Þ¤¹:

+ +

+ Options Includes +

+ +

Æó¤Ä¤á¤Î .htaccess ¤Ë¤è¤ê¡¢¥Ç¥£¥ì¥¯¥È¥ê + /www/htdocs/example1/example2 ¤Ç¤Ï CGI ¤Î¼Â¹Ô¤Ï + µö²Ä¤µ¤ì¤Þ¤»¤ó¡£¤³¤ì¤Ï¡¢Options Includes ¤Î¤ß¤¬ + ¸úÎϤò»ý¤Á¡¢¤½¤ì¤¬¤¹¤Ù¤Æ¤Î°ÊÁ°¤ÎÀßÄê¤ò¾å½ñ¤­¤¹¤ë¤«¤é¤Ç¤¹¡£

+ +

¥á¥¤¥óÀßÄê¥Õ¥¡¥¤¥ë¤ËÂФ¹¤ë + .htaccess ¤Î¥Þ¡¼¥¸

+ +

As discussed in the documentation on Configuration Sections, + .htaccess files can override the <Directory> sections for + the corresponding directory, but will be overriden by other types + of configuration sections from the main configuration files. This + fact can be used to enforce certain configurations, even in the + presence of a liberal AllowOverride setting. For example, to + prevent script execution while allowing anything else to be set in + .htaccess you can use:

+

¥»¥¯¥·¥ç¥ó¤ÎÀßÄê + ¤Ëµ­ºÜ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¡¢.htaccess ¥Õ¥¡¥¤¥ë¤ò»È¤Ã¤Æ + <Directory> + ¥»¥¯¥·¥ç¥ó¤ÎÀßÄê¤ò¥Ç¥£¥ì¥¯¥È¥êËè¤Ë¾å½ñ¤­¤Ç¤­¤Þ¤¹¤¬¡¢ + ¥á¥¤¥óÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Ë¤¢¤ë¡¢Â¾¤Î¼ïÎà¤ÎÀßÄꥻ¥¯¥·¥ç¥ó¤Ë¤è¤Ã¤Æ + ¤µ¤é¤Ë¾å½ñ¤­¤µ¤ì¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£ + ¤³¤ÎÆÃħ¤ò»È¤Ã¤Æ¡¢ + AllowOverride + ¤Ç¼«Í³Å٤ι⤤ÀßÄ꤬¤¢¤Ã¤¿¤È¤·¤Æ¤â¡¢¤¢¤ëÆÃÄê¤ÎÀßÄ꤬³Î¼Â¤Ë + È¿±Ç¤µ¤ì¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¡¢CGI ¥¹¥¯¥ê¥×¥È¤Î¼Â¹Ô¤Ï + ÉÔµö²Ä¤Ë¡¢¤«¤Ä¡¢.htaccess ¤Ç¤½¤Î¾¤Î¹àÌÜ¤Ï + ÀßÄê¤Ç¤­¤ë¤è¤¦¤Ë¡¢¤È¤¤¤¦¾ì¹ç¤Ï¼¡¤Î¤è¤¦¤Ë¤Ç¤­¤Þ¤¹ :

+ +

+<Directory />
+ +Allowoverride All
+ +</Directory>
+
+<Location />
+ +Options +IncludesNoExec -ExecCGI
+ +</Location> +

+ + +
top
+
+

ǧ¾Ú¤ÎÎã

+ +

¤â¤·Ç§¾Ú¤ÎÊýË¡¤òÃΤ뤿¤á¤Ë¤³¤ÎÉôʬ¤ËľÀÜÍ褿¤Î¤Ç¤¢¤ì¤Ð¡¢¼¡¤Î¤³¤È¤ò + ÃΤäƤª¤¯¤³¤È¤¬½ÅÍפǤ¹¡£¤è¤¯¤¢¤ë¸í²ò¤Ë¡¢¥Ñ¥¹¥ï¡¼¥Éǧ¾Ú¤ò¹Ô¤Ê¤¦¤¿¤á¤Ë¤Ï + .htaccess ¥Õ¥¡¥¤¥ë¤ò»È¤¦É¬Íפ¬¤¢¤ë¡¢¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤ÏÀµ¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£¼ç¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤Î <Directory> ¥»¥¯¥·¥ç¥ó¤Ë + ǧ¾ÚÍѤΥǥ£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¯Êý¤¬¿ä¾©¤µ¤ì¤ëÊýË¡¤Ç¡¢.htaccess + ¥Õ¥¡¥¤¥ë¤Ï¼ç¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤òÊѹ¹¤Ç¤­¤Ê¤¤¤È¤­¤Ë¤Î¤ß»ÈÍѤ¹¤Ù¤­¤Ç¤¹¡£ + ¤¤¤Ä .htaccess ¥Õ¥¡¥¤¥ë¤ò»È¤¦¤Ù¤­¤Ç¡¢¤¤¤Ä»È¤¦¤Ù¤­¤Ç¤Ï¤Ê¤¤¤«¤Ë + ¤Ä¤¤¤Æ¤Ï ¾å¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

°Ê¾å¤Î¤³¤È¤ò¤Õ¤Þ¤¨¤¿¾å¤Ç¡¢¤â¤· .htaccess ¤Î»ÈÍѤ¬ + ¤Þ¤ÀɬÍפÀ¤È»×¤¦¾ì¹ç¤Ï¡¢¼¡¤Î¤è¤¦¤Ê¤â¤Î¤¬Ë¾¤ß¤Î¤³¤È¤ò¤·¤Æ¤¯¤ì¤ë¤«¤â + ¤·¤ì¤Þ¤»¤ó¡£

+ +

.htaccess ¥Õ¥¡¥¤¥ë¤ÎÆâÍÆ:

+ +

+ AuthType Basic
+ AuthName "Password Required"
+ AuthUserFile /www/passwords/password.file
+ AuthGroupFile /www/passwords/group.file
+ Require Group admins +

+ +

¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Í­¸ú¤Ë¤Ê¤ë¤¿¤á¤Ë¤Ï¡¢ + AllowOverride AuthConfig ¤¬Í­¸ú¤Ç¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

ǧ¾Ú¤È¾µÇ§¤Ë¤Ä¤¤¤Æ¤Ï ǧ¾Ú¥Á¥å¡¼¥È¥ê¥¢¥ë¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

SSI ¤ÎÎã

+ +

¤â¤¦°ì¤Ä¤Î .htaccess ¥Õ¥¡¥¤¥ë¤Î¤è¤¯¤¢¤ëÍøÍÑË¡¤Ï + ÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ç SSI ¤òÍ­¸ú¤Ë¤¹¤ë¤³¤È¤Ç¤¹¡£¤³¤ì¤Ï¡¢Ë¾¤ß¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î + .htaccess ¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¯¤³¤È¤Ç + ãÀ®¤Ç¤­¤Þ¤¹:

+ +

+ Options +Includes
+ AddType text/html shtml
+ AddHandler server-parsed shtml +

+ +

¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Í­¸ú¤Ë¤Ê¤ë¤¿¤á¤Ë¤Ï¡¢ + AllowOverride Options ¤È AllowOverride + FileInfo ¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

¤è¤ê¤Þ¤È¤Þ¤Ã¤¿ SSI ¤ÎÀâÌÀ¤Ï SSI ¥Á¥å¡¼¥È¥ê¥¢¥ë¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

CGI ¤ÎÎã

+ +

ºÇ¸å¤Ë¡¢ÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ç CGI ¥×¥í¥°¥é¥à¤Î¼Â¹Ô¤òµö²Ä¤·¤¿¤¤¤³¤È¤¬ + ¤¢¤ë¤Ç¤·¤ç¤¦¡£¤³¤ì¤Ï°Ê²¼¤ÎÀßÄê¤Ç¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ Options +ExecCGI
+ AddHandler cgi-script cgi pl +

+ +

¤â¤·¤¯¤Ï¡¢¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Î¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤¬ CGI ¥×¥í¥°¥é¥à¤È + ¤ß¤Ê¤µ¤ì¤ë¤è¤¦¤Ë¤·¤¿¤¤¤Ê¤é¡¢°Ê²¼¤ÎÀßÄê¤Ç¼Â¸½¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ Options +ExecCGI
+ SetHandler cgi-script +

+ +

¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Í­¸ú¤Ë¤Ê¤ë¤¿¤á¤Ë¤Ï¡¢ + AllowOverride Options ¤È AllowOverride + FileInfo ¤¬Í­¸ú¤Ç¤¢¤ëɬÍפ¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

CGI ¥×¥í¥°¥é¥à¤ÈÀßÄê¤Î¤è¤ê¤Þ¤È¤Þ¤Ã¤¿ÀâÌÀ¤Ï CGI ¥Á¥å¡¼¥È¥ê¥¢¥ë¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
top
+
+

ÌäÂê²ò·è

+ +

ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò .htaccess ¥Õ¥¡¥¤¥ë¤Ë½ñ¤¤¤¿¤±¤ì¤É¤â¡¢ + ´üÂÔ¤·¤¿¸ú²Ì¤¬ÆÀ¤é¤ì¤Ê¤¤¤È¤­¤Ë¤Ï¡¢¤¤¤¯¤Ä¤«¤Î¸¶°ø¤¬¹Í¤¨¤é¤ì¤Þ¤¹¡£

+ +

°ìÈ֤褯¤¢¤ë¤³¤È¤Ï¡¢ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¹Í褵¤ì¤ë¤è¤¦¤Ë¤Ï + AllowOverride ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤ + ¤È¤¤¤¦¤â¤Î¤Ç¤¹¡£³ºÅö¤Î¥Õ¥¡¥¤¥ë¤Î¥¹¥³¡¼¥×¤Ë AllowOverride None + ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£¤³¤ì¤òÄ´¤Ù¤ë¤¿¤á¤ÎÎɤ¤ÊýË¡¤Ï¡¢ + .htaccess ¥Õ¥¡¥¤¥ë¤Ë¤´¤ß¤ò½ñ¤¤¤Æ¡¢¥ê¥í¡¼¥É¤¹¤ë¤³¤È¤Ç¤¹¡£ + ¥µ¡¼¥Ð¤Î¥¨¥é¡¼¤¬À¸À®¤µ¤ì¤Ê¤¤¤È¤­¤Ï¡¢¤Û¤Ü³Î¼Â¤Ë AllowOverride + None ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¾õÂ֤ˤʤäƤ¤¤Þ¤¹¡£

+ +

¤½¤¦¤Ç¤Ï¤Ê¤¯¡¢Ê¸½ñ¤ò¥¢¥¯¥»¥¹¤·¤è¤¦¤È¤·¤¿¤È¤­¤Ë¥¨¥é¡¼¤¬È¯À¸¤·¤Æ¤¤¤ë + ¤È¤­¤Ï¡¢Apache ¤Î¥¨¥é¡¼¥í¥°¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£.htaccess ¥Õ¥¡¥¤¥ë¤Ç + »ÈÍѤµ¤ì¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬µö²Ä¤µ¤ì¤Æ¤¤¤Ê¤¤¡¢¤È¤¤¤¦¤³¤È¤òÃΤ餻¤Æ¤¤¤ë + ²ÄǽÀ­¤¬¹â¤¤¤Ç¤¹¡£¤Þ¤¿¤Ï¡¢¹½Ê¸¤Î´Ö°ã¤¤¤¬¤¢¤ë¤³¤È¤ò½Ò¤Ù¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤½¤Î¾ì¹ç¤Ë¤Ï¤Þ¤º¤½¤ì¤ò½¤Àµ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +
+
+

Available Languages:  en  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/htaccess.html.ko.euc-kr b/docs/manual/howto/htaccess.html.ko.euc-kr new file mode 100644 index 00000000..68f4172a --- /dev/null +++ b/docs/manual/howto/htaccess.html.ko.euc-kr @@ -0,0 +1,333 @@ + + + +¾ÆÆÄÄ¡ ÅõÅ丮¾ó: .htaccess ÆÄÀÏ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

¾ÆÆÄÄ¡ ÅõÅ丮¾ó: .htaccess ÆÄÀÏ

+
+

°¡´ÉÇÑ ¾ð¾î:  en  | + ja  | + ko  | + pt-br 

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

.htaccess ÆÄÀÏÀ» »ç¿ëÇÏ¿© µð·ºÅ丮º°·Î ¼³Á¤À» +º¯°æÇÒ ¼ö ÀÖ´Ù.

+
+ +
top
+
+

.htaccess ÆÄÀÏ

+
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+
top
+
+

¹«¾ùÀ̸ç/¾î¶»°Ô »ç¿ëÇϴ°¡

+ + +

.htaccess ÆÄÀÏ(ȤÀº "ºÐ»ê ¼³Á¤ÆÄÀÏ")À» + »ç¿ëÇÏ¸é µð·ºÅ丮º°·Î ¼³Á¤À» º¯°æÇÒ ¼ö ÀÖ´Ù. ¿©·¯ ¼³Á¤ Áö½Ã¾î°¡ + ÀÖ´Â ÆÄÀÏÀ» ƯÁ¤ ¹®¼­ µð·ºÅ丮¿¡ µÎ¸é, ±× µð·ºÅ丮¿Í ¸ðµç + ÇÏÀ§µð·ºÅ丮¿¡ Áö½Ã¾î¸¦ Àû¿ëÇÑ´Ù.

+ +

ÁÖÀÇ:

+

.htaccess ÆÄÀϸíÀ» ´Ù¸£°Ô »ç¿ëÇÏ°í ½Í´Ù¸é, + AccessFileName Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© º¯°æÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, .config + ÆÄÀϸíÀ» »ç¿ëÇÏ·Á¸é ¼­¹ö ¼³Á¤ÆÄÀÏ¿¡ ´ÙÀ½°ú °°ÀÌ Ãß°¡ÇÑ´Ù.

+ +

+ AccessFileName .config +

+
+ +

ÀϹÝÀûÀ¸·Î .htaccess ÆÄÀÏÀº ÁÖ¼³Á¤ÆÄÀÏ°ú ¹®¹ýÀÌ + °°´Ù. AllowOverride + Áö½Ã¾î°¡ ÀÌ ÆÄÀÏ¿¡ ³ª¿Ã ¼ö ÀÖ´Â ³»¿ëÀ» °áÁ¤ÇÑ´Ù. ÀÌ Áö½Ã¾î´Â + .htaccess ÆÄÀÏ¿¡¼­ Çã¿ëÇÏ´Â Áö½Ã¾î ºÐ·ù¸¦ ÁöÁ¤ÇÑ´Ù. + Áö½Ã¾î¸¦ .htaccess ÆÄÀÏ¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖ´Ù¸é, + ÇØ´ç Áö½Ã¾î ¹®¼­ÀÇ Override Ç׸ñÀº Áö½Ã¾î¸¦ Çã¿ëÇϱâÀ§ÇØ + AllowOverride¿¡ »ç¿ëÇÒ + °ªÀ» ¾Ë·ÁÁØ´Ù.

+ +

¿¹¸¦ µé¾î, AddDefaultCharset + Áö½Ã¾î ¹®¼­¸¦ º¸¸é ÀÌ Áö½Ã¾î¸¦ .htaccess ÆÄÀÏ¿¡¼­ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. (Áö½Ã¾î ¿ä¾à¿¡¼­ »ç¿ëÀå¼Ò Ç׸ñÀ» º¸¶ó.) + Override + ÁÙ¿¡ FileInfo°¡ ÀÖ´Ù. ±×·¡¼­ ÀÌ Áö½Ã¾î¸¦ + .htaccess ÆÄÀÏ¿¡¼­ »ç¿ëÇϱâÀ§Çؼ­´Â ÃÖ¼ÒÇÑ + AllowOverride FileInfo°¡ ÇÊ¿äÇÏ´Ù.

+ +

¿¹Á¦:

+ + + + + + + + + +
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override:FileInfo
+ +

ƯÁ¤ Áö½Ã¾î¸¦ .htaccess ÆÄÀÏ¿¡¼­ »ç¿ëÇÒ + ¼ö ÀÖ´ÂÁö ±Ã±ÝÇϸé Áö½Ã¾î ¹®¼­ÀÇ »ç¿ëÀå¼Ò Ç׸ñ¿¡ ".htaccess"°¡ + ÀÖ´ÂÁö È®ÀÎÇÑ´Ù.

+
top
+
+

¾ðÁ¦ .htaccess ÆÄÀÏÀ» »ç¿ëÇϳª + (ȤÀº »ç¿ëÇÏÁö ¾Ê³ª)

+ +

ÀϹÝÀûÀ¸·Î ÁÖ¼­¹öÆÄÀÏ¿¡ Á¢±ÙÇÒ ¼ö ¾ø´Â °æ¿ì°¡ ¾Æ´Ï¶ó¸é + .htaccess ÆÄÀÏÀ» »ç¿ëÇÏ¸é ¾ÈµÈ´Ù. ¿¹¸¦ µé¾î, + »ç¿ëÀÚ ÀÎÁõÀÌ Ç×»ó .htaccess ÆÄÀÏ¿¡ ÀÖ¾î¾ß + ÇÑ´Ù´Â °ÍÀº À߸ø ¾Ë·ÁÁø ¿ÀÇØ´Ù. ÀÌ´Â »ç½ÇÀÌ ¾Æ´Ï´Ù. ÁÖ¼­¹ö¼³Á¤¿¡ + »ç¿ëÀÚ ÀÎÁõ ¼³Á¤À» ÀûÀ» ¼ö ÀÖ°í, »ç½Ç ÀÌ·¯±æ ±ÇÇÑ´Ù.

+ +

.htaccess ÆÄÀÏÀº ÄÁÅÙÃ÷ Á¦°øÀÚ°¡ µð·ºÅ丮º°·Î + ¼­¹ö ¼³Á¤À» ´Ù¸£°ÔÇÏ°í ½ÍÁö¸¸ ¼­¹ö ½Ã½ºÅÛ¿¡ root ±ÇÇÑÀÌ + ¾ø´Â °æ¿ì¿¡ »ç¿ëÇÑ´Ù. ¼­¹ö °ü¸®ÀÚ°¡ ¼³Á¤À» ÀÚÁÖ º¯°æÇÏ°í + ½ÍÁö ¾ÊÀº °æ¿ì ÀÏ¹Ý »ç¿ëÀÚ°¡ Á÷Á¢ .htaccess + ÆÄÀÏÀ» ¼öÁ¤Çϵµ·Ï Çã¿ëÇÏ´Â °ÍÀÌ ¹Ù¶÷Á÷ÇÏ´Ù. ¿¹¸¦ µé¾î, ÇÑ + ÄÄÇ»ÅÍ¿¡ ¿©·¯ »ç¿ëÀÚ »çÀÌÆ®¸¦ ¼­ºñ½ºÇÏ´Â ISP¿¡¼­ »ç¿ëÀÚ°¡ + ÀÚ½ÅÀÇ ¼³Á¤À» º¯°æÇÏ°í ½ÍÀº °æ¿ì°¡ ±×·¯ÇÏ´Ù.

+ +

±×·¯³ª ÀϹÝÀûÀ¸·Î .htaccess ÆÄÀÏÀº °¡±ÞÀû + ÇÇÇØ¾ß ÇÑ´Ù. .htaccess ÆÄÀÏ¿¡¼­ Çã¿ëÇÏ´Â Áö½Ã¾î´Â + ÁÖ¼³Á¤ÆÄÀÏÀÇ <Directory> ¼½¼Ç°ú °°Àº È¿°ú°¡ + ÀÖ´Ù.

+ +

´ÙÀ½ µÎ°¡Áö Å« ÀÌÀ¯¶§¹®¿¡ .htaccess ÆÄÀÏ + »ç¿ëÀ» ÇÇÇØ¾ß ÇÑ´Ù.

+ +

ù¹ø°´Â ¼º´ÉÀÌ´Ù. AllowOverride°¡ .htaccess + ÆÄÀÏÀ» »ç¿ëÇϵµ·Ï Çã¿ëÇϸé, ¾ÆÆÄÄ¡´Â µð·ºÅ丮¸¶´Ù + .htaccess ÆÄÀÏÀ» ã´Â´Ù. ±×·¡¼­ + .htaccess ÆÄÀÏÀ» Çã¿ëÇÏ¸é ½ÇÁ¦·Î ÆÄÀÏÀ» »ç¿ëÇÏÁö + ¾Ê´Â °æ¿ì¿¡µµ ¼º´ÉÀÌ ¶³¾îÁø´Ù! ¶Ç, .htaccess + ÆÄÀÏÀº ¹®¼­¸¦ ¿äûÇÒ¶§¸¶´Ù ÀоîµéÀδÙ.

+ +

°Ô´Ù°¡ Àû¿ëÇØ¾ß ÇÏ´Â Àüü Áö½Ã¾î¸¦ ¸ðÀ¸±âÀ§ÇØ ¾ÆÆÄÄ¡´Â + ¸ðµç »óÀ§ µð·ºÅ丮¿¡¼­ .htaccess ÆÄÀÏÀ» ã´Â´Ù. + (¾î¶»°Ô Áö½Ã¾î¸¦ Àû¿ëÇϳª ÀýÀ» Âü°í.) + ±×·¡¼­ /www/htdocs/example µð·ºÅ丮¿¡ ÀÖ´Â + ÆÄÀÏÀ» ¿äûÇϸé, ¾ÆÆÄÄ¡´Â ´ÙÀ½ ÆÄÀϵéÀ» ã¾Æ¾ß ÇÑ´Ù.

+ +

+ /.htaccess
+ /www/.htaccess
+ /www/htdocs/.htaccess
+ /www/htdocs/example/.htaccess +

+ +

±×·¡¼­ ±× µð·ºÅ丮¿¡ ÀÖ´Â ÆÄÀÏÀ» Á¢±ÙÇÒ ¶§¸¶´Ù ¼³Á¤ÆÄÀÏÀÌ + ÀüÇô ¾ø¾îµµ ÆÄÀϽýºÅÛÀ» 4¹ø ´õ Á¢±ÙÇØ¾ß ÇÑ´Ù. + (/¿¡¼­µµ .htaccess ÆÄÀÏÀ» Çã¿ëÇÑ + °æ¿ì¸¦ ¸»ÇÑ´Ù. º¸ÅëÀº Çã¿ëÇÏÁö ¾Ê´Â´Ù.)

+ +

µÎ¹ø° ÀÌÀ¯´Â º¸¾ÈÀÌ´Ù. »ç¿ëÀÚ¿¡°Ô ¼­¹ö¼³Á¤ º¯°æ ±ÇÇÑÀ» + ÁÖ¸é ´ç½ÅÀÌ °¨´çÇÒ ¼ö ¾ø´Â º¯È­°¡ ÀϾ ¼ö ÀÖ´Ù. »ç¿ëÀÚ¿¡°Ô + ÀÌ·± ±ÇÇÑÀ» ÁÙÁö °õ°õÀÌ »ý°¢Ç϶ó. ¶Ç, »ç¿ëÀÚ°¡ ¿øÇÏ´Â °Íº¸´Ù + ÀûÀº ±ÇÇÑÀ» ÁÖ¸é ±â¼úÁö¿ø¿äûÀÌ µé¾î¿Â´Ù. »ç¿ëÀÚ¿¡°Ô °¡´ÉÇÑ + ±ÇÇÑ ¼öÁØÀ» ¸íÈ®È÷ ¾Ë·Á¶ó. »ç¿ëÀÚ¿¡°Ô AllowOverride¸¦ ¾î¶»°Ô ¼³Á¤ÇÏ¿´´ÂÁö + Á¤È®È÷ ¾Ë¸®°í °ü·Ã ¹®¼­¸¦ Á¦°øÇÏ¸é ¾ÕÀ¸·Î È¥¶õÀ» ÇÇÇÒ ¼ö + ÀÖ´Ù.

+ +

Áö½Ã¾î¸¦ /www/htdocs/example µð·ºÅ丮ÀÇ + .htaccess ÆÄÀÏÀ» µÎ´Â °Í°ú ÁÖ¼­¹ö¼³Á¤ÀÇ + <Directory /www/htdocs/example> Directory + ¼³Á¤¿¡ µÎ´Â °ÍÀº ¿ÏÀüÈ÷ °°´Ù.

+ +

/www/htdocs/example¿¡ ÀÖ´Â + .htaccess ¼½¼Ç:

+ +

/www/htdocs/example¿¡ ÀÖ´Â + .htaccess ÆÄÀÏ ³»¿ë

+ AddType text/example .exm +

+ +

httpd.conf ÆÄÀÏ¿¡ ÀÖ´Â ¼½¼Ç

+ <Directory /www/htdocs/example>
+ + AddType text/example .exm
+ + </Directory> +

+ +

±×·¯³ª ÆÄÀÏÀ» ¿äûÇÒ ¶§¸¶´Ù ¼³Á¤À» ÀÐÁö¾Ê°í ¾ÆÆÄÄ¡°¡ + ½ÃÀÛÇÒ¶§ Çѹø¸¸ ¼³Á¤À» Àб⶧¹®¿¡ °°Àº ¼³Á¤À» ¼­¹ö¼³Á¤ÆÄÀÏ¿¡ + »ç¿ëÇÏ¸é ¼º´ÉÀÌ ´õ ºü¸£´Ù.

+ +

AllowOverride Áö½Ã¾î¸¦ + noneÀ¸·Î ¼³Á¤Çϸé .htaccess ÆÄÀÏÀ» + ¿ÏÀüÈ÷ »ç¿ëÇÒ ¼ö ¾ø´Ù.

+ +

+ AllowOverride None +

+
top
+
+

¾î¶»°Ô Áö½Ã¾î¸¦ Àû¿ëÇϳª

+ +

.htaccess ÆÄÀÏÀ» ¹ß°ßÇÑ µð·ºÅ丮¿Í ±× µð·ºÅ丮ÀÇ + ¸ðµç ÇÏÀ§µð·ºÅ丮¿¡ .htaccess ÆÄÀÏ¿¡ ÀÖ´Â ¼³Á¤ + Áö½Ã¾î¸¦ Àû¿ëÇÑ´Ù. ±×·¡¼­ »óÀ§µð·ºÅ丮ÀÇ .htaccess + ÆÄÀÏÀ» ÁÖÀÇÇØ¾ß ÇÑ´Ù. ¹ß°ßÇÑ ¼ø¼­·Î Áö½Ã¾î¸¦ Àû¿ëÇÑ´Ù. ƯÁ¤ + µð·ºÅ丮¿¡ ÀÖ´Â .htaccess ÆÄÀÏÀº »óÀ§µð·ºÅ丮¿¡ + ÀÖ´Â .htaccess ÆÄÀÏÀÇ Áö½Ã¾î¸¦ ¹«È¿·Î ¸¸µé + ¼ö ÀÖ°í, »óÀ§µð·ºÅ丮¿¡ ÀÖ´Â Áö½Ã¾î´Â ´õ »óÀ§µð·ºÅ丮 ȤÀº + ÁÖ¼³Á¤ÆÄÀÏ¿¡ ÀÖ´Â Áö½Ã¾î¸¦ ¹«È¿·Î ¸¸µé ¼ö ÀÖ´Ù.

+ +

¿¹Á¦:

+ +

/www/htdocs/example1 µð·ºÅ丮¿¡ ´ÙÀ½°ú °°Àº + .htaccess ÆÄÀÏÀÌ ÀÖ´Ù.

+ +

+ Options +ExecCGI +

+ +

(ÁÖÀÇ: .htaccess ÆÄÀÏ¿¡ "Options" Áö½Ã¾î¸¦ »ç¿ëÇÏ·Á¸é + "AllowOverride Options"°¡ ÇÊ¿äÇÏ´Ù.)

+ +

/www/htdocs/example1/example2 µð·ºÅ丮¿¡´Â + ´ÙÀ½°ú °°Àº .htaccess ÆÄÀÏÀÌ ÀÖ´Ù.

+ +

+ Options Includes +

+ +

ÀÌ µÎ¹ø° .htaccess ÆÄÀÏÀÇ + Options Includes°¡ ÀÌÀü ¼³Á¤À» ¿ÏÀüÈ÷ ¹«È¿·Î + ¸¸µé±â¶§¹®¿¡ /www/htdocs/example1/example2 + µð·ºÅ丮´Â CGI ½ÇÇàÀ» Çã¿ëÇÏÁö ¾Ê´Â´Ù.

+
top
+
+

ÀÎÁõ ¿¹Á¦

+ +

ÀÎÁõ ¹æ¹ýÀ» ¾Ë±âÀ§ÇØ ¹Ù·Î ÀÌ°÷ºÎÅÍ Àд´ٸé ÁÖÀÇÇÒ °ÍÀÌ + ÀÖ´Ù. ¾ÏÈ£ ÀÎÁõÀ» ÇÏ·Á¸é .htaccess ÆÄÀÏÀÌ + ÇÊ¿äÇÏ´Ù´Â ¿ÀÇØ°¡ ³Î¸® ÆÛÁ®ÀÖ´Ù. ÀÌ´Â »ç½ÇÀÌ ¾Æ´Ï´Ù. + ÁÖ¼³Á¤ÆÄÀÏÀÇ <Directory> ¼½¼Ç¿¡ ÀÎÁõ Áö½Ã¾î¸¦ + µÎ´Â °ÍÀÌ ´õ ±ÇÀåÇÏ´Â ¹æ¹ýÀÌ°í, ¼­¹öÀÇ ÁÖ¼³Á¤ÆÄÀÏÀ» ¼öÁ¤ÇÒ + ¼ö ¾ø´Â °æ¿ì¿¡¸¸ .htaccess ÆÄÀÏÀ» »ç¿ëÇØ¾ß + ÇÑ´Ù. ¾ðÁ¦ .htaccess ÆÄÀÏÀ» »ç¿ëÇØ¾ß ÇÏ´ÂÁö¿Í + »ç¿ëÇÏÁö ¸»¾Æ¾ß ÇÏ´ÂÁö´Â À§¿¡¼­ + ¼³¸íÇÏ¿´´Ù.

+ +

¾Õ¿¡¼­ ¸»ÇßÁö¸¸ ¾ÆÁ÷µµ .htaccess ÆÄÀÏÀÌ + ÇÊ¿äÇÏ´Ù°í »ý°¢µÇ¸é ¾Æ·¡ ¼³Á¤ÀÌ µµ¿òÀÌ µÉ °ÍÀÌ´Ù.

+ +

.htaccess ÆÄÀÏ ³»¿ë.

+ +

+ AuthType Basic
+ AuthName "Password Required"
+ AuthUserFile /www/passwords/password.file
+ AuthGroupFile /www/passwords/group.file
+ Require Group admins +

+ +

ÀÌ Áö½Ã¾î°¡ µ¿ÀÛÇϱâÀ§Çؼ­´Â + AllowOverride AuthConfig Áö½Ã¾î°¡ ÇÊ¿äÇÔÀ» + ¸í½ÉÇ϶ó.

+ +

ÀÎÁõ°ú ±ÇÇѺο©¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸íÀº ÀÎÁõ + ÅõÅ丮¾óÀ» º¸±æ ¹Ù¶õ´Ù.

+
top
+
+

Server Side Includes ¿¹Á¦

+ +

¶Ç´Ù¸¥ ÀϹÝÀûÀÎ .htaccess ÆÄÀÏÀÇ ¿ëµµ´Â + ƯÁ¤ µð·ºÅ丮¿¡¼­ Server Side Includes¸¦ °¡´ÉÇÏ°Ô ¸¸µå´Â + °ÍÀÌ´Ù. ¿øÇÏ´Â µð·ºÅ丮ÀÇ .htaccess ÆÄÀÏ¿¡ + ´ÙÀ½°ú °°Àº ¼³Á¤ Áö½Ã¾î¸¦ »ç¿ëÇÏ¸é µÈ´Ù.

+ +

+ Options +Includes
+ AddType text/html shtml
+ AddHandler server-parsed shtml +

+ +

ÀÌ Áö½Ã¾î°¡ µ¿ÀÛÇÏ·Á¸é AllowOverride Options¿Í + AllowOverride FileInfo°¡ ¸ðµÎ ÇÊ¿äÇÔÀ» ¸í½ÉÇ϶ó.

+ +

server-side includes¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸íÀº SSI ÅõÅ丮¾óÀ» º¸±æ ¹Ù¶õ´Ù.

+
top
+
+

CGI ¿¹Á¦

+ +

¸¶Áö¸·À¸·Î .htaccess ÆÄÀÏÀ» »ç¿ëÇÏ¿© ƯÁ¤ + µð·ºÅ丮¿¡¼­ CGI ÇÁ·Î±×·¥ ½ÇÇàÀ» Çã¿ëÇÏ°í ½Í´Ù¸é, ´ÙÀ½°ú + °°Àº ¼³Á¤À» »ç¿ëÇÑ´Ù.

+ +

+ Options +ExecCGI
+ AddHandler cgi-script cgi pl +

+ +

ȤÀº ÀÌ µð·ºÅ丮¿¡ ÀÖ´Â ¸ðµç ÆÄÀÏÀ» CGI ÇÁ·Î±×·¥À¸·Î + ó¸®ÇÏ°í ½Í´Ù¸é ´ÙÀ½°ú °°Àº ¼³Á¤µµ °¡´ÉÇÏ´Ù.

+ +

+ Options +ExecCGI
+ SetHandler cgi-script +

+ +

ÀÌ Áö½Ã¾î°¡ µ¿ÀÛÇÏ·Á¸é AllowOverride Options¿Í + AllowOverride FileInfo°¡ ¸ðµÎ ÇÊ¿äÇÔÀ» ¸í½ÉÇ϶ó.

+ +

CGI ÇÁ·Î±×·¡¹Ö°ú ¼³Á¤¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸íÀº CGI ÅõÅ丮¾óÀ» º¸±æ ¹Ù¶õ´Ù.

+ +
top
+
+

¹®Á¦ÇØ°á

+ +

.htaccess ÆÄÀÏ¿¡ µÐ ¼³Á¤ Áö½Ã¾î°¡ ¿øÇÏ´Â + ±â´ÉÀ» ÇÏÁö ¾Ê´Â °æ¿ì ¿©·¯°¡Áö ÀÌÀ¯°¡ ÀÖÀ» ¼ö ÀÖ´Ù.

+ +

°¡Àå ÀϹÝÀûÀÎ ¹®Á¦´Â ¼³Á¤ Áö½Ã¾î¸¦ °¡´ÉÇÏ°Ô ¸¸µå´Â AllowOverride¸¦ ¼³Á¤ÇÏÁö ¾ÊÀº + °æ¿ì´Ù. ¹®Á¦°¡ µÇ´Â ÆÄÀÏ ¿µ¿ª¿¡ AllowOverride NoneÀÌ + ¾ø´ÂÁö È®ÀÎÇÑ´Ù. .htaccess ÆÄÀÏÀ» ¾Æ¹«·¸°Ô³ª + ÀûÀº ´ÙÀ½ ÆäÀÌÁö¸¦ ´Ù½Ã Á¢±ÙÇÏ¿© ½±°Ô °Ë»çÇغ¼ ¼ö ÀÖ´Ù. + ¼­¹ö ¿À·ù°¡ ³ª¿ÀÁö ¾ÊÀ¸¸é °ÅÀÇ È®½ÇÈ÷ + AllowOverride NoneÀ» »ç¿ëÇÑ °æ¿ì´Ù.

+ +

¹Ý´ë·Î ¹®¼­¿¡ Á¢±ÙÇÒ¶§ ¼­¹ö ¿À·ù°¡ ¹ß»ýÇÏ¸é ¾ÆÆÄÄ¡ ¿À·ù·Î±×¸¦ + »ìÆìºÁ¶ó. ¾Æ¸¶µµ .htaccess ÆÄÀÏ¿¡ ÀÖ´Â Áö½Ã¾î¸¦ + Çã¿ëÇÏÁö ¾Ê´Â´Ù°í ÇÒ °ÍÀÌ´Ù. ¾Æ´Ï°í ¹®¹ý ¿À·ù°¡ ÀÖ´Ù¸é ¿À·ù¸¦ + °íÄ£´Ù.

+ +
+
+

°¡´ÉÇÑ ¾ð¾î:  en  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/htaccess.html.pt-br b/docs/manual/howto/htaccess.html.pt-br new file mode 100644 index 00000000..f48691a6 --- /dev/null +++ b/docs/manual/howto/htaccess.html.pt-br @@ -0,0 +1,375 @@ + + + +Tutorial do Apache: arquivos .htaccess - Servidor HTTP Apache + + + + +
+

Módulos | Diretrizes | FAQ | Glossário | Mapa do site

+

Servidor HTTP Apache Versão 2.2

+
+
<-
+
+Apache > Servidor HTTP > Documentação > Versão 2.2 > How-To / Tutoriais

Tutorial do Apache: arquivos .htaccess

+
+

Línguas Disponíveis:  en  | + ja  | + ko  | + pt-br 

+
+ +

Arquivos .htaccess oferecem um meio de fazer mudanças + nas configurações por-diretório.

+
+ +
top
+
+

Arquivos .htaccess

+
Módulos RelacionadosDiretrizes Relacionadas
+
top
+
+

O que eles são/Como usá-los

+ + +

Os arquivos .htaccess (ou "arquivos de + configuração distribuída") oferecem um meio de fazer mudanças nas + configurações por-diretório. Um arquivo, contendo uma ou mais + diretrizes de configurações, é colocado em um diretório + em particular, e as diretrizes se aplicam para aquele diretório e todos + os seu subdiretórios subseqüentes.

+ +

Nota:

+

Se você quiser renomear o seu arquivo .htaccess + para outro nome, você deve usar a diretriz AccessFileName. Por exemplo, se você + prefere que o arquivo se chame .config, então você + pode adicionar a seguinte linha ao seu arquivo de configuração + do servidor:

+ +

+ AccessFileName .config +

+
+ +

No geral, arquivos .htaccess usam a mesma sintaxe + que os arquivos de + configuração principal. O que você pode colocar nesses + arquivos é determinado pele diretriz AllowOverride. Essa diretriz especifica, + em categorias, quais diretrizes serão aceitas caso sejam + encontradas em um arquivo .htaccess. Se uma diretriz + for permitida em um arquivo .htaccess, a documentação + para essa diretriz irá conter uma seção Override, + especificando que valor precisa estar em AllowOverride para que esta diretriz + seja permitida.

+ +

Por exemplo, se você procurar na documentação pela diretriz + AddDefaultCharset, você + achará que ela é permitida nos arquivos .htaccess. + (Veja a linha Contexto no sumário das diretivas.) A + linha Override lê + FileInfo. Então, você deve ao menos ter + AllowOverride FileInfo para que essa diretriz seja + aceita nos arquivos .htaccess.

+ +

Exemplo:

+ + + + + + + + + +
Contexto:configuração do servidor, hospedeiros virtuais, diretório, .htaccess
Override:FileInfo
+ +

Se você estiver incerto se uma diretriz em particular é + aceita em um arquivo .htaccess, procure na + documentação por essa diretriz, e verifique a linha de + Contexto por ".htaccess".

top
+
+

Quando (não) usar arquivos .htaccess

+ +

No geral, você nunca deve usar arquivos .htaccess + a não ser que você não tenha acesso ao arquivo de configuração + principal do servidor. Existe, por exemplo, um erro de concepção + que dita que a autenticação de usuários sempre deve + ser feita usando os arquivos .htaccess. Esse + simplesmente não é o caso. Você pode usar as configurações de + autenticação de usuário no arquivo de configuração principal do + servidor, e isso é, de fato, a maneira mais adequada de se fazer + as coisas.

+ +

Arquivos .htaccess devem ser usados em casos onde + os provedores de conteúdo do site precisem fazer mudanças na + configuração do servidor por-diretório, mas não tem + acesso root ao sistema do servidor. Caso o administrador do + servidor não esteja disposto a fazer mudanças freqüentes nas + configurações do servidor, é desejável permitir que os + usuários possam fazer essas mudanças através de arquivos + .htaccess eles mesmos. Isso é particularmente + verdade, por exemplo, em casos onde provedores estão fornecendo + múltiplos sites para usuários em apenas uma máquina, e querem que + seus usuários possam alterar suas configurações.

+ +

No entanto, de modo geral, o uso de arquivos .htaccess + deve ser evitado quando possível. Quaisquer configurações + que você considerar acrescentar em um arquivo .htaccess, podem + ser efetivamente colocadas em uma seção <Directory> no arquivo principal de + configuração de seu servidor.

+ +

Existem duas razões principais para evitar o uso de arquivos + .htaccess.

+ +

A primeira delas é a performance. Quando AllowOverride é configurado para + permitir o uso de arquivos .htaccess, o Apache procura + em todos diretórios por arquivos .htaccess. + Logo, permitir arquivos .htaccess causa um impacto na + performance, mesmo sem você usá-los de fato! Além disso, + o arquivo .htaccess é carregado toda vez que um documento + é requerido.

+ +

Além disso, note que o Apache precisa procurar pelos arquivos + .htaccess em todos os diretórios superiores, para ter + o complemento total de todas as diretivas que devem ser + aplicadas. (Veja a seção como as diretrizes são + aplicadas.) Então, se um arquivo de um diretório + /www/htdocs/example é requerido, o Apache precisa + procurar pelos seguintes arquivos:

+ +

+ /.htaccess
+ /www/.htaccess
+ /www/htdocs/.htaccess
+ /www/htdocs/example/.htaccess +

+ +

Assim, para cada acesso de arquivo fora desse diretório, + existem 4 acessos ao sistema de arquivos adicionais, mesmo + que nenhum desses arquivos estejam presentes. (Note que esse + só será o caso se os arquivos .htaccess + estiverem habilitados para /, o que + normalmente não é o verdade.)

+ +

A segunda consideração é relativa à segurança. + Você está permitindo que os usuários modifiquem as + configurações do servidor, o que pode resultar em mudanças + que podem fugir ao seu controle. Considere com cuidado se você quer + ou não dar aos seus usuários esses privilégios. Note também + que dar aos usuários menos privilégios que eles precisam, acarreta em + pedidos de suporte técnico adicionais. Tenha certeza que você comunicou + aos usuários que nível de privilégios você os deu. + Especificar exatamente o que você configurou na diretriz AllowOverride, e direcioná-los para a + documentação relevante, irá poupá-lo de muita confusão + depois.

+ +

Perceba que é exatamente equivalente colocar o arquivo + .htaccess em um diretório + /www/htdocs/example contendo uma diretriz, e + adicionar a mesma diretriz em uma seção Directory + <Directory /www/htdocs/example> na configuração + principal do seu servidor:

+ +

Arquivo .htaccess em /www/htdocs/example:

+ +

Conteúdo de um arquivo .htaccess em + /www/htdocs/example

+ AddType text/example .exm +

+ +

Seção do seu arquivo httpd.conf

+ <Directory /www/htdocs/example>
+ + AddType text/example .exm
+ + </Directory> +

+ +

No entanto, adicionando isso ao seu arquivo de configuração do + servidor resultará em uma menor perda de performance, na medida que + a configuração é carregada no momento da inicialização do + servidor, ao invés de toda que que um arquivo é requerido.

+ +

O uso de arquivos .htaccess pode ser totalmente + desabilitado, ajustando a diretriz AllowOverride para none:

+ +

+ AllowOverride None +

+
top
+
+

Como as diretrizes são aplicadas

+ +

As diretrizes de configuração que se encontram em um arquivo + .htaccess são aplicadas para o diretório no qual o + arquivo .htaccess se encontra, e para todos os + subdiretórios ali presentes. Mas, é importante lembrar também que + podem existir arquivos .htaccess no diretórios + superiores. As diretrizes são aplicadas na ordem que são + achadas. Logo, um arquivo .htaccess em um diretório + em particular, pode sobrescrever as diretrizes encontradas em um + diretório acima deste em sua respectiva árvore. Estes, por sua vez, + podem ter suas diretrizes sobrescritas por diretrizes ainda mais + acima, ou no próprio arquivo de configuração principal do + servidor.

+ +

Exemplo:

+ +

No diretório /www/htdocs/example1 nós temos + um arquivo .htaccess contendo o seguinte:

+ +

+ Options +ExecCGI +

+ +

(Nota: você deve ter "AllowOverride Options" para + permitir o uso da diretriz "Options" nos arquivos + .htaccess .)

+ +

No diretório /www/htdocs/example1/example2 nós temos + um arquivo .htaccess contendo:

+ +

+ Options Includes +

+ +

Devido a esse segundo arquivo .htaccess, no + diretório /www/htdocs/example1/example2, a execução + de scripts CGI não é permitida, pois somente Options + Includes está em efeito, o que sobrescreve completamente + quaisquer outros ajustes previamente configurados.

+
top
+
+

Exemplo de Autenticação

+ +

Se você veio diretamente à esta parte do documento para + aprender como fazer autenticação, é importante notar uma + coisa. Existe uma concepção errada, mas muito comum, de que é + necessário o uso de arquivos .htaccess para implementar + a autenticação por senha. Este não é o caso. Colocar + diretrizes de senha em uma seção <Directory>, no seu arquivo principal de + configuração do servidor, é a melhor maneira de se implementar + isto, e os arquivos .htaccess devem ser usados apenas + se você não tem acesso ao arquivo principal de configuração do + servidor. Veja acima a discussão sobre quando + você deve e quando não deve usar os arquivos + .htaccess.

+ +

Dito isso, se você ainda acredita que precisa usar um arquivo + .htaccess, a configuração a seguir provavelmente + funcionará para você.

+ +

Conteúdo de um arquivo .htaccess:

+ +

+ AuthType Basic
+ AuthName "Password Required"
+ AuthUserFile /www/passwords/password.file
+ AuthGroupFile /www/passwords/group.file
+ Require Group admins +

+ +

Note que AllowOverride AuthConfig precisa estar + habilitado para que estas diretrizes tenham efeito.

+ +

Por favor veja o tutorial de + autenticação para uma discussão mais completa sobre + autenticação e autorização.

+
top
+
+

Exemplo de Server Side Includes

+ +

Outro uso comum de arquivos .htaccess é ativar o + Server Side Includes para um diretório em particular. Isto pode + ser feito com as seguintes diretrizes de configuração, colocadas em + um arquivo .htaccess no diretório desejado:

+ +

+ Options +Includes
+ AddType text/html shtml
+ AddHandler server-parsed shtml +

+ +

Note que ambos AllowOverride Options e + AllowOverride FileInfo precisam estar habilitados + para essas diretrizes terem efeito.

+ +

Por favor veja o tutorial de SSI para + uma discussão mais completa sobre server-side includes.

+
top
+
+

Exemplo de CGI

+ +

Finalmente, você pode querer que um arquivo + .htaccess permita a execução de programas CGI em um + diretório em particular. Isto pode ser implementado com as + seguintes configurações:

+ +

+ Options +ExecCGI
+ AddHandler cgi-script cgi pl +

+ +

Alternativamente, se você desejar que todos os arquivos de um + dado diretório, sejam considerados programas CGI, isso pode ser + feito com a seguinte configuração:

+ +

+ Options +ExecCGI
+ SetHandler cgi-script +

+ +

Note que ambos AllowOverride Options e + AllowOverride FileInfo precisam estar habilitados + para que essas diretrizes tenham quaisquer efeito.

+ +

Por favor veja o tutorial de CGI + tutorial para uma discussão mais completa sobre programação + e configuração CGI.

+
top
+
+

Resolvendo Problemas

+ +

Quando você adiciona diretrizes de configuração em um arquivo + .htaccess, e não obtém o efeito desejado, existe uma + série de pontos que podem estar errados.

+ +

Mais comumente, o problema é que a diretriz AllowOverride não está habilitada + corretamente para que as suas diretrizes de configurações sejam + honradas. Verifique se você não possui AllowOverride + None ajustado para o escopo do arquivo em questão. Um bom + meio de testar isso é colocar "lixo" em seu arquivo + .htaccess e recarregá-lo. Se não for gerado nenhum + erro do servidor, certamente você tem AllowOverride + None habilitado.

+ +

Se, por outro lado, você está obtendo erros do servidor ao + tentar acessar documentos, verifique o registro de erros do + Apache. Ele provavelmente irá indicar que a diretriz usada em + seu arquivo .htaccess não é permitida. + Alternativamente, ele pode acusar erros de sintaxe que você terá + que corrigir.

+ +
+
+

Línguas Disponíveis:  en  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/index.html b/docs/manual/howto/index.html new file mode 100644 index 00000000..9ee33086 --- /dev/null +++ b/docs/manual/howto/index.html @@ -0,0 +1,11 @@ +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/howto/index.html.en b/docs/manual/howto/index.html.en new file mode 100644 index 00000000..5e918118 --- /dev/null +++ b/docs/manual/howto/index.html.en @@ -0,0 +1,117 @@ + + + +How-To / Tutorials - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

How-To / Tutorials

+
+

Available Languages:  en  | + ja  | + ko 

+
+
+
top
+
+

How-To / Tutorials

+ + + +
+
Authentication and Authorization
+
+

Authentication is any process by which you verify that + someone is who they claim they are. Authorization is any + process by which someone is allowed to be where they want to + go, or to have information that they want to have.

+ +

See: Authentication, Authorization

+
+
+ +
+
Access Control
+
+

Access control refers to the process of restricting, or + granting access to a resource based on arbitrary criteria. There + are a variety of different ways that this can be + accomplished.

+ +

See: Access Control

+
+
+ +
+
Dynamic Content with CGI
+
+

The CGI (Common Gateway Interface) defines a way for a web + server to interact with external content-generating programs, + which are often referred to as CGI programs or CGI scripts. It + is the simplest, and most common, way to put dynamic content on + your web site. This document will be an introduction to setting + up CGI on your Apache web server, and getting started writing + CGI programs.

+ +

See: CGI: Dynamic Content

+
+
+ +
+
.htaccess files
+
+

.htaccess files provide a way to make configuration + changes on a per-directory basis. A file, containing one or more + configuration directives, is placed in a particular document directory, + and the directives apply to that directory, and all subdirectories thereof.

+ +

See: .htaccess files

+
+
+ +
+
Introduction to Server Side Includes
+
+

SSI (Server Side Includes) are directives that are placed in + HTML pages, and evaluated on the server while the pages are + being served. They let you add dynamically generated content to + an existing HTML page, without having to serve the entire page + via a CGI program, or other dynamic technology.

+ +

See: Server Side Includes (SSI)

+
+
+ +
+
Per-user web directories
+
+

On systems with multiple users, each user can be permitted to have a + web site in their home directory using the UserDir directive. Visitors + to a URL http://example.com/~username/ will get content + out of the home directory of the user "username", out of + the subdirectory specified by the UserDir directive.

+ +

See: User web directories (public_html)

+
+
+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/index.html.ja.euc-jp b/docs/manual/howto/index.html.ja.euc-jp new file mode 100644 index 00000000..ef8cf41f --- /dev/null +++ b/docs/manual/howto/index.html.ja.euc-jp @@ -0,0 +1,104 @@ + + + +How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+
+
top
+
+

How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë

+ + + +
+
ǧ¾Ú
+
+

ǧ¾Ú¤È¤Ï¡¢Ã¯¤«¤¬¼«Ê¬¤Ïï¤Ç¤¢¤ë¤«¤ò̾¾è¤Ã¤Æ¤¤¤ë¤â¤Î¤ò¸¡¾Ú¤¹¤ë + ½èÍý¤Î¤³¤È¤Ç¤¹¡£¾µÇ§¤È¤Ï¡¢Ã¯¤«¤¬Ë¾¤ß¤Î¾ì½ê¤Ëé¤êÃ失¤¿¤ê¡¢ + ˾¤ß¤Î¾ðÊó¤ò¼ê¤ËÆþ¤ì¤¿¤ê¤¹¤ë¤³¤È¤òµö²Ä¤¹¤ë½èÍý¤Î¤³¤È¤Ç¤¹¡£

+ +

»²¾È: ǧ¾Ú¡¢¾µÇ§¡¢¥¢¥¯¥»¥¹À©¸æ

+
+
+ +
+
CGI ¤Ë¤è¤ëưŪ¥³¥ó¥Æ¥ó¥Ä
+
+

CGI (Common Gateway Interface) ¤Ï¥¦¥§¥Ö¥µ¡¼¥Ð¤¬³°Éô¤Î¥³¥ó¥Æ¥ó¥Ä + À¸À®¥×¥í¥°¥é¥à¤È¤É¤Î¤è¤¦¤ËÁê¸ßÆ°ºî¤ò¤¹¤ë¤«¤òÄêµÁ¤·¤Þ¤¹¡£ + ¤½¤Î³°Éô¥×¥í¥°¥é¥à¤ÏÄ̾ï CGI ¥×¥í¥°¥é¥à¤ä CGI ¥¹¥¯¥ê¥×¥È¤È¸Æ¤Ð¤ì¤Þ¤¹¡£ + CGI ¤Ï¥¦¥§¥Ö¥µ¥¤¥È¤ËưŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤òÄɲ乤뤿¤á¤Î¡¢ + °ìÈÖñ½ã¤Ç¤è¤¯»È¤ï¤ì¤Æ¤¤¤ëÊýË¡¤Ç¤¹¡£¤³¤Îʸ½ñ¤Ï Apache ¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë + CGI ¤òÀßÄꤷ¡¢CGI ¥×¥í¥°¥é¥à¤ò½ñ¤­»Ï¤á¤ë¤¿¤á¤Î¥¤¥ó¥È¥í¥À¥¯¥·¥ç¥ó¤Ç¤¹¡£

+ +

»²¾È: CGI: ưŪ¥³¥ó¥Æ¥ó¥Ä

+
+
+ +
+
.htaccess ¥Õ¥¡¥¤¥ë
+
+

.htaccess ¥Õ¥¡¥¤¥ë¤Ï¥Ç¥£¥ì¥¯¥È¥êËè¤ËÀßÄê¤òÊѹ¹¤¹¤ë¤¿¤á¤Î + ÊýË¡¤òÄ󶡤·¤Þ¤¹¡£ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬½ñ¤«¤ì¤¿¥Õ¥¡¥¤¥ë¤¬¡¢¤¢¤ë¥É¥­¥å¥á¥ó¥È + ¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤«¤ì¤ë¤È¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤È + ¤¹¤Ù¤Æ¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ËŬÍѤµ¤ì¤Þ¤¹¡£

+ +

»²¾È: .htaccess ¥Õ¥¡¥¤¥ë

+
+
+ +
+
Server Side Includes ¥¤¥ó¥È¥í¥À¥¯¥·¥ç¥ó
+
+

SSI (Server Side Includes) ¤Ï HTML ¥Ú¡¼¥¸Ãæ¤Ë½ñ¤«¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¡¢ + ¥Ú¡¼¥¸¤¬Á÷¤é¤ì¤ë»þ¤Ë¥µ¡¼¥Ð¤Ë¤è¤êɾ²Á¤µ¤ì¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢¥Ú¡¼¥¸Á´ÂΤò + CGI ¥×¥í¥°¥é¥à¤ÇÀ¸À®¤·¤¿¤ê¡¢Â¾¤ÎưŪ¤Êµ»½Ñ¤ò»È¤¦¤³¤È¤Ê¤¯¡¢´û¸¤Î HTML + ¥Ú¡¼¥¸¤ËưŪ¤ËÀ¸À®¤µ¤ì¤¿ÆâÍƤòÉղ乤뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

»²¾È: Server Side Includes (SSI)

+
+
+ +
+
¥æ¡¼¥¶Ëè¤Î¥¦¥§¥Ö¥Ç¥£¥ì¥¯¥È¥ê
+
+

Ê£¿ô¥æ¡¼¥¶¤Î¸ºß¤¹¤ë¥·¥¹¥Æ¥à¤Ç¤Ï¡¢¤½¤ì¤¾¤ì¤Î¥æ¡¼¥¶¤Ï UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤³¤È¤Ë¤è¤Ã¤Æ + ¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¾å¤Ë¥¦¥§¥Ö¥µ¥¤¥È¤òºîÀ®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + URL http://example.com/~username/ ¤òˬ¤ì¤¿¿Í¤Ï + ¥æ¡¼¥¶ "username" ¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Î¡¢UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿ + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¥³¥ó¥Æ¥ó¥Ä¤òÆÀ¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

»²¾È: ¥æ¡¼¥¶¥¦¥§¥Ö¥Ç¥£¥ì¥¯¥È¥ê (public_html)

+
+
+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/index.html.ko.euc-kr b/docs/manual/howto/index.html.ko.euc-kr new file mode 100644 index 00000000..53410a64 --- /dev/null +++ b/docs/manual/howto/index.html.ko.euc-kr @@ -0,0 +1,109 @@ + + + +How-To / ÅõÅ丮¾ó - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

How-To / ÅõÅ丮¾ó

+
+

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

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

How-To / ÅõÅ丮¾ó

+ + + +
+
ÀÎÁõ
+
+

ÀÎÁõ(authentication)Àº ÀÚ½ÅÀÌ ´©±¸¶ó°í ÁÖÀåÇÏ´Â »ç¶÷À» + È®ÀÎÇÏ´Â ÀýÂ÷ÀÌ´Ù. ±ÇÇѺο©(authorization)´Â °¡°í ½ÍÀº + °÷À¸·Î °¡µµ·Ï ȤÀº ¿øÇÏ´Â Á¤º¸¸¦ ¾òµµ·Ï Çã¿ëÇÏ´Â °úÁ¤ÀÌ´Ù.

+ +

Âü°í: ÀÎÁõ, ±ÇÇѺο©, Á¢±ÙÁ¦¾î

+
+
+ +
+
CGI¸¦ »ç¿ëÇÑ µ¿Àû ÆäÀÌÁö »ý¼º
+
+

CGI (Common Gateway Interface)´Â À¥¼­¹ö°¡ º¸Åë CGI + ÇÁ·Î±×·¥ ȤÀº CGI ½ºÅ©¸³Æ®ÇÏ°í ºÎ¸£´Â, (À¥ÆäÀÌÁö ³»¿ëÀ» + ¸¸µå´Â) ¿ÜºÎ ÇÁ·Î±×·¥°ú »óÈ£ÀÛ¿ëÇÏ´Â ¹æ¹ýÀ» Á¤ÀÇÇÑ´Ù. + À¥»çÀÌÆ®¿¡¼­ µ¿ÀûÀÎ ÆäÀÌÁö¸¦ ¸¸µå´Â °¡Àå ÈçÇÏ°í °£´ÜÇÑ + ¹æ¹ýÀÌ´Ù. ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ À¥¼­¹ö¿¡ CGI¸¦ ±¸¼ºÇÏ´Â ¹æ¹ýÀ» + ¼Ò°³ÇÏ°í, CGI ÇÁ·Î±×·¥À» ÀÛ¼ºÇغ»´Ù.

+ +

Âü°í: CGI: µ¿Àû ÆäÀÌÁö »ý¼º

+
+
+ +
+
.htaccess ÆÄÀÏ
+
+

.htaccess ÆÄÀÏÀ» »ç¿ëÇÏ¿© µð·ºÅ丮º°·Î + ¼³Á¤À» º¯°æÇÒ ¼ö ÀÖ´Ù. ¿©·¯ ¼³Á¤ Áö½Ã¾î°¡ ÀÖ´Â ÆÄÀÏÀ» + ƯÁ¤ ¹®¼­ µð·ºÅ丮¿¡ µÎ¸é, ±× µð·ºÅ丮¿Í ¸ðµç ÇÏÀ§µð·ºÅ丮¿¡ + Áö½Ã¾î¸¦ Àû¿ëÇÑ´Ù.

+ +

Âü°í: .htaccess + ÆÄÀÏ

+
+
+ +
+
Server Side Includes ¼Ò°³
+
+

SSI (Server Side Includes)´Â HTML ÆäÀÌÁö¿¡ »ç¿ëÇÏ´Â + Áö½Ã¾î·Î, ÆäÀÌÁö¸¦ ¼­ºñ½ºÇÒ¶§ ¼­¹ö°¡ ó¸®ÇÑ´Ù. SSI¸¦ + »ç¿ëÇϸé CGI ÇÁ·Î±×·¥À̳ª ´Ù¸¥ µ¿ÀûÀÎ ±â¼ú·Î ÆäÀÌÁö + Àüü¸¦ ¸¸µé¾î¼­ ¼­ºñ½ºÇÏÁö ¾Ê°íµµ HTML ÆäÀÌÁö¿¡ µ¿ÀûÀ¸·Î + »ý¼ºÇÑ ³»¿ëÀ» Ãß°¡ÇÒ ¼ö ÀÖ´Ù.

+ +

Âü°í: Server Side Includes (SSI)

+
+
+ +
+
»ç¿ëÀÚº° À¥µð·ºÅ丮
+
+

¿©·¯ »ç¿ëÀÚ°¡ ÀÖ´Â ½Ã½ºÅÛ¿¡¼­ UserDir Áö½Ã¾î¸¦ »ç¿ëÇϸé + °¢ »ç¿ëÀÚ´Â ÀÚ½ÅÀÇ È¨µð·ºÅ丮 ¾È¿¡ À¥»çÀÌÆ®¸¦ ¸¸µé ¼ö + ÀÖ´Ù. URL http://example.com/~username/¿¡ + Á¢±ÙÇÏ¸é »ç¿ëÀÚ "username"ÀÇ È¨µð·ºÅ丮¿¡¼­ + UserDir + Áö½Ã¾î·Î ÁöÁ¤ÇÑ ÇÏÀ§µð·ºÅ丮¿¡ ÀÖ´Â ÆäÀÌÁö¸¦ °¡Á®¿À°Ô + µÈ´Ù.

+ +

Âü°í: »ç¿ëÀÚ À¥µð·ºÅ丮 + (public_html)

+
+
+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/howto/public_html.html b/docs/manual/howto/public_html.html new file mode 100644 index 00000000..690c35b2 --- /dev/null +++ b/docs/manual/howto/public_html.html @@ -0,0 +1,11 @@ +URI: public_html.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: public_html.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: public_html.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/howto/public_html.html.en b/docs/manual/howto/public_html.html.en new file mode 100644 index 00000000..b227be48 --- /dev/null +++ b/docs/manual/howto/public_html.html.en @@ -0,0 +1,161 @@ + + + +Per-user web directories - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

Per-user web directories

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

On systems with multiple users, each user can be permitted to have a + web site in their home directory using the UserDir directive. Visitors + to a URL http://example.com/~username/ will get content + out of the home directory of the user "username", out of + the subdirectory specified by the UserDir directive.

+ +
+ +
top
+
+

Per-user web directories

+ +
Related ModulesRelated Directives
+
top
+
+

Setting the file path with UserDir

+ + +

The UserDir + directive specifies a directory out of which per-user + content is loaded. This directive may take several different forms.

+ +

If a path is given which does not start with a leading slash, it is + assumed to be a directory path relative to the home directory of the + specified user. Given this configuration:

+ +

+ UserDir public_html +

+ +

the URL http://example.com/~rbowen/file.html will be + translated to the file path + /home/rbowen/public_html/file.html

+ +

If a path is given starting with a slash, a directory path will be + constructed using that path, plus the username specified. Given this + configuration:

+ +

+ UserDir /var/html +

+ +

the URL http://example.com/~rbowen/file.html will be + translated to the file path /var/html/rbowen/file.html

+ +

If a path is provided which contains an asterisk (*), a path is used + in which the asterisk is replaced with the username. Given this + configuration:

+ +

+ UserDir /var/www/*/docs +

+ +

the URL http://example.com/~rbowen/file.html will be + translated to the file path + /var/www/rbowen/docs/file.html

+ +
top
+
+

Restricting what users are permitted to use this + feature

+ + +

Using the syntax shown in the UserDir documentation, you can restrict + what users are permitted to use this functionality:

+ +

+ UserDir enabled
+ UserDir disabled root jro fish +

+ +

The configuration above will enable the feature for all users + except for those listed in the disabled statement. + You can, likewise, disable the feature for all but a few users by + using a configuration like the following:

+ +

+ UserDir disabled
+ UserDir enabled rbowen krietz +

+ +

See UserDir + documentation for additional examples.

+ +
top
+
+

Enabling a cgi directory for each user

+ + +

In order to give each user their own cgi-bin directory, you can use + a <Directory> + directive to make a particular subdirectory of a user's home directory + cgi-enabled.

+ +

+ <Directory /home/*/public_html/cgi-bin/>
+ Options ExecCGI
+ SetHandler cgi-script
+ </Directory> +

+ +

Then, presuming that UserDir is set to + public_html, a cgi program example.cgi + could be loaded from that directory as:

+ +

+ http://example.com/~rbowen/cgi-bin/example.cgi +

+ +
top
+
+

Allowing users to alter configuration

+ + +

If you want to allows users to modify the server configuration in + their web space, they will need to use .htaccess files to + make these changed. Ensure that you have set AllowOverride to a + value sufficient for the directives that you want to permit the users + to modify. See the .htaccess tutorial for + additional details on how this works.

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/public_html.html.ja.euc-jp b/docs/manual/howto/public_html.html.ja.euc-jp new file mode 100644 index 00000000..ea621c6a --- /dev/null +++ b/docs/manual/howto/public_html.html.ja.euc-jp @@ -0,0 +1,155 @@ + + + +¥æ¡¼¥¶Ëè¤Î¥¦¥§¥Ö¥Ç¥£¥ì¥¯¥È¥ê - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë

¥æ¡¼¥¶Ëè¤Î¥¦¥§¥Ö¥Ç¥£¥ì¥¯¥È¥ê

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

Ê£¿ô¤Î¥æ¡¼¥¶¤Î¤¤¤ë¥·¥¹¥Æ¥à¤Ç¤Ï¡¢UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ + ³Æ¥æ¡¼¥¶¤¬¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥¦¥§¥Ö¥µ¥¤¥È¤ò¹½ÃۤǤ­¤ë¤è¤¦¤ËÀßÄꤹ¤ë¤³¤È¤¬ + ²Äǽ¤Ç¤¹¡£URL http://example.com/~username/ ¤òˬ¤ì¤¿¿Í¤Ï + "username" ¤È¤¤¤¦¥æ¡¼¥¶¤Î UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿ + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¥³¥ó¥Æ¥ó¥Ä¤òÆÀ¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+
+ +
top
+
+

¥æ¡¼¥¶Ëè¤Î¥¦¥§¥Ö¥Ç¥£¥ì¥¯¥È¥ê

+ +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+
top
+
+

UserDir ¤ò»È¤Ã¤Æ¥Õ¥¡¥¤¥ë¤Î¥Ñ¥¹¤òÀßÄꤹ¤ë

+ + +

UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥æ¡¼¥¶Ëè¤Î¥³¥ó¥Æ¥ó¥Ä¤¬Æɤ߹þ¤Þ¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¤¤í¤¤¤í°ã¤Ã¤¿·Á¼°¤ò¼è¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¥¹¥é¥Ã¥·¥å¤Ç»Ï¤Þ¤é¤Ê¤¤¥Ñ¥¹¤¬Í¿¤¨¤é¤ì¤¿¤È¤­¤Ï¡¢¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê + ¤«¤é¤ÎÁêÂХѥ¹¤È¤ß¤Ê¤µ¤ì¤Þ¤¹¡£¼¡¤ÎÀßÄ꤬¤¢¤Ã¤¿¤È¤­¤Ë:

+ +

+ UserDir public_html +

+ +

URL http://example.com/~rbowen/file.html ¤Ï + ¥Ñ¥¹ /home/rbowen/public_html/file.html ¤Ø + ÊÑ´¹¤µ¤ì¤Þ¤¹¡£

+ +

¥Ñ¥¹¤¬¥¹¥é¥Ã¥·¥å¤Ç»Ï¤Þ¤ë¤È¤­¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥ê¥Ñ¥¹¤Ï¤½¤Î¥Ñ¥¹¤Ë + ¥æ¡¼¥¶Ì¾¤ò²Ã¤¨¤¿¤â¤Î¤«¤é¤Ê¤ê¤Þ¤¹¡£¼¡¤ÎÀßÄê¤Î¤È¤­:

+ +

+ UserDir /var/html +

+ +

URL http://example.com/~rbowen/file.html ¤Ï + ¥Ñ¥¹ /var/html/rbowen/file.html ¤ØÊÑ´¹¤µ¤ì¤Þ¤¹¡£

+ +

¥¢¥¹¥¿¥ê¥¹¥¯ (*) ¤ò´Þ¤à¥Ñ¥¹¤¬»ØÄꤵ¤ì¤¿¤È¤­¤Ï¡¢¥¢¥¹¥¿¥ê¥¹¥¯¤ò + ¥æ¡¼¥¶Ì¾¤ÇÃÖ´¹¤·¤¿¤â¤Î¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£¤³¤Î¤è¤¦¤ÊÀßÄê¤À¤È:

+ +

+ UserDir /var/www/*/docs +

+ +

URL http://example.com/~rbowen/file.html ¤Ï + ¥Ñ¥¹ /var/www/rbowen/docs/file.html ¤ØÊÑ´¹¤µ¤ì¤Þ¤¹¡£

+ +
top
+
+

¤³¤Îµ¡Ç½¤ò»ÈÍѤǤ­¤ë¥æ¡¼¥¶¤òÀ©¸Â¤¹¤ë

+ + +

UserDir ¤Î¥É¥­¥å¥á¥ó¥È¤Ë¼¨¤µ¤ì¤Æ¤¤¤ë¹½Ê¸¤ò»È¤¦¤³¤È¤Ç¡¢ + ¤É¤Î¥æ¡¼¥¶¤¬¤³¤Îµ¡Ç½¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤ë¤«¤òÀ©¸Â¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ UserDir enabled
+ UserDir disabled root jro fish +

+ +

¾å¤ÎÀßÄê¤Ï dissabled ʸ¤Î¥æ¡¼¥¶°Ê³°¤Î¤¹¤Ù¤Æ¤Î¥æ¡¼¥¶¤Ë + ÂФ·¤Æ UserDir ¤Îµ¡Ç½¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£Æ±Íͤˤ·¤Æ¡¢°Ê²¼¤Î¤è¤¦¤Ë + ¿ô̾¤Î¥æ¡¼¥¶°Ê³°¤ËÂФ·¤Æ¤³¤Îµ¡Ç½¤ò̵¸ú¤Ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹:

+ +

+ UserDir disabled
+ UserDir enabled rbowen krietz +

+ +

¾¤ÎÎã¤Ï UserDir + ¤ÎÀâÌÀ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
top
+
+

¥æ¡¼¥¶Ëè¤Î CGI ¥Ç¥£¥ì¥¯¥È¥ê

+ + +

¤½¤ì¤¾¤ì¤Î¥æ¡¼¥¶¤ËÀìÍѤΠcgi-bin ¥Ç¥£¥ì¥¯¥È¥ê¤òÍ¿¤¨¤ë¤¿¤á¤Ë¡¢ + <Directory> + ¤ò»È¤Ã¤Æ¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Î»ØÄꤵ¤ì¤¿Îΰè¤ËÂФ·¤Æ CGI ¤òÍ­¸ú¤Ë + ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ <Directory /home/*/public_html/cgi-bin/>
+ Options ExecCGI
+ SetHandler cgi-script
+ </Directory> +

+ +

¤½¤·¤Æ¡¢UserDir ¤¬ + public_html ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤È²¾Äꤹ¤ë¤È¡¢ + ¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î CGI ¥×¥í¥°¥é¥à example.cgi + ¤Ï°Ê²¼¤ÎÍͤ˸ƤӽФµ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ http://example.com/~rbowen/cgi-bin/example.cgi +

+ +
top
+
+

¥æ¡¼¥¶¤Ë¤è¤ëÀßÄêÊѹ¹¤òµö²Ä

+ + +

¥æ¡¼¥¶¤ËÈà¤é¤Î¥¦¥§¥Ö¶õ´Ö¤Ç¤Î¥µ¡¼¥Ð¤ÎÀßÄê¤ÎÊѹ¹¤òµö²Ä¤¹¤ë¾ì¹ç¡¢ + ¥æ¡¼¥¶¤Ï .htaccess ¥Õ¥¡¥¤¥ë¤ò»È¤Ã¤ÆÀßÄê¤òÊѹ¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + AllowOverride ¤ÎÃͤò + ¥æ¡¼¥¶¤¬Êѹ¹¤¹¤ë¤³¤È¤òµö²Ä¤·¤¿¤¤¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ËÂФ·¤Æ½½Ê¬¤Ê¤â¤Î¤Ë + ÀßÄꤷ¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£¤³¤Îµ¡Ç½¤¬¤É¤Î¤è¤¦¤Ë¤·¤ÆÆ°ºî¤·¤Æ¤¤¤ë¤« + ¤Î¾ÜºÙ¤Ï .htaccess ¥Á¥å¡¼¥È¥ê¥¢¥ë ¤òÆɤó¤Ç + ¤¯¤À¤µ¤¤¡£

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/public_html.html.ko.euc-kr b/docs/manual/howto/public_html.html.ko.euc-kr new file mode 100644 index 00000000..359e5d74 --- /dev/null +++ b/docs/manual/howto/public_html.html.ko.euc-kr @@ -0,0 +1,156 @@ + + + +»ç¿ëÀÚº° À¥µð·ºÅ丮 - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

»ç¿ëÀÚº° À¥µð·ºÅ丮

+
+

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

+
+ +

¿©·¯ »ç¿ëÀÚ°¡ ÀÖ´Â ½Ã½ºÅÛ¿¡¼­ UserDir Áö½Ã¾î¸¦ »ç¿ëÇϸé + °¢ »ç¿ëÀÚ´Â ÀÚ½ÅÀÇ È¨µð·ºÅ丮 ¾È¿¡ À¥»çÀÌÆ®¸¦ ¸¸µé ¼ö ÀÖ´Ù. + URL http://example.com/~username/¿¡ Á¢±ÙÇϸé + »ç¿ëÀÚ "username"ÀÇ È¨µð·ºÅ丮¿¡¼­ UserDir Áö½Ã¾î·Î ÁöÁ¤ÇÑ + ÇÏÀ§µð·ºÅ丮¿¡ ÀÖ´Â ÆäÀÌÁö¸¦ °¡Á®¿À°Ô µÈ´Ù.

+ +
+ +
top
+
+

»ç¿ëÀÚº° À¥µð·ºÅ丮

+ +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+
top
+
+

UserDir·Î ÆÄÀÏ°æ·Î ÁöÁ¤Çϱâ

+ + +

UserDir + Áö½Ã¾î´Â »ç¿ëÀÚº° ÆäÀÌÁö¸¦ °¡Á®¿Ã µð·ºÅ丮¸¦ ÁöÁ¤ÇÑ´Ù. ÀÌ + Áö½Ã¾îÀÇ »ç¿ë¹ýÀº ¿©·¯°¡Áö´Ù.

+ +

½½·¡½¬·Î ½ÃÀÛÇÏÁö¾Ê´Â °æ·Î¸¦ ÁöÁ¤ÇÏ¸é °¢ »ç¿ëÀÚÀÇ + Ȩµð·ºÅ丮¿¡ »ó´ëÀûÀÎ µð·ºÅ丮 °æ·Î·Î ó¸®ÇÑ´Ù. ¿¹¸¦ µé¾î, + ¾Æ·¡ ¼³Á¤ÀÇ °æ¿ì:

+ +

+ UserDir public_html +

+ +

URL http://example.com/~rbowen/file.htmlÀº + ÆÄÀÏ °æ·Î /home/rbowen/public_html/file.htmlÀ» + ¶æÇÑ´Ù.

+ +

½½·¡½¬·Î ½ÃÀÛÇÏ´Â °æ·Î¸¦ ÁöÁ¤Çϸé ÁöÁ¤ÇÑ µð·ºÅ丮¿¡ + »ç¿ëÀÚ¸íÀ» ´õÇÑ µð·ºÅ丮 °æ·Î¸¦ »ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î, ¾Æ·¡ + ¼³Á¤ÀÇ °æ¿ì:

+ +

+ UserDir /var/html +

+ +

URL http://example.com/~rbowen/file.htmlÀº + ÆÄÀÏ °æ·Î /var/html/rbowen/file.htmlÀ» ¶æÇÑ´Ù.

+ +

º°Ç¥ (*)¸¦ Æ÷ÇÔÇÑ °æ·Î¸¦ ÁöÁ¤ÇÏ¸é º°Ç¥¸¦ »ç¿ëÀÚ¸íÀ¸·Î + ´ëüÇÑ °æ·Î¸¦ »ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î, ¾Æ·¡ ¼³Á¤ÀÇ °æ¿ì:

+ +

+ UserDir /var/www/*/docs +

+ +

URL http://example.com/~rbowen/file.htmlÀº + ÆÄÀÏ °æ·Î /var/www/rbowen/docs/file.htmlÀ» + ¶æÇÑ´Ù.

+ +
top
+
+

±â´ÉÀ» ÀÌ¿ëÇÒ »ç¿ëÀÚ Á¦ÇÑÇϱâ

+ + +

UserDir ¹®¼­¿¡ ÀÖ´Â ¹®¹ýÀ» »ç¿ëÇÏ¿© »ç¿ëÀÚº° À¥µð·ºÅ丮 + ±â´ÉÀ» ÀÌ¿ëÇÒ ¼ö ÀÖ´Â »ç¿ëÀÚ¸¦ Á¦ÇÑÇÒ ¼ö ÀÖ´Ù:

+ +

+ UserDir enabled
+ UserDir disabled root jro fish +

+ +

À§ ¼³Á¤Àº disabled ¹®Àå¿¡ ¿­°ÅÇÑ »ç¶÷À» + Á¦¿ÜÇÏ°í ¸ðµç »ç¿ëÀÚ¿¡°Ô À¥µð·ºÅ丮 ±â´ÉÀ» Çã¶ôÇÑ´Ù. ¶Ç, + ´ÙÀ½°ú °°ÀÌ ¸î¸î »ç¿ëÀÚ¸¦ Á¦¿ÜÇÏ°í ±â´ÉÀ» Çã¶ôÇÏÁö ¾ÊÀ» + ¼öµµ ÀÖ´Ù:

+ +

+ UserDir disabled
+ UserDir enabled rbowen krietz +

+ +

UserDir + ¹®¼­¿¡ ÀÖ´Â ´Ù¸¥ ¿¹µéµµ Âü°íÇ϶ó.

+ +
top
+
+

°¢ »ç¿ëÀÚº° cgi µð·ºÅ丮 ÁöÁ¤Çϱâ

+ + +

»ç¿ëÀÚ¸¶´Ù cgi-bin µð·ºÅ丮¸¦ ºÎ¿©ÇÏ·Á¸é <Directory> Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© »ç¿ëÀÚ È¨µð·ºÅ丮ÀÇ Æ¯Á¤ ÇÏÀ§µð·ºÅ丮¸¦ cgi °¡´ÉÇÏ°Ô + ¸¸µç´Ù.

+ +

+ <Directory /home/*/public_html/cgi-bin/>
+ Options ExecCGI
+ SetHandler cgi-script
+ </Directory> +

+ +

UserDirÀÌ public_htmlÀ̶ó°í + °¡Á¤Çϸé, ´ÙÀ½°ú °°ÀÌ ±× ¾È¿¡ ÀÖ´Â cgi ÇÁ·Î±×·¥ + example.cgi¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Ù.

+ +

+ http://example.com/~rbowen/cgi-bin/example.cgi +

+ +
top
+
+

»ç¿ëÀÚ°¡ ¼³Á¤À» º¯°æÇÒ ¼ö ÀÖµµ·Ï ¸¸µé±â

+ + +

»ç¿ëÀÚ°¡ ÀÚ½ÅÀÇ À¥°ø°£¿¡ ´ëÇÑ À¥¼­¹ö ¼³Á¤À» ¼öÁ¤ÇÏ·Á¸é, + .htaccess ÆÄÀÏÀ» »ç¿ëÇÒ ¼ö ÀÖ¾î¾ß ÇÑ´Ù. AllowOverride¸¦ »ç¿ëÀÚ°¡ ¼öÁ¤ÇÒ + ¼ö ÀÖ´Â Áö½Ã¾î¿¡ ÀûÇÕÇÑ °ªÀ¸·Î ¼³Á¤Ç϶ó. ¾î¶»°Ô µ¿ÀÛÇÏ´ÂÁö¿¡ + ´ëÇÑ ÀÚ¼¼ÇÑ Á´º¸´Â .htaccess + ÅõÅ丮¾óÀ» Âü°íÇ϶ó.

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/howto/ssi.html b/docs/manual/howto/ssi.html new file mode 100644 index 00000000..6142aec8 --- /dev/null +++ b/docs/manual/howto/ssi.html @@ -0,0 +1,11 @@ +URI: ssi.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: ssi.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: ssi.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/howto/ssi.html.en b/docs/manual/howto/ssi.html.en new file mode 100644 index 00000000..4401f26c --- /dev/null +++ b/docs/manual/howto/ssi.html.en @@ -0,0 +1,486 @@ + + + +Apache Tutorial: Introduction to Server Side Includes - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

Apache Tutorial: Introduction to Server Side Includes

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

Server-side includes provide a means to add dynamic content to +existing HTML documents.

+
+ +
top
+
+

Introduction

+
Related ModulesRelated Directives
+ +

This article deals with Server Side Includes, usually called + simply SSI. In this article, I'll talk about configuring your + server to permit SSI, and introduce some basic SSI techniques + for adding dynamic content to your existing HTML pages.

+ +

In the latter part of the article, we'll talk about some of + the somewhat more advanced things that can be done with SSI, + such as conditional statements in your SSI directives.

+ +
top
+
+

What are SSI?

+ +

SSI (Server Side Includes) are directives that are placed in + HTML pages, and evaluated on the server while the pages are + being served. They let you add dynamically generated content to + an existing HTML page, without having to serve the entire page + via a CGI program, or other dynamic technology.

+ +

The decision of when to use SSI, and when to have your page + entirely generated by some program, is usually a matter of how + much of the page is static, and how much needs to be + recalculated every time the page is served. SSI is a great way + to add small pieces of information, such as the current time. + But if a majority of your page is being generated at the time + that it is served, you need to look for some other + solution.

+
top
+
+

Configuring your server to permit SSI

+ + +

To permit SSI on your server, you must have the following + directive either in your httpd.conf file, or in a + .htaccess file:

+

+ Options +Includes +

+ +

This tells Apache that you want to permit files to be parsed + for SSI directives. Note that most configurations contain + multiple Options directives + that can override each other. You will probably need to apply the + Options to the specific directory where you want SSI + enabled in order to assure that it gets evaluated last.

+ +

Not just any file is parsed for SSI directives. You have to + tell Apache which files should be parsed. There are two ways to + do this. You can tell Apache to parse any file with a + particular file extension, such as .shtml, with + the following directives:

+

+ AddType text/html .shtml
+ AddOutputFilter INCLUDES .shtml +

+ +

One disadvantage to this approach is that if you wanted to + add SSI directives to an existing page, you would have to + change the name of that page, and all links to that page, in + order to give it a .shtml extension, so that those + directives would be executed.

+ +

The other method is to use the XBitHack directive:

+

+ XBitHack on +

+ +

XBitHack + tells Apache to parse files for SSI + directives if they have the execute bit set. So, to add SSI + directives to an existing page, rather than having to change + the file name, you would just need to make the file executable + using chmod.

+

+ chmod +x pagename.html +

+ +

A brief comment about what not to do. You'll occasionally + see people recommending that you just tell Apache to parse all + .html files for SSI, so that you don't have to + mess with .shtml file names. These folks have + perhaps not heard about XBitHack. The thing to + keep in mind is that, by doing this, you're requiring that + Apache read through every single file that it sends out to + clients, even if they don't contain any SSI directives. This + can slow things down quite a bit, and is not a good idea.

+ +

Of course, on Windows, there is no such thing as an execute + bit to set, so that limits your options a little.

+ +

In its default configuration, Apache does not send the last + modified date or content length HTTP headers on SSI pages, + because these values are difficult to calculate for dynamic + content. This can prevent your document from being cached, and + result in slower perceived client performance. There are two + ways to solve this:

+ +
    +
  1. Use the XBitHack Full configuration. This + tells Apache to determine the last modified date by looking + only at the date of the originally requested file, ignoring + the modification date of any included files.
    2. + +
  2. Use the directives provided by + mod_expires to set an explicit expiration + time on your files, thereby letting browsers and proxies + know that it is acceptable to cache them.
    3. +
+
top
+
+

Basic SSI directives

+ +

SSI directives have the following syntax:

+

+ <!--#element attribute=value attribute=value ... --> +

+ +

It is formatted like an HTML comment, so if you don't have + SSI correctly enabled, the browser will ignore it, but it will + still be visible in the HTML source. If you have SSI correctly + configured, the directive will be replaced with its + results.

+ +

The element can be one of a number of things, and we'll talk + some more about most of these in the next installment of this + series. For now, here are some examples of what you can do with + SSI

+ +

Today's date

+ +

+ <!--#echo var="DATE_LOCAL" --> +

+ +

The echo element just spits out the value of a + variable. There are a number of standard variables, which + include the whole set of environment variables that are + available to CGI programs. Also, you can define your own + variables with the set element.

+ +

If you don't like the format in which the date gets printed, + you can use the config element, with a + timefmt attribute, to modify that formatting.

+ +

+ <!--#config timefmt="%A %B %d, %Y" -->
+ Today is <!--#echo var="DATE_LOCAL" --> +

+ + +

Modification date of the file

+ +

+ This document last modified <!--#flastmod file="index.html" --> +

+ +

This element is also subject to timefmt format + configurations.

+ + +

Including the results of a CGI program

+ +

This is one of the more common uses of SSI - to output the + results of a CGI program, such as everybody's favorite, a ``hit + counter.''

+ +

+ <!--#include virtual="/cgi-bin/counter.pl" --> +

+ + +
top
+
+

Additional examples

+ + +

Following are some specific examples of things you can do in + your HTML documents with SSI.

+ +

When was this document +modified?

+ +

Earlier, we mentioned that you could use SSI to inform the + user when the document was most recently modified. However, the + actual method for doing that was left somewhat in question. The + following code, placed in your HTML document, will put such a + time stamp on your page. Of course, you will have to have SSI + correctly enabled, as discussed above.

+

+ <!--#config timefmt="%A %B %d, %Y" -->
+ This file last modified <!--#flastmod file="ssi.shtml" --> +

+ +

Of course, you will need to replace the + ssi.shtml with the actual name of the file that + you're referring to. This can be inconvenient if you're just + looking for a generic piece of code that you can paste into any + file, so you probably want to use the + LAST_MODIFIED variable instead:

+

+ <!--#config timefmt="%D" -->
+ This file last modified <!--#echo var="LAST_MODIFIED" --> +

+ +

For more details on the timefmt format, go to + your favorite search site and look for strftime. The + syntax is the same.

+ + +

Including a standard footer

+ + +

If you are managing any site that is more than a few pages, + you may find that making changes to all those pages can be a + real pain, particularly if you are trying to maintain some kind + of standard look across all those pages.

+ +

Using an include file for a header and/or a footer can + reduce the burden of these updates. You just have to make one + footer file, and then include it into each page with the + include SSI command. The include + element can determine what file to include with either the + file attribute, or the virtual + attribute. The file attribute is a file path, + relative to the current directory. That means that it + cannot be an absolute file path (starting with /), nor can it + contain ../ as part of that path. The virtual + attribute is probably more useful, and should specify a URL + relative to the document being served. It can start with a /, + but must be on the same server as the file being served.

+

+ <!--#include virtual="/footer.html" --> +

+ +

I'll frequently combine the last two things, putting a + LAST_MODIFIED directive inside a footer file to be + included. SSI directives can be contained in the included file, + and includes can be nested - that is, the included file can + include another file, and so on.

+ + +
top
+
+

What else can I config?

+ + +

In addition to being able to config the time + format, you can also config two other things.

+ +

Usually, when something goes wrong with your SSI directive, + you get the message

+

+ [an error occurred while processing this directive] +

+ +

If you want to change that message to something else, you + can do so with the errmsg attribute to the + config element:

+

+ <!--#config errmsg="[It appears that you don't know how to use SSI]" --> +

+ +

Hopefully, end users will never see this message, because + you will have resolved all the problems with your SSI + directives before your site goes live. (Right?)

+ +

And you can config the format in which file + sizes are returned with the sizefmt attribute. You + can specify bytes for a full count in bytes, or + abbrev for an abbreviated number in Kb or Mb, as + appropriate.

+
top
+
+

Executing commands

+ + +

I expect that I'll have an article some time in the coming + months about using SSI with small CGI programs. For now, here's + something else that you can do with the exec + element. You can actually have SSI execute a command using the + shell (/bin/sh, to be precise - or the DOS shell, + if you're on Win32). The following, for example, will give you + a directory listing.

+

+ <pre>
+ <!--#exec cmd="ls" -->
+ </pre> +

+ +

or, on Windows

+

+ <pre>
+ <!--#exec cmd="dir" -->
+ </pre> +

+ +

You might notice some strange formatting with this directive + on Windows, because the output from dir contains + the string ``<dir>'' in it, which confuses + browsers.

+ +

Note that this feature is exceedingly dangerous, as it will + execute whatever code happens to be embedded in the + exec tag. If you have any situation where users + can edit content on your web pages, such as with a + ``guestbook'', for example, make sure that you have this + feature disabled. You can allow SSI, but not the + exec feature, with the IncludesNOEXEC + argument to the Options directive.

+
top
+
+

Advanced SSI techniques

+ + +

In addition to spitting out content, Apache SSI gives you + the option of setting variables, and using those variables in + comparisons and conditionals.

+ +

Caveat

+ +

Most of the features discussed in this article are only + available to you if you are running Apache 1.2 or later. Of + course, if you are not running Apache 1.2 or later, you need to + upgrade immediately, if not sooner. Go on. Do it now. We'll + wait.

+ + +

Setting variables

+ +

Using the set directive, you can set variables + for later use. We'll need this later in the discussion, so + we'll talk about it here. The syntax of this is as follows:

+

+ <!--#set var="name" value="Rich" --> +

+ +

In addition to merely setting values literally like that, you + can use any other variable, including environment variables or the variables + discussed above (like LAST_MODIFIED, for example) to + give values to your variables. You will specify that something is + a variable, rather than a literal string, by using the dollar sign + ($) before the name of the variable.

+ +

<!--#set var="modified" value="$LAST_MODIFIED" --> +

+ +

To put a literal dollar sign into the value of your + variable, you need to escape the dollar sign with a + backslash.

+

+ <!--#set var="cost" value="\$100" --> +

+ +

Finally, if you want to put a variable in the midst of a + longer string, and there's a chance that the name of the + variable will run up against some other characters, and thus be + confused with those characters, you can place the name of the + variable in braces, to remove this confusion. (It's hard to + come up with a really good example of this, but hopefully + you'll get the point.)

+

+ <!--#set var="date" value="${DATE_LOCAL}_${DATE_GMT}" --> +

+ + +

Conditional expressions

+ + +

Now that we have variables, and are able to set and compare + their values, we can use them to express conditionals. This + lets SSI be a tiny programming language of sorts. + mod_include provides an if, + elif, else, endif + structure for building conditional statements. This allows you + to effectively generate multiple logical pages out of one + actual page.

+ +

The structure of this conditional construct is:

+

+ <!--#if expr="test_condition" -->
+ <!--#elif expr="test_condition" -->
+ <!--#else -->
+ <!--#endif --> +

+ +

A test_condition can be any sort of logical + comparison - either comparing values to one another, or testing + the ``truth'' of a particular value. (A given string is true if + it is nonempty.) For a full list of the comparison operators + available to you, see the mod_include + documentation. Here are some examples of how one might use this + construct.

+ +

In your configuration file, you could put the following + line:

+

+ BrowserMatchNoCase macintosh Mac
+ BrowserMatchNoCase MSIE InternetExplorer +

+ +

This will set environment variables ``Mac'' and + ``InternetExplorer'' to true, if the client is running Internet + Explorer on a Macintosh.

+ +

Then, in your SSI-enabled document, you might do the + following:

+

+ <!--#if expr="${Mac} && ${InternetExplorer}" -->
+ Apologetic text goes here
+ <!--#else -->
+ Cool JavaScript code goes here
+ <!--#endif --> +

+ +

Not that I have anything against IE on Macs - I just + struggled for a few hours last week trying to get some + JavaScript working on IE on a Mac, when it was working + everywhere else. The above was the interim workaround.

+ +

Any other variable (either ones that you define, or normal + environment variables) can be used in conditional statements. + With Apache's ability to set environment variables with the + SetEnvIf directives, and other related directives, + this functionality can let you do some pretty involved dynamic + stuff without ever resorting to CGI.

+ +
top
+
+

Conclusion

+ +

SSI is certainly not a replacement for CGI, or other + technologies used for generating dynamic web pages. But it is a + great way to add small amounts of dynamic content to pages, + without doing a lot of extra work.

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/ssi.html.ja.euc-jp b/docs/manual/howto/ssi.html.ja.euc-jp new file mode 100644 index 00000000..e1d56b97 --- /dev/null +++ b/docs/manual/howto/ssi.html.ja.euc-jp @@ -0,0 +1,481 @@ + + + +Apache ¥Á¥å¡¼¥È¥ê¥¢¥ë: Server Side Includes ÆþÌç - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë

Apache ¥Á¥å¡¼¥È¥ê¥¢¥ë: Server Side Includes ÆþÌç

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

¥µ¡¼¥Ð¥µ¥¤¥É¥¤¥ó¥¯¥ë¡¼¥É¤Ë¤è¤Ã¤Æ¡¢´û¸¤Î HTML +¥É¥­¥å¥á¥ó¥È¤ËưŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤òÄɲ乤뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
+ +
top
+
+

¤Ï¤¸¤á¤Ë

+
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

¤³¤Îµ­»ö¤Ï¡¢Ä̾ï¤Ïñ¤Ë SSI ¤È¸Æ¤Ð¤ì¤ë Server Side Includes + ¤ò°·¤¤¤Þ¤¹¡£¤³¤Îµ­»ö¤Ë¤ª¤¤¤Æ¤Ï¡¢¥µ¡¼¥Ð¤Ç¤Î SSI ¤òµö²Ä¤¹¤ë¤¿¤á¤ÎÀßÄê¤È¡¢ + ¸½ºß¤Î HTML ¥Ú¡¼¥¸¤ËưŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤ò²Ã¤¨¤ë¤¿¤á¤Î¤¤¤¯¤Ä¤«¤Î´ðËÜŪ¤Ê + SSI µ»½Ñ¤ò¾Ò²ð¤·¤Þ¤¹¡£

+ +

µ­»ö¤Î¸åȾ¤Ç¤Ï¡¢SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç SSI + ¤È¶¦¤Ë¼Â¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¾ò·ïʸ¤Î¤è¤¦¤Ê + ´öʬ¹âÅ٤ʻöÊÁ¤Ë¤Ä¤¤¤Æ½Ò¤Ù¤Æ¤¤¤Þ¤¹¡£

+ +
top
+
+

SSI ¤È¤Ï ?

+ +

SSI (Server Side Includes) ¤Ï¡¢HTML + ¥Ú¡¼¥¸Ãæ¤ËÇÛÃÖ¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤¢¤ê¡¢ + ¥µ¡¼¥Ð¤Ç¥Ú¡¼¥¸¤òÄ󶡤¹¤ë»þ¤Ëɾ²Á¤µ¤ì¤Þ¤¹¡£SSI ¤Ï¡¢CGI + ¥×¥í¥°¥é¥à¤ä¤½¤Î¾¤ÎưŪ¤Êµ»½Ñ¤ÇÁ´¤Æ¤Î¥Ú¡¼¥¸¤òÄ󶡤»¤º¤Ë¡¢ + ưŪ¤ËÀ¸À®¤µ¤ì¤¿¥³¥ó¥Æ¥ó¥Ä¤ò¸½ºß¤Î HTML ¥Ú¡¼¥¸¤Ë²Ã¤¨¤Þ¤¹¡£

+ +

¤É¤¦¤¤¤¦¾ì¹ç¤Ë SSI ¤ò»È¤¤¡¢¤É¤¦¤¤¤¦¾ì¹ç¤Ë¥×¥í¥°¥é¥à¤Ç + ¥Ú¡¼¥¸¤ò´°Á´¤ËÀ¸À®¤¹¤ë¤«¤Ï¡¢¥Ú¡¼¥¸¤Î¤¦¤Á¤É¤ÎÄøÅÙ¤¬ÀÅŪ¤Ç¤¢¤ê¡¢ + ¥Ú¡¼¥¸¤¬Ä󶡤µ¤ì¤ë¤¿¤Ó¤ËºÆ·×»»¤¹¤ëɬÍפ¬¤É¤ÎÄøÅÙ¤¢¤ë¤«¤ÇÄ̾ï¤Ï·èÄꤷ¤Þ¤¹¡£ + SSI ¤Ï¸½ºß»þ¹ï¤Î¤è¤¦¤Ê¾®¤µ¤¤¾ðÊó¤ò²Ã¤¨¤ë¤Ë¤Ï¤¦¤Ã¤Æ¤Ä¤±¤ÎÊýË¡¤Ç¤¹¡£ + ¤·¤«¤·¡¢¤½¤Î¥Ú¡¼¥¸¤Î¤Û¤È¤ó¤É¤ÎÉôʬ¤¬Ä󶡻þ¤ËÀ¸À®¤µ¤ì¤ë¾ì¹ç¤Ï¡¢ + ¾¤ÎÊýË¡¤òõ¤¹É¬Íפ¬¤¢¤ê¤Þ¤¹¡£

+
top
+
+

SSI ¤òµö²Ä¤¹¤ë¤¿¤á¤Î¥µ¡¼¥Ð¤ÎÀßÄê

+ + +

¥µ¡¼¥Ð¤Ç SSI ¤òµö²Ä¤¹¤ë¤Ë¤Ï¡¢httpd.conf + ¥Õ¥¡¥¤¥ë¤Þ¤¿¤Ï .htaccess + ¥Õ¥¡¥¤¥ë¤Ë¼¡¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹:

+

+ Options +Includes +

+ +

¤³¤Î»ØÄê¤Ï¡¢¥Õ¥¡¥¤¥ë¤ò SSI + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç²òÀϤµ¤»¤ë¤³¤È¤òµö²Ä¤¹¤ë¤È¤¤¤¦¤³¤È¤ò Apache + ¤ËÅÁ¤¨¤Þ¤¹¡£¤Û¤È¤ó¤É¤ÎÀßÄê¤Ç¤Ï¤ª¸ß¤¤¤ò¾å½ñ¤­¤Ç¤­¤ë¡¢Ê£¿ô¤Î + Options ¤¬¤¢¤ë¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤ª¤½¤é¤¯¡¢ÀßÄ꤬ºÇ¸å¤Ëɾ²Á¤µ¤ì¤ë¤³¤È¤ò + Êݾڤµ¤ì¤ë¤¿¤á¤Ë¡¢SSI ¤ò»ÈÍѤ·¤¿¤¤¥Ç¥£¥ì¥¯¥È¥ê¤Ë Options + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òŬÍѤ¹¤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£

+ +

Á´¤Æ¤Î¥Õ¥¡¥¤¥ë¤¬ SSI + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç²òÀϤµ¤ì¤ë¤È¤¤¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¤É¤Î¥Õ¥¡¥¤¥ë¤¬²òÀϤµ¤ì¤ë¤«¤ò Apache ¤ËÅÁ¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤ò¹Ô¤Ê¤¦¤Ë¤ÏÆó¤ÄÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£ + ¼¡¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤³¤È¤Ç¡¢Î㤨¤Ð .shtml + ¤Î¤è¤¦¤ÊÆÃÊ̤ʥե¡¥¤¥ë³ÈÄ¥»Ò¤ò»ý¤Ä¥Õ¥¡¥¤¥ë¤ò²òÀϤ¹¤ë¤è¤¦ + Apache ¤ËÅÁ¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+

+ AddType text/html .shtml
+ AddOutputFilter INCLUDES .shtml +

+ +

¤³¤ÎÊýË¡¤Î·çÅÀ¤Ï¡¢¤â¤·¸½ºß¤Î¥Ú¡¼¥¸¤Ë SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò²Ã¤¨¤¿¤¤¾ì¹ç¡¢ + ¤½¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¼Â¹Ô¤µ¤ì¤ë¤è¤¦¤Ë + .shtml ³ÈÄ¥»Ò¤Ë¤¹¤ë¤¿¤á¡¢¤½¤Î¥Ú¡¼¥¸¤Î̾Á°¤È¡¢ + ¤½¤Î¥Ú¡¼¥¸¤Ø¤ÎÁ´¤Æ¤Î¥ê¥ó¥¯¤òÊѹ¹¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤³¤È¤Ç¤¹¡£

+ +

¤â¤¦°ì¤Ä¤ÎÊýË¡¤Ï¡¢XBitHack + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¤¹:

+

+ XBitHack on +

+ +

XBitHack + ¤Ï¡¢¥Õ¥¡¥¤¥ë¤Î¼Â¹Ô¥Ó¥Ã¥È¤¬Î©¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢ + SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê²òÀϤ¹¤ë¤³¤È¤ò Apache ¤ËÅÁ¤¨¤Þ¤¹¡£ + ½¾¤Ã¤Æ¡¢SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¸½ºß¤Î¥Ú¡¼¥¸¤Ë²Ã¤¨¤ë¤¿¤á¤Ë¤Ï¡¢ + ¥Õ¥¡¥¤¥ë̾¤òÊѹ¹¤·¤Ê¤¯¤Æ¤â¤è¤¯¡¢Ã±¤Ë chmod + ¤ò»ÈÍѤ·¤Æ¥Õ¥¡¥¤¥ë¤ò¼Â¹Ô²Äǽ¤Ë¤¹¤ë¤À¤±¤ÇºÑ¤ß¤Þ¤¹¡£

+

+ chmod +x pagename.html +

+ +

¹Ô¤Ê¤¦¤Ù¤­¤Ç¤Ï¤Ê¤¤¤³¤È¤Ë´Ø¤¹¤ëû¤¤¥³¥á¥ó¥È¡£»þ¡¹Ã¯¤«¤¬¡¢Á´¤Æ¤Î + .html ¥Õ¥¡¥¤¥ë¤ò SSI ¤Ç²òÀϤ¹¤ë¤è¤¦ Apache ¤ËÅÁ¤¨¤ì¤Ð¡¢ + ¤ï¤¶¤ï¤¶ .shtml ¤È¤¤¤¦¥Õ¥¡¥¤¥ë̾¤Ë¤¹¤ëɬÍפ¬¤Ê¤¤¤È¤¤¤Ã¤Æ + Á¦¤á¤ë¤Î¤ò¸«¤ë¤³¤È¤Ç¤·¤ç¤¦¡£¤³¤¦¤¤¤¦¿Í¤¿¤Á¤Ï¡¢¤ª¤½¤é¤¯ + XBitHack + ¤Ë¤Ä¤¤¤Æʹ¤¤¤¿¤³¤È¤¬¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¡£ + ¤³¤ÎÊýË¡¤Ë¤Ä¤¤¤ÆÃí°Õ¤¹¤ë¤³¤È¤Ï¡¢¤¿¤È¤¨ SSI + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÁ´¤¯´Þ¤Þ¤Ê¤¤¾ì¹ç¤Ç¤â¡¢Apache ¤¬¥¯¥é¥¤¥¢¥ó¥È¤Ë + Á÷¤ëÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤òºÇ¸å¤Þ¤ÇÆɤ߹þ¤Þ¤»¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ÎÊýË¡¤Ï¤«¤Ê¤ê½èÍý¤òÃÙ¤¯¤¹¤ë¤â¤Î¤Ç¤¢¤ê¡¢Îɤ¯¤Ê¤¤¥¢¥¤¥Ç¥¢¤Ç¤¹¡£

+ +

¤â¤Á¤í¤ó¡¢Windows ¤Ç¤Ï¤½¤Î¤è¤¦¤Ê¼Â¹Ô¥Ó¥Ã¥È¤ò¥»¥Ã¥È + ¤¹¤ë¤è¤¦¤Ê¤â¤Î¤Ï¤¢¤ê¤Þ¤»¤ó¤Î¤Ç¥ª¥×¥·¥ç¥ó¤¬¾¯¤·À©¸Â¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Ç¤Ï¡¢Apache ¤Ï SSI ¥Ú¡¼¥¸¤Ë¤Ä¤¤¤ÆºÇ½ªÊѹ¹»þ¹ï¤ä + ¥³¥ó¥Æ¥ó¥Ä¤ÎŤµ¤ò HTTP ¥Ø¥Ã¥À¤ËÁ÷¤ê¤Þ¤»¤ó¡£ + ưŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤Ç¤¢¤ë¤¿¤á¡¢¤½¤ì¤é¤ÎÃͤò·×»»¤¹¤ë¤Î¤¬Æñ¤·¤¤¤«¤é¤Ç¤¹¡£ + ¤³¤Î¤¿¤á¥É¥­¥å¥á¥ó¥È¤¬¥­¥ã¥Ã¥·¥å¤µ¤ì¤Ê¤¯¤Ê¤ê¡¢ + ·ë²Ì¤È¤·¤Æ¥¯¥é¥¤¥¢¥ó¥È¤ÎÀ­Ç½¤¬ÃÙ¤¯¤Ê¤Ã¤¿¤è¤¦¤Ë´¶¤¸¤µ¤»¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ì¤ò²ò·è¤¹¤ëÊýË¡¤¬Æó¤Ä¤¢¤ê¤Þ¤¹:

+ +
    +
  1. XBitHack Full ÀßÄê¤ò»ÈÍѤ¹¤ë¡£ + ¤³¤ÎÀßÄê¤Ë¤è¤ê¡¢¤â¤È¤â¤ÈÍ׵ᤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î»þ¹ï¤ò»²¾È¤·¡¢ + Æɤ߹þ¤Þ¤ì¤ë¥Õ¥¡¥¤¥ë¤ÎÊѹ¹»þ¹ï¤ò̵»ë¤·¤ÆºÇ½ªÊѹ¹»þ¹ï¤ò·èÄꤹ¤ë¤è¤¦ + Apache ¤ËÅÁ¤¨¤Þ¤¹¡£
    2. + +
  2. mod_expires + ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¡¢ + ¥Õ¥¡¥¤¥ë¤¬Ìµ¸ú¤Ë¤Ê¤ë»þ¹ï¤òÌÀ¼¨¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢ + ¥Ö¥é¥¦¥¶¤È¥×¥í¥­¥·¤Ë¥­¥ã¥Ã¥·¥å¤¬Í­¸ú¤Ç¤¢¤ë¤³¤È¤òÄÌÃΤ·¤Þ¤¹¡£
    3. +
+
top
+
+

´ðËÜŪ¤Ê SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï°Ê²¼¤Îʸˡ¤Çµ­½Ò¤·¤Þ¤¹:

+

+ <!--#element attribute=value attribute=value ... --> +

+ +

HTML ¤Î¥³¥á¥ó¥È¤Î¤è¤¦¤Ê½ñ¼°¤ò¤·¤Æ¤¤¤ë¤Î¤Ç¡¢¤â¤· SSI + ¤òÀµ¤·¤¯Æ°ºî²Äǽ¤Ë¤·¤Ê¤±¤ì¤Ð¡¢¥Ö¥é¥¦¥¶¤Ï¤½¤ì¤ò̵»ë¤¹¤ë¤Ç¤·¤ç¤¦¡£ + ¤·¤«¤·¡¢HTML ¥½¡¼¥¹Ãæ¤Ç¤Ï¸«¤¨¤Þ¤¹¡£¤â¤· SSI ¤òÀµ¤·¤¯ÀßÄꤷ¤¿¤Ê¤é¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤½¤Î·ë²Ì¤ÈÃÖ¤­´¹¤¨¤é¤ì¤Þ¤¹¡£

+ +

element ¤Ï¤¿¤¯¤µ¤ó¤¢¤ë¤â¤Î¤«¤é°ì¤Ä»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + »ØÄê¤Ç¤­¤ë¤â¤Î¤ÎÂç¿¿ô¤Ë¤Ä¤¤¤Æ¤Ï¡¢¼¡²ó¤â¤¦¾¯¤·¾Ü¤·¤¯ÀâÌÀ¤·¤Þ¤¹¡£ + ¤³¤³¤Ç¤Ï¡¢SSI ¤Ç¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤ëÎã¤ò¤¤¤¯¤Ä¤«¼¨¤·¤Þ¤¹¡£

+ +

º£Æü¤ÎÆüÉÕ

+ +

+ <!--#echo var="DATE_LOCAL" --> +

+ +

echo Í×ÁǤÏñ¤ËÊÑ¿ô¤ÎÃͤò½ÐÎϤ·¤Þ¤¹¡£ + CGI ¥×¥í¥°¥é¥à¤ËÍøÍѲÄǽ¤Ê´Ä¶­ÊÑ¿ô¤ÎÁ´¤Æ¤Î + ¥»¥Ã¥È¤ò´Þ¤à¿¤¯¤Îɸ½àÊÑ¿ô¤¬¤¢¤ê¤Þ¤¹¡£¤Þ¤¿¡¢set + Í×ÁǤòÍѤ¤¤ë¤³¤È¤Ç¡¢Æȼ«¤ÎÊÑ¿ô¤òÄêµÁ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +

+ +

½ÐÎϤµ¤ì¤ëÆüÉդνñ¼°¤¬¹¥¤­¤Ç¤Ï¤Ê¤¤¾ì¹ç¡¢¤½¤Î½ñ¼°¤ò½¤Àµ¤¹¤ë¤¿¤á¤Ë¡¢ + config Í×ÁÇ¤Ë timefmt + °À­¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ <!--#config timefmt="%A %B %d, %Y" -->
+ Today is <!--#echo var="DATE_LOCAL" --> +

+ + +

¥Õ¥¡¥¤¥ë¤ÎÊѹ¹Æü

+ +

+ This document last modified <!--#flastmod file="index.html" --> +

+ +

¤³¤ÎÍ×ÁǤâ timefmt + ¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎÀßÄê¤Ë½¾¤¤¤Þ¤¹¡£

+ + +

CGI ¥×¥í¥°¥é¥à¤Î·ë²Ì¤ò¼è¤ê¹þ¤à

+ +

¤³¤ì¤Ï¡¢Á´¤Æ¤Î¿Í¤Î¤ªµ¤¤ËÆþ¤ê¤Ç¤¢¤ë ``¥Ò¥Ã¥È¥«¥¦¥ó¥¿'' ¤Î¤è¤¦¤Ê + CGI ¥×¥í¥°¥é¥à¤Î·ë²Ì¤ò½ÐÎϤ¹¤ë SSI + ¤Î¤è¤ê°ìÈÌŪ¤Ê»ÈÍѤΤ¦¤Á¤Î°ì¤Ä¤Ç¤¹¡£

+ +

+ <!--#include virtual="/cgi-bin/counter.pl" --> +

+ + +
top
+
+

ÄɲäÎÎã

+ + +

°Ê²¼¤Ï¡¢SSI ¤ò»ÈÍѤ·¤Æ HTML + ¥É¥­¥å¥á¥ó¥È¤Ë¤ª¤¤¤Æ¤Ç¤­¤ë¤³¤È¤Î¤¤¤¯¤Ä¤«¤ÎÆÃÊ̤ÊÎã¤Ç¤¹¡£

+ +

¤¤¤Ä¤³¤Î¥É¥­¥å¥á¥ó¥È¤Ï½¤Àµ¤µ¤ì¤¿¤Î¤« +?

+ +

Àè¤Ë¡¢¥É¥­¥å¥á¥ó¥È¤¬ºÇ¸å¤ËÊѹ¹¤µ¤ì¤¿¤Î¤Ï¤¤¤Ä¤«¤ò + ¥æ¡¼¥¶¤ËÄÌÃΤ¹¤ë¤¿¤á¤Ë SSI ¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤³¤È¤ò½Ò¤Ù¤Þ¤·¤¿¡£ + ¤·¤«¤·¤Ê¤¬¤é¡¢¼ÂºÝ¤ÎÊýË¡¤Ï¡¢¤¤¤¯¤Ö¤óÌäÂê¤Î¤Þ¤Þ¤Ë¤·¤Æ¤ª¤­¤Þ¤·¤¿¡£ + HTML ¥É¥­¥å¥á¥ó¥È¤ËÇÛÃÖ¤µ¤ì¤¿¼¡¤Î¥³¡¼¥É¤Ï¡¢¥Ú¡¼¥¸¤Ë¤½¤Î¤è¤¦¤Ê + ¥¿¥¤¥à¥¹¥¿¥ó¥×¤òÆþ¤ì¤ë¤Ç¤·¤ç¤¦¡£¤â¤Á¤í¤ó¡¢¾å½Ò¤Î¤è¤¦¤Ë¡¢ + SSI ¤òÀµ¤·¤¯Æ°ºî²Äǽ¤Ë¤·¤Æ¤ª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£

+

+ <!--#config timefmt="%A %B %d, %Y" -->
+ This file last modified <!--#flastmod file="ssi.shtml" --> +

+ +

¤â¤Á¤í¤ó¡¢ssi.shtml + ¤ÎÉôʬ¤ò¼ÂºÝ¤ÎÅö³º¥Õ¥¡¥¤¥ë̾¤ÈÃÖ¤­´¹¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤â¤·¡¢¤¢¤é¤æ¤ë¥Õ¥¡¥¤¥ë¤ËÄ¥¤ë¤³¤È¤¬¤Ç¤­¤ë°ìÈÌŪ¤Ê¥³¡¼¥É¤òõ¤·¤Æ¤¤¤ë¤Ê¤é¡¢ + ¤³¤ì¤ÏÉÔÊؤǤ¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¤ª¤½¤é¤¯¤½¤Î¾ì¹ç¤Ï¡¢ + ¤½¤¦¤¹¤ëÂå¤ï¤ê¤ËÊÑ¿ô LAST_MODIFIED + ¤ò»ÈÍѤ·¤¿¤¤¤È¹Í¤¨¤ë¤Ç¤·¤ç¤¦:

+

+ <!--#config timefmt="%D" -->
+ This file last modified <!--#echo var="LAST_MODIFIED" --> +

+ +

timefmt + ½ñ¼°¤Ë¤Ä¤¤¤Æ¤Î¤è¤ê¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¡¢¤ª¹¥¤ß¤Î¸¡º÷¥µ¥¤¥È¤Ë¹Ô¤­¡¢ + strftime ¤Ç¸¡º÷¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£Ê¸Ë¡¤ÏƱ¤¸¤Ç¤¹¡£

+ + +

ɸ½à¤Î¥Õ¥Ã¥¿¤òÁÞÆþ¤¹¤ë

+ + +

¤â¤·¿ô¥Ú¡¼¥¸¤òĶ¤¨¤ë¥Ú¡¼¥¸¤ò»ý¤Ä¥µ¥¤¥È¤ò´ÉÍý¤·¤Æ¤¤¤ë¤Ê¤é¤Ð¡¢ + Á´¥Ú¡¼¥¸¤ËÂФ·¤ÆÊѹ¹¤ò¹Ô¤Ê¤¦¤³¤È¤¬ËÜÅö¤Ë¶ìÄˤȤʤêÆÀ¤ë¤³¤È¤¬ + ʬ¤«¤ë¤Ç¤·¤ç¤¦¡£Á´¤Æ¤Î¥Ú¡¼¥¸¤ËÅϤäƤ¢¤ë¼ï¤Îɸ½àŪ¤Ê³°´Ñ¤ò + °Ý»ý¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤Ê¤é¤ÐÆäˤ½¤¦¤Ç¤·¤ç¤¦¡£

+ +

¥Ø¥Ã¥À¤ä¥Õ¥Ã¥¿ÍѤÎÁÞÆþÍÑ¥Õ¥¡¥¤¥ë¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢ + ¤³¤Î¤è¤¦¤Ê¹¹¿·¤Ë¤«¤«¤ëÉéô¤ò¸º¤é¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + °ì¤Ä¤Î¥Õ¥Ã¥¿¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¡¢¤½¤ì¤ò include + SSI ¥³¥Þ¥ó¥É¤Ç³Æ¥Ú¡¼¥¸¤ËÆþ¤ì¤ë¤À¤±¤ÇºÑ¤ß¤Þ¤¹¡£include + Í×ÁǤϡ¢file °À­¤Þ¤¿¤Ï virtual + °À­¤Î¤¤¤º¤ì¤«¤ò»ÈÍѤ·¤Æ¤É¤Î¥Õ¥¡¥¤¥ë¤òÁÞÆþ¤¹¤ë¤«¤ò·è¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + file °À­¤Ï¡¢¥«¥ì¥ó¥È¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤ÎÁêÂХѥ¹¤Ç¼¨¤µ¤ì¤¿ + ¥Õ¥¡¥¤¥ë¥Ñ¥¹¤Ç¤¹¡£ + ¤½¤ì¤Ï / ¤Ç»Ï¤Þ¤ëÀäÂÐ¥Õ¥¡¥¤¥ë¥Ñ¥¹¤Ë¤Ï¤Ç¤­¤º¡¢¤Þ¤¿¡¢¤½¤Î¥Ñ¥¹¤Î°ìÉô¤Ë ../ + ¤ò´Þ¤à¤³¤È¤¬¤Ç¤­¤Ê¤¤¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£virtual + °À­¤Ï¡¢¤ª¤½¤é¤¯¤è¤êÊØÍø¤À¤È»×¤¤¤Þ¤¹¤¬¡¢Ä󶡤¹¤ë¥É¥­¥å¥á¥ó¥È¤«¤é¤ÎÁêÂÐ + URL ¤Ç»ØÄꤹ¤Ù¤­¤Ç¤¹¡£¤½¤ì¤Ï / ¤Ç»Ï¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢ + Ä󶡤¹¤ë¥Õ¥¡¥¤¥ë¤ÈƱ¤¸¥µ¡¼¥Ð¾å¤Ë¸ºß¤·¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£

+

+ <!--#include virtual="/footer.html" --> +

+ +

»ä¤ÏºÇ¸å¤ÎÆó¤Ä¤òÁȤ߹ç¤ï¤»¤Æ¡¢LAST_MODIFIED + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¥Õ¥Ã¥¿¥Õ¥¡¥¤¥ë¤ÎÃæ¤ËÃÖ¤¯¤³¤È¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£ + SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ÁÞÆþÍѤΥե¡¥¤¥ë¤Ë´Þ¤Þ¤»¤¿¤ê¡¢ + ÁÞÆþ¥Õ¥¡¥¤¥ë¤Î¥Í¥¹¥È¤ò¤·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤¹¤Ê¤ï¤Á¡¢ + ÁÞÆþÍѤΥե¡¥¤¥ë¤Ï¾¤Î¥Õ¥¡¥¤¥ë¤òºÆµ¢Åª¤ËÁÞÆþ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ + +
top
+
+

¾¤Ë²¿¤¬ÀßÄê¤Ç¤­¤ë¤Î¤« ?

+ + +

»þ¹ï½ñ¼°¤ò config ¤ÇÀßÄê¤Ç¤­¤ë¤³¤È¤Ë²Ã¤¨¤Æ¡¢ + ¹¹¤ËÆó¤Ä config ¤ÇÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Ä̾SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç²¿¤«¤¬¤¦¤Þ¤¯¤¤¤«¤Ê¤¤¤È¤­¤Ï¡¢ + ¼¡¤Î¥á¥Ã¥»¡¼¥¸¤¬½ÐÎϤµ¤ì¤Þ¤¹¡£

+

+ [an error occurred while processing this directive] +

+ +

¤³¤Î¥á¥Ã¥»¡¼¥¸¤ò¾¤Î¤â¤Î¤Ë¤·¤¿¤¤¾ì¹ç¡¢config + Í×ÁǤΠerrmsg °À­¤ÇÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+

+ <!--#config errmsg="[It appears that you don't know how to use SSI]" --> +

+ +

¤ª¤½¤é¤¯¡¢¥¨¥ó¥É¥æ¡¼¥¶¤Ï¤³¤Î¥á¥Ã¥»¡¼¥¸¤ò·è¤·¤Æ¸«¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¤Ê¤¼¤Ê¤é¡¢¤½¤Î¥µ¥¤¥È¤¬À¸¤­¤¿¾õÂ֤ˤʤëÁ°¤Ë SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë´Ø¤¹¤ë + Á´¤Æ¤ÎÌäÂê¤ò²ò·è¤·¤Æ¤¤¤ë¤Ï¤º¤À¤«¤é¤Ç¤¹¡£(¤½¤¦¤Ç¤¹¤è¤Í?)

+ +

¤½¤·¤Æ¡¢config ¤Ë¤ª¤¤¤Æ sizefmt + °À­¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢ + ÊÖ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¥µ¥¤¥º¤Î½ñ¼°¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥Ð¥¤¥È¿ô¤Ë¤Ï bytes ¤ò¡¢Å¬Åö¤Ë Kb ¤ä Mb + ¤Ëû½Ì¤µ¤»¤ë¤Ë¤Ï abbrev ¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
top
+
+

¥³¥Þ¥ó¥É¤Î¼Â¹Ô

+ + +

º£¸å¿ô¥ö·î¤Î¤¦¤Á¤Ë¡¢¾®¤µ¤Ê CGI ¥×¥í¥°¥é¥à¤È SSI + ¤ò»ÈÍѤ¹¤ëµ­»ö¤ò½Ð¤·¤¿¤¤¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£¤³¤³¤Ç¤Ï¤½¤ì¤È¤ÏÊ̤ˡ¢ + exec Í×ÁǤˤè¤Ã¤Æ¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ + SSI ¤Ë¥·¥§¥ë (Àµ³Î¤Ë¤Ï /bin/sh¡£Win32 ¤Ê¤é¤Ð DOS ¥·¥§¥ë) + ¤ò»ÈÍѤ·¤Æ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ²¼µ­¤ÎÎã¤Ç¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥ê¥ê¥¹¥È½ÐÎϤò¹Ô¤Ê¤¤¤Þ¤¹¡£

+

+ <pre>
+ <!--#exec cmd="ls" -->
+ </pre> +

+ +

Windows ¾å¤Ç¤Ï¡¢

+

+ <pre>
+ <!--#exec cmd="dir" -->
+ </pre> +

+ +

Windows ¾å¤Ç¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤Æ¤¤¤¯¤Ä¤«¤Î´ñ̯¤Ê + ½ñ¼°¤Ëµ¤¤Å¤¯¤Ç¤·¤ç¤¦¡£¤Ê¤¼¤Ê¤é dir ¤Î½ÐÎϤ¬Ê¸»úÎó + ``<dir>'' ¤ò´Þ¤ß¡¢¥Ö¥é¥¦¥¶¤òº®Í𤵤»¤ë¤«¤é¤Ç¤¹¡£

+ +

¤³¤Îµ¡Ç½¤ÏÈó¾ï¤Ë´í¸±¤Ç¤¢¤ê¡¢¤É¤ó¤Ê¥³¡¼¥É¤Ç¤â exec + ¥¿¥°¤ËËä¤á¹þ¤Þ¤ì¤Æ¤·¤Þ¤¨¤Ð¼Â¹Ô¤¹¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£Î㤨¤Ð + `` ¥²¥¹¥È¥Ö¥Ã¥¯ '' ¤Î¤è¤¦¤Ë¡¢¤â¤·¡¢ + ¥æ¡¼¥¶¤¬¥Ú¡¼¥¸¤ÎÆâÍƤòÊÔ½¸¤Ç¤­¤ë¾õ¶·¤Ë¤¢¤ë¤Ê¤é¤Ð¡¢ + ¤³¤Îµ¡Ç½¤ò³Î¼Â¤ËÍÞÀ©¤·¤Æ¤¯¤À¤µ¤¤¡£Options + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î IncludesNOEXEC °ú¿ô¤ò»ØÄꤹ¤ë¤³¤È¤Ç¡¢ + SSI ¤Ïµö²Ä¤¹¤ë¤±¤ì¤É exec + µ¡Ç½¤Ïµö²Ä¤·¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
top
+
+

¹âÅÙ¤Ê SSI ¥Æ¥¯¥Ë¥Ã¥¯

+ + +

¥³¥ó¥Æ¥ó¥Ä¤ò½ÐÎϤ¹¤ë¤³¤È¤Ë²Ã¤¨¡¢Apache SSI ¤ÏÊÑ¿ô¤òÀßÄꤷ¡¢ + ¤½¤·¤ÆÈæ³Ó¤È¾ò·ïʬ´ô¤Ë¤½¤ÎÊÑ¿ô¤ò»ÈÍѤǤ­¤ëµ¡Ç½¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£ +

+ +

·Ù¹ð

+ +

¤³¤Îµ­»ö¤Ç½Ò¤Ù¤¿ÂçÉôʬ¤Îµ¡Ç½¤Ï¡¢Apache 1.2 + °Ê¹ß¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Î¤ßÍøÍѲÄǽ¤Ç¤¹¡£¤â¤Á¤í¤ó¡¢¤â¤· Apache 1.2 + °Ê¹ß¤ò»ÈÍѤ·¤Æ¤Ê¤¤¾ì¹ç¡¢Ä¾¤Á¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤µ¤¡¡¢º£¤½¤ì¤ò¹Ô¤Ê¤¤¤Ê¤µ¤¤¡£¤½¤ì¤Þ¤ÇÂԤäƤ¤¤Þ¤¹¡£

+ + +

ÊÑ¿ô¤òÀßÄꤹ¤ë

+ +

set ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¡¢ + ¸å¤Ç»ÈÍѤ¹¤ë¤¿¤á¤ËÊÑ¿ô¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ï¸å¤ÎÀâÌÀ¤ÇɬÍפˤʤë¤Î¤Ç¡¢¤³¤³¤Ç¤½¤ì¤Ë¤Ä¤¤¤Æ½Ò¤Ù¤Æ¤¤¤Þ¤¹¡£ + ʸˡ¤Ï°Ê²¼¤Î¤È¤ª¤ê¤Ç¤¹:

+

+ <!--#set var="name" value="Rich" --> +

+ +

¤³¤Î¤è¤¦¤Ëñ½ã¤Ëʸ»ú¤É¤ª¤ê¤ËÀßÄꤹ¤ë¤³¤È¤Ë²Ã¤¨¡¢ + ´Ä¶­ÊÑ¿ô¤ä¾åµ­¤ÎÊÑ¿ô + (Î㤨¤Ð LAST_MODIFIED ¤Î¤è¤¦¤Ê) + ¤ò´Þ¤à¾¤Î¤¢¤é¤æ¤ëÊÑ¿ô¤òÃͤòÀßÄꤹ¤ë¤Î¤Ë»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ÊÑ¿ô̾¤ÎÁ°¤Ë¥É¥ëµ­¹æ ($) ¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢ + ¤½¤ì¤¬¥ê¥Æ¥é¥ëʸ»úÎó¤Ç¤Ï¤Ê¤¯¤ÆÊÑ¿ô¤Ç¤¢¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£

+

+ <!--#set var="modified" value="$LAST_MODIFIED" --> +

+ +

¥É¥ëµ­¹æ ($) ¤òʸ»ú¤È¤·¤ÆÊÑ¿ô¤ÎÃͤËÆþ¤ì¤ë¤Ë¤Ï¡¢ + ¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Ë¤è¤Ã¤Æ¥É¥ëµ­¹æ¤ò¥¨¥¹¥±¡¼¥×¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+

+ <!--#set var="cost" value="\$100" --> +

+ +

ºÇ¸å¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢Ä¹¤¤Ê¸»úÎó¤ÎÃæ¤ËÊÑ¿ô¤òÃÖ¤­¤¿¤¤¾ì¹ç¤Ç¡¢ + ÊÑ¿ô̾¤¬Â¾¤Îʸ»ú¤È¤Ö¤Ä¤«¤ë²ÄǽÀ­¤¬¤¢¤ê¡¢ + ¤½¤ì¤é¤Îʸ»ú¤Ë¤Ä¤¤¤Æº®Í𤷤Ƥ·¤Þ¤¦¾ì¹ç¡¢¤³¤Îº®Íð¤ò¼è¤ê½ü¤¯¤¿¤á¡¢ + ÊÑ¿ô̾¤òÃæ³ç¸Ì¤Ç°Ï¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹ + (¤³¤ì¤Ë¤Ä¤¤¤Æ¤ÎÎɤ¤Îã¤ò¼¨¤¹¤Î¤ÏÆñ¤·¤¤¤Î¤Ç¤¹¤¬¡¢ + ¤ª¤½¤é¤¯Ê¬¤«¤Ã¤Æ¤¤¤¿¤À¤±¤ë¤Ç¤·¤ç¤¦)¡£ +

+

+ <!--#set var="date" value="${DATE_LOCAL}_${DATE_GMT}" --> +

+ + +

¾ò·ï¼°

+ + +

¤µ¤Æ¡¢ÊÑ¿ô¤ò»ý¤Ã¤Æ¤¤¤Æ¡¢ + ¤½¤ì¤é¤ÎÃͤòÀßÄꤷ¤ÆÈæ³Ó¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤Î¤Ç¤¹¤«¤é¡¢ + ¾ò·ï¤òɽ¤¹¤¿¤á¤Ë¤½¤ì¤é¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê + SSI ¤Ï¤¢¤ë¼ï¤Î¾®¤µ¤Ê¥×¥í¥°¥é¥ß¥ó¥°¸À¸ì¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + mod_include ¤Ï¾ò·ï¤òɽ¸½¤¹¤ë¤¿¤á¤Ë if, + elif, else, endif + ¹½Â¤¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ë¤è¤Ã¤Æ¡¢ + °ì¤Ä¤Î¼ÂºÝ¤Î¥Ú¡¼¥¸¤«¤éÊ£¿ô¤ÎÏÀÍý¥Ú¡¼¥¸¤ò¸ú²ÌŪ¤ËÀ¸À®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¾ò·ï¹½Â¤¤Ï°Ê²¼¤Î¤È¤ª¤ê¤Ç¤¹:

+

+ <!--#if expr="test_condition" -->
+ <!--#elif expr="test_condition" -->
+ <!--#else -->
+ <!--#endif --> +

+ +

test_condition + ¤Ï¤¢¤é¤æ¤ë¼ïÎà¤ÎÏÀÍýŪÈæ³Ó¤ò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ÃͤòÈæ³Ó¤·¤¿¤ê¡¢¤½¤ÎÃͤ¬ ``¿¿'' ¤«¤É¤¦¤«¤òɾ²Á¤·¤Þ¤¹ + (¶õ¤Ç¤Ê¤¤¤Ê¤éÍ¿¤¨¤é¤ì¤¿Ê¸»úÎó¤Ï¿¿¤Ç¤¹)¡£ + ÍøÍѲÄǽ¤ÊÈæ³Ó±é»»»Ò¤ÎÁ´¤Æ¤Î¥ê¥¹¥È¤Ë¤Ä¤¤¤Æ¤Ï¡¢ + mod_include ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤³¤Ç¤Ï¡¢¤³¤Î¹½Â¤¤ò¤É¤¦»ÈÍѤ¹¤ë¤«¤ÎÎã¤ò¤¤¤¯¤Ä¤«¼¨¤·¤Þ¤¹¡£

+ +

ÀßÄê¥Õ¥¡¥¤¥ë¤Ç¼¡¤Î¹Ô¤òµ­½Ò¤·¤Þ¤¹:

+

+ BrowserMatchNoCase macintosh Mac
+ BrowserMatchNoCase MSIE InternetExplorer +

+ +

¤³¤ì¤Ï¥¯¥é¥¤¥¢¥ó¥È¤¬ Macintosh + ¾å¤Ç¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥¨¥¯¥¹¥×¥í¡¼¥é¤¬Æ°¤¤¤Æ¤¤¤ë¾ì¹ç¡¢´Ä¶­ÊÑ¿ô + ``Mac'' ¤È ``InternetExplorer'' ¤ò¿¿¤ÈÀßÄꤷ¤Þ¤¹¡£

+ +

¼¡¤Ë¡¢SSI ¤¬²Äǽ¤Ë¤Ê¤Ã¤¿¥É¥­¥å¥á¥ó¥È¤Ç°Ê²¼¤ò¹Ô¤Ê¤¤¤Þ¤¹: +

+

+ <!--#if expr="${Mac} && ${InternetExplorer}" -->
+ Apologetic text goes here
+ <!--#else -->
+ Cool JavaScript code goes here
+ <!--#endif --> +

+ +

Mac ¾å¤Î IE ¤ËÂФ·¤Æ²¿¤«»×¤¦¤È¤³¤í¤¬¤¢¤ë¤ï¤±¤Ç¤¢¤ê¤Þ¤»¤ó¡£ + ¾¤Ç¤Ï¼Â¹Ô¤Ç¤­¤Æ¤¤¤ë¤¤¤¯¤Ä¤«¤Î JavaScript ¤ò Mac ¾å¤Î IE + ¤Ç¼Â¹Ô¤µ¤»¤ë¤Î¤Ë¡¢Àè½µ¿ô»þ´Ö¶ìÏ«¤·¤¿¤È¤¤¤¦¤À¤±¤Î¤³¤È¤Ç¤¹¡£ + ¾å¤ÎÎã¤Ï¤½¤Î»ÃÄêŪ¤ÊÂнèÊýË¡¤Ç¤¹¡£

+ +

¾¤Î¤É¤ó¤ÊÊÑ¿ô (¤¢¤Ê¤¿¤¬ÄêµÁ¤¹¤ë¤â¤Î¡¢ + ¤Þ¤¿¤ÏÉáÄ̤δĶ­ÊÑ¿ô¤Î¤¤¤º¤ì¤«) ¤â¡¢¾ò·ïʸ¤Ë»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + Apache ¤Ï SetEnvIf ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä¾¤Î´ØÏ¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Îµ¡Ç½¤Ë¤è¤ê¡¢CGI + ¤ËÍê¤ë¤³¤È¤Ê¤¯¤«¤Ê¤êÊ£»¨¤ÊưŪ¤Ê¤³¤È¤ò¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +
top
+
+

½ª¤ï¤ê¤Ë

+ +

SSI ¤Ï³Î¤«¤Ë CGI + ¤äưŪ¤Ê¥¦¥§¥Ö¥Ú¡¼¥¸¤òÀ¸À®¤¹¤ë¾¤Îµ»½Ñ¤ËÂå¤ï¤ë¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¤·¤«¤·¡¢¤¿¤¯¤µ¤ó¤Î;ʬ¤Êºî¶È¤ò¤»¤º¤Ë¡¢ + ¾¯Î̤ÎưŪ¤Ê¥³¥ó¥Æ¥ó¥Ä¤ò²Ã¤¨¤ë¤Ë¤Ï¤¹¤°¤ì¤¿ÊýË¡¤Ç¤¹¡£

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/howto/ssi.html.ko.euc-kr b/docs/manual/howto/ssi.html.ko.euc-kr new file mode 100644 index 00000000..27696bd2 --- /dev/null +++ b/docs/manual/howto/ssi.html.ko.euc-kr @@ -0,0 +1,426 @@ + + + +¾ÆÆÄÄ¡ ÅõÅ丮¾ó: Server Side Includes ¼Ò°³ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > How-To / Tutorials

¾ÆÆÄÄ¡ ÅõÅ丮¾ó: Server Side Includes ¼Ò°³

+
+

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

+
+ +

Server-side includes¸¦ »ç¿ëÇÏ¿© HTML ¹®¼­¿¡ µ¿ÀûÀÎ ³»¿ëÀ» +Ãß°¡ÇÒ ¼ö ÀÖ´Ù.

+
+ +
top
+
+

¼Ò°³

+
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

ÀÌ ±ÛÀº º¸Åë SSI¶ó°í ºÎ¸£´Â Server Side Includes¸¦ ¼³¸íÇÑ´Ù. + SSI°¡ °¡´ÉÇϵµ·Ï ¼­¹ö¸¦ ¼³Á¤ÇÏ´Â ¹æ¹ý°ú HTML ÆäÀÌÁö¿¡ µ¿ÀûÀÎ + ³»¿ëÀ» Ãß°¡ÇÏ´Â ±âº»ÀûÀÎ SSI »ç¿ë¹ýÀ» ¼Ò°³ÇÑ´Ù.

+ +

ÀÌ ±ÛÀÇ µÞºÎºÐÀº SSI Áö½Ã¾î Á¶°Ç¹®°ú °°Àº °í±Þ±â¹ýÀ» + ¼³¸íÇÑ´Ù.

+ +
top
+
+

SSI°¡ ¹«¾ùÀΰ¡?

+ +

SSI (Server Side Includes)´Â HTML ÆäÀÌÁö¿¡ »ç¿ëÇÏ´Â Áö½Ã¾î·Î, + ÆäÀÌÁö¸¦ ¼­ºñ½ºÇÒ¶§ ¼­¹ö°¡ ó¸®ÇÑ´Ù. SSI¸¦ »ç¿ëÇϸé CGI + ÇÁ·Î±×·¥À̳ª ´Ù¸¥ µ¿ÀûÀÎ ±â¼ú·Î ÆäÀÌÁö Àüü¸¦ ¸¸µé¾î¼­ + ¼­ºñ½ºÇÏÁö ¾Ê°íµµ HTML ÆäÀÌÁö¿¡ µ¿ÀûÀ¸·Î »ý¼ºÇÑ ³»¿ëÀ» Ãß°¡ÇÒ + ¼ö ÀÖ´Ù.

+ +

SSI¸¦ »ç¿ëÇÒÁö ¾Æ´Ï¸é ÇÁ·Î±×·¥À¸·Î ÆäÀÌÁö Àüü¸¦ »ý¼ºÇÒÁö + °áÁ¤Àº ÆäÀÌÁö¿¡¼­ Á¤ÀûÀÎ ºÎºÐÀÌ ¸¹ÀºÁö¿Í ÆäÀÌÁö¸¦ ¼­ºñ½ºÇÒ + ¶§¸¶´Ù ¾î´ÀÁ¤µµ¸¦ ´Ù½Ã °è»êÇؾßÇÒÁö¿¡ ´Þ·È´Ù. SSI´Â ÇöÀç + ½Ã°£°ú °°ÀÌ ÀûÀº Á¤º¸¸¦ Ãß°¡Çϴµ¥ ÁÁ´Ù. ±×·¯³ª ÆäÀÌÁö¸¦ + ¼­ºñ½ºÇÒ¶§ ÆäÀÌÁöÀÇ ´ëºÎºÐÀ» »ý¼ºÇØ¾ß ÇÑ´Ù¸é ´Ù¸¥ ¹æ¹ýÀ» + ã¾ÆºÁ¾ß ÇÑ´Ù.

+
top
+
+

SSI°¡ °¡´ÉÇϵµ·Ï ¼­¹ö ¼³Á¤Çϱâ

+ + +

¼­¹ö°¡ SSI¸¦ ó¸®ÇÏ·Á¸é httpd.conf ÆÄÀÏÀ̳ª + .htaccess ÆÄÀÏ¿¡¼­ ´ÙÀ½ Áö½Ã¾î¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù.

+

+ Options +Includes +

+ +

±×·¯¸é ¾ÆÆÄÄ¡´Â ÆÄÀÏ¿¡¼­ SSI Áö½Ã¾î¸¦ ó¸®ÇÑ´Ù. ¼³Á¤¿¡´Â + º¸Åë ¿©·¯ Options Áö½Ã¾î°¡ + ÀÖ°í, ÀÌ Áö½Ã¾îµéÀº ¼­·Î µ¤¾î½á¼­ ¹«È¿·Î ¸¸µé´Ù. ±×·¡¼­ + Áö½Ã¾î¸¦ ¸Ç¸¶Áö¸·¿¡ ó¸®ÇϱâÀ§ÇØ º¸Åë SSI¸¦ ¿øÇϴ ƯÁ¤ + µð·ºÅ丮¿¡¼­ Options¸¦ »ç¿ëÇÑ´Ù.

+ +

¸ðµç ÆÄÀÏ¿¡¼­ SSI Áö½Ã¾î¸¦ ó¸®ÇÏ´Â °ÍÀº ¾Æ´Ï´Ù. ¾ÆÆÄÄ¡¿¡°Ô + ¾î¶² ÆÄÀÏÀ» ó¸®ÇÒÁö ¾Ë·ÁÁà¾ß ÇÑ´Ù. µÎ°¡Áö ¹æ¹ýÀÌ ÀÖ´Ù. + Çϳª´Â ´ÙÀ½°ú °°Àº Áö½Ã¾î·Î .shtml°ú °°Àº ƯÁ¤ + ÆÄÀÏ È®ÀåÀÚ¸¦ °¡Áø ÆÄÀÏÀ» ó¸®ÇÏ´Â ¹æ¹ýÀÌ´Ù.

+

+ AddType text/html .shtml
+ AddOutputFilter INCLUDES .shtml +

+ +

ÀÌ ¹æ¹ýÀÇ ´ÜÁ¡Àº ÀÌ¹Ì ÀÖ´Â ÆäÀÌÁö¿¡ SSI Áö½Ã¾î¸¦ Ãß°¡ÇÏ´Â + °æ¿ì SSI Áö½Ã¾î¸¦ ó¸®ÇϱâÀ§ÇØ .shtml È®ÀåÀÚ¸¦ + ºÎ¿©Çϱ⶧¹®¿¡ ÆÄÀϸí°ú ÀÌ ÆäÀÌÁöÀÇ ¸ðµç ¸µÅ©¸¦ º¯°æÇØ¾ß + ÇÏ´Â Á¡ÀÌ´Ù.

+ +

´Ù¸¥ ¹æ¹ýÀº XBitHack + Áö½Ã¾î¸¦ »ç¿ëÇÏ´Â ¹æ¹ýÀÌ´Ù.

+

+ XBitHack on +

+ +

XBitHack´Â + ½ÇÇà±ÇÇÑÀÌ ÀÖ´Â ÆÄÀÏ¿¡¼­ SSI Áö½Ã¾î¸¦ ó¸®ÇÑ´Ù. ±×·¡¼­ ÀÌ¹Ì + ÀÖ´Â ÆäÀÌÁö¿¡ SSI Áö½Ã¾î¸¦ Ãß°¡ÇÑ´Ù¸é ÆÄÀϸíÀ» º¯°æÇÏÁö + ¾Ê°í chmod·Î ÆÄÀÏ¿¡ ½ÇÇà±ÇÇÑÀ» ÁÖ¸é µÈ´Ù.

+

+ chmod +x pagename.html +

+ +

ÇÏÁö ¸»¾Æ¾ß ÇÒ °Í Çϳª. °¡²û .shtml ÆÄÀÏ¸í¿¡ + °ñÄ¡¸¦ ¾ÎÁö¸»°í ¸ðµç .html ÆÄÀÏÀ» SSI ó¸®Ç϶ó°í + Ãæ°íÇÏ´Â »ç¶÷ÀÌ ÀÖ´Ù. ÀÌ »ç¶÷µéÀº ¾Æ¸¶µµ XBitHack¿¡ ´ëÇØ ¸ð¸£´Â + °Í °°´Ù. ¸í½ÉÇÒ Á¡Àº ÀÌ·¸°Ô ÇÏ¸é ¾ÆÆÄÄ¡´Â ÆÄÀÏ¿¡ SSI Áö½Ã¾î°¡ + ¾ø´õ¶óµµ Ŭ¶óÀ̾ðÆ®·Î º¸³»´Â ¸ðµç ÆÄÀÏÀ» »ìÆìºÁ¾ß ÇÑ´Ù´Â + °ÍÀÌ´Ù. ¼º´ÉÀÌ ¸Å¿ì ´À·ÁÁú ¼ö ÀÖÀ¸¸ç, ÁÁÀº »ý°¢ÀÌ ¾Æ´Ï´Ù.

+ +

¹°·Ð À©µµ¿ìÁî¿¡¼­´Â ½ÇÇà±ÇÇÑÀ̶õ °ÍÀÌ ¾ø±â¶§¹®¿¡ ÈÄÀÚ¸¦ + »ç¿ëÇÒ ¼ö ¾ø´Ù.

+ +

³»¿ëÀÌ µ¿ÀûÀÌ¿©¼­ °è»êÇϱ⠾î·Æ±â¶§¹®¿¡ ¾ÆÆÄÄ¡ ±âº» ¼³Á¤Àº + SSI ÆäÀÌÁöÀÇ ÃÖ±Ù¼öÁ¤ÀÏ°ú content length HTTP Çì´õ¸¦ º¸³»Áö + ¾Ê´Â´Ù. ±×·¡¼­ ¹®¼­¸¦ ij½¬ÇÏÁö ¸øÇÏ°í Ŭ¶óÀ̾ðÆ®°¡ ´À³¢´Â + ¼º´ÉÀÌ ¶³¾îÁø´Ù. µÎ°¡Áö ÇØ°á¹æ¹ýÀÌ ÀÖ´Ù.

+ +
    +
  1. XBitHack Full ¼³Á¤Àº »ç¿ëÇÑ´Ù. ±×·¯¸é + ¾ÆÆÄÄ¡´Â Æ÷ÇÔÇÏ´Â(include) ÆÄÀϵéÀÇ ¼öÁ¤ÀÏÀº ¹«½ÃÇÑü + ¿ø·¡ ¿äûÇÑ ÆÄÀÏÀÇ ³¯Â¥¸¸ º¸°í ÃÖ±Ù¼öÁ¤ÀÏÀ» ¾Ë¾Æ³½´Ù.
    2. + +
  2. mod_expires¿¡ ÀÖ´Â Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + ÆÄÀÏ¿¡ Á÷Á¢ ¸¸±âÀÏÀ» ¼³Á¤ÇÏ¸é ºê¶ó¿ìÀú¿Í ÇÁ·Ï½Ã°¡ ¹®¼­¸¦ + ij½¬ÇÒ ¼ö ÀÖ´Ù.
    3. +
+
top
+
+

±âº» SSI Áö½Ã¾î

+ +

SSI Áö½Ã¾îÀÇ »ç¿ë¹ýÀº ´ÙÀ½°ú °°´Ù.

+

+ <!--#element attribute=value attribute=value ... --> +

+ +

HTML ÁÖ¼®°°ÀÌ »ý°å±â¶§¹®¿¡ SSI ±â´ÉÀ» °¡µ¿ÇÏÁö ¾Ê¾Æµµ + HTML ¼Ò½º¿¡´Â ³ª¿ÀÁö¸¸ ºê¶ó¿ìÀú´Â ¹«½ÃÇÑ´Ù. SSI¸¦ ¿Ã¹Ù·Î + ¼³Á¤Çϸé Áö½Ã¾î¸¦ °á°ú°ªÀ¸·Î ¹Ù²Û´Ù.

+ +

element´Â ´ÙÀ½Áß Çϳª´Ù. ´ÙÀ½ ȸ¿¡ ´õ ÀÚ¼¼È÷ ¼³¸íÇÒ °ÍÀÌ´Ù. + Áö±ÝÀº SSI·Î ÇÒ ¼ö ÀÖ´Â ¸î°¡Áö ¿¹¸¦ º¸ÀδÙ

+ +

¿À´Ã ³¯Â¥

+ +

+ <!--#echo var="DATE_LOCAL" --> +

+ +

echo element´Â º¯¼ö°ªÀ» ±×´ë·Î Ãâ·ÂÇÑ´Ù. + CGI ÇÁ·Î±×·¥¿¡ Á¦°øÇϴ ȯ°æº¯¼öµé ¿Ü¿¡µµ ¿©·¯ Ç¥ÁØ º¯¼ö°¡ + ÀÖ´Ù. ¶Ç, set element¸¦ »ç¿ëÇÏ¿© Á÷Á¢ º¯¼ö¸¦ + Á¤ÀÇÇÒ ¼öµµ ÀÖ´Ù.

+ +

³¯Â¥ Ãâ·Â Çü½ÄÀÌ ¸¶À½¿¡ µéÁö ¾Ê´Â´Ù¸é, ´ÙÀ½°ú °°ÀÌ + config elementÀÇ timefmt attribute¸¦ + »ç¿ëÇÑ´Ù.

+ +

+ <!--#config timefmt="%A %B %d, %Y" -->
+ Today is <!--#echo var="DATE_LOCAL" --> +

+ + +

ÆÄÀÏÀÇ ¼öÁ¤ÀÏ

+ +

+ ÀÌ ¹®¼­´Â <!--#flastmod file="index.html" -->¿¡ ¸¶Áö¸·À¸·Î ¼öÁ¤µÇ¾ú´Ù +

+ +

ÀÌ elementµµ timefmt Çü½Ä ¼³Á¤¿¡ ´Þ·È´Ù.

+ + +

CGI ÇÁ·Î±×·¥ °á°ú¸¦ Æ÷ÇÔÇϱâ

+ +

ÀϹÝÀûÀÎ SSI »ç¿ë¹ýÁß Çϳª·Î, ¸¹ÀÌµé ¾Ö¿ëÇÏ´Â ``¹æ¹®¼ö + Ä«¿îÅÍ'' °°Àº CGI ÇÁ·Î±×·¥ °á°ú¸¦ Ãâ·ÂÇÑ´Ù.

+ +

+ <!--#include virtual="/cgi-bin/counter.pl" --> +

+ + +
top
+
+

Ãß°¡ ¿¹Á¦

+ + +

´ÙÀ½Àº HTML ¹®¼­¿¡ »ç¿ëÇÒ ¼ö ÀÖ´Â ¸î°¡Áö SSI ¿¹Á¦´Ù.

+ +

ÀÌ ¹®¼­°¡ ¾ðÁ¦ ¸¶Áö¸·À¸·Î +¼öÁ¤µÇ¾ú³ª?

+ +

¾Õ¿¡¼­ SSI¸¦ »ç¿ëÇÏ¿© »ç¿ëÀÚ¿¡°Ô ¹®¼­ÀÇ ÃÖ±Ù¼öÁ¤ÀÏÀ» + ¾Ë¸± ¼ö ÀÖ´Ù°í ¸»Çß´Ù. ±×·¯³ª ½ÇÁ¦ ¹æ¹ýÀº ¾Ë·ÁÁÖÁö ¾Ê¾Ò´Ù. + ´ÙÀ½ Äڵ带 HTML ¹®¼­¿¡ »ç¿ëÇϸé ÆäÀÌÁö¿¡ ½Ã°£ ±â·ÏÀ» ³²±ä´Ù. + ¹°·Ð À§¿¡¼­ ¼³¸íÇÑ´ë·Î SSI°¡ ¿Ã¹Ù·Î ÀÛµ¿ÇØ¾ß ÇÑ´Ù.

+

+ <!--#config timefmt="%A %B %d, %Y" -->
+ ÀÌ ¹®¼­´Â <!--#flastmod file="ssi.shtml" -->¿¡ ¸¶Áö¸·À¸·Î ¼öÁ¤µÇ¾ú´Ù; +

+ +

¹°·Ð ssi.shtml´ë½Å ¿øÇÏ´Â ½ÇÁ¦ ÆÄÀϸíÀ» + »ç¿ëÇÑ´Ù. ¾Æ¹« ÆäÀÌÁö¿¡¶óµµ ºÙ¿©³ÖÀ» ¼ö ÀÖ´Â ¹ü¿ëÄڵ带 + ¿øÇÑ´Ù¸é, ÆÄÀÏ¸í ´ë½Å LAST_MODIFIED º¯¼ö¸¦ + »ç¿ëÇÑ´Ù.

+

+ <!--#config timefmt="%D" -->
+ This file last modified <!--#echo var="LAST_MODIFIED" --> +

+ +

timefmt Çü½Ä¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ Á¤º¸´Â °Ë»ö¿£Áø¿¡¼­ + strftimeÀ» ã¾ÆºÁ¶ó. ¹®¹ýÀº °°´Ù.

+ + +

Ç¥ÁØ ÆäÀÌÁö ÇÏ´ÜÀ» Æ÷ÇÔÇϱâ

+ + +

¿©·¯ ÆäÀÌÁö°¡ ÀÖ´Â »çÀÌÆ®¸¦ °ü¸®ÇÑ´Ù¸é ÆäÀÌÁö Àüü¸¦ + ¼öÁ¤ÇÏ´Â °ÍÀº, ƯÈ÷ ÆäÀÌÁöµéÀÌ Ç¥ÁØ ¿Ü°üÀ» °¡Áöµµ·Ï ¼öÁ¤ÇÏ´Â + °ÍÀº Á¤¸»·Î ±«·Ó´Ù.

+ +

ÆäÀÌÁö »ó´Ü(header)°ú ÇÏ´Ü(footer)À» ÆÄÀÏ·Î Æ÷ÇÔÇÏ¿© + ÀÌ·± ¼öÁ¤ÀÇ ºÎ´ãÀ» ´ú ¼ö ÀÖ´Ù. ¸ðµç ÆäÀÌÁö¿¡¼­ + include SSI ¸í·É¾î¸¦ »ç¿ëÇÏ¿© ÆäÀÌÁö ÇÏ´Ü ÆÄÀÏ + Çϳª¸¦ Æ÷ÇÔÇÏ¸é µÈ´Ù. include elementÀÇ + file attribute³ª virtual attribute·Î + Æ÷ÇÔÇÒ ÆÄÀÏÀ» ÁöÁ¤ÇÑ´Ù. file attribute´Â ÇöÀç + µð·ºÅ丮¿¡ »ó´ëÀûÀÎ ÆÄÀÏ°æ·Î´Ù. Áï, (/·Î ½ÃÀÛÇÏ´Â) + Àý´ëÆÄÀÏ°æ·Î³ª °æ·Î ¾È¿¡ ../¸¦ »ç¿ëÇÒ ¼ö ¾ø´Ù. ¾Æ¸¶µµ ¼­ºñ½ºÇÏ´Â + ¹®¼­ÀÇ »ó´ë URLÀ» ÁöÁ¤ÇÒ ¼ö ÀÖ´Â virtual attribute°¡ + ´õ À¯¿ëÇÒ °ÍÀÌ´Ù. °æ·Î¸¦ /·Î ½ÃÀÛÇÒ ¼ö ÀÖÁö¸¸, Æ÷ÇÔÇÏ·Á´Â + ÆÄÀÏÀÌ ¼­ºñ½ºÇÏ´Â ÆÄÀÏ°ú °°Àº ¼­¹ö¿¡ ÀÖ¾î¾ß ÇÑ´Ù.

+

+ <!--#include virtual="/footer.html" --> +

+ +

³ª´Â º¸Åë ÀÌ µÎ°¡Áö¸¦ ÇÕÃļ­ Æ÷ÇÔÇÒ ÆäÀÌÁö ÇÏ´Ü ÆÄÀÏ¿¡ + LAST_MODIFIED Áö½Ã¾î¸¦ ³Ö´Â´Ù. Æ÷ÇÔÇÏ·Á´Â ÆÄÀÏ¿¡µµ + SSI Áö½Ã¾î°¡ ³ª¿Ã ¼ö ÀÖÀ¸¸ç, ÀÌ·¸°Ô Æ÷ÇÔÇÑ ÆÄÀÏÀÌ ´Ù¸¥ ÆÄÀÏÀ» + Æ÷ÇÔÇÏ´Â ½ÄÀ¸·Î ¿©·¯¹ø °è¼Ó Æ÷ÇÔÇÒ ¼öµµ ÀÖ´Ù.

+ + +
top
+
+

ÀÌ¿Ü¿¡ ¼³Á¤ÇÒ ¼ö ÀÖ´Â °ÍÀº?

+ + +

½Ã°£ Çü½Ä config(¼³Á¤) ¿Ü¿¡ µÎ°¡Áö¸¦ ´õ + config(¼³Á¤)ÇÒ ¼ö ÀÖ´Ù.

+ +

º¸Åë SSI Áö½Ã¾î°¡ À߸øµÇ¸é ´ÙÀ½°ú °°Àº ¹®±¸°¡ ³ª¿Â´Ù

+

+ [an error occurred while processing this directive] +

+ +

ÀÌ ¹®±¸¸¦ º¯°æÇÏ°í ½Í´Ù¸é config elementÀÇ + errmsg attribute¸¦ »ç¿ëÇÏ¿© º¯°æÇÑ´Ù.

+

+ <!--#config errmsg="[It appears that you don't know how to use SSI]" --> +

+ +

»çÀÌÆ®¸¦ ¼­ºñ½ºÇϱâ Àü¿¡ ¸ðµç SSI Áö½Ã¾î ¹®Á¦¸¦ ÇØ°áÇÏ¿© + »ç¿ëÀÚ°¡ ÀÌ·± ¹®±¸¸¦ º¸Áö ¾Ê±æ ¹Ù¶õ´Ù. (±×·¸Áö?)

+ +

±×¸®°í sizefmt attribute°¡ ¹ÝȯÇÏ´Â ÆÄÀÏÅ©±â + Çü½ÄÀ» config(¼³Á¤)ÇÒ ¼ö ÀÖ´Ù. ¹ÙÀÌÆ®·Î Å©±â¸¦ + º¸¿©ÁÖ·Á¸é bytes, ÀûÀýÈ÷ Kb³ª Mb·Î Å©±â¸¦ + º¸¿©ÁÖ·Á¸é abbrev¸¦ »ç¿ëÇÑ´Ù.

+
top
+
+

¸í·É¾î ½ÇÇàÇϱâ

+ + +

³ª´Â ´ÙÀ½ ´Þ¿¡ ÀÛÀº CGI ÇÁ·Î±×·¥°ú SSI¸¦ °°ÀÌ »ç¿ëÇÏ´Â + ±ÛÀ» ¾µ ¿¹Á¤ÀÌ´Ù. Áö±ÝÀº exec element·Î ÇÒ + ¼ö ÀÖ´Â ´Ù¸¥ °ÍµéÀ» ¼³¸íÇÒ °ÍÀÌ´Ù. SSI´Â ½ÇÁ¦ ½©À» (Á¤È®È÷´Â + /bin/sh³ª Win32¸¦ »ç¿ëÇÑ´Ù¸é DOS ½©) »ç¿ëÇÏ¿© + ¸í·É¾î¸¦ ½ÇÇàÇÑ´Ù. ¿¹¸¦ µé¾î, ´ÙÀ½Àº µð·ºÅ丮 ¸ñ·ÏÀ» º¸¿©ÁØ´Ù.

+

+ <pre>
+ <!--#exec cmd="ls" -->
+ </pre> +

+ +

or, on Windows

+

+ <pre>
+ <!--#exec cmd="dir" -->
+ </pre> +

+ +

dir Ãâ·Â¿¡ ºê¶ó¿ìÀú°¡ È¥µ¿ÇÒ + ``<dir>'' ¹®ÀÚ¿­ÀÌ Æ÷ÇÔµÇÀֱ⶧¹®¿¡, + À©µµ¿ìÁî¿¡¼­ ÀÌ Áö½Ã¾î¸¦ »ç¿ëÇÏ¸é °á°ú°¡ Á¶±Ý ÀÌ»óÇÒ °ÍÀÌ´Ù.

+ +

ÀÌ ±â´ÉÀº exec ű׿¡ »ç¿ëÇÑ ¾î¶² ¸í·É¾î¶óµµ + ½ÇÇàÇÒ ¼ö Àֱ⶧¹®¿¡ ¸Å¿ì À§ÇèÇÏ´Ù. ``¹æ¸í·Ï''°ú °°ÀÌ »ç¿ëÀÚ°¡ + À¥ÆäÀÌÁö ³»¿ëÀ» ¼öÁ¤ÇÒ ¼ö Àִ ȯ°æÀ̶ó¸é, ÀÌ ±â´ÉÀ» Àý´ë·Î + »ç¿ëÇؼ± ¾ÈµÈ´Ù. Options Áö½Ã¾î¿¡ + IncludesNOEXEC ¾Æ±Ô¸ÕÆ®¸¦ »ç¿ëÇÏ¿© SSI¸¦ Çã¿ëÇÏÁö¸¸ + exec ±â´ÉÀ» ¸·À» ¼ö ÀÖ´Ù.

+
top
+
+

°í±Þ SSI ±â¹ý

+ + +

³»¿ëÀ» Ãâ·ÂÇÏ´Â ±â´É ¿Ü¿¡ ¾ÆÆÄÄ¡ SSI´Â º¯¼ö ¼³Á¤ÀÌ °¡´ÉÇÏ°í, + ºñ±³¹®°ú Á¶°Ç¹®¿¡ ÀÌ º¯¼ö¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

°æ°í

+ +

ÀÌ ±Û¿¡¼­ ¼³¸íÇÏ´Â ´ëºÎºÐÀÇ ±â´ÉÀº ¾ÆÆÄÄ¡ 1.2 ÀÌÈĺÎÅÍ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¹°·Ð, ¾ÆÆÄÄ¡ 1.2 ÀÌ»óÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù¸é + ¾Æ¸¶µµ »¡¸® ¾÷±×·¹À̵åÇØ¾ß ÇÑ´Ù. Çضó. Áö±Ý Çضó. ±â´Ù¸± + °ÍÀÌ´Ù.

+ + +

º¯¼ö ¼³Á¤

+ +

set Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ³ªÁß¿¡ »ç¿ëÇÒ º¯¼ö¸¦ + ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ¾ÕÀ¸·Î º¯¼ö°¡ ÇÊ¿äÇϱ⶧¹®¿¡ ¸ÕÀú ¼³¸íÇÑ´Ù. + ¹®¹ýÀº ´ÙÀ½°ú °°´Ù.

+

+ <!--#set var="name" value="Rich" --> +

+ +

´ÙÀ½°ú °°ÀÌ °ªÀ» ¹®ÀÚ±×´ë·Î ¼³Á¤ÇÏÁö ¾Ê°í ȯ°æº¯¼ö³ª À§¿¡¼­ ¼³¸íÇÑ º¯¼ö(¿¹¸¦ + µé¾î, LAST_MODIFIED)¿Í °°ÀÌ ´Ù¸¥ º¯¼ö¸¦ »ç¿ëÇÏ¿© + º¯¼ö°ªÀ» ¼³Á¤ÇÒ ¼öµµ ÀÖ´Ù. À̶§ º¯¼ö¸í ¾Õ¿¡ ´Þ·¯ Ç¥½Ã($)¸¦ + ºÙ¿©¼­ ¹®ÀÚ¿­ÀÌ ¾Æ´Ñ º¯¼öÀÓÀ» Ç¥½ÃÇÑ´Ù.

+ +

<!--#set var="modified" value="$LAST_MODIFIED" --> +

+ +

º¯¼ö°ª¿¡ ´Þ·¯ ¹®ÀÚ¸¦ ±×´ë·Î ÀÔ·ÂÇÏ·Á¸é ´Þ·¯ Ç¥½Ã ¾Õ¿¡ + ¹é½½·¡½¬¸¦ »ç¿ëÇÑ´Ù.

+

+ <!--#set var="cost" value="\$100" --> +

+ +

¸¶Áö¸·À¸·Î ±ä ¹®ÀÚ¿­ Áß°£¿¡ º¯¼ö¸¦ »ç¿ëÇϴµ¥ µÚ¿¡ ÀÖ´Â + ¹®ÀÚµµ º¯¼ö¸íÀ¸·Î ¿ÀÀÎÇÏ¿© È¥µ¿µÇ´Â °æ¿ì, º¯¼ö¸íÀ» ´ë°ýÈ£·Î + ¹­¾î¼­ È®½ÇÈ÷ ÇÑ´Ù. (ÁÁÀº ¿¹¸¦ ã±â ÈûµéÁö¸¸, ¹«½¼ ¸»ÀÎÁö + ÀÌÇØÇÏ±æ ¹Ù¶õ´Ù.)

+

+ <!--#set var="date" value="${DATE_LOCAL}_${DATE_GMT}" --> +

+ + +

Á¶°Ç Ç¥Çö½Ä

+ + +

º¯¼ö¸¦ ¼³Á¤ÇÏ°í ºñ±³ÇÒ ¼ö ÀÖÀ¸´Ï Á¶°Ç¹®ÀÌ °¡´ÉÇÏ´Ù. ÀÌÁ¦ + SSI°¡ ÀÏÁ¾ÀÇ °£´ÜÇÑ ÇÁ·Î±×·¡¹Ö¾ð¾î°¡ µÈ´Ù. + mod_include´Â Á¶°Ç¹®À» ¸¸µå´Â if, + elif, else, endif + ±¸Á¶¸¦ Á¦°øÇÑ´Ù. ½ÇÁ¦ ÇÑ ÆäÀÌÁö·Î ¿©·¯ ³í¸®ÀûÀÎ ÆäÀÌÁö¸¦ + ¸¸µé ¼ö ÀÖ´Ù.

+ +

Á¶°Ç¹® ±¸Á¶´Â ´ÙÀ½°ú °°´Ù.

+

+ <!--#if expr="test_condition" -->
+ <!--#elif expr="test_condition" -->
+ <!--#else -->
+ <!--#endif --> +

+ +

test_condition¿¡´Â ¾î¶² ³í¸®ºñ±³¶óµµ »ç¿ëÇÒ + ¼ö ÀÖ´Ù. °ªÀ» ´Ù¸¥ °ª°ú ºñ±³Çϰųª, ƯÁ¤ °ªÀÌ ``Âü''ÀÎÁö + °Ë»çÇÑ´Ù. (¹®ÀÚ¿­ÀÌ ºñ¾îÀÖÁö ¾ÊÀ¸¸é ÂüÀÌ´Ù.) »ç¿ë°¡´ÉÇÑ + ºñ±³ ¿¬»êÀÚ¸¦ ¸ðµÎ º¸·Á¸é, mod_include + ¹®¼­¸¦ Âü°íÇ϶ó. ´ÙÀ½Àº Á¶°Ç¹®À» »ç¿ëÇÑ ¸î°¡Áö ¿¹Á¦´Ù.

+ +

¼³Á¤ÆÄÀÏ¿¡ ´ÙÀ½ ÁÙÀ» Ãß°¡ÇÑ´Ù.

+

+ BrowserMatchNoCase macintosh Mac
+ BrowserMatchNoCase MSIE InternetExplorer +

+ +

Ŭ¶óÀ̾ðÆ®°¡ ¸ÆŲÅä½Ã¿¡¼­ ½ÇÇàÇÏ´Â Internet Explorer¶ó¸é + ȯ°æº¯¼ö ``Mac''°ú ``InternetExplorer'' ¸ðµÎ ÂüÀ¸·Î ¼³Á¤ÇÑ´Ù.

+ +

±×¸®°í SSI ¹®¼­¿¡ ´ÙÀ½°ú °°ÀÌ Àû´Â´Ù.

+

+ <!--#if expr="${Mac} && ${InternetExplorer}" -->
+ ¿©±â¿¡ »ç°ú¹®°¡ ³ª¿Â´Ù
+ <!--#else -->
+ ¿©±â¿¡ ¸ÚÁø JavaScript Äڵ尡 ³ª¿Â´Ù
+ <!--#endif --> +

+ +

³»°¡ ¸ÅŲÅä½Ã IE¿¡ ¹Ý°¨ÀÌ ÀÖ´Â °ÍÀº ¾Æ´Ï´Ù. ³ª´Â ´ÜÁö + Àú¹øÁÖ¿¡ ´Ù¸¥ °÷¿¡¼­´Â ¹®Á¦°¡ ¾ø´Â JavaScript Äڵ尡 ¸ÅŲÅä½Ã + IE¿¡¼­´Â µ¿ÀÛÇÏÁö ¾Ê¾Æ¼­ ¸î½Ã°£À» °í»ýÇß´Ù. À§´Â Àӽà + ÇØ°áÃ¥ÀÌ´Ù.

+ +

(Á÷Á¢ Á¤ÀÇÇÏ¿´°Ç ÀÏ¹Ý È¯°æº¯¼öÀÌ°Ç) ¾î¶² º¯¼ö¶óµµ Á¶°Ç¹®¿¡ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¾Æ¶óÄ¡´Â SetEnvIf³ª ´Ù¸¥ °ü·Ã + Áö½Ã¾î·Î ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÒ ¼ö Àֱ⶧¹®¿¡ CGI ¾øÀ̵µ ¸ÚÁö°Ô + µ¿ÀûÀÎ ³»¿ëÀ» ¸¸µé ¼ö ÀÖ´Ù.

+ +
top
+
+

°á·Ð

+ +

SSI´Â È®½ÇÈ÷ CGI³ª µ¿ÀûÀÎ À¥ÆäÀÌÁö¸¦ »ý¼ºÇÏ´Â ´Ù¸¥ ±â¼úÀ» + ´ëüÇÒ ¼ö ¾ø´Ù. ±×·¯³ª ¸¹Àº Ãß°¡ ÀÛ¾÷¾øÀÌ ÆäÀÌÁö¿¡ µ¿ÀûÀÎ + ³»¿ëÀ» Á¶±Ý Ãß°¡Çϱ⿡´Â ÈǸ¢ÇÑ ¹æ¹ýÀÌ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/images/apache_header.gif b/docs/manual/images/apache_header.gif new file mode 100644 index 00000000..260e421b Binary files /dev/null and b/docs/manual/images/apache_header.gif differ diff --git a/docs/manual/images/caching_fig1.gif b/docs/manual/images/caching_fig1.gif new file mode 100644 index 00000000..456da36f Binary files /dev/null and b/docs/manual/images/caching_fig1.gif differ diff --git a/docs/manual/images/caching_fig1.png b/docs/manual/images/caching_fig1.png new file mode 100644 index 00000000..9f824d65 Binary files /dev/null and b/docs/manual/images/caching_fig1.png differ diff --git a/docs/manual/images/custom_errordocs.png b/docs/manual/images/custom_errordocs.png new file mode 100644 index 00000000..f2b94907 Binary files /dev/null and b/docs/manual/images/custom_errordocs.png differ diff --git a/docs/manual/images/down.gif b/docs/manual/images/down.gif new file mode 100644 index 00000000..2194532b Binary files /dev/null and b/docs/manual/images/down.gif differ diff --git a/docs/manual/images/favicon.ico b/docs/manual/images/favicon.ico new file mode 100644 index 00000000..bfb4f63a Binary files /dev/null and b/docs/manual/images/favicon.ico differ diff --git a/docs/manual/images/feather.gif b/docs/manual/images/feather.gif new file mode 100644 index 00000000..441e3dd1 Binary files /dev/null and b/docs/manual/images/feather.gif differ diff --git a/docs/manual/images/feather.png b/docs/manual/images/feather.png new file mode 100644 index 00000000..5dd0dd10 Binary files /dev/null and b/docs/manual/images/feather.png differ diff --git a/docs/manual/images/filter_arch.png b/docs/manual/images/filter_arch.png new file mode 100644 index 00000000..de021af5 Binary files /dev/null and b/docs/manual/images/filter_arch.png differ diff --git a/docs/manual/images/home.gif b/docs/manual/images/home.gif new file mode 100644 index 00000000..11299c1c Binary files /dev/null and b/docs/manual/images/home.gif differ diff --git a/docs/manual/images/index.gif b/docs/manual/images/index.gif new file mode 100644 index 00000000..741c8939 Binary files /dev/null and b/docs/manual/images/index.gif differ diff --git a/docs/manual/images/left.gif b/docs/manual/images/left.gif new file mode 100644 index 00000000..2be39310 Binary files /dev/null and b/docs/manual/images/left.gif differ diff --git a/docs/manual/images/mod_filter_new.gif b/docs/manual/images/mod_filter_new.gif new file mode 100644 index 00000000..15660785 Binary files /dev/null and b/docs/manual/images/mod_filter_new.gif differ diff --git a/docs/manual/images/mod_filter_new.png b/docs/manual/images/mod_filter_new.png new file mode 100644 index 00000000..ad2cc735 Binary files /dev/null and b/docs/manual/images/mod_filter_new.png differ diff --git a/docs/manual/images/mod_filter_old.gif b/docs/manual/images/mod_filter_old.gif new file mode 100644 index 00000000..d9a9ede2 Binary files /dev/null and b/docs/manual/images/mod_filter_old.gif differ diff --git a/docs/manual/images/mod_rewrite_fig1.gif b/docs/manual/images/mod_rewrite_fig1.gif new file mode 100644 index 00000000..664ac1e7 Binary files /dev/null and b/docs/manual/images/mod_rewrite_fig1.gif differ diff --git a/docs/manual/images/mod_rewrite_fig1.png b/docs/manual/images/mod_rewrite_fig1.png new file mode 100644 index 00000000..f914f681 Binary files /dev/null and b/docs/manual/images/mod_rewrite_fig1.png differ diff --git a/docs/manual/images/mod_rewrite_fig2.gif b/docs/manual/images/mod_rewrite_fig2.gif new file mode 100644 index 00000000..3ea8cb65 Binary files /dev/null and b/docs/manual/images/mod_rewrite_fig2.gif differ diff --git a/docs/manual/images/mod_rewrite_fig2.png b/docs/manual/images/mod_rewrite_fig2.png new file mode 100644 index 00000000..90dbf544 Binary files /dev/null and b/docs/manual/images/mod_rewrite_fig2.png differ diff --git a/docs/manual/images/pixel.gif b/docs/manual/images/pixel.gif new file mode 100644 index 00000000..c0801475 Binary files /dev/null and b/docs/manual/images/pixel.gif differ diff --git a/docs/manual/images/right.gif b/docs/manual/images/right.gif new file mode 100644 index 00000000..f27eb970 Binary files /dev/null and b/docs/manual/images/right.gif differ diff --git a/docs/manual/images/ssl_intro_fig1.gif b/docs/manual/images/ssl_intro_fig1.gif new file mode 100644 index 00000000..3c209864 Binary files /dev/null and b/docs/manual/images/ssl_intro_fig1.gif differ diff --git a/docs/manual/images/ssl_intro_fig1.png b/docs/manual/images/ssl_intro_fig1.png new file mode 100644 index 00000000..e599d239 Binary files /dev/null and b/docs/manual/images/ssl_intro_fig1.png differ diff --git a/docs/manual/images/ssl_intro_fig2.gif b/docs/manual/images/ssl_intro_fig2.gif new file mode 100644 index 00000000..26b295a6 Binary files /dev/null and b/docs/manual/images/ssl_intro_fig2.gif differ diff --git a/docs/manual/images/ssl_intro_fig2.png b/docs/manual/images/ssl_intro_fig2.png new file mode 100644 index 00000000..c540f48a Binary files /dev/null and b/docs/manual/images/ssl_intro_fig2.png differ diff --git a/docs/manual/images/ssl_intro_fig3.gif b/docs/manual/images/ssl_intro_fig3.gif new file mode 100644 index 00000000..00a975b5 Binary files /dev/null and b/docs/manual/images/ssl_intro_fig3.gif differ diff --git a/docs/manual/images/ssl_intro_fig3.png b/docs/manual/images/ssl_intro_fig3.png new file mode 100644 index 00000000..d71a1cba Binary files /dev/null and b/docs/manual/images/ssl_intro_fig3.png differ diff --git a/docs/manual/images/sub.gif b/docs/manual/images/sub.gif new file mode 100644 index 00000000..93061c5a Binary files /dev/null and b/docs/manual/images/sub.gif differ diff --git a/docs/manual/images/up.gif b/docs/manual/images/up.gif new file mode 100644 index 00000000..5afcbe2d Binary files /dev/null and b/docs/manual/images/up.gif differ diff --git a/docs/manual/index.html b/docs/manual/index.html new file mode 100644 index 00000000..90fa64a5 --- /dev/null +++ b/docs/manual/index.html @@ -0,0 +1,27 @@ +URI: index.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: index.html.pt-br +Content-Language: pt-br +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/index.html.de b/docs/manual/index.html.de new file mode 100644 index 00000000..0fc33d0b --- /dev/null +++ b/docs/manual/index.html.de @@ -0,0 +1,104 @@ + + + +Dokumentation zum Apache HTTP Server Version +2.2 - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation
+

Dokumentation zum Apache HTTP Server Version +2.2

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+

+

Hinweise zur Version

+ +

Bedienungsanleitung

+ +

Benutzerhandbuch

+ +

Praxis / Anleitungen

+ +

Plattform-spezifische Anmerkungen

+ +

Weitere Themen

+ +
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/index.html.en b/docs/manual/index.html.en new file mode 100644 index 00000000..a8734184 --- /dev/null +++ b/docs/manual/index.html.en @@ -0,0 +1,103 @@ + + + +Apache HTTP Server Version 2.2 +Documentation - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation
+

Apache HTTP Server Version 2.2 +Documentation

+
+

Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+

+

Release Notes

+ +

Reference Manual

+ +

Users' Guide

+ +

How-To / Tutorials

+ +

Platform Specific Notes

+ +

Other Topics

+ +
+
+

Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/index.html.es b/docs/manual/index.html.es new file mode 100644 index 00000000..60e7873a --- /dev/null +++ b/docs/manual/index.html.es @@ -0,0 +1,110 @@ + + + +Versión 2.2 de la documentación del +Servidor de HTTP Apache - Servidor HTTP Apache + + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación
+

Versión 2.2 de la documentación del +Servidor de HTTP Apache

+
+

Idiomas disponibles:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+

+

Notas de la Versión

+ +

Manual de Referencia

+ +

Guía del Usuario

+ +

How-To / Tutoriales

+ +

Notas específicas sobre plataformas

+ +

Documentación adicional

+ +
+
+

Idiomas disponibles:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/index.html.fr b/docs/manual/index.html.fr new file mode 100644 index 00000000..b0e93061 --- /dev/null +++ b/docs/manual/index.html.fr @@ -0,0 +1,103 @@ + + + +Documentation du Serveur HTTP Apache Version +2.2 - Serveur Apache HTTP + + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur Apache HTTP Version 2.2

+
+
<-
+
+Apache > Serveur HTTP > Documentation
+

Documentation du Serveur HTTP Apache Version +2.2

+
+

Langues Disponibles:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+
Cette traduction peut être périmée. Verifiez la version + Anglaise pour les changements récents.
+

+

Notes sur cette version

+ +

Manuel de Référence

+ +

Guide de l'Utilisateur

+ +

Marche-à-Suivre / Tutoriels

+ +

Notes Spécifiques aux Différentes Plate-formes

+ +

Autres Sujets

+ +
+
+

Langues Disponibles:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/index.html.ja.euc-jp b/docs/manual/index.html.ja.euc-jp new file mode 100644 index 00000000..277f48e0 --- /dev/null +++ b/docs/manual/index.html.ja.euc-jp @@ -0,0 +1,103 @@ + + + +Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2 +¥É¥­¥å¥á¥ó¥È - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó
+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2 +¥É¥­¥å¥á¥ó¥È

+
+

Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+

+

¥ê¥ê¡¼¥¹¥Î¡¼¥È

+ +

¥ê¥Õ¥¡¥ì¥ó¥¹¥Þ¥Ë¥å¥¢¥ë

+ +

¥æ¡¼¥¶¤Î¼ê°ú

+ +

How-To / ¥Á¥å¡¼¥È¥ê¥¢¥ë

+ +

¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸ÇÍ­¤Î¾ðÊó

+ +

¤½¤Î¾

+ +
+
+

Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/index.html.ko.euc-kr b/docs/manual/index.html.ko.euc-kr new file mode 100644 index 00000000..ca6cdc79 --- /dev/null +++ b/docs/manual/index.html.ko.euc-kr @@ -0,0 +1,101 @@ + + + +Apache HTTP Server Version 2.2 ¹®¼­ - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation
+

Apache HTTP Server Version 2.2 ¹®¼­

+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

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

+

¹ßÇ¥¹®

+ +

ÂüÁ¶ ¼³¸í¼­

+ +

»ç¿ëÀÚ Áöħ¼­

+ +

How-To / ÅõÅ丮¾ó

+ +

Ç÷¡Æûº° ¼³¸í

+ +

´Ù¸¥ ÁÖÁ¦

+ +
+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/index.html.pt-br b/docs/manual/index.html.pt-br new file mode 100644 index 00000000..4179232a --- /dev/null +++ b/docs/manual/index.html.pt-br @@ -0,0 +1,102 @@ + + + +Documentação do Servidor HTTP Apache Versão +2.2 - Servidor HTTP Apache + + + + + +
+

Módulos | Diretrizes | FAQ | Glossário | Mapa do site

+

Servidor HTTP Apache Versão 2.2

+
+
<-
+
+Apache > Servidor HTTP > Documentação
+

Documentação do Servidor HTTP Apache Versão +2.2

+
+

Línguas Disponíveis:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+
Esta tradução pode estar desatualizada. + Verifique a versão em Inglês para mudanças recentes.
+

+

Notas da Versão

+ +

Manual de Referência

+ +

Guia do Usuário

+ +

How-To / Tutoriais

+ +

Notas Específicas sobre Platformas

+ +

Outros Tópicos

+ +
+
+

Línguas Disponíveis:  de  | + en  | + es  | + fr  | + ja  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/install.html b/docs/manual/install.html new file mode 100644 index 00000000..53619faf --- /dev/null +++ b/docs/manual/install.html @@ -0,0 +1,23 @@ +URI: install.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: install.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: install.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: install.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: install.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: install.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/install.html.de b/docs/manual/install.html.de new file mode 100644 index 00000000..3097054d --- /dev/null +++ b/docs/manual/install.html.de @@ -0,0 +1,428 @@ + + + +Kompilieren und Installieren - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Kompilieren und Installieren

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ +

Dieses Dokument umfaßt nur die Kompilierung und Installation des + Apache HTTP Servers auf Unix und Unix-ähnlichen Systemen. Für die + Kompilierung und Installation unter Windows lesen Sie bitte Den Apache HTTPd unter Microsoft Windows + betreiben. Für andere Plattformen lesen Sie bitte die + Dokumentation Plattformen.

+ +

Der Apache HTTPd verwendet libtool und + autoconf, um eine Erstellungsumgebung zu schaffen, die der + vieler anderer Open Source Projekte ähnlich sieht.

+ +

Wenn Sie von einer Unterversion auf die nächste aktualisieren (z.B. + von 2.2.50 auf 2.2.51), springen Sie bitte zum Abschnitt Upgrade.

+
+ +
top
+
+

Überblick für die Ungeduldigen

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Download$ lynx http://httpd.apache.org/download.cgi +
Auspacken$ gzip -d httpd-NN.tar.gz
+ $ tar xvf httpd-NN.tar + $ cd httpd-NN
Konfigurieren$ ./configure --prefix=PREFIX +
Kompilieren$ make
Installieren$ make install
Anpassen$ vi PREFIX/conf/httpd.conf
Testen$ PREFIX/bin/apachectl -k start +
+ +

NN muss durch die entsprechende Versionsnummer ersetzt + werden und PREFIX durch den Verzeichnispfad, + in dem der Server installiert werden soll. Wenn PREFIX nicht + angegeben ist, wird die Voreinstellung /usr/local/apache2 + verwendet.

+ +

Beginnend mit den Anforderungen + für die Kompilierung und Installation des Apache HTTP Servers ist + weiter unten jeder Abschnitt des Kompilierungs- und + Installationsvorganges genauer beschrieben.

+
top
+
+

Anforderungen

+ +

Folgende Anforderungen gelten für die Erstellung des + Apache HTTPd:

+ +
+
Plattenplatz
+
Stellen Sie sicher, dass Sie kurzzeitig wenigstens 50 MB freien + Festplattenplatz zur Verfügung haben. Nach der Installation + belegt der Apache ungefähr 10 MB Plattenplatz. Der + tatsächliche Platzbedarf variiert in Abhängigkeit von den + gewählten Konfigurationseinstellungen und + Modulen von Drittanbietern.
+ +
ANSI-C-Compiler und Generierungswerkzeuge
+
Stellen Sie sicher, dass Sie einen ANSI-C Compiler installiert + haben. Der GNU C + Compiler (GCC) der Free Software + Foundation (FSF) ist empfehlenswert. Wenn + Sie den GCC nicht besitzen, stellen Sie zumindest sicher, dass der + Compiler Ihres Anbieters ANSI-kompatibel ist. Außerdem muss Ihr + PATH wesentliche Generierungswerkzeuge wie + make enthalten.
+ +
Zeitgenauigkeit bewahren
+
Elemente des HTTP-Protokolls werden in Form einer Tageszeit + ausgedrückt. Darum sollten Sie jetzt prüfen, ob Ihr System + die Fähigkeit zur Zeitsynchronisation besitzt, und diese + gegebenenfalls installieren. Üblicherweise werden hierfür + die Programme ntpdate oder xntpd verwendet, + die auf dem Network Time Protocol (NTP) basieren. Nähere + Informationen über NTP Software und öffentliche Zeitserver + finden Sie auf der NTP-Homepage.
+ +
Perl 5 + [OPTIONAL]
+
Für einige Hilfsskripte wie apxs + oder dbmmanage (die in Perl + geschrieben sind) wird der Perl 5 Interpreter benötigt (die + Versionen ab 5.003 sind ausreichend). Wenn Sie mehrere Perl + Interpreter haben (beispielsweise eine systemweite Installation von + Perl 4 und Ihre eigene Perl 5-Installation), dann sollten Sie die + --with-perl-Option (siehe unten) verwenden, um + sicherzustellen, dass der richtige Interpreter von + configure ausgewählt wird. + Wenn kein Perl 5-Interpreter vom configure-Skript + gefunden werden kann, können Sie die betroffenen Hilfsskripte nicht + verwenden, sind jedoch selbstverständlich nach wie vor in der Lage, + den Apache HTTPd zu bauen und zu installieren.
+ +
apr/apr-util >= 1.2
+
apr und apr-util werden mit den + Quelltext-Veröffentlichungen des Apache HTTPd gebündelt und in + nahezu allen Fällen ohne Probleme verwendet. Sind jedoch die + apr- oder apr-util-Versionen 1.0 oder 1.1 auf + Ihrem System installiert, dann müssen Sie diese + apr-/apr-util-Installationen entweder + aktualisieren oder httpd separate Kompilate verwenden lassen. Um + hierfür die mitgelieferten + apr-/apr-util-Quellen zu verwenden, + müssen Sie diese manuell installieren: +

+ # apr 1.2 bauen und installieren
+ cd srclib/apr
+ ./configure --prefix=/usr/local/apr-httpd/
+ make
+ make install
+
+ # apr-util 1.2 bauen und installieren
+ cd ../apr-util
+ ./configure --prefix=/usr/local/apr-util-httpd/ + --with-apr=/usr/local/apr-httpd/
+ make
+ make install
+
+ # httpd konfigurieren
+ cd ../../
+ ./configure --with-apr=/usr/local/apr-httpd/ + --with-apr-util=/usr/local/apr-util-httpd/ +

+
+
+
top
+
+

Download

+ +

Der Apache HTTP Server kann von der Apache-HTTP-Server-Downloadseite heruntergeladen werden, auf der + verschiedene Spiegelserver angegeben sind. Für die meisten Benutzer + des Apache HTTPd ist es auf Unix-ähnlichen Systemen am Besten, die + Quellcodeversion herunterzuladen und zu kompilieren. Der + Erstellungsprozess (weiter unten beschrieben) ist einfach und erlaubt es + Ihnen, den Server Ihren Bedürfnissen anzupassen. Dazu kommt, dass + Binärdistributionen gegenüber der aktuellen Quellcodeversion oft + veraltet sind. Wenn Sie tatsächlich ein Binärpaket + herunterladen, folgen Sie bitte den Anweisungen in der Datei + INSTALL.bindist, die der Distribution beiliegt.

+ +

Es ist wichtig, dass Sie nach dem Herunterladen überprüfen, + dass es sich um einer vollständige und unveränderte Version des + Apache HTTP Servers handelt. Das können Sie erreichen, indem Sie das + heruntergeladene Paket gegen die PGP-Signatur prüfen. Einzelheiten dazu + erfahren Sie auf der Download-Seite. Es + ist auch ein erweitertes Beispiel verfügbar, dass die Anwendung von PGP + beschreibt.

+ +
top
+
+

Auspacken

+ +

Das Auspacken des Quellcodes aus dem Apache-HTTPd-Tarball besteht + aus einem simplen Dekomprimieren und danach "Ent-tarren":

+ +

+ $ gzip -d httpd-NN.tar.gz
+ $ tar xvf httpd-NN.tar +

+ +

Dies erstellt unterhalb des aktuellen Verzeichnisses ein neues + Verzeichnis, das den Quellcode für die Distribution enthält. + Sie sollten mit cd in dieses Verzeichnis wechseln, + bevor Sie mit der Kompilierung des Servers weitermachen.

+ +
top
+
+

Den Codebaum konfigurieren

+ +

Der nächste Schritt ist die Konfiguration des + Apache-HTTPd-Codebaumes für Ihre spezielle Plattform und Ihre + persönlichen Bedürfnisse. Dies wird mit dem Skript + configure durchgeführt, das im Wurzelverzeichnis + der Distribution enthalten ist. (Entwickler, welche eine nicht + freigegebene Version des Apache-HTTPd-Codebaumes herunterladen, müssen + autoconf und libtool installiert haben und müssen + buildconf ausführen, bevor sie mit den + nächsten Schritten fortfahren können. Dies wird bei + offiziellen Releases nicht notwendig sein.)

+ +

Um den Codebaum mit den Standardeinstellungen zu konfigurieren, + geben Sie einfach ./configure ein. Zur Änderung + dieser Voreinstellungen akzeptiert configure eine + Reihe von Variablen und Kommandozeilenoptionen.

+ +

Die wichtigste Option ist --prefix, der Ablageort, an dem + der Apache HTTP Server später installiert wird, da er für diesen Ort + konfiguriert werden muss, um korrekt zu arbeiten. Eine feinere Einstellung + der Dateiablagen ist mit weiteren configure-Optionen + möglich.

+ +

Weiterhin können Sie zu diesem Zeitpunkt festlegen, welche Funktionalität + Sie in den Apache HTTPd aufnehmen möchten, indem Sie Module aktivieren oder deaktivieren. Der Apache HTTP + Server bindet standardmäßig einen Satz von Basismodulen ein. Andere Module + werden mit Hilfe der Option --enable-module + aktiviert, wobei module den Namen des Moduls ohne das + Präfix mod_ darstellt. Ausserdem sind alle Unterstriche + durch Bindestriche zu ersetzen. Sie können sich auch entscheiden, + Module als "Shared Objects (DSOs)" zu kompilieren, + welche zur Laufzeit ge- und entladen werden können. Dazu verwenden + Sie die Option --enable-module=shared. + Entsprechend können Sie Basismodule mit der Option + --disable-module deaktivieren. Lassen Sie Vorsicht + walten. wenn Sie diese Optionen verwenden, da configure + Sie nicht warnen kann, wenn die von Ihnen angegebenen Module nicht + existieren; die Option wird dann einfach ignoriert.

+ +

Zusätzlich ist es zuweilen notwendig, das + configure-Skript mit Extrainformationen zum Ablageort + Ihres Compilers, Ihrer Bibliotheken oder Header-Dateien zu versorgen. Das + tun Sie, indem Sie entweder Umgebungsvariablen oder Kommandozeilenoptionen + an configure übergeben. Für mehr Informationen + lesen Sie bitte die Hilfeseite zu configure.

+ +

Um einen kurzen Eindruck zu gewinnen, welche Möglichkeiten Sie + haben, folgt hier ein typisches Beispiel, das den Apache mit einem + speziellen Compiler und Compilerflags für das + Installationsverzeichnis /sk/pkg/apache kompiliert, sowie + die beiden zusätzlichen Module mod_rewrite und + mod_speling für späteres Laden durch den + DSO-Mechanismus:

+ +

+ $ CC="pgcc" CFLAGS="-O2" \
+ ./configure --prefix=/sw/pkg/apache \
+ --enable-rewrite=shared \
+ --enable-speling=shared +

+ +

Wenn configure startet, benötigt es mehrere + Minuten, um die Verfügbarkeit von Features auf Ihrem System zu + prüfen und ein Makefile zu generieren, das später zur + Kompilierung des Servers verwendet wird.

+ +

Einzelheiten zu den vielen verschiedenen configure-Optionen finden Sie auf der Hilfeseite zu + configure.

+ +
top
+
+

Erstellen

+ +

Nun können Sie die verschiedenen Teile, die das Apache-HTTPd-Paket + bilden, einfach durch Ausführen des folgenden Befehls erstellen:

+ +

$ make

+ +

Seien Sie hierbei bitte geduldig, denn eine Basiskonfiguration + benötigt mehrere Minuten zum Kompilieren. Die Zeit kann jedoch + abhängig von Ihrer Hardware und der Anzahl + der Module, die Sie aktiviert haben, sehr stark variieren.

+
top
+
+

Installieren

+ +

Nun endlich installieren Sie das Package unter dem konfigurierten + Installations-PREFIX (siehe oben: Option --prefix + durch Aufrufen von:

+ +

$ make install

+ +

Wenn Sie upgraden, wird die Installation Ihre Konfigurationsdateien + oder Dokumente nicht überschrieben.

+
top
+
+

Anpassen

+ +

Als nächstes können Sie Ihren Apache HTTP Server anpassen, + indem Sie die Konfigurationsdateien + unterhalb von PREFIX/conf/ editieren.

+ +

$ vi PREFIX/conf/httpd.conf

+ +

Werfen Sie auch einen Blick in das Apache-HTTP-Server-Handbuch unter docs/manual/. Die aktuellste Version dieses Handbuchs + sowie eine komplette Referenz der verfügbaren Konfigurationsanweisungen finden + Sie unter http://httpd.apache.org/docs/2.2/.

+
top
+
+

Testen

+ +

Sie können nun Ihren Apache HTTP Server starten, indem Sie einfach

+ +

$ PREFIX/bin/apachectl -k start

+ +

ausführen.

+ +

Danach sollten Sie Ihr erstes Dokument unter dem URL + http://localhost/ anfordern können. Die Webseite, + die Sie sehen, ist im DocumentRoot + abgelegt, welches üblicherweise PREFIX/htdocs/ + ist. Den Server stoppen Sie wieder durch + Ausführen von:

+ +

$ PREFIX/bin/apachectl -k stop

+
top
+
+

Upgrade

+ +

Der erste Schritt beim Aktualisieren besteht darin, die + Versionsankündigung sowie die CHANGES-Datei in der + Quelltextdistribution zu lesen, um Änderungen zu finden, die Ihr + System möglicherweise betreffen. Wenn Sie einen größeren + Versionssprung durchführen (z.B. vom 1.3 auf 2.0 oder von 2.0 auf + 2.2), wird es wahrscheinlich auch größere Unterschiede in der + Kompilier- und Laufzeitkonfiguration geben, die manuelle Nacharbeiten + erfordern. Außerdem müssen alle Module aktualisiert + werden, um den Änderungen der Modul-API gerecht zu werden.

+ +

Die Aktualisierung einer Unterversion auf eine andere (z.B. von 2.2.55 + auf 2.2.57) ist einfacher. make install überschreibt + keine der bereits existierenden Dokumente, Log- und Konfigurationsdateien. + Ausserdem bemühen sich die Entwickler, inkompatible Änderungen + der configure-Optionen, der Laufzeitkonfiguration sowie + der Modul-API zu vermeiden. In den meisten Fällen sollten Sie in der + Lage sein, den gleichen configure-Befehl, die gleiche + Konfiguration und die gleichen Module wieder zu verwenden.

+ +

Um auf eine neue Unterversion zu aktualisieren, suchen Sie zunächst + die Datei config.nice im build-Verzeichnis + Ihrer Serverinstallation oder im Wurzelverzeichnis des Quelltextbaums + der alten Installation. Die Datei enthält den genauen + configure-Befehl, der verwendet wurde, um den + Quellcode zu konfigurieren. Um jetzt von einer Version auf die + nächste zu aktualisieren, kopieren Sie einfach die + config.nice in das Verzeichnis der neuen Version, + passen sie bei Bedarf an, und führen Sie sie aus:

+ +

+ $ ./config.nice
+ $ make
+ $ make install
+ $ PREFIX/bin/apachectl -k graceful-stop
+ $ PREFIX/bin/apachectl -k start
+

+ +
Sie sollten jede neue Version immer in Ihrer Umgebung + testen, bevor Sie sie produktiv schalten. Beispielsweise können Sie + die neue Version neben der alten installieren, indem Sie ein anderes + --prefix und einen anderen Port wählen (durch Anpassen der + Listen-Direktive). So + können Sie auf eventuelle Inkompatibilitäten testen, bevor Sie + endgültig die neue Version verwenden.
+
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en new file mode 100644 index 00000000..96f073c0 --- /dev/null +++ b/docs/manual/install.html.en @@ -0,0 +1,412 @@ + + + +Compiling and Installing - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Compiling and Installing

+
+

Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ + +

This document covers compilation and installation of the Apache HTTP + Server on Unix and Unix-like systems only. For compiling and + installation on Windows, see Using Apache HTTPd with Microsoft + Windows. For other platforms, see the platform documentation.

+ +

Apache HTTPd uses libtool and autoconf + to create a build environment that looks like many other Open Source + projects.

+ +

If you are upgrading from one minor version to the next (for + example, 2.2.50 to 2.2.51), please skip down to the upgrading section.

+ +
+ +
top
+
+

Overview for the + impatient

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Download$ lynx http://httpd.apache.org/download.cgi +
Extract$ gzip -d httpd-NN.tar.gz
+ $ tar xvf httpd-NN.tar
+ $ cd httpd-NN
Configure$ ./configure --prefix=PREFIX +
Compile$ make
Install$ make install
Customize$ vi PREFIX/conf/httpd.conf
Test$ PREFIX/bin/apachectl -k start +
+ +

NN must be replaced with the current version + number, and PREFIX must be replaced with the + filesystem path under which the server should be installed. If + PREFIX is not specified, it defaults to + /usr/local/apache2.

+ +

Each section of the compilation and installation process is + described in more detail below, beginning with the requirements + for compiling and installing Apache HTTP Server.

+
top
+
+

Requirements

+ +

The following requirements exist for building Apache HTTPd:

+ +
+
Disk Space
+
Make sure you have at least 50 MB of temporary free disk + space available. After installation Apache occupies + approximately 10 MB of disk space. The actual disk space + requirements will vary considerably based on your chosen + configuration options and any third-party modules.
+ +
ANSI-C Compiler and Build System
+
Make sure you have an ANSI-C compiler installed. The GNU C + compiler (GCC) from the Free Software Foundation (FSF) + is recommended. If you don't have GCC + then at least make sure your vendor's compiler is ANSI + compliant. In addition, your PATH must contain + basic build tools such as make.
+ +
Accurate time keeping
+
Elements of the HTTP protocol are expressed as the time of + day. So, it's time to investigate setting some time + synchronization facility on your system. Usually the + ntpdate or xntpd programs are used for + this purpose which are based on the Network Time Protocol (NTP). + See the NTP + homepage for more details about NTP software and public + time servers.
+ +
Perl 5 + [OPTIONAL]
+
For some of the support scripts like apxs or dbmmanage (which are + written in Perl) the Perl 5 interpreter is required (versions + 5.003 or newer are sufficient). If you have multiple Perl + interpreters (for example, a systemwide install of Perl 4, and + your own install of Perl 5), you are advised to use the + --with-perl option (see below) to make sure the + correct one is used by configure. + If no Perl 5 interpreter is found by the + configure script, you will not be able to use + the affected support scripts. Of course, you will still be able to + build and use Apache HTTPd.
+ +
apr/apr-util >= 1.2
+
apr and apr-util are bundled + with the Apache HTTPd source releases, and will be used without any + problems in almost all circumstances. However, if + apr or apr-util, versions 1.0 or 1.1, + are installed on your system, you must either upgrade your + apr/apr-util installations to + 1.2, or have httpd use seperate builds. To use the bundled + apr/apr-util sources for this + purpose you must install them manually: +

+ # Build and install apr 1.2
+ cd srclib/apr
+ ./configure --prefix=/usr/local/apr-httpd/
+ make
+ make install
+
+ # Build and install apr-util 1.2
+ cd ../apr-util
+ ./configure --prefix=/usr/local/apr-util-httpd/ + --with-apr=/usr/local/apr-httpd/
+ make
+ make install
+
+ # Configure httpd
+ cd ../../
+ ./configure --with-apr=/usr/local/apr-httpd/ + --with-apr-util=/usr/local/apr-util-httpd/ +

+
+
+
top
+
+

Download

+ +

The Apache HTTP Server can be downloaded from the Apache HTTP Server + download site, which lists several mirrors. Most users of + Apache HTTPd on unix-like systems will be better off downloading and + compiling a source version. The build process (described below) is + easy, and it allows you to customize your server to suit your needs. + In addition, binary releases are often not up to date with the latest + source releases. If you do download a binary, follow the instructions + in the INSTALL.bindist file inside the distribution.

+ +

After downloading, it is important to verify that you have a + complete and unmodified version of the Apache HTTP Server. This + can be accomplished by testing the downloaded tarball against the + PGP signature. Details on how to do this are available on the download + page and an extended example is available describing the use of + PGP.

+ +
top
+
+

Extract

+ +

Extracting the source from the Apache HTTPd tarball is a + simple matter of uncompressing, and then untarring:

+ +

+ $ gzip -d httpd-NN.tar.gz
+ $ tar xvf httpd-NN.tar +

+ +

This will create a new directory under the current directory + containing the source code for the distribution. You should + cd into that directory before proceeding with + compiling the server.

+
top
+
+

Configuring the source tree

+ +

The next step is to configure the Apache HTTPd source tree for your + particular platform and personal requirements. This is done using + the script configure included in + the root directory of the distribution. (Developers downloading + an unreleased version of the Apache HTTPd source tree will need to have + autoconf and libtool installed and will + need to run buildconf before proceeding with the next + steps. This is not necessary for official releases.)

+ +

To configure the source tree using all the default options, + simply type ./configure. To change the default + options, configure accepts a variety of variables + and command line options.

+ +

The most important option is the location --prefix + where the Apache HTTP Server is to be installed later, because Apache + HTTPd has to be + configured for this location to work correctly. More fine-tuned + control of the location of files is possible with additional configure + options.

+ +

Also at this point, you can specify which features you + want included in Apache HTTPd by enabling and disabling modules. The Apache HTTP Server comes with a Base set of modules included by + default. Other modules are enabled using the + --enable-module option, where + module is the name of the module with the + mod_ string removed and with any underscore converted + to a dash. You can also choose to compile modules as shared objects (DSOs) -- which can be loaded + or unloaded at runtime -- by using the option + --enable-module=shared. Similarly, you can + disable Base modules with the + --disable-module option. Be careful when + using these options, since configure cannot warn you + if the module you specify does not exist; it will simply ignore the + option.

+ +

In addition, it is sometimes necessary to provide the + configure script with extra information about the + location of your compiler, libraries, or header files. This is + done by passing either environment variables or command line + options to configure. For more information, see the + configure manual page.

+ +

For a short impression of what possibilities you have, here + is a typical example which compiles Apache for the installation + tree /sw/pkg/apache with a particular compiler and flags + plus the two additional modules mod_rewrite and + mod_speling for + later loading through the DSO mechanism:

+ +

+ $ CC="pgcc" CFLAGS="-O2" \
+ ./configure --prefix=/sw/pkg/apache \
+ --enable-rewrite=shared \
+ --enable-speling=shared +

+ +

When configure is run it will take several minutes to + test for the availability of features on your system and build + Makefiles which will later be used to compile the server.

+ +

Details on all the different configure options are + available on the configure manual page.

+
top
+
+

Build

+ +

Now you can build the various parts which form the Apache HTTPd + package by simply running the command:

+ +

$ make

+ +

Please be patient here, since a base configuration takes + several minutes to compile and the time will vary widely + depending on your hardware and the number of modules that you + have enabled.

+
top
+
+

Install

+ +

Now it's time to install the package under the configured + installation PREFIX (see --prefix option + above) by running:

+ +

$ make install

+ +

If you are upgrading, the installation will not overwrite + your configuration files or documents.

+
top
+
+

Customize

+ +

Next, you can customize your Apache HTTP Server by editing + the configuration files under + PREFIX/conf/.

+ +

$ vi PREFIX/conf/httpd.conf

+ +

Have a look at the Apache HTTP Server manual under docs/manual/ or consult http://httpd.apache.org/docs/2.2/ for the most recent + version of this manual and a complete reference of available configuration directives.

+
top
+
+

Test

+ +

Now you can start your Apache + HTTP Server by immediately running:

+ +

$ PREFIX/bin/apachectl -k start

+ +

and then you should be able to request your first document + via URL http://localhost/. The web page you see is located + under the DocumentRoot, + which will usually be PREFIX/htdocs/. + Then stop the server again by + running:

+ +

$ PREFIX/bin/apachectl -k stop

+
top
+
+

Upgrading

+ +

The first step in upgrading is to read the release announcement + and the file CHANGES in the source distribution to + find any changes that may affect your site. When changing between + major releases (for example, from 1.3 to 2.0 or from 2.0 to 2.2), + there will likely be major differences in the compile-time and + run-time configuration that will require manual adjustments. All + modules will also need to be upgraded to accomodate changes in the + module API.

+ +

Upgrading from one minor version to the next (for example, from + 2.2.55 to 2.2.57) is easier. The make install + process will not overwrite any of your existing documents, log + files, or configuration files. In addition, the developers make + every effort to avoid incompatible changes in the + configure options, run-time configuration, or the + module API between minor versions. In most cases you should be able to + use an identical configure command line, an identical + configuration file, and all of your modules should continue to + work.

+ +

To upgrade across minor versions, start by finding the file + config.nice in the build directory of + your installed server or at the root of the source tree for your + old install. This will contain the exact + configure command line that you used to + configure the source tree. Then to upgrade from one version to + the next, you need only copy the config.nice file to + the source tree of the new version, edit it to make any desired + changes, and then run:

+ +

+ $ ./config.nice
+ $ make
+ $ make install
+ $ PREFIX/bin/apachectl -k graceful-stop
+ $ PREFIX/bin/apachectl -k start
+

+ +
You should always test any new version in your + environment before putting it into production. For example, you + can install and run the new version along side the old one by + using a different --prefix and a + different port (by adjusting the Listen directive) to test for any + incompatibilities before doing the final upgrade.
+
+
+

Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/install.html.es b/docs/manual/install.html.es new file mode 100644 index 00000000..3734125d --- /dev/null +++ b/docs/manual/install.html.es @@ -0,0 +1,438 @@ + + + +Compilación e Instalación - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

Compilación e Instalación

+
+

Idiomas disponibles:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ + +

Este documento explica cómo compilar e instalar Apache en + sistemas Unix y tipo Unix. Para obtener información sobre + cómo compilar e instalar en Windows, consulte la sección + Usar Apache en Microsoft + Windows. Para otras plataformas, consulte la + documentación sobre plataformas.

+ +

El entorno de configuración e instalación de Apache + 2.0 ha cambiado completamente respecto al de Apache 1.3. Apache + 1.3 usaba un conjunto de scripts a medida para conseguir una + instalación fácil. Apache 2.0 usa libtool y + autoconf para crear un entorno más parecido al + de muchos otros proyectos Open Source.

+ +

Si lo que quiere hacer es actualizar su servidor Apache desde + una versión menor (por ejemplo, desde la 2.0.50 a la 2.0.51), + pase directamente a la sección de actualización.

+ +
+ +
top
+
+

Visión general del proceso para + impacientes

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Descargar$ lynx http://httpd.apache.org/download.cgi +
Descomprimir$ gzip -d httpd-2_1_NN.tar.gz
+ $ tar xvf httpd-2_1_NN.tar
Ejecutar el script configure$ ./configure --prefix=PREFIX +
Compilar$ make
Instalar$ make install
Personalizar$ vi PREFIX/conf/httpd.conf
Comprobar que la instalación + funciona$ PREFIX/bin/apachectl start +
+ +

NN hay que reemplazarlo por el número de la + versión menor, y PREFIX hay que reemplazarlo por la + ruta en la que se va a instalar Apache. Si no especifica + ningún valor en PREFIX, el valor por defecto que se + toma es /usr/local/apache2.

+ +

Cada parte del proceso de configuración e instalación + se describe detalladamente más abajo, empezando por los + requisitos para compilar e instalar Apache.

+
top
+
+

Requisitos

+ +

Estos son los requisitos necesarios para compilar Apache:

+ +
+
Espacio en disco
Compruebe que tiene disponibles al + menos 50 MB de espacio libre en disco. Después de la + instalación, Apache ocupa aproximadamente 10 MB. No + obstante, la necesidad real de espacio en disco varía + considerablemente en función de las opciones de + configuración que elija y de los módulos externos que + use.
+ +
Compilador ANSI-C y Build System
Compruebe que + tiene instalado un compilador de ANSI-C. Se recomienda el Compilador GNU C + (GCC) de la Free Software + Foundation (FSF) (con la versión 2.7.2 es + suficiente). Si no tiene instaldo el GCC, entonces compruebe que + el compilador que va a utilizar cumple con los estándares + ANSI. Además, su PATH debe contener la + ubicación donde de encuentran las herramientas básicas + para compilar tales como make.
+ +
Ajuste exacto del reloj del sistema
Los elementos + del protocolo HTTP están expresados según la hora del + dia. Por eso, si quiere puede investigar como instalar alguna + utilidad para sincronizar la hora de su sistema. Para esto, + normalmente, se usan los programas ntpdate o + xntpd, que están basados en el protocolo + Network Time Protocol (NTP). Consulte el grupo de noticias comp.protocols.time.ntp + y el sitio web de NTP + para obtener más información sobre NTP y los + servidores públicos de tiempo.
+ +
Perl 5 [OPCIONAL]
+
Para algunos de los scripts de soporte como apxs o dbmmanage (que están + escritos en Perl) es necesario el intérprete de Perl 5 (las + versiones 5.003 o posteriores son suficientes). Si el script + `configure' no encuentra ese intérprete + tampoco pasa nada. Aún puede compilar e instalar Apache + 2.0. Lo único que ocurrirá es que esos scripts de + soporte no podrán ser usados. Si usted tiene varios + interpretes de Perl instalados (quizás Perl 4 porque estaba + ya incluido en su distribución de Linux y Perl 5 porque lo + ha instalado usted), entonces se recomienda usar la opción + --with-perl para asegurarse de que + ./configure usa el intérprete correcto.
+
+
top
+
+

Descargar

+ +

Puede descargar Apache desde la sección de + descargas del sitio web de Apache el cual tiene varios + mirrors. Para la mayoría de los usuarios de Apache que tienen + sistemas tipo Unix, se recomienda que se descarguen y compilen el + código fuente. El proceso de compilación (descrito + más abajo) es fácil, y permite adaptar el servidor + Apache a sus necesidades. Además, las versiones de + disponibles en archivos binarios no están siempre actulizadas + con las últimas modificaciones en el codigo fuente. Si se + descarga un binario, siga las instrucciones contenidas en el + archivo INSTALL.bindist incluido en la + distribución

+ +

Después de la descarga, es importante que verifique que el + archivo descargado del servidor HTTP Apache está completo y + sin modificaciones. Esto puede hacerlo comparando el archivo + descargado (.tgz) con su firma PGP. Instrucciones detalladas de + cómo hacer esto están disponibles en la + sección de descargas junto con un ejemplo de cómo usar + PGP.

+ +
top
+
+

Descomprimir

+ +

Extraer el código fuente del archivo .tgz que acabada de + descargar es muy fácil. Ejecute los siguientes comandos:

+ +

+ $ gzip -d httpd-2_1_NN.tar.gz
+ $ tar xvf httpd-2_1_NN.tar +

+ +

Estos comandos crearán un nuevo directorio dentro del + directorio en el que se encuentra y que contendrá el + código fuente de la distribución. Debe cambiarse a ese + directorio con cd para proceder a compilar el + servidor Apache.

+ +
top
+
+

Configuración de la estructura de +directorios

+ +

El siguiente paso es configurar la estructura de directorios + para su plataforma y sus necesidades personales. Esto se hace + usando el script configure incluido en el directorio + raiz de la distribución que acaba de descargar. (Los + desarrolladores que se descarguen la versión del CVS de la + estructura de directorios necesitarán tener instalados + autoconf y libtool, y necesitarán + ejecutar buildconf antes de continuar con los + siguientes pasos. Esto no es preciso para las versiones + oficiales.)

+ +

Para configurar la estructura de directorios a partir del + código fuente usando las opciones por defecto, solo tiene que + ejecutar ./configure. Para cambiar las opciones por + defecto, configure acepta una serie de variables y + opciones por la línea de comandos.

+ +

La opción más importante es --prefix que + es el directorio en el que Apache va a ser instalado después, + porque Apache tiene que ser configurado para el directorio que se + especifique para que funcione correctamente. Es posible lograr un + mayor control del lugar donde se van a instalar los ficheros de + Apache con otras opciones de + configuración.

+ +

En este momento, puede especificar que características + o funcionalidades quiere incluir en Apache activando o + desactivando módulos. Apache viene con + una selección + básica de módulos incluidos por defecto. Se pueden + activar otros módulos usando la opción + --enable-module, donde module + es el nombre del módulo sin el mod_ y + convirtiendo los guiones bajos que tenga en guiones normales. + También puede optar por compilar módulos como objetos dinámicos compartidos (DSOs) -- + que pueden ser activados o desactivados al ejecutar -- usando la + opción --enable-module=shared. De + igual manera, puede desactivar alguno de los módulos que + vienen por defecto en la selección basica con la opción + --disable-module. Tenga cuidado cuando + use estas opciones, porque configure no le + avisará si el módulo que especifica no existe; + simplemente ignorará esa opción.

+ +

Además, a veces es necesario pasarle al script + configure información adicional sobre donde esta + su compilador, librerias o ficheros de cabecera. Esto se puede + hacer, tanto pasando variables de entorno, como pasandole opciones + a configure a través de la línea de + comandos. Para más información, consulte el Manual del script + configure.

+ +

Para que se haga una idea sobre las posibilidades que tiene, + aquí tiene un ejemplo típico que configura Apache para + la ruta /sw/pkg/apache con un compilador y unos flags + determinados, y además, con dos módulos adicionales + mod_rewrite y mod_speling para + cargarlos después a través del mecanismo DSO:

+ +

+ $ CC="pgcc" CFLAGS="-O2" \
+ ./configure --prefix=/sw/pkg/apache \
+ --enable-rewrite=shared \
+ --enable-speling=shared +

+ +

Cuando se ejecuta configure se comprueban que + características o funcionalidades están disponibles en + su sistema y se crean los Makefiles que serán usados luego + para compilar el servidor. Esto tardará algunos minutos.

+ +

La información sobre todas las opciones de + configure está disponible en el Manual del script + configure.

+ +
top
+
+

Compilar

+ +

Ahora puede compilar las diferentes partes que forman Apache + simplemente ejecutando el siguiente comando:

+ +

$ make

+ +

Por favor, tanga un poco de paciencia ahora, porque una + configuración básica tarda aproximadamente 3 minutos en + compilar en un Pentium III con un sistema Linux 2.2, pero este + tiempo puede variar considerablemente en función de su + hardware y del número de módulos que haya + seleccionado.

+
top
+
+

Instalar

+ +

Ahora es el momento de instalar el paquete en el diretorio + elegido en PREFIX (consulte la opción + --prefix más arriba) ejecutando:

+ +

$ make install

+ +

Si usted está solo actualizando una instalación + anterior, la nueva instalación no sobreescribirá sus + ficheros de configuración ni otros documentos.

+
top
+
+

Personalizar

+ +

El paso siguiente, es personalizar su servidor Apache editando + los ficheros de configuración + que están en PREFIX/conf/.

+ +

$ vi PREFIX/conf/httpd.conf

+ +

échele un vistazo al Manual de Apache que está en docs/manual/ o consulte en http://httpd.apache.org/docs/2.2/ la versión más + reciente de este manual y la Guia de Referencia de todas las directivas de configuración + disponibles.

+
top
+
+

Comprobar que la instalación +funciona

+ +

Ahora puede iniciar su servidor + Apache cuando quiera ejecutando:

+ +

$ PREFIX/bin/apachectl start

+ +

y entonces debe poder acceder al documento que tenga + especificado por defecto usando el siguiente URL: + http://localhost/. El documento que verá + estará en DocumentRoot y + casi siempre estará en PREFIX/htdocs/. + Si quiere parar el servidor, puede + hacerlo ejecutando:

+ +

$ PREFIX/bin/apachectl stop

+
top
+
+

Actualizar una instalación +prrevia

+ +

El primer paso para actualizar una instalación anterior es + leer las especificaciones de la versión y el fichero + CHANGES en la distribución de código fuente + que ha descargado para encontrar los cambios que puedan afectar a + su instalación actual. Cuando el cambio sea entre versiones + mayores (por ejemplo, de la 1.3 a la 2.0 o de la 2.0 a la 2.2), + entonces es más probable que haya diferencias importantes en + la compilación y en la ejecución que necesitarán + ajustes manuales. Todos los módulos necesitarán + también ser actualizados para adaptarse a los cambios en el + interfaz de programación (API) de módulos.

+ +

La actualización cuando el cambio es entre versiones + menores (por ejemplo, de la 2.0.55 a la 2.0.57) es más + fácil. El proceso make install no + sobreescribirá ninguno de los documentos existentes, archivos + log, o archivos de configuración. Además, los + desarrolladores hacen todos los esfuerzos posibles para evitar + cambios que generen incompatibilidades en las opciones de + configure, en la configuración de la + ejecución o en la interfaz de programación de + módulos. En la mayor parte de los casos debe poder usar un + comando configure idéntico, un fichero de + configuracién idéntico, y todos sus módulos deben + seguir funcionando. (Esto es válido solo para versiones + posteriores a la 2.0.41; las versiones anteriores contienen + cambios incompatibles.)

+ +

Si va a conservar la estructura de directorios de su anterior + instalación, la actualización es más fácil + incluso. El fichero config.nice que está en el + directorio raiz de la estructura de directorios antigua contiene + exactamente el comando configure que usted usó + para configurar la estructura de directorios de Apache. Entonces, + para actualizar su instalación de una versóon a la + siguinete, solo tiene que copiar el archivo + config.nice a la estructura de directorios del + código fuente de la nueva versión, editarlo, hacer + cualquier cambio que desee, y ejecutarlo :

+ +

+ $ ./config.nice
+ $ make
+ $ make install
+ $ PREFIX/bin/apachectl stop
+ $ PREFIX/bin/apachectl start
+

+ +
Tenga en cuenta que antes de poner una nueva + versión de Apache en producción, debe siempre probarla + antes en su entorno. Por ejemplo, puede instalar y ejecutar la + nueva versión junto con la antigua usando un + --prefix diferente y un puerto diferente (modificando + la directiva Listen) + para comprobar que no existe ninguna incompatibilidad antes de + hacer la actualización definitiva.
+
+
+

Idiomas disponibles:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/install.html.fr b/docs/manual/install.html.fr new file mode 100644 index 00000000..2ffe5e91 --- /dev/null +++ b/docs/manual/install.html.fr @@ -0,0 +1,430 @@ + + + +Compilation et Installation - Serveur Apache HTTP + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur Apache HTTP Version 2.2

+
+
<-
+
+Apache > Serveur HTTP > Documentation > Version 2.2

Compilation et Installation

+
+

Langues Disponibles:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+
Cette traduction peut être périmée. Verifiez la version + Anglaise pour les changements récents.
+ + +

Ce document couvre la compilation et l'installation d'Apache sur les + systèmes Unix et clones d'Unix. Pour la compilation et l'installation sous + Windows, voir Utiliser Apache sous Windows + . Pour les autres plates-formes, voir la documentation des plates-formes.

+ +

L'environnement de configuration et d'installation d'Apache 2.0 a été + complétement revu par rapport à celui d'Apache 1.3. Apache 1.3 utilisait un + ensemble de scripts pour permettre une installation facile. Apache 2.0 + utilise à présent libtool et autoconf afin de + créer un environnement le plus proche possible d'autres projets + Logiciel Libre.

+ +

Si vous faite une mise à niveau d'une version mineure à la suivante (par + exemple, de 2.0.50 à 2.0.51), veuillez s'il vous plaît passer directement à + la section Mise à niveau.

+ +
+ +
top
+
+

Survol Rapide pour les + impatients

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Télécharger$ lynx http://httpd.apache.org/download.cgi +
Extraire$ gzip -d httpd-2_1_NN.tar.gz
+ $ tar xvf httpd-2_1_NN.tar
Configurer$ ./configure --prefix=PREFIX +
Compiler$ make
Installer$ make install
Personnaliser$ vi PREFIX/conf/httpd.conf
Tester$ PREFIX/bin/apachectl start +
+ +

NN doit être remplacé par le numéro de version mineure actuel, et + PREFIX par le chemin où le serveur doit être installé. Si + PREFIX n'est pas spécifié, l'installation se fait dans + /usr/local/apache2.

+ +

Chacune des sections du processus de compilation et d'installation est + décrite ci-après, en commençant par les pré-requis à la compilation et à + l'installation d'Apache HTTPD.

+
top
+
+

Pré-requis

+ +

Les pré-requis suivants sont nécessaire pour l'installation d'Apache:

+ +
+
Espace Disque
+
Au moins 50 Mo d'espace disque temporaire sont nécessaires. Après + installation, Apache occupe environ 10 Mo sur le disque. L'espace disque + occupé par une installation complète dépend beaucoup de la configuration + du serveur, ainsi que de la présence éventuelle de modules tiers.
+ +
Compilateur C ANSI et Build
+
Un compilateur C ANSI doit être utilisé. Le compilateur C GNU + (GCC) de la Free Software Foundation + (FSF) est recommandé (la version 2.7.2 convient). En cas + d'absence de GCC, vérifiez que le compilateur fourni avec l'architecture + utilisée est conforme aux normes ANSI. De plus, les outils de constructions + de base, tel make, doivent être présents dans votre + PATH.
+ +
S'assurer que la machine est et reste à l'heure
+
Certains éléments du protocole HTTP sont exprimés en tant qu'heure de + la journée. Aussi est-il important de s'assurer que le système où Apache + doit tourner dispose de mécanismes de synchronisation temporelle. En + général, les programmes ntpdate ou xntpd sont + utilisés; ces programmes implémentent le Network Time Protocol (NTP). + Voir le groupe Usenet comp.protocols.time.ntp et la page NTP pour plus de détails + sur les logiciels NTP et les serveurs de temps publics.
+ +
Perl 5 + [FACULTATIF]
+
Certains des scripts fournis avec Apache, tel apxs ou dbmmanage (qui sont écrits en + Perl) nécessitent l'interpréteur Perl 5 (version 5.003 ou supérieure). + Au cas où le script configure ne trouve pas d'interpréteur + Perl, la compilation sera quand même réalisée sans souci. Seuls ces + scripts ne seront pas utilisables. Si plusieurs interpréteurs Perl sont + installés (par exemple, Perl 4 fourni avec l'OS, et Perl 5 installé par + l'administrateur), il est conseillé de passer l'option + --with-perl afin de garantir que le bon interpréteur est + utilisé par ./configure.
+
+
top
+
+

Télécharger

+ +

Apache est téléchargeable depuis le site de téléchargement + d'Apache qui fournit la liste de plusieurs miroirs. Là sont disponibles + les dernières versions. La plupart des + utilisateurs d'Apache sur des systèmes de type Unix devraient + probablement télécharger et compiler une version à partir du code source. + Le processus de construction (décrit ci-dessous) est facile et + vous permet d'adapter votre serveur pour convenir à vos besoins. + En outre, les versions binaires ne sont souvent pas à jour avec + les dernières versions du code source. Si vous téléchargez une + version binaire, suivez les instructions dans le dossier + INSTALL.bindist à l'intérieur de la distribution.

+ +

Après le téléchargement, il est important de vérifier que les sources + téléchargées sont bien complètes et non modifiées, et ce surtout si un + miroir a été utilisé pour le téléchargement. Ceci peut être fait en + testant l'archive tar téléchargée avec la signature PGP. Cette procédure + s'effectue en 2 étapes. D'abord, il faut récupérer le fichier KEYS du site + de distribution d'Apache. (Pour vérifier que ce fichier KEYS + n'a pas été modifié, une bonne idée peut être d'utiliser un fichier d'une + distribution précédente d'Apache ou d'importer les clés d'un serveur de + clés public.) Les clés peuvent être importées dans le keyring de + l'utilisateur au moyen d'une des commandes (selon la version de PGP):

+ +

$ pgp < KEYS

+ +

ou

+ +

$ gpg --import KEYS

+ +

La prochaine étape est de tester l'archive tar au moyen de la signature + PGP, qui devrait toujours être disponible sur le site principal d'Apache. + Un lien vers cette signature est placé derrière le lien de téléchargement + correspondant ou peut être trouvé dans le répertoire correspondant sur le site de distribution + d'Apache. Le nom de ce fichier est le même que celui de l'archive + source, avec en plus l'extension .asc. La distribution + téléchargée peut alors être vérifiée au moyen de la commande (à nouveau, + selon la version de PGP):

+ +

$ pgp httpd-2_1_NN.tar.gz.asc

+ +

ou

+ +

$ gpg --verify httpd-2_1_NN.tar.gz.asc

+ +

Un message comme celui-ci devrait s'afficher

+ +

Good signature from user "Martin Kraemer + <martin@apache.org>".

+ +

Selon les relations de confiances contenues dans le keyring de + l'utilisateur, un message peut s'afficher, spécifiant que la relation entre + la clé et le signataire ne peut être vérifiée. Ceci n'est pas un problème si + vous ne mettez pas en doute l'authenticité du fichier KEYS.

+
top
+
+

Extraire

+ +

Extraire les sources à partir de l'archive tar est une simple affaire de + décompression et d'extraction tar:

+ +

+$ gzip -d httpd-2_1_NN.tar.gz
+$ tar xvf httpd-2_1_NN.tar +

+ +

Un nouveau répertoire est créé dans le répertoire courant, il contient le + code source de la distribution. Il faut aller dans ce répertoire au moyen + de la commande cd avant de commencer la compilation du + serveur.

+
top
+
+

Configurer l'arborescence source

+ +

L'étape suivante est la configuration de l'arborescence source d'Apache, + pour votre plate-forme et selon les nécessités du site. Cette configuration est + réalisée au moyen du script configure fourni dans le + répertoire racine de la distribution. (Les développeurs qui téléchargent + Apache via CVS devront utiliser les outils autoconf et + libtool avant de passer à la suite. Ceci n'est pas nécessaire + pour les versions officielles.)

+ +

Pour configurer l'arborescence source en utilisant les options par + défaut, tapez ./configure. Pour modifier les valeurs des + options par défaut, configure accepte un grand nombre de + variables et d'options de ligne de commande.

+ +

La plus importante de ces options est le chemin du répertoire où + Apache sera installé, + car Apache doit être configuré pour que cet emplacement fonctionne + correctement. Plusieurs autres options sont disponibles pour + le contrôle fin de l'emplacement des fichiers résultants avec options de + configuration.

+ +

En outre, à ce moment, vous pouvez indiquer quels fonctionnalités + vous voulez inclure dans Apache en ajoutant et/ou en retranchant + des modules. Apache vient avec un ensemble + de modules de Base + inclus par défaut. D'autres modules peuvent être ajoutés en utilisant + l'option --enable-module, où + module est le nom du module avec la chaîne + mod_ coupée et avec les caractères de soulignement + convertis en tirets. Vous pouvez également choisir de compiler + des modules en tant qu'objets partagés (DSOs), + qui peuvent être chargés ou déchargé à l'exécution -- en employant + l'option --enable-module=shared. + De même, vous pouvez retrancher les modules de Base avec l'option + --disable-module. Prenez garde lorsque + vous employez ces options, puisque configure ne peut + vous informer si le module cible n'existe pas; configure + ignorera simplement l'option.

+ +

Il est parfois nécessaire de fournir des + informations supplémentaires au script + configure sur l'emplacement de vos + compilateur, bibliothèques ou dossiers d'en-tête. Ceci se fait en + passant les variables d'environnement ou des options incluses sur la ligne + de commande à configure. Pour plus d'information + sur ce sujet, consultez la page de documentation + configurer.

+ +

L'exemple suivant compile Apache pour être installé + dans /sw/pkg/apache avec un + compilateur et des options de compilation particulières, ainsi que les deux + modules mod_rewrite et mod_speling, qui + pourront être chargés plus tard au moyen des mécanismes DSO:

+ +

+ $ CC="pgcc" CFLAGS="-O2" \
+ ./configure --prefix=/sw/pkg/apache \
+ --enable-rewrite=shared \
+ --enable-speling=shared +

+ +

Une fois lancé, configure peut prendre quelques minutes + pour tester les possibilités du système et produire les fichiers + Makefile qui seront utilisés pour construire le serveur.

+ +

Les détails de toutes les options configure sont + disponibles sur la page de documentation configurer.

+
top
+
+

Compiler

+ +

Les différents composants d'Apache sont à présent prêts à + être compilés, en tapant simplement la commande:

+ +

$ make

+ +

Un peu de patience est requise, une configuration standard met environ 3 + minutes à compiler sur un Pentium III sous Linux 2.2. Ce temps peut + varier largement suivant le matériel utilisé et les modules + selectionnés.

+
top
+
+

Installer

+ +

Il est temps d'installer le 'package' dans le répertoire d'installation + PREFIX configuré auparavant (voir l'option --prefix + ci-dessus) en tapant:

+ +

$ make install

+ +

En cas de mise à jour, l'installation n'écrasera ni les fichiers de + configuration du serveur, ni ses documents.

+
top
+
+

Personnaliser la Configuration

+ +

Il reste à présent à configurer le serveur HTTP Apache, en éditant les + fichiers de configuration placés dans + PREFIX/conf/.

+ +

$ vi PREFIX/conf/httpd.conf

+ +

A consulter : le manuel d'Apache dans + docs/manual/ ou bien http://httpd.apache.org/docs/2.2/ pour la dernière + version de ce manuel, ainsi qu'une référence complète de + toutes les + directives de configuration.

+
top
+
+

Tester

+ +

Une fois configuré, le serveur HTTP Apache peut être + démarré en tapant:

+ +

$ PREFIX/bin/apachectl start

+ +

Vous devriez alors pouvoir tester l'URL http://localhost/. + La page affichée se trouve dans le répertoire + DocumentRoot, habituellement configuré + en tant que PREFIX/htdocs/. + Le serveur peut être arrêté en tapant:

+ +

$ PREFIX/bin/apachectl stop

+
top
+
+

Mise à niveau

+ +

La première étape pour une mise à niveau est de lire + l'annonce de la nouvelle version et le fichier CHANGES + dans la distribution afin de trouver tous les changements qui + peuvent affecter votre site. Si la mise à jour est effectuée + entre deux versions principales (par exemple, de 1.3 à 2.0 ou + de 2.0 à 2.2), attendez-vous à des différences majeures + au moment de la compilation et de l'exécution, exigeant probablement + des ajustements manuels. Tous les modules devront également + être mis à niveau pour tenir compte des changements de l'API.

+ +

La mise à niveau d'une version mineure à une plus récente + (par exemple, de 2.0.55 à 2.0.57) est plus facile. Le processus + make install n'écrasera aucun de vos documents, + fichiers journaux, ou fichiers de configuration existants. + En outre, les développeurs font tous les efforts possibles + pour éviter les changements incompatibles des options + configure, de la configuration d'exécution, + ou de l'API entre les versions mineures. Dans la plupart + des cas vous devriez pouvoir employer une ligne de commande + configure et un fichier de configuration + identiques. De plus, tous vos modules devraient continuer à fonctionner. + (Ceci ne vaut que pour les versions postérieures à 2.0.41; + les versions antérieures ont des changements incompatibles.)

+ +

Si vous avez gardé l'arborescence source de votre dernière + installation, la mise à niveau est encore plus facile. + Le dossier config.nice dans la racine de l'ancienne + arborescence contient la ligne de commande configure + exacte que vous avez utilisée pour configurer l'arborescence des + sources. Pour faire la mise à niveau d'une version à la suivante, + vous devez copier le dossier config.nice dans + l'arborescence des sources de la nouvelle version, l'éditer + pour faire les changements désirés, puis exécuter:

+ +

+ $ ./config.nice
+ $ make
+ $ make install
+ $ PREFIX/bin/apachectl stop
+ $ PREFIX/bin/apachectl start
+

+ +
Vous devriez toujours essayer une + nouvelle version dans un environnement de test avant de la + mettre dans un environnement de production. Par exemple, vous pouvez + installer et exécuter la nouvelle version côte à côte avec l'ancienne + en employant un --prefix et un port différents + (ce qui est possible en ajustant la directive Listen) + dans le but de tester toutes les incompatibilités possibles avant de + faire la mise à niveau finale.
+
+
+

Langues Disponibles:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/install.html.ja.euc-jp b/docs/manual/install.html.ja.euc-jp new file mode 100644 index 00000000..bb4a9334 --- /dev/null +++ b/docs/manual/install.html.ja.euc-jp @@ -0,0 +1,419 @@ + + + +¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë

+
+

Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ + +

¤³¤Îʸ½ñ¤Ç°·¤¦ÈϰϤϡ¢Unix ¤ä Unix ¤ËÎà»÷¤·¤¿¥·¥¹¥Æ¥à¤Ç¤Î + Apache HTTPd ¥µ¡¼¥Ð¤Î¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤¹¡£ Windows ¤Ë¤ª¤±¤ë + ¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë¤Ë´Ø¤·¤Æ¤Ï¡ÖMicrosoft + Windows ¤Ç Apache HTTPd ¤ò»È¤¦¡×¤ò¤´Í÷²¼¤µ¤¤¡£ + ¤½¤Î¾¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ë´Ø¤·¤Æ¤Ï¡Ö¥×¥é¥Ã¥È¥Û¡¼¥à¡×¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

Apache HTTPd ¤Ç¤Ï¾¤Î Open Source ¥×¥í¥¸¥§¥¯¥È¤ÈƱÍÍ¡¢ + ¥Ó¥ë¥É´Ä¶­¹½ÃÛ¤Ë libtool ¤È autoconf + ¤ò»È¤¦¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó¤«¤é¤½¤Î¼¡¤Î¥Ð¡¼¥¸¥ç¥ó¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë + (2.2.50 ¤«¤é 2.2.51 ¤ØÅù) ¾ì¹ç¤Ï¡¢¤Þ¤º + ¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò¤´Í÷²¼¤µ¤¤¡£

+ +
+ +
top
+
+

³µÍ× (¤»¤Ã¤«¤Á¤Ê¿Í¸þ¤±)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¥À¥¦¥ó¥í¡¼¥É$ lynx http://httpd.apache.org/download.cgi +
Ÿ³«$ gzip -d httpd-NN.tar.gz
+ $ tar xvf httpd-NN.tar
+ $ cd httpd-NN
ÀßÄê$ ./configure --prefix=PREFIX +
¥³¥ó¥Ñ¥¤¥ë$ make
¥¤¥ó¥¹¥È¡¼¥ë$ make install
¥«¥¹¥¿¥Þ¥¤¥º$ vi PREFIX/conf/httpd.conf
¥Æ¥¹¥È$ PREFIX/bin/apachectl -k start +
+ +

NN ¤ÏºÇ¿·¤Î¥Ð¡¼¥¸¥ç¥ó¥Ê¥ó¥Ð¡¼¤Ë¡¢ + PREFIX ¤Ï¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¥µ¡¼¥Ð¤Ç¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ñ¥¹¤Ë¡¢ + ÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£PREFIX ¤ò»ØÄꤷ¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Î /usr/local/apache2 ¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Apache HTTP ¥µ¡¼¥Ð¤Î¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë¤ËɬÍפʤâ¤Î¤ò¤Ï¤¸¤á¤È¤·¤Æ¡¢ + ¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë¤Ë¤Ä¤¤¤Æ¤Ï¡¢¼¡¤Ë¾Ü¤·¤¯µ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+
top
+
+

ɬÍפʤâ¤Î

+ +

Apache HTTPd ¤Î¥Ó¥ë¥É¤Ë¤Ï¼¡¤Î¤â¤Î¤¬É¬ÍפǤ¹:

+ +
+
¥Ç¥£¥¹¥¯¥¹¥Ú¡¼¥¹
+
¥Ç¥£¥¹¥¯¤Ë¾¯¤Ê¤¯¤È¤â 50 MB ¤Î°ì»þŪ¤Ê¶õ¤­ÍÆÎ̤¬¤¢¤ë¤è¤¦¤Ë + µ¤¤òÉÕ¤±¤Æ¤¯¤À¤µ¤¤¡£¥¤¥ó¥¹¥È¡¼¥ë¸å¤Ï Apache ¤Ï 10 MB ÄøÅ٤Π+ ¥Ç¥£¥¹¥¯¥¹¥Ú¡¼¥¹¤òÀê¤á¤Þ¤¹¡£¼ÂºÝ¤ËɬÍפˤʤë¥Ç¥£¥¹¥¯¥¹¥Ú¡¼¥¹¤Ï¡¢ + ÀßÄꥪ¥×¥·¥ç¥ó¤ä¥µ¡¼¥É¥Ñ¡¼¥Æ¥£¡¼À½¥â¥¸¥å¡¼¥ë¤ò¤É¤¦ÁªÂò¤¹¤ë¤«¤Ë¤è¤Ã¤Æ + Â礭¤¯ÊѤï¤ë¤Ç¤·¤ç¤¦¡£
+ +
ANSI-C ¥³¥ó¥Ñ¥¤¥é¤È¥Ó¥ë¥É¥·¥¹¥Æ¥à
+
ANSI-C ¥³¥ó¥Ñ¥¤¥é¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤ª¤¤¤Æ²¼¤µ¤¤¡£¤ªÁ¦¤á¤Ï Free Software Foundation (FSF) + ¤Ë¤è¤ë GNU C + compiler (GCC) ¤Ç¤¹¡£GCC ¤¬¤Ê¤¤¾ì¹ç¤Ï¡¢ + ¾¯¤Ê¤¯¤È¤âÄ󶡤µ¤ì¤Æ¤¤¤ë¥³¥ó¥Ñ¥¤¥é¤¬ ANSI ½àµò¤Ç¤¢¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤ª¤¤¤Æ²¼¤µ¤¤¡£ + ¤½¤ì¤«¤é¡¢ÊÑ¿ô PATH ¤Ë¤Ï make + ¤È¤¤¤Ã¤¿´ðËÜŪ¤Ê¥Ó¥ë¥É¥Ä¡¼¥ë¤¬´Þ¤Þ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
+ +
»þ¹ï¤òÀµ³Î¤Ë¤¹¤ë
+
HTTP ¥×¥í¥È¥³¥ë¤ÎÍ×ÁǤÏÆü»þ¤Î»þ¹ï¤Çɽ¸½¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢ + Àµ³Î¤Ê»þ¹ï¤Ë¥·¥ó¥¯¥í¤µ¤»¤ëµ¡Ç½¤ò¥·¥¹¥Æ¥à¤ËÀßÄꤹ¤ë¤³¤È¤ò¶ãÌ£¤·¤Æ¤ß¤Æ²¼¤µ¤¤¡£ + Network Time Protocol (NTP) ¤ò¥Ù¡¼¥¹¤È¤·¤¿ ntpdate ¤ä xntpd ¥×¥í¥°¥é¥à¤¬ + ¤³¤ÎÌÜŪ¤Ë¤è¤¯ÍѤ¤¤é¤ì¤Þ¤¹¡£NTP ¥½¥Õ¥È¥¦¥§¥¢¤ä¸ø³« NTP + ¥µ¡¼¥Ð¤Ë´Ø¤¹¤ë¾ÜºÙ¤Ï¡¢NTP ¥Û¡¼¥à¥Ú¡¼¥¸ ¤ò¤´Í÷²¼¤µ¤¤¡£
+ +
Perl 5 + [¥ª¥×¥·¥ç¥ó]
+
Ä󶡤µ¤ì¤Æ¤¤¤ë¥¹¥¯¥ê¥×¥È´ö¤Ä¤«¡¢Î㤨¤Ð apxs ¤ä + dbmmanage ¤Ï + Perl ¤Ç½ñ¤«¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢Perl + 5 ¥¤¥ó¥¿¥×¥ê¥¿¤¬É¬Íפˤʤê¤Þ¤¹ (5.003 °Ê¹ß)¡£ + Perl ¥¤¥ó¥¿¥×¥ê¥¿¤òÊ£¿ô¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¤¤ë (¤¿¤È¤¨¤ÐÁ´ÂΤΥ·¥¹¥Æ¥à¤Î°ìÉô + ¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë Perl 4 ¤È¡¢¼«Ê¬¤ÇÄɲäǥ¤¥ó¥¹¥È¡¼¥ë¤·¤¿ + Perl 5 ¤¬¤¢¤ë¤Ê¤É¤Î) ¾ì¹ç¡¢--with-perl ¥ª¥×¥·¥ç¥ó (²¼µ­»²¾È) + ¤ò»È¤Ã¤Æ configure ¤¬°Õ¿Þ¤·¤¿¤â¤Î¤ò»È¤¦¤è¤¦¤Ë + ÌÀ¼¨Åª¤Ë»ØÄꤹ¤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£ + configure ¥¹¥¯¥ê¥×¥È¤Ç Perl 5 ¥¤¥ó¥¿¥×¥ê¥¿¤¬ + ¸«¤Ä¤«¤é¤Ê¤¤¾ì¹ç¤Ï¡¢¤³¤Î±Æ¶Á¤ò¼õ¤±¤ë¥µ¥Ý¡¼¥È¥¹¥¯¥ê¥×¥È¤¬»È¤¨¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£ + ¤â¤Á¤í¤ó¡¢Apache HTTPd ¤Î¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë¤ÏÌäÂê¤Ê¤¯¹Ô¤¨¤Þ¤¹¡£
+ +
apr/apr-util >= 1.2
+
apr ¤È apr-util ¤Ï Apache HTTPd + ¥½¡¼¥¹¥ê¥ê¡¼¥¹¤ËƱº­¤µ¤ì¤Æ¤¤¤Þ¤¹¤·¡¢¤É¤ó¤Ê´Ä¶­¤Ç¤â¤Û¤ÜÌäÂê¤Ê¤¯ + »È¤¨¤ë¤Ï¤º¤Ç¤¹¡£¤¿¤À¤· apr ¤È apr-util + ¤Î¥Ð¡¼¥¸¥ç¥ó 1.0 ¤ä 1.1 ¤¬¥·¥¹¥Æ¥à¤Î°ìÉô¤È¤·¤Æ´û¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢ + apr/apr-util ¤ò 1.2 ¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¤«¡¢ + httpd ¤ò³ÖÎ¥¤·¤¿´Ä¶­¤Ç¥Ó¥ë¥É¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¥Ð¥ó¥É¥ë¤µ¤ì¤Æ¤¤¤ë apr/apr-util ¤ò»È¤Ã¤Æ + ¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¾ì¹ç¤Ï¡¢¤³¤ì¤é¤ò¼êÆ°¤Ç¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹ : +

+ # Build and install apr 1.2
+ cd srclib/apr
+ ./configure --prefix=/usr/local/apr-httpd/
+ make
+ make install
+
+ # Build and install apr-util 1.2
+ cd ../apr-util
+ ./configure --prefix=/usr/local/apr-util-httpd/ + --with-apr=/usr/local/apr-httpd/
+ make
+ make install
+
+ # Configure httpd
+ cd ../../
+ ./configure --with-apr=/usr/local/apr-httpd/ + --with-apr-util=/usr/local/apr-util-httpd/ +

+
+
+
top
+
+

¥À¥¦¥ó¥í¡¼¥É

+ +

Apache HTTP ¥µ¡¼¥Ð¤Ï Apache HTTP + ¥µ¡¼¥Ð¥À¥¦¥ó¥í¡¼¥É¥µ¥¤¥È¤«¤é¥À¥¦¥ó¥í¡¼¥É¤Ç¤­¤Þ¤¹¤·¡¢ + Ʊ¤¸¾ì½ê¤Ë´ö¤Ä¤«¤Î¥ß¥é¡¼¥µ¥¤¥È¤â¥ê¥¹¥È¤·¤Æ¤¤¤Þ¤¹¡£ + UNIX ¤ËÎà»÷¤¹¤ë¥·¥¹¥Æ¥à¤Ç Apache HTTPd ¤ò»È¤¦¥æ¡¼¥¶¤Ï¡¢¥½¡¼¥¹¤ò + ¥À¥¦¥ó¥í¡¼¥É¤·¤Æ¥Ó¥ë¥É¤·¤¿¤Û¤¦¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£ + ¥Ó¥ë¥É¤Î¼ê½ç¡Ê²¼µ­¡Ë¤Ï´Êñ¤Ç¤¹¤·¡¢¤½¤Î¤ª¤«¤²¤Ç¥Ë¡¼¥º¤Ë + ¸«¹ç¤Ã¤¿¥«¥¹¥¿¥Þ¥¤¥º¤ò´Êñ¤Ë¤Ç¤­¤Þ¤¹¡£ + ¤µ¤é¤Ë¡¢¥Ð¥¤¥Ê¥ê¤Î¥ê¥ê¡¼¥¹¤Ï¥½¡¼¥¹¥ê¥ê¡¼¥¹¤è¤ê¤â + ÃÙ¤ì¤Æ¤¤¤ë¤³¤È¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£ + ¤½¤ì¤Ç¤â¥Ð¥¤¥Ê¥ê¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤ÎÃæ¤Ë¤¢¤ë INSSTALL.bindist + ¥Õ¥¡¥¤¥ë¤ÎÀâÌÀ¤Ë½¾¤Ã¤Æ¤¯¤À¤µ¤¤¡£

+ +

¥À¥¦¥ó¥í¡¼¥É¸å¡¢¥À¥¦¥ó¥í¡¼¥É¤·¤¿¤â¤Î¤¬ Apache HTTP + ¥µ¡¼¥Ð¤Î´°Á´¤Ç²þã⤵¤ì¤Æ¤¤¤Ê¤¤¥Ð¡¼¥¸¥ç¥ó¤Ç¤¢¤ë¤³¤È¤ò + ¸¡¾Ú¤¹¤ë¤³¤È¤¬½ÅÍפǤ¹¡£¤³¤ì¤Ï¥À¥¦¥ó¥í¡¼¥É¤·¤¿ tarball ¤Î PGP ½ð̾¤ò + ¥Æ¥¹¥È¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¸¡¾Ú¤·¤Þ¤¹¡£ + ¤³¤Î¼ê½ç¤Î¾ÜºÙ¤Ï ¥À¥¦¥ó¥í¡¼¥É + ¥Ú¡¼¥¸ ¤Ë¤¢¤ê¡¢¤µ¤é¤Ë¾Ü¤·¤¤Îã¤Ï PGP ¤Î»ÈÍÑ + ¤Ëµ­ºÜ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +
top
+
+

Ÿ³«

+ +

Apache HTTPd ¤Î tarball + ¤«¤é¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤òŸ³«¤·¤Æ¼è¤ê½Ð¤¹¤È¤Ï¡¢ + ñ¤Ê¤ë°µ½Ì¤Î²ò½ü¤È tar ¤ÎŸ³«¤Ç¤¹:

+ +

+ $ gzip -d httpd-NN.tar.gz
+ $ tar xvf httpd-NN.tar +

+ +

ÇÛÉÛÍѤΥ½¡¼¥¹¥³¡¼¥É¤¬¤¢¤ë¸½ºß¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Î²¼¤Ë¡¢ + ¿·¤·¤¤¥Ç¥£¥ì¥¯¥È¥ê¤¬ºî¤é¤ì¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤ò¥³¥ó¥Ñ¥¤¥ë¤¹¤ëÃʳ¬¤Ë¿Ê¤àÁ°¤Ë¡¢¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë + cd ¤Ç°ÜÆ°¤·¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

¥½¡¼¥¹¥Ä¥ê¡¼¤òÀßÄꤹ¤ë

+ +

¼¡¤Î¥¹¥Æ¥Ã¥×¤Ï¡¢¤¢¤Ê¤¿¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤È + ¸Ä¿ÍŪ¤ÊÍ×µá¤Ë¹ç¤¦¤è¤¦¤Ë Apache HTTPd + ¥½¡¼¥¹¥Ä¥ê¡¼¤òÀßÄꤹ¤ë¤³¤È¤Ç¤¹¡£ + ¤³¤ì¤ÏÇÛÉۥǥ£¥ì¥¯¥È¥ê¤Î¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë¡¢ + configure + ¥¹¥¯¥ê¥×¥È¤Ç¹Ô¤Ê¤¤¤Þ¤¹¡£ + (Apache HTTPd ¥½¡¼¥¹¥Ä¥ê¡¼¤Î̤¥ê¥ê¡¼¥¹ + ÈǤò¥À¥¦¥ó¥í¡¼¥É¤·¤¿³«È¯¼Ô¤Ï¡¢¼¡¤Î¥¹¥Æ¥Ã¥×¤Ë¿Ê¤àÁ°¤Ë + autoconf ¤Èlibtool + ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ buildconf + ¤ò¼Â¹Ô¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¸ø¼°¥ê¥ê¡¼¥¹¤Ç¤Ï¤³¤Îºî¶È¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£)

+ +

¥Ç¥Õ¥©¥ë¥È¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¥½¡¼¥¹¥Ä¥ê¡¼¤òÁ´¤ÆÀßÄꤹ¤ë + ¤Î¤Ç¤¢¤ì¤Ð¡¢Ã±½ã¤Ë ./configure ¤È¥¿¥¤¥×¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¥Ç¥Õ¥©¥ë¥È¥ª¥×¥·¥ç¥ó¤òÊѹ¹¤Ç¤­¤ë¤è¤¦¤Ë¡¢configure + ¤Ë¤ÏÍÍ¡¹¤ÊÊÑ¿ô¤ä¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤¬ÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

ºÇ¤â½ÅÍפʥª¥×¥·¥ç¥ó¤Ï¡¢Apache HTTPd ¤¬¤³¤Î¸å¤Ç¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤ë°ÌÃÖ + --prefix ¤Ç¤¹¡£Apache HTTPd ¤Ï¡¢¤³¤Î¥¤¥ó¥¹¥È¡¼¥ë°ÌÃÖ¤Ë + ¤ª¤¤¤ÆÀµ¾ï¤ËÆ°ºî¤¹¤ë¤è¤¦¤ËÀßÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤é¤Ç¤¹¡£ + ¤µ¤é¤Ë¾ÜºÙ¤Ê¥Õ¥¡¥¤¥ë°ÌÃÖ¤ÎÀ©¸æ¤ÏÄɲäΠÀßÄꥪ¥×¥·¥ç¥ó + ¤Ç¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤Î»þÅÀ¤Ç¡¢¥â¥¸¥å¡¼¥ë ¤òÍ­¸ú¤Ë¤·¤¿¤ê + ̵¸ú¤Ë¤·¤¿¤ê¤¹¤ë¤³¤È¤Ç Apache HTTPd ËÜÂΤ˴ޤޤì¤ë µ¡Ç½ + ¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£Apache HTTPd ËÜÂΤˤϥǥե©¥ë¥È¤Ç¡¢¥â¥¸¥å¡¼¥ë¤Î Base ¥»¥Ã¥È¤¬ + ´Þ¤Þ¤ì¤Þ¤¹¡£¤½¤Î¾¤Î¥â¥¸¥å¡¼¥ë¤Ï + --enable-module ¥ª¥×¥·¥ç¥ó¤Ç + Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤³¤Ç module ¤Ï¥â¥¸¥å¡¼¥ë¤Î̾Á°¤Ç¡¢ + ¤Ä¤Þ¤ê¤½¤ì¤Ï¥â¥¸¥å¡¼¥ë¤Î̾Á°¤«¤é mod_ ʸ»úÎó¤ò¼è¤ê½ü¤¤¤¿¸å¤Ë + ¥¢¥ó¥À¡¼¥¹¥³¥¢¤ò¥À¥Ã¥·¥å¤ÇÃÖ´¹¤·¤¿Ê¸»úÎó¤Ç¤¹¡£ + ¤³¤ì¤È¤ÏÊ̤ÎÊýË¡¤Ç --enable-module=shared + ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¡¢¥â¥¸¥å¡¼¥ë¤ò + ¥·¥§¥¢¡¼¥É¥ª¥Ö¥¸¥§¥¯¥È (DSO) -- ¼Â¹Ô»þ¤Ë¥í¡¼¥É¤·¤¿¤ê + ¥¢¥ó¥í¡¼¥É¤·¤¿¤ê¤Ç¤­¤ë·Á¼° -- ¤È¤·¤Æ¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + ƱÍͤˡ¢--disable-module ¥ª¥×¥·¥ç¥ó¤Ç + Base ¥â¥¸¥å¡¼¥ë¤ò̵¸ú²½¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤é¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¤¤¤ë¤È¤­¤Ë¡¢¤â¤·»ØÄꤷ¤¿¥â¥¸¥å¡¼¥ë¤¬Â¸ºß¤·¤Ê¤¯¤Æ¤â + configure ¤Ï·Ù¹ð¤ò¾å¤²¤ë¤³¤È¤Ê¤¯¡¢Ã±½ã¤Ë¥ª¥×¥·¥ç¥ó¤ò + ̵»ë¤¹¤ë¤³¤È¤Ëµ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£

+ +

¾åµ­¤Ë²Ã¤¨¤Æ¡¢configure ¥¹¥¯¥ê¥×¥È¤Ë¡¢ + ¥³¥ó¥Ñ¥¤¥é¡¢¥é¥¤¥Ö¥é¥ê¡¢¥Ø¥Ã¥À¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ¤òÄɲþðÊó¤È¤·¤ÆÅϤ¹ + ɬÍפ¬¤¢¤ë¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£¤³¤Î¤è¤¦¤Ê¾ì¹ç¤Ë¤Ï¡¢´Ä¶­ÊÑ¿ô¤¢¤ë¤¤¤Ï + ¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Ç configure ¤ËÅϤ·¤Þ¤¹¡£ + ¾ÜºÙ¤Ë´Ø¤·¤Æ¤Ï configure ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸ + ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£

+ +

¤Á¤ç¤Ã¤È¤É¤ó¤Ê¤³¤È¤¬¤Ç¤­¤ë¤«¤ò¸«¤»¤Þ¤·¤ç¤¦¡£ + ¤³¤³¤Çŵ·¿Åª¤ÊÎã¤È¤·¤Æ¡¢/sw/pkg/apache + ¤È¤¤¤¦¥¤¥ó¥¹¥È¡¼¥ë¥Ä¥ê¡¼¤Ç¥³¥ó¥Ñ¥¤¥é¤È¥Õ¥é¥°¤ò»ØÄꤷ¤Æ¡¢ + ¤µ¤é¤ËÆó¤Ä¤ÎÄɲå⥸¥å¡¼¥ë mod_rewrite ¤È + mod_speling ¤ò¸å¤Ç DSO + ¥á¥«¥Ë¥º¥à¤Ç¥í¡¼¥É¤¹¤ë¤è¤¦¤Ë¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤ß¤Þ¤¹:

+ +

+ $ CC="pgcc" CFLAGS="-O2" \
+ ./configure --prefix=/sw/pkg/apache \
+ --enable-rewrite=shared \
+ --enable-speling=shared +

+ +

configure ¤ò¼Â¹Ô¤·¤¿¤é¡¢¥·¥¹¥Æ¥à¤Îµ¡Ç½¤ò + ¥Æ¥¹¥È¤·¤¿¤ê¡¢¸å¤Ç¥µ¡¼¥Ð¤ò¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤¿¤á¤ËɬÍ×¤Ê Makefile + ¤òÀ¸À®¤·¤¿¤ê¤¹¤ë¤Î¤Ë¿ôʬ´Ö¤«¤«¤ë¤Ç¤·¤ç¤¦¡£

+ +

¸Ä¡¹¤Î configure ¥ª¥×¥·¥ç¥ó¤Î¾ÜºÙ¤Ë´Ø¤·¤Æ¤Ï + configure ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸ + ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£

+
top
+
+

¥Ó¥ë¥É

+ +

¤³¤ì¤Ç Apache HTTPd ¤ÎÍÍ¡¹¤Ê¥Ñ¡¼¥Ä¤ò¥Ó¥ë¥É¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¼¡¤Î¥³¥Þ¥ó¥É¤òñ½ã¤Ë¼Â¹Ô¤¹¤ë¤À¤±¤Ç¤¹:

+ +

$ make

+ +

´ðËÜŪ¤ÊÀßÄê¤ò¤¹¤ë¤Î¤Ë¿ôʬ¤«¤«¤ê¤Þ¤¹¤¬¡¢ + ¤¢¤é¤«¤¸¤á¤´Î»¾µ¤¯¤À¤µ¤¤¡£ + ¤Þ¤¿¡¢»þ´Ö¤Ï¥Ï¡¼¥É¥¦¥§¥¢¤äÍ­¸ú¤Ë¤·¤¿¥â¥¸¥å¡¼¥ë¤Î¿ô¤Ë + Â礭¤¯°Í¸¤¹¤ë¤Ç¤·¤ç¤¦¡£

+
top
+
+

¥¤¥ó¥¹¥È¡¼¥ë

+ +

¤µ¤Æ¡¢ÀßÄꤷ¤¿¥¤¥ó¥¹¥È¡¼¥ë PREFIX + (Á°½Ò¤Î --prefix ¥ª¥×¥·¥ç¥ó¤ò»²¾È) + °Ê²¼¤Ë¥Ñ¥Ã¥±¡¼¥¸¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëÃʳ¬¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + ¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤:

+ +

$ make install

+ +

¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¾ì¹ç¤Ï¡¢¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤ä + ¥É¥­¥å¥á¥ó¥È¥Õ¥¡¥¤¥ë¤Î¾å½ñ¤­¤Ï¹Ô¤¤¤Þ¤»¤ó¡£

+
top
+
+

¥«¥¹¥¿¥Þ¥¤¥º

+ +

¼¡¤Ë PREFIX/conf/ °Ê²¼¤Ë¤¢¤ë ÀßÄê¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¤Æ¡¢ + Apache HTTP ¥µ¡¼¥Ð¤ò¥«¥¹¥¿¥Þ¥¤¥º¤·¤Þ¤¹¡£

+ +

$ vi PREFIX/conf/httpd.conf

+ +

docs/manual/ ¤Î Apache HTTP ¥µ¡¼¥Ð¥Þ¥Ë¥å¥¢¥ë¤ò¤¶¤Ã¤È¸«¤Æ¤¯¤À¤µ¤¤¡£ + ¤Þ¤¿¤Ï¡¢http://httpd.apache.org/docs/2.2/ + ¤Ë¤¢¤ë¥Þ¥Ë¥å¥¢¥ëºÇ¿·ÈÇ¡¢ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ËÅö¤¿¤Ã¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

¥Æ¥¹¥È

+ +

¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ Apache HTTP ¥µ¡¼¥Ð¤ò³«»Ï¤Ç¤­¤Þ¤¹:

+ +

$ PREFIX/bin/apachectl -k start

+ +

URL http://localhost/ ¤òÄ̤·¤ÆºÇ½é¤Î¥É¥­¥å¥á¥ó¥È¤ËÂФ¹¤ë + ¥ê¥¯¥¨¥¹¥È¤òȯ¹Ô¤¹¤ë»ö¤¬¤Ç¤­¤ë¤Ï¤º¤Ç¤¹¡£¤³¤ì¤Ç¸«¤¨¤ë + ¥¦¥§¥Ö¥Ú¡¼¥¸¤Ï DocumentRoot + °Ê²¼¤ËÃÖ¤«¤ì¤¿¤â¤Î¤Ç¡¢Ä̾ï¤Ï + PREFIX/htdocs/ ¤Ç¤·¤ç¤¦¡£ + ¥µ¡¼¥Ð¤òºÆ¤ÓÄä»ß¤¹¤ë¤Ë¤Ï¡¢ + ¼¡¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Þ¤¹:

+ +

$ PREFIX/bin/apachectl -k stop

+
top
+
+

¥¢¥Ã¥×¥°¥ì¡¼¥É

+ +

¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ç¤Þ¤º¹Ô¤Ê¤¦¤Ù¤­¤³¤È¤Ï¡¢¥ê¥ê¡¼¥¹¥¢¥Ê¥¦¥ó¥¹¤È + ¥½¡¼¥¹¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤ËÆþ¤Ã¤Æ¤¤¤ë CHANGES ¤òÆɤó¤Ç¡¢ + ¼«¿È¤Î¥µ¥¤¥È¤ËÂФ·¤Æ±Æ¶Á¤òµÚ¤Ü¤¹Êѹ¹ÅÀ¤òõ¤¹¤³¤È¤Ç¤¹¡£ + ¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹´Ö¤ÎÊѹ¹¤ò¤¹¤ë¾ì¹ç (Î㤨¤Ð 1.3 ¤«¤é 2.0 ¤Ø¡¢2.0 ¤«¤é 2.2 ¤Ø) + ¤Ï¡¢¥³¥ó¥Ñ¥¤¥ë»þ¤ä¼Â¹Ô»þ¤ÎÀßÄê¤ËÂ礭¤Êº¹°Û¤¬¤¢¤ë¤Ç¤·¤ç¤¦¤«¤é¡¢ + ¼êÆ°¤ÎÄ´À°¤¬É¬Íפˤʤë¤Ç¤·¤ç¤¦¡£¥â¥¸¥å¡¼¥ë¤âÁ´¤Æ¡¢API + ¤ÎÊѹ¹¤Ë¹ç¤ï¤»¤ë¤¿¤á¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¬É¬Íפˤʤë¤Ç¤·¤ç¤¦¡£

+ +

¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó¤«¤é¼¡¤Î¥Ð¡¼¥¸¥ç¥ó¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¾ì¹ç + (Î㤨¤Ð 2.2.55 ¤«¤é 2.2.57 ¤Ø) ¤Ï¡¢¤â¤Ã¤È´Êñ¤Ç¤¹¡£ + make install ¤ò¼Â¹Ô¤·¤Æ¤âº£¤¢¤ë¥É¥­¥å¥á¥ó¥È¡¢ + ¥í¥°¥Õ¥¡¥¤¥ë¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤Ï¾å½ñ¤­¤µ¤ì¤Þ¤»¤ó¡£ + ¤µ¤é¤Ë¡¢¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó´Ö¤Ç¤Ï configure ¥ª¥×¥·¥ç¥ó¡¢ + ¼Â¹Ô»þ¤ÎÀßÄê¡¢¥â¥¸¥å¡¼¥ë API ¤ËÉÔÀ°¹ç¤¬µ¯¤³¤é¤Ê¤¤¤è¤¦¤Ë¡¢ + ³«È¯¼Ô¤ÏºÇÂç¸Â¤ÎÅØÎϤò¤·¤Æ¤¤¤Þ¤¹¡£ + ÂçÄñ¤Î¾ì¹ç¡¢Æ±°ì¤Î configure ¥³¥Þ¥ó¥É¥é¥¤¥ó¡¢ + Ʊ°ì¤ÎÀßÄê¥Õ¥¡¥¤¥ë¡¢¥â¥¸¥å¡¼¥ëÁ´¤Æ¤¬Àµ¾ï¤ËÆ°ºî¤¹¤ë¤Ï¤º¤Ç¤¹¡£

+ +

¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó¤Ç¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¾ì¹ç¤Ï¡¢ + ´û¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¥µ¡¼¥Ð¤Î build ¥Ç¥£¥ì¥¯¥È¥êÆ⤫¡¢ + °ÊÁ°¥¤¥ó¥¹¥È¡¼¥ë¤Ë»È¤Ã¤¿¥½¡¼¥¹¥³¡¼¥É¥Ä¥ê¡¼¤ÎºÇ¾å°Ì¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ë¤¢¤ë¡¢ + config.nice ¥Õ¥¡¥¤¥ë¤òõ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤Î¥Õ¥¡¥¤¥ë¤Ë¤Ï¥½¡¼¥¹¥Ä¥ê¡¼¤òÀßÄꤷ¤¿»þ¤Ë»È¤Ã¤¿ + configure ¥³¥Þ¥ó¥É¥é¥¤¥ó¤¬¡¢¤½¤Î¤Þ¤ÞÆþ¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¼¡¤Î¥Ð¡¼¥¸¥ç¥ó¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¾ì¹ç¤Ï config.nice + ¥Õ¥¡¥¤¥ë¤ò¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤Î¥½¡¼¥¹¥Ä¥ê¡¼¤Ë¥³¥Ô¡¼¤·¡¢ + ɬÍפǤ¢¤ì¤Ð¤½¤ì¤òÊÔ½¸¤·¤¿¸å¤Ë¡¢¼¡¤Î¤è¤¦¤Ë¼Â¹Ô¤·¤Þ¤¹¡£

+ +

+ $ ./config.nice
+ $ make
+ $ make install
+ $ PREFIX/bin/apachectl -k graceful-stop
+ $ PREFIX/bin/apachectl -k start
+

+ +
¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤ò»ÈÍѤ¹¤ë¾ì¹ç¤Ï¡¢ + ¼ÂºÝ¤Ë±¿ÍѤò»Ï¤á¤ëÁ°¤Ë¡¢É¬¤º¼«Ê¬ÍѤδĶ­¤Ç¥Æ¥¹¥È¤¹¤Ù¤­¤Ç¤¹¡£ + ºÇ½ªÅª¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ëÁ°¤Ë¡¢Èó¸ß´¹À­¤¬¤Ê¤¤¤«¤ò¥Æ¥¹¥È¤¹¤ë¤¿¤á¤Ë¡¢ + Î㤨¤Ð¡¢°Û¤Ê¤ë --prefix ¤È°Û¤Ê¤ë¥Ý¡¼¥È (Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤷ¤Þ¤¹) + ¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤Ë±Æ¶Á¤òÍ¿¤¨¤º¤Ë¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤ò + ¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢¼Â¹Ô¤Ç¤­¤Þ¤¹¡£
+
+
+

Available Languages:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/install.html.ko.euc-kr b/docs/manual/install.html.ko.euc-kr new file mode 100644 index 00000000..9b7470bf --- /dev/null +++ b/docs/manual/install.html.ko.euc-kr @@ -0,0 +1,360 @@ + + + +ÄÄÆÄÀÏ°ú ¼³Ä¡ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

ÄÄÆÄÀÏ°ú ¼³Ä¡

+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + fr  | + ja  | + ko 

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

ÀÌ ¹®¼­´Â À¯´Ð½º¿Í À¯´Ð½º·ù ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÏ°í + ¼³Ä¡ÇÏ´Â °Í¸¸À» ´Ù·é´Ù. À©µµ¿ìÁî¿¡¼­ ÄÄÆÄÀÏÇÏ°í ¼³Ä¡ÇÏ´Â ¹æ¹ýÀº + ¸¶ÀÌÅ©·Î¼ÒÇÁÆ® À©µµ¿ìÁî¿¡¼­ + ¾ÆÆÄÄ¡ »ç¿ëÀ» Âü°íÇ϶ó. ´Ù¸¥ Ç÷¡Æû¿¡ ´ëÇؼ­´Â Ç÷¡Æû ¹®¼­¸¦ Âü°íÇ϶ó.

+ +

¾ÆÆÄÄ¡ 2.0ÀÇ ±¸¼º°ú ¼³Ä¡ ȯ°æÀº 1.3°ú ¸Å¿ì ´Ù¸£´Ù. + ¾ÆÆÄÄ¡ 1.3Àº ½¬¿î ¼³Ä¡¸¦ À§ÇØ ÀÚü ½ºÅ©¸³Æ®¸¦ »ç¿ëÇß´Ù. + ¾ÆÆÄÄ¡ 2.0Àº ÀÌÁ¦ ´Ù¸¥ ¿©·¯ ¿ÀǼҽº ÇÁ·ÎÁ§Æ®¿Í ºñ½ÁÇÑ È¯°æÀ» + ¸¸µé±âÀ§ÇØ libtool°ú autoconf¸¦ + »ç¿ëÇÑ´Ù.

+ +

¸¸¾à ÀÛÀº ¹öÀüÀ» ÇÑ´Ü°è ¾÷±×·¹À̵åÇÑ´Ù¸é (¿¹¸¦ µé¾î, + 2.0.50¿¡¼­ 2.0.51), ¾÷±×·¹À̵å + ÀåÀ¸·Î ¹Ù·Î °¡±æ ¹Ù¶õ´Ù.

+ +
+ +
top
+
+

¼º¹Ì ±ÞÇÑ »ç¶÷À» À§ÇÑ °³¿ä

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
´Ù¿î·Îµå$ lynx http://httpd.apache.org/download.cgi +
¾ÐÃà Ç®±â$ gzip -d httpd-2_1_NN.tar.gz
+ $ tar xvf httpd-2_1_NN.tar
±¸¼º$ ./configure --prefix=PREFIX +
ÄÄÆÄÀÏ$ make
¼³Ä¡$ make install
¼³Á¤$ vi PREFIX/conf/httpd.conf
°Ë»ç$ PREFIX/bin/apachectl start +
+ +

NNÀº ÇöÀç ÀÛÀº ¹öÀü ¼ýÀÚ·Î, PREFIX´Â + ¼­¹ö°¡ ¼³Ä¡µÉ ÆÄÀϽýºÅÛ °æ·Î·Î ´ëüÇØ¾ß ÇÑ´Ù. PREFIX¸¦ + ÁöÁ¤ÇÏÁö ¾ÊÀ¸¸é ±âº»°ªÀ¸·Î /usr/local/apache2¸¦ + »ç¿ëÇÑ´Ù.

+ +

¾Æ·¡´Â ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ÄÄÆÄÀÏÇÏ°í ¼³Ä¡ÇϱâÀ§ÇÑ ¿ä±¸»çÇ׺ÎÅÍ + ÄÄÆÄÀÏ°ú ¼³Ä¡ °úÁ¤À» °¢°¢ ÀÚ¼¼È÷ ¼³¸íÇÑ´Ù.

+
top
+
+

¿ä±¸»çÇ×

+ +

¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇϱâÀ§ÇØ ´ÙÀ½°ú °°Àº °ÍµéÀÌ ÇÊ¿äÇÏ´Ù:

+ +
+
µð½ºÅ© °ø°£
+
µð½ºÅ© ¿©À¯°ø°£ÀÌ ÃÖ¼Ò 50 MB ÀÌ»óÀÎÁö È®ÀÎÇ϶ó. + ¼³Ä¡ÈÄ ¾ÆÆÄÄ¡´Â ¾à 10 MBÀÇ µð½ºÅ© °ø°£À» Â÷ÁöÇÑ´Ù. + ½ÇÁ¦ ÇÊ¿äÇÑ µð½ºÅ© °ø°£Àº ¼±ÅÃÇÑ ±¸¼º ¿É¼Ç°ú Ãß°¡ ¸ðµâ¿¡ + µû¶ó »ó´çÈ÷ Â÷ÀÌ°¡ ³­´Ù.
+ +
ANSI-C ÄÄÆÄÀÏ·¯¿Í ÄÄÆÄÀÏ ½Ã½ºÅÛ
+
ANSI-C ÄÄÆÄÀÏ·¯°¡ ¼³Ä¡µÇÀÖ´ÂÁö È®ÀÎÇ϶ó. Free Software Foundation (FSF)ÀÇ + GNU C + compiler (GCC)¸¦ ÃßõÇÑ´Ù. (¹öÀü 2.7.2¸é µÈ´Ù.) GCC°¡ + ¾ø´Ù¸é ÃÖ¼ÒÇÑ »ç¿ëÇÏ´Â ÄÄÆÄÀÏ·¯°¡ ANSI ȣȯÀÎÁö È®ÀÎÇ϶ó. + Ãß°¡·Î PATH ȯ°æº¯¼ö´Â make¿Í + °°Àº ±âº»ÀûÀÎ ÄÄÆÄÀÏ µµ±¸¸¦ Æ÷ÇÔÇØ¾ß ÇÑ´Ù.
+ +
Á¤È®ÇÑ ½Ã°£
+
HTTP ÇÁ·ÎÅäÄÝ¿¡´Â ÇÏ·çÁß ½Ã°£À» Ç¥ÇöÇÏ´Â ºÎºÐÀÌ ÀÖ´Ù. ±×·¡¼­ + ÀÌÁ¦ ½Ã½ºÅÛÀÇ ½Ã°£ µ¿±âÈ­ ±â´ÉÀ» »ìÆ캼 ½Ã°£ÀÌ´Ù. º¸Åë + À̸¦ À§ÇØ Network Time Protocol (NTP)¿¡ ±â¹ÝÇÑ + ntpdate³ª xntpd¸¦ »ç¿ëÇÑ´Ù. + NTP ¼ÒÇÁÆ®¿þ¾î¿Í °ø°³ ½Ã°£ ¼­¹ö¿¡ ´ëÇÑ Á¤º¸´Â ´º½º±×·ì + comp.protocols.time.ntp¿Í + NTP ȨÆäÀÌÁö¸¦ + Âü°íÇ϶ó.
+ +
Perl 5 + [¼±ÅûçÇ×]
+
(Perl·Î ¾²¿©Áø) apxs³ª + dbmmanage¿Í °°Àº + Áö¿ø ½ºÅ©¸³Æ®¸¦ À§ÇØ Perl 5 ÀÎÅÍÇÁ¸®ÅÍ°¡ ÇÊ¿äÇÏ´Ù. (¹öÀü + 5.003 ÀÌ»óÀÌ¸é µÈ´Ù.) `configure' ½ºÅ©¸³Æ®°¡ + ÀÌ ÀÎÅÍÇÁ¸®Å͸¦ ãÁö ¸øÇصµ ¹®Á¦¾øÀÌ ¾ÆÆÄÄ¡ 2.0À» + ÄÄÆÄÀÏÇÏ°í ¼³Ä¡ÇÒ ¼ö ÀÖ´Ù. ´Ù¸¸ Áö¿ø ½ºÅ©¸³Æ®¸¦ »ç¿ëÇÏÁö + ¸øÇÒ »ÓÀÌ´Ù. ¿©·¯ Perl ÀÎÅÍÇÁ¸®ÅÍ°¡ ¼³Ä¡µÇÀÖ´Ù¸é (¾Æ¸¶µµ + »ì¶§ Æ÷ÇÔµÈ Perl 4¿Í Á÷Á¢ ÄÄÆÄÀÏÇÑ Perl 5) + ./configure°¡ ¿Ã¹Ù¸¥ °ÍÀ» ã±âÀ§ÇØ + --with-perl ¿É¼ÇÀ» (¾Æ·¡ Âü°í) »ç¿ëÇÏ±æ ¹Ù¶õ´Ù.
+
+
top
+
+

´Ù¿î·Îµå

+ +

¾ÆÆÄÄ¡´Â ¿©·¯ ¹Ì·¯ ¸ñ·ÏÀÌ ÀÖ´Â ¾ÆÆÄÄ¡ À¥¼­¹ö + ´Ù¿î·Îµå »çÀÌÆ®¿¡¼­ ´Ù¿î·ÎµåÇÒ ¼ö ÀÖ´Ù. À¯´Ð½º·ù ½Ã½ºÅÛÀ» + »ç¿ëÇÑ´Ù¸é ¼Ò½ºÄڵ带 ´Ù¿î¹Þ¾Æ¼­ ÄÄÆÄÀÏÇÏ´Â ÆíÀÌ ³´´Ù. ½±°Ô + (¾Æ·¡¿¡¼­ ¼³¸í) ÄÄÆÄÀÏÇÒ ¼ö ÀÖ°í, ÀÚ½ÅÀÇ ¿ëµµ¿¡ ¾Ë¸Â°Ô ¼­¹ö¸¦ + ¸ÂÃâ ¼ö ÀÖ´Ù. ¶Ç, ÃֽŠ¹öÀü ¹ÙÀ̳ʸ® ¹èÆ÷º»ÀÌ ¾ø´Â °æ¿ìµµ + ¸¹´Ù. ¹ÙÀ̳ʸ®¸¦ ´Ù¿î¹Þ´Â´Ù¸é ¹èÆ÷º»¿¡ ÀÖ´Â + INSTALL.bindist ÆÄÀÏÀÇ Áö½Ã¸¦ µû¸£¶ó.

+ +

´Ù¿î·ÎµåÈÄ ´Ù¿î¹ÞÀº ÆÄÀÏÀÌ ¿ÏÀüÇÏ°í + º¯°æµÇÁö¾ÊÀº ¾ÆÆÄÄ¡ À¥¼­¹öÀÓÀ» È®ÀÎÇÏ´Â °ÍÀÌ Áß¿äÇÏ´Ù. + PGP ¼­¸íÀ» °¡Áö°í ´Ù¿î·ÎµåÇÑ Å¸º¼(tarball)À» °Ë»çÇÏ¿© È®ÀÎÇÑ´Ù. + ÀÚ¼¼ÇÑ ¹æ¹ýÀº ´Ù¿î·Îµå + ÆäÀÌÁö¿¡ ÀÖ°í, PGP + »ç¿ë¹ýÀ» ¼³¸íÇÏ´Â »ó¼¼ÇÑ ¿¹µµ ÀÖ´Ù.

+ +
top
+
+

¾ÐÃà Ç®±â

+ +

¾ÆÆÄÄ¡ À¥¼­¹ö Ÿº¼¿¡¼­ ¼Ò½º¸¦ Ǫ´Â ÀÛ¾÷Àº ´Ü¼øÈ÷ ¾ÐÃà°ú + tar¸¦ Ǫ´Â °ÍÀÌ´Ù:

+ +

+$ gzip -d httpd-2_1_NN.tar.gz
+$ tar xvf httpd-2_1_NN.tar +

+ +

±×·¯¸é ÇöÀç µð·ºÅ丮 ¾Æ·¡¿¡ ¹èÆ÷º»ÀÇ ¼Ò½ºÄڵ带 ´ãÀº + »õ·Î¿î µð·ºÅ丮°¡ »ý±ä´Ù. ¼­¹ö¸¦ ÄÄÆÄÀÏÇϱâ Àü¿¡ ±× + µð·ºÅ丮·Î cdÇØ¾ß ÇÑ´Ù.

+
top
+
+

¼Ò½º Æ®¸® ±¸¼ºÇϱâ

+ +

´ÙÀ½ °úÁ¤Àº ƯÁ¤ Ç÷¡Æû°ú °³ÀÎÀûÀÎ ÇÊ¿ä¿¡ µû¶ó ¾ÆÆÄÄ¡ + ¼Ò½º Æ®¸®¸¦ ±¸¼ºÇÏ´Â ÀÏÀÌ´Ù. À̸¦ À§ÇØ ¹èÆ÷º»ÀÇ ÃÖ»óÀ§ µð·ºÅ丮¿¡ + ÀÖ´Â configure + ½ºÅ©¸³Æ®¸¦ »ç¿ëÇÑ´Ù. (¾ÆÆÄÄ¡ + ¼Ò½º Æ®¸®ÀÇ CVS ¹öÀüÀ» ´Ù¿î·ÎµåÇÑ °³¹ßÀÚ´Â ÀÌ¹Ì + autoconf¿Í libtool°¡ ¼³Ä¡µÇÀÖ°í, + ´ÙÀ½ °úÁ¤À¸·Î ³Ñ¾î°¡±â Àü¿¡ buildconf¸¦ ½ÇÇàÇØ¾ß + ÇÑ´Ù. ÀÌ´Â Á¤½Ä ¹öÀü¿¡¼­´Â ÇÊ¿ä¾ø´Ù.)

+ +

¸ðµÎ ±âº» ¿É¼ÇÀ» »ç¿ëÇÏ¿© ¼Ò½º Æ®¸®¸¦ ±¸¼ºÇÏ·Á¸é °£´ÜÈ÷ + ./configure¸¦ ÀÔ·ÂÇϸéµÈ´Ù. ±âº» ¿É¼ÇÀ» ¼öÁ¤ÇÏ·Á¸é + ./configure¿¡ ¿©·¯ º¯¼ö¿Í ¸í·ÉÇà ¿É¼ÇÀ» »ç¿ëÇÑ´Ù.

+ +

°¡Àå Áß¿äÇÑ ¿É¼ÇÀº ¾ÆÆÄÄ¡°¡ Á¤»óÀûÀ¸·Î ÀÛµ¿ÇϱâÀ§ÇØ ¾ÆÆÄÄ¡¸¦ + ±¸¼ºÇÏ°í ¼³Ä¡ÇÒ Àå¼ÒÀÎ --prefix´Ù. ´Ù¸¥ configure + ¿É¼ÇµéÀ» »ç¿ëÇÏ¿© ÆÄÀÏÀÇ À§Ä¡¸¦ ´õ ÀÚ¼¼È÷ ¼³Á¤ÇÒ ¼öµµ + ÀÖ´Ù.

+ +

¸ðµâÀ» Æ÷ÇÔÇϰųª »©¼­ ¾ÆÆÄÄ¡¿¡ Æ÷ÇÔÇÒ + ±â´ÉÀ» + ¼±ÅÃÇÑ´Ù. Base + »óÅÂÀÎ ¸ðµâÀº ±âº»ÀûÀ¸·Î ¾ÆÆÄÄ¡¿¡ Æ÷ÇԵȴÙ. ´Ù¸¥ »óÅÂÀÇ + ¸ðµâÀº --enable-module ¿É¼ÇÀ» »ç¿ëÇÏ¿© + Æ÷ÇÔÇÑ´Ù. ¿©±â¼­ moduleÀº ¸ðµâ À̸§¿¡¼­ + mod_¸¦ »©°í ¹ØÁÙÀ» »©±â±âÈ£·Î º¯°æÇÑ °á°ú´Ù. + --enable-module=shared ¿É¼ÇÀ» »ç¿ëÇϸé + ¸ðµâÀ» ½ÇÇàÁß¿¡ Æ÷ÇÔÇϰųª »¬ ¼ö ÀÖ´Â °øÀ¯°´Ã¼(shared object, DSO)·Î ÄÄÆÄÀÏÇÑ´Ù. + ¶Ç, --disable-module ¿É¼ÇÀ» »ç¿ëÇÏ¿© + Base ¸ðµâÀ» »¬ ¼ö ÀÖ´Ù. ÁöÁ¤ÇÑ ¸ðµâÀÌ ¾ø¾îµµ + configure°¡ °æ°íÇÏÁö¾Ê°í ±×³É ¹«½ÃÇϱ⶧¹®¿¡ + ¸ðµâ À̸§À» Á¤È®È÷ ÀÔ·ÂÇ϶ó.

+ +

°¡²û configure ½ºÅ©¸³Æ®¿¡°Ô ÄÄÆÄÀÏ·¯, + ¶óÀ̺귯¸®, Çì´õÆÄÀÏ µîÀÇ À§Ä¡¸¦ ¾Ë·ÁÁà¾ß ÇÒ °æ¿ì°¡ ÀÖ´Ù. + ÀÌ Á¤º¸´Â ȯ°æº¯¼ö³ª configureÀÇ ¸í·ÉÇà ¿É¼ÇÀ» + »ç¿ëÇÏ¿© Àü´ÞÇÑ´Ù. ÀÚ¼¼ÇÑ ³»¿ëÀº configure manpage¸¦ + Âü°íÇ϶ó.

+ +

¿©·¯ºÐÀÌ ¼±ÅÃÇÒ ¼ö ÀÖ´Â °¡´É¼ºÀ» º¸¿©ÁÖ±âÀ§ÇØ ´ÙÀ½Àº + ƯÁ¤ ÄÄÆÄÀÏ·¯¿Í Ç÷¡±×¸¦ »ç¿ëÇÏ°í ³ªÁß¿¡ DSO·Î ÀоîµéÀÏ + µÎ ¸ðµâ mod_rewrite¿Í + mod_spelingÀ» Ãß°¡ÇÏ¿© + /sw/pkg/apache¿¡ ¼³Ä¡ÇÒ ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÏ´Â + ÀüÇüÀûÀÎ ¿¹ÀÌ´Ù:

+ +

+ $ CC="pgcc" CFLAGS="-O2" \
+ ./configure --prefix=/sw/pkg/apache \
+ --enable-rewrite=shared \
+ --enable-speling=shared +

+ +

configure¸¦ ½ÇÇàÇÏ¸é ¸îºÐ°£ ½Ã½ºÅÛÀÇ ±â´ÉÀ» + °Ë»çÇÏ¿© ³ªÁß¿¡ ¼­¹ö¸¦ ÄÄÆÄÀÏÇÒ¶§ »ç¿ëÇÒ MakefileµéÀ» + ¸¸µç´Ù.

+ +

configure ¿É¼Çµé¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸íÀº configure manpage¿¡ ÀÖ´Ù.

+
top
+
+

ÄÄÆÄÀÏ

+ +

ÀÌÁ¦ ´ÙÀ½ ¸í·É¾î Çϳª·Î ¾ÆÆÄÄ¡ÀÇ ¿©·¯ ºÎºÐÀ» ÄÄÆÄÀÏÇÒ + ¼ö ÀÖ´Ù:

+ +

$ make

+ +

¿©±â¼­ Á» ±â´Ù·Á¶ó. ÆæƼ¾ö III/¸®´ª½º 2.2 ½Ã½ºÅÛ¿¡¼­ + ±âº» ±¸¼ºÀ» ÄÄÆÄÀÏÇϴµ¥ ¾à 3ºÐ Á¤µµ °É¸°´Ù. ÀÌ ½Ã°£Àº + Çϵå¿þ¾î¿Í Æ÷ÇÔÇÑ ¸ðµâ¼ö¿¡ µû¶ó Å©°Ô º¯ÇÑ´Ù.

+
top
+
+

¼³Ä¡

+ +

ÀÌÁ¦ ´ÙÀ½ ¸í·É¾î·Î ÆÐÅ°Áö¸¦ (À§ÀÇ --prefix + ¿É¼Ç Âü°í) ÁöÁ¤ÇÑ ¼³Ä¡ À§Ä¡ PREFIX¿¡ ¼³Ä¡ÇÑ´Ù:

+ +

$ make install

+ +

¾÷±×·¹À̵åÇÑ´Ù¸é ÀÌ ¼³Ä¡ °úÁ¤ÀÌ ±âÁ¸ ¼³Á¤ÆÄÀÏÀ̳ª ¹®¼­¸¦ + µ¤¾î¾²Áö ¾Ê´Â´Ù.

+
top
+
+

¼³Á¤

+ +

´ÙÀ½À¸·Î PREFIX/conf/¿¡ ÀÖ´Â + ¼³Á¤ÆÄÀÏÀ» ÆíÁýÇÏ¿© ¾ÆÆÄÄ¡ + À¥¼­¹ö¸¦ ¼³Á¤ÇÑ´Ù.

+ +

$ vi PREFIX/conf/httpd.conf

+ +

»ç¿ë°¡´ÉÇÑ ¼³Á¤ Áö½Ã¾î¿¡ + ´ëÇÑ ¿ÏÀüÇÑ ¼³¸í°ú ÀÌ ¹®¼­ÀÇ °¡Àå ÃÖ±Ù ÆÇÀº docs/manual/À̳ª http://httpd.apache.org/docs/2.2/¿¡ ÀÖ´Â ¾ÆÆÄÄ¡ ¼³¸í¼­¸¦ + Âü°íÇ϶ó.

+
top
+
+

°Ë»ç

+ +

ÀÌÁ¦ ´ÙÀ½°ú °°ÀÌ ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ½ÃÀÛÇÒ ¼ö ÀÖ´Ù:

+ +

$ PREFIX/bin/apachectl start

+ +

±×¸®°í URL http://localhost/·Î ù ¹®¼­¸¦ + ¿äûÇÑ´Ù. º¸°ÔµÉ À¥ÆäÀÌÁö´Â ¾Æ¸¶µµ + PREFIX/htdocs/ÀÏ DocumentRoot ¾Æ·¡¿¡ ÀÖ´Ù. ±×¸®°í + ´ÙÀ½ ¸í·É¾î·Î ´Ù½Ã ¼­¹ö¸¦ Áß´ÜÇÑ´Ù:

+ +

$ PREFIX/bin/apachectl stop

+
top
+
+

¾÷±×·¹À̵å

+ +

¾÷±×·¹À̵åÇÑ´Ù¸é ¸ÕÀú »çÀÌÆ®¿¡ ¿µÇâÀ» ÁÙ ¼ö ÀÖ´Â º¯È­°¡ + ÀÖ´ÂÁö ¾Ë¾Æº¸±âÀ§ÇØ ¹ßÇ¥¹®°ú ¼Ò½º ¹èÆ÷º»ÀÇ CHANGES + ÆÄÀÏÀ» Àд´Ù. (¿¹¸¦ µé¾î, 1.3¿¡¼­ 2.0À̳ª 2.0¿¡¼­ 2.2¿Í + °°Àº) Å« ¹öÀüÀÌ º¯ÇÑ °æ¿ì ÄÄÆÄÀÏ ¿É¼Ç°ú ¼³Á¤À» Á÷Á¢ ¼öÁ¤ÇؾßÇÒ + Á¤µµÀÇ Å« º¯È­°¡ ÀÖÀ» °ÍÀÌ´Ù. ¸ðµç ¸ðµâµµ ¸ðµâ APIÀÇ º¯È­¿¡ + ¾Ë¸Â°Ô ¾÷±×·¹À̵åÇØ¾ß ÇÑ´Ù.

+ +

ÀÛÀº ¹öÀüÀ» ÇÑ´Ü°è ¾÷±×·¹À̵åÇÏ´Â °ÍÀº (¿¹¸¦ µé¾î, + 2.0.55¿¡¼­ 2.0.57) ½±´Ù. make install ÀÛ¾÷Àº + ±âÁ¸ÀÇ ¹®¼­, ·Î±×ÆÄÀÏ, ¼³Á¤ÆÄÀÏÀ» ¼öÁ¤ÇÏÁö ¾Ê´Â´Ù. ¶Ç, + °³¹ßÀÚ´Â ÀÛÀº ¹öÀü°£¿¡ configure ¿É¼Ç, ¼³Á¤, + ¸ðµâ APIÀÇ È£È¯¼º¾ø´Â º¯È­¸¦ ÃÖ´ëÇÑ ¸·´Â´Ù. ´ëºÎºÐÀÇ °æ¿ì + µ¿ÀÏÇÑ configure ¸í·ÉÇà, µ¿ÀÏÇÑ ¼³Á¤ÆÄÀÏÀ» + »ç¿ëÇÒ ¼ö ÀÖ°í, ¸ðµâµéµµ ¸ðµÎ °è¼Ó µ¿ÀÛÇÒ °ÍÀÌ´Ù. (ÀÌ ¸»Àº + 2.0.41ÀÌÈÄ ¹öÀü¿¡¸¸ ÇØ´çÇÑ´Ù. ÀÌÀü ¹öÀüµé¿¡´Â ȣȯ¼º¾ø´Â + º¯È­°¡ ÀÖ´Ù.)

+ +

ÀÌÀü¿¡ ¼³Ä¡Çß´ø ¼Ò½º¸¦ °¡Áö°í ÀÖ´Ù¸é, ¾÷±×·¹À̵尡 ´õ + ½¬¿öÁø´Ù. ÀÌÀü ¼Ò½º ÃÖ»óÀ§¿¡ ÀÖ´Â config.nice + ÆÄÀÏ¿¡´Â ¼Ò½º¸¦ ±¸¼ºÇÒ ¶§ »ç¿ëÇß´ø configure + ¸í·ÉÇà ¿É¼ÇÀÌ ±×´ë·Î ÀÖ´Ù. ±×·¡¼­ ´ÙÀ½ ¹öÀüÀ¸·Î ¾÷±×·¹À̵åÇÑ´Ù¸é + »õ·Î¿î ¹öÀü ¼Ò½º·Î config.nice ÆÄÀÏÀ» º¹»çÇÏ°í, + ¿øÇÑ´Ù¸é Á¶±Ý ¼öÁ¤À» ÇÑ ÈÄ, ´ÙÀ½°ú °°ÀÌ ½ÇÇàÇÑ´Ù:

+ +

+ $ ./config.nice
+ $ make
+ $ make install
+ $ PREFIX/bin/apachectl stop
+ $ PREFIX/bin/apachectl start
+

+ +
»õ·Î¿î ¹öÀüÀ» »ç¿ëÇϱâ Àü¿¡ Ç×»ó °Ë»çÇغÁ¾ß + ÇÑ´Ù. ¿¹¸¦ µé¾î, ¾÷±×·¹À̵带 ¸¶Ä¡±â Àü¿¡ ȣȯ¼º ¹®Á¦°¡ + ÀÖ´ÂÁö ¾Ë¾Æº¸±âÀ§ÇØ ´Ù¸¥ --prefix¿Í (Listen Áö½Ã¾î·Î) ´Ù¸¥ Æ÷Æ®¸¦ + »ç¿ëÇÏ¿© »õ·Î¿î ¹öÀüÀ» ¼³Ä¡ÇÑÈÄ ÀÌÀü ¹öÀü°ú °°ÀÌ ½ÇÇàÇغ¼ + ¼ö ÀÖ´Ù.
+
+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + fr  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/invoking.html b/docs/manual/invoking.html new file mode 100644 index 00000000..11c637ae --- /dev/null +++ b/docs/manual/invoking.html @@ -0,0 +1,23 @@ +URI: invoking.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: invoking.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: invoking.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: invoking.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: invoking.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: invoking.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R diff --git a/docs/manual/invoking.html.de b/docs/manual/invoking.html.de new file mode 100644 index 00000000..c08272a1 --- /dev/null +++ b/docs/manual/invoking.html.de @@ -0,0 +1,156 @@ + + + +Apache starten - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Apache starten

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

Unter Windows läuft der Apache üblicherweise als Dienst + (Windows NT, 2000 und XP) oder als Konsolenanwendung (Windows 9x und + ME). Für Einzelheiten lesen Sie bitte Apache als Dienst betreiben + und Apache als Konsolenanwendung betreiben.

+ +

Unter Unix wird das httpd-Programm als Daemon + ausgeführt, der im Hintergrund fortlaufend aktiv ist, um + Anfragen zu bearbeiten. Dieses Dokument beschreibt, wie + httpd aufgerufen wird.

+
+ +
top
+
+

Wie der Apache startet

+ +

Wenn die in der Konfigurationsdatei angegebene Listen-Anweisung auf die Voreinstellung + von 80 gesetzt ist (oder einen anderen Port unterhalb von 1024), dann + müssen Sie root-Berechtigung besitzen, um den Apache starten + zu können. Nur dann kann er sich an diesen privilegierten + Port binden. Sobald der Server gestartet ist und einige vorbereitende + Aktionen wie das Öffnen seiner Log-Dateien ausgeführt hat, + startet er mehrere Kind-Prozesse, welche die Arbeit erledigen: + das Lauschen auf und Beantworten von Anfragen von Clients. Der + Haupt-httpd-Prozess läuft unter dem Benutzer root + weiter, die Kind-Prozesse jedoch werden unter weniger privilegierten + Benutzerkennungen ausgeführt. Dies wird von dem ausgewählten + Multi-Processing-Modul gesteuert.

+ +

Die Verwendung des Steuerskripts apachectl ist die + empfohlene Methode, das httpd-Programm zu starten. + Dieses Skript setzt verschiedene Umgebungsvariablen, die für die + korrekte Funktion von httpd unter einigen + Betriebssystemen notwendig sind, und startet dann das + httpd-Programm. apachectl + reicht alle Kommandozeilenargumente durch, so dass alle + httpd-Optionen auch mit apachectl + verwendet werden können. Um den korrekten Ablageort des + httpd-Programms sowie einige Kommandozeilenargumente + anzugeben, die Sie immer verwenden möchten, können + Sie auch das Skript apachectl direkt editieren und die + Variable HTTPD am Anfang ändern.

+ +

Das Erste was httpd macht, wenn es startet, ist das + Suchen und Einlesen der Konfigurationsdatei httpd.conf. + Der Ablageort dieser Datei wird zur Kompilierungszeit festgelegt. Es ist + aber möglich, den Ablageort zur Laufzeit anzugeben, indem die + Kommandozeilenoption -f wie folgt verwendet wird:

+ +

/usr/local/apache2/bin/apachectl -f + /usr/local/apache2/conf/httpd.conf

+ +

Wenn während des Starts alles gutgeht, trennt sich der Server + vom Terminal ab und die Eingabeaufforderung erscheint gleich darauf + wieder. Dies zeigt an, dass der Server hochgefahren ist und läuft. + Sie können nun Ihren Browser benutzen, um Verbindung zum Server + aufzunehmen und sich die Testseite im DocumentRoot-Verzeichnis anzusehen wie auch + die lokale Kopie der Dokumentation, die von dieser Seite aus verlinkt + ist.

+
top
+
+

Fehler während des Hochfahrens

+ +

Wenn der Apache während des Hochfahrens einen schweren Fehler + feststellt, schreibt er entweder eine Nachricht, die das Problem + näher schildert, auf die Konsole oder ins ErrorLog, bevor er sich selbst beendet. + Eine der häufigsten Fehlermeldungen ist "Unable + to bind to Port ..." (Anm.d.Ü.: "Kann nicht an Port ... + binden"). Diese Meldung wird üblicherweise verursacht:

+ +
    +
  • entweder durch den Versuch, den Server an einem privilegierten + Port zu starten, während man nicht als Benutzer root angemeldet + ist,
    • + +
  • oder durch den Versuch, den Server zu starten, wenn bereits eine + andere Instanz des Apache oder ein anderer Webserver an den gleichen + Port gebunden ist.
    • +
+ +

Für weitere Anleitungen zur Fehlerbehebung lesen Sie bitte die + Apache-FAQ.

+
top
+
+

Beim Bootvorgang starten

+ +

Wenn Sie möchten, dass Ihr Server direkt nach einem + System-Neustart weiterläuft, sollten Sie einen Aufruf von + apachectl zu den Startdateien Ihres Systems + hinzufügen (üblicherweise rc.local oder + eine Datei in einem rc.N-Verzeichnis). Dies startet + den Apache als root. Stellen Sie zuvor jedoch sicher, dass Ihr + Server hinsichtlich Sicherheit und Zugriffsbeschränkungen + richtig konfiguriert ist.

+ +

Das apachectl-Skript ist dafür ausgelegt, wie + ein Standard-SysV-init-Skript zu arbeiten. Es akzeptiert die Argumente + start, restart und stop + und übersetzt sie in die entsprechenden Signale für + httpd. Daher können Sie oftmals + einfach apachectl in das entsprechende init-Verzeichnis + linken. Überprüfen Sie bitte auf jeden Fall die genauen + Anforderungen Ihres Systems.

+
top
+
+

Weitere Informationen

+ +

Weitere Informationen über Kommandozeilenoptionen von httpd und apachectl sowie anderen + Hilfsprogrammen, die dem Server beigefügt sind, sind auf der + Seite Server und Hilfsprogramme + verfügbar. Es existiert außerdem eine Dokumentation + aller in der Apache-Distribution enthaltenen Module und der von ihnen bereitgestellten + Direktiven.

+
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/invoking.html.en b/docs/manual/invoking.html.en new file mode 100644 index 00000000..c1967d0a --- /dev/null +++ b/docs/manual/invoking.html.en @@ -0,0 +1,151 @@ + + + +Starting Apache - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Starting Apache

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

On Windows, Apache is normally run as a service on Windows + NT, 2000 and XP, or as a console application on Windows 9x and + ME. For details, see Running Apache as a Service + and Running Apache as a + Console Application.

+ +

On Unix, the httpd program + is run as a daemon that executes continuously in the + background to handle requests. This document describes how + to invoke httpd.

+
+ +
top
+
+

How Apache Starts

+ +

If the Listen + specified in the configuration file is default of 80 (or any other + port below 1024), then it is necessary to have root privileges in + order to start apache, so that it can bind to this privileged + port. Once the server has started and performed a few preliminary + activities such as opening its log files, it will launch several + child processes which do the work of listening for and + answering requests from clients. The main httpd + process continues to run as the root user, but the child processes + run as a less privileged user. This is controlled by the selected + Multi-Processing Module.

+ +

The recommended method of invoking the httpd + executable is to use the apachectl control script. This + script sets certain environment variables that are necessary for + httpd to function correctly under some operating + systems, and then invokes the httpd binary. + apachectl will pass through any command line + arguments, so any httpd options may also be used with + apachectl. You may also directly edit the + apachectl script by changing the HTTPD + variable near the top to specify the correct location of the + httpd binary and any command-line arguments that you + wish to be always present.

+ +

The first thing that httpd does when it is + invoked is to locate and read the configuration file + httpd.conf. The location of this file is set at + compile-time, but it is possible to specify its location at run + time using the -f command-line option as in

+ +

/usr/local/apache2/bin/apachectl -f + /usr/local/apache2/conf/httpd.conf

+ +

If all goes well during startup, the server will detach from + the terminal and the command prompt will return almost + immediately. This indicates that the server is up and running. + You can then use your browser to connect to the server and view + the test page in the DocumentRoot directory + and the local copy of the documentation linked from that + page.

+
top
+
+

Errors During Start-up

+ +

If Apache suffers a fatal problem during startup, it will + write a message describing the problem either to the console or + to the ErrorLog before + exiting. One of the most common error messages is "Unable + to bind to Port ...". This message is usually caused by + either:

+ +
    +
  • Trying to start the server on a privileged port when not + logged in as the root user; or
    • + +
  • Trying to start the server when there is another instance + of Apache or some other web server already bound to the same + Port.
    • +
+ +

For further trouble-shooting instructions, consult the + Apache FAQ.

+
top
+
+

Starting at Boot-Time

+ +

If you want your server to continue running after a system + reboot, you should add a call to apachectl to your + system startup files (typically rc.local or a file in + an rc.N directory). This will start Apache as + root. Before doing this ensure that your server is properly + configured for security and access restrictions.

+ +

The apachectl script is designed to act like a + standard SysV init script; it can take the arguments + start, restart, and stop + and translate them into the appropriate signals to + httpd. So you can often simply link + apachectl into the appropriate init directory. But be + sure to check the exact requirements of your system.

+
top
+
+

Additional Information

+ +

Additional information about the command-line options of httpd and apachectl as well as other support + programs included with the server is available on the + Server and Supporting Programs page. + There is also documentation on all the modules included with the Apache distribution + and the directives that they + provide.

+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/invoking.html.es b/docs/manual/invoking.html.es new file mode 100644 index 00000000..431493a4 --- /dev/null +++ b/docs/manual/invoking.html.es @@ -0,0 +1,168 @@ + + + +iniciar Apache - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

iniciar Apache

+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ +

En Windows, Apache se ejecuta normalmente como un servicio en + Windows NT, 2000 and XP, y como una aplicacion de consola en + Windows 9x y ME. Para obtener más información, consulte + Ejecutar Apache como un + servicio y Ejecutar + Apache como una aplicación de consola.

+ +

En Unix, el programa httpd se + ejecuta como un demonio (daemon) de forma silenciosa y atiende las + peticiones que le lleguen. Este documento describe cómo + invocar el programa httpd.

+
+ +
top
+
+

Cómo iniciar Apache

+ +

Si el puerto especificado en la directiva Listen del fichero de + configuración es el que viene por defecto, es decir, el + puerto 80 (o cualquier otro puerto por debajo del 1024), entonces + es necesario tener privilegios de usuario root (superusuario) para + iniciar Apache, de modo que pueda establecerse una conexión a + través de esos puertos privilegiados. Una vez que el servidor + Apache se ha iniciado y ha completado algunas tareas preliminares, + tales como abrir sus ficheros log, lanzará varios procesos, + procesos hijo, que hacen el trabajo de escuchar y atender + las peticiones de los clientes. El proceso principal, + httpd continúa ejecutandose como root, pero los + procesos hijo se ejecutan con menores privilegios de usuario. + Esto lo controla el Módulo de + MultiProcesamiento (MPM) seleccionado.

+ +

La forma recomendada para invocar el ejecutable + httpd es usando el script de control apachectl. Este script fija + determinadas variables de entorno que son necesarias para que + httpd funcione correctamente en el sistema operativo, + y después invoca el binario httpd. + apachectl pasa a httpd cualquier argumento que se le + pase a través de la línea de comandos, de forma que + cualquier opción de httpd puede ser usada + también con apachectl. Puede editar + directamente el script apachectl y cambiar la + variable HTTPD variable que está al principio y + que especifica la ubicación exacta en la que está el + binario httpd y cualquier argumento de línea de + comandos que quiera que esté siempre presente.

+ +

La primera cosa que hace httpd cuando es invocado + es localizar y leer el fichero de + configuración httpd.conf. El lugar en el que + está ese fichero se determina al compilar, pero también + es posible especificar la ubicación en la que se encuentra al + iniciar el servidor Apache usando la opción de línea de + comandos -f

+ +

/usr/local/apache2/bin/apachectl -f + /usr/local/apache2/conf/httpd.conf

+ +

Si todo va bien durante el arranque, la sesión de terminal + se suspenderá un momento y volverá a estar activa casi + inmediatamente. Esto quiere decir que el servidor está activo + y funcionando. Puede usar su navegador para conectarse al + servidor y ver la pagina de prueba que hay en el directorio + DocumentRoot y la copia local + de esta documentación a la que se puede acceder desde esa + página.

+
top
+
+

Errores Durante el Arranque

+ +

Si Apache encuentra una error irrecuperable durante el + arranque, escribirá un mensaje describiendo el problema en la + consola o en el archivo ErrorLog antes de abortar la + ejecución. Uno de los mensajes de error más comunes es + "Unable to bind to Port ...". Cuando se recibe este + mensaje es normalmente por alguna de las siguientes razones:

+ +
    +
  • Está intentando iniciar el servidor Apache en un puerto + privilegiado (del 0 al 1024) sin haber hecho login como usuario + root; ó
    • + +
  • Está intentando iniciar el servidor Apache mientras + está ya ejecutando Apache o algún otro servidor web en + el mismo puerto.
    • +
+ +

Puede encontrar más información sobre cómo + solucionar problemas, en la sección de Preguntas Frecuentes de Apache.

+
top
+
+

Iniciar Apache al Iniciar el Sistema

+ +

Si quiere que el servidor Apache continú su ejecución + después de reiniciar el sistema, debe añadir una llamada + a apachectl en sus archivos de arranque (normalmente + rc.local o un fichero en ese directorio del tipo + rc.N). Esto iniciará Apache como usuario + root. Antes de hacer esto, asegúrese de que la + configuración de seguridad y las restricciones de acceso de + su servidor Apache están correctamente configuradas.

+ +

El script apachectl está diseñado para + actuar como un script estandar de tipo SysV init; puede tomar los + argumentos start, restart, y + stop y traducirlos en las señales apropiadas + para httpd. De esta manera, casi siempre puede + simplemente enlazar apachectl con el directorio init + adecuado. Pero asegúrese de comprobar los requisitos exactos + de su sistema.

+
top
+
+

Información Adicional

+ +

En la sección El Servidor y Programas + de Soporte puede encontrar más información sobre + las opciones de línea de comandos que puede pasar a httpd y apachectl asi como sobre otros + programas de soporte incluidos con el servidor Apache. + También hay documentación sobre todos los módulos incluidos con la distribucion de + Apache y sus correspondientes directivas asociadas.

+
+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/invoking.html.ja.euc-jp b/docs/manual/invoking.html.ja.euc-jp new file mode 100644 index 00000000..3e386d59 --- /dev/null +++ b/docs/manual/invoking.html.ja.euc-jp @@ -0,0 +1,161 @@ + + + +Apache ¤Îµ¯Æ° - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

Apache ¤Îµ¯Æ°

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

Windows ¾å¤Ç¤Ï¡¢Apache ¤ÏÄ̾ï¤Ï + Windows NT, 2000, XP ¤Ç¤Ï¥µ¡¼¥Ó¥¹¤È¤·¤Æ¡¢Windows 9x, ME + ¤Ç¤Ï¥³¥ó¥½¡¼¥ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤È¤·¤Æ¼Â¹Ô¤µ¤ì¤Þ¤¹¡£ + ¾ÜºÙ¤Ë´Ø¤·¤Æ¤Ï¡¢¡Ö + ¥µ¡¼¥Ó¥¹¤È¤·¤Æ¼Â¹Ô¤¹¤ë¡×¤È¡Ö + ¥³¥ó¥½¡¼¥ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤È¤·¤Æ¼Â¹Ô¤¹¤ë¡×¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

Unix¤Ç¤Ï¡¢httpd + ¥×¥í¥°¥é¥à¤¬¡¢¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ç¾ï¤Ë¥ê¥¯¥¨¥¹¥È½èÍý¤ò¹Ô¤¦ + ¥Ç¡¼¥â¥ó¤È¤·¤Æ¼Â¹Ô¤µ¤ì¤Þ¤¹¡£¤³¤Îʸ½ñ¤Ç¤Ï¤É¤Î¤è¤¦¤Ë + httpd ¤òµ¯Æ°¤¹¤ë¤«¤Ë¤Ä¤¤¤Æµ­½Ò¤·¤Æ¤¤¤Þ¤¹¡£

+
+ +
top
+
+

Apache ¤Îµ¯Æ°ÊýË¡

+ +

¤â¤·¡¢ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Ç»ØÄꤵ¤ì¤Æ¤¤¤ë + Listen + ¤¬¥Ç¥Õ¥©¥ë¥È¤Î 80 (¤â¤·¤¯¤Ï 1024 °Ê²¼¤Î¾¤Î¥Ý¡¼¥È) + ¤Ç¤¢¤ë¾ì¹ç¤Ï¡¢Apache ¤òµ¯Æ°¤¹¤ë¤¿¤á¤Ë¤Ï root + ¸¢¸Â¤¬É¬Íפˤʤê¤Þ¤¹¤¬¡¢ + ¤³¤ì¤Ï¤³¤ÎÆø¢¥Ý¡¼¥È¤Ë¥Ð¥¤¥ó¥É¤¹¤ë¤¿¤á¤Ç¤¹¡£ + µ¯Æ°¤·¤Æ¡¢°ìÅÙ¥í¥°¥Õ¥¡¥¤¥ë¤ò³«¤¯¤È¤¤¤Ã¤¿½àÈ÷¤Î¤¿¤á¤Î + Æ°ºî¤ò´ö¤Ä¤«¼Â¹Ô¤·¤¿¸å¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë + listen ¤È±þÅú¤ò¼ÂºÝ¤Ë¹Ô¤¦»Ò¥×¥í¥»¥¹¤òµ¯Æ°¤·¤Þ¤¹¡£ + ¥á¥¤¥ó¤Î httpd ¥×¥í¥»¥¹¤Ï root ¸¢¸Â¤ÇÁö¤ê³¤±¤Þ¤¹¤¬¡¢ + »Ò¥×¥í¥»¥¹¤Ï¤â¤Ã¤ÈÄ㤤¸¢¸Â¤ÇÁö¤ê¤Þ¤¹¡£ + ¤³¤ì¤ÏÁªÂò¤·¤¿¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë¤ÇÀ©¸æ¤µ¤ì¤Þ¤¹¡£

+ +

¿ä¾©¤Î httpd ¼Â¹Ô¥×¥í¥°¥é¥à¤Îµ¯Æ°ÊýË¡¤Ï¡¢ + apachectl + À©¸æ¥¹¥¯¥ê¥×¥È¤ò»ÈÍѤ¹¤ëÊýË¡¤Ç¤¹¡£¤³¤Î¥¹¥¯¥ê¥×¥È¤Ï¡¢httpd + ¤¬¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¾å¤ÇÀµ¾ï¤ËÆ°ºî¤¹¤ë¤è¤¦¤ËɬÍפʴĶ­ÊÑ¿ô¤ò + ŬÀÚ¤ËÀßÄꤷ¤Æ¡¢httpd ¥Ð¥¤¥Ê¥ê¤òµ¯Æ°¤·¤Þ¤¹¡£ + apachectl ¤Ï¤É¤ó¤Ê¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¿ô¤âÄ̲ᤵ¤»¤Þ¤¹¤Î¤Ç¡¢ + httpd ¤Î¤É¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤â + apchectl ¤Î¥ª¥×¥·¥ç¥ó¤È¤·¤Æ»ÈÍѤǤ­¤Þ¤¹¡£ + ¤Þ¤¿¡¢apchectl ¥¹¥¯¥ê¥×¥È¤òľÀÜÊÔ½¸¤·¡¢ + ¥¹¥¯¥ê¥×¥ÈÀèƬÉÕ¶á¤Î HTTPD ÊÑ¿ô¤òÊѹ¹¤¹¤ë¤³¤È¤Ç¡¢ + httpd ¥Ð¥¤¥Ê¥ê¤ÎÀµ¤·¤¤°ÌÃÖ¤ò»ØÄꤷ¤¿¤ê¡¢¾ï¤Ë + Éղ䵤»¤ë¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¿ô¤ò»ØÄꤷ¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

httpd ¤¬µ¯Æ°¤µ¤ì¤Æ¤Þ¤ººÇ½é¤Ë¤¹¤ë¤³¤È¤Ï¡¢ + ÀßÄê¥Õ¥¡¥¤¥ë + httpd.conf ¤Î°ÌÃÖ¤òÆÃÄꤷ¤ÆÆɤ߹þ¤à¤³¤È¤Ç¤¹¡£ + ¤³¤Î¥Õ¥¡¥¤¥ë¤Î°ÌÃ֤ϥ³¥ó¥Ñ¥¤¥ë»þ¤ËÀßÄꤵ¤ì¤Þ¤¹¤¬¡¢¼Â¹Ô»þ¤Ë + -f ¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ + °ÌÃÖ¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¼¡¤Î¤è¤¦¤Ë¤Ç¤¹¡£

+ +

/usr/local/apache2/bin/apachectl -f + /usr/local/apache2/conf/httpd.conf

+ +

¥¹¥¿¡¼¥È¥¢¥Ã¥×¤¬Ëü»ö¾å¼ê¤¯¤¤¤Ã¤¿¤é¡¢¥µ¡¼¥Ð¤Ï¥¿¡¼¥ß¥Ê¥ë¤«¤é + ÀÚ¤êÎ¥¤µ¤ì¤Æ¡¢¥³¥Þ¥ó¥É¥×¥í¥ó¥×¥È¤¬Â¨ºÂ¤ËÌá¤Ã¤Æ¤¯¤ë¤Ç¤·¤ç¤¦¡£ + ¤³¤ì¤Ï¥µ¡¼¥Ð¤¬µ¯Æ°¤·¤Æ¤¤¤ë¾õÂÖ¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£ + ¤½¤Î¸å¤Ï¥Ö¥é¥¦¥¶¤Ç¥µ¡¼¥Ð¤ËÀܳ¤·¤Æ¡¢ + DocumentRoot + ¥Ç¥£¥ì¥¯¥È¥ê¤Î¥Æ¥¹¥È¥Ú¡¼¥¸¤ä¤½¤³¤«¤é¥ê¥ó¥¯¤µ¤ì¤Æ¤¤¤ë + ¥í¡¼¥«¥ë¤Î¥É¥­¥å¥á¥ó¥È¤ò¸«¤ë¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£

+
top
+
+

µ¯Æ°»þ¤Î¥¨¥é¡¼

+ +

Apache ¤Ï¡¢µ¯Æ°»þ¤ËÃ×̿Ū¤ÊÌäÂê¤ËÁø¶ø¤¹¤ë¤È¡¢ + ½ªÎ»¤¹¤ëÁ°¤Ë¡¢¥³¥ó¥½¡¼¥ë¤« + ErrorLog + ¤Î¤É¤Á¤é¤«¤ËÌäÂê¤òµ­½Ò¤·¤¿¥á¥Ã¥»¡¼¥¸¤ò½ÐÎϤ·¤Þ¤¹¡£ + ºÇ¤â¤è¤¯¤¢¤ë¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Ï + ¡ÖUnable to bind to Port ...¡× + ¤Ç¤¹¡£¤³¤Î¥á¥Ã¥»¡¼¥¸¤ÏÉáÄ̤ϼ¡¤Î¤É¤Á¤é¤«¤¬¸¶°ø¤Ç¤¹¡£

+ +
    +
  • root ¤Ç¥í¥°¥¤¥ó¤·¤Æ¤¤¤Ê¤¤»þ¤Ë¡¢ + Æø¢¥Ý¡¼¥È¤Ç¥µ¡¼¥Ð¤òµ¯Æ°¤·¤è¤¦¤È¤·¤¿¡£
    • + +
  • Ʊ¤¸¥Ý¡¼¥È¤Ë´û¤Ë¥Ð¥¤¥ó¥É¤µ¤ì¤Æ¤¤¤ë Apache + ¤¬¤â¤¦°ì¤Ä¤¢¤ë¤È¤­¤ä¾¤Î¥¦¥§¥Ö¥µ¡¼¥Ð¤¬Â¸ºß¤·¤Æ¤¤¤ë»þ¤Ë¡¢ + ¥µ¡¼¥Ð¤ò³«»Ï¤·¤è¤¦¤È¤·¤¿¡£
    • +
+ +

¤è¤ê¿¤¯¤ÎÌäÂê²ò·è¤ÎÊýºö¤ÎÀâÌÀ¤Ï¡¢ + Apache FAQ ¤ò¤´Í÷²¼¤µ¤¤¡£

+
top
+
+

¥Ö¡¼¥È»þ¤Îµ¯Æ°

+ +

¥·¥¹¥Æ¥à¤¬¥ê¥Ö¡¼¥È¤·¤¿¸å¤Ç¤â + ¥µ¡¼¥Ð¤¬¼Â¹Ô¤µ¤ì³¤±¤ë¤è¤¦¤Ë¤·¤¿¤¤¾ì¹ç¤Ï¡¢ + apachectl + ¤ò¸Æ¤Ó½Ð¤¹¤â¤Î¤ò¥·¥¹¥Æ¥à¥¹¥¿¡¼¥È¥¢¥Ã¥×¥Õ¥¡¥¤¥ë + (Ä̾ï rc.local ¤ä rc.N + Æâ¤Î¥Õ¥¡¥¤¥ë) ¤ËÄɲ䷤ʤ±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤³¤ÎÊýË¡¤Ç¤Ï Apache ¤ò root ¸¢¸Â¤Çµ¯Æ°¤·¤Þ¤¹¡£ + ¤³¤ì¤ò¤¹¤ëÁ°¤Ë¡¢¥»¥­¥å¥ê¥Æ¥£¤ä¥¢¥¯¥»¥¹À©¸Â¤¬ + ŬÀÚ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

apachectl ¥¹¥¯¥ê¥×¥È¤ÏÄ̾ï¤Ï¡¢É¸½àŪ¤Ê SysV init + ¥¹¥¯¥ê¥×¥È¤È¤·¤ÆÆ°ºî¤¹¤ë¤è¤¦¤ËÀ߷פµ¤ì¤Æ¤¤¤Þ¤¹¡£ + start, restart, stop + ¤È¤¤¤Ã¤¿°ú¿ô¤ò¤È¤Ã¤Æ¡¢httpd + ¤Ø¤ÎŬÀڤʥ·¥°¥Ê¥ë¤ËÊÑ´¹¤·¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢Ä̾ï¤Ïñ¤ËŬÀÚ¤Ê init ¥Ç¥£¥ì¥¯¥È¥êÆ⤫¤é + apachectl ¤Ø¥ê¥ó¥¯¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤·¤«¤·¡¢ + Ç°¤Î¤¿¤á¥·¥¹¥Æ¥à¤ÎÍ×µá¤Ë¹çÃפ·¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

ÄɲþðÊó

+ +

httpd ¤ä + apachectl¡¢¥µ¡¼¥Ð¤Ë´Þ¤Þ¤ì¤Æ¤¤¤¿¤½¤Î¾Êä½õ¥×¥í¥°¥é¥à¤Î¡¢ + ¥³¥Þ¥ó¥É¥é¥¤¥ó¥ª¥×¥·¥ç¥ó¤Ë´Ø¤¹¤ëÄɲþðÊó¤Ï¡¢ + ¥µ¡¼¥Ð¤ÈÊä½õ¥×¥í¥°¥é¥à¥Ú¡¼¥¸¤Ë + µ­ºÜ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + Apache ÇÛÉۤ˴ޤޤì¤Æ¤¤¤ëÁ´¥â¥¸¥å¡¼¥ë¡¢ + ¤½¤ì¤Ë¤è¤Ã¤ÆÄ󶡤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤Î¥É¥­¥å¥á¥ó¥È¤â¤¢¤ê¤Þ¤¹¡£

+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/invoking.html.ko.euc-kr b/docs/manual/invoking.html.ko.euc-kr new file mode 100644 index 00000000..24ba2a14 --- /dev/null +++ b/docs/manual/invoking.html.ko.euc-kr @@ -0,0 +1,140 @@ + + + +¾ÆÆÄÄ¡ ½ÃÀÛ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¾ÆÆÄÄ¡ ½ÃÀÛ

+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + ja  | + ko  | + ru 

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

º¸Åë ¾ÆÆÄÄ¡´Â Windows NT, 2000, XP¿¡¼­´Â ¼­ºñ½º·Î, + Windows 95°ú ME¿¡¼­´Â ÄÜ¼Ö ÇÁ·Î±×·¥À¸·Î ½ÇÇàµÈ´Ù. ÀÚ¼¼ÇÑ + ³»¿ëÀº ¼­ºñ½º·Î + ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇϱâ¿Í ÄÜ¼Ö ÇÁ·Î±×·¥À¸·Î + ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇϱâ.

+ +

À¯´Ð½º¿¡¼­ httpd + ÇÁ·Î±×·¥Àº ¹é±×¶ó¿îµå¿¡¼­ °è¼Ó ¿äûÀ» ó¸®ÇÏ´Â µ¥¸óÀ¸·Î + ½ÇÇàµÈ´Ù. ÀÌ ¹®¼­´Â httpd¸¦ ½ÃÀÛÇÏ´Â ¹æ¹ýÀ» + ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

¾î¶»°Ô ¾ÆÆÄÄ¡°¡ ½ÃÀÛÇϳª

+ +

¼³Á¤ÆÄÀÏ¿¡¼­ ListenÀÌ ±âº»°ªÀÎ 80(ȤÀº + 1024ÀÌÇÏÀÇ ´Ù¸¥ Æ÷Æ®)À̶ó¸é ÀÌ Æ¯±Ç Æ÷Æ®¿¡ ¿¬°áÇϱâÀ§ÇØ + root ±ÇÇÑÀÌ ÇÊ¿äÇÏ´Ù. ¼­¹ö´Â ½ÃÀÛÇÏ¿© ·Î±×ÆÄÀÏÀ» ¿©´Â µîÀÇ + ¸î¸î ±âÃÊÀûÀÎ ÀÛ¾÷À» ¸¶Ä£ÈÄ, Ŭ¶óÀ̾ðÆ®ÀÇ ¿äûÀ» ±â´Ù¸®°í + ÀÀ´äÇÏ´Â ÀÚ½Ä(child) ÇÁ·Î¼¼½º¸¦ ¿©·¯°³ ¶ç¿î´Ù. + ÁÖ httpd ÇÁ·Î¼¼½º´Â °è¼Ó root »ç¿ëÀÚ·Î ½ÇÇàµÇÁö¸¸, + ÀÚ½Ä ÇÁ·Î¼¼½ºµéÀº ´õ ±ÇÇÑÀÌ ÀÛÀº »ç¿ëÀÚ·Î ½ÇÇàµÈ´Ù. ÀÌ´Â + ¼±ÅÃÇÑ ´ÙÁßó¸® ¸ðµâ·Î Á¶Á¤ÇÑ´Ù.

+ +

apachectl + ½ºÅ©¸³Æ®¸¦ »ç¿ëÇÏ¿© httpd ½ÇÇàÆÄÀÏÀ» ½ÃÀÛÇϱæ + ±ÇÀåÇÑ´Ù. ÀÌ ½ºÅ©¸³Æ®´Â httpd°¡ ¸î¸î + ¿î¿µÃ¼Á¦¿¡¼­ Á¤»óÀûÀ¸·Î µ¿ÀÛÇϱâÀ§ÇØ ÇÊ¿äÇÑ È¯°æº¯¼öµéÀ» + ¼³Á¤ÇÏ°í httpd ½ÇÇàÆÄÀÏÀ» ½ÃÀÛÇÑ´Ù. + apachectlÀº ¸í·ÉÇà ¾Æ±Ô¸ÕÆ®¸¦ ±×´ë·Î ³Ñ±â±â¶§¹®¿¡, + httpdÀÇ ¾î¶² ¿É¼ÇÀÌ¶óµµ apachectl¿¡ + »ç¿ë°¡´ÉÇÏ´Ù. ¶Ç, apachectl ½ºÅ©¸³Æ®ÀÇ ¾ÕºÎºÐ¿¡ + ³ª¿À´Â HTTPD º¯¼ö¸¦ httpd ½ÇÇàÆÄÀÏÀÌ + ÀÖ´Â À§Ä¡¿Í Ç×»ó »ç¿ëÇÒ ¸í·ÉÇà ¾Æ±Ô¸ÕÆ®·Î Á÷Á¢ + ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +

httpd¸¦ ½ÇÇàÇÏ¸é ¸ÕÀú ¼³Á¤ÆÄÀÏ httpd.conf¸¦ + ã¾Æ¼­ Àд´Ù. ÀÌ ÆÄÀÏÀÇ À§Ä¡´Â ÄÄÆÄÀÏ Áß¿¡ ÁöÁ¤Çϳª, ½ÇÇà½Ã + ´ÙÀ½°ú °°ÀÌ -f ¸í·ÉÇà ¿É¼ÇÀ¸·Î ÁöÁ¤ÇÒ ¼öµµ ÀÖ´Ù.

+ +

/usr/local/apache2/bin/apachectl -f + /usr/local/apache2/conf/httpd.conf

+ +

½ÃÀÛÇÏ´Â °úÁ¤¿¡¼­ ¹®Á¦°¡ ¾ø´Ù¸é, ¼­¹ö´Â Å͹̳ο¡¼­ + ¶³¾îÁö°í ¸í·É ÇÁ·ÒÇÁÆ®°¡ °ÅÀÇ Áï½Ã ³ª¿À°ÔµÈ´Ù. ÀÌ´Â ¼­¹ö°¡ + ½ÇÇàµÊÀ» ÀǹÌÇÑ´Ù. ºê¶ó¿ìÀú·Î ¼­¹ö¿¡ ¿¬°áÇÏ¿© DocumentRoot µð·ºÅ丮¿¡ ÀÖ´Â + Å×½ºÆ® ÆäÀÌÁö¿Í ±× ÆäÀÌÁö¿¡ ¸µÅ©µÈ (·ÎÄÃÄ«ÇÇ) ¼³¸í¼­¸¦ º¼ + ¼ö ÀÖ´Ù.

+
top
+
+

½ÃÀÛÁß ¿À·ù

+ +

¾ÆÆÄÄ¡°¡ ½ÃÀÛÇÏ´Â °úÁ¤Áß¿¡ ½É°¢ÇÑ ¹®Á¦°¡ ¹ß»ýÇϸé, + Á¾·áÇϱâ Àü¿¡ ¹®Á¦¸¦ ¾Ë¸®´Â ¹®±¸¸¦ ÄܼÖÀ̳ª ErrorLog¿¡ ¾´´Ù. °¡Àå ÈçÇÑ ¿À·ù¹® Áß + Çϳª´Â "Unable to bind to Port ..."ÀÌ´Ù. + ÀÌ ¸Þ¼¼Áö´Â º¸Åë ´ÙÀ½ µÎ °æ¿ì¿¡ ¹ß»ýÇÑ´Ù:

+ +
    +
  • root »ç¿ëÀÚ·Î ·Î±×ÀÎÇÏÁö ¾Ê°í Ư±Ç Æ÷Æ®¿¡ ¼­¹ö¸¦ + ½ÃÀÛÇÏ·Á ÇÑ °æ¿ì. ȤÀº
    • + +
  • ÀÌ¹Ì ¾ÆÆÄÄ¡³ª ´Ù¸¥ À¥¼­¹ö°¡ »ç¿ëÁßÀÎ Æ÷Æ®¿¡ + ¼­¹ö¸¦ ½ÃÀÛÇÏ·Á ÇÑ °æ¿ì.
    • +
+ +

±âŸ ¹®Á¦ÇØ°á ¹æ¹ýÀº ¾ÆÆÄÄ¡ FAQ¸¦ + Âü°íÇ϶ó.

+
top
+
+

ºÎÆÃÇÒ¶§ ½ÃÀÛÇϱâ

+ +

½Ã½ºÅÛÀÌ Àç½ÃÀÛÇÑ ÈÄ¿¡µµ ¼­¹ö°¡ °è¼Ó ½ÇÇàµÇ±æ ¹Ù¶õ´Ù¸é, + ½Ã½ºÅÛ ½ÃÀÛÆÄÀÏ(º¸Åë rc.localÀ̳ª rc.N + µð·ºÅ丮¿¡ ÀÖ´Â ÆÄÀÏ)¿¡ apachectlÀ» Ãß°¡ÇØ¾ß + ÇÑ´Ù. ÀÌ °æ¿ì ¾ÆÆÄÄ¡´Â root·Î ½ÃÀ۵ȴÙ. ÀÌÀü¿¡ ¼­¹öÀÇ º¸¾ÈÀ̳ª + Á¢±Ù Á¦ÇÑ(ÆÄÀϱÇÇÑ)ÀÌ ¿Ã¹Ù·Î ¼³Á¤µÇ¾ú´ÂÁö È®ÀÎÇ϶ó.

+ +

apachectlÀº Ç¥ÁØ SysV init ½ºÅ©¸³Æ®¿Í ºñ½ÁÇÏ°Ô + µ¿ÀÛÇϵµ·Ï ¸¸µé¾îÁ³´Ù. ½ºÅ©¸³Æ®´Â ¾Æ±Ô¸ÕÆ®·Î start, + restart, stopÀ» ¹ÞÀ¸¸é °¢°¢ ÀûÀýÇÑ + ½Ã±×³ÎÀ» httpd¿¡ º¸³½´Ù. ±×·¡¼­ º¸ÅëÀº + apachectlÀ» ÀûÀýÇÑ init µð·ºÅ丮·Î ¸µÅ©¸¦ °É¸éµÈ´Ù. + ±×·¯³ª »ç¿ëÇÏ´Â ½Ã½ºÅÛÀÇ Á¤È®ÇÑ ¿ä±¸»çÇ×À» È®ÀÎÇ϶ó.

+
top
+
+

Ãß°¡ Á¤º¸

+ +

httpd¿Í apachectl, ±âŸ ¼­¹ö¿¡ + Æ÷ÇÔµÈ Áö¿ø ÇÁ·Î±×·¥µéÀÇ ¸í·ÉÇà ¿É¼ÇÀº + ¼­¹ö¿Í Áö¿ø ÇÁ·Î±×·¥ ÆäÀÌÁö¸¦ + Âü°íÇ϶ó. ¶Ç ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡´Â ¸ðµç ¸ðµâ°ú + ±×µéÀÌ Á¦°øÇÏ´Â Áö½Ã¾î¿¡ + ´ëÇÑ ¹®¼­°¡ ÀÖ´Ù.

+
+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/invoking.html.ru.koi8-r b/docs/manual/invoking.html.ru.koi8-r new file mode 100644 index 00000000..0bd6d5b0 --- /dev/null +++ b/docs/manual/invoking.html.ru.koi8-r @@ -0,0 +1,143 @@ + + + +úÁÐÕÓË Apache - HTTP ÓÅÒ×ÅÒ Apache + + + + +
+

íÏÄÕÌÉ | äÉÒÅËÔÉ×Ù | FAQ | çÌÏÓÓÁÒÉÊ | ëÁÒÔÁ ÓÁÊÔÁ

+

HTTP ÓÅÒ×ÅÒ Apache ×ÅÒÓÉÉ 2.2

+
+
<-
+
+Apache > HTTP ÓÅÒ×ÅÒ > äÏËÕÍÅÎÔÁÃÉÑ > ÷ÅÒÓÉÑ 2.2

úÁÐÕÓË Apache

+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

îÁ Windows ÐÌÁÔÆÏÒÍÁÈ Apache ÏÂÙÞÎÏ ÒÁÂÏÔÁÅÔ ËÁË ÓÅÒ×ÉÓ Windows NT/2000/XP + ÉÌÉ ËÁË ËÏÎÓÏÌØÎÏÅ ÐÒÉÌÏÖÅÎÉÅ Windows 95/ME. äÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏÊ + ÉÎÆÏÒÍÁÃÉÉ ÐÏ ÜÔÏÍÕ ×ÏÐÒÏÓÕ, ÏÂÒÁÔÉÔÅÓØ Ë ÄÏËÕÍÅÎÔÁÍ, ÏÂßÑÓÎÑÀÝÉÍ ÒÁÂÏÔÕ Apache ÐÏÄ Windows × ËÁÞÅÓÔ×Å ÓÅÒ×ÉÓÁ É + ÒÁÂÏÔÕ Apache ÐÏÄ Windows × ËÁÞÅÓÔ×Å ËÏÎÓÏÌØÎÏÇÏ + ÐÒÉÌÏÖÅÎÉÑ.

+ +

÷ Unix ÐÒÏÇÒÁÍÍÁ httpd ÐÒÅÄÓÔÁ×ÌÑÅÔ ÓÏÂÏÊ + ÄÅÍÏÎ, ×ÙÐÏÌÎÑÀÝÉÊÓÑ × ÆÏÎÏ×ÏÍ ÒÅÖÉÍÅ É ÏÂÓÌÕÖÉ×ÁÀÝÉÊ ÐÏÓÔÕÐÁÀÝÉÅ ÚÁÐÒÏÓÙ. + ï ÔÏÍ, ËÁËÉÍ ÏÂÒÁÚÏÍ ÍÏÖÎÏ ÚÁÐÕÓÔÉÔØ httpd É ÞÔÏ × ÒÅÚÕÌØÔÁÔÅ ÜÔÏÇÏ + ÐÏÌÕÞÉÔÓÑ, É ÒÁÓÓËÁÚÙ×ÁÅÔÓÑ × ÜÔÏÍ ÄÏËÕÍÅÎÔÅ.

+
+ +
top
+
+

þÔÏ ÐÒÏÉÓÈÏÄÉÔ × ÍÏÍÅÎÔ ÚÁÐÕÓËÁ Apache

+ +

åÓÌÉ × ÄÉÒÅËÔÉ×Å Listen + × ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÍ ÆÁÊÌÅ ÕËÁÚÁÎÏ ÚÎÁÞÅÎÉÅ 80 (ÚÁÄÁ×ÁÅÍÏÅ ÐÏ ÕÍÏÌÞÁÎÉÀ) + ÉÌÉ ÌÀÂÏÅ ÄÒÕÇÏÅ ÚÎÁÞÅÎÉÅ ÐÏÒÔÁ ÍÅÎØÛÅÅ 1024, ÔÏ ÄÌÑ ÚÁÐÕÓËÁ Apache + ÎÅÏÂÈÏÄÉÍÏ ÂÙÔØ ÐÒÉ×ÉÌÅÇÉÒÏ×ÁÎÎÙÍ ÐÏÌØÚÏ×ÁÔÅÌÅÍ, ÔÁË ËÁË Apache ÐÒÉÄÅÔÓÑ + ÐÏÄËÌÀÞÁÔØÓÑ Ë ÐÒÉ×ÉÌÅÇÉÒÏ×ÁÎÎÏÍÕ ÐÏÒÔÕ. ðÏÓÌÅ ÔÏÇÏ, ËÁË ÓÅÒ×ÅÒ ÚÁÐÕÓÔÉÌÓÑ + É ×ÙÐÏÌÎÉÌ ÒÑÄ ÐÏÄÇÏÔÏ×ÉÔÅÌØÎÙÈ ÏÐÅÒÁÃÉÊ, ÔÁËÉÈ ËÁË ÏÔËÒÙÔÉÅ Ó×ÏÉÈ log-ÆÁÊÌÏ×, + ÏÎ ÐÏÒÏÖÄÁÅÔ ÎÅÓËÏÌØËÏ ÐÒÏÃÅÓÓÏ× ÐÏÔÏÍËÏ×, ËÏÔÏÒÙÅ É ÂÕÄÕÔ ×ÙÐÏÌÎÑÔØ + ×ÓÀ ÒÁÂÏÔÕ ÐÏ ÏÂÒÁÂÏÔËÅ ÚÁÐÒÏÓÏ× ÏÔ ËÌÉÅÎÔÏ×. ïÓÎÏ×ÎÏÊ ÐÒÏÃÅÓÓ httpd + ×ÙÐÏÌÎÑÅÔÓÑ Ó ÐÒÁ×ÁÍÉ ÐÒÉ×ÉÌÅÇÉÒÏ×ÁÎÎÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ, × ÔÏ ×ÒÅÍÑ ËÁË ÐÒÏÃÅÓÓÙ + ÐÏÔÏÍËÉ ÉÍÅÀÔ ÍÅÎØÛÉÊ ÐÒÉÏÒÉÔÅÔ. ÷ÓÅ ÜÔÏ ËÏÎÔÒÏÌÉÒÕÅÔÓÑ íð-ÍÏÄÕÌÅÍ, ËÏÔÏÒÙÊ ËÏÍÐÉÌÉÒÕÅÔÓÑ ×ÍÅÓÔÅ Ó ÓÅÒ×ÅÒÏÍ.

+ +

äÌÑ ÚÁÐÕÓËÁ ÄÅÍÏÎÁ httpd ÌÕÞÛÅ ×ÓÅÇÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÓËÒÉÐÔ + apachectl. üÔÏÔ ÓËÒÉÐÔ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔ ÒÑÄ + ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ, ÎÅÏÂÈÏÄÉÍÙÈ ÄÌÑ ÐÒÁ×ÉÌØÎÏÊ ÒÁÂÏÔÙ ÓÅÒ×ÅÒÁ ÐÏÄ ÎÅËÏÔÏÒÙÍÉ + ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ, Á ÚÁÔÅÍ ÚÁÐÕÓËÁÅÔ ÉÓÐÏÌÎÑÅÍÙÊ ÆÁÊÌ httpd. + óËÒÉÐÔ apachectl ÐÅÒÅÄÁÓÔ ÓÅÒ×ÅÒÕ ÌÀÂÕÀ ËÏÍÁÎÄÎÕÀ ÓÔÒÏËÕ, ÔÁË ÞÔÏ + ÐÒÉ ×ÙÚÏ×Å ÍÏÖÎÏ ÕËÁÚÙ×ÁÔØ × ÅÇÏ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÅ ×ÓÅ ÎÅÏÂÈÏÄÉÍÙÅ ÄÌÑ ÓÅÒ×ÅÒÁ ÏÐÃÉÉ. + ÷Ù ÔÁËÖÅ ÍÏÖÅÔÅ ×ÒÕÞÎÕÀ ×ÎÅÓÔÉ ÎÅËÏÔÏÒÙÅ ÉÚÍÅÎÅÎÉÑ × ÓËÒÉÐÔ apachectl, + × ÞÁÓÔÎÏÓÔÉ, ÉÚÍÅÎÉ× ÚÎÁÞÅÎÉÅ ÐÅÒÅÍÅÎÎÏÊ HTTPD ÄÌÑ ÚÁÐÕÓËÁ Apache + ÉÚ ÄÒÕÇÏÇÏ ËÁÔÁÌÏÇÁ, É ÕËÁÚÁ× ÏÐÃÉÉ, ËÏÔÏÒÙÅ ÂÕÄÕÔ ÐÅÒÅÄÁ×ÁÔØÓÑ ÓÅÒ×ÅÒÕ ËÁÖÄÙÊ ÒÁÚ + ÐÒÉ ÅÇÏ ÚÁÐÕÓËÅ.

+ +

ðÅÒ×ÙÍ ÄÅÌÏÍ httpd ÎÁÈÏÄÉÔ É ÓÞÉÔÙ×ÁÅÔ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ + ÆÁÊÌ httpd.conf. ðÕÔØ Ë ÜÔÏÍÕ ÆÁÊÌÕ ÚÁÄÁÅÔÓÑ ÅÝÅ ×Ï ×ÒÅÍÑ ÓÂÏÒËÉ ÓÅÒ×ÅÒÁ, + ÎÏ ÅÇÏ ÍÏÖÎÏ ÉÚÍÅÎÉÔØ É ÐÏÓÌÅ ÜÔÏÇÏ, ÚÁÐÕÓÔÉ× ÓÅÒ×ÅÒ Ó ÏÐÃÉÅÊ -f, ËÁË ÜÔÏ ÐÏËÁÚÁÎÏ + × ÓÌÅÄÕÀÝÅÍ ÐÒÉÍÅÒÅ

+ +

/usr/local/apache2/bin/apachectl -f + /usr/local/apache2/conf/httpd.conf

+ +

åÓÌÉ ×Ï ×ÒÅÍÑ ÚÁÐÕÓËÁ ÎÅ ×ÏÚÎÉËÌÏ ÎÉËÁËÉÈ ÐÒÏÂÌÅÍ, ÔÏ ÓÅÒ×ÅÒ ÏÔÓÏÅÄÉÎÉÔÓÑ + ÏÔ ËÏÎÓÏÌÉ É ÐÒÉÇÌÁÛÅÎÉÅ ÎÁ ××ÏÄ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ ×ÅÒÎÅÔÓÑ Ë ÐÏÌØÚÏ×ÁÔÅÌÀ + ÐÒÁËÔÉÞÅÓËÉ ÍÇÎÏ×ÅÎÎÏ. üÔÏ ÕËÁÚÙ×ÁÅÔ ÎÁ ÔÏ, ÞÔÏ ÓÅÒ×ÅÒ ÚÁÐÕÓÔÉÌÓÑ É ÔÅÐÅÒØ + ×ÙÐÏÌÎÑÅÔ Ó×ÏÀ ÒÁÂÏÔÕ. ôÅÐÅÒØ ×Ù ÍÏÖÅÔÅ, ÉÓÐÏÌØÚÕÑ ÂÒÁÕÚÅÒ, ÐÏÄËÌÀÞÉÔØÓÑ Ë + ÎÅÍÕ É Õ×ÉÄÅÔØ ÔÅÓÔÏ×ÕÀ ÓÔÒÁÎÉÃÕ, ÎÁÈÏÄÑÝÕÀÓÑ × ËÁÔÁÌÏÇÅ + DocumentRoot, Á ÔÁËÖÅ ÌÏËÁÌØÎÕÀ ËÏÐÉÀ ÄÏËÕÍÅÎÔÁÃÉÉ, + ÓÓÙÌËÕ ÎÁ ËÏÔÏÒÕÀ ×Ù ÎÁÊÄÅÔÅ ÎÁ ÔÏÊ ÖÅ ÓÔÒÁÎÉÃÅ.

+
top
+
+

ïÛÉÂËÉ, ËÏÔÏÒÙÅ ÍÏÇÕÔ ×ÏÚÎÉËÎÕÔØ ×Ï ×ÒÅÍÑ ÚÁÐÕÓËÁ

+ +

åÓÌÉ ×Ï ×ÒÅÍÑ ÚÁÐÕÓËÁ Apache ÐÒÏÉÚÏÊÄÅÔ ËÁËÁÑ-ÌÉÂÏ ÆÁÔÁÌØÎÁÑ ÏÛÉÂËÁ, + ÔÏ ÐÅÒÅÄ ÔÅÍ, ËÁË ÚÁ×ÅÒÛÉÔØ Ó×ÏÀ ÒÁÂÏÔÕ, ÓÅÒ×ÅÒ ÐÏÛÌÅÔ ÎÁ ËÏÎÓÏÌØ ÉÌÉ × + ErrorLog ÓÏÏÂÝÅÎÉÅ, ÏÐÉÓÙ×ÁÀÝÅÅ + ÄÁÎÎÕÀ ÏÛÉÂËÕ. îÁÉÂÏÌÅÅ ÒÁÓÐÒÏÓÔÒÁÎÅÎÎÙÍ ÓÏÏÂÝÅÎÉÅÍ Ï ÏÛÉÂËÅ Ñ×ÌÑÅÔÓÑ + "Unable to bind to Port ...". ðÏÄÏÂÎÁÑ ÏÛÉÂËÁ ×ÏÚÎÉËÁÅÔ × Ä×ÕÈ ÓÌÕÞÁÑÈ:

+ +
    +
  • åÓÌÉ ×Ù ÐÙÔÁÅÔÅÓØ ÚÁÐÕÓÔÉÔØ ÓÅÒ×ÅÒ ÎÁ ÐÒÉ×ÉÌÅÇÉÒÏ×ÁÎÎÏÍ ÐÏÒÔÕ, ÂÕÄÕÞÉ ÚÁÒÅÇÉÓÔÒÉÒÏ×ÁÎÎÙÍ + × ÓÉÓÔÅÍÅ ËÁË ÏÂÙÞÎÙÊ ÐÏÌØÚÏ×ÁÔÅÌØ; ÉÌÉ
    • + +
  • åÓÌÉ ×Ù ÐÙÔÁÅÔÅÓØ ÚÁÐÕÓÔØ ÓÅÒ×ÅÒ, ËÏÇÄÁ × ÓÉÓÔÅÍÅ ÕÖÅ ÅÓÔØ ×ÙÐÏÌÎÑÀÝÉÊÓÑ ÄÅÍÏÎ Apache + ÉÌÉ ÄÒÕÇÏÊ web-ÓÅÒ×ÅÒ, ÓÌÕÛÁÀÝÉÊ ÔÏÔ ÖÅ ÓÁÍÙÊ ÐÏÒÔ.
    • +
+ +

òÅÛÅÎÉÅ ÍÎÏÇÉÈ ÐÏÄÏÂÎÙÈ ÐÒÏÂÌÅÍ ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ ÓÔÒÁÎÉÃÅ + FAQ.

+
top
+
+

úÁÐÕÓË ÓÅÒ×ÅÒÁ ×ÍÅÓÔÅ Ó ÚÁÐÕÓËÏÍ ×ÓÅÊ ÓÉÓÔÅÍÙ

+ +

åÓÌÉ ×Ù ÈÏÔÉÔÅ, ÞÔÏÂÙ ÓÅÒ×ÅÒ ÚÁÐÕÓËÁÌÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ ÐÏÓÌÅ ÐÅÒÅÚÁÇÒÕÚËÉ ÓÉÓÔÅÍÙ, + ÄÏÂÁ×ØÔÅ ×ÙÚÏ× ÓËÒÉÐÔÁ apachectl × ÓÉÓÔÅÍÎÙÅ ÆÁÊÌÙ, ÏÔ×ÅÞÁÀÝÉÅ ÚÁ ÚÁÇÒÕÚËÕ + ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÒÅÄÙ (ÏÂÙÞÎÏ ÜÔÏ rc.local ÉÌÉ ÆÁÊÌÙ × ËÁÔÁÌÏÇÅ rc.N). + üÔÏ ÐÒÉ×ÅÄÅÔ Ë ÚÁÐÕÓËÕ Apache ÏÔ ÉÍÅÎÉ ÐÒÉ×ÉÌÅÇÉÒÏ×ÁÎÎÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. + ÷Ï ÉÚÂÅÖÁÎÉÅ ÐÒÏÂÌÅÍ Ó ÂÅÚÏÐÁÓÎÏÓÔØÀ ÓÉÓÔÅÍÙ, ÕÂÅÄÉÔÅÓØ, ÞÔÏ ÓÅÒ×ÅÒ ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÎ ÐÒÁ×ÉÌØÎÏ.

+ +

óËÒÉÐÔ apachectl ÒÁÚÒÁÂÏÔÁÎ ÔÁËÉÍ ÏÂÒÁÚÏÍ, ÞÔÏ ÏÎ ÍÏÖÅÔ + ÄÅÊÓÔ×Ï×ÁÔØ ËÁË ÓÔÁÎÄÁÒÔÎÙÊ init-ÓËÒÉÐÔ ÓÉÓÔÅÍÙ SysV; ÏÎ ÍÏÖÅÔ ÐÒÉÎÉÍÁÔØ + ÁÒÇÕÍÅÎÔÙ start, restart, É stop + É ÐÅÒÅ×ÏÄÉÔØ ÉÈ × ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÅ ÓÉÇÎÁÌÙ ÐÒÏÃÅÓÓÕ httpd. + ðÏÜÔÏÍÕ ÞÁÝÅ ×ÓÅÇÏ ×ÁÍ ÄÏÓÔÁÔÏÞÎÏ ÓÄÅÌÁÔØ ÓÓÙÌËÕ ÎÁ apachectl + × ÚÁÐÕÓËÎÏÍ ËÁÔÁÌÏÇÅ ÐÒÏÃÅÓÓÁ init. îÏ ÐÒÅÖÄÅ ÞÅÍ ÄÅÌÁÔØ ÜÔÏ, ÕÚÎÁÊÔÅ + ÔÏÞÎÙÅ ÔÒÅÂÏ×ÁÎÉÑ ×ÁÛÅÊ ÓÉÓÔÅÍÙ.

+
top
+
+

äÏÐÏÌÎÉÔÅÌØÎÁÑ ÉÎÆÏÒÍÁÃÉÑ

+ +

äÏÐÏÌÎÉÔÅÌØÎÕÀ ÉÎÆÏÒÍÁÃÉÀ ÐÏ ÏÐÃÉÑÍ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ httpd + É apachectl, Á ÔÁËÖÅ ÄÒÕÇÉÈ + ×ÓÐÏÍÏÇÁÔÅÌØÎÙÈ ÐÒÏÇÒÁÍÍ, ×Ù ÍÏÖÅÔÅ ÎÁÊÔÉ ÎÁ ÓÔÒÁÎÉÃÅ "óÅÒ×ÅÒ + É ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÐÒÏÇÒÁÍÍÙ". éÍÅÅÔÓÑ ÔÁËÖÅ ÄÏËÕÍÅÎÔÁÃÉÑ + ÎÁ ×ÓÅ ÍÏÄÕÌÉ, ×ÈÏÄÑÝÉÅ × ÄÉÓÔÒÉÂÕÔÉ× Apache, É ×ÓÅ ÄÉÒÅËÔÉ×Ù, ËÏÔÏÒÙÅ ÏÎÉ ÐÒÅÄÏÓÔÁ×ÌÑÀÔ.

+
+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/license.html b/docs/manual/license.html new file mode 100644 index 00000000..11472e45 --- /dev/null +++ b/docs/manual/license.html @@ -0,0 +1,3 @@ +URI: license.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/license.html.en b/docs/manual/license.html.en new file mode 100644 index 00000000..4dc2d17f --- /dev/null +++ b/docs/manual/license.html.en @@ -0,0 +1,238 @@ + + + +The Apache License, Version 2.0 - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

The Apache License, Version 2.0

+
+

Available Languages:  en 

+
+ +

Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/

+ + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

+ +
    +
  1. Definitions
    + +

    "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document.

    + +

    "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License.

    + +

    "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity.

    + +

    "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License.

    + +

    "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files.

    + +

    "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types.

    + +

    "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below).

    + +

    "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof.

    + +

    "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution."

    + +

    "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work.

    2. + +
  2. Grant of Copyright License. Subject to the terms + and conditions of this License, each Contributor hereby grants to You + a perpetual, worldwide, non-exclusive, no-charge, royalty-free, + irrevocable copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form.
    3. + +
  3. Grant of Patent License. Subject to the terms + and conditions of this License, each Contributor hereby grants to You a + perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed.
    4. + +
  4. Redistribution. You may reproduce and distribute + copies of the Work or Derivative Works thereof in any medium, with or + without modifications, and in Source or Object form, provided that You + meet the following conditions: + +
      +
    1. You must give any other recipients of the Work or + Derivative Works a copy of this License; and
      2. + +
    2. You must cause any modified files to carry prominent notices + stating that You changed the files; and
      3. + +
    3. You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and
      4. + +
    4. If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License.
      5. +
    + +

    You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License.

    5. + +
  5. Submission of Contributions. Unless You explicitly + state otherwise, any Contribution intentionally submitted for inclusion + in the Work by You to the Licensor shall be under the terms and + conditions of this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions.
    6. + +
  6. Trademarks. This License does not grant permission + to use the trade names, trademarks, service marks, or product names of + the Licensor, except as required for reasonable and customary use in + describing the origin of the Work and reproducing the content of the + NOTICE file.
    7. + +
  7. Disclaimer of Warranty. Unless required by + applicable law or agreed to in writing, Licensor provides the Work (and + each Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License.
    8. + +
  8. Limitation of Liability. In no event and under no + legal theory, whether in tort (including negligence), contract, or + otherwise, unless required by applicable law (such as deliberate and + grossly negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages.
    9. + +
  9. Accepting Warranty or Additional Liability. While + redistributing the Work or Derivative Works thereof, You may choose to + offer, and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability.
    10. +
+ +

END OF TERMS AND CONDITIONS

+ +

APPENDIX: How to apply the Apache License to your + work.

+ +

To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives.

+ + 
Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/logs.html b/docs/manual/logs.html new file mode 100644 index 00000000..0ab020d4 --- /dev/null +++ b/docs/manual/logs.html @@ -0,0 +1,11 @@ +URI: logs.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: logs.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: logs.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en new file mode 100644 index 00000000..6f661d80 --- /dev/null +++ b/docs/manual/logs.html.en @@ -0,0 +1,602 @@ + + + +Log Files - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Log Files

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

In order to effectively manage a web server, it is necessary + to get feedback about the activity and performance of the + server as well as any problems that may be occurring. The Apache + HTTP Server provides very comprehensive and flexible logging + capabilities. This document describes how to configure its + logging capabilities, and how to understand what the logs + contain.

+
+ +
top
+
+

Security Warning

+ + +

Anyone who can write to the directory where Apache is + writing a log file can almost certainly gain access to the uid + that the server is started as, which is normally root. Do + NOT give people write access to the directory the logs + are stored in without being aware of the consequences; see the + security tips document + for details.

+ +

In addition, log files may contain information supplied + directly by the client, without escaping. Therefore, it is + possible for malicious clients to insert control-characters in + the log files, so care must be taken in dealing with raw + logs.

+
top
+
+

Error Log

+ + +
Related ModulesRelated Directives
+ +

The server error log, whose name and location is set by the + ErrorLog directive, is the + most important log file. This is the place where Apache httpd + will send diagnostic information and record any errors that it + encounters in processing requests. It is the first place to + look when a problem occurs with starting the server or with the + operation of the server, since it will often contain details of + what went wrong and how to fix it.

+ +

The error log is usually written to a file (typically + error_log on unix systems and + error.log on Windows and OS/2). On unix systems it + is also possible to have the server send errors to + syslog or pipe them to a + program.

+ +

The format of the error log is relatively free-form and + descriptive. But there is certain information that is contained + in most error log entries. For example, here is a typical + message.

+ +

+ [Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1] + client denied by server configuration: + /export/home/live/ap/htdocs/test +

+ +

The first item in the log entry is the date and time of the + message. The second entry lists the severity of the error being + reported. The LogLevel + directive is used to control the types of errors that are sent + to the error log by restricting the severity level. The third + entry gives the IP address of the client that generated the + error. Beyond that is the message itself, which in this case + indicates that the server has been configured to deny the + client access. The server reports the file-system path (as + opposed to the web path) of the requested document.

+ +

A very wide variety of different messages can appear in the + error log. Most look similar to the example above. The error + log will also contain debugging output from CGI scripts. Any + information written to stderr by a CGI script will + be copied directly to the error log.

+ +

It is not possible to customize the error log by adding or + removing information. However, error log entries dealing with + particular requests have corresponding entries in the access log. For example, the above example + entry corresponds to an access log entry with status code 403. + Since it is possible to customize the access log, you can + obtain more information about error conditions using that log + file.

+ +

During testing, it is often useful to continuously monitor + the error log for any problems. On unix systems, you can + accomplish this using:

+ +

+ tail -f error_log +

+
top
+
+

Access Log

+ + +
Related ModulesRelated Directives
+ +

The server access log records all requests processed by the + server. The location and content of the access log are + controlled by the CustomLog + directive. The LogFormat + directive can be used to simplify the selection of + the contents of the logs. This section describes how to configure the server + to record information in the access log.

+ +

Of course, storing the information in the access log is only + the start of log management. The next step is to analyze this + information to produce useful statistics. Log analysis in + general is beyond the scope of this document, and not really + part of the job of the web server itself. For more information + about this topic, and for applications which perform log + analysis, check the + Open Directory or + Yahoo.

+ +

Various versions of Apache httpd have used other modules and + directives to control access logging, including + mod_log_referer, mod_log_agent, and the + TransferLog directive. The CustomLog directive now subsumes + the functionality of all the older directives.

+ +

The format of the access log is highly configurable. The format + is specified using a format string that looks much like a C-style + printf(1) format string. Some examples are presented in the next + sections. For a complete list of the possible contents of the + format string, see the mod_log_config format strings.

+ +

Common Log Format

+ + +

A typical configuration for the access log might look as + follows.

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common +

+ +

This defines the nickname common and + associates it with a particular log format string. The format + string consists of percent directives, each of which tell the + server to log a particular piece of information. Literal + characters may also be placed in the format string and will be + copied directly into the log output. The quote character + (") must be escaped by placing a back-slash before + it to prevent it from being interpreted as the end of the + format string. The format string may also contain the special + control characters "\n" for new-line and + "\t" for tab.

+ +

The CustomLog + directive sets up a new log file using the defined + nickname. The filename for the access log is relative to + the ServerRoot unless it + begins with a slash.

+ +

The above configuration will write log entries in a format + known as the Common Log Format (CLF). This standard format can + be produced by many different web servers and read by many log + analysis programs. The log file entries produced in CLF will + look something like this:

+ +

+ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET + /apache_pb.gif HTTP/1.0" 200 2326 +

+ +

Each part of this log entry is described below.

+ +
+
127.0.0.1 (%h)
+ +
This is the IP address of the client (remote host) which + made the request to the server. If HostnameLookups is + set to On, then the server will try to determine + the hostname and log it in place of the IP address. However, + this configuration is not recommended since it can + significantly slow the server. Instead, it is best to use a + log post-processor such as logresolve to determine + the hostnames. The IP address reported here is not + necessarily the address of the machine at which the user is + sitting. If a proxy server exists between the user and the + server, this address will be the address of the proxy, rather + than the originating machine.
+ +
- (%l)
+ +
The "hyphen" in the output indicates that the requested + piece of information is not available. In this case, the + information that is not available is the RFC 1413 identity of + the client determined by identd on the clients + machine. This information is highly unreliable and should + almost never be used except on tightly controlled internal + networks. Apache httpd will not even attempt to determine + this information unless IdentityCheck is set + to On.
+ +
frank (%u)
+ +
This is the userid of the person requesting the document + as determined by HTTP authentication. The same value is + typically provided to CGI scripts in the + REMOTE_USER environment variable. If the status + code for the request (see below) is 401, then this value + should not be trusted because the user is not yet + authenticated. If the document is not password protected, + this entry will be "-" just like the previous + one.
+ +
[10/Oct/2000:13:55:36 -0700] + (%t)
+ +
+ The time that the request was received. + The format is: + +

+ [day/month/year:hour:minute:second zone]
+ day = 2*digit
+ month = 3*letter
+ year = 4*digit
+ hour = 2*digit
+ minute = 2*digit
+ second = 2*digit
+ zone = (`+' | `-') 4*digit +

+ It is possible to have the time displayed in another format + by specifying %{format}t in the log format + string, where format is as in + strftime(3) from the C standard library. +
+ +
"GET /apache_pb.gif HTTP/1.0" + (\"%r\")
+ +
The request line from the client is given in double + quotes. The request line contains a great deal of useful + information. First, the method used by the client is + GET. Second, the client requested the resource + /apache_pb.gif, and third, the client used the + protocol HTTP/1.0. It is also possible to log + one or more parts of the request line independently. For + example, the format string "%m %U%q %H" will log + the method, path, query-string, and protocol, resulting in + exactly the same output as "%r".
+ +
200 (%>s)
+ +
This is the status code that the server sends back to the + client. This information is very valuable, because it reveals + whether the request resulted in a successful response (codes + beginning in 2), a redirection (codes beginning in 3), an + error caused by the client (codes beginning in 4), or an + error in the server (codes beginning in 5). The full list of + possible status codes can be found in the HTTP + specification (RFC2616 section 10).
+ +
2326 (%b)
+ +
The last entry indicates the size of the object returned + to the client, not including the response headers. If no + content was returned to the client, this value will be + "-". To log "0" for no content, use + %B instead.
+
+ + +

Combined Log Format

+ + +

Another commonly used format string is called the Combined + Log Format. It can be used as follows.

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\"" combined
+ CustomLog log/access_log combined +

+ +

This format is exactly the same as the Common Log Format, + with the addition of two more fields. Each of the additional + fields uses the percent-directive + %{header}i, where header can be + any HTTP request header. The access log under this format will + look like:

+ +

+ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET + /apache_pb.gif HTTP/1.0" 200 2326 + "http://www.example.com/start.html" "Mozilla/4.08 [en] + (Win98; I ;Nav)" +

+ +

The additional fields are:

+ +
+
"http://www.example.com/start.html" + (\"%{Referer}i\")
+ +
The "Referer" (sic) HTTP request header. This gives the + site that the client reports having been referred from. (This + should be the page that links to or includes + /apache_pb.gif).
+ +
"Mozilla/4.08 [en] (Win98; I ;Nav)" + (\"%{User-agent}i\")
+ +
The User-Agent HTTP request header. This is the + identifying information that the client browser reports about + itself.
+
+ + +

Multiple Access Logs

+ + +

Multiple access logs can be created simply by specifying + multiple CustomLog + directives in the configuration + file. For example, the following directives will create three + access logs. The first contains the basic CLF information, + while the second and third contain referer and browser + information. The last two CustomLog lines show how + to mimic the effects of the ReferLog and AgentLog directives.

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common
+ CustomLog logs/referer_log "%{Referer}i -> %U"
+ CustomLog logs/agent_log "%{User-agent}i" +

+ +

This example also shows that it is not necessary to define a + nickname with the LogFormat directive. Instead, + the log format can be specified directly in the CustomLog directive.

+ + +

Conditional Logs

+ + +

There are times when it is convenient to exclude certain + entries from the access logs based on characteristics of the + client request. This is easily accomplished with the help of environment variables. First, an + environment variable must be set to indicate that the request + meets certain conditions. This is usually accomplished with + SetEnvIf. Then the + env= clause of the CustomLog directive is used to + include or exclude requests where the environment variable is + set. Some examples:

+ +

+ # Mark requests from the loop-back interface
+ SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog
+ # Mark requests for the robots.txt file
+ SetEnvIf Request_URI "^/robots\.txt$" dontlog
+ # Log what remains
+ CustomLog logs/access_log common env=!dontlog +

+ +

As another example, consider logging requests from + english-speakers to one log file, and non-english speakers to a + different log file.

+ +

+ SetEnvIf Accept-Language "en" english
+ CustomLog logs/english_log common env=english
+ CustomLog logs/non_english_log common env=!english +

+ +

Although we have just shown that conditional logging is very + powerful and flexible, it is not the only way to control the + contents of the logs. Log files are more useful when they + contain a complete record of server activity. It is often + easier to simply post-process the log files to remove requests + that you do not want to consider.

+ +
top
+
+

Log Rotation

+ + +

On even a moderately busy server, the quantity of + information stored in the log files is very large. The access + log file typically grows 1 MB or more per 10,000 requests. It + will consequently be necessary to periodically rotate the log + files by moving or deleting the existing logs. This cannot be + done while the server is running, because Apache will continue + writing to the old log file as long as it holds the file open. + Instead, the server must be restarted after the log files are + moved or deleted so that it will open new log files.

+ +

By using a graceful restart, the server can be + instructed to open new log files without losing any existing or + pending connections from clients. However, in order to + accomplish this, the server must continue to write to the old + log files while it finishes serving old requests. It is + therefore necessary to wait for some time after the restart + before doing any processing on the log files. A typical + scenario that simply rotates the logs and compresses the old + logs to save space is:

+ +

+ mv access_log access_log.old
+ mv error_log error_log.old
+ apachectl graceful
+ sleep 600
+ gzip access_log.old error_log.old +

+ +

Another way to perform log rotation is using piped logs as discussed in the next + section.

+
top
+
+

Piped Logs

+ + +

Apache httpd is capable of writing error and access log + files through a pipe to another process, rather than directly + to a file. This capability dramatically increases the + flexibility of logging, without adding code to the main server. + In order to write logs to a pipe, simply replace the filename + with the pipe character "|", followed by the name + of the executable which should accept log entries on its + standard input. Apache will start the piped-log process when + the server starts, and will restart it if it crashes while the + server is running. (This last feature is why we can refer to + this technique as "reliable piped logging".)

+ +

Piped log processes are spawned by the parent Apache httpd + process, and inherit the userid of that process. This means + that piped log programs usually run as root. It is therefore + very important to keep the programs simple and secure.

+ +

One important use of piped logs is to allow log rotation + without having to restart the server. The Apache HTTP Server + includes a simple program called rotatelogs + for this purpose. For example, to rotate the logs every 24 hours, you + can use:

+ +

+ CustomLog "|/usr/local/apache/bin/rotatelogs + /var/log/access_log 86400" common +

+ +

Notice that quotes are used to enclose the entire command + that will be called for the pipe. Although these examples are + for the access log, the same technique can be used for the + error log.

+ +

A similar but much more flexible log rotation program + called cronolog + is available at an external site.

+ +

As with conditional logging, piped logs are a very powerful + tool, but they should not be used where a simpler solution like + off-line post-processing is available.

+
top
+
+

Virtual Hosts

+ + +

When running a server with many virtual + hosts, there are several options for dealing with log + files. First, it is possible to use logs exactly as in a + single-host server. Simply by placing the logging directives + outside the <VirtualHost> sections in the + main server context, it is possible to log all requests in the + same access log and error log. This technique does not allow + for easy collection of statistics on individual virtual + hosts.

+ +

If CustomLog + or ErrorLog + directives are placed inside a + <VirtualHost> + section, all requests or errors for that virtual host will be + logged only to the specified file. Any virtual host which does + not have logging directives will still have its requests sent + to the main server logs. This technique is very useful for a + small number of virtual hosts, but if the number of hosts is + very large, it can be complicated to manage. In addition, it + can often create problems with insufficient file + descriptors.

+ +

For the access log, there is a very good compromise. By + adding information on the virtual host to the log format + string, it is possible to log all hosts to the same log, and + later split the log into individual files. For example, + consider the following directives.

+ +

+ LogFormat "%v %l %u %t \"%r\" %>s %b" + comonvhost
+ CustomLog logs/access_log comonvhost +

+ +

The %v is used to log the name of the virtual + host that is serving the request. Then a program like split-logfile can be used to + post-process the access log in order to split it into one file + per virtual host.

+
top
+
+

Other Log Files

+ + +
Related ModulesRelated Directives
+ +

Logging actual bytes sent and recieved

+ + +

mod_logio adds in two additional + LogFormat fields + (%I and %O) that log the actual number of bytes received and sent + on the network.

+ + +

Forensic Logging

+ + +

mod_log_forensic provides for forensic logging of + client requests. Logging is done before and after processing a + request, so the forensic log contains two log lines for each + request. The forensic logger is very strict with no customizations. + It can be an invaluable debugging and security tool.

+ + +

PID File

+ + +

On startup, Apache httpd saves the process id of the parent + httpd process to the file logs/httpd.pid. This + filename can be changed with the PidFile directive. The + process-id is for use by the administrator in restarting and + terminating the daemon by sending signals to the parent + process; on Windows, use the -k command line option instead. + For more information see the Stopping + and Restarting page.

+ + +

Script Log

+ + +

In order to aid in debugging, the + ScriptLog directive + allows you to record the input to and output from CGI scripts. + This should only be used in testing - not for live servers. + More information is available in the mod_cgi documentation.

+ + +

Rewrite Log

+ + +

When using the powerful and complex features of mod_rewrite, it is almost + always necessary to use the RewriteLog to help + in debugging. This log file produces a detailed analysis of how + the rewriting engine transforms requests. The level of detail + is controlled by the RewriteLogLevel directive.

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/logs.html.ja.euc-jp b/docs/manual/logs.html.ja.euc-jp new file mode 100644 index 00000000..3090fea8 --- /dev/null +++ b/docs/manual/logs.html.ja.euc-jp @@ -0,0 +1,571 @@ + + + +¥í¥°¥Õ¥¡¥¤¥ë - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥í¥°¥Õ¥¡¥¤¥ë

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¸ú²ÌŪ¤Ë´ÉÍý¤¹¤ë¤¿¤á¤Ë¤Ï¡¢¥µ¡¼¥Ð¤Î³èÆ°¤ä¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¡¢ + º£È¯À¸¤·¤Æ¤¤¤ë¤«¤â¤·¤ì¤Ê¤¤ÌäÂê¤Ë´Ø¤¹¤ë¥Õ¥£¡¼¥É¥Ð¥Ã¥¯¤òÆÀ¤ë¤³¤È¤¬É¬ÍפǤ¹¡£ + Apache HTTP ¥µ¡¼¥Ð¤Ë¤ÏÈó¾ï¤ËÊñ³çŪ¤Ç½ÀÆð¤Ê¥í¥®¥ó¥°µ¡Ç½¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Îʸ½ñ¤Ï¥í¥®¥ó¥°µ¡Ç½¤ÎÀßÄê¤Î»ÅÊý¤È¡¢¥í¥°¤Ë²¿¤¬½ñ¤«¤ì¤Æ¤¤¤ë¤«¤ò + Íý²ò¤¹¤ë¤¿¤á¤ÎÊýË¡¤òÀâÌÀ¤·¤Þ¤¹¡£

+
+ +
top
+
+

+ ¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤¹¤ë·Ù¹ð

+ +

Apache ¤¬¥í¥°¥Õ¥¡¥¤¥ë¤ò½ñ¤¤¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ë½ñ¤­¹þ¤á¤ë¿Í¤Ï¡¢ + ¤Û¤Ü³Î¼Â¤Ë¥µ¡¼¥Ð¤¬µ¯Æ°¤µ¤ì¤¿ uid ¤Ø¤Î¥¢¥¯¥»¥¹¤ò¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤½¤·¤Æ¡¢¤½¤ì¤ÏÄ̾ï¤Ï root ¥æ¡¼¥¶¤Ç¤¹¡£ + ¤Á¤ã¤ó¤È·ë²Ì¤ò¹Í¤¨¤ë¤³¤È¤Ê¤¯¡¢¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î + ½ñ¤­¹þ¤ß¸¢¸Â¤òÍ¿¤¨¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£¾Ü¤·¤¯¤Ï + ¥»¥­¥å¥ê¥Æ¥£¤Î¤³¤Ä¤Îʸ½ñ¤ò + Æɤó¤Ç¤¯¤À¤µ¤¤¡£

+ +

²Ã¤¨¤Æ¡¢¥í¥°¥Õ¥¡¥¤¥ë¤Ë¤Ï¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¾ðÊ󤬤½¤Î¤Þ¤Þ¡¢ + ¥¨¥¹¥±¡¼¥×¤µ¤ì¤ë¤³¤È¤Ê¤¯½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢°­°Õ¤Î¤¢¤ë + ¥¯¥é¥¤¥¢¥ó¥È¤¬¥í¥°¥Õ¥¡¥¤¥ë¤ËÀ©¸æʸ»ú¤òÁÞÆþ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + À¸¤Î¥í¥°¤ò°·¤¦¤È¤­¤ÏÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

¥¨¥é¡¼¥í¥°

+ +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

ErrorLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê + ̾Á°¤È¾ì½ê¤¬·è¤Þ¤ë¥µ¡¼¥Ð¤Î¥¨¥é¡¼¥í¥°¤Ï¡¢°ìÈÖ½ÅÍ×¤Ê¥í¥°¥Õ¥¡¥¤¥ë¤Ç¤¹¡£ + Apache ¤Î¿ÇÃǾðÊó¤Ï¤³¤³¤ËÁ÷¤é¤ì¡¢¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤·¤Æ¤¤¤ë¤È¤­¤Ë + ȯÀ¸¤·¤¿¥¨¥é¡¼¤Ï¤¹¤Ù¤Æ¤³¤³¤Ëµ­Ï¿¤µ¤ì¤Þ¤¹¡£¥µ¡¼¥Ð¤òµ¯Æ°¤·¤¿¤È¤­¤ä¡¢ + ¥µ¡¼¥Ð¤ÎÆ°ºî¤ËÌäÂ꤬µ¯¤³¤Ã¤¿¤È¤­¤Ï¡¢°ìÈֺǽé¤ËÄ´¤Ù¤ë¤Ù¤­ + ¤È¤³¤í¤Ç¤¹¡£´Ö°ã¤¤¤Î¾ÜºÙ¤ä½¤ÀµÊýË¡¤¬¤½¤³¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¤³¤È¤¬ + ¤è¤¯¤¢¤ê¤Þ¤¹¡£

+ +

¥¨¥é¡¼¥í¥°¤ÏÉáÄ̤ϥե¡¥¤¥ë¤Ë½ñ¤«¤ì¤Þ¤¹ (Ä̾ï unix ¥·¥¹¥Æ¥à¤Ç¤Ï + error_log¡¢Windows ¤È OS/2 ¤Ç¤Ï error.log)¡£ + Unix ¥·¥¹¥Æ¥à¤Ç¤Ï¥¨¥é¡¼¤ò syslog ¤ä + ¥Ñ¥¤¥×¤Ç¥×¥í¥°¥é¥à¤ËÁ÷¤ë ¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¥¨¥é¡¼¥í¥°¤Î½ñ¼°¤ÏÈæ³ÓŪ¼«Í³Å٤ι⤤¤â¤Î¤Ç¡¢ÀâÌÀŪ¤Ë½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤¿¤À¤·¡¢¤¤¤¯¤Ä¤«¤Î¾ðÊó¤Ï¤Û¤È¤ó¤É¤Î¥¨¥é¡¼¥í¥°¤Î¥¨¥ó¥È¥ê¤Ë¤¢¤ê¤Þ¤¹¡£ + Î㤨¤Ð¡¢ÂåɽŪ¤Ê¤â¤Î¤Ë¼¡¤Î¤è¤¦¤Ê¥á¥Ã¥»¡¼¥¸¤¬¤¢¤ê¤Þ¤¹¡£

+ +

+ [Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1] + client denied by server configuration: + /export/home/live/ap/htdocs/test +

+ +

¥í¥°¥¨¥ó¥È¥ê¤ÎºÇ½é¤Î¹àÌܤϥá¥Ã¥»¡¼¥¸¤ÎÆüÉդȻþ¹ï¤Ç¤¹¡£ + Æó¤Ä¤á¤Î¹àÌܤÏÊó¹ð¤µ¤ì¤Æ¤¤¤ë¥¨¥é¡¼¤Î½ÅÍ×Å٤Ǥ¹¡£ + LogLevel ¤Ç½ÅÍ×Å٤Υì¥Ù¥ë¤ò + À©¸Â¤¹¤ë¤³¤È¤Ë¤è¤ê¥¨¥é¡¼¥í¥°¤ËÁ÷¤é¤ì¤ë¥¨¥é¡¼¤Î¼ïÎà¤òÀ©¸æ¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£»°¤ÄÌܤιàÌܤϥ¨¥é¡¼¤òȯÀ¸¤µ¤»¤¿¥¯¥é¥¤¥¢¥ó¥È¤Î IP ¥¢¥É¥ì¥¹ + ¤Ç¤¹¡£»Ä¤ê¤Ï¥á¥Ã¥»¡¼¥¸¤Ç¡¢¤³¤Î¾ì¹ç¤Ï¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤Î¥¢¥¯¥»¥¹¤ò + µñÈݤ¹¤ë¤è¤¦¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¡¢¤È¤¤¤¦¤³¤È¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤Ï¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿Ê¸½ñ¤Î (¥¦¥§¥Ö¤Î¥Ñ¥¹¤Ç¤Ï¤Ê¤¯) ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î + ¥Ñ¥¹¤òÊó¹ð¤·¤Þ¤¹¡£

+ +

Èó¾ï¤Ë¹­ÈϰϤΥá¥Ã¥»¡¼¥¸¤¬¥¨¥é¡¼¥í¥°¤Ë¸½¤ì¤Þ¤¹¡£¤¿¤¤¤Æ¤¤¤Î¤â¤Î¤Ï + ¾å¤ÎÎã¤Î¤è¤¦¤Ê´¶¤¸¤Ç¤¹¡£¥¨¥é¡¼¥í¥°¤Ë¤Ï CGI ¥¹¥¯¥ê¥×¥È¤Î¥Ç¥Ð¥Ã¥° + ½ÐÎϤâ½ñ¤«¤ì¤Þ¤¹¡£CGI ¥¹¥¯¥ê¥×¥È¤¬ stderr ¤Ë½ñ¤¤¤¿ + ¤¹¤Ù¤Æ¤Î¾ðÊó¤ÏľÀÜ¥¨¥é¡¼¥í¥°¤Ë¥³¥Ô¡¼¤µ¤ì¤Þ¤¹¡£

+ +

¾ðÊó¤òÄɲä·¤¿¤êºï½ü¤·¤¿¤ê¤·¤Æ¥¨¥é¡¼¥í¥°¤ò¥«¥¹¥¿¥Þ¥¤¥º¤¹¤ë¤³¤È¤Ï + ¤Ç¤­¤Þ¤»¤ó¡£¤·¤«¤·¡¢¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë¥¨¥é¡¼¥í¥°¤Î¥¨¥ó¥È¥ê¤Ï¡¢ + Âбþ¤¹¤ë¥¨¥ó¥È¥ê¤¬¥¢¥¯¥»¥¹¥í¥°¤Ë¤¢¤ê¤Þ¤¹¡£ + Î㤨¤Ð¡¢¾å¤ÎÎã¤Î¥¨¥ó¥È¥ê¤Ï¥¢¥¯¥»¥¹¥í¥°¤Î¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É 403 ¤Î + ¥¨¥ó¥È¥ê¤ËÂбþ¤·¤Þ¤¹¡£¥¢¥¯¥»¥¹¥í¥°¤Ï¥«¥¹¥¿¥Þ¥¤¥º²Äǽ¤Ç¤¹¤Î¤Ç¡¢ + ¤½¤Á¤é¤ò»È¤¦¤³¤È¤Ë¤è¤ê¥¨¥é¡¼¤Î¾õ¶·¤Ë´Ø¤¹¤ë¾ðÊó¤ò¤è¤ê¿¤¯ + ¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¥Æ¥¹¥È¤ÎºÇÃæ¤Ï¡¢ÌäÂ꤬ȯÀ¸¤·¤Æ¤¤¤ë¤«¤É¤¦¤«¤ò¸«¤ë¤¿¤á¤Ë¡¢ + ¾ï¤Ë¥¨¥é¡¼¥í¥°¤ò´Æ»ë¤¹¤ë¤Î¤¬Ìò¤ËΩ¤Ä¾ì¹ç¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£ + Unix ¥·¥¹¥Æ¥à¤Ç¤Ï¡¢¼¡¤Î¤â¤Î¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ tail -f error_log +

+
top
+
+

¥¢¥¯¥»¥¹¥í¥°

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

¥µ¡¼¥Ð¥¢¥¯¥»¥¹¥í¥°¤Ï¥µ¡¼¥Ð¤¬½èÍý¤ò¤·¤¿¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤ò + µ­Ï¿¤·¤Þ¤¹¡£¥¢¥¯¥»¥¹¥í¥°¤Î¾ì½ê¤ÈÆâÍÆ¤Ï CustomLog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê·è¤Þ¤ê¤Þ¤¹¡£¥í¥°¤ÎÆâÍƤÎÁªÂò¤ò´Ê·é¤Ë¤¹¤ë¤¿¤á¤Ë + LogFormat + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤Î¥»¥¯¥·¥ç¥ó¤Ï¥¢¥¯¥»¥¹¥í¥°¤Ë + ¾ðÊó¤òµ­Ï¿¤¹¤ë¤¿¤á¤Î¥µ¡¼¥Ð¤ÎÀßÄêÊýË¡¤òÀâÌÀ¤·¤Þ¤¹¡£

+ +

¤â¤Á¤í¤ó¡¢¥¢¥¯¥»¥¹¥í¥°¤Ë¾ðÊó¤òÃßÀѤ¹¤ë¤³¤È¤Ï¥í¥°´ÉÍý¤Î + »Ï¤Þ¤ê¤Ë²á¤®¤Þ¤»¤ó¡£¼¡¤ÎÃʳ¬¤ÏÍ­ÍѤÊÅý·×¤ò¼è¤ë¤¿¤á¤Ë¤³¤Î¾ðÊó¤ò + ²òÀϤ¹¤ë¤³¤È¤Ç¤¹¡£°ìÈÌŪ¤Ê¥í¥°²òÀϤϤ³¤Îʸ½ñ¤ÎÈϰϳ°¤Ç¡¢ + ¥¦¥§¥Ö¥µ¡¼¥Ð¼«¿È¤Î»Å»ö¤È¤¤¤¦¤ï¤±¤Ç¤â¤¢¤ê¤Þ¤»¤ó¡£¤³¤ÎÏä䡢 + ¥í¥°²òÀϤò¹Ô¤Ê¤¦¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¾ðÊó¤òÆÀ¤ë¤Ë¤Ï¡¢ + Open Directory ¤ä + Yahoo ¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£

+ +

¤¤¤í¤ó¤Ê¥Ð¡¼¥¸¥ç¥ó¤Î Apache httpd ¤¬ mod_log_config, + mod_log_agent, TransferLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤¤¤Ã¤¿¡¢ + ¾¤Î¥â¥¸¥å¡¼¥ë¤ä¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¥¢¥¯¥»¥¹¤Î¥í¥®¥ó¥°¤ò + À©¸æ¤·¤Æ¤­¤Þ¤·¤¿¡£º£¤Ç¤Ï¡¢CustomLog ¤¬¤¹¤Ù¤Æ¤Î¸Å¤¤ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Îµ¡Ç½¤ò´Þ¤à¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

¥¢¥¯¥»¥¹¥í¥°¤Î½ñ¼°¤ÏÈó¾ï¤Ë½ÀÆð¤ÊÀßÄ꤬²Äǽ¤Ç¤¹¡£ + ½ñ¼°¤Ï C ¤Î printf(1) ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤ËÈó¾ï¤Ë»÷¤¿ + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó + ¤Ë¤è¤ê»ØÄꤵ¤ì¤Þ¤¹¡£¤¤¤¯¤Ä¤«¼¡¤ÎÀá¤ÇÎã¤ò¼¨¤·¤Þ¤¹¡£ + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ë»ÈÍѤǤ­¤ëÆâÍƤΰìÍ÷¤Ï mod_log_config ¤Îʸ½ñ + ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£

+ +

Common Log Format

+ + +

¥¢¥¯¥»¥¹¥í¥°¤Î¤è¤¯¤¢¤ëÀßÄê¤Ë°Ê²¼¤Î¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common +

+ +

¤³¤ì¤Ï¡¢¥Ë¥Ã¥¯¥Í¡¼¥à common ¤òÄêµÁ¤·¡¢ + ¥í¥°¤Î¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Î°ì¤Ä¤È´ØÏ¢ÉÕ¤±¤Þ¤¹¡£¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ï + ¥Ñ¡¼¥»¥ó¥È¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤«¤é¤Ê¤ê¡¢¤½¤ì¤¾¤ì¤Î¥Ñ¡¼¥»¥ó¥È¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥µ¡¼¥Ð¤Ë¤É¤Î¾ðÊó¤ò¥í¥®¥ó¥°¤¹¤ë¤«¤ò»Ø¼¨¤·¤Þ¤¹¡£¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ë + ʸ»ú¤ò¤½¤Î¤Þ¤ÞÆþ¤ì¤ë¤³¤È¤â¤Ç¤­¡¢¤½¤ì¤é¤Ï¥í¥°¤Î½ÐÎϤËľÀÜ¥³¥Ô¡¼¤µ¤ì¤Þ¤¹¡£ + ¤½¤³¤Ë°úÍÑʸ»ú (") ¤ò½ñ¤¯¤È¤­¤Ï¡¢ + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤ÎºÇ¸å¤È¤·¤Æ²ò¼á + ¤µ¤ì¤ë¤³¤È¤òËɤ°¤¿¤á¤Ë¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Ç¥¨¥¹¥±¡¼¥×¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ë¤Ï²þ¹ÔÍѤΠ"\n"¡¢¥¿¥ÖÍѤΠ+ "\t" ¤È¤¤¤¦ÆÃÊ̤ÊÀ©¸æʸ»ú¤â´Þ¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

CustomLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ´û¤ËÄêµÁ¤µ¤ì¤¿ + ¥Ë¥Ã¥¯¥Í¡¼¥à ¤ò»È¤Ã¤Æ¿·¤·¤¤¥í¥°¥Õ¥¡¥¤¥ë¤òÀßÄꤷ¤Þ¤¹¡£ + ¥¢¥¯¥»¥¹¥í¥°¤Î¥Õ¥¡¥¤¥ë̾¤Ï¥¹¥é¥Ã¥·¥å¤Ç»Ï¤Þ¤é¤Ê¤¤¸Â¤ê¡¢ + ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ + °·¤ï¤ì¤Þ¤¹¡£

+ +

¾å¤ÎÀßÄê¤Ï Common Log Format (CLF) ¤È¸Æ¤Ð¤ì¤ë·Á¼°¤Ç + ¥í¥°¥¨¥ó¥È¥ê¤ò½ñ¤­¤Þ¤¹¡£¤³¤Îɸ½à¤Î·Á¼°¤Ï°Û¤Ê¤ë¥¦¥§¥Ö¥µ¡¼¥Ð¤Î¿¤¯¤¬ + À¸À®¤¹¤ë¤³¤È¤¬¤Ç¤­¡¢Â¿¤¯¤Î¥í¥°²òÀÏ¥×¥í¥°¥é¥à¤¬Æɤߤ³¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + CLF ¤Ë¤è¤êÀ¸À®¤µ¤ì¤¿¥í¥°¥Õ¥¡¥¤¥ë¤Î¥¨¥ó¥È¥ê¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹:

+ +

+ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET + /apache_pb.gif HTTP/1.0" 200 2326 +

+ +

¤³¤Î¥í¥°¥¨¥ó¥È¥ê¤Î¤½¤ì¤¾¤ì¤ÎÉôʬ¤Î°ÕÌ£¤Ï°Ê²¼¤ÇÀâÌÀ¤·¤Þ¤¹¡£

+ +
+
127.0.0.1 (%h)
+ +
¤³¤ì¤Ï¥µ¡¼¥Ð¤Ø¥ê¥¯¥¨¥¹¥È¤ò¤·¤¿¥¯¥é¥¤¥¢¥ó¥È (¥ê¥â¡¼¥È¥Û¥¹¥È) + ¤Î IP ¥¢¥É¥ì¥¹¤Ç¤¹¡£HostnameLookups ¤¬ + On ¤Î¾ì¹ç¤Ï¡¢¥µ¡¼¥Ð¤Ï¥Û¥¹¥È̾¤òÄ´¤Ù¤Æ¡¢ + IP ¥¢¥É¥ì¥¹¤¬½ñ¤«¤ì¤Æ¤¤¤ë¤È¤³¤í¤Ëµ­Ï¿¤·¤Þ¤¹¡£¤·¤«¤·¡¢¤³¤ÎÀßÄê¤Ï + ¥µ¡¼¥Ð¤ò¤«¤Ê¤êÃÙ¤¯¤¹¤ë¤Î¤Ç¡¢¤¢¤Þ¤ê¤ª´«¤á¤Ç¤­¤Þ¤»¤ó¡£ + ¤½¤¦¤Ç¤Ï¤Ê¤¯¡¢logresolve ¤Î + ¤è¤¦¤Ê¥í¥°¤Î¸å½èÍý¤ò¹Ô¤Ê¤¦¥×¥í¥°¥é¥à¤Ç¥Û¥¹¥È̾¤òÄ´¤Ù¤ë¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£ + ¤³¤³¤ËÊó¹ð¤µ¤ì¤ë IP ¥¢¥É¥ì¥¹¤Ïɬ¤º¤·¤â¥æ¡¼¥¶¤¬»È¤Ã¤Æ¤¤¤ë¥Þ¥·¥ó¤Î + ¤â¤Î¤Ç¤¢¤ë¤È¤Ï¸Â¤ê¤Þ¤»¤ó¡£¥æ¡¼¥¶¤È¥µ¡¼¥Ð¤Î´Ö¤Ë¥×¥í¥­¥·¥µ¡¼¥Ð¤¬ + ¤¢¤ì¤Ð¡¢¤³¤Î¥¢¥É¥ì¥¹¤Ï¸µ¤Î¥Þ¥·¥ó¤Î¤â¤Î¤Ç¤Ï¤Ê¤¯¡¢¥×¥í¥­¥·¤Î + ¥¢¥É¥ì¥¹¤Ë¤Ê¤ê¤Þ¤¹¡£
+ +
- (%l)
+ +
½ÐÎÏÃæ¤Î¡Ö¥Ï¥¤¥Õ¥ó¡×¤ÏÍ׵ᤵ¤ì¤¿¾ðÊ󤬼ê¤ËÆþ¤é¤Ê¤«¤Ã¤¿¤È¤¤¤¦¤³¤È¤ò + °ÕÌ£¤·¤Þ¤¹¡£¤³¤Î¾ì¹ç¡¢¼èÆÀ¤Ç¤­¤Ê¤«¤Ã¤¿¾ðÊó¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Î¥Þ¥·¥ó¤Î + identd ¤Ë¤è¤ê·è¤Þ¤ë RFC 1413 ¤Î¥¯¥é¥¤¥¢¥ó¥È¤Î + ¥¢¥¤¥Ç¥ó¥Æ¥£¥Æ¥£¤Ç¤¹¡£¤³¤Î¾ðÊó¤Ï¤¢¤Þ¤ê¿®ÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤º¡¢ + ¤·¤Ã¤«¤ê¤È´ÉÍý¤µ¤ì¤¿ÆâÉô¥Í¥Ã¥È¥ï¡¼¥¯¤ò½ü¤¤¤Æ¤Ï»È¤¦¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + Apache ¤Ï IdentityCheck ¤¬ + On ¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢¤³¤Î¾ðÊó¤òÆÀ¤è¤¦¤È¤¹¤é¤·¤Þ¤»¤ó¡£
+ +
frank (%u)
+ +
¤³¤ì¤Ï HTTP ǧ¾Ú¤Ë¤è¤ë¡¢¥É¥­¥å¥á¥ó¥È¤ò¥ê¥¯¥¨¥¹¥È¤·¤¿¿Í¤Î + ¥æ¡¼¥¶ ID ¤Ç¤¹¡£CGI ¥¹¥¯¥ê¥×¥È¤Ë¤ÏÄ̾ïƱ¤¸Ãͤ¬ REMOTE_USER + ´Ä¶­ÊÑ¿ô¤È¤·¤ÆÍ¿¤¨¤é¤ì¤Þ¤¹¡£¥ê¥¯¥¨¥¹¥È¤Î¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É + (°Ê²¼¤ò»²¾È) ¤¬ 401 ¤Ç¤¢¤Ã¤¿¾ì¹ç¤Ï¡¢¥æ¡¼¥¶¤Ïǧ¾Ú¤Ë¼ºÇÔ¤·¤Æ¤¤¤ë¤Î¤Ç¡¢ + ¤³¤ÎÃͤϿ®ÍѤǤ­¤Þ¤»¤ó¡£¥É¥­¥å¥á¥ó¥È¤¬¥Ñ¥¹¥ï¡¼¥É¤ÇÊݸ¤ì¤Æ¤¤¤Ê¤¤ + ¾ì¹ç¤Ï¡¢¤³¤Î¥¨¥ó¥È¥ê¤ÏÁ°¤Î¤â¤Î¤ÈƱ¤¸¤è¤¦¤Ë "-" ¤Ë + ¤Ê¤ê¤Þ¤¹¡£
+ +
[10/Oct/2000:13:55:36 -0700] + (%t)
+ +
+ ¥µ¡¼¥Ð¤¬¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤Ã¤¿»þ¹ï¤Ç¤¹¡£½ñ¼°¤Ï: + +

+ [day/month/year:hour:minute:second zone]
+ day = 2*digit
+ month = 3*letter
+ year = 4*digit
+ hour = 2*digit
+ minute = 2*digit
+ second = 2*digit
+ zone = (`+' | `-') 4*digit +

+ ¥í¥°¤Î¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ë %{format}t ¤ò + »ØÄꤹ¤ë¤³¤È¤Ç¡¢Ê̤ηÁ¼°¤Ç»þ¹ï¤òɽ¼¨¤µ¤»¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¤È¤­¡¢format ¤Ï C ¤Îɸ½à¥é¥¤¥Ö¥é¥ê¤Î + strftime(3) ¤Î·Á¼°¤Ë¤Ê¤ê¤Þ¤¹¡£ +
+ +
"GET /apache_pb.gif HTTP/1.0" + (\"%r\")
+ +
¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤¬Æó½Å°úÍÑÉä¤ÎÃæ¤Ë¼¨¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¤Ë¤Ï¿¤¯¤ÎÍ­ÍѤʾðÊ󤬤¢¤ê¤Þ¤¹¡£¤Þ¤º¡¢¤³¤Î¾ì¹ç¥¯¥é¥¤¥¢¥ó¥È¤¬ + »È¤Ã¤¿¥á¥½¥Ã¥É¤Ï GET ¤Ç¤¹¡£¼¡¤Ë¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï + ¥ê¥½¡¼¥¹ /apache_pb.gif ¤òÍ׵ᤷ¤Þ¤·¤¿¡£¤½¤·¤Æ¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤Ï¥×¥í¥È¥³¥ë HTTP/1.0 ¤ò»ÈÍѤ·¤Þ¤·¤¿¡£ + ¥ê¥¯¥¨¥¹¥È¤Î³ÆÉôʬ¤òÆÈΩ¤Ë¥í¥°¼ý½¸¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¡¢ + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó "%m %U%q %H" ¤Ï + ¥á¥½¥Ã¥É¡¢¥Ñ¥¹¡¢¥¯¥¨¥êʸ»úÎó¡¢¥×¥í¥È¥³¥ë¤ò¥í¥°¼ý½¸¤·¡¢ + ·ë¶É "%r" ¤È¤Þ¤Ã¤¿¤¯Æ±¤¸½ÐÎϤˤʤê¤Þ¤¹¡£
+ +
200 (%>s)
+ +
¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤êÊÖ¤¹¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤Ç¤¹¡£ + ¤³¤Î¾ðÊó¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤¬À®¸ù±þÅú (2 ¤Ç»Ï¤Þ¤ë¥³¡¼¥É) ¤Ç¤¢¤Ã¤¿¤«¡¢ + ¥ê¥À¥¤¥ì¥¯¥·¥ç¥ó (3 ¤Ç»Ï¤Þ¤ë¥³¡¼¥É) ¤Ç¤¢¤Ã¤¿¤«¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ë¤è¤ë + ¥¨¥é¡¼ (4 ¤Ç»Ï¤Þ¤ë¥³¡¼¥É) ¤Ç¤¢¤Ã¤¿¤«¡¢¥µ¡¼¥Ð¤Î¥¨¥é¡¼ (5 ¤Ç»Ï¤Þ¤ë¥³¡¼¥É) + ¤Ç¤¢¤Ã¤¿¤«¡¢¤òɽ¤¹¤Î¤Ç¡¢Èó¾ï¤ËÂçÀڤǤ¹¡£¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤Î + ´°Á´¤Ê¥ê¥¹¥È¤Ï HTTP + µ¬³Ê (RFC2616 Âè 10 Àá) ¤Ë¤¢¤ê¤Þ¤¹¡£
+ +
2326 (%b)
+ +
¤³¤ÎºÇ¸å¤Î¥¨¥ó¥È¥ê¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¿®¤µ¤ì¤¿¥ª¥Ö¥¸¥§¥¯¥È¤Î¡¢ + ±þÅú¥Ø¥Ã¥À¤ò½ü¤¤¤¿¥µ¥¤¥º¤òɽ¤·¤Þ¤¹¡£¥³¥ó¥Æ¥ó¥È¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤é¤ì¤Ê¤«¤Ã¤¿ + ¾ì¹ç¤Ï¡¢¤³¤ÎÃÍ¤Ï "-" ¤Ë¤Ê¤ê¤Þ¤¹¡£¥³¥ó¥Æ¥ó¥È¤¬Ìµ¤¤¾ì¹ç¤Ë + "0" ¤ò¥í¥°¼ý½¸¤¹¤ë¤Ë¤Ï¡¢%b ¤Ç¤Ï¤Ê¤¯ + %B ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
+ +
+ + +

Combined Log Format

+ + +

¤â¤¦°ì¤Ä¤Î¤è¤¯»È¤ï¤ì¤ë½ñ¼°¤Ï Combined Log Format ¤È¸Æ¤Ð¤ì¤Æ¤¤¤Þ¤¹¡£ + °Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\"" combined
+ CustomLog log/access_log combined +

+ +

¤³¤Î½ñ¼°¤ÎºÇ½é¤ÎÊý¤Ï Common Log Format ¤È¤Þ¤Ã¤¿¤¯Æ±¤¸¤Ç¡¢ºÇ¸å¤Ë + Æó¤ÄÄɲäΥ¨¥ó¥È¥ê¤¬¤¢¤ê¤Þ¤¹¡£ÄɲäΥ¨¥ó¥È¥ê¤Ï¥Ñ¡¼¥»¥ó¥È¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + %{header}i ¤ò»È¤Ã¤Æ¤¤¤Þ¤¹¡£¤³¤³¤Ç + header ¤Ï HTTP ¤Î¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Î¤É¤ì¤«¤Ç¤¹¡£¤³¤Î½ñ¼°¤Ë¤è¤ë + ¥¢¥¯¥»¥¹¥í¥°¤Ï°Ê²¼¤Î¤è¤¦¤Ê´¶¤¸¤Ë¤Ê¤ê¤Þ¤¹:

+ +

+ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET + /apache_pb.gif HTTP/1.0" 200 2326 + "http://www.example.com/start.html" "Mozilla/4.08 [en] + (Win98; I ;Nav)" +

+ +

ÄɲäΥ¨¥ó¥È¥ê¤Ï:

+ +
+
"http://www.example.com/start.html" + (\"%{Referer}i\")
+ +
"Referer" (°Õ¿ÞŪ¤ÊÄÖ¤ê´Ö°ã¤¤) HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Ç¤¹¡£ + ¤³¤ì¤Ï¥¯¥é¥¤¥¢¥ó¥È¤¬Êó¹ð¤·¤Æ¤¯¤ë»²¾È¸µ¤Î¥µ¥¤¥È¤òɽ¤·¤Þ¤¹¡£ + (¤³¤Î¾ì¹ç¤Ï¡¢/apache_pb.gif ¤Ë¥ê¥ó¥¯¤·¤Æ¤¤¤ë¤«¡¢ + ¤½¤ì¤ò´Þ¤ó¤Ç¤¤¤ë¥Ú¡¼¥¸¤Ç¤¹)¡£
+ +
"Mozilla/4.08 [en] (Win98; I ;Nav)" + (\"%{User-agent}i\")
+ +
User-Agent HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Ç¤¹¡£¤³¤ì¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Î¥Ö¥é¥¦¥¶¤¬ + ¼«Ê¬¼«¿È¤Î¤³¤È¤òÊó¹ð¤·¤Æ¤¯¤ë¾ðÊó¤Ç¤¹¡£
+
+ + +

Ê£¿ô¤Î¥¢¥¯¥»¥¹¥í¥°

+ + +

Ê£¿ô¤Î¥¢¥¯¥»¥¹¥í¥°¤Ïñ¤ËÀßÄê¥Õ¥¡¥¤¥ë¤ËÊ£¿ô¤Î CustomLog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¯¤³¤È¤ÇºîÀ®¤µ¤ì¤Þ¤¹¡£Î㤨¤Ð¡¢°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + »°¤Ä¤Î¥¢¥¯¥»¥¹¥í¥°¤òºî¤ê¤Þ¤¹¡£ºÇ½é¤Î¤â¤Î¤Ï´ðËÜŪ¤Ê CLF ¤Î¾ðÊó¤Ç¡¢ + Æó¤ÄÌܤȻ°¤ÄÌÜ¤Ï referer ¤È¥Ö¥é¥¦¥¶¤Î¾ðÊó¤Ç¤¹¡£ºÇ¸åÆó¤Ä¤Î + CustomLog ¤Ï + ReferLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + AgentLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¸ú²Ì¤ò¤Þ¤Í¤ëÊýË¡¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common
+ CustomLog logs/referer_log "%{Referer}i -> %U"
+ CustomLog logs/agent_log "%{User-agent}i" +

+ +

¤³¤ÎÎã¤Ï LogFormat ¤Ç + ¥Ë¥Ã¥¯¥Í¡¼¥à¤òÄêµÁ¤¹¤ëɬÍפ¬¤Ê¤¤¡¢ + ¤È¤¤¤¦¤³¤È¤â¼¨¤·¤Æ¤¤¤Þ¤¹¡£¥Ë¥Ã¥¯¥Í¡¼¥à¤ÎÂå¤ï¤ê¤Ë¡¢ + CustomLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë + ľÀÜ¥í¥°¤Î½ñ¼°¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ + +

¾ò·ïÉÕ¤­¥í¥°

+ + +

¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ÎÆÃħ¤Ë´ð¤Å¤¤¤Æ¥¢¥¯¥»¥¹¥í¥°¤Ë¥¨¥ó¥È¥ê¤Î + °ìÉô¤ò¥í¥®¥ó¥°¤·¤Ê¤¤Êý¤¬ÊØÍø¤Ê¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤Ï ´Ä¶­ÊÑ¿ô ¤ÎÊä½õ¤Ë¤è¤ê´Êñ¤Ë¼Â¸½¤Ç¤­¤Þ¤¹¡£¤Þ¤º¡¢ + ¥ê¥¯¥¨¥¹¥È¤¬²¿¤é¤«¤Î¾ò·ï¤Ë¹ç¤¦¤È¤¤¤¦¤³¤È¤òɽ¤¹¤¿¤á¤Ë´Ä¶­ÊÑ¿ô¤¬ + ÀßÄꤵ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤ÏÄ̾ï¤Ï SetEnvIf ¤Ë¤è¤ê + ¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£¤½¤·¤Æ¡¢CustomLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + env= Àá¤ò»È¤Ã¤Æ´Ä¶­ÊÑ¿ô¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¥ê¥¯¥¨¥¹¥È¤ò + ´Þ¤á¤¿¤êÇÓ½ü¤·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤¤¤¯¤Ä¤«Îã¤òµó¤²¤Þ¤¹:

+ +

+ # Mark requests from the loop-back interface
+ SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog
+ # Mark requests for the robots.txt file
+ SetEnvIf Request_URI "^/robots\.txt$" dontlog
+ # Log what remains
+ CustomLog logs/access_log common env=!dontlog +

+ +

¾¤ÎÎã¤È¤·¤Æ¡¢±Ñ¸ì¤òÏ乿ͤ«¤é¤Î¥ê¥¯¥¨¥¹¥È¤È¤½¤ì°Ê³°¤Î¿Í¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤ò + ʬ¤±¤¿¤¤¡¢¤È¤¤¤¦¾ì¹ç¤ò¹Í¤¨¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ SetEnvIf Accept-Language "en" english
+ CustomLog logs/english_log common env=english
+ CustomLog logs/non_english_log common env=!english +

+ +

¤³¤³¤Þ¤Ç¤Ç¤Ï¾ò·ïÉÕ¤­¥í¥®¥ó¥°¤¬Èó¾ï¤Ë¶¯ÎϤǽÀÆð¤Ç¤¢¤ë¤³¤È¤ò¼¨¤·¤Æ¤­¤Þ¤·¤¿¤¬¡¢ + ¤½¤ì¤¬¥í¥°¤ÎÆâÍƤòÀ©¸æ¤¹¤ëÍ£°ì¤ÎÊýË¡¤È¤¤¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¥í¥°¥Õ¥¡¥¤¥ë¤Ï + ¥µ¡¼¥Ð¤Î³èÆ°¤Î´°Á´¤Êµ­Ï¿¤Ç¤¢¤ëÊý¤¬¤è¤êÌò¤ËΩ¤Á¤Þ¤¹¡£Ã±½ã¤Ë¥í¥°¥Õ¥¡¥¤¥ë¤ò + ¸å½èÍý¤·¤Æ¡¢¹Íθ¤·¤¿¤¯¤Ê¤¤¥í¥°¤òºï½ü¤¹¤ëÊý¤¬´Êñ¤Ç¤¢¤ë¤³¤È¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£

+ +
top
+
+

¥í¥°¤Î¸òÂØ

+ + +

ÉáÄ̤ÎÉé²Ù¤Î¥µ¡¼¥Ð¤Ç¤µ¤¨¡¢¥í¥°¥Õ¥¡¥¤¥ë¤ËÊݸ¤µ¤ì¤ë¾ðÊó¤ÎÎÌ¤Ï + ËÄÂç¤Ë¤Ê¤ê¤Þ¤¹¡£¥¢¥¯¥»¥¹¥í¥°¤Î¥Õ¥¡¥¤¥ë¤ÏÉáÄÌ 10,000 ¥ê¥¯¥¨¥¹¥ÈËè¤Ë + 1 MB °Ê¾åÁý¤¨¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢´û¸¤Î¥í¥°¤ò°ÜÆ°¤·¤¿¤ê¡¢ºï½ü¤·¤¿¤ê¤·¤Æ¡¢ + Äê´üŪ¤Ë¥í¥°¤ò¸òÂؤµ¤»¤ë¤³¤È¤¬É¬Íפˤʤê¤Þ¤¹¡£¤³¤ì¤Ï¥µ¡¼¥Ð¤Î¼Â¹ÔÃæ¤Ë¤Ï + ¹Ô¤Ê¤¨¤Þ¤»¤ó¡£¤È¤¤¤¦¤Î¤Ï¡¢Apache ¤Ï¥Õ¥¡¥¤¥ë¤¬ open ¤µ¤ì¤Æ¤¤¤ë´Ö¤Ï + ¤º¤Ã¤È¸Å¤¤¥í¥°¥Õ¥¡¥¤¥ë¤Ë½ñ¤­Â³¤±¤ë¤«¤é¤Ç¤¹¡£ + ¿·¤·¤¤¥í¥°¥Õ¥¡¥¤¥ë¤ò open ¤Ç¤­¤ë¤è¤¦¤Ë¡¢¥í¥°¥Õ¥¡¥¤¥ë¤¬°ÜÆ°¤µ¤ì¤¿¤ê + ºï½ü¤µ¤ì¤¿¸å¤Ë¡¢¥µ¡¼¥Ð¤òºÆµ¯Æ°¤¹¤ë + ɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

Í¥²í¤Ê ºÆµ¯Æ°¤ò¹Ô¤Ê¤¦¤³¤È¤Ç¡¢¥µ¡¼¥Ð¤Ï´û¸¤Î¥³¥Í¥¯¥·¥ç¥ó¤ä + ½èÍýÂÔ¤Á¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò¼º¤¦¤³¤È¤Ê¤¯¿·¤·¤¤¥í¥°¥Õ¥¡¥¤¥ë¤ò open ¤µ¤»¤ë + ¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤·¤«¤·¡¢¤³¤ì¤ò¼Â¸½¤¹¤ë¤¿¤á¤Ë¡¢¥µ¡¼¥Ð¤Ï¸Å¤¤¥ê¥¯¥¨¥¹¥È¤ò + °·¤Ã¤Æ¤¤¤ë´Ö¤Ï¸Å¤¤¥í¥°¥Õ¥¡¥¤¥ë¤Ë½ñ¤­Â³¤±¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢ºÆµ¯Æ°¤Î¸å¤Ç¤Ï¥í¥°¥Õ¥¡¥¤¥ë¤Î½èÍý¤ò»Ï¤á¤ëÁ°¤Ë¡¢¤·¤Ð¤é¤¯ÂÔ¤¿¤Ê¤±¤ì¤Ð + ¤Ê¤ê¤Þ¤»¤ó¡£Ã±¤Ë¥í¥°¤ò¸òÂؤµ¤»¤Æ¡¢¥Ç¥£¥¹¥¯¤ÎÀáÌó¤Î¤¿¤á¤Ë¸Å¤¤¥í¥°¤ò + °µ½Ì¤¹¤ëÉáÄ̤Υ·¥Ê¥ê¥ª¤Ï:

+ +

+ mv access_log access_log.old
+ mv error_log error_log.old
+ apachectl graceful
+ sleep 600
+ gzip access_log.old error_log.old +

+ +

¥í¥°¤Î¸òÂؤò¤¹¤ë¤â¤¦°ì¤Ä¤ÎÊýË¡¤Ï¥Ñ¥¤¥×·Ðͳ¤Î¥í¥°¤ò»È¤¦¤â¤Î¤Ç¡¢¼¡¤ÎÀá¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+
top
+
+

¥Ñ¥¤¥×·Ðͳ¤Î¥í¥°

+ + +

Apache httpd ¤Ï¥¨¥é¡¼¥í¥°¤È¥¢¥¯¥»¥¹¥í¥°¤ò¥Õ¥¡¥¤¥ë¤ËľÀܽñ¤¯Âå¤ï¤ê¤Ë¡¢ + ¥Ñ¥¤¥×¤òÄ̤·¤ÆÊÌ¤Î¥×¥í¥°¥é¥à¤Ë½ñ¤­½Ð¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Îµ¡Ç½¤Ë¤è¤ê¡¢¼ç¥µ¡¼¥Ð¤Ë¥³¡¼¥É¤òÄɲ乤뤳¤È¤Ê¤¯ + ¥í¥®¥ó¥°¤Î½ÀÆðÀ­¤¬Èó¾ï¤Ë¹â¤Þ¤Ã¤Æ¤¤¤Þ¤¹¡£¥Ñ¥¤¥×¤Ë¥í¥°¤ò½ñ¤¯¤¿¤á¤Ë¤Ï¡¢ + ñ¤Ë¥Õ¥¡¥¤¥ë̾¤ò¥Ñ¥¤¥×ʸ»ú "|" ¤ËÃÖ¤­´¹¤¨¡¢¤½¤Î³¤­¤Ë + ɸ½àÆþÎϤ«¤é¥í¥°¤Î¥¨¥ó¥È¥ê¤ò¼õ¤±¤È¤ë¼Â¹Ô¥×¥í¥°¥é¥à¤Î̾Á°¤ò½ñ¤¯¤À¤±¤Ç¤¹¡£ + Apache ¤Ï¥Ñ¥¤¥×·Ðͳ¤Î¥í¥°ÍÑ¤Î¥×¥í¥»¥¹¤ò¥µ¡¼¥Ð¤Îµ¯Æ°»þ¤Ë¼Â¹Ô¤·¡¢ + ¥µ¡¼¥Ð¤Î¼Â¹ÔÃæ¤Ë¤½¤Î¥×¥í¥°¥é¥à¤¬¥¯¥é¥Ã¥·¥å¤·¤¿¤È¤­¤Ï¤½¤ì¤òºÆ¤Ó + ¼Â¹Ô¤·¤Þ¤¹¡£(¤³¤ÎºÇ¸å¤Îµ¡Ç½¤¬¤³¤Îµ»½Ñ¤¬¡Ö¿®ÍêÀ­¤Î¤¢¤ë¥Ñ¥¤¥×·Ðͳ¤Î¥í¥®¥ó¥°¡× + ¤È¸Æ¤Ð¤ì¤Æ¤¤¤ëÍýͳ¤Ç¤¹¡£)

+ +

¥Ñ¥¤¥×·Ðͳ¤Î¥í¥°ÍÑ¤Î¥×¥í¥»¥¹¤Ï Apache httpd ¤Î¿Æ¥×¥í¥»¥¹¤«¤éµ¯Æ°¤µ¤ì¡¢ + ¤½¤Î¥×¥í¥»¥¹¤Î¥æ¡¼¥¶ ID ¤ò·Ñ¾µ¤·¤Þ¤¹¡£¤³¤ì¤Ï¡¢¥Ñ¥¤¥×·Ðͳ¤Î¥í¥°ÍѤΠ+ ¥×¥í¥°¥é¥à¤ÏÉáÄÌ root ¤È¤·¤Æ¼Â¹Ô¤µ¤ì¤ë¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢¥×¥í¥°¥é¥à¤ò´Êñ¤Ç°ÂÁ´¤ËÊݤĤ³¤È¤¬Èó¾ï¤Ë½ÅÍפǤ¹¡£

+ +

¥Ñ¥¤¥×·Ðͳ¤Î¥í¥°¤Î½ÅÍפÊÍøÍÑË¡¤Ï¡¢¥µ¡¼¥Ð¤ÎºÆµ¯Æ°¤Ê¤·¤Ç¥í¥°¤Î¸òÂؤò + ¤¹¤ë¤³¤È¤Ç¤¹¡£Apache HTTP ¥µ¡¼¥Ð¤Ë¤Ï¤³¤Î¤¿¤á¤Î rotatelogs ¤È¸Æ¤Ð¤ì¤ë´Êñ¤Ê + ¥×¥í¥°¥é¥à¤¬ÉÕ°¤·¤Æ¤¤¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢24 »þ´ÖËè¤Ë¥í¥°¤ò¸òÂؤµ¤»¤ë¤Ë¤Ï¡¢ + °Ê²¼¤Î¤â¤Î¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ CustomLog "|/usr/local/apache/bin/rotatelogs + /var/log/access_log 86400" common +

+ +

¥Ñ¥¤¥×¤ÎÀè¤Ç¸Æ¤Ð¤ì¤ë¥³¥Þ¥ó¥ÉÁ´ÂΤ¬°úÍÑÉä¤Ç°Ï¤Þ¤ì¤Æ¤¤¤ë¤³¤È¤ËÃíÌܤ·¤Æ + ¤¯¤À¤µ¤¤¡£¤³¤ÎÎã¤Ï¥¢¥¯¥»¥¹¥í¥°¤ò»È¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢¥¨¥é¡¼¥í¥°¤Ë¤âƱ¤¸µ»½Ñ¤ò + »È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

»÷¤Æ¤¤¤ë¤±¤ì¤É¡¢¤è¤ê¤º¤Ã¤È½ÀÆð¤Ê + cronolog ¤È¤¤¤¦¥í¥°¸òÂØÍѤΠ+ ¥×¥í¥°¥é¥à¤¬³°Éô¤Î¥µ¥¤¥È¤Ë¤¢¤ê¤Þ¤¹¡£

+ +

¾ò·ïÉÕ¤­¥í¥®¥ó¥°¤ÈƱÍÍ¡¢¥Ñ¥¤¥×·Ðͳ¤Î¥í¥°¤ÏÈó¾ï¤Ë¶¯ÎÏ¤Ê + Æ»¶ñ¤Ç¤¹¤¬¡¢¥ª¥Õ¥é¥¤¥ó¤Î¸å½èÍý¤Î¤è¤¦¤Ê¡¢¤è¤ê´Êñ¤Ê²ò·èÊýË¡¤¬¤¢¤ë¤È¤­¤Ï + »È¤ï¤Ê¤¤Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+
top
+
+

¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È

+ + +

¿¤¯¤Î ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È ¤Î¤¢¤ë¥µ¡¼¥Ð¤ò¼Â¹Ô¤·¤Æ¤¤¤ë + ¤È¤­¤Ï¡¢¥í¥°¥Õ¥¡¥¤¥ë¤Î°·¤¤Êý¤Ë¤¤¤¯¤Ä¤«¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£ + ¤Þ¤º¡¢Ã±ÆȤΥۥ¹¥È¤Î¤ß¤Î¥µ¡¼¥Ð¤È¤Þ¤Ã¤¿¤¯Æ±¤¸¤è¤¦¤Ë¥í¥°¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥í¥®¥ó¥°¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¼ç¥µ¡¼¥Ð¤Î¥³¥ó¥Æ¥­¥¹¥È¤Î + <VirtualHost> ¥»¥¯¥·¥ç¥ó¤Î³°¤ËÃÖ¤¯¤³¤È¤Ç¡¢ + ¤¹¤Ù¤Æ¤Î¥í¥°¤òƱ¤¸¥¢¥¯¥»¥¹¥í¥°¤È¥¨¥é¡¼¥í¥°¤Ë¥í¥°¼ý½¸¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¼êË¡¤Ç¤Ï¸Ä¡¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÅý·×¤ò´Êñ¤Ë¤È¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£

+ +

CustomLog ¤ä + ErrorLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + <VirtualHost> ¤ÎÃæ¤Ë + ÃÖ¤«¤ì¤¿¾ì¹ç¤Ï¡¢¤½¤Î¥Ð¡¼¥Á¥ã¥ë + ¥Û¥¹¥È¤Ø¤Î¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤ä¥¨¥é¡¼¤¬¤½¤³¤Ç»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤Ë¤Î¤ß + ¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹¡£¥í¥®¥ó¥°¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¤Ê¤¤¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ï + °ÍÁ³¤È¤·¤Æ¥ê¥¯¥¨¥¹¥È¤¬¼ç¥µ¡¼¥Ð¤Î¥í¥°¤ËÁ÷¤é¤ì¤Þ¤¹¡£¤³¤Î¼êË¡¤Ï¾¯¤Ê¤¤ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËÂФ·¤Æ¤ÏÈó¾ï¤ËÍ­ÍѤǤ¹¤¬¡¢¥Û¥¹¥È¤Î¿ô¤¬Èó¾ï¤Ë¿¤¯¤Ê¤ë¤È + ´ÉÍý¤¬ÂçÊѤˤʤê¤Þ¤¹¡£¤µ¤é¤Ë¡¢¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î¸Â³¦¤ÎÌäÂê¤òµ¯¤³¤¹¤³¤È¤¬ + ¤¢¤ê¤Þ¤¹¡£

+ +

¥¢¥¯¥»¥¹¥í¥°¤Ë¤Ï¡¢Èó¾ï¤ËÎɤ¤ÂŶ¨°Æ¤¬¤¢¤ê¤Þ¤¹¡£¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î + ¾ðÊó¤ò¥í¥°¤Î¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ë²Ã¤¨¤ë¤³¤È¤Ç¡¢¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤Ø¤Î + ¥ê¥¯¥¨¥¹¥È¤òƱ¤¸¥í¥°¤Ë¥í¥°¼ý½¸¤·¤Æ¡¢¸å¤Ç¥í¥°¤ò¸Ä¡¹¤Î¥Õ¥¡¥¤¥ë¤Ëʬ³ä¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ LogFormat "%v %l %u %t \"%r\" %>s %b" + comonvhost
+ CustomLog logs/access_log comonvhost +

+ +

%v ¤¬¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤Æ¤¤¤ë¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î̾Á°¤ò + ¥í¥°¼ý½¸¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£¤½¤·¤Æ¡¢split-logfile ¤Î¤è¤¦¤Ê¥×¥í¥°¥é¥à¤ò + »È¤Ã¤Æ¥¢¥¯¥»¥¹¥í¥°¤ò¸å½èÍý¤¹¤ë¤³¤È¤Ç¡¢ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈËè¤Î¥Õ¥¡¥¤¥ë¤Ë¥í¥°¤òʬ³ä¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

»ÄÇ°¤Ê¤¬¤é¡¢¥¨¥é¡¼¥í¥°¤Ë¤ÏƱÍͤμêË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤Ç¤¹¤«¤é¡¢ + ¤¹¤Ù¤Æ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤òƱ¤¸¥¨¥é¡¼¥í¥°¤ÎÃæ¤Ëº®¤¼¤ë¤«¡¢ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈËè¤Ë¥¨¥é¡¼¥í¥°¤ò»È¤¦¤«¤òÁª¤Ð¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
top
+
+

¾¤Î¥í¥°¥Õ¥¡¥¤¥ë

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

¼ÂºÝ¤ËÁ÷¼õ¿®¤·¤¿¥Ð¥¤¥È¿ô¤Î¥í¥°

+ + +

mod_logio ¤Ï¡¢ + ¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Ç¼ÂºÝ¤ËÁ÷¼õ¿®¤·¤¿¿ô¤ò¥í¥°¤¹¤ë + Æó¤Ä¤Î¥Õ¥£¡¼¥ë¥É (%I ¤È %O) ¤ò + LogFormat + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ËÄɲä·¤Þ¤¹¡£

+ + +

Forensic ¥í¥°

+ + +

mod_log_forensic ¤Ï¥¯¥é¥¤¥¢¥ó¥È¥ê¥¯¥¨¥¹¥È¤Î + forensic ¥í¥°¤ò¼è¤ê¤Þ¤¹¡£¥í¥°¤Ï¥ê¥¯¥¨¥¹¥È½èÍýÁ°¤È½èÍý¸å¤Ë + ¹Ô¤ï¤ì¤Þ¤¹¤Î¤Ç¡¢1 ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ 2 ¹Ô¤Î¥í¥°¤¬½ÐÎϤµ¤ì¤Þ¤¹¡£ + forensic ¥í¥¬¡¼¤Ï¤È¤Æ¤â¸·Ì©¤Ç¥«¥¹¥¿¥Þ¥¤¥º¤Ç¤­¤Þ¤»¤ó¡£ + ¥Ç¥Ð¥Ã¥°¤ä¥»¥­¥å¥ê¥Æ¥£ÍѤΥġ¼¥ë¤È¤·¤ÆÍ­¸ú¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ + +

PID ¥Õ¥¡¥¤¥ë

+ + +

µ¯Æ°»þ¤Ë¡¢Apache ¤Ï¿Æ httpd ¥×¥í¥»¥¹¤Î¥×¥í¥»¥¹ ID ¤ò + logs/httpd.pid ¤ËÊݸ¤·¤Þ¤¹¡£¤³¤Î + ¥Õ¥¡¥¤¥ë̾¤Ï PidFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ + Êѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¥×¥í¥»¥¹ ID ¤Ï´ÉÍý¼Ô¤¬¿Æ¥×¥í¥»¥¹¤Ë + ¥·¥°¥Ê¥ë¤òÁ÷¤ë¤³¤È¤Ç¥Ç¡¼¥â¥ó¤òºÆµ¯Æ°¤·¤¿¤ê½ªÎ»¤µ¤»¤¿¤ê¤¹¤ë¤È¤­¤Ë + »ÈÍѤ·¤Þ¤¹¡£Windows ¤Ç¤Ï¡¢Âå¤ï¤ê¤Ë -k ¥³¥Þ¥ó¥É¥ª¥×¥·¥ç¥ó¤ò + »È¤Ã¤Æ¤¯¤À¤µ¤¤¡£¾Ü¤·¤¤¾ðÊó¤Ï ½ªÎ»¤È + ºÆµ¯Æ° ¤Î¥Ú¡¼¥¸¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£

+ + +

¥¹¥¯¥ê¥×¥È¥í¥°

+ + +

¥Ç¥Ð¥Ã¥°¤ÎÊä½õ¤Î¤¿¤á¤Ë¡¢ScriptLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + CGI ¥¹¥¯¥ê¥×¥È¤ÎÆþÎϤȽÐÎϤòµ­Ï¿¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ï¥Æ¥¹¥ÈÍѤˤΤ߻ÈÍѤ·¤Æ¡¢Ä̾ï¤Î¥µ¡¼¥Ð¤Ç¤Ï»ÈÍѤ·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + ¾Ü¤·¤¤¾ðÊó¤Ï mod_cgi ¤Îʸ½ñ ¤Ë¤¢¤ê¤Þ¤¹¡£

+ + +

¥ê¥é¥¤¥È¥í¥°

+ + +

mod_rewrite ¤Î¶¯ÎÏ¤Ç + Ê£»¨¤Êµ¡Ç½¤ò + »È¤Ã¤Æ¤¤¤ë¤È¤­¤Ï¡¢¤Û¤Ü¤¤¤Ä¤â¥Ç¥Ð¥Ã¥°¤ò´Êñ¤Ë¤¹¤ë¤¿¤á¤Ë + RewriteLog ¤Î»ÈÍѤ¬ + ɬÍפǤ·¤ç¤¦¡£¤³¤Î¥í¥°¥Õ¥¡¥¤¥ë¤Ë¤Ï¥ê¥é¥¤¥È¥¨¥ó¥¸¥ó¤¬¥ê¥¯¥¨¥¹¥È¤ò + ½ñ¤­´¹¤¨¤ëÊýË¡¤Î¾ÜºÙ¤Ê²òÀϤ¬½ÐÎϤµ¤ì¤Þ¤¹¡£¾Ü¤·¤µ¤ÎÅÙ¹ç¤Ï RewriteLogLevel + ¤ÇÀ©¸æ¤Ç¤­¤Þ¤¹¡£

+ +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/logs.html.ko.euc-kr b/docs/manual/logs.html.ko.euc-kr new file mode 100644 index 00000000..3e22813b --- /dev/null +++ b/docs/manual/logs.html.ko.euc-kr @@ -0,0 +1,521 @@ + + + +·Î±×ÆÄÀÏ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

·Î±×ÆÄÀÏ

+
+

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

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

È¿À²ÀûÀ¸·Î À¥¼­¹ö¸¦ °ü¸®ÇÏ·Á¸é ¹ß»ýÇÏ´Â ¹®Á¦¿Í ÇÔ²² ¼­¹öÀÇ + È°µ¿°ú ¼º´É¿¡ ´ëÇØ ¾Ë¾Æ¾ß ÇÑ´Ù. ¾ÆÆÄÄ¡ À¥¼­¹ö´Â ¸Å¿ì Á¾ÇÕÀûÀÌ°í + À¯¿¬ÇÑ ·Î±× ±â´ÉÀ» Á¦°øÇÑ´Ù. ÀÌ ¹®¼­´Â ·Î±× ±â´ÉÀ» ¼³Á¤ÇÏ´Â + ¹æ¹ý°ú ·Î±×¿¡ µé¾î°¥ ³»¿ëÀ» ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

º¸¾È °æ°í

+ + +

´©±º°¡¿¡°Ô ¾ÆÆÄÄ¡ÀÇ ·Î±×ÆÄÀÏÀÌ ÀÖ´Â µð·ºÅ丮¿¡ ¾²±â±ÇÇÑÀÌ + ÀÖ´Ù¸é (º¸Åë root) ¼­¹ö¸¦ ½ÇÇàÇÏ´Â uid¸¦ °ÅÀÇ È®½ÇÈ÷ ¾òÀ» + ¼ö ÀÖ´Ù. À̸¦ °í·ÁÇÏÁö¾Ê°í ·Î±×°¡ ÀúÀåµÈ µð·ºÅ丮¿¡ ¾²±â±ÇÇÑÀ» + ÁÖÁö ¸¶¶ó. ÀÚ¼¼ÇÑ ³»¿ëÀº º¸¾È ÆÁ ¹®¼­¸¦ Âü°íÇ϶ó.

+ +

¶Ç, Ŭ¶óÀ̾ðÆ®°¡ Á¦°øÇÑ Á¤º¸´Â ·Î±×ÆÄÀÏ¿¡ °ÅÀÇ ±×´ë·Î + ±â·ÏµÈ´Ù. ±×·¡¼­ ¾ÇÀÇ°¡ Àִ Ŭ¶óÀ̾ðÆ®°¡ ·Î±×ÆÄÀÏ¿¡ Á¦¾î¹®ÀÚ¸¦ + ³ÖÀ» ¼ö ÀÖÀ¸¹Ç·Î, ·Î±×¸¦ ´Ù·ê¶§´Â ÁÖÀÇÇØ¾ß ÇÑ´Ù.

+
top
+
+

¿À·ù ·Î±× (Error Log)

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

ErrorLog Áö½Ã¾î´Â + °¡Àå Áß¿äÇÑ ·Î±×ÆÄÀÏÀÎ ¼­¹ö ¿À·ù ·Î±×ÀÇ À̸§°ú À§Ä¡¸¦ ÁöÁ¤ÇÑ´Ù. + ¾ÆÆÄÄ¡ À¥¼­¹ö´Â ÀÌ ÆÄÀÏ¿¡ Áø´ÜÁ¤º¸¿Í ¿äûÀ» ó¸®ÇÏ´Â µµÁß + ¹ß»ýÇÑ ¿À·ù¸¦ ±â·ÏÇÑ´Ù. ¼­¹ö°¡ ½ÃÀÛÇϰųª µ¿ÀÛÇϴµ¥ ¹®Á¦°¡ + ÀÖ´Ù¸é ¹«¾ùÀÌ À߸øµÇ¾ú°í ¶§¶§·Î ¾î¶»°Ô °íÄ¡´ÂÁö¸¦ ¾Ë·ÁÁÖ´Â + ÀÌ°÷À» °¡Àå ¸ÕÀú »ìÆìºÁ¾ß ÇÑ´Ù.

+ +

¿À·ù ·Î±×´Â º¸Åë (ÀüÇüÀûÀ¸·Î À¯´Ð½º ½Ã½ºÅÛ¿¡¼­´Â + error_log, À©µµ¿ìÁî¿Í OS/2¿¡¼­´Â + error.log) ÆÄÀÏ¿¡ ±â·ÏµÈ´Ù. À¯´Ð½º ½Ã½ºÅÛ¿¡¼­ + ¼­¹ö´Â ¿À·ù¸¦ syslog³ª ÆÄÀÌÇÁ¸¦ + »ç¿ëÇÏ¿© ´Ù¸¥ ÇÁ·Î±×·¥À¸·Î º¸³¾ ¼öµµ ÀÖ´Ù.

+ +

¿À·ù ·Î±×ÀÇ Çü½ÄÀº »ó´ëÀûÀ¸·Î ÀÚÀ¯·Ó°í ÀÚ¼¼ÇÏ´Ù. ±×·¯³ª + ´ëºÎºÐÀÇ ¿À·ù ·Î±× Ç׸ñ¿¡ °øÅëÀûÀ¸·Î ³ª¿À´Â Á¤º¸°¡ ÀÖ´Ù. + ¿¹¸¦ µé¾î, Ç׸ñÀº º¸Åë ´ÙÀ½°ú °°´Ù.

+ +

+ [Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1] + client denied by server configuration: + /export/home/live/ap/htdocs/test +

+ +

·Î±× Ç׸ñ¿¡¼­ ù¹ø° Ç׸ñÀº ³¯Â¥¿Í ½Ã°£ÀÌ´Ù. µÎ¹ø° + Ç׸ñÀº º¸°íÇÏ´Â ¿À·ùÀÇ ½É°¢¼ºÀ» ³ªÅ¸³½´Ù. LogLevel Áö½Ã¾î·Î ¿À·ù ·Î±×¿¡ + ±â·ÏµÇ´Â ¿À·ùÀÇ ½É°¢¼ºÀ» Á¦ÇÑÇÒ ¼ö ÀÖ´Ù. ¼¼¹ø° Ç׸ñÀº + ¿À·ù¸¦ ¹ß»ýÇÑ Å¬¶óÀ̾ðÆ®ÀÇ IP ÁÖ¼ÒÀÌ´Ù. ÀÌ ´ÙÀ½ºÎÅÍ ¿À·ù¹®ÀÌ + ³ª¿À¸ç, ÀÌ °æ¿ì ¼­¹ö°¡ Ŭ¶óÀ̾ðÆ®ÀÇ Á¢±ÙÀ» °ÅºÎÇϵµ·Ï + ¼³Á¤µÇ¾ú´Ù°í ³ª¿ÍÀÖ´Ù. ¿äûÇÑ ¹®¼­ÀÇ (À¥ °æ·Î°¡ ¾Æ´Ñ) + ÆÄÀϽýºÅÛ °æ·Îµµ º¸ÀδÙ.

+ +

¿À·ù ·Î±×¿¡´Â ¸Å¿ì ´Ù¾çÇÑ Á¾·ùÀÇ ¹®±¸°¡ ³ª¿Ã ¼ö ÀÖ´Ù. + ´ëºÎºÐÀº À§¿Í ºñ½ÁÇÏ´Ù. CGI ½ºÅ©¸³Æ®ÀÇ µð¹ö±ë Ãâ·Âµµ ¿À·ù + ·Î±×¿¡ ±â·ÏµÈ´Ù. CGI ½ºÅ©¸³Æ®°¡ stderr¿¡ ¾´ + Á¤º¸´Â ±×´ë·Î ¿À·ù ·Î±×·Î º¹»çµÈ´Ù.

+ +

¿À·ù ·Î±×¿¡ Á¤º¸¸¦ Ãß°¡ÇÏ°¡³ª »ý·«ÇÒ ¼ö ¾ø´Ù. ±×·¯³ª + ¿äû¿¡ ´ëÇÑ ¿À·ù ·Î±×ÀÇ °æ¿ì Á¢±Ù + ·Î±×¿¡µµ ´ëÀÀÇÏ´Â Ç׸ñÀÌ »ý±ä´Ù. ¿¹¸¦ µé¾î, À§ÀÇ °æ¿ì + »óÅÂÄڵ尡 403ÀÎ Á¢±Ù ·Î±× Ç׸ñÀÌ »ý±ä´Ù. Á¢±Ù ·Î±×´Â + »ç¿ëÀÚÁ¤ÀÇÇÒ ¼ö ÀÖÀ¸¹Ç·Î ÀÌ ÆÄÀÏÀ» Âü°íÇÏ¿© ¿À·ù »óȲ¿¡ + ´ëÇÑ Ãß°¡Á¤º¸¸¦ ¾òÀ» ¼ö ÀÖ´Ù.

+ +

°Ë»çÇÒ¶§ ¾î¶² ¹®Á¦°¡ »ý±â´ÂÁö ¿À·ù ·Î±×¸¦ °è¼Ó »ìÆ캸´Â + °ÍÀÌ ÁÁ´Ù. À¯´Ð½º ½Ã½ºÅÛ¿¡¼­ ´ÙÀ½°ú °°ÀÌ ÇÑ´Ù:

+ +

+ tail -f error_log +

+
top
+
+

Á¢±Ù ·Î±× (Access Log)

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

¼­¹ö Á¢±Ù ·Î±×´Â ¼­¹ö°¡ ó¸®ÇÏ´Â ¸ðµç ¿äûÀ» ±â·ÏÇÑ´Ù. + CustomLog + Áö½Ã¾î´Â Á¢±Ù ·Î±×ÀÇ À§Ä¡¿Í ³»¿ëÀ» ÁöÁ¤ÇÑ´Ù. LogFormat Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© ·Î±×¿¡ Æ÷ÇÔÇÒ ³»¿ëÀ» ½±°Ô ¼±ÅÃÇÒ ¼ö ÀÖ´Ù. ÀÌ ÀýÀº + ¼­¹ö°¡ Á¢±Ù ·Î±×¿¡ ¾µ ³»¿ëÀ» ¼³Á¤ÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù.

+ +

¹°·Ð Á¢±Ù ·Î±×¿¡ Á¤º¸¸¦ ±â·ÏÇÏ´Â °ÍÀº ·Î±× °ü¸®ÀÇ ½ÃÀÛÀÏ + »ÓÀÌ´Ù. ´ÙÀ½ ´Ü°è´Â ÀÌ Á¤º¸¸¦ ºÐ¼®ÇÏ¿© À¯¿ëÇÑ Åë°è¸¦ ¸¸µå´Â + °ÍÀÌ´Ù. ÀÌ ¹®¼­´Â ÀϹÝÀûÀÎ ·Î±× ºÐ¼®¿¡ ´ëÇؼ­ ´Ù·çÁö ¾ÊÀ¸¸ç, + ·Î±× ºÐ¼®Àº ½ÇÁ¦ À¥¼­¹ö°¡ ÇÒ ÀÏÀÌ ¾Æ´Ï´Ù. ·Î±× ºÐ¼®¿¡ ´ëÇÑ + Á¤º¸¿Í ·Î±×¸¦ ºÐ¼®ÇÏ´Â ¼ÒÇÁÆ®¿þ¾î¿¡ ´ëÇؼ­´Â Open Directory³ª + Yahoo¸¦ + Âü°íÇ϶ó.

+ +

¾ÆÆÄÄ¡ À¥¼­¹ö´Â ÀÌÀüºÎÅÍ mod_log_referer, mod_log_agent, + CustomLog + °°Àº ¸ðµâ°ú Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© Á¢±Ù ·Î±×¸¦ ´Ù·ç¾ú´Ù. Áö±ÝÀº + CustomLog + Áö½Ã¾î°¡ ¿À·¡µÈ Áö½Ã¾îµéÀÇ ¸ðµç ±â´ÉÀ» À̾î¹Þ¾Ò´Ù.

+ +

Á¢±Ù ·Î±×ÀÇ Çü½ÄÀº ¸Å¿ì »ç¿ëÀÚÁ¤ÀÇ °¡´ÉÇÏ´Ù. Çü½ÄÀº CÀÇ + printf(1) Çü½Ä¹®ÀÚ¿­°ú ¸Å¿ì À¯»çÇÑ Çü½Ä¹®ÀÚ¿­À» »ç¿ëÇÏ¿© + ÁöÁ¤ÇÑ´Ù. ´ÙÀ½ Àý¿¡ ¿¹¸¦ µé¾ú´Ù. Çü½Ä¹®ÀÚ¿­¿¡ »ç¿ë°¡´ÉÇÑ + ¸ðµç ³»¿ëÀ» ¾Ë·Á¸é mod_log_config Çü½Ä¹®ÀÚ¿­À» + Âü°íÇ϶ó.

+ +

Common ·Î±× Çü½Ä

+ + +

Á¢±Ù ·Î±×ÀÇ ÀüÇüÀûÀÎ ¼³Á¤Àº ´ÙÀ½°ú °°´Ù.

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common +

+ +

±×·¯¸é ÁöÁ¤ÇÑ ·Î±× Çü½Ä¹®ÀÚ¿­À» º°¸í + commonÀ¸·Î Á¤ÀÇÇÑ´Ù. Çü½Ä¹®ÀÚ¿­Àº ÆÛ¼¾Æ® + Áö½Ã¾îµé·Î ±¸¼ºµÇ¸ç, °¢°¢Àº ¾î¶² Á¤º¸¸¦ ±â·ÏÇÒÁö ¾Ë¸°´Ù. + Çü½Ä¹®ÀÚ¿­¿¡ ÀÏ¹Ý ¹®ÀÚ¸¦ ÀûÀ¸¸é ±×´ë·Î ·Î±×¿¡ Ãâ·ÂµÈ´Ù. + µû¿ÈÇ¥ ¹®ÀÚ(")¸¦ Ãâ·ÂÇÏ°í ½Í´Ù¸é ¹é½½·¡½¬¸¦ + ¾Õ¿¡ ºÙ¿©¼­ Çü½Ä¹®ÀÚ¿­ÀÇ ³¡ÀÌ ¾Æ´ÔÀ» Ç¥½ÃÇÑ´Ù. Çü½Ä¹®ÀÚ¿­¿¡ + ÁÙ¹Ù²Þ "\n", ÅÇ "\t"¿Í °°Àº + Ư¼ö Á¶Àý¹®ÀÚ¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

CustomLog + Áö½Ã¾î´Â Á¤ÀÇÇÑ º°¸íÀ» »ç¿ëÇÏ´Â »õ·Î¿î ·Î±×ÆÄÀÏÀ» + ¸¸µç´Ù. Á¢±Ù ·Î±×ÀÇ ÆÄÀϸíÀÌ ½½·¡½¬·Î ½ÃÀÛÇÏÁö¾ÊÀ¸¸é + ServerRootÀÇ »ó´ë°æ·ÎÀÌ´Ù.

+ +

¾ÕÀÇ ¼³Á¤Àº °øÅë·Î±×Çü½Ä(Common Log Format, CLF)À̶ó´Â + Çü½ÄÀ¸·Î ·Î±× Ç׸ñÀ» ±â·ÏÇÑ´Ù. ¿©·¯ ´Ù¸¥ À¥¼­¹öµéµµ ÀÌ·± + Ç¥ÁØ Çü½ÄÀ¸·Î ·Î±×¸¦ ¸¸µé¸ç, ¿©·¯ ·Î±× ºÐ¼® ÇÁ·Î±×·¥¿¡¼­ + ÀÐÀ» ¼ö ÀÖ´Ù. CLF·Î ¸¸µç ·Î±×ÆÄÀÏ Ç׸ñÀº ´ÙÀ½°ú °°´Ù:

+ +

+ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET + /apache_pb.gif HTTP/1.0" 200 2326 +

+ +

ÀÌÁ¦ ·Î±× Ç׸ñÀÇ °¢ ºÎºÐÀ» ¼³¸íÇÑ´Ù.

+ +
+
127.0.0.1 (%h)
+ +
¼­¹ö¿¡ ¿äûÀ» ÇÑ Å¬¶óÀ̾ðÆ®(¿ø°Ý È£½ºÆ®)ÀÇ IP + ÁÖ¼ÒÀÌ´Ù. HostnameLookups°¡ + OnÀ̶ó¸é È£½ºÆ®¸íÀ» ã¾Æ¼­ IP ÁÖ¼Ò ÀÚ¸®¿¡ + ´ë½Å ¾´´Ù. ±×·¯³ª ÀÌ ¼³Á¤Àº ¼­¹ö¸¦ ¸Å¿ì ´À¸®°Ô ÇÒ ¼ö + ÀÖÀ¸¹Ç·Î ÃßõÇÏÁö ¾Ê´Â´Ù. È£½ºÆ®¸íÀ» ¾Ë·Á¸é ´ë½Å ³ªÁß¿¡ + logresolve¿Í + °°Àº ·Î±×¸¦ ó¸®ÇÏ´Â ÇÁ·Î±×·¥À» »ç¿ëÇÏ´Â °ÍÀÌ ÁÁ´Ù. + ¿©±â¿¡ ³ª¿Â IP ÁÖ¼Ò´Â »ç¿ëÀÚ°¡ »ç¿ëÇÏ´Â ÄÄÇ»ÅÍ ÁÖ¼Ò°¡ + ¾Æ´Ò ¼ö ÀÖ´Ù. ÇÁ·Ï½Ã ¼­¹ö°¡ »ç¿ëÀÚ¿Í ¼­¹ö»çÀÌ¿¡ Á¸ÀçÇÑ´Ù¸é, + ¿ø·¡ ÄÄÇ»ÅÍ ÁÖ¼Ò°¡ ¾Æ´Ï¶ó ÇÁ·Ï½ÃÀÇ ÁÖ¼Ò°¡ ±â·ÏµÉ °ÍÀÌ´Ù.
+ +
- (%l)
+ +
Ãâ·Â¿¡¼­ "»©±â±âÈ£"´Â ¿äûÇÑ Á¤º¸°¡ ¾øÀ½À» ³ªÅ¸³½´Ù. + ÀÌ °æ¿ì ¿©±â¿¡ ³ª¿Ã Á¤º¸´Â Ŭ¶óÀ̾ðÆ® ÄÄÇ»ÅÍÀÇ + identd°¡ Á¦°øÇÒ Å¬¶óÀ̾ðÆ®ÀÇ RFC 1413 + ½Å¿øÀÌ´Ù. ÀÌ Á¤º¸´Â ¸Å¿ì ¹ÏÀ» ¼ö ¾ø±â¶§¹®¿¡, ±ä¹ÐÈ÷ + °ü¸®µÇ´Â ³»ºÎ ³×Æ®¿÷ÀÌ ¾Æ´Ï¶ó¸é Àý´ë·Î ÀÌ Á¤º¸¸¦ »ç¿ëÇϸé + ¾ÈµÈ´Ù. IdentityCheck°¡ + OnÀÌ ¾Æ´Ï¶ó¸é ¾ÆÆÄÄ¡ À¥¼­¹ö´Â ÀÌ Á¤º¸¸¦ + ¾Ë¾Æº¸·Á°í ½ÃµµÇÏÁöµµ ¾Ê´Â´Ù.
+ +
frank (%u)
+ +
ÀÌ´Â HTTP ÀÎÁõÀ¸·Î ¾Ë¾Æ³½ ¹®¼­¸¦ ¿äûÇÑ »ç¿ëÀÚÀÇ + useridÀÌ´Ù. º¸Åë ÀÌ °ªÀº CGI ½ºÅ©¸³Æ®¿¡°Ô + REMOTE_USER ȯ°æº¯¼ö·Î ³Ñ°ÜÁø´Ù. ¿äûÀÇ + »óÅÂÄڵ尡 401À̶ó¸é (¾Æ·¡ Âü°í) »ç¿ëÀÚ°¡ ¾ÆÁ÷ ÀÎÁõÀ» + °ÅÄ¡Áö ¾Ê¾ÒÀ¸¹Ç·Î ÀÌ °ªÀ» ¹ÏÀ¸¸é ¾ÈµÈ´Ù. ¹®¼­¸¦ ¾ÏÈ£·Î + º¸È£ÇÏÁö ¾Ê´Â´Ù¸é ÀÌ Ç׸ñÀº ÀÌÀü Ç׸ñ°ú °°ÀÌ + "-"ÀÌ´Ù.
+ +
[10/Oct/2000:13:55:36 -0700] + (%t)
+ +
+ ¼­¹ö°¡ ¿äû󸮸¦ ¸¶Ä£ ½Ã°£. + Çü½ÄÀº: + +

+ [day/month/year:hour:minute:second zone]
+ day = ¼ýÀÚ 2°³
+ month = ¼ýÀÚ 3°³
+ year = ¼ýÀÚ 4°³
+ hour = ¼ýÀÚ 2°³
+ minute = ¼ýÀÚ 2°³
+ second = ¼ýÀÚ 2°³
+ zone = (`+' | `-') ¼ýÀÚ 4°³ +

+ ·Î±× Çü½Ä¹®ÀÚ¿­¿¡ %{format}t¸¦ »ç¿ëÇÏ¿© + ´Ù¸¥ Çü½ÄÀ¸·Î ½Ã°£À» Ãâ·ÂÇÒ ¼ö ÀÖ´Ù. formatÀº + C Ç¥ÁØ ¶óÀ̺귯¸®ÀÇ strftime(3)°ú °°´Ù. +
+ +
"GET /apache_pb.gif HTTP/1.0" + (\"%r\")
+ +
Ŭ¶óÀ̾ðÆ®ÀÇ ¿äûÁÙÀÌ ½Öµû¿ÈÇ¥·Î ¹­¿©ÀÖ´Ù. ¿äûÁÙÀº + ¸Å¿ì À¯¿ëÇÑ Á¤º¸¸¦ ´ã°í ÀÖ´Ù. ù°, Ŭ¶óÀ̾ðÆ®°¡ »ç¿ëÇÑ + ¸Þ½áµå´Â GETÀÌ´Ù. µÑ°, Ŭ¶óÀ̾ðÆ®´Â ÀÚ¿ø + /apache_pb.gif¸¦ ¿äûÇÑ´Ù. ¼¼¹ø°, Ŭ¶óÀ̾ðÆ®´Â + HTTP/1.0 ÇÁ·ÎÅäÄÝÀ» »ç¿ëÇÑ´Ù. ¿äûÁÙÀÇ + ¿©·¯ ºÎºÐÀ» µû·Î ·Î±×ÇÒ ¼öµµ ÀÖ´Ù. ¿¹¸¦ µé¾î, Çü½Ä¹®ÀÚ¿­ + "%m %U%q %H"Àº "%r"°ú ¶È°°ÀÌ + ¸Þ½áµå, °æ·Î, ÁúÀǹ®ÀÚ¿­, ÇÁ·ÎÅäÄÝÀ» ·Î±×ÇÑ´Ù.
+ +
200 (%>s)
+ +
ÀÌ´Â ¼­¹ö°¡ Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³»´Â »óÅÂÄÚµåÀÌ´Ù. ÀÌ + Á¤º¸´Â (2·Î ½ÃÀÛÇÏ´Â ÄÚµå) ¿äûÀÌ ¼º°øÇÏ¿´´ÂÁö, (4·Î + ½ÃÀÛÇÏ´Â ÄÚµå) Ŭ¶óÀ̾ðÆ®¿¡ ¿À·ù°¡ ÀÖ´ÂÁö, (5·Î ½ÃÀÛÇÏ´Â + ÄÚµå) ¼­¹ö¿¡ ¿À·ù°¡ ÀÖ´ÂÁö ¾Ë·ÁÁֹǷΠ¸Å¿ì Áß¿äÇÏ´Ù. + »óÅÂÄÚµåÀÇ Àüü ¸ñ·ÏÀº HTTP + ±Ô¾à (RFC2616 section 10)¿¡¼­ ãÀ» ¼ö ÀÖ´Ù.
+ +
2326 (%b)
+ +
¸¶Áö¸· Ç׸ñÀº ÀÀ´ä Çì´õ¸¦ Á¦¿ÜÇÏ°í Ŭ¶óÀ̾ðÆ®¿¡°Ô + º¸³»´Â ³»¿ëÀÇ Å©±â¸¦ ³ªÅ¸³½´Ù. Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³»´Â + ³»¿ëÀÌ ¾ø´Ù¸é ÀÌ °ªÀº "-"ÀÌ´Ù. ³»¿ëÀÌ + ¾ø´Â °æ¿ì "0"À» ·Î±×ÇÏ·Á¸é ´ë½Å + %B¸¦ »ç¿ëÇÑ´Ù.
+
+ + +

Combined ·Î±× Çü½Ä

+ + +

ÀÚÁÖ »ç¿ëµÇ´Â ´Ù¸¥ Çü½Ä¹®ÀÚ¿­Àº °áÇյȷα×Çü½Ä(Combined + Log Format)ÀÌ´Ù. ´ÙÀ½°ú °°ÀÌ »ç¿ëÇÑ´Ù.

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\"" combined
+ CustomLog log/access_log combined +

+ +

ÀÌ Çü½ÄÀº µÎ Ç׸ñÀ» ´õ Ãß°¡ÇÑ °ÍÀ» Á¦¿ÜÇÏ°í´Â Common + ·Î±× Çü½Ä°ú ¿ÏÀüÈ÷ °°´Ù. Ãß°¡µÈ Ç׸ñµéÀº ÆÛ¼¾Æ® Áö½Ã¾î + %{header}i¸¦ »ç¿ëÇÑ´Ù. ¿©±â¼­ + header ÀÚ¸®¿¡ HTTP ¿äû Çì´õ À̸§ÀÌ ³ª¿Ã ¼ö + ÀÖ´Ù. ÀÌ Çü½ÄÀÇ Á¢±Ù ·Î±×´Â ´ÙÀ½°ú °°´Ù:

+ +

+ 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET + /apache_pb.gif HTTP/1.0" 200 2326 + "http://www.example.com/start.html" "Mozilla/4.08 [en] + (Win98; I ;Nav)" +

+ +

Ãß°¡µÈ Ç׸ñÀº:

+ +
+
"http://www.example.com/start.html" + (\"%{Referer}i\")
+ +
"Referer" (¸ÂÃã¹ý Ʋ¸®Áö¾Ê¾ÒÀ½) HTTP ¿äû Çì´õ. + Ŭ¶óÀ̾ðÆ®°¡ ÂüÁ¶Çß´Ù°í ¼­¹ö¿¡°Ô ¾Ë¸° »çÀÌÆ®ÀÌ´Ù. + (Áï, /apache_pb.gif¸¦ ¸µÅ©ÇÏ¿´°Å³ª Æ÷ÇÔÇÑ + »çÀÌÆ®ÀÌ´Ù.)
+ +
"Mozilla/4.08 [en] (Win98; I ;Nav)" + (\"%{User-agent}i\")
+ +
User-Agent HTTP ¿äû Çì´õ. Ŭ¶óÀ̾ðÆ® ºê¶ó¿ìÀú°¡ + Àڽſ¡ ´ëÇØ ¾Ë¸®´Â ½Äº°Á¤º¸ÀÌ´Ù.
+
+ + +

¿©·¯ Á¢±Ù ·Î±×

+ + +

¼³Á¤ÆÄÀÏ¿¡ ¿©·¯ CustomLog Áö½Ã¾î¸¦ + »ç¿ëÇϸé Á¢±Ù ·Î±×°¡ ¿©·¯°³ ¸¸µé¾îÁø´Ù. ¿¹¸¦ µé¾î, ´ÙÀ½ + ¼³Á¤Àº ¼¼°¡Áö Á¢±Ù ·Î±×¸¦ ¸¸µç´Ù. ù¹ø°´Â ±âº» CLF Á¤º¸¸¦ + ±â·ÏÇÏ°í, µÎ¹ø°¿Í ¼¼¹ø°´Â referer¿Í ºê¶ó¿ìÀú Á¤º¸¸¦ + ±â·ÏÇÑ´Ù. ¸¶Áö¸· µÎ CustomLog ÁÙÀº ¾î¶»°Ô + ÀÌÀü ReferLog¿Í AgentLog Áö½Ã¾îÀÇ + ±â´ÉÀ» Èä³»³¾ ¼ö ÀÖ´ÂÁö º¸¿©ÁØ´Ù.

+ +

+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common
+ CustomLog logs/referer_log "%{Referer}i -> %U"
+ CustomLog logs/agent_log "%{User-agent}i" +

+ +

¶Ç, ÀÌ ¿¹´Â LogFormatÀ¸·Î ¹Ýµå½Ã + º°¸íÀ» Á¤ÀÇÇÒ ÇÊ¿ä´Â ¾øÀ½À» º¸¿©ÁØ´Ù. ´ë½Å CustomLog Áö½Ã¾î¿¡ + Á÷Á¢ ·Î±× Çü½ÄÀ» ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ + +

Á¶°ÇºÎ ·Î±×

+ + +

Ŭ¶óÀ̾ðÆ® ¿äûÀÇ ¼º°Ý¿¡ µû¶ó ÇØ´ç Ç׸ñÀ» Á¢±Ù ·Î±×¿¡ + ±â·ÏÇÏÁö¾Ê°í ½ÍÀ» ¶§°¡ ÀÖ´Ù. ȯ°æº¯¼ö¸¦ + »ç¿ëÇÏ¸é ½±°Ô ÇØ°áµÈ´Ù. ¸ÕÀú, Ŭ¶óÀ̾ðÆ®°¡ ƯÁ¤ Á¶°ÇÀ» + ¸¸Á·Çϸé ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù. ÀÌ ÀÛ¾÷¿¡´Â º¸Åë SetEnvIf¸¦ »ç¿ëÇÑ´Ù. + ±×¸®°í CustomLog + Áö½Ã¾î¿¡ env=À» »ç¿ëÇÏ¿© ȯ°æº¯¼ö À¯¹«¿¡ + µû¶ó ¿äûÀ» Áý¾î³Ö°Å³ª »«´Ù. ¿¹¸¦ µé¸é:

+ +

+ # loop-back ÀÎÅÍÆäÀ̽º¿¡¼­ ¿äûÀ» Ç¥½ÃÇÑ´Ù
+ SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog
+ # robots.txt ÆÄÀÏ¿¡ ´ëÇÑ ¿äûÀ» Ç¥½ÃÇÑ´Ù
+ SetEnvIf Request_URI "^/robots\.txt$" dontlog
+ # ³ª¸ÓÁö¸¦ ·Î±×¿¡ ³²±ä´Ù
+ CustomLog logs/access_log common env=!dontlog +

+ +

´Ù¸¥ ¿¹·Î ¿µ¾î±Ç »ç¿ëÀÚÀÇ ¿äû¸¸À» ÇÑ ·Î±×ÆÄÀÏ¿¡ ±â·ÏÇÏ°í, + ºñ¿µ¾î±Ç »ç¿ëÀÚÀÇ ¿äûÀº ´Ù¸¥ ·Î±×ÆÄÀÏ¿¡ ±â·ÏÇÏ´Â °æ¿ì¸¦ + »ý°¢Çغ¸ÀÚ.

+ +

+ SetEnvIf Accept-Language "en" english
+ CustomLog logs/english_log common env=english
+ CustomLog logs/non_english_log common env=!english +

+ +

Á¶°ÇºÎ ·Î±×´Â ¸Å¿ì °­·ÂÇÏ°í À¯¿¬ÇÏÁö¸¸, ÀÌ°ÍÀÌ ·Î±× + ³»¿ëÀ» Á¶ÀýÇÏ´Â À¯ÀÏÇÑ ¹æ¹ýÀº ¾Æ´Ï´Ù. ·Î±×ÆÄÀÏÀº ¼­¹öÀÇ + ¸ðµç ÇൿÀ» ±â·ÏÇÒ¶§ ´õ À¯¿ëÇÏ´Ù. ³ªÁß¿¡ ¿øÇÏÁö¾Ê´Â ¿äûÀ» + Á¦¿ÜÇÏ°í ·Î±×ÆÄÀÏÀ» ºÐ¼®ÇÏ´Â °ÍÀÌ ´õ ½±´Ù.

+ +
top
+
+

·Î±× ¼øȯ (Log Rotation)

+ + +

Á¶±Ý ¹Ù»Û ¼­¹öÁ¶Â÷µµ ·Î±×ÆÄÀÏ¿¡ ÀúÀåµÇ´Â Á¤º¸·®Àº ¸Å¿ì + ¸¹´Ù. Á¢¼Ó ·Î±×´Â º¸Åë ¸¸¹ø ¿äû´ç 1MB ÀÌ»ó Áõ°¡ÇÑ´Ù. °á°úÀûÀ¸·Î + ±âÁ¸ÀÇ ·Î±×¸¦ ¿Å±â°Å³ª Áö¿ì´Â ¹æ¹ýÀ¸·Î ·Î±×¸¦ ÁÖ±âÀûÀ¸·Î + ¼øÈ°ÇÒ ÇÊ¿ä°¡ ÀÖ´Ù. ¾ÆÆÄÄ¡´Â ÆÄÀÏÀ» ¿­°íÀÖ´Â µ¿¾È¿¡´Â °è¼Ó + ÀÌÀü ·Î±×ÆÄÀÏ¿¡ ¾²±â¶§¹®¿¡ ¼­¹ö°¡ ½ÇÇàÁßÀ϶§ ·Î±×¸¦ ¼øȯÇÒ + ¼ö ¾ø´Ù. ´ë½Å ·Î±×ÆÄÀÏÀ» ¿Å±â°Å³ª Áö¿îÈÄ ¼­¹ö¸¦ Àç½ÃÀÛÇÏ¿©, ·Î±×ÆÄÀÏÀ» »õ·Î ¿­¾î¾ß + ÇÑ´Ù.

+ +

Á¡ÀÝÀº Àç½ÃÀÛÀ» »ç¿ëÇÏ¸é ¼­¹ö´Â Ŭ¶óÀ̾ðÆ®¿Í + ±âÁ¸ÀÇ È¤Àº ´ë±âµÈ ¿¬°áÀ» ÀÒÁö¾Ê°í »õ ·Î±×ÆÄÀÏÀ» ¿­ ¼ö ÀÖ´Ù. + ±×·¯³ª À̸¦ À§ÇØ ¼­¹ö´Â ¿À·¡µÈ ¿äûÀÇ ¼­ºñ½º¸¦ ³¡³»´Â µ¿¾È + ÀÌÀü ·Î±×ÆÄÀÏÀ» °è¼Ó »ç¿ëÇØ¾ß ÇÑ´Ù. ±×·¯¹Ç·Î Àç½ÃÀÛÇÑÈÄ + ·Î±×ÆÄÀÏÀ» ó¸®Çϱâ Àü¿¡ ¾ó¸¶°£ ±â´Ù¸± ÇÊ¿ä°¡ ÀÖ´Ù. ÀϹÝÀûÀ¸·Î + ´ÙÀ½°ú °°ÀÌ ·Î±×¸¦ ¼øȯÇÏ°í, µð½ºÅ©°ø°£À» Àý¾àÇϱâÀ§ÇØ ÀÌÀü + ·Î±×¸¦ ¾ÐÃàÇÑ´Ù:

+ +

+ mv access_log access_log.old
+ mv error_log error_log.old
+ apachectl graceful
+ sleep 600
+ gzip access_log.old error_log.old +

+ +

·Î±×¸¦ ¼øȯÇÏ´Â ´Ù¸¥ ¹æ¹ýÀº ´ÙÀ½ Àý¿¡¼­ ¼³¸íÇÒ ÆÄÀÌÇÁ ·Î±×¸¦ »ç¿ëÇÏ´Â °ÍÀÌ´Ù.

+
top
+
+

·Î±×¸¦ ÆÄÀÌÇÁ·Î º¸³»±â

+ + +

¾ÆÆÄÄ¡ À¥¼­¹ö´Â ¿À·ù ·Î±×¿Í Á¢±Ù ·Î±×¸¦ ÆÄÀÏ¿¡ Á÷Á¢ + ¾²Áö¾Ê°í ÆÄÀÌÇÁ¸¦ ÅëÇØ ´Ù¸¥ ÇÁ·Î¼¼½º·Î º¸³¾ ¼ö ÀÖ´Ù. ÀÌ + ±â´ÉÀ» »ç¿ëÇÏ¸é ¼­¹ö¿¡ Äڵ带 Ãß°¡ÇÏÁö¾Ê°íµµ ¸Å¿ì À¯¿¬ÇÏ°Ô + ·Î±×¸¦ ó¸®ÇÒ ¼ö ÀÖ´Ù. ·Î±×¸¦ ÆÄÀÌÇÁ¿¡ ¾²±âÀ§ÇØ ÆÄÀϸí + ÀÚ¸®¿¡ ÆÄÀÌÇÁ¹®ÀÚ "|"¿Í µÚ¿¡ Ç¥ÁØÀÔ·ÂÀ¸·Î + ·Î±× Ç׸ñÀ» ÀÐÀ» ½ÇÇàÆÄÀϸíÀ» ÀûÀ¸¸é µÈ´Ù. ¾ÆÆÄÄ¡´Â ¼­¹ö°¡ + ½ÃÀÛÇÒ¶§ ÆÄÀÌÇÁ·Î ¿¬°áÇÒ ·Î±× ÇÁ·Î¼¼½º¸¦ ½ÃÀÛÇÏ°í, ¼­¹ö°¡ + ½ÇÇàµÇ´Â µ¿¾È ÇÁ·Î¼¼½º°¡ Á×À¸¸é ´Ù½Ã ½ÃÀÛÇÑ´Ù. (ÀÌ ¸¶Áö¸· + ±â´É¶§¹®¿¡ ¿ì¸®´Â ÀÌ ¹æ¹ýÀ» "¹ÏÀ» ¼ö ÀÖ´Â ÆÄÀÌÇÁ ·Î±×"¶ó°í + ºÎ¸¥´Ù.)

+ +

ÆÄÀÌÇÁ·Î ¿¬°áµÈ ·Î±× ÇÁ·Î¼¼½º´Â ºÎ¸ð ¾ÆÆÄÄ¡ httpd ÇÁ·Î¼¼½º°¡ + ¶ç¿ì°í, ÇÁ·Î¼¼½ºÀÇ useridµµ °°´Ù. Áï, ÆÄÀÌÇÁ·Î ¿¬°áµÈ ·Î±× + ÇÁ·Î±×·¥Àº º¸Åë root·Î ½ÇÇàµÈ´Ù. ±×·¯¹Ç·Î ÇÁ·Î±×·¥À» °£´ÜÇÏ°í + ¾ÈÀüÇÏ°Ô ¸¸µå´Â °ÍÀÌ ¸Å¿ì Áß¿äÇÏ´Ù.

+ +

ÆÄÀÌÇÁ·Î ºÎ¸£´Â Àüü ¸í·É¾î¸¦ µû¿ÈÇ¥·Î ¹­À½À» ¸í½ÉÇ϶ó. + ÀÌ ¿¹´Â Á¢±Ù ·Î±×¿¡ ´ëÇÑ °ÍÀÌÁö¸¸, ¿À·ù ·Î±×µµ ¸¶Âù°¡Áö´Ù.

+ +

¼­¹ö¸¦ Àç½ÃÀÛÇÏÁö¾Ê°í ·Î±×¸¦ ¼øȯÇÒ ¼ö ÀÖ´Â °ÍÀÌ ÆÄÀÌÇÁ + ·Î±×¸¦ »ç¿ëÇÏ´Â Áß¿äÇÑ ÀÌÀ¯´Ù. ¾ÆÆÄÄ¡ À¥¼­¹ö´Â À̸¦ À§ÇØ + rotatelogs¶ó´Â °£´ÜÇÑ + ÇÁ·Î±×·¥À» Æ÷ÇÔÇÑ´Ù. ¿¹¸¦ µé¾î 24½Ã°£¸¶´Ù ·Î±×¸¦ ¼øȯÇÑ´Ù¸é:

+ +

+ CustomLog "|/usr/local/apache/bin/rotatelogs + /var/log/access_log 86400" common +

+ +

´Ù¸¥ »çÀÌÆ®¿¡ cronolog¶ó´Â ºñ½ÁÇÏÁö¸¸ + ÈξÀ ´õ À¯¿¬ÇÑ ·Î±× ¼øȯ ÇÁ·Î±×·¥ÀÌ ÀÖ´Ù.

+ +

Á¶°ÇºÎ ·Î±×¿Í °°ÀÌ ÆÄÀÌÇÁ ·Î±×´Â ¸Å¿ì °­·ÂÇÑ µµ±¸Áö¸¸, + ³ªÁß¿¡ ó¸®ÇÏ´Â µîÀÇ ´õ °£´ÜÇÑ ¹æ¹ýÀÌ °¡´ÉÇÑ °æ¿ì »ç¿ëÇؼ­´Â + ¾ÈµÈ´Ù.

+
top
+
+

°¡»óÈ£½ºÆ®

+ + +

¸¹Àº °¡»óÈ£½ºÆ®°¡ ÀÖ´Â ¼­¹ö¸¦ + ¿î¿µÇÒ¶§ ¿©·¯°¡Áö ¹æ¹ýÀ¸·Î ·Î±×ÆÄÀÏÀ» ´Ù·ê ¼ö ÀÖ´Ù. ¸ÕÀú, + È£½ºÆ®°¡ ÇÑ°³ÀÎ ¼­¹ö¿Í °°ÀÌ ·Î±×¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù. <VirtualHost> ¼½¼ÇÀÌ + ¾Æ´Ñ ÁÖ¼­¹ö ¼³Á¤¿¡ ·Î±× Áö½Ã¾î¸¦ µÎ¸é ¸ðµç ¿äûÀÌ °°Àº Á¢±Ù + ·Î±×¿Í ¿À·ù ·Î±×·Î ±â·ÏµÈ´Ù. ÀÌ ¹æ¹ýÀº °¡»óÈ£½ºÆ®º°·Î ½±°Ô + Åë°è󸮸¦ ÇÒ ¼ö ¾ø´Ù.

+ +

<VirtualHost> + ¼½¼Ç ¾È¿¡ CustomLog³ª + ErrorLog Áö½Ã¾î¸¦ + »ç¿ëÇϸé ÇØ´ç °¡»óÈ£½ºÆ®¿¡ ´ëÇÑ ¿äû°ú ¿À·ù¸¸ÀÌ ÁöÁ¤µÈ + ÆÄÀÏ¿¡ ±â·ÏµÈ´Ù. ·Î±× Áö½Ã¾î°¡ ¾ø´Â ´Ù¸¥ °¡»óÈ£½ºÆ®´Â °è¼Ó + ÁÖ¼­¹ö ·Î±×¿¡ ·Î±×¸¦ ±â·ÏÇÑ´Ù. ÀÌ ¹æ¹ýÀº °¡»óÈ£½ºÆ® °³¼ö°¡ + ÀûÀ» °æ¿ì ¸Å¿ì À¯¿ëÇÏÁö¸¸, È£½ºÆ® ¼ö°¡ ¸¹´Ù¸é °ü¸®Çϱâ + Èûµé¾îÁø´Ù. ¶Ç, ÆÄÀϱâ¼úÀÚ°¡ + ºÎÁ·ÇÑ ¹®Á¦°¡ ÀÚÁÖ ¹ß»ýÇÑ´Ù.

+ +

Á¢±Ù ·Î±×ÀÇ °æ¿ì ¸Å¿ì ÁÁÀº ÇØ°áÃ¥ÀÌ ÀÖ´Ù. ·Î±× Çü½Ä¹®ÀÚ¿­¿¡ + °¡»óÈ£½ºÆ®¿¡ ´ëÇÑ Á¤º¸¸¦ Ãß°¡ÇÏ¸é ¸ðµç È£½ºÆ®°¡ °°Àº ·Î±×¸¦ + »ç¿ëÇÏ°í, ³ªÁß¿¡ ·Î±×¸¦ °¡»óÈ£½ºÆ®º°·Î ³ª´­ ¼ö ÀÖ´Ù. ¿¹¸¦ + µé¾î, ´ÙÀ½ Áö½Ã¾î¸¦ ºÁ¶ó.

+ +

+ LogFormat "%v %l %u %t \"%r\" %>s %b" + comonvhost
+ CustomLog logs/access_log comonvhost +

+ +

%v´Â ¿äûÀ» ¼­ºñ½ºÇÏ´Â °¡»óÈ£½ºÆ® À̸§À» + ±â·ÏÇÑ´Ù. ³ªÁß¿¡ split-logfile + °°Àº ÇÁ·Î±×·¥À¸·Î Á¢±Ù ·Î±×¸¦ °¡»óÈ£½ºº°·Î ³ª´­ ¼ö ÀÖ´Ù.

+
top
+
+

´Ù¸¥ ·Î±×ÆÄÀÏ

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

PID ÆÄÀÏ

+ + +

¾ÆÆÄÄ¡ À¥¼­¹ö´Â ½ÃÀÛÇÒ¶§ logs/httpd.pid + ÆÄÀÏ¿¡ ºÎ¸ð httpd ÇÁ·Î¼¼½ºÀÇ process id¸¦ ÀúÀåÇÑ´Ù. ÀÌ + ÆÄÀϸíÀº PidFile + Áö½Ã¾î·Î º¯°æÇÒ ¼ö ÀÖ´Ù. process-id´Â °ü¸®ÀÚ°¡ ºÎ¸ð ÇÁ·Î¼¼½º¿¡ + ½Ã±×³ÎÀ» º¸³» ¼­¹ö¸¦ Àç½ÃÀÛÇϰųª Á×À϶§ »ç¿ëÇÑ´Ù. + À©µµ¿ìÁî¿¡¼­´Â ´ë½Å -k ¸í·ÉÇà¿É¼ÇÀ» »ç¿ëÇÑ´Ù. ´õ ÀÚ¼¼ÇÑ + Á¤º¸´Â Áß´Ü°ú Àç½ÃÀÛ ÆäÀÌÁö¸¦ + Âü°íÇ϶ó.

+ + +

½ºÅ©¸³Æ® ·Î±×

+ + +

µð¹ö±ëÀ» µ½±âÀ§ÇØ ScriptLog Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + CGI ½ºÅ©¸³Æ®ÀÇ ÀԷ°ú Ãâ·ÂÀ» ±â·ÏÇÒ ¼ö ÀÖ´Ù. ÀÌ Áö½Ã¾î´Â + ¿ÀÁ÷ Å×½ºÆ®¿ëÀ¸·Î¸¸ »ç¿ëÇØ¾ß ÇÑ´Ù. ½ÇÁ¦ »ç¿ëÇÏ´Â ¼­¹ö¿¡¼­ + »ç¿ëÇÏ¸é ¾ÈµÈ´Ù. ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â mod_cgi ¹®¼­¸¦ Âü°íÇ϶ó.

+ + +

ÀçÀÛ¼º ·Î±×

+ + +

mod_rewriteÀÇ °­·ÂÇÏ°í + º¹ÀâÇÑ ±â´ÉÀ» »ç¿ëÇÑ´Ù¸é µð¹ö±ëÀ» À§ÇØ °ÅÀÇ Ç×»ó RewriteLog¸¦ »ç¿ëÇÒ ÇÊ¿ä°¡ + ÀÖ´Ù. ÀÌ ·Î±×ÆÄÀÏÀº ÀçÀÛ¼º ¿£ÁøÀÌ ¾î¶»°Ô ¿äûÀ» º¯È¯ÇÏ´ÂÁö¿¡ + ´ëÇØ ÀÚ¼¼È÷ ¾Ë·ÁÁØ´Ù. ÀÚ¼¼ÇÑ Á¤µµ´Â RewriteLogLevel Áö½Ã¾î·Î + Á¶ÀýÇÑ´Ù.

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/misc/index.html b/docs/manual/misc/index.html new file mode 100644 index 00000000..5b7bb86f --- /dev/null +++ b/docs/manual/misc/index.html @@ -0,0 +1,7 @@ +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/misc/index.html.en b/docs/manual/misc/index.html.en new file mode 100644 index 00000000..bc8e2e97 --- /dev/null +++ b/docs/manual/misc/index.html.en @@ -0,0 +1,80 @@ + + + +Apache Miscellaneous Documentation - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Apache Miscellaneous Documentation

+
+

Available Languages:  en  | + ko 

+
+ + +

Below is a list of additional documentation pages that apply + to the Apache web server development project.

+ +

Warning

+

The documents below have not been fully updated + to take into account changes made in the 2.1 version of the + Apache HTTP Server. Some of the information may still be + relevant, but please use it with care.

+
+ +
+
Performance Notes - Apache + Tuning
+ +
+

Notes about how to (run-time and compile-time) configure + Apache for highest performance. Notes explaining why Apache + does some things, and why it doesn't do other things (which + make it slower/faster).

+
+ +
Security Tips
+ +
+

Some "do"s - and "don't"s - for keeping your Apache web + site secure.

+
+ +
URL Rewriting Guide
+ +
+

This document supplements the mod_rewrite + reference documentation. + It describes how one can use Apache's mod_rewrite + to solve typical URL-based problems webmasters are usually confronted + with in practice.

+
+ +
Relevant Standards
+ +
+

This document acts as a reference page for most of the relevant + standards that Apache follows.

+
+
+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/misc/index.html.ko.euc-kr b/docs/manual/misc/index.html.ko.euc-kr new file mode 100644 index 00000000..d497a6c1 --- /dev/null +++ b/docs/manual/misc/index.html.ko.euc-kr @@ -0,0 +1,76 @@ + + + +±âŸ ¾ÆÆÄÄ¡ ¹®¼­ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

±âŸ ¾ÆÆÄÄ¡ ¹®¼­

+
+

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

+
+ + +

¾Æ·¡´Â ¾ÆÆÄÄ¡ À¥¼­¹ö °³¹ß ÇÁ·ÎÁ§Æ®¿¡ ´ëÇÑ Ãß°¡ ¹®¼­ + ¸ñ·ÏÀÌ´Ù.

+ +

ÁÖÀÇ

+

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

+
+ +
+
¾ÆÆÄÄ¡ ¼º´ÉÇâ»ó
+ +
+

ÃÖ°íÀÇ ¼º´ÉÀ» ³»±âÀ§ÇØ ¾ÆÆÄÄ¡¸¦ (½ÇÇà½Ã, ÄÄÆÄÀϽÃ) + ¼³Á¤ÇÏ´Â ¹æ¹ýÀ» ´Ù·é´Ù. ¾ÆÆÄÄ¡°¡ ¿Ö ¾î¶² ÀÛ¾÷À» ÇÏ°í + (¾ÆÆÄÄ¡¸¦ ´À¸®°Å³ª ºü¸£°Ô ¸¸µå´Â) ¾î¶² ÀÛ¾÷À» ÇÏÁö ¾Ê´ÂÁö + ¼³¸íÇÑ´Ù.

+
+ +
º¸¾È ÆÁ
+ +
+

¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ¾ÈÀüÇÏ°Ô À¯ÁöÇϱâÀ§ÇØ "ÇÒ ÀÏ"°ú "ÇÏÁö + ¸»¾Æ¾ß ÇÒ ÀÏ".

+
+ +
URL ÀçÀÛ¼º Áöħ¼­
+ +
+

ÀÌ ¹®¼­´Â mod_rewrite ÂüÁ¶ ¹®¼­¸¦ º¸ÃæÇÑ´Ù. + ÀÌ ¹®¼­´Â À¥°ü¸®ÀÚ°¡ ½ÇÁ¦ ÀÛ¾÷¿¡¼­ ºÎµúÄ¡°ÔµÇ´Â ÀüÇüÀûÀÎ + URL°ü·Ã ¹®Á¦¸¦ ÇØ°áÇϱâÀ§Çؼ­ ¾î¶»°Ô ¾ÆÆÄÄ¡ + mod_rewrite¸¦ »ç¿ëÇÏ´ÂÁö ¼³¸íÇÑ´Ù.

+
+ +
°ü·Ã Ç¥ÁØ
+ +
+

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡°¡ µû¸£´Â °ü·Ã Ç¥ÁصéÀ» ¿­°ÅÇÑ´Ù.

+
+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/misc/perf-tuning.html b/docs/manual/misc/perf-tuning.html new file mode 100644 index 00000000..5eaaf715 --- /dev/null +++ b/docs/manual/misc/perf-tuning.html @@ -0,0 +1,7 @@ +URI: perf-tuning.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: perf-tuning.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/misc/perf-tuning.html.en b/docs/manual/misc/perf-tuning.html.en new file mode 100644 index 00000000..73f9eab0 --- /dev/null +++ b/docs/manual/misc/perf-tuning.html.en @@ -0,0 +1,1056 @@ + + + +Apache Performance Tuning - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Miscellaneous Documentation

Apache Performance Tuning

+
+

Available Languages:  en  | + ko 

+
+ + +

Apache 2.0 is a general-purpose webserver, designed to + provide a balance of flexibility, portability, and performance. + Although it has not been designed specifically to set benchmark + records, Apache 2.0 is capable of high performance in many + real-world situations.

+ +

Compared to Apache 1.3, release 2.0 contains many additional + optimizations to increase throughput and scalability. Most of + these improvements are enabled by default. However, there are + compile-time and run-time configuration choices that can + significantly affect performance. This document describes the + options that a server administrator can configure to tune the + performance of an Apache 2.0 installation. Some of these + configuration options enable the httpd to better take advantage + of the capabilities of the hardware and OS, while others allow + the administrator to trade functionality for speed.

+ +
+ +
top
+
+

Hardware and Operating System Issues

+ + + +

The single biggest hardware issue affecting webserver + performance is RAM. A webserver should never ever have to swap, + as swapping increases the latency of each request beyond a point + that users consider "fast enough". This causes users to hit + stop and reload, further increasing the load. You can, and + should, control the MaxClients setting so that your server + does not spawn so many children it starts swapping. This procedure + for doing this is simple: determine the size of your average Apache + process, by looking at your process list via a tool such as + top, and divide this into your total available memory, + leaving some room for other processes.

+ +

Beyond that the rest is mundane: get a fast enough CPU, a + fast enough network card, and fast enough disks, where "fast + enough" is something that needs to be determined by + experimentation.

+ +

Operating system choice is largely a matter of local + concerns. But some guidelines that have proven generally + useful are:

+ +
    +
  • +

    Run the latest stable release and patchlevel of the + operating system that you choose. Many OS suppliers have + introduced significant performance improvements to their + TCP stacks and thread libraries in recent years.

    +
    • + +
  • +

    If your OS supports a sendfile(2) system + call, make sure you install the release and/or patches + needed to enable it. (With Linux, for example, this means + using Linux 2.4 or later. For early releases of Solaris 8, + you may need to apply a patch.) On systems where it is + available, sendfile enables Apache 2 to deliver + static content faster and with lower CPU utilization.

    +
    • +
+ +
top
+
+

Run-Time Configuration Issues

+ + + +
Related ModulesRelated Directives
+ +

HostnameLookups and other DNS considerations

+ + + +

Prior to Apache 1.3, HostnameLookups defaulted to On. + This adds latency to every request because it requires a + DNS lookup to complete before the request is finished. In + Apache 1.3 this setting defaults to Off. If you need + to have addresses in your log files resolved to hostnames, use the + logresolve + program that comes with Apache, or one of the numerous log + reporting packages which are available.

+ +

It is recommended that you do this sort of postprocessing of + your log files on some machine other than the production web + server machine, in order that this activity not adversely affect + server performance.

+ +

If you use any Allow + from domain or Deny from domain + directives (i.e., using a hostname, or a domain name, rather than + an IP address) then you will pay for + a double reverse DNS lookup (a reverse, followed by a forward + to make sure that the reverse is not being spoofed). For best + performance, therefore, use IP addresses, rather than names, when + using these directives, if possible.

+ +

Note that it's possible to scope the directives, such as + within a <Location /server-status> section. + In this case the DNS lookups are only performed on requests + matching the criteria. Here's an example which disables lookups + except for .html and .cgi files:

+ +

+ HostnameLookups off
+ <Files ~ "\.(html|cgi)$">
+ + HostnameLookups on
+ + </Files> +

+ +

But even still, if you just need DNS names in some CGIs you + could consider doing the gethostbyname call in the + specific CGIs that need it.

+ + + +

FollowSymLinks and SymLinksIfOwnerMatch

+ + + +

Wherever in your URL-space you do not have an Options + FollowSymLinks, or you do have an Options + SymLinksIfOwnerMatch Apache will have to issue extra + system calls to check up on symlinks. One extra call per + filename component. For example, if you had:

+ +

+ DocumentRoot /www/htdocs
+ <Directory />
+ + Options SymLinksIfOwnerMatch
+ + </Directory> +

+ +

and a request is made for the URI /index.html. + Then Apache will perform lstat(2) on + /www, /www/htdocs, and + /www/htdocs/index.html. The results of these + lstats are never cached, so they will occur on + every single request. If you really desire the symlinks + security checking you can do something like this:

+ +

+ DocumentRoot /www/htdocs
+ <Directory />
+ + Options FollowSymLinks
+ + </Directory>
+
+ <Directory /www/htdocs>
+ + Options -FollowSymLinks +SymLinksIfOwnerMatch
+ + </Directory> +

+ +

This at least avoids the extra checks for the + DocumentRoot path. + Note that you'll need to add similar sections if you + have any Alias or + RewriteRule paths + outside of your document root. For highest performance, + and no symlink protection, set FollowSymLinks + everywhere, and never set SymLinksIfOwnerMatch.

+ + + +

AllowOverride

+ + + +

Wherever in your URL-space you allow overrides (typically + .htaccess files) Apache will attempt to open + .htaccess for each filename component. For + example,

+ +

+ DocumentRoot /www/htdocs
+ <Directory />
+ + AllowOverride all
+ + </Directory> +

+ +

and a request is made for the URI /index.html. + Then Apache will attempt to open /.htaccess, + /www/.htaccess, and + /www/htdocs/.htaccess. The solutions are similar + to the previous case of Options FollowSymLinks. + For highest performance use AllowOverride None + everywhere in your filesystem.

+ + + +

Negotiation

+ + + +

If at all possible, avoid content-negotiation if you're + really interested in every last ounce of performance. In + practice the benefits of negotiation outweigh the performance + penalties. There's one case where you can speed up the server. + Instead of using a wildcard such as:

+ +

+ DirectoryIndex index +

+ +

Use a complete list of options:

+ +

+ DirectoryIndex index.cgi index.pl index.shtml index.html +

+ +

where you list the most common choice first.

+ +

Also note that explicitly creating a type-map + file provides better performance than using + MultiViews, as the necessary information can be + determined by reading this single file, rather than having to + scan the directory for files.

+ +

If your site needs content negotiation consider using + type-map files, rather than the Options + MultiViews directive to accomplish the negotiation. See the + Content Negotiation + documentation for a full discussion of the methods of negotiation, + and instructions for creating type-map files.

+ + + +

Memory-mapping

+ + + +

In situations where Apache 2.0 needs to look at the contents + of a file being delivered--for example, when doing server-side-include + processing--it normally memory-maps the file if the OS supports + some form of mmap(2).

+ +

On some platforms, this memory-mapping improves performance. + However, there are cases where memory-mapping can hurt the performance + or even the stability of the httpd:

+ +
    +
  • +

    On some operating systems, mmap does not scale + as well as read(2) when the number of CPUs increases. + On multiprocessor Solaris servers, for example, Apache 2.0 sometimes + delivers server-parsed files faster when mmap is disabled.

    +
    • + +
  • +

    If you memory-map a file located on an NFS-mounted filesystem + and a process on another NFS client machine deletes or truncates + the file, your process may get a bus error the next time it tries + to access the mapped file content.

    +
    • +
+ +

For installations where either of these factors applies, you + should use EnableMMAP off to disable the memory-mapping + of delivered files. (Note: This directive can be overridden on + a per-directory basis.)

+ + + +

Sendfile

+ + + +

In situations where Apache 2.0 can ignore the contents of the file + to be delivered -- for example, when serving static file content -- + it normally uses the kernel sendfile support the file if the OS + supports the sendfile(2) operation.

+ +

On most platforms, using sendfile improves performance by eliminating + separate read and send mechanics. However, there are cases where using + sendfile can harm the stability of the httpd:

+ +
    +
  • +

    Some platforms may have broken sendfile support that the build + system did not detect, especially if the binaries were built on + another box and moved to such a machine with broken sendfile support.

    +
    • +
  • +

    With an NFS-mounted files, the kernel may be unable + to reliably serve the network file through it's own cache.

    +
    • +
+ +

For installations where either of these factors applies, you + should use EnableSendfile off to disable sendfile + delivery of file contents. (Note: This directive can be overridden + on a per-directory basis.)

+ + + +

Process Creation

+ + + +

Prior to Apache 1.3 the MinSpareServers, MaxSpareServers, and StartServers settings all had drastic effects on + benchmark results. In particular, Apache required a "ramp-up" + period in order to reach a number of children sufficient to serve + the load being applied. After the initial spawning of + StartServers children, + only one child per second would be created to satisfy the + MinSpareServers + setting. So a server being accessed by 100 simultaneous + clients, using the default StartServers of 5 would take on + the order 95 seconds to spawn enough children to handle + the load. This works fine in practice on real-life servers, + because they aren't restarted frequently. But does really + poorly on benchmarks which might only run for ten minutes.

+ +

The one-per-second rule was implemented in an effort to + avoid swamping the machine with the startup of new children. If + the machine is busy spawning children it can't service + requests. But it has such a drastic effect on the perceived + performance of Apache that it had to be replaced. As of Apache + 1.3, the code will relax the one-per-second rule. It will spawn + one, wait a second, then spawn two, wait a second, then spawn + four, and it will continue exponentially until it is spawning + 32 children per second. It will stop whenever it satisfies the + MinSpareServers + setting.

+ +

This appears to be responsive enough that it's almost + unnecessary to twiddle the MinSpareServers, MaxSpareServers and StartServers knobs. When more than 4 children are + spawned per second, a message will be emitted to the + ErrorLog. If you + see a lot of these errors then consider tuning these settings. + Use the mod_status output as a guide.

+ +

Related to process creation is process death induced by the + MaxRequestsPerChild + setting. By default this is 0, + which means that there is no limit to the number of requests + handled per child. If your configuration currently has this set + to some very low number, such as 30, you may want to bump this + up significantly. If you are running SunOS or an old version of + Solaris, limit this to 10000 or so because of memory leaks.

+ +

When keep-alives are in use, children will be kept busy + doing nothing waiting for more requests on the already open + connection. The default KeepAliveTimeout of 5 + seconds attempts to minimize this effect. The tradeoff here is + between network bandwidth and server resources. In no event + should you raise this above about 60 seconds, as + most of the benefits are lost.

+ + + +
top
+
+

Compile-Time Configuration Issues

+ + + +

Choosing an MPM

+ + + +

Apache 2.x supports pluggable concurrency models, called + Multi-Processing Modules (MPMs). + When building Apache, you must choose an MPM to use. There + are platform-specific MPMs for some platforms: + beos, mpm_netware, + mpmt_os2, and mpm_winnt. For + general Unix-type systems, there are several MPMs from which + to choose. The choice of MPM can affect the speed and scalability + of the httpd:

+ +
    + +
  • The worker MPM uses multiple child + processes with many threads each. Each thread handles + one connection at a time. Worker generally is a good + choice for high-traffic servers because it has a smaller + memory footprint than the prefork MPM.
    • + +
  • The prefork MPM uses multiple child + processes with one thread each. Each process handles + one connection at a time. On many systems, prefork is + comparable in speed to worker, but it uses more memory. + Prefork's threadless design has advantages over worker + in some situations: it can be used with non-thread-safe + third-party modules, and it is easier to debug on platforms + with poor thread debugging support.
    • + +
+ +

For more information on these and other MPMs, please + see the MPM documentation.

+ + + +

Modules

+ + + +

Since memory usage is such an important consideration in + performance, you should attempt to eliminate modules that youare + not actually using. If you have built the modules as DSOs, eliminating modules is a simple + matter of commenting out the associated LoadModule directive for that module. + This allows you to experiment with removing modules, and seeing + if your site still functions in their absense.

+ +

If, on the other hand, you have modules statically linked + into your Apache binary, you will need to recompile Apache in + order to remove unwanted modules.

+ +

An associated question that arises here is, of course, what + modules you need, and which ones you don't. The answer here + will, of course, vary from one web site to another. However, the + minimal list of modules which you can get by with tends + to include mod_mime, mod_dir, + and mod_log_config. mod_log_config is, + of course, optional, as you can run a web site without log + files. This is, however, not recommended.

+ + + +

Atomic Operations

+ + + +

Some modules, such as mod_cache and + recent development builds of the worker MPM, use APR's + atomic API. This API provides atomic operations that can + be used for lightweight thread synchronization.

+ +

By default, APR implements these operations using the + most efficient mechanism available on each target + OS/CPU platform. Many modern CPUs, for example, have + an instruction that does an atomic compare-and-swap (CAS) + operation in hardware. On some platforms, however, APR + defaults to a slower, mutex-based implementation of the + atomic API in order to ensure compatibility with older + CPU models that lack such instructions. If you are + building Apache for one of these platforms, and you plan + to run only on newer CPUs, you can select a faster atomic + implementation at build time by configuring Apache with + the --enable-nonportable-atomics option:

+ +

+ ./buildconf
+ ./configure --with-mpm=worker --enable-nonportable-atomics=yes +

+ +

The --enable-nonportable-atomics option is + relevant for the following platforms:

+ +
    + +
  • Solaris on SPARC
    + By default, APR uses mutex-based atomics on Solaris/SPARC. + If you configure with --enable-nonportable-atomics, + however, APR generates code that uses a SPARC v8plus opcode for + fast hardware compare-and-swap. If you configure Apache with + this option, the atomic operations will be more efficient + (allowing for lower CPU utilization and higher concurrency), + but the resulting executable will run only on UltraSPARC + chips. +
    • + +
  • Linux on x86
    + By default, APR uses mutex-based atomics on Linux. If you + configure with --enable-nonportable-atomics, + however, APR generates code that uses a 486 opcode for fast + hardware compare-and-swap. This will result in more efficient + atomic operations, but the resulting executable will run only + on 486 and later chips (and not on 386). +
    • + +
+ + + +

mod_status and ExtendedStatus On

+ + + +

If you include mod_status and you also set + ExtendedStatus On when building and running + Apache, then on every request Apache will perform two calls to + gettimeofday(2) (or times(2) + depending on your operating system), and (pre-1.3) several + extra calls to time(2). This is all done so that + the status report contains timing indications. For highest + performance, set ExtendedStatus off (which is the + default).

+ + + +

accept Serialization - multiple sockets

+ + + +

Warning:

+

This section has not been fully 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.

+
+ +

This discusses a shortcoming in the Unix socket API. Suppose + your web server uses multiple Listen statements to listen on either multiple + ports or multiple addresses. In order to test each socket + to see if a connection is ready Apache uses + select(2). select(2) indicates that a + socket has zero or at least one connection + waiting on it. Apache's model includes multiple children, and + all the idle ones test for new connections at the same time. A + naive implementation looks something like this (these examples + do not match the code, they're contrived for pedagogical + purposes):

+ +

+ for (;;) {
+ + for (;;) {
+ + fd_set accept_fds;
+
+ FD_ZERO (&accept_fds);
+ for (i = first_socket; i <= last_socket; ++i) {
+ + FD_SET (i, &accept_fds);
+ + }
+ rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);
+ if (rc < 1) continue;
+ new_connection = -1;
+ for (i = first_socket; i <= last_socket; ++i) {
+ + if (FD_ISSET (i, &accept_fds)) {
+ + new_connection = accept (i, NULL, NULL);
+ if (new_connection != -1) break;
+ + }
+ + }
+ if (new_connection != -1) break;
+ + }
+ process the new_connection;
+ + } +

+ +

But this naive implementation has a serious starvation problem. + Recall that multiple children execute this loop at the same + time, and so multiple children will block at + select when they are in between requests. All + those blocked children will awaken and return from + select when a single request appears on any socket + (the number of children which awaken varies depending on the + operating system and timing issues). They will all then fall + down into the loop and try to accept the + connection. But only one will succeed (assuming there's still + only one connection ready), the rest will be blocked + in accept. This effectively locks those children + into serving requests from that one socket and no other + sockets, and they'll be stuck there until enough new requests + appear on that socket to wake them all up. This starvation + problem was first documented in PR#467. There + are at least two solutions.

+ +

One solution is to make the sockets non-blocking. In this + case the accept won't block the children, and they + will be allowed to continue immediately. But this wastes CPU + time. Suppose you have ten idle children in + select, and one connection arrives. Then nine of + those children will wake up, try to accept the + connection, fail, and loop back into select, + accomplishing nothing. Meanwhile none of those children are + servicing requests that occurred on other sockets until they + get back up to the select again. Overall this + solution does not seem very fruitful unless you have as many + idle CPUs (in a multiprocessor box) as you have idle children, + not a very likely situation.

+ +

Another solution, the one used by Apache, is to serialize + entry into the inner loop. The loop looks like this + (differences highlighted):

+ +

+ for (;;) {
+ + accept_mutex_on ();
+ for (;;) {
+ + fd_set accept_fds;
+
+ FD_ZERO (&accept_fds);
+ for (i = first_socket; i <= last_socket; ++i) {
+ + FD_SET (i, &accept_fds);
+ + }
+ rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);
+ if (rc < 1) continue;
+ new_connection = -1;
+ for (i = first_socket; i <= last_socket; ++i) {
+ + if (FD_ISSET (i, &accept_fds)) {
+ + new_connection = accept (i, NULL, NULL);
+ if (new_connection != -1) break;
+ + }
+ + }
+ if (new_connection != -1) break;
+ + }
+ accept_mutex_off ();
+ process the new_connection;
+ + } +

+ +

The functions + accept_mutex_on and accept_mutex_off + implement a mutual exclusion semaphore. Only one child can have + the mutex at any time. There are several choices for + implementing these mutexes. The choice is defined in + src/conf.h (pre-1.3) or + src/include/ap_config.h (1.3 or later). Some + architectures do not have any locking choice made, on these + architectures it is unsafe to use multiple + Listen + directives.

+ +

The directive AcceptMutex can be used to + change the selected mutex implementation at run-time.

+ +
+
AcceptMutex flock
+ +
+

This method uses the flock(2) system call to + lock a lock file (located by the LockFile directive).

+
+ +
AcceptMutex fcntl
+ +
+

This method uses the fcntl(2) system call to + lock a lock file (located by the LockFile directive).

+
+ +
AcceptMutex sysvsem
+ +
+

(1.3 or later) This method uses SysV-style semaphores to + implement the mutex. Unfortunately SysV-style semaphores have + some bad side-effects. One is that it's possible Apache will + die without cleaning up the semaphore (see the + ipcs(8) man page). The other is that the + semaphore API allows for a denial of service attack by any + CGIs running under the same uid as the webserver + (i.e., all CGIs, unless you use something like + suexec or cgiwrapper). For these + reasons this method is not used on any architecture except + IRIX (where the previous two are prohibitively expensive + on most IRIX boxes).

+
+ +
AcceptMutex pthread
+ +
+

(1.3 or later) This method uses POSIX mutexes and should + work on any architecture implementing the full POSIX threads + specification, however appears to only work on Solaris (2.5 + or later), and even then only in certain configurations. If + you experiment with this you should watch out for your server + hanging and not responding. Static content only servers may + work just fine.

+
+ +
AcceptMutex posixsem
+ +
+

(2.0 or later) This method uses POSIX semaphores. The + semaphore ownership is not recovered if a thread in the process + holding the mutex segfaults, resulting in a hang of the web + server.

+
+ +
+ +

If your system has another method of serialization which + isn't in the above list then it may be worthwhile adding code + for it to APR.

+ +

Another solution that has been considered but never + implemented is to partially serialize the loop -- that is, let + in a certain number of processes. This would only be of + interest on multiprocessor boxes where it's possible multiple + children could run simultaneously, and the serialization + actually doesn't take advantage of the full bandwidth. This is + a possible area of future investigation, but priority remains + low because highly parallel web servers are not the norm.

+ +

Ideally you should run servers without multiple + Listen + statements if you want the highest performance. + But read on.

+ + + +

accept Serialization - single socket

+ + + +

The above is fine and dandy for multiple socket servers, but + what about single socket servers? In theory they shouldn't + experience any of these same problems because all children can + just block in accept(2) until a connection + arrives, and no starvation results. In practice this hides + almost the same "spinning" behaviour discussed above in the + non-blocking solution. The way that most TCP stacks are + implemented, the kernel actually wakes up all processes blocked + in accept when a single connection arrives. One of + those processes gets the connection and returns to user-space, + the rest spin in the kernel and go back to sleep when they + discover there's no connection for them. This spinning is + hidden from the user-land code, but it's there nonetheless. + This can result in the same load-spiking wasteful behaviour + that a non-blocking solution to the multiple sockets case + can.

+ +

For this reason we have found that many architectures behave + more "nicely" if we serialize even the single socket case. So + this is actually the default in almost all cases. Crude + experiments under Linux (2.0.30 on a dual Pentium pro 166 + w/128Mb RAM) have shown that the serialization of the single + socket case causes less than a 3% decrease in requests per + second over unserialized single-socket. But unserialized + single-socket showed an extra 100ms latency on each request. + This latency is probably a wash on long haul lines, and only an + issue on LANs. If you want to override the single socket + serialization you can define + SINGLE_LISTEN_UNSERIALIZED_ACCEPT and then + single-socket servers will not serialize at all.

+ + + +

Lingering Close

+ + + +

As discussed in + draft-ietf-http-connection-00.txt section 8, in order for + an HTTP server to reliably implement the + protocol it needs to shutdown each direction of the + communication independently (recall that a TCP connection is + bi-directional, each half is independent of the other). This + fact is often overlooked by other servers, but is correctly + implemented in Apache as of 1.2.

+ +

When this feature was added to Apache it caused a flurry of + problems on various versions of Unix because of a + shortsightedness. The TCP specification does not state that the + FIN_WAIT_2 state has a timeout, but it doesn't prohibit it. + On systems without the timeout, Apache 1.2 induces many sockets + stuck forever in the FIN_WAIT_2 state. In many cases this + can be avoided by simply upgrading to the latest TCP/IP patches + supplied by the vendor. In cases where the vendor has never + released patches (i.e., SunOS4 -- although folks with + a source license can patch it themselves) we have decided to + disable this feature.

+ +

There are two ways of accomplishing this. One is the socket + option SO_LINGER. But as fate would have it, this + has never been implemented properly in most TCP/IP stacks. Even + on those stacks with a proper implementation (i.e., + Linux 2.0.31) this method proves to be more expensive (cputime) + than the next solution.

+ +

For the most part, Apache implements this in a function + called lingering_close (in + http_main.c). The function looks roughly like + this:

+ +

+ void lingering_close (int s)
+ {
+ + char junk_buffer[2048];
+
+ /* shutdown the sending side */
+ shutdown (s, 1);
+
+ signal (SIGALRM, lingering_death);
+ alarm (30);
+
+ for (;;) {
+ + select (s for reading, 2 second timeout);
+ if (error) break;
+ if (s is ready for reading) {
+ + if (read (s, junk_buffer, sizeof (junk_buffer)) <= 0) {
+ + break;
+ + }
+ /* just toss away whatever is here */
+ + }
+ + }
+
+ close (s);
+ + } +

+ +

This naturally adds some expense at the end of a connection, + but it is required for a reliable implementation. As HTTP/1.1 + becomes more prevalent, and all connections are persistent, + this expense will be amortized over more requests. If you want + to play with fire and disable this feature you can define + NO_LINGCLOSE, but this is not recommended at all. + In particular, as HTTP/1.1 pipelined persistent connections + come into use lingering_close is an absolute + necessity (and + pipelined connections are faster, so you want to support + them).

+ + + +

Scoreboard File

+ + + +

Apache's parent and children communicate with each other + through something called the scoreboard. Ideally this should be + implemented in shared memory. For those operating systems that + we either have access to, or have been given detailed ports + for, it typically is implemented using shared memory. The rest + default to using an on-disk file. The on-disk file is not only + slow, but it is unreliable (and less featured). Peruse the + src/main/conf.h file for your architecture and + look for either USE_MMAP_SCOREBOARD or + USE_SHMGET_SCOREBOARD. Defining one of those two + (as well as their companions HAVE_MMAP and + HAVE_SHMGET respectively) enables the supplied + shared memory code. If your system has another type of shared + memory, edit the file src/main/http_main.c and add + the hooks necessary to use it in Apache. (Send us back a patch + too please.)

+ +
Historical note: The Linux port of Apache didn't start to + use shared memory until version 1.2 of Apache. This oversight + resulted in really poor and unreliable behaviour of earlier + versions of Apache on Linux.
+ + + +

DYNAMIC_MODULE_LIMIT

+ + + +

If you have no intention of using dynamically loaded modules + (you probably don't if you're reading this and tuning your + server for every last ounce of performance) then you should add + -DDYNAMIC_MODULE_LIMIT=0 when building your + server. This will save RAM that's allocated only for supporting + dynamically loaded modules.

+ + + +
top
+
+

Appendix: Detailed Analysis of a Trace

+ + + +

Here is a system call trace of Apache 2.0.38 with the worker MPM + on Solaris 8. This trace was collected using:

+ +

+ truss -l -p httpd_child_pid. +

+ +

The -l option tells truss to log the ID of the + LWP (lightweight process--Solaris's form of kernel-level thread) + that invokes each system call.

+ +

Other systems may have different system call tracing utilities + such as strace, ktrace, or par. + They all produce similar output.

+ +

In this trace, a client has requested a 10KB static file + from the httpd. Traces of non-static requests or requests + with content negotiation look wildly different (and quite ugly + in some cases).

+ + 
/67:    accept(3, 0x00200BEC, 0x00200C0C, 1) (sleeping...)
+/67:    accept(3, 0x00200BEC, 0x00200C0C, 1)            = 9
+ +

In this trace, the listener thread is running within LWP #67.

+ +
Note the lack of accept(2) serialization. On this + particular platform, the worker MPM uses an unserialized accept by + default unless it is listening on multiple ports.
+ + 
/65:    lwp_park(0x00000000, 0)                         = 0
+/67:    lwp_unpark(65, 1)                               = 0
+ +

Upon accepting the connection, the listener thread wakes up + a worker thread to do the request processing. In this trace, + the worker thread that handles the request is mapped to LWP #65.

+ + 
/65:    getsockname(9, 0x00200BA4, 0x00200BC4, 1)       = 0
+ +

In order to implement virtual hosts, Apache needs to know + the local socket address used to accept the connection. It + is possible to eliminate this call in many situations (such + as when there are no virtual hosts, or when + Listen directives + are used which do not have wildcard addresses). But + no effort has yet been made to do these optimizations.

+ + 
/65:    brk(0x002170E8)                                 = 0
+/65:    brk(0x002190E8)                                 = 0
+ +

The brk(2) calls allocate memory from the heap. + It is rare to see these in a system call trace, because the httpd + uses custom memory allocators (apr_pool and + apr_bucket_alloc) for most request processing. + In this trace, the httpd has just been started, so it must + call malloc(3) to get the blocks of raw memory + with which to create the custom memory allocators.

+ + 
/65:    fcntl(9, F_GETFL, 0x00000000)                   = 2
+/65:    fstat64(9, 0xFAF7B818)                          = 0
+/65:    getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B910, 2190656) = 0
+/65:    fstat64(9, 0xFAF7B818)                          = 0
+/65:    getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B914, 2190656) = 0
+/65:    setsockopt(9, 65535, 8192, 0xFAF7B918, 4, 2190656) = 0
+/65:    fcntl(9, F_SETFL, 0x00000082)                   = 0
+ +

Next, the worker thread puts the connection to the client (file + descriptor 9) in non-blocking mode. The setsockopt(2) + and getsockopt(2) calls are a side-effect of how + Solaris's libc handles fcntl(2) on sockets.

+ + 
/65:    read(9, " G E T   / 1 0 k . h t m".., 8000)     = 97
+ +

The worker thread reads the request from the client.

+ + 
/65:    stat("/var/httpd/apache/httpd-8999/htdocs/10k.html", 0xFAF7B978) = 0
+/65:    open("/var/httpd/apache/httpd-8999/htdocs/10k.html", O_RDONLY) = 10
+ +

This httpd has been configured with Options FollowSymLinks + and AllowOverride None. Thus it doesn't need to + lstat(2) each directory in the path leading up to the + requested file, nor check for .htaccess files. + It simply calls stat(2) to verify that the file: + 1) exists, and 2) is a regular file, not a directory.

+ + 
/65:    sendfilev(0, 9, 0x00200F90, 2, 0xFAF7B53C)      = 10269
+ +

In this example, the httpd is able to send the HTTP response + header and the requested file with a single sendfilev(2) + system call. Sendfile semantics vary among operating systems. On some other + systems, it is necessary to do a write(2) or + writev(2) call to send the headers before calling + sendfile(2).

+ + 
/65:    write(4, " 1 2 7 . 0 . 0 . 1   -  ".., 78)      = 78
+ +

This write(2) call records the request in the + access log. Note that one thing missing from this trace is a + time(2) call. Unlike Apache 1.3, Apache 2.0 uses + gettimeofday(3) to look up the time. On some operating + systems, like Linux or Solaris, gettimeofday has an + optimized implementation that doesn't require as much overhead + as a typical system call.

+ + 
/65:    shutdown(9, 1, 1)                               = 0
+/65:    poll(0xFAF7B980, 1, 2000)                       = 1
+/65:    read(9, 0xFAF7BC20, 512)                        = 0
+/65:    close(9)                                        = 0
+ +

The worker thread does a lingering close of the connection.

+ + 
/65:    close(10)                                       = 0
+/65:    lwp_park(0x00000000, 0)         (sleeping...)
+ +

Finally the worker thread closes the file that it has just delivered + and blocks until the listener assigns it another connection.

+ + 
/67:    accept(3, 0x001FEB74, 0x001FEB94, 1) (sleeping...)
+ +

Meanwhile, the listener thread is able to accept another connection + as soon as it has dispatched this connection to a worker thread (subject + to some flow-control logic in the worker MPM that throttles the listener + if all the available workers are busy). Though it isn't apparent from + this trace, the next accept(2) can (and usually does, under + high load conditions) occur in parallel with the worker thread's handling + of the just-accepted connection.

+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/misc/perf-tuning.html.ko.euc-kr b/docs/manual/misc/perf-tuning.html.ko.euc-kr new file mode 100644 index 00000000..c4ba7013 --- /dev/null +++ b/docs/manual/misc/perf-tuning.html.ko.euc-kr @@ -0,0 +1,976 @@ + + + +¾ÆÆÄÄ¡ ¼º´ÉÇâ»ó - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Miscellaneous Documentation

¾ÆÆÄÄ¡ ¼º´ÉÇâ»ó

+
+

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

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

¾ÆÆÄÄ¡ 2.0Àº ±â´É°ú Æ÷Æð¡´É¼º°ú ¼º´ÉÀÇ ±ÕÇüÀÌ ¸Âµµ·Ï + ¼³°èÇÑ ¹ü¿ë À¥¼­¹öÀÌ´Ù. º¥Ä¡¸¶Å© ±â·ÏÀ» ¼¼¿ì±âÀ§ÇØ ¼³°èÇÏÁö + ¾Ê¾ÒÁö¸¸ ¾ÆÆÄÄ¡ 2.0Àº ½ÇÁ¦ ¸¹Àº °æ¿ì ³ôÀº ¼º´ÉÀ» ³½´Ù.

+ +

¾ÆÆÄÄ¡ 1.3°ú ºñ±³Çؼ­ 2.0 ¹öÀüÀº 󸮷®°ú È®À强(scalability)À» + ³ôÀ̱âÀ§ÇØ ¸¹Àº ÃÖÀûÈ­¸¦ Çß´Ù. ±âº»°ªÀ¸·Î ´ëºÎºÐ ÃÖÀûÈ­ÇÑ + °ªÀ» »ç¿ëÇÑ´Ù. ±×·¯³ª ÄÄÆÄÀϽà ȤÀº ½ÇÇà½Ã ¼³Á¤ÀÌ ¼º´É¿¡ + Å« ¿µÇâÀ» ÁÙ ¼ö ÀÖ´Ù. ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ 2.0ÀÇ ¼º´ÉÀ» Çâ»óÇϱâÀ§ÇØ + ¼­¹ö °ü¸®ÀÚ°¡ ¼³Á¤ÇÒ ¼ö ÀÖ´Â ¿É¼ÇÀ» ¼³¸íÇÑ´Ù. ¾î¶² ¼³Á¤ + ¿É¼ÇÀº À¥¼­¹ö°¡ Çϵå¿þ¾î¿Í ¿î¿µÃ¼Á¦ÀÇ ±â´ÉÀ» ´õ Àß È°¿ëÇϵµ·Ï + ÇÏ´Â ¹Ý¸é, ¾î¶² ¿É¼ÇÀº ¼Óµµ¸¦ À§ÇØ ±â´ÉÀ» Èñ»ýÇÑ´Ù.

+ +
+ +
top
+
+

Çϵå¿þ¾î¿Í ¿î¿µÃ¼Á¦¿¡ ´ëÇؼ­

+ + + +

À¥¼­¹ö ¼º´É¿¡ °¡Àå Å« ¿µÇâÀ» ÁÖ´Â °ÍÀº ¸Þ¸ð¸®´Ù. ½º¿ÒÀº + ¿äû´ç Áö¿¬½Ã°£À» »ç¿ëÀÚ°¡ "ÃæºÐÈ÷ ºü¸£´Ù°í" »ý°¢ÇÏÁö ¸øÇÏ°Ô + ´Ã¸®±â¶§¹®¿¡ À¥¼­¹ö´Â ½º¿ÒÀ» ÇÏ¸é ¾ÈµÈ´Ù. ´À·ÁÁö¸é »ç¿ëÀÚ´Â + Á¤ÁöÇÏ°í ´Ù½Ã Á¢¼ÓÇÏ¿© ºÎÇÏ°¡ °è¼Ó Áõ°¡ÇÑ´Ù. MaxClients Áö½Ã¾î¸¦ Á¶ÀýÇÏ¿© + À¥¼­¹ö°¡ ½º¿ÒÀ» ÇÒ Á¤µµ·Î ¸¹Àº ÀÚ½ÄÀ» ¸¸µéÁö¾Êµµ·Ï ÇØ¾ß + ÇÑ´Ù. ¹æ¹ýÀº °£´ÜÇÏ´Ù: top°ú °°Àº µµ±¸¿¡¼­ + ÇÁ·Î¼¼½º ¸ñ·ÏÀ» º¸°í ¾ÆÆÄÄ¡ ÇÁ·Î¼¼½ºÀÇ Æò±Õ ¸Þ¸ð¸® »ç¿ë·®À» + ¾Ë¾Æ³½ÈÄ, Àüü »ç¿ë°¡´ÉÇÑ ¸Þ¸ð¸®¿¡¼­ ´Ù¸¥ ÇÁ·Î¼¼½ºµéÀÌ »ç¿ëÇÒ + °ø°£À» »« °ª¿¡¼­ ³ª´«´Ù.

+ +

³ª¸ÓÁö´Â Æò¹üÇÏ´Ù: ÃæºÐÈ÷ ºü¸¥ CPU, ÃæºÐÈ÷ ºü¸¥ ³×Æ®¿÷Ä«µå, + ÃæºÐÈ÷ ºü¸¥ µð½ºÅ©, ¿©±â¼­ "ÃæºÐÈ÷ ºü¸¥"Àº ½ÇÇèÀ» Çؼ­ °áÁ¤ÇØ¾ß + ÇÑ´Ù.

+ +

¿î¿µÃ¼Á¦´Â º¸Åë °¢ÀÚ ¾Ë¾Æ¼­ ¼±ÅÃÇÒ ÀÏÀÌ´Ù. ±×·¯³ª ÀϹÝÀûÀ¸·Î + À¯¿ëÇÏ´Ù°í ÆǸíµÈ ¸î°¡Áö ÁöħÀÌ ÀÖ´Ù:

+ +
    +
  • +

    ¼±ÅÃÇÑ ¿î¿µÃ¼Á¦ÀÇ ÃֽŠ¾ÈÁ¤ ¹öÀü°ú ÆÐÄ¡¸¦ ½ÇÇàÇÑ´Ù. + ¸¹Àº ¿î¿µÃ¼Á¦ Á¦ÀÛ»ç´Â ÃÖ±Ù TCP ½ºÅðú ¾²·¹µå ¶óÀ̺귯¸®¿¡ + ¸¹Àº ¼ÓµµÇâ»óÀ» Çß´Ù.

    +
    • + +
  • +

    ¿î¿µÃ¼Á¦°¡ sendfile(2) ½Ã½ºÅÛÈ£ÃâÀ» + Áö¿øÇÑ´Ù¸é, À̸¦ »ç¿ëÇϱâÀ§ÇÑ ¹öÀüÀ̳ª ÆÐÄ¡¸¦ ¼³Ä¡ÇÏ¿´´ÂÁö + È®ÀÎÇÑ´Ù. (¿¹¸¦ µé¾î, ¸®´ª½º¶ó¸é 2.4 ÀÌ»ó ¹öÀüÀ» ¶æÇÑ´Ù. + Solaris 8 Ãʱ⠹öÀüÀº ÆÐÄ¡°¡ ÇÊ¿äÇÏ´Ù.) Áö¿øÇÏ´Â ½Ã½ºÅÛÀ̶ó¸é + ¾ÆÆÄÄ¡ 2´Â sendfileÀ» »ç¿ëÇÏ¿© CPU¸¦ ´ú + »ç¿ëÇϸç Á¤Àû ÆÄÀÏÀ» ´õ »¡¸® Àü¼ÛÇÒ ¼ö ÀÕ´Ù.

    +
    • +
+ +
top
+
+

½ÇÇà½Ã ¼³Á¤¿¡ ´ëÇؼ­

+ + + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

HostnameLookups¿Í DNS¿¡ ´ëÇØ °í·ÁÇÒ Á¡µé

+ + + +

¾ÆÆÄÄ¡ 1.3 ÀÌÀü¿¡ HostnameLookupsÀÇ ±âº»°ªÀº + OnÀÌ¿´´Ù. ¿äûÀ» ¸¶Ä¡±âÀü¿¡ DNS °Ë»öÀÌ ³¡³ª¾ß + ÇϹǷΠ¿äû¸¶´Ù Áö¿¬ÀÌ »ý°å´Ù. ¾ÆÆÄÄ¡ 1.3¿¡¼­ ÀÌ ¼³Á¤ÀÇ + ±âº»°ªÀÌ Off·Î º¯°æµÇ¾ú´Ù. ·Î±×ÆÄÀÏÀÇ ÁÖ¼Ò¸¦ + È£½ºÆ®¸íÀ¸·Î º¯È¯ÇÏ·Á¸é ¿©·¯ ·Î±×ó¸® ÇÁ·Î±×·¥Áß ÇϳªÀÎ, + ¾ÆÆÄÄ¡¿¡ Æ÷ÇÔµÈ logresolve + ÇÁ·Î±×·¥À» »ç¿ëÇ϶ó.

+ +

·Î±×ó¸® ÀÛ¾÷ÀÌ ¼­¹ö ¼º´É¿¡ ¾Ç¿µÇâÀ» ¹ÌÄ¡¹Ç·Î ½ÇÁ¦ + »ç¿ëÇÏ´Â À¥¼­¹ö°¡ ¾Æ´Ñ ´Ù¸¥ ÄÄÇ»ÅÍ¿¡¼­ ·Î±×ÆÄÀÏÀ» ÈÄó¸®Çϱæ + ¹Ù¶õ´Ù.

+ +

Allow + from domainÀ̳ª Deny from domain + Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù¸é (Áï, IP ÁÖ¼Ò°¡ ¾Æ´Ñ È£½ºÆ®¸íÀ̳ª µµ¸ÞÀθíÀ» + »ç¿ëÇÑ´Ù¸é) ºÎµæÀÌ Áߺ¹-¿ª DNS °Ë»öÀ» (¿ª°Ë»öÀ» ÇÑÈÄ ¾ÇÀÇ·Î + º¯°æµÇ¾ú´ÂÁö È®ÀÎÇϱâÀ§ÇØ ´Ù½Ã °Ë»ö) ÇØ¾ß ÇÑ´Ù. ±×·¯¹Ç·Î + ¼º´ÉÀ» ³ôÀ̱âÀ§ÇØ ÀÌ·± Áö½Ã¾î¿¡´Â °¡´ÉÇϸé À̸§´ë½Å IP + ÁÖ¼Ò¸¦ »ç¿ëÇÑ´Ù.

+ +

<Location /server-status> ¼½¼Ç µîÀ¸·Î + Áö½Ã¾îÀÇ Àû¿ë¹üÀ§¸¦ Á¦ÇÑÇÒ ¼ö ÀÖÀ½À» ±â¾ïÇ϶ó. ÀÌ °æ¿ì + Á¶°Ç¿¡ ¸Â´Â ¿äû¿¡¸¸ DNS Á¶È¸¸¦ ÇÑ´Ù. ´ÙÀ½Àº + .html°ú .cgi ÆÄÀϸ¸ DNS °Ë»öÀ» + ÇÏ´Â ¿¹Á¦´Ù:

+ +

+ HostnameLookups off
+ <Files ~ "\.(html|cgi)$">
+ + HostnameLookups on
+ + </Files> +

+ +

±×·¯³ª CGI¿¡¼­ DNS¸íÀÌ ÇÊ¿äÇÒ »ÓÀ̶ó¸é, ÇÊ¿äÇÑ Æ¯Á¤ + CGI¿¡¼­¸¸ gethostbyname È£ÃâÀ» Çϵµ·Ï °í·ÁÇغ¼ + ¼ö ÀÖ´Ù.

+ + + +

FollowSymLinks¿Í SymLinksIfOwnerMatch

+ + + +

URL °ø°£¿¡¼­ Options FollowSymLinks¸¦ + »ç¿ëÇÏÁö¾Ê°í Options SymLinksIfOwnerMatch¸¦ + »ç¿ëÇÏ¸é ¾ÆÆÄÄ¡´Â ½Éº¼¸µÅ©¸¦ °Ë»çÇϱâÀ§ÇØ ½Ã½ºÅÛÈ£ÃâÀ» + Çѹø ´õ ÇØ¾ß ÇÑ´Ù. ÆÄÀϸíÀÇ °¢ ºÎºÐ¸¶´Ù Çѹø¾¿ ´õ È£ÃâÀ» + ÇÑ´Ù. ¿¹¸¦ µé¾î, ¼³Á¤ÀÌ ´ÙÀ½°ú °°°í:

+ +

+ DocumentRoot /www/htdocs
+ <Directory />
+ + Options SymLinksIfOwnerMatch
+ + </Directory> +

+ +

/index.html URI¿¡ ´ëÇÑ ¿äûÀÌ ÀÖ´Ù°í °¡Á¤ÇÏÀÚ. + ±×·¯¸é ¾ÆÆÄÄ¡´Â /www, /www/htdocs, + /www/htdocs/index.html °¢°¢¿¡ ´ëÇØ + lstat(2)¸¦ È£ÃâÇÑ´Ù. lstats + °á°ú¸¦ ij½ÌÇÏÁö ¾Ê±â¶§¹®¿¡ ¿äûÀÌ µé¾î¿Ã ¶§¸¶´Ù ¸Å¹ø °°Àº + ÀÛ¾÷À» ÇÑ´Ù. ÁøÂ¥ ½Éº¼¸µÅ© º¸¾È °Ë»ç¸¦ ¿øÇÑ´Ù¸é ´ÙÀ½°ú + °°ÀÌ ÇÒ ¼ö ÀÖ´Ù:

+ +

+ DocumentRoot /www/htdocs
+ <Directory />
+ + Options FollowSymLinks
+ + </Directory>
+
+ <Directory /www/htdocs>
+ + Options -FollowSymLinks +SymLinksIfOwnerMatch
+ + </Directory> +

+ +

ÀÌ °æ¿ì ÃÖ¼ÒÇÑ DocumentRoot °æ·Î´Â °Ë»çÇÏÁö + ¾Ê´Â´Ù. DocumentRoot ¹Û¿¡ ÀÖ´Â °æ·Î·Î Alias³ª RewriteRuleÀ» »ç¿ëÇÑ + °æ¿ì¿¡µµ À§¿Í ºñ½ÁÇÑ ¼½¼ÇÀÌ ÇÊ¿äÇÏ´Ù. ½Éº¼¸µÅ© º¸¾ÈÀ» + °í·ÁÇÏÁö ¾Ê°í ÃÖ°íÀÇ ¼º´ÉÀ» ¾òÀ¸·Á¸é, + FollowSymLinks¸¦ ¼³Á¤ÇÏ°í, + SymLinksIfOwnerMatch´Â Àý´ë·Î ¾ÈµÈ´Ù.

+ + + +

AllowOverride

+ + + +

URL °ø°£¿¡¼­ overrides¸¦ Çã¿ëÇÑ´Ù¸é (º¸Åë + .htaccess ÆÄÀÏ) ¾ÆÆÄÄ¡´Â ÆÄÀϸíÀÇ °¢ ºÎºÐ¸¶´Ù + .htaccess¸¦ ¿­±æ ½ÃµµÇÑ´Ù. ¿¹¸¦ µé¾î,

+ +

+ DocumentRoot /www/htdocs
+ <Directory />
+ + AllowOverride all
+ + </Directory> +

+ +

/index.html URI¿¡ ´ëÇÑ ¿äûÀÌ ÀÖ´Ù°í °¡Á¤ÇÏÀÚ. + ¾ÆÆÄÄ¡´Â /.htaccess, /www/.htaccess, + /www/htdocs/.htaccess¸¦ ¿­·Á°í ½ÃµµÇÑ´Ù. + ÇØ°áÃ¥Àº ¾ÕÀÇ Options FollowSymLinks °æ¿ì¿Í + ºñ½ÁÇÏ´Ù. ÃÖ°íÀÇ ¼º´ÉÀ» ¾òÀ¸·Á¸é ÆÄÀϽýºÅÛ¿¡ ´ëÇؼ­ Ç×»ó + AllowOverride NoneÀ» »ç¿ëÇÑ´Ù.

+ + + +

³»¿ëÇù»ó

+ + + +

°¡´ÉÇÏ°í ÁøÂ¥ Á¶±ÝÀÇ ¼º´ÉÇâ»ó¿¡µµ °ü½ÉÀÌ ÀÖ´Ù¸é ³»¿ëÇù»óÀ» + ¸·´Â´Ù. ½ÇÁ¦·Î Çù»óÀÇ À̵æÀº ¼º´ÉÀúÇϺ¸´Ù ÀÛ´Ù. ¼­¹ö¸¦ + ºü¸£°Ô ÇÒ ¼ö ÀÖ´Ù. ´ÙÀ½°ú °°ÀÌ ¿ÍÀϵåÄ«µå¸¦ »ç¿ëÇÏ´Â ´ë½Å:

+ +

+ DirectoryIndex index +

+ +

¿ÏÀüÇÑ ¸ñ·ÏÀ» »ç¿ëÇÑ´Ù:

+ +

+ DirectoryIndex index.cgi index.pl index.shtml index.html +

+ +

°¡Àå ÈçÇÑ °ÍÀ» ¾Õ¿¡ µÐ´Ù.

+ +

¶Ç, µð·ºÅ丮¿¡¼­ ÆÄÀϵéÀ» ã´Â MultiViews + º¸´Ù´Â, ÇÑ ÆÄÀϸ¸ ÀÐÀ¸¸é ÇÊ¿äÇÑ Á¤º¸¸¦ ¾òÀ» ¼ö ÀÖ´Â + type-map ÆÄÀÏÀ» Á÷Á¢ ¸¸µå´Â °ÍÀÌ ´õ ºü¸§À» + ¸í½ÉÇ϶ó.

+ +

»çÀÌÆ®¿¡ ³»¿ëÇù»óÀÌ ÇÊ¿äÇÏ´Ù¸é Çù»óÀ» À§ÇØ Options + MultiViews Áö½Ã¾î¸¦ »ç¿ëÇϱ⺸´Ù type-map + ÆÄÀÏÀ» °í·ÁÇ϶ó. Çù»ó¹æ¹ý¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸í°ú + type-map ÆÄÀÏÀ» ¸¸µå´Â ¹æ¹ýÀº ³»¿ëÇù»ó ¹®¼­¸¦ Âü°íÇ϶ó.

+ + + +

¸Þ¸ð¸®´ëÀÀ (memory-mapping)

+ + + +

¿¹¸¦ µé¾î, server-side-include¸¦ ó¸®ÇÏ´Â µî ¾ÆÆÄÄ¡ + 2.0ÀÌ Àü¼ÛÇÒ ÆÄÀÏÀ» ÀÐÀ»¶§ ¿î¿µÃ¼Á¦°¡ mmap(2) + µîÀ» Áö¿øÇÑ´Ù¸é ÆÄÀÏÀ» ¸Þ¸ð¸®´ëÀÀÇÑ´Ù.

+ +

¿©·¯ Ç÷¡Æû¿¡¼­ ¸Þ¸ð¸®´ëÀÀÀ» ¼º´ÉÀ» Çâ»óÇÑ´Ù. ±×·¯³ª + ¸Þ¸ð¸®´ëÀÀÀÌ ¼­¹öÀÇ ¼º´ÉÀ» ¶³¾îÆ®¸®°í ½ÉÁö¾î ¾ÈÁ¤¼ºÀ» + ÇØÄ¡´Â °æ¿ì°¡ ÀÖ´Ù:

+ +
    +
  • +

    ¾î¶² ¿î¿µÃ¼Á¦¿¡¼­ mmapÀº CPU °³¼ö°¡ + ¸¹¾ÆÁú¶§ read(2) ¸¸Å­ È®À强ÀÌ ÁÁÁö ¾Ê´Ù. + ¿¹¸¦ µé¾î, ´ÙÁßÇÁ·Î¼¼¼­ Solaris ¼­¹ö¿¡¼­ ¾ÆÆÄÄ¡ 2.0Àº + Á¾Á¾ mmapÀ» »ç¿ëÇÏÁö ¾ÊÀ»¶§ ¼­¹ö°¡ ó¸®ÇÑ + ÆÄÀÏÀ» ´õ »¡¸® Àü¼ÛÇÑ´Ù.

    +
    • + +
  • +

    NFS ¸¶¿îÆ®ÇÑ ÆÄÀϽýºÅÛ¿¡ ÀÖ´Â ÆÄÀÏÀ» ¸Þ¸ð¸®´ëÀÀÇÏ´Â + µµÁß¿¡ ´Ù¸¥ NFS Ŭ¶óÀ̾ðÆ®¿¡ ÀÖ´Â ÇÁ·Î¼¼½º°¡ ÆÄÀÏÀ» + Áö¿ì°Å³ª ÆÄÀÏÅ©±â¸¦ ÁÙÀ̸é, À¥¼­¹ö ÇÁ·Î¼¼½º°¡ ´ÙÀ½ + ¹ø¿¡ ¸Þ¸ð¸®´ëÀÀÇÑ ÆÄÀϳ»¿ëÀ» ÀÐÀ»¶§ bus error°¡ ¹ß»ýÇÒ + ¼ö ÀÖ´Ù.

    +
    • +
+ +

À§ÀÇ Á¶°Ç¿¡ ÇØ´çÇϸé Àü¼ÛÇÏ´Â ÆÄÀÏÀ» ¸Þ¸ð¸®´ëÀÀÇÏÁö + ¾Êµµ·Ï EnableMMAP off¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù. (ÁÖÀÇ: + ÀÌ Áö½Ã¾î´Â µð·ºÅ丮º°·Î º¯°æÇÒ ¼ö ÀÖ´Ù.)

+ + + +

Sendfile

+ + + +

¾ÆÆÄÄ¡´Â ¿î¿µÃ¼Á¦°¡ sendfile(2)À» Áö¿øÇϸé + Ä¿³Î sendfileÀ» »ç¿ëÇÏ¿© -- ¿¹¸¦ µé¾î, Á¤Àû ÆÄÀÏÀ» ¼­ºñ½ºÇÒ¶§ + -- Àü¼ÛÇÒ ÆÄÀÏÀ» Á÷Á¢ ÀÐÁö¾ÊÀ» ¼ö ÀÖ´Ù.

+ +

¿©·¯ Ç÷¡Æû¿¡¼­ sendfileÀ» »ç¿ëÇϸé read¿Í send¸¦ µû·Î + ÇÒ ÇÊ¿ä°¡ ¾ø¾î¼­ »¡¶óÁø´Ù. ±×·¯³ª sendfileÀ» »ç¿ëÇϸé + À¥¼­¹öÀÇ ¾ÈÁ¤¼ºÀ» ÇØÄ¡°ÔµÇ´Â °æ¿ì°¡ ÀÖ´Ù:

+ +
    +
  • +

    sendfile Áö¿øÀÌ À߸øµÇ¾ú°í ÄÄÆÄÀÏ ½Ã½ºÅÛÀÌ ÀÌÁ¡À» + ¹ß°ßÇÏÁö ¸øÇÏ´Â Ç÷¡ÆûÀÌ ÀÖ´Ù. ƯÈ÷ ´Ù¸¥ ÄÄÇ»ÅÍ¿¡¼­ + ½ÇÇàÆÄÀÏÀ» ÄÄÆÄÀÏÇÏ¿© sendfile Áö¿øÀÌ À߸øµÈ ÄÄÇ»ÅÍ·Î + °¡Á®¿Â °æ¿ì¿¡ °¡´ÉÇÏ´Ù.

    +
    • +
  • +

    Ä¿³ÎÀº ÀÚ½ÅÀÇ Ä³½¬¸¦ »ç¿ëÇÏ¿© NFS·Î ¸¶¿îÆ®ÇÑ ÆÄÀÏÀ» + ¾ÈÁ¤ÀûÀ¸·Î ¼­ºñ½ºÇÒ ¼ö ¾ø´Â °æ¿ì°¡ ÀÖ´Ù.

    +
    • +
+ +

À§ÀÇ Á¶°Ç¿¡ ÇØ´çÇϸé ÆÄÀÏÀ» sendfile Àü¼ÛÇÏÁö ¾Êµµ·Ï + EnableSendfile off¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù. (ÁÖÀÇ: + ÀÌ Áö½Ã¾î´Â µð·ºÅ丮º°·Î º¯°æÇÒ ¼ö ÀÖ´Ù.)

+ + + +

ÇÁ·Î¼¼½º »ý¼º

+ + + +

¾ÆÆÄÄ¡ 1.3 ÀÌÀü¿¡´Â MinSpareServers, MaxSpareServers, StartServers ¼³Á¤ÀÌ ¸ðµÎ + º¥Ä¡¸¶Å© °á°ú¿¡ Å« ¿µÇâÀ» ¹ÌÃÆ´Ù. ƯÈ÷ ¾ÆÆÄÄ¡´Â ÀÛ¾÷À» + ¼­ºñ½ºÇϱâÀ§ÇØ ÃæºÐÇÑ Àڽļö¿¡ ´Ù´Ù¸¦ ¶§±îÁö "µµ´Þ" ±â°£ÀÌ + ÇÊ¿äÇß´Ù. óÀ½ StartServers°³ ÀÚ½ÄÀ» + ¸¸µçÈÄ, MinSpareServers + ¼³Á¤°ª±îÁö ÃÊ´ç ÀÚ½ÄÀ» Çϳª¾¿ ¸¸µé¾ú´Ù. ±×·¡¼­ StartServers ±âº»°ªÀÌ + 5ÀÎ ¼­¹ö¿¡ Ŭ¶óÀ̾ðÆ® 100°³°¡ µ¿½Ã¿¡ Á¢¼ÓÇϸé + ºÎÇϸ¦ ó¸®Çϱ⿡ ÃæºÐÇÑ ÀÚ½ÄÀ» ¸¸µé±â±îÁö 95ÃÊ°¡ °É·È´Ù. + ÀÚÁÖ Àç½ÃÀÛÇÏÁö ¾Ê´Â ½ÇÁ¦ ¼­¹ö¿¡¼­´Â Àß µ¿ÀÛÇÏÁö¸¸, 10ºÐ°£¸¸ + ½ÇÇàÇÏ´Â º¥Ä¡¸¶Å© °á°ú´Â ¸Å¿ì ³ª»Ú°Ô ³ª¿Â´Ù.

+ +

ÃÊ´ç ÇÑ°³ ±ÔÄ¢Àº ÀÚ½ÄÀ» »õ·Î ½ÃÀÛÇϸ鼭 ¼­¹ö¿¡ ¹«¸®¸¦ + ÁÖÁö ¾ÊÀ¸·Á°í Á¤Çß´Ù. ÄÄÇ»ÅÍ°¡ ÀÚ½ÄÀ» ½ÃÀÛÇÏ´À¶ó ¹Ù»Ú¸é + ¿äûÀ» ¼­ºñ½ºÇÒ ¼ö ¾ø´Ù. ±×·¯³ª ÀÌ ±ÔÄ¢ÀÌ ¾ÆÆÄÄ¡ÀÇ Ã¼°¨ + ¼º´É¿¡ ¾Ç¿µÇâÀ» ÁÖ¾î º¯°æÇÏ¿´´Ù. ¾ÆÆÄÄ¡ 1.3¿¡¼­ ÃÊ´ç ÇÑ°³ + ±ÔÄ¢Àº ¿ÏÈ­µÇ¾ú´Ù. ÄÚµå´Â ÀÚ½Ä ÇÑ°³¸¦ ¸¸µé°í, 1ÃÊ ½¬°í, + µÎ°³¸¦ ¸¸µé°í, 1ÃÊ ½¬°í, ³×°³¸¦ ¸¸µé°í, ÀÌ·± ½ÄÀ¸·Î ÃÊ´ç + ÀÚ½ÄÀ» 32°³ ¸¸µé¶§±îÁö Áö¼ö·Î Áõ°¡ÇÑ´Ù. Àڽļö°¡ MinSpareServers ¼³Á¤¿¡ ´Ù´Ù¸£¸é + Áõ°¡¸¦ Áß´ÜÇÑ´Ù.

+ +

ÀÌ °æ¿ì ¹ÝÀÀ¼Óµµ°¡ »¡¶óÁ®¼­ MinSpareServers, MaxSpareServers, StartServers¸¦ °ÅÀÇ ¼³Á¤ÇÒ ÇÊ¿ä°¡ ¾ø´Ù. ÀÏÃÊ¿¡ + ÀÚ½ÄÀ» 4°³ ÀÌ»ó »ý¼ºÇϸé ErrorLog¿¡ ±â·ÏÇÑ´Ù. ÀÌ·± ¿À·ù¹®ÀÌ + ¸¹ÀÌ º¸À̸é ÀÌ ¼³Á¤µéÀ» Á¶ÀýÇÏ±æ ¹Ù¶õ´Ù. + mod_status °á°ú°¡ µµ¿òÀÌ µÉ °ÍÀÌ´Ù.

+ +

ÇÁ·Î¼¼½º »ý¼º°ú °ü·ÃÇÏ¿© MaxRequestsPerChild ¼³Á¤Àº + ÇÁ·Î¼¼½º¸¦ Á¾·áÇÑ´Ù. ±âº»°ªÀº ÀڽĴç ó¸®ÇÒ ¿äû¼ö¿¡ Á¦ÇÑÀÌ + ¾ø´Ù´Â 0ÀÌ´Ù. ÇöÀç ¼³Á¤ÀÌ 30°ú + °°ÀÌ ¸Å¿ì ÀÛÀº °ªÀ¸·Î ¼³Á¤µÇÀÖ´Ù¸é, °ªÀ» »ó´çÈ÷ ³ôÈú ÇÊ¿ä°¡ + ÀÖ´Ù. SunOS³ª ¿À·¡µÈ Solaris ¹öÀüÀ» »ç¿ëÇÑ´Ù¸é, ¸Þ¸ð¸®À¯Ã⶧¹®¿¡ + ÀÌ °ªÀ» 10000 Á¤µµ·Î ¼³Á¤Ç϶ó.

+ +

¿¬°áÀ¯Áö(keep-alive)¸¦ »ç¿ëÇÑ´Ù¸é ÀڽĵéÀº ÀÌ¹Ì ¿­¸° + ¿¬°á¿¡¼­ Ãß°¡ ¿äûÀ» ±â´Ù¸®¸ç ¾Æ¹«°Íµµ ÇÏÁö¾Ê±â¶§¹®¿¡ °è¼Ó + ¹Ù»Ú´Ù. KeepAliveTimeoutÀÇ + ±âº»°ª 15 ÃÊ´Â ÀÌ·± Çö»óÀ» ÃÖ¼ÒÈ­ÇÑ´Ù. ³×Æ®¿÷ + ´ë¿ªÆø°ú ¼­¹ö ÀÚ¿ø °£ÀÇ ±ÕÇüÀÌ ¸Â°Ô ¼³Á¤ÇÑ´Ù. + ¿¬°áÀ¯ÁöÀÇ ´ëºÎºÐÀÇ ÀÌÁ¡ÀÌ »ç¶óÁö±â¶§¹®¿¡ ¾î¶² °æ¿ì¿¡µµ + ÀÌ °ªÀ» 60 ÃÊ ÀÌ»óÀ¸·Î ¿Ã¸®Áö ¸¶¶ó.

+ + + +
top
+
+

ÄÄÆÄÀϽà ¼³Á¤¿¡ ´ëÇؼ­

+ + + +

MPM ¼±ÅÃ

+ + + +

¾ÆÆÄÄ¡ 2.x´Â ´ÙÁß󸮸ðµâ + (MPMs)À̶ó´Â ±³Ã¼ÇÒ ¼ö ÀÖ´Â µ¿±âÈ­ ¸ðµ¨À» Áö¿øÇÑ´Ù. ¾ÆÆÄÄ¡¸¦ + ÄÄÆÄÀÏÇÒ¶§ MPMÀ» ¼±ÅÃÇØ¾ß ÇÑ´Ù. beos, + mpm_netware, mpmt_os2, + mpm_winnt¿Í °°ÀÌ Æ¯Á¤ Ç÷¡Æû¿¡¼­¸¸ »ç¿ëÇÒ + ¼ö ÀÖ´Â MPMµµ ÀÖ´Ù. ÀϹÝÀûÀÎ À¯´Ð½º·ù ½Ã½ºÅÛÀº ¿©·¯ MPM + Áß¿¡ Çϳª¸¦ ¼±ÅÃÇÒ ¼ö ÀÖ´Ù. À¥¼­¹öÀÇ ¼Óµµ¿Í + È®À强(scalability)Àº ¾î¶² MPMÀ» ¼±ÅÃÇ߳Ŀ¡ ´Þ·È´Ù:

+ +
    + +
  • worker MPMÀº ¿©·¯ ÀÚ½Ä ÇÁ·Î¼¼½º°¡ + °¢°¢ ¿©·¯ ¾²·¹µå¸¦ »ç¿ëÇÑ´Ù. °¢ ¾²·¹µå´Â Çѹø¿¡ ÇÑ ¿¬°áÀ» + ´ã´çÇÑ´Ù. ÀϹÝÀûÀ¸·Î worker´Â prefork MPM º¸´Ù ÀûÀº + ¸Þ¸ð¸®¸¦ »ç¿ëÇϹǷΠÅë½Å·®ÀÌ ¸¹Àº ¼­¹ö¿¡ ÀûÀýÇÏ´Ù.
    • + +
  • prefork MPMÀº ¾²·¹µå°¡ ÇÑ°³ÀÎ ÀÚ½Ä + ÇÁ·Î¼¼½º¸¦ ¿©·¯°³ »ç¿ëÇÑ´Ù. °¢ ÇÁ·Î¼¼½º´Â Çѹø¿¡ ÇÑ + ¿¬°áÀ» ´ã´çÇÑ´Ù. ¿©·¯ ½Ã½ºÅÛ¿¡¼­ preforkÀÇ ¼Óµµ´Â worker¿Í + ºñ½ÁÇÏÁö¸¸, ´õ ¸¹Àº ¸Þ¸ð¸®¸¦ »ç¿ëÇÑ´Ù. ´ÙÀ½°ú °°Àº »óȲ¿¡¼­ + ¾²·¹µå¸¦ »ç¿ëÇÏÁö ¾Ê´Â prefork ¹æ½ÄÀÌ worker¿¡ ºñÇØ + ÀÌÁ¡À» °¡Áø´Ù: ¾²·¹µå¿¡ ¾ÈÀüÇÏÁö (thread-safe) ¾ÊÀº + Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀ» »ç¿ëÇÒ ¼ö ÀÖ°í, ¾²·¹µå µð¹ö±ë Áö¿øÀÌ + ºó¾àÇÑ Ç÷¡Æû¿¡¼­ ½±°Ô µð¹ö±ëÇÒ ¼ö ÀÖ´Ù.
    • + +
+ +

ÀÌ MPMµé°ú ´Ù¸¥ MPM¿¡ ´ëÇØ ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â MPM ¹®¼­¸¦ Âü°íÇÏ±æ ¹Ù¶õ´Ù.

+ + + +

¸ðµâ

+ + + +

¸Þ¸ð¸® »ç¿ë·®ÀÌ ¼º´É¿¡¼­ °¡Àå Áß¿äÇÑ ¿äÀÎÀ̱⶧¹®¿¡ + ½ÇÁ¦·Î »ç¿ëÇÏÁö ¾Ê´Â ¸ðµâÀ» Á¦°ÅÇغ¸ÀÚ. ¸ðµâÀ» DSO·Î ÄÄÆÄÀÏÇß´Ù¸é °£´ÜÈ÷ ±× + ¸ðµâ¿¡ ´ëÇÑ LoadModule Áö½Ã¾î¸¦ ÁÖ¼®Ã³¸®Çϸé + µÈ´Ù. ±×·¡¼­ ¸ðµâÀ» Á¦°ÅÇÏ°í ½ÇÇàÇÏ¿© »çÀÌÆ®°¡ ¸ðµâ¾øÀ̵µ + Á¤»óÀûÀ¸·Î µ¿ÀÛÇÏ´ÂÁö »ìÆ캼 ¼ö ÀÖ´Ù.

+ +

¹Ý´ë·Î ¸ðµâÀÌ ¾ÆÆÄÄ¡ ½ÇÇàÆÄÀÏ¿¡ Á¤ÀûÀ¸·Î ¸µÅ©µÇÀÖ´Ù¸é + ¿øÇÏÁö ¾Ê´Â ¸ðµâÀ» Á¦°ÅÇϱâÀ§ÇØ ¾ÆÆÄÄ¡¸¦ ÀçÄÄÆÄÀÏÇØ¾ß + ÇÑ´Ù.

+ +

¿©±â¼­ ´ç¿¬È÷ ¾î¶² ¸ðµâÀ» »ç¿ëÇÏ°í »ç¿ëÇÏÁö ¸»Áö + Àǹ®ÀÌ »ý±ä´Ù. Á¤´äÀº À¥»çÀÌÆ®¸¶´Ù ´Ù¸£´Ù. ±×·¯³ª ¾Æ¸¶µµ + ÃÖ¼ÒÇÑ mod_mime, + mod_dir, mod_log_config + ¸ðµâÀº »ç¿ëÇÒ °ÍÀÌ´Ù. ¹°·Ð À¥»çÀÌÆ®¿¡ ·Î±×ÆÄÀÏÀÌ ÇÊ¿ä¾ø´Ù¸é + mod_log_config´Â ¾ø¾îµµ µÈ´Ù. ±×·¯³ª ÃßõÇÏÁö + ¾Ê´Â´Ù.

+ + + +

Atomic ¸í·É

+ + + +

mod_cache °°Àº ¸ðµâ°ú ÃÖ±Ù °³¹ßÁßÀÎ + worker MPMÀº APRÀÇ atomic API¸¦ »ç¿ëÇÑ´Ù. ÀÌ API´Â °æ·®±Þ + ¾²·¹µå µ¿±âÈ­¸¦ À§ÇÒ atomic ¸í·ÉÀ» Á¦°øÇÑ´Ù.

+ +

±âº»ÀûÀ¸·Î APRÀº °¢ ¿î¿µÃ¼Á¦/CPU Ç÷¡Æû¿¡¼­ °¡Àå È¿À²ÀûÀÎ + ¹æ¹ýÀ» »ç¿ëÇÏ¿© ÀÌ ¸í·ÉÀ» ±¸ÇöÇÑ´Ù. ¿¹¸¦ µé¾î, ¿©·¯ ÃֽŠ+ CPU¿¡´Â Çϵå¿þ¾î·Î atomic compare-and-swap (CAS) ¿¬»êÀ» + ÇÏ´Â ¸í·É¾î°¡ ÀÖ´Ù. ±×·¯³ª ¾î¶² Ç÷¡Æû¿¡¼­ APRÀº ÀÌ·± + ¸í·É¾î°¡ ¾ø´Â ¿À·¡µÈ CPU¿Í ȣȯ¼ºÀ» À§ÇØ ´õ ´À¸° mutex±â¹Ý + ±¸ÇöÀ» ±âº»ÀûÀ¸·Î »ç¿ëÇÑ´Ù. ÀÌ·± Ç÷¡Æû¿¡¼­ ¾ÆÆÄÄ¡¸¦ + ÄÄÆÄÀÏÇÒ¶§ ¾ÆÆÄÄ¡¸¦ ÃֽŠCPU¿¡¼­¸¸ ½ÇÇàÇÒ °èȹÀ̶ó¸é, + ¾ÆÆÄÄ¡¸¦ ±¸¼ºÇÒ¶§ --enable-nonportable-atomics + ¿É¼ÇÀ» »ç¿ëÇÏ¿© ´õ ºü¸¥ atomic ±¸ÇöÀ» ¼±ÅÃÇÒ ¼ö ÀÖ´Ù:

+ +

+ ./buildconf
+ ./configure --with-mpm=worker --enable-nonportable-atomics=yes +

+ +

--enable-nonportable-atomics ¿É¼ÇÀº ´ÙÀ½°ú + °°Àº Ç÷¡Æû¿¡ ¿µÇâÀÌ ÀÖ´Ù:

+ +
    + +
  • SPARC¿¡¼­ Solaris
    + ±âº»ÀûÀ¸·Î APRÀº Solaris/SPARC¿¡¼­ mutex±â¹Ý atomicÀ» + »ç¿ëÇÑ´Ù. ±×·¯³ª ±¸¼ºÇÒ¶§ + --enable-nonportable-atomics¸¦ »ç¿ëÇϸé + APRÀº ºü¸¥ Çϵå¿þ¾î compare-and-swapÀ» À§ÇÑ SPARC + v8plus ¸í·É¾î¸¦ »ç¿ëÇÑ´Ù. ÀÌ ¿É¼ÇÀ» »ç¿ëÇϸé atomic + ¸í·ÉÀÌ ´õ È¿À²ÀûÀÌÁö¸¸ (CPU¸¦ ´ú »ç¿ëÇÏ°í ´õ ³ôÀº + µ¿±âÈ­°¡ °¡´ÉÇÏ´Ù), ÄÄÆÄÀÏÇÑ ½ÇÇàÆÄÀÏÀº UltraSPARC + Ĩ¿¡¼­¸¸ ½ÇÇàÇÒ ¼ö ÀÖ´Ù. +
    • + +
  • Linux on x86
    + ±âº»ÀûÀ¸·Î APRÀº ¸®´ª½º¿¡¼­ mutex±â¹Ý atomicÀ» + »ç¿ëÇÑ´Ù. ±×·¯³ª ±¸¼ºÇÒ¶§ + --enable-nonportable-atomics¸¦ »ç¿ëÇϸé + APRÀº ºü¸¥ Çϵå¿þ¾î compare-and-swapÀ» À§ÇÑ 486 + ¸í·É¾î¸¦ »ç¿ëÇÑ´Ù. ´õ È¿À²ÀûÀÎ atomic ¸í·ÉÀÌ °¡´ÉÇÏÁö¸¸, + ÄÄÆÄÀÏÇÑ ½ÇÇàÆÄÀÏÀº 486 ÀÌ»ó Ĩ¿¡¼­¸¸ (386Àº ¾ÈµÈ´Ù) + ½ÇÇàÇÒ ¼ö ÀÖ´Ù. +
    • + +
+ + + +

mod_status¿Í ExtendedStatus On

+ + + +

¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÒ¶§ mod_status¸¦ Æ÷ÇÔÇÏ°í + ½ÇÇàÇÒ¶§ ExtendedStatus OnÀ» ¼³Á¤ÇÏ¸é ¾ÆÆÄÄ¡´Â + ¿äûÀ» ¹ÞÀ»¶§¸¶´Ù gettimeofday(2)(ȤÀº ¿î¿µÃ¼Á¦¿¡ + µû¶ó times(2))¸¦ µÎ¹ø È£ÃâÇÏ°í (1.3 ÀÌÀü¿¡´Â) + time(2)µµ Ãß°¡·Î ¿©·¯¹ø È£ÃâÇÑ´Ù. »óÅ º¸°í¼­¿¡ + µ¿À۽ð£ÀÌ ÇÊ¿äÇϱ⠶§¹®ÀÌ´Ù. ÃÖ»óÀÇ ¼º´ÉÀ» ¾òÀ¸·Á¸é + (±âº»°ªÀÎ) ExtendedStatus off¸¦ ¼³Á¤ÇÑ´Ù.

+ + + +

accept Á÷·ÄÈ­ - ¿©·¯ ¼ÒÄÏ

+ + + +

ÁÖÀÇ:

+

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

+
+ +

À¯´Ð½º ¼ÒÄÏ APIÀÇ ´ÜÁ¡À» ¼³¸íÇÑ´Ù. À¥¼­¹ö°¡ ¿©·¯ Æ÷Æ® + ȤÀº ¿©·¯ ÁÖ¼Ò¸¦ ±â´Ù¸®±âÀ§ÇØ ¿©·¯ ListenÀ» »ç¿ëÇÑ´Ù°í °¡Á¤ÇÏÀÚ. + ¿¬°áÀÌ °¡´ÉÇÑÁö °¢ ¼ÒÄÏÀ» °Ë»çÇϱâÀ§ÇØ ¾ÆÆÄÄ¡´Â + select(2)¸¦ »ç¿ëÇÑ´Ù. select(2)´Â + ¼ÒÄÏ¿¡ ±â´Ù¸®°í ÀÖ´Â ¿¬°áÀÌ ¾ø´ÂÁö ȤÀº ÃÖ¼ÒÇÑ + ÇÑ°³ ÀÖ´ÂÁö ¾Ë·ÁÁØ´Ù. ¾ÆÆÄÄ¡¿¡´Â ¿©·¯ ÀÚ½ÄÀÌ ÀÖ°í, + ½¬°í ÀÖ´Â ¸ðµç ÀÚ½ÄÀº µ¿½Ã¿¡ »õ·Î¿î ¿¬°áÀ» °Ë»çÇÑ´Ù. ¿ø·¡ + ±¸ÇöÀº ´ÙÀ½°ú ºñ½ÁÇÏ´Ù (ÀÌ ¿¹´Â Äڵ忡¼­ °¡Á®¿ÀÁö ¾Ê¾Ò´Ù. + ´ÜÁö ¼³¸íÇϱâÀ§ÇÑ ¿ëµµ·Î ¸¸µé¾ú´Ù.):

+ +

+ for (;;) {
+ + for (;;) {
+ + fd_set accept_fds;
+
+ FD_ZERO (&accept_fds);
+ for (i = first_socket; i <= last_socket; ++i) {
+ + FD_SET (i, &accept_fds);
+ + }
+ rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);
+ if (rc < 1) continue;
+ new_connection = -1;
+ for (i = first_socket; i <= last_socket; ++i) {
+ + if (FD_ISSET (i, &accept_fds)) {
+ + new_connection = accept (i, NULL, NULL);
+ if (new_connection != -1) break;
+ + }
+ + }
+ if (new_connection != -1) break;
+ + }
+ process the new_connection;
+ + } +

+ +

±×·¯³ª À§ÀÇ ´Ü¼øÇÑ ±¸Çö¿¡´Â ½É°¢ÇÑ °í°¥(starvation) + ¹®Á¦°¡ ÀÖ´Ù. ¿©·¯ ÀÚ½ÄÀÌ µ¿½Ã¿¡ ÀÌ ¹Ýº¹¹®À» ½ÇÇàÇϸé, + ¿äûÀ» ±â´Ù¸®¸ç ¸ðµÎ select¿¡¼­ ¸ØÃá´Ù. À̶§ + ¾î¶² ¼ÒÄÏ¿¡ ¿äûÀÌ Çϳª¶óµµ µé¾î¿À¸é ¸ðµç ÀÚ½ÄÀÌ ±ú¾î³­´Ù + (±ú¾î³ª´Â ÀÚ½ÄÀÇ °³¼ö´Â ¿î¿µÃ¼Á¦¿Í ŸÀֿ̹¡ µû¶ó ´Ù¸£´Ù). + À̵éÀº ¸ðµÎ ¿¬°áÀ» acceptÇÏ±æ ½ÃµµÇÑ´Ù. ±×·¯³ª + (¾ÆÁ÷µµ ÇÑ ¿¬°á¸¸ ´ë±âÁßÀ̶ó¸é) ÇÑ Àڽĸ¸ ¼º°øÇÏ°í, ³ª¸ÓÁö´Â + accept¿¡¼­ ¸ØÃá´Ù. ±×·¯¸é ÀÌ ÀڽĵéÀº + ÇÑ ¼ÒÄÏÀÇ ¿äû¸¸À» ¼­ºñ½ºÇϵµ·Ï ¹­¿©¼­, ±× ¼ÒÄÏÀ¸·Î »õ·Î¿î + ¿äûÀÌ ÃæºÐÈ÷ µé¾î¿Í¼­ ¸ðµç ÀÚ½ÄÀ» ±ú¿ï¶§±îÁö Á¤ÁöÇØÀÖ´Ù. + ÀÌ·± °í°¥ ¹®Á¦´Â PR#467¿¡ + óÀ½ º¸°íµÇ¾ú´Ù. ÃÖ¼ÒÇÑ µÎ°¡Áö ÇØ°áÃ¥ÀÌ ÀÖ´Ù.

+ +

ÇÑ°¡Áö´Â ¼ÒÄÏÀ» ´ë±âÇÏÁö ¾Êµµ·Ï (non-blocking) ¸¸µå´Â + ¹æ¹ýÀÌ´Ù. ÀÌ °æ¿ì ÀÚ½ÄÀÌ accept¸¦ Çصµ ¸ØÃßÁö + ¾Ê°í, Áï½Ã ÁøÇàÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª CPU ½Ã°£À» ³¶ºñÇÑ´Ù. + select¿¡¼­ ½¬´Â ÀÚ½ÄÀÌ 10°³ ÀÖ°í, »õ·Î ¿¬°áÀÌ + ÇÑ°³ µé¾î¿Ô´Ù°í °¡Á¤ÇÏÀÚ. ±×·¯¸é ÀÌ ÀÚ½ÄÁß 9°³´Â ±ú¾î³ª¼­ + ¿¬°áÀ» acceptÇÏ±æ ½ÃµµÇÏ°í ½ÇÆÐÇÏ¸é ¾Æ¹« + Àϵµ ÇÏÁö ¾Ê°í ´Ù½Ã select¸¦ ¹Ýº¹ÇÑ´Ù. ´Ù½Ã + select·Î µ¹¾Æ¿Ã ¶§±îÁö ¾î¶² Àڽĵµ ´Ù¸¥ ¼ÒÄÏ¿¡ + µé¾î¿Â ¿äûÀ» ¼­ºñ½ºÇÏÁö ¾Ê´Â´Ù. (´ÙÁßÇÁ·Î¼¼¼­ ÄÄÇ»ÅÍ¿¡¼­) + ½¬´Â ÀÚ½Ä °³¼ö¸¸Å­ CPU °³¼ö°¡ ÀÖ´Â µå¹® °æ¿ì°¡ ¾Æ´Ï¶ó¸é + ÀÌ ÇØ°áÃ¥Àº º°·Î ÁÁ¾Æº¸ÀÌÁö ¾Ê´Â´Ù.

+ +

´Ù¸¥ ¹æ¹ýÀº ¾ÆÆÄÄ¡°¡ »ç¿ëÇÏ´Â ¹æ¹ýÀ¸·Î ³»ºÎ ¹Ýº¹¹®¿¡ + ÇÑ Àڽĸ¸À» µé¿©º¸³½´Ù. ¹Ýº¹¹®Àº ´ÙÀ½°ú °°´Ù (Â÷À̸¦ + °­Á¶ÇßÀ½):

+ +

+ for (;;) {
+ + accept_mutex_on ();
+ for (;;) {
+ + fd_set accept_fds;
+
+ FD_ZERO (&accept_fds);
+ for (i = first_socket; i <= last_socket; ++i) {
+ + FD_SET (i, &accept_fds);
+ + }
+ rc = select (last_socket+1, &accept_fds, NULL, NULL, NULL);
+ if (rc < 1) continue;
+ new_connection = -1;
+ for (i = first_socket; i <= last_socket; ++i) {
+ + if (FD_ISSET (i, &accept_fds)) {
+ + new_connection = accept (i, NULL, NULL);
+ if (new_connection != -1) break;
+ + }
+ + }
+ if (new_connection != -1) break;
+ + }
+ accept_mutex_off ();
+ process the new_connection;
+ + } +

+ +

accept_mutex_on°ú accept_mutex_off + ÇÔ¼ö´Â mutex ¼¼¸¶Æ÷¾î¸¦ + ±¸ÇöÇÑ´Ù. Çѹø¿¡ ¿ÀÁ÷ ÇÑ Àڽĸ¸ÀÌ mutex¸¦ °¡Áú ¼ö ÀÖ´Ù. + mutex¸¦ ±¸ÇöÇÏ´Â ¹æ¹ýÀº ¿©·¯°¡ÁöÀÌ´Ù. ±¸Çö ¹æ¹ýÀº (1.3 + ÀÌÀü) src/conf.h³ª (1.3°ú ±× ÀÌÈÄ) + src/include/ap_config.h¿¡ Á¤ÀǵÇÀÖ´Ù. ¾î¶² + ¾ÆÅ°ÅØÃÄ´Â Àá±Ý(locking) ¹æ¹ýÀ» ¼±ÅÃÇÏÁö ¾Ê±â¶§¹®¿¡, ÀÌ·± + ¾ÆÅ°ÅØÃÄ¿¡¼­ ¿©·¯ Listen Áö½Ã¾î¸¦ »ç¿ëÇϸé + À§ÇèÇÏ´Ù.

+ +

½ÇÇà½Ã AcceptMutex Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + mutex ±¸ÇöÀ» º¯°æÇÒ ¼ö ÀÖ´Ù.

+ +
+
AcceptMutex flock
+ +
+

ÀÌ ¹æ¹ýÀº Àá±ÝÆÄÀÏÀ» Àá±×±âÀ§ÇØ flock(2) + ½Ã½ºÅÛÈ£ÃâÀ» »ç¿ëÇÑ´Ù (Àá±ÝÆÄÀÏ À§Ä¡´Â LockFile Áö½Ã¾î·Î ÁöÁ¤).

+
+ +
AcceptMutex fcntl
+ +
+

ÀÌ ¹æ¹ýÀº Àá±ÝÆÄÀÏÀ» Àá±×±âÀ§ÇØ fcntl(2) + ½Ã½ºÅÛÈ£ÃâÀ» »ç¿ëÇÑ´Ù (Àá±ÝÆÄÀÏ À§Ä¡´Â LockFile Áö½Ã¾î·Î ÁöÁ¤).

+
+ +
AcceptMutex sysvsem
+ +
+

(1.3°ú ±× ÀÌÈÄ) ÀÌ ¹æ¹ýÀ» SysV½Ä ¼¼¸¶Æ÷¾î¸¦ »ç¿ëÇÏ¿© + mutex¸¦ ±¸ÇöÇÑ´Ù. ºÒÇàÈ÷µµ SysV½Ä ¼¼¸¶Æ÷¾î´Â ³ª»Û + ºÎÀÛ¿ëÀÌ ÀÖ´Ù. Çϳª´Â ¾ÆÆÄÄ¡°¡ ¼¼¸¶Æ÷¾î¸¦ Á¤¸®ÇÏÁö + ¾Ê°í Á×À» ¼ö ÀÖ´Â Á¡ÀÌ´Ù (ipcs(8) manpage + Âü°í). ´Ù¸¥ Çϳª´Â À¥¼­¹ö¿Í µ¿ÀÏÇÑ uid·Î ½ÇÇàÇÏ´Â + CGI°¡ (Áï, suexec³ª + cgiwrapper¸¦ »ç¿ëÇÏÁö¾Ê´Â ÇÑ ¸ðµç CGI) + ¼¼¸¶Æ÷¾î API¸¦ »ç¿ëÇÏ¿© ¼­ºñ½º°ÅºÎ°ø°ÝÀ» ÇÒ ¼ö ÀÖ´Â + Á¡ÀÌ´Ù. ÀÌ·± ÀÌÀ¯¶§¹®¿¡ IRIX¸¦ Á¦¿ÜÇÑ ¾ÆÅ°ÅØÃÄ¿¡¼­ + ÀÌ ¹æ¹ýÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù (´ëºÎºÐÀÇ IRIX ÄÄÇ»ÅÍ¿¡¼­ + ¾ÕÀÇ µÎ ¹æ¹ýÀº Áö³ªÄ¡°Ô ¹ö°Ì´Ù).

+
+ +
AcceptMutex pthread
+ +
+

(1.3°ú ±× ÀÌÈÄ) ÀÌ ¹æ¹ýÀº POSIX mutex¸¦ »ç¿ëÇϱ⶧¹®¿¡ + POSIX ¾²·¹µå ±Ô¾àÀ» ¿ÏÀüÈ÷ ±¸ÇöÇÑ ¾ÆÅ°ÅØÃĶó¸é ¸ðµÎ + »ç¿ë°¡´ÉÇÏÁö¸¸, (2.5 ÀÌÈÄ) Solaris¿¡¼­¸¸ ±×°Íµµ ƯÁ¤ + ±¸¼º¿¡¼­¸¸ µ¿ÀÛÇÏ´Â µíÇÏ´Ù. ÀÌ ¹æ¹ýÀ» ½ÃµµÇغ»´Ù¸é + ¼­¹ö°¡ ¸ØÃç¼­ ÀÀ´äÀ» ¾ÈÇÏ´ÂÁö »ìÆìºÁ¾ß ÇÑ´Ù. Á¤Àû + ³»¿ë¸¸ ¼­ºñ½ºÇÏ´Â ¼­¹ö´Â Àß µ¿ÀÛÇÏ´Â °Í °°´Ù.

+
+ +
AcceptMutex posixsem
+ +
+

(2.0°ú ±× ÀÌÈÄ) ÀÌ ¹æ¹ýÀº POSIX ¼¼¸¶Æ÷¾î¸¦ »ç¿ëÇÑ´Ù. + mutex¸¦ °¡Áø ÇÁ·Î¼¼½ºÀÇ ¾²·¹µå°¡ Á״´ٸé(segfault) + ¼¼¸¶Æ÷¾î ¼ÒÀ¯±ÇÀÌ È¸º¹µÇÁö ¾Ê¾Æ¼­ À¥¼­¹ö°¡ ¸ØÃá´Ù.

+
+ +
+ +

½Ã½ºÅÛ¿¡ À§ ¸ñ·Ï¿¡ ¾ø´Â Á÷·ÄÈ­(serialization) ¹æ¹ýÀÌ + ÀÖ´Ù¸é ±× ¹æ¹ýÀ» »ç¿ëÇÏ´Â Äڵ带 APR¿¡ Ãß°¡ÇÒ °¡Ä¡°¡ ÀÖ´Ù.

+ +

°í·Á´Â ÇغÃÁö¸¸ ±¸ÇöÇÏÁö¾ÊÀº ´Ù¸¥ ¹æ¹ýÀº ºÎºÐÀûÀ¸·Î + ¹Ýº¹¹®À» Á÷·ÄÈ­ÇÏ´Â ¹æ¹ýÀÌ´Ù. Áï, ÇÁ·Î¼¼¼­¸¦ ¸î°³¸¸ µé¿©º¸³»´Â + °ÍÀÌ´Ù. ÀÌ ¹æ¹ýÀº ¿©·¯ ÀÚ½ÄÀ» µ¿½Ã¿¡ ½ÇÇàÇÒ ¼ö À־ + Á÷·ÄÈ­¶§¹®¿¡ Àüü ´ë¿ªÆøÀ» È°¿ëÇÏÁö ¸øÇÏ´Â ´ÙÁßÇÁ·Î¼¼¼­ + ÄÄÇ»ÅÍ¿¡¼­¸¸ °ü½ÉÀ» °¡Á®º¼ ¼ö ÀÖ´Ù. ¾ÕÀ¸·Î »ìÆ캼 ºÎºÐÀÌÁö¸¸, + ¸Å¿ì º´·ÄÈ­µÈ À¥¼­¹ö°¡ ÈçÇÏÁö ¾Ê¾Æ¼­ ¿ì¼±¼øÀ§°¡ ³·´Ù.

+ +

ÃÖ»óÀÇ ¼º´ÉÀ» ¾ò±âÀ§Çؼ­´Â ¿©·¯ Listen ¹®À» »ç¿ëÇÏÁö ¾Ê´Â + °ÍÀÌ ÀÌ»óÀûÀÌ´Ù. ±×·¯³ª °è¼Ó ¼³¸íÇÑ´Ù.

+ + + +

accept Á÷·ÄÈ­ - ¼ÒÄÏ ÇÑ°³

+ + + +

¾ÕÀÇ ¼³¸íÀº ´ÙÁß¼ÒÄÏ ¼­¹ö¿¡´Â ÁÁÁö¸¸, ¼ÒÄÏÀÌ ÇÑ°³ÀÎ + ¼­¹ö´Â ¾î¶²°¡? ¿¬°áÀÌ µµÂøÇÒ¶§±îÁö ¸ðµç ÀÚ½ÄÀÌ + accept(2)¿¡¼­ ¸ØÃçÀֱ⶧¹®¿¡ ÀÌ·Ð»ó °°Àº + ¹®Á¦°¡ ¹ß»ýÇÏÁö ¾Ê°í, °í°¥ ¹®Á¦µµ ¾ø´Ù. ±×·¯³ª ½ÇÁ¦·Î´Â + ¾Õ¿¡¼­ ¸»ÇÑ ´ë±âÇÏÁö ¾Ê´Â (non-blocking) ¹æ¹ý¿¡¼­ ¹ß»ýÇÏ´Â + "°øȸÀü(spinning)" Çö»óÀ» °¨Ãß°í ÀÖ´Ù. ´ëºÎºÐÀÇ TCP ½ºÅÃÀº + ¿¬°áÀÌ µµÂøÇϸé Ä¿³ÎÀÌ accept¿¡¼­ ¸ØÃçÀÖ´Â + ¸ðµç ÀÚ½ÄÀ» ±ú¿ìµµ·Ï ±¸ÇöµÇÀÖ´Ù. ÇÁ·Î¼¼½ºÁß ÇÑ°³°¡ ¿¬°áÀ» + ¾ò°í »ç¿ëÀÚ¿µ¿ªÀ¸·Î µ¹¾Æ°¡°í, ³ª¸ÓÁö´Â Ä¿³Î¿¡¼­ °øȸÀüÇÏ¿© + ¿¬°áÀÌ ¾øÀ½À» ¹ß°ßÇÏ¸é ´Ù½Ã ÀáÀ» ÀÜ´Ù. »ç¿ëÀÚ¿µ¿ª Äڵ忡¼­´Â + ÀÌ·± °øȸÀüÀ» ¾Ë ¼ö ¾øÁö¸¸, ºÐ¸íÈ÷ Á¸ÀçÇÑ´Ù. ±×·¡¼­ ´ÙÁß¼ÒÄÏÀÇ + ´ë±âÇÏÁö ¾Ê´Â ¹æ¹ý°ú µ¿ÀÏÇÏ°Ô ºÎÇϸ¦ ³ôÀÌ´Â ºÒÇÊ¿äÇÑ ÇൿÀÌ + ÀϾ´Ù.

+ +

±×·¡¼­ ¿ì¸®´Â ¿©·¯ ¾ÆÅ°ÅØÃÄ¿¡¼­ ¼ÒÄÏÀÌ ÇÑ°³ÀÎ °æ¿ì¿¡µµ + Á÷·ÄÈ­ÇÏ¸é ´õ "Àß" µ¿ÀÛÇÔÀ» ¹ß°ßÇß´Ù. ±×·¡¼­ °ÅÀÇ ´ëºÎºÐÀÇ + °æ¿ì ±âº»ÀûÀ¸·Î Á÷·ÄÈ­¸¦ »ç¿ëÇÑ´Ù. ¸®´ª½º¿¡¼­ (Ä¿³Î 2.0.30, + 128Mb ¸Þ¸ð¸®¿¡ µà¾ó Pentium pro) ½ÇÇèÇÑ °á°ú ¼ÒÄÏ ÇÑ°³¸¦ + Á÷·ÄÈ­Çϸé ÇÏÁö ¾ÊÀº °æ¿ì¿¡ ºñÇØ ÃÊ´ç ¿äûÀÌ 3% ¹Ì¸¸ + ÁÙ¾îµé¾ú´Ù. ±×·¯³ª Á÷·ÄÈ­¸¦ ÇÏÁö ¾ÊÀº °æ¿ì ¿äû´ç 100ms + Áö¿¬ÀÌ ¹ß»ýÇß´Ù. ÀÌ Áö¿¬Àº ¾Æ¸¶µµ LAN¿¡¼­ ¹ß»ýÇÏ´Â ±ä + ¿¬°á¼±¶§¹®ÀÏ °ÍÀÌ´Ù. ¼ÒÄÏÀÌ ÇÑ°³ÀÎ °æ¿ì Á÷·ÄÈ­¸¦ »ç¿ëÇÏÁö + ¾ÊÀ¸·Á¸é SINGLE_LISTEN_UNSERIALIZED_ACCEPT¸¦ + Á¤ÀÇÇÑ´Ù.

+ + + +

Close Áö¿¬(lingering)

+ + + +

+ draft-ietf-http-connection-00.txt 8Àý¿¡¼­ ¼³¸íÇϵíÀÌ + ¾ÈÁ¤ÀûÀÎ À¥¼­¹ö°¡ µÇ·Á¸é, Åë½ÅÀÇ ¾ç ¹æÇâÀ» + µ¶¸³ÀûÀ¸·Î ´ÝÀ» ¼ö ÀÖ¾î¾ß ÇÑ´Ù (TCP ¿¬°áÀº ½Ö¹æÇâÀÌ°í, + ¹æÇâÀº ¼­·Î µ¶¸³ÀûÀÌ´Ù). ÀÌÁ¡À» ´Ù¸¥ ¼­¹ö¿¡¼­´Â ÀÚÁÖ + °£°úÇÏÁö¸¸, ¾ÆÆÄÄ¡´Â 1.2ºÎÅÍ Á¤È®È÷ ±¸ÇöÇØ¿Ô´Ù.

+ +

ÀÌ ±â´ÉÀ» ºÎÁÖÀÇÇÏ°Ô ¾ÆÆÄÄ¡¿¡ Ãß°¡ÇßÀ»¶§ ¿©·¯ À¯´Ð½º + ¹öÀü¿¡¼­ ¸¹Àº ¹®Á¦°¡ ¹ß»ýÇß´Ù. TCP ±Ô¾àÀº + FIN_WAIT_2¿¡ ŸÀӾƿôÀÌ ÀÖ´Ù°í Á¤ÇÏÁö ¾Ê¾ÒÁö¸¸, + ±ÝÁöÇÏÁöµµ ¾Ê¾Ò´Ù. ŸÀӾƿôÀÌ ¾ø´Â ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡ 1.2´Â + ¸¹Àº ¼ÒÄÏÀ» ¿µ¿øÈ÷ FIN_WAIT_2 »óÅ·Π¸¸µé¾ú´Ù. + ¸¹Àº °æ¿ì ÀÌ ¹®Á¦´Â Á¦Àۻ簡 Á¦°øÇÏ´Â ÃֽŠTCP/IP ÆÐÄ¡¸¦ + Àû¿ëÇÏ¿© ÇØ°áÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª Á¦Àۻ簡 ÆÐÄ¡¸¦ ¹ßÇ¥ÇÏÁö + ¾Ê´Â °æ¿ì°¡ (Áï, SunOS4 -- ¼Ò½º ¶óÀ̼±½º°¡ ÀÖ´Â + »ç¶÷Àº Á÷Á¢ ÆÐÄ¡ÇÒ ¼ö ÀÖÁö¸¸) Àֱ⶧¹®¿¡ ÀÌ ±â´ÉÀ» »ç¿ëÇÏÁö + ¾Ê±â·Î °áÁ¤Çß´Ù.

+ +

¹æ¹ýÀº µÎ°¡Áö´Ù. Çϳª´Â ¼ÒÄÏ ¿É¼Ç SO_LINGER¸¦ + »ç¿ëÇÏ´Â ¹æ¹ýÀÌ´Ù. ±×·¯³ª ºÒÇàÈ÷µµ ´ëºÎºÐÀÇ TCP/IP ½ºÅÃÀº + ÀÌ ¿É¼ÇÀ» ¿Ã¹Ù·Î ±¸ÇöÇÏÁö ¾Ê¾Ò´Ù. ¿Ã¹Ù·Î ±¸ÇöÇÑ ½ºÅÿ¡¼­ + Á¶Â÷µµ (Áï, ¸®´ª½º 2.0.31) ÀÌ ¹æ¹ýÀº ´ÙÀ½ ¹æ¹ýº¸´Ù + ´õ cpu¸¦ Àâ¾Æ¸Ô´Â´Ù.

+ +

¾ÆÆÄÄ¡´Â º¸Åë (http_main.c¿¡ ÀÖ´Â) + lingering_close¶ó´Â ÇÔ¼ö¸¦ »ç¿ëÇÑ´Ù. ÀÌ ÇÔ¼ö´Â + ´ëÃæ ´ÙÀ½°ú °°´Ù:

+ +

+ void lingering_close (int s)
+ {
+ + char junk_buffer[2048];
+
+ /* shutdown the sending side */
+ shutdown (s, 1);
+
+ signal (SIGALRM, lingering_death);
+ alarm (30);
+
+ for (;;) {
+ + select (s for reading, 2 second timeout);
+ if (error) break;
+ if (s is ready for reading) {
+ + if (read (s, junk_buffer, sizeof (junk_buffer)) <= 0) {
+ + break;
+ + }
+ /* just toss away whatever is here */
+ + }
+ + }
+
+ close (s);
+ + } +

+ +

ÀÌ ÄÚµå´Â ¿¬°áÀ» ´ÝÀ»¶§ ´õ CPU¸¦ »ç¿ëÇÏÁö¸¸, ¾ÈÁ¤ÀûÀÎ + ±¸ÇöÀ» À§ÇØ ÇÊ¿äÇÏ´Ù. HTTP/1.1ÀÌ ´õ ³Î¸® ÆÛÁö°í ¸ðµç ¿¬°áÀ» + À¯ÁöÇÑ´Ù¸é(persistent), ¿¬°áÀ» ¹Þ´Â ºñ¿ëÀº ¿©·¯ ¿äûÀ» + ó¸®Çϸ鼭 »ó¼âµÉ °ÍÀÌ´Ù. À§ÇèÇÏ°Ôµµ + NO_LINGCLOSE¸¦ Á¤ÀÇÇÏ¿© ÀÌ ±â´ÉÀ» »ç¿ëÇÏÁö + ¾ÊÀ» ¼ö ÀÖÁö¸¸, Àý´ë·Î ±ÇÇÏÁö ¾Ê´Â´Ù. ƯÈ÷ HTTP/1.1 + ÆÄÀÌÇÁ¶óÀÎ (¿ªÁÖ; ¿¬°áÀ¯Áö »óÅ¿¡¼­ ÀÀ´äÀ» ±â´Ù¸®Áö + ¾Ê°í ¿©·¯ ¿äûÀ» º¸³»´Â ±â¼ú) ¿¬°áÀ¯Áö¿¡´Â + lingering_close°¡ ÇʼöÀûÀÌ´Ù (±×¸®°í + ÆÄÀÌÇÁ¶óÀÎ ¿¬°áÀÌ ´õ ºü¸£±â¶§¹®¿¡ »ç¿ëÇÏ±æ ¹Ù¶ö °ÍÀÌ´Ù).

+ + + +

Scoreboard ÆÄÀÏ

+ + + +

¾ÆÆÄÄ¡ÀÇ ºÎ¸ð¿Í ÀÚ½ÄÀº scoreboard¶ó´Â °ÍÀ» ÅëÇØ ¼­·Î + Åë½ÅÇÑ´Ù. ÀÌ»óÀûÀ¸·Î´Â scoreboard¸¦ °øÀ¯¸Þ¸ð¸®·Î ±¸ÇöÇØ¾ß + ÇÑ´Ù. ¿ì¸® °³¹ßÀÚ°¡ ÇØ´ç ¿î¿µÃ¼Á¦¿¡ Á¢±ÙÇÒ ¼ö Àְųª »ó¼¼ÇÑ + Æ÷Æà °á°ú¸¦ ¹ÞÀº °æ¿ì º¸Åë °øÀ¯¸Þ¸ð¸®¸¦ »ç¿ëÇÏ¿© ±¸ÇöÇÑ´Ù. + ³ª¸ÓÁö´Â µð½ºÅ©¿¡ ÀÖ´Â ÆÄÀÏÀ» »ç¿ëÇÏ¿© ±¸ÇöÇÑ´Ù. µð½ºÅ©¿¡ + ÀÖ´Â ÆÄÀÏÀº ´À¸®°í ½Å·Úµµ°¡ ¶³¾îÁø´Ù (±â´Éµµ ´õ Àû´Ù). + src/main/conf.h ÆÄÀÏ¿¡¼­ »ç¿ëÇÏ´Â ¾ÆÅ°ÅØÃĸ¦ + ã¾Æ¼­ USE_MMAP_SCOREBOARD ȤÀº + USE_SHMGET_SCOREBOARDÀÎÁö È®ÀÎÇÑ´Ù. µÑÁß + Çϳª¸¦ (°¢°¢ ÇÔ²² »ç¿ëÇÒ HAVE_MMAPÀ̳ª + HAVE_SHMGETµµ °°ÀÌ) Á¤ÀÇÇÏ¸é °øÀ¯¸Þ¸ð¸® Äڵ带 + »ç¿ëÇÑ´Ù. ½Ã½ºÅÛÀÌ ´Ù¸¥ Á¾·ùÀÇ °øÀ¯¸Þ¸ð¸®¸¦ »ç¿ëÇÑ´Ù¸é + src/main/http_main.c ÆÄÀÏÀ» ¼öÁ¤ÇÏ¿© ¾ÆÆÄÄ¡¿¡¼­ + °øÀ¯¸Þ¸ð¸®¸¦ »ç¿ëÇÒ ¼ö ÀÖµµ·Ï ÈÅ(hook)À» Ãß°¡Ç϶ó. (¶ÇÇÑ + ÆÐÄ¡¸¦ ¿ì¸®¿¡°Ô º¸³»ÁÖ±æ ¹Ù¶õ´Ù.)

+ +
¿ª»çÀû ¼³¸í: ¾ÆÆÄÄ¡ÀÇ ¸®´ª½º ¹öÀüÀº ¾ÆÆÄÄ¡ 1.2 ¹öÀüºÎÅÍ + °øÀ¯¸Þ¸ð¸®¸¦ »ç¿ëÇϱ⠽ÃÀÛÇß´Ù. ¸®´ª½º¿¡¼­ Ãʱ⠾ÆÆÄÄ¡ + ¹öÀüÀÌ ´À¸®°í ½Å·Úµµ°¡ ¶³¾îÁ³±â ¶§¹®ÀÌ´Ù.
+ + + +

DYNAMIC_MODULE_LIMIT

+ + + +

¸ðµâÀ» µ¿ÀûÀ¸·Î ÀоîµéÀÌÁö ¾Ê´Â´Ù¸é (°¡´ÉÇÑ Á¶±ÝÀÌ¶óµµ + ¼º´ÉÀ» ³ôÀ̱âÀ§ÇØ ÀÌ ±ÛÀ» ÀÐ´Â´Ù¸é ¾Æ¸¶µµ ¸ðµâÀ» µ¿ÀûÀ¸·Î + ÀоîµéÀÌÁö ¾ÊÀ» °ÍÀÌ´Ù), ¼­¹ö¸¦ ÄÄÆÄÀÏÇÒ¶§ + -DDYNAMIC_MODULE_LIMIT=0À» Ãß°¡ÇÑ´Ù. ±×·¯¸é + ¸ðµâÀ» µ¿ÀûÀ¸·Î ÀоîµéÀ̱âÀ§ÇØ ÇÒ´çÇÏ´Â ¸Þ¸ð¸®¸¦ Àý¾àÇÑ´Ù.

+ + + +
top
+
+

ºÎ·Ï: ½Ã½ºÅÛÈ£Ãâ ±â·ÏÀ» ÀÚ¼¼È÷ ºÐ¼®Çϱâ

+ + + +

´ÙÀ½Àº Solaris 8¿¡¼­ worker MPMÀ» »ç¿ëÇÑ ¾ÆÆÄÄ¡ 2.0.38ÀÇ + ½Ã½ºÅÛÈ£Ãâ ±â·Ï(trace)ÀÌ´Ù. ¾Æ·¡ ¸í·É¾î¸¦ »ç¿ëÇÏ¿© ±â·ÏÀ» + ¾ò¾ú´Ù:

+ +

+ truss -l -p httpd_child_pid. +

+ +

-l ¿É¼ÇÀ» »ç¿ëÇϸé truss´Â ½Ã½ºÅÛÈ£ÃâÀ» + ÇÏ´Â LWP (lightweight process, °æ·®±Þ ÇÁ·Î¼¼½º--SolarisÀÇ + Ä¿³Î¼öÁØ ¾²·¹µå) ID¸¦ °°ÀÌ ±â·ÏÇÑ´Ù.

+ +

´Ù¸¥ ½Ã½ºÅÛ¿¡´Â strace, ktrace, + par °°Àº ½Ã½ºÅÛÈ£Ãâ ÃßÀû µµ±¸°¡ ÀÖ´Ù. °á°ú´Â + ºñ½ÁÇÏ´Ù.

+ +

Ŭ¶óÀ̾ðÆ®´Â À¥¼­¹ö¿¡°Ô Å©±â°¡ 10KBÀÎ Á¤Àû ÆÄÀÏÀ» ¿äûÇÑ´Ù. + Á¤ÀûÀÎ ÆÄÀÏÀ» ¿äûÇÏÁö ¾Ê°Å³ª ³»¿ëÇù»óÇÏ´Â ¿äûÀ» ÇÑ °æ¿ì + ±â·ÏÀÌ ¸Å¿ì ´Ù¸£´Ù (¶§·Î´Â ¸Å¿ì ¾Ë¾Æº¸±â Èûµé´Ù).

+ + 
/67:    accept(3, 0x00200BEC, 0x00200C0C, 1) (sleeping...)
+/67:    accept(3, 0x00200BEC, 0x00200C0C, 1)            = 9
+ +

À§¿¡¼­ ¿¬°á´ë±â(listener) ¾²·¹µå°¡ LWP #67¿¡¼­ ½ÇÇàµÊÀ» + ¾Ë ¼ö ÀÖ´Ù.

+ +
accept(2) Á÷·ÄÈ­¸¦ »ç¿ëÇÏÁö ¾ÊÀ½À» ÁÖ¸ñÇ϶ó. + ¿©·¯ Æ÷Æ®¸¦ ±â´Ù¸®Áö¾Ê´Â °æ¿ì ÀÌ Ç÷¡ÆûÀÇ worker MPMÀº + ±âº»ÀûÀ¸·Î Á÷·ÄÈ­ÇÏÁö ¾ÊÀº accept¸¦ »ç¿ëÇÑ´Ù.
+ + 
/65:    lwp_park(0x00000000, 0)                         = 0
+/67:    lwp_unpark(65, 1)                               = 0
+ +

¿¬°áÀº ¹Þ¾ÆµéÀÌ°í(accept) ¿¬°á´ë±â ¾²·¹µå´Â + worker ¾²·¹µå¸¦ ±ú¿ö¼­ ¿äûÀ» ó¸®ÇÏ°Ô ÇÑ´Ù. ¾Æ·¡ ±â·Ï¿¡¼­ + ¿äûÀ» ó¸®ÇÏ´Â worker ¾²·¹µå°¡ LWP #65ÀÓÀ» ¾Ë ¼ö ÀÖ´Ù.

+ + 
/65:    getsockname(9, 0x00200BA4, 0x00200BC4, 1)       = 0
+ +

°¡»óÈ£½ºÆ®¸¦ ±¸ÇöÇϱâÀ§ÇØ ¾ÆÆÄÄ¡´Â ¿¬°áÀ» ¹Þ¾ÆµéÀÎ + Áö¿ª(local) ¼ÒÄÏ ÁÖ¼Ò¸¦ ¾Ë¾Æ¾ß ÇÑ´Ù. (°¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÏÁö + ¾Ê°Å³ª Listen + Áö½Ã¾î¿¡ ¿ÍÀϵåÄ«µå ÁÖ¼Ò¸¦ »ç¿ëÇÏÁö ¾ÊÀº °æ¿ì µî) ¸¹Àº °æ¿ì + ÀÌ È£ÃâÀ» ¾ø¾Ù ¼ö ÀÖ´Ù. ±×·¯³ª ¾ÆÁ÷ ÀÌ·± ÃÖÀûÈ­ ÀÛ¾÷ÀÌ + ¾ÈµÇÀÖ´Ù.

+ + 
/65:    brk(0x002170E8)                                 = 0
+/65:    brk(0x002190E8)                                 = 0
+ +

brk(2) È£ÃâÀº Èü(heap)¿¡¼­ ¸Þ¸ð¸®¸¦ ÇÒ´çÇÑ´Ù. + À¥¼­¹ö´Â ´ëºÎºÐÀÇ ¿äû 󸮽à ÀÚü ¸Þ¸ð¸® + ÇÒ´çÀÚ(apr_pool°ú apr_bucket_alloc)¸¦ + »ç¿ëÇϱ⶧¹®¿¡ ½Ã½ºÅÛÈ£Ãâ ±â·Ï¿¡¼­ ÀÌ ½Ã½ºÅÛÈ£ÃâÀ» º¸±â°¡ + µå¹°´Ù. ÀÌ ±â·Ï¿¡¼­ À¥¼­¹ö´Â ½ÃÀÛÇÏÀÚ¸¶ÀÚ ÀÚü ¸Þ¸ð¸® ÇÒ´çÀÚ°¡ + »ç¿ëÇÒ ¸Þ¸ð¸®ºí·ÏÀ» ¾ò±âÀ§ÇØ malloc(3)À» È£ÃâÇÑ´Ù.

+ + 
/65:    fcntl(9, F_GETFL, 0x00000000)                   = 2
+/65:    fstat64(9, 0xFAF7B818)                          = 0
+/65:    getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B910, 2190656) = 0
+/65:    fstat64(9, 0xFAF7B818)                          = 0
+/65:    getsockopt(9, 65535, 8192, 0xFAF7B918, 0xFAF7B914, 2190656) = 0
+/65:    setsockopt(9, 65535, 8192, 0xFAF7B918, 4, 2190656) = 0
+/65:    fcntl(9, F_SETFL, 0x00000082)                   = 0
+ +

´ÙÀ½ worker ¾²·¹µå´Â Ŭ¶óÀ̾ðÆ®ÀÇ ¿¬°á(ÆÄÀϱâ¼úÀÚ 9)À» + ´ë±â¾ÈÇÔ(non-blocking) »óÅ·Π¹Ù²Û´Ù. setsockopt(2)¿Í + getsockopt(2) È£ÃâÀº SolarisÀÇ libc°¡ ¼ÒÄÏ¿¡ + ´ëÇÑ fcntl(2)À» ¾î¶»°Ô ó¸®ÇÏ´ÂÁö º¸¿©ÁØ´Ù.

+ + 
/65:    read(9, " G E T   / 1 0 k . h t m".., 8000)     = 97
+ +

worker ¾²·¹µå´Â Ŭ¶óÀ̾ðÆ®·Î ºÎÅÍ ¿äûÀ» Àд´Ù.

+ + 
/65:    stat("/var/httpd/apache/httpd-8999/htdocs/10k.html", 0xFAF7B978) = 0
+/65:    open("/var/httpd/apache/httpd-8999/htdocs/10k.html", O_RDONLY) = 10
+ +

À¥¼­¹ö ¼³Á¤Àº Options FollowSymLinks¿Í + AllowOverride NoneÀÌ´Ù. ±×·¡¼­ ¿äûÇÑ ÆÄÀÏ°æ·ÎÀÇ + °¢ µð·ºÅ丮¿¡ ´ëÇØ lstat(2)Çϰųª + .htaccess ÆÄÀÏÀ» °Ë»çÇÒ ÇÊ¿ä°¡ ¾ø´Ù. ÆÄÀÏÀ» + °Ë»çÇϱâÀ§ÇØ, 1) ÆÄÀÏÀÌ ÀÖ´ÂÁö, 2) µð·ºÅ丮°¡ ¾Æ´Ñ ÀϹÝÆÄÀÏÀÎÁö, + stat(2) È£Ã⸸ ÇÏ¸é µÈ´Ù.

+ + 
/65:    sendfilev(0, 9, 0x00200F90, 2, 0xFAF7B53C)      = 10269
+ +

ÀÌ °æ¿ì À¥¼­¹ö´Â ÇѹøÀÇ sendfilev(2) ½Ã½ºÅÛÈ£Ãâ·Î + HTTP ÀÀ´äÇì´õ¿Í ¿äûÇÑ ÆÄÀÏÀ» Àü¼ÛÇÒ ¼ö ÀÖ´Ù. Sendfile Áö¿ø¿©ºÎ´Â + ¿î¿µÃ¼Á¦¸¶´Ù ´Ù¸£´Ù. ´Ù¸¥ ½Ã½ºÅÛÀ̶ó¸é sendfile(2)À» + È£ÃâÇϱâ Àü¿¡ Çì´õ¸¦ º¸³»±âÀ§ÇØ write(2)³ª + writev(2) È£ÃâÀ» ÇÑ´Ù.

+ + 
/65:    write(4, " 1 2 7 . 0 . 0 . 1   -  ".., 78)      = 78
+ +

write(2) È£ÃâÀº Á¢±Ù·Î±×(access log)¿¡ ¿äûÀ» + ±â·ÏÇÑ´Ù. ÀÌ ±â·Ï¿¡ time(2) È£ÃâÀÌ ¾øÀ½À» ÁÖ¸ñÇ϶ó. + ¾ÆÆÄÄ¡ 1.3°ú ´Þ¸® ¾ÆÆÄÄ¡ 2.0Àº ½Ã°£À» ¾Ë±âÀ§ÇØ + gettimeofday(3)¸¦ »ç¿ëÇÑ´Ù. + gettimeofday¸¦ ÃÖÀûÈ­ÇÑ ¸®´ª½º¿Í Solaris °°Àº + ¸î¸î ¿î¿µÃ¼Á¦¿¡¼­´Â ÀϹÝÀûÀÎ ½Ã½ºÅÛÈ£Ã⠺δãÀÌ ¾ø´Ù.

+ + 
/65:    shutdown(9, 1, 1)                               = 0
+/65:    poll(0xFAF7B980, 1, 2000)                       = 1
+/65:    read(9, 0xFAF7BC20, 512)                        = 0
+/65:    close(9)                                        = 0
+ +

worker ¾²·¹µå´Â ¿¬°áÀ» Áö¿¬´Ý±â(lingering close)ÇÑ´Ù.

+ + 
/65:    close(10)                                       = 0
+/65:    lwp_park(0x00000000, 0)         (sleeping...)
+ +

¸¶Áö¸·À¸·Î worker ¾²·¹µå´Â ¹æ±Ý Àü¼ÛÇÑ ÆÄÀÏÀ» ´Ý°í, + ¿¬°á´ë±â(listener) ¾²·¹µå°¡ ´Ù¸¥ ¿¬°áÀ» ÇÒ´çÇÒ ¶§±îÁö + Á¤ÁöÇÑ´Ù.

+ + 
/67:    accept(3, 0x001FEB74, 0x001FEB94, 1) (sleeping...)
+ +

±×µ¿¾È ¿¬°á´ë±â ¾²·¹µå´Â ¿¬°áÀ» (¸ðµç worker°¡ ÀÛ¾÷ÁßÀ̸é + ¿¬°á´ë±â ¾²·¹µå¸¦ ¸ØÃß´Â worker MPMÀÇ È帧Á¦¾î ±â´É¿¡ µû¶ó) + worker ¾²·¹µå¿¡ ÇÒ´çÇÏÀÚ¸¶ÀÚ ´Ù¸¥ ¿¬°áÀ» ¹Þ¾ÆµéÀÏ ¼ö ÀÖ´Ù. + ÀÌ ±â·Ï¿¡´Â ³ª¿ÀÁö ¾ÊÁö¸¸, worker ¾²·¹µå°¡ ¹æ±Ý ¹ÞÀº ¿¬°áÀ» + ó¸®ÇÏ´Â µ¿¾È ´ÙÀ½ accept(2)°¡ (¿äûÀÌ ¸Å¿ì + ¸¹Àº °æ¿ì Ç×»ó) ÀϾ ¼ö ÀÖ´Ù.

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/misc/relevant_standards.html b/docs/manual/misc/relevant_standards.html new file mode 100644 index 00000000..ca9e9006 --- /dev/null +++ b/docs/manual/misc/relevant_standards.html @@ -0,0 +1,7 @@ +URI: relevant_standards.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: relevant_standards.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/misc/relevant_standards.html.en b/docs/manual/misc/relevant_standards.html.en new file mode 100644 index 00000000..f25a0890 --- /dev/null +++ b/docs/manual/misc/relevant_standards.html.en @@ -0,0 +1,199 @@ + + + +Relevant Standards - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Miscellaneous Documentation

Relevant Standards

+
+

Available Languages:  en  | + ko 

+
+ +

This page documents all the relevant standards that the + Apache HTTP Server follows, along with brief descriptions.

+ +

In addition to the information listed below, the following resources + should be consulted:

+ + + +

Notice

+

This document is not yet complete.

+
+ +
+ +
top
+
+

HTTP Recommendations

+ +

Regardless of what modules are compiled and used, Apache as a + basic web server complies with the following IETF recommendations:

+ +
+
RFC 1945 + (Informational)
+ +
The Hypertext Transfer Protocol (HTTP) is an application-level + protocol with the lightness and speed necessary for distributed, + collaborative, hypermedia information systems. This documents + HTTP/1.0.
+ +
RFC 2616 + (Standards Track)
+ +
The Hypertext Transfer Protocol (HTTP) is an + application-level protocol for distributed, collaborative, + hypermedia information systems. This documents HTTP/1.1.
+ +
RFC 2396 + (Standards Track)
+ +
A Uniform Resource Identifier (URI) is a compact string of + characters for identifying an abstract or physical resource.
+
+ +
top
+
+

HTML Recommendations

+ +

Regarding the Hypertext Markup Language, Apache complies with + the following IETF and W3C recommendations:

+ +
+
RFC 2854 + (Informational)
+ +
This document summarizes the history of HTML development, + and defines the "text/html" MIME type by pointing to the relevant + W3C recommendations.
+ +
HTML 4.01 Specification + (Errata) +
+ +
This specification defines the HyperText Markup Language (HTML), + the publishing language of the World Wide Web. This specification + defines HTML 4.01, which is a subversion of HTML 4.
+ +
HTML 3.2 Reference + Specification
+ +
The HyperText Markup Language (HTML) is a simple markup language + used to create hypertext documents that are portable from one + platform to another. HTML documents are SGML documents.
+ +
XHTML 1.1 - + Module-based XHTML + (Errata) +
+ +
This Recommendation defines a new XHTML document type + that is based upon the module framework and modules defined in + Modularization of XHTML.
+ +
XHTML 1.0 The + Extensible HyperText Markup Language (Second Edition) + (Errata) +
+ +
This specification defines the Second Edition of XHTML 1.0, + a reformulation of HTML 4 as an XML 1.0 application, and three + DTDs corresponding to the ones defined by HTML 4.
+
+ +
top
+
+

Authentication

+ +

Concerning the different methods of authentication, Apache + follows the following IETF recommendations:

+ +
+
RFC 2617 + (Draft standard)
+ +
"HTTP/1.0", includes the specification for a Basic + Access Authentication scheme.
+ +
+ +
top
+
+

Language/Country Codes

+ +

The following links document ISO and other language and country + code information:

+ +
+
ISO 639-2
+ +
ISO 639 provides two sets of language codes, one as a two-letter + code set (639-1) and another as a three-letter code set (this part + of ISO 639) for the representation of names of languages.
+ +
+ ISO 3166-1
+ +
These pages document the country names (official short names + in English) in alphabetical order as given in ISO 3166-1 and the + corresponding ISO 3166-1-alpha-2 code elements.
+ +
BCP 47 + (Best Current Practice), + RFC 3066
+ +
This document describes a language tag for use in cases where + it is desired to indicate the language used in an information + object, how to register values for use in this language tag, + and a construct for matching such language tags.
+ +
RFC 3282 + (Standards Track)
+ +
This document defines a "Content-language:" header, for use in + cases where one desires to indicate the language of something that + has RFC 822-like headers, like MIME body parts or Web documents, + and an "Accept-Language:" header for use in cases where one wishes + to indicate one's preferences with regard to language.
+
+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/misc/relevant_standards.html.ko.euc-kr b/docs/manual/misc/relevant_standards.html.ko.euc-kr new file mode 100644 index 00000000..6398c40d --- /dev/null +++ b/docs/manual/misc/relevant_standards.html.ko.euc-kr @@ -0,0 +1,191 @@ + + + +°ü·Ã Ç¥ÁØ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Miscellaneous Documentation

°ü·Ã Ç¥ÁØ

+
+

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

+
+ +

ÀÌ ¹®¼­¿¡´Â °£´ÜÇÑ ¼³¸í°ú ÇÔ²² ¾ÆÆÄÄ¡ À¥¼­¹ö°¡ µû¸£´Â + ¸ðµç °ü·Ã Ç¥ÁØÀ» ¿­°ÅÇÑ´Ù.

+ +

¾Æ·¡ Á¤º¸¿¡ ´õÇÏ¿© ´ÙÀ½ ÀÚ·áµµ »ìÆìºÁ¾ß ÇÑ´Ù:

+ + + +

ÁÖÀÇ

+

ÀÌ ¹®¼­´Â ¾ÆÁ÷ ¿ÏÀüÇÏÁö ¾Ê´Ù.

+
+ +
+ +
top
+
+

HTTP ±Ç°í

+ +

¾î¶² ¸ðµâÀ» ÄÄÆÄÀÏÇÏ°í »ç¿ëÇÏ´ÂÁö¿Í °ü°è¾øÀÌ ±âº»ÀûÀ¸·Î + À¥¼­¹öÀÎ ¾ÆÆÄÄ¡´Â ´ÙÀ½ IETF ±Ç°í(recommendation)¸¦ µû¸¥´Ù:

+ +
+
RFC 1945 + (Informational)
+ +
ÇÏÀÌÆÛÅؽºÆ® Àü¼Û ÇÁ·ÎÅäÄÝ (Hypertext Transfer Protocol, + HTTP)Àº ºÐ»ê, Çùµ¿, ÇÏÀÌÆÛ¸Åü Á¤º¸ ½Ã½ºÅÛ¿¡ ÇÊ¿äÇÑ ºü¸£°í + °¡º­¿î ¾îÇø®ÄÉÀÌ¼Ç ¼öÁØ(application-level) ÇÁ·ÎÅäÄÝÀÌ´Ù. + ÀÌ ¹®¼­´Â HTTP/1.0À» ¼³¸íÇÑ´Ù.
+ +
RFC 2616 + (Standards Track)
+ +
ÇÏÀÌÆÛÅؽºÆ® Àü¼Û ÇÁ·ÎÅäÄÝ (Hypertext Transfer Protocol, + HTTP)Àº ºÐ»ê, Çùµ¿, ÇÏÀÌÆÛ¸Åü Á¤º¸ ½Ã½ºÅÛÀ» À§ÇÑ ¾îÇø®ÄÉÀÌ¼Ç + ¼öÁØ ÇÁ·ÎÅäÄÝÀÌ´Ù. ÀÌ ¹®¼­´Â HTTP/1.1À» ¼³¸íÇÑ´Ù.
+ +
RFC 2396 + (Standards Track)
+ +
Ç¥ÁØ ÀÚ¿ø ½Äº°ÀÚ (Uniform Resource Identifier, URI)´Â + Ãß»óÀû ȤÀº ¹°¸®Àû ÀÚ¿øÀ» ½Äº°ÇϱâÀ§ÇÑ ÂªÀº ¹®ÀÚ¿­ÀÌ´Ù.
+
+ +
top
+
+

HTML ±Ç°í

+ +

ÇÏÀÌÆÛÅؽºÆ® ¸¶Å©¾÷ ¾ð¾î (Hypertext Markup Language, + HTML)¿Í °ü·ÃÇÏ¿© ¾ÆÆÄÄ¡´Â ´ÙÀ½ IETF ±Ç°í¿Í W3C ±Ç°í¸¦ µû¸¥´Ù:

+ +
+
RFC 2854 + (Informational)
+ +
ÀÌ ¹®¼­´Â HTML °³¹ß°úÁ¤À» ¿ä¾àÇÏ°í, °ü·Ã W3C ±Ç°í¸¦ + ±â¹ÝÀ¸·Î "text/html" MIME typeÀ» Á¤ÀÇÇÑ´Ù.
+ +
HTML 4.01 ±Ô¾à + (Errata) +
+ +
ÀÌ ±Ô¾àÀº ¿ùµå¿ÍÀ̵åÀ¥ÀÇ ÃâÆǾð¾îÀÎ ÇÏÀÌÆÛÅؽºÆ® ¸¶Å©¾÷ + ¾ð¾î (Hypertext Markup Language, HTML)¸¦ Á¤ÀÇÇÑ´Ù. ÀÌ + ±Ô¾àÀº HTML 4ÀÇ ÇÏÀ§¹öÀüÀÎ HTML 4.01À» Á¤ÀÇÇÑ´Ù.
+ +
HTML 3.2 Âü°í ±Ô¾à
+ +
ÇÏÀÌÆÛÅؽºÆ® ¸¶Å©¾÷ ¾ð¾î (Hypertext Markup Language, + HTML)´Â Ç÷¡Æû°ú ¹«°üÇÑ ÇÏÀÌÆÛÅؽºÆ® ¹®¼­¸¦ À§ÇÑ °£´ÜÇÑ + ¸¶Å©¾÷ ¾ð¾îÀÌ´Ù. HTML ¹®¼­´Â SGML ¹®¼­À̱⵵ ÇÏ´Ù.
+ +
XHTML 1.1 - + ¸ðµâ±â¹Ý XHTML + (Á¤¿ÀÇ¥) +
+ +
ÀÌ ±Ç°í´Â Modularization of XHTML¿¡¼­ Á¤ÀÇÇÑ ¸ðµâ + Ç÷¹ÀÓ¿öÅ©¿Í ¸ðµâµéÀ» ±â¹ÝÀ¸·Î »õ·Î¿î XHTML document typeÀ» + Á¤ÀÇÇÑ´Ù.
+ +
XHTML 1.0 + È®Àå ÇÏÀÌÆÛÅؽºÆ® ¸¶Å©¾÷ ¾ð¾î (Extensible HyperText Markup + Language) (Second Edition) + (Á¤¿ÀÇ¥) +
+ +
ÀÌ ¹®¼­´Â HTML 4¸¦ XML 1.0À¸·Î À籸¼ºÇÑ XHTML 1.0ÀÇ + µÎ¹ø° ¹öÀü°ú HTML 4¿¡ ÇØ´çÇÏ´Â ¼¼°¡Áö DTD¸¦ Á¤ÀÇÇÑ´Ù.
+
+ +
top
+
+

ÀÎÁõ

+ +

ÀÎÁõ¹æ¹ý¿¡ ´ëÇØ ¾ÆÆÄÄ¡´Â ´ÙÀ½ IETF ±Ç°í¸¦ µû¸¥´Ù:

+ +
+
RFC 2617 + (Draft standard)
+ +
Basic Access Authentication ±Ô¾àÀ» Æ÷ÇÔÇÑ "HTTP/1.0".
+ +
+ +
top
+
+

¾ð¾î/±¹°¡ ÄÚµå

+ +

¾Æ·¡ ¸µÅ©¿¡ ISO¿Í ´Ù¸¥ ¾ð¾î/±¹°¡ ÄÚµå Á¤º¸°¡ ÀÖ´Ù:

+ +
+
ISO 639-2
+ +
ISO 639´Â ¾ð¾îÀÇ À̸§À» ³ªÅ¸³»´Â µÎ°¡Áö ¾ð¾î Äڵ带 + Á¦°øÇÑ´Ù. Çϳª´Â (639-1) µÎ ±ÛÀÚ ÄÚµåÀÌ°í ´Ù¸¥ Çϳª´Â + (ÀÌ ¹®¼­) ¼¼ ±ÛÀÚ ÄÚµåÀÌ´Ù.
+ +
+ ISO 3166-1
+ +
ÀÌ ¹®¼­´Â ISO 3166-1°ú ISO 3166-1-alpha-2 Äڵ忡 µû¶ó + ¾ËÆĺª ¼ø¼­·Î (¿µ¾î·Î ªÀº °ø½ÄÀ̸§) ±¹°¡¸íÀ» ¿­°ÅÇÑ´Ù.
+ +
BCP 47 + (Best Current Practice), + RFC 3066
+ +
ÀÌ ¹®¼­´Â Á¤º¸ °´Ã¼¿¡ »ç¿ëÇÑ ¾ð¾î¸¦ ¾Ë¸®±âÀ§ÇØ »ç¿ëÇÒ + ¾ð¾î ÅÂ±×¿Í ¾ð¾î ű׿¡ »ç¿ëÇÒ °ªÀ» µî·ÏÇÏ´Â ¹æ¹ý, ¾ð¾î + ű׸¦ ã´Â ¹æ½ÄÀ» ¼³¸íÇÑ´Ù.
+ +
RFC 3282 + (Standards Track)
+ +
ÀÌ ¹®¼­´Â MIME ³»¿ë ºÎºÐ°ú À¥ ¹®¼­¿Í °°Àº RFC 822½Ä + Çì´õ°¡ ÀÖ´Â Á¤º¸ÀÇ ¾ð¾î¸¦ ¾Ë¸®±âÀ§ÇÑ "Content-language:" + Çì´õ¿Í, ¼±È£ÇÏ´Â ¾ð¾î¸¦ ³ªÅ¸³»´Â "Accept-Language:" Çì´õ¸¦ + Á¤ÀÇÇÑ´Ù.
+
+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/misc/rewriteguide.html b/docs/manual/misc/rewriteguide.html new file mode 100644 index 00000000..01caef13 --- /dev/null +++ b/docs/manual/misc/rewriteguide.html @@ -0,0 +1,7 @@ +URI: rewriteguide.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: rewriteguide.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/misc/rewriteguide.html.en b/docs/manual/misc/rewriteguide.html.en new file mode 100644 index 00000000..845a224e --- /dev/null +++ b/docs/manual/misc/rewriteguide.html.en @@ -0,0 +1,2102 @@ + + + +URL Rewriting Guide - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Miscellaneous Documentation

URL Rewriting Guide

+
+

Available Languages:  en  | + ko 

+
+ +
+

Originally written by
+ Ralf S. Engelschall <rse@apache.org>
+ December 1997

+
+ +

This document supplements the mod_rewrite + reference documentation. + It describes how one can use Apache's mod_rewrite + to solve typical URL-based problems with which webmasters are + commonly confronted. We give detailed descriptions on how to + solve each problem by configuring URL rewriting rulesets.

+ +
+ +
top
+
+

Introduction to mod_rewrite

+ + + +

The Apache module mod_rewrite is a killer + one, i.e. it is a really sophisticated module which provides + a powerful way to do URL manipulations. With it you can do nearly + all types of URL manipulations you ever dreamed about. + The price you have to pay is to accept complexity, because + mod_rewrite's major drawback is that it is + not easy to understand and use for the beginner. And even + Apache experts sometimes discover new aspects where + mod_rewrite can help.

+ +

In other words: With mod_rewrite you either + shoot yourself in the foot the first time and never use it again + or love it for the rest of your life because of its power. + This paper tries to give you a few initial success events to + avoid the first case by presenting already invented solutions + to you.

+ +
top
+
+

Practical Solutions

+ + + +

Here come a lot of practical solutions I've either invented + myself or collected from other people's solutions in the past. + Feel free to learn the black magic of URL rewriting from + these examples.

+ +
ATTENTION: Depending on your server-configuration + it can be necessary to slightly change the examples for your + situation, e.g. adding the [PT] flag when + additionally using mod_alias and + mod_userdir, etc. Or rewriting a ruleset + to fit in .htaccess context instead + of per-server context. Always try to understand what a + particular ruleset really does before you use it. It + avoid problems.
+ +
top
+
+

URL Layout

+ + + +

Canonical URLs

+ + + +
+
Description:
+ +
+

On some webservers there are more than one URL for a + resource. Usually there are canonical URLs (which should be + actually used and distributed) and those which are just + shortcuts, internal ones, etc. Independent of which URL the + user supplied with the request he should finally see the + canonical one only.

+
+ +
Solution:
+ +
+

We do an external HTTP redirect for all non-canonical + URLs to fix them in the location view of the Browser and + for all subsequent requests. In the example ruleset below + we replace /~user by the canonical + /u/user and fix a missing trailing slash for + /u/user.

+ +
+RewriteRule   ^/~([^/]+)/?(.*)    /u/$1/$2  [R]
+RewriteRule   ^/([uge])/([^/]+)$  /$1/$2/   [R]
+
+
+
+ + + +

Canonical Hostnames

+ + + +
+
Description:
+ +
...
+ +
Solution:
+ +
+
+RewriteCond %{HTTP_HOST}   !^fully\.qualified\.domain\.name [NC]
+RewriteCond %{HTTP_HOST}   !^$
+RewriteCond %{SERVER_PORT} !^80$
+RewriteRule ^/(.*)         http://fully.qualified.domain.name:%{SERVER_PORT}/$1 [L,R]
+RewriteCond %{HTTP_HOST}   !^fully\.qualified\.domain\.name [NC]
+RewriteCond %{HTTP_HOST}   !^$
+RewriteRule ^/(.*)         http://fully.qualified.domain.name/$1 [L,R]
+
+
+
+ + + +

Moved DocumentRoot

+ + + +
+
Description:
+ +
+

Usually the DocumentRoot + of the webserver directly relates to the URL "/". + But often this data is not really of top-level priority, it is + perhaps just one entity of a lot of data pools. For instance at + our Intranet sites there are /e/www/ + (the homepage for WWW), /e/sww/ (the homepage for + the Intranet) etc. Now because the data of the DocumentRoot stays at /e/www/ we had + to make sure that all inlined images and other stuff inside this + data pool work for subsequent requests.

+
+ +
Solution:
+ +
+

We redirect the URL / to + /e/www/: +

+ +
+RewriteEngine on
+RewriteRule   ^/$  /e/www/  [R]
+
+ +

Note that this can also be handled using the RedirectMatch directive:

+ +

+ RedirectMatch ^/$ http://example.com/e/www/ +

+
+
+ + + +

Trailing Slash Problem

+ + + +
+
Description:
+ +
+

Every webmaster can sing a song about the problem of + the trailing slash on URLs referencing directories. If they + are missing, the server dumps an error, because if you say + /~quux/foo instead of /~quux/foo/ + then the server searches for a file named + foo. And because this file is a directory it + complains. Actually it tries to fix it itself in most of + the cases, but sometimes this mechanism need to be emulated + by you. For instance after you have done a lot of + complicated URL rewritings to CGI scripts etc.

+
+ +
Solution:
+ +
+

The solution to this subtle problem is to let the server + add the trailing slash automatically. To do this + correctly we have to use an external redirect, so the + browser correctly requests subsequent images etc. If we + only did a internal rewrite, this would only work for the + directory page, but would go wrong when any images are + included into this page with relative URLs, because the + browser would request an in-lined object. For instance, a + request for image.gif in + /~quux/foo/index.html would become + /~quux/image.gif without the external + redirect!

+ +

So, to do this trick we write:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo$  foo/  [R]
+
+ +

The crazy and lazy can even do the following in the + top-level .htaccess file of their homedir. + But notice that this creates some processing + overhead.

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteCond    %{REQUEST_FILENAME}  -d
+RewriteRule    ^(.+[^/])$           $1/  [R]
+
+
+
+ + + +

Webcluster through Homogeneous URL Layout

+ + + +
+
Description:
+ +
+

We want to create a homogeneous and consistent URL + layout over all WWW servers on a Intranet webcluster, i.e. + all URLs (per definition server local and thus server + dependent!) become actually server independent! + What we want is to give the WWW namespace a consistent + server-independent layout: no URL should have to include + any physically correct target server. The cluster itself + should drive us automatically to the physical target + host.

+
+ +
Solution:
+ +
+

First, the knowledge of the target servers come from + (distributed) external maps which contain information + where our users, groups and entities stay. The have the + form

+ +
+user1  server_of_user1
+user2  server_of_user2
+:      :
+
+ +

We put them into files map.xxx-to-host. + Second we need to instruct all servers to redirect URLs + of the forms

+ +
+/u/user/anypath
+/g/group/anypath
+/e/entity/anypath
+
+ +

to

+ +
+http://physical-host/u/user/anypath
+http://physical-host/g/group/anypath
+http://physical-host/e/entity/anypath
+
+ +

when the URL is not locally valid to a server. The + following ruleset does this for us by the help of the map + files (assuming that server0 is a default server which + will be used if a user has no entry in the map):

+ +
+RewriteEngine on
+
+RewriteMap      user-to-host   txt:/path/to/map.user-to-host
+RewriteMap     group-to-host   txt:/path/to/map.group-to-host
+RewriteMap    entity-to-host   txt:/path/to/map.entity-to-host
+
+RewriteRule   ^/u/([^/]+)/?(.*)   http://${user-to-host:$1|server0}/u/$1/$2
+RewriteRule   ^/g/([^/]+)/?(.*)  http://${group-to-host:$1|server0}/g/$1/$2
+RewriteRule   ^/e/([^/]+)/?(.*) http://${entity-to-host:$1|server0}/e/$1/$2
+
+RewriteRule   ^/([uge])/([^/]+)/?$          /$1/$2/.www/
+RewriteRule   ^/([uge])/([^/]+)/([^.]+.+)   /$1/$2/.www/$3\
+
+
+
+ + + +

Move Homedirs to Different Webserver

+ + + +
+
Description:
+ +
+

Many webmasters have asked for a solution to the + following situation: They wanted to redirect just all + homedirs on a webserver to another webserver. They usually + need such things when establishing a newer webserver which + will replace the old one over time.

+
+ +
Solution:
+ +
+

The solution is trivial with mod_rewrite. + On the old webserver we just redirect all + /~user/anypath URLs to + http://newserver/~user/anypath.

+ +
+RewriteEngine on
+RewriteRule   ^/~(.+)  http://newserver/~$1  [R,L]
+
+
+
+ + + +

Structured Homedirs

+ + + +
+
Description:
+ +
+

Some sites with thousands of users usually use a + structured homedir layout, i.e. each homedir is in a + subdirectory which begins for instance with the first + character of the username. So, /~foo/anypath + is /home/f/foo/.www/anypath + while /~bar/anypath is + /home/b/bar/.www/anypath.

+
+ +
Solution:
+ +
+

We use the following ruleset to expand the tilde URLs + into exactly the above layout.

+ +
+RewriteEngine on
+RewriteRule   ^/~(([a-z])[a-z0-9]+)(.*)  /home/$2/$1/.www$3
+
+
+
+ + + +

Filesystem Reorganization

+ + + +
+
Description:
+ +
+

This really is a hardcore example: a killer application + which heavily uses per-directory + RewriteRules to get a smooth look and feel + on the Web while its data structure is never touched or + adjusted. Background: net.sw is + my archive of freely available Unix software packages, + which I started to collect in 1992. It is both my hobby + and job to to this, because while I'm studying computer + science I have also worked for many years as a system and + network administrator in my spare time. Every week I need + some sort of software so I created a deep hierarchy of + directories where I stored the packages:

+ +
+drwxrwxr-x   2 netsw  users    512 Aug  3 18:39 Audio/
+drwxrwxr-x   2 netsw  users    512 Jul  9 14:37 Benchmark/
+drwxrwxr-x  12 netsw  users    512 Jul  9 00:34 Crypto/
+drwxrwxr-x   5 netsw  users    512 Jul  9 00:41 Database/
+drwxrwxr-x   4 netsw  users    512 Jul 30 19:25 Dicts/
+drwxrwxr-x  10 netsw  users    512 Jul  9 01:54 Graphic/
+drwxrwxr-x   5 netsw  users    512 Jul  9 01:58 Hackers/
+drwxrwxr-x   8 netsw  users    512 Jul  9 03:19 InfoSys/
+drwxrwxr-x   3 netsw  users    512 Jul  9 03:21 Math/
+drwxrwxr-x   3 netsw  users    512 Jul  9 03:24 Misc/
+drwxrwxr-x   9 netsw  users    512 Aug  1 16:33 Network/
+drwxrwxr-x   2 netsw  users    512 Jul  9 05:53 Office/
+drwxrwxr-x   7 netsw  users    512 Jul  9 09:24 SoftEng/
+drwxrwxr-x   7 netsw  users    512 Jul  9 12:17 System/
+drwxrwxr-x  12 netsw  users    512 Aug  3 20:15 Typesetting/
+drwxrwxr-x  10 netsw  users    512 Jul  9 14:08 X11/
+
+ +

In July 1996 I decided to make this archive public to + the world via a nice Web interface. "Nice" means that I + wanted to offer an interface where you can browse + directly through the archive hierarchy. And "nice" means + that I didn't wanted to change anything inside this + hierarchy - not even by putting some CGI scripts at the + top of it. Why? Because the above structure should be + later accessible via FTP as well, and I didn't want any + Web or CGI stuff to be there.

+
+ +
Solution:
+ +
+

The solution has two parts: The first is a set of CGI + scripts which create all the pages at all directory + levels on-the-fly. I put them under + /e/netsw/.www/ as follows:

+ +
+-rw-r--r--   1 netsw  users    1318 Aug  1 18:10 .wwwacl
+drwxr-xr-x  18 netsw  users     512 Aug  5 15:51 DATA/
+-rw-rw-rw-   1 netsw  users  372982 Aug  5 16:35 LOGFILE
+-rw-r--r--   1 netsw  users     659 Aug  4 09:27 TODO
+-rw-r--r--   1 netsw  users    5697 Aug  1 18:01 netsw-about.html
+-rwxr-xr-x   1 netsw  users     579 Aug  2 10:33 netsw-access.pl
+-rwxr-xr-x   1 netsw  users    1532 Aug  1 17:35 netsw-changes.cgi
+-rwxr-xr-x   1 netsw  users    2866 Aug  5 14:49 netsw-home.cgi
+drwxr-xr-x   2 netsw  users     512 Jul  8 23:47 netsw-img/
+-rwxr-xr-x   1 netsw  users   24050 Aug  5 15:49 netsw-lsdir.cgi
+-rwxr-xr-x   1 netsw  users    1589 Aug  3 18:43 netsw-search.cgi
+-rwxr-xr-x   1 netsw  users    1885 Aug  1 17:41 netsw-tree.cgi
+-rw-r--r--   1 netsw  users     234 Jul 30 16:35 netsw-unlimit.lst
+
+ +

The DATA/ subdirectory holds the above + directory structure, i.e. the real + net.sw stuff and gets + automatically updated via rdist from time to + time. The second part of the problem remains: how to link + these two structures together into one smooth-looking URL + tree? We want to hide the DATA/ directory + from the user while running the appropriate CGI scripts + for the various URLs. Here is the solution: first I put + the following into the per-directory configuration file + in the DocumentRoot + of the server to rewrite the announced URL + /net.sw/ to the internal path + /e/netsw:

+ +
+RewriteRule  ^net.sw$       net.sw/        [R]
+RewriteRule  ^net.sw/(.*)$  e/netsw/$1
+
+ +

The first rule is for requests which miss the trailing + slash! The second rule does the real thing. And then + comes the killer configuration which stays in the + per-directory config file + /e/netsw/.www/.wwwacl:

+ +
+Options       ExecCGI FollowSymLinks Includes MultiViews
+
+RewriteEngine on
+
+#  we are reached via /net.sw/ prefix
+RewriteBase   /net.sw/
+
+#  first we rewrite the root dir to
+#  the handling cgi script
+RewriteRule   ^$                       netsw-home.cgi     [L]
+RewriteRule   ^index\.html$            netsw-home.cgi     [L]
+
+#  strip out the subdirs when
+#  the browser requests us from perdir pages
+RewriteRule   ^.+/(netsw-[^/]+/.+)$    $1                 [L]
+
+#  and now break the rewriting for local files
+RewriteRule   ^netsw-home\.cgi.*       -                  [L]
+RewriteRule   ^netsw-changes\.cgi.*    -                  [L]
+RewriteRule   ^netsw-search\.cgi.*     -                  [L]
+RewriteRule   ^netsw-tree\.cgi$        -                  [L]
+RewriteRule   ^netsw-about\.html$      -                  [L]
+RewriteRule   ^netsw-img/.*$           -                  [L]
+
+#  anything else is a subdir which gets handled
+#  by another cgi script
+RewriteRule   !^netsw-lsdir\.cgi.*     -                  [C]
+RewriteRule   (.*)                     netsw-lsdir.cgi/$1
+
+ +

Some hints for interpretation:

+ +
    +
  1. Notice the L (last) flag and no + substitution field ('-') in the forth part
    2. + +
  2. Notice the ! (not) character and + the C (chain) flag at the first rule + in the last part
    3. + +
  3. Notice the catch-all pattern in the last rule
    4. +
+
+
+ + + +

NCSA imagemap to Apache mod_imagemap

+ + + +
+
Description:
+ +
+

When switching from the NCSA webserver to the more + modern Apache webserver a lot of people want a smooth + transition. So they want pages which use their old NCSA + imagemap program to work under Apache with the + modern mod_imagemap. The problem is that there + are a lot of hyperlinks around which reference the + imagemap program via + /cgi-bin/imagemap/path/to/page.map. Under + Apache this has to read just + /path/to/page.map.

+
+ +
Solution:
+ +
+

We use a global rule to remove the prefix on-the-fly for + all requests:

+ +
+RewriteEngine  on
+RewriteRule    ^/cgi-bin/imagemap(.*)  $1  [PT]
+
+
+
+ + + +

Search pages in more than one directory

+ + + +
+
Description:
+ +
+

Sometimes it is necessary to let the webserver search + for pages in more than one directory. Here MultiViews or + other techniques cannot help.

+
+ +
Solution:
+ +
+

We program a explicit ruleset which searches for the + files in the directories.

+ +
+RewriteEngine on
+
+#   first try to find it in custom/...
+#   ...and if found stop and be happy:
+RewriteCond         /your/docroot/dir1/%{REQUEST_FILENAME}  -f
+RewriteRule  ^(.+)  /your/docroot/dir1/$1  [L]
+
+#   second try to find it in pub/...
+#   ...and if found stop and be happy:
+RewriteCond         /your/docroot/dir2/%{REQUEST_FILENAME}  -f
+RewriteRule  ^(.+)  /your/docroot/dir2/$1  [L]
+
+#   else go on for other Alias or ScriptAlias directives,
+#   etc.
+RewriteRule   ^(.+)  -  [PT]
+
+
+
+ + + +

Set Environment Variables According To URL Parts

+ + + +
+
Description:
+ +
+

Perhaps you want to keep status information between + requests and use the URL to encode it. But you don't want + to use a CGI wrapper for all pages just to strip out this + information.

+
+ +
Solution:
+ +
+

We use a rewrite rule to strip out the status information + and remember it via an environment variable which can be + later dereferenced from within XSSI or CGI. This way a + URL /foo/S=java/bar/ gets translated to + /foo/bar/ and the environment variable named + STATUS is set to the value "java".

+ +
+RewriteEngine on
+RewriteRule   ^(.*)/S=([^/]+)/(.*)    $1/$3 [E=STATUS:$2]
+
+
+
+ + + +

Virtual User Hosts

+ + + +
+
Description:
+ +
+

Assume that you want to provide + www.username.host.domain.com + for the homepage of username via just DNS A records to the + same machine and without any virtualhosts on this + machine.

+
+ +
Solution:
+ +
+

For HTTP/1.0 requests there is no solution, but for + HTTP/1.1 requests which contain a Host: HTTP header we + can use the following ruleset to rewrite + http://www.username.host.com/anypath + internally to /home/username/anypath:

+ +
+RewriteEngine on
+RewriteCond   %{HTTP_HOST}                 ^www\.[^.]+\.host\.com$
+RewriteRule   ^(.+)                        %{HTTP_HOST}$1          [C]
+RewriteRule   ^www\.([^.]+)\.host\.com(.*) /home/$1$2
+
+
+
+ + + +

Redirect Homedirs For Foreigners

+ + + +
+
Description:
+ +
+

We want to redirect homedir URLs to another webserver + www.somewhere.com when the requesting user + does not stay in the local domain + ourdomain.com. This is sometimes used in + virtual host contexts.

+
+ +
Solution:
+ +
+

Just a rewrite condition:

+ +
+RewriteEngine on
+RewriteCond   %{REMOTE_HOST}  !^.+\.ourdomain\.com$
+RewriteRule   ^(/~.+)         http://www.somewhere.com/$1 [R,L]
+
+
+
+ + + +

Redirect Failing URLs To Other Webserver

+ + + +
+
Description:
+ +
+

A typical FAQ about URL rewriting is how to redirect + failing requests on webserver A to webserver B. Usually + this is done via ErrorDocument CGI-scripts in Perl, but + there is also a mod_rewrite solution. + But notice that this performs more poorly than using an + ErrorDocument + CGI-script!

+
+ +
Solution:
+ +
+

The first solution has the best performance but less + flexibility, and is less error safe:

+ +
+RewriteEngine on
+RewriteCond   /your/docroot/%{REQUEST_FILENAME} !-f
+RewriteRule   ^(.+)                             http://webserverB.dom/$1
+
+ +

The problem here is that this will only work for pages + inside the DocumentRoot. While you can add more + Conditions (for instance to also handle homedirs, etc.) + there is better variant:

+ +
+RewriteEngine on
+RewriteCond   %{REQUEST_URI} !-U
+RewriteRule   ^(.+)          http://webserverB.dom/$1
+
+ +

This uses the URL look-ahead feature of mod_rewrite. + The result is that this will work for all types of URLs + and is a safe way. But it does a performance impact on + the webserver, because for every request there is one + more internal subrequest. So, if your webserver runs on a + powerful CPU, use this one. If it is a slow machine, use + the first approach or better a ErrorDocument CGI-script.

+
+
+ + + +

Extended Redirection

+ + + +
+
Description:
+ +
+

Sometimes we need more control (concerning the + character escaping mechanism) of URLs on redirects. + Usually the Apache kernels URL escape function also + escapes anchors, i.e. URLs like "url#anchor". + You cannot use this directly on redirects with + mod_rewrite because the + uri_escape() function of Apache + would also escape the hash character. + How can we redirect to such a URL?

+
+ +
Solution:
+ +
+

We have to use a kludge by the use of a NPH-CGI script + which does the redirect itself. Because here no escaping + is done (NPH=non-parseable headers). First we introduce a + new URL scheme xredirect: by the following + per-server config-line (should be one of the last rewrite + rules):

+ +
+RewriteRule ^xredirect:(.+) /path/to/nph-xredirect.cgi/$1 \
+            [T=application/x-httpd-cgi,L]
+
+ +

This forces all URLs prefixed with + xredirect: to be piped through the + nph-xredirect.cgi program. And this program + just looks like:

+ +
+#!/path/to/perl
+##
+##  nph-xredirect.cgi -- NPH/CGI script for extended redirects
+##  Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved.
+##
+
+$| = 1;
+$url = $ENV{'PATH_INFO'};
+
+print "HTTP/1.0 302 Moved Temporarily\n";
+print "Server: $ENV{'SERVER_SOFTWARE'}\n";
+print "Location: $url\n";
+print "Content-type: text/html\n";
+print "\n";
+print "<html>\n";
+print "<head>\n";
+print "<title>302 Moved Temporarily (EXTENDED)</title>\n";
+print "</head>\n";
+print "<body>\n";
+print "<h1>Moved Temporarily (EXTENDED)</h1>\n";
+print "The document has moved <a HREF=\"$url\">here</a>.<p>\n";
+print "</body>\n";
+print "</html>\n";
+
+##EOF##
+
+ +

This provides you with the functionality to do + redirects to all URL schemes, i.e. including the one + which are not directly accepted by mod_rewrite. + For instance you can now also redirect to + news:newsgroup via

+ +
+RewriteRule ^anyurl  xredirect:news:newsgroup
+
+ +
Notice: You have not to put [R] or + [R,L] to the above rule because the + xredirect: need to be expanded later + by our special "pipe through" rule above.
+
+
+ + + +

Archive Access Multiplexer

+ + + +
+
Description:
+ +
+

Do you know the great CPAN (Comprehensive Perl Archive + Network) under http://www.perl.com/CPAN? + This does a redirect to one of several FTP servers around + the world which carry a CPAN mirror and is approximately + near the location of the requesting client. Actually this + can be called an FTP access multiplexing service. While + CPAN runs via CGI scripts, how can a similar approach + implemented via mod_rewrite?

+
+ +
Solution:
+ +
+

First we notice that from version 3.0.0 + mod_rewrite can + also use the "ftp:" scheme on redirects. + And second, the location approximation can be done by a + RewriteMap + over the top-level domain of the client. + With a tricky chained ruleset we can use this top-level + domain as a key to our multiplexing map.

+ +
+RewriteEngine on
+RewriteMap    multiplex                txt:/path/to/map.cxan
+RewriteRule   ^/CxAN/(.*)              %{REMOTE_HOST}::$1                 [C]
+RewriteRule   ^.+\.([a-zA-Z]+)::(.*)$  ${multiplex:$1|ftp.default.dom}$2  [R,L]
+
+ +
+##
+##  map.cxan -- Multiplexing Map for CxAN
+##
+
+de        ftp://ftp.cxan.de/CxAN/
+uk        ftp://ftp.cxan.uk/CxAN/
+com       ftp://ftp.cxan.com/CxAN/
+ :
+##EOF##
+
+
+
+ + + +

Time-Dependent Rewriting

+ + + +
+
Description:
+ +
+

When tricks like time-dependent content should happen a + lot of webmasters still use CGI scripts which do for + instance redirects to specialized pages. How can it be done + via mod_rewrite?

+
+ +
Solution:
+ +
+

There are a lot of variables named TIME_xxx + for rewrite conditions. In conjunction with the special + lexicographic comparison patterns <STRING, + >STRING and =STRING we can + do time-dependent redirects:

+ +
+RewriteEngine on
+RewriteCond   %{TIME_HOUR}%{TIME_MIN} >0700
+RewriteCond   %{TIME_HOUR}%{TIME_MIN} <1900
+RewriteRule   ^foo\.html$             foo.day.html
+RewriteRule   ^foo\.html$             foo.night.html
+
+ +

This provides the content of foo.day.html + under the URL foo.html from + 07:00-19:00 and at the remaining time the + contents of foo.night.html. Just a nice + feature for a homepage...

+
+
+ + + +

Backward Compatibility for YYYY to XXXX migration

+ + + +
+
Description:
+ +
+

How can we make URLs backward compatible (still + existing virtually) after migrating document.YYYY + to document.XXXX, e.g. after translating a + bunch of .html files to .phtml?

+
+ +
Solution:
+ +
+

We just rewrite the name to its basename and test for + existence of the new extension. If it exists, we take + that name, else we rewrite the URL to its original state.

+ + +
+#   backward compatibility ruleset for
+#   rewriting document.html to document.phtml
+#   when and only when document.phtml exists
+#   but no longer document.html
+RewriteEngine on
+RewriteBase   /~quux/
+#   parse out basename, but remember the fact
+RewriteRule   ^(.*)\.html$              $1      [C,E=WasHTML:yes]
+#   rewrite to document.phtml if exists
+RewriteCond   %{REQUEST_FILENAME}.phtml -f
+RewriteRule   ^(.*)$ $1.phtml                   [S=1]
+#   else reverse the previous basename cutout
+RewriteCond   %{ENV:WasHTML}            ^yes$
+RewriteRule   ^(.*)$ $1.html
+
+
+
+ + + +
top
+
+

Content Handling

+ + + +

From Old to New (intern)

+ + + +
+
Description:
+ +
+

Assume we have recently renamed the page + foo.html to bar.html and now want + to provide the old URL for backward compatibility. Actually + we want that users of the old URL even not recognize that + the pages was renamed.

+
+ +
Solution:
+ +
+

We rewrite the old URL to the new one internally via the + following rule:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  bar.html
+
+
+
+ + + +

From Old to New (extern)

+ + + +
+
Description:
+ +
+

Assume again that we have recently renamed the page + foo.html to bar.html and now want + to provide the old URL for backward compatibility. But this + time we want that the users of the old URL get hinted to + the new one, i.e. their browsers Location field should + change, too.

+
+ +
Solution:
+ +
+

We force a HTTP redirect to the new URL which leads to a + change of the browsers and thus the users view:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  bar.html  [R]
+
+
+
+ + + +

Browser Dependent Content

+ + + +
+
Description:
+ +
+

At least for important top-level pages it is sometimes + necessary to provide the optimum of browser dependent + content, i.e. one has to provide a maximum version for the + latest Netscape variants, a minimum version for the Lynx + browsers and a average feature version for all others.

+
+ +
Solution:
+ +
+

We cannot use content negotiation because the browsers do + not provide their type in that form. Instead we have to + act on the HTTP header "User-Agent". The following condig + does the following: If the HTTP header "User-Agent" + begins with "Mozilla/3", the page foo.html + is rewritten to foo.NS.html and and the + rewriting stops. If the browser is "Lynx" or "Mozilla" of + version 1 or 2 the URL becomes foo.20.html. + All other browsers receive page foo.32.html. + This is done by the following ruleset:

+ +
+RewriteCond %{HTTP_USER_AGENT}  ^Mozilla/3.*
+RewriteRule ^foo\.html$         foo.NS.html          [L]
+
+RewriteCond %{HTTP_USER_AGENT}  ^Lynx/.*         [OR]
+RewriteCond %{HTTP_USER_AGENT}  ^Mozilla/[12].*
+RewriteRule ^foo\.html$         foo.20.html          [L]
+
+RewriteRule ^foo\.html$         foo.32.html          [L]
+
+
+
+ + + +

Dynamic Mirror

+ + + +
+
Description:
+ +
+

Assume there are nice webpages on remote hosts we want + to bring into our namespace. For FTP servers we would use + the mirror program which actually maintains an + explicit up-to-date copy of the remote data on the local + machine. For a webserver we could use the program + webcopy which acts similar via HTTP. But both + techniques have one major drawback: The local copy is + always just as up-to-date as often we run the program. It + would be much better if the mirror is not a static one we + have to establish explicitly. Instead we want a dynamic + mirror with data which gets updated automatically when + there is need (updated data on the remote host).

+
+ +
Solution:
+ +
+

To provide this feature we map the remote webpage or even + the complete remote webarea to our namespace by the use + of the Proxy Throughput feature + (flag [P]):

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^hotsheet/(.*)$  http://www.tstimpreso.com/hotsheet/$1  [P]
+
+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^usa-news\.html$   http://www.quux-corp.com/news/index.html  [P]
+
+
+
+ + + +

Reverse Dynamic Mirror

+ + + +
+
Description:
+ +
...
+ +
Solution:
+ +
+
+RewriteEngine on
+RewriteCond   /mirror/of/remotesite/$1           -U
+RewriteRule   ^http://www\.remotesite\.com/(.*)$ /mirror/of/remotesite/$1
+
+
+
+ + + +

Retrieve Missing Data from Intranet

+ + + +
+
Description:
+ +
+

This is a tricky way of virtually running a corporate + (external) Internet webserver + (www.quux-corp.dom), while actually keeping + and maintaining its data on a (internal) Intranet webserver + (www2.quux-corp.dom) which is protected by a + firewall. The trick is that on the external webserver we + retrieve the requested data on-the-fly from the internal + one.

+
+ +
Solution:
+ +
+

First, we have to make sure that our firewall still + protects the internal webserver and that only the + external webserver is allowed to retrieve data from it. + For a packet-filtering firewall we could for instance + configure a firewall ruleset like the following:

+ +
+ALLOW Host www.quux-corp.dom Port >1024 --> Host www2.quux-corp.dom Port 80
+DENY  Host *                 Port *     --> Host www2.quux-corp.dom Port 80
+
+ +

Just adjust it to your actual configuration syntax. + Now we can establish the mod_rewrite + rules which request the missing data in the background + through the proxy throughput feature:

+ +
+RewriteRule ^/~([^/]+)/?(.*)          /home/$1/.www/$2
+RewriteCond %{REQUEST_FILENAME}       !-f
+RewriteCond %{REQUEST_FILENAME}       !-d
+RewriteRule ^/home/([^/]+)/.www/?(.*) http://www2.quux-corp.dom/~$1/pub/$2 [P]
+
+
+
+ + + +

Load Balancing

+ + + +
+
Description:
+ +
+

Suppose we want to load balance the traffic to + www.foo.com over www[0-5].foo.com + (a total of 6 servers). How can this be done?

+
+ +
Solution:
+ +
+

There are a lot of possible solutions for this problem. + We will discuss first a commonly known DNS-based variant + and then the special one with mod_rewrite:

+ +
    +
  1. + DNS Round-Robin + +

    The simplest method for load-balancing is to use + the DNS round-robin feature of BIND. + Here you just configure www[0-9].foo.com + as usual in your DNS with A(address) records, e.g.

    + +
    +www0   IN  A       1.2.3.1
+www1   IN  A       1.2.3.2
+www2   IN  A       1.2.3.3
+www3   IN  A       1.2.3.4
+www4   IN  A       1.2.3.5
+www5   IN  A       1.2.3.6
+
    + +

    Then you additionally add the following entry:

    + +
    +www    IN  CNAME   www0.foo.com.
+       IN  CNAME   www1.foo.com.
+       IN  CNAME   www2.foo.com.
+       IN  CNAME   www3.foo.com.
+       IN  CNAME   www4.foo.com.
+       IN  CNAME   www5.foo.com.
+       IN  CNAME   www6.foo.com.
+
    + +

    Notice that this seems wrong, but is actually an + intended feature of BIND and can be used + in this way. However, now when www.foo.com gets + resolved, BIND gives out www0-www6 + - but in a slightly permutated/rotated order every time. + This way the clients are spread over the various + servers. But notice that this not a perfect load + balancing scheme, because DNS resolve information + gets cached by the other nameservers on the net, so + once a client has resolved www.foo.com + to a particular wwwN.foo.com, all + subsequent requests also go to this particular name + wwwN.foo.com. But the final result is + ok, because the total sum of the requests are really + spread over the various webservers.

    +
    2. + +
  2. + DNS Load-Balancing + +

    A sophisticated DNS-based method for + load-balancing is to use the program + lbnamed which can be found at + http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html. + It is a Perl 5 program in conjunction with auxilliary + tools which provides a real load-balancing for + DNS.

    +
    3. + +
  3. + Proxy Throughput Round-Robin + +

    In this variant we use mod_rewrite + and its proxy throughput feature. First we dedicate + www0.foo.com to be actually + www.foo.com by using a single

    + +
    +www    IN  CNAME   www0.foo.com.
+
    + +

    entry in the DNS. Then we convert + www0.foo.com to a proxy-only server, + i.e. we configure this machine so all arriving URLs + are just pushed through the internal proxy to one of + the 5 other servers (www1-www5). To + accomplish this we first establish a ruleset which + contacts a load balancing script lb.pl + for all URLs.

    + +
    +RewriteEngine on
+RewriteMap    lb      prg:/path/to/lb.pl
+RewriteRule   ^/(.+)$ ${lb:$1}           [P,L]
+
    + +

    Then we write lb.pl:

    + +
    +#!/path/to/perl
+##
+##  lb.pl -- load balancing script
+##
+
+$| = 1;
+
+$name   = "www";     # the hostname base
+$first  = 1;         # the first server (not 0 here, because 0 is myself)
+$last   = 5;         # the last server in the round-robin
+$domain = "foo.dom"; # the domainname
+
+$cnt = 0;
+while (<STDIN>) {
+    $cnt = (($cnt+1) % ($last+1-$first));
+    $server = sprintf("%s%d.%s", $name, $cnt+$first, $domain);
+    print "http://$server/$_";
+}
+
+##EOF##
+
    + +
    A last notice: Why is this useful? Seems like + www0.foo.com still is overloaded? The + answer is yes, it is overloaded, but with plain proxy + throughput requests, only! All SSI, CGI, ePerl, etc. + processing is completely done on the other machines. + This is the essential point.
    +
    4. + +
  4. + Hardware/TCP Round-Robin + +

    There is a hardware solution available, too. Cisco + has a beast called LocalDirector which does a load + balancing at the TCP/IP level. Actually this is some + sort of a circuit level gateway in front of a + webcluster. If you have enough money and really need + a solution with high performance, use this one.

    +
    5. +
+
+
+ + + +

New MIME-type, New Service

+ + + +
+
Description:
+ +
+

On the net there are a lot of nifty CGI programs. But + their usage is usually boring, so a lot of webmaster + don't use them. Even Apache's Action handler feature for + MIME-types is only appropriate when the CGI programs + don't need special URLs (actually PATH_INFO + and QUERY_STRINGS) as their input. First, + let us configure a new file type with extension + .scgi (for secure CGI) which will be processed + by the popular cgiwrap program. The problem + here is that for instance we use a Homogeneous URL Layout + (see above) a file inside the user homedirs has the URL + /u/user/foo/bar.scgi. But + cgiwrap needs the URL in the form + /~user/foo/bar.scgi/. The following rule + solves the problem:

+ +
+RewriteRule ^/[uge]/([^/]+)/\.www/(.+)\.scgi(.*) ...
+... /internal/cgi/user/cgiwrap/~$1/$2.scgi$3  [NS,T=application/x-http-cgi]
+
+ +

Or assume we have some more nifty programs: + wwwlog (which displays the + access.log for a URL subtree and + wwwidx (which runs Glimpse on a URL + subtree). We have to provide the URL area to these + programs so they know on which area they have to act on. + But usually this ugly, because they are all the times + still requested from that areas, i.e. typically we would + run the swwidx program from within + /u/user/foo/ via hyperlink to

+ +
+/internal/cgi/user/swwidx?i=/u/user/foo/
+
+ +

which is ugly. Because we have to hard-code + both the location of the area + and the location of the CGI inside the + hyperlink. When we have to reorganize the area, we spend a + lot of time changing the various hyperlinks.

+
+ +
Solution:
+ +
+

The solution here is to provide a special new URL format + which automatically leads to the proper CGI invocation. + We configure the following:

+ +
+RewriteRule   ^/([uge])/([^/]+)(/?.*)/\*  /internal/cgi/user/wwwidx?i=/$1/$2$3/
+RewriteRule   ^/([uge])/([^/]+)(/?.*):log /internal/cgi/user/wwwlog?f=/$1/$2$3
+
+ +

Now the hyperlink to search at + /u/user/foo/ reads only

+ +
+HREF="*"
+
+ +

which internally gets automatically transformed to

+ +
+/internal/cgi/user/wwwidx?i=/u/user/foo/
+
+ +

The same approach leads to an invocation for the + access log CGI program when the hyperlink + :log gets used.

+
+
+ + + +

From Static to Dynamic

+ + + +
+
Description:
+ +
+

How can we transform a static page + foo.html into a dynamic variant + foo.cgi in a seamless way, i.e. without notice + by the browser/user.

+
+ +
Solution:
+ +
+

We just rewrite the URL to the CGI-script and force the + correct MIME-type so it gets really run as a CGI-script. + This way a request to /~quux/foo.html + internally leads to the invocation of + /~quux/foo.cgi.

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  foo.cgi  [T=application/x-httpd-cgi]
+
+
+
+ + + +

On-the-fly Content-Regeneration

+ + + +
+
Description:
+ +
+

Here comes a really esoteric feature: Dynamically + generated but statically served pages, i.e. pages should be + delivered as pure static pages (read from the filesystem + and just passed through), but they have to be generated + dynamically by the webserver if missing. This way you can + have CGI-generated pages which are statically served unless + one (or a cronjob) removes the static contents. Then the + contents gets refreshed.

+
+ +
Solution:
+ +
+ This is done via the following ruleset: + +
+RewriteCond %{REQUEST_FILENAME}   !-s
+RewriteRule ^page\.html$          page.cgi   [T=application/x-httpd-cgi,L]
+
+ +

Here a request to page.html leads to a + internal run of a corresponding page.cgi if + page.html is still missing or has filesize + null. The trick here is that page.cgi is a + usual CGI script which (additionally to its STDOUT) + writes its output to the file page.html. + Once it was run, the server sends out the data of + page.html. When the webmaster wants to force + a refresh the contents, he just removes + page.html (usually done by a cronjob).

+
+
+ + + +

Document With Autorefresh

+ + + +
+
Description:
+ +
+

Wouldn't it be nice while creating a complex webpage if + the webbrowser would automatically refresh the page every + time we write a new version from within our editor? + Impossible?

+
+ +
Solution:
+ +
+

No! We just combine the MIME multipart feature, the + webserver NPH feature and the URL manipulation power of + mod_rewrite. First, we establish a new + URL feature: Adding just :refresh to any + URL causes this to be refreshed every time it gets + updated on the filesystem.

+ +
+RewriteRule   ^(/[uge]/[^/]+/?.*):refresh  /internal/cgi/apache/nph-refresh?f=$1
+
+ +

Now when we reference the URL

+ +
+/u/foo/bar/page.html:refresh
+
+ +

this leads to the internal invocation of the URL

+ +
+/internal/cgi/apache/nph-refresh?f=/u/foo/bar/page.html
+
+ +

The only missing part is the NPH-CGI script. Although + one would usually say "left as an exercise to the reader" + ;-) I will provide this, too.

+ +
+#!/sw/bin/perl
+##
+##  nph-refresh -- NPH/CGI script for auto refreshing pages
+##  Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved.
+##
+$| = 1;
+
+#   split the QUERY_STRING variable
+@pairs = split(/&/, $ENV{'QUERY_STRING'});
+foreach $pair (@pairs) {
+    ($name, $value) = split(/=/, $pair);
+    $name =~ tr/A-Z/a-z/;
+    $name = 'QS_' . $name;
+    $value =~ s/%([a-fA-F0-9][a-fA-F0-9])/pack("C", hex($1))/eg;
+    eval "\$$name = \"$value\"";
+}
+$QS_s = 1 if ($QS_s eq '');
+$QS_n = 3600 if ($QS_n eq '');
+if ($QS_f eq '') {
+    print "HTTP/1.0 200 OK\n";
+    print "Content-type: text/html\n\n";
+    print "&lt;b&gt;ERROR&lt;/b&gt;: No file given\n";
+    exit(0);
+}
+if (! -f $QS_f) {
+    print "HTTP/1.0 200 OK\n";
+    print "Content-type: text/html\n\n";
+    print "&lt;b&gt;ERROR&lt;/b&gt;: File $QS_f not found\n";
+    exit(0);
+}
+
+sub print_http_headers_multipart_begin {
+    print "HTTP/1.0 200 OK\n";
+    $bound = "ThisRandomString12345";
+    print "Content-type: multipart/x-mixed-replace;boundary=$bound\n";
+    &print_http_headers_multipart_next;
+}
+
+sub print_http_headers_multipart_next {
+    print "\n--$bound\n";
+}
+
+sub print_http_headers_multipart_end {
+    print "\n--$bound--\n";
+}
+
+sub displayhtml {
+    local($buffer) = @_;
+    $len = length($buffer);
+    print "Content-type: text/html\n";
+    print "Content-length: $len\n\n";
+    print $buffer;
+}
+
+sub readfile {
+    local($file) = @_;
+    local(*FP, $size, $buffer, $bytes);
+    ($x, $x, $x, $x, $x, $x, $x, $size) = stat($file);
+    $size = sprintf("%d", $size);
+    open(FP, "&lt;$file");
+    $bytes = sysread(FP, $buffer, $size);
+    close(FP);
+    return $buffer;
+}
+
+$buffer = &readfile($QS_f);
+&print_http_headers_multipart_begin;
+&displayhtml($buffer);
+
+sub mystat {
+    local($file) = $_[0];
+    local($time);
+
+    ($x, $x, $x, $x, $x, $x, $x, $x, $x, $mtime) = stat($file);
+    return $mtime;
+}
+
+$mtimeL = &mystat($QS_f);
+$mtime = $mtime;
+for ($n = 0; $n &lt; $QS_n; $n++) {
+    while (1) {
+        $mtime = &mystat($QS_f);
+        if ($mtime ne $mtimeL) {
+            $mtimeL = $mtime;
+            sleep(2);
+            $buffer = &readfile($QS_f);
+            &print_http_headers_multipart_next;
+            &displayhtml($buffer);
+            sleep(5);
+            $mtimeL = &mystat($QS_f);
+            last;
+        }
+        sleep($QS_s);
+    }
+}
+
+&print_http_headers_multipart_end;
+
+exit(0);
+
+##EOF##
+
+
+
+ + + +

Mass Virtual Hosting

+ + + +
+
Description:
+ +
+

The <VirtualHost> feature of Apache is nice + and works great when you just have a few dozens + virtual hosts. But when you are an ISP and have hundreds of + virtual hosts to provide this feature is not the best + choice.

+
+ +
Solution:
+ +
+

To provide this feature we map the remote webpage or even + the complete remote webarea to our namespace by the use + of the Proxy Throughput feature (flag [P]):

+ +
+##
+##  vhost.map
+##
+www.vhost1.dom:80  /path/to/docroot/vhost1
+www.vhost2.dom:80  /path/to/docroot/vhost2
+     :
+www.vhostN.dom:80  /path/to/docroot/vhostN
+
+ +
+##
+##  httpd.conf
+##
+    :
+#   use the canonical hostname on redirects, etc.
+UseCanonicalName on
+
+    :
+#   add the virtual host in front of the CLF-format
+CustomLog  /path/to/access_log  "%{VHOST}e %h %l %u %t \"%r\" %>s %b"
+    :
+
+#   enable the rewriting engine in the main server
+RewriteEngine on
+
+#   define two maps: one for fixing the URL and one which defines
+#   the available virtual hosts with their corresponding
+#   DocumentRoot.
+RewriteMap    lowercase    int:tolower
+RewriteMap    vhost        txt:/path/to/vhost.map
+
+#   Now do the actual virtual host mapping
+#   via a huge and complicated single rule:
+#
+#   1. make sure we don't map for common locations
+RewriteCond   %{REQUEST_URL}  !^/commonurl1/.*
+RewriteCond   %{REQUEST_URL}  !^/commonurl2/.*
+    :
+RewriteCond   %{REQUEST_URL}  !^/commonurlN/.*
+#
+#   2. make sure we have a Host header, because
+#      currently our approach only supports
+#      virtual hosting through this header
+RewriteCond   %{HTTP_HOST}  !^$
+#
+#   3. lowercase the hostname
+RewriteCond   ${lowercase:%{HTTP_HOST}|NONE}  ^(.+)$
+#
+#   4. lookup this hostname in vhost.map and
+#      remember it only when it is a path
+#      (and not "NONE" from above)
+RewriteCond   ${vhost:%1}  ^(/.*)$
+#
+#   5. finally we can map the URL to its docroot location
+#      and remember the virtual host for logging puposes
+RewriteRule   ^/(.*)$   %1/$1  [E=VHOST:${lowercase:%{HTTP_HOST}}]
+    :
+
+
+
+ + + +
top
+
+

Access Restriction

+ + + +

Blocking of Robots

+ + + +
+
Description:
+ +
+

How can we block a really annoying robot from + retrieving pages of a specific webarea? A + /robots.txt file containing entries of the + "Robot Exclusion Protocol" is typically not enough to get + rid of such a robot.

+
+ +
Solution:
+ +
+

We use a ruleset which forbids the URLs of the webarea + /~quux/foo/arc/ (perhaps a very deep + directory indexed area where the robot traversal would + create big server load). We have to make sure that we + forbid access only to the particular robot, i.e. just + forbidding the host where the robot runs is not enough. + This would block users from this host, too. We accomplish + this by also matching the User-Agent HTTP header + information.

+ +
+RewriteCond %{HTTP_USER_AGENT}   ^NameOfBadRobot.*
+RewriteCond %{REMOTE_ADDR}       ^123\.45\.67\.[8-9]$
+RewriteRule ^/~quux/foo/arc/.+   -   [F]
+
+
+
+ + + +

Blocked Inline-Images

+ + + +
+
Description:
+ +
+

Assume we have under http://www.quux-corp.de/~quux/ + some pages with inlined GIF graphics. These graphics are + nice, so others directly incorporate them via hyperlinks to + their pages. We don't like this practice because it adds + useless traffic to our server.

+
+ +
Solution:
+ +
+

While we cannot 100% protect the images from inclusion, + we can at least restrict the cases where the browser + sends a HTTP Referer header.

+ +
+RewriteCond %{HTTP_REFERER} !^$
+RewriteCond %{HTTP_REFERER} !^http://www.quux-corp.de/~quux/.*$ [NC]
+RewriteRule .*\.gif$        -                                    [F]
+
+ +
+RewriteCond %{HTTP_REFERER}         !^$
+RewriteCond %{HTTP_REFERER}         !.*/foo-with-gif\.html$
+RewriteRule ^inlined-in-foo\.gif$   -                        [F]
+
+
+
+ + + +

Host Deny

+ + + +
+
Description:
+ +
+

How can we forbid a list of externally configured hosts + from using our server?

+
+ +
Solution:
+ +
+

For Apache >= 1.3b6:

+ +
+RewriteEngine on
+RewriteMap    hosts-deny  txt:/path/to/hosts.deny
+RewriteCond   ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR]
+RewriteCond   ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND} !=NOT-FOUND
+RewriteRule   ^/.*  -  [F]
+
+ +

For Apache <= 1.3b6:

+ +
+RewriteEngine on
+RewriteMap    hosts-deny  txt:/path/to/hosts.deny
+RewriteRule   ^/(.*)$ ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND}/$1
+RewriteRule   !^NOT-FOUND/.* - [F]
+RewriteRule   ^NOT-FOUND/(.*)$ ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND}/$1
+RewriteRule   !^NOT-FOUND/.* - [F]
+RewriteRule   ^NOT-FOUND/(.*)$ /$1
+
+ +
+##
+##  hosts.deny
+##
+##  ATTENTION! This is a map, not a list, even when we treat it as such.
+##             mod_rewrite parses it for key/value pairs, so at least a
+##             dummy value "-" must be present for each entry.
+##
+
+193.102.180.41 -
+bsdti1.sdm.de  -
+192.76.162.40  -
+
+
+
+ + + +

Proxy Deny

+ + + +
+
Description:
+ +
+

How can we forbid a certain host or even a user of a + special host from using the Apache proxy?

+
+ +
Solution:
+ +
+

We first have to make sure mod_rewrite + is below(!) mod_proxy in the Configuration + file when compiling the Apache webserver. This way it gets + called before mod_proxy. Then we + configure the following for a host-dependent deny...

+ +
+RewriteCond %{REMOTE_HOST} ^badhost\.mydomain\.com$
+RewriteRule !^http://[^/.]\.mydomain.com.*  - [F]
+
+ +

...and this one for a user@host-dependent deny:

+ +
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST}  ^badguy@badhost\.mydomain\.com$
+RewriteRule !^http://[^/.]\.mydomain.com.*  - [F]
+
+
+
+ + + +

Special Authentication Variant

+ + + +
+
Description:
+ +
+

Sometimes a very special authentication is needed, for + instance a authentication which checks for a set of + explicitly configured users. Only these should receive + access and without explicit prompting (which would occur + when using the Basic Auth via mod_auth_basic).

+
+ +
Solution:
+ +
+

We use a list of rewrite conditions to exclude all except + our friends:

+ +
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend1@client1.quux-corp\.com$
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend2@client2.quux-corp\.com$
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend3@client3.quux-corp\.com$
+RewriteRule ^/~quux/only-for-friends/      -                                 [F]
+
+
+
+ + + +

Referer-based Deflector

+ + + +
+
Description:
+ +
+

How can we program a flexible URL Deflector which acts + on the "Referer" HTTP header and can be configured with as + many referring pages as we like?

+
+ +
Solution:
+ +
+

Use the following really tricky ruleset...

+ +
+RewriteMap  deflector txt:/path/to/deflector.map
+
+RewriteCond %{HTTP_REFERER} !=""
+RewriteCond ${deflector:%{HTTP_REFERER}} ^-$
+RewriteRule ^.* %{HTTP_REFERER} [R,L]
+
+RewriteCond %{HTTP_REFERER} !=""
+RewriteCond ${deflector:%{HTTP_REFERER}|NOT-FOUND} !=NOT-FOUND
+RewriteRule ^.* ${deflector:%{HTTP_REFERER}} [R,L]
+
+ +

... in conjunction with a corresponding rewrite + map:

+ +
+##
+##  deflector.map
+##
+
+http://www.badguys.com/bad/index.html    -
+http://www.badguys.com/bad/index2.html   -
+http://www.badguys.com/bad/index3.html   http://somewhere.com/
+
+ +

This automatically redirects the request back to the + referring page (when "-" is used as the value + in the map) or to a specific URL (when an URL is specified + in the map as the second argument).

+
+
+ + + +
top
+
+

Other

+ + + +

External Rewriting Engine

+ + + +
+
Description:
+ +
+

A FAQ: How can we solve the FOO/BAR/QUUX/etc. + problem? There seems no solution by the use of + mod_rewrite...

+
+ +
Solution:
+ +
+

Use an external RewriteMap, i.e. a program which acts + like a RewriteMap. It is run once on startup of Apache + receives the requested URLs on STDIN and has + to put the resulting (usually rewritten) URL on + STDOUT (same order!).

+ +
+RewriteEngine on
+RewriteMap    quux-map       prg:/path/to/map.quux.pl
+RewriteRule   ^/~quux/(.*)$  /~quux/${quux-map:$1}
+
+ +
+#!/path/to/perl
+
+#   disable buffered I/O which would lead
+#   to deadloops for the Apache server
+$| = 1;
+
+#   read URLs one per line from stdin and
+#   generate substitution URL on stdout
+while (<>) {
+    s|^foo/|bar/|;
+    print $_;
+}
+
+ +

This is a demonstration-only example and just rewrites + all URLs /~quux/foo/... to + /~quux/bar/.... Actually you can program + whatever you like. But notice that while such maps can be + used also by an average user, only the + system administrator can define it.

+
+
+ + + +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/misc/rewriteguide.html.ko.euc-kr b/docs/manual/misc/rewriteguide.html.ko.euc-kr new file mode 100644 index 00000000..f5e544c9 --- /dev/null +++ b/docs/manual/misc/rewriteguide.html.ko.euc-kr @@ -0,0 +1,2006 @@ + + + +URL ÀçÀÛ¼º Áöħ¼­ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Miscellaneous Documentation

URL ÀçÀÛ¼º Áöħ¼­

+
+

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

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

¿øÀúÀÚ
+ Ralf S. Engelschall <rse@apache.org>
+ 1997³â 12¿ù

+
+ +

ÀÌ ¹®¼­´Â mod_rewrite ÂüÁ¶ ¹®¼­¸¦ º¸ÃæÇÑ´Ù. + ÀÌ ¹®¼­´Â À¥°ü¸®ÀÚ°¡ ½ÇÁ¦ ÀÛ¾÷¿¡¼­ ºÎµúÄ¡°ÔµÇ´Â ÀüÇüÀûÀÎ + URL°ü·Ã ¹®Á¦¸¦ ÇØ°áÇϱâÀ§Çؼ­ ¾î¶»°Ô ¾ÆÆÄÄ¡ + mod_rewrite¸¦ »ç¿ëÇÏ´ÂÁö ¼³¸íÇÑ´Ù. URL + ÀçÀÛ¼º ±ÔÄ¢À» ¼³Á¤ÇÏ¿© ¹®Á¦¸¦ ÇØ°áÇÏ´Â ¹æ¹ýÀ» ÀÚ¼¼È÷ ¼³¸íÇÑ´Ù.

+ +
+ +
top
+
+

mod_rewrite ¼Ò°³

+ + + +

¾ÆÆÄÄ¡ mod_rewrite ¸ðµâÀº ±²ÀåÇÏ´Ù. + Áï, URLÀ» Á¶ÀÛÇÒ ¼ö ÀÖ´Â °­·ÂÇÏ°í ½Ç·Î Á¤±³ÇÑ ¸ðµâÀÌ´Ù. + »ó»óÇØ¿Ô´ø °ÅÀÇ ¸ðµç Á¾·ùÀÇ URL Á¶ÀÛÀÌ °¡´ÉÇÏ´Ù. ±×·¯³ª + ±× ´ë°¡·Î »ç¿ëÇϱ⠺¹ÀâÇÏ´Ù. mod_rewriteÀÇ + ÃÖ´ë ´ÜÁ¡Àº Ãʺ¸ÀÚ°¡ ÀÌÇØÇÏ°í »ç¿ëÇϱ⠽±Áö ¾Ê´Ù´Â Á¡ÀÌ´Ù. + ½ÉÁö¾î ¾ÆÆÄÄ¡ Àü¹®°¡µµ Á¾Á¾ mod_rewriteÀÇ + »õ·Î¿î ¿ëµµ¸¦ ¹ß°ßÇÑ´Ù.

+ +

´Ù¸¥ ¸»·Î: mod_rewrite¿¡ ´ëÇØ ´ç½ÅÀº + óÀ½¿¡ °ÌÀ» ¸Ô°í Àý´ë·Î ´Ù½Ã »ç¿ëÇÏÁö ¾Ê°Å³ª, °­·ÂÇÔ¿¡ ¸Å·áµÇ¾î + ¾ÕÀ¸·Î »î µ¿¾È »ç¶û¿¡ ºüÁú °ÍÀÌ´Ù. ÀÌ ±ÛÀº ù¹ø° °æ¿ì¸¦ + ¸·±âÀ§ÇØ ÀÌ¹Ì ¾Ë·ÁÁø ¸î°¡Áö ¼º°ø»ç·Ê¸¦ ¼Ò°³ÇÏ·Á°í ÇÑ´Ù.

+ +
top
+
+

½Ç¿ëÀûÀÎ ÇØ°áÃ¥

+ + + +

ÀÌÁ¦ ³»°¡ Á÷Á¢ ¸¸µé¾ú°Å³ª ´Ù¸¥ »ç¶÷µéÀÌ ¸¸µç ¸¹Àº ½Ç¿ëÀûÀÎ + ÇØ°áÃ¥ÀÌ ³ª¿Â´Ù. ¿¹Á¦¿¡¼­ URL ÀçÀÛ¼ºÀÇ È渶¼úÀ» ¸¶À½²¯ ¹è¿ì±æ + ¹Ù¶õ´Ù.

+ +
ÁÖÀÇ: ¼­¹ö ¼³Á¤¿¡ µû¶ó »óȲ¿¡ ¸Â°Ô + ¿¹Á¦¸¦ Á¶±Ý ¼öÁ¤ÇØ¾ß ÇÒ °æ¿ì°¡ ÀÖ´Ù. ¿¹¸¦ µé¾î, Ãß°¡·Î + mod_alias, mod_userdir + µîÀ» »ç¿ëÇÑ´Ù¸é [PT] Ç÷¡±×¸¦ Ãß°¡ÇÑ´Ù. ȤÀº + ÁÖ¼­¹ö¼³Á¤/°¡»óÈ£½ºÆ® »ç¿ëÀå¼Ò°¡ ¾Æ´Ñ .htaccess + »ç¿ëÀå¼Ò¿¡ ¾Ë¸Â°Ô ±ÔÄ¢À» ¼öÁ¤ÇÒ ¼öµµ ÀÖ´Ù. »ç¿ëÇϱâ Àü¿¡ + Ç×»ó ±ÔÄ¢ÀÌ ¾î¶² ±â´ÉÀ» ÇÏ´ÂÁö ÀÌÇØÇϵµ·Ï Çضó. ±×·¯¸é ¹®Á¦¸¦ + ÇÇÇÒ ¼ö ÀÖ´Ù.
+ +
top
+
+

URL ±¸Á¶

+ + + +

±âÁØÀÌ µÇ´Â URL

+ + + +
+
»óȲ¼³¸í:
+ +
+

ÇÑ ¸®¼Ò½º¿¡ ´ëÇØ ¿©·¯ URLÀ» °¡Áö´Â À¥¼­¹ö°¡ ÀÖ´Ù. + º¸Åë (½ÇÁ¦ »ç¿ëÇÏ°í ¾Ë·ÁÁ®¾ß ÇÒ) ±âÁØÀÌ µÇ´Â URL°ú, + ´ÜÃà ȤÀº ³»ºÎ ¿ëµµÀÇ URLÀÌ ÀÖ´Ù. »ç¿ëÀÚ°¡ ¿äû¿¡ + ¾î¶² URLÀ» »ç¿ëÇÏ´øÁö ±âÁØÀÌ µÇ´Â URL¸¸À» º¸¿©Áà¾ß + ÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

±âÁØÀÌ µÇÁö¾Ê´Â ¸ðµç URLÀ» ºê¶ó¿ìÀú°¡ ¾Ëµµ·Ï °íÄ¡±âÀ§ÇØ + ¿ÜºÎ HTTP ¸®´ÙÀÌ·º¼ÇÇÑ´Ù. ¿¹¸¦ µé¾î ¾Æ·¡ ±ÔÄ¢Àº + /~user¸¦ ±âÁØÀÌ µÇ´Â /u/user·Î + ´ëüÇÏ°í, /u/user ¸¶Áö¸·¿¡ ½½·¡½¬°¡ ¾ø´Ù¸é + Ãß°¡ÇÑ´Ù.

+ +
+RewriteRule   ^/~([^/]+)/?(.*)    /u/$1/$2  [R]
+RewriteRule   ^/([uge])/([^/]+)$  /$1/$2/   [R]
+
+
+
+ + + +

±âÁØÀÌ µÇ´Â È£½ºÆ®¸í

+ + + +
+
»óȲ¼³¸í:
+ +
...
+ +
ÇØ°áÃ¥:
+ +
+
+RewriteCond %{HTTP_HOST}   !^fully\.qualified\.domain\.name [NC]
+RewriteCond %{HTTP_HOST}   !^$
+RewriteCond %{SERVER_PORT} !^80$
+RewriteRule ^/(.*)         http://fully.qualified.domain.name:%{SERVER_PORT}/$1 [L,R]
+RewriteCond %{HTTP_HOST}   !^fully\.qualified\.domain\.name [NC]
+RewriteCond %{HTTP_HOST}   !^$
+RewriteRule ^/(.*)         http://fully.qualified.domain.name/$1 [L,R]
+
+
+
+ + + +

DocumentRoot¸¦ ¿Å±ä °æ¿ì

+ + + +
+
»óȲ¼³¸í:
+ +
+

À¥¼­¹öÀÇ DocumentRoot´Â º¸Åë URL + "/"°ú Á÷Á¢ °ü·ÃÀÖ´Ù. ±×·¯³ª ÀÌ°÷¿¡ ¸ðµç + ÀÚ·á°¡ ÀÖÁö ¾Ê°í, ÀÚ·á°¡ ´Ù¸¥ ¿©·¯ °÷¿¡ Èð¾îÁ®ÀÖ´Â + °æ¿ì°¡ ÀÖ´Ù. ¿¹¸¦ µé¾î ÀÎÆ®¶ó³Ý »çÀÌÆ®¿¡ (¿ÜºÎ¸¦ À§ÇÑ + ȨÆäÀÌÁö) /e/www/¿Í (ÀÎÆ®¶ó³ÝÀ» À§ÇÑ + ȨÆäÀÌÁö) /e/sww/°¡ ÀÖ´Ù°í ÇÏÀÚ. ÀÌÁ¦ + DocumentRoot°¡ + /e/www/À̱⶧¹®¿¡, ¿äû¿¡¼­ ÆäÀÌÁö¿¡ + Æ÷ÇÔµÈ ±×¸² µîÀ» ÀÌ°÷¿¡¼­ °¡Á®¿Í¾ß ÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

¿ì¸®´Â URL /¸¦ /e/www/·Î + ¸®´ÙÀÌ·º¼Ç¸¸ ÇÏ¸é µÈ´Ù. »ç¼ÒÇØ º¸ÀÌÁö¸¸ ½ÇÁ¦·Î + mod_rewrite¸¦ »ç¿ëÇؼ­¸¸ °¡´ÉÇÏ´Ù. + (mod_alias µîÀÌ Á¦°øÇÏ´Â) URL + Alias °°Àº ÀüÇüÀûÀÎ ¹æ¹ýÀº ¾ÕºÎºÐ¸¸ + ã´Â´Ù. DocumentRoot°¡ + ¸ðµç URLÀÇ ¾ÕºÎºÐÀ̱⶧¹®¿¡ ÀÌ ¹æ¹ýÀ» »ç¿ëÇÏ¿© ¸®´ÙÀÌ·º¼ÇÀ» + ÇÒ ¼ö ¾ø´Ù. mod_rewrite¸¦ »ç¿ëÇϸé + ÁøÂ¥ °£´ÜÇÏ´Ù:

+ +
+RewriteEngine on
+RewriteRule   ^/$  /e/www/  [R]
+
+
+
+ + + +

¸¶Áö¸· ½½·¡½¬ ¹®Á¦

+ + + +
+
»óȲ¼³¸í:
+ +
+

µð·ºÅ丮¸¦ ÁöĪÇÏ´Â URLÀÇ ¸¶Áö¸· ½½·¡½¬ ¹®Á¦°¡ + ¾ø´Ù¸é ¸ðµç À¥°ü¸®Àڴ ȯȣÇÒ °ÍÀÌ´Ù. ½½·¡½¬°¡ ¾ø´Ù¸é, + Áï /~quux/foo/ ´ë½Å /~quux/foo¸¦ + »ç¿ëÇÏ¸é ¼­¹ö°¡ foo¶ó´Â ÆÄÀÏÀ» + ã±â¶§¹®¿¡ ¿À·ù°¡ ¹ß»ýÇÑ´Ù. ÆÄÀÏÀÌ µð·ºÅ丮À̱⶧¹®¿¡ + ¹Þ¾ÆµéÀÌÁö ¾Ê´Â´Ù. ´ëºÎºÐÀÇ °æ¿ì º¸Åë ¼­¹ö°¡ ÀÚµ¿À¸·Î + URLÀ» °íÄ¡Áö¸¸, °¡²û Á÷Á¢ ÇØÁà¾ß ÇÒ °æ¿ì°¡ ÀÖ´Ù. ¿¹¸¦ + µé¾î, CGI ½ºÅ©¸³Æ® µîÀ¸·Î º¹ÀâÇÑ URL ÀçÀÛ¼ºÀ» ÇÑ ÈÄ¿¡ + ±×·¯ÇÏ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

ÀÌ ¹Ì¹¦ÇÑ ¹®Á¦ÀÇ ÇØ°á¹æ¹ýÀº ¼­¹ö°¡ ÀÚµ¿À¸·Î ¸¶Áö¸· + ½½·¡½¬¸¦ Ãß°¡ÇÏ´Â °ÍÀÌ´Ù. ºê¶ó¿ìÀú°¡ ³ª¸ÓÁö ±×¸² µîÀ» + ¿Ã¹Ù·Î ¿äûÇÒ ¼ö ÀÖµµ·Ï, ¿ÜºÎ ¸®´ÙÀÌ·º¼ÇÀ» ÇØ¾ß ÇÑ´Ù. + ³»ºÎ ¸®´ÙÀÌ·º¼ÇÀ» ÇÑ´Ù¸é µð·ºÅ丮 ÆäÀÌÁö¿¡¸¸ µ¿ÀÛÇÏ¿© + ÀÌ ÆäÀÌÁö°¡ »ó´ë URL·Î Æ÷ÇÔÇÏ´Â ±×¸²À» ºê¶ó¿ìÀú°¡ + ¿äûÇÒ¶§ ãÀ» ¼ö ¾ø´Ù. ¿¹¸¦ µé¾î, ¿ÜºÎ ¸®´ÙÀÌ·º¼ÇÀ» + »ç¿ëÇÏÁö ¾ÊÀ»¶§ /~quux/foo/index.html¿¡¼­ + image.gif¸¦ ¿äûÇϸé + /~quux/image.gif¸¦ ¿äûÇÏ°Ô µÈ´Ù!

+ +

±×·¡¼­ À̸¦ ÇØ°áÇϱâÀ§ÇØ ´ÙÀ½°ú °°ÀÌ ¼³Á¤ÇÑ´Ù:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo$  foo/  [R]
+
+ +

Ȩµð·ºÅ丮ÀÇ ÃÖ»óÀ§ .htaccess ÆÄÀÏ¿¡ + ´ÙÀ½°ú °°ÀÌ ¼³Á¤ÇÒ ¼öµµ ÀÖ´Ù. ±×·¯³ª ó¸®Çϴµ¥ ºÎ´ãÀÌ + µÈ´Ù.

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteCond    %{REQUEST_FILENAME}  -d
+RewriteRule    ^(.+[^/])$           $1/  [R]
+
+
+
+ + + +

ÀÏ°üµÈ URL ±¸Á¶·Î ¸¸µç À¥Å¬·¯½ºÅÍ

+ + + +
+
»óȲ¼³¸í:
+ +
+

ÀÎÆ®¶ó³Ý À¥¼­¹ö±ºÀÇ ¸ðµç À¥¼­¹ö¿¡ µ¿ÀÏÇÏ°í ÀÏ°üµÈ + URL ±¸Á¶¸¦ ¸¸µé°í ½Í´Ù. Áï, ¸ðµç (Á¤ÀÇ»ó ¼­¹ö¿¡ ¼ÓÇÏ¿© + ¼­¹ö¿¡ ÀÇÁ¸ÀûÀÎ!) URLÀ» ¼­¹ö µ¶¸³ÀûÀ¸·Î ¸¸µç´Ù! + À¥ À̸§°ø°£¿¡ ¼­¹öµ¶¸³ÀûÀÎ µ¿ÀÏÇÑ ±¸Á¶¸¦ ºÎ¿©ÇØ¾ß ÇÑ´Ù: + URLÀº ½ÇÁ¦ ¼­¹ö¸¦ ÁöĪÇÏ¸é ¾ÈµÈ´Ù. ¼­¹ö±ºÀÌ ÀÚµ¿À¸·Î + ½ÇÁ¦ ¼­¹ö·Î À¯µµÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

¸ÕÀú »ç¿ëÀÚ, ±×·ì, µ¶¸³Ã¼ÀÇ À§Ä¡ Á¤º¸¸¦ ÀúÀåÇÑ + (ºÐ»êµÈ) ¿ÜºÎ¸Ê¿¡ ½ÇÁ¦ ¼­¹ö Á¤º¸¸¦ ¾ò¾î¿Â´Ù. ¿ÜºÎ¸ÊÀº + ´ÙÀ½°ú °°Àº Çü½ÄÀÌ´Ù

+ +
+user1  server_of_user1
+user2  server_of_user2
+:      :
+
+ +

¿ì¸®´Â ÀÌ Á¤º¸¸¦ °¢°¢ map.xxx-to-host + ÆÄÀÏ¿¡ ÀúÀåÇß´Ù. ´ÙÀ½À¸·Î ¸ðµç ¼­¹ö¿¡¼­ URLÀÌ ¼­¹ö¿¡ + ¾ø´Ù¸é ´ÙÀ½°ú °°Àº URLÀ»,

+ +
+/u/user/anypath
+/g/group/anypath
+/e/entity/anypath
+
+ +

´ÙÀ½°ú °°ÀÌ ¸®´ÙÀÌ·º¼ÇÇÑ´Ù

+ +
+http://physical-host/u/user/anypath
+http://physical-host/g/group/anypath
+http://physical-host/e/entity/anypath
+
+ +

¾Æ·¡ ±ÔÄ¢Àº ¸ÊÆÄÀÏÀ» »ç¿ëÇÏ¿© ÀÌ ÀÛ¾÷À» ÇÑ´Ù (server0Àº + ¸Ê¿¡ Ç׸ñÀÌ ¾ø´Â °æ¿ì »ç¿ëÇÒ ±âº»¼­¹ö¶ó°í °¡Á¤ÇÑ´Ù):

+ +
+RewriteEngine on
+
+RewriteMap      user-to-host   txt:/path/to/map.user-to-host
+RewriteMap     group-to-host   txt:/path/to/map.group-to-host
+RewriteMap    entity-to-host   txt:/path/to/map.entity-to-host
+
+RewriteRule   ^/u/([^/]+)/?(.*)   http://${user-to-host:$1|server0}/u/$1/$2
+RewriteRule   ^/g/([^/]+)/?(.*)  http://${group-to-host:$1|server0}/g/$1/$2
+RewriteRule   ^/e/([^/]+)/?(.*) http://${entity-to-host:$1|server0}/e/$1/$2
+
+RewriteRule   ^/([uge])/([^/]+)/?$          /$1/$2/.www/
+RewriteRule   ^/([uge])/([^/]+)/([^.]+.+)   /$1/$2/.www/$3\
+
+
+
+ + + +

Ȩµð·ºÅ丮¸¦ ´Ù¸¥ À¥¼­¹ö·Î ÀÌÀü

+ + + +
+
»óȲ¼³¸í:
+ +
+

¸¹Àº À¥°ü¸®ÀÚ´Â À¥¼­¹öÀÇ ¸ðµç Ȩµð·ºÅ丮¸¦ ´Ù¸¥ + À¥¼­¹ö·Î ÀÌÀüÇÑ °æ¿ì ÇØ°áÃ¥À» ¹°¾îº»´Ù. ÀÌ ¹æ¹ýÀº + ÀÌÀü ¼­¹ö¸¦ ´ëüÇÒ »õ·Î¿î ¼­¹ö¸¦ ±¸¼ºÇϴµ¥ ½Ã°£ÀÌ + °É¸®´Â °æ¿ì¿¡ ÇÊ¿äÇÏ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

mod_rewrite¸¦ »ç¿ëÇÏ¸é °£´ÜÇÏ´Ù. + ÀÌÀü À¥¼­¹ö´Â ¸ðµç /~user/anypath URLÀ» + http://newserver/~user/anypath·Î + ¸®´ÙÀÌ·º¼ÇÇÏ¸é µÈ´Ù.

+ +
+RewriteEngine on
+RewriteRule   ^/~(.+)  http://newserver/~$1  [R,L]
+
+
+
+ + + +

Ȩµð·ºÅ丮 ±¸Á¶ ¸¸µé±â

+ + + +
+
»óȲ¼³¸í:
+ +
+

»ç¿ëÀÚ°¡ ¼öõ¸íÀÎ »çÀÌÆ®´Â º¸Åë Ȩµð·ºÅ丮 ±¸Á¶¸¦ + ¸¸µç´Ù. Áï, ¿¹¸¦ µé¾î À̸§ÀÌ »ç¿ëÀÚ¸íÀÇ Ã¹¹ø° ¹®ÀÚÀÎ + ÇÏÀ§µð·ºÅ丮¿¡ Ȩµð·ºÅ丮¸¦ µÐ´Ù. ±×·¡¼­, + /~foo/anypath´Â + /home/f/foo/.www/anypathÀÌ°í, + /~bar/anypath´Â + /home/b/bar/.www/anypathÀÌ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

¹°°áÇ¥½Ã°¡ ÀÖ´Â URLÀ» À§¿Í °°Àº ±¸Á¶·Î º¯È¯ÇϱâÀ§ÇØ + ´ÙÀ½ ±ÔÄ¢À» »ç¿ëÇÑ´Ù.

+ +
+RewriteEngine on
+RewriteRule   ^/~(([a-z])[a-z0-9]+)(.*)  /home/$2/$1/.www$3
+
+
+
+ + + +

ÆÄÀϽýºÅÛ À籸¼º

+ + + +
+
»óȲ¼³¸í:
+ +
+

ÀÌ ¿¹´Â ½Ç·Î ÇϵåÄÚ¾îÀûÀÌ´Ù: µð·ºÅ丮º° + RewriteRules¸¦ ¸Å¿ì ¸¹ÀÌ »ç¿ëÇÏ¿© ÀÚ·á + ÀÚü´Â ±×´ë·Î µÐü·Î À¥¿¡ ÀڷḦ ÀÚ¿¬½º·´°Ô ºê¶ó¿ì¡Çϵµ·Ï + ÇÑ´Ù. ¹è°æ: ³ª´Â 1992³â ºÎÅÍ ÀÚÀ¯·Ó°Ô »ç¿ëÇÒ ¼ö ÀÖ´Â + À¯´Ð½º ¼ÒÇÁÆ®¿þ¾îµéÀ» net.sw¿¡ + ¸ð¾ÆµÎ°í ÀÖ¾ú´Ù. ÀÌ´Â ³»°¡ ÄÄÇ»ÅÍ°úÇÐÀ» °øºÎÇϸ鼭 + ¿©·¯Çص¿¾È ¿©°¡½Ã°£¿¡ ½Ã½ºÅÛ °ü¸®ÀÚ¿Í ³×Æ®¿÷ °ü¸®ÀÚ¸¦ + ÇؿԱ⶧¹®¿¡ ³» Ãë¹ÌÀÌÀÚ ÀÏÀÌ´Ù. ¸ÅÁÖ¸¶´Ù »õ·Î ¼ÒÇÁÆ®¿þ¾î°¡ + Ãß°¡µÉ ¶§¸¶´Ù µð·ºÅ丮¸¦ ±í°Ô ¸¸µé¾î¿Ô´Ù:

+ +
+drwxrwxr-x   2 netsw  users    512 Aug  3 18:39 Audio/
+drwxrwxr-x   2 netsw  users    512 Jul  9 14:37 Benchmark/
+drwxrwxr-x  12 netsw  users    512 Jul  9 00:34 Crypto/
+drwxrwxr-x   5 netsw  users    512 Jul  9 00:41 Database/
+drwxrwxr-x   4 netsw  users    512 Jul 30 19:25 Dicts/
+drwxrwxr-x  10 netsw  users    512 Jul  9 01:54 Graphic/
+drwxrwxr-x   5 netsw  users    512 Jul  9 01:58 Hackers/
+drwxrwxr-x   8 netsw  users    512 Jul  9 03:19 InfoSys/
+drwxrwxr-x   3 netsw  users    512 Jul  9 03:21 Math/
+drwxrwxr-x   3 netsw  users    512 Jul  9 03:24 Misc/
+drwxrwxr-x   9 netsw  users    512 Aug  1 16:33 Network/
+drwxrwxr-x   2 netsw  users    512 Jul  9 05:53 Office/
+drwxrwxr-x   7 netsw  users    512 Jul  9 09:24 SoftEng/
+drwxrwxr-x   7 netsw  users    512 Jul  9 12:17 System/
+drwxrwxr-x  12 netsw  users    512 Aug  3 20:15 Typesetting/
+drwxrwxr-x  10 netsw  users    512 Jul  9 14:08 X11/
+
+ +

1996³â 7¿ù ÀÌ ÀúÀå¼Ò¸¦ ¸ÚÀÖ´Â À¥ ÀÎÅÍÆäÀ̽º¸¦ ÅëÇØ + ¼¼»ó¿¡ °ø°³Çϱâ·Î °áÁ¤ÇÞ´Ù. "¸ÚÀÖ´Ù"´Â ¸»Àº, ÃÖ»óÀ§ + µð·ºÅ丮¿¡ CGI ½ºÅ©¸³Æ®¸¦ µÎÁö ¾Ê°íµµ, ÀúÀå¼Ò °èÃþ±¸Á¶¸¦ + Á÷Á¢ ºê¶ó¿ìÁúÇÏ±æ ¹Ù¶õ´Ù´Â ¶æÀÌ´Ù. ¿Ö? ÀúÀå¼Ò¸¦ ³ªÁß¿¡ + FTP·Îµµ Á¢±ÙÇÒ ¼ö ÀÖµµ·Ï ¸¸µé ¿¹Á¤ÀÌ¿´±â¶§¹®¿¡ À¥À̳ª + CGI¿Í °ü·ÃµÈ ³»¿ëÀ» °°ÀÌ µÎ±â ½È¾ú´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

ÇØ°áÃ¥Àº µÎ ºÎºÐÀ¸·Î ³ª´¶´Ù: ¸ÕÀú µð·ºÅ丮 ¼öÁØ¿¡¼­ + ÇÊ¿äÇÑ ¸ðµç ÆäÀÌÁö¸¦ µ¿ÀûÀ¸·Î ¸¸µå´Â CGI ½ºÅ©¸³Æ®°¡ + ÇÊ¿äÇÏ´Ù. ³ª´Â ÀÌ ½ºÅ©¸³Æ®µéÀ» ´ÙÀ½°ú °°ÀÌ + /e/netsw/.www/¿¡ µÎ¾ú´Ù:

+ +
+-rw-r--r--   1 netsw  users    1318 Aug  1 18:10 .wwwacl
+drwxr-xr-x  18 netsw  users     512 Aug  5 15:51 DATA/
+-rw-rw-rw-   1 netsw  users  372982 Aug  5 16:35 LOGFILE
+-rw-r--r--   1 netsw  users     659 Aug  4 09:27 TODO
+-rw-r--r--   1 netsw  users    5697 Aug  1 18:01 netsw-about.html
+-rwxr-xr-x   1 netsw  users     579 Aug  2 10:33 netsw-access.pl
+-rwxr-xr-x   1 netsw  users    1532 Aug  1 17:35 netsw-changes.cgi
+-rwxr-xr-x   1 netsw  users    2866 Aug  5 14:49 netsw-home.cgi
+drwxr-xr-x   2 netsw  users     512 Jul  8 23:47 netsw-img/
+-rwxr-xr-x   1 netsw  users   24050 Aug  5 15:49 netsw-lsdir.cgi
+-rwxr-xr-x   1 netsw  users    1589 Aug  3 18:43 netsw-search.cgi
+-rwxr-xr-x   1 netsw  users    1885 Aug  1 17:41 netsw-tree.cgi
+-rw-r--r--   1 netsw  users     234 Jul 30 16:35 netsw-unlimit.lst
+
+ +

DATA/ ÇÏÀ§µð·ºÅ丮¿¡ À§¿¡¼­ ¸»ÇÑ ÀúÀå¼Ò°¡ + ÀÖ´Ù. ½ÇÁ¦ net.swÀÇ ³»¿ëÀº º¸Åë + rdist¸¦ »ç¿ëÇÏ¿© ÀÚµ¿À¸·Î °¡Á®¿Â´Ù. µÎ¹ø° + ºÎºÐÀÌ ³²¾Ò´Ù: ¾î¶»°Ô ÀÌ µÎ ±¸Á¶¸¦ ÇϳªÀÇ ÀÚ¿¬½º·¯¿î + URL ±¸Á¶·Î ¿¬°áÇϴ°¡? »ç¿ëÀÚ¿¡°Ô DATA/ + µð·ºÅ丮¸¦ °¨Ãß°í, URL¸¶´Ù ÀûÀýÇÑ CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÏ°í + ½Í´Ù. ÇØ°áÃ¥Àº ´ÙÀ½°ú °°´Ù: ¸ÕÀú ¼­¹öÀÇ DocumentRoot¿¡¼­ °ø°³µÈ + URL /net.sw/¸¦ ³»ºÎ °æ·Î /e/netsw·Î + ÀçÀÛ¼ºÇϱâÀ§ÇØ µð·ºÅ丮º° ¼³Á¤ÆÄÀÏ¿¡ ´ÙÀ½°ú °°ÀÌ ¼³Á¤ÇÑ´Ù:

+ +
+RewriteRule  ^net.sw$       net.sw/        [R]
+RewriteRule  ^net.sw/(.*)$  e/netsw/$1
+
+ +

ù¹ø° ±ÔÄ¢Àº ¸¶Áö¸·¿¡ ½½·¡½¬°¡ ¾ø´Â ¿äûÀ» À§Çؼ­ + »ç¿ëÇß´Ù! µÎ¹ø° ±ÔÄ¢ÀÌ ½ÇÁ¦ ÀÛ¾÷À» ÇÑ´Ù. ±×¸®°í µð·ºÅ丮º° + ¼³Á¤ÆÄÀÏ /e/netsw/.www/.wwwacl¿¡ °áÁ¤ÀûÀÎ + ¼³Á¤ÀÌ ³ª¿Â´Ù:

+ +
+Options       ExecCGI FollowSymLinks Includes MultiViews
+
+RewriteEngine on
+
+#  ¾Õ ºÎºÐÀÌ /net.sw/ ·Î Á¢±ÙÇÑ´Ù
+RewriteBase   /net.sw/
+
+#  ¸ÕÀú ÃÖ»óÀ§ µð·ºÅ丮¸¦
+#  cgi ½ºÅ©¸³Æ®·Î ÀçÀÛ¼ºÇÑ´Ù
+RewriteRule   ^$                       netsw-home.cgi     [L]
+RewriteRule   ^index\.html$            netsw-home.cgi     [L]
+
+#  ºê¶ó¿ìÀú°¡ µð·ºÅ丮º° ÆäÀÌÁö¸¦ ¿äûÇÑ °æ¿ì
+#  ÇÏÀ§µð·ºÅ丮¸¦ ÃßÃâÇÑ´Ù
+RewriteRule   ^.+/(netsw-[^/]+/.+)$    $1                 [L]
+
+#  ÀÌÁ¦ ÀçÀÛ¼ºÀ» ¸¶Ä£´Ù
+RewriteRule   ^netsw-home\.cgi.*       -                  [L]
+RewriteRule   ^netsw-changes\.cgi.*    -                  [L]
+RewriteRule   ^netsw-search\.cgi.*     -                  [L]
+RewriteRule   ^netsw-tree\.cgi$        -                  [L]
+RewriteRule   ^netsw-about\.html$      -                  [L]
+RewriteRule   ^netsw-img/.*$           -                  [L]
+
+#  ´Ù¸¥ cgi ½ºÅ©¸³Æ®°¡ ó¸®ÇÒ
+#  ÇÏÀ§µð·ºÅ丮°¡ ³²¾Ò´Ù
+RewriteRule   !^netsw-lsdir\.cgi.*     -                  [C]
+RewriteRule   (.*)                     netsw-lsdir.cgi/$1
+
+ +

Çؼ®À» À§ÇÑ ÈùÆ®:

+ +
    +
  1. ³×¹ø° ºÎºÐ¿¡¼­ ´ëü Çʵå('-')°¡ + ¾ø°í L (last) Ç÷¡±×°¡ ÀÖÀ½À» ÁÖ¸ñÇ϶ó
    2. + +
  2. ¸¶Áö¸· ºÎºÐ¿¡¼­ ù¹ø° ±ÔÄ¢¿¡ ! + (not) ¹®ÀÚ¿Í C (chain) Ç÷¡±×¸¦ ÁÖ¸ñÇ϶ó
    3. + +
  3. ¸¶Áö¸· ±ÔÄ¢¿¡¼­ ±âŸ ÇØ´çÇÏÁö ¾Ê´Â ¸ðµç °æ¿ì¸¦ + Àâ¾Æ³»´Â ÆÐÅÏÀ» ÁÖ¸ñÇ϶ó
    4. +
+
+
+ + + +

NCSA imagemapÀ» ¾ÆÆÄÄ¡ mod_imagemapÀ¸·Î

+ + + +
+
»óȲ¼³¸í:
+ +
+

»ç¶÷µéÀº NCSA À¥¼­¹ö¿¡¼­ Çö´ëÀûÀÎ ¾ÆÆÄÄ¡ À¥¼­¹ö·Î + ÀÚ¿¬½º·´°Ô ¿Å°Ü°¡±æ ¹Ù¶õ´Ù. ±×·¡¼­ ¿À·¡µÈ NCSA + imagemap ÇÁ·Î±×·¥À» »ç¿ëÇÑ ÆäÀÌÁö¸¦ Çö´ëÀûÀÎ + ¾ÆÆÄÄ¡ mod_imagemap·Î ó¸®ÇÏ±æ ¹Ù¶õ´Ù. + ¹®Á¦´Â imagemap ÇÁ·Î±×·¥À» + /cgi-bin/imagemap/path/to/page.map°ú + °°ÀÌ ÂüÁ¶ÇÏ´Â ÇÏÀÌÆÛ¸µÅ©°¡ ¸¹´Ù´Â °ÍÀÌ´Ù. ¾ÆÆÄÄ¡´Â + /path/to/page.map°ú °°Àº ¿äûÀ» ¹Þ¾Æ¾ß + ÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

¸ðµç ¿äû¿¡¼­ ¾ÕºÎºÐÀ» µ¿ÀûÀ¸·Î Á¦°ÅÇÏ´Â Àü¿ª ±ÔÄ¢À» + »ç¿ëÇÑ´Ù:

+ +
+RewriteEngine  on
+RewriteRule    ^/cgi-bin/imagemap(.*)  $1  [PT]
+
+
+
+ + + +

¿©·¯ µð·ºÅ丮¿¡¼­ ÆäÀÌÁö °Ë»ö

+ + + +
+
»óȲ¼³¸í:
+ +
+

°¡²û À¥¼­¹ö°¡ ¿©·¯ µð·ºÅ丮¿¡¼­ ÆÄÀÏÀ» ã¾Æ¾ß ÇÒ + ¶§°¡ ÀÖ´Ù. ÀÌ °æ¿ì MultiViews³ª ´Ù¸¥ ¹æ¹ýÀº µµ¿òÀÌ + ¾ÈµÈ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

¿©·¯ µð·ºÅ丮¿¡¼­ ÆÄÀÏÀ» ã´Â ±ÔÄ¢À» Á÷Á¢ ÇÁ·Î±×·¥ÇÑ´Ù.

+ +
+RewriteEngine on
+
+#   ¸ÕÀú custom/¿¡¼­ ã±æ ½ÃµµÇÏ°í...
+#   ...ãÀ¸¸é ³¡!
+RewriteCond         /your/docroot/dir1/%{REQUEST_FILENAME}  -f
+RewriteRule  ^(.+)  /your/docroot/dir1/$1  [L]
+
+#   µÎ¹ø°·Î pub/¿¡¼­ ã±æ ½ÃµµÇÑ´Ù...
+#   ...ãÀ¸¸é ³¡!
+RewriteCond         /your/docroot/dir2/%{REQUEST_FILENAME}  -f
+RewriteRule  ^(.+)  /your/docroot/dir2/$1  [L]
+
+#   ¸øãÀ¸¸é ´Ù¸¥ Alias³ª ScriptAlias Áö½Ã¾î µîÀ¸·Î ÁøÇàÇÑ´Ù.
+RewriteRule   ^(.+)  -  [PT]
+
+
+
+ + + +

URL¿¡ µû¶ó ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù

+ + + +
+
»óȲ¼³¸í:
+ +
+

¿äûµé°£¿¡ »óÅÂÁ¤º¸¸¦ À¯ÁöÇϱâÀ§ÇØ URL¿¡ Á¤º¸¸¦ + ÀÎÄÚµùÇÏ´Â ¹æ¹ýµµ ÀÖ´Ù. ±×·¯³ª ´ÜÁö ÀÌ Á¤º¸¸¦ Á¦°ÅÇϱâÀ§ÇØ + ¸ðµç ÆäÀÌÁö¿¡ CGI wrapper¸¦ »ç¿ëÇÏ°í ½ÍÁö ¾Ê´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

ÀçÀÛ¼º ±ÔÄ¢À» »ç¿ëÇÏ¿© »óÅÂÁ¤º¸¸¦ ÃßÃâÇÏ°í, ÃßÃâÇÑ + Á¤º¸¸¦ ³ªÁß¿¡ XSSI³ª CGI¿¡¼­ »ç¿ëÇϱâÀ§ÇØ È¯°æº¯¼ö¿¡ + ÀúÀåÇÑ´Ù. ±×·¡¼­ URL /foo/S=java/bar/´Â + /foo/bar/·Î º¯È¯µÇ°í STATUS¶ó´Â + ȯ°æº¯¼ö °ªÀ» "java"·Î ¼³Á¤ÇÑ´Ù.

+ +
+RewriteEngine on
+RewriteRule   ^(.*)/S=([^/]+)/(.*)    $1/$3 [E=STATUS:$2]
+
+
+
+ + + +

°¡»ó »ç¿ëÀÚ È£½ºÆ®

+ + + +
+
»óȲ¼³¸í:
+ +
+

°¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÏÁö ¾Ê°í °°Àº ÄÄÇ»ÅÍ·Î DNS A + ·¹Äڵ带 ¼³Á¤ÇÏ¿© + www.username.host.domain.comÀ» + »ç¿ëÀÚÀÇ È¨ÆäÀÌÁö·Î Á¦°øÇÏ°í ½Í´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

HTTP/1.0 ¿äûÀÇ °æ¿ì ¹æ¹ýÀÌ ¾øÁö¸¸, Host: HTTP + Çì´õ¸¦ Æ÷ÇÔÇÑ HTTP/1.1 ¿äûÀº ´ÙÀ½ ±ÔÄ¢À» »ç¿ëÇÏ¿© + ³»ºÎÀûÀ¸·Î http://www.username.host.com/anypath¸¦ + /home/username/anypath·Î ÀçÀÛ¼ºÇÒ ¼ö + ÀÖ´Ù:

+ +
+RewriteEngine on
+RewriteCond   %{HTTP_HOST}                 ^www\.[^.]+\.host\.com$
+RewriteRule   ^(.+)                        %{HTTP_HOST}$1          [C]
+RewriteRule   ^www\.([^.]+)\.host\.com(.*) /home/$1$2
+
+
+
+ + + +

Ȩµð·ºÅ丮¸¦ ¿ÜºÎ ¼­¹ö·Î ¸®´ÙÀÌ·º¼Ç

+ + + +
+
»óȲ¼³¸í:
+ +
+

Áö¿ª µµ¸ÞÀÎ ourdomain.com ¹Û¿¡¼­ ¿äûÀÌ + µé¾î¿À¸é Ȩµð·ºÅ丮 URLÀ» ´Ù¸¥ À¥¼­¹ö + www.somewhere.comÀ¸·Î ¸®´Ù¸®·º¼ÇÇϱæ + ¹Ù¶õ´Ù. Á¾Á¾ °¡»óÈ£½ºÆ® »ç¿ëÀå¼Ò¿¡¼­ »ç¿ëÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

ÀçÀÛ¼º Á¶°ÇÀ» »ç¿ëÇÏ¸é µÈ´Ù:

+ +
+RewriteEngine on
+RewriteCond   %{REMOTE_HOST}  !^.+\.ourdomain\.com$
+RewriteRule   ^(/~.+)         http://www.somewhere.com/$1 [R,L]
+
+
+
+ + + +

½ÇÆÐÇÑ URLÀ» ´Ù¸¥ À¥¼­¹ö·Î ¸®´ÙÀÌ·º¼Ç

+ + + +
+
»óȲ¼³¸í:
+ +
+

URL ÀçÀÛ¼º¿¡ ´ëÇؼ­ À¥¼­¹ö A¿¡ ÇØ´ç ÆÄÀÏÀÌ ¾ø´Â + °æ¿ì À¥¼­¹ö B·Î ¿äûÀ» ¸®´ÙÀÌ·º¼ÇÇÏ´Â ¹æ¹ýÀ» ÀÚÁÖ + ¹°¾îº»´Ù. º¸Åë Perl·Î ÀÛ¼ºÇÑ ErrorDocument CGI ½ºÅ©¸³Æ®¸¦ + »ç¿ëÇÏÁö¸¸, mod_rewrite¸¦ »ç¿ëÇÏ´Â + ¹æ¹ýµµ ÀÖ´Ù. ±×·¯³ª ¼º´ÉÀº ErrorDocument CGI ½ºÅ©¸³Æ®º¸´Ù + ¶³¾îÁüÀ» ¸í½ÉÇ϶ó!

+
+ +
ÇØ°áÃ¥:
+ +
+

ù¹ø° ¹æ¹ýÀº ºü¸£Áö¸¸ À¯¿¬¼ºÀÌ ¶³¾îÁö°í ¿ÏÀüÇÏÁö + ¾Ê´Ù:

+ +
+RewriteEngine on
+RewriteCond   /your/docroot/%{REQUEST_FILENAME} !-f
+RewriteRule   ^(.+)                             http://webserverB.dom/$1
+
+ +

ÀÌ ¹æ¹ýÀÇ ´ÜÁ¡Àº DocumentRoot ¾È¿¡ ÀÖ´Â ÆäÀÌÁö¸¸ + °¡´ÉÇÏ´Ù´Â Á¡ÀÌ´Ù. (¿¹¸¦ µé¾î Ȩµð·ºÅ丮 µîÀ» À§ÇØ) + Á¶°ÇÀ» Ãß°¡ÇÒ ¼ö ÀÖÁö¸¸, ´õ ÁÁÀº ¹æ¹ýÀÌ ÀÖ´Ù:

+ +
+RewriteEngine on
+RewriteCond   %{REQUEST_URI} !-U
+RewriteRule   ^(.+)          http://webserverB.dom/$1
+
+ +

mod_rewriteÀÇ URL Àü¹æÂüÁ¶(look-ahead)¸¦ + »ç¿ëÇÑ´Ù. ±×·¡¼­ ¸ðµç URL¿¡ µ¿ÀÛÇÏ°í ¾ÈÀüÇÏ´Ù. ±×·¯³ª + ¸ðµç ¿äû¸¶´Ù ³»ºÎ ÇÏÀ§¿äûÀ» Çѹø ´õ Çϱ⶧¹®¿¡ À¥¼­¹ö + ¼º´É¿¡ ¾Ç¿µÇâÀ» ÁØ´Ù. ±×·¡¼­ °­·ÂÇÑ CPU¿¡¼­ À¥¼­¹ö¸¦ + ½ÇÇàÇÑ´Ù¸é »ç¿ëÇ϶ó. ÄÄÇ»ÅÍ°¡ ´À¸®´Ù¸é ù¹ø° ¹æ¹ýÀ̳ª + ´õ ³ªÀº ErrorDocument + CGI ½ºÅ©¸³Æ®¸¦ »ç¿ëÇ϶ó.

+
+
+ + + +

È®Àå ¸®´ÙÀÌ·º¼Ç

+ + + +
+
»óȲ¼³¸í:
+ +
+

°¡²û ¸®´ÙÀÌ·º¼ÇÇÏ´Â URLÀ» ´õ Á¶ÀýÇÒ ÇÊ¿ä°¡ ÀÖ´Ù. + ¾ÆÆÄÄ¡ ³»ºÎ URL escape ÇÔ¼ö´Â "url#anchor" + °°Àº URLÀÇ anchorµµ escapeÇÑ´Ù. ¾ÆÆÄÄ¡ÀÇ + uri_escape() ÇÔ¼ö´Â ¿ì¹°Á¤ÀÚ(#)µµ °°ÀÌ + escapeÇϹǷΠ»ç¿ëÇÒ ¼ö ¾ø´Ù. ±×·¯¸é ¾î¶»°Ô ÀÌ·± URL·Î + ¸®´ÙÀÌ·º¼ÇÇÒ ¼ö ÀÖ³ª?

+
+ +
ÇØ°áÃ¥:
+ +
+

Á÷Á¢ ¸®´ÙÀÌ·º¼ÇÇÏ´Â NPH-CGI ½ºÅ©¸³Æ®¸¦ »ç¿ëÇÑ ÇØ°áÃ¥ÀÌ + ÇÊ¿äÇÏ´Ù. escape¸¦ ÇÏÁö ¾Ê±â¶§¹®ÀÌ´Ù (NPH=non-parseable + headers). ¸ÕÀú ´ÙÀ½ ¼­¹ö¼³Á¤À» ÇÏ¿© (ÀçÀÛ¼º ±ÔÄ¢ÀÇ + ³¡ºÎºÐ¿¡ »ç¿ëÇØ¾ß ÇÑ´Ù) »õ·Î¿î URL scheme + xredirect:¸¦ µµÀÔÇÑ´Ù:

+ +
+RewriteRule ^xredirect:(.+) /path/to/nph-xredirect.cgi/$1 \
+            [T=application/x-httpd-cgi,L]
+
+ +

±×·¯¸é xredirect:·Î ½ÃÀÛÇÏ´Â ¸ðµç URLÀº + nph-xredirect.cgi ÇÁ·Î±×·¥À» ÅëÇÏ°Ô µÈ´Ù. + ÇÁ·Î±×·¥Àº ´ÙÀ½°ú °°´Ù:

+ +
+#!/path/to/perl
+##
+##  nph-xredirect.cgi -- NPH/CGI script for extended redirects
+##  Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved.
+##
+
+$| = 1;
+$url = $ENV{'PATH_INFO'};
+
+print "HTTP/1.0 302 Moved Temporarily\n";
+print "Server: $ENV{'SERVER_SOFTWARE'}\n";
+print "Location: $url\n";
+print "Content-type: text/html\n";
+print "\n";
+print "<html>\n";
+print "<head>\n";
+print "<title>302 Moved Temporarily (EXTENDED)</title>\n";
+print "</head>\n";
+print "<body>\n";
+print "<h1>Moved Temporarily (EXTENDED)</h1>\n";
+print "The document has moved <a HREF=\"$url\">here</a>.<p>\n";
+print "</body>\n";
+print "</html>\n";
+
+##EOF##
+
+ +

±×·¯¸é mod_rewrite°¡ Á÷Á¢ ¹ÞÁö¸øÇÏ´Â + ¸ðµç URL schemeÀ¸·Î ¸®´ÙÀÌ·º¼ÇÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, + ´ÙÀ½°ú °°ÀÌ news:newsgroupÀ¸·Î ¸®´ÙÀÌ·º¼ÇÇÒ + ¼ö ÀÖ´Ù

+ +
+RewriteRule ^anyurl  xredirect:news:newsgroup
+
+ +
ÁÖÀÇ: À§ÀÇ Æ¯º°ÇÑ "Åë°ú" ±ÔÄ¢À» »ç¿ëÇÏ¿© + xredirect:¸¦ ¸¶Áö¸·¿¡ È®ÀåÇØ¾ß Çϱ⶧¹®¿¡ + ±ÔÄ¢¿¡ [R]À̳ª [R,L]À» »ç¿ëÇϸé + ¾ÈµÈ´Ù.
+
+
+ + + +

ÀúÀå¼Ò Á¢±Ù Áß°è(multiplexer)

+ + + +
+
»óȲ¼³¸í:
+ +
+

http://www.perl.com/CPAN¿¡ + ÀÖ´Â ´ë´ÜÇÑ CPAN (Comprehensive Perl Archive Network)À» + ¾Æ´Â°¡? ÀÌ ÁÖ¼Ò´Â ¼¼°è¿¡ Èð¾îÁø ¿©·¯ CPAN ¹Ì·¯ FTP + ¼­¹öÁß Å¬¶óÀ̾ðÆ®¿¡ °¡±îÀÌ ÀÖ´Â ¼­¹ö·Î ¸®´ÙÀÌ·º¼ÇÇÑ´Ù. + À̸¦ FTP Á¢±Ù Áß°è ¼­ºñ½º¶ó°í ÇÑ´Ù. CPANÀº CGI ½ºÅ©¸³Æ®¸¦ + »ç¿ëÇÏÁö¸¸, mod_rewrite¸¦ »ç¿ëÇÏ¿© + ºñ½ÁÇÏ°Ô ¸¸µé ¼ö ÀÖÀ»±î?

+
+ +
ÇØ°áÃ¥:
+ +
+

¸ÕÀú mod_rewrite 3.0.0 ¹öÀüºÎÅÍ + ¸®´ÙÀÌ·º¼Ç¿¡ "ftp:" schemeÀ» »ç¿ëÇÒ ¼ö + ÀÖ´Ù. ´ÙÀ½À¸·Î Ŭ¶óÀ̾ðÆ®ÀÇ ÃÖ»óÀ§ µµ¸ÞÀÎÀ» RewriteMap°ú °°ÀÌ + »ç¿ëÇÏ¿© À§Ä¡¸¦ ÃßÁ¤ÇÒ ¼ö ÀÖ´Ù. º¹ÀâÈ÷ ¿«ÀÎ ±ÔÄ¢¿¡¼­ + ÃÖ»óÀ§ µµ¸ÞÀÎÀ» Áß°è¸ÊÀÇ Å°·Î »ç¿ëÇÑ´Ù.

+ +
+RewriteEngine on
+RewriteMap    multiplex                txt:/path/to/map.cxan
+RewriteRule   ^/CxAN/(.*)              %{REMOTE_HOST}::$1                 [C]
+RewriteRule   ^.+\.([a-zA-Z]+)::(.*)$  ${multiplex:$1|ftp.default.dom}$2  [R,L]
+
+ +
+##
+##  map.cxan -- Multiplexing Map for CxAN
+##
+
+de        ftp://ftp.cxan.de/CxAN/
+uk        ftp://ftp.cxan.uk/CxAN/
+com       ftp://ftp.cxan.com/CxAN/
+ :
+##EOF##
+
+
+
+ + + +

½Ã°£¿¡ µû¸¥ ÀçÀÛ¼º

+ + + +
+
»óȲ¼³¸í:
+ +
+

½Ã°£¿¡ µû¶ó ´Ù¸¥ ³»¿ëÀ» ¼­ºñ½ºÇÏ´Â °æ¿ì ¸¹Àº À¥°ü¸®ÀÚ´Â + Àá½Ã Ưº°ÇÑ ÆäÀÌÁö·Î ¸®´ÙÀÌ·º¼ÇÇϱâÀ§ÇØ CGI ½ºÅ©¸³Æ®¸¦ + »ç¿ëÇÑ´Ù. mod_rewrite·Î´Â ¾î¶»°Ô + ÇÒ ¼ö Àִ°¡?

+
+ +
ÇØ°áÃ¥:
+ +
+

ÀçÀÛ¼º Á¶°Ç¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖ´Â ¿©·¯ TIME_xxx + º¯¼ö°¡ ÀÖ´Ù. º¯¼ö¿Í Ưº°ÇÑ »çÀü¼ø¼­ ºñ±³ + <STRING, >STRING, + =STRINGÀ» »ç¿ëÇÏ¿© ½Ã°£¿¡ µû¶ó ¸®´ÙÀÌ·º¼ÇÇÒ + ¼ö ÀÖ´Ù:

+ +
+RewriteEngine on
+RewriteCond   %{TIME_HOUR}%{TIME_MIN} >0700
+RewriteCond   %{TIME_HOUR}%{TIME_MIN} <1900
+RewriteRule   ^foo\.html$             foo.day.html
+RewriteRule   ^foo\.html$             foo.night.html
+
+ +

URL foo.htmlÀ» ¿äûÇϸé + 07:00-19:00 µ¿¾È foo.day.html + ³»¿ëÀ» ¼­ºñ½ºÇÏ°í, ³ª¸ÓÁö ½Ã°£ µ¿¾È + foo.night.html ³»¿ëÀ» ¼­ºñ½ºÇÑ´Ù. ȨÆäÀÌÁö¿¡¼­ + »ç¿ëÇϱâ ÁÁÀº ±â´ÉÀÌ´Ù...

+
+
+ + + +

YYYY¸¦ XXXX·Î ÀÌÀüÇÑ °æ¿ì ¿ªÈ£È¯

+ + + +
+
»óȲ¼³¸í:
+ +
+

¿©·¯ .html ÆÄÀÏÀ» .phtml·Î + º¯È¯ÇÏ´Â µî document.YYYY¸¦ + document.XXXX·Î ÀÌÀüÇÑÈÄ ¿ªÈ£È¯(backward + compatibility) URLÀ» (°¡»óÀûÀ¸·Î Á¸ÀçÇÏ°Ô) ¸¸µé ¼ö + ÀÖ³ª?

+
+ +
ÇØ°áÃ¥:
+ +
+

À̸§À» ±âº»À̸§À¸·Î ÀçÀÛ¼ºÇÑÈÄ »õ·Î¿î È®ÀåÀÚ¸¦ + °¡Áø ÆÄÀÏÀÌ ÀÖ´ÂÁö °Ë»çÇÑ´Ù. ÀÖ´Ù¸é ±× ÆÄÀϸíÀ» »ç¿ëÇÏ°í, + ¾øÀ¸¸é URLÀ» ¿ø·¡ »óÅ·ΠÀçÀÛ¼ºÇÑ´Ù.

+ + +
+#   ¹®¼­.html ÀÌ ¾ø°í
+#   ¹®¼­.phtml ¸¸ ÀÖ´Â °æ¿ì
+#   ¹®¼­.html À» ¹®¼­.phtml ·Î
+#   ÀçÀÛ¼ºÇÏ´Â ¿ªÈ£È¯ ±ÔÄ¢
+RewriteEngine on
+RewriteBase   /~quux/
+#   ±âº»À̸§À» ã°í, ã¾Ò´Ù´Â »ç½ÇÀ» ±â¾ïÇÑ´Ù
+RewriteRule   ^(.*)\.html$              $1      [C,E=WasHTML:yes]
+#   ÆÄÀÏÀÌ ÀÖ´Ù¸é ¹®¼­.phtml ·Î ÀçÀÛ¼ºÇÑ´Ù
+RewriteCond   %{REQUEST_FILENAME}.phtml -f
+RewriteRule   ^(.*)$ $1.phtml                   [S=1]
+#   ¾Æ´Ï¸é ¾Õ¿¡¼­ ãÀº ±âº»À̸§À» µÇµ¹¸°´Ù
+RewriteCond   %{ENV:WasHTML}            ^yes$
+RewriteRule   ^(.*)$ $1.html
+
+
+
+ + + +
top
+
+

ÄÁÅÙÃ÷ ´Ù·ç±â

+ + + +

»õ·Î ÀÌÀü (°¨Ãß±â)

+ + + +
+
»óȲ¼³¸í:
+ +
+

ÃÖ±Ù foo.htmlÀ» bar.html·Î + º¯°æÇÏ°í ¿ªÈ£È¯¼ºÀ» À§ÇØ ÀÌÀü URLÀ» °è¼Ó Á¦°øÇÏ°í + ½Í´Ù°í °¡Á¤ÇÏÀÚ. »ç¿ëÀÚ´Â ÀÌÀü URLÀÌ º¯°æµÇ¾ú´Ù´Â + »ç½ÇÀ» ´«Ä¡Ã¤Áö ¸øÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

´ÙÀ½ ±ÔÄ¢À¸·Î ÀÌÀü URLÀ» ³»ºÎÀûÀ¸·Î »õ·Î¿î URL·Î + ÀçÀÛ¼ºÇÑ´Ù:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  bar.html
+
+
+
+ + + +

»õ·Î ÀÌÀü (¾Ë¸®±â)

+ + + +
+
»óȲ¼³¸í:
+ +
+

´Ù½Ã foo.htmlÀ» bar.html·Î + º¯°æÇÏ°í ¿ªÈ£È¯¼ºÀ» À§ÇØ ÀÌÀü URLÀ» °è¼Ó Á¦°øÇÏ°í + ½Í´Ù°í °¡Á¤ÇÏÀÚ. ±×·¯³ª ÀÌÁ¦´Â ÀÌÀü URLÀ» »ç¿ëÇϸé + »ç¿ëÀÚ¿¡°Ô »õ·Î¿î URLÀ» ÈùÆ®·Î ¾Ë·ÁÁØ´Ù. Áï, ºê¶ó¿ìÀú + ÁÖ¼ÒâÀÌ º¯ÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

»õ·Î¿î URL·Î HTTP ¸®´ÙÀÌ·º¼ÇÇÏ´Ù. ±×·¯¸é ºê¶ó¿ìÀú°¡ + »õ·Î¿î URL¸¦ º¸ÀÌ°í º¯°æ»ç½ÇÀ» »ç¿ëÀÚ°¡ ¾Ë°ÔµÈ´Ù:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  bar.html  [R]
+
+
+
+ + + +

ºê¶ó¿ìÀú¿¡ µû¸¥ ³»¿ë

+ + + +
+
»óȲ¼³¸í:
+ +
+

ÃÖ¼ÒÇÑ Áß¿äÇÑ ÃÖ»óÀ§ ÆäÀÌÁö´Â ºê¶ó¿ìÀú¿¡ ÃÖÀûÈ­µÈ + ³»¿ëÀ¸·Î ¼­ºñ½ºÇؾßÇÒ °æ¿ì°¡ ÀÖ´Ù. Áï, ÃֽŠNetscape + ºê¶ó¿ìÀú¿¡°Ô´Â ÃÖ»óÀÇ ¹öÀüÀ», Lynx ºê¶ó¿ìÀú¿¡°Ô´Â + ÃÖÀú ¹öÀüÀ», ³ª¸ÓÁö ºê¶ó¿ìÀú¿¡´Â Æò±ÕÀûÀÎ ¹öÀüÀ» + Á¦°øÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

ºê¶ó¿ìÀú°¡ ³»¿ëÇù»óÀ» À§ÇØ ÀÚ½ÅÀÇ Á¾·ù¿¡ ´ëÇÑ Á¤º¸¸¦ + Á¦°øÇÏÁö ¾Ê±â¶§¹®¿¡ ³»¿ëÇù»óÀ» »ç¿ëÇÒ ¼ö ¾ø´Ù. ´ë½Å + HTTP "User-Agent" Çì´õ¸¦ »ç¿ëÇÑ´Ù. ´ÙÀ½ ±ÔÄ¢Àº HTTP + "User-Agent" Çì´õ°¡ "Mozilla/3"À¸·Î ½ÃÀÛÇϸé + foo.html ÆäÀÌÁö¸¦ foo.NS.html·Î + ÀçÀÛ¼ºÇÏ°í ÀçÀÛ¼ºÀ» Áß´ÜÇÑ´Ù. ºê¶ó¿ìÀú°¡ "Lynx"³ª + "Mozilla" ¹öÀü 1 ȤÀº 2¶ó¸é URLÀº + foo.20.htmlÀÌ µÈ´Ù. ³ª¸ÓÁö ºê¶ó¿ìÀú´Â + foo.32.html ÆäÀÌÁö¸¦ ¹Þ´Â´Ù. ¾Æ·¡ ±ÔÄ¢ÀÌ + ÀÌ ÀÛ¾÷À» ÇÑ´Ù:

+ +
+RewriteCond %{HTTP_USER_AGENT}  ^Mozilla/3.*
+RewriteRule ^foo\.html$         foo.NS.html          [L]
+
+RewriteCond %{HTTP_USER_AGENT}  ^Lynx/.*         [OR]
+RewriteCond %{HTTP_USER_AGENT}  ^Mozilla/[12].*
+RewriteRule ^foo\.html$         foo.20.html          [L]
+
+RewriteRule ^foo\.html$         foo.32.html          [L]
+
+
+
+ + + +

µ¿Àû ¹Ì·¯

+ + + +
+
»óȲ¼³¸í:
+ +
+

¿ÜºÎ È£½ºÆ®¿¡ ¿ì¸® »çÀÌÆ®·Î °¡Á®¿À°í ½ÍÀº ÁÁÀº + À¥ÆäÀÌÁö°¡ ÀÖ´Ù°í °¡Á¤ÇÏÀÚ. FTP ¼­¹öÀÇ °æ¿ì Á÷Á¢ ¿ÜºÎ + ÀÚ·áÀÇ Ãֽź¹»çº»À» À¯ÁöÇÏ´Â mirror ÇÁ·Î±×·¥À» + »ç¿ëÇÒ ¼ö ÀÖ°í, À¥¼­¹ö¶ó¸é HTTP·Î ºñ½ÁÇÑ ÀÛ¾÷À» ÇÏ´Â + webcopy ÇÁ·Î±×·¥À» »ç¿ëÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª + µÎ ¹æ¹ý ¸ðµÎ ´ÜÁ¡ÀÌ ÀÖ´Ù: º¹»çº»Àº °¡²û¾¿ ÇÁ·Î±×·¥À» + ½ÇÇàÇØÁÙ ¶§¸¸ ÃÖ½ÅÆÇÀ¸·Î À¯ÁöµÈ´Ù. Á÷Á¢ ±¸¼ºÇؾßÇÏ´Â + Á¤ÀûÀÎ ¹Ì·¯°¡ ¾Æ´Ï¶ó¸é ÁÁ°Ú´Ù. ´ë½Å (¿ÜºÎ È£½ºÆ®¿¡¼­ + ÀÚ·á°¡ °»½ÅµÇ¸é) ÇÊ¿äÇÒ¶§ ÀÚµ¿À¸·Î ÀڷḦ °»½ÅÇÏ´Â + µ¿Àû ¹Ì·¯°¡ ÇÊ¿äÇÏ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

À̸¦ À§ÇØ Proxy Throughput ±â´ÉÀ» (Ç÷¡±× + [P]) »ç¿ëÇÏ¿© ¿ÜºÎ À¥ÆäÀÌÁö ȤÀº ¿ÜºÎ + À¥°ø°£ Àüü¸¦ ¿ì¸® À̸§°ø°£À¸·Î ´ëÀÀÇÑ´Ù:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^hotsheet/(.*)$  http://www.tstimpreso.com/hotsheet/$1  [P]
+
+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^usa-news\.html$   http://www.quux-corp.com/news/index.html  [P]
+
+
+
+ + + +

µ¿Àû ¿ª¹Ì·¯

+ + + +
+
»óȲ¼³¸í:
+ +
...
+ +
ÇØ°áÃ¥:
+ +
+
+RewriteEngine on
+RewriteCond   /mirror/of/remotesite/$1           -U
+RewriteRule   ^http://www\.remotesite\.com/(.*)$ /mirror/of/remotesite/$1
+
+
+
+ + + +

¾ø´Â ÀڷḦ ÀÎÆ®¶ó³Ý¿¡¼­ °¡Á®¿À±â

+ + + +
+
»óȲ¼³¸í:
+ +
+

½ÇÁ¦ ÀڷḦ ¹æÈ­º®ÀÌ º¸È£ÇÏ´Â (³»ºÎ) ÀÎÆ®¶ó³Ý À¥¼­¹ö¿¡ + (www2.quux-corp.dom) ÀúÀåÇϸ鼭, ±â¾÷ÀÇ + (¿ÜºÎ) ÀÎÅÍ³Ý À¥¼­¹ö¸¦ (www.quux-corp.dom) + ½ÇÇàÇÏ´Â °Íó·³ º¸ÀÌ°Ô ÇÑ´Ù. ¿ÜºÎ À¥¼­¹ö´Â ¿äûÇÑ + ÀڷḦ ³»ºÎ À¥¼­¹ö¿¡¼­ °¡Á®¿Â´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

¸ÕÀú ¹æÈ­º®ÀÌ ³»ºÎ À¥¼­¹ö¸¦ º¸È£ÇÏ°í ¿ÜºÎ À¥¼­¹ö¸¸ÀÌ + ³»ºÎ À¥¼­¹ö¿¡¼­ ÀڷḦ ¾òÀ» ¼ö ÀÖ°Ô ÇÑ´Ù. ´ÙÀ½°ú °°ÀÌ + ÆÐŶÇÊÅ͸µ ¹æÈ­º®À» ¼³Á¤ÇÑ´Ù:

+ +
+ALLOW Host www.quux-corp.dom Port >1024 --> Host www2.quux-corp.dom Port 80
+DENY  Host *                 Port *     --> Host www2.quux-corp.dom Port 80
+
+ +

½ÇÁ¦ ¼³Á¤¹®¹ý¿¡ ¾Ë¸Â°Ô °íÃĶó. ¾ø´Â ÀڷḦ ³»ºÎÀûÀ¸·Î + proxy throughput ±â´ÉÀ» ÅëÇØ ¿äûÇÏ´Â + mod_rewrite ±ÔÄ¢À» ÀÛ¼ºÇÑ´Ù:

+ +
+RewriteRule ^/~([^/]+)/?(.*)          /home/$1/.www/$2
+RewriteCond %{REQUEST_FILENAME}       !-f
+RewriteCond %{REQUEST_FILENAME}       !-d
+RewriteRule ^/home/([^/]+)/.www/?(.*) http://www2.quux-corp.dom/~$1/pub/$2 [P]
+
+
+
+ + + +

·Îµå¹ë·±½Ì (ºÎÇÏ ºÐ»êÇϱâ)

+ + + +
+
»óȲ¼³¸í:
+ +
+

www.foo.comÀÇ Åë½Å·®À» + www[0-5].foo.com (ÃÑ ¼­¹ö 6´ë)À¸·Î ºÐ»êÇÏ°í + ½Í´Ù. ¾î¶»°Ô Çϴ°¡?

+
+ +
ÇØ°áÃ¥:
+ +
+

¸Å¿ì ´Ù¾çÇÑ ¹æ¹ýÀ¸·Î ÀÌ ¹®Á¦¸¦ ÇØ°áÇÒ ¼ö ÀÖ´Ù. + ¸ÕÀú DNS¸¦ »ç¿ëÇÑ Àß ¾Ë·ÁÁø ¹æ¹ýÀ» ¼³¸íÇÏ°í, + mod_rewrite¸¦ »ç¿ëÇÏ´Â °æ¿ì¸¦ »ìÆ캸ÀÚ:

+ +
    +
  1. + DNS Round-Robin + +

    °¡Àå °£´ÜÇÑ ·Îµå¹ë·±½Ì ¹æ¹ýÀº BINDÀÇ + DNS round-robin ¹æ½ÄÀ» »ç¿ëÇÏ´Â °ÍÀÌ´Ù. ´ÙÀ½°ú + °°ÀÌ DNS A(address) ·¹Äڵ忡 + www[0-9].foo.comÀ» ¼³Á¤ÇÑ´Ù.

    + +
    +www0   IN  A       1.2.3.1
+www1   IN  A       1.2.3.2
+www2   IN  A       1.2.3.3
+www3   IN  A       1.2.3.4
+www4   IN  A       1.2.3.5
+www5   IN  A       1.2.3.6
+
    + +

    ±×¸®°í ´ÙÀ½ Ç׸ñÀ» Ãß°¡ÇÑ´Ù:

    + +
    +www    IN  CNAME   www0.foo.com.
+       IN  CNAME   www1.foo.com.
+       IN  CNAME   www2.foo.com.
+       IN  CNAME   www3.foo.com.
+       IN  CNAME   www4.foo.com.
+       IN  CNAME   www5.foo.com.
+       IN  CNAME   www6.foo.com.
+
    + +

    À߸øµÈ °Íó·³ º¸ÀÌÁö¸¸, ½ÇÁ¦·Î BINDÀÇ + ÀǵµµÈ ±â´ÉÀÌ´Ù. ÀÌÁ¦ www.foo.comÀ» + ãÀ¸¸é, BIND´Â ¸Å¹ø ¼ø¼­¸¦ Á¶±Ý¾¿ + ¹Ù²ã°¡¸ç www0-www6À» ¹ÝȯÇÑ´Ù. ±×·¡¼­ + Ŭ¶óÀ̾ðÆ®µéÀ» ¿©·¯ ¼­¹ö·Î ºÐ»êÇÑ´Ù. ±×·¯³ª DNS + °Ë»ö °á°ú°¡ ³×Æ®¿÷ÀÇ ´Ù¸¥ ³×ÀÓ¼­¹ö¿¡ ij½¬µÇ¿© + www.foo.comÀ» ãÀº °á°ú°¡ ƯÁ¤ + wwwN.foo.comÀ̸é Ŭ¶óÀ̾ðÆ®ÀÇ ´ÙÀ½ + ¿äûµéµµ °°Àº wwwN.foo.comÀ¸·Î + º¸³»Áö±â¶§¹®¿¡ ¿Ïº®ÇÑ ·Îµå¹ë·±½Ì ±â¹ýÀÌ ¾Æ´ÔÀ» + ÁÖÀÇÇ϶ó. ±×·¯³ª Å©°Ô º¸¸é ¿äûÀÌ ¿©·¯ À¥¼­¹ö¿¡ + ºÐ»êµÇ¹Ç·Î È¿°ú°¡ ÁÁ´Ù.

    +
    2. + +
  2. + DNS ·Îµå¹ë·±½Ì + +

    http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html¿¡ + ÀÖ´Â lbnamed ÇÁ·Î±×·¥À» »ç¿ëÇÏ¿© + Á¤±³ÇÑ DNS±â¹Ý ·Îµå¹ë·±½ÌÀ» ÇÒ ¼ö ÀÖ´Ù. DNS°¡ + ½ÇÁ¦ ·Îµå¹ë·±½ÌÀ» Çϵµ·Ï ¸¸µå´Â ¿©·¯ µµ±¸¿Í Perl + 5 ÇÁ·Î±×·¥ÀÌ´Ù.

    +
    3. + +
  3. + Proxy Throughput Round-Robin + +

    ÀÌ ¹æ¹ýÀº mod_rewrite¿Í proxy + throughput ±â´ÉÀ» »ç¿ëÇÑ´Ù. ¸ÕÀú DNS¿¡ ´ÙÀ½ Ç׸ñÀ» + »ç¿ëÇÏ¿© www0.foo.comÀÌ ½ÇÁ¦ + www.foo.comÀ» Àü´ãÇÏ°Ô ÇÑ´Ù

    + +
    +www    IN  CNAME   www0.foo.com.
+
    + +

    ±×¸®°í www0.foo.comÀ» ÇÁ·Ï½ÃÀü¿ë + ¼­¹ö·Î º¯°æÇÑ´Ù. Áï, URLÀ» ¹ÞÀ¸¸é ¼­¹ö´Â ³»ºÎ + ÇÁ·Ï½Ã¸¦ ÅëÇØ ´Ù¸¥ 5´ë ¼­¹öÁß (www1-www5) + ÇÑ´ë·Î º¸³»±â¸¸ ÇÑ´Ù. À̸¦ À§ÇØ ¸ÕÀú ¸ðµç URLÀ» + ·Îµå¹ë·±½Ì ½ºÅ©¸³Æ® lb.pl·Î º¸³»´Â + ±ÔÄ¢À» ¸¸µç´Ù.

    + +
    +RewriteEngine on
+RewriteMap    lb      prg:/path/to/lb.pl
+RewriteRule   ^/(.+)$ ${lb:$1}           [P,L]
+
    + +

    lb.plÀ» ÀÛ¼ºÇÑ´Ù:

    + +
    +#!/path/to/perl
+##
+##  lb.pl -- ·Îµå¹ë·±½Ì ½ºÅ©¸³Æ®
+##
+
+$| = 1;
+
+$name   = "www";     # ±âº» È£½ºÆ®¸í
+$first  = 1;         # ù¹ø° ¼­¹ö (ÀÚ½ÅÀÌ 0À̱⠶§¹®¿¡, 0À» »ç¿ëÇÏÁö ¾Ê´Â´Ù)
+$last   = 5;         # round-robin¿¡¼­ ¸¶Áö¸· ¼­¹ö
+$domain = "foo.dom"; # µµ¸ÞÀθí
+
+$cnt = 0;
+while (<STDIN>) {
+    $cnt = (($cnt+1) % ($last+1-$first));
+    $server = sprintf("%s%d.%s", $name, $cnt+$first, $domain);
+    print "http://$server/$_";
+}
+
+##EOF##
+
    + +
    ¸¶Áö¸· ÁÖÀÇ: ¿Ö ÀÌ ¹æ¹ýÀÌ À¯¿ëÇÑ°¡? + www0.foo.com¿¡ ºÎ´ãÀÌ °¡Áö¾Ê´Â°¡? + ¹°·Ð, ºÎ´ãÀÌ µÈ´Ù. ±×·¯³ª ´Ü¼øÇÑ proxy throughput + ¿äû¸¸ Çϱ⶧¹®¿¡ ±¦Âú´Ù! ¸ðµç SSI, CGI, ePerl + µîÀº ÀüÀûÀ¸·Î ´Ù¸¥ ¼­¹ö°¡ ó¸®ÇÑ´Ù. ÀÌ°ÍÀÌ ÇÙ½ÉÀÌ´Ù.
    +
    4. + +
  4. + Çϵå¿þ¾î/TCP Round-Robin + +

    Çϵå¿þ¾î¸¦ »ç¿ëÇÑ ÇØ°áÃ¥µµ ÀÖ´Ù. Cisco´Â TCP/IP + ¼öÁØ¿¡¼­ ·Îµå¹ë·±½ÌÀ» ÇÏ´Â LocalDirector¶ó´Â ±«¹°À» + ÆÇ´Ù. ½ÇÁ¦·Î´Â À¥¼­¹ö±º ¾Õ´Ü¿¡ À§Ä¡ÇÏ´Â ÀÏÁ¾ÀÇ + ȸ·Î¼öÁØ °ÔÀÌÆ®¿þÀÌ´Ù. ÀÚ±ÝÀÌ ÃæºÐÇÏ°í °í¼º´É + ÇØ°áÃ¥ÀÌ ÇÊ¿äÇÏ´Ù¸é ÀÌ°ÍÀ» »ç¿ëÇ϶ó.

    +
    5. +
+
+
+ + + +

»õ·Î¿î MIME-type, »õ·Î¿î ¼­ºñ½º

+ + + +
+
»óȲ¼³¸í:
+ +
+

³×Æ®¿÷¿¡´Â ¸ÚÁø CGI ÇÁ·Î±×·¥µéÀÌ ¸¹´Ù. ±×·¯³ª »ç¿ëÇϱâ + ¹ø°Å·¯¿ö¼­ ¸¹Àº À¥°ü¸®ÀÚ°¡ »ç¿ëÇÏÁö ¾Ê´Â´Ù. ¾ÆÆÄÄ¡ÀÇ + MIME-type¿¡ µû¸¥ Action Çڵ鷯 ±â´Éµµ CGI ÇÁ·Î±×·¥ÀÌ + Ưº°ÇÑ URLÀ» (Á¤È®È÷ PATH_INFO¿Í + QUERY_STRINGS) ÇÁ·Î±×·¥ÀÇ ÀÔ·ÂÀ¸·Î »ç¿ëÇÏÁö + ¾ÊÀ» ¶§¸¸ ÀûÀýÇÏ´Ù. ¸ÕÀú, È®ÀåÀÚ°¡ (secure CGI¸¦ ÁÙ¿©) + .scgiÀÎ ÆÄÀÏÀ» À¯¸íÇÑ cgiwrap + ÇÁ·Î±×·¥À¸·Î ó¸®ÇϱâÀ§ÇØ »õ·Î¿î typeÀ» ¼³Á¤ÇÑ´Ù. + ¹®Á¦´Â (À§¿¡¼­ º») ÀÏ°üµÈ URL ±¸Á¶¸¦ »ç¿ëÇÏ´Â °æ¿ì + »ç¿ëÀÚ È¨µð·ºÅ丮°¡ /u/user/foo/bar.scgi°°Àº + URLÀÎ Á¡ÀÌ´Ù. cgiwrap´Â + /~user/foo/bar.scgi/ Çü½ÄÀÇ URLÀ» + ¿øÇϱ⶧¹®ÀÌ´Ù. ´ÙÀ½ ±ÔÄ¢ÀÌ ¹®Á¦¸¦ ÇØ°áÇÑ´Ù:

+ +
+RewriteRule ^/[uge]/([^/]+)/\.www/(.+)\.scgi(.*) ...
+... /internal/cgi/user/cgiwrap/~$1/$2.scgi$3  [NS,T=application/x-http-cgi]
+
+ +

ÀÌÁ¦ ´Ù¸¥ ¸ÚÁø ÇÁ·Î±×·¥, (URL ÇÏÀ§Æ®¸®¿¡ ´ëÇÑ + access.log¸¦ Ãâ·ÂÇÏ´Â) wwwlog¿Í + (URL ÇÏÀ§Æ®¸®¿¡ Glimpse¸¦ ½ÇÇàÇÏ´Â) wwwidx°¡ + ÀÖ´Ù°í °¡Á¤ÇÏÀÚ. ¿ì¸®´Â ÇÁ·Î±×·¥¿¡°Ô ÀÛ¾÷ÇÒ ´ë»óÀÎ + URL ¿µ¿ªÀ» ¾Ë·ÁÁà¾ß ÇÑ´Ù. ±×·¯³ª ¿äûÇÒ¶§¸¶´Ù Ç×»ó + Àû¾îÁà¾ß Çϱ⶧¹®¿¡ ±ò²ûÇÏÁö ¾Ê´Ù. Áï, º¸Åë + /u/user/foo/¿¡ ´ëÇØ swwidx + ÇÁ·Î±×·¥À» ½ÇÇàÇÑ´Ù¸é ´ÙÀ½°ú °°Àº ¸µÅ©¸¦ »ç¿ëÇÑ´Ù

+ +
+/internal/cgi/user/swwidx?i=/u/user/foo/
+
+ +

±ò²ûÇÏÁö ¾Ê´Ù. ¸µÅ©¿¡ ¿µ¿ªÀÇ À§Ä¡¿Í + CGI À§Ä¡¸¦ ¸ðµÎ Àû¾î¾ß Çϱ⶧¹®ÀÌ´Ù. + ¿µ¿ªÀ» À籸¼ºÇÑ´Ù¸é ¿©·¯ ÇÏÀÌÆÛ¸µÅ©¸¦ ¼öÁ¤Çϴµ¥ ¸¹Àº + ½Ã°£ÀÌ °É¸± °ÍÀÌ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

ÇØ°áÃ¥Àº ÀÚµ¿À¸·Î ÀûÀýÇÑ CGI¸¦ ½ÇÇàÇÏ´Â »õ·Î¿î + Ưº°ÇÑ URL Çü½ÄÀ» ¸¸µå´Â °ÍÀÌ´Ù. ´ÙÀ½°ú °°ÀÌ ¼³Á¤ÇÑ´Ù:

+ +
+RewriteRule   ^/([uge])/([^/]+)(/?.*)/\*  /internal/cgi/user/wwwidx?i=/$1/$2$3/
+RewriteRule   ^/([uge])/([^/]+)(/?.*):log /internal/cgi/user/wwwlog?f=/$1/$2$3
+
+ +

ÀÌÁ¦ /u/user/foo/À» °Ë»öÇÏ´Â ¸µÅ©´Â + ´ÙÀ½°ú °°´Ù

+ +
+HREF="*"
+/u/user/foo/* (???)
+
+ +

³»ºÎÀûÀ¸·Î ´ÙÀ½°ú °°ÀÌ ÀÚµ¿º¯È¯µÈ´Ù

+ +
+/internal/cgi/user/wwwidx?i=/u/user/foo/
+
+ +

°°Àº ¹æ¹ýÀ¸·Î ¸µÅ© µÚ¿¡ :log¸¦ »ç¿ëÇÏ¿© + Á¢±Ù ·Î±× CGI ÇÁ·Î±×·¥À» ½ÇÇàÇÒ ¼ö ÀÖ´Ù.

+
+
+ + + +

Á¤Àû¿¡¼­ µ¿ÀûÀ¸·Î

+ + + +
+
»óȲ¼³¸í:
+ +
+

¾î¶»°Ô ºê¶ó¿ìÀú¿Í »ç¿ëÀÚ°¡ ¸ð¸£°Ô ÀÚ¿¬½º·´°Ô Á¤Àû + ÆäÀÌÁö foo.htmlÀ» µ¿ÀûÀÎ foo.cgi·Î + º¯°æÇÒ ¼ö ÀÖ³ª.

+
+ +
ÇØ°áÃ¥:
+ +
+

URLÀ» CGI ½ºÅ©¸³Æ®·Î ÀçÀÛ¼ºÇÏ°í, MIME-typeÀ» ¼öÁ¤ÇÏ¿© + CGI ½ºÅ©¸³Æ®·Î ½ÇÇàÇÏ°Ô ÇÑ´Ù. ±×·¡¼­ + /~quux/foo.html¸¦ ¿äûÇÏ¸é ³»ºÎÀûÀ¸·Î + /~quux/foo.cgi¸¦ ½ÇÇàÇÏ°Ô µÈ´Ù.

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  foo.cgi  [T=application/x-httpd-cgi]
+
+
+
+ + + +

Áï¼® ÄÁÅÙÃ÷ Àç»ý¼º

+ + + +
+
»óȲ¼³¸í:
+ +
+

ÀÌ ¹æ¹ýÀº ½Ç·Î ºñ±âÀÌ´Ù: µ¿ÀûÀ¸·Î ÆäÀÌÁö¸¦ »ý¼ºÇÏÁö¸¸, + Á¤ÀûÀ¸·Î ÆäÀÌÁö¸¦ ¼­ºñ½ºÇÑ´Ù. Áï, ÆäÀÌÁö´Â ¼ø¼öÇÏ°Ô + (ÆÄÀϽýºÅÛ¿¡¼­ ÀÐÀº ³»¿ëÀ» ±×´ë·Î) Á¤Àû ÆäÀÌÁö·Î + Àü´ÞµÇÁö¸¸, ¾øÀ» °æ¿ì À¥¼­¹ö°¡ µ¿ÀûÀ¸·Î »ý¼ºÇÑ´Ù. + ±×·¯¸é ´©°¡ (ȤÀº cron ÀÛ¾÷ÀÌ) Á¤Àû ÄÁÅÙÃ÷¸¦ Áö¿ìÁö¾Ê´Â + ÇÑ CGI°¡ »ý¼ºÇÑ ÆäÀÌÁö¸¦ Á¤ÀûÀ¸·Î ¼­ºñ½ºÇÑ´Ù. ÄÁÅÙÃ÷¸¦ + Áö¿ì¸é ³»¿ëÀ» °»½ÅÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+ ´ÙÀ½ ±ÔÄ¢À» »ç¿ëÇÑ´Ù: + +
+RewriteCond %{REQUEST_FILENAME}   !-s
+RewriteRule ^page\.html$          page.cgi   [T=application/x-httpd-cgi,L]
+
+ +

¿©±â¼­ page.html¸¦ ¿äûÇÒ¶§ + page.htmlÀÌ ¾ø°Å³ª ÆÄÀÏÅ©±â°¡ 0ÀÎ °æ¿ì + ³»ºÎÀûÀ¸·Î page.cgi¸¦ ½ÇÇàÇÑ´Ù. ¿©±â¼­ + ºñ°áÀº page.cgi°¡ ÀϹÝÀûÀÎ CGI ½ºÅ©¸³Æ®¿Í + °°ÀÌ STDOUT¿¡ Ãâ·ÂÇÏ°í, Ãß°¡·Î Ãâ·ÂÀ» + page.html ÆÄÀÏ¿¡ Àû´Â´Ù. Çѹø ½ÇÇàÇÑÈÄ + ¼­¹ö´Â page.htmlÀÇ Á¤º¸¸¦ º¸³½´Ù. À¥°ü¸®ÀÚ°¡ + °­Àç·Î ³»¿ëÀ» °»½ÅÇÏ°í ½Í´Ù¸é, (º¸Åë cron ÀÛ¾÷ÀÌ) + page.htmlÀ» Áö¿ì±â¸¸ ÇÏ¸é µÈ´Ù.

+
+
+ + + +

ÀÚµ¿À¸·Î »õ·Î °íħÇÏ´Â ¹®¼­

+ + + +
+
»óȲ¼³¸í:
+ +
+

º¹ÀâÇÑ À¥ÆäÀÌÁö¸¦ ¸¸µé¶§ ÆíÁýÀÚ°¡ ³»¿ëÀ» ¼öÁ¤ÇÒ + ¶§¸¶´Ù ÀÚµ¿À¸·Î ÆäÀÌÁö¸¦ »õ·Î °íħÇÏ´Â À¥ºê¶ó¿ìÀú°¡ + ÀÖÀ¸¸é ¾ó¸¶³ª ÁÁÀ»±î? ºÒ°¡´ÉÇÑ°¡?

+
+ +
ÇØ°áÃ¥:
+ +
+

°¡´ÉÇÏ´Ù! MIME multipart ±â´É°ú À¥¼­¹ö NPH ±â´É, + mod_rewriteÀÇ URL Á¶ÀÛ ´É·ÂÀ» °áÇÕÇϸé + µÈ´Ù. ¸ÕÀú, »õ·Î¿î URL ±â´ÉÀ» ¸¸µç´Ù: URL¿¡ + :refresh¸¦ Ãß°¡Çϱ⸸ Çϸé ÆÄÀϽýºÅÛ¿¡¼­ + ¼öÁ¤µÉ ¶§¸¶´Ù »õ·Î °íħÇÑ´Ù.

+ +
+RewriteRule   ^(/[uge]/[^/]+/?.*):refresh  /internal/cgi/apache/nph-refresh?f=$1
+
+ +

ÀÌÁ¦ ´ÙÀ½ URL¿¡ Á¢±ÙÇϸé

+ +
+/u/foo/bar/page.html:refresh
+
+ +

´ÙÀ½ URLÀ» ³»ºÎÀûÀ¸·Î ºÎ¸¥´Ù

+ +
+/internal/cgi/apache/nph-refresh?f=/u/foo/bar/page.html
+
+ +

ÀÌÁ¦ NPH-CGI ½ºÅ©¸³Æ®¸¸ ³²¾Ò´Ù. º¸Åë "µ¶ÀÚ¿¡°Ô + ¿¬½ÀÀ¸·Î ³²°ÜµÒ"À̶ó°í ¸»ÇÏÁö¸¸ ;-) ³ª´Â À̰͵µ Á¦°øÇÑ´Ù.

+ +
+#!/sw/bin/perl
+##
+##  nph-refresh -- NPH/CGI script for auto refreshing pages
+##  Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved.
+##
+$| = 1;
+
+#   split the QUERY_STRING variable
+@pairs = split(/&/, $ENV{'QUERY_STRING'});
+foreach $pair (@pairs) {
+    ($name, $value) = split(/=/, $pair);
+    $name =~ tr/A-Z/a-z/;
+    $name = 'QS_' . $name;
+    $value =~ s/%([a-fA-F0-9][a-fA-F0-9])/pack("C", hex($1))/eg;
+    eval "\$$name = \"$value\"";
+}
+$QS_s = 1 if ($QS_s eq '');
+$QS_n = 3600 if ($QS_n eq '');
+if ($QS_f eq '') {
+    print "HTTP/1.0 200 OK\n";
+    print "Content-type: text/html\n\n";
+    print "&lt;b&gt;ERROR&lt;/b&gt;: No file given\n";
+    exit(0);
+}
+if (! -f $QS_f) {
+    print "HTTP/1.0 200 OK\n";
+    print "Content-type: text/html\n\n";
+    print "&lt;b&gt;ERROR&lt;/b&gt;: File $QS_f not found\n";
+    exit(0);
+}
+
+sub print_http_headers_multipart_begin {
+    print "HTTP/1.0 200 OK\n";
+    $bound = "ThisRandomString12345";
+    print "Content-type: multipart/x-mixed-replace;boundary=$bound\n";
+    &print_http_headers_multipart_next;
+}
+
+sub print_http_headers_multipart_next {
+    print "\n--$bound\n";
+}
+
+sub print_http_headers_multipart_end {
+    print "\n--$bound--\n";
+}
+
+sub displayhtml {
+    local($buffer) = @_;
+    $len = length($buffer);
+    print "Content-type: text/html\n";
+    print "Content-length: $len\n\n";
+    print $buffer;
+}
+
+sub readfile {
+    local($file) = @_;
+    local(*FP, $size, $buffer, $bytes);
+    ($x, $x, $x, $x, $x, $x, $x, $size) = stat($file);
+    $size = sprintf("%d", $size);
+    open(FP, "&lt;$file");
+    $bytes = sysread(FP, $buffer, $size);
+    close(FP);
+    return $buffer;
+}
+
+$buffer = &readfile($QS_f);
+&print_http_headers_multipart_begin;
+&displayhtml($buffer);
+
+sub mystat {
+    local($file) = $_[0];
+    local($time);
+
+    ($x, $x, $x, $x, $x, $x, $x, $x, $x, $mtime) = stat($file);
+    return $mtime;
+}
+
+$mtimeL = &mystat($QS_f);
+$mtime = $mtime;
+for ($n = 0; $n &lt; $QS_n; $n++) {
+    while (1) {
+        $mtime = &mystat($QS_f);
+        if ($mtime ne $mtimeL) {
+            $mtimeL = $mtime;
+            sleep(2);
+            $buffer = &readfile($QS_f);
+            &print_http_headers_multipart_next;
+            &displayhtml($buffer);
+            sleep(5);
+            $mtimeL = &mystat($QS_f);
+            last;
+        }
+        sleep($QS_s);
+    }
+}
+
+&print_http_headers_multipart_end;
+
+exit(0);
+
+##EOF##
+
+
+
+ + + +

´ë·®ÀÇ °¡»óÈ£½ºÆ®

+ + + +
+
»óȲ¼³¸í:
+ +
+

°¡»óÈ£½ºÆ®°¡ ¸î°³¸¸ ÀÖ´Ù¸é ¾ÆÆÄÄ¡ÀÇ <VirtualHost> + ±â´ÉÀÌ Àß µ¿ÀÛÇÑ´Ù. ±×·¯³ª °¡»óÈ£½ºÆ®°¡ ¼ö¹é°³ ÀÖ´Â + ISP¶ó¸é ÀÌ ±â´ÉÀÌ ÃÖ¼±Àº ¾Æ´Ï´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

ÀÌ ±â´ÉÀ» Á¦°øÇÏ·Á¸é Proxy Throughput + ±â´ÉÀ» (Ç÷¡±× [P]) »ç¿ëÇÏ¿© ¿ÜºÎ À¥ÆäÀÌÁö + ȤÀº Àüü ¿ÜºÎ À¥¿µ¿ªÀ» ¿ì¸®ÀÇ À̸§°ø°£¿¡ ´ëÀÀÇÑ´Ù:

+ +
+##
+##  vhost.map
+##
+www.vhost1.dom:80  /path/to/docroot/vhost1
+www.vhost2.dom:80  /path/to/docroot/vhost2
+     :
+www.vhostN.dom:80  /path/to/docroot/vhostN
+
+ +
+##
+##  httpd.conf
+##
+    :
+#   ¸®´ÙÀÌ·ºÆ®ÇÒ¶§ Á¤±Ô È£½ºÆ®¸íÀ» »ç¿ëÇÑ´Ù.
+UseCanonicalName on
+
+    :
+#   °¡»óÈ£½ºÆ®¸¦ CLF Çü½Ä ¾Õ¿¡ Ãß°¡ÇÑ´Ù
+CustomLog  /path/to/access_log  "%{VHOST}e %h %l %u %t \"%r\" %>s %b"
+    :
+
+#   ÁÖ¼­¹ö¿¡¼­ ÀçÀÛ¼º ¿£ÁøÀ» »ç¿ëÇÑ´Ù
+RewriteEngine on
+
+#   µÎ ¸ÊÀ» Á¤ÀÇÇÑ´Ù: Çϳª´Â URLÀ» °íÄ¡°í,
+#   ´Ù¸¥ Çϳª´Â °¡»óÈ£½ºÆ®º° DocumentRoot¸¦
+#   Á¤ÀÇÇÑ´Ù.
+RewriteMap    lowercase    int:tolower
+RewriteMap    vhost        txt:/path/to/vhost.map
+
+#   ÀÌÁ¦ Å©°í º¹ÀâÇÑ ±ÔÄ¢ ÇÑ°³¸¦ »ç¿ëÇÏ¿©
+#   °¡»óÈ£½ºÆ®·Î ´ëÀÀÇÑ´Ù.
+#
+#   1. °¡»óÈ£½ºÆ®µéÀÌ °°ÀÌ »ç¿ëÇÏ´Â À§Ä¡´Â ´ëÀÀÇÏÁö ¾Ê´Â´Ù
+RewriteCond   %{REQUEST_URL}  !^/commonurl1/.*
+RewriteCond   %{REQUEST_URL}  !^/commonurl2/.*
+    :
+RewriteCond   %{REQUEST_URL}  !^/commonurlN/.*
+#
+#   2. ¿ì¸®°¡ ÇöÀç »ç¿ëÇÏ´Â ¹æ¹ýÀÌ Host Çì´õ¸¦
+#      °¡»óÈ£½ºÆ®¸¦ Áö¿øÇϹǷÎ
+#      Host Çì´õ°¡ ÀÖ´ÂÁö È®ÀÎÇÑ´Ù
+RewriteCond   %{HTTP_HOST}  !^$
+#
+#   3. È£½ºÆ®¸íÀ» ¼Ò¹®ÀÚ·Î ¸¸µç´Ù
+RewriteCond   ${lowercase:%{HTTP_HOST}|NONE}  ^(.+)$
+#
+#   4. vhost.map¿¡¼­ È£½ºÆ®¸íÀ» ã°í
+#      °æ·ÎÀ϶§¸¸ ±â¾ïÇÑ´Ù
+#      (À§¿¡¼­ "NONE"Àº ¾Æ´Ï´Ù)
+RewriteCond   ${vhost:%1}  ^(/.*)$
+#
+#   5. ¸¶Áö¸·À¸·Î URLÀ» ¹®¼­ À§Ä¡·Î ´ëÀÀÇÏ°í
+#      ·Î±×¿¡ ³²±â±âÀ§ÇØ °¡»óÈ£½ºÆ®¸¦ ±â¾ïÇØ µÐ´Ù
+RewriteRule   ^/(.*)$   %1/$1  [E=VHOST:${lowercase:%{HTTP_HOST}}]
+    :
+
+
+
+ + + +
top
+
+

Á¢±Ù Á¦ÇÑ

+ + + +

·Îº¿ ¸·±â

+ + + +
+
»óȲ¼³¸í:
+ +
+

¾î¶»°Ô Çϸé ƯÁ¤ À¥°ø°£ÀÇ ÆäÀÌÁö¸¦ ±Ü¾î¸ðÀ¸´Â ±ÍÂúÀº + ·Îº¿À» ¸·À» ¼ö ÀÖ³ª? "Robot Exclusion Protocol" Ç׸ñÀ» + ÀúÀåÇÑ /robots.txt ÆÄÀÏÀº º¸Åë ÀÌ·± ·Îº¿À» + ¸·´Âµ¥ ÃæºÐÇÏÁö ¾Ê´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

(¾Æ¸¶µµ µð·ºÅ丮°¡ ±í¾î¼­ ·Îº¿ÀÌ µ¹¾Æ´Ù´Ï¸é ¼­¹ö¿¡ + ºÎ´ãÀÌ Å« °æ¿ì) À¥°ø°£ /~quux/foo/arc/¿¡ + ÀÖ´Â URLµéÀ» °ÅºÎÇÏ´Â ±ÔÄ¢À» »ç¿ëÇÑ´Ù. ¿ì¸®´Â ƯÁ¤ + ·Îº¿ÀÇ Á¢±ÙÀ» ¸·¾Æ¾ß ÇÑ´Ù. Áï, ·Îº¿À» ½ÇÇàÇϴ ȣ½ºÆ®¸¦ + ¸·´Â °ÍÀ¸·Î´Â ºÒÃæºÐÇϸç, ±× È£½ºÆ®ÀÇ »ç¿ëÀÚµµ ¸·¾Æ¹ö¸®°Ô + µÈ´Ù. User-Agent HTTP Çì´õ Á¤º¸µµ ºñ±³ÇÑ´Ù.

+ +
+RewriteCond %{HTTP_USER_AGENT}   ^NameOfBadRobot.*
+RewriteCond %{REMOTE_ADDR}       ^123\.45\.67\.[8-9]$
+RewriteRule ^/~quux/foo/arc/.+   -   [F]
+
+
+
+ + + +

±×¸² ÆÛ°¡±â ¹æÁö

+ + + +
+
»óȲ¼³¸í:
+ +
+

http://www.quux-corp.de/~quux/¿¡ ÀÖ´Â + ÆäÀÌÁöµéÀÌ GIF ±×¸²À» Æ÷ÇÔÇÑ´Ù°í °¡Á¤ÇÏÀÚ. ÀÌ ±×¸²ÀÌ + ¸ÚÀ־, ´Ù¸¥ »ç¶÷µéÀÌ ÀÚ½ÅÀÇ ÆäÀÌÁö¿¡ Á÷Á¢ ¸µÅ©¸¦ + °Ç´Ù. ¼­¹ö¿¡ ºÒÇÊ¿äÇÑ ºÎ´ãÀÌ µÇ¹Ç·Î ¸·°í ½Í´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

±×¸²À» 100% º¸È£ÇÒ ¼ö´Â ¾øÁö¸¸, ÃÖ¼ÒÇÑ ºê¶ó¿ìÀú°¡ + HTTP Referer Çì´õ¸¦ º¸³»´Â °æ¿ì Á¦ÇÑÇÒ ¼ö ÀÖ´Ù.

+ +
+RewriteCond %{HTTP_REFERER} !^$
+RewriteCond %{HTTP_REFERER} !^http://www.quux-corp.de/~quux/.*$ [NC]
+RewriteRule .*\.gif$        -                                    [F]
+
+ +
+RewriteCond %{HTTP_REFERER}         !^$
+RewriteCond %{HTTP_REFERER}         !.*/foo-with-gif\.html$
+RewriteRule ^inlined-in-foo\.gif$   -                        [F]
+
+
+
+ + + +

È£½ºÆ® °ÅºÎ

+ + + +
+
»óȲ¼³¸í:
+ +
+

¾î¶»°Ô ¿ÜºÎ¿¡¼­ ¼­¹ö¿¡ Á¢±ÙÇÒ ¼ö ¾ø´Â È£½ºÆ® ¸ñ·ÏÀ» + ¼³Á¤ÇÒ ¼ö ÀÖ³ª?

+
+ +
ÇØ°áÃ¥:
+ +
+

¾ÆÆÄÄ¡ >= 1.3b6¿¡¼­:

+ +
+RewriteEngine on
+RewriteMap    hosts-deny  txt:/path/to/hosts.deny
+RewriteCond   ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR]
+RewriteCond   ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND} !=NOT-FOUND
+RewriteRule   ^/.*  -  [F]
+
+ +

¾ÆÆÄÄ¡ <= 1.3b6¿¡¼­:

+ +
+RewriteEngine on
+RewriteMap    hosts-deny  txt:/path/to/hosts.deny
+RewriteRule   ^/(.*)$ ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND}/$1
+RewriteRule   !^NOT-FOUND/.* - [F]
+RewriteRule   ^NOT-FOUND/(.*)$ ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND}/$1
+RewriteRule   !^NOT-FOUND/.* - [F]
+RewriteRule   ^NOT-FOUND/(.*)$ /$1
+
+ +
+##
+##  hosts.deny
+##
+##  ÁÖÀÇ! ÀÌ°ÍÀº ¸ñ·Ïó·³ º¸ÀÌÁö¸¸ ¸ñ·ÏÀÌ ¾Æ´Ï¶ó ¸ÊÀÌ´Ù.
+##        mod_rewrite´Â ÀÌ Á¤º¸¸¦ Å°/°ª ½ÖÀ¸·Î Çؼ®Çϱ⶧¹®¿¡,
+##        °¢ Ç׸ñÀÇ °ª ÀÚ¸®¿¡ ÃÖ¼ÒÇÑ "-"°¡ ÇÊ¿äÇÏ´Ù.
+##
+
+193.102.180.41 -
+bsdti1.sdm.de  -
+192.76.162.40  -
+
+
+
+ + + +

ÇÁ·Ï½Ã °ÅºÎ

+ + + +
+
»óȲ¼³¸í:
+ +
+

¾î¶»°Ô ƯÁ¤ È£½ºÆ® ȤÀº ƯÁ¤ È£½ºÆ®ÀÇ »ç¿ëÀÚ°¡ + ¾ÆÆÄÄ¡ ÇÁ·Ï½Ã¸¦ »ç¿ëÇÒ ¼ö ¾øµµ·Ï Çϳª?

+
+ +
ÇØ°áÃ¥:
+ +
+

¸ÕÀú ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ÄÄÆÄÀÏÇÒ¶§ ±¸¼ºÆÄÀÏ¿¡¼­ + mod_rewrite°¡ mod_proxy + ¾Æ·¡¿¡(!) ÀÖ¾î¾ß ÇÑ´Ù. ±×·¯¸é mod_rewrite´Â + mod_proxy ÀÌÀü¿¡ ºÒ¸°´Ù. + ÀÌÁ¦ ´ÙÀ½°ú °°ÀÌ Æ¯Á¤ È£½ºÆ®¸¦ °ÅºÎÇϵµ·Ï ¼³Á¤ÇÑ´Ù...

+ +
+RewriteCond %{REMOTE_HOST} ^badhost\.mydomain\.com$
+RewriteRule !^http://[^/.]\.mydomain.com.*  - [F]
+
+ +

...±×¸®°í ´ÙÀ½Àº user@host¿¡ µû¶ó °ÅºÎÇÑ´Ù:

+ +
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST}  ^badguy@badhost\.mydomain\.com$
+RewriteRule !^http://[^/.]\.mydomain.com.*  - [F]
+
+
+
+ + + +

Ưº°ÇÑ ÀÎÁõ ¹æ½Ä

+ + + +
+
»óÈ°¼³¸í:
+ +
+

°¡²û ¸Å¿ì Ưº°ÇÑ ÀÎÁõÀÌ ÇÊ¿äÇÒ ¶§°¡ ÀÖ´Ù. ¿¹¸¦ + µé¾î, ¹Ì¸® ¼³Á¤ÇصР»ç¿ëÀÚÀÎÁö °Ë»çÇÑ´Ù. À̵鿡°Ô¸¸ + (mod_auth_basicÀÇ Basic Auth¸¦ »ç¿ëÇÑ + °æ¿ì¿Í ´Þ¸®) º°´Ù¸¥ ¹°À½¾øÀÌ Á¢±ÙÀ» Çã¿ëÇÑ´Ù.

+
+ +
ÇØ°áÃ¥:
+ +
+

Ä£±¸¸¸ Á¢±ÙÀÌ °¡´ÉÇϵµ·Ï ÀçÀÛ¼º ±ÔÄ¢µéÀ» »ç¿ëÇÑ´Ù:

+ +
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend1@client1.quux-corp\.com$
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend2@client2.quux-corp\.com$
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend3@client3.quux-corp\.com$
+RewriteRule ^/~quux/only-for-friends/      -                                 [F]
+
+
+
+ + + +

Referer±â¹Ý º¯È¯±â(deflector)

+ + + +
+
»óȲ¼³¸í:
+ +
+

"Referer" HTTP Çì´õ¿¡ µû¶ó ¿øÇϴ´ë·Î ÂüÁ¶ÆäÀÌÁö¸¦ + ¼³Á¤ÇÒ ¼ö ÀÖ´Â À¯¿¬ÇÑ URL º¯È¯±â¸¦ ¸¸µé ¼ö Àִ°¡?

+
+ +
ÇØ°áÃ¥:
+ +
+

´ÙÀ½°ú °°ÀÌ º¹ÀâÇÑ ±ÔÄ¢À»...

+ +
+RewriteMap  deflector txt:/path/to/deflector.map
+
+RewriteCond %{HTTP_REFERER} !=""
+RewriteCond ${deflector:%{HTTP_REFERER}} ^-$
+RewriteRule ^.* %{HTTP_REFERER} [R,L]
+
+RewriteCond %{HTTP_REFERER} !=""
+RewriteCond ${deflector:%{HTTP_REFERER}|NOT-FOUND} !=NOT-FOUND
+RewriteRule ^.* ${deflector:%{HTTP_REFERER}} [R,L]
+
+ +

... ÀçÀÛ¼º ¸Ê°ú °°ÀÌ »ç¿ëÇÑ´Ù:

+ +
+##
+##  deflector.map
+##
+
+http://www.badguys.com/bad/index.html    -
+http://www.badguys.com/bad/index2.html   -
+http://www.badguys.com/bad/index3.html   http://somewhere.com/
+
+ +

±×·¯¸é ¿äûÀ» ÀÚµ¿À¸·Î (¸Ê¿¡¼­ °ªÀ¸·Î "-"¸¦ + »ç¿ëÇÑ °æ¿ì) ÂüÁ¶ÆäÀÌÁö³ª (URLÀÌ ¸Ê¿¡ ÀÖ´Â °æ¿ì µÎ¹ø° + ¾Æ±Ô¸ÕÆ®·Î) ƯÁ¤ URL·Î ¸®´ÙÀÌ·º¼ÇÇÑ´Ù.

+
+
+ + + +
top
+
+

±âŸ

+ + + +

¿ÜºÎ ÀçÀÛ¼º ¿£Áø

+ + + +
+
»óȲ¼³¸í:
+ +
+

FAQ: ¾î¶»°Ô ÀÌ·±Àú·± Àâ´ÙÇÑ ¹®Á¦¸¦ Ç® ¼ö Àִ°¡? + mod_rewrite·Î´Â ÇØ°áÃ¥ÀÌ ¾Èº¸ÀδÙ...

+
+ +
ÇØ°áÃ¥:
+ +
+

¿ÜºÎ RewriteMapÀ» »ç¿ëÇ϶ó. + Áï, ÇÁ·Î±×·¥ÀÌ RewriteMap ¿ªÇÒÀ» + ÇÑ´Ù. ÇÁ·Î±×·¥Àº ¾ÆÆÄÄ¡°¡ ½ÃÀÛÇÒ¶§ ½ÃÀÛÇÏ¿© + STDIN¿¡¼­ ¿äûÇÑ URLÀ» ¹Þ°í, (°°Àº ¼ø¼­·Î!) + °á°ú (º¸Åë ÀçÀÛ¼ºµÈ) URLÀ» STDOUT¿¡ Ãâ·ÂÇÑ´Ù.

+ +
+RewriteEngine on
+RewriteMap    quux-map       prg:/path/to/map.quux.pl
+RewriteRule   ^/~quux/(.*)$  /~quux/${quux-map:$1}
+
+ +
+#!/path/to/perl
+
+#   ¾ÆÆÄÄ¡ ¼­¹ö°¡ ¸ØÃßÁö ¾Êµµ·Ï
+#   ÀÔÃâ·Â ¹öÆÛ¸¦ »ç¿ëÇÏÁö ¾Ê´Â´Ù
+$| = 1;
+
+#   stdin¿¡¼­ ÇÑÁÙ¾¿ URLÀ» Àаí
+#   stdout¿¡ º¯È¯ÇÑ URLÀ» Ãâ·ÂÇÑ´Ù
+while (<>) {
+    s|^foo/|bar/|;
+    print $_;
+}
+
+ +

¼³¸íÇϱâÀ§ÇØ ¸ðµç /~quux/foo/... URLÀ» + /~quux/bar/...·Î ÀçÀÛ¼ºÇÏ´Â ½ºÅ©¸³Æ®¸¦ + ¿¹·Î µé¾ú´Ù. ½ÇÁ¦·Î ¸¶À½´ë·Î ÇÁ·Î±×·¡¹ÖÇÒ ¼ö ÀÖ´Ù. + ±×·¯³ª ÀÏ¹Ý »ç¿ëÀÚ°¡ ÀÌ·± ¸ÊÀ» »ç¿ëÇÒ + ¼ö ÀÖ´Ù°í ÇÏ´õ¶ó°í, ¿ÀÁ÷ ½Ã½ºÅÛ °ü¸®ÀÚ¸¸ÀÌ ¸ÊÀ» + Á¤ÀÇÇØ¾ß ÇÔÀ» ÁÖÀÇÇ϶ó.

+
+
+ + + +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/misc/security_tips.html b/docs/manual/misc/security_tips.html new file mode 100644 index 00000000..3746e186 --- /dev/null +++ b/docs/manual/misc/security_tips.html @@ -0,0 +1,7 @@ +URI: security_tips.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: security_tips.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/misc/security_tips.html.en b/docs/manual/misc/security_tips.html.en new file mode 100644 index 00000000..911a622b --- /dev/null +++ b/docs/manual/misc/security_tips.html.en @@ -0,0 +1,350 @@ + + + +Security Tips - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Miscellaneous Documentation

Security Tips

+
+

Available Languages:  en  | + ko 

+
+ +

Some hints and tips on security issues in setting up a web server. + Some of the suggestions will be general, others specific to Apache.

+
+ +
top
+
+

Keep up to Date

+ +

The Apache HTTP Server has a good record for security and a + developer community highly concerned about security issues. But + it is inevitable that some problems -- small or large -- will be + discovered in software after it is released. For this reason, it + is crucial to keep aware of updates to the software. If you have + obtained your version of the HTTP Server directly from Apache, we + highly recommend you subscribe to the Apache + HTTP Server Announcements List where you can keep informed of + new releases and security updates. Similar services are available + from most third-party distributors of Apache software.

+ +

Of course, most times that a web server is compromised, it is + not because of problems in the HTTP Server code. Rather, it comes + from problems in add-on code, CGI scripts, or the underlying + Operating System. You must therefore stay aware of problems and + updates with all the software on your system.

+ +
top
+
+

Permissions on ServerRoot Directories

+ + + +

In typical operation, Apache is started by the root user, and it + switches to the user defined by the User directive to serve hits. As is the + case with any command that root executes, you must take care that it is + protected from modification by non-root users. Not only must the files + themselves be writeable only by root, but so must the directories, and + parents of all directories. For example, if you choose to place + ServerRoot in /usr/local/apache then it is suggested that you create + that directory as root, with commands like these:

+ +

+ mkdir /usr/local/apache
+ cd /usr/local/apache
+ mkdir bin conf logs
+ chown 0 . bin conf logs
+ chgrp 0 . bin conf logs
+ chmod 755 . bin conf logs +

+ +

It is assumed that /, /usr, and /usr/local are only modifiable by + root. When you install the httpd executable, you + should ensure that it is similarly protected:

+ +

+ cp httpd /usr/local/apache/bin
+ chown 0 /usr/local/apache/bin/httpd
+ chgrp 0 /usr/local/apache/bin/httpd
+ chmod 511 /usr/local/apache/bin/httpd +

+ +

You can create an htdocs subdirectory which is modifiable by other + users -- since root never executes any files out of there, and shouldn't + be creating files in there.

+ +

If you allow non-root users to modify any files that root either + executes or writes on then you open your system to root compromises. + For example, someone could replace the httpd binary so + that the next time you start it, it will execute some arbitrary code. If + the logs directory is writeable (by a non-root user), someone could replace + a log file with a symlink to some other system file, and then root + might overwrite that file with arbitrary data. If the log files + themselves are writeable (by a non-root user), then someone may be + able to overwrite the log itself with bogus data.

+ +
top
+
+

Server Side Includes

+ + + +

Server Side Includes (SSI) present a server administrator with + several potential security risks.

+ +

The first risk is the increased load on the server. All + SSI-enabled files have to be parsed by Apache, whether or not + there are any SSI directives included within the files. While this + load increase is minor, in a shared server environment it can become + significant.

+ +

SSI files also pose the same risks that are associated with CGI + scripts in general. Using the "exec cmd" element, SSI-enabled files + can execute any CGI script or program under the permissions of the + user and group Apache runs as, as configured in httpd.conf.

+ +

There are ways to enhance the security of SSI files while still + taking advantage of the benefits they provide.

+ +

To isolate the damage a wayward SSI file can cause, a server + administrator can enable suexec as + described in the CGI in General section

+ +

Enabling SSI for files with .html or .htm extensions can be + dangerous. This is especially true in a shared, or high traffic, + server environment. SSI-enabled files should have a separate extension, + such as the conventional .shtml. This helps keep server load at a + minimum and allows for easier management of risk.

+ +

Another solution is to disable the ability to run scripts and + programs from SSI pages. To do this replace Includes + with IncludesNOEXEC in the Options directive. Note that users may + still use <--#include virtual="..." --> to execute CGI scripts if + these scripts are in directories desginated by a ScriptAlias directive.

+ +
top
+
+

CGI in General

+ + + +

First of all, you always have to remember that you must trust the + writers of the CGI scripts/programs or your ability to spot potential + security holes in CGI, whether they were deliberate or accidental. CGI + scripts can run essentially arbitrary commands on your system with the + permissions of the web server user and can therefore be extremely + dangerous if they are not carefully checked.

+ +

All the CGI scripts will run as the same user, so they have potential + to conflict (accidentally or deliberately) with other scripts e.g. User + A hates User B, so he writes a script to trash User B's CGI database. One + program which can be used to allow scripts to run as different users is + suEXEC which is included with Apache as of + 1.2 and is called from special hooks in the Apache server code. Another + popular way of doing this is with + CGIWrap.

+ +
top
+
+

Non Script Aliased CGI

+ + + +

Allowing users to execute CGI scripts in any directory should only be + considered if:

+ +
    +
  • You trust your users not to write scripts which will deliberately + or accidentally expose your system to an attack.
    • +
  • You consider security at your site to be so feeble in other areas, + as to make one more potential hole irrelevant.
    • +
  • You have no users, and nobody ever visits your server.
    • +
+ +
top
+
+

Script Aliased CGI

+ + + +

Limiting CGI to special directories gives the admin control over what + goes into those directories. This is inevitably more secure than non + script aliased CGI, but only if users with write access to the + directories are trusted or the admin is willing to test each + new CGI script/program for potential security holes.

+ +

Most sites choose this option over the non script aliased CGI + approach.

+ +
top
+
+

Other sources of dynamic content

+ + + +

+ Embedded scripting options which run as part of the server itself, + such as mod_php, mod_perl, mod_tcl, and mod_python, run under the + identity of the server itself (see the User directive), and therefore + scripts executed by these engines potentially can access anything the + server user can. Some scripting engines may provide restrictions, but + it is better to be safe and assume not.

+ +
top
+
+

Protecting System Settings

+ + + +

To run a really tight ship, you'll want to stop users from setting + up .htaccess files which can override security features + you've configured. Here's one way to do it.

+ +

In the server configuration file, put

+ +

+ <Directory />
+ AllowOverride None
+ </Directory> +

+ +

This prevents the use of .htaccess files in all + directories apart from those specifically enabled.

+ +
top
+
+

Protect Server Files by Default

+ + + +

One aspect of Apache which is occasionally misunderstood is the + feature of default access. That is, unless you take steps to change it, + if the server can find its way to a file through normal URL mapping + rules, it can serve it to clients.

+ +

For instance, consider the following example:

+ +

+ # cd /; ln -s / public_html
+ Accessing http://localhost/~root/ +

+ +

This would allow clients to walk through the entire filesystem. To + work around this, add the following block to your server's + configuration:

+ +

+ <Directory />
+ Order Deny,Allow
+ Deny from all
+ </Directory> +

+ +

This will forbid default access to filesystem locations. Add + appropriate Directory blocks to + allow access only in those areas you wish. For example,

+ +

+ <Directory /usr/users/*/public_html>
+ Order Deny,Allow
+ Allow from all
+ </Directory>
+ <Directory /usr/local/httpd>
+ Order Deny,Allow
+ Allow from all
+ </Directory> +

+ +

Pay particular attention to the interactions of Location and Directory directives; for instance, even + if <Directory /> denies access, a + <Location /> directive might overturn it

+ +

Also be wary of playing games with the UserDir directive; setting it to + something like "./" would have the same effect, for root, as the first + example above. If you are using Apache 1.3 or above, we strongly + recommend that you include the following line in your server + configuration files:

+ +

+ UserDir disabled root +

+ +
top
+
+

Watching Your Logs

+ + + +

To keep up-to-date with what is actually going on against your server + you have to check the Log Files. Even though + the log files only reports what has already happened, they will give you + some understanding of what attacks is thrown against the server and + allows you to check if the necessary level of security is present.

+ +

A couple of examples:

+ +

+ grep -c "/jsp/source.jsp?/jsp/ /jsp/source.jsp??" access_log
+ grep "client denied" error_log | tail -n 10 +

+ +

The first example will list the number of attacks trying to exploit the + Apache Tomcat + Source.JSP Malformed Request Information Disclosure Vulnerability, + the second example will list the ten last denied clients, for example:

+ +

+ [Thu Jul 11 17:18:39 2002] [error] [client foo.bar.com] client denied + by server configuration: /usr/local/apache/htdocs/.htpasswd +

+ +

As you can see, the log files only report what already has happened, so + if the client had been able to access the .htpasswd file you + would have seen something similar to:

+ +

+ foo.bar.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" +

+ +

in your Access Log. This means + you probably commented out the following in your server configuration + file:

+ +

+ <Files ~ "^\.ht">
+ Order allow,deny
+ Deny from all
+ </Files> +

+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/misc/security_tips.html.ko.euc-kr b/docs/manual/misc/security_tips.html.ko.euc-kr new file mode 100644 index 00000000..36be0301 --- /dev/null +++ b/docs/manual/misc/security_tips.html.ko.euc-kr @@ -0,0 +1,343 @@ + + + +º¸¾È ÆÁ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Miscellaneous Documentation

º¸¾È ÆÁ

+
+

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

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

À¥¼­¹ö¸¦ ¿î¿µÇÒ¶§ µµ¿òÀÌ µÉ º¸¾È °ü·Ã ÈùÆ®¿Í ÆÁÀÌ´Ù. + ¾î¶² °ÍÀº ÀϹÝÀûÀÌ°í, ¾î¶² °ÍÀº ¾ÆÆÄÄ¡¿¡¸¸ ÇØ´çÇÏ´Â °ÍÀÌ´Ù.

+
+ +
top
+
+

ÃÖ½ÅÆÇÀ¸·Î À¯ÁöÇϱâ

+ +

¾ÆÆÄÄ¡ À¥¼­¹ö´Â ¾ÈÀü°ú º¸¾È ¹®Á¦¿¡ °ü½ÉÀÌ ¸¹Àº °³¹ßÀÚ + °øµ¿Ã¼·Î À¯¸íÇÏ´Ù. ±×·¯³ª Å©°Ç ÀÛ°Ç ¹ßÇ¥ÈÄ ¹ß°ßµÇ´Â ¹®Á¦µéÀ» + ÇÇÇÒ ¼ö ¾ø´Ù. ±×·¡¼­ ¼ÒÇÁÆ®¿þ¾î¸¦ ÃֽŹöÀüÀ¸·Î À¯ÁöÇÏ´Â + °ÍÀÌ Áß¿äÇÏ´Ù. ¾ÆÆÄÄ¡¿¡¼­ Á÷Á¢ À¥¼­¹ö¸¦ ´Ù¿î·ÎµåÇß´Ù¸é, + »õ·Î¿î ¹öÀü°ú º¸¾È ¾÷µ¥ÀÌÆ®¸¦ ¾Ë·ÁÁÖ´Â ¾ÆÆÄÄ¡ + À¥¼­¹ö ¹ßÇ¥ ¸ÞÀϸµ¸®½ºÆ®¸¦ ±¸µ¶ÇÏ±æ °­·ÂÈ÷ ±ÇÇÑ´Ù. + ¾ÆÆÄÄ¡ ¼ÒÇÁÆ®¿þ¾î¸¦ ¹èÆ÷ÇÏ´Â ¸¹Àº Á¦»ïÀڵ鵵 ºñ½ÁÇÑ ¼­ºñ½º¸¦ + Á¦°øÇÑ´Ù.

+ +

¹°·Ð À¥¼­¹ö Äڵ嶧¹®¿¡ À¥¼­¹ö°¡ °ø°ÝÀ» ´çÇÏ´Â °æ¿ì´Â + ¸¹Áö ¾Ê´Ù. ±×º¸´Ù Ãß°¡ ÄÚµå, CGI ½ºÅ©¸³Æ®, ÇÏÀ§ ¿î¿µÃ¼Á¦ÀÇ + ¹®Á¦·Î °ø°ÝÀ» ´çÇÏ´Â °æ¿ì°¡ ¸¹´Ù. ±×·¯¹Ç·Î Ç×»ó ÁÖÀÇÇϸç + ½Ã½ºÅÛÀÇ ¸ðµç ¼ÒÇÁÆ®¿þ¾î¸¦ ¾÷µ¥ÀÌÆ®ÇØ¾ß ÇÑ´Ù.

+ +
top
+
+

ServerRoot µð·ºÅ丮 ±ÇÇÑ

+ + + +

º¸Åë root »ç¿ëÀÚ°¡ ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇÑ ÈÄ, ¿äûÀ» ¼­ºñ½ºÇϱâÀ§ÇØ + User Áö½Ã¾î·Î + ÁöÁ¤ÇÑ »ç¿ëÀÚ·Î º¯È¯ÇÑ´Ù. root°¡ ½ÇÇàÇÏ´Â ¸í·É¾î°¡ ÀÖ´Ù¸é, + root ÀÌ¿ÜÀÇ »ç¿ëÀÚ°¡ ¼öÁ¤ÇÏÁö ¸øÇϵµ·Ï ÁÖÀÇÇØ¾ß ÇÑ´Ù. ÀÌ + ÆÄÀϵéÀ» root¸¸ ¾µ ¼ö ÀÖ¾î¾ß ÇÏ°í, µð·ºÅ丮¿Í ¸ðµç »óÀ§µð·ºÅ丮µµ + ¸¶Âù°¡Áö´Ù. ¿¹¸¦ µé¾î, ServerRoot·Î /usr/local/apache¸¦ + »ç¿ëÇÑ´Ù¸é root »ç¿ëÀÚ°¡ ´ÙÀ½°ú °°ÀÌ µð·ºÅ丮¸¦ ¸¸µé±æ + Á¦¾ÈÇÑ´Ù:

+ +

+ mkdir /usr/local/apache
+ cd /usr/local/apache
+ mkdir bin conf logs
+ chown 0 . bin conf logs
+ chgrp 0 . bin conf logs
+ chmod 755 . bin conf logs +

+ +

±×·¯¸é /, /usr, /usr/local Àº root¸¸ÀÌ ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù. + httpd ½ÇÇàÆÄÀÏÀ» ¼³Ä¡ÇÒ¶§ ´ÙÀ½°ú °°ÀÌ º¸È£ÇØ¾ß ÇÑ´Ù:

+ +

+ cp httpd /usr/local/apache/bin
+ chown 0 /usr/local/apache/bin/httpd
+ chgrp 0 /usr/local/apache/bin/httpd
+ chmod 511 /usr/local/apache/bin/httpd +

+ +

htdocs ÇÏÀ§µð·ºÅ丮´Â ´Ù¸¥ »ç¿ëÀÚµéÀÌ ¼öÁ¤ÇÒ ¼ö ÀÖµµ·Ï + ¸¸µé ¼ö ÀÖ´Ù -- root´Â ±×°÷¿¡ ÀÖ´Â ÆÄÀÏÀ» ½ÇÇàÇÏÁöµµ, ¸¸µéÁöµµ + ¾Ê¾Æ¾ß ÇÑ´Ù.

+ +

root°¡ ¾Æ´Ñ »ç¿ëÀÚ°¡ root°¡ ½ÇÇàÇϰųª ¾²±â°¡´ÉÇÑ ÆÄÀÏÀ» + ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù¸é ½Ã½ºÅÛÀÇ root ±ÇÇÑÀ» ÈÉÄ¥ ¼ö ÀÖ´Ù. ¿¹¸¦ + µé¾î, ´©±º°¡ httpd ½ÇÇàÆÄÀÏÀ» º¯°æÇÏ¿´´Ù¸é ´ÙÀ½¹ø ½ÃÀÛÇÒ¶§ + ÀÓÀÇÀÇ Äڵ带 ½ÇÇàÇÏ°Ô µÈ´Ù. logs µð·ºÅ丮°¡ (root°¡ ¾Æ´Ñ + »ç¿ëÀÚ¿¡°Ô) ¾²±â°¡´ÉÇÏ´Ù¸é ´©±º°¡ ·Î±×ÆÄÀÏÀ» ´Ù¸¥ ½Ã½ºÅÛÆÄÀÏ·Î + ½Éº¼¸µÅ©¸¦ °É¾î¼­ root°¡ ÆÄÀÏ¿¡ ÀÓÀÇÀÇ ÀڷḦ µ¤¾î¾µ ¼ö + ÀÖ´Ù. ·Î±×ÆÄÀÏÀÌ (root°¡ ¾Æ´Ñ »ç¿ëÀÚ¿¡°Ô) ¾²±â°¡´ÉÇÏ´Ù¸é + ´©±º°¡ ·Î±×¿¡ ÀÌ»óÇÑ ÀڷḦ ±â·ÏÇÒ ¼ö ÀÖ´Ù.

+ +
top
+
+

Server Side Includes

+ + + +

Server Side Includes (SSI)´Â ¼­¹ö °ü¸®ÀÚ¿¡°Ô º¸¾È»ó ¸î°¡Áö + ÀáÀçÀûÀÎ À§ÇèÀÌ´Ù.

+ +

ù¹ø° À§ÇèÀº ¼­¹öÀÇ ºÎÇϸ¦ ´Ã¸®´Â Á¡ÀÌ´Ù. ¾ÆÆÄÄ¡´Â ÆÄÀÏ¿¡ + SSI Áö½Ã¾î°¡ ÀÖ´ÂÁö ¿©ºÎ¿Í °ü°è¾øÀÌ ¸ðµç SSI ÆÄÀÏÀ» ºÐ¼®ÇØ¾ß + ÇÑ´Ù. Á¶±Ý ºÎÇÏ°¡ ´ÃÁö¸¸, ¼­¹ö¸¦ ¿©·¯ »ç¶÷ÀÌ °°ÀÌ »ç¿ëÇÏ´Â + ȯ°æ¿¡¼­´Â ½É°¢ÇÒ ¼ö ÀÖ´Ù.

+ +

¶Ç, SSI ÆÄÀÏÀº ÀϹÝÀûÀÎ CGI ½ºÅ©¸³Æ®¿Í µ¿ÀÏÇÑ À§ÇèÀ» + °¡Áø´Ù. SSI ÆÄÀÏ¿¡¼­ "exec cmd"¸¦ »ç¿ëÇϸé httpd.conf¿¡¼­ + ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇϵµ·Ï ¼³Á¤ÇÑ »ç¿ëÀÚ¿Í ±×·ì ±ÇÇÑÀ¸·Î CGI + ½ºÅ©¸³Æ®³ª ÇÁ·Î±×·¥À» ½ÇÇàÇÒ ¼ö ÀÖ´Ù.

+ +

ÀåÁ¡À» È°¿ëÇϸ鼭 SSI ÆÄÀÏÀÇ º¸¾ÈÀ» Çâ»ó½ÃÅ°´Â ¹æ¹ýÀÌ + ÀÖ´Ù.

+ +

SSI ÆÄÀÏÀÌ °¡Á®¿Ã ¼ö ÀÖ´Â ÇÇÇظ¦ °Ý¸®ÇϱâÀ§ÇØ ¼­¹ö°ü¸®ÀÚ´Â + ÀϹÝÀûÀÎ CGI Àý¿¡¼­ ¼³¸íÇÏ´Â ¹æ¹ýÀ¸·Î + suexec¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù

+ +

.htmlÀ̳ª .htm È®ÀåÀÚ¸¦ SSI ÆÄÀÏ·Î »ç¿ëÇÏ´Â °ÍÀº À§ÇèÇÏ´Ù. + ƯÈ÷ ¿©·¯ »ç¶÷ÀÌ °øÀ¯Çϰųª Åë½Å·®ÀÌ ¸¹Àº ¼­¹ö ȯ°æ¿¡¼­ + À§ÇèÇÏ´Ù. SSI ÆÄÀÏÀº ÀϹÝÀûÀ¸·Î ¸¹ÀÌ »ç¿ëÇÏ´Â .shtml °°Àº + º°µµÀÇ È®ÀåÀÚ¸¦ °¡Á®¾ß ÇÑ´Ù. ±×·¯¸é ¼­¹ö ºÎÇϸ¦ ÃÖ¼ÒÈ­ÇÏ°í + À§Çè¿ä¼Ò¸¦ ½±°Ô °ü¸®ÇÒ ¼ö ÀÖ´Ù.

+ +

´Ù¸¥ ¹æ¹ýÀº SSI ÆäÀÌÁö°¡ ½ºÅ©¸³Æ®³ª ÇÁ·Î±×·¥À» ½ÇÇàÇÏÁö + ¸øÇϵµ·Ï ¸¸µå´Â °ÍÀÌ´Ù. Options Áö½Ã¾î¿¡¼­ Includes + ´ë½Å IncludesNOEXEC¸¦ »ç¿ëÇÑ´Ù. ±×·¡µµ ½ºÅ©¸³Æ®°¡ + ScriptAlias Áö½Ã¾î·Î + ÁöÁ¤ÇÑ µð·ºÅ丮¿¡ ÀÖ´Ù¸é <--#include virtual="..." -->¸¦ + »ç¿ëÇÏ¿© CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÒ ¼ö ÀÖÀ½À» ÁÖÀÇÇ϶ó.

+ +
top
+
+

ÀϹÝÀûÀÎ CGI

+ + + +

°á±¹ ´ç½ÅÀº Ç×»ó CGI ½ºÅ©¸³Æ®/ÇÁ·Î±×·¥ÀÇ ÀúÀÚ¸¦ ½Å·ÚÇØ¾ß + ÇÏ°í, °íÀÇ°Ç ½Ç¼öÀÌ°Ç CGIÀÇ ÀáÀçÀûÀÎ º¸¾È»ó ÇãÁ¡À» ¹ß°ßÇÒ + ¼ö ÀÖ¾î¾ß ÇÑ´Ù. ±âº»ÀûÀ¸·Î CGI ½ºÅ©¸³Æ®´Â À¥¼­¹ö »ç¿ëÀÚ + ±ÇÇÑÀ¸·Î ½Ã½ºÅÛ¿¡¼­ ¾î¶² ¸í·É¾î¶óµµ ½ÇÇàÇÒ ¼ö Àֱ⶧¹®¿¡ + ÁÖÀÇÀÖ°Ô È®ÀÎÇÏÁö ¾ÊÀ¸¸é ¸Å¿ì À§ÇèÇÏ´Ù.

+ +

¸ðµç CGI ½ºÅ©¸³Æ®°¡ °°Àº »ç¿ëÀÚ·Î ½ÇÇàµÇ±â¶§¹®¿¡ ´Ù¸¥ + ½ºÅ©¸³Æ®¿Í (°íÀÇ°Ç ½Ç¼öÀÌ°Ç) Ãæµ¹ÇÒ °¡´É¼ºÀÌ ÀÖ´Ù. ¿¹¸¦ + µé¾î, »ç¿ëÀÚ A´Â »ç¿ëÀÚ B¸¦ ¸Å¿ì ½È¾îÇÏ¿©, »ç¿ëÀÚ BÀÇ CGI + µ¥ÀÌÅͺ£À̽º¸¦ Áö¿ö¹ö¸®´Â ½ºÅ©¸³Æ®¸¦ ÀÛ¼ºÇÒ ¼ö ÀÖ´Ù. ¾ÆÆÄÄ¡ + 1.2 ¹öÀüºÎÅÍ Æ÷ÇԵǾú°í ¾ÆÆÄÄ¡ ¼­¹ö¿¡¼­ Ưº°ÇÑ ÈÅ(hook)À¸·Î + µ¿ÀÛÇÏ´Â suEXEC´Â ½ºÅ©¸³Æ®¸¦ + ´Ù¸¥ »ç¿ëÀÚ·Î ½ÇÇàÇÏ´Â ¹æ¹ýÁß Çϳª´Ù. ´Ù¸¥ ´ëÁßÀûÀÎ ¹æ¹ý¿¡´Â + CGIWrapÀÌ ÀÖ´Ù.

+ +
top
+
+

ScriptAliasÇÏÁö ¾ÊÀº CGI

+ + + +

´ÙÀ½ Á¶°ÇÀ» ¸¸Á·ÇÒ¶§¸¸ »ç¿ëÀÚ°¡ ¾î¶² µð·ºÅ丮¿¡¼­¶óµµ + CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇϵµ·Ï Çã¿ëÇÒ ¼ö ÀÖ´Ù:

+ +
    +
  • ´ç½ÅÀº °íÀÇ°Ç ½Ç¼öÀÌ°Ç »ç¿ëÀÚ°¡ ½Ã½ºÅÛÀ» °ø°Ý¿¡ ³ëÃâ½ÃÅ°´Â + ½ºÅ©¸³Æ®¸¦ ÀÛ¼ºÇÏÁö ¾Ê´Â´Ù°í ¹Ï´Â´Ù.
    • +
  • ½Ã½ºÅÛÀÇ ´Ù¸¥ ºÎºÐÀÇ º¸¾ÈÀÌ ¾àÇؼ­, ÀáÀçÀûÀÎ ÇãÁ¡À» + Çϳª ´õ ¸¸µé¾îµµ ³ªºüÁú °ÍÀÌ ¾ø´Ù°í »ý°¢ÇÏ´Â °æ¿ì.
    • +
  • »ç¿ëÀÚ°¡ ¾ø°í, ¾Æ¸¶ ¾Æ¹«µµ ¼­¹ö¸¦ ¹æ¹®ÇÏÁö¾Ê´Â °æ¿ì.
    • +
+ +
top
+
+

ScriptAliasÇÑ CGI

+ + + +

ƯÁ¤ µð·ºÅ丮¿¡¼­¸¸ CGI¸¦ ½ÇÇàÇÒ ¼ö ÀÖµµ·Ï Á¦ÇÑÇÏ¸é °ü¸®ÀÚ´Â + ÀÌµé µð·ºÅ丮¸¦ ÅëÁ¦ÇÒ ¼ö ÀÖ´Ù. ÀÌ °æ¿ì´Â scriptaliasÇÏÁö + ¾ÊÀº CGIº¸´Ù È®½ÇÈ÷ ¾ÈÀüÇÏ´Ù. ´Ü, ½Å·ÚÇÏ´Â »ç¿ëÀÚ¸¸ µð·ºÅ丮¿¡ + Á¢±ÙÇÒ ¼ö ÀÖ°í, °ü¸®ÀÚ°¡ »õ·Î¿î CGI ½ºÅ©¸³Æ®/ÇÁ·Î±×·¥ÀÇ + ÀáÀçÀûÀÎ º¸¾È»ó ÇãÁ¡À» °Ë»çÇÒ ¿ëÀÌ°¡ ÀÖ´Ù¸é.

+ +

´ëºÎºÐÀÇ »çÀÌÆ®´Â scriptaliasÇÏÁö ¾ÊÀº CGI ¹æ½Ä ´ë½Å + ÀÌ ¹æ½ÄÀ» »ç¿ëÇÑ´Ù.

+ +
top
+
+

µ¿Àû ³»¿ëÀ» »ý¼ºÇÏ´Â ´Ù¸¥ ¹æ¹ý

+ + + +

+ mod_php, mod_perl, mod_tcl, mod_python °°ÀÌ ¼­¹öÀÇ ÀϺηΠ+ µ¿ÀÛÇÏ´Â ÀÓº£µðµå ½ºÅ©¸³Æ®´Â ¼­¹ö¿Í °°Àº »ç¿ëÀÚ·Î (User Áö½Ã¾î Âü°í) ½ÇÇàµÇ±â¶§¹®¿¡, + ½ºÅ©¸³Æ® ¿£ÁøÀÌ ½ÇÇàÇÏ´Â ½ºÅ©¸³Æ®´Â ÀáÀçÀûÀ¸·Î ¼­¹ö »ç¿ëÀÚ°¡ + Á¢±ÙÇÒ ¼ö ÀÖ´Â ¸ðµç °Í¿¡ Á¢±ÙÇÒ ¼ö ÀÖ´Ù. ¾î¶² ½ºÅ©¸³Æ® ¿£ÁøÀº + ¾î´ÀÁ¤µµ Á¦ÇÑÀ» ÇÏÁö¸¸, ¾ÈÀüÇÏ´Ù°í °¡Á¤ÇÏÁö ¾Ê´Â °ÍÀÌ ÁÁ´Ù.

+ +
top
+
+

½Ã½ºÅÛ ¼³Á¤ º¸È£Çϱâ

+ + + +

Á¤¸»·Î ¾ÈÀüÇÑ ¼­¹ö¸¦ ¿î¿µÇÏ·Á¸é »ç¿ëÀÚ°¡ + .htaccess ÆÄÀÏÀ» »ç¿ëÇÏ¿© ´ç½ÅÀÌ ¼³Á¤ÇÑ º¸¾È±â´ÉÀ» + º¯°æÇÏ±æ ¹Ù¶óÁö ¾ÊÀ» °ÍÀÌ´Ù. ±×·¯±âÀ§ÇØ ´ÙÀ½°ú °°Àº ¹æ¹ýÀÌ + ÀÖ´Ù.

+ +

¼­¹ö ¼³Á¤ÆÄÀÏ¿¡ ´ÙÀ½À» Ãß°¡ÇÑ´Ù

+ +

+ <Directory />
+ AllowOverride None
+ </Directory> +

+ +

±×·¯¸é »ç¿ë°¡´ÉÇϵµ·Ï ¸í½ÃÀûÀ¸·Î Çã¿ëÇÑ µð·ºÅ丮¸¦ Á¦¿ÜÇÏ°í´Â + .htaccess ÆÄÀÏÀ» »ç¿ëÇÒ ¼ö ¾ø´Ù.

+ +
top
+
+

±âº»ÀûÀ¸·Î ¼­¹ö¿¡ ÀÖ´Â ÆÄÀÏ º¸È£Çϱâ

+ + + +

»ç¶÷µéÀº Á¾Á¾ ¾ÆÆÄÄ¡ÀÇ ±âº» Á¢±Ù¿¡ ´ëÇØ À߸ø ¾Ë°íÀÖ´Ù. + Áï, ¼­¹ö°¡ ÀϹÝÀûÀÎ URL ´ëÀÀ ±ÔÄ¢À» »ç¿ëÇÏ¿© ÆÄÀÏÀ» ãÀ» + ¼ö ÀÖ´Ù¸é, Ưº°È÷ Á¶Ä¡¸¦ ÇÏÁö ¾Ê´ÂÇÑ Å¬¶óÀ̾ðÆ®¿¡°Ô ÆÄÀÏÀÌ + ¼­ºñ½ºµÉ ¼ö ÀÖ´Ù.

+ +

¿¹¸¦ µé¾î, ¾Æ·¡¿Í °°Àº °æ¿ì:

+ +

+ # cd /; ln -s / public_html
+ http://localhost/~root/ ¿¡ Á¢±ÙÇÑ´Ù +

+ +

±×·¯¸é Ŭ¶óÀ̾ðÆ®´Â Àüü ÆÄÀϽýºÅÛÀ» µ¹¾Æ´Ù´Ò ¼ö ÀÖ´Ù. + À̸¦ ¸·±âÀ§ÇØ ¼­¹ö¼³Á¤¿¡¼­ ´ÙÀ½°ú °°Àº Á¶Ä¡¸¦ ÇÑ´Ù:

+ +

+ <Directory />
+ Order Deny,Allow
+ Deny from all
+ </Directory> +

+ +

±×·¯¸é ÆÄÀϽýºÅÛ À§Ä¡¿¡ ´ëÇØ ±âº» Á¢±ÙÀÌ °ÅºÎµÈ´Ù. + ¿øÇÏ´Â ¿µ¿ª¿¡ Á¢±ÙÇÒ ¼ö ÀÖµµ·Ï ´ÙÀ½°ú °°Àº Directory ºí·ÏÀ» Ãß°¡ÇÑ´Ù.

+ +

+ <Directory /usr/users/*/public_html>
+ Order Deny,Allow
+ Allow from all
+ </Directory>
+ <Directory /usr/local/httpd>
+ Order Deny,Allow
+ Allow from all
+ </Directory> +

+ +

Location°ú Directory Áö½Ã¾î¸¦ °°ÀÌ »ç¿ëÇÏ´Â + °æ¿ì Ưº°È÷ ÁÖÀǸ¦ ±â¿ï¿©¶ó. ¿¹¸¦ µé¾î, <Directory + />°¡ Á¢±ÙÀ» °ÅºÎÇÏ´õ¶óµµ <Location + /> Áö½Ã¾î°¡ À̸¦ ¹«½ÃÇÒ ¼ö ÀÖ´Ù

+ +

UserDir Áö½Ã¾î¸¦ + »ç¿ëÇÏ´Â °æ¿ì¿¡µµ ÁÖÀÇÇ϶ó. Áö½Ã¾î¸¦ "./" °°ÀÌ ¼³Á¤Çϸé + root »ç¿ëÀÚ¿¡ ´ëÇØ ¹Ù·Î À§ÀÇ °æ¿ì¿Í °°Àº ¹®Á¦°¡ ¹ß»ýÇÑ´Ù. + ¾ÆÆÄÄ¡ 1.3 ÀÌ»óÀ» »ç¿ëÇÑ´Ù¸é ¼­¹ö ¼³Á¤ÆÄÀÏ¿¡ ¾Æ·¡ ÁÙÀ» Ãß°¡Çϱæ + °­·ÂÈ÷ ±ÇÇÑ´Ù:

+ +

+ UserDir disabled root +

+ +
top
+
+

·Î±× »ìÆ캸±â

+ + + +

½ÇÁ¦·Î ¼­¹ö¿¡¼­ ¹«½¼ ÀÏÀÌ À־°í ÀÖ´ÂÁö ¾Ë·Á¸é ·Î±×ÆÄÀÏÀ» »ìÆìºÁ¾ß ÇÑ´Ù. ·Î±×ÆÄÀÏÀº + ÀÌ¹Ì ÀϾ Àϸ¸À» º¸°íÇÏÁö¸¸, ¼­¹ö¿¡ ¾î¶² °ø°ÝÀÌ ÀÖ¾ú´ÂÁö + ¾Ë·ÁÁÖ°í ÇöÀç ÇÊ¿äÇÑ ¸¸Å­ ¾ÈÀüÇÑÁö È®ÀÎÇÏ°Ô ÇØÁØ´Ù.

+ +

¿©·¯°¡Áö ¿¹:

+ +

+ grep -c "/jsp/source.jsp?/jsp/ /jsp/source.jsp??" access_log
+ grep "client denied" error_log | tail -n 10 +

+ +

ù¹ø° ¿¹´Â À߸øµÈ + Source.JSP ¿äûÀ¸·Î ¼­¹öÁ¤º¸¸¦ ¾Ë¾Æ³¾ ¼ö ÀÖ´Â TomcatÀÇ + Ãë¾àÁ¡¸¦ ÀÌ¿ëÇÏ·Á´Â °ø°Ý Ƚ¼ö¸¦ ¾Ë·ÁÁÖ°í, µÎ¹ø° ¿¹´Â + Á¢±ÙÀÌ °ÅºÎµÈ Ãֱ٠Ŭ¶óÀ̾ðÆ® 10°³¸¦ ´ÙÀ½°ú °°ÀÌ º¸¿©ÁØ´Ù:

+ +

+ [Thu Jul 11 17:18:39 2002] [error] [client foo.bar.com] client denied + by server configuration: /usr/local/apache/htdocs/.htpasswd +

+ +

Àß ¾Ë µíÀÌ ·Î±×ÆÄÀÏÀº ÀÌ¹Ì ¹ß»ýÇÑ »ç°Ç¸¸À» º¸°íÇÑ´Ù. + ±×·¡¼­ Ŭ¶óÀ̾ðÆ®°¡ .htpasswd ÆÄÀÏ¿¡ Á¢±ÙÇÒ + ¼ö ÀÖ¾ú´Ù¸é Á¢±Ù ·Î±×¿¡ + ´ÙÀ½°ú °°Àº ±â·ÏÀÌ ³²À» °ÍÀÌ´Ù:

+ +

+ foo.bar.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1" +

+ +

Áï, ´ç½ÅÀº ¼­¹ö ¼³Á¤ÆÄÀÏ¿¡¼­ ´ÙÀ½ ºÎºÐÀ» ÁÖ¼®Ã³¸®ÇßÀ» + °ÍÀÌ´Ù:

+ +

+ <Files ~ "^\.ht">
+ Order allow,deny
+ Deny from all
+ <Files> +

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/beos.html b/docs/manual/mod/beos.html new file mode 100644 index 00000000..3d72b3f9 --- /dev/null +++ b/docs/manual/mod/beos.html @@ -0,0 +1,15 @@ +URI: beos.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: beos.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: beos.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: beos.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/beos.html.de b/docs/manual/mod/beos.html.de new file mode 100644 index 00000000..f7467a8f --- /dev/null +++ b/docs/manual/mod/beos.html.de @@ -0,0 +1,109 @@ + + + +beos - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module
+
+

Apache-MPM beos

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ko 

+
+ + + +
Beschreibung:Dieses Multi-Processing-Modul ist für BeOS + optimiert.
Status:MPM
Modulbezeichner:mpm_beos_module
Quelltext-Datei:beos.c
+

Zusammenfassung

+ +

Dieses Multi-Processing-Modul (MPM) ist das Standardmodul für BeOS. + Es benutzt einen einzelnen Steuerprozess welcher Threads für die + Bedienung der Anfragen erzeugt.

+
+ + +
top
+

MaxRequestsPerThread-Direktive

+ + + + + + + +
Beschreibung:Die maximale Anzahl von Anfragen, die ein einzelner Thread + während seiner Lebensdauer bedient.
Syntax:MaxRequestsPerThread Anzahl
Voreinstellung:MaxRequestsPerThread 0
Kontext:Serverkonfiguration
Status:MPM
Modul:beos
+

Die Direktive MaxRequestsPerThread legt die + Anzahl der Anfragen fest, die ein einzelner Server-Thread bedient. Nach + Erreichen der angegebenen Anzahl von Anfragen wird der Thread beendet. + Wird für MaxRequestsPerThread der Wert + 0 angegeben, wird der Thread niemals beendet.

+ +

Das Setzen von MaxRequestsPerThread auf einen + Wert ungleich null hat zwei Vorteile:

+ +
    +
  • Die Menge des von einem Thread benötigten Speicherplatzes + bei (unvorhergesehenen) Speicherproblemen kann begrenzt werden;
    • + +
  • Threads mit begrenzter Lebensdauer reduzieren die Anzahl + der Threads bei reduzierter Serverlast.
    • +
+ +

Hinweis:

+

Bei KeepAlive-Anfragen wird nur die + erste Anfrage auf das Maximum angerechnet. Das führt dazu, dass + die Anzahl der Verbindungen + pro Thread reduziert wird.

+
+ +
+
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/beos.html.en b/docs/manual/mod/beos.html.en new file mode 100644 index 00000000..b7c62ffd --- /dev/null +++ b/docs/manual/mod/beos.html.en @@ -0,0 +1,107 @@ + + + +beos - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache MPM beos

+
+

Available Languages:  de  | + en  | + es  | + ko 

+
+ + + +
Description:This Multi-Processing Module is optimized for BeOS.
Status:MPM
Module Identifier:mpm_beos_module
Source File:beos.c
+

Summary

+ +

This Multi-Processing Module (MPM) is the default for BeOS. It uses + a single control process which creates threads to handle requests.

+
+ + +
top
+

MaxRequestsPerThread Directive

+ + + + + + + +
Description:Limit on the number of requests that an individual thread +will handle during its life
Syntax:MaxRequestsPerThread number
Default:MaxRequestsPerThread 0
Context:server config
Status:MPM
Module:beos
+

The MaxRequestsPerThread directive sets + the limit on the number of requests that an individual server thread + will handle. After MaxRequestsPerThread + requests, the thread will die. If MaxRequestsPerThread is 0, then the thread + will never expire.

+ +

Setting MaxRequestsPerThread to a + non-zero limit has two beneficial effects:

+ +
    +
  • it limits the amount of memory that a thread can consume + by (accidental) memory leakage;
    • + +
  • by giving threads a finite lifetime, it helps reduce + the number of threads when the server load reduces.
    • +
+ +

Note:

+

For KeepAlive requests, only + the first request is counted towards this limit. In effect, it + changes the behavior to limit the number of connections + per thread.

+
+ +
+
+
+

Available Languages:  de  | + en  | + es  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/beos.html.es b/docs/manual/mod/beos.html.es new file mode 100644 index 00000000..9284dc4e --- /dev/null +++ b/docs/manual/mod/beos.html.es @@ -0,0 +1,115 @@ + + + +beos - Servidor HTTP Apache + + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2 > Módulos
+
+

MPM de Apache beos

+
+

Idiomas disponibles:  de  | + en  | + es  | + ko 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ + + +
Descripción:Este módulo de muiltiprocesamiento está +optimizado para BeOS.
Estado:MPM
Identificador de Módulos:mpm_beos_module
Fichero de Código Fuente:beos.c
+

Resumen de contenidos

+ +

Este módulo de muiltiprocesamiento (MMP) + es el que usa por defecto para BeOS. Usa un + único proceso de control que crea hebras para atender las + peticiones.

+
+ + +
top
+

MaxRequestsPerThread Directiva

+ + + + + + + +
Descripción:Limita el número de peticiones que una hebra (thread) puede +atender durante su vida
Sintaxis:MaxRequestsPerThread number
Valor por defecto:MaxRequestsPerThread 0
Contexto:server config
Estado:MPM
Módulo:beos
+

La directiva MaxRequestsPerThread fija + el número máximo de peticiones que una hebra del + servidor puede atender durante su vida. Despues de atender + MaxRequestsPerThread peticiones, la hebra + termina. Si el límite fijado en MaxRequestsPerThread es 0, entonces la + hebra puede atender peticiones indefinidamente.

+ +

Fijar la directiva MaxRequestsPerThread + a un límite distinto de cero ofrece dos benefcios + fundamentales:

+ +
    +
  • limita la cantidad de memoria que puede consumir una hebra + si hay una filtración (accidental) de memoria;
    • + +
  • poniendo un límite a la vida de las hebras, se ayuda a + reducir el número de hebras cuando se reduce la carga de + trabajo en el servidor.
    • +
+ +

Nota:

Para peticiones KeepAlive, solo la primera + petición se tiene en cuenta para este límite. De hecho, en este + caso el límite se impone sobre el número máximo + de conexiones por hebra.

+
+ +
+
+
+

Idiomas disponibles:  de  | + en  | + es  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/beos.html.ko.euc-kr b/docs/manual/mod/beos.html.ko.euc-kr new file mode 100644 index 00000000..41e56c1a --- /dev/null +++ b/docs/manual/mod/beos.html.ko.euc-kr @@ -0,0 +1,105 @@ + + + +beos - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ MPM beos

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:BeOS¿¡ ÃÖÀûÈ­µÈ ´ÙÁßó¸® ¸ðµâ.
»óÅÂ:MPM
¸ðµâ¸í:mpm_beos_module
¼Ò½ºÆÄÀÏ:beos.c
+

¿ä¾à

+ +

ÀÌ ´ÙÁßó¸® ¸ðµâ(MPM)Àº BeOS¿¡¼­ ±âº»ÀûÀ¸·Î »ç¿ëÇÑ´Ù. + ÇÑ Á¶Àý ÇÁ·Î¼¼½º°¡ ¿äûÀ» ó¸®ÇÒ ¾²·¹µåµéÀ» ¸¸µç´Ù.

+
+ + +
top
+

MaxRequestsPerThread Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÇÑ ¾²·¹µå°¡ ½ÇÇàÇÏ´Â µ¿¾È ó¸®ÇÒ ¿äû°³¼ö ÇÑ°è
¹®¹ý:MaxRequestsPerThread number
±âº»°ª:MaxRequestsPerThread 0
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:MPM
¸ðµâ:beos
+

MaxRequestsPerThread Áö½Ã¾î´Â + ÇÑ ¼­¹ö ¾²·¹µå°¡ ó¸®ÇÒ ¿äû°³¼ö¸¦ Á¦ÇÑÇÑ´Ù. + MaxRequestsPerThread°³ ¿äûÀ» ó¸®ÇÑÈÄ + ¾²·¹µå´Â Á״´Ù. MaxRequestsPerThread°¡ + 0À̸é Àý´ë·Î ¾²·¹µå¸¦ Á×ÀÌÁö ¾Ê´Â´Ù.

+ +

MaxRequestsPerThread¸¦ 0ÀÌ ¾Æ´Ñ + °ªÀ¸·Î ¼³Á¤ÇÏ¸é µÎ°¡Áö ÀåÁ¡ÀÌ ÀÖ´Ù:

+ +
    +
  • (¿ì¿¬È÷ ¹ß»ýÇÑ) ¸Þ¸ð¸® À¯Ãâ(memory leakage)¶§¹®¿¡ + ¾²·¹µå°¡ ³¶ºñÇÒ ¸Þ¸ð¸®·®À» Á¦ÇÑÇÑ´Ù;
    • + +
  • ¾²·¹µåÀÇ ¼ö¸íÀ» Á¦ÇÑÇÏ¿© ¼­¹ö ºÎÇÏ°¡ °¨¼ÒÇÒ¶§ + ¾²·¹µå ¼ö¸¦ ÁÙÀδÙ.
    • +
+ +

ÁÖÀÇ:

+

KeepAlive ¿äûÀÇ + °æ¿ì ¿ÀÁ÷ ù¹ø° ¿äû¸¸À» ¼¾´Ù. ±×·¡¼­ ÀÌ Áö½Ã¾î´Â ¾²·¹µå´ç + ¿¬°á °³¼ö¸¦ Á¦ÇÑÇÏ°Ô µÈ´Ù.

+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html new file mode 100644 index 00000000..424afeda --- /dev/null +++ b/docs/manual/mod/core.html @@ -0,0 +1,11 @@ +URI: core.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: core.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: core.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/core.html.de b/docs/manual/mod/core.html.de new file mode 100644 index 00000000..9ab26ed5 --- /dev/null +++ b/docs/manual/mod/core.html.de @@ -0,0 +1,3357 @@ + + + +core - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module
+
+

Apache-Kernfunktionen

+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+
Diese Übersetzung ist möglicherweise + nicht mehr aktuell. Bitte prüfen Sie die englische Version auf + die neuesten Änderungen.
+ +
Beschreibung:Ständig verfügbare Kernfunktionen des Apache HTTP +Servers
Status:Core
+
+ + +
top
+

AcceptPathInfo-Direktive

+ + + + + + + + + +
Beschreibung:Ressourcen lassen angehängte Pfadangaben zu
Syntax:AcceptPathInfo On|Off|Default
Voreinstellung:AcceptPathInfo Default
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
Kompatibilität:Verfügbar ab Apache 2.0.30
+

Die Direktive steuert, ob Anfragen akzeptiert oder + abgewiesen werden, bei denen nach der tatsächlichen + Datei (oder einer nicht existierenden Datei in einem existierenden + Verzeichnis) zusätzliche Pfadangaben folgen. Die angehängte + Pfadangabe kann Skripten in der Umgebungsvariable PATH_INFO + verfügbar gemacht werden.

+ +

Nehmen wir beispielsweise an, dass /test/ auf ein + Verzeichnis zeigt, welches lediglich eine Datei here.html + enthält. Dann wird bei Anfragen nach + /test/here.html/more und + /test/nothere.html/more beides Mal /more + als PATH_INFO ermittelt.

+ +

Die drei möglichen Argumente für die Direktive + AcceptPathInfo sind:

+ +
+
Off
Eine Anfrage wird nur dann akzeptiert, + wenn sie exakt auf ein existierendes Verzeichnis (oder eine Datei) + abgebildet werden kann. Daher würde eine Anfrage mit einer nach dem + tatsächlichen Dateinamen angehängten Pfadangabe, wie + /test/here.html/more im obigen Beispiel, den Fehler + 404 NOT FOUND (Anm.d.Ü.: nicht gefunden) + zurückgeben.
+ +
On
+
Eine Anfrage wird akzeptiert, wenn eine vorangestellte Pfadangabe + auf ein existierendes Verzeichnis abgebildet werden kann. Das + obige Beispiel /test/here.html/more wird akzeptiert, + wenn /test/here.html auf eine gültige Datei + zeigt.
+ +
Default
+
Die Behandlung von Anfragen mit angehängten Pfadangaben + wird von dem für die Anfrage verantwortlichen Handler bestimmt. Der Core-Handler + für gewöhnliche Dateien weist PATH_INFO-Zugriffe + standardmäßig zurück. Handler, die Skripte bedienen, + wie z.B. cgi-script und + isapi-handler, sind im Allgemeinen darauf + voreingestellt, PATH_INFO zu akzeptieren.
+
+ +

Das eigentliche Ziel von AcceptPathInfo ist es, Ihnen + das Überschreiben der Voreinstellung der Handler bezüglich + der Akzeptanz oder Ablehnung von PATH_INFO zu erlauben. + Eine solche Änderung ist zum Beispiel notwendig, wenn Sie einen + Filter wie INCLUDES verwenden, um Inhalte + abhängig von PATH_INFO zu generieren. Der + Core-Handler würde die Anfrage normalerweise abweisen. Verwenden + Sie die folgende Konfiguration, um dennoch solch ein Skript zu + ermöglichen.

+ +

+ <Files "mypaths.shtml">
+ + Options +Includes
+ SetOutputFilter INCLUDES
+ AcceptPathInfo On
+ + </Files> +

+ + +
+
top
+

AccessFileName-Direktive

+ + + + + + + +
Beschreibung:Name der dezentralen Konfigurationsdateien
Syntax:AccessFileName Dateiname [Dateiname] ...
Voreinstellung:AccessFileName .htaccess
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

Aus dieser Namensliste sucht der Server während der + Bearbeitung einer Anfrage in jedem Verzeichnis nach der ersten + existierenden Datei, sofern im betreffenden Verzeichnis dezentrale + Konfigurationsdateien erlaubt sind. + Beispiel:

+ +

+ AccessFileName .acl +

+ +

Vor der Rücksendung des Dokuments + /usr/local/web/index.html wird der Server + /.acl, /usr/.acl, + /usr/local/.acl und /usr/local/web/.acl + einlesen, solange diese nicht mit

+ +

+ <Directory />
+ + AllowOverride None
+ + </Directory> +

+ +

deaktiviert wurden.

+ +

Siehe auch

+ +
+
top
+

AddDefaultCharset-Direktive

+ + + + + + + + +
Beschreibung:Standard-Charset-Parameter, der bei Antworten vom Content-Type + text/plain oder text/html hinzugefügt wird +
Syntax:AddDefaultCharset On|Off|Zeichenkodierung
Voreinstellung:AddDefaultCharset Off
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
+

Die Direktive gibt einen Standardwert für den Charset-Paramter des + Medientyps (den Namen einer Zeichencodierung) an, der einer Antwort + genau dann hinzugefügt wird, wenn der Content-Type der Antwort entweder + text/plain oder text/html ist. Dies sollte jedes + mittels META-Element im Datenteil der Antwort angegebene + Charset überschreiben. Das genaue Verhalten hängt jedoch oft von + der Client-Konfiguration des Benutzers ab. Die Einstellung + AddDefaultCharset Off deaktiviert diese Funktionalität. + AddDefaultCharset On aktiviert die Standard-Zeichenkodierung + iso-8859-1. Jeder andere Wert wird als die zu verwendende + Zeichenkodierung aufgefaßt, die eines der bei IANA registrierten + Charset-Werte zur Verwendung in MIME-Medientypen sein sollte. Zum + Beispiel:

+ +

+ AddDefaultCharset utf-8 +

+ +

AddDefaultCharset sollte nur verwendet werden, + wenn von allen Textressourcen, für die es gilt, bekannt ist, dass sie + in dieser Zeichkodierung vorliegen, oder wenn es zu unbequem ist, ihre + Zeichenkodierung indivuell zu benennen. Ein solches Beispiel ist das + Hinzufügen des Charset-Parameters zu Ressourcen, die generierte + Inhalte enthalten. Ein Beispiel sind CGI-Skript-Altlasten, die aufgrund von + in die Ausgabe integrierten Daten, die durch den Benutzer übermittelt + wurden, gegen Cross-Site-Scripting-Angriffe verwundbar sind. Eine bessere + Lösung wäre jedoch, diese Skripte zu korrigieren (oder zu + löschen), da die Angabe einer Standard-Zeichencodierung keine + Anwender schützt, die in ihrem Browser die Funktion zur + automatischen Erkennung der Zeichenkodierung aktiviert haben.

+ +

Siehe auch

+ +
+
top
+

AddOutputFilterByType-Direktive

+ + + + + + + + +
Beschreibung:einen Ausgabefilter einem bestimmten MIME-Type +zuordnen
Syntax:AddOutputFilterByType Filter[;Filter...] +MIME-Type [MIME-Type] ...
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
Kompatibilität:Verfügbar ab Apache 2.0.33
+

Die Direktive aktiviert für eine Anfrage abhängig vom + MIME-Type der Antwort einen bestimmten Ausgabe-Filter.

+ +

Das folgende Beispiel verwendet den Filter DEFLATE, + der von mod_deflate angeboten wird. Er komprimiert + jede Ausgabe, die als text/html oder text/plain + gekennzeichnet ist, (gleichgültig, ob statisch oder dynamisch) + bevor sie an den Client gesendet wird.

+ +

+ AddOutputFilterByType DEFLATE text/html text/plain +

+ +

Wenn Sie den Inhalt von mehr als einem Filter verarbeiten lassen + wollen, dann müssen deren Namen durch Semikolons voneinander + getrennt werden. Es ist ebenfalls möglich, eine + AddOutputFilterByType-Direktive für + jeden von diesen Filtern zu verwenden.

+ +

Die folgende Konfiguration sorgt dafür, dass alle + Skriptausgaben, die als text/html gekennzeichnet + sind, zuerst vom INCLUDES-Filter und dann vom + DEFLATE-Filter verarbeitet werden.

+ +

+ <Location /cgi-bin/>
+ + Options Includes
+ AddOutputFilterByType INCLUDES;DEFLATE text/html
+ + </Location> +

+ +

Hinweis:

+

Die Aktivierung von Filtern mittels + AddOutputFilterByType kann in einigen + Fällen ganz oder teilweise fehlschlagen. Beispielsweise + werden keine Filter angewendet, wenn der MIME-Type nicht bestimmt + werden kann und auf die Einstellung der DefaultType-Anweisung zurückfällt, + selbst wenn die DefaultType-Einstellung die gleiche ist.

+ +

Wenn Sie jedoch sicherstellen wollen, dass der Filter + angewendet wird, sollten Sie den Content-Type z.B. mit + AddType oder + ForceType der Ressource + explizit zuordnen. Das Setzen des Content-Types innerhalb + eines (nicht-nph) CGI-Skriptes funktioniert ebenfalls + zuverlässig.

+ +

Die Typ-gebundenen Ausgabefilter werden niemals auf + Proxy-Anfragen angewendet.

+
+ +

Siehe auch

+ +
+
top
+

AllowEncodedSlashes-Direktive

+ + + + + + + + +
Beschreibung:Legt fest, ob kodierte Pfadtrennzeichen in URLs durchgereicht +werden dürfen
Syntax:AllowEncodedSlashes On|Off
Voreinstellung:AllowEncodedSlashes Off
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
Kompatibilität:Verfügbar ab Apache 2.0.46
+

Die AllowEncodedSlashes-Direktive erlaubt die + Verwendung von URLs, welche kodierte Pfadtrennzeichen (%2F + für / und auf entsprechenden Systemen zusätzlich + %5C für \) enthalten. Normalerweise werden + derartige URLs mit einem 404-Fehler (Nicht gefunden) abgewiesen.

+ +

AllowEncodedSlashes On ist + vor allem in Verbindung mit PATH_INFO hilfreich.

+ +

Anmerkung

+

Das Erlauben von Schrägstrichen impliziert nicht deren + Dekodierung. Vorkommen von %2F oder %5C + (nur auf entsprechenden Systemen) werden unverändert in der + ansonsten dekodierten URL belassen.

+
+ +

Siehe auch

+ +
+
top
+

AllowOverride-Direktive

+ + + + + + + +
Beschreibung:Direktiven-Typen, die in .htaccess-Dateien +erlaubt sind.
Syntax:AllowOverride All|None|Direktiven-Typ +[Direktiven-Typ] ...
Voreinstellung:AllowOverride All
Kontext:Verzeichnis
Status:Core
Modul:core
+

Wenn der Server eine .htaccess-Datei (wie durch + AccessFileName definiert) + findet, muss er wissen, welche in der Datei angegebenen Direktiven + frühere Konfigurationsanweisungen überschreiben + dürfen.

+ +

Nur in <Directory>-Abschnitten verfügbar

+ AllowOverride ist nur in <Directory>-Abschnitten + gültig, die ohne reguläre Ausdrücke definiert wurden, nicht + in <Location>-, + <DirectoryMatch>- oder + <Files>-Abschnitten. +
+ +

Wenn diese Anweisung auf None gesetzt wird, dann + werden .htaccess-Dateien komplett + ignoriert. In diesem Fall wird der Server nicht einmal versuchen, + die .htaccess-Dateien im Dateisystem zu lesen.

+ +

Wenn diese Anweisung auf All gesetzt wird, dann + ist jede Direktive in den .htaccess-Dateien erlaubt, + die den Kontext + .htaccess besitzt.

+ +

Der Direktiven-Typ kann eine der folgenden + Anweisungsgruppen sein.

+ +
+
AuthConfig
+ +
+ Erlaubt die Verwendung von Autorisierungs-Anweisungen (AuthDBMGroupFile, + AuthDBMUserFile, + AuthGroupFile, + AuthName, + AuthType, AuthUserFile, Require usw.).
+ +
FileInfo
+ +
+ Erlaubt die Verwendung von Direktiven zur Steuerung der + Dokumenttypen (DefaultType, ErrorDocument, ForceType, LanguagePriority, + SetHandler, SetInputFilter, SetOutputFilter, und + mod_mime-Direktiven Add* und Remove* + usw.).
+ +
Indexes
+ +
+ Erlaubt die Verwendung von Direktiven zur Steuerung von + Verzeichnisindizes (AddDescription, + AddIcon, AddIconByEncoding, + AddIconByType, + DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName + usw.).
+ +
Limit
+ +
+ Erlaubt die Verwendung von Direktiven zur Steuerung des + Zugriffs von Hosts (Allow, Deny und Order).
+ +
Options[=Option,...]
+ +
+ Erlaubt die Verwendung von Direktiven zur Steuerung spezieller + Verzeichniseigenschaften (Options + und XBitHack). Sie + können mit einem Gleichheitszeichen gefolgt von einer + kommaseparierten Liste (ohne Leerzeichen) angeben, welche Optionen mit + der Options-Direktive gesetzt + werden dürfen.
+
+ +

Beispiel:

+ +

+ AllowOverride AuthConfig Indexes +

+ +

Im obigen Beispiel erzeugen alle Direktiven einen internal server + error (Anm.d.Ü.: Server-interner Fehler), die weder der + Gruppe AuthConfig noch der Gruppe Indexes + angehören.

+ +

Siehe auch

+ +
+
top
+

AuthName-Direktive

+ + + + + + + +
Beschreibung:Autorisierungsbereich zur Verwendung in der +HTTP-Authentisierung
Syntax:AuthName auth-Bereich
Kontext:Verzeichnis, .htaccess
AllowOverride:AuthConfig
Status:Core
Modul:core
+

Die Direktive legt den Namen des Autorisierungsbereiches + (Anm.d.Ü.: Der Autorisierungsbereich wird auch Realm genannt.) + für ein Verzeichnis fest. Dieser Realm wird dem Client mitgeteilt, + damit der Anwender weiß, welchen Benutzernamen und welches Passwort + er zu übermitteln hat. AuthName akzeptiert ein + Argument. Falls der Name des Realm Leerzeichen enthält, muss er in + Anführungszeichen eingeschlossen werden. Um zu funktionieren, muss + die Anweisung von den Direktiven AuthType und Require sowie von + Direktiven wie AuthUserFile + und AuthGroupFile + begleitet werden.

+ +

Beispiel:

+ +

+ AuthName "Top Secret" +

+ +

Die AuthName übergebene Zeichenkette ist das, + was in dem von den meisten Browsern angebotenen Passwort-Dialog + angezeigt wird.

+ +

Siehe auch

+ +
+
top
+

AuthType-Direktive

+ + + + + + + +
Beschreibung:Art der Authentisierung
Syntax:AuthType Basic|Digest
Kontext:Verzeichnis, .htaccess
AllowOverride:AuthConfig
Status:Core
Modul:core
+

Die Direktive wählt die Art der Benutzer-Authentisierung + für ein Verzeichnis aus. Derzeit sind lediglich Basic + und Digest implementiert. + Um zu funktionieren, muss die Anweisung von den Direktiven AuthName und Require sowie von + Direktiven wie AuthUserFile + und AuthGroupFile + begleitet werden.

+ +

Siehe auch

+ +
+
top
+

CGIMapExtension-Direktive

+ + + + + + + + +
Beschreibung:Technik zur Bestimmung des Interpreters für +CGI-Skripte
Syntax:CGIMapExtension CGI-Pfad .Endung
Kontext:Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
Kompatibilität:ausschließlich NetWare
+

Die Direktive wird zur Steuerung verwendet, wie Apache + den Interpreter ermittelt, der zur Ausführung von + CGI-Skripten verwendet wird. Beispielsweise bestimmt die Angabe + von CGIMapExtension sys:\foo.nlm .foo, dass + alle CGI-Scripte mit der Endung .foo an den + FOO-Interpreter übergeben werden.

+ +
+
top
+

ContentDigest-Direktive

+ + + + + + + + +
Beschreibung:Aktiviert die Generierung von Content-MD5 +HTTP-Response-Headern
Syntax:ContentDigest On|Off
Voreinstellung:ContentDigest Off
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:Options
Status:Core
Modul:core
+

Die Direktive aktiviert die Generierung von + Content-MD5-Headern, wie sie in RFC1864 bzw. RFC2068 + definiert sind.

+ +

MD5 ist ein Algorithmus zur Berechnung eines "Datenextrakts" + (zuweilen "Fingerabdruck" genannt) (Anm.d.Ü.: Der "Datenextrakt" wird im + Englischen als "message digest" oder "fingerprint" bezeichnet.) + aus beliebig langen Daten. Es gilt als zuverlässig, dass + Veränderungen an den Daten sich in Veränderungen des + Extrakts wiederspiegeln.

+ +

Der Content-MD5-Header bietet eine + End-to-End-Integritätsprüfung (MIC) (Anm.d.Ü.: MIC steht für + "message integrity check".) des Daten-Inhalts. Ein Proxy oder + Client kann diesen Header prüfen, um zufällige Veränderungen + des Entity-Inhalts bei der Übertragung festzustellen. + Beispielheader:

+ +

+ Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA== +

+ +

Beachten Sie bitte, dass dies Performanceprobleme auf Ihrem + System verursachen kann, da der Extrakt bei jeder Anfrage + berechnet wird (der Wert wird nicht zwischengespeichert).

+ +

Content-MD5 wird nur für Dokumente gesendet, + die von core bedient werden, nicht jedoch bei + Modulen. SSI-Dokumente, CGI-Skript-Ausgaben und Byte-Range-Antworten + besitzen diesen Header beispielsweise nicht.

+ +
+
top
+

DefaultType-Direktive

+ + + + + + + + +
Beschreibung:MIME-Content-Type, der gesendet wird, wenn der Server den Typ +nicht auf andere Weise ermitteln kann.
Syntax:DefaultType MIME-Type
Voreinstellung:DefaultType text/plain
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
+

Es kann vorkommen, dass der Server ein Dokument ausliefern muss, + dessen Typ er nicht mit Hilfe seiner MIME-Type-Zuordnungen bestimmen + kann.

+ +

Der Server muss den Client über den Content-Type des + Dokumentes informieren. Daher verwendet er im Falle eines + unbekannten Typs die DefaultType-Einstellung. + Zum Beispiel:

+ +

+ DefaultType image/gif +

+ +

wäre angemessen für ein Verzeichnis, das viele GIF-Bilder + enthält, deren Dateinamen nicht Endung .gif + besitzen.

+ +

Beachten Sie bitte, dass die Direktive anders als ForceType lediglich den Standard-MIME-Type + bestimmt. Alle anderen MIME-Type-Definitionen, einschließlich + Dateierweiterungen, die den Medien-Typ anzeigen können, + überschreiben diese Voreinstellung.

+ +
+
top
+

<Directory>-Direktive

+ + + + + + +
Beschreibung:Umschließt eine Gruppe von Direktiven, die nur auf +das genannte Verzeichnis des Dateisystems und Unterverzeichnisse angewendet +werden
Syntax:<Directory Verzeichnispfad> +... </Directory>
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

<Directory> und + </Directory> werden dazu verwendet, eine Gruppe + von Direktiven zusammenzufassen, die nur für das genannte + Verzeichnis und dessen Unterverzeichnisse gelten. Jede Direktive, + die im Verzeichnis-Kontext erlaubt ist, kann verwendet werden. + Verzeichnispfad ist entweder der vollständige Pfad zu + einem Verzeichnis oder eine Zeichenkette mit Platzhaltern wie sie von der + Unix-Shell zum Abgleich verwendet werden. In einer Zeichenkette + mit Platzhaltern (Anm.d.Ü.: sogenannte wild-cards) entspricht + ? einem einzelnen Zeichen und * einer + Zeichenkette beliebiger Länge. Sie können auch auch + []-Zeichenbereiche verwenden. Keiner der Platzhalter + entspricht dem Zeichen "/". Daher passt <Directory + /*/public_html> nicht auf /home/user/public_html, + <Directory /home/*/public_html> jedoch tut es. + Beispiel:

+ +

+ <Directory /usr/local/httpd/htdocs>
+ + Options Indexes FollowSymLinks
+ + </Directory> +

+ +
+

Seien Sie vorsichtig mit den Verzeichnispfad-Argumenten. + Sie müssen buchstäblich mit dem Dateisystempfad + übereinstimmen, den der Apache für den Zugriff auf die + Dateien verwendet. Direktiven, die für ein bestimmtes + Verzeichnis gelten, gelten nicht für Dateien in dem Verzeichnis, + auf die über einen anderen Pfad zugegriffen wird, wie z.B. + über verschiedene symbolische Links.

+
+ +

Erweiterte reguläre Ausdrücke können ebenfalls + verwendet werden, indem das Zeichen ~ hinzugefügt + wird. Beispielsweise würde

+ +

+ <Directory ~ "^/www/.*/[0-9]{3}"> +

+ +

auf Verzeichnisse in /www/ passen, die aus drei + Zahlen bestehen.

+ +

Wenn mehrere <Directory>-Abschnitte + (ohne reguläre Ausdrücke) auf ein Verzeichnis (oder + ein ihm übergeordnetes Verzeichnis) passen, welches ein Dokument + enthält, dann werden die Direktiven der Reihe nach, angefangen + beim kürzesten passenden Muster, vermischt mit den Direktiven + aus den .htaccess-Dateien, angewendet. + Beispiel:

+ +

+ <Directory />
+ + AllowOverride None
+ + </Directory>
+
+ <Directory /home/>
+ + AllowOverride FileInfo
+ + </Directory> +

+ +

Beim Zugriff auf das Dokument /home/web/dir/doc.html + sind die einzelnen Schritte:

+ +
    +
  • Wende die Direktive AllowOverride None an + (deaktiviere .htaccess-Dateien).
    • + +
  • Wende die Direktive AllowOverride FileInfo + (auf das Verzeichnis /home) an.
    • + +
  • Wende jede FileInfo-Direktive aus + /home/.htaccess, /home/web/.htaccess und + /home/web/dir/.htaccess der Reihe nach an.
    • +
+ +

Reguläre Ausdrücke werden solange nicht berücksichtigt, + bis alle normalen Abschnitte angewendet wurden. Anschließend + werden alle regulären Ausdrücke in der Reihenfolge + geprüft, in der sie in der Konfigurationsdatei auftauchen. + Beispielsweise wird bei

+ +

+ <Directory ~ abc$>
+ + # ... hier die Direktiven ...
+ + </Directory> +

+ +

der Abschnitt mit dem regulären Ausdruck nicht + berücksichtigt, bis alle normalen + <Directory>-Abschnitte und + .htaccess-Dateien angewendet wurden. Dann erst wird + der reguläre Ausdruck mit /home/abc/public_html/abc + abgeglichen und der entsprechende <Directory>-Abschnitt angewendet.

+ +

Beachten Sie bitte, dass der vom Apache voreingestellte + Zugriff für <Directory /> + Allow from All ist. Das bedeutet, dass der Apache + jede Datei ausliefert, die durch eine URL abgebildet wird. Es wird + empfohlen, dass Sie dies durch einen Block wie

+ +

+ <Directory />
+ + Order Deny,Allow
+ Deny from All
+ + </Directory> +

+ +

ändern und anschließend für + Verzeichnisse überschreiben, die Sie verfügbar machen + wollen. Für weitere Einzelheiten lesen Sie bitte + die Seite zu den Sicherheitshinweisen.

+ +

Die Verzeichnisabschnitte erscheinen in der Datei + httpd.conf. <Directory>-Direktiven dürfen nicht + ineinander verschachtelt werden oder innerhalb von <Limit>- oder <LimitExcept>-Abschnitten auftauchen.

+ +

Siehe auch

+ +
+
top
+

<DirectoryMatch>-Direktive

+ + + + + + +
Beschreibung:Umschließt eine Gruppe von Direktiven, die auf + Verzeichnisse des Dateisystems und ihre Unterverzeichnisse abgebildet + werden, welche auf einen regulären Ausdruck passen
Syntax:<DirectoryMatch regex> +... </DirectoryMatch>
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

<DirectoryMatch> und + </DirectoryMatch> werden dazu verwendet, eine + Gruppe von Direktiven zusammenzufassen, die nur für das + genannte Verzeichnis und dessen Unterverzeichnisse gelten, genauso + wie bei <Directory>. + Als Argument dient jedoch ein regulärer Ausdruck. + Beispielsweise würde

+ +

+ <DirectoryMatch "^/www/.*/[0-9]{3}"> +

+ +

auf Verzeichnisse in /www/ passen, die aus drei + Zeichen bestehen.

+ +

Siehe auch

+ +
+
top
+

DocumentRoot-Direktive

+ + + + + + + +
Beschreibung:Verzeichnis, welches den Haupt-Dokumentenbaum bildet, der im +Web sichtbar ist.
Syntax:DocumentRoot Verzeichnis
Voreinstellung:DocumentRoot /usr/local/apache/htdocs
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

Die Direktive setzt das Verzeichnis, von dem aus + httpd Dateien ausliefert. Sofern nicht eine Direktive + wie Alias greift, hängt + der Server Pfade aus der angeforderten URL an das Wurzelverzeichnis + an, um den Pfad zum Dokument zu bilden. Beispiel:

+ +

+ DocumentRoot /usr/web +

+ +

Damit bezieht sich ein Zugriff auf + http://www.my.host.com/index.html auf + /usr/web/index.html. Wenn das Verzeichnis nicht + absolut angegeben ist, wird es relativ zu ServerRoot betrachtet.

+ +

DocumentRoot sollte ohne einen + Schrägstrich am Ende angegeben werden.

+ +

Siehe auch

+ +
+
top
+

EnableMMAP-Direktive

+ + + + + + + + +
Beschreibung:Verwende Memory-Mapping, um Dateien während der +Auslieferung zu lesen
Syntax:EnableMMAP On|Off
Voreinstellung:EnableMMAP On
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
+

Die Direktive steuert, ob httpd Memory-Mapping + verwenden darf, wenn er während der Auslieferung den Inhalt einer + Datei lesen muss. Wenn die Bearbeitung einer Anfrage es erfordert, + auf die Daten in einer Datei zuzugreifen -- zum Beispiel bei der + Auslieferung einer mittels mod_include serverseitig + analysierten Datei --, dann verwendet der Apache standardmäßig + Memory-Mapping für diese Datei, sofern das Betriebssystem es + unterstützt.

+ +

Memory-Mapping bedeutet zuweilen eine Performanceverbesserung. + In einigen Umgebungen ist es jedoch besser, Memory-Mapping zu + deaktivieren, um Problemen während des Betriebs vorzubeugen:

+ +
    +
  • Bei einigen Multiprozessorsystemen kann Memory-Mapping die + Performance von httpd reduzieren.
    • +
  • Bei einem per NFS eingebundenen DocumentRoot kann httpd mit + einem Speicherzugriffsfehler (Anm.d.Ü.: ein so genannter "segmentation + fault") abstürzen, wenn eine Datei gelöscht oder + gekürzt wird, während httpd sie im Speicher + abbildet.
    • +
+ +

Bei Serverkonfigurationen, die für dieses Problem + anfällig sind, sollten Sie das Memory-Mapping für + auszuliefernde Dateien deaktivieren, indem Sie schreiben:

+ +

+ EnableMMAP Off +

+ +

Bei per NFS eingebundenen Dateien kann diese Funktion + explizit für die störenden Dateien deaktiviert werden, + indem Sie angeben:

+ +

+ <Directory "/pfad-zu-den-nfs-dateien"> + + EnableMMAP Off + + </Directory> +

+ +
+
top
+

EnableSendfile-Direktive

+ + + + + + + + + +
Beschreibung:Verwende die sendfile-Unterstützung des Kernels, um +Dateien an den Client auszuliefern
Syntax:EnableSendfile On|Off
Voreinstellung:EnableSendfile On
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
Kompatibilität:Verfügbar ab Apache Version 2.0.44
+

Die Direktive steuert, ob httpd die + sendfile-Unterstützung des Kernels verwenden kann, um + Dateiinhalte an den Client zu übermitteln. Wenn die Bearbeitung + einer Anfrage keinen Zugriff auf die Daten in der Datei erfordert -- + zum Beispiel bei der Auslieferung einer statischen Datei -- und das + Betriebssystem es unterstützt, verwendet der Apache + standardmäßig sendfile, um den Dateiinhalt zu + übertragen, ohne die Datei jemals zu lesen.

+ +

Der sendfile-Mechanismus vermeidet getrennte Lese- und + Sendeoperationen sowie Puffer-Zuweisungen. Bei einigen Plattformen bzw. + Dateisystemen deaktivieren Sie diese Funktion jedoch besser, um Probleme + während des Betriebs zu vermeiden:

+ +
    +
  • Einige Plattformen besitzen u.U. eine fehlerhafte + sendfile-Unterstützung, die das Erstellungssystem nicht erkennt, + insbesondere wenn die Binärdateien auf einem anderen Rechner erstellt + und auf eine solche Maschine mit fehlerhafter sendfile-Unterstützung + übertragen wurden.
    • +
  • Bei einem über das Netzwerk eingebundenen DocumentRoot (z.B. NFS oder SMB) ist der + Kernel möglicherweise nicht in der Lage, die Netzwerkdatei + über seinen eigenen Cache zu bedienen.
    • +
  • Unter Linux löst die Verwendung von sendfile + in Verbindung mit bestimmten Netzwerkkarten und IPv6 + TCP-Checksummenfehler aus.
    • +
+ +

Bei Serverkonfigurationen, die für dieses Problam + anfällig sind, sollten die diese Funktion deaktivieren, indem + Sie schreiben:

+ +

+ EnableSendfile Off +

+ +

Bei per NFS oder SMB eingebundenen Dateien kann diese Funktion + explizit für die störenden Dateien deaktiviert werden, indem + Sie angeben:

+ +

+ <Directory "/pfad-zu-den-nfs-dateien"> + + EnableSendfile Off + + </Directory> +

+ +
+
top
+

ErrorDocument-Direktive

+ + + + + + + + +
Beschreibung:Das, was der Server im Fehlerfall an den Client +zurückgibt
Syntax:ErrorDocument Fehlercode Dokument
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
Kompatibilität:Die Syntax der Anführungszeichen bei Textnachrichten hat +sich im Apache 2.0 geändert
+

Im Falle eines Problems oder Fehlers kann der Apache + konfiguriert werden, eine der vier Aktionen auszuführen:

+ +
    +
  1. Ausgabe einer einfachen, hartkodierten Fehlermeldung
    2. + +
  2. Ausgabe einer angepassten Meldung
    3. + +
  3. Umleitung zu einem lokalen URL-Pfad der das + Problem bzw. den Fehler behandelt
    4. + +
  4. Umleitung zu einer externen URL, die das Problem + bzw. den Fehler behandelt
    5. +
+ +

Die erste Option ist Voreinstellung, während die Optionen + 2 bis 4 über die Direktive ErrorDocument + eingestellt werden, welcher der HTTP-Statuscode und eine + URL oder Nachricht folgen. Abhängig vom Problem bzw. Fehler bietet + der Apache manchmal zusätzliche Informationen an.

+ +

URLs können bei lokalen Webpfaden mit einem Schrägstrich + (/) beginnen (relativ zum DocumentRoot-Verzeichnis) oder eine vollständige URL + bilden, die der Client auflösen kann. Alternativ kann eine + Nachricht für die Anzeige im Browser angeboten werden. Beispiel:

+ +

+ ErrorDocument 500 http://foo.example.com/cgi-bin/tester
+ ErrorDocument 404 /cgi-bin/falsche_urls.pl
+ ErrorDocument 401 /info_zur_anmeldung.html
+ ErrorDocument 403 "Der Zugriff ist nicht erlaubt." +

+ +

Außerdem kann der spezielle Wert default angegeben + werden, um die schlichte, hartkodierte Nachricht des Apache zu verwenden. + Es wird normalerweise nicht benötigt, doch default + stellt die einfach, im Apache hartkodierte Meldung in Konfigurationen + wieder her, die ansonsten von einem existierenden (Anm.d.Ü.: zuvor + konfigurierten) ErrorDocument erben + würden.

+ +

+ ErrorDocument 404 /cgi-bin/bad_urls.pl

+ <Directory /web/docs>
+ + ErrorDocument 404 default
+ + </Directory> +

+ +

Wenn Sie eine ErrorDocument-Anweisung + angeben, die auf eine entfernte URL weist (d.h. irgendetwas mit der + Methode http davor), beachten Sie bitte, dass der Apache + eine Umleitung zum Client sendet, um diesem mitzuteilen, wo das + Dokument zu finden ist, auch wenn das Dokument letztlich wieder zum + gleichen Server führt. Das hat mehrere Auswirkungen. Die + wichtigste ist, dass der Client nicht den Original-Statuscode + erhält sondern statt dessen einen Umleitungs-Statuscode. Dies + wiederum kann Web-Robots und andere Clients verwirren, die den + Statuscode dazu verwenden, herauszufinden ob eine URL gültig ist. + Wenn Sie eine entfernte URL in einer Anweisung + ErrorDocument 401 verwenden, wird der Client + darüber hinaus nicht wissen, dass er den Benutzer zur Eingabe + eines Passwortes auffordern muss, da er den Statuscode 401 nicht + erhält. Deshalb müssen Sie sich auf ein lokales + Dokument beziehen, wenn Sie eine Anweisung ErrorDocument + 401 verwenden.

+ +

Der Microsoft Internet Explorer (MSIE) ignoriert + standardmäßig serverseitig generierte Fehlermeldungen, wenn + sie "zu kurz" sind und ersetzt sie durch eigene "freundliche" + Fehlermeldungen. Die Größe variiert abhängig von der + Art des Fehlers, im Allgemeinen zeigt der MSIE jedoch den + serverseitig generierten Fehler, anstatt ihn zu verstecken, wenn Ihr + Fehlerdokument größer als 512 Bytes ist. Weitere Informationen + sind im Artikel Q294807 in der Microsoft Knowledgebase verfügbar.

+ +

Obwohl die meisten Fehlermeldungen überschrieben werden + können, werden unter bestimmten Umständen die internen + Meldungen ungeachtet der Einstellung der ErrorDocument-Direktive verwendet. Insbesondere bei + einer fehlerhaften Anfrage werden der normale Bearbeitungsprozess sofort + beendet und die interne Meldung zurückgegeben. Das ist notwendig, um + Sicherheitsprobleme zu vermeiden, die auf Grund fehlerhafter Anfragen + entstehen.

+ +

In Versionen vor 2.0 wurden Meldungen durch ein einzelnes + vorangestelltes Anführungszeichen (") erkannt.

+ +

Siehe auch

+ +
+
top
+

ErrorLog-Direktive

+ + + + + + + +
Beschreibung:Ablageort, an dem der Server Fehler protokolliert
Syntax: ErrorLog Dateiname|syslog[:facility]
Voreinstellung:ErrorLog logs/error_log (Unix) ErrorLog logs/error.log (Windows and + OS/2)
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

Die Direktive ErrorLog bestimmt den Namen + der Datei, in welcher der Server alle auftretenden Fehler protokolliert. + Wenn Dateiname nicht absolut ist, wird er relativ zu ServerRoot betrachtet.

+ +

Beispiel

+ ErrorLog /var/log/httpd/error_log +

+ +

Wenn der Dateiname mit einem senkrechten Strich (|, + engl.: Pipe) beginnt, wird angenommen, dass es sich um einen Befehl + handelt, der ausgeführt wird, um das Fehlerprotokolls zu + verarbeiten.

+ +

Beispiel

+ ErrorLog "|/usr/local/bin/httpd_errors" +

+ +

Die Verwendung von syslog anstelle eines Dateinamens + aktiviert die Protokollierung mittels syslogd(8), sofern das System + es unterstützt. Als Voreinstellung wird der syslog-Typ (syslog + facility) local7 verwendet, Sie können dies jedoch + auch überschreiben, indem Sie die Syntax + syslog:facility verwenden, wobei + facility einer der Namen sein kann, die üblicherweise + in syslog(1) dokumentiert sind.

+ +

Beispiel

+ ErrorLog syslog:user +

+ +

SICHERHEITSHINWEIS: Lesen Sie das Dokument Sicherheitshinweise + zu Einzelheiten darüber, warum Ihre Sicherheit gefährdet + sein kann, wenn das Verzeichnis, in dem die Log-Dateien gespeichert + werden, für jemand anderen, als den Benutzer, der den Server + gestartet hat, beschreibbar ist.

+ +

Anmerkung

+

Bei der Eingabe eines Dateipfads auf nicht-Unix-Plattformen sollte + darauf geachtet werden, nur (Vorwärts-)Schrägstriche zu + verwenden, auch wenn die Plattform rückwärts gerichtete + Schrägstriche (Backslashes) erlaubt. Im Allgemeinen ist es eine gute + Idee, innerhalb der Konfigurationsdateien immer + Vorwärts-Schrägstriche zu verwenden.

+
+ +

Siehe auch

+ +
+
top
+

FileETag-Direktive

+ + + + + + + + +
Beschreibung:Dateiattribute, die zur Erstellung des HTTP-Response-Headers +ETag verwendet werden
Syntax:FileETag Komponente ...
Voreinstellung:FileETag INode MTime Size
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
+

Wenn dem Dokument eine Datei zugrundeliegt, bestimmt die Direktive + FileETag die Dateiattribute, die zur Erstellung + des HTTP-Response-Headers ETag (Entity-Tag) verwendet + werden. (Der Wert von ETag wird bei der Cache-Verwaltung + zur Einsparung von Netzwerk-Bandbreite benutzt.) Im Apache 1.3.22 und + früher wurde der ETag-Wert stets aus + der I-Node, der Größe und dem Datum der letzten + Änderung (mtime) der Datei gebildet. Die Direktive + FileETag erlaubt es Ihnen, zu bestimmen, + welche dieser Eigenschaften -- falls überhaupt -- verwendet + werden sollen. Die gültigen Schlüsselworte lauten:

+ +
+
INode
+
Die I-Node-Nummer wird in die Berechnung mit einbezogen
+
MTime
+
Datum und Uhrzeit der letzten Änderung werden mit einbezogen
+
Size
+
Die Anzahl der Bytes in der Datei wird mit einbezogen
+
All
+
Alle verfügbaren Angaben werden verwendet. Die ist + gleichbedeutend mit: +

FileETag INode MTime Size

+
None
+
Es wird keine ETag-Angabe in die Antwort eingefügt, + wenn dem Dokument eine Datei zugrundeliegt.
+
+ +

Den Schlüsselwörtern INode, MTime + und Size kann entweder ein + oder ein + - vorangestellt werden, was die Änderung einer + Vorgabe erlaubt, die von einem größeren Umfeld + geerbt wurde. Jedes Schlüselwort ohne ein solches Prefix + hebt die ererbte Einstellung sofort und vollständig auf.

+ +

Wenn die Konfiguration für ein Verzeichnis + FileETag INode MTime Size enthält + und die eines Unterverzeichnisses FileETag -INode, + dann ist die Einstellung für das Unterverzeichnis (die an + jedes Unter-Unterverzeichnis weitervererbt wird, welches dies nicht + überschreibt) äquivalent mit + FileETag MTime Size.

+ +
+
top
+

<Files>-Direktive

+ + + + + + + +
Beschreibung:Enthält Direktiven, die sich nur auf passende Dateinamen +beziehen
Syntax:<Files Dateiname> ... </Files>
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Die Direktive <Files> + begrenzt die Reichweite der enthaltenen Anweisungen auf Dateinamen. + Sie ist vergleichbar mit den Direktiven <Directory> und <Location>. Sie muss eine + passende </Files>-Anweisung besitzen. + Die innerhalb dieses Abschnittes angegebenen Direktiven werden auf + jedes Objekt mit einem Basisnamen (letzte Komponente des Dateinamens) + angewendet, der auf die angegebenen Dateinamen passt. <Files>-Container werden, nachdem die + <Directory>-Container + und .htaccess-Dateien gelesen sind, jedoch vor den + <Location>-Containern, + in der Reihenfolge ihres Auftretens ausgeführt. Beachten Sie, dass + <Files>-Anweisungen innerhalb von + <Directory>-Containern + auftreten können, um den Teil des Dateisystems einzuschränken, + den sie betreffen.

+ +

Das Argument Dateiname kann einen Dateinamen oder eine + Zeichenkette mit Platzhaltern enthalten, wobei ? auf ein + einzelnes Zeichen passt und * auf eine beliebige Folge von + Zeichen. Erweiterte reguläre Ausdrücke können ebenfalls + verwendet werden, indem das Zeichen ~ hinzugefügt wird. + Beispielsweise würde

+ +

+ <Files ~ "\.(gif|jpe?g|png)$"> +

+ +

auf die gebräuchlichsten Grafikformate im Internet passen. + <FilesMatch> wird + jedoch bevorzugt.

+ +

Beachten Sie bitte, dass die <Files>-Container anders als <Directory>- und <Location>-Container innerhalb + von .htaccess-Dateien verwendet werden können. + Dies erlaubt den Anwendern auf Dateiebene die Kontrolle über ihre + eigenen Dateien.

+ +

Siehe auch

+ +
+
top
+

<FilesMatch>-Direktive

+ + + + + + + +
Beschreibung:Enthält Direktiven, die für Dateinamen gelten, die + auf einen regulären Ausdruck passen
Syntax:<FilesMatch regex> ... </FilesMatch>
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Die Direktive <FilesMatch> + begrenzt wie die Direktive <Files> die enthaltenen Anweisungen auf + Dateinamen. Sie akzeptiert jedoch reguläre Ausdrücke. + Beispielsweise würde

+ +

+ <FilesMatch "\.(gif|jpe?g|png)$"> +

+ +

auf die gebräuchlichsten Grafikformate im Internet passen.

+ +

Siehe auch

+ +
+
top
+

ForceType-Direktive

+ + + + + + + + +
Beschreibung:Erzwingt die Auslieferung aller passendenden Dateien mit dem +angegebenen MIME-Content-Type
Syntax:ForceType MIME-Type|None
Kontext:Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
Kompatibilität:Wurde im Apache 2.0 in den Core verschoben
+

Wenn sie innerhalb einer .htaccess-Datei, eines + <Directory>-, + <Location>- + <Files>-Containers + angegeben wird, erzwingt die Direktive die Auslieferung aller + entsprechenden Dateien mit dem Content-Type, der durch + MIME-Type definiert wurde. Wenn Sie zum Beispiel ein + Verzeichnis voller GIF-Dateien haben, die Sie nicht alle durch + .gif kennzeichnen wollen, können Sie angeben:

+ +

+ ForceType image/gif +

+ +

Beachten Sie bitte, dass die Direktive anders als DefaultType alle MIME-Type-Zuordnungen + überschreibt, einschließlich Dateiendungen, die einen + Medientyp bezeichnen könnten.

+ +

Sie können jede ForceType-Angabe + durch die Verwendung des Wertes None überschreiben:

+ +

+ # erzwinge image/gif für alle Dateien:
+ <Location /images>
+ + ForceType image/gif
+ + </Location>
+
+ # hier jedoch normale MIME-Type-Zuordnungen:
+ <Location /images/mixed>
+ + ForceType None
+ + </Location> +

+ +
+
top
+

HostnameLookups-Direktive

+ + + + + + + +
Beschreibung:Aktiviert DNS-Lookups auf Client-IP-Adressen
Syntax:HostnameLookups On|Off|Double
Voreinstellung:HostnameLookups Off
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis
Status:Core
Modul:core
+

Diese Direktive aktiviert die DNS-Abfrage (Anm.d.Ü.: ein sogenannter + DNS-Lookup), so dass Hostnamen protokolliert (und in + REMOTE_HOST an CGIs/SSIs übergeben) werden könnnen. + Der Wert Double bezieht sich auf ein + Double-Reverse-DNS-Lookup. D.h. nachdem ein Reverse-Lookup + durchgeführt wurde, wird dann auf dem Ergebnis ein + Forward-Lookup ausgeführt. Wenigstens eine der IP-Adressen + aus dem Forward-Lookup muss der Originaladresse entsprechen. + (In der "tcpwrappers"-Terminologie wird dies PARANOID + genannt.)

+ +

Unabhängig von der Einstellung wird ein Double-Reverse-Lookup + durchgeführt, wenn mod_authz_host zur + Zugriffskontrolle per Hostnamen eingesetzt wird. Dies ist aus + Sicherheitsgründen notwendig. Beachten Sie, dass das Ergebnis dieses + Double-Reverse-Lookups nicht generell verfügbar ist, solange Sie + nicht HostnameLookups Double setzen. Wenn beispielsweise + nur HostnameLookups On angegeben ist und eine Anfrage + für ein Objekt erfolgt, welches durch Hostnamen-Beschränkungen + geschützt ist, dann wird CGIs nur das Ergebnis des + Singel-Reverse-Lookups in REMOTE_HOST übergeben, + egal ob das Doble-Reverse-Lookup fehlschlug oder nicht.

+ +

Die Voreinstellung ist Off, um Netzwerktraffic bei den + Angeboten einzusparen, die nicht tatsächlich Reverse-Lookups + benötigen. Es ist auch für die Endanwender besser, da sie nicht + die zusätzliche Wartezeit ertragen müssen, die ein Lookup mit + sich bringt. Hoch frequentierte Angebote sollten diese Direktive auf + Offlassen. Das Hilfsprogramm logresolve, das standardmäßig in das + Unterverzeichnis bin Ihres Installationsverzeichnisses + kompiliert wird, kann dazu verwendet werden, um offline Hostnamen von + protokollierten IP-Adressen nachzuschlagen.

+ +
+
top
+

<IfDefine>-Direktive

+ + + + + + + +
Beschreibung:Schließt Direktiven ein, die nur ausgeführt werden, +wenn eine Testbedingung beim Start wahr ist
Syntax:<IfDefine [!]Parametername> ... + </IfDefine>
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Der Container <IfDefine Test>...</IfDefine> + wird dazu verwendet, Direktiven als bedingt zu kennzeichnen. + Die Direktiven innerhalb eines <IfDefine>-Abschnittes werden nur ausgeführt, + wenn Test wahr ist. Ist Test falsch, wird alles + zwischen der Start- und Endemarkierung ignoriert.

+ +

In der <IfDefine>-Anweisung kann + Test eine von zwei Formen annehmen:

+ +
    +
  • Parametername
    • + +
  • !Parametername
    • +
+ +

Im ersten Fall werden die Direktiven zwischen der Start- und + Endemarkierung nur ausgeführt, wenn der Parameter namens + Parametername definiert ist. Die zweite Form kehrt den + Test um und führt die Direktiven nur dann aus, wenn + Parametername nicht definiert ist.

+ +

Das Argument Parametername ist ein sogenanntes + "Define", das beim beim Start des Servers in der + httpd-Befehlszeile durch + -DParameter angegeben wird.

+ +

<IfDefine>-Container können + ineinander verschachtelt werden, um einfache Multi-Parameter-Tests + zu implementieren. Beispiel:

+ +

+ httpd -DReverseProxy ...
+
+ # httpd.conf
+ <IfDefine ReverseProxy>
+ + LoadModule rewrite_module modules/mod_rewrite.so
+ LoadModule proxy_module modules/libproxy.so
+ + </IfDefine> +

+ +
+
top
+

<IfModule>-Direktive

+ + + + + + + + +
Beschreibung:Schließt Direktiven ein, die abhängig vom +Vorhandensein oder Fehlen eines speziellen Moduls ausgeführt +werden
Syntax:<IfModule [!]Modulname|Modulbezeichner> + ... </IfModule>
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
Kompatibilität:Modulbezeichner sind ab Version 2.1 + verfügbar.
+

Der Container <IfModule + Test>...</IfModule> wird dazu verwendet, + Direktiven als abhängig von dem Vorhandensein eines speziellen + Moduls zu kennzeichnen. Die Direktiven innerhalb eines <IfModule>-Abschnitts werden nur + ausgeführt, wenn Test wahr ist. Ist Test + falsch, wird alles zwischen der Start- und Endemarkierung ignoriert.

+ +

In der <IfModule>-Anweisung + kann Test eine von zwei Formen annehmen:

+ +
    +
  • Modul
    • + +
  • !Modul
    • +
+ +

Im ersten Fall werden die Direktiven zwischen der Start- und + Endemarkierung nur ausgeführt, das Modul namens + Modul im Apache enthalten ist -- entweder einkompiliert + oder mittels LoadModule + dynamisch geladen. Die zweite Form dreht den Test um und führt die + Direktiven nur aus, wenn Modul nicht + enthalten ist.

+ +

Das Argument Modul kann entweder der Modulbezeichner oder + der Dateiname des Moduls zum Zeitpunkt seiner Kompilierung sein. + rewrite_module beispielsweise ist der Bezeichner und + mod_rewrite.c ist der Dateiname. Wenn ein Modul aus mehreren + Quelltext-Dateien besteht, verwenden Sie den Namen der Datei, welche die + Zeichenfolge STANDARD20_MODULE_STUFF enthält.

+ +

<IfModule>-Container können + inneinander verschachtelt werden, um einfache Multi-Modul-Tests + durchzuführen.

+ +

Dieser Container sollte verwendet werden, wenn Sie eine + Konfigurationsdatei benötigen, die unabhängig davon funktioniert, + ob ein bestimmtes Modul verfügbar ist oder nicht. Normalerweise + ist es nicht notwendig, Direktiven in <IfModule>-Containern unterzubringen.

+ +
+
top
+

Include-Direktive

+ + + + + + + +
Beschreibung:Fügt andere Konfigurationsdateien innerhalb der +Server-Konfigurationsdatei ein
Syntax:Include Dateiname|Verzeichnis
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis
Status:Core
Modul:core
Kompatibilität:Die Platzhalter-Suche ist verfügbar seit +2.0.41
+

Die Direktive erlaubt das Einfügen anderer Konfigurationsdateien + in die Konfigurationsdatei des Servers.

+ +

Shell-typische (fnmatch()) Platzhlaterzeichen können + dazu verwendet werden, mehrere Dateien auf einmal in alphabetischer + Reihenfolge einzufügen. Wenn Include + darüber hinaus auf ein Verzeichnis anstatt auf eine Datei zeigt, + liest der Apache alle Dateien in diesem Verzeichnis und allen + Unterverzeichnissen ein. Das Einfügen ganzer Verzeichnisse ist + jedoch nicht empfehlenswert, da temporäre Dateien sehr leicht + versehentlich in einem Verzeichnis zurückgelassen werden, was + httpd scheitern lassen kann.

+ +

Der angegebene Dateiname kann ein absoluter Pfad sein oder relativ zum + ServerRoot-Verzeichnis angegeben + werden.

+ +

Beispiele:

+ +

+ Include /usr/local/apache2/conf/ssl.conf
+ Include /usr/local/apache2/conf/vhosts/*.conf +

+ +

Oder Sie geben Pfade relativ zu Ihrem ServerRoot-Verzeichnis an:

+ +

+ Include conf/ssl.conf
+ Include conf/vhosts/*.conf +

+ +

Der Aufruf von apachectl configtest liefert eine Liste + der Dateien, die während des Konfigurations-Tests verarbeitet + werden:

+ +

+ root@host# apachectl configtest
+ Processing config file: /usr/local/apache2/conf/ssl.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost1.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost2.conf
+ Syntax OK +

+ +

Siehe auch

+ +
+
top
+

KeepAlive-Direktive

+ + + + + + + +
Beschreibung:Aktiviert persistente HTTP-Verbindungen
Syntax:KeepAlive On|Off
Voreinstellung:KeepAlive On
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

Die Keep-Alive-Erweiterung von HTTP/1.0 und die + HTTP/1.1-Funktionalität persistenter Verbindungen unterstützt + langlebige HTTP-Sitzungen, die es erlauben, mehrere Anfragen über + die gleich TCP-Verbindung zu senden. In einigen Fällen wurde eine + Beschleunigung der Wartezeiten von beinahe 50% für HTML-Dokumente + mit vielen Bildern festgestellt. Um Keep-Alive-Verbindungen zu aktivieren, + setzen Sie KeepAlive On.

+ +

Bei HTTP/1.0-Clients werden Keep-Alive-Verbindungen nur dann verwendet, + wenn sie vom Client eigens angefordert werden. Desweiteren können + Keep-Alive-Verbindungen bei einem HTTP/1.0-Client nur dann verwendet + werden, wenn die Länge des Inhalts im Voraus bekannt ist. Dies + impliziert, dass dynamische Inhalte wie CGI-Ausgaben, SSI-Seiten und + servergenerierte Verzeichnisauflistungen im Allgemeinen keine + Keep-Alive-Verbindungen mit HTTP/1.0-Clients verwenden. Bei + HTTP/1.1-Clients sind Keep-Alive-Verbindungen Voreinstellung, solange + nichts anderes angegeben ist. Wenn der Client es anfordert, wird + Chunked-Encoding verwendet, um Inhalte mit unbekannter Länge + über persistente Verbindungen zu senden.

+ +

Siehe auch

+ +
+
top
+

KeepAliveTimeout-Direktive

+ + + + + + + +
Beschreibung:Zeitspanne, die der Server während persistenter Verbindungen +auf nachfolgende Anfragen wartet
Syntax:KeepAliveTimeout Sekunden
Voreinstellung:KeepAliveTimeout 5
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

Dies legt die Anzahl der Sekunden fest, die der Apache auf weitere + Anfragen wartet, bevor er die Verbindung schließt. Nachdem einmal + eine Anfrage entgegen genommen wurde, wird die durch die Direktive + Timeout festgelegte Auszeit + angewendet.

+ +

Auf stark belasteten Servern kann ein hoher + KeepAliveTimeout-Wert zu Durchsatzminderungen + führen. Je höher die Auszeit angegeben ist, desto länger + ist der Apache damit beschäftigt, auf untätige Clients zu + warten.

+ +
+
top
+

<Limit>-Direktive

+ + + + + + + +
Beschreibung:Beschränkt die eingeschlossenen Zugriffskontrollen auf +bestimmte HTTP-Methoden
Syntax:<Limit Methode [Methode] ... > ... + </Limit>
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Zugriffskontrollen gelten normalerweise für alle + Zugriffsmethoden, was normalerweise auch das gewünschte Verhalten ist. + Im Allgemeinen sollten Zugriffskontrollen nicht in einen + <Limit>-Container gepackt + werden.

+ +

Der Sinn der Direktive <Limit> + ist es, den Effekt der Zugriffskontrollen auf die angegebenen + HTTP-Methoden zu beschränken. Bei allen anderen Methoden haben + die in der <Limit>-Gruppe + enthaltenen Zugriffsbeschränkungen keine Wirkung. + Im folgenden Beispiel gilt die Zugriffskontrolle nur für die + Methoden POST, PUT und DELETE. + Alle anderen Methoden bleiben ungeschützt:

+ +

+ <Limit POST PUT DELETE>
+ + Require valid-user
+ + </Limit> +

+ +

Sie können eine oder mehrere der folgenden Methoden angeben: + GET, POST, PUT, DELETE, + CONNECT, OPTIONS, + PATCH, PROPFIND, PROPPATCH, + MKCOL, COPY, MOVE, + LOCK und UNLOCK. Die Methodennamen + unterscheiden zwischen Groß- und Kleinschreibung. Wenn + GET verwendet wird, sind HEAD-Anfragen + ebenfalls eingeschränkt. Die TRACE-Methode kann nicht + limitiert werden.

+ +
+ Wenn es um Zugriffsbeschränkungen geht, sollte + ein <LimitExcept>-Container sollte immmer einem <Limit>-Container vorgezogen + werden, da <LimitExcept> + einen Schutz gegen beliebige Methoden bietet. +
+ +
+
top
+

<LimitExcept>-Direktive

+ + + + + + + +
Beschreibung:Beschränkt Zugriffskontrollen auf alle HTTP-Methoden +außer den genannten
Syntax:<LimitExcept Methode [Methode] ... > ... + </LimitExcept>
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

<LimitExcept> und + </LimitExcept> werden dazu verwendet, eine Gruppe + von Anweisungen zur Zugriffskontrolle zusammenzufassen, die dann auf + jede HTTP-Methode angewendet werden, die nicht + als Argument angegeben ist. D.h. dies ist das Gegenteil des + <Limit>-Containers + und kann zur Steuerung von Standard- und nicht-Standard-/unbekannten + Methoden verwendet werden. Für weitere Einzelheiten lesen Sie bitte + die Beschreibung zu <Limit>.

+ +

Beispiel:

+ +

+ <LimitExcept POST GET>
+ + Require valid-user
+ + </LimitExcept> +

+ + +
+
top
+

LimitInternalRecursion-Direktive

+ + + + + + + + +
Beschreibung:Bestimmt die maximale Anzahl interner Umleitungen und + verschachtelter Unteranfragen
Syntax:LimitInternalRecursion Zahl [Zahl]
Voreinstellung:LimitInternalRecursion 10
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
Kompatibilität:Verfügbar ab Apache 2.0.47
+

Eine interne Umleitung erfolgt beispielsweise, wenn die Direktive + Action verwendet wird, welche + die Originalanfrage intern zu einem CGI-Skript weiterleitet. Eine + Unteranfrage (Anm.d.Ü.: engl. Subrequest) ist ein Mechanismus des + Apache, um herauszufinden, was bei einer URI geschehen würde, wäre + sie angefordert worden. mod_dir z.B. verwendet + Unteranfragen, um nach den Dateien zu suchen, die in der DirectoryIndex-Anweisung aufgeführt + sind.

+ +

LimitInternalRecursion bewahrt den Server vor + einem Absturz, wenn er in eine Endlosschleife aus internen Umleitungen + oder Unteranfragen hineinläuft. Derartige Schleifen werden + gewöhnlich durch Fehlkonfiguration verursacht.

+ +

Die Direktive setzt zwei verschiedene Begrenzungen, welche je Anfrage + ausgewertet werden. Die erste Zahl bestimmt die maximale + Anzahl der Umleitungen, die aufeinander folgen dürfen. Die zweite + Zahl legt fest, wie tief Unteranfragen ineinander + verschachtelt werden dürfen. Wenn Sie lediglich eine Zahl + angeben, wird sie beiden Begrenzungen zugewiesen.

+ +

Beispiel

+ LimitInternalRecursion 5 +

+ +
+
top
+

LimitRequestBody-Direktive

+ + + + + + + + +
Beschreibung:Begrenzt die Gesamtgröße des vom Client gesendeten +HTTP-Request-Body
Syntax:LimitRequestBody Bytes
Voreinstellung:LimitRequestBody 0
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Die Direktive gibt die Anzahl der Bytes zwischen 0 + (unbegrenzt) und 2147483647 (2GB) an, die im Request-Body (Datenteil der + Anfrage) erlaubt sind.

+ +

Die Direktive LimitRequestBody erlaubt es dem + Benutzer, die Größe des HTTP-Request-Bodys in dem Kontext zu + begrenzen, in dem die Anweisung angegeben ist (Server, pro Verzeichnis, + pro Datei oder pro Adresse). Wenn die Anfrage des Clients dieses Limit + überschreitet, gibt der Server einen Fehler zurück anstatt die + Anfrage zu bearbeiten. Die Größe des Datenteils einer Anfrage + kann sehr stark variieren, abhängig von der Art der Ressource und + den für diese Ressource erlaubten Methoden. CGI-Skripte verwenden + den Datenteil üblicherweise zum Empfang von Formulardaten. Wird + die PUT-Methode angewendet, dann muss der Wert mindestens + so groß sein wie irgendeine Darstellungsform, die der Server + für diese Ressource akzeptieren soll.

+ +

Die Direktive gibt dem Serveradministrator eine größere + Kontrolle gegenüber abnormalem Verhalten von Clients, was bei der + Vermeidung einiger Formen von Denial-of-Service-Attacken hilfreich + sein kann.

+ +

Wenn Sie beispielsweise das Hochladen von Dateien zu einer bestimmten + Adresse erlauben, aber die Größe der hochgeladenen Dateien + auf 100K beschränken wollen, können Sie die folgende Anweisung + verwenden:

+ +

+ LimitRequestBody 102400 +

+ + +
+
top
+

LimitRequestFields-Direktive

+ + + + + + + +
Beschreibung:Begrenzt die Anzahl der HTTP-Request-Header, die vom Client +entgegengenommen werden
Syntax:LimitRequestFields Anzahl
Voreinstellung:LimitRequestFields 100
Kontext:Serverkonfiguration
Status:Core
Modul:core
+

Anzahl ist ein Integer-Wert (eine positive Ganzzahl) + zwischen 0 (unbegrenzt) und 32767. Die Voreinstellung wird durch die + Konstante DEFAULT_LIMIT_REQUEST_FIELDS (100 + bei der Auslieferung) zur Kompilierungszeit gesetzt.

+ +

Die Direktive LimitRequestFields erlaubt es + dem Serveradministrator, die maximale Anzahl der in einem HTTP-Request + erlaubten HTTP-Request-Header zu verändern. Für den Server + muss dieser Wert größer sein als die Anzahl der Headerzeilen, + die ein normaler Client senden könnte. Die Anzahl der Request-Header, + die ein gewöhnlicher Client verwendet, überschreitet selten 20 + Zeilen. Allerdings kann dies zwischen den verschiedenen + Client-Ausführungen variieren, oft abhängig vom Ausmaß, + mit dem der Anwender die genaue Content-Negotiation-Unterstützung + seines Browsers konfiguriert hat. Optionale HTTP-Erweiterungen + äußern sich oft in Form von HTTP-Headern.

+ +

Die Direktive gibt dem Serveradministrator eine größere + Kontrolle gegenüber abnormalem Verhalten von Clients, was bei der + Vermeidung einiger Formen von Denial-of-Service-Attacken hilfreich + sein kann. Der Wert sollte erhöht werden, wenn normale Clients + eine Fehlermeldung vom Server erhalten, die besagt, dass mit der Anfrage + zu viele Headerzeilen gesendet wurden.

+ +

Beispiel:

+ +

+ LimitRequestFields 50 +

+ + +
+
top
+

LimitRequestFieldSize-Direktive

+ + + + + + + +
Beschreibung:Begrenzt die Länge des vom Client gesendeten +HTTP-Request-Headers
Syntax:LimitRequestFieldsize Bytes
Voreinstellung:LimitRequestFieldsize 8190
Kontext:Serverkonfiguration
Status:Core
Modul:core
+

Die Direktive gibt die Anzahl der Bytes an, die in einem + HTTP-Header erlaubt sind.

+ +

Die Direktive LimitRequestFieldsize erlaubt es + dem Serveradministrator, die maximale Größe eines + HTTP-Request-Headers zu verringern oder erhöhen. Für den Server + muss der Wert groß genug sein, um eine beliebige Headerzeile einer + normalen Client-Anfrage vorzuhalten. Die Größe variiert stark + zwischen den verschiedenen Client-Ausführungen, oft abhängig vom + Ausmaß, mit dem der Anwender die genaue + Content-Negotiation-Unterstützung seines Browsers konfiguriert hat. + SPNEGO-Authentisierungs-Header können bis zu 12392 Bytes lang + sein.

+ +

Die Direktive gibt dem Serveradministrator eine größere + Kontrolle gegenüber abnormalem Verhalten von Clients, was bei der + Vermeidung einiger Formen von Denial-of-Service-Attacken hilfreich + sein kann.

+ +

Beispiel:

+ +

+ LimitRequestFieldSize 4094 +

+ +
Unter normalen Umständen sollte die Voreinstellung nicht + verändert werden.
+ +
+
top
+

LimitRequestLine-Direktive

+ + + + + + + +
Beschreibung:Begrenzt die Länge der vom Client entgegengenommenen +HTTP-Anfragezeile
Syntax:LimitRequestLine Bytes
Voreinstellung:LimitRequestLine 8190
Kontext:Serverkonfiguration
Status:Core
Modul:core
+

Die Direktive legt die Anzahl der Bytes fest, die in der + HTTP-Anfragezeile erlaubt sind.

+ +

Die Direktive LimitRequestLine erlaubt es dem + Serveradministrator, die maximale Größe der + HTTP-Anfragezeile zu verringern oder erhöhen. Da + die Anfragezeile aus der HTTP-Methode, der URI und der Protokollversion + besteht, bedeutet die LimitRequestLine-Direktive + eine Beschränkung der Länge der für eine Anfrage an den + Server erlaubten Anfrage-URI. Für den Server muss der Wert groß + genug sein, um jeden seiner Ressourcennamen vorzuhalten, + einschließlich aller Informationen, die im Query-String einer + GET-Anfrage übergeben werden können.

+ +

Die Direktive gibt dem Serveradministrator eine größere + Kontrolle gegenüber abnormalem Verhalten von Clients, was bei der + Vermeidung einiger Formen von Denial-of-Service-Attacken hilfreich + sein kann.

+ +

Beispiel:

+ +

+ LimitRequestLine 4094 +

+ +
Unter normalen Umständen sollte die Voreinstellung nicht + verändert werden.
+ +
+
top
+

LimitXMLRequestBody-Direktive

+ + + + + + + + +
Beschreibung:Begrenzt die Größe eines XML-basierten +Request-Bodys
Syntax:LimitXMLRequestBody Bytes
Voreinstellung:LimitXMLRequestBody 1000000
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Dies gibt die Grenze für die maximale Größe (in Bytes) + des XML-basierten Request-Bodys an. Der Wert 0 deaktiviert + diese Prüfung.

+ +

Beispiel:

+ +

+ LimitXMLRequestBody 0 +

+ + +
+
top
+

<Location>-Direktive

+ + + + + + +
Beschreibung:Wendet die enthaltenen Direktiven nur auf die entsprechenden +URLs an
Syntax:<Location + URL-Pfad|URL> ... </Location>
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

Die Direktive <Location> + begrenzt die Reichweite der enthaltenen Anweisungen auf URLs. + Sie ist der Direktive <Directory> ähnlich und startet einen + Abschnitt, der mit der Anweisung </Location> + abgeschlossen wird. <Location>-Container werden, nachdem die + <Directory>-Container + und .htaccess-Dateien gelesen wurden, und nach den + <Files>-Containern, in + der Reihenfolge ausgeführt, in der sie in der Konfigurationsdatei + erscheinen.

+ +

<Location>-Abschnitte operieren + vollständig außerhalb des Dateisystems. Dies hat mehrere + Konsequenzen. An Wichtigsten, <Location>-Anweisungen sollten nicht dafür + verwendet werden, den Zugriff zu Teilen des Dateisystems zu steuern. Da + mehrere unterschiedliche URLs auf die gleiche Stelle des Dateisystems + zeigen können, könnte eine solche Zugriffskontrolle u.U. + umgangen werden.

+ +

Wann sollte<Location> verwendet werden

+ +

Verwenden Sie <Location>, um + Anweisungen auf Inhalte anzuwenden, die außerhalb des Dateisystems + abgelegt sind. Benutzen Sie <Directory> und <Files> für Inhalte, die + innerhalb des Dateisystems abgelegt sind. Eine Ausnahme bildet + <Location />, welches ein einfacher Weg ist, um eine + Konfiguration auf den gesamten Server anzuwenden.

+
+ +

Für alle nicht-Proxy-Anfragen ist die entsprechende URL + ein URL-Pfad in der Form /path/. Es dürfen weder ein + Schema, noch ein Hostname, noch ein Port, noch ein Query-String einbezogen + werden. Für Proxy-Anfragen hat die Vergleichs-URL die Form + schema://servername/path. Das Präfix muss angegeben + werden.

+ +

Die URL kann Platzhalter verwenden. In einer Zeichenfolge mit + Platzhaltern entspricht ? einem einzelnen Zeichen und + *einer beliebigen Zeichenfolge.

+ +

Erweiterte reguläre Ausdrücke können ebenfalls + verwendet werden, indem das Zeichen ~ hinzugefügt + wird. Beispielsweise würde

+ +

+ <Location ~ "/(extra|special)/data"> +

+ +

auf URLs passen, welche die Zeichenfolge /extra/data + oder /special/data enthalten. Die Direktive <LocationMatch> verhält sich + genauso wie <Location> mit + regulären Ausdrücken.

+ +

Die Funktionalität von <Location> ist insbesondere dann nützlich, + wenn sie mit der SetHandler-Direktive + kombiniert wird. Um zum Beispiel Statusabfragen zu aktivieren, sie aber + nur von Browsern aus foo.com zuzulassen, könnten Sie + schreiben:

+ +

+ <Location /status>
+ + SetHandler server-status
+ Order Deny,Allow
+ Deny from all
+ Allow from .foo.com
+ + </Location> +

+ +

Anmerkung zu / (Schrägstrich, Slash)

+

Das Slash-Zeichen hat eine besondere Bedeutung, je nachdem, wo es + in der URL erscheint. Manche werden sein Verhalten vom Dateisystem + gewohnt sein, wo mehrere aufeinanderfolgende Schrägstriche + häufig zu einem Schrägstrich zusammengefaßt werden + (d.h. /home///foo ist das gleiche wie + /home/foo). Im URL-Raum ist dies nicht notwendigerweise + genauso. Bei der Direktive <LocationMatch> und der <Location>-Version mit regulären Ausdrücken + müssen Sie explizit mehrere Schrägstriche angeben, wenn Sie + genau dies beabsichtigen.

+ +

Beispielsweise würde <LocationMatch ^/abc> + auf die angeforderte URL /abc passen, nicht aber auf + //abc. Die Direktive <Location> (ohne reguläre Ausdrücke) verhält + sich ähnlich, wenn sie für Proxy-Anfragen verwendet wird. + Wenn <Location> (ohne + reguläre Ausdrücke) jedoch für nicht-Proxy-Anfragen + verwendet wird, werden stillscheigend mehrere Schrächstriche mit + mit einem einzigen Schrägstrich gleichgesetzt. Geben Sie + beispielsweise <Location /abc/def> an und die + Anfrage lautet auf /abc//def, dann greift die Anweisung.

+
+ +

Siehe auch

+ +
+
top
+

<LocationMatch>-Direktive

+ + + + + + +
Beschreibung:Wendet die enthaltenen Direktiven nur auf URLs an, die auf +reguläre Ausdrücke passen
Syntax:<LocationMatch + regex> ... </LocationMatch>
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

Die Direktive <LocationMatch> + begrenzt die Reichweite der enthaltenen Anweisungen in der gleichen Weise + wie <Location> auf URLs. + Sie verwendet jedoch reguläre Ausdrücke als Argument anstelle + einer einfachen Zeichenkette. Beispielsweise würde

+ +

+ <LocationMatch "/(extra|special)/data"> +

+ +

auf URLs passen, welche die Zeichenfolge /extra/data + oder /special/data enthalten.

+ +

Siehe auch

+ +
+
top
+

LogLevel-Direktive

+ + + + + + + +
Beschreibung:Steuert die Ausführlichkeit des Fehlerprotokolls
Syntax:LogLevel Level
Voreinstellung:LogLevel warn
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

LogLevel stellt die Ausführlichkeit + der Nachrichten ein, die im Fehlerprotokoll aufgezeichnet werden (siehe + Direktive ErrorLog). Die folgenden, + nach absteigender Aussagekraft sortierten Level sind + verfügbar:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Level Beschreibung Beispiel
emerg Notfall - das System ist unbenutzbar."Child cannot open lock file. Exiting" + (Anm.d.Ü.: "Kindprozess kann die Lock-Datei nicht öffnen. + Beende Programm")
alert Maßnahmen müssen unverzüglich ergriffen + werden."getpwuid: couldn't determine user name from uid" + (Anm.d.Ü.: "getpwuid: kann keinen Benutzernamen aus der UID + ermitteln")
crit Kritischer Zustand."socket: Failed to get a socket, exiting child" + (Anm.d.Ü.: "socket: Socket-Zuweisung fehlgeschlagen, beende + Kindprozess")
error Fehlerbedingung."Premature end of script headers" + (Anm.d.Ü.: "Vorzeitiges Ende der Skript-Header")
warn Warnung."child process 1234 did not exit, sending another SIGHUP" + (Anm.d.Ü.: "Kindprozess 1234 nicht beendet, sende ein weiteres + SIGHUP")
notice Normaler, aber signifikanter Zustand."httpd: caught SIGBUS, attempting to dump core in ..." + (Anm.d.Ü.: "httpd: SIGBUS empfangen, versuche Speicherabbild nach ... + zu schreiben")
info Information."Server seems busy, (you may need to increase + StartServers, or Min/MaxSpareServers)..." + (Anm.d.Ü.: "Server scheint beschäftigt zu sein, + (möglicherweise müssen Sie StartServers oder + Min/MaxSpareServers erhöhen)")
debug Debug-Level-Nachrichten"Opening config file ..." + (Anm.d.Ü.: "Öffne Konfigurationsdatei ...")
+ +

Geben Sie einen bestimmten Level an, denn werden Nachrichten von + allen höheren Leveln ebenso angezeigt. Z.B.: Wenn + LogLevel info eingestellt ist, dann werden Nachrichten der + Log-Level notice und warn ebenso eingetragen.

+ +

Es wird empfohlen, mindestens den Level crit zu + verwenden.

+ +

Beispiel:

+ +

+ LogLevel notice +

+ +

Hinweis

+

Beim Protokollieren in eine reguläre Datei können + Nachrichten des Levels notice nicht unterdrückt + werden und werden daher immer protokolliert. Dies trifft allerdings + nicht zu, wenn mittels syslog protokolliert wird.

+
+ +
+
top
+

MaxKeepAliveRequests-Direktive

+ + + + + + + +
Beschreibung:Anzahl der Anfragen, die bei einer persistenten Verbindung +zulässig sind
Syntax:MaxKeepAliveRequests Anzahl
Voreinstellung:MaxKeepAliveRequests 100
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

Die Direktive MaxKeepAliveRequests + begrenzt die Anzahl der Anfragen, die pro Verbindung zulässig sind, + wenn KeepAlive eingeschaltet ist. + Bei der Einstellung 0 sind unbegrenzt viele Anfragen + erlaubt. Wir empfehlen für diese Einstellung einen hohen Wert + für eine maximale Serverleistung.

+ +

Beispiel:

+ +

+ MaxKeepAliveRequests 500 +

+ +
+
top
+

NameVirtualHost-Direktive

+ + + + + + +
Beschreibung:Bestimmt eine IP-Adresse für den Betrieb namensbasierter +virtueller Hosts
Syntax:NameVirtualHost Adresse[:Port]
Kontext:Serverkonfiguration
Status:Core
Modul:core
+

Die Direktive NameVirtualHost ist erforderlich, + wenn Sie namensbasierte virtuelle Hosts + konfigurieren möchten.

+ +

Obwohl Adresse eine Hostname sein kann, wird empfohlen, + dass Sie stets eine IP-Adresse verwenden, z.B.:

+ +

+ NameVirtualHost 111.22.33.44 +

+ +

Mit der NameVirtualHost-Anweisung geben Sie + die IP-Adresse an, unter der der Server Anfragen für + namensbasierte virtuelle Hosts entgegennimmt. Das ist üblicherweise + die Adresse, zu der die Namen Ihrer namensbasierten virtuellen Hosts + aufgelöst werden. Falls eine Firewall oder ein anderer Proxy die + Anfrage in Empfang nimmt und Sie zu einer weiteren IP-Adresse des Servers + weiterleitet, müssen Sie die IP-Adresse der physikalischen + Schnittstelle der Maschine angeben, welche die Anfragen bedient. + Wenn Sie mehrere namensbasierte Hosts an verschiedenen Adressen + betreiben, wiederholen Sie einfach die Anweisung für jede + Adresse.

+ +

Anmerkung

+

Beachten Sie, dass der "Hauptserver" und jeder + _default_-Server niemals bei einer + Anfrage an einer NameVirtualHost-IP-Adresse + bedient wird (es sei denn, Sie geben aus irgendwelchen Gründen + NameVirtualHost an, definieren dann aber keine + VirtualHosts für diese Adresse).

+
+ +

Optional können Sie die Nummer eines Ports angeben, an dem + namensbasierte virtuelle Hosts verwendet werden sollen. Beispiel:

+ +

+ NameVirtualHost 111.22.33.44:8080 +

+ +

IPv6-Adressen müssen, wie im folgenden Beispiel angegeben, in + eckige Klammern eingeschlossen werden:

+ +

+ NameVirtualHost [2001:db8::a00:20ff:fea7:ccea]:8080 +

+ +

Um an allen Schnittstellen Anfragen zu empfangen, können Sie + * als Argument verwenden.

+ +

+ NameVirtualHost * +

+ +

Argument der Direktive <VirtualHost>

+

Beachten Sie, dass das Argument der <VirtualHost>-Anweisung exakt auf das Argument + der NameVirtualHost-Anweisung passen muss.

+ +

+ NameVirtualHost 1.2.3.4
+ <VirtualHost 1.2.3.4>
+ # ...
+ </VirtualHost>
+

+
+ +

Siehe auch

+ +
+
top
+

Options-Direktive

+ + + + + + + + +
Beschreibung:Definiert, welche Eigenschaften oder Funktionen in einem +bestimmten Verzeichnis verfügbar sind
Syntax:Options + [+|-]Option [[+|-]Option] ...
Voreinstellung:Options All
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:Options
Status:Core
Modul:core
+

Die Direktive Options steuert, welche + Eigenschaften bzw. Funktionen in einem bestimmten Verzeichnis + verfügbar sind.

+ +

Option kann auf None gesetzt werden, wobei + keine der besonderen Eigenschaften verfügbar sind, oder auf eines + oder mehrere der folgenden:

+ +
+
All
+ +
Alle Optionen außer MultiViews. Dies ist + die Voreinstellung.
+ +
ExecCGI
+ +
Die Ausführung von CGI-Skripten, welche mod_cgi + verwenden, ist erlaubt.
+ +
FollowSymLinks
+ +
Der Server folgt symbolischen Links in diesem Verzeichnis. +
+

Auch wenn der Server symbolischen Links folgt, bedeutet dies + nicht, dass der zum Abgleich gegen <Directory>-Abschnitte verwendete Pfadname + wechselt.

+

Beachten Sie auch, dass diese Option innerhalb eines + <Location>-Abschnitts + ignoriert wird.

+
+ +
Includes
+ +
+ Server Side Includes, die von mod_include bereitgestellt + werden, sind erlaubt.
+ +
IncludesNOEXEC
+ +
Server Side Includes sind erlaubt, #exec cmd + und #exec cgi sind jedoch deaktiviert. Es ist aber noch + möglich, CGI-Skripte aus + ScriptAlias-Verzeichnissen mittels + #include virtual einzubinden.
+ +
Indexes
+ +
Wenn eine URL, die auf ein Verzeichnis zeigt, in dem sich keine durch + DirectoryIndex definierte + Indexdatei (z.B. index.html) befindet, dann liefert + mod_autoindex eine formatierte Auflistung des + Verzeichnisses zurück.
+ +
MultiViews
+ +
"MultiViews" sind bei der Verwendung von + mod_negotiation erlaubt (siehe Content-Negotiation).
+ +
SymLinksIfOwnerMatch
+ +
Der Server folgt nur symbolischen Links, bei denen die Zieldatei + bzw. das Zielverzeichnis der gleichen Benutzerkennung gehört, wie + der Link. +

Anmerkung

Diese Option wird innerhalb eines + <Location>-Abschnitts + ignoriert.
+
+ +

Wenn mehrere Options auf ein Verzeichnis + angewandt werden können, dann wird normalerweise die + spezifischste (Anm.d.Ü.: Gemeint ist die zuletzt + ausgeführte Option.) verwendet und alle anderen werden + ignoriert; die Optionen werden nicht vermischt. (Siehe auch Wie Abschnitte zusammengeführt + werden..) Wenn jedoch allen Optionen der + Options-Anweisung eines der Zeichen + + oder - vorangestellt wird, werden die Optionen + zusammengemischt. Jede Option mit vorangestelltem + wird + zu den momentan gültigen Optionen hinzugefügt und jede Option + mit vorangestelltem - wird aus den derzeit gültigen + Optionen entfernt.

+ +

So wird zum Beispiel ohne die Zeichen + und + -

+ +

+ <Directory /web/docs>
+ + Options Indexes FollowSymLinks
+ + </Directory>
+
+ <Directory /web/docs/spec>
+ + Options Includes
+ + </Directory> +

+ +

für das Verzeichnis /web/docs/spec wird jetzt + lediglich Includes gesetzt. Wenn die zweite + Options-Anweisung jedoch +- + und --Zeichen verwenden würde,

+ +

+ <Directory /web/docs>
+ + Options Indexes FollowSymLinks
+ + </Directory>
+
+ <Directory /web/docs/spec>
+ + Options +Includes -Indexes
+ + </Directory> +

+ +

dann würden die Optionen FollowSymLinks und + Includes für das Verzeichnis /web/docs/spec + gesetzt.

+ +

Anmerkung

+

Die Verwendung von -IncludesNOEXEC oder + -Includes deaktiviert Server Side Includes unabhängig + von der vorigen Einstellung vollständig.

+
+ +

Die Voreinstellung ist All, sofern keine anderen Angaben + gemacht wurden.

+ +
+
top
+

Require-Direktive

+ + + + + + + +
Beschreibung:Wählt die authentisierten Benutzer aus, die auf eine +Ressource zugreifen können
Syntax:Require Name [Name] ...
Kontext:Verzeichnis, .htaccess
AllowOverride:AuthConfig
Status:Core
Modul:core
+

Die Direktive wählt aus, welche authentisierten Benutzer auf eine + Ressource zugreifen dürfen. Folgende Syntax ist erlaubt:

+ +
+
Require user User-ID [User-ID] + ...
+
Nur die genannten Benutzer dürfen auf die Ressource + zugreifen.
+ +
Require group Gruppenname [Gruppenname] + ...
+
Nur Benutzer der genannten Gruppen dürfen auf die + Ressource zugreifen.
+ +
Require valid-user
+
Alle gültigen Benutzer dürfen auf die Ressource + zugreifen.
+
+ +

Require muss von den Direktiven + AuthName und AuthType sowie Direktiven wie + AuthUserFile + und AuthGroupFile + (zur Definition von Benutzern und Gruppen) begleitet werden, um + korrekt zu funktionieren. Beispiel:

+ +

+ AuthType Basic
+ AuthName "Geschützte Ressource"
+ AuthUserFile /web/users
+ AuthGroupFile /web/groups
+ Require group admin +

+ +

Zugriffskontrollen, die in dieser Form angewandt werden, gelten + für alle Methoden. Dies ist normalerweise + gewünscht. Wenn Sie Zugriffskontrollen nur auf bestimmte + Methoden anwenden möchten, während andere Methoden + ungeschützt bleiben, dann müssen Sie die + Require-Anweisung innerhalb eines + <Limit>-Abschnitts + platzieren.

+ +

Siehe auch

+ +
+
top
+

RLimitCPU-Direktive

+ + + + + + + + +
Beschreibung:Begrenzt den CPU-Verbrauch von Prozessen, die von +Apache-Kindprozessen gestartet wurden
Syntax:RLimitCPU Sekunden|max [Sekunden|max]
Voreinstellung:unbestimmt; verwendet die Voreinstellung des Systems
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Akzeptiert einen oder zwei Parameter. Der erste Paramater setzt eine + weiche Ressourcenbegrenzung für alle Prozesse, der zweite Parameter + setzt die Maximalgrenze für die Ressourcennutzung. Jeder der + Parameter kann eine Zahl oder max sein. max + zeigt dem Server an, dass das vom Betriebssystem erlaubte Maximum + verwendet werden soll. Das Anheben der maximal erlaubten Ressourcennutzung + erfordert, dass der Server als root läuft, zumindest in + der anfänglichen Startphase.

+ +

Dies wird auf Prozesse angewendet, die von Anfragen bearbeitenden + Apache-Kindprozessen abgespalten werden, nicht auf die + Apache-Kindprozesse selbst. Das beinhaltet CGI-Skripte und + SSI-exec-Befehle, nicht jedoch Prozesse, die vom Apache-Elternprozess + abgespalten werden, wie z.B. Protokollierung.

+ +

CPU-Ressourcenbegrenzung wird in Sekunden pro Prozess + ausgedrückt.

+ +

Siehe auch

+ +
+
top
+

RLimitMEM-Direktive

+ + + + + + + + +
Beschreibung:Begrenzt den Speicherverbrauch von Prozessen, die von +Apache-Kindprozessen gestartet wurden
Syntax:RLimitMEM Bytes|max [Bytes|max]
Voreinstellung:unbestimmt; verwendet die Voreinstellung des Systems
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Akzeptiert einen oder zwei Parameter. Der erste Paramater setzt eine + weiche Ressourcenbegrenzung für alle Prozesse, der zweite Parameter + setzt die Maximalgrenze für die Ressourcennutzung. Jeder der + Parameter kann eine Zahl oder max sein. max + zeigt dem Server an, dass das vom Betriebssystem erlaubte Maximum + verwendet werden soll. Das Anheben der maximal erlaubten Ressourcennutzung + erfordert, dass der Server als root läuft, zumindest in + der anfänglichen Startphase.

+ +

Dies wird auf Prozesse angewendet, die von Anfragen bearbeitenden + Apache-Kindprozessen abgespalten werden, nicht auf die + Apache-Kindprozesse selbst. Das beinhaltet CGI-Skripte und + SSI-exec-Befehle, nicht jedoch Prozesse, die vom Apache-Elternprozess + abgespalten werden, wie z.B. Protokollierung.

+ +

Die Begrenzung des Speicherverbrauchs wird in Bytes pro Prozess + ausgedrückt.

+ +

Siehe auch

+ +
+
top
+

RLimitNPROC-Direktive

+ + + + + + + + +
Beschreibung:Begrenzt die Anzahl der Prozesse, die von Prozessen gestartet +werden können, der ihrerseits von Apache-Kinprozessen gestartet +wurden
Syntax:RLimitNPROC Zahl|max [Zahl|max]
Voreinstellung:unbestimmt; verwendet die Voreinstellung des Systems
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Akzeptiert einen oder zwei Parameter. Der erste Paramater setzt eine + weiche Ressourcenbegrenzung für alle Prozesse, der zweite Parameter + setzt die Maximalgrenze für die Ressourcennutzung. Jeder der + Parameter kann eine Zahl oder max sein. max + zeigt dem Server an, dass das vom Betriebssystem erlaubte Maximum + verwendet werden soll. Das Anheben der maximal erlaubten Ressourcennutzung + erfordert, dass der Server als root läuft, zumindest in + der anfänglichen Startphase.

+ +

Dies wird auf Prozesse angewendet, die von Anfragen bearbeitenden + Apache-Kindprozessen abgespalten werden, nicht auf die + Apache-Kindprozesse selbst. Dies beinhaltet CGI-Skripte und + SSI-exec-Befehle, nicht jedoch Prozesse, die vom Apache-Elternprozess + abgespalten werden, wie z.B. Protokollierung.

+ +

Prozessbegrenzungen steuern die Anzahl der Prozesse pro Benutzer.

+ +

Anmerkung

+

Wenn CGI-Prozesse nicht unter anderen Benutzerkennungen als der + User-ID des Webservers laufen, dann beschränkt diese Direktive + die Anzahl der Prozesse, die der Server selbst erstellen kann. + Kennzeichen einer solchen Situation sind + cannot fork-Meldungen + (Anm.d.Ü.: kann nicht abspalten) in der + Datei error_log.

+
+ +

Siehe auch

+ +
+
top
+

Satisfy-Direktive

+ + + + + + + + + +
Beschreibung:Zusammenspiel von rechnerbasierter Zugriffskontrolle und +Benutzerauthentisierung
Syntax:Satisfy Any|All
Voreinstellung:Satisfy All
Kontext:Verzeichnis, .htaccess
AllowOverride:AuthConfig
Status:Core
Modul:core
Kompatibilität:Wird seit Version 2.0.51 von <Limit> und <LimitExcept> beeinflusst
+

Verfahrensweise für den Zugriff, falls sowohl Allow als auch Require verwendet werden. Der Parameter kann + entweder All oder Any sein. Die Direktive ist + nur dann nützlich, wenn der Zugriff zu einem bestimmten Bereich + durch Benutzername/Passwort und Clientrechner-Adressen + eingeschränkt ist. In diesem Fall verlangt die Voreinstellung + (All), dass der Client die Adressbeschränkung passiert + und eine gültige Benutzerkennung und ein gültiges + Passwort übermittelt. Mit der Auswahl Any wird dem + Client der Zugriff erlaubt, wenn er entweder die Rechner-Beschänkung + passiert oder einen gültigen Benutzernamen und ein gültiges + Passwort übermittelt. Dies kann verwendet werden, um einen Bereich + mit einem Passwort zu schützen, jedoch Clients von bestimmten + Adressen ohne Abfrage des Passwortes zuzulassen.

+ +

Wenn Sie beispielsweise möchten, dass Personen aus Ihrem + privaten Netzwerk unbechänkten Zugriff zu Teilen Ihres + Webangebots haben, jedoch verlangen, dass Personen außerhalb + Ihres privaten Netzwerks ein Passwort übergeben müssen, + können Sie eine Konfiguration ähnlich der folgenden + verwenden:

+ +

+ Require valid-user
+ Allow from 192.168.1
+ Satisfy Any +

+ +

Seit Version 2.0.51 können + Satisfy-Anweisungen durch <Limit>- und <LimitExcept>-Abschnitte auf bestimmte Methoden + beschränkt werden.

+ +

Siehe auch

+ +
+
top
+

ScriptInterpreterSource-Direktive

+ + + + + + + + + +
Beschreibung:Methode zur Ermittlung des Interpreters von +CGI-Skripten
Syntax:ScriptInterpreterSource Registry|Registry-Strict|Script
Voreinstellung:ScriptInterpreterSource Script
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
Kompatibilität:ausschließlich Win32; +Die Option Registry-Strict ist verfügbar seit Apache +2.0.
+

Die Direktive steuert, wie der Apache den Interpreter zur Ausführung + von CGI-Skripten bestimmt. Die Voreinstellung ist Script. Dies + veranlaßt den Apache, den Interpreter zu verwenden, auf den die + Shebang-Zeile (erste Zeile, beginnt mit #!) im Skript zeigt. + Auf Win32-Systemen sieht diese Zeile üblicherweise so aus:

+ +

+ #!C:/Perl/bin/perl.exe +

+ +

oder, wenn perl im Pfad (Umgebungsvariable PATH) liegt, + einfach:

+ +

+ #!perl +

+ +

Die Einstellung ScriptInterpreterSource Registry + veranlaßt eine Suche in HKEY_CLASSES_ROOT der + Windows-Registrierungsdatenbank und verwendet die Endung der Skript-Datei + (z.B. .pl) als Suchargument. Der durch den Unterschlüssel + Shell\ExecCGI\Command oder, falls dieser nicht existiert, + Shell\Open\Command definierte Befehl wird zum Öffnen der + Skript-Datei verwendet. Wenn der Schlüssel zur Dateiendung oder + beide Unterschlüssel fehlen, dann verwendet der Apache die Option + Script.

+ +

Sicherheit

+

Seien Sie vorsichtig, ScriptInterpreterSource Registry bei + Verzeichnissen zu verwenden, auf die eine ScriptAlias-Anweisung zeigt, denn der + Apache versucht jede Datei innerhalb des Verzeichnisses + auszuführen. Die Einstellung Registry kann + unerwünschte Programmaufrufe bei Dateien verursachen, die + üblicherweise nicht ausgeführt werden. Auf den meisten + Windows-Systemen beispielsweise startet der voreingestellte + Öffnen-Befehl für .htm-Dateien den Microsoft + Internet Explorer, so dass jede HTTP-Anfrage nach einer existierenden + .htm-Datei im Skript-Verzeichnis den Browser im Hintergrund + starten würde. Dies ist eine wirksame Methode, Ihr System binnen + etwa einer Minute zum Absturz zu bringen.

+
+ +

Die seit Apache 2.0 neue Option Registry-Strict + macht das gleiche wie Registry, verwendet jedoch nur den + Unterschlüssel Shell\ExecCGI\Command. Der Schlüssel + ExecCGI ist gewöhnlich nicht voreingestellt. Er muss + manuell eingerichtet werden und schützt Ihr System so for + versehentlichen Programmaufrufen.

+ +
+
top
+

ServerAdmin-Direktive

+ + + + + + +
Beschreibung:E-Mail-Adresse, die der Server in Fehlermeldungen einfügt, +welche an den Client gesendet werden
Syntax:ServerAdmin E-Mail-Adresse|URL
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
+

ServerAdmin legt die Kontaktadresse fest, + die der Server in jede Fehlermeldung einfügt, die er an den + Client zurückschickt. Wenn httpd das übergebene + Argument nicht als URL erkennt, nimmt er an, dess es sich um eine + E-Mail-Adresse handelt und stellt in Hyperlinks + mailto: voran. Es ist jedoch sogar sinnvoll, eine + E-Mail-Adresse zu verwenden, da viele CGI-Skripte davon ausgehen. Wenn Sie + eine URL verwenden möchten, sollten Sie auf einem anderen unter Ihrer + Kontrolle stehenden Server verweisen. Andernfalls können Besucher Sie + im Fehlerfall möglicherweise nicht kontaktieren.

+ +

Es kann sich lohnen, hierfür eine reservierte Adresse + anzugeben, z.B.

+ +

+ ServerAdmin www-admin@foo.example.com +

+ +

da Anwender nicht unbedingt erwähnen, dass sie vom Server + sprechen!

+ +
+
top
+

ServerAlias-Direktive

+ + + + + + +
Beschreibung:Alternativer Name für einen Host, der verwendet wird, wenn +Anfragen einem namensbasierten virtuellen Host zugeordnet werden
Syntax:ServerAlias Hostname [Hostname] ...
Kontext:Virtual Host
Status:Core
Modul:core
+

Die Direktive ServerAlias bestimmt die + alternativen Namen eines Hosts zur Verwendung mit namensbasierten virtuellen Hosts.

+ +

+ <VirtualHost *>
+ ServerName server.domain.com
+ ServerAlias server server2.domain.com server2
+ # ...
+ </VirtualHost> +

+ +

Siehe auch

+ +
+
top
+

ServerName-Direktive

+ + + + + + + +
Beschreibung:Rechnername und Port, die der Server dazu verwendet, sich +selbst zu identifizieren
Syntax:ServerName +voll-qualifizierter-Domainname[:port]
Kontext:Serverkonfiguration, Virtual Host
Status:Core
Modul:core
Kompatibilität:Diese Direktive löst in Version 2.0 die + Funktionalität der Direktive Port aus + Version 1.3 ab.
+

Die Direktive ServerName bestimmt den + Rechnernamen und Port, den der Server dazu verwendet, sich selbst + zu identifizieren. Diese werden bei der Erstellung von Umleitungs-URLs + benötigt. Wenn beispielsweise der Name der Maschine, die den Webserver + beherbergt, simple.example.com lautet, die Maschine jedoch + auch einen DNS-Alias www.example.com besitzt und Sie den + Webserver so identifizieren möchten, sollten Sie die folgende + Anweisung verwenden:

+ +

+ ServerName www.example.com:80 +

+ +

Wenn kein ServerName angegeben wurde, + dann versucht der Server den Rechnernamen mittels eines Reverse-Lookup + herzuleiten. Wenn kein Port in der + ServerName-Anweisung angegeben wurde, dann + verwendet der Server den Port der eingegangenen Anfrage. Für eine + optimale Zuverlässigkeit und Berechenbarkeit sollten Sie einen + eindeutigen Rechnernamen und Port angeben, in dem Sie die Direktive + ServerName verwenden.

+ +

Wenn Sie namensbasierte + virtuelle Hosts verwenden, gibt ServerName + innerhalb eines <VirtualHost>-Abschnitts an, welcher + Hostname im Host:-Header der Anfrage auftauchen muss, + damit sie diesem virtuellen Host zugeordnet wird.

+ +

Lesen Sie bitte die Beschreibung der Direktive UseCanonicalName für Einstellungen, die + bestimmen, ob selbstreferenzierende URLs (z.B. vom Modul + mod_dir) auf den angegebenen Port zeigen oder auf die + Portnummern die in der Anfrage des Clients angegeben ist.

+ +

Siehe auch

+ +
+
top
+

ServerPath-Direktive

+ + + + + + +
Beschreibung:Veralteter URL-Pfad für einen namensbasierten +virtuellen Host, auf den von einem inkompatiblen Browser zugegriffen +wird
Syntax:ServerPath URL-Pfad
Kontext:Virtual Host
Status:Core
Modul:core
+

Die Direktive ServerPath legt den + veralteten (Anm.d.Ü.: Gemeint ist eigentlich "Altlast" aufgrund + antiquierter Clients.) URL-Pfad eines Hosts zur Verwendung mit + namensbasierten virtuellen Hosts fest.

+ +

Siehe auch

+ +
+
top
+

ServerRoot-Direktive

+ + + + + + + +
Beschreibung:Basisverzeichnis der Serverinstallation
Syntax:ServerRoot Verzeichnis
Voreinstellung:ServerRoot /usr/local/apache
Kontext:Serverkonfiguration
Status:Core
Modul:core
+

Die Direktive ServerRoot bestimmt das + Verzeichnis, in dem der Server installiert ist. Üblicherweise + enthält es die Unterverzeichnisse conf/ und + logs/. Relative Pfadangaben anderer Direktiven (wie z.B. + Include oder LoadModule) werden relativ zu diesem + Verzeichnis betrachtet.

+ +

Beispiel

+ ServerRoot /home/httpd +

+ +

Siehe auch

+ +
+
top
+

ServerSignature-Direktive

+ + + + + + + + +
Beschreibung:Konfiguriert die Fußzeile von servergenerierten +Dokumenten
Syntax:ServerSignature On|Off|EMail
Voreinstellung:ServerSignature Off
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:All
Status:Core
Modul:core
+

Die Direktive ServerSignature ermöglicht + die Gestaltung einer unter servergenerierten Dokumenten (z.B. + Fehlerdokumente, FTP-Verzeichnislisten von mod_proxy, + mod_info-Ausgaben, ...) angefügten + Fußzeile. Ein möglicher Grund für die Aktivierung einer + solchen Fußzeile ist, dass der Anwender bei einer Kette von + Proxy-Servern oft keine Möglichkeit hat, zu erkennen, welcher der + verketteten Server gegenwärtig die zurückgegebene Fehlermeldung + produziert hat.

+ +

Die (Vor-)Einstellung Off unterdrückt die + Fußzeile (und ist damit kompatibel zum Verhalten des Apache 1.2 und + früher). Die Einstellung On fügt schlicht eine + Zeile mit der Versionsnummer des Servers und dem Servernamen (ServerName) des bedienenden virtuellen Hosts an. + Die Einstellung EMail erstellt zusätzlich einen + "mailto:"-Verweis zum Serveradministrator (ServerAdmin) des referenzierten Dokuments.

+ +

Ab Version 2.0.44 werden die Details der angegebenen Versionsnummer des + Servers von der Direktive ServerTokens kontrolliert.

+ +

Siehe auch

+ +
+
top
+

ServerTokens-Direktive

+ + + + + + + +
Beschreibung:Konfiguriert den HTTP-Response-Header +Server
Syntax:ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full
Voreinstellung:ServerTokens Full
Kontext:Serverkonfiguration
Status:Core
Modul:core
+

die Direktive steuert, ob der Response-Header Server, + der an den Client zurückgesendet wird, eine Beschreibung des + allgemeinen Betriesbsystemtyps des Servers wie auch Informationen + über einkompilierte Module enthält.

+ +
+
ServerTokens Prod[uctOnly]
+ +
Der Server sendet (z.B.): Server: + Apache
+ +
ServerTokens Major
+ +
Der Server sendet (z.B.): Server: + Apache/2
+ +
ServerTokens Minor
+ +
Der Server sendet (z.B.): Server: + Apache/2.0
+ +
ServerTokens Min[imal]
+ +
Der Server sendet (z.B.): Server: + Apache/2.0.41
+ +
ServerTokens OS
+ +
Der Server sendet (z.B.): Server: Apache/2.0.41 + (Unix)
+ +
ServerTokens Full (oder nicht angegeben)
+ +
Der Server sendet (z.B.): Server: Apache/2.0.41 + (Unix) PHP/4.2.2 MyMod/1.2
+
+ +

Diese Einstellung gilt für den gesamten Server und kann nicht + auf Virtual-Host-Basis aktiviert oder deaktiviert werden.

+ +

Ab Version 2.0.44 steuert diese Direktive auch die Informationen, die + durch die Direktive ServerSignature + angeboten werden.

+ +

Siehe auch

+ +
+
top
+

SetHandler-Direktive

+ + + + + + + + +
Beschreibung:Erzwingt die Verarbeitung aller passenden Dateien durch +einen Handler
Syntax:SetHandler Handlername|None
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
Kompatibilität:Seit Apache 2.0 im Core
+

Wenn die Direktive innerhalb einer .htaccess-Datei + oder in einem <Directory>- oder + <Location>-Abschnitt + angegeben wird, erzwingt sie, dass alle entsprechenden Dateien von dem + durch Handlername angegebenen Handler analysiert werden. Wenn Sie + beispielsweise ein Verzeichnis haben, dessen Dateien unabhängig von + der Endung gänzlich als Image-Maps interpretiert werden sollen, + können Sie folgendes in eine .htaccess-Datei in + dem Verzeichnis schreiben:

+ +

+ SetHandler imap-file +

+ +

Noch ein Beispiel: wenn Sie den Server immer, wenn die URL + http://servername/status aufgerufen wird, einen + Statusbericht anzeigen lassen möchten, dann können + Sie folgendes in die httpd.conf schreiben:

+ +

+ <Location /status>
+ + SetHandler server-status
+ + </Location> +

+

Sie können eine zuvor definierte + SetHandler-Anweisung aufheben, indem Sie den Wert + None verwenden.

+ +

Siehe auch

+ +
+
top
+

SetInputFilter-Direktive

+ + + + + + + +
Beschreibung:Bestimmt die Filter, die Client-Anfragen und POST-Eingaben +verarbeiten
Syntax:SetInputFilter Filter[;Filter...]
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
+

Die Direktive SetInputFilter bestimmt den oder + die Filter, die Client-Anfragen und POST-Eingaben verarbeiten, wenn + sie vom Server empfangen werden. Diese gelten zusätzlich zu + anderweitig definierten Filtern, einschließlich denen der Direktive + AddInputFilter.

+ +

Wenn mehr als ein Filter angegeben wird, dann müssen diese + durch Semikolon voneinander getrennt in der Reihenfolge angegeben werden, + in der sie die Daten verarbeiten sollen.

+ +

Siehe auch

+ +
+
top
+

SetOutputFilter-Direktive

+ + + + + + + +
Beschreibung:Bestimmt die Filter, die Antworten des Servers verarbeiten
Syntax:SetOutputFilter Filter[;Filter...]
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Core
Modul:core
+

Die Direktive SetOutputFilter bestimmt + die Filter, die Antworten des Servers verarbeiten, bevor sie an den + Client gesendet werden. Diese gelten zusätzlich zu anderweitig + definierten Filtern, einschließlich denen der Direktive + AddOutputFilter.

+ +

Die folgende Konfiguration verarbeitet zum Beispiel alle Dateien + im Verzeichnis /www/data als Server Side Includes.

+ +

+ <Directory /www/data/>
+ + SetOutputFilter INCLUDES
+ + </Directory> +

+ +

Wenn mehr als ein Filter angegeben wird, dann müssen diese + durch Semikolon voneinander getrennt in der Reihenfolge angegeben werden, + in der sie die Daten verarbeiten sollen.

+ +

Siehe auch

+ +
+
top
+

TimeOut-Direktive

+ + + + + + + +
Beschreibung:Zeitspanne, die der Server auf verschiedene Ereignisse wartet, +bevor er die Anfrage abbricht
Syntax:TimeOut Sekunden
Voreinstellung:TimeOut 300
Kontext:Serverkonfiguration
Status:Core
Modul:core
+

Die Direktive TimeOut definiert derzeit die + Zeitspanne, die der Apache auf drei Dinge wartet:

+ +
    +
  1. Die gesamte Zeispanne, die benötigt wird, um eine GET-Anfrage + zu empfangen.
    2. + +
  2. Die Zeitspanne zwischen dem Empfang von TCP-Paketen einer + POST- oder PUT-Anfrage.
    3. + +
  3. Die Zeitspanne zwischen ACKs bei der Übermittlung der + TCP-Pakete der Antwort.
    4. +
+ +

Wir haben vor, diese Zeitspannen in Zukunft separat konfigurierbar zu + machen. Vor Version 1.2 war der Zeitgeber auf 1200 voreingestellt, wurde + dann aber auf 300 herabgesetzt, was immer noch weit mehr ist, als in den + meisten Situationen benötigt wird. Die Voreinstellung wurde nicht + weiter herabgesetzt, da gelegentlich noch Stellen im Code existieren + können, wo der Zeitgeber nicht zurückgesetzt wird, wenn ein + Paket verschickt wird.

+ +
+
top
+

UseCanonicalName-Direktive

+ + + + + + + +
Beschreibung:Bestimmt, wie der Server seinen eigenen Namen und Port +ermittelt
Syntax:UseCanonicalName On|Off|DNS
Voreinstellung:UseCanonicalName Off
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis
Status:Core
Modul:core
+

In vielen Situationen muss der Apache eine + selbstreferenzierende URL -- d.h. eine URL, die auf den selben + Server zurück verweist -- zusammenbauen. Bei UseCanonicalName + On verwendet der Apache den Hostnamen und Port, der in der + ServerName-Anweisung angegeben ist, + um den kanonischen Namen des Servers zu erstellen. Dieser Name wird in + allen selbstreferenzierenden URLs sowie in CGI-Skripten für die + Werte von SERVER_NAME und SERVER_PORT + verwendet.

+ +

Bei UseCanonicalName Off bildet der Apache + selbstreferenzierende URLs, indem er den vom Client übermittelten + Hostnamen und Port verwendet, sofern diese vorhanden sind (andernfalls + wird der kanonische Name, wie oben beschrieben, benutzt). Die Werte + sind die gleichen, die zur Anwendung von namensbasierten virtuellen Hosts + verwendet werden, und sie sind mit den gleichen Clients verfügbar + (Anm.d.Ü.: , die auch in der Lage sind, auf namensbasierte virtuelle Hosts + zuzugreifen, d.h. einen Host-Header mitschicken). + Die CGI-Variablen SERVER_NAME und SERVER_PORT + werden ebenfalls aus den vom Client angeboten Werten erstellt.

+ +

Ein Intranet-Server, auf den Anwender mit kurzen Namen wie + www zugreifen, ist ein Beispiel, wo dies sinnvoll sein kann. + Sie werden bemerken, dass der Apache den Benutzer auf + http://www.domain.com/splat/ umleitet, wenn dieser einen + Kurznamen und eine URL, die einem Verzeichnis entspricht, ohne + abschließenden Schrägstrich eingibt, wie z.B. + http://www/splat. Wenn Sie Authentisierung aktiviert haben, + bewirkt dies, dass der Benutzer sich zweimal identifizieren muss + (einmal für www und noch einmal für + www.domain.com -- lesen Sie für weitere Informationen die + FAQ zu diesem Thema). Wenn UseCanonicalName + jedoch auf Off gesetzt ist, denn wird der Apache zu + http://www/splat/ umleiten.

+ +

Es existiert noch eine dritte Option, UseCanonicalName DNS, + die für den Betrieb von IP-basierten Massen-Virtual-Hosts gedacht ist, + um antiquierte Clients zu unterstützen, die keinen + Host:-Header bereit stellen. Um selbstreferenzierende + URLs zu ermitteln, führt der Apache bei dieser Option ein + Reverse-DNS-Lookup auf die IP-Adresse des Servers aus, zu der der Client + Verbindung aufgenommen hat.

+ +

Warnung

+

Wenn CGI-Skripte Vermutungen aufgrund des Wertes von + SERVER_NAME anstellen, können sie durch diese + Option fehlschlagen. Clients steht es im Wesentlichen frei, einen Wert + für den Hostnamen anzugeben, wie er will. Wenn das + CGI-Skript SERVER_NAME jedoch lediglich dazu verwendet, + selbstreferenzierende URLs zu erstellen, sollte das gerade noch + in Ordnung sein.

+
+ +

Siehe auch

+ +
+
top
+

<VirtualHost>-Direktive

+ + + + + + +
Beschreibung:Enthält Direktiven, die nur auf bestimmte Hostnamen oder +IP-Adressen angewendet werden
Syntax:<VirtualHost + Adresse[:Port] [Adresse[:Port]] + ...> ... </VirtualHost>
Kontext:Serverkonfiguration
Status:Core
Modul:core
+

<VirtualHost> und + </VirtualHost> werden dazu verwendet, eine Gruppe + von Direktiven zusammenzufassen, die nur auf einen bestimmten virtuellen + Host angewendet werden. Jede Direktive, die im Virtual-Host-Kontext + zulässig ist, kann verwendet werden. Wenn der Server eine Anfrage + für ein bestimmtes Dokument eines bestimmten virtuellen Hosts + empfängt, dann benutzt er die im + <VirtualHost>-Container enthaltenen + Konfigurationsanweisungen. Adresse kann sein:

+ +
    +
  • Die IP-Adresse des virtuellen Hosts.
    • + +
  • Ein voll qualifizierter Domainname für die IP-Adresse des + virtuellen Hosts.
    • + +
  • Das Zeichen *, welches nur in Kombination mit + NameVirtualHost * verwendet wird, um allen IP-Adressen + zu entsprechen.
    • + +
  • Die Zeichenkette _default_, die nur mit IP-basierten + virtuellen Hosts verwendet wird, um nicht zugewiesene IP-Adressen + aufzufangen.
    • +
+ +

Beispiel

+ <VirtualHost 10.1.2.3>
+ + ServerAdmin webmaster@host.foo.com
+ DocumentRoot /www/docs/host.foo.com
+ ServerName host.foo.com
+ ErrorLog logs/host.foo.com-error_log
+ TransferLog logs/host.foo.com-access_log
+ + </VirtualHost> +

+ +

IPv6-Adressen müssen in eckigen Klammern angegeben werden, da die + optionale Portnummer sonst nicht erkannt werden kann. Hier ein + IPv6-Beispiel:

+ +

+ <VirtualHost [2001:db8::a00:20ff:fea7:ccea]>
+ + ServerAdmin webmaster@host.example.com
+ DocumentRoot /www/docs/host.example.com
+ ServerName host.example.com
+ ErrorLog logs/host.example.com-error_log
+ TransferLog logs/host.example.com-access_log
+ + </VirtualHost> +

+ +

Jeder virtuelle Host muss einer anderen IP-Adresse, einem anderen Port + oder einem anderen Hostnamen für den Server entsprechen. Im ersten + Fall muss die Servermaschine so eingerichtet sein, dass sie IP-Pakete + für mehrere Adressen akzeptiert. (Wenn der Rechner nicht mehrere + Netzwerkkarten besitzt, kann dies mit dem Befehl ifconfig + alias durchgeführt werden -- sofern Ihr Betriebssystem das + unterstützt).

+ +

Anmerkung

+

Die Verwendung von <VirtualHost> + beeinflusst nicht, an welchen Adressen der Apache + lauscht. Sie müssen mit Listen sicherstellen, dass der Apache + an der richtigen Adresse lauscht.

+
+ +

Bei der Verwendung IP-basierter virtuellen Hosts kann der spezielle + Name _default_ benutzt werden. In diesem Fall weist + der Apache jede IP-Adresse diesem virtuellen Host zu, die nicht explizit in + einem anderen virtuellen Host angegeben ist. Falls kein virtueller Host + _default_ angegeben ist, wird die "Hauptserver"-Konfiguration, + die aus allen Definitionen außerhalb der Virtual-Host-Abschnitte + besteht, für nicht passende IPs verwendet. (Beachten Sie jedoch, + dass eine IP-Adressen die zu einer NameVirtualHost-Anweisung passt, weder den + "Hauptserver" noch den virtuellen Host _default_ verwendet. + Lesen Sie für weitere Details die Dokumentation zu namensbasierten virtuell Hosts.)

+ +

Sie können einen speziellen :Port angeben, + um den entsprechenden Port zu wechseln. Falls nicht angegeben, wird + er auf den gleichen Port voreingestellt, wie die letzte + Listen-Anweisung des + Hauptservers. Sie können auch :* angeben, um alle + Ports dieser Adresse zu akzeptieren. (Dies wird zusammen mit + _default_ empfohlen.)

+ +

Sicherheit

+

Lesen Sie das Dokument Sicherheitshinweise für + Details, warum Ihre Sicherheit gefährdet sein kann, wenn das + Verzeichnis, in dem Protokolldateien gespeichert werden, für + jemanden anderes als den Benutzer beschreibbar ist, der den Server + gestartet hat.

+
+ +

Siehe auch

+ +
+
+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en new file mode 100644 index 00000000..3f832a6f --- /dev/null +++ b/docs/manual/mod/core.html.en @@ -0,0 +1,3389 @@ + + + +core - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Core Features

+
+

Available Languages:  de  | + en  | + ja 

+
+ +
Description:Core Apache HTTP Server features that are always +available
Status:Core
+
+ + +
top
+

AcceptFilter Directive

+ + + + + + + +
Description:Configures optimizations for a Protocol's Listener Sockets
Syntax:AcceptFilter protocol accept_filter
Context:server config
Status:Core
Module:core
Compatibility:Available in Apache 2.1.5 and later
+

This directive enables operating system specific optimizations for a + listening socket by the Protocol type. The basic premise is for the + kernel to not send a socket to the server process until either data + is received or an entire HTTP Request is buffered. Only + + FreeBSD's Accept Filters and Linux's more primitive + TCP_DEFER_ACCEPT are currently supported.

+ +

The default values on FreeBSD are:

+

+ AcceptFilter http httpready
+ AcceptFilter https dataready +

+ +

The httpready accept filter buffers entire HTTP requests at + the kernel level. Once an entire request is recieved, the kernel then + sends it to the server. See the + + accf_http(9) man page for more details. Since HTTPS requests are + encrypted only the + accf_data(9) filter is used.

+ +

The default values on Linux are:

+

+ AcceptFilter http data
+ AcceptFilter https data +

+ +

Linux's TCP_DEFER_ACCEPT does not support buffering http + requests. Any value besides none will enable + TCP_DEFER_ACCEPT on that listener. For more details + see the Linux + + tcp(7) man page.

+ +

Using none for an argument will disable any accept filters + for that protocol. This is useful for protocols that require a server + send data first, such as nntp:

+

AcceptFilter nttp none

+ + +
+
top
+

AcceptPathInfo Directive

+ + + + + + + + + +
Description:Resources accept trailing pathname information
Syntax:AcceptPathInfo On|Off|Default
Default:AcceptPathInfo Default
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
Compatibility:Available in Apache 2.0.30 and later
+ +

This directive controls whether requests that contain trailing + pathname information that follows an actual filename (or + non-existent file in an existing directory) will be accepted or + rejected. The trailing pathname information can be made + available to scripts in the PATH_INFO environment + variable.

+ +

For example, assume the location /test/ points to + a directory that contains only the single file + here.html. Then requests for + /test/here.html/more and + /test/nothere.html/more both collect + /more as PATH_INFO.

+ +

The three possible arguments for the + AcceptPathInfo directive are:

+
+
Off
A request will only be accepted if it + maps to a literal path that exists. Therefore a request with + trailing pathname information after the true filename such as + /test/here.html/more in the above example will return + a 404 NOT FOUND error.
+ +
On
A request will be accepted if a + leading path component maps to a file that exists. The above + example /test/here.html/more will be accepted if + /test/here.html maps to a valid file.
+ +
Default
The treatment of requests with + trailing pathname information is determined by the handler responsible for the request. + The core handler for normal files defaults to rejecting + PATH_INFO requests. Handlers that serve scripts, such as cgi-script and isapi-handler, generally accept + PATH_INFO by default.
+
+ +

The primary purpose of the AcceptPathInfo + directive is to allow you to override the handler's choice of + accepting or rejecting PATH_INFO. This override is required, + for example, when you use a filter, such + as INCLUDES, to generate content + based on PATH_INFO. The core handler would usually reject + the request, so you can use the following configuration to enable + such a script:

+ +

+ <Files "mypaths.shtml">
+ + Options +Includes
+ SetOutputFilter INCLUDES
+ AcceptPathInfo On
+ + </Files> +

+ + +
+
top
+

AccessFileName Directive

+ + + + + + + +
Description:Name of the distributed configuration file
Syntax:AccessFileName filename [filename] ...
Default:AccessFileName .htaccess
Context:server config, virtual host
Status:Core
Module:core
+

While processing a request the server looks for + the first existing configuration file from this list of names in + every directory of the path to the document, if distributed + configuration files are enabled for that + directory. For example:

+ +

+ AccessFileName .acl +

+ +

before returning the document + /usr/local/web/index.html, the server will read + /.acl, /usr/.acl, + /usr/local/.acl and /usr/local/web/.acl + for directives, unless they have been disabled with

+ +

+ <Directory />
+ + AllowOverride None
+ + </Directory> +

+ +

See also

+ +
+
top
+

AddDefaultCharset Directive

+ + + + + + + + +
Description:Default charset parameter to be added when a response +content-type is text/plain or text/html
Syntax:AddDefaultCharset On|Off|charset
Default:AddDefaultCharset Off
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
+

This directive specifies a default value for the media type + charset parameter (the name of a character encoding) to be added + to a response if and only if the response's content-type is either + text/plain or text/html. This should override + any charset specified in the body of the response via a META + element, though the exact behavior is often dependent on the user's client + configuration. A setting of AddDefaultCharset Off + disables this functionality. AddDefaultCharset On enables + a default charset of iso-8859-1. Any other value is assumed + to be the charset to be used, which should be one of the + IANA registered + charset values for use in MIME media types. + For example:

+ +

+ AddDefaultCharset utf-8 +

+ +

AddDefaultCharset should only be used when all + of the text resources to which it applies are known to be in that + character encoding and it is too inconvenient to label their charset + individually. One such example is to add the charset parameter + to resources containing generated content, such as legacy CGI + scripts, that might be vulnerable to cross-site scripting attacks + due to user-provided data being included in the output. Note, however, + that a better solution is to just fix (or delete) those scripts, since + setting a default charset does not protect users that have enabled + the "auto-detect character encoding" feature on their browser.

+ +

See also

+ +
+
top
+

AddOutputFilterByType Directive

+ + + + + + + + +
Description:assigns an output filter to a particular MIME-type
Syntax:AddOutputFilterByType filter[;filter...] +MIME-type [MIME-type] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
Compatibility:Available in Apache 2.0.33 and later; deprecated in Apache 2.1 and later
+

This directive activates a particular output filter for a request depending on the + response MIME-type. Because of certain + problems discussed below, this directive is deprecated. The same + functionality is available using mod_filter.

+ +

The following example uses the DEFLATE filter, which + is provided by mod_deflate. It will compress all + output (either static or dynamic) which is labeled as + text/html or text/plain before it is sent + to the client.

+ +

+ AddOutputFilterByType DEFLATE text/html text/plain +

+ +

If you want the content to be processed by more than one filter, their + names have to be separated by semicolons. It's also possible to use one + AddOutputFilterByType directive for each of + these filters.

+ +

The configuration below causes all script output labeled as + text/html to be processed at first by the + INCLUDES filter and then by the DEFLATE + filter.

+ +

+ <Location /cgi-bin/>
+ + Options Includes
+ AddOutputFilterByType INCLUDES;DEFLATE text/html
+ + </Location> +

+ +

Note

+

Enabling filters with AddOutputFilterByType + may fail partially or completely in some cases. For example, no + filters are applied if the MIME-type could not be determined and falls + back to the DefaultType setting, + even if the DefaultType is the + same.

+ +

However, if you want to make sure, that the filters will be + applied, assign the content type to a resource explicitly, for + example with AddType or + ForceType. Setting the + content type within a (non-nph) CGI script is also safe.

+ +

The by-type output filters are never applied on proxy requests.

+
+ +

See also

+ +
+
top
+

AllowEncodedSlashes Directive

+ + + + + + + + +
Description:Determines whether encoded path separators in URLs are allowed to +be passed through
Syntax:AllowEncodedSlashes On|Off
Default:AllowEncodedSlashes Off
Context:server config, virtual host
Status:Core
Module:core
Compatibility:Available in Apache 2.0.46 and later
+

The AllowEncodedSlashes directive allows URLs + which contain encoded path separators (%2F for / + and additionally %5C for \ on according systems) + to be used. Normally such URLs are refused with a 404 (Not found) error.

+ +

Turning AllowEncodedSlashes On is + mostly useful when used in conjunction with PATH_INFO.

+ +

Note

+

Allowing encoded slashes does not imply decoding. + Occurrences of %2F or %5C (only on + according systems) will be left as such in the otherwise decoded URL + string.

+
+ +

See also

+ +
+
top
+

AllowOverride Directive

+ + + + + + + +
Description:Types of directives that are allowed in +.htaccess files
Syntax:AllowOverride All|None|directive-type +[directive-type] ...
Default:AllowOverride All
Context:directory
Status:Core
Module:core
+

When the server finds an .htaccess file (as + specified by AccessFileName) + it needs to know which directives declared in that file can override + earlier configuration directives.

+ +

Only available in <Directory> sections

+ AllowOverride is valid only in + <Directory> + sections specified without regular expressions, not in <Location>, <DirectoryMatch> or + <Files> sections. +
+ +

When this directive is set to None, then + .htaccess files are completely ignored. + In this case, the server will not even attempt to read + .htaccess files in the filesystem.

+ +

When this directive is set to All, then any + directive which has the .htaccess Context is allowed in + .htaccess files.

+ +

The directive-type can be one of the following + groupings of directives.

+ +
+
AuthConfig
+ +
+ + Allow use of the authorization directives (AuthDBMGroupFile, + AuthDBMUserFile, + AuthGroupFile, + AuthName, + AuthType, AuthUserFile, Require, etc.).
+ +
FileInfo
+ +
+ Allow use of the directives controlling document types (DefaultType, ErrorDocument, ForceType, LanguagePriority, + SetHandler, SetInputFilter, SetOutputFilter, and + mod_mime Add* and Remove* + directives, etc.), document meta data (Header, RequestHeader, SetEnvIf, SetEnvIfNoCase, BrowserMatch, CookieExpires, CookieDomain, CookieStyle, CookieTracking, CookieName), + mod_rewrite directives RewriteEngine, RewriteOptions, RewriteBase, RewriteCond, RewriteRule) and + Action from + mod_actions. +
+ +
Indexes
+ +
+ Allow use of the directives controlling directory indexing + (AddDescription, + AddIcon, AddIconByEncoding, + AddIconByType, + DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName, + etc.).
+ +
Limit
+ +
+ Allow use of the directives controlling host access (Allow, Deny and Order).
+ +
Options[=Option,...]
+ +
+ Allow use of the directives controlling specific directory + features (Options and + XBitHack). + An equal sign may be given followed by a comma (but no spaces) + separated lists of options that may be set using the Options command.
+
+ +

Example:

+ +

+ AllowOverride AuthConfig Indexes +

+ +

In the example above all directives that are neither in the group + AuthConfig nor Indexes cause an internal + server error.

+ +

See also

+ +
+
top
+

AuthName Directive

+ + + + + + + +
Description:Authorization realm for use in HTTP +authentication
Syntax:AuthName auth-domain
Context:directory, .htaccess
Override:AuthConfig
Status:Core
Module:core
+

This directive sets the name of the authorization realm for a + directory. This realm is given to the client so that the user + knows which username and password to send. + AuthName takes a single argument; if the + realm name contains spaces, it must be enclosed in quotation + marks. It must be accompanied by AuthType and Require directives, and directives such + as AuthUserFile and + AuthGroupFile to + work.

+ +

For example:

+ +

+ AuthName "Top Secret" +

+ +

The string provided for the AuthName is what will + appear in the password dialog provided by most browsers.

+ +

See also

+ +
+
top
+

AuthType Directive

+ + + + + + + +
Description:Type of user authentication
Syntax:AuthType Basic|Digest
Context:directory, .htaccess
Override:AuthConfig
Status:Core
Module:core
+

This directive selects the type of user authentication for a + directory. The authentication types available are + Basic (implemented by + mod_auth_basic) and Digest + (implemented by mod_auth_digest).

+ +

To implement authentication, you must also use the AuthName and Require directives. In addition, the + server must have an authentication-provider module such as + mod_authn_file and an authorization module such + as mod_authz_user.

+ +

See also

+ +
+
top
+

CGIMapExtension Directive

+ + + + + + + + +
Description:Technique for locating the interpreter for CGI +scripts
Syntax:CGIMapExtension cgi-path .extension
Context:directory, .htaccess
Override:FileInfo
Status:Core
Module:core
Compatibility:NetWare only
+

This directive is used to control how Apache finds the + interpreter used to run CGI scripts. For example, setting + CGIMapExtension sys:\foo.nlm .foo will + cause all CGI script files with a .foo extension to + be passed to the FOO interpreter.

+ +
+
top
+

ContentDigest Directive

+ + + + + + + + +
Description:Enables the generation of Content-MD5 HTTP Response +headers
Syntax:ContentDigest On|Off
Default:ContentDigest Off
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Core
Module:core
+

This directive enables the generation of + Content-MD5 headers as defined in RFC1864 + respectively RFC2068.

+ +

MD5 is an algorithm for computing a "message digest" + (sometimes called "fingerprint") of arbitrary-length data, with + a high degree of confidence that any alterations in the data + will be reflected in alterations in the message digest.

+ +

The Content-MD5 header provides an end-to-end + message integrity check (MIC) of the entity-body. A proxy or + client may check this header for detecting accidental + modification of the entity-body in transit. Example header:

+ +

+ Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA== +

+ +

Note that this can cause performance problems on your server + since the message digest is computed on every request (the + values are not cached).

+ +

Content-MD5 is only sent for documents served + by the core, and not by any module. For example, + SSI documents, output from CGI scripts, and byte range responses + do not have this header.

+ +
+
top
+

DefaultType Directive

+ + + + + + + + +
Description:MIME content-type that will be sent if the +server cannot determine a type in any other way
Syntax:DefaultType MIME-type
Default:DefaultType text/plain
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
+

There will be times when the server is asked to provide a + document whose type cannot be determined by its MIME types mappings.

+ +

The server must inform the client of the content-type of the + document, so in the event of an unknown type it uses the + DefaultType. For example:

+ +

+ DefaultType image/gif +

+ +

would be appropriate for a directory which contained many GIF + images with filenames missing the .gif extension.

+ +

Note that unlike ForceType, this directive only + provides the default mime-type. All other mime-type definitions, + including filename extensions, that might identify the media type + will override this default.

+ +
+
top
+

<Directory> Directive

+ + + + + + +
Description:Enclose a group of directives that apply only to the +named file-system directory and sub-directories
Syntax:<Directory directory-path> +... </Directory>
Context:server config, virtual host
Status:Core
Module:core
+

<Directory> and + </Directory> are used to enclose a group of + directives that will apply only to the named directory and + sub-directories of that directory. Any directive that is allowed + in a directory context may be used. Directory-path is + either the full path to a directory, or a wild-card string using + Unix shell-style matching. In a wild-card string, ? matches + any single character, and * matches any sequences of + characters. You may also use [] character ranges. None + of the wildcards match a `/' character, so <Directory + /*/public_html> will not match + /home/user/public_html, but <Directory + /home/*/public_html> will match. Example:

+ +

+ <Directory /usr/local/httpd/htdocs>
+ + Options Indexes FollowSymLinks
+ + </Directory> +

+ +
+

Be careful with the directory-path arguments: + They have to literally match the filesystem path which Apache uses + to access the files. Directives applied to a particular + <Directory> will not apply to files accessed from + that same directory via a different path, such as via different symbolic + links.

+
+ +

Regular + expressions can also be used, with the addition of the + ~ character. For example:

+ +

+ <Directory ~ "^/www/.*/[0-9]{3}"> +

+ +

would match directories in /www/ that consisted of + three numbers.

+ +

If multiple (non-regular expression) <Directory> sections + match the directory (or one of its parents) containing a document, + then the directives are applied in the order of shortest match + first, interspersed with the directives from the .htaccess files. For example, + with

+ +

+ <Directory />
+ + AllowOverride None
+ + </Directory>
+
+ <Directory /home/>
+ + AllowOverride FileInfo
+ + </Directory> +

+ +

for access to the document /home/web/dir/doc.html + the steps are:

+ +
    +
  • Apply directive AllowOverride None + (disabling .htaccess files).
    • + +
  • Apply directive AllowOverride FileInfo (for + directory /home).
    • + +
  • Apply any FileInfo directives in + /home/.htaccess, /home/web/.htaccess and + /home/web/dir/.htaccess in that order.
    • +
+ +

Regular expressions are not considered until after all of the + normal sections have been applied. Then all of the regular + expressions are tested in the order they appeared in the + configuration file. For example, with

+ +

+ <Directory ~ abc$>
+ + # ... directives here ...
+ + </Directory> +

+ +

the regular expression section won't be considered until after + all normal <Directory>s and + .htaccess files have been applied. Then the regular + expression will match on /home/abc/public_html/abc and + the corresponding <Directory> will + be applied.

+ +

Note that the default Apache access for + <Directory /> is Allow from All. + This means that Apache will serve any file mapped from an URL. It is + recommended that you change this with a block such + as

+ +

+ <Directory />
+ + Order Deny,Allow
+ Deny from All
+ + </Directory> +

+ +

and then override this for directories you + want accessible. See the Security Tips page for more + details.

+ +

The directory sections occur in the httpd.conf file. + <Directory> directives + cannot nest, and cannot appear in a <Limit> or <LimitExcept> section.

+ +

See also

+ +
+
top
+

<DirectoryMatch> Directive

+ + + + + + +
Description:Enclose directives that apply to +file-system directories matching a regular expression and their +subdirectories
Syntax:<DirectoryMatch regex> +... </DirectoryMatch>
Context:server config, virtual host
Status:Core
Module:core
+

<DirectoryMatch> and + </DirectoryMatch> are used to enclose a group + of directives which will apply only to the named directory and + sub-directories of that directory, the same as <Directory>. However, it + takes as an argument a regular + expression. For example:

+ +

+ <DirectoryMatch "^/www/(.+/)?[0-9]{3}"> +

+ +

would match directories in /www/ that consisted of three + numbers.

+ +

See also

+ +
+
top
+

DocumentRoot Directive

+ + + + + + + +
Description:Directory that forms the main document tree visible +from the web
Syntax:DocumentRoot directory-path
Default:DocumentRoot /usr/local/apache/htdocs
Context:server config, virtual host
Status:Core
Module:core
+

This directive sets the directory from which httpd + will serve files. Unless matched by a directive like Alias, the server appends the + path from the requested URL to the document root to make the + path to the document. Example:

+ +

+ DocumentRoot /usr/web +

+ +

then an access to + http://www.my.host.com/index.html refers to + /usr/web/index.html. If the directory-path is + not absolute then it is assumed to be relative to the ServerRoot.

+ +

The DocumentRoot should be specified without + a trailing slash.

+ +

See also

+ +
+
top
+

EnableMMAP Directive

+ + + + + + + + +
Description:Use memory-mapping to read files during delivery
Syntax:EnableMMAP On|Off
Default:EnableMMAP On
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
+

This directive controls whether the httpd may use + memory-mapping if it needs to read the contents of a file during + delivery. By default, when the handling of a request requires + access to the data within a file -- for example, when delivering a + server-parsed file using mod_include -- Apache + memory-maps the file if the OS supports it.

+ +

This memory-mapping sometimes yields a performance improvement. + But in some environments, it is better to disable the memory-mapping + to prevent operational problems:

+ +
    +
  • On some multiprocessor systems, memory-mapping can reduce the + performance of the httpd.
    • +
  • With an NFS-mounted DocumentRoot, + the httpd may crash due to a segmentation fault if a file + is deleted or truncated while the httpd has it + memory-mapped.
    • +
+ +

For server configurations that are vulnerable to these problems, + you should disable memory-mapping of delivered files by specifying:

+ +

+ EnableMMAP Off +

+ +

For NFS mounted files, this feature may be disabled explicitly for + the offending files by specifying:

+ +

+ <Directory "/path-to-nfs-files"> + + EnableMMAP Off + + </Directory> +

+ +
+
top
+

EnableSendfile Directive

+ + + + + + + + + +
Description:Use the kernel sendfile support to deliver files to the client
Syntax:EnableSendfile On|Off
Default:EnableSendfile On
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
Compatibility:Available in version 2.0.44 and later
+

This directive controls whether httpd may use the + sendfile support from the kernel to transmit file contents to the client. + By default, when the handling of a request requires no access + to the data within a file -- for example, when delivering a + static file -- Apache uses sendfile to deliver the file contents + without ever reading the file if the OS supports it.

+ +

This sendfile mechanism avoids separate read and send operations, + and buffer allocations. But on some platforms or within some + filesystems, it is better to disable this feature to avoid + operational problems:

+ +
    +
  • Some platforms may have broken sendfile support that the build + system did not detect, especially if the binaries were built on + another box and moved to such a machine with broken sendfile + support.
    • +
  • On Linux the use of sendfile triggers TCP-checksum + offloading bugs on certain networking cards when using IPv6.
    • +
  • On Linux on Itanium, sendfile may be unable to handle files + over 2GB in size.
    • +
  • With a network-mounted DocumentRoot (e.g., NFS or SMB), + the kernel may be unable to serve the network file through + its own cache.
    • +
+ +

For server configurations that are vulnerable to these problems, + you should disable this feature by specifying:

+ +

+ EnableSendfile Off +

+ +

For NFS or SMB mounted files, this feature may be disabled explicitly + for the offending files by specifying:

+ +

+ <Directory "/path-to-nfs-files"> + + EnableSendfile Off + + </Directory> +

+ +
+
top
+

ErrorDocument Directive

+ + + + + + + + +
Description:What the server will return to the client +in case of an error
Syntax:ErrorDocument error-code document
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
Compatibility:Quoting syntax for text messages is different in Apache +2.0
+

In the event of a problem or error, Apache can be configured + to do one of four things,

+ +
    +
  1. output a simple hardcoded error message
    2. + +
  2. output a customized message
    3. + +
  3. redirect to a local URL-path to handle the + problem/error
    4. + +
  4. redirect to an external URL to handle the + problem/error
    5. +
+ +

The first option is the default, while options 2-4 are + configured using the ErrorDocument + directive, which is followed by the HTTP response code and a URL + or a message. Apache will sometimes offer additional information + regarding the problem/error.

+ +

URLs can begin with a slash (/) for local web-paths (relative + to the DocumentRoot), or be a + full URL which the client can resolve. Alternatively, a message + can be provided to be displayed by the browser. Examples:

+ +

+ ErrorDocument 500 http://foo.example.com/cgi-bin/tester
+ ErrorDocument 404 /cgi-bin/bad_urls.pl
+ ErrorDocument 401 /subscription_info.html
+ ErrorDocument 403 "Sorry can't allow you access today" +

+ +

Additionally, the special value default can be used + to specify Apache's simple hardcoded message. While not required + under normal circumstances, default will restore + Apache's simple hardcoded message for configurations that would + otherwise inherit an existing ErrorDocument.

+ +

+ ErrorDocument 404 /cgi-bin/bad_urls.pl

+ <Directory /web/docs>
+ + ErrorDocument 404 default
+ + </Directory> +

+ +

Note that when you specify an ErrorDocument + that points to a remote URL (ie. anything with a method such as + http in front of it), Apache will send a redirect to the + client to tell it where to find the document, even if the + document ends up being on the same server. This has several + implications, the most important being that the client will not + receive the original error status code, but instead will + receive a redirect status code. This in turn can confuse web + robots and other clients which try to determine if a URL is + valid using the status code. In addition, if you use a remote + URL in an ErrorDocument 401, the client will not + know to prompt the user for a password since it will not + receive the 401 status code. Therefore, if you use an + ErrorDocument 401 directive then it must refer to a local + document.

+ +

Microsoft Internet Explorer (MSIE) will by default ignore + server-generated error messages when they are "too small" and substitute + its own "friendly" error messages. The size threshold varies depending on + the type of error, but in general, if you make your error document + greater than 512 bytes, then MSIE will show the server-generated + error rather than masking it. More information is available in + Microsoft Knowledge Base article Q294807.

+ +

Although most error messages can be overriden, there are certain + circumstances where the internal messages are used regardless of the + setting of ErrorDocument. In + particular, if a malformed request is detected, normal request processing + will be immediately halted and the internal error message returned. + This is necessary to guard against security problems caused by + bad requests.

+ +

Prior to version 2.0, messages were indicated by prefixing + them with a single unmatched double quote character.

+ +

See also

+ +
+
top
+

ErrorLog Directive

+ + + + + + + +
Description:Location where the server will log errors
Syntax: ErrorLog file-path|syslog[:facility]
Default:ErrorLog logs/error_log (Unix) ErrorLog logs/error.log (Windows and OS/2)
Context:server config, virtual host
Status:Core
Module:core
+

The ErrorLog directive sets the name of + the file to which the server will log any errors it encounters. If + the file-path is not absolute then it is assumed to be + relative to the ServerRoot.

+ +

Example

+ ErrorLog /var/log/httpd/error_log +

+ +

If the file-path + begins with a pipe (|) then it is assumed to be a command to spawn + to handle the error log.

+ +

Example

+ ErrorLog "|/usr/local/bin/httpd_errors" +

+ +

Using syslog instead of a filename enables logging + via syslogd(8) if the system supports it. The default is to use + syslog facility local7, but you can override this by + using the syslog:facility syntax where + facility can be one of the names usually documented in + syslog(1).

+ +

Example

+ ErrorLog syslog:user +

+ +

SECURITY: See the security tips + document for details on why your security could be compromised + if the directory where log files are stored is writable by + anyone other than the user that starts the server.

+

Note

+

When entering a file path on non-Unix platforms, care should be taken + to make sure that only forward slashed are used even though the platform + may allow the use of back slashes. In general it is a good idea to always + use forward slashes throughout the configuration files.

+
+ +

See also

+ +
+
top
+

FileETag Directive

+ + + + + + + + +
Description:File attributes used to create the ETag +HTTP response header
Syntax:FileETag component ...
Default:FileETag INode MTime Size
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
+

+ The FileETag directive configures the file + attributes that are used to create the ETag (entity + tag) response header field when the document is based on a file. + (The ETag value is used in cache management to save + network bandwidth.) In Apache 1.3.22 and earlier, the + ETag value was always formed + from the file's inode, size, and last-modified time (mtime). The + FileETag directive allows you to choose + which of these -- if any -- should be used. The recognized keywords are: +

+ +
+
INode
+
The file's i-node number will be included in the calculation
+
MTime
+
The date and time the file was last modified will be included
+
Size
+
The number of bytes in the file will be included
+
All
+
All available fields will be used. This is equivalent to: +

FileETag INode MTime Size

+
None
+
If a document is file-based, no ETag field will be + included in the response
+
+ +

The INode, MTime, and Size + keywords may be prefixed with either + or -, + which allow changes to be made to the default setting inherited + from a broader scope. Any keyword appearing without such a prefix + immediately and completely cancels the inherited setting.

+ +

If a directory's configuration includes + FileETag INode MTime Size, and a + subdirectory's includes FileETag -INode, + the setting for that subdirectory (which will be inherited by + any sub-subdirectories that don't override it) will be equivalent to + FileETag MTime Size.

+ +
+
top
+

<Files> Directive

+ + + + + + + +
Description:Contains directives that apply to matched +filenames
Syntax:<Files filename> ... </Files>
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

The <Files> directive + limits the scope of the enclosed directives by filename. It is comparable + to the <Directory> + and <Location> + directives. It should be matched with a </Files> + directive. The directives given within this section will be applied to + any object with a basename (last component of filename) matching the + specified filename. <Files> + sections are processed in the order they appear in the + configuration file, after the <Directory> sections and + .htaccess files are read, but before <Location> sections. Note + that <Files> can be nested + inside <Directory> sections to restrict the + portion of the filesystem they apply to.

+ +

The filename argument should include a filename, or + a wild-card string, where ? matches any single character, + and * matches any sequences of characters. + Regular expressions + can also be used, with the addition of the + ~ character. For example:

+ +

+ <Files ~ "\.(gif|jpe?g|png)$"> +

+ +

would match most common Internet graphics formats. <FilesMatch> is preferred, + however.

+ +

Note that unlike <Directory> and <Location> sections, <Files> sections can be used inside + .htaccess files. This allows users to control access to + their own files, at a file-by-file level.

+ + +

See also

+ +
+
top
+

<FilesMatch> Directive

+ + + + + + + +
Description:Contains directives that apply to regular-expression matched +filenames
Syntax:<FilesMatch regex> ... </FilesMatch>
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

The <FilesMatch> directive + limits the scope of the enclosed directives by filename, just as the + <Files> directive + does. However, it accepts a regular + expression. For example:

+ +

+ <FilesMatch "\.(gif|jpe?g|png)$"> +

+ +

would match most common Internet graphics formats.

+ +

See also

+ +
+
top
+

ForceType Directive

+ + + + + + + + +
Description:Forces all matching files to be served with the specified +MIME content-type
Syntax:ForceType MIME-type|None
Context:directory, .htaccess
Override:FileInfo
Status:Core
Module:core
Compatibility:Moved to the core in Apache 2.0
+

When placed into an .htaccess file or a + <Directory>, or + <Location> or + <Files> + section, this directive forces all matching files to be served + with the content type identification given by + MIME-type. For example, if you had a directory full of + GIF files, but did not want to label them all with .gif, + you might want to use:

+ +

+ ForceType image/gif +

+ +

Note that unlike DefaultType, + this directive overrides all mime-type associations, including + filename extensions, that might identify the media type.

+ +

You can override any ForceType setting + by using the value of None:

+ +

+ # force all files to be image/gif:
+ <Location /images>
+ + ForceType image/gif
+ + </Location>
+
+ # but normal mime-type associations here:
+ <Location /images/mixed>
+ + ForceType None
+ + </Location> +

+ +
+
top
+

HostnameLookups Directive

+ + + + + + + +
Description:Enables DNS lookups on client IP addresses
Syntax:HostnameLookups On|Off|Double
Default:HostnameLookups Off
Context:server config, virtual host, directory
Status:Core
Module:core
+

This directive enables DNS lookups so that host names can be + logged (and passed to CGIs/SSIs in REMOTE_HOST). + The value Double refers to doing double-reverse + DNS lookup. That is, after a reverse lookup is performed, a forward + lookup is then performed on that result. At least one of the IP + addresses in the forward lookup must match the original + address. (In "tcpwrappers" terminology this is called + PARANOID.)

+ +

Regardless of the setting, when mod_authz_host is + used for controlling access by hostname, a double reverse lookup + will be performed. This is necessary for security. Note that the + result of this double-reverse isn't generally available unless you + set HostnameLookups Double. For example, if only + HostnameLookups On and a request is made to an object + that is protected by hostname restrictions, regardless of whether + the double-reverse fails or not, CGIs will still be passed the + single-reverse result in REMOTE_HOST.

+ +

The default is Off in order to save the network + traffic for those sites that don't truly need the reverse + lookups done. It is also better for the end users because they + don't have to suffer the extra latency that a lookup entails. + Heavily loaded sites should leave this directive + Off, since DNS lookups can take considerable + amounts of time. The utility logresolve, compiled by + default to the bin subdirectory of your installation + directory, can be used to look up host names from logged IP addresses + offline.

+ +
+
top
+

<IfDefine> Directive

+ + + + + + + +
Description:Encloses directives that will be processed only +if a test is true at startup
Syntax:<IfDefine [!]parameter-name> ... + </IfDefine>
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

The <IfDefine test>...</IfDefine> + section is used to mark directives that are conditional. The + directives within an <IfDefine> + section are only processed if the test is true. If + test is false, everything between the start and end markers is + ignored.

+ +

The test in the <IfDefine> section directive can be one of two forms:

+ +
    +
  • parameter-name
    • + +
  • !parameter-name
    • +
+ +

In the former case, the directives between the start and end + markers are only processed if the parameter named + parameter-name is defined. The second format reverses + the test, and only processes the directives if + parameter-name is not defined.

+ +

The parameter-name argument is a define as given on + the httpd command line via -Dparameter- + , at the time the server was started.

+ +

<IfDefine> sections are + nest-able, which can be used to implement simple + multiple-parameter tests. Example:

+ +

+ httpd -DReverseProxy ...
+
+ # httpd.conf
+ <IfDefine ReverseProxy>
+ + LoadModule rewrite_module modules/mod_rewrite.so
+ LoadModule proxy_module modules/libproxy.so
+ + </IfDefine> +

+ +
+
top
+

<IfModule> Directive

+ + + + + + + + +
Description:Encloses directives that are processed conditional on the +presence or absence of a specific module
Syntax:<IfModule [!]module-file|module-identifier> ... + </IfModule>
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
Compatibility:Module identifiers are available in version 2.1 and +later.
+

The <IfModule test>...</IfModule> + section is used to mark directives that are conditional on the presence of + a specific module. The directives within an <IfModule> section are only processed if the test + is true. If test is false, everything between the start and + end markers is ignored.

+ +

The test in the <IfModule> section directive can be one of two forms:

+ +
    +
  • module
    • + +
  • !module
    • +
+ +

In the former case, the directives between the start and end + markers are only processed if the module named module + is included in Apache -- either compiled in or + dynamically loaded using LoadModule. The second format reverses the test, + and only processes the directives if module is + not included.

+ +

The module argument can be either the module identifier or + the file name of the module, at the time it was compiled. For example, + rewrite_module is the identifier and + mod_rewrite.c is the file name. If a module consists of + several source files, use the name of the file containing the string + STANDARD20_MODULE_STUFF.

+ +

<IfModule> sections are + nest-able, which can be used to implement simple multiple-module + tests.

+ +
This section should only be used if you need to have one + configuration file that works whether or not a specific module + is available. In normal operation, directives need not be + placed in <IfModule> + sections.
+ +
+
top
+

Include Directive

+ + + + + + + +
Description:Includes other configuration files from within +the server configuration files
Syntax:Include file-path|directory-path
Context:server config, virtual host, directory
Status:Core
Module:core
Compatibility:Wildcard matching available in 2.0.41 and later
+

This directive allows inclusion of other configuration files + from within the server configuration files.

+ +

Shell-style (fnmatch()) wildcard characters can be used to + include several files at once, in alphabetical order. In + addition, if Include points to a directory, + rather than a file, Apache will read all files in that directory + and any subdirectory. But including entire directories is not + recommended, because it is easy to accidentally leave temporary + files in a directory that can cause httpd to + fail.

+ +

The file path specified may be an absolute path, or may be relative + to the ServerRoot directory.

+ +

Examples:

+ +

+ Include /usr/local/apache2/conf/ssl.conf
+ Include /usr/local/apache2/conf/vhosts/*.conf +

+ +

Or, providing paths relative to your ServerRoot directory:

+ +

+ Include conf/ssl.conf
+ Include conf/vhosts/*.conf +

+ +

Running apachectl configtest will give you a list + of the files that are being processed during the configuration + check:

+ +

+ root@host# apachectl configtest
+ Processing config file: /usr/local/apache2/conf/ssl.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost1.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost2.conf
+ Syntax OK +

+ +

See also

+ +
+
top
+

KeepAlive Directive

+ + + + + + + +
Description:Enables HTTP persistent connections
Syntax:KeepAlive On|Off
Default:KeepAlive On
Context:server config, virtual host
Status:Core
Module:core
+

The Keep-Alive extension to HTTP/1.0 and the persistent + connection feature of HTTP/1.1 provide long-lived HTTP sessions + which allow multiple requests to be sent over the same TCP + connection. In some cases this has been shown to result in an + almost 50% speedup in latency times for HTML documents with + many images. To enable Keep-Alive connections, set + KeepAlive On.

+ +

For HTTP/1.0 clients, Keep-Alive connections will only be + used if they are specifically requested by a client. In + addition, a Keep-Alive connection with an HTTP/1.0 client can + only be used when the length of the content is known in + advance. This implies that dynamic content such as CGI output, + SSI pages, and server-generated directory listings will + generally not use Keep-Alive connections to HTTP/1.0 clients. + For HTTP/1.1 clients, persistent connections are the default + unless otherwise specified. If the client requests it, chunked + encoding will be used in order to send content of unknown + length over persistent connections.

+ +

See also

+ +
+
top
+

KeepAliveTimeout Directive

+ + + + + + + +
Description:Amount of time the server will wait for subsequent +requests on a persistent connection
Syntax:KeepAliveTimeout seconds
Default:KeepAliveTimeout 5
Context:server config, virtual host
Status:Core
Module:core
+

The number of seconds Apache will wait for a subsequent + request before closing the connection. Once a request has been + received, the timeout value specified by the + Timeout directive applies.

+ +

Setting KeepAliveTimeout to a high value + may cause performance problems in heavily loaded servers. The + higher the timeout, the more server processes will be kept + occupied waiting on connections with idle clients.

+ +
+
top
+

<Limit> Directive

+ + + + + + + +
Description:Restrict enclosed access controls to only certain HTTP +methods
Syntax:<Limit method [method] ... > ... + </Limit>
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

Access controls are normally effective for + all access methods, and this is the usual + desired behavior. In the general case, access control + directives should not be placed within a + <Limit> section.

+ +

The purpose of the <Limit> + directive is to restrict the effect of the access controls to the + nominated HTTP methods. For all other methods, the access + restrictions that are enclosed in the <Limit> bracket will have no + effect. The following example applies the access control + only to the methods POST, PUT, and + DELETE, leaving all other methods unprotected:

+ +

+ <Limit POST PUT DELETE>
+ + Require valid-user
+ + </Limit> +

+ +

The method names listed can be one or more of: GET, + POST, PUT, DELETE, + CONNECT, OPTIONS, + PATCH, PROPFIND, PROPPATCH, + MKCOL, COPY, MOVE, + LOCK, and UNLOCK. The method name is + case-sensitive. If GET is used it will also + restrict HEAD requests. The TRACE method + cannot be limited.

+ +
A <LimitExcept> section should always be + used in preference to a <Limit> section when restricting access, + since a <LimitExcept> section provides protection + against arbitrary methods.
+ + +
+
top
+

<LimitExcept> Directive

+ + + + + + + +
Description:Restrict access controls to all HTTP methods +except the named ones
Syntax:<LimitExcept method [method] ... > ... + </LimitExcept>
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

<LimitExcept> and + </LimitExcept> are used to enclose + a group of access control directives which will then apply to any + HTTP access method not listed in the arguments; + i.e., it is the opposite of a <Limit> section and can be used to control + both standard and nonstandard/unrecognized methods. See the + documentation for <Limit> for more details.

+ +

For example:

+ +

+ <LimitExcept POST GET>
+ + Require valid-user
+ + </LimitExcept> +

+ + +
+
top
+

LimitInternalRecursion Directive

+ + + + + + + + +
Description:Determine maximum number of internal redirects and nested +subrequests
Syntax:LimitInternalRecursion number [number]
Default:LimitInternalRecursion 10
Context:server config, virtual host
Status:Core
Module:core
Compatibility:Available in Apache 2.0.47 and later
+

An internal redirect happens, for example, when using the Action directive, which internally + redirects the original request to a CGI script. A subrequest is Apache's + mechanism to find out what would happen for some URI if it were requested. + For example, mod_dir uses subrequests to look for the + files listed in the DirectoryIndex + directive.

+ +

LimitInternalRecursion prevents the server + from crashing when entering an infinite loop of internal redirects or + subrequests. Such loops are usually caused by misconfigurations.

+ +

The directive stores two different limits, which are evaluated on + per-request basis. The first number is the maximum number of + internal redirects, that may follow each other. The second number + determines, how deep subrequests may be nested. If you specify only one + number, it will be assigned to both limits.

+ +

Example

+ LimitInternalRecursion 5 +

+ +
+
top
+

LimitRequestBody Directive

+ + + + + + + + +
Description:Restricts the total size of the HTTP request body sent +from the client
Syntax:LimitRequestBody bytes
Default:LimitRequestBody 0
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

This directive specifies the number of bytes from 0 + (meaning unlimited) to 2147483647 (2GB) that are allowed in a + request body.

+ +

The LimitRequestBody directive allows + the user to set a limit on the allowed size of an HTTP request + message body within the context in which the directive is given + (server, per-directory, per-file or per-location). If the client + request exceeds that limit, the server will return an error + response instead of servicing the request. The size of a normal + request message body will vary greatly depending on the nature of + the resource and the methods allowed on that resource. CGI scripts + typically use the message body for retrieving form information. + Implementations of the PUT method will require + a value at least as large as any representation that the server + wishes to accept for that resource.

+ +

This directive gives the server administrator greater + control over abnormal client request behavior, which may be + useful for avoiding some forms of denial-of-service + attacks.

+ +

If, for example, you are permitting file upload to a particular + location, and wish to limit the size of the uploaded file to 100K, + you might use the following directive:

+ +

+ LimitRequestBody 102400 +

+ + +
+
top
+

LimitRequestFields Directive

+ + + + + + + +
Description:Limits the number of HTTP request header fields that +will be accepted from the client
Syntax:LimitRequestFields number
Default:LimitRequestFields 100
Context:server config
Status:Core
Module:core
+

Number is an integer from 0 (meaning unlimited) to + 32767. The default value is defined by the compile-time + constant DEFAULT_LIMIT_REQUEST_FIELDS (100 as + distributed).

+ +

The LimitRequestFields directive allows + the server administrator to modify the limit on the number of + request header fields allowed in an HTTP request. A server needs + this value to be larger than the number of fields that a normal + client request might include. The number of request header fields + used by a client rarely exceeds 20, but this may vary among + different client implementations, often depending upon the extent + to which a user has configured their browser to support detailed + content negotiation. Optional HTTP extensions are often expressed + using request header fields.

+ +

This directive gives the server administrator greater + control over abnormal client request behavior, which may be + useful for avoiding some forms of denial-of-service attacks. + The value should be increased if normal clients see an error + response from the server that indicates too many fields were + sent in the request.

+ +

For example:

+ +

+ LimitRequestFields 50 +

+ + +
+
top
+

LimitRequestFieldSize Directive

+ + + + + + + +
Description:Limits the size of the HTTP request header allowed from the +client
Syntax:LimitRequestFieldsize bytes
Default:LimitRequestFieldsize 8190
Context:server config
Status:Core
Module:core
+

This directive specifies the number of bytes + that will be allowed in an HTTP request header.

+ +

The LimitRequestFieldSize directive + allows the server administrator to reduce or increase the limit + on the allowed size of an HTTP request header field. A server + needs this value to be large enough to hold any one header field + from a normal client request. The size of a normal request header + field will vary greatly among different client implementations, + often depending upon the extent to which a user has configured + their browser to support detailed content negotiation. SPNEGO + authentication headers can be up to 12392 bytes.

+ +

This directive gives the server administrator greater + control over abnormal client request behavior, which may be + useful for avoiding some forms of denial-of-service attacks.

+ +

For example:

+ +

+ LimitRequestFieldSize 4094 +

+ +
Under normal conditions, the value should not be changed from + the default.
+ + +
+
top
+

LimitRequestLine Directive

+ + + + + + + +
Description:Limit the size of the HTTP request line that will be accepted +from the client
Syntax:LimitRequestLine bytes
Default:LimitRequestLine 8190
Context:server config
Status:Core
Module:core
+

This directive sets the number of bytes that will be + allowed on the HTTP request-line.

+ +

The LimitRequestLine directive allows + the server administrator to reduce or increase the limit on the allowed size + of a client's HTTP request-line. Since the request-line consists of the + HTTP method, URI, and protocol version, the + LimitRequestLine directive places a + restriction on the length of a request-URI allowed for a request + on the server. A server needs this value to be large enough to + hold any of its resource names, including any information that + might be passed in the query part of a GET request.

+ +

This directive gives the server administrator greater + control over abnormal client request behavior, which may be + useful for avoiding some forms of denial-of-service attacks.

+ +

For example:

+ +

+ LimitRequestLine 4094 +

+ +
Under normal conditions, the value should not be changed from + the default.
+ +
+
top
+

LimitXMLRequestBody Directive

+ + + + + + + + +
Description:Limits the size of an XML-based request body
Syntax:LimitXMLRequestBody bytes
Default:LimitXMLRequestBody 1000000
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

Limit (in bytes) on maximum size of an XML-based request + body. A value of 0 will disable any checking.

+ +

Example:

+ +

+ LimitXMLRequestBody 0 +

+ + +
+
top
+

<Location> Directive

+ + + + + + +
Description:Applies the enclosed directives only to matching +URLs
Syntax:<Location + URL-path|URL> ... </Location>
Context:server config, virtual host
Status:Core
Module:core
+

The <Location> directive + limits the scope of the enclosed directives by URL. It is similar to the + <Directory> + directive, and starts a subsection which is terminated with a + </Location> directive. <Location> sections are processed in the + order they appear in the configuration file, after the <Directory> sections and + .htaccess files are read, and after the <Files> sections.

+ +

<Location> sections operate + completely outside the filesystem. This has several consequences. + Most importantly, <Location> + directives should not be used to control access to filesystem + locations. Since several different URLs may map to the same + filesystem location, such access controls may by circumvented.

+ +

When to use <Location>

+ +

Use <Location> to apply + directives to content that lives outside the filesystem. For + content that lives in the filesystem, use <Directory> and <Files>. An exception is + <Location />, which is an easy way to + apply a configuration to the entire server.

+
+ +

For all origin (non-proxy) requests, the URL to be matched is a + URL-path of the form /path/. No scheme, hostname, + port, or query string may be included. For proxy requests, the + URL to be matched is of the form + scheme://servername/path, and you must include the + prefix.

+ +

The URL may use wildcards. In a wild-card string, ? matches + any single character, and * matches any sequences of + characters.

+ +

Regular expressions + can also be used, with the addition of the + ~ character. For example:

+ +

+ <Location ~ "/(extra|special)/data"> +

+ +

would match URLs that contained the substring /extra/data + or /special/data. The directive <LocationMatch> behaves + identical to the regex version of <Location>.

+ +

The <Location> + functionality is especially useful when combined with the + SetHandler + directive. For example, to enable status requests, but allow them + only from browsers at foo.com, you might use:

+ +

+ <Location /status>
+ + SetHandler server-status
+ Order Deny,Allow
+ Deny from all
+ Allow from .foo.com
+ + </Location> +

+ +

Note about / (slash)

+

The slash character has special meaning depending on where in a + URL it appears. People may be used to its behavior in the filesystem + where multiple adjacent slashes are frequently collapsed to a single + slash (i.e., /home///foo is the same as + /home/foo). In URL-space this is not necessarily true. + The <LocationMatch> + directive and the regex version of <Location> require you to explicitly specify multiple + slashes if that is your intention.

+ +

For example, <LocationMatch ^/abc> would match + the request URL /abc but not the request URL + //abc. The (non-regex) <Location> directive behaves similarly when used for + proxy requests. But when (non-regex) <Location> is used for non-proxy requests it will + implicitly match multiple slashes with a single slash. For example, + if you specify <Location /abc/def> and the + request is to /abc//def then it will match.

+
+ +

See also

+ +
+
top
+

<LocationMatch> Directive

+ + + + + + +
Description:Applies the enclosed directives only to regular-expression +matching URLs
Syntax:<LocationMatch + regex> ... </LocationMatch>
Context:server config, virtual host
Status:Core
Module:core
+

The <LocationMatch> directive + limits the scope of the enclosed directives by URL, in an identical manner + to <Location>. However, + it takes a regular expression + as an argument instead of a simple string. For example:

+ +

+ <LocationMatch "/(extra|special)/data"> +

+ +

would match URLs that contained the substring /extra/data + or /special/data.

+ +

See also

+ +
+
top
+

LogLevel Directive

+ + + + + + + +
Description:Controls the verbosity of the ErrorLog
Syntax:LogLevel level
Default:LogLevel warn
Context:server config, virtual host
Status:Core
Module:core
+

LogLevel adjusts the verbosity of the + messages recorded in the error logs (see ErrorLog directive). The following + levels are available, in order of decreasing + significance:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Level Description Example
emerg Emergencies - system is unusable."Child cannot open lock file. Exiting"
alert Action must be taken immediately."getpwuid: couldn't determine user name from uid"
crit Critical Conditions."socket: Failed to get a socket, exiting child"
error Error conditions."Premature end of script headers"
warn Warning conditions."child process 1234 did not exit, sending another + SIGHUP"
notice Normal but significant condition."httpd: caught SIGBUS, attempting to dump core in + ..."
info Informational."Server seems busy, (you may need to increase + StartServers, or Min/MaxSpareServers)..."
debug Debug-level messages"Opening config file ..."
+ +

When a particular level is specified, messages from all + other levels of higher significance will be reported as well. + E.g., when LogLevel info is specified, + then messages with log levels of notice and + warn will also be posted.

+ +

Using a level of at least crit is + recommended.

+ +

For example:

+ +

+ LogLevel notice +

+ +

Note

+

When logging to a regular file messages of the level + notice cannot be suppressed and thus are always + logged. However, this doesn't apply when logging is done + using syslog.

+
+ +
+
top
+

MaxKeepAliveRequests Directive

+ + + + + + + +
Description:Number of requests allowed on a persistent +connection
Syntax:MaxKeepAliveRequests number
Default:MaxKeepAliveRequests 100
Context:server config, virtual host
Status:Core
Module:core
+

The MaxKeepAliveRequests directive + limits the number of requests allowed per connection when + KeepAlive is on. If it is + set to 0, unlimited requests will be allowed. We + recommend that this setting be kept to a high value for maximum + server performance.

+ +

For example:

+ +

+ MaxKeepAliveRequests 500 +

+ +
+
top
+

NameVirtualHost Directive

+ + + + + + +
Description:Designates an IP address for name-virtual +hosting
Syntax:NameVirtualHost addr[:port]
Context:server config
Status:Core
Module:core
+

The NameVirtualHost directive is a + required directive if you want to configure name-based virtual hosts.

+ +

Although addr can be hostname it is recommended + that you always use an IP address, e.g.

+ +

+ NameVirtualHost 111.22.33.44 +

+ +

With the NameVirtualHost directive you + specify the IP address on which the server will receive requests + for the name-based virtual hosts. This will usually be the address + to which your name-based virtual host names resolve. In cases + where a firewall or other proxy receives the requests and forwards + them on a different IP address to the server, you must specify the + IP address of the physical interface on the machine which will be + servicing the requests. If you have multiple name-based hosts on + multiple addresses, repeat the directive for each address.

+ +

Note

+

Note, that the "main server" and any _default_ servers + will never be served for a request to a + NameVirtualHost IP address (unless for some + reason you specify NameVirtualHost but then + don't define any VirtualHosts for that + address).

+
+ +

Optionally you can specify a port number on which the + name-based virtual hosts should be used, e.g.

+ +

+ NameVirtualHost 111.22.33.44:8080 +

+ +

IPv6 addresses must be enclosed in square brackets, as shown + in the following example:

+ +

+ NameVirtualHost [2001:db8::a00:20ff:fea7:ccea]:8080 +

+ +

To receive requests on all interfaces, you can use an argument of + *

+ +

+ NameVirtualHost * +

+ +

Argument to <VirtualHost> + directive

+

Note that the argument to the <VirtualHost> directive must + exactly match the argument to the NameVirtualHost directive.

+ +

+ NameVirtualHost 1.2.3.4
+ <VirtualHost 1.2.3.4>
+ # ...
+ </VirtualHost>
+

+
+ +

See also

+ +
+
top
+

Options Directive

+ + + + + + + + +
Description:Configures what features are available in a particular +directory
Syntax:Options + [+|-]option [[+|-]option] ...
Default:Options All
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Core
Module:core
+

The Options directive controls which + server features are available in a particular directory.

+ +

option can be set to None, in which + case none of the extra features are enabled, or one or more of + the following:

+ +
+
All
+ +
All options except for MultiViews. This is the default + setting.
+ +
ExecCGI
+ +
+ Execution of CGI scripts using mod_cgi + is permitted.
+ +
FollowSymLinks
+ +
+ + The server will follow symbolic links in this directory. +
+

Even though the server follows the symlink it does not + change the pathname used to match against <Directory> sections.

+

Note also, that this option gets ignored if set + inside a <Location> + section.

+
+ +
Includes
+ +
+ Server-side includes provided by mod_include + are permitted.
+ +
IncludesNOEXEC
+ +
+ + Server-side includes are permitted, but the #exec + cmd and #exec cgi are disabled. It is still + possible to #include virtual CGI scripts from + ScriptAliased + directories.
+ +
Indexes
+ +
+ If a URL which maps to a directory is requested, and there + is no DirectoryIndex + (e.g., index.html) in that directory, then + mod_autoindex will return a formatted listing + of the directory.
+ +
MultiViews
+ +
+ Content negotiated + "MultiViews" are allowed using + mod_negotiation.
+ +
SymLinksIfOwnerMatch
+ +
The server will only follow symbolic links for which the + target file or directory is owned by the same user id as the + link. + +

Note

This option gets ignored if + set inside a <Location> section.
+
+
+ +

Normally, if multiple Options could + apply to a directory, then the most specific one is used and + others are ignored; the options are not merged. (See how sections are merged.) + However if all the options on the + Options directive are preceded by a + + or - symbol, the options are + merged. Any options preceded by a + are added to the + options currently in force, and any options preceded by a + - are removed from the options currently in + force.

+ +

For example, without any + and - symbols:

+ +

+ <Directory /web/docs>
+ + Options Indexes FollowSymLinks
+ + </Directory>
+
+ <Directory /web/docs/spec>
+ + Options Includes
+ + </Directory> +

+ +

then only Includes will be set for the + /web/docs/spec directory. However if the second + Options directive uses the + and + - symbols:

+ +

+ <Directory /web/docs>
+ + Options Indexes FollowSymLinks
+ + </Directory>
+
+ <Directory /web/docs/spec>
+ + Options +Includes -Indexes
+ + </Directory> +

+ +

then the options FollowSymLinks and + Includes are set for the /web/docs/spec + directory.

+ +

Note

+

Using -IncludesNOEXEC or + -Includes disables server-side includes completely + regardless of the previous setting.

+
+ +

The default in the absence of any other settings is + All.

+ +
+
top
+

Require Directive

+ + + + + + + +
Description:Selects which authenticated users can access +a resource
Syntax:Require entity-name [entity-name] ...
Context:directory, .htaccess
Override:AuthConfig
Status:Core
Module:core
+

This directive selects which authenticated users can access a + resource. The restrictions are processed by authorization + modules. Some of the allowed syntaxes provided by + mod_authz_user and + mod_authz_groupfile are:

+ +
+
Require user userid [userid] + ...
+
Only the named users can access the resource.
+ +
Require group group-name [group-name] + ...
+
Only users in the named groups can access the resource.
+ +
Require valid-user
+
All valid users can access the resource.
+
+ +

Other authorization modules that implement require options + include mod_authnz_ldap, + mod_authz_dbm, and + mod_authz_owner.

+ +

Require must be accompanied by + AuthName and AuthType directives, and directives such + as AuthUserFile + and AuthGroupFile (to + define users and groups) in order to work correctly. Example:

+ +

+ AuthType Basic
+ AuthName "Restricted Resource"
+ AuthUserFile /web/users
+ AuthGroupFile /web/groups
+ Require group admin +

+ +

Access controls which are applied in this way are effective for + all methods. This is what is normally + desired. If you wish to apply access controls only to + specific methods, while leaving other methods unprotected, then + place the Require statement into a + <Limit> + section.

+ +

If Require is used together with + the Allow or + Deny directives, + then the interaction of these restrictions is controlled by + the Satisfy directive.

+ +

Removing controls in subdirectories

+

The following example shows how to use the Satisfy directive to disable access + controls in a subdirectory of a protected directory. This + technique should be used with caution, because it will also + disable any access controls imposed by + mod_authz_host.

+

+ <Directory /path/to/protected/>
+ + Require user david
+ + </Directory>
+ <Directory /path/to/protected/unprotected>
+ + # All access controls and authentication are disabled
+ # in this directory
+ Satisfy Any
+ Allow from all
+ + </Directory>
+

+
+ + +

See also

+ +
+
top
+

RLimitCPU Directive

+ + + + + + + + +
Description:Limits the CPU consumption of processes launched +by Apache children
Syntax:RLimitCPU seconds|max [seconds|max]
Default:Unset; uses operating system defaults
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

Takes 1 or 2 parameters. The first parameter sets the soft + resource limit for all processes and the second parameter sets + the maximum resource limit. Either parameter can be a number, + or max to indicate to the server that the limit should + be set to the maximum allowed by the operating system + configuration. Raising the maximum resource limit requires that + the server is running as root, or in the initial startup + phase.

+ +

This applies to processes forked off from Apache children + servicing requests, not the Apache children themselves. This + includes CGI scripts and SSI exec commands, but not any + processes forked off from the Apache parent such as piped + logs.

+ +

CPU resource limits are expressed in seconds per + process.

+ +

See also

+ +
+
top
+

RLimitMEM Directive

+ + + + + + + + +
Description:Limits the memory consumption of processes launched +by Apache children
Syntax:RLimitMEM bytes|max [bytes|max]
Default:Unset; uses operating system defaults
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

Takes 1 or 2 parameters. The first parameter sets the soft + resource limit for all processes and the second parameter sets + the maximum resource limit. Either parameter can be a number, + or max to indicate to the server that the limit should + be set to the maximum allowed by the operating system + configuration. Raising the maximum resource limit requires that + the server is running as root, or in the initial startup + phase.

+ +

This applies to processes forked off from Apache children + servicing requests, not the Apache children themselves. This + includes CGI scripts and SSI exec commands, but not any + processes forked off from the Apache parent such as piped + logs.

+ +

Memory resource limits are expressed in bytes per + process.

+ +

See also

+ +
+
top
+

RLimitNPROC Directive

+ + + + + + + + +
Description:Limits the number of processes that can be launched by +processes launched by Apache children
Syntax:RLimitNPROC number|max [number|max]
Default:Unset; uses operating system defaults
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

Takes 1 or 2 parameters. The first parameter sets the soft + resource limit for all processes and the second parameter sets + the maximum resource limit. Either parameter can be a number, + or max to indicate to the server that the limit + should be set to the maximum allowed by the operating system + configuration. Raising the maximum resource limit requires that + the server is running as root, or in the initial startup + phase.

+ +

This applies to processes forked off from Apache children + servicing requests, not the Apache children themselves. This + includes CGI scripts and SSI exec commands, but not any + processes forked off from the Apache parent such as piped + logs.

+ +

Process limits control the number of processes per user.

+ +

Note

+

If CGI processes are not running + under user ids other than the web server user id, this directive + will limit the number of processes that the server itself can + create. Evidence of this situation will be indicated by + cannot fork messages in the + error_log.

+
+ +

See also

+ +
+
top
+

Satisfy Directive

+ + + + + + + + + +
Description:Interaction between host-level access control and +user authentication
Syntax:Satisfy Any|All
Default:Satisfy All
Context:directory, .htaccess
Override:AuthConfig
Status:Core
Module:core
Compatibility:Influenced by <Limit> and <LimitExcept> in version 2.0.51 and +later
+

Access policy if both Allow and Require used. The parameter can be + either All or Any. This directive is only + useful if access to a particular area is being restricted by both + username/password and client host address. In this case + the default behavior (All) is to require that the client + passes the address access restriction and enters a valid + username and password. With the Any option the client will be + granted access if they either pass the host restriction or enter a + valid username and password. This can be used to password restrict + an area, but to let clients from particular addresses in without + prompting for a password.

+ +

For example, if you wanted to let people on your network have + unrestricted access to a portion of your website, but require that + people outside of your network provide a password, you could use a + configuration similar to the following:

+ +

+ Require valid-user
+ Allow from 192.168.1
+ Satisfy Any +

+ +

Since version 2.0.51 Satisfy directives can + be restricted to particular methods by <Limit> and <LimitExcept> sections.

+ +

See also

+ +
+
top
+

ScriptInterpreterSource Directive

+ + + + + + + + + +
Description:Technique for locating the interpreter for CGI +scripts
Syntax:ScriptInterpreterSource Registry|Registry-Strict|Script
Default:ScriptInterpreterSource Script
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
Compatibility:Win32 only; +option Registry-Strict is available in Apache 2.0 and +later
+

This directive is used to control how Apache finds the + interpreter used to run CGI scripts. The default setting is + Script. This causes Apache to use the interpreter pointed to + by the shebang line (first line, starting with #!) in the + script. On Win32 systems this line usually looks like:

+ +

+ #!C:/Perl/bin/perl.exe +

+ +

or, if perl is in the PATH, simply:

+ +

+ #!perl +

+ +

Setting ScriptInterpreterSource Registry will + cause the Windows Registry tree HKEY_CLASSES_ROOT to be + searched using the script file extension (e.g., .pl) as a + search key. The command defined by the registry subkey + Shell\ExecCGI\Command or, if it does not exist, by the subkey + Shell\Open\Command is used to open the script file. If the + registry keys cannot be found, Apache falls back to the behavior of the + Script option.

+ +

Security

+

Be careful when using ScriptInterpreterSource + Registry with ScriptAlias'ed directories, because + Apache will try to execute every file within this + directory. The Registry setting may cause undesired + program calls on files which are typically not executed. For + example, the default open command on .htm files on + most Windows systems will execute Microsoft Internet Explorer, so + any HTTP request for an .htm file existing within the + script directory would start the browser in the background on the + server. This is a good way to crash your system within a minute or + so.

+
+ +

The option Registry-Strict which is new in Apache + 2.0 does the same thing as Registry but uses only the + subkey Shell\ExecCGI\Command. The + ExecCGI key is not a common one. It must be + configured manually in the windows registry and hence prevents + accidental program calls on your system.

+ +
+
top
+

ServerAdmin Directive

+ + + + + + +
Description:Email address that the server includes in error +messages sent to the client
Syntax:ServerAdmin email-address|URL
Context:server config, virtual host
Status:Core
Module:core
+

The ServerAdmin sets the contact address + that the server includes in any error messages it returns to the + client. If the httpd doesn't recognize the supplied argument + as an URL, it + assumes, that it's an email-address and prepends it with + mailto: in hyperlink targets. However, it's recommended to + actually use an email address, since there are a lot of CGI scripts that + make that assumption. If you want to use an URL, it should point to another + server under your control. Otherwise users may not be able to contact you in + case of errors.

+ +

It may be worth setting up a dedicated address for this, e.g.

+ +

+ ServerAdmin www-admin@foo.example.com +

+

as users do not always mention that they are talking about the + server!

+ +
+
top
+

ServerAlias Directive

+ + + + + + +
Description:Alternate names for a host used when matching requests +to name-virtual hosts
Syntax:ServerAlias hostname [hostname] ...
Context:virtual host
Status:Core
Module:core
+

The ServerAlias directive sets the + alternate names for a host, for use with name-based virtual hosts.

+ +

+ <VirtualHost *>
+ ServerName server.domain.com
+ ServerAlias server server2.domain.com server2
+ # ...
+ </VirtualHost> +

+ +

See also

+ +
+
top
+

ServerName Directive

+ + + + + + + +
Description:Hostname and port that the server uses to identify +itself
Syntax:ServerName [scheme://]fully-qualified-domain-name[:port]
Context:server config, virtual host
Status:Core
Module:core
Compatibility:In version 2.0, this + directive supersedes the functionality of the Port + directive from version 1.3.
+

The ServerName directive sets the + request scheme, hostname and + port that the server uses to identify itself. This is used when + creating redirection URLs. For example, if the name of the + machine hosting the web server is simple.example.com, + but the machine also has the DNS alias www.example.com + and you wish the web server to be so identified, the following + directive should be used:

+ +

+ ServerName www.example.com:80 +

+ +

If no ServerName is specified, then the + server attempts to deduce the hostname by performing a reverse + lookup on the IP address. If no port is specified in the + ServerName, then the server will use the + port from the incoming request. For optimal reliability and + predictability, you should specify an explicit hostname and port + using the ServerName directive.

+ +

If you are using name-based virtual hosts, + the ServerName inside a + <VirtualHost> + section specifies what hostname must appear in the request's + Host: header to match this virtual host.

+ + +

Sometimes, the server runs behind a device that processes SSL, + such as a reverse proxy, load balancer or SSL offload + appliance. When this is the case, specify the + https:// scheme and the port number to which the + clients connect in the ServerName directive + to make sure that the server generates the correct + self-referential URLs. +

+ +

See the description of the + UseCanonicalName and + UseCanonicalPhysicalPortdirectives for + settings which determine whether self-referential URLs (e.g., by the + mod_dir module) will refer to the + specified port, or to the port number given in the client's request. +

+ + +

See also

+ +
+
top
+

ServerPath Directive

+ + + + + + +
Description:Legacy URL pathname for a name-based virtual host that +is accessed by an incompatible browser
Syntax:ServerPath URL-path
Context:virtual host
Status:Core
Module:core
+

The ServerPath directive sets the legacy + URL pathname for a host, for use with name-based virtual hosts.

+ +

See also

+ +
+
top
+

ServerRoot Directive

+ + + + + + + +
Description:Base directory for the server installation
Syntax:ServerRoot directory-path
Default:ServerRoot /usr/local/apache
Context:server config
Status:Core
Module:core
+

The ServerRoot directive sets the + directory in which the server lives. Typically it will contain the + subdirectories conf/ and logs/. Relative + paths in other configuration directives (such as Include or LoadModule, for example) are taken as + relative to this directory.

+ +

Example

+ ServerRoot /home/httpd +

+ + +

See also

+ +
+
top
+

ServerSignature Directive

+ + + + + + + + +
Description:Configures the footer on server-generated documents
Syntax:ServerSignature On|Off|EMail
Default:ServerSignature Off
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Core
Module:core
+

The ServerSignature directive allows the + configuration of a trailing footer line under server-generated + documents (error messages, mod_proxy ftp directory + listings, mod_info output, ...). The reason why you + would want to enable such a footer line is that in a chain of proxies, + the user often has no possibility to tell which of the chained servers + actually produced a returned error message.

+ +

The Off + setting, which is the default, suppresses the footer line (and is + therefore compatible with the behavior of Apache-1.2 and + below). The On setting simply adds a line with the + server version number and ServerName of the serving virtual host, + and the EMail setting additionally creates a + "mailto:" reference to the ServerAdmin of the referenced + document.

+ +

After version 2.0.44, the details of the server version number + presented are controlled by the ServerTokens directive.

+ +

See also

+ +
+
top
+

ServerTokens Directive

+ + + + + + + +
Description:Configures the Server HTTP response +header
Syntax:ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full
Default:ServerTokens Full
Context:server config
Status:Core
Module:core
+

This directive controls whether Server response + header field which is sent back to clients includes a + description of the generic OS-type of the server as well as + information about compiled-in modules.

+ +
+
ServerTokens Prod[uctOnly]
+ +
Server sends (e.g.): Server: + Apache
+ +
ServerTokens Major
+ +
Server sends (e.g.): Server: + Apache/2
+ +
ServerTokens Minor
+ +
Server sends (e.g.): Server: + Apache/2.0
+ +
ServerTokens Min[imal]
+ +
Server sends (e.g.): Server: + Apache/2.0.41
+ +
ServerTokens OS
+ +
Server sends (e.g.): Server: Apache/2.0.41 + (Unix)
+ +
ServerTokens Full (or not specified)
+ +
Server sends (e.g.): Server: Apache/2.0.41 + (Unix) PHP/4.2.2 MyMod/1.2
+
+ +

This setting applies to the entire server, and cannot be + enabled or disabled on a virtualhost-by-virtualhost basis.

+ +

After version 2.0.44, this directive also controls the + information presented by the ServerSignature directive.

+ +

See also

+ +
+
top
+

SetHandler Directive

+ + + + + + + + +
Description:Forces all matching files to be processed by a +handler
Syntax:SetHandler handler-name|None
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
Compatibility:Moved into the core in Apache 2.0
+

When placed into an .htaccess file or a + <Directory> or + <Location> + section, this directive forces all matching files to be parsed + through the handler given by + handler-name. For example, if you had a directory you + wanted to be parsed entirely as imagemap rule files, regardless + of extension, you might put the following into an + .htaccess file in that directory:

+ +

+ SetHandler imap-file +

+ +

Another example: if you wanted to have the server display a + status report whenever a URL of + http://servername/status was called, you might put + the following into httpd.conf:

+ +

+ <Location /status>
+ + SetHandler server-status
+ + </Location> +

+ +

You can override an earlier defined SetHandler + directive by using the value None.

+ +

See also

+ +
+
top
+

SetInputFilter Directive

+ + + + + + + +
Description:Sets the filters that will process client requests and POST +input
Syntax:SetInputFilter filter[;filter...]
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
+

The SetInputFilter directive sets the + filter or filters which will process client requests and POST + input when they are received by the server. This is in addition to + any filters defined elsewhere, including the + AddInputFilter + directive.

+ +

If more than one filter is specified, they must be separated + by semicolons in the order in which they should process the + content.

+ +

See also

+ +
+
top
+

SetOutputFilter Directive

+ + + + + + + +
Description:Sets the filters that will process responses from the +server
Syntax:SetOutputFilter filter[;filter...]
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Core
Module:core
+

The SetOutputFilter directive sets the filters + which will process responses from the server before they are + sent to the client. This is in addition to any filters defined + elsewhere, including the + AddOutputFilter + directive.

+ +

For example, the following configuration will process all files + in the /www/data/ directory for server-side + includes.

+ +

+ <Directory /www/data/>
+ + SetOutputFilter INCLUDES
+ + </Directory> +

+ +

If more than one filter is specified, they must be separated + by semicolons in the order in which they should process the + content.

+ +

See also

+ +
+
top
+

TimeOut Directive

+ + + + + + + +
Description:Amount of time the server will wait for +certain events before failing a request
Syntax:TimeOut seconds
Default:TimeOut 300
Context:server config
Status:Core
Module:core
+

The TimeOut directive currently defines + the amount of time Apache will wait for three things:

+ +
    +
  1. The total amount of time it takes to receive a GET + request.
    2. + +
  2. The amount of time between receipt of TCP packets on a + POST or PUT request.
    3. + +
  3. The amount of time between ACKs on transmissions of TCP + packets in responses.
    4. +
+ +

We plan on making these separately configurable at some point + down the road. The timer used to default to 1200 before 1.2, + but has been lowered to 300 which is still far more than + necessary in most situations. It is not set any lower by + default because there may still be odd places in the code where + the timer is not reset when a packet is sent.

+ +
+
top
+

TraceEnable Directive

+ + + + + + + + +
Description:Determines the behaviour on TRACE +requests
Syntax:TraceEnable [on|off|extended]
Default:TraceEnable on
Context:server config
Status:Core
Module:core
Compatibility:Available in Apache 1.3.34, 2.0.55 and later
+

This directive overrides the behavior of TRACE for both + the core server and mod_proxy. The default + TraceEnable on permits TRACE requests per + RFC 2616, which disallows any request body to accompany the request. + TraceEnable off causes the core server and + mod_proxy to return a 405 (Method not + allowed) error to the client.

+ +

Finally, for testing and diagnostic purposes only, request + bodies may be allowed using the non-compliant TraceEnable + extended directive. The core (as an origin server) will + restrict the request body to 64k (plus 8k for chunk headers if + Transfer-Encoding: chunked is used). The core will + reflect the full headers and all chunk headers with the response + body. As a proxy server, the request body is not restricted to 64k.

+ +
+
top
+

UseCanonicalName Directive

+ + + + + + + +
Description:Configures how the server determines its own name and +port
Syntax:UseCanonicalName On|Off|DNS
Default:UseCanonicalName Off
Context:server config, virtual host, directory
Status:Core
Module:core
+

In many situations Apache must construct a self-referential + URL -- that is, a URL that refers back to the same server. With + UseCanonicalName On Apache will use the hostname and port + specified in the ServerName + directive to construct the canonical name for the server. This name + is used in all self-referential URLs, and for the values of + SERVER_NAME and SERVER_PORT in CGIs.

+ +

With UseCanonicalName Off Apache will form + self-referential URLs using the hostname and port supplied by + the client if any are supplied (otherwise it will use the + canonical name, as defined above). These values are the same + that are used to implement name based virtual hosts, + and are available with the same clients. The CGI variables + SERVER_NAME and SERVER_PORT will be + constructed from the client supplied values as well.

+ +

An example where this may be useful is on an intranet server + where you have users connecting to the machine using short + names such as www. You'll notice that if the users + type a shortname, and a URL which is a directory, such as + http://www/splat, without the trailing + slash then Apache will redirect them to + http://www.domain.com/splat/. If you have + authentication enabled, this will cause the user to have to + authenticate twice (once for www and once again + for www.domain.com -- see the + FAQ on this subject for more information). But if + UseCanonicalName is set Off, then + Apache will redirect to http://www/splat/.

+ +

There is a third option, UseCanonicalName DNS, + which is intended for use with mass IP-based virtual hosting to + support ancient clients that do not provide a + Host: header. With this option Apache does a + reverse DNS lookup on the server IP address that the client + connected to in order to work out self-referential URLs.

+ +

Warning

+

If CGIs make assumptions about the values of SERVER_NAME + they may be broken by this option. The client is essentially free + to give whatever value they want as a hostname. But if the CGI is + only using SERVER_NAME to construct self-referential URLs + then it should be just fine.

+
+ +

See also

+ +
+
top
+

UseCanonicalPhysicalPort Directive

+ + + + + + + +
Description:Configures how the server determines its own name and +port
Syntax:UseCanonicalPhysicalPort On|Off
Default:UseCanonicalPhysicalPort Off
Context:server config, virtual host, directory
Status:Core
Module:core
+

In many situations Apache must construct a self-referential + URL -- that is, a URL that refers back to the same server. With + UseCanonicalPhysicalPort On Apache will, when + constructing the canonical port for the server to honor + the UseCanonicalName directive, + provide the actual physical port number being used by this request + as a potential port. With UseCanonicalPhysicalPort Off + Apache will not ever use the actual physical port number, instead + relying on all configured information to construct a valid port number.

+ +

Note

+

The ordering of when the physical port is used is as follows:

+ UseCanonicalName On

+
    +
  • Port provided in Servername
    • +
  • Physical port
    • +
  • Default port
    • +
+ UseCanonicalName Off | DNS +
    +
  • Parsed port from Host: header
    • +
  • Physical port
    • +
  • Port provided in Servername
    • +
  • Default port
    • +
+ +

With UseCanonicalPhysicalPort Off, the + physical ports are removed from the ordering.

+
+ + +

See also

+ +
+
top
+

<VirtualHost> Directive

+ + + + + + +
Description:Contains directives that apply only to a specific +hostname or IP address
Syntax:<VirtualHost + addr[:port] [addr[:port]] + ...> ... </VirtualHost>
Context:server config
Status:Core
Module:core
+

<VirtualHost> and + </VirtualHost> are used to enclose a group of + directives that will apply only to a particular virtual host. Any + directive that is allowed in a virtual host context may be + used. When the server receives a request for a document on a + particular virtual host, it uses the configuration directives + enclosed in the <VirtualHost> + section. Addr can be:

+ +
    +
  • The IP address of the virtual host;
    • + +
  • A fully qualified domain name for the IP address of the + virtual host;
    • + +
  • The character *, which is used only in combination with + NameVirtualHost * to match all IP addresses; or
    • + +
  • The string _default_, which is used only + with IP virtual hosting to catch unmatched IP addresses.
    • +
+ +

Example

+ <VirtualHost 10.1.2.3>
+ + ServerAdmin webmaster@host.foo.com
+ DocumentRoot /www/docs/host.foo.com
+ ServerName host.foo.com
+ ErrorLog logs/host.foo.com-error_log
+ TransferLog logs/host.foo.com-access_log
+ + </VirtualHost> +

+ + +

IPv6 addresses must be specified in square brackets because + the optional port number could not be determined otherwise. An + IPv6 example is shown below:

+ +

+ <VirtualHost [2001:db8::a00:20ff:fea7:ccea]>
+ + ServerAdmin webmaster@host.example.com
+ DocumentRoot /www/docs/host.example.com
+ ServerName host.example.com
+ ErrorLog logs/host.example.com-error_log
+ TransferLog logs/host.example.com-access_log
+ + </VirtualHost> +

+ +

Each Virtual Host must correspond to a different IP address, + different port number or a different host name for the server, + in the former case the server machine must be configured to + accept IP packets for multiple addresses. (If the machine does + not have multiple network interfaces, then this can be + accomplished with the ifconfig alias command -- if + your OS supports it).

+ +

Note

+

The use of <VirtualHost> does + not affect what addresses Apache listens on. You + may need to ensure that Apache is listening on the correct addresses + using Listen.

+
+ +

When using IP-based virtual hosting, the special name + _default_ can be specified in + which case this virtual host will match any IP address that is + not explicitly listed in another virtual host. In the absence + of any _default_ virtual host the "main" server config, + consisting of all those definitions outside any VirtualHost + section, is used when no IP-match occurs. (But note that any IP + address that matches a NameVirtualHost directive will use neither + the "main" server config nor the _default_ virtual host. + See the name-based virtual hosting + documentation for further details.)

+ +

You can specify a :port to change the port that is + matched. If unspecified then it defaults to the same port as the + most recent Listen + statement of the main server. You may also specify :* + to match all ports on that address. (This is recommended when used + with _default_.)

+ +

Security

+

See the security tips + document for details on why your security could be compromised if the + directory where log files are stored is writable by anyone other + than the user that starts the server.

+
+ +

See also

+ +
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/core.html.ja.euc-jp b/docs/manual/mod/core.html.ja.euc-jp new file mode 100644 index 00000000..ba561901 --- /dev/null +++ b/docs/manual/mod/core.html.ja.euc-jp @@ -0,0 +1,3373 @@ + + + +core - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥³¥¢µ¡Ç½

+
+

Available Languages:  de  | + en  | + ja 

+
+ +
ÀâÌÀ:¾ï¤Ë»ÈÍѲÄǽ¤Ê Apache HTTP ¥µ¡¼¥Ð¤Î¥³¥¢µ¡Ç½
¥¹¥Æ¡¼¥¿¥¹:Core
+
+ + +
top
+

AcceptFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥×¥í¥È¥³¥ë¤ò Listen ¤·¤Æ¤¤¤ë¥½¥±¥Ã¥È¤ÎºÇŬ²½¤òÀßÄꤹ¤ë
¹½Ê¸:AcceptFilter protocol accept_filter
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:2.1.5 °Ê¹ß
+

Listen ¤·¤Æ¤¤¤ë¥½¥±¥Ã¥È¤ËÂФ·¤Æ¡¢OS ¤¬¸ÇÍ­¤Ë»ý¤Ã¤Æ¤¤¤ë¥×¥í¥È¥³¥ë¤Ë¤Ä¤¤¤Æ¤ÎºÇŬ²½¤ò + Í­¸ú¤Ë¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤¹¡£ÂçÁ°Äó¤È¤Ê¤ë¾ò·ï¤Ï¡¢¥Ç¡¼¥¿¤¬¼õ¿®¤µ¤ì¤ë¤« + HTTP ¥ê¥¯¥¨¥¹¥ÈÁ´ÂΤ¬¥Ð¥Ã¥Õ¥¡¤µ¤ì¤ë¤«¤¹¤ë¤Þ¤Ç¡¢¥«¡¼¥Í¥ë¤¬¥µ¡¼¥Ð¥×¥í¥»¥¹¤Ë + ¥½¥±¥Ã¥È¤òÁ÷¤é¤Ê¤¤¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¡¢¤È¤¤¤¦¤³¤È¤Ç¤¹¡£¸½ºß¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¤Î¤Ï¡¢ + + FreeBSD ¤Î Accept Filter ¤È Linux ¤Î¥×¥ê¥ß¥Æ¥£¥Ö¤Ê + TCP_DEFER_ACCEPT ¤Î¤ß¤Ç¤¹¡£

+ +

FreeBSD ¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï :

+

+ AcceptFilter http httpready
+ AcceptFilter https dataready +

+ +

httpready Accept Filter ¤Ï HTTP ¥ê¥¯¥¨¥¹¥ÈÁ´ÂΤò¡¢ + ¥«¡¼¥Í¥ë¥ì¥Ù¥ë¤Ç¥Ð¥Ã¥Õ¥¡¥ê¥ó¥°¤·¤Þ¤¹¡£¥ê¥¯¥¨¥¹¥ÈÁ´ÂΤò¼õ¿®¤·½ª¤ï¤ë¤È¡¢ + ¤½¤Î¸å¥µ¡¼¥Ð¥×¥í¥»¥¹¤Ë¤½¤ì¤òÁ÷¤ê¤Þ¤¹¡£¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï accf_http(9) + ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£HTTPS ¤Î¥ê¥¯¥¨¥¹¥È¤Ï°Å¹æ²½¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç accf_data(9) + ¥Õ¥£¥ë¥¿¤Î¤ß¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£

+ +

Linux ¤Ç¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï :

+

+ AcceptFilter http data
+ AcceptFilter https data +

+ +

Linux ¤Î TCP_DEFER_ACCEPT ¤Ï HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ð¥Ã¥Õ¥¡¥ê¥ó¥°¤ò + ¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤»¤ó¡£none °Ê³°¤ÎÃÍ¤Ç + TCP_DEFER_ACCEPT ¤¬Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï Linux + man ¥Ú¡¼¥¸ tcp(7) + ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

°ú¿ô¤Ë none ¤ò»ØÄꤹ¤ë¤È¡¢¥×¥í¥È¥³¥ë¤ËÂФ¹¤ëÁ´¤Æ¤Î Accept + Filter ¤¬Ìµ¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£nntp ¤È¤¤¤Ã¤¿¡¢Àè¤Ë¥µ¡¼¥Ð¤Ë¥Ç¡¼¥¿¤ò + Á÷¤ëɬÍפΤ¢¤ë¥×¥í¥È¥³¥ë¤ËÍ­¸ú¤Ç¤¹ :

+

AcceptFilter nttp none

+ + +
+
top
+

AcceptPathInfo ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:¸å¤Ë³¤¯¥Ñ¥¹Ì¾¾ðÊó¤ò¼õ¤±ÉÕ¤±¤ë¥ê¥½¡¼¥¹¤Î»ØÄê
¹½Ê¸:AcceptPathInfo On|Off|Default
¥Ç¥Õ¥©¥ë¥È:AcceptPathInfo Default
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Apache 2.0.30 °Ê¹ß¤Ç»ÈÍѲÄǽ
+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë̾ (¤â¤·¤¯¤Ï¸ºß¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Î + ¸ºß¤·¤Ê¤¤¥Õ¥¡¥¤¥ë) ¤Î¸å¤Ë³¤¯¥Ñ¥¹Ì¾¾ðÊ󤬤¢¤ë¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤ë¤« + µñÈݤ¹¤ë¤«¤òÀ©¸æ¤·¤Þ¤¹¡£Â³¤­¤Î¥Ñ¥¹Ì¾¾ðÊó¤Ï¥¹¥¯¥ê¥×¥È¤Ë¤Ï PATH_INFO + ´Ä¶­ÊÑ¿ô¤È¤·¤ÆÍøÍѲÄǽ¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢/test/ ¤¬¡¢here.html ¤È¤¤¤¦¥Õ¥¡¥¤¥ë + °ì¤Ä¤Î¤ß¤¬¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ò»Ø¤·¤Æ¤¤¤ë¤È¤·¤Þ¤¹¡£¤½¤¦¤¹¤ë¤È¡¢ + /test/here.html/more ¤È /test/nothere.html/more + ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ÏξÊý¤È¤â /more ¤ò PATH_INFO ¤È¤·¤Þ¤¹¡£

+ +

AcceptPathInfo ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë»ØÄê²Äǽ¤Ê + »°¤Ä¤Î°ú¿ô¤Ï:

+ +
+
Off
¥ê¥¯¥¨¥¹¥È¤Ï¸ºß¤¹¤ë¥Ñ¥¹¤Ë¤½¤Î¤Þ¤Þ + ¥Þ¥Ã¥×¤µ¤ì¤ë¾ì¹ç¤Ë¤Î¤ß¼õ¤±ÉÕ¤±¤é¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢¾å¤ÎÎã¤Î + /test/here.html/more ¤Î¤è¤¦¤Ë¡¢ËÜÅö¤Î¥Õ¥¡¥¤¥ë̾¤Î + ¸å¤Ë¥Ñ¥¹Ì¾¾ðÊó¤¬Â³¤¯¥ê¥¯¥¨¥¹¥È¤Ë¤Ï 404 NOT FOUND ¥¨¥é¡¼¤¬ÊÖ¤ê¤Þ¤¹¡£
+ +
On
Á°¤ÎÊý¤Î¥Ñ¥¹¤¬Â¸ºß¤¹¤ë¥Õ¥¡¥¤¥ë¤Ë¥Þ¥Ã¥×¤¹¤ë¾ì¹ç¤Ï + ¥ê¥¯¥¨¥¹¥È¤¬¼õ¤±ÉÕ¤±¤é¤ì¤Þ¤¹¡£¾å¤ÎÎã¤Î /test/here.html/more + ¤Ï /test/here.html ¤¬Í­¸ú¤Ê¥Õ¥¡¥¤¥ë¤Ë¥Þ¥Ã¥×¤¹¤ì¤Ð + ¼õ¤±ÉÕ¤±¤é¤ì¤Þ¤¹¡£
+ +
Default
³¤­¤Î¥Ñ¥¹Ì¾¾ðÊó¤Î°·¤¤¤Ï¥ê¥¯¥¨¥¹¥È¤Î + ¥Ï¥ó¥É¥é¤Ç·è¤Þ¤ê¤Þ¤¹¡£ + ÉáÄ̤Υե¡¥¤¥ë¤Î¤¿¤á¤Î¥³¥¢¥Ï¥ó¥É¥é¤Î¥Ç¥Õ¥©¥ë¥È¤Ï PATH_INFO ¤òµñÈݤ·¤Þ¤¹¡£ + cgi-script ¤ä isapi-handler ¤Î¤è¤¦¤Ë¥¹¥¯¥ê¥×¥È¤ò°·¤¦¥Ï¥ó¥É¥é¤Ï + °ìÈÌŪ¤Ë¥Ç¥Õ¥©¥ë¥È¤Ç PATH_INFO ¤ò¼õ¤±ÉÕ¤±¤Þ¤¹¡£
+
+ +

AcceptPathInfo ¤Î¼ç¤ÊÌÜŪ¤Ï¥Ï¥ó¥É¥é¤Î PATH_INFO ¤ò + ¼õ¤±ÉÕ¤±¤ë¤«µñÈݤ¹¤ë¤«¤ÎÁªÂò¤ò¾å½ñ¤­¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ç¤¹¡£ + Î㤨¤Ð¡¢¤³¤ì¤ÏÎ㤨¤Ð INCLUDES ¤Î¤è¤¦¤Ê + ¥Õ¥£¥ë¥¿¤ò»È¤Ã¤Æ PATH_INFO ¤Ë + ´ð¤Å¤¤¤Æ¥³¥ó¥Æ¥ó¥Ä¤òÀ¸À®¤·¤Æ¤¤¤ë¤È¤­¤ËɬÍפˤʤê¤Þ¤¹¡£

+ +

+ <Files "mypaths.shtml">
+ + Options +Includes
+ SetOutputFilter INCLUDES
+ AcceptPathInfo On
+ + </Files> +

+ +
+
top
+

AccessFileName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:ʬ»¶ÀßÄê¥Õ¥¡¥¤¥ë¤Î̾Á°
¹½Ê¸:AccessFileName filename [filename] ...
¥Ç¥Õ¥©¥ë¥È:AccessFileName .htaccess
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤¹¤ë¤È¤­¡¢¥µ¡¼¥Ð¤Ï¥Ç¥£¥ì¥¯¥È¥ê¤Ë + ÂФ·¤Æʬ»¶ÀßÄê¥Õ¥¡¥¤¥ë¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ì¤Ð¡¢ + ¤½¤Î¥É¥­¥å¥á¥ó¥È¤Ø¤Î + ¥Ñ¥¹¾å¤Ë¤¢¤ëÁ´¤Æ¤Î¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¡¢¤³¤³¤Ç»ØÄꤵ¤ì¤¿Ì¾Á°¤Î°ìÍ÷¤ÎÃæ¤Ç + ºÇ½é¤Ë¸«¤Ä¤«¤Ã¤¿¥Õ¥¡¥¤¥ë¤ò¤½¤ì¤¾¤ìÀßÄê¥Õ¥¡¥¤¥ë¤È¤·¤ÆÆɤ߹þ¤ß¤Þ¤¹¡£Î㤨¤Ð:

+ +

+ AccessFileName .acl +

+ +

¤È¤¤¤¦ÀßÄ꤬¤¢¤ë¤È¡¢°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ̵¸ú¤Ë¤µ¤ì¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢ + ¥É¥­¥å¥á¥ó¥È /usr/local/web/index.html + ¤òÊÖ¤¹Á°¤Ë¡¢¥µ¡¼¥Ð¤Ï /.acl, /usr/.acl, + /usr/local/.acl, /usr/local/web/.acl ¤«¤é + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÆɤ߹þ¤ß¤Þ¤¹¡£

+ +

+ <Directory />
+ + AllowOverride None
+ + </Directory> +

+ +

»²¾È

+ +
+
top
+

AddDefaultCharset ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥ì¥¹¥Ý¥ó¥¹¤Î¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤¬ text/plain ¤¢¤ë¤¤¤Ï +text/html ¤Î¾ì¹ç¤ËÄɲ乤ë¥Ç¥Õ¥©¥ë¥È¤Î charset ¥Ñ¥é¥á¡¼¥¿
¹½Ê¸:AddDefaultCharset On|Off|charset
¥Ç¥Õ¥©¥ë¥È:AddDefaultCharset Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¥ì¥¹¥Ý¥ó¥¹¤Î¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤¬ text/plain + ¤¢¤ë¤¤¤Ï text/html + ¤Î¾ì¹ç¤Ë¸Â¤ê¤Þ¤¹¤¬¡¢¥ì¥¹¥Ý¥ó¥¹¤ËÄɲ乤ë¥á¥Ç¥£¥¢¥¿¥¤¥×¤Îʸ»ú¥»¥Ã¥È¥Ñ¥é¥á¡¼¥¿ + (ʸ»ú¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Î̾Á°) ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤò¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤷ¤Þ¤¹¡£ + ¤³¤ì¤Ï¥ì¥¹¥Ý¥ó¥¹ (ÌõÃí: ¥ì¥¹¥Ý¥ó¥¹¤Î HTML) Æâ¤Ç META + Í×ÁǤǻØÄꤵ¤ì¤¿¡¢¤É¤Î¤è¤¦¤Êʸ»ú¥»¥Ã¥È¤â̵¸ú¤Ë¤·¤Þ¤¹¤¬¡¢ + ºÇ½ªÅª¤ÊµóÆ°¤Ï¥æ¡¼¥¶¤Î¥¯¥é¥¤¥¢¥ó¥È¦¤ÎÀßÄê¤Ç·è¤Þ¤ê¤Þ¤¹¡£ + ¤³¤Îµ¡Ç½¤Ï AddDefaultCharset Off ¤È¤¤¤¦ÀßÄê¤Ç̵¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + AddDefaultCharset On ¤Ë¤¹¤ì¤Ð¡¢ + Apache ÆâÉô¤Î¥Ç¥Õ¥©¥ë¥Èʸ»ú¥»¥Ã¥È iso-8859-1 ¤ËÀßÄꤵ¤ì¤Þ¤¹¡£ + ¤½¤Î¾ charset ¤Ë»ØÄê¤Ç¤­¤ëÃͤǤ¢¤ì¤Ð¡¢¤É¤ó¤ÊÃͤǤâ»È¤¨¤Þ¤¹¡£ + »ØÄꤹ¤ëÃͤϡ¢MIME ¥á¥Ç¥£¥¢¥¿¥¤¥×¤È¤·¤Æ»È¤ï¤ì¤ë + IANA + ¤ËÅÐÏ¿¤µ¤ì¤Æ¤¤¤ëʸ»ú¥»¥Ã¥È̾¤Î¤¦¤Á¤Î°ì¤Ä¤Ë¤¹¤Ù¤­¤Ç¤¹¡£ + Î㤨¤Ð:

+ +

+ AddDefaultCharset utf-8 +

+ +

AddDefaultCharset ¤ò»È¤¦¤È¤­¤Ï¡¢Á´¤Æ¤Î¥Æ¥­¥¹¥È¥ê¥½¡¼¥¹¤¬ + »ØÄꤹ¤ëʸ»ú¥¨¥ó¥³¡¼¥É¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤Èʬ¤«¤Ã¤Æ¤¤¤Æ¡¢¤«¤Ä¡¢ + ¥ê¥½¡¼¥¹¤Î¸Ä¡¹¤Ëʸ»ú¥»¥Ã¥È¤ò»ØÄꤹ¤ë¤Î¤¬ÂçÊѤʾì¹ç¤Î¤ß¤Ç¤¹¡£ + Îã¤òµó¤²¤ë¤È¡¢¥ì¥¬¥·¡¼¤Ê CGI ¥¹¥¯¥ê¥×¥È¤Ê¤É¤Î¡¢Æ°Åª¤ËÀ¸À®¤µ¤ì¤ë + ¥³¥ó¥Æ¥ó¥Ä¤ò´Þ¤à¥ê¥½¡¼¥¹¤Ëʸ»ú¥»¥Ã¥È¥Ñ¥é¥á¡¼¥¿¤òÄɲ乤ë¾ì¹ç¤Ç¡¢ + ¥æ¡¼¥¶¤ÎÆþÎϥǡ¼¥¿¤¬½ÐÎϤËÆþ¤ê¡¢¥¯¥í¥¹¥µ¥¤¥È¥¹¥¯¥ê¥×¥Æ¥£¥ó¥°¤¬ + °ú¤­µ¯¤³¤µ¤ì¤¦¤ë¾ì¹ç¤Ç¤¹¡£¥Ç¥Õ¥©¥ë¥Èʸ»ú¥»¥Ã¥È¤ò¥»¥Ã¥È¤·¤¿¤È¤·¤Æ¤â¡¢ + ¥Ö¥é¥¦¥¶¤Î "ʸ»ú¥¨¥ó¥³¡¼¥É¤Î¼«Æ°ÁªÂò" µ¡Ç½¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¥æ¡¼¥¶¤ò + ¼é¤ë¤³¤È¤Ë¤Ï¤Ê¤é¤Ê¤¤¤Î¤Ç¡¢¤â¤Á¤í¤ó¤è¤êÎɤ¤²ò·èºö¤Ïñ¤Ë¥¹¥¯¥ê¥×¥È¤ò½¤Àµ + (¤¢¤ë¤¤¤Ïºï½ü) ¤¹¤ë¤³¤È¤Ç¤¹¡£

+ +

»²¾È

+ +
+
top
+

AddOutputFilterByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:MIME-type ¤Ë½ÐÎÏ¥Õ¥£¥ë¥¿¤ò³ä¤êÅö¤Æ¤ë
¹½Ê¸:AddOutputFilterByType filter[;filter...] MIME-type +[MIME-type] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Apache 2.0.33 °Ê¹ß¤Ç»ÈÍѲÄǽ¡£¤¿¤À¤· 2.1 °Ê¹ß¤ÇÈó¿ä¾©¡£
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï±þÅú¤Î MIME ¥¿¥¤¥× ¤Ë±þ¤¸¤Æ½ÐÎÏ¥Õ¥£¥ë¥¿¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ¤¿¤À¤·²¼¤ÇÀâÌÀ¤µ¤ì¤ëÍýͳ¤Ë¤è¤ê¡¢Ëܥǥ£¥ì¥¯¥Æ¥£¥Ö¤ÏÈó¿ä¾©¤Ç¤¹¡£ + ƱÅù¤Îµ¡Ç½¤Ï mod_filter ¤ÇÍøÍѤǤ­¤Þ¤¹¡£

+ +

¼¡¤ÎÎã¤Ï mod_deflate ¤Î DEFLATE ¥Õ¥£¥ë¥¿¤ò + »È¤Ã¤Æ¤¤¤Þ¤¹¡£text/html ¤È text/plain ¤Î + ¤¹¤Ù¤Æ¤Î½ÐÎÏ (ÀÅŪ¤Ê¤â¤Î¤âưŪ¤Ê¤â¤Î¤â) ¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤é¤ì¤ëÁ°¤Ë + °µ½Ì¤·¤Þ¤¹¡£

+ +

+ AddOutputFilterByType DEFLATE text/html text/plain +

+ +

Ê£¿ô¤Î¥Õ¥£¥ë¥¿¤Ç¥³¥ó¥Æ¥ó¥Ä¤ò½èÍý¤µ¤»¤¿¤¤¤È¤­¤Ï¡¢¤½¤ì¤¾¤ì¤Î̾Á°¤ò¥»¥ß¥³¥í¥ó¤Ç + ʬ¤±¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£³Æ¥Õ¥£¥ë¥¿¤ËÂФ·¤Æ + AddOutputFilterByType ¤ò°ì¤Ä¤º¤Ä½ñ¤¯¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

¼¡¤ÎÎã¤Ï text/html ¤Î¥¹¥¯¥ê¥×¥È¤Î¤¹¤Ù¤Æ¤Î½ÐÎϤò + ¤Þ¤º INCLUDES ¥Õ¥£¥ë¥¿¤Ç½èÍý¤·¡¢¤µ¤é¤Ë DEFLATE ¥Õ¥£¥ë¥¿¤Ë¤«¤±¤Þ¤¹¡£

+ +

+ <Location /cgi-bin/>
+ + Options Includes
+ AddOutputFilterByType INCLUDES;DEFLATE text/html
+ + </Location> +

+ +

Ãí:

+

AddOutputFilterByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê + Í­¸ú¤Ë¤·¤¿¥Õ¥£¥ë¥¿¤Ï¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï¡¢ÉôʬŪ¤â¤·¤¯¤Ï´°Á´¤ËŬÍѤµ¤ì¤Ê¤¤¤³¤È¤¬ + ¤¢¤ê¤Þ¤¹¡£Î㤨¤Ð¡¢MIME ¥¿¥¤¥× ¤¬·èÄê¤Ç¤­¤Ê¤¤¤È¤­¤Ë¤Ï + DefaultType ¤ÎÀßÄ꤬Ʊ¤¸¤À¤Ã¤¿¤È¤·¤Æ¤â¡¢ + DefaultType ÀßÄê¤ò»È¤¦¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+

¤·¤«¤·¡¢³Î¼Â¤Ë¥Õ¥£¥ë¥¿¤¬Å¬ÍѤµ¤ì¤ë¤è¤¦¤Ë¤·¤¿¤¤¤È¤­¤Ï¡¢¥ê¥½¡¼¥¹¤Ë + ÌÀ¼¨Åª¤Ë¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ò³ä¤êÅö¤Æ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤Ë¤ÏÎ㤨¤Ð + AddType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä + ForceType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¤¤Þ¤¹¡£ + (nph¤Ç¤Ê¤¤) CGI ¥¹¥¯¥ê¥×¥È¤Ç¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤òÀßÄꤹ¤ë¤È¤¤¤¦¤â¤Î¤Ç¤â + Âç¾æÉפǤ¹¡£

+ +

¥¿¥¤¥×Ëè¤Î½ÐÎÏ¥Õ¥£¥ë¥¿¤Ï¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤Ë¤Ï·è¤·¤ÆŬÍѤµ¤ì¤Þ¤»¤ó¡£

+
+ +

»²¾È

+ +
+
top
+

AllowEncodedSlashes ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:URL Ãæ¤ÎÉä¹æ²½¤µ¤ì¤¿¥Ñ¥¹Ê¬Î¥Ê¸»ú¤¬Àè¤ËÅÁ¤¨¤é¤ì¤ë¤Î¤òµö²Ä¤¹¤ë¤«¤É¤¦¤«¤ò +·èÄꤹ¤ë
¹½Ê¸:AllowEncodedSlashes On|Off
¥Ç¥Õ¥©¥ë¥È:AllowEncodedSlashes Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Apache 2.0.46 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

AllowEncodedSlashes ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÉä¹æ²½¤µ¤ì¤¿ + ¥Ñ¥¹Ê¬Î¥Ê¸»ú (/ ¤Ï %2F¡¢¤µ¤é¤Ë¥·¥¹¥Æ¥à¤Ë¤è¤Ã¤Æ¤Ï + \ ¤ËÂбþ¤¹¤ë %5C) ¤¬Â¸ºß¤¹¤ë URL ¤Î»ÈÍѤò + µö²Ä¤¹¤ë¤«¤É¤¦¤«¤ò·èÄꤷ¤Þ¤¹¡£Ä̾ï¤Ï¤½¤Î¤è¤¦¤Ê URL ¤Ï 404 (Not found) ¥¨¥é¡¼ + ¤ÇµñÈݤµ¤ì¤Þ¤¹¡£

+ +

AllowEncodedSlashes On ¤Ë¤è¤ë + ¥Ñ¥¹Ê¬Î¥Ê¸»ú¤Î»ÈÍѤϡ¢PATH_INFO ¤È¹ç¤ï¤»¤Æ + »È¤¦¤È¤­¤Ë°ìÈÖÌò¤ËΩ¤Á¤Þ¤¹¡£

+ +

Ãí

+

Éä¹æ²½¤µ¤ì¤¿¥¹¥é¥Ã¥·¥å¤òµö²Ä¤¹¤ë¤³¤È¤Ï¡¢Éü¹æ¤ò¤¹¤ë¤³¤È¤ò + °ÕÌ£¤·¤Þ¤»¤ó¡£%2F ¤ä (´Ø·¸¤¹¤ë¥·¥¹¥Æ¥à¤Ç¤Î) + %5C ¤Ï¡¢Â¾¤ÎÉôʬ¤¬Éü¹æ¤µ¤ì¤¿ URL ¤ÎÃæ¤Ç¤â¤½¤Î¤Þ¤Þ¤Î·Á¼°¤Ç + »Ä¤µ¤ì¤Þ¤¹¡£

+
+ +

»²¾È

+ +
+
top
+

AllowOverride ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:.htaccess ¤Çµö²Ä¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¼ïÎà
¹½Ê¸:AllowOverride All|None|directive-type +[directive-type] ...
¥Ç¥Õ¥©¥ë¥È:AllowOverride All
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¥µ¡¼¥Ð¤¬ (AccessFileName ¤Ë¤è¤Ã¤Æ»ØÄꤵ¤ì¤¿) + .htaccess ¥Õ¥¡¥¤¥ë¤ò¸«¤Ä¤±¤¿»þ¡¢¤½¤Î¥Õ¥¡¥¤¥ë¤ÎÃæ¤Ç + Àë¸À¤µ¤ì¤¿¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¤è¤êÁ°¤ËÄêµÁ¤µ¤ì¤¿ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ¾å½ñ¤­¤Ç¤­¤ë¤«¤òÃΤëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

<Directory> ¥»¥¯¥·¥ç¥ó¤Ç¤Î¤ß»ÈÍѲÄǽ

+ AllowOverride ¤ÏÀµµ¬É½¸½Ìµ¤·¤Î<Directory> + ¥»¥¯¥·¥ç¥ó¤Ç¤Î¤ßÍ­¸ú¤Ç¡¢<Location> ¤ä <DirectoryMatch> + ¤ä <Files> ¥»¥¯¥·¥ç¥ó¤Ç¤Ï̵¸ú¤Ç¤¹¡£ +
+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò None ¤ËÀßÄꤹ¤ë¤È¡¢.htaccess ¥Õ¥¡¥¤¥ë¤Ï´°Á´¤Ë + ̵»ë¤µ¤ì¤Þ¤¹¡£ + ¤³¤Î¾ì¹ç¡¢¥µ¡¼¥Ð¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î .htaccess ¥Õ¥¡¥¤¥ë¤òÆɤळ¤È¤ò + »î¤ß¤µ¤¨¤·¤Þ¤»¤ó¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ All ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë»þ¤Ë¤Ï¡¢ + .htaccess ¤È¤¤¤¦ ¥³¥ó¥Æ¥­¥¹¥È ¤ò»ý¤Ä + Á´¤Æ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ÍøÍѤǤ­¤Þ¤¹¡£

+ +

directive-type ¤Ë¤Ï¡¢°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö·²¤Î + ¥­¡¼¥ï¡¼¥É¤Î¤É¤ì¤«¤ò»ØÄꤷ¤Þ¤¹¡£

+ +
+
AuthConfig
+ +
+ + ǧ¾Ú¤Ë´Ø¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î»ÈÍѤòµö²Ä¤¹¤ë (AuthDBMGroupFile, + AuthDBMUserFile, + AuthGroupFile, + AuthName, + AuthType, AuthUserFile, Require ¤Ê¤É)¡£
+ +
FileInfo
+ +
+ ¥É¥­¥å¥á¥ó¥È¥¿¥¤¥×¤òÀ©¸æ¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö (DefaultType, ErrorDocument, ForceType, LanguagePriority, + SetHandler, SetInputFilter, SetOutputFilter, + mod_mime ¤Î Add* ¤È Remove* + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ê¤É)¡¢ + ¥É¥­¥å¥á¥ó¥È¤Î¥á¥¿¥Ç¡¼¥¿¤òÀ©¸æ¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö (Header, RequestHeader, SetEnvIf, SetEnvIfNoCase, BrowserMatch, CookieExpires, CookieDomain, CookieStyle, CookieTracking, CookieName), + mod_rewrite ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö RewriteEngine, RewriteOptions, RewriteBase, RewriteCond, RewriteRule) ¤È + mod_actions ¤Î + Action + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î»ÈÍѤòµö²Ä¤¹¤ë¡£
+ +
Indexes
+ +
+ ¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤òÀ©¸æ¤¹¤ë¤¿¤á¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î»ÈÍѤòµö²Ä¤¹¤ë + (AddDescription, + AddIcon, AddIconByEncoding, + AddIconByType, + DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName + ¤Ê¤É)¡£
+ +
Limit
+ +
+ ¥Û¥¹¥È¤Ø¤Î¥¢¥¯¥»¥¹À©¸æ¤ò¹Ô¤¦¤¿¤á¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î»ÈÍѤòµö²Ä¤¹¤ë (Allow, Deny, Order).
+ +
Options[=Option,...]
+ +
+ ÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤ª¤±¤ëµ¡Ç½¤ò»ØÄꤹ¤ë¤¿¤á¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î»ÈÍѤòµö²Ä¤¹¤ë + (Options ¤È + XBitHack)¡£ + Options ¤ÇÀßÄꤹ¤ë¥ª¥×¥·¥ç¥ó + ¤ò¡¢(¶õÇò¤ò´Þ¤á¤Ê¤¤) ¥³¥ó¥Þ¶èÀÚ¤ê¤Î¥ê¥¹¥È¤Ë¤·¤ÆÅù¹æ¤Î¸å¤Ë³¤±¤ë¤³¤È¤Ç + ÀßÄê¤Ç¤­¤Þ¤¹¡£
+
+ +

Îã:

+ +

+ AllowOverride AuthConfig Indexes +

+ +

¾å¤ÎÎã¤Ç¤Ï AuthConfig ¤È Indexes ¤Î¤É¤Á¤é¤Ë¤â + °¤µ¤Ê¤¤¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¹¤Ù¤ÆÆâÉô¥µ¡¼¥Ð¥¨¥é¡¼¤ò°ú¤­µ¯¤³¤·¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

AuthName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:HTTP ǧ¾Ú¤Îǧ²ÄÎΰè (ÌõÃí: realm)
¹½Ê¸:AuthName auth-domain
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ¹¤ëǧ²ÄÎΰè (ÌõÃí: realm) + ¤Î̾Á°¤ò»ØÄꤷ¤Þ¤¹¡£ + ǧ²ÄÎΰè¤Ï¡¢ÍøÍѼԤ¬¤É¤Î¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤òÁ÷¿®¤¹¤ì¤Ð¤è¤¤¤Î¤«¤ò + ¥¯¥é¥¤¥¢¥ó¥È¤Ë¶µ¤¨¤ë¤¿¤á¤ËÍøÍѤ·¤Þ¤¹¡£ + AuthName ¤Ï°ì¤Ä¤Î°ú¿ô¤ò¤È¤ê¡¢ + ¥¹¥Ú¡¼¥¹¤¬´Þ¤Þ¤ì¤ë¾ì¹ç¤Ë¤Ï¡¢ + °úÍÑÉä¤Ç³ç¤é¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + AuthType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä + Require ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¡¢ + AuthUserFile ¤ä + AuthGroupFile ¤Ê¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + °ì½ï¤ËÍøÍѤ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

Î㤨¤Ð:

+ +

+ AuthName "Top Secret" +

+ +

¤³¤³¤Ç AuthName ¤Ë»ØÄꤷ¤¿Ê¸»úÎ󤬡¢ + ÂçÉôʬ¤Î¥Ö¥é¥¦¥¶¤Î¥Ñ¥¹¥ï¡¼¥É¥À¥¤¥¢¥í¥°¤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

AuthType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥æ¡¼¥¶Ç§¾Ú¤Î¼ïÎà
¹½Ê¸:AuthType Basic|Digest
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÂоݥǥ£¥ì¥¯¥È¥ê¤ÇÍøÍѤ¹¤ë¥æ¡¼¥¶¡¼Ç§¾Ú¤Î¼ïÎà¤òÁª¤Ó¤Þ¤¹¡£ + »ÈÍѤǤ­¤ëǧ¾ÚÊý¼°¤Ï Basic (mod_auth_basic + ¤Ç¼ÂÁõ) ¤È Digest (mod_auth_digest + ¤Ç¼ÂÁõ) ¤Ç¤¹¡£

+ +

ǧ¾Ú¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢AuthName + ¤È Require ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤â + »È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£¤½¤ì¤Ë²Ã¤¨¤Æǧ¾Ú¥×¥í¥Ð¥¤¥À¥â¥¸¥å¡¼¥ë¤Î + mod_authn_file Åù¤È¡¢¾µÇ§¥â¥¸¥å¡¼¥ë + mod_authz_user Åù¤â¥µ¡¼¥Ð¤ËÁȤ߹þ¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

CGIMapExtension ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:CGI ¥¹¥¯¥ê¥×¥È¤Î¥¤¥ó¥¿¡¼¥×¥ê¥¿¤Î°ÌÃÖ¤òÄ´¤Ù¤ë¤¿¤á¤Î¼êË¡
¹½Ê¸:CGIMapExtension cgi-path .extension
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:NetWare ¤Î¤ß
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache ¤¬ CGI ¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤¹¤ë¤¿¤á¤Î + ¥¤¥ó¥¿¡¼¥×¥ê¥¿¤òõ¤¹ÊýË¡¤òÀ©¸æ¤·¤Þ¤¹¡£ + Î㤨¤Ð¡¢CGIMapExtension sys:\foo.nlm .foo ¤ÈÀßÄꤹ¤ë¤È + .foo ¤È¤¤¤¦³ÈÄ¥»Ò¤Î¤¹¤Ù¤Æ¤Î CGI ¥¹¥¯¥ê¥×¥È¤Ï FOO ¥¤¥ó¥¿¡¼¥×¥ê¥¿¤Ë + ÅϤµ¤ì¤Þ¤¹¡£

+ +
+
top
+

ContentDigest ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:Content-MD5 HTTP ±þÅú¥Ø¥Ã¥À¤ÎÀ¸À®¤òÍ­¸ú¤Ë¤¹¤ë
¹½Ê¸:ContentDigest On|Off
¥Ç¥Õ¥©¥ë¥È:ContentDigest Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Options
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢RFC1864 µÚ¤Ó RFC2068 ¤Ë¤ª¤¤¤ÆÄêµÁ¤µ¤ì¤Æ¤¤¤ë + Content-MD5 ¥Ø¥Ã¥À¡¼¤ÎÀ¸À®¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£

+ +

MD5 ¤Ï¡¢Ç¤°ÕĹ¤Î¥Ç¡¼¥¿¤Î¡Ö¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È¡×(¡Ö»ØÌæ¡× + ¤Èɽ¸½¤µ¤ì¤ë¤³¤È¤â¤¢¤ë) ¤ò·×»»¤¹¤ë¥¢¥ë¥´¥ê¥º¥à¤Ç¡¢ + ¥Ç¡¼¥¿¤ÎÊѹ¹¤¬¤¢¤Ã¤¿¾ì¹ç¤Ë¤ÏÈó¾ï¤Ë¹â¤¤¿®ÍêÅ٤ǥá¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È¤ËÊѹ¹¤¬ + È¿±Ç¤µ¤ì¤Þ¤¹¡£

+ +

Content-MD5 ¥Ø¥Ã¥À¤Ï¡¢¥¨¥ó¥É¥Ä¡¼¥¨¥ó¥É¤Ç + ¥¨¥ó¥Æ¥£¥Æ¥£¥Ü¥Ç¥£¡¼¤Ë´Þ¤Þ¤ì¤ë¥á¥Ã¥»¡¼¥¸¤Î´°Á´À­¥Á¥§¥Ã¥¯ + (Message Integrity Check - MIC)¤òÄ󶡤·¤Þ¤¹¡£ + ¤³¤Î¥Ø¥Ã¥À¤òÄ´¤Ù¤ë¤³¤È¤Ç¡¢¥×¥í¥­¥·¤ä¥¯¥é¥¤¥¢¥ó¥È¤Ï¡¢ + ÅÓÃæ·ÐÏ©¤Ë¤ª¤±¤ë¥¨¥ó¥Æ¥£¥Æ¥£¥Ü¥Ç¥£¤Îͽ´ü¤»¤ÌÊѹ¹¤Ê¤É¤ò + ¸¡½Ð¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¥Ø¥Ã¥À¤ÎÎã:

+ +

+ Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA== +

+ +

¥ê¥¯¥¨¥¹¥ÈËè¤Ë¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È¤ò·×»»¤¹¤ë (Ãͤϥ­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó) + ¤³¤È¤«¤é¡¢ + ¥µ¡¼¥Ð¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤¬Äã²¼¤¹¤ë¤³¤È¤Ë¤Ä¤¤¤ÆÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Content-MD5¤Ï¡¢core µ¡Ç½¤Ë¤è¤ê½èÍý¤µ¤ì¤¿ + ¥É¥­¥å¥á¥ó¥È¤òÁ÷¤ë¤È¤­¤Î¤ßÍ­¸ú¤Ç¤¢¤ê¡¢ + SSI ¥É¥­¥å¥á¥ó¥È¤ä CGI ¥¹¥¯¥ê¥×¥È¤Î½ÐÎÏ¡¢¥Ð¥¤¥È¥ì¥ó¥¸¤ò»ØÄꤷ¤¿ + ±þÅú¤Î¾ì¹ç¤Ë¤Ï¤³¤Î¥Ø¥Ã¥À¤ÏÉÕÍ¿¤µ¤ì¤Þ¤»¤ó¡£ +

+ +
+
top
+

DefaultType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ò·èÄê¤Ç¤­¤Ê¤¤¤È¤­¤Ë +Á÷¤é¤ì¤ë MIME ¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×
¹½Ê¸:DefaultType MIME-type
¥Ç¥Õ¥©¥ë¥È:DefaultType text/plain
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¥µ¡¼¥Ð¤Ï¡¢MIME ¥¿¥¤¥× + ¤Î¥Þ¥Ã¥Ô¥ó¥°¤Ç¤Ï·èÄê¤Ç¤­¤Ê¤¤ + ¥É¥­¥å¥á¥ó¥È¤ÎÁ÷¿®¤òÍ׵ᤵ¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£

+ +

¥µ¡¼¥Ð¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤Î¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÄÌÃΤ¹¤ëɬÍפ¬ + ¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢¤³¤Î¤è¤¦¤Ë¥¿¥¤¥×¤¬Ì¤ÃΤξì¹ç¤Ï + DefaultType ¤Ç»ØÄꤵ¤ì¤¿¥¿¥¤¥×¤òÍøÍѤ·¤Þ¤¹¡£ + Îã:

+ +

+ DefaultType image/gif +

+ +

¤³¤ì¤Ï .gif ¤È¤¤¤¦³ÈÄ¥»Ò¤¬¥Õ¥¡¥¤¥ë̾¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Ê¤¤ + ¿¤¯¤Î GIF ²èÁü¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ËŬ¤·¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£

+ +

ForceType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + °ã¤Ã¤Æ¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Ç¥Õ¥©¥ë¥È¤Î MIME ¥¿¥¤¥×¤òÄ󶡤¹¤ë¤À¤±¤Ç + ¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò´Þ¤á¡¢ + ¥á¥Ç¥£¥¢¥¿¥¤¥×¤ò·èÄê¤Ç¤­¤ë¾¤Î MIME ¥¿¥¤¥×¤ÎÄêµÁ¤¬¤¢¤ì¤Ð + ¤³¤Î¥Ç¥Õ¥©¥ë¥È¤Ï¾å½ñ¤­¤µ¤ì¤Þ¤¹¡£

+ +
+
top
+

<Directory> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:»ØÄê¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ç¥£¥ì¥¯¥È¥ê¤È¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤È¤Î¤ß¤Ë +ŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
¹½Ê¸:<Directory directory-path> +... </Directory>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

»ØÄꤵ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤È¤½¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤Î¤ß + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òŬÍѤµ¤»¤ë¤¿¤á¤Ë¤Ï¡¢ + <Directory> ¤È + </Directory> ¤òÂФȤ·¤Æ¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö·²¤ò°Ï¤¤¤Þ¤¹¡£ + ¤½¤ÎÃæ¤Ë¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥ê¥³¥ó¥Æ¥­¥¹¥È¤Çµö²Ä¤µ¤ì¤¿Á´¤Æ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ÍøÍѤǤ­¤Þ¤¹¡£ + directive-path ¤Ï¡¢¥Õ¥ë¥Ñ¥¹¤â¤·¤¯¤Ï Unix ¤Î¥·¥§¥ë·Á¼°¤Î + ¥ï¥¤¥ë¥É¥«¡¼¥É¤ò»ØÄꤷ¤Þ¤¹¡£ + ? ¤ÏǤ°Õ¤Î 1 ʸ»ú¡¢* ¤ÏǤ°Õ¤Îʸ»úÎó¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + ¥·¥§¥ë¤Ë¤ª¤±¤ë»ØÄêƱÍÍ¡¢Ê¸»ú¤ÎÈϰϤò [] ¤Ç»ØÄê¤Ç¤­¤Þ¤¹¡£ + ¥ï¥¤¥ë¥É¥«¡¼¥É¤Ï `/' ʸ»ú¤Ë¤Ï¥Þ¥Ã¥Á¤·¤Þ¤»¤ó¤Î¤Ç¡¢ + /home/user/public_html ¤Ë¤Ï + <Directory /*/public_html> ¤Ï¥Þ¥Ã¥Á¤·¤Þ¤»¤ó¤¬¡¢ + <Directory /home/*/public_html> ¤Ï¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + Îã:

+ +

+ <Directory /usr/local/httpd/htdocs>
+ + Options Indexes FollowSymLinks
+ + </Directory> +

+ +
+

directory-path °ú¿ô¤Ë¤ÏÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤: ¤½¤Î°ú¿ô¤Ï +Apache ¤¬¥Õ¥¡¥¤¥ë¤ò¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë»È¤¦¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ñ¥¹¤Ë +¤½¤Î¤Þ¤Þ¥Þ¥Ã¥Á¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤¢¤ë <Directory> ¤Ë +ŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Ê̤Υ·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò¤¿¤É¤Ã¤¿¤ê¤·¤Æ +Ʊ¤¸¥Ç¥£¥ì¥¯¥È¥ê¤ò°ã¤¦¥Ñ¥¹¤Ç¥¢¥¯¥»¥¹¤·¤¿¾ì¹ç¤Ë¤ÏŬÍѤµ¤ì¤Þ¤»¤ó¡£

+
+ +

~ ¤È¤¤¤¦Ê¸»ú¤ò + Éղ乤뤳¤È¤ÇÀµµ¬É½¸½¤òÍøÍѤ¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + Î㤨¤Ð:

+ +

+ <Directory ~ "^/www/.*/[0-9]{3}"> +

+ +

¤È¤¤¤Ã¤¿»ØÄê¤Î¾ì¹ç¡¢/www/ °Ê²¼¤Ë¤¢¤ë¿ô»ú + 3 ʸ»ú¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£

+ +

¤â¤·Ê£¿ô¤Î (Àµµ¬É½¸½°Ê³°¤Î) <Directory>¥»¥¯¥·¥ç¥ó¤¬ + ¥É¥­¥å¥á¥ó¥È¤ò´Þ¤à¥Ç¥£¥ì¥¯¥È¥ê (¤ä¤½¤Î¾å°Ì¥Ç¥£¥ì¥¯¥È¥ê¤Î¤É¤ì¤«) ¤È¥Þ¥Ã¥Á¤·¤¿¤Ê¤é¤Ð¡¢ + .htaccess ¥Õ¥¡¥¤¥ë¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤âÆɤ߹þ¤ß¤Ä¤Ä¡¢ + û¤¤¥Ñ¥¹¤«¤é½ç¤ËŬÍѤµ¤ì¤Þ¤¹¡£ + Î㤨¤Ð¡¢

+ +

+ <Directory />
+ + AllowOverride None
+ + </Directory>
+
+ <Directory /home/>
+ + AllowOverride FileInfo
+ + </Directory> +

+ +

¤ÈÀßÄꤷ¡¢¥É¥­¥å¥á¥ó¥È /home/web/dir/doc.html ¤Ø¤Î + ¥¢¥¯¥»¥¹¤¬¤¢¤Ã¤¿¾ì¹ç¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤ËÆ°ºî¤·¤Þ¤¹:

+ +
    +
  • AllowOverride None ¤¬Å¬ÍѤµ¤ì¤ë¡£ + (.htaccess ¥Õ¥¡¥¤¥ë¤Ï̵¸ú¤Ë¤Ê¤ë)
    • + +
  • AllowOverride FileInfo ¤¬Å¬ÍѤµ¤ì¤ë + (/home ¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ·¤Æ)¡£
    • + +
  • /home/.htaccess, /home/web/.htaccess, + /home/web/dir/.htaccess ¤Î½ç¤Ë¤½¤ì¤é¤Î¥Õ¥¡¥¤¥ëÃæ¤Î + FileInfo ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Å¬ÍѤµ¤ì¤ë¡£
    • +
+ +

Àµµ¬É½¸½¤Ï¡¢Ä̾ï¤Î¥»¥¯¥·¥ç¥ó¤¬¤¹¤Ù¤ÆŬÍѤµ¤ì¤ë¤Þ¤Ç + ¹Í褵¤ì¤Þ¤»¤ó¡£ + ¤½¤Î¸å¡¢Á´¤Æ¤ÎÀµµ¬É½¸½¤¬ÀßÄê¥Õ¥¡¥¤¥ë¤Ë¸½¤ì¤¿½ç¤Ç»î¤µ¤ì¤Þ¤¹¡£ + Î㤨¤Ð¡¢°Ê²¼¤Î¤è¤¦¤Ê¾ì¹ç¤Ë

+ +

+ <Directory ~ abc$>
+ + # ... directives here ...
+ + </Directory> +

+ +

Àµµ¬É½¸½¤Î¥»¥¯¥·¥ç¥ó¤Ï¤¹¤Ù¤Æ¤ÎÄ̾ï¤Î <Directory> ¤È + .htaccess ¤ÎŬÍѤ¬½ª¤ï¤ë¤Þ¤Ç¹Í褵¤ì¤Þ¤»¤ó¡£ + ¤½¤Î¸å¤Ç¡¢Àµµ¬É½¸½¤Ï /home/abc/public_html/abc ¤Ë¥Þ¥Ã¥Á¤·¡¢ + Âбþ¤¹¤ë <Directory> ¤¬Å¬ÍѤµ¤ì¤Þ¤¹¡£

+ +

Apache ¤Î¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï <Directory /> ¤Ø¤Î¥¢¥¯¥»¥¹¤Ï + Allow from All ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤ì¤Ï¡¢URL ¤«¤é¥Þ¥Ã¥×¤µ¤ì¤¿¤É¤Î¥Õ¥¡¥¤¥ë¤Ç¤â Apache ¤ÏÁ÷¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£ + ¤³¤ì¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤ÆÊѹ¹¤¹¤ë¤³¤È¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

+ <Directory />
+ + Order Deny,Allow
+ Deny from All
+ + </Directory> +

+ +

¤½¤·¤Æ¥¢¥¯¥»¥¹¤ò²Äǽ¤Ë¤·¤¿¤¤¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ·¤Æ + ¸ÄÊ̤ËÀßÄꤹ¤ì¤Ð¤è¤¤¤Ç¤·¤ç¤¦¡£ + ¤³¤Î¤¢¤¿¤ê¤Ë¤Ä¤¤¤Æ¤Ï¡¢¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤¹¤ë¥³¥Ä¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

¥Ç¥£¥ì¥¯¥È¥ê¥»¥¯¥·¥ç¥ó¤Ï httpd.conf ¥Õ¥¡¥¤¥ë½ñ¤­¤Þ¤¹¡£ + <Directory> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÆþ¤ì»Ò¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤º¡¢ + <Limit> ¤ä <LimitExcept> ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤Ë¤â + µ­½Ò¤Ç¤­¤Þ¤»¤ó¡£

+ + +

»²¾È

+ +
+
top
+

<DirectoryMatch> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:Àµµ¬É½¸½¤Ë¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ç¥£¥ì¥¯¥È¥ê¤È +¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤È¤Î¤ß¤ËŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
¹½Ê¸:<DirectoryMatch regex> +... </DirectoryMatch>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

<Directory> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈƱÍͤˡ¢<DirectoryMatch> + ¤È </DirectoryMatch> ¤Ï»ØÄꤵ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤È + ¤½¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤Î¤ßŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö·²¤ò°Ï¤¤¤Þ¤¹¡£ + ¤·¤«¤·¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï°ú¿ô¤È¤·¤ÆÀµµ¬É½¸½¤ò¤È¤ê¤Þ¤¹¡£Î㤨¤Ð:

+ +

+ <DirectoryMatch "^/www/(.+/)?[0-9]{3}"> +

+ +

¤Ï /www/ °Ê²¼¤Ë¤¢¤ë¿ô»ú 3 ʸ»ú¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£

+ + +

»²¾È

+ +
+
top
+

DocumentRoot ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¦¥§¥Ö¤«¤é¸«¤¨¤ë¥á¥¤¥ó¤Î¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼¤Ë¤Ê¤ë +¥Ç¥£¥ì¥¯¥È¥ê
¹½Ê¸:DocumentRoot directory-path
¥Ç¥Õ¥©¥ë¥È:DocumentRoot /usr/local/apache/htdocs
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢httpd + ¤¬¥Õ¥¡¥¤¥ë¤òÄ󶡤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤òÀßÄꤷ¤Þ¤¹¡£ + Alias ¤Î¤è¤¦¤Ê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¥Þ¥Ã¥Á¤·¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢ + ¥É¥­¥å¥á¥ó¥È¤Î (ÌõÃí:¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î) ¥Ñ¥¹¤òÀ¸À®¤¹¤ë¤¿¤á¤Ë¡¢ + ¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿ URL ¤Î¥Ñ¥¹Éôʬ¤ò¥É¥­¥å¥á¥ó¥È¥ë¡¼¥È¤ËÉÕÍ¿¤·¤Þ¤¹¡£ + Îã:

+ +

+ DocumentRoot /usr/web +

+ +

¤³¤Î¾ì¹ç¡¢ + http://www.my.host.com/index.html ¤Ø¤Î¥¢¥¯¥»¥¹¤¬¤¢¤ì¤Ð + /usr/web/index.html ¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£ + directory-path ¤¬ÀäÂХѥ¹¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢ + ServerRoot + ¤«¤é¤ÎÁêÂХѥ¹¤È¤ß¤Ê¤µ¤ì¤Þ¤¹¡£

+ +

DocumentRoot ¤ÏºÇ¸å¤Î¥¹¥é¥Ã¥·¥å̵¤·¤Ç + »ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

EnableMMAP ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:ÇÛÁ÷Ãæ¤Ë¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤à¤¿¤á¤Ë¥á¥â¥ê¥Þ¥Ã¥Ô¥ó¥°¤ò +»È¤¦¤«¤É¤¦¤«
¹½Ê¸:EnableMMAP On|Off
¥Ç¥Õ¥©¥ë¥È:EnableMMAP On
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÇÛÁ÷Ãæ¤Ë¥Õ¥¡¥¤¥ë¤ÎÆâÍƤòÆɤ߹þ¤àɬÍפ¬¤¢¤ë¤È¤­¤Ë + httpd ¤¬¥á¥â¥ê¥Þ¥Ã¥Ô¥ó¥°¤ò»È¤¦¤«¤É¤¦¤«¤òÀ©¸æ¤·¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢ + Î㤨¤Ð¡¢mod_include ¤ò»È¤Ã¤Æ SSI ¥Õ¥¡¥¤¥ë¤òÇÛÁ÷ + ¤¹¤ë¤È¤­¤Î¤è¤¦¤Ë¡¢¥Õ¥¡¥¤¥ë¤ÎÅÓÃæ¤Î¥Ç¡¼¥¿¤ò¥¢¥¯¥»¥¹¤¹¤ëɬÍפ¬¤¢¤ë¤È¤­¤Ë¤Ï + Apache ¤Ï OS ¤¬¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ì¤Ð¥Õ¥¡¥¤¥ë¤ò¥á¥â¥ê¤Ë¥Þ¥Ã¥×¤·¤Þ¤¹¡£

+ +

+ ¤³¤Î¥á¥â¥ê¥Þ¥Ã¥×¤ÏÀ­Ç½¤Î¸þ¾å¤ò»ý¤¿¤é¤¹¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¤·¤«¤·¡¢´Ä¶­¤Ë¤è¤Ã¤Æ¤Ï±¿ÍѾå¤ÎÌäÂê¤òËɤ°¤¿¤á¤Ë¥á¥â¥ê¥Þ¥Ã¥Ô¥ó¥°¤ò + »ÈÍѤ·¤Ê¤¤¤è¤¦¤Ë¤·¤¿Êý¤¬Îɤ¤¾ì¹ç¤â¤¢¤ê¤Þ¤¹:

+ +
    +
  • ¥Þ¥ë¥Á¥×¥í¥»¥Ã¥µ¥·¥¹¥Æ¥à¤ÎÃæ¤Ë¤Ï¥á¥â¥ê¥Þ¥Ã¥Ô¥ó¥°¤ò¤¹¤ë¤È + httpd ¤ÎÀ­Ç½¤¬Íî¤Á¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
    • +
  • NFS ¥Þ¥¦¥ó¥È¤µ¤ì¤¿ DocumentRoot + ¤Ç¤Ï¡¢httpd ¤¬¥á¥â¥ê¥Þ¥Ã¥×¤·¤Æ¤¤¤ë´Ö¤Ë¥Õ¥¡¥¤¥ë¤¬ºï½ü¤µ¤ì¤¿¤ê + û¤¯¤Ê¤Ã¤¿¤ê¤·¤¿¤È¤­¤Ëµ¯¤³¤ë¥»¥°¥á¥ó¥Æ¡¼¥·¥ç¥ó¥Õ¥©¡¼¥ë¥È¤Î¤¿¤á¤Ë + httpd ¤¬¥¯¥é¥Ã¥·¥å¤¹¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
    • +
+ +

¤³¤ì¤é¤ÎÌäÂê¤ËÅö¤Æ¤Ï¤Þ¤ë¥µ¡¼¥Ð¤ÎÀßÄê¤Î¾ì¹ç¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ + ¥Õ¥¡¥¤¥ë¤ÎÇÛÁ÷»þ¤Î¥á¥â¥ê¥Þ¥Ã¥Ô¥ó¥°¤ò»ÈÍÑÉԲĤˤ·¤Æ¤¯¤À¤µ¤¤:

+ +

+ EnableMMAP Off +

+ +

NFS ¥Þ¥¦¥ó¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢ÌäÂê¤Î¤¢¤ë¥Õ¥¡¥¤¥ë¤Ë¤Î¤ßÌÀ¼¨Åª¤Ë + ¤³¤Îµ¡Ç½¤ò»ÈÍÑÉԲĤˤ·¤Þ¤¹:

+ +

+ <Directory "/path-to-nfs-files"> + + EnableMMAP Off + + </Directory> +

+ +
+
top
+

EnableSendfile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Î¥¯¥é¥¤¥¢¥ó¥È¤Ø¤ÎÇÛÁ÷»þ¤Ë¥«¡¼¥Í¥ë¤Î sendfile ¥µ¥Ý¡¼¥È¤ò +»È¤¦¤«¤É¤¦¤«
¹½Ê¸:EnableSendfile On|Off
¥Ç¥Õ¥©¥ë¥È:EnableSendfile On
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.0.44 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ë¥Õ¥¡¥¤¥ë¤ÎÆâÍƤòÁ÷¤ë¤È¤­¤Ë + httpd ¤¬¥«¡¼¥Í¥ë¤Î + sendfile ¥µ¥Ý¡¼¥È¤ò»È¤¦¤«¤É¤¦¤«¤òÀ©¸æ¤·¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢ + Î㤨¤ÐÀÅŪ¤Ê¥Õ¥¡¥¤¥ë¤ÎÇÛÁ÷¤Î¤è¤¦¤Ë¡¢¥ê¥¯¥¨¥¹¥È¤Î½èÍý¤Ë¥Õ¥¡¥¤¥ë¤Î + ÅÓÃæ¤Î¥Ç¡¼¥¿¤Î¥¢¥¯¥»¥¹¤òɬÍפȤ·¤Ê¤¤¤È¤­¤Ë¤Ï¡¢Apache ¤Ï OS ¤¬ + ¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ì¤Ð¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤à¤³¤È¤Ê¤¯ sendfile ¤ò»È¤Ã¤Æ + ¥Õ¥¡¥¤¥ë¤ÎÆâÍƤòÁ÷¤ê¤Þ¤¹¡£

+ +

sendfile ¤Ï read ¤È send ¤òÊÌ¡¹¤Ë¹Ô¤Ê¤¦¤³¤È¤È¡¢¥Ð¥Ã¥Õ¥¡¤Î³ä¤êÅö¤Æ¤ò + ²óÈò¤·¤Þ¤¹¡£¤·¤«¤·¡¢¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤ä¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÃæ¤Ë¤Ï + ±¿ÍѾå¤ÎÌäÂê¤òÈò¤±¤ë¤¿¤á¤Ë¤³¤Îµ¡Ç½¤ò»ÈÍÑÉԲĤˤ·¤¿Êý¤¬Îɤ¤¾ì¹ç¤¬¤¢¤ê¤Þ¤¹:

+ +
    +
  • ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤ÎÃæ¤Ë¤Ï¥Ó¥ë¥É¥·¥¹¥Æ¥à¤¬¸¡ÃΤǤ­¤Ê¤«¤Ã¤¿¡¢²õ¤ì¤¿ + sendfile ¤Î¥µ¥Ý¡¼¥È¤¬Â¸ºß¤¹¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤ÏÆÃ¤Ë + ¥Ð¥¤¥Ê¥ê¤¬Ê̤Υޥ·¥ó¤Ç¥Ó¥ë¥É¤µ¤ì¡¢²õ¤ì¤¿ sendfile ¤Î¤¢¤ë¥Þ¥·¥ó¤Ë + °ÜÆ°¤·¤¿¤È¤­¤Ëµ¯¤³¤ê¤Þ¤¹¡£
    • +
  • Linux ¤Ç¤Ï¡¢sendfile ¤òÍѤ¤¤ë¤È¡¢ + IPv6 »ÈÍÑ»þ¤Ë¸ºß¤¹¤ëÆÃÄê¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤Î TCP-checksum + ¥ª¥Õ¥í¡¼¥É¤Î¥Ð¥°¤òƧ¤ó¤Ç¤·¤Þ¤¤¤Þ¤¹¡£
    • +
  • Itanium ¤ÇÆ°¤¤¤Æ¤¤¤ë Linux ¤Ç¡¢sendfile ¤Ï 2GB °Ê¾å¤Î + ¥Õ¥¡¥¤¥ë¤ò°·¤¦¤³¤È¤¬¤Ç¤­¤Ê¤¤¤Ç¤·¤ç¤¦¡£
    • +
  • ¥Í¥Ã¥È¥ï¡¼¥¯¥Þ¥¦¥ó¥È¤µ¤ì¤¿ DocumentRoot + (Î㤨¤Ð NFS ¤ä SMB) + ¤Ç¤Ï¡¢¥«¡¼¥Í¥ë¤Ï¼«¿È¤Î¥­¥ã¥Ã¥·¥å¤ò»È¤Ã¤Æ¥Í¥Ã¥È¥ï¡¼¥¯¤«¤é¤Î¥Õ¥¡¥¤¥ë¤ò + Á÷¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
    • +
+ +

¤³¤ì¤é¤ÎÌäÂê¤ËÅö¤Æ¤Ï¤Þ¤ë¥µ¡¼¥Ð¤ÎÀßÄê¤Î¾ì¹ç¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ + ¤³¤Îµ¡Ç½¤ò»ÈÍÑÉԲĤˤ·¤Æ¤¯¤À¤µ¤¤:

+ + +

+ EnableSendfile Off +

+ +

NFS ¤ä SMB ¥Þ¥¦¥ó¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Ë¤Ï¡¢ÌäÂê¤Î¤¢¤ë¥Õ¥¡¥¤¥ë¤Ë¤Î¤ßÌÀ¼¨Åª¤Ë + ¤³¤Îµ¡Ç½¤ò»ÈÍÑÉԲĤˤ·¤Þ¤¹:

+ +

+ <Directory "/path-to-nfs-files"> + + EnableSendfile Off + + </Directory> +

+ +
+
top
+

ErrorDocument ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥¨¥é¡¼¤¬È¯À¸¤·¤¿¤È¤­¤Ë¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ë¤â¤Î
¹½Ê¸:ErrorDocument error-code document
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Apache 2.0 ¤Ç¤Ï¥Æ¥­¥¹¥È¤ò¥¯¥¦¥©¡¼¥È¤¹¤ë¹½Ê¸¤¬°ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤«¤é +ÊѤï¤Ã¤Æ¤¤¤Þ¤¹¡£
+

ÌäÂê¤ä¥¨¥é¡¼¤¬È¯À¸¤·¤¿¤È¤­¤ÎÆ°ºî¤È¤·¤Æ¡¢ + Apache ¤Ë¤Ï°Ê²¼¤Î»Í¤Ä¤Î¤¦¤Á°ì¤Ä¤ÎÆ°ºî¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +
    +
  1. Apache ɸ½à¤Î´Êñ¤Ê¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤òɽ¼¨
    2. + +
  2. ¼«Ê¬¤Ç»ØÄꤷ¤¿¥á¥Ã¥»¡¼¥¸¤òɽ¼¨
    3. + +
  3. ÌäÂê¤ä¥¨¥é¡¼¤Î½èÍý¤ò¤¹¤ë°Ù¤Ë¡¢¼«¥µ¡¼¥ÐÆâ¤Î + URL-path ¤Ø¥ê¥À¥¤¥ì¥¯¥È
    4. + +
  4. ÌäÂê¤ä¥¨¥é¡¼¤Î½èÍý¤ò¤¹¤ë°Ù¤Ë¡¢³°Éô¤Î URL ¤Ø¥ê¥À¥¤¥ì¥¯¥È
    5. +
+ +

ºÇ½é¤Î¤â¤Î¤¬¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤Ç¡¢2 ÈÖÌܤ«¤é 4 ÈÖÌܤϡ¢ + ErrorDocument¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¡¢ + HTTP ¤Î¥ì¥¹¥Ý¥ó¥¹¥³¡¼¥É¤È¡¢¥á¥Ã¥»¡¼¥¸¤« URL ¤ò»ØÄꤹ¤ë¤³¤È¤ÇÀßÄꤷ¤Þ¤¹¡£ + Apache ¤¬ÌäÂê¤â¤·¤¯¤Ï¥¨¥é¡¼¤Ë´Ø¤¹¤ëÄɲþðÊó¤òÄ󶡤¹¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£

+ +

URL ¤Î¾ì¹ç¤Ï¡¢¥¹¥é¥Ã¥·¥å¤Ç»Ï¤Þ¤ë (/) ¥í¡¼¥«¥ë¤Î web-path ( + DocumentRoot ¤«¤é¤ÎÁêÂХѥ¹ + ) ¤«¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬²ò·è¤Ç¤­¤ë´°Á´¤Ê URL ¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤â¤·¤¯¤Ï¡¢¥Ö¥é¥¦¥¶¤Ëɽ¼¨¤µ¤ì¤ë¥á¥Ã¥»¡¼¥¸¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£ + Îã:

+ +

+ ErrorDocument 500 http://foo.example.com/cgi-bin/tester
+ ErrorDocument 404 /cgi-bin/bad_urls.pl
+ ErrorDocument 401 /subscription_info.html
+ ErrorDocument 403 "Sorry can't allow you access today" +

+ +

²Ã¤¨¤Æ¡¢ÆÃÊ̤ÊÃÍ default ¤ò»È¤Ã¤Æ Apache ¤Ë + ¥Ï¡¼¥É¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë´Êñ¤Ê¥á¥Ã¥»¡¼¥¸¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + Ä̾ï¤ÏɬÍפǤϤ¢¤ê¤Þ¤»¤ó¤¬¡¢default ¤ò»È¤¦¤È + ´û¸¤Î ErrorDocument ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀßÄê¤ò + ·Ñ¾µ¤¹¤ë¤È¤³¤í¤Ç¡¢Apache ¤Î¥Ï¡¼¥É¥³¡¼¥É¤µ¤ì¤¿´Êñ¤Ê¥á¥Ã¥»¡¼¥¸¤Ë + Ì᤹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ ErrorDocument 404 /cgi-bin/bad_urls.pl

+ <Directory /web/docs>
+ + ErrorDocument 404 default
+ + </Directory> +

+ +

¥ê¥â¡¼¥È URL (Î㤨¤Ð¡¢Æ¬¤Ë http ¤ÈÉÕÍ¿¤·¤¿ÊýË¡) ¤ò + ErrorDocument ¤Ë»ØÄꤹ¤ë¤È¤­¡¢ + ¤¿¤È¤¨Ê¸½ñ¤¬Æ±¤¸¥µ¡¼¥Ð¤Ë¤¢¤í¤¦¤È¤â¡¢¥É¥­¥å¥á¥ó¥È¤¬¤É¤³¤Ë¤¢¤ë¤«¤òÄÌÃΤ¹¤ë¤¿¤á¤Ë¡¢ + Apache ¤Ï¥ê¥À¥¤¥ì¥¯¥È¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷½Ð¤¹¤ë¤È¤¤¤¦¤³¤È¤Ë¡¢Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤ì¤Ë¤Ï¤¤¤í¤¤¤í¤È´ØÏ¢¤·¤Æµ¯¤³¤ëÌäÂ꤬¤¢¤ê¤Þ¤¹¡£ + Ãæ¤Ç¤âºÇ¤â½ÅÍפʤΤϡ¢¥¯¥é¥¤¥¢¥ó¥È¤Ï¸µ¡¹¤Î¥¨¥é¡¼¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤ò¼õ¤±¼è¤é¤º¡¢ + Âå¤ï¤ê¤Ë¥ê¥À¥¤¥ì¥¯¥È¤Î¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤ò¼õ¤±¼è¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤ò»È¤Ã¤Æ URL ¤¬Í­¸ú¤Ç¤¢¤ë¤«¤É¤¦¤«¤ò·èÄꤷ¤è¤¦¤È¤¹¤ë + ¥¦¥§¥Ö¥í¥Ü¥Ã¥È¤ä¤½¤Î¾¥¯¥é¥¤¥¢¥ó¥È¤ò¡¢º®Í𤵤»¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤µ¤é¤Ë¡¢ErrorDocument 401 ¤Ë¥ê¥â¡¼¥È¤Î URL ¤ò»ØÄꤹ¤ë¤È¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤Ï 401 ¤È¤¤¤¦¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤ò¼õ¤±¼è¤é¤Ê¤¤¤¿¤á¡¢ + ¥Ñ¥¹¥ï¡¼¥É¤ò¥æ¡¼¥¶¡¼¤ËÆþÎÏÍ׵ᤷ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤³¤È¤¬¤ï¤«¤ê¤Þ¤»¤ó¡£ + ½¾¤Ã¤Æ¡¢ErrorDocument 401 ¤È¤¤¤¦¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¾ì¹ç¤Ï¡¢ + ɬ¤º¥í¡¼¥«¥ë¤Êʸ½ñ¤ò»²¾È¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

Microsoft Internet Explorer (MSIE) ¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥µ¡¼¥Ð¤¬À¸À®¤·¤¿¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤¬ + ¡Ö¾®¤µ¤¹¤®¤ë¡×¤È¤­¤Ë¤Ï̵»ë¤ò¤·¤Æ¼«Ê¬¼«¿È¤Î¡Ö¤ä¤µ¤·¤¤¡×¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Ç + ÃÖ´¹¤·¤Þ¤¹¡£¥µ¥¤¥º¤Î¤·¤­¤¤Ãͤϥ¨¥é¡¼¤Î¼ïÎà¤Ë¤è¤Ã¤Æ°Û¤Ê¤ê¤Þ¤¹¤¬¡¢ + °ìÈÌŪ¤Ë¤Ï¥¨¥é¡¼¤Îʸ½ñ¤ò 512 ¥Ð¥¤¥È¤è¤ê¤âÂ礭¤¯¤¹¤ë¤È¡¢MSIE ¤Ï + ¥µ¡¼¥Ð¤¬À¸À®¤·¤¿¥¨¥é¡¼¤ò±£¤µ¤º¤Ëɽ¼¨¤·¤Þ¤¹¡£¾Ü¤·¤¤¾ðÊó¤Ï Microsoft + Knowledge Base ¤Îµ­»ö Q294807 + ¤Ë¤¢¤ê¤Þ¤¹¡£

+ +

¤Û¤È¤ó¤É¤Î¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò¾å½ñ¤­¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢ÆÃÄê¤Î¾õ¶·²¼¤Ç¤Ï + ErrorDocument ¤ÎÀßÄê¤Ë¤«¤«¤ï¤é¤º + Æ⢤Υá¥Ã¥»¡¼¥¸¤¬»È¤ï¤ì¤Þ¤¹¡£ + Æäˡ¢ÉÔÀµ¤Ê·Á¼°¤Î¥ê¥¯¥¨¥¹¥È¤¬¸¡½Ð¤µ¤ì¤¿¾ì¹ç¡¢Ä̾ï¤Î¥ê¥¯¥¨¥¹¥È½èÍý¤Ï + ¨ºÂ¤ËÃæ»ß¤µ¤ì¡¢Æ⢤Υ¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£ + ¤³¤Î½èÃÖ¤ÏÉÔÀµ¤Ê¥ê¥¯¥¨¥¹¥È¤Ë¤è¤Ã¤Æ°ú¤­µ¯¤³¤µ¤ì¤ë¡¢¥»¥­¥å¥ê¥Æ¥£ÌäÂ꤫¤é + ¼é¤ë¤¿¤á¤ËɬÍפÊÁ¼Ã֤Ǥ¹¡£

+ +

2.0 ¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢ÂФˤʤäƤ¤¤Ê¤¤Æó½Å°úÍÑÉä¤ò + ÀèƬ¤ËÉÕ¤±¤ë¤³¤È¤Ë¤è¤ê¥á¥Ã¥»¡¼¥¸¤Ç¤¢¤ë¤³¤È¤ò»ØÄꤷ¤Æ¤¤¤Þ¤·¤¿¡£

+ + +

»²¾È

+ +
+
top
+

ErrorLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬¥¨¥é¡¼¤ò¥í¥°¼ý½¸¤¹¤ë¾ì½ê
¹½Ê¸: ErrorLog file-path|syslog[:facility]
¥Ç¥Õ¥©¥ë¥È:ErrorLog logs/error_log (Unix) ErrorLog logs/error.log (Windows and OS/2)
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

ErrorLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥µ¡¼¥Ð¤ËÀ¸¤¸¤¿¤µ¤Þ¤¶¤Þ¤Ê¥¨¥é¡¼¤ò + µ­Ï¿¤¹¤ë°Ù¤Î¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤷ¤Þ¤¹¡£ + file-path ¤¬ÀäÂХѥ¹¤Ç¤Ê¤¤¤È¤­¤Ï¡¢ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤È¤ß¤Ê¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ ErrorLog /var/log/httpd/error_log +

+ +

file-path ¤¬¥Ñ¥¤¥× (|) ¤«¤é»Ï¤Þ¤ë¾ì¹ç¤Ï¡¢ + ¥¨¥é¡¼¥í¥°¤ò½èÍý¤¹¤ë¤¿¤á¤Ë¼Â¹Ô¤µ¤ì¤ë¥³¥Þ¥ó¥É¤¬ + »ØÄꤵ¤ì¤Æ¤¤¤ë¤È²ò¼á¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ ErrorLog "|/usr/local/bin/httpd_errors" +

+ +

¥Õ¥¡¥¤¥ë̾¤ÎÊѤï¤ê¤Ë syslog ¤È»ØÄꤹ¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢ + ¥·¥¹¥Æ¥à¤¬¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ì¤Ð syslogd(8) ¤òÍøÍѤ·¤¿¥í¥®¥ó¥°¤¬Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢local7 ¥Õ¥¡¥·¥ê¥Æ¥£¤È¤Ê¤ê¤Þ¤¹¤¬¡¢ + syslog:facility ¤È¤¤¤Ã¤¿·Á¤Çµ­½Ò¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢ + Ä̾ï syslog(1) ¤Î¥É¥­¥å¥á¥ó¥È¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¥Õ¥¡¥·¥ê¥Æ¥£¤Î°ì¤Ä¤ò»È¤¦¤è¤¦¤Ë + ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Îã

+ ErrorLog syslog:user +

+ +

¥»¥­¥å¥ê¥Æ¥£: + ¥í¥°¥Õ¥¡¥¤¥ë¤ò³ÊǼ¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤¬¡¢¥µ¡¼¥Ð¤òµ¯Æ°¤·¤¿¥æ¡¼¥¶°Ê³°¤Î + ¥æ¡¼¥¶¤Ë¤è¤Ã¤Æ½ñ¤­¹þ¤á¤ë¾ì¹ç¤Ë¥»¥­¥å¥ê¥Æ¥£¤¬Çˤé¤ì¤ë²ÄǽÀ­¤¬¤¢¤ë¤³¤È¤Ë + ´Ø¤¹¤ë¾ÜºÙ¤Ï ¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤¹¤ë¥³¥Ä ¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+

Ãí

+

Unix °Ê³°¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¥Õ¥¡¥¤¥ë¤Î¥Ñ¥¹¤òÆþÎϤ¹¤ë¤È¤­¤Ï¡¢ + ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤¬¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Î»ÈÍѤòµö¤·¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢ + ³Î¼Â¤Ë¥¹¥é¥Ã¥·¥å¤Î¤ß¤¬»ÈÍѤµ¤ì¤ë¤è¤¦¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£°ìÈÌŪ¤Ë¤Ï¡¢ + ÀßÄê¥Õ¥¡¥¤¥ëÁ´È̤ǥ¹¥é¥Ã¥·¥å¤Î¤ß¤ò»È¤¦Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+
+ +

»²¾È

+ +
+
top
+

FileETag ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:ETag HTTP ±þÅú¥Ø¥Ã¥À¤òºîÀ®¤¹¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤ë +¥Õ¥¡¥¤¥ë¤Î°À­
¹½Ê¸:FileETag component ...
¥Ç¥Õ¥©¥ë¥È:FileETag INode MTime Size
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

+ FileETag ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥É¥­¥å¥á¥ó¥È¤¬¥Õ¥¡¥¤¥ë¤Ë´ð¤Å¤¤¤¿¤â¤Î¤Ç¤¢¤ë¤È¤­¤Ë¡¢ + ETag (¥¨¥ó¥Æ¥£¥Æ¥£¥¿¥°) ±þÅú¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤òºîÀ®¤¹¤ë¤È¤­¤Ë»ÈÍѤ¹¤ë + ¥Õ¥¡¥¤¥ë¤Î°À­¤òÀßÄꤷ¤Þ¤¹¡£ (ETag ¤ÎÃͤϥͥåȥ¥¯¤ÎÂÓ°è¤òÀáÌ󤹤뤿¤á¤Î + ¥­¥ã¥Ã¥·¥å¤Î´ÉÍý¤Ç»È¤ï¤ì¤Þ¤¹¡£) Apache 1.3.22 °ÊÁ°¤Ç¤Ï¡¢ETag ¤ÎÃÍ¤Ï + ¾ï¤Ë¥Õ¥¡¥¤¥ë¤Î inode, ¥µ¥¤¥º¡¢ºÇ½ª½¤Àµ»þ¹ï (mtime) ¤«¤éºîÀ® + ¤µ¤ì¤Æ¤¤¤Þ¤·¤¿¡£FileETag ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¡¢¤³¤ì¤é¤Î¤É¤ì¤ò»È¤¦¤«¤ò + Áª¤Ö¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Ç§¼±¤µ¤ì¤ë¥­¡¼¥ï¡¼¥É¤Ï: +

+ +
+
INode
+
¥Õ¥¡¥¤¥ë¤Î inode ÈÖ¹æ¤ò·×»»¤Ë»È¤¤¤Þ¤¹
+
MTime
+
¥Õ¥¡¥¤¥ë¤ÎºÇ½ª½¤Àµ»þ¹ï¤ò»È¤¤¤Þ¤¹
+
Size
+
¥Õ¥¡¥¤¥ë¤ÎÃæ¿È¤Î¥Ð¥¤¥È¿ô¤ò»È¤¤¤Þ¤¹
+
All
+
»ÈÍѲÄǽ¤Ê¤¹¤Ù¤Æ¤Î¥Õ¥£¡¼¥ë¥É¤ò»È¤¤¤Þ¤¹¡£ + ¤³¤ì¤Ï

FileETag INode MTime Size

¤ÈÅù²Á¤Ç¤¹¡£
+
None
+
¥É¥­¥å¥á¥ó¥È¤¬¥Õ¥¡¥¤¥ë¤Ë´ð¤Å¤¤¤¿¤â¤Î¤Ç¤â¡¢ETag ¥Õ¥£¡¼¥ë¥É¤ò + ±þÅú¤ËÉղä·¤Þ¤»¤ó
+
+ +

INode, MTime, Size ¥­¡¼¥ï¡¼¥É¤Ë¤Ï + + ¤ä - ¤òÁ°¤ËÉÕ¤±¤Æ + »ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤³¤Î¾ì¹ç¤Ï¡¢¤è¤ê¹­¤¤ÈϰϤ«¤é·Ñ¾µ¤µ¤ì¤¿ + ¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤ËÊѹ¹¤ò²Ã¤¨¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£¤½¤Î¤è¤¦¤ÊÀÜƬ¼­¤Î + ̵¤¤¥­¡¼¥ï¡¼¥É¤ò»ØÄꤹ¤ë¤È¡¢Â¨ºÂ¤Ë·Ñ¾µ¤·¤¿ÀßÄê¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£

+ +

¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ÎÀßÄê¤Ë + FileETag INode MTime Size ¤¬¤¢¤ê¡¢ + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ÎÀßÄê¤Ë FileETag -INode ¤¬¤¢¤ë¤È¤­¤Ï¡¢ + ¤½¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ÎÀßÄê¤Ï (ÀßÄ꤬¾å½ñ¤­¤µ¤ì¤Ê¤±¤ì¤Ð¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Î + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤â·Ñ¾µ¤µ¤ì¤Þ¤¹) FileETag MTime Size + ¤ÈƱ¤¸¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +
+
top
+

<Files> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë̾¤ËŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
¹½Ê¸:<Files filename> ... </Files>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

<Files> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¤½¤ÎÃæ¤Ë¤¢¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎŬÍÑÈϰϤò¥Õ¥¡¥¤¥ë̾¤ÇÀ©¸Â¤·¤Þ¤¹¡£ + <Directory> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä <Location> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + Ʊ¤¸¤è¤¦¤Êµ¡Ç½¤ò»ý¤Á¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢</Files> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈÂÐ¤Ë + ¤Ê¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤³¤Î¥»¥¯¥·¥ç¥óÃæ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥Ù¡¼¥¹Ì¾ (¥Õ¥¡¥¤¥ë̾¤ÎºÇ¸å¤ÎÉôʬ) + ¤¬»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë̾¤Ë¥Þ¥Ã¥Á¤¹¤ë¤¹¤Ù¤Æ¤Î¥ª¥Ö¥¸¥§¥¯¥È¤ËŬÍѤµ¤ì¤Þ¤¹¡£ + <Files> ¥»¥¯¥·¥ç¥ó¤Ï + <Directory> ¥»¥¯¥·¥ç¥ó¤È + .htaccess ¤¬Æɤ߹þ¤Þ¤ì¤¿¸å¡¢ + <Location> ¥»¥¯¥·¥ç¥ó¤è¤ê¤ÏÀè¤Ë + ÀßÄê¥Õ¥¡¥¤¥ë¤Ë¸½¤ì¤¿½ç¤ËŬÍѤµ¤ì¤Þ¤¹¡£ + <Files> ¤Ï¡¢ + <Directory> ¥»¥¯¥·¥ç¥óÆâ¤Ë + ¥Í¥¹¥È¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¡¢ + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ìÉô¤Ë¤Î¤ß¸ÂÄꤷ¤ÆŬÍѤµ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

filename °ú¿ô¤Ï¡¢¥Õ¥¡¥¤¥ë̾¤«¥ï¥¤¥ë¥É¥«¡¼¥Éʸ»úÎó + ¤Ç¡¢¥ï¥¤¥ë¥É¥«¡¼¥É¤Ç¤Ï ? ¤Ï°ì¤Ä¤Îʸ»ú¡¢* ¤ÏǤ°Õ¤Îʸ»úÎó¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + ~ ¤È¤¤¤¦Ê¸»ú¤òÉղ乤뤳¤È¤ÇÀµµ¬É½¸½¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + Î㤨¤Ð¡¢

+ +

+ <Files ~ "\.(gif|jpe?g|png)$"> +

+ +

¤È¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢°ìÈÌŪ¤Ê¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Î²èÁü¥Õ¥©¡¼¥Þ¥Ã¥È¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + ¤¿¤À¤·¡¢ + <FilesMatch> ¤ò»È¤¦Êý¤¬ + ¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

¤Á¤Ê¤ß¤Ë¡¢<Directory> ¤È <Location> ¥»¥¯¥·¥ç¥ó¤È¤Ï°Û¤Ê¤ê¡¢ + <Files> + ¤Ï .htaccess ¥Õ¥¡¥¤¥ëÆâ¤ÇÍøÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¥æ¡¼¥¶¤¬¥Õ¥¡¥¤¥ëËè¤Ë¥¢¥¯¥»¥¹¤ÎÀ©¸æ¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë + ¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+ + +

»²¾È

+ +
+
top
+

<FilesMatch> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:Àµµ¬É½¸½¤Ë¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë̾¤ËŬÍѤµ¤ì¤ë +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
¹½Ê¸:<FilesMatch regex> ... </FilesMatch>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

<FilesMatch> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + <Files> + ¥Ç¥£¥ì¥¯¥Æ¥£¥ÖƱÍͤˤ½¤ÎÃæ¤Ë¤¢¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎŬÍÑÈϰϤò¥Õ¥¡¥¤¥ë̾¤ÇÀ©¸Â¤·¤Þ¤¹¡£¤¿¤À¤·¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤ÏÀµµ¬É½¸½¤ò»ØÄꤷ¤Þ¤¹¡£ + Î㤨¤Ð:

+ +

+ <FilesMatch "\.(gif|jpe?g|png)$"> +

+ +

¤Ï°ìÈÌŪ¤Ê¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Î²èÁü·Á¼°¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

ForceType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¤¹¤Ù¤Æ¤Î¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë¤¬»ØÄê¤Î MIME ¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤Ç +Á÷¤é¤ì¤ë¤è¤¦¤Ë¤¹¤ë
¹½Ê¸:ForceType MIME-type|None
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Apache 2.0 ¤Ç core ¤Ë°ÜÆ°
+

.htaccess ¤ä <Directory> ¥»¥¯¥·¥ç¥ó¡¢ + <Location> ¥»¥¯¥·¥ç¥ó¡¢ + <Files> ¥»¥¯¥·¥ç¥ó¤Ë + ½ñ¤«¤ì¤¿¾ì¹ç¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤½¤³¤Ë¤¢¤ë¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤¬ + MIME-type + ¤Ç»ØÄꤵ¤ì¤¿¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤È¤·¤Æ°·¤ï¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢ + GIF ¥Õ¥¡¥¤¥ë¤Ð¤«¤ê¤Î¥Ç¥£¥ì¥¯¥È¥ê¤¬¤¢¤Ã¤Æ¡¢¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò .gif + ¤Ç½ª¤ï¤é¤»¤¿¤¯¤Ï¤Ê¤¤¤È¤­¤Ë¡¢°Ê²¼¤Î¤â¤Î¤ò»ÈÍѤ·¤Þ¤¹:

+ +

+ ForceType image/gif +

+ +

DefaultType ¤È°ã¤Ã¤Æ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥á¥Ç¥£¥¢¥¿¥¤¥×¤ò·è¤á¤ë¤³¤È¤¬¤Ç¤­¤ë¤«¤â¤·¤ì¤Ê¤¤ + ¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤â´Þ¤á¡¢¤¹¤Ù¤Æ¤Î MIME ¥¿¥¤¥×¤Î´ØÏ¢ÉÕ¤±¤ò + ¾å½ñ¤­¤¹¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

None ¤È¤¤¤¦Ãͤò»È¤¦¤³¤È¤Ç ForceType ¤Î + ÀßÄê¤ò̵¸ú¤Ë¤Ç¤­¤Þ¤¹:

+ +

+ # force all files to be image/gif:
+ <Location /images>
+ + ForceType image/gif
+ + </Location>
+
+ # but normal mime-type associations here:
+ <Location /images/mixed>
+ + ForceType None
+ + </Location> +

+ +
+
top
+

HostnameLookups ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤Î IP ¥¢¥É¥ì¥¹¤Î DNS ¥ë¥Ã¥¯¥¢¥Ã¥×¤ò +Í­¸ú¤Ë¤¹¤ë
¹½Ê¸:HostnameLookups On|Off|Double
¥Ç¥Õ¥©¥ë¥È:HostnameLookups Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥Û¥¹¥È̾¤ò¥í¥°¼ý½¸¤Ç¤­¤ë¤è¤¦¤Ë + DNS ¥ë¥Ã¥¯¥¢¥Ã¥×¤òÍ­¸ú¤Ë¤·¤Þ¤¹ + (¤µ¤é¤Ë¡¢CGI/SSI ¤Ë REMOTE_HOST ÊÑ¿ô¤È¤·¤ÆÅϤ·¤Þ¤¹)¡£ + Double¤ò»ØÄꤷ¤¿¾ì¹ç¡¢2 ½Å¤ÎµÕ°ú¤­¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£ + ¤Ä¤Þ¤ê¡¢µÕ°ú¤­¤Î¸å¤Ë¡¢¤½¤Î·ë²Ì¤ËÂФ·¤ÆÀµ°ú¤­¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£Àµ°ú¤­¤Î + ·ë²Ì¤Î IP ¥¢¥É¥ì¥¹¤ÎÃæ¤Ë¥ª¥ê¥¸¥Ê¥ë¤Î¥¢¥É¥ì¥¹¤È°ìÃפ¹¤ë¤â¤Î¤¬¤Ê¤±¤ì¤Ð + ¤Ê¤ê¤Þ¤»¤ó¡£("tcpwrappers" ¤ÎÍѸì¤Ç¤Ï PARANOID ¤È¸Æ¤Ð¤ì¤Æ¤¤¤Þ¤¹¡£)

+ +

mod_authz_host ¤Ç¥Û¥¹¥È̾¤Ë¤è¤ë¥¢¥¯¥»¥¹ + À©¸æ¤ò¹Ô¤Ê¤¦¾ì¹ç¤Ë¤Ï¡¢ + ÀßÄê¤ÎÇ¡²¿¤Ë¤è¤é¤º 2 ½Å¤ÎµÕ°ú¤­¤¬¼Â¹Ô¤µ¤ì¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥»¥­¥å¥ê¥Æ¥£¤òÊݤĤ¿¤á¤ËɬÍפǤ¹¡£ + HostnameLookups Double ¤òÀßÄꤷ¤Ê¤¤¸Â¤ê¡¢ + ¾¤ÎÉôʬ¤Ï¤³¤Î 2 ½ÅµÕ°ú¤­¤Î·ë²Ì¤ò»È¤¦¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ + Î㤨¤Ð¡¢HostnameLookups On ¤ÈÀßÄꤷ¤Æ¤¢¤ë¾õÂ֤ǡ¢ + ¥Û¥¹¥È̾¤Ë¤è¤ë¥¢¥¯¥»¥¹À©¸Â¤ò¹Ô¤Ê¤Ã¤¿¥ª¥Ö¥¸¥§¥¯¥È¤Ø¤Î + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¤¿¤È¤¹¤ë¤È¡¢2 ½Å¤ÎµÕ°ú¤­¤¬À®¸ù¤¹¤ë¤«Èݤ«¤Ë¤è¤é¤º¡¢ + REMOTE_HOST ¤Ë¤ÏÄ̾ï¤ÎµÕ°ú¤­·ë²Ì¤¬ÅϤµ¤ì¤Þ¤¹¡£

+ +

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥Ç¥Õ¥©¥ë¥È¤Ï + ËÜÅö¤ËµÕ°ú¤­¤òɬÍפȤ·¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¥µ¥¤¥È¤Î + ¥Í¥Ã¥È¥ï¡¼¥¯¥È¥é¥Õ¥£¥Ã¥¯¤òÄ㸺¤µ¤»¤ë¤¿¤á¤Ë¡¢Off ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¥ë¥Ã¥¯¥¢¥Ã¥×¤Ë¤è¤ë;·×¤ÊÃٱ䤬¤Ê¤¯¤Ê¤ë¤¿¤á¡¢ + ¥¨¥ó¥É¥æ¡¼¥¶¤Ë¤È¤Ã¤Æ¤âÎɤ¤¤Ç¤·¤ç¤¦¡£ + DNS ¤Î¥ë¥Ã¥¯¥¢¥Ã¥×¤Ë¤Ï¡¢¤«¤Ê¤ê¤Î»þ´Ö¤¬É¬ÍפȤʤë¾ì¹ç¤¬Â¿¤¯¡¢ + Éé²Ù¤Î¹â¤¤¥µ¥¤¥È¤Ç¤Ï¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Off ¤Ë¤¹¤Ù¤­¤Ç¤¹¡£ + ¤Ê¤ª¡¢/support ¥Ç¥£¥ì¥¯¥È¥ê¤Ë´Þ¤Þ¤ì¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï + ¥¤¥ó¥¹¥È¡¼¥ë¥Ç¥£¥ì¥¯¥È¥ê¤Î bin ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë + ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤ë logresolve ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ë¤è¤ê¡¢ + Apache ¤ÎÆ°ºî¤È¤ÏÊ̤ˡ¢¥í¥°¤Ë»Ä¤µ¤ì¤Æ¤¤¤ë IP ¥¢¥É¥ì¥¹¤«¤é¥Û¥¹¥È̾¤ò + ¥ë¥Ã¥¯¥¢¥Ã¥×¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¹¡£

+ +
+
top
+

<IfDefine> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:µ¯Æ°»þ¤Ë¥Æ¥¹¥È¤¬¿¿¤Ç¤¢¤ë¤È¤­¤Î¤ß¤Ë½èÍý¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò +°Ï¤à
¹½Ê¸:<IfDefine [!]parameter-name> ... + </IfDefine>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

<IfDefine test>...</IfDefine> + ¥»¥¯¥·¥ç¥ó¤Ï¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¾ò·ïÉÕ¤­¤Ç»ØÄꤹ¤ë¤¿¤á¤ËÍøÍѤ·¤Þ¤¹¡£ + <IfDefine> ¥»¥¯¥·¥ç¥ó¤Ë + ´Þ¤Þ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢test¤¬ + ÄêµÁ¤µ¤ì¤Æ¤¤¤ë¤È¤­¤Î¤ß½èÍý¤µ¤ì¤Þ¤¹¡£ + ¤â¤· test ¤¬ÄêµÁ¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢ + ³«»Ï¤È½ªÎ»¤Î»ØÄê¤Î´Ö¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£

+ +

<IfDefine> ¥»¥¯¥·¥ç¥ó¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë + »ØÄꤹ¤ë test ¤Ï¡¢ + ¼¡¤ÎÆó¤Ä¤Î·Á¼°¤Î¤¦¤Á¤Î°ì¤Ä¤ò¤È¤ê¤Þ¤¹:

+ +
    +
  • parameter-name
    • + +
  • !parameter-name
    • +
+ +

Á°¼Ô¤Î¾ì¹ç¤Ë¤Ï¡¢parameter-name ¤È̾ÉÕ¤±¤é¤ì¤¿¥Ñ¥é¥á¡¼¥¿¤¬ + ÄêµÁ¤µ¤ì¤Æ¤¤¤ì¤Ð³«»Ï¤È½ªÎ»¤Î´Ö¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬½èÍý¤µ¤ì¤Þ¤¹¡£ + ¸å¼Ô¤Î¾ì¹ç¤ÏµÕ¤Ç¡¢parameter-name ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤ + ¾ì¹ç¤Ë½èÍý¤µ¤ì¤Þ¤¹¡£

+ +

parameter-name °ú¿ô¤Ï¡¢¥µ¡¼¥Ð¤òµ¯Æ°¤¹¤ëºÝ¤Ë + httpd ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Ë + -Dparameter- ¤È¤¤¤¦·Á¤Ç»ØÄꤹ¤ë¤ÈÄêµÁ¤µ¤ì¤Þ¤¹¡£

+ +

<IfDefine> ¥»¥¯¥·¥ç¥ó¤Ï + Æþ¤ì»Ò¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¡¢Ê£¿ô¤Î¥Ñ¥é¥á¡¼¥¿¤Ë¤è¤ë¥Æ¥¹¥È¤ò¤¹¤ë¤¿¤á¤Ë»ÈÍѤǤ­¤Þ¤¹¡£ + Îã:

+ +

+ httpd -DReverseProxy ...
+
+ # httpd.conf
+ <IfDefine ReverseProxy>
+ + LoadModule rewrite_module modules/mod_rewrite.so
+ LoadModule proxy_module modules/libproxy.so
+ + </IfDefine> +

+ +
+
top
+

<IfModule> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥â¥¸¥å¡¼¥ë¤Î¸ºß¤¹¤ë¤«¤·¤Ê¤¤¤«¤Ë±þ¤¸¤Æ½èÍý¤µ¤ì¤ë +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
¹½Ê¸:<IfModule [!]module-file|module-identifier> ... + </IfModule>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:¥â¥¸¥å¡¼¥ë¼±Ê̻ҤϥС¼¥¸¥ç¥ó 2.1 °Ê¹ß¤Ç»ÈÍѲÄǽ¡£
+

<IfModule test>...</IfModule> + ¥»¥¯¥·¥ç¥ó¤Ï¡¢¥â¥¸¥å¡¼¥ë¤¬Â¸ºß¤¹¤ë¤È¤­¤Ë½èÍý¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »ØÄꤹ¤ë¤¿¤á¤ËÍøÍѤ·¤Þ¤¹¡£ + <IfModule> ¥»¥¯¥·¥ç¥ó¤Ë + ´Þ¤Þ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢test + ¤Ç»ØÄꤹ¤ë¥â¥¸¥å¡¼¥ë¤¬ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤È¤­¤Î¤ß½èÍý¤µ¤ì¤Þ¤¹¡£ + ¤â¤· test ¤¬ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢³«»Ï¤È½ªÎ»¤Î´Ö¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£

+ +

<IfModule> ¥»¥¯¥·¥ç¥ó¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë + »ØÄꤹ¤ë test ¤Ï¡¢ + ¼¡¤ÎÆó¤Ä¤Î·Á¼°¤Î¤¦¤Á¤Î°ì¤Ä¤ò¤È¤ê¤Þ¤¹¡£

+ +
    +
  • module
    • + +
  • !module
    • +
+ +

Á°¼Ô¤Î¾ì¹ç¤Ï¡¢module ¤È̾ÉÕ¤±¤é¤ì¤¿¥â¥¸¥å¡¼¥ë¤¬ + Apache ¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ì¤Ð + (¥³¥ó¥Ñ¥¤¥ëºÑ¤ß¤Î¤â¤Î¤È¡¢LoadModule ¤òÍøÍѤ·¤Æ + ưŪ¤ËÆɤ߹þ¤ó¤À¤â¤Î¤ÎξÊý)¡¢ + ³«»Ï¤È½ªÎ»¤Î´Ö¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬½èÍý¤µ¤ì¤Þ¤¹¡£ + ¸å¼Ô¤Î¾ì¹ç¤ÏµÕ¤Ç¡¢module ¤¬ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Ê¤¤ + ¾ì¹ç¤Ë½èÍý¤µ¤ì¤Þ¤¹¡£

+ +

module °ú¿ô¤Ï¡¢¥â¥¸¥å¡¼¥ë¼±Ê̻Ҥ« + ¥³¥ó¥Ñ¥¤¥ë¤ò¤·¤¿»þ¤Î¥â¥¸¥å¡¼¥ë¤Î¥Õ¥¡¥¤¥ë̾¤Ç¤¹¡£ + Î㤨¤Ð¡¢rewrite_module ¤Ï¼±ÊÌ»Ò¤Ç + mod_rewrite.c ¤Ï¥Õ¥¡¥¤¥ë̾¤Ç¤¹¡£ + ¥â¥¸¥å¡¼¥ë¤¬Ê£¿ô¤Î¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤«¤é¹½À®¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢Ê¸»úÎó + STANDARD20_MODULE_STUFF ¤¬¤¢¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°¤ò + »È¤Ã¤Æ¤¯¤À¤µ¤¤¡£

+ +

<IfModule> ¥»¥¯¥·¥ç¥ó¤Ï + Æþ¤ì»Ò¤Ë¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¢¤ê¡¢ + Ê£¿ô¤Î¥â¥¸¥å¡¼¥ë¤Î¥Æ¥¹¥È¤ò¹Ô¤Ê¤¦¤¿¤á¤Ë»ÈÍѤǤ­¤Þ¤¹¡£

+ +
ÆÃÄê¤Î¥â¥¸¥å¡¼¥ë¤Î¸ºß¤Ë´Ø¤ï¤é¤ºÆ°ºî¤¹¤ë + ÀßÄê¥Õ¥¡¥¤¥ë¤Î¸¶Ëܤ¬É¬ÍפʤȤ­¤Ë¤Î¤ß¤³¤Î¥»¥¯¥·¥ç¥ó¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£ + Ä̾ï¤ÎÆ°ºî¤Ç¤Ï¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + <IfModule> ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤Ë + Æþ¤ì¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
+ +
+
top
+

Include ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ëÃ椫¤é¾¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò¼è¤ê¹þ¤à
¹½Ê¸:Include file-path|directory-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:¥ï¥¤¥ë¥É¥«¡¼¥É¤Ë¤è¤ë¥Þ¥Ã¥Á¤Ï 2.0.41 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¡¢¥µ¡¼¥Ð¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤«¤é + ¾¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò¥¤¥ó¥¯¥ë¡¼¥É¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Ê£¿ô¤Î¥Õ¥¡¥¤¥ë¤ò¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È½ç¤Ë°ìÅÙ¤ËÆɤ߹þ¤à¤¿¤á¤Ë¡¢ + ¥·¥§¥ë·Á¼° (fnmatch) ¤Î¥ï¥¤¥ë¥É¥«¡¼¥Éʸ»ú¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤µ¤é¤Ë¡¢Include ¤Ë¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤¿¾ì¹ç¤Ï¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê¤È¤½¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥êÆâ¤ÎÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò + ¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È½ç¤ËÆɤ߹þ¤ó¤Ç¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤È¤·¤Æ½èÍý¤·¤Þ¤¹¡£ + ¤·¤«¤·¡¢¥Ç¥£¥ì¥¯¥È¥êÁ´ÂΤòÆɤ߹þ¤à¤Î¤Ï¤ª´«¤á¤Ç¤­¤Þ¤»¤ó¡£ + ¤Õ¤È¤·¤¿¤³¤È¤«¤é httpd ¤¬Æɤ߹þ¤ß¤Ë¼ºÇÔ¤¹¤ë¤è¤¦¤Ê + °ì»þ¥Õ¥¡¥¤¥ë¤ò¥Ç¥£¥ì¥¯¥È¥ê¤Ë»Ä¤·¤Æ¤·¤Þ¤¦¤è¤¦¤Ê¤³¤È¤¬¤è¤¯¤¢¤ë¤«¤é¤Ç¤¹¡£

+ +

»ØÄꤹ¤ë¥Õ¥¡¥¤¥ë¥Ñ¥¹¤ÏÀäÂХѥ¹¤«¡¢ + ServerRoot ¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤Î + ÁêÂХѥ¹¤«¡¢¤Î¤É¤Á¤é¤«¤Ç¤¹¡£

+ +

Îã:

+ +

+ Include /usr/local/apache2/conf/ssl.conf
+ Include /usr/local/apache2/conf/vhosts/*.conf +

+ +

ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤Î¾ì¹ç¤Ï:

+ +

+ Include conf/ssl.conf
+ Include conf/vhosts/*.conf +

+ +

apachectl configtest ¤ò¼Â¹Ô¤¹¤ë¤È¡¢ÀßÄê¤ò¥Á¥§¥Ã¥¯¤·¤Æ¤¤¤ë»þ¤Ë + Æɤ߹þ¤Þ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î¥ê¥¹¥È¤¬É½¼¨¤µ¤ì¤Þ¤¹:

+ +

+ root@host# apachectl configtest
+ Processing config file: /usr/local/apache2/conf/ssl.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost1.conf
+ Processing config file: /usr/local/apache2/conf/vhosts/vhost2.conf
+ Syntax OK +

+ +

»²¾È

+ +
+
top
+

KeepAlive ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:HTTP ¤Î»ý³Ū¤ÊÀܳ¤òÍ­¸ú¤Ë¤¹¤ë
¹½Ê¸:KeepAlive On|Off
¥Ç¥Õ¥©¥ë¥È:KeepAlive On
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

HTTP/1.0 ¤Î Keep-Alive ³ÈÄ¥¤È HTTP/1.1 ¤Î»ý³ŪÀܳ¤Îµ¡Ç½¤Ï¡¢ + Ê£¿ô¤Î¥ê¥¯¥¨¥¹¥È¤¬Æ±¤¸ TCP ¤ÎÀܳ¤ÇÁ÷¤é¤ì¤ë¡¢Ä¹»þ´Ö»ý³¤¹¤ë + HTTP ¥»¥Ã¥·¥ç¥ó¤òÄ󶡤·¤Þ¤¹¡£¤¿¤¯¤µ¤ó¤Î²èÁü¤¬ + ´Þ¤Þ¤ì¤ë HTML ¥É¥­¥å¥á¥ó¥È¤Ç¤Ï¾ì¹ç¤Ë¤è¤Ã¤Æ¤ÏÃÙ±ä»þ´Ö¤¬ 50% û½Ì¤µ¤ì¤ë·ë²Ì¤â + ¤Ç¤Æ¤¤¤Þ¤¹¡£Keep-Alive Àܳ¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï + KeepAlive On ¤ÈÀßÄꤷ¤Þ¤¹¡£

+ +

HTTP/1.0 ¤ËÂбþ¤·¤¿¥¯¥é¥¤¥¢¥ó¥È¤ÎºÝ¤Ë¤Ï¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤è¤êÆäËÍ׵᤬¤¢¤Ã¤¿¾ì¹ç¤Î¤ß Keep-Alive Àܳ¤È¤Ê¤ê¤Þ¤¹¡£ + ¤µ¤é¤Ë¡¢HTTP/1.0 ¥¯¥é¥¤¥¢¥ó¥È¤Ç¤Ï¡¢¥³¥ó¥Æ¥ó¥Ä¤ÎÍÆÎ̤¬Àè¤Ë + (ÌõÃí: Í×µá¤ËÂФ·¤Æ±þÅú¤òÊÖ¤¹Á°¤Ë) ¤ï¤«¤ë¾ì¹ç¤Î¤ß Keep-Alive + Àܳ¤òÍøÍѤǤ­¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢CGI ¤Î½ÐÎϤä SSI ¤Î¥Ú¡¼¥¸¡¢ + ¥µ¡¼¥Ð¤¬À¸À®¤·¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Î¥ê¥¹¥È¤Î¤è¤¦¤ÊưŪ¥³¥ó¥Æ¥ó¥Ä¤ò + HTTP/1.0 ¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ë¾ì¹ç¤Ë¤Ï Keep-Alive Àܳ¤ò»È¤¨¤Ê¤¤¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ + HTTP/1.1 ¤ËÂбþ¤·¤¿¥¯¥é¥¤¥¢¥ó¥È¤ÎºÝ¤Ë¤Ï¡¢ + Æä˻ØÄꤵ¤ì¤Ê¤¤¸Â¤ê¤Ï¥Ç¥Õ¥©¥ë¥È¤È¤·¤Æ»ý³Ū¤ÊÀܳ¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£ + ¥¯¥é¥¤¥¢¥ó¥È¤¬Í׵᤹¤ì¤Ð¡¢¥³¥ó¥Æ¥ó¥Ä¤ÎÍÆÎ̤òȽÊ̤Ǥ­¤Ê¤¤¤â¤Î¤ò + »ý³Ū¤ÊÀܳ¤òÄ̤·¤ÆÁ÷¤ë¤¿¤á¤Ë¡¢¥Á¥ã¥ó¥¯¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤¬ÍѤ¤¤é¤ì¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

KeepAliveTimeout ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:»ý³Ū¤ÊÀܳ¤Ç¼¡¤Î¥ê¥¯¥¨¥¹¥È¤¬Íè¤ë¤Þ¤Ç¥µ¡¼¥Ð¤¬ÂԤĻþ´Ö
¹½Ê¸:KeepAliveTimeout seconds
¥Ç¥Õ¥©¥ë¥È:KeepAliveTimeout 5
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

Àܳ¤òÊĤ¸¤ëÁ°¤Ë¡¢Apache ¤¬¼¡¤Î¥ê¥¯¥¨¥¹¥È¤ò²¿ÉÃÂԤĤ«¤ò»ØÄꤷ¤Þ¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤¿¸å¤Ï¡¢Timeout ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤Æ + »ØÄꤵ¤ì¤¿¥¿¥¤¥à¥¢¥¦¥ÈÃͤ¬»È¤ï¤ì¤Þ¤¹¡£

+ +

KeepAliveTimeout ¤òÂ礭¤ÊÃͤËÀßÄꤹ¤ë¤È¡¢ + Éé²Ù¤Î¹â¤¤¥µ¡¼¥Ð¤Ë¤ª¤¤¤Æ¤Ï¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤ÎÌäÂê¤ò°ú¤­µ¯¤³¤¹¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£ + ¥¿¥¤¥à¥¢¥¦¥È¤¬Ä¹¤±¤ì¤ÐŤ¤¤Û¤É¡¢¤è¤ê¿¤¯¤Î¥µ¡¼¥Ð¥×¥í¥»¥¹¤¬ + ³èȯ¤Ç¤Ê¤¤¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤ÎÀܳ¤Î½ªÎ»¤òÂÔ¤Á³¤±¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +
+
top
+

<Limit> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:°Ï¤¤¤ÎÃæ¤Ë¤¢¤ë¥¢¥¯¥»¥¹À©¸æ¤ÎŬÍѤòÆÃÄê¤Î HTTP ¥á¥½¥Ã¥É¤Î¤ß¤Ë +À©¸Â¤¹¤ë
¹½Ê¸:<Limit method [method] ... > ... + </Limit>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¥¢¥¯¥»¥¹À©¸æ¤Ï¡¢Ä̾ïÁ´¤Æ¤Î¥¢¥¯¥»¥¹¥á¥½¥Ã¥É¤ËÂФ·¤Æ + ±Æ¶Á¤·¡¢ÉáÄ̤Ϥ³¤ì¤¬Ë¾¤Þ¤·¤¤µóÆ°¤Ç¤¹¡£ + ¤½¤¦¤·¤¿¤³¤È¤«¤é¡¢ÂçÉôʬ¤Î¾ì¹ç¤Ë¤Ï¥¢¥¯¥»¥¹À©¸æ¤Ë´Ø¤ï¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + <Limit> ¥»¥¯¥·¥ç¥óÆâ¤Ë + ½ñ¤¯¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +

<Limit> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ÌÜŪ¤Ï¡¢¥¢¥¯¥»¥¹À©¸æ¤ÎÈϰϤò + »ØÄꤵ¤ì¤¿ HTTP ¥á¥½¥Ã¥É¤Ë¸ÂÄꤹ¤ë¤¿¤á¤Ç¤¹¡£ + ¤½¤ì°Ê³°¤Î¥á¥½¥Ã¥É¤Ï¡¢<Limit> ¤Ç°Ï¤ï¤ì¤¿¥¢¥¯¥»¥¹À©¸æ¤Î + ±Æ¶Á¤ò¼õ¤±¤Þ¤»¤ó¡£ + °Ê²¼¤ÎÎã¤Ï¡¢POST, PUT, DELETE ¤Î¥á¥½¥Ã¥É¤ËÂФ·¤Æ¤Î¤ß¥¢¥¯¥»¥¹¤ÎÀ©¸æ¤ò¹Ô¤Ê¤¤¡¢ + ¤½¤ì°Ê³°¤Î¥á¥½¥Ã¥É¤Ë¤Ä¤¤¤Æ¤ÏÀ©¸Â¤·¤Þ¤»¤ó:

+ +

+ <Limit POST PUT DELETE>
+ + Require valid-user
+ + </Limit> +

+ +

¥á¥½¥Ã¥É̾¤Ë¤Ï°Ê²¼¤ÎÃ椫¤é°ì¤Ä°Ê¾å¤òÎóµó¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹: + GET, + POST, PUT, DELETE, + CONNECT, OPTIONS, + PATCH, PROPFIND, PROPPATCH, + MKCOL, COPY, MOVE, + LOCK, UNLOCK. ¥á¥½¥Ã¥É̾¤Ï + Âçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤¹¡£ GET ¤ò»ØÄꤷ¤¿¾ì¹ç¤Ë¤Ï + HEAD ¥ê¥¯¥¨¥¹¥È¤Ë¤âÀ©¸Â¤¬¤«¤«¤ê¤Þ¤¹¡£TRACE + ¥á¥½¥Ã¥É¤ËÀ©¸Â¤ò¤«¤±¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£

+ +
¥¢¥¯¥»¥¹À©¸æ¤¬ÌÜŪ¤Î¾ì¹ç¤Ï + <Limit> + ¥»¥¯¥·¥ç¥ó¤ÎÂå¤ï¤ê¤Ë <LimitExcept> ¥»¥¯¥·¥ç¥ó¤ò»ÈÍѤ·¤¿Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£ + <LimitExcept> + ¥»¥¯¥·¥ç¥ó¤Ç¤ÏÉÔÆÃÄê¤Î¥á¥½¥Ã¥É¤ËÂФ·¤Æ¤âËɸæ¤Ç¤­¤ë¤«¤é¤Ç¤¹¡£
+ + +
+
top
+

<LimitExcept> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:»ØÄꤵ¤ì¤¿¤â¤Î°Ê³°¤Î HTTP ¥á¥½¥Ã¥É¤Ë¥¢¥¯¥»¥¹À©¸æ¤ò +À©¸Â¤¹¤ë
¹½Ê¸:<LimitExcept method [method] ... > ... + </LimitExcept>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

<LimitExcept> ¤È + </LimitExcept> ¤Ï¡¢°ú¿ô¤Ë + ´Þ¤Þ¤ì¤Æ¤¤¤Ê¤¤ + HTTP ¤Î¥¢¥¯¥»¥¹¥á¥½¥Ã¥É¤ËŬÍѤ¹¤ë¤¿¤á¤Î¥¢¥¯¥»¥¹À©¸æ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò³ç¤ë¤¿¤á¤ËÍøÍѤ·¤Þ¤¹¡£ + ¤Ä¤Þ¤ê¡¢<Limit> ¥»¥¯¥·¥ç¥ó¤ÎÈ¿ÂФÎÆ°ºî¤ò¤·¡¢ + ɸ½à¤Î¥á¥½¥Ã¥É¤Èɸ½à³°¤ä̤ǧ¼±¤Î¥á¥½¥Ã¥É¤Î¾ì¹ç¤ÎξÊý¤òÀßÄê¤Ç¤­¤Þ¤¹¡£ + <Limit> ¤Î¥É¥­¥å¥á¥ó¥È¤â + Ê»¤»¤Æ»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Îã:

+ +

+ <LimitExcept POST GET>
+ + Require valid-user
+ + </LimitExcept> +

+ + +
+
top
+

LimitInternalRecursion ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:ÆâÉô¥ê¥À¥¤¥ì¥¯¥È¤ÈÆþ¤ì»Ò¤Ë¤Ê¤Ã¤¿¥µ¥Ö¥ê¥¯¥¨¥¹¥È¤ÎºÇÂç¿ô¤ò·èÄꤹ¤ë
¹½Ê¸:LimitInternalRecursion number [number]
¥Ç¥Õ¥©¥ë¥È:LimitInternalRecursion 10
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Apache 2.0.47 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

ÆâÉô¥ê¥À¥¤¥ì¥¯¥È¤ÏÎ㤨¤Ð Action ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤Ã¤Æ¤¤¤ë¤È¤­¤Ëµ¯¤³¤ê¤Þ¤¹¡£Action ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¸µ¡¹¤Î¥ê¥¯¥¨¥¹¥È¤ò CGI ¥¹¥¯¥ê¥×¥È¤ËÆâÉô¥ê¥À¥¤¥ì¥¯¥È¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£ + ¥µ¥Ö¥ê¥¯¥¨¥¹¥È¤Ï¤¤¤¯¤Ä¤«¤Î URI ¤ËÂФ·¤Æ¡¢¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¤È¤­¤Ë + ²¿¤¬µ¯¤³¤ë¤«¤òÄ´¤Ù¤ë¤¿¤á¤Î Apache ¤Îµ¡¹½¤Ç¤¹¡£Î㤨¤Ð¡¢mod_dir + ¤Ï DirectoryIndex ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤¬¥ê¥¹¥È¤¹¤ë¥Õ¥¡¥¤¥ë¤òÄ´¤Ù¤ë¤¿¤á¤Ë¥µ¥Ö¥ê¥¯¥¨¥¹¥È¤ò»È¤¤¤Þ¤¹¡£

+ +

LimitInternalRecursion ¤ÏÆâÉô¥ê¥À¥¤¥ì¥¯¥È¤ä + ¥µ¥Ö¥ê¥¯¥¨¥¹¥È¤¬Ìµ¸Â¥ë¡¼¥×¤Ë´Ù¤Ã¤¿¤È¤­¤Î¥µ¡¼¥Ð¥¯¥é¥Ã¥·¥å¤òËɤ®¤Þ¤¹¡£ + ÉáÄÌ¡¢¤½¤Î¤è¤¦¤Ê¥ë¡¼¥×¤ÏÀßÄê¤Ë¼ºÇÔ¤·¤¿¤È¤­¤ËȯÀ¸¤·¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥ê¥¯¥¨¥¹¥ÈËè¤Ëɾ²Á¤µ¤ì¤ë¡¢Æó¤Ä¤Î°ã¤¦¸Â³¦Ãͤò + ÀßÄꤷ¤Þ¤¹¡£ºÇ½é¤Î number ¤Ï¡¢µ¯¤³¤êÆÀ¤ë + ÆâÉô¥ê¥¯¥¨¥¹¥È¤ÎºÇÂçÃͤòÀßÄꤷ¤Þ¤¹¡£Æó¤Ä¤á¤Î number ¤Ï + ¥µ¥Ö¥ê¥¯¥¨¥¹¥È¤¬Æþ¤ì»Ò¤Ë¤Ç¤­¤ë¿¼¤µ¤òÀßÄꤷ¤Þ¤¹¡£number ¤ò + °ì¤Ä¤À¤±»ØÄꤷ¤¿¤È¤­¤Ï¡¢Î¾Êý¤Î¸Â³¦Ãͤˤ½¤ÎÃͤ¬ÀßÄꤵ¤ì¤Þ¤¹¡£

+ +

Îã

+ LimitInternalRecursion 5 +

+ +
+
top
+

LimitRequestBody ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤«¤éÁ÷¤é¤ì¤ë HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ü¥Ç¥£¤Î +ÁíÎ̤òÀ©¸Â¤¹¤ë
¹½Ê¸:LimitRequestBody bytes
¥Ç¥Õ¥©¥ë¥È:LimitRequestBody 0
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥ê¥¯¥¨¥¹¥È¥Ü¥Ç¥£¤Ëµö¤µ¤ì¤ë¥Ð¥¤¥È¿ô¡¢bytes + ¤ò 0 (̵À©¸Â¤ò°ÕÌ£¤·¤Þ¤¹) ¤«¤é 2147483647 (2GB) ¤Þ¤Ç¤Î¿ôÃͤǻØÄꤷ¤Þ¤¹¡£

+ +

LimitRequestBody ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬½ñ¤«¤ì¤¿¥³¥ó¥Æ¥­¥¹¥È + (¥µ¡¼¥ÐÁ´ÂΡ¢¥Ç¥£¥ì¥¯¥È¥ê¡¢¥Õ¥¡¥¤¥ë¡¢¥í¥±¡¼¥·¥ç¥ó) Æâ¤Ç + µöÍƤ¹¤ë HTTP ¥ê¥¯¥¨¥¹¥È¥á¥Ã¥»¡¼¥¸¥Ü¥Ç¥£¤Î¥µ¥¤¥º¤ËÀ©¸Â¤ò¤«¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤¬¤½¤ÎÀ©¸ÂÃͤò±Û¤¨¤Æ¤¤¤ì¤Ð¡¢ + ¥µ¡¼¥Ð¤Ï¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤»¤º¤Ë¥¨¥é¡¼¤òÊÖ¤·¤Þ¤¹¡£ + ÉáÄ̤Υꥯ¥¨¥¹¥È¥á¥Ã¥»¡¼¥¸¥Ü¥Ç¥£¤Î¥µ¥¤¥º¤Ï¡¢¥ê¥½¡¼¥¹¤Î¼ïÎà¤ä + µö²Ä¤µ¤ì¤Æ¤¤¤ë¥á¥½¥Ã¥É¤Ë¤è¤Ã¤ÆÂ礭¤¯ÊѤï¤ê¤Þ¤¹¡£ + CGI ¥¹¥¯¥ê¥×¥È¤Ï¡¢¤è¤¯¾ðÊó¤ò¼õ¿®¤¹¤ë¤¿¤á¤Ë + ¥á¥Ã¥»¡¼¥¸¥Ü¥Ç¥£¤ò»È¤¤¤Þ¤¹¡£ + PUT ¥á¥½¥Ã¥É¤Î¼ÂÁõ¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃͤȤ·¤Æ + ¾¯¤Ê¤¯¤È¤â¤¢¤ë¥ê¥½¡¼¥¹¤ËÂФ·¤Æ¥µ¡¼¥Ð¤¬¼õ¤±ÉÕ¤±¤è¤¦¤È¤¹¤ë + ɽ¸½¤ÎÂ礭¤µ¤Û¤É¤ÎÃͤòɬÍפȤ·¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ´ÉÍý¼Ô¤Ë¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î°Û¾ï¤Ê¥ê¥¯¥¨¥¹¥È¤òÀ©¸æ¤Ç¤­¤ë¤è¤¦¤Ë¤·¡¢ + ²¿¤é¤«¤Î·Á¤Î¥µ¡¼¥Ó¥¹µñÈݹ¶·â (ÌõÃí:DoS) ¤òÈò¤±¤ë¤Î¤ËÍ­¸ú¤Ç¤¹¡£

+ +

¤¢¤ë¾ì½ê¤Ø¤Î¥Õ¥¡¥¤¥ë¥¢¥Ã¥×¥í¡¼¥É¤òµö²Ä¤¹¤ë¾ì¹ç¤Ë¡¢ + ¥¢¥Ã¥×¥í¡¼¥É¤Ç¤­¤ë¥Õ¥¡¥¤¥ë¤Î¥µ¥¤¥º¤ò 100K ¤ËÀ©¸Â¤·¤¿¤±¤ì¤Ð¡¢ + °Ê²¼¤Î¤è¤¦¤Ë»ØÄꤷ¤Þ¤¹:

+ +

+ LimitRequestBody 102400 +

+ + +
+
top
+

LimitRequestFields ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤Î¿ô¤ò +À©¸Â¤¹¤ë
¹½Ê¸:LimitRequestFields number
¥Ç¥Õ¥©¥ë¥È:LimitRequestFields 100
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

number ¤Ë¤Ï¡¢0 (̵À©¸Â¤ò°ÕÌ£¤·¤Þ¤¹) ¤«¤é 32767 + ¤Þ¤Ç¤ÎÀ°¿ô¤ò»ØÄꤷ¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥ÈÃͤϡ¢Äê¿ô DEFAULT_LIMIT_REQUEST_FIELDS + ¤Ë¤è¤ê¥³¥ó¥Ñ¥¤¥ë»þ¤ËÄêµÁ¤µ¤ì¤Þ¤¹ (ÇÛÉÛ»þ¤Ë¤Ï 100 ¤È»ØÄꤵ¤ì¤Æ¤¤¤Þ¤¹)¡£

+ +

LimitRequestBody ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥µ¡¼¥Ð´ÉÍý¼Ô¤¬ HTTP ¥ê¥¯¥¨¥¹¥ÈÃæ¤Ë¤ª¤¤¤Æµö²Ä¤¹¤ë¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¿ô¤ò + »ØÄꤷ¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤Ï¤³¤ÎÃͤˤÏÄ̾ï¤Î¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤Ë´Þ¤Þ¤ì¤ë¤Ç¤¢¤í¤¦ + ¥Õ¥£¡¼¥ë¥É¤Î¿ô¤è¤êÂ礭¤ÊÃͤ¬É¬ÍפȤ·¤Þ¤¹¡£ + ¥¯¥é¥¤¥¢¥ó¥È¤Ë¤è¤ê»È¤ï¤ì¤¿Í×µá¥Ø¥Ã¥À¡¼¥Õ¥£¡¼¥ë¥É¤Î¿ô¤¬ + 20 ¤òĶ¤¨¤ë¤³¤È¤Ï¤Û¤È¤ó¤É¤¢¤ê¤Þ¤»¤ó¤¬¡¢ + ¤³¤ì¤Ï¼ï¡¹¤Î¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÂÁõ¤Ë¤è¤Ã¤ÆÊѤï¤ê¡¢ + ¾ÜºÙ¤Ê¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò¤¹¤ë¤¿¤á¤Î¥Ö¥é¥¦¥¶¤ÎÀßÄê¤Þ¤Ç¤Ë¤â + ±Æ¶Á¤µ¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¥ª¥×¥·¥ç¥ó¤Î HTTP ³ÈÄ¥¤Ï¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤ò»È¤Ã¤Æɽ¤µ¤ì¤ë¾ì¹ç¤¬ + ¿¤¯¤¢¤ê¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ´ÉÍý¼Ô¤Ë¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î°Û¾ï¤Ê¥ê¥¯¥¨¥¹¥È¤òÀ©¸æ¤Ç¤­¤ë¤è¤¦¤Ë¤·¡¢ + ²¿¤é¤«¤Î·Á¤Î¥µ¡¼¥Ó¥¹µñÈݹ¶·â (ÌõÃí:DoS) ¤òÈò¤±¤ë¤Î¤ËÍ­¸ú¤Ç¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¤Î¥Õ¥£¡¼¥ë¥É¤¬Â¿²á¤®¤ë¤³¤È¤ò°ÕÌ£¤¹¤ë¥¨¥é¡¼±þÅú¤¬ + ÉáÄ̤Υ¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤µ¤ì¤ë¤è¤¦¤Ê»þ¤Ï¤³¤ÎÃͤòÁý¤ä¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Îã:

+ +

+ LimitRequestFields 50 +

+ + +
+
top
+

LimitRequestFieldSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¤Î +¥µ¥¤¥º¤òÀ©¸Â¤¹¤ë
¹½Ê¸:LimitRequestFieldsize bytes
¥Ç¥Õ¥©¥ë¥È:LimitRequestFieldsize 8190
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À°ì¤Ä¤Ç¼õÉÕ¤±¤ë + ¥Ð¥¤¥È¿ô bytes ¤ò»ØÄꤷ¤Þ¤¹¡£

+ +

LimitRequestFieldSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤ÇµöÍƤµ¤ì¤ë¥µ¥¤¥º¤òÁý¸º¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃͤȤ·¤Æ¡¢ + °ìÈÌŪ¤Ê¥¯¥é¥¤¥¢¥ó¥È¤«¤é¥ê¥¯¥¨¥¹¥È¤¬Á÷¤é¤ì¤¿ºÝ¤Ë¡¢¤½¤Î¥ê¥¯¥¨¥¹¥È¤Ë + ÉÕ°¤·¤Æ¤¤¤ë¤É¤Î¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤Ë¤Ä¤¤¤Æ¤â¡¢ + ½½Ê¬Â­¤ê¤ëÂ礭¤µ¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + °ìÈÌŪ¤Ê¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Î¥µ¥¤¥º¤È¤¤¤Ã¤Æ¤â¡¢¤½¤ÎÂ礭¤µ¤Ï¸Ä¡¹¤Î + ¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÂÁõ¤Ë¤è¤Ã¤ÆÂ礭¤¯°Û¤Ê¤ê¡¢ + ¾ÜºÙ¤Ê¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤«¤É¤¦¤«¤Î¡¢ + ¥Ö¥é¥¦¥¶¤ÎÀßÄê¤Ë¤â±Æ¶Á¤µ¤ì¤¿¤ê¤·¤Þ¤¹¡£ + SPNEGO ǧ¾Ú¥Ø¥Ã¥À¤Ç¤Ï 12392 ¥Ð¥¤¥È¤Ë¤Þ¤ÇµÚ¤Ö¤³¤È¤¹¤é¤¢¤ê¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ´ÉÍý¼Ô¤Ë¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î°Û¾ï¤Ê¥ê¥¯¥¨¥¹¥È¤òÀ©¸æ¤Ç¤­¤ë¤è¤¦¤Ë¤·¡¢ + ²¿¤é¤«¤Î·Á¤Î¥µ¡¼¥Ó¥¹µñÈݹ¶·â (ÌõÃí:DoS) ¤òÈò¤±¤ë¤Î¤ËÍ­¸ú¤Ç¤¹¡£

+ +

Îã:

+ +

+ LimitRequestFieldSize 4094 +

+ +
Ä̾ï¤Ï¥Ç¥Õ¥©¥ë¥È¤«¤éÊѹ¹¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
+ + +
+
top
+

LimitRequestLine ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î HTTP ¥ê¥¯¥¨¥¹¥È¹Ô¤Î¥µ¥¤¥º¤òÀ©¸Â¤¹¤ë
¹½Ê¸:LimitRequestLine bytes
¥Ç¥Õ¥©¥ë¥È:LimitRequestLine 8190
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢HTTP ¥ê¥¯¥¨¥¹¥È¹ÔÆâ¤ÇµöÍƤµ¤ì¤ë¥Ð¥¤¥È¿ô + bytes ¤ò»ØÄꤷ¤Þ¤¹¡£

+ +

LimitRequestLine ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î HTTP ¥ê¥¯¥¨¥¹¥È¹Ô¤ÎµöÍÆ¥µ¥¤¥º¤òÁý¸º¤Ç¤­¤Þ¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¹Ô¤Ï¡¢HTTP¥á¥½¥Ã¥É¡¢URI¡¢¥×¥í¥È¥³¥ë¥Ð¡¼¥¸¥ç¥ó¤«¤éÀ®¤Ã¤Æ¤ª¤ê¡¢ + LimitRequestLine ¤Ï¥µ¡¼¥Ð¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ + µöÍƤ¹¤ë¥ê¥¯¥¨¥¹¥È URI ¤ÎŤµ¤òÀ©¸Â¤¹¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤Ï¡¢GET ¥ê¥¯¥¨¥¹¥È¤Î¥¯¥¨¥êÉôʬ¤â´Þ¤á¤Æ¡¢¥ê¥½¡¼¥¹¤Î̾Á°¤¬Æþ¤ë¤Ë­¤ë + Â礭¤µ¤òɬÍפȤ·¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ´ÉÍý¼Ô¤Ë¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î°Û¾ï¤Ê¥ê¥¯¥¨¥¹¥È¤òÀ©¸æ¤Ç¤­¤ë¤è¤¦¤Ë¤·¡¢ + ²¿¤é¤«¤Î·Á¤Î¥µ¡¼¥Ó¥¹µñÈݹ¶·â (ÌõÃí:DoS) ¤òÈò¤±¤ë¤Î¤ËÍ­¸ú¤Ç¤¹¡£

+ +

Îã:

+ +

+ LimitRequestLine 4094 +

+ +
Ä̾ï¤Ï¥Ç¥Õ¥©¥ë¥È¤«¤éÊѹ¹¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£
+ +
+
top
+

LimitXMLRequestBody ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:XML ·Á¼°¤Î¥ê¥¯¥¨¥¹¥È¤Î¥Ü¥Ç¥£¤Î¥µ¥¤¥º¤òÀ©¸Â¤¹¤ë
¹½Ê¸:LimitXMLRequestBody bytes
¥Ç¥Õ¥©¥ë¥È:LimitXMLRequestBody 1000000
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

XML ·Á¼°¤Î¥ê¥¯¥¨¥¹¥È¤Î¥Ü¥Ç¥£¤ÎºÇÂçÃͤò (¥Ð¥¤¥Èñ°Ì¤Ç) À©¸Â¤·¤Þ¤¹¡£ + ÃÍ¤Ë 0 ¤ò»ØÄꤹ¤ë¤È¥Á¥§¥Ã¥¯¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£

+ +

Îã:

+ +

+ LimitXMLRequestBody 0 +

+ + +
+
top
+

<Location> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:°Ï¤ó¤À¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¥Þ¥Ã¥Á¤¹¤ë URL ¤Î¤ß¤ËŬÍÑ
¹½Ê¸:<Location + URL-path|URL> ... </Location>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

<Location> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + URL ¤Ë¤è¤êÃæ¤Ë½ñ¤«¤ì¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎŬÍÑÈϰϤòÀ©¸Â¤·¤Þ¤¹¡£ + <Directory> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È»÷¤Æ¤¤¤Æ¡¢ + </Location> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç½ªÎ»¤¹¤ë + ¥µ¥Ö¥»¥¯¥·¥ç¥ó¤ò³«»Ï¤·¤Þ¤¹¡£ + <Location> ¥»¥¯¥·¥ç¥ó¤Ï¡¢ + <Directory> ¥»¥¯¥·¥ç¥ó¤È + .htaccess ¤ÎÆɤ߹þ¤ß¤Î¸å¡¢ + <Files> ¥»¥¯¥·¥ç¥ó¤ò + ŬÍѤ·¤¿¸å¤Ë¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤Ë¸½¤ì¤¿½ç¤Ë½èÍý¤µ¤ì¤Þ¤¹¡£

+ +

<Location> ¥»¥¯¥·¥ç¥ó¤Ï + ´°Á´¤Ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤È´ØÏ¢¤»¤º¤ËÆ°ºî¤·¤Þ¤¹¡£¤³¤Î¤³¤È¤«¤éƳ¤«¤ì¤ë + ·ë²Ì¤Ë¤Ï¤¤¤Ä¤¯¤«Ãí°Õ¤¹¤ëÅÀ¤¬¤¢¤ê¤Þ¤¹¡£ºÇ¤â½ÅÍפʤâ¤Î¤Ï¡¢ + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤ؤΥ¢¥¯¥»¥¹À©¸æ¤Ë <Location> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤Ù¤­¤Ç¤Ï¤Ê¤¤ + ¤È¤¤¤¦¤³¤È¤Ç¤¹¡£Ê£¿ô¤Î URL ¤¬¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎƱ¤¸°ÌÃ֤˥ޥåפµ¤ì¤ë + ²Äǽ¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢¤½¤Î¤è¤¦¤Ê¥¢¥¯¥»¥¹À©¸æ¤Ï²óÈò¤µ¤ì¤Æ¤·¤Þ¤¦²ÄǽÀ­¤¬ + ¤¢¤ê¤Þ¤¹¡£

+ +

¤¤¤Ä <Location> ¤ò»È¤¦¤«

+ +

<Location> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à³°¤Î¥³¥ó¥Æ¥ó¥Ä¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òŬÍѤ¹¤ë¤È¤­¤Ë + »ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¸ºß¤¹¤ë¥³¥ó¥Æ¥ó¥Ä¤ËÂФ·¤Æ¤Ï¡¢ + <Directory> ¤È <Files> ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£ + Îã³°¤Ï¡¢<Location /> ¤Ç¡¢¤³¤ì¤Ï¥µ¡¼¥ÐÁ´ÂΤËÂФ·¤Æ + ÀßÄê¤òŬÍѤ¹¤ë´Êñ¤ÊÊýË¡¤Ç¤¹¡£

+
+ +

Á´¤Æ¤Î (¥×¥í¥­¥·°Ê³°¤Î) ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¡¢ + URL ¤Ï /path/ ¤È¤¤¤¦¡¢ + ÀÜƬ¼­ http://servername ¤ò´Þ¤Þ¤Ê¤¤·Á¤Ç¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + ¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤Î¾ì¹ç¤Ë¤Ï¡¢scheme://servername/path + ¤È¤¤¤¦ÀÜƬ¼­¤ò´Þ¤à·Á¤Ç¥Þ¥Ã¥Á¤·¡¢ÀÜƬ¼­¤ò´Þ¤á¤Æ»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

URL ¤Ë¤Ï¥ï¥¤¥ë¥É¥«¡¼¥É¤òÍøÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ? ¤ÏǤ°Õ¤Î°ìʸ»ú¡¢* ¤ÏǤ°Õ¤Îʸ»úÎó¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£

+ +

~ ¤È¤¤¤¦Ê¸»ú¤òÄɲ乤뤳¤È¤Ç¡¢Àµµ¬É½¸½¤ò + ÍøÍѤ¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + Î㤨¤Ð:

+ +

+ <Location ~ "/(extra|special)/data"> +

+ +

¤Ï URL ¤Ë /extra/data ¤« /special/data ¤È¤¤¤¦Ê¸»úÎó¤¬ + ´Þ¤Þ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + <LocationMatch> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + <Location> ¤ÎÀµµ¬É½¸½ + ÈǤȤޤ俤¯Æ±¤¸Æ°ºî¤ò¤·¤Þ¤¹¡£

+ +

<Location> µ¡Ç½¤Ï¡¢SetHandler ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + Áȹç¤ï¤»¤ÆÍøÍѤ¹¤ë¤ÈÆäËÊØÍø¤Ç¤¹¡£ + Î㤨¤Ð¡¢foo.com ¤Î¥Ö¥é¥¦¥¶¤«¤é¤Î¤ß¥¹¥Æ¡¼¥¿¥¹¤Î»²¾È¤òÍ­¸ú¤Ë¤·¤¿¤±¤ì¤Ð¡¢ + ¼¡¤Î¤è¤¦¤Ë¤¹¤ì¤ÐÎɤ¤¤Ç¤·¤ç¤¦¡£

+ +

+ <Location /status>
+ + SetHandler server-status
+ Order Deny,Allow
+ Deny from all
+ Allow from .foo.com
+ + </Location> +

+ +

/ (¥¹¥é¥Ã¥·¥å) ¤Ë´Ø¤¹¤ëÃí

+

¥¹¥é¥Ã¥·¥åʸ»ú¤Ï¡¢URL Æâ¤Ë¸½¤ì¤ë¾ì½ê¤Ë±þ¤¸¤ÆÊѲ½¤¹¤ë + ÆÃÊ̤ʰÕÌ£¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¤ª¤¤¤ÆÍøÍѤ¹¤ë¾ì¹ç¤Ë¤ÏÊ£¿ô¤Î¥¹¥é¥Ã¥·¥å¤Ç¤â°ì¤Ä¤Î + ¥¹¥é¥Ã¥·¥å¤È¤·¤Æ°·¤ï¤ì¤ë¤³¤È¤¬Â¿¤¤¤Ç¤¹¤¬¡¢ + (¤¹¤Ê¤ï¤Á¡¢/home///foo ¤Ï + /home/foo ¤ÈƱ¤¸¤¤¤Ã¤¿¤è¤¦¤Ë) + URL ¤Ë¤ª¤¤¤Æ¤Ïɬ¤º¤·¤â¤½¤¦¤Ê¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + <LocationMatch> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤äÀµµ¬É½¸½¤òÍøÍѤ·¤¿ + <Location> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¡¢ + Ê£¿ô¤Î¥¹¥é¥Ã¥·¥å¤Ë¥Þ¥Ã¥Á¤µ¤»¤¿¤¤¤È¤­¤Ë¤Ï¡¢¡¢ÌÀ¼¨Åª¤Ëµ­½Ò¤¹¤ë + ɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢<LocationMatch ^/abc> ¤Ï¡¢ + /abc ¤È¤¤¤¦¥ê¥¯¥¨¥¹¥È URL ¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¤¬¡¢ + //abc ¤È¤¤¤¦¥ê¥¯¥¨¥¹¥È URL ¤Ë¤Ï¥Þ¥Ã¥Á¤·¤Þ¤»¤ó¡£ + (Àµµ¬É½¸½¤Ç¤Ê¤¤) <Location> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + proxy ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤ÆÍøÍѤ¹¤ëºÝ¤Ë¤ÏƱÍͤﶤëÉñ¤¤¤ò¤·¤Þ¤¹¤¬¡¢ + (Àµµ¬É½¸½¤Ç¤Ê¤¤) <Location> ¤ò proxy + ¤Ç¤Ê¤¤¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤ÆÍøÍѤ¹¤ëºÝ¤Ë¤Ï¡¢ + °ì¤Ä¤Î¥¹¥é¥Ã¥·¥å¤ÇÊ£¿ô¤Î¥¹¥é¥Ã¥·¥å¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ + Î㤨¤Ð¡¢<Location /abc/def> ¤È»ØÄꤷ¡¢ + /abc//def ¤È¤¤¤¦¥ê¥¯¥¨¥¹¥È¤¬¤¢¤ì¤Ð¡¢ + ¥Þ¥Ã¥Á¤¹¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ + +

»²¾È

+ +
+
top
+

<LocationMatch> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:°Ï¤ó¤À¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÀµµ¬É½¸½¤Ë¥Þ¥Ã¥Á¤¹¤ë URL ¤Î¤ß¤Ë +ŬÍÑ
¹½Ê¸:<LocationMatch + regex> ... </LocationMatch>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

<LocationMatch> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + <Location> ¤ÈƱ¤¸ÍÍ¤Ë + URL ¤Ë¤è¤êÃæ¤Ë½ñ¤«¤ì¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎŬÍÑÈϰϤòÀ©¸Â¤·¤Þ¤¹¡£ + ⤷¡¢°ú¿ô¤ÏÉáÄ̤Îʸ»úÎó¤Ç¤Ï¤Ê¤¯¡¢Àµµ¬É½¸½¤È¤Ê¤ê¤Þ¤¹¡£ + Î㤨¤Ð¡¢

+ +

+ <LocationMatch "/(extra|special)/data"> +

+ +

¤Ï URL ¤Ë /extra/data ¤« /special/data + ¤È¤¤¤¦Ê¸»úÎ󤬴ޤޤì¤Æ¤¤¤ë¾ì¹ç¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

LogLevel ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:ErrorLog ¤Î¾éĹÀ­¤òÀ©¸æ¤¹¤ë
¹½Ê¸:LogLevel level
¥Ç¥Õ¥©¥ë¥È:LogLevel warn
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

LogLevel ¤Ï¡¢¥¨¥é¡¼¥í¥° (ErrorLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ¸«¤Æ¤¯¤À¤µ¤¤) ¤Øµ­Ï¿¤¹¤ë¥á¥Ã¥»¡¼¥¸¤Î¾éĹÀ­¤òÄ´À°¤·¤Þ¤¹¡£ + °Ê²¼¤Î level ¤ò»ØÄê¤Ç¤­¡¢½ç¤Ë½ÅÍ×ÅÙ¤¬²¼¤¬¤Ã¤Æ¤¤¤­¤Þ¤¹¡£

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¥ì¥Ù¥ë ÀâÌÀ Îã
emerg ¶ÛµÞ - ¥·¥¹¥Æ¥à¤¬ÍøÍѤǤ­¤Ê¤¤Child cannot open lock file. Exiting + (»Ò¥×¥í¥»¥¹¤¬¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤ò³«¤±¤Ê¤¤¤¿¤á½ªÎ»¤·¤¿)
alert ľ¤Á¤ËÂн褬ɬÍ×getpwuid: couldn't determine user name from uid + (getpwuid: UID ¤«¤é¥æ¡¼¥¶Ì¾¤òÆÃÄê¤Ç¤­¤Ê¤«¤Ã¤¿)
crit Ã×̿Ū¤Ê¾õÂÖsocket: Failed to get a socket, exiting child + (socket: ¥½¥±¥Ã¥È¤¬ÆÀ¤é¤ì¤Ê¤¤¤¿¤á¡¢»Ò¥×¥í¥»¥¹¤ò½ªÎ»¤µ¤»¤¿)
error ¥¨¥é¡¼Premature end of script headers + (¥¹¥¯¥ê¥×¥È¤Î¥Ø¥Ã¥À¤¬Â­¤ê¤Ê¤¤¤Þ¤Þ¤Ç½ª¤ï¤Ã¤¿)
warn ·Ù¹ðchild process 1234 did not exit, sending another SIGHUP + (»Ò¥×¥í¥»¥¹ 1234 ¤¬½ªÎ»¤·¤Ê¤«¤Ã¤¿¡£¤â¤¦°ìÅÙ SIGHUP ¤òÁ÷¤ë)
notice ÉáÄ̤À¤¬¡¢½ÅÍפʾðÊóhttpd: caught SIGBUS, attempting to dump core in ... + (httpd: SIGBUS ¥·¥°¥Ê¥ë¤ò¼õ¤±¡¢... ¤Ø¥³¥¢¥À¥ó¥×¤ò¤·¤¿)
info ÄɲþðÊó"Server seems busy, (you may need to increase + StartServers, or Min/MaxSpareServers)..." (¡Ö¥µ¡¼¥Ð¤ÏÉé²Ù¤¬¹â¤¤¡¢ + (StartServers ¤ä Min/MaxSpareServers ¤ÎÃͤòÁý¤ä¤¹É¬Íפ¬¤¢¤ë¤«¤â)¡×)
debug ¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸"Opening config file ..." (ÀßÄê¥Õ¥¡¥¤¥ë¤ò³«¤¤¤Æ¤¤¤ë...)
+ +

ÆÃÄê¤Î¥ì¥Ù¥ë¤¬»ØÄꤵ¤ì¤¿¾ì¹ç¡¢¤½¤ì¤è¤ê¹â¤¤¥ì¥Ù¥ë¤ÎÁ´¤Æ¤Î¥á¥Ã¥»¡¼¥¸¤¬ + Êó¹ð¤µ¤ì¤Þ¤¹¡£ + Î㤨¤Ð¡¢LogLevel info ¤Ë»ØÄꤹ¤ë¤È¡¢ + notice ¤È warn ¤âÊó¹ð¤µ¤ì¤Þ¤¹¡£

+ +

¤Ê¤ª crit °Ê¾å¤Î¥ì¥Ù¥ë¤ò»ØÄꤹ¤ë¤³¤È¤¬¿ä¾©¤µ¤ì¤Þ¤¹¡£

+ +

Îã:

+ +

+ LogLevel notice +

+ +

Ãí

+

¥Õ¥¡¥¤¥ë¤Ë¥í¥°¤ò½ÐÎϤ¹¤ë¾ì¹ç¡¢notice + ¥ì¥Ù¥ë¤Î¥á¥Ã¥»¡¼¥¸¤ÏÍÞÀ©¤µ¤ì¤º¡¢¤¹¤Ù¤Æ¥í¥°¤Ë½ÐÎϤµ¤ì¤Þ¤¹¡£ + ¤·¤«¤· syslog ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¤³¤ì¤ÏÅö¤Æ¤Ï¤Þ¤ê¤Þ¤»¤ó¡£

+
+ +
+
top
+

MaxKeepAliveRequests ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:»ý³Ū¤ÊÀܳ¾å¤Çµö²Ä¤µ¤ì¤ë¥ê¥¯¥¨¥¹¥È¤Î¿ô
¹½Ê¸:MaxKeepAliveRequests number
¥Ç¥Õ¥©¥ë¥È:MaxKeepAliveRequests 100
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

MaxKeepAliveRequests ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + KeepAlive ¤¬Í­¸ú¤Ê¾ì¹ç¤Ë¡¢ + °ì²ó¤ÎÀܳ¤Ç¼õ¤±ÉÕ¤±²Äǽ¤Ê¥ê¥¯¥¨¥¹¥È¤Î¿ô¤òÀ©¸Â¤·¤Þ¤¹¡£ + 0 ¤ËÀßÄꤷ¤Æ¤¤¤ì¤Ð¡¢¼õ¤±ÉÕ¤±¤ë¥ê¥¯¥¨¥¹¥È¤Ï̵À©¸Â¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ÎÀßÄê¤Ï¡¢¥µ¡¼¥ÐÀ­Ç½¤ò¸þ¾å¤µ¤»¤ë¤¿¤á¤Ë¡¢Â礭¤Ê¿ôÃͤò»ØÄꤹ¤ë¤³¤È´«¤á¤Þ¤¹¡£ +

+ +

Îã:

+ +

+ MaxKeepAliveRequests 500 +

+ +
+
top
+

NameVirtualHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¤¿¤á¤Î IP ¥¢¥É¥ì¥¹¤ò»ØÄê
¹½Ê¸:NameVirtualHost addr[:port]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

NameVirtualHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÀßÄê¤ò¹Ô¤Ê¤¤¤¿¤¤¾ì¹ç¤Ë + ɬÍפȤʤë¤â¤Î¤Ç¤¹¡£

+ +

addr ¤Ë¤Ï¥Û¥¹¥È̾¤ò»ØÄê¤Ç¤­¤Þ¤¹¤¬¡¢ + ¾ï¤Ë IP ¥¢¥É¥ì¥¹¤ò»ØÄꤹ¤ë¤Î¤¬¿ä¾©¤µ¤ì¤Þ¤¹¡£ + Î㤨¤Ð¡¢

+ +

+ NameVirtualHost 111.22.33.44 +

+ +

NameVirtualHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò + ÍøÍѤ·¤Æ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤ë IP ¥¢¥É¥ì¥¹¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢ÉáÄ̤Ï̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¥¢¥É¥ì¥¹¤Ç¤¹¡£ + ¤¿¤À¤·¡¢¥Õ¥¡¥¤¥¢¡¼¥¦¥©¡¼¥ë¤ä¾¤Î¥×¥í¥­¥·¤¬¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¡¢ + °ã¤¦ IP ¥¢¥É¥ì¥¹¤Î¥µ¡¼¥Ð¤Ë¥Õ¥©¥ï¡¼¥É¤¹¤ë¤È¤¤¤¦¾ì¹ç¤Ï¡¢ + ¥ê¥¯¥¨¥¹¥È¤òÄ󶡤·¤¿¤¤¥Þ¥·¥ó¾å¤ÎʪÍý¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Î + IP ¥¢¥É¥ì¥¹¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + Ê£¿ô¤Î¥¢¥É¥ì¥¹¤ÇÊ£¿ô¤Î̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò»ØÄꤹ¤ë¾ì¹ç¤Ï + ³Æ¥¢¥É¥ì¥¹¤ËÂФ·¤Æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£

+ +

Ãæ

+

¡Ö¼ç¥µ¡¼¥Ð¡×¤ä¡¢¤É¤Î _default_ ¥µ¡¼¥Ð¤â¡¢ + NameVirtualHost ¤Ç»ØÄꤷ¤¿ IP ¥¢¥É¥ì¥¹¤Ø¤Î¥ê¥¯¥¨¥¹¥È + ¤ò½èÍý¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó (¤Ê¤¼¤« + NameVirtualHost ¤ò + »ØÄꤷ¤¿¤±¤É¤½¤Î¥¢¥É¥ì¥¹¤Ë VirtualHost ¤òÄêµÁ¤·¤Ê¤«¤Ã¤¿¾ì¹ç¤ò½ü¤¯)¡£

+
+ +

̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¥Ý¡¼¥ÈÈÖ¹æ¤ò»ØÄꤹ¤ë¤³¤È¤â²Äǽ¤Ç¤¹¡£ + Î㤨¤Ð

+ +

+ NameVirtualHost 111.22.33.44:8080 +

+ +

IPV6 ¤Î¥¢¥É¥ì¥¹¤Ï¼¡¤ÎÎã¤Î¤è¤¦¤Ë³Ñ³ç¸Ì¤Ç°Ï¤àɬÍפ¬¤¢¤ê¤Þ¤¹:

+ +

+ NameVirtualHost [2001:db8::a00:20ff:fea7:ccea]:8080 +

+ +

¤¹¤Ù¤Æ¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ + °ú¿ô¤È¤·¤Æ * ¤ò»È¤¤¤Þ¤¹¡£

+ +

+ NameVirtualHost * +

+ +

<VirtualHost> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô

+

<VirtualHost> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô¤Ï NameVirtualHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô¤ËÀµ³Î¤Ë + ¹ç¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ NameVirtualHost 1.2.3.4
+ <VirtualHost 1.2.3.4>
+ # ...
+ </VirtualHost>
+

+
+ + +

»²¾È

+ +
+
top
+

Options ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ·¤Æ»ÈÍѲÄǽ¤Êµ¡Ç½¤òÀßÄꤹ¤ë
¹½Ê¸:Options + [+|-]option [[+|-]option] ...
¥Ç¥Õ¥©¥ë¥È:Options All
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Options
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

Options ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ·¤Æ + ¤É¤Îµ¡Ç½¤¬»ÈÍѲÄǽ¤«¤òÀ©¸æ¤·¤Þ¤¹¡£

+ +

option ¤ò None¤Ë»ØÄꤹ¤ë¤È¡¢ + ÆÃÊ̤ʵ¡Ç½¤ÏÁ´¤Æ̵¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤Þ¤¿¡¢°Ê²¼¤Î¼¨¤¹ 1 ¸Ä°Ê¾å¤Î¤â¤Î¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£

+ +
+
All
+ +
MultiViews ¤ò½ü¤¤¤¿Á´¤Æ¤Îµ¡Ç½¤¬Í­¸ú¤È¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ì¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤¹¡£
+ +
ExecCGI
+ +
+ mod_cgi ¤Ë¤è¤ë CGI ¥¹¥¯¥ê¥×¥È¤Î¼Â¹Ô¤òµö²Ä¤·¤Þ¤¹¡£
+ +
FollowSymLinks
+ +
+ ¥µ¡¼¥Ð¤¬¡¢¤³¤Î¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ç¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò¤¿¤É¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ +

¥µ¡¼¥Ð¤¬¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò¤¿¤É¤ë¾ì¹ç¤Ç¤â¡¢ + <Directory> ¥»¥¯¥·¥ç¥ó¤Ë + ¥Þ¥Ã¥Á¤µ¤»¤ë¤¿¤á¤Î + ¥Ñ¥¹Ì¾¤ÏÊѹ¹¤µ¤ì¤Þ¤»¤ó¡£

+

<Location> Æâ¤Ë + ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Æ¤â̵»ë¤µ¤ì¤ë¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
Includes
+ +
+ mod_include ¤¬Ä󶡤¹¤ë SSI ¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£
+ +
IncludesNOEXEC
+ +
+ SSI ¤ÏÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢#exec ¥³¥Þ¥ó¥É ¤È #exec CGI ¤Ï̵¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤¿¤À¤·¡¢#include virtual ¤Ë¤è¤ê¡¢ScriptAlias ¤µ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Ç + CGI ¤ò¼Â¹Ô¤¹¤ë¤³¤È¤Ï²Äǽ¤Ç¤¹¡£
+ +
Indexes
+ +
+ ¤â¤·¡¢URL ¤¬¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥Þ¥Ã¥×¤¹¤ë¥ê¥¯¥¨¥¹¥È¤Ç¤¢¤Ã¤Æ¡¢ + ³î¤Ä DirectoryIndex ¤Ç»ØÄꤷ¤¿¥Õ¥¡¥¤¥ë (Î㤨¤Ð¡¢index.html) ¤¬ + ¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ë̵¤±¤ì¤Ð¡¢mod_autoindex ¤¬ + ¥Ç¥£¥ì¥¯¥È¥êÆâ¤Î°ìÍ÷¤òÀ°·Á¤·¤ÆÊÖ¤·¤Þ¤¹¡£
+ +
MultiViews
+ +
+ mod_negotiation ¤Ë¤è¤ë + ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó + ¤µ¤ì¤¿ "MultiViews" ¤òµö²Ä¤·¤Þ¤¹¡£
+ +
SymLinksIfOwnerMatch
+ +
+ ¥·¥ó¥Ü¥ê¥Ã¥¯Àè¤Î¥Õ¥¡¥¤¥ë¤Þ¤¿¤Ï¥Ç¥£¥ì¥¯¥È¥ê¤¬¡¢ + ¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤Î½êÍ­¥æ¡¼¥¶ ID ¤ÈƱ¤¸¾ì¹ç¤Ë¤Î¤ß¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò + ¤¿¤É¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ + +

Ãí

<Location> Æâ¤Ë¤³¤Î¥ª¥×¥·¥ç¥ó¤ò + »ØÄꤷ¤Æ¤â̵»ë¤µ¤ì¤Þ¤¹¡£
+
+
+ +

Ä̾¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ·¤ÆÊ£¿ô¤Î Options ¤¬ + ŬÍѲÄǽ¤Ê¾ì¹ç¡¢ + ºÇ¤â¶á¤¤¤â¤Î°ì¤Ä¤Î¤ß¤¬Å¬ÍѤµ¤ì¡¢Â¾¤Î¤â¤Î¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£ + Ê£¿ô¤Î»ØÄ꤬¥Þ¡¼¥¸¤µ¤ì¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£(¥»¥¯¥·¥ç¥ó¤Î¥Þ¡¼¥¸ÊýË¡¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£) + ¤·¤«¤·¡¢¤¹¤Ù¤Æ¤Î Options ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + ¤ä - ÉÕ¤­¤Ç + »ØÄꤵ¤ì¤¿¾ì¹ç¤Ï¥ª¥×¥·¥ç¥ó¤ÎÃͤϥޡ¼¥¸¤µ¤ì¤Þ¤¹¡£ + + ¤òƬ¤Ë¤Ä¤±¤ì¤Ð¸½ºß¤ÎÀßÄê¤Ë²Ã¤¨¤é¤ì¡¢ + - ¤òÉÕ¤±¤ì¤Ð¸½ºß¤ÎÀßÄ꤫¤éºï½ü¤µ¤ì¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢+ ¤ä - ¤òÍøÍѤ·¤Ê¤¤¾ì¹ç¤Ï:

+ +

+ <Directory /web/docs>
+ + Options Indexes FollowSymLinks
+ + </Directory>
+
+ <Directory /web/docs/spec>
+ + Options Includes
+ + </Directory> +

+ +

/web/docs/spec ¤È¤¤¤¦¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤Ï¡¢ + Includes ¤À¤±¤¬Å¬ÍѤµ¤ì¤Þ¤¹¡£ + ¤·¤«¤·¡¢2 ÈÖÌܤΠOptions ¤Ç + ¤ä - ¤òÍøÍѤ·¤Æ¤ß¤ë¤È:

+ +

+ <Directory /web/docs>
+ + Options Indexes FollowSymLinks
+ + </Directory>
+
+ <Directory /web/docs/spec>
+ + Options +Includes -Indexes
+ + </Directory> +

+ +

/web/docs/spec ¤È¤¤¤¦¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤Ï¡¢ FollowSymLinks ¤È + Includes ¤¬Å¬ÍѤµ¤ì¤Þ¤¹¡£

+ +

Ãí

+

-IncludesNOEXEC ¤â¤·¤¯¤Ï + -Includes ¤ò»ØÄꤹ¤ë¤È¡¢ + Á°¤ÎÀßÄ꤬¤É¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤è¤¦¤È¤â SSI ¤Ï̵¸ú¤È¤Ê¤ê¤Þ¤¹¡£

+
+ +

¤É¤Î¤è¤¦¤ÊÀßÄê¤â¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï All ¤Ë + ¤Ê¤ê¤Þ¤¹¡£

+ +
+
top
+

Require ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¤É¤Îǧ¾ÚºÑ¤ß¥æ¡¼¥¶¤¬¥ê¥½¡¼¥¹¤ò¥¢¥¯¥»¥¹¤Ç¤­¤ë¤«¤òÁªÂò¤¹¤ë
¹½Ê¸:Require entity-name [entity-name] ...
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Ç§¾Ú¤µ¤ì¤¿¥æ¡¼¥¶¤¬¥ê¥½¡¼¥¹¤ËÂФ·¤Æ + ¥¢¥¯¥»¥¹¤Ç¤­¤ë¤«¤òÀ©¸æ¤·¤Þ¤¹¡£ + À©¸Â¾ò·ï¤Ï¾µÇ§¥â¥¸¥å¡¼¥ë¤Ç½èÍý¤µ¤ì¤Þ¤¹¡£ + mod_authz_user ¤È mod_authz_groupfile + ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë¹½Ê¸¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ê¤â¤Î¤â¤¢¤ê¤Þ¤¹:

+ +
+
Require user userid [userid] ...
+ +
»ØÄꤵ¤ì¤¿¥æ¡¼¥¶¤Î¤ß¡¢¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¥¢¥¯¥»¥¹¤òµö²Ä¤·¤Þ¤¹¡£
+ +
Require group group-name [group-name] ...
+ +
»ØÄꤵ¤ì¤¿¥°¥ë¡¼¥×¤Ë°¤¹¤ë¥æ¡¼¥¶¤Î¤ß¡¢¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¥¢¥¯¥»¥¹¤òµö²Ä¤·¤Þ¤¹¡£
+ +
Require valid-user
+ +
Á´¤Æ¤Îǧ¾Ú¤µ¤ì¤¿¥æ¡¼¥¶¤Ë¡¢¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¥¢¥¯¥»¥¹¤òµö²Ä¤·¤Þ¤¹¡£
+
+ +

require ¥ª¥×¥·¥ç¥ó¤ò¼ÂÁõ¤·¤Æ¤¤¤ë¾¤Î¾µÇ§¥â¥¸¥å¡¼¥ë¤Ë¤Ï¡¢ + mod_authnz_ldap, + mod_authz_dbm, + mod_authz_owner ¤È¤¤¤Ã¤¿¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£

+ +

Require ¤Ï¡¢Àµ¤·¤¯Æ°ºî¤¹¤ë¤¿¤á¤Ë¤Ï AuthName µÚ¤Ó AuthType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä¡¢ + (¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤ò»ØÄꤹ¤ë¤¿¤á¤Ë) AuthUserFile µÚ¤Ó AuthGroupFile + ¤È¤¤¤Ã¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¶¦¤Ë + »ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + Î㤨¤Ð:

+ +

+ AuthType Basic
+ AuthName "Restricted Resource"
+ AuthUserFile /web/users
+ AuthGroupFile /web/groups
+ Require group admin +

+ +

¤³¤Î¤è¤¦¤Ë¤·¤ÆŬÍѤµ¤ì¤¿¥¢¥¯¥»¥¹À©¸æ¤Ï¡¢Á´¤Æ¤Î¥á¥½¥Ã¥É¤Ë + ÂФ·¤Æ¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£ + Ä̾ï¤Ï¡¢¤³¤ì¤¬Ë¾¤Þ¤·¤¤Æ°ºî¤Ç¤¹¡£ + ¤â¤·¡¢ÆÃÄê¤Î¥á¥½¥Ã¥É¤ËÂФ·¤Æ¤Î¤ß¥¢¥¯¥»¥¹¤ÎÀ©¸æ¤òŬÍѤ·¡¢ + ¾¤Î¥á¥½¥Ã¥É¤ÏÀ©¸Â¤·¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢<Limit> ¥»¥¯¥·¥ç¥óÆâ¤Ë + Require ¤ò + »ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£

+ +

Require ¤ò Allow ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä Deny ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + ÁȤ߹ç¤ï¤»¤Æ»È¤Ã¤¿¾ì¹ç¡¢¤³¤ì¤é¤ÎÀ©Ìó¤ÎÁê¸ßºîÍÑ¤Ï Satisfy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀ©¸æ¤µ¤ì¤Þ¤¹¡£ +

+ +

¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ÇÀ©¸æ¤ò²ò½ü¤¹¤ëÊýË¡

+

Satisfy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤Ç¡¢Êݸ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ç¥¢¥¯¥»¥¹À©¸æ¤ò + ̵¸ú¤Ë¤¹¤ëÎã¤Ï¡¢²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + mod_authz_host ¤Ë¤è¤ë¥¢¥¯¥»¥¹À©¸æ¤â̵¸ú²½¤µ¤ì¤ë¤Î¤Ç¡¢ + ¤³¤Î¥Æ¥¯¥Ë¥Ã¥¯¤ÏÃí°Õ¤·¤Æ¤´³èÍѤ¯¤À¤µ¤¤¡£

+

+ <Directory /path/to/protected/>
+ + Require user david
+ + </Directory>
+ <Directory /path/to/protected/unprotected>
+ + # All access controls and authentication are disabled
+ # in this directory
+ Satisfy Any
+ Allow from all
+ + </Directory>
+

+
+ + +

»²¾È

+ +
+
top
+

RLimitCPU ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤éµ¯Æ°¤µ¤ì¤¿¥×¥í¥»¥¹¤Î CPU ¾ÃÈñÎ̤ò +À©¸Â¤¹¤ë
¹½Ê¸:RLimitCPU seconds|max [seconds|max]
¥Ç¥Õ¥©¥ë¥È:̤ÀßÄê¡£¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ç¥Õ¥©¥ë¥È¤ò»ÈÍÑ
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

°ì¤Ä¤«Æó¤Ä¤Î¥Ñ¥é¥á¡¼¥¿¤ò¤È¤ê¤Þ¤¹¡£ + ºÇ½é¤Î¥Ñ¥é¥á¡¼¥¿¤ÏÁ´¥×¥í¥»¥¹¤ËÂФ¹¤ë¥ê¥½¡¼¥¹¤Î¥½¥Õ¥È¥ê¥ß¥Ã¥È¤òÀßÄꤷ¡¢ + 2 ÈÖÌܤΥѥé¥á¡¼¥¿¤ÏºÇÂç¤Î¥ê¥½¡¼¥¹¥ê¥ß¥Ã¥È¤òÀßÄꤷ¤Þ¤¹¡£ + ¥Ñ¥é¥á¡¼¥¿¤Ë¤Ï¿ô»ú¤«¡¢¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ÎºÇÂç¤È¤Ê¤ë + max ¤Î¤É¤Á¤é¤«¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ºÇÂç¤Î¥ê¥½¡¼¥¹¥ê¥ß¥Ã¥È¤ò¾å¤²¤ë¤¿¤á¤Ë¤Ï¡¢¥µ¡¼¥Ð¤ò + root ¤Ç¼Â¹Ô¤¹¤ë¤«µ¯Æ°¤µ¤ì¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£

+ +

¤Á¤Ê¤ß¤Ë¡¢¤³¤ÎÀßÄê¤Ï Apache ¤Î»Ò¥×¥í¥»¥¹¼«ÂΤǤϤʤ¯¡¢ + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤¿ Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤é fork ¤µ¤ì¤¿¥×¥í¥»¥¹¤Ë + ŬÍѤµ¤ì¤Þ¤¹¡£ + ¤³¤ì¤Ë¤Ï CGI ¤ä SSI ¤«¤é¼Â¹Ô¤µ¤ì¤¿¥³¥Þ¥ó¥É¤¬´Þ¤Þ¤ì¤Þ¤¹¤¬¡¢Apache ¤Î + ¿Æ¥×¥í¥»¥¹¤«¤é fork ¤µ¤ì¤¿¥í¥°¤Î¥Ñ¥¤¥×¥×¥í¥»¥¹¤Ê¤É¤Ë¤ÏŬÍѤµ¤ì¤Þ¤»¤ó¡£

+ +

CPU ¥ê¥½¡¼¥¹¤Î¥ê¥ß¥Ã¥È¤Ï¥×¥í¥»¥¹¤¢¤¿¤ê¤ÎÉÿô¤Çɽ¤ï¤µ¤ì¤Þ¤¹¡£

+ + +

»²¾È

+ +
+
top
+

RLimitMEM ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤éµ¯Æ°¤µ¤ì¤¿¥×¥í¥»¥¹¤Î¥á¥â¥ê¾ÃÈñÎ̤ò +À©¸Â¤¹¤ë
¹½Ê¸:RLimitMEM bytes|max [bytes|max]
¥Ç¥Õ¥©¥ë¥È:̤ÀßÄê¡£¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ç¥Õ¥©¥ë¥È¤ò»ÈÍÑ
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

°ì¤Ä¤«Æó¤Ä¤Î¥Ñ¥é¥á¡¼¥¿¤ò¤È¤ê¤Þ¤¹¡£ + ºÇ½é¤Î¥Ñ¥é¥á¡¼¥¿¤ÏÁ´¥×¥í¥»¥¹¤ËÂФ¹¤ë¥ê¥½¡¼¥¹¤Î¥½¥Õ¥È¥ê¥ß¥Ã¥È¤òÀßÄꤷ¡¢ + 2 ÈÖÌܤΥѥé¥á¡¼¥¿¤ÏºÇÂç¤Î¥ê¥½¡¼¥¹¥ê¥ß¥Ã¥È¤òÀßÄꤷ¤Þ¤¹¡£ + ¥Ñ¥é¥á¡¼¥¿¤Ë¤Ï¿ô»ú¤«¡¢¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ÎºÇÂç¤È¤Ê¤ë + max ¤Î¤É¤Á¤é¤«¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ºÇÂç¤Î¥ê¥½¡¼¥¹¥ê¥ß¥Ã¥È¤ò¾å¤²¤ë¤¿¤á¤Ë¤Ï¡¢¥µ¡¼¥Ð¤ò + root ¤Ç¼Â¹Ô¤¹¤ë¤«µ¯Æ°¤µ¤ì¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£

+ +

¤³¤ÎÀßÄê¤Ï Apache ¤Î»Ò¥×¥í¥»¥¹¼«ÂΤǤϤʤ¯¡¢ + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤¿ Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤é fork ¤µ¤ì¤¿¥×¥í¥»¥¹¤Ë + ŬÍѤµ¤ì¤Þ¤¹¡£ + ¤³¤ì¤Ë¤Ï CGI ¤ä SSI ¤«¤é¼Â¹Ô¤µ¤ì¤¿¥³¥Þ¥ó¥É¤¬´Þ¤Þ¤ì¤Þ¤¹¤¬¡¢Apache ¤Î + ¿Æ¥×¥í¥»¥¹¤«¤é fork ¤µ¤ì¤¿¥í¥°¤Î¥Ñ¥¤¥×¥×¥í¥»¥¹¤Ê¤É¤Ë¤ÏŬÍѤµ¤ì¤Þ¤»¤ó¡£

+ +

¥á¥â¥ê¥ê¥½¡¼¥¹¤Î¥ê¥ß¥Ã¥È¤Ï¥×¥í¥»¥¹¤¢¤¿¤ê¤Î¥Ð¥¤¥È¿ô¤Çɽ¤ï¤µ¤ì¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

RLimitNPROC ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤éµ¯Æ°¤µ¤ì¤¿¥×¥í¥»¥¹¤¬µ¯Æ°¤¹¤ë¥×¥í¥»¥¹¤Î +¿ô¤òÀ©¸Â¤¹¤ë
¹½Ê¸:RLimitNPROC number|max [number|max]
¥Ç¥Õ¥©¥ë¥È:̤ÀßÄê¡£¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ç¥Õ¥©¥ë¥È¤ò»ÈÍÑ
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

°ì¤Ä¤«Æó¤Ä¤Î¥Ñ¥é¥á¡¼¥¿¤ò¤È¤ê¤Þ¤¹¡£ + ºÇ½é¤Î¥Ñ¥é¥á¡¼¥¿¤ÏÁ´¥×¥í¥»¥¹¤ËÂФ¹¤ë¥ê¥½¡¼¥¹¤Î¥½¥Õ¥È¥ê¥ß¥Ã¥È¤òÀßÄꤷ¡¢ + 2 ÈÖÌܤΥѥé¥á¡¼¥¿¤ÏºÇÂç¤Î¥ê¥½¡¼¥¹¥ê¥ß¥Ã¥È¤òÀßÄꤷ¤Þ¤¹¡£ + ¥Ñ¥é¥á¡¼¥¿¤Ë¤Ï¿ô»ú¤«¡¢¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ÎºÇÂç¤È¤Ê¤ë + max ¤Î¤É¤Á¤é¤«¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ºÇÂç¤Î¥ê¥½¡¼¥¹¥ê¥ß¥Ã¥È¤ò¾å¤²¤ë¤¿¤á¤Ë¤Ï¡¢¥µ¡¼¥Ð¤ò + root ¤Ç¼Â¹Ô¤¹¤ë¤«µ¯Æ°¤µ¤ì¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£

+ +

¤³¤ÎÀßÄê¤Ï Apache ¤Î»Ò¥×¥í¥»¥¹¼«ÂΤǤϤʤ¯¡¢ + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤¿ Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤é fork ¤µ¤ì¤¿¥×¥í¥»¥¹¤Ë + ŬÍѤµ¤ì¤Þ¤¹¡£ + ¤³¤ì¤Ë¤Ï CGI ¤ä SSI ¤«¤é¼Â¹Ô¤µ¤ì¤¿¥³¥Þ¥ó¥É¤¬´Þ¤Þ¤ì¤Þ¤¹¤¬¡¢Apache ¤Î + ¿Æ¥×¥í¥»¥¹¤«¤é fork ¤µ¤ì¤¿¥í¥°¤Î¥Ñ¥¤¥×¥×¥í¥»¥¹¤Ê¤É¤Ë¤ÏŬÍѤµ¤ì¤Þ¤»¤ó¡£

+ +

¥×¥í¥»¥¹¤ÎÀ©¸Â¤Ï¡¢¥æ¡¼¥¶¤¢¤¿¤ê¤Î¥×¥í¥»¥¹¿ô¤ÇÀ©¸æ¤µ¤ì¤Þ¤¹¡£

+ +

Ãí

+

CGI ¥×¥í¥»¥¹¤¬¥¦¥§¥Ö¥µ¡¼¥Ð¤Î¥æ¡¼¥¶ ID °Ê³°¤Ç¼Â¹Ô¤µ¤ì¤ë¤Î¤Ç + ̵¤±¤ì¤Ð¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥µ¡¼¥Ð¼«¿È¤¬À¸À®¤Ç¤­¤ë¥×¥í¥»¥¹¤Î¿ô¤òÀ©¸Â¤¹¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤½¤Î¤è¤¦¤Ê¾õ¶·¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤«¤É¤¦¤«¤Ï¡¢error_log Ãæ¤Î + cannot fork ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤Ë¤è¤ê + ³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
+ +

»²¾È

+ +
+
top
+

Satisfy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:¥Û¥¹¥È¥ì¥Ù¥ë¤Î¥¢¥¯¥»¥¹À©¸æ¤È¥æ¡¼¥¶Ç§¾Ú¤È¤ÎÁê¸ßºîÍѤò»ØÄê
¹½Ê¸:Satisfy Any|All
¥Ç¥Õ¥©¥ë¥È:Satisfy All
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.0.51 °Ê¹ß¤Ç¤Ï <Limit> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È <LimitExcept> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î±Æ¶Á¤ò¼õ¤±¤ë +
+

Allow ¤È + Require ¤ÎξÊý¤¬»È¤ï¤ì¤Æ¤¤¤ë¤È¤­¤Î + ¥¢¥¯¥»¥¹¥Ý¥ê¥·¡¼¤òÀßÄꤷ¤Þ¤¹¡£¥Ñ¥é¥á¡¼¥¿¤Ï All ¤« Any + ¤Ç¤¹¡£¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¢¤ë¾ì½ê¤Ø¤Î¥¢¥¯¥»¥¹¤¬¥æ¡¼¥¶Ì¾/¥Ñ¥¹¥ï¡¼¥É + ¤È¥¯¥é¥¤¥¢¥ó¥È¤Î¥Û¥¹¥È¤Î¥¢¥É¥ì¥¹¤ÇÀ©¸Â¤µ¤ì¤Æ¤¤¤ë¤È¤­¤Ë¤Î¤ß + ÌòΩ¤Á¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî (All) ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤¬¥¢¥É¥ì¥¹¤Ë¤è¤ë + ¥¢¥¯¥»¥¹À©¸Â¤òËþ¤¿¤·¡¢¤«¤ÄÀµ¤·¤¤¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤òÆþÎϤ¹¤ë¤³¤È¤ò + Í׵ᤷ¤Þ¤¹¡£Any ¤Ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï¥Û¥¹¥È¤ÎÀ©¸Â¤òËþ¤¿¤¹¤«¡¢ + Àµ¤·¤¤¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤ÎÆþÎϤò¤¹¤ë¤«¤ò¤¹¤ì¤Ð¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¤¢¤ë¾ì½ê¤ò¥Ñ¥¹¥ï¡¼¥É¤ÇÊݸ¤ë¤±¤ì¤É¡¢ÆÃÄê¤Î¥¢¥É¥ì¥¹¤«¤é¤Î + ¥¯¥é¥¤¥¢¥ó¥È¤Ë¤Ï¥Ñ¥¹¥ï¡¼¥É¤ÎÆþÎϤòÍ׵᤻¤º¤Ë¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë¡¢ + ¤È¤¤¤¦¤è¤¦¤Ê¤È¤­¤Ë»ÈÍѤǤ­¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢Æ±¤¸¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Ë¤¤¤ë¿Í¤Ë¤Ï¥¦¥§¥Ö¥µ¥¤¥È¤Î¤¢¤ëÉôʬ¤Ë¤Ä¤¤¤Æ + ̵À©¸Â¤Î¥¢¥¯¥»¥¹¤òµö¤·¤¿¤¤¤±¤ì¤É¡¢³°¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤Î¿Í¤Ë¤Ï + ¥Ñ¥¹¥ï¡¼¥É¤òÄ󶡤µ¤»¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤ÊÀßÄê¤ò¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹:

+ +

+ Require valid-user
+ Allow from 192.168.1
+ Satisfy Any +

+ +

¥Ð¡¼¥¸¥ç¥ó 2.0.51 ¤«¤é¤Ï + <Limit> ¥»¥¯¥·¥ç¥ó¤È + <LimitExcept> ¥»¥¯¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç + Satisfy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + ŬÍѤµ¤ì¤ë¥á¥½¥Ã¥É¤òÀ©¸Â¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£

+ +

»²¾È

+ +
+
top
+

ScriptInterpreterSource ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:CGI ¥¹¥¯¥ê¥×¥È¤Î¥¤¥ó¥¿¡¼¥×¥ê¥¿¤Î°ÌÃÖ¤òÄ´¤Ù¤ë¤¿¤á¤Î¼êË¡
¹½Ê¸:ScriptInterpreterSource Registry|Registry-Strict|Script
¥Ç¥Õ¥©¥ë¥È:ScriptInterpreterSource Script
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Win32 ¤Î¤ß¡£ +¥ª¥×¥·¥ç¥ó Registry-Strict ¤Ï Apache 2.0 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Apache ¤Ç CGI ¥¹¥¯¥ê¥×¥È¤ò + ¼Â¹Ô¤¹¤ë¾ì¹ç¤ËÍøÍѤ¹¤ë¥¤¥ó¥¿¡¼¥×¥ê¥¿¤ò¡¢ + ¤É¤Î¤è¤¦¤Ëõ¤·½Ð¤¹¤«¤Ë¤Ä¤¤¤ÆÀ©¸æ¤¹¤ë¤¿¤á¤Ë»ÈÍѤ·¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Ï Script ¤Ç¤¹¡£¤³¤ì¤Ï¥¹¥¯¥ê¥×¥È¤Î + shebang ¹Ô (ºÇ½é¤Î¹Ô¤Ç #! ¤«¤é»Ï¤Þ¤ë¤â¤Î) + ¤Ë»Ø¤µ¤ì¤Æ¤¤¤ë¥¤¥ó¥¿¡¼¥×¥ê¥¿¤ò»ÈÍѤ·¤Þ¤¹¡£Win32 ¤Ç¤Ï¤½¤Î¹Ô¤Ï + °Ê²¼¤ÎÍͤˤʤê¤Þ¤¹¡£

+ +

+ #!C:/Perl/bin/perl.exe +

+ +

¤â¤·¤¯¤Ï¡¢perl ¤¬ PATH ¤Ë¤¢¤ë¾ì¹ç¤Ïñ¤Ë:

+ +

+ #!perl +

+ +

ScriptInterpreterSource Registry ¤ò»ØÄꤹ¤ë¤È¡¢ + ¥¹¥¯¥ê¥×¥È¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò (Î㤨¤Ð¡¢.pl) ¤ò + ¥­¡¼¤È¤·¤Æ¡¢Windows ¤Î¥ì¥¸¥¹¥È¥ê¥Ä¥ê¡¼ HKEY_CLASSES_ROOT + ¤ò¸¡º÷¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£¥ì¥¸¥¹¥È¥ê¤Î¥µ¥Ö¥­¡¼ + Shell\ExecCGI\Command ¤«¡¢¤½¤ì¤¬Â¸ºß¤·¤Ê¤¤¾ì¹ç¤Ï + Shell\Open\Command ¤¬¥¹¥¯¥ê¥×¥È¥Õ¥¡¥¤¥ë¤ò³«¤¯¤¿¤á¤Ë + »È¤ï¤ì¤Þ¤¹¡£¥ì¥¸¥¹¥È¥ê¥­¡¼¤¬¸«¤Ä¤«¤é¤Ê¤¤¤È¤­¤Ï¡¢Apache ¤Ï Script + ¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤¿¤È¤­¤ÎÆ°ºî¤ËÌá¤ê¤Þ¤¹¡£

+ +

¥»¥­¥å¥ê¥Æ¥£

+

ScriptInterpreterSource Registry ¤ò ScriptAlias ¤µ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Ç»È¤¦¤È¤­¤Ï + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£Apache ¤Ï¤½¤Î¥Ç¥£¥ì¥¯¥È¥êÃæ¤Î¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò + ¼Â¹Ô¤·¤è¤¦¤È¤·¤Þ¤¹¡£Registry ¤È¤¤¤¦ÀßÄê¤ÏÄ̾ï¤Ï¼Â¹Ô¤µ¤ì¤Ê¤¤ + ¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ˾¤Þ¤·¤¯¤Ê¤¤¥×¥í¥°¥é¥à¤Î¼Â¹Ô¤¬È¯À¸¤¹¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ + Î㤨¤Ð¡¢¤Û¤È¤ó¤É¤Î Windows ¥·¥¹¥Æ¥à¤Ç¡¢ + .htm ¥Õ¥¡¥¤¥ë¤Î¥Ç¥Õ¥©¥ë¥È¤Î¡Ö³«¤¯¡×¥³¥Þ¥ó¥É¤Ï + Microsoft Internet Explorer ¤ò¼Â¹Ô¤·¤Þ¤¹¤Î¤Ç¡¢¥¹¥¯¥ê¥×¥È¤Ë»ØÄꤵ¤ì¤¿ + ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë .htm ¥Õ¥¡¥¤¥ë¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï¥µ¡¼¥Ð¤Î + ¥Ð¥Ã¥¯¥°¥é¥¦¥ó¥É¤Ç¥Ö¥é¥¦¥¶¤ò¼Â¹Ô¤¹¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤ì¤Ï¡¢°ìʬÆ⤯¤é¤¤¤Ç + ¥·¥¹¥Æ¥à¤ò¥¯¥é¥Ã¥·¥å¤µ¤ë¤¿¤á¤ÎÎɤ¤ÊýË¡¤Ç¤¹¡£

+
+ +

Apache 2.0 ¤«¤éƳÆþ¤µ¤ì¤¿¥ª¥×¥·¥ç¥ó Registry-Strict ¤Ï + Registry ¤ÈƱ¤¸¤³¤È¤ò¹Ô¤Ê¤¤¤Þ¤¹¤¬¡¢¥µ¥Ö¥­¡¼ + Shell\ExecCGI\Command ¤Î¤ß¤ò»È¤¤¤Þ¤¹¡£ + ExecCGI ¥­¡¼¤ÏÉáÄ̤˻Ȥï¤ì¤ë¥­¡¼¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£Windows + ¥ì¥¸¥¹¥È¥ê¤Ë¼êÆ°¤ÇÀßÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢¥·¥¹¥Æ¥à¤Ç¤Î¶öȯŪ¤Ê¥×¥í¥°¥é¥à¤Î + ¼Â¹Ô¤òËɤ°¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +
+
top
+

ServerAdmin ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ë¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Ë´Þ¤á¤ëÅŻҥ᡼¥ë¤Î +¥¢¥É¥ì¥¹
¹½Ê¸:ServerAdmin email-address|URL
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

ServerAdmin ¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤¹¤µ¤Þ¤¶¤Þ¤Ê + ¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸Ãæ¤Ëµ­½Ò¤¹¤ë¡¢ + Ìä¹ç¤»¥¢¥É¥ì¥¹¤òÀßÄꤷ¤Þ¤¹¡£Í¿¤¨¤é¤ì¤¿°ú¿ô¤ò httpd ¤¬ + URL ¤Èǧ¼±¤·¤Ê¤¤¾ì¹ç¤Ï¡¢email-address ¤À¤È²ò¼á¤·¤Æ¡¢ + ¥Ï¥¤¥Ñ¡¼¥ê¥ó¥¯¤Î¥¿¡¼¥²¥Ã¥È¤Ë mailto: ¤òÉÕ¤±¤Þ¤¹¡£ + ¼ÂºÝ¤Ë¤Ï¡¢¤³¤³¤Ë¤ÏÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤ò»È¤¦¤³¤È¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¿¤¯¤Î CGI ¥¹¥¯¥ê¥×¥È¤Ï¤½¤¦¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤ò²¾Äꤷ¤Æ¤¤¤Þ¤¹¡£ + URL ¤ò»È¤¦¾ì¹ç¤Ï¡¢¤¢¤Ê¤¿¤Î´ÉÍý²¼¤Ë¤¢¤ëÊÌ¥µ¡¼¥Ð¤ò»Ø¤¹¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤½¤¦¤Ç¤Ê¤¤¤È¡¢¥¨¥é¡¼¤¬µ¯¤³¤Ã¤¿¤È¤­¤ËÏ¢Íí¤ò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¯¤Ê¤Ã¤Æ + ¤·¤Þ¤¤¤Þ¤¹¡£ +

+ +

¤½¤ÎºÝ¡¢¤³¤ì¤Î¤¿¤á¤ËÀìÍѤΥ¢¥É¥ì¥¹¤òÀßÄꤹ¤ë¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£ + Î㤨¤Ð¡¢

+ +

+ ServerAdmin www-admin@foo.example.com +

+ +

¤È¤¤¤Ã¤¿¤è¤¦¤Ë¤·¤Þ¤¹¡£¥æ¡¼¥¶¤Ï¤¤¤Ä¤â¥µ¡¼¥Ð¤Ë´Ø¤¹¤ëÏäǤ¢¤ë¤È¤¤¤¦¤³¤È¤ò + ÌÀµ­¤·¤Æ¤¯¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤Î¤Ç¡£

+ + +
+
top
+

ServerAlias ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤ò̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¥Þ¥Ã¥Á¤µ¤»¤Æ¤¤¤ë¤È¤­¤Ë +»ÈÍѤµ¤ì¤ë¥Û¥¹¥È¤ÎÊÌ̾
¹½Ê¸:ServerAlias hostname [hostname] ...
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

ServerAlias ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥Í¡¼¥à¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¤ª¤¤¤Æ + »ÈÍѤ¹¤ë¥Û¥¹¥È¤ÎÊÌ̾¤ò»ØÄꤷ¤Þ¤¹¡£

+ +

+ <VirtualHost *>
+ ServerName server.domain.com
+ ServerAlias server server2.domain.com server2
+ # ...
+ </VirtualHost> +

+ +

»²¾È

+ +
+
top
+

ServerName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬¼«Ê¬¼«¿È¤ò¼¨¤¹¤È¤­¤Ë»È¤¦¥Û¥¹¥È̾¤È¥Ý¡¼¥È
¹½Ê¸:ServerName fully-qualified-domain-name[:port]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Ð¡¼¥¸¥ç¥ó 2.0 ¤Ç¤Ï¥Ð¡¼¥¸¥ç¥ó 1.3 ¤Î + Port ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Îµ¡Ç½¤â´Þ¤ß¤Þ¤¹¡£
+

ServerName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥µ¡¼¥Ð¤¬¼«Ê¬¼«¿È¤ò¼¨¤¹¥Û¥¹¥È̾¤È¥Ý¡¼¥È¤òÀßÄꤷ¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë URL ¤òÀ¸À®¤¹¤ëºÝ¤ËÍøÍѤµ¤ì¤Þ¤¹¡£ + Î㤨¤Ð¡¢¥¦¥§¥Ö¥µ¡¼¥Ð¤òÆ°¤«¤·¤Æ¤¤¤ë¥Þ¥·¥ó¤Ï simple.example.com + ¤Ç¡¢DNS ¤Î¥¨¥¤¥ê¥¢¥¹ www.example.com ¤â¤¢¤ë¤È¤­¤Ë¡¢ + ¥¦¥§¥Ö¥µ¡¼¥Ð¤¬¸å¼Ô¤È¤·¤Æǧ¼±¤µ¤ì¤ÆÍߤ·¤¤¤È¤­¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤¤¤Þ¤¹¡£

+ +

+ ServerName www.example.com:80 +

+ +

ServerName ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ï¡¢ + ¥µ¡¼¥Ð¤Ï IP ¥¢¥É¥ì¥¹¤«¤éµÕ°ú¤­¤ò¹Ô¤Ê¤¦¤³¤È¤Ç¥Û¥¹¥È̾¤òÃÎ¤í¤¦¤È¤·¤Þ¤¹¡£ + ServerName ¤Ë¥Ý¡¼¥È¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ï¡¢ + ¥µ¡¼¥Ð¤Ï¥ê¥¯¥¨¥¹¥È¤¬Íè¤Æ¤¤¤ë + ¥Ý¡¼¥È¤ò»È¤¤¤Þ¤¹¡£ºÇ¹â¤Î¿®ÍêÀ­¤È³Î¼ÂÀ­¤ò¤â¤¿¤é¤¹¤¿¤á¤Ë¤Ï¡¢ + ServerName ¤ò»È¤Ã¤Æ¥Û¥¹¥È̾¤È¥Ý¡¼¥È¤òÌÀ¼¨Åª¤Ë + »ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£

+ +

̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È + ¤òÍøÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢<VirtualHost> ¥»¥¯¥·¥ç¥óÆâ¤Î + ServerName ¤Ï¤³¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¥Þ¥Ã¥Á¤¹¤ë¤¿¤á¤Ë + ²¿¤¬¥ê¥¯¥¨¥¹¥È¤Î Host: ¥Ø¥Ã¥À¤Ë¸½¤ì¤ëɬÍפ¬¤¢¤ë¤Î¤«¤ò»ØÄꤷ¤Þ¤¹¡£

+ +

¼«¸Ê»²¾È URL (Î㤨¤Ð mod_dir ¥â¥¸¥å¡¼¥ë¤Ë¤è¤ë¤â¤Î¤Ê¤É) + ¤¬»ØÄꤵ¤ì¤¿¥Ý¡¼¥È¤ò»È¤¦¤«¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤Î¥Ý¡¼¥ÈÈÖ¹æ¤ò»È¤¦¤«¤ò + ·èÄꤹ¤ëÀßÄê¤Ï UseCanonicalName + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È UseCanonicalPhysicalPort + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

»²¾È

+ +
+
top
+

ServerPath ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:Èó¸ß´¹¤Î¥Ö¥é¥¦¥¶¤¬Ì¾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¥¢¥¯¥»¥¹¤·¤¿¤È¤­¤Î +¤¿¤á¤Î¸ß´¹ÍÑ URL ¥Ñ¥¹Ì¾
¹½Ê¸:ServerPath URL-path
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

ServerPath ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥Í¡¼¥à¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¤ª¤¤¤ÆÍøÍѤ¹¤ë + ¸ß´¹ÍÑ URL ¥Ñ¥¹Ì¾¤òÀßÄꤷ¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

ServerRoot ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤¿¥µ¡¼¥Ð¤Î¥Ù¡¼¥¹¥Ç¥£¥ì¥¯¥È¥ê
¹½Ê¸:ServerRoot directory-path
¥Ç¥Õ¥©¥ë¥È:ServerRoot /usr/local/apache
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

ServerRoot ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥µ¡¼¥Ð¤¬Â¸ºß¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤òÀßÄꤷ¤Þ¤¹¡£ + Ä̾conf/ ¤ä logs/ ¤È¤¤¤Ã¤¿¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤¬ + ¸ºß¤·¤Þ¤¹¡£ + ¤Þ¤¿¡¢Â¾¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö (Î㤨¤Ð Include ¤ä LoadModule ¤Ê¤É) ¤Ë¤ª¤±¤ëÁêÂХѥ¹¤Ï¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤ÎÁêÂаÌÃ֤Ȥʤê¤Þ¤¹¡£

+ +

Îã

+ ServerRoot /home/httpd +

+ + + +

»²¾È

+ +
+
top
+

ServerSignature ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬À¸À®¤¹¤ë¥É¥­¥å¥á¥ó¥È¤Î¥Õ¥Ã¥¿¤òÀßÄê
¹½Ê¸:ServerSignature On|Off|EMail
¥Ç¥Õ¥©¥ë¥È:ServerSignature Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

ServerSignature ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥µ¡¼¥Ð¤¬À¸À®¤¹¤ë¥É¥­¥å¥á¥ó¥È + (¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¡¢mod_proxy ¤Ë¤ª¤±¤ë FTP ¤Î¥Ç¥£¥ì¥¯¥È¥ê¥ê¥¹¥È¡¢ + mod_info ¤Î½ÐÎÏ¡¢Åù¡¹) + ¤ÎºÇ²¼¹Ô¤ËÉÕÍ¿¤¹¤ë¥Õ¥Ã¥¿¤ÎÀßÄê¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£ + ¤½¤Î¤è¤¦¤Ê¥Õ¥Ã¥¿¹Ô¤òÍ­¸ú¤Ë¤·¤¿¤¤Íýͳ¤Ë¤Ï¡¢ + ¥×¥í¥­¥·¤¬Ê£¿ôÏ¢¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¡¢¥æ¡¼¥¶¤Ï¤É¤Î¥µ¡¼¥Ð¤¬ÊÖ¤·¤¿ + ¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤«¤òÃΤë¼êÃʤ¬¤Û¤È¤ó¤É̵¤¤¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£

+ + +

¥Ç¥Õ¥©¥ë¥È¤Ç¤¢¤ë Off ¤ËÀßÄê¤ò¤¹¤ë¤È¡¢¥Õ¥Ã¥¿¹Ô¤¬ÍÞÀ©¤µ¤ì¤Þ¤¹ + (¤½¤·¤Æ¡¢Apache-1.2 °ÊÁ°¤È¸ß´¹¤ÎÆ°ºî¤ò¤·¤Þ¤¹)¡£ + On ¤ËÀßÄꤷ¤¿¾ì¹ç¤Ï¡¢Ã±¤Ë¥É¥­¥å¥á¥ó¥È¤ÎÃæ¤Ë¡¢¥µ¡¼¥Ð¤Î¥Ð¡¼¥¸¥ç¥ó¡¢ + ²ÔÆ°Ãæ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î ServerName ¤Î½ñ¤«¤ì¤¿¹Ô¤òÄɲä·¡¢ + EMail ¤Ë¤·¤¿¾ì¹ç¤Ï¤µ¤é¤Ë»²¾È¤µ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤ËÂФ¹¤ë ServerAdmin ¤ò»Ø¤¹ "mailto:" ¤¬Äɲ䵤ì¤Þ¤¹¡£

+ +

¥Ð¡¼¥¸¥ç¥ó 2.0.44 °Ê¹ß¤Ç¤Ï¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï ServerSignature + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤êɽ¼¨¤µ¤ì¤ë¾ðÊó¤âÀ©¸æ¤·¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

ServerTokens ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:Server HTTP ±þÅú¥Ø¥Ã¥À¤òÀßÄꤹ¤ë
¹½Ê¸:ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full
¥Ç¥Õ¥©¥ë¥È:ServerTokens Full
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤êÊÖ¤¹ Server + ±þÅú¥Ø¥Ã¥ÀÆâ¤Ë¡¢¥µ¡¼¥Ð¤Î°ìÈÌŪ¤Ê OS ¼ïÊ̤䡢 + ¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤ÆÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¥â¥¸¥å¡¼¥ë¤Î¾ðÊó¤ò + ´Þ¤á¤ë¤«¤É¤¦¤«¤ò»ØÄꤷ¤Þ¤¹¡£

+ +
+
ServerTokens Prod[uctOnly]
+ +
¥µ¡¼¥Ð¤Ï (Î㤨¤Ð): Server: + Apache ¤È¤¤¤Ã¤¿¤è¤¦¤ËÁ÷¤ê¤Þ¤¹¡£
+ +
ServerTokens Major
+ +
Server sends (e.g.): Server: + Apache/2
+ +
ServerTokens Minor
+ +
Server sends (e.g.): Server: + Apache/2.0
+ +
ServerTokens Min[imal]
+ +
¥µ¡¼¥Ð¤Ï (Î㤨¤Ð): Server: + Apache/2.0.41 ¤È¤¤¤Ã¤¿¤è¤¦¤ËÁ÷¤ê¤Þ¤¹¡£
+ +
ServerTokens OS
+ +
¥µ¡¼¥Ð¤Ï (Î㤨¤Ð): Server: Apache/2.0.41 + (Unix) ¤È¤¤¤Ã¤¿¤è¤¦¤ËÁ÷¤ê¤Þ¤¹¡£
+ +
ServerTokens Full (¤â¤·¤¯¤Ï̤»ØÄê)
+ +
¥µ¡¼¥Ð¤Ï (Î㤨¤Ð): Server: Apache/2.0.41 + (Unix) PHP/4.2.2 MyMod/1.2 ¤È¤¤¤Ã¤¿¤è¤¦¤ËÁ÷¤ê¤Þ¤¹¡£
+
+ +

¤³¤ÎÀßÄê¤Ï¥µ¡¼¥ÐÁ´ÂΤËŬÍѤµ¤ì¡¢¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¾å¤ÇÍ­¸ú¤Ë¤·¤¿¤ê + ̵¸ú¤Ë¤·¤¿¤ê¤Ï¤Ç¤­¤Þ¤»¤ó¡£

+ +

¥Ð¡¼¥¸¥ç¥ó 2.0.44 °Ê¹ß¤Ç¤Ï¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï ServerSignature + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤êɽ¼¨¤µ¤ì¤ë¾ðÊó¤âÀ©¸æ¤·¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

SetHandler ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë¤¬¥Ï¥ó¥É¥é¤Ç½èÍý¤µ¤ì¤ë¤è¤¦¤Ë¤¹¤ë
¹½Ê¸:SetHandler handler-name|None
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Apache 2.0 ¤Ç core ¤Ë°ÜÆ°
+

.htaccess ¤ä <Directory> + ¥»¥¯¥·¥ç¥ó¡¢<Location> + ¥»¥¯¥·¥ç¥ó¤Ë½ñ¤«¤ì¤¿¾ì¹ç¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤½¤³¤Ë¤¢¤ë¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤¬ + handler-name ¤Ç»ØÄꤵ¤ì¤¿¥Ï¥ó¥É¥é¤Ç°·¤ï¤ì¤ë¤³¤È¤ò¶¯À©¤·¤Þ¤¹¡£Î㤨¤Ð¡¢³ÈÄ¥»Ò¤Ë´Ø¤ï¤é¤º¡¢ + ¥Ç¥£¥ì¥¯¥È¥êÁ´ÂΤ¬¥¤¥á¡¼¥¸¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤È¤·¤Æ²òÀϤ·¤ÆÍߤ·¤¤¾ì¹ç¤Ë¤Ï¡¢ + °Ê²¼¤ò¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î .htaccess + ¥Õ¥¡¥¤¥ë¤Ëµ­½Ò¤·¤Þ¤¹:

+ +

+ SetHandler imap-file +

+ +

Ê̤ÎÎã: URL http://servername/status + ¤¬»ØÄꤵ¤ì¤¿¤È¤­¤Ë¥µ¡¼¥Ð¤¬¾õÂÖÊó¹ð¤ò¤¹¤ë¤è¤¦¤Ë¤·¤¿¤¤¤È¤­¤Ï¡¢°Ê²¼¤ò + httpd.conf ¤Ëµ­½Ò¤·¤Þ¤¹:

+ +

+ <Location /status>
+ + SetHandler server-status
+ + </Location> +

+ +

None ¤È¤¤¤¦ÃͤòÀßÄꤹ¤ë¤³¤È¤Ç¡¢ + Á°¤ÎÊý¤Î SetHandler ¤ÇÄêµÁ¤µ¤ì¤¿ÀßÄê¤ò̵¸ú¤Ë¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+

Ãí°Õ:SetHandler ¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¥Ï¥ó¥É¥é¤ò¥ª¡¼¥Ð¡¼¥é¥¤¥É + ¤·¤Þ¤¹¤Î¤Ç¡¢Ä̾ï¤ÎµóÆ°¡¢¤¿¤È¤¨¤Ð¡¢¥¹¥é¥Ã¥·¥å (/) ¤Ç½ª¤ï¤ë URL ¤¬ + ¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¤È¤­¤Ë¥Ç¥£¥ì¥¯¥È¥ê¤ä¥¤¥ó¥Ç¥Ã¥¯¥¹¥Õ¥¡¥¤¥ë¤òÊÖ¤¹¤è¤¦¼è¤ê°·¤¦µóÆ°¤Ï¡¢ + ¹Ô¤ï¤ì¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£ +

+ + +

»²¾È

+ +
+
top
+

SetInputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ä POST ¤ÎÆþÎϤò½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤òÀßÄꤹ¤ë
¹½Ê¸:SetInputFilter filter[;filter...]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

SetInputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Î + ¥ê¥¯¥¨¥¹¥È¤ä POST ¤ÎÆþÎϤò¥µ¡¼¥Ð¤¬¼õ¤±¼è¤Ã¤¿¤È¤­¤Ë½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤ò + ÀßÄꤷ¤Þ¤¹¡£¤³¤ì¤Ï AddInputFilter + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò´Þ¤á¡¢Â¾¤Î¾ì½ê¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë¥Õ¥£¥ë¥¿¤ÎÀßÄê¤Ë + Äɲ䵤ì¤Þ¤¹¡£

+ +

Ê£¿ô¤Î¥Õ¥£¥ë¥¿¤ò»ØÄꤹ¤ë¤È¤­¤Ï¡¢¥Ç¡¼¥¿¤ò½èÍý¤¹¤ë½çÈÖ¤Ë + ¥»¥ß¥³¥í¥ó¤Ç¶èÀÚ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ + +

»²¾È

+ +
+
top
+

SetOutputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤Î±þÅú¤ò½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤òÀßÄꤹ¤ë
¹½Ê¸:SetOutputFilter filter[;filter...]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

SetOutputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥µ¡¼¥Ð¤Î±þÅú¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤êÊÖ¤µ¤ì¤ëÁ°¤Ë½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤òÀßÄꤷ¤Þ¤¹¡£ + ¤³¤ì¤Ï AddOutputFilter + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò´Þ¤á¡¢Â¾¤Î¾ì½ê¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë¥Õ¥£¥ë¥¿¤ÎÀßÄê¤Ë + Äɲ䵤ì¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢°Ê²¼¤ÎÀßÄê¤Ï /www/data/ ¥Ç¥£¥ì¥¯¥È¥ê¤Î¤¹¤Ù¤Æ¤Î + ¥Õ¥¡¥¤¥ë¤ò SSI ¤Ç½èÍý¤·¤Þ¤¹¡£

+ +

+ <Directory /www/data/>
+ + SetOutputFilter INCLUDES
+ + </Directory> +

+ +

Ê£¿ô¤Î¥Õ¥£¥ë¥¿¤ò»ØÄꤹ¤ë¤È¤­¤Ï¡¢¥Ç¡¼¥¿¤ò½èÍý¤¹¤ë½çÈÖ¤Ë + ¥»¥ß¥³¥í¥ó¤Ç¶èÀÚ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

TimeOut ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:³Æ¥¤¥Ù¥ó¥È¤Ë¤Ä¤¤¤Æ¡¢¥ê¥¯¥¨¥¹¥È¤ò¼ºÇÔ¤µ¤»¤ë¤Þ¤Ç¤Ë¥µ¡¼¥Ð¤¬ +ÂԤĻþ´Ö¤òÀßÄê
¹½Ê¸:TimeOut seconds
¥Ç¥Õ¥©¥ë¥È:TimeOut 300
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

TimeOut ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¸½ºß¤Î¤È¤³¤í + °Ê²¼¤Î»°¤Ä¤ÎÂÔ¤Á»þ´Ö¤Ë¤Ä¤¤¤Æ¤ÎÄêµÁ¤ò¹Ô¤¤¤Þ¤¹:

+ +
    +
  1. GET ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤ë¤Î¤Ë¤«¤«¤ëÁí»þ´Ö
    2. + +
  2. POST ¤ä PUT¥ê¥¯¥¨¥¹¥È¤Ë¤ª¤¤¤Æ¡¢¼¡¤Î TCP ¥Ñ¥±¥Ã¥È¤¬ÆϤ¯¤Þ¤Ç¤ÎÂÔ¤Á»þ´Ö
    3. + +
  3. ¥ì¥¹¥Ý¥ó¥¹¤òÊÖ¤¹ºÝ¡¢TCP ¤Î ACK ¤¬µ¢¤Ã¤Æ¤¯¤ë¤Þ¤Ç¤Î»þ´Ö
    4. +
+ +

¾­Íè¤Ë¤ÏÊÌ¡¹¤ÎÀßÄê¤ò¤¹¤ë¤³¤È¤¬²Äǽ¤Ë¤Ç¤­¤ë¤è¤¦¹ÍθÃæ¤Ç¤¹¡£ + Apache 1.2 °ÊÁ°¤Ï¥¿¥¤¥Þ¡¼¤Ï 1200 ¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤·¤¿¤¬¡¢ + 300 ¤Ë²¼¤²¤é¤ì¤Þ¤·¤¿¡£300 ¤Ç¤â¤Û¤È¤ó¤É¤Î¾ì¹ç¤Ï½½Ê¬¤¹¤®¤ëÃͤǤ¹¡£ + ¥³¡¼¥ÉÃæ¤ÎÊѤʾì½ê¤Ë¤Þ¤À¥Ñ¥±¥Ã¥È¤òÁ÷¤ëºÝ¤Ë¥¿¥¤¥Þ¤ò¥ê¥»¥Ã¥È¤·¤Ê¤¤ + ¾ì½ê¤¬¤¢¤ë¤«¤â¤·¤ì¤Ê¤¤¤Î¤Ç¡¢¥Ç¥Õ¥©¥ë¥È¤ò¤è¤ê¾®¤µ¤¤ÃͤˤϤ·¤Æ¤¤¤Þ¤»¤ó¡£

+ + +
+
top
+

TraceEnable ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:TRACE ¥á¥½¥Ã¥É¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë±þÅúÊýË¡¤ò·è¤á¤ë +
¹½Ê¸:TraceEnable [on|off|extended]
¥Ç¥Õ¥©¥ë¥È:TraceEnable on
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
¸ß´¹À­:Apache 1.3.34, 2.0.55 °Ê¹ß
+

¥³¥¢¥µ¡¼¥Ð¤È mod_proxy ξÊý¤Î TRACE + ¤ÎµóÆ°¤ò¥ª¡¼¥Ð¡¼¥é¥¤¥É¤·¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Î TraceEnable on + ¤Ï¡¢¥ê¥¯¥¨¥¹¥È¥Ü¥Ç¥£¤ò¼õ¤±Æþ¤ì¤Ê¤¤¤è¤¦¤Ê¡¢RFC2616 ¤Ë½àµò¤·¤¿ + TRACE ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤Þ¤¹¡£ + TraceEnale off ¤ÈÀßÄꤹ¤ë¤È¡¢¥³¥¢¥µ¡¼¥Ð¤È + mod_proxy ¤Ï 405 (¥á¥½¥Ã¥ÉÉÔµö²Ä) + ¥¨¥é¡¼¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤·¤Þ¤¹¡£

+ +

ºÇ¸å¤Ë¡¢¥Æ¥¹¥È¤äÄ´ººÌÜŪ¤Ê¤É¤Î¸ÂÄêÍÑÅӤȤ·¤Æ¡¢»ÈÍѤ˽àµò¤·¤Ê¤¤ + TraceEnable extended ¤ò»È¤Ã¤Æ¡¢¥ê¥¯¥¨¥¹¥È¥Ü¥Ç¥£¤ò + ¼õ¤±ÉÕ¤±¤ë¤è¤¦¤ËµóÆ°¤òÊѹ¹¤Ç¤­¤Þ¤¹¡£(¥ª¥ê¥¸¥ó¥µ¡¼¥Ð¤È¤·¤Æ¤Î) + ¥³¥¢¥µ¡¼¥Ð¤Ç¤Ï¡¢¥ê¥¯¥¨¥¹¥È¥Ü¥Ç¥£¤Î¥µ¥¤¥º¤Ï 64k ( + Transfer-Encoding: chunked ¤¬»È¤ï¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï + chunk ¥Ø¥Ã¥ÀÍÑ¤Ë +8k) ¤ËÀ©¸Â¤µ¤ì¤Þ¤¹¡£ + ¥³¥¢¥µ¡¼¥Ð¤Ï¡¢¥Õ¥ë¥Ø¥Ã¥À¤ÈÁ´¤Æ¤Î chunk ¥Ø¥Ã¥À¤ò¥ì¥¹¥Ý¥ó¥¹¤Î + ¥Ü¥Ç¥£¤È¤·¤ÆÊֵѤ·¤Þ¤¹¡£ + proxy ¥µ¡¼¥Ð¤È¤·¤Æ¤Ï¡¢¥ê¥¯¥¨¥¹¥È¥Ü¥Ç¥£¤Î¥µ¥¤¥º¤Ï 64k ¤ËÀ©¸Â¤µ¤ì¤Þ¤»¤ó¡£

+ +
+
top
+

UseCanonicalName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬¼«Ê¬¼«¿È¤Î̾Á°¤È¥Ý¡¼¥È¤ò·èÄꤹ¤ëÊýË¡¤òÀßÄꤹ¤ë
¹½Ê¸:UseCanonicalName On|Off|Dns
¥Ç¥Õ¥©¥ë¥È:UseCanonicalName Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

¿¤¯¤Î¾õ¶·¤Ç Apache ¤Ï¼«¸Ê»²¾È URL¡¢¤¹¤Ê¤ï¤Á + Ʊ¤¸¥µ¡¼¥Ð¤ò»Ø¤¹ URL¡¢¤òºîÀ®¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + UseCanonicalName On ¤Î¾ì¹ç¤Ï¡¢ServerName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤Æ¤¤¤ë + ¥Û¥¹¥È̾¤È¥Ý¡¼¥ÈÈÖ¹æ¤ò»È¤Ã¤Æ¡¢¤½¤ÎÀµµ¬Ì¾ (¼«¸Ê»²¾È¤Î̾Á°) ¤òÀ¸À®¤·¤Þ¤¹¡£ + ¤³¤Î̾Á°¤Ï¡¢¤¹¤Ù¤Æ¤Î¼«¸Ê»²¾È URL ¤Ç»È¤ï¤ì¤Þ¤¹¤·¡¢CGI ¤Î + SERVER_NAME ¤È SERVER_PORT ¤Ç¤â»È¤ï¤ì¤Þ¤¹¡£

+ +

UseCanonicalName Off ¤Î¾ì¹ç¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤¬¥Û¥¹¥È̾¤È¥Ý¡¼¥È¤ò»ØÄꤷ¤¿¤È¤­¤Ë¤Ï¡¢ + ¤½¤ì¤é¤ò¸µ¤Ë¼«¸Ê»²¾È URL ¤òºîÀ®¤·¤Þ¤¹ (»ØÄ꤬¤Ê¤«¤Ã¤¿¤È¤­¤Ï + ¾å¤ÎÄêµÁ¤ÈƱÍͤˤ·¤ÆÀµµ¬Ì¾¤ò²ò·è¤·¤Þ¤¹)¡£ + ¤³¤ì¤é¤ÎÃͤÏ̾Á°¥Ù¡¼¥¹¤Î + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò¼ÂÁõ¤Ç»È¤ï¤ì¤Æ¤¤¤ë¤Î¤ÈƱ¤¸Ãͤǡ¢ + Ʊ¤¸¥¯¥é¥¤¥¢¥ó¥È¤Ç¼èÆÀ¤Ç¤­¤ëÃͤˤʤäƤ¤¤Þ¤¹¡£ + CGI ÊÑ¿ô SERVER_NAME ¤È SERVER_PORT + ¤â¥¯¥é¥¤¥¢¥ó¥È¤«¤éÍ¿¤¨¤é¤ì¤¿Ãͤ«¤éºîÀ®¤µ¤ì¤Þ¤¹¡£

+ +

¤³¤Î¤è¤¦¤ÊµóÆ°¤¬ÊØÍø¤ÊÎã¤Ï¡¢¥¤¥ó¥È¥é¥Í¥Ã¥È¤Î¥µ¡¼¥Ð¤Ç www + ¤Î¤è¤¦¤Êû¤¤Ì¾Á°¤Ç¥æ¡¼¥¶¤¬¥Þ¥·¥ó¤ËÀܳ¤¹¤ë¤È¤­¤Ç¤¹¡£ + ¥æ¡¼¥¶¤ÎÆþÎϤÇû¤¤¥Û¥¹¥È̾¤¬»È¤ï¤ì¤Æ¤¤¤Æ¡¢URL ¤¬ºÇ¸å¤Î¥¹¥é¥Ã¥·¥å̵¤·¤Î + ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤Ê¤Ã¤Æ¤¤¤ë http://www/splat ¤Î¤è¤¦¤Ê¤È¤­¡¢ + Apache ¤Ï¥ê¥¯¥¨¥¹¥È¤ò http://www.domain.com/splat/ + ¤Ø¥ê¥À¥¤¥ì¥¯¥È¤·¤Þ¤¹¡£ + ǧ¾Ú¤ò¤¹¤ë¤è¤¦¤ËÀßÄꤷ¤Æ¤¤¤ë¤È¡¢¤³¤Î¾ì¹ç + ¥æ¡¼¥¶¤Ï 2 ²óǧ¾Ú¤ò¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¯¤Ê¤ê¤Þ¤¹ (www ¤Ë + ÂФ·¤Æ 1 ²ó¡¢www.domain.com ¤ËÂФ·¤Æ¤â¤¦ 1 ²ó -- + ¾ÜºÙ¤Ï ¤³¤ÎÏÃÂê¤Î + FAQ ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤)¡£ + ¤·¤«¤· UseCanonicalName ¤¬ Off ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤È¡¢ + Apache ¤Ï http://www/splat/ ¤Ë¥ê¥À¥¤¥ì¥¯¥È¤·¤Þ¤¹¡£

+ +

»°¤ÄÌܤΥª¥×¥·¥ç¥ó UseCanonicalName DNS ¤Ï¡¢ + Â絬ÌÏ¤Ê IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥Æ¥£¥ó¥°¤Ç¡¢ + Host: ¥Ø¥Ã¥À¤òÄ󶡤·¤Ê¤¤¸Å¤¤¥¯¥é¥¤¥¢¥ó¥È¤ò + ¥µ¥Ý¡¼¥È¤¹¤ë¾ì¹ç¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ç¤Ï Apache ¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬Àܳ¤·¤¿ IP ¥¢¥É¥ì¥¹¤ËÂФ·¤Æ + DNS ¤ÎµÕ°ú¤­¤ò¹Ô¤Ê¤Ã¤Æ¡¢¼«¸Ê»²¾È URL ¤òºîÀ®¤·¤Þ¤¹¡£

+ +

·Ù¹ð

+

CGI ¤¬ SERVER_NAME ¤Ë´Ø¤·¤Æ²¿¤é¤«¤ÎÁ°Äó¾ò·ï¤ò + ²¾Äꤷ¤Æ¤¤¤ë¤È¤­¤Ë¤Ï¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤ÎÀßÄê¤Ë¤è¤Ã¤Æ¤ÏÆ°ºî¤·¤Ê¤¯ + ¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¥¯¥é¥¤¥¢¥ó¥È¤Ï¼Â¼ÁŪ¤Ë¤Ï¥Û¥¹¥È̾¤È¤·¤Æ + ²¿¤Ç¤â˾¤ß¤ÎÃͤò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£CGI ¤¬ + SERVER_NAME ¤ò»È¤Ã¤Æ¼«¸Ê»²¾È URL ¤òºîÀ®¤¹¤ë¤³¤È¤·¤«¤·¤Ê¤¤ + ¾ì¹ç¤Ï¡¢¤É¤ÎÀßÄê¤ò¹Ô¤Ê¤Ã¤Æ¤âÂç¾æÉפʤϤº¤Ç¤¹¡£

+ +

»²¾È

+ +
+
top
+

UseCanonicalPhysicalPort ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤Î̾Á°¤È¥Ý¡¼¥È¤Î²ò·èÊýË¡¤òÀßÄꤹ¤ë
¹½Ê¸:UseCanonicalPhysicalPort On|Off
¥Ç¥Õ¥©¥ë¥È:UseCanonicalPhysicalPort Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

Apache ¤ÏÍÍ¡¹¤Ê¾õ¶·¤Ç ¼«¸Ê»²¾È URL ¤Ä¤Þ¤ê¥µ¡¼¥Ð¤¬¼«Ê¬¼«¿È¤ò»Ø¤·¼¨¤¹ + URL ¤òÀ¸À®¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + UseCanonicalName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ÀßÄê¤Ë¤è¤Ã¤Æ¥µ¡¼¥Ð¤ÎÊÌ̾¤ò¹½À®¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢ + ¤½¤ÎºÝ¤ÎÊÌ̾¤Ë»È¤¦¥Ý¡¼¥È¤Ï + UseCanonicalPhysicalPort On ¤È¤¤¤¦ÀßÄ꤬¤¢¤ì¤Ð¡¢ + ¼ÂºÝ¤Î¥Ý¡¼¥ÈÈÖ¹æ¤ò¥Ý¡¼¥ÈÈÖ¹æ¤È¤·¤Æ»È¤¦¸õÊä¤ËÆþ¤ì¤Æ¥ê¥¯¥¨¥¹¥È¤ò + ½èÍý¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£UseCanonicalPhysicalPort Off + ¤È¤¤¤¦ÀßÄê¤Ç¤¢¤ì¤Ð¡¢¼ÂºÝ¤Î¥Ý¡¼¥ÈÈÖ¹æ¤Ï»ÈÍѤ»¤º¡¢ÀßÄꤵ¤ì¤Æ¤¤¤ë¾ðÊó¤ò + Á´¤Æ¿®¤¸¤Æ¥Ý¡¼¥ÈÈÖ¹æ¤ò¹½À®¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Ãí

+

¼ÂºÝ¤Î¥Ý¡¼¥ÈÈֹ椬»È¤ï¤ì¤ë½ç½ø¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹ :

+ UseCanonicalName On

+
    +
  • ServerName ¤Ç»ØÄꤵ¤ì¤Æ¤¤¤ë¥Ý¡¼¥ÈÈÖ¹æ
    • +
  • ¼ÂºÝ¤Î¥Ý¡¼¥ÈÈÖ¹æ
    • +
  • ¥Ç¥Õ¥©¥ë¥È¤Î¥Ý¡¼¥ÈÈÖ¹æ
    • +
+ UseCanonicalName Off | DNS +
    +
  • Host: ¥Ø¥Ã¥À¤«¤éÃê½Ð¤µ¤ì¤¿¥Ý¡¼¥ÈÈÖ¹æ
    • +
  • ¼ÂºÝ¤Î¥Ý¡¼¥ÈÈÖ¹æ
    • +
  • ServerName ¤Ç»ØÄꤵ¤ì¤Æ¤¤¤ë¥Ý¡¼¥ÈÈÖ¹æ
    • +
  • ¥Ç¥Õ¥©¥ë¥È¤Î¥Ý¡¼¥ÈÈÖ¹æ
    • +
+ +

UseCanonicalPhysicalPort Off ¤Ç¡¢ + ¼ÂºÝ¤Î¥Ý¡¼¥ÈÈֹ椬¾å¤Î½ç½ø¤«¤é¼è¤ê½ü¤«¤ì¤Þ¤¹¡£

+
+ + +

»²¾È

+ +
+
top
+

<VirtualHost> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:ÆÃÄê¤Î¥Û¥¹¥È̾¤ä IP ¥¢¥É¥ì¥¹¤Î¤ß¤ËŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò +°Ï¤à
¹½Ê¸:<VirtualHost + addr[:port] [addr[:port]] + ...> ... </VirtualHost>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Core
¥â¥¸¥å¡¼¥ë:core
+

<VirtualHost> µÚ¤Ó + </VirtualHost> ¤Ï¡¢ + ÆÃÄê¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËÂФ·¤Æ¤Î¤ßŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö·²¤ò³ç¤ë + ¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¥³¥ó¥Æ¥­¥¹¥È¤Çµö²Ä¤µ¤ì¤ëÁ´¤Æ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ØÄê²Äǽ¤Ç¤¹¡£ + ¥µ¡¼¥Ð¤¬¡¢»ØÄꤵ¤ì¤¿¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¤¢¤ë¥É¥­¥å¥á¥ó¥È¤Ø¤Î + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤¿¾ì¹ç¡¢ + <VirtualHost> ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤Ë¤¢¤ë + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Å¬ÍѤµ¤ì¤Þ¤¹¡£ + Addr¤Ï¡¢¼¡¤Î¤â¤Î¤¬ÍøÍѤǤ­¤Þ¤¹:

+ +
    +
  • ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î IP ¥¢¥É¥ì¥¹
    • + +
  • ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î IP ¤ËÂбþ¤¹¤ë´°Á´¤Ê¥É¥á¥¤¥ó̾
    • + +
  • NameVirtualHost * ¤È¶¦¤Ë»È¤ï¤ì¤ë¡¢ + ¤¹¤Ù¤Æ¤Î IP ¥¢¥É¥ì¥¹¤Ë¥Þ¥Ã¥Á¤¹¤ëʸ»ú *
    • + +
  • IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ç¾¤Î¤â¤Î¤Ë¥Þ¥Ã¥Á¤·¤Ê¤¤ IP ¥¢¥É¥ì¥¹ + ¤Î¤¿¤á¤Îʸ»úÎó _default_
    • +
+ +

Îã

+ <VirtualHost 10.1.2.3>
+ + ServerAdmin webmaster@host.foo.com
+ DocumentRoot /www/docs/host.foo.com
+ ServerName host.foo.com
+ ErrorLog logs/host.foo.com-error_log
+ TransferLog logs/host.foo.com-access_log
+ + </VirtualHost> +

+ +

IPv6 ¥¢¥É¥ì¥¹¤Ï¥ª¥×¥·¥ç¥ó¤Î¥Ý¡¼¥ÈÈÖ¹æ¤Î»ØÄê¤È¶èÊ̤¹¤ë¤¿¤á¤Ë¡¢ + ³Ñ³ç¸Ì¤Ç³ç¤Ã¤Æ»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¼¡¤Ï IPv6 ¤ÎÎã¤Ç¤¹:

+ +

+ <VirtualHost [2001:db8::a00:20ff:fea7:ccea]>
+ + ServerAdmin webmaster@host.example.com
+ DocumentRoot /www/docs/host.example.com
+ ServerName host.example.com
+ ErrorLog logs/host.example.com-error_log
+ TransferLog logs/host.example.com-access_log
+ + </VirtualHost> +

+ +

³Æ¡¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¤Ï¤½¤ì¤¾¤ì°ã¤¦ IP ¥¢¥É¥ì¥¹¡¢¥Ý¡¼¥ÈÈÖ¹æ + ¤â¤·¤¯¤Ï¥Û¥¹¥È̾¤ËÂбþ¤¹¤ëɬÍפ¬¤¢¤ê¡¢ + 1 ÈÖÌܤξì¹ç¤Ë¤ÏÊ£¿ô¤Î¥¢¥É¥ì¥¹¤Ç IP ¥Ñ¥±¥Ã¥È¤ò¼õ¿®¤Ç¤­¤ë¤è¤¦¤Ë + ¥µ¡¼¥Ð¥Þ¥·¥ó¤òÀßÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + (¤â¤·¡¢¥Þ¥·¥ó¤¬Ê£¿ô¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤È»ý¤¿¤Ê¤¤¾ì¹ç¤Ï¡¢ + (OS¤¬¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ì¤Ð) ifconfig alias ¥³¥Þ¥ó¥É¤Ë¤è¤ê + ãÀ®¤Ç¤­¤Þ¤¹)¡£

+ +

Ãí°ÕÅÀ

+

<VirtualHost> ¤Ï Apache ¤¬ Listen ¤¹¤ë + IP ¥¢¥É¥ì¥¹¤Ë¤Ï±Æ¶Á¤òÍ¿¤¨¤Þ¤»¤ó¡£ + Listen ¤ò + »È¤Ã¤Æ Apache ¤¬Àµ¤·¤¤¥¢¥É¥ì¥¹¤ò listen ¤¹¤ë¤è¤¦¤ËÀßÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+
+ +

IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ÆÃÊ̤Ê̾Á° + _default_ ¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤½¤Î¾ì¹ç¤Ï + ¤½¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ï¾¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÇÌÀ¼¨Åª¤Ëµó¤²¤é¤ì¤Æ¤¤¤Ê¤¤ + ¤¹¤Ù¤Æ¤Î IP ¥¢¥É¥ì¥¹¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£_default_ ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬Ìµ¤¤ + ¾ì¹ç¤Ë IP ¤¬¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ç»ØÄꤵ¤ì¤¿¤â¤Î¤Ë¥Þ¥Ã¥Á¤·¤Ê¤¤¤È¤­¤Ï¡¢ + VirtualHost ¥»¥¯¥·¥ç¥ó¤Î³°¤Î¤¹¤Ù¤Æ¤ÎÄêµÁ¤«¤é¤Ê¤ë¡Ö¼ç¡×¥µ¡¼¥ÐÀßÄ꤬ + »È¤ï¤ì¤Þ¤¹¡£(¤¿¤À¤·¡¢NameVirtualHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¥Þ¥Ã¥Á¤¹¤ë + ¤¹¤Ù¤Æ¤Î IP ¥¢¥É¥ì¥¹¤Ï¡Ö¼ç¡×¥µ¡¼¥ÐÀßÄê¤â _default_ ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤â + »È¤ï¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¾Ü¤·¤¯¤Ï ¥Í¡¼¥à¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È ¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£)

+ +

:port ¤È¤¤¤Ã¤¿·Á¼°¤Çµ­½Ò¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢ + ¥Þ¥Ã¥Á¤µ¤»¤ë¥Ý¡¼¥È¤òÊѹ¹²Äǽ¤Ç¤¹¡£ + ¤³¤Î»ØÄê¤ò¤·¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢¼ç¥µ¡¼¥ÐÀßÄê¤Ë¤ª¤±¤ë + °ìÈֺǸå¤Ë Port ¤Ç»ØÄꤵ¤ì¤¿¥Ý¡¼¥È¤¬ + ¥Ç¥Õ¥©¥ë¥È¤È¤Ê¤ê¤Þ¤¹¡£ + :* ¤ò»ØÄꤹ¤ë¤³¤È¤Ë¤è¤ê¡¢ + ¥¢¥É¥ì¥¹¾å¤ÎÁ´¤Æ¤Î¥Ý¡¼¥È¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£(_default_ ¤Î¤È¤­¤Ï + ¤³¤ì¤ò»È¤¦¤³¤È¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£)

+ +

¥»¥­¥å¥ê¥Æ¥£

+

¥µ¡¼¥Ð¡¼¤òµ¯Æ°¤·¤¿°Ê³°¤Î¥æ¡¼¥¶¤¬¥í¥°¥Õ¥¡¥¤¥ë¤¬Êݴɤµ¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ë + ½ñ¤­¹þ¤ß²Äǽ¤Ê¤È¤­¤Ë¤Ê¤¼¥»¥­¥å¥ê¥Æ¥£¤¬Çˤé¤ì¤ë²ÄǽÀ­¤¬¤¢¤ë¤«¤Î¾ÜºÙ¤Ï + ¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤¹¤ë¥³¥Ä ¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

»²¾È

+ +
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directive-dict.html b/docs/manual/mod/directive-dict.html new file mode 100644 index 00000000..1ed62d36 --- /dev/null +++ b/docs/manual/mod/directive-dict.html @@ -0,0 +1,11 @@ +URI: directive-dict.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: directive-dict.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: directive-dict.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/directive-dict.html.en b/docs/manual/mod/directive-dict.html.en new file mode 100644 index 00000000..2350e1cb --- /dev/null +++ b/docs/manual/mod/directive-dict.html.en @@ -0,0 +1,291 @@ + + + +Terms Used to Describe Directives - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Terms Used to Describe Directives

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

This document describes the terms that are used to describe + each Apache configuration + directive.

+
+ +
top
+
+

Description

+ +

A brief description of the purpose of the directive.

+
top
+
+

Syntax

+ +

This indicates the format of the directive as it would + appear in a configuration file. This syntax is extremely + directive-specific, and is described in detail in the + directive's definition. Generally, the directive name is + followed by a series of one or more space-separated arguments. + If an argument contains a space, the argument must be enclosed + in double quotes. Optional arguments are enclosed in square + brackets. Where an argument can take on more than one possible + value, the possible values are separated by vertical bars "|". + Literal text is presented in the default font, while + argument-types for which substitution is necessary are + emphasized. Directives which can take a variable + number of arguments will end in "..." indicating that the last + argument is repeated.

+ +

Directives use a great number of different argument types. A + few common ones are defined below.

+ +
+
URL
+ +
A complete Uniform Resource Locator including a scheme, + hostname, and optional pathname as in + http://www.example.com/path/to/file.html
+ +
URL-path
+ +
The part of a url which follows the scheme and + hostname as in /path/to/file.html. The + url-path represents a web-view of a resource, as + opposed to a file-system view.
+ +
file-path
+ +
The path to a file in the local file-system beginning + with the root directory as in + /usr/local/apache/htdocs/path/to/file.html. + Unless otherwise specified, a file-path which does + not begin with a slash will be treated as relative to the ServerRoot.
+ +
directory-path
+ +
The path to a directory in the local file-system + beginning with the root directory as in + /usr/local/apache/htdocs/path/to/.
+ +
filename
+ +
The name of a file with no accompanying path information + as in file.html.
+ +
regex
+ +
A Perl-compatible regular + expression. The directive definition will specify what the + regex is matching against.
+ +
extension
+ +
In general, this is the part of the filename + which follows the last dot. However, Apache recognizes + multiple filename extensions, so if a filename + contains more than one dot, each dot-separated part of the + filename following the first dot is an extension. + For example, the filename file.html.en + contains two extensions: .html and + .en. For Apache directives, you may specify + extensions with or without the leading dot. In + addition, extensions are not case sensitive.
+ +
MIME-type
+ +
A method of describing the format of a file which + consists of a major format type and a minor format type, + separated by a slash as in text/html.
+ +
env-variable
+ +
The name of an environment + variable defined in the Apache configuration process. + Note this is not necessarily the same as an operating system + environment variable. See the environment variable documentation for + more details.
+
+
top
+
+

Default

+ +

If the directive has a default value (i.e., if you + omit it from your configuration entirely, the Apache Web server + will behave as though you set it to a particular value), it is + described here. If there is no default value, this section + should say "None". Note that the default listed here + is not necessarily the same as the value the directive takes in + the default httpd.conf distributed with the server.

+
top
+
+

Context

+ +

This indicates where in the server's configuration files the + directive is legal. It's a comma-separated list of one or more + of the following values:

+ +
+
server config
+ +
This means that the directive may be used in the server + configuration files (e.g., httpd.conf), but + not within any + <VirtualHost> + or <Directory> + containers. It is not allowed in .htaccess files + at all.
+ +
virtual host
+ +
This context means that the directive may appear inside + <VirtualHost> + containers in the server + configuration files.
+ +
directory
+ +
A directive marked as being valid in this context may be + used inside <Directory>, <Location>, <Files>, and <Proxy> containers + in the server configuration files, subject to the restrictions + outlined in Configuration + Sections.
+ +
.htaccess
+ +
If a directive is valid in this context, it means that it + can appear inside per-directory + .htaccess files. It may not be processed, though + depending upon the overrides currently active.
+
+ +

The directive is only allowed within the designated + context; if you try to use it elsewhere, you'll get a + configuration error that will either prevent the server from + handling requests in that context correctly, or will keep the + server from operating at all -- i.e., the server won't + even start.

+ +

The valid locations for the directive are actually the + result of a Boolean OR of all of the listed contexts. In other + words, a directive that is marked as being valid in + "server config, .htaccess" can be used in the + httpd.conf file and in .htaccess + files, but not within any <Directory> or + <VirtualHost> + containers.

+
top
+
+

Override

+ +

This directive attribute indicates which configuration + override must be active in order for the directive to be + processed when it appears in a .htaccess file. If + the directive's context + doesn't permit it to appear in .htaccess files, + then no context will be listed.

+ +

Overrides are activated by the AllowOverride directive, and apply + to a particular scope (such as a directory) and all + descendants, unless further modified by other + AllowOverride directives at + lower levels. The documentation for that directive also lists the + possible override names available.

+
top
+
+

Status

+ +

This indicates how tightly bound into the Apache Web server + the directive is; in other words, you may need to recompile the + server with an enhanced set of modules in order to gain access + to the directive and its functionality. Possible values for + this attribute are:

+ +
+
Core
+ +
If a directive is listed as having "Core" status, that + means it is part of the innermost portions of the Apache Web + server, and is always available.
+ +
MPM
+ +
A directive labeled as having "MPM" status is provided by + a Multi-Processing Module. This + type of directive will be available if and only if you are + using one of the MPMs listed on the Module line of the directive + definition.
+ +
Base
+ +
A directive labeled as having "Base" status is supported + by one of the standard Apache modules which is compiled into + the server by default, and is therefore normally available + unless you've taken steps to remove the module from your + configuration.
+ +
Extension
+ +
A directive with "Extension" status is provided by one of + the modules included with the Apache server kit, but the + module isn't normally compiled into the server. To enable the + directive and its functionality, you will need to change the + server build configuration files and re-compile Apache.
+ +
Experimental
+ +
"Experimental" status indicates that the directive is + available as part of the Apache kit, but you're on your own + if you try to use it. The directive is being documented for + completeness, and is not necessarily supported. The module + which provides the directive may or may not be compiled in by + default; check the top of the page which describes the + directive and its module to see if it remarks on the + availability.
+
+
top
+
+

Module

+ +

This quite simply lists the name of the source module which + defines the directive.

+
top
+
+

Compatibility

+ +

If the directive wasn't part of the original Apache version + 2 distribution, the version in which it was introduced should + be listed here. In addition, if the directive is available + only on certain platforms, it will be noted here.

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directive-dict.html.ja.euc-jp b/docs/manual/mod/directive-dict.html.ja.euc-jp new file mode 100644 index 00000000..5253211d --- /dev/null +++ b/docs/manual/mod/directive-dict.html.ja.euc-jp @@ -0,0 +1,303 @@ + + + +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î²òÀâ¤Ë»È¤ï¤ì¤ëÍѸì - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î²òÀâ¤Ë»È¤ï¤ì¤ëÍѸì

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +

¤³¤Îʸ½ñ¤Ï³Æ Apache ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤òÀâÌÀ¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Æ¤¤¤ëÍѸì¤òÀâÌÀ¤·¤Þ¤¹¡£

+
+ +
top
+
+

ÀâÌÀ

+ +

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÌÜŪ¤Î´Êñ¤ÊÀâÌÀ¡£

+
top
+
+

¹½Ê¸

+ +

ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î½ñ¼°¤ò¼¨¤·¤Þ¤¹¡£ + ¤³¤Î¹½Ê¸¤Ï¥Ç¥£¥ì¥¯¥Æ¥£¥ÖÆÃÍ­¤Ê¤Î¤Ç¡¢¾ÜºÙ¤Ï¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀâÌÀ¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£°ìÈÌŪ¤Ë¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö̾¤Î¸å¤Ë¤Ï + ¶õÇò¤Ë¤è¤êʬ³ä¤µ¤ì¤¿¤¤¤¯¤Ä¤«¤Î°ú¿ô¤¬Â³¤­¤Þ¤¹¡£ + °ú¿ô¤¬¶õÇò¤ò´Þ¤à¤È¤­¤ÏÆó½Å°úÍÑÉä (ÌõÃí: ") + ¤Ç°Ï¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ ¥ª¥×¥·¥ç¥Ê¥ë¤Ê°ú¿ô¤Ï³ç¸Ì + (ÌõÃí: []) ¤Ç°Ï¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ + °ú¿ô¤¬Ê£¿ô¤ÎÃͤò¼è¤êÆÀ¤ë¾ì¹ç¤Ï¡¢¤½¤ì¤é¤ÎÃͤϿ⾤ÎËÀ "|" + ¤Ç ʬ³ä¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + Êѹ¹¤µ¤ì¤Ê¤¤¥Æ¥­¥¹¥È¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¥Õ¥©¥ó¥È¤Çɽ¼¨¤µ¤ì¡¢ÃÖ´¹¤ÎɬÍ×¤Ê + °ú¿ô¤Ï¶¯Ä´¤µ¤ì¤Æɽ¼¨¤µ¤ì¤Þ¤¹¡£ + °ú¿ô¤Î¿ô¤¬ÊѤï¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏºÇ¸å¤Î + °ú¿ô¤¬·«¤êÊÖ¤µ¤ì¤ë¤³¤È¤ò¼¨¤¹¤¿¤á¤Ë "..." + ¤Ç½ª¤ï¤ê¤Þ¤¹¡£

+ +

+ ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¿¤¯¤Î°ã¤¦·¿¤Î°ú¿ô¤ò¤È¤ê¤Þ¤¹¡£¤¤¤¯¤Ä¤«¡¢Îɤ¯ + »È¤ï¤ì¤ë¤â¤Î¤ò°Ê²¼¤ÇÄêµÁ¤·¤Þ¤¹¡£

+ +
+
URL
+ +
http://www.example.com/path/to/file.html + ¤Î¤è¤¦¤Ë¡¢ + ¥¹¥­¡¼¥à¡¢¥Û¥¹¥È̾¡¢¥Ñ¥¹Ì¾(¾Êά²Äǽ)¤ò´Þ¤ó¤Ç¤¤¤ë´°Á´¤Ê + Uniform Resource Locator¡£
+ +
URL-path
+ +
/path/to/file.html ¤Î¤è¤¦¤Ë¡¢¥¹¥­¡¼¥à¤È + ¥Û¥¹¥È̾¤Î¸å¤Ë³¤¯ url + ¤Î°ìÉô¡£url-path ¤Ï + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤«¤é¤Î»ëÅÀ¤Ç¤Ï¤Ê¤¯¡¢ + ¥¦¥§¥Ö¤«¤é¤Î»ëÅÀ¤Ç¥ê¥½¡¼¥¹¤òɽ¸½¤·¤Þ¤¹¡£
+ +
file-path
+ +
/usr/local/apache/htdocs/path/to/file.html + ¤Î¤è¤¦¤Ë¡¢ + ¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê¤«¤é»Ï¤Þ¤ë¥í¡¼¥«¥ë¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î¥Ñ¥¹¡£ + Ä̾¥¹¥é¥Ã¥·¥å¤Ç»Ï¤Þ¤é¤Ê¤¤ file-path ¤Ï ServerRoot + ¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ °·¤ï¤ì¤Þ¤¹¡£
+ +
directory-path
+ +
/usr/local/apache/htdocs/path/to/ + ¤Î¤è¤¦¤Ë¡¢ + ¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê¤«¤é»Ï¤Þ¤ë¥í¡¼¥«¥ë¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î + ¥Ñ¥¹¡£
+ +
filename
+ +
file.html ¤Î¤è¤¦¤Ë¡¢¥Ñ¥¹¾ðÊó¤ÎÉÕ¤¤¤Æ¤¤¤Ê¤¤ + ¥Õ¥¡¥¤¥ë̾¡£
+ +
regex
+ +
Perl ¸ß´¹¤ÎÀµµ¬É½¸½¤Ç¤¹¡£ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÄêµÁ¤¬ regex + ¤¬²¿¤ËÂФ·¤Æ¥Þ¥Ã¥Á¤ò¹Ô¤Ê¤¦¤Î¤«¤ò»ØÄꤷ¤Þ¤¹¡£
+ +
extension
+ +
°ìÈÌŪ¤Ë¤Ï filename + ¤ÎºÇ¸å¤Î¥É¥Ã¥È¤Î¸å¤ÎÉôʬ¤Ç¤¹¡£ ¤·¤«¤·¡¢Apache + ¤ÏÊ£¿ô¤Î¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤òǧ¼±¤·¤Þ¤¹¤Î¤Ç¡¢filename + ¤ËÊ£¿ô¤Î¥É¥Ã¥È¤¬¤¢¤ë¤È¡¢ºÇ½é¤Î¥É¥Ã¥È¤Î¸å¤Î¡¢¤½¤ì¤¾¤ì¤Î¥É¥Ã¥È¤ÇʬΥ¤µ¤ì¤¿Éôʬ¤¬ + extension (ÌõÃí: ³ÈÄ¥»Ò) + ¤Ë¤Ê¤ê¤Þ¤¹¡£Î㤨¤Ð¡¢filename + file.html.en + ¤Ë¤ÏÆó¤Ä¤Î³ÈÄ¥»Ò¤¬¤¢¤ê¤Þ¤¹¡£.html ¤È + .en ¤Ç¤¹¡£Apache + ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï¡¢extension + ¤Ï¥É¥Ã¥ÈÉÕ¤­¤Ç¤â̵¤·¤Ç¤â»ØÄê¤Ç¤­¤Þ¤¹¡£¤µ¤é¤Ë¡¢extension + ¤Ï Âçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£
+ +
MIME-type
+ +
text/html ¤Î¤è¤¦¤Ë¡¢¥¹¥é¥Ã¥·¥å¤ÇʬΥ¤µ¤ì¤¿ + ¼ç¥Õ¥©¡¼¥Þ¥Ã¥È¤ÈÉû¥Õ¥©¡¼¥Þ¥Ã¥È¤Ë¤è¤Ã¤Æ¥Õ¥¡¥¤¥ë¤Î·Á¼°¤ò + ɽ¤¹ÊýË¡¤Ç¤¹¡£
+ +
env-variable
+ +
Apache ¤ÎÀßÄê¤Ë¤è¤êÄêµÁ¤µ¤ì¤ë ´Ä¶­ÊÑ¿ô¤Î̾Á°¤Ç¤¹¡£¤³¤ì¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î + ´Ä¶­ÊÑ¿ô¤ÈƱ¤¸¤È¤Ï¸Â¤é¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¾ÜºÙ¤Ï ´Ä¶­ÊÑ¿ô¤ÎÀâÌÀ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
+
+
top
+
+

¥Ç¥Õ¥©¥ë¥È

+ +

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¥Ç¥Õ¥©¥ë¥ÈÃÍ + (¤¹¤Ê¤ï¤Á¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤«¤é + ¾Êά¤µ¤ì¤Æ¤¤¤Æ¤â¡¢Apache + ¥¦¥§¥Ö¥µ¡¼¥Ð¤ÏÆÃÄê¤ÎÃͤËÀßÄꤵ¤ì¤Æ¤¤¤ë¤«¤Î¤è¤¦¤Ë + Æ°ºî¤·¤Þ¤¹) ¤¬¤¢¤ë¾ì¹ç¤Ï¤³¤³¤Ëµ­½Ò¤µ¤ì¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥ÈÃͤÎ̵¤¤¾ì¹ç¡¢¤³¤³¤Ï "None" ¤È + ½ñ¤«¤ì¤Þ¤¹¡£¤³¤³¤Ç½ñ¤«¤ì¤Æ¤¤¤ë¥Ç¥Õ¥©¥ë¥È¤Ï¥µ¡¼¥Ð¤È¶¦¤ËÇÛÉÛ¤µ¤ì¤Æ¤¤¤ë + ¥Ç¥Õ¥©¥ë¥È¤Î httpd.conf + Æâ¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃÍ¤È + °ã¤¦²ÄǽÀ­¤¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

¥³¥ó¥Æ¥­¥¹¥È

+ +

+ ¤³¤ì¤Ï¡¢¥µ¡¼¥Ð¤ÎÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î¤É¤³¤Ç¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Í­¸ú¤Ê¤Î¤«¤ò¼¨¤·¤Þ¤¹¡£ + ¼¡¤Ë¼¨¤¹Ãͤ¬°ì¤Ä°Ê¾å¥«¥ó¥Þ¶èÀÚ¤ê¤ÇÎóµó¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +
+
¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
+ +
¤³¤ì¤Ï¡¢¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë + (Î㤨¤Ð¡¢httpd.conf, + srm.conf, access.conf) + Æâ¤Ç¤Ï»ÈÍѤǤ­¤Þ¤¹¤¬¡¢ + <VirtualHost> ¤ä + <Directory> ¤ÎÃæ¤Ç¤Ï + »ÈÍѤǤ­¤Ê¤¤¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ + .htaccess¥Õ¥¡¥¤¥ë¤Ç¤Î»ÈÍѤϵö²Ä¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£
+ +
¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
+ +
¤³¤ì¤Ï¡¢¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤Î + <VirtualHost> + ¤ÎÃæ¤Ç»ÈÍѤǤ­¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
+ +
¥Ç¥£¥ì¥¯¥È¥ê
+ +
¤³¤ì¤Ï¡¢¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤Î + <Directory>, + <Location>, + <Files>, + <Proxy> + ¥³¥ó¥Æ¥Ê¤ÎÃæ¤Ç¡¢ ÀßÄꥻ¥¯¥·¥ç¥ó + ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ëÀ©¸Â¤Î²¼¤Ç»ÈÍѤǤ­¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
+ +
.htaccess
+ +
¤³¤ì¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥êËè¤Î + .htaccess ¥Õ¥¡¥¤¥ëÆâ¤Ç + »ÈÍѲÄǽ¤Ç¤¢¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ ¤¿¤À¡¢¾å½ñ¤­ + ¤ÎÀßÄê¤Ë¤è¤Ã¤Æ¤Ï¡¢½èÍý¤µ¤ì¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
+
+ +

+ ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï»Ø¼¨¤µ¤ì¤¿¥³¥ó¥Æ¥­¥¹¥È¤Ç¤Î¤ßµö²Ä¤µ¤ì¤Þ¤¹¡£ + ¾¤Î¾ì½ê¤Ç»È¤ª¤¦¤È¤¹¤ë¤È¡¢¥µ¡¼¥Ð¤¬¤½¤Î¥³¥ó¥Æ¥­¥¹¥È¤òÀµ¤·¤¯°·¤¨¤Ê¤¯ + ¤Ê¤ë¤è¤¦¤ÊÀßÄꥨ¥é¡¼¤¬È¯À¸¤¹¤ë¤«¡¢¥µ¡¼¥Ð¤¬¤Þ¤Ã¤¿¤¯Æ°ºî¤·¤Ê¤¯¤Ê¤ë¡¢ + ¤¹¤Ê¤ï¤Á¡¢¥µ¡¼¥Ð¤¬µ¯Æ°¤·¤Ê¤¯¤Ê¤ë¤È¤¤¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

+ ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÍ­¸ú¤Ê°ÌÃ֤ϡ¢¼ÂºÝ¤Ïµó¤²¤é¤ì¤Æ¤¤¤ë¥³¥ó¥Æ¥­¥¹¥È¤Î + ÏÀÍýÏ (ÌõÃí: Boolen OR) + ¤Ë¤Ê¤ê¤Þ¤¹¡£¸À¤¤´¹¤¨¤ë¤È¡¢ + "¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¡¢.htaccess" ¤ÇÍ­¸ú¤À¤È + µ­¤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï httpd.conf + ¥Õ¥¡¥¤¥ë¤È .htaccess + ¥Õ¥¡¥¤¥ë¤È¤ÇÍ­¸ú¤Ç¤¹¤¬¡¢ <Directory> + ¤ä <VirtualHost> + ¤ÎÃæ¤Ç¤Ï»ÈÍѤǤ­¤Þ¤»¤ó¡£

+
top
+
+

¾å½ñ¤­

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°À­¤Ï¡¢.htaccess + ¥Õ¥¡¥¤¥ëÃæ¤Ë + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¸½¤ì¤¿¤È¤­¤Ë¡¢¤½¤ì¤Î½èÍý¤òÍ­¸ú¤Ë¤¹¤ë¤¿¤á¤Ë + ¤É¤ÎÀßÄê¤Î¾å½ñ¤­¤¬É¬Íפ«¤ò¼¨¤·¤Þ¤¹¡£ ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ¥³¥ó¥Æ¥­¥¹¥È + ¤¬¡¢.htaccess + ¥Õ¥¡¥¤¥ëÃæ¤Ç¤Ïµö²Ä¤·¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ï¡¢ ¤³¤Î°À­¤Ï + "ŬÍÑÉÔ²Ä" ¤È½ñ¤«¤ì¤Þ¤¹¡£

+ +

¾å½ñ¤­¤Ï¡¢AllowOverride + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤ÆÍ­¸ú¤Ë¤µ¤ì¡¢ + ÆÃÄê¤Î¥¹¥³¡¼¥×(¥Ç¥£¥ì¥¯¥È¥ê¤Ê¤É)¤È¡¢ + ¤µ¤é¤Ë²¼°Ì¤Î¥ì¥Ù¥ë¤Î AllowOverride + ¤Ç½¤Àµ¤µ¤ì¤Ê¤¤¸Â¤ê¡¢ ¤½¤ÎÇÛ²¼¤ËÂФ·¤ÆŬÍѤµ¤ì¤Þ¤¹¡£ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥É¥­¥å¥á¥ó¥È¤Ï¼è¤êÆÀ¤ë¾å½ñ¤­¤Î̾Á°¤âµó¤²¤Þ¤¹¡£

+
top
+
+

¥¹¥Æ¡¼¥¿¥¹

+ +

¤³¤ì¤Ï¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ Apache + ¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë¤É¤ì¤¯¤é¤¤¤­¤Ä¤¯ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤«¤ò + ¼¨¤·¤Þ¤¹¡£¸À¤¤´¹¤¨¤ì¤Ð¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤½¤Îµ¡Ç½¤òÍøÍѤ¹¤ë¤¿¤á¤Ë¡¢ + ¥â¥¸¥å¡¼¥ë¤Î¿ô¤òÁý¤ä¤·¤Æ¡¢¥µ¡¼¥Ð¤òºÆ¥³¥ó¥Ñ¥¤¥ë¤¹¤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Ê¤¤ + ¤È¤¤¤¦¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ + ¤³¤Î°À­¤¬¼è¤êÆÀ¤ëÃͤϰʲ¼¤Î¤â¤Î¤Ç¤¹:

+ +
+
Core
+ +
"Core" ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache + ¥¦¥§¥Ö¥µ¡¼¥Ð¤Î´ðËܤȤʤë¤Ù¤­¤â¤Î¤Ç¤¢¤ê¡¢ + ¾ï¤Ë»ÈÍѲÄǽ¤Ç¤¢¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
+ +
MPM
+ +
"MPM" ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë¤ÇÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¼ïÎà¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÄêµÁ¤Î¥â¥¸¥å¡¼¥ë¤Î¹Ô¤Ë»È¤Ã¤Æ¤¤¤ë¥â¥¸¥å¡¼¥ë¤Î̾Á°¤¬½ñ¤«¤ì¤Æ¤¤¤ë + ¾ì¹ç¤Ë¤Î¤ß»ÈÍѲÄǽ¤Ç¤¹¡£
+ +
Base
+ +
"Base" ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥Ç¥Õ¥©¥ë¥È¤Ç¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ëɸ½à¥â¥¸¥å¡¼¥ë¤ÎÃæ¤Î°ì¤Ä¤Ç¥µ + ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Æ¡¢¤ï¤¶¤ï¤¶ÀßÄ꤫¤é¥â¥¸¥å¡¼¥ë¤òºï½ü¤·¤¿¤È¤­¤ò½ü¤¤¤Æ¡¢ + Ä̾ï¤Ç¤Ï»ÈÍѲÄǽ¤Ç¤¢¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£
+ +
Extension
+ +
"Extension" ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ Apache + ¥µ¡¼¥Ð¤ÎÇÛÉÛʪ¤ËƱº­¤µ¤ì¤Æ¤¤¤ë¥â¥¸¥å¡¼¥ë¤Î°ì¤Ä¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë¤â¤Î¤Î¡¢ + Ä̾ï¤Ç¤Ï¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Ê¤¤¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤½¤Îµ¡Ç½¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢¥µ¡¼¥Ð¥Ó¥ë¥ÉÍѤÎÀßÄê¥Õ¥¡¥¤¥ë¤ò + Êѹ¹¤·¤Æ Apache + ¤òºÆ¥³¥ó¥Ñ¥¤¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
+ +
Experimental
+ +
"Experimental" ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Apache + ÇÛÉÛʪ¤Ë + Ʊº­¤µ¤ì¤Æ¤¤¤ë¤â¤Î¤Î¡¢»î¤·¤¿¤¤¾ì¹ç¤Ï¼«¸ÊÀÕǤ¤Ç¹Ô¤Ê¤¦ + ɬÍפ¬¤¢¤ë¤È¤¤¤¦¤³¤È¤ò¼¨¤·¤Þ¤¹¡£¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¤¹¤Ù¤Æ¤Î¥É¥­¥å¥á¥ó¥È¤ò + ´°Á´¤Ë¤½¤í¤ï¤»¤ë¤¿¤á¤Ë²òÀ⤵¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¤È¤Ï¸Â¤ê¤Þ¤»¤ó¡£ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÄ󶡤¹¤ë¥â¥¸¥å¡¼¥ë¤Ï¥Ç¥Õ¥©¥ë¥È¤ÇÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤«¤â + ¤·¤ì¤Þ¤»¤ó¤·¡¢¤½¤¦¤Ç¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£»ÈÍѲÄǽ¤«¤É¤¦¤«¤Ï¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¥â¥¸¥å¡¼¥ë¤ÎÀâÌÀ¤ò¤·¤Æ¤¤¤ë¥Ú¡¼¥¸¤ÎÀèƬ¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£
+
+
top
+
+

¥â¥¸¥å¡¼¥ë

+ +

+ ¤³¤ì¤Ïñ½ã¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ÄêµÁ¤µ¤ì¤Æ¤¤¤ë¥â¥¸¥å¡¼¥ë¤Î̾Á°¤òµ­ºÜ¤·¤Þ¤¹¡£

+
top
+
+

¸ß´¹À­

+ +

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ Apache 2 + ¤ÎÇÛÉÛ¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Ê¤«¤Ã¤¿¾ì¹ç¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Æ³Æþ¤µ¤ì¤¿¥Ð¡¼¥¸¥ç¥ó¤¬¤³¤³¤Ë½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤Þ¤¿¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ÆÃÄê¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ë¤Î¤ß¸ºß¤¹¤ë¤È¤­¤â + ¤³¤³¤Ë½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directive-dict.html.ko.euc-kr b/docs/manual/mod/directive-dict.html.ko.euc-kr new file mode 100644 index 00000000..5f3fa861 --- /dev/null +++ b/docs/manual/mod/directive-dict.html.ko.euc-kr @@ -0,0 +1,252 @@ + + + +Áö½Ã¾î¸¦ ¼³¸íÇϴµ¥ »ç¿ëÇÑ ¿ë¾îµé - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Áö½Ã¾î¸¦ ¼³¸íÇϴµ¥ »ç¿ëÇÑ ¿ë¾îµé

+
+

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

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

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ ¼³Á¤ + Áö½Ã¾î¸¦ ¼³¸íÇϴµ¥ »ç¿ëÇÑ ¿ë¾îµéÀ» ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

¼³¸í (Description)

+ +

Áö½Ã¾îÀÇ ¸ñÀû¿¡ ´ëÇÑ °£´ÜÇÑ ¼³¸í.

+
top
+
+

¹®¹ý (Syntax)

+ +

¼³Á¤ÆÄÀÏ¿¡¼­ »ç¿ëÇÒ Áö½Ã¾îÀÇ Çü½ÄÀ» ¾Ë·ÁÁØ´Ù. ÀÌ ¹®¹ýÀº + Áö½Ã¾î¸¶´Ù ¸Å¿ì ´Ù¸£¸ç, Áö½Ã¾î¸¦ Á¤ÀÇÇÒ ¶§¸¶´Ù ÀÚ¼¼È÷ ¼³¸íÇÑ´Ù. + ÀϹÝÀûÀ¸·Î Áö½Ã¾î À̸§ µÚ¿¡ °ø¹éÀ¸·Î ±¸ºÐÇÑ ¾Æ±Ô¸ÕÆ®µéÀÌ + ³ª¿Â´Ù. ¾Æ±Ô¸ÕÆ®°¡ °ø¹éÀ» Æ÷ÇÔÇÑ´Ù¸é ¾Æ±Ô¸ÕÆ®¸¦ ½Öµû¿ÈÇ¥·Î + ¹­¾î¾ß ÇÑ´Ù. ¼±ÅÃÀûÀÎ ¾Æ±Ô¸ÕÆ®´Â Áß°ýÈ£·Î ¹­´Â´Ù. ¾Æ±Ô¸ÕÆ®°¡ + ¿©·¯ °ªÁß ÇϳªÀÏ °æ¿ì °ªµéÀ» ¼öÁ÷¸·´ë "|"·Î ±¸ºÐÇÑ´Ù. + ¹®ÀÚ±×´ë·Î »ç¿ëÇÒ ºÎºÐÀº ±âº» ¹®ÀÚü·Î ¾²°í, ´ëüÇÒ ¾Æ±Ô¸ÕÆ®´Â + °­Á¶ÇÑ´Ù. ¾Æ±Ô¸ÕÆ® °³¼ö°¡ Á¤ÇØÁöÁö¾ÊÀº Áö½Ã¾î´Â + ¸¶Áö¸· ¾Æ±Ô¸ÕÆ®°¡ ¹Ýº¹µÊÀ» ³ªÅ¸³»´Â "..."À¸·Î ³¡³­´Ù.

+ +

Áö½Ã¾î´Â ¸Å¿ì ´Ù¾çÇÑ Á¾·ùÀÇ ¾Æ±Ô¸ÕÆ®¸¦ ¹Þ´Â´Ù. ÀÌÁß ÀÚÁÖ + »ç¿ëÇÏ´Â °ÍÀº ¾Æ·¡¿Í °°´Ù.

+ +
+
URL
+ +
http://www.example.com/path/to/file.html°ú + °°ÀÌ ½ºÅ´(scheme), È£½ºÆ®¸í, ¼±ÅÃÀûÀÎ °æ·Î¸íÀ» Æ÷ÇÔÇÑ + ¿ÏÀüÇÑ Uniform Resource Locator
+ +
URL-path
+ +
/path/to/file.html°ú °°ÀÌ url¿¡¼­ + ½ºÅ´°ú È£½ºÆ®¸í µÚ¿¡ ³ª¿À´Â ºÎºÐ. url-path´Â + ÆÄÀϽýºÅÛ¿¡¼­ º» ½ÃÁ¡ÀÌ ¾Æ´Ñ À¥¿¡¼­ º» ½ÃÁ¡¿¡¼­ÀÇ ÀڷḦ + ³ªÅ¸³½´Ù.
+ +
file-path
+ +
/usr/local/apache/htdocs/path/to/file.html°ú + °°ÀÌ root µð·ºÅ丮·Î ½ÃÀÛÇÏ´Â ÆÄÀϽýºÅÛ»óÀÇ ÆÄÀÏ °æ·Î. µû·Î + ¾ð±ÞÇÏÁö¾ÊÀ¸¸é, ½½·¡½¬·Î ½ÃÀÛÇÏÁö¾ÊÀº file-path´Â + ServerRoot¿¡ »ó´ë°æ·Î·Î + Ãë±ÞÇÑ´Ù.
+ +
directory-path
+ +
/usr/local/apache/htdocs/path/to/¿Í °°ÀÌ + root µð·ºÅ丮·Î ½ÃÀÛÇÏ´Â ÆÄÀϽýºÅÛ»óÀÇ µð·ºÅ丮 °æ·Î.
+ +
filename
+ +
file.html°ú °°ÀÌ °æ·Î Á¤º¸°¡ ¾ø´Â ÆÄÀϸí.
+ +
regex
+ +
Perl Çü½ÄÀÇ Á¤±ÔÇ¥Çö½Ä(regular + expression). Áö½Ã¾î´Â regex·Î ¹«¾ùÀΰ¡¸¦ °Ë»öÇÑ´Ù.
+ +
extension
+ +
ÀϹÝÀûÀ¸·Î filename¿¡¼­ ¸¶Áö¸· ¸¶Ä§Ç¥ µÚ¿¡ + ³ª¿À´Â ºÎºÐÀÌ´Ù. ±×·¯³ª ¾ÆÆÄÄ¡´Â ¿©·¯ È®ÀåÀÚ¸¦ ÀνÄÇÒ + ¼ö Àֱ⶧¹®¿¡, filename¿¡ ¸¶Ä§Ç¥°¡ ¿©·¯°³ Æ÷ÇÔµÈ + °æ¿ì ¸¶Ä§Ç¥·Î ±¸ºÐµÈ ¸ðµç ºÎºÐÀ» È®ÀåÀÚ(extension)·Î + ó¸®ÇÑ´Ù. ¿¹¸¦ µé¾î, ÆÄÀϸí file.html.enÀº + .html°ú .enÀ̶ó´Â µÎ°¡Áö È®ÀåÀÚ¸¦ + °¡Áø´Ù. ¾ÆÆÄÄ¡ Áö½Ã¾î¿¡¼­ extension¿¡ ÁöÁ¤ÇÑ + °ª ¾Õ¿¡ ¸¶Ä§Ç¥°¡ À־ µÇ°í ¾ø¾îµµ µÈ´Ù. ¶Ç, + extensionÀº ´ë¼Ò¹®ÀÚ¸¦ °¡¸®Áö¾Ê´Â´Ù.
+ +
MIME-type
+ +
text/html°ú °°ÀÌ ½½·¡½¬·Î major format + type°ú minor format type¸¦ ±¸ºÐÇÏ¿© ÆÄÀÏÀÇ Çü½ÄÀ» ¼³¸íÇÏ´Â + ¹æ½Ä.
+ +
env-variable
+ +
¾ÆÆÄÄ¡ ¼³Á¤¿¡¼­ Á¤ÀÇÇÑ È¯°æº¯¼ö + À̸§. ¿î¿µÃ¼Á¦ÀÇ È¯°æº¯¼ö¿Í ´Ù¸§À» ÁÖÀÇÇ϶ó. ÀÚ¼¼ÇÑ ³»¿ëÀº + ȯ°æº¯¼ö ¹®¼­¸¦ Âü°íÇ϶ó.
+
+
top
+
+

±âº»°ª (Default)

+ +

Áö½Ã¾î¿¡ ±âº»°ªÀÌ ÀÖ´Ù¸é (¿¹¸¦ µé¾î, ¼³Á¤¿¡¼­ + Áö½Ã¾î¸¦ »ý·«ÇÑ °æ¿ì ¾ÆÆÄÄ¡ À¥¼­¹ö´Â ÀÌ °ªÀ» »ç¿ëÇÑ´Ù.) + ÀÌ Ç׸ñ¿¡ ³ª¿Â´Ù. ±âº»°ªÀÌ ¾ø´Ù¸é ÀÌ Ç׸ñÀº + "None"À̾î¾ß ÇÑ´Ù. ±âº»°ªÀÌ ¼­¹ö¿¡ Æ÷ÇÔµÈ ±âº» + httpd.confÀÇ Áö½Ã¾î °ª°ú ´Ù¸¦ ¼ö ÀÖÀ½À» ÁÖÀÇÇ϶ó.

+
top
+
+

»ç¿ëÀå¼Ò (Context)

+ +

¼­¹öÀÇ ¼³Á¤ÆÄÀÏÁß ¾î´À°÷¿¡¼­ Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖ´ÂÁö + ¾Ë·ÁÁØ´Ù. ´ÙÀ½ °ªµéÀ» ½°Ç¥·Î ±¸ºÐÇÑ ¸ñ·ÏÀÌ´Ù:

+ +
+
ÁÖ¼­¹ö¼³Á¤ (server config)
+ +
Áö½Ã¾î¸¦ ¼­¹ö ¼³Á¤ÆÄÀÏ¿¡¼­ (¿¹¸¦ µé¾î, + httpd.conf) »ç¿ëÇÒ ¼ö ÀÖÀ¸³ª, <VirtualHost>³ª + <Directory>¿¡¼­ + »ç¿ëÇÒ ¼ö ¾øÀ½À» ¶æÇÑ´Ù. ÀÌ Áö½Ã¾î´Â + .htaccess ÆÄÀÏ¿¡¼­µµ »ç¿ëÇÒ ¼ö ¾ø´Ù.
+ +
°¡»óÈ£½ºÆ® (virtual host)
+ +
Áö½Ã¾î¸¦ ¼­¹ö ¼³Á¤ÆÄÀÏÀÇ <VirtualHost> ¾È¿¡¼­ »ç¿ëÇÒ ¼ö + ÀÖÀ½À» ¶æÇÑ´Ù.
+ +
µð·ºÅ丮 (directory)
+ +
Áö½Ã¾î°¡ ¼½¼Ç ¼³Á¤¿¡ + ¼³¸íÇÑ Á¦¾àÀ» µû¸£¸ç, ¼­¹ö ¼³Á¤ÆÄÀÏÀÇ <Directory>, <Location>, <Files>, <Proxy>¿¡¼­ + »ç¿ëÇÒ ¼ö ÀÖÀ½À» ¶æÇÑ´Ù.
+ +
.htaccess
+ +
Áö½Ã¾î¸¦ µð·ºÅ丮º° .htaccess + ÆÄÀÏ¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖÀ½À» ¶æÇÑ´Ù. ÀÌ Áö½Ã¾î´Â ÇöÀç »ç¿ëÇÏ´Â + overrides °ª¿¡ µû¶ó ¹«½ÃµÉ ¼ö + ÀÖ´Ù.
+
+ +

Áö½Ã¾î´Â ÁöÁ¤µÈ Àå¼Ò¿¡¼­¸¸ »ç¿ëÇÒ ¼ö ÀÖ´Ù. ´Ù¸¥ + °÷¿¡¼­ »ç¿ëÇÏ¸é ¼³Á¤¿À·ù°¡ ¹ß»ýÇÏ°í ¼­¹ö´Â ºÎºÐ¿¡ ´ëÇÑ ¿äûÀ» + ¿Ã¹Ù·Î ó¸®ÇÏÁö ¸øÇϰųª ÀÛµ¿ÀÌ, ¿¹¸¦ µé¾î ½ÃÀÛÁ¶Â÷µµ, + ¾ÈµÉ ¼ö ÀÖ´Ù.

+ +

Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Â Àå¼Ò´Â ¿­°ÅÇÑ Àå¼Ò¸¦ ¸ðµÎ + ºÒ¸°(boolean) ORÇÑ °á°úÀÌ´Ù. Áï, + "server config, .htaccess"¿¡¼­ °¡´ÉÇÏ´Ù´Â + Áö½Ã¾î´Â httpd.conf ÆÄÀÏ°ú .htaccess + ÆÄÀÏ¿¡¼­´Â »ç¿ëÇÒ ¼ö ÀÖÁö¸¸, <Directory>³ª <VirtualHost>¿¡¼­´Â »ç¿ëÇÒ ¼ö ¾ø´Ù.

+
top
+
+

Override ¿É¼Ç (Override)

+ +

ÀÌ Áö½Ã¾î¸¦ .htaccess ÆÄÀÏ¿¡¼­ »ç¿ëÇÏ·Á¸é + ¾î¶² override ¿É¼ÇÀ» »ç¿ëÇØ¾ß ÇÏ´ÂÁö¸¦ ³ªÅ¸³½´Ù. Áö½Ã¾îÀÇ + »ç¿ëÀå¼Ò°¡ Áö½Ã¾î¸¦ .htaccess + ÆÄÀÏ¿¡¼­ »ç¿ëÇÒ ¼ö ¾ø´Ù°í ÇÑ´Ù¸é ¾î¶² »ç¿ëÀå¼Òµµ ³ª¿ÀÁö + ¾Ê´Â´Ù.

+ +

Overrides´Â AllowOverride Áö½Ã¾î·Î Áö½ÃÇÏ°í, + (µð·ºÅ丮 µîÀÇ) ƯÁ¤ ¹üÀ§¿Í ÇÏÀ§ ¹üÀ§¿¡¼­ ´Ù¸¥ AllowOverride Áö½Ã¾î·Î ´Ù¸¥ °ªÀ» + ¼³Á¤ÇÏÁö¾Ê¾Ò´Ù¸é ÇÏÀ§ ¹üÀ§¿¡µµ ±×´ë·Î Àû¿ëµÈ´Ù. Áö½Ã¾î ¼³¸í¿¡ + »ç¿ë°¡´ÉÇÑ override À̸§µéÀÌ ³ª¿Â´Ù.

+
top
+
+

»óÅÂ (Status)

+ +

Áö½Ã¾î°¡ ¾ÆÆÄÄ¡ À¥¼­¹ö¿¡ ¾ó¸¶³ª ±ä¹ÐÈ÷ ¹­¿©ÀÖ´ÂÁö¸¦ + ³ªÅ¸³½´Ù. Áï, ±× Áö½Ã¾î³ª ±â´ÉÀ» »ç¿ëÇϱâÀ§ÇØ ¼­¹ö¸¦ + ¸ðµâ°ú °°ÀÌ ´Ù½Ã ÄÄÆÄÀÏÇÒ ÇÊ¿ä°¡ ÀÖÀ» ¼öµµ ÀÖ´Ù. + °¡´ÉÇÑ °ªÀº ´ÙÀ½°ú °°´Ù:

+ +
+
Core
+ +
Áö½Ã¾î°¡ "Core" »óŸ¦ °¡Áö¸é, Áö½Ã¾î°¡ ¾ÆÆÄÄ¡ À¥¼­¹ö + Çٽɺκп¡ ¼ÓÇÏ°í Ç×»ó »ç¿ë°¡´ÉÇÔÀ» ¶æÇÑ´Ù.
+ +
MPM
+ +
"MPM" »óÅÂÀÎ Áö½Ã¾î´Â ´ÙÁßó¸® + ¸ðµâÀ» Á¦°øÇÑ´Ù. ÀÌ·± Áö½Ã¾î´Â Áö½Ã¾î ¼³¸í¿¡¼­ ¸ðµâ¿¡ ¿­°ÅµÈ MPMÁß Çϳª¸¦ »ç¿ëÇÒ¶§¸¸ + °¡´ÉÇÏ´Ù.
+ +
Base
+ +
±âº»ÀûÀ¸·Î ¼­¹ö¿Í °°ÀÌ ÄÄÆÄÀϵǹǷΠÁ÷Á¢ ±¸¼º¿¡¼­ + ¸ðµâÀ» Á¦°ÅÇÏÁö ¾Ê¾Ò´Ù¸é ÀϹÝÀûÀ¸·Î »ç¿ë°¡´ÉÇÑ Ç¥ÁØ ¾ÆÆÄÄ¡ + ¸ðµâÀÌ Á¦°øÇÏ´Â Áö½Ã¾î´Â "Base" »óÅÂÀÌ´Ù.
+ +
Extension
+ +
¾ÆÆÄÄ¡ ¼­¹ö ¹èÆ÷º»¿¡´Â Æ÷ÇÔµÇÀÖÁö¸¸ º¸Åë ¼­¹ö¿Í °°ÀÌ + ÄÄÆÄÀϵÇÁö¾Ê´Â ¸ðµâÀÌ Á¦°øÇÏ´Â Áö½Ã¾î´Â "Extension" »óÅÂÀÌ´Ù. + ÀÌ·± Áö½Ã¾î¸¦ »ç¿ëÇÏ·Á¸é ¼­¹ö ÄÄÆÄÀÏ ±¸¼ºÆÄÀÏÀ» ¼öÁ¤ÇÏ°í + ¾ÆÆÄÄ¡¸¦ ´Ù½Ã ÄÄÆÄÀÏÇØ¾ß ÇÑ´Ù.
+ +
Experimental
+ +
"Experimental"Àº Áö½Ã¾î°¡ ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡ Æ÷ÇÔµÇÀÖÁö¸¸, + »ç¿ëÀº ÀÚ½ÅÀÇ Ã¥ÀÓÀÓÀ» ³ªÅ¸³½´Ù. Áö½Ã¾î´Â ¹®¼­È­µÇÀÖÁö¸¸, + ½ÇÁ¦¿Í ´Ù¸¦ ¼ö ÀÖ´Ù. Áö½Ã¾î¸¦ Á¦°øÇÏ´Â ¸ðµâÀº ±âº»ÀûÀ¸·Î + ¾ÆÆÄÄ¡¿Í °°ÀÌ ÄÄÆÄÀ쵃 ¼öµµ ¾ÈµÉ ¼öµµ ÀÖ´Ù. Áö½Ã¾î¿Í ¸ðµâÀ» + ¼³¸íÇÏ´Â ¹®¼­ ¾Õ¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖ´ÂÁö »ìÆìºÁ¶ó.
+
+
top
+
+

¸ðµâ (Module)

+ +

´Ü¼øÈ÷ Áö½Ã¾î¸¦ Á¤ÀÇÇÑ ¼Ò½º ¸ðµâ¸íÀ» ¿­°ÅÇÑ´Ù.

+
top
+
+

Áö¿ø (Compatibility)

+ +

Áö½Ã¾î°¡ ¿ø·¡ ¾ÆÆÄÄ¡ ¹öÀü 2 ¹èÆ÷º»ÀÇ ÀϺΰ¡ ¾Æ´Ï¿´´Ù¸é, + Áö½Ã¾î¸¦ Ãß°¡Çϱ⠽ÃÀÛÇÑ ¹öÀüÀÌ ¿©±â ³ª¿Â´Ù. ¶Ç, ¾î¶² + Ç÷¡Æû¿¡¼­¸¸ »ç¿ë°¡´ÉÇÑ Áö½Ã¾îµµ ¿©±â ³ª¿Â´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directives.html b/docs/manual/mod/directives.html new file mode 100644 index 00000000..d52769de --- /dev/null +++ b/docs/manual/mod/directives.html @@ -0,0 +1,23 @@ +URI: directives.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: directives.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: directives.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: directives.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: directives.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: directives.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R diff --git a/docs/manual/mod/directives.html.de b/docs/manual/mod/directives.html.de new file mode 100644 index 00000000..ed8dfd2d --- /dev/null +++ b/docs/manual/mod/directives.html.de @@ -0,0 +1,428 @@ + + + +Verzeichnis der Direktiven - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module

Verzeichnis der Direktiven

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

+ Hier sind alle Apache-Direktiven aufgeführt, die in der + Standard-Apache-Distribution verfügbar sind. Sie sind in + einem einheitlichen Format beschrieben. Ein Glossar + erläutert die in der Beschreibung verwendeten Begriffe. +

+ +

+ Außerdem existiert eine Kurzreferenz der Direktiven, welche + zu jeder Direktive eine Zusammenfassung der Details enthält. +

+ +

 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X 

+
+
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directives.html.en b/docs/manual/mod/directives.html.en new file mode 100644 index 00000000..64bc3674 --- /dev/null +++ b/docs/manual/mod/directives.html.en @@ -0,0 +1,434 @@ + + + +Directive Index - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules

Directive Index

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

+ Each Apache directive available in the standard Apache + distribution is listed here. They are described using a + consistent format, and there is a dictionary of the terms used in their + descriptions available. +

+ +

+ A Directive Quick-Reference + is also available giving details about each directive in a + summary form. +

+ +

 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X 

+
+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directives.html.es b/docs/manual/mod/directives.html.es new file mode 100644 index 00000000..4141bbc8 --- /dev/null +++ b/docs/manual/mod/directives.html.es @@ -0,0 +1,436 @@ + + + +Índice de Directivas - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2 > Módulos

Índice de Directivas

+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

+ Todas las directivas disponibles en la distribución + estándar de Apache están en la lista que se muestra más + abajo. Cada una se describe usando un formato uniforme, y existe + un glosario + de los términos usados en las descripciones que puede + consultar. +

+ +

+ También existe una Guía Rápida de + Referencia de Directivas con información de cada + directiva de forma resumida. +

+ +

 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X 

+
+
+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directives.html.ja.euc-jp b/docs/manual/mod/directives.html.ja.euc-jp new file mode 100644 index 00000000..e7b56403 --- /dev/null +++ b/docs/manual/mod/directives.html.ja.euc-jp @@ -0,0 +1,429 @@ + + + +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö°ìÍ÷ - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö°ìÍ÷

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

+ ɸ½à Apache ÇÛÉۤˤ¢¤ë¤¹¤Ù¤Æ¤Î Apache ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ìÍ÷¤Ç¤¹¡£ + ¤³¤ì¤é¤Ï°ì´Ó¤·¤¿·Á¼°¤Ç½ñ¤«¤ì¤Æ¤¤¤Æ¡¢»È¤ï¤ì¤Æ¤¤¤ëÍѸì¤Î + ÍѸ콸 ¤âÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ +

+

+ ³Æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î³µÍפòÀâÌÀ¤·¤¿ ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¥¯¥¤¥Ã¥¯¥ê¥Õ¥¡¥ì¥ó¥¹¤â + ¤¢¤ê¤Þ¤¹¡£ +

+ +

 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X 

+
+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directives.html.ko.euc-kr b/docs/manual/mod/directives.html.ko.euc-kr new file mode 100644 index 00000000..7cdb00a7 --- /dev/null +++ b/docs/manual/mod/directives.html.ko.euc-kr @@ -0,0 +1,428 @@ + + + +Áö½Ã¾î ¸ñ·Ï - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ

Áö½Ã¾î ¸ñ·Ï

+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

+ ´ÙÀ½Àº Ç¥ÁØ ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡¼­ »ç¿ë°¡´ÉÇÑ Áö½Ã¾î ¸ñ·ÏÀÌ´Ù. + À̵éÀ» µ¿ÀÏÇÑ Çü½ÄÀ¸·Î ¼³¸íÇÏ¿´°í, ¼³¸í¿¡ »ç¿ëÇÑ ¿ë¾î + »çÀüµµ ÀÖ´Ù. +

+ +

+ °¢ Áö½Ã¾î¸¦ ¿ä¾àÇÏ¿© ¼³¸íÇÑ Áö½Ã¾î ºü¸¥ÂüÁ¶µµ ÀÖ´Ù. +

+ +

 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X 

+
+
+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/directives.html.ru.koi8-r b/docs/manual/mod/directives.html.ru.koi8-r new file mode 100644 index 00000000..3b9597e1 --- /dev/null +++ b/docs/manual/mod/directives.html.ru.koi8-r @@ -0,0 +1,433 @@ + + + +áÌÆÁ×ÉÔÎÙÊ ÕËÁÚÁÔÅÌØ ÄÉÒÅËÔÉ× - HTTP ÓÅÒ×ÅÒ Apache + + + + +
+

íÏÄÕÌÉ | äÉÒÅËÔÉ×Ù | FAQ | çÌÏÓÓÁÒÉÊ | ëÁÒÔÁ ÓÁÊÔÁ

+

HTTP ÓÅÒ×ÅÒ Apache ×ÅÒÓÉÉ 2.2

+
+
<-
+
+Apache > HTTP ÓÅÒ×ÅÒ > äÏËÕÍÅÎÔÁÃÉÑ > ÷ÅÒÓÉÑ 2.2 > íÏÄÕÌÉ

áÌÆÁ×ÉÔÎÙÊ ÕËÁÚÁÔÅÌØ ÄÉÒÅËÔÉ×

+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

úÄÅÓØ ÐÒÉ×ÏÄÉÔÓÑ ÓÐÉÓÏË ×ÓÅÈ ÄÉÒÅËÔÉ×, ËÏÔÏÒÙÅ ÄÏÓÔÕÐÎÙ + × ÓÔÁÎÄÁÒÔÎÏÍ ÄÉÓÔÒÉÂÕÔÉ×Å Apache. äÌÑ ËÁÖÄÏÊ ÄÉÒÅËÔÉ×Ù + ÄÁ£ÔÓÑ ËÒÁÔËÏÅ ÏÐÉÓÁÎÉÅ, Á ÓÍÙÓÌ ×ÓÅÈ ÔÅÒÍÉÎÏ×, + ÉÓÐÏÌØÚÏ×ÁÎÎÙÈ ÐÒÉ ÜÔÏÍ, ÍÏÖÎÏ ÎÁÊÔÉ × çÌÏÓÓÁÒÉÉ ÔÅÒÍÉÎÏ×. +

+ +

+ ôÁËÖÅ ÄÏÓÔÕÐÎÏ ëÒÁÔËÏÅ ÒÕËÏ×ÏÄÓÔ×Ï + ÐÏ ÄÉÒÅËÔÉ×ÁÍ, × ËÏÔÏÒÏÍ ÐÒÉ×ÏÄÉÔÓÑ ÓÕÍÍÁÒÎÁÑ ÉÎÆÏÒÍÁÃÉÑ + ÐÏ ×ÓÅÍ ÄÉÒÅËÔÉ×ÁÍ. +

+ +

 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X 

+
+
+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/event.html b/docs/manual/mod/event.html new file mode 100644 index 00000000..df756d52 --- /dev/null +++ b/docs/manual/mod/event.html @@ -0,0 +1,3 @@ +URI: event.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/event.html.en b/docs/manual/mod/event.html.en new file mode 100644 index 00000000..2e55d4b6 --- /dev/null +++ b/docs/manual/mod/event.html.en @@ -0,0 +1,146 @@ + + + +event - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache MPM event

+
+

Available Languages:  en 

+
+ + + +
Description:An experimental variant of the standard worker +MPM
Status:MPM
Module Identifier:mpm_event_module
Source File:event.c
+

Summary

+ +

Warning

+

This MPM is experimental, so it may or may not work as + expected.

+
+ +

The event Multi-Processing Module (MPM) is + designed to allow more requests to be served simultaneously by + passing off some processing work to supporting threads, freeing up + the main threads to work on new requests. It is based on the + worker MPM, which implements a hybrid + multi-process multi-threaded server. Run-time configuration + directives are identical to those provided by + worker.

+ +

To use the event MPM, add + --with-mpm=event to the configure + script's arguments when building the httpd.

+ +
+ +
top
+
+

How it Works

+

This MPM tries to fix the 'keep alive problem' in HTTP. After a client + completes the first request, the client can keep the connection + open, and send further requests using the same socket. This can + save signifigant overhead in creating TCP connections. However, + Apache traditionally keeps an entire child process/thread waiting + for data from the client, which brings its own disadvantages. To + solve this problem, this MPM uses a dedicated thread to handle both + the Listening sockets, and all sockets that are in a Keep Alive + state.

+ +

The MPM assumes that the underlying apr_pollset + implementation is reasonably threadsafe. This enables the MPM to + avoid excessive high level locking, or having to wake up the listener + thread in order to send it a keep-alive socket. This is currently + only compatible with KQueue and EPoll.

+ +
top
+
+

Requirements

+

This MPM depends on APR's atomic + compare-and-swap operations for thread synchronization. If you are + compiling for an x86 target and you don't need to support 386s, or + you are compiling for a SPARC and you don't need to run on + pre-UltraSPARC chips, add + --enable-nonportable-atomics=yes to the + configure script's arguments. This will cause + APR to implement atomic operations using efficient opcodes not + available in older CPUs.

+ +

This MPM does not perform well on older platforms which lack good + threading, but the requirement for EPoll or KQueue makes this + moot.

+ +
    + +
  • To use this MPM on FreeBSD, FreeBSD 5.3 or higher is recommended. + However, it is possible to run this MPM on FreeBSD 5.2.1, if you + use libkse (see man libmap.conf).
    • + +
  • For NetBSD, at least version 2.0 is recommended.
    • + +
  • For Linux, a 2.6 kernel is recommended. It is also necessary to + ensure that your version of glibc has been compiled + with support for EPoll.
    • + +
+
top
+
+

Issues

+

At present, this MPM is incompatible with mod_ssl, and + other input filters.

+
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/index.html b/docs/manual/mod/index.html new file mode 100644 index 00000000..15e69b07 --- /dev/null +++ b/docs/manual/mod/index.html @@ -0,0 +1,19 @@ +URI: index.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/index.html.de b/docs/manual/mod/index.html.de new file mode 100644 index 00000000..5a154980 --- /dev/null +++ b/docs/manual/mod/index.html.de @@ -0,0 +1,193 @@ + + + +Modul-Index - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Modul-Index

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko 

+
+ +

+ Unten ist eine Liste aller Module angegeben, die als Bestandteil der + Apache-Distribution mitgeliefert werden. Bitte beachten Sie auch die + vollständige alphabetische Liste aller + Apache-Direktiven. +

+
+ +
top
+

Kernfunktionen und + Multi-Processing-Module

+
+
core
Ständig verfügbare Kernfunktionen des Apache HTTP +Servers
+
mpm_common
Eine Sammlung von Direktiven, die in mehr als einem + Multi-Processing-Modul (MPM) implementiert sind.
+
beos
Dieses Multi-Processing-Modul ist für BeOS + optimiert.
+
event
An experimental variant of the standard worker +MPM
+
mpm_netware
Multi-Processing Module implementing an exclusively threaded web + server optimized for Novell NetWare
+
mpmt_os2
Hybrid multi-process, multi-threaded MPM for OS/2
+
prefork
Implementiert einen im Voraus forkenden Webserver ohne + Thread-Unterstützung
+
mpm_winnt
Das Multi-Processing-Modul ist optimiert für + Windows NT.
+
worker
Multi-Processing-Modul, das einen Hybrid-Webserver mit + Multi-Thread und Multi-Prozess-Unterstützung implementiert
+
+
top
+

Andere Module

+

 A  |  C  |  D  |  E  |  F  |  H  |  I  |  L  |  M  |  N  |  P  |  R  |  S  |  U  |  V 

+
mod_actions
Dieses Modul ermöglicht die Ausführung von CGI-Skripten + in Abhängigkeit von Medientypen und Anfragemethoden.
+
mod_alias
Provides for mapping different parts of the host + filesystem in the document tree and for URL redirection
+
mod_asis
Sends files that contain their own +HTTP headers
+
mod_auth_basic
Basic authentication
+
mod_auth_digest
User authentication using MD5 + Digest Authentication.
+
mod_authn_alias
Provides the ability to create extended authentication + providers based on actual providers
+
mod_authn_anon
Allows "anonymous" user access to authenticated + areas
+
mod_authn_dbd
User authentication using an SQL database
+
mod_authn_dbm
User authentication using DBM files
+
mod_authn_default
Authentication fallback module
+
mod_authn_file
User authentication using text files
+
mod_authnz_ldap
Allows an LDAP directory to be used to store the database +for HTTP Basic authentication.
+
mod_authz_dbm
Group authorization using DBM files
+
mod_authz_default
Authorization fallback module
+
mod_authz_groupfile
Group authorization using plaintext files
+
mod_authz_host
Group authorizations based on host (name or IP +address)
+
mod_authz_owner
Authorization based on file ownership
+
mod_authz_user
User Authorization
+
mod_autoindex
Generates directory indexes, + automatically, similar to the Unix ls command or the + Win32 dir shell command
+
mod_cache
Content cache keyed to URIs.
+
mod_cern_meta
CERN httpd metafile semantics
+
mod_cgi
Execution of CGI scripts
+
mod_cgid
Execution of CGI scripts using an + external CGI daemon
+
mod_charset_lite
Specify character set translation or recoding
+
mod_dav
Distributed Authoring and Versioning +(WebDAV) functionality
+
mod_dav_fs
filesystem provider for mod_dav
+
mod_dav_lock
generic locking module for mod_dav
+
mod_dbd
Manages SQL database connections
+
mod_deflate
Compress content before it is delivered to the +client
+
mod_dir
Provides for "trailing slash" redirects and + serving directory index files
+
mod_disk_cache
Content cache storage manager keyed to URIs
+
mod_dumpio
Dumps all I/O to error log as desired.
+
mod_echo
A simple echo server to illustrate protocol +modules
+
mod_env
Modifies the environment which is passed to CGI scripts and +SSI pages
+
mod_example
Illustrates the Apache module API
+
mod_expires
Generation of Expires and +Cache-Control HTTP headers according to user-specified +criteria
+
mod_ext_filter
Pass the response body through an external program before +delivery to the client
+
mod_file_cache
Caches a static list of files in memory
+
mod_filter
Context-sensitive smart filter configuration module
+
mod_headers
Customization of HTTP request and response +headers
+
mod_ident
RFC 1413 ident lookups
+
mod_imagemap
Server-side imagemap processing
+
mod_include
Server-parsed html documents (Server Side Includes)
+
mod_info
Provides a comprehensive overview of the server +configuration
+
mod_isapi
ISAPI Extensions within Apache for Windows
+
mod_ldap
LDAP connection pooling and result caching services for use +by other LDAP modules
+
mod_log_config
Logging of the requests made to the server
+
mod_log_forensic
Forensic Logging of the requests made to the server
+
mod_logio
Logging of input and output bytes per request
+
mod_mem_cache
Content cache keyed to URIs
+
mod_mime
Associates the requested filename's extensions + with the file's behavior (handlers and filters) + and content (mime-type, language, character set and + encoding)
+
mod_mime_magic
Determines the MIME type of a file + by looking at a few bytes of its contents
+
mod_negotiation
Provides for content negotiation
+
mod_nw_ssl
Enable SSL encryption for NetWare
+
mod_proxy
HTTP/1.1 proxy/gateway server
+
mod_proxy_ajp
AJP support module for +mod_proxy
+
mod_proxy_balancer
mod_proxy extension for load balancing
+
mod_proxy_connect
mod_proxy extension for +CONNECT request handling
+
mod_proxy_ftp
FTP support module for +mod_proxy
+
mod_proxy_http
HTTP support module for +mod_proxy
+
mod_rewrite
Provides a rule-based rewriting engine to rewrite requested +URLs on the fly
+
mod_setenvif
Allows the setting of environment variables based +on characteristics of the request
+
mod_so
Loading of executable code and +modules into the server at start-up or restart time
+
mod_speling
Attempts to correct mistaken URLs that +users might have entered by ignoring capitalization and by +allowing up to one misspelling
+
mod_ssl
Strong cryptography using the Secure Sockets +Layer (SSL) and Transport Layer Security (TLS) protocols
+
mod_status
Provides information on server activity and +performance
+
mod_suexec
Allows CGI scripts to run as a specified user +and Group
+
mod_unique_id
Provides an environment variable with a unique +identifier for each request
+
mod_userdir
User-specific directories
+
mod_usertrack
+Clickstream logging of user activity on a site +
+
mod_version
Version dependent configuration
+
mod_vhost_alias
Provides for dynamically configured mass virtual +hosting
+
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/index.html.en b/docs/manual/mod/index.html.en new file mode 100644 index 00000000..539fa723 --- /dev/null +++ b/docs/manual/mod/index.html.en @@ -0,0 +1,191 @@ + + + +Module Index - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Module Index

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ +

+ Below is a list of all of the modules that come as part of + the Apache distribution. See also the complete + alphabetical list of all Apache + directives. +

+
+ +
top
+

Core Features and Multi-Processing + Modules

+
+
core
Core Apache HTTP Server features that are always +available
+
mpm_common
A collection of directives that are implemented by +more than one multi-processing module (MPM)
+
beos
This Multi-Processing Module is optimized for BeOS.
+
event
An experimental variant of the standard worker +MPM
+
mpm_netware
Multi-Processing Module implementing an exclusively threaded web + server optimized for Novell NetWare
+
mpmt_os2
Hybrid multi-process, multi-threaded MPM for OS/2
+
prefork
Implements a non-threaded, pre-forking web server
+
mpm_winnt
This Multi-Processing Module is optimized for Windows +NT.
+
worker
Multi-Processing Module implementing a hybrid + multi-threaded multi-process web server
+
+
top
+

Other Modules

+

 A  |  C  |  D  |  E  |  F  |  H  |  I  |  L  |  M  |  N  |  P  |  R  |  S  |  U  |  V 

+
mod_actions
This module provides for executing CGI scripts based on +media type or request method.
+
mod_alias
Provides for mapping different parts of the host + filesystem in the document tree and for URL redirection
+
mod_asis
Sends files that contain their own +HTTP headers
+
mod_auth_basic
Basic authentication
+
mod_auth_digest
User authentication using MD5 + Digest Authentication.
+
mod_authn_alias
Provides the ability to create extended authentication + providers based on actual providers
+
mod_authn_anon
Allows "anonymous" user access to authenticated + areas
+
mod_authn_dbd
User authentication using an SQL database
+
mod_authn_dbm
User authentication using DBM files
+
mod_authn_default
Authentication fallback module
+
mod_authn_file
User authentication using text files
+
mod_authnz_ldap
Allows an LDAP directory to be used to store the database +for HTTP Basic authentication.
+
mod_authz_dbm
Group authorization using DBM files
+
mod_authz_default
Authorization fallback module
+
mod_authz_groupfile
Group authorization using plaintext files
+
mod_authz_host
Group authorizations based on host (name or IP +address)
+
mod_authz_owner
Authorization based on file ownership
+
mod_authz_user
User Authorization
+
mod_autoindex
Generates directory indexes, + automatically, similar to the Unix ls command or the + Win32 dir shell command
+
mod_cache
Content cache keyed to URIs.
+
mod_cern_meta
CERN httpd metafile semantics
+
mod_cgi
Execution of CGI scripts
+
mod_cgid
Execution of CGI scripts using an + external CGI daemon
+
mod_charset_lite
Specify character set translation or recoding
+
mod_dav
Distributed Authoring and Versioning +(WebDAV) functionality
+
mod_dav_fs
filesystem provider for mod_dav
+
mod_dav_lock
generic locking module for mod_dav
+
mod_dbd
Manages SQL database connections
+
mod_deflate
Compress content before it is delivered to the +client
+
mod_dir
Provides for "trailing slash" redirects and + serving directory index files
+
mod_disk_cache
Content cache storage manager keyed to URIs
+
mod_dumpio
Dumps all I/O to error log as desired.
+
mod_echo
A simple echo server to illustrate protocol +modules
+
mod_env
Modifies the environment which is passed to CGI scripts and +SSI pages
+
mod_example
Illustrates the Apache module API
+
mod_expires
Generation of Expires and +Cache-Control HTTP headers according to user-specified +criteria
+
mod_ext_filter
Pass the response body through an external program before +delivery to the client
+
mod_file_cache
Caches a static list of files in memory
+
mod_filter
Context-sensitive smart filter configuration module
+
mod_headers
Customization of HTTP request and response +headers
+
mod_ident
RFC 1413 ident lookups
+
mod_imagemap
Server-side imagemap processing
+
mod_include
Server-parsed html documents (Server Side Includes)
+
mod_info
Provides a comprehensive overview of the server +configuration
+
mod_isapi
ISAPI Extensions within Apache for Windows
+
mod_ldap
LDAP connection pooling and result caching services for use +by other LDAP modules
+
mod_log_config
Logging of the requests made to the server
+
mod_log_forensic
Forensic Logging of the requests made to the server
+
mod_logio
Logging of input and output bytes per request
+
mod_mem_cache
Content cache keyed to URIs
+
mod_mime
Associates the requested filename's extensions + with the file's behavior (handlers and filters) + and content (mime-type, language, character set and + encoding)
+
mod_mime_magic
Determines the MIME type of a file + by looking at a few bytes of its contents
+
mod_negotiation
Provides for content negotiation
+
mod_nw_ssl
Enable SSL encryption for NetWare
+
mod_proxy
HTTP/1.1 proxy/gateway server
+
mod_proxy_ajp
AJP support module for +mod_proxy
+
mod_proxy_balancer
mod_proxy extension for load balancing
+
mod_proxy_connect
mod_proxy extension for +CONNECT request handling
+
mod_proxy_ftp
FTP support module for +mod_proxy
+
mod_proxy_http
HTTP support module for +mod_proxy
+
mod_rewrite
Provides a rule-based rewriting engine to rewrite requested +URLs on the fly
+
mod_setenvif
Allows the setting of environment variables based +on characteristics of the request
+
mod_so
Loading of executable code and +modules into the server at start-up or restart time
+
mod_speling
Attempts to correct mistaken URLs that +users might have entered by ignoring capitalization and by +allowing up to one misspelling
+
mod_ssl
Strong cryptography using the Secure Sockets +Layer (SSL) and Transport Layer Security (TLS) protocols
+
mod_status
Provides information on server activity and +performance
+
mod_suexec
Allows CGI scripts to run as a specified user +and Group
+
mod_unique_id
Provides an environment variable with a unique +identifier for each request
+
mod_userdir
User-specific directories
+
mod_usertrack
+Clickstream logging of user activity on a site +
+
mod_version
Version dependent configuration
+
mod_vhost_alias
Provides for dynamically configured mass virtual +hosting
+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/index.html.es b/docs/manual/mod/index.html.es new file mode 100644 index 00000000..679cc332 --- /dev/null +++ b/docs/manual/mod/index.html.es @@ -0,0 +1,194 @@ + + + +Índice de Módulos - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

Índice de Módulos

+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko 

+
+ +

+ Abajo se muestra una lista con todos los módulos que forman + parte de la distribución de Apache. Consulte también la lista + alfabética completa de las + directivas de Apache. +

+
+ +
top
+

Funcionalidad Básica y Módulos + de MultiProcesamiento

+
+
core
Core Apache HTTP Server features that are always +available
+
mpm_common
A collection of directives that are implemented by +more than one multi-processing module (MPM)
+
beos
Este módulo de muiltiprocesamiento está +optimizado para BeOS.
+
event
An experimental variant of the standard worker +MPM
+
mpm_netware
Multi-Processing Module implementing an exclusively threaded web + server optimized for Novell NetWare
+
mpmt_os2
Hybrid multi-process, multi-threaded MPM for OS/2
+
prefork
Implements a non-threaded, pre-forking web server
+
mpm_winnt
This Multi-Processing Module is optimized for Windows +NT.
+
worker
Multi-Processing Module implementing a hybrid + multi-threaded multi-process web server
+
+
top
+

Otros Módulos

+

 A  |  C  |  D  |  E  |  F  |  H  |  I  |  L  |  M  |  N  |  P  |  R  |  S  |  U  |  V 

+
mod_actions
This module provides for executing CGI scripts based on +media type or request method.
+
mod_alias
Provides for mapping different parts of the host + filesystem in the document tree and for URL redirection
+
mod_asis
Sends files that contain their own +HTTP headers
+
mod_auth_basic
Basic authentication
+
mod_auth_digest
User authentication using MD5 + Digest Authentication.
+
mod_authn_alias
Provides the ability to create extended authentication + providers based on actual providers
+
mod_authn_anon
Allows "anonymous" user access to authenticated + areas
+
mod_authn_dbd
User authentication using an SQL database
+
mod_authn_dbm
User authentication using DBM files
+
mod_authn_default
Authentication fallback module
+
mod_authn_file
User authentication using text files
+
mod_authnz_ldap
Allows an LDAP directory to be used to store the database +for HTTP Basic authentication.
+
mod_authz_dbm
Group authorization using DBM files
+
mod_authz_default
Authorization fallback module
+
mod_authz_groupfile
Group authorization using plaintext files
+
mod_authz_host
Group authorizations based on host (name or IP +address)
+
mod_authz_owner
Authorization based on file ownership
+
mod_authz_user
User Authorization
+
mod_autoindex
Generates directory indexes, + automatically, similar to the Unix ls command or the + Win32 dir shell command
+
mod_cache
Content cache keyed to URIs.
+
mod_cern_meta
CERN httpd metafile semantics
+
mod_cgi
Execution of CGI scripts
+
mod_cgid
Execution of CGI scripts using an + external CGI daemon
+
mod_charset_lite
Specify character set translation or recoding
+
mod_dav
Distributed Authoring and Versioning +(WebDAV) functionality
+
mod_dav_fs
filesystem provider for mod_dav
+
mod_dav_lock
generic locking module for mod_dav
+
mod_dbd
Manages SQL database connections
+
mod_deflate
Compress content before it is delivered to the +client
+
mod_dir
Provides for "trailing slash" redirects and + serving directory index files
+
mod_disk_cache
Content cache storage manager keyed to URIs
+
mod_dumpio
Dumps all I/O to error log as desired.
+
mod_echo
A simple echo server to illustrate protocol +modules
+
mod_env
Modifies the environment which is passed to CGI scripts and +SSI pages
+
mod_example
Illustrates the Apache module API
+
mod_expires
Generation of Expires and +Cache-Control HTTP headers according to user-specified +criteria
+
mod_ext_filter
Pass the response body through an external program before +delivery to the client
+
mod_file_cache
Caches a static list of files in memory
+
mod_filter
Context-sensitive smart filter configuration module
+
mod_headers
Customization of HTTP request and response +headers
+
mod_ident
RFC 1413 ident lookups
+
mod_imagemap
Server-side imagemap processing
+
mod_include
Server-parsed html documents (Server Side Includes)
+
mod_info
Provides a comprehensive overview of the server +configuration
+
mod_isapi
ISAPI Extensions within Apache for Windows
+
mod_ldap
LDAP connection pooling and result caching services for use +by other LDAP modules
+
mod_log_config
Logging of the requests made to the server
+
mod_log_forensic
Forensic Logging of the requests made to the server
+
mod_logio
Logging of input and output bytes per request
+
mod_mem_cache
Content cache keyed to URIs
+
mod_mime
Associates the requested filename's extensions + with the file's behavior (handlers and filters) + and content (mime-type, language, character set and + encoding)
+
mod_mime_magic
Determines the MIME type of a file + by looking at a few bytes of its contents
+
mod_negotiation
Provides for content negotiation
+
mod_nw_ssl
Enable SSL encryption for NetWare
+
mod_proxy
HTTP/1.1 proxy/gateway server
+
mod_proxy_ajp
AJP support module for +mod_proxy
+
mod_proxy_balancer
mod_proxy extension for load balancing
+
mod_proxy_connect
mod_proxy extension for +CONNECT request handling
+
mod_proxy_ftp
FTP support module for +mod_proxy
+
mod_proxy_http
HTTP support module for +mod_proxy
+
mod_rewrite
Provides a rule-based rewriting engine to rewrite requested +URLs on the fly
+
mod_setenvif
Allows the setting of environment variables based +on characteristics of the request
+
mod_so
Loading of executable code and +modules into the server at start-up or restart time
+
mod_speling
Attempts to correct mistaken URLs that +users might have entered by ignoring capitalization and by +allowing up to one misspelling
+
mod_ssl
Strong cryptography using the Secure Sockets +Layer (SSL) and Transport Layer Security (TLS) protocols
+
mod_status
Provides information on server activity and +performance
+
mod_suexec
Allows CGI scripts to run as a specified user +and Group
+
mod_unique_id
Provides an environment variable with a unique +identifier for each request
+
mod_userdir
User-specific directories
+
mod_usertrack
+Clickstream logging of user activity on a site +
+
mod_version
Version dependent configuration
+
mod_vhost_alias
Provides for dynamically configured mass virtual +hosting
+
+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/index.html.ja.euc-jp b/docs/manual/mod/index.html.ja.euc-jp new file mode 100644 index 00000000..ecf7de13 --- /dev/null +++ b/docs/manual/mod/index.html.ja.euc-jp @@ -0,0 +1,179 @@ + + + +¥â¥¸¥å¡¼¥ë°ìÍ÷ - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥â¥¸¥å¡¼¥ë°ìÍ÷

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ +

+ °Ê²¼¤Ï Apache ¤ÎÇÛÉۤΰìÉô¤È¤·¤ÆÇÛ¤é¤ì¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¥â¥¸¥å¡¼¥ë¤Î + °ìÍ÷¤Ç¤¹¡£¤¹¤Ù¤Æ¤Î Apache + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö ¤Î¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È½ç¤Î¥ê¥¹¥È¤â¸«¤Æ¤¯¤À¤µ¤¤¡£ +

+
+ +
top
+

¥³¥¢µ¡Ç½¤È MPM

+
+
core
¾ï¤Ë»ÈÍѲÄǽ¤Ê Apache HTTP ¥µ¡¼¥Ð¤Î¥³¥¢µ¡Ç½
+
mpm_common
Æó¤Ä°Ê¾å¤Î¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM) +¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥³¥ì¥¯¥·¥ç¥ó
+
beos
This Multi-Processing Module is optimized for BeOS.
+
event
An experimental variant of the standard worker +MPM
+
mpm_netware
Multi-Processing Module implementing an exclusively threaded web + server optimized for Novell NetWare
+
mpmt_os2
Hybrid multi-process, multi-threaded MPM for OS/2
+
prefork
¥¹¥ì¥Ã¥É¤ò»È¤ï¤º¡¢Àè¹Ô¤·¤Æ fork ¤ò¹Ô¤Ê¤¦¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¼ÂÁõ +
+
mpm_winnt
Windows NT +¸þ¤±¤ËºÇŬ²½¤µ¤ì¤¿¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë
+
worker
¥Þ¥ë¥Á¥¹¥ì¥Ã¥É¤È¥Þ¥ë¥Á¥×¥í¥»¥¹¤Î¥Ï¥¤¥Ö¥ê¥Ã¥É·¿ +¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¼ÂÁõ¤·¤¿¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë
+
+
top
+

¾¤Î¥â¥¸¥å¡¼¥ë

+

 A  |  C  |  D  |  E  |  F  |  H  |  I  |  L  |  M  |  N  |  P  |  R  |  S  |  U  |  V 

+
mod_actions
¥á¥Ç¥£¥¢¥¿¥¤¥×¤ä¥ê¥¯¥¨¥¹¥È¥á¥½¥Ã¥É¤Ë±þ¤¸¤Æ +CGI ¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤¹¤ëµ¡Ç½¤òÄó¶¡
+
mod_alias
¥Û¥¹¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î¤¤¤í¤¤¤í¤Ê°ã¤¦¾ì½ê¤ò + ¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼¤Ë¥Þ¥Ã¥×¤¹¤ëµ¡Ç½¤È¡¢ + URL ¤Î¥ê¥À¥¤¥ì¥¯¥È¤ò¹Ô¤Ê¤¦µ¡Ç½¤òÄ󶡤¹¤ë
+
mod_asis
¼«Ê¬ÍѤΠHTTP ¥Ø¥Ã¥À¤Î½ñ¤«¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤òÁ÷¿®¤¹¤ë
+
mod_auth_basic
´ðËÜǧ¾Ú
+
mod_auth_digest
User authentication using MD5 + Digest Authentication.
+
mod_authn_alias
Provides the ability to create extended authentication + providers based on actual providers
+
mod_authn_anon
ǧ¾Ú¤¬É¬ÍפÊÎΰè¤Ø¤Î "anonymous" ¥æ¡¼¥¶¤Î¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë +
+
mod_authn_dbd
User authentication using an SQL database
+
mod_authn_dbm
DBM ¥Õ¥¡¥¤¥ë¤òÍѤ¤¤¿¥æ¡¼¥¶Ç§¾Ú
+
mod_authn_default
ǧ¾Ú¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¥â¥¸¥å¡¼¥ë
+
mod_authn_file
¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤òÍѤ¤¤¿¥æ¡¼¥¶Ç§¾Ú
+
mod_authnz_ldap
Allows an LDAP directory to be used to store the database +for HTTP Basic authentication.
+
mod_authz_dbm
Group authorization using DBM files
+
mod_authz_default
¾µÇ§¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¥â¥¸¥å¡¼¥ë
+
mod_authz_groupfile
¥×¥ì¡¼¥ó¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤òÍѤ¤¤¿¥°¥ë¡¼¥×¾µÇ§
+
mod_authz_host
¥Û¥¹¥È (̾Á°¤â¤·¤¯¤Ï IP ¥¢¥É¥ì¥¹) ¤Ë´ð¤Å¤¤¤¿¥°¥ë¡¼¥×¾µÇ§
+
mod_authz_owner
¥Õ¥¡¥¤¥ë¤Î½êÍ­¼Ô¤Ë´ð¤Å¤¤¤¿¾µÇ§
+
mod_authz_user
¥æ¡¼¥¶¾µÇ§
+
mod_autoindex
Unix ¤Î ls ¥³¥Þ¥ó¥É¤ä + Win32 ¤Î dir ¥·¥§¥ë¥³¥Þ¥ó¥É¤Ë»÷¤¿ + ¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤òÀ¸À®¤¹¤ë
+
mod_cache
URI ¤ò¥­¡¼¤Ë¤·¤¿¥³¥ó¥Æ¥ó¥Ä¤Î¥­¥ã¥Ã¥·¥å
+
mod_cern_meta
CERN httpd metafile semantics
+
mod_cgi
CGI ¥¹¥¯¥ê¥×¥È¤Î¼Â¹Ô
+
mod_cgid
³°Éô CGI ¥Ç¡¼¥â¥ó¤ò»È¤Ã¤¿ CGI ¥¹¥¯¥ê¥×¥È¤Î¼Â¹Ô
+
mod_charset_lite
Specify character set translation or recoding
+
mod_dav
ʬ»¶¥ª¡¼¥µ¥ê¥ó¥°¤È¥Ð¡¼¥¸¥ç¥ó´ÉÍý +(WebDAV) µ¡Ç½
+
mod_dav_fs
mod_dav ¤Î¤¿¤á¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥×¥í¥Ð¥¤¥À
+
mod_dav_lock
mod_dav ÍѤÎÈÆÍÑ¥í¥Ã¥¯¥â¥¸¥å¡¼¥ë
+
mod_dbd
Manages SQL database connections
+
mod_deflate
¥¯¥é¥¤¥¢¥ó¥È¤ØÁ÷¤é¤ì¤ëÁ°¤Ë¥³¥ó¥Æ¥ó¥Ä¤ò°µ½Ì¤¹¤ë
+
mod_dir
¡ÖºÇ¸å¤Î¥¹¥é¥Ã¥·¥å¡×¤Î¥ê¥À¥¤¥ì¥¯¥È¤È¡¢¥Ç¥£¥ì¥¯¥È¥ê¤Î +¥¤¥ó¥Ç¥Ã¥¯¥¹¥Õ¥¡¥¤¥ë¤ò°·¤¦µ¡Ç½¤òÄ󶡤¹¤ë
+
mod_disk_cache
URI ¤ò¥­¡¼¤Ë¤·¤¿¥³¥ó¥Æ¥ó¥Ä¥­¥ã¥Ã¥·¥å¥¹¥È¥ì¡¼¥¸´ÉÍý
+
mod_dumpio
˾¤à¤è¤¦¤Ë¤¹¤Ù¤Æ¤Î I/O ¤ò¥¨¥é¡¼¥í¥°¤Ë¥À¥ó¥×¤¹¤ë
+
mod_echo
¥×¥í¥È¥³¥ë¥â¥¸¥å¡¼¥ë¤Î³µÍפò¼¨¤¹¤¿¤á¤Îñ½ã¤Ê¥¨¥³¡¼¥µ¡¼¥Ð +
+
mod_env
CGI ¥¹¥¯¥ê¥×¥ÈµÚ¤Ó SSI +¥Ú¡¼¥¸¤ËÅϤµ¤ì¤ë´Ä¶­ÊÑ¿ô¤òÊѹ¹¤¹¤ëµ¡Ç½¤òÄ󶡤¹¤ë
+
mod_example
Illustrates the Apache module API
+
mod_expires
¥æ¡¼¥¶¤Î»ØÄꤷ¤¿´ð½à¤Ë´ð¤Å¤¤¤¿ Expires ¤È +Cache-Control HTTP ¥Ø¥Ã¥À¤ÎÀ¸À®
+
mod_ext_filter
¥ì¥¹¥Ý¥ó¥¹¤Î¥Ü¥Ç¥£¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ëÁ°¤Ë³°Éô¥×¥í¥°¥é¥à¤Ç½èÍý¤¹¤ë
+
mod_file_cache
Caches a static list of files in memory
+
mod_filter
Context-sensitive smart filter configuration module
+
mod_headers
HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¤È±þÅú¤Î¥Ø¥Ã¥À¤Î¥«¥¹¥¿¥Þ¥¤¥º
+
mod_ident
RFC 1413 ident lookups
+
mod_imagemap
Server-side imagemap processing
+
mod_include
¥µ¡¼¥Ð¤¬¥Ñ¡¼¥¹¤¹¤ë html ¥É¥­¥å¥á¥ó¥È (Server Side Includes)
+
mod_info
¥µ¡¼¥Ð¤ÎÀßÄê¤ÎÊñ³çŪ¤Ê³µ´Ñ¤òÄ󶡤¹¤ë
+
mod_isapi
ISAPI Extensions within Apache for Windows
+
mod_ldap
LDAP connection pooling and result caching services for use +by other LDAP modules
+
mod_log_config
¥µ¡¼¥Ð¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Î¥í¥®¥ó¥°
+
mod_log_forensic
¥µ¡¼¥Ð¤ËÁ÷¤é¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î forensic ¥í¥®¥ó¥°
+
mod_logio
¥ê¥¯¥¨¥¹¥ÈËè¤ËÆþÎϥХ¤¥È¿ô¤È½ÐÎϥХ¤¥È¿ô¤È¤ò¥í¥®¥ó¥°
+
mod_mem_cache
URI ¤ò¥­¡¼¤Ë¤·¤¿¥³¥ó¥Æ¥ó¥Ä¤Î¥­¥ã¥Ã¥·¥å
+
mod_mime
¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤È¥Õ¥¡¥¤¥ë¤Î¿¶¤ëÉñ¤¤ + (¥Ï¥ó¥É¥é¤È¥Õ¥£¥ë¥¿)¡¢ÆâÍÆ (MIME ¥¿¥¤¥×¡¢¸À¸ì¡¢Ê¸»ú¥»¥Ã¥È¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°) + ¤È¤ò´ØÏ¢ÉÕ¤±¤ë
+
mod_mime_magic
Determines the MIME type of a file + by looking at a few bytes of its contents
+
mod_negotiation
¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó + µ¡Ç½¤òÄ󶡤¹¤ë
+
mod_nw_ssl
Enable SSL encryption for NetWare
+
mod_proxy
HTTP/1.1 ¥×¥í¥­¥·/¥²¡¼¥È¥¦¥§¥¤¥µ¡¼¥Ð
+
mod_proxy_ajp
mod_proxy ¤Ç AJP +¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤¿¤á¤Î¥â¥¸¥å¡¼¥ë
+
mod_proxy_balancer
Éé²Ùʬ»¶¤Î¤¿¤á¤Î mod_proxy ³ÈÄ¥
+
mod_proxy_connect
mod_proxy extension for +CONNECT request handling
+
mod_proxy_ftp
FTP support module for +mod_proxy
+
mod_proxy_http
HTTP support module for +mod_proxy
+
mod_rewrite
Provides a rule-based rewriting engine to rewrite requested +URLs on the fly
+
mod_setenvif
¥ê¥¯¥¨¥¹¥È¤ÎÆÃħ¤Ë´ð¤Å¤¤¤¿´Ä¶­ÊÑ¿ô¤ÎÀßÄê¤ò²Äǽ¤Ë¤¹¤ë
+
mod_so
µ¯Æ°»þ¤äºÆµ¯Æ°»þ¤Ë¼Â¹Ô¥³¡¼¥É¤È¥â¥¸¥å¡¼¥ë¤ò¥µ¡¼¥Ð¤Ë¥í¡¼¥É¤¹¤ë +
+
mod_speling
¥æ¡¼¥¶¤¬ÆþÎϤ·¤¿¤Ç¤¢¤í¤¦´Ö°ã¤Ã¤¿ URL ¤ò¡¢ +Âçʸ»ú¾®Ê¸»ú¤Î¶èÊ̤ò̵»ë¤¹¤ë¤³¤È¤È°ì¤Ä°Ê²¼¤ÎÄÖ¤ê´Ö°ã¤¤¤òµöÍƤ¹¤ë¤³¤È¤Ç +½¤Àµ¤ò»î¤ß¤ë
+
mod_ssl
Strong cryptography using the Secure Sockets +Layer (SSL) and Transport Layer Security (TLS) protocols
+
mod_status
¥µ¡¼¥Ð¤Î³èÆ°¾õ¶·¤ÈÀ­Ç½¤Ë´Ø¤¹¤ë¾ðÊó¤òÄ󶡤¹¤ë
+
mod_suexec
»ØÄꤵ¤ì¤¿¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤Ç CGI ¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤¹¤ë
+
mod_unique_id
¤½¤ì¤¾¤ì¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë°ì°Õ¤Ê¼±Ê̻ҤÎÆþ¤Ã¤¿´Ä¶­ÊÑ¿ô¤ò +Ä󶡤¹¤ë
+
mod_userdir
¥æ¡¼¥¶ÀìÍѤΥǥ£¥ì¥¯¥È¥ê¤òÄó¶¡ +
+
mod_usertrack
+Clickstream logging of user activity on a site +
+
mod_version
¥Ð¡¼¥¸¥ç¥ó°Í¸¤ÎÀßÄê
+
mod_vhost_alias
Provides for dynamically configured mass virtual +hosting
+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/index.html.ko.euc-kr b/docs/manual/mod/index.html.ko.euc-kr new file mode 100644 index 00000000..777906b6 --- /dev/null +++ b/docs/manual/mod/index.html.ko.euc-kr @@ -0,0 +1,173 @@ + + + +¸ðµâ ¸ñ·Ï - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¸ðµâ ¸ñ·Ï

+
+

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

+
+ +

+ ´ÙÀ½Àº ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡ Æ÷ÇÔµÈ ¸ðµç ¸ðµâ ¸ñ·ÏÀÌ´Ù. ¸ðµç ¾ÆÆÄÄ¡ Áö½Ã¾î ¸ñ·Ïµµ + Âü°íÇ϶ó. +

+
+ +
top
+

ÇÙ½É ±â´É°ú ´ÙÁßó¸® ¸ðµâ

+
+
core
Core Apache HTTP Server features that are always +available
+
mpm_common
A collection of directives that are implemented by +more than one multi-processing module (MPM)
+
beos
BeOS¿¡ ÃÖÀûÈ­µÈ ´ÙÁßó¸® ¸ðµâ.
+
event
An experimental variant of the standard worker +MPM
+
mpm_netware
Multi-Processing Module implementing an exclusively threaded web + server optimized for Novell NetWare
+
mpmt_os2
Hybrid multi-process, multi-threaded MPM for OS/2
+
prefork
Implements a non-threaded, pre-forking web server
+
mpm_winnt
This Multi-Processing Module is optimized for Windows +NT.
+
worker
Multi-Processing Module implementing a hybrid + multi-threaded multi-process web server
+
+
top
+

´Ù¸¥ ¸ðµâ

+

 A  |  C  |  D  |  E  |  F  |  H  |  I  |  L  |  M  |  N  |  P  |  R  |  S  |  U  |  V 

+
mod_actions
ÀÌ ¸ðµâÀº ¹Ìµð¾îÁ¾·ù³ª ¿äû¸Þ¼­µå¿¡ µû¶ó CGI +½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÑ´Ù.
+
mod_alias
ÆÄÀϽýºÅÛÀÇ ´Ù¸¥ ºÎºÐµéÀ» ¹®¼­ °èÃþ±¸Á¶¿¡ Æ÷ÇÔÇÏ°í, + URL ¸®´ÙÀÌ·º¼ÇÀ» Á¦°øÇÑ´Ù
+
mod_asis
HTTP Çì´õ¸¦ Æ÷ÇÔÇÑ ÆÄÀÏÀ» º¸³½´Ù
+
mod_auth_basic
Basic authentication
+
mod_auth_digest
MD5 Digest AuthenticationÀ» »ç¿ëÇÑ »ç¿ëÀÚÀÎÁõ.
+
mod_authn_alias
Provides the ability to create extended authentication + providers based on actual providers
+
mod_authn_anon
ÀÎÁõ¿µ¿ª¿¡ "À͸í(anonymous)" »ç¿ëÀÚÀÇ Á¢±ÙÀ» +Çã¿ëÇÑ´Ù
+
mod_authn_dbd
User authentication using an SQL database
+
mod_authn_dbm
DBM ÆÄÀÏÀ» »ç¿ëÇÑ »ç¿ëÀÚ ÀÎÁõ
+
mod_authn_default
ÃÖÈÄ ÀÎÁõ¸ðµâ
+
mod_authn_file
¹®ÀÚÆÄÀÏÀ» ÀÌ¿ëÇÑ »ç¿ëÀÚ ÀÎÁõ
+
mod_authnz_ldap
Allows an LDAP directory to be used to store the database +for HTTP Basic authentication.
+
mod_authz_dbm
DBM ÆÄÀÏÀ» »ç¿ëÇÑ ±×·ì ÀÎÁõ
+
mod_authz_default
ÃÖÈÄ ±ÇÇѺο©¸ðµâ
+
mod_authz_groupfile
ÀÏ¹Ý ¹®ÀÚÆÄÀÏÀ» ÀÌ¿ëÇÑ ±×·ì ±ÇÇѺο©
+
mod_authz_host
È£½ºÆ® (À̸§À̳ª IP ÁÖ¼Ò)¸¦ »ç¿ëÇÑ ±×·ì ±ÇÇѺο©
+
mod_authz_owner
ÆÄÀÏ ¼ÒÀ¯ÀÚ¸¦ ÀÌ¿ëÇÑ ±ÇÇѺο©
+
mod_authz_user
»ç¿ëÀÚ ±ÇÇѺο©
+
mod_autoindex
ÀÚµ¿À¸·Î À¯´Ð½ºÀÇ ls ¸í·É¾î³ª Win32ÀÇ + dir ½©¸í·É¾î¿Í À¯»çÇÑ µð·ºÅ丮 ¸ñ·ÏÀ» ¸¸µç´Ù
+
mod_cache
URI¸¦ Å°·Î »ç¿ëÇÏ¿© ³»¿ëÀ» ij½¬ÇÑ´Ù.
+
mod_cern_meta
CERN À¥¼­¹ö ¸ÞŸÆÄÀÏ Áö¿ø
+
mod_cgi
CGI ½ºÅ©¸³Æ® ½ÇÇà
+
mod_cgid
¿ÜºÎ CGI µ¥¸óÀ» »ç¿ëÇÏ¿© CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇà
+
mod_charset_lite
¹®ÀÚÁýÇÕ º¯È¯À» ÁöÁ¤
+
mod_dav
Distributed Authoring and Versioning +(WebDAV) ±â´É
+
mod_dav_fs
mod_davÀ» À§ÇÑ ÆÄÀϽýºÅÛ Á¦°øÀÚ
+
mod_dav_lock
generic locking module for mod_dav
+
mod_dbd
Manages SQL database connections
+
mod_deflate
³»¿ëÀ» Ŭ¶óÀ̾ðÆ®·Î º¸³»±â Àü¿¡ ¾ÐÃàÇÑ´Ù
+
mod_dir
"¸¶Áö¸· ½½·¡½¬" ¸®´ÙÀÌ·º¼ÇÀ» Á¦°øÇÏ°í µð·ºÅ丮 +index ÆÄÀÏÀ» ¼­ºñ½ºÇÑ´Ù
+
mod_disk_cache
Content cache storage manager keyed to URIs
+
mod_dumpio
Dumps all I/O to error log as desired.
+
mod_echo
ÇÁ·ÎÅäÄÝ ¸ðµâÀ» ¼³¸íÇϱâÀ§ÇÑ °£´ÜÇÑ echo ¼­¹ö
+
mod_env
CGI ½ºÅ©¸³Æ®³ª SSI ÆäÀÌÁö¿¡ Àü´ÞÇÒ È¯°æº¯¼ö¸¦ +¼öÁ¤ÇÑ´Ù
+
mod_example
¾ÆÆÄÄ¡ ¸ðµâ API¸¦ ¼³¸íÇÑ´Ù
+
mod_expires
»ç¿ëÀÚ°¡ ÁöÁ¤ÇÑ ±âÁØ¿¡ µû¶ó Expires¿Í +Cache-Control HTTP Çì´õ¸¦ »ý¼ºÇÑ´Ù
+
mod_ext_filter
ÀÀ´ä ³»¿ëÀ» ¿ÜºÎ ÇÁ·Î±×·¥À¸·Î ó¸®ÇÑ ÈÄ Å¬¶óÀ̾ðÆ®·Î +º¸³½´Ù
+
mod_file_cache
¸Þ¸ð¸®¿¡ Á¤Àû ÆÄÀϵéÀ» ij½¬
+
mod_filter
Context-sensitive smart filter configuration module
+
mod_headers
HTTP ¿äû Çì´õ¿Í ÀÀ´ä Çì´õ ¼öÁ¤
+
mod_ident
RFC 1413 ident °Ë»ö
+
mod_imagemap
¼­¹öÃø À̹ÌÁö¸Ê(imagemap) ó¸®
+
mod_include
Server-parsed html documents (Server Side Includes)
+
mod_info
¼­¹ö ¼³Á¤¿¡ ´ëÇÑ Á¾ÇÕÀûÀÎ Á¤º¸¸¦ º¸¿©ÁØ´Ù
+
mod_isapi
Windows¿ë ¾ÆÆÄÄ¡¿¡¼­ ISAPI Extension »ç¿ë
+
mod_ldap
LDAP connection pooling and result caching services for use +by other LDAP modules
+
mod_log_config
¼­¹ö·ÎÀÇ ¿äûÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù
+
mod_log_forensic
Forensic Logging of the requests made to the server
+
mod_logio
¿äû´ç ÀÔÃâ·Â ¹ÙÀÌÆ®¼ö¸¦ ±â·Ï
+
mod_mem_cache
URI¸¦ Å°·Î »ç¿ëÇÏ¿© ³»¿ëÀ» ij½¬ÇÑ´Ù.
+
mod_mime
Associates the requested filename's extensions + with the file's behavior (handlers and filters) + and content (mime-type, language, character set and + encoding)
+
mod_mime_magic
Determines the MIME type of a file + by looking at a few bytes of its contents
+
mod_negotiation
Provides for content negotiation
+
mod_nw_ssl
Enable SSL encryption for NetWare
+
mod_proxy
HTTP/1.1 proxy/gateway server
+
mod_proxy_ajp
AJP support module for +mod_proxy
+
mod_proxy_balancer
mod_proxy extension for load balancing
+
mod_proxy_connect
mod_proxy extension for +CONNECT request handling
+
mod_proxy_ftp
FTP support module for +mod_proxy
+
mod_proxy_http
HTTP support module for +mod_proxy
+
mod_rewrite
Provides a rule-based rewriting engine to rewrite requested +URLs on the fly
+
mod_setenvif
¿äûÀÇ ¼º°Ý¿¡ µû¶ó ȯ°æº¯¼ö ¼³Á¤À» º¯°æÇÑ´Ù
+
mod_so
½ÃÀÛÇÒ¶§ ȤÀº Àç½ÃÀÛÇÒ¶§ ½ÇÇà°¡´ÉÇÑ ÄÚµå¿Í ¸ðµâÀ» +¼­¹ö·Î ÀоîµéÀδÙ
+
mod_speling
»ç¿ëÀÚ°¡ ´ë¼Ò¹®ÀÚ¸¦ À߸ø »ç¿ëÇϰųª ¸ÂÃã¹ýÀÌ Æ²¸®´Â +°ÍÀ» Çѹø±îÁö Çã¿ëÇÏ¿© À߸øµÈ URLÀ» °íÄ¡·Á°í ½ÃµµÇÑ´Ù
+
mod_ssl
Strong cryptography using the Secure Sockets +Layer (SSL) and Transport Layer Security (TLS) protocols
+
mod_status
¼­¹ö È°µ¿°ú ¼º´É¿¡ ´ëÇÑ Á¤º¸¸¦ Á¦°øÇÑ´Ù
+
mod_suexec
CGI ½ºÅ©¸³Æ®¸¦ ƯÁ¤ »ç¿ëÀÚ¿Í ±×·ì ±ÇÇÑÀ¸·Î ½ÇÇàÇÑ´Ù
+
mod_unique_id
°¢ ¿äû¸¶´Ù À¯ÀÏÇÑ ½Äº°ÀÚ¸¦ °¡Áö´Â ȯ°æº¯¼ö¸¦ +Á¦°øÇÑ´Ù
+
mod_userdir
»ç¿ëÀÚº° µð·ºÅ丮
+
mod_usertrack
+Clickstream logging of user activity on a site +
+
mod_version
¹öÀüº° ¼³Á¤
+
mod_vhost_alias
Provides for dynamically configured mass virtual +hosting
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_actions.html b/docs/manual/mod/mod_actions.html new file mode 100644 index 00000000..8b947013 --- /dev/null +++ b/docs/manual/mod/mod_actions.html @@ -0,0 +1,15 @@ +URI: mod_actions.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_actions.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_actions.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_actions.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_actions.html.de b/docs/manual/mod/mod_actions.html.de new file mode 100644 index 00000000..2725b699 --- /dev/null +++ b/docs/manual/mod/mod_actions.html.de @@ -0,0 +1,166 @@ + + + +mod_actions - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module
+
+

Apache-Modul mod_actions

+
+

Verfügbare Sprachen:  de  | + en  | + ja  | + ko 

+
+ + + +
Beschreibung:Dieses Modul ermöglicht die Ausführung von CGI-Skripten + in Abhängigkeit von Medientypen und Anfragemethoden.
Status:Base
Modulbezeichner:actions_module
Quelltext-Datei:mod_actions.c
+

Zusammenfassung

+ +

Das Modul besitzt zwei Direktiven. Die Direktive Action erlaubt die Ausführung von + CGI-Skripten immer dann, wenn eine Anfrage zu einem bestimmten MIME-Type erfolgt. Die Direktive Script erlaubt die Ausführung + von CGI-Skripten abhängig von einer + bestimmten Methode, die in der Anfrage verwendet wird. Dies macht es + deutlich einfacher, Skripte auszuführen, die Dateien + verarbeiten.

+
+ + +
top
+

Action-Direktive

+ + + + + + + + +
Beschreibung:Aktiviert ein CGI-Skript für einen bestimmten Handler oder + Content-Type
Syntax:Action Aktionsart CGI-Skript [virtual]
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis, .htaccess
AllowOverride:FileInfo
Status:Base
Modul:mod_actions
Kompatibilität:Der Schalter virtual und die Übergabe des + Handlers wurden in Apache 2.1 eingeführt.
+

Die Direktive fügt eine Aktion hinzu, welche das + CGI-Skript aktiviert, sobald die Aktionsart durch + eine Anfrage ausgelöst wird. CGI-Skript ist der URL-Pfad + zu einer Ressource, die unter Verwendung von ScriptAlias oder AddHandler als CGI-Skript gekennzeichnet + wurde. Die Aktionsart kann entweder ein Handler oder ein MIME-Type sein. Die URL und den Dateipfad des + angeforderten Dokuments in den Standard-CGI-Umgebungsvariablen + PATH_INFO und PATH_TRANSLATED übergeben. + Der für die jeweilige Anfrage verwendete Handler wird in der + Umgebungsvariablen REDIRECT_HANDLER übergeben.

+ +

Beispiele

+ # Anfragen für Dateien eines bestimmten MIME-Types:
+ Action image/gif /cgi-bin/images.cgi
+
+ # Dateien einer bestimmten Dateiendung
+ AddHandler my-file-type .xyz
+ Action my-file-type /cgi-bin/program.cgi
+

+ +

Im ersten Beispiel werden Anfragen für Dateien mit dem MIME-Type + image/gif von dem angegebenen CGI-Skript + /cgi-bin/images.cgi bearbeitet.

+ +

Im zweiten Beispiel werden Anfragen für Dateien mit der Dateiendung + .xyz von dem angegebenen CGI-Skript + /cgi-bin/program.cgi bearbeitet.

+ +

Der optionale Schalter virtual deaktiviert die Prüfung + auf Existenz der angeforderten Datei. Dies ist beispielsweise + nützlich, wenn Sie die Direktive Action in + Verbindung mit virtuellen Adressräumen verwenden möchten.

+ +

Beispiel

+ <Location /news>
+ + SetHandler news-handler
+ Action news-handler /cgi-bin/news.cgi virtual
+ + </Location> +

+ +

Siehe auch

+ +
+
top
+

Script-Direktive

+ + + + + + +
Beschreibung:Aktiviert ein CGI-Skript für eine bestimmte + Anfragemethode.
Syntax:Script Methode CGI-Skript
Kontext:Serverkonfiguration, Virtual Host, Verzeichnis
Status:Base
Modul:mod_actions
+

Die Direktive fügt eine Aktion hinzu, welche das + CGI-Skript aktiviert, wenn eine Datei unter der Verwendung der + Methode Methode angefordert wird. CGI-Skript ist der + URL-Pfad zu einer Ressource, die unter Verwendung von ScriptAlias oder AddHandler als CGI-Skript gekennzeichnet + wurde. Die URL und der Dateipfad des angeforderten Dokuments werden in den + Standard-CGI-Umgebungsvariablen PATH_INFO und + PATH_TRANSLATED übergeben.

+ +
+ Der Methodenname kann frei gewählt werden. Bei Methodennamen + wird zwischen Groß- und Kleinschreibung unterschieden, so + dass Script PUT und Script put zu vollkommen + unterschiedlichen Ergebnissen führen. +
+ +

Beachten Sie, dass der Script-Befehl nur + Voreinstellungen für Aktionen definiert. Wird ein CGI-Skript + - oder eine andere Ressource, die in der Lage ist, die angeforderte + Methode intern zu bearbeiten - aufgerufen, so wird diese(s) verwendet. + Beachten Sie auch, dass Script mit der Methode + GET nur dann aufgerufen wird, wenn Query-Argumente vorhanden + sind (z.B. foo.html?hi). Andernfalls wird die Anfrage normal + bearbeitet.

+ +

Beispiele

+ # Für <ISINDEX>-ähnliches Suchen
+ Script GET /cgi-bin/search
+
+ # Ein CGI-PUT-Handler
+ Script PUT /~bob/put.cgi
+

+ +
+
+
+

Verfügbare Sprachen:  de  | + en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_actions.html.en b/docs/manual/mod/mod_actions.html.en new file mode 100644 index 00000000..8f62d32a --- /dev/null +++ b/docs/manual/mod/mod_actions.html.en @@ -0,0 +1,164 @@ + + + +mod_actions - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_actions

+
+

Available Languages:  de  | + en  | + ja  | + ko 

+
+ + + +
Description:This module provides for executing CGI scripts based on +media type or request method.
Status:Base
Module Identifier:actions_module
Source File:mod_actions.c
+

Summary

+ +

This module has two directives. The Action directive lets you run CGI + scripts whenever a file of a certain MIME content type is requested. The + Script directive lets + you run CGI scripts whenever a particular method is used in a + request. This makes it much easier to execute scripts that process + files.

+ + +
top
+

Action Directive

+ + + + + + + + +
Description:Activates a CGI script for a particular handler or +content-type
Syntax:Action action-type cgi-script [virtual]
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_actions
Compatibility:The virtual modifier and handler passing were +introduced in Apache 2.1
+

This directive adds an action, which will activate + cgi-script when action-type is triggered by + the request. The cgi-script is the URL-path to a + resource that has been designated as a CGI script using ScriptAlias or AddHandler. The + action-type can be either a handler or a MIME content type. It sends the URL and + file path of the requested document using the standard CGI + PATH_INFO and PATH_TRANSLATED + environment variables. The handler used for the particular request + is passed using the REDIRECT_HANDLER variable.

+ +

Examples

+ # Requests for files of a particular MIME content type:
+ Action image/gif /cgi-bin/images.cgi
+
+ # Files of a particular file extension
+ AddHandler my-file-type .xyz
+ Action my-file-type /cgi-bin/program.cgi
+

+ +

In the first example, requests for files with a MIME content + type of image/gif will be handled by the + specified cgi script /cgi-bin/images.cgi.

+ +

In the second example, requests for files with a file extension of + .xyz are handled by the specified cgi script + /cgi-bin/program.cgi.

+ +

The optional virtual modifier turns off the check + whether the requested file really exists. This is useful, for example, + if you want to use the Action directive in + virtual locations.

+ +

Example

+ <Location /news>
+ + SetHandler news-handler
+ Action news-handler /cgi-bin/news.cgi virtual
+ + </Location> +

+ +

See also

+ +
+
top
+

Script Directive

+ + + + + + +
Description:Activates a CGI script for a particular request +method.
Syntax:Script method cgi-script
Context:server config, virtual host, directory
Status:Base
Module:mod_actions
+

This directive adds an action, which will activate + cgi-script when a file is requested using the method of + method. The cgi-script is the URL-path to a + resource that has been designated as a CGI script using ScriptAlias or AddHandler. The URL and + file path of the requested document is sent using the standard CGI + PATH_INFO and PATH_TRANSLATED environment + variables.

+ +
+ Any arbitrary method name may be used. Method names are + case-sensitive, so Script PUT and + Script put have two entirely different + effects. +
+ +

Note that the Script command defines default + actions only. If a CGI script is called, or some other resource that is + capable of handling the requested method internally, it will do + so. Also note that Script with a method of + GET will only be called if there are query arguments present + (e.g., foo.html?hi). Otherwise, the request will + proceed normally.

+ +

Examples

+ # For <ISINDEX>-style searching
+ Script GET /cgi-bin/search
+
+ # A CGI PUT handler
+ Script PUT /~bob/put.cgi
+

+ +
+
+
+

Available Languages:  de  | + en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_actions.html.ja.euc-jp b/docs/manual/mod/mod_actions.html.ja.euc-jp new file mode 100644 index 00000000..044c37f9 --- /dev/null +++ b/docs/manual/mod/mod_actions.html.ja.euc-jp @@ -0,0 +1,175 @@ + + + +mod_actions - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_actions

+
+

Available Languages:  de  | + en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥á¥Ç¥£¥¢¥¿¥¤¥×¤ä¥ê¥¯¥¨¥¹¥È¥á¥½¥Ã¥É¤Ë±þ¤¸¤Æ +CGI ¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤¹¤ëµ¡Ç½¤òÄó¶¡
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:actions_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_actions.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ë¤ÏÆó¤Ä¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¤¢¤ê¤Þ¤¹¡£Action + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÆÃÄê¤Î MIME ¥¿¥¤¥×¤Î¥Õ¥¡¥¤¥ë¤ò¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¾ì¹ç¤Ë + CGI ¥¹¥¯¥ê¥×¥È¤¬¼Â¹Ô¤µ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£Script + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥ê¥¯¥¨¥¹¥È¤ÇÆÃÄê¤Î¥á¥½¥Ã¥É¤¬»ÈÍѤµ¤ì¤¿¤È¤­¤Ë CGI + ¥¹¥¯¥ê¥×¥È¤¬¼Â¹Ô¤µ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ¤³¤ì¤Ï¥Õ¥¡¥¤¥ë¤ò½èÍý¤¹¤ë¥¹¥¯¥ê¥×¥È¤Î¼Â¹Ô¤ò¤º¤Ã¤È´Êñ¤Ë¤·¤Þ¤¹¡£

+
+ + +
top
+

Action ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:ÆÃÄê¤Î¥Ï¥ó¥É¥é¤ä¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ËÂФ·¤Æ CGI ¤ò¼Â¹Ô¤¹¤ë¤è¤¦¤Ë +ÀßÄê
¹½Ê¸:Action action-type cgi-script [virtual]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_actions
¸ß´¹À­:virtual ½¤¾þ»Ò¤È¥Ï¥ó¥É¥éÅϤ·¤Ï +Apache 2.1 ¤ÇƳÆþ¤µ¤ì¤Þ¤·¤¿
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï action-type + ¤¬¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¤È¤­¤Ë cgi-script + ¤¬¼Â¹Ô¤µ¤ì¤ë¤È¤¤¤¦Æ°ºî¤òÄɲä·¤Þ¤¹¡£cgi-script ¤Ï + ScriptAlias ¤ä + AddHandler ¤Ë¤è¤Ã¤Æ + CGI ¥¹¥¯¥ê¥×¥È¤ËÀßÄꤵ¤ì¤¿¥ê¥½¡¼¥¹¤Ø¤Î URL-path ¤Ç¤¹¡£ + Action-type ¤Ë¤Ï + handler ¤« MIME + ¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤Î URL + ¤È¥Õ¥¡¥¤¥ë¤Î¥Ñ¥¹¤Ïɸ½à CGI ´Ä¶­ÊÑ¿ô PATH_INFO ¤È + PATH_TRANSLATED ¤ò»È¤Ã¤ÆÅÁ¤¨¤é¤ì¤Þ¤¹¡£ + ÆÃÄê¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ»ÈÍѤµ¤ì¤ë¥Ï¥ó¥É¥é¤Ø¤Ï¡¢ + REDIRECT_HANDLER ÊÑ¿ô¤ò»È¤Ã¤ÆÅϤ»¤Þ¤¹¡£

+ +

Îã

+ # Requests for files of a particular MIME content type:
+ Action image/gif /cgi-bin/images.cgi
+
+ # Files of a particular file extension
+ AddHandler my-file-type .xyz
+ Action my-file-type /cgi-bin/program.cgi
+

+ +

ºÇ½é¤ÎÎã¤Ç¤Ï¡¢MIME ¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤¬ image/gif + ¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï¡¢»ØÄꤷ¤¿¥¹¥¯¥ê¥×¥È + /cgi-bin/images.cgi ¤Ç½èÍý¤µ¤ì¤Þ¤¹¡£

+ +

2 ÈÖÌܤÎÎã¤Ç¤Ï¡¢³ÈÄ¥»Ò¤¬ .xyz + ¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï¡¢»ØÄꤷ¤¿¥¹¥¯¥ê¥×¥È + /cgi-bin/program.cgi ¤Ç½èÍý¤µ¤ì¤Þ¤¹¡£

+ +

¥ª¥×¥·¥ç¥ó¤Î virtual ½¤¾þ»Ò¤ò»ÈÍѤ¹¤ë¤È¡¢ + ¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤¬¼ÂºÝ¤Ë¸ºß¤¹¤ë¤«¤É¤¦¤«¤ò¸¡ºº¤·¤Ê¤¤¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤ÏÎ㤨¤Ð¡¢Action ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¥Ð¡¼¥Á¥ã¥ë¤Ê + Location ¤Ë»ÈÍѤ·¤¿¤¤¡¢¤È¤¤¤Ã¤¿¾ì¹ç¤ËÊØÍø¤Ç¤¹¡£

+ +

Îã

+ <Location /news>
+ + SetHandler news-handler
+ Action news-handler /cgi-bin/news.cgi virtual
+ + </Location> +

+ +

»²¾È

+ +
+
top
+

Script ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:ÆÃÄê¤Î¥ê¥¯¥¨¥¹¥È¥á¥½¥Ã¥É¤ËÂФ·¤Æ CGI ¥¹¥¯¥ê¥×¥È¤ò +¼Â¹Ô¤¹¤ë¤è¤¦¤ËÀßÄê
¹½Ê¸:Script method cgi-script
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_actions
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï method + ¤È¤¤¤¦¥á¥½¥Ã¥É¤ò»È¤Ã¤Æ¥ê¥¯¥¨¥¹¥È¤¬¹Ô¤Ê¤ï¤ì¤¿¤È¤­¤Ë + cgi-script ¤ò¼Â¹Ô¤¹¤ë¤È¤¤¤¦Æ°ºî¤òÄɲä·¤Þ¤¹¡£ + cgi-script ¤Ï + ScriptAlias ¤ä + AddHandler ¤Ë¤è¤Ã¤Æ + CGI ¥¹¥¯¥ê¥×¥È¤ËÀßÄꤵ¤ì¤¿¥ê¥½¡¼¥¹¤Ø¤Î URL-path ¤Ç¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤Î URL ¤È¥Õ¥¡¥¤¥ë¤Î¥Ñ¥¹¤Ïɸ½à CGI + ´Ä¶­ÊÑ¿ô PATH_INFO ¤È PATH_TRANSLATED + ¤ò»È¤Ã¤ÆÅÁ¤¨¤é¤ì¤Þ¤¹¡£

+ +
+ Ǥ°Õ¤Î¥á¥½¥Ã¥É̾¤ò»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥á¥½¥Ã¥É̾¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢ + Script PUT ¤È Script put + ¤Ï¤Þ¤Ã¤¿¤¯°ã¤Ã¤¿¸ú²Ì¤Ë¤Ê¤ê¤Þ¤¹¡£ +
+ +

Script ¥³¥Þ¥ó¥É¤Ï¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤ò + Äɲ乤ë¤À¤±¤Ç¤¢¤ë¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤â¤· CGI ¥¹¥¯¥ê¥×¥È¤¬¸Æ¤Ð¤ì¤¿¤ê¡¢¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿ + ¥á¥½¥Ã¥É¤òÆâÉô¤Ç°·¤¦¤³¤È¤Î¤Ç¤­¤ë¾¤Î¥ê¥½¡¼¥¹¤¬¤¢¤ì¤Ð¡¢¤½¤ì¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£ + GET ¥á¥½¥Ã¥É¤Î Script ¤ÏÌä¹ç¤» + °ú¿ô¤¬¤¢¤ë¾ì¹ç¤Ë¤Î¤ß + (¤¿¤È¤¨¤Ð¡¢foo.html?hi) ¸Æ¤Ð¤ì¤ë¤È¤¤¤¦¤³¤È¤Ë¤âÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤ÏÄ̾ïÄ̤ê½èÍý¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ # For <ISINDEX>-style searching
+ Script GET /cgi-bin/search
+
+ # A CGI PUT handler
+ Script PUT /~bob/put.cgi
+

+ +
+
+
+

Available Languages:  de  | + en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_actions.html.ko.euc-kr b/docs/manual/mod/mod_actions.html.ko.euc-kr new file mode 100644 index 00000000..b9e3caa5 --- /dev/null +++ b/docs/manual/mod/mod_actions.html.ko.euc-kr @@ -0,0 +1,166 @@ + + + +mod_actions - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_actions

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:ÀÌ ¸ðµâÀº ¹Ìµð¾îÁ¾·ù³ª ¿äû¸Þ¼­µå¿¡ µû¶ó CGI +½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÑ´Ù.
»óÅÂ:Base
¸ðµâ¸í:actions_module
¼Ò½ºÆÄÀÏ:mod_actions.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâ¿¡´Â µÎ°¡Áö Áö½Ã¾î°¡ ÀÖ´Ù. Action Áö½Ã¾î´Â ¿äûÇÏ´Â + ÆÄÀÏÀÇ MIME content type¿¡ µû¶ó CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÑ´Ù. + Script Áö½Ã¾î´Â + ¿äûÀÌ Æ¯Á¤ ¸Þ¼­µå¸¦ »ç¿ëÇÒ °æ¿ì CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÑ´Ù. + ±×·¡¼­ ÆÄÀÏÀ» ó¸®ÇÏ´Â ½ºÅ©¸³Æ®¸¦ ¸Å¿ì ½±°Ô ½ÇÇàÇÒ ¼ö ÀÖ´Ù.

+
+ + +
top
+

Action Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ƯÁ¤ Çڵ鷯³ª content-type¿¡ ´ëÇØ CGI ½ºÅ©¸³Æ®¸¦ +»ç¿ëÇÑ´Ù
¹®¹ý:Action action-type cgi-script [virtual]
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_actions
Áö¿ø:virtual ¼öÁ¤ÀÚ¿Í Çڵ鷯´Â ¾ÆÆÄÄ¡ +2.1¶§ Ãß°¡µÇ¾ú´Ù
+

ÀÌ Áö½Ã¾î´Â ¿äûÀÌ action-typeÀ̸é + cgi-script¸¦ ½ÇÇàÇÏ´Â ÇൿÀ» ¼­¹ö¿¡ Ãß°¡ÇÑ´Ù. + cgi-script´Â ScriptAlias³ª AddHandler¸¦ »ç¿ëÇÏ¿© CGI + ½ºÅ©¸³Æ®·Î ÁöÁ¤ÇÑ ¸®¼Ò½ºÀÇ URL°æ·ÎÀÌ´Ù. + action-type¿¡´Â Çڵ鷯³ª MIME content typeÀ» + »ç¿ëÇÒ ¼ö ÀÖ´Ù. ÀÌ Áö½Ã¾î´Â PATH_INFO¿Í + PATH_TRANSLATED CGI Ç¥ÁØ È¯°æº¯¼ö·Î ¿äûÇÑ + ¹®¼­ÀÇ URL°ú ÆÄÀÏ°æ·Î¸¦ Àü´ÞÇÑ´Ù. REDIRECT_HANDLER + º¯¼ö·Î ƯÁ¤ ¿äû¿¡ »ç¿ëÇÒ Çڵ鷯¸¦ Àü´ÞÇÑ´Ù.

+ +

¿¹Á¦

+ # ƯÁ¤ MIME content typeÀÇ ÆÄÀÏ ¿äû:
+ Action image/gif /cgi-bin/images.cgi
+
+ # ƯÁ¤ÇÑ È®ÀåÀÚ¸¦ °¡Áø ÆÄÀÏ
+ AddHandler my-file-type .xyz
+ Action my-file-type /cgi-bin/program.cgi
+

+ +

ù¹ø° ¿¹¿¡¼­ MIME content typeÀÌ image/gifÀÎ + ÆÄÀÏÀ» ¿äûÇϸé ÁöÁ¤ÇÑ cgi ½ºÅ©¸³Æ® /cgi-bin/images.cgi°¡ + ó¸®ÇÑ´Ù.

+ +

µÎ¹ø° ¿¹¿¡¼­ È®ÀåÀÚ°¡ .xyzÀÎ ÆÄÀÏÀ» ¿äûÇϸé + ÁöÁ¤ÇÑ cgi ½ºÅ©¸³Æ® /cgi-bin/program.cgi°¡ + ó¸®ÇÑ´Ù.

+

In the second example, requests for files with a file extension of + .xyz are handled instead by the specified cgi script + /cgi-bin/program.cgi.

+ +

¼±ÅÃÀûÀÎ virtual ¼öÁ¤ÀÚ´Â ¿äûÇÑ ÆÄÀÏÀÌ + ½ÇÁ¦·Î Á¸ÀçÇÏ´ÂÁö °Ë»çÇÏÁö ¾Êµµ·Ï ÇÑ´Ù. ¿¹¸¦ µé¾î, °¡»óÀÇ + À§Ä¡¿¡ Action Áö½Ã¾î¸¦ »ç¿ëÇÏ·Á´Â + °æ¿ì À¯¿ëÇÏ´Ù.

+ +

¿¹Á¦

+ <Location /news>
+ + SetHandler news-handler
+ Action news-handler /cgi-bin/news.cgi virtual
+ + </Location> +

+ +

Âü°í

+ +
+
top
+

Script Áö½Ã¾î

+ + + + + + +
¼³¸í:ƯÁ¤ ¿äû¸Þ¼­µå¿¡ ´ëÇØ CGI ½ºÅ©¸³Æ®¸¦ +»ç¿ëÇÑ´Ù.
¹®¹ý:Script method cgi-script
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory
»óÅÂ:Base
¸ðµâ:mod_actions
+

ÀÌ Áö½Ã¾î´Â ÆÄÀÏÀ» method ¸Þ¼­µå¸¦ »ç¿ëÇÏ¿© + ¿äûÇϸé cgi-script¸¦ ½ÇÇàÇÏ´Â ÇൿÀ» ¼­¹ö¿¡ + Ãß°¡ÇÑ´Ù. cgi-script´Â ScriptAlias³ª AddHandler¸¦ »ç¿ëÇÏ¿© CGI + ½ºÅ©¸³Æ®·Î ÁöÁ¤ÇÑ ¸®¼Ò½ºÀÇ URL°æ·ÎÀÌ´Ù. ÀÌ Áö½Ã¾î´Â + PATH_INFO¿Í PATH_TRANSLATED CGI + Ç¥ÁØ È¯°æº¯¼ö·Î ¿äûÇÑ ¹®¼­ÀÇ URL°ú ÆÄÀÏ°æ·Î¸¦ Àü´ÞÇÑ´Ù.

+ +
+ ¾î¶² ¸Þ¼­µå À̸§ÀÌ¶óµµ »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¸Þ¼­µå À̸§Àº + ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÑ´Ù. ±×·¡¼­ Script PUT°ú + Script putÀº ¿ÏÀüÈ÷ ´Ù¸£´Ù. +
+ +

Script ¸í·É¾î´Â ±âº»ÀûÀÎ Çൿ¸¸À» + ó¸®ÇÔÀ» ÁÖÀÇÇ϶ó. CGI ½ºÅ©¸³Æ®°¡ ºÒ¸®°Å³ª, ¿äûÇÑ ¸Þ¼­µå¸¦ + ¾Ë¾Æ¼­ ó¸®ÇÒ ¼ö ÀÖ´Â ¸®¼Ò½ºÀÇ °æ¿ì ±×´ë·Î ó¸®ÇÑ´Ù. + GET ¸Þ¼­µåÀÇ Script´Â + ÁúÀǾƱԸÕÆ®°¡ ÀÖÀ»¶§¸¸ (¿¹, foo.html?hi) »ç¿ëÇÔÀ» + ÁÖÀÇÇ϶ó. ÁúÀǾƱԸÕÆ®°¡ ¾ø´Ù¸é Á¤»óÀûÀ¸·Î ¿äûÀ» ó¸®ÇÑ´Ù.

+ +

¿¹Á¦

+ # <ISINDEX>½Ä °Ë»öÀ» À§ÇØ
+ Script GET /cgi-bin/search
+
+ # CGI PUT Çڵ鷯
+ Script PUT /~bob/put.cgi
+

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_alias.html b/docs/manual/mod/mod_alias.html new file mode 100644 index 00000000..cbf64ded --- /dev/null +++ b/docs/manual/mod/mod_alias.html @@ -0,0 +1,11 @@ +URI: mod_alias.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_alias.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_alias.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_alias.html.en b/docs/manual/mod/mod_alias.html.en new file mode 100644 index 00000000..0ac82977 --- /dev/null +++ b/docs/manual/mod/mod_alias.html.en @@ -0,0 +1,391 @@ + + + +mod_alias - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_alias

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Provides for mapping different parts of the host + filesystem in the document tree and for URL redirection
Status:Base
Module Identifier:alias_module
Source File:mod_alias.c
+

Summary

+ +

The directives contained in this module allow for manipulation + and control of URLs as requests arrive at the server. The + Alias and ScriptAlias directives are used to + map between URLs and filesystem paths. This allows for content + which is not directly under the DocumentRoot served as part of the web + document tree. The ScriptAlias directive has the + additional effect of marking the target directory as containing + only CGI scripts.

+ +

The Redirect + directives are used to instruct clients to make a new request with + a different URL. They are often used when a resource has moved to + a new location.

+ +

mod_alias is designed to handle simple URL + manipulation tasks. For more complicated tasks such as + manipulating the query string, use the tools provided by + mod_rewrite.

+ +
+ +
top
+
+

Order of Processing

+ +

Aliases and Redirects occuring in different contexts are processed +like other directives according to standard merging rules. But when multiple +Aliases or Redirects occur in the same context (for example, in the +same <VirtualHost> +section) they are processed in a particular order.

+ +

First, all Redirects are processed before Aliases are processed, +and therefore a request that matches a Redirect or RedirectMatch will never have Aliases +applied. Second, the Aliases and Redirects are processed in the order +they appear in the configuration files, with the first match taking +precedence.

+ +

For this reason, when two or more of these directives apply to the +same sub-path, you must list the most specific path first in order for +all the directives to have an effect. For example, the following +configuration will work as expected:

+ +

+Alias /foo/bar /baz
+Alias /foo /gaq +

+ +

But if the above two directives were reversed in order, the +/foo Alias +would always match before the /foo/bar Alias, so the latter directive would be +ignored.

+ +
+
top
+

Alias Directive

+ + + + + + +
Description:Maps URLs to filesystem locations
Syntax:Alias URL-path +file-path|directory-path
Context:server config, virtual host
Status:Base
Module:mod_alias
+ +

The Alias directive allows documents to + be stored in the local filesystem other than under the + DocumentRoot. URLs with a + (%-decoded) path beginning with url-path will be mapped + to local files beginning with directory-path.

+ +

Example:

+ Alias /image /ftp/pub/image +

+ +

A request for http://myserver/image/foo.gif would cause the + server to return the file /ftp/pub/image/foo.gif. Only complete + path segments are matched, so the above alias would not match a + request for http://myserver/imagefoo.gif. For more complex + matching using regular expressions, see the AliasMatch directive.

+ +

Note that if you include a trailing / on the + url-path then the server will require a trailing / in + order to expand the alias. That is, if you use Alias + /icons/ /usr/local/apache/icons/ then the url + /icons will not be aliased.

+ +

Note that you may need to specify additional <Directory> sections which + cover the destination of aliases. Aliasing occurs before + <Directory> sections + are checked, so only the destination of aliases are affected. + (Note however <Location> + sections are run through once before aliases are performed, so + they will apply.)

+ +

In particular, if you are creating an Alias to a + directory outside of your DocumentRoot, you may need to explicitly + permit access to the target directory.

+ +

Example:

+ Alias /image /ftp/pub/image
+ <Directory /ftp/pub/image>
+ + Order allow,deny
+ Allow from all
+ + </Directory> +

+ + +
+
top
+

AliasMatch Directive

+ + + + + + +
Description:Maps URLs to filesystem locations using regular +expressions
Syntax:AliasMatch regex +file-path|directory-path
Context:server config, virtual host
Status:Base
Module:mod_alias
+

This directive is equivalent to Alias, but makes use of + regular expressions, + instead of simple prefix matching. The + supplied regular expression is matched against the URL-path, and + if it matches, the server will substitute any parenthesized + matches into the given string and use it as a filename. For + example, to activate the /icons directory, one might + use:

+ +

+ AliasMatch ^/icons(.*) /usr/local/apache/icons$1 +

+ +
+
top
+

Redirect Directive

+ + + + + + + +
Description:Sends an external redirect asking the client to fetch +a different URL
Syntax:Redirect [status] URL-path +URL
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_alias
+

The Redirect directive maps an old URL into a new one by asking + the client to refetch the resource at the new location.

+ +

The old URL-path is a (%-decoded) path beginning with + a slash. A relative path is not allowed. The new URL + should be an absolute URL beginning with a scheme and hostname, + but a URL-path beginning with a slash may also be used, in which + case the scheme and hostname of the current server will be + added.

+ +

Then any request beginning with URL-Path will return a + redirect request to the client at the location of the target + URL. Additional path information beyond the matched + URL-Path will be appended to the target URL.

+ +

Example:

+ Redirect /service http://foo2.example.com/service +

+ +

If the client requests http://example.com/service/foo.txt, it + will be told to access http://foo2.example.com/service/foo.txt + instead. Only complete path segments are matched, so the above + example would not match a request for + http://example.com/servicefoo.txt. For more complex matching + using regular expressions, see the RedirectMatch directive.

+ + +

Note

Redirect directives take precedence over +Alias and ScriptAlias directives, irrespective of their ordering in +the configuration file.

+ +

If no status argument is given, the redirect will + be "temporary" (HTTP status 302). This indicates to the client + that the resource has moved temporarily. The status + argument can be used to return other HTTP status codes:

+ +
+
permanent
+ +
Returns a permanent redirect status (301) indicating that + the resource has moved permanently.
+ +
temp
+ +
Returns a temporary redirect status (302). This is the + default.
+ +
seeother
+ +
Returns a "See Other" status (303) indicating that the + resource has been replaced.
+ +
gone
+ +
Returns a "Gone" status (410) indicating that the + resource has been permanently removed. When this status is + used the URL argument should be omitted.
+
+ +

Other status codes can be returned by giving the numeric + status code as the value of status. If the status is + between 300 and 399, the URL argument must be present, + otherwise it must be omitted. Note that the status must be + known to the Apache code (see the function + send_error_response in http_protocol.c).

+ +

Example:

+ Redirect permanent /one http://example.com/two
+ Redirect 303 /three http://example.com/other +

+ + +
+
top
+

RedirectMatch Directive

+ + + + + + + +
Description:Sends an external redirect based on a regular expression match +of the current URL
Syntax:RedirectMatch [status] regex +URL
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_alias
+

This directive is equivalent to Redirect, but makes use of + regular expressions, + instead of simple prefix matching. The + supplied regular expression is matched against the URL-path, and + if it matches, the server will substitute any parenthesized + matches into the given string and use it as a filename. For + example, to redirect all GIF files to like-named JPEG files on + another server, one might use:

+ +

+ RedirectMatch (.*)\.gif$ http://www.anotherserver.com$1.jpg +

+ +
+
top
+

RedirectPermanent Directive

+ + + + + + + +
Description:Sends an external permanent redirect asking the client to fetch +a different URL
Syntax:RedirectPermanent URL-path URL
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_alias
+

This directive makes the client know that the Redirect is + permanent (status 301). Exactly equivalent to Redirect + permanent.

+ +
+
top
+

RedirectTemp Directive

+ + + + + + + +
Description:Sends an external temporary redirect asking the client to fetch +a different URL
Syntax:RedirectTemp URL-path URL
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_alias
+

This directive makes the client know that the Redirect is + only temporary (status 302). Exactly equivalent to + Redirect temp.

+ +
+
top
+

ScriptAlias Directive

+ + + + + + +
Description:Maps a URL to a filesystem location and designates the +target as a CGI script
Syntax:ScriptAlias URL-path +file-path|directory-path
Context:server config, virtual host
Status:Base
Module:mod_alias
+

The ScriptAlias directive has the same + behavior as the Alias + directive, except that in addition it marks the target directory + as containing CGI scripts that will be processed by mod_cgi's cgi-script handler. URLs with a + (%-decoded) path beginning with URL-path will be mapped + to scripts beginning with the second argument which is a full + pathname in the local filesystem.

+ +

Example:

+ ScriptAlias /cgi-bin/ /web/cgi-bin/ +

+ +

A request for http://myserver/cgi-bin/foo would cause the + server to run the script /web/cgi-bin/foo.

+ +
+
top
+

ScriptAliasMatch Directive

+ + + + + + +
Description:Maps a URL to a filesystem location using a regular expression +and designates the target as a CGI script
Syntax:ScriptAliasMatch regex +file-path|directory-path
Context:server config, virtual host
Status:Base
Module:mod_alias
+

This directive is equivalent to ScriptAlias, but makes use of + regular expressions, + instead of simple prefix matching. The + supplied regular expression is matched against the URL-path, + and if it matches, the server will substitute any parenthesized + matches into the given string and use it as a filename. For + example, to activate the standard /cgi-bin, one + might use:

+ +

+ ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1 +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_alias.html.ja.euc-jp b/docs/manual/mod/mod_alias.html.ja.euc-jp new file mode 100644 index 00000000..494a4680 --- /dev/null +++ b/docs/manual/mod/mod_alias.html.ja.euc-jp @@ -0,0 +1,387 @@ + + + +mod_alias - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_alias

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥Û¥¹¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î¤¤¤í¤¤¤í¤Ê°ã¤¦¾ì½ê¤ò + ¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼¤Ë¥Þ¥Ã¥×¤¹¤ëµ¡Ç½¤È¡¢ + URL ¤Î¥ê¥À¥¤¥ì¥¯¥È¤ò¹Ô¤Ê¤¦µ¡Ç½¤òÄ󶡤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:alias_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_alias.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥µ¡¼¥Ð¤Ë¥ê¥¯¥¨¥¹¥È¤¬ÅþÃ夷¤¿¤È¤­¤Ë + URL ¤ÎÁàºî¤äÀ©¸æ¤ò¤¹¤ë¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£Alias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È ScriptAlias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + URL ¤È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ñ¥¹¤ò¥Þ¥Ã¥×¤¹¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£¤³¤ì¤Ï + DocumentRoot + ¤Î²¼¤Ë¤Ê¤¤¥É¥­¥å¥á¥ó¥È¤ò¥¦¥§¥Ö¤Î¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼¤Î°ìÉô¤È¤·¤Æ + Á÷¤é¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ScriptAlias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤Ï¥Þ¥Ã¥×Àè¤Î¥Ç¥£¥ì¥¯¥È¥ê¤¬ CGI + ¥¹¥¯¥ê¥×¥È¤Î¤ß¤Ç¤¢¤ë¤³¤È¤ò¼¨¤¹¤È¤¤¤¦Äɲäθú²Ì¤¬¤¢¤ê¤Þ¤¹¡£ +

+ +

Redirect ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥¯¥é¥¤¥¢¥ó¥È¤Ë°ã¤Ã¤¿ + URL ¤Ë¿·¤·¤¤¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ë¤è¤¦¤Ë»Ø¼¨¤·¤Þ¤¹¡£¤³¤ì¤Ï¡¢ + ¥ê¥½¡¼¥¹¤¬¿·¤·¤¤¾ì½ê¤Ë°ÜÆ°¤·¤¿¤È¤­¤Ë¤è¤¯»ÈÍѤµ¤ì¤Þ¤¹¡£

+ +

mod_alias ¤Ï´Êñ¤Ê URL Áàºî¸þ¤±¤ËÀ߷פµ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤è¤êÊ£»¨¤ÊÁàºî¡¢¥¯¥¨¥ê¡¼¥¹¥È¥ê¥ó¥°¤ÎÁàºî¤Ë¤Ï¡¢mod_rewrite + ¤ÇÄ󶡤µ¤ì¤ë¥Ä¡¼¥ë¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+ +
top
+
+

½èÍý¤Î½çÈÖ

+ +

ÍÍ¡¹¤Ê¥³¥ó¥Æ¥­¥¹¥ÈÃæ¤Ç¤Î Alias ¤ä Redirect ¤Ï¾¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È +Ʊ¤¸¤è¤¦¤Ëɸ½à¤Î ¥Þ¡¼¥¸µ¬Â§ ¤Ë +½¾¤Ã¤Æ½èÍý¤µ¤ì¤Þ¤¹¡£¤¿¤À¤·¡¢(Î㤨¤Ð <VirtualHost> ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤Î¤è¤¦¤Ë) Ê£¿ô¤Î Alias ¤ä Redirect ¤¬ +Ʊ¤¸¥³¥ó¥Æ¥­¥¹¥ÈÃæ¤Ë¸½¤ì¤¿¾ì¹ç¤Ï·è¤Þ¤Ã¤¿½çÈ֤ǽèÍý¤µ¤ì¤Þ¤¹¡£

+ +

¤Þ¤º¡¢Alias ¤ÎÁ°¤Ë¤¹¤Ù¤Æ¤Î Redirect ¤¬½èÍý¤µ¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢Redirect ¤« RedirectMatch ¤Ë¥Þ¥Ã¥Á¤¹¤ë¥ê¥¯¥¨¥¹¥È¤Ë¤Ï +Alias ¤Ï·è¤·¤ÆŬÍѤµ¤ì¤Þ¤»¤ó¡£¼¡¤Ë¡¢Alias ¤È Redirect ¤¬ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î +½çÈÖ¤ËŬÍѤµ¤ì¡¢ºÇ½é¤Ë¥Þ¥Ã¥Á¤·¤¿¤â¤Î¤¬Í¥À褵¤ì¤Þ¤¹¡£

+ +

¤Ç¤¹¤«¤é¡¢Æó¤Ä°Ê¾å¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Æ±¤¸¥Ñ¥¹¤ËŬÍѤµ¤ì¤ë¤È¤­¤Ï¡¢ +¤¹¤Ù¤Æ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¸ú²Ì¤òÆÀ¤ë¤¿¤á¤Ë¤Ï¤è¤ê¾Ü¤·¤¤¥Ñ¥¹¤òÀè¤Ë½ñ¤¯ +ɬÍפ¬¤¢¤ê¤Þ¤¹¡£Î㤨¤Ð¡¢¼¡¤ÎÀßÄê¤Ï´üÂÔÄ̤ê¤ÎÆ°ºî¤ò¤·¤Þ¤¹:

+ +

+Alias /foo/bar /baz
+Alias /foo /gaq +

+ +

¤·¤«¤·¡¢¾åµ­¤ÎÆó¤Ä¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î½çÈÖ¤¬µÕ¤Ë¤Ê¤ë¤È¡¢ +/foo Alias ¤¬ +¾ï¤Ë /foo/bar Alias ¤è¤êÀè¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¤Î¤Ç¡¢¸å¼Ô¤Ï +·è¤·¤ÆŬÍѤµ¤ì¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +
+
top
+

Alias ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:URL ¤ò¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤˥ޥåפ¹¤ë
¹½Ê¸:Alias URL-path +file-path|directory-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_alias
+

Alias ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥É¥­¥å¥á¥ó¥È¤ò + ¥í¡¼¥«¥ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î + DocumentRoot + °Ê³°¤Î¾ì½ê¤ËÊݴɤ¹¤ë¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£ + URL ¤Î (% ¤¬Éü¹æ¤µ¤ì¤¿) ¥Ñ¥¹¤¬ url-path ¤Ç»Ï¤Þ¤ë¤â¤Î¤Ï + directory-filename + ¤Ç»Ï¤Þ¤ë¥í¡¼¥«¥ë¥Õ¥¡¥¤¥ë¤Ë¥Þ¥Ã¥×¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ Alias /image /ftp/pub/image +

+ +

http://myserver/image/foo.gif ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¡¢¥µ¡¼¥Ð¤Ï + ¥Õ¥¡¥¤¥ë /ftp/pub/image/foo.gif ¤òÊÖ¤·¤Þ¤¹¡£

+ +

¤â¤· url-path ¤ÎºÇ¸å¤Ë / + ¤ò½ñ¤¤¤¿¤Ê¤é¡¢¥µ¡¼¥Ð¤¬¥¨¥¤¥ê¥¢¥¹¤òŸ³«¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ºÇ¸å¤Î / + ¤¬É¬Íפˤʤ뤳¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤¹¤Ê¤ï¤Á¡¢Alias /icons/ + /usr/local/apache/icons/ ¤È¤¤¤¦¤â¤Î¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + /icons ¤È¤¤¤¦ url ¤Ï¥¨¥¤¥ê¥¢¥¹¤µ¤ì¤Þ¤»¤ó¡£

+ +

¥¨¥¤¥ê¥¢¥¹¤Î¹Ô¤­Àè¤ò´Þ¤ó¤Ç¤¤¤ë <Directory> + ¥»¥¯¥·¥ç¥ó¤òÄɲ乤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¥¨¥¤¥ê¥¢¥¹¤ÎŸ³«¤Ï <Directory> + ¥»¥¯¥·¥ç¥ó¤òÄ´¤Ù¤ëÁ°¤Ë¹Ô¤Ê¤ï¤ì¤Þ¤¹¤Î¤Ç¡¢ + ¥¨¥¤¥ê¥¢¥¹¤Î¹Ô¤­Àè¤Î <Directory> ¥»¥¯¥·¥ç¥ó¤Î¤ß + ¸ú²Ì¤¬¤¢¤ê¤Þ¤¹¡£ + (¤·¤«¤·¡¢<Location> + ¥»¥¯¥·¥ç¥ó¤Ï¥¨¥¤¥ê¥¢¥¹¤¬½èÍý¤µ¤ì¤ëÁ°¤Ë¼Â¹Ô¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢ + ¤³¤Á¤é¤ÏŬÍѤµ¤ì¤Þ¤¹¡£)

+ +

Æäˡ¢Alias ¤ò + DocumentRoot + ¥Ç¥£¥ì¥¯¥È¥ê¤Î³°Â¦¤ËÇÛÃÖ¤·¤¿¾ì¹ç¤Ï¡¢¹Ô¤­Àè¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ¹¤ë + ¥¢¥¯¥»¥¹¸¢¸Â¤òÌÀ¼¨Åª¤ËÀ©¸Â¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤Ç¤·¤ç¤¦¡£

+ +

Îã

+ Alias /image /ftp/pub/image
+ <Directory /ftp/pub/image>
+ + Order allow,deny
+ Allow from all
+ + </Directory> +

+ + +
+
top
+

AliasMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:Àµµ¬É½¸½¤ò»È¤Ã¤Æ URL ¤ò¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤˥ޥåפ¹¤ë
¹½Ê¸:AliasMatch regex +file-path|directory-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_alias
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Alias + ¤È¤Û¤È¤ó¤ÉƱ¤¸¤Ç¤¹¤¬¡¢´Êñ¤ÊÀèƬ¤«¤é¤Î¥Þ¥Ã¥Á¤ò¹Ô¤Ê¤¦¤Î¤Ç¤Ï¤Ê¤¯¡¢ + ɸ½àÀµµ¬É½¸½¤òÍøÍѤ·¤Þ¤¹¡£¤³¤³¤Ç»ØÄꤵ¤ì¤¿Àµµ¬É½¸½¤È URL ¤Î¥Ñ¥¹ + ¤¬¹ç¤¦¤«¤É¤¦¤«¤òÄ´¤Ù¡¢¹ç¤¦¾ì¹ç¤Ï³ç¸Ì¤Ç³ç¤é¤ì¤¿¥Þ¥Ã¥Á¤ò + Í¿¤¨¤é¤ì¤¿Ê¸»úÎó¤ÇÃÖ¤­´¹¤¨¡¢¤½¤ì¤ò¥Õ¥¡¥¤¥ë̾¤È¤·¤Æ»ÈÍѤ·¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢ + /icons ¥Ç¥£¥ì¥¯¥È¥ê¤ò»È¤¦ + ¤¿¤á¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ê¤â¤Î¤¬»ÈÍѤǤ­¤Þ¤¹:

+ +

+ AliasMatch ^/icons(.*) /usr/local/apache/icons$1 +

+ +
+
top
+

Redirect ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤¬°ã¤¦ URL ¤ò¼èÆÀ¤¹¤ë¤è¤¦¤Ë³°Éô¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤ò +Á÷¤ë
¹½Ê¸:Redirect [status] URL-path +URL
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_alias
+

Redirect ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¸Å¤¤ URL ¤ò¿·¤·¤¤¤â¤Î¤Ø¥Þ¥Ã¥×¤·¤Þ¤¹¡£ + ¿·¤·¤¤ URL ¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤µ¤ì¤Þ¤¹¡£¤½¤·¤Æ¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤Ï¿·¤·¤¤¥¢¥É¥ì¥¹¤ò¤â¤¦°ì²ó¼èÆÀ¤·¤è¤¦¤È¤·¤Þ¤¹¡£ + URL-path (% ¤¬Éü¹æ¤µ¤ì¤¿) ¥Ñ¥¹¤Ç»Ï¤Þ¤ë¥É¥­¥å¥á¥ó¥È¤Ø¤Î + ¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤Ï URL ¤Ç»Ï¤Þ¤ë¿·¤·¤¤ + (% ¤¬Éä¹æ²½¤µ¤ì¤¿) URL ¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¥¨¥é¡¼¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ Redirect /service http://foo2.bar.com/service +

+ +

¥¯¥é¥¤¥¢¥ó¥È¤Ï http://myserver/service/foo.txt + ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò¹Ô¤Ê¤¦¤È¡¢Âå¤ï¤ê¤Ë http://foo2.bar.com/service/foo.txt + ¤ò¥¢¥¯¥»¥¹¤¹¤ë¤è¤¦¤Ë¹ð¤²¤é¤ì¤Þ¤¹¡£

+ +

Ãí°Õ

ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î½çÈ֤˴ؤï¤é¤º¡¢ +Redirect ·Ï¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Alias +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È ScriptAlias ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤è¤ê¤âÍ¥À褵¤ì¤Þ¤¹¡£ +¤Þ¤¿¡¢.htaccess ¥Õ¥¡¥¤¥ë¤ä <Directory> +¥»¥¯¥·¥ç¥ó¤ÎÃæ¤Ç»È¤ï¤ì¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢URL-path +¤ÏÁêÂХѥ¹¤Ç¤Ï¤Ê¤¯¡¢´°Á´¤Ê URL ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

¤â¤· status °ú¿ô¤¬Í¿¤¨¤é¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢¥ê¥À¥¤¥ì¥¯¥È¤Ï + "temporary" (HTTP ¥¹¥Æ¡¼¥¿¥¹ 302) ¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤ì¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ë + ¥ê¥½¡¼¥¹¤¬°ì»þŪ¤Ë°ÜÆ°¤·¤¿¤È¤¤¤¦¤³¤È¤ò¼¨¤·¤Þ¤¹¡£Status + °ú¿ô¤Ï ¾¤Î HTTP ¤Î¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤òÊÖ¤¹¤¿¤á¤Ë»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +
+
permanent
+ +
±Êµ×¤Ë¥ê¥À¥¤¥ì¥¯¥È¤ò¤¹¤ë¥¹¥Æ¡¼¥¿¥¹ (301) ¤òÊÖ¤·¤Þ¤¹¡£ + ¤³¤ì¤Ï¥ê¥½¡¼¥¹¤¬±Êµ×¤Ë°ÜÆ°¤·¤¿¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
+ +
temp
+ +
°ì»þŪ¤Ê¥ê¥À¥¤¥ì¥¯¥È¥¹¥Æ¡¼¥¿¥¹ (302) + ¤òÊÖ¤·¤Þ¤¹¡£¤³¤ì¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤¹¡£
+ +
seeother
+ +
"See Other" ¥¹¥Æ¡¼¥¿¥¹ (303) ¤òÊÖ¤·¤Þ¤¹¡£ + ¤³¤ì¤Ï¥ê¥½¡¼¥¹¤¬Â¾¤Î¤â¤Î¤ÇÃÖ¤­´¹¤¨¤é¤ì¤¿¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£
+ +
gone
+ +
"Gone" ¥¹¥Æ¡¼¥¿¥¹ (410) ¤òÊÖ¤·¤Þ¤¹¡£¤³¤ì¤Ï¥ê¥½¡¼¥¹¤¬±Êµ×¤Ë + ºï½ü¤µ¤ì¤¿¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£¤³¤Î¥¹¥Æ¡¼¥¿¥¹¤¬»ÈÍѤµ¤ì¤¿¾ì¹ç¡¢ + url °ú¿ô¤Ï¾Êά¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
+
+ +

Status ¤ÎÃͤ˥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤ò¿ôÃͤÇÍ¿¤¨¤ë¤³¤È¤Ç + ¾¤Î¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤âÊÖ¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¥¹¥Æ¡¼¥¿¥¹¤¬ 300 ¤È 399 + ¤Î´Ö¤Ë¤¢¤ë¾ì¹ç¡¢url °ú¿ô¤Ï¸ºß¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£ + ¤½¤Î¾¤Î¾ì¹ç¤Ï¾Êά¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤¿¤À¤·¡¢ + ¥¹¥Æ¡¼¥¿¥¹¤Ï Apache ¤Î¥³¡¼¥É¤¬ÃΤäƤ¤¤ë¤â¤Î¤Ç¤¢¤ëɬÍפ¬¤¢¤ê¤Þ¤¹ + (http_protocol.c ¤Î´Ø¿ô send_error_response + ¤ò¸«¤Æ¤¯¤À¤µ¤¤)¡£

+

Îã:

+ +

Îã

+ Redirect permanent /one http://example.com/two
+ Redirect 303 /three http://example.com/other +

+ + +
+
top
+

RedirectMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¸½ºß¤Î URL ¤Ø¤ÎÀµµ¬É½¸½¤Î¥Þ¥Ã¥Á¤Ë¤è¤ê +³°Éô¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷¤ë
¹½Ê¸:RedirectMatch [status] regex +URL
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_alias
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Redirect + ¤È¤Û¤È¤ó¤ÉƱ¤¸¤Ç¤¹¤¬¡¢´Êñ¤ÊÀèƬ¤«¤é¤Î¥Þ¥Ã¥Á¤ò¹Ô¤Ê¤¦¤Î¤Ç¤Ï¤Ê¤¯¡¢ + ɸ½àÀµµ¬É½¸½¤òÍøÍѤ·¤Þ¤¹¡£¤³¤³¤Ç»ØÄꤵ¤ì¤¿Àµµ¬É½¸½¤È URL-path + ¤¬¹ç¤¦¤«¤É¤¦¤«¤òÄ´¤Ù¡¢¹ç¤¦¾ì¹ç¤Ï³ç¸Ì¤Ç³ç¤é¤ì¤¿¥Þ¥Ã¥Á¤ò + Í¿¤¨¤é¤ì¤¿Ê¸»úÎó¤ÇÃÖ¤­´¹¤¨¡¢¤½¤ì¤ò¥Õ¥¡¥¤¥ë̾¤È¤·¤Æ»ÈÍѤ·¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¡¢¤¹¤Ù¤Æ¤Î GIF ¥Õ¥¡¥¤¥ë¤òÊÌ¥µ¡¼¥Ð¤ÎƱÍͤÊ̾Á°¤Î JPEG + ¥Õ¥¡¥¤¥ë¤Ë¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤Ë¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ê¤â¤Î¤ò»È¤¤¤Þ¤¹: +

+ +

+ RedirectMatch (.*)\.gif$ http://www.anotherserver.com$1.jpg +

+ +
+
top
+

RedirectPermanent ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤¬°ã¤¦ URL ¤ò¼èÆÀ¤¹¤ë¤è¤¦¤Ë³°Éô¤Ø¤Î±Êµ×Ū¤Ê +¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷¤ë
¹½Ê¸:RedirectPermanent URL-path URL
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_alias
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ë Redirect ¤¬±Êµ×Ū¤Ê¤â¤Î + (¥¹¥Æ¡¼¥¿¥¹ 301) ¤Ç¤¢¤ë¤³¤È¤òÃΤ餻¤Þ¤¹¡£ + Redirect permanent ¤È¤Þ¤Ã¤¿¤¯Æ±¤¸¤Ç¤¹¡£

+ +
+
top
+

RedirectTemp ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤¬°ã¤¦ URL ¤ò¼èÆÀ¤¹¤ë¤è¤¦¤Ë³°Éô¤Ø¤Î°ì»þŪ¤Ê +¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷¤ë
¹½Ê¸:RedirectTemp URL-path URL
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_alias
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ë Redirect + ¤¬°ì»þŪ¤Ê¤â¤Î¤Ç¤¢¤ë (¥¹¥Æ¡¼¥¿¥¹ 302) ¤³¤È¤òÃΤ餻¤Þ¤¹¡£ + Redirect temp ¤È¤Þ¤Ã¤¿¤¯Æ±¤¸¤Ç¤¹¡£

+ +
+
top
+

ScriptAlias ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:URL ¤ò¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤إޥåפ·¡¢¥Þ¥Ã¥×Àè¤ò +CGI ¥¹¥¯¥ê¥×¥È¤Ë»ØÄê
¹½Ê¸:ScriptAlias URL-path +file-path|directory-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_alias
+

ScriptAlias ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Âоݥǥ£¥ì¥¯¥È¥ê¤Ë + mod_cgi ¤Î cgi-script + ¥Ï¥ó¥É¥é¤Ç½èÍý¤µ¤ì¤ë CGI + ¥¹¥¯¥ê¥×¥È¤¬¤¢¤ë¤³¤È¤ò¼¨¤¹°Ê³°¤Ï + Alias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈƱ¤¸¿¶¤ëÉñ¤¤¤ò¤·¤Þ¤¹¡£ + URL ¤Î (% ¤¬Éü¹æ¤µ¤ì¤¿) ¥Ñ¥¹¤¬ URL-path ¤Ç»Ï¤Þ¤ë¤â¤Î¤Ï + ¥í¡¼¥«¥ë¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î + ¥Õ¥ë¥Ñ¥¹¤Ç¤¢¤ëÆóÈÖÌܤΰú¿ô¤Ë¥Þ¥Ã¥×¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ ScriptAlias /cgi-bin/ /web/cgi-bin/ +

+ +

http://myserver/cgi-bin/foo + ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¥µ¡¼¥Ð¤Ï¥¹¥¯¥ê¥×¥È + /web/cgi-bin/foo ¤ò¼Â¹Ô¤·¤Þ¤¹¡£

+ +
+
top
+

ScriptAliasMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:URL ¤òÀµµ¬É½¸½¤ò»È¤Ã¤Æ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤إޥåפ·¡¢¥Þ¥Ã¥×Àè¤ò +CGI ¥¹¥¯¥ê¥×¥È¤Ë»ØÄê
¹½Ê¸:ScriptAliasMatch regex +file-path|directory-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_alias
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï ScriptAlias + ¤È¤Û¤È¤ó¤ÉƱ¤¸¤Ç¤¹¤¬¡¢´Êñ¤ÊÀèƬ¤«¤é¤Î¥Þ¥Ã¥Á¤ò¹Ô¤Ê¤¦¤Î¤Ç¤Ï¤Ê¤¯¡¢ + ɸ½àÀµµ¬É½¸½¤òÍøÍѤ·¤Þ¤¹¡£¤³¤³¤Ç»ØÄꤵ¤ì¤¿Àµµ¬É½¸½¤È URL-path + ¤¬¹ç¤¦¤«¤É¤¦¤«¤òÄ´¤Ù¡¢¹ç¤¦¾ì¹ç¤Ï³ç¸Ì¤Ç³ç¤é¤ì¤¿¥Þ¥Ã¥Á¤ò + Í¿¤¨¤é¤ì¤¿Ê¸»úÎó¤ÇÃÖ¤­´¹¤¨¡¢¤½¤ì¤ò¥Õ¥¡¥¤¥ë̾¤È¤·¤Æ»ÈÍѤ·¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¡¢É¸½à¤Î /cgi-bin + ¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ê¤â¤Î¤ò»È¤¤¤Þ¤¹: +

+ +

+ ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1 +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_alias.html.ko.euc-kr b/docs/manual/mod/mod_alias.html.ko.euc-kr new file mode 100644 index 00000000..5facf118 --- /dev/null +++ b/docs/manual/mod/mod_alias.html.ko.euc-kr @@ -0,0 +1,356 @@ + + + +mod_alias - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_alias

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:ÆÄÀϽýºÅÛÀÇ ´Ù¸¥ ºÎºÐµéÀ» ¹®¼­ °èÃþ±¸Á¶¿¡ Æ÷ÇÔÇÏ°í, + URL ¸®´ÙÀÌ·º¼ÇÀ» Á¦°øÇÑ´Ù
»óÅÂ:Base
¸ðµâ¸í:alias_module
¼Ò½ºÆÄÀÏ:mod_alias.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀÌ Á¦°øÇÏ´Â Áö½Ã¾îµéÀ» »ç¿ëÇÏ¿© ¼­¹ö°¡ ¿äûÀ» + ¹ÞÀ»¶§ URLÀ» ¼öÁ¤Çϰųª Á¶ÀÛÇÒ ¼ö ÀÖ´Ù. Alias¿Í ScriptAlias Áö½Ã¾î´Â URLÀ» + ÆÄÀϽýºÅÛ °æ·Î·Î ´ëÀÀÇÑ´Ù. ±×·¡¼­ DocumentRoot ¾Æ·¡¿¡ ¾ø´Â ³»¿ëÀ» + À¥À¸·Î ¼­ºñ½ºÇÒ ¼ö ÀÖ´Ù. ¶Ç, ScriptAlias Áö½Ã¾î´Â ÁöÁ¤ÇÑ + µð·ºÅ丮¿¡ CGI ½ºÅ©¸³Æ®¹Û¿¡ ¾ø´Ù°í ¾Ë¸°´Ù.

+ +

Redirect Áö½Ã¾î´Â + Ŭ¶óÀ̾ðÆ®¿¡°Ô ´Ù¸¥ URL·Î »õ·Î¿î ¿äûÀ» Çϵµ·Ï Áö½ÃÇÑ´Ù. + ÀÚ¿øÀ» »õ·Î¿î Àå¼Ò·Î ¿Å±ä °æ¿ì ÀÚÁÖ »ç¿ëÇÑ´Ù.

+ +

mod_alias´Â °£´ÜÇÑ URL Á¶ÀÛÀ» À§ÇØ + ¼³°èµÇ¾ú´Ù. ÁúÀǹ®ÀÚ¿­ Á¶ÀÛ°ú °°Àº º¹ÀâÇÑ ÀÛ¾÷Àº + mod_rewrite°¡ Á¦°øÇÏ´Â ±â´ÉÀ» ÀÌ¿ëÇ϶ó.

+ +
+ +
top
+
+

ó¸® ¼ø¼­

+ +

¼­·Î ´Ù¸¥ »ç¿ëÀå¼Ò¿¡¼­ Alias¿Í Redirect¸¦ »ç¿ëÇÏ¸é ´Ù¸¥ Áö½Ã¾î¿Í +°°ÀÌ Ç¥ÁØ °áÇÕ ¹æ¹ý¿¡ +µû¶ó ó¸®ÇÑ´Ù. ±×·¯³ª °°Àº »ç¿ëÀå¼Ò¿¡ (¿¹¸¦ µé¾î, °°Àº <VirtualHost> ¼½¼Ç¿¡) +Alias¿Í Redirect¸¦ »ç¿ëÇÏ¸é ¾Æ·¡ ¼ø¼­´ë·Î ó¸®ÇÑ´Ù.

+ +

¸ÕÀú ¸ðµç Redirect¸¦ ó¸®ÇÑ ÈÄ Alias¸¦ ó¸®ÇÑ´Ù. ±×·¡¼­ +Redirect³ª RedirectMatch¿¡ ÇØ´çÇÏ´Â ¿äûÀº +Àý´ë·Î AliasÇÏÁö ¾Ê´Â´Ù. ±×¸®°í Alias¿Í Redirect´Â ¼³Á¤ÆÄÀÏ¿¡¼­ +ù¹ø°·Î ³ª¿À´Â °ÍÀ» »ç¿ëÇÑ´Ù.

+ +

±×·¡¼­ ¿©·¯ Áö½Ã¾î°¡ µ¿ÀÏÇÑ ÇÏÀ§°æ·Î¿¡ ÇØ´çÇÏ´Â °æ¿ì ¸ðµç +Áö½Ã¾î¸¦ Àû¿ëÇϱâÀ§Çؼ­´Â °¡Àå »ó¼¼ÇÑ °æ·Î¸¦ ¸ÕÀú »ç¿ëÇØ¾ß ÇÑ´Ù. +¿¹¸¦ µé¾î, ´ÙÀ½ ¼³Á¤Àº ÀǵµÇÑ´ë·Î µ¿ÀÛÇÑ´Ù:

+ +

+Alias /foo/bar /baz
+Alias /foo /gaq +

+ +

±×·¯³ª À§ÀÇ µÎ Áö½Ã¾î ¼ø¼­¸¦ ¹Ù²Ù¸é /foo/bar +Alias ÀÌÀü¿¡ +/foo Alias¸¦ +Àû¿ëÇϹǷΠÇ×»ó µÎ¹ø° Áö½Ã¾î¸¦ ¹«½ÃÇÑ´Ù.

+ +
+
top
+

Alias Áö½Ã¾î

+ + + + + + +
¼³¸í:URLÀ» ƯÁ¤ ÆÄÀϽýºÅÛ Àå¼Ò·Î ´ëÀÀÇÑ´Ù
¹®¹ý:Alias URL-path +file-path|directory-path
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_alias
+ +

Alias Áö½Ã¾î¸¦ »ç¿ëÇϸé ÆÄÀϽýºÅÛ¿¡¼­ + DocumentRoot ¹Û¿¡ ÀÖ´Â + ¹®¼­µµ ¼­ºñ½ºÇÒ ¼ö ÀÖ´Ù. url-path·Î ½ÃÀÛÇÏ´Â + (%·Î ÀÎÄÚµùµÈ) URLÀ» directory-path·Î ½ÃÀÛÇÏ´Â + ÆÄÀÏ¿¡ ´ëÀÀÇÑ´Ù.

+ +

¿¹Á¦:

+ Alias /image /ftp/pub/image +

+ +

http://myserver/image/foo.gif¸¦ ¿äûÇÏ¸é ¼­¹ö´Â + /ftp/pub/image/foo.gif ÆÄÀÏÀ» ³Ñ°ÜÁØ´Ù.

+ +

url-path ³¡¿¡ /¸¦ Æ÷ÇÔÇϸé, URL ³¡¿¡ /¸¦ + »ç¿ëÇؾ߸¸ ¿µÇâÀÌ ÀÖÀ½À» ÁÖÀÇÇ϶ó. Áï, Alias /icons/ + /usr/local/apache/icons/ ¼³Á¤Àº url /icons¿Í + °ü°è°¡ ¾ø´Ù.

+ +

´ëÀÀÀÇ ´ë»óÀ» Æ÷ÇÔÇÏ´Â ¿©·¯ <Directory> ¼½¼ÇÀÌ + ÇÊ¿äÇÒÁöµµ ¸ð¸¥´Ù. ÀÌ Áö½Ã¾î´Â <Directory> ¼½¼ÇÀ» °Ë»çÇϱâ Àü¿¡ + ó¸®ÇϹǷÎ, ´ëÀÀÀÇ ´ë»ó¸¸ ¼½¼ÇÀÇ ¿µÇâÀ» ¹Þ´Â´Ù. (±×·¯³ª + <Location> + ¼½¼ÇÀº ÀÌ Áö½Ã¾î¸¦ ó¸®Çϱâ Àü¿¡ Çѹø¸¸ °Ë»çÇϹǷΠÁöÁ¤ÇÑ + URL ÀÌÇÏ Àüü¿¡ ¿µÇâÀ» ÁØ´Ù.)

+ +

ƯÈ÷ DocumentRoot + ¹Û¿¡ ÀÖ´Â µð·ºÅ丮·Î Alias¸¦ ¸¸µé¾ú´Ù¸é, Á÷Á¢ + ´ë»ó µð·ºÅ丮ÀÇ Á¢±ÙÀ» Çã¿ëÇØÁà¾ß ÇÑ´Ù.

+ +

¿¹Á¦:

+ Alias /image /ftp/pub/image
+ <Directory /ftp/pub/image>
+ + Order allow,deny
+ Allow from all
+ + </Directory> +

+ + +
+
top
+

AliasMatch Áö½Ã¾î

+ + + + + + +
¼³¸í:Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ¿© URLÀ» ÆÄÀϽýºÅÛ Àå¼Ò·Î +´ëÀÀÇÑ´Ù
¹®¹ý:AliasMatch regex +file-path|directory-path
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_alias
+

ÀÌ Áö½Ã¾î´Â Alias¿Í + °°Áö¸¸, °£´ÜÈ÷ URLÀÇ ¾ÕºÎºÐ¸¸ ºñ±³ÇÏ´Â ´ë½Å Ç¥ÁØ Á¤±ÔÇ¥Çö½ÄÀ» + »ç¿ëÇÑ´Ù. ÁöÁ¤ÇÑ Á¤±ÔÇ¥Çö½ÄÀ» URL °æ·Î¿Í ºñ±³ÇÏ¿© ¸Â´Ù¸é, + ¼­¹ö´Â °ýÈ£·Î ¹­Àº ºÎºÐÀ» ´ëüÇÏ¿© ÆÄÀϸíÀ¸·Î »ç¿ëÇÑ´Ù. + ¿¹¸¦ µé¾î, ´ÙÀ½°ú °°ÀÌ /icons µð·ºÅ丮¸¦ »ç¿ëÇÒ + ¼ö ÀÖ´Ù:

+ +

+ AliasMatch ^/icons(.*) /usr/local/apache/icons$1 +

+ +
+
top
+

Redirect Áö½Ã¾î

+ + + + + + + +
¼³¸í:Ŭ¶óÀ̾ðÆ®°¡ ´Ù¸¥ URL¿¡ Á¢¼ÓÇϵµ·Ï ¿äûÇÏ´Â ¿ÜºÎ +¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù
¹®¹ý:Redirect [status] URL-path +URL
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_alias
+

Redirect Áö½Ã¾î´Â ÀÌÀü URLÀ» »õ·Î¿î URL·Î ´ëÀÀÇÑ´Ù. + Ŭ¶óÀ̾ðÆ®¿¡°Ô »õ·Î¿î URLÀ» º¸³»°í, Ŭ¶óÀ̾ðÆ®´Â »õ·Î¿î + ÁÖ¼Ò·Î ´Ù½Ã Çѹø Á¢¼ÓÇÑ´Ù. (%·Î ÀÎÄÚµùµÈ) URL-path·Î + ½ÃÀÛÇÏ´Â ¿äûÀ» ¹ÞÀ¸¸é (%·Î ÀÎÄÚµùµÈ) URL·Î ½ÃÀÛÇÏ´Â + »õ·Î¿î URL·Î ¸®´ÙÀÌ·º¼Ç ¿À·ù¸¦ º¸³½´Ù.

+ +

¿¹Á¦:

+ Redirect /service http://foo2.bar.com/service +

+ +

Ŭ¶óÀ̾ðÆ®°¡ http://myserver/service/foo.txt¸¦ ¿äûÇϸé + ´ë½Å http://foo2.bar.com/service/foo.txt¿¡ Á¢±ÙÇ϶ó´Â ÀÀ´äÀ» + ¹Þ´Â´Ù.

+ +

ÁÖÀÇ

Redirect Áö½Ã¾î´Â ¼³Á¤ÆÄÀÏ¿¡¼­ +³ª¿À´Â ¼ø¼­¿Í °ü°è¾øÀÌ Alias¿Í ScriptAlias Áö½Ã¾îº¸´Ù ¿ì¼±¼øÀ§°¡ +³ô´Ù. ¶Ç, .htaccess ÆÄÀÏÀ̳ª <Directory> ¼½¼Ç¿¡¼­ »ç¿ëÇÏ´õ¶óµµ +URL-path¿¡´Â »ó´ë°æ·Î°¡ ¾Æ´Ï¶ó ¹Ýµå½Ã ¿ÏÀüÇÑ URLÀ» +»ç¿ëÇØ¾ß ÇÑ´Ù.

+ +

status ¾Æ±Ô¸ÕÆ®¸¦ ÁöÁ¤ÇÏÁö¾ÊÀ¸¸é, "Àӽà + (temporary)" (HTTP »óÅ 302) ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù. Áï, + Ŭ¶óÀ̾ðÆ®¿¡°Ô ÀÚ¿øÀ» Àӽ÷Π¿Å°å´Ù°í ¾Ë¸°´Ù. status + ¾Æ±Ô¸ÕÆ®¸¦ »ç¿ëÇÏ¿© ´Ù¸¥ HTTP »óÅÂÄڵ带 ¹ÝȯÇÒ ¼ö ÀÖ´Ù:

+ +
+
permanent
+ +
ÀÚ¿øÀ» ¿ÏÀüÈ÷ ¿Å°åÀ½À» ¶æÇÏ´Â ¿µ±¸ ¸®´ÙÀÌ·º¼Ç »óŸ¦ + (301) ¹ÝȯÇÑ´Ù.
+ +
temp
+ +
Àӽà ¸®´ÙÀÌ·º¼Ç »óŸ¦ (302) ¹ÝȯÇÑ´Ù. ±âº»°ªÀÌ´Ù.
+ +
seeother
+ +
ÀÚ¿øÀÌ ±³Ã¼µÇ¾úÀ½À» ¶æÇÏ´Â "ÂüÁ¶ (See Other)" »óŸ¦ + (303) ¹ÝȯÇÑ´Ù.
+ +
gone
+ +
ÀÚ¿øÀÌ ¿µ±¸È÷ »èÁ¦µÇ¾úÀ½À» ¶æÇÏ´Â "¼Ò¸ê (Gone)" »óŸ¦ + (410) ¹ÝȯÇÑ´Ù. ÀÌ »óŸ¦ »ç¿ëÇϸé URL ¾Æ±Ô¸ÕÆ®¸¦ + »ç¿ëÇÒ ¼ö ¾ø´Ù.
+
+ +

status¿¡ ¼ýÀÚ »óÅÂÄڵ带 »ç¿ëÇÏ¿© ´Ù¸¥ »óÅÂÄڵ嵵 + ¹ÝȯÇÒ ¼ö ÀÖ´Ù. »óÅ°¡ 300°ú 399 »çÀ̶ó¸é URL + ¾Æ±Ô¸ÕÆ®¸¦ »ç¿ëÇØ¾ß ÇÏ°í, ¾Æ´Ï¶ó¸é »ý·«ÇØ¾ß ÇÑ´Ù. ´Ü, ¾ÆÆÄÄ¡ + Äڵ忡 »óÅ°¡ Á¤ÀǵÇÀÖ¾î¾ß ÇÑ´Ù (http_protocol.cÀÇ + send_error_response ÇÔ¼ö Âü°í).

+ +

¿¹Á¦:

+ Redirect permanent /one http://example.com/two
+ Redirect 303 /three http://example.com/other +

+ + +
+
top
+

RedirectMatch Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÇöÀç URLÀÌ Á¤±ÔÇ¥Çö½Ä¿¡ ÇØ´çÇÏ¸é ¿ÜºÎ ¸®´ÙÀÌ·º¼ÇÀ» +º¸³½´Ù
¹®¹ý:RedirectMatch [status] regex +URL
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_alias
+

ÀÌ Áö½Ã¾î´Â Redirect¿Í °°Áö¸¸, °£´ÜÈ÷ + URLÀÇ ¾ÕºÎºÐ¸¸ ºñ±³ÇÏ´Â ´ë½Å Ç¥ÁØ Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÑ´Ù. + ÁöÁ¤ÇÑ Á¤±ÔÇ¥Çö½ÄÀ» URL °æ·Î¿Í ºñ±³ÇÏ¿© ¸Â´Ù¸é, ¼­¹ö´Â °ýÈ£·Î + ¹­Àº ºÎºÐÀ» ´ëüÇÏ¿© ÆÄÀϸíÀ¸·Î »ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î, ´ÙÀ½Àº + ¸ðµç GIF ÆÄÀÏ ¿äû¿¡ ´ëÇØ ´Ù¸¥ ¼­¹öÀÇ ºñ½ÁÇÑ À̸§À» °¡Áø + JPEG ÆÄÀÏ·Î ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù:

+ +

+ RedirectMatch (.*)\.gif$ http://www.anotherserver.com$1.jpg +

+ +
+
top
+

RedirectPermanent Áö½Ã¾î

+ + + + + + + +
¼³¸í:Ŭ¶óÀ̾ðÆ®°¡ ´Ù¸¥ URL¿¡ Á¢¼ÓÇϵµ·Ï ¿äûÇÏ´Â ¿ÜºÎ +¿µ±¸ ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù
¹®¹ý:RedirectPermanent URL-path URL
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_alias
+

ÀÌ Áö½Ã¾î´Â Ŭ¶óÀ̾ðÆ®¿¡°Ô ¸®´ÙÀÌ·º¼ÇÀÌ ¿µ±¸ÀûÀÓÀ» (»óÅ + 301) ¾Ë¸°´Ù. Redirect permanent¿Í Á¤È®È÷ °°´Ù.

+ +
+
top
+

RedirectTemp Áö½Ã¾î

+ + + + + + + +
¼³¸í:Ŭ¶óÀ̾ðÆ®°¡ ´Ù¸¥ URL¿¡ Á¢¼ÓÇϵµ·Ï ¿äûÇÏ´Â ¿ÜºÎ +Àӽà ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù
¹®¹ý:RedirectTemp URL-path URL
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_alias
+

ÀÌ Áö½Ã¾î´Â Ŭ¶óÀ̾ðÆ®¿¡°Ô ¸®´ÙÀÌ·º¼ÇÀÌ ÀÓ½ÃÀûÀÓÀ» (»óÅ + 302) ¾Ë¸°´Ù. Redirect temp¿Í Á¤È®È÷ °°´Ù.

+ +
+
top
+

ScriptAlias Áö½Ã¾î

+ + + + + + +
¼³¸í:URLÀ» ƯÁ¤ ÆÄÀϽýºÅÛ Àå¼Ò·Î ´ëÀÀÇÏ°í ´ë»óÀÌ CGI +½ºÅ©¸³Æ®¶ó°í ¾Ë¸°´Ù
¹®¹ý:ScriptAlias URL-path +file-path|directory-path
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_alias
+

ScriptAlias Áö½Ã¾î´Â Alias Áö½Ã¾î¿Í ºñ½ÁÇÏÁö¸¸, + Ãß°¡·Î ´ë»ó µð·ºÅ丮¿¡ mod_cgiÀÇ cgi-script + Çڵ鷯°¡ ó¸®ÇÒ CGI ½ºÅ©¸³Æ®°¡ ÀÖ´Ù°í ¾Ë¸°´Ù. + URL-path·Î ½ÃÀÛÇÏ´Â (%·Î ÀÎÄÚµùµÈ) URLÀ» ÆÄÀϽýºÅÛÀÇ + Àý´ë°æ·ÎÀÎ µÎ¹ø° ¾Æ±Ô¸ÕÆ®·Î ½ÃÀÛÇÏ´Â ½ºÅ©¸³Æ®¿¡ ´ëÀÀÇÑ´Ù.

+ +

¿¹Á¦:

+ ScriptAlias /cgi-bin/ /web/cgi-bin/ +

+ +

http://myserver/cgi-bin/foo¸¦ ¿äûÇÏ¸é ¼­¹ö´Â + /web/cgi-bin/foo ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÑ´Ù.

+ +
+
top
+

ScriptAliasMatch Áö½Ã¾î

+ + + + + + +
¼³¸í:Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ¿© URLÀ» ƯÁ¤ ÆÄÀϽýºÅÛ Àå¼Ò·Î +´ëÀÀÇÏ°í ´ë»óÀÌ CGI ½ºÅ©¸³Æ®¶ó°í ¾Ë¸°´Ù
¹®¹ý:ScriptAliasMatch regex +file-path|directory-path
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_alias
+

ÀÌ Áö½Ã¾î´Â ScriptAlias¿Í °°Áö¸¸, °£´ÜÈ÷ + URLÀÇ ¾ÕºÎºÐ¸¸ ºñ±³ÇÏ´Â ´ë½Å Ç¥ÁØ Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÑ´Ù. + ÁöÁ¤ÇÑ Á¤±ÔÇ¥Çö½ÄÀ» URL °æ·Î¿Í ºñ±³ÇÏ¿© ¸Â´Ù¸é, ¼­¹ö´Â °ýÈ£·Î + ¹­Àº ºÎºÐÀ» ´ëüÇÏ¿© ÆÄÀϸíÀ¸·Î »ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î, ´ÙÀ½°ú + °°ÀÌ Ç¥ÁØÀûÀÎ /cgi-binÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù:

+ +

+ ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1 +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_asis.html b/docs/manual/mod/mod_asis.html new file mode 100644 index 00000000..66ab1a74 --- /dev/null +++ b/docs/manual/mod/mod_asis.html @@ -0,0 +1,11 @@ +URI: mod_asis.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_asis.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_asis.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_asis.html.en b/docs/manual/mod/mod_asis.html.en new file mode 100644 index 00000000..c3dbd79c --- /dev/null +++ b/docs/manual/mod/mod_asis.html.en @@ -0,0 +1,112 @@ + + + +mod_asis - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_asis

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Sends files that contain their own +HTTP headers
Status:Base
Module Identifier:asis_module
Source File:mod_asis.c
+

Summary

+ +

This module provides the handler send-as-is + which causes Apache to send the document without adding most of + the usual HTTP headers.

+ +

This can be used to send any kind of data from the server, + including redirects and other special HTTP responses, without + requiring a cgi-script or an nph script.

+ +

For historical reasons, this module will also process any + file with the mime type httpd/send-as-is.

+
+

Directives

+

This module provides no + directives.

+

Topics

+

See also

+
+
top
+
+

Usage

+ +

In the server configuration file, associate files with the + send-as-is handler e.g.

+ +

AddHandler send-as-is asis

+ +

The contents of any file with a .asis extension + will then be sent by Apache to the client with almost no + changes. In particular, HTTP headers are derived from the file + itself according to mod_cgi rules, so an asis + file must include valid headers, and may also use the CGI + Status: header to determine the HTTP response code.

+ +

Here's an example of a file whose contents are sent as + is so as to tell the client that a file has + redirected.

+ + +

+ Status: 301 Now where did I leave that URL
+ Location: http://xyz.abc.com/foo/bar.html
+ Content-type: text/html
+
+ <html>
+ <head>
+ <title>Lame excuses'R'us</title>
+ </head>
+ <body>
+ <h1>Fred's exceptionally wonderful page has moved to
+ <a href="http://xyz.abc.com/foo/bar.html">Joe's</a> + site.
+ </h1>
+ </body>
+ </html> +

+ +

Notes:

+

The server always adds a Date: and Server: + header to the data returned to the client, so these should not be + included in the file. The server does not add a + Last-Modified header; it probably should.

+
+
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_asis.html.ja.euc-jp b/docs/manual/mod/mod_asis.html.ja.euc-jp new file mode 100644 index 00000000..9ae5b28a --- /dev/null +++ b/docs/manual/mod/mod_asis.html.ja.euc-jp @@ -0,0 +1,112 @@ + + + +mod_asis - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_asis

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¼«Ê¬ÍѤΠHTTP ¥Ø¥Ã¥À¤Î½ñ¤«¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤òÁ÷¿®¤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:asis_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_asis.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥Ï¥ó¥É¥é send-as-is + ¤òÄ󶡤·¤Þ¤¹¡£¤³¤Î¥Ï¥ó¥É¥é¤ÏÄ̾ï¤Î HTTP + ¥Ø¥Ã¥À¤ò¤Û¤È¤ó¤ÉÄɲ乤뤳¤È¤Ê¤¯¥É¥­¥å¥á¥ó¥È¤òÁ÷¿®¤·¤Þ¤¹¡£

+ +

¤³¤ì¤Ï¥µ¡¼¥Ð¤«¤é¤É¤ó¤Ê¼ïÎà¤Î¥Ç¡¼¥¿¤òÁ÷¤ë¤È¤­¤Ë¤â»ÈÍѤǤ­¤Þ¤¹¡£ + Cgi ¥¹¥¯¥ê¥×¥È¤ä nph ¥¹¥¯¥ê¥×¥È¤¬Ìµ¤¯¤Æ¤â¥ê¥À¥¤¥ì¥¯¥È¤ä¾¤ÎÆÃÊÌ¤Ê + HTTP ±þÅú¤òÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Îò»ËŪ¤ÊÍýͳ¤Ë¤è¤ê¡¢¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï mime ¥¿¥¤¥× + httpd/send-as-is ¤Î¥Õ¥¡¥¤¥ë¤â½èÍý¤·¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+

¥È¥Ô¥Ã¥¯

+

»²¾È

+
+
top
+
+

»ÈÍÑË¡

+ +

¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤Ç¡¢¥Õ¥¡¥¤¥ë¤È send-as-is + ¥Ï¥ó¥É¥é¤òÎ㤨¤Ð°Ê²¼¤Î¤è¤¦¤Ë´ØÏ¢ÉÕ¤±¤Æ¤¯¤À¤µ¤¤¡£

+ +

AddHandler send-as-is asis

+ +

³ÈÄ¥»Ò¤¬ .asis ¤Î¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ÎÆâÍÆ¤Ï Apache + ¤«¤é¥¯¥é¥¤¥¢¥ó¥È¤Ø¤Û¤È¤ó¤ÉÊѹ¹Ìµ¤¯Á÷¤é¤ì¤Þ¤¹¡£¥¯¥é¥¤¥¢¥ó¥È¤Ë¤Ï + HTTP ¥Ø¥Ã¥À¤¬É¬ÍפǤ¹¤Î¤Ç¡¢¥Õ¥¡¥¤¥ë¤Ë½ñ¤¯¤³¤È¤ò˺¤ì¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + Status: ¥Ø¥Ã¥À¤âɬÍפǤ¹¡£¥Ç¡¼¥¿¤Ï 3 ·å¤Î HTTP + ±þÅú¥³¡¼¥É¤È¡¢¤½¤Î¸å¤Ë¥Æ¥­¥¹¥È¥á¥Ã¥»¡¼¥¸¤¬Â³¤¤¤¿¤â¤Î¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

¤³¤ì¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ë¥Õ¥¡¥¤¥ë¤¬°ÜÆ°¤·¤¿¤³¤È¤òÃΤ餻¤ë¤¿¤á¤Ë + as is (¤½¤Î¤Þ¤Þ) ¤ÇÁ÷¤é¤ì¤ë¥Õ¥¡¥¤¥ë¤ÎÆâÍƤÎÎã¤Ç¤¹¡£ +

+ + +

+ Status: 301 Now where did I leave that URL
+ Location: http://xyz.abc.com/foo/bar.html
+ Content-type: text/html
+
+ <html>
+ <head>
+ <title>Lame excuses'R'us</title>
+ </head>
+ <body>
+ <h1>Fred's exceptionally wonderful page has moved to
+ <a href="http://xyz.abc.com/foo/bar.html">Joe's</a> + site.
+ </h1>
+ </body>
+ </html> +

+ +

Ãí°Õ

+

Ãí°Õ: ¥µ¡¼¥Ð¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤µ¤ì¤ë¥Ç¡¼¥¿¤Ë¾ï¤Ë Date: + ¤È Server: ¥Ø¥Ã¥À¤òÄɲä·¤Þ¤¹¤Î¤Ç¡¢ + ¤½¤ì¤é¤¬¥Õ¥¡¥¤¥ë¤Ë½ñ¤«¤ì¤Æ¤¤¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ + ¥µ¡¼¥Ð¤Ï Last-Modified ¥Ø¥Ã¥À¤òÄɲä·¤Þ¤»¤ó¡£ + ¤ª¤½¤é¤¯¤Ï¤½¤¦¤¹¤Ù¤­¤Ç¤·¤ç¤¦¤±¤ì¤É¡£

+
+
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_asis.html.ko.euc-kr b/docs/manual/mod/mod_asis.html.ko.euc-kr new file mode 100644 index 00000000..718f36be --- /dev/null +++ b/docs/manual/mod/mod_asis.html.ko.euc-kr @@ -0,0 +1,110 @@ + + + +mod_asis - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_asis

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:HTTP Çì´õ¸¦ Æ÷ÇÔÇÑ ÆÄÀÏÀ» º¸³½´Ù
»óÅÂ:Base
¸ðµâ¸í:asis_module
¼Ò½ºÆÄÀÏ:mod_asis.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ¾ÆÆÄÄ¡°¡ ÀϹÝÀûÀÎ HTTP Çì´õÀÇ ´ëºÎºÐÀ» Ãß°¡ÇÏÁö¾Ê°í + ¹®¼­¸¦ º¸³»µµ·Ï ¸¸µå´Â send-as-is Çڵ鷯¸¦ + Á¦°øÇÑ´Ù.

+ +

±×·¡¼­ ¼­¹ö´Â cgi ½ºÅ©¸³Æ®³ª nph ½ºÅ©¸³Æ®¸¦ »ç¿ëÇÏÁö¾Ê°íµµ + ¸®´ÙÀÌ·º¼Ç°ú ´Ù¸¥ Ưº°ÇÑ HTTP ÀÀ´ä µî ¾î¶² ÀÚ·áµµ º¸³¾ ¼ö + ÀÖ´Ù.

+ +

°ú°Å¿¡ ÀÌ ¸ðµâÀº mime typeÀÌ httpd/send-as-isÀÎ + ÆÄÀϵµ ó¸®Çß´Ù.

+
+

Áö½Ã¾îµé

+

ÀÌ ¸ðµâ¿¡´Â Áö½Ã¾î°¡ ¾ø½À´Ï´Ù.

+

ÁÖÁ¦

+

Âü°í

+
+
top
+
+

»ç¿ë¹ý

+ +

¼­¹ö ¼³Á¤ÆÄÀÏ¿¡¼­ ÆÄÀÏ°ú send-as-is Çڵ鷯¸¦ + ¿¹¸¦ µé¾î ´ÙÀ½°ú °°ÀÌ ¿¬°áÇÑ´Ù.

+ +

AddHandler send-as-is asis

+ +

¾ÆÆÄÄ¡´Â .asis È®ÀåÀÚ¸¦ °¡Áø ÆÄÀÏÀÇ ³»¿ëÀ» + °ÅÀÇ ¼öÁ¤ÇÏÁö¾Ê°í Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³½´Ù. Ŭ¶óÀ̾ðÆ®´Â HTTP + Çì´õ°¡ ÇÊ¿äÇϹǷΠ»©¸ÔÁö¸¶¶ó. Status: Çì´õµµ ÇÊ¿äÇÏ´Ù. ÀÌ + Çì´õÀÇ ³»¿ëÀº ¼¼ÀÚ¸® ¼ýÀÚÀÎ HTTP ÀÀ´äÄÚµå¿Í ±× µÚÀÇ ¹®±¸ÀÌ´Ù.

+ +

´ÙÀ½Àº ³»¿ë ±×´ë·Î Ŭ¶óÀ̾ðÆ®¿¡°Ô ÆÄÀÏÀÌ + ¸®´ÙÀ̷¼ǵǾú´Ù°í ¾Ë¸®´Â ÆÄÀÏÀÇ ¿¹ÀÌ´Ù.

+ + +

+ Status: 301 Now where did I leave that URL
+ Location: http://xyz.abc.com/foo/bar.html
+ Content-type: text/html
+
+ <html>
+ <head>
+ <title>Lame excuses'R'us</title>
+ </head>
+ <body>
+ <h1>Fred's exceptionally wonderful page has moved to
+ <a href="http://xyz.abc.com/foo/bar.html">Joe's</a> + site.
+ </h1>
+ </body>
+ </html> +

+ +

ÁÖÀÇ:

+

¼­¹ö´Â ÀڷḦ Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³¾¶§ Ç×»ó Date:¿Í + Server: Çì´õ¸¦ Ãß°¡ÇϹǷÎ, ÆÄÀÏ¿¡ ÀÌ Çì´õ°¡ + ÀÖÀ¸¸é ¾ÈµÈ´Ù. ¼­¹ö´Â Last-Modified Çì´õ¸¦ + Ãß°¡ÇÏÁö ¾Ê´Â´Ù. ±×·¡¼­ ¾Æ¸¶µµ ÀÌ Çì´õ´Â Æ÷ÇÔÇØ¾ß + ÇÑ´Ù.

+
+
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_basic.html b/docs/manual/mod/mod_auth_basic.html new file mode 100644 index 00000000..e93a9911 --- /dev/null +++ b/docs/manual/mod/mod_auth_basic.html @@ -0,0 +1,11 @@ +URI: mod_auth_basic.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_auth_basic.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_auth_basic.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_auth_basic.html.en b/docs/manual/mod/mod_auth_basic.html.en new file mode 100644 index 00000000..f2757605 --- /dev/null +++ b/docs/manual/mod/mod_auth_basic.html.en @@ -0,0 +1,127 @@ + + + +mod_auth_basic - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_auth_basic

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Basic authentication
Status:Base
Module Identifier:auth_basic_module
Source File:mod_auth_basic.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module allows the use of HTTP Basic Authentication to + restrict access by looking up users in the given providers. + HTTP Digest Authentication is provided by + mod_auth_digest. This module should + usually be combined with at least one authentication module + such as mod_authn_file and one authorization + module such as mod_authz_user.

+
+ + +
top
+

AuthBasicAuthoritative Directive

+ + + + + + + + +
Description:Sets whether authorization and authentication are passed to +lower level modules
Syntax:AuthBasicAuthoritative On|Off
Default:AuthBasicAuthoritative On
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_auth_basic
+

Normally, each authorization module listed in AuthBasicProvider will attempt + to verify the user, and if the user is not found in any provider, + access will be denied. Setting the + AuthBasicAuthoritative directive explicitly + to Off allows for both authentication and + authorization to be passed on to other non-provider-based modules + if there is no userID or rule + matching the supplied userID. This should only be necessary when + combining mod_auth_basic with third-party modules + that are not configured with the AuthBasicProvider + directive. When using such modules, the order of processing + is determined in the modules' source code and is not configurable.

+ +
+
top
+

AuthBasicProvider Directive

+ + + + + + + + +
Description:Sets the authentication provider(s) for this location
Syntax:AuthBasicProvider provider-name +[provider-name] ...
Default:AuthBasicProvider file
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_auth_basic
+

The AuthBasicProvider directive sets + which provider is used to authenticate the users for this location. + The default file provider is implemented + by the mod_authn_file module. Make sure + that the chosen provider module is present in the server.

+ +

Example

+ <Location /secure>
+ + AuthType basic
+ AuthName "private area"
+ AuthBasicProvider dbm
+ AuthDBMType SDBM
+ AuthDBMUserFile /www/etc/dbmpasswd
+ Require valid-user
+ + </Location> +

+ +

Providers are implemented by mod_authn_dbm, + mod_authn_file, mod_authn_dbd, + and mod_authnz_ldap.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_basic.html.ja.euc-jp b/docs/manual/mod/mod_auth_basic.html.ja.euc-jp new file mode 100644 index 00000000..e70ffd6f --- /dev/null +++ b/docs/manual/mod/mod_auth_basic.html.ja.euc-jp @@ -0,0 +1,135 @@ + + + +mod_auth_basic - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_auth_basic

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + + +
ÀâÌÀ:´ðËÜǧ¾Ú
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:auth_basic_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_auth_basic.c
¸ß´¹À­:Apache 2.1 °Ê¹ß
+

³µÍ×

+ +

Í¿¤¨¤é¤ì¤¿¥×¥í¥Ð¥¤¥À (ÌõÃí: ǧ¾Ú¤Ç¤Î¾È²ñ¤ò¹Ô¤¦Ì䤤¹ç¤ï¤»Àè) + ¤Ç¥æ¡¼¥¶¤ò¸¡º÷¤·¡¢HTTP ´ðËÜǧ¾Ú¤Ç¥¢¥¯¥»¥¹À©¸Â¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + HTTP ¥À¥¤¥¸¥§¥¹¥Èǧ¾Ú¤Ë¤Ä¤¤¤Æ¤Ï mod_auth_digest + ¤ÇÄ󶡤µ¤ì¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

AuthBasicAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:ǧ¾Ú¤È¾µÇ§¤ò¡¢¤è¤êÄ㤤¥ì¥Ù¥ë¤Î¥â¥¸¥å¡¼¥ë¤Ë°Ü¹Ô¤µ¤»¤ë¤«¤ò +ÀßÄꤷ¤Þ¤¹¡£
¹½Ê¸:AuthBasicAuthoritative On|Off
¥Ç¥Õ¥©¥ë¥È:AuthBasicAuthoritative On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_auth_basic
+

AuthBasicAuthoritative + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÌÀ¼¨Åª¤Ë Off¤ËÀßÄꤹ¤ë¤È¡¢ + Í¿¤¨¤é¤ì¤¿Ç§¾Ú¥æ¡¼¥¶ ID ¤ËÂФ·¤Æ¥æ¡¼¥¶ ID ¤¬¤Ê¤¤ + ¤Þ¤¿¤Ï¥ë¡¼¥ë¤¬¤Ê¤¤¾ì¹ç¤Ë¡¢ + ǧ¾Ú¤È¾µÇ§¤ÎξÊý¤Î¥×¥í¥»¥¹¤¬¡¢ + ¤è¤êÄ㤤¥ì¥Ù¥ë¤Î¥â¥¸¥å¡¼¥ë (modules.c ¥Õ¥¡¥¤¥ë¤ÇÄêµÁ) ¤Ë°Ü¹Ô¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£ + ¥æ¡¼¥¶ ID ¤¬¤¢¤ë¡¢¤«¤Ä¤Þ¤¿¤Ï¡¢¥ë¡¼¥ë¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + Ä̾ï¤Î¥Ñ¥¹¥ï¡¼¥É¤È¥¢¥¯¥»¥¹¥Á¥§¥Ã¥¯¤¬Å¬ÍѤµ¤ì¤Æ¡¢ + ǧ¾Ú¤Ë¼ºÇÔ¤¹¤ë¤È "Authentication Required" ±þÅú¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£

+ +

¤Ç¤¹¤«¤é¡¢Æó¤Ä°Ê¾å¤Î¥â¥¸¥å¡¼¥ë¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÇƱ°ì¤Î + ¥æ¡¼¥¶ ID ¤¬¸½¤ï¤ì¤¿¤ê¡¢ + ¤Þ¤¿¤Ï¡¢Àµ¤·¤¤ Require + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Æó¤Ä°Ê¾å¤Î¥â¥¸¥å¡¼¥ë¤Ç¸½¤ï¤ì¤¿¤ê¤·¤¿¾ì¹ç¤Ï¡¢ + °ì¤ÄÌܤΥ⥸¥å¡¼¥ë¤¬Ç§Äê¤ò¹Ô¤Ã¤Æ¡¢AuthAuthoritative + ÀßÄê¤Ë´Ø¤ï¤é¤º¡¢¥¢¥¯¥»¥¹¤Ï°Ü¹Ô¤·¤Þ¤»¤ó¡£

+ +

¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢À©¸æ¤Ï°Ü¹Ô¤·¤Þ¤»¤ó¡£¤½¤·¤Æ¡¢Ì¤ÃΤΥ桼¥¶ ID ¤ä + ¥ë¡¼¥ë¤¬¤¢¤Ã¤Æ¤â "Authentication Required" ±þÅú¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÀßÄꤷ¤Ê¤¤¤³¤È¤Ç¥·¥¹¥Æ¥à¤Î°ÂÁ´¤ò°Ý»ý¤Ç¤­¤Æ¡¢¤Þ¤¿¡¢ + NCSA ½àµò¤ÎµóÆ°¤ò¶¯À©¤Ç¤­¤Þ¤¹¡£

+ +
+
top
+

AuthBasicProvider ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¤³¤Î°ÌÃÖ¤ËÂФ¹¤ëǧ¾Ú¥×¥í¥Ð¥¤¥À¤òÀßÄꤷ¤Þ¤¹¡£
¹½Ê¸:AuthBasicProvider On|Off|provider-name +[provider-name] ...
¥Ç¥Õ¥©¥ë¥È:AuthBasicProvider On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_auth_basic
+

AuthBasicProvider ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¡¢ + ¤³¤Î°ÌÃÖ¤ËÂФ¹¤ë¥æ¡¼¥¶Ç§¾Ú¤ËÍѤ¤¤é¤ì¤ëǧ¾Ú¥×¥í¥Ð¥¤¥À¤òÀßÄꤷ¤Þ¤¹¡£ + On ¤ËÀßÄꤹ¤ë¤È¥Ç¥Õ¥©¥ë¥È¤Îǧ¾Ú¥×¥í¥Ð¥¤¥À + (file) ¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£file + ¥×¥í¥Ð¥¤¥À¤Ï mod_authn_file + ¥â¥¸¥å¡¼¥ë¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢ + ¤³¤Î¥â¥¸¥å¡¼¥ë¤¬¥µ¡¼¥Ð¤ËÆþ¤Ã¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Example

+ <Location /secure>
+ + AuthBasicProvider dbm
+ AuthDBMType SDBM
+ AuthDBMUserFile /www/etc/dbmpasswd
+ Require valid-user
+ + </Location> +

+ +

ǧ¾Ú¥×¥í¥Ð¥¤¥À¤Ë¤Ä¤¤¤Æ¤Ï + mod_authn_dbm ¤È mod_authn_file + ¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

Off ¤Ï¥×¥í¥Ð¥¤¥À¥ê¥¹¥È¤ò¥¯¥ê¥¢¤·¤Æ¡¢¥Ç¥Õ¥©¥ë¥È¤Î + ¾õÂÖ¤ËÌᤷ¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_basic.html.ko.euc-kr b/docs/manual/mod/mod_auth_basic.html.ko.euc-kr new file mode 100644 index 00000000..5068be68 --- /dev/null +++ b/docs/manual/mod/mod_auth_basic.html.ko.euc-kr @@ -0,0 +1,130 @@ + + + +mod_auth_basic - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_auth_basic

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:Basic authentication
»óÅÂ:Base
¸ðµâ¸í:auth_basic_module
¼Ò½ºÆÄÀÏ:mod_auth_basic.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ÇØ´ç Á¦°øÀÚ(provider)¸¦ »ç¿ëÇÏ¿© »ç¿ëÀÚº°·Î + Á¢±ÙÀ» Á¦ÇÑÇÏ´Â HTTP Basic AuthenticationÀ» Á¦°øÇÑ´Ù. + HTTP Digest AuthenticationÀº mod_auth_digest°¡ + Á¦°øÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

AuthBasicAuthoritative Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ÀÎÁõ°ú ±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ¿¡ ³Ñ°ÜÁÙÁö °áÁ¤ÇÑ´Ù
¹®¹ý:AuthBasicAuthoritative On|Off
±âº»°ª:AuthBasicAuthoritative On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Base
¸ðµâ:mod_auth_basic
+

AuthBasicAuthoritative Áö½Ã¾î¸¦ + Off·Î ¼³Á¤Çϸé ÁÖ¾îÁø »ç¿ëÀÚ ¾ÆÀ̵𿡠ÇØ´çÇÏ´Â + »ç¿ëÀÚ ¾ÆÀ̵𳪠±ÔÄ¢À» + ãÀ» ¼ö ¾ø´Â °æ¿ì ÀÎÁõ°ú ±ÇÇѺο© ¸ðµÎ¸¦ (modules.c + ÆÄÀÏ¿¡¼­ Á¤ÀÇÇÑ) Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁØ´Ù. ÁÖ¾îÁø »ç¿ëÀÚ + ¾ÆÀ̵𳪠±ÔÄ¢À» ã¾Ò´Ù¸é º¸Å붧¿Í °°ÀÌ ¾ÏÈ£¿Í Á¢±ÙÇã¿ë¿©ºÎ¸¦ + °Ë»çÇÏ°í, ½ÇÆÐÇϸé "Authentication Required (ÀÎÁõ ÇÊ¿ä)" + ÀÀ´äÀ» ÇÑ´Ù.

+ +

±×·¡¼­ ¿©·¯ ¸ðµâÀÇ µ¥ÀÌÅͺ£À̽º¿¡ »ç¿ëÀÚ ¾ÆÀ̵𰡠Àְųª + À¯È¿ÇÑ Require Áö½Ã¾î¸¦ + ¿©·¯ ¸ðµâ¿¡ Àû¿ëÇϸé, ù¹ø° ¸ðµâÀÌ »ç¿ëÀÚ¸¦ °Ë»çÇÏ°í, + AuthBasicAuthoritative ¼³Á¤°ú °ü°è¾øÀÌ + Á¢±ÙÀ» ³Ñ±âÁö¾Ê´Â´Ù.

+ +

±âº»ÀûÀ¸·Î Á¦¾î¸¦ ³Ñ±âÁö¾Ê°í, ¸ð¸£´Â »ç¿ëÀÚ ¾ÆÀ̵ð¿Í + ±ÔÄ¢ÀÎ °æ¿ì "Authentication Required (ÀÎÁõ ÇÊ¿ä)" ÀÀ´äÀ» + ÇÑ´Ù. ÀÌ Áö½Ã¾î¸¦ ¼³Á¤ÇÏÁö¾ÊÀ¸¸é ½Ã½ºÅÛÀÌ ¾ÈÀüÇÏ°Ô À¯ÁöµÇ¸ç, + NCSA À¥¼­¹ö¿Í °°ÀÌ µ¿ÀÛÇÑ´Ù.

+ +
+
top
+

AuthBasicProvider Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ÀÌ À§Ä¡¿¡ ´ëÇÑ ÀÎÁõÁ¦°øÀÚ¸¦ ÁöÁ¤ÇÑ´Ù
¹®¹ý:AuthBasicProvider On|Off|provider-name +[provider-name] ...
±âº»°ª:AuthBasicProvider On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Base
¸ðµâ:mod_auth_basic
+

AuthBasicProvider Áö½Ã¾î´Â ÀÌ + À§Ä¡¿¡¼­ »ç¿ëÀÚ¸¦ ÀÎÁõÇÒ Á¦°øÀÚ¸¦ ÁöÁ¤ÇÑ´Ù. °ªÀÌ + OnÀÌ¸é ±âº»Á¦°øÀÚ(file)¸¦ ¼±ÅÃÇÑ´Ù. + mod_authn_file ¸ðµâÀÌ file + Á¦°øÀÚ¸¦ ±¸ÇöÇϱ⶧¹®¿¡ ¼­¹ö¿¡ ÀÌ ¸ðµâÀÌ ÀÖ´ÂÁö È®ÀÎÇØ¾ß + ÇÑ´Ù.

+ +

¿¹Á¦

+ <Location /secure>
+ + AuthBasicProvider dbm
+ AuthDBMType SDBM
+ AuthDBMUserFile /www/etc/dbmpasswd
+ Require valid-user
+ + </Location> +

+ +

Á¦°øÀÚ´Â mod_authn_dbm°ú + mod_authn_fileÀ» Âü°íÇ϶ó.

+ +

°ªÀÌ OffÀ̸é Á¦°øÀÚ ¸ñ·ÏÀ» Áö¿ì°í ±âº»»óÅ·Π+ µ¹¾Æ°£´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_digest.html b/docs/manual/mod/mod_auth_digest.html new file mode 100644 index 00000000..ff515283 --- /dev/null +++ b/docs/manual/mod/mod_auth_digest.html @@ -0,0 +1,7 @@ +URI: mod_auth_digest.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_auth_digest.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_auth_digest.html.en b/docs/manual/mod/mod_auth_digest.html.en new file mode 100644 index 00000000..d6c676da --- /dev/null +++ b/docs/manual/mod/mod_auth_digest.html.en @@ -0,0 +1,329 @@ + + + +mod_auth_digest - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_auth_digest

+
+

Available Languages:  en  | + ko 

+
+ + + +
Description:User authentication using MD5 + Digest Authentication.
Status:Experimental
Module Identifier:auth_digest_module
Source File:mod_auth_digest.c
+

Summary

+ +

This module implements HTTP Digest Authentication. However, it + has not been extensively tested and is therefore marked + experimental.

+
+ +
top
+
+

Using Digest Authentication

+ +

Using MD5 Digest authentication is very simple. Simply set + up authentication normally, using AuthType Digest and + AuthDigestProvider + instead of the normal AuthType Basic and + AuthBasicProvider. + Then add a AuthDigestDomain directive containing at least the root + URI(s) for this protection space.

+ +

Appropriate user (text) files can be created using the + htdigest tool.

+ +

Example:

+ <Location /private/>
+ + AuthType Digest
+ AuthName "private area"
+ AuthDigestDomain /private/ http://mirror.my.dom/private2/
+
+ AuthDigestProvider file
+ AuthUserFile /web/auth/.digest_pw
+ Require valid-user
+ + </Location> +

+ +

Note

+

Digest authentication is more secure than Basic authentication, + but only works with supporting browsers. As of September 2004, major + browsers that support digest authentication include Amaya, Konqueror, MS Internet Explorer + for Mac OS X and Windows (although the Windows version fails when + used with a query string -- see "Working with MS + Internet Explorer" below for a workaround), Mozilla, + Netscape 7, Opera, and Safari. lynx does not + support digest authentication. Since digest authentication is not as + widely implemented as basic authentication, you should use it only + in environments where all users will have supporting browsers.

+
+
top
+
+

Working with MS Internet Explorer

+

The Digest authentication implementation in current Internet + Explorer for Windows implementations has known issues, namely that + GET requests with a query string are not RFC compliant. + There are a few ways to work around this issue.

+ +

+ The first way is to use POST requests instead of + GET requests to pass data to your program. This method + is the simplest approach if your application can work with this + limitation. +

+ +

Since version 2.0.51 Apache also provides a workaround in the + AuthDigestEnableQueryStringHack environment variable. + If AuthDigestEnableQueryStringHack is set for the + request, Apache will take steps to work around the MSIE bug and + remove the request URI from the digest comparison. Using this + method would look similar to the following.

+ +

Using Digest Authentication with MSIE:

+ BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On +

+ +

See the BrowserMatch + directive for more details on conditionally setting environment + variables

+
+
top
+

AuthDigestAlgorithm Directive

+ + + + + + + + +
Description:Selects the algorithm used to calculate the challenge and +response hashes in digest authentication
Syntax:AuthDigestAlgorithm MD5|MD5-sess
Default:AuthDigestAlgorithm MD5
Context:directory, .htaccess
Override:AuthConfig
Status:Experimental
Module:mod_auth_digest
+

The AuthDigestAlgorithm directive + selects the algorithm used to calculate the challenge and response + hashes.

+ +
+ MD5-sess is not correctly implemented yet. +
+ + +
+
top
+

AuthDigestDomain Directive

+ + + + + + + +
Description:URIs that are in the same protection space for digest +authentication
Syntax:AuthDigestDomain URI [URI] ...
Context:directory, .htaccess
Override:AuthConfig
Status:Experimental
Module:mod_auth_digest
+

The AuthDigestDomain directive allows + you to specify one or more URIs which are in the same protection + space (i.e. use the same realm and username/password info). + The specified URIs are prefixes; the client will assume + that all URIs "below" these are also protected by the same + username/password. The URIs may be either absolute URIs (i.e. + including a scheme, host, port, etc.) or relative URIs.

+ +

This directive should always be specified and + contain at least the (set of) root URI(s) for this space. + Omitting to do so will cause the client to send the + Authorization header for every request sent to this + server. Apart from increasing the size of the request, it may + also have a detrimental effect on performance if AuthDigestNcCheck is on.

+ +

The URIs specified can also point to different servers, in + which case clients (which understand this) will then share + username/password info across multiple servers without + prompting the user each time.

+ +
+
top
+

AuthDigestNcCheck Directive

+ + + + + + + +
Description:Enables or disables checking of the nonce-count sent by the +server
Syntax:AuthDigestNcCheck On|Off
Default:AuthDigestNcCheck Off
Context:server config
Status:Experimental
Module:mod_auth_digest
+
+ Not implemented yet. +
+ + +
+
top
+

AuthDigestNonceFormat Directive

+ + + + + + + +
Description:Determines how the nonce is generated
Syntax:AuthDigestNonceFormat format
Context:directory, .htaccess
Override:AuthConfig
Status:Experimental
Module:mod_auth_digest
+
Not implemented yet.
+ + +
+
top
+

AuthDigestNonceLifetime Directive

+ + + + + + + + +
Description:How long the server nonce is valid
Syntax:AuthDigestNonceLifetime seconds
Default:AuthDigestNonceLifetime 300
Context:directory, .htaccess
Override:AuthConfig
Status:Experimental
Module:mod_auth_digest
+

The AuthDigestNonceLifetime directive + controls how long the server nonce is valid. When the client + contacts the server using an expired nonce the server will send + back a 401 with stale=true. If seconds is + greater than 0 then it specifies the amount of time for which the + nonce is valid; this should probably never be set to less than 10 + seconds. If seconds is less than 0 then the nonce never + expires. +

+ +
+
top
+

AuthDigestProvider Directive

+ + + + + + + + +
Description:Sets the authentication provider(s) for this location
Syntax:AuthDigestProvider provider-name +[provider-name] ...
Default:AuthDigestProvider file
Context:directory, .htaccess
Override:AuthConfig
Status:Experimental
Module:mod_auth_digest
+

The AuthDigestProvider directive sets + which provider is used to authenticate the users for this location. + The default file provider is implemented + by the mod_authn_file module. Make sure + that the chosen provider module is present in the server.

+ +

See mod_authn_dbm, mod_authn_file, + and mod_authn_dbd for providers.

+ +
+
top
+

AuthDigestQop Directive

+ + + + + + + + +
Description:Determines the quality-of-protection to use in digest +authentication
Syntax:AuthDigestQop none|auth|auth-int [auth|auth-int]
Default:AuthDigestQop auth
Context:directory, .htaccess
Override:AuthConfig
Status:Experimental
Module:mod_auth_digest
+

The AuthDigestQop directive determines + the quality-of-protection to use. auth will + only do authentication (username/password); auth-int is + authentication plus integrity checking (an MD5 hash of the entity + is also computed and checked); none will cause the module + to use the old RFC-2069 digest algorithm (which does not include + integrity checking). Both auth and auth-int may + be specified, in which the case the browser will choose which of + these to use. none should only be used if the browser for + some reason does not like the challenge it receives otherwise.

+ +
+ auth-int is not implemented yet. +
+ +
+
top
+

AuthDigestShmemSize Directive

+ + + + + + + +
Description:The amount of shared memory to allocate for keeping track +of clients
Syntax:AuthDigestShmemSize size
Default:AuthDigestShmemSize 1000
Context:server config
Status:Experimental
Module:mod_auth_digest
+

The AuthDigestShmemSize directive defines + the amount of shared memory, that will be allocated at the server + startup for keeping track of clients. Note that the shared memory + segment cannot be set less than the space that is necessary for + tracking at least one client. This value is dependant on your + system. If you want to find out the exact value, you may simply + set AuthDigestShmemSize to the value of + 0 and read the error message after trying to start the + server.

+ +

The size is normally expressed in Bytes, but you + may let the number follow a K or an M to + express your value as KBytes or MBytes. For example, the following + directives are all equivalent:

+ +

+ AuthDigestShmemSize 1048576
+ AuthDigestShmemSize 1024K
+ AuthDigestShmemSize 1M +

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_auth_digest.html.ko.euc-kr b/docs/manual/mod/mod_auth_digest.html.ko.euc-kr new file mode 100644 index 00000000..543ef839 --- /dev/null +++ b/docs/manual/mod/mod_auth_digest.html.ko.euc-kr @@ -0,0 +1,321 @@ + + + +mod_auth_digest - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_auth_digest

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:MD5 Digest AuthenticationÀ» »ç¿ëÇÑ »ç¿ëÀÚÀÎÁõ.
»óÅÂ:Experimental
¸ðµâ¸í:auth_digest_module
¼Ò½ºÆÄÀÏ:mod_auth_digest.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº HTTP Digest AuthenticationÀ» ±¸ÇöÇÑ´Ù. + ±×·¯³ª ¸¹Àº Å×½ºÆ®¸¦ °ÅÄ¡Áö ¾ÊÀº ½ÇÇèÀûÀÎ ¸ðµâÀÌ´Ù.

+
+ +
top
+
+

Digest Authentication »ç¿ëÇϱâ

+ +

MD5 Digest authenticationÀº ¸Å¿ì ½±°Ô »ç¿ëÇÒ ¼ö ÀÖ´Ù. + AuthType Basic°ú AuthBasicProvider ´ë½Å + AuthType Digest¿Í AuthDigestProvider¸¦ + »ç¿ëÇÏ¿© °£´ÜÈ÷ ÀÎÁõÀ» ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ±×¸®°í ÃÖ¼ÒÇÑ º¸È£ÇÏ·Á´Â + ¿µ¿ªÀÇ ±âº» URIÀ» AuthDigestDomain Áö½Ã¾î¿¡ »ç¿ëÇÑ´Ù.

+ +

htdigest µµ±¸¸¦ + »ç¿ëÇÏ¿© »ç¿ëÀÚ (¹®ÀÚ)ÆÄÀÏÀ» ¸¸µé ¼ö ÀÖ´Ù.

+ +

¿¹Á¦:

+ <Location /private/>
+ + AuthType Digest
+ AuthName "private area"
+ AuthDigestDomain /private/ http://mirror.my.dom/private2/
+
+ AuthDigestProvider file
+ AuthUserFile /web/auth/.digest_pw
+ Require valid-user
+ + </Location> +

+ +

ÁÖÀÇ

+

Digest authenticationÀº Basic authenticationº¸´Ù ´õ + ¾ÈÀüÇÏÁö¸¸, ºê¶ó¿ìÀú°¡ Áö¿øÇØ¾ß ÇÑ´Ù. 2002³â 11¿ù ÇöÀç digest + authenticationÀ» Áö¿øÇÏ´Â ºê¶ó¿ìÀú¿¡´Â Amaya, Konqueror, (Windows¿ëÀº + ÁúÀǹ®ÀÚ¿­°ú ÇÔ²² »ç¿ëÇÏ¸é ¾ÈµÇÁö¸¸ - ÇØ°á¹æ¹ýÀº ¾Æ·¡ "MS Internet Explorer ¹®Á¦ ÇØ°áÇϱâ"¸¦ Âü°í) + Mac OS X¿Í Windows¿ë MS Internet + Explorer, Mozilla, + Netscape ¹öÀü 7, Opera, + Safari µîÀÌ ÀÖ´Ù. + lynx´Â digest authenticationÀ» + Áö¿øÇÏÁö ¾Ê´Â´Ù. digest authenticationÀÌ + basic authentication ¸¸Å­ ³Î¸® ±¸ÇöµÇÁö ¾Ê¾Ò±â¶§¹®¿¡ ¸ðµç + »ç¿ëÀÚ°¡ Áö¿øÇÏ´Â ºê¶ó¿ìÀú¸¦ »ç¿ëÇÏ´Â °æ¿ì¿¡¸¸ »ç¿ëÇØ¾ß + ÇÑ´Ù.

+
+
top
+
+

MS Internet Explorer ¹®Á¦ ÇØ°áÇϱâ

+

ÇöÀç Windows¿ë Internet Explorer´Â Digest authentication + »ç¿ë½Ã ÁúÀǹ®ÀÚ¿­ÀÌ ÀÖ´Â GET ¿äûÀ» RFC¿Í ´Ù¸£°Ô + ó¸®ÇÏ´Â ¹®Á¦°¡ ÀÖ´Ù. ¸î°¡Áö ¹æ¹ýÀ¸·Î ÀÌ ¹®Á¦¸¦ ÇØ°áÇÒ ¼ö + ÀÖ´Ù.

+ +

+ ù¹ø°´Â ÇÁ·Î±×·¥¿¡ ÀڷḦ ³Ñ°ÜÁÖ±âÀ§ÇØ GET + ´ë½Å POST ¿äûÀ» »ç¿ëÇÏ´Â ¹æ¹ýÀÌ´Ù. ÀÌ ¹æ¹ýÀÌ + °¡´ÉÇÏ´Ù¸é °¡Àå °£´ÜÇÑ ÇØ°áÃ¥ÀÌ´Ù. +

+ +

¶Ç, ¾ÆÆÄÄ¡ 2.0.51ºÎÅÍ AuthDigestEnableQueryStringHack + ȯ°æº¯¼ö¸¦ Á¦°øÇÏ¿© ¹®Á¦¸¦ ÇØ°áÇÑ´Ù. ¿äû¿¡ + AuthDigestEnableQueryStringHackÀ» ¼³Á¤Çϸé + ¾ÆÆÄÄ¡´Â MSIE ¹ö±×¸¦ ÇÇÇØ°¥ Á¶Ä¡¸¦ ÃëÇÏ°í ¿äû URI¸¦ digest + ºñ±³¿¡¼­ Á¦¿ÜÇÑ´Ù. ÀÌ ¹æ¹ýÀº ´ÙÀ½°ú °°ÀÌ »ç¿ëÇÑ´Ù.

+ +

MSIE¿¡¼­ Digest Authentication »ç¿ëÇϱâ:

+ BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On +

+ +

¼±ÅÃÀûÀΠȯ°æº¯¼ö ¼³Á¤¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ³»¿ëÀº BrowserMatch Áö½Ã¾î¸¦ + Âü°íÇ϶ó.

+
+
top
+

AuthDigestAlgorithm Áö½Ã¾î

+ + + + + + + + +
¼³¸í:digest authentication¿¡¼­ challenge¿Í response +hash¸¦ °è»êÇÏ´Â ¾Ë°í¸®ÁòÀ» ¼±ÅÃÇÑ´Ù
¹®¹ý:AuthDigestAlgorithm MD5|MD5-sess
±âº»°ª:AuthDigestAlgorithm MD5
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Experimental
¸ðµâ:mod_auth_digest
+

AuthDigestAlgorithm Áö½Ã¾î´Â + challenge¿Í response hash¸¦ °è»êÇÏ´Â ¾Ë°í¸®ÁòÀ» ¼±ÅÃÇÑ´Ù.

+ +
+ MD5-sess´Â ¾ÆÁ÷ ¿ÏÀüÈ÷ ±¸ÇöµÇÁö ¾Ê¾Ò´Ù. +
+ + +
+
top
+

AuthDigestDomain Áö½Ã¾î

+ + + + + + + +
¼³¸í:digest authentication¿¡¼­ °°Àº º¸È£¿µ¿ª¿¡ ¼ÓÇÏ´Â +URIµé
¹®¹ý:AuthDigestDomain URI [URI] ...
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Experimental
¸ðµâ:mod_auth_digest
+

AuthDigestDomain Áö½Ã¾î´Â °°Àº + º¸È£¿µ¿ª¿¡ ÀÖ´Â (¿¹¸¦ µé¾î °°Àº ¿µ¿ª°ú »ç¿ëÀÚ¸í/¾ÏÈ£ + Á¤º¸¸¦ »ç¿ëÇÏ´Â) URIµéÀ» ÁöÁ¤ÇÑ´Ù. ÁöÁ¤ÇÑ URI´Â Á¢µÎ»ç·Î + »ç¿ëÇÑ´Ù. Ŭ¶óÀ̾ðÆ®´Â URI "¾Æ·¡" ¸ðµÎ¸¦ + °°Àº »ç¿ëÀÚ¸í/¾ÏÈ£·Î º¸È£ÇÑ´Ù°í °¡Á¤ÇÑ´Ù. URI´Â + (Áï, ½ºÅ´(scheme), È£½ºÆ®, Æ÷Æ® µîÀ» Æ÷ÇÔÇÏ´Â) + Àý´ë URLÀ̰ųª »ó´ë URIÀÌ´Ù.

+ +

ÀÌ Áö½Ã¾î´Â Ç×»ó ÁöÁ¤ÇØ¾ß Çϸç, ÃÖ¼ÒÇÑ ¿µ¿ªµéÀÇ + ±âº» URI(µé)¸¦ Æ÷ÇÔÇØ¾ß ÇÑ´Ù. »ý·«Çϸé Ŭ¶óÀ̾ðÆ®´Â + ÀÌ ¼­¹ö·Î º¸³»´Â ¸ðµç ¿äû¿¡ Authorization Çì´õ¸¦ + Æ÷ÇÔÇÑ´Ù. ±×·¯¸é ¿äûÀÇ Å©±â°¡ Ä¿Áö¸ç, AuthDigestNcCheck¸¦ + »ç¿ëÇÑ´Ù¸é ¼º´É¿¡ ³ª»Û ¿µÇâÀ» ÁÙ ¼ö ÀÖ´Ù.

+ +

´Ù¸¥ ¼­¹öÀÇ URI¸¦ ÁöÁ¤Çϸé, (À̸¦ ÀÌÇØÇÏ´Â) Ŭ¶óÀ̾ðÆ®´Â + ¿©·¯ ¼­¹ö¸¶´Ù ¸Å¹ø »ç¿ëÀÚ¿¡°Ô ¹¯Áö¾Ê°í °°Àº »ç¿ëÀÚ¸í/¾ÏÈ£¸¦ + »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +
+
top
+

AuthDigestNcCheck Áö½Ã¾î

+ + + + + + + +
¼³¸í:¼­¹ö°¡ º¸³»´Â nonce-count¸¦ °Ë»çÇÒÁö ¿©ºÎ
¹®¹ý:AuthDigestNcCheck On|Off
±âº»°ª:AuthDigestNcCheck Off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_auth_digest
+
+ ¾ÆÁ÷ ±¸ÇöµÇÁö ¾Ê¾Ò´Ù. +
+ + +
+
top
+

AuthDigestNonceFormat Áö½Ã¾î

+ + + + + + + +
¼³¸í:nonce¸¦ ¸¸µå´Â ¹æ¹ýÀ» °áÁ¤ÇÑ´Ù
¹®¹ý:AuthDigestNonceFormat format
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Experimental
¸ðµâ:mod_auth_digest
+
¾ÆÁ÷ ±¸ÇöµÇÁö ¾Ê¾Ò´Ù.
+ + +
+
top
+

AuthDigestNonceLifetime Áö½Ã¾î

+ + + + + + + + +
¼³¸í:¼­¹ö nonce°¡ À¯È¿ÇÑ ±â°£
¹®¹ý:AuthDigestNonceLifetime seconds
±âº»°ª:AuthDigestNonceLifetime 300
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Experimental
¸ðµâ:mod_auth_digest
+

AuthDigestNonceLifetime Áö½Ã¾î´Â + ¼­¹ö nonce°¡ À¯È¿ÇÑ ±â°£À» Á¶ÀýÇÑ´Ù. Ŭ¶óÀ̾ðÆ®°¡ ¸¸±âµÈ + nonce¸¦ °¡Áö°í ¼­¹ö¿¡ Á¢±ÙÇÏ¸é ¼­¹ö´Â stale=true¿Í + ÇÔ²² 401À» ¹ÝȯÇÑ´Ù. seconds°¡ 0º¸´Ù Å©¸é nonce°¡ + À¯È¿ÇÑ ±â°£À» ÁöÁ¤ÇÑ´Ù. ¾Æ¸¶µµ 10 Ãʺ¸´Ù ÀÛ°Ô ¼³Á¤ÇÏ¸é ¾ÈµÈ´Ù. + seconds°¡ 0º¸´Ù ÀÛÀ¸¸é nonce´Â ¿µ¿øÈ÷ ¸¸±âµÇÁö + ¾Ê´Â´Ù. +

+ +
+
top
+

AuthDigestProvider Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ÀÌ À§Ä¡¿¡ ´ëÇÑ ÀÎÁõÁ¦°øÀÚ¸¦ ÁöÁ¤ÇÑ´Ù
¹®¹ý:AuthDigestProvider On|Off|provider-name +[provider-name] ...
±âº»°ª:AuthDigestProvider On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Experimental
¸ðµâ:mod_auth_digest
+

AuthDigestProvider Áö½Ã¾î´Â ÀÌ + À§Ä¡¿¡¼­ »ç¿ëÀÚ¸¦ ÀÎÁõÇÒ Á¦°øÀÚ¸¦ ÁöÁ¤ÇÑ´Ù. °ªÀÌ + OnÀÌ¸é ±âº»Á¦°øÀÚ(file)¸¦ »ç¿ëÇÑ´Ù. + mod_authn_file ¸ðµâÀÌ file + Á¦°øÀÚ¸¦ ±¸ÇöÇϱ⶧¹®¿¡ ¼­¹ö¿¡ ÀÌ ¸ðµâÀÌ ÀÖ´ÂÁö È®ÀÎÇØ¾ß + ÇÑ´Ù.

+ +

Á¦°øÀÚ´Â mod_authn_dbm°ú + mod_authn_fileÀ» Âü°íÇ϶ó.

+ +

°ªÀÌ OffÀ̸é Á¦°øÀÚ ¸ñ·ÏÀ» Áö¿ì°í ±âº»»óÅ·Π+ µ¹¾Æ°£´Ù.

+ +
+
top
+

AuthDigestQop Áö½Ã¾î

+ + + + + + + + +
¼³¸í:digest authentication°¡ »ç¿ëÇÒ +º¸È£¼öÁØ(quality-of-protection)À» ÁöÁ¤ÇÑ´Ù.
¹®¹ý:AuthDigestQop none|auth|auth-int [auth|auth-int]
±âº»°ª:AuthDigestQop auth
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Experimental
¸ðµâ:mod_auth_digest
+

AuthDigestQop Áö½Ã¾î´Â + º¸È£¼öÁØ(quality-of-protection)À» ÁöÁ¤ÇÑ´Ù. + auth´Â (»ç¿ëÀÚ¸í/¾ÏÈ£) ÀÎÁõ¸¸ ÇÏ°í, + auth-int´Â ÀÎÁõ°ú ¿Ï°á¼º °Ë»ç¸¦ (MD5 Çؽ¬µµ + °è»êÇÏ¿© °Ë»çÇÑ´Ù) ÇÑ´Ù. noneÀº (¿Ï°á¼º °Ë»ç¸¦ + ÇÏÁö¾Ê´Â) ¿À·¡µÈ RFC-2069 digest ¾Ë°í¸®ÁòÀ» »ç¿ëÇÑ´Ù. + auth¿Í auth-int¸¦ ¸ðµÎ ÁöÁ¤ÇÒ + ¼ö ÀÖ´Ù. ÀÌ °æ¿ì ºê¶ó¿ìÀú´Â ¾î¶² °ÍÀ» »ç¿ëÇÒÁö ¼±ÅÃÇÑ´Ù. + ºê¶ó¿ìÀú°¡ ¾î´ø ÀÌÀ¯¿¡¼­°Ç challenge¸¦ ÁÁ¾ÆÇÏÁö ¾Ê´Â´Ù¸é + noneÀ» »ç¿ëÇØ¾ß ÇÑ´Ù.

+ +
+ auth-int´Â ¾ÆÁ÷ ±¸ÇöµÇÁö ¾Ê¾Ò´Ù. +
+ +
+
top
+

AuthDigestShmemSize Áö½Ã¾î

+ + + + + + + +
¼³¸í:Ŭ¶óÀ̾ðÆ®¸¦ ÃßÀûÇϱâÀ§ÇØ ÇÒ´çÇÏ´Â °øÀ¯¸Þ¸ð¸®·®
¹®¹ý:AuthDigestShmemSize size
±âº»°ª:AuthDigestShmemSize 1000
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_auth_digest
+

AuthDigestShmemSize Áö½Ã¾î´Â + Ŭ¶óÀ̾ðÆ®¸¦ ÃßÀûÇϱâÀ§ÇØ ¼­¹ö°¡ ½ÃÀÛÇÒ¶§ ÇÒ´çÇÏ´Â + °øÀ¯¸Þ¸ð¸®·®À» Á¤ÀÇÇÑ´Ù. °øÀ¯¸Þ¸ð¸®´Â ÃÖ¼ÒÇÑ ÇϳªÀÇ + Ŭ¶óÀ̾ðÆ®¸¦ ÃßÀûÇϱâÀ§ÇØ ÇÊ¿äÇÑ °ø°£º¸´Ù ÀÛÀ» ¼ö ¾øÀ½À» + ÁÖÀÇÇ϶ó. ÀÌ °ªÀº ½Ã½ºÅÛ¿¡ µû¶ó ´Ù¸£´Ù. Á¤È®ÇÑ °ªÀ» ¾Ë·Á¸é + AuthDigestShmemSize¸¦ 0À¸·Î + ¼³Á¤ÇÏ°í ¼­¹ö¸¦ ½ÃÀÛÇÑÈÄ ¿À·ù¹®À» Âü°íÇ϶ó.

+ +

size´Â º¸Åë ¹ÙÀÌÆ® ´ÜÀ§ÀÌÁö¸¸, µÚ¿¡ + K³ª MÀ» »ç¿ëÇÏ¿© KBytes³ª MBytes¸¦ + ³ªÅ¸³¾ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, ´ÙÀ½ Áö½Ã¾îµéÀº ¸ðµÎ °°´Ù:

+ +

+ AuthDigestShmemSize 1048576
+ AuthDigestShmemSize 1024K
+ AuthDigestShmemSize 1M +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_alias.html b/docs/manual/mod/mod_authn_alias.html new file mode 100644 index 00000000..6abb4b34 --- /dev/null +++ b/docs/manual/mod/mod_authn_alias.html @@ -0,0 +1,3 @@ +URI: mod_authn_alias.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_authn_alias.html.en b/docs/manual/mod/mod_authn_alias.html.en new file mode 100644 index 00000000..563223be --- /dev/null +++ b/docs/manual/mod/mod_authn_alias.html.en @@ -0,0 +1,121 @@ + + + +mod_authn_alias - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authn_alias

+
+

Available Languages:  en 

+
+ + + + +
Description:Provides the ability to create extended authentication + providers based on actual providers
Status:Extension
Module Identifier:authn_alias_module
Source File:mod_authn_alias.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module allows extended authentication providers to be created + within the configuration file and assigned an alias name. The alias + providers can then be referenced through the directives + AuthBasicProvider or + AuthDigestProvider in + the same way as a base authentication provider. Besides the ability + to create and alias an extended provider, it also allows the same + extended authentication provider to be reference by multiple + locations.

+ +
+

Directives

+ +

Topics

+
+
top
+
+

Example

+

The example below creates two different ldap authentication + provider aliases based on the ldap provider. This allows + a single authenticated location to be serviced by multiple + ldap hosts:

+ +

Example

+ LoadModule authn_alias_module modules/mod_authn_alias.so

+ <AuthnProviderAlias ldap ldap-alias1>
+ + AuthLDAPBindDN cn=youruser,o=ctx
+ AuthLDAPBindPassword yourpassword
+ AuthLDAPURL ldap://ldap.host/o=ctx
+ + </AuthnProviderAlias>

+ <AuthnProviderAlias ldap ldap-other-alias>
+ + AuthLDAPBindDN cn=yourotheruser,o=dev
+ AuthLDAPBindPassword yourotherpassword
+ AuthLDAPURL ldap://other.ldap.host/o=dev?cn
+ + </AuthnProviderAlias>

+ + Alias /secure /webpages/secure
+ <Directory /webpages/secure>
+ + Order deny,allow
+ Allow from all

+ + AuthBasicProvider ldap-other-alias ldap-alias1

+ + AuthType Basic
+ AuthName LDAP_Protected_Place
+ AuthzLDAPAuthoritative off
+ require valid-user
+ + </Directory>
+

+
+
top
+

<AuthnProviderAlias> Directive

+ + + + + + +
Description:Enclose a group of directives that represent an +extension of a base authentication provider and referenced by +the specified alias
Syntax:<AuthnProviderAlias baseProvider Alias> +... </AuthnProviderAlias>
Context:server config, virtual host
Status:Extension
Module:mod_authn_alias
+

<AuthnProviderAlias> and + </AuthnProviderAlias> are used to enclose a group of + authentication directives that can be referenced by the alias name + using one of the directives + AuthBasicProvider or + AuthDigestProvider.

+ + +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_anon.html b/docs/manual/mod/mod_authn_anon.html new file mode 100644 index 00000000..3afcbf61 --- /dev/null +++ b/docs/manual/mod/mod_authn_anon.html @@ -0,0 +1,11 @@ +URI: mod_authn_anon.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authn_anon.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authn_anon.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authn_anon.html.en b/docs/manual/mod/mod_authn_anon.html.en new file mode 100644 index 00000000..03baeaa8 --- /dev/null +++ b/docs/manual/mod/mod_authn_anon.html.en @@ -0,0 +1,224 @@ + + + +mod_authn_anon - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authn_anon

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Allows "anonymous" user access to authenticated + areas
Status:Extension
Module Identifier:authn_anon_module
Source File:mod_authn_anon.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module provides authentication front-ends such as + mod_auth_basic to authenticate users similar + to anonymous-ftp sites, i.e. have a 'magic' user id + 'anonymous' and the email address as a password. These email + addresses can be logged.

+ +

Combined with other (database) access control methods, this + allows for effective user tracking and customization according + to a user profile while still keeping the site open for + 'unregistered' users. One advantage of using Auth-based user + tracking is that, unlike magic-cookies and funny URL + pre/postfixes, it is completely browser independent and it + allows users to share URLs.

+ +

When using mod_auth_basic, this module is invoked + via the AuthBasicProvider + directive with the anon value.

+
+ +
top
+
+

Example

+

The example below is combined with "normal" htpasswd-file based + authentication and allows users in additionally as 'guests' with the + following properties:

+ +
    +
  • It insists that the user enters a userID. + (Anonymous_NoUserID)
    • + +
  • It insists that the user enters a password. + (Anonymous_MustGiveEmail)
    • + +
  • The password entered must be a valid email address, i.e. + contain at least one '@' and a '.'. + (Anonymous_VerifyEmail)
    • + +
  • The userID must be one of anonymous guest www test + welcome and comparison is not case + sensitive. (Anonymous)
    • + +
  • And the Email addresses entered in the passwd field are + logged to the error log file. + (Anonymous_LogEmail)
    • +
+ +

Example

+ <Directory /foo> + + AuthName "Use 'anonymous' & Email address for guest entry"
+ AuthType Basic
+ AuthBasicProvider file anon
+ AuthUserFile /path/to/your/.htpasswd
+
+ Anonymous_NoUserID off
+ Anonymous_MustGiveEmail on
+ Anonymous_VerifyEmail on
+ Anonymous_LogEmail on
+ Anonymous anonymous guest www test welcome
+
+ Order Deny,Allow
+ Allow from all
+
+ Require valid-user
+ + </Directory> +

+
+
top
+

Anonymous Directive

+ + + + + + + +
Description:Specifies userIDs that are allowed access without +password verification
Syntax:Anonymous user [user] ...
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authn_anon
+

A list of one or more 'magic' userIDs which are allowed + access without password verification. The userIDs are space + separated. It is possible to use the ' and " quotes to allow a + space in a userID as well as the \ escape character.

+ +

Please note that the comparison is + case-IN-sensitive.
+ It's strongly recommended that the magic username + 'anonymous' is always one of the allowed + userIDs.

+ +

Example:

+ Anonymous anonymous "Not Registered" "I don't know" +

+ +

This would allow the user to enter without password + verification by using the userIDs "anonymous", + "AnonyMous", "Not Registered" and "I Don't Know".

+ +

As of Apache 2.1 it is possible to specify the userID as + "*". That allows any supplied userID to be + accepted.

+ +
+
top
+

Anonymous_LogEmail Directive

+ + + + + + + + +
Description:Sets whether the password entered will be logged in the +error log
Syntax:Anonymous_LogEmail On|Off
Default:Anonymous_LogEmail On
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authn_anon
+

When set On, the default, the 'password' entered + (which hopefully contains a sensible email address) is logged in + the error log.

+ +
+
top
+

Anonymous_MustGiveEmail Directive

+ + + + + + + + +
Description:Specifies whether blank passwords are allowed
Syntax:Anonymous_MustGiveEmail On|Off
Default:Anonymous_MustGiveEmail On
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authn_anon
+

Specifies whether the user must specify an email address as + the password. This prohibits blank passwords.

+ +
+
top
+

Anonymous_NoUserID Directive

+ + + + + + + + +
Description:Sets whether the userID field may be empty
Syntax:Anonymous_NoUserID On|Off
Default:Anonymous_NoUserID Off
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authn_anon
+

When set On, users can leave the userID (and + perhaps the password field) empty. This can be very convenient for + MS-Explorer users who can just hit return or click directly on the + OK button; which seems a natural reaction.

+ +
+
top
+

Anonymous_VerifyEmail Directive

+ + + + + + + + +
Description:Sets whether to check the password field for a correctly +formatted email address
Syntax:Anonymous_VerifyEmail On|Off
Default:Anonymous_VerifyEmail Off
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authn_anon
+

When set On the 'password' entered is checked for + at least one '@' and a '.' to encourage users to enter valid email + addresses (see the above Anonymous_LogEmail).

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_anon.html.ja.euc-jp b/docs/manual/mod/mod_authn_anon.html.ja.euc-jp new file mode 100644 index 00000000..9cd69065 --- /dev/null +++ b/docs/manual/mod/mod_authn_anon.html.ja.euc-jp @@ -0,0 +1,224 @@ + + + +mod_authn_anon - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authn_anon

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:ǧ¾Ú¤¬É¬ÍפÊÎΰè¤Ø¤Î "anonymous" ¥æ¡¼¥¶¤Î¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë +
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authn_anon_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authn_anon.c
¸ß´¹À­:Apache 2.1 °Ê¹ß
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï mod_auth_basic ¤Î¤è¤¦¤Ê + ǧ¾Ú¥Õ¥í¥ó¥È¥¨¥ó¥É¤È¤·¤Æ¡¢anonymous-ftp ¥µ¥¤¥È¤Î¤è¤¦¤Ê¡¢¡ÖËâË¡¤Î¡×¥æ¡¼¥¶ ID + 'anonymous' ¤ÈÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤ò¥Ñ¥¹¥ï¡¼¥É¤Ë¤·¤¿¥æ¡¼¥¶Ç§¾Ú¤ò + ¹Ô¤Ê¤¦µ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£¤³¤ÎÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤Ï¥í¥°¼ý½¸¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+ +

¾¤Î (¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë¤è¤ë) ¥¢¥¯¥»¥¹À©¸æÊýË¡¤ÈÁȤ߹ç¤ï¤»¤ë¤³¤È¤Ç¡¢ + ¡Ö̤ÅÐÏ¿¡×¥æ¡¼¥¶¤ËÂФ·¤Æ¥µ¥¤¥È¤ò¸ø³«¤·¤Ä¤Ä¡¢¸úΨ¤è¤¯¥æ¡¼¥¶ÄÉÀפ·¤¿¤ê¡¢ + ¥æ¡¼¥¶¤Î¥×¥í¥Õ¥¡¥¤¥ë¤Ë±þ¤¸¤¿¥«¥¹¥¿¥Þ¥¤¥º¤ò¤·¤¿¤ê¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Êǧ¾Ú¤Ë´ð¤Å¤¤¤¿¥æ¡¼¥¶ÄÉÀפÎÍøÅÀ¤Î°ì¤Ä¤Ï¡¢ + ¥Þ¥¸¥Ã¥¯¥¯¥Ã¥­¡¼¤Ë´ð¤Å¤¯¥æ¡¼¥¶ÄÉÀ×ÊýË¡¤ä¡¢ + ÄÁ̯¤Ê URL ¤ÎÀÜƬ¼­¤äÀÜÈø¼­¤òÍøÍѤ·¤¿¥æ¡¼¥¶ÄÉÀ×ÊýË¡¤È¤Ï°Û¤Ê¤ê¡¢ + ´°Á´¤Ë¥Ö¥é¥¦¥¶Èó°Í¸¤Ç¤¢¤ê¡¢¥æ¡¼¥¶´Ö¤Ç URL ¤ò¶¦Í­¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤È¤¤¤¦ + ÅÀ¤Ç¤¹¡£

+ +

mod_auth_basic ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï + AuthBasicProvider ¤Ë + anon ¤È¤¤¤¦ÃͤòÀßÄꤹ¤ë¤³¤È¤Çµ¯Æ°¤µ¤ì¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

¥È¥Ô¥Ã¥¯

+
+
top
+
+

Îã

+

°Ê²¼¤ÎÎã¤Ï¡ÖÉáÄ̡פΠhtpasswd ¥Õ¥¡¥¤¥ë¤Ë´ð¤Å¤¤¤¿Ç§¾Ú¤ÈÁȤ߹ç¤ï¤µ¤ì¤Æ + ¤ª¤ê¡¢°Ê²¼¤ÎÍ×·ï¤ò¸«¤¿¤¹¥æ¡¼¥¶¤ò¡Ö¥²¥¹¥È¡×¤È¤·¤Æµö²Ä¤·¤Þ¤¹:

+ +
    +
  • ¥æ¡¼¥¶¤Ï userID ¤òÆþÎϤ·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + (Anonymous_NoUserID)
    • + +
  • ¥æ¡¼¥¶¤Ï¥Ñ¥¹¥ï¡¼¥É¤òÆþÎϤ·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + (Anonymous_MustGiveEmail)
    • + +
  • ÆþÎϤµ¤ì¤¿¥Ñ¥¹¥ï¡¼¥É¤ÏÍ­¸ú¤ÊÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤Ç¤Ê¤±¤ì¤Ð + ¤Ê¤ê¤Þ¤»¤ó¡£¤¹¤Ê¤ï¤Á¡¢¾¯¤¯¤È¤â°ì¤Ä¤Î '@' ¤È '.' ¤¬ + ´Þ¤Þ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + (Anonymous_VerifyEmail)
    • + +
  • userID ¤Ï anonymous guest www test + welcome ¤Î¤É¤ì¤«¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¥æ¡¼¥¶Ì¾¤ÎÈæ³Ó¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£
    • + +
  • ¥Ñ¥¹¥ï¡¼¥ÉÍó¤ËÆþÎϤµ¤ì¤¿ÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤Ï¥¨¥é¡¼¥í¥°¥Õ¥¡¥¤¥ë¤Ë + ¥í¥®¥ó¥°¤µ¤ì¤Þ¤¹¡£ + (Anonymous_LogEmail)
    • +
+ +

Îã

+ <Directory /foo> + + AuthName "Use 'anonymous' & Email address for guest entry"
+ AuthType Basic
+ AuthBasicProvider file anon
+ AuthUserFile /path/to/your/.htpasswd
+
+ Anonymous_NoUserID off
+ Anonymous_MustGiveEmail on
+ Anonymous_VerifyEmail on
+ Anonymous_LogEmail on
+ Anonymous anonymous guest www test welcome
+
+ Order Deny,Allow
+ Allow from all
+
+ Require valid-user
+ + </Directory> +

+
+
top
+

Anonymous ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Ñ¥¹¥ï¡¼¥É¤Î¸¡ººÌµ¤·¤Ç¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë userID ¤ò»ØÄꤹ¤ë +
¹½Ê¸:Anonymous user [user] ...
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_authn_anon
+

¥Ñ¥¹¥ï¡¼¥É¤Î¸¡ºº¤ò¤·¤Ê¤¤¤Ç¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë¡ÖËâË¡¤Î¡× userID ¤ò + ÀßÄꤷ¤Þ¤¹¡£userID Ãæ¤Ë¶õÇò¤ò»È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¡¢ + ¥¨¥¹¥±¡¼¥×ʸ»ú \ ¤Ë¤è¤ëÊýË¡¤È¡¢°úÍÑÉä ' ¤È " ¤Ë¤è¤ë¥¯¥ª¡¼¥Æ¥£¥ó¥° + ¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¥æ¡¼¥¶Ì¾¤ÎÈæ³Ó¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Ê¤¤¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
+ ËâË¡¤Î¥æ¡¼¥¶Ì¾ 'anonymous' ¤¬µö²Ä¤µ¤ì¤Æ¤¤¤ë userID ¤Ë + ´Þ¤à¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ï¶¯¤¯¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

Îã:

+ Anonymous anonymous "Not Registered" "I don't know" +

+ +

¤³¤ì¤Ï¡¢userID "anonymous", + "AnonyMous", "Not Registered", "I Don't Know" ¤Î¤É¤ì¤«¤ò»È¤Ã¤Æ¤â + ¥Ñ¥¹¥ï¡¼¥É̵¤·¤Ç¥æ¡¼¥¶¤¬¥µ¥¤¥È¤ËÆþ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

Apache 2.1 ¤Ç¤Ï userID ¤Ë "*" ¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¾ì¹ç¡¢¤¹¤Ù¤Æ¤ÎuserID ¤òµö²Ä¤·¤Þ¤¹¡£

+ +
+
top
+

Anonymous_LogEmail ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:ÆþÎϤµ¤ì¤¿¥Ñ¥¹¥ï¡¼¥É¤¬¥¨¥é¡¼¥í¥°¤Ë¥í¥®¥ó¥°¤µ¤ì¤ë¤«¤É¤¦¤«¤ò +ÀßÄꤹ¤ë
¹½Ê¸:Anonymous_LogEmail On|Off
¥Ç¥Õ¥©¥ë¥È:Anonymous_LogEmail On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_authn_anon
+

¥Ç¥Õ¥©¥ë¥È¤Î On ¤ËÀßÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢ + ÆþÎϤµ¤ì¤¿ (¤Þ¤Ã¤È¤¦¤ÊÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤Ç¤¢¤ë¤³¤È¤¬ + ´üÂÔ¤µ¤ì¤ë) ¡Ö¥Ñ¥¹¥ï¡¼¥É¡×¤¬¥¨¥é¡¼¥í¥°¤Ë¥í¥®¥ó¥°¤µ¤ì¤Þ¤¹¡£

+ +
+
top
+

Anonymous_MustGiveEmail ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¶õ¥Ñ¥¹¥ï¡¼¥É¤òµö²Ä¤¹¤ë¤«¤É¤¦¤«¤ò»ØÄꤹ¤ë
¹½Ê¸:Anonymous_MustGiveEmail On|Off
¥Ç¥Õ¥©¥ë¥È:Anonymous_MustGiveEmail On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_authn_anon
+

¥æ¡¼¥¶¤¬¥Ñ¥¹¥ï¡¼¥É¤È¤·¤ÆÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ë¤«¤É¤¦¤«¤ò + ÀßÄꤷ¤Þ¤¹¡£¤³¤ì¤Ï¶õ¥Ñ¥¹¥ï¡¼¥É¤ò¶Ø»ß¤·¤Þ¤¹¡£

+ +
+
top
+

Anonymous_NoUserID ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¶õ userID ¤òµö²Ä¤¹¤ë¤«¤ò»ØÄꤹ¤ë
¹½Ê¸:Anonymous_NoUserID On|Off
¥Ç¥Õ¥©¥ë¥È:Anonymous_NoUserID Off
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_authn_anon
+

On ¤ËÀßÄꤹ¤ë¤È¡¢¥æ¡¼¥¶¤Ï userID (¤È¤ª¤½¤é¤¯¤Ï + ¥Ñ¥¹¥ï¡¼¥ÉÍó¤â) ¶õ¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤Ïñ¤Ë¥ê¥¿¡¼¥ó¥­¡¼¤ò + ᤤ¤¿¤ê OK ¥Ü¥¿¥ó¤òľÀÜ¥¯¥ê¥Ã¥¯¤·¤¿¤ê¤¹¤ë MS-Explorer ¥æ¡¼¥¶¤Ë¤Ï + Èó¾ï¤ËÊØÍø¤Ç¤¹¡£¤½¤Î¤è¤¦¤ÊÁàºî¤Ï¤´¤¯¤´¤¯¼«Á³¤Ê¤â¤Î¤Ç¤·¤ç¤¦¡£

+ +
+
top
+

Anonymous_VerifyEmail ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Ñ¥¹¥ï¡¼¥ÉÍó¤¬Àµ¤·¤¤·Á¼°¤ÎÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤Ç¤¢¤ë¤³¤È¤ò +Ä´¤Ù¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
¹½Ê¸:Anonymous_VerifyEmail On|Off
¥Ç¥Õ¥©¥ë¥È:Anonymous_VerifyEmail Off
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_authn_anon
+

On ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢¥æ¡¼¥¶¤¬Í­¸ú¤ÊÅŻҥ᡼¥ë + ¥¢¥É¥ì¥¹¤òÆþÎϤ¹¤ë¤³¤È¤ò¿ä¾©¤¹¤ë¤¿¤á¡¢ÆþÎϤµ¤ì¤¿¡Ö¥Ñ¥¹¥ï¡¼¥É¡×¤Ï + ¾¯¤Ê¤¯¤È¤â°ì¤Ä¤Î '@' ¤È '.' ¤ò´Þ¤ó¤Ç¤¤¤ë¤«¤É¤¦¤«¤òÄ´¤Ù¤Þ¤¹ + (¾å¤Î Anonymous_LogEmail »²¾È)¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_anon.html.ko.euc-kr b/docs/manual/mod/mod_authn_anon.html.ko.euc-kr new file mode 100644 index 00000000..7723e3c1 --- /dev/null +++ b/docs/manual/mod/mod_authn_anon.html.ko.euc-kr @@ -0,0 +1,211 @@ + + + +mod_authn_anon - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authn_anon

+
+

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

+
+ + + + +
¼³¸í:ÀÎÁõ¿µ¿ª¿¡ "À͸í(anonymous)" »ç¿ëÀÚÀÇ Á¢±ÙÀ» +Çã¿ëÇÑ´Ù
»óÅÂ:Extension
¸ðµâ¸í:authn_anon_module
¼Ò½ºÆÄÀÏ:mod_authn_anon.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº mod_auth_basic µî ÀÎÁõ¾Õ´Ü¸ðµâÀ» + À§ÇØ (¿¹¸¦ µé¾î 'Ưº°ÇÑ' »ç¿ëÀÚ ¾ÆÀ̵ð 'anonymous'¿Í + ÀüÀÚ¿ìÆí ÁÖ¼Ò¸¦ ¾ÏÈ£·Î »ç¿ëÇÏ´Â) À͸í-ftp »çÀÌÆ®¿Í À¯»çÇÑ + »ç¿ëÀÚ ÀÎÁõÀ» ÇÑ´Ù. ÀüÀÚ¿ìÆí ÁÖ¼Ò¸¦ ·Î±×¿¡ ±â·ÏÇÒ ¼ö ÀÖ´Ù.

+ +

´Ù¸¥ (µ¥ÀÌÅͺ£À̽º) Á¢±ÙÁ¦¾î ¹æ½Ä°ú ÇÔ²² »ç¿ëÇÏ¿© + 'µî·ÏÇÏÁö¾ÊÀº' »ç¿ëÀÚ¿¡°Ô »çÀÌÆ®¸¦ ¿­¾îµÎ¸é¼­ È¿À²ÀûÀÎ »ç¿ëÀÚ + ÃßÀû°ú »ç¿ëÀÚÁ¤ÀÇ°¡ °¡´ÉÇÏ´Ù. ÀÎÁõ±â¹Ý »ç¿ëÀÚ ÃßÀûÀº ÄíÅ°³ª + ±«»óÇÑ URL Á¢µÎ»ç/Á¢¹Ì»ç¿Í ´Þ¸® ¿ÏÀüÈ÷ ºê¶ó¿ìÀú µ¶¸³ÀûÀÌ°í + »ç¿ëÀÚ°¡ URLÀ» °øÀ¯ÇÒ ¼ö ÀÖ´Ù´Â ÀåÁ¡ÀÌ ÀÖ´Ù.

+ +

mod_auth_basicÀ» »ç¿ëÇÒ¶§ AuthBasicProviderÀÇ + °ªÀ¸·Î anonÀ» ¼³Á¤Çϸé ÀÌ ¸ðµâÀ» »ç¿ëÇÑ´Ù.

+
+ +
top
+
+

¿¹Á¦

+

´ÙÀ½ ¿¹´Â "ÀϹÝÀûÀÎ" htpasswd-ÆÄÀϱâ¹Ý ÀÎÁõ¿¡ Ãß°¡·Î + »ç¿ëÀÚ°¡ ´ÙÀ½ Á¶°ÇÀ» ¸¸Á·ÇÑ´Ù¸é '¼Õ´Ô(guest)'À¸·Î Á¢±ÙÇÒ + ¼ö ÀÖµµ·Ï ÇÑ´Ù:

+ +
    +
  • »ç¿ëÀÚ´Â »ç¿ëÀÚ ¾ÆÀ̵𸦠ÀÔ·ÂÇØ¾ß ÇÑ´Ù. (Anonymous_NoUserID)
    • + +
  • »ç¿ëÀÚ´Â ¾ÏÈ£¸¦ ÀÔ·ÂÇØ¾ß ÇÑ´Ù. (Anonymous_MustGiveEmail)
    • + +
  • ¾ÏÈ£·Î À¯È¿ÇÑ ÀüÀÚ¿ìÆí ÁÖ¼Ò¸¦ ÀÔ·ÂÇØ¾ß ÇÑ´Ù. ¿¹¸¦ + µé¾î ÃÖ¼ÒÇÑ '@'¿Í '.' ÇÑ°³¸¦ Æ÷ÇÔÇØ¾ß ÇÑ´Ù. (Anonymous_VerifyEmail)
    • + +
  • »ç¿ëÀÚ ¾ÆÀ̵ð´Â anonymous guest www test + welcome Áß ÇϳªÀ̸ç, ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö + ¾Ê´Â´Ù. (Anonymous)
    • + +
  • ±×¸®°í ¾ÏÈ£·Î ÀÔ·ÂÇÑ ÀüÀÚ¿ìÆí ÁÖ¼Ò¸¦ ¿À·ù·Î±×ÆÄÀÏ¿¡ + ±â·ÏÇÑ´Ù. (Anonymous_LogEmail)
    • +
+ +

¿¹Á¦

+ <Directory /foo> + + AuthName "¼Õ´ÔÀ¸·Î ¹æ¹®ÇÏ·Á¸é 'anonymous'¿Í ÀüÀÚ¿ìÆí ÁÖ¼Ò¸¦ »ç¿ëÇ϶ó"
+ AuthType Basic
+ AuthBasicProvider file anon
+ AuthUserFile /path/to/your/.htpasswd
+
+ Anonymous_NoUserID off
+ Anonymous_MustGiveEmail on
+ Anonymous_VerifyEmail on
+ Anonymous_LogEmail on
+ Anonymous anonymous guest www test welcome
+
+ Order Deny,Allow
+ Allow from all
+
+ Require valid-user
+ + </Directory> +

+
+
top
+

Anonymous Áö½Ã¾î

+ + + + + + + +
¼³¸í:¾ÏÈ£°Ë»ç¾øÀÌ Á¢±ÙÀ» Çã¿ëÇÒ »ç¿ëÀÚ ¾ÆÀ̵ðµéÀ» +ÁöÁ¤ÇÑ´Ù
¹®¹ý:Anonymous user [user] ...
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authn_anon
+

¾ÏÈ£°Ë»ç¾øÀÌ Á¢±ÙÀ» Çã¿ëÇÒ 'Ưº°ÇÑ' »ç¿ëÀÚ ¾ÆÀ̵ð ¸ñ·Ï. + »ç¿ëÀÚ ¾ÆÀ̵ðµéÀ» °ø¹éÀ¸·Î ±¸ºÐÇÑ´Ù. µû¿ÈÇ¥ '¿Í "³ª Å»Ãâ¹®ÀÚ + \¸¦ »ç¿ëÇÏ¿© »ç¿ëÀÚ ¾ÆÀ̵ð ¾È¿¡ °ø¹éÀ» Æ÷ÇÔÇÒ ¼ö ÀÖ´Ù.

+ +

¾ÆÀ̵ð´Â ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾ÊÀ½À» + ÁÖÀÇÇ϶ó.
+ Çã¿ëÇÒ »ç¿ëÀÚ ¾ÆÀ̵𿡠Ưº°ÇÑ »ç¿ëÀÚ¸íÀÎ + 'anonymous'¸¦ Ç×»ó Æ÷ÇÔÇÏ±æ °­·ÂÈ÷ ±ÇÇÑ´Ù.

+ +

¿¹Á¦:

+ Anonymous anonymous "Not Registered" "I don't know" +

+ +

"anonymous", "AnonyMous", "Not Registered", "I Don't Know" + µî »ç¿ëÀÚ ¾ÆÀ̵𸦠»ç¿ëÇÏ¸é ¾ÏÈ£°Ë»ç¾øÀÌ »ç¿ëÀÚ¸¦ Çã¿ëÇÑ´Ù.

+ +

¾ÆÆÄÄ¡ 2.1¿¡¼­´Â »ç¿ëÀÚ ¾ÆÀ̵ð·Î "*"¸¦ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. ±×·¯¸é ¾î¶² »ç¿ëÀÚ ¾ÆÀ̵ð¶óµµ + ¹Þ¾ÆµéÀδÙ.

+ +
+
top
+

Anonymous_LogEmail Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ÀÔ·ÂÇÑ ¾ÏÈ£¸¦ ¿À·ù·Î±×¿¡ ±â·ÏÇÒÁö ¿©ºÎ
¹®¹ý:Anonymous_LogEmail On|Off
±âº»°ª:Anonymous_LogEmail On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authn_anon
+

±âº»°ªÀÎ OnÀ¸·Î ¼³Á¤Çϸé (¾Æ¸¶µµ ÀüÀÚ¿ìÆí + ÁÖ¼ÒÀÏ) ÀÔ·ÂÇÑ '¾ÏÈ£'¸¦ ¿À·ù·Î±×¿¡ ±â·ÏÇÑ´Ù.

+ +
+
top
+

Anonymous_MustGiveEmail Áö½Ã¾î

+ + + + + + + + +
¼³¸í:¾ÏÈ£°¡ ¾ø¾îµµ °¡´ÉÇÑÁö ¿©ºÎ
¹®¹ý:Anonymous_MustGiveEmail On|Off
±âº»°ª:Anonymous_MustGiveEmail On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authn_anon
+

»ç¿ëÀÚ°¡ ¾ÏÈ£·Î ÀüÀÚ¿ìÆí ÁÖ¼Ò¸¦ ÀÔ·ÂÇØ¾ß ÇÏ´ÂÁö ¿©ºÎ¸¦ + °áÁ¤ÇÑ´Ù. ¾ÏÈ£°¡ ¾øÀ¸¸é °ÅºÎÇÑ´Ù.

+ +
+
top
+

Anonymous_NoUserID Áö½Ã¾î

+ + + + + + + + +
¼³¸í:»ç¿ëÀÚ ¾ÆÀ̵𰡠¾ø¾îµµ °¡´ÉÇÏÁö ¿©ºÎ
¹®¹ý:Anonymous_NoUserID On|Off
±âº»°ª:Anonymous_NoUserID Off
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authn_anon
+

OnÀ¸·Î ¼³Á¤ÇÏ¸é »ç¿ëÀÚ´Â »ç¿ëÀÚ ¾ÆÀ̵𸦠+ (¾Æ¸¶ ¾ÏÈ£µµ) ÀÔ·ÂÇÏÁö ¾Ê¾Æµµ µÈ´Ù. ÀÌ´Â ÀÚ¿¬½º·´°Ô ±×³É + returnÀ» Ä¡°Å³ª OK ¹öÆ°À» Ŭ¸¯ÇÏ´Â MS-Explorer »ç¿ëÀÚ¿¡°Ô + ¸Å¿ì Æí¸®ÇÏ´Ù.

+ +
+
top
+

Anonymous_VerifyEmail Áö½Ã¾î

+ + + + + + + + +
¼³¸í:¾ÏÈ£°¡ ¿Ã¹Ù¸¥ Çü½ÄÀÇ ÀüÀÚ¿ìÆí ÁÖ¼ÒÀÎÁö °Ë»ç +¿©ºÎ
¹®¹ý:Anonymous_VerifyEmail On|Off
±âº»°ª:Anonymous_VerifyEmail Off
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authn_anon
+

OnÀ¸·Î ¼³Á¤ÇÏ¸é »ç¿ëÀÚ°¡ ¿Ã¹Ù¸¥ ÀüÀÚ¿ìÆí + ÁÖ¼Ò¸¦ ÀÔ·ÂÇϵµ·Ï ÀÔ·ÂÇÑ '¾ÏÈ£'°¡ ÃÖ¼ÒÇÑ '@'¿Í '.'¸¦ ÇÑ°³¾¿ + Æ÷ÇÔÇÏ´ÂÁö °Ë»çÇÑ´Ù (À§ÀÇ Anonymous_LogEmail Âü°í).

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_dbd.html b/docs/manual/mod/mod_authn_dbd.html new file mode 100644 index 00000000..f86a5a66 --- /dev/null +++ b/docs/manual/mod/mod_authn_dbd.html @@ -0,0 +1,3 @@ +URI: mod_authn_dbd.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_authn_dbd.html.en b/docs/manual/mod/mod_authn_dbd.html.en new file mode 100644 index 00000000..bb9209e3 --- /dev/null +++ b/docs/manual/mod/mod_authn_dbd.html.en @@ -0,0 +1,155 @@ + + + +mod_authn_dbd - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authn_dbd

+
+

Available Languages:  en 

+
+ + + + +
Description:User authentication using an SQL database
Status:Extension
Module Identifier:authn_dbd_module
Source File:mod_authn_dbd.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module provides authentication front-ends such as + mod_auth_digest and mod_auth_basic + to authenticate users by looking up users in SQL tables. + Similar functionality is provided by, for example, + mod_authn_file.

+

This module relies on mod_dbd to specify + the backend database driver and connection parameters, and + manage the database connections.

+ +

When using mod_auth_basic or + mod_auth_digest, this module is invoked via the + AuthBasicProvider or + AuthDigestProvider + with the dbd value.

+
+ +
top
+
+

Configuration Example

+ +

This simple example shows use of this module in the context of +the Authentication and DBD frameworks.

+
+#Database Management
+
+#Use the PostgreSQL driver
+DBDriver pgsql
+
+#Connection string: database name and login credentials
+DBDParams "dbname=htpasswd user=apache password=xxxxxx"
+
+#Parameters for Connection Pool Management
+DBDMin  1
+DBDKeep 2
+DBDMax  10
+DBDExptime 60
+
+#Authentication Section
+<Directory /usr/www/myhost/private>
+
+    #mod_auth configuration for authn_dbd
+    AuthType Basic
+    AuthName "My Server"
+    AuthBasicProvider dbd
+
+    #authz configuration
+    Require valid-user
+
+    #SQL query to verify a user
+    #(note: DBD drivers recognise both stdio-like %s and native syntax)
+    AuthDBDUserPWQuery "select password from authn where username = %s"
+</Directory>
+
+
+
top
+

AuthDBDUserPWQuery Directive

+ + + + + + +
Description:SQL query to look up a password for a user
Syntax:AuthDBDUserPWQuery query
Context:directory
Status:Extension
Module:mod_authn_dbd
+

The AuthDBDUserPWQuery specifies an + SQL query to look up a password for a specified user. + The query must take a single string (typically SQL varchar) + argument (username), and return a single value (encrypted password). +

+

+ AuthDBDUserPWQuery "SELECT password FROM authn WHERE username = %s" +

+ + +
+
top
+

AuthDBDUserRealmQuery Directive

+ + + + + + +
Description:SQL query to look up a password hash for a user and realm. +
Syntax:AuthDBDUserRealmQuery query
Context:directory
Status:Extension
Module:mod_authn_dbd
+

The AuthDBDUserRealmQuery specifies an + SQL query to look up a password for a specified user and realm. + The query must take two string (typically SQL varchar) arguments + (username and realm), and return a single value (encrypted password). +

+

+ AuthDBDUserRealmQuery "SELECT password FROM authn + WHERE username = %s AND realm = %s" +

+ + +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_dbm.html b/docs/manual/mod/mod_authn_dbm.html new file mode 100644 index 00000000..a4472a2c --- /dev/null +++ b/docs/manual/mod/mod_authn_dbm.html @@ -0,0 +1,11 @@ +URI: mod_authn_dbm.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authn_dbm.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authn_dbm.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authn_dbm.html.en b/docs/manual/mod/mod_authn_dbm.html.en new file mode 100644 index 00000000..6bc0739f --- /dev/null +++ b/docs/manual/mod/mod_authn_dbm.html.en @@ -0,0 +1,136 @@ + + + +mod_authn_dbm - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authn_dbm

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:User authentication using DBM files
Status:Extension
Module Identifier:authn_dbm_module
Source File:mod_authn_dbm.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module provides authentication front-ends such as + mod_auth_digest and mod_auth_basic + to authenticate users by looking up users in dbm password + files. Similar functionality is provided by + mod_authn_file.

+ +

When using mod_auth_basic or + mod_auth_digest, this module is invoked via the + AuthBasicProvider or + AuthDigestProvider + with the dbm value.

+
+

Directives

+ +

See also

+
+ +
top
+

AuthDBMType Directive

+ + + + + + + + +
Description:Sets the type of database file that is used to +store passwords
Syntax:AuthDBMType default|SDBM|GDBM|NDBM|DB
Default:AuthDBMType default
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authn_dbm
+

Sets the type of database file that is used to store the passwords. + The default database type is determined at compile time. The + availability of other types of database files also depends on + compile-time settings.

+ +

It is crucial that whatever program you use to create your password + files is configured to use the same type of database.

+ +
+
top
+

AuthDBMUserFile Directive

+ + + + + + + +
Description:Sets the name of a database file containing the list of users and +passwords for authentication
Syntax:AuthDBMUserFile file-path
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authn_dbm
+

The AuthDBMUserFile directive sets the + name of a DBM file containing the list of users and passwords for + user authentication. File-path is the absolute path to + the user file.

+ +

The user file is keyed on the username. The value for a user is + the encrypted password, optionally followed by a colon and arbitrary + data. The colon and the data following it will be ignored by the + server.

+ +

Security:

+

Make sure that the AuthDBMUserFile is stored + outside the document tree of the web-server; do not put it in + the directory that it protects. Otherwise, clients will be able to + download the AuthDBMUserFile.

+
+ +

Important compatibility note: The implementation of + dbmopen in the apache modules reads the string length of + the hashed values from the DBM data structures, rather than relying + upon the string being NULL-appended. Some applications, such as + the Netscape web server, rely upon the string being + NULL-appended, so if you are having trouble using DBM files + interchangeably between applications this may be a part of the + problem.

+ +

A perl script called + dbmmanage is included with + Apache. This program can be used to create and update DBM + format password files for use with this module.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_dbm.html.ja.euc-jp b/docs/manual/mod/mod_authn_dbm.html.ja.euc-jp new file mode 100644 index 00000000..a32ceec1 --- /dev/null +++ b/docs/manual/mod/mod_authn_dbm.html.ja.euc-jp @@ -0,0 +1,135 @@ + + + +mod_authn_dbm - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authn_dbm

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:DBM ¥Õ¥¡¥¤¥ë¤òÍѤ¤¤¿¥æ¡¼¥¶Ç§¾Ú
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authn_dbm_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authn_dbm.c
¸ß´¹À­:Apache 2.1 °Ê¹ß
+

³µÍ×

+ +

Ëܥ⥸¥å¡¼¥ë¤Ï mod_auth_digest ¤ä + mod_auth_basic ¤È¤¤¤Ã¤¿Ç§¾Ú¥Õ¥í¥ó¥È¥¨¥ó¥É¤ËÂФ·¤Æ¡¢ + dbm ¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ëÆ⤫¤é¤Î¥æ¡¼¥¶¸¡º÷¤Ë¤è¤ë + ¥æ¡¼¥¶Ç§¾Úµ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£»÷¤¿¤è¤¦¤Êµ¡Ç½¤Ï mod_authn_file + ¤Ç¤âÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

mod_auth_basic ¤ä mod_auth_digest + ¤ò»ÈÍѤ¹¤ëºÝ¤Ë¤Ï¡¢¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï + AuthBasicProvider ¤ä + AuthDigestPrivider + ¤Ç dbm ¤È»ØÄꤹ¤ë¤³¤È¤Çµ¯Æ°¤µ¤ì¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

AuthDBMType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Ñ¥¹¥ï¡¼¥É¤òÊݸ¤¹¤ë¤¿¤á¤ËɬÍפʥǡ¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤Î¼ïÎà¤ò +ÀßÄꤹ¤ë
¹½Ê¸:AuthDBMType default|SDBM|GDBM|NDBM|DB
¥Ç¥Õ¥©¥ë¥È:AuthDBMType default
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_authn_dbm
+

¥Ñ¥¹¥ï¡¼¥É¤òÊݸ¤¹¤ë¤¿¤á¤Ë»ÈÍѤ¹¤ë¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤Î¼ïÎà¤ò + ÀßÄꤷ¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¼ïÎà¤Ï¥³¥ó¥Ñ¥¤¥ë»þ¤Ë·è¤Þ¤ê¤Þ¤¹¡£ + ¾¤Î¼ïÎà¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬»ÈÍѲÄǽ¤«¤É¤¦¤«¤â ¥³¥ó¥Ñ¥¤¥ë»þ¤ÎÀßÄê¤Ë°Í¸¤·¤Þ¤¹¡£

+ +

¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤òºîÀ®¤¹¤ë¤Î¤Ë»ÈÍѤ¹¤ë¥×¥í¥°¥é¥à¤¬Æ±¤¸¼ïÎà¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò + »ÈÍѤ¹¤ë¤è¤¦¤ËÀßÄꤹ¤ë¤³¤È¤ÏÈó¾ï¤Ë½ÅÍפǤ¹¡£

+ +
+
top
+

AuthDBMUserFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:ǧ¾ÚÍѤΥ桼¥¶¤È¥Ñ¥¹¥ï¡¼¥É¤Î¥ê¥¹¥È¤òÊÝ»ý¤·¤Æ¤¤¤ë +¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë̾¤òÀßÄꤹ¤ë
¹½Ê¸:AuthDBMUserFile file-path
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_authn_dbm
+

AuthDBMUserFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ǧ¾ÚÍѤΥ桼¥¶¤È¥Ñ¥¹¥ï¡¼¥É¤Î¥ê¥¹¥È¤òÊÝ»ý¤·¤Æ¤¤¤ë DBM ¥Õ¥¡¥¤¥ë¤Î + ̾Á°¤òÀßÄꤷ¤Þ¤¹¡£File-path ¤Ï¥æ¡¼¥¶¥Õ¥¡¥¤¥ë¤Ø¤Î + ÀäÂХѥ¹¤Ç¤¹¡£

+ +

¥æ¡¼¥¶¥Õ¥¡¥¤¥ë¤Î¥­¡¼¤Ï¥æ¡¼¥¶Ì¾¤Ç¤¹¡£¥æ¡¼¥¶¤ËÂФ·¤ÆÊÖ¤µ¤ì¤ëÃÍ¤Ï + °Å¹æ²½¤µ¤ì¤¿¥Ñ¥¹¥ï¡¼¥É¤Ç¡¢¤½¤Î¸å¤Ë¡¢¥³¥í¥ó¤Ë³¤¤¤ÆǤ°Õ¤Î¥Ç¡¼¥¿¤¬ + ³¤¤¤Æ¤¤¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£¥³¥í¥ó¤È¤½¤Î¸å¤Î¥Ç¡¼¥¿¤Ï¥µ¡¼¥Ð¤Ï + ̵»ë¤·¤Þ¤¹¡£

+ +

¥»¥­¥å¥ê¥Æ¥£

+

AuthDBMUserFile ¤Ï¡¢ + ¥¦¥§¥Ö¥µ¡¼¥Ð¤Î¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼¤Î³°Â¦¤ËÊݴɤ¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + Êݸ¤è¤¦¤È¤·¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê°Ê²¼¤Ë¤Ï + ÃÖ¤«¤Ê¤¤¤Ç²¼¤µ¤¤¡£ + ¤½¤¦¤·¤Ê¤¤¤È¥¯¥é¥¤¥¢¥ó¥È¤¬ AuthUserFile ¤ò + ¥À¥¦¥ó¥í¡¼¥É¤Ç¤­¤Æ¤·¤Þ¤¤¤Þ¤¹¡£

+
+ +

½ÅÍפʸߴ¹À­¤Ë´Ø¤¹¤ëÃí°Õ: apache module ¤Î dbmopen ¤Î¼ÂÁõ¤Ï + ʸ»úÎó¤¬ NULL ¤Ç½ª¤ï¤Ã¤Æ¤¤¤ë¤³¤È¤Ë°Í¸¤¹¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢DBM ¥Ç¡¼¥¿¥¹¥È¥é¥¯¥Á¥ã + ¤Î¥Ï¥Ã¥·¥åÃͤÎʸ»úÎó¤ÎŤµ¤òÆɤ߼è¤ê¤Þ¤¹¡£Netscape ¥¦¥§¥Ö¥µ¡¼¥Ð¤Ê¤É¡¢ + ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ÎÃæ¤Ë¤Ïʸ»úÎó¤¬ NULL ¤Ç½ª¤ï¤Ã¤Æ¤¤¤ë¤³¤È¤Ë°Í¸¤·¤Æ¤¤¤ë + ¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢°Û¤Ê¤ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó´Ö¤Ç¤Î DBM ¥Õ¥¡¥¤¥ë¤Î + »ÈÍѤËÌäÂ꤬¤¢¤ë¾ì¹ç¤Ï¡¢¤³¤ì¤¬¸¶°ø¤Ë¤Ê¤Ã¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£

+ +

Apache ¤Ë¤Ï dbmmanage ¤È¤¤¤¦ + perl ¥¹¥¯¥ê¥×¥È¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥×¥í¥°¥é¥à¤ò»È¤Ã¤Æ¤³¤Î + ¥â¥¸¥å¡¼¥ë¤¬»ÈÍѤ¹¤ë DBM ¥Õ¥©¡¼¥Þ¥Ã¥È¤Î¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤¿¤ê + ¹¹¿·¤·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_dbm.html.ko.euc-kr b/docs/manual/mod/mod_authn_dbm.html.ko.euc-kr new file mode 100644 index 00000000..51c18917 --- /dev/null +++ b/docs/manual/mod/mod_authn_dbm.html.ko.euc-kr @@ -0,0 +1,131 @@ + + + +mod_authn_dbm - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authn_dbm

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:DBM ÆÄÀÏÀ» »ç¿ëÇÑ »ç¿ëÀÚ ÀÎÁõ
»óÅÂ:Extension
¸ðµâ¸í:authn_dbm_module
¼Ò½ºÆÄÀÏ:mod_authn_dbm.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº mod_auth_digest³ª + mod_auth_basic ÀÎÁõ¾Õ´Ü¸ðµâÀ» À§ÇØ + dbm ¾ÏÈ£ÆÄÀÏ¿¡¼­ »ç¿ëÀÚ¸¦ ã¾Æ¼­ ÀÎÁõÇÑ´Ù. + mod_authn_file°ú ±â´ÉÀÌ ºñ½ÁÇÑ´Ù.

+ +

mod_auth_basicÀ̳ª + mod_auth_digest¸¦ »ç¿ëÇÒ¶§ AuthBasicProvider³ª + AuthDigestProviderÀÇ + °ªÀ¸·Î dbmÀ» ¼³Á¤Çϸé ÀÌ ¸ðµâÀ» »ç¿ëÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

AuthDBMType Áö½Ã¾î

+ + + + + + + + +
¼³¸í:¾ÏÈ£¸¦ ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º ÆÄÀÏ Á¾·ù¸¦ +ÁöÁ¤ÇÑ´Ù
¹®¹ý:AuthDBMType default|SDBM|GDBM|NDBM|DB
±âº»°ª:AuthDBMType default
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authn_dbm
+

¾ÏÈ£¸¦ ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º ÆÄÀÏ Á¾·ù¸¦ ÁöÁ¤ÇÑ´Ù. ±âº» + µ¥ÀÌÅͺ£À̽º Á¾·ù´Â ÄÄÆÄÀ϶§ ÆÇ´ÜÇÑ´Ù. »ç¿ëÇÒ ¼ö ÀÖ´Â ´Ù¸¥ + µ¥ÀÌÅͺ£À̽º ÆÄÀÏ Á¾·ùµµ ÄÄÆÄÀÏ + ¼³Á¤¿¡ ´Þ·È´Ù.

+ +

¾ÏÈ£ÆÄÀÏÀ» ¸¸µå´Â ÇÁ·Î±×·¥ÀÌ °°Àº Á¾·ùÀÇ µ¥ÀÌÅͺ£À̽º¸¦ + »ç¿ëÇϵµ·Ï ¼³Á¤ÇØ¾ß ÇÑ´Ù.

+ +
+
top
+

AuthDBMUserFile Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÀÎÁõÇÒ »ç¿ëÀÚ¿Í ¾ÏÈ£ ¸ñ·ÏÀ» ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º +ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù
¹®¹ý:AuthDBMUserFile file-path
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authn_dbm
+

AuthDBMUserFile Áö½Ã¾î´Â »ç¿ëÀÚ + ÀÎÁõ¿¡ »ç¿ëÇÒ »ç¿ëÀÚ¿Í ¾ÏÈ£ ¸ñ·ÏÀ» ÀúÀåÇÏ´Â DBM ÆÄÀϸíÀ» + ÁöÁ¤ÇÑ´Ù. File-path´Â ÆÄÀÏÀÇ Àý´ë°æ·ÎÀÌ´Ù.

+ +

ÆÄÀÏÀº »ç¿ëÀÚ¸íÀ» Å°·Î »ç¿ëÇÑ´Ù. »ç¿ëÀÚ¿¡ ´ëÇÑ °ªÀº + ÀÎÄÚµùµÈ ¾ÏÈ£ÀÌ´Ù. ¾ÏÈ£ µÚ¿¡ Äݷаú ÀÓÀÇÀÇ Á¤º¸°¡ ³ª¿Ã ¼ö + ÀÖ´Ù. ¼­¹ö´Â Äݷаú µÚ¿¡ ³ª¿À´Â Á¤º¸¸¦ ¹«½ÃÇÑ´Ù.

+ +

º¸¾È:

+

AuthDBMUserFileÀÌ À¥¼­¹öÀÇ ¹®¼­µé + ¹Û¿¡ ÀÖÀ½À» È®ÀÎÇ϶ó. ÀÌ ÆÄÀÏÀ» º¸È£ÇÒ µð·ºÅ丮 ¾È¿¡ °°ÀÌ + µÎÁö ¸¶¶ó. ±×·¸Áö ¾ÊÀ¸¸é, Ŭ¶óÀ̾ðÆ®°¡ + AuthDBMUserFileÀ» ´Ù¿î·ÎµåÇÒ ¼ö + ÀÖ´Ù.

+
+ +

Áß¿äÇÑ È£È¯¼º ÁÖÀÇ: ¾ÆÆÄÄ¡ ¸ðµâÀÇ dbmopen + ±¸ÇöÀº ¹®ÀÚ¿­ ³¡ÀÇ NULL¿¡ ÀÇÁ¸ÇÏÁö¾Ê°í DBM ÀڷᱸÁ¶¿¡¼­ + Çؽ̰ªÀÇ ¹®ÀÚ¿­ ±æÀ̸¦ Àд´Ù. Netscape À¥¼­¹ö µî ¾î¶² + ÇÁ·Î±×·¥Àº ¹®ÀÚ¿­ÀÌ NULL·Î ³¡³­´Ù°í °¡Á¤Çϱ⶧¹®¿¡ ¿©·¯ + ÇÁ·Î±×·¥ÀÌ DBM ÆÄÀÏÀ» »ç¿ëÇÏ¸é ¹®Á¦°¡ µÉ ¼ö ÀÖ´Ù.

+ +

¾ÆÆÄÄ¡´Â dbmmanage¶ó´Â + Perl ½ºÅ©¸³Æ®¸¦ Æ÷ÇÔÇÑ´Ù. ÀÌ ÇÁ·Î±×·¥Àº ÀÌ ¸ðµâÀÌ »ç¿ëÇÒ + DBMÇü½Ä ¾ÏÈ£ÆÄÀÏÀ» ¸¸µé°í ¼öÁ¤ÇÑ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_default.html b/docs/manual/mod/mod_authn_default.html new file mode 100644 index 00000000..9a1beb27 --- /dev/null +++ b/docs/manual/mod/mod_authn_default.html @@ -0,0 +1,11 @@ +URI: mod_authn_default.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authn_default.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authn_default.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authn_default.html.en b/docs/manual/mod/mod_authn_default.html.en new file mode 100644 index 00000000..c962a61b --- /dev/null +++ b/docs/manual/mod/mod_authn_default.html.en @@ -0,0 +1,80 @@ + + + +mod_authn_default - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authn_default

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Authentication fallback module
Status:Base
Module Identifier:authn_default_module
Source File:mod_authn_default.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module is designed to be the fallback module, if you don't + have configured an authentication module like + mod_auth_basic. It simply rejects any + credentials supplied by the user.

+
+

Directives

+ +
+ +
top
+

AuthDefaultAuthoritative Directive

+ + + + + + + + +
Description:Sets whether authentication is passed to lower level +modules
Syntax:AuthDefaultAuthoritative On|Off
Default:AuthDefaultAuthoritative On
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_authn_default
+

Setting the AuthDefaultAuthoritative directive + explicitly to Off allows for authentication to be passed on + to lower level modules (as defined in the modules.c + files).

+ +

Note

+

Normally there are no lower level modules, since + mod_authn_default is defined to be already on + a very low level. Therefore you should leave the value of + AuthDefaultAuthoritative as default + (On).

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_default.html.ja.euc-jp b/docs/manual/mod/mod_authn_default.html.ja.euc-jp new file mode 100644 index 00000000..c138de3c --- /dev/null +++ b/docs/manual/mod/mod_authn_default.html.ja.euc-jp @@ -0,0 +1,80 @@ + + + +mod_authn_default - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authn_default

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:ǧ¾Ú¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¥â¥¸¥å¡¼¥ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authn_default_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authn_default.c
¸ß´¹À­:Apache 2.1 °Ê¹ß
+

³µÍ×

+ +

mod_auth_basic ¤Î¤è¤¦¤Êǧ¾Ú¥â¥¸¥å¡¼¥ë¤ò + ÀßÄꤷ¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï¡¢Ëܥ⥸¥å¡¼¥ë¤¬¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¤È¤Ê¤ê¤Þ¤¹¡£ + ¥æ¡¼¥¶¤«¤éÄ󼨤µ¤ì¤¿¤É¤ó¤Ê¾Ú½ñ¤âñ¤ËµñÈݤ·¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +
+ +
top
+

AuthDefaultAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¼¡¤ÎÄ㼡¥ì¥Ù¥ë¤Îǧ¾Ú¥â¥¸¥å¡¼¥ë¤ËÀ©¸æ¤òÅϤ¹¤«¤É¤¦¤«¤ò +ÀßÄꤷ¤Þ¤¹
¹½Ê¸:AuthDefaultAuthoritative On|Off
¥Ç¥Õ¥©¥ë¥È:AuthDefaultAuthoritative On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authn_default
+

AuthDefaultAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ÌÀ¼¨Åª¤Ë Off ¤ËÀßÄꤹ¤ë¤È¡¢ + ǧ¾Ú¤ò¼¡¤Î (modules.c ¥Õ¥¡¥¤¥ë¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë) + Ä㼡¥ì¥Ù¥ë¤Î¥â¥¸¥å¡¼¥ë¤ËÅϤ·¤Þ¤¹¡£ +

+ +

Ãí°Õ

+

mod_authn_default ¼«ÂΤ¬¤È¤Æ¤âÄ㤤 + ¥ì¥Ù¥ë¤È¤·¤ÆÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢Ä̾ï¤Ï¤³¤ì¤è¤ê¤âÄ㼡¤Î + ¥â¥¸¥å¡¼¥ë¤Ï¸ºß¤·¤Þ¤»¤ó¡£¤Ç¤¹¤«¤é + AuthDefaultAuthoritative ¤Ï¥Ç¥Õ¥©¥ë¥È + (On) ¤Î¤Þ¤Þ¤Ë¤·¤¿¤Û¤¦¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_default.html.ko.euc-kr b/docs/manual/mod/mod_authn_default.html.ko.euc-kr new file mode 100644 index 00000000..af50668f --- /dev/null +++ b/docs/manual/mod/mod_authn_default.html.ko.euc-kr @@ -0,0 +1,76 @@ + + + +mod_authn_default - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authn_default

+
+

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

+
+ + + + +
¼³¸í:ÃÖÈÄ ÀÎÁõ¸ðµâ
»óÅÂ:Base
¸ðµâ¸í:authn_default_module
¼Ò½ºÆÄÀÏ:mod_authn_default.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº mod_auth_basic°ú °°Àº ÀÎÁõ¸ðµâÀ» + ¼³Á¤ÇÏÁö¾ÊÀº ÃÖÈÄÀÇ °æ¿ì ´ë½Å »ç¿ëÇÑ´Ù. ÀÌ ¸ðµâÀº »ç¿ëÀÚ°¡ + Á¦°øÇÑ ¾î¶°ÇÑ Á¤º¸µµ °ÅºÎÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +
+ +
top
+

AuthDefaultAuthoritative Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ÀÎÁõÀ» Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
¹®¹ý:AuthDefaultAuthoritative On|Off
±âº»°ª:AuthDefaultAuthoritative On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Base
¸ðµâ:mod_authn_default
+

AuthDefaultAuthoritative Áö½Ã¾î¸¦ + Á÷Á¢ Off·Î ¼³Á¤Çϸé (modules.c + ÆÄÀÏ¿¡¼­ Á¤ÀÇÇÑ) Àú¼öÁØ ¸ðµâ·Î ÀÎÁõÀ» ³Ñ°ÜÁØ´Ù.

+ +

ÁÖÀÇ

+

mod_authn_default°¡ ÀÌ¹Ì ¸Å¿ì + Àú¼öÁØÀ¸·Î Á¤ÀǵÇÀֱ⠶§¹®¿¡ º¸Åë ´õ ³·Àº ¸ðµâÀÌ ¾ø´Ù. + ±×·¯¹Ç·Î AuthDefaultAuthoritative¸¦ + ±âº»°ª(On)À¸·Î ³²°ÜµÖ¾ß ÇÑ´Ù.

+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_file.html b/docs/manual/mod/mod_authn_file.html new file mode 100644 index 00000000..d3f6ce2a --- /dev/null +++ b/docs/manual/mod/mod_authn_file.html @@ -0,0 +1,11 @@ +URI: mod_authn_file.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authn_file.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authn_file.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authn_file.html.en b/docs/manual/mod/mod_authn_file.html.en new file mode 100644 index 00000000..fa0d304e --- /dev/null +++ b/docs/manual/mod/mod_authn_file.html.en @@ -0,0 +1,132 @@ + + + +mod_authn_file - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authn_file

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:User authentication using text files
Status:Base
Module Identifier:authn_file_module
Source File:mod_authn_file.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module provides authentication front-ends such as + mod_auth_digest and mod_auth_basic + to authenticate users by looking up users in plain text password files. + Similar functionality is provided by mod_authn_dbm.

+ +

When using mod_auth_basic or + mod_auth_digest, this module is invoked via the + AuthBasicProvider or + AuthDigestProvider + with the file value.

+
+

Directives

+ +

See also

+
+ +
top
+

AuthUserFile Directive

+ + + + + + + +
Description:Sets the name of a text file containing the list of users and +passwords for authentication
Syntax:AuthUserFile file-path
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_authn_file
+

The AuthUserFile directive sets the name + of a textual file containing the list of users and passwords for + user authentication. File-path is the path to the user + file. If it is not absolute, it is treated as relative to the + ServerRoot.

+ +

Each line of the user file contains a username followed by + a colon, followed by the encrypted password. If the same user + ID is defined multiple times, mod_authn_file will + use the first occurrence to verify the password.

+ +

The utility htpasswd + which is installed as part of the binary distribution, or which + can be found in src/support, is used to maintain + the password file for HTTP Basic Authentication. See the + man page for more details. + In short:

+ +

Create a password file Filename with + username as the initial ID. It will prompt for + the password:

+ +

+ htpasswd -c Filename username +

+ +

Add or modify username2 in the password file + Filename:

+ +

+ htpasswd Filename username2 +

+ +

Note that searching large text files is very + inefficient; AuthDBMUserFile should be used + instead.

+ +

If you are using HTTP Digest Authentication, the htpasswd tool is not sufficient. + You have to use htdigest + instead. Note that you cannot mix user data for Digest Authentication + and Basic Authentication within the same file.

+ +

Security

+

Make sure that the AuthUserFile is + stored outside the document tree of the web-server. Do + not put it in the directory that it protects. + Otherwise, clients may be able to download the + AuthUserFile.

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_file.html.ja.euc-jp b/docs/manual/mod/mod_authn_file.html.ja.euc-jp new file mode 100644 index 00000000..e914cc95 --- /dev/null +++ b/docs/manual/mod/mod_authn_file.html.ja.euc-jp @@ -0,0 +1,142 @@ + + + +mod_authn_file - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authn_file

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤òÍѤ¤¤¿¥æ¡¼¥¶Ç§¾Ú
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authn_file_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authn_file.c
¸ß´¹À­:Apache 2.1 °Ê¹ß
+

³µÍ×

+ +

Ëܥ⥸¥å¡¼¥ë¤Ï mod_auth_digest ¤ä + mod_auth_basic ¤È¤¤¤Ã¤¿Ç§¾Ú¥Õ¥í¥ó¥È¥¨¥ó¥É¤ËÂФ·¤Æ¡¢ + ¥×¥ì¥¤¥ó¥Æ¥­¥¹¥È¤Î¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ëÆ⤫¤é¥æ¡¼¥¶¤ò¸¡º÷¤¹¤ë¤³¤È¤Ç¡¢ + ¥æ¡¼¥¶Ç§¾Úµ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£»÷¤¿¤è¤¦¤Êµ¡Ç½¤Ï mod_authn_dbm + ¤Ç¤âÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

mod_auth_basic ¤ä mod_auth_digest + ¤ò»ÈÍѤ¹¤ëºÝ¤Ë¤Ï¡¢ + AuthBasicProvider ¤ä + AuthDigestPrivider + ¤Ç file ¤È»ØÄꤹ¤ë¤³¤È¤Ç¤³¤Î¥â¥¸¥å¡¼¥ë¤Ïµ¯Æ°¤µ¤ì¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

AuthUserFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:ǧ¾Ú¤Ë»ÈÍѤ¹¤ë¥æ¡¼¥¶¤È¥Ñ¥¹¥ï¡¼¥É¤Î°ìÍ÷¤¬³ÊǼ¤µ¤ì¤Æ¤¤¤ë¡¢ +¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤹ¤ë
¹½Ê¸:AuthUserFile file-path
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authn_file
+

AuthUserFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥æ¡¼¥¶Ç§¾Ú¤Î¤¿¤á¤Î¥æ¡¼¥¶¤È¥Ñ¥¹¥ï¡¼¥É¤Î°ìÍ÷¤ò³ÊǼ¤·¤¿ + ¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤷ¤Þ¤¹¡£file-path + ¤Ï¥æ¡¼¥¶¥Õ¥¡¥¤¥ë¤Ø¤Î¥Ñ¥¹¤Ç¤¹¡£ + ¤â¤·ÀäÂХѥ¹¤Ç¤Ê¤±¤ì¤Ð¡¢ + ServerRoot + ¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£

+ +

¥æ¡¼¥¶¥Õ¥¡¥¤¥ë¤Î³Æ¹Ô¤Ë¤Ï¡¢¥æ¡¼¥¶Ì¾¡¢¥³¥í¥ó¡¢ + °Å¹æ²½¤·¤¿¥Ñ¥¹¥ï¡¼¥É¤òµ­½Ò¤·¤Þ¤¹¡£ + Ʊ°ì¥æ¡¼¥¶ ID ¤¬Ê£¿ô²óÅÐÏ¿¤µ¤ì¤¿»þ¤Ï¡¢ + mod_authn_file + ¤ÏºÇ½é¤Ë¸«¤Ä¤«¤Ã¤¿¥Ñ¥¹¥ï¡¼¥É¤ò»ÈÍѤ·¤Æǧ¾Ú¤·¤Þ¤¹¡£

+ +

¥Ð¥¤¥Ê¥êÇÛÉۤΰìÉô¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤ë¤«¡¢ + ¤¢¤ë¤¤¤Ï src/support ¤Ë¤¢¤ë + htpasswd + ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ç¡¢¤³¤Î HTTP ´ðËÜǧ¾Ú + Íѥѥ¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤ò¥á¥¤¥ó¥Æ¥Ê¥ó¥¹¤·¤Þ¤¹¡£ + ¾ÜºÙ¤Ï man + ¥Ú¡¼¥¸¤ò¤´Í÷ĺ¤¯¤È¤·¤Æ¡¢´Êñ¤Ë¤Ï:

+ +

½é´ü ID username ¤Ç¡¢Filename + ¤È¤¤¤¦¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë¤òÀ¸À®¤·¤Þ¤¹¡£ + ¼¡¤Î¥³¥Þ¥ó¥É¤òȯ¹Ô¤¹¤ë¤È¥Ñ¥¹¥ï¡¼¥É¤¬Í׵ᤵ¤ì¤Þ¤¹:

+ +

+ htpasswd -c Filename username +

+ +

¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ë Filename ¤Ë¡¢username2 + ¤òÄɲä·¤¿¤ê½¤Àµ¤·¤¿¤ê¤·¤Þ¤¹:

+ +

+ htpasswd Filename username2 +

+ +

(ÌõÃí: Èó¾ï¤Ë¿¤¯¤Î¥æ¡¼¥¶¤òÅÐÏ¿¤¹¤ë¤ÈÂ礭¤Ê¥Õ¥¡¥¤¥ë¤Ë¤Ê¤ê¤Þ¤¹¤¬) + Â礭¤Ê¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤ò¸¡º÷¤¹¤ë¤Î¤ÏÈó¾ï¤Ë¸úΨ¤¬°­¤¤ + ¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤½¤Î¤è¤¦¤ÊɬÍפΤ¢¤ë»þ¤Ï¡¢ + AuthDBMUserFile + ¤òÂå¤ï¤ê¤Ë»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£

+ +

HTTP ¥À¥¤¥¸¥§¥¹¥Èǧ¾Ú¤ò»ÈÍѤ¹¤ë¾ì¹ç¤Ï¡¢ + htpasswd + ¥×¥í¥°¥é¥à¤Ç¤ÏÉÔ½½Ê¬¤Ç¤¹¡£¤½¤ÎÂå¤ï¤ê¤Ë + htdigest + ¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£¥À¥¤¥¸¥§¥¹¥Èǧ¾ÚÍѤΥǡ¼¥¿¤È + ´ðËÜǧ¾ÚÍѤΥǡ¼¥¿¤òƱ°ì¥Õ¥¡¥¤¥ë¤Ëº®¤¼¤ÆÊݸ¤Ç¤­¤Ê¤¤¡¢ + ¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

¥»¥­¥å¥ê¥Æ¥£

+

AuthUserFile + ¤Ï¡¢¥¦¥§¥Ö¥µ¡¼¥Ð¤Î¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼¤Î³°Â¦¤ËÊݴɤ¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + Êݸ¤è¤¦¤È¤·¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê°Ê²¼¤Ë¤Ï¡¢ÃÖ¤«¤Ê¤¤¤Ç²¼¤µ¤¤¡£ + ¤½¤¦¤·¤Ê¤¤¤È AuthUserFile ¤Ï + ¥À¥¦¥ó¥í¡¼¥É¤Ç¤­¤Æ¤·¤Þ¤¤¤Þ¤¹¡£

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authn_file.html.ko.euc-kr b/docs/manual/mod/mod_authn_file.html.ko.euc-kr new file mode 100644 index 00000000..0e2c0b72 --- /dev/null +++ b/docs/manual/mod/mod_authn_file.html.ko.euc-kr @@ -0,0 +1,129 @@ + + + +mod_authn_file - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authn_file

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:¹®ÀÚÆÄÀÏÀ» ÀÌ¿ëÇÑ »ç¿ëÀÚ ÀÎÁõ
»óÅÂ:Base
¸ðµâ¸í:authn_file_module
¼Ò½ºÆÄÀÏ:mod_authn_file.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈÄ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº mod_auth_digest¿Í + mod_auth_basic °°Àº ÀÎÁõ¾Õ´Ü¸ðµâÀ» À§ÇØ + ÀÏ¹Ý ¹®ÀÚ ¾ÏÈ£ÆÄÀÏ¿¡¼­ »ç¿ëÀÚ¸¦ ã¾Æ¼­ ÀÎÁõÇÑ´Ù. + mod_authn_dbm°ú ±â´ÉÀÌ ºñ½ÁÇÏ´Ù.

+ +

mod_auth_basicÀ̳ª + mod_auth_digest¸¦ »ç¿ëÇÒ¶§ AuthBasicProvider³ª + AuthDigestProviderÀÇ + °ªÀ» file·Î ¼³Á¤Çϸé ÀÌ ¸ðµâÀ» »ç¿ëÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

AuthUserFile Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÀÎÁõÇÒ »ç¿ëÀÚ¸í¿Í ¾ÏÈ£ ¸ñ·ÏÀ» ÀúÀåÇÏ´Â ¹®ÀÚÆÄÀϸíÀ» +ÁöÁ¤ÇÑ´Ù
¹®¹ý:AuthUserFile file-path
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Base
¸ðµâ:mod_authn_file
+

AuthUserFile Áö½Ã¾î´Â »ç¿ëÀÚ ÀÎÁõ¿¡ + »ç¿ëÇÒ »ç¿ëÀÚ¸í¿Í ¾ÏÈ£ ¸ñ·ÏÀ» ÀúÀåÇÏ´Â ¹®ÀÚÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù. + File-path´Â ÆÄÀÏ°æ·ÎÀÌ´Ù. Àý´ë°æ·Î¸¦ »ç¿ëÇÏÁö + ¾ÊÀ¸¸é ServerRootÀÇ + »ó´ë°æ·Î·Î ó¸®ÇÑ´Ù.

+ +

ÆÄÀÏÀÇ °¢ ÁÙ¿¡´Â »ç¿ëÀÚ¸í, ÄÝ·Ð, ÀÎÄÚµùµÈ ¾ÏÈ£°¡ ¼ø¼­´ë·Î + ³ª¿Â´Ù. ¿©·¯ ÁÙ¿¡¼­ µ¿ÀÏÇÑ »ç¿ëÀÚ ¾ÆÀ̵𸦠Á¤ÀÇÇϸé, + mod_authn_file´Â ù¹ø°·Î ³ª¿À´Â ¾ÏÈ£¸¦ + »ç¿ëÇÑ´Ù.

+ +

ÄÄÆÄÀÏµÈ ¹èÆ÷º»À̳ª src/support¿¡ ÀÖ´Â htpasswd µµ±¸´Â HTTP + Basic Authentication¿¡ »ç¿ëÇÒ ¾ÏÈ£ÆÄÀÏÀ» °ü¸®ÇÑ´Ù. + ÀÚ¼¼ÇÑ ³»¿ëÀº manpage¸¦ + Âü°íÇ϶ó. ¿ä¾àÇϸé:

+ +

Ãʱ⠾ÆÀ̵ð usernameÀ» °¡Áø ¾ÏÈ£ÆÄÀÏ + FilenameÀ» ¸¸µç´Ù. ¾ÏÈ£¸¦ ¹°¾îº»´Ù:

+ +

+ htpasswd -c Filename username +

+ +

¾ÏÈ£ÆÄÀÏ Filename¿¡ username2¸¦ + Ãß°¡Çϰųª ¼öÁ¤ÇÑ´Ù:

+ +

+ htpasswd Filename username2 +

+ +

Å« ¹®ÀÚÆÄÀÏÀ» °Ë»öÇÏ´Â °ÍÀº ¸Å¿ì ºñÈ¿À²ÀûÀÓÀ» + ÁÖÀÇÇ϶ó. »ç¿ëÀÚ°¡ ¸¹´Ù¸é ´ë½Å AuthDBMUserFileÀ» »ç¿ëÇØ¾ß + ÇÑ´Ù.

+ +

HTTP Digest AuthenticationÀ» »ç¿ëÇÑ´Ù¸é htpasswd µµ±¸·Î ¾ÈµÈ´Ù. + ´ë½Å htdigest¸¦ + »ç¿ëÇØ¾ß ÇÑ´Ù. Digest Authentication°ú Basic AuthenticationÀ» + À§ÇÑ ÀڷḦ °°Àº ÆÄÀÏ¿¡ ¼¯¾î¼­ »ç¿ëÇÒ ¼ö ¾øÀ½À» ÁÖÀÇÇ϶ó.

+ +

º¸¾È

+

AuthUserFileÀÌ À¥¼­¹öÀÇ ¹®¼­µé + ¹Û¿¡ À§Ä¡ÇÔÀ» È®ÀÎÇ϶ó. ÀÌ ÆÄÀÏÀ» º¸È£ÇÒ µð·ºÅ丮 ¾È¿¡ + °°ÀÌ µÎÁö ¸¶¶ó. ±×·¸Áö ¾ÊÀ¸¸é, Ŭ¶óÀ̾ðÆ®°¡ + AuthUserFileÀ» ´Ù¿î·ÎµåÇÒ ¼ö ÀÖ´Ù.

+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authnz_ldap.html b/docs/manual/mod/mod_authnz_ldap.html new file mode 100644 index 00000000..54401c84 --- /dev/null +++ b/docs/manual/mod/mod_authnz_ldap.html @@ -0,0 +1,3 @@ +URI: mod_authnz_ldap.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_authnz_ldap.html.en b/docs/manual/mod/mod_authnz_ldap.html.en new file mode 100644 index 00000000..aadcffcb --- /dev/null +++ b/docs/manual/mod/mod_authnz_ldap.html.en @@ -0,0 +1,940 @@ + + + +mod_authnz_ldap - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authnz_ldap

+
+

Available Languages:  en 

+
+ + + + +
Description:Allows an LDAP directory to be used to store the database +for HTTP Basic authentication.
Status:Extension
Module Identifier:authnz_ldap_module
Source File:mod_authnz_ldap.c
Compatibility:Available in version 2.1 and later
+

Summary

+ +

This module provides authentication front-ends such as + mod_auth_basic to authenticate users through + an ldap directory.

+ +

mod_authnz_ldap supports the following features:

+ +
    +
  • Known to support the OpenLDAP SDK (both 1.x + and 2.x), + Novell LDAP SDK and the iPlanet + (Netscape) SDK.
    • + +
  • Complex authorization policies can be implemented by + representing the policy with LDAP filters.
    • + +
  • Uses extensive caching of LDAP operations via mod_ldap.
    • + +
  • Support for LDAP over SSL (requires the Netscape SDK) or + TLS (requires the OpenLDAP 2.x SDK or Novell LDAP SDK).
    • +
+ +

When using mod_auth_basic, this module is invoked + via the AuthBasicProvider + directive with the ldap value.

+
+ +
top
+
+

Contents

+ + +
top
+
+

Operation

+ +

There are two phases in granting access to a user. The first + phase is authentication, in which the mod_authnz_ldap + authentication provider verifies that the user's credentials are valid. + This is also called the search/bind phase. The second phase is + authorization, in which mod_authnz_ldap determines + if the authenticated user is allowed access to the resource in + question. This is also known as the compare + phase.

+ +

mod_authnz_ldap registers both an authn_ldap authentication + provider and an authz_ldap authorization handler. The authn_ldap + authentication provider can be enabled through the + AuthBasicProvider directive + using the ldap value. The authz_ldap handler extends the + Require directive's authorization types + by adding ldap-user, ldap-dn and ldap-group + values.

+ +

The Authentication + Phase

+ +

During the authentication phase, mod_authnz_ldap + searches for an entry in the directory that matches the username + that the HTTP client passes. If a single unique match is found, + then mod_authnz_ldap attempts to bind to the + directory server using the DN of the entry plus the password + provided by the HTTP client. Because it does a search, then a + bind, it is often referred to as the search/bind phase. Here are + the steps taken during the search/bind phase.

+ +
    +
  1. Generate a search filter by combining the attribute and + filter provided in the AuthLDAPURL directive with + the username passed by the HTTP client.
    2. + +
  2. Search the directory using the generated filter. If the + search does not return exactly one entry, deny or decline + access.
    3. + +
  3. Fetch the distinguished name of the entry retrieved from + the search and attempt to bind to the LDAP server using the + DN and the password passed by the HTTP client. If the bind is + unsuccessful, deny or decline access.
    4. +
+ +

The following directives are used during the search/bind + phase

+ + + + + + + + + + + + + + + + + + + + +
AuthLDAPURLSpecifies the LDAP server, the + base DN, the attribute to use in the search, as well as the + extra search filter to use.
AuthLDAPBindDNAn optional DN to bind with + during the search phase.
AuthLDAPBindPasswordAn optional password to bind + with during the search phase.
+ + +

The Authorization Phase

+ +

During the authorization phase, mod_authnz_ldap + attempts to determine if the user is authorized to access the + resource. Many of these checks require + mod_authnz_ldap to do a compare operation on the + LDAP server. This is why this phase is often referred to as the + compare phase. mod_authnz_ldap accepts the + following Require + directives to determine if the credentials are acceptable:

+ +
    +
  • Grant access if there is a require ldap-user directive, and the + username in the directive matches the username passed by the + client.
    • + +
  • Grant access if there is a require + ldap-dn directive, and the DN in the directive matches + the DN fetched from the LDAP directory.
    • + +
  • Grant access if there is a require ldap-group directive, and + the DN fetched from the LDAP directory (or the username + passed by the client) occurs in the LDAP group.
    • + +
  • Grant access if there is a + require ldap-attribute + directive, and the attribute fetched from the LDAP directory + matches the given value.
    • + +
  • Grant access if there is a + require ldap-filter + directive, and the search filter successfully finds a single user + object that matches the dn of the authenticated user.
    • + +
  • otherwise, deny or decline access
    • +
+ +

Other Require values may also be + used which may require loading additional authorization modules.

+ + + + +

mod_authnz_ldap uses the following directives during the + compare phase:

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
AuthLDAPURL The attribute specified in the + URL is used in compare operations for the require + ldap-user operation.
AuthLDAPCompareDNOnServerDetermines the behavior of the + require ldap-dn directive.
AuthLDAPGroupAttributeDetermines the attribute to + use for comparisons in the require ldap-group + directive.
AuthLDAPGroupAttributeIsDNSpecifies whether to use the + user DN or the username when doing comparisons for the + require ldap-group directive.
+ +
top
+
+

The require Directives

+ +

Apache's Require + directives are used during the authorization phase to ensure that + a user is allowed to access a resource. mod_authnz_ldap extends the + authorization types with ldap-user, ldap-dn, + ldap-group, ldap-attribute and + ldap-filter. Other authorization types may also be + used but may require that additional authorization modules be loaded.

+ +

require valid-user

+ +

If this directive exists, mod_authnz_ldap grants + access to any user that has successfully authenticated during the + search/bind phase. Requires that mod_authz_user be + loaded and that the + AuthzLDAPAuthoritative + directive be set to off.

+ + +

require ldap-user

+ +

The require ldap-user directive specifies what + usernames can access the resource. Once + mod_authnz_ldap has retrieved a unique DN from the + directory, it does an LDAP compare operation using the username + specified in the require ldap-user to see if that username + is part of the just-fetched LDAP entry. Multiple users can be + granted access by putting multiple usernames on the line, + separated with spaces. If a username has a space in it, then it + must be surrounded with double quotes. Multiple users can also be + granted access by using multiple require ldap-user + directives, with one user per line. For example, with a AuthLDAPURL of + ldap://ldap/o=Airius?cn (i.e., cn is + used for searches), the following require directives could be used + to restrict access:

+

+require ldap-user "Barbara Jenson"
+require ldap-user "Fred User"
+require ldap-user "Joe Manager"
+

+ +

Because of the way that mod_authnz_ldap handles this + directive, Barbara Jenson could sign on as Barbara + Jenson, Babs Jenson or any other cn that + she has in her LDAP entry. Only the single require + ldap-user line is needed to support all values of the attribute + in the user's entry.

+ +

If the uid attribute was used instead of the + cn attribute in the URL above, the above three lines + could be condensed to

+

require ldap-user bjenson fuser jmanager

+ + +

require ldap-group

+ +

This directive specifies an LDAP group whose members are + allowed access. It takes the distinguished name of the LDAP + group. Note: Do not surround the group name with quotes. + For example, assume that the following entry existed in + the LDAP directory:

+

+dn: cn=Administrators, o=Airius
+objectClass: groupOfUniqueNames
+uniqueMember: cn=Barbara Jenson, o=Airius
+uniqueMember: cn=Fred User, o=Airius
+

+ +

The following directive would grant access to both Fred and + Barbara:

+

require ldap-group cn=Administrators, o=Airius

+ +

Behavior of this directive is modified by the AuthLDAPGroupAttribute and + AuthLDAPGroupAttributeIsDN + directives.

+ + +

require ldap-dn

+ +

The require ldap-dn directive allows the administrator + to grant access based on distinguished names. It specifies a DN + that must match for access to be granted. If the distinguished + name that was retrieved from the directory server matches the + distinguished name in the require ldap-dn, then + authorization is granted. Note: do not surround the distinguished + name with quotes.

+ +

The following directive would grant access to a specific + DN:

+

require ldap-dn cn=Barbara Jenson, o=Airius

+ +

Behavior of this directive is modified by the AuthLDAPCompareDNOnServer + directive.

+ + +

require ldap-attribute

+ +

The require ldap-attribute directive allows the + administrator to grant access based on attributes of the authenticated + user in the LDAP directory. If the attribute in the directory + matches the value given in the configuration, access is granted.

+ +

The following directive would grant access to anyone with + the attribute employeeType = active

+ +

require ldap-attribute employeeType=active

+ +

Multiple attribute/value pairs can be specified on the same line + separated by spaces or they can be specified in multiple + require ldap-attribute directives. The effect of listing + multiple attribute/values pairs is an OR operation. Access will be + granted if any of the listed attribute values match the value of the + corresponding attribute in the user object. If the value of the + attribute contains a space, only the value must be within double quotes.

+ +

The following directive would grant access to anyone with + the city attribute equal to "San Jose" or status equal to "Active"

+ +

require ldap-attribute city="San Jose" status=active

+ + + +

require ldap-filter

+ +

The require ldap-filter directive allows the + administrator to grant access based on a complex LDAP search filter. + If the dn returned by the filter search matches the authenticated user + dn, access is granted.

+ +

The following directive would grant access to anyone having a cell phone + and is in the marketing department

+ +

require ldap-filter &(cell=*)(department=marketing)

+ +

The difference between the require ldap-filter directive and the + require ldap-attribute directive is that ldap-filter + performs a search operation on the LDAP directory using the specified search + filter rather than a simple attribute comparison. If a simple attribute + comparison is all that is required, the comparison operation performed by + ldap-attribute will be faster than the search operation + used by ldap-filter especially within a large directory.

+ + + +
top
+
+

Examples

+ +
    +
  • + Grant access to anyone who exists in the LDAP directory, + using their UID for searches. +

    +AuthLDAPURL ldap://ldap1.airius.com:389/ou=People, o=Airius?uid?sub?(objectClass=*)
    +require valid-user +

    +
    • + +
  • + The next example is the same as above; but with the fields + that have useful defaults omitted. Also, note the use of a + redundant LDAP server. +

    AuthLDAPURL ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius
    +require valid-user +

    +
    • + +
  • + The next example is similar to the previous one, but it + uses the common name instead of the UID. Note that this + could be problematical if multiple people in the directory + share the same cn, because a search on cn + must return exactly one entry. That's why + this approach is not recommended: it's a better idea to + choose an attribute that is guaranteed unique in your + directory, such as uid. +

    +AuthLDAPURL ldap://ldap.airius.com/ou=People, o=Airius?cn
    +require valid-user +

    +
    • + +
  • + Grant access to anybody in the Administrators group. The + users must authenticate using their UID. +

    +AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid
    +require ldap-group cn=Administrators, o=Airius +

    +
    • + +
  • + The next example assumes that everyone at Airius who + carries an alphanumeric pager will have an LDAP attribute + of qpagePagerID. The example will grant access + only to people (authenticated via their UID) who have + alphanumeric pagers: +

    +AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(qpagePagerID=*)
    +require valid-user +

    +
    • + +
  • +

    The next example demonstrates the power of using filters + to accomplish complicated administrative requirements. + Without filters, it would have been necessary to create a + new LDAP group and ensure that the group's members remain + synchronized with the pager users. This becomes trivial + with filters. The goal is to grant access to anyone who has + a pager, plus grant access to Joe Manager, who doesn't + have a pager, but does need to access the same + resource:

    +

    +AuthLDAPURL ldap://ldap.airius.com/o=Airius?uid??(|(qpagePagerID=*)(uid=jmanager))
    +require valid-user +

    + +

    This last may look confusing at first, so it helps to + evaluate what the search filter will look like based on who + connects, as shown below. If + Fred User connects as fuser, the filter would look + like

    + +

    (&(|(qpagePagerID=*)(uid=jmanager))(uid=fuser))

    + +

    The above search will only succeed if fuser has a + pager. When Joe Manager connects as jmanager, the + filter looks like

    + +

    (&(|(qpagePagerID=*)(uid=jmanager))(uid=jmanager))

    + +

    The above search will succeed whether jmanager + has a pager or not.

    +
    • +
+
top
+
+

Using TLS

+ +

To use TLS, see the mod_ldap directives LDAPTrustedClientCert, LDAPTrustedGlobalCert and LDAPTrustedMode.

+ +

An optional second parameter can be added to the + AuthLDAPURL to override + the default connection type set by LDAPTrustedMode. + This will allow the connection established by an ldap:// Url + to be upgraded to a secure connection on the same port.

+
top
+
+

Using SSL

+ +

To use SSL, see the mod_ldap directives LDAPTrustedClientCert, LDAPTrustedGlobalCert and LDAPTrustedMode.

+ +

To specify a secure LDAP server, use ldaps:// in the + AuthLDAPURL + directive, instead of ldap://.

+
top
+
+

Using Microsoft + FrontPage with mod_authnz_ldap

+ +

Normally, FrontPage uses FrontPage-web-specific user/group + files (i.e., the mod_authn_file and + mod_authz_groupfile modules) to handle all + authentication. Unfortunately, it is not possible to just + change to LDAP authentication by adding the proper directives, + because it will break the Permissions forms in + the FrontPage client, which attempt to modify the standard + text-based authorization files.

+ +

Once a FrontPage web has been created, adding LDAP + authentication to it is a matter of adding the following + directives to every .htaccess file + that gets created in the web

+
+AuthLDAPURL            "the url"
+AuthzLDAPAuthoritative off
+AuthGroupFile mygroupfile
+require group mygroupfile
+
+ +

AuthzLDAPAuthoritative + must be off to allow mod_authnz_ldap to decline group + authentication so that Apache will fall back to file + authentication for checking group membership. This allows the + FrontPage-managed group file to be used.

+ +

How It Works

+ +

FrontPage restricts access to a web by adding the require + valid-user directive to the .htaccess + files. The require valid-user directive will succeed for + any user who is valid as far as LDAP is + concerned. This means that anybody who has an entry in + the LDAP directory is considered a valid user, whereas FrontPage + considers only those people in the local user file to be + valid. By substituting the ldap-group with group file authorization, + Apache is allowed to consult the local user file (which is managed by + FrontPage) - instead of LDAP - when handling authorizing the user.

+ +

Once directives have been added as specified above, + FrontPage users will be able to perform all management + operations from the FrontPage client.

+ + +

Caveats

+ +
    +
  • When choosing the LDAP URL, the attribute to use for + authentication should be something that will also be valid + for putting into a mod_authn_file user file. + The user ID is ideal for this.
    • + +
  • When adding users via FrontPage, FrontPage administrators + should choose usernames that already exist in the LDAP + directory (for obvious reasons). Also, the password that the + administrator enters into the form is ignored, since Apache + will actually be authenticating against the password in the + LDAP database, and not against the password in the local user + file. This could cause confusion for web administrators.
    • + + +
  • Apache must be compiled with mod_auth_basic, + mod_authn_file and + mod_authz_groupfile in order to + use FrontPage support. This is because Apache will still use + the mod_authz_groupfile group file for determine + the extent of a user's access to the FrontPage web.
    • + +
  • The directives must be put in the .htaccess + files. Attempting to put them inside <Location> or <Directory> directives won't work. This + is because mod_authnz_ldap has to be able to grab + the AuthGroupFile + directive that is found in FrontPage .htaccess + files so that it knows where to look for the valid user list. If + the mod_authnz_ldap directives aren't in the same + .htaccess file as the FrontPage directives, then + the hack won't work, because mod_authnz_ldap will + never get a chance to process the .htaccess file, + and won't be able to find the FrontPage-managed user file.
    • +
+ +
+
top
+

AuthLDAPBindDN Directive

+ + + + + + + +
Description:Optional DN to use in binding to the LDAP server
Syntax:AuthLDAPBindDN distinguished-name
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

An optional DN used to bind to the server when searching for + entries. If not provided, mod_authnz_ldap will use + an anonymous bind.

+ +
+
top
+

AuthLDAPBindPassword Directive

+ + + + + + + +
Description:Password used in conjuction with the bind DN
Syntax:AuthLDAPBindPassword password
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

A bind password to use in conjunction with the bind DN. Note + that the bind password is probably sensitive data, and should be + properly protected. You should only use the AuthLDAPBindDN and AuthLDAPBindPassword if you + absolutely need them to search the directory.

+ +
+
top
+

AuthLDAPCharsetConfig Directive

+ + + + + + +
Description:Language to charset conversion configuration file
Syntax:AuthLDAPCharsetConfig file-path
Context:server config
Status:Extension
Module:mod_authnz_ldap
+

The AuthLDAPCharsetConfig directive sets the location + of the language to charset conversion configuration file. File-path is relative + to the ServerRoot. This file specifies + the list of language extensions to character sets. + Most administrators use the provided charset.conv + file, which associates common language extensions to character sets.

+ +

The file contains lines in the following format:

+ +

+ Language-Extension charset [Language-String] ... +

+ +

The case of the extension does not matter. Blank lines, and lines + beginning with a hash character (#) are ignored.

+ +
+
top
+

AuthLDAPCompareDNOnServer Directive

+ + + + + + + + +
Description:Use the LDAP server to compare the DNs
Syntax:AuthLDAPCompareDNOnServer on|off
Default:AuthLDAPCompareDNOnServer on
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

When set, mod_authnz_ldap will use the LDAP + server to compare the DNs. This is the only foolproof way to + compare DNs. mod_authnz_ldap will search the + directory for the DN specified with the require dn directive, then, + retrieve the DN and compare it with the DN retrieved from the user + entry. If this directive is not set, + mod_authnz_ldap simply does a string comparison. It + is possible to get false negatives with this approach, but it is + much faster. Note the mod_ldap cache can speed up + DN comparison in most situations.

+ +
+
top
+

AuthLDAPDereferenceAliases Directive

+ + + + + + + + +
Description:When will the module de-reference aliases
Syntax:AuthLDAPDereferenceAliases never|searching|finding|always
Default:AuthLDAPDereferenceAliases Always
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

This directive specifies when mod_authnz_ldap will + de-reference aliases during LDAP operations. The default is + always.

+ +
+
top
+

AuthLDAPGroupAttribute Directive

+ + + + + + + +
Description:LDAP attributes used to check for group membership
Syntax:AuthLDAPGroupAttribute attribute
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

This directive specifies which LDAP attributes are used to + check for group membership. Multiple attributes can be used by + specifying this directive multiple times. If not specified, + then mod_authnz_ldap uses the member and + uniquemember attributes.

+ +
+
top
+

AuthLDAPGroupAttributeIsDN Directive

+ + + + + + + + +
Description:Use the DN of the client username when checking for +group membership
Syntax:AuthLDAPGroupAttributeIsDN on|off
Default:AuthLDAPGroupAttributeIsDN on
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

When set on, this directive says to use the + distinguished name of the client username when checking for group + membership. Otherwise, the username will be used. For example, + assume that the client sent the username bjenson, + which corresponds to the LDAP DN cn=Babs Jenson, + o=Airius. If this directive is set, + mod_authnz_ldap will check if the group has + cn=Babs Jenson, o=Airius as a member. If this + directive is not set, then mod_authnz_ldap will + check if the group has bjenson as a member.

+ +
+
top
+

AuthLDAPRemoteUserIsDN Directive

+ + + + + + + + +
Description:Use the DN of the client username to set the REMOTE_USER +environment variable
Syntax:AuthLDAPRemoteUserIsDN on|off
Default:AuthLDAPRemoteUserIsDN off
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

If this directive is set to on, the value of the + REMOTE_USER environment variable will be set to the full + distinguished name of the authenticated user, rather than just + the username that was passed by the client. It is turned off by + default.

+ +
+
top
+

AuthLDAPUrl Directive

+ + + + + + + +
Description:URL specifying the LDAP search parameters
Syntax:AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

An RFC 2255 URL which specifies the LDAP search parameters + to use. The syntax of the URL is

+

ldap://host:port/basedn?attribute?scope?filter

+ +
+
ldap
+ +
For regular ldap, use the + string ldap. For secure LDAP, use ldaps + instead. Secure LDAP is only available if Apache was linked + to an LDAP library with SSL support.
+ +
host:port
+ +
+

The name/port of the ldap server (defaults to + localhost:389 for ldap, and + localhost:636 for ldaps). To + specify multiple, redundant LDAP servers, just list all + servers, separated by spaces. mod_authnz_ldap + will try connecting to each server in turn, until it makes a + successful connection.

+ +

Once a connection has been made to a server, that + connection remains active for the life of the + httpd process, or until the LDAP server goes + down.

+ +

If the LDAP server goes down and breaks an existing + connection, mod_authnz_ldap will attempt to + re-connect, starting with the primary server, and trying + each redundant server in turn. Note that this is different + than a true round-robin search.

+
+ +
basedn
+ +
The DN of the branch of the + directory where all searches should start from. At the very + least, this must be the top of your directory tree, but + could also specify a subtree in the directory.
+ +
attribute
+ +
The attribute to search for. + Although RFC 2255 allows a comma-separated list of + attributes, only the first attribute will be used, no + matter how many are provided. If no attributes are + provided, the default is to use uid. It's a good + idea to choose an attribute that will be unique across all + entries in the subtree you will be using.
+ +
scope
+ +
The scope of the search. Can be either one or + sub. Note that a scope of base is + also supported by RFC 2255, but is not supported by this + module. If the scope is not provided, or if base scope + is specified, the default is to use a scope of + sub.
+ +
filter
+ +
A valid LDAP search filter. If + not provided, defaults to (objectClass=*), which + will search for all objects in the tree. Filters are + limited to approximately 8000 characters (the definition of + MAX_STRING_LEN in the Apache source code). This + should be than sufficient for any application.
+
+ +

When doing searches, the attribute, filter and username passed + by the HTTP client are combined to create a search filter that + looks like + (&(filter)(attribute=username)).

+ +

For example, consider an URL of + ldap://ldap.airius.com/o=Airius?cn?sub?(posixid=*). When + a client attempts to connect using a username of Babs + Jenson, the resulting search filter will be + (&(posixid=*)(cn=Babs Jenson)).

+ +

An optional parameter can be added to allow the LDAP Url to override + the connection type. This parameter can be one of the following:

+ +
+
NONE
+
Establish an unsecure connection on the default LDAP port. This + is the same as ldap:// on port 389.
+
SSL
+
Establish a secure connection on the default secure LDAP port. + This is the same as ldaps://
+
TLS | STARTTLS
+
Establish an upgraded secure connection on the default LDAP port. + This connection will be initiated on port 389 by default and then + upgraded to a secure connection on the same port.
+
+ +

See above for examples of AuthLDAPURL URLs.

+ +
+
top
+

AuthzLDAPAuthoritative Directive

+ + + + + + + + +
Description:Prevent other authentication modules from +authenticating the user if this one fails
Syntax:AuthzLDAPAuthoritative on|off
Default:AuthzLDAPAuthoritative on
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authnz_ldap
+

Set to off if this module should let other + authentication modules attempt to authenticate the user, should + authentication with this module fail. Control is only passed on + to lower modules if there is no DN or rule that matches the + supplied user name (as passed by the client).

+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_dbm.html b/docs/manual/mod/mod_authz_dbm.html new file mode 100644 index 00000000..5b5cdad6 --- /dev/null +++ b/docs/manual/mod/mod_authz_dbm.html @@ -0,0 +1,7 @@ +URI: mod_authz_dbm.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authz_dbm.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authz_dbm.html.en b/docs/manual/mod/mod_authz_dbm.html.en new file mode 100644 index 00000000..52f34b6d --- /dev/null +++ b/docs/manual/mod/mod_authz_dbm.html.en @@ -0,0 +1,185 @@ + + + +mod_authz_dbm - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authz_dbm

+
+

Available Languages:  en  | + ko 

+
+ + + + +
Description:Group authorization using DBM files
Status:Extension
Module Identifier:authz_dbm_module
Source File:mod_authz_dbm.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module provides authorization capabilities so that + authenticated users can be allowed or denied access to portions + of the web site by group membership. Similar functionality is + provided by mod_authz_groupfile.

+
+ + +
top
+

AuthDBMGroupFile Directive

+ + + + + + + +
Description:Sets the name of the database file containing the list +of user groups for authorization
Syntax:AuthDBMGroupFile file-path
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authz_dbm
+

The AuthDBMGroupFile directive sets the + name of a DBM file containing the list of user groups for user + authorization. File-path is the absolute path to the + group file.

+ +

The group file is keyed on the username. The value for a + user is a comma-separated list of the groups to which the users + belongs. There must be no whitespace within the value, and it + must never contain any colons.

+ +

Security

+

Make sure that the AuthDBMGroupFile is + stored outside the document tree of the web-server. Do + not put it in the directory that it protects. + Otherwise, clients will be able to download the + AuthDBMGroupFile unless otherwise + protected.

+
+ +

Combining Group and Password DBM files: In some cases it is + easier to manage a single database which contains both the + password and group details for each user. This simplifies any + support programs that need to be written: they now only have to + deal with writing to and locking a single DBM file. This can be + accomplished by first setting the group and password files to + point to the same DBM:

+ +

+ AuthDBMGroupFile /www/userbase
+ AuthDBMUserFile /www/userbase +

+ +

The key for the single DBM is the username. The value consists + of

+ +

+ Encrypted Password : List of Groups [ : (ignored) ] +

+ +

The password section contains the encrypted + password as before. This is followed by a colon and the comma + separated list of groups. Other data may optionally be left in the + DBM file after another colon; it is ignored by the authorization + module. This is what www.telescope.org uses for its combined + password and group database.

+ +
+
top
+

AuthzDBMAuthoritative Directive

+ + + + + + + + +
Description:Sets whether authorization will be passed on to lower level +modules
Syntax:AuthzDBMAuthoritative On|Off
Default:AuthzDBMAuthoritative On
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authz_dbm
+

Setting the AuthzDBMAuthoritative + directive explicitly to Off allows group authorization + to be passed on to lower level modules (as defined in the + modules.c file) if there is no group found + for the the supplied userID. If there are any groups + specified, the usual checks will be applied and a failure will + give an Authentication Required reply.

+ +

So if a userID appears in the database of more than one module; + or if a valid Require + directive applies to more than one module; then the first module + will verify the credentials; and no access is passed on; + regardless of the AuthAuthoritative setting.

+ +

A common use for this is in conjunction with one of the + auth providers; such as mod_authn_dbm or + mod_authn_file. Whereas this DBM module supplies + the bulk of the user credential checking; a few (administrator) related + accesses fall through to a lower level with a well protected + .htpasswd file.

+ +

By default, control is not passed on and an unknown group + will result in an Authentication Required reply. Not + setting it thus keeps the system secure and forces an NCSA + compliant behaviour.

+ +

Security

+

Do consider the implications of allowing a user to + allow fall-through in his .htaccess file; and verify that this + is really what you want; Generally it is easier to just secure + a single .htpasswd file, than it is to secure a + database which might have more access interfaces.

+
+ +
+
top
+

AuthzDBMType Directive

+ + + + + + + + +
Description:Sets the type of database file that is used to +store list of user groups
Syntax:AuthzDBMType default|SDBM|GDBM|NDBM|DB
Default:AuthzDBMType default
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authz_dbm
+

Sets the type of database file that is used to store the list + of user groups. + The default database type is determined at compile time. The + availability of other types of database files also depends on + compile-time settings.

+ +

It is crucial that whatever program you use to create your group + files is configured to use the same type of database.

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_dbm.html.ko.euc-kr b/docs/manual/mod/mod_authz_dbm.html.ko.euc-kr new file mode 100644 index 00000000..e8cee8ec --- /dev/null +++ b/docs/manual/mod/mod_authz_dbm.html.ko.euc-kr @@ -0,0 +1,170 @@ + + + +mod_authz_dbm - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authz_dbm

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:DBM ÆÄÀÏÀ» »ç¿ëÇÑ ±×·ì ÀÎÁõ
»óÅÂ:Extension
¸ðµâ¸í:authz_dbm_module
¼Ò½ºÆÄÀÏ:mod_authz_dbm.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ÀÎÁõÇÑ »ç¿ëÀÚÀÇ ±×·ì±ÇÇÑÀ¸·Î À¥ÀÇ ÀϺθ¦ Á¢±ÙÇÒ + ¼ö ÀÖ´ÂÁö °áÁ¤ÇÏ¿© ±ÇÇѺο©¸¦ ÇÑ´Ù. + mod_authz_groupfile°ú ±â´ÉÀÌ ºñ½ÁÇÏ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

AuthDBMGroupFile Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÀÎÁõ¿¡ »ç¿ëÇÒ »ç¿ëÀÚ ±×·ì ¸ñ·ÏÀ» ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º +ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù
¹®¹ý:AuthDBMGroupFile file-path
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authz_dbm
+

AuthDBMGroupFile Áö½Ã¾î´Â ÀÎÁõ¿¡ + »ç¿ëÇÒ »ç¿ëÀÚ ±×·ì ¸ñ·ÏÀ» ÀúÀåÇÏ´Â DBM ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù. + File-path´Â ÆÄÀÏÀÇ Àý´ë°æ·ÎÀÌ´Ù.

+ +

ÆÄÀÏÀº »ç¿ëÀÚ¸íÀ» Å°·Î »ç¿ëÇÑ´Ù. »ç¿ëÀÚ¿¡ ´ëÇÑ °ªÀº ½°Ç¥·Î + ±¸ºÐÇÑ »ç¿ëÀÚ°¡ ¼ÓÇÑ ±×·ì ¸ñ·ÏÀÌ´Ù. °ª¿¡ °ø¹éÀ̳ª ÄÝ·ÐÀ» + »ç¿ëÇÒ ¼ö ¾ø´Ù.

+ +

º¸¾È

+

AuthDBMGroupFileÀÌ À¥¼­¹öÀÇ + ¹®¼­µé ¹Û¿¡ À§Ä¡ÇÔÀ» È®ÀÎÇ϶ó. ÀÌ ÆÄÀÏÀ» º¸È£ÇÒ µð·ºÅ丮 + ¾È¿¡ °°ÀÌ µÎÁö ¸¶¶ó. ±×·¸Áö ¾ÊÀ¸¸é, Ŭ¶óÀ̾ðÆ®°¡ + AuthDBMGroupFile¸¦ ´Ù¿î·ÎµåÇÒ ¼ö + ÀÖ´Ù.

+
+ +

±×·ì DBM ÆÄÀÏ°ú ¾ÏÈ£ DBM ÆÄÀÏÀ» °°ÀÌ »ç¿ëÇϱâ: »ç¿ëÀÚ¿¡ + ´ëÇÑ ¾ÏÈ£¿Í ±×·ì Á¤º¸ ¸ðµÎ¸¦ ÇÑ µ¥ÀÌÅͺ£À̽º¿¡¼­ °ü¸®ÇÏ´Â + °ÍÀÌ ½¬¿ï¶§°¡ ÀÖ´Ù. ÀÌ °æ¿ì ÀÛ¼ºÇÒ Áö¿ø ÇÁ·Î±×·¥ÀÌ °£´ÜÇØÁø´Ù. + ÇÁ·Î±×·¥Àº ÇÑ DBM ÆÄÀϸ¸À» Àá±×°í ¾²¸é µÈ´Ù. ±×·ìÆÄÀÏ°ú + ¾ÏÈ£ÆÄÀÏÀ» °°Àº DBMÆÄÀÏ·Î ¼³Á¤ÇÏ¸é °¡´ÉÇÏ´Ù:

+ +

+ AuthDBMGroupFile /www/userbase
+ AuthDBMUserFile /www/userbase +

+ +

ÀÌ ÅëÇÕ DBMÀÇ Å°´Â »ç¿ëÀÚ¸íÀÌ´Ù. °ªÀº ´ÙÀ½°ú °°´Ù

+ +

+ ÀÎÄÚµùµÈ ¾ÏÈ£ : ±×·ì ¸ñ·Ï [ : (¹«½Ã) ] +

+ +

¾ÏÈ£ ºÎºÐÀº Àü°ú °°ÀÌ ÀÎÄÚµùµÈ ¾ÏÈ£ÀÌ´Ù. ÄÝ·Ð µÚ¿¡ ½°Ç¥·Î + ±¸ºÐÇÑ ±×·ì ¸ñ·ÏÀÌ ³ª¿Â´Ù. ¶Ç ´Ù½Ã ÄÝ·Ð ´ÙÀ½¿¡ ´Ù¸¥ Á¤º¸¸¦ + ±â·ÏÇÒ ¼ö ÀÖ´Ù. ÀÌ ºÎºÐÀº ÀÎÁõ¸ðµâÀÌ ¹«½ÃÇÑ´Ù. + www.telescope.org´Â ÀÌ·¸°Ô ¾ÏÈ£ µ¥ÀÌÅͺ£À̽º¿Í ±×·ì + µ¥ÀÌÅͺ£À̽º¸¦ °°ÀÌ »ç¿ëÇÑ´Ù.

+ +
+
top
+

AuthzDBMAuthoritative Áö½Ã¾î

+ + + + + + + + +
¼³¸í:±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
¹®¹ý:AuthzDBMAuthoritative On|Off
±âº»°ª:AuthzDBMAuthoritative On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authz_dbm
+

AuthzDBMAuthoritative Áö½Ã¾î¸¦ + Á÷Á¢ Off·Î ¼³Á¤Çϸé ÇØ´ç »ç¿ëÀÚ ¾ÆÀ̵𿡠´ëÇÑ + ±×·ìÀÌ ¾ø´Â °æ¿ì ±×·ì ±ÇÇѺο©¸¦ (modules.c + ÆÄÀÏ¿¡¼­ Á¤ÀÇÇÑ) Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁØ´Ù. ÁöÁ¤ÇÑ ±×·ìÀÌ ÀÖ´Ù¸é + º¸Å붧¿Í °°ÀÌ °Ë»çÇÏ°í, ½ÇÆÐÇϸé ÀÎÁõ ÇÊ¿ä ÀÀ´äÀ» ÇÑ´Ù.

+ +

±×·¡¼­ ¿©·¯ ¸ðµâÀÇ µ¥ÀÌÅͺ£À̽º¿¡ »ç¿ëÀÚ ¾ÆÀ̵𰡠Àְųª + À¯È¿ÇÑ Require Áö½Ã¾î¸¦ + ¿©·¯ ¸ðµâ¿¡ Àû¿ëÇϸé, ù¹ø° ¸ðµâÀÌ »ç¿ëÀÚ¸¦ °Ë»çÇÏ°í, + AuthAuthoritative ¼³Á¤°ú °ü°è¾øÀÌ + Á¢±ÙÀ» ³Ñ±âÁö¾Ê´Â´Ù.

+ +

ÀϹÝÀûÀ¸·Î mod_authn_dbmÀ̳ª + mod_authn_file°ú °°Àº ÀÎÁõÁ¦°øÀÚ¿Í °°ÀÌ + »ç¿ëÇÑ´Ù. ´ë·®ÀÇ »ç¿ëÀÚ °Ë»ç¿¡ ´ëÇÑ °Ë»ç´Â DBM ¸ðµâÀ» + »ç¿ëÇÏÁö¸¸, ¼Ò¼ö(°ü¸®ÀÚ)¿¡ ´ëÇÑ °Ë»ç´Â Àß º¸È£µÈ + .htpasswd ÆÄÀÏ·Î ³Ñ±ä´Ù.

+ +

±âº»ÀûÀ¸·Î Á¦¾î¸¦ ³Ñ±âÁö¾Ê°í, ¸ð¸£´Â ±×·ìÀÇ °æ¿ì ÀÎÁõ + ÇÊ¿ä ÀÀ´äÀ» ÇÑ´Ù. ÀÌ Áö½Ã¾î¸¦ ¼³Á¤ÇÏÁö¾ÊÀ¸¸é ½Ã½ºÅÛÀÌ ¾ÈÀüÇÏ°Ô + À¯ÁöµÇ¸ç, NCSA À¥¼­¹ö¿Í °°ÀÌ µ¿ÀÛÇÑ´Ù.

+ +

º¸¾È

+

»ç¿ëÀÚ°¡ ÀÚ½ÅÀÇ .htaccess ÆÄÀÏÀ» »ç¿ëÇÏ°Ô µÇ´ÂÁö »ìÆ캸°í, + ÀÌ·± ÇൿÀ» Çã¿ëÇÒÁö °áÁ¤Ç϶ó. ÀϹÝÀûÀ¸·Î ¿©·¯°¡Áö ¹æ¹ýÀ¸·Î + Á¢±ÙÇÒ ¼ö ÀÖ´Â µ¥ÀÌÅͺ£À̽º¸¦ º¸È£ÇÏ´Â °Íº¸´Ù ÇϳªÀÇ + .htpasswd ÆÄÀÏÀ» º¸È£ÇÏ´Â °ÍÀÌ ´õ ½±´Ù.

+
+ +
+
top
+

AuthzDBMType Áö½Ã¾î

+ + + + + + + + +
¼³¸í:¾ÏÈ£¸¦ ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º ÆÄÀÏ Á¾·ù¸¦ ÁöÁ¤ÇÑ´Ù
¹®¹ý:AuthzDBMType default|SDBM|GDBM|NDBM|DB
±âº»°ª:AuthzDBMType default
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authz_dbm
+

¾ÏÈ£¸¦ ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º ÆÄÀÏ Á¾·ù¸¦ ÁöÁ¤ÇÑ´Ù. + µ¥ÀÌÅͺ£À̽º Á¾·ù ±âº»°ªÀº ÄÄÆÄÀ϶§ Á¤ÇØÁø´Ù. »ç¿ëÇÒ ¼ö + ÀÖ´Â ´Ù¸¥ µ¥ÀÌÅͺ£À̽º ÆÄÀÏ Á¾·ùµµ ÄÄÆÄÀÏ ¼³Á¤¿¡ ´Þ·È´Ù.

+ +

¾ÏÈ£ÆÄÀÏÀ» ¸¸µç ÇÁ·Î±×·¥ÀÌ °°Àº Á¾·ùÀÇ µ¥ÀÌÅͺ£À̽º¸¦ + »ç¿ëÇϵµ·Ï ¼³Á¤ÇØ¾ß ÇÑ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_default.html b/docs/manual/mod/mod_authz_default.html new file mode 100644 index 00000000..612b1b68 --- /dev/null +++ b/docs/manual/mod/mod_authz_default.html @@ -0,0 +1,11 @@ +URI: mod_authz_default.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authz_default.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authz_default.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authz_default.html.en b/docs/manual/mod/mod_authz_default.html.en new file mode 100644 index 00000000..5c73dc4c --- /dev/null +++ b/docs/manual/mod/mod_authz_default.html.en @@ -0,0 +1,80 @@ + + + +mod_authz_default - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authz_default

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Authorization fallback module
Status:Base
Module Identifier:authz_default_module
Source File:mod_authz_default.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module is designed to be the fallback module, if you don't + have configured an authorization module like + mod_authz_user or mod_authz_groupfile. + It simply rejects any authorization request.

+
+

Directives

+ +
+ +
top
+

AuthzDefaultAuthoritative Directive

+ + + + + + + + +
Description:Sets whether authorization is passed to lower level +modules
Syntax:AuthzDefaultAuthoritative On|Off
Default:AuthzDefaultAuthoritative On
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_authz_default
+

Setting the AuthzDefaultAuthoritative directive + explicitly to Off allows for authorization to be passed on + to lower level modules (as defined in the modules.c + files).

+ +

Note

+

Normally there are no lower level modules, since + mod_authz_default is defined to be already on + a very low level. Therefore you should leave the value of + AuthzDefaultAuthoritative as default + (On).

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_default.html.ja.euc-jp b/docs/manual/mod/mod_authz_default.html.ja.euc-jp new file mode 100644 index 00000000..0b4f4ca4 --- /dev/null +++ b/docs/manual/mod/mod_authz_default.html.ja.euc-jp @@ -0,0 +1,79 @@ + + + +mod_authz_default - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authz_default

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:¾µÇ§¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¥â¥¸¥å¡¼¥ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authz_default_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authz_default.c
¸ß´¹À­:Apache 2.1 °Ê¹ß
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï mod_authz_user ¤ä + mod_authz_groupfile ¤È¤¤¤Ã¤¿¾µÇ§¥â¥¸¥å¡¼¥ë¤ò + ÀßÄꤷ¤Ê¤«¤Ã¤¿¾ì¹ç¤Î¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¥â¥¸¥å¡¼¥ë¤È¤·¤ÆÀ߷פµ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤É¤Î¤è¤¦¤Ê¾µÇ§¥ê¥¯¥¨¥¹¥È¤âñ¤ËµñÈݤ·¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +
+ +
top
+

AuthzDefaultAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¾µÇ§¤¬Äã°Ì¤Î¥â¥¸¥å¡¼¥ë¤ËÅϤµ¤ì¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
¹½Ê¸:AuthzDefaultAuthoritative On|Off
¥Ç¥Õ¥©¥ë¥È:AuthzDefaultAuthoritative On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authz_default
+

AuthzDefaultAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ÌÀ¼¨Åª¤Ë Off ¤ËÀßÄꤹ¤ë¤È + ǧ¾Ú¤ò¼¡¤Î (modules.c ¥Õ¥¡¥¤¥ë¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë) + Äã°Ì¤Î¥â¥¸¥å¡¼¥ë¤ËÅϤ¹¤³¤È¤òµö²Ä¤·¤Þ¤¹¡£

+ +

Ãí°Õ

+

mod_authz_default ¼«ÂΤ¬¤È¤Æ¤âÄ㤤 + ¥ì¥Ù¥ë¤È¤·¤ÆÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢Ä̾ï¤Ï¤³¤ì¤è¤ê¤âÄ㼡¤Î + ¥â¥¸¥å¡¼¥ë¤Ï¸ºß¤·¤Þ¤»¤ó¡£¤Ç¤¹¤«¤é + AuthDefaultAuthoritative ¤Ï¥Ç¥Õ¥©¥ë¥È + (On) ¤Î¤Þ¤Þ¤Ë¤·¤¿¤Û¤¦¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_default.html.ko.euc-kr b/docs/manual/mod/mod_authz_default.html.ko.euc-kr new file mode 100644 index 00000000..b0146297 --- /dev/null +++ b/docs/manual/mod/mod_authz_default.html.ko.euc-kr @@ -0,0 +1,78 @@ + + + +mod_authz_default - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authz_default

+
+

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

+
+ + + + +
¼³¸í:ÃÖÈÄ ±ÇÇѺο©¸ðµâ
»óÅÂ:Base
¸ðµâ¸í:authz_default_module
¼Ò½ºÆÄÀÏ:mod_authz_default.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº mod_authz_user³ª + mod_authz_groupfile¿Í °°Àº ±ÇÇѺο©¸ðµâÀ» + ¼³Á¤ÇÏÁö¾ÊÀº ÃÖÈÄÀÇ °æ¿ì ´ë½Å »ç¿ëÇÑ´Ù. ÀÌ ¸ðµâÀº ¸ðµç ±ÇÇѺο© + ¿äûÀ» °ÅºÎÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +
+ +
top
+

AuthzDefaultAuthoritative Áö½Ã¾î

+ + + + + + + + +
¼³¸í:±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
¹®¹ý:AuthzDefaultAuthoritative On|Off
±âº»°ª:AuthzDefaultAuthoritative On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Base
¸ðµâ:mod_authz_default
+

AuthzDefaultAuthoritative Áö½Ã¾î¸¦ + Á÷Á¢ Off·Î ¼³Á¤Çϸé (modules.c + ÆÄÀÏ¿¡¼­ Á¤ÀÇÇÑ) Àú¼öÁØ ¸ðµâ·Î ±ÇÇѺο©¸¦ ³Ñ°ÜÁØ´Ù.

+ +

ÁÖÀÇ

+

mod_authz_default°¡ ÀÌ¹Ì ¸Å¿ì + Àú¼öÁØÀ¸·Î Á¤ÀǵÇÀֱ⠶§¹®¿¡ º¸Åë ´õ ³·Àº ¸ðµâÀÌ + ¾ø´Ù. ±×·¯¹Ç·Î + AuthzDefaultAuthoritative¸¦ + ±âº»°ª(On)À¸·Î ³²°ÜµÖ¾ß ÇÑ´Ù.

+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_groupfile.html b/docs/manual/mod/mod_authz_groupfile.html new file mode 100644 index 00000000..eae1ea35 --- /dev/null +++ b/docs/manual/mod/mod_authz_groupfile.html @@ -0,0 +1,11 @@ +URI: mod_authz_groupfile.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authz_groupfile.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authz_groupfile.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authz_groupfile.html.en b/docs/manual/mod/mod_authz_groupfile.html.en new file mode 100644 index 00000000..f0919d25 --- /dev/null +++ b/docs/manual/mod/mod_authz_groupfile.html.en @@ -0,0 +1,125 @@ + + + +mod_authz_groupfile - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authz_groupfile

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Group authorization using plaintext files
Status:Base
Module Identifier:authz_groupfile_module
Source File:mod_authz_groupfile.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module provides authorization capabilities so that + authenticated users can be allowed or denied access to portions + of the web site by group membership. Similar functionality is + provided by mod_authz_dbm.

+
+

Directives

+ +

See also

+
+ +
top
+

AuthGroupFile Directive

+ + + + + + + +
Description:Sets the name of a text file containing the list +of user groups for authorization
Syntax:AuthGroupFile file-path
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_authz_groupfile
+

The AuthGroupFile directive sets the + name of a textual file containing the list of user groups for user + authorization. File-path is the path to the group + file. If it is not absolute, it is treated as relative to the ServerRoot.

+ +

Each line of the group file contains a groupname followed by a + colon, followed by the member usernames separated by spaces.

+ +

Example:

+ mygroup: bob joe anne +

+ +

Note that searching large text files is very + inefficient; AuthDBMGroupFile provides a much better performance.

+ +

Security

+

Make sure that the AuthGroupFile is + stored outside the document tree of the web-server; do not + put it in the directory that it protects. Otherwise, clients may + be able to download the AuthGroupFile.

+
+ +
+
top
+

AuthzGroupFileAuthoritative Directive

+ + + + + + + + +
Description:Sets whether authorization will be passed on to lower level +modules
Syntax:AuthzGroupFileAuthoritative On|Off
Default:AuthzGroupFileAuthoritative On
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_authz_groupfile
+

Setting the AuthzGroupFileAuthoritative + directive explicitly to Off allows for + group authorization to be passed on to lower level modules (as defined + in the modules.c files) if there is no + group matching the supplied userID.

+ +

By default, control is not passed on and an unknown group + will result in an Authentication Required reply. Not + setting it thus keeps the system secure and forces an NCSA + compliant behaviour.

+ +

Security

+

Do consider the implications of allowing a user to + allow fall-through in his .htaccess file; and verify + that this is really what you want; Generally it is easier to just + secure a single .htpasswd file, than it is to secure + a database which might have more access interfaces.

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_groupfile.html.ja.euc-jp b/docs/manual/mod/mod_authz_groupfile.html.ja.euc-jp new file mode 100644 index 00000000..bfb09cdf --- /dev/null +++ b/docs/manual/mod/mod_authz_groupfile.html.ja.euc-jp @@ -0,0 +1,132 @@ + + + +mod_authz_groupfile - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authz_groupfile

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:¥×¥ì¡¼¥ó¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤òÍѤ¤¤¿¥°¥ë¡¼¥×¾µÇ§
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authz_groupfile_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authz_groupfile.c
¸ß´¹À­:Apache 2.1 °Ê¹ß
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ïǧ¾Ú¤µ¤ì¤¿¥æ¡¼¥¶¤¬¥°¥ë¡¼¥×¤Î¥á¥ó¥Ð¡¼¤« + Èݤ«¤Ë¤è¤Ã¤Æ¥¦¥§¥Ö¥µ¥¤¥È¤Î°ìÉô¤Ø¤Î¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë¤«µñÈݤ¹¤ë¤«¤Î + ¾µÇ§µ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£Æ±Íͤε¡Ç½¤Ï mod_authz_dbm + ¤Ë¤è¤Ã¤Æ¤âÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

AuthGroupFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¾Úǧ¤Ë»ÈÍѤ¹¤ë¥æ¡¼¥¶¥°¥ë¡¼¥×¤Î°ìÍ÷¤¬³ÊǼ¤µ¤ì¤Æ¤¤¤ë¡¢ +¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤹ¤ë
¹½Ê¸:AuthGroupFile file-path
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authz_groupfile
+

AuthGroupFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¾Úǧ¤Ë»ÈÍѤ¹¤ë¥æ¡¼¥¶¥°¥ë¡¼¥×¤Î°ìÍ÷¤¬³ÊǼ¤µ¤ì¤Æ¤¤¤ë¡¢ + ¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤷ¤Þ¤¹¡£ + file-path ¤Ï¥°¥ë¡¼¥×¥Õ¥¡¥¤¥ë¤Ø¤Î¥Ñ¥¹¤Ç¤¹¡£ + ÀäÂХѥ¹¤Ç¤Ê¤±¤ì¤Ð¡¢ + ServerRoot + ¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£

+ +

¥°¥ë¡¼¥×¥Õ¥¡¥¤¥ë³Æ¹Ô¤Ï¡¢¥°¥ë¡¼¥×̾¡¢¥³¥í¥ó¡¢¤½¤·¤Æ + ¥¹¥Ú¡¼¥¹¶èÀÚ¤ê¤Ç¤½¤Î¥á¥ó¥Ð¡¼¤Î¥æ¡¼¥¶Ì¾¤òµ­½Ò¤·¤Þ¤¹¡£

+ +

Îã:

+ mygroup: bob joe anne +

+ +

Â礭¤Ê¥Õ¥¡¥¤¥ë¤òõº÷¤¹¤ë¤Î¤Ï¡¢Èó¾ï¤Ë¸úΨ¤¬°­¤¤¤È¤¤¤¦ÅÀ¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤½¤Î¤è¤¦¤Ê¾ì¹ç¤Ï¡¢ + AuthDBMGroupFile + ¤ÎÊý¤¬¤º¤Ã¤ÈÎɤ¤À­Ç½¤òȯ´ø¤·¤Þ¤¹¡£

+ +

¥»¥­¥å¥ê¥Æ¥£

+

AuthGroupFile ¤Ï¡¢ + ¥¦¥§¥Ö¥µ¡¼¥Ð¤Î¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼¤Î³°Â¦¤Ë + Êݴɤ¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + Êݸ¤è¤¦¤È¤·¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê°Ê²¼¤Ë¤Ï¡¢ÃÖ¤«¤Ê¤¤¤Ç²¼¤µ¤¤¡£ + ¤½¤¦¤·¤Ê¤¤¤È¥¯¥é¥¤¥¢¥ó¥È¤¬ AuthGroupFile ¤ò + ¥À¥¦¥ó¥í¡¼¥É¤Ç¤­¤Æ¤·¤Þ¤¦²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£

+
+ +
+
top
+

AuthzGroupFileAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¾µÇ§¤¬²¼°Ì¤Î¥â¥¸¥å¡¼¥ë¤ËÅϤµ¤ì¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
¹½Ê¸:AuthzGroupFileAuthoritative On|Off
¥Ç¥Õ¥©¥ë¥È:AuthzGroupFileAuthoritative On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authz_groupfile
+

AuthzGroupFileAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ÌÀ¼¨Åª¤Ë Off ¤ËÀßÄꤹ¤ë¤È userID ¤ËÂбþ¤¹¤ë + ¥°¥ë¡¼¥×¤¬¤Ê¤¤¾ì¹ç¤Ë¡¢ + (module.c ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë) ²¼°Ì¤Î¥â¥¸¥å¡¼¥ë¤Ë¥°¥ë¡¼¥×¾µÇ§¤ò + ÅϤ¹¤³¤È¤òµö²Ä¤·¤Þ¤¹¡£

+ + +

¥Ç¥Õ¥©¥ë¥È¤Ç¤ÏÀ©¸æ¤ÏÅϤµ¤ì¤º¡¢Ì¤ÃΤΥ°¥ë¡¼¥×¤Î¾ì¹ç¤Ï Authentication + Required ±þÅú¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢¤³¤ì¤òÀßÄꤷ¤Ê¤¤¤È + ¥·¥¹¥Æ¥à¤ò°ÂÁ´¤ËÊݤĤ³¤È¤¬¤Ç¤­¡¢NCSA ¸ß´¹¤Î¿¶¤ëÉñ¤¤¤ò¤µ¤»¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¥»¥­¥å¥ê¥Æ¥£

+

¥æ¡¼¥¶¤Î .htaccess ¥Õ¥¡¥¤¥ë¤Ç¾¤Î¾µÇ§¼êÃʤؤΠ+ °Ñ¾ù¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤Î°ÕÌ£¤¹¤ë¤È¤³¤í¤Ï½½Ê¬¤Ë¹Íθ¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£ + ¤½¤·¤Æ¤½¤ì¤¬¡¢ËÜÅö¤Ë˾¤àµóÆ°¤Ç¤¢¤ë¤³¤È¤ò³Î¤«¤á¤Æ¤¯¤À¤µ¤¤¡£ + Ä̾ï¤Ï°ì¤Ä¤Î .htpasswd ¥Õ¥¡¥¤¥ë¤ò°ÂÁ´¤Ë¤¹¤ëÊý¤¬ + ¤è¤ê¿¤¯¤Î¥¢¥¯¥»¥¹¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»ý¤Ä¤«¤â¤·¤ì¤Ê¤¤¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò + °ÂÁ´¤Ë¤¹¤ë¤è¤ê¤â´Êñ¤Ç¤¹¡£

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr b/docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr new file mode 100644 index 00000000..34192e05 --- /dev/null +++ b/docs/manual/mod/mod_authz_groupfile.html.ko.euc-kr @@ -0,0 +1,121 @@ + + + +mod_authz_groupfile - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authz_groupfile

+
+

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

+
+ + + + +
¼³¸í:ÀÏ¹Ý ¹®ÀÚÆÄÀÏÀ» ÀÌ¿ëÇÑ ±×·ì ±ÇÇѺο©
»óÅÂ:Base
¸ðµâ¸í:authz_groupfile_module
¼Ò½ºÆÄÀÏ:mod_authz_groupfile.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ÀÎÁõÇÑ »ç¿ëÀÚÀÇ ±×·ì±ÇÇÑÀ¸·Î À¥»çÀÌÆ®ÀÇ ÀϺθ¦ + Á¢±ÙÇÒ ¼ö ÀÖ´ÂÁö °áÁ¤ÇÏ¿© ±ÇÇѺο©¸¦ ÇÑ´Ù. + mod_authz_dbm°ú ±â´ÉÀÌ ºñ½ÁÇÏ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

AuthGroupFile Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÀÎÁõ¿¡ »ç¿ëÇÒ »ç¿ëÀÚ ±×·ì ¸ñ·ÏÀ» ÀúÀåÇÏ´Â ¹®ÀÚÆÄÀϸíÀ» +ÁöÁ¤ÇÑ´Ù
¹®¹ý:AuthGroupFile file-path
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Base
¸ðµâ:mod_authz_groupfile
+

AuthGroupFile Áö½Ã¾î´Â »ç¿ëÀÚ + ÀÎÁõ¿¡ »ç¿ëÇÒ »ç¿ëÀÚ ±×·ì ¸ñ·ÏÀ» ÀúÀåÇÏ´Â ¹®ÀÚÆÄÀϸíÀ» + ÁöÁ¤ÇÑ´Ù. File-path´Â ±×·ìÆÄÀÏ °æ·ÎÀÌ´Ù. Àý´ë°æ·Î¸¦ + »ç¿ëÇÏÁö ¾ÊÀ¸¸é ServerRootÀÇ »ó´ë°æ·Î·Î ¹Þ¾ÆµéÀδÙ.

+ +

±×·ìÆÄÀÏÀÇ °¢ ÁÙ¿¡´Â ±×·ì¸í, ÄÝ·Ð, °ø¹éÀ¸·Î ±¸ºÐÇÑ + »ç¿ëÀÚ¸íµéÀÌ ¼ø¼­´ë·Î ³ª¿Â´Ù.

+ +

¿¹Á¦:

+ mygroup: bob joe anne +

+ +

¸¹Àº ±×·ìÀ» ÀúÀåÇÑ Å« ¹®ÀÚÆÄÀÏÀ» °Ë»öÇÏ´Â °ÍÀº ¸Å¿ì + ºñÈ¿À²ÀûÀÓÀ» ÁÖÀÇÇ϶ó. AuthDBMGroupFileÀÌ ´õ ¼º´ÉÀÌ ÁÁ´Ù.

+ +

º¸¾È

+

AuthGroupFileÀÌ À¥¼­¹öÀÇ ¹®¼­µé + ¹Û¿¡ À§Ä¡ÇÔÀ» È®ÀÎÇ϶ó. ÀÌ ÆÄÀÏÀ» º¸È£ÇÒ µð·ºÅ丮 ¾È¿¡ + °°ÀÌ µÎÁö ¸¶¶ó. ±×·¸Áö ¾ÊÀ¸¸é, Ŭ¶óÀ̾ðÆ®°¡ + AuthGroupFileÀ» ´Ù¿î·ÎµåÇÒ ¼ö ÀÖ´Ù.

+
+ +
+
top
+

AuthzGroupFileAuthoritative Áö½Ã¾î

+ + + + + + + + +
¼³¸í:±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
¹®¹ý:AuthzGroupFileAuthoritative On|Off
±âº»°ª:AuthzGroupFileAuthoritative On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Base
¸ðµâ:mod_authz_groupfile
+

AuthzGroupFileAuthoritative Áö½Ã¾î¸¦ + Á÷Á¢ Off·Î ¼³Á¤Çϸé ÇØ´ç »ç¿ëÀÚ ¾ÆÀ̵𿡠´ëÇÑ + ±×·ìÀÌ ¾ø´Â °æ¿ì ±×·ì ±ÇÇѺο©¸¦ + (modules.c ÆÄÀÏ¿¡¼­ Á¤ÀÇÇÑ) Àú¼öÁØ ¸ðµâ·Î + ³Ñ°ÜÁØ´Ù.

+ +

±âº»ÀûÀ¸·Î Á¦¾î¸¦ ³Ñ±âÁö¾Ê°í, ¸ð¸£´Â ±×·ìÀÇ °æ¿ì ÀÎÁõ + ÇÊ¿ä ÀÀ´äÀ» ÇÑ´Ù. ÀÌ Áö½Ã¾î¸¦ ¼³Á¤ÇÏÁö¾ÊÀ¸¸é ½Ã½ºÅÛÀÌ ¾ÈÀüÇÏ°Ô + À¯ÁöµÇ¸ç, NCSA À¥¼­¹ö¿Í °°ÀÌ µ¿ÀÛÇÑ´Ù.

+ +

º¸¾È

+

»ç¿ëÀÚ°¡ ÀÚ½ÅÀÇ .htaccess ÆÄÀÏÀ» »ç¿ëÇÏ°Ô µÇ´ÂÁö »ìÆ캸°í, + ÀÌ·± ÇൿÀ» Çã¿ëÇÒÁö °áÁ¤Ç϶ó. ÀϹÝÀûÀ¸·Î ¿©·¯°¡Áö ¹æ¹ýÀ¸·Î + Á¢±ÙÇÒ ¼ö ÀÖ´Â µ¥ÀÌÅͺ£À̽º¸¦ º¸È£ÇÏ´Â °Íº¸´Ù ÇϳªÀÇ + .htpasswd ÆÄÀÏÀ» º¸È£ÇÏ´Â °ÍÀÌ ´õ ½±´Ù.

+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_host.html b/docs/manual/mod/mod_authz_host.html new file mode 100644 index 00000000..fc883205 --- /dev/null +++ b/docs/manual/mod/mod_authz_host.html @@ -0,0 +1,11 @@ +URI: mod_authz_host.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authz_host.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authz_host.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authz_host.html.en b/docs/manual/mod/mod_authz_host.html.en new file mode 100644 index 00000000..1414aa98 --- /dev/null +++ b/docs/manual/mod/mod_authz_host.html.en @@ -0,0 +1,333 @@ + + + +mod_authz_host - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authz_host

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Group authorizations based on host (name or IP +address)
Status:Base
Module Identifier:authz_host_module
Source File:mod_authz_host.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

The directives provided by mod_authz_host are + used in <Directory>, + <Files>, and + <Location> sections + as well as .htaccess + files to control access to particular parts of the server. + Access can be controlled based on the client hostname, IP address, or + other characteristics of the client request, as captured in environment variables. The Allow and Deny directives are used to + specify which clients are or are not allowed access to the server, + while the Order + directive sets the default access state, and configures how the + Allow and Deny directives interact with each + other.

+ +

Both host-based access restrictions and password-based + authentication may be implemented simultaneously. In that case, + the Satisfy directive is used + to determine how the two sets of restrictions interact.

+ +

In general, access restriction directives apply to all + access methods (GET, PUT, + POST, etc). This is the desired behavior in most + cases. However, it is possible to restrict some methods, while + leaving other methods unrestricted, by enclosing the directives + in a <Limit> section.

+
+

Directives

+ +

See also

+
+ +
top
+

Allow Directive

+ + + + + + + +
Description:Controls which hosts can access an area of the +server
Syntax: Allow from all|host|env=env-variable +[host|env=env-variable] ...
Context:directory, .htaccess
Override:Limit
Status:Base
Module:mod_authz_host
+

The Allow directive affects which hosts can + access an area of the server. Access can be controlled by + hostname, IP Address, IP Address range, or by other + characteristics of the client request captured in environment + variables.

+ +

The first argument to this directive is always + from. The subsequent arguments can take three + different forms. If Allow from all is specified, then + all hosts are allowed access, subject to the configuration of the + Deny and Order directives as discussed + below. To allow only particular hosts or groups of hosts to access + the server, the host can be specified in any of the + following formats:

+ +
+
A (partial) domain-name
+ +
+

Example:

+ Allow from apache.org
+ Allow from .net example.edu +

+

Hosts whose names match, or end in, this string are allowed + access. Only complete components are matched, so the above + example will match foo.apache.org but it will not + match fooapache.org. This configuration will cause + Apache to perform a double reverse DNS lookup on the client IP + address, regardless of the setting of the HostnameLookups directive. It will do + a reverse DNS lookup on the IP address to find the associated + hostname, and then do a forward lookup on the hostname to assure + that it matches the original IP address. Only if the forward + and reverse DNS are consistent and the hostname matches will + access be allowed.

+ +
A full IP address
+ +
+

Example:

+ Allow from 10.1.2.3
+ Allow from 192.168.1.104 192.168.1.205 +

+

An IP address of a host allowed access

+ +
A partial IP address
+ +
+

Example:

+ Allow from 10.1
+ Allow from 10 172.20 192.168.2 +

+

The first 1 to 3 bytes of an IP address, for subnet + restriction.

+ +
A network/netmask pair
+ +
+

Example:

+ Allow from 10.1.0.0/255.255.0.0 +

+

A network a.b.c.d, and a netmask w.x.y.z. For more + fine-grained subnet restriction.

+ +
A network/nnn CIDR specification
+ +
+

Example:

+ Allow from 10.1.0.0/16 +

+

Similar to the previous case, except the netmask consists of + nnn high-order 1 bits.

+
+ +

Note that the last three examples above match exactly the + same set of hosts.

+ +

IPv6 addresses and IPv6 subnets can be specified as shown + below:

+ +

+ Allow from 2001:db8::a00:20ff:fea7:ccea
+ Allow from 2001:db8::a00:20ff:fea7:ccea/10 +

+ +

The third format of the arguments to the + Allow directive allows access to the server + to be controlled based on the existence of an environment variable. When Allow from + env=env-variable is specified, then the request is + allowed access if the environment variable env-variable + exists. The server provides the ability to set environment + variables in a flexible way based on characteristics of the client + request using the directives provided by + mod_setenvif. Therefore, this directive can be + used to allow access based on such factors as the clients + User-Agent (browser type), Referer, or + other HTTP request header fields.

+ +

Example:

+ SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
+ <Directory /docroot>
+ + Order Deny,Allow
+ Deny from all
+ Allow from env=let_me_in
+ + </Directory> +

+ +

In this case, browsers with a user-agent string beginning + with KnockKnock/2.0 will be allowed access, and all + others will be denied.

+ +
+
top
+

Deny Directive

+ + + + + + + +
Description:Controls which hosts are denied access to the +server
Syntax: Deny from all|host|env=env-variable +[host|env=env-variable] ...
Context:directory, .htaccess
Override:Limit
Status:Base
Module:mod_authz_host
+

This directive allows access to the server to be restricted + based on hostname, IP address, or environment variables. The + arguments for the Deny directive are + identical to the arguments for the Allow directive.

+ +
+
top
+

Order Directive

+ + + + + + + + +
Description:Controls the default access state and the order in which +Allow and Deny are +evaluated.
Syntax: Order ordering
Default:Order Deny,Allow
Context:directory, .htaccess
Override:Limit
Status:Base
Module:mod_authz_host
+

The Order directive controls the default + access state and the order in which Allow and Deny directives are evaluated. + Ordering is one of

+ +
+
Deny,Allow
+ +
The Deny directives + are evaluated before the Allow directives. Access is + allowed by default. Any client which does not match a + Deny directive or does + match an Allow + directive will be allowed access to the server.
+ +
Allow,Deny
+ +
The Allow + directives are evaluated before the Deny directives. Access is denied + by default. Any client which does not match an Allow directive or does match a + Deny directive will be + denied access to the server.
+ +
Mutual-failure
+ +
Only those hosts which appear on the Allow list and do not appear on + the Deny list are + granted access. This ordering has the same effect as Order + Allow,Deny and is deprecated in favor of that + configuration.
+
+ +

Keywords may only be separated by a comma; no whitespace is + allowed between them. Note that in all cases every Allow and Deny statement is evaluated.

+ +

In the following example, all hosts in the apache.org domain + are allowed access; all other hosts are denied access.

+ +

+ Order Deny,Allow
+ Deny from all
+ Allow from apache.org +

+ +

In the next example, all hosts in the apache.org domain are + allowed access, except for the hosts which are in the + foo.apache.org subdomain, who are denied access. All hosts not + in the apache.org domain are denied access because the default + state is to deny access to the server.

+ +

+ Order Allow,Deny
+ Allow from apache.org
+ Deny from foo.apache.org +

+ +

On the other hand, if the Order in the last + example is changed to Deny,Allow, all hosts will + be allowed access. This happens because, regardless of the + actual ordering of the directives in the configuration file, + the Allow from apache.org will be evaluated last + and will override the Deny from foo.apache.org. + All hosts not in the apache.org domain will also + be allowed access because the default state will change to + allow.

+ +

The presence of an Order directive can affect + access to a part of the server even in the absence of accompanying + Allow and Deny directives because of its effect + on the default access state. For example,

+ +

+ <Directory /www>
+ + Order Allow,Deny
+ + </Directory> +

+ +

will deny all access to the /www directory + because the default access state will be set to + deny.

+ +

The Order directive controls the order of access + directive processing only within each phase of the server's + configuration processing. This implies, for example, that an + Allow or Deny directive occurring in a + <Location> section will + always be evaluated after an Allow or Deny directive occurring in a + <Directory> section or + .htaccess file, regardless of the setting of the + Order directive. For details on the merging + of configuration sections, see the documentation on How Directory, Location and Files sections + work.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_host.html.ja.euc-jp b/docs/manual/mod/mod_authz_host.html.ja.euc-jp new file mode 100644 index 00000000..fc20aac5 --- /dev/null +++ b/docs/manual/mod/mod_authz_host.html.ja.euc-jp @@ -0,0 +1,347 @@ + + + +mod_authz_host - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authz_host

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:¥Û¥¹¥È (̾Á°¤â¤·¤¯¤Ï IP ¥¢¥É¥ì¥¹) ¤Ë´ð¤Å¤¤¤¿¥°¥ë¡¼¥×¾µÇ§
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authz_host_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authz_host.c
¸ß´¹À­:Apache 2.1 °Ê¹ß
+

³µÍ×

+ +

mod_authz_host ¤Ë¤è¤êÄ󶡤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥µ¡¼¥Ð¤ÎÆÃÄê¤ÎÉôʬ¤Ø¤Î + ¥¢¥¯¥»¥¹¤òÀ©¸æ¤¹¤ë¤¿¤á¤Ë <Directory>, <Files>, <Location> + ¤È .htaccess ¥Õ¥¡¥¤¥ë¤Ç»ÈÍѤµ¤ì¤Þ¤¹¡£¥¯¥é¥¤¥¢¥ó¥È¤Î¥Û¥¹¥È̾¡¢IP + ¥¢¥É¥ì¥¹¤ä ´Ä¶­ÊÑ¿ô¤È¤·¤Æ¼èÆÀ¤µ¤ì¤¿¡¢¤½¤Î¾¤Î¥ê¥¯¥¨¥¹¥È¤ÎÆÃħ¤Ë´ð¤Å¤¤¤Æ + ¥¢¥¯¥»¥¹À©¸æ¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Allow ¤È + Deny ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¤É¤Î¤è¤¦¤Ê¥¯¥é¥¤¥¢¥ó¥È¤Ë¥¢¥¯¥»¥¹¤ò + µö²Ä¤¹¤ë¡¢¤·¤Ê¤¤¤«¤ò»ØÄꤹ¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£°ìÊý¡¢ + Order ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥Ç¥Õ¥©¥ë¥È¤Î¥¢¥¯¥»¥¹¾õÂ֤ȡ¢ + Allow ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤Î¤ª¸ß¤¤¤Ø¤Î±Æ¶Á¤Î»ÅÊý¤òÀßÄꤷ¤Þ¤¹¡£ +

+ +

¥Û¥¹¥È¤Ë¤è¤ë¥¢¥¯¥»¥¹À©¸Â¤È¥Ñ¥¹¥ï¡¼¥É¤Ë¤è¤ëǧ¾Ú¤òƱ»þ¤Ë + ¹Ô¤Ê¤¦¤³¤È¤¬²Äǽ¤Ç¤¹¡£¤½¤Î¾ì¹ç¡¢¤½¤ÎÆó¤Ä¤ÎÀ©¸Â¤Î´Ø·¸¤ò»ØÄꤹ¤ë¤¿¤á¤Ë + Satisfy + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Þ¤¹¡£

+ +

°ìÈÌŪ¤Ë¤Ï¡¢¥¢¥¯¥»¥¹À©¸Â¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¹¤Ù¤Æ¤Î¥¢¥¯¥»¥¹¥á¥½¥Ã¥É + (GET, PUT, POST ¤Ê¤É) + ¤ËŬÍѤµ¤ì¤Þ¤¹¡£¤½¤·¤Æ¡¢¤Û¤È¤ó¤É¤Î¾ì¹ç¤³¤ì¤¬Ë¾¤Þ¤·¤¤Æ°ºî¤Ç¤¹¡£ + ¤·¤«¤·¡¢<Limit> + ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¯¤³¤È¤Ç¡¢ + °ìÉô¤Î¥á¥½¥Ã¥É¤Ë¤Î¤ßÀ©¸Â¤ò¤«¤±¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

Allow ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤Î¤¢¤ëÎΰè¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¥Û¥¹¥È¤òÀ©¸æ¤¹¤ë
¹½Ê¸: Allow from all|host|env=env-variable +[host|env=env-variable] ...
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Limit
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authz_host
+

Allow ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤É¤Î¥Û¥¹¥È¤¬ + ¥µ¡¼¥Ð¤Î¤¢¤ëÎΰè¤ò¥¢¥¯¥»¥¹¤Ç¤­¤ë¤«¤Ë±Æ¶Á¤òÍ¿¤¨¤Þ¤¹¡£ + ¥¢¥¯¥»¥¹¤Ï¥Û¥¹¥È̾¡¢IP ¥¢¥É¥ì¥¹¡¢IP ¥¢¥É¥ì¥¹¤ÎÈϰϤ䡢 + ´Ä¶­ÊÑ¿ô¤È¤·¤Æ¼èÆÀ¤µ¤ì¤¿¡¢¤½¤Î¾¤Î¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤Î + ÆÃħ¤Ë¤è¤Ã¤ÆÀ©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎºÇ½é¤Î°ú¿ô¤Ï¾ï¤Ë from ¤Ç¤¹¡£ + ¤½¤ì¤Ë³¤¯°ú¿ô¤Ï»°¤Ä¤Î°ã¤Ã¤¿·Á¼°¤¬¤¢¤ê¤Þ¤¹¡£Allow from + all ¤¬»ØÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤Ë¥¢¥¯¥»¥¹¤òµö²Ä¤·¡¢ + ¥¢¥¯¥»¥¹À©¸Â¤Ï²¼¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¡¢ + Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È Order + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀßÄê¤Ç·è¤Þ¤ê¤Þ¤¹¡£ + ÆÃÄê¤Î¥Û¥¹¥È¤ä¥Û¥¹¥È·²¤Ë¤Î¤ß¥µ¡¼¥Ð¤Ø¤Î¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ + °Ê²¼¤Î¤É¤ì¤«¤Î·Á¼°¤Ç host ¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +
+
¥É¥á¥¤¥ó̾ (¤Î°ìÉô)
+ +
+

Îã

+ Allow from apache.org
+ Allow from .net example.edu +

+

¤³¤Îʸ»úÎó¤Ë¹ç¤¦¤«¡¢¤³¤ì¤Ç½ª¤ï¤ë̾Á°¤Î¥Û¥¹¥È¤Î¥¢¥¯¥»¥¹¤¬µö²Ä¤µ¤ì¤Þ¤¹¡£ + ³ÆÉôʬ¤¬´°Á´¤Ë¹ç¤¦¤â¤Î¤À¤±¤ËŬÍѤµ¤ì¤Þ¤¹¤Î¤Ç¡¢¾å¤ÎÎã¤Ï + foo.apache.org ¤Ë¤Ï¥Þ¥Ã¥Á¤·¤Þ¤¹¤¬¡¢ + fooapache.org ¤Ë¤Ï¥Þ¥Ã¥Á¤·¤Þ¤»¤ó¡£ + ¤³¤ÎÀßÄê¤ò¤¹¤ë¤È¡¢Apache ¤Ï + HostnameLookups + ¤ÎÀßÄê¤Ë´Ø¤ï¤é¤º¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î IP ¥¢¥É¥ì¥¹¤ËÂФ·¤Æ + DNS ¤Î 2 ½ÅµÕ°ú¤­¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£ + ¥Û¥¹¥È̾¤«¤é¥ª¥ê¥¸¥Ê¥ë¤Î IP ¥¢¥É¥ì¥¹¤ò½ç°ú¤­¤·¤Þ¤¹¡£ + ½ç°ú¤­¤ÈµÕ°ú¤­¤¬°ìÃפ·¡¢¥Û¥¹¥È̾¤¬³ºÅö¤·¤¿¾ì¹ç¤Ë¤Î¤ß¡¢ + ¥¢¥¯¥»¥¹¤¬µö²Ä¤µ¤ì¤Þ¤¹¡£

+ +
´°Á´¤Ê IP ¥¢¥É¥ì¥¹
+ +
+

Îã

+ Allow from 10.1.2.3
+ Allow from 192.168.1.104 192.168.1.205 +

+

¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë IP ¥¢¥É¥ì¥¹¤Ç¤¹¡£

+ +
IP ¥¢¥É¥ì¥¹¤Î°ìÉô
+ +
+

Îã

+ Allow from 10.1
+ Allow from 10 172.20 192.168.2 +

+

¥µ¥Ö¥Í¥Ã¥È¤ÎÀ©¸ÂÍѤΡ¢IP + ¥¢¥É¥ì¥¹¤ÎºÇ½é¤Î°ì¤Ä¤«¤é»°¤Ä¤Þ¤Ç¤Î¥Ð¥¤¥È¤Ç¤¹¡£

+ +
¥Í¥Ã¥È¥ï¡¼¥¯/¥Í¥Ã¥È¥Þ¥¹¥¯ ¤ÎÂÐ
+ +
+

Îã

+ Allow from 10.1.0.0/255.255.0.0 +

+

¥Í¥Ã¥È¥ï¡¼¥¯ a.b.c.d ¤È¥Í¥Ã¥È¥Þ¥¹¥¯ w.x.y.z ¤Ç¤¹¡£ + ¤è¤êºÙγÅ٤Υµ¥Ö¥Í¥Ã¥ÈÀ©¸ÂÍѤǤ¹¡£

+ +
¥Í¥Ã¥È¥ï¡¼¥¯/nnn CIDR »ØÄê
+ +
+

Îã

+ Allow from 10.1.0.0/16 +

+

¥Í¥Ã¥È¥Þ¥¹¥¯¤¬ nnn ¤Î¾å°Ì¥Ó¥Ã¥È¤¬ 1 + ¤È¤Ê¤Ã¤Æ¤¤¤ë¤â¤Î¤«¤é¤Ê¤ë¤³¤È°Ê³°¤ÏÁ°¤Î¤â¤Î¤ÈƱ¤¸¤Ç¤¹¡£

+
+ +

Ãí: ºÇ¸å¤Î»°¤Ä¤ÎÎã¤Ï¤Þ¤Ã¤¿¤¯Æ±¤¸¥Û¥¹¥È¤Ë¹ç¤¤¤Þ¤¹¡£

+ + +

IPv6 ¥¢¥É¥ì¥¹¤È IPv6 ¤Î¥µ¥Ö¥Í¥Ã¥È¤Ï°Ê²¼¤Î¤è¤¦¤Ë»ØÄê¤Ç¤­¤Þ¤¹:

+ +

+ Allow from 2001:db8::a00:20ff:fea7:ccea
+ Allow from 2001:db8::a00:20ff:fea7:ccea/10 +

+ +

Allow ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô¤Î»°¤ÄÌܤηÁ¼°¤Ï¡¢ + ´Ä¶­ÊÑ¿ô + ¤Î¸ºß¤Ë¤è¤ê¥¢¥¯¥»¥¹¤ÎÀ©¸æ¤ò¹Ô¤Ê¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤â¤Î¤Ç¤¹¡£ + Allow from env=env-variable + ¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢´Ä¶­ÊÑ¿ô env-variable + ¤¬Â¸ºß¤·¤¿¾ì¹ç¤Ë¥ê¥¯¥¨¥¹¥È¤Ï¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤Þ¤¹¡£¥µ¡¼¥Ð¤Ï + mod_setenvif + ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È + ¤ÎÆÃħ¤Ë´ð¤Å¤¤¤Æ½ÀÆð¤Ë´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ëµ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Î + User-Agent (¥Ö¥é¥¦¥¶¤Î¼ïÎà)¡¢Referer + ¤ä¾¤Î HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤Ê¤É¤Ë´ð¤Å¤¤¤Æ + ¥¢¥¯¥»¥¹µö²Ä¤ò¤¹¤ë¤¿¤á¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +

+ +

Example:

+ SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
+ <Directory /docroot>
+ + Order Deny,Allow
+ Deny from all
+ Allow from env=let_me_in
+ + </Directory> +

+ +

¤³¤Î¾ì¹ç¡¢user-agent ¤Îʸ»úÎó¤¬ KnockKnock/2.0 + ¤Ç»Ï¤Þ¤ë¥Ö¥é¥¦¥¶¤Î¤ß¤¬¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¡¢ + ¾¤Î¤â¤Î¤Ï¥¢¥¯¥»¥¹¤òµñÈݤµ¤ì¤Þ¤¹¡£

+ + +
+
top
+

Deny ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬¥¢¥¯¥»¥¹¤òµñÈݤ¹¤ë¥Û¥¹¥È¤òÀ©¸æ¤¹¤ë
¹½Ê¸: Deny from all|host|env=env-variable +[host|env=env-variable] ...
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Limit
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authz_host
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Û¥¹¥È̾¡¢IP + ¥¢¥É¥ì¥¹¡¢´Ä¶­ÊÑ¿ô¤Ë´ð¤Å¤¤¤Æ¥µ¡¼¥Ð¤Ø¤Î¥¢¥¯¥»¥¹¤òÀ©¸Â¤·¤Þ¤¹¡£ + Deny ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô¤Ï Allow + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤Þ¤Ã¤¿¤¯Æ±¤¸¤Ç¤¹¡£

+ +
+
top
+

Order ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Ç¥Õ¥©¥ë¥È¤Î¥¢¥¯¥»¥¹²Äǽ¤Ê¾õÂ֤ȡ¢Allow ¤È +Deny ¤¬É¾²Á¤µ¤ì¤ë½çÈÖ¤òÀ©¸æ¤¹¤ë
¹½Ê¸: Order ordering
¥Ç¥Õ¥©¥ë¥È:Order Deny,Allow
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Limit
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authz_host
+

Order ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¥¢¥¯¥»¥¹¤Î¾õÂÖ¤È + Allow ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬É¾²Á¤µ¤ì¤ë½çÈÖ¤òÀ©¸æ¤·¤Þ¤¹¡£ + Ordering ¤Ï°Ê²¼¤Î¤É¤ì¤«¤Ç¤¹¡£

+ +
+
Deny,Allow
+ +
Deny ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + Allow + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÁ°¤Ëɾ²Á¤µ¤ì¤Þ¤¹¡£ + ¥¢¥¯¥»¥¹¤Ï¥Ç¥Õ¥©¥ë¥È¤Çµö²Ä¤µ¤ì¤Þ¤¹¡£Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¹ç¤ï¤Ê¤¤¤«¡¢Allow + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¹ç¤¦¥¯¥é¥¤¥¢¥ó¥È¤Ï¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤Þ¤¹¡£
+ +
Allow,Deny
+ +
Allow + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÁ°¤Ëɾ²Á¤µ¤ì¤Þ¤¹¡£ + ¥¢¥¯¥»¥¹¤Ï¥Ç¥Õ¥©¥ë¥È¤ÇµñÈݤµ¤ì¤Þ¤¹¡£Allow + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¹ç¤ï¤Ê¤¤¤«¡¢Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¹ç¤¦¥¯¥é¥¤¥¢¥ó¥È¤Ï¥¢¥¯¥»¥¹¤òµñÈݤµ¤ì¤Þ¤¹¡£ +
+ +
Mutual-failure
+ +
Allow ¤Î¥ê¥¹¥È¤Ë¸½¤ì¤Æ¡¢ + Deny + ¤Î¥ê¥¹¥È¤Ë¸½¤ì¤Ê¤¤¥Û¥¹¥È¤Î¤ß¤¬¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤Þ¤¹¡£ + ¤³¤Î½çÈÖÉÕ¤±¤Ï Order Allow,Deny ¤ÈƱ¤¸¸ú²Ì¤ò»ý¤Á¡¢ + ¤½¤ÎÀßÄê¤ÎÊý¤¬¹¥¤Þ¤·¤¤¤¿¤á¤ËÈó¿ä¾©¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
+
+ +

¥­¡¼¥ï¡¼¥É¤Ï¥³¥ó¥Þ¤ÇʬΥ¤¹¤ë¤³¤È¤À¤±¤¬²Äǽ¤Ç¤¹¡£ + ´Ö¤Ë¶õÇò¤¬¤¢¤Ã¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£¤É¤Î¾ì¹ç¤Ç¤â¡¢Allow ¤È + Deny ʸ¤Ï + Á´¤Æɾ²Á¤µ¤ì¤ë¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ +

+ +

°Ê²¼¤ÎÎã¤Ç¤Ï¡¢apache.org + ¥É¥á¥¤¥ó¤Î¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤Ï¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤Þ¤¹¡£ + ¾¤Î¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤Ï¥¢¥¯¥»¥¹¤òµñÈݤµ¤ì¤Þ¤¹¡£

+ +

+ Order Deny,Allow
+ Deny from all
+ Allow from apache.org +

+ +

¼¡¤ÎÎã¤Ç¤Ï¡¢foo.apache.org ¥µ¥Ö¥É¥á¥¤¥ó¤Ë¤¢¤ë¥Û¥¹¥È°Ê³°¤Î¡¢ + apache.org ¥É¥á¥¤¥ó¤Î¤¹¤Ù¤Æ¤Î¥Û¥¹¥È¤¬¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤Þ¤¹¡£ + apache.org + ¥É¥á¥¤¥ó¤Ç¤Ê¤¤¥Û¥¹¥È¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Î¾õÂÖ¤¬¥¢¥¯¥»¥¹µñÈݤΤ¿¤á¡¢ + ¥µ¡¼¥Ð¤Ø¤Î¥¢¥¯¥»¥¹¤òµñÈݤµ¤ì¤Þ¤¹¡£

+ +

+ Order Allow,Deny
+ Allow from apache.org
+ Deny from foo.apache.org +

+ +

°ìÊý¡¢¾å¤ÎÎã¤Î Order ¤¬ Deny,Allow + ¤ËÊѤï¤Ã¤Æ¤¤¤ì¤Ð¡¢¤¹¤Ù¤Î¥Û¥¹¥È¤Ë¥¢¥¯¥»¥¹¤¬µö²Ä¤µ¤ì¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î¼ÂºÝ¤Î½çÈ֤˴ؤï¤é¤º¡¢ + Allow from apache.org ¤¬ºÇ¸å¤Ëɾ²Á¤µ¤ì¤Æ¡¢ + Deny from foo.apache.org ¤ò¾å½ñ¤­¤¹¤ë¤«¤é¤Ç¤¹¡£ + apache.org + ¥É¥á¥¤¥ó¤Ë¤Ê¤¤¥Û¥¹¥È¤â¡¢¥Ç¥Õ¥©¥ë¥È¤Î¾õÂÖ¤¬ allow + ¤ËÊѲ½¤¹¤ë¤¿¤á¤Ë¡¢¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤Þ¤¹¡£ +

+ +

Order + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¥¢¥¯¥»¥¹¤Î¾õÂ֤˱ƶÁ¤òÍ¿¤¨¤ë¤Î¤Ç¡¢ + Allow ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Ìµ¤¯¤Æ¤â¡¢¥µ¡¼¥Ð¤Î¥¢¥¯¥»¥¹¤Ë±Æ¶Á¤òÍ¿¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¡¢

+ +

+ <Directory /www>
+ + Order Allow,Deny
+ + </Directory> +

+ +

¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¥¢¥¯¥»¥¹¾õÂÖ¤¬ deny ¤Ë¤Ê¤ë¤¿¤á¡¢ + /www ¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¤¹¤Ù¤Æ¤Î¥¢¥¯¥»¥¹¤òµñÈݤ·¤Þ¤¹¡£ +

+ +

Order + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥µ¡¼¥Ð¤ÎÀßÄê½èÍý¤Î³ÆÃʳ¬¤Ç¤À¤± + ¥¢¥¯¥»¥¹¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î½èÍý¤Î½çÈÖ¤òÊѹ¹¤·¤Þ¤¹¡£¤³¤ì¤Ï¡¢¤¿¤È¤¨¤Ð¡¢ + Order ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀßÄê¤Ë´Ø¤ï¤é¤º¡¢ + <Location> ¥»¥¯¥·¥ç¥ó¤Î + Allow ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä + Deny ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + Directory ¥»¥¯¥·¥ç¥ó¤ä + .htaccess ¥Õ¥¡¥¤¥ë¤Î Allow + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä Deny + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤è¤ê¤â¾ï¤Ë¸å¤Ëɾ²Á¤µ¤ì¤ë¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ + ÀßÄꥻ¥¯¥·¥ç¥ó¤Î¥Þ¡¼¥¸¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¡¢ + Directory,Location, Files + ¥»¥¯¥·¥ç¥ó¤ÎÆ°ºîÊýË¡ ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_host.html.ko.euc-kr b/docs/manual/mod/mod_authz_host.html.ko.euc-kr new file mode 100644 index 00000000..2f0c546b --- /dev/null +++ b/docs/manual/mod/mod_authz_host.html.ko.euc-kr @@ -0,0 +1,310 @@ + + + +mod_authz_host - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authz_host

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:È£½ºÆ® (À̸§À̳ª IP ÁÖ¼Ò)¸¦ »ç¿ëÇÑ ±×·ì ±ÇÇѺο©
»óÅÂ:Base
¸ðµâ¸í:authz_host_module
¼Ò½ºÆÄÀÏ:mod_authz_host.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

<Directory>, + <Files>, + <Location> + ¼½¼Ç°ú .htaccess + ÆÄÀÏ¿¡¼­ ¼­¹öÀÇ Æ¯Á¤ ºÎºÐÀÇ Á¢±ÙÀ» Á¦¾îÇϱâÀ§ÇØ + mod_authz_host°¡ Á¦°øÇÏ´Â Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. + Ŭ¶óÀ̾ðÆ®ÀÇ È£½ºÆ®¸í, IP ÁÖ¼Ò, ȯ°æº¯¼ö¿¡ ±â·ÏµÈ ¿äûÀÇ Æ¯¼º¿¡ µû¶ó + Á¢±ÙÀ» Á¦¾îÇÑ´Ù. Allow¿Í Deny Áö½Ã¾î´Â ¾î¶² + Ŭ¶óÀ̾ðÆ®°¡ ¼­¹ö¿¡ Á¢±ÙÇÒ ¼ö ÀÖ´ÂÁö¸¦ Áö½ÃÇÏ°í, Order Áö½Ã¾î´Â ±âº»ÀûÀ¸·Î + Á¢±ÙÀ» Çã¿ëÇÒÁö °ÅºÎÇÒÁö ¿©ºÎ¿Í ¾î¶»°Ô Allow Áö½Ã¾î¿Í Deny Áö½Ã¾î°¡ ¼­·Î ¿µÇâÀ» + ¹ÌÄ¡´ÂÁö °áÁ¤ÇÑ´Ù.

+ +

È£½ºÆ®±â¹Ý Á¢±ÙÁ¦ÇÑ°ú ¾ÏÈ£±â¹Ý ÀÎÁõÀ» µ¿½Ã¿¡ »ç¿ëÇÒ ¼öµµ + ÀÖ´Ù. ÀÌ °æ¿ì Satisfy + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ¾î¶»°Ô µÎ Á¦ÇÑÀÌ ¼­·Î ¿µÇâÀ» ¹ÌÄ¡´ÂÁö + °áÁ¤ÇÑ´Ù.

+ +

ÀϹÝÀûÀ¸·Î Á¢±ÙÁ¦ÇÑ Áö½Ã¾î´Â (GET, + PUT, POST µî) ¸ðµç ¸Þ¼­µå¿¡ Àû¿ëµÇ¸ç, + ÀÌ ÇൿÀº ´ëºÎºÐÀÇ °æ¿ì ¹Ù¶÷Á÷ÇÏ´Ù. ±×·¯³ª <Limit> ¼½¼Ç¾È¿¡ + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ƯÁ¤ ¸Þ¼­µå¿¡¸¸ Á¦ÇÑÇÒ ¼ö ÀÖ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

Allow Áö½Ã¾î

+ + + + + + + +
¼³¸í:¼­¹öÀÇ ÀϺο¡ Á¢±ÙÇÒ ¼ö Àִ ȣ½ºÆ®¸¦ ÁöÁ¤ÇÑ´Ù
¹®¹ý: Allow from all|host|env=env-variable +[host|env=env-variable] ...
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:Limit
»óÅÂ:Base
¸ðµâ:mod_authz_host
+

Allow Áö½Ã¾î´Â ¾î¶² È£½ºÆ®°¡ ¼­¹öÀÇ + ÀϺο¡ Á¢±ÙÇÒ ¼ö ÀÖ´ÂÁö Áö½ÃÇÑ´Ù. È£½ºÆ®¸í, IP ÁÖ¼Ò, IP + ÁÖ¼Ò¿µ¿ª, ȯ°æº¯¼ö¿¡ ±â·ÏµÈ ´Ù¸¥ Ư¼º¿¡ µû¶ó Á¢±ÙÀ» Á¶ÀýÇÒ + ¼ö ÀÖ´Ù.

+ +

ÀÌ Áö½Ã¾îÀÇ Ã¹¹ø° ¾Æ±Ô¸ÕÆ®´Â Ç×»ó fromÀÌ´Ù. + ´ÙÀ½ ¾Æ±Ô¸ÕÆ®¿¡´Â ¼¼°¡Áö Çü½ÄÀÌ ÀÖ´Ù. Allow from allÀ» + »ç¿ëÇϸé, ¾Æ·¡¿¡¼­ ¼³¸íÇÒ Deny¿Í Order Áö½Ã¾î ¼³Á¤¿¡ + µû¶ó ¸ðµç È£½ºÆ®ÀÇ Á¢±ÙÀ» Çã°¡ÇÑ´Ù. ƯÁ¤ È£½ºÆ®¸¸ ¼­¹ö·Î + Á¢±ÙÀ» Çã¿ëÇÏ·Á¸é ´ÙÀ½°ú °°Àº Çü½ÄÀ¸·Î host¸¦ Áö½ÃÇÒ + ¼ö ÀÖ´Ù:

+ +
+
È£½ºÆ®¸í (ÀϺÎ)
+ +
+

¿¹Á¦:

+ Allow from apache.org +

+

È£½ºÆ®¸íÀÌ ÀÌ ¹®ÀÚ¿­°ú °°°Å³ª ÀÌ ¹®ÀÚ¿­·Î ³¡³ª¸é Á¢±ÙÀ» + Çã¿ëÇÑ´Ù. ±×·¡¼­ ÀÌ °æ¿ì foo.apache.org´Â + ÇØ´çµÇ°í, fooapache.org´Â ÇØ´çµÇÁö ¾Ê´Â´Ù. + ÀÌ ¼³Á¤À» »ç¿ëÇÏ¸é ¾ÆÆÄÄ¡´Â HostnameLookups Áö½Ã¾î ¼³Á¤°ú + °ü°è¾øÀÌ Å¬¶óÀ̾ðÆ® IP ÁÖ¼Ò¸¦ °¡Áö°í Áߺ¹-¿ª DNS °Ë»öÀ» + ÇÑ´Ù. Áï, È£½ºÆ®¸íÀ» ã±âÀ§ÇØ IP ÁÖ¼Ò¸¦ ¿ªDNS °Ë»öÀ» ÇÑ + ÈÄ, ´Ù½Ã È£½ºÆ®¸íÀ¸·Î °Ë»öÇÏ¿© ¿ø·¡ IP ÁÖ¼Ò¿Í ÀÏÄ¡ÇÏ´ÂÁö + È®ÀÎÇÑ´Ù. °á°ú°¡ °°°í È£½ºÆ®¸íÀÌ ¼³Á¤°ª¿¡ ÇØ´çÇϸé, Á¢±ÙÀ» + Çã¿ëÇÑ´Ù.

+ +
IP ÁÖ¼Ò Àüü
+ +
+

¿¹Á¦:

+ Allow from 10.1.2.3 +

+

Á¢±ÙÀ» Çã°¡Çϴ ȣ½ºÆ®ÀÇ IP ÁÖ¼Ò

+ +
IP ÁÖ¼Ò ÀϺÎ
+ +
+

¿¹Á¦:

+ Allow from 10.1 +

+

¼­ºê³×Æ®¿öÅ©·Î Á¦ÇÑÇϱâÀ§ÇØ IP ÁÖ¼Ò ¾ÕÀÇ 1¿¡¼­ 3 + ¹ÙÀÌÆ®.

+ +
³×Æ®¿öÅ©/³Ý¸Å½ºÅ© ½Ö
+ +
+

¿¹Á¦:

+ Allow from 10.1.0.0/255.255.0.0 +

+

³×Æ®¿öÅ© a.b.c.d¿Í ³Ý¸Å½ºÅ© w.x.y.z. ´õ ¼¼¹ÐÇÏ°Ô + ¼­ºê³×Æ®¿öÅ©·Î Á¦ÇÑÇÒ¶§ »ç¿ëÇÑ´Ù.

+ +
³×Æ®¿öÅ©/nnn CIDR ±Ô¾à
+ +
+

¿¹Á¦:

+ Allow from 10.1.0.0/16 +

+

¾ÕÀÇ °æ¿ì¿Í °°Áö¸¸, »óÀ§ nnn°³ ºñÆ® °ªÀÌ 1ÀÎ ³Ý¸Å½ºÅ©¸¦ + »ç¿ëÇÑ´Ù.

+
+ +

¸¶Áö¸· ¼¼°¡Áö ¿¹´Â Á¤È®È÷ µ¿ÀÏÇÑ È£½ºÆ®µéÀ» ÁöĪÇÑ´Ù.

+ +

´ÙÀ½°ú °°ÀÌ IPv6 ÁÖ¼Ò¿Í IPv6 ¼­ºê³×Æ®¿öÅ©¸¦ ÁöÁ¤ÇÒ ¼öµµ + ÀÖ´Ù:

+ +

+ Allow from 2001:db8::a00:20ff:fea7:ccea
+ Allow from 2001:db8::a00:20ff:fea7:ccea/10 +

+ +

Allow Áö½Ã¾î ¾Æ±Ô¸ÕÆ®ÀÇ ¼¼¹ø° + Çü½ÄÀº ȯ°æº¯¼ö À¯¹«¿¡ µû¶ó Á¢±ÙÀ» + Á¦¾îÇÑ´Ù. Allow from env=env-variableÀ» + »ç¿ëÇϸé, env-variable ȯ°æº¯¼ö°¡ Á¤ÀÇµÈ °æ¿ì + Á¢±ÙÀ» Çã°¡ÇÑ´Ù. mod_setenvif°¡ Á¦°øÇÏ´Â + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© Ŭ¶óÀ̾ðÆ® ¿äûÀÇ Æ¯¼º¿¡ µû¶ó ÀÚÀ¯·Ó°Ô + ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ±×·¯¹Ç·Î ÀÌ Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + Ŭ¶óÀ̾ðÆ® User-Agent (ºê¶ó¿ìÀú Á¾·ù), + Referer, ´Ù¸¥ HTTP ¿äû Çì´õ¿¡ µû¶ó Á¢±ÙÀ» + Çã°¡ÇÒ ¼ö ÀÖ´Ù.

+ +

¿¹Á¦:

+ SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
+ <Directory /docroot>
+ + Order Deny,Allow
+ Deny from all
+ Allow from env=let_me_in
+ + </Directory> +

+ +

ÀÌ °æ¿ì user-agent ¹®ÀÚ¿­ÀÌ KnockKnock/2.0À¸·Î + ½ÃÀÛÇÏ´Â ºê¶ó¿ìÀúÀÇ Á¢±ÙÀº Çã¿ëÇÏ°í, ³ª¸ÓÁö´Â ¸ðµÎ °ÅºÎÇÑ´Ù.

+ +
+
top
+

Deny Áö½Ã¾î

+ + + + + + + +
¼³¸í:¼­¹ö Á¢±ÙÀ» °ÅºÎÇÒ È£½ºÆ®¸¦ ÁöÁ¤ÇÑ´Ù
¹®¹ý: Deny from all|host|env=env-variable +[host|env=env-variable] ...
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:Limit
»óÅÂ:Base
¸ðµâ:mod_authz_host
+

ÀÌ Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© È£½ºÆ®¸í, IP ÁÖ¼Ò, ȯ°æº¯¼ö¿¡ µû¶ó + ¼­¹ö Á¢±ÙÀ» Á¦ÇÑÇÒ ¼ö ÀÖ´Ù. Deny + Áö½Ã¾îÀÇ ¾Æ±Ô¸ÕÆ®´Â Allow Áö½Ã¾î¿Í µ¿ÀÏÇÏ´Ù.

+ +
+
top
+

Order Áö½Ã¾î

+ + + + + + + + +
¼³¸í:±âº»ÀûÀ¸·Î Á¢±ÙÀ» Çã¿ëÇÒÁö °ÅºÎÇÒÁö ¿©ºÎ¿Í +Allow¿Í Deny +󸮼ø¼­¸¦ Á¤ÇÑ´Ù.
¹®¹ý: Order ordering
±âº»°ª:Order Deny,Allow
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:Limit
»óÅÂ:Base
¸ðµâ:mod_authz_host
+

Order Áö½Ã¾î´Â ±âº»ÀûÀ¸·Î Á¢±ÙÀ» + Çã¿ëÇÒÁö °ÅºÎÇÒÁö ¿©ºÎ¿Í Allow¿Í Deny Áö½Ã¾î 󸮼ø¼­¸¦ + Á¤ÇÑ´Ù. orderingÀº ´ÙÀ½ Áß ÇϳªÀÌ´Ù

+ +
+
Deny,Allow
+ +
Deny + Áö½Ã¾î¸¦ Allow + Áö½Ã¾î º¸´Ù ¸ÕÀú »ìÆ캻´Ù. ±×¸®°í ±âº»ÀûÀ¸·Î Á¢±ÙÀ» Çã¿ëÇÑ´Ù. + Deny³ª + Allow Áö½Ã¾î¿¡ + ÇØ´çµÇÁö ¾Ê´Â Ŭ¶óÀ̾ðÆ®ÀÇ Á¢±ÙÀ» Çã¿ëÇÑ´Ù.
+ +
Allow,Deny
+ +
Allow + Áö½Ã¾î¸¦ Deny Áö½Ã¾î º¸´Ù ¸ÕÀú + »ìÆ캻´Ù. ±×¸®°í ±âº»ÀûÀ¸·Î Á¢±ÙÀ» Çã¿ëÇÏÁö ¾Ê´Â´Ù. + Deny³ª + Allow Áö½Ã¾î¿¡ + ÇØ´çµÇÁö ¾Ê´Â Ŭ¶óÀ̾ðÆ®ÀÇ Á¢±ÙÀ» °ÅºÎÇÑ´Ù.
+ +
Mutual-failure
+ +
Deny + ¸ñ·Ï¿¡´Â ¾È³ª¿À°í Allow ¸ñ·Ï¿¡¸¸ ³ª¿À´Â + È£½ºÆ®¸¸ Á¢±ÙÀ» Çã¿ëÇÑ´Ù. Order Allow,Deny¿Í + °°Àº ÀÏÀ» Çϱ⶧¹®¿¡ »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+
+ +

Å°¿öµå´Â ½°Ç¥·Î¸¸ ±¸ºÐÇÑ´Ù; »çÀÌ¿¡ °ø¹éÀÌ ÀÖÀ¸¸é + ¾ÈµÈ´Ù. ¸ðµç °æ¿ì Allow¿Í Deny ¸ðµÎ »ìÆ캽À» + ¸í½ÉÇ϶ó.

+ +

¾Æ·¡ ¿¹¿¡¼­ apache.org µµ¸ÞÀÎÀÇ ¸ðµç È£½ºÆ®ÀÇ Á¢±ÙÀº + Çã¿ëÇÏÁö¸¸, ´Ù¸¥ È£½ºÆ®´Â ¸ðµÎ °ÅºÎÇÑ´Ù.

+ +

+ Order Deny,Allow
+ Deny from all
+ Allow from apache.org +

+ +

¾Æ·¡ ¿¹¿¡¼­ foo.apache.org ÇÏÀ§µµ¸ÞÀο¡ Àִ ȣ½ºÆ®¸¸ + °ÅºÎÇÏ°í, apache.org µµ¸ÞÀο¡ Àִ ȣ½ºÆ®´Â ¸ðµÎ Á¢±ÙÀ» + Çã¿ëÇÑ´Ù. ±âº»ÀûÀ¸·Î Á¢±ÙÀ» °ÅºÎÇϱ⶧¹®¿¡ apache.org µµ¸ÞÀο¡ + ¼ÓÇÏÁö ¾Ê´Â È£½ºÆ®´Â Á¢±ÙÀ» °ÅºÎÇÑ´Ù.

+ +

+ Order Allow,Deny
+ Allow from apache.org
+ Deny from foo.apache.org +

+ +

¹Ý´ë·Î À§ÀÇ Order¸¦ + Deny,Allow·Î º¯°æÇϸé, ¸ðµç È£½ºÆ®ÀÇ Á¢±ÙÀ» + Çã¿ëÇÑ´Ù. ¼³Á¤ÆÄÀÏ¿¡¼­ Áö½Ã¾î°¡ ³ª¿À´Â ¼ø¼­¿Í °ü°è¾øÀÌ + Allow from apache.org¸¦ Á¦ÀÏ ¸¶Áö¸·¿¡ ó¸®ÇÏ¿© + Deny from foo.apache.orgÀÇ È¿°ú¸¦ ¹«½ÃÇϱâ + ¶§¹®ÀÌ´Ù. ¶Ç, ±âº»ÀûÀ¸·Î Á¢±ÙÀ» Çã°¡ÇϹǷΠ+ apache.org µµ¸ÞÀο¡ ¼ÓÇÏÁö ¾Ê´Â È£½ºÆ®µµ ¸ðµÎ + Á¢±ÙÀ» Çã°¡ÇÑ´Ù.

+ +

Order Áö½Ã¾î´Â ±âº»ÀûÀ¸·Î Á¢±ÙÀ» + Çã¿ëÇÒÁö °ÅºÎÇÒÁö¸¦ Á¤Çϱ⶧¹®¿¡ Allow³ª Deny Áö½Ã¾î¸¦ »ç¿ëÇÏÁö + ¾Ê¾Æµµ Á¢±Ù°¡´É ¿©ºÎ¿¡ ¿µÇâÀ» ÁØ´Ù. ¿¹¸¦ µé¾î,

+ +

+ <Directory /www>
+ + Order Allow,Deny
+ + </Directory> +

+ +

´Â ±âº»ÀûÀ¸·Î Á¢±ÙÀ» °ÅºÎÇϱ⶧¹®¿¡ + /www µð·ºÅ丮¿¡ ´ëÇÑ ¸ðµç Á¢±ÙÀ» °ÅºÎÇÑ´Ù.

+ +

Order Áö½Ã¾î°¡ Á¤ÇÏ´Â Á¢±Ù Áö½Ã¾î + 󸮼ø¼­´Â ÇØ´ç ¼­¹ö¼³Á¤ 󸮴ܰ迡¸¸ ¿µÇâÀ» ÁØ´Ù. Áï, + Order Áö½Ã¾î ¼³Á¤°ú °ü°è¾øÀÌ <Location> ¼½¼Ç ¾È¿¡ + ÀÖ´Â Allow³ª + Deny Áö½Ã¾î´Â + <Directory> + ¼½¼ÇÀ̳ª .htaccess ÆÄÀÏ¿¡ ÀÖ´Â Allow¿Í Deny Áö½Ã¾î¸¦ ¸ðµÎ ó¸®ÇÑ + ÈÄ¿¡ ó¸®ÇÑ´Ù. ¼³Á¤ ¼½¼ÇµéÀÌ °áÇÕÇÏ´Â ¹æ¹ý¿¡ ´ëÇؼ­´Â ¾î¶»°Ô Directory, Location, Files + ¼½¼ÇÀÌ µ¿ÀÛÇϳª ¹®¼­¸¦ Âü°íÇ϶ó.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_owner.html b/docs/manual/mod/mod_authz_owner.html new file mode 100644 index 00000000..f23a815f --- /dev/null +++ b/docs/manual/mod/mod_authz_owner.html @@ -0,0 +1,11 @@ +URI: mod_authz_owner.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authz_owner.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authz_owner.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authz_owner.html.en b/docs/manual/mod/mod_authz_owner.html.en new file mode 100644 index 00000000..d61c68eb --- /dev/null +++ b/docs/manual/mod/mod_authz_owner.html.en @@ -0,0 +1,185 @@ + + + +mod_authz_owner - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authz_owner

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Authorization based on file ownership
Status:Extension
Module Identifier:authz_owner_module
Source File:mod_authz_owner.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module authorizes access to files by comparing the userid used + for HTTP authentication (the web userid) with the file-system owner or + group of the requested file. The supplied username and password + must be already properly verified by an authentication module, + such as mod_auth_basic or + mod_auth_digest. mod_authz_owner + recognizes two arguments for the Require directive, file-owner and + file-group, as follows:

+ +
+
file-owner
+
The supplied web-username must match the system's name for the + owner of the file being requested. That is, if the operating system + says the requested file is owned by jones, then the + username used to access it through the web must be jones + as well.
+ +
file-group
+
The name of the system group that owns the file must be present + in a group database, which is provided, for example, by mod_authz_groupfile or mod_authz_dbm, + and the web-username must be a member of that group. For example, if + the operating system says the requested file is owned by (system) + group accounts, the group accounts must + appear in the group database and the web-username used in the request + must be a member of that group.
+
+ +

Note

+

If mod_authz_owner is used in order to authorize + a resource that is not actually present in the filesystem + (i.e. a virtual resource), it will deny the access.

+ +

Particularly it will never authorize content negotiated + "MultiViews" resources.

+
+
+

Directives

+ +

Topics

+

See also

+
+
top
+
+

Configuration Examples

+ +

Require file-owner

+

Consider a multi-user system running the Apache Web server, with + each user having his or her own files in ~/public_html/private. Assuming that there is a single + AuthDBMUserFile database + that lists all of their web-usernames, and that these usernames match + the system's usernames that actually own the files on the server, then + the following stanza would allow only the user himself access to his + own files. User jones would not be allowed to access + files in /home/smith/public_html/private unless they + were owned by jones instead of smith.

+ +

+ <Directory /home/*/public_html/private>
+ + AuthType Basic
+ AuthName MyPrivateFiles
+ AuthBasicProvider dbm
+ AuthDBMUserFile /usr/local/apache2/etc/.htdbm-all
+ Satisfy All
+ Require file-owner
+ + </Directory> +

+ + +

Require file-group

+

Consider a system similar to the one described above, but with + some users that share their project files in + ~/public_html/project-foo. The files are owned by the + system group foo and there is a single AuthDBMGroupFile database that + contains all of the web-usernames and their group membership, + i.e. they must be at least member of a group named + foo. So if jones and smith + are both member of the group foo, then both will be + authorized to access the project-foo directories of + each other.

+ +

+ <Directory /home/*/public_html/project-foo>
+ + AuthType Basic
+ AuthName "Project Foo Files"
+ AuthBasicProvider dbm
+
+ # combined user/group database
+ AuthDBMUserFile /usr/local/apache2/etc/.htdbm-all
+ AuthDBMGroupFile /usr/local/apache2/etc/.htdbm-all
+
+ Satisfy All
+ Require file-group
+ + </Directory> +

+ +
+
top
+

AuthzOwnerAuthoritative Directive

+ + + + + + + + +
Description:Sets whether authorization will be passed on to lower level +modules
Syntax:AuthzOwnerAuthoritative On|Off
Default:AuthzOwnerAuthoritative On
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_authz_owner
+

Setting the AuthzOwnerAuthoritative + directive explicitly to Off allows for + user authorization to be passed on to lower level modules (as defined + in the modules.c files) if:

+ +
    +
  • in the case of file-owner the file-system owner does not + match the supplied web-username or could not be determined, or
    • + +
  • in the case of file-group the file-system group does not + contain the supplied web-username or could not be determined.
    • +
+ +

Note that setting the value to Off also allows the + combination of file-owner and file-group, so + access will be allowed if either one or the other (or both) match.

+ +

By default, control is not passed on and an authorization failure + will result in an "Authentication Required" reply. Not + setting it to Off thus keeps the system secure and forces + an NCSA compliant behaviour.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_owner.html.ja.euc-jp b/docs/manual/mod/mod_authz_owner.html.ja.euc-jp new file mode 100644 index 00000000..ee6ca3d9 --- /dev/null +++ b/docs/manual/mod/mod_authz_owner.html.ja.euc-jp @@ -0,0 +1,187 @@ + + + +mod_authz_owner - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authz_owner

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Î½êÍ­¼Ô¤Ë´ð¤Å¤¤¤¿¾µÇ§
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authz_owner_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authz_owner.c
¸ß´¹À­:Apache 2.1 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î + ½êÍ­¼Ô¤ä¥°¥ë¡¼¥×¤ò HTTP ǧ¾Ú¤Ë»È¤ï¤ì¤¿¥æ¡¼¥¶ ID (¥¦¥§¥Ö¥æ¡¼¥¶ ID) ¤È + Èæ³Ó¤¹¤ë¤³¤È¤Ç¥¢¥¯¥»¥¹¤ò¾µÇ§¤·¤Þ¤¹¡£Ä󶡤µ¤ì¤¿¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤Ï + mod_auth_basic ¤ä + mod_auth_digest ¤Î¤è¤¦¤Êǧ¾Ú¥â¥¸¥å¡¼¥ë¤Ç´û¤Ë + ŬÀڤ˸¡¾Ú¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£mod_authz_owner + ¤Ï°Ê²¼¤Î¤è¤¦¤Ë¡¢Require ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î file-owner ¤È + file-group ¤È¤¤¤¦Æó¤Ä¤Î°ú¿ô¤òǧ¼±¤·¤Þ¤¹:

+ +
+
file-owner
+
Ä󶡤µ¤ì¤¿¥¦¥§¥Ö¥æ¡¼¥¶Ì¾¤Ï¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î½êÍ­¼Ô¤Î + ¥·¥¹¥Æ¥à¤Ë¤ª¤±¤ë̾Á°¤È°ìÃפ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤Ä¤Þ¤ê¡¢¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥° + ¥·¥¹¥Æ¥à¤¬¥Õ¥¡¥¤¥ë¤Ï jones ¤Ë¤è¤ê½êÍ­¤µ¤ì¤Æ¤¤¤ë + ¤È¸À¤Ã¤¿¤È¤­¤Ï¡¢¥¦¥§¥Ö¤«¤é¤Î¥¢¥¯¥»¥¹¤Ë»È¤ï¤ì¤ë¥æ¡¼¥¶Ì¾¤â + jones ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
+ +
file-group
+
¥Õ¥¡¥¤¥ë¤ò½êÍ­¤¹¤ë¥·¥¹¥Æ¥à¤Î¥°¥ë¡¼¥×¤Î̾Á°¤¬¡¢Î㤨¤Ð + mod_authz_groupfile ¤ä mod_authz_dbm + ¤Ë¤è¤êÄ󶡤µ¤ì¤ë¥°¥ë¡¼¥×¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë¸ºß¤·¤Æ¤¤¤Æ¡¢ + ¥¦¥§¥Ö¥æ¡¼¥¶Ì¾¤¬¤½¤Î¥°¥ë¡¼¥×¤Ë°¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + Î㤨¤Ð¡¢¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤¬¥Õ¥¡¥¤¥ë¤Ï (¥·¥¹¥Æ¥à¤Î) ¥°¥ë¡¼¥× + accounts ¤Ë¤è¤ê½êÍ­¤µ¤ì¤Æ¤¤¤ë¤È¸À¤Ã¤¿¤È¤­¤Ï¡¢ + accounts ¤¬¥°¥ë¡¼¥×¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë¸ºß¤·¤Æ¡¢ + ¥ê¥¯¥¨¥¹¥È¤Ë»ÈÍѤµ¤ì¤¿¥¦¥§¥Ö¥æ¡¼¥¶Ì¾¤¬¤½¤Î¥°¥ë¡¼¥×¤Ë°¤·¤Æ¤¤¤ë + ɬÍפ¬¤¢¤ê¤Þ¤¹¡£
+
+ +

Ãí

+

¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë¼ÂºÝ¤Ë¤Ï¸ºß¤·¤Ê¤¤¥ê¥½¡¼¥¹ + (¤Ä¤Þ¤ê ¥Ð¡¼¥Á¥ã¥ë¤Ê¥ê¥½¡¼¥¹) ¤Î¾µÇ§¤Ë + mod_authz_owner ¤¬»ÈÍѤµ¤ì¤¿¤È¤­¤Ï¡¢ + ¥¢¥¯¥»¥¹¤ÏµñÈݤµ¤ì¤Þ¤¹¡£

+ +

Æäˡ¢¥³¥ó¥Æ¥ó¥È + ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤µ¤ì¤¿"MultiViews" ¤Î¥ê¥½¡¼¥¹¤Ï + ·è¤·¤Æ¾µÇ§¤·¤Þ¤»¤ó¡£

+
+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

¥È¥Ô¥Ã¥¯

+

»²¾È

+
+
top
+
+

ÀßÄêÎã

+ +

Require file-owner

+

Ê£¿ô¥æ¡¼¥¶¤Î¥·¥¹¥Æ¥à¤Ç Apache ¥¦¥§¥Ö¥µ¡¼¥Ð¤¬¼Â¹Ô¤µ¤ì¤Æ¤¤¤Æ¡¢ + ~/public_html/private ¤Ë³Æ¥æ¡¼¥¶¤¬¥Õ¥¡¥¤¥ë¤òÃÖ¤¤¤Æ¤¤¤ë¤È¤·¤Þ¤¹¡£ + AuthDBMUserFile + ¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬°ì¤Ä¤À¤±¤¢¤ê¡¢¤¹¤Ù¤Æ¤Î¥¦¥§¥Ö¥æ¡¼¥¶Ì¾¤¬Îóµó¤µ¤ì¤Æ¤ª¤ê¡¢ + ¤³¤Î¥æ¡¼¥¶Ì¾¤¬¥µ¡¼¥Ð¤Ç¼ÂºÝ¤Ë¥Õ¥¡¥¤¥ë¤ò½êÍ­¤·¤Æ¤¤¤ë¥æ¡¼¥¶Ì¾¤È°ìÃפ·¤Æ¤¤¤ë¾ì¹ç¡¢ + ¼¡¤ÎÀá¤Î¤è¤¦¤ÊÀßÄê¤Ç¡¢¥æ¡¼¥¶¤¬¼«Ê¬¼«¿È¤Î¥Õ¥¡¥¤¥ë¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + /home/smith/public_html/private ¤ÎÃæ¤Î¥Õ¥¡¥¤¥ë¤Ï¡¢½êÍ­¼Ô¤¬ + smith ¤ÎÂå¤ï¤ê¤Ë jones ¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢ + jones ¤Ë¤Ï¥¢¥¯¥»¥¹¤Ïµö²Ä¤µ¤ì¤Þ¤»¤ó¡£

+ +

+ <Directory /home/*/public_html/private>
+ + AuthType Basic
+ AuthName MyPrivateFiles
+ AuthBasicProvider dbm
+ AuthDBMUserFile /usr/local/apache2/etc/.htdbm-all
+ Satisfy All
+ Require file-owner
+ + </Directory> +

+ + +

Require file-group

+

¾åµ­¤Î¤è¤¦¤Ê¥·¥¹¥Æ¥à¤Ç¡¢¿ô¿Í¤Î¥æ¡¼¥¶¤¬¥×¥í¥¸¥§¥¯¥È¤Î¥Õ¥¡¥¤¥ë¤ò + ~/public_html/project-foo ¤Ç¶¦Í­¤·¤Æ¤¤¤ë¤È¤·¤Þ¤¹¡£ + ¥Õ¥¡¥¤¥ë¤Ï¥·¥¹¥Æ¥à¤Î¥°¥ë¡¼¥× foo ¤Ë½êÍ­¤µ¤ì¤Æ¤¤¤Æ¡¢ + AuthDBMGroupFile + ¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬°ì¤Ä¤À¤±¤¢¤ê¡¢¤½¤³¤Ë¤¹¤Ù¤Æ¤Î¥¦¥§¥Ö¥æ¡¼¥¶Ì¾¤È + ¥°¥ë¡¼¥×¤Î¥á¥ó¥Ð¤¬Îóµó¤µ¤ì¤Æ¤¤¤ë¡¢¤Ä¤Þ¤ê¡¢¤½¤ì¤é¤Î + ¥æ¡¼¥¶¤Ï¾¯¤Ê¤¯¤È¤â foo ¤È¤¤¤¦¥°¥ë¡¼¥×¤Ë°¤·¤Æ¤¤¤ë¡¢¤È¤·¤Þ¤¹¡£ + jones ¤Èsmith ¤ÎÆó¿Í¶¦¤¬¥°¥ë¡¼¥× + foo ¤Î¥á¥ó¥Ð¤Ç¤¢¤ë¾ì¹ç¡¢¤É¤Á¤é¤Î¿Í¤âξÊý¤Î + project-foo ¤Ë¥¢¥¯¥»¥¹¤¬µö²Ä¤µ¤ì¤Þ¤¹¡£

+ +

+ <Directory /home/*/public_html/project-foo>
+ + AuthType Basic
+ AuthName "Project Foo Files"
+ AuthBasicProvider dbm
+
+ # combined user/group database
+ AuthDBMUserFile /usr/local/apache2/etc/.htdbm-all
+ AuthDBMGroupFile /usr/local/apache2/etc/.htdbm-all
+
+ Satisfy All
+ Require file-group
+ + </Directory> +

+ +
+
top
+

AuthzOwnerAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¾µÇ§¤¬²¼°Ì¾µÇ§¥â¥¸¥å¡¼¥ë¤ËÅϤµ¤ì¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
¹½Ê¸:AuthzOwnerAuthoritative On|Off
¥Ç¥Õ¥©¥ë¥È:AuthzOwnerAuthoritative On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_authz_owner
+

AuthzOwnerAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ÌÀ¼¨Åª¤Ë Off ¤ËÀßÄꤹ¤ë¤È¡¢°Ê²¼¤Î¾ì¹ç¤Ëǧ¾Ú¤¬ + (modules.c ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë) ²¼°Ì¤Î¥â¥¸¥å¡¼¥ë¤Ë + ÅϤµ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹:

+ +
    +
  • file-owner ¤Î¾ì¹ç¤Ï¡¢Ä󶡤µ¤ì¤¿¥¦¥§¥Ö¥æ¡¼¥¶Ì¾¤Ë + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î½êÍ­¼Ô¤¬°ìÃפ·¤Ê¤¤¤«¡¢½êÍ­¼Ô¤¬¤ï¤«¤é¤Ê¤¤¾ì¹ç¡£
    • + +
  • file-group ¤Î¾ì¹ç¤Ï¡¢Ä󶡤µ¤ì¤¿¥¦¥§¥Ö¥æ¡¼¥¶Ì¾¤¬ + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥°¥ë¡¼¥×¤Ë¸ºß¤·¤Ê¤¤¤«¡¢¤ï¤«¤é¤Ê¤¤¾ì¹ç¡£
    • +
+ +

Ãͤò Off ¤ËÀßÄꤹ¤ë¤È¡¢file-owner ¤È + file-group ¤òÁȤ߹ç¤ï¤»¤ë¤³¤È¤â¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¡¢ + ¤½¤Î¾ì¹ç¤Ï¤É¤Á¤é¤« (ξÊý¤Ç¤â) ¤Ë¥Þ¥Ã¥Á¤·¤¿¾ì¹ç¤Ë¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤Þ¤¹¡£

+ +

¥Ç¥Õ¥©¥ë¥È¤Ç¤ÏÀ©¸æ¤ÏÅϤµ¤ì¤º¡¢Ì¤ÃΤΥ°¥ë¡¼¥×¤Î¾ì¹ç¤Ï Authentication + Required ±þÅú¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢Off ¤ËÀßÄꤷ¤Ê¤¤¤³¤È¤Ç + ¥·¥¹¥Æ¥à¤ò°ÂÁ´¤ËÊݤĤ³¤È¤¬¤Ç¤­¡¢NCSA ¸ß´¹¤Î¿¶¤ëÉñ¤¤¤ò¤µ¤»¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_owner.html.ko.euc-kr b/docs/manual/mod/mod_authz_owner.html.ko.euc-kr new file mode 100644 index 00000000..094ae8c8 --- /dev/null +++ b/docs/manual/mod/mod_authz_owner.html.ko.euc-kr @@ -0,0 +1,182 @@ + + + +mod_authz_owner - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authz_owner

+
+

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

+
+ + + + +
¼³¸í:ÆÄÀÏ ¼ÒÀ¯ÀÚ¸¦ ÀÌ¿ëÇÑ ±ÇÇѺο©
»óÅÂ:Extension
¸ðµâ¸í:authz_owner_module
¼Ò½ºÆÄÀÏ:mod_authz_owner.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº HTTP ÀÎÁõ¿¡ »ç¿ëÇÑ »ç¿ëÀÚ ¾ÆÀ̵ð(À¥ »ç¿ëÀÚ + ¾ÆÀ̵ð)¸¦ ¿äûÇÑ ÆÄÀÏÀÇ ÆÄÀϽýºÅÛ ¼ÒÀ¯ÀÚ/±×·ì°ú ºñ±³ÇÏ¿© + ÆÄÀÏÀÇ Á¢±Ù±ÇÇÑÀ» ºÎ¿©ÇÑ´Ù. ¿©±â¼­ »ç¿ëÀÚ¸í°ú ¾ÏÈ£´Â ÀÌ¹Ì + mod_auth_basicÀ̳ª + mod_auth_digest °°Àº ÀÎÁõ¸ðµâÀÇ È®ÀÎÀ» + °ÅÃÆ´Ù. mod_authz_owner´Â Require Áö½Ã¾îÀÇ ´ÙÀ½ µÎ ¾Æ±Ô¸ÕÆ®, + file-owner¿Í file-groupÀ» ó¸®ÇÑ´Ù:

+ +
+
file-owner
+
À¥ »ç¿ëÀÚ¸íÀÌ ¿äûÇÑ ÆÄÀÏ ¼ÒÀ¯ÀÚÀÇ ½Ã½ºÅÛ À̸§°ú °°¾Æ¾ß + ÇÑ´Ù. Áï, ¿î¿µÃ¼Á¦°¡ ¿äûÇÑ ÆÄÀÏÀÇ ¼ÒÀ¯ÀÚ°¡ + jones¶ó¸é, À¥À» ÅëÇØ ÆÄÀÏ¿¡ Á¢±ÙÇÏ´Â »ç¿ëÀÚµµ + ¸¶Âù°¡Áö·Î jonesÀ̾î¾ß ÇÑ´Ù.
+ +
file-group
+
ÆÄÀÏÀ» ¼ÒÀ¯ÇÑ ½Ã½ºÅÛ ±×·ì¸íÀÌ + mod_authz_groupfileÀ̳ª + mod_authz_dbm°ú °°Àº ±×·ì µ¥ÀÌÅͺ£À̽º¿¡ + ÀÖ°í, À¥ »ç¿ëÀÚ¸íÀÌ ÇØ´ç ±×·ì¿¡ ¼ÓÇØ¾ß ÇÑ´Ù. ¿¹¸¦ µé¾î, + ¿î¿µÃ¼Á¦°¡ ¿äûÇÑ ÆÄÀÏÀ» accounts (½Ã½ºÅÛ) + ±×·ìÀÌ ¼ÒÀ¯ÇÏ°í ÀÖ´Ù¸é, ±×·ì µ¥ÀÌÅͺ£À̽º¿¡ + accounts¶ó´Â ±×·ìÀÌ ÀÖ°í ¿äû¿¡ »ç¿ëÇÑ À¥ + »ç¿ëÀÚ¸íÀÌ ±× ±×·ì¿¡ ¼ÓÇØ¾ß ÇÑ´Ù.
+
+ +

ÁÖÀÇ

+

mod_authz_owner°¡ ½ÇÁ¦·Î ÆÄÀϽýºÅÛ¿¡ + ÀÖÁö ¾Ê´Â ÀÚ¿øÀ» (Áï, °¡»ó ÀÚ¿ø) ±ÇÇѺο©ÇÑ´Ù¸é, + Á¢±ÙÀ» °ÅºÎÇÑ´Ù.

+ +

ƯÈ÷ ³»¿ëÇù»óÇÑ + "MultiViews" ÀÚ¿øÀ» ±ÇÇѺο©ÇÏÁö ¾Ê´Â´Ù.

+
+
+

Áö½Ã¾îµé

+ +

ÁÖÁ¦

+

Âü°í

+
+
top
+
+

¼³Á¤ ¿¹Á¦

+ +

Require file-owner

+

¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ¿î¿µÇÏ´Â ´ÙÁß»ç¿ëÀÚ ½Ã½ºÅÛ¿¡¼­ °¢ »ç¿ëÀÚ°¡ + ~/public_html/private¿¡ ÀÚ½ÅÀÇ ÆÄÀÏÀ» ÀúÀåÇÑ´Ù°í + °¡Á¤ÇÏÀÚ. ¸ðµç À¥ »ç¿ëÀÚ¸íÀ» ÀúÀåÇÏ´Â AuthDBMUserFile + µ¥ÀÌÅͺ£À̽º°¡ ÀÖ°í, ¿©±â¿¡ ÀúÀåµÈ »ç¿ëÀÚ¸íÀº ¼­¹ö¿¡¼­ + ½ÇÁ¦ ÆÄÀÏÀ» ¼ÒÀ¯ÇÏ´Â ½Ã½ºÅÛ »ç¿ëÀÚ¸í°ú µ¿ÀÏÇÏ´Ù. ÀÌ °æ¿ì + ¾Æ·¡ ¼³Á¤Àº ÆÄÀÏ ¼ÒÀ¯ÀÚ¿¡°Ô¸¸ Á¢±ÙÀ» Çã¿ëÇÑ´Ù. »ç¿ëÀÚ + jones´Â ÆÄÀÏÀ» jones°¡ ¾Æ´Ñ + smith°¡ ¼ÒÀ¯ÇÏ°í ÀÖ´Â ÇÑ + /home/smith/public_html/private¿¡ ÀÖ´Â ÆÄÀÏ¿¡ + Á¢±ÙÇÒ ¼ö ¾ø´Ù.

+ +

+ <Directory /home/*/public_html/private>
+ + AuthType Basic
+ AuthName MyPrivateFiles
+ AuthBasicProvider dbm
+ AuthDBMUserFile /usr/local/apache2/etc/.htdbm-all
+ Satisfy All
+ Require file-owner
+ + </Directory> +

+ + +

Require file-group

+

À§¿Í »óȲÀÌ ºñ½ÁÇÏÁö¸¸ ¿©·¯¸íÀÌ + ~/public_html/project-foo¿¡ ÇÁ·ÎÁ§Æ® ÆÄÀÏÀ» + °øÀ¯ÇÑ´Ù°í °¡Á¤ÇÏÀÚ. ÆÄÀϵéÀº ½Ã½ºÅÛ ±×·ì foo°¡ + ¼ÒÀ¯Çϸç, ¸ðµç À¥ »ç¿ëÀÚ¸í°ú »ç¿ëÀÚ ±×·ìÀ» ±â·ÏÇÏ´Â AuthDBMGroupFile + µ¥ÀÌÅͺ£À̽º°¡ ÀÖ´Ù. Áï, ÃÖ¼ÒÇÑ foo¶ó´Â + ±×·ì¿¡ ±¸¼º¿øÀÌ ÀÖ´Ù. jones¿Í + smith°¡ ¸ðµÎ ±×·ì fooÀÇ + ±¸¼º¿øÀ̶ó¸é, µÑ ¸ðµÎ project-foo µð·ºÅ丮¿¡ + Á¢±ÙÇÒ ¼ö ÀÖ´Ù.

+ +

+ <Directory /home/*/public_html/project-foo>
+ + AuthType Basic
+ AuthName "Project Foo Files"
+ AuthBasicProvider dbm
+
+ # combined user/group database
+ AuthDBMUserFile /usr/local/apache2/etc/.htdbm-all
+ AuthDBMGroupFile /usr/local/apache2/etc/.htdbm-all
+
+ Satisfy All
+ Require file-group
+ + </Directory> +

+ +
+
top
+

AuthzOwnerAuthoritative Áö½Ã¾î

+ + + + + + + + +
¼³¸í:±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
¹®¹ý:AuthzOwnerAuthoritative On|Off
±âº»°ª:AuthzOwnerAuthoritative On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Extension
¸ðµâ:mod_authz_owner
+

AuthzOwnerAuthoritative Áö½Ã¾î¸¦ + Á÷Á¢ Off·Î ¼³Á¤ÇÏ¸é ´ÙÀ½°ú °°Àº °æ¿ì »ç¿ëÀÚ + ±ÇÇѺο©¸¦ (modules.c ÆÄÀÏ¿¡¼­ Á¤ÀÇÇÑ) Àú¼öÁØ + ¸ðµâ·Î ³Ñ°ÜÁØ´Ù.

+ +
    +
  • file-owner¸¦ »ç¿ëÇϸé ÆÄÀϽýºÅÛ ¼ÒÀ¯ÀÚ¸¦ + ¾Ë ¼ö ¾ø°Å³ª ÁÖ¾îÁø À¥ »ç¿ëÀÚ¸í°ú ´Ù¸¥ °æ¿ì
    • + +
  • file-groupÀ» »ç¿ëÇϸé ÆÄÀϽýºÅÛ ±×·ìÀ» + ¾Ë ¼ö ¾ø°Å³ª ÁÖ¾îÁø À¥ »ç¿ëÀÚ¸íÀÌ ±¸¼º¿øÀÌ ¾Æ´Ñ °æ¿ì.
    • +
+ +

¶Ç, °ªÀ» Off·Î ¼³Á¤Çϸé + file-owner¿Í file-groupÀ» °áÇÕÇÏ¿©, + µÑ Áß Çϳª¸¸ ¸¸Á·Çصµ Á¢±ÙÀ» Çã°¡ÇÑ´Ù.

+ +

±âº»ÀûÀ¸·Î Á¦¾î¸¦ ³Ñ±âÁö¾Ê°í, ¸ð¸£´Â ±×·ìÀÇ °æ¿ì ÀÎÁõ + ÇÊ¿ä ÀÀ´äÀ» ÇÑ´Ù. ÀÌ Áö½Ã¾î¸¦ Off·Î ¼³Á¤ÇÏÁö¾ÊÀ¸¸é + ½Ã½ºÅÛÀÌ ¾ÈÀüÇÏ°Ô À¯ÁöµÇ¸ç, NCSA À¥¼­¹ö¿Í °°ÀÌ µ¿ÀÛÇÑ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_user.html b/docs/manual/mod/mod_authz_user.html new file mode 100644 index 00000000..bbf7fe11 --- /dev/null +++ b/docs/manual/mod/mod_authz_user.html @@ -0,0 +1,11 @@ +URI: mod_authz_user.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_authz_user.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_authz_user.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_authz_user.html.en b/docs/manual/mod/mod_authz_user.html.en new file mode 100644 index 00000000..34e1b957 --- /dev/null +++ b/docs/manual/mod/mod_authz_user.html.en @@ -0,0 +1,84 @@ + + + +mod_authz_user - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_authz_user

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:User Authorization
Status:Base
Module Identifier:authz_user_module
Source File:mod_authz_user.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module provides authorization capabilities so that + authenticated users can be allowed or denied access to portions + of the web site. mod_authz_user grants + access if the authenticated user is listed in a Require user + directive. Alternatively require valid-user can be used to + grant access to all successfully authenticated users.

+
+

Directives

+ +

See also

+
+ +
top
+

AuthzUserAuthoritative Directive

+ + + + + + + + +
Description:Sets whether authorization will be passed on to lower level +modules
Syntax:AuthzUserAuthoritative On|Off
Default:AuthzUserAuthoritative On
Context:directory, .htaccess
Override:AuthConfig
Status:Base
Module:mod_authz_user
+

Setting the AuthzUserAuthoritative + directive explicitly to Off allows for + user authorization to be passed on to lower level modules (as defined + in the modules.c files) if there is no + user matching the supplied userID.

+ +

By default, control is not passed on and an unknown user + will result in an Authentication Required reply. Not + setting it to Off thus keeps the system secure and forces + an NCSA compliant behaviour.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_user.html.ja.euc-jp b/docs/manual/mod/mod_authz_user.html.ja.euc-jp new file mode 100644 index 00000000..261d39bc --- /dev/null +++ b/docs/manual/mod/mod_authz_user.html.ja.euc-jp @@ -0,0 +1,83 @@ + + + +mod_authz_user - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_authz_user

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:¥æ¡¼¥¶¾µÇ§
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:authz_user_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_authz_user.c
¸ß´¹À­:Apache 2.1 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢Ç§¾Ú¤µ¤ì¤¿¥æ¡¼¥¶¤Ë¥¦¥§¥Ö¥µ¥¤¥È¤Î°ìÉô¤Ø¤Î + ¥¢¥¯¥»¥¹¤òµö²Ä¤·¤¿¤êµñÈݤ·¤¿¤ê¤¹¤ë¤¿¤á¤Î¾µÇ§µ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£ + mod_authz_user ¤Ïǧ¾Ú¤µ¤ì¤¿¥æ¡¼¥¶¤¬ + Require user ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë½ñ¤«¤ì¤Æ¤¤¤ì¤Ð + ¥¢¥¯¥»¥¹¤òǧ¤á¤Þ¤¹¡£Ç§¾Ú¤ËÀ®¸ù¤·¤¿¥æ¡¼¥¶¤¹¤Ù¤Æ¤Ë¥¢¥¯¥»¥¹¤ò + µö²Ä¤¹¤ë¤Ë¤Ï¡¢Âå¤ï¤ê¤Ë require valid-user ¤ò + »È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

AuthzUserAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¾µÇ§¤¬²¼°Ì¤Î¥â¥¸¥å¡¼¥ë¤ËÅϤµ¤ì¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
¹½Ê¸:AuthzUserAuthoritative On|Off
¥Ç¥Õ¥©¥ë¥È:AuthzUserAuthoritative On
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:AuthConfig
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_authz_user
+

AuthzUserAuthoritative ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ÌÀ¼¨Åª¤Ë Off ¤ËÀßÄꤹ¤ë¤È userID ¤ËÂбþ¤¹¤ë + ¥°¥ë¡¼¥×¤¬¤Ê¤¤¾ì¹ç¤Ë¡¢ + (module.c ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë) ²¼°Ì¤Î¥â¥¸¥å¡¼¥ë¤Ë¥°¥ë¡¼¥×¾µÇ§¤ò + ÅϤ¹¤³¤È¤òµö²Ä¤·¤Þ¤¹¡£

+ +

¥Ç¥Õ¥©¥ë¥È¤Ç¤ÏÀ©¸æ¤ÏÅϤµ¤ì¤º¡¢Ì¤ÃΤΥ°¥ë¡¼¥×¤Î¾ì¹ç¤Ï Authentication + Required ±þÅú¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢¤³¤ì¤òÀßÄꤷ¤Ê¤¤¤È + ¥·¥¹¥Æ¥à¤ò°ÂÁ´¤ËÊݤĤ³¤È¤¬¤Ç¤­¡¢NCSA ¸ß´¹¤Î¿¶¤ëÉñ¤¤¤ò¤µ¤»¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_authz_user.html.ko.euc-kr b/docs/manual/mod/mod_authz_user.html.ko.euc-kr new file mode 100644 index 00000000..11bce391 --- /dev/null +++ b/docs/manual/mod/mod_authz_user.html.ko.euc-kr @@ -0,0 +1,81 @@ + + + +mod_authz_user - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_authz_user

+
+

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

+
+ + + + +
¼³¸í:»ç¿ëÀÚ ±ÇÇѺο©
»óÅÂ:Base
¸ðµâ¸í:authz_user_module
¼Ò½ºÆÄÀÏ:mod_authz_user.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ±ÇÇÑÀ» ºÎ¿©ÇÏ¿©, ÀÎÁõÇÑ »ç¿ëÀÚ°¡ À¥»çÀÌÆ®ÀÇ + ÀϺο¡ Á¢±ÙÇÒ ¼ö ÀÖ´ÂÁö °áÁ¤ÇÑ´Ù. + mod_authz_user´Â Require user + Áö½Ã¾î ¸ñ·Ï¿¡ ÀÎÁõÇÑ »ç¿ëÀÚ°¡ µé¾îÀÖÀ¸¸é Á¢±ÙÀ» Çã¿ëÇÑ´Ù. + ¶Ç, require valid-user´Â ¼º°øÀûÀ¸·Î ÀÎÁõÇÑ + »ç¿ëÀÚ ¸ðµÎ¿¡°Ô Á¢±ÙÀ» Çã¿ëÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

AuthzUserAuthoritative Áö½Ã¾î

+ + + + + + + + +
¼³¸í:±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
¹®¹ý:AuthzUserAuthoritative On|Off
±âº»°ª:AuthzUserAuthoritative On
»ç¿ëÀå¼Ò:directory, .htaccess
Override ¿É¼Ç:AuthConfig
»óÅÂ:Base
¸ðµâ:mod_authz_user
+

AuthzUserAuthoritative Áö½Ã¾î¸¦ + Á÷Á¢ Off·Î ¼³Á¤Çϸé ÇØ´ç »ç¿ëÀÚ°¡ + ¾ø´Â °æ¿ì »ç¿ëÀÚ ±ÇÇѺο©¸¦ (modules.c + ÆÄÀÏ¿¡¼­ Á¤ÀÇÇÑ) Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁØ´Ù.

+ +

±âº»ÀûÀ¸·Î Á¦¾î¸¦ ³Ñ±âÁö¾Ê°í, ¸ð¸£´Â »ç¿ëÀÚÀÇ °æ¿ì ÀÎÁõ + ÇÊ¿ä ÀÀ´äÀ» ÇÑ´Ù. ÀÌ Áö½Ã¾î¸¦ Off·Î ¼³Á¤ÇÏÁö¾ÊÀ¸¸é + ½Ã½ºÅÛÀÌ ¾ÈÀüÇÏ°Ô À¯ÁöµÇ¸ç, NCSA À¥¼­¹ö¿Í °°ÀÌ µ¿ÀÛÇÑ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_autoindex.html b/docs/manual/mod/mod_autoindex.html new file mode 100644 index 00000000..16baec2f --- /dev/null +++ b/docs/manual/mod/mod_autoindex.html @@ -0,0 +1,11 @@ +URI: mod_autoindex.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_autoindex.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_autoindex.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_autoindex.html.en b/docs/manual/mod/mod_autoindex.html.en new file mode 100644 index 00000000..87a734f5 --- /dev/null +++ b/docs/manual/mod/mod_autoindex.html.en @@ -0,0 +1,893 @@ + + + +mod_autoindex - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_autoindex

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Generates directory indexes, + automatically, similar to the Unix ls command or the + Win32 dir shell command
Status:Base
Module Identifier:autoindex_module
Source File:mod_autoindex.c
+

Summary

+ +

The index of a directory can come from one of two + sources:

+ +
    +
  • A file written by the user, typically called + index.html. The DirectoryIndex directive sets the + name of this file. This is controlled by + mod_dir.
    • + +
  • Otherwise, a listing generated by the server. The other + directives control the format of this listing. The AddIcon, AddIconByEncoding and + AddIconByType are + used to set a list of icons to display for various file types; + for each file listed, the first icon listed that matches the + file is displayed. These are controlled by + mod_autoindex.
    • +
+

The two functions are separated so that you can completely + remove (or replace) automatic index generation should you want + to.

+ +

Automatic index generation is enabled with using + Options +Indexes. See the + Options directive for + more details.

+ +

If the FancyIndexing option is given with the IndexOptions directive, + the column headers are links that control the order of the + display. If you select a header link, the listing will be + regenerated, sorted by the values in that column. Selecting the + same header repeatedly toggles between ascending and descending + order. These column header links are suppressed with + IndexOptions directive's + SuppressColumnSorting option.

+ +

Note that when the display is sorted by "Size", it's the + actual size of the files that's used, not the + displayed value - so a 1010-byte file will always be displayed + before a 1011-byte file (if in ascending order) even though + they both are shown as "1K".

+
+ +
top
+
+

Autoindex Request Query Arguments

+ + +

Apache 2.0.23 reorganized the Query Arguments for Column + Sorting, and introduced an entire group of new query options. + To effectively eliminate all client control over the output, + the IndexOptions + IgnoreClient option was introduced.

+ +

The column sorting headers themselves are self-referencing + hyperlinks that add the sort query options shown below. Any + option below may be added to any request for the directory + resource.

+ +
    +
  • C=N sorts the directory by file name
    • + +
  • C=M sorts the directory by last-modified + date, then file name
    • + +
  • C=S sorts the directory by size, then file + name
    • + +
  • C=D sorts the directory by description, then + file name
    • + +
  • O=A sorts the listing in Ascending + Order
    • + +
  • O=D sorts the listing in Descending + Order
    • + +
  • F=0 formats the listing as a simple list + (not FancyIndexed)
    • + +
  • F=1 formats the listing as a FancyIndexed + list
    • + +
  • F=2 formats the listing as an + HTMLTable FancyIndexed list
    • + +
  • V=0 disables version sorting
    • + +
  • V=1 enables version sorting
    • + +
  • P=pattern lists only files matching + the given pattern
    • +
+ +

Note that the 'P'attern query argument is tested + after the usual IndexIgnore directives are processed, + and all file names are still subjected to the same criteria as + any other autoindex listing. The Query Arguments parser in + mod_autoindex will stop abruptly when an unrecognized + option is encountered. The Query Arguments must be well formed, + according to the table above.

+ +

The simple example below, which can be clipped and saved in + a header.html file, illustrates these query options. Note that + the unknown "X" argument, for the submit button, is listed last + to assure the arguments are all parsed before mod_autoindex + encounters the X=Go input.

+ +

+ <form action="" method="get">
+ + Show me a <select name="F">
+ + <option value="0"> Plain list</option>
+ <option value="1" selected="selected"> Fancy list</option>
+ <option value="2"> Table list</option>
+ + </select>
+ Sorted by <select name="C">
+ + <option value="N" selected="selected"> Name</option>
+ <option value="M"> Date Modified</option>
+ <option value="S"> Size</option>
+ <option value="D"> Description</option>
+ + </select>
+ <select name="O">
+ + <option value="A" selected="selected"> Ascending</option>
+ <option value="D"> Descending</option>
+ + </select>
+ <select name="V">
+ + <option value="0" selected="selected"> in Normal order</option>
+ <option value="1"> in Version order</option>
+ + </select>
+ Matching <input type="text" name="P" value="*" />
+ <input type="submit" name="X" value="Go" />
+ + </form> +

+ +
+
top
+

AddAlt Directive

+ + + + + + + +
Description:Alternate text to display for a file, instead of an +icon selected by filename
Syntax:AddAlt string file [file] ...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

AddAlt provides the alternate text to + display for a file, instead of an icon, for FancyIndexing. + File is a file extension, partial filename, wild-card + expression or full filename for files to describe. + If String contains any whitespace, you have to enclose it + in quotes (" or '). This alternate text + is displayed if the client is image-incapable, has image loading + disabled, or fails to retrieve the icon.

+ +

Examples

+ AddAlt "PDF file" *.pdf
+ AddAlt Compressed *.gz *.zip *.Z +

+ +
+
top
+

AddAltByEncoding Directive

+ + + + + + + +
Description:Alternate text to display for a file instead of an icon +selected by MIME-encoding
Syntax:AddAltByEncoding string MIME-encoding +[MIME-encoding] ...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

AddAltByEncoding provides the alternate + text to display for a file, instead of an icon, for FancyIndexing. + MIME-encoding is a valid content-encoding, such as + x-compress. If String contains any whitespace, + you have to enclose it in quotes (" or '). + This alternate text is displayed if the client is image-incapable, + has image loading disabled, or fails to retrieve the icon.

+ +

Example

+ AddAltByEncoding gzip x-gzip +

+ +
+
top
+

AddAltByType Directive

+ + + + + + + +
Description:Alternate text to display for a file, instead of an +icon selected by MIME content-type
Syntax:AddAltByType string MIME-type +[MIME-type] ...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

AddAltByType sets the alternate text to + display for a file, instead of an icon, for FancyIndexing. + MIME-type is a valid content-type, such as + text/html. If String contains any whitespace, + you have to enclose it in quotes (" or '). + This alternate text is displayed if the client is image-incapable, + has image loading disabled, or fails to retrieve the icon.

+ +

Example

+ AddAltByType 'plain text' text/plain +

+ +
+
top
+

AddDescription Directive

+ + + + + + + +
Description:Description to display for a file
Syntax:AddDescription string file [file] ...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

This sets the description to display for a file, for + FancyIndexing. + File is a file extension, partial filename, wild-card + expression or full filename for files to describe. + String is enclosed in double quotes (").

+ +

Example

+ AddDescription "The planet Mars" /web/pics/mars.gif +

+ +

The typical, default description field is 23 bytes wide. 6 + more bytes are added by the IndexOptions SuppressIcon option, 7 bytes are + added by the IndexOptions SuppressSize option, and 19 bytes are + added by the IndexOptions SuppressLastModified option. + Therefore, the widest default the description column is ever + assigned is 55 bytes.

+ +

See the DescriptionWidth IndexOptions keyword for details on overriding the size + of this column, or allowing descriptions of unlimited length.

+ +

Caution

+

Descriptive text defined with AddDescription + may contain HTML markup, such as tags and character entities. If the + width of the description column should happen to truncate a tagged + element (such as cutting off the end of a bolded phrase), the + results may affect the rest of the directory listing.

+
+ +
+
top
+

AddIcon Directive

+ + + + + + + +
Description:Icon to display for a file selected by name
Syntax:AddIcon icon name [name] +...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

This sets the icon to display next to a file ending in + name for FancyIndexing. Icon is either a (%-escaped) + relative URL to the icon, or of the format + (alttext,url) where alttext + is the text tag given for an icon for non-graphical browsers.

+ +

Name is either ^^DIRECTORY^^ for directories, + ^^BLANKICON^^ for blank lines (to format the list + correctly), a file extension, a wildcard expression, a partial + filename or a complete filename.

+ +

Examples

+ AddIcon (IMG,/icons/image.xbm) .gif .jpg .xbm
+ AddIcon /icons/dir.xbm ^^DIRECTORY^^
+ AddIcon /icons/backup.xbm *~ +

+ +

AddIconByType + should be used in preference to AddIcon, + when possible.

+ +
+
top
+

AddIconByEncoding Directive

+ + + + + + + +
Description:Icon to display next to files selected by MIME +content-encoding
Syntax:AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

This sets the icon to display next to files with FancyIndexing. + Icon is either a (%-escaped) relative URL to the icon, + or of the format (alttext,url) + where alttext is the text tag given for an icon for + non-graphical browsers.

+ +

MIME-encoding is a wildcard expression matching + required the content-encoding.

+ +

Example

+ AddIconByEncoding /icons/compress.xbm x-compress +

+ +
+
top
+

AddIconByType Directive

+ + + + + + + +
Description:Icon to display next to files selected by MIME +content-type
Syntax:AddIconByType icon MIME-type +[MIME-type] ...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

This sets the icon to display next to files of type + MIME-type for FancyIndexing. + Icon is either a (%-escaped) relative URL to the icon, + or of the format (alttext,url) + where alttext is the text tag given for an icon for + non-graphical browsers.

+ +

MIME-type is a wildcard expression matching + required the mime types.

+ +

Example

+ AddIconByType (IMG,/icons/image.xbm) image/* +

+ +
+
top
+

DefaultIcon Directive

+ + + + + + + +
Description:Icon to display for files when no specific icon is +configured
Syntax:DefaultIcon url-path
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

The DefaultIcon directive sets the icon + to display for files when no specific icon is known, for FancyIndexing. + Url-path is a (%-escaped) relative URL to the icon.

+ +

Example

+ DefaultIcon /icon/unknown.xbm +

+ +
+
top
+

HeaderName Directive

+ + + + + + + +
Description:Name of the file that will be inserted at the top +of the index listing
Syntax:HeaderName filename
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

The HeaderName directive sets the name + of the file that will be inserted at the top of the index + listing. Filename is the name of the file to include.

+ +

Example

+ HeaderName HEADER.html +

+ +
+

Both HeaderName and ReadmeName now treat + Filename as a URI path relative to the one used to + access the directory being indexed. If Filename begins + with a slash, it will be taken to be relative to the DocumentRoot.

+ +

Example

+ HeaderName /include/HEADER.html +

+ +

Filename must resolve to a document with a major + content type of text/* (e.g., + text/html, text/plain, etc.). This means + that filename may refer to a CGI script if the script's + actual file type (as opposed to its output) is marked as + text/html such as with a directive like:

+ +

+ AddType text/html .cgi +

+ +

Content negotiation + will be performed if Options + MultiViews is in effect. If filename resolves + to a static text/html document (not a CGI script) and + either one of the options + Includes or IncludesNOEXEC is enabled, + the file will be processed for server-side includes (see the + mod_include documentation).

+
+ +

If the file specified by HeaderName contains + the beginnings of an HTML document (<html>, <head>, etc.) + then you will probably want to set IndexOptions + +SuppressHTMLPreamble, so that these tags are not + repeated.

+ +
+
top
+

IndexIgnore Directive

+ + + + + + + +
Description:Adds to the list of files to hide when listing +a directory
Syntax:IndexIgnore file [file] ...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

The IndexIgnore directive adds to the + list of files to hide when listing a directory. File is a + shell-style wildcard expression or full + filename. Multiple IndexIgnore directives add + to the list, rather than the replacing the list of ignored + files. By default, the list contains . (the current + directory).

+ +

+ IndexIgnore README .htaccess *.bak *~ +

+ +
+
top
+

IndexOptions Directive

+ + + + + + + +
Description:Various configuration settings for directory +indexing
Syntax:IndexOptions [+|-]option [[+|-]option] +...
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

The IndexOptions directive specifies the + behavior of the directory indexing. Option can be one + of

+ +
+
DescriptionWidth=[n | *] (Apache 2.0.23 and + later)
+ +
The DescriptionWidth keyword allows you to + specify the width of the description column in + characters.
+ +
-DescriptionWidth (or unset) allows + mod_autoindex to calculate the best width.
+ +
DescriptionWidth=n fixes the column width to + n bytes wide.
+ +
DescriptionWidth=* grows the column to the + width necessary to accommodate the longest description + string.
+ +
See the section on AddDescription for dangers + inherent in truncating descriptions.
+ +
FancyIndexing
+ +
This turns on fancy indexing of directories.
+ +
FoldersFirst (Apache + 2.0.23 and later)
+ +
If this option is enabled, subdirectory listings will + always appear first, followed by normal files in the + directory. The listing is basically broken into two + components, the files and the subdirectories, and each is + sorted separately and then displayed subdirectories-first. + For instance, if the sort order is descending by name, and + FoldersFirst is enabled, subdirectory + Zed will be listed before subdirectory + Beta, which will be listed before normal files + Gamma and Alpha. This option + only has an effect if FancyIndexing is also enabled.
+ +
HTMLTable (Experimental, + Apache 2.0.23 and later)
+ +
This experimental option with FancyIndexing constructs a + simple table for the fancy directory listing. Note this will + confuse older browsers. It is particularly necessary if file + names or description text will alternate between + left-to-right and right-to-left reading order, as can happen + on WinNT or other utf-8 enabled platforms.
+ +
IconsAreLinks
+ +
This makes the icons part of the anchor for the filename, for + fancy indexing.
+ +
IconHeight[=pixels]
+ +
Presence of this option, when used with IconWidth, will cause + the server to include height and width + attributes in the img tag for the file icon. This allows + browser to precalculate the page layout without having to wait until + all the images have been loaded. If no value is given for the option, + it defaults to the standard height of the icons supplied with the Apache + software.
+ +
IconWidth[=pixels]
+ +
Presence of this option, when used with IconHeight, + will cause the server to include height and + width attributes in the img tag for + the file icon. This allows browser to precalculate the page + layout without having to wait until all the images have been + loaded. If no value is given for the option, it defaults to + the standard width of the icons supplied with the Apache + software.
+ +
IgnoreCase
+ +
If this option is enabled, names are sorted in a case-insensitive + manner. For instance, if the sort order is ascending by name, and + IgnoreCase is enabled, file Zeta will be listed after file alfa + (Note: file GAMMA will always be listed before file gamma).
+ +
IgnoreClient
+ +
This option causes mod_autoindex to ignore all + query variables from the client, including sort order (implies + SuppressColumnSorting.)
+ +
NameWidth=[n + | *]
+ +
The NameWidth keyword allows you to specify the width + of the filename column in bytes.
+ +
-NameWidth (or unset) allows mod_autoindex to calculate the best width.
+ +
NameWidth=n fixes the column width to + n bytes wide.
+ +
NameWidth=* grows the column to the necessary + width.
+ +
ScanHTMLTitles
+ +
This enables the extraction of the title from HTML documents + for fancy indexing. If the file does not have a description + given by AddDescription + then httpd will read the document for the value of the + title element. This is CPU and disk intensive.
+ +
ShowForbidden
+ +
If specified, Apache will show files normally hidden because + the subrequest returned HTTP_UNAUTHORIZED or HTTP_FORBIDDEN
+ +
SuppressColumnSorting
+ +
If specified, Apache will not make the column headings in a + FancyIndexed directory listing into links for sorting. The + default behavior is for them to be links; selecting the + column heading will sort the directory listing by the values + in that column. Prior to Apache 2.0.23, this also + disabled parsing the Query Arguments for the sort + string. That behavior is now controlled by IndexOptions + IgnoreClient in Apache 2.0.23.
+ +
SuppressDescription
+ +
This will suppress the file description in fancy indexing + listings. By default, no file descriptions are defined, and + so the use of this option will regain 23 characters of screen + space to use for something else. See AddDescription for information about setting the file + description. See also the DescriptionWidth + index option to limit the size of the description column.
+ +
SuppressHTMLPreamble
+ +
If the directory actually contains a file specified by the + HeaderName + directive, the module usually includes the contents of the file + after a standard HTML preamble (<html>, + <head>, et cetera). The + SuppressHTMLPreamble option disables this behaviour, + causing the module to start the display with the header file + contents. The header file must contain appropriate HTML instructions + in this case. If there is no header file, the preamble is generated + as usual.
+ +
SuppressIcon (Apache + 2.0.23 and later)
+ +
This will suppress the icon in fancy indexing listings. + Combining both SuppressIcon and + SuppressRules yields proper HTML 3.2 output, which + by the final specification prohibits img and + hr elements from the pre block (used to + format FancyIndexed listings.)
+ +
SuppressLastModified
+ +
This will suppress the display of the last modification date, + in fancy indexing listings.
+ +
SuppressRules + (Apache 2.0.23 and later)
+ +
This will suppress the horizontal rule lines (hr + elements) in directory listings. Combining both SuppressIcon and + SuppressRules yields proper HTML 3.2 output, which + by the final specification prohibits img and + hr elements from the pre block (used to + format FancyIndexed listings.)
+ +
SuppressSize
+ +
This will suppress the file size in fancy indexing listings.
+ +
TrackModified (Apache + 2.0.23 and later)
+ +
This returns the Last-Modified and ETag values for the listed + directory in the HTTP header. It is only valid if the + operating system and file system return appropriate stat() + results. Some Unix systems do so, as do OS2's JFS and Win32's + NTFS volumes. OS2 and Win32 FAT volumes, for example, do not. + Once this feature is enabled, the client or proxy can track + changes to the list of files when they perform a HEAD + request. Note some operating systems correctly track new and + removed files, but do not track changes for sizes or dates of + the files within the directory. Changes to the size + or date stamp of an existing file will not update the + Last-Modified header on all Unix platforms. If this + is a concern, leave this option disabled.
+ +
VersionSort + (Apache 2.0a3 and later)
+ +
The VersionSort keyword causes files containing + version numbers to sort in a natural way. Strings are sorted as + usual, except that substrings of digits in the name and + description are compared according to their numeric value. + +

Example:

+ foo-1.7
+ foo-1.7.2
+ foo-1.7.12
+ foo-1.8.2
+ foo-1.8.2a
+ foo-1.12 +

+ +

If the number starts with a zero, then it is considered to + be a fraction:

+ +

+ foo-1.001
+ foo-1.002
+ foo-1.030
+ foo-1.04 +

+
+ +
XHTML + (Apache 2.0.49 and later)
+ +
The XHTML keyword forces mod_autoindex + to emit XHTML 1.0 code instead of HTML 3.2.
+
+ + +
Incremental IndexOptions
+
+

Apache 1.3.3 introduced some significant changes in the + handling of IndexOptions directives. In + particular:

+ +
    +
  • Multiple IndexOptions directives for a + single directory are now merged together. The result of: + +

    + <Directory /foo> + + IndexOptions HTMLTable
    + IndexOptions SuppressColumnsorting +     + </Directory> +

    + +

    will be the equivalent of

    + +

    + IndexOptions HTMLTable SuppressColumnsorting +

    +
    • + +
  • The addition of the incremental syntax (i.e., prefixing + keywords with + or -).
    • +
+ +

Whenever a '+' or '-' prefixed keyword is encountered, it + is applied to the current IndexOptions + settings (which may have been inherited from an upper-level + directory). However, whenever an unprefixed keyword is processed, it + clears all inherited options and any incremental settings encountered + so far. Consider the following example:

+ +

+ IndexOptions +ScanHTMLTitles -IconsAreLinks FancyIndexing
+ IndexOptions +SuppressSize +

+ +

The net effect is equivalent to IndexOptions FancyIndexing + +SuppressSize, because the unprefixed FancyIndexing + discarded the incremental keywords before it, but allowed them to + start accumulating again afterward.

+ +

To unconditionally set the IndexOptions for + a particular directory, clearing the inherited settings, specify + keywords without any + or - prefixes.

+
+
+ +
+
top
+

IndexOrderDefault Directive

+ + + + + + + + +
Description:Sets the default ordering of the directory index
Syntax:IndexOrderDefault Ascending|Descending +Name|Date|Size|Description
Default:IndexOrderDefault Ascending Name
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

The IndexOrderDefault directive is used + in combination with the FancyIndexing index option. By default, fancyindexed + directory listings are displayed in ascending order by filename; the + IndexOrderDefault allows you to change this + initial display order.

+ +

IndexOrderDefault takes two + arguments. The first must be either Ascending or + Descending, indicating the direction of the sort. + The second argument must be one of the keywords Name, + Date, Size, or Description, + and identifies the primary key. The secondary key is + always the ascending filename.

+ +

You can force a directory listing to only be displayed in a + particular order by combining this directive with the SuppressColumnSorting index option; this will prevent + the client from requesting the directory listing in a different + order.

+ +
+
top
+

IndexStyleSheet Directive

+ + + + + + + +
Description:Adds a CSS stylesheet to the directory index
Syntax:IndexStyleSheet url-path
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

The IndexStyleSheet directive sets the name of + the file that will be used as the CSS for the index listing. +

+

Example

+ + IndexStyleSheet "/css/style.css" +

+ +
+
top
+

ReadmeName Directive

+ + + + + + + +
Description:Name of the file that will be inserted at the end +of the index listing
Syntax:ReadmeName filename
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_autoindex
+

The ReadmeName directive sets the name + of the file that will be appended to the end of the index + listing. Filename is the name of the file to include, and + is taken to be relative to the location being indexed. If + Filename begins with a slash, it will be taken to be + relative to the DocumentRoot. +

+ +

Example

+ ReadmeName FOOTER.html +

+ +

Example 2

+ ReadmeName /include/FOOTER.html +

+ +

See also HeaderName, where this behavior is described in greater + detail.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_autoindex.html.ja.euc-jp b/docs/manual/mod/mod_autoindex.html.ja.euc-jp new file mode 100644 index 00000000..d20ff04e --- /dev/null +++ b/docs/manual/mod/mod_autoindex.html.ja.euc-jp @@ -0,0 +1,985 @@ + + + +mod_autoindex - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_autoindex

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:Unix ¤Î ls ¥³¥Þ¥ó¥É¤ä + Win32 ¤Î dir ¥·¥§¥ë¥³¥Þ¥ó¥É¤Ë»÷¤¿ + ¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤òÀ¸À®¤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:autoindex_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_autoindex.c
+

³µÍ×

+ +

¥Ç¥£¥ì¥¯¥È¥ê¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤ÏÆó¤Ä¤Î¾ðÊ󸻤Τ¦¤Á¤Î + °ì¤Ä¤«¤éÀ¸À®¤Ç¤­¤Þ¤¹:

+ +
    +
  • ÉáÄÌ¤Ï index.html ¤È¸Æ¤Ð¤ì¤ë + ¥æ¡¼¥¶¤Ë¤è¤Ã¤Æ½ñ¤«¤ì¤¿¥Õ¥¡¥¤¥ë¡£ + DirectoryIndex + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤³¤Î¥Õ¥¡¥¤¥ë̾¤òÀßÄꤷ¤Þ¤¹¡£ + ¤³¤ì¤Ï mod_dir ¤ÇÀ©¸æ¤µ¤ì¤Þ¤¹¡£
    • + +
  • ¤â¤·¤¯¤Ï¡¢¥µ¡¼¥Ð¤Ë¤è¤Ã¤ÆÀ¸À®¤µ¤ì¤¿°ìÍ÷¡£ + ¤½¤Î¾¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤³¤Î°ìÍ÷¤Î½ñ¼°¤òÀ©¸æ¤·¤Þ¤¹¡£ + AddIcon, AddIconByEncoding ¤È + AddIconByType + ¤ò»È¤¦¤³¤È¤Ç¡¢ÍÍ¡¹¤Ê¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤ËÂФ·¤Æ¥¢¥¤¥³¥ó°ìÍ÷¤ò + ¥»¥Ã¥È¤·¤Þ¤¹¡£¤Ä¤Þ¤ê¡¢¥ê¥¹¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ëËè¤Ë¡¢ + ¥Õ¥¡¥¤¥ë¤Ë¥Þ¥Ã¥Á¤·¤¿°ìÈֺǽé¤Î¥¢¥¤¥³¥ó¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£ + ¤³¤ì¤é¤Ï mod_autoindex ¤ÇÀ©¸æ¤µ¤ì¤Þ¤¹¡£
    • +
+

˾¤à¤Ê¤é¤Ð¡¢¼«Æ°¥¤¥ó¥Ç¥Ã¥¯¥¹À¸À®¤ò´°Á´¤Ë½üµî (¤¢¤ë¤¤¤ÏÃÖ´¹) + ¤Ç¤­¤ë¤è¤¦¤Ë¡¢¤³¤ÎÆó¤Ä¤Îµ¡Ç½¤ÏʬΥ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

¼«Æ°¥¤¥ó¥Ç¥Ã¥¯¥¹À¸À®¤Ï Options +Indexes + ¤ò»È¤¦¤³¤È¤ÇÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¡¢ + Options + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

¤â¤· FancyIndexing¥ª¥×¥·¥ç¥ó¤¬ + IndexOptions + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ËÍ¿¤¨¤é¤ì¤Æ¤¤¤ë¤Ê¤é¤Ð¡¢ + Îó¤ÎÀèƬ¤Ïɽ¼¨¤Î½çÈÖ¤òÀ©¸æ¤¹¤ë¥ê¥ó¥¯¤Ë¤Ê¤ê¤Þ¤¹¡£ + ÀèƬ¤Î¥ê¥ó¥¯¤òÁªÂò¤¹¤ë¤È¡¢°ìÍ÷¤ÏºÆÀ¸À®¤µ¤ì¤Æ + ¤½¤ÎÎó¤ÎÃͤǥ½¡¼¥È¤µ¤ì¤Þ¤¹¡£ + Ʊ¤¸ÀèƬ¤ò³¤±¤ÆÁªÂò¤¹¤ë¤È¡¢¸ò¸ß¤Ë¾º½ç¤È¹ß½ç¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ì¤é¤ÎÎó¤ÎÀèƬ¤Î¥ê¥ó¥¯¤Ï¡¢ + IndexOptions + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + SuppressColumnSorting + ¥ª¥×¥·¥ç¥ó¤Ç¾Ã¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

"Size" ¤Ç¥½¡¼¥È¤·¤¿¾ì¹ç¤Ï¡¢ÍѤ¤¤é¤ì¤ë¤Î¤Ï + ¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë¤Î¥µ¥¤¥º¤Ç¤¢¤Ã¤Æ¡¢ + ɽ¼¨¤ÎÃͤǤϤʤ¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤ - + ¤¿¤È¤¨Î¾Êý¤È¤â¤¬ "1K" ¤Èɽ¼¨¤µ¤ì¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢ + 1010 ¥Ð¥¤¥È¤Î¥Õ¥¡¥¤¥ë¤Ïɬ¤º 1011 + ¥Ð¥¤¥È¤Î¥Õ¥¡¥¤¥ë¤è¤ê¤âÁ° (¾º½ç¤Î¾ì¹ç) ¤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£

+
+ +
top
+
+

Autoindex ¥ê¥¯¥¨¥¹¥È¥¯¥¨¥ê¡¼°ú¿ô

+ + +

Apache 2.0.23 ¤Ç¡¢ + ¥³¥é¥à¥½¡¼¥È¤Î¤¿¤á¤Ë¥¯¥¨¥ê¡¼°ú¿ô¤òºÆÊÔÀ®¤·¤Æ¡¢ + ¿·¤·¤¤¥¯¥¨¥ê¡¼¥ª¥×¥·¥ç¥ó¤Î¥°¥ë¡¼¥×¤òƳÆþ¤·¤Þ¤·¤¿¡£ + ½ÐÎϤËÂФ¹¤ë¥¯¥é¥¤¥¢¥ó¥È¤Î¤¹¤Ù¤Æ¤ÎÀ©¸æ¤ò¸úΨŪ¤ËËõ¾Ã + ¤Ç¤­¤ë¤è¤¦¤Ë¡¢ + IndexOptions + IgnoreClient ¤¬Æ³Æþ¤µ¤ì¤Þ¤·¤¿¡£

+ +

¥³¥é¥à¥½¡¼¥È¤Î¥Ø¥Ã¥À¤½¤ì¼«ÂΤ¬¡¢ + ²¼µ­¤Î¥½¡¼¥È¥¯¥¨¥ê¡¼¥ª¥×¥·¥ç¥ó¤òÉղ乤ë + ¼«Ê¬¼«¿È¤ò»²¾È¤¹¤ë¥ê¥ó¥¯¤Ç¤¹¡£ + ²¼µ­¤Î¥ª¥×¥·¥ç¥ó¤Î¤É¤ì¤Ç¤â¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê¥ê¥½¡¼¥¹¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ë²Ã¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +
    +
  • C=N ¤Ï¡¢¥Õ¥¡¥¤¥ë̾¤Ç¥½¡¼¥È¤·¤Þ¤¹¡£
    • + +
  • C=M ¤Ï¡¢¹¹¿·Æü»þ¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê¡¢¥Õ¥¡¥¤¥ë̾¤Î½ç¤Ç¥½¡¼¥È¤·¤Þ¤¹¡£
    • + +
  • C=S ¤Ï¡¢¥µ¥¤¥º¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê¡¢¥Õ¥¡¥¤¥ë̾¤Î½ç¤Ç¥½¡¼¥È¤·¤Þ¤¹¡£
    • + +
  • C=D ¤Ï¡¢ÀâÌÀ¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê¡¢¥Õ¥¡¥¤¥ë̾¤Î½ç¤Ç¥½¡¼¥È¤·¤Þ¤¹¡£
    • + +
  • O=A ¤Ï¡¢¾º½ç¤Çɽ¤ò¥½¡¼¥È¤·¤Þ¤¹¡£
    • + +
  • O=D ¤Ï¡¢¹ß½ç¤Çɽ¤ò¥½¡¼¥È¤·¤Þ¤¹¡£
    • + +
  • F=0 ¤Ï¡¢Ã±½ã¤Êɽ¤Î½ñ¼°¤Ë¤·¤Þ¤¹¡£ + (FancyIndex ¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£)
    • + +
  • F=1 ¤Ï¡¢FancyIndex + ɽ¼¨¤Îɽ¤Î½ñ¼°¤Ë¤·¤Þ¤¹¡£
    • + +
  • F=2 ¤Ï¡¢É½¤ò HTML + ¤Î¥Æ¡¼¥Ö¥ë¤ò»È¤Ã¤¿ FancyIndex ¤Î½ñ¼°¤Ë¤·¤Þ¤¹¡£
    • + +
  • V=0 + ¤Ï¡¢¥Ð¡¼¥¸¥ç¥ó¤Ë¤è¤ë¥½¡¼¥È¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£
    • + +
  • V=1 + ¤Ï¡¢¥Ð¡¼¥¸¥ç¥ó¤Ë¤è¤ë¥½¡¼¥È¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£
    • + +
  • P=pattern + ¤Ï¡¢Í¿¤¨¤é¤ì¤¿ pattern + ¤ËŬ¹ç¤·¤¿¥Õ¥¡¥¤¥ë¤Î¤ß¤òɽ¼¨¤·¤Þ¤¹¡£
    • +
+ +

"P (¥Ñ¥¿¡¼¥ó¤Î P)" ¥¯¥¨¥ê¡¼°ú¿ô¤Ï¡¢ + Ä̾ï¤Î IndexIgnore + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬½èÍý¤µ¤ì¤¿¸å¤Ë¸¡ºº¤µ¤ì¡¢ + ¥Õ¥¡¥¤¥ë̾Á´¤Æ¤¬¡¢Â¾¤Î autoindex + ¥ê¥¹¥È½èÍý¤ÈƱÍͤÎȽÄê´ð½à²¼¤ËÃÖ¤«¤ì³¤±¤ë + ¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + mod_autoindex ¤Î¥¯¥¨¥ê¡¼°ú¿ô¥Ñ¡¼¥µ (²òÀÏ) ¤Ï¡¢ + ǧ¼±ÉÔǽ¤Ê¥ª¥×¥·¥ç¥ó¤Ë¤Ö¤Ä¤«¤ë¤È¨ºÂ¤ËÄä»ß¤·¤Þ¤¹¡£ + ¥¯¥¨¥ê¡¼°ú¿ô¤Ï¾å¤Îɽ¤Ë½¾¤Ã¤Æ + Àµ¤·¤¤·Á¼°¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

²¼¤Îñ½ã¤ÊÎã¤Ï¡¢¤³¤ì¤é¤Î¥¯¥¨¥ê¡¼¥ª¥×¥·¥ç¥ó¤ò + ɽ¤·¤Þ¤¹¡£¤³¤ì¤ò¤½¤Î¤Þ¤ÞÀÚ¤ê¼è¤Ã¤Æ HEADER.html + ¥Õ¥¡¥¤¥ë¤ËÊݸ¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + mod_autoindex ¤¬ X=Go ÆþÎϤˤ֤Ĥ«¤ëÁ°¤Ë + °ú¿ô¤¬Á´¤Æ²ò¼á¤µ¤ì¤ë¤è¤¦¤Ë¡¢ + ̤ÃΤΰú¿ô "X" ¤Ï¥ê¥¹¥È¤ÎºÇ¸å¤ËÃÖ¤«¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

+ <form action="" method="get">
+ + Show me a <select name="F">
+ + <option value="0"> Plain list</option>
+ <option value="1" selected="selected"> Fancy list</option>
+ <option value="2"> Table list</option>
+ + </select>
+ Sorted by <select name="C">
+ + <option value="N" selected="selected"> Name</option>
+ <option value="M"> Date Modified</option>
+ <option value="S"> Size</option>
+ <option value="D"> Description</option>
+ + </select>
+ <select name="O">
+ + <option value="A" selected="selected"> Ascending</option>
+ <option value="D"> Descending</option>
+ + </select>
+ <select name="V">
+ + <option value="0" selected="selected"> in Normal order</option>
+ <option value="1"> in Version order</option>
+ + </select>
+ Matching <input type="text" name="P" value="*" />
+ <input type="submit" name="X" value="Go" />
+ + </form> +

+ +
+
top
+

AddAlt ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ë +ɽ¼¨¤µ¤ì¤ë¡¢¥Õ¥¡¥¤¥ë̾¤ÇÁªÂò¤µ¤ì¤¿ÂåÂإƥ­¥¹¥È
¹½Ê¸:AddAlt string file [file] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

AddAlt ¤Ï¡¢FancyIndexing + ¤Ë¤ª¤¤¤Æ¡¢¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ëɽ¼¨¤¹¤ëÂåÂإƥ­¥¹¥È¤òÄ󶡤·¤Þ¤¹¡£ + file ¤Ï¡¢ÀâÌÀ¤¹¤ë¥Õ¥¡¥¤¥ë¤Î¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¡¢ + ¥Õ¥¡¥¤¥ë̾¤Î°ìÉô¡¢¥ï¥¤¥ë¥É¥«¡¼¥Éɽ¸½¡¢´°Á´¤Ê¥Õ¥¡¥¤¥ë̾¤Î + ¤É¤ì¤«¤Ë¤Ê¤ê¤Þ¤¹¡£ + string ¤Ë¶õÇò¤¬¤¢¤ë¾ì¹ç¤Ï°úÍÑÉä (" + ¤« ') ¤Ç°Ï¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Îʸ»úÎó¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬²èÁü¤òɽ¼¨¤Ç¤­¤Ê¤¤¾ì¹ç¤ä + ²èÁü¤Î¥í¡¼¥É¤ò̵¸ú¤Ë¤·¤Æ¤¤¤ë¾ì¹ç¤ä + ¥¢¥¤¥³¥ó¤Î¼èÆÀ¤Ë¼ºÇÔ¤·¤¿¤È¤­¤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ AddAlt "PDF file" *.pdf
+ AddAlt Compressed *.gz *.zip *.Z +

+ +
+
top
+

AddAltByEncoding ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ëɽ¼¨¤µ¤ì¤ë¡¢MIME Éä¹æ²½ÊýË¡¤ÇÁªÂò¤µ¤ì¤¿ +ÂåÂإƥ­¥¹¥È
¹½Ê¸:AddAltByEncoding string MIME-encoding +[MIME-encoding] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

AddAltByEncoding ¤Ï¡¢ + FancyIndexing + ¤Ë¤ª¤¤¤Æ¡¢¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ëɽ¼¨¤¹¤ëÂåÂØʸ»úÎó¤òÄ󶡤·¤Þ¤¹¡£ + MIME-encoding ¤ÏÍ­¸ú¤ÊÉä¹æ²½¡¢Î㤨¤Ð + x-compress + ¤Ç¤¹¡£ + string ¤Ë¶õÇò¤¬¤¢¤ë¤È¤­¤Ï¡¢°úÍÑÉä (" ¤« + ') ¤Ç°Ï¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Îʸ»úÎó¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬²èÁü¤òɽ¼¨¤Ç¤­¤Ê¤¤¾ì¹ç¤ä + ²èÁü¤Î¥í¡¼¥É¤ò̵¸ú¤Ë¤·¤Æ¤¤¤ë¾ì¹ç¤ä + ¥¢¥¤¥³¥ó¤Î¼èÆÀ¤Ë¼ºÇÔ¤·¤¿¤È¤­¤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ AddAltByEncoding gzip x-gzip +

+ +
+
top
+

AddAltByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ë +ɽ¼¨¤µ¤ì¤ë¡¢MIME ¥¿¥¤¥×¤ÇÁªÂò¤µ¤ì¤¿ÂåÂإƥ­¥¹¥È
¹½Ê¸:AddAltByType string MIME-type +[MIME-type] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

AddAltByType ¤Ï¡¢ + FancyIndexing + ¤Ë¤ª¤¤¤Æ¡¢¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ëɽ¼¨¤¹¤ëÂåÂØʸ»úÎó¤òÀßÄꤷ¤Þ¤¹¡£ + MIME-type ¤ÏÍ­¸ú¤Ê¥¿¥¤¥×¡¢Î㤨¤Ð + text/html + ¤Ç¤¹¡£ + string ¤Ë¶õÇò¤¬¤¢¤ë¤È¤­¤Ï¡¢°úÍÑÉä (" ¤« + ') ¤Ç°Ï¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Îʸ»úÎó¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬²èÁü¤òɽ¼¨¤Ç¤­¤Ê¤¤¾ì¹ç¤ä + ²èÁü¤Î¥í¡¼¥É¤ò̵¸ú¤Ë¤·¤Æ¤¤¤ë¾ì¹ç¤ä + ¥¢¥¤¥³¥ó¤Î¼èÆÀ¤Ë¼ºÇÔ¤·¤¿¤È¤­¤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ AddAltByType 'plain text' text/plain +

+ +
+
top
+

AddDescription ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æɽ¼¨¤¹¤ëÀâÌÀ
¹½Ê¸:AddDescription string file [file] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

FancyIndexing + ¤Ë¤ª¤¤¤Æ¡¢¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æɽ¼¨¤¹¤ëÀâÌÀ¤òÀßÄꤷ¤Þ¤¹¡£ + file ¤ÏÀâÌÀ¤¹¤ë¥Õ¥¡¥¤¥ë¤Î¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¡¢ + ¥Õ¥¡¥¤¥ë̾¤Î°ìÉô¡¢¥ï¥¤¥ë¥É¥«¡¼¥Éɽ¸½¡¢´°Á´¤Ê¥Õ¥¡¥¤¥ë̾¤Î + ¤É¤ì¤«¤Ë¤Ê¤ê¤Þ¤¹¡£ + string ¤ÏÆó½Å°úÍÑÉä (") ¤Ç°Ï¤Þ¤ì¤Þ¤¹¡£

+ +

Îã

+ AddDescription "The planet Mars" /web/pics/mars.gif +

+ +

Ä̾ï¤Î¥Ç¥Õ¥©¥ë¥È¤ÎÀâÌÀÎΰè¤Ï 23 ¥Ð¥¤¥È¤ÎÉý¤Ç¤¹¡£ + IndexOptions SuppressIcon + ¥ª¥×¥·¥ç¥ó¤Ç 6 ¥Ð¥¤¥ÈÄɲᢠ+ IndexOptions SuppressSize + ¥ª¥×¥·¥ç¥ó¤Ç 7 ¥Ð¥¤¥ÈÄɲᢠ+ IndexOptions SuppressLastModified + ¥ª¥×¥·¥ç¥ó¤Ç 19 ¥Ð¥¤¥ÈÄɲ䵤ì¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢¥Ç¥Õ¥©¥ë¥È¤ÎÀâÌÀ¥³¥é¥à¤ÎºÇÂçÉý¤Ï + 55 ¥Ð¥¤¥È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¤³¤Î¥³¥é¥à¤ÎÂ礭¤µ¤ò¾å½ñ¤­¤·¤¿¤ê¡¢ + ÀâÌÀ¤¬ÌµÀ©¸ÂŤǤâ¤è¤¤¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Î¾ÜºÙ¤Ë´Ø¤·¤Æ¤Ï¡¢ + DescriptionWidth + ¤È¤¤¤¦ + IndexOptions + ¤Î¥­¡¼¥ï¡¼¥É¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

·Ù¹ð

+

AddDescription + ¤ÇÄêµÁ¤µ¤ì¤¿ÀâÌÀ¥Æ¥­¥¹¥È¤Ï¡¢¥¿¥°¤äʸ»úÎó¤È¤¤¤Ã¤¿ + HTML ¥Þ¡¼¥¯¥¢¥Ã¥×¤ò´Þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤â¤·¡¢ÀâÌÀ¥³¥é¥à¤ÎÉý¤Ë¤è¤Ã¤Æ¥¿¥°ÉÕ¤±¤µ¤ì¤¿Í×ÁǤ¬´Ý¤á¹þ¤Þ¤ì¤¿ + (ÂÀ»ú¤Î¸ì¶ç¤ÎºÇ¸å¤¬ÀÚ¤ì¤ë¤È¤¤¤Ã¤¿) ¾ì¹ç¡¢ + ½ÐÎÏ·ë²Ì¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤Î»Ä¤ê¤ÎÉôʬ¤Ë±Æ¶Á¤òÍ¿¤¨¤ë¤Ç¤·¤ç¤¦¡£

+
+ +
+
top
+

AddIcon ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤ò̾Á°¤ÇÁªÂò
¹½Ê¸:AddIcon icon name +[name] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

FancyIndexing + ¤Ë¤ª¤¤¤Æ¡¢ + name ¤Ç½ª¤ï¤ë¥Õ¥¡¥¤¥ë¤ÎÎÙ¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤òÀßÄꤷ¤Þ¤¹¡£ + icon ¤Ï¡¢(% ¤Ç¥¨¥¹¥±¡¼¥×¤µ¤ì¤¿) ¥¢¥¤¥³¥ó¤Ø¤ÎÁêÂÐ URL + ¤«¡¢Â¾¤Î½ñ¼° (alttext, url) ¤Ç¤¹¡£ + ¤³¤³¤Ç alttext + ¤Ï¡¢Èó¥°¥é¥Õ¥£¥«¥ë¥Ö¥é¥¦¥¶¸þ¤±¤Ë¥¢¥¤¥³¥ó¤ËÉÕ¤±¤é¤ì¤¿¥Æ¥­¥¹¥È¥¿¥°¤Ç¤¹¡£ +

+ +

name ¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥ê¤ËÂбþ¤¹¤ë ^^DIRECTORY^^ + ¤«¡¢¶õÇò¹Ô¤ËÂбþ¤¹¤ë ^^BLANKICON^^ (°ìÍ÷¤¬Àµ¤·¤¯É½¼¨¤µ¤ì¤ë¤¿¤á¤Ë) ¤«¡¢ + ¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤«¡¢¥ï¥¤¥ë¥É¥«¡¼¥Éɽ¸½¤«¡¢¥Õ¥¡¥¤¥ë̾¤Î°ìÉô¤« + ´°Á´¤Ê¥Õ¥¡¥¤¥ë̾¤Ç¤¹¡£

+ +

Îã

+ AddIcon (IMG,/icons/image.xbm) .gif .jpg .xbm
+ AddIcon /icons/dir.xbm ^^DIRECTORY^^
+ AddIcon /icons/backup.xbm *~ +

+ +

¤â¤·²Äǽ¤Ê¤é¡¢ + AddIcon + ¤è¤ê + AddIconByType + ¤òÍ¥ÀèŪ¤Ë»È¤¦¤Ù¤­¤Ç¤·¤ç¤¦¡£

+ +
+
top
+

AddIconByEncoding ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤ò MIME +Éä¹æ²½ÊýË¡¤ÇÁªÂò
¹½Ê¸:AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

FancyIndexing + ¤Ë¤ª¤¤¤Æ¡¢¥Õ¥¡¥¤¥ë¤ÎÎÙ¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤òÀßÄꤷ¤Þ¤¹¡£ + icon ¤Ï¡¢(% ¤Ç¥¨¥¹¥±¡¼¥×¤µ¤ì¤¿) ¥¢¥¤¥³¥ó¤Ø¤ÎÁêÂÐ URL + ¤«¡¢Â¾¤Î½ñ¼° (alttext, url) ¤Ç¤¹¡£ + ¤³¤³¤Ç alttext + ¤Ï¡¢Èó¥°¥é¥Õ¥£¥«¥ë¥Ö¥é¥¦¥¶¸þ¤±¤Ë¥¢¥¤¥³¥ó¤ËÉÕ¤±¤é¤ì¤¿¥Æ¥­¥¹¥È¥¿¥°¤Ç¤¹¡£ +

+ +

MIME-encoding ¤Ï¡¢Í׵ᤵ¤ì¤¿¥¨¥ó¥³¡¼¥É¤Ë³ºÅö¤¹¤ë + ¥ï¥¤¥ë¥É¥«¡¼¥Éɽ¸½¤Ç¤¹¡£

+ +

Îã

+ AddIconByEncoding /icons/compress.xbm x-compress +

+ +
+
top
+

AddIconByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤ÎÎÙ¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤ò +MIME ¥¿¥¤¥×¤Ë¤è¤Ã¤ÆÁªÂò
¹½Ê¸:AddIconByType icon MIME-type +[MIME-type] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

FancyIndexing + ¤Ë¤ª¤¤¤Æ¡¢¥Õ¥¡¥¤¥ë¤ÎÎÙ¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤òÀßÄꤷ¤Þ¤¹¡£ + icon ¤Ï¡¢(% ¤Ç¥¨¥¹¥±¡¼¥×¤µ¤ì¤¿) ¥¢¥¤¥³¥ó¤Ø¤ÎÁêÂÐ URL + ¤«¡¢Â¾¤Î½ñ¼° (alttext, url) ¤Ç¤¹¡£ + ¤³¤³¤Ç alttext + ¤Ï¡¢Èó¥°¥é¥Õ¥£¥«¥ë¥Ö¥é¥¦¥¶¸þ¤±¤Ë¥¢¥¤¥³¥ó¤ËÉÕ¤±¤é¤ì¤¿¥Æ¥­¥¹¥È¥¿¥°¤Ç¤¹¡£ +

+ +

MIME-type ¤Ï¡¢Í׵ᤵ¤ì¤¿¥¿¥¤¥×¤Ë³ºÅö¤¹¤ë + ¥ï¥¤¥ë¥É¥«¡¼¥Éɽ¸½¤Ç¤¹¡£

+ +

Îã

+ AddIconByType (IMG,/icons/image.xbm) image/* +

+ +
+
top
+

DefaultIcon ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:ÆÃÄê¤Î¥¢¥¤¥³¥ó¤¬²¿¤âÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤»þ¤Ë +¥Õ¥¡¥¤¥ë¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó
¹½Ê¸:DefaultIcon url-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

FancyIndexing + ¤Ë¤ª¤¤¤Æ¡¢ + ÆÃÄê¤Î¥¢¥¤¥³¥ó¤¬¤Ê¤¤¾ì¹ç¤Ë¥Õ¥¡¥¤¥ë¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤òÀßÄꤷ¤Þ¤¹¡£ + url-path ¤Ï¡¢(% ¤Ç¥¨¥¹¥±¡¼¥×¤µ¤ì¤¿) ¥¢¥¤¥³¥ó¤Ø¤ÎÁêÂÐ URL + ¤Ç¤¹¡£

+ +

Îã

+ DefaultIcon /icon/unknown.xbm +

+ +
+
top
+

HeaderName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ: +¥¤¥ó¥Ç¥Ã¥¯¥¹°ìÍ÷¤ÎÀèƬ¤ËÁÞÆþ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°
¹½Ê¸:HeaderName filename
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

HeaderName + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥¤¥ó¥Ç¥Ã¥¯¥¹°ìÍ÷¤ÎÀèƬ¤ËÁÞÆþ¤¹¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤷ¤Þ¤¹¡£ + Filename ¤Ï¼è¤ê¹þ¤à¥Õ¥¡¥¤¥ë¤Î̾Á°¤Ç¤¹¡£

+ +

Îã

+ HeaderName HEADER.html +

+ +
+

HeaderName ¤â ReadmeName + ¤âξÊý¤È¤â¸½ºß¤Ï¡¢filename + ¤ò¥¤¥ó¥Ç¥Ã¥¯¥¹¤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ËÍѤ¤¤é¤ì¤¿ URI + ¤ËÂФ¹¤ëÁêÂÐ URI ¥Ñ¥¹¤È¤·¤Æ°·¤¤¤Þ¤¹¡£ + filename ¤¬¥¹¥é¥Ã¥·¥å¤Ç»Ï¤Þ¤ë¾ì¹ç¤Ï¡¢ + DocumentRoot + ¤«¤é¤ÎÁêÂХѥ¹¤È¤Ê¤ê¤Þ¤¹¡£

+ +

Îã

+ HeaderName /include/HEADER.html +

+ +

filename ¤Ï + ¥á¥¸¥ã¡¼¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤¬ "text/*" + (Î㤨¤Ð¡¢text/html, + text/plain Åù¤Ç¤¹¡£) + ¤Î¥É¥­¥å¥á¥ó¥È¤È¤·¤Æ²ò·è + ¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤³¤ì¤Ï¤Ä¤Þ¤ê¡¢ + ¤â¤· CGI ¥¹¥¯¥ê¥×¥È¤Î¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤¬ + ¼¡¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¤è¤¦¤Ë¤·¤Æ¼ÂºÝ¤Î½ÐÎÏ¤È¤Ï°Û¤Ê¤Ã¤Æ + text/html ¤È¤·¤Æ¥Þ¡¼¥¯¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢ + filename + ¤Ï CGI ¥¹¥¯¥ê¥×¥È¤ò»²¾È¤¹¤ë¤«¤âÃΤì¤Ê¤¤¡¢ + ¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹:

+ +

+ AddType text/html .cgi +

+ +

Options MultiViews ¤¬ + Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó + ¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£ + ¤â¤· filename ¤¬ (CGI ¥¹¥¯¥ê¥×¥È¤Ç¤Ê¤¤) ÀÅŪ¤Ê + text/html ¥É¥­¥å¥á¥ó¥È¤Ç²ò·è¤µ¤ì¡¢ + options + Includes ¤« IncludesNOEXEC + ¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥Õ¥¡¥¤¥ë¤Ï¥µ¡¼¥Ð¡¼¥µ¥¤¥É¥¤¥ó¥¯¥ë¡¼¥É¤Ç½èÍý¤µ¤ì¤Þ¤¹ + (mod_include ¥É¥­¥å¥á¥ó¥È¤ò»²¾È¤·¤Æ²¼¤µ¤¤)¡£

+
+ +

¤â¤· HeaderName ¤Ç»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤¬ + HTML ¥É¥­¥å¥á¥ó¥È¤Î³«»ÏÉôʬ (<html>, <head>, + Åù) ¤ò´Þ¤ó¤Ç¤¤¤¿¤é¡¢ + IndexOptions + +SuppressHTMLPreamble + ¤òÀßÄꤷ¤Æ¡¢¤³¤ì¤é¤Î¥¿¥°¤¬·«¤êÊÖ¤µ¤ì¤Ê¤¤¤è¤¦¤Ë¤·¤¿¤¤¤È»×¤¦¤Ç¤·¤ç¤¦¡£

+ +
+
top
+

IndexIgnore ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤ò¹Ô¤Ê¤¦ºÝ¤Ë̵»ë¤¹¤Ù¤­ +¥Õ¥¡¥¤¥ë¥ê¥¹¥È¤ËÄɲÃ
¹½Ê¸:IndexIgnore file [file] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

IndexIgnore ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê¤Î°ìÍ÷¤ò¹Ô¤¦ºÝ¤Ë̵»ë¤¹¤Ù¤­¥Õ¥¡¥¤¥ë¥ê¥¹¥È¤ËÄɲä·¤Þ¤¹¡£ + file ¤Ï¡¢ + ¥·¥§¥ë·Á¼°¤Î¥ï¥¤¥ë¥É¥«¡¼¥Éɽ¸½¤«´°Á´¤Ê¥Õ¥¡¥¤¥ë̾¤Ç¤¹¡£ + IndexIgnore ¤¬Ê£¿ô¤¢¤ë¾ì¹ç¤Ï¡¢Ìµ»ë¤¹¤ë¥ê¥¹¥È¤ËÄɲ䬹Ԥï¤ì¡¢ + ÃÖ´¹¤Ï¹Ô¤ï¤ì¤Þ¤»¤ó¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥ê¥¹¥È¤Ë¤Ï . + (¥«¥ì¥ó¥È¥Ç¥£¥ì¥¯¥È¥ê) ¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

+ IndexIgnore README .htaccess *.bak *~ +

+ +
+
top
+

IndexOptions ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤ÎÍÍ¡¹¤ÊÀßÄê¹àÌÜ +
¹½Ê¸:IndexOptions [+|-]option [[+|-]option] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

IndexOptions + ¤Ï¡¢¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤ÎµóÆ°¤ò»ØÄꤷ¤Þ¤¹¡£ + option ¤Ï¼¡¤Î¤É¤ì¤«¤Ç¤¹:

+ +
+
DescriptionWidth=[n | *] + (2.0.23 °Ê¹ß)
+ +
DescriptionWidth + ¥­¡¼¥ï¡¼¥É¤ÏÀâÌÀ¥³¥é¥à¤ÎÉý¤òʸ»ú¿ô¤Ç»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
+ +
-DescriptionWidth (¤Þ¤¿¤ÏÈóÀßÄê) ¤Ç¡¢ + mod_autoindex ¤¬ºÇŬ¤ÊÉý¤ò·×»»¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£
+ +
DescriptionWidth=n + ¤Ç¡¢¥³¥é¥àÉý¤ò n ¥Ð¥¤¥È¤Ë¸ÇÄꤷ¤Þ¤¹¡£
+ +
DescriptionWidth=* + ¤Ï¡¢ºÇŤÎÀâÌÀ¤Ë¹ç¤ï¤»¤ÆɬÍפÊŤµ¤Þ¤Ç¥³¥é¥à¤ò±ä¤Ð¤·¤Þ¤¹¡£
+ +
ÀâÌÀ¤ò´Ý¤á¹þ¤ó¤À¾ì¹çÆÃÍ­¤Î´í¸±¤Ë¤Ä¤¤¤Æ¤Ï + AddDescription + ¥»¥¯¥·¥ç¥ó¤ò¤ªÆɤ߲¼¤µ¤¤¡£
+ +
FancyIndexing
+ +
¾þ¤êÉÕ¤­¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò¥ª¥ó¤Ë¤·¤Þ¤¹¡£
+ +
FoldersFirst + (2.0.23 °Ê¹ß)
+ +
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤Ë¤Ê¤Ã¤¿¾ì¹ç¡¢¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Î°ìÍ÷¤Ï + ɬ¤ººÇ½é¤Ë¸½¤ï¤ì¤Æ¡¢¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ÎÄ̾ï¤Î¥Õ¥¡¥¤¥ë¤Ï + ¤½¤Î¸å¤Ë³¤­¤Þ¤¹¡£ + °ìÍ÷¤Ï´ðËÜŪ¤Ë¤Ï¡¢¥Õ¥¡¥¤¥ë¤È¥Ç¥£¥ì¥¯¥È¥ê¤ÎÆó¤Ä¤ÎÉôʬ¤Ëʬ¤±¤é¤ì¤Æ¡¢ + ¤½¤ì¤¾¤ì¤ÏÊÌ¡¹¤Ë¥½¡¼¥È¤µ¤ì¡¢¤½¤Î¸å¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤òÀè¤Ë¤·¤Æ + ɽ¼¨¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£Î㤨¤Ð¥½¡¼¥È½ç¤¬Ì¾Á°¤Î¹ß½ç¤Ë¤Ê¤Ã¤Æ¤¤¤Æ¡¢ + FoldersFirst ¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê Zed ¤Ï¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê + Beta ¤è¤ê¤âÁ°¤Ë¥ê¥¹¥È¤µ¤ì¡¢Ä̾ï¤Î¥Õ¥¡¥¤¥ë + Gamma ¤ä Alpha + ¤è¤ê¤âÁ°¤Ë¥ê¥¹¥È¤µ¤ì¤Þ¤¹¡£¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï + FancyIndexing + ¤âÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤È¤­¤Ë¤Î¤ß¡¢¸ú²Ì¤¬¤¢¤ê¤Þ¤¹¡£
+ +
HTMLTable (¼Â¸³Åª¡¢ + Apache 2.0.23 °Ê¹ß)
+ +
¤³¤Î¼Â¸³Åª¤Ê¥ª¥×¥·¥ç¥ó¤Ï FancyIndexing ¤È¤È¤â¤Ë»ØÄꤹ¤ë¤³¤È¤Ç¡¢ + ¾þ¤ê¤ÎÉÕ¤¤¤¿¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤Î¤¿¤á¤Ë¥Æ¡¼¥Ö¥ë¤ò»È¤Ã¤¿Ã±½ã¤Êɽ¤òºî¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï¸Å¤¤¥Ö¥é¥¦¥¶¤òº®Í𤵤»¤ë¤«¤â¤·¤ì¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + WinNT ¤ä¤½¤Î¾ utf-8 + ¤¬Í­¸ú¤Ê¥×¥é¥Ã¥È¥Û¡¼¥à¤Î¤è¤¦¤Ë¡¢¥Õ¥¡¥¤¥ë̾¤äÀâÌÀ¥Æ¥­¥¹¥È¤¬ + ±¦Æɤߤˤʤ俤꺸Æɤߤˤʤꤨ¤ë¾ì¹ç¤ÏÆäËɬÍפǤ¹¡£
+ +
IconsAreLinks
+ +
¤³¤ì¤Ï¡¢FancyIndexing ¤Ë¤ª¤¤¤Æ¡¢ + ¥¢¥¤¥³¥ó¤â¥Õ¥¡¥¤¥ë̾¤Ø¤Î¥ê¥ó¥¯¤Î°ìÉô¤Ë¤·¤Þ¤¹¡£
+ +
IconHeight[=pixels]
+ +
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬¡¢IconWidth ¤È¤È¤â¤Ë»È¤ï¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥µ¡¼¥Ð¤Ï¥Õ¥¡¥¤¥ë¥¢¥¤¥³¥ó¤Î¤¿¤á¤Î img + ¥¿¥°¤Ë height ¤È width + °À­¤ò¼è¤ê¹þ¤à¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤Ã¤Æ¡¢¥¤¥á¡¼¥¸Á´¤Æ¤ò¥í¡¼¥É¤·½ª¤ï¤ë¤Þ¤ÇÂÔ¤¿¤Ê¤¯¤Æ¤â¡¢ + ¥Ö¥é¥¦¥¶¤Ï¥Ú¡¼¥¸¥ì¥¤¥¢¥¦¥È¤ò¤¢¤é¤«¤¸¤á·×»»¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ë²¿¤âÃͤ¬Í¿¤¨¤é¤ì¤Ê¤±¤ì¤Ð¡¢Apache + ¥½¥Õ¥È¥¦¥§¥¢¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë¥¢¥¤¥³¥ó¤Îɸ½à¤Î¹â¤µ¤¬ + ¥Ç¥Õ¥©¥ë¥È¤Ê¤ê¤Þ¤¹¡£
+ +
IconWidth[=pixels]
+ +
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬¡¢IconHeight ¤È¤È¤â¤Ë»È¤ï¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥µ¡¼¥Ð¤Ï¥Õ¥¡¥¤¥ë¥¢¥¤¥³¥ó¤Î¤¿¤á¤Î img + ¥¿¥°¤Ë height ¤È width + °À­¤ò¼è¤ê¹þ¤à¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤Ã¤Æ¡¢¥¤¥á¡¼¥¸Á´¤Æ¤ò¥í¡¼¥É¤·½ª¤ï¤ë¤Þ¤ÇÂÔ¤¿¤Ê¤¯¤Æ¤â¡¢ + ¥Ö¥é¥¦¥¶¤Ï¥Ú¡¼¥¸¥ì¥¤¥¢¥¦¥È¤ò¤¢¤é¤«¤¸¤á·×»»¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ë²¿¤âÃͤ¬Í¿¤¨¤é¤ì¤Ê¤±¤ì¤Ð¡¢Apache + ¥½¥Õ¥È¥¦¥§¥¢¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë¥¢¥¤¥³¥ó¤Îɸ½à¤Î¹â¤µ¤¬ + ¥Ç¥Õ¥©¥ë¥È¤Ê¤ê¤Þ¤¹¡£
+ +
IgnoreCase
+ +
¤³¤Î¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤Ç¤¢¤ë¤È¡¢¥Õ¥¡¥¤¥ë̾¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¤Ë¥½¡¼¥È¤µ¤ì¤Þ¤¹¡£ + Î㤨¤Ð¥Õ¥¡¥¤¥ë̾¤¬¾º½ç¤Ç¥½¡¼¥È¤µ¤ì¡¢IgnoreCase ¤¬Í­¸ú¤Ç¤¢¤ì¤Ð¡¢ + Zeta ¤Ï alfa ¤Î¸å¤Ë¥ê¥¹¥È¤µ¤ì¤Þ¤¹ + (Ãí°Õ: GAMMA ¤Ï¾ï¤Ë gamma ¤ÎÁ°¤Ë¤Ê¤ê¤Þ¤¹)¡£
+ +
IgnoreClient
+ +
¤³¤Î¥ª¥×¥·¥ç¥ó¤Ç mod_autoindex ¤Ï¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤ÎÁ´¤Æ¤Î¥¯¥¨¥ê¡¼ÊÑ¿ô¤ò̵»ë¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï¥½¡¼¥È½ç¤â´Þ¤ß¤Þ¤¹¡£ + (¤Ä¤Þ¤ê SuppressColumnSorting + ¤ò°Å¤Ë°ÕÌ£¤·¤Þ¤¹¡£)
+ +
NameWidth=[n + | *]
+ +
NameWidth ¥­¡¼¥ï¡¼¥É¤Ç¥Õ¥¡¥¤¥ë̾¥³¥é¥à¤ÎÉý¤ò¥Ð¥¤¥È¿ô¤Ç + »ØÄê¤Ç¤­¤Þ¤¹¡£
+ +
-NameWidth (¤Þ¤¿¤ÏÈóÀßÄê) ¤Ç¡¢ + mod_autoindex ¤¬ºÇŬ¤ÊÉý¤ò·×»»¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£
+ +
NameWidth=n + ¤Ç¡¢¥³¥é¥àÉý¤ò n ¥Ð¥¤¥È¤Ë¸ÇÄꤷ¤Þ¤¹¡£
+ +
NameWidth=* + ¤Ï¡¢É¬ÍפÊŤµ¤Þ¤Ç¥³¥é¥à¤ò±ä¤Ð¤·¤Þ¤¹¡£
+ +
ScanHTMLTitles
+ +
FancyIndexing ¤Î¤¿¤á¤Ë¡¢ + HTML ¥É¥­¥å¥á¥ó¥È¤«¤é¥¿¥¤¥È¥ë¤ò¼è¤ê½Ð¤¹¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£ + ¤â¤·¥Õ¥¡¥¤¥ë¤Ë + AddDescription + ¤ÇÀâÌÀ¤¬Í¿¤¨¤é¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢ + httpd ¤Ï title ¥¿¥°¤ÎÃͤòÆɤि¤á¤Ë¥É¥­¥å¥á¥ó¥È¤òÆɤ߻Ϥá¤Þ¤¹¡£ + ¤³¤ì¤Ï CPU ¤ä disk ¤ËÉé²Ù¤ò¤«¤±¤Þ¤¹¡£
+ +
ShowForbidden
+ +
»ØÄꤷ¤¿¾ì¹ç¤Ç¤¢¤Ã¤Æ¤â¡¢¥µ¥Ö¥ê¥¯¥¨¥¹¥È¤Î·ë²Ì¤¬ HTTP_UNAUTHORIZED ¤ä + HTTP_FORBIDDEN ¤Î¥Õ¥¡¥¤¥ë¤ÏÄ̾ïÄ̤걣¤µ¤ì¤¿¾õÂ֤Τޤޡ¢ + ¥Õ¥¡¥¤¥ë°ìÍ÷¤¬À¸À®¤µ¤ì¤Þ¤¹¡£
+ +
SuppressColumnSorting
+ +
¤â¤·»ØÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢Apache ¤Ï + FancyIndexing ¤Çɽ¼¨¤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤Ç¤Î + ¥³¥é¥à¤ÎÀèƬ¤ò¡¢¥½¡¼¥È¤Î¤¿¤á¤Î¥ê¥ó¥¯¤Ë¤·¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤ÎµóÆ°¤Ï¡¢¥ê¥ó¥¯¤È¤·¤Þ¤¹¡£ + ¥³¥é¥à¤ÎÀèƬ¤òÁª¤Ö¤È¥³¥é¥à¤ÎÃͤ˽¾¤Ã¤Æ¥Ç¥£¥ì¥¯¥È¥ê¥ê¥¹¥È¤ò + ¥½¡¼¥È¤·¤Þ¤¹¡£ + Apache 2.0.23 °ÊÁ°¤Ç¤Ï¡¢¤³¤ì¤ÏƱ»þ¤Ë + ¥½¡¼¥Èʸ»úÎó¤Î¤¿¤á¤Î¥¯¥¨¥ê¡¼°ú¿ô¤Î²òÀϤâ̵¸ú¤Ë¤·¤Þ¤¹¡£ + + ¤³¤ÎµóÆ°¤Ï Apache 2.0.23 ¤Ç¤Ï + IndexOptions + IgnoreClient ¤ÇÀ©¸æ¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
+ +
SuppressDescription
+ +
¤³¤ì¤Ï FancyIndexing ¤Ë¤ª¤±¤ë¥Õ¥¡¥¤¥ë¤ÎÀâÌÀ¤ò¾Ãµî¤·¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢ÀâÌÀ¤ÏÄêµÁ¤µ¤ì¤Æ¤ª¤é¤º¡¢ + ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤È¾¤Î¤¿¤á¤Ë 23 + ʸ»ú¤Î¶õÇò¤ò²Ô¤°¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ ¥Õ¥¡¥¤¥ë¤ÎÀâÌÀ¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¡¢ + AddDescription + ¤ò¤´Í÷²¼¤µ¤¤¡£¤Þ¤¿¡¢ÀâÌÀ¤Î¥³¥é¥à¥µ¥¤¥º¤òÀ©¸Â¤¹¤ë + DescriptionWidth + ¥¤¥ó¥Ç¥Ã¥¯¥¹¥ª¥×¥·¥ç¥ó¤â¤´Í÷²¼¤µ¤¤¡£
+ +
SuppressHTMLPreamble
+ +
Ä̾ + HeaderName + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤷ¤¿¥Õ¥¡¥¤¥ë¤ò + ¥Ç¥£¥ì¥¯¥È¥ê¤¬¼ÂºÝ¤Ë´Þ¤ó¤Ç¤¤¤ì¤Ð¡¢É¸½àŪ¤Ê HTML ¥×¥ê¥¢¥ó¥Ö¥ë + (<html>, <head>, Åù) ¤Î¸å¤Ë¡¢ + ¥â¥¸¥å¡¼¥ë¤Ï¥Õ¥¡¥¤¥ë¤ÎÃæ¿È¤ò¥¤¥ó¥¯¥ë¡¼¥É¤·¤Þ¤¹¡£ + SuppressHTMLPreamble ¥ª¥×¥·¥ç¥ó¤Ï¡¢ + ¤³¤ÎµóÆ°¤ò̵¸ú¤Ë¤Ç¤­¤Æ¡¢ + ¥â¥¸¥å¡¼¥ë¤¬¥Ø¥Ã¥À¡¼¥Õ¥¡¥¤¥ë¤ÎÃæ¿È¤«¤éɽ¼¨¤ò»Ï¤á¤Þ¤¹¡£ + ¤³¤Î¾ì¹ç¡¢¥Ø¥Ã¥À¡¼¥Õ¥¡¥¤¥ë¤ÏÀµ¤·¤¤ HTML + Ì¿Îá¤ò´Þ¤ó¤Ç¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¥Ø¥Ã¥À¡¼¥Õ¥¡¥¤¥ë¤¬Â¸ºß¤·¤Ê¤¤¾ì¹ç¤Ï¡¢¥×¥ê¥¢¥ó¥Ö¥ë¤ÏÄ̾ïÄ̤ê + À¸À®¤µ¤ì¤Þ¤¹¡£
+ +
SuppressIcon (Apache + 2.0.23 °Ê¹ß)
+ +
+ ¤³¤ì¤Ï FancyIndexing ¤Î°ìÍ÷¤«¤é¥¢¥¤¥³¥ó¤ò¾Ãµî¤·¤Þ¤¹¡£ + SuppressIcon ¤È SuppressRules + ¤ÈÁȹç¤ï¤»¤ë¤³¤È¤Ë¤è¤Ã¤ÆÀµ¤·¤¤ HTML 3.2 ¤Î½ÐÎϤ¬ÆÀ¤é¤ì¤Þ¤¹¡£ + Àµ¤·¤¤ HTML 3.2 ½ÐÎϤϡ¢ºÇ½ªµ¬³Ê¤Ë¤ª¤¤¤Æ img ¤È hr + ¤¬ pre ¥Ö¥í¥Ã¥¯¤ËÆþ¤ë (FancyIndexing °ìÍ÷¤Ç½ñ¼°¤Ë»È¤ï¤ì¤Æ¤¤¤Þ¤¹) + ¤³¤È¤ò¶Ø»ß¤·¤Æ¤¤¤Þ¤¹¡£
+ +
SuppressLastModified
+ +
FancyIndexing °ìÍ÷¤Ë¤ª¤¤¤ÆºÇ½ª¹¹¿·Æü»þ¤Îɽ¼¨¤ò¾Ãµî¤·¤Þ¤¹¡£
+ +
SuppressRules + (Apache 2.0.23 °Ê¹ß)
+ +
¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤Ë¤ª¤¤¤Æ¿åÊ¿¶èÀÚ¤êÀþ (hr ¥¿¥°) ¤ò¾Ãµî¤·¤Þ¤¹¡£ + SuppressIcon ¤È SuppressRules + ¤ÈÁȹç¤ï¤»¤ë¤³¤È¤Ë¤è¤Ã¤ÆÀµ¤·¤¤ HTML 3.2 ¤Î½ÐÎϤ¬ÆÀ¤é¤ì¤Þ¤¹¡£ + Àµ¤·¤¤ HTML 3.2 ½ÐÎϤϡ¢ºÇ½ªµ¬³Ê¤Ë¤ª¤¤¤Æ img ¤È hr + ¤¬ pre ¥Ö¥í¥Ã¥¯¤ËÆþ¤ë (FancyIndexing °ìÍ÷¤Ç½ñ¼°¤Ë»È¤ï¤ì¤Æ¤¤¤Þ¤¹) + ¤³¤È¤ò¶Ø»ß¤·¤Æ¤¤¤Þ¤¹¡£
+ +
SuppressSize
+ +
FancyIndexing °ìÍ÷¤Ë¤ª¤¤¤Æ¥Õ¥¡¥¤¥ë¥µ¥¤¥º¤Îɽ¼¨¤ò¾Ãµî¤·¤Þ¤¹¡£
+ +
TrackModified + (Apache 2.0.23 °Ê¹ß)
+ +
¤³¤ì¤Ï HTTP ¥Ø¥Ã¥ÀÃæ¤Ë¡¢ + ¥ê¥¹¥È¤µ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤ÎºÇ½ª¹¹¿·Æü¤ä ETag Ãͤò´Þ¤á¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ä¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬ + ŬÀÚ¤Ê stat() ¤ÎÊÖ¤êÃͤòÊÖ¤¹¾ì¹ç¤Ë¤Î¤ßÍ­¸ú¤Ç¤¹¡£ + ¤¤¤¯¤Ä¤«¤Î UNIX ¥·¥¹¥Æ¥à¡¢OS2 ¤Î JFS ¤ä Win32 ¤Î NTFS + ¥Ü¥ê¥å¡¼¥à¤Ï¤½¤¦¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + Î㤨¤Ð¡¢OS2 ¤È Win32 FAT ¥Ü¥ê¥å¡¼¥à¤Ï¤½¤¦¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¤³¤Îµ¡Ç½¤¬Í­¸ú¤Ë¤Ê¤ë¤È¡¢¥¯¥é¥¤¥¢¥ó¥È¤ä¥×¥í¥­¥·¤Ï + HEAD ¥ê¥¯¥¨¥¹¥È¤ò¹Ô¤¦¤³¤È¤Ë¤è¤Ã¤Æ¡¢ + ¥Õ¥¡¥¤¥ë°ìÍ÷¤ÎÊѲ½¤òÄÉÀפ¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤¤¤¯¤Ä¤«¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ï¡¢¿·µ¬¥Õ¥¡¥¤¥ë¤ä + °ÜÆ°¥Õ¥¡¥¤¥ë¤ÏÀµ¤·¤¯ÄÉÀפ¹¤ë¤±¤ì¤É¤â¡¢ + ¥Ç¥£¥ì¥¯¥È¥êÃæ¤Î¥Õ¥¡¥¤¥ë¤Î¥µ¥¤¥º¤äÆüÉÕ¤ÏÄÉÀפ·¤Ê¤¤¤È¤¤¤¦¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ´û¤Ë¸ºß¤¹¤ë¥Õ¥¡¥¤¥ë¤Î¥µ¥¤¥º¤äÆüÉդΥ¹¥¿¥ó¥×¤¬ÊѲ½¤·¤Æ¤â¡¢ + Á´¤Æ¤Î Unix ¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤Ï¡¢ + ºÇ½ª¹¹¿·Æü¥Ø¥Ã¥À¡¼¤ò¹¹¿·¤·¤Þ¤»¤ó¡£ + ¤â¤·¤³¤ì¤¬½ÅÍפǤ¢¤ì¤Ð¡¢ + ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò̵¸ú¤Î¤Þ¤Þ¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
+ +
VersionSort + (Apache 2.0a3 °Ê¹ß)
+ +
VersionSort ¥­¡¼¥ï¡¼¥É¤Ï¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤ò´Þ¤ó¤À¥Õ¥¡¥¤¥ë¤¬ + ¼«Á³¤ÊÊýË¡¤Ç¥½¡¼¥È¤µ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ʸ»úÎó¤ÏÄ̾ïÄ̤꥽¡¼¥È¤µ¤ì¡¢ + ¤½¤ì°Ê³°¤Î¡¢ÀâÌÀ¤ä̾Á°Ãæ¤Î¿ô¤È¤Ê¤ëÉôʬʸ»úÎó¤Ï + ¤½¤Î¿ôÃͤÇÈæ³Ó¤µ¤ì¤Þ¤¹¡£ + +

Îã:

+ foo-1.7
+ foo-1.7.2
+ foo-1.7.12
+ foo-1.8.2
+ foo-1.8.2a
+ foo-1.12 +

+ +

Èֹ椬 0 ¤«¤é»Ï¤Þ¤ë¾ì¹ç¤Ï¡¢Ã¼¿ô¤È¹Í¤¨¤é¤ì¤Þ¤¹

+ +

+ foo-1.001
+ foo-1.002
+ foo-1.030
+ foo-1.04 +

+
+ +
XHTML + (Apache 2.0.49 °Ê¹ß)
+ +
XHTML ¥­¡¼¥ï¡¼¥É¤ò»ØÄꤹ¤ë¤È¡¢mod_autoindex + ¤Ï HTML 3.2 ¤ÎÂå¤ï¤ê¤Ë XHTML 1.0 ¤Î¥³¡¼¥É¤ò½ÐÎϤ¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
+
+ + +
Áý¸º»ØÄê¤Ç¤­¤ë IndexOptions
+
+

Apache 1.3.3 ¤Ç¤Ï¡¢ + IndexOptions + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°·¤¤¤Ç´ö¤Ä¤«¤ÎÂ礭¤ÊÊѲ½¤¬Æ³Æþ¤µ¤ì¤Þ¤·¤¿¡£ + Æäˡ¢

+ +
    +
  • °ì¤Ä¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ¹¤ëÊ£¿ô¤Î + IndexOptions + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¸½ºß¤Ç¤Ï°ì¤Ä¤Ë¥Þ¡¼¥¸¤µ¤ì¤Þ¤¹¡£ + ¾å¤ÎÎã¤Î·ë²Ì¤Ï¡¢ + +

    + <Directory /foo> + + IndexOptions HTMLTable
    + IndexOptions SuppressColumnsorting +     + </Directory> +

    + +

    ¤ÈƱ°ì¤Ë¤Ê¤ê¤Þ¤¹¡£

    + +

    + IndexOptions HTMLTable SuppressColumnsorting +

    +
    • + +
  • Áý¸º¹½Ê¸ + (¤¹¤Ê¤ï¤Á¡¢'+' ¤ä '-' + ¤ÎÀÜƬ¼­¤¬ÉÕ¤¯¥­¡¼¥ï¡¼¥É) ¤ÎÄɲá£
    • +
+ +

'+' ¤ä '-' ÀÜƬ¼­¤ÎÉÕ¤¤¤¿¥­¡¼¥ï¡¼¥É¤Ë½Ð²ñ¤¦¤È¤½¤ì¤Ï¡¢ + ¤½¤Î»þÅÀ¤Ç¤Î IndexOptions + ¤ÎÀßÄê (¤³¤ì¤Ï¾åή¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ò¼õ¤±·Ñ¤®¤Þ¤¹) + ¤ËÂФ·¤ÆŬ±þ¤µ¤ì¤Þ¤¹¡£ + ¤·¤«¤·¤Ê¤¬¤é¡¢ÀÜƬ¼­¤ÎÉÕ¤«¤Ê¤¤¥­¡¼¥ï¡¼¥É¤¬½èÍý¤µ¤ì¤¿¾ì¹ç¤Ï¡¢ + ¼õ¤±·Ñ¤¤¤À¥ª¥×¥·¥ç¥óÁ´¤Æ¤È¤½¤ì¤Þ¤Ç½Ð²ñ¤Ã¤¿Áý¸ºÀßÄêÁ´¤Æ¤¬ + ¾Ãµî¤µ¤ì¤Þ¤¹¡£¼¡¤ÎÎã¤ò¹Í¤¨¤Æ¤ß¤Æ¤¯¤À¤µ¤¤:

+ +

+ IndexOptions +ScanHTMLTitles -IconsAreLinks FancyIndexing
+ IndexOptions +SuppressSize +

+ +

Ãæ¿È¤Î¸ú²Ì¤Ï + IndexOptions FancyIndexing +SuppressSize + ¤ÈƱ°ì¤Ç¤¹¡£ + ÀÜƬ¼­¤ÎÉÕ¤«¤Ê¤¤ FancyIndexing + ¤Ç¤½¤ì°ÊÁ°¤ÎÁý¸º¥­¡¼¥ï¡¼¥É¤ò̵¸ú¤Ë¤µ¤ì¤Æ¡¢ + ¤½¤Î¸å¤ÎÎßÀѤ¬»Ï¤Þ¤ë¤«¤é¤Ç¤¹¡£

+ +

̵¾ò·ï¤Ë IndexOptions + ¤ò¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ÇÀßÄꤹ¤ë¤³¤È¤Ë¤è¤Ã¤Æ + ·Ñ¾µ¤·¤¿ÀßÄê¤ò¾Ãµî¤·¤Æ¡¢+ ¤ä - + ÀÜƬ¼­¤ÎÉÕ¤«¤Ê¤¤¥­¡¼¥ï¡¼¥É¤ÇÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£

+
+
+ +
+
top
+

IndexOrderDefault ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ: +¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤Îɸ½à¤Î½çÈÖÉÕ¤±¤òÀßÄê
¹½Ê¸:IndexOrderDefault Ascending|Descending +Name|Date|Size|Description
¥Ç¥Õ¥©¥ë¥È:IndexOrderDefault Ascending Name
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

IndexOrderDefault ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + FancyIndexing + ¥¤¥ó¥Ç¥Ã¥¯¥¹¥ª¥×¥·¥ç¥ó¤ÈÊ»¤»¤ÆÍѤ¤¤ì¤ì¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢FancyIndexing + ¤Î¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤Ï¥Õ¥¡¥¤¥ë̾¤Î¾º½ç¤Çɽ¼¨¤µ¤ì¤Þ¤¹¡£ + IndexOrderDefault + ¤Ç¡¢½é´ü¾õÂÖ¤Îɽ¼¨½çÈÖ¤òÊѤ¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

IndexOrderDefault + ¤ÏÆó¤Ä¤Î°ú¿ô¤ò¤È¤ê¤Þ¤¹¡£°ì¤ÄÌܤϥ½¡¼¥È¤ÎÊý¸þ¤ò»Ø¼¨¤¹¤ë + Ascending ¤« Descending ¤Î¤¤¤º¤ì¤«¤Ç¤¹¡£ + Æó¤ÄÌܤΰú¿ô¤Ï Name, Date, + Size ¤« Description + ¤Î¤¤¤º¤ì¤«°ì¤Ä¤Î¥­¡¼¥ï¡¼¥É¤Ç¤¢¤Ã¤Æ¡¢¥×¥é¥¤¥Þ¥ê¥­¡¼¤ò»ØÄꤷ¤Þ¤¹¡£ + Æó¤ÄÌܤΥ­¡¼¤Ï¾ï¤Ë¥Õ¥¡¥¤¥ë̾¤Î¾º½ç¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È SuppressColumnSorting + ¥¤¥ó¥Ç¥Ã¥¯¥¹¥ª¥×¥·¥ç¥ó¤È¤òÁȤ߹ç¤ï¤»¤ë¤³¤È¤Ç¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤ò¤¢¤ëÆÃÄê¤Î½çÈ֤ǤΤßɽ¼¨¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤¬Ê̤νçÈ֤ǥǥ£¥ì¥¯¥È¥ê°ìÍ÷¤ò¥ê¥¯¥¨¥¹¥È¤¹¤ë¤³¤È¤òËɤ®¤Þ¤¹¡£

+ +
+
top
+

IndexStyleSheet ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ë CSS ¥¹¥¿¥¤¥ë¥·¡¼¥È¤òÄɲ乤ë
¹½Ê¸:IndexStyleSheet url-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

IndexStyleSheet ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥¤¥ó¥Ç¥Ã¥¯¥¹É½¼¨¤Ë»ÈÍѤµ¤ì¤ë CSS ¤Î¥Õ¥¡¥¤¥ë̾¤òÀßÄꤷ¤Þ¤¹¡£ +

+

Îã

+ + IndexStyleSheet "/css/style.css" +

+ +
+
top
+

ReadmeName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¤¥ó¥Ç¥Ã¥¯¥¹°ìÍ÷¤ÎºÇ¸å¤ËÁÞÆþ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°
¹½Ê¸:ReadmeName filename
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_autoindex
+

ReadmeName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Î½ª¤ï¤ê¤ËÉÕ¤±²Ã¤¨¤é¤ì¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤷ¤Þ¤¹¡£ + filename ¤ÏÁÞÆþ¤¹¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°¤Ç¡¢ + °ìÍ÷¤Î¹Ô¤ï¤ì¤Æ¤¤¤ë°ÌÃÖ¤«¤éÁêÂÐŪ¤Ê¤â¤Î¤È¤·¤Æ²ò¼á¤µ¤ì¤Þ¤¹¡£ + filename ¤¬¥¹¥é¥Ã¥·¥å¤Ç»Ï¤Þ¤ë¾ì¹ç¤Ï¡¢ + DocumentRoot + ¤«¤é¤ÎÁêÂХѥ¹¤È¤Ê¤ê¤Þ¤¹¡£

+ +

Îã

+ ReadmeName FOOTER.html +

+ +

Îã 2

+ ReadmeName /include/FOOTER.html +

+ +

¤è¤ê¾ÜºÙ¤Ë¤Þ¤Ç¤³¤ÎµóÆ°¤Ë¤Ä¤¤¤Æµ­½Ò¤·¤Æ¤¤¤ë HeaderName + ¤â¤´Í÷²¼¤µ¤¤¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_autoindex.html.ko.euc-kr b/docs/manual/mod/mod_autoindex.html.ko.euc-kr new file mode 100644 index 00000000..70cc4822 --- /dev/null +++ b/docs/manual/mod/mod_autoindex.html.ko.euc-kr @@ -0,0 +1,835 @@ + + + +mod_autoindex - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_autoindex

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:ÀÚµ¿À¸·Î À¯´Ð½ºÀÇ ls ¸í·É¾î³ª Win32ÀÇ + dir ½©¸í·É¾î¿Í À¯»çÇÑ µð·ºÅ丮 ¸ñ·ÏÀ» ¸¸µç´Ù
»óÅÂ:Base
¸ðµâ¸í:autoindex_module
¼Ò½ºÆÄÀÏ:mod_autoindex.c
+

¿ä¾à

+ +

µð·ºÅ丮 ¸ñ·ÏÀº ¾ò´Â ¹æ¹ýÀº µÎ°¡Áö´Ù:

+ +
    +
  • º¸Åë index.htmlÀ̶õ À̸§À¸·Î »ç¿ëÀÚ°¡ + ÀÛ¼ºÇÑ ÆÄÀÏ. ÀÌ ÆÄÀÏÀÇ À̸§Àº DirectoryIndex Áö½Ã¾î·Î + ÁöÁ¤ÇÑ´Ù. ÀÌ ÀÛ¾÷Àº mod_dirÀÌ ÇÑ´Ù.
    • + +
  • ¾Æ´Ï¸é ¼­¹ö°¡ ¸ñ·ÏÀ» ¸¸µç´Ù. ÀÌ ¸ñ·ÏÀÇ Çü½ÄÀ» ÁöÁ¤ÇÏ´Â + Áö½Ã¾îµéÀÌ ÀÖ´Ù. AddIcon, AddIconByEncoding, + AddIconByTypeÀº + ¿©·¯ ÆÄÀÏÁ¾·ù¸¶´Ù º¸¿©ÁÙ ¾ÆÀÌÄܵéÀ» ÁöÁ¤ÇÑ´Ù. °¢ ÆÄÀÏ¿¡ + ´ëÀÀÇϴ ù¹ø° ¾ÆÀÌÄÜÀ» º¸ÀδÙ. ÀÌ ÀÛ¾÷À» + mod_autoindex°¡ ÇÑ´Ù.
    • +
+

ÀÌ µÎ ±â´ÉÀº ¼­·Î º°°³·Î, ¿øÇÑ´Ù¸é ÀÚµ¿ ¸ñ·Ï »ý¼ºÀ» ¿ÏÀüÈ÷ + Á¦¿ÜÇÒ (ȤÀº ´ëüÇÒ) ¼ö ÀÖ´Ù.

+ +

ÀÚµ¿ ¸ñ·Ï »ý¼ºÀº Options +Indexes·Î °¡´ÉÇÏ´Ù. + ÀÚ¼¼ÇÑ ³»¿ëÀº Options + Áö½Ã¾î¸¦ Âü°íÇ϶ó.

+ +

IndexOptions + Áö½Ã¾î¿¡ FancyIndexing ¿É¼ÇÀ» ÁÖ¸é, ¿­ À̸§À» Ãâ·ÂÇÒ + ¼ø¼­¸¦ ¹Ù²Ù´Â ¸µÅ©·Î ¸¸µç´Ù. À̸§ ¸µÅ©¸¦ ¼±ÅÃÇÏ¸é ±× ¿­ÀÇ + °ª ¼ø¼­·Î ¸ñ·ÏÀ» ´Ù½Ã ¸¸µç´Ù. °°Àº À̸§À» ¹Ýº¹Çؼ­ ¼±ÅÃÇϸé + ¿À¸§Â÷¼ø°ú ³»¸²Â÷¼ø »çÀ̸¦ ¿À°£´Ù. IndexOptions Áö½Ã¾îÀÇ + SuppressColumnSorting ¿É¼ÇÀº ÀÌ·± ¿­ À̸§ ¸µÅ©¸¦ + ¸¸µéÁö ¾Ê´Â´Ù.

+ +

"Size(Å©±â)" ¼øÀ¸·Î º¼¶§ Ãâ·ÂµÇ´Â °ª ¼ø¼­°¡ ¾Æ´Ï¶ó ½ÇÁ¦ + ÆÄÀÏÅ©±â ¼ø¼­ÀÓÀ» ÁÖÀÇÇ϶ó. Áï, 1010 ¹ÙÀÌÆ® ÆÄÀÏ°ú 1011 + ¹ÙÀÌÆ® ÆÄÀÏÀº µÑ´Ù "1K"·Î º¸ÀÌ´õ¶óµµ Ç×»ó 1010 ¹ÙÀÌÆ® ÆÄÀÏÀÌ + ¾Õ¿¡ ³ª¿Â´Ù.

+
+ +
top
+
+

Autoindex ¿äû ¾Æ±Ô¸ÕÆ®

+ + +

¾ÆÆÄÄ¡ 2.0.23´Â ¿­¼ø¼­¿¡ ´ëÇÑ ¿äû ¾Æ±Ô¸ÕÆ®¸¦ Á¤¸®ÇÏ°í, + »õ·Î¿î ¿É¼ÇµéÀ» Ãß°¡Çß´Ù. Ãâ·ÂÀ» Ŭ¶óÀ̾ðÆ®°¡ Á¶ÀýÇÒ ¼ö + ¾øµµ·Ï ¸¸µå´Â IndexOptions + IgnoreClient ¿É¼ÇÀÌ Ãß°¡µÇ¾ú´Ù.

+ +

¿­¼ø¼­ À̸§Àº ¾Æ·¡ ³ª¿Â ¼ø¼­ ¿äû ¿É¼ÇÀ» ´õÇÑ ÀÚ±âÂüÁ¶ + ¸µÅ©´Ù. ¾Æ·¡ ¿É¼ÇÀº µð·ºÅ丮 ÀÚ¿ø¿¡ ´ëÇÑ ¾î¶² ¿äû¿¡µµ + »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +
    +
  • C=NÀº ÆÄÀÏ¸í ¼øÀÌ´Ù
    • + +
  • C=MÀº ÃÖ±Ù ¼öÁ¤ÀÏ ¼ø, ±×¸®°í ÆÄÀÏ¸í ¼øÀÌ´Ù
    • + +
  • C=S´Â Å©±â ¼ø, ±×¸®°í ÆÄÀÏ¸í ¼øÀÌ´Ù
    • + +
  • C=D´Â ¼³¸í ¼ø, ±×¸®°í ÆÄÀϸí + ¼øÀÌ´Ù
    • + +
  • O=A´Â ¿À¸§Â÷¼øÀ¸·Î ¸ñ·ÏÀ» Á¤·ÄÇÑ´Ù
    • + +
  • O=D´Â ³»¸²Â÷¼øÀ¸·Î ¸ñ·ÏÀ» Á¤·ÄÇÑ´Ù
    • + +
  • F=0Àº (FancyIndexed°¡ ¾Æ´Ñ) °£´ÜÇÑ ¸ñ·Ï Çü½ÄÀÌ´Ù
    • + +
  • F=1Àº FancyIndexed ¸ñ·Ï Çü½ÄÀÌ´Ù
    • + +
  • F=2´Â HTMLTable FancyIndexed ¸ñ·Ï + Çü½ÄÀÌ´Ù
    • + +
  • V=0Àº ¹öÀü ¼øÀ¸·Î Á¤·ÄÇÏÁö ¾Ê´Â´Ù
    • + +
  • V=1Àº ¹öÀü ¼øÀ¸·Î Á¤·ÄÇÑ´Ù
    • + +
  • P=patternÀº ÁÖ¾îÁø pattern¿¡ + ÇØ´çÇÏ´Â ÆÄÀϸ¸À» ¸ñ·ÏÀ¸·Î ¸¸µç´Ù
    • +
+ +

'P'attern ¾Æ±Ô¸ÕÆ®´Â ÀϹÝÀûÀÎ IndexIgnore Áö½Ã¾î¸¦ ó¸®ÇÑ ÈÄ¿¡ + °Ë»çÇϱ⶧¹®¿¡, ¸ñ·ÏÀº ´Ù¸¥ autoindex Á¶°ÇÀ» µû¸§À» ÁÖÀÇÇ϶ó. + mod_autoindexÀÇ ¿äû ¾Æ±Ô¸ÕÆ®¸¦ ÀоîµéÀ϶§ + ¾Ë ¼ö ¾ø´Â ¿É¼ÇÀ» ¹ß°ßÇÏ¸é ´õ ÀÌ»ó ÀÐÁö¾Ê´Â´Ù. ¿äû ¾Æ±Ô¸ÕÆ®´Â + À§ÀÇ Ç¥¿¡ µû¶ó ¸¸µé¾î¾ß ÇÑ´Ù.

+ +

header.html ÆÄÀÏ¿¡ »ç¿ëÇÒ ¼ö ÀÖ´Â ¾Æ·¡ °£´ÜÇÑ ¿¹Á¦´Â + ÀÌ ¿É¼ÇµéÀ» ¼³¸íÇÑ´Ù. submit ¹öÅÏÀÇ ¾Ë ¼ö ¾ø´Â "X" ¾Æ±Ô¸ÕÆ®´Â + mod_autoindex°¡ X=Go Àü±îÁö ¸ðµç ¾Æ±Ô¸ÕÆ®¸¦ ÀоîµéÀÓÀ» + È®ÀÎÇϱâÀ§ÇØ ¸¶Áö¸·¿¡ »ç¿ëÇß´Ù.

+ +

+ <form action="" method="get">
+ + Show me a <select name="F">
+ + <option value="0"> Plain list</option>
+ <option value="1" selected="selected"> Fancy list</option>
+ <option value="2"> Table list</option>
+ + </select>
+ Sorted by <select name="C">
+ + <option value="N" selected="selected"> Name</option>
+ <option value="M"> Date Modified</option>
+ <option value="S"> Size</option>
+ <option value="D"> Description</option>
+ + </select>
+ <select name="O">
+ + <option value="A" selected="selected"> Ascending</option>
+ <option value="D"> Descending</option>
+ + </select>
+ <select name="V">
+ + <option value="0" selected="selected"> in Normal order</option>
+ <option value="1"> in Version order</option>
+ + </select>
+ Matching <input type="text" name="P" value="*" />
+ <input type="submit" name="X" value="Go" />
+ + </form> +

+ +
+
top
+

AddAlt Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÆÄÀϸíÀ¸·Î ¼±ÅÃÇÑ ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ÆÄÀÏ ¼³¸í±Û
¹®¹ý:AddAlt string file [file] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

AddAlt´Â FancyIndexing¿¡¼­ + ÆÄÀÏ¿¡ ´ëÇÑ ¾ÆÀÌÄÜ´ë½Å º¸ÀÏ ±ÛÀ» ÁöÁ¤ÇÑ´Ù. File¿¡´Â + ¼³¸íÇÒ ÆÄÀÏÀÇ ÆÄÀÏ È®ÀåÀÚ, ÆÄÀϸí ÀϺÎ, ¿ÍÀϵåÄ«µå Ç¥Çö, + Àüü ÆÄÀϸíÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. String¿¡ °ø¹éÀÌ + µé¾î°£´Ù¸é µû¿ÈÇ¥(" ȤÀº ')·Î + ¹­¾î¾ß ÇÑ´Ù. Ŭ¶óÀ̾ðÆ®°¡ À̹ÌÁö¸¦ º¼ ¼ö ¾ø°Å³ª, À̹ÌÁö¸¦ + ÀÐÁö¾Ê°Å³ª, ¾ÆÀÌÄÜÀ» ¸ø ¾òÀº °æ¿ì ÀÌ Ãß°¡ ±ÛÀÌ º¸ÀÌ°Ô µÈ´Ù.

+ +

¿¹Á¦

+ AddAlt "PDF file" *.pdf
+ AddAlt Compressed *.gz *.zip *.Z +

+ +
+
top
+

AddAltByEncoding Áö½Ã¾î

+ + + + + + + +
¼³¸í:MIME-encodingÀ¸·Î ¼±ÅÃÇÑ ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ÆÄÀÏ +¼³¸í±Û
¹®¹ý:AddAltByEncoding string MIME-encoding +[MIME-encoding] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

AddAltByEncodingÀº FancyIndexing¿¡¼­ + ÆÄÀÏ¿¡ ´ëÇÑ ¾ÆÀÌÄÜ´ë½Å º¸ÀÏ ±ÛÀ» ÁöÁ¤ÇÑ´Ù. MIME-encodingÀº + x-compress¿Í °°Àº À¯È¿ÇÑ content-encodingÀÌ´Ù. + String¿¡ °ø¹éÀÌ µé¾î°£´Ù¸é µû¿ÈÇ¥(" + ȤÀº ')·Î ¹­¾î¾ß ÇÑ´Ù. Ŭ¶óÀ̾ðÆ®°¡ À̹ÌÁö¸¦ + º¼ ¼ö ¾ø°Å³ª, À̹ÌÁö¸¦ ÀÐÁö¾Ê°Å³ª, ¾ÆÀÌÄÜÀ» ¸ø ¾òÀº °æ¿ì + ÀÌ Ãß°¡ ±ÛÀÌ º¸ÀÌ°Ô µÈ´Ù.

+ +

¿¹Á¦

+ AddAltByEncoding gzip x-gzip +

+ +
+
top
+

AddAltByType Áö½Ã¾î

+ + + + + + + +
¼³¸í:MIME content-typeÀ¸·Î ¼±ÅÃÇÑ ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ÆÄÀÏ +¼³¸í±Û
¹®¹ý:AddAltByType string MIME-type +[MIME-type] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

AddAltByTypeÀº FancyIndexing¿¡¼­ + ÆÄÀÏ¿¡ ´ëÇÑ ¾ÆÀÌÄÜ´ë½Å º¸ÀÏ ±ÛÀ» ÁöÁ¤ÇÑ´Ù. MIME-typeÀº + text/html°ú °°Àº À¯È¿ÇÑ content-typeÀÌ´Ù. + String¿¡ °ø¹éÀÌ µé¾î°£´Ù¸é µû¿ÈÇ¥(" + ȤÀº ')·Î ¹­¾î¾ß ÇÑ´Ù. Ŭ¶óÀ̾ðÆ®°¡ À̹ÌÁö¸¦ + º¼ ¼ö ¾ø°Å³ª, À̹ÌÁö¸¦ ÀÐÁö¾Ê°Å³ª, ¾ÆÀÌÄÜÀ» ¸ø ¾òÀº °æ¿ì + ÀÌ Ãß°¡ ±ÛÀÌ º¸ÀÌ°Ô µÈ´Ù.

+ +

¿¹Á¦

+ AddAltByType 'plain text' text/plain +

+ +
+
top
+

AddDescription Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÆÄÀÏ¿¡ ´ëÇÑ ¼³¸í
¹®¹ý:AddDescription string file [file] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

ÀÌ Áö½Ã¾î´Â FancyIndexing¿¡¼­ ÆÄÀÏ¿¡ ´ëÇÑ ¼³¸íÀ» ÁöÁ¤ÇÑ´Ù. + File¿¡´Â ¼³¸íÇÒ ÆÄÀÏÀÇ ÆÄÀÏ È®ÀåÀÚ, ÆÄÀϸí ÀϺÎ, + ¿ÍÀϵåÄ«µå Ç¥Çö, Àüü ÆÄÀϸíÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. StringÀº + µû¿ÈÇ¥(")·Î ¹­¾î¾ß ÇÑ´Ù.

+ +

¿¹Á¦

+ AddDescription "The planet Mars" /web/pics/mars.gif +

+ +

ÀüÇüÀûÀÎ ±âº» ¼³¸í ÇʵåÆøÀº 23 ¹ÙÀÌÆ®´Ù. IndexOptions + SuppressIcon ¿É¼ÇÀ» »ç¿ëÇÏ¸é ±âº»Æø¿¡ 6 ¹ÙÀÌÆ®¸¦ + ´õ Ãß°¡ÇÏ°í, IndexOptions SuppressSize ¿É¼ÇÀº 7 ¹ÙÀÌÆ®¸¦, + IndexOptions SuppressLastModified ¿É¼ÇÀº 19 + ¹ÙÀÌÆ®¸¦ ´õ Ãß°¡ÇÑ´Ù. ±×·¯¹Ç·Î °¡Àå ³ÐÀº ¼³¸íÆøÀº 55 ¹ÙÀÌÆ®´Ù.

+ +

ÀÌ ÇʵåÀÇ Æø¸¦ ¹Ù²Ù°Å³ª ¼³¸íÀÇ ±æÀ̸¦ ¹«ÇÑ´ë·Î ¸¸µå·Á¸é + DescriptionWidth IndexOptions Å°¿öµå¸¦ Âü°íÇ϶ó.

+ +

Á¶½É

+

AddDescriptionÀ¸·Î ÁöÁ¤ÇÑ ¼³¸í±Û¿¡ + ű׳ª character entity(¿ªÁÖ; &lt;, &amp; µîÀ» + ÁöĪ)°°Àº HTMLÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª Æø¶§¹®¿¡ + űװ¡ ÀÖ´Â ºÎºÐÀÌ Â©¸®°ÔµÇ¸é (¿¹¸¦ µé¾î ±½ÀºÃ¼ ºÎºÐ ³¡ÀÌ + ©¸®¸é) ³ª¸ÓÁö µð·ºÅ丮 ¸ñ·Ï¿¡ ¿µÇâÀ» ÁÙ ¼ö ÀÖ´Ù.

+
+ +
+
top
+

AddIcon Áö½Ã¾î

+ + + + + + + +
¼³¸í:À̸§À¸·Î ¼±ÅÃÇÑ ÆÄÀÏ¿¡ »ç¿ëÇÒ ¾ÆÀÌÄÜ
¹®¹ý:AddIcon icon name [name] +...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

ÀÌ Áö½Ã¾î´Â FancyIndexing¿¡¼­ nameÀ¸·Î ³¡³ª´Â + ÆÄÀÏ ¿·¿¡ º¸¿©ÁÙ ¾ÆÀÌÄÜÀ» ÁöÁ¤ÇÑ´Ù. IconÀº + ¾ÆÀÌÄÜÀÇ (%-escaped) »ó´ë URL ȤÀº + (alttext,url) Çü½ÄÀÌ´Ù. + ¿©±â¼­ alttext´Â ±×¸²À» º¸¿©ÁÙ ¼ö ¾ø´Â ºê¶ó¿ìÀú°¡ + ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ¹®±¸ÀÌ´Ù.

+ +

Name¿¡´Â µð·ºÅ丮¸¦ ³ªÅ¸³»´Â ^^DIRECTORY^^, + (¸ñ·Ï Çü½ÄÀ» ¿Ã¹Ù·Î ¸ÂÃß±âÀ§ÇØ) ºóÁÙÀ» ³ªÅ¸³»´Â + ^^BLANKICON^^, ÆÄÀÏ È®ÀåÀÚ, ¿ÍÀϵåÄ«µå Ç¥Çö, + ÆÄÀϸí ÀϺΠȤÀº Àüü¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

¿¹Á¦

+ AddIcon (IMG,/icons/image.xbm) .gif .jpg .xbm
+ AddIcon /icons/dir.xbm ^^DIRECTORY^^
+ AddIcon /icons/backup.xbm *~ +

+ +

°¡´ÉÇϸé AddIconº¸´Ù´Â AddIconByTypeÀ» »ç¿ëÇØ¾ß ÇÑ´Ù.

+ +
+
top
+

AddIconByEncoding Áö½Ã¾î

+ + + + + + + +
¼³¸í:MIME content-encodingÀ¸·Î ¼±ÅÃÇÑ ÆÄÀÏ¿¡ »ç¿ëÇÒ ¾ÆÀÌÄÜ
¹®¹ý:AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

ÀÌ Áö½Ã¾î´Â FancyIndexing¿¡¼­ + ÆÄÀÏ ¿·¿¡ º¸¿©ÁÙ ¾ÆÀÌÄÜÀ» ÁöÁ¤ÇÑ´Ù. IconÀº + ¾ÆÀÌÄÜÀÇ (%-escaped) »ó´ë URL ȤÀº + (alttext,url) Çü½ÄÀÌ´Ù. + ¿©±â¼­ alttext´Â ±×¸²À» º¸¿©ÁÙ ¼ö ¾ø´Â ºê¶ó¿ìÀú°¡ + ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ¹®±¸ÀÌ´Ù.

+ +

MIME-encoding´Â content-encoding¿¡ ÇØ´çÇÏ´Â + ¿ÍÀϵåÄ«µå Ç¥ÇöÀÌ´Ù.

+ +

¿¹Á¦

+ AddIconByEncoding /icons/compress.xbm x-compress +

+ +
+
top
+

AddIconByType Áö½Ã¾î

+ + + + + + + +
¼³¸í:MIME content-typeÀ¸·Î ¼±ÅÃÇÑ ÆÄÀÏ¿¡ »ç¿ëÇÒ ¾ÆÀÌÄÜ
¹®¹ý:AddIconByType icon MIME-type +[MIME-type] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

ÀÌ Áö½Ã¾î´Â FancyIndexing¿¡¼­ + MIME-typeÀÇ ÆÄÀÏ ¿·¿¡ º¸¿©ÁÙ ¾ÆÀÌÄÜÀ» ÁöÁ¤ÇÑ´Ù. + IconÀº ¾ÆÀÌÄÜÀÇ (%-escaped) »ó´ë URL ȤÀº + (alttext,url) Çü½ÄÀÌ´Ù. + ¿©±â¼­ alttext´Â ±×¸²À» º¸¿©ÁÙ ¼ö ¾ø´Â ºê¶ó¿ìÀú°¡ + ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ¹®±¸ÀÌ´Ù.

+ +

MIME-typeÀº mime type¿¡ ÇØ´çÇÏ´Â ¿ÍÀϵåÄ«µå + Ç¥ÇöÀÌ´Ù.

+ +

¿¹Á¦

+ AddIconByType (IMG,/icons/image.xbm) image/* +

+ +
+
top
+

DefaultIcon Áö½Ã¾î

+ + + + + + + +
¼³¸í:ƯÁ¤ ¾ÆÀÌÄÜÀ» ¼³Á¤ÇÏÁö¾ÊÀº ÆÄÀÏ¿¡ »ç¿ëÇÒ ¾ÆÀÌÄÜ
¹®¹ý:DefaultIcon url-path
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

DefaultIcon Áö½Ã¾î´Â FancyIndexing¿¡¼­ + ƯÁ¤ ¾ÆÀÌÄÜÀ» ¼³Á¤ÇÏÁö¾ÊÀº ÆÄÀÏ ¿·¿¡ ³ª¿Ã ¾ÆÀÌÄÜÀÌ´Ù. + IconÀº ¾ÆÀÌÄÜÀÇ (%-escaped) »ó´ë URLÀÌ´Ù.

+ +

¿¹Á¦

+ DefaultIcon /icon/unknown.xbm +

+ +
+
top
+

HeaderName Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÆÄÀϸñ·Ï À§¿¡ »ðÀÔÇÒ ÆÄÀÏÀÇ À̸§
¹®¹ý:HeaderName filename
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

HeaderName Áö½Ã¾î´Â ÆÄÀϸñ·Ï ¾Õ¿¡ + »ðÀÔÇÒ ÆÄÀÏÀÇ À̸§À» ÁöÁ¤ÇÑ´Ù. FilenameÀº »ðÀÔÇÒ + ÆÄÀϸíÀÌ´Ù.

+ +

¿¹Á¦

+ HeaderName HEADER.html +

+ +
+

ÇöÀç HeaderName°ú ReadmeName µÑ ¸ðµÎ + FilenameÀ» Á¢±ÙÇÏ·Á´Â µð·ºÅ丮ÀÇ »ó´ë URI °æ·Î·Î + ¹Þ¾ÆµéÀδÙ. FilenameÀÌ ½½·¡½¬·Î ½ÃÀÛÇϸé DocumentRoot¿¡ »ó´ëÀûÀÎ °æ·Î·Î + ¹Þ¾ÆµéÀδÙ.

+ +

¿¹Á¦

+ HeaderName /include/HEADER.html +

+ +

Filename¿¡´Â major content typeÀÌ text/*ÀÎ + (¿¹¸¦ µé¾î, text/html, text/plain, + µî) ¹®¼­¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù. Áï, ½ºÅ©¸³Æ®ÀÇ (Ãâ·ÂÀÌ ¾Æ´Ñ) ½ÇÁ¦ ÆÄÀÏ + typeÀ» ´ÙÀ½°ú °°ÀÌ text/html·Î ÁöÁ¤ÇÑ´Ù¸é + filenameÀ¸·Î CGI ½ºÅ©¸³Æ®¸¦ ÁöÁ¤ÇÒ ¼öµµ ÀÖ´Ù:

+ +

+ AddType text/html .cgi +

+ +

Options + MultiViewsÀ» »ç¿ëÇÏ¸é ³»¿ëÇù»óÀ» ÇÑ´Ù. + filenameÀÌ (CGI ½ºÅ©¸³Æ®°¡ ¾Æ´Ñ) °íÁ¤µÈ + text/html ¹®¼­ÀÌ°í options Includes³ª + IncludesNOEXEC Áß Çϳª¸¦ »ç¿ëÇÑ´Ù¸é ÆÄÀÏÀ» + server-side includes·Î ó¸®ÇÑ´Ù. (mod_include + ¹®¼­ Âü°í)

+
+ +

HeaderNameÀ¸·Î ÁöÁ¤ÇÑ ÆÄÀÏ¿¡ + (<html>, <head>, µî) HTML ¹®¼­ ½ÃÀۺκÐÀÌ Æ÷ÇÔµÇÀÖ´Ù¸é + IndexOptions + +SuppressHTMLPreambleÀ» »ç¿ëÇÏ¿© ÀÌ ºÎºÐÀ» Ãß°¡ÇÏÁö¾Ê´Â + °ÍÀÌ ÁÁ´Ù.

+ +
+
top
+

IndexIgnore Áö½Ã¾î

+ + + + + + + +
¼³¸í:µð·ºÅ丮 ¸ñ·Ï¿¡¼­ ¼û±æ ÆÄÀϸñ·ÏÀ» Ãß°¡ÇÑ´Ù
¹®¹ý:IndexIgnore file [file] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

IndexIgnore Áö½Ã¾î´Â µð·ºÅ丮 + ¸ñ·Ï¿¡¼­ °¨Ãâ ÆÄÀϸñ·ÏÀ» Ãß°¡ÇÑ´Ù. File¿¡´Â °¨Ãâ + (½©¿¡¼­ »ç¿ëÇÏ´Â) È­ÀϵåÄ«µå Ç¥ÇöÀ̳ª Àüü ÆÄÀϸíÀ» + »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¿©·¯ IndexIgnore Áö½Ã¾î¸¦ »ç¿ëÇÏ¸é ±âÁ¸ÀÇ + °¨Ãâ ÆÄÀϸñ·ÏÀ» ´ëüÇÏÁö¾Ê°í ¸ñ·Ï¿¡ ÁöÁ¤ÇÑ ÆÄÀϵéÀ» Ãß°¡ÇÑ´Ù. + ±âº»ÀûÀ¸·Î ¸ñ·ÏÀº .À» (ÇöÀç µð·ºÅ丮) Æ÷ÇÔÇÑ´Ù.

+ +

+ IndexIgnore README .htaccess *.bak *~ +

+ +
+
top
+

IndexOptions Áö½Ã¾î

+ + + + + + + +
¼³¸í:µð·ºÅ丮 ¸ñ·ÏÀÇ ¿©·¯ ¼³Á¤µé
¹®¹ý:IndexOptions [+|-]option [[+|-]option] +...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

IndexOptions Áö½Ã¾î´Â µð·ºÅ丮 + ¸ñ·ÏÀ» ¼³Á¤ÇÑ´Ù. OptionÀº ´ÙÀ½ Áß ÇϳªÀÌ´Ù

+ +
+
DescriptionWidth=[n | *] (¾ÆÆÄÄ¡ + 2.0.23 ÀÌÈÄ)
+ +
DescriptionWidth Å°¿öµå¸¦ »ç¿ëÇÏ¿© ¹®ÀÚ´ÜÀ§·Î + ¼³¸í¿­ÀÇ ÆøÀ» ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù.
+ +
-DescriptionWidth¸¦ ÁöÁ¤Çϸé (ȤÀº ¾Æ¹«°Íµµ + ÁöÁ¤ÇÏÁö¾ÊÀ¸¸é) mod_autoindex°¡ ÃÖÀûÀÇ + ÆøÀ» °è»êÇÑ´Ù.
+ +
DescriptionWidth=nÀº ¿­ÀÇ + ÆøÀ» n ¹ÙÀÌÆ®·Î °íÁ¤ÇÑ´Ù.
+ +
DescriptionWidth=*Àº ¿­ÀÇ ÆøÀ» °¡Àå ±ä + ¼³¸í±ÛÀ» ´ãÀ» ¼ö Àִ¸¸Å­ ´Ã¸°´Ù.
+ +
¼³Á¤ÀÌ Â©¸± ¼ö ÀÖ´Â ¹®Á¦´Â AddDescription + ÀýÀ» Âü°íÇ϶ó.
+ +
FancyIndexing
+ +
µð·ºÅ丮ÀÇ fancy ¸ñ·ÏÀ» ¸¸µç´Ù.
+ +
FoldersFirst + (¾ÆÆÄÄ¡ 2.0.23 ÀÌÈÄ)
+ +
ÀÌ ¿É¼ÇÀ» »ç¿ëÇϸé ÇÏÀ§µð·ºÅ丮 ¸ñ·ÏÀÌ Ç×»ó + ¸ÕÀú ³ª¿À°í, µð·ºÅ丮¿¡ ÀÖ´Â ÀÏ¹Ý ÆÄÀÏÀÌ µÚ¿¡ ³ª¿Â´Ù. + ±âº»ÀûÀ¸·Î ¸ñ·ÏÀº ÆÄÀÏ°ú ÇÏÀ§µð·ºÅ丮·Î ³ª´µ°í, µû·Î + °¢°¢ÀÇ ¼ø¼­¸¦ Á¤¸®ÇÏ¿© ÇÏÀ§µð·ºÅ丮µéÀ» ¸ÕÀú º¸ÀδÙ. + ¿¹¸¦ µé¾î, À̸§ ¿ª¼øÀ¸·Î Á¤·ÄÇÏ°í FoldersFirst¸¦ + »ç¿ëÇÑ´Ù¸é ÇÏÀ§µð·ºÅ丮 Zed°¡ ÇÏÀ§µð·ºÅ丮 + Beta ¾Õ¿¡ ³ª¿À°í, ÇÏÀ§µð·ºÅ丮 Beta´Â + ÀÏ¹Ý ÆÄÀÏ Gamma¿Í Alpha ¾Õ¿¡ + ³ª¿Â´Ù. ÀÌ ¿É¼ÇÀº FancyIndexingÀ» ÇÔ²² »ç¿ëÇÒ¶§¸¸ È¿°ú°¡ + ÀÖ´Ù.
+ +
HTMLTable (½ÇÇèÀû, + ¾ÆÆÄÄ¡ 2.0.23 ÀÌÈÄ)
+ +
ÀÌ ½ÇÇèÀûÀÎ FancyIndexing ¿É¼ÇÀº °£´ÜÇÑ HTML Ç¥·Î + fancy µð·ºÅ丮 ¸ñ·ÏÀ» ¸¸µç´Ù. ÀÌ ¿É¼ÇÀº ¿À·¡µÈ ºê¶ó¿ìÀú¸¦ + È¥¶õ½º·´°Ô ÇÒ ¼ö ÀÖÀ½À» ÁÖÀÇÇ϶ó. ÀÌ ¿É¼ÇÀº WinNT³ª ´Ù¸¥ + utf-8 »ç¿ë Ç÷¡Æû¿¡¼­ ÆÄÀϸíÀ̳ª ¼³¸í¹®ÀÇ Àб⠼ø¼­(¿ÞÂÊ¿¡¼­ + ¿À¸¥ÂÊ È¤Àº ¿À¸¥ÂÊ¿¡¼­ ¿ÞÂÊÀ¸·Î)°¡ ´Ù¸¦¶§ Ưº°È÷ À¯¿ëÇÏ´Ù.
+ +
IconsAreLinks
+ +
fancy ¸ñ·Ï¿¡¼­ ÆÄÀÏ¸í ¸µÅ©¿¡ ¾ÆÀÌÄÜÀ» Æ÷ÇÔÇÑ´Ù.
+ +
IconHeight[=pixels]
+ +
ÀÌ ¿É¼ÇÀ» IconWidth¿Í °°ÀÌ »ç¿ëÇÏ¸é ¼­¹ö´Â ÆÄÀÏ ¾ÆÀÌÄÜÀÇ + img ű׿¡ height¿Í width + ¼Ó¼ºÀ» Æ÷ÇÔÇÑ´Ù. ±×·¯¸é ºê¶ó¿ìÀú´Â ¸ðµç À̹ÌÁö¸¦ ¹ÞÁö¾ÊÀº + »óȲ¿¡¼­µµ ÆäÀÌÁö ±¸¼ºÀ» ¹Ì¸® °è»êÇÒ ¼ö ÀÖ´Ù. ¿É¼Ç¿¡ °ªÀ» + ÁÖÁö¾ÊÀ¸¸é ¾ÆÆÄÄ¡°¡ Á¦°øÇÏ´Â ¾ÆÀÌÄÜÀÇ Ç¥ÁØ ³ôÀ̸¦ »ç¿ëÇÑ´Ù.
+ +
IconWidth[=pixels]
+ +
ÀÌ ¿É¼ÇÀ» IconHeight¿Í °°ÀÌ »ç¿ëÇϸé + ¼­¹ö´Â ÆÄÀÏ ¾ÆÀÌÄÜÀÇ img ű׿¡ + height¿Í width ¼Ó¼ºÀ» Æ÷ÇÔÇÑ´Ù. + ±×·¯¸é ºê¶ó¿ìÀú´Â ¸ðµç À̹ÌÁö¸¦ ¹ÚÁö¾ÊÀº »óȲ¿¡¼­µµ ÆäÀÌÁö + ±¸¼ºÀ» ¹Ì¸® °è»êÇÒ ¼ö ÀÖ´Ù. ¿É¼Ç¿¡ °ªÀ» ÁÖÁö¾ÊÀ¸¸é ¾ÆÆÄÄ¡°¡ + Á¦°øÇÏ´Â ¾ÆÀÌÄÜÀÇ Ç¥ÁØ ÆøÀ» »ç¿ëÇÑ´Ù.
+ +
IgnoreCase
+ +
ÀÌ ¿É¼ÇÀ» »ç¿ëÇÏ¸é ´ë¼Ò¹®ÀÚ ±¸º°ÇÏÁö¾Ê°í À̸§À» Á¤·ÄÇÑ´Ù. + ¿¹¸¦ µé¾î, À̸§À¸·Î ¿À¸§Â÷¼øÀÌ°í IgnoreCase¸¦ »ç¿ëÇϸé + ÆÄÀÏ Zeta´Â ÆÄÀÏ alfa µÚ¿¡ ³ª¿Â´Ù (ÁÖÀÇ: ÆÄÀÏ GAMMA´Â + Ç×»ó ÆÄÀÏ gamma ¾Õ¿¡ ³ª¿Â´Ù).
+ +
IgnoreClient
+ +
ÀÌ ¿É¼ÇÀ» »ç¿ëÇϸé mod_autoindex´Â + ¼ø¼­¸¦ Æ÷ÇÔÇÏ¿© Ŭ¶óÀ̾ðÆ®°¡ º¸³»´Â ¸ðµç ÁúÀǺ¯¼ö¸¦ ¹«½ÃÇÑ´Ù. + (SuppressColumnSortingÀ» °¡Á¤ÇÑ´Ù.)
+ +
NameWidth=[n + | *]
+ +
NameWidth Å°¿öµå´Â ¹ÙÀÌÆ®´ÜÀ§·Î ÆÄÀϸí + ¿­ÀÇ ÆøÀ» ÁöÁ¤ÇÑ´Ù.
+ +
-NameWidthÀ» ÁöÁ¤Çϸé (ȤÀº ¾Æ¹«°Íµµ + ÁöÁ¤ÇÏÁö¾ÊÀ¸¸é) mod_autoindex°¡ ÃÖÀûÀÇ + ÆøÀ» °è»êÇÑ´Ù.
+ +
NameWidth=n´Â ¿­ÀÇ ÆøÀ» n + ¹ÙÀÌÆ®·Î °íÁ¤ÇÑ´Ù.
+ +
NameWidth=*Àº ¿­ÀÇ ÆøÀ» ÇÊ¿äÇѸ¸Å­ ´Ã¸°´Ù.
+ +
ScanHTMLTitles
+ +
fancy ¸ñ·Ï¿¡¼­ HTML ¹®¼­ÀÇ titleÀ» »Ì´Â´Ù. ÆÄÀÏ¿¡ + AddDescription·Î + ÁöÁ¤ÇÑ ¼³¸íÀÌ ¾ø´Ù¸é À¥¼­¹ö´Â ¹®¼­ÀÇ title + ¿ä¼Ò°ªÀ» ÀоîµéÀδÙ. ÀÌ ÀÛ¾÷Àº CPU¿Í µð½ºÅ©¸¦ ¸¹ÀÌ »ç¿ëÇÑ´Ù.
+ +
SuppressColumnSorting
+ +
ÀÌ ¿É¼ÇÀ» »ç¿ëÇÏ¸é ¾ÆÆÄÄ¡´Â FancyIndexed µð·ºÅ丮 + ¸ñ·Ï¿¡¼­ ¿­ À̸§À» ¼ø¼­¸¦ ¹Ù²Ù´Â ¸µÅ©·Î ¸¸µéÁö ¾Ê´Â´Ù. + º¸ÅëÀº ¿­ À̸§À» ¸µÅ©·Î ¸¸µé¾î¼­, ¿­ À̸§À» ¼±ÅÃÇÏ¸é ±× + ¿­¿¡ ÀÖ´Â °ª¼ø¼­·Î µð·ºÅ丮 ¸ñ·ÏÀ» ¸¸µç´Ù. ¾ÆÆÄÄ¡ + 2.0.23 ÀÌÀü¿¡´Â ¼ø¼­ ¾Æ±Ô¸ÕÆ®µµ ÀÐÁö ¾Ê¾Ò´Ù. + ¾ÆÆÄÄ¡ 2.0.23¿¡¼­´Â IndexOptions + IgnoreClient¸¦ »ç¿ëÇÏ¿© ¼ø¼­ ¾Æ±Ô¸ÕÆ®¸¦ ÀÐÁö ¾Ê´Â´Ù.
+ +
SuppressDescription
+ +
fancy ¸ñ·Ï¿¡¼­ ÆÄÀÏ ¼³¸íÀ» Æ÷ÇÔÇÏÁö ¾Ê´Â´Ù. ±âº»ÀûÀ¸·Î + ¾î¶² ÆÄÀÏ ¼³¸íµµ Á¤ÀǵÇÀÖÁö¾Ê°í, ÀÌ ¿É¼ÇÀ» »ç¿ëÇϸé 23 + ¹®ÀÚ °ø°£À» ´Ù¸¥ ¿ëµµ·Î »ç¿ëÇÑ´Ù. ÆÄÀÏ ¼³¸íÀ» ÁöÁ¤ÇÏ´Â + ¹æ¹ýÀº AddDescriptionÀ» Âü°íÇ϶ó. ¼³¸í¿­ÀÇ Å©±â¸¦ + ÁöÁ¤ÇÏ´Â DescriptionWidth + ¿É¼Çµµ Âü°íÇ϶ó.
+ +
SuppressHTMLPreamble
+ +
µð·ºÅ丮¿¡ HeaderName Áö½Ã¾î·Î + ÁöÁ¤ÇÑ ÆÄÀÏÀÌ ÀÖ´Â °æ¿ì ¸ðµâÀº º¸Åë Ç¥ÁØ HTML ½ÃÀۺκР+ (<html>, <head>, + et cetera) µÚ¿¡ ÆÄÀÏ ³»¿ëÀ» ÷°¡ÇÑ´Ù. ±×·¯³ª + SuppressHTMLPreamble ¿É¼ÇÀ» »ç¿ëÇϸé óÀ½ºÎÅÍ + header ÆÄÀÏ ³»¿ëÀ» Æ÷ÇÔÇÑ´Ù. ÀÌ °æ¿ì header ÆÄÀÏ¿¡´Â ÀûÀýÇÑ + HTML ¸í·ÉÀÌ ÀÖ¾î¾ß ÇÑ´Ù. header ÆÄÀÏÀÌ ¾ø´Ù¸é ÀϹÝÀûÀÎ + ½ÃÀۺκÐÀÌ ¸¸µé¾îÁø´Ù.
+ +
SuppressIcon + (¾ÆÆÄÄ¡ 2.0.23 ÀÌÈÄ)
+ +
fancy ¸ñ·Ï¿¡¼­ ¾ÆÀÌÄÜÀ» »«´Ù. SuppressIcon°ú + SuppressRules¸¦ °°ÀÌ »ç¿ëÇϸé, (FancyIndexed + ¸ñ·ÏÀÌ »ç¿ëÇÑ) pre ¾È¿¡ img¿Í + hr ¿ä¼Ò »ç¿ëÀ» ±ÝÁöÇÑ ¸¶Áö¸· Ç¥ÁØÀÎ HTML 3.2¿¡ + ¾Ë¸ÂÀº Ãâ·ÂÀÌ µÈ´Ù.
+ +
SuppressLastModified
+ +
fancy ¸ñ·Ï¿¡¼­ ¸¶Áö¸· ¼öÁ¤ÀÏÀ» Ç¥½ÃÇÏÁö ¾Ê´Â´Ù.
+ +
SuppressRules + (¾ÆÆÄÄ¡ 2.0.23 ÀÌÈÄ)
+ +
µð·ºÅ丮 ¸ñ·Ï¿¡¼­ ¼öÆòÁÙÀ» (hr ¿ä¼Ò) + »ç¿ëÇÏÁö ¾Ê´Â´Ù. SuppressIcon°ú + SuppressRules¸¦ °°ÀÌ »ç¿ëÇϸé, (FancyIndexed + ¸ñ·ÏÀÌ »ç¿ëÇÑ) pre ¾È¿¡ img¿Í + hr ¿ä¼Ò »ç¿ëÀ» ±ÝÁöÇÑ ¸¶Áö¸· Ç¥ÁØÀÎ HTML 3.2¿¡ + ¾Ë¸ÂÀº Ãâ·ÂÀÌ µÈ´Ù.
+ +
SuppressSize
+ +
fancy ¸ñ·Ï¿¡¼­ ÆÄÀÏÅ©±â¸¦ Ç¥½ÃÇÏÁö ¾Ê´Â´Ù.
+ +
TrackModified + (¾ÆÆÄÄ¡ 2.0.23 ÀÌÈÄ)
+ +
µð·ºÅ丮 ¸ñ·ÏÀÇ HTTP Çì´õ¿¡ Last-Modified¿Í ETag °ªÀ» + Æ÷ÇÔÇÑ´Ù. ÀÌ ¿É¼ÇÀº ¿î¿µÃ¼Á¦¿Í ÆÄÀϽýºÅÛ¿¡¼­ ÀûÀýÇÑ stat() + °á°ú¸¦ ¾òÀ» ¼ö ÀÖÀ»¶§¸¸ À¯È¿ÇÏ´Ù. À¯´Ð½º ½Ã½ºÅÛ°ú OS2ÀÇ + JFS, Win32ÀÇ NTFS¿¡¼­´Â °¡´ÉÇÏ´Ù. ¿¹¸¦ µé¾î, OS2¿Í Win32ÀÇ + FATÀº ºÒ°¡´ÉÇÏ´Ù. ÀÌ ±â´ÉÀ» »ç¿ëÇϸé Ŭ¶óÀ̾ðÆ®³ª ÇÁ·Ï½Ã´Â + HEAD ¿äûÀ» »ç¿ëÇÏ¿© ÆÄÀϸñ·ÏÀÇ º¯È­¸¦ ÃßÀûÇÒ + ¼ö ÀÖ´Ù. ¾î¶² ¿î¿µÃ¼Á¦´Â »õ·Î¿î ÆÄÀÏ°ú »èÁ¦ÇÑ ÆÄÀÏÀ» ¿Ã¹Ù·Î + ÃßÀûÇÏÁö¸¸, µð·ºÅ丮¿¡ ÀÖ´Â ÆÄÀÏÀÇ Å©±â³ª ³¯Â¥ º¯È­¸¦ + ÃßÀûÇÏÁö ¸øÇÔÀ» ÁÖÀÇÇ϶ó. ¸ðµç À¯´Ð½º Ç÷¡Æû¿¡¼­ + ±âÁ¸ ÆÄÀÏÀÇ Å©±â³ª ³¯Â¥ º¯È­½Ã Last-Modified Çì´õ°¡ + ¹Ù²îÁö¾Ê´Â´Ù. ÀÌ·± º¯È­°¡ Áß¿äÇÏ´Ù¸é ÀÌ ¿É¼ÇÀ» + »ç¿ëÇÏÁö ¸¶¶ó.
+ +
VersionSort + (¾ÆÆÄÄ¡ 2.0a3 ÀÌÈÄ)
+ +
VersionSort Å°¿öµå´Â ¹öÀü ¹øÈ£¸¦ Æ÷ÇÔÇÑ + ÆÄÀϸíÀ» ÀÚ¿¬½º·´°Ô Á¤·ÄÇÑ´Ù. ¹®ÀÚ ºÎºÐÀº Á¤»óÀûÀÎ ¼ø¼­¸¦ + Á¤·ÄÇÏÁö¸¸, ÆÄÀÏ°ú ¼³¸í¿¡ ÀÖ´Â ¼ýÀÚ ºÎºÐÀº ¼ýÀÚ°ªÀ¸·Î + ºñ±³ÇÑ´Ù. + +

¿¹Á¦:

+ foo-1.7
+ foo-1.7.2
+ foo-1.7.12
+ foo-1.8.2
+ foo-1.8.2a
+ foo-1.12 +

+ +

¼ö°¡ 0À¸·Î ½ÃÀÛÇϸé, ±× ¼ö¸¦ ºÐ¼ö·Î Ãë±ÞÇÑ´Ù:

+ +

+ foo-1.001
+ foo-1.002
+ foo-1.030
+ foo-1.04 +

+
+ +
XHTML + (¾ÆÆÄÄ¡ 2.0.49 ÀÌÈÄ)
+ +
XHTML Å°¿öµå¸¦ »ç¿ëÇϸé + mod_autoindex´Â HTML 3.2 ´ë½Å XHTML 1.0 + Äڵ带 »ý¼ºÇÑ´Ù.
+
+ + +
Á¡ÁøÀûÀÎ IndexOptions
+
+

¾ÆÆÄÄ¡ 1.3.3¿¡¼­ IndexOptions + Áö½Ã¾î 󸮹æ½ÄÀÌ Å©°Ô º¯È­µÇ¾ú´Ù. Ưº°È÷:

+ +
    +
  • ÀÌÁ¦ ÇÑ µð·ºÅ丮¿¡ ´ëÇÑ ¿©·¯ + IndexOptions Áö½Ã¾îµéÀ» ¼­·Î °áÇÕÇÑ´Ù. + ´ÙÀ½ÀÇ °á°ú´Â: + +

    + <Directory /foo> + + IndexOptions HTMLTable
    + IndexOptions SuppressColumnsorting +     + </Directory> +

    + +

    ´ÙÀ½°ú °°´Ù

    + +

    + IndexOptions HTMLTable SuppressColumnsorting +

    +
    • + +
  • (¿¹¸¦ µé¾î, Å°¿öµå ¾Õ¿¡ +³ª + -¸¦ ºÙÀÌ´Â) Á¡ÁøÀûÀÎ ¹®¹ýÀÌ Ãß°¡µÇ¾ú´Ù.
    • +
+ +

Å°¿öµå ¾Õ¿¡ '+'³ª '-'°¡ ºÙÀ»¶§¸¶´Ù ÇØ´ç Å°¿öµå°¡ ÇöÀç + (»óÀ§ µð·ºÅ丮¿¡¼­ »ó¼ÓµÇ¾úÀ») IndexOptions + ¼³Á¤¿¡ ¹Ý¿µµÈ´Ù. ±×·¯³ª ¾Õ¿¡ ¾Æ¹«°Íµµ ¾ø´Â Å°¿öµå¸¦ ¸¸³ª¸é + ¾ÆÁ÷±îÁö »ó¼ÓµÇ°Å³ª Á¡ÁøÀûÀ¸·Î º¯°æµÈ ¼³Á¤À» ¸ðµÎ Áö¿î´Ù. + ´ÙÀ½ ¿¹Á¦¸¦ »ìÆ캸ÀÚ:

+ +

+ IndexOptions +ScanHTMLTitles -IconsAreLinks FancyIndexing
+ IndexOptions +SuppressSize +

+ +

¾Õ¿¡ ¾Æ¹«°Íµµ ¾ø´Â FancyIndexingÀÌ ÀÌÀüÀÇ + Á¡ÁøÀûÀÎ ¼³Á¤À» Áö¿ö¹ö·ÈÁö¸¸ ¼³Á¤ÀÌ ´Ù½Ã Ãß°¡µÇ¿© °á°ú´Â + IndexOptions FancyIndexing +SuppressSize¿Í °°´Ù.

+ +

ƯÁ¤ µð·ºÅ丮¿¡ ´ëÇØ ¹«Á¶°ÇÀûÀÎ + IndexOptions¸¦ ¼³Á¤ÇÏ·Á¸é Å°¿öµå + ¾Õ¿¡ +³ª -¸¦ »ç¿ëÇÏÁö¸»°í + »ó¼ÓµÈ ¼³Á¤À» Áö¿î´Ù.

+
+
+ +
+
top
+

IndexOrderDefault Áö½Ã¾î

+ + + + + + + + +
¼³¸í:µð·ºÅ丮 ¸ñ·ÏÀÇ ±âº» ¼ø¼­¸¦ ¼³Á¤ÇÑ´Ù
¹®¹ý:IndexOrderDefault Ascending|Descending +Name|Date|Size|Description
±âº»°ª:IndexOrderDefault Ascending Name
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

IndexOrderDefault Áö½Ã¾î´Â FancyIndexing + ¸ñ·Ï ¿É¼Ç°ú ÇÔ²² »ç¿ëÇÑ´Ù. ±âº»ÀûÀ¸·Î fancyindexed µð·ºÅ丮 + ¸ñ·ÏÀº ÆÄÀÏ¸í ¿À¸§Â÷¼øÀÌ´Ù. IndexOrderDefault´Â + ÀÌ Ãʱ⠼ø¼­¸¦ º¯°æÇÒ ¼ö ÀÖ´Ù.

+ +

IndexOrderDefault´Â µÎ ¾Æ±Ô¸ÕÆ®¸¦ + ¹Þ´Â´Ù. ù¹ø°´Â ¼ø¼­ÀÇ ¹æÇâÀ» Áö½ÃÇÏ´Â Ascending + (¿À¸¥Â÷¼ø) À̳ª Descending (³»¸²Â÷¼ø) Áß Çϳª´Ù. + µÎ¹ø° ¾Æ±Ô¸ÕÆ®´Â ÀÏÂ÷ ¼ø¼­¸¦ ³ªÅ¸³»´Â Å°¿öµå Name, + Date, Size, Description + Áß Çϳª´Ù. ÀÌÂ÷ ¼ø¼­´Â Ç×»ó ÆÄÀÏ¸í ¿À¸§Â÷¼øÀÌ´Ù.

+ +

ÀÌ Áö½Ã¾î¿Í SuppressColumnSorting ¸ñ·Ï ¿É¼ÇÀ» °°ÀÌ »ç¿ëÇϸé + ƯÁ¤ ¼ø¼­·Î¸¸ µð·ºÅ丮 ¸ñ·ÏÀ» ¸¸µç´Ù. ÀÌ °æ¿ì Ŭ¶óÀ̾ðÆ®´Â + ´Ù¸¥ ¼ø¼­·Î µð·ºÅ丮 ¸ñ·ÏÀ» ¿äûÇÏÁö ¸øÇÑ´Ù.

+ +
+
top
+

IndexStyleSheet Áö½Ã¾î

+ + + + + + + +
¼³¸í:µð·ºÅ丮 ¸ñ·Ï¿¡ CSS ½ºÅ¸ÀϽ¬Æ®¸¦ Ãß°¡ÇÑ´Ù
¹®¹ý:IndexStyleSheet url-path
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

IndexStyleSheet Áö½Ã¾î´Â µð·ºÅ丮 + ¸ñ·Ï¿¡¼­ CSS·Î »ç¿ëÇÒ ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù. +

+

Example

+ + IndexStyleSheet "/css/style.css" +

+ +
+
top
+

ReadmeName Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÆÄÀϸñ·Ï ¸¶Áö¸·¿¡ »ðÀÔÇÒ ÆÄÀÏÀÇ À̸§
¹®¹ý:ReadmeName filename
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_autoindex
+

ReadmeName Áö½Ã¾î´Â ÆÄÀϸñ·Ï ³¡¿¡ + »ðÀÔÇÒ ÆÄÀÏÀÇ À̸§À» ÁöÁ¤ÇÑ´Ù. FilenameÀº Æ÷ÇÔÇÒ + ÆÄÀϸíÀÌ°í, ¸ñ·ÏÀ» ¸¸µé·Á´Â À§Ä¡ÀÇ »ó´ë°æ·Î·Î ¹Þ¾ÆµéÀδÙ. + FilenameÀÌ ½½·¡½¬·Î ½ÃÀÛÇϸé DocumentRoot¿¡ »ó´ë°æ·Î·Î ¹Þ¾ÆµéÀδÙ. +

+ +

¿¹Á¦

+ ReadmeName FOOTER.html +

+ +

¿¹Á¦ 2

+ ReadmeName /include/FOOTER.html +

+ +

ÀÌ µ¿ÀÛÀ» ÀÚ¼¼È÷ ¼³¸íÇÑ HeaderNameµµ Âü°íÇ϶ó.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cache.html b/docs/manual/mod/mod_cache.html new file mode 100644 index 00000000..cba0697e --- /dev/null +++ b/docs/manual/mod/mod_cache.html @@ -0,0 +1,11 @@ +URI: mod_cache.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_cache.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_cache.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_cache.html.en b/docs/manual/mod/mod_cache.html.en new file mode 100644 index 00000000..46dde826 --- /dev/null +++ b/docs/manual/mod/mod_cache.html.en @@ -0,0 +1,463 @@ + + + +mod_cache - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_cache

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Content cache keyed to URIs.
Status:Extension
Module Identifier:cache_module
Source File:mod_cache.c
+

Summary

+ +
This module should be used with care and + can be used to circumvent Allow and Deny directives. You + should not enable caching for any content to which you wish + to limit access by client host name, address or environment + variable.
+ +

mod_cache implements an RFC 2616 compliant HTTP + content cache that can be used to cache either local or proxied content. + mod_cache requires the services of one or more storage + management modules. Two storage management modules are included in + the base Apache distribution:

+
+
mod_disk_cache
+
implements a disk based storage manager.
+ +
mod_mem_cache
+
implements a memory based storage manager. + mod_mem_cache can be configured to operate in two + modes: caching open file descriptors or caching objects in heap storage. + mod_mem_cache can be used to cache locally generated content + or to cache backend server content for mod_proxy when + configured using ProxyPass + (aka reverse proxy)
+
+ +

Content is stored in and retrieved from the cache using URI based keys. Content with + access protection is not cached.

+

Further details, discussion, and examples, are provided in the + Caching Guide.

+
+ +
top
+
+

Related Modules and Directives

+
Related ModulesRelated Directives
+
top
+
+

Sample Configuration

+

Sample httpd.conf

+ #
+ # Sample Cache Configuration
+ #
+ LoadModule cache_module modules/mod_cache.so
+
+ <IfModule mod_cache.c>
+ + #LoadModule disk_cache_module modules/mod_disk_cache.so
+ # If you want to use mod_disk_cache instead of mod_mem_cache,
+ # uncomment the line above and comment out the LoadModule line below.
+ <IfModule mod_disk_cache.c>
+ + CacheRoot c:/cacheroot
+ CacheEnable disk /
+ CacheDirLevels 5
+ CacheDirLength 3
+ + </IfModule>
+
+ LoadModule mem_cache_module modules/mod_mem_cache.so
+ <IfModule mod_mem_cache.c>
+ + CacheEnable mem /
+ MCacheSize 4096
+ MCacheMaxObjectCount 100
+ MCacheMinObjectSize 1
+ MCacheMaxObjectSize 2048
+ + </IfModule>
+
+ # When acting as a proxy, don't cache the list of security updates
+ CacheDisable http://security.update.server/update-list/
+ + </IfModule> +

+
+
top
+

CacheDefaultExpire Directive

+ + + + + + + +
Description:The default duration to cache a document when no expiry date is specified.
Syntax:CacheDefaultExpire seconds
Default:CacheDefaultExpire 3600 (one hour)
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

The CacheDefaultExpire directive specifies a default time, + in seconds, to cache a document if neither an expiry date nor last-modified date are provided + with the document. The value specified with the CacheMaxExpire + directive does not override this setting.

+ +

+ CacheDefaultExpire 86400 +

+ +
+
top
+

CacheDisable Directive

+ + + + + + +
Description:Disable caching of specified URLs
Syntax:CacheDisable url-string
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

The CacheDisable directive instructs + mod_cache to not cache urls at or below + url-string.

+ +

Example

+ CacheDisable /local_files +

+ +
+
top
+

CacheEnable Directive

+ + + + + + +
Description:Enable caching of specified URLs using a specified storage +manager
Syntax:CacheEnable cache_type url-string
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

The CacheEnable directive instructs + mod_cache to cache urls at or below + url-string. The cache storage manager is specified with the + cache_type argument. cache_type mem + instructs mod_cache to use the memory based storage + manager implemented by mod_mem_cache. + cache_type disk instructs + mod_cache to use the disk based storage manager + implemented by mod_disk_cache. + cache_type fd instructs + mod_cache to use the file descriptor cache implemented + by mod_mem_cache.

+

In the event that the URL space overlaps between different + CacheEnable directives (as in the example below), + each possible storage manager will be run until the first one that + actually processes the request. The order in which the storage managers are + run is determined by the order of the CacheEnable + directives in the configuration file.

+ +

+ CacheEnable mem /manual
+ CacheEnable fd /images
+ CacheEnable disk /
+

+ +

When acting as a forward proxy server, url-string can + also be used to specify remote sites and proxy protocols which + caching should be enabled for.

+ +

+ # Cache proxied url's
+ CacheEnable disk /

+ # Cache FTP-proxied url's
+ CacheEnable disk ftp://

+ # Cache content from www.apache.org
+ CacheEnable disk http://www.apache.org/
+

+ + +
+
top
+

CacheIgnoreCacheControl Directive

+ + + + + + + +
Description:Ignore request to not serve cached content to client
Syntax:CacheIgnoreCacheControl On|Off
Default:CacheIgnoreCacheControl Off
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

Ordinarily, requests containing a Cache-Control: no-cache or + Pragma: no-cache header value will not be served from the cache. The + CacheIgnoreCacheControl directive allows this + behavior to be overridden. CacheIgnoreCacheControl + On tells the server to attempt to serve the resource from the cache even + if the request contains no-cache header values. Resources requiring + authorization will never be cached.

+ +

+ CacheIgnoreCacheControl On +

+ +

Warning:

+ This directive will allow serving from the cache even if the client has + requested that the document not be served from the cache. This might + result in stale content being served. +
+ +

See also

+ +
+
top
+

CacheIgnoreHeaders Directive

+ + + + + + + +
Description:Do not store the given HTTP header(s) in the cache. +
Syntax:CacheIgnoreHeaders header-string [header-string] ...
Default:CacheIgnoreHeaders None
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

According to RFC 2616, hop-by-hop HTTP headers are not stored in + the cache. The following HTTP headers are hop-by-hop headers and thus + do not get stored in the cache in any case regardless of the + setting of CacheIgnoreHeaders:

+ +
    +
  • Connection
    • +
  • Keep-Alive
    • +
  • Proxy-Authenticate
    • +
  • Proxy-Authorization
    • +
  • TE
    • +
  • Trailers
    • +
  • Transfer-Encoding
    • +
  • Upgrade
    • +
+ +

CacheIgnoreHeaders specifies additional HTTP + headers that should not to be stored in the cache. For example, it makes + sense in some cases to prevent cookies from being stored in the cache.

+ +

CacheIgnoreHeaders takes a space separated list + of HTTP headers that should not be stored in the cache. If only hop-by-hop + headers not should be stored in the cache (the RFC 2616 compliant + behaviour), CacheIgnoreHeaders can be set to + None.

+ +

Example 1

+ CacheIgnoreHeaders Set-Cookie +

+ +

Example 2

+ CacheIgnoreHeaders None +

+ +

Warning:

+ If headers like Expires which are needed for proper cache + management are not stored due to a + CacheIgnoreHeaders setting, the behaviour of + mod_cache is undefined. +
+ +
+
top
+

CacheIgnoreNoLastMod Directive

+ + + + + + + +
Description:Ignore the fact that a response has no Last Modified +header.
Syntax:CacheIgnoreNoLastMod On|Off
Default:CacheIgnoreNoLastMod Off
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

Ordinarily, documents without a last-modified date are not cached. + Under some circumstances the last-modified date is removed (during + mod_include processing for example) or not provided + at all. The CacheIgnoreNoLastMod directive + provides a way to specify that documents without last-modified dates + should be considered for caching, even without a last-modified date. + If neither a last-modified date nor an expiry date are provided with + the document then the value specified by the + CacheDefaultExpire directive will be used to + generate an expiration date.

+ +

+ CacheIgnoreNoLastMod On +

+ +
+
top
+

CacheLastModifiedFactor Directive

+ + + + + + + +
Description:The factor used to compute an expiry date based on the +LastModified date.
Syntax:CacheLastModifiedFactor float
Default:CacheLastModifiedFactor 0.1
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

In the event that a document does not provide an expiry date but does + provide a last-modified date, an expiry date can be calculated based on + the time since the document was last modified. The + CacheLastModifiedFactor directive specifies a + factor to be used in the generation of this expiry date + according to the following formula: + + expiry-period = time-since-last-modified-date * factor + expiry-date = current-date + expiry-period + + For example, if the document was last modified 10 hours ago, and + factor is 0.1 then the expiry-period will be set to + 10*0.1 = 1 hour. If the current time was 3:00pm then the computed + expiry-date would be 3:00pm + 1hour = 4:00pm. + + If the expiry-period would be longer than that set by + CacheMaxExpire, then the latter takes + precedence.

+ +

+ CacheLastModifiedFactor 0.5 +

+ +
+
top
+

CacheMaxExpire Directive

+ + + + + + + +
Description:The maximum time in seconds to cache a document
Syntax:CacheMaxExpire seconds
Default:CacheMaxExpire 86400 (one day)
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

The CacheMaxExpire directive specifies the maximum number of + seconds for which cachable HTTP documents will be retained without checking the origin + server. Thus, documents will be out of date at most this number of seconds. This maximum + value is enforced even if an expiry date was supplied with the document.

+ +

+ CacheMaxExpire 604800 +

+ +
+
top
+

CacheStoreNoStore Directive

+ + + + + + + +
Description:Attempt to cache requests or responses that have been marked as no-store.
Syntax:CacheStoreNoStore On|Off
Default:CacheStoreNoStore Off
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

Ordinarily, requests or responses with Cache-Control: no-store header + values will not be stored in the cache. The + CacheStoreNoCache directive allows this + behavior to be overridden. CacheStoreNoCache On + tells the server to attempt to cache the resource even if it contains + no-store header values. Resources requiring authorization will + never be cached.

+ +

+ CacheStoreNoStore On +

+ +

Warning:

+ As described in RFC 2616, the no-store directive is intended to + "prevent the inadvertent release or retention of sensitive information + (for example, on backup tapes)." Enabling this option could store + sensitive information in the cache. You are hereby warned. +
+ +

See also

+ +
+
top
+

CacheStorePrivate Directive

+ + + + + + + +
Description:Attempt to cache responses that the server has marked as private
Syntax:CacheStorePrivate On|Off
Default:CacheStorePrivate Off
Context:server config, virtual host
Status:Extension
Module:mod_cache
+

Ordinarily, responses with Cache-Control: private header values will not + be stored in the cache. The CacheStorePrivate + directive allows this behavior to be overridden. + CacheStorePrivate On + tells the server to attempt to cache the resource even if it contains + private header values. Resources requiring authorization will + never be cached.

+ +

+ CacheStorePrivate On +

+ +

Warning:

+ This directive will allow caching even if the upstream server has + requested that the resource not be cached. This directive is only + ideal for a 'private' cache. +
+ +

See also

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cache.html.ja.euc-jp b/docs/manual/mod/mod_cache.html.ja.euc-jp new file mode 100644 index 00000000..8627fff9 --- /dev/null +++ b/docs/manual/mod/mod_cache.html.ja.euc-jp @@ -0,0 +1,443 @@ + + + +mod_cache - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_cache

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:URI ¤ò¥­¡¼¤Ë¤·¤¿¥³¥ó¥Æ¥ó¥Ä¤Î¥­¥ã¥Ã¥·¥å
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:cache_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_cache.c
+

³µÍ×

+ +
+ ¤³¤ì¤Ï¼Â¸³Åª¤Ê¥â¥¸¥å¡¼¥ë¤Ç¤¹¡£Ê¸½ñ¤â¤Þ¤À³«È¯Ãæ¤Ç¤¹... +
+ +

mod_cache ¤Ï¥í¡¼¥«¥ë¤Î¥³¥ó¥Æ¥ó¥Ä¤ä¥×¥í¥­¥·¤µ¤ì¤¿ + ¥³¥ó¥Æ¥ó¥Ä¤ò¥­¥ã¥Ã¥·¥å¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤ë RFC 2616 ½àµò¤Î + HTTP ¥³¥ó¥Æ¥ó¥Ä¥­¥ã¥Ã¥·¥å¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£mod_cache + ¤ÎÆ°ºî¤Ë¤Ï¥¹¥È¥ì¡¼¥¸¤ò´ÉÍý¤¹¤ë¥â¥¸¥å¡¼¥ë¤¬É¬ÍפǤ¹¡£É¸½à + Apache ÇÛÉۤˤÏÆó¤Ä¥¹¥È¥ì¡¼¥¸´ÉÍý¥â¥¸¥å¡¼¥ë¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹:

+ +
+
mod_disk_cache
+
¥Ç¥£¥¹¥¯¤ò»ÈÍѤ·¤¿¥¹¥È¥ì¡¼¥¸´ÉÍýµ¡¹½¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£
+ +
mod_mem_cache
+
¥á¥â¥ê¤ò»ÈÍѤ·¤¿¥¹¥È¥ì¡¼¥¸´ÉÍýµ¡¹½¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£ + mod_mem_cache ¤Ï¼¡¤ÎÆó¤Ä¤Î¥â¡¼¥É¤Î¤É¤Á¤é¤«¤ÇÆ°ºî¤¹¤ë + ¤è¤¦¤ËÀßÄê¤Ç¤­¤Þ¤¹: ¥ª¡¼¥×¥ó¤µ¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤ò¥­¥ã¥Ã¥·¥å¤¹¤ë¥â¡¼¥É¤«¡¢ + ¥Ò¡¼¥×¾å¤Ç¤Î¥ª¥Ö¥¸¥§¥¯¥È¤Î¼«ÂΤò¥­¥ã¥Ã¥·¥å¤ò¤¹¤ë¥â¡¼¥É¤Ç¤¹¡£ + mod_mem_cache ¤Ï¥í¡¼¥«¥ë¤ÇÀ¸À®¤µ¤ì¤ë¥³¥ó¥Æ¥ó¥Ä¤ä¡¢ + mod_proxy ¤¬ + ProxyPass ¤ò»È¤Ã¤ÆÀßÄꤵ¤ì¤Æ¤¤¤ë + ¤È¤­¤Î (¤Ä¤Þ¤ê¥ê¥Ð¡¼¥¹¥×¥í¥­¥· ¤Ç¤Î) ¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤Î + ¥³¥ó¥Æ¥ó¥Ä¤ò¥­¥ã¥Ã¥·¥å¤¹¤ë¤Î¤Ë»È¤¨¤Þ¤¹¡£
+
+ +

¥³¥ó¥Æ¥ó¥Ä¤Î¥­¥ã¥Ã¥·¥å¤Ø¤ÎÊݸ¤È¼èÆÀ¤Ï URI ¤Ë´ð¤Å¤¤¤¿¥­¡¼¤¬»È¤ï¤ì¤Þ¤¹¡£ + ¥¢¥¯¥»¥¹Êݸî¤Î¤«¤±¤é¤ì¤Æ¤¤¤ë¥³¥ó¥Æ¥ó¥Ä¤Ï¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£

+
+ +
top
+
+

´ØÏ¢¥â¥¸¥å¡¼¥ë¤È¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+
top
+
+

¥µ¥ó¥×¥ëÀßÄê

+

Sample httpd.conf

+ #
+ # Sample Cache Configuration
+ #
+ LoadModule cache_module modules/mod_cache.so
+
+ <IfModule mod_cache.c>
+ + #LoadModule disk_cache_module modules/mod_disk_cache.so
+ # If you want to use mod_disk_cache instead of mod_mem_cache, + # uncomment the line above and comment out the LoadModule line below. + <IfModule mod_disk_cache.c>
+ + CacheRoot c:/cacheroot
+ CacheEnable disk /
+ CacheDirLevels 5
+ CacheDirLength 3
+ + </IfModule>
+
+ LoadModule mem_cache_module modules/mod_mem_cache.so
+ <IfModule mod_mem_cache.c>
+ + CacheEnable mem /
+ MCacheSize 4096
+ MCacheMaxObjectCount 100
+ MCacheMinObjectSize 1
+ MCacheMaxObjectSize 2048
+ + </IfModule>
+ + </IfModule> +

+
+
top
+

CacheDefaultExpire ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:´üÆü¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ë¥É¥­¥å¥á¥ó¥È¤ò¥­¥ã¥Ã¥·¥å¤¹¤ë¥Ç¥Õ¥©¥ë¥È¤Î´ü´Ö
¹½Ê¸:CacheDefaultExpire seconds
¥Ç¥Õ¥©¥ë¥È:CacheDefaultExpire 3600 (1»þ´Ö)
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

CacheDefaultExpire ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤Ë + Í­¸ú´ü¸Â (expiry) ¤äºÇ½ª½¤Àµ»þ¹ï (last-modified) ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Î + ¥Ç¥Õ¥©¥ë¥È¤Î»þ´Ö¤ò»ØÄꤷ¤Þ¤¹¡£CacheMaxExpire + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿ÃͤϤ³¤ÎÀßÄê¤ò¾å½ñ¤­¤·¤Þ¤»¤ó¡£

+ +

+ CacheDefaultExpire 86400 +

+ +
+
top
+

CacheDisable ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:ÆÃÄê¤Î URL ¤ò¥­¥ã¥Ã¥·¥å¤·¤Ê¤¤
¹½Ê¸:CacheDisable url-string
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

CacheDisable ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + mod_cache ¥â¥¸¥å¡¼¥ë¤¬ url-string °Ê²¼¤Î + URL ¤ò¥­¥ã¥Ã¥·¥å¤·¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

Îã

+ CacheDisable /local_files +

+ +
+
top
+

CacheEnable ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:»ØÄꤷ¤¿¥¹¥È¥ì¡¼¥¸´ÉÍýÊý¼°¤ò»È¤Ã¤Æ¤Î¥­¥ã¥Ã¥·¥å¤òÍ­¸ú¤Ë¤¹¤ë
¹½Ê¸:CacheEnable cache_type url-string
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

CacheEnable ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç mod_cache + ¥â¥¸¥å¡¼¥ë¤¬ url-string °Ê²¼¤Î URL ¤ò¥­¥ã¥Ã¥·¥å¤¹¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ¥­¥ã¥Ã¥·¥å¥¹¥È¥ì¡¼¥¸´ÉÍýÊý¼°¤Ï cache_type °ú¿ô¤Ç»ØÄꤷ¤Þ¤¹¡£ + cache_type mem ¤Ç¡¢ + mod_mem_cache ¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë¥á¥â¥ê¤ò»È¤Ã¤¿¥¹¥È¥ì¡¼¥¸ + ´ÉÍýÊý¼°¤ò»È¤¦¤è¤¦¤Ë mod_cache ¤Ë»Ø¼¨¤·¤Þ¤¹¡£ + cache_type disk ¤Ç¡¢ + mod_disk_cache ¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥¹¥¯¤ò»È¤Ã¤¿¥¹¥È¥ì¡¼¥¸ + ´ÉÍý¤ò»È¤¦¤è¤¦¤Ë mod_cache ¤Ë»Ø¼¨¤·¤Þ¤¹¡£ + cache_type fd ¤Ï mod_cache ¤Ë + mod_mem_cache ¤Ë¤è¤ê¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î + ¥­¥ã¥Ã¥·¥å¤ò»È¤¦¤è¤¦¤Ë»Ø¼¨¤·¤Þ¤¹¡£

+ +

(²¼¤ÎÎã¤Î¤è¤¦¤Ë) CacheEnable ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + URL ¶õ´Ö¤¬½ÅÊ£¤·¤Æ¤¤¤ë¤È¤­¤Ï¡¢³ºÅö¤¹¤ë¥¹¥È¥ì¡¼¥¸Êý¼°¤ò½ç¤Ë»î¤·¤Æ¡¢ + ¼ÂºÝ¤Ë¥ê¥¯¥¨¥¹¥È¤Î½èÍý¤¬¤Ç¤­¤ë¤È¡¢¤½¤ÎÊý¼°¤Ç½èÍý¤·¤Þ¤¹¡£ + ¥¹¥È¥ì¡¼¥¸´ÉÍýÊý¼°¤¬¼Â¹Ô¤µ¤ì¤ë½çÈÖ¤ÏÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î + CacheEnable ¤Î½çÈ֤ˤè¤ê·èÄꤵ¤ì¤Þ¤¹¡£

+ +

+ CacheEnable mem /manual
+ CacheEnable fd /images
+ CacheEnable disk /
+

+ +
+
top
+

CacheIgnoreCacheControl ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤µ¤ì¤Æ¤¤¤ë¥³¥ó¥Æ¥ó¥Ä¤òÊÖ¤µ¤Ê¤¤¤è¤¦¤Ë¥¯¥é¥¤¥¢¥ó¥È¤«¤é +¥ê¥¯¥¨¥¹¥È¤µ¤ì¤Æ¤â̵»ë¤¹¤ë
¹½Ê¸:CacheIgnoreCacheControl On|Off
¥Ç¥Õ¥©¥ë¥È:CacheIgnoreCacheControl Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

Cache-Control: no-cache ¥Ø¥Ã¥À¤ä Pragma: no-store ¥Ø¥Ã¥À¤Î¤¢¤ë¥ê¥¯¥¨¥¹¥È¤Ë + ÂФ·¤Æ¤Ï¡¢Ä̾省¥ã¥Ã¥·¥å¤ò»È¤¤¤Þ¤»¤ó¡£CacheIgnoreCacheControl + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤È¡¢¤³¤ÎÆ°ºî¤ò¾å½ñ¤­¤Ç¤­¤Þ¤¹¡£ + CacheIgnoreCacheControl On ¤È¤¹¤ë¤È¡¢ + ¥ê¥¯¥¨¥¹¥È¤Ë no-cache ¤È¤¤¤¦Ãͤ¬¤¢¤Ã¤Æ¤â¡¢¥­¥ã¥Ã¥·¥å¤ò»È¤Ã¤Æ¥É¥­¥å¥á¥ó¥È¤ò + ÊÖ¤¹¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£Ç§¾Ú¤òɬÍפȤ¹¤ë¥É¥­¥å¥á¥ó¥È¤Ï·è¤·¤Æ + ¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£

+ +

+ CacheIgnoreCacheControl On +

+ +

·Ù¹ð

+ ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤È¡¢¥É¥­¥å¥á¥ó¥È¼èÆÀ»þ¤Ë¥­¥ã¥Ã¥·¥å¤ò»È¤ï¤Ê¤¤¤è¤¦¤Ë + ¥¯¥é¥¤¥¢¥ó¥È¤¬¥ê¥¯¥¨¥¹¥È¤·¤Æ¤¤¤ë¤Ë¤â¤«¤«¤ï¤é¤º¡¢¥­¥ã¥Ã¥·¥å¤ò + »È¤¦¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£¤½¤Î·ë²Ì¡¢ + ¸Å¤¤¥³¥ó¥Æ¥ó¥Ä¤¬Á÷¤é¤ì³¤±¤ë¤³¤È¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¦¤«¤â¤·¤ì¤Þ¤»¤ó¡£ +
+ +

»²¾È

+ +
+
top
+

CacheIgnoreHeaders ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:»ØÄꤵ¤ì¤¿ HTTP ¥Ø¥Ã¥À¤ò¥­¥ã¥Ã¥·¥å¤ËÊݸ¤·¤Ê¤¤¡£ +
¹½Ê¸:CacheIgnoreHeaders header-string [header-string] ...
¥Ç¥Õ¥©¥ë¥È:CacheIgnoreHeaders None
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

RFC 2616 ¤Ë¤è¤ë¤È¡¢hop-by-hop HTTP ¥Ø¥Ã¥À¤Ï¥­¥ã¥Ã¥·¥å¤Ë¤ÏÊݴɤµ¤ì¤Þ¤»¤ó¡£ + °Ê²¼¤Î¥Ø¥Ã¥À¤Ï hop-by-hop ¥Ø¥Ã¥À¤Ë³ºÅö¤·¤Þ¤¹¤Î¤Ç¡¢ + CacheIgnoreHeaders + ¤ÎÀßÄê¤Ë´Ø·¸¤Ê¤¯¥­¥ã¥Ã¥·¥å¤Ë¤ÏÊݴɤµ¤ì¤Þ¤»¤ó:

+
    +
  • Connection
    • +
  • Keep-Alive
    • +
  • Proxy-Authenticate
    • +
  • Proxy-Authorization
    • +
  • TE
    • +
  • Trailers
    • +
  • Transfer-Encoding
    • +
  • Upgrade
    • +
+ +

CacheIgnoreHeaders ¤Ç + ¥­¥ã¥Ã¥·¥å¤ËÊݴɤ·¤Ê¤¤ÄɲäΠHTTP ¥Ø¥Ã¥À¤ò»ØÄꤷ¤Þ¤¹¡£ + Î㤨¤Ð¡¢¥¯¥Ã¥­¡¼¤ò¥­¥ã¥Ã¥·¥å¤ËÊݴɤ·¤Ê¤¤¤è¤¦¤Ë¤·¤¿Êý¤¬¤è¤¤¾ì¹ç¤â + ¤¢¤ë¤Ç¤·¤ç¤¦¡£

+ +

CacheIgnoreHeaders ¤Î°ú¿ô¤Ï¡¢ + ¥­¥ã¥Ã¥·¥å¤ËÊݴɤ·¤Ê¤¤ HTTP ¥Ø¥Ã¥À¤ò¶õÇò¶èÀÚ¤ê¤Ë¤·¤¿¥ê¥¹¥È·Á¼°¤Ç¤¹¡£ + ¥­¥ã¥Ã¥·¥å¤ËÊݴɤ·¤Ê¤¤¥Ø¥Ã¥À¤¬ hop-by-hop ¥Ø¥Ã¥À¤À¤±¤Î¾ì¹ç + (RFC 2616 ½àµò¤ÎÆ°ºî¤Î¤È¤­) ¤Ï¡¢ + CacheIgnoreHeaders ¤ò None + ¤ËÀßÄê¤Ç¤­¤Þ¤¹¡£

+ +

Îã 1

+ CacheIgnoreHeaders Set-Cookie +

+ +

Îã 2

+ CacheIgnoreHeaders None +

+ +

·Ù¹ð:

+ Expires ¤Î¤è¤¦¤ÊŬÀڤΥ­¥ã¥Ã¥·¥å´ÉÍý¤Î¤¿¤á¤ËɬÍ×¤Ê + ¥Ø¥Ã¥À¤¬ CacheIgnoreHeaders ¤ÎÀßÄê¤Ë¤è¤ê + Êݴɤµ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ï¡¢mod_cache ¤ÎÆ°ºî¤ÏÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£ +
+ +
+
top
+

CacheIgnoreNoLastMod ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:±þÅú¤Ë Last Modified ¤¬Ìµ¤¯¤Æ¤âµ¤¤Ë¤·¤Ê¤¤¤è¤¦¤Ë¤¹¤ë
¹½Ê¸:CacheIgnoreNoLastMod On|Off
¥Ç¥Õ¥©¥ë¥È:CacheIgnoreNoLastMod Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

Ä̾Last-Modified ¤Ë¤è¤ëºÇ½ª½¤Àµ»þ¹ï¤Î̵¤¤¥É¥­¥å¥á¥ó¥È¤Ï¥­¥ã¥Ã¥·¥å + ¤µ¤ì¤Þ¤»¤ó¡£(Î㤨¤Ð mod_include ¤Ë¤è¤ë½èÍý¤Î¤È¤­¤Ê¤É¤Ë) + Last-Modified »þ¹ï¤¬¾Ãµî¤µ¤ì¤¿¤ê¡¢¤½¤â¤½¤âºÇ½é¤«¤éÄ󶡤µ¤ì¤Æ¤¤¤Ê¤¤ + ¾õ¶·¤¬¤¢¤ê¤Þ¤¹¡£CacheIgnoreNoLastMod + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤È¡¢Last-Modified Æü»þ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤ + ¥É¥­¥å¥á¥ó¥È¤Ç¤â¥­¥ã¥Ã¥·¥å¤¹¤ë¤è¤¦¤Ë»ØÄê¤Ç¤­¤Þ¤¹¡£¥É¥­¥å¥á¥ó¥È¤Ë + ºÇ½ª½¤Àµ»þ¹ï (Last-Modified) Í­¸ú´ü¸Â (expiry) ¤¬¤Ê¤¤¾ì¹ç¤Ï¡¢Í­¸ú´ü¸Â¤Î + À¸À®¤Ë CacheDefaultExpire ¤¬»È¤ï¤ì¤Þ¤¹¡£

+ +

+ CacheIgnoreNoLastMod On +

+ +
+
top
+

CacheLastModifiedFactor ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:LastModified ¤ÎÆüÉդ˴ð¤Å¤¤¤ÆÍ­¸ú´ü¸Â (expiry) +¤ò·×»»¤¹¤ë¤¿¤á¤Î½Å¤ß¤ò»ØÄꤹ¤ë +
¹½Ê¸:CacheLastModifiedFactor float
¥Ç¥Õ¥©¥ë¥È:CacheLastModifiedFactor 0.1
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

¥É¥­¥å¥á¥ó¥È¤Ë Last-Modified ¤ÎÆüÉÕ¤¬Ìµ¤¤¤±¤ì¤É¤âÍ­¸ú´ü¸Â (expiry) + ¤ÎÆüÉÕ¤¬¤¢¤ë¤È¤¤¤¦¤È¤­¤Ë¡¢Í­¸ú´ü¸Â¤òºÇ½ª½¤Àµ»þ¹ï¤«¤é¤Î·Ð²á»þ´Ö¤È¤·¤Æ + ·×»»¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£Í­¸ú´ü¸Â¤ò¼¡¤Î·×»»¼°¤Ë½¾¤Ã¤ÆÀ¸À®¤¹¤ë¤Î¤Ç¤¹¤¬¡¢ + ¤½¤Î¤È¤­¤Ë»È¤ï¤ì¤ë factor ¤ò + CacheLastModifiedFactor ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤷ¤Þ¤¹¡£ +

+ +

expiry-period = time-since-last-modified-date * factor + expiry-date = current-date + expiry-period

+ +

Î㤨¤Ð¡¢¥É¥­¥å¥á¥ó¥È¤¬ 10 »þ´ÖÁ°¤ËºÇ¸å¤Ë½¤Àµ¤µ¤ì¤Æ¤¤¤Æ¡¢ + factor ¤¬ 0.1 ¤Ç¤¢¤ì¤Ð¡¢´üÆü¤Ï 10*0.1 = 1 »þ´Ö¤Ë + ÀßÄꤵ¤ì¤Þ¤¹¡£¸½ºß»þ¹ï¤¬ 3:00pm ¤Ç¤¢¤ì¤Ð¡¢·×»»¤µ¤ì¤¿´üÆü¤Ï + 3:00pm + 1hour = 4:00pm ¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

´üÆü¤¬ CacheMaxExpire ¤ÇÀßÄꤵ¤ì¤Æ¤¤¤ëÃÍ + ¤è¤êÂ礭¤¯¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢CacheMaxExpire + ¤ÎÀßÄêÃͤ¬Í¥À褵¤ì¤Þ¤¹¡£

+ +

+ CacheLastModifiedFactor 0.5 +

+ +
+
top
+

CacheMaxExpire ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥É¥­¥å¥á¥ó¥È¤ò¥­¥ã¥Ã¥·¥å¤¹¤ëºÇÂç»þ´Ö¤òÉÿô¤Ç¸½¤·¤¿¤â¤Î
¹½Ê¸:CacheMaxExpire seconds
¥Ç¥Õ¥©¥ë¥È:CacheMaxExpire 86400 (°ìÆü)
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

CacheMaxExpire ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥­¥ã¥Ã¥·¥å¤¹¤ë HTTP ¥É¥­¥å¥á¥ó¥È¤ò¡¢¸µ¤Î¥µ¡¼¥Ð¤ËÌ䤤¹ç¤ï¤»¤Ê¤¤¤Þ¤ÞºÇÂ粿Éà + ÊÝ»ý¤·¤Æ¤â¤è¤¤¤«¤ò»ØÄꤷ¤Þ¤¹¡£¤Ä¤Þ¤ê¡¢¥É¥­¥å¥á¥ó¥È¤ÏºÇÂç¤Ç¤³¤ÎÉÿô´Ö¤Ö¤ó¸Å¤¯ + ¤Ê¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤ÎºÇÂçÃͤϡ¢(ÌõÃí:¥ì¥¹¥Ý¥ó¥¹Ãæ¤Ç)¥É¥­¥å¥á¥ó¥È¤È¶¦¤Ë + ¥É¥­¥å¥á¥ó¥È¤Î´üÆü¤¬Ä󶡤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ç¤âŬÍѤµ¤ì¤Þ¤¹¡£

+ +

+ CacheMaxExpire 604800 +

+ +
+
top
+

CacheStoreNoStore ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:no-store ¤È»ØÄꤵ¤ì¤Æ¤¤¤ë¥ì¥¹¥Ý¥ó¥¹¤Î¥­¥ã¥Ã¥·¥å¤ò»î¤ß¤ë¡£
¹½Ê¸:CacheStoreNoStore On|Off
¥Ç¥Õ¥©¥ë¥È:CacheStoreNoStore Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

Ä̾ï Cache-Control: no-store ¥Ø¥Ã¥À¤Î¤Ä¤¤¤Æ¤¤¤ë¥ì¥¹¥Ý¥ó¥¹¤Ï + ¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£CacheStoreNoCache + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤³¤ÎµóÆ°¤ò¾å½ñ¤­¤Ç¤­¤Þ¤¹¡£ + CacheStoreNoCache On ¤Ç no-store ¥Ø¥Ã¥À¤Î¤Ä¤¤¤Æ¤¤¤ë + ¥ê¥½¡¼¥¹¤ËÂФ·¤Æ¤â¥­¥ã¥Ã¥·¥å¤ò»î¤ß¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤¿¤À¤·Ç§¾Ú¤Îµá¤á¤é¤ì¤ë¥ê¥½¡¼¥¹¤Ï ·è¤·¤Æ ¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£

+ +

+ CacheStoreNoStore On +

+ +

·Ù¹ð:

+ RFC 2616 ¤Ëµ­ºÜ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë no-store ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + "ÉÔÃí°Õ¤Ë¤è¤ëµ¡Ì©¾ðÊó¤Îϳ±Ì¤ä»Äα (¥Ð¥Ã¥¯¥¢¥Ã¥×¥Æ¡¼¥×Åù) ¤òËɤ°" + ÌÜŪ¤Ç»È¤ï¤ì¤Þ¤¹¤¬¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤òÍ­¸ú¤Ë¤¹¤ë¤È¡¢ + µ¡Ì©¾ðÊó¤òÊÝ»ý¤¹¤ë¤³¤È¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£ + ¤Ç¤¹¤Î¤Ç¡¢¤³¤³¤Ç·Ù¹ð¤·¤Æ¤ª¤­¤Þ¤¹¡£ +
+ +

»²¾È

+ +
+
top
+

CacheStorePrivate ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:private ¤È»ØÄꤵ¤ì¤Æ¤¤¤ë¥ì¥¹¥Ý¥ó¥¹¤Î¥­¥ã¥Ã¥·¥å¤ò»î¤ß¤ë¡£
¹½Ê¸:CacheStorePrivate On|Off
¥Ç¥Õ¥©¥ë¥È:CacheStorePrivate Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_cache
+

Ä̾ï Cache-Control: private ¥Ø¥Ã¥À¤Î¤Ä¤¤¤Æ¤¤¤ë¥ì¥¹¥Ý¥ó¥¹¤Ï + ¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£CacheStorePrivate + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤³¤ÎµóÆ°¤ò¾å½ñ¤­¤Ç¤­¤Þ¤¹¡£ + CacheStorePrivate On ¤Ç private ¥Ø¥Ã¥À¤Î¤Ä¤¤¤Æ¤¤¤ë + ¥ê¥½¡¼¥¹¤ËÂФ·¤Æ¤â¥­¥ã¥Ã¥·¥å¤ò»î¤ß¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤¿¤À¤·Ç§¾Ú¤Îµá¤á¤é¤ì¤ë¥ê¥½¡¼¥¹¤Ï ·è¤·¤Æ ¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£

+ +

+ CacheStorePrivate On +

+ +

·Ù¹ð:

+ ¾åή¥µ¡¼¥Ð¤¬¥­¥ã¥Ã¥·¥å¤·¤Ê¤¤¤è¤¦¤Ë»ØÄꤷ¤Æ¤­¤Æ¤â¡¢ + ¤½¤ì¤ò̵»ë¤·¤Æ¥­¥ã¥Ã¥·¥å¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ˾¤Þ¤·¤¤µóÆ°¤Ë¤Ê¤ë¤Î¤Ï¡¢ËÜÅö¤Ë 'private' ¤Ê¥­¥ã¥Ã¥·¥å¤Ë¤Ä¤¤¤Æ¤Î¤ß¤Ç¤·¤ç¤¦¡£ +
+ +

»²¾È

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cache.html.ko.euc-kr b/docs/manual/mod/mod_cache.html.ko.euc-kr new file mode 100644 index 00000000..e372806d --- /dev/null +++ b/docs/manual/mod/mod_cache.html.ko.euc-kr @@ -0,0 +1,347 @@ + + + +mod_cache - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_cache

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:URI¸¦ Å°·Î »ç¿ëÇÏ¿© ³»¿ëÀ» ij½¬ÇÑ´Ù.
»óÅÂ:Experimental
¸ðµâ¸í:cache_module
¼Ò½ºÆÄÀÏ:mod_cache.c
+

¿ä¾à

+ +
+ ÀÌ ¸ðµâÀº ½ÇÇèÀûÀÎ »óÅÂÀÌ´Ù. ¹®¼­´Â ¾ÆÁ÷ ÀÛ¾÷ÁßÀÌ´Ù... +
+ +

mod_cache´Â °°Àº ÄÄÇ»ÅÍ¿¡ ÀÖ´Â ³»¿ëÀ̳ª + ÇÁ·Ï½ÃµÈ ³»¿ëÀ» ij½¬ÇÒ ¼ö ÀÖ´Â RFC 2616 + ȣȯ HTTP ³»¿ëij½¬¸¦ ±¸ÇöÇÑ´Ù. mod_cache¸¦ + »ç¿ëÇÏ·Á¸é ÀúÀå°ü¸®¸ðµâ(storage management module)ÀÌ ÇÊ¿äÇÏ´Ù. + ±âº» ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡´Â µÎ°¡Áö ÀúÀå°ü¸®¸ðµâÀÌ ÀÖ´Ù:

+
+
mod_disk_cache
+
´Â µð½ºÅ©±â¹Ý ÀúÀå°ü¸®ÀÚ¸¦ ±¸ÇöÇÑ´Ù.
+ +
mod_mem_cache
+
´Â ¸Þ¸ð¸®±â¹Ý ÀúÀå°ü¸®ÀÚ¸¦ ±¸ÇöÇÑ´Ù. + mod_mem_cache´Â ÆÄÀϱâ¼úÀÚ¸¦ ij½¬Çϰųª + Èü(heap) °ø°£¿¡ °´Ã¼¸¦ ij½¬ÇÏ´Â µÎ°¡Áö ¹æ½ÄÁß ÇÑ°¡Áö ¹æ¹ýÀ¸·Î + µ¿ÀÛÇϵµ·Ï ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. mod_mem_cache´Â + ÀÚ½ÅÀÌ »ý¼ºÇÑ ³»¿ëÀ» ij½¬Çϰųª, (¿ªÇÁ·Ï½Ã(reverse proxy)·Î + ¾Ë·ÁÁø) ProxyPass¸¦ + »ç¿ëÇÏ¿© mod_proxy¸¦ À§ÇØ µÞ´Ü ¼­¹ö³»¿ëÀ» + ij½¬ÇÒ ¼ö ÀÖ´Ù.
+
+ +

³»¿ëÀ» URI¸¦ Åä´ë·Î ¸¸µç Å°·Î ij½¬¿¡ ÀúÀåÇÏ°í °¡Á®¿Â´Ù. + Á¢±Ùº¸È£°¡ µÈ ³»¿ëÀº ij½¬ÇÏÁö¾Ê´Â´Ù.

+
+ +
top
+
+

°ü·ÃµÈ ¸ðµâ°ú Áö½Ã¾î

+
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+
top
+
+

¼³Á¤¿¹

+

Sample httpd.conf

+ #
+ # ¿¹Á¦ ij½¬ ¼³Á¤
+ #
+ LoadModule cache_module modules/mod_cache.so
+
+ <IfModule mod_cache.c>
+ + #LoadModule disk_cache_module modules/mod_disk_cache.so
+ <IfModule mod_disk_cache.c>
+ + CacheRoot c:/cacheroot
+ CacheSize 256
+ CacheEnable disk /
+ CacheDirLevels 5
+ CacheDirLength 3
+ + </IfModule>
+
+ LoadModule mem_cache_module modules/mod_mem_cache.so
+ <IfModule mod_mem_cache.c>
+ + CacheEnable mem /
+ MCacheSize 4096
+ MCacheMaxObjectCount 100
+ MCacheMinObjectSize 1
+ MCacheMaxObjectSize 2048
+ + </IfModule>
+ + </IfModule> +

+
+
top
+

CacheDefaultExpire Áö½Ã¾î

+ + + + + + + +
¼³¸í:¸¸±â½Ã°£À» ÁöÁ¤ÇÏÁö¾ÊÀº ¹®¼­¸¦ ij½¬ÇÒ ±âº» ±â°£.
¹®¹ý:CacheDefaultExpire seconds
±âº»°ª:CacheDefaultExpire 3600 (one hour)
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_cache
+

CacheDefaultExpire Áö½Ã¾î´Â ¹®¼­ÀÇ + ¸¸±â½Ã°£°ú ÃÖ±Ù¼öÁ¤½Ã°£ÀÌ ¾ø´Â °æ¿ì ¹®¼­¸¦ ij½¬ÇÒ ÃÊ´ÜÀ§ + ±âº» ½Ã°£À» ÁöÁ¤ÇÑ´Ù. CacheMaxExpire·Î + ÁöÁ¤ÇÑ °ªÀÌ ÀÌ ¼³Á¤À» ¹«½ÃÇÏÁö ¾Ê´Â´Ù.

+ +

+ CacheDefaultExpire 86400 +

+ +
+
top
+

CacheDisable Áö½Ã¾î

+ + + + + + +
¼³¸í:ƯÁ¤ URLÀ» ij½¬ÇÏÁö ¾Ê´Â´Ù
¹®¹ý:CacheDisable url-string
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_cache
+

CacheDisable Áö½Ã¾î¸¦ »ç¿ëÇϸé + mod_cache°¡ url-string ÀÌÇÏÀÇ + urlµéÀ» ij½¬ÇÏÁö ¾Ê´Â´Ù.

+ +

¿¹Á¦

+ CacheDisable /local_files +

+ +
+
top
+

CacheEnable Áö½Ã¾î

+ + + + + + +
¼³¸í:ÁöÁ¤ÇÑ ÀúÀå°ü¸®ÀÚ¸¦ »ç¿ëÇÏ¿© ÁöÁ¤ÇÑ URLÀ» ij½¬ÇÑ´Ù
¹®¹ý:CacheEnable cache_type url-string
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_cache
+

CacheEnable Áö½Ã¾î¸¦ »ç¿ëÇϸé + mod_cache°¡ url-string ÀÌÇÏ + urlµéÀ» ij½¬ÇÑ´Ù. ij½¬ ÀúÀå°ü¸®ÀÚ´Â cache_type + ¾Æ±Ô¸ÕÆ®·Î ÁöÁ¤ÇÑ´Ù. cache_type memÀº + mod_mem_cache°¡ ±¸ÇöÇÏ´Â ¸Þ¸ð¸®±â¹Ý + ÀúÀå°ü¸®ÀÚ¸¦ »ç¿ëÇÑ´Ù. cache_type disk´Â + mod_disk_cache°¡ ±¸ÇöÇÏ´Â µð½ºÅ©±â¹Ý + ÀúÀå°ü¸®ÀÚ¸¦ »ç¿ëÇÑ´Ù. cache_type fd´Â + mod_mem_cache°¡ ±¸ÇöÇÏ´Â ÆÄÀϱâ¼úÀÚ Ä³½¬¸¦ + »ç¿ëÇÑ´Ù.

+

(¾Æ·¡ ¿¹¿Í °°ÀÌ) URL °ø°£ÀÌ ´Ù¸¥ + CacheEnable Áö½Ã¾î¿Í °ãÄ¡¸é ½ÇÁ¦·Î + ÇÑ ÀúÀå°ü¸®ÀÚ°¡ ¿äûÀ» ó¸®ÇÒ¶§±îÁö µÎ ÀúÀå°ü¸®ÀÚ¸¦ ¸ðµÎ + ½ÇÇàÇÑ´Ù. ¼³Á¤ÆÄÀÏ¿¡¼­ CacheEnable + Áö½Ã¾îÀÇ ¼ø¼­´ë·Î ÀúÀå°ü¸®ÀÚ°¡ ½ÇÇàµÈ´Ù.

+ +

+ CacheEnable mem /manual
+ CacheEnable fd /images
+ CacheEnable disk /
+

+ +
+
top
+

CacheIgnoreCacheControl Áö½Ã¾î

+ + + + + + + +
¼³¸í:Ŭ¶óÀ̾ðÆ®°¡ ij½¬ÇÏÁö¾Ê´Â ³»¿ëÀ» ¿äûÇÔÀ» ¹«½ÃÇÑ´Ù.
¹®¹ý:CacheIgnoreCacheControl On|Off
±âº»°ª:CacheIgnoreCacheControl Off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_cache
+

º¸Åë no-cache³ª no-store Çì´õ°ªÀ» °¡Áø ¹®¼­´Â ij½¬¿¡ + ÀúÀåÇÏÁö¾Ê´Â´Ù. CacheIgnoreCacheControl + Áö½Ã¾î´Â ÀÌ·± ÇൿÀ» º¯°æÇÑ´Ù. + CacheIgnoreCacheControl OnÀ» »ç¿ëÇϸé + ¼­¹ö´Â ¹®¼­¿¡ no-cache³ª no-store Çì´õ°ªÀÌ À־ ¹®¼­¸¦ + ij½¬ÇÑ´Ù. ÀÎÁõÀÌ ÇÊ¿äÇÑ ¹®¼­´Â Àý´ë·Î ij½¬ÇÏÁö + ¾Ê´Â´Ù.

+ +

+ CacheIgnoreCacheControl On +

+ +
+
top
+

CacheIgnoreHeaders Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬¿¡ ÁöÁ¤ÇÑ HTTP Çì´õ(µé)¸¦ ÀúÀåÇÏÁö ¾Ê´Â´Ù +
¹®¹ý:CacheIgnoreHeaders header-string [header-string] ...
±âº»°ª:CacheIgnoreHeaders None
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_cache
+

RFC 2616¿¡ µû¸£¸é È©°£(hop-by-hop) HTTP Çì´õ´Â ij½¬¿¡ + ÀúÀåÇÏÁö ¾Ê´Â´Ù. È©°£ HTTP Çì´õ¿¡´Â ´ÙÀ½°ú °°Àº °ÍÀÌ ÀÖÀ¸¸ç, + CacheIgnoreHeaders ¼³Á¤°ú °ü°è¾øÀÌ + ¾î¶² °æ¿ì¿¡µµ ij½¬¿¡ ÀúÀåµÇÁö ¾Ê´Â´Ù.

+ +
    +
  • Connection
    • +
  • Keep-Alive
    • +
  • Proxy-Authenticate
    • +
  • Proxy-Authorization
    • +
  • TE
    • +
  • Trailers
    • +
  • Transfer-Encoding
    • +
  • Upgrade
    • +
+ +

CacheIgnoreHeaders´Â ij½¬¿¡ ÀúÀåÇϸé + ¾ÈµÇ´Â HTTP Çì´õ¸¦ Ãß°¡·Î ÁöÁ¤ÇÑ´Ù. ¿¹¸¦ µé¾î, ÄíÅ°(cookie)¸¦ + ij½¬¿¡ ÀúÀåÇÏ¸é ¾ÈµÇ´Â °æ¿ì°¡ ÀÖ´Ù.

+ +

CacheIgnoreHeaders´Â ij½¬¿¡ ÀúÀåÇÏÁö + ¾ÊÀ» HTTP Çì´õµéÀ» °ø¹éÀ¸·Î ±¸ºÐÇÑ ¸ñ·ÏÀ» ¹Þ´Â´Ù. (RFC 2616¿¡ + µû¶ó) ij½¬¿¡ È©°£ Çì´õ¸¸ ÀúÀåÇÏÁö ¾ÊÀ¸·Á¸é, + CacheIgnoreHeaders¸¦ + NoneÀ¸·Î ¼³Á¤ÇÑ´Ù.

+ +

¿¹Á¦ 1

+ CacheIgnoreHeaders Set-Cookie +

+ +

¿¹Á¦ 2

+ CacheIgnoreHeaders None +

+ +

°æ°í:

+ CacheIgnoreHeaders ¼³Á¤À» »ç¿ëÇÏ¿© + Expires °°ÀÌ Ä³½¬ °ü¸®¿¡ ÇÊ¿äÇÑ Çì´õ¸¦ ÀúÀåÇÏÁö + ¾ÊÀ¸¸é, mod_cache´Â ºñÁ¤»óÀûÀ¸·Î µ¿ÀÛÇÑ´Ù. +
+ +
+
top
+

CacheIgnoreNoLastMod Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÀÀ´ä¿¡ Last Modified Çì´õ°¡ ¾ø´Ù´Â »ç½ÇÀ» ¹«½ÃÇÑ´Ù.
¹®¹ý:CacheIgnoreNoLastMod On|Off
±âº»°ª:CacheIgnoreNoLastMod Off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_cache
+

º¸Åë ÃÖ±Ù¼öÁ¤ÀÏÀÌ ¾ø´Â ¹®¼­´Â ij½¬ÇÏÁö ¾Ê´Â´Ù. ¾î¶² °æ¿ì + ÃÖ±Ù¼öÁ¤ÀÏÀ» (¿¹¸¦ µé¾î mod_include ó¸®Áß¿¡) + »©°Å³ª óÀ½ºÎÅÍ ¾ø¾úÀ» ¼ö°¡ ÀÖ´Ù. + CacheIgnoreNoLastMod Áö½Ã¾î´Â ÃÖ±Ù¼öÁ¤ÀÏÀÌ + ¾ø´Â ¹®¼­µµ ¹Ýµå½Ã ij½¬Çϵµ·Ï ¸¸µç´Ù. ¹®¼­¿¡ ÃÖ±Ù¼öÁ¤ÀÏ°ú + ¸¸±â½Ã°£ÀÌ ¾ø´Â °æ¿ì CacheDefaultExpire + Áö½Ã¾î·Î ÁöÁ¤ÇÑ °ªÀ» ¸¸±â½Ã°£À¸·Î »ç¿ëÇÑ´Ù.

+ +

+ CacheIgnoreNoLastMod On +

+ +
+
top
+

CacheLastModifiedFactor Áö½Ã¾î

+ + + + + + + +
¼³¸í:LastModified ½Ã°£À¸·Î ¸¸±â½Ã°£À» °è»êÇϴµ¥ »ç¿ëÇÏ´Â +°è¼ö.
¹®¹ý:CacheLastModifiedFactor float
±âº»°ª:CacheLastModifiedFactor 0.1
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_cache
+

¹®¼­¿¡ ¸¸±â½Ã°£Àº ¾øÁö¸¸ ÃÖ±Ù¼öÁ¤ÀÏÀÌ ÀÖ´Â °æ¿ì ÃÖ±Ù¼öÁ¤ÀÏ + ÀÌÈÄ Áö³­ ½Ã°£À¸·Î ¸¸±â½Ã°£À» °è»êÇÑ´Ù. + CacheLastModifiedFactor Áö½Ã¾î´Â + ¸¸±â½Ã°£À» °è»êÇÏ´Â ´ÙÀ½ °ø½Ä¿¡¼­ »ç¿ëÇÒ factor¸¦ + ÁöÁ¤ÇÑ´Ù: + + expiry-period = time-since-last-modified-date * factor + expiry-date = current-date + expiry-period + + ¿¹¸¦ µé¾î, ¹®¼­°¡ 10 ½Ã°£ Àü¿¡ ¸¶Áö¸·À¸·Î ¼öÁ¤µÇ¾ú°í factor°¡ + 0.1À̶ó¸é ¸¸±â±â°£Àº 10*01 = 1 ½Ã°£ÀÌ µÈ´Ù. ÇöÀç ½Ã°£ÀÌ + 3:00pmÀ̶ó¸é ¸¸±â½Ã°£Àº 3:00pm + 1½Ã°£ = 4:00pmÀÌ´Ù. + + ¸¸±â±â°£ÀÌ CacheMaxExpire º¸´Ù ±æ´Ù¸é + CacheMaxExpire¸¦ »ç¿ëÇÑ´Ù.

+ +

+ CacheLastModifiedFactor 0.5 +

+ +
+
top
+

CacheMaxExpire Áö½Ã¾î

+ + + + + + + +
¼³¸í:¹®¼­¸¦ ij½¬ÇÏ´Â ÃÊ´ÜÀ§ ÃÖ´ë½Ã°£
¹®¹ý:CacheMaxExpire seconds
±âº»°ª:CacheMaxExpire 86400 (ÇÏ·ç)
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_cache
+

CacheMaxExpire Áö½Ã¾î´Â ½ÇÁ¦ ¼­¹ö¸¦ + °Ë»çÇÏÁö¾Ê°í ij½¬°¡´ÉÇÑ HTTP ¹®¼­¸¦ À¯ÁöÇÒ ¼ö ÀÖ´Â ÃÊ´ÜÀ§ + ÃÖ´ë½Ã°£À» ÁöÁ¤ÇÑ´Ù. Áï, ¹®¼­´Â ÃÖ´ëÇÑ ÀÌ ¼³Á¤°ª¸¸Å­ ¿À·¡µÇ¾ú´Ù. + ¹®¼­°¡ ¸¸±â½Ã°£À» ÁöÁ¤ÇÏ¿©µµ ÀÌ ÃÖ´ë°ªÀ» ÁöŲ´Ù.

+ +

+ CacheMaxExpire 604800 +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cern_meta.html b/docs/manual/mod/mod_cern_meta.html new file mode 100644 index 00000000..a0a4d49c --- /dev/null +++ b/docs/manual/mod/mod_cern_meta.html @@ -0,0 +1,7 @@ +URI: mod_cern_meta.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_cern_meta.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_cern_meta.html.en b/docs/manual/mod/mod_cern_meta.html.en new file mode 100644 index 00000000..8240c6b6 --- /dev/null +++ b/docs/manual/mod/mod_cern_meta.html.en @@ -0,0 +1,128 @@ + + + +mod_cern_meta - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_cern_meta

+
+

Available Languages:  en  | + ko 

+
+ + + +
Description:CERN httpd metafile semantics
Status:Extension
Module Identifier:cern_meta_module
Source File:mod_cern_meta.c
+

Summary

+ +

Emulate the CERN HTTPD Meta file semantics. Meta files are HTTP + headers that can be output in addition to the normal range of + headers for each file accessed. They appear rather like the + Apache .asis files, and are able to provide a crude way of + influencing the Expires: header, as well as providing other + curiosities. There are many ways to manage meta information, + this one was chosen because there is already a large number of + CERN users who can exploit this module.

+ +

More information on the CERN metafile semantics is available.

+
+

Directives

+ +

See also

+
+ +
top
+

MetaDir Directive

+ + + + + + + + +
Description:Name of the directory to find CERN-style meta information +files
Syntax:MetaDir directory
Default:MetaDir .web
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Extension
Module:mod_cern_meta
+

Specifies the name of the directory in which Apache can find + meta information files. The directory is usually a 'hidden' + subdirectory of the directory that contains the file being + accessed. Set to "." to look in the same directory + as the file:

+ +

MetaDir .

+ +

Or, to set it to a subdirectory of the directory containing the + files:

+ +

MetaDir .meta

+ +
+
top
+

MetaFiles Directive

+ + + + + + + + +
Description:Activates CERN meta-file processing
Syntax:MetaFiles on|off
Default:MetaFiles off
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Extension
Module:mod_cern_meta
+

Turns on/off Meta file processing on a per-directory basis.

+ +
+
top
+

MetaSuffix Directive

+ + + + + + + + +
Description:File name suffix for the file containg CERN-style +meta information
Syntax:MetaSuffix suffix
Default:MetaSuffix .meta
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Extension
Module:mod_cern_meta
+

Specifies the file name suffix for the file containing the + meta information. For example, the default values for the two + directives will cause a request to + DOCUMENT_ROOT/somedir/index.html to look in + DOCUMENT_ROOT/somedir/.web/index.html.meta and + will use its contents to generate additional MIME header + information.

+ +

Example:

+ MetaSuffix .meta +

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cern_meta.html.ko.euc-kr b/docs/manual/mod/mod_cern_meta.html.ko.euc-kr new file mode 100644 index 00000000..4b3bbc97 --- /dev/null +++ b/docs/manual/mod/mod_cern_meta.html.ko.euc-kr @@ -0,0 +1,120 @@ + + + +mod_cern_meta - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_cern_meta

+
+

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

+
+ + + +
¼³¸í:CERN À¥¼­¹ö ¸ÞŸÆÄÀÏ Áö¿ø
»óÅÂ:Extension
¸ðµâ¸í:cern_meta_module
¼Ò½ºÆÄÀÏ:mod_cern_meta.c
+

¿ä¾à

+ +

CERN À¥¼­¹ö ¸ÞŸÆÄÀÏÀ» Èä³»³½´Ù. ¸ÞŸÆÄÀÏÀº Á¢±ÙÇÏ´Â + ÆÄÀÏ¿¡ ´ëÇØ ÀϹÝÀûÀÎ Çì´õ¿Ü¿¡ Ãß°¡·Î Ãâ·ÂÇÒ HTTP Çì´õ¸¦ + ´ã°íÀÖ´Ù. ¾ÆÆÄÄ¡ .asis ÆÄÀÏ°ú ºñ½ÁÇÏ°í, Expires: Çì´õ¸¦ + ¼öÁ¤Çϰųª ´Ù¸¥ ½Å±âÇÑ ÀϵéÀ» ÇÒ ¼ö ÀÖ´Ù. ¸ÞŸ Á¤º¸¸¦ ´Ù·ç´Â + ¹æ¹ýÀº ´Ù¾çÇÏÁö¸¸, ÀÌ¹Ì ÀÌ ¸ðµâÀ» »ç¿ëÇÏ´Â ¸¹Àº CERN »ç¿ëÀÚµéÀ» + À§ÇØ ÀÌ ¹æ¹ýÀ» ¼±ÅÃÇß´Ù.

+ +

´õ ÀÚ¼¼ÇÑ Á¤º¸´Â CERN metafile semantics¸¦ Âü°íÇ϶ó.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

MetaDir Áö½Ã¾î

+ + + + + + + + +
¼³¸í:CERN ¸ÞŸÁ¤º¸¸¦ ãÀ» µð·ºÅ丮 À̸§
¹®¹ý:MetaDir directory
±âº»°ª:MetaDir .web
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Extension
¸ðµâ:mod_cern_meta
+

¾ÆÆÄÄ¡°¡ ¸ÞŸÁ¤º¸ ÆÄÀÏÀ» ãÀ» µð·ºÅ丮¸íÀ» ÁöÁ¤ÇÑ´Ù. + µð·ºÅ丮´Â º¸Åë Á¢±ÙÇÒ ÆÄÀÏÀÌ ÀÖ´Â µð·ºÅ丮ÀÇ '°¨ÃçÁø' + ÇÏÀ§µð·ºÅ丮´Ù. "."À¸·Î ÁöÁ¤ÇÏ¸é °°Àº µð·ºÅ丮¿¡¼­ + ÆÄÀÏÀ» ã´Â´Ù:

+ +

MetaDir .

+ +

¾Æ´Ï¸é ÆÄÀÏÀÌ ÀÖ´Â ÇÏÀ§µð·ºÅ丮¸¦ ÁöÁ¤ÇÑ´Ù:

+ +

MetaDir .meta

+ +
+
top
+

MetaFiles Áö½Ã¾î

+ + + + + + + + +
¼³¸í:CERN ¸ÞŸÆÄÀÏÀ» ó¸®ÇÑ´Ù
¹®¹ý:MetaFiles on|off
±âº»°ª:MetaFiles off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Extension
¸ðµâ:mod_cern_meta
+

µð·ºÅ丮º°·Î ¸ÞŸÆÄÀÏ Ã³¸®¿©ºÎ¸¦ °áÁ¤ÇÑ´Ù.

+ +
+
top
+

MetaSuffix Áö½Ã¾î

+ + + + + + + + +
¼³¸í:CERN ¸ÞŸÁ¤º¸¸¦ ÀúÀåÇÏ´Â ÆÄÀÏÀÇ Á¢¹Ì»ç
¹®¹ý:MetaSuffix suffix
±âº»°ª:MetaSuffix .meta
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Extension
¸ðµâ:mod_cern_meta
+

¸ÞŸÁ¤º¸¸¦ ÀúÀåÇÏ´Â ÆÄÀÏÀÇ Á¢¹Ì»ç¸¦ ÁöÁ¤ÇÑ´Ù. ¿¹¸¦ µé¾î, + µÎ Áö½Ã¾îÀÇ ±âº»°ªÀ» »ç¿ëÇÒ °æ¿ì + DOCUMENT_ROOT/somedir/index.htmlÀ» ¿äûÇϸé + DOCUMENT_ROOT/somedir/.web/index.html.metaÀÇ + ³»¿ëÀ» Âü°íÇÏ¿© MIME Çì´õ Á¤º¸¸¦ Ãß°¡ÇÑ´Ù.

+ +

¿¹Á¦:

+ MetaSuffix .meta +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cgi.html b/docs/manual/mod/mod_cgi.html new file mode 100644 index 00000000..7970a36c --- /dev/null +++ b/docs/manual/mod/mod_cgi.html @@ -0,0 +1,11 @@ +URI: mod_cgi.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_cgi.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_cgi.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_cgi.html.en b/docs/manual/mod/mod_cgi.html.en new file mode 100644 index 00000000..f51f5964 --- /dev/null +++ b/docs/manual/mod/mod_cgi.html.en @@ -0,0 +1,247 @@ + + + +mod_cgi - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_cgi

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Execution of CGI scripts
Status:Base
Module Identifier:cgi_module
Source File:mod_cgi.c
+

Summary

+ + + +

Any file that has the mime type + application/x-httpd-cgi or handler + cgi-script (Apache 1.1 or later) will be treated + as a CGI script, and run by the server, with its output being + returned to the client. Files acquire this type either by + having a name containing an extension defined by the + AddType directive, or by being + in a ScriptAlias + directory.

+ +

When the server invokes a CGI script, it will add a variable + called DOCUMENT_ROOT to the environment. This + variable will contain the value of the + DocumentRoot configuration + variable.

+ +

For an introduction to using CGI scripts with Apache, see + our tutorial on Dynamic Content + With CGI.

+ +

When using a multi-threaded MPM under unix, the module + mod_cgid should be used in place of + this module. At the user level, the two modules are essentially + identical.

+
+ +
top
+
+

CGI Environment variables

+

The server will set the CGI environment variables as described + in the CGI + specification, with the following provisions:

+ +
+
PATH_INFO
+ +
This will not be available if the AcceptPathInfo directive is explicitly set to + off. The default behavior, if AcceptPathInfo is not given, is that mod_cgi will accept path info (trailing + /more/path/info following the script filename in the URI), + while the core server will return a 404 NOT FOUND error for requests + with additional path info. Omitting the AcceptPathInfo directive has the same effect as setting + it On for mod_cgi requests.
+ +
REMOTE_HOST
+ +
This will only be set if HostnameLookups is set to on (it + is off by default), and if a reverse DNS lookup of the accessing + host's address indeed finds a host name.
+ +
REMOTE_IDENT
+ +
This will only be set if IdentityCheck is set to + on and the accessing host supports the ident + protocol. Note that the contents of this variable cannot be + relied upon because it can easily be faked, and if there is a + proxy between the client and the server, it is usually + totally useless.
+ +
REMOTE_USER
+ +
This will only be set if the CGI script is subject to + authentication.
+
+
top
+
+

CGI Debugging

+

Debugging CGI scripts has traditionally been difficult, mainly + because it has not been possible to study the output (standard + output and error) for scripts which are failing to run + properly. These directives, included in Apache 1.2 and later, + provide more detailed logging of errors when they occur.

+ +

CGI Logfile Format

+

When configured, the CGI error log logs any CGI which does not + execute properly. Each CGI script which fails to operate causes + several lines of information to be logged. The first two lines + are always of the format:

+ +

+ %% [time] request-line
+ %% HTTP-status CGI-script-filename +

+ +

If the error is that CGI script cannot be run, the log file + will contain an extra two lines:

+ +

+ %%error
+ error-message +

+ +

Alternatively, if the error is the result of the script + returning incorrect header information (often due to a bug in + the script), the following information is logged:

+ +

+ %request
+ All HTTP request headers received
+ POST or PUT entity (if any)
+ %response
+ All headers output by the CGI script
+ %stdout
+ CGI standard output
+ %stderr
+ CGI standard error
+

+ +

(The %stdout and %stderr parts may be missing if the script did + not output anything on standard output or standard error).

+ +
+
top
+

ScriptLog Directive

+ + + + + + +
Description:Location of the CGI script error logfile
Syntax:ScriptLog file-path
Context:server config, virtual host
Status:Base
Module:mod_cgi, mod_cgid
+

The ScriptLog directive sets the CGI + script error logfile. If no ScriptLog is given, + no error log is created. If given, any CGI errors are logged into the + filename given as argument. If this is a relative file or path it is + taken relative to the ServerRoot. +

+ +

Example

+ ScriptLog logs/cgi_log +

+ +

This log will be opened as the user the child processes run + as, i.e. the user specified in the main User directive. This means that + either the directory the script log is in needs to be writable + by that user or the file needs to be manually created and set + to be writable by that user. If you place the script log in + your main logs directory, do NOT change the + directory permissions to make it writable by the user the child + processes run as.

+ +

Note that script logging is meant to be a debugging feature + when writing CGI scripts, and is not meant to be activated + continuously on running servers. It is not optimized for speed + or efficiency, and may have security problems if used in a + manner other than that for which it was designed.

+ +
+
top
+

ScriptLogBuffer Directive

+ + + + + + + +
Description:Maximum amount of PUT or POST requests that will be recorded +in the scriptlog
Syntax:ScriptLogBuffer bytes
Default:ScriptLogBuffer 1024
Context:server config, virtual host
Status:Base
Module:mod_cgi, mod_cgid
+

The size of any PUT or POST entity body that is logged to + the file is limited, to prevent the log file growing too big + too quickly if large bodies are being received. By default, up + to 1024 bytes are logged, but this can be changed with this + directive.

+ +
+
top
+

ScriptLogLength Directive

+ + + + + + + +
Description:Size limit of the CGI script logfile
Syntax:ScriptLogLength bytes
Default:ScriptLogLength 10385760
Context:server config, virtual host
Status:Base
Module:mod_cgi, mod_cgid
+

ScriptLogLength can be used to limit the + size of the CGI script logfile. Since the logfile logs a lot of + information per CGI error (all request headers, all script output) + it can grow to be a big file. To prevent problems due to unbounded + growth, this directive can be used to set an maximum file-size for + the CGI logfile. If the file exceeds this size, no more + information will be written to it.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cgi.html.ja.euc-jp b/docs/manual/mod/mod_cgi.html.ja.euc-jp new file mode 100644 index 00000000..070a68fa --- /dev/null +++ b/docs/manual/mod/mod_cgi.html.ja.euc-jp @@ -0,0 +1,254 @@ + + + +mod_cgi - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_cgi

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:CGI ¥¹¥¯¥ê¥×¥È¤Î¼Â¹Ô
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:cgi_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_cgi.c
+

³µÍ×

+ + + +

Mime ¥¿¥¤¥×¤¬ application/x-httpd-cgi + ¤Ç¤¢¤ë¤«¡¢¥Ï¥ó¥É¥é cgi-script (Apache 1.1 °Ê¹ß) + ¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Ï CGI ¥¹¥¯¥ê¥×¥È¤È¤·¤Æ°·¤ï¤ì¡¢ + ¥µ¡¼¥Ð¤Ë¤è¤ê¼Â¹Ô¤µ¤ì¡¢¤½¤Î½ÐÎϤ¬¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤µ¤ì¤Þ¤¹¡£ + ¥Õ¥¡¥¤¥ë¤Ï¡¢AddType + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë»ØÄꤵ¤ì¤¿ ³ÈÄ¥»Ò¤ò̾Á°¤Ë´Þ¤à¤«¡¢ + ScriptAlias + ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¸ºß¤¹¤ë¤³¤È¤Ë¤è¤ê¤³¤Î¥¿¥¤¥×¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¥µ¡¼¥Ð¤¬ CGI ¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤¹¤ë¤È¤­¤Ë¤Ï¡¢ + DOCUMENT_ROOT + ¤È¸Æ¤Ð¤ì¤ëÊÑ¿ô¤ò´Ä¶­¤ËÄɲä·¤Þ¤¹¡£¤³¤ÎÊÑ¿ô¤Ï + DocumentRoot + ¤ÎÃͤòÊÝ»ý¤·¤Þ¤¹¡£

+ +

Apache ¤Ç CGI ¥¹¥¯¥ê¥×¥È¤ò»ÈÍѤ¹¤ë¤¿¤á¤Î¥¤¥ó¥È¥í¥À¥¯¥·¥ç¥ó¤Ï¡¢ + CGI ¤Ë¤è¤ëưŪ¥³¥ó¥Æ¥ó¥Ä + ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Unix ¤Ç¥Þ¥ë¥Á¥¹¥ì¥Ã¥É¤Î MPM ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢¤³¤Î¥â¥¸¥å¡¼¥ë¤Î + Âå¤ï¤ê¤Ë mod_cgid ¤ò»È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£ + ¥æ¡¼¥¶¥ì¥Ù¥ë¤Ç¤Ï¤³¤ÎÆó¤Ä¤Î¥â¥¸¥å¡¼¥ë¤ÏËܼÁŪ¤Ë¤ÏƱ°ì¤Ç¤¹¡£

+
+ +
top
+
+

CGI ´Ä¶­ÊÑ¿ô

+

¥µ¡¼¥Ð¤Ï CGI + µ¬³Ê ¤Ç·è¤á¤é¤ì¤Æ¤¤¤ë CGI + ´Ä¶­ÊÑ¿ô¤òÀßÄꤷ¤Þ¤¹¡£°Ê²¼¤Î¤â¤Î¤Ï¡¢¾ò·ïÉÕ¤­¤ÇÀßÄꤵ¤ì¤Þ¤¹¡£

+ +
+
PATH_INFO
+ +
¤³¤ì¤Ï AcceptPathInfo ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ÌÀ¼¨Åª¤Ë off + ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¤ÏÀßÄꤵ¤ì¤Þ¤»¤ó¡£¥Ç¥Õ¥©¥ë¥È¤Î¡¢ + AcceptPathInfo ¤¬ + »ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Î¿¶¤ëÉñ¤¤¤Ç¤Ï¡¢mod_cgi ¤Ï¥Ñ¥¹¾ðÊó + (URI ¤Î¥¹¥¯¥ê¥×¥È¤Î¥Õ¥¡¥¤¥ë̾¤Î¸å¤Ë³¤¯ /more/path/info) ¤ò + ¼õ¤±ÉÕ¤±¤Þ¤¹¤¬¡¢¥³¥¢¤Ï¥µ¡¼¥Ð¤Ï¥Ñ¥¹¾ðÊó¤Î¤¢¤ë¥ê¥¯¥¨¥¹¥È¤Ë + ÂФ·¤Æ 404 NOT FOUND ¥¨¥é¡¼¤òÊÖ¤·¤Þ¤¹¡£AcceptPathInfo + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ¾Êά¤¹¤ë¤È¡¢mod_cgi ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ + On ¤ò + ÀßÄꤷ¤¿¤Î¤ÈƱ¤¸¸ú²Ì¤Ë¤Ê¤ê¤Þ¤¹¡£
+ +
REMOTE_HOST
+ +
HostnameLookups + ¤¬ on (¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï off ¤Ç¤¹) + ¤Ç¡¢¥¢¥¯¥»¥¹¤·¤Æ¤¤¤ë¥Û¥¹¥È¤Î¥¢¥É¥ì¥¹¤Î DNS + ¤ÎµÕ°ú¤­¤¬¼ÂºÝ¤Ë¥Û¥¹¥È̾¤ò¸«¤Ä¤±¤¿¤È¤­¤Ë¤Î¤ßÀßÄꤵ¤ì¤Þ¤¹¡£
+ +
REMOTE_IDENT
+ +
IdentityCheck + ¤¬ on ¤ËÀßÄꤵ¤ì¤Æ¤¤¤Æ¡¢¥¢¥¯¥»¥¹¤·¤Æ¤¤¤ë¥Û¥¹¥È¤¬ + ident ¥×¥í¥È¥³¥ë¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤È¤­¤Ë¤Î¤ßÀßÄꤵ¤ì¤Þ¤¹¡£ + ¤³¤ì¤Ï´Êñ¤Ëµ¶¤ë¤³¤È¤¬¤Ç¤­¡¢¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¤Î´Ö¤Ë + ¥×¥í¥­¥·¤¬¤¢¤ì¤Ð¤Þ¤Ã¤¿¤¯Ìò¤ËΩ¤¿¤Ê¤¤¤Î¤Ç¡¢ + ¤³¤ÎÊÑ¿ô¤ÎÃͤϿ®ÍѤǤ­¤Ê¤¤¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ +
+ +
REMOTE_USER
+ +
CGI + ¥¹¥¯¥ê¥×¥È¤Ëǧ¾Ú¤¬É¬ÍפʤȤ­¤Ë¤Î¤ßÀßÄꤵ¤ì¤Þ¤¹¡£
+
+
top
+
+

CGI ¤Î¥Ç¥Ð¥Ã¥°

+

CGI ¥¹¥¯¥ê¥×¥È¤Î¥Ç¥Ð¥Ã¥°¤Ï¡¢Àµ¤·¤¯Æ°ºî¤·¤Æ¤¤¤Ê¤¤¥¹¥¯¥ê¥×¥È¤Î½ÐÎÏ + (ɸ½à½ÐÎϤȥ¨¥é¡¼) + ¤òÄ´¤Ù¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤¿¤á¤Ë¡¢Æñ¤·¤¤¾õÂÖ¤¬Â³¤¤¤Æ¤¤¤Þ¤·¤¿¡£ + ¤³¤ì¤é¤Î Apache 1.2 °Ê¹ß¤Ë¤¢¤ë + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤è¤ê¾ÜºÙ¤Ê¥¨¥é¡¼¤Î¥í¥°¼ý½¸¤òÄ󶡤·¤Þ¤¹¡£

+ +

CGI ¥í¥°¥Õ¥¡¥¤¥ë¤Î½ñ¼°

+

ÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¤­¤Ë¤Ï¡¢CGI ¥¨¥é¡¼¥í¥°¤ÏŬÀÚ¤ËÆ°ºî¤·¤Ê¤¤¤¹¤Ù¤Æ¤Î + CGI ¤ò¥í¥°¼ý½¸¤·¤Þ¤¹¡£¤½¤ì¤¾¤ì¤ÎÀµ¤·¤¯Æ°ºî¤·¤Ê¤¤ CGI + ¥¹¥¯¥ê¥×¥È¤Ï Ê£¿ô¤Î¹Ô¤Ë¤ï¤¿¤ë¾ðÊó¤¬¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹¡£ºÇ½é¤Î + 2 ¹Ô¤Ï¾ï¤Ë°Ê²¼¤Î½ñ¼°¤Ç¤¹:

+ +

+ %% [time] request-line
+ %% HTTP-status CGI-script-filename +

+ +

¥¨¥é¡¼¤¬¡¢CGI ¥¹¥¯¥ê¥×¥È¤¬¼Â¹Ô¤Ç¤­¤Ê¤¤¤È¤¤¤¦¤â¤Î¤Ç¤¢¤ë¾ì¹ç¤Ï¡¢ + ¥í¥°¥Õ¥¡¥¤¥ë¤Ï¤µ¤é¤Ë¤â¤¦ 2 ¹Ô½ñ¤«¤ì¤Þ¤¹:

+ +

+ %%error
+ error-message +

+ +

¤½¤¦¤Ç¤Ï¤Ê¤¯¡¢¥¨¥é¡¼¤¬Àµ¤·¤¯¤Ê¤¤¥Ø¥Ã¥À¾ðÊó¤òÊÖ¤¹·ë²Ì¤Ç¤¢¤ë¾ì¹ç + (¥¹¥¯¥ê¥×¥È¤Î¥Ð¥°¤Ç¤¢¤ë¤³¤È¤¬¤è¤¯¤¢¤ê¤Þ¤¹)¡¢ + °Ê²¼¤Î¾ðÊó¤¬¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹:

+ +

+ %request
+ ¼õ¤±¼è¤Ã¤¿¤¹¤Ù¤Æ¤Î HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À
+ (¤â¤·¤¢¤ì¤Ð) POST ¤ä PUT ¤ÎÃæ¿È
+ %response
+ CGI ¥¹¥¯¥ê¥×¥È¤Ë¤è¤ê½ÐÎϤµ¤ì¤¿¤¹¤Ù¤Æ¤Î¥Ø¥Ã¥À
+ %stdout
+ CGI ɸ½à½ÐÎÏ
+ %stderr
+ CGI ɸ½à¥¨¥é¡¼
+

+ +

(¥¹¥¯¥ê¥×¥È¤¬É¸½à½ÐÎϤäɸ½à¥¨¥é¡¼¤Ë²¿¤â½ÐÎϤ·¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï¡¢ + %stdout ¤ä %stderr ¤Ï¤¢¤ê¤Þ¤»¤ó)¡£

+ +
+
top
+

ScriptLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:CGI ¥¹¥¯¥ê¥×¥È¤Î¥¨¥é¡¼¥í¥°¥Õ¥¡¥¤¥ë¤Î¾ì½ê
¹½Ê¸:ScriptLog file-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_cgi, mod_cgid
+

ScriptLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï CGI ¥¹¥¯¥ê¥×¥È¤Î + ¥¨¥é¡¼¥í¥°¥Õ¥¡¥¤¥ë¤òÀßÄꤷ¤Þ¤¹¡£ScriptLog ¤¬ + ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ï¡¢ + ¥¨¥é¡¼¥í¥°¤ÏºîÀ®¤µ¤ì¤Þ¤»¤ó¡£ÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¤­¤Ï¡¢CGI + ¤Î¥¨¥é¡¼¤Ï¤¹¤Ù¤Æ°ú¿ô¤È¤·¤ÆÍ¿¤¨¤é¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë̾¤Ë¥í¥°¤µ¤ì¤Þ¤¹¡£ + ÁêÂХѥ¹¤Ç»ØÄꤵ¤ì¤Æ¤¤¤ë¤È¤­¤Ï¡¢ + ServerRoot¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ + °·¤ï¤ì¤Þ¤¹¡£

+ +

Îã

+ ScriptLog logs/cgi_log +

+ +

¤³¤Î¥í¥°¤Ï»Ò¥×¥í¥»¥¹¤¬¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¥æ¡¼¥¶¤È¤·¤Æ¥ª¡¼¥×¥ó¤µ¤ì¤Þ¤¹¡£ + ¤¹¤Ê¤ï¤Á¡¢User ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿ + ¥æ¡¼¥¶¤Ç¤¹¡£¤³¤ì¤Ï¡¢¥¹¥¯¥ê¥×¥È¥í¥°¤¬½ñ¤«¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¤¬¤½¤Î¥æ¡¼¥¶¤Ç + ½ñ¤­¹þ¤ß²Äǽ¤«¡¢¥¹¥¯¥ê¥×¥È¥Õ¥¡¥¤¥ë¤¬¼êÆ°¤ÇºîÀ®¤µ¤ì¡¢¤½¤Î¥æ¡¼¥¶¤Ç + ½ñ¤­¹þ¤ß²Äǽ¤Ë¤Ê¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£¥¹¥¯¥ê¥×¥È¥í¥°¤ò + ¥¢¥¯¥»¥¹¥í¥°¤Ê¤É¤Î¤¿¤á¤Î¥í¥°¥Ç¥£¥ì¥¯¥È¥ê¤Ë½ñ¤«¤ì¤ë¤è¤¦¤Ë¤·¤¿¤È¤­¤Ï¡¢ + ¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ò»Ò¥×¥í¥»¥¹¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¥æ¡¼¥¶¤Î¸¢¸Â¤Ç + ½ñ¤­¹þ¤ß²Äǽ¤Ë¤Ï¤·¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

¥¹¥¯¥ê¥×¥È¤Î¥í¥°¼ý½¸¤Ï CGI ¥¹¥¯¥ê¥×¥È¤ò½ñ¤¯¤È¤­¤Î + ¥Ç¥Ð¥Ã¥°ÍѤε¡Ç½¤È¤·¤Æ°Õ¿Þ¤µ¤ì¤Æ¤¤¤Æ¡¢Ä̾ï¤Î¥µ¡¼¥Ð¤Ç + ¾ï¤Ë»ÈÍѤµ¤ì¤ë¤è¤¦¤Ë¤Ï°Õ¿Þ¤µ¤ì¤Æ¤¤¤Ê¤¤¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ®ÅÙ¤ä¸úΨ¤ÏºÇŬ²½¤µ¤ì¤Æ¤ª¤é¤º¡¢À߷פµ¤ì¤¿°Ê³°¤ÎÊýË¡¤Ç»ÈÍѤµ¤ì¤ë¤È + ¥»¥­¥å¥ê¥Æ¥£¤ÎÌäÂ꤬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ +
+
top
+

ScriptLogBuffer ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¹¥¯¥ê¥×¥È¥í¥°¤Ëµ­Ï¿¤µ¤ì¤ë PUT ¤ä POST ¥ê¥¯¥¨¥¹¥È¤ÎÆâÍƤξå¸Â
¹½Ê¸:ScriptLogBuffer bytes
¥Ç¥Õ¥©¥ë¥È:ScriptLogBuffer 1024
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_cgi, mod_cgid
+

Â礭¤ÊËÜÂΤò¼õ¤±¼è¤Ã¤¿¤È¤­¤Ë¥í¥°¥Õ¥¡¥¤¥ë¤¬¤¹¤°¤ËÂ礭¤¯¤Ê¤ê¤¹¤®¤ë + ÌäÂê¤òÈò¤±¤ë¤¿¤á¤Ë¡¢¥Õ¥¡¥¤¥ë¤Ë¥í¥°¼ý½¸¤µ¤ì¤ë PUT ¤È POST + ¤ÎËÜÂΤÎÂ礭¤µ¤ÏÀ©¸Â¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢1024 + ¥Ð¥¤¥È¤Þ¤Ç¤¬¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹¤¬¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤½¤ì¤òÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +

+ +
+
top
+

ScriptLogLength ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:CGI ¥¹¥¯¥ê¥×¥È¤Î¥í¥°¥Õ¥¡¥¤¥ë¤ÎÂ礭¤µ¤Î¾å¸Â
¹½Ê¸:ScriptLogLength bytes
¥Ç¥Õ¥©¥ë¥È:ScriptLogLength 10385760
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_cgi, mod_cgid
+

ScriptLogLength ¤Ï CGI ¥¹¥¯¥ê¥×¥È¤Î¥í¥°¥Õ¥¡¥¤¥ë + ¤ÎÂ礭¤µ¤òÀ©¸Â¤¹¤ë¤¿¤á¤Ë»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¥í¥°¥Õ¥¡¥¤¥ë¤Ï + CGI ¤Î¥¨¥é¡¼Ëè¤ËÂçÎ̤ξðÊó (¥ê¥¯¥¨¥¹¥È¤Î¤¹¤Ù¤Æ¤Î¥Ø¥Ã¥À¡¢ + ¤¹¤Ù¤Æ¤Î½ÐÎÏ)¤ò¥í¥°¤·¤Þ¤¹¤Î¤Ç¡¢¤¹¤°¤ËÂ礭¤Ê¥Õ¥¡¥¤¥ë¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤ÎÂ礭¤µ¤ÎÀ©¸Â¤¬¤Ê¤¤¤³¤È¤Ë¤è¤ëÌäÂê¤òËɤ°¤¿¤á¤Ë¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ CGI ¤Î¥í¥°¥Õ¥¡¥¤¥ë¤Î + ºÇÂç¤Î¥Õ¥¡¥¤¥ë¥µ¥¤¥º¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥Õ¥¡¥¤¥ë¤¬¤³¤ÎÂ礭¤µ¤òĶ¤¨¤¿¾ì¹ç¤Ï¡¢¤½¤ì°Ê¾å¤Ï½ñ¤­¹þ¤Þ¤ì¤Þ¤»¤ó¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cgi.html.ko.euc-kr b/docs/manual/mod/mod_cgi.html.ko.euc-kr new file mode 100644 index 00000000..a642479a --- /dev/null +++ b/docs/manual/mod/mod_cgi.html.ko.euc-kr @@ -0,0 +1,234 @@ + + + +mod_cgi - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_cgi

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:CGI ½ºÅ©¸³Æ® ½ÇÇà
»óÅÂ:Base
¸ðµâ¸í:cgi_module
¼Ò½ºÆÄÀÏ:mod_cgi.c
+

¿ä¾à

+ + + +

¼­¹ö´Â mime typeÀÌ application/x-httpd-cgiÀ̰ųª + (¾ÆÆÄÄ¡ 1.1 ÀÌÈÄ) Çڵ鷯°¡ cgi-scriptÀÎ ¸ðµç + ÆÄÀÏÀ» CGI ½ºÅ©¸³Æ®·Î ÀνÄÇÏ¿©, ½ÇÇàÇÏ°í, ±× °á°ú¸¦ Ŭ¶óÀ̾ðÆ®¿¡°Ô + º¸³½´Ù. ÆÄÀÏÀÌ AddType + Áö½Ã¾î·Î ÁöÁ¤ÇÑ È®ÀåÀÚ¸¦ °¡Áö°Å³ª, ScriptAlias µð·ºÅ丮 ¾È¿¡ + ÀÖÀ¸¸é CGI·Î 󸮵ȴÙ.

+ +

¼­¹ö´Â CGI ½ºÅ©¸³Æ®¸¦ ºÎ¸¦¶§ DOCUMENT_ROOT¶ó´Â + ȯ°æº¯¼ö¸¦ Ãß°¡ÇÑ´Ù. ÀÌ º¯¼ö´Â DocumentRoot ¼³Á¤°ªÀ» °¡Áø´Ù.

+ +

¾ÆÆÄÄ¡¿¡¼­ CGI ½ºÅ©¸³Æ®¸¦ »ç¿ëÇÏ´Â ¹æ¹ý¿¡ ´ëÇÑ ¼Ò°³´Â + CGI·Î µ¿Àû ÆäÀÌÁö »ý¼º ÅõÅ丮¾óÀ» + Âü°íÇ϶ó.

+ +

À¯´Ð½º¿¡¼­ ´ÙÁß¾²·¹µå MPMÀ» »ç¿ëÇÑ´Ù¸é ÀÌ ¸ðµâ´ë½Å + mod_cgid ¸ðµâÀ» »ç¿ëÇØ¾ß ÇÑ´Ù. »ç¿ëÀÚ + ÀÔÀå¿¡¼­ ÀÌ µÎ ¸ðµâÀº ±âº»ÀûÀ¸·Î µ¿ÀÏÇÏ´Ù.

+
+ +
top
+
+

CGI ȯ°æº¯¼ö

+

¼­¹ö´Â ´ÙÀ½°ú °°Àº ¹æ¹ýÀ¸·Î CGI Ç¥ÁØÀÌ ¼³¸íÇÏ´Â + CGI ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù:

+ +
+
PATH_INFO
+ +
ÀÌ º¯¼ö´Â AcceptPathInfo Áö½Ã¾î¸¦ Á÷Á¢ off·Î + ÁöÁ¤ÇÑ °æ¿ì¿¡¸¸ ¼³Á¤ÇÑ´Ù. AcceptPathInfo°¡ ¾ø´Â °æ¿ì ¼­¹ö´Â ±âº»ÀûÀ¸·Î + °æ·Î Á¤º¸°¡ ÀÖ´Â ¿äû¿¡ ´ëÇØ 404 NOT FOUND ¿À·ù¸¦ ³»Áö¸¸, + mod_cgi´Â °æ·Î Á¤º¸¸¦ (URI¿¡¼­ ½ºÅ©¸³Æ® + ÆÄÀÏ¸í µÚ¿¡ ³ª¿À´Â /more/path/info) ¹Þ´Â´Ù. + AcceptPathInfo Áö½Ã¾î¸¦ »ý·«Çϸé + mod_cgi ¿äû¿¡ ´ëÇؼ­ AcceptPathInfo¸¦ OnÀ¸·Î + ¼³Á¤ÇÑ °Í°ú °°´Ù.
+ +
REMOTE_HOST
+ +
ÀÌ º¯¼ö´Â HostnameLookups°¡ onÀÌ°í (±âº»°ªÀº + off), Á¢¼ÓÇÑ È£½ºÆ® ÁÖ¼Ò¸¦ ¿ªDNS °Ë»öÇÏ¿© ½ÇÁ¦ È£½ºÆ®¸íÀ» + ãÀº °æ¿ì¿¡¸¸ ¼³Á¤ÇÑ´Ù.
+ +
REMOTE_IDENT
+ +
ÀÌ º¯¼ö´Â IdentityCheck°¡ onÀÌ°í, Á¢¼ÓÇÑ + È£½ºÆ®°¡ ident ÇÁ·ÎÅäÄÝÀ» Áö¿øÇÏ´Â °æ¿ì¿¡¸¸ ¼³Á¤ÇÑ´Ù. + ½±°Ô ÀÌ °ªÀ» ¼ÓÀÏ ¼ö Àֱ⶧¹®¿¡ ÀÌ º¯¼öÀÇ ³»¿ëÀ» ¹ÏÀ¸¸é + ¾ÈµÇ°í, Ŭ¶óÀ̾ðÆ®¿Í ¼­¹ö »çÀÌ¿¡ ÇÁ·Ï½Ã°¡ ÀÖ´Ù¸é º¯¼ö + ³»¿ëÀÌ ¿ÏÀüÈ÷ ¹«ÀǹÌÇÔÀ» ÁÖÀÇÇ϶ó.
+ +
REMOTE_USER
+ +
CGI ½ºÅ©¸³Æ®°¡ ÀÎÁõÀ» °ÅÃľßÇÏ´Â °æ¿ì¿¡¸¸ ¼³Á¤ÇÑ´Ù.
+
+
top
+
+

CGI µð¹ö±ë

+

¾îµð¿¡¼­ À߸ø ½ÇÇàµÇ´ÂÁö ½ºÅ©¸³Æ®ÀÇ Ãâ·ÂÀ» (Ç¥ÁØÃâ·Â°ú + Ç¥ÁØ¿À·ù) º¼ ¼ö ¾ø±â¶§¹®¿¡ CGI ½ºÅ©¸³Æ®´Â ÀüÅëÀûÀ¸·Î µð¹ö±ëÇϱâ + ¾î·Á¿ü´Ù. ¾ÆÆÄÄ¡ 1.2 ÀÌÈÄ¿¡ Ãß°¡µÈ Áö½Ã¾î¸¦ »ç¿ëÇÏ¸é ¹ß»ýÇÑ + ¿À·ù¸¦ ÀÚ¼¼È÷ ·Î±×¿¡ ³²±æ ¼ö ÀÖ´Ù.

+ +

CGI ·Î±×ÆÄÀÏ Çü½Ä

+

CGI ¿À·ù·Î±×´Â Á¤»óÀûÀ¸·Î ½ÇÇàÇÏÁö ¸øÇÑ CGI¸¦ ±â·ÏÇÑ´Ù. + ¿À·ù°¡ ¹ß»ýÇÑ CGI ½ºÅ©¸³Æ®´Â ·Î±×¿¡ ¿©·¯ ÁÙÀÇ Á¤º¸¸¦ ³²±ä´Ù. + ù¹ø° µÎ ÁÙÀº Ç×»ó ¾Æ·¡¿Í °°Àº Çü½ÄÀÌ´Ù:

+ +

+ %% [½Ã°£] ¿äûÁÙ
+ %% HTTP-»óÅ CGI-½ºÅ©¸³Æ®-ÆÄÀϸí +

+ +

CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÒ ¼ö ¾ø´Â ¿À·ùÀÎ °æ¿ì ·Î±×ÆÄÀÏ¿¡ + Ãß°¡·Î µÎ ÁÙÀ» ´õ ±â·ÏÇÑ´Ù:

+ +

+ %%error
+ ¿À·ù¹® +

+ +

½ºÅ©¸³Æ®°¡ (º¸Åë ½ºÅ©¸³Æ®ÀÇ ¹ö±×¶§¹®¿¡) À߸øµÈ Çì´õ + Á¤º¸¸¦ ¹ÝȯÇÏ´Â °æ¿ì, ´ÙÀ½ ³»¿ëÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù:

+ +

+ %request
+ ¹ÞÀº ¸ðµç HTTP Çì´õ
+ (ÀÖ´Ù¸é) POST³ª PUT ³»¿ë
+ %response
+ CGI ½ºÅ©¸³Æ® Ãâ·ÂÀÇ ¸ðµç Çì´õ
+ %stdout
+ CGI Ç¥ÁØÃâ·Â
+ %stderr
+ CGI Ç¥ÁØ¿À·ù
+

+ +

(½ºÅ©¸³Æ®°¡ Ç¥ÁØÃâ·ÂÀ̳ª Ç¥ÁØ¿À·ù¿¡ ¾Æ¹« ³»¿ëµµ Ãâ·ÂÇÏÁö + ¾Ê¾Ò´Ù¸é %stdout°ú %stderr ºÎºÐÀº »ý·«µÉ ¼ö ÀÖ´Ù).

+ +
+
top
+

ScriptLog Áö½Ã¾î

+ + + + + + +
¼³¸í:CGI ½ºÅ©¸³Æ® ¿À·ù·Î±×ÆÄÀÏÀÇ À§Ä¡
¹®¹ý:ScriptLog file-path
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_cgi, mod_cgid
+

ScriptLog Áö½Ã¾î´Â CGI ½ºÅ©¸³Æ® + ¿À·ù·Î±×ÆÄÀÏÀ» ÁöÁ¤ÇÑ´Ù. ScriptLog¸¦ + »ç¿ëÇÏÁö¾ÊÀ¸¸é ¿À·ù·Î±×¸¦ ¸¸µéÁö ¾Ê´Â´Ù. »ç¿ëÇÏ¸é ¾Æ±Ô¸ÕÆ®·Î + ÁöÁ¤ÇÑ ÆÄÀÏ¿¡ CGI ¿À·ù¸¦ ±â·ÏÇÑ´Ù. »ó´ë°æ·Î¸¦ ÁöÁ¤Çϸé + ServerRoot¿¡ »ó´ë°æ·Î·Î + ¹Þ¾ÆµéÀδÙ. +

+ +

¿¹Á¦

+ ScriptLog logs/cgi_log +

+ +

ÀÚ½Ä ÇÁ·Î¼¼½º¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚ, Áï User Áö½Ã¾î·Î ÁöÁ¤ÇÑ »ç¿ëÀÚ + ±ÇÇÑÀ¸·Î ·Î±×¸¦ ¿¬´Ù. ±×·¡¼­ ±× »ç¿ëÀÚ°¡ ½ºÅ©¸³Æ® ·Î±×°¡ + ÀÖ´Â µð·ºÅ丮¿¡ ¾²±â±ÇÇÑÀÌ ÀÖ´øÁö, Á÷Á¢ ¹Ì¸® ÆÄÀÏÀ» ¸¸µé¾î¼­ + ±× »ç¿ëÀÚ¿¡°Ô ¾²±â±ÇÇÑÀ» Áà¾ß ÇÑ´Ù. ½ºÅ©¸³Æ® ·Î±×¸¦ ÁÖ ·Î±× + µð·ºÅ丮¿¡ µÐ´Ù¸é ÀÚ½Ä ÇÁ·Î¼¼½º¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚ¿¡°Ô ¾²±â±ÇÇÑÀ» + ÁÖ±âÀ§ÇØ µð·ºÅ丮 ±ÇÇÑÀ» º¯°æÇÏÁö ¸¶¶ó.

+ +

½ºÅ©¸³Æ® ·Î±×´Â CGI ½ºÅ©¸³Æ®¸¦ ÀÛ¼ºÇÒ¶§ µð¹ö±ëÀ» À§ÇÑ + ¿ëµµÀÌÁö ¼­¹ö¸¦ ½ÇÇàÇÏ´Â µ¿¾È °è¼Ó »ç¿ëÇϱâÀ§ÇÔÀÌ ¾Æ´ÔÀ» + ÁÖÀÇÇ϶ó. ¼Óµµ¿Í È¿À²¼º¸é¿¡¼­ ÃÖÀûÈ­°¡ ¾ÈµÇÀÖ°í, ¼³°èÇÑ + ¸ñÀûÀÌ¿ÜÀÇ ¹æ¹ýÀ¸·Î »ç¿ëÇÏ¸é º¸¾È»ó ¹®Á¦°¡ µÉ ¼ö ÀÖ´Ù.

+ +
+
top
+

ScriptLogBuffer Áö½Ã¾î

+ + + + + + + +
¼³¸í:½ºÅ©¸³Æ® ·Î±×¿¡ ±â·ÏÇÒ PUT ȤÀº POST ¿äûÀÇ ÃÖ´ë·®
¹®¹ý:ScriptLogBuffer bytes
±âº»°ª:ScriptLogBuffer 1024
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_cgi, mod_cgid
+

Å« ³»¿ëÀ» ¹Þ¾Æ¼­ ·Î±×ÆÄÀÏÀÌ ³Ê¹« »¡¸® Ä¿Áö´Â Çö»óÀ» ¸·±âÀ§ÇØ + ÆÄÀÏ¿¡ ±â·ÏÇÒ PUT ȤÀº POST ³»¿ëÀÇ Å©±â¸¦ Á¦ÇÑÇÑ´Ù. ±âº»ÀûÀ¸·Î + 1024 ¹ÙÀÌÆ®±îÁö ·Î±×¿¡ ±â·ÏÇÏÁö¸¸, ÀÌ Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +
+
top
+

ScriptLogLength Áö½Ã¾î

+ + + + + + + +
¼³¸í:CGI ½ºÅ©¸³Æ® ·Î±×ÆÄÀÏÀÇ Å©±â Á¦ÇÑ
¹®¹ý:ScriptLogLength bytes
±âº»°ª:ScriptLogLength 10385760
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_cgi, mod_cgid
+

ScriptLogLength´Â CGI ½ºÅ©¸³Æ® + ·Î±×ÆÄÀÏÀÇ Å©±â¸¦ Á¦ÇÑÇÑ´Ù. CGI ¿À·ù°¡ ¹ß»ýÇÒ¶§¸¶´Ù (¸ðµç + ¿äû Çì´õ, ¸ðµç ½ºÅ©¸³Æ® Ãâ·Â µî) ¸¹Àº Á¤º¸°¡ ·Î±×¿¡ + ±â·ÏµÇ±â¶§¹®¿¡ ÆÄÀÏÀÌ ¸Å¿ì Ä¿Áú ¼ö ÀÖ´Ù. ÆÄÀÏÀÌ ¹«ÇÑÈ÷ Ä¿Áö´Â + ¹®Á¦¸¦ ¸·±âÀ§ÇØ ÀÌ Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© CGI ·Î±×ÆÄÀÏÀÇ ÃÖ´ë + ÆÄÀÏÅ©±â¸¦ ¼³Á¤ÇÑ´Ù. ÆÄÀÏÀÇ Å©±â°¡ ¼³Á¤ÇÑ °ªÀ» ³ÑÀ¸¸é ´õ + ÀÌ»ó Á¤º¸¸¦ ±â·ÏÇÏÁö¾Ê´Â´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cgid.html b/docs/manual/mod/mod_cgid.html new file mode 100644 index 00000000..f89ee3c7 --- /dev/null +++ b/docs/manual/mod/mod_cgid.html @@ -0,0 +1,11 @@ +URI: mod_cgid.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_cgid.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_cgid.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_cgid.html.en b/docs/manual/mod/mod_cgid.html.en new file mode 100644 index 00000000..f701f5e0 --- /dev/null +++ b/docs/manual/mod/mod_cgid.html.en @@ -0,0 +1,106 @@ + + + +mod_cgid - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_cgid

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Execution of CGI scripts using an + external CGI daemon
Status:Base
Module Identifier:cgid_module
Source File:mod_cgid.c
Compatibility:Unix threaded MPMs only
+

Summary

+ +

Except for the optimizations and the additional ScriptSock directive noted below, + mod_cgid behaves similarly to mod_cgi. + See the mod_cgi summary for additional details + about Apache and CGI.

+ +

On certain unix operating systems, forking a process from a + multi-threaded server is a very expensive operation because the + new process will replicate all the threads of the parent + process. In order to avoid incurring this expense on each CGI + invocation, mod_cgid creates an external daemon that is + responsible for forking child processes to run CGI scripts. The + main server communicates with this daemon using a unix domain + socket.

+ +

This module is used by default instead of + mod_cgi whenever a multi-threaded MPM + is selected during the compilation process. At the user level, + this module is identical in configuration and operation to + mod_cgi. The only exception is the + additional directive ScriptSock which gives the + name of the socket to use for communication with the cgi + daemon.

+
+ + +
top
+

ScriptSock Directive

+ + + + + + + +
Description:The filename prefix of the socket to use for communication with +the cgi daemon
Syntax:ScriptSock file-path
Default:ScriptSock logs/cgisock
Context:server config
Status:Base
Module:mod_cgid
+

This directive sets the filename prefix of the socket to use for + communication with the CGI daemon, an extension correspondening to + the process ID of the server will be appended. The socket will be opened + using the permissions of the user who starts Apache (usually + root). To maintain the security of communications with CGI + scripts, it is important that no other user has permission to + write in the directory where the socket is located.

+ +

Example

+ ScriptSock /var/run/cgid.sock +

+ + +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cgid.html.ja.euc-jp b/docs/manual/mod/mod_cgid.html.ja.euc-jp new file mode 100644 index 00000000..fc0a40d6 --- /dev/null +++ b/docs/manual/mod/mod_cgid.html.ja.euc-jp @@ -0,0 +1,100 @@ + + + +mod_cgid - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_cgid

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + + +
ÀâÌÀ:³°Éô CGI ¥Ç¡¼¥â¥ó¤ò»È¤Ã¤¿ CGI ¥¹¥¯¥ê¥×¥È¤Î¼Â¹Ô
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:cgid_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_cgid.c
¸ß´¹À­:Unix ¤Î¥¹¥ì¥Ã¥É MPM ¤Î¤ß
+

³µÍ×

+ +

ºÇŬ²½¤¬»Ü¤µ¤ì¤Æ¤¤¤ë¤³¤È¤È¡¢°Ê²¼¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ëÄɲäΠScriptSock ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ü¤¤¤Æ¤Ï¡¢ + mod_cgid ¤Ï mod_cgi ¤ÈƱÍͤΠ+ Æ°ºî¤ò¤·¤Þ¤¹¡£Apache ¤È CGI ¤Ë´Ø¤¹¤ë¾ÜºÙ¤Ï + mod_cgi ¤Î³µÍפòÆɤó¤Ç¤¯¤À¤µ¤¤¡£

+ +

Unix ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ÎÃæ¤Ë¤Ï¡¢¥Þ¥ë¥Á¥¹¥ì¥Ã¥É¤Î¥µ¡¼¥Ð¤«¤é + ¥×¥í¥»¥¹¤ò fork ¤¹¤ë¤Î¤¬Èó¾ï¤Ë¥³¥¹¥È¤Î¹â¤¤Æ°ºî¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£ + Íýͳ¤Ï¡¢¿·¤·¤¤¥×¥í¥»¥¹¤¬¿Æ¥×¥í¥»¥¹¤Î¥¹¥ì¥Ã¥É¤¹¤Ù¤Æ¤òÊ£À½¤¹¤ë¤«¤é¤Ç¤¹¡£ + ³Æ CGI µ¯Æ°»þ¤Ë¤³¤Î¥³¥¹¥È¤¬¤«¤«¤ë¤Î¤òËɤ°¤¿¤á¤Ë¡¢mod_cgid + ¤Ï»Ò¥×¥í¥»¥¹¤ò fork ¤·¤Æ CGI ¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤¹¤ë¤¿¤á¤Î + ³°Éô¥Ç¡¼¥â¥ó¤ò¼Â¹Ô¤·¤Þ¤¹¡£ + ¼ç¥µ¡¼¥Ð¤Ï unix ¥É¥á¥¤¥ó¥½¥±¥Ã¥È¤ò»È¤Ã¤Æ¤³¤Î¥Ç¡¼¥â¥ó¤ÈÄÌ¿®¤·¤Þ¤¹¡£

+ +

¥³¥ó¥Ñ¥¤¥ë»þ¤Ë¥Þ¥ë¥Á¥¹¥ì¥Ã¥É MPM ¤¬Áª¤Ð¤ì¤¿¤È¤­¤Ï + mod_cgi ¤ÎÂå¤ï¤ê¤Ëɬ¤º¤³¤Î¥â¥¸¥å¡¼¥ë¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£ + ¥æ¡¼¥¶¤Î¥ì¥Ù¥ë¤Ç¤Ï¤³¤Î¥â¥¸¥å¡¼¥ë¤ÎÀßÄê¤ÈÆ°ºî¤Ï mod_cgi + ¤È¤Þ¤Ã¤¿¤¯Æ±¤¸¤Ç¤¹¡£Í£°ì¤ÎÎã³°¤Ï ScriptSock ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + Äɲäǡ¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï CGI ¥Ç¡¼¥â¥ó¤È¤ÎÄÌ¿®ÍѤΥ½¥±¥Ã¥È¤Î̾Á°¤ò + »ØÄꤷ¤Þ¤¹¡£

+
+ + +
top
+

ScriptSock ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:CGI ¥Ç¡¼¥â¥ó¤È¤ÎÄÌ¿®¤Ë»È¤ï¤ì¤ë¥½¥±¥Ã¥È¤Î̾Á°
¹½Ê¸:ScriptSock file-path
¥Ç¥Õ¥©¥ë¥È:ScriptSock logs/cgisock
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_cgid
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï CGI ¥Ç¡¼¥â¥ó¤È¤ÎÄÌ¿®¤Ë»È¤ï¤ì¤ë¥½¥±¥Ã¥È¤Î + ̾Á°¤òÀßÄꤷ¤Þ¤¹¡£¥½¥±¥Ã¥È¤Ï Apache ¤¬µ¯Æ°¤µ¤ì¤¿¥æ¡¼¥¶ (Ä̾ï root) ¤Î + ¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤òÍѤ¤¤Æ¥ª¡¼¥×¥ó¤µ¤ì¤Þ¤¹¡£CGI ¥¹¥¯¥ê¥×¥È¤È¤ÎÄÌ¿®¤Î + ¥»¥­¥å¥ê¥Æ¥£¤òÊݤĤ¿¤á¤Ë¡¢¥½¥±¥Ã¥È¤Î¸ºß¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ë + ¾¤Î¥æ¡¼¥¶¤¬½ñ¤­¹þ¤ß¸¢¸Â¤ò»ý¤Ã¤Æ¤¤¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¤³¤È¤¬½ÅÍפǤ¹¡£

+ +

Îã

+ ScriptSock /var/run/cgid.sock +

+ + +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_cgid.html.ko.euc-kr b/docs/manual/mod/mod_cgid.html.ko.euc-kr new file mode 100644 index 00000000..be87fe1e --- /dev/null +++ b/docs/manual/mod/mod_cgid.html.ko.euc-kr @@ -0,0 +1,99 @@ + + + +mod_cgid - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_cgid

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:¿ÜºÎ CGI µ¥¸óÀ» »ç¿ëÇÏ¿© CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇà
»óÅÂ:Base
¸ðµâ¸í:cgid_module
¼Ò½ºÆÄÀÏ:mod_cgid.c
Áö¿ø:À¯´Ð½º¿¡¼­ ¾²·¹µå¸¦ »ç¿ëÇÏ´Â MPMs Àü¿ë
+

¿ä¾à

+ +

¾Æ·¡¿¡¼­ ¼³¸íÇÏ´Â Ãß°¡µÈ ScriptSock Áö½Ã¾î¸¦ Á¦¿ÜÇÏ°í + mod_cgid´Â mod_cgi¿Í + ºñ½ÁÇÏ°Ô µ¿ÀÛÇÑ´Ù. ¾ÆÆÄÄ¡¿Í CGI¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸íÀº + mod_cgi¸¦ Âü°íÇ϶ó.

+ +

¾î¶² À¯´Ð½º ¿î¿µÃ¼Á¦ÀÇ °æ¿ì ´ÙÁß¾²·¹µå ¼­¹ö¿¡¼­ ÇÁ·Î¼¼½º¸¦ + Æ÷Å©(fork)ÇÏ¸é »õ·Î¿î ÇÁ·Î¼¼½º°¡ ºÎ¸ð ÇÁ·Î¼¼½ºÀÇ ¸ðµç ¾²·¹µå¸¦ + º¹Á¦ÇØ¾ß ÇϹǷΠºÎ´ãÀÌ µÈ´Ù. CGI ½ÇÇึ´Ù ÀÌ·± ºÎ´ãÀ» ÁÖÁö + ¾Ê±âÀ§ÇØ mod_cgid´Â CGI ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÏ´Â + ÀÚ½Ä ÇÁ·Î¼¼½º¸¦ Æ÷Å©ÇÏ´Â ¿ÜºÎ µ¥¸óÀ» ¸¸µç´Ù. ÁÖ¼­¹ö´Â ÀÌ + µ¥¸ó°ú À¯´Ð½º¼ÒÄÏ(unix domain socket)À» »ç¿ëÇÏ¿© Åë½ÅÇÑ´Ù.

+ +

ÄÄÆÄÀÏÇÒ¶§ ´ÙÁß¾²·¹µå MPMÀ» ¼±ÅÃÇÏ¸é ±âº»ÀûÀ¸·Î + mod_cgi ´ë½Å ÀÌ ¸ðµâÀ» »ç¿ëÇÑ´Ù. »ç¿ëÀÚ + ÀÔÀå¿¡¼­ ÀÌ ¸ðµâÀÇ ¼³Á¤°ú µ¿ÀÛÀº mod_cgi¿Í + µ¿ÀÏÇÏ´Ù. À¯ÀÏÇÑ Â÷ÀÌÁ¡Àº cgi µ¥¸ó°ú Åë½ÅÀ» À§ÇØ »ç¿ëÇÒ + ¼ÒÄÏÀÇ À̸§À» ¼³Á¤ÇÏ´Â ScriptSock Áö½Ã¾î°¡ + Ãß°¡µÈ Á¡ÀÌ´Ù.

+
+ + +
top
+

ScriptSock Áö½Ã¾î

+ + + + + + + +
¼³¸í:cgi µ¥¸ó°ú Åë½ÅÀ» À§ÇØ »ç¿ëÇÒ ¼ÒÄÏÀÇ À̸§
¹®¹ý:ScriptSock file-path
±âº»°ª:ScriptSock logs/cgisock
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_cgid
+

ÀÌ Áö½Ã¾î´Â CGI µ¥¸ó°ú Åë½ÅÀ» À§ÇØ »ç¿ëÇÒ ¼ÒÄÏÀÇ À̸§À» + ÁöÁ¤ÇÑ´Ù. ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇÑ »ç¿ëÀÚ (º¸Åë root) ±ÇÇÑÀ¸·Î ¼ÒÄÏÀ» + ¿¬´Ù. CGI ½ºÅ©¸³Æ®¿Í Åë½ÅÀÇ º¸¾ÈÀ» À§ÇØ ´Ù¸¥ »ç¿ëÀÚ°¡ ¼ÒÄÏÀÌ + ÀÖ´Â µð·ºÅ丮¿¡ ¾²±â±ÇÇÑÀ» °¡ÁöÁö¾Ê´Â °ÍÀÌ Áß¿äÇÏ´Ù.

+ +

¿¹Á¦

+ ScriptSock /var/run/cgid.sock +

+ + +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_charset_lite.html b/docs/manual/mod/mod_charset_lite.html new file mode 100644 index 00000000..1592ea01 --- /dev/null +++ b/docs/manual/mod/mod_charset_lite.html @@ -0,0 +1,7 @@ +URI: mod_charset_lite.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_charset_lite.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_charset_lite.html.en b/docs/manual/mod/mod_charset_lite.html.en new file mode 100644 index 00000000..b58dc227 --- /dev/null +++ b/docs/manual/mod/mod_charset_lite.html.en @@ -0,0 +1,210 @@ + + + +mod_charset_lite - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_charset_lite

+
+

Available Languages:  en  | + ko 

+
+ + + +
Description:Specify character set translation or recoding
Status:Experimental
Module Identifier:charset_lite_module
Source File:mod_charset_lite.c
+

Summary

+ +

This is an experimental module and should + be used with care. Experiment with your + mod_charset_lite configuration to ensure that it + performs the desired function.

+ +

mod_charset_lite allows the administrator to + specify the source character set of objects as well as the + character set they should be translated into before sending to the + client. mod_charset_lite does not translate the + data itself but instead tells Apache what translation to + perform. mod_charset_lite is applicable to EBCDIC + and ASCII host environments. In an EBCDIC environment, Apache + normally translates text content from the code page of the Apache + process locale to ISO-8859-1. mod_charset_lite + can be used to specify that a different translation is to be + performed. In an ASCII environment, Apache normally performs no + translation, so mod_charset_lite is needed in + order for any translation to take place.

+ +

This module provides a small subset of configuration + mechanisms implemented by Russian Apache and its associated + mod_charset.

+
+ +
top
+
+

Common Problems

+ +

Invalid character set names

+ +

The character set name parameters of CharsetSourceEnc and + CharsetDefault + must be acceptable to the translation mechanism used by + APR on the system where + mod_charset_lite is deployed. These character + set names are not standardized and are usually not the same as + the corresponding values used in http headers. Currently, APR + can only use iconv(3), so you can easily test your character set + names using the iconv(1) program, as follows:

+ +

+ iconv -f charsetsourceenc-value -t charsetdefault-value +

+ + +

Mismatch between character set of content and translation + rules

+ +

If the translation rules don't make sense for the content, + translation can fail in various ways, including:

+ +
    +
  • The translation mechanism may return a bad return code, + and the connection will be aborted.
    • + +
  • The translation mechanism may silently place special + characters (e.g., question marks) in the output buffer when + it cannot translate the input buffer.
    • +
+ +
+
top
+

CharsetDefault Directive

+ + + + + + + +
Description:Charset to translate into
Syntax:CharsetDefault charset
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Experimental
Module:mod_charset_lite
+

The CharsetDefault directive specifies the + charset that content in the associated container should be + translated to.

+ +

The value of the charset argument must be accepted + as a valid character set name by the character set support in + APR. Generally, this means that it must be + supported by iconv.

+ +

Example

+ <Directory /export/home/trawick/apacheinst/htdocs/convert>
+ + CharsetSourceEnc UTF-16BE
+ CharsetDefault ISO-8859-1
+ + </Directory> +

+ +
+
top
+

CharsetOptions Directive

+ + + + + + + + +
Description:Configures charset translation behavior
Syntax:CharsetOptions option [option] ...
Default:CharsetOptions DebugLevel=0 NoImplicitAdd
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Experimental
Module:mod_charset_lite
+

The CharsetOptions directive configures certain + behaviors of mod_charset_lite. Option can + be one of

+ +
+
DebugLevel=n
+ +
The DebugLevel keyword allows you to specify + the level of debug messages generated by + mod_charset_lite. By default, no messages are + generated. This is equivalent to DebugLevel=0. + With higher numbers, more debug messages are generated, and + server performance will be degraded. The actual meanings of + the numeric values are described with the definitions of the + DBGLVL_ constants near the beginning of + mod_charset_lite.c.
+ +
ImplicitAdd | NoImplicitAdd
+ +
The ImplicitAdd keyword specifies that + mod_charset_lite should implicitly insert its + filter when the configuration specifies that the character + set of content should be translated. If the filter chain is + explicitly configured using the AddOutputFilter directive, NoImplicitAdd + should be specified so that mod_charset_lite + doesn't add its filter.
+
+ +
+
top
+

CharsetSourceEnc Directive

+ + + + + + + +
Description:Source charset of files
Syntax:CharsetSourceEnc charset
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Experimental
Module:mod_charset_lite
+

The CharsetSourceEnc directive specifies the + source charset of files in the associated container.

+ +

The value of the charset argument must be accepted + as a valid character set name by the character set support in + APR. Generally, this means that it must be + supported by iconv.

+ +

Example

+ <Directory /export/home/trawick/apacheinst/htdocs/convert>
+ + CharsetSourceEnc UTF-16BE
+ CharsetDefault ISO-8859-1
+ + </Directory> +

+ +

The character set names in this example work with the iconv + translation support in Solaris 8.

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_charset_lite.html.ko.euc-kr b/docs/manual/mod/mod_charset_lite.html.ko.euc-kr new file mode 100644 index 00000000..8adb21e5 --- /dev/null +++ b/docs/manual/mod/mod_charset_lite.html.ko.euc-kr @@ -0,0 +1,198 @@ + + + +mod_charset_lite - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_charset_lite

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:¹®ÀÚÁýÇÕ º¯È¯À» ÁöÁ¤
»óÅÂ:Experimental
¸ðµâ¸í:charset_lite_module
¼Ò½ºÆÄÀÏ:mod_charset_lite.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ½ÇÇèÀûÀÎ ¸ðµâÀÌ°í, ÁÖÀÇÀÖ°Ô + »ç¿ëÇØ¾ß ÇÑ´Ù. ¿øÇÏ´Â µ¿ÀÛÀ» ÇÏ´ÂÁö + mod_charset_lite ¼³Á¤À» ½ÃÇèÇغÁ¶ó.

+ +

mod_charset_lite¸¦ »ç¿ëÇÏ¿© ¹®¼­ ¿øº»ÀÇ + ¹®ÀÚÁýÇÕ°ú ¹®¼­¸¦ Ŭ¶óÀ̾ðÆ®·Î º¸³»±â Àü¿¡ º¯È¯ÇÒ ¹®ÀÚÁýÇÕÀ» + ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù. mod_charset_lite´Â Á÷Á¢ + ÀڷḦ º¯È¯ÇÏÁö¾Ê°í ´ë½Å ¾ÆÆÄÄ¡¿¡°Ô º¯È¯Ç϶ó°í ¿äûÇÑ´Ù. + mod_charset_lite´Â EBCDIC°ú ASCII ȯ°æ¿¡¼­ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. EBCDIC ȯ°æ¿¡¼­ ¾ÆÆÄÄ¡´Â º¸Åë ¾ÆÆÄÄ¡ ÇÁ·Î¼¼½ºÀÇ + ÄÚµåÆäÀÌÁö¿¡¼­ ISO-8859-1 ¹®ÀÚÁýÇÕÀ¸·Î ¹®¼­¸¦ º¯È¯ÇÑ´Ù. + mod_charset_lite¸¦ »ç¿ëÇÏ¿© ´Ù¸¥ º¯È¯À» + Áö½ÃÇÒ ¼ö ÀÖ´Ù. ASCII ȯ°æ¿¡¼­ ¾ÆÆÄÄ¡´Â ±âº»ÀûÀ¸·Î º¯È¯À» + ÇÏÁö ¾Ê±â¶§¹®¿¡, ¾î¶² º¯È¯À» À§Çؼ­´Â + mod_charset_lite°¡ ÇÊ¿äÇÏ´Ù.

+ +

ÀÌ ¸ðµâÀº ·¯½Ã¾ÆÆÇ ¾ÆÆÄÄ¡ÀÇ mod_charsetÀÌ + Á¦°øÇÏ´Â ¼³Á¤ÀÇ ÀϺθ¦ Á¦°øÇÑ´Ù.

+
+ +
top
+
+

ÀϹÝÀûÀÎ ¹®Á¦Á¡

+ +

À߸øµÈ ¹®ÀÚÁýÇÕ À̸§

+ +

mod_charset_lite¸¦ »ç¿ëÇÏ´Â ½Ã½ºÅÛÀÇ + ARP ¹ø¿ª±â´ÉÀÌ CharsetSourceEnc¿Í + CharsetDefaultÀÇ + ÆĶó¹ÌÅÍÀÎ ¹®ÀÚÁýÇÕ À̸§À» ó¸®ÇÒ ¼ö ÀÖ¾î¾ß ÇÑ´Ù. ¹®ÀÚÁýÇÕ + À̸§Àº Ç¥ÁØÈ­µÇÁö ¾Ê¾Ò°í, http Çì´õ¿¡ »ç¿ëÇÏ´Â °ª°ú Ç×»ó + °°Áö´Â ¾Ê´Ù. ÇöÀç APRÀº iconv(3)¸¸À» »ç¿ëÇϱ⶧¹®¿¡, + ´ÙÀ½°ú °°ÀÌ iconv(1) ÇÁ·Î±×·¥À» »ç¿ëÇÏ¿© ƯÁ¤ ¹®ÀÚÁýÇÕ + À̸§À» »ç¿ëÇÒ ¼ö ÀÖ´ÂÁö ½±°Ô ¾Ë ¼ö ÀÖ´Ù:

+ +

+ iconv -f charsetsourceenc-value -t charsetdefault-value +

+ + +

³»¿ë°ú º¯È¯±ÔÄ¢ÀÇ ¹®ÀÚÁýÇÕÀÌ ¼­·Î ´Ù¸§

+ +

º¯È¯±ÔÄ¢ÀÌ »óȲ¿¡ ¸ÂÁö¾ÊÀ¸¸é ´ÙÀ½°ú °°Àº ¿©·¯ ¹æ½ÄÀ¸·Î + º¯È¯ÀÌ ½ÇÆÐÇÒ ¼ö ÀÖ´Ù:

+ +
    +
  • º¯È¯±â´ÉÀÌ ½ÇÆÐ ¹ÝȯÄڵ带 ¹ÝȯÇÏ°í ¿¬°áÀÌ ²÷¾îÁú + ¼ö ÀÖ´Ù.
    • + +
  • ÀԷ¹öÆÛ¸¦ º¯È¯ÇÏÁö ¸øÇÒ¶§ Ãâ·Â¹öÆÛ¿¡ ´ë½Å Ưº°ÇÑ + ¹®ÀÚ¸¦ (¿¹, ¹°À½Ç¥) ÀûÀ» ¼ö ÀÖ´Ù.
    • +
+ +
+
top
+

CharsetDefault Áö½Ã¾î

+ + + + + + + +
¼³¸í:º¯È¯ÇÒ ¹®ÀÚÁýÇÕ
¹®¹ý:CharsetDefault charset
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Experimental
¸ðµâ:mod_charset_lite
+

CharsetDefault Áö½Ã¾î´Â Áö½Ã¾î¸¦ + »ç¿ëÇÑ À§Ä¡¿¡ ÀÖ´Â ¿øº»À» º¯È¯ÇÒ ¹®ÀÚÁýÇÕÀ» ÁöÁ¤ÇÑ´Ù.

+ +

charset ¾Æ±Ô¸ÕÆ®¿¡´Â APRÀÌ Áö¿øÇÏ´Â ¹®ÀÚÁýÇÕ + À̸§À» »ç¿ëÇØ¾ß ÇÑ´Ù. ÀϹÝÀûÀ¸·Î iconv°¡ Áö¿øÇÏ´Â ¹®ÀÚÁýÇÕÀ» + ÀǹÌÇÑ´Ù.

+ +

¿¹Á¦

+ <Directory /export/home/trawick/apacheinst/htdocs/convert>
+ + CharsetSourceEnc UTF-16BE
+ CharsetDefault ISO-8859-1
+ + </Directory> +

+ +
+
top
+

CharsetOptions Áö½Ã¾î

+ + + + + + + + +
¼³¸í:¹®ÀÚÁýÇÕ º¯È¯ ±â´ÉÀ» ¼³Á¤
¹®¹ý:CharsetOptions option [option] ...
±âº»°ª:CharsetOptions DebugLevel=0 NoImplicitAdd
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Experimental
¸ðµâ:mod_charset_lite
+

CharsetOptions Áö½Ã¾î´Â + mod_charset_liteÀÇ ±â´ÉÀ» ¼³Á¤ÇÑ´Ù. + Option¿¡´Â ¾Æ·¡ Ç׸ñµéÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù

+ +
+
DebugLevel=n
+ +
DebugLevel Å°¿öµå´Â + mod_charset_lite°¡ ±â·ÏÇÏ´Â µð¹ö±×¹®±¸ÀÇ + ¼öÁØÀ» ¼³Á¤ÇÑ´Ù. ±âº»ÀûÀ¸·Î ¾î¶² °Íµµ ±â·ÏÇÏÁö ¾Ê´Â´Ù. + ÀÌ´Â DebugLevel=0°ú °°´Ù. ³ôÀº ¼ýÀÚ¸¦ »ç¿ëÇÒ¼ö·Ï + ´õ ¸¹Àº µð¹ö±×¹®±¸¸¦ ±â·ÏÇÏ°ÔµÇ¾î ¼­¹ö ¼º´ÉÀÌ ¶³¾îÁø´Ù. + ¼ýÀÚ°ªÀÇ ½ÇÁ¦ Àǹ̴ mod_charset_lite.c ¾ÕºÎºÐÀÇ + DBGLVL_ »ó¼ö Á¤ÀǸ¦ Âü°íÇ϶ó.
+ +
ImplicitAdd | NoImplicitAdd
+ +
ImplicitAdd Å°¿öµå´Â ³»¿ëÀ» º¯È¯ÇÒ + ¹®ÀÚÁýÇÕÀ» ÁöÁ¤Çϸé ÀÚµ¿À¸·Î mod_charset_lite¸¦ + ÇÊÅÍ¿¡ Ãß°¡ÇÑ´Ù. AddOutputFilter Áö½Ã¾î·Î ÇÊÅͼø¼­¸¦ Á÷Á¢ + ÁöÁ¤ÇÑ´Ù¸é, NoImplicitAdd¸¦ »ç¿ëÇÏ¿© + mod_charset_lite°¡ ÀÚµ¿À¸·Î ÇÊÅÍ¿¡ + Ãß°¡µÇÁö¾Êµµ·Ï ÇØ¾ß ÇÑ´Ù.
+
+ +
+
top
+

CharsetSourceEnc Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÆÄÀÏ ¿øº»ÀÇ ¹®ÀÚÁýÇÕ
¹®¹ý:CharsetSourceEnc charset
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Experimental
¸ðµâ:mod_charset_lite
+

CharsetSourceEnc Áö½Ã¾î´Â Áö½Ã¾î¸¦ + »ç¿ëÇÑ À§Ä¡¿¡ ÀÖ´Â ÆÄÀÏµé ¿øº»ÀÇ ¹®ÀÚÁýÇÕÀ» ÁöÁ¤ÇÑ´Ù.

+ +

charset ¾Æ±Ô¸ÕÆ®¿¡´Â APRÀÌ Áö¿øÇÏ´Â ¹®ÀÚÁýÇÕ + À̸§À» »ç¿ëÇØ¾ß ÇÑ´Ù. ÀϹÝÀûÀ¸·Î iconv°¡ Áö¿øÇÏ´Â ¹®ÀÚÁýÇÕÀ» + ÀǹÌÇÑ´Ù.

+ +

¿¹Á¦

+ <Directory /export/home/trawick/apacheinst/htdocs/convert>
+ + CharsetSourceEnc UTF-16BE
+ CharsetDefault ISO-8859-1
+ + </Directory> +

+ +

Solaris 8ÀÇ iconv°¡ ÀÌ ¿¹Á¦ÀÇ ¹®ÀÚÁýÇÕÀ» Áö¿øÇÑ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dav.html b/docs/manual/mod/mod_dav.html new file mode 100644 index 00000000..347f8cf2 --- /dev/null +++ b/docs/manual/mod/mod_dav.html @@ -0,0 +1,11 @@ +URI: mod_dav.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_dav.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_dav.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_dav.html.en b/docs/manual/mod/mod_dav.html.en new file mode 100644 index 00000000..aa4e14ac --- /dev/null +++ b/docs/manual/mod/mod_dav.html.en @@ -0,0 +1,270 @@ + + + +mod_dav - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_dav

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Distributed Authoring and Versioning +(WebDAV) functionality
Status:Extension
Module Identifier:dav_module
Source File:mod_dav.c
+

Summary

+ +

This module provides class 1 and class 2 WebDAV ('Web-based Distributed + Authoring and Versioning') functionality for Apache. This + extension to the HTTP protocol allows creating, moving, + copying, and deleting resources and collections on a remote web + server.

+
+ +
top
+
+

Enabling WebDAV

+

To enable mod_dav, add the following to a + container in your httpd.conf file:

+ +

Dav On

+ +

This enables the DAV file system provider, which is implemented + by the mod_dav_fs module. Therefore, that module + must be compiled into the server or loaded at runtime using the + LoadModule directive.

+ +

In addition, a location for the DAV lock database must be + specified in the global section of your httpd.conf + file using the DavLockDB + directive:

+ +

+ DavLockDB /usr/local/apache2/var/DavLock +

+ +

The directory containing the lock database file must be + writable by the User + and Group under which + Apache is running.

+ +

You may wish to add a <Limit> clause inside the <Location> directive to limit access to + DAV-enabled locations. If you want to set the maximum amount of + bytes that a DAV client can send at one request, you have to use + the LimitXMLRequestBody + directive. The "normal" LimitRequestBody directive has no effect on DAV + requests.

+ +

Full Example

+ DavLockDB /usr/local/apache2/var/DavLock
+
+ <Location /foo>
+ + Order Allow,Deny
+ Allow from all
+ Dav On
+
+ AuthType Basic
+ AuthName DAV
+ AuthUserFile user.passwd
+
+ <LimitExcept GET OPTIONS>
+ + require user admin
+ + </LimitExcept>
+ + </Location>
+

+ +

mod_dav is a descendent of Greg Stein's mod_dav for Apache 1.3. More + information about the module is available from that site.

+
top
+
+

Security Issues

+ +

Since DAV access methods allow remote clients to manipulate + files on the server, you must take particular care to assure that + your server is secure before enabling mod_dav.

+ +

Any location on the server where DAV is enabled should be + protected by authentication. The use of HTTP Basic Authentication + is not recommended. You should use at least HTTP Digest + Authentication, which is provided by the + mod_auth_digest module. Nearly all WebDAV clients + support this authentication method. An alternative is Basic + Authentication over an SSL enabled + connection.

+ +

In order for mod_dav to manage files, it must + be able to write to the directories and files under its control + using the User and + Group under which + Apache is running. New files created will also be owned by this + User and Group. For this reason, it is + important to control access to this account. The DAV repository + is considered private to Apache; modifying files outside of Apache + (for example using FTP or filesystem-level tools) should not be + allowed.

+ +

mod_dav may be subject to various kinds of + denial-of-service attacks. The LimitXMLRequestBody directive can be + used to limit the amount of memory consumed in parsing large DAV + requests. The DavDepthInfinity directive can be + used to prevent PROPFIND requests on a very large + repository from consuming large amounts of memory. Another + possible denial-of-service attack involves a client simply filling + up all available disk space with many large files. There is no + direct way to prevent this in Apache, so you should avoid giving + DAV access to untrusted users.

+
top
+
+

Complex Configurations

+ +

One common request is to use mod_dav to + manipulate dynamic files (PHP scripts, CGI scripts, etc). This is + difficult because a GET request will always run the + script, rather than downloading its contents. One way to avoid + this is to map two different URLs to the content, one of which + will run the script, and one of which will allow it to be + downloaded and manipulated with DAV.

+ +

+Alias /phparea /home/gstein/php_files
+Alias /php-source /home/gstein/php_files
+<Location /php-source> + + DAV On
+ ForceType text/plain
+ +</Location> +

+ +

With this setup, http://example.com/phparea can be + used to access the output of the PHP scripts, and + http://example.com/php-source can be used with a DAV + client to manipulate them.

+
+
top
+

Dav Directive

+ + + + + + + +
Description:Enable WebDAV HTTP methods
Syntax:Dav On|Off|provider-name
Default:Dav Off
Context:directory
Status:Extension
Module:mod_dav
+

Use the Dav directive to enable the + WebDAV HTTP methods for the given container:

+ +

+ <Location /foo>
+ + Dav On
+ + </Location> +

+ +

The value On is actually an alias for the default + provider filesystem which is served by the mod_dav_fs module. Note, that once you have DAV enabled + for some location, it cannot be disabled for sublocations. + For a complete configuration example have a look at the section above.

+ +
+ Do not enable WebDAV until you have secured your server. Otherwise + everyone will be able to distribute files on your system. +
+ +
+
top
+

DavDepthInfinity Directive

+ + + + + + + +
Description:Allow PROPFIND, Depth: Infinity requests
Syntax:DavDepthInfinity on|off
Default:DavDepthInfinity off
Context:server config, virtual host, directory
Status:Extension
Module:mod_dav
+

Use the DavDepthInfinity directive to + allow the processing of PROPFIND requests containing the + header 'Depth: Infinity'. Because this type of request could constitute + a denial-of-service attack, by default it is not allowed.

+ +
+
top
+

DavMinTimeout Directive

+ + + + + + + +
Description:Minimum amount of time the server holds a lock on +a DAV resource
Syntax:DavMinTimeout seconds
Default:DavMinTimeout 0
Context:server config, virtual host, directory
Status:Extension
Module:mod_dav
+

When a client requests a DAV resource lock, it can also + specify a time when the lock will be automatically removed by + the server. This value is only a request, and the server can + ignore it or inform the client of an arbitrary value.

+ +

Use the DavMinTimeout directive to specify, in + seconds, the minimum lock timeout to return to a client. + Microsoft Web Folders defaults to a timeout of 120 seconds; the + DavMinTimeout can override this to a higher value + (like 600 seconds) to reduce the chance of the client losing + the lock due to network latency.

+ +

Example

+ <Location /MSWord>
+ + DavMinTimeout 600
+ + </Location> +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dav.html.ja.euc-jp b/docs/manual/mod/mod_dav.html.ja.euc-jp new file mode 100644 index 00000000..9d799e14 --- /dev/null +++ b/docs/manual/mod/mod_dav.html.ja.euc-jp @@ -0,0 +1,276 @@ + + + +mod_dav - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_dav

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:ʬ»¶¥ª¡¼¥µ¥ê¥ó¥°¤È¥Ð¡¼¥¸¥ç¥ó´ÉÍý +(WebDAV) µ¡Ç½
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:dav_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_dav.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥¯¥é¥¹ 1 ¤È¥¯¥é¥¹ 2 ¤Î + WebDAV + ('¥¦¥§¥Ö¥Ù¡¼¥¹¤Îʬ»¶¥ª¡¼¥µ¥ê¥ó¥°¤È¥Ð¡¼¥¸¥ç¥ó´ÉÍý') + µ¡Ç½¤ò Apache ¤ËÄ󶡤·¤Þ¤¹¡£ + ¤³¤Î HTTP ¥×¥í¥È¥³¥ë¤Î³ÈÄ¥¤Ë¤è¤ê¡¢¥ê¥â¡¼¥È¤Î¥¦¥§¥Ö¥µ¡¼¥Ð¾å¤Ë¤¢¤ë + ¥ê¥½¡¼¥¹¤ä¥³¥ì¥¯¥·¥ç¥ó¤ò + ºîÀ®¡¢°ÜÆ°¡¢Ê£À½¡¢ºï½ü¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+
+ +
top
+
+

Enabling WebDAV

+

mod_dav ¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢httpd.conf + ¥Õ¥¡¥¤¥ëÃæ¤Î¥³¥ó¥Æ¥Ê¤Ë¼¡¤ò²Ã¤¨¤Þ¤¹:

+ +

Dav On

+ +

¤³¤ì¤Ï DAV ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥×¥í¥Ð¥¤¥À¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£DAV + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥×¥í¥Ð¥¤¥À¤Ï mod_dav_fs + ¥â¥¸¥å¡¼¥ë¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥³¥ó¥Ñ¥¤¥ë»þ¤Ë + ¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤«¡¢¤¢¤ë¤¤¤Ï + LoadModule + ¤ò»ÈÍѤ·¤Æ¼Â¹Ô»þ¤Ë¥í¡¼¥É¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

¤µ¤é¤Ë¡¢DAV ¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¾ì½ê¤¬ + DavLockDB ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ + httd.conf ¥Õ¥¡¥¤¥ë¤Î¥°¥í¡¼¥Ð¥ë¥»¥¯¥·¥ç¥ó¤Ë»ØÄꤵ¤ì¤Æ¤¤¤ë + ɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

+ DavLockDB /usr/local/apache2/var/DavLock +

+ +

¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤Î¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ï Apache ¤¬¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë + User ¤È Group ¤Ë½ñ¤­¹þ¤ß¸¢¸Â¤¬¤¢¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

<Limit> + Àá¤ò <Location> + ¥Ç¥£¥ì¥¯¥Æ¥£¥ÖÆâÉô¤ËÄɲ䷤ơ¢DAV ¤¬Í­¸ú¤Ê¾ì½ê¤Ø¤Î + ¥¢¥¯¥»¥¹¤òÀ©¸Â¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£DAV ¥¯¥é¥¤¥¢¥ó¥È¤¬ + °ìÅ٤Υꥯ¥¨¥¹¥È¤ÇÁ÷¿®¤Ç¤­¤ëºÇÂç¥Ð¥¤¥È¿ô¤ò»ØÄꤷ¤¿¤¤¤È¤­¤Ï¡¢ + LimitXMLRequestBody + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¡ÖÄ̾ï¤Î¡× + LimitRequestBody + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï DAV ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¤Ï¸úÎϤò»ý¤Á¤Þ¤»¤ó¡£

+ +

´°Á´¤ÊÎã

+ DavLockDB /usr/local/apache2/var/DavLock
+
+ <Location /foo>
+ + Dav On
+
+ AuthType Basic
+ AuthName DAV
+ AuthUserFile user.passwd
+
+ <LimitExcept GET OPTIONS>
+ + require user admin
+ + </LimitExcept>
+ + </Location>
+

+ +

mod_dav ¤Ï Greg Stein ¤µ¤ó¤Î Apache 1.3 ÍѤΠmod_dav ¤Ë + ͳÍ褹¤ë¤â¤Î¤Ç¤¹¡£¤½¤Î¥µ¥¤¥È¤«¤é¤è¤ê¿¤¯¤Î¾ðÊó¤ò¼ê¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
top
+
+

¥»¥­¥å¥ê¥Æ¥£¤ÎÌäÂê

+ +

DAV ¤Î¥¢¥¯¥»¥¹¥á¥½¥Ã¥É¤Ï±ó³Ö¥¯¥é¥¤¥¢¥ó¥È¤¬¥µ¡¼¥Ð¤Î¥Õ¥¡¥¤¥ë¤ò + Áàºî¤¹¤ë¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¤Î¤Ç¡¢ mod_dav ¤ò»ÈÍѤ¹¤ë + Á°¤Ë¡¢¥µ¡¼¥Ð¤¬°ÂÁ´¤Ç¤¢¤ë¤³¤È¤òÆäËÃí°Õ¤·¤Æ³Îǧ¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

¥µ¡¼¥Ð¾å¤Î DAV ¤¬»ÈÍѲÄǽ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì½ê¤Ï¤¹¤Ù¤Æǧ¾Ú¤ÇÊݸ¤Æ¤¯¤À¤µ¤¤¡£ + HTTP ´ðËÜǧ¾Ú¤Î»ÈÍѤϿ侩¤Ç¤­¤Þ¤»¤ó¡£¾¯¤Ê¤¯¤È¤â + mod_auth_digest ¥â¥¸¥å¡¼¥ë¤ÇÄ󶡤µ¤ì¤ë HTTP + ¥À¥¤¥¸¥§¥¹¥Èǧ¾Ú¤òÍѤ¤¤ë¤Ù¤­¤Ç¤¹¡£WebDAV ¥¯¥é¥¤¥¢¥ó¥È¤Î¤Û¤È¤ó¤É¤Ï + ¤³¤Îǧ¾ÚÊýË¡¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£Âå¤ï¤ê¤Ë¡¢SSL ¤¬ + Í­¸ú¤Ê¥³¥Í¥¯¥·¥ç¥ó¤òÄ̤·¤¿´ðËÜǧ¾Ú¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

mod_dav ¤¬¥Õ¥¡¥¤¥ë¤òÁàºî¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ + ´ÉÍý²¼¤Î¥Ç¥£¥ì¥¯¥È¥ê¤È¥Õ¥¡¥¤¥ë¤È¤Ë Apache ¤¬¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë User ¤È Group ¤Ç½ñ¤­¹þ¤ß²Äǽ¤Ç¤¢¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¿·¤·¤¯ºîÀ®¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤â¤³¤Î User + ¤È Group ¤Ë½êÍ­¤µ¤ì¤ë + ¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤ÎÍýͳ¤«¤é¡¢¤½¤Î¥¢¥«¥¦¥ó¥È¤Ø¤Î¥¢¥¯¥»¥¹¤òÀ©¸æ¤¹¤ë¤³¤È¤Ï + ½ÅÍפǤ¹¡£DAV ¥ê¥Ý¥¸¥È¥ê¤Ï Apache ÀìÍѤΤâ¤Î¤À¤È¤ß¤Ê¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + Apache °Ê³°¤ÎÊýË¡¤Ç¥Õ¥¡¥¤¥ë¤ò½¤Àµ¤¹¤ë¤³¤È (Î㤨¤Ð FTP ¤ä¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à + ÍѤΥġ¼¥ë¤Ê¤É¤ò»È¤Ã¤Æ) ¤Ïµö²Ä¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£

+ +

mod_dav ¤Ï¤¤¤í¤¤¤í¤Ê¼ïÎà¤Î¥µ¡¼¥Ó¥¹µñÈݹ¶·â¤Ë¤µ¤é¤µ¤ì¤ë + ¤«¤â¤·¤ì¤Þ¤»¤ó¡£LimitXMLRequestBody ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤È + Â礭¤Ê DAV ¥ê¥¯¥¨¥¹¥È¤ò²òÀϤ¹¤ë¤È¤­¤Ë¾ÃÈñ¤µ¤ì¤ë¥á¥â¥ê¤ÎÎ̤òÀ©¸Â¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£DavDepthInfinity ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + PROPFIND ¥ê¥¯¥¨¥¹¥È¤¬µðÂç¥ê¥Ý¥¸¥È¥ê¤ÇÂçÎ̤Υá¥â¥ê¤ò¾ÃÈñ¤¹¤ë¤Î¤ò + Ëɤ°¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Â¾¤Î¥µ¡¼¥Ó¥¹µñÈݹ¶·â¤Ë¤Ïñ½ã¤Ë»ÈÍѲÄǽ¤Ê¥Ç¥£¥¹¥¯Îΰè¤ò + ¿¤¯¤ÎÂ礭¤Ê¥Õ¥¡¥¤¥ë¤ÇËä¤á¤Æ¤·¤Þ¤¦¤ó¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤òľÀÜËɤ°ÊýË¡¤Ï + Apache ¤Ë¤Ï¤¢¤ê¤Þ¤»¤ó¤Î¤Ç¡¢¿®ÍѤǤ­¤Ê¤¤¥æ¡¼¥¶¤Ë DAV ¥¢¥¯¥»¥¹¤òÄ󶡤¹¤ë¤Î¤Ï + Èò¤±¤¿Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+
top
+
+

Ê£»¨¤ÊÀßÄê

+ +

¤è¤¯¤¢¤ëÍ×µá¤Ë¡¢mod_dav ¤ò»È¤Ã¤ÆưŪ¤Ê¥Õ¥¡¥¤¥ë + (PHP ¥¹¥¯¥ê¥×¥È¡¢CGI ¥¹¥¯¥ê¥×¥È¤Ê¤É) ¤òÁàºî¤·¤¿¤¤¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Î¼Â¸½¤Ï¡¢GET ¥ê¥¯¥¨¥¹¥È¤Ï¥¹¥¯¥ê¥×¥È¤ÎÆâÍƤò¥À¥¦¥ó¥í¡¼¥É¤µ¤»¤ë + Âå¤ï¤ê¤Ë¡¢¥¹¥¯¥ê¥×¥È¤ò¾ï¤Ë¼Â¹Ô¤µ¤»¤Æ¤·¤Þ¤¦¤Î¤ÇÆñ¤·¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¤³¤ì¤ò²óÈò¤¹¤ëÊýË¡¤Ë¤Ï¡¢Æó¤Ä¤Î°ã¤¦ URL ¤òƱ¤¸¥³¥ó¥Æ¥ó¥Ä¤Ë¥Þ¥Ã¥×¤·¡¢ + °ì¤Ä¤Ï¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤µ¤»¡¢¤â¤¦°ì¤Ä¤Ï¥À¥¦¥ó¥í¡¼¥É¤µ¤»¤¿¤ê¡¢DAV ¤«¤é + Áàºî¤µ¤ì¤¿¤ê¤¹¤ë¤è¤¦¤ËÀßÄꤹ¤ë¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£

+ +

+Alias /phparea /home/gstein/php_files
+Alias /php-source /home/gstein/php_files
+<Location /php-source> + + DAV On
+ ForceType text/plain
+ +</Location> +

+ +

¤³¤ÎÀßÄê¤Ë¤è¤ê¡¢http://example.com/phparea ¤ò PHP ¥¹¥¯¥ê¥×¥È¤Î + ½ÐÎϤò¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¡¢ + http://example.com/php-source ¤ò DAV ¥¯¥é¥¤¥¢¥ó¥È¤Ë¤è¤ë + ¤¬Áàºî¤Î¤¿¤á¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
+
top
+

Dav ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:WebDAV HTTP ¥á¥½¥Ã¥É¤òÍ­¸ú¤Ë¤·¤Þ¤¹
¹½Ê¸:Dav On|Off|provider-name
¥Ç¥Õ¥©¥ë¥È:Dav Off
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_dav
+

Í¿¤¨¤é¤ì¤¿¥³¥ó¥Æ¥Ê¤Ç WebDAV HTTP ¥á¥½¥Ã¥É¤¬»È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï + ¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

+ <Location /foo>
+ + Dav On
+ + </Location> +

+ +

On ¤È¤¤¤¦»ØÄê¤Ï¼ÂºÝ¤Ë¤Ï mod_dav_fs + ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë¥Ç¥Õ¥©¥ë¥È¤Î¥×¥í¥Ð¥¤¥À¡¢filesystem + ¤Ø¤Î¥¨¥¤¥ê¥¢¥¹¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£°ìÅÙ¤¢¤ë¥í¥±¡¼¥·¥ç¥ó¤Ç DAV + ¤òÍ­¸ú¤Ë¤·¤¿¸å¤Ï¡¢¤½¤Î¥µ¥Ö¥í¥±¡¼¥·¥ç¥ó¤Ç̵¸ú²½¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Ê¤¤ + ¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£´°Á´¤ÊÀßÄêÎã¤Ï¾åµ­¤Î¥»¥¯¥·¥ç¥ó ¤ò¤´Í÷²¼¤µ¤¤¡£

+ +
+ ¥µ¡¼¥Ð¤Î¥»¥­¥å¥ê¥Æ¥£¤¬³ÎÊݤǤ­¤ë¤Þ¤Ç WebDAV ¤òÍ­¸ú¤Ë¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + ¤½¤¦¤·¤Ê¤±¤ì¤Ðï¤Ç¤â¤½¤Î¥µ¡¼¥Ð¤Ç¥Õ¥¡¥¤¥ë¤òÇÛÉÛ¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë + ¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£ +
+ +
+
top
+

DavDepthInfinity ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:PROPFIND, Depth: Infinity ¥ê¥¯¥¨¥¹¥È¤òµö²Ä¤·¤Þ¤¹
¹½Ê¸:DavDepthInfinity on|off
¥Ç¥Õ¥©¥ë¥È:DavDepthInfinity off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_dav
+

'Depth: Infinity' ¤ò´Þ¤ó¤Ç¤¤¤ë + PROPFIND ¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢ + DavDepthInfinity + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¤¤Þ¤¹¡£¤³¤Î¥¿¥¤¥×¤Î¥ê¥¯¥¨¥¹¥È¤Ï + denial-of-service ¥¢¥¿¥Ã¥¯¤È¤Ê¤ê¤¦¤ë¤Î¤Ç¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ïµö²Ä¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£

+ +
+
top
+

DavMinTimeout ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬ DAV ¥ê¥½¡¼¥¹¤Î¥í¥Ã¥¯¤ò°Ý»ý¤¹¤ëºÇ¾®»þ´Ö¤Ç¤¹¡£ +
¹½Ê¸:DavMinTimeout seconds
¥Ç¥Õ¥©¥ë¥È:DavMinTimeout 0
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_dav
+

¥¯¥é¥¤¥¢¥ó¥È¤¬ DAV ¥ê¥½¡¼¥¹¥í¥Ã¥¯¤òÍ׵ᤷ¤¿¾ì¹ç¡¢ + ¥í¥Ã¥¯¤¬¥µ¡¼¥Ð¤Ë¤è¤Ã¤Æ¼«Æ°Åª¤Ë²ò½ü¤µ¤ì¤ë¤Þ¤Ç¤Î»þ´Ö¤ò + Ʊ»þ¤Ë»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ÎÃͤÏñ¤Ê¤ë¥ê¥¯¥¨¥¹¥È¤Ç¤¢¤Ã¤Æ¡¢ + ¥µ¡¼¥Ð¤Ï¤³¤ì¤ò̵»ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¤·¡¢ + Ǥ°Õ¤ÎÃͤò¥¯¥é¥¤¥¢¥ó¥È¤ËÄÌÃΤ¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

¥¯¥é¥¤¥¢¥ó¥È¤ËÌ᤹¥í¥Ã¥¯¥¿¥¤¥à¥¢¥¦¥È¤ÎºÇ¾®»þ´Ö¤ò¡¢ + Éäǡ¢»ØÄꤹ¤ë¤¿¤á¤Ë DavMinTimeout + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¤¤Þ¤¹¡£ + ¥Þ¥¤¥¯¥í¥½¥Õ¥È¤Î¥¦¥§¥Ö¥Õ¥©¥ë¥À¤Î¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï 120 ÉäǤ¹¤¬¡¨ + ¥Í¥Ã¥È¥ï¡¼¥¯¤ÎÃÙ±ä¤Î¤»¤¤¤Ç¥¯¥é¥¤¥¢¥ó¥È¤¬¥í¥Ã¥¯¤ò¼º¤¦¤Î¤ò¸º¤é¤¹¤¿¤á¤Ë¡¢ + DavMinTimeout ¤ò»È¤Ã¤Æ + ¤³¤ì¤ò¤â¤Ã¤ÈÂ礭¤ÊÃÍ (Î㤨¤Ð 600 ÉÃ) ¤Ë¾å½ñ¤­¤Ç¤­¤Þ¤¹¡£

+ +

Îã

+ <Location /MSWord>
+ + DavMinTimeout 600
+ + </Location> +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dav.html.ko.euc-kr b/docs/manual/mod/mod_dav.html.ko.euc-kr new file mode 100644 index 00000000..a21fbab7 --- /dev/null +++ b/docs/manual/mod/mod_dav.html.ko.euc-kr @@ -0,0 +1,265 @@ + + + +mod_dav - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_dav

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:Distributed Authoring and Versioning +(WebDAV) ±â´É
»óÅÂ:Extension
¸ðµâ¸í:dav_module
¼Ò½ºÆÄÀÏ:mod_dav.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ¾ÆÆÄÄ¡¿¡ WebDAV + ('Web-based Distributed Authoring and Versioning') class 1°ú + class 2 ±â´ÉÀ» Ãß°¡ÇÑ´Ù. WebDAV´Â ¿ø°Ý À¥¼­¹öÀÇ ÀÚ¿ø°ú + ÄÝ·º¼Ç(collection)À» (¿ªÁÖ; ÄÝ·º¼ÇÀº ÆÄÀϽýºÅÛÀÇ µð·ºÅ丮¿Í + °°Àº °³³äÀÌ´Ù) ¸¸µé°í, ¿Å±â°í, º¹»çÇÏ°í, Áö¿ï + ¼ö ÀÖµµ·Ï HTTP ÇÁ·ÎÅäÄÝÀ» È®ÀåÇÑ °ÍÀÌ´Ù.

+
+ +
top
+
+

WebDAV »ç¿ëÇϱâ

+

mod_dav¸¦ »ç¿ëÇÏ·Á¸é httpd.conf + ÆÄÀÏ¿¡ ¾Æ·¡°ú °°ÀÌ Ãß°¡ÇÑ´Ù:

+ +

Dav On

+ +

±×·¯¸é mod_dav_fs ¸ðµâÀÌ ±¸ÇöÇÏ´Â DAV + ÆÄÀϽýºÅÛ Á¦°øÀÚ(provider)¸¦ »ç¿ëÇÑ´Ù. ±×·¯¹Ç·Î ÀÌ ¸ðµâµµ + ¼­¹ö¿¡ °°ÀÌ ÄÄÆÄÀϵÇÀְųª LoadModule Áö½Ã¾î·Î ½ÇÇàÁß¿¡ + Àоîµé¿©¾ß ÇÑ´Ù.

+ +

¶Ç, DAV Àá±Ý(lock) µ¥ÀÌÅͺ£À̽ºÀÇ À§Ä¡¸¦ httpd.conf + ÆÄÀÏÀÇ Àü¿ª ºÎºÐ¿¡ DavLockDB Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + ÁöÁ¤ÇØ¾ß ÇÑ´Ù:

+ +

+ DavLockDB /usr/local/apache2/var/DavLock +

+ +

¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏ´Â User¿Í GroupÀº Àá±Ý µ¥ÀÌÅͺ£À̽º°¡ + ÀÖ´Â µð·ºÅ丮¿¡ ¾²±â ±ÇÇÑÀ» °¡Á®¾ß ÇÑ´Ù.

+ +

DAV¸¦ »ç¿ëÇÏ´Â À§Ä¡¿¡ Á¢±ÙÀ» Á¦ÇÑÇϱâÀ§ÇØ <Location> Áö½Ã¾î + ¾È¿¡ <Limit> + Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù. DAV Ŭ¶óÀ̾ðÆ®°¡ ÇѹøÀÇ ¿äû¿¡ + º¸³¾ ¼ö ÀÖ´Â ÃÖ´ë ¹ÙÀÌÆ®¼ö¸¦ Á¦ÇÑÇÏ·Á¸é LimitXMLRequestBody Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. + "ÀϹÝÀûÀÎ" LimitRequestBody + Áö½Ã¾î´Â DAV ¿äû°ú °ü°è¾ø´Ù.

+ +

Àüü ¿¹Á¦

+ DavLockDB /usr/local/apache2/var/DavLock
+
+ <Location /foo>
+ + Dav On
+
+ AuthType Basic
+ AuthName DAV
+ AuthUserFile user.passwd
+
+ <LimitExcept GET OPTIONS>
+ + require user admin
+ + </LimitExcept>
+ + </Location>
+

+ +

mod_dav´Â Greg SteinÀÌ ¸¸µç Apache 1.3¿ë mod_dav¸¦ + ±â¹ÝÀ¸·Î ¸¸µé¾ú´Ù. ¸ðµâ¿¡ ´ëÇÑ ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â ±× »çÀÌÆ®¸¦ + Âü°íÇ϶ó.

+
top
+
+

º¸¾È ¹®Á¦

+ +

DAV¸¦ »ç¿ëÇÏ¸é ¿ø°Ý Ŭ¶óÀ̾ðÆ®°¡ ¼­¹öÀÇ ÆÄÀÏÀ» Á¶ÀÛÇÒ + ¼ö Àֱ⶧¹®¿¡, mod_dav¸¦ »ç¿ëÇϱâ Àü¿¡ + ¼­¹ö°¡ ¾ÈÀüÇÑÁö Ưº°È÷ °ü½ÉÀ» °¡Á®¾ß ÇÑ´Ù.

+ +

¼­¹ö¿¡¼­ DAV°¡ °¡´ÉÇÑ À§Ä¡´Â ÀÎÁõÀ¸·Î º¸È£ÇØ¾ß ÇÑ´Ù. + HTTP Basic Authentication´Â ÃßõÇÏÁö ¾Ê´Â´Ù. ÃÖ¼ÒÇÑ + mod_auth_digest ¸ðµâÀÌ Á¦°øÇÏ´Â HTTP Digest + AuthenticationÀ» »ç¿ëÇØ¾ß ÇÑ´Ù. °ÅÀÇ ¸ðµç WebDAV Ŭ¶óÀ̾ðÆ®´Â + ÀÌ ÀÎÁõ ¹æ½ÄÀ» Áö¿øÇÑ´Ù. ¾Æ´Ï¸é SSL + ¿¬°á¿¡¼­ Basic AuthenticationÀ» »ç¿ëÇÒ ¼öµµ ÀÖ´Ù.

+ +

mod_dav°¡ ÆÄÀÏÀ» Á¶ÀÛÇÏ·Á¸é, ¾ÆÆÄÄ¡¸¦ + ½ÇÇàÇÏ´Â User¿Í + GroupÀº ÇØ´ç + µð·ºÅ丮¿Í ÆÄÀÏ¿¡ ¾²±â ±ÇÇÑÀ» °¡Á®¾ß ÇÑ´Ù. ¶Ç, »õ·Î »ý¼ºÇÑ + ÆÄÀÏÀº User¿Í + GroupÀÌ ¼ÒÀ¯ÇÏ°Ô + µÈ´Ù. ±×·¡¼­ ¾Æ¹«³ª ÀÌ °èÁ¤¿¡ Á¢±ÙÇÒ ¼ö ¾øµµ·Ï Ç϶ó. DAV + ÀúÀå¼Ò´Â ¾ÆÆÄÄ¡¸¸ Á¢±ÙÇÒ ¼ö ÀÖ´Ù°í °¡Á¤ÇÑ´Ù. ¾ÆÆÄÄ¡¸¦ ÅëÇÏÁö¾Ê°í + (¿¹¸¦ µé¾î FTP³ª ÆÄÀϽýºÅÛ µµ±¸¸¦ »ç¿ëÇÏ¿©) ÆÄÀÏÀ» ¼öÁ¤ÇÔÀ» + Çã¿ëÇÏ¸é ¾ÈµÈ´Ù.

+ +

mod_dav´Â ¿©·¯ ¼­ºñ½º°ÅºÎ °ø°ÝÀÇ ´ë»óÀÌ + µÉ ¼ö ÀÖ´Ù. LimitXMLRequestBody Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© Å« DAV ¿äûÀ» ÀÐÀ»¶§ ¸Þ¸ð¸®·®À» Á¦ÇÑÇÒ ¼ö ÀÖ´Ù. + DavDepthInfinity + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ¸¹Àº ¸Þ¸ð¸®¸¦ ¼Ò¸ðÇϱâÀ§ÇÑ ¸Å¿ì Å« ÀúÀå¼ÒÀÇ + PROPFIND ¿äûÀ» ¸·À» ¼ö ÀÖ´Ù. ´Ü¼øÈ÷ Ŭ¶óÀ̾ðÆ®°¡ + ¿©·¯ Å« ÆÄÀϵé·Î µð½ºÅ©°ø°£À» ä¿ì´Â ¼­ºñ½º°ÅºÎ °ø°Ýµµ °¡´ÉÇÏ´Ù. + ¾ÆÆÄÄ¡¿¡¼­ À̸¦ ¸·À» Á÷Á¢ÀûÀÎ ¹æ¹ýÀº ¾ø´Ù. ±×·¯¹Ç·Î ½Å·ÚÇÏÁö¾Ê´Â + »ç¿ëÀÚ¿¡°Ô DAV Á¢±ÙÀ» Çã¿ëÇÏÁö ¾Êµµ·ÏÇ϶ó.

+
top
+
+

º¹ÀâÇÑ ¼³Á¤

+ +

ÀϹÝÀûÀÎ Áú¹®Áß Çϳª´Â (PHP ½ºÅ©¸³Æ®, CGI ½ºÅ©¸³Æ® µî) + µ¿ÀûÆÄÀÏ ÀÛ¾÷À» À§ÇØ mod_dav¸¦ »ç¿ëÇÏ´Â + ¹æ¹ýÀÌ´Ù. ÀÌ´Â GET ¿äûÀÌ ÆÄÀÏ ³»¿ëÀ» ´Ù¿î·ÎµåÇÏÁö + ¾Ê°í Ç×»ó ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇϹǷΠ¾î·Æ´Ù. ÇØ°á¹æ¹ýÁß Çϳª´Â + ³»¿ë¿¡ µÎ°³ÀÇ URLÀ» ´ëÀÀÇÏ´Â °ÍÀÌ´Ù. ÇÑ URLÀº ½ºÅ©¸³Æ®¸¦ + ½ÇÇàÇÏ°í, ´Ù¸¥ URL·Î´Â ÆÄÀÏÀ» ´Ù¿î·ÎµåÇÏ¿© DAV·Î ÀÛ¾÷ÇÒ + ¼ö ÀÖ´Ù.

+ +

+Alias /phparea /home/gstein/php_files
+Alias /php-source /home/gstein/php_files
+<Location /php-source> + + DAV On
+ ForceType text/plain
+ +</Location> +

+ +

ÀÌ ¼³Á¤¿¡¼­ http://example.com/phparea´Â + PHP ½ºÅ©¸³Æ®ÀÇ °á°ú¸¦ º¸¿©ÁÖ°í, + http://example.com/php-source·Î´Â DAV Ŭ¶óÀ̾ðÆ®¿¡¼­ + ½ºÅ©¸³Æ®¸¦ ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+
+
top
+

Dav Áö½Ã¾î

+ + + + + + + +
¼³¸í:WebDAV HTTP ¸Þ½áµå¸¦ ½ÃÀÛÇÑ´Ù
¹®¹ý:Dav On|Off|provider-name
±âº»°ª:Dav Off
»ç¿ëÀå¼Ò:directory
»óÅÂ:Extension
¸ðµâ:mod_dav
+

ÁöÁ¤ÇÑ À§Ä¡¿¡¼­ WebDAV HTTP ¸Þ½áµå¸¦ »ç¿ëÇÏ·Á¸é + Dav Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù:

+ +

+ <Location /foo>
+ + Dav On
+ + </Location> +

+ +

On °ªÀº ½ÇÁ¦·Î mod_dav_fs + ¸ðµâÀÌ Á¦°øÇÏ´Â ±âº» Á¦°øÀÚÀÎ filesystemÀÇ + º°ÄªÀÌ´Ù. ¾î¶² À§Ä¡¿¡¼­ DAV¸¦ ½ÃÀÛÇϸé ÇÏÀ§°ø°£¿¡¼­ DAV¸¦ + »ç¿ë¾ÈÇϵµ·Ï ¼³Á¤ÇÒ ¼ö ¾øÀ½À» ÁÖÀÇÇ϶ó. ¿ÏÀüÇÑ + ¼³Á¤¿¹´Â À§ÀÇ ÀýÀ» Âü°íÇ϶ó.

+ +
+ ¼­¹ö¸¦ ¾ÈÀüÇÏ°Ô ±¸¼ºÇÒ¶§±îÁö WebDAVÀ» »ç¿ëÇÏÁö ¸¶¶ó. ±×·¸Áö + ¾ÊÀ¸¸é ´©±¸¶óµµ ¼­¹ö¸¦ ÅëÇØ ÆÄÀÏÀ» ºÐ¹èÇÒ ¼ö ÀÖ°Ô µÈ´Ù. +
+ +
+
top
+

DavDepthInfinity Áö½Ã¾î

+ + + + + + + +
¼³¸í:PROPFINDÀÇ Depth: Infinity ¿äûÀ» Çã°¡ÇÑ´Ù
¹®¹ý:DavDepthInfinity on|off
±âº»°ª:DavDepthInfinity off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory
»óÅÂ:Extension
¸ðµâ:mod_dav
+

DavDepthInfinity Áö½Ã¾î¸¦ »ç¿ëÇϸé + 'Depth: Infinity' Çì´õ¸¦ °¡Áø PROPFIND ¿äûÀ» + Çã°¡ÇÑ´Ù. ÀÌ·± ¿äûÀ» »ç¿ëÇÏ¿© ¼­ºñ½º°ÅºÎ °ø°ÝÀÌ °¡´ÉÇϱâ + ¶§¹®¿¡ ±âº»ÀûÀ¸·Î Çã¿ëÇÏÁö ¾Ê´Â´Ù.

+ +
+
top
+

DavMinTimeout Áö½Ã¾î

+ + + + + + + +
¼³¸í:¼­¹ö°¡ DAV ÀÚ¿ø¿¡ ´ëÇØ À¯ÁöÇÒ Àá±ÝÀÇ Ãּҽð£
¹®¹ý:DavMinTimeout seconds
±âº»°ª:DavMinTimeout 0
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory
»óÅÂ:Extension
¸ðµâ:mod_dav
+

Ŭ¶óÀ̾ðÆ®°¡ DAV ÀÚ¿ø¿¡ Àá±Ý(lock)À» ¿äûÇÒ¶§ ¼­¹ö°¡ + ¾Ë¾Æ¼­ Àá±ÝÀ» Á¦°ÅÇÒ ¼ö ÀÖ´Â ½Ã°£À» °°ÀÌ ¾Ë·ÁÁÙ ¼ö ÀÖ´Ù. ÀÌ °ªÀº + ´ÜÁö ¿äûÀÏ»ÓÀ̸ç, ¼­¹ö´Â Ŭ¶óÀ̾ðÆ®°¡ ¿äûÇÑ °ªÀ» ¹«½ÃÇÏ°í + Ŭ¶óÀ̾ðÆ®¿¡°Ô ÀÓÀÇÀÇ ½Ã°£À» ¾Ë·ÁÁÙ ¼ö ÀÖ´Ù.

+ +

DavMinTimeout Áö½Ã¾î´Â Ŭ¶óÀ̾ðÆ®¿¡°Ô + º¸³¾ ÃÖ¼Ò Àá±Ý ½Ã°£À» (ÃÊ´ÜÀ§) ÁöÁ¤ÇÑ´Ù. Microsoft Web Folders´Â + ±âº»°ªÀ¸·Î 120 Ãʸ¦ »ç¿ëÇÑ´Ù. DavMinTimeout¿¡ + (600 ÃÊ¿Í °°ÀÌ) ´õ ³ôÀº °ªÀ» »ç¿ëÇϸé Ŭ¶óÀ̾ðÆ®°¡ ³×Æ®¿÷ + Áö¿¬¶§¹®¿¡ Àá±ÝÀ» ÀҰԵǴ °æ¿ì¸¦ ÁÙÀÏ ¼ö ÀÖ´Ù.

+ +

¿¹Á¦

+ <Location /MSWord>
+ + DavMinTimeout 600
+ + </Location> +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dav_fs.html b/docs/manual/mod/mod_dav_fs.html new file mode 100644 index 00000000..44954c4d --- /dev/null +++ b/docs/manual/mod/mod_dav_fs.html @@ -0,0 +1,11 @@ +URI: mod_dav_fs.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_dav_fs.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_dav_fs.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_dav_fs.html.en b/docs/manual/mod/mod_dav_fs.html.en new file mode 100644 index 00000000..97dae47d --- /dev/null +++ b/docs/manual/mod/mod_dav_fs.html.en @@ -0,0 +1,97 @@ + + + +mod_dav_fs - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_dav_fs

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:filesystem provider for mod_dav
Status:Extension
Module Identifier:dav_fs_module
Source File:mod_dav_fs.c
+

Summary

+ +

This module requires the service of mod_dav. It acts as a support module for mod_dav and provides access to resources located in the + server's file system. The formal name of this provider is + filesystem. mod_dav backend providers + will be invoked by using the Dav + directive:

+ +

Example

+ Dav filesystem +

+ +

Since filesystem is the default provider for + mod_dav, you may simply use the value + On instead.

+
+

Directives

+ +

See also

+
+ +
top
+

DavLockDB Directive

+ + + + + + +
Description:Location of the DAV lock database
Syntax:DavLockDB file-path
Context:server config, virtual host
Status:Extension
Module:mod_dav_fs
+

Use the DavLockDB directive to specify + the full path to the lock database, excluding an extension. If + the path is not absolute, it will be taken relative to ServerRoot. The implementation of + mod_dav_fs uses a SDBM database to track user + locks.

+ + + +

Example

+ DavLockDB var/DavLock +

+ +

The directory containing the lock database file must be + writable by the User + and Group under which + Apache is running. For security reasons, you should create a + directory for this purpose rather than changing the permissions on + an existing directory. In the above example, Apache will create + files in the var/ directory under the ServerRoot with the base filename + DavLock and extension name chosen by the server.

+ + +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dav_fs.html.ja.euc-jp b/docs/manual/mod/mod_dav_fs.html.ja.euc-jp new file mode 100644 index 00000000..35728ebe --- /dev/null +++ b/docs/manual/mod/mod_dav_fs.html.ja.euc-jp @@ -0,0 +1,89 @@ + + + +mod_dav_fs - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_dav_fs

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:mod_dav ¤Î¤¿¤á¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥×¥í¥Ð¥¤¥À
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:dav_fs_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_dav_fs.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï mod_dav + ¤Î¥µ¡¼¥Ó¥¹¤òɬÍפȤ·¤Þ¤¹¡£mod_dav + ¤Î¥µ¥Ý¡¼¥È¥â¥¸¥å¡¼¥ë¤È¤·¤ÆÆ°ºî¤·¡¢¥µ¡¼¥Ð¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Ë + °ÌÃÖ¤¹¤ë¥ê¥½¡¼¥¹¤Ø¤Î¥¢¥¯¥»¥¹¤òÄ󶡤·¤Þ¤¹¡£¤³¤Î¥×¥í¥Ð¥¤¥À¤ÎÀµ¼°¤Ê̾Á°¤Ï + filesystem ¤Ç¤¹¡£mod_dav + ¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥Ð¥¤¥À¤Ï Dav + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æµ¯Æ°¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ Dav filesystem +

+ +

filesystem ¤Ï mod_dav + ¤Î¥Ç¥Õ¥©¥ë¥È¥×¥í¥Ð¥¤¥À¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¤«¤é¡¢Âå¤ï¤ê¤Ëñ¤Ë + On ¤È»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

DavLockDB ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:DAV ¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î°ÌÃÖ
¹½Ê¸:DavLockDB file-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_dav_fs
+

¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ø¤Î¥Õ¥ë¥Ñ¥¹¤ò¡¢³ÈÄ¥»Ò¤ò½ü¤¤¤¿·Á¤Ç + »ØÄꤹ¤ë¤Ë¤Ï¡¢DavLockDB + ¤ò»È¤¤¤Þ¤¹¡£¥Ñ¥¹¤¬ÀäÂХѥ¹¤Ç¤Ê¤±¤ì¤Ð¡¢ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤È²ò¼á¤µ¤ì¤Þ¤¹¡£ + mod_dav_fs ¼ÂÁõ¤Ç¤Ï¡¢¥æ¡¼¥¶¥í¥Ã¥¯¤ò + ÄÉÀפ¹¤ë¤¿¤á¤Ë SDBM ¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»È¤¤¤Þ¤¹¡£

+ + + +

Îã

+ DavLockDB logs/DavLock +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dav_fs.html.ko.euc-kr b/docs/manual/mod/mod_dav_fs.html.ko.euc-kr new file mode 100644 index 00000000..d1742c06 --- /dev/null +++ b/docs/manual/mod/mod_dav_fs.html.ko.euc-kr @@ -0,0 +1,96 @@ + + + +mod_dav_fs - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_dav_fs

+
+

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

+
+ + + +
¼³¸í:mod_davÀ» À§ÇÑ ÆÄÀϽýºÅÛ Á¦°øÀÚ
»óÅÂ:Extension
¸ðµâ¸í:dav_fs_module
¼Ò½ºÆÄÀÏ:mod_dav_fs.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº mod_dav ¼­ºñ½º¿¡ ÇÊ¿äÇÏ´Ù. + mod_dav¸¦ Áö¿øÇÏ´Â ¸ðµâ·Î ¼­¹öÀÇ ÆÄÀϽýºÅÛ¿¡ + ÀÖ´Â ÀÚ¿øÀ» Á¢±ÙÇÒ ¼ö ÀÖµµ·Ï ÇÑ´Ù. ÀÌ Á¦°øÀÚ(provider)ÀÇ + Á¤½Ä¸íĪÀº filesystemÀÌ´Ù. Dav Áö½Ã¾î¸¦ ÁöÁ¤ÇÏ¿© + mod_dav µÞ´Ü Á¦°øÀÚ¸¦ »ç¿ëÇÑ´Ù:

+ +

¿¹Á¦

+ Dav filesystem +

+ +

filesystemÀÌ mod_davÀÇ + ±âº» Á¦°øÀÚÀ̹ǷΠ´ë½Å OnÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

DavLockDB Áö½Ã¾î

+ + + + + + +
¼³¸í:DAV Àá±Ý µ¥ÀÌÅͺ£À̽º À§Ä¡
¹®¹ý:DavLockDB file-path
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Extension
¸ðµâ:mod_dav_fs
+

DavLockDB Áö½Ã¾î´Â Àá±Ý µ¥ÀÌÅͺ£À̽ºÀÇ + Àüü °æ·Î¸¦ È®ÀåÀÚ¸¦ Á¦¿ÜÇÏ°í ÁöÁ¤ÇÑ´Ù. Àý´ë°æ·Î°¡ ¾Æ´Ï¸é + ServerRoot¿¡ »ó´ë°æ·Î·Î + ó¸®ÇÑ´Ù. mod_dav_fs´Â Àá±ÝÀ» SDBM µ¥ÀÌÅͺ£À̽º¿¡ + ±â·ÏÇÑ´Ù.

+ + + +

¿¹Á¦

+ DavLockDB var/DavLock +

+ +

¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏ´Â User¿Í + GroupÀº Àá±Ý + µ¥ÀÌÅͺ£À̽º°¡ ÀÖ´Â µð·ºÅ丮¿¡ ¾²±â ±ÇÇÑÀ» °¡Á®¾ß ÇÑ´Ù. + º¸¾È»ó ÀÌÀ¯·Î ±âÁ¸ µð·ºÅ丮ÀÇ ±ÇÇÑÀ» ¹Ù²Ù±âº¸´Ù´Â Àá±Ý + µ¥ÀÌÅͺ£À̽º¿ë µð·ºÅ丮¸¦ ¸¸µé¾î¾ß ÇÑ´Ù. À§ÀÇ °æ¿ì ¾ÆÆÄÄ¡´Â + ServerRoot ¾Æ·¡ + var/ µð·ºÅ丮¿¡ ¼­¹ö°¡ ¼±ÅÃÇÑ È®Àå¸íÀ» °¡Áø + DavLock ÆÄÀÏÀ» ¸¸µç´Ù.

+ + +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dav_lock.html b/docs/manual/mod/mod_dav_lock.html new file mode 100644 index 00000000..495493ea --- /dev/null +++ b/docs/manual/mod/mod_dav_lock.html @@ -0,0 +1,7 @@ +URI: mod_dav_lock.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_dav_lock.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_dav_lock.html.en b/docs/manual/mod/mod_dav_lock.html.en new file mode 100644 index 00000000..119c2ab6 --- /dev/null +++ b/docs/manual/mod/mod_dav_lock.html.en @@ -0,0 +1,101 @@ + + + +mod_dav_lock - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_dav_lock

+
+

Available Languages:  en  | + ja 

+
+ + + + +
Description:generic locking module for mod_dav
Status:Extension
Module Identifier:dav_lock_module
Source File:mod_dav_lock.c
Compatibility:Available in version 2.1 and later
+

Summary

+ +

This module implements a generic locking API which can be used by any + backend provider of mod_dav. It requires at least + the service of mod_dav. But without a backend provider + which makes use of it, it's useless and should not be loaded into the + server. A sample backend module which actually utilizes + mod_dav_lock, is mod_dav_svn, the subversion provider module.

+ +

Note that mod_dav_fs does not need this + generic locking module, because it uses it's own more specialized + version.

+ +

In order to make mod_dav_lock functional, you just have + to specify the location of the lock database using the DavGenericLockDB directive described + below.

+ +

Developer's Note

+

In order to retrieve the pointer to the locking provider function, you + have to use the ap_lookup_provider API with the arguments + dav-lock, generic and 0.

+
+
+

Directives

+ +

See also

+
+ +
top
+

DavGenericLockDB Directive

+ + + + + + +
Description:Location of the DAV lock database
Syntax:DavGenericLockDB file-path
Context:server config, virtual host, directory
Status:Extension
Module:mod_dav_lock
+

Use the DavGenericLockDB directive to specify + the full path to the lock database, excluding an extension. If + the path is not absolute, it will be taken relative to ServerRoot. The implementation of + mod_dav_lock uses a SDBM database to track user + locks.

+ +

Example

+ DavGenericLockDB var/DavLock +

+ +

The directory containing the lock database file must be + writable by the User + and Group under which + Apache is running. For security reasons, you should create a + directory for this purpose rather than changing the permissions on + an existing directory. In the above example, Apache will create + files in the var/ directory under the ServerRoot with the base filename + DavLock and extension name chosen by the server.

+ + +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dav_lock.html.ja.euc-jp b/docs/manual/mod/mod_dav_lock.html.ja.euc-jp new file mode 100644 index 00000000..d3afc11c --- /dev/null +++ b/docs/manual/mod/mod_dav_lock.html.ja.euc-jp @@ -0,0 +1,105 @@ + + + +mod_dav_lock - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_dav_lock

+
+

Available Languages:  en  | + ja 

+
+ + + + +
ÀâÌÀ:mod_dav ÍѤÎÈÆÍÑ¥í¥Ã¥¯¥â¥¸¥å¡¼¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:dav_lock_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_dav_lock.c
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.1 °Ê¹ß
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï mod_dav ¤Î¤É¤Î¥Ð¥Ã¥¯¥¨¥ó¥É + ¤«¤é¤Ç¤â»È¤¨¤ëÈÆÍÑ¥í¥Ã¥¯ API ¤òÄ󶡤·¤Þ¤¹¡£ + »ÈÍѤˤϺÇÄã¸Â mod_dav + ¤òɬÍפȤ·¤Þ¤¹¤¬¡¢¤³¤ì¤òÍøÍѤ¹¤ë¥Ð¥Ã¥¯¥¨¥ó¥É¤¬Â¸ºß¤·¤Ê¤¤¤ÈÌò¤ËΩ¤¿¤Ê¤¤¤Î¤Ç¡¢ + ¤½¤Î¤è¤¦¤Ê¾ì¹ç¤Ï¥µ¡¼¥Ð¤ËÆɤ߹þ¤à¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + mod_dav_lock + ¤ò¼ÂºÝ¤ËÍøÍѤ¹¤ë¥Ð¥Ã¥¯¥¨¥ó¥É¥â¥¸¥å¡¼¥ë¤ÎÎã¤È¤·¤Æ¤Ï subversion + ¥×¥í¥Ð¥¤¥À¥â¥¸¥å¡¼¥ë¤Î mod_dav_svn ¤¬¤¢¤ê¤Þ¤¹¡£

+ +

mod_dav_fs ¤ÏÆò½¤µ¤ì¤¿ÀìÍѤΥС¼¥¸¥ç¥ó¤ò + »È¤¦¤¿¤á¡¢¤³¤ÎÈÆÍѥ⥸¥å¡¼¥ë¤ÏɬÍפʤ¤¤³¤È¤ËÃí°Õ¤·¤Æ + ¤¯¤À¤µ¤¤¡£

+ +

mod_dav_lock ¤òµ¡Ç½¤µ¤»¤ë¤Ë¤Ï¡¢ + °Ê²¼¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë DavGenericLockDB ¤ò»È¤Ã¤Æ + ¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¾ì½ê¤ò»ØÄꤹ¤ë¤À¤±¤Ç¤¹¡£

+ +

³«È¯¼Ô¸þ¤±¤Î¥á¥â

+

¥í¥Ã¥¯¤òÄ󶡤·¤Æ¤¤¤ë´Ø¿ô¤Ø¤Î¥Ý¥¤¥ó¥¿¤ò¼èÆÀ¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ + ap_lookup_provider API ¤ò¡¢°ú¿ô dav-lock, + generic, 0 ¤ò»ØÄꤷ¤Æ»È¤¦É¬Íפ¬ + ¤¢¤ê¤Þ¤¹¡£

+
+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

DavGenericLockDB ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:DAV ¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¾ì½ê
¹½Ê¸:DavGenericLockDB file-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_dav_lock
+

DavGenericLockDB ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤Ã¤Æ¡¢³ÈÄ¥»Ò¤ò½ü¤¤¤¿¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ø¤Î¥Õ¥ë¥Ñ¥¹¤ò + »ØÄꤷ¤Þ¤¹¡£ÀäÂХѥ¹¤Ç¤Ê¤¤¤È¤­¤Ï ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ + °·¤ï¤ì¤Þ¤¹¡£mod_dav_lock ¤Î¼ÂÁõ¤Ç¤Ï¥æ¡¼¥¶¤Î + ¥í¥Ã¥¯¤òÄÉÀפ¹¤ë¤Î¤Ë SDBM ¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»È¤¤¤Þ¤¹¡£

+ +

Îã

+ DavGenericLockDB var/DavLock +

+ +

¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤Î¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ï + Apache ¤¬¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë User + ¤È Group ¤Ë¤è¤Ã¤Æ + ½ñ¤­¹þ¤ß²Äǽ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÍýͳ¤«¤é¡¢ + ´û¸¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤òÊѹ¹¤¹¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢ + ÀìÍѤΥǥ£¥ì¥¯¥È¥ê¤òºî¤ë¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£¾å¤ÎÎã¤Ç¤Ï¡¢ + Apache ¤Ï ServerRoot ¤Î²¼¤Î var/ + ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¡¢¥Õ¥¡¥¤¥ë̾¤ÎËÜÂΤ¬ DavLock ¤Ç + ¥µ¡¼¥Ð¤¬ÁªÂò¤·¤¿³ÈÄ¥»Ò¤ò»ý¤Ä¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Þ¤¹¡£

+ + +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dbd.html b/docs/manual/mod/mod_dbd.html new file mode 100644 index 00000000..53de34db --- /dev/null +++ b/docs/manual/mod/mod_dbd.html @@ -0,0 +1,3 @@ +URI: mod_dbd.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_dbd.html.en b/docs/manual/mod/mod_dbd.html.en new file mode 100644 index 00000000..8c2c6a87 --- /dev/null +++ b/docs/manual/mod/mod_dbd.html.en @@ -0,0 +1,263 @@ + + + +mod_dbd - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_dbd

+
+

Available Languages:  en 

+
+ + + + +
Description:Manages SQL database connections
Status:Extension
Module Identifier:dbd_module
Source File:mod_dbd.c
Compatibility:Version 2.1 and later
+

Summary

+ +

mod_dbd manages SQL database connections using + apr_dbd. + It provides database connections on request to modules + requiring SQL database functions, and takes care of + managing databases with optimal efficiency and scalability + for both threaded and non-threaded MPMs.

+
+ +
top
+
+

Connection Pooling

+

This module manages database connections, in a manner + optimised for the platform. On non-threaded platforms, + it provides a persistent connection in the manner of + classic LAMP (Linux, Apache, Mysql, Perl/PHP/Python). + On threaded platform, it provides an altogether more + scalable and efficient connection pool, as + described in this article at ApacheTutor. mod_dbd supersedes + the modules presented in that article.

+
top
+
+

Apache DBD API

+

mod_dbd exports five functions for other modules + to use. The API is as follows:

+ + 
typedef struct {
+    apr_dbd_t *handle;
+    apr_dbd_driver_t *driver;
+    apr_hash_t *prepared;
+} ap_dbd_t;
+
+/* Export functions to access the database */
+
+/* acquire a connection that MUST be explicitly closed.
+ * Returns NULL on error
+ */
+AP_DECLARE(ap_dbd_t*) ap_dbd_open(apr_pool_t*, server_rec*);
+
+/* release a connection acquired with ap_dbd_open */
+AP_DECLARE(void) ap_dbd_close(server_rec*, ap_dbd_t*);
+
+/* acquire a connection that will have the lifetime of a request
+ * and MUST NOT be explicitly closed.  Return NULL on error.
+ * This is the preferred function for most applications.
+ */
+AP_DECLARE(ap_dbd_t*) ap_dbd_acquire(request_rec*);
+
+/* acquire a connection that will have the lifetime of a connection
+ * and MUST NOT be explicitly closed.  Return NULL on error.
+ */
+AP_DECLARE(ap_dbd_t*) ap_dbd_cacquire(request_rec*);
+
+/* Prepare a statement for use by a client module */
+AP_DECLARE(void) ap_dbd_prepare(server_rec*, const char*, const char*);
+
+/* Also export them as optional functions for modules that prefer it */
+APR_DECLARE_OPTIONAL_FN(ap_dbd_t*, ap_dbd_open, (apr_pool_t*, server_rec*));
+APR_DECLARE_OPTIONAL_FN(void, ap_dbd_close, (server_rec*, ap_dbd_t*));
+APR_DECLARE_OPTIONAL_FN(ap_dbd_t*, ap_dbd_acquire, (request_rec*));
+APR_DECLARE_OPTIONAL_FN(ap_dbd_t*, ap_dbd_cacquire, (conn_rec*));
+APR_DECLARE_OPTIONAL_FN(void, ap_dbd_prepare, (server_rec*, const char*, const char*));
+
+
top
+
+

SQL Prepared Statements

+

mod_dbd supports SQL prepared statements on behalf + of modules that may wish to use them. Each prepared statement + must be assigned a name (label), and they are stored in a hash: + the prepared field of an ap_dbd_t. + Hash entries are of type apr_dbd_prepared_t + and can be used in any of the apr_dbd prepared statement + SQL query or select commands.

+ +

It is up to dbd user modules to use the prepared statements + and document what statements can be specified in httpd.conf, + or to provide their own directives and use ap_dbd_prepare.

+
+
top
+

DBDExptime Directive

+ + + + + + +
Description:Keepalive time for idle connections
Syntax:DBDExptime time-in-seconds
Context:server config, virtual host
Status:Extension
Module:mod_dbd
+

Set the time to keep idle connections alive where the number + of connections specified in DBDKeep has been exceeded (threaded + platforms only).

+ +
+
top
+

DBDKeep Directive

+ + + + + + +
Description:Maximum sustained number of connections
Syntax:DBDKeep number
Context:server config, virtual host
Status:Extension
Module:mod_dbd
+

Set the maximum number of connections per process to be + sustained, other than for handling peak demand (threaded + platforms only).

+ +
+
top
+

DBDMax Directive

+ + + + + + +
Description:Maximum number of connections
Syntax:DBDMax number
Context:server config, virtual host
Status:Extension
Module:mod_dbd
+

Set the hard maximum number of connections per process + (threaded platforms only).

+ +
+
top
+

DBDMin Directive

+ + + + + + +
Description:Minimum number of connections
Syntax:DBDMin number
Context:server config, virtual host
Status:Extension
Module:mod_dbd
+

Set the minimum number of connections per process (threaded + platforms only).

+ +
+
top
+

DBDParams Directive

+ + + + + + +
Description:Parameters for database connection
Syntax:DBDParams +param1=value1[,param2=value2]
Context:server config, virtual host
Status:Extension
Module:mod_dbd
+

As required by the underlying driver. Typically this will be + used to pass whatever cannot be defaulted amongst username, + password, database name, hostname and port number for connection.

+

Connection string parameters for current drivers include:

+
+
MySQL
+
host, port, user, pass, dbname, sock
+
Oracle
+
user, pass, dbname, server
+
PostgreSQL
+
The connection string is passed straight through to PQconnectdb
+
SQLite2
+
The connection string is split on a colon, and part1:part2 is used as sqlite_open(part1, atoi(part2), NULL)
+
SQLite3
+
The connection string is passed straight through to sqlite3_open
+
+ +
+
top
+

DBDPersist Directive

+ + + + + + +
Description:Whether to use persistent connections
Syntax:DBDPersist 0|1
Context:server config, virtual host
Status:Extension
Module:mod_dbd
+

If set to 0, persistent and pooled connections are disabled. + A new database connection is opened when requested by a client, + and closed immediately on release. This option is for debugging + and low-usage servers.

+ +

The default is to enable a pool of persistent connections + (or a single LAMP-style persistent connection in the case of a + non-threaded server), and should almost always be used in operation.

+ +
+
top
+

DBDPrepareSQL Directive

+ + + + + + +
Description:Define an SQL prepared statement
Syntax:DBDPrepareSQL "SQL statement" label
Context:server config, virtual host
Status:Extension
Module:mod_dbd
+

For modules such as authentication that use repeatedly use a + single SQL statement, optimum performance is achieved by preparing + the statement at startup rather than every time it is used. + This directive prepares an SQL statement and assigns it a label.

+ +
+
top
+

DBDriver Directive

+ + + + + + +
Description:Specify an SQL driver
Syntax:DBDriver name
Context:server config, virtual host
Status:Extension
Module:mod_dbd
+

Selects an apr_dbd driver by name. The driver must be installed + on your system (on most systems, it will be a shared object or dll). + For example, DBDriver mysql will select the MySQL + driver in apr_dbd_mysql.so.

+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_deflate.html b/docs/manual/mod/mod_deflate.html new file mode 100644 index 00000000..dd4e6dce --- /dev/null +++ b/docs/manual/mod/mod_deflate.html @@ -0,0 +1,11 @@ +URI: mod_deflate.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_deflate.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_deflate.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_deflate.html.en b/docs/manual/mod/mod_deflate.html.en new file mode 100644 index 00000000..c21e4b58 --- /dev/null +++ b/docs/manual/mod/mod_deflate.html.en @@ -0,0 +1,376 @@ + + + +mod_deflate - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_deflate

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Compress content before it is delivered to the +client
Status:Extension
Module Identifier:deflate_module
Source File:mod_deflate.c
+

Summary

+ +

The mod_deflate module provides + the DEFLATE output filter that allows output from + your server to be compressed before being sent to the client over + the network.

+
+ +
top
+
+

Sample Configurations

+

This is a simple sample configuration for the impatient.

+ +

Compress only a few types

+ AddOutputFilterByType DEFLATE text/html text/plain text/xml +

+ +

The following configuration, while resulting in more compressed content, + is also much more complicated. Do not use this unless you fully understand + all the configuration details.

+ +

Compress everything except images

+ <Location />
+ + # Insert filter
+ SetOutputFilter DEFLATE
+
+ # Netscape 4.x has some problems...
+ BrowserMatch ^Mozilla/4 gzip-only-text/html
+
+ # Netscape 4.06-4.08 have some more problems
+ BrowserMatch ^Mozilla/4\.0[678] no-gzip
+
+ # MSIE masquerades as Netscape, but it is fine
+ BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
+ # Don't compress images
+ SetEnvIfNoCase Request_URI \
+ + \.(?:gif|jpe?g|png)$ no-gzip dont-vary
+ +
+ # Make sure proxies don't deliver the wrong content
+ Header append Vary User-Agent env=!dont-vary
+ + </Location> +

+ +
top
+
+

Enabling Compression

+ +

Output Compression

+

Compression is implemented by the DEFLATE + filter. The following directive + will enable compression for documents in the container where it + is placed:

+ +

+ SetOutputFilter DEFLATE +

+ +

Some popular browsers cannot handle compression of all content + so you may want to set the gzip-only-text/html note to + 1 to only allow html files to be compressed (see + below). If you set this to anything but 1 it + will be ignored.

+ +

If you want to restrict the compression to particular MIME types + in general, you may use the AddOutputFilterByType directive. Here is an example of + enabling compression only for the html files of the Apache + documentation:

+ +

+ <Directory "/your-server-root/manual">
+ + AddOutputFilterByType DEFLATE text/html
+ + </Directory> +

+ +

For browsers that have problems even with compression of all file + types, use the BrowserMatch directive to set the no-gzip + note for that particular browser so that no compression will be + performed. You may combine no-gzip with gzip-only-text/html to get the best results. In that case + the former overrides the latter. Take a look at the following + excerpt from the configuration example + defined in the section above:

+ +

+ BrowserMatch ^Mozilla/4 gzip-only-text/html
+ BrowserMatch ^Mozilla/4\.0[678] no-gzip
+ BrowserMatch \bMSIE !no-gzip !gzip-only-text/html +

+ +

At first we probe for a User-Agent string that + indicates a Netscape Navigator version of 4.x. These versions + cannot handle compression of types other than + text/html. The versions 4.06, 4.07 and 4.08 also + have problems with decompressing html files. Thus, we completely + turn off the deflate filter for them.

+ +

The third BrowserMatch + directive fixes the guessed identity of the user agent, because + the Microsoft Internet Explorer identifies itself also as "Mozilla/4" + but is actually able to handle requested compression. Therefore we + match against the additional string "MSIE" (\b means + "word boundary") in the User-Agent Header and turn off + the restrictions defined before.

+ +

Note

+ The DEFLATE filter is always inserted after RESOURCE + filters like PHP or SSI. It never touches internal subrequests. +
+

Note

+ There is a environment variable force-gzip, + set via SetEnv, which + will ignore the accept-encoding setting of your browser and will + send compressed output. +
+ + +

Output Decompression

+

The mod_deflate module also provides a filter for + inflating/uncompressing a gzip compressed response body. In order to activate + this feature you have to insert the INFLATE filter into + the outputfilter chain using SetOutputFilter or AddOutputFilter, for example:

+ +

+ <Location /dav-area>
+ + ProxyPass http://example.com/
+ SetOutputFilter INFLATE
+ + </Location> +

+ +

This Example will uncompress gzip'ed output from example.com, so other + filters can do further processing with it. +

+ + +

Input Decompression

+

The mod_deflate module also provides a filter for + decompressing a gzip compressed request body . In order to activate + this feature you have to insert the DEFLATE filter into + the input filter chain using SetInputFilter or AddInputFilter, for example:

+ +

+ <Location /dav-area>
+ + SetInputFilter DEFLATE
+ + </Location> +

+ +

Now if a request contains a Content-Encoding: + gzip header, the body will be automatically decompressed. + Few browsers have the ability to gzip request bodies. However, + some special applications actually do support request + compression, for instance some WebDAV clients.

+ +

Note on Content-Length

+

If you evaluate the request body yourself, don't trust + the Content-Length header! + The Content-Length header reflects the length of the + incoming data from the client and not the byte count of + the decompressed data stream.

+
+ +
top
+
+

Dealing with proxy servers

+ +

The mod_deflate module sends a Vary: + Accept-Encoding HTTP response header to alert proxies that + a cached response should be sent only to clients that send the + appropriate Accept-Encoding request header. This + prevents compressed content from being sent to a client that will + not understand it.

+ +

If you use some special exclusions dependent + on, for example, the User-Agent header, you must + manually configure an addition to the Vary header + to alert proxies of the additional restrictions. For example, + in a typical configuration where the addition of the DEFLATE + filter depends on the User-Agent, you should add:

+ +

+ Header append Vary User-Agent +

+ +

If your decision about compression depends on other information + than request headers (e.g. HTTP version), you have to set the + Vary header to the value *. This prevents + compliant proxies from caching entirely.

+ +

Example

+ Header set Vary * +

+
+
top
+

DeflateBufferSize Directive

+ + + + + + + +
Description:Fragment size to be compressed at one time by zlib
Syntax:DeflateBufferSize value
Default:DeflateBufferSize 8096
Context:server config, virtual host
Status:Extension
Module:mod_deflate
+

The DeflateBufferSize directive specifies + the size in bytes of the fragments that zlib should compress at one + time.

+ +
+
top
+

DeflateCompressionLevel Directive

+ + + + + + + + +
Description:How much compression do we apply to the output
Syntax:DeflateCompressionLevel value
Default:Zlib's default
Context:server config, virtual host
Status:Extension
Module:mod_deflate
Compatibility:This directive is available since Apache 2.0.45
+

The DeflateCompressionLevel directive specifies + what level of compression should be used, the higher the value, + the better the compression, but the more CPU time is required to + achieve this.

+

The value must between 1 (less compression) and 9 (more compression).

+ +
+
top
+

DeflateFilterNote Directive

+ + + + + + + +
Description:Places the compression ratio in a note for logging
Syntax:DeflateFilterNote [type] notename
Context:server config, virtual host
Status:Extension
Module:mod_deflate
Compatibility:type is available since Apache 2.0.45
+

The DeflateFilterNote directive + specifies that a note about compression ratios should be attached + to the request. The name of the note is the value specified for + the directive. You can use that note for statistical purposes by + adding the value to your access log.

+ +

Example

+ DeflateFilterNote ratio
+
+ LogFormat '"%r" %b (%{ratio}n) "%{User-agent}i"' deflate
+ CustomLog logs/deflate_log deflate +

+ +

If you want to extract more accurate values from your logs, you + can use the type argument to specify the type of data + left as note for logging. type can be one of:

+ +
+
Input
+
Store the byte count of the filter's input stream in the note.
+ +
Output
+
Store the byte count of the filter's output stream in the note.
+ +
Ratio
+
Store the compression ratio (output/input * 100) + in the note. This is the default, if the type argument + is omitted.
+
+ +

Thus you may log it this way:

+ +

Accurate Logging

+ DeflateFilterNote Input instream
+ DeflateFilterNote Output outstream
+ DeflateFilterNote Ratio ratio
+
+ LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate
+ CustomLog logs/deflate_log deflate +

+ +

See also

+ +
+
top
+

DeflateMemLevel Directive

+ + + + + + + +
Description:How much memory should be used by zlib for compression
Syntax:DeflateMemLevel value
Default:DeflateMemLevel 9
Context:server config, virtual host
Status:Extension
Module:mod_deflate
+

The DeflateMemLevel directive specifies + how much memory should be used by zlib for compression + (a value between 1 and 9).

+ +
+
top
+

DeflateWindowSize Directive

+ + + + + + + +
Description:Zlib compression window size
Syntax:DeflateWindowSize value
Default:DeflateWindowSize 15
Context:server config, virtual host
Status:Extension
Module:mod_deflate
+

The DeflateWindowSize directive specifies the + zlib compression window size (a value between 1 and 15). Generally, the + higher the window size, the higher can the compression ratio be expected.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_deflate.html.ja.euc-jp b/docs/manual/mod/mod_deflate.html.ja.euc-jp new file mode 100644 index 00000000..cf03ddb8 --- /dev/null +++ b/docs/manual/mod/mod_deflate.html.ja.euc-jp @@ -0,0 +1,385 @@ + + + +mod_deflate - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_deflate

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤ØÁ÷¤é¤ì¤ëÁ°¤Ë¥³¥ó¥Æ¥ó¥Ä¤ò°µ½Ì¤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:deflate_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_deflate.c
+

³µÍ×

+ +

mod_deflate ¥â¥¸¥å¡¼¥ë¤Ï DEFLATE + ½ÐÎÏ¥Õ¥£¥ë¥¿¤òÄ󶡤·¤Þ¤¹¡£¤³¤ì¤Ï¥µ¡¼¥Ð¤«¤é¤Î½ÐÎϤò¡¢¥Í¥Ã¥È¥ï¡¼¥¯¤ò + Ä̤·¤Æ¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ëÁ°¤Ë°µ½Ì¤¹¤ë¤³¤È¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£

+
+ +
top
+
+

¥µ¥ó¥×¥ëÀßÄê

+

²¼¤Ë¤»¤Ã¤«¤Á¤Ê¿Í¸þ¤±¤Î´Êñ¤ÊÀßÄêÎã¤ò¼¨¤·¤Þ¤¹¡£

+ +

¿ô¥¿¥¤¥×¤Î¤ß°µ½Ì¤¹¤ë

+ AddOutputFilterByType DEFLATE text/html text/plain text/xml +

+ +

°Ê²¼¤ÎÀßÄê¤Ï¥³¥ó¥Æ¥ó¥Ä¤ò¤è¤ê°µ½Ì¤·¤Þ¤¹¤¬¡¢¤º¤Ã¤ÈÊ£»¨¤ÊÀßÄê¤Ë¤Ê¤ê¤Þ¤¹¡£ + ÀßÄê¤Î¶ù¡¹¤Þ¤Ç¤è¤¯Íý²ò¤·¤Ê¤¤¤Ç»È¤ï¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£

+ +

²èÁü°Ê³°Á´¤Æ°µ½Ì¤¹¤ë

+ <Location />
+ + # Insert filter
+ SetOutputFilter DEFLATE
+
+ # Netscape 4.x has some problems...
+ BrowserMatch ^Mozilla/4 gzip-only-text/html
+
+ # Netscape 4.06-4.08 have some more problems
+ BrowserMatch ^Mozilla/4\.0[678] no-gzip
+
+ # MSIE masquerades as Netscape, but it is fine
+ # BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
+
+ # NOTE: Due to a bug in mod_setenvif up to Apache 2.0.48
+ # the above regex won't work. You can use the following
+ # workaround to get the desired effect:
+ BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html
+
+ # Don't compress images
+ SetEnvIfNoCase Request_URI \
+ + \.(?:gif|jpe?g|png)$ no-gzip dont-vary
+ +
+ # Make sure proxies don't deliver the wrong content
+ Header append Vary User-Agent env=!dont-vary
+ + </Location> +

+ +
top
+
+

°µ½Ì¤òÍ­¸ú¤Ë¤¹¤ë

+ +

Output Compression

+

°µ½Ìµ¡Ç½¤Ï DEFLATE ¥Õ¥£¥ë¥¿ + ¤Ë¤è¤ê¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤½¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¤¢¤ë + ¥³¥ó¥Æ¥ÊÃæ¤Î¥É¥­¥å¥á¥ó¥È¤ò°µ½Ì¤¹¤ë¤è¤¦¤Ë¤·¤Þ¤¹:

+ +

+ SetOutputFilter DEFLATE +

+ +

¤è¤¯»È¤ï¤ì¤Æ¤¤¤ë¥Ö¥é¥¦¥¶¤Ç¤Ï¡¢¤¹¤Ù¤Æ¤Î¥³¥ó¥Æ¥ó¥Ä¤ËÂФ¹¤ë + °µ½Ì¤ò°·¤¨¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤Ç¤¹¤«¤é¡¢gzip-only-text/html + ¥Î¡¼¥È¤ò 1 ¤Ë¤·¤Æ¡¢html ¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ¤Î¤ß + °µ½Ì¤¬Æ¯¤¯¤è¤¦¤Ë¤·¤¿Êý¤¬¤è¤¤¤«¤â¤·¤ì¤Þ¤»¤ó (°Ê²¼»²¾È) + ¤³¤ÎÃͤò 1 °Ê³°¤ÎÃͤËÀßÄꤷ¤¿¾ì¹ç¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£

+ +

Ä̾ÆÃÄê¤ÎMIME¥¿¥¤¥×¤Ë¤Ä¤¤¤Æ¤Î¤ß°µ½Ì¤·¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢ + AddOutputFilterByType + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Þ¤¹¡£¼¡¤Ë Apache ¤Î¥É¥­¥å¥á¥ó¥È¤Î html + ¥Õ¥¡¥¤¥ë¤Î¤ß¤Î°µ½Ì¤òÍ­¸ú¤Ë¤¹¤ëÎã¤ò¼¨¤·¤Þ¤¹¡£

+ +

+ <Directory "/your-server-root/manual">
+ + AddOutputFilterByType DEFLATE text/html
+ + </Directory> +

+ +

Á´¤Æ¤Î¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤Ç¤Î°µ½Ì¤ËÌäÂê¤òÊú¤¨¤Æ¤¤¤ë¥Ö¥é¥¦¥¶¤ËÂФ·¤Æ¤Ï¡¢ + BrowserMatch + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¡¢ÆÃÄê¤Î¥Ö¥é¥¦¥¶¤Ë no-gzip + ¥Î¡¼¥È¤ò¥»¥Ã¥È¤·¡¢°µ½Ì¤¬¹Ô¤Ê¤ï¤ì¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£ + no-gzip ¤È gzip-only-text/html + ¤òÁȤ߹ç¤ï¤»¤ë¤³¤È¤Ç¾å¼ê¤¯Âнè¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¾ì¹ç¡¢Á°¼Ô¤¬¸å¼Ô¤ò¥ª¡¼¥Ð¡¼¥é¥¤¥É¤·¤Þ¤¹¡£ + ¾åµ­¤ÎÀßÄêÎã¤ÎÈ´¿è¤ò + ¼¡¤Ë¼¨¤·¤Þ¤¹¤Î¤Ç¤´Í÷²¼¤µ¤¤¡£

+ +

+ BrowserMatch ^Mozilla/4 gzip-only-text/html
+ BrowserMatch ^Mozilla/4\.0[678] no-gzip
+ BrowserMatch \bMSIE !no-gzip !gzip-only-text/html +

+ +

¤Þ¤º»Ï¤á¤Ë User-Agent ʸ»úÎ󤫤é Netscape Navigator + 4.x ¤Ç¤¢¤ë¤«¤É¤¦¤«¤òÄ´¤Ù¤Þ¤¹¡£¤³¤ì¤é¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢ + text/html °Ê³°¤Î¥¿¥¤¥×¤Î°µ½Ì¤ò°·¤¦¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£ + 4.06, 4.07, 4.08 ¤Ï html ¥Õ¥¡¥¤¥ë¤Î¿­Ä¥¤Ë¤âÌäÂê¤òÊú¤¨¤Æ¤¤¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¤³¤ì¤é¤ËÂФ·¤Æ¤Ï¡¢´°Á´¤Ë deflate ¥Õ¥£¥ë¥¿¤ò¥ª¥Õ¤Ë¤·¤Þ¤¹¡£

+ +

3 ÈÖÌܤΠBrowserMatch + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¡¢¿ä¬¤·¤¿¥æ¡¼¥¶¡¼¥¨¡¼¥¸¥§¥ó¥È¤ò½¤Àµ¤·¤Þ¤¹¡£ + ¤Ê¤¼¤Ê¤é Microsoft Internet Explorer ¤â "Mozilla/4" ¤ÈÆÃÄꤵ¤ì¤Þ¤¹¤¬¡¢ + ¤³¤ì¤é¤Ï¼ÂºÝ¤Ë¤Ï°µ½Ì¤ò°·¤¦¤³¤È¤¬¤Ç¤­¤ë¤«¤é¤Ç¤¹¡£ + User-Agent ¥Ø¥Ã¥À¤ò "MSIE" + (\b ¤Ï¡Öñ¸ì¤Î¶­³¦¡×¤ò°ÕÌ£¤·¤Þ¤¹) ¤ÎÄɲÃʸ»ú¤Ç¸¡ºº¤·¤Æ¡¢ + ¤³¤ì°ÊÁ°¤ËÀßÄꤷ¤¿À©¸Â¤òºÆ¤Ó²ò½ü¤·¤Þ¤¹¡£

+ +

Ãí

+ DEFLATE ¥Õ¥£¥ë¥¿¤Ïɬ¤º¡¢PHP ¤ä SSI ¤È¤¤¤Ã¤¿ RESOURCE + ¥Õ¥£¥ë¥¿¤Î¸å¤Ë¤Ê¤ê¤Þ¤¹¡£ + DEFLATE ¥Õ¥£¥ë¥¿¤ÏÆâÉôŪ¤Ê¥µ¥Ö¥ê¥¯¥¨¥¹¥È¤ò´ØÃΤ·¤Þ¤»¤ó¡£ +
+

Ãí

+ SetEnv ¤ÇÀßÄꤵ¤ì¤ë + force-gzip ´Ä¶­ÊÑ¿ô¤¬¤¢¤ê¤Þ¤¹¤¬¡¢¤³¤ì¤Ï + ¥Ö¥é¥¦¥¶¤Î accept-encoding ÀßÄê¤ò̵»ë¤·¡¢°µ½Ì¤·¤¿½ÐÎϤò¤·¤Þ¤¹¡£ +
+ + +

½ÐÎϤο­Ä¹

+

mod_deflate ¥â¥¸¥å¡¼¥ë¤Ï¡¢gzip °µ½Ì¤µ¤ì¤¿¥ì¥¹¥Ý¥ó¥¹ + ËÜʸ¤ò inflate/uncompress ¤¹¤ë¥Õ¥£¥ë¥¿¤âÄ󶡤·¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Îµ¡Ç½¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢SetOutputFilter + ¤ä AddOutputFilter ¤ò»È¤Ã¤Æ¡¢ + INFLATE ¥Õ¥£¥ë¥¿¤ò½ÐÎÏ¥Õ¥£¥ë¥¿¥Á¥§¥¤¥ó¤ËÁÞÆþ¤·¤Þ¤¹¡£ + Î㤨¤Ð¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

+ <Location /dav-area>
+ + ProxyPass http://example.com/
+ SetOutputFilter INFLATE
+ + </Location> +

+ +

¤³¤ÎÎã¤Ç¤Ï¡¢example.com ¤«¤é¤Î gzip °µ½Ì¤µ¤ì¤¿½ÐÎϤò¿­Ä¹¤·¡¢ + ¤½¤Î¾¤Î¥Õ¥£¥ë¥¿¤¬¤µ¤é¤Ë¤½¤Î½ÐÎϤò½èÍý¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ +

+ + +

ÆþÎϤο­Ä¥

+

mod_deflate ¥â¥¸¥å¡¼¥ë¤Ï¡¢gzip + ¤Ç°µ½Ì¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥ÈËÜÂΤò¿­Ä¥¤¹¤ë¥Õ¥£¥ë¥¿¤âÄ󶡤·¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Îµ¡Ç½¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢SetInputFilter + ¤« AddInputFilter ¤ò»ÈÍѤ·¤Æ¡¢ + DEFLATE ¥Õ¥£¥ë¥¿¤òÆþÎÏ¥Õ¥£¥ë¥¿¥Á¥§¥¤¥ó¤ËÁȤ߹þ¤ß¤Þ¤¹¡£ + Î㤨¤Ð¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

+ <Location /dav-area>
+ + SetInputFilter DEFLATE
+ + </Location> +

+ +

¤³¤ÎÀßÄê¤Ç¤¢¤ì¤Ð¡¢Content-Encoding: gzip + ¥Ø¥Ã¥À¤ò´Þ¤à¥ê¥¯¥¨¥¹¥È¤¬Íè¤ë¤È¡¢ËÜÂΤϼ«Æ°Åª¤Ë¿­Ä¥¤µ¤ì¤Þ¤¹¡£ + gzip ¥ê¥¯¥¨¥¹¥ÈËÜÂΤòÁ÷¿®¤¹¤ë¥Ö¥é¥¦¥¶¤Ï¤¢¤Þ¤ê¤¢¤ê¤Þ¤»¤ó¡£ + ¤·¤«¤·¡¢Î㤨¤Ð WebDAV + ¥¯¥é¥¤¥¢¥ó¥È¤Î´ö¤Ä¤«¤Ê¤É¡¢ÆÃÊ̤ʥ¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ç¥ê¥¯¥¨¥¹¥È¤Î + °µ½Ì¤ò¼ÂºÝ¤Ë¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£

+ +

Content-Length ¤Ë´Ø¤¹¤ëÃí°Õ

+

¥ê¥¯¥¨¥¹¥ÈËÜÂΤ½¤ì¼«ÂΤòɾ²Á¤¹¤ë¾ì¹ç¤Ï¡¢Content-Length + ¥Ø¥Ã¥À¤ò¿®ÍѤ·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£Content-Length ¥Ø¥Ã¥À¤Ï¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤«¤éÁ÷¿®¤µ¤ì¤ë¥Ç¡¼¥¿¤ÎŤµ¤òÈ¿±Ç¤·¤Æ¤¤¤ë¤Î¤Ç¤¢¤Ã¤Æ¡¢ + ¿­Ä¥¤µ¤ì¤¿¥Ç¡¼¥¿¥¹¥È¥ê¡¼¥à¤Î¥Ð¥¤¥È¥«¥¦¥ó¥È¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+
+ +
top
+
+

Proxy ¥µ¡¼¥Ð¤Ç¤Î°·¤¤

+ +

mod_deflate ¥â¥¸¥å¡¼¥ë¤Ï Vary: Accept-Encoding + HTTP ±þÅú¥Ø¥Ã¥À¤òÁ÷¿®¤·¤Æ¡¢Å¬ÀÚ¤Ê Accept-Encoding + ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤òÁ÷¿®¤¹¤ë¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ·¤Æ¤Î¤ß¡¢ + ¥×¥í¥¯¥·¥µ¡¼¥Ð¤¬¥­¥ã¥Ã¥·¥å¤·¤¿±þÅú¤òÁ÷¿®¤¹¤ë¤è¤¦¤ËÃí°Õ¤ò´­µ¯¤·¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Ë¤·¤Æ¡¢°µ½Ì¤ò°·¤¦¤³¤È¤Î¤Ç¤­¤Ê¤¤¥¯¥é¥¤¥¢¥ó¥È¤Ë + °µ½Ì¤µ¤ì¤¿ÆâÍƤ¬Á÷¤é¤ì¤ë¤³¤È¤Î¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

¤â¤·ÆÃÊ̤˲¿¤«¤Ë°Í¸¤·¤Æ½ü³°¤·¤¿¤¤¾ì¹ç¡¢Î㤨¤Ð User-Agent + ¥Ø¥Ã¥À¤Ê¤É¤Ë°Í¸¤·¤Æ¤¤¤ë¾ì¹ç¡¢¼êÆ°¤Ç Vary ¥Ø¥Ã¥À¤òÀßÄꤷ¤Æ¡¢ + ÄɲäÎÀ©¸Â¤Ë¤Ä¤¤¤Æ¥×¥í¥¯¥·¥µ¡¼¥Ð¤ËÃí°Õ¤ò¹Ô¤Ê¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£ + Î㤨¤Ð User-Agent ¤Ë°Í¸¤·¤Æ DEFLATE + ¤òÄɲ乤ëŵ·¿Åª¤ÊÀßÄê¤Ç¤Ï¡¢¼¡¤Î¤è¤¦¤ËÄɲ乤뤳¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

+ Header append Vary User-Agent +

+ +

¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À°Ê³°¤Î¾ðÊó (Î㤨¤Ð HTTP ¥Ð¡¼¥¸¥ç¥ó) + ¤Ë°Í¸¤·¤Æ°µ½Ì¤¹¤ë¤«¤É¤¦¤«·è¤á¤ë¾ì¹ç¡¢ + Vary ¥Ø¥Ã¥À¤ò * ¤ËÀßÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Ë¤¹¤ë¤È¡¢»ÅÍͤ˽àµò¤·¤¿¥×¥í¥¯¥·¤Ï¥­¥ã¥Ã¥·¥å¤òÁ´¤¯¹Ô¤Ê¤ï¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£

+ +

Îã

+ Header set Vary * +

+
+
top
+

DeflateBufferSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:zlib ¤¬°ìÅ٤˰µ½Ì¤¹¤ë²ô¤ÎÂ礭¤µ
¹½Ê¸:DeflateBufferSize value
¥Ç¥Õ¥©¥ë¥È:DeflateBufferSize 8096
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_deflate
+

DeflateBufferSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + zlib ¤¬°ìÅ٤˰µ½Ì¤¹¤ë²ô¤ÎÂ礭¤µ¤ò¥Ð¥¤¥Èñ°Ì¤Ç»ØÄꤷ¤Þ¤¹¡£

+ +
+
top
+

DeflateCompressionLevel ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:½ÐÎϤËÂФ·¤Æ¹Ô¤Ê¤¦°µ½Ì¤ÎÄøÅÙ
¹½Ê¸:DeflateCompressionLevel value
¥Ç¥Õ¥©¥ë¥È:Zlib ¤Î¥Ç¥Õ¥©¥ë¥È
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_deflate
¸ß´¹À­:This directive is available since Apache 2.0.45
+

DeflateCompressionLevel ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + °µ½Ì¤ÎÄøÅÙ¤òÀßÄꤷ¤Þ¤¹¡£Â礭¤ÊÃͤǤϡ¢¤è¤ê°µ½Ì¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¤¬¡¢ + CPU »ñ¸»¤ò¾ÃÈñ¤·¤Þ¤¹¡£

+

ÃÍ¤Ï 1 (Äã°µ½Ì) ¤«¤é 9 (¹â°µ½Ì) ¤Ç¤¹¡£

+ +
+
top
+

DeflateFilterNote ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥í¥®¥ó¥°ÍѤ˰µ½ÌÈæ¤ò¥á¥â¤ËÄɲÃ
¹½Ê¸:DeflateFilterNote [type] notename
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_deflate
¸ß´¹À­:type is available since Apache 2.0.45
+

DeflateFilterNote ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + °µ½ÌÈæ¤Ë´Ø¤¹¤ë¥á¥â¤¬¥ê¥¯¥¨¥¹¥È¤ËÉղ䵤ì¤ë¤³¤È¤ò»ØÄꤷ¤Þ¤¹¡£ + ¥á¥â (note) ¤Î̾Á°¤Ï¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë»ØÄꤵ¤ì¤¿ÃͤǤ¹¡£ + ¥á¥â¤Ï¥¢¥¯¥»¥¹¥í¥°¤Ë + Ãͤòµ­Ï¿¤·¡¢Åý·×¤ò¼è¤ëÌÜŪ¤Ë¤â»È¤¨¤Þ¤¹¡£

+ +

Îã

+ DeflateFilterNote ratio
+
+ LogFormat '"%r" %b (%{ratio}n) "%{User-agent}i"' deflate
+ CustomLog logs/deflate_log deflate +

+ +

¥í¥°¤«¤é¤â¤Ã¤ÈÀºÌ©¤ÊÃͤòÃê½Ð¤·¤¿¤¤¾ì¹ç¤Ï¡¢type + °ú¿ô¤ò»ÈÍѤ·¤Æ¡¢¥Ç¡¼¥¿¥¿¥¤¥×¤ò¥í¥°¤Î¥á¥â¤È¤·¤Æ»Ä¤¹¤è¤¦¤Ë»ØÄê¤Ç¤­¤Þ¤¹¡£ + type ¤Ï¼¡¤Î¤¦¤Á¤Î°ì¤Ä¤Ç¤¹¡£

+ +
+
Input
+
¥Õ¥£¥ë¥¿¤ÎÆþÎÏ¥¹¥È¥ê¡¼¥à¤Î¥Ð¥¤¥È¥«¥¦¥ó¥È¤ò¥á¥â¤ËÊݸ¤¹¤ë¡£
+ +
Output
+
¥Õ¥£¥ë¥¿¤Î½ÐÎÏ¥¹¥È¥ê¡¼¥à¤Î¥Ð¥¤¥È¥«¥¦¥ó¥È¤ò¥á¥â¤ËÊݸ¤¹¤ë¡£
+ +
Ratio
+
°µ½ÌΨ (½ÐÎÏ / ÆþÎÏ * 100) ¤ò¥á¥â¤ËÊݸ¤¹¤ë¡£ + type °ú¿ô¤ò¾Êά¤·¤¿¾ì¹ç¤Ï¡¢¤³¤ì¤¬¥Ç¥Õ¥©¥ë¥È¤È¤Ê¤ê¤Þ¤¹¡£
+
+ +

¤Þ¤È¤á¤ë¤È¡¢¼¡¤Î¤è¤¦¤Ë¥í¥°¤ò¼è¤ë¤³¤È¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£

+ +

ÀºÌ©¤Ê¥í¥°ºÎ¼è

+ DeflateFilterNote Input instream
+ DeflateFilterNote Output outstream
+ DeflateFilterNote Ratio ratio
+
+ LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate
+ CustomLog logs/deflate_log deflate +

+ +

»²¾È

+ +
+
top
+

DeflateMemLevel ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:zlib ¤¬°µ½Ì¤Ë»È¤¦¥á¥â¥ê¤Î¥ì¥Ù¥ë¤ò»ØÄê
¹½Ê¸:DeflateMemLevel value
¥Ç¥Õ¥©¥ë¥È:DeflateMemLevel 9
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_deflate
+

DeflateMemLevel ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + zlib ¤¬°µ½Ì¤Ë»È¤¦¥á¥â¥ê¤Î¥ì¥Ù¥ë¤òÀßÄꤷ¤Þ¤¹ (1 ¤«¤é 9 ¤Î´Ö¤ÎÃÍ)¡£ + (ÌõÃí: 2 ¤òÄì¤È¤¹¤ëÂпô¤ÎÃͤˤʤê¤Þ¤¹¡£ + 8 ÄøÅÙ¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£)

+ +
+
top
+

DeflateWindowSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:Zlib ¤Î°µ½ÌÍÑ¥¦¥£¥ó¥É¥¦¤ÎÂ礭¤µ
¹½Ê¸:DeflateWindowSize value
¥Ç¥Õ¥©¥ë¥È:DeflateWindowSize 15
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_deflate
+

DeflateWindowSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + zlib ¤Î°µ½ÌÍÑ¥¦¥£¥ó¥É¥¦ (ÌõÃí: zlib ¤Ç»ÈÍѤµ¤ì¤ëÍúÎò¥Ð¥Ã¥Õ¥¡) + ¤ÎÂ礭¤µ¤ò»ØÄꤷ¤Þ¤¹ (1 ¤«¤é 15 ¤Î´Ö¤ÎÃÍ)¡£ + °ìÈÌŪ¤ËÂ礭¤Ê¥¦¥£¥ó¥É¥¦¥µ¥¤¥º¤ò»ÈÍѤ¹¤ë¤È°µ½ÌΨ¤¬¸þ¾å¤·¤Þ¤¹¡£ + (ÌõÃí: 2 ¤òÄì¤È¤¹¤ëÂпô¤ÎÃͤˤʤê¤Þ¤¹¡£ + 8 ¤«¤é 15 ¤Ë¤¹¤ë¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£)

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_deflate.html.ko.euc-kr b/docs/manual/mod/mod_deflate.html.ko.euc-kr new file mode 100644 index 00000000..c1feb297 --- /dev/null +++ b/docs/manual/mod/mod_deflate.html.ko.euc-kr @@ -0,0 +1,368 @@ + + + +mod_deflate - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_deflate

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:³»¿ëÀ» Ŭ¶óÀ̾ðÆ®·Î º¸³»±â Àü¿¡ ¾ÐÃàÇÑ´Ù
»óÅÂ:Extension
¸ðµâ¸í:deflate_module
¼Ò½ºÆÄÀÏ:mod_deflate.c
+

¿ä¾à

+ +

mod_deflate ¸ðµâÀº ¼­¹öÀÇ Ãâ·ÂÀ» ³×Æ®¿÷À¸·Î + Ŭ¶óÀ̾ðÆ®¿¡ º¸³»±â Àü¿¡ ¾ÐÃàÇÏ´Â DEFLATE Ãâ·ÂÇÊÅ͸¦ + Á¦°øÇÑ´Ù.

+
+ +
top
+
+

°ßº» ¼³Á¤

+

±ÞÇÑ »ç¶÷À» À§ÇÑ °ßº» ¼³Á¤ÀÌ´Ù.

+ +

ÀϺΠtype¸¸ ¾ÐÃà

+ AddOutputFilterByType DEFLATE text/html text/plain text/xml +

+ +

¾Æ·¡ ¼³Á¤Àº ¿ä¾àÇÏ¿´Áö¸¸ ±×·¡µµ º¹ÀâÇÏ´Ù. ¼³Á¤À» ¿ÏÀüÈ÷ + ÀÌÇØÇÑ ÈÄ »ç¿ëÇ϶ó.

+ +

À̹ÌÁö¸¦ Á¦¿ÜÇÑ ¸ðµç °ÍÀ» ¾ÐÃà

+ <Location />
+ + # ÇÊÅ͸¦ Ãß°¡ÇÑ´Ù
+ SetOutputFilter DEFLATE
+
+ # Netscape 4.x¿¡ ¹®Á¦°¡ ÀÖ´Ù...
+ BrowserMatch ^Mozilla/4 gzip-only-text/html
+
+ # Netscape 4.06-4.08¿¡ ´õ ¹®Á¦°¡ ÀÖ´Ù
+ BrowserMatch ^Mozilla/4\.0[678] no-gzip
+
+ # MSIEÀº Netscape¶ó°í ÀÚ½ÅÀ» ¾Ë¸®Áö¸¸, ¹®Á¦°¡ ¾ø´Ù
+ # BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
+
+ # ÁÖÀÇ: ¾ÆÆÄÄ¡ 2.0.48±îÁö mod_setenvifÀÇ ¹ö±×¶§¹®¿¡
+ # À§ÀÇ Á¤±ÔÇ¥Çö½ÄÀº µ¿ÀÛÇÏÁö ¾Ê´Â´Ù. ¿øÇÏ´Â È¿°ú¸¦
+ # ¾ò±âÀ§ÇØ ´ÙÀ½°ú °°ÀÌ ¼öÁ¤ÇÏ¿© »ç¿ëÇÑ´Ù:
+ BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html
+
+ # À̹ÌÁö¸¦ ¾ÐÃàÇÏÁö ¾Ê´Â´Ù
+ SetEnvIfNoCase Request_URI \
+ + \.(?:gif|jpe?g|png)$ no-gzip dont-vary
+ +
+ # ÇÁ·Ï½Ã°¡ À߸øµÈ ³»¿ëÀ» Àü´ÞÇÏÁö¾Êµµ·Ï ÇÑ´Ù
+ Header append Vary User-Agent env=!dont-vary
+ + </Location> +

+ +
top
+
+

¾ÐÃàÇϱâ

+ +

Ãâ·Â ¾ÐÃà

+

DEFLATE ÇÊÅÍ°¡ + ¾ÐÃàÀ» ÇÑ´Ù. ´ÙÀ½ Áö½Ã¾î´Â Áö½Ã¾î°¡ ÀÖ´Â À§Ä¡ÀÇ ¹®¼­¸¦ + ¾ÐÃàÇÑ´Ù:

+ +

+ SetOutputFilter DEFLATE +

+ +

¸ðµç ³»¿ëÀ» ¾ÐÃàÇϸé ó¸®ÇÏÁö ¸øÇÏ´Â ºê¶ó¿ìÀú°¡ Àֱ⶧¹®¿¡ + html ÆÄÀϸ¸À» ¾ÐÃàÇϱâÀ§ÇØ (¾Æ·¡ Âü°í) + gzip-only-text/htmlÀ» 1·Î ¼³Á¤ÇÒÁöµµ + ¸ð¸¥´Ù. À̸¦ 1ÀÌ ¾Æ´Ñ °ªÀ¸·Î ¼³Á¤Çϸé + ¹«½ÃÇÑ´Ù.

+ +

º¸Åë Ưº°ÇÑ MIME type¸¸ ¾ÐÃàÇÏ·Á¸é AddOutputFilterByType Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. + ´ÙÀ½ ¼³Á¤Àº html ÆÄÀϸ¸À» ¾ÐÃàÇÑ´Ù:

+ +

+ <Directory "/your-server-root/manual">
+ + AddOutputFilterByType DEFLATE text/html
+ + </Directory> +

+ +

¾ÐÃàÇÑ ÆÄÀÏÀ» ó¸®ÇÏÁö ¸øÇÏ´Â ºê¶ó¿ìÀú¿¡°Ô´Â ¾ÐÃàÇÏÁö¾Ê°í + º¸³»±æÀ§ÇØ BrowserMatch Áö½Ã¾î¿¡ no-gzipÀ» + ¼³Á¤ÇÑ´Ù. ÃÖÀûÀÇ °á°ú¸¦ ¾ò±âÀ§ÇØ no-gzip°ú + gzip-only-text/htmlÀ» °°ÀÌ »ç¿ëÇÒ ¼ö ÀÖ´Ù. + ÀÌ °æ¿ì ÀüÀÚ°¡ ÈÄÀÚ¸¦ ¹«½ÃÇÑ´Ù. À§ ÀýÀÇ ¼³Á¤ ¿¹Á¦ ÀϺθ¦ »ìÆ캸ÀÚ:

+ +

+ BrowserMatch ^Mozilla/4 gzip-only-text/html
+ BrowserMatch ^Mozilla/4\.0[678] no-gzip
+ BrowserMatch \bMSIE !no-gzip !gzip-only-text/html +

+ +

¸ÕÀú User-Agent ¹®ÀÚ¿­À» º¸°í Netscape + Navigator ¹öÀü 4.xÀÎÁö °Ë»çÇÑ´Ù. ÀÌ ¹öÀüÀº text/htmlÀÌ + ¾Æ´Ñ typeÀÇ ¾ÐÃàÀ» ó¸®ÇÏÁö ¸øÇÑ´Ù. ¹öÀü 4.06, 4.07, 4.08Àº + html ÆÄÀÏ ¾ÐÃàÀ» ó¸®Çϴ´뵵 ¹®Á¦°¡ ÀÖ´Ù. ±×·¡¼­ ¿ì¸®´Â + ÀÌ °æ¿ì deflate ÇÊÅ͸¦ ¿ÏÀüÈ÷ »ç¿ëÇÏÁö¾Ê´Â´Ù.

+ +

¼¼¹ø° BrowserMatch + Áö½Ã¾î´Â Microsoft Internet Explorer°¡ ÀÚ½ÅÀ» "Mozilla/4"·Î + ¾Ë¸®Áö¸¸ ¾ÐÃàµÈ ¿äûÀ» ó¸®ÇÒ ¼ö Àֱ⶧¹®¿¡ user agent + ÃßÃøÀ» ¼öÁ¤ÇÑ´Ù. User-Agent Çì´õ¿¡¼­ "MSIE" + (\b´Â "´Ü¾î °æ°è"¸¦ ¶æÇÑ´Ù) ¹®ÀÚ¿­À» ¹ß°ßÇϸé + ¾Õ¿¡¼­ ¼³Á¤ÇÑ Á¦¾àÀ» Ǭ´Ù.

+ +

ÁÖÀÇ

+ DEFLATE ÇÊÅÍ´Â Ç×»ó PHP³ª SSI¿Í °°Àº RESOURCE + ÇÊÅÍ µÚ¿¡ µé¾î°£´Ù. ¶Ç, ³»ºÎ ÇÏÀ§¿äû(subrequest)¿¡ ¿µÇâÀ» + ÁÖÁö ¾Ê´Â´Ù. +
+

ÁÖÀÇ

+ SetEnv·Î + force-gzip ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÏ¸é ºê¶ó¿ìÀúÀÇ + accept-encoding ¼³Á¤À» ¹«½ÃÇÏ°í ¾ÐÃàµÈ °á°ú¸¦ º¸³½´Ù. +
+ + +

Ãâ·Â ¾ÐÃàÇ®±â

+

mod_deflate ¸ðµâÀº gzipÀ¸·Î ¾ÐÃàµÈ + ÀÀ´ä ³»¿ëÀ» Ǫ´Â ÇÊÅ͵µ Á¦°øÇÑ´Ù. ÀÌ ±â´ÉÀ» »ç¿ëÇÏ·Á¸é + ´ÙÀ½°ú °°ÀÌ SetOutputFilter³ª AddOutputFilter¸¦ »ç¿ëÇÏ¿© + Ãâ·ÂÇÊÅͼø¼­¿¡ INFLATE ÇÊÅ͸¦ Ãß°¡ÇÑ´Ù.

+ +

+ <Location /dav-area>
+ + ProxyPass http://example.com/
+ SetOutputFilter INFLATE
+ + </Location> +

+ +

ÀÌ ¿¹Á¦´Â example.comÀÌ º¸³½ gzipÀ¸·Î ¾ÐÃàµÈ °á°úÀÇ + ¾ÐÃàÀ» Ç®¾î¼­, ´Ù¸¥ ÇÊÅÍ°¡ ´õ ó¸®ÇÒ ¼ö ÀÖµµ·Ï ÇÑ´Ù. +

+ + +

ÀÔ·Â ¾ÐÃàÇ®±â

+

mod_deflate ¸ðµâÀº gzipÀ¸·Î ¾ÐÃàµÈ ¿äû + ³»¿ëÀ» Ǫ´Â ÇÊÅ͵µ Á¦°øÇÑ´Ù. ÀÌ ±â´ÉÀ» »ç¿ëÇÏ·Á¸é ´ÙÀ½°ú + °°ÀÌ SetInputFilter³ª + AddInputFilter¸¦ + »ç¿ëÇÏ¿© ÀÔ·ÂÇÊÅͼø¼­¿¡ DEFLATE ÇÊÅ͸¦ + Ãß°¡ÇÑ´Ù.

+ +

+ <Location /dav-area>
+ + SetInputFilter DEFLATE
+ + </Location> +

+ +

¿äû¿¡ Content-Encoding: gzip Çì´õ°¡ ÀÖ´Ù¸é + ÀÚµ¿À¸·Î ¾ÐÃàµÈ ³»¿ëÀ» Ǭ´Ù. gzip ¿äûÀ» ÇÒ ¼ö ÀÖ´Â + ºê¶ó¿ìÀú´Â µå¹°´Ù. ±×·¯³ª ¾î¶² WebDAV Ŭ¶óÀ̾ðÆ®¿Í °°Àº + Ưº°ÇÑ ÇÁ·Î±×·¥Àº ¿äû ¾ÐÃàÀ» Áö¿øÇÑ´Ù.

+ +

Content-Length¿¡ ´ëÇÑ ÁÖÀÇ

+

¿äû ³»¿ëÀ» Á÷Á¢ »ìÆ캻´Ù¸é, Content-Length + Çì´õ¸¦ ¹ÏÁö¸¶¶ó! Content-Length Çì´õ´Â Ŭ¶óÀ̾ðÆ®°¡ + º¸³½ ³»¿ëÀÇ ±æÀÌÀÌÁö, ¾ÐÃàÀ» Ǭ °á°úÀÇ ¹ÙÀÌÆ®¼ö°¡ + ¾Æ´Ï´Ù.

+
+ +
top
+
+

ÇÁ·Ï½Ã ¼­¹ö ´Ù·ç±â

+ +

mod_deflate ¸ðµâÀº ÇÁ·Ï½Ã°¡ ÀÚ½ÅÀÌ Ä³½¬ÇÑ + ÀÀ´äÀ» ÀûÀýÇÑ Accept-Encoding ¿äû Çì´õ¸¦ º¸³½ + Ŭ¶óÀ̾ðÆ®¿¡°Ô¸¸ º¸³»µµ·Ï Vary: + Accept-Encoding HTTP ÀÀ´ä Çì´õ¸¦ Ãß°¡ÇÑ´Ù. ±×·¡¼­ + ¾ÐÃàµÈ ³»¿ëÀ» ÀÌÇØÇÒ ¼ö ¾ø´Â Ŭ¶óÀ̾ðÆ®¿¡ ¾ÐÃàµÈ ³»¿ëÀ» + º¸³»Áö¾Êµµ·Ï ÇÑ´Ù.

+ +

¿¹¸¦ µé¾î, User-Agent Çì´õ µî¿¡ µû¶ó Ưº°È÷ + ÇÊÅÍ Àû¿ëÀ» Ãë¼ÒÇÑ´Ù¸é, ÇÁ·Ï½Ã¿¡°Ô ÀÌ·¯ÇÑ Á¦ÇÑÀ» ¾Ë·ÁÁÖ±âÀ§ÇØ + Á÷Á¢ Vary Çì´õ¿¡ Ãß°¡ÇØ¾ß ÇÑ´Ù. ¿¹¸¦ µé¾î, + ¼³Á¤ÀÌ User-Agent¿¡ µû¶ó DEFLATE + ÇÊÅ͸¦ Ãß°¡ÇÑ´Ù¸é ´ÙÀ½À» »ç¿ëÇÑ´Ù:

+ +

+ Header append Vary User-Agent +

+ +

¿äû Çì´õ¿ÜÀÇ ´Ù¸¥ Á¤º¸¿¡ (¿¹¸¦ µé¾î, HTTP ¹öÀü) + µû¶ó ¾ÐÃà ¿©ºÎ°¡ °áÁ¤µÈ´Ù¸é, Vary Çì´õ°ªÀ» + *·Î ¼³Á¤ÇØ¾ß ÇÑ´Ù. ±×·¯¸é Ç¥ÁØÀ» µû¸£´Â ÇÁ·Ï½Ã´Â + ij½¬¸¦ ÇÏÁö ¾Ê°Ô µÈ´Ù.

+ +

¿¹Á¦

+ Header set Vary * +

+
+
top
+

DeflateBufferSize Áö½Ã¾î

+ + + + + + + +
¼³¸í:zlibÀÌ Çѹø¿¡ ¾ÐÃàÇÒ Å©±â
¹®¹ý:DeflateBufferSize value
±âº»°ª:DeflateBufferSize 8096
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Extension
¸ðµâ:mod_deflate
+

DeflateBufferSize Áö½Ã¾î´Â zlibÀÌ + Çѹø¿¡ ¾ÐÃàÇÒ ¹ÙÀÌÆ®¼ö¸¦ ÁöÁ¤ÇÑ´Ù.

+ +
+
top
+

DeflateCompressionLevel Áö½Ã¾î

+ + + + + + + + +
¼³¸í:Ãâ·ÂÀ» ¾î´ÀÁ¤µµ ¾ÐÃàÇϴ°¡
¹®¹ý:DeflateCompressionLevel value
±âº»°ª:Zlib's default
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Extension
¸ðµâ:mod_deflate
Áö¿ø:¾ÆÆÄÄ¡ 2.0.45 ºÎÅÍ
+

DeflateCompressionLevel Áö½Ã¾î´Â + »ç¿ëÇÒ ¾ÐÃà¼öÁØÀ» ¼±ÅÃÇÑ´Ù. °ªÀÌ Å¬¼ö·Ï ¾ÐÃà·üÀÌ Áõ°¡ÇÏÁö¸¸, + CPU¸¦ ´õ ¸¹ÀÌ »ç¿ëÇÑ´Ù.

+

(°¡Àå ´ú ¾ÐÃà) 1°ú (°¡Àå ¸¹ÀÌ ¾ÐÃà) 9 »çÀÌÀÇ °ªÀ» ÁöÁ¤ÇÑ´Ù.

+ +
+
top
+

DeflateFilterNote Áö½Ã¾î

+ + + + + + + +
¼³¸í:¾ÐÃà·üÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù
¹®¹ý:DeflateFilterNote [type] notename
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Extension
¸ðµâ:mod_deflate
Áö¿ø:typeÀº ¾ÆÆÄÄ¡ 2.0.4 ºÎÅÍ
+

DeflateFilterNote Áö½Ã¾î´Â ¿äûÀÇ + ¾ÐÃà·üÀ» ·Î±×¿¡ ±â·ÏÇÏ´Â ±âÈ£¸¦ ÁöÁ¤ÇÑ´Ù. ±âÈ£ À̸§Àº Áö½Ã¾î·Î + ÁöÁ¤ÇÑ °ªÀÌ´Ù. Åë°è¸¦ À§ÇØ Á¢±Ù + ·Î±×¿¡¼­ ±âÈ£¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

¿¹Á¦

+ DeflateFilterNote ratio
+
+ LogFormat '"%r" %b (%{ratio}n) "%{User-agent}i"' deflate
+ CustomLog logs/deflate_log deflate +

+ +

·Î±×¿¡¼­ ´õ Á¤È®ÇÑ °ªÀ» ÃßÃâÇÏ·Á¸é type ¾Æ±Ô¸ÕÆ®·Î + ±â·ÏÇÒ ÀڷḦ ¼±ÅÃÇÑ´Ù. type´Â ´ÙÀ½Áß ÇϳªÀÌ´Ù:

+ +
+
Input
+
ÇÊÅÍ ÀԷ½ºÆ®¸²ÀÇ ¹ÙÀÌÆ®¼ö¸¦ ÀúÀåÇÑ´Ù.
+ +
Output
+
ÇÊÅÍ Ãâ·Â½ºÆ®¸²ÀÇ ¹ÙÀÌÆ®¼ö¸¦ ÀúÀåÇÑ´Ù..
+ +
Ratio
+
¾ÐÃà·üÀ» (output/input * 100) ÀúÀåÇÑ´Ù. + type ¾Æ±Ô¸ÕÆ®¸¦ »ý·«ÇÏ¸é »ç¿ëÇÏ´Â ±âº»°ªÀÌ´Ù.
+
+ +

±×·¡¼­ ÀÌ·¸°Ô ·Î±×¿¡ ±â·ÏÇÒ ¼ö ÀÖ´Ù:

+ +

Á¤¹ÐÇÑ ·Î±×

+ DeflateFilterNote Input instream
+ DeflateFilterNote Output outstream
+ DeflateFilterNote Ratio ratio
+
+ LogFormat '"%r" %{outstream}n/%{instream}n (%{ratio}n%%)' deflate
+ CustomLog logs/deflate_log deflate +

+ +

Âü°í

+ +
+
top
+

DeflateMemLevel Áö½Ã¾î

+ + + + + + + +
¼³¸í:zlibÀÌ ¾ÐÃàÇÒ¶§ »ç¿ëÇÏ´Â ¸Þ¸ð¸®·®
¹®¹ý:DeflateMemLevel value
±âº»°ª:DeflateMemLevel 9
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Extension
¸ðµâ:mod_deflate
+

DeflateMemLevel Áö½Ã¾î´Â zlibÀÌ + ¾ÐÃàÇÒ¶§ ¾ó¸¶¸¸Å­ ¸Þ¸ð¸®¸¦ »ç¿ëÇÒÁö °áÁ¤ÇÑ´Ù. (1°ú 9 »çÀÌÀÇ + °ª)

+ +
+
top
+

DeflateWindowSize Áö½Ã¾î

+ + + + + + + +
¼³¸í:Zlib ¾ÐÃà window size
¹®¹ý:DeflateWindowSize value
±âº»°ª:DeflateWindowSize 15
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Extension
¸ðµâ:mod_deflate
+

DeflateWindowSize Áö½Ã¾î´Â zlib + ¾ÐÃà window size¸¦ (1°ú 15 »çÀÌÀÇ °ª) ÁöÁ¤ÇÑ´Ù. ÀϹÝÀûÀ¸·Î + window size°¡ Ŭ¼ö·Ï ¾ÐÃà·üÀÌ Áõ°¡ÇÑ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dir.html b/docs/manual/mod/mod_dir.html new file mode 100644 index 00000000..be6c14c8 --- /dev/null +++ b/docs/manual/mod/mod_dir.html @@ -0,0 +1,11 @@ +URI: mod_dir.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_dir.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_dir.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_dir.html.en b/docs/manual/mod/mod_dir.html.en new file mode 100644 index 00000000..91a1ba01 --- /dev/null +++ b/docs/manual/mod/mod_dir.html.en @@ -0,0 +1,169 @@ + + + +mod_dir - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_dir

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Provides for "trailing slash" redirects and + serving directory index files
Status:Base
Module Identifier:dir_module
Source File:mod_dir.c
+

Summary

+ +

The index of a directory can come from one of two sources:

+ +
    +
  • A file written by the user, typically called + index.html. The DirectoryIndex directive sets the + name of this file. This is controlled by + mod_dir.
    • + +
  • Otherwise, a listing generated by the server. This is + provided by mod_autoindex.
    • +
+

The two functions are separated so that you can completely + remove (or replace) automatic index generation should you want + to.

+ +

A "trailing slash" redirect is issued when the server + receives a request for a URL + http://servername/foo/dirname where + dirname is a directory. Directories require a + trailing slash, so mod_dir issues a redirect to + http://servername/foo/dirname/.

+
+

Directives

+ +
+ +
top
+

DirectoryIndex Directive

+ + + + + + + + +
Description:List of resources to look for when the client requests +a directory
Syntax:DirectoryIndex + local-url [local-url] ...
Default:DirectoryIndex index.html
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_dir
+

The DirectoryIndex directive sets the + list of resources to look for, when the client requests an index + of the directory by specifying a / at the end of the directory + name. Local-url is the (%-encoded) URL of a document on + the server relative to the requested directory; it is usually the + name of a file in the directory. Several URLs may be given, in + which case the server will return the first one that it finds. If + none of the resources exist and the Indexes option is + set, the server will generate its own listing of the + directory.

+ +

Example

+ DirectoryIndex index.html +

+ +

then a request for http://myserver/docs/ would + return http://myserver/docs/index.html if it + exists, or would list the directory if it did not.

+ +

Note that the documents do not need to be relative to the + directory;

+ +

+ DirectoryIndex index.html index.txt /cgi-bin/index.pl +

+ +

would cause the CGI script /cgi-bin/index.pl to be + executed if neither index.html or index.txt + existed in a directory.

+ +
+
top
+

DirectorySlash Directive

+ + + + + + + + + +
Description:Toggle trailing slash redirects on or off
Syntax:DirectorySlash On|Off
Default:DirectorySlash On
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_dir
Compatibility:Available in version 2.0.51 and later
+

The DirectorySlash directive determines, whether + mod_dir should fixup URLs pointing to a directory or + not.

+ +

Typically if a user requests a resource without a trailing slash, which + points to a directory, mod_dir redirects him to the same + resource, but with trailing slash for some good reasons:

+ +
    +
  • The user is finally requesting the canonical URL of the resource
    • +
  • mod_autoindex works correctly. Since it doesn't emit + the path in the link, it would point to the wrong path.
    • +
  • DirectoryIndex will be evaluated + only for directories requested with trailing slash.
    • +
  • Relative URL references inside html pages will work correctly.
    • +
+ +

Well, if you don't want this effect and the reasons above don't + apply to you, you can turn off the redirect with:

+ +

+ # see security warning below!
+ <Location /some/path>
+ + DirectorySlash Off
+ SetHandler some-handler
+ + </Location> +

+ +

Security Warning

+

Turning off the trailing slash redirect may result in an information + disclosure. Consider a situation where mod_autoindex is + active (Options +Indexes) and DirectoryIndex is set to a valid resource (say, + index.html) and there's no other special handler defined for + that URL. In this case a request with a trailing slash would show the + index.html file. But a request without trailing slash + would list the directory contents.

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dir.html.ja.euc-jp b/docs/manual/mod/mod_dir.html.ja.euc-jp new file mode 100644 index 00000000..143d693b --- /dev/null +++ b/docs/manual/mod/mod_dir.html.ja.euc-jp @@ -0,0 +1,182 @@ + + + +mod_dir - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_dir

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¡ÖºÇ¸å¤Î¥¹¥é¥Ã¥·¥å¡×¤Î¥ê¥À¥¤¥ì¥¯¥È¤È¡¢¥Ç¥£¥ì¥¯¥È¥ê¤Î +¥¤¥ó¥Ç¥Ã¥¯¥¹¥Õ¥¡¥¤¥ë¤ò°·¤¦µ¡Ç½¤òÄ󶡤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:dir_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_dir.c
+

³µÍ×

+ +

¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¡¢¼¡¤ÎÆó¤Ä¤Î¤¦¤Á¤É¤Á¤é¤«¤¬ÍøÍѤµ¤ì¤Þ¤¹:

+ +
    +
  • °ì¤ÄÌܤϡ¢¥æ¡¼¥¶¤¬ºîÀ®¤·¤¿¥Õ¥¡¥¤¥ë¤òÍѤ¤¤ë¤â¤Î¤Ç¡¢Ä̾ï + index.html ¤È¤¤¤¦¥Õ¥¡¥¤¥ë̾¤ò»È¤¤¤Þ¤¹¡£¤³¤Î¥Õ¥¡¥¤¥ë̾¤Ï¡¢ + DirectoryIndex ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + »ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤Îµ¡Ç½¤Ï mod_dir + ¥â¥¸¥å¡¼¥ë¤ÇÄ󶡤µ¤ì¤Þ¤¹¡£
    • + +
  • ¤â¤¦°ì¤Ä¤ÎÊýË¡¤Ï¡¢ + ¥µ¡¼¥Ð¤Ë¤è¤Ã¤Æ¼«Æ°Åª¤ËÀ¸À®¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¥ê¥¹¥È¤òÍѤ¤¤ë¾ì¹ç¤Ç¤¹¡£ + ¤³¤Îµ¡Ç½¤Ï¡¢mod_autoindex + ¥â¥¸¥å¡¼¥ë¤Ë¤è¤êÄ󶡤µ¤ì¤Þ¤¹¡£
    • +
+ +

¼«Æ°Åª¤Ê¥¤¥ó¥Ç¥Ã¥¯¥¹À¸À®µ¡Ç½¤òºï½ü (¤â¤·¤¯¤Ï¸ò´¹) + ¤Ç¤­¤ë¤è¤¦¤Ë¡¢¤³¤ÎÆó¤Ä¤Îµ¡Ç½¤ÏʬΥ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

¤Ê¤ª http://servername/foo/dirname ¤È¤¤¤¦ URL + ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤¬¤¢¤Ã¤¿ºÝ¤Ë¡¢dirname + ¤È¤¤¤¦¥Ç¥£¥ì¥¯¥È¥ê¤¬¤¢¤ì¤Ð¡¢¡ÖºÇ¸å¤Ë¥¹¥é¥Ã¥·¥å¤ò¤Ä¤±¤¿·Á¡×¤Î URL + ¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷½Ð¤·¤Þ¤¹¡£ + ¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¥¢¥¯¥»¥¹¤Ï¥¹¥é¥Ã¥·¥å¤Ç½ª¤ï¤Ã¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¡¢ + mod_dir ¤Ï¡¢http://servername/foo/dirname/ + ¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷½Ð¤¹¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +
+ +
top
+

DirectoryIndex ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤¬¥Ç¥£¥ì¥¯¥È¥ê¤ò¥ê¥¯¥¨¥¹¥È¤·¤¿¤È¤­¤ËÄ´¤Ù¤ë +¥ê¥½¡¼¥¹¤Î¥ê¥¹¥È
¹½Ê¸:DirectoryIndex + local-url [local-url] ...
¥Ç¥Õ¥©¥ë¥È:DirectoryIndex index.html
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_dir
+

+ ¥¯¥é¥¤¥¢¥ó¥È¤¬¡¢¥Ç¥£¥ì¥¯¥È¥ê̾¤ÎºÇ¸å¤Ë¡Ö/¡× + ¤ò»ØÄꤷ¤Æ¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤òÍ׵᤹¤ë¾ì¹ç¤Ëõ¤¹¥ê¥½¡¼¥¹¤Î¥ê¥¹¥È¤ò + DirectoryIndex ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤷ¤Þ¤¹¡£ + Local-url + ¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤ËÂбþ¤¹¤ë¡¢¥µ¡¼¥Ð¾å¤Î¥É¥­¥å¥á¥ó¥È¤Î + (% ¥¨¥ó¥³¡¼¥É¤µ¤ì¤¿) URL ¤Ç¡¢ÉáÄ̤ϥǥ£¥ì¥¯¥È¥êÃæ¤Î¥Õ¥¡¥¤¥ë¤Î̾Á°¤Ç¤¹¡£ + Ê£¿ô¤Î URL ¤¬ÀßÄꤵ¤ì¤¿¾ì¹ç¤Ë¤Ï¡¢ºÇ½é¤Ë¸«¤Ä¤«¤Ã¤¿¤â¤Î¤òÊÖ¤·¤Þ¤¹¡£ + ¤½¤ì¤é¤¬¸«¤Ä¤«¤é¤º¡¢Indexes + ¥ª¥×¥·¥ç¥ó¤¬¥»¥Ã¥È¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢¥Ç¥£¥ì¥¯¥È¥ê¤Î¥ê¥¹¥È¤òÀ¸À®¤·¤Þ¤¹¡£ +

+ +

Îã

+ DirectoryIndex index.html +

+ +

http://myserver/docs/ ¤Ø¤Î¥¢¥¯¥»¥¹¤¬¤¢¤ê¡¢ + http://myserver/docs/index.html + ¤¬Â¸ºß¤¹¤ì¤Ð¡¢¤³¤Î URL ¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£ + ¤â¤·Â¸ºß¤·¤Ê¤±¤ì¤Ð¡¢¥Ç¥£¥ì¥¯¥È¥ê¤Î¥ê¥¹¥È¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£

+ +

Ãí: ¥É¥­¥å¥á¥ó¥È¤¬Æ±¤¸¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ë¸ºß¤¹¤ë¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£ +

+ +

+ DirectoryIndex index.html index.txt /cgi-bin/index.pl +

+ +

¤È¤·¤¿¾ì¹ç¡¢index.html ¤È index.txt + ¤Î¤É¤Á¤é¤â¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ë¸ºß¤·¤Ê¤¤¾ì¹ç¡¢CGI ¥¹¥¯¥ê¥×¥È + /cgi-bin/index.pl ¤¬¼Â¹Ô¤µ¤ì¤Þ¤¹¡£

+ +
+
top
+

DirectorySlash ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:¥Ñ¥¹ËöÈø¤Î¥¹¥é¥Ã¥·¥å¤Ç¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤«¤É¤¦¤«¤Î¥ª¥ó¥ª¥Õ¤ò¥È¥°¥ë¤µ¤»¤ë
¹½Ê¸:DirectorySlash On|Off
¥Ç¥Õ¥©¥ë¥È:DirectorySlash On
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_dir
¸ß´¹À­:2.0.51 °Ê¹ß
+

Í×µá¤Î¤¢¤Ã¤¿ URL ¤¬¥Ç¥£¥ì¥¯¥È¥ê¤ò»Ø¤¹¤«¤É¤¦¤«¤ò¡¢ + mod_dir ¤¬Ä´À°¤¹¤ë¤Ù¤­¤«¤É¤¦¤«¤ò + DirectorySlash + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤷ¤Þ¤¹¡£

+ +

ŵ·¿Åª¤Ë¤Ï¡¢¥æ¡¼¥¶¤¬ËöÈø¤Î¥¹¥é¥Ã¥·¥å̵¤·¤Ç¥ê¥½¡¼¥¹¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤òȯ¹Ô¤·¡¢ + ¤½¤·¤Æ¡¢¤½¤Î¥ê¥½¡¼¥¹¤¬¥Ç¥£¥ì¥¯¥È¥ê¤ò»Ø¤·¤Æ¤¤¤¿¾ì¹ç¡¢mod_dir + ¤Ï¡¢ËöÈø¤Ë¥¹¥é¥Ã¥·¥å¤òÉղä·¤¿¾å¤ÇƱ¤¸¥ê¥½¡¼¥¹¤Ë¥ê¥À¥¤¥ì¥¯¥È¤µ¤»¤Þ¤¹¡£ + ¤³¤ÎµóÆ°¤Ë¤Ï´ö¤Ä¤«Íýͳ¤¬¤¢¤ê¤Þ¤¹:

+ +
    +
  • ¥æ¡¼¥¶¤Ï¡¢ºÇ½ªÅª¤Ë¤Ï¥ê¥½¡¼¥¹¤ÎÊÌ̾ URL ¤ò¥ê¥¯¥¨¥¹¥È¤¹¤ë¤³¤È¤Ë¤Ê¤ë¡£
    • +
  • mod_autoindex ¤¬´üÂÔÄ̤ê¤ËÆ°¤¯¡£mod_autoindex + ¤ÎÀ¸À®¤¹¤ë¥ê¥ó¥¯¤Ï¥Ñ¥¹¤ò½ÐÎϤ·¤Þ¤»¤ó¤Î¤Ç¡¢¥¹¥é¥Ã¥·¥å¤¬¤Ê¤¤¾ì¹ç¤Ï´Ö°ã¤Ã¤¿¥Ñ¥¹¤ò + »Ø¤·¤Æ¤·¤Þ¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
    • +
  • DirectoryIndex ¤Ï¡¢ + ËöÈø¤Ë¥¹¥é¥Ã¥·¥å¤¬¤Ä¤¤¤Æ¤¤¤ë¥ê¥¯¥¨¥¹¥È¤Ë¤Ä¤¤¤Æ¤Î¤ßɾ²Á¤µ¤ì¤ë¡£
    • +
  • HTML ¥Ú¡¼¥¸¤ÎÁêÂÐ URL »²¾È¤¬Àµ¤·¤¯Æ°ºî¤¹¤ë¡£
    • +
+ +

¤È¤Ï¤¤¤¨¡¢¤â¤·¤³¤¦¤¤¤Ã¤¿¸ú²Ì¤ò˾¤Þ¤Ê¤¤¡¢¤«¤Ä¡¢ + ¾åµ­¤Î¤è¤¦¤ÊÍýͳ¤¬Åö¤Æ¤Ï¤Þ¤é¤Ê¤¤¾ì¹ç¤Ï¡¢¥ê¥À¥¤¥ì¥¯¥È¤ò¼¡¤Î¤è¤¦¤Ë¤·¤Æ¥ª¥Õ¤Ë¤Ç¤­¤Þ¤¹:

+ +

+ # see security warning below!
+ <Location /some/path>
+ + DirectorySlash Off
+ SetHandler some-handler
+ + </Location> +

+ +

¥»¥­¥å¥ê¥Æ¥£·Ù¹ð

+

ËöÈø¤Î¥¹¥é¥Ã¥·¥å¤Ç¤Î¥ê¥À¥¤¥ì¥¯¥È¤ò¥ª¥Õ¤Ë¤¹¤ë¤È¡¢·ë²ÌŪ¤Ë¾ðÊóϳ±Ì¤ò + ¾·¤¯¤³¤È¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + mod_autoindex ¤¬Í­¸ú (Options +Indexes) ¤Ç¡¢ + DirectoryIndex ¤¬Í­¸ú¤Ê¥ê¥½¡¼¥¹ (Î㤨¤Ð + index.html) ¤ò»Ø¤·¤Æ¤¤¤Æ¡¢¤Þ¤¿¡¢Í×µá¤Î¤¢¤Ã¤¿ URL ¤ËÆÃÊÌ¤Ê + ¥Ï¥ó¥É¥é¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤ò¹Í¤¨¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤Î¾ì¹çËöÈø¤Ë¥¹¥é¥Ã¥·¥å¤Î¤Ä¤¤¤Æ¤¤¤ë¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¤Ï index.html + ¥Õ¥¡¥¤¥ë¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£¤·¤«¤·¥¹¥é¥Ã¥·¥å¤Î¤Ê¤¤¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¤Ï¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê¤ÎÆâÍÆ°ìÍ÷¤òÊÖ¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dir.html.ko.euc-kr b/docs/manual/mod/mod_dir.html.ko.euc-kr new file mode 100644 index 00000000..8d2bd944 --- /dev/null +++ b/docs/manual/mod/mod_dir.html.ko.euc-kr @@ -0,0 +1,169 @@ + + + +mod_dir - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_dir

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:"¸¶Áö¸· ½½·¡½¬" ¸®´ÙÀÌ·º¼ÇÀ» Á¦°øÇÏ°í µð·ºÅ丮 +index ÆÄÀÏÀ» ¼­ºñ½ºÇÑ´Ù
»óÅÂ:Base
¸ðµâ¸í:dir_module
¼Ò½ºÆÄÀÏ:mod_dir.c
+

¿ä¾à

+ +

µð·ºÅ丮ÀÇ index´Â ´ÙÀ½ µÑÁß ÇÑ°¡Áö ¹æ¹ýÀ¸·Î Á¦°øµÈ´Ù:

+ +
    +
  • »ç¿ëÀÚ°¡ ÀÛ¼ºÇÑ º¸Åë index.htmlÀ̶ó´Â + ÆÄÀÏ. DirectoryIndex + Áö½Ã¾î´Â ÀÌ ÆÄÀÏÀÇ À̸§À» ÁöÁ¤ÇÑ´Ù. mod_dir°¡ + ÀÌ Áö½Ã¾î¸¦ Á¦°øÇÑ´Ù.
    • + +
  • ¾Æ´Ï¶ó¸é ¼­¹ö°¡ ¸¸µç ¸ñ·Ï. mod_autoindex°¡ + ÀÌ ±â´ÉÀ» Á¦°øÇÑ´Ù.
    • +
+

µÎ ±â´ÉÀº ¼­·Î º°°³·Î ¿øÇÑ´Ù¸é ÀÚµ¿ index »ý¼ºÀ» ¿ÏÀüÈ÷ + ¾ø¾Ù (ȤÀº ±³Ã¼ÇÒ) ¼ö ÀÖ´Ù.

+ +

dirnameÀÌ µð·ºÅ丮¶ó¸é ¼­¹ö´Â URL + http://servername/foo/dirname ¿äûÀ» ¹ÞÀ¸¸é + "¸¶Áö¸· ½½·¡½¬" ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù. µð·ºÅ丮¿¡´Â ¸¶Áö¸· + ½½·¡½¬°¡ ÇÊ¿äÇÏ´Ù. ±×·¡¼­ mod_dirÀº + http://servername/foo/dirname/·Î ¸®´ÙÀÌ·º¼ÇÀ» + º¸³½´Ù.

+
+

Áö½Ã¾îµé

+ +
+ +
top
+

DirectoryIndex Áö½Ã¾î

+ + + + + + + + +
¼³¸í:Ŭ¶óÀ̾ðÆ®°¡ µð·ºÅ丮¸¦ ¿äûÇÒ¶§ ã¾Æº¼ ÀÚ¿ø ¸ñ·Ï
¹®¹ý:DirectoryIndex + local-url [local-url] ...
±âº»°ª:DirectoryIndex index.html
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_dir
+

DirectoryIndex Áö½Ã¾î´Â Ŭ¶óÀ̾ðÆ®°¡ + µð·ºÅ丮¸í ³¡¿¡ /¸¦ ºÙ¿©¼­ µð·ºÅ丮ÀÇ index¸¦ ¿äûÇÒ¶§ ã¾Æº¼ + ÀÚ¿ø ¸ñ·ÏÀ» ÁöÁ¤ÇÑ´Ù. Local-urlÀº ¿äûÇÑ µð·ºÅ丮¿¡ + »ó´ëÀûÀÎ ¹®¼­ÀÇ (%·Î ÀÎÄÚµùµÈ) URLÀÌ´Ù. º¸ÅëÀº µð·ºÅ丮¿¡ + ÀÖ´Â ÆÄÀϸíÀÌ´Ù. ¿©·¯ URLÀ» ÁöÁ¤ÇÒ ¼ö ÀÖ°í, ÀÌ °æ¿ì ¼­¹ö´Â + ù¹ø°·Î ãÀº ÆÄÀÏÀ» º¸³½´Ù. ÀÚ¿øÀ» ãÀ» ¼ö ¾ø°í + Indexes ¿É¼ÇÀ» ¼³Á¤ÇÏ¿´´Ù¸é ¼­¹ö´Â Á÷Á¢ µð·ºÅ丮 + ¸ñ·ÏÀ» ¸¸µç´Ù.

+ +

¿¹Á¦

+ DirectoryIndex index.html +

+ +

ÀÌ °æ¿ì http://myserver/docs/¸¦ ¿äûÇÒ¶§ + http://myserver/docs/index.htmlÀÌ ÀÖÀ¸¸é À̸¦ + º¸³»°í, ¾ø´Ù¸é µð·ºÅ丮 ¸ñ·ÏÀ» º¸³½´Ù.

+ +

¹®¼­°¡ ¹Ýµå½Ã µð·ºÅ丮¿¡ »ó´ëÀûÀÏ ÇÊ¿ä´Â ¾ø´Ù.

+ +

+ DirectoryIndex index.html index.txt /cgi-bin/index.pl +

+ +

ÀÌ °æ¿ì µð·ºÅ丮¿¡ index.htmlÀ̳ª + index.txt°¡ ¾øÀ¸¸é CGI ½ºÅ©¸³Æ® + /cgi-bin/index.plÀ» ½ÇÇàÇÑ´Ù.

+ +
+
top
+

DirectorySlash Áö½Ã¾î

+ + + + + + + + + +
¼³¸í:¸¶Áö¸· ½½·¡½¬ ¸®´ÙÀÌ·º¼ÇÀ» Å°°í ²ö´Ù
¹®¹ý:DirectorySlash On|Off
±âº»°ª:DirectorySlash On
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_dir
Áö¿ø:¾ÆÆÄÄ¡ 2.0.51 ÀÌÈĺÎÅÍ
+

DirectorySlash Áö½Ã¾î´Â + mod_dir°¡ µð·ºÅ丮¸¦ °¡¸®Å°´Â URLÀ» ¼öÁ¤ÇÒÁö + ¿©ºÎ¸¦ °áÁ¤ÇÑ´Ù.

+ +

»ç¿ëÀÚ°¡ ¸¶Áö¸· ½½·¡½¬¾øÀÌ µð·ºÅ丮¿¡ ÇØ´çÇÏ´Â ÀÚ¿øÀ» + ¿äûÇϸé, mod_dir´Â º¸Åë ´ÙÀ½°ú °°Àº ÀÌÀ¯·Î + »ç¿ëÀÚ¸¦ ¸¶Áö¸· ½½·¡½¬¸¦ ºÙÀÎ µ¿ÀÏÇÑ ÀÚ¿øÀ¸·Î + ¸®´ÙÀÌ·º¼ÇÇÑ´Ù.

+ +
    +
  • »ç¿ëÀÚ´Â °á±¹ ÀÚ¿øÀÇ Á¤±Ô URLÀ» ¿äûÇÏ°Ô µÈ´Ù
    • +
  • mod_autoindex°¡ ¿Ã¹Ù·Î µ¿ÀÛÇÑ´Ù. ÀÌ + ±â´ÉÀÌ ¾ø´Ù¸é ÀÌ ¸ðµâÀº ¸µÅ©¿¡ À߸øµÈ °æ·Î¸¦ ¾²°Ô µÈ´Ù.
    • +
  • DirectoryIndex´Â + ¸¶Áö¸· ½½·¡½¬°¡ ÀÖ´Â µð·ºÅ丮 ¿äû¸¸À» ó¸®ÇÑ´Ù.
    • +
  • html ÆäÀÌÁö¿¡ ÀÖ´Â »ó´ëÀûÀÎ URL ÂüÁ¶°¡ ¿Ã¹Ù·Î µ¿ÀÛÇÑ´Ù.
    • +
+ +

±×·±µ¥ ÀÌ ±â´ÉÀ» ¿øÇÏÁö ¾Ê°Å³ª À§¿¡ µç ÀÌÀ¯°¡ + ´ç½Å¿¡°Ô ¾Ë¸ÂÁö ¾Ê´Ù¸é ´ÙÀ½°ú °°ÀÌ ¸®´ÙÀÌ·º¼ÇÀ» ÇÏÁö ¾ÊÀ» + ¼ö ÀÖ´Ù.

+ +

+ # ¾Æ·¡ º¸¾È °æ°í Âü°í!
+ <Location /some/path>
+ + DirectorySlash Off
+ SetHandler some-handler
+ + </Location> +

+ +

º¸¾È °æ°í

+

¸¶Áö¸· ½½·¡½¬ ¸®´ÙÀÌ·º¼ÇÀ» ²ô¸é Á¤º¸°¡ À¯ÃâµÉ ¼ö ÀÖ´Ù. + (Options +Indexes) mod_autoindex¸¦ + »ç¿ëÇÏ°í DirectoryIndex¸¦ + (index.html °°Àº) À¯È¿ÇÑ ÀÚ¿øÀ¸·Î ¼³Á¤ÇÏ¿´Áö¸¸ + ÇØ´ç URL¿¡ ´Ù¸¥ Ưº°ÇÑ Çڵ鷯°¡ ¾ø´Â »óȲÀ» »ó»óÇغ¸¶ó. + ÀÌ °æ¿ì ¸¶Áö¸· ½½·¡½¬°¡ ÀÖ´Â ¿äûÀº index.html + ÆÄÀÏÀ» º¸¿©ÁØ´Ù. ±×·¯³ª ¸¶Áö¸· ½½·¡½¬°¡ ¾ø´Â ¿äûÀº + µð·ºÅ丮 ³»¿ëÀ» º¸¿©ÁØ´Ù.

+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_disk_cache.html b/docs/manual/mod/mod_disk_cache.html new file mode 100644 index 00000000..84207ada --- /dev/null +++ b/docs/manual/mod/mod_disk_cache.html @@ -0,0 +1,11 @@ +URI: mod_disk_cache.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_disk_cache.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_disk_cache.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_disk_cache.html.en b/docs/manual/mod/mod_disk_cache.html.en new file mode 100644 index 00000000..5364af30 --- /dev/null +++ b/docs/manual/mod/mod_disk_cache.html.en @@ -0,0 +1,178 @@ + + + +mod_disk_cache - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_disk_cache

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Content cache storage manager keyed to URIs
Status:Extension
Module Identifier:disk_cache_module
Source File:mod_disk_cache.c
+

Summary

+ +

mod_disk_cache implements a disk based storage + manager. It is primarily of use in conjunction + mod_cache.

+ +

Content is stored in and retrieved from the cache using URI based + keys. Content with access protection is not cached.

+ +

htcacheclean can be used to maintain the cache + size at a maximum level.

+ +

Note:

+

mod_disk_cache requires the services of + mod_cache.

+
+
+ + +
top
+

CacheDirLength Directive

+ + + + + + + +
Description:The number of characters in subdirectory names
Syntax:CacheDirLength length
Default:CacheDirLength 2
Context:server config, virtual host
Status:Extension
Module:mod_disk_cache
+

The CacheDirLength directive sets the number + of characters for each subdirectory name in the cache hierarchy.

+ +
+

The result of CacheDirLevels* CacheDirLength + must not be higher than 20.

+
+ +

+ CacheDirLength 4 +

+ +
+
top
+

CacheDirLevels Directive

+ + + + + + + +
Description:The number of levels of subdirectories in the +cache.
Syntax:CacheDirLevels levels
Default:CacheDirLevels 3
Context:server config, virtual host
Status:Extension
Module:mod_disk_cache
+

The CacheDirLevels directive sets the number + of subdirectory levels in the cache. Cached data will be saved this + many directory levels below the CacheRoot directory.

+ +
+

The result of CacheDirLevels* + CacheDirLength must + not be higher than 20.

+
+ +

+ CacheDirLevels 5 +

+ +
+
top
+

CacheMaxFileSize Directive

+ + + + + + + +
Description:The maximum size (in bytes) of a document to be placed in the +cache
Syntax:CacheMaxFileSize bytes
Default:CacheMaxFileSize 1000000
Context:server config, virtual host
Status:Extension
Module:mod_disk_cache
+

The CacheMaxFileSize directive sets the + maximum size, in bytes, for a document to be considered for storage in + the cache.

+ +

+ CacheMaxFileSize 64000 +

+ +
+
top
+

CacheMinFileSize Directive

+ + + + + + + +
Description:The minimum size (in bytes) of a document to be placed in the +cache
Syntax:CacheMinFileSize bytes
Default:CacheMinFileSize 1
Context:server config, virtual host
Status:Extension
Module:mod_disk_cache
+

The CacheMinFileSize directive sets the + minimum size, in bytes, for a document to be considered for storage + in the cache.

+ +

+ CacheMinFileSize 64 +

+ +
+
top
+

CacheRoot Directive

+ + + + + + +
Description:The directory root under which cache files are +stored
Syntax:CacheRoot directory
Context:server config, virtual host
Status:Extension
Module:mod_disk_cache
+

The CacheRoot directive defines the name of + the directory on the disk to contain cache files. If the mod_disk_cache module has been loaded or compiled in to the + Apache server, this directive must be defined. Failing to + provide a value for CacheRoot will result in + a configuration file processing error. The CacheDirLevels and CacheDirLength directives define + the structure of the directories under the specified root directory.

+ +

+ CacheRoot c:/cacheroot +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_disk_cache.html.ja.euc-jp b/docs/manual/mod/mod_disk_cache.html.ja.euc-jp new file mode 100644 index 00000000..0fdb6b12 --- /dev/null +++ b/docs/manual/mod/mod_disk_cache.html.ja.euc-jp @@ -0,0 +1,174 @@ + + + +mod_disk_cache - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_disk_cache

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:URI ¤ò¥­¡¼¤Ë¤·¤¿¥³¥ó¥Æ¥ó¥Ä¥­¥ã¥Ã¥·¥å¥¹¥È¥ì¡¼¥¸´ÉÍý
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:disk_cache_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_disk_cache.c
+

³µÍ×

+ +

mod_disk_cache ¤Ï¥Ç¥£¥¹¥¯¤ò»ÈÍѤ·¤¿¥¹¥È¥ì¡¼¥¸ + ´ÉÍýµ¡¹½¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£¼ç¤Ë + mod_cache ¤ÈÁȤ߹ç¤ï¤»¤Æ»È¤ï¤ì¤Þ¤¹¡£

+ +

¥³¥ó¥Æ¥ó¥Ä¤Î¥­¥ã¥Ã¥·¥å¤Ø¤ÎÊݸ¤È¼èÆÀ¤Ï URI ¤Ë´ð¤Å¤¤¤¿¥­¡¼¤¬»È¤ï¤ì¤Þ¤¹¡£ + ¥¢¥¯¥»¥¹Êݸî¤Î¤«¤±¤é¤ì¤Æ¤¤¤ë¥³¥ó¥Æ¥ó¥Ä¤Ï¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£

+ +

¥­¥ã¥Ã¥·¥å¤ÎÂ礭¤µ¤òºÇÂç¥ì¥Ù¥ë¤Ç°Ý»ý¤¹¤ë¤¿¤á¤Ë + htcacheclean ¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Ãí:

+

mod_disk_cache ¤Ï + mod_cache ¤òɬÍפȤ·¤Þ¤¹

+
+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +
+ +
top
+

CacheDirLength ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê̾¤Îʸ»ú¿ô
¹½Ê¸:CacheDirLength length
¥Ç¥Õ¥©¥ë¥È:CacheDirLength 2
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_disk_cache
+

CacheDirLength ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥­¥ã¥Ã¥·¥å + ³¬Áؤγƥµ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Îʸ»ú¿ô¤òÀßÄꤷ¤Þ¤¹¡£

+ +
+

CacheDirLevels* + CacheDirLength ¤Î + ·ë²Ì¤Ï 20 °ÊÆâ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
+ +

+ CacheDirLength 4 +

+ +
+
top
+

CacheDirLevels ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Î¿¼¤µ¤Î¿ô
¹½Ê¸:CacheDirLevels levels
¥Ç¥Õ¥©¥ë¥È:CacheDirLevels 3
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_disk_cache
+

CacheDirLevels ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥­¥ã¥Ã¥·¥å¤Î + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Î¿¼¤µ¤òÀßÄꤷ¤Þ¤¹¡£¥­¥ã¥Ã¥·¥å¥Ç¡¼¥¿¤Ï CacheRoot ¥Ç¥£¥ì¥¯¥È¥ê¤«¤é + ¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î¿¼¤µÊ¬²¼¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ËÊݸ¤µ¤ì¤Þ¤¹¡£

+ +
+

CacheDirLevels* + CacheDirLength ¤Î + ·ë²Ì¤Ï 20 °ÊÆâ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
+ +

+ CacheDirLevels 5 +

+ +
+
top
+

CacheMaxFileSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤ËÊݴɤµ¤ì¤ë¥É¥­¥å¥á¥ó¥È¤ÎºÇÂç¤Î (¥Ð¥¤¥È¤Ç¤Î) ¥µ¥¤¥º
¹½Ê¸:CacheMaxFileSize bytes
¥Ç¥Õ¥©¥ë¥È:CacheMaxFileSize 1000000
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_disk_cache
+

CacheMaxFileSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤ò + ¥­¥ã¥Ã¥·¥å¤¹¤ë¤«¤É¤¦¤«¤òȽÄꤹ¤ë¡¢ºÇÂç¤Î¥µ¥¤¥º¤ò¥Ð¥¤¥È¿ô¤ÇÀßÄꤷ¤Þ¤¹¡£

+ +

+ CacheMaxFileSize 64000 +

+ +
+
top
+

CacheMinFileSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤ËÊݴɤµ¤ì¤ë¥É¥­¥å¥á¥ó¥È¤ÎºÇ¾®¸Â¤Î (¥Ð¥¤¥È¤Ç¤Î) Â礭¤µ
¹½Ê¸:CacheMinFileSize bytes
¥Ç¥Õ¥©¥ë¥È:CacheMinFileSize 1
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_disk_cache
+

CacheMinFileSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤ò + ¥­¥ã¥Ã¥·¥å¤¹¤ë¤«¤É¤¦¤«¤òȽÄꤹ¤ë¡¢ºÇ¾®¤Î¥µ¥¤¥º¤ò¥Ð¥¤¥È¿ô¤ÇÀßÄꤷ¤Þ¤¹¡£

+ +

+ CacheMinFileSize 64 +

+ +
+
top
+

CacheRoot ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¥Õ¥¡¥¤¥ë¤¬Êݴɤµ¤ì¤ë¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê
¹½Ê¸:CacheRoot directory
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_disk_cache
+

CacheRoot ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥­¥ã¥Ã¥·¥å¥Õ¥¡¥¤¥ë¤ò + Êݴɤ¹¤ë¤¿¤á¤Î¥Ç¥£¥¹¥¯¾å¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤Þ¤¹¡£mod_disk_cache ¥â¥¸¥å¡¼¥ë¤¬ Apache ¥µ¡¼¥Ð¤Ë¥í¡¼¥É¤µ¤ì¤Æ + ¤¤¤ë¤«¡¢ÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ì¤Ð¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïɬ¤º + ÄêµÁ¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + CacheRoot ¤ÎÃͤò»ØÄꤷ¤Ê¤±¤ì¤Ð¡¢ + ÀßÄê¥Õ¥¡¥¤¥ë¤Î½èÍý¤Ç¥¨¥é¡¼¤Ë¤Ê¤ê¤Þ¤¹¡£CacheDirLevels ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È CacheDirLength ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + »ØÄꤵ¤ì¤¿¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê²¼¤Î¥Ç¥£¥ì¥¯¥È¥ê¹½À®¤òÄêµÁ¤·¤Þ¤¹¡£

+ +

+ CacheRoot c:/cacheroot +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_disk_cache.html.ko.euc-kr b/docs/manual/mod/mod_disk_cache.html.ko.euc-kr new file mode 100644 index 00000000..18d9142c --- /dev/null +++ b/docs/manual/mod/mod_disk_cache.html.ko.euc-kr @@ -0,0 +1,175 @@ + + + +mod_disk_cache - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_disk_cache

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:Content cache storage manager keyed to URIs
»óÅÂ:Experimental
¸ðµâ¸í:disk_cache_module
¼Ò½ºÆÄÀÏ:mod_disk_cache.c
+

¿ä¾à

+ +
+ ÀÌ ¸ðµâÀº ½ÇÇèÀûÀÎ »óÅÂÀÌ´Ù. ¹®¼­´Â ¾ÆÁ÷ ÀÛ¾÷ÁßÀÌ´Ù... +
+ +

mod_disk_cache´Â µð½ºÅ©±â¹Ý ÀúÀå°ü¸®ÀÚ¸¦ + ±¸ÇöÇÑ´Ù. ÀÌ ¸ðµâÀº ±âº»ÀûÀ¸·Î mod_proxy¿Í + °°ÀÌ »ç¿ëÇÑ´Ù.

+ +

³»¿ëÀ» URI¸¦ Åä´ë·Î ¸¸µç Å°·Î ij½¬¿¡ ÀúÀåÇÏ°í °¡Á®¿Â´Ù. + Á¢±Ùº¸È£°¡ µÈ ³»¿ëÀº ij½¬ÇÏÁö¾Ê´Â´Ù.

+ +

ÁÖÀÇ:

+

mod_disk_cache´Â + mod_cache°¡ ÇÊ¿äÇÏ´Ù.

+
+
+ + +
top
+

CacheDirLength Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÇÏÀ§µð·ºÅ丮¸íÀÇ ¹®ÀÚ°³¼ö
¹®¹ý:CacheDirLength length
±âº»°ª:CacheDirLength 2
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_disk_cache
+

CacheDirLength Áö½Ã¾î´Â ij½¬ + °èÃþ±¸Á¶¿¡¼­ °¢ ÇÏÀ§µð·ºÅ丮¸íÀÇ ¹®ÀÚ¼ö¸¦ ÁöÁ¤ÇÑ´Ù.

+ +
+

CacheDirLevels¿Í + CacheDirLength¸¦ °öÇÏ¿© 20 º¸´Ù + Å©¸é ¾ÈµÈ´Ù.

+
+ +

+ CacheDirLength 4 +

+ +
+
top
+

CacheDirLevels Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬ÀÇ ÇÏÀ§µð·ºÅ丮 ±íÀÌ.
¹®¹ý:CacheDirLevels levels
±âº»°ª:CacheDirLevels 3
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_disk_cache
+

CacheDirLevels Áö½Ã¾î´Â ij½¬ÀÇ + ÇÏÀ§µð·ºÅ丮 ±íÀ̸¦ ÁöÁ¤ÇÑ´Ù. ij½¬µÈ ÀڷḦ CacheRoot µð·ºÅ丮 + ¾Æ·¡ ÀÌ ±íÀ̱îÁö ÀúÀåÇÑ´Ù.

+ +
+

CacheDirLevels¿Í CacheDirLength¸¦ + °öÇÏ¿© 20 º¸´Ù Å©¸é ¾ÈµÈ´Ù.

+
+ +

+ CacheDirLevels 5 +

+ +
+
top
+

CacheMaxFileSize Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬¿¡ ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ´ëÅ©±â (¹ÙÀÌÆ® ´ÜÀ§)
¹®¹ý:CacheMaxFileSize bytes
±âº»°ª:CacheMaxFileSize 1000000
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_disk_cache
+

CacheMaxFileSize Áö½Ã¾î´Â ij½¬¿¡ + ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ´ëÅ©±â¸¦ ¹ÙÀÌÆ® ´ÜÀ§·Î ÁöÁ¤ÇÑ´Ù.

+ +

+ CacheMaxFileSize 64000 +

+ +
+
top
+

CacheMinFileSize Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬¿¡ ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ¼ÒÅ©±â (¹ÙÀÌÆ® ´ÜÀ§)
¹®¹ý:CacheMinFileSize bytes
±âº»°ª:CacheMinFileSize 1
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_disk_cache
+

CacheMinFileSize Áö½Ã¾î´Â ij½¬¿¡ + ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ¼ÒÅ©±â¸¦ ¹ÙÀÌÆ® ´ÜÀ§·Î ÁöÁ¤ÇÑ´Ù.

+ +

+ CacheMinFileSize 64 +

+ +
+
top
+

CacheRoot Áö½Ã¾î

+ + + + + + +
¼³¸í:ij½¬ ÆÄÀÏÀ» ÀúÀåÇÒ µð·ºÅ丮 root
¹®¹ý:CacheRoot directory
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_disk_cache
+

CacheRoot Áö½Ã¾î´Â µð½ºÅ©¿¡¼­ + ij½¬ ÆÄÀÏÀ» ÀúÀåÇÒ µð·ºÅ丮¸¦ ÁöÁ¤ÇÑ´Ù. mod_disk_cache ¸ðµâÀ» ¾ÆÆÄÄ¡ ¼­¹ö¿Í °°ÀÌ ÄÄÆÄÀÏÇÏ¿´°Å³ª + ÀоîµéÀÎ °æ¿ì ¹Ýµå½Ã ÀÌ Áö½Ã¾î¸¦ Á¤ÀÇÇØ¾ß ÇÑ´Ù. + CacheRoot¿¡ °ªÀÌ ¾øÀ¸¸é ¼³Á¤ÆÄÀÏÀ» + ó¸®ÇÏÁö ¾Ê´Â´Ù. CacheDirLevels¿Í CacheDirLength Áö½Ã¾î´Â + ÀÌ Áö½Ã¾î·Î ÁöÁ¤ÇÑ root µð·ºÅ丮ÀÇ ÇÏÀ§µð·ºÅ丮 ±¸Á¶¸¦ Áö½ÃÇÑ´Ù.

+ +

+ CacheRoot c:/cacheroot +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dumpio.html b/docs/manual/mod/mod_dumpio.html new file mode 100644 index 00000000..2548737a --- /dev/null +++ b/docs/manual/mod/mod_dumpio.html @@ -0,0 +1,7 @@ +URI: mod_dumpio.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_dumpio.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_dumpio.html.en b/docs/manual/mod/mod_dumpio.html.en new file mode 100644 index 00000000..c5c3ca70 --- /dev/null +++ b/docs/manual/mod/mod_dumpio.html.en @@ -0,0 +1,106 @@ + + + +mod_dumpio - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_dumpio

+
+

Available Languages:  en  | + ja 

+
+ + + +
Description:Dumps all I/O to error log as desired.
Status:Extension
Module Identifier:dumpio_module
Source File:mod_dumpio.c
+

Summary

+ +

mod_dumpio allows for the logging of + all input received by Apache and/or all output sent by + Apache to be logged (dumped) to the error.log file. +

+ +

The data logging is done right after SSL decoding (for + input) and right before SSL encoding (for output). As can + be expected, this can produce extreme volumes of data, + and should only be used when debugging problems.

+
+

Directives

+ +

Topics

+
+
top
+
+

Enabling dumpio Support

+ + +

To enable the module, it should be compiled and + loaded in to your running Apache configuration. Logging + can then be enabled or disabled via the below directives.

+
+
top
+

DumpIOInput Directive

+ + + + + + + + +
Description:Dump all input data to the error log
Syntax:DumpIOInput On|Off
Default:DumpIOInput Off
Context:server config
Status:Extension
Module:mod_dumpio
Compatibility:DumpIOInput is only available in Apache 2.1.3 and +later.
+

Enable dumping of all input.

+ +

Example

+ DumpIOInput On +

+ +
+
top
+

DumpIOOutput Directive

+ + + + + + + + +
Description:Dump all output data to the error log
Syntax:DumpIOOutput On|Off
Default:DumpIOOutput Off
Context:server config
Status:Extension
Module:mod_dumpio
Compatibility:DumpIOOutput is only available in Apache 2.1.3 and +later.
+

Enable dumping of all output.

+ +

Example

+ DumpIOOutput On +

+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_dumpio.html.ja.euc-jp b/docs/manual/mod/mod_dumpio.html.ja.euc-jp new file mode 100644 index 00000000..0751c8b3 --- /dev/null +++ b/docs/manual/mod/mod_dumpio.html.ja.euc-jp @@ -0,0 +1,105 @@ + + + +mod_dumpio - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_dumpio

+
+

Available Languages:  en  | + ja 

+
+ + + +
ÀâÌÀ:˾¤à¤è¤¦¤Ë¤¹¤Ù¤Æ¤Î I/O ¤ò¥¨¥é¡¼¥í¥°¤Ë¥À¥ó¥×¤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:dumpio_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_dumpio.c
+

³µÍ×

+ +

mod_dumpio ¤ò»È¤¦¤È¡¢Apache ¤¬¼õ¤±¼è¤Ã¤¿¤¹¤Ù¤Æ¤ÎÆþÎÏ¤È + Apache ¤Ë¤è¤êÁ÷¤é¤ì¤¿¤¹¤Ù¤Æ¤Î½ÐÎϤȤΡ¢Î¾Êý¤â¤·¤¯¤Ï¤É¤Á¤é¤«°ìÊý¤ò¡¢ + ¥¨¥é¡¼¥í¥°¥Õ¥¡¥¤¥ë¤Ë¥í¥°¼ý½¸ (ÌõÃí: ¥À¥ó¥× dump) + ¤Ç¤­¤Þ¤¹¡£

+ +

¥Ç¡¼¥¿¤Î¥í¥®¥ó¥°¤Ï¡¢SSL Éü¹æ²½¤Îľ¸å (ÆþÎÏ) ¤È SSL + °Å¹æ²½¤ÎľÁ° (½ÐÎÏ) ¤Ë¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£¤´ÁÛÁü¤ÎÄ̤ꡢ + ¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¤È¤Æ¤Ä¤â¤Ê¤¤¥Ç¡¼¥¿Î̤ò½ÐÎϤ·¤Þ¤¹¤Î¤Ç¡¢ + ÌäÂê¤ò¥Ç¥Ð¥Ã¥°¤·¤Æ¤¤¤ë¤È¤­¤Ë¤Î¤ß»ÈÍѤ¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

¥È¥Ô¥Ã¥¯

+
+
top
+
+

dumpio ¥µ¥Ý¡¼¥È¤òÍ­¸ú¤Ë¤¹¤ë

+ + +

¤³¤Î¥â¥¸¥å¡¼¥ë¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢¥â¥¸¥å¡¼¥ë¤¬¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤Æ¡¢ + ¼Â¹Ô¤¹¤ë Apache ¤ÎÀßÄê¤Ç¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¥í¥®¥ó¥°µ¡Ç½¤Ï¡¢°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤ÆÍ­¸ú¤Ë¤·¤¿¤ê + ̵¸ú¤Ë¤·¤¿¤ê¤Ç¤­¤Þ¤¹¡£

+
+
top
+

DumpIOInput ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥¨¥é¡¼¥í¥°¤Ë¤¹¤Ù¤Æ¤ÎÆþÎϥǡ¼¥¿¤ò¥À¥ó¥×
¹½Ê¸:DumpIOInput On|Off
¥Ç¥Õ¥©¥ë¥È:DumpIOInput Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_dumpio
¸ß´¹À­:DumpIOInput ¤Ï Apache 2.1.3 °Ê¹ß¤Î¤ß¤Ç»ÈÍѲÄǽ
+

¤¹¤Ù¤Æ¤ÎÆþÎϤΥÀ¥ó¥×¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£

+ +

Îã

+ DumpIOInput On +

+ +
+
top
+

DumpIOOutput ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥¨¥é¡¼¥í¥°¤Ë¤¹¤Ù¤Æ¤Î½ÐÎϥǡ¼¥¿¤ò¥À¥ó¥×
¹½Ê¸:DumpIOOutput On|Off
¥Ç¥Õ¥©¥ë¥È:DumpIOOutput Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_dumpio
¸ß´¹À­:DumpIOOutput ¤Ï Apache 2.1.3 °Ê¹ß¤Ç¤Î¤ß»ÈÍѲÄǽ
+

¤¹¤Ù¤Æ¤Î½ÐÎϤΥÀ¥ó¥×¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£

+ +

Îã

+ DumpIOOutput On +

+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_echo.html b/docs/manual/mod/mod_echo.html new file mode 100644 index 00000000..f4db4ba0 --- /dev/null +++ b/docs/manual/mod/mod_echo.html @@ -0,0 +1,11 @@ +URI: mod_echo.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_echo.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_echo.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_echo.html.en b/docs/manual/mod/mod_echo.html.en new file mode 100644 index 00000000..8ea950d7 --- /dev/null +++ b/docs/manual/mod/mod_echo.html.en @@ -0,0 +1,73 @@ + + + +mod_echo - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_echo

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:A simple echo server to illustrate protocol +modules
Status:Experimental
Module Identifier:echo_module
Source File:mod_echo.c
Compatibility:Available in Apache 2.0 and later
+

Summary

+ +

This module provides an example protocol module to illustrate the + concept. It provides a simple echo server. Telnet to it and type + stuff, and it will echo it.

+
+

Directives

+ +
+ +
top
+

ProtocolEcho Directive

+ + + + + + + +
Description:Turn the echo server on or off
Syntax:ProtocolEcho On|Off
Context:server config, virtual host
Status:Experimental
Module:mod_echo
Compatibility:ProtocolEcho is only available in 2.0 and +later.
+

The ProtocolEcho directive enables or + disables the echo server.

+ +

Example

+ ProtocolEcho On +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_echo.html.ja.euc-jp b/docs/manual/mod/mod_echo.html.ja.euc-jp new file mode 100644 index 00000000..159bdbe1 --- /dev/null +++ b/docs/manual/mod/mod_echo.html.ja.euc-jp @@ -0,0 +1,72 @@ + + + +mod_echo - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_echo

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:¥×¥í¥È¥³¥ë¥â¥¸¥å¡¼¥ë¤Î³µÍפò¼¨¤¹¤¿¤á¤Îñ½ã¤Ê¥¨¥³¡¼¥µ¡¼¥Ð +
¥¹¥Æ¡¼¥¿¥¹:Experimental
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:echo_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_echo.c
¸ß´¹À­:Apache 2.0 °Ê¹ß
+

³µÍ×

+ +

Ëܥ⥸¥å¡¼¥ë¤Ï¥³¥ó¥»¥×¥È¤òÅÁ¤¨¤ë¤¿¤á¤Î¥×¥í¥È¥³¥ë¥â¥¸¥å¡¼¥ë¤Î + ¼ÂÁõÎã¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£Ã±½ã¤Ê¥¨¥³¡¼¥µ¡¼¥Ð¤òÄ󶡤·¤Þ¤¹¡£ + Telnet ¤ÇÀܳ¤·¡¢Ê¸»úÎó¤òÁ÷¿®¤¹¤ë¤È¡¢¥¨¥³¡¼¤òÊÖ¤·¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +
+ +
top
+

ProtocolEcho ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¨¥³¡¼¥µ¡¼¥Ð¤ÎÍ­¸ú̵¸ú¤òÀßÄꤷ¤Þ¤¹¡£
¹½Ê¸:ProtocolEcho On|Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Experimental
¥â¥¸¥å¡¼¥ë:mod_echo
¸ß´¹À­:Apache 2.0 °Ê¹ß
+

ProtocolEcho ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + ¥¨¥³¡¼¥µ¡¼¥Ð¤ÎÍ­¸ú̵¸ú¤òÀßÄꤷ¤Þ¤¹¡£

+ +

Îã

+ ProtocolEcho On +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_echo.html.ko.euc-kr b/docs/manual/mod/mod_echo.html.ko.euc-kr new file mode 100644 index 00000000..60c5397b --- /dev/null +++ b/docs/manual/mod/mod_echo.html.ko.euc-kr @@ -0,0 +1,71 @@ + + + +mod_echo - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_echo

+
+

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

+
+ + + + +
¼³¸í:ÇÁ·ÎÅäÄÝ ¸ðµâÀ» ¼³¸íÇϱâÀ§ÇÑ °£´ÜÇÑ echo ¼­¹ö
»óÅÂ:Experimental
¸ðµâ¸í:echo_module
¼Ò½ºÆÄÀÏ:mod_echo.c
Áö¿ø:Apache 2.0 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ÇÁ·ÎÅäÄÝ ¸ðµâÀÇ °³³äÀ» ¼³¸íÇϱâÀ§ÇÑ ¿¹Á¦ÀÌ´Ù. + ÀÌ ¸ðµâÀº °£´ÜÇÑ echo ¼­¹ö¸¦ ±¸ÇöÇÑ´Ù. ÀÌ ¼­¹ö·Î telnetÇÏ¿© + ¹«¾ð°¡¸¦ ÀÔ·ÂÇϸé, ¼­¹ö´Â ÀÔ·ÂÇÑ ³»¿ëÀÌ ±×´ë·Î ¹ÝȯÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +
+ +
top
+

ProtocolEcho Áö½Ã¾î

+ + + + + + + +
¼³¸í:echo ¼­¹ö¸¦ Å°°í ²ö´Ù
¹®¹ý:ProtocolEcho On|Off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Experimental
¸ðµâ:mod_echo
Áö¿ø:ProtocolEcho´Â 2.0 ÀÌÈÄ¿¡¸¸ ÀÖ´Ù.
+

ProtocolEcho Áö½Ã¾î´Â echo ¼­¹ö¸¦ + Å°°í ²ö´Ù.

+ +

¿¹Á¦

+ ProtocolEcho On +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_env.html b/docs/manual/mod/mod_env.html new file mode 100644 index 00000000..00d518a7 --- /dev/null +++ b/docs/manual/mod/mod_env.html @@ -0,0 +1,11 @@ +URI: mod_env.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_env.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_env.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_env.html.en b/docs/manual/mod/mod_env.html.en new file mode 100644 index 00000000..91be154c --- /dev/null +++ b/docs/manual/mod/mod_env.html.en @@ -0,0 +1,117 @@ + + + +mod_env - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_env

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Modifies the environment which is passed to CGI scripts and +SSI pages
Status:Base
Module Identifier:env_module
Source File:mod_env.c
+

Summary

+ +

This module allows for control of the environment that will + be provided to CGI scripts and SSI pages. Environment variables + may be passed from the shell which invoked the httpd + process. Alternatively, environment variables may be set or unset within + the configuration process.

+
+

Directives

+ +

See also

+
+ +
top
+

PassEnv Directive

+ + + + + + + +
Description:Passes environment variables from the shell
Syntax:PassEnv env-variable [env-variable] +...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_env
+

Specifies one or more environment variables to pass to CGI + scripts and SSI pages from the environment of the shell which + invoked the httpd process.

+ +

Example

+ PassEnv LD_LIBRARY_PATH +

+ +
+
top
+

SetEnv Directive

+ + + + + + + +
Description:Sets environment variables
Syntax:SetEnv env-variable value
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_env
+

Sets an environment variable, which is then passed on to CGI + scripts and SSI pages.

+ +

Example

+ SetEnv SPECIAL_PATH /foo/bin +

+ +
+
top
+

UnsetEnv Directive

+ + + + + + + +
Description:Removes variables from the environment
Syntax:UnsetEnv env-variable [env-variable] +...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_env
+

Removes one or more environment variables from those passed + on to CGI scripts and SSI pages.

+ +

Example

+ UnsetEnv LD_LIBRARY_PATH +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_env.html.ja.euc-jp b/docs/manual/mod/mod_env.html.ja.euc-jp new file mode 100644 index 00000000..bc31f79f --- /dev/null +++ b/docs/manual/mod/mod_env.html.ja.euc-jp @@ -0,0 +1,117 @@ + + + +mod_env - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_env

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:CGI ¥¹¥¯¥ê¥×¥ÈµÚ¤Ó SSI +¥Ú¡¼¥¸¤ËÅϤµ¤ì¤ë´Ä¶­ÊÑ¿ô¤òÊѹ¹¤¹¤ëµ¡Ç½¤òÄ󶡤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:env_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_env.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ë¤è¤ê CGI ¥¹¥¯¥ê¥×¥È¤È SSI + ¥Ú¡¼¥¸¤ËŬÍѤµ¤ì¤ë´Ä¶­ÊÑ¿ô¤òÀ©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ´Ä¶­ÊÑ¿ô¤Ï httpd ¥×¥í¥»¥¹¤òµ¯Æ°¤·¤¿¥·¥§¥ë¤«¤éÅϤµ¤ì¤Þ¤¹¡£¤Þ¤¿¡¢ + ÀßÄê¥Õ¥¡¥¤¥ë¤Ç´Ä¶­ÊÑ¿ô¤òÀßÄꤷ¤¿¤ê¡¢ºï½ü¤·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

PassEnv ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥·¥§¥ë¤«¤é¤Î´Ä¶­ÊÑ¿ô¤òÅϤ¹
¹½Ê¸:PassEnv env-variable [env-variable] +...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_env
+ +

httpd ¥×¥í¥»¥¹¤òµ¯Æ°¤·¤¿¥·¥§¥ë¤Î´Ä¶­¤«¤é CGI ¥¹¥¯¥ê¥×¥È¤È + SSI ¥Ú¡¼¥¸¤ËÅϤ¹´Ä¶­ÊÑ¿ô¤ò°ì¤Ä°Ê¾å»ØÄꤷ¤Þ¤¹¡£

+ +

Îã

+ PassEnv LD_LIBRARY_PATH +

+ +
+
top
+

SetEnv ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë
¹½Ê¸:SetEnv env-variable value
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_env
+

´Ä¶­ÊÑ¿ô¤òÀßÄꤷ¡¢¤½¤ì¤ò CGI ¥¹¥¯¥ê¥×¥È¤È SSI + ¥Ú¡¼¥¸¤ËÅϤ¹¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

Îã

+ SetEnv SPECIAL_PATH /foo/bin +

+ +
+
top
+

UnsetEnv ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:´Ä¶­¤«¤éÊÑ¿ô¤ò¼è¤ê½ü¤¯
¹½Ê¸:UnsetEnv env-variable [env-variable] +...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_env
+

CGI ¥¹¥¯¥ê¥×¥È¤È SSI + ¥Ú¡¼¥¸¤ËÅϤµ¤ì¤ë´Ä¶­ÊÑ¿ô¤«¤é»ØÄꤵ¤ì¤¿´Ä¶­ÊÑ¿ô¤ò¼è¤ê½ü¤­¤Þ¤¹¡£

+ +

Îã

+ UnsetEnv LD_LIBRARY_PATH +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_env.html.ko.euc-kr b/docs/manual/mod/mod_env.html.ko.euc-kr new file mode 100644 index 00000000..c50969fd --- /dev/null +++ b/docs/manual/mod/mod_env.html.ko.euc-kr @@ -0,0 +1,114 @@ + + + +mod_env - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_env

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:CGI ½ºÅ©¸³Æ®³ª SSI ÆäÀÌÁö¿¡ Àü´ÞÇÒ È¯°æº¯¼ö¸¦ +¼öÁ¤ÇÑ´Ù
»óÅÂ:Base
¸ðµâ¸í:env_module
¼Ò½ºÆÄÀÏ:mod_env.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº CGI ½ºÅ©¸³Æ®³ª SSI ÆäÀÌÁö¿¡ Àü´ÞÇÒ È¯°æº¯¼ö¸¦ + Á¶ÀýÇÑ´Ù. À¥¼­¹ö¸¦ ½ÃÀÛÇÑ ½©¿¡¼­ ȯ°æº¯¼ö¸¦ °¡Á®¿Ã ¼ö ÀÖ´Ù. + ¾Æ´Ï¸é ¼³Á¤°úÁ¤Áß¿¡ ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÏ°í Á¦°ÅÇÒ ¼ö ÀÖ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

PassEnv Áö½Ã¾î

+ + + + + + + +
¼³¸í:½©¿¡¼­ ȯ°æº¯¼ö¸¦ °¡Á®¿Â´Ù
¹®¹ý:PassEnv env-variable [env-variable] +...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_env
+

À¥¼­¹ö¸¦ ½ÇÇàÇÑ ½©ÀÇ Æ¯Á¤ ȯ°æº¯¼ö¸¦ CGI ½ºÅ©¸³Æ®³ª + SSI ÆäÀÌÁö·Î Àü´ÞÇÑ´Ù.

+ +

¿¹Á¦

+ PassEnv LD_LIBRARY_PATH +

+ +
+
top
+

SetEnv Áö½Ã¾î

+ + + + + + + +
¼³¸í:ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù
¹®¹ý:SetEnv env-variable value
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_env
+

CGI ½ºÅ©¸³Æ®³ª SSI ÆäÀÌÁö¿¡ Àü´ÞÇÒ È¯°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù.

+ +

¿¹Á¦

+ SetEnv SPECIAL_PATH /foo/bin +

+ +
+
top
+

UnsetEnv Áö½Ã¾î

+ + + + + + + +
¼³¸í:ȯ°æº¯¼ö¸¦ Á¦°ÅÇÑ´Ù
¹®¹ý:UnsetEnv env-variable [env-variable] +...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_env
+

CGI ½ºÅ©¸³Æ®³ª SSI ÆäÀÌÁö¿¡ ȯ°æº¯¼ö¸¦ Àü´ÞÇÏÁö ¾Ê´Â´Ù.

+ +

¿¹Á¦

+ UnsetEnv LD_LIBRARY_PATH +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_example.html b/docs/manual/mod/mod_example.html new file mode 100644 index 00000000..41b1d56e --- /dev/null +++ b/docs/manual/mod/mod_example.html @@ -0,0 +1,7 @@ +URI: mod_example.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_example.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_example.html.en b/docs/manual/mod/mod_example.html.en new file mode 100644 index 00000000..ce42e380 --- /dev/null +++ b/docs/manual/mod/mod_example.html.en @@ -0,0 +1,156 @@ + + + +mod_example - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_example

+
+

Available Languages:  en  | + ko 

+
+ + + +
Description:Illustrates the Apache module API
Status:Experimental
Module Identifier:example_module
Source File:mod_example.c
+

Summary

+ +

Some files in the modules/experimental directory + under the Apache distribution directory tree are provided as an + example to those that wish to write modules that use the Apache + API.

+ +

The main file is mod_example.c, which + illustrates all the different callback mechanisms and call + syntaxes. By no means does an add-on module need to include + routines for all of the callbacks - quite the contrary!

+ +

The example module is an actual working module. If you link + it into your server, enable the "example-handler" handler for a + location, and then browse to that location, you will see a + display of some of the tracing the example module did as the + various callbacks were made.

+
+ +
top
+
+

Compiling the example module

+ +

To include the example module in your server, follow the + steps below:

+ +
    +
  1. + Run configure with --enable-example + option.
    2. + +
  2. Make the server (run "make").
    3. +
+ +

To add another module of your own:

+ +
    +
  1. cp modules/experimental/mod_example.c + modules/new_module/mod_myexample.c
    2. + +
  2. Modify the file.
    3. + +
  3. Create modules/new_module/config.m4. +
      +
    1. Add APACHE_MODPATH_INIT(new_module).
      2. +
    2. Copy APACHE_MODULE line with "example" from + modules/experimental/config.m4.
      3. +
    3. Replace the first argument "example" with myexample.
      4. +
    4. Replace the second argument with brief description of your module. + It will be used in configure --help.
      5. +
    5. If your module needs additional C compiler flags, linker flags or + libraries, add them to CFLAGS, LDFLAGS and LIBS accordingly. + See other config.m4 files in modules directory for + examples.
      6. +
    6. Add APACHE_MODPATH_FINISH.
      7. +
    +
    4. + +
  4. Create module/new_module/Makefile.in. + If your module doesn't need special build instructions, + all you need to have in that file is + include $(top_srcdir)/build/special.mk.
    5. + +
  5. Run ./buildconf from the top-level directory.
    6. + +
  6. Build the server with --enable-myexample
    7. + +
+
top
+
+

Using the mod_example Module

+ +

To activate the example module, include a block similar to + the following in your httpd.conf file:

+

+ <Location /example-info>
+ SetHandler example-handler
+ </Location> +

+ +

As an alternative, you can put the following into a .htaccess file + and then request the file "test.example" from that location:

+

+ AddHandler example-handler .example +

+ +

After reloading/restarting your server, you should be able + to browse to this location and see the brief display mentioned + earlier.

+
+
top
+

Example Directive

+ + + + + + +
Description:Demonstration directive to illustrate the Apache module +API
Syntax:Example
Context:server config, virtual host, directory, .htaccess
Status:Experimental
Module:mod_example
+

The Example directive just sets a demonstration + flag which the example module's content handler displays. It + takes no arguments. If you browse to an URL to which the + example content-handler applies, you will get a display of the + routines within the module and how and in what order they were + called to service the document request. The effect of this + directive one can observe under the point "Example + directive declared here: YES/NO".

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_example.html.ko.euc-kr b/docs/manual/mod/mod_example.html.ko.euc-kr new file mode 100644 index 00000000..b87807ca --- /dev/null +++ b/docs/manual/mod/mod_example.html.ko.euc-kr @@ -0,0 +1,155 @@ + + + +mod_example - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_example

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:¾ÆÆÄÄ¡ ¸ðµâ API¸¦ ¼³¸íÇÑ´Ù
»óÅÂ:Experimental
¸ðµâ¸í:example_module
¼Ò½ºÆÄÀÏ:mod_example.c
+

¿ä¾à

+ +

¾ÆÆÄÄ¡ ¹èÆ÷º» modules/experimental µð·ºÅ丮¿¡ + ÀÖ´Â ÆÄÀϵéÀº ¾ÆÆÄÄ¡ API¸¦ »ç¿ëÇÏ¿© ¸ðµâÀ» ÀÛ¼ºÇÏ·Á´Â »ç¶÷µéÀ» + µ½±âÀ§ÇÑ ¿¹Á¦´Ù.

+ +

mod_example.c´Â ¸ðµç Äݹé(callback) ±¸Á¶¿Í + È£Ãâ ¹®¹ýÀ» ¼³¸íÇÏ´Â ÆÄÀÏÀÌ´Ù. ´ç½ÅÀº ¸ðµâ¿¡ ÀÌ ¸ðµç ÄݹéÀ» + ±¸ÇöÇÒ ÇÊ¿ä°¡ ¾ø´Ù. »ç½Ç Á¤¹Ý´ë´Ù!

+ +

example ¸ðµâÀº ½ÇÁ¦·Î µ¿ÀÛÇÏ´Â ¸ðµâÀÌ´Ù. ÀÌ ¸ðµâÀ» ¼­¹ö¿¡ + ¿¬°áÇÏ°í ƯÁ¤ À§Ä¡¿¡ "example-handler" Çڵ鷯¸¦ ÇÒ´çÇÏ¿© + ±×°÷À» ºê¶ó¿ì¡Çϸé example ¸ðµâÀÇ ¿©·¯ ÄݹéÀ» È®ÀÎÇÒ ¼ö + ÀÖ´Ù.

+
+ +
top
+
+

example ¸ðµâ ÄÄÆÄÀÏÇϱâ

+ +

¼­¹ö¿¡ example ¸ðµâÀ» Æ÷ÇÔÇÏ·Á¸é ´ÙÀ½ °úÁ¤À» °ÅÄ£´Ù:

+ +
    +
  1. + --enable-example ¿É¼Ç°ú ÇÔ²² + configure¸¦ ½ÇÇàÇÑ´Ù.
    2. + +
  2. ¼­¹ö¸¦ ÄÄÆÄÀÏÇÑ´Ù ("make"¸¦ ½ÇÇàÇÑ´Ù).
    3. +
+ +

ÀÚ½ÅÀÌ ¸¸µç ¸ðµâÀ» Ãß°¡ÇÏ·Á¸é:

+ +
    +
  1. cp modules/experimental/mod_example.c + modules/new_module/mod_myexample.c
    2. + +
  2. ÆÄÀÏÀ» ¼öÁ¤ÇÑ´Ù.
    3. + +
  3. modules/new_module/config.m4 ÆÄÀÏÀ» ¸¸µç´Ù. +
      +
    1. APACHE_MODPATH_INIT(new_module)À» + Ãß°¡ÇÑ´Ù.
      2. +
    2. modules/experimental/config.m4 ÆÄÀÏ¿¡¼­ + "example"ÀÌ ÀÖ´Â APACHE_MODULE ÁÙÀ» º¹»çÇؿ´Ù.
      3. +
    3. ù¹ø° ¾Æ±Ô¸ÕÆ® "example"À» myexample·Î + º¯°æÇÑ´Ù.
      4. +
    4. µÎ¹ø° ¾Æ±Ô¸ÕÆ® ÀÚ¸®¿¡ ÀÚ½ÅÀÌ ¸¸µç ¸ðµâ¿¡ ´ëÇÑ + °£´ÜÇÑ ¼³¸íÀ» Àû´Â´Ù. configure --help¸¦ + ½ÇÇàÇÏ¸é ¿©±â¿¡ ±â·ÏÇÑ ¼³¸íÀ» º¸¿©ÁØ´Ù.
      5. +
    5. ¸ðµâÀ» ÄÄÆÄÀÏÇÒ¶§ Ưº°ÇÑ C ÄÄÆÄÀÏ·¯ ¿É¼Ç, ¸µÄ¿ + ¿É¼Ç, ¶óÀ̺귯¸®°¡ ÇÊ¿äÇÏ¸é °¢°¢ CFLAGS, LDFLAGS, + LIBS¿¡ Ãß°¡ÇÑ´Ù. modules µð·ºÅ丮¿¡ ÀÖ´Â ´Ù¸¥ + config.m4 ÆÄÀϵéÀ» Âü°íÇ϶ó.
      6. +
    6. APACHE_MODPATH_FINISH¸¦ Ãß°¡ÇÑ´Ù.
      7. +
    +
    4. + +
  4. module/new_module/Makefile.in ÆÄÀÏÀ» + ¸¸µç´Ù. ¸ðµâÀ» ÄÄÆÄÀÏÇϴµ¥ Ưº°ÇÑ ¸í·É¾î°¡ ÇÊ¿ä¾ø´Ù¸é, + ÆÄÀÏ¿¡ include $(top_srcdir)/build/special.mk¸¸ + À־ µÈ´Ù.
    5. + +
  5. ÃÖ»óÀ§ µð·ºÅ丮¿¡¼­ ./buildconf ¸¦ ½ÇÇàÇÑ´Ù.
    6. + +
  6. --enable-myexample ¿É¼ÇÀ» »ç¿ëÇÏ¿© ¼­¹ö¸¦ ÄÄÆÄÀÏÇÑ´Ù
    7. + +
+
top
+
+

mod_example ¸ðµâ »ç¿ëÇϱâ

+ +

example ¸ðµâÀ» »ç¿ëÇÏ·Á¸é httpd.conf ÆÄÀÏ¿¡ + ´ÙÀ½°ú °°Àº ¼³Á¤À» Ãß°¡Ç϶ó:

+

+ <Location /example-info>
+ SetHandler example-handler
+ </Location> +

+ +

¾Æ´Ï¸é .htaccess + ÆÄÀÏ¿¡ ´ÙÀ½°ú °°Àº ³»¿ëÀ» Ãß°¡ÇÏ°í, ±× À§Ä¡¿¡¼­ "test.example" + °°Àº ÆÄÀÏÀ» ¿äûÇ϶ó:

+

+ AddHandler example-handler .example +

+ +

¼­¹ö¸¦ Àç½ÃÀÛÇÑ ÈÄ ÀÌ À§Ä¡¸¦ ºê¶ó¿ì¡ÇÏ¸é ¾Õ¿¡¼­ ¸»ÇÑ + ³»¿ëÀ» º¸°ÔµÉ °ÍÀÌ´Ù.

+
+
top
+

Example Áö½Ã¾î

+ + + + + + +
¼³¸í:¾ÆÆÄÄ¡ ¸ðµâ API¸¦ ¼³¸íÇϱâÀ§ÇÑ ¿¹Á¦ Áö½Ã¾î
¹®¹ý:Example
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
»óÅÂ:Experimental
¸ðµâ:mod_example
+

Example Áö½Ã¾î´Â example ¸ðµâÀÇ + ³»¿ëÇڵ鷯°¡ °£´ÜÇÑ ¹®±¸¸¦ º¸ÀÏÁö ¿©ºÎ¸¦ ¼³Á¤ÇÑ´Ù. ÀÌ Áö½Ã¾î´Â + ¾Æ±Ô¸ÕÆ®¸¦ ¹ÞÁö¾Ê´Â´Ù. example ³»¿ëÇڵ鷯¸¦ Àû¿ëÇÑ URL¿¡ + Á¢¼ÓÇÏ¸é ¹®¼­ ¿äûÀ» ¼­ºñ½ºÇϱâÀ§ÇØ ¸ðµâ¾È¿¡ ÇÔ¼öµéÀÌ ¾î¶»°Ô + ±×¸®°í ¾î¶² ¼ø¼­·Î ºÒ¸®´ÂÁö ¾Ë ¼ö ÀÖ´Ù. ÀÌ Áö½Ã¾îÀÇ È¿°ú´Â + "Example directive declared here: YES/NO"·Î + È®ÀÎÇÒ ¼ö ÀÖ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_expires.html b/docs/manual/mod/mod_expires.html new file mode 100644 index 00000000..c3692c25 --- /dev/null +++ b/docs/manual/mod/mod_expires.html @@ -0,0 +1,11 @@ +URI: mod_expires.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_expires.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_expires.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_expires.html.en b/docs/manual/mod/mod_expires.html.en new file mode 100644 index 00000000..dbe29d25 --- /dev/null +++ b/docs/manual/mod/mod_expires.html.en @@ -0,0 +1,247 @@ + + + +mod_expires - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_expires

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Generation of Expires and +Cache-Control HTTP headers according to user-specified +criteria
Status:Extension
Module Identifier:expires_module
Source File:mod_expires.c
+

Summary

+ +

This module controls the setting of the Expires + HTTP header and the max-age directive of the + Cache-Control HTTP header in server responses. The + expiration date can set to be relative to either the time the + source file was last modified, or to the time of the client + access.

+ +

These HTTP headers are an instruction to the client about the + document's validity and persistence. If cached, the document may + be fetched from the cache rather than from the source until this + time has passed. After that, the cache copy is considered + "expired" and invalid, and a new copy must be obtained from the + source.

+ +

To modify Cache-Control directives other than + max-age (see RFC + 2616 section 14.9), you can use the Header directive.

+ +
+ +
top
+
+

Alternate Interval Syntax

+

The ExpiresDefault and + ExpiresByType directives + can also be defined in a more readable syntax of the form:

+ +

+ ExpiresDefault "<base> [plus] {<num> + <type>}*"
+ ExpiresByType type/encoding "<base> [plus] + {<num> <type>}*" +

+ +

where <base> is one of:

+ +
    +
  • access
    • + +
  • now (equivalent to + 'access')
    • + +
  • modification
    • +
+ +

The plus keyword is optional. <num> + should be an integer value [acceptable to atoi()], + and <type> is one of:

+ +
    +
  • years
    • +
  • months
    • +
  • weeks
    • +
  • days
    • +
  • hours
    • +
  • minutes
    • +
  • seconds
    • +
+ +

For example, any of the following directives can be used to + make documents expire 1 month after being accessed, by + default:

+ +

+ ExpiresDefault "access plus 1 month"
+ ExpiresDefault "access plus 4 weeks"
+ ExpiresDefault "access plus 30 days" +

+ +

The expiry time can be fine-tuned by adding several + '<num> <type>' clauses:

+ +

+ ExpiresByType text/html "access plus 1 month 15 + days 2 hours"
+ ExpiresByType image/gif "modification plus 5 hours 3 + minutes" +

+ +

Note that if you use a modification date based setting, the + Expires header will not be added to content + that does not come from a file on disk. This is due to the fact + that there is no modification time for such content.

+
+
top
+

ExpiresActive Directive

+ + + + + + + +
Description:Enables generation of Expires +headers
Syntax:ExpiresActive On|Off
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Extension
Module:mod_expires
+

This directive enables or disables the generation of the + Expires and Cache-Control headers for + the document realm in question. (That is, if found in an + .htaccess file, for instance, it applies only to + documents generated from that directory.) If set to + Off, the headers will not be generated for any + document in the realm (unless overridden at a lower level, such as + an .htaccess file overriding a server config + file). If set to On, the headers will be added to + served documents according to the criteria defined by the + ExpiresByType and + ExpiresDefault + directives (q.v.).

+ +

Note that this directive does not guarantee that an + Expires or Cache-Control header will be + generated. If the criteria aren't met, no header will be sent, and + the effect will be as though this directive wasn't even + specified.

+ +
+
top
+

ExpiresByType Directive

+ + + + + + + +
Description:Value of the Expires header configured +by MIME type
Syntax:ExpiresByType MIME-type +<code>seconds
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Extension
Module:mod_expires
+

This directive defines the value of the Expires + header and the max-age directive of the + Cache-Control header generated for documents of the + specified type (e.g., text/html). The second + argument sets the number of seconds that will be added to a base + time to construct the expiration date. The Cache-Control: + max-age is calculated by subtracting the request time from + the expiration date and expressing the result in seconds.

+ +

The base time is either the last modification time of the + file, or the time of the client's access to the document. Which + should be used is specified by the + <code> field; M + means that the file's last modification time should be used as + the base time, and A means the client's access + time should be used.

+ +

The difference in effect is subtle. If M is used, + all current copies of the document in all caches will expire at + the same time, which can be good for something like a weekly + notice that's always found at the same URL. If A is + used, the date of expiration is different for each client; this + can be good for image files that don't change very often, + particularly for a set of related documents that all refer to + the same images (i.e., the images will be accessed + repeatedly within a relatively short timespan).

+ +

Example:

+ # enable expirations
+ ExpiresActive On
+ # expire GIF images after a month in the client's cache
+ ExpiresByType image/gif A2592000
+ # HTML documents are good for a week from the
+ # time they were changed
+ ExpiresByType text/html M604800 +

+ +

Note that this directive only has effect if + ExpiresActive On has been specified. It overrides, + for the specified MIME type only, any expiration date + set by the ExpiresDefault + directive.

+ +

You can also specify the expiration time calculation using + an alternate syntax, described earlier in + this document.

+ +
+
top
+

ExpiresDefault Directive

+ + + + + + + +
Description:Default algorithm for calculating expiration time
Syntax:ExpiresDefault <code>seconds
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Extension
Module:mod_expires
+

This directive sets the default algorithm for calculating the + expiration time for all documents in the affected realm. It can be + overridden on a type-by-type basis by the ExpiresByType directive. See the + description of that directive for details about the syntax of the + argument, and the alternate syntax + description as well.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_expires.html.ja.euc-jp b/docs/manual/mod/mod_expires.html.ja.euc-jp new file mode 100644 index 00000000..5024b29c --- /dev/null +++ b/docs/manual/mod/mod_expires.html.ja.euc-jp @@ -0,0 +1,233 @@ + + + +mod_expires - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_expires

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:¥æ¡¼¥¶¤Î»ØÄꤷ¤¿´ð½à¤Ë´ð¤Å¤¤¤¿ Expires ¤È +Cache-Control HTTP ¥Ø¥Ã¥À¤ÎÀ¸À®
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:expires_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_expires.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥µ¡¼¥Ð±þÅú¤Î Expires HTTP ¥Ø¥Ã¥À + ¤È Cache-Control ¥Ø¥Ã¥À¤Î max-age ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ÀßÄê¤òÀ©¸æ¤·¤Þ¤¹¡£¸µ¤Î¥Õ¥¡¥¤¥ë¤¬ºîÀ®¤µ¤ì¤¿»þ¹ï¤Þ¤¿¤Ï + ¥¯¥é¥¤¥¢¥ó¥È¤Î¥¢¥¯¥»¥¹»þ¹ï¤Î¤É¤Á¤é¤«¤Ë´ð¤Å¤¤¤Æ´ü¸ÂÀÚ¤ìÆü¤ò + ÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤ì¤é¤Î¥Ø¥Ã¥À¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ëʸ½ñ¤Î + Í­¸úÀ­¤È·Ñ³À­¤ò»Ø¼¨¤·¤Þ¤¹¡£Ê¸½ñ¤¬¥­¥ã¥Ã¥·¥å¤µ¤ì¤¿¾ì¹ç¤Ë¤Ï¡¢ + »ØÄê»þ¹ï¤Ë㤹¤ë¤Þ¤Ç¤Ï¡¢¸µ¤Î¾ì½ê¤«¤é¼èÆÀ¤¹¤ëÂå¤ï¤ê¤Ë + ¥­¥ã¥Ã¥·¥å¤µ¤ì¤Æ¤¤¤ë¤â¤Î¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤½¤Î¸å¤Ï¡¢ + ¥­¥ã¥Ã¥·¥å¤Ë¤¢¤ë¥³¥Ô¡¼¤Ï´ü¸ÂÀÚ¤ì (expired) ¤Ç̵¸ú¤Ç¤¢¤ë¤È¤µ¤ì¡¢ + ¸µ¤Î¾ì½ê¤«¤é¿·¤·¤¤¤â¤Î¤ò¼èÆÀ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

max-age °Ê³° (RFC + 2616 section 14.9 »²¾È) ¤Î Cache-Control ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + Áàºî¤¹¤ë¤Ë¤Ï Header ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

¥È¥Ô¥Ã¥¯

+
+
top
+
+

ÂåÂØ´ü´Ö»ØÄ깽ʸ

+ +

ExpiresDefault ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + ExpiresByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + °Ê²¼¤Î¤è¤êÆɤ߰פ¤¹½Ê¸¤ò»È¤Ã¤ÆÄêµÁ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ ExpiresDefault "<base> [plus] {<num> + <type>}*"
+ ExpiresByType type/encoding "<base> [plus] + {<num> <type>}*" +

+ +

<base> ¤Ï°Ê²¼¤Î¤É¤ì¤«¤Ç¤¹:

+ +
    +
  • access
    • + +
  • now ('access' ¤ÈÅù²Á)
    • + +
  • modification
    • +
+ +

plus ¥­¡¼¥ï¡¼¥É¤Ï¾Êά²Äǽ¤Ç¤¹¡£<num> + ¤Ï (atoi() ¤¬¼õ¤±ÉÕ¤±¤ë) À°¿ôÃÍ¡¢ + <type> ¤Ï°Ê²¼¤Î¤É¤ì¤«¤Ç¤¹:

+ +
    +
  • years
    • +
  • months
    • +
  • weeks
    • +
  • days
    • +
  • hours
    • +
  • minutes
    • +
  • seconds
    • +
+ +

Î㤨¤Ð¡¢°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤É¤ì¤â¥Ç¥Õ¥©¥ë¥È¤Çʸ½ñ¤¬¥¢¥¯¥»¥¹¤Î 1 ¥ö·î¸å¤Ë + ´ü¸Â¤¬ÀÚ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë»È¤¨¤Þ¤¹:

+ +

+ ExpiresDefault "access plus 1 month"
+ ExpiresDefault "access plus 4 weeks"
+ ExpiresDefault "access plus 30 days" +

+ +

´ü¸ÂÀÚ¤ì»þ¹ï¤Ï¤¤¤¯¤Ä¤« + '<num> <type>' Àá¤òÄɲ乤뤳¤È¤Ç¤è¤êºÙ¤«¤¯ + À©¸æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ ExpiresByType text/html "access plus 1 month 15 + days 2 hours"
+ ExpiresByType image/gif "modification plus 5 hours 3 + minutes" +

+ +

½¤Àµ»þ¹ï¤Ë´ð¤Å¤¤¤¿ÀßÄê¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢Expires ¥Ø¥Ã¥À¤Ï + ¥Ç¥£¥¹¥¯¤Î¥Õ¥¡¥¤¥ë°Ê³°¤Î¥³¥ó¥Æ¥ó¥Ä¤Ë¤ÏÄɲ䵤ì¤Ê¤¤¤³¤È¤ËÃí°Õ + ¤·¤Æ¤¯¤À¤µ¤¤¡£¤½¤Î¤è¤¦¤Ê¥³¥ó¥Æ¥ó¥Ä¤Ë¤Ï½¤Àµ»þ¹ï¤Ï¸ºß¤·¤Ê¤¤¤«¤é¤Ç¤¹¡£

+
+
top
+

ExpiresActive ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:Expires ¥Ø¥Ã¥À¤ÎÀ¸À®¤òÍ­¸ú¤Ë¤¹¤ë
¹½Ê¸:ExpiresActive On|Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_expires
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÂбþ¤¹¤ë¥É¥­¥å¥á¥ó¥È¤ÎÎΰè¤Ç + Expires ¤È Cache-Control¥Ø¥Ã¥À¤ò + Í­¸ú¤Ë¤¹¤ë¤«Ìµ¸ú¤Ë¤¹¤ë¤«¤ò·è¤á¤Þ¤¹¡£ + (Î㤨¤Ð¡¢.htaccess ¥Õ¥¡¥¤¥ë¤Ç¤Ï¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î + ʸ½ñ¤Î¤ß¤ËŬÍѤµ¤ì¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£) Off ¤Ë + ÀßÄꤵ¤ì¤¿¾ì¹ç¤ÏÂбþÎΰè¤Ç¤½¤ì¤é¤Î¥Ø¥Ã¥À¤Ï + À¸À®¤µ¤ì¤Þ¤»¤ó (.htaccess ¤¬¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤ÎÀßÄê¤ò + ¾å½ñ¤­¤¹¤ë¡¢¤È¤¤¤¦¤è¤¦¤Ê²¼°Ì¥ì¥Ù¥ë¤Ç¤Î¾å½ñ¤­¤¬¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð)¡£ + On ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢¥Ø¥Ã¥À¤Ï ExpiresByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + ExpiresDefault ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤Î´ð½à¤Ë½¾¤Ã¤Æʸ½ñ¤Ë¥Ø¥Ã¥À¤òÄɲä·¤Þ¤¹ (³Æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö»²¾È)¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Expires ¤È + Cache-Control ¥Ø¥Ã¥À¤Î¸ºß¤ò + Êݾڤ¹¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£´ð½à¤¬Ëþ¤¿¤µ¤ì¤Æ + ¤¤¤Ê¤¤¾ì¹ç¤Ï¥Ø¥Ã¥À¤ÏÄɲ䵤줺¡¢·ë²Ì¤È¤·¤Æ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + »ØÄꤵ¤ì¤Æ¤¤¤Ê¤«¤Ã¤¿¤«¤Î¤è¤¦¤Ë¤µ¤¨¸«¤¨¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +
+
top
+

ExpiresByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:MIME ¥¿¥¤¥×¤Ë¤è¤Ã¤ÆÀßÄꤵ¤ì¤ë Expires ¥Ø¥Ã¥À¤ÎÃÍ
¹½Ê¸:ExpiresByType MIME-type +<code>seconds
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_expires
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï»ØÄꤵ¤ì¤¿¥¿¥¤¥×¤Î¥É¥­¥å¥á¥ó¥È + (Î㤨¤Ð text/html) + ¤ËÂФ·¤ÆÀ¸À®¤µ¤ì¤ë Expires ¥Ø¥Ã¥À¤È Cache-Control + ¥Ø¥Ã¥À¤Î max-age ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃͤòÄêµÁ¤·¤Þ¤¹¡£ + Æó¤ÄÌܤΰú¿ô¤Ï´ü¸ÂÀÚ¤ì¤ÎÆü»þ¤òÀ¸À®¤¹¤ë¤¿¤á¤Î´ð½à»þ¹ï¤ËÄɲ䵤ì¤ë + Éÿô¤òÀßÄꤷ¤Þ¤¹¡£Cache-Control: + max-age ¤Ï´ü¸ÂÀÚ¤ì¤Î»þ¹ï¤«¤é¥ê¥¯¥¨¥¹¥È»þ¹ï¤ò°ú¤¤¤¿¤â¤Î¤òÉÃ¤Ç + ɽ¤¹¤³¤È¤ÇÀ¸À®¤µ¤ì¤Þ¤¹¡£

+ +

´ð½à»þ¹ï¤Ï¥Õ¥¡¥¤¥ë¤ÎºÇ½ª½¤Àµ»þ¹ï¤«¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¥É¥­¥å¥á¥ó¥È¤Ø¤Î + ¥¢¥¯¥»¥¹»þ¹ï¤Ç¤¹¡£¤É¤Á¤é¤ò»È¤¦¤Ù¤­¤«¤Ï <code> + ¤Ë¤è¤Ã¤Æ»ØÄꤷ¤Þ¤¹¡£M ¤Ï´ð½à»þ¹ï¤È¤·¤Æ + ¥Õ¥¡¥¤¥ë¤ÎºÇ½ª½¤Àµ»þ¹ï¤ò¤È¤¤¤¦°ÕÌ£¤Ç¡¢A ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Î + ¥¢¥¯¥»¥¹»þ¹ï¤ò»È¤¦¤È¤¤¤¦°ÕÌ£¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¸ú²Ì¤Ë¤ÏÈù̯¤Ê°ã¤¤¤¬¤¢¤ê¤Þ¤¹¡£M ¤¬»ÈÍѤµ¤ì¤¿¾ì¹ç¤Ï¡¢ + ¤¹¤Ù¤Æ¤Î¥­¥ã¥Ã¥·¥å¤Ë¤¢¤ë¸½ºß¤Î¥É¥­¥å¥á¥ó¥È¥­¥ã¥Ã¥·¥å¤ÏƱ»þ¤Ë´ü¸Â¤¬ + ÀÚ¤ì¤Þ¤¹¡£¤³¤ì¤ÏƱ¤¸ URL ¤ËËè½µ¾ï¤ËÃÖ¤«¤ì¤ëÊ󤻤Τ褦¤Ê¤â¤Î¤Ë¤Ï + Èó¾ï¤ËÍ­¸ú¤Ç¤¹¡£A ¤¬»ÈÍѤµ¤ì¤¿¾ì¹ç¤Ï¡¢´ü¸ÂÀÚ¤ì¤Î + »þ´Ö¤Ï³Æ¥¯¥é¥¤¥¢¥ó¥È¤Ë¤è¤Ã¤Æ°Û¤Ê¤ê¤Þ¤¹¡£¤³¤ì¤Ï¤¢¤Þ¤êÊѹ¹¤µ¤ì¤Ê¤¤ + ²èÁü¥Õ¥¡¥¤¥ë¤Ê¤É¡¢Æä˴ØÏ¢¤¹¤ë¥É¥­¥å¥á¥ó¥È·²¤¬¤¹¤Ù¤ÆƱ¤¸²èÁü¤ò + »²¾È¤¹¤ë¤È¤­ (¤¹¤Ê¤ï¤Á²èÁü¤¬Èæ³ÓŪû¤¤´ü´ÖÆâ¤Ë·«¤êÊÖ¤· + ¥¢¥¯¥»¥¹¤µ¤ì¤ë¤È¤­) ¤ËÍ­¸ú¤Ç¤¹¡£

+ +

Îã:

+ # enable expirations
+ ExpiresActive On
+ # expire GIF images after a month in the client's cache
+ ExpiresByType image/gif A2592000
+ # HTML documents are good for a week from the
+ # time they were changed
+ ExpiresByType text/html M604800 +

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï ExpiresActive On ¤¬»ØÄꤵ¤ì¤Æ¤¤¤ë + ¤È¤­¤Î¤ßÍ­¸ú¤Ç¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤³¤ì¤Ï¡¢ + »ØÄꤵ¤ì¤¿ MIME ¥¿¥¤¥×¤ËÂФ·¤Æ¤Î¤ß ExpiresDefault ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + ÀßÄꤵ¤ì¤¿´ü¸ÂÀÚ¤ì´üÆü¤ò¾å½ñ¤­¤·¤Þ¤¹¡£

+ +

¤³¤Îʸ½ñ¤ÎÁ°¤ÎÊý¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ëÂåÂع½Ê¸¤ò + »È¤Ã¤Æ´ü¸ÂÀÚ¤ì´üÆü¤Î·×»»ÊýË¡¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +
+
top
+

ExpiresDefault ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:´ü¸ÂÀÚ¤ì´üÆü¤ò·×»»¤¹¤ë¥Ç¥Õ¥©¥ë¥È¥¢¥ë¥´¥ê¥º¥à
¹½Ê¸:ExpiresDefault <code>seconds
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Indexes
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_expires
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÂбþ¤¹¤ëÈϰϤΤ¹¤Ù¤Æ¤Î¥É¥­¥å¥á¥ó¥È¤ËÂФ·¤Æ + ¥Ç¥Õ¥©¥ë¥È¤Î´ü¸ÂÀÚ¤ì´üÆü¤Î·×»»¥¢¥ë¥´¥ê¥º¥à¤òÀßÄꤷ¤Þ¤¹¡£ExpiresByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤Æ + ¥¿¥¤¥×Ëè¤Ë¾å½ñ¤­¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£°ú¿ô¤Î¹½Ê¸¤Ï¤½¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ÀâÌÀ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£¤Þ¤¿¡¢ÂåÂع½Ê¸¤â + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_expires.html.ko.euc-kr b/docs/manual/mod/mod_expires.html.ko.euc-kr new file mode 100644 index 00000000..172efb46 --- /dev/null +++ b/docs/manual/mod/mod_expires.html.ko.euc-kr @@ -0,0 +1,225 @@ + + + +mod_expires - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_expires

+
+

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

+
+ + + +
¼³¸í:»ç¿ëÀÚ°¡ ÁöÁ¤ÇÑ ±âÁØ¿¡ µû¶ó Expires¿Í +Cache-Control HTTP Çì´õ¸¦ »ý¼ºÇÑ´Ù
»óÅÂ:Extension
¸ðµâ¸í:expires_module
¼Ò½ºÆÄÀÏ:mod_expires.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ¼­¹ö ÀÀ´äÀÇ Expires HTTP Çì´õ¿Í + Cache-Control HTTP Çì´õÀÇ max-age + Áö½Ã¾î ¼³Á¤À» Á¶ÀýÇÑ´Ù. ¸¸±âÀÏÀ» ÆÄÀÏÀÌ ¸¶Á÷¸· ¼öÁ¤µÈ ½Ã°£ + ȤÀº Ŭ¶óÀ̾ðÆ®°¡ Á¢¼ÓÇÑ ½Ã°£¿¡ »ó´ëÀûÀ¸·Î ¼³Á¤ÇÒ ¼ö ÀÖ´Ù.

+ +

ÀÌ HTTP Çì´õµéÀº Ŭ¶óÀ̾ðÆ®¿¡°Ô ¹®¼­ÀÇ + À¯È¿¼º°ú Áö¼Ó¼ºÀ» ¾Ë·ÁÁØ´Ù. ÀÌ ½Ã°£ÀÌ ¾ÆÁ÷ Áö³ªÁö¾Ê¾Ò´Ù¸é, + ¹®¼­¸¦ ij½¬¿¡¼­ °¡Á®¿Íµµ µÈ´Ù. ¸¸±âÀÏÀÌ Áö³µ´Ù¸é ij½¬µÈ + °ÍÀ» "¸¸·áµÇ°í" À¯È¿ÇÏÁö ¾Ê´Ù°í °£ÁÖÇÏ¿©, ¼Ò½º¿¡¼­ ¹®¼­¸¦ + »õ·Î ¾ò¾î¿Í¾ß ÇÑ´Ù.

+ +

Header Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© max-age ¿ÜÀÇ ´Ù¸¥ + Cache-Control Áö½Ã¾î(RFC + 2616, 14.9 Àý Âü°í)¸¦ ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +
+

Áö½Ã¾îµé

+ +

ÁÖÁ¦

+
+
top
+
+

´Ù¸¥ ³»ºÎ ¹®¹ý

+

ExpiresDefault¿Í + ExpiresByType + Áö½Ã¾î¸¦ ´õ Àбâ ÁÁÀº Çü½ÄÀ¸·Î ±â¼úÇÒ ¼ö ÀÖ´Ù:

+ +

+ ExpiresDefault "<base> [plus] {<num> + <type>}*"
+ ExpiresByType type/encoding "<base> [plus] + {<num> <type>}*" +

+ +

<base>´Â ´ÙÀ½Áß ÇϳªÀÌ´Ù:

+ +
    +
  • access
    • + +
  • now ('access'¿Í °°À½)
    • + +
  • modification
    • +
+ +

plus Å°¿öµå´Â ¾ø¾îµµ µÈ´Ù. <num>Àº + [atoi()¿¡ »ç¿ëÇÒ ¼ö ÀÖ´Â] Á¤¼ö°ªÀÌ´Ù. + <type>Àº ´ÙÀ½Áß ÇϳªÀÌ´Ù:

+ +
    +
  • years
    • +
  • months
    • +
  • weeks
    • +
  • days
    • +
  • hours
    • +
  • minutes
    • +
  • seconds
    • +
+ +

¿¹¸¦ µé¾î, ´ÙÀ½ ¸ðµÎ´Â ¹®¼­°¡ ±âº»ÀûÀ¸·Î Á¢¼ÓµÈÁö 1´ÞÈÄ¿¡ + ¸¸±âµÈ´Ù°í ¼³Á¤ÇÑ´Ù:

+ +

+ ExpiresDefault "access plus 1 month"
+ ExpiresDefault "access plus 4 weeks"
+ ExpiresDefault "access plus 30 days" +

+ +

'<num> <type>' ±¸¹®À» ¹Ýº¹Çؼ­ »ç¿ëÇÏ¿© + ¸¸±â½Ã°£À» ÀÚ¼¼È÷ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù:

+ +

+ ExpiresByType text/html "access plus 1 month 15 + days 2 hours"
+ ExpiresByType image/gif "modification plus 5 hours 3 + minutes" +

+ +

¸¸¾à ¼öÁ¤½Ã°£(modification)À» ±âÁØÀ¸·Î ¸¸±â½Ã°£À» ¼³Á¤ÇÏ´Â + °æ¿ì ³»¿ëÀ» µð½ºÅ©¿¡ ÀÖ´Â ÆÄÀÏ¿¡¼­ °¡Á®¿ÀÁö ¾Ê´Â´Ù¸é Expires + Çì´õ¸¦ ºÙÀÌÁö ¾Ê´Â´Ù. ÀÌ °æ¿ì ³»¿ë¿¡ ¼öÁ¤½Ã°£ÀÌ + ¾ø±â ¶§¹®ÀÌ´Ù.

+
+
top
+

ExpiresActive Áö½Ã¾î

+ + + + + + + +
¼³¸í:Expires Çì´õ¸¦ »ý¼ºÇÑ´Ù
¹®¹ý:ExpiresActive On|Off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Extension
¸ðµâ:mod_expires
+

ÀÌ Áö½Ã¾î´Â ÇØ´ç ¿µ¿ª¿¡ ´ëÇØ (Áï, .htaccess + ÆÄÀÏ¿¡¼­ »ç¿ëÇÑ´Ù¸é ±× µð·ºÅ丮 ¾Æ·¡¿¡ ÀÖ´Â ¹®¼­µé¸¸ ÇØ´çµÈ´Ù.) + Expires¿Í Cache-Control Çì´õ¸¦ + »ý¼ºÇÒÁö À¯¹«¸¦ °áÁ¤ÇÑ´Ù. (.htaccess ÆÄÀÏ µîÀ¸·Î + ´õ ÇÏÀ§ ´Ü°è¿¡¼­ ¼­¹ö¼³Á¤À» º¯°æÇÏÁö¾Ê´Â ÇÑ) + OffÀ̸é ÇØ´ç ¿µ¿ª¿¡ ÀÖ´Â ¹®¼­¿¡ À̵é Çì´õ¸¦ + »ý¼ºÇÏÁö ¾Ê´Â´Ù. OnÀ̸é ExpiresByType°ú ExpiresDefault Áö½Ã¾î·Î + (ÇØ´ç Ç׸ñÀ» Âü°íÇ϶ó) ÁöÁ¤ÇÑ ±ÔÄ¢¿¡ µû¶ó ¼­ºñ½ºÇÏ·Á´Â + ¹®¼­¿¡ ÀÌ Çì´õµéÀ» »ý¼ºÇÑ´Ù.

+ +

ÀÌ Áö½Ã¾î°¡ Expires³ª Cache-Control + Çì´õ¸¦ º¸ÀåÇÏÁö´Â ¾Ê´Â´Ù. ±ÔÄ¢¿¡ ÇØ´çÇÏÁö ¾Ê´Ù¸é ¸¶Ä¡ ÀÌ + Áö½Ã¾î°¡ ¾ø´Â °Íó·³ Çì´õ¸¦ ¸¸µéÁö ¾Ê´Â´Ù.

+ +
+
top
+

ExpiresByType Áö½Ã¾î

+ + + + + + + +
¼³¸í:MIME typeÀ¸·Î Expires Çì´õ°ªÀ» ¼³Á¤ÇÑ´Ù
¹®¹ý:ExpiresByType MIME-type +<code>seconds
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Extension
¸ðµâ:mod_expires
+

ÀÌ Áö½Ã¾î´Â ƯÁ¤ Á¾·ùÀÇ (¿¡¸¦ µé¾î, + text/html) ¹®¼­¿¡ ´ëÇÑ Expires + Çì´õ°ª°ú Cache-Control Çì´õÀÇ max-age + Áö½Ã¾î°ªÀ» Á¤ÀÇÇÑ´Ù. µÎ¹ø° ¾Æ±Ô¸ÕÆ®´Â ¸¸±â½Ã°£À» °áÁ¤ÇÒ¶§ + ±âÁØ ½Ã°£¿¡ ´õÇÒ ÃÊ´ÜÀ§ °ªÀ» ÁöÁ¤ÇÑ´Ù. Cache-Control: + max-age´Â ¸¸±â½Ã°£¿¡¼­ ¿äûÇÑ ½Ã°£À» »©¼­ °è»êÇÏ°í, + °á°ú´Â ÃÊ´ÜÀ§·Î Ç¥½ÃÇÑ´Ù.

+ +

±âÁØ ½Ã°£Àº ÆÄÀÏÀÇ ÃÖ±Ù ¼öÁ¤½Ã°£ ȤÀº Ŭ¶óÀ̾ðÆ®°¡ ¹®¼­¿¡ + Á¢±ÙÇÑ ½Ã°£ÀÌ´Ù. À̶² °ÍÀ» »ç¿ëÇÒÁö´Â + <code> Çʵå·Î °áÁ¤ÇØ¾ß ÇÑ´Ù. + MÀº ±âÁØ ½Ã°£À¸·Î ÆÄÀÏÀÇ ÃÖ±Ù ¼öÁ¤½Ã°£À» + »ç¿ëÇÏ°í, A´Â Ŭ¶óÀ̾ðÆ®ÀÇ Á¢±Ù ½Ã°£À» »ç¿ëÇÑ´Ù.

+ +

Â÷ÀÌ´Â ¹Ì¹¦ÇÏ´Ù. MÀ» »ç¿ëÇϸé ij½¬¿¡ ÀÖ´Â + ¸ðµç º¹»çº»ÀÌ °°Àº ½Ã°£¿¡ ¸¸·áµÈ´Ù. ±×·¡¼­ Ç×»ó °°Àº URL·Î + ã¾Æº¼ ¼ö ÀÖ´Â ÁÖ°£ÀÏÁ¤ °°Àº ¿ëµµ¿¡ ÁÁ´Ù. A¸¦ + »ç¿ëÇÏ¸é º¹»çº»ÀÇ ¸¸±â½Ã°£ÀÌ °¢°¢ ´Ù¸£´Ù. ÀÌ´Â ÀÚÁÖ ¼öÁ¤µÇÁö¾Ê´Â + ±×¸²ÆÄÀÏ¿¡, ƯÈ÷ ¿©·¯ ¹®¼­¿¡¼­ °°Àº ±×¸²À» ÂüÁ¶ÇÒ¶§ (¿¹¸¦ + µé¾î, À̹ÌÁö´Â »ó´ëÀûÀ¸·Î ªÀº ±â°£µ¿¾È ¹Ýº¹Çؼ­ Á¢±ÙµÈ´Ù), + À¯¿ëÇÏ´Ù.

+ +

¿¹Á¦:

+ # ¸¸±âÇì´õ¸¦ »ç¿ëÇÑ´Ù
+ ExpiresActive On
+ # Ŭ¶óÀ̾ðÆ® ij½¬ÀÇ GIF ±×¸²Àº ÇÑ ´ÞÈÄ¿¡ ¸¸±âÇÑ´Ù
+ ExpiresByType image/gif A2592000
+ # HTML ¹®¼­´Â º¯°æÈÄ ÀÏÁÖÀÏ°£ À¯È¿ÇÏ´Ù + ExpiresByType text/html M604800 +

+ +

ÀÌ Áö½Ã¾î´Â ExpiresActive OnÀ» »ç¿ëÇÒ¶§¸¸ + À¯È¿ÇÔÀ» ÁÖÀÇÇ϶ó. ExpiresDefault Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© ƯÁ¤ MIME type¿¡ ´ëÇؼ­¸¸ ¸¸±â½Ã°£À» + ¼³Á¤ÇÒ ¼ö ÀÖ´Ù.

+ +

¾Õ¿¡¼­ ¼³¸íÇÑ ´Ù¸¥ ¹®¹ýÀ» »ç¿ëÇÏ¿© + ¸¸±â½Ã°£À» °è»êÇÒ ¼öµµ ÀÖ´Ù.

+ +
+
top
+

ExpiresDefault Áö½Ã¾î

+ + + + + + + +
¼³¸í:¸¸±â½Ã°£À» °è»êÇÏ´Â ±âº» ¾Ë°í¸®Áò
¹®¹ý:ExpiresDefault <code>seconds
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Extension
¸ðµâ:mod_expires
+

ÀÌ Áö½Ã¾î´Â ÇØ´ç ¿µ¿ª¿¡ ÀÖ´Â ¸ðµç ¹®¼­ÀÇ ¸¸±â½Ã°£À» + °è»êÇÏ´Â ±âº» ¾Ë°í¸®ÁòÀ» ÁöÁ¤ÇÑ´Ù. ExpiresByType Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© Á¾·ùº°·Î ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ¾Æ±Ô¸ÕÆ® ¹®¹ý¿¡ ´ëÇÑ + ÀÚ¼¼ÇÑ ¼³¸íÀº ±× Áö½Ã¾î¿Í ´Ù¸¥ ¹®¹ýÀ» + Âü°íÇ϶ó.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_ext_filter.html b/docs/manual/mod/mod_ext_filter.html new file mode 100644 index 00000000..aacf8a65 --- /dev/null +++ b/docs/manual/mod/mod_ext_filter.html @@ -0,0 +1,11 @@ +URI: mod_ext_filter.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_ext_filter.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_ext_filter.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_ext_filter.html.en b/docs/manual/mod/mod_ext_filter.html.en new file mode 100644 index 00000000..a0f2e8a2 --- /dev/null +++ b/docs/manual/mod/mod_ext_filter.html.en @@ -0,0 +1,376 @@ + + + +mod_ext_filter - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_ext_filter

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Pass the response body through an external program before +delivery to the client
Status:Extension
Module Identifier:ext_filter_module
Source File:mod_ext_filter.c
+

Summary

+ +

mod_ext_filter presents a simple and familiar + programming model for filters. With + this module, a program which reads from stdin and writes to stdout + (i.e., a Unix-style filter command) can be a filter for + Apache. This filtering mechanism is much slower than using a + filter which is specially written for the Apache API and runs + inside of the Apache server process, but it does have the + following benefits:

+ +
    +
  • the programming model is much simpler
    • + +
  • any programming/scripting language can be used, provided + that it allows the program to read from standard input and + write to standard output
    • + +
  • existing programs can be used unmodified as Apache + filters
    • +
+ +

Even when the performance characteristics are not suitable + for production use, mod_ext_filter can be used as + a prototype environment for filters.

+ +
+

Directives

+ +

Topics

+

See also

+
+
top
+
+

Examples

+ +

Generating HTML from some other type of response

+

+ # mod_ext_filter directive to define a filter
+ # to HTML-ize text/c files using the external
+ # program /usr/bin/enscript, with the type of
+ # the result set to text/html
+ ExtFilterDefine c-to-html mode=output \
+ + intype=text/c outtype=text/html \
+ cmd="/usr/bin/enscript --color -W html -Ec -o - -"
+ +
+ <Directory "/export/home/trawick/apacheinst/htdocs/c">
+ + # core directive to cause the new filter to
+ # be run on output
+ SetOutputFilter c-to-html
+
+ # mod_mime directive to set the type of .c
+ # files to text/c
+ AddType text/c .c
+
+ # mod_ext_filter directive to set the debug
+ # level just high enough to see a log message
+ # per request showing the configuration in force
+ ExtFilterOptions DebugLevel=1
+ + </Directory> +

+ + +

Implementing a content encoding filter

+

Note: this gzip example is just for the purposes of illustration. + Please refer to mod_deflate for a practical + implementation.

+ +

+ # mod_ext_filter directive to define the external filter
+ ExtFilterDefine gzip mode=output cmd=/bin/gzip
+
+ <Location /gzipped>
+ + # core directive to cause the gzip filter to be
+ # run on output
+ SetOutputFilter gzip
+
+ # mod_header directive to add
+ # "Content-Encoding: gzip" header field
+ Header set Content-Encoding gzip
+ + </Location> +

+ + +

Slowing down the server

+

+ # mod_ext_filter directive to define a filter
+ # which runs everything through cat; cat doesn't
+ # modify anything; it just introduces extra pathlength
+ # and consumes more resources
+ ExtFilterDefine slowdown mode=output cmd=/bin/cat \
+ + preservescontentlength
+ +
+ <Location />
+ + # core directive to cause the slowdown filter to
+ # be run several times on output
+ #
+ SetOutputFilter slowdown;slowdown;slowdown
+ + </Location> +

+ + +

Using sed to replace text in the response

+

+ # mod_ext_filter directive to define a filter which
+ # replaces text in the response
+ #
+ ExtFilterDefine fixtext mode=output intype=text/html \
+ + cmd="/bin/sed s/verdana/arial/g"
+ +
+ <Location />
+ + # core directive to cause the fixtext filter to
+ # be run on output
+ SetOutputFilter fixtext
+ + </Location> +

+ + +

Tracing another filter

+

+ # Trace the data read and written by mod_deflate
+ # for a particular client (IP 192.168.1.31)
+ # experiencing compression problems.
+ # This filter will trace what goes into mod_deflate.
+ ExtFilterDefine tracebefore \
+ + cmd="/bin/tracefilter.pl /tmp/tracebefore" \
+ EnableEnv=trace_this_client
+ +
+ # This filter will trace what goes after mod_deflate.
+ # Note that without the ftype parameter, the default
+ # filter type of AP_FTYPE_RESOURCE would cause the
+ # filter to be placed *before* mod_deflate in the filter
+ # chain. Giving it a numeric value slightly higher than
+ # AP_FTYPE_CONTENT_SET will ensure that it is placed
+ # after mod_deflate.
+ ExtFilterDefine traceafter \
+ + cmd="/bin/tracefilter.pl /tmp/traceafter" \
+ EnableEnv=trace_this_client ftype=21
+ +
+ <Directory /usr/local/docs>
+ + SetEnvIf Remote_Addr 192.168.1.31 trace_this_client
+ SetOutputFilter tracebefore;deflate;traceafter
+ + </Directory> +

+ +

Here is the filter which traces the data:

+ #!/usr/local/bin/perl -w
+ use strict;
+
+ open(SAVE, ">$ARGV[0]")
+ + or die "can't open $ARGV[0]: $?";
+ +
+ while (<STDIN>) {
+ + print SAVE $_;
+ print $_;
+ + }
+
+ close(SAVE); +

+ +
+
top
+

ExtFilterDefine Directive

+ + + + + + +
Description:Define an external filter
Syntax:ExtFilterDefine filtername parameters
Context:server config
Status:Extension
Module:mod_ext_filter
+

The ExtFilterDefine directive defines the + characteristics of an external filter, including the program to + run and its arguments.

+ +

filtername specifies the name of the filter being + defined. This name can then be used in SetOutputFilter + directives. It must be unique among all registered filters. + At the present time, no error is reported by the + register-filter API, so a problem with duplicate names isn't + reported to the user.

+ +

Subsequent parameters can appear in any order and define the + external command to run and certain other characteristics. The + only required parameter is cmd=. These parameters + are:

+ +
+
cmd=cmdline
+ +
The cmd= keyword allows you to specify the + external command to run. If there are arguments after the + program name, the command line should be surrounded in + quotation marks (e.g., cmd="/bin/mypgm + arg1 arg2".) Normal shell quoting is + not necessary since the program is run directly, bypassing the shell. + Program arguments are blank-delimited. A backslash can be used to + escape blanks which should be part of a program argument. Any + backslashes which are part of the argument must be escaped with + backslash themselves. In addition to the standard CGI environment + variables, DOCUMENT_URI, DOCUMENT_PATH_INFO, and + QUERY_STRING_UNESCAPED will also be set for the program.
+ +
mode=mode
+ +
Use mode=output (the default) for filters which + process the response. Use mode=input for filters + which process the request. mode=input is available + in Apache 2.1 and later.
+ +
intype=imt
+ +
This parameter specifies the internet media type (i.e., + MIME type) of documents which should be filtered. By default, + all documents are filtered. If intype= is + specified, the filter will be disabled for documents of other + types.
+ +
outtype=imt
+ +
This parameter specifies the internet media type (i.e., + MIME type) of filtered documents. It is useful when the + filter changes the internet media type as part of the + filtering operation. By default, the internet media type is + unchanged.
+ +
PreservesContentLength
+ +
The PreservesContentLength keyword specifies + that the filter preserves the content length. This is not the + default, as most filters change the content length. In the + event that the filter doesn't modify the length, this keyword + should be specified.
+ +
ftype=filtertype
+ +
This parameter specifies the numeric value for filter type + that the filter should be registered as. The default value, + AP_FTYPE_RESOURCE, is sufficient in most cases. If the filter + needs to operate at a different point in the filter chain than + resource filters, then this parameter will be necessary. See + the AP_FTYPE_foo definitions in util_filter.h for appropriate + values.
+ +
disableenv=env
+ +
This parameter specifies the name of an environment variable + which, if set, will disable the filter.
+ +
enableenv=env
+ +
This parameter specifies the name of an environment variable + which must be set, or the filter will be disabled.
+
+ +
+
top
+

ExtFilterOptions Directive

+ + + + + + + +
Description:Configure mod_ext_filter options
Syntax:ExtFilterOptions option [option] ...
Default:ExtFilterOptions DebugLevel=0 NoLogStderr
Context:directory
Status:Extension
Module:mod_ext_filter
+

The ExtFilterOptions directive specifies + special processing options for mod_ext_filter. + Option can be one of

+ +
+
DebugLevel=n
+ +
+ The DebugLevel keyword allows you to specify + the level of debug messages generated by + mod_ext_filter. By default, no debug messages + are generated. This is equivalent to + DebugLevel=0. With higher numbers, more debug + messages are generated, and server performance will be + degraded. The actual meanings of the numeric values are + described with the definitions of the DBGLVL_ constants + near the beginning of mod_ext_filter.c. + +

Note: The core directive LogLevel should be used to cause debug messages to + be stored in the Apache error log.

+
+ +
LogStderr | NoLogStderr
+ +
The LogStderr keyword specifies that + messages written to standard error by the external filter + program will be saved in the Apache error log. + NoLogStderr disables this feature.
+
+ +

Example

+ ExtFilterOptions LogStderr DebugLevel=0 +

+ +

Messages written to the filter's standard error will be stored + in the Apache error log. No debug messages will be generated by + mod_ext_filter.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_ext_filter.html.ja.euc-jp b/docs/manual/mod/mod_ext_filter.html.ja.euc-jp new file mode 100644 index 00000000..b2d231d7 --- /dev/null +++ b/docs/manual/mod/mod_ext_filter.html.ja.euc-jp @@ -0,0 +1,369 @@ + + + +mod_ext_filter - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_ext_filter

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥ì¥¹¥Ý¥ó¥¹¤Î¥Ü¥Ç¥£¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ëÁ°¤Ë³°Éô¥×¥í¥°¥é¥à¤Ç½èÍý¤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:ext_filter_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_ext_filter.c
+

³µÍ×

+ +

mod_ext_filter ¤Ç¤Ï ¥Õ¥£¥ë¥¿ + ¤Î´·¤ì¿Æ¤·¤ó¤Àñ½ã¤Ê¥×¥í¥°¥é¥ß¥ó¥°¥â¥Ç¥ë¤¬Ä󶡤µ¤ì¤Þ¤¹¡£¤³¤Î¥â¥¸¥å¡¼¥ë¤ò + »È¤¨¤Ð¡¢É¸½àÆþÎϤ«¤éÆɤ߹þ¤ó¤Ç¡¢É¸½à½ÐÎϤ˽ñ¤­½Ð¤¹¥×¥í¥°¥é¥à + (¤¹¤Ê¤ï¤Á Unix ·Á¼°¤Î¥Õ¥£¥ë¥¿¥³¥Þ¥ó¥É) ¤ò Apache ¤Î¥Õ¥£¥ë¥¿¤Ë¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£¤³¤Î¥Õ¥£¥ë¥¿¤Îµ¡¹½¤Ï¡¢Apache API ¸þ¤±¤Ë½ñ¤«¤ì¤¿ Apache + ¥µ¡¼¥Ð¥×¥í¥»¥¹Æâ¤Ç¼Â¹Ô¤µ¤ì¤ëÀìÍѤΥե£¥ë¥¿¤è¤ê¤â¤º¤Ã¤ÈÃÙ¤¤¤Ç¤¹¤¬¡¢ + °Ê²¼¤Î¤è¤¦¤ÊÍøÅÀ¤â¤¢¤ê¤Þ¤¹¡£

+ +
    +
  • ¤º¤Ã¤È¥·¥ó¥×¥ë¤Ê¥×¥í¥°¥é¥ß¥ó¥°¥â¥Ç¥ë
    • + +
  • ¥×¥í¥°¥é¥à¤¬É¸½àÆþÎϤ«¤éÆɤó¤Çɸ½à½ÐÎϤ˽ñ¤¯¤â¤Î¤Ç¤¢¤ë¸Â¤ê¡¢ + ¤É¤ó¤Ê¥×¥í¥°¥é¥à¸À¸ì¤ä¥¹¥¯¥ê¥×¥È¸À¸ì¤Ç¤â»È¤¦¤³¤È¤¬¤Ç¤­¤ë
    • + +
  • ´û¸¤Î¥×¥í¥°¥é¥à¤òÊѹ¹¤¹¤ë¤³¤È¤Ê¤¯ Apache ¤Î¥Õ¥£¥ë¥¿¤È¤·¤Æ + »È¤¦¤³¤È¤¬¤Ç¤­¤ë
    • +
+ +

À­Ç½¤ÎÌäÂê¤Ë¤è¤ê¼Â±¿ÍѤËŬ¤µ¤Ê¤¤¤È¤·¤Æ¤â¡¢¥Õ¥£¥ë¥¿¤Î¥×¥í¥È¥¿¥¤¥×ÍѤΠ+ ´Ä¶­¤È¤·¤Æ¤Ï mod_ext_filter ¤Ï»È¤¨¤Þ¤¹¡£

+ +
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

¥È¥Ô¥Ã¥¯

+

»²¾È

+
+
top
+
+

Îã

+ +

¾¤Î¥¿¥¤¥×¤Î¥ì¥¹¥Ý¥ó¥¹¤«¤é HTML ¤òÀ¸À®¤¹¤ë

+

+ # mod_ext_filter directive to define a filter
+ # to HTML-ize text/c files using the external
+ # program /usr/bin/enscript, with the type of
+ # the result set to text/html
+ ExtFilterDefine c-to-html mode=output \
+ + intype=text/c outtype=text/html \
+ cmd="/usr/bin/enscript --color -W html -Ec -o - -"
+ +
+ <Directory "/export/home/trawick/apacheinst/htdocs/c">
+ + # core directive to cause the new filter to
+ # be run on output
+ SetOutputFilter c-to-html
+
+ # mod_mime directive to set the type of .c
+ # files to text/c
+ AddType text/c .c
+
+ # mod_ext_filter directive to set the debug
+ # level just high enough to see a log message
+ # per request showing the configuration in force
+ ExtFilterOptions DebugLevel=1
+ + </Directory> +

+ + +

¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Î¥Õ¥£¥ë¥¿¤ò¼ÂÁõ¤¹¤ë

+

Ãí: ¤³¤Î gzip ¤ÎÎã¤Ï¥Ç¥âÍѤǤ¹¡£¼ÂÍÑŪ¤Ê¼ÂÁõ¤Ï + mod_deflate ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ # mod_ext_filter directive to define the external filter
+ ExtFilterDefine gzip mode=output cmd=/bin/gzip
+
+ <Location /gzipped>
+ + # core directive to cause the gzip filter to be
+ # run on output
+ SetOutputFilter gzip
+
+ # mod_header directive to add
+ # "Content-Encoding: gzip" header field
+ Header set Content-Encoding gzip
+ + </Location> +

+ + +

¥µ¡¼¥Ð¤òÃÙ¤¯¤¹¤ë

+

+ # mod_ext_filter directive to define a filter
+ # which runs everything through cat; cat doesn't
+ # modify anything; it just introduces extra pathlength
+ # and consumes more resources
+ ExtFilterDefine slowdown mode=output cmd=/bin/cat \
+ + preservescontentlength
+ +
+ <Location />
+ + # core directive to cause the slowdown filter to
+ # be run several times on output
+ #
+ SetOutputFilter slowdown;slowdown;slowdown
+ + </Location> +

+ + +

sed ¤ò»È¤Ã¤Æ±þÅúÃæ¤Î¥Æ¥­¥¹¥È¤òÃÖ´¹¤¹¤ë

+

+ # mod_ext_filter directive to define a filter which
+ # replaces text in the response
+ #
+ ExtFilterDefine fixtext mode=output intype=text/html \
+ + cmd="/bin/sed s/verdana/arial/g"
+ +
+ <Location />
+ + # core directive to cause the fixtext filter to
+ # be run on output
+ SetOutputFilter fixtext
+ + </Location> +

+ + +

Ê̤Υե£¥ë¥¿¤Î¥È¥ì¡¼¥¹

+

+ # Trace the data read and written by mod_deflate
+ # for a particular client (IP 192.168.1.31)
+ # experiencing compression problems.
+ # This filter will trace what goes into mod_deflate.
+ ExtFilterDefine tracebefore \
+ + cmd="/bin/tracefilter.pl /tmp/tracebefore" \
+ EnableEnv=trace_this_client
+ +
+ # This filter will trace what goes after mod_deflate.
+ # Note that without the ftype parameter, the default
+ # filter type of AP_FTYPE_RESOURCE would cause the
+ # filter to be placed *before* mod_deflate in the filter
+ # chain. Giving it a numeric value slightly higher than
+ # AP_FTYPE_CONTENT_SET will ensure that it is placed
+ # after mod_deflate.
+ ExtFilterDefine traceafter \
+ + cmd="/bin/tracefilter.pl /tmp/traceafter" \
+ EnableEnv=trace_this_client ftype=21
+ +
+ <Directory /usr/local/docs>
+ + SetEnvIf Remote_Addr 192.168.1.31 trace_this_client
+ SetOutputFilter tracebefore;deflate;traceafter
+ + </Directory> +

+ +

¥Ç¡¼¥¿¤ò¥È¥ì¡¼¥¹¤¹¤ë¥Õ¥£¥ë¥¿:

+ #!/usr/local/bin/perl -w
+ use strict;
+
+ open(SAVE, ">$ARGV[0]")
+ + or die "can't open $ARGV[0]: $?";
+ +
+ while (<STDIN>) {
+ + print SAVE $_;
+ print $_;
+ + }
+
+ close(SAVE); +

+ +
+
top
+

ExtFilterDefine ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:³°Éô¥Õ¥£¥ë¥¿¤òÄêµÁ
¹½Ê¸:ExtFilterDefine filtername parameters
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_ext_filter
+

ExtFilterDefine ¤Ï¡¢¼Â¹Ô¤¹¤ë¥×¥í¥°¥é¥à¤ä + °ú¿ô¤Ê¤É¡¢³°Éô¥Õ¥£¥ë¥¿¤ÎÆÃÀ­¤òÄêµÁ¤·¤Þ¤¹¡£

+ +

filtername ¤ÏÄêµÁ¤¹¤ë¥Õ¥£¥ë¥¿¤Î̾Á°¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤³¤Î̾Á°¤Ï¸å¤Ç SetOutputFilter + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄê¤Ç¤­¤Þ¤¹¡£Ì¾Á°¤ÏÅÐÏ¿¤µ¤ì¤ë¤¹¤Ù¤Æ¤Î¥Õ¥£¥ë¥¿¤Ç + °ì°Õ¤Ç¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£¸½»þÅÀ¤Ç¤Ï¡¢¥Õ¥£¥ë¥¿¤ÎÅÐÏ¿ API ¤«¤é¤Ï + ¥¨¥é¡¼¤ÏÊó¹ð¤µ¤ì¤Þ¤»¤ó¡£¤Ç¤¹¤«¤é¡¢½ÅÊ£¤¹¤ë̾Á°¤ò»È¤Ã¤Æ¤·¤Þ¤Ã¤¿¤È¤­¤Ç¤â + ¥æ¡¼¥¶¤Ë¤Ï¤½¤Î¤³¤È¤ÏÊó¹ð¤µ¤ì¤Þ¤»¤ó¡£

+ +

³¤¯¥Ñ¥é¥á¡¼¥¿¤Î½çÈ֤ϴط¸Ìµ¤¯¡¢¤½¤ì¤é¤Ï¼Â¹Ô¤¹¤ë³°Éô¥³¥Þ¥ó¥É¤È¡¢ + ¾¤ÎÆÃÀ­¤òÄêµÁ¤·¤Þ¤¹¡£cmd= ¤À¤±¤¬É¬¿Ü¤Î¥Ñ¥é¥á¡¼¥¿¤Ç¤¹¡£ + »ØÄê²Äǽ¤Ê¥Ñ¥é¥á¡¼¥¿¤Ï:

+ +
+
cmd=cmdline
+ +
cmd= ¥­¡¼¥ï¡¼¥É¤Ï¼Â¹Ô¤¹¤ë³°Éô¥³¥Þ¥ó¥É¤ò»ØÄꤷ¤Þ¤¹¡£ + ¥×¥í¥°¥é¥à̾¤Î¸å¤Ë°ú¿ô¤¬¤¢¤ë¾ì¹ç¤Ï¡¢¥³¥Þ¥ó¥É¹Ô¤Ï°úÍÑÉä¤Ç°Ï¤à + ɬÍפ¬¤¢¤ê¤Þ¤¹ (Î㤨¤Ð¡¢cmd="/bin/mypgm + arg1 arg2" ¤Î¤è¤¦¤Ë)¡£¥×¥í¥°¥é¥à¤Ï + ¥·¥§¥ë·Ðͳ¤Ç¤Ê¤¯¡¢Ä¾Àܼ¹Ԥµ¤ì¤Þ¤¹¤Î¤Ç¡¢Ä̾ï¤Î¥·¥§¥ëÍѤΠ+ ¥¨¥¹¥±¡¼¥×¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£¥×¥í¥°¥é¥à¤Î°ú¿ô¤Ï¶õÇò¤Ç¶èÀÚ¤é¤ì¤Þ¤¹¡£ + ¥×¥í¥°¥é¥à¤Î°ú¿ô¤Î°ìÉô¤È¤Ê¤ëɬÍפΤ¢¤ë¶õÇò¤Ï¥Ð¥Ã¥¯¥¹¥Ú¡¼¥¹¤Ç¥¨¥¹¥±¡¼¥× + ¤Ç¤­¤Þ¤¹¡£°ú¿ô¤Î°ìÉô¤Ë¤Ê¤ë¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Ï¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Ç + ¥¨¥¹¥±¡¼¥×¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£É¸½à¤Î CGI ´Ä¶­ÊÑ¿ô¤Ë²Ã¤¨¤Æ¡¢ + ´Ä¶­ÊÑ¿ô DOCUMENT_URI, DOCUMENT_PATH_INFO, and + QUERY_STRING_UNESCAPED ¤¬¥×¥í¥°¥é¥à¤Î¤¿¤á¤ËÀßÄꤵ¤ì¤Þ¤¹¡£
+ +
mode=mode
+ +
±þÅú¤ò½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤Ë¤Ï mode=output (¥Ç¥Õ¥©¥ë¥È) + ¤ò»È¤¤¤Þ¤¹¡£¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤Ë¤Ï mode=input + ¤ò»È¤¤¤Þ¤¹¡£mode=input ¤Ï Apache 2.1 ¤«¤é¤Î¿·¤·¤¤µ¡Ç½¤Ç¤¹¡£
+ +
intype=imt
+ +
¤³¤Î¥Ñ¥é¥á¡¼¥¿¤Ï¥Õ¥£¥ë¥¿¤µ¤ì¤ë¤Ù¤­¥É¥­¥å¥á¥ó¥È¤Î + ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥á¥Ç¥£¥¢¥¿¥¤¥× (¤¹¤Ê¤ï¤Á¡¢MIME ¥¿¥¤¥×) ¤ò + »ØÄꤷ¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¤¹¤Ù¤Æ¤Î¥É¥­¥å¥á¥ó¥È¤¬¥Õ¥£¥ë¥¿¤µ¤ì¤Þ¤¹¡£ + intype= ¤¬»ØÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢¥Õ¥£¥ë¥¿¤Ï»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤ + ¥É¥­¥å¥á¥ó¥È¤Ë¤ÏŬÍѤµ¤ì¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£
+ +
outtype=imt
+ +
¤³¤Î¥Ñ¥é¥á¡¼¥¿¤Ï¥Õ¥£¥ë¥¿¤µ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤Î + ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥á¥Ç¥£¥¢¥¿¥¤¥× (¤¹¤Ê¤ï¤Á¡¢MIME ¥¿¥¤¥×) ¤ò + »ØÄꤷ¤Þ¤¹¡£¥Õ¥£¥ë¥¿Æ°ºî¤Ë¤È¤â¤Ê¤Ã¤Æ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥á¥Ç¥£¥¢¥¿¥¤¥×¤¬ + ÊѤï¤ë¾ì¹ç¤ËÍ­ÍѤǤ¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥á¥Ç¥£¥¢¥¿¥¤¥×¤Ï + Êѹ¹¤µ¤ì¤Þ¤»¤ó¡£
+ +
PreservesContentLength
+ +
PreservesContentLength ¥­¡¼¥ï¡¼¥É¤Ï¥Õ¥£¥ë¥¿¤¬ + content length (ÌõÃí: ¥³¥ó¥Æ¥ó¥È¤ÎŤµ) + ¤òÊѹ¹¤·¤Ê¤¤¤È¤¤¤¦¤³¤È¤ò»ØÄꤷ¤Þ¤¹¡£¤Û¤È¤ó¤É¤Î¥Õ¥£¥ë¥¿¤Ï + content length ¤òÊѹ¹¤¹¤ë¤¿¤á¡¢¤³¤ì¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¥Õ¥£¥ë¥¿¤¬Ä¹¤µ¤òÊѤ¨¤Ê¤¤¤È¤­¤Ï¡¢¤³¤Î¥­¡¼¥ï¡¼¥É¤ò»ØÄꤹ¤ë¤È + ¤è¤¤¤Ç¤·¤ç¤¦¡£
+ +
ftype=filtertype
+ +
¤³¤Î¥Ñ¥é¥á¡¼¥¿¤Ï¥Õ¥£¥ë¥¿¤¬ÅÐÏ¿¤µ¤ì¤ë¤Ù¤­¥Õ¥£¥ë¥¿¥¿¥¤¥×¤Î + ¿ôÃͤò»ØÄꤷ¤Þ¤¹¡£¤Û¤È¤ó¤É¤Î¾ì¹ç¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Î AP_FTYPE_RESOURCE ¤Ç + ½½Ê¬¤Ç¤¹¡£¥Õ¥£¥ë¥¿¤¬¥Õ¥£¥ë¥¿¥Á¥§¡¼¥ó¤ÎÊ̤ξì½ê¤ÇÆ°ºî¤¹¤ëɬÍפ¬¤¢¤ë + ¾ì¹ç¤Ï¡¢¤³¤Î¥Ñ¥é¥á¡¼¥¿¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£»ØÄê²Äǽ¤ÊÃÍ¤Ï + util_filter.h ¤Î AP_FTYPE_foo ÄêµÁ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
+ +
disableenv=env
+ +
ÀßÄꤵ¤ì¤Æ¤¤¤¿¾ì¹ç¤Ë¥Õ¥£¥ë¥¿¤ò̵¸ú¤Ë¤¹¤ë¤¿¤á¤Î´Ä¶­ÊÑ¿ô¤ò + »ØÄꤷ¤Þ¤¹¡£
+ +
enableenv=env
+ +
¤³¤Î¥Ñ¥é¥á¡¼¥¿¤Ï¥Õ¥£¥ë¥¿¤¬Í­¸ú¤Ë¤Ê¤ë¤¿¤á¤ËÀßÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð + ¤Ê¤é¤Ê¤¤´Ä¶­ÊÑ¿ô¤ò»ØÄꤷ¤Þ¤¹¡£
+
+ +
+
top
+

ExtFilterOptions ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:mod_ext_filter ¤Î¥ª¥×¥·¥ç¥ó¤òÀßÄê
¹½Ê¸:ExtFilterOptions option [option] ...
¥Ç¥Õ¥©¥ë¥È:ExtFilterOptions DebugLevel=0 NoLogStderr
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_ext_filter
+

ExtFilterOptions ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + mod_ext_filter ¤ÎÆÃÊ̤ʽèÍýÍѤΥª¥×¥·¥ç¥ó¤ò + »ØÄꤷ¤Þ¤¹¡£Option ¤Ë¤Ï°Ê²¼¤Î¤É¤ì¤«¤ò»ØÄꤷ¤Þ¤¹¡£

+ +
+
DebugLevel=n
+ +
+ DebugLevel ¤Ç mod_ext_filter + ¤ÎÀ¸À®¤¹¤ë¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸¤Î¥ì¥Ù¥ë¤òÀßÄê¤Ç¤­¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸¤ÏÀ¸À®¤µ¤ì¤Þ¤»¤ó¡£ + ¤³¤ì¤Ï DebugLevel=0 ¤ÈÀßÄꤹ¤ë¤Î¤ÈƱ¤¸¤Ç¤¹¡£ + ¿ô»ú¤¬Â礭¤¯¤Ê¤ì¤Ð¤Ê¤ë¤Û¤É¡¢¤è¤ê¿¤¯¤Î¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸¤¬ + À¸À®¤µ¤ì¡¢¥µ¡¼¥Ð¤ÎÀ­Ç½¤ÏÍî¤Á¤Þ¤¹¡£¿ôÃͤμºݤΰÕÌ£¤Ï + mod_ext_filter.c ¤ÎÀèƬ¶á¤¯¤Î DBGLVL_ Äê¿ô¤Î + ÄêµÁ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + +

Ãí: ¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸¤ò Apache ¤Î¥¨¥é¡¼¥í¥°¤Ë + Êݸ¤¹¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢core ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + LogLevel + ¤ò»È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£

+
+ +
LogStderr | NoLogStderr
+ +
LogStderr ¥­¡¼¥ï¡¼¥É¤Ï³°Éô¥Õ¥£¥ë¥¿¥×¥í¥°¥é¥à¤Ë¤è¤ê + ɸ½à¥¨¥é¡¼ (ÌõÃí: stderr) ¤Ë½ñ¤«¤ì¤¿¥á¥Ã¥»¡¼¥¸¤ò + Apache ¤Î¥¨¥é¡¼¥í¥°¤ËÊݸ¤¹¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£NoLogStderr ¤Ï + µÕ¤ËÊݸ¤·¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£
+
+ +

Îã

+ ExtFilterOptions LogStderr DebugLevel=0 +

+ +

¤³¤ÎÎã¤Ç¤Ï¡¢¥Õ¥£¥ë¥¿¤Îɸ½à½ÐÎϤ˽ñ¤«¤ì¤¿¥á¥Ã¥»¡¼¥¸¤Ï + Apache ¤Î¥¨¥é¡¼¥í¥°¤ËÊݸ¤µ¤ì¤Þ¤¹¡£mod_ext_filter ¤«¤é¤Ï + ¥Ç¥Ð¥Ã¥°¥á¥Ã¥»¡¼¥¸¤ÏÀ¸À®¤µ¤ì¤Þ¤»¤ó¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_ext_filter.html.ko.euc-kr b/docs/manual/mod/mod_ext_filter.html.ko.euc-kr new file mode 100644 index 00000000..8bcd83fb --- /dev/null +++ b/docs/manual/mod/mod_ext_filter.html.ko.euc-kr @@ -0,0 +1,354 @@ + + + +mod_ext_filter - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_ext_filter

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:ÀÀ´ä ³»¿ëÀ» ¿ÜºÎ ÇÁ·Î±×·¥À¸·Î ó¸®ÇÑ ÈÄ Å¬¶óÀ̾ðÆ®·Î +º¸³½´Ù
»óÅÂ:Extension
¸ðµâ¸í:ext_filter_module
¼Ò½ºÆÄÀÏ:mod_ext_filter.c
+

¿ä¾à

+ +

mod_ext_filter¸¦ »ç¿ëÇÏ¸é °£´ÜÇÏ°í Àͼ÷ÇÑ + ¹æ¹ýÀ¸·Î ÇÊÅ͸¦ ¸¸µé ¼ö ÀÖ´Ù. + Ç¥ÁØÀԷ¿¡¼­ Àаí Ç¥ÁØÃâ·Â¿¡ ¾²´Â ÇÁ·Î±×·¥(Áï, À¯´Ð½º½Ä + ÇÊÅÍ ¸í·É¾î)À» ¾ÆÆÄÄ¡ ÇÊÅÍ·Î »ç¿ëÇÒ ¼ö ÀÖ´Ù. ÀÌ·± ÇÊÅÍ´Â + ¾ÆÆÄÄ¡ API·Î ¾²¿©Áö°í ¾ÆÆÄÄ¡ ¼­¹ö ÇÁ·Î¼¼½º ¾È¿¡¼­ ½ÇÇàµÇ´Â + ÇÊÅÍ¿¡ ºñÇØ ¸Å¿ì ´À¸®Áö¸¸, ´ÙÀ½°ú °°Àº ÀåÁ¡ÀÌ ÀÖ´Ù:

+ +
    +
  • ÇÁ·Î±×·¡¹Ö ¸ðµ¨ÀÌ ¸Å¿ì °£´ÜÇÏ´Ù
    • + +
  • ÇÁ·Î±×·¥ÀÌ Ç¥ÁØÀԷ¿¡¼­ Àаí Ç¥ÁØÃâ·Â¿¡ ¾µ ¼ö¸¸ ÀÖ´Ù¸é + ¾î¶² ÇÁ·Î±×·¡¹Ö/½ºÅ©¸³Æ® ¾ð¾î¶óµµ »ç¿ëÇÒ ¼ö ÀÖ´Ù
    • + +
  • ÀÌ¹Ì ÀÖ´Â ÇÁ·Î±×·¥À» ¼öÁ¤¾øÀÌ ¾ÆÆÄÄ¡ ÇÊÅÍ·Î »ç¿ëÇÒ + ¼ö ÀÖ´Ù
    • +
+ +

½ÇÁ¦ »ç¿ëÇϱ⿡´Â ¼º´ÉÀÌ ¶³¾îÁöÁö¸¸, + mod_ext_filter¸¦ »ç¿ëÇÏ¿© ÇÊÅ͸¦ »¡¸® ¸¸µé¾îº¼ + ¼ö ÀÖ´Ù.

+ +
+

Áö½Ã¾îµé

+ +

ÁÖÁ¦

+

Âü°í

+
+
top
+
+

¿¹Á¦

+ +

´Ù¸¥ typeÀÇ ÀÀ´äÀ» HTML·Î ¸¸µç´Ù

+

+ # mod_ext_filter Áö½Ã¾î¸¦ °¡Áö°í
+ # ¿ÜºÎ ÇÁ·Î±×·¥ /usr/bin/enscript¸¦ »ç¿ëÇÏ¿©
+ # ¹®¼­ÆÄÀÏ°ú text/c ÆÄÀÏÀ» HTML·Î ¸¸µé°í °á°úÀÇ
+ # typeÀ» text/html·Î º¯°æÇÏ´Â ÇÊÅ͸¦ Á¤ÀÇÇÑ´Ù
+ ExtFilterDefine c-to-html mode=output \
+ + intype=text/c outtype=text/html \
+ cmd="/usr/bin/enscript --color -W html -Ec -o - -"
+ +
+ <Directory "/export/home/trawick/apacheinst/htdocs/c">
+ + # Ãâ·Â¿¡ »õ·Î¿î ÇÊÅ͸¦ ½ÇÇàÇÏ´Â core Áö½Ã¾î
+ SetOutputFilter c-to-html
+
+ # .c ÆÄÀÏÀÇ typeÀ» text/c·Î ¸¸µå´Â mod_mime
+ # Áö½Ã¾î
+ AddType text/c .c
+
+ # µð¹ö±× ¼öÁØÀ» ³ô¿©¼­ ¿äû¸¶´Ù ÇöÀç ¼³Á¤À»
+ # ¾Ë·ÁÁÖ´Â ·Î±×¹®À» ±â·ÏÇÏ´Â mod_ext_filter
+ # Áö½Ã¾î
+ ExtFilterOptions DebugLevel=1
+ + </Directory> +

+ + +

content ÀÎÄÚµù ÇÊÅÍ ±¸ÇöÇϱâ

+

Note: ¾Æ·¡ gzip ¿¹Á¦´Â ´ÜÁö ¼³¸íÀ» ¿¹·Î µç °ÍÀÌ´Ù. + ½ÇÁ¦ ¼­ºñ½º¿¡ »ç¿ëÇÏ·Á¸é mod_deflate¸¦ + Âü°íÇÏ±æ ¹Ù¶õ´Ù.

+ +

+ # ¿ÜºÎ ÇÊÅ͸¦ Á¤ÀÇÇÏ´Â mod_ext_filter Áö½Ã¾î
+ ExtFilterDefine gzip mode=output cmd=/bin/gzip
+
+ <Location /gzipped>
+ + # Ãâ·ÂÇÒ¶§ gzip ÇÊÅ͸¦ ½ÇÇàÇÏ´Â core Áö½Ã¾î
+ SetOutputFilter gzip
+
+ # "Content-Encoding: gzip" Çì´õ¸¦ Ãß°¡ÇÏ´Â
+ # mod_header Áö½Ã¾î
+ Header set Content-Encoding gzip
+ + </Location> +

+ + +

¼­¹ö¸¦ ´À¸®°Ô Çϱâ

+

+ # catÀ¸·Î ¸ðµç ³»¿ëÀ» Åë°úÇÏ´Â ÇÊÅ͸¦ Á¤ÀÇÇÏ´Â
+ # mod_ext_filter Áö½Ã¾î; catÀº ¾Æ¹«°Íµµ ¼öÁ¤ÇÏÁö
+ # ¾Ê´Â´Ù; ´ÜÁö 󸮰æ·Î¸¦ ±æ°Ô ÇÏ¿© ÀÚ¿øÀ» ´õ ¼Ò¸ðÇÑ´Ù
+ ExtFilterDefine slowdown mode=output cmd=/bin/cat \
+ + preservescontentlength
+ +
+ <Location />
+ + # Ãâ·ÂÇÒ¶§ slowdown ÇÊÅ͸¦ ¿©·¯¹ø ½ÇÇàÇÏ´Â core Áö½Ã¾î
+ #
+ SetOutputFilter slowdown;slowdown;slowdown
+ + </Location> +

+ + +

sed¸¦ »ç¿ëÇÏ¿© ÀÀ´ä¿¡¼­ ±ÛÀ» ´ëüÇϱâ

+

+ # ÀÀ´ä¿¡¼­ ±ÛÀ» ´ëüÇÏ´Â ÇÊÅ͸¦ Á¤ÀÇÇÏ´Â
+ # mod_ext_filter Áö½Ã¾î
+ #
+ ExtFilterDefine fixtext mode=output intype=text/html \
+ + cmd="/bin/sed s/verdana/arial/g"
+ +
+ <Location />
+ + # Ãâ·ÂÇÒ¶§ fixtext ÇÊÅ͸¦ ½ÇÇàÇÏ´Â core Áö½Ã¾î
+ SetOutputFilter fixtext
+ + </Location> +

+ + +

´Ù¸¥ ÇÊÅ͸¦ ÃßÀûÇϱâ

+

+ # ¾ÐÃà ¹®Á¦°¡ Àִ ƯÁ¤ Ŭ¶óÀ̾ðÆ®(IP 192.168.1.31)¿¡
+ # ´ëÇØ mod_deflate°¡ ÀÐ°í ¾²´Â ÀڷḦ ÃßÀûÇÑ´Ù.
+ # ÀÌ ÇÊÅÍ´Â mod_deflate·Î º¸³»±â Àü ÀڷḦ ÃßÀûÇÑ´Ù.
+ ExtFilterDefine tracebefore \
+ + cmd="/bin/tracefilter.pl /tmp/tracebefore" \
+ EnableEnv=trace_this_client
+ +
+ # ÀÌ ÇÊÅÍ´Â mod_deflate¿¡¼­ ³ª¿À´Â ÀڷḦ ÃßÀûÇÑ´Ù.
+ # ftype ÆĶó¹ÌÅ͸¦ »ç¿ëÇÏÁö¾Ê´Â °æ¿ì, ±âº» ÇÊÅÍÇü
+ # AP_FTYPE_RESOURCE´Â ÇÊÅÍ ¼ø¼­¸¦ mod_deflate *ÀÌÀü¿¡*
+ # µÐ´Ù. AP_FTYPE_CONTENT_SET º¸´Ù Á¶±Ý ³ôÀº ¼ýÀÚ°ªÀ»
+ # ÁöÁ¤Çϸé mod_deflate ÀÌÈÄ¿¡ ½ÇÇàÇÑ´Ù.
+ ExtFilterDefine traceafter \
+ + cmd="/bin/tracefilter.pl /tmp/traceafter" \
+ EnableEnv=trace_this_client ftype=21
+ +
+ <Directory /usr/local/docs>
+ + SetEnvIf Remote_Addr 192.168.1.31 trace_this_client
+ SetOutputFilter tracebefore;deflate;traceafter
+ + </Directory> +

+ +

´ÙÀ½Àº ÀڷḦ ÃßÀûÇÏ´Â ÇÊÅÍÀÌ´Ù:

+ #!/usr/local/bin/perl -w
+ use strict;
+
+ open(SAVE, ">$ARGV[0]")
+ + or die "can't open $ARGV[0]: $?";
+ +
+ while (<STDIN>) {
+ + print SAVE $_;
+ print $_;
+ + }
+
+ close(SAVE); +

+ +
+
top
+

ExtFilterDefine Áö½Ã¾î

+ + + + + + +
¼³¸í:¿ÜºÎ ÇÊÅ͸¦ Á¤ÀÇÇÑ´Ù
¹®¹ý:ExtFilterDefine filtername parameters
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Extension
¸ðµâ:mod_ext_filter
+

ExtFilterDefine Áö½Ã¾î´Â ¿ÜºÎ + ÇÊÅÍÀÇ ¼ºÁú°ú ½ÇÇàÇÒ ÇÁ·Î±×·¥, ¾Æ±Ô¸ÕÆ®¸¦ Á¤ÀÇÇÑ´Ù.

+ +

filternameÀº Á¤ÀÇÇÒ ÇÊÅÍ À̸§À» ÁöÁ¤ÇÑ´Ù. + ÀÌ À̸§À» SetOutputFilter Áö½Ã¾î¿¡¼­ »ç¿ëÇÑ´Ù. µî·ÏÇÑ ¸ðµç + ÇÊÅ͵鰣¿¡ À̸§ÀÌ °ãÄ¡¸é ¾ÈµÈ´Ù. ÇöÀç ÇÊÅ͵î·Ï API´Â + ¿À·ù¸¦ º¸°íÇÏÁö ¾Ê´Â´Ù. ±×·¡¼­ »ç¿ëÀÚ´Â À̸§ÀÌ °ãÄ¡´Â ¹®Á¦¸¦ + ¾ËÁö ¸øÇÑ´Ù.

+ +

½ÇÇàÇÒ ¿ÜºÎ ¸í·É¾î¿Í ´Ù¸¥ ¼ºÁúÀ» Á¤ÀÇÇÏ´Â ³ª¸ÓÁö ¾Æ±Ô¸ÕÆ®´Â + ¾î¶² ¼ø¼­·Î ³ª¿Íµµ °¡´ÉÇÏ´Ù. ´Ü, cmd= ÆĶó¹ÌÅÍ´Â + ¹Ýµå½Ã ÇÊ¿äÇÏ´Ù. »ç¿ëÇÒ ¼ö ÀÖ´Â ÆĶó¹ÌÅÍ´Â ´ÙÀ½°ú °°´Ù:

+ +
+
cmd=cmdline
+ +
cmd= Å°¿öµå´Â ½ÇÇàÇÒ ¿ÜºÎ ¸í·É¾î¸¦ ÁöÁ¤ÇÑ´Ù. + ÇÁ·Î±×·¥¸í µÚ¿¡ ¾Æ±Ô¸ÕÆ®°¡ ÀÖ´Ù¸é ¸í·ÉÇàÀ» ½Öµû¿ÈÇ¥·Î + ¹­¾î¾ß ÇÑ´Ù (¿¹¸¦ µé¾î, + cmd="/bin/mypgm arg1 + arg2"). ½©À» °ÅÄ¡Áö¾Ê°í Á÷Á¢ ÇÁ·Î±×·¥À» + ½ÇÇàÇϱ⶧¹®¿¡ ÀϹÝÀûÀÎ ½© µû¿ÈÇ¥´Â ÇÊ¿ä¾ø´Ù. ÇÁ·Î±×·¥ + ¾Æ±Ô¸ÕÆ®µéÀº °ø¹éÀ¸·Î ±¸ºÐÇÑ´Ù. ÇÁ·Î±×·¥ ¾Æ±Ô¸ÕÆ®¿¡ °ø¹éÀÌ + ÀÖ´Ù¸é °ø¹é ¾Õ¿¡ ¹é½½·¡½¬·Î »ç¿ëÇØ¾ß ÇÑ´Ù. ¹é½½·¡½¬°¡ + ¾Æ±Ô¸ÕÆ®ÀÇ ÀϺζó¸é ¹é½½·¡½¬¸¦ µÎ¹ø »ç¿ëÇØ¾ß ÇÑ´Ù. ÇÁ·Î±×·¥À» + ½ÇÇàÇÒ¶§ Ç¥ÁØ CGI ȯ°æº¯¼ö¿Í Ãß°¡·Î DOCUMENT_URI, + DOCUMENT_PATH_INFO, QUERY_STRING_UNESCAPED º¯¼ö¸¦ ¼³Á¤ÇÑ´Ù.
+ +
mode=mode
+ +
ÀÀ´äÀ» ó¸®ÇÏ´Â ÇÊÅÍ´Â (±âº»°ªÀÎ) mode=outputÀ» + »ç¿ëÇÑ´Ù. ¿äûÀ» ó¸®ÇÏ´Â ÇÊÅÍ´Â mode=inputÀ» + »ç¿ëÇÑ´Ù. mode=inputÀº ¾ÆÆÄÄ¡ 2.1¿¡ Ãß°¡µÇ¾ú´Ù.
+ +
intype=imt
+ +
ÀÌ ÆĶó¹ÌÅÍ´Â ÇÊÅͷΠó¸®ÇÒ ¹®¼­ÀÇ ÀÎÅÍ³Ý media + type(Áï, MIME type)À» ÁöÁ¤ÇÑ´Ù. ±âº»ÀûÀ¸·Î ¸ðµç + ¹®¼­¸¦ ÇÊÅͷΠó¸®ÇÑ´Ù. intype=À» ÁöÁ¤Çϸé + ´Ù¸¥ typeÀÇ ¹®¼­´Â ÇÊÅͷΠó¸®ÇÏÁö ¾Ê´Â´Ù.
+ +
outtype=imt
+ +
ÀÌ ÆĶó¹ÌÅÍ´Â ÇÊÅͷΠó¸®ÇÑ ¹®¼­ÀÇ ÀÎÅÍ³Ý media + type(Áï, MIME type)À» ÁöÁ¤ÇÑ´Ù. ÇÊÅÍó¸® ÀÛ¾÷Áß¿¡ + ÀÎÅÍ³Ý media typeÀ» º¯°æÇÒ¶§ À¯¿ëÇÏ´Ù. ±âº»ÀûÀ¸·Î, ÀÎÅÍ³Ý + media typeÀº º¯ÇÏÁö ¾Ê´Â´Ù.
+ +
PreservesContentLength
+ +
PreservesContentLength Å°¿öµå´Â ÇÊÅÍ°¡ + content length¸¦ À¯ÁöÇϵµ·Ï ÇÑ´Ù. ´ëºÎºÐÀÇ ÇÊÅÍ°¡ content + length¸¦ º¯°æÇϹǷΠÀÌ Å°¿öµå´Â ±âº»°ªÀÌ ¾Æ´Ï´Ù. ÇÊÅÍ°¡ + ±æÀ̸¦ À¯ÁöÇÒ¶§¸¸ ÀÌ Å°¿öµå¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
ftype=filtertype
+ +
ÀÌ ÆĶó¹ÌÅÍ´Â ÇÊÅÍ Á¾·ù¿¡ ´ëÇÑ ¼ýÀÚ°ªÀ» ÁöÁ¤ÇÑ´Ù. + ´ëºÎºÐÀÇ °æ¿ì ±âº»°ªÀÎ AP_FTYPE_RESOURCE°¡ Àû´çÇÏ´Ù. + ÇÊÅ͸¦ ½ÇÇàÇÏ´Â ¼ø¼­°¡ ÀÚ¿øÇÊÅÍ¿Í ´Þ¶ó¾ßÇÏ´Â °æ¿ì ÀÌ + ÆĶó¹ÌÅÍ°¡ ÇÊ¿äÇÏ´Ù. Àû´çÇÑ °ªÀ» ¾Ë·Á¸é util_filter.h¿¡ + ÀÖ´Â AP_FTYPE_* Á¤ÀǸ¦ Âü°íÇ϶ó.
+ +
disableenv=env
+ +
ÀÌ ÆĶó¹ÌÅÍ·Î ¼³Á¤ÇÑ È¯°æº¯¼ö°¡ Á¤ÀǵǾú´Ù¸é ÇÊÅ͸¦ + »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
enableenv=env
+ +
ÀÌ ÆĶó¹ÌÅÍ·Î ¼³Á¤ÇÑ È¯°æº¯¼ö°¡ Á¤ÀÇµÈ °æ¿ì ÇÊÅ͸¦ + »ç¿ëÇÑ´Ù.
+
+ +
+
top
+

ExtFilterOptions Áö½Ã¾î

+ + + + + + + +
¼³¸í:mod_ext_filter ¿É¼ÇÀ» ¼³Á¤ÇÑ´Ù
¹®¹ý:ExtFilterOptions option [option] ...
±âº»°ª:ExtFilterOptions DebugLevel=0 NoLogStderr
»ç¿ëÀå¼Ò:directory
»óÅÂ:Extension
¸ðµâ:mod_ext_filter
+

ExtFilterOptions Áö½Ã¾î´Â + mod_ext_filterÀÇ Æ¯º°ÇÑ Ã³¸®¿É¼ÇÀ» ÁöÁ¤ÇÑ´Ù. + OptionÀº ´ÙÀ½Áß Çϳª´Ù.

+ +
+
DebugLevel=n
+ +
+ DebugLevel Å°¿öµå´Â + mod_ext_filter°¡ ±â·ÏÇÏ´Â µð¹ö±× ¹®±¸ + ¼öÁØÀ» Á¤ÇÑ´Ù. ±âº»°ªÀº µð¹ö±×¹®À» ±â·ÏÇÏÁö ¾Ê´Â´Ù. + ÀÌ´Â DebugLevel=0°ú °°´Ù. ³ôÀº ¼ýÀÚ¸¦ + »ç¿ëÇÒ¼ö·Ï, ´õ ¸¹Àº µð¹ö±×¹®ÀÌ ±â·ÏµÇ°í ¼­¹ö ¼º´ÉÀÌ + ¶³¾îÁø´Ù. ¼ýÀÚ°ªÀÇ ½ÇÁ¦ Àǹ̴ mod_ext_filter.c + ¾ÕºÎºÐ¿¡ ÀÖ´Â DBGLVL_ »ó¼ö Á¤ÀÇ¿¡ ¼³¸íµÇÀÖ´Ù. + +

ÁÖÀÇ: ÇÊÅÍ ·Î±×¸¦ ±â·ÏÇÏ·Á¸é core Áö½Ã¾î LogLevelÀ» »ç¿ëÇÏ¿© µð¹ö±×¹®À» + ¾ÆÆÄÄ¡ ¿À·ù·Î±×¿¡ ±â·ÏÇØ¾ß ÇÑ´Ù.

+
+ +
LogStderr | NoLogStderr
+ +
LogStderr Å°¿öµå´Â ¿ÜºÎ ÇÊÅÍ ÇÁ·Î±×·¥ÀÌ + Ç¥ÁØ¿À·ù·Î Ãâ·ÂÇÏ´Â ¹®±¸¸¦ ¾ÆÆÄÄ¡ ¿À·ù·Î±×¿¡ ±â·ÏÇÑ´Ù. + NoLogStderr´Â ÀÌ ±â´ÉÀ» ÇÏÁö ¾Ê´Â´Ù.
+
+ +

¿¹Á¦

+ ExtFilterOptions LogStderr DebugLevel=0 +

+ +

À§ÀÇ ¼³Á¤À» »ç¿ëÇϸé ÇÊÅÍ°¡ Ç¥ÁØ¿À·ù·Î Ãâ·ÂÇÏ´Â ¹®±¸¸¦ + ¾ÆÆÄÄ¡ ¿À·ù·Î±×¿¡ ±â·ÏÇÏ°í, mod_ext_filter´Â + ÀÚü µð¹ö±×¹®À» ±â·ÏÇÏÁö ¾Ê´Â´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_file_cache.html b/docs/manual/mod/mod_file_cache.html new file mode 100644 index 00000000..1fc51cd7 --- /dev/null +++ b/docs/manual/mod/mod_file_cache.html @@ -0,0 +1,7 @@ +URI: mod_file_cache.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_file_cache.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_file_cache.html.en b/docs/manual/mod/mod_file_cache.html.en new file mode 100644 index 00000000..51a47a02 --- /dev/null +++ b/docs/manual/mod/mod_file_cache.html.en @@ -0,0 +1,212 @@ + + + +mod_file_cache - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_file_cache

+
+

Available Languages:  en  | + ko 

+
+ + + +
Description:Caches a static list of files in memory
Status:Experimental
Module Identifier:file_cache_module
Source File:mod_file_cache.c
+

Summary

+ + +
+ This module should be used with care. You can easily create a broken + site using mod_file_cache, so read this document + carefully. +
+ +

Caching frequently requested files that change very + infrequently is a technique for reducing server load. + mod_file_cache provides two techniques for caching + frequently requested static files. Through configuration + directives, you can direct mod_file_cache to either + open then mmap() a file, or to pre-open a file and save + the file's open file handle. Both techniques reduce server + load when processing requests for these files by doing part of the work + (specifically, the file I/O) for serving the file when the + server is started rather than during each request.

+ +

Notice: You cannot use this for speeding up CGI programs or + other files which are served by special content handlers. It + can only be used for regular files which are usually served by + the Apache core content handler.

+ +

This module is an extension of and borrows heavily from the + mod_mmap_static module in Apache 1.3.

+
+

Directives

+ +

Topics

+
+
top
+
+

Using mod_file_cache

+ +

mod_file_cache caches a list of statically + configured files via MMapFile or CacheFile directives in the main server configuration.

+ +

Not all platforms support both directives. For example, Apache + on Windows does not currently support the MMapStatic directive, while + other platforms, like AIX, support both. You will receive an error + message in the server error log if you attempt to use an + unsupported directive. If given an unsupported directive, the + server will start but the file will not be cached. On platforms + that support both directives, you should experiment with both to + see which works best for you.

+ +

MMapFile Directive

+ +

The MMapFile + directive of mod_file_cache maps a list of + statically configured files into memory through the system call + mmap(). This system call is available on most modern + Unix derivates, but not on all. There are sometimes system-specific + limits on the size and number of files that can be + mmap()ed, experimentation is probably the easiest way + to find out.

+ +

This mmap()ing is done once at server start or + restart, only. So whenever one of the mapped files changes on the + filesystem you have to restart the server (see the Stopping and Restarting documentation). + To reiterate that point: if the files are modified in place + without restarting the server you may end up serving requests that + are completely bogus. You should update files by unlinking the old + copy and putting a new copy in place. Most tools such as + rdist and mv do this. The reason why this + modules doesn't take care of changes to the files is that this check + would need an extra stat() every time which is a waste + and against the intent of I/O reduction.

+ + +

CacheFile Directive

+ +

The CacheFile + directive of mod_file_cache opens an active + handle or file descriptor to the file (or files) + listed in the configuration directive and places these open file + handles in the cache. When the file is requested, the server + retrieves the handle from the cache and passes it to the + sendfile() (or TransmitFile() on Windows), + socket API.

+ + + +

This file handle caching is done once at server start or + restart, only. So whenever one of the cached files changes on + the filesystem you have to restart the server (see the + Stopping and Restarting + documentation). To reiterate that point: if the files are + modified in place without restarting the server you + may end up serving requests that are completely bogus. You + should update files by unlinking the old copy and putting a new + copy in place. Most tools such as rdist and + mv do this.

+ + +

Note

+

Don't bother asking for a directive which recursively + caches all the files in a directory. Try this instead... See the + Include directive, and consider + this command:

+ +

+ find /www/htdocs -type f -print \
+ | sed -e 's/.*/mmapfile &/' > /www/conf/mmap.conf +

+
+
+
top
+

CacheFile Directive

+ + + + + + +
Description:Cache a list of file handles at startup time
Syntax:CacheFile file-path [file-path] ...
Context:server config
Status:Experimental
Module:mod_file_cache
+

The CacheFile directive opens handles to + one or more files (given as whitespace separated arguments) and + places these handles into the cache at server startup + time. Handles to cached files are automatically closed on a server + shutdown. When the files have changed on the filesystem, the + server should be restarted to to re-cache them.

+ +

Be careful with the file-path arguments: They have + to literally match the filesystem path Apache's URL-to-filename + translation handlers create. We cannot compare inodes or other + stuff to match paths through symbolic links etc. + because that again would cost extra stat() system + calls which is not acceptable. This module may or may not work + with filenames rewritten by mod_alias or + mod_rewrite.

+ +

Example

+ CacheFile /usr/local/apache/htdocs/index.html +

+ +
+
top
+

MMapFile Directive

+ + + + + + +
Description:Map a list of files into memory at startup time
Syntax:MMapFile file-path [file-path] ...
Context:server config
Status:Experimental
Module:mod_file_cache
+

The MMapFile directive maps one or more files + (given as whitespace separated arguments) into memory at server + startup time. They are automatically unmapped on a server + shutdown. When the files have changed on the filesystem at + least a HUP or USR1 signal should be send to + the server to re-mmap() them.

+ +

Be careful with the file-path arguments: They have + to literally match the filesystem path Apache's URL-to-filename + translation handlers create. We cannot compare inodes or other + stuff to match paths through symbolic links etc. + because that again would cost extra stat() system + calls which is not acceptable. This module may or may not work + with filenames rewritten by mod_alias or + mod_rewrite.

+ +

Example

+ MMapFile /usr/local/apache/htdocs/index.html +

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_file_cache.html.ko.euc-kr b/docs/manual/mod/mod_file_cache.html.ko.euc-kr new file mode 100644 index 00000000..ef5709ed --- /dev/null +++ b/docs/manual/mod/mod_file_cache.html.ko.euc-kr @@ -0,0 +1,200 @@ + + + +mod_file_cache - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_file_cache

+
+

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

+
+ + + +
¼³¸í:¸Þ¸ð¸®¿¡ Á¤Àû ÆÄÀϵéÀ» ij½¬
»óÅÂ:Experimental
¸ðµâ¸í:file_cache_module
¼Ò½ºÆÄÀÏ:mod_file_cache.c
+

¿ä¾à

+ + +
+ ÀÌ ¸ðµâÀº Á¶½ÉÇؼ­ »ç¿ëÇØ¾ß ÇÑ´Ù. mod_file_cache¸¦ + »ç¿ëÇÏ¿© »çÀÌÆ®¸¦ ¾û¸ÁÀ¸·Î ¸¸µé±â ½±±â¶§¹®¿¡ ÀÌ ¹®¼­¸¦ + ²Ä²ÄÈ÷ ÀÐ±æ ¹Ù¶õ´Ù. +
+ +

°ÅÀÇ º¯ÇÏÁö ¾Ê°í ÀÚÁÖ ¿äûµÇ´Â ÆÄÀÏÀ» ij½¬¿¡ + ÀúÀåÇÏ¿© ¼­¹ö ºÎÇϸ¦ ÁÙÀÏ ¼ö ÀÖ´Ù. mod_file_cache´Â + ÀÚÁÖ ¿äûµÇ´Â Á¤Àû ÆÄÀÏÀ» µÎ°¡Áö ¹æ½ÄÀ¸·Î ij½¬¿¡ + ÀúÀåÇÑ´Ù. ¼³Á¤ Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© mod_file_cache°¡ + ÆÄÀÏÀ» ¿­°í(open) mmap()ÇÒÁö ¾Æ´Ï¸é ÆÄÀÏÀ» + ¿­°í ÆÄÀÏ ÇÚµéÀ» ÀúÀåÇÒÁö °áÁ¤ÇÑ´Ù. µÎ ¹æ½Ä ¸ðµÎ + ÆÄÀÏÀ» ¼­ºñ½ºÇϱâÀ§ÇØ ÇÊ¿äÇÑ ÀÛ¾÷ÀÇ ÀϺθ¦ (ƯÈ÷ ÆÄÀÏ ÀÔÃâ·Â + ÀÛ¾÷) ÆÄÀÏÀ» ¿äûÇÒ ¶§¸¶´Ù ¸Å¹ø ÇÏ´Â ´ë½Å ¼­¹ö°¡ ½ÃÀÛÇÒ¶§ + Çѹø¸¸ ÇÏ¿© ¼­¹ö ºÎÇÏ°¡ °¨¼ÒÇÑ´Ù.

+ +

ÁÖÀÇ: ÀÌ ¹æ¹ýÀº CGI ÇÁ·Î±×·¥À̳ª Ưº°ÇÑ ³»¿ëÇڵ鷯¸¦ + ÅëÇØ ¼­ºñ½ºÇÏ´Â ÆÄÀÏÀÇ ¼­ºñ½º ¼Óµµ¸¦ ³ôÀÏ ¼ö ¾ø´Ù. ÀÌ ¹æ¹ýÀº + º¸Åë ¾ÆÆÄÄ¡ core ³»¿ëÇڵ鷯°¡ ¼­ºñ½ºÇÏ´Â ÀϹÝÆÄÀÏ¿¡¸¸ + Àû¿ëµÈ´Ù.

+ +

ÀÌ ¸ðµâÀº ¾ÆÆÄÄ¡ 1.3¿¡ ÀÖ´Â mod_mmap_static + ¸ðµâÀÇ ±â´ÉÀ» È®ÀåÇÑ °á°ú´Ù.

+
+

Áö½Ã¾îµé

+ +

ÁÖÁ¦

+
+
top
+
+

mod_file_cache »ç¿ëÇϱâ

+ +

mod_file_cache´Â ÁÖ¼­¹ö ¼³Á¤¿¡¼­ MMapFile°ú CacheFile Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + ¼³Á¤ÇÑ Á¤Àû ÆÄÀϵéÀ» ij½¬¿¡ ÀúÀåÇÑ´Ù.

+ +

¸ðµç Ç÷¡ÆûÀÌ µÎ Áö½Ã¾î¸¦ ¸ðµÎ Áö¿øÇÏ´Â °ÍÀº ¾Æ´Ï´Ù. + ¿¹¸¦ µé¾î, À©µµ¿ìÁî¿ë ¾ÆÆÄÄ¡´Â ÇöÀç MMapStatic Áö½Ã¾î¸¦ + Áö¿øÇÏÁö ¾ÊÁö¸¸, AIX °°Àº ´Ù¸¥ Ç÷¡ÆûÀº µÑ ¸ðµÎ¸¦ Áö¿øÇÑ´Ù. + Áö¿øÇÏÁö¾Ê´Â Áö½Ã¾î¸¦ »ç¿ëÇÒ °æ¿ì ¼­¹ö ¿À·ù ·Î±×¿¡ ¿À·ù¹®À» + ³²±ä´Ù. Áö¿øÇÏÁö¾Ê´Â Áö½Ã¾î¸¦ »ç¿ëÇصµ ¼­¹ö´Â µ¿ÀÛÇÏÁö¸¸ + ÆÄÀÏÀ» ij½¬¿¡ ÀúÀåÇÏÁö ¾Ê´Â´Ù. µÎ Áö½Ã¾î¸¦ ¸ðµÎ Áö¿øÇÏ´Â + Ç÷¡ÆûÀ» »ç¿ëÇÑ´Ù¸é ¾î¶² ¹æ½ÄÀÌ ´õ ÁÁÀºÁö ½ÇÇèÇغ¸¶ó.

+ +

MMapFile Áö½Ã¾î

+ +

mod_file_cacheÀÇ MMapFile Áö½Ã¾î´Â + ¼³Á¤ÇÑ Á¤Àû ÆÄÀϵéÀ» mmap() ½Ã½ºÅÛÈ£ÃâÀ» + »ç¿ëÇÏ¿© ¸Þ¸ð¸®¿¡ ´ëÀÀÇÑ´Ù. ÃֽŠÀ¯´Ð½º·ù ¿î¿µÃ¼Á¦¶ó¸é + º¸Åë ÀÌ ½Ã½ºÅÛÈ£ÃâÀÌ ÀÖÁö¸¸, ¾ø´Â ¿î¿µÃ¼Á¦µµ ÀÖ´Ù. ¶Ç, + mmap()ÇÒ ¼ö ÀÖ´Â ÆÄÀÏ Å©±â¿Í °³¼ö¸¦ ½Ã½ºÅÛÀÌ + Á¦ÇÑÇÒ ¼ö ÀÖÀ¸¹Ç·Î ¹Ì¸® ½ÇÇèÇغ¸´Â °ÍÀÌ ÁÁ´Ù.

+ +

¼­¹ö´Â ½ÃÀÛÇÒ¶§¿Í Àç½ÃÀÛÇÒ¶§¸¸ mmap()ÇÑ´Ù. + ±×·¡¼­ ÆÄÀϽýºÅÛ¿¡¼­ ÇØ´ç ÆÄÀÏÁß Çϳª¶óµµ º¯°æµÇ¸é ¼­¹ö¸¦ + Àç½ÃÀÛÇØ¾ß ÇÑ´Ù (Áß´Ü°ú + Àç½ÃÀÛ ¹®¼­ Âü°í). ´Ù½Ã ¸»Çؼ­ ÆÄÀÏÀÌ º¯°æµÇ¾ú´Âµ¥ + ¼­¹ö¸¦ Àç½ÃÀÛÇÏÁö ¾ÊÀ¸¸é ¿ÏÀüÈ÷ ÀÌ»óÇÏ°Ô ¿äûÀ» ¼­ºñ½ºÇÒÁöµµ + ¸ð¸¥´Ù. ÀÌÀü ÆÄÀÏÀ» Áö¿ì°í(unlink) ±× ÀÚ¸®¿¡ »õ·Î¿î ÆÄÀÏÀ» + ¸¸µé´Â ¹æ½ÄÀ¸·Î ÆÄÀÏÀ» ¼öÁ¤ÇØ¾ß ÇÑ´Ù. rdist³ª + mv¿Í °°Àº ´ë´Ù¼öÀÇ µµ±¸°¡ ÀÌ·± ¹æ½ÄÀ¸·Î µ¿ÀÛÇÑ´Ù. + ¸Å¹ø Ãß°¡·Î ºÒÇÊ¿äÇÑ stat() °Ë»ç°¡ ÇÊ¿äÇÏ°í + ÀÔÃâ·Â °¨¼Ò¶ó´Â ¿ø·¡ Àǵµ¿¡ ¹ÝÇϱ⶧¹®¿¡ ÀÌ ¸ðµâÀº ÆÄÀÏÀÇ + º¯È­¸¦ ¹«½ÃÇÑ´Ù.

+ + +

CacheFile Áö½Ã¾î

+ +

mod_file_cacheÀÇ CacheFile Áö½Ã¾î´Â + ¼³Á¤ Áö½Ã¾î¿¡ ¿­°ÅÇÑ ÆÄÀÏ(°ú ÆÄÀϵé)À» ¿­¾î¼­ ÆÄÀÏÀÇ + ÇÚµé(handle) ȤÀº ÆÄÀÏ ±â¼úÀÚ(file descriptor)¸¦ + ij½¬¿¡ ÀúÀåÇÑ´Ù. ÆÄÀÏÀ» ¿äûÇÏ¸é ¼­¹ö´Â ij½¬¿¡¼­ ÇÚµéÀ» + ã¾Æ¼­ ¼ÒÄÏ API sendfile()¿¡ (À©µµ¿ìÁî¿¡¼­´Â + TransmitFile()) ³Ñ±ä´Ù.

+ + + +

¼­¹ö´Â ½ÃÀÛÇÒ¶§¿Í Àç½ÃÀÛÇÒ¶§¸¸ ÆÄÀÏ ÇÚµéÀ» ij½¬ÇÑ´Ù. + ±×·¡¼­ ÆÄÀϽýºÅÛ¿¡¼­ ij½¬ÇÑ ÆÄÀÏÁß Çϳª¶óµµ º¯°æµÇ¸é + ¼­¹ö¸¦ Àç½ÃÀÛÇØ¾ß ÇÑ´Ù (Áß´Ü°ú Àç½ÃÀÛ ¹®¼­ Âü°í). + ´Ù½Ã ¸»Çؼ­ ÆÄÀÏÀÌ º¯°æµÇ¾ú´Âµ¥ ¼­¹ö¸¦ Àç½ÃÀÛÇÏÁö ¾ÊÀ¸¸é + ¿ÏÀüÈ÷ ÀÌ»óÇÏ°Ô ¿äûÀ» ¼­ºñ½ºÇÒÁöµµ ¸ð¸¥´Ù. ÀÌÀü ÆÄÀÏÀ» + Áö¿ì°í(unlink) ±× ÀÚ¸®¿¡ »õ·Î¿î ÆÄÀÏÀ» ¸¸µå´Â ¹æ½ÄÀ¸·Î + ÆÄÀÏÀ» ¼öÁ¤ÇØ¾ß ÇÑ´Ù. rdist³ª mv¿Í + °°Àº ´ë´Ù¼öÀÇ µµ±¸°¡ ÀÌ·± ¹æ½ÄÀ¸·Î µ¿ÀÛÇÑ´Ù.

+ + +

ÁÖÀÇ

+

µð·ºÅ丮ÀÇ ¸ðµç ÆÄÀÏÀ» Àç±ÍÀûÀ¸·Î ij½¬¿¡ ÀúÀåÇÏ´Â Áö½Ã¾î´Â + ¾ø´Ù. ´ë½Å ´ÙÀ½°ú °°ÀÌ Çغ¸¶ó... Include Áö½Ã¾î¸¦ Âü°íÇÏ¿© ´ÙÀ½°ú + °°Àº ¸í·É¾î¸¦ ½ÇÇàÇÑ´Ù:

+ +

+ find /www/htdocs -type f -print \
+ | sed -e 's/.*/mmapfile &/' > /www/conf/mmap.conf +

+
+
+
top
+

CacheFile Áö½Ã¾î

+ + + + + + +
¼³¸í:½ÃÀ۽à ¿©·¯ ÆÄÀÏ ÇÚµéÀ» ij½¬ÇÑ´Ù
¹®¹ý:CacheFile file-path [file-path] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_file_cache
+

CacheFile Áö½Ã¾î´Â ¼­¹ö°¡ ½ÃÀÛÇÒ¶§ + ¿©·¯ ÆÄÀÏÀ» ¿­°í(open) ÆÄÀϵéÀÇ ÇÚµéÀ» ij½¬¿¡ ÀúÀåÇÑ´Ù. + ¼­¹ö Á¾·á½Ã ÀÚµ¿À¸·Î ij½¬ÇÑ ÆÄÀÏÀÇ ÇÚµéÀ» ´Ý´Â´Ù(close). + ÆÄÀϽýºÅÛ¿¡¼­ ÆÄÀÏÀÌ º¯°æµÇ¸é ÆÄÀÏÀ» ´Ù½Ã ij½¬ÇϱâÀ§ÇØ + ¼­¹ö¸¦ Àç½ÃÀÛÇØ¾ß ÇÑ´Ù.

+ +

file-path ¾Æ±Ô¸ÕÆ®¸¦ Á¶½ÉÇضó. ¾Æ±Ô¸ÕÆ®´Â + ¾ÆÆÄÄ¡ÀÇ URL-ÆÄÀÏ¸í º¯È¯ Çڵ鷯°¡ ¸¸µç ÆÄÀϽýºÅÛ °æ·Î¿Í + Á¤È®È÷ ÀÏÄ¡ÇØ¾ß ÇÑ´Ù. Çѹø ´õ ºÒÇÊ¿äÇÑ stat() + ½Ã½ºÅÛÈ£ÃâÀÌ ÇÊ¿äÇϱ⶧¹®¿¡ inode³ª ½Éº¼¸µÅ© µîÀ» + °æ·Î¸¦ ÁöÁ¤ÇÒ ¼ö ¾ø´Ù. ÀÌ ¸ðµâÀº mod_alias³ª + mod_rewrite·Î ÀçÀÛ¼ºÇÑ ÆÄÀϸíÀ» ´Ù·ê ¼ö + Àֱ⵵ ¾ø±âµµ ÇÏ´Ù.

+ +

¿¹Á¦

+ CacheFile /usr/local/apache/htdocs/index.html +

+ +
+
top
+

MMapFile Áö½Ã¾î

+ + + + + + +
¼³¸í:½ÃÀ۽à ¿©·¯ ÆÄÀÏÀ» ¸Þ¸ð¸®¿¡ ´ëÀÀÇÑ´Ù
¹®¹ý:MMapFile file-path [file-path] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_file_cache
+

MMapFile Áö½Ã¾î´Â ¼­¹ö°¡ ½ÃÀÛÇÒ¶§ + (°ø¹éÀ¸·Î ±¸ºÐÇÑ ¾Æ±Ô¸ÕÆ®·Î ÁöÁ¤ÇÑ) ¿©·¯ ÆÄÀÏÀ» ¸Þ¸ð¸®¿¡ + ´ëÀÀÇÑ´Ù(map). ¼­¹ö Á¾·á½Ã ÀÚµ¿À¸·Î ´ëÀÀÀ» Ǭ´Ù(unmap). + ÆÄÀϽýºÅÛ¿¡¼­ ÆÄÀÏÀÌ º¯°æµÇ¸é ÆÄÀϵéÀ» ´Ù½Ã + mmap()ÇϱâÀ§ÇØ ÃÖ¼ÒÇÑ ¼­¹ö¿¡ HUPÀ̳ª + USR1 ½Ã±×³ÎÀ» º¸³»¾ß ÇÑ´Ù.

+ +

file-path ¾Æ±Ô¸ÕÆ®¸¦ Á¶½ÉÇضó. ¾Æ±Ô¸ÕÆ®´Â + ¾ÆÆÄÄ¡ÀÇ URL-ÆÄÀÏ¸í º¯È¯ Çڵ鷯°¡ ¸¸µç ÆÄÀϽýºÅÛ °æ·Î¿Í + Á¤È®È÷ ÀÏÄ¡ÇØ¾ß ÇÑ´Ù. Çѹø ´õ ºÒÇÊ¿äÇÑ stat() + ½Ã½ºÅÛÈ£ÃâÀÌ ÇÊ¿äÇϱ⶧¹®¿¡ inode³ª ½Éº¼¸µÅ© µîÀ» + °æ·Î¸¦ ÁöÁ¤ÇÒ ¼ö ¾ø´Ù. ÀÌ ¸ðµâÀº mod_alias³ª + mod_rewrite·Î ÀçÀÛ¼ºÇÑ ÆÄÀϸíÀ» ´Ù·ê ¼ö + Àֱ⵵ ¾ø±âµµ ÇÏ´Ù.

+ +

¿¹Á¦

+ MMapFile /usr/local/apache/htdocs/index.html +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_filter.html b/docs/manual/mod/mod_filter.html new file mode 100644 index 00000000..522140ca --- /dev/null +++ b/docs/manual/mod/mod_filter.html @@ -0,0 +1,3 @@ +URI: mod_filter.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_filter.html.en b/docs/manual/mod/mod_filter.html.en new file mode 100644 index 00000000..8a627237 --- /dev/null +++ b/docs/manual/mod/mod_filter.html.en @@ -0,0 +1,443 @@ + + + +mod_filter - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_filter

+
+

Available Languages:  en 

+
+ + + + +
Description:Context-sensitive smart filter configuration module
Status:Base
Module Identifier:filter_module
Source File:mod_filter.c
Compatibility:Version 2.1 and later
+

Summary

+ +

This module enables smart, context-sensitive configuration of + output content filters. For example, apache can be configured to + process different content-types through different filters, even + when the content-type is not known in advance (e.g. in a proxy).

+ +

mod_filter works by introducing indirection into + the filter chain. Instead of inserting filters in the chain, we insert + a filter harness which in turn dispatches conditionally + to a filter provider. Any content filter may be used as a provider + to mod_filter; no change to existing filter modules is + required (although it may be possible to simplify them).

+
+ +
top
+
+

Smart Filtering

+

In the traditional filtering model, filters are inserted unconditionally + using AddOutputFilter and family. + Each filter then needs to determine whether to run, and there is little + flexibility available for server admins to allow the chain to be + configured dynamically.

+ +

mod_filter by contrast gives server administrators a + great deal of flexibility in configuring the filter chain. In fact, + filters can be inserted based on any Request Header, Response Header + or Environment Variable. This generalises the limited flexibility offered + by AddOutputFilterByType, and fixes + it to work correctly with dynamic content, regardless of the + content generator. The ability to dispatch based on Environment + Variables offers the full flexibility of configuration with + mod_rewrite to anyone who needs it.

+
top
+
+

Filter Declarations, Providers and Chains

+

+ [This image displays the traditional filter model]
+ Figure 1: The traditional filter model

+ +

In the traditional model, output filters are a simple chain + from the content generator (handler) to the client. This works well + provided the filter chain can be correctly configured, but presents + problems when the filters need to be configured dynamically based on + the outcome of the handler.

+ +

+ [This image shows the mod_filter model]
+ Figure 2: The mod_filter model

+ +

mod_filter works by introducing indirection into + the filter chain. Instead of inserting filters in the chain, we insert + a filter harness which in turn dispatches conditionally + to a filter provider. Any content filter may be used as a provider + to mod_filter; no change to existing filter modules + is required (although it may be possible to simplify them). There can be + multiple providers for one filter, but no more than one provider will + run for any single request.

+ +

A filter chain comprises any number of instances of the filter + harness, each of which may have any number of providers. A special + case is that of a single provider with unconditional dispatch: this + is equivalent to inserting the provider filter directly into the chain.

+
top
+
+

Configuring the Chain

+

There are three stages to configuring a filter chain with + mod_filter. For details of the directives, see below.

+ +
+
Declare Filters
+
The FilterDeclare directive + declares a filter, assigning it a name and filter type. Required + only if the filter is not the default type AP_FTYPE_RESOURCE.
+ +
Register Providers
+
The FilterProvider + directive registers a provider with a filter. The filter may have + been declared with FilterDeclare; if not, FilterProvider will implicitly + declare it with the default type AP_FTYPE_RESOURCE. The provider + must have been + registered with ap_register_output_filter by some module. + The remaining arguments to FilterProvider are a dispatch criterion and a match string. + The former may be an HTTP request or response header, an environment + variable, or the Handler used by this request. The latter is matched + to it for each request, to determine whether this provider will be + used to implement the filter for this request.
+ +
Configure the Chain
+
The above directives build components of a smart filter chain, + but do not configure it to run. The FilterChain directive builds a filter chain from smart + filters declared, offering the flexibility to insert filters at the + beginning or end of the chain, remove a filter, or clear the chain.
+
+
top
+
+

Examples

+
+
Server side Includes (SSI)
+
A simple case of using mod_filter in place of + AddOutputFilterByType +

+ FilterDeclare SSI
+ FilterProvider SSI INCLUDES resp=Content-Type $text/html
+ FilterChain SSI +

+
+ +
Server side Includes (SSI)
+
The same as the above but dispatching on handler (classic + SSI behaviour; .shtml files get processed). +

+ FilterProvider SSI INCLUDES Handler server-parsed
+ FilterChain SSI +

+
+ +
Emulating mod_gzip with mod_deflate
+
Insert INFLATE filter only if "gzip" is NOT in the + Accept-Encoding header. This filter runs with ftype CONTENT_SET. +

+ FilterDeclare gzip CONTENT_SET
+ FilterProvider gzip inflate req=Accept-Encoding !$gzip
+ FilterChain gzip +

+
+ +
Image Downsampling
+
Suppose we want to downsample all web images, and have filters + for GIF, JPEG and PNG. +

+ FilterProvider unpack jpeg_unpack Content-Type $image/jpeg
+ FilterProvider unpack gif_unpack Content-Type $image/gif
+ FilterProvider unpack png_unpack Content-Type $image/png
+
+ FilterProvider downsample downsample_filter Content-Type $image
+ FilterProtocol downsample "change=yes"
+
+ FilterProvider repack jpeg_pack Content-Type $image/jpeg
+ FilterProvider repack gif_pack Content-Type $image/gif
+ FilterProvider repack png_pack Content-Type $image/png
+ <Location /image-filter>
+ + FilterChain unpack downsample repack
+ + </Location> +

+
+
+
top
+
+

Protocol Handling

+

Historically, each filter is responsible for ensuring that whatever + changes it makes are correctly represented in the HTTP response headers, + and that it does not run when it would make an illegal change. This + imposes a burden on filter authors to re-implement some common + functionality in every filter:

+ +
    +
  • Many filters will change the content, invalidating existing content + tags, checksums, hashes, and lengths.
    • + +
  • Filters that require an entire, unbroken response in input need to + ensure they don't get byteranges from a backend.
    • + +
  • Filters that transform output in a filter need to ensure they don't + violate a Cache-Control: no-transform header from the + backend.
    • + +
  • Filters may make responses uncacheable.
    • +
+ +

mod_filter aims to offer generic handling of these + details of filter implementation, reducing the complexity required of + content filter modules. This is work-in-progress; the + FilterProtocol implements + some of this functionality for back-compatibility with Apache 2.0 + modules. For httpd 2.1 and later, the + ap_register_output_filter_protocol and + ap_filter_protocol API enables filter modules to + declare their own behaviour.

+ +

At the same time, mod_filter should not interfere + with a filter that wants to handle all aspects of the protocol. By + default (i.e. in the absence of any FilterProtocol directives), mod_filter + will leave the headers untouched.

+ +

At the time of writing, this feature is largely untested, + as modules in common use are designed to work with 2.0. + Modules using it should test it carefully.

+
+
top
+

FilterChain Directive

+ + + + + + + +
Description:Configure the filter chain
Syntax:FilterChain [+=-@!]filter-name ...
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Base
Module:mod_filter
+

This configures an actual filter chain, from declared filters. + FilterChain takes any number of arguments, + each optionally preceded with a single-character control that + determines what to do:

+ +
+
+filter-name
+
Add filter-name to the end of the filter chain
+ +
@filter-name
+
Insert filter-name at the start of the filter chain
+ +
-filter-name
+
Remove filter-name from the filter chain
+ +
=filter-name
+
Empty the filter chain and insert filter-name
+ +
!
+
Empty the filter chain
+ +
filter-name
+
Equivalent to +filter-name
+
+ +
+
top
+

FilterDeclare Directive

+ + + + + + + +
Description:Declare a smart filter
Syntax:FilterDeclare filter-name [type]
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Base
Module:mod_filter
+

This directive declares an output filter together with a + header or environment variable that will determine runtime + configuration. The first argument is a filter-name + for use in FilterProvider, + FilterChain and + FilterProtocol directives.

+ +

The final (optional) argument + is the type of filter, and takes values of ap_filter_type + - namely RESOURCE (the default), CONTENT_SET, + PROTOCOL, TRANSCODE, CONNECTION + or NETWORK.

+ +
+
top
+

FilterProtocol Directive

+ + + + + + + +
Description:Deal with correct HTTP protocol handling
Syntax:FilterProtocol filter-name [provider-name] + proto-flags
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Base
Module:mod_filter
+

This directs mod_filter to deal with ensuring the + filter doesn't run when it shouldn't, and that the HTTP response + headers are correctly set taking into account the effects of the + filter.

+ +

There are two forms of this directive. With three arguments, it + applies specifically to a filter-name and a + provider-name for that filter. + With two arguments it applies to a filter-name whenever the + filter runs any provider.

+ +

proto-flags is one or more of

+ +
+
change=yes
+
The filter changes the content, including possibly the content + length
+ +
change=1:1
+
The filter changes the content, but will not change the content + length
+ +
byteranges=no
+
The filter cannot work on byteranges and requires complete input
+ +
proxy=no
+
The filter should not run in a proxy context
+ +
proxy=transform
+
The filter transforms the response in a manner incompatible with + the HTTP Cache-Control: no-transform header.
+ +
cache=no
+
The filter renders the output uncacheable (eg by introducing randomised + content changes)
+
+ +
+
top
+

FilterProvider Directive

+ + + + + + + +
Description:Register a content filter
Syntax:FilterProvider filter-name provider-name + [req|resp|env]=dispatch match
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Base
Module:mod_filter
+

This directive registers a provider for the smart filter. + The provider will be called if and only if the match declared + here matches the value of the header or environment variable declared + as dispatch.

+ +

+ provider-name must have been registered by loading + a module that registers the name with + ap_register_output_filter. + +

+ +

The dispatch argument is a string with optional + req=, resp= or env= prefix + causing it to dispatch on (respectively) the request header, response + header, or environment variable named. In the absence of a + prefix, it defaults to a response header. A special case is the + word handler, which causes mod_filter + to dispatch on the content handler.

+ +

The match argument specifies a match that will be applied to + the filter's dispatch criterion. The match may be + a string match (exact match or substring), a regex, an integer (greater, lessthan or equals), or + unconditional. The first characters of the match argument + determines this:

+ +

First, if the first character is an exclamation mark + (!), this reverses the rule, so the provider will be used + if and only if the match fails.

+ +

Second, it interprets the first character excluding + any leading ! as follows:

+ + + + + + + + + + + +
CharacterDescription
(none)exact match
$substring match
/regex match (delimited by a second /)
=integer equality
<integer less-than
<=integer less-than or equal
>integer greater-than
>=integer greater-than or equal
*Unconditional match
+ +
+
top
+

FilterTrace Directive

+ + + + + + +
Description:Get debug/diagnostic information from + mod_filter
Syntax:FilterTrace filter-name level
Context:server config, virtual host, directory
Status:Base
Module:mod_filter
+

This directive generates debug information from + mod_filter. + It is designed to help test and debug providers (filter modules), although + it may also help with mod_filter itself.

+ +

The debug output depends on the level set:

+
+
0 (default)
+
No debug information is generated.
+ +
1
+
mod_filter will record buckets and brigades + passing through the filter to the error log, before the provider has + processed them. This is similar to the information generated by + mod_diagnostics. +
+ +
2 (not yet implemented)
+
Will dump the full data passing through to a tempfile before the + provider. For single-user debug only; this will not + support concurrent hits.
+
+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_headers.html b/docs/manual/mod/mod_headers.html new file mode 100644 index 00000000..3729f8da --- /dev/null +++ b/docs/manual/mod/mod_headers.html @@ -0,0 +1,11 @@ +URI: mod_headers.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_headers.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_headers.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_headers.html.en b/docs/manual/mod/mod_headers.html.en new file mode 100644 index 00000000..25c5bc06 --- /dev/null +++ b/docs/manual/mod/mod_headers.html.en @@ -0,0 +1,356 @@ + + + +mod_headers - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_headers

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Customization of HTTP request and response +headers
Status:Extension
Module Identifier:headers_module
Source File:mod_headers.c
Compatibility:RequestHeader +is available only in Apache 2.0
+

Summary

+ +

This module provides directives to control and modify HTTP + request and response headers. Headers can be merged, replaced + or removed.

+
+ +
top
+
+

Order of Processing

+ +

The directives provided by mod_headers can + occur almost anywhere within the server configuration, and can be + limited in scope by enclosing them in configuration sections.

+ +

Order of processing is important and is affected both by the + order in the configuration file and by placement in configuration sections. These + two headers have a different effect if reversed:

+ +

+ RequestHeader append MirrorID "mirror 12"
+ RequestHeader unset MirrorID +

+ +

This way round, the MirrorID header is not set. If + reversed, the MirrorID header is set to "mirror 12".

+
top
+
+

Early and Late Processing

+

mod_headers can be applied either early or late + in the request. The normal mode is late, when Request Headers are + set immediately before running the content generator and Response + Headers just as the response is sent down the wire. Always use + Late mode in an operational server.

+ +

Early mode is designed as a test/debugging aid for developers. + Directives defined using the early keyword are set + right at the beginning of processing the request. This means + they can be used to simulate different requests and set up test + cases, but it also means that headers may be changed at any time + by other modules before generating a Response.

+ +

Because early directives are processed before the request path's + configuration is traversed, early headers can only be set in a + main server or virtual host context. Early directives cannot depend + on a request path, so they will fail in contexts such as + <Directory> or <Location>.

+
top
+
+

Examples

+ +
    +
  1. + Copy all request headers that begin with "TS" to the + response headers: + +

    + Header echo ^TS +

    +
    2. + +
  2. + Add a header, MyHeader, to the response including a + timestamp for when the request was received and how long it + took to begin serving the request. This header can be used by + the client to intuit load on the server or in isolating + bottlenecks between the client and the server. + +

    + Header add MyHeader "%D %t" +

    + +

    results in this header being added to the response:

    + +

    + MyHeader: D=3775428 t=991424704447256 +

    +
    3. + +
  3. + Say hello to Joe + +

    + Header add MyHeader "Hello Joe. It took %D microseconds \
    + for Apache to serve this request." +

    + +

    results in this header being added to the response:

    + +

    + MyHeader: Hello Joe. It took D=3775428 microseconds for Apache + to serve this request. +

    +
    4. + +
  4. + Conditionally send MyHeader on the response if and + only if header "MyRequestHeader" is present on the request. This + is useful for constructing headers in response to some client + stimulus. Note that this example requires the services of the + mod_setenvif module. + +

    + SetEnvIf MyRequestHeader value HAVE_MyRequestHeader
    + Header add MyHeader "%D %t mytext" env=HAVE_MyRequestHeader
    +

    + +

    If the header MyRequestHeader: value is present on + the HTTP request, the response will contain the following header:

    + +

    + MyHeader: D=3775428 t=991424704447256 mytext +

    +
    5. +
+
+
top
+

Header Directive

+ + + + + + + +
Description:Configure HTTP response headers
Syntax:Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_headers
+

This directive can replace, merge or remove HTTP response + headers. The header is modified just after the content handler + and output filters are run, allowing outgoing headers to be + modified.

+ +

The optional condition can be either onsuccess + or always. It determines, which internal header table should be + operated on. onsuccess stands for 2xx + status codes and always for all status codes (including + 2xx). Especially if you want to unset headers + set by certain modules, you should try out, which table is affected.

+ +

The action it performs is determined by the second + argument. This can be one of the following values:

+ +
+
set
+
The response header is set, replacing any previous header + with this name. The value may be a format string.
+ +
append
+
The response header is appended to any existing header of + the same name. When a new value is merged onto an existing + header it is separated from the existing header with a comma. + This is the HTTP standard way of giving a header multiple values.
+ +
add
+
The response header is added to the existing set of headers, + even if this header already exists. This can result in two + (or more) headers having the same name. This can lead to + unforeseen consequences, and in general "append" should be + used instead.
+ +
unset
+
The response header of this name is removed, if it exists. + If there are multiple headers of the same name, all will be + removed. value must be omitted.
+ +
echo
+
Request headers with this name are echoed back in the + response headers. header may be a + regular expression. + value must be omitted.
+
+ +

This argument is followed by a header name, which + can include the final colon, but it is not required. Case is + ignored for set, append, add + and unset. The header name for echo + is case sensitive and may be a regular + expression.

+ +

For add, append and set a + value is specified as the third argument. If value + contains spaces, it should be surrounded by doublequotes. + value may be a character string, a string containing format + specifiers or a combination of both. The following format specifiers + are supported in value:

+ + + + + + + + + + + + +
FormatDescription
%%The percent sign
%tThe time the request was received in Universal Coordinated Time + since the epoch (Jan. 1, 1970) measured in microseconds. The value + is preceded by t=.
%DThe time from when the request was received to the time the + headers are sent on the wire. This is a measure of the duration + of the request. The value is preceded by D=.
%{FOOBAR}eThe contents of the environment + variable FOOBAR.
%{FOOBAR}sThe contents of the SSL environment + variable FOOBAR, if mod_ssl is enabled.
+ +

Note

+

The %s format specifier is only available in + Apache 2.1 and later; it can be used instead of %e + to avoid the overhead of enabling SSLOptions + +StdEnvVars. If SSLOptions +StdEnvVars must + be enabled anyway for some other reason, %e will be + more efficient than %s.

+
+ +

The Header directive may be followed by an + an additional argument, which may be used to specify conditions under + which the action will be taken, or may be the keyword early + to specify early processing. If the + environment variable specified in the + env=... argument exists (or if the environment + variable does not exist and env=!... is specified) + then the action specified by the Header directive + will take effect. Otherwise, the directive will have no effect + on the request.

+ +

Except in early mode, the + Header directives are processed just + before the response is sent to the network. These means that it is + possible to set and/or override most headers, except for those headers + added by the header filter.

+ +
+
top
+

RequestHeader Directive

+ + + + + + + +
Description:Configure HTTP request headers
Syntax:RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_headers
+

This directive can replace, merge or remove HTTP request + headers. The header is modified just before the content handler + is run, allowing incoming headers to be modified. The action it + performs is determined by the first argument. This can be one + of the following values:

+ +
+
set
+
The request header is set, replacing any previous header + with this name
+ +
append
+
The request header is appended to any existing header of the + same name. When a new value is merged onto an existing header + it is separated from the existing header with a comma. This + is the HTTP standard way of giving a header multiple + values.
+ +
add
+
The request header is added to the existing set of headers, + even if this header already exists. This can result in two + (or more) headers having the same name. This can lead to + unforeseen consequences, and in general append should be + used instead.
+ +
unset
+
The request header of this name is removed, if it exists. If + there are multiple headers of the same name, all will be removed. + value must be omitted.
+
+ +

This argument is followed by a header name, which can + include the final colon, but it is not required. Case is + ignored. For add, append and + set a value is given as the third argument. If + value contains spaces, it should be surrounded by double + quotes. For unset, no value should be given. + value may be a character string, a string containing format + specifiers or a combination of both. The supported format specifiers + are the same as for the Header, + please have a look there for details.

+ +

The RequestHeader directive may be followed by + an additional argument, which may be used to specify conditions under + which the action will be taken, or may be the keyword early + to specify early processing. If the + environment + variable specified in the env=... argument + exists (or if the environment variable does not exist and + env=!... is specified) then the action specified + by the RequestHeader directive will take effect. + Otherwise, the directive will have no effect on the request.

+ +

Except in early mode, the + RequestHeader directive is processed + just before the request is run by its handler in the fixup phase. + This should allow headers generated by the browser, or by Apache + input filters to be overridden or modified.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_headers.html.ja.euc-jp b/docs/manual/mod/mod_headers.html.ja.euc-jp new file mode 100644 index 00000000..014dff88 --- /dev/null +++ b/docs/manual/mod/mod_headers.html.ja.euc-jp @@ -0,0 +1,349 @@ + + + +mod_headers - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_headers

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + + +
ÀâÌÀ:HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¤È±þÅú¤Î¥Ø¥Ã¥À¤Î¥«¥¹¥¿¥Þ¥¤¥º
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:headers_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_headers.c
¸ß´¹À­:RequestHeader +¤Ï Apache 2.0 °Ê¹ß¤Î¤ß¤Ç»ÈÍѲÄǽ
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï HTTP ¤Î¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤È±þÅú¥Ø¥Ã¥À¤òÀ©¸æ¤·¡¢ + Êѹ¹¤¹¤ë¤¿¤á¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÄ󶡤·¤Þ¤¹¡£¥Ø¥Ã¥À¤òÄɲä·¤¿¤ê¡¢ + ÃÖ¤­´¹¤¨¤¿¤ê¡¢ºï½ü¤·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

¥È¥Ô¥Ã¥¯

+
+
top
+
+

½èÍý¤Î½çÈÖ

+ +

mod_header ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥µ¡¼¥ÐÀßÄê¤Î¤Û¤Ü¤É¤³¤Ë¤Ç¤â + ½ñ¤¯¤³¤È¤¬¤Ç¤­¡¢±Æ¶Á¤¹¤ëÈϰϤòÀßÄêÍÑ¥»¥¯¥·¥ç¥ó¤Ç°Ï¤à¤³¤È¤Ç¸ÂÄꤹ¤ë + ¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

½èÍý¤Î½çÈ֤ϽÅÍפǡ¢ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î½çÈ֤ȡ¢ÀßÄêÍÑ¥»¥¯¥·¥ç¥óÆâ¤Î°ÌÃ֤ȤÎξÊý¤Ë + ±Æ¶Á¤µ¤ì¤Þ¤¹¡£°Ê²¼¤ÎÆó¤Ä¤Î¥Ø¥Ã¥À¤Ï½çÈÖ¤¬µÕ¤Ë¤Ê¤ë¤È + °ã¤¦·ë²Ì¤Ë¤Ê¤ê¤Þ¤¹:

+ +

+ RequestHeader append MirrorID "mirror 12"
+ RequestHeader unset MirrorID +

+ +

¤³¤Î½çÈ֤ξì¹ç¤Ï¡¢MirrorID ¥Ø¥Ã¥À¤ÏÀßÄꤵ¤ì¤Þ¤»¤ó¡£ + µÕ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤È¡¢MirrorID ¥Ø¥Ã¥À¤Ï "mirror 12" ¤ËÀßÄꤵ¤ì¤Þ¤¹¡£

+
top
+
+

Áá´ü½èÍý¡¢¸å´ü½èÍý

+

mod_headers ¤Ç¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤ÎÁá´ü¤«¸å´ü¤«¤Î + ¤É¤Á¤é¤ÇŬÍѤ¹¤ë¤«¤òÁª¤Ù¤Þ¤¹¡£Ä̾ï¤Ï¸å´ü¥â¡¼¥É¤Ç¡¢ + ¥³¥ó¥Æ¥ó¥ÄÀ¸À®¤¬¼Â¹Ô¤µ¤ì¤ëľÁ°¤Ë¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤¬¥»¥Ã¥È¤µ¤ì¡¢ + ¥ì¥¹¥Ý¥ó¥¹¤È¤·¤ÆÁ÷½Ð¤µ¤ì¤ëľÁ°¤Ë¥ì¥¹¥Ý¥ó¥¹¥Ø¥Ã¥À¤¬¥»¥Ã¥È¤µ¤ì¤Þ¤¹¡£ + ±¿ÍÑÃæ¤Î¥µ¡¼¥Ð¤Ç¤Ïɬ¤º¸å´ü¥â¡¼¥É¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£

+ +

Áá´ü¥â¡¼¥É¤Ï³«È¯¼Ô¸þ¤±¤Î¥Æ¥¹¥È/¥Ç¥Ð¥Ã¥°ÍѤËÀ߷פµ¤ì¤Æ¤¤¤Þ¤¹¡£ + early ¥­¡¼¥ï¡¼¥É»ØÄꤵ¤ì¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤Ã¤Æ¡¢ + ¥ê¥¯¥¨¥¹¥È½èÍý¤Î³«»ÏÃÏÅÀ¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤Ä¤Þ¤ê¡¢°Û¤Ê¤ë¥ê¥¯¥¨¥¹¥È¤ò»î¤·¤¿¤ê¥Æ¥¹¥È¥±¡¼¥¹¤ò¥»¥Ã¥È¥¢¥Ã¥×¤¹¤ë¤Î¤Ë + ³èÍѤǤ­¤ë°ìÊý¤Ç¡¢¥ì¥¹¥Ý¥ó¥¹¤òÀ¸À®¤¹¤ëÁ°¤Ë¾¤Î¥â¥¸¥å¡¼¥ë¤Ë¤è¤Ã¤Æ + ¥Ø¥Ã¥À¤¬½ñ¤­´¹¤¨¤é¤ì¤Æ¤·¤Þ¤¦¤«¤â¤·¤ì¤Ê¤¤¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£

+ +

early ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï¥ê¥¯¥¨¥¹¥È¥Ñ¥¹¤ÎÀßÄ꤬²ò·è¤µ¤ì¤ëÁ°¤Ë + ½èÍý¤µ¤ì¤ë¤Î¤Ç¡¢¥á¥¤¥ó¥µ¡¼¥Ð¤«¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¥³¥ó¥Æ¥­¥¹¥È¤Ç¤Î¤ß¡¢ + Áá´ü¥Ø¥Ã¥À¤ò¥»¥Ã¥È¤Ç¤­¤Þ¤¹¡£early ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥ê¥¯¥¨¥¹¥È¥Ñ¥¹¤Ë + °Í¸¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¤Î¤Ç¡¢<Directory> ¤ä + <Location> ¤È¤¤¤Ã¤¿¥³¥ó¥Æ¥­¥¹¥ÈÆâ¤Ç¤Ï»ÈÍÑ + ¤Ç¤­¤Þ¤»¤ó¡£

+
top
+
+

Îã

+ +
    +
  1. ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥ÀÃæ¤Î "TS" ¤Ç»Ï¤Þ¤ë¥Õ¥£¡¼¥ë¥É¤ò¤¹¤Ù¤Æ±þÅú¥Ø¥Ã¥À¤Ë + ¥³¥Ô¡¼¤·¤Þ¤¹: +

    + Header echo ^TS +

    +
    2. + +
  2. + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤¿»þ¹ï¤È¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤·¤¿»þ´Ö¤òÆþ¤ì¤¿¥Ø¥Ã¥À¡¢ + MyHeader ¤ò±þÅú¤ËÄɲä·¤Þ¤¹¡£¤³¤Î¥Ø¥Ã¥À¤Ï¥¯¥é¥¤¥¢¥ó¥È¤¬ + ¥µ¡¼¥Ð¤ÎÉé²Ù¤òľ´ÑŪ¤ËÃΤ뤿¤á¤ä¡¢¥¯¥é¥¤¥¢¥ó¥È-¥µ¡¼¥Ð´Ö¤Î + ¥Ü¥È¥ë¥Í¥Ã¥¯¤òÄ´¤Ù¤ë¤¿¤á¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + +

    + Header add MyHeader "%D %t" +

    + +

    ¾åµ­¤ÎÀßÄê¤Ç¤Ï¡¢°Ê²¼¤Î¤è¤¦¤Ê¥Ø¥Ã¥À¤¬±þÅú¤ËÄɲ䵤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹:

    + +

    + MyHeader: D=3775428 t=991424704447256 +

    +
    3. + +
  3. + Joe ¤Ë¤¢¤¤¤µ¤Ä¤ò¤·¤Þ¤¹: + +

    + Header add MyHeader "Hello Joe. It took %D microseconds for Apache to serve this request." +

    + +

    °Ê²¼¤Î¤è¤¦¤Ê¥Ø¥Ã¥À¤¬±þÅú¤ËÄɲ䵤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹

    + +

    + MyHeader: Hello Joe. It took D=3775428 microseconds for Apache to serve this request. +

    +
    4. + +
  4. ¥ê¥¯¥¨¥¹¥È¤Ë "MyRequestHeader" ¤¬¤¢¤ë¤È¤­¤Ë¸Â¤ê MyHeader ¤ò±þÅú¤Ë + ÉÕ¤±¤Þ¤¹¡£¤³¤ì¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÎÍ×µá¤Ë±þ¤¨¤Æ¥Ø¥Ã¥À¤òºîÀ®¤¹¤ë¤È¤­¤Ë + Ìò¤ËΩ¤Á¤Þ¤¹¡£¤³¤ÎÎã¤Ç¤Ï mod_setenvif ¥â¥¸¥å¡¼¥ë¤¬É¬Íפʤ³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + +

    + SetEnvIf MyRequestHeader value HAVE_MyRequestHeader
    + Header add MyHeader "%D %t mytext" env=HAVE_MyRequestHeader +

    + +

    ¤â¤· HTTP ¥ê¥¯¥¨¥¹¥È¤Ë MyRequestHeader: value ¥Ø¥Ã¥À¤¬ + ¤¢¤ë¤È¡¢±þÅú¤Ë¤Ï°Ê²¼¤Î¤è¤¦¤Ê¥Ø¥Ã¥À¤¬Éղ䵤ì¤Þ¤¹¡£

    + +

    + MyHeader: D=3775428 t=991424704447256 mytext +

    +
    5. +
+
+
top
+

Header ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:HTTP ±þÅú¥Ø¥Ã¥À¤ÎÀßÄê
¹½Ê¸:Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_headers
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï HTTP ±þÅú¥Ø¥Ã¥À¤òÃÖ´¹¡¢Äɲᢺï½ü¤Ç¤­¤Þ¤¹¡£ + ¥Ø¥Ã¥À¤Ï¥³¥ó¥Æ¥ó¥È¥Ï¥ó¥É¥é¤ä½ÐÎÏ¥Õ¥£¥ë¥¿¤¬¼Â¹Ô¤µ¤ì¤¿Ä¾¸å¤Ë¼Â¹Ô¤µ¤ì¡¢ + ½Ð¤Æ¹Ô¤¯¥Ø¥Ã¥À¤òÊѹ¹¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

¥ª¥×¥·¥ç¥ó¤Î condition ¤Ï onsuccess ¤« + always ¤Î¤É¤Á¤é¤«¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£¤³¤ì¤ÏÆâÉô¥Ø¥Ã¥À¥Æ¡¼¥Ö¥ë¤Î¤É¤ì¤ò + Áàºî¤¹¤ë¤«¤ò·èÄꤷ¤Þ¤¹¡£onsuccess ¤Ï 2xx + ¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤Î¡¢always ¤ÏÁ´¤Æ¤Î¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É + (2xx ¤ò´Þ¤à) ¤Î°ÕÌ£¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤¢¤ë¥â¥¸¥å¡¼¥ë¤Ç¥»¥Ã¥È¤µ¤ì¤ë¥Ø¥Ã¥À¤ò¥¢¥ó¥»¥Ã¥È¤·¤¿¤¤¾ì¹ç¤ÏÆäˡ¢ + ¤É¤Î¥Æ¡¼¥Ö¥ë¤¬±Æ¶Á¤ò¼õ¤±¤ë¤«¤ò¼ÂºÝ¤Ë»î¤·¤¿¤Û¤¦¤¬¤è¤¤¤Ç¤·¤ç¤¦¡£

+ +

¹Ô¤Ê¤¦½èÍý¤ÏÆóÈÖÌܤΤΰú¿ô¤Ç·è¤Þ¤ê¤Þ¤¹¡£ + ¤³¤Î°ú¿ô¤Ë¤Ï¼¡¤ÎÃͤò»ØÄê¤Ç¤­¤Þ¤¹:

+ +
+
set
+
±þÅú¥Ø¥Ã¥À¤òÀßÄꤷ¤Þ¤¹¡£Æ±¤¸Ì¾Á°¤Î¥Ø¥Ã¥À¤¬Â¸ºß¤¹¤ë¾ì¹ç¤Ï¤½¤ì¤ò + ÃÖ¤­´¹¤¨¤Þ¤¹¡£value ¤Ë¤Ï¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤ò + »ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
+ +
append
+
±þÅú¥Ø¥Ã¥À¤ò´û¤Ë¸ºß¤¹¤ëƱ¤¸Ì¾Á°¤Î¥Ø¥Ã¥À¤ËÄɲä·¤Þ¤¹¡£ + ¿·¤·¤¤Ãͤ¬´û¸¤Î¥Ø¥Ã¥À¤ËÄɲ䵤ì¤ë¤È¤­¤Ë¤Ï¡¢´û¸¤Î¥Ø¥Ã¥À¤Î + ¸å¤Ë¥³¥ó¥Þ¤Ç¶èÀÚ¤é¤ì¤ÆÄɲ䵤ì¤Þ¤¹¡£¤³¤ì¤Ï¥Ø¥Ã¥À¤ËÊ£¿ô¤ÎÃͤò + »ØÄꤹ¤ë¤È¤­¤Î HTTP ¤Îɸ½à¤ÎÊýË¡¤Ç¤¹¡£
+ +
add
+
¥Ø¥Ã¥À¤¬´û¤Ë¸ºß¤·¤Æ¤¤¤ë¤È¤­¤Ç¤µ¤¨¤â¡¢±þÅú¥Ø¥Ã¥À¤ò + ´û¸¤Î¥Ø¥Ã¥À¤ËÄɲä·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢Æó¤Ä (¤«¤½¤ì°Ê¾å) ¤Î + ¥Ø¥Ã¥À¤Î̾Á°¤¬Æ±¤¸¤Ë¤Ê¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£¤½¤Î·ë²Ì¡¢ÁÛÄê¤Ç¤­¤Ê¤¤ + ¤³¤È¤¬µ¯¤³¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢°ìÈÌŪ¤Ë¤Ï append ¤ÎÊý¤ò + »È¤¦Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£
+ +
unset
+
¤â¤·»ØÄꤵ¤ì¤¿Ì¾Á°¤Î±þÅú¥Ø¥Ã¥À¤¬Â¸ºß¤·¤Æ¤¤¤ì¤Ð¡¢ºï½ü¤µ¤ì¤Þ¤¹¡£ + Ʊ¤¸Ì¾Á°¤Î¥Ø¥Ã¥À¤¬Ê£¿ô¤¢¤ë¤È¤­¤Ï¡¢¤¹¤Ù¤Æºï½ü¤µ¤ì¤Þ¤¹¡£ + value ¤ò¤Ä¤±¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
+ +
echo
+
»ØÄꤵ¤ì¤¿¤â¤Î¤ÈƱ¤¸Ì¾Á°¤Î¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤ò±þÅú¥Ø¥Ã¥À¤Ç + ¤½¤Î¤Þ¤ÞÊÖ¤·¤Þ¤¹¡£header ¤Ë¤ÏÀµµ¬É½¸½¤â»ØÄê¤Ç¤­¤Þ¤¹¡£ + value ¤ò¤Ä¤±¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
+
+ +

¤³¤Î°ú¿ô¤Î¸å¤Ë¤Ï¥Ø¥Ã¥À̾ (header) ¤¬Â³¤­¤Þ¤¹¡£ + ¥Ø¥Ã¥À̾¤Ë¤ÏºÇ¸å¤Ë¥³¥í¥ó¤ò´Þ¤á¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¤¬¡¢Ìµ¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£ + set, append, add, + unset ¤Ç¤ÏÂçʸ»ú¾®Ê¸»ú¤Ï + ¶èÊ̤µ¤ì¤Þ¤»¤ó¡£echo ¤Î header ̾¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¡¢ + Àµµ¬É½¸½¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

add, append, + set ¤Ç¤Ï value ¤ò»°¤ÄÌܤΠ+ °ú¿ô¤È¤·¤Æ»ØÄꤷ¤Þ¤¹¡£value ¤Ë¶õÇò¤¬¤¢¤ë¾ì¹ç¤ÏÆó½Å°úÍÑÉä¤Ç + °Ï¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£value ¤Ïʸ»ú¤Î¤ß¤«¤é¤Ê¤ëʸ»úÎó¡¢ + ¥Õ¥©¡¼¥Þ¥Ã¥È»Ø¼¨»Ò¤ò´Þ¤àʸ»úÎ󡢤⤷¤¯¤ÏξÊý¤«¤é¤Ê¤ëʸ»úÎó¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£ + value ¤Ï°Ê²¼¤Î¥Õ¥©¡¼¥Þ¥Ã¥È»Ø¼¨»Ò¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹:

+ + + + + + + + + + + + +
¥Õ¥©¡¼¥Þ¥Ã¥È²òÀâ
%%¥Ñ¡¼¥»¥ó¥Èµ­¹æ
%t¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤Ã¤¿»þ¹ï¤ò¡¢ + Universal Coordinated Time ¤Ç¤Î»Ï¤Þ¤ê¤Î»þ¹ï (Jan. 1, 1970) ¤«¤é·Ð²á¤·¤¿ + »þ´Ö¤ò¥Þ¥¤¥¯¥íÉäȤ·¤Æ¸½¤·¤¿¤â¤Î¡£Ãͤκǽé¤Ë¤Ï + t= ¤¬Éղ䵤ì¤Þ¤¹¡£
%D¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤Ã¤¿»þ¹ï¤È¡¢¥Ø¥Ã¥À¤òÁ÷¤ê½Ð¤·¤¿ + »þ´Ö¤È¤Îº¹¡£¤³¤ì¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤¬Â¸ºß¤·¤Æ¤¤¤¿´ü´Ö¤ò¸½¤·¤Þ¤¹¡£ + Ãͤκǽé¤Ë¤Ï D= ¤¬Éղ䵤ì¤Þ¤¹¡£
%{FOOBAR}e´Ä¶­ÊÑ¿ô + FOOBAR ¤ÎÃͤǤ¹¡£
%{FOOBAR}smod_ssl ¤¬Í­¸ú¤Ê¾ì¹ç¡¢ + SSL ´Ä¶­ÊÑ¿ô FOOBAR + ¤ÎÆâÍÆ
+ +

Ãí

+

%s ¥Õ¥©¡¼¥Þ¥Ã¥È»ØÄê»Ò¤Ï 2.1 °Ê¹ß¤Ç¤Î¤ßÍøÍѤǤ­¤Þ¤¹¡£ + SSLOptions +StdEnvVars ¤òÍ­¸ú¤Ë¤¹¤ë¤³¤È¤Ë¤è¤ë¥ª¡¼¥Ð¡¼¥Ø¥Ã¥É¤ò + Èò¤±¤ë¤¿¤á¡¢%e ¤ÎÂå¤ï¤ê¤È¤·¤Æ»È¤¨¤Þ¤¹¡£ + ¾¤ÎÍýͳ¤Ê¤É¤¬¤¢¤Ã¤Æ¡¢¤É¤¦¤·¤Æ¤â SSLOptions +StdEnvVars + ¤òÍ­¸ú¤Ë¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¾ì¹ç¤Ï¡¢%e ¤Î¤Û¤¦¤¬ + %s ¤è¤ê¤â½èÍý¸úΨ¤ÏÎɤ¤¤Ç¤¹¡£

+
+ +

Header ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤ÏÄɲäΰú¿ô¤ò»ý¤¿¤»¤ë¤³¤È¤¬ + ¤Ç¤­¤Æ¡¢¤É¤¦¤¤¤Ã¤¿¥¢¥¯¥·¥ç¥ó¤¬¹Ô¤ï¤ì¤¿¤«¤Î¾ò·ï¤ò»ØÄꤷ¤¿¤ê¡¢ + Áá´ü½èÍý ¤ò»ØÄꤹ¤ë early ¥­¡¼¥ï¡¼¥É¤ò + »ØÄê¤Ç¤­¤Þ¤¹¡£ + env=... °ú¿ô¤Ç»ØÄꤵ¤ì¤¿ ´Ä¶­ÊÑ¿ô ¤¬Â¸ºß¤¹¤ë (¤â¤·¤¯¤Ï env=!... + ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Æ´Ä¶­ÊÑ¿ô¤¬Â¸ºß¤·¤Ê¤¤) ¾ì¹ç¤Ï¡¢Header + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿Æ°ºî¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤½¤Î¥ê¥¯¥¨¥¹¥È¤Ë¤Ï²¿¤â¤·¤Þ¤»¤ó¡£

+ +

Áá´ü½èÍý¥â¡¼¥É¤Î¾ì¹ç°Ê³°¤Ç¤Ï¡¢ + Header + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï±þÅú¤¬¥Í¥Ã¥È¥ï¡¼¥¯¤ËÁ÷¤é¤ì¤ëľÁ°¤Ë + ½èÍý¤µ¤ì¤Þ¤¹¡£¤³¤ì¤Ï¡¢¥Ø¥Ã¥À¥Õ¥£¥ë¥¿¤Ë¤è¤êÄɲ䵤ì¤ë¥Ø¥Ã¥À¤ò + ½ü¤­¡¢¤Û¤È¤ó¤É¤Î¥Ø¥Ã¥À¤òÀßÄꤷ¤¿¤ê¾å½ñ¤­¤·¤¿¤ê¤¹¤ë¤³¤È¤¬ + ²Äǽ¡¢¤È¤¤¤¦¤³¤È¤Ç¤¹¡£

+ +
+
top
+

RequestHeader ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤ÎÀßÄê
¹½Ê¸:RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_headers
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤òÃÖ´¹¡¢Äɲᢺï½ü¤Ç¤­¤Þ¤¹¡£ + ¥Ø¥Ã¥À¤Ï¥³¥ó¥Æ¥ó¥È¥Ï¥ó¥É¥é¤¬¼Â¹Ô¤µ¤ì¤ëľÁ°¤Ë¼Â¹Ô¤µ¤ì¡¢ + Æþ¤Ã¤ÆÍè¤ë¥Ø¥Ã¥À¤òÊѹ¹¤¹¤ë¤³¤È¤¬²Äǽ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¹Ô¤Ê¤¦½èÍý¤ÏÂè 1 °ú¿ô¤Ë¤è¤ê·è¤Þ¤ê¤Þ¤¹¡£¤³¤ì¤Ë¤Ï°Ê²¼¤ÎÃͤò»ØÄê + ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +
+
set
+
¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤òÀßÄꤷ¤Þ¤¹¡£Æ±¤¸Ì¾Á°¤Î¥Ø¥Ã¥À¤¬Â¸ºß¤·¤Æ¤¤¤ë¤È¡¢ + ¤½¤ì¤òÃÖ¤­´¹¤¨¤Þ¤¹¡£
+ +
append
+
¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Ï¡¢´û¤Ë¸ºß¤¹¤ëƱ¤¸Ì¾Á°¤Î¥Ø¥Ã¥À¤ËÄɲ䵤ì¤Þ¤¹¡£ + ¿·¤·¤¤Ãͤ¬´û¸¤Î¥Ø¥Ã¥À¤ËÄɲ䵤ì¤ë¤È¤­¤Ë¤Ï¡¢´û¸¤Î¥Ø¥Ã¥À¤Î + ¸å¤Ë¥³¥ó¥Þ¤Ç¶èÀÚ¤é¤ì¤ÆÄɲ䵤ì¤Þ¤¹¡£¤³¤ì¤Ï¥Ø¥Ã¥À¤ËÊ£¿ô¤ÎÃͤò + »ØÄꤹ¤ë¤È¤­¤Î HTTP ¤Îɸ½à¤ÎÊýË¡¤Ç¤¹¡£
+ +
add
+
¥Ø¥Ã¥À¤¬´û¤Ë¸ºß¤·¤Æ¤¤¤ë¤È¤­¤Ç¤µ¤¨¤â¡¢¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤ò + ´û¸¤Î¥Ø¥Ã¥À¤ËÄɲä·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢Æó¤Ä (¤«¤½¤ì°Ê¾å) ¤Î + ¥Ø¥Ã¥À¤Î̾Á°¤¬Æ±¤¸¤Ë¤Ê¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£¤½¤Î·ë²Ì¡¢ÁÛÄê¤Ç¤­¤Ê¤¤ + ¤³¤È¤¬µ¯¤³¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢°ìÈÌŪ¤Ë¤Ï append ¤ÎÊý¤ò + »È¤¦Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£
+ +
unset
+
¤â¤·»ØÄꤵ¤ì¤¿Ì¾Á°¤Î¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤¬Â¸ºß¤·¤Æ¤¤¤ì¤Ð¡¢ºï½ü¤µ¤ì¤Þ¤¹¡£ + Ʊ¤¸Ì¾Á°¤ÎÊ£¿ô¤Î¥Ø¥Ã¥À¤¬¤¢¤ë¤È¤­¤Ï¡¢¤¹¤Ù¤Æºï½ü¤µ¤ì¤Þ¤¹¡£ + value ¤ò¤Ä¤±¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£
+
+ +

¤³¤Î°ú¿ô¤Î¸å¤Ë¤Ï¥Ø¥Ã¥À̾ (header) ¤¬Â³¤­¤Þ¤¹¡£ + ¥Ø¥Ã¥À̾¤Ë¤ÏºÇ¸å¤Ë¥³¥í¥ó¤ò´Þ¤á¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¤¬¡¢Ìµ¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£ + Âçʸ»ú¾®Ê¸»ú¤Ï¶èÊ̤µ¤ì¤Þ¤»¤ó¡£add, + append, set ¤Î¾ì¹ç¤Ï¡¢value ¤¬»°¤ÄÌܤΠ+ °ú¿ô¤È¤·¤Æ»ØÄꤵ¤ì¤Þ¤¹¡£value ¤Ë¶õÇò¤¬¤¢¤ë¾ì¹ç¤ÏÆó½Å°úÍÑÉä¤Ç + °Ï¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£unset ¤Î¾ì¹ç¤Ï¡¢value ¤Ï»ØÄꤷ¤Þ¤»¤ó¡£ + value ¤Ïʸ»úÎó¡¢¥Õ¥©¡¼¥Þ¥Ã¥È»ØÄê»Ò¡¢¤¢¤ë¤¤¤Ï¡¢¤½¤Îº®¹ç¤Ç¤¹¡£ + »È¤¦¤³¤È¤Î¤Ç¤­¤ë¥Õ¥©¡¼¥Þ¥Ã¥È»ØÄê»Ò¤Ï¡¢Header ¤ÈƱ¤¸¤Ç¤¹¤Î¤Ç¡¢ + ¾ÜºÙ¤Ï¤½¤Á¤é¤ò¤´Í÷¤¯¤À¤µ¤¤¡£

+ +

RequestHeader ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¤É¤¦¤¤¤Ã¤¿¾ò·ï²¼¤Ç¥¢¥¯¥·¥ç¥ó¤ò¹Ô¤¦¤«¤ò»ØÄꤹ¤ëÄɲðú¿ô + ¤¢¤ë¤¤¤Ï¡¢Áá´ü½èÍý ¤ò»ØÄꤹ¤ë early + ¥­¡¼¥ï¡¼¥É¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + env=... ¤Î°ú¿ô¤ÇÀßÄꤵ¤ì¤Æ¤¤¤ë + ´Ä¶­ÊÑ¿ô ¤¬Â¸ºß¤·¤Æ¤¤¤ë + (¤¢¤ë¤¤¤Ï env=!... ¤Ç»ØÄꤵ¤ì¤¿´Ä¶­ÊÑ¿ô¤¬ + ¸ºß¤·¤Ê¤¤) ¾ì¹ç¡¢RequestHeader ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£¤½¤ì°Ê³°¤Î¾ì¹ç¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¸úÎϤò»ý¤Á¤Þ¤»¤ó¡£

+ +

early ¥â¡¼¥É¤Ç¤Ê¤¤¾ì¹ç¤Ë¸Â¤ê¡¢ + RequestHeader ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + fixup ¥Õ¥§¡¼¥º¤Ç¥ê¥¯¥¨¥¹¥È¤¬¥Ï¥ó¥É¥é¤Ë°·¤ï¤ì¤ëľÁ°¤Ë + ½èÍý¤µ¤ì¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢¥Ö¥é¥¦¥¶¤ä Apache ¤ÎÆþÎÏ¥Õ¥£¥ë¥¿¤Ë¤è¤ê + À¸À®¤µ¤ì¤¿¥Ø¥Ã¥À¤ò¾å½ñ¤­¤·¤¿¤ê½¤Àµ¤·¤¿¤ê¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_headers.html.ko.euc-kr b/docs/manual/mod/mod_headers.html.ko.euc-kr new file mode 100644 index 00000000..c01f739e --- /dev/null +++ b/docs/manual/mod/mod_headers.html.ko.euc-kr @@ -0,0 +1,339 @@ + + + +mod_headers - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_headers

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:HTTP ¿äû Çì´õ¿Í ÀÀ´ä Çì´õ ¼öÁ¤
»óÅÂ:Extension
¸ðµâ¸í:headers_module
¼Ò½ºÆÄÀÏ:mod_headers.c
Áö¿ø:RequestHeader´Â ¾ÆÆÄÄ¡ 2.0¿¡¸¸ +ÀÖ´Ù
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº HTTP ¿äû Çì´õ¿Í ÀÀ´ä Çì´õ¸¦ Á¶ÀýÇÏ°í ¼öÁ¤ÇÏ´Â + Áö½Ã¾îµéÀ» Á¦°øÇÑ´Ù. Çì´õ¸¦ ÇÕÄ¡°Å³ª ´ëü, Á¦°ÅÇÒ ¼ö ÀÖ´Ù.

+
+ +
top
+
+

ó¸® ¼ø¼­

+ +

mod_headers°¡ Á¦°øÇÏ´Â Áö½Ã¾î´Â ¼­¹ö¼³Á¤ÀÇ + °ÅÀÇ ¸ðµç Àå¼Ò¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖÀ¸¸ç, ¼³Á¤ ¼½¼ÇÀ¸·Î °¨½Î¼­ Áö½Ã¾îÀÇ + ¹üÀ§¸¦ Á¦ÇÑÇÒ ¼öµµ ÀÖ´Ù.

+ +

󸮼ø¼­´Â Áß¿äÇϸç, ¼³Á¤ÆÄÀÏ¿¡ ³ª¿Â ¼ø¼­¿Í ¼³Á¤ ¼½¼ÇÀÇ ¿µÇâÀ» ¹Þ´Â´Ù. + ´ÙÀ½ µÎ Áö½Ã¾î¸¦ ¹Ý´ë·Î ÀûÀ¸¸é È¿°ú°¡ ´Þ¶óÁø´Ù.

+ +

+ RequestHeader append MirrorID "mirror 12"
+ RequestHeader unset MirrorID +

+ +

À§¿Í °°ÀÌ ÀûÀ¸¸é MirrorID Çì´õ°¡ ³ª¿ÀÁö + ¾Ê´Â´Ù. ¹Ý´ë·Î ÀûÀ¸¸é MirrorID Çì´õ¸¦ "mirror 12"·Î ¼³Á¤ÇÑ´Ù.

+
top
+
+

À̸¥(early) ó¸®¿Í ´ÊÀº(late) ó¸®

+

mod_headers¸¦ ¿äû Ãʱ⳪ ³ªÁß¿¡ Àû¿ëÇÒ + ¼ö ÀÖ´Ù. º¸ÅëÀº ³»¿ë»ý¼ºÀÚ¸¦ ½ÇÇàÇϱâ Á÷Àü¿¡ ¿äû Çì´õ¸¦ + ¼³Á¤ÇÏ°í ÀÀ´äÀ» ³×Æ®¿÷¿¡ ¾µ¶§ ÀÀ´ä Çì´õ¸¦ ¼³Á¤ÇÏ´Â ´ÊÀº(late) + ¹æ½ÄÀ» »ç¿ëÇÑ´Ù. ½ÇÁ¦ ¼­ºñ½ºÇÏ´Â ¼­¹ö¿¡¼­´Â Ç×»ó ´À¸° ¹æ½ÄÀ» + »ç¿ëÇ϶ó.

+ +

À̸¥(early) ¹æ½ÄÀº °³¹ßÀÚ¸¦ À§ÇØ °Ë»ç/µð¹ö±ë¿ëÀ¸·Î ¸¸µé¾ú´Ù. + early Å°¿öµå¸¦ »ç¿ëÇÏ¿© Á¤ÀÇÇÑ Áö½Ã¾î´Â ¿äûÀ» + ó¸®Çϱ⠽ÃÀÛÇÒ¶§ ¼³Á¤ÇÑ´Ù. Áï, ´Ù¸¥ ¿äûÀ» ¸ðÀǽÇÇèÇϰųª + °Ë»ç¸¦ ÇϱâÀ§ÇØ »ç¿ëÇÒ ¼ö ÀÖÁö¸¸, ÀÀ´äÀ» »ý¼ºÇϱâ Àü¿¡ ´Ù¸¥ + ¸ðµâÀÌ ºÒ½Ã¿¡ Çì´õ¸¦ ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +

¿äû°æ·Î¿¡ ´ëÇÑ ¼³Á¤À» »ìÆ캸±â Àü¿¡ À̸¥ Áö½Ã¾î¸¦ + ó¸®Çϱ⶧¹®¿¡ À̸¥ Çì´õ Áö½Ã¾î´Â ÁÖ¼­¹öÀ̳ª °¡»óÈ£½ºÆ® + »ç¿ëÀå¼Ò¿¡¼­¸¸ »ç¿ëÇÒ ¼ö ÀÖ´Ù. À̸¥ Áö½Ã¾î´Â ¿äû°æ·Î¿¡ + ÀÇÁ¸ÇÒ ¼ö ¾ø±â¶§¹®¿¡ <Directory>³ª + <Location>°°Àº »ç¿ëÀå¼Ò¿¡¼­ »ç¿ëÇÒ ¼ö + ¾ø´Ù.

+
top
+
+

¿¹Á¦

+ +
    +
  1. + "TS"·Î ½ÃÀÛÇÏ´Â ¸ðµç ¿äû Çì´õ¸¦ ÀÀ´ä Çì´õ·Î º¹»çÇÑ´Ù. + +

    + Header echo ^TS +

    +
    2. + +
  2. + ÀÀ´ä¿¡ ¿äûÀ» ¹ÞÀº ½Ã°£°ú ¿äûÀ» ¼­ºñ½ºÇϴµ¥ °É¸± ½Ã°£À» + ¾Ë·ÁÁÖ´Â MyHeader Çì´õ¸¦ Ãß°¡ÇÑ´Ù. Ŭ¶óÀ̾ðÆ®´Â + ÀÌ Çì´õ¸¦ º¸°í ¼­¹öÀÇ ºÎÇϸ¦ ÃßÁ¤Çϰųª Ŭ¶óÀ̾ðÆ®¿Í + ¼­¹ö°£ÀÇ º´¸ñÁ¡À» ãÀ» ¼ö ÀÖ´Ù. + +

    + Header add MyHeader "%D %t" +

    + +

    ÀÀ´ä¿¡ ´ÙÀ½°ú °°Àº Çì´õ°¡ »ý±ä´Ù.

    + +

    + MyHeader: D=3775428 t=991424704447256 +

    +
    3. + +
  3. + Joe¿¡°Ô ¾È³ç + +

    + Header add MyHeader "Hello Joe. It took %D microseconds \
    + for Apache to serve this request." +

    + +

    ÀÀ´ä¿¡ ´ÙÀ½°ú °°Àº Çì´õ°¡ »ý±ä´Ù.

    + +

    + MyHeader: Hello Joe. It took D=3775428 microseconds for Apache + to serve this request. +

    +
    4. + +
  4. + ¿äû¿¡ "MyRequestHeader" Çì´õ°¡ ÀÖ´Â °æ¿ì¿¡¸¸ ¼±ÅÃÀûÀ¸·Î + ÀÀ´ä¿¡ MyHeader¸¦ º¸³½´Ù. ƯÁ¤ Ŭ¶óÀ̾ðÆ®¿¡°Ô¸¸ + ÀÀ´ä¿¡ Çì´õ¸¦ Ãß°¡ÇÒ¶§ À¯¿ëÇÏ´Ù. ÀÌ ¿¹Á¦°¡ µ¿ÀÛÇÏ·Á¸é + mod_setenvif ¸ðµâÀÌ ÇÊ¿äÇÏ´Ù. + +

    + SetEnvIf MyRequestHeader value HAVE_MyRequestHeader
    + Header add MyHeader "%D %t mytext" env=HAVE_MyRequestHeader
    +

    + +

    HTTP ¿äû¿¡ MyRequestHeader: value Çì´õ°¡ + ÀÖ´Ù¸é, ÀÀ´ä¿¡ ´ÙÀ½°ú °°Àº Çì´õ°¡ »ý±ä´Ù.

    + +

    + MyHeader: D=3775428 t=991424704447256 mytext +

    +
    5. +
+
+
top
+

Header Áö½Ã¾î

+ + + + + + + +
¼³¸í:HTTP ÀÀ´ä Çì´õ¸¦ ±¸¼ºÇÑ´Ù
¹®¹ý:Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Extension
¸ðµâ:mod_headers
+

ÀÌ Áö½Ã¾î´Â HTTP ÀÀ´ä Çì´õ¸¦ ÇÕÄ¡°Å³ª ´ëü, Á¦°ÅÇÑ´Ù. + ³»¿ë Çڵ鷯¿Í Ãâ·Â ÇÊÅÍ°¡ ½ÇÇàÇÑ Á÷ÈÄ¿¡ Çì´õ¸¦ ¼öÁ¤Çϱ⶧¹®¿¡ + º¸³¾ Çì´õ¸¦ ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +

conditionÀº ¼±ÅÃÀûÀ¸·Î »ç¿ëÇϸç, °ªÀ¸·Î + onsuccess ȤÀº always¸¦ »ç¿ëÇÑ´Ù. + ÀÌ´Â ¾î¶² ³»ºÎ Çì´õÇ¥¿¡ µ¿ÀÛÇÒÁö¸¦ °áÁ¤ÇÑ´Ù. + onsuccess´Â 2xx »óÅÂÄڵ带 + ¶æÇÏ°í, always´Â (2xx¸¦ + Æ÷ÇÔÇÑ) ¸ðµç »óÅÂÄڵ带 ¶æÇÑ´Ù. ƯÈ÷ ¾î¶² ¸ðµâÀÌ ¼³Á¤ÇÑ + Çì´õ¸¦ ÇØÁ¦ÇÏ°í ½Í´Ù¸é, µÑÁß ¾î¶² °ÍÀ» »ç¿ëÇÒÁö Àß »ìÆìºÁ¾ß + ÇÑ´Ù.

+ +

µÎ¹ø° ¾Æ±Ô¸ÕÆ®¿¡ µû¶ó ±â´ÉÀÌ ´Ù¸£´Ù. µÎ¹ø° ¾Æ±Ô¸ÕÆ®·Î + ¾Æ·¡ °ªÁß Çϳª¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +
+
set
+
ÀÀ´ä Çì´õ¸¦ ¼³Á¤ÇÑ´Ù. °°Àº À̸§À¸·Î ÀÌ¹Ì Çì´õ°¡ ÀÖ´Ù¸é + ´ëüÇÑ´Ù. value¿¡ Çü½Ä¹®ÀÚ¿­À» »ç¿ëÇÒ ¼ö ÀÖ´Ù.
+ +
append
+
ÀÌ¹Ì Á¸ÀçÇÏ´Â °°Àº À̸§ÀÇ ÀÀ´ä Çì´õ¿¡ Ãß°¡ÇÑ´Ù. ±âÁ¸ + Çì´õ¿¡ »õ·Î¿î °ªÀ» ÇÕÄ¡¸é, ±âÁ¸ Çì´õ¿Í »õ·Î¿î °ª »çÀÌ¿¡ + ½°Ç¥¸¦ ºÙÀδÙ. ÀÌ´Â ¿©·¯ Çì´õ°ªÀ» ÁöÁ¤ÇÏ´Â HTTP Ç¥ÁØ ¹æ½ÄÀÌ´Ù.
+ +
add
+
Çì´õ°¡ ÀÌ¹Ì ÀÖ´õ¶óµµ ÀÀ´ä Çì´õ¸¦ Ãß°¡ÇÑ´Ù. ±×·¡¼­ °°Àº + À̸§ÀÇ Çì´õ°¡ µÎ°³ (ȤÀº ¸¹ÀÌ) »ý±æ ¼ö ÀÖ´Ù. ÀÌ °æ¿ì ÀÇ¿ÜÀÇ + °á°ú°¡ ¹ß»ýÇÒ ¼ö Àֱ⶧¹®¿¡ º¸Åë ´ë½Å append¸¦ + »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
unset
+
ÀÌ·± À̸§ÀÇ ÀÀ´ä Çì´õ°¡ ÀÖ´Ù¸é »èÁ¦ÇÑ´Ù. °°Àº À̸§À» + °¡Áø Çì´õ°¡ ¿©·¯°³ ÀÖ´Ù¸é ¸ðµÎ Á¦°ÅÇÑ´Ù. value´Â + ÀûÁö ¾Ê´Â´Ù.
+ +
echo
+
ÀÌ·± À̸§ÀÇ ¿äû Çì´õ¸¦ ±×´ë·Î ÀÀ´ä Çì´õ·Î º¸³½´Ù. + header¿¡ Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. + value´Â ÀûÁö ¾Ê´Â´Ù.
+
+ +

¾Æ±Ô¸ÕÆ® µÚ¿¡ header À̸§ÀÌ ³ª¿Â´Ù. Çì´õ¸í + µÚ¿¡ ÄÝ·ÐÀ» ÀûÀ» ¼ö ÀÖÁö¸¸, ¾ø¾îµµ µÈ´Ù. set, + append, add, unset¿¡¼­ + ´ë¼Ò¹®ÀÚ´Â ¹«½ÃÇÑ´Ù. echoÀÇ header + À̸§Àº ´ë¼ö¹®ÀÚ¸¦ ±¸º°ÇÏ°í Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

add, append, setÀ» + »ç¿ëÇÒ¶§´Â ¼¼¹ø° ¾Æ±Ô¸ÕÆ® value°¡ ÇÊ¿äÇÏ´Ù. + value ¾È¿¡ °ø¹éÀÌ ÀÖ´Ù¸é ½Öµû¿ÈÇ¥·Î ¹­¾î¾ß ÇÑ´Ù. + value´Â ÀÏ¹Ý ¹®ÀÚ¿­À̳ª Çü½ÄÀ» ±â¼úÇÏ´Â ¹®ÀÚ¿­À̸ç, + µÎ°¡Áö¸¦ °°ÀÌ »ç¿ëÇÒ ¼öµµ ÀÖ´Ù. value¿¡¼­ Áö¿øÇÏ´Â + Çü½Ä±â¼úÀÚ´Â ´ÙÀ½°ú °°´Ù.

+ + + + + + + + + + + + +
Çü½Ä¼³¸í
%%ÆÛ¼¾Æ® ±âÈ£
%t¿äûÀ» ¹ÞÀº ½Ã°£À» ±¹Á¦Ç¥Áؽ÷Πepoch (1970³â 1¿ù + 1ÀÏ) ÀÌÈÄ Áö³­ ¸¶ÀÌÅ©·ÎÃÊ ´ÜÀ§·Î. °ª ¾Õ¿¡ t=ÀÌ + ºÙ´Â´Ù.
%D¿äûÀ» ¹ÞÀº ½Ã°£ºÎÅÍ Çì´õ¸¦ ³×Æ®¿÷¿¡ ¾µ¶§±îÁö °É¸° + ½Ã°£. ¿äûÀÇ ±â°£À» Àé´Ù. °ª ¾Õ¿¡ D=ÀÌ + ºÙ´Â´Ù.
%{FOOBAR}eȯ°æº¯¼ö FOOBARÀÇ + ³»¿ë.
%{FOOBAR}smod_sslÀÌ µ¿ÀÛÇÑ´Ù¸é, SSL ȯ°æº¯¼ö + FOOBARÀÇ ³»¿ë.
+ +

ÁÖÀÇ

+

%s Çü½Ä Áö½ÃÀÚ´Â ¾ÆÆÄÄ¡ 2.1 ÀÌÈÄ¿¡¸¸ ÀÖ´Ù. + ÀÌ Áö½ÃÀÚ´Â SSLOptions +StdEnvVars¸¦ »ç¿ëÇÏ´Â + ºÎ´ãÀ» ´ú±âÀ§ÇØ %e ´ë½Å »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¾î¶² + ÀÌÀ¯¿¡¼­°Ç SSLOptions +StdEnvVars¸¦ »ç¿ëÇØ¾ß + ÇÑ´Ù¸é, %e´Â %s º¸´Ù ÈξÀ ´õ + È¿À²ÀûÀÌ´Ù.

+
+ +

Header Áö½Ã¾î µÚ¿¡ ÇൿÀÌ ÀϾ + Á¶°ÇÀ» Áö½ÃÇÏ´Â Ãß°¡ ¾Æ±Ô¸ÕÆ®³ª À̸¥ 󸮸¦ + ¶æÇÏ´Â Å°¿öµå early°¡ ³ª¿Ã ¼ö ÀÖ´Ù. + env=... ¾Æ±Ô¸ÕÆ®¸¦ »ç¿ëÇÑ °æ¿ì ÇØ´ç + ȯ°æº¯¼ö°¡ Á¸ÀçÇÑ´Ù¸é (ȤÀº + env=!...¿¡ ³ª¿Â ȯ°æº¯¼ö°¡ Á¸ÀçÇÏÁö + ¾Ê´Ù¸é) Header Áö½Ã¾î°¡ µ¿ÀÛÇÑ´Ù. + ±×·¸Áö ¾ÊÀ¸¸é Áö½Ã¾î´Â ¿äû¿¡ ¾Æ¹« ¿µÇâÀ» ¹ÌÄ¡Áö ¾Ê´Â´Ù.

+ +

À̸¥ ¹æ½ÄÀÌ ¾Æ´Ï¶ó¸é ÀÀ´äÀ» ³×Æ®¿÷À¸·Î + º¸³»±â Á÷Àü¿¡ Header Áö½Ã¾î¸¦ ó¸®ÇÑ´Ù. + ±×·¡¼­ Çì´õ ÇÊÅÍ°¡ Ãß°¡ÇÏ´Â Çì´õ¸¦ Á¦¿ÜÇÑ ´ëºÎºÐÀÇ Çì´õ¸¦ + ¼³Á¤Çϰųª µ¤¾î¾µ ¼ö ÀÖ´Ù.

+ +
+
top
+

RequestHeader Áö½Ã¾î

+ + + + + + + +
¼³¸í:HTTP ¿äû Çì´õ¸¦ ±¸¼ºÇÑ´Ù
¹®¹ý:RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Extension
¸ðµâ:mod_headers
+

ÀÌ Áö½Ã¾î´Â HTTP ¿äû Çì´õ¸¦ ÇÕÄ¡°Å³ª ´ëü, Á¦°ÅÇÑ´Ù. + ³»¿ë Çڵ鷯°¡ ½ÇÇàÇϱâ Á÷Àü¿¡ Çì´õ¸¦ ¼öÁ¤Çϱ⶧¹®¿¡ ¹ÞÀº + Çì´õ¸¦ ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù. ù¹ø° ¾Æ±Ô¸ÕÆ®¿¡ µû¶ó ±â´ÉÀÌ ´Ù¸£´Ù. + ù¹ø° ¾Æ±Ô¸ÕÆ®·Î ¾Æ·¡ °ªÁß Çϳª¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +
+
set
+
¿äû Çì´õ¸¦ ¼³Á¤ÇÑ´Ù. °°Àº À̸§À¸·Î ÀÌ¹Ì Çì´õ°¡ ÀÖ´Ù¸é + ´ëüÇÑ´Ù
+ +
append
+
ÀÌ¹Ì Á¸ÀçÇÏ´Â °°Àº À̸§ÀÇ ¿äû Çì´õ¿¡ Ãß°¡ÇÑ´Ù. ±âÁ¸ + Çì´õ¿¡ »õ·Î¿î °ªÀ» ÇÕÄ¡¸é, ±âÁ¸ Çì´õ¿Í »õ·Î¿î °ª »çÀÌ¿¡ + ½°Ç¥¸¦ ºÙÀδÙ. ÀÌ´Â ¿©·¯ Çì´õ°ªÀ» ÁöÁ¤ÇÏ´Â HTTP Ç¥ÁØ ¹æ½ÄÀÌ´Ù.
+ +
add
+
Çì´õ°¡ ÀÌ¹Ì ÀÖ´õ¶óµµ ¿äû Çì´õ¸¦ Ãß°¡ÇÑ´Ù. ±×·¡¼­ °°Àº + À̸§ÀÇ Çì´õ°¡ µÎ°³ (ȤÀº ¸¹ÀÌ) »ý±æ ¼ö ÀÖ´Ù. ÀÌ °æ¿ì ÀÇ¿ÜÀÇ + °á°ú°¡ ¹ß»ýÇÒ ¼ö Àֱ⶧¹®¿¡ º¸Åë ´ë½Å append¸¦ + »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
unset
+
ÀÌ·± À̸§ÀÇ ¿äû Çì´õ°¡ ÀÖ´Ù¸é »èÁ¦ÇÑ´Ù. °°Àº À̸§À» + °¡Áø Çì´õ°¡ ¿©·¯°³ ÀÖ´Ù¸é ¸ðµÎ Á¦°ÅÇÑ´Ù. value´Â + ÀûÁö ¾Ê´Â´Ù.
+
+ +

¾Æ±Ô¸ÕÆ® µÚ¿¡ Çì´õ¸íÀÌ ³ª¿Â´Ù. Çì´õ¸í µÚ¿¡ ÄÝ·ÐÀ» ÀûÀ» + ¼ö ÀÖÁö¸¸, ¾ø¾îµµ µÈ´Ù. ´ë¼Ò¹®ÀÚ´Â ¹«½ÃÇÑ´Ù. add, + append, setÀ» »ç¿ëÇÒ¶§´Â ¼¼¹ø° + ¾Æ±Ô¸ÕÆ® value°¡ ÇÊ¿äÇÏ´Ù. value ¾È¿¡ + °ø¹éÀÌ ÀÖ´Ù¸é ½Öµû¿ÈÇ¥·Î ¹­¾î¾ß ÇÑ´Ù. unsetÀ» »ç¿ëÇÒ¶§´Â + value¸¦ ÀûÀ¸¸é ¾ÈµÈ´Ù. value´Â ÀÏ¹Ý + ¹®ÀÚ¿­À̳ª Çü½ÄÀ» ±â¼úÇÏ´Â ¹®ÀÚ¿­À̸ç, µÎ°¡Áö¸¦ °°ÀÌ »ç¿ëÇÒ + ¼öµµ ÀÖ´Ù. Áö¿øÇÏ´Â Çü½Ä±â¼úÀÚ´Â Header¿Í °°À¸¹Ç·Î ÀÚ¼¼ÇÑ + ³»¿ëÀº ±×°÷À» Âü°íÇ϶ó.

+ +

RequestHeader Áö½Ã¾î µÚ¿¡ ÇൿÀÌ + ÀϾ Á¶°ÇÀ» Áö½ÃÇÏ´Â Ãß°¡ ¾Æ±Ô¸ÕÆ®³ª À̸¥ 󸮸¦ ¶æÇÏ´Â Å°¿öµå + early°¡ ³ª¿Ã ¼ö ÀÖ´Ù. env=... + ¾Æ±Ô¸ÕÆ®¸¦ »ç¿ëÇÑ °æ¿ì ÇØ´ç ȯ°æº¯¼ö°¡ + Á¸ÀçÇÑ´Ù¸é (ȤÀº env=!...¿¡ ³ª¿Â + ȯ°æº¯¼ö°¡ Á¸ÀçÇÏÁö ¾Ê´Ù¸é) RequestHeader + Áö½Ã¾î°¡ µ¿ÀÛÇÑ´Ù. ±×·¸Áö ¾ÊÀ¸¸é Áö½Ã¾î´Â ¿äû¿¡ ¾Æ¹« ¿µÇâÀ» + ¹ÌÄ¡Áö ¾Ê´Â´Ù.

+ +

À̸¥ ¹æ½ÄÀÌ ¾Æ´Ï¶ó¸é fixup ´Ü°è¿¡¼­ + ¿äû¿¡ ÇØ´çÇÏ´Â Çڵ鷯¸¦ ½ÇÇàÇϱâ Á÷Àü¿¡ + RequestHeader Áö½Ã¾î¸¦ ó¸®ÇÑ´Ù. + ±×·¡¼­ ºê¶ó¿ìÀú¿¡ µû¶ó ȤÀº ¾ÆÆÄÄ¡ ÀÔ·ÂÇÊÅÍ°¡ Çì´õ¸¦ µ¤¾î¾²°Å³ª + ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_ident.html b/docs/manual/mod/mod_ident.html new file mode 100644 index 00000000..35282bad --- /dev/null +++ b/docs/manual/mod/mod_ident.html @@ -0,0 +1,7 @@ +URI: mod_ident.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_ident.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_ident.html.en b/docs/manual/mod/mod_ident.html.en new file mode 100644 index 00000000..144becf8 --- /dev/null +++ b/docs/manual/mod/mod_ident.html.en @@ -0,0 +1,101 @@ + + + +mod_ident - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_ident

+
+

Available Languages:  en  | + ko 

+
+ + + + +
Description:RFC 1413 ident lookups
Status:Extension
Module Identifier:ident_module
Source File:mod_ident.c
Compatibility:Available in Apache 2.1 and later
+

Summary

+ +

This module queries an RFC 1413 compatible daemon on a remote host to look up the owner of + a connection.

+
+

Directives

+ +

See also

+
+ +
top
+

IdentityCheck Directive

+ + + + + + + + +
Description:Enables logging of the RFC 1413 identity of the remote +user
Syntax:IdentityCheck On|Off
Default:IdentityCheck Off
Context:server config, virtual host, directory
Status:Extension
Module:mod_ident
Compatibility:Moved out of core in Apache 2.1
+

This directive enables RFC 1413-compliant logging of the remote user name for each + connection, where the client machine runs identd or something similar. + This information is logged in the access log using the %...l + format string.

+ +
+ The information should not be trusted in any way except for + rudimentary usage tracking. +
+ +

Note that this can cause serious latency problems accessing + your server since every request requires one of these lookups + to be performed. When firewalls or proxy servers are involved, + each lookup might possibly fail and add a latency duration as + defined by the IdentityCheckTimeout directive to each hit. So in + general this is not very useful on public servers accessible from + the Internet.

+ +
+
top
+

IdentityCheckTimeout Directive

+ + + + + + + +
Description:Determines the timeout duration for ident requests
Syntax:IdentityCheckTimeout seconds
Default:IdentityCheckTimeout 30
Context:server config, virtual host, directory
Status:Extension
Module:mod_ident
+

This directive specifies the timeout duration of an ident + request. The default value of 30 seconds is recommended by RFC 1413, mainly because + of possible network latency. However, you may want to adjust the + timeout value according to your local network speed.

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_ident.html.ko.euc-kr b/docs/manual/mod/mod_ident.html.ko.euc-kr new file mode 100644 index 00000000..cf9185ad --- /dev/null +++ b/docs/manual/mod/mod_ident.html.ko.euc-kr @@ -0,0 +1,98 @@ + + + +mod_ident - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_ident

+
+

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

+
+ + + + +
¼³¸í:RFC 1413 ident °Ë»ö
»óÅÂ:Extension
¸ðµâ¸í:ident_module
¼Ò½ºÆÄÀÏ:mod_ident.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº ¿¬°áÀÇ ¼ÒÀ¯ÀÚ¸¦ ã±âÀ§ÇØ ¿ø°Ý È£½ºÆ®¿¡ ÀÖ´Â + RFC 1413 + ȣȯ µ¥¸óÀ» °Ë»öÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

IdentityCheck Áö½Ã¾î

+ + + + + + + + +
¼³¸í:¿ø°Ý »ç¿ëÀÚÀÇ RFC 1413 ½Å¿øÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù
¹®¹ý:IdentityCheck On|Off
±âº»°ª:IdentityCheck Off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory
»óÅÂ:Extension
¸ðµâ:mod_ident
Áö¿ø:¾ÆÆÄÄ¡ 2.1ºÎÅÍ core¿¡¼­ ºüÁ® ³ª¿Ô´Ù
+

ÀÌ Áö½Ã¾î´Â RFC + 1413À» ÀÌ¿ëÇÏ¿© Ŭ¶óÀ̾ðÆ® ¸Ó½®ÀÌ identd µîÀ» ½ÇÇàÇÑ´Ù¸é + ¿¬°á¿¡ ´ëÇÑ ¿ø°Ý »ç¿ëÀÚ¸íÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù. Çü½Ä¹®ÀÚ¿­·Î + %...lÀ» »ç¿ëÇÏ¿© Á¢±Ù ·Î±×¿¡ ÀÌ Á¤º¸¸¦ ±â·ÏÇÑ´Ù.

+ +
+ ±âº»ÀûÀÎ »ç¿ëÃßÀû ¿ÜÀÇ ¿ëµµ·Î ÀÌ Á¤º¸¸¦ ½Å·ÚÇÒ ¼ö ¾ø´Ù. +
+ +

¿äû¸¶´Ù °Ë»öÀ» ÇØ¾ß Çϱ⶧¹®¿¡ ¼­¹ö Á¢±ÙÀÌ »ó´çÈ÷ Áö¿¬µÇ´Â + ¹®Á¦°¡ ¹ß»ýÇÒ ¼ö ÀÖÀ½À» À¯ÀÇÇ϶ó. Áß°£¿¡ ¹æÈ­º®À̳ª ÇÁ·Ï½Ã¼­¹ö°¡ + ÀÖ´Ù¸é, ¾Æ¸¶µµ °Ë»öÀº ½ÇÆÐÇÒ °ÍÀÌ°í ¸Å ¿äû¿¡ IdentityCheckTimeout Áö½Ã¾î·Î + ÁöÁ¤ÇѸ¸Å­ Áö¿¬ÀÌ ¹ß»ýÇÑ´Ù. ±×·¡¼­ º¸Åë ÀÎÅͳÝÀÇ °ø°³µÈ + ¼­¹ö¿¡¼­´Â À¯¿ëÇÏÁö ¾Ê´Ù.

+ +
+
top
+

IdentityCheckTimeout Áö½Ã¾î

+ + + + + + + +
¼³¸í:ident ¿äûÀÇ ½Ã°£Á¦ÇÑÀ» ÁöÁ¤ÇÑ´Ù
¹®¹ý:IdentityCheckTimeout seconds
±âº»°ª:IdentityCheckTimeout 30
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory
»óÅÂ:Extension
¸ðµâ:mod_ident
+

ÀÌ Áö½Ã¾î´Â ident ¿äûÀÇ ½Ã°£Á¦ÇÑÀ» ÁöÁ¤ÇÑ´Ù. ±âº»°ªÀº + ³×Æ®¿÷ Áö¿¬À» °í·ÁÇÏ¿© RFC 1413ÀÌ + ±ÇÇÏ´Â 30 ÃÊÀÌ´Ù. ±×·¯³ª ³×Æ®¿÷ ¼Óµµ »óȲ¿¡ µû¶ó ½Ã°£Á¦ÇÑ°ªÀ» + ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_imagemap.html b/docs/manual/mod/mod_imagemap.html new file mode 100644 index 00000000..b571be95 --- /dev/null +++ b/docs/manual/mod/mod_imagemap.html @@ -0,0 +1,7 @@ +URI: mod_imagemap.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_imagemap.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_imagemap.html.en b/docs/manual/mod/mod_imagemap.html.en new file mode 100644 index 00000000..854e31a6 --- /dev/null +++ b/docs/manual/mod/mod_imagemap.html.en @@ -0,0 +1,382 @@ + + + +mod_imagemap - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_imagemap

+
+

Available Languages:  en  | + ko 

+
+ + + +
Description:Server-side imagemap processing
Status:Base
Module Identifier:imagemap_module
Source File:mod_imagemap.c
+

Summary

+ +

This module processes .map files, thereby + replacing the functionality of the imagemap CGI + program. Any directory or document type configured to use the + handler imap-file (using either + AddHandler or + SetHandler) + will be processed by this module.

+ +

The following directive will activate files ending with + .map as imagemap files:

+ +

AddHandler imap-file map

+ +

Note that the following is still supported:

+ +

AddType application/x-httpd-imap map

+ +

However, we are trying to phase out "magic MIME types" so we + are deprecating this method.

+
+ +
top
+
+

New Features

+ +

The imagemap module adds some new features that were not + possible with previously distributed imagemap programs.

+ +
    +
  • URL references relative to the Referer: information.
    • + +
  • Default <base> assignment through a new map + directive base.
    • + +
  • No need for imagemap.conf file.
    • + +
  • Point references.
    • + +
  • Configurable generation of imagemap menus.
    • +
+
top
+
+

Imagemap File

+ +

The lines in the imagemap files can have one of several + formats:

+ +

+ directive value [x,y ...]
+ directive value "Menu text" [x,y + ...]
+ directive value x,y ... "Menu text" +

+ +

The directive is one of base, + default, poly, circle, + rect, or point. The value is an + absolute or relative URL, or one of the special values listed + below. The coordinates are x,y + pairs separated by whitespace. The quoted text is used as the text of + the link if a imagemap menu is generated. Lines beginning with '#' are + comments.

+ +

Imagemap File Directives

+

There are six directives allowed in the imagemap file. The + directives can come in any order, but are processed in the + order they are found in the imagemap file.

+ +
+
base Directive
+ +

Has the effect of <base href="value"> + . The non-absolute URLs of the map-file are taken relative + to this value. The base directive overrides + ImapBase as set in a + .htaccess file or in the server configuration files. + In the absence of an ImapBase configuration + directive, base defaults to + http://server_name/.

+

base_uri is synonymous with base. + Note that a trailing slash on the URL is significant.

+ +
default Directive
+ +
The action taken if the coordinates given do not fit any + of the poly, circle or + rect directives, and there are no + point directives. Defaults to nocontent + in the absence of an ImapDefault configuration setting, causing a status + code of 204 No Content to be returned. The client + should keep the same page displayed.
+ +
poly Directive
+ +
Takes three to one-hundred points, and is obeyed if the + user selected coordinates fall within the polygon defined by + these points.
+ +
circle
+ +
Takes the center coordinates of a circle and a point on + the circle. Is obeyed if the user selected point is with the + circle.
+ +
rect Directive
+ +
Takes the coordinates of two opposing corners of a + rectangle. Obeyed if the point selected is within this + rectangle.
+ +
point Directive
+ +
Takes a single point. The point directive closest to the + user selected point is obeyed if no other directives are + satisfied. Note that default will not be + followed if a point directive is present and + valid coordinates are given.
+
+ + +

Values

+ +

The values for each of the directives can any of the following:

+ +
+
a URL
+ +

The URL can be relative or absolute URL. Relative URLs + can contain '..' syntax and will be resolved relative to the + base value.

+

base itself will not resolved according to the + current value. A statement base mailto: will + work properly, though.

+ +
map
+ +
Equivalent to the URL of the imagemap file itself. No + coordinates are sent with this, so a menu will be generated + unless ImapMenu is set to + none.
+ +
menu
+
Synonymous with map.
+ +
referer
+ +
Equivalent to the URL of the referring document. Defaults + to http://servername/ if no Referer: + header was present.
+ +
nocontent
+ +
Sends a status code of 204 No Content, + telling the client to keep the same page displayed. Valid for + all but base.
+ +
error
+ +
Fails with a 500 Server Error. Valid for all + but base, but sort of silly for anything but + default.
+
+ + +

Coordinates

+ +
+
0,0 200,200
+ +
A coordinate consists of an x and a y + value separated by a comma. The coordinates are separated + from each other by whitespace. To accommodate the way Lynx + handles imagemaps, should a user select the coordinate + 0,0, it is as if no coordinate had been + selected.
+
+ + + +

Quoted Text

+ +
+
"Menu Text"
+ +

After the value or after the coordinates, the line + optionally may contain text within double quotes. This string + is used as the text for the link if a menu is + generated:

+ +

+ <a href="http://foo.com/">Menu text</a> +

+ +

If no quoted text is present, the name of the link will be + used as the text:

+ +

+ <a href="http://foo.com/">http://foo.com</a> +

+ +

If you want to use double quotes within this text, you have to + write them as &quot;.

+
+ + +
top
+
+

Example Mapfile

+ +

+ #Comments are printed in a 'formatted' or 'semiformatted' menu.
+ #And can contain html tags. <hr>
+ base referer
+ poly map "Could I have a menu, please?" 0,0 0,10 10,10 10,0
+ rect .. 0,0 77,27 "the directory of the referer"
+ circle http://www.inetnebr.com/lincoln/feedback/ 195,0 305,27
+ rect another_file "in same directory as referer" 306,0 419,27
+ point http://www.zyzzyva.com/ 100,100
+ point http://www.tripod.com/ 200,200
+ rect mailto:nate@tripod.com 100,150 200,0 "Bugs?"
+

+ +
top
+
+

Referencing your mapfile

+ +

HTML example

+ <a href="/maps/imagemap1.map">
+ + <img ismap src="/images/imagemap1.gif">
+ + </a> +

+ +

XHTML example

+ <a href="/maps/imagemap1.map">
+ + <img ismap="ismap" src="/images/imagemap1.gif" />
+ + </a> +

+ +
+
top
+

ImapBase Directive

+ + + + + + + + +
Description:Default base for imagemap files
Syntax:ImapBase map|referer|URL
Default:ImapBase http://servername/
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_imagemap
+

The ImapBase directive sets the default + base used in the imagemap files. Its value is + overridden by a base directive within the imagemap + file. If not present, the base defaults to + http://servername/.

+ +

See also

+ +
+
top
+

ImapDefault Directive

+ + + + + + + + +
Description:Default action when an imagemap is called with coordinates +that are not explicitly mapped
Syntax:ImapDefault error|nocontent|map|referer|URL
Default:ImapDefault nocontent
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_imagemap
+

The ImapDefault directive sets the default + default used in the imagemap files. Its value is + overridden by a default directive within the + imagemap file. If not present, the default action + is nocontent, which means that a 204 No + Content is sent to the client. In this case, the client + should continue to display the original page.

+ +
+
top
+

ImapMenu Directive

+ + + + + + + +
Description:Action if no coordinates are given when calling +an imagemap
Syntax:ImapMenu none|formatted|semiformatted|unformatted
Context:server config, virtual host, directory, .htaccess
Override:Indexes
Status:Base
Module:mod_imagemap
+

The ImapMenu directive determines the + action taken if an imagemap file is called without valid + coordinates.

+ +
+
none
+
If ImapMenu is none, no menu is generated, + and the default action is performed.
+ +
formatted
+
A formatted menu is the simplest menu. + Comments in the imagemap file are ignored. A level one header + is printed, then an hrule, then the links each on a separate + line. The menu has a consistent, plain look close to that of + a directory listing.
+ +
semiformatted
+
In the semiformatted menu, comments are + printed where they occur in the imagemap file. Blank lines + are turned into HTML breaks. No header or hrule is printed, + but otherwise the menu is the same as a + formatted menu.
+ +
unformatted
+
Comments are printed, blank lines are ignored. Nothing is + printed that does not appear in the imagemap file. All breaks + and headers must be included as comments in the imagemap + file. This gives you the most flexibility over the appearance + of your menus, but requires you to treat your map files as + HTML instead of plaintext.
+
+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_imagemap.html.ko.euc-kr b/docs/manual/mod/mod_imagemap.html.ko.euc-kr new file mode 100644 index 00000000..04e6ac26 --- /dev/null +++ b/docs/manual/mod/mod_imagemap.html.ko.euc-kr @@ -0,0 +1,363 @@ + + + +mod_imagemap - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_imagemap

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:¼­¹öÃø À̹ÌÁö¸Ê(imagemap) ó¸®
»óÅÂ:Base
¸ðµâ¸í:imagemap_module
¼Ò½ºÆÄÀÏ:mod_imagemap.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº imagemap CGI ÇÁ·Î±×·¥À» ´ë½ÅÇÏ¿© + .map ÆÄÀÏÀ» ó¸®ÇÑ´Ù. ÀÌ ¸ðµâÀº (AddHandler³ª SetHandler¸¦ »ç¿ëÇÏ¿©) + imap-file Çڵ鷯¸¦ »ç¿ëÇϵµ·Ï ¼³Á¤ÇÑ µð·ºÅ丮³ª + ¹®¼­¸¦ ó¸®ÇÑ´Ù.

+ +

¾Æ·¡ Áö½Ã¾î´Â .mapÀ¸·Î ³¡³ª´Â ÆÄÀÏÀ» À̹ÌÁö¸Ê + ÆÄÀÏ·Î ¼³Á¤ÇÑ´Ù.

+ +

AddHandler imap-file map

+ +

¾ÆÁ÷µµ ¾Æ·¡¿Í °°Àº ¼³Á¤À» Áö¿øÇÑ´Ù.

+ +

AddType application/x-httpd-imap map

+ +

±×·¯³ª ¿ì¸®´Â Á¡Â÷ "¼­¹ö¿¡°Ô Ưº°ÇÑ Àǹ̰¡ ÀÖ´Â MIME + type"À» Á¦°ÅÇÏ·Á°í Çϱ⶧¹®¿¡ ÀÌ ¹æ¹ýÀº ¾ø¾îÁú °ÍÀÌ´Ù.

+
+ +
top
+
+

»õ·Î¿î ±â´É

+ +

À̹ÌÁö¸Ê ¸ðµâ¿¡´Â ÀÌÀü À̹ÌÁö¸Ê ÇÁ·Î±×·¥¿¡´Â ¾ø´Â ¸î°¡Áö + »õ·Î¿î ±â´ÉÀÌ ÀÖ´Ù.

+ +
    +
  • Referer: Á¤º¸¿¡ »ó´ëÀûÀÎ URL ÂüÁ¶.
    • + +
  • »õ·Î¿î base ¸ÊÁö½Ã¾î¸¦ »ç¿ëÇÏ¿© ±âº» + <base> ÁöÁ¤.
    • + +
  • imagemap.conf ÆÄÀÏ ÇÊ¿ä¾øÀ½.
    • + +
  • Á¡(point) ÂüÁ¶.
    • + +
  • À̹ÌÁö¸Ê ¸Þ´º Á¶Á¤ °¡´É.
    • +
+
top
+
+

À̹ÌÁö¸Ê ÆÄÀÏ

+ +

À̹ÌÁö¸Ê ÆÄÀÏÀº ¾Æ·¡¿Í °°Àº Çü½ÄÀ¸·Î ÀÛ¼ºÇÑ´Ù.

+ +

+ directive value [x,y ...]
+ directive value "Menu text" [x,y + ...]
+ directive value x,y ... "Menu text" +

+ +

directive´Â base, default, + poly, circle, rect, + point Áß Çϳª´Ù. value¿¡´Â Àý´ë URLÀ̳ª »ó´ë + URL ȤÀº ¾Æ·¡¿¡¼­ ¿­°ÅÇÒ Æ¯¼ö°ªÀ» »ç¿ëÇÑ´Ù. ÁÂÇ¥´Â °ø¹éÀ¸·Î + ±¸ºÐÇÑ x,y ½ÖÀÌ´Ù. µû¿ÈÇ¥·Î + ¹­Àº ¹®±¸´Â À̹ÌÁö¸Ê ¸Þ´º¸¦ ¸¸µé¶§ ¸µÅ© Á¦¸ñÀ¸·Î »ç¿ëÇÑ´Ù. + '#'·Î ½ÃÀÛÇÏ´Â ÁÙÀº ÁÖ¼®ÀÌ´Ù.

+ +

À̹ÌÁö¸Ê ÆÄÀÏ Áö½Ã¾î

+

À̹ÌÁö¸Ê ÆÄÀÏ¿¡¼­ 6°¡Áö Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù. Áö½Ã¾î´Â + Ưº°ÇÑ ¼ø¼­¾øÀÌ »ç¿ëÇÒ ¼ö ÀÖÁö¸¸, À̹ÌÁö¸Ê ÆÄÀÏ¿¡ ³ª¿Â + ¼ø¼­´ë·Î ó¸®ÇÑ´Ù.

+ +
+
base Áö½Ã¾î
+ +

<base href="value"> + ±â´ÉÀ» ÇÑ´Ù. ¸ÊÆÄÀÏ¿¡¼­ ³ª¿À´Â URLÀº Àý´ë URLÀÌ ¾Æ´Ï¶ó¸é + ÀÌ °ª¿¡ »ó´ë URL·Î Ãë±ÞÇÑ´Ù. base Áö½Ã¾î´Â + .htaccess ÆÄÀÏÀ̳ª ¼­¹ö¼³Á¤ÆÄÀÏ¿¡¼­ ¼³Á¤ÇÑ + ImapBase °ªÀ» + ¹«½ÃÇÑ´Ù. ImapBase ¼³Á¤Áö½Ã¾î°¡ + ¾ø´Ù¸é ±âº» base °ªÀº + http://server_name/ÀÌ´Ù.

+

base_uri´Â base¿Í °°´Ù. URL¿¡¼­ + ¸¶Áö¸· ½½·¡½¬¸¦ ÀØÁö¸¶¶ó.

+ +
default Áö½Ã¾î
+ +
ÇØ´ç ÁÂÇ¥°¡ poly, circle, + rect Áö½Ã¾î¿¡ ÇØ´çÇÏÁö ¾Ê°í point + Áö½Ã¾î¸¦ »ç¿ëÇÏÁö ¾ÊÀº °æ¿ì ÇൿÀ» ÁöÁ¤ÇÑ´Ù. ImapDefault ¼³Á¤ÀÌ ¾ø´Ù¸é + ±âº»°ªÀº 204 No Content »óÅÂÄڵ带 ¹ÝȯÇÏ´Â + nocontentÀÌ´Ù. ÀÌ °æ¿ì Ŭ¶óÀ̾ðÆ®´Â µ¿ÀÏÇÑ + ÆäÀÌÁö¸¦ º¸¿©Áà¾ß ÇÑ´Ù.
+ +
poly Áö½Ã¾î
+ +
Á¡À» ¼¼°³¿¡¼­ ¹é°³±îÁö ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù. »ç¿ëÀÚ°¡ ÀÌ + Á¡µé·Î ÀÌ·ç¾îÁø ´Ù°¢Çü ¾ÈÀÇ ÁÂÇ¥¸¦ ¼±ÅÃÇÑ °æ¿ì¿¡ »ç¿ëÇÑ´Ù.
+ +
circle
+ +
¿øÀÇ Á߽ɰú ¿øÀ§ÀÇ ÇÑ Á¡ÀÇ ÁÂÇ¥¸¦ ¹Þ´Â´Ù. »ç¿ëÀÚ°¡ + ¿ø ¾ÈÀÇ ÁÂÇ¥¸¦ ¼±ÅÃÇÑ °æ¿ì¿¡ »ç¿ëÇÑ´Ù.
+ +
rect Áö½Ã¾î
+ +
»ç°¢ÇüÀÇ µÎ ¸ð¼­¸® Á¡ÀÇ ÁÂÇ¥¸¦ ¹Þ´Â´Ù. »ç°¢Çü ¾ÈÀÇ + ÁÂÇ¥¸¦ ¼±ÅÃÇÑ °æ¿ì¿¡ »ç¿ëÇÑ´Ù.
+ +
point Áö½Ã¾î
+ +
ÇÑ Á¡ÀÇ ÁÂÇ¥¸¦ ¹Þ´Â´Ù. ´Ù¸¥ Áö½Ã¾îµéÀ» ¸¸Á·ÇÏÁö ¾ÊÀº + °æ¿ì »ç¿ëÀÚ°¡ ¼±ÅÃÇÑ ÁÂÇ¥¿¡ °¡Àå °¡±î¿î point Áö½Ã¾î¸¦ + »ç¿ëÇÑ´Ù. point Áö½Ã¾î¸¦ »ç¿ëÇÏ°í À¯È¿ÇÑ + ÁÂÇ¥¸¦ ¼±ÅÃÇÑ °æ¿ì default´Â Àý´ë·Î »ç¿ëµÇÁö + ¾Ê´Â´Ù.
+
+ + +

Áö½Ã¾î¿¡ »ç¿ëÇÒ ¼ö ÀÖ´Â °ªµé

+ +

Áö½Ã¾î¿¡ ¾Æ·¡ value¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +
+
URL
+ +

»ó´ë URLÀ̳ª Àý´ë URLÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. »ó´ë URL¿¡ + '..'À» »ç¿ëÇÒ ¼ö ÀÖÀ¸¸ç, base °ªÀ» ±âÁØÀ¸·Î + ã´Â´Ù.

+

base¸¦ ¼³Á¤ÇÒ¶§´Â ÇöÀç base°ªÀº ¹«½ÃÇÑ´Ù. + ±×·¯³ª, base mailto: ¹®Àº »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +
map
+ +
À̹ÌÁö¸Ê ÆÄÀÏ ÀÚü URL°ú °°´Ù. ÁÂÇ¥°¡ ¾ø°í ImapMenu°¡ noneÀÌ + ¾Æ´Ï¶ó¸é ¸Þ´º¸¦ ¸¸µç´Ù.
+ +
menu
+
map°ú °°´Ù.
+ +
referer
+ +
ÂüÁ¶(¸µÅ©¸¦ µû¶ó¿À±â Àü) ¹®¼­ URL°ú °°´Ù. + Referer: Çì´õ°¡ ¾ø´Ù¸é ±âº»°ªÀº + http://servername/ÀÌ´Ù.
+ +
nocontent
+ +
Ŭ¶óÀ̾ðÆ®¿¡°Ô µ¿ÀÏÇÑ ÆäÀÌÁö¸¦ ±×´ë·Î º¸¿©ÁÖ¶ó´Â + 204 No Content »óÅÂÄڵ带 º¸³½´Ù. + base¸¦ Á¦¿ÜÇÑ ¸ðµç Áö½Ã¾î¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖ´Ù.
+ +
error
+ +
½ÇÆи¦ ³ªÅ¸³»´Â 500 Server Error¸¦ º¸³½´Ù. + base¸¦ Á¦¿ÜÇÑ ¸ðµç Áö½Ã¾î¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖÁö¸¸, + default ¿Ü¿¡´Â »ç¿ëÇÒ ÀÏÀÌ ¾ø´Ù.
+
+ + +

ÁÂÇ¥

+ +
+
0,0 200,200
+ +
ÁÂÇ¥´Â ½°Ç¥·Î ±¸ºÐÇÑ x¿Í y °ªÀÌ´Ù. + ÁÂÇ¥µéÀº ¼­·Î °ø¹éÀ¸·Î ±¸ºÐÇÑ´Ù. À̹ÌÁö¸ÊÀ» ´Ù·ç´Â ¹æ½Ä»ó + LynxÀÇ ÆíÀǸ¦ À§ÇØ »ç¿ëÀÚ°¡ 0,0 ÁÂÇ¥¸¦ ¼±ÅÃÇÏ¿´´Ù¸é + ÁÂÇ¥¸¦ ¼±ÅÃÇÏÁö ¾ÊÀº °Íó·³ µ¿ÀÛÇÑ´Ù.
+
+ + + +

µû¿ÈÇ¥·Î ¹­Àº ¹®±¸

+ +
+
"Menu Text"
+ +

value µÚ³ª ÁÂÇ¥ µÚ¿¡ ½Öµû¿ÈÇ¥·Î ¹­Àº ¹®±¸¸¦ ÀûÀ» + ¼öµµ ÀÖ´Ù. ÀÌ ¹®ÀÚ¿­Àº ¸Þ´º¸¦ ¸¸µé¶§ ¸µÅ© Á¦¸ñÀ¸·Î »ç¿ëÇÑ´Ù.

+ +

+ <a href="http://foo.com/">Menu text</a> +

+ +

µû¿ÈÇ¥·Î ¹­Àº ¹®±¸°¡ ¾ø´Ù¸é ´ÙÀ½°ú °°ÀÌ ¸µÅ©¸¦ ¸µÅ© + Á¦¸ñÀ¸·Î »ç¿ëÇÑ´Ù.

+ +

+ <a href="http://foo.com/">http://foo.com</a> +

+ +

¹®±¸¿¡ ½Öµû¿ÈÇ¥¸¦ ¾²·Á¸é &quot;¿Í + °°ÀÌ Àû¾î¾ß ÇÑ´Ù.

+
+ + +
top
+
+

¸ÊÆÄÀÏ ¿¹Á¦

+ +

+ #'formatted'³ª 'semiformatted' ¸Þ´º´Â ÁÖ¼®À» Ãâ·ÂÇÑ´Ù.
+ #±×¸®°í ÁÖ¼®¿¡ html ű׸¦ ¾µ ¼ö ÀÖ´Ù. <hr>
+ base referer
+ poly map "¸Þ´º¸¦ º¸¿©ÁÖ¼¼¿ä." 0,0 0,10 10,10 10,0
+ rect .. 0,0 77,27 "ÂüÁ¶ ¹®¼­°¡ ÀÖ´Â µð·ºÅ丮"
+ circle http://www.inetnebr.com/lincoln/feedback/ 195,0 305,27
+ rect another_file "ÂüÁ¶ ¹®¼­¿Í °°Àº µð·ºÅ丮¿¡ ÀÖ´Â" 306,0 419,27
+ point http://www.zyzzyva.com/ 100,100
+ point http://www.tripod.com/ 200,200
+ rect mailto:nate@tripod.com 100,150 200,0 "¹ö±×?"
+

+ +
top
+
+

¸ÊÆÄÀÏ »ç¿ëÇϱâ

+ +

HTML ¿¡Á¦

+ <a href="/maps/imagemap1.map">
+ + <img ismap src="/images/imagemap1.gif">
+ + </a> +

+ +

XHTML ¿¹Á¦

+ <a href="/maps/imagemap1.map">
+ + <img ismap="ismap" src="/images/imagemap1.gif" />
+ + </a> +

+ +
+
top
+

ImapBase Áö½Ã¾î

+ + + + + + + + +
¼³¸í:À̹ÌÁö¸Ê ÆÄÀÏ¿¡¼­ base ±âº»°ª
¹®¹ý:ImapBase map|referer|URL
±âº»°ª:ImapBase http://servername/
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_imagemap
+

ImapBase Áö½Ã¾î´Â À̹ÌÁö¸Ê ÆÄÀÏ¿¡¼­ + »ç¿ëÇÒ base ±âº»°ªÀ» ¼³Á¤ÇÑ´Ù. À̹ÌÁö¸Ê ÆÄÀÏ + ¾È¿¡¼­ base Áö½Ã¾î¸¦ »ç¿ëÇÏ¸é ¿©±â¼­ ¼³Á¤ÇÑ + °ªÀº ¹«½ÃÇÑ´Ù. µÑ ¸ðµÎ ¾ø´Ù¸é, base ±âº»°ªÀº + http://servername/ÀÌ´Ù.

+ +

Âü°í

+ +
+
top
+

ImapDefault Áö½Ã¾î

+ + + + + + + + +
¼³¸í:À̹ÌÁö¸Ê¿¡ ¾î´À ¿µ¿ª¿¡µµ ÇØ´çÇÏÁö ¾Ê´Â ÁÂÇ¥¸¦ ÁØ +°æ¿ì ±âº» Çൿ
¹®¹ý:ImapDefault error|nocontent|map|referer|URL
±âº»°ª:ImapDefault nocontent
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_imagemap
+

ImapDefault Áö½Ã¾î´Â À̹ÌÁö¸Ê + ÆÄÀÏ¿¡¼­ »ç¿ëÇÒ default ±âº»°ªÀ» ¼³Á¤ÇÑ´Ù. + À̹ÌÁö¸Ê ÆÄÀÏ ¾È¿¡¼­ default Áö½Ã¾î¸¦ »ç¿ëÇϸé + ¿©±â¼­ ¼³Á¤ÇÑ °ªÀº ¹«½ÃÇÑ´Ù. µÑ ¸ðµÎ ¾ø´Ù¸é, default + ÇൿÀº Ŭ¶óÀ̾ðÆ®¿¡°Ô 204 No Content¸¦ º¸³»´Â + nocontentÀÌ´Ù. ÀÌ °æ¿ì Ŭ¶óÀ̾ðÆ®´Â ¿ø·¡ ÆäÀÌÁö¸¦ + ±×´ë·Î º¸¿©Áà¾ß ÇÑ´Ù.

+ +
+
top
+

ImapMenu Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÁÂÇ¥¾øÀÌ À̹ÌÁö¸Ê ¿äû½Ã ÃëÇÒ Çൿ
¹®¹ý:ImapMenu none|formatted|semiformatted|unformatted
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Indexes
»óÅÂ:Base
¸ðµâ:mod_imagemap
+

ImapMenu Áö½Ã¾î´Â À̹ÌÁö¸Ê ÆÄÀÏ¿¡ + À¯È¿ÇÑ ÁÂÇ¥¸¦ ÁÖÁö ¾ÊÀº °æ¿ì ÃëÇÒ ÇൿÀ» °áÁ¤ÇÑ´Ù.

+ +
+
none
+
ImapMenu°¡ noneÀ̸é, ¸Þ´º¸¦ ¸¸µéÁö¾Ê°í + default ÇൿÀ» ÃëÇÑ´Ù.
+ +
formatted
+
formatted ¸Þ´º´Â °¡Àå °£´ÜÇÑ ¸Þ´º´Ù. + À̹ÌÁö¸Ê ÆÄÀÏÀÇ ÁÖ¼®Àº ¹«½ÃÇÑ´Ù. °¡Àå Å« Ç¥Á¦¿Í ¼öÁ÷¼±À» + Ãâ·ÂÇÏ°í, ¸µÅ©¸¦ ÇÑÁÙ¾¿ Ãâ·ÂÇÑ´Ù. ¸Þ´º´Â ÀÏ°üµÇ°í ÆòÀÌÇϸç, + µð·ºÅ丮 ¸ñ·Ï°ú Èí»çÇÏ´Ù.
+ +
semiformatted
+
semiformatted ¸Þ´º´Â À̹ÌÁö¸Ê ÆÄÀÏ¿¡ + ³ª¿À´Â ÁÖ¼®À» Ãâ·ÂÇÑ´Ù. ºóÁÙÀº HTML Çà¹Ù²ÞÀ¸·Î º¯È¯ÇÑ´Ù. + Ç¥Á¦³ª ¼öÁ÷¼±À» ±×¸®Áö ¾ÊÁö¸¸, ³ª¸ÓÁö´Â formatted + ¸Þ´º¿Í °°´Ù.
+ +
unformatted
+
ÁÖ¼®Àº Ãâ·ÂÇÏ°í, ºóÁÙÀº ¹«½ÃÇÑ´Ù. À̹ÌÁö¸Ê ÆÄÀÏ¿¡ + ÀÖ´Â ³»¿ë¸¸ Ãâ·ÂÇÑ´Ù. À̹ÌÁö¸Ê ÆÄÀÏÀÇ ÁÖ¼®¿¡ ÇÊ¿äÇÑ ¸ðµç + Çà¹Ù²Þ°ú Ç¥Á¦¸¦ Àû¾î¾ß ÇÑ´Ù. ¸Þ´ºÀÇ ¿Ü°üÀ» °¡Àå ÀÚÀ¯ÀÚÁ¦·Î + ²Ù¹Ð ¼ö ÀÖÁö¸¸, À̹ÌÁö¸Ê ÆÄÀÏÀ» »ç½Ç»ó ÀÏ¹Ý ¹®ÀÚÆÄÀÏÀÌ + ¾Æ´Ñ HTML·Î ºÁ¾ß ÇÑ´Ù.
+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_include.html b/docs/manual/mod/mod_include.html new file mode 100644 index 00000000..b45a07fc --- /dev/null +++ b/docs/manual/mod/mod_include.html @@ -0,0 +1,7 @@ +URI: mod_include.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_include.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_include.html.en b/docs/manual/mod/mod_include.html.en new file mode 100644 index 00000000..f11723e9 --- /dev/null +++ b/docs/manual/mod/mod_include.html.en @@ -0,0 +1,806 @@ + + + +mod_include - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_include

+
+

Available Languages:  en  | + ja 

+
+ + + + +
Description:Server-parsed html documents (Server Side Includes)
Status:Base
Module Identifier:include_module
Source File:mod_include.c
Compatibility:Implemented as an output filter since Apache +2.0
+

Summary

+ +

This module provides a filter which will process files + before they are sent to the client. The processing is + controlled by specially formatted SGML comments, referred to as + elements. These elements allow conditional text, the + inclusion of other files or programs, as well as the setting and + printing of environment variables.

+
+ +
top
+
+

Enabling Server-Side Includes

+ + +

Server Side Includes are implemented by the + INCLUDES filter. If + documents containing server-side include directives are given + the extension .shtml, the following directives will make Apache + parse them and assign the resulting document the mime type of + text/html:

+ +

+ AddType text/html .shtml
+ AddOutputFilter INCLUDES .shtml +

+ +

The following directive must be given for the directories + containing the shtml files (typically in a + <Directory> section, + but this directive is also valid in .htaccess files if + AllowOverride Options + is set):

+ +

+ Options +Includes +

+ +

For backwards compatibility, the server-parsed + handler also activates the + INCLUDES filter. As well, Apache will activate the INCLUDES + filter for any document with mime type + text/x-server-parsed-html or + text/x-server-parsed-html3 (and the resulting + output will have the mime type text/html).

+ +

For more information, see our Tutorial on Server Side Includes.

+
top
+
+

PATH_INFO with Server Side Includes

+ + +

Files processed for server-side includes no longer accept + requests with PATH_INFO (trailing pathname information) + by default. You can use the AcceptPathInfo directive to + configure the server to accept requests with PATH_INFO.

+
top
+
+

Basic Elements

+

The document is parsed as an HTML document, with special + commands embedded as SGML comments. A command has the syntax:

+ +

+ <!--#element attribute=value + attribute=value ... --> +

+ +

The value will often be enclosed in double quotes, but single + quotes (') and backticks (`) are also + possible. Many commands only allow a single attribute-value pair. + Note that the comment terminator (-->) should be + preceded by whitespace to ensure that it isn't considered part of + an SSI token. Note that the leading <!--# is one + token and may not contain any whitespaces.

+ +

The allowed elements are listed in the following table:

+ + + + + + + + + + + + + + + + + + + +
ElementDescription
configconfigure output formats
echoprint variables
execexecute external programs
fsizeprint size of a file
flastmodprint last modification time of a file
includeinclude a file
printenvprint all available variables
setset a value of a variable
+ +

SSI elements may be defined by modules other than + mod_include. In fact, the exec element is provided by + mod_cgi, and will only be available if this + module is loaded.

+ +

The config Element

+

This command controls various aspects of the parsing. The + valid attributes are:

+ +
+
echomsg (Apache 2.1 and later)
+
The value is a message that is sent back to the + client if the echo element + attempts to echo an undefined variable. This overrides any SSIUndefinedEcho directives.
+ +
errmsg
+
The value is a message that is sent back to the + client if an error occurs while parsing the + document. This overrides any SSIErrorMsg directives.
+ +
sizefmt
+
The value sets the format to be used which displaying + the size of a file. Valid values are bytes + for a count in bytes, or abbrev for a count + in Kb or Mb as appropriate, for example a size of 1024 bytes + will be printed as "1K".
+ +
timefmt
+
The value is a string to be used by the + strftime(3) library routine when printing + dates.
+
+ + +

The echo Element

+

This command prints one of the include + variables, defined below. If the variable is unset, the result is + determined by the SSIUndefinedEcho directive. Any dates printed are + subject to the currently configured timefmt.

+ +

Attributes:

+ +
+
var
+
The value is the name of the variable to print.
+ +
encoding
+

Specifies how Apache should encode special characters + contained in the variable before outputting them. If set + to none, no encoding will be done. If set to + url, then URL encoding (also known as %-encoding; + this is appropriate for use within URLs in links, etc.) will be + performed. At the start of an echo element, + the default is set to entity, resulting in entity + encoding (which is appropriate in the context of a block-level + HTML element, e.g. a paragraph of text). This can be + changed by adding an encoding attribute, which will + remain in effect until the next encoding attribute + is encountered or the element ends, whichever comes first.

+ +

The encoding attribute must precede the + corresponding var attribute to be effective, and + only special characters as defined in the ISO-8859-1 character + encoding will be encoded. This encoding process may not have the + desired result if a different character encoding is in use.

+ +
+ In order to avoid cross-site scripting issues, you should + always encode user supplied data. +
+
+
+ + +

The exec Element

+

The exec command executes a given shell command or + CGI script. It requires mod_cgi to be present + in the server. If Options + IncludesNOEXEC is set, this command is completely + disabled. The valid attributes are:

+ +
+
cgi
+

The value specifies a (%-encoded) URL-path to + the CGI script. If the path does not begin with a slash (/), + then it is taken to be relative to the current + document. The document referenced by this path is + invoked as a CGI script, even if the server would not + normally recognize it as such. However, the directory + containing the script must be enabled for CGI scripts + (with ScriptAlias + or Options + ExecCGI).

+ +

The CGI script is given the PATH_INFO and query + string (QUERY_STRING) of the original request from the + client; these cannot be specified in the URL path. The + include variables will be available to the script in addition to + the standard CGI environment.

+ +

Example

+ <!--#exec cgi="/cgi-bin/example.cgi" --> +

+ +

If the script returns a Location: header instead of + output, then this will be translated into an HTML anchor.

+ +

The include virtual + element should be used in preference to exec cgi. In + particular, if you need to pass additional arguments to a CGI program, + using the query string, this cannot be done with exec + cgi, but can be done with include virtual, as + shown here:

+ +

+ <!--#include virtual="/cgi-bin/example.cgi?argument=value" --> +

+
+ +
cmd
+

The server will execute the given string using + /bin/sh. The include variables are available to the command, in addition + to the usual set of CGI variables.

+ +

The use of #include virtual is almost always prefered to using + either #exec cgi or #exec cmd. The former + (#include virtual) uses the standard Apache sub-request + mechanism to include files or scripts. It is much better tested and + maintained.

+ +

In addition, on some platforms, like Win32, and on unix when + using suexec, you cannot pass arguments + to a command in an exec directive, or otherwise include + spaces in the command. Thus, while the following will work under a + non-suexec configuration on unix, it will not produce the desired + result under Win32, or when running suexec:

+ +

+ <!--#exec cmd="perl /path/to/perlscript arg1 arg2" --> +

+
+
+ + +

The fsize Element

+

This command prints the size of the specified file, subject + to the sizefmt format specification. Attributes:

+ +
+
file
+
The value is a path relative to the directory + containing the current document being parsed.
+ +
virtual
+
The value is a (%-encoded) URL-path. If it does not begin with + a slash (/) then it is taken to be relative to the current document. + Note, that this does not print the size of any CGI output, + but the size of the CGI script itself.
+
+ + +

The flastmod Element

+

This command prints the last modification date of the + specified file, subject to the timefmt format + specification. The attributes are the same as for the + fsize command.

+ + +

The include Element

+

This command inserts the text of another document or file + into the parsed file. Any included file is subject to the usual + access control. If the directory containing the parsed file has + Options + IncludesNOEXEC set, then only documents with a text + MIME-type (text/plain, + text/html etc.) will be included. Otherwise CGI + scripts are invoked as normal using the complete URL given in + the command, including any query string.

+ +

An attribute defines the location of the document; the + inclusion is done for each attribute given to the include + command. The valid attributes are:

+ +
+
file
+
The value is a path relative to the directory + containing the current document being parsed. It cannot + contain ../, nor can it be an absolute path. + Therefore, you cannot include files that are outside of the + document root, or above the current document in the directory + structure. The virtual attribute should always be + used in preference to this one.
+ +
virtual
+

The value is a (%-encoded) URL-path. The URL cannot contain a + scheme or hostname, only a path and an optional query string. If it + does not begin with a slash (/) then it is taken to be relative to the + current document.

+ +

A URL is constructed from the attribute, and the output the + server would return if the URL were accessed by the client is + included in the parsed output. Thus included files can be nested.

+ +

If the specified URL is a CGI program, the program will be + executed and its output inserted in place of the directive in the + parsed file. You may include a query string in a CGI url:

+ +

+ <!--#include virtual="/cgi-bin/example.cgi?argument=value" --> +

+ +

include virtual should be used in preference + to exec cgi to include the output of CGI programs + into an HTML document.

+
+
+ + +

The printenv Element

+

This prints out a listing of all existing variables and + their values. Special characters are entity encoded (see the echo element for details) + before being output. There are no attributes.

+ +

Example

+ <!--#printenv --> +

+ + +

The set Element

+

This sets the value of a variable. Attributes:

+ +
+
var
+
The name of the variable to set.
+ +
value
+
The value to give a variable.
+
+ +

Example

+ <!--#set var="category" value="help" --> +

+ +
top
+
+

Include Variables

+ + +

In addition to the variables in the standard CGI environment, + these are available for the echo command, for + if and elif, and to any program + invoked by the document.

+ +
+
DATE_GMT
+
The current date in Greenwich Mean Time.
+ +
DATE_LOCAL
+
The current date in the local time zone.
+ +
DOCUMENT_NAME
+
The filename (excluding directories) of the document + requested by the user.
+ +
DOCUMENT_URI
+
The (%-decoded) URL path of the document requested by the + user. Note that in the case of nested include files, this is + not the URL for the current document.
+ +
LAST_MODIFIED
+
The last modification date of the document requested by + the user.
+ +
QUERY_STRING_UNESCAPED
+
If a query string is present, this variable contains the + (%-decoded) query string, which is escaped for shell + usage (special characters like & etc. are + preceded by backslashes).
+
+
top
+
+

Variable Substitution

+ +

Variable substitution is done within quoted strings in most + cases where they may reasonably occur as an argument to an SSI + directive. This includes the config, + exec, flastmod, fsize, + include, echo, and set + directives, as well as the arguments to conditional operators. + You can insert a literal dollar sign into the string using backslash + quoting:

+ +

+ <!--#if expr="$a = \$test" --> +

+ +

If a variable reference needs to be substituted in the + middle of a character sequence that might otherwise be + considered a valid identifier in its own right, it can be + disambiguated by enclosing the reference in braces, + a la shell substitution:

+ +

+ <!--#set var="Zed" value="${REMOTE_HOST}_${REQUEST_METHOD}" --> +

+ +

This will result in the Zed variable being set + to "X_Y" if REMOTE_HOST is + "X" and REQUEST_METHOD is + "Y".

+ +

The below example will print "in foo" if the + DOCUMENT_URI is /foo/file.html, "in bar" + if it is /bar/file.html and "in neither" otherwise:

+ +

+ <!--#if expr='"$DOCUMENT_URI" = "/foo/file.html"' -->
+ + in foo
+ + <!--#elif expr='"$DOCUMENT_URI" = "/bar/file.html"' -->
+ + in bar
+ + <!--#else -->
+ + in neither
+ + <!--#endif --> +

+
top
+
+

Flow Control Elements

+ + +

The basic flow control elements are:

+ +

+ <!--#if expr="test_condition" -->
+ <!--#elif expr="test_condition" -->
+ <!--#else -->
+ <!--#endif --> +

+ +

The if element works like an if statement in a + programming language. The test condition is evaluated and if + the result is true, then the text until the next elif, + else or endif element is included in the + output stream.

+ +

The elif or else statements are be used + to put text into the output stream if the original + test_condition was false. These elements are optional.

+ +

The endif element ends the if element + and is required.

+ +

test_condition is one of the following:

+ +
+
string
+
true if string is not empty
+ +
string1 = string2
+ string1 == string2
+ string1 != string2
+ +

Compare string1 with string2. If + string2 has the form /string2/ + then it is treated as a regular expression. Regular expressions are + implemented by the PCRE engine and + have the same syntax as those in perl + 5. Note that == is just an alias for = + and behaves exactly the same way.

+ +

If you are matching positive (= or ==), you + can capture grouped parts of the regular expression. The captured parts + are stored in the special variables $1 .. + $9.

+ +

Example

+ <!--#if expr="$QUERY_STRING = /^sid=([a-zA-Z0-9]+)/" -->
+ + <!--#set var="session" value="$1" -->
+ + <!--#endif --> +

+
+ +
string1 < string2
+ string1 <= string2
+ string1 > string2
+ string1 >= string2
+ +
Compare string1 with string2. Note, that + strings are compared literally (using + strcmp(3)). Therefore the string "100" is less than + "20".
+ +
( test_condition )
+
true if test_condition is true
+ +
! test_condition
+
true if test_condition is false
+ +
test_condition1 && + test_condition2
+
true if both test_condition1 and + test_condition2 are true
+ +
test_condition1 || + test_condition2
+
true if either test_condition1 or + test_condition2 is true
+
+ +

"=" and "!=" bind more tightly than + "&&" and "||". "!" binds + most tightly. Thus, the following are equivalent:

+ +

+ <!--#if expr="$a = test1 && $b = test2" -->
+ <!--#if expr="($a = test1) && ($b = test2)" --> +

+ +

The boolean operators && and || + share the same priority. So if you want to bind such an operator more + tightly, you should use parentheses.

+ +

Anything that's not recognized as a variable or an operator + is treated as a string. Strings can also be quoted: + 'string'. Unquoted strings can't contain whitespace + (blanks and tabs) because it is used to separate tokens such as + variables. If multiple strings are found in a row, they are + concatenated using blanks. So,

+ +

string1    string2 results in string1 string2
+
+ and
+
+ 'string1    string2' results in string1    string2.

+ +

Optimization of Boolean Expressions

+

If the expressions become more complex and slow down processing + significantly, you can try to optimize them according to the + evaluation rules:

+
    +
  • Expressions are evaluated from left to right
    • +
  • Binary boolean operators (&& and ||) + are short circuited wherever possible. In conclusion with the rule + above that means, mod_include evaluates at first + the left expression. If the left result is sufficient to determine + the end result, processing stops here. Otherwise it evaluates the + right side and computes the end result from both left and right + results.
    • +
  • Short circuit evaluation is turned off as long as there are regular + expressions to deal with. These must be evaluated to fill in the + backreference variables ($1 .. $9).
    • +
+

If you want to look how a particular expression is handled, you can + recompile mod_include using the + -DDEBUG_INCLUDE compiler option. This inserts for every + parsed expression tokenizer information, the parse tree and how it is + evaluated into the output sent to the client.

+
+
+
top
+

SSIEndTag Directive

+ + + + + + + + +
Description:String that ends an include element
Syntax:SSIEndTag tag
Default:SSIEndTag "-->"
Context:server config, virtual host
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.30 and later.
+

This directive changes the string that mod_include + looks for to mark the end of an include element.

+ +

Example

+ SSIEndTag "%>" +

+ + +

See also

+ +
+
top
+

SSIErrorMsg Directive

+ + + + + + + + + +
Description:Error message displayed when there is an SSI +error
Syntax:SSIErrorMsg message
Default:SSIErrorMsg "[an error occurred while processing this +directive]"
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.30 and later.
+

The SSIErrorMsg directive changes the error + message displayed when mod_include encounters an + error. For production servers you may consider changing the default + error message to "<!-- Error -->" so that + the message is not presented to the user.

+ +

This directive has the same effect as the <!--#config + errmsg=message --> element.

+ +

Example

+ SSIErrorMsg "<!-- Error -->" +

+ +
+
top
+

SSIStartTag Directive

+ + + + + + + + +
Description:String that starts an include element
Syntax:SSIStartTag tag
Default:SSIStartTag "<!--#"
Context:server config, virtual host
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.30 and later.
+

This directive changes the string that mod_include + looks for to mark an include element to process.

+ +

You may want to use this option if you have 2 servers parsing the + output of a file each processing different commands (possibly at + different times).

+ +

Example

+ SSIStartTag "<%"
+ SSIEndTag "%>" +

+ +

The example given above, which also specifies a matching + SSIEndTag, will + allow you to use SSI directives as shown in the example + below:

+ +

SSI directives with alternate start and end tags

+ <%printenv %> +

+ +

See also

+ +
+
top
+

SSITimeFormat Directive

+ + + + + + + + + +
Description:Configures the format in which date strings are +displayed
Syntax:SSITimeFormat formatstring
Default:SSITimeFormat "%A, %d-%b-%Y %H:%M:%S %Z"
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.30 and later.
+

This directive changes the format in which date strings are displayed + when echoing DATE environment variables. The + formatstring is as in strftime(3) from the + C standard library.

+ +

This directive has the same effect as the <!--#config + timefmt=formatstring --> element.

+ +

Example

+ SSITimeFormat "%R, %B %d, %Y" +

+ +

The above directive would cause times to be displayed in the + format "22:26, June 14, 2002".

+ +
+
top
+

SSIUndefinedEcho Directive

+ + + + + + + + + +
Description:String displayed when an unset variable is echoed
Syntax:SSIUndefinedEcho string
Default:SSIUndefinedEcho "(none)"
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Base
Module:mod_include
Compatibility:Available in version 2.0.34 and later.
+

This directive changes the string that mod_include + displays when a variable is not set and "echoed".

+ +

Example

+ SSIUndefinedEcho "<!-- undef -->" +

+ +
+
top
+

XBitHack Directive

+ + + + + + + + +
Description:Parse SSI directives in files with the execute bit +set
Syntax:XBitHack on|off|full
Default:XBitHack off
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Base
Module:mod_include
+

The XBitHack directive controls the parsing + of ordinary html documents. This directive only affects files associated + with the MIME-type text/html. XBitHack can take on the following values:

+ +
+
off
+
No special treatment of executable files.
+ +
on
+
Any text/html file that has the user-execute bit + set will be treated as a server-parsed html document.
+ +
full
+
As for on but also test the group-execute bit. + If it is set, then set the Last-modified date of the + returned file to be the last modified time of the file. If + it is not set, then no last-modified date is sent. Setting + this bit allows clients and proxies to cache the result of + the request. + +

Note

+

You would not want to use the full option, unless you assure the + group-execute bit is unset for every SSI script which might #include a CGI or otherwise produces different output on + each hit (or could potentially change on subsequent requests).

+
+
+
+ + +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_include.html.ja.euc-jp b/docs/manual/mod/mod_include.html.ja.euc-jp new file mode 100644 index 00000000..36db5657 --- /dev/null +++ b/docs/manual/mod/mod_include.html.ja.euc-jp @@ -0,0 +1,791 @@ + + + +mod_include - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_include

+
+

Available Languages:  en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬¥Ñ¡¼¥¹¤¹¤ë html ¥É¥­¥å¥á¥ó¥È (Server Side Includes)
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:include_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_include.c
¸ß´¹À­:Apache 2.0 ¤«¤é½ÐÎÏ¥Õ¥£¥ë¥¿¤È¤·¤Æ¼ÂÁõ¤µ¤ì¤Þ¤·¤¿¡£
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥Õ¥¡¥¤¥ë¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤é¤ì¤ëÁ°¤Ë½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤ò + Ä󶡤·¤Þ¤¹¡£½èÍý¤ÎÆâÍƤÏÍ×ÁǤȸƤФì¤ëÆÃÊ̤ʷÁ¼°¤Î SGML ¥³¥á¥ó¥È¤Ë¤è¤ê + À©¸æ¤µ¤ì¤Þ¤¹¡£¤³¤ì¤é¤ÎÍ×ÁǤϾò·ïʬ´ô¤ä¡¢Â¾¤Î¥Õ¥¡¥¤¥ë¤ä + ¥×¥í¥°¥é¥à¤Î½ÐÎϤμè¤ê¹þ¤ß¡¢´Ä¶­ÊÑ¿ô¤ÎÀßÄê¤äɽ¼¨¤ò¹Ô¤Ê¤¦¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+
+ +
top
+
+

Server-Side Includes ¤òÍ­¸ú¤Ë¤¹¤ë

+ + +

Server Side Includes ¤Ï INCLUDES + ¥Õ¥£¥ë¥¿ ¤Ë¤è¤ê¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + Server-side include ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò´Þ¤à¥É¥­¥å¥á¥ó¥È¤Î³ÈÄ¥»Ò¤¬ + .shtml ¤Î¾ì¹ç¡¢°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï Apache ¤¬¤½¤ì¤é¤ò + ¥Ñ¡¼¥¹¤·¤Æ¡¢¤½¤Î·ë²Ì¤Ç¤­¤ë¥É¥­¥å¥á¥ó¥È¤Ë text/html ¤Î + MIME ¥¿¥¤¥×¤ò³ä¤êÅö¤Æ¤Þ¤¹:

+ +

+ AddType text/html .shtml
+ AddOutputFilter INCLUDES .shtml +

+ +

°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï shtml ¥Õ¥¡¥¤¥ë¤Î¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ç»ØÄꤵ¤ì¤Æ¤¤¤ë + ɬÍפ¬¤¢¤ê¤Þ¤¹ (Ä̾ï¤Ï <Directory> ¥»¥¯¥·¥ç¥ó¤Ç»ØÄꤷ¤Þ¤¹¤¬¡¢ + AllowOverride Options + ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢.htaccess ¥Õ¥¡¥¤¥ë¤Ë½ñ¤¯¤³¤È¤â¤Ç¤­¤Þ¤¹):

+ +

+ Options +Includes +

+ +

¸ß´¹À­¤òÊݤĤ¿¤á¤Ë¡¢server-parsed + ¥Ï¥ó¥É¥é ¤â INCLUDES ¥Õ¥£¥ë¥¿¤ò + Í­¸ú¤Ë¤·¤Þ¤¹¡£MIME ¥¿¥¤¥× text/x-server-parsed-html ¤ä + text/x-server-parsed-html3 ¤Î¥É¥­¥å¥á¥ó¥È¤ËÂФ·¤Æ¤â + Apache ¤Ï INCLUDES ¥Õ¥£¥ë¥¿¤òÍ­¸ú¤Ë¤·¤Þ¤¹ (½ÐÎϤµ¤ì¤ë¤â¤Î¤Ï + MIME ¥¿¥¤¥× text/html ¤Ë¤Ê¤ê¤Þ¤¹)¡£

+ +

¾Ü¤·¤¤¾ðÊó¤Ï Tutorial on Server Side Includes.

+
top
+
+

¥µ¡¼¥Ð¥µ¥¤¥É¥¤¥ó¥¯¥ë¡¼¥É (SSI) ¤Ç¤Î PATH_INFO

+ + +

SSI ¤Ç½èÍý¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï PATH_INFO + (¸å³¤Î¥Ñ¥¹Ì¾¾ðÊó) + ÉÕ¤­¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±Æþ¤ì¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿¡£AcceptPathInfo ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + PATH_INFO ÉÕ¤­¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±Æþ¤ì¤ë¤è¤¦¤Ë¥µ¡¼¥Ð¤ò + ÀßÄê¤Ç¤­¤Þ¤¹¡£

+
top
+
+

´ðËÜÍ×ÁÇ

+

¥É¥­¥å¥á¥ó¥È¤Ï¡¢SGML ¤Î¥³¥á¥ó¥È¤È¤·¤ÆÆÃÊ̤ʥ³¥Þ¥ó¥É¤¬Ëä¤á¹þ¤Þ¤ì¤¿ + HTML ¥É¥­¥å¥á¥ó¥È¤È¤·¤Æ¥Ñ¡¼¥¹¤µ¤ì¤Þ¤¹¡£¥³¥Þ¥ó¥É¤Î¹½Ê¸¤Ï¼¡¤Î¤è¤¦¤Ë + ¤Ê¤Ã¤Æ¤¤¤Þ¤¹:

+ +

+ <!--#element attribute=value + attribute=value ... --> +

+ +

ÃÍ (ÌõÃí: value) ¤ÏÆó½Å°úÍÑÉä¤Ç°Ï¤à¤Î¤¬°ìÈÌŪ¤Ç¤¹¤¬¡¢ + ¥·¥ó¥°¥ë¥¯¥ª¡¼¥È (') ¤È¥Ð¥Ã¥¯¥¯¥ª¡¼¥È (`) ¤â»ÈÍѤǤ­¤Þ¤¹¡£ + ¿¤¯¤Î¥³¥Þ¥ó¥É¤Ï°À­-ÃÍ (ÌõÃí: attribute-value) ¤ÎÁȤò°ì¤Ä¤À¤±»ØÄê¤Ç¤­¤Þ¤¹¡£ + ¥³¥á¥ó¥È¤Î½ª¤ï¤ê (-->) + ¤ÎÁ°¤Ë¤Ï¡¢SSI ¤Î¶ç¤Î°ìÉô¤À¤È²ò¼á¤µ¤ì¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¶õÇò¤ò + Æþ¤ì¤Æ¤¯¤À¤µ¤¤¡£ºÇ½é¤Î <!--# ¤Ï¤Þ¤È¤á¤Æ°ì¤Ä¤Î + ¶ç¤Ç¡¢¶õÇò¤ò¤Õ¤¯¤ó¤Ç¤Ï¤¤¤±¤Ê¤¤¤³¤ÈÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Í×ÁÇ (ÌõÃí: element) ¤ò°Ê²¼¤Îɽ¤Ë¼¨¤·¤Þ¤¹¡£

+ + + + + + + + + + + + + + + + + + + +
Í×ÁÇÀâÌÀ
configconfigure output formats
echoprint variables
execexecute external programs
fsizeprint size of a file
flastmodprint last modification time of a file
includeinclude a file
printenvprint all available variables
setset a value of a variable
+ +

SSI Í×ÁÇ¤Ï mod_include °Ê³°¤Î¥â¥¸¥å¡¼¥ë¤Ç + ÄêµÁ¤µ¤ì¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£¼ÂºÝ¡¢ + exec Í×ÁÇ¤Ï + mod_cgi ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤Æ¡¢¤³¤Î¥â¥¸¥å¡¼¥ë¤¬ + ¥í¡¼¥É¤µ¤ì¤ë¾ì¹ç¤Ë¤Î¤ßÍøÍѲÄǽ¤È¤Ê¤ê¤Þ¤¹¡£

+ +

config Í×ÁÇ

+

¼¡¤Î¥³¥Þ¥ó¥É¤Ï²òÀϤÎÍÍ¡¹¤Ê¦Ì̤òÀ©¸æ¤·¤Þ¤¹¡£Â°À­¤Ï¼¡¤ÎÄ̤ê¤Ç¤¹¡£

+ +
+
echomsg (Apache 2.1 °Ê¹ß)
+
»ØÄꤵ¤ì¤ëÃͤϡ¢echo + Í×ÁǤ¬Ì¤ÄêµÁ¤ÎÊÑ¿ô¤ò¥¨¥³¡¼¤·¤è¤¦¤È¤·¤¿ºÝ¤Ë¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤é¤ì¤ë¥á¥Ã¥»¡¼¥¸¤Ë¤Ê¤ê¤Þ¤¹¡£ + SSIUndefinedEcho + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¾å½ñ¤­¤·¤Þ¤¹¡£
+ +
errmsg
+
¤³¤ÎÃͤ¬¡¢¥É¥­¥å¥á¥ó¥È¤Î²òÀÏÃæ¤Ë¥¨¥é¡¼¤¬È¯À¸¤·¤¿»þ¤Ë + ¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¿®¤µ¤ì¤ë¥á¥Ã¥»¡¼¥¸¤Ë¤Ê¤ê¤Þ¤¹¡£ + SSIErrorMsg + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¾å½ñ¤­¤·¤Þ¤¹¡£
+ +
sizefmt
+
¤³¤ÎÃͤϡ¢¥Õ¥¡¥¤¥ë¤Î¥µ¥¤¥º¤òɽ¼¨¤¹¤ëºÝ¤Ë»ÈÍѤ¹¤ë + ¥Õ¥©¡¼¥Þ¥Ã¥È¤òÀßÄꤷ¤Þ¤¹¡£ÃÍ¤Ï ¥Ð¥¤¥È¥«¥¦¥ó¥È¤Î + bytes¤«¡¢Kb ¤ä Mb ¤òÍ¥ÀèŪ¤Ë»ÈÍѤ¹¤ë + abbrec (Î㤨¤Ð 1024 ¥Ð¥¤¥È¤Ï "1K" ¤Èɽ¼¨¤µ¤ì¤Þ¤¹) + ¤Ç¤¹¡£
+ +
timefmt
+
¤³¤ÎÃÍ¤Ï strftime(3) ¥é¥¤¥Ö¥é¥ê¥ë¡¼¥Á¥ó¤¬ + Æü»þ¤ò¥×¥ê¥ó¥È¤¹¤ëºÝ¤ËÍѤ¤¤é¤ì¤Þ¤¹¡£
+
+ + +

echo Í×ÁÇ

+

¤³¤Î¥³¥Þ¥ó¥É¤Ï°Ê²¼¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë include + ÊÑ¿ô ¤òɽ¼¨¤·¤Þ¤¹¡£ÊÑ¿ô¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ï SSIUndefinedEcho ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + ·èÄꤵ¤ì¤ë·ë²Ì¤È¤Ê¤ê¤Þ¤¹¡£ÆüÉդϤ½¤Î»þÅÀ¤Ç¤Î timefmt ¤Ë½¾¤Ã¤Æ + ɽ¼¨¤µ¤ì¤Þ¤¹¡£Â°À­¤Ï¼¡¤ÎÄ̤ê¤Ç¤¹¡£

+ +
+
var
+
ÃͤÏɽ¼¨¤¹¤ëÊÑ¿ô¤Î̾Á°¤Ç¤¹¡£
+ +
encoding
+

ÊÑ¿ô¤ò½ÐÎϤ¹¤ëÁ°¤Ë¡¢ÊÑ¿ôÃæ¤ÎÆÃÊÌʸ»ú¤ò¤É¤Î¤è¤¦¤Ë¥¨¥ó¥³¡¼¥É¤¹¤ë¤«¤ò + »ØÄꤷ¤Þ¤¹¡£none ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢¥¨¥ó¥³¡¼¥É¤Ï¹Ô¤Ê¤ï¤ì¤Þ¤»¤ó¡£ + url ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢URL ¥¨¥ó¥³¡¼¥É (%-¥¨¥ó¥³¡¼¥É¤È¤â + ¸Æ¤Ð¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ï¥ê¥ó¥¯Åù¤Î URL ¤Î»ÈÍѤËŬÀڤǤ¹) ¤¬ + ¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£echo Í×ÁǤγ«»Ï»þ¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ï + entity ¤ËÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ï¥¨¥ó¥Æ¥£¥Æ¥£¥¨¥ó¥³¡¼¥É + (ÃÊÍî¤ä¥Æ¥­¥¹¥È¤Ê¤É¤Î¥Ö¥í¥Ã¥¯¥ì¥Ù¥ë¤Î HTML ¥¨¥ì¥á¥ó¥È¤Î¥³¥ó¥Æ¥­¥¹¥È¤Ë + Ŭ¤·¤Æ¤¤¤Þ¤¹) ¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£¤³¤ì¤Ï encoding °À­ + ¤ò²Ã¤¨¤ë¤³¤È¤ÇÊѹ¹¤Ç¤­¤Þ¤¹¡£Êѹ¹¤Ï¼¡¤Î encoding °À­¤«¡¢ + Í×ÁǤνªÎ»¤Þ¤Ç¸úÎϤò»ý¤Á¤Þ¤¹¡£

+ +

encoding °À­¤Ï¥¨¥ó¥³¡¼¥É¤ÎÊѹ¹¤ò¤·¤¿¤¤ var + ¤ÎÁ°¤Ë ¤¢¤ëɬÍפ¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤Þ¤¿¡¢ISO-8859-1 ¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ç + ÄêµÁ¤µ¤ì¤Æ¤¤¤ëÆÃÊ̤Êʸ»ú¤À¤±¤¬¥¨¥ó¥³¡¼¥É¤µ¤ì¤Þ¤¹¡£ + Ê̤Îʸ»ú¤Î¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Î¾ì¹ç¤Ï¡¢¤³¤Î¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ï + ˾¤ß¤Î·ë²Ì¤Ë¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ +
+ ¥¯¥í¥¹¥µ¥¤¥È¥¹¥¯¥ê¥×¥Æ¥£¥ó¥°¤ÎÌäÂê¤òÈò¤±¤ë¤¿¤á¤Ë¡¢ + ¾ï¤Ë¥æ¡¼¥¶¤«¤é¤Î¥Ç¡¼¥¿¤ò¥¨¥ó¥³¡¼¥É¤¹¤Ù¤­¤Ç¤¹¡£ +
+
+
+ + +

exec Í×ÁÇ

+

exec ¥³¥Þ¥ó¥É¤Ï»ØÄꤵ¤ì¤¿¥·¥§¥ë¥³¥Þ¥ó¥É¤ä CGI ¥¹¥¯¥ê¥×¥È¤ò + ¼Â¹Ô¤·¤Þ¤¹¡£mod_cgi ¤¬¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤¤¤Ê¤±¤ì¤Ð + ¤Ê¤ê¤Þ¤»¤ó¡£Option + IncludesNOEXEC ¤Ï¤³¤Î¥³¥Þ¥ó¥É¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£ + »ÈÍѲÄǽ¤Ê°À­¤Ï¼¡¤ÎÄ̤ê¤Ç¤¹¡£

+ +
+
cgi
+

ÃÍ¤Ï (%-¥¨¥ó¥³¡¼¥É¤µ¤ì¤¿) URL ¤ò»ØÄꤷ¤Þ¤¹¡£¥Ñ¥¹¤¬ + ¥¹¥é¥Ã¥·¥å (/) ¤Ç»Ï¤Þ¤é¤Ê¤¤¤È¤­¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤«¤é¤Î + ÁêÂХѥ¹¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£¤³¤Î¥Ñ¥¹¤Ç»²¾È¤µ¤ì¤Æ¤¤¤ë¥É¥­¥å¥á¥ó¥È¤Ï + ¥µ¡¼¥Ð¤¬ CGI ¥¹¥¯¥ê¥×¥È¤È¤·¤Æ°·¤Ã¤Æ¤¤¤Ê¤¯¤Æ¤â CGI ¥¹¥¯¥ê¥×¥È¤È¤·¤Æ + µ¯Æ°¤µ¤ì¤Þ¤¹¡£¤¿¤À¤·¡¢¥¹¥¯¥ê¥×¥È¤Î¤¢¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤Ï + (ScriptAlias + ¤ä Option ExecCGI + ¤Ë¤è¤Ã¤Æ) CGI ¥¹¥¯¥ê¥×¥È¤Î»ÈÍѤ¬µö²Ä¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

CGI ¥¹¥¯¥ê¥×¥È¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¸µ¡¹¤Î¥ê¥¯¥¨¥¹¥È¤Î + PATH_INFO ¤È¥¯¥¨¥ê¡¼Ê¸»úÎó (QUERY_STRING) ¤¬ÅϤµ¤ì¤Þ¤¹¡£ + ¤³¤ì¤é¤Ï URL ¥Ñ¥¹¤È¤·¤ÆÆÃÄê¤Ç¤­¤Ê¤¤¤â¤Î¤Ç¤¹¡£ + ¥¹¥¯¥ê¥×¥È¤Ïɸ½à CGI ´Ä¶­¤Ë²Ã¤¨¤Æ¡¢include ÊÑ¿ô¤ò + »ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Îã

+ <!--#exec cgi="/cgi-bin/example.cgi" --> +

+ +

¥¹¥¯¥ê¥×¥È¤¬¡¢½ÐÎϤÎÂå¤ï¤ê¤Ë Location: ¥Ø¥Ã¥À¤òÊÖ¤¹¤È¡¢ + HTML ¤Î¥¢¥ó¥«¡¼ (ÌõÃí¡§¥ê¥ó¥¯) ¤ËÊÑ´¹¤µ¤ì¤Þ¤¹¡£

+ +

exec cgi ¤è¤ê¤â¡¢ + include virtual + ¤ÎÊý¤ò»È¤¦¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£Æäˡ¢CGI ¤Ø¤ÎÄɲäΰú¿ô¤ò + ¥¯¥¨¥ê¡¼Ê¸»úÎó¤ò»È¤Ã¤ÆÅϤ¹¤³¤È¤Ï exec cgi ¤Ï + ¤Ç¤­¤Þ¤»¤ó¤¬¡¢include virtual ¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ + ²Äǽ¤Ç¤¹¡£

+ +

+ <!--#include virtual="/cgi-bin/example.cgi?argument=value" --> +

+
+ +
cmd
+

¥µ¡¼¥Ð¤Ï»ØÄꤵ¤ì¤¿Ê¸»úÎó¤ò /bin/sh ¤ò»È¤Ã¤Æ + ¼Â¹Ô¤·¤Þ¤¹¡£¥³¥Þ¥ó¥É¤ÏÄ̾ï¤Î CGI ÊÑ¿ô¤Ë²Ã¤¨¤Æ include ÊÑ¿ô¤â»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤Û¤È¤ó¤É¤Î¾ì¹ç¡¢#include + virtual ¤ò»È¤¦Êý¤¬ #exec cgi ¤ä #exec + cmd ¤ò»È¤¦¤è¤ê¤âÎɤ¤¤Ç¤¹¡£Á°¼Ô (#include virtual) + ¤Ïɸ½à¤Î Apache ¤Î¥µ¥Ö¥ê¥¯¥¨¥¹¥Èµ¡¹½¤ò»È¤Ã¤Æ¥Õ¥¡¥¤¥ë¤ä¥¹¥¯¥ê¥×¥È¤Î + ½ÐÎϤò¼è¤ê¹þ¤ß¤Þ¤¹¡£ + ¤³¤Á¤é¤ÎÊý¤¬¤è¤¯¥Æ¥¹¥È¤µ¤ì¥á¥ó¥Æ¥Ê¥ó¥¹¤µ¤ì¤¿ÊýË¡¤Ç¤¹¡£

+ +

¤µ¤é¤Ë¡¢Win32 ¤Î¤è¤¦¤Ê¤¤¤¯¤Ä¤«¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤ä¡¢suexec ¤ò»È¤Ã¤Æ¤¤¤ë unix ¤Ç¤Ï¡¢ + exec ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥³¥Þ¥ó¥É¤Ë + °ú¿ô¤òÅϤ·¤¿¤ê¡¢¥³¥Þ¥ó¥É¤Ë¶õÇò¤òÆþ¤ì¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ + ¤Ç¤¹¤«¤é¡¢°Ê²¼¤Î¤â¤Î¤Ï unix ¤Î suexec ¤Ç¤Ê¤¤ÀßÄê¤Ç¤ÏÆ°ºî¤·¤Þ¤¹¤¬¡¢ + Win32 ¤ä suexec ¤ò»È¤Ã¤Æ¤¤¤ë unix ¤Ç¤Ï´üÂÔ¤·¤¿·ë²Ì¤Ë¤Ï¤Ê¤ê¤Þ¤»¤ó:

+ +

+ <!--#exec cmd="perl /path/to/perlscript arg1 arg2" --> +

+
+
+ + +

fsize Í×ÁÇ

+

¤³¤Î¥³¥Þ¥ó¥É¤Ï»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤ÎÂ礭¤µ¤ò sizefmt ¤Î + ½ñ¼°»ØÄê¤Ë´ð¤Å¤¤¤Æ½ÐÎϤ·¤Þ¤¹¡£Â°À­¤Ï¼¡¤ÎÄ̤ê¤Ç¤¹¡£

+ +
+
file
+
ÃͤϲòÀϤµ¤ì¤Æ¤¤¤ë¥É¥­¥å¥á¥ó¥È¤Î¸ºß¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤Î + ÁêÂХѥ¹¤Ç¤¹¡£
+ +
virtual
+
ÃÍ¤Ï (% ¥¨¥ó¥³¡¼¥É¤µ¤ì¤¿) URL-path ¤Ç¤¹¡£¥¹¥é¥Ã¥·¥å (/) ¤Ç + »Ï¤Þ¤é¤Ê¤¤¤È¤­¤Ï¥É¥­¥å¥á¥ó¥È¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£ + CGI ¤Î½ÐÎϤΥµ¥¤¥º¤Ï¥×¥ê¥ó¥È¤µ¤ì¤Þ¤»¤ó¡£CGI + ¥¹¥¯¥ê¥×¥È¼«ÂΤΥµ¥¤¥º¤¬¥×¥ê¥ó¥È¤µ¤ì¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
+
+ + +

flastmod Í×ÁÇ

+

¤³¤Î¥³¥Þ¥ó¥É¤Ï»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤ÎºÇ½ª½¤Àµ»þ¹ï¤ò + timefmt ½ñ¼°»ØÄê¤Ë½¾¤Ã¤Æɽ¼¨¤·¤Þ¤¹¡£ + »ØÄê²Äǽ¤Ê°À­¤Ï fsize ¥³¥Þ¥ó¥É¤ÈƱ¤¸¤Ç¤¹¡£

+ + +

include Í×ÁÇ

+

¤³¤Î¥³¥Þ¥ó¥É¤ÏÊ̤Îʸ½ñ¤ä¥Õ¥¡¥¤¥ë¤Î¥Æ¥­¥¹¥È¤ò²òÀϤ·¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Ë + ÁÞÆþ¤·¤Þ¤¹¡£ÁÞÆþ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤Ï¥¢¥¯¥»¥¹À©¸æ¤Î´ÉÍý²¼¤Ë¤¢¤ê¤Þ¤¹¡£ + ²òÀϤ·¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Î¸ºß¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ë + Option IncludesNOEXEC + ¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢text MIME ¥¿¥¤¥× (text/plain, + text/html Åù) ¤Î¥É¥­¥å¥á¥ó¥È¤Î¤ß¥¤¥ó¥¯¥ë¡¼¥É¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£ + ¤½¤Î¾¤Î¾ì¹ç¤Ï¡¢¥¯¥¨¥ê¡¼Ê¸»úÎó¤â´Þ¤á¡¢¥³¥Þ¥ó¥É¤Ç»ØÄꤵ¤ì¤¿ + ´°Á´¤Ê URL ¤ò»È¤Ã¤ÆÉáÄÌ¤Ë CGI ¥¹¥¯¥ê¥×¥È¤¬¸Æ¤Ó½Ð¤µ¤ì¤Þ¤¹¡£

+ +

°À­¤¬Ê¸½ñ¤Î°ÌÃÖ¤ò»ØÄꤷ¤Þ¤¹¡£include ¥³¥Þ¥ó¥É¤ËÍ¿¤¨¤é¤ì¤¿¤½¤ì¤¾¤ì¤Î + °À­¤ËÂФ·¤ÆÁÞÆþºî¶È¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£Í­¸ú¤Ê°À­¤Ï¼¡¤ÎÄ̤ê¤Ç¤¹¡£

+ +
+
file
+
ÃͤϲòÀϤµ¤ì¤Æ¤¤¤ë¥É¥­¥å¥á¥ó¥È¤Î¸ºß¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤Î + ÁêÂХѥ¹¤Ç¤¹¡£ + ../ ¤ò´Þ¤ó¤Ç¤¤¤¿¤ê¡¢ÀäÂХѥ¹¤ò»ØÄꤷ¤¿¤ê¤Ï¤Ç¤­¤Þ¤»¤ó¡£ + ¤Ç¤¹¤«¤é¡¢¥É¥­¥å¥á¥ó¥È¥ë¡¼¥È¤Î³°¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¤ä¡¢¥Ç¥£¥ì¥¯¥È¥ê¹½Â¤¤Ç + ¾å°Ì¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¤òÁÞÆþ¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ + ¾ï¤Ë¤³¤Î°À­¤è¤ê¤Ï¡¢virtual °À­¤ò»È¤¦¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ +
+ +
virtual
+

ÃͤϲòÀϤµ¤ì¤Æ¤¤¤ë¥É¥­¥å¥á¥ó¥È¤«¤é¤Î (% ¥¨¥ó¥³¡¼¥É¤µ¤ì¤¿) URL + ¤Ç¤¹¡£URL ¤Ë¤Ï¥¹¥­¡¼¥à¤ä¥Û¥¹¥È̾¤ò´Þ¤á¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£¥Ñ¥¹¤È¡¢ + ¤â¤·¤¢¤ì¤Ð¥¯¥¨¥ê¡¼Ê¸»úÎó¤ò»ØÄê¤Ç¤­¤ë¤À¤±¤Ç¤¹¡£¥¹¥é¥Ã¥·¥å (/) ¤«¤é + »Ï¤Þ¤é¤Ê¤¤¾ì¹ç¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£

+ +

URL ¤Ï°À­¤«¤éºî¤é¤ì¡¢¤½¤Î URL ¤ò¥¯¥é¥¤¥¢¥ó¥È¤¬¥¢¥¯¥»¥¹¤·¤¿¤È¤­¤Ë + ½ÐÎϤµ¤ì¤ëÆâÍƤ¬²òÀϸå¤Î½ÐÎϤ˴ޤá¤é¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢ÁÞÆþ¤µ¤ì¤ë + ¥Õ¥¡¥¤¥ë¤ÏÆþ¤ì»Ò¹½Â¤¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

»ØÄꤵ¤ì¤¿ URL ¤¬ CGI ¥×¥í¥°¥é¥à¤Ç¤¢¤Ã¤¿¾ì¹ç¤Ï¡¢ + ¥×¥í¥°¥é¥à¤¬¼Â¹Ô¤µ¤ì¡¢¤½¤Î½ÐÎϤ¬²òÀϤ·¤Æ¤¤¤ë¥Õ¥¡¥¤¥ëÃæ¤Î + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¤¢¤Ã¤¿°ÌÃÖ¤ËÁÞÆþ¤µ¤ì¤Þ¤¹¡£CGI ¤Î url ¤Ë + ¥¯¥¨¥ê¡¼ URL ¤òÆþ¤ì¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

+ <!--#include virtual="/cgi-bin/example.cgi?argument=value" --> +

+ +

HTML ¥É¥­¥å¥á¥ó¥È¤Ë CGI ¥×¥í¥°¥é¥à¤Î½ÐÎϤò´Þ¤á¤ëÊýË¡¤È¤·¤Æ¤Ï¡¢ + include virtual ¤ÎÊý¤¬ exec cgi ¤è¤ê¤â + ¹¥¤Þ¤·¤¤ÊýË¡¤Ç¤¹¡£

+
+
+ + +

printenv Í×ÁÇ

+

¤³¤ì¤Ï¡¢Â¸ºß¤¹¤ë¤¹¤Ù¤Æ¤ÎÊÑ¿ô¤È¤½¤ÎÃͤòɽ¼¨¤·¤Þ¤¹¡£Apache 1.3.12 ¤«¤é¡¢ + ÆÃÊ̤Êʸ»ú¤Ï½ÐÎϤµ¤ì¤ëÁ°¤Ë¥¨¥ó¥Æ¥£¥Æ¥£¥¨¥ó¥³¡¼¥É (¾ÜºÙ¤Ï echo Í×ÁǤò»²¾È) + ¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£Â°À­¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +

Îã

+ <!--#printenv --> +

+ + +

set Í×ÁÇ

+

¤³¤ì¤ÏÊÑ¿ô¤ÎÃͤòÀßÄꤷ¤Þ¤¹¡£Â°À­¤Ï¼¡¤ÎÄ̤ê¤Ç¤¹¡£

+ +
+
var
+
ÀßÄꤹ¤ëÊÑ¿ô¤Î̾Á°¡£
+ +
value
+
ÊÑ¿ô¤ËÀßÄꤹ¤ëÃÍ¡£
+
+ +

Îã

+ <!--#set var="category" value="help" --> +

+ +
top
+
+

Include ÊÑ¿ô

+ + +

ɸ½à CGI ´Ä¶­¤ÎÊÑ¿ô¤Ë²Ã¤¨¤Æ¡¢echo ¥³¥Þ¥ó¥É¤ä¡¢ + if ¤ä elif, ¤½¤ì¤Ë¥É¥­¥å¥á¥ó¥È¤«¤é¸Æ¤Ó½Ð¤µ¤ì¤ë + ¤¹¤Ù¤Æ¤Î¥×¥í¥°¥é¥à¤«¤é»ÈÍѤǤ­¤ëÊÑ¿ô¤¬¤¢¤ê¤Þ¤¹¡£

+ +
+
DATE_GMT
+
¥°¥ê¥Ë¥Ã¥¸É¸½à»þ¤Ë¤è¤ë¸½ºß»þ¹ï¡£
+ +
DATE_LOCAL
+
¥í¡¼¥«¥ë¤Îɸ½à»þ¤Ë¤è¤ë¸½ºß»þ¹ï¡£
+ +
DOCUMENT_NAME
+
¥æ¡¼¥¶¤¬¥ê¥¯¥¨¥¹¥È¤·¤¿ (¥Ç¥£¥ì¥¯¥È¥ê¤ò½ü¤¤¤¿) ¥Õ¥¡¥¤¥ë̾¡£
+ +
DOCUMENT_URI
+
¥æ¡¼¥¶¤¬¥ê¥¯¥¨¥¹¥È¤·¤¿ (% ¥¨¥ó¥³¡¼¥É¤µ¤ì¤¿) URL-path¡£ + ÁÞÆþ¥Õ¥¡¥¤¥ë¤¬Æþ¤ì»Ò¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢²òÀϤµ¤ì¤Æ¤¤¤ë + ¥É¥­¥å¥á¥ó¥È¤Î URL ¤Ç¤Ï¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
+ +
LAST_MODIFIED
+
¥æ¡¼¥¶¤¬¥ê¥¯¥¨¥¹¥È¤·¤¿¥É¥­¥å¥á¥ó¥È¤ÎºÇ½ª½¤Àµ»þ¹ï¡£
+ +
QUERY_STRING_UNESCAPED
+
¥¯¥¨¥ê¡¼Ê¸»úÎ󤬤¢¤ë¾ì¹ç¡¢¤³¤ÎÊÑ¿ô¤Ë¤Ï (%-¥Ç¥³¡¼¥É¤µ¤ì¤¿) + ¥¯¥¨¥ê¡¼Ê¸»úÎó¤¬ÂåÆþ¤µ¤ì¤Æ¤¤¤Æ¡¢shell ¤Ç»ÈÍѤǤ­¤ë¤è¤¦¤Ë + ¥¨¥¹¥±¡¼¥×¤µ¤ì¤Æ¤¤¤Þ¤¹ (& + ¤È¤¤¤Ã¤¿Æüìʸ»ú¤Ë¤Ï¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤¬Ä¾Á°¤ËÃÖ¤«¤ì¤Þ¤¹)¡£
+
+
top
+
+

ÊÑ¿ôÃÖ´¹

+ +

ÊÑ¿ôÃÖ´¹¤Ï¤¿¤¤¤Æ¤¤¤Î¾ì¹ç SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô¤È¤·¤ÆÂÅÅö¤Ê¾ì½ê¤Ë¤¢¤ë + °úÍÑÉä¤Ç°Ï¤Þ¤ì¤¿Ê¸»úÎóÃæ¤Ç¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£¤³¤ì¤Ë³ºÅö¤¹¤ë¤â¤Î¤Ë¤Ï¡¢ + config, + exec, flastmod, fsize, + include, echo, set ¤Î + ³Æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¡¢¾ò·ïʬ´ôÍѤΥª¥Ú¥ì¡¼¥¿¤Ø¤Î°ú¿ô¤¬¤¢¤ê¤Þ¤¹¡£ + ¥É¥ëµ­¹æ¤Ï¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤ò»È¤¦¤³¤È¤Ç»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ <!--#if expr="$a = \$test" --> +

+ +

ÊÑ¿ô̾¤È¤·¤Æ¤ß¤Ê¤µ¤ì¤ëʸ»úÎó¤ÎÃæ¤ÇÊÑ¿ô¤Ø¤Î»²¾È¤òÃÖ´¹¤¹¤ëɬÍפ¬¤¢¤ë¤È¤­¤Ï¡¢ + ¥·¥§¥ë¤Ç¤ÎÊÑ¿ôÃÖ´¹¤Î¤è¤¦¤Ë¡¢Ãæ³ç¸Ì¤Ç³ç¤ë¤³¤È¤Ç¶èÊ̤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ <!--#set var="Zed" value="${REMOTE_HOST}_${REQUEST_METHOD}" --> +

+ +

¤³¤ÎÎã¤Ç¤Ï¡¢REMOTE_HOST ¤¬ + "X" ¤Ç REQUEST_METHOD ¤¬ + "Y" ¤Î¤È¤­¤ËÊÑ¿ô Zed ¤ò "X_Y" + ¤ËÀßÄꤷ¤Þ¤¹¡£

+ +

°Ê²¼¤ÎÎã¤Ç¤Ï¡¢DOCUMENT_URI ¤¬ /foo/file.html + ¤Î¤È¤­¤Ë "in foo" ¤ò¡¢/bar/file.html ¤Î¤È¤­¤Ë "in bar" ¤ò¡¢ + ¤É¤Á¤é¤Ç¤â¤Ê¤¤¤È¤­¤Ë¤Ï "in neither" ¤òɽ¼¨¤·¤Þ¤¹¡£

+ +

+ <!--#if expr='"$DOCUMENT_URI" = "/foo/file.html"' -->
+ + in foo
+ + <!--#elif expr='"$DOCUMENT_URI" = "/bar/file.html"' -->
+ + in bar
+ + <!--#else -->
+ + in neither
+ + <!--#endif --> +

+
top
+
+

¥Õ¥í¡¼À©¸æÍ×ÁÇ

+ + +

´ðËÜŪ¤Ê¥Õ¥í¡¼¥³¥ó¥È¥í¡¼¥ëÍ×ÁǤϼ¡¤ÎÄ̤ê¤Ç¤¹¡£

+ +

+ <!--#if expr="test_condition" -->
+ <!--#elif expr="test_condition" -->
+ <!--#else -->
+ <!--#endif --> +

+ +

if Í×ÁÇ¤Ï¥×¥í¥°¥é¥ß¥ó¥°¸À¸ì¤Î + if ʸ¤ÈƱ¤¸¤è¤¦¤ËÆ°ºî¤·¤Þ¤¹¡£¾ò·ï¤¬É¾²Á¤µ¤ì¡¢·ë²Ì¤¬¿¿¤Ç¤¢¤ì¤Ð¼¡¤Î + elif ¤« else ¤« endif + Í×ÁǤޤǤÎʸ»úÎ󤬽ÐÎϤËÁÞÆþ¤µ¤ì¤Þ¤¹¡£

+ +

elif ¤ä else ʸ¤Ï test_condition + ¤¬µ¶¤Î¤È¤­¤Ë¥Æ¥­¥¹¥È¤ò½ÐÎϤËÁÞÆþ¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£ + ¤³¤ì¤é¤ÎÍ×ÁǤϤ¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

endif Í×ÁÇ¤Ï if + Í×ÁǤò½ªÎ»¤µ¤»¤Þ¤¹¡£¤³¤ÎÍ×ÁǤÏɬ¿Ü¤Ç¤¹¡£

+ +

test_condition ¤Ï°Ê²¼¤Î¤É¤ì¤«¤Ç¤¹:

+ +
+
string
+
string ¤¬¶õ¤Ç¤Ê¤¤¾ì¹ç¤Ë¿¿¤Ç¤¹
+ +
string1 = string2
+ string1 == string2
+ string1 != string2
+ +

string1 ¤È string2 ¤òÈæ³Ó¤·¤Þ¤¹¡£ + string2 ¤¬ /string/ + ¤È¤¤¤¦·Á¼°¤Ç¤¢¤ì¤Ð¡¢Àµµ¬É½¸½¤È¤·¤ÆÈæ³Ó¤µ¤ì¤Þ¤¹¡£Àµµ¬É½¸½¤Ï + PCRE ¥¨¥ó¥¸¥ó¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤Æ¡¢ + perl 5 ¤ÈƱ¤¸¹½Ê¸¤ò»ÈÍѤ·¤Þ¤¹¡£ + == ¤Ïñ¤Ë = ¤ÎÊÌ̾¤Ç¡¢¤Þ¤Ã¤¿¤¯Æ±¤¸Æ°ºî¤ò + ¤·¤Þ¤¹¡£

+ +

Àµ¤Î¥Þ¥Ã¥Á¥ó¥° (= ¤Þ¤¿¤Ï ==) ¤Î¾ì¹ç¤Ï¡¢ + Àµµ¬É½¸½¤Ç¥°¥ë¡¼¥×ʬ¤±¤µ¤ì¤¿¥Ñ¡¼¥Ä¤ò¥­¥ã¥×¥Á¥ã¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥­¥ã¥×¥Á¥ã¤µ¤ì¤¿Éôʬ¤ÏÆüìÊÑ¿ô $1 .. $9 + ¤Ë³ÊǼ¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ <!--#if expr="$QUERY_STRING = /^sid=([a-zA-Z0-9]+)/" -->
+ + <!--#set var="session" value="$1" -->
+ + <!--#endif --> +

+
+ +
string1 < string2
+ string1 <= string2
+ string1 > string2
+ string1 >= string2
+ +
string1 ¤È string2 ¤òÈæ³Ó¤·¤Þ¤¹¡£ + ʸ»úÎó¤È¤·¤ÆÈæ³Ó¤µ¤ì¤ë (strcmp(3) ¤ò»ÈÍÑ) + ¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤Ç¤¹¤«¤é¡¢Ê¸»úÎó "100" ¤Ï "20" + ¤è¤ê¤â¾®¤µ¤¤¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£
+ +
( test_condition )
+
test_condition ¤¬¿¿¤Î¤È¤­¡¢¿¿
+ +
! test_condition
+
test_condition ¤¬µ¶¤Î¤È¤­¡¢¿¿
+ +
test_condition1 && + test_condition2
+
test_condition1 ¤«¤Ä + test_condition2 ¤¬¿¿¤Î¤È¤­¡¢¿¿
+ +
test_condition1 || + test_condition2
+
test_condition1 ¤Þ¤¿¤Ï + test_condition2 ¤¬¿¿¤Î¤È¤­¡¢¿¿
+
+ +

"=" ¤È "!=" ¤ÎÊý¤¬ "&&" ¤è¤ê + ¤­¤Ä¤¯Â«Çû¤·¤Þ¤¹¡£"!" ¤Î«Çû¤¬°ìÈÖ¤­¤Ä¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é°Ê²¼¤ÎÆó¤Ä¤ÏÅù²Á¤Ç¤¹:

+ +

+ <!--#if expr="$a = test1 && $b = test2" -->
+ <!--#if expr="($a = test1) && ($b = test2)" --> +

+ +

¿¿µ¶ÃÍ¥ª¥Ú¥ì¡¼¥¿ && ¤È || + ¤ÏƱ¤¸Í¥ÀèÅ٤Ǥ¹¡£ + ¤³¤ì¤é¤Î¥ª¥Ú¥ì¡¼¥¿¤Ç°ìÊý¤Ë¤è¤ê¶¯¤¤Í¥ÀèÅÙ¤ò¤Ä¤±¤¿¤¤¾ì¹ç¤Ë¤Ï¡¢ + ³ç¸Ì¤ò»È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£

+ +

ÊÑ¿ô¤ä¥ª¥Ú¥ì¡¼¥¿¤È¤·¤Æǧ¼±¤µ¤ì¤Ê¤¤¤â¤Î¤Ï¤¹¤Ù¤Æʸ»úÎó¤È¤·¤Æ + °·¤ï¤ì¤Þ¤¹¡£Ê¸»úÎó¤Ï°úÍÑÉä¤Ç°Ï¤à¤³¤È¤â¤Ç¤­¤Þ¤¹: 'string' + ¤Î¤è¤¦¤Ë¡£°úÍÑÉä¤Ç°Ï¤Þ¤ì¤Æ¤¤¤Ê¤¤Ê¸»úÎó¤Ë¤Ï¶õÇò (¥¹¥Ú¡¼¥¹¤È¥¿¥Ö) + ¤ò´Þ¤á¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£¤½¤ì¤é¤ÏÊÑ¿ô¤Ê¤É¤Î¶ç¤òʬΥ¤¹¤ë¤¿¤á¤Ë + »È¤ï¤ì¤Æ¤¤¤ë¤«¤é¤Ç¤¹¡£Ê£¿ô¤Îʸ»úÎó¤¬Â³¤¤¤Æ¤¤¤ë¤È¤­¤Ï¡¢ + ¶õÇò¤ò´Ö¤ËÆþ¤ì¤Æ°ì¤Ä¤Ë¤¯¤Ã¤Ä¤±¤é¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢

+ +

string1    string2 ¤Ï string1 string2 ¤Ë¤Ê¤ê¤Þ¤¹¡£
+
+ ¤Þ¤¿¡¢
+
+ 'string1    string2' ¤Ï string1    string2 + ¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¿¿µ¶ÃÍɽ¸½¤ÎºÇŬ²½

+

¼°¤¬¤â¤Ã¤ÈÊ£»¨¤Ë¤Ê¤ê¡¢½èÍý¤Î®ÅÙÄã²¼¤¬¸²Ãø¤Ë¤Ê¤Ã¤¿¾ì¹ç¤Ï¡¢ + ɾ²Á¥ë¡¼¥ë¤Ë½¾¤Ã¤ÆºÇŬ²½¤·¤Æ¤ß¤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£

+
    +
  • ɾ²Á¤Ïº¸¤«¤é±¦¤Ë¸þ¤«¤Ã¤Æ¹Ô¤ï¤ì¤Þ¤¹¡£
    • +
  • ÆóÃÍ¿¿µ¶ÃÍ¥ª¥Ú¥ì¡¼¥¿ (&& ¤È ||) + ¤Ï¡¢½ÐÍè¤ë¸Â¤êûÍíɾ²Á¤µ¤ì¤Þ¤¹¡£¤Ä¤Þ¤ê·ë²Ì¤È¤·¤Æ¾åµ­¤Î¥ë¡¼¥ë¤Ï¡¢ + mod_include ¤¬º¸¤Îɾ²Á¼°¤òɾ²Á¤·¤Þ¤¹¡£ + º¸Â¦¤Ç·ë²Ì¤ò½½Ê¬·èÄê¤Ç¤­¤ë¾ì¹ç¤Ï¡¢É¾²Á¤Ï¤½¤³¤ÇÄä»ß¤·¤Þ¤¹¡£ + ¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤Ï±¦Â¦¤òɾ²Á¤·¤Æ¡¢º¸¤È±¦¤ÎξÊý¤«¤é·ë²Ì¤ò·×»»¤·¤Þ¤¹¡£
    • +
  • ûÍíɾ²Á¤Ïɾ²Á¤ÎÂоݤËÀµµ¬É½¸½¤¬´Þ¤Þ¤ì¤ë¾ì¹ç¡¢¥ª¥Õ¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¸åÊý»²¾È¤¹¤ëÊÑ¿ô ($1 .. $9) + ¤òËä¤á¤ë¤¿¤á¤Ë¡¢¼ÂºÝ¤Ëɾ²Á¤¹¤ëɬÍפ¬¤¢¤ë¤«¤é¤Ç¤¹¡£
    • +
+

ÆÃÄê¤Î¼°¤¬¤É¤Î¤è¤¦¤Ë°·¤ï¤ì¤ë¤«¤òÃΤꤿ¤¤¾ì¹ç¤Ï¡¢ + -DDEBUG_INCLUDE ¥³¥ó¥Ñ¥¤¥é¥ª¥×¥·¥ç¥ó¤òÉÕ¤±¤Æ + mod_include ¤ò¥ê¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤ÈÎɤ¤¤Ç¤·¤ç¤¦¡£ + ¤³¤ì¤Ë¤è¤ê¡¢Á´¤Æ¤Î¥Ñ¡¼¥¹¤µ¤ì¤¿¼°¤ËÂФ·¤Æ¡¢»ú¶ç²òÀϾðÊó¡¢ + ¥Ñ¡¼¥¹¥Ä¥ê¡¼¤È¡¢ + ¤½¤ì¤¬¤É¤Î¤è¤¦¤Ë¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤é¤ì¤¿½ÐÎϤޤÇɾ²Á¤µ¤ì¤¿¤«¤ò + ÁÞÆþ¤·¤Þ¤¹¡£

+
+
+
top
+

SSIEndTag ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:include Í×ÁǤò½ªÎ»¤µ¤»¤ëʸ»úÎó
¹½Ê¸:SSIEndTag tag
¥Ç¥Õ¥©¥ë¥È:SSIEndTag "-->"
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_include
¸ß´¹À­:2.0.30 °Ê¹ß¤ÇÍøÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï mod_include ¤¬Ãµ¤¹¡¢ + include Í×ÁǤνªÎ»¤ò¼¨¤¹Ê¸»úÎó¤òÊѹ¹¤·¤Þ¤¹¡£

+ +

Îã

+ SSIEndTag "%>" +

+ + +

»²¾È

+ +
+
top
+

SSIErrorMsg ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:SSI ¤Î¥¨¥é¡¼¤¬¤¢¤Ã¤¿¤È¤­¤Ëɽ¼¨¤µ¤ì¤ë¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸
¹½Ê¸:SSIErrorMsg message
¥Ç¥Õ¥©¥ë¥È:SSIErrorMsg "[an error occurred while processing this +directive]"
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_include
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.0.30 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

SSIErrorMsg ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï mod_include + ¤¬¥¨¥é¡¼¤¬µ¯¤³¤Ã¤¿¤È¤­¤Ëɽ¼¨¤¹¤ë¥á¥Ã¥»¡¼¥¸¤òÊѹ¹¤·¤Þ¤¹¡£¥×¥í¥À¥¯¥·¥ç¥ó¥µ¡¼¥Ð¤Ç¤Ï + ¥á¥Ã¥»¡¼¥¸¤¬¥æ¡¼¥¶¤Ëɽ¼¨¤µ¤ì¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë + ¥Ç¥Õ¥©¥ë¥È¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò "<!-- Error -->" + ¤ËÊѤ¨¤ë¤È¤¤¤¦¤è¤¦¤Ê¤³¤È¤ò¹Í¤¨¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï <!--#config + errmsg=message --> Í×ÁǤÈƱ¤¸¸ú²Ì¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Îã

+ SSIErrorMsg "<!-- Error -->" +

+ +
+
top
+

SSIStartTag ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:include Í×ÁǤò³«»Ï¤¹¤ëʸ»úÎó
¹½Ê¸:SSIStartTag tag
¥Ç¥Õ¥©¥ë¥È:SSIStartTag "<!--#"
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_include
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.0.30 °Ê¹ß¤Ç»ÈÍѲÄǽ
+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï mod_include ¤¬Ãµ¤¹¡¢include + Í×ÁǤγ«»Ï¤ò¼¨¤¹Ê¸»úÎó¤òÊѹ¹¤·¤Þ¤¹¡£

+ +

Æó¤Ä¤Î¥µ¡¼¥Ð¤Ç (¤â¤·¤«¤¹¤ë¤ÈÊÌ¡¹¤ÎÃʳ¬¤Ç) ¥Õ¥¡¥¤¥ë¤Î½ÐÎϤò²òÀϤ·¤Æ¤¤¤Æ¡¢ + ¤½¤ì¤¾¤ì¤Ë°ã¤¦¥³¥Þ¥ó¥É¤ò½èÍý¤µ¤»¤¿¤¤¡¢ + ¤È¤¤¤¦¤è¤¦¤Ê¤È¤­¤Ë¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤¤¤Þ¤¹¡£

+ +

Îã

+ SSIStartTag "<%"
+ SSIEndTag "%>" +

+ +

¾å¤ÎÎã¤Î¤è¤¦¤ËÂбþ¤¹¤ë + SSIEndTag ¤òÊ»¤»¤Æ»È¤¦¤È¡¢ + ²¼¤Ë¼¨¤¹Îã¤Î¤è¤¦¤Ë SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¨¤Þ¤¹:

+ +

°ã¤¦³«»Ï¤È½ªÎ»¤Î¥¿¥°¤ò»È¤Ã¤¿ SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ <%printenv %> +

+ +

»²¾È

+ +
+
top
+

SSITimeFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:ÆüÉÕ¤±¤ò¸½¤¹Ê¸»úÎó¤Î½ñ¼°¤òÀßÄꤹ¤ë
¹½Ê¸:SSITimeFormat formatstring
¥Ç¥Õ¥©¥ë¥È:SSITimeFormat "%A, %d-%b-%Y %H:%M:%S %Z"
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_include
¸ß´¹À­:2.0.30 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï DATE ´Ä¶­ÊÑ¿ô¤ò echo ¤·¤ÆÆüÉÕ¤ò¸½¤¹Ê¸»úÎó¤¬ + ɽ¼¨¤µ¤ì¤ë¤È¤­¤Î½ñ¼°¤òÊѹ¹¤·¤Þ¤¹¡£formatstring ¤Ï + C ɸ½à¥é¥¤¥Ö¥é¥ê¤Î strftime(3) ¤ÈƱ¤¸·Á¼°¤Ç¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï <!--#config + timefmt=formatstring --> Í×ÁǤÈƱ¤¸¸ú²Ì¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Îã

+ SSITimeFormat "%R, %B %d, %Y" +

+ +

¾å¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï¡¢ÆüÉÕ¤Ï "22:26, June 14, 2002" ¤È¤¤¤¦ + ·Á¼°¤Çɽ¼¨¤µ¤ì¤Þ¤¹¡£

+ +
+
top
+

SSIUndefinedEcho ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:̤ÄêµÁ¤ÎÊÑ¿ô¤¬ echo ¤µ¤ì¤¿¤È¤­¤Ëɽ¼¨¤µ¤ì¤ëʸ»úÎó
¹½Ê¸:SSIUndefinedEcho string
¥Ç¥Õ¥©¥ë¥È:SSIUndefinedEcho "(none)"
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_include
¸ß´¹À­:2.0.34 °Ê¹ß¤ÇÍøÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÊÑ¿ô¤¬ÄêµÁ¤µ¤ì¤Æ¤¤¤Ê¤¤¤Ë¤â´Ø¤ï¤é¤º + "echo" ¤µ¤ì¤¿¤È¤­¤Ë mod_include + ¤¬É½¼¨¤¹¤ëʸ»úÎó¤òÊѹ¹¤·¤Þ¤¹¡£

+ +

Îã

+ SSIUndefinedEcho "<!-- undef -->" +

+ +
+
top
+

XBitHack ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¼Â¹Ô¥Ó¥Ã¥È¤¬ÀßÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò +²òÀϤ¹¤ë
¹½Ê¸:XBitHack on|off|full
¥Ç¥Õ¥©¥ë¥È:XBitHack off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Options
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_include
+

XBitHack ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÄ̾ï¤Î HTML + ¥É¥­¥å¥á¥ó¥È¤Î²òÀϤòÀ©¸æ¤·¤Þ¤¹¡£¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï MIME ¥¿¥¤¥× + text/html ¤È´ØÏ¢ÉÕ¤±¤é¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Ë¤Î¤ß±Æ¶Á¤·¤Þ¤¹¡£ + XBitHack ¤Ï°Ê²¼¤ÎÃͤò¤È¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +
+
off
+
¼Â¹Ô²Äǽ¥Õ¥¡¥¤¥ë¤ËÂФ·¤ÆÆÃÊ̤ʰ·¤¤¤ò¤·¤Þ¤»¤ó¡£
+ +
on
+
¥æ¡¼¥¶¤Î¼Â¹Ô¥Ó¥Ã¥È¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë text/html + ¥Õ¥¡¥¤¥ë¤ÏÁ´¤Æ¥µ¡¼¥Ð¤Ç²òÀϤ¹¤ë html ¥É¥­¥å¥á¥ó¥È¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£
+ +
full
+
on ¤ÈƱÍͤǤ¹¤¬¡¢¥°¥ë¡¼¥×¼Â¹Ô¥Ó¥Ã¥È¤â¥Æ¥¹¥È¤·¤Þ¤¹¡£ + ¤â¤·¤½¤ì¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢ÊÖ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤Î Last-modified ¤Î + ÆüÉÕ¤ò¥Õ¥¡¥¤¥ë¤ÎºÇ½ª½¤Àµ»þ¹ï¤Ë¤·¤Þ¤¹¡£¤½¤ì¤¬ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ï¡¢ + last-modified ¤ÎÆüÉÕ¤ÏÁ÷¤é¤ì¤Þ¤»¤ó¡£¤³¤Î¥Ó¥Ã¥È¤òÀßÄꤹ¤ë¤È¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤ä¥×¥í¥­¥·¤¬¥ê¥¯¥¨¥¹¥È¤ò¥­¥ã¥Ã¥·¥å¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + +
Ãí°Õ ¾¤Î CGI ¤ò #include + ¤¹¤ë¤«¤â¤·¤ì¤Ê¤¤¤â¤Î¤ä¡¢³Æ¥¢¥¯¥»¥¹¤ËÂФ·¤Æ°ã¤¦½ÐÎϤòÀ¸À®¤¹¤ë + (¤â¤·¤¯¤Ï¸å¤Î¥ê¥¯¥¨¥¹¥È¤ÇÊѤï¤ë¤«¤â¤·¤ì¤Ê¤¤¤â¤Î) + ¤¹¤Ù¤Æ¤Î SSI ¥¹¥¯¥ê¥×¥È¤ËÂФ·¤Æ¥°¥ë¡¼¥×¼Â¹Ô¥Ó¥Ã¥È¤¬ + ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤³¤È¤ò³Îǧ¤Ç¤­¤Ê¤¤¾ì¹ç¤Ï¡¢full ¤Ï»È¤ï¤Ê¤¤Êý¤¬Îɤ¤ + ¤Ç¤·¤ç¤¦¡£
+
+
+ + +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_info.html b/docs/manual/mod/mod_info.html new file mode 100644 index 00000000..84991103 --- /dev/null +++ b/docs/manual/mod/mod_info.html @@ -0,0 +1,11 @@ +URI: mod_info.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_info.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_info.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_info.html.en b/docs/manual/mod/mod_info.html.en new file mode 100644 index 00000000..add438f6 --- /dev/null +++ b/docs/manual/mod/mod_info.html.en @@ -0,0 +1,194 @@ + + + +mod_info - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_info

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Provides a comprehensive overview of the server +configuration
Status:Extension
Module Identifier:info_module
Source File:mod_info.c
+

Summary

+ +

To configure mod_info, add the following to your + httpd.conf file.

+ +

+ <Location /server-info>
+ + SetHandler server-info
+ + </Location> +

+ +

You may wish to use mod_access inside the + <Location> + directive to limite access to your server configuration + information:

+ +

+ <Location /server-info>
+ + SetHandler server-info
+ Order deny,allow
+ Deny from all
+ Allow from yourcompany.com
+ + </Location> +

+ +

Once configured, the server information is obtained by + accessing http://your.host.example.com/server-info

+
+ +
top
+
+

Security Issues

+

Once mod_info is loaded into the server, its + handler capability is available in all configuration + files, including per-directory files (e.g., + .htaccess). This may have security-related + ramifications for your site.

+ +

In particular, this module can leak sensitive information + from the configuration directives of other Apache modules such as + system paths, usernames/passwords, database names, etc. Therefore, + this module should only be + used in a controlled environment and always with caution.

+ +

You will probably want to use mod_authz_host + to limit access to your server configuration information.

+ +

Access control

+ <Location /server-info>
+ + SetHandler server-info
+ Order allow,deny
+ # Allow access from server itself
+ Allow from 127.0.0.1
+ # Additionally, allow access from local workstation
+ Allow from 192.168.1.17
+ + </Location> +

+
top
+
+

Selecting the information shown

+

By default, the server information includes a list of + all enabled modules, and for each module, a description of + the directives understood by that module, the hooks implemented + by that module, and the relevant directives from the current + configuration.

+ +

Other views of the configuration information are available by + appending a query to the server-info request. For + example, http://your.host.example.com/server-info?config + will show all configuration directives.

+ +
+
?<module-name>
+
Only information relevant to the named module
+
?config
+
Just the configuration directives, not sorted by module
+
?hooks
+
Only the list of Hooks each module is attached to
+
?list
+
Only a simple list of enabled modules
+
?server
+
Only the basic server information
+
+
top
+
+

Known Limitations

+

mod_info provides its information by reading the + parsed configuration, rather than reading the original configuration + file. There are a few limitations as a result of the way the parsed + configuration tree is created:

+
    +
  • Directives which are executed immediately rather than being + stored in the parsed configuration are not listed. These include + ServerRoot, + LoadModule, and + LoadFile.
    • +
  • Directives which control the configuration file itself, such as + Include, + <IfModule> and + <IfDefine> are not + listed, but the included configuration directives are.
    • +
  • Comments are not listed. (This may be considered a feature.)
    • +
  • Configuration directives from .htaccess files are + not listed (since they do not form part of the permanent server + configuration).
    • +
  • Container directives such as + <Directory> + are listed normally, but mod_info cannot figure + out the line number for the closing + </Directory>.
    • +
  • Directives generated by third party modules such as mod_perl + might not be listed.
    • +
+
+
top
+

AddModuleInfo Directive

+ + + + + + + +
Description:Adds additional information to the module +information displayed by the server-info handler
Syntax:AddModuleInfo module-name string
Context:server config, virtual host
Status:Extension
Module:mod_info
Compatibility:Apache 1.3 and above
+

This allows the content of string to be shown as + HTML interpreted, Additional Information for + the module module-name. Example:

+ +

+ AddModuleInfo mod_deflate.c 'See <a \
+ + href="http://www.apache.org/docs/2.2/mod/mod_deflate.html">\
+ http://www.apache.org/docs/2.2/mod/mod_deflate.html</a>' + +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_info.html.ja.euc-jp b/docs/manual/mod/mod_info.html.ja.euc-jp new file mode 100644 index 00000000..7c05e4dc --- /dev/null +++ b/docs/manual/mod/mod_info.html.ja.euc-jp @@ -0,0 +1,188 @@ + + + +mod_info - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_info

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:¥µ¡¼¥Ð¤ÎÀßÄê¤ÎÊñ³çŪ¤Ê³µ´Ñ¤òÄ󶡤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:info_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_info.c
+

³µÍ×

+ +

mod_info ¤òÀßÄꤹ¤ë¤Ë¤Ï¡¢°Ê²¼¤ò httpd.conf + ¥Õ¥¡¥¤¥ë¤Ë²Ã¤¨¤Þ¤¹¡£

+ +

+ <Location /server-info>
+ + SetHandler server-info
+ + </Location> +

+ +

<Location> + ¤ÎÃæ¤Ç mod_access ¤ò»È¤Ã¤Æ¡¢¥µ¡¼¥ÐÀßÄê¾ðÊó¤Ø¤Î + ¥¢¥¯¥»¥¹¤òÀ©¸Â¤·¤¿¤¤¤È»×¤¦¤«¤â¤·¤ì¤Þ¤»¤ó :

+ +

+ <Location /server-info>
+ + SetHandler server-info
+ Order deny,allow
+ Deny from all
+ Allow from yourcompany.com
+ + </Location> +

+ +

°ìöÀßÄꤹ¤ë¤È¡¢http://your.host.example.com/server-info + ¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤Ç¥µ¡¼¥Ð¤Î¾ðÊó¤òÆÀ¤é¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

¥È¥Ô¥Ã¥¯

+
+
top
+
+

Security Issues

+

°ìö mod_info ¤¬¥µ¡¼¥Ð¤ËÆɤ߹þ¤Þ¤ì¤ë¤È¡¢ + Ä󶡤·¤Æ¤¤¤ë¥Ï¥ó¥É¥éµ¡Ç½¤Ï¥Ç¥£¥ì¥¯¥È¥êËè¤ÎÀßÄê¥Õ¥¡¥¤¥ë (Î㤨¤Ð + .htaccess) ¤ò´Þ¤à ¤¹¤Ù¤Æ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ÇÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤Î¥â¥¸¥å¡¼¥ë¤òÍ­¸ú¤Ë¤¹¤ë¤È¤­¤Ï¥»¥­¥å¥ê¥Æ¥£¤ÎÌäÂê¤ò¹Íθ¤¹¤ëɬÍפ¬ + ¤¢¤ë¤Ç¤·¤ç¤¦¡£

+ +

Æäˡ¢¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥·¥¹¥Æ¥à¥Ñ¥¹¡¢¥æ¡¼¥¶Ì¾/¥Ñ¥¹¥ï¡¼¥É¡¢ + ¥Ç¡¼¥¿¥Ù¡¼¥¹Ì¾¤Ê¤É¡¢Â¾¤Î Apache ¥â¥¸¥å¡¼¥ë¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤«¤é + ¥»¥­¥å¥ê¥Æ¥£¾åÈù̯¤Ê¾ðÊó¤òϳ¤é¤¹²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¤­¤Á¤ó¤È¥¢¥¯¥»¥¹À©¸æ¤µ¤ì¤¿´Ä¶­¤Ç¤Î¤ß¡¢ + Ãí°Õ¤·¤Æ»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£

+ +

ÀßÄê¾ðÊó¤Ø¤Î¥¢¥¯¥»¥¹¤òÀ©¸Â¤¹¤ë¤¿¤á¤Ë¡¢mod_authz_host ¤ò + »È¤¦¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

+ +

¥¢¥¯¥»¥¹À©¸æ

+ <Location /server-info>
+ + SetHandler server-info
+ Order allow,deny
+ # Allow access from server itself
+ Allow from 127.0.0.1
+ # Additionally, allow access from local workstation
+ Allow from 192.168.1.17
+ + </Location> +

+
top
+
+

ɽ¼¨¤µ¤ì¤ë¾ðÊó¤ÎÁªÂò

+

¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥µ¡¼¥Ð¾ðÊó¤Ï¤¹¤Ù¤Æ¤ÎÍ­¸ú¤Ê¥â¥¸¥å¡¼¥ë¤È¡¢ + ³Æ¥â¥¸¥å¡¼¥ë¤Ë¤Ä¤¤¤Æ¡¢¥â¥¸¥å¡¼¥ë¤¬Íý²ò¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢ + ¼ÂÁõ¤·¤Æ¤¤¤ë¡¢¥Õ¥Ã¥¯¡¢¸½»þÅÀ¤Ç¤ÎÀßÄê¤Î´ØÏ¢¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë + ¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

server-info ¥ê¥¯¥¨¥¹¥È¤Ø¥¯¥¨¥ê¡¼¤òÄɲ乤뤳¤È¤Ç¡¢ + ÀßÄê¾ðÊó¤Î¾¤Îɽ¼¨·Á¼°¤òÁª¤Ö¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¡¢ + http://your.host.example.com/server-info?config ¤Ï + ¤¹¤Ù¤Æ¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òɽ¼¨¤·¤Þ¤¹¡£

+ +
+
?<module-name>
+
»ØÄꤵ¤ì¤¿¥â¥¸¥å¡¼¥ë¤Ë´ØÏ¢¤¹¤ë¾ðÊó¤Î¤ß
+
?config
+
¥â¥¸¥å¡¼¥ë¤Ç¥½¡¼¥È¤»¤º¤Ë¡¢ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¤ß
+
?hooks
+
³Æ¥â¥¸¥å¡¼¥ë¤¬»ÈÍѤ¹¤ë¥Õ¥Ã¥¯¤Î¤ß
+
?list
+
Í­¸ú¤Ê¥â¥¸¥å¡¼¥ë¤Î´Êñ¤Ê¥ê¥¹¥È¤Î¤ß
+
?server
+
´ðËÜ¥µ¡¼¥Ð¾ðÊó¤Î¤ß
+
+
top
+
+

´ûÃΤÎÀ©¸Â

+

mod_info ¤Ï¡¢¸µ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤òÆɤà¤Î¤Ç¤Ï¤Ê¤¯¡¢ + ´û¤Ë¥Ñ¡¼¥¹¤µ¤ì¤¿ÀßÄê¤òÆɤ߹þ¤à¤³¤È¤Ç¾ðÊó¤òÄ󶡤·¤Þ¤¹¡£½¾¤Ã¤Æ¡¢ + ¥Ñ¡¼¥¹ºÑ¤ß¤ÎÀßÄê¾ðÊó¤ÎÌÚ¤¬À¸À®¤µ¤ì¤ëÊýË¡¤Ë¤è¤ëÀ©¸Â¤¬¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹:

+
    +
  • ¥Ñ¡¼¥¹¤µ¤ì¤¿ÀßÄê¤ËÊݸ¤µ¤ì¤º¤Ë¡¢¤¹¤°¤Ë¼Â¹Ô¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + °ìÍ÷¤Ë¸½¤ì¤Þ¤»¤ó¡£¤³¤ì¤Ë¤Ï + ServerRoot, + LoadModule, + LoadFile ¤¬¤¢¤ê¤Þ¤¹¡£
    • +
  • Include, + <IfModule>, + <IfDefine>, + ¤Î¤è¤¦¤ÊÀßÄê¥Õ¥¡¥¤¥ë¼«¿È¤òÀ©¸æ¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïɽ¼¨¤µ¤ì¤Þ¤»¤ó¡£ + ¤½¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃæ¤Ë¤¢¤ê¡¢Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ɽ¼¨¤µ¤ì¤Þ¤¹¡£
    • +
  • ¥³¥á¥ó¥È¤Ïɽ¼¨¤µ¤ì¤Þ¤»¤ó¡£(¤³¤ì¤Ï»ÅÍͤÀ¤È»×¤Ã¤Æ¤¯¤À¤µ¤¤¡£)
    • +
  • .htaccess ¥Õ¥¡¥¤¥ë¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïɽ¼¨¤µ¤ì¤Þ¤»¤ó + (±Êµ×Ū¤Ê¥µ¡¼¥ÐÀßÄê¤Î°ìÉô¤Ç¤Ï¤Ê¤¤¤«¤é¤Ç¤¹)¡£
    • +
  • <Directory> + ¤Î¤è¤¦¤Ê¥³¥ó¥Æ¥Ê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÉáÄ̤Ëɽ¼¨¤µ¤ì¤Þ¤¹¤¬¡¢ + mod_info ¤ÏÊĤ¸¥¿¥°¤Î </Directory> ¤Ê¤É¤Î¿ô¤òÃΤ뤳¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£
    • +
  • mod_perl ¤Î¤è¤¦¤Ê¥µ¡¼¥É¥Ñ¡¼¥Æ¥£¥â¥¸¥å¡¼¥ë + ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïɽ¼¨¤µ¤ì¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
    • +
+
+
top
+

AddModuleInfo ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:server-info ¥Ï¥ó¥É¥é¤Ë¤è¤êɽ¼¨¤µ¤ì¤ë¥â¥¸¥å¡¼¥ë¤Î¾ðÊó¤Ë +ÄɲäξðÊó¤òÉÕ¤±²Ã¤¨¤ë
¹½Ê¸:AddModuleInfo module-name string
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_info
¸ß´¹À­:Apache 1.3 °Ê¹ß
+

¤³¤ì¤Ï¡¢string ¤ÎÆâÍƤ¬¥â¥¸¥å¡¼¥ë module-name + ¤ÎÄɲþðÊó ¤È¤·¤Æ HTML + ¤È¤·¤Æ²ò¼á¤µ¤ì¡¢É½¼¨¤µ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£Îã:

+ +

+ AddModuleInfo mod_deflate.c 'See <a \
+ + href="http://www.apache.org/docs/2.2/mod/mod_deflate.html">\
+ http://www.apache.org/docs/2.2/mod/mod_deflate.html</a>' + +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_info.html.ko.euc-kr b/docs/manual/mod/mod_info.html.ko.euc-kr new file mode 100644 index 00000000..ae6bb572 --- /dev/null +++ b/docs/manual/mod/mod_info.html.ko.euc-kr @@ -0,0 +1,169 @@ + + + +mod_info - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_info

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:¼­¹ö ¼³Á¤¿¡ ´ëÇÑ Á¾ÇÕÀûÀÎ Á¤º¸¸¦ º¸¿©ÁØ´Ù
»óÅÂ:Extension
¸ðµâ¸í:info_module
¼Ò½ºÆÄÀÏ:mod_info.c
+

¿ä¾à

+ +

mod_info¸¦ »ç¿ëÇÏ·Á¸é httpd.conf + ÆÄÀÏ¿¡ ´ÙÀ½°ú °°ÀÌ Ãß°¡ÇÑ´Ù.

+ +

+ <Location /server-info>
+ + SetHandler server-info
+ + </Location> +

+ +

ÀÌ·¸°Ô ¼³Á¤Çϸé + http://your.host.example.com/server-info¿¡ + Á¢±ÙÇÏ¿© ¼­¹ö¿¡ ´ëÇÑ Á¤º¸¸¦ º¼ ¼ö ÀÖ´Ù.

+
+ +
top
+
+

º¸¾È ¹®Á¦

+

Çѹø ¼­¹ö°¡ mod_info¸¦ ÀоîµéÀ̸é, µð·ºÅ丮º° + ¼³Á¤ÆÄÀÏ(¿¹¸¦ µé¾î, .htaccess)À» Æ÷ÇÔÇÑ + ¸ðµç ¼³Á¤ÆÄÀÏ¿¡¼­ ÀÌ Çڵ鷯 ±â´ÉÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. + ±×·¡¼­ »çÀÌÆ®¿¡ º¸¾È°ü·Ã ¹®Á¦°¡ µÉ ¼ö ÀÖ´Ù.

+ +

ƯÈ÷ ÀÌ ¸ðµâÀº ½Ã½ºÅÛ °æ·Î, »ç¿ëÀÚ¸í/¾ÏÈ£, µ¥ÀÌÅͺ£À̽º + À̸§°ú °°ÀÌ ¿©·¯ ¾ÆÆÄÄ¡ ¸ðµâÀÇ ¼³Á¤Áö½Ã¾î¿¡ ±â·ÏÇÑ ¹Î°¨ÇÑ + Á¤º¸¸¦ À¯ÃâÇÒ ¼ö ÀÖ´Ù. ±×·¡¼­ ÀÌ ¸ðµâÀº Ç×»ó ÁÖÀÇÇØ¾ß Çϸç + ÅëÁ¦µÈ ȯ°æ¿¡¼­¸¸ »ç¿ëÇØ¾ß ÇÑ´Ù.

+ +

´ÙÀ½°ú °°ÀÌ mod_authz_host¸¦ »ç¿ëÇÏ¿© + ¼­¹ö ¼³Á¤ Á¤º¸¿¡ ´ëÇÑ Á¢±ÙÀ» Á¦ÇÑÇÒ ¼ö ÀÖ´Ù.

+ +

Á¢±Ù Á¦¾î

+ <Location /server-info>
+ + SetHandler server-info
+ Order allow,deny
+ # ÀÚ½ÅÀ¸·Î ºÎÅÍ Á¢±Ù Çã°¡
+ Allow from 127.0.0.1
+ # Ãß°¡·Î, ±Ùó¿¡ ÀÖ´Â ¿öÅ©½ºÅ×À̼ÇÀ¸·Î ºÎÅÍ Á¢±Ù Çã°¡
+ Allow from 192.168.1.17
+ + </Location> +

+
top
+
+

º¸¿©ÁÖ´Â Á¤º¸ ¼±ÅÃÇϱâ

+

±âº»ÀûÀ¸·Î ¼­¹ö Á¤º¸¿¡´Â »ç¿ëÇÏ´Â ¸ðµâ ¸ñ·Ï°ú ¸ðµâº°·Î + ¸ðµâÀÌ ÀÌÇØÇÏ´Â Áö½Ã¾î ¼³¸í, ¸ðµâÀÌ ±¸ÇöÇÑ ÈÅ(hook), ÇöÀç + ¼³Á¤¿¡¼­ »ç¿ëÇÑ Áö½Ã¾î Á¤º¸°¡ ÀÖ´Ù.

+ +

server-info ¿äû¿¡ ÁúÀǹ®ÀÚ¿­À» ºÙ¿©¼­ ¼³Á¤ + Á¤º¸¸¦ ´Ù¸£°Ô º¼ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, + http://your.host.example.com/server-info?config´Â + ¸ðµç ¼³Á¤Áö½Ã¾î¸¦ º¸¿© ÁØ´Ù.

+ +
+
?<module-name>
+
¸í½ÃÇÑ ¸ðµâ¿¡ ´ëÇÑ Á¤º¸¸¸
+
?config
+
¸ðµâº°·Î Á¤·ÄÇÏÁö ¾Ê°í, ¼³Á¤Áö½Ã¾î¸¸
+
?hooks
+
¸ðµâÀÌ µî·ÏÇÑ ÈÅ(hook) ¸ñ·Ï¸¸
+
?list
+
»ç¿ëÇÏ´Â ¸ðµâ ¸ñ·Ï¸¸
+
?server
+
±âº» ¼­¹ö Á¤º¸¸¸
+
+
top
+
+

¾Ë·ÁÁø ÇÑ°è

+

mod_info´Â ¿ø·¡ ¼³Á¤ÆÄÀÏÀ» ÀÐÁö ¾Ê°í + ÀÌ¹Ì ÀоîµéÀÎ ¼³Á¤ Á¤º¸¸¦ Âü°íÇÏ¿© Á¤º¸¸¦ º¸¿©ÁØ´Ù. ¼³Á¤À» + ÆĽÌÇÏ´Â ¹æ¹ý¶§¹®¿¡ ´ÙÀ½°ú °°Àº ¸î°¡Áö ÇÑ°è°¡ ÀÖ´Ù.

+
    +
  • ÆĽÌÇÑ ¼³Á¤ Á¤º¸¿¡ ±â·ÏÇÏÁö ¾Ê°í Áï½Ã ½ÇÇàµÇ´Â Áö½Ã¾î¸¦ + º¸¿©ÁÖÁö ¸øÇÑ´Ù. ServerRoot, LoadModule, LoadFile°ú °°Àº Áö½Ã¾î°¡ + ¿©±â¿¡ ÇØ´çÇÑ´Ù.
    • +
  • Include, <IfModule>, <IfDefine>°ú °°ÀÌ + ¼³Á¤ÆÄÀÏ ÀÚü¸¦ Á¶Á¤ÇÏ´Â Áö½Ã¾î¸¦ º¸¿©ÁÖÁö ¸øÇÑ´Ù. + ±×·¯³ª ¾È¿¡ ÀÖ´Â ¼³Á¤Áö½Ã¾î´Â º¸¿©ÁØ´Ù.
    • +
  • ÁÖ¼®À» º¸¿©ÁÖÁö ¸øÇÑ´Ù. (ÇÑ°è¶ó±â º¸´Ù´Â ±â´ÉÀ̶ó°í + »ý°¢ÇÒ ¼ö ÀÖ´Ù.)
    • +
  • (Áö¼ÓÀûÀÎ ¼­¹ö¼³Á¤ÀÌ ¾Æ´Ï±â ¶§¹®¿¡) .htaccess + ÆÄÀÏ¿¡ ÀÖ´Â ¼³Á¤Áö½Ã¾î¸¦ º¸¿©ÁÖÁö ¸øÇÑ´Ù.
    • +
  • º¸Åë <Directory>¿Í + °°Àº ¹üÀ§Á¦ÇÑ Áö½Ã¾î´Â º¸¿©ÁÖÁö¸¸, + mod_info´Â ¸¶Ä¡´Â </Directory>ÀÇ ÁÙ¹øÈ£¸¦ + ¾Ë ¼ö ¾ø´Ù.
    • +
  • mod_perl°ú °°ÀÌ Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀÇ + Áö½Ã¾î¸¦ º¸¿©ÁÖÁö ¸øÇÒ ¼ö ÀÖ´Ù.
    • +
+
+
top
+

AddModuleInfo Áö½Ã¾î

+ + + + + + + +
¼³¸í:¸ðµâ¿¡ ´ëÇÑ Ãß°¡ Á¤º¸¸¦ server-info Çڵ鷯°¡ º¸¿©ÁÖµµ·Ï +Ãß°¡ÇÑ´Ù
¹®¹ý:AddModuleInfo module-name string
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Extension
¸ðµâ:mod_info
Áö¿ø:¾ÆÆÄÄ¡ 1.3 ÀÌÈÄ
+

module-name ¸ðµâ¿¡ ´ëÇÑ Ãß°¡ Á¤º¸·Î + stringÀÇ ³»¿ëÀ» HTML·Î º¸¿©ÁØ´Ù. ¿¹¸¦ µé¾î,

+ +

+ AddModuleInfo mod_deflate.c 'See <a \
+ + href="http://www.apache.org/docs/2.2/mod/mod_deflate.html">\
+ http://www.apache.org/docs/2.2/mod/mod_deflate.html</a>' + +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_isapi.html b/docs/manual/mod/mod_isapi.html new file mode 100644 index 00000000..6d92c773 --- /dev/null +++ b/docs/manual/mod/mod_isapi.html @@ -0,0 +1,7 @@ +URI: mod_isapi.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_isapi.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_isapi.html.en b/docs/manual/mod/mod_isapi.html.en new file mode 100644 index 00000000..5195df71 --- /dev/null +++ b/docs/manual/mod/mod_isapi.html.en @@ -0,0 +1,343 @@ + + + +mod_isapi - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_isapi

+
+

Available Languages:  en  | + ko 

+
+ + + + +
Description:ISAPI Extensions within Apache for Windows
Status:Base
Module Identifier:isapi_module
Source File:mod_isapi.c
Compatibility:Win32 only
+

Summary

+ +

This module implements the Internet Server extension API. It + allows Internet Server extensions (e.g. ISAPI .dll + modules) to be served by Apache for Windows, subject to the + noted restrictions.

+ +

ISAPI extension modules (.dll files) are written by third + parties. The Apache Group does not author these modules, so we + provide no support for them. Please contact the ISAPI's author + directly if you are experiencing problems running their ISAPI + extension. Please do not post such problems to + Apache's lists or bug reporting pages.

+
+ +
top
+
+

Usage

+ +

In the server configuration file, use + the AddHandler directive to + associate ISAPI files with the isapi-handler handler, and map + it to them with their file extensions. To enable any .dll file to be + processed as an ISAPI extension, edit the httpd.conf file and add the + following line:

+

+ AddHandler isapi-handler .dll +

+ +
In older versions of the Apache server, + isapi-isa was the proper handler name, rather than + isapi-handler. For compatibility, configurations may + continue using isapi-isa through all versions of Apache + prior to 2.3.0.
+ +

There is no capability within the Apache server to leave a + requested module loaded. However, you may preload and keep a + specific module loaded by using the following syntax in your + httpd.conf:

+

+ ISAPICacheFile c:/WebWork/Scripts/ISAPI/mytest.dll +

+ +

Whether or not you have preloaded an ISAPI extension, all + ISAPI extensions are governed by the same permissions and + restrictions as CGI scripts. That is, Options ExecCGI must be set for the + directory that contains the ISAPI .dll file.

+ +

Review the Additional Notes and the Programmer's Journal for additional details + and clarification of the specific ISAPI support offered by + mod_isapi.

+
top
+
+

Additional Notes

+ +

Apache's ISAPI implementation conforms to all of the ISAPI + 2.0 specification, except for some "Microsoft-specific" + extensions dealing with asynchronous I/O. Apache's I/O model + does not allow asynchronous reading and writing in a manner + that the ISAPI could access. If an ISA tries to access + unsupported features, including async I/O, a message is placed + in the error log to help with debugging. Since these messages + can become a flood, the directive ISAPILogNotSupported + Off exists to quiet this noise.

+ +

Some servers, like Microsoft IIS, load the ISAPI extension + into the server and keep it loaded until memory usage is too + high, or unless configuration options are specified. Apache + currently loads and unloads the ISAPI extension each time it is + requested, unless the ISAPICacheFile directive is specified. + This is inefficient, but Apache's memory model makes this the + most effective method. Many ISAPI modules are subtly + incompatible with the Apache server, and unloading these + modules helps to ensure the stability of the server.

+ +

Also, remember that while Apache supports ISAPI Extensions, + it does not support ISAPI Filters. Support for + filters may be added at a later date, but no support is planned + at this time.

+
top
+
+

Programmer's Journal

+ +

If you are programming Apache 2.0 mod_isapi + modules, you must limit your calls to ServerSupportFunction + to the following directives:

+ +
+
HSE_REQ_SEND_URL_REDIRECT_RESP
+
Redirect the user to another location.
+ This must be a fully qualified URL (e.g. + http://server/location).
+ +
HSE_REQ_SEND_URL
+
Redirect the user to another location.
+ This cannot be a fully qualified URL, you are not allowed to + pass the protocol or a server name (e.g. simply + /location).
+ This redirection is handled by the server, not the + browser.
+

Warning

+

In their recent documentation, Microsoft appears to have + abandoned the distinction between the two + HSE_REQ_SEND_URL functions. Apache continues to treat + them as two distinct functions with different requirements + and behaviors.

+
+ +
HSE_REQ_SEND_RESPONSE_HEADER
+
Apache accepts a response body following the header if it + follows the blank line (two consecutive newlines) in the + headers string argument. This body cannot contain NULLs, + since the headers argument is NULL terminated.
+ +
HSE_REQ_DONE_WITH_SESSION
+
Apache considers this a no-op, since the session will be + finished when the ISAPI returns from processing.
+ +
HSE_REQ_MAP_URL_TO_PATH
+
Apache will translate a virtual name to a physical + name.
+ +
HSE_APPEND_LOG_PARAMETER
+
+ This logged message may be captured in any of the following + logs: + + + +

The first option, the %{isapi-parameter}n component, + is always available and preferred.

+
+ +
HSE_REQ_IS_KEEP_CONN
+
Will return the negotiated Keep-Alive status.
+ +
HSE_REQ_SEND_RESPONSE_HEADER_EX
+
Will behave as documented, although the fKeepConn + flag is ignored.
+ +
HSE_REQ_IS_CONNECTED
+
Will report false if the request has been aborted.
+
+ +

Apache returns FALSE to any unsupported call to + ServerSupportFunction, and sets the + GetLastError value to + ERROR_INVALID_PARAMETER.

+ +

ReadClient retrieves the request body exceeding the + initial buffer (defined by ISAPIReadAheadBuffer). Based on the + ISAPIReadAheadBuffer setting (number of bytes + to buffer prior to calling the ISAPI handler) shorter requests are sent + complete to the extension when it is invoked. If the request is + longer, the ISAPI extension must use ReadClient to + retrieve the remaining request body.

+ +

WriteClient is supported, but only with the + HSE_IO_SYNC flag or no option flag (value of + 0). Any other WriteClient request + will be rejected with a return value of FALSE, and a + GetLastError value of + ERROR_INVALID_PARAMETER.

+ +

GetServerVariable is supported, although extended server + variables do not exist (as defined by other servers.) All the + usual Apache CGI environment variables are available from + GetServerVariable, as well as the ALL_HTTP + and ALL_RAW values.

+ +

Apache 2.0 mod_isapi supports additional + features introduced in later versions of the ISAPI specification, + as well as limited emulation of async I/O and the + TransmitFile semantics. Apache also supports preloading + ISAPI .dlls for performance, neither of which were not available under + Apache 1.3 mod_isapi.

+
+
top
+

ISAPIAppendLogToErrors Directive

+ + + + + + + + +
Description:Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the error log
Syntax:ISAPIAppendLogToErrors on|off
Default:ISAPIAppendLogToErrors off
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_isapi
+

Record HSE_APPEND_LOG_PARAMETER requests from ISAPI + extensions to the server error log.

+ +
+
top
+

ISAPIAppendLogToQuery Directive

+ + + + + + + + +
Description:Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the query field
Syntax:ISAPIAppendLogToQuery on|off
Default:ISAPIAppendLogToQuery on
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_isapi
+

Record HSE_APPEND_LOG_PARAMETER requests from ISAPI + extensions to the query field (appended to the CustomLog %q + component).

+ +
+
top
+

ISAPICacheFile Directive

+ + + + + + +
Description:ISAPI .dll files to be loaded at startup
Syntax:ISAPICacheFile file-path [file-path] +...
Context:server config, virtual host
Status:Base
Module:mod_isapi
+

Specifies a space-separated list of file names to be loaded + when the Apache server is launched, and remain loaded until the + server is shut down. This directive may be repeated for every + ISAPI .dll file desired. The full path name of each file should + be specified. If the path name is not absolute, it will be treated + relative to ServerRoot.

+ +
+
top
+

ISAPIFakeAsync Directive

+ + + + + + + + +
Description:Fake asynchronous support for ISAPI callbacks
Syntax:ISAPIFakeAsync on|off
Default:ISAPIFakeAsync off
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_isapi
+

While set to on, asynchronous support for ISAPI callbacks is + simulated.

+ +
+
top
+

ISAPILogNotSupported Directive

+ + + + + + + + +
Description:Log unsupported feature requests from ISAPI +extensions
Syntax:ISAPILogNotSupported on|off
Default:ISAPILogNotSupported off
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_isapi
+

Logs all requests for unsupported features from ISAPI + extensions in the server error log. This may help administrators + to track down problems. Once set to on and all desired ISAPI modules + are functioning, it should be set back to off.

+ +
+
top
+

ISAPIReadAheadBuffer Directive

+ + + + + + + + +
Description:Size of the Read Ahead Buffer sent to ISAPI +extensions
Syntax:ISAPIReadAheadBuffer size
Default:ISAPIReadAheadBuffer 49152
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_isapi
+

Defines the maximum size of the Read Ahead Buffer sent to + ISAPI extensions when they are initially invoked. All remaining + data must be retrieved using the ReadClient callback; some + ISAPI extensions may not support the ReadClient function. + Refer questions to the ISAPI extension's author.

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_isapi.html.ko.euc-kr b/docs/manual/mod/mod_isapi.html.ko.euc-kr new file mode 100644 index 00000000..e67b37f8 --- /dev/null +++ b/docs/manual/mod/mod_isapi.html.ko.euc-kr @@ -0,0 +1,319 @@ + + + +mod_isapi - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_isapi

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:Windows¿ë ¾ÆÆÄÄ¡¿¡¼­ ISAPI Extension »ç¿ë
»óÅÂ:Base
¸ðµâ¸í:isapi_module
¼Ò½ºÆÄÀÏ:mod_isapi.c
Áö¿ø:Win32 only
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº Internet Server extension API¸¦ ±¸ÇöÇÑ´Ù. ±×·¡¼­ + Á¦¾àÀº ÀÖÁö¸¸ Windows¿ë ¾ÆÆÄÄ¡¿¡¼­ Internet Server extensionÀ» + (Áï, ISAPI .dll ¸ðµâ) »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

ISAPI extension ¸ðµâ(.dll ÆÄÀÏ)Àº Á¦»ïÀÚ°¡ ÀÛ¼ºÇÑ´Ù. + Apache GroupÀÌ ÀÌµé ¸ðµâÀ» ¸¸µéÁö ¾Ê¾ÒÀ¸¸ç, Áö¿øµµ ÇÏÁö + ¾Ê´Â´Ù. ISAPI extension »ç¿ë¿¡ °üÇÑ ¹®Á¦´Â ISAPI Á¦ÀÛÀÚ¿¡°Ô + Á÷Á¢ ¿¬¶ôÇÏ±æ ¹Ù¶õ´Ù. Á¦¹ß ÀÌ·± ¹®Á¦¸¦ ¾ÆÆÄÄ¡ + ¸ÞÀϸµ¸®½ºÆ®³ª ¹ö±×º¸°í ÆäÀÌÁö¿¡ ¿Ã¸®Áö ¸¶¶ó.

+
+ +
top
+
+

»ç¿ë¹ý

+ +

¼­¹ö¼³Á¤ÆÄÀÏ¿¡¼­ AddHandler Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + ISAPI ÆÄÀÏ È®ÀåÀÚ¿Í isapi-handler Çڵ鷯¸¦ ¿¬°áÇÑ´Ù. + .dll ÆÄÀÏÀ» ISAPI extensionÀ¸·Î ó¸®ÇÏ·Á¸é httpd.conf ÆÄÀÏ¿¡ + ´ÙÀ½°ú °°ÀÌ Ãß°¡ÇÑ´Ù.

+

+ AddHandler isapi-handler .dll +

+ +

¾ÆÆÄÄ¡ ¼­¹ö´Â ¿äûÇÑ ¸ðµâÀ» ¸Þ¸ð¸®¿¡ °è¼Ó µÑ ¼ö ¾ø´Ù. + ±×·¯³ª httpd.conf¿¡¼­ ´ÙÀ½°ú °°Àº ¼³Á¤À¸·Î ƯÁ¤ ¸ðµâÀ» ¹Ì¸® + ÀоîµéÀÏ ¼ö´Â ÀÖ´Ù.

+

+ ISAPICacheFile c:/WebWork/Scripts/ISAPI/mytest.dll +

+ +

ISAPI extensionÀ» ¹Ì¸® ÀоîµéÀÌ´øÁö ¹Ì¸® ÀоîµéÀÌÁö ¾Ê´øÁö + °ü°è¾øÀÌ ISAPI extensionÀº CGI ½ºÅ©¸³Æ®¿Í µ¿ÀÏÇÑ ±ÇÇÑ°ú + Á¦¾àÀ» µû¸¥´Ù. Áï, ISAPI .dll ÆÄÀÏÀÌ ÀÖ´Â µð·ºÅ丮¿¡ Options ExecCGI°¡ + ÇÊ¿äÇÏ´Ù.

+ +

mod_isapiÀÇ ISAPI Áö¿ø¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ + ³»¿ë°ú ¼³¸íÀº Ãß°¡ ¼³¸í°ú °³¹ßÀÚ Á¤º¸¸¦ Âü°íÇ϶ó.

+
top
+
+

Ãß°¡ ¼³¸í

+ +

¾ÆÆÄÄ¡ ISAPI ±¸ÇöÀº ºñµ¿±â ÀÔÃâ·Â¿¡ ´ëÇÑ "¸¶ÀÌÅ©·Î¼ÒÇÁÆ® + ƯÀ¯ÀÇ" È®Àå±â´ÉÀ» Á¦¿ÜÇÑ ISAPI 2.0 ±Ô¾àÀ» ¸ðµÎ ¸¸Á·ÇÑ´Ù. + ¾ÆÆÄÄ¡ÀÇ ÀÔÃâ·Â ±¸Á¶·Î´Â ISAPI°¡ »ç¿ëÇÒ ¼ö ÀÖ´Â ¹æ½ÄÀ¸·Î + ºñµ¿±â ÀÔÃâ·ÂÀ» ÇÒ ¼ö ¾ø´Ù. ISA°¡ ºñµ¿±â ÀÔÃâ·Â°ú °°ÀÌ Áö¿øÇÏÁö + ¾Ê´Â ±â´ÉÀ» »ç¿ëÇÏ·Á ÇÑ´Ù¸é, µð¹ö±ë¿¡ µµ¿òÀ» ÁÖ±âÀ§ÇØ ¿À·ù + ·Î±×¿¡ ±â·ÏÀ» ³²±ä´Ù. ·Î±×°¡ ¸Å¿ì Ä¿Áú ¼ö Àֱ⶧¹®¿¡ + ISAPILogNotSupported Off Áö½Ã¾î¸¦ »ç¿ëÇϸé + ·Î±×¿¡ ±â·ÏÇÏÁö ¾Ê´Â´Ù.

+ +

Microsoft IIS¿Í °°Àº ¼­¹ö´Â ISAPI extensionÀ» ¸Þ¸ð¸®·Î + Àоîµé¿©¼­ ¸Þ¸ð¸® »ç¿ë·®ÀÌ ¸Å¿ì ¸¹Áö ¾Ê°Å³ª Ưº°È÷ ¼³Á¤ÇÏÁö + ¾Ê´ÂÇÑ ±×´ë·Î ¸Þ¸ð¸®¿¡ µÐ´Ù. ¾ÆÆÄÄ¡´Â ÇöÀç ISAPICacheFile Áö½Ã¾î¸¦ »ç¿ëÇÏÁö + ¾Ê´Â´Ù¸é ¿äûÀ» ¹ÞÀ»¶§¸¶´Ù ISAPI extensionÀ» ¸Þ¸ð¸®¿¡ ÀоîµéÀÌ°í + ¹ö¸°´Ù. ºñÈ¿À²ÀûÀÌÁö¸¸, ¾ÆÆÄÄ¡ÀÇ ¸Þ¸ð¸® ±¸Á¶»ó ÀÌ°ÍÀÌ °¡Àå + È¿À²ÀûÀÎ ¹æ¹ýÀÌ´Ù. ¿©·¯ ISAPI ¸ðµâÀÌ ¾ÆÆÄÄ¡ ¼­¹ö¿Í ¾à°£ + ȣȯÀÌ ¾È¸Â±â¶§¹®¿¡ ¼­¹öÀÇ ¾ÈÁ¤¼ºÀ» À§ÇØ ¸ðµâÀ» ¸Þ¸ð¸®¿¡¼­ + ¹ö¸°´Ù.

+ +

¶Ç, ¾ÆÆÄÄ¡´Â ISAPI ExtensionÀ» Áö¿øÇÏÁö¸¸, ISAPI + Filter¸¦ Áö¿øÇÏÁö ¾ÊÀ½À» ±â¾ïÇ϶ó. ³ªÁß¿¡ ÇÊÅ͸¦ + Áö¿øÇÒ ¼ö ÀÖÁö¸¸, ÇöÀç´Â °èȹÀÌ ¾ø´Ù.

+
top
+
+

°³¹ßÀÚ Á¤º¸

+ +

¾ÆÆÄÄ¡ 2.0 mod_isapi ¸ðµâÀ» ÇÁ·Î±×·¡¹ÖÇÑ´Ù¸é, + ServerSupportFunction È£ÃâÀ» ´ÙÀ½ Áö½Ã¾î·Î + Á¦ÇÑÇØ¾ß ÇÑ´Ù.

+ +
+
HSE_REQ_SEND_URL_REDIRECT_RESP
+
»ç¿ëÀÚ¸¦ ´Ù¸¥ À§Ä¡·Î ¸®´ÙÀÌ·º¼ÇÇÑ´Ù.
+ ¿ÏÀüÇÑ URLÀ» »ç¿ëÇØ¾ß ÇÑ´Ù (¿¹¸¦ µé¾î, + http://server/location).
+ +
HSE_REQ_SEND_URL
+
»ç¿ëÀÚ¸¦ ´Ù¸¥ À§Ä¡·Î ¸®´ÙÀÌ·º¼ÇÇÑ´Ù.
+ ¿ÏÀüÇÑ URLÀÌ ¾Æ´Ï¸ç, ÇÁ·ÎÅäÄÝ°ú ¼­¹ö¸íÀ» ³Ñ±æ ¼ö ¾ø´Ù + (¿¹¸¦ µé¾î, /location°°Àº °Í¸¸ °¡´É).
+ ºê¶ó¿ìÀú°¡ ¾Æ´Ï¶ó ¼­¹ö°¡ ¸®´ÙÀÌ·º¼ÇÀ» ó¸®ÇÑ´Ù.
+

°æ°í

+

ÃÖ±Ù ¹®¼­¸¦ º¸¸é Microsoft°¡ µÎ HSE_REQ_SEND_URL + ±â´É°£ÀÇ Â÷À̸¦ ¾ø¾Ø °Íó·³ º¸ÀδÙ. ¾ÆÆÄÄ¡´Â °è¼Ó ÀÌ + µÑÀÇ ¾Æ±Ô¸ÕÆ® Á¶°Ç°ú ÇൿÀ» ´Ù¸£°Ô ó¸®ÇÒ °ÍÀÌ´Ù.

+
+ +
HSE_REQ_SEND_RESPONSE_HEADER
+
headers ¹®ÀÚ¿­ ¾Æ±Ô¸ÕÆ®¿¡ ºóÁÙÀÌ (Áٹٲ޹®ÀÚ°¡ µÎ¹ø + ¿¬¼Ó) ÀÖ´Ù¸é ¾ÆÆÄÄ¡´Â Çì´õ ´ÙÀ½ ³»¿ëÀ» ÀÀ´ä ³»¿ëÀ¸·Î »ç¿ëÇÑ´Ù. + headers ¾Æ±Ô¸ÕÆ®°¡ NULL·Î ³¡³ª±â¶§¹®¿¡, ÀÀ´ä ³»¿ë¿¡ NULLÀ» + »ç¿ëÇÒ ¼ö ¾ø´Ù.
+ +
HSE_REQ_DONE_WITH_SESSION
+
ISAPI°¡ 󸮸¦ ¸¶Ä¡¸é ¼¼¼ÇÀÌ ³¡³ª±â¶§¹®¿¡ ¾ÆÆÄÄ¡´Â + ¾Æ¹« Àϵµ ÇÏÁö ¾Ê´Â´Ù.
+ +
HSE_REQ_MAP_URL_TO_PATH
+
¾ÆÆÄÄ¡´Â °¡»ó À̸§À» ¹°¸®Àû(½ÇÁ¦) À̸§À¸·Î º¯È¯ÇÑ´Ù.
+ +
HSE_APPEND_LOG_PARAMETER
+
+ ¹®±¸¸¦ ¾Æ·¡ ·Î±×Áß ÇÑ°÷¿¡ ³²±ä´Ù. + + + +

ù¹ø°·Î ³ª¿Â %{isapi-parameter}n Ç׸ñÀº + ¾ðÁ¦³ª »ç¿ëÇÒ ¼ö ÀÖÀ¸¸ç ±ÇÀåÇÑ´Ù.

+
+ +
HSE_REQ_IS_KEEP_CONN
+
Çù»óµÈ Keep-Alive »óŸ¦ ¹ÝȯÇÑ´Ù.
+ +
HSE_REQ_SEND_RESPONSE_HEADER_EX
+
fKeepConn ¿É¼ÇÀ» ¹«½ÃÇÏ´Â °ÍÀ» Á¦¿ÜÇÏ°í´Â + ¹®¼­¿¡ ³ª¿Âµ¥·Î µ¿ÀÛÇÑ´Ù.
+ +
HSE_REQ_IS_CONNECTED
+
¿äûÀÌ Áß°£¿¡ ²÷¾îÁ³´Ù¸é false¸¦ ¹ÝȯÇÑ´Ù.
+
+ +

Áö¿øÇÏÁö ¾Ê´Â ServerSupportFunction È£ÃâÀ» + ÇÏ¸é ¾ÆÆÄÄ¡´Â FALSE¸¦ ¹ÝȯÇÏ°í + GetLastError °ªÀ» + ERROR_INVALID_PARAMETER·Î ¼³Á¤ÇÑ´Ù.

+ +

ReadClient´Â (ISAPIReadAheadBuffer·Î Á¤ÀÇÇÑ) + Ãʱâ¹öÆÛÅ©±â¸¦ ³Ñ¾î¼± ¿äû ³»¿ëÀ» °¡Á®¿Â´Ù. + ISAPIReadAheadBuffer ¼³Á¤ (ISAPI + Çڵ鷯¸¦ ºÎ¸£±âÀü ¹öÆÛÀÇ ¹ÙÀÌÆ®¼ö) º¸´Ù ªÀº ¿äûÀº extensionÀ» + ºÎ¸¦¶§ ÀüºÎ Àü´ÞµÈ´Ù. ¿äûÀÌ ±æ¸é, ISAPI extensionÀº + ReadClient·Î ³ª¸ÓÁö ¿äû ³»¿ëÀ» °¡Á®¿Í¾ß ÇÑ´Ù.

+ +

WriteClient¸¦ Áö¿øÇÏÁö¸¸, + HSE_IO_SYNC ¿É¼Ç¸¸ »ç¿ëÇϰųª (0 + °ª) ¾Æ¹« ¿É¼Çµµ »ç¿ëÇÏÁö ¾Ê¾Æ¾ß ÇÑ´Ù. ´Ù¸¥ + WriteClient ¿äûÀº FALSE¸¦ ¹ÝȯÇϸç + ½ÇÆÐÇÏ°í, GetLastError °ªÀº + ERROR_INVALID_PARAMETER°¡ µÈ´Ù.

+ +

GetServerVariableÀº Áö¿øÇÏÁö¸¸, (´Ù¸¥ ¼­¹ö¿¡¼­ + Á¤ÀÇÇÏ´Â) È®Àå ¼­¹öº¯¼ö´Â ¾ø´Ù. + GetServerVariable¿¡¼­ ¸ðµç ÀϹÝÀûÀÎ ¾ÆÆÄÄ¡ + CGI ȯ°æº¯¼ö¿Í ALL_HTTP, ALL_RAW + °ªÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

¾ÆÆÄÄ¡ 2.0 mod_isapi´Â ÀÌÈÄ ISAPI ±Ô¾à¿¡ + ³ª¿Â Ãß°¡ ±â´ÉÀ» Áö¿øÇÏ°í, ºñµ¿±â ÀÔÃâ·Â°ú + TransmitFile ±â´ÉÀ» Á¶±Ý Èä³»³½´Ù. ¶Ç, ISAPI + .dllÀ» ¹Ì¸® Àоîµé¿©¼­ ¼º´ÉÀ» ³ôÀÌ´Â ¾ÆÆÄÄ¡ 1.3 + mod_isapi¿¡´Â ¾ø´Â ±â´ÉÀ» Áö¿øÇÑ´Ù.

+
+
top
+

ISAPIAppendLogToErrors Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ISAPI exntensionÀÇ HSE_APPEND_LOG_PARAMETER +¿äûÀ» ¿À·ù ·Î±×¿¡ ±â·ÏÇÑ´Ù
¹®¹ý:ISAPIAppendLogToErrors on|off
±âº»°ª:ISAPIAppendLogToErrors off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_isapi
+

ISAPI exntensionÀÇ HSE_APPEND_LOG_PARAMETER + ¿äûÀ» ¿À·ù ·Î±×¿¡ ±â·ÏÇÑ´Ù.

+ +
+
top
+

ISAPIAppendLogToQuery Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ISAPI exntensionÀÇ HSE_APPEND_LOG_PARAMETER +¿äûÀ» ÁúÀǹ®ÀÚ¿­¿¡ ±â·ÏÇÑ´Ù
¹®¹ý:ISAPIAppendLogToQuery on|off
±âº»°ª:ISAPIAppendLogToQuery on
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_isapi
+

ISAPI exntensionÀÇ HSE_APPEND_LOG_PARAMETER + ¿äûÀ» ÁúÀǹ®ÀÚ¿­¿¡ ±â·ÏÇÑ´Ù (CustomLog %q + Ç׸ñ¿¡ µ¡ºÙÀδÙ).

+ +
+
top
+

ISAPICacheFile Áö½Ã¾î

+ + + + + + +
¼³¸í:¼­¹ö°¡ ½ÃÀÛÇÒ¶§ ¸Þ¸ð¸®·Î ÀоîµéÀÏ ISAPI .dll ÆÄÀϵé
¹®¹ý:ISAPICacheFile file-path [file-path] +...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_isapi
+

¾ÆÆÄÄ¡ ¼­¹ö°¡ ½ÃÀÛÇÒ¶§ ¸Þ¸ð¸®·Î Àоîµé¿©¼­ ¼­¹ö¸¦ Á¾·áÇÒ¶§±îÁö + ¸Þ¸ð¸®¿¡ ³²¾ÆÀÖÀ» ÆÄÀϸíÀ» °ø¹éÀ¸·Î ±¸ºÐÇÏ¿© ÁöÁ¤ÇÑ´Ù. ÀÌ + Áö½Ã¾î´Â ISAPI .dll ÆÄÀϺ°·Î ¿©·¯¹ø »ç¿ëÇÒ ¼ö ÀÖ´Ù. ÆÄÀÏÀÇ + Àüü °æ·Î¸¦ Àû´Â´Ù. Àý´ë °æ·Î°¡ ¾Æ´Ï¸é ServerRoot¿¡ »ó´ë °æ·Î·Î ¹Þ¾ÆµéÀδÙ.

+ +
+
top
+

ISAPIFakeAsync Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ºñµ¿±â ISAPI ÄݹéÀ» Áö¿øÇϴ ôÇÑ´Ù
¹®¹ý:ISAPIFakeAsync on|off
±âº»°ª:ISAPIFakeAsync off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_isapi
+

onÀ¸·Î ¼³Á¤ÇÏ¸é ºñµ¿±â ISAPI Äݹé Áö¿øÀ» Èä³»³½´Ù.

+ +
+
top
+

ISAPILogNotSupported Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ISAPI extensionÀÌ Áö¿øÇÏÁö ¾Ê´Â ±â´ÉÀ» ¿äûÇϸé +·Î±×¿¡ ±â·ÏÇÑ´Ù
¹®¹ý:ISAPILogNotSupported on|off
±âº»°ª:ISAPILogNotSupported off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_isapi
+

ISAPI extensionÀÌ Áö¿øÇÏÁö ¾Ê´Â ±â´ÉÀ» ¿äûÇÏ¸é ¼­¹ö + ¿À·ù ·Î±×¿¡ ±â·ÏÇÑ´Ù. ³ªÁß¿¡ °ü¸®ÀÚ°¡ ¹®Á¦¸¦ ÃßÀûÇϴµ¥ + µµ¿òÀÌ µÈ´Ù. ¿øÇÏ´Â ¸ðµç ISAPI ¸ðµâÀÌ Á¤»óÀûÀ¸·Î µ¿ÀÛÇϸé + ´Ù½Ã off·Î µÇµ¹·Á¾ß ÇÑ´Ù.

+ +
+
top
+

ISAPIReadAheadBuffer Áö½Ã¾î

+ + + + + + + + +
¼³¸í:ISAPI extensionÀÇ ¹Ì¸®Àбâ¹öÆÛ(read ahead buffer) +Å©±â
¹®¹ý:ISAPIReadAheadBuffer size
±âº»°ª:ISAPIReadAheadBuffer 49152
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_isapi
+

ISAPI extensionÀ» óÀ½ È£ÃâÇÒ¶§ ¹Ì¸®Àбâ¹öÆÛÀÇ ÃÖ´ë Å©±â¸¦ + ÁöÁ¤ÇÑ´Ù. (ÀÌ Å©±âº¸´Ù Å«) ³ª¸ÓÁö ÀÚ·á´Â ReadClient + ÄݹéÀ» »ç¿ëÇÏ¿© Àоî¾ß ÇÑ´Ù. ¾î¶² ISAPI extensionÀº + ReadClient ±â´ÉÀ» Áö¿øÇÏÁö ¾Ê´Â´Ù. ÀÌ °æ¿ì + ISAPI extension Á¦ÀÛÀÚ¿¡°Ô ¹®ÀÇÇ϶ó.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_ldap.html b/docs/manual/mod/mod_ldap.html new file mode 100644 index 00000000..059ee1a9 --- /dev/null +++ b/docs/manual/mod/mod_ldap.html @@ -0,0 +1,3 @@ +URI: mod_ldap.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_ldap.html.en b/docs/manual/mod/mod_ldap.html.en new file mode 100644 index 00000000..c7f23ff2 --- /dev/null +++ b/docs/manual/mod/mod_ldap.html.en @@ -0,0 +1,627 @@ + + + +mod_ldap - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_ldap

+
+

Available Languages:  en 

+
+ + + + +
Description:LDAP connection pooling and result caching services for use +by other LDAP modules
Status:Extension
Module Identifier:ldap_module
Source File:util_ldap.c
Compatibility:Available in version 2.0.41 and later
+

Summary

+ +

This module was created to improve the performance of + websites relying on backend connections to LDAP servers. In + addition to the functions provided by the standard LDAP + libraries, this module adds an LDAP connection pool and an LDAP + shared memory cache.

+ +

To enable this module, LDAP support must be compiled into + apr-util. This is achieved by adding the --with-ldap + flag to the configure script when building + Apache.

+ +

SSL/TLS support is dependant on which LDAP toolkit has been + linked to APR. As of this writing, APR-util supports: + OpenLDAP SDK (2.x or later), + Novell LDAP + SDK, + Mozilla LDAP SDK, native Solaris LDAP SDK (Mozilla based), + native Microsoft LDAP SDK, or the + iPlanet + (Netscape) SDK. See the APR + website for details.

+ +
+ +
top
+
+

Example Configuration

+

The following is an example configuration that uses + mod_ldap to increase the performance of HTTP Basic + authentication provided by mod_authnz_ldap.

+ +

+ # Enable the LDAP connection pool and shared
+ # memory cache. Enable the LDAP cache status
+ # handler. Requires that mod_ldap and mod_authnz_ldap
+ # be loaded. Change the "yourdomain.example.com" to
+ # match your domain.
+
+ LDAPSharedCacheSize 200000
+ LDAPCacheEntries 1024
+ LDAPCacheTTL 600
+ LDAPOpCacheEntries 1024
+ LDAPOpCacheTTL 600
+
+ <Location /ldap-status>
+ + SetHandler ldap-status
+ Order deny,allow
+ Deny from all
+ Allow from yourdomain.example.com
+ AuthLDAPURL ldap://127.0.0.1/dc=example,dc=com?uid?one
+ AuthzLDAPAuthoritative off
+ require valid-user
+ + </Location> +

+
top
+
+

LDAP Connection Pool

+ +

LDAP connections are pooled from request to request. This + allows the LDAP server to remain connected and bound ready for + the next request, without the need to unbind/connect/rebind. + The performance advantages are similar to the effect of HTTP + keepalives.

+ +

On a busy server it is possible that many requests will try + and access the same LDAP server connection simultaneously. + Where an LDAP connection is in use, Apache will create a new + connection alongside the original one. This ensures that the + connection pool does not become a bottleneck.

+ +

There is no need to manually enable connection pooling in + the Apache configuration. Any module using this module for + access to LDAP services will share the connection pool.

+
top
+
+

LDAP Cache

+ +

For improved performance, mod_ldap uses an aggressive + caching strategy to minimize the number of times that the LDAP + server must be contacted. Caching can easily double or triple + the throughput of Apache when it is serving pages protected + with mod_authnz_ldap. In addition, the load on the LDAP server + will be significantly decreased.

+ +

mod_ldap supports two types of LDAP caching during + the search/bind phase with a search/bind cache and + during the compare phase with two operation + caches. Each LDAP URL that is used by the server has + its own set of these three caches.

+ +

The Search/Bind Cache

+

The process of doing a search and then a bind is the + most time-consuming aspect of LDAP operation, especially if + the directory is large. The search/bind cache is used to + cache all searches that resulted in successful binds. + Negative results (i.e., unsuccessful searches, or searches + that did not result in a successful bind) are not cached. + The rationale behind this decision is that connections with + invalid credentials are only a tiny percentage of the total + number of connections, so by not caching invalid + credentials, the size of the cache is reduced.

+ +

mod_ldap stores the username, the DN + retrieved, the password used to bind, and the time of the bind + in the cache. Whenever a new connection is initiated with the + same username, mod_ldap compares the password + of the new connection with the password in the cache. If the + passwords match, and if the cached entry is not too old, + mod_ldap bypasses the search/bind phase.

+ +

The search and bind cache is controlled with the LDAPCacheEntries and LDAPCacheTTL directives.

+ + +

Operation Caches

+

During attribute and distinguished name comparison + functions, mod_ldap uses two operation caches + to cache the compare operations. The first compare cache is + used to cache the results of compares done to test for LDAP + group membership. The second compare cache is used to cache + the results of comparisons done between distinguished + names.

+ +

The behavior of both of these caches is controlled with + the LDAPOpCacheEntries + and LDAPOpCacheTTL + directives.

+ + +

Monitoring the Cache

+

mod_ldap has a content handler that allows + administrators to monitor the cache performance. The name of + the content handler is ldap-status, so the + following directives could be used to access the + mod_ldap cache information:

+ +

+ <Location /server/cache-info>
+ + SetHandler ldap-status
+ + </Location> +

+ +

By fetching the URL http://servername/cache-info, + the administrator can get a status report of every cache that is used + by mod_ldap cache. Note that if Apache does not + support shared memory, then each httpd instance has its + own cache, so reloading the URL will result in different + information each time, depending on which httpd + instance processes the request.

+ +
top
+
+

Using SSL/TLS

+ +

The ability to create an SSL and TLS connections to an LDAP server + is defined by the directives + LDAPTrustedGlobalCert, + LDAPTrustedClientCert and + LDAPTrustedMode. These directives specify the CA and + optional client certificates to be used, as well as the type of + encryption to be used on the connection (none, SSL or TLS/STARTTLS).

+ +

+ # Establish an SSL LDAP connection on port 636. Requires that
+ # mod_ldap and mod_authnz_ldap be loaded. Change the
+ # "yourdomain.example.com" to match your domain.
+
+ LDAPTrustedGlobalCert CA_DER /certs/certfile.der
+
+ <Location /ldap-status>
+ + SetHandler ldap-status
+ Order deny,allow
+ Deny from all
+ Allow from yourdomain.example.com
+ AuthLDAPURL ldaps://127.0.0.1/dc=example,dc=com?uid?one
+ AuthzLDAPAuthoritative off
+ require valid-user
+ + </Location> +

+ +

+ # Establish a TLS LDAP connection on port 389. Requires that
+ # mod_ldap and mod_authnz_ldap be loaded. Change the
+ # "yourdomain.example.com" to match your domain.
+
+ LDAPTrustedGlobalCert CA_DER /certs/certfile.der
+
+ <Location /ldap-status>
+ + SetHandler ldap-status
+ Order deny,allow
+ Deny from all
+ Allow from yourdomain.example.com
+ AuthLDAPURL ldap://127.0.0.1/dc=example,dc=com?uid?one TLS
+ AuthzLDAPAuthoritative off
+ require valid-user
+ + </Location> +

+ +
top
+
+

SSL/TLS Certificates

+ +

The different LDAP SDKs have widely different methods of setting + and handling both CA and client side certificates.

+ +

If you intend to use SSL or TLS, read this section CAREFULLY so as to + understand the differences between configurations on the different LDAP + toolkits supported.

+ +

Netscape/Mozilla/iPlanet SDK

+

CA certificates are specified within a file called cert7.db. + The SDK will not talk to any LDAP server whose certificate was + not signed by a CA specified in this file. If + client certificates are required, an optional key3.db file may + be specified with an optional password. The secmod file can be + specified if required. These files are in the same format as + used by the Netscape Communicator or Mozilla web browsers. The easiest + way to obtain these files is to grab them from your browser + installation.

+ +

Client certificates are specified per connection using the + LDAPTrustedClientCert directive by referring + to the certificate "nickname". An optional password may be + specified to unlock the certificate's private key.

+ +

The SDK supports SSL only. An attempt to use STARTTLS will cause + an error when an attempt is made to contact the LDAP server at + runtime.

+ +

+ # Specify a Netscape CA certificate file
+ LDAPTrustedGlobalCert CA_CERT7_DB /certs/cert7.db
+ # Specify an optional key3.db file for client certificate support
+ LDAPTrustedGlobalCert CERT_KEY3_DB /certs/key3.db
+ # Specify the secmod file if required
+ LDAPTrustedGlobalCert CA_SECMOD /certs/secmod
+ <Location /ldap-status>
+ + SetHandler ldap-status
+ Order deny,allow
+ Deny from all
+ Allow from yourdomain.example.com
+ LDAPTrustedClientCert CERT_NICKNAME <nickname> [password]
+ AuthLDAPURL ldaps://127.0.0.1/dc=example,dc=com?uid?one
+ AuthzLDAPAuthoritative off
+ require valid-user
+ + </Location> +

+ + + +

Novell SDK

+ +

One or more CA certificates must be specified for the Novell + SDK to work correctly. These certificates can be specified as + binary DER or Base64 (PEM) encoded files.

+ +

Note: Client certificates are specified globally rather than per + connection, and so must be specified with the LDAPTrustedGlobalCert + directive as below. Trying to set client certificates via the + LDAPTrustedClientCert directive will cause an error to be logged + when an attempt is made to connect to the LDAP server..

+ +

The SDK supports both SSL and STARTTLS, set using the + LDAPTrustedMode parameter. If an ldaps:// URL is specified, + SSL mode is forced, override this directive.

+ +

+ # Specify two CA certificate files
+ LDAPTrustedGlobalCert CA_DER /certs/cacert1.der
+ LDAPTrustedGlobalCert CA_BASE64 /certs/cacert2.pem
+ # Specify a client certificate file and key
+ LDAPTrustedGlobalCert CERT_BASE64 /certs/cert1.pem
+ LDAPTrustedGlobalCert KEY_BASE64 /certs/key1.pem [password]
+ # Do not use this directive, as it will throw an error
+ #LDAPTrustedClientCert CERT_BASE64 /certs/cert1.pem
+

+ + + +

OpenLDAP SDK

+ +

One or more CA certificates must be specified for the OpenLDAP + SDK to work correctly. These certificates can be specified as + binary DER or Base64 (PEM) encoded files.

+ +

Client certificates are specified per connection using the + LDAPTrustedClientCert directive.

+ +

The documentation for the SDK claims to support both SSL and + STARTTLS, however STARTTLS does not seem to work on all versions + of the SDK. The SSL/TLS mode can be set using the + LDAPTrustedMode parameter. If an ldaps:// URL is specified, + SSL mode is forced. The OpenLDAP documentation notes that SSL + (ldaps://) support has been deprecated to be replaced with TLS, + although the SSL functionality still works.

+ +

+ # Specify two CA certificate files
+ LDAPTrustedGlobalCert CA_DER /certs/cacert1.der
+ LDAPTrustedGlobalCert CA_BASE64 /certs/cacert2.pem
+ <Location /ldap-status>
+ + SetHandler ldap-status
+ Order deny,allow
+ Deny from all
+ Allow from yourdomain.example.com
+ LDAPTrustedClientCert CERT_BASE64 /certs/cert1.pem
+ LDAPTrustedClientCert KEY_BASE64 /certs/key1.pem
+ AuthLDAPURL ldaps://127.0.0.1/dc=example,dc=com?uid?one
+ AuthzLDAPAuthoritative off
+ require valid-user
+ + </Location> +

+ + + +

Solaris SDK

+ +

SSL/TLS for the native Solaris LDAP libraries is not yet + supported. If required, install and use the OpenLDAP libraries + instead.

+ + + +

Microsoft SDK

+ +

SSL/TLS certificate configuration for the native Microsoft + LDAP libraries is done inside the system registry, and no + configuration directives are required.

+ +

Both SSL and TLS are supported by using the ldaps:// URL + format, or by using the LDAPTrustedMode directive accordingly.

+ +

Note: The status of support for client certificates is not yet known + for this toolkit.

+ + + +
+
top
+

LDAPCacheEntries Directive

+ + + + + + + +
Description:Maximum number of entries in the primary LDAP cache
Syntax:LDAPCacheEntries number
Default:LDAPCacheEntries 1024
Context:server config
Status:Extension
Module:mod_ldap
+

Specifies the maximum size of the primary LDAP cache. This + cache contains successful search/binds. Set it to 0 to turn off + search/bind caching. The default size is 1024 cached + searches.

+ +
+
top
+

LDAPCacheTTL Directive

+ + + + + + + +
Description:Time that cached items remain valid
Syntax:LDAPCacheTTL seconds
Default:LDAPCacheTTL 600
Context:server config
Status:Extension
Module:mod_ldap
+

Specifies the time (in seconds) that an item in the + search/bind cache remains valid. The default is 600 seconds (10 + minutes).

+ +
+
top
+

LDAPConnectionTimeout Directive

+ + + + + + +
Description:Specifies the socket connection timeout in seconds
Syntax:LDAPConnectionTimeout seconds
Context:server config
Status:Extension
Module:mod_ldap
+

Specifies the timeout value (in seconds) in which the module will + attempt to connect to the LDAP server. If a connection is not + successful with the timeout period, either an error will be + returned or the module will attempt to connect to a secondary LDAP + server if one is specified. The default is 10 seconds.

+ +
+
top
+

LDAPOpCacheEntries Directive

+ + + + + + + +
Description:Number of entries used to cache LDAP compare +operations
Syntax:LDAPOpCacheEntries number
Default:LDAPOpCacheEntries 1024
Context:server config
Status:Extension
Module:mod_ldap
+

This specifies the number of entries mod_ldap + will use to cache LDAP compare operations. The default is 1024 + entries. Setting it to 0 disables operation caching.

+ +
+
top
+

LDAPOpCacheTTL Directive

+ + + + + + + +
Description:Time that entries in the operation cache remain +valid
Syntax:LDAPOpCacheTTL seconds
Default:LDAPOpCacheTTL 600
Context:server config
Status:Extension
Module:mod_ldap
+

Specifies the time (in seconds) that entries in the + operation cache remain valid. The default is 600 seconds.

+ +
+
top
+

LDAPSharedCacheFile Directive

+ + + + + + +
Description:Sets the shared memory cache file
Syntax:LDAPSharedCacheFile directory-path/filename
Context:server config
Status:Extension
Module:mod_ldap
+

Specifies the directory path and file name of the shared memory + cache file. If not set, anonymous shared memory will be used if the + platform supports it.

+ +
+
top
+

LDAPSharedCacheSize Directive

+ + + + + + + +
Description:Size in bytes of the shared-memory cache
Syntax:LDAPSharedCacheSize bytes
Default:LDAPSharedCacheSize 102400
Context:server config
Status:Extension
Module:mod_ldap
+

Specifies the number of bytes to allocate for the shared + memory cache. The default is 100kb. If set to 0, shared memory + caching will not be used.

+ +
+
top
+

LDAPTrustedClientCert Directive

+ + + + + + +
Description:Sets the file containing or nickname referring to a per +connection client certificate. Not all LDAP toolkits support per +connection client certificates.
Syntax:LDAPTrustedClientCert type directory-path/filename/nickname [password]
Context:server config, virtual host, directory, .htaccess
Status:Extension
Module:mod_ldap
+

It specifies the directory path, file name or nickname of a + per connection client certificate used when establishing an SSL + or TLS connection to an LDAP server. Different locations or + directories may have their own independant client certificate + settings. Some LDAP toolkits (notably Novell) + do not support per connection client certificates, and will throw an + error on LDAP server connection if you try to use this directive + (Use the LDAPTrustedGlobalCert directive instead for Novell client + certificates - See the SSL/TLS certificate guide above for details). + The type specifies the kind of certificate parameter being + set, depending on the LDAP toolkit being used. Supported types are:

+
    +
  • CERT_DER - binary DER encoded client certificate
    • +
  • CERT_BASE64 - PEM encoded client certificate
    • +
  • CERT_NICKNAME - Client certificate "nickname" (Netscape SDK)
    • +
  • KEY_DER - binary DER encoded private key
    • +
  • KEY_BASE64 - PEM encoded private key
    • +
+ +
+
top
+

LDAPTrustedGlobalCert Directive

+ + + + + + +
Description:Sets the file or database containing global trusted +Certificate Authority or global client certificates
Syntax:LDAPTrustedGlobalCert type directory-path/filename [password]
Context:server config
Status:Extension
Module:mod_ldap
+

It specifies the directory path and file name of the trusted CA + certificates and/or system wide client certificates mod_ldap + should use when establishing an SSL or TLS connection to an LDAP + server. Note that all certificate information specified using this directive + is applied globally to the entire server installation. Some LDAP toolkits + (notably Novell) require all client certificates to be set globally using + this directive. Most other toolkits require clients certificates to be set + per Directory or per Location using LDAPTrustedClientCert. If you get this + wrong, an error may be logged when an attempt is made to contact the LDAP + server, or the connection may silently fail (See the SSL/TLS certificate + guide above for details). + The type specifies the kind of certificate parameter being + set, depending on the LDAP toolkit being used. Supported types are:

+
    +
  • CA_DER - binary DER encoded CA certificate
    • +
  • CA_BASE64 - PEM encoded CA certificate
    • +
  • CA_CERT7_DB - Netscape cert7.db CA certificate database file
    • +
  • CA_SECMOD - Netscape secmod database file
    • +
  • CERT_DER - binary DER encoded client certificate
    • +
  • CERT_BASE64 - PEM encoded client certificate
    • +
  • CERT_KEY3_DB - Netscape key3.db client certificate database file
    • +
  • CERT_NICKNAME - Client certificate "nickname" (Netscape SDK)
    • +
  • CERT_PFX - PKCS#12 encoded client certificate (Novell SDK)
    • +
  • KEY_DER - binary DER encoded private key
    • +
  • KEY_BASE64 - PEM encoded private key
    • +
  • KEY_PFX - PKCS#12 encoded private key (Novell SDK)
    • +
+ +
+
top
+

LDAPTrustedMode Directive

+ + + + + + +
Description:Specifies the SSL/TLS mode to be used when connecting to an LDAP server.
Syntax:LDAPTrustedMode type
Context:server config, virtual host
Status:Extension
Module:mod_ldap
+

The following modes are supported:

+
    +
  • NONE - no encryption
    • +
  • SSL - ldaps:// encryption on default port 636
    • +
  • TLS - STARTTLS encryption on default port 389
    • +
+ +

Not all LDAP toolkits support all the above modes. An error message + will be logged at runtime if a mode is not supported, and the + connection to the LDAP server will fail. +

+ +

If an ldaps:// URL is specified, the mode becomes SSL and the setting + of LDAPTrustedMode is ignored.

+ +
+
top
+

LDAPVerifyServerCert Directive

+ + + + + + + +
Description:Force server certificate verification
Syntax:LDAPVerifyServerCert On|Off
Default:LDAPVerifyServerCert On
Context:server config
Status:Extension
Module:mod_ldap
+

Specifies whether to force the verification of a + server certificate when establishing an SSL connection to the + LDAP server.

+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_log_config.html b/docs/manual/mod/mod_log_config.html new file mode 100644 index 00000000..34224912 --- /dev/null +++ b/docs/manual/mod/mod_log_config.html @@ -0,0 +1,11 @@ +URI: mod_log_config.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_log_config.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_log_config.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_log_config.html.en b/docs/manual/mod/mod_log_config.html.en new file mode 100644 index 00000000..51b80a88 --- /dev/null +++ b/docs/manual/mod/mod_log_config.html.en @@ -0,0 +1,472 @@ + + + +mod_log_config - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_log_config

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Logging of the requests made to the server
Status:Base
Module Identifier:log_config_module
Source File:mod_log_config.c
+

Summary

+ +

This module provides for flexible logging of client + requests. Logs are written in a customizable format, and may be + written directly to a file, or to an external program. + Conditional logging is provided so that individual requests may + be included or excluded from the logs based on characteristics + of the request.

+ +

Three directives are provided by this module: + TransferLog to create + a log file, LogFormat + to set a custom format, and CustomLog to define a log file and format in one + step. The TransferLog and CustomLog directives can be used multiple times in each + server to cause each request to be logged to multiple files.

+
+ +
top
+
+

Custom Log Formats

+ +

The format argument to the LogFormat and CustomLog directives is a string. This string is + used to log each request to the log file. It can contain literal + characters copied into the log files and the C-style control + characters "\n" and "\t" to represent new-lines and tabs. + Literal quotes and back-slashes should be escaped with + back-slashes.

+ +

The characteristics of the request itself are logged by + placing "%" directives in the format string, which are + replaced in the log file by the values as follows:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Format StringDescription
%%The percent sign
%aRemote IP-address
%ALocal IP-address
%BSize of response in bytes, excluding HTTP headers.
%bSize of response in bytes, excluding HTTP headers. In CLF format, i.e. + a '-' rather than a 0 when no bytes are sent.
%{Foobar}CThe contents of cookie Foobar in the request sent + to the server.
%DThe time taken to serve the request, in microseconds.
%{FOOBAR}eThe contents of the environment variable + FOOBAR
%fFilename
%hRemote host
%HThe request protocol
%{Foobar}iThe contents of Foobar: header line(s) + in the request sent to the server.
%lRemote logname (from identd, if supplied). This will return a + dash unless mod_ident is present and IdentityCheck is set + On.
%mThe request method
%{Foobar}nThe contents of note Foobar from another + module.
%{Foobar}oThe contents of Foobar: header line(s) + in the reply.
%pThe canonical port of the server serving the request
%PThe process ID of the child that serviced the request.
%{format}PThe process ID or thread id of the child that serviced the + request. Valid formats are pid, tid, + and hextid. hextid requires APR 1.2.0 or + higher. +
%qThe query string (prepended with a ? if a query + string exists, otherwise an empty string)
%rFirst line of request
%sStatus. For requests that got internally redirected, this is + the status of the *original* request --- %>s + for the last.
%tTime the request was received (standard english + format)
%{format}tThe time, in the form given by format, which should be in + strftime(3) format. (potentially localized)
%TThe time taken to serve the request, in seconds.
%uRemote user (from auth; may be bogus if return status + (%s) is 401)
%UThe URL path requested, not including any query string.
%vThe canonical ServerName + of the server serving the request.
%VThe server name according to the UseCanonicalName setting.
%XConnection status when response is completed: + + + + + + + + + +
X =connection aborted before the response completed.
+ =connection may be kept alive after the response is + sent.
- = connection will be closed after the response is + sent.
+ +

(This directive was %c in late versions of Apache + 1.3, but this conflicted with the historical ssl + %{var}c syntax.)

%IBytes received, including request and headers, cannot be zero. + You need to enable mod_logio to use this.
%OBytes sent, including headers, cannot be zero. You need to + enable mod_logio to use this.
+ +

Modifiers

+ +

Particular items can be restricted to print only for + responses with specific HTTP status codes by placing a + comma-separated list of status codes immediately following the + "%". For example, "%400,501{User-agent}i" logs + User-agent on 400 errors and 501 errors only. For + other status codes, the literal string "-" will be + logged. The status code list may be preceded by a + "!" to indicate negation: + "%!200,304,302{Referer}i" logs Referer + on all requests that do not return one of the three + specified codes.

+ +

The modifiers "<" and ">" can be used for requests that + have been internally redirected to choose whether the original + or final (respectively) request should be consulted. By + default, the % directives %s, %U, %T, + %D, and %r look at the original request + while all others look at the final request. So for example, + %>s can be used to record the final status of + the request and %<u can be used to record the + original authenticated user on a request that is internally + redirected to an unauthenticated resource.

+ + + +

Some Notes

+ +

For security reasons, starting with version 2.0.46, + non-printable and other special characters in %r, + %i and %o are escaped using + \xhh sequences, where hh + stands for the hexadecimal representation of the raw + byte. Exceptions from this rule are " and + \, which are escaped by prepending a backslash, and + all whitespace characters, which are written in their C-style + notation (\n, \t, etc). In versions + prior to 2.0.46, no escaping was performed on these strings so + you had to be quite careful when dealing with raw log files.

+ +

In httpd 2.0, unlike 1.3, the %b and + %B format strings do not represent the number of + bytes sent to the client, but simply the size in bytes of the + HTTP response (which will differ, for instance, if the + connection is aborted, or if SSL is used). The %O + format provided by mod_logio will log the + actual number of bytes sent over the network.

+ + + +

Examples

+ +

Some commonly used log format strings are:

+ +
+
Common Log Format (CLF)
+
"%h %l %u %t \"%r\" %>s %b"
+ +
Common Log Format with Virtual Host
+
"%v %h %l %u %t \"%r\" %>s %b"
+ +
NCSA extended/combined log format
+
"%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\""
+ +
Referer log format
+
"%{Referer}i -> %U"
+ +
Agent (Browser) log format
+
"%{User-agent}i"
+
+ +
top
+
+

Security Considerations

+

See the security tips + document for details on why your security could be compromised + if the directory where logfiles are stored is writable by + anyone other than the user that starts the server.

+
+
top
+

BufferedLogs Directive

+ + + + + + + + +
Description:Buffer log entries in memory before writing to disk
Syntax:BufferedLogs On|Off
Default:BufferedLogs Off
Context:server config
Status:Base
Module:mod_log_config
Compatibility:Available in versions 2.0.41 and later.
+

The BufferedLogs directive causes + mod_log_config to store several log entries in + memory and write them together to disk, rather than writing them + after each request. On some systems, this may result in more + efficient disk access and hence higher performance. It may be + set only once for the entire server; it cannot be configured + per virtual-host.

+ +
This directive is experimental and should be used with + caution.
+ +
+
top
+

CookieLog Directive

+ + + + + + + +
Description:Sets filename for the logging of cookies
Syntax:CookieLog filename
Context:server config, virtual host
Status:Base
Module:mod_log_config
Compatibility:This directive is deprecated.
+

The CookieLog directive sets the + filename for logging of cookies. The filename is relative to the + ServerRoot. This directive is + included only for compatibility with mod_cookies, + and is deprecated.

+ +
+
top
+

CustomLog Directive

+ + + + + + +
Description:Sets filename and format of log file
Syntax:CustomLog file|pipe +format|nickname +[env=[!]environment-variable]
Context:server config, virtual host
Status:Base
Module:mod_log_config
+

The CustomLog directive is used to + log requests to the server. A log format is specified, and the + logging can optionally be made conditional on request + characteristics using environment variables.

+ +

The first argument, which specifies the location to which + the logs will be written, can take one of the following two + types of values:

+ +
+
file
+
A filename, relative to the ServerRoot.
+ +
pipe
+
The pipe character "|", followed by the path + to a program to receive the log information on its standard + input. + +

Security:

+

If a program is used, then it will be run as the user who + started httpd. This will be root if the server was + started by root; be sure that the program is secure.

+
+

Note

+

When entering a file path on non-Unix platforms, care should be taken + to make sure that only forward slashed are used even though the platform + may allow the use of back slashes. In general it is a good idea to always + use forward slashes throughout the configuration files.

+
+
+ +

The second argument specifies what will be written to the + log file. It can specify either a nickname defined by + a previous LogFormat + directive, or it can be an explicit format string as + described in the log formats section.

+ +

For example, the following two sets of directives have + exactly the same effect:

+ +

+ # CustomLog with format nickname
+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common
+
+ # CustomLog with explicit format string
+ CustomLog logs/access_log "%h %l %u %t \"%r\" %>s %b" +

+ +

The third argument is optional and controls whether or + not to log a particular request based on the + presence or absence of a particular variable in the server + environment. If the specified environment + variable is set for the request (or is not set, in the case + of a 'env=!name' clause), then the + request will be logged.

+ +

Environment variables can be set on a per-request + basis using the mod_setenvif + and/or mod_rewrite modules. For + example, if you want to record requests for all GIF + images on your server in a separate logfile but not in your main + log, you can use:

+ +

+ SetEnvIf Request_URI \.gif$ gif-image
+ CustomLog gif-requests.log common env=gif-image
+ CustomLog nongif-requests.log common env=!gif-image +

+ +

Or, to reproduce the behavior of the old RefererIgnore + directive, you might use the following:

+ +

+ SetEnvIf Referer example\.com localreferer
+ CustomLog referer.log referer env=!localreferer +

+ +
+
top
+

LogFormat Directive

+ + + + + + + +
Description:Describes a format for use in a log file
Syntax:LogFormat format|nickname +[nickname]
Default:LogFormat "%h %l %u %t \"%r\" %>s %b"
Context:server config, virtual host
Status:Base
Module:mod_log_config
+

This directive specifies the format of the access log + file.

+ +

The LogFormat directive can take one of two + forms. In the first form, where only one argument is specified, + this directive sets the log format which will be used by logs + specified in subsequent TransferLog + directives. The single argument can specify an explicit + format as discussed in the custom log + formats section above. Alternatively, it can use a + nickname to refer to a log format defined in a + previous LogFormat directive as described + below.

+ +

The second form of the LogFormat + directive associates an explicit format with a + nickname. This nickname can then be used in + subsequent LogFormat or + CustomLog directives + rather than repeating the entire format string. A + LogFormat directive that defines a nickname + does nothing else -- that is, it only + defines the nickname, it doesn't actually apply the format and make + it the default. Therefore, it will not affect subsequent + TransferLog directives. + In addition, LogFormat cannot use one nickname + to define another nickname. Note that the nickname should not contain + percent signs (%).

+ +

Example

+ LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common +

+ +
+
top
+

TransferLog Directive

+ + + + + + +
Description:Specify location of a log file
Syntax:TransferLog file|pipe
Context:server config, virtual host
Status:Base
Module:mod_log_config
+

This directive has exactly the same arguments and effect as + the CustomLog + directive, with the exception that it does not allow the log format + to be specified explicitly or for conditional logging of requests. + Instead, the log format is determined by the most recently specified + LogFormat directive + which does not define a nickname. Common Log Format is used if no + other format has been specified.

+ +

Example

+ LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\""
+ TransferLog logs/access_log +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_log_config.html.ja.euc-jp b/docs/manual/mod/mod_log_config.html.ja.euc-jp new file mode 100644 index 00000000..ef5b8dcb --- /dev/null +++ b/docs/manual/mod/mod_log_config.html.ja.euc-jp @@ -0,0 +1,471 @@ + + + +mod_log_config - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_log_config

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:¥µ¡¼¥Ð¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Î¥í¥®¥ó¥°
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:log_config_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_log_config.c
+

³µÍ×

+ +

+ ¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ò½ÀÆð¤Ë¥í¥°¼ý½¸¤¹¤ëµ¡Ç½¤ò + Ä󶡤·¤Þ¤¹¡£¥í¥°¤Ï¥«¥¹¥¿¥Þ¥¤¥º²Äǽ¤Ê½ñ¼°¤Ç½ñ¤«¤ì¡¢¥Õ¥¡¥¤¥ë¤ËľÀÜ + ½ñ¤¤¤¿¤ê¡¢³°Éô¥×¥í¥°¥é¥à¤ËÅϤ·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¸Ä¡¹¤Î¥ê¥¯¥¨¥¹¥È¤ò + ÆÃħ¤Ë±þ¤¸¤Æ¥í¥°¤Ë½ñ¤¤¤¿¤ê½ñ¤«¤Ê¤«¤Ã¤¿¤ê¤Ç¤­¤ë¤è¤¦¤Ë¡¢¾ò·ï¤Ë¤è¤ë + ¥í¥°¼ý½¸¤âÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï»°¤Ä¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥ÖÄ󶡤·¤Þ¤¹: + ¥í¥°¥Õ¥¡¥¤¥ë¤òºîÀ®¤¹¤ë¤¿¤á¤Î TransferLog, + ¿·¤·¤¤½ñ¼°¤ò ÄêµÁ¤¹¤ë LogFormat, + ¥í¥°¥Õ¥¡¥¤¥ë¤È ½ñ¼°¤ò°ìÅÙ¤ËÄêµÁ¤¹¤ë CustomLog ¤Ç¤¹¡£ + ³Æ¥ê¥¯¥¨¥¹¥È¤¬Ê£¿ô²ó¥í¥°¼ý½¸¤µ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë + TransferLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + CustomLog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÊ£¿ô²ó»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
+ +
top
+
+

¥«¥¹¥¿¥à¥í¥°½ñ¼°

+ +

LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + CustomLog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î½ñ¼°¤ò»ØÄꤹ¤ë°ú¿ô¤Ïʸ»úÎó¤Ç¤¹¡£¤³¤Îʸ»úÎó¤ò»È¤Ã¤Æ¤½¤ì¤¾¤ì¤Î + ¥ê¥¯¥¨¥¹¥È¤¬¥í¥°¥Õ¥¡¥¤¥ë¤Ë¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹¡£¤½¤Îʸ»úÎó¤Ë¤Ï + ¥í¥°¥Õ¥¡¥¤¥ë¤Ë¤½¤Î¤Þ¤Þ + ½ñ¤«¤ì¤ëʸ»úÎó¤ä¡¢¤½¤ì¤¾¤ì²þ¹Ô¤È¥¿¥Ö¤òɽ¤¹ C ¸À¸ì + ·Á¼°¤ÎÀ©¸æʸ»ú "\n" ¤È "\t" + ¤È¤ò´Þ¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤½¤Î¤Þ¤Þ½ÐÎϤµ¤»¤¿¤¤°úÍÑÉä¤È¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Ï + ¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Ç¥¨¥¹¥±¡¼¥×¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

¥ê¥¯¥¨¥¹¥È¤ÎÆÃħ¤½¤Î¤â¤Î¤Ï "%" + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¼°¤Îʸ»úÎó¤Ë½ñ¤¯¤³¤È¤Ç + ¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹¡£"%" + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥í¥°¥Õ¥¡¥¤¥ëÃæ¤Ç¤Ï°Ê²¼¤Î¤è¤¦¤Ê + ÃͤÇÃÖ´¹¤µ¤ì¤Þ¤¹:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎóÀâÌÀ
%%¥Ñ¡¼¥»¥ó¥Èµ­¹æ
%a¥ê¥â¡¼¥È IP ¥¢¥É¥ì¥¹
%A¥í¡¼¥«¥ë IP ¥¢¥É¥ì¥¹
%B¥ì¥¹¥Ý¥ó¥¹¤Î¥Ð¥¤¥È¿ô¡£HTTP ¥Ø¥Ã¥À¤Ï½ü¤¯¡£
%b¥ì¥¹¥Ý¥ó¥¹¤Î¥Ð¥¤¥È¿ô¡£HTTP ¥Ø¥Ã¥À¤Ï½ü¤¯¡£CLF ½ñ¼°¡£ + ¤¹¤Ê¤ï¤Á¡¢1 ¥Ð¥¤¥È¤âÁ÷¤é¤ì¤Ê¤«¤Ã¤¿¤È¤­¤Ï 0 ¤Ç¤Ï¤Ê¤¯¡¢ + '-' ¤Ë¤Ê¤ë
%{Foobar}C¥µ¡¼¥Ð¤ËÁ÷¤é¤ì¤¿¥ê¥¯¥¨¥¹¥ÈÃæ¤Î¥¯¥Ã¥­¡¼ Foobar ¤ÎÃÍ
%D¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤¹¤ë¤Î¤Ë¤«¤«¤Ã¤¿»þ´Ö¡¢¥Þ¥¤¥¯¥íÉÃñ°Ì
%{FOOBAR}e´Ä¶­ÊÑ¿ô FOOBAR ¤ÎÆâÍÆ
%f¥Õ¥¡¥¤¥ë̾
%h¥ê¥â¡¼¥È¥Û¥¹¥È
%H¥ê¥¯¥¨¥¹¥È¥×¥í¥È¥³¥ë
%{Foobar}i¥µ¡¼¥Ð¤ËÁ÷¤é¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î Foobar: + ¥Ø¥Ã¥À¤ÎÆâÍÆ
%l(identd ¤«¤é¤â¤·Ä󶡤µ¤ì¤Æ¤¤¤ì¤Ð) ¥ê¥â¡¼¥È¥í¥°Ì¾¡£ + ¤³¤ì¤Ï mod_ident ¤¬¥µ¡¼¥Ð¤Ë¸ºß¤·¤Æ¡¢ + IdentityCheck + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ On ¤ËÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢ + - ¤Ë¤Ê¤ê¤Þ¤¹¡£
%m¥ê¥¯¥¨¥¹¥È¥á¥½¥Ã¥É
%{Foobar}n¾¤Î¥â¥¸¥å¡¼¥ë¤«¤é¤Î¥á¥â Foobar ¤ÎÆâÍÆ
%{Foobar}o±þÅú¤Î Foobar: ¥Ø¥Ã¥À¤ÎÆâÍÆ
%p¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤Æ¤¤¤ë¥µ¡¼¥Ð¤ÎÀµ¼°¤Ê¥Ý¡¼¥È
%P¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤¿»Ò¥×¥í¥»¥¹¤Î¥×¥í¥»¥¹ ID
%{format}P¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤¿¥ï¡¼¥«¡¼¤Î¥×¥í¥»¥¹ ID ¤«¥¹¥ì¥Ã¥É ID¡£ + format ¤È¤·¤ÆÍ­¸ú¤ÊÃÍ¤Ï pid, tid, + hextid ¤Ç¤¹¡£hextid ¤ò»È¤¦¤Ë¤Ï + APR 1.2.0 °Ê¹ß¤¬É¬ÍפǤ¹¡£ +
%qÌ䤤¹ç¤»Ê¸»úÎó (¸ºß¤¹¤ë¾ì¹ç¤ÏÁ°¤Ë ? ¤¬Äɲ䵤ì¤ë¡£ + ¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤Ï¶õʸ»úÎó)
%r¥ê¥¯¥¨¥¹¥È¤ÎºÇ½é¤Î¹Ô
%s¥¹¥Æ¡¼¥¿¥¹¡£ÆâÉô¤Ç¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Ï¡¢¸µ¡¹¤Î + ¥ê¥¯¥¨¥¹¥È¤Î¥¹¥Æ¡¼¥¿¥¹ --- ºÇ¸å¤Î¥¹¥Æ¡¼¥¿¥¹¤Ï %>s +
%t¥ê¥¯¥¨¥¹¥È¤ò¼õÉÕ¤±¤¿»þ¹ï¡£ + CLF ¤Î»þ¹ï¤Î½ñ¼° (ɸ½à¤Î±Ñ¸ì¤Î½ñ¼°)
%{format}tformat ¤ÇÍ¿¤¨¤é¤ì¤¿½ñ¼°¤Ë¤è¤ë»þ¹ï¡£format ¤Ï + strftime (3) ¤Î + ½ñ¼°¤Ç¤¢¤ëɬÍפ¬¤¢¤ë¡£(ÃÏ°è²½¤µ¤ì¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ë)
%T¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤Î¤Ë¤«¤«¤Ã¤¿»þ´Ö¡¢ÉÃñ°Ì
%u¥ê¥â¡¼¥È¥æ¡¼¥¶ (ǧ¾Ú¤Ë¤è¤ë¤â¤Î¡£¥¹¥Æ¡¼¥¿¥¹ (%s) ¤¬ + 401 ¤Î¤È¤­¤Ï°ÕÌ£¤¬¤Ê¤¤¤â¤Î¤Ç¤¢¤ë²ÄǽÀ­¤¬¤¢¤ë) +
%U¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿ URL ¥Ñ¥¹¡£¥¯¥¨¥êʸ»úÎó¤Ï´Þ¤Þ¤Ê¤¤
%v¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤Æ¤¤¤ë¥µ¡¼¥Ð¤ÎÀµ¼°¤Ê ServerName
%VUseCanonicalName ¤ÎÀßÄê¤Ë¤è¤ë¥µ¡¼¥Ð̾
%X±þÅú¤¬´°Î»¤·¤¿¤È¤­¤ÎÀܳ¥¹¥Æ¡¼¥¿¥¹: + + + + + + + + + +
X =±þÅú¤¬´°Î»¤¹¤ëÁ°¤ËÀܳ¤¬°Û¾ï½ªÎ»
+ =±þÅú¤¬Á÷¤é¤ì¤¿¸å¤ËÀܳ¤ò»ý³¤¹¤ë¤³¤È¤¬²Äǽ
- = ±þÅú¤¬Á÷¤é¤ì¤¿¸å¤ËÀܳ¤¬ÀÚ¤é¤ì¤ë
+ +

(¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache + 1.3 ¤Î¸å´ü¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï %c ¤Ë³ä¤êÅö¤Æ¤é¤ì¤Æ + ¤¤¤Þ¤·¤¿¤¬¡¢¤³¤ì¤ÏÎò»ËŪ¤Ë ssl ¤¬»ÈÍѤ·¤Æ¤¤¤ë + %{var}c + ¹½Ê¸¤È¾×Æͤ·¤Æ¤¤¤Þ¤·¤¿¡£)

%I¥ê¥¯¥¨¥¹¥È¤È¥Ø¥Ã¥À¤ò´Þ¤à¡¢¼õ¤±¼è¤Ã¤¿¥Ð¥¤¥È¿ô¡£ + 0 ¤Ë¤Ï¤Ê¤é¤Ê¤¤¡£ + ¤³¤ì¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï mod_logio ¤¬É¬Í×
%O¥Ø¥Ã¥À¤ò´Þ¤à¡¢Á÷¿®¤·¤¿¥Ð¥¤¥È¿ô¡£0 ¤Ë¤Ï¤Ê¤é¤Ê¤¤¡£ + ¤³¤ì¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï mod_logio ¤¬É¬Í×
+ +

½¤¾þ»Ò

+ +

ÆÃÄê¤ÎÍ×ÁÇ¤Ï "%" ¤Îľ¸å¤Ë HTTP ¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤ò¥«¥ó¥Þ¶èÀÚ¤ê¤Ç + »ØÄꤹ¤ë¤³¤È¤Ç¡¢É½¼¨¤òÀ©¸Â¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð + "%400,501{User-agent}i" ¤Ç¤Ï¡¢ + 400 ¤È 500 ÈÖ¥¨¥é¡¼¤Ç¤Î¤ß User-agent ¤ò¥í¥°¤·¤Þ¤¹¡£ + ¾¤Î¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤Ç¤Ï "-" ¤È¤¤¤¦Ê¸»úÎó¤¬ + ¥í¥°¤µ¤ì¤Þ¤¹¡£¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤Î¥ê¥¹¥È¤Ï "!" + ¤ÇÈÝÄê¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹ : + "%!200,304,302{Referer}i" ¤Ï¡¢»ØÄꤵ¤ì¤¿ + 3 ¤Ä¤Î¥³¡¼¥É¤Î¤É¤ì¤Ë¤â³ºÅö¤·¤Ê¤¤¥ê¥¯¥¨¥¹¥ÈÁ´¤Æ¤Ç + Referer ¤ò¥í¥°¤·¤Þ¤¹¡£

+ +

½¤¾þ»Ò "<" ¤È ">" ¤ÏÆâÉô¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î¥í¥°¤Ë + ¸µ¤Î¥ê¥¯¥¨¥¹¥È¤«ºÇ½ªÅª¤Ê¥ê¥¯¥¨¥¹¥È¤Î¤É¤Á¤é¤ò»ÈÍѤ¹¤ë¤«¤ò + »ØÄꤹ¤ë¤¿¤á¤Ë»È¤¤¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢% ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + %s, %U, %T, %D, %r ¤Ï¸µ¤Î¥ê¥¯¥¨¥¹¥È¤ò¡¢Â¾¤ÏºÇ½ªÅª¤Ê¥ê¥¯¥¨¥¹¥È¤ò + »ÈÍѤ·¤Þ¤¹¡£Î㤨¤Ð¡¢¥ê¥¯¥¨¥¹¥È¤ÎºÇ½ª¥¹¥Æ¡¼¥¿¥¹¤òµ­Ï¿¤¹¤ë¤Ë¤Ï + %>s ¤ò¡¢ÆâÉôŪ¤Ëǧ¾Ú¤µ¤ì¤Æ¤¤¤Ê¤¤¥ê¥½¡¼¥¹¤Ø¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤¿ + ¥ê¥¯¥¨¥¹¥È¤Ç¸µ¤Î¥ê¥¯¥¨¥¹¥È¤Çǧ¾Ú¤µ¤ì¤¿¥æ¡¼¥¶¤òµ­Ï¿¤¹¤ë¤¿¤á¤Ë¤Ï + %<u ¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ + + +

¤½¤Î¾Ãí°ÕÅÀ

+ +

¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÍýͳ¤Ë¤è¤ê 2.0.46 ¤è¤ê¡¢ + %r, %i, %o ¤ËÆþ¤Ã¤Æ¤¤¤ë¡¢ + °õ»úÉÔ²Äǽ¤Êʸ»ú¤È¾¤ÎÆÃÊ̤Êʸ»ú¤Ï¡¢\xhh + ¤È¤¤¤¦·Á¼°¤Îʸ»úÎó¤Ç¥¨¥¹¥±¡¼¥×¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£hh ¤Ï + ¤½¤Î¤Þ¤Þ¤Î¥Ð¥¤¥È¤ÎÃͤΠ16 ¿Ê¤Ç¤ÎÃͤǤ¹¡£¤³¤Îµ¬Â§¤ÎÎã³°¤Ë¤Ï¡¢ + ¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤ò»È¤Ã¤Æ¥¨¥¹¥±¡¼¥×¤µ¤ì¤ë " ¤È \ ¤È¡¢ + C ·Á¼°¤Îɽµ­Ë¡¤¬»È¤ï¤ì¤ë¶õÇòʸ»ú (\n, \t ¤Ê¤É) + ¤¬¤¢¤ê¤Þ¤¹¡£2.0.46 °ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¥¨¥¹¥±¡¼¥×½èÍý¤Ï¹Ô¤ï¤ì¤Þ¤»¤ó¤Î¤Ç¡¢ + À¸¥í¥°¥Õ¥¡¥¤¥ë¤ò°·¤¦ºÝ¤ËÃí°Õ¤¬É¬ÍפǤ¹¡£

+ +

httpd 2.0 ¤Ç¤Ï 1.3 ¤È¤Ï°Û¤Ê¤ê¡¢%b ¤È %B + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¿®¤µ¤ì¤¿¥Ð¥¤¥È¿ô¤½¤Î¤â¤Î¤Ç¤Ï¤Ê¤¯¡¢ + HTTP ¥ì¥¹¥Ý¥ó¥¹¤Î¥Ð¥¤¥È¿ô¤Ç¤¹ (¤³¤ì¤é¤Ï°Û¤Ê¤ë¤â¤Î¤Ç¡¢¤¿¤È¤¨¤Ð¡¢ + ¥³¥Í¥¯¥·¥ç¥ó¤¬ÅÓÃæ¤ÇÇË´þ¤µ¤ì¤¿¾ì¹ç¤ä¡¢SSL »ÈÍÑ»þ¤Ë°ìÃפ·¤Þ¤»¤ó) ¡£ + mod_logio ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë %O + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ç¡¢¥Í¥Ã¥È¥ï¡¼¥¯·Ðͳ¤Ç¼ÂºÝ¤ËžÁ÷¤µ¤ì¤¿¥Ð¥¤¥È¿ô¤ò + µ­Ï¿¤Ç¤­¤Þ¤¹¡£

+ + + +

Îã

+ +

¤è¤¯»È¤ï¤ì¤ë¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ï:

+ +
+
Common Log Format (CLF)
+
"%h %l %u %t \"%r\" %>s %b"
+ +
¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈÉÕ¤­ Common Log Format
+
"%v %h %l %u %t \"%r\" %>s %b"
+ +
NCSA extended/combined ¥í¥°½ñ¼°
+
"%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\""
+ +
Referer ¥í¥°½ñ¼°
+
"%{Referer}i -> %U"
+ +
Agent (¥Ö¥é¥¦¥¶) ¥í¥°½ñ¼°
+
"%{User-agent}i"
+
+ +
top
+
+

¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤·¤Æ

+

¥í¥°¥Õ¥¡¥¤¥ë¤¬Êݸ¤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤¬¥µ¡¼¥Ð¤òµ¯Æ°¤·¤¿°Ê³°¤Î¥æ¡¼¥¶¤Ç + ½ñ¤­¹þ¤ß²Äǽ¤Ê¤È¤­¤Ë¥»¥­¥å¥ê¥Æ¥£¤ÎÌäÂ꤬ȯÀ¸¤¹¤ëÍýͳ¤Î¾ÜºÙ¤Ï¥»¥­¥å¥ê¥Æ¥£¤Î¤³¤Ä + ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+
top
+

BufferedLogs ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Ç¥£¥¹¥¯¤Ë½ñ¤­½Ð¤¹Á°¤Ë¥á¥â¥ê¤Ë¥í¥°¥¨¥ó¥È¥ê¤ò¥Ð¥Ã¥Õ¥¡¤¹¤ë
¹½Ê¸:BufferedLogs On|Off
¥Ç¥Õ¥©¥ë¥È:BufferedLogs Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_log_config
¸ß´¹À­:2.0.41 °Ê¹ß
+

BufferedLogs ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤È + mod_log_config ¤ÎµóÆ°¤¬ÊѲ½¤·¤Æ¡¢ + Ê£¿ô¤Î¥í¥°¤ò½ñ¤­½Ð¤¹ºÝ¤Ë¡¢¤½¤ì¤¾¤ì¤Î¥ê¥¯¥¨¥¹¥È½èÍý¸åËè¤Ë + ½ñ¤­½Ð¤¹¤Î¤Ç¤Ï¤Ê¤¯¡¢¤¤¤Ã¤¿¤ó¥á¥â¥ê¤ËÃߤ¨¤Æ¤«¤é¡¢ + ¤Þ¤È¤á¤Æ¥Ç¥£¥¹¥¯¤Ë½ñ¤­½Ð¤¹¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤Î·ë²Ì¥Ç¥£¥¹¥¯¥¢¥¯¥»¥¹¤¬¤è¤ê¸úΨŪ¤Ë¤Ê¤ê¡¢ + ¹â¤¤¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤ÎÆÀ¤é¤ì¤ë¥·¥¹¥Æ¥à¤â¤¢¤ë¤Ç¤·¤ç¤¦¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥µ¡¼¥ÐÁ´ÂΤǰìÅÙ¤À¤±ÀßÄê¤Ç¤­¤Þ¤¹; + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤´¤È¤ËÀßÄꤹ¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£

+ +
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¼Â¸³Åª¤Ê¤â¤Î¤Ç¤¹¤Î¤Ç¡¢ + »ÈÍѤ¹¤ëºÝ¤ÏÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£
+ +
+
top
+

CookieLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥Ã¥­¥ó¥°¤Î¥í¥®¥ó¥°¤Î¤¿¤á¤Î¥Õ¥¡¥¤¥ë̾¤òÀßÄꤹ¤ë
¹½Ê¸:CookieLog filename
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_log_config
¸ß´¹À­:¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÈó¿ä¾©
+

CookieLog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¯¥Ã¥­¡¼¤Î¥í¥®¥ó¥°¤Î¤¿¤á¤Î¥Õ¥¡¥¤¥ë̾¤ò + ÀßÄꤷ¤Þ¤¹¡£filename ¤Ï ServerRoot + ¤«¤é¤ÎÁêÂХѥ¹¤Ç¤¹¡£¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï mod_cookies ¤È¤Î¸ß´¹À­¤Î¤¿¤á¤À¤±¤Ë + ¸ºß¤·¡¢»ÈÍѤϿ侩¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£

+ +
+
top
+

CustomLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥í¥°¥Õ¥¡¥¤¥ë¤Î̾Á°¤È½ñ¼°¤òÀßÄꤹ¤ë
¹½Ê¸:CustomLog file|pipe +format|nickname +[env=[!]environment-variable]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_log_config
+

CustomLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥µ¡¼¥Ð¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò + ¥í¥°¼ý½¸¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£¥í¥°¤Î½ñ¼°¤¬»ØÄꤵ¤ì¡¢ + ´Ä¶­ÊÑ¿ô¤ò»È¤Ã¤Æ¥í¥®¥ó¥°¤¬¾ò·ï¤Ë±þ¤¸¤Æ¹Ô¤Ê¤ï¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

¥í¥°¤¬½ñ¤«¤ì¤ë¾ì½ê¤ò»ØÄꤹ¤ëºÇ½é¤Î°ú¿ô¤Ï°Ê²¼¤ÎÆó¤Ä¤Î·Á¼°¤ÎÃͤò + ¤È¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +
+
file
+
ServerRoot + ¤«¤é¤ÎÁêÂХѥ¹¤Çɽ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë̾¡£
+ +
pipe
+
¥Ñ¥¤¥×ʸ»ú "|" ¤È¡¢¤½¤Î¸å¤Ëɸ½àÆþÎϤ«¤é¥í¥°¤Î + ¾ðÊó¤ò¼õ¤±¤È¤ë¥×¥í¥°¥é¥à¤Ø¤Î¥Ñ¥¹¤¬Â³¤¤¤¿¤â¤Î¡£ + +

¥»¥­¥å¥ê¥Æ¥£

+

¤â¤·¥×¥í¥°¥é¥à¤¬»ÈÍѤµ¤ì¤¿¾ì¹ç¡¢ + httpd ¤¬µ¯Æ°¤µ¤ì¤¿¥æ¡¼¥¶¤È¤·¤Æ¼Â¹Ô¤µ¤ì¤Þ¤¹¡£¤³¤ì¤Ï¥µ¡¼¥Ð¤¬ + root ¤Ë¤è¤Ã¤Æµ¯Æ°¤µ¤ì¤¿¾ì¹ç¤Ï root ¤Ë¤Ê¤ê¤Þ¤¹¡£¥×¥í¥°¥é¥à¤¬ + °ÂÁ´¤Ç¤¢¤ë¤è¤¦¤Ëα°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+

Ãí

+

Unix ¤Ç¤Ê¤¤¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¥Õ¥¡¥¤¥ë¤Î¥Ñ¥¹¤òÆþÎϤ·¤Æ¤¤¤ë¤È¤­¤Ï¡¢ + »ÈÍѤ·¤Æ¤¤¤ë¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤¬¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Î»ÈÍѤòµö²Ä¤·¤Æ¤¤¤¿ + ¤È¤·¤Æ¡¢Ä̾ï¤Î¥¹¥é¥Ã¥·¥å¤À¤±¤ò»È¤¦¤è¤¦¤Ëµ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£ + °ìÈÌŪ¤Ë¡¢ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Ç¤Ï¾ï¤ËÉáÄ̤Υ¹¥é¥Ã¥·¥å¤Î¤ß¤ò»È¤¦¤è¤¦¤Ë¤¹¤ë + Êý¤¬Îɤ¤¤Ç¤¹¡£

+
+
+ +

Æó¤Ä¤á¤Î°ú¿ô¤Ï¥í¥°¥Õ¥¡¥¤¥ë¤Ë²¿¤¬½ñ¤«¤ì¤ë¤«¤ò»ØÄꤷ¤Þ¤¹¡£ + Á°¤Ë¤¢¤ë LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê + ÄêµÁ¤µ¤ì¤¿ nickname ¤«¡¢¥í¥°¤Î½ñ¼° + ¤Î¤È¤³¤í¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¡¢ÌÀ¼¨Åª¤Ê format ʸ»úÎó¤Î + ¤É¤Á¤é¤«¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢°Ê²¼¤ÎÆó¤Ä¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö·²¤ÏÁ´¤¯Æ±¤¸¸ú²Ì¤ò¤â¤¿¤é¤·¤Þ¤¹:

+ +

+ # CustomLog with format nickname
+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common
+
+ # CustomLog with explicit format string
+ CustomLog logs/access_log "%h %l %u %t \"%r\" %>s %b" +

+ +

»°¤ÄÌܤΰú¿ô¤Ï¾Êά²Äǽ¤Ç¡¢¥µ¡¼¥Ð¤Î´Ä¶­¤Ë¤¢¤ëÊÑ¿ô¤¬¤¢¤ë¤«¤Ê¤¤¤«¤Ë + ±þ¤¸¤Æ¥ê¥¯¥¨¥¹¥È¤ò¥í¥°¼ý½¸¤¹¤ë¤«¤É¤¦¤«¤òÀ©¸æ¤¹¤ë¤¿¤á¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + »ØÄꤵ¤ì¤¿´Ä¶­ÊÑ¿ô¤¬¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ + ÀßÄꤵ¤ì¤Æ¤¤¤¿¾ì¹ç ('env=!name' ʸ¤¬»È¤ï¤ì¤¿¤È¤­¤Ï + ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç)¡¢¥ê¥¯¥¨¥¹¥È¤¬¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹¡£

+ +

´Ä¶­ÊÑ¿ô¤Ï mod_setenvif ¥â¥¸¥å¡¼¥ë¤È + mod_rewrite ¥â¥¸¥å¡¼¥ë¤ÎξÊý¤â¤·¤¯¤Ï + ÊÒÊý¤òÍѤ¤¤Æ¥ê¥¯¥¨¥¹¥È¤´¤È¤ËÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + Î㤨¤Ð¡¢¥µ¡¼¥Ð¤Ë¤¢¤ë¤¹¤Ù¤Æ¤Î GIF ²èÁü¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤òÊÌ¤Î¥í¥°¥Õ¥¡¥¤¥ë + ¤Ë¤Ïµ­Ï¿¤·¤¿¤¤¤±¤ì¤É¡¢¥á¥¤¥ó¥í¥°¤Ë¤Ïµ­Ï¿¤·¤¿¤¯¤Ê¤¤¡¢¤È¤¤¤¦¤È¤­¤Ï + °Ê²¼¤Î¤â¤Î¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ SetEnvIf Request_URI \.gif$ gif-image
+ CustomLog gif-requests.log common env=gif-image
+ CustomLog nongif-requests.log common env=!gif-image +

+ +

¸Å¤¤ RefererIgnore ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈƱ¤¸µóÆ°¤ò¤µ¤»¤¿¤¤¾ì¹ç¤Ï¡¢ + ¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹:

+ +

+ SetEnvIf Referer example\.com localreferer
+ CustomLog referer.log referer env=!localreferer +

+ +
+
top
+

LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥í¥°¥Õ¥¡¥¤¥ë¤Ç»ÈÍѤ¹¤ë½ñ¼°¤òÀßÄꤹ¤ë
¹½Ê¸:LogFormat format|nickname +[nickname]
¥Ç¥Õ¥©¥ë¥È:LogFormat "%h %l %u %t \"%r\" %>s %b"
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_log_config
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¢¥¯¥»¥¹¥í¥°¥Õ¥¡¥¤¥ë¤Î½ñ¼°¤ò»ØÄꤷ¤Þ¤¹¡£

+ +

LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÆó¤Ä¤Î·Á¼°¤Î¤É¤Á¤é¤«¤ò + ¤È¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ºÇ½é¤Î·Á¼°¤Ç¤Ï°ì¤Ä¤Î°ú¿ô¤Î¤ß¤¬»ØÄꤵ¤ì¡¢ + ³¤¯ TransferLog + ¤Ç»ØÄꤵ¤ì¤¿¥í¥°¤Ç»È¤ï¤ì¤ë¥í¥°¤Î½ñ¼°¤òÀßÄꤷ¤Þ¤¹¡£¤³¤ÎñÆȤΰú¿ô¤Ç¤Ï + ¾å¤Î¥«¥¹¥¿¥à¥í¥°½ñ¼°¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë + format ¤òÌÀ¼¨Åª¤Ë»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤â¤·¤¯¤Ï¡¢²¼¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤ËÁ°¤Ë LogFormat + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÄêµÁ¤µ¤ì¤¿¥í¥°¤Î½ñ¼°¤ò nickname¤ò»È¤Ã¤Æ + »²¾È¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÆó¤Ä¤á¤Î·Á¼°¤Ï + format ¤Ë nickname ¤òÍ¿¤¨¤Þ¤¹¡£ + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎóÁ´ÂΤòºÆ¤Ó½ñ¤¯¤«¤ï¤ê¤Ë¡¢ + ¤³¤Î nickname ¤ò³¤­¤Î LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä + CustomLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + Nickname ¤òÄêµÁ¤¹¤ë LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¾¤Ë¤Ï²¿¤â¤·¤Þ¤»¤ó -- ¤¹¤Ê¤ï¤Á¡¢¥Ë¥Ã¥¯¥Í¡¼¥à¤òÄêµÁ + ¤¹¤ë¤À¤±¤Ç¡¢¼ÂºÝ¤Ë½ñ¼°¤òŬÍѤ·¤Æ¥Ç¥Õ¥©¥ë¥È¤Ë¤¹¤ë¤È¤¤¤¦¤³¤È¤Ï¹Ô¤Ê¤¤¤Þ¤»¤ó¡£ + ¤Ç¤¹¤«¤é¡¢¤³¤ì¤Ï³¤¯ TransferLog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤Ï±Æ¶Á¤òÍ¿¤¨¤Þ¤»¤ó¡£ + ¤µ¤é¤Ë¡¢LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï´û¸¤Î nickname ¤ò + »È¤Ã¤ÆÊ̤Πnickname ¤òÄêµÁ¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£Nickname ¤Ë¤Ï + ¥Ñ¡¼¥»¥ó¥Èµ­¹æ (%) ¤¬´Þ¤Þ¤ì¤Æ¤¤¤Æ¤Ï¤¤¤±¤Ê¤¤¤³¤È¤Ë¤âÃí°Õ + ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Îã

+ LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common +

+ +
+
top
+

TransferLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥í¥°¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ¤ò»ØÄê
¹½Ê¸:TransferLog file|pipe
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_log_config
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥í¥°½ñ¼°¤òľÀÜ»ØÄê¤Ç¤­¤Ê¤¤¤³¤È¤È¡¢ + ¾ò·ïÉÕ¤­¥í¥®¥ó¥°¤¬Ìµ¤¤¤³¤È¤ò½ü¤¯¤È¡¢CustomLog ¤ÈÁ´¤¯Æ±¤¸°ú¿ô¤È¸ú²Ì¤¬¤¢¤ê¤Þ¤¹¡£ + ľÀÜ¥í¥°½ñ¼°¤ò»ØÄꤹ¤ëÂå¤ï¤ê¤Ë¡¢¥í¥°¤Î½ñ¼°¤Ï¤½¤³¤Þ¤Ç¤Ç°ìÈֺǸå¤Ë»ØÄꤵ¤ì¤¿ + ¥Ë¥Ã¥¯¥Í¡¼¥à¤òÄêµÁ¤·¤Ê¤¤ + LogFormat ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤ÇÄêµÁ¤µ¤ì¤¿¤â¤Î¤ò»È¤¤¤Þ¤¹¡£ + ¤â¤·Â¾¤Î½ñ¼°¤¬Á´¤¯»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ï Common Log Format + ¤¬»È¤ï¤ì¤Þ¤¹¡£

+ +

Îã

+ LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\""
+ TransferLog logs/access_log +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_log_config.html.ko.euc-kr b/docs/manual/mod/mod_log_config.html.ko.euc-kr new file mode 100644 index 00000000..115a2fb4 --- /dev/null +++ b/docs/manual/mod/mod_log_config.html.ko.euc-kr @@ -0,0 +1,401 @@ + + + +mod_log_config - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_log_config

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:¼­¹ö·ÎÀÇ ¿äûÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù
»óÅÂ:Base
¸ðµâ¸í:log_config_module
¼Ò½ºÆÄÀÏ:mod_log_config.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº Ŭ¶óÀ̾ðÆ®ÀÇ ¿äûÀ» ·Î±×¿¡ ÀÚÀ¯·Ó°Ô ±â·ÏÇÑ´Ù. + ÀÚ½ÅÀÌ ¿øÇÏ´Â Çü½ÄÀ¸·Î ·Î±×¸¦ ±â·ÏÇÒ ¼ö ÀÖ°í, ÆÄÀÏÀ̳ª ¿ÜºÎ + ÇÁ·Î±×·¥¿¡ Á÷Á¢ ·Î±×¸¦ º¸³¾ ¼öµµ ÀÖ´Ù. Á¶°ÇÀû ·Î±×¸¦ »ç¿ëÇϸé + ¿äûÀÇ ¼º°Ý¿¡ µû¶ó ¿äûÀ» ·Î±×¿¡ Ãß°¡Çϰųª Á¦¿ÜÇÒ ¼ö ÀÖ´Ù.

+ +

ÀÌ ¸ðµâÀº ¼¼°¡Áö Áö½Ã¾î¸¦ Á¦°øÇÑ´Ù. TransferLog´Â ·Î±×ÆÄÀÏÀ» + ¸¸µé°í, LogFormatÀº + ¿øÇÏ´Â Çü½ÄÀ» Á¤ÇÏ°í, CustomLog´Â Çѹø¿¡ ·Î±×ÆÄÀÏ°ú + Çü½ÄÀ» ¸ðµÎ ÁöÁ¤ÇÑ´Ù. TransferLog¿Í + CustomLog Áö½Ã¾î¸¦ ¿©·¯¹ø »ç¿ëÇϸé + ¿äûÀ» ¿©·¯ ÆÄÀÏ¿¡ ±â·ÏÇÒ ¼ö ÀÖ´Ù.

+
+ +
top
+
+

·Î±× Çü½Ä ÁöÁ¤Çϱâ

+ +

LogFormat°ú + CustomLog + Áö½Ã¾îÀÇ Çü½Ä ¾Æ±Ô¸ÕÆ®´Â ¹®ÀÚ¿­ÀÌ´Ù. ÀÌ ¹®ÀÚ¿­¿¡ µû¶ó ¿äûÀ» + ·Î±×ÆÄÀÏ¿¡ ±â·ÏÇÑ´Ù. ¹®ÀÚ¿­¿¡´Â ·Î±×ÆÄÀÏ¿¡ ±×´ë·Î º¹»çµÇ´Â + ¹®ÀÚ¿Í Çà¹Ù²Þ°ú ÅÇÀ» ³ªÅ¸³»´Â CÀÇ "\n"°ú "\t" Á¦¾î¹®ÀÚ¸¦ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. ·Î±×ÆÄÀÏ¿¡ µû¿ÈÇ¥³ª ¹é½½·¡½¬¸¦ ¾²·Á¸é ¾Õ¿¡ + ¹Ýµå½Ã ¹é½½·¡½¬¸¦ Àû¾îÁà¾ß ÇÑ´Ù.

+ +

¿äûÀÇ Æ¯Â¡Àº Çü½Ä ¹®ÀÚ¿­¿¡ "%" Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© ±â·ÏÇÑ´Ù. ÀÌ Áö½Ã¾î´Â ·Î±×ÆÄÀÏ¿¡¼­ ´ÙÀ½°ú °°ÀÌ + º¯°æµÈ´Ù.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Çü½Ä ¹®ÀÚ¿­¼³¸í
%%ÆÛ¼¾Æ® ±âÈ£
%...a¿ø°Ý IP-ÁÖ¼Ò
%...A(¼­¹ö) IP-ÁÖ¼Ò
%...BHTTP Çì´õ¸¦ Á¦¿ÜÇÑ Àü¼Û ¹ÙÀÌÆ®¼ö.
%...bHTTP Çì´õ¸¦ Á¦¿ÜÇÑ Àü¼Û ¹ÙÀÌÆ®¼ö. CLF Çü½Ä°ú °°ÀÌ + Àü¼ÛÇÑ ³»¿ëÀÌ ¾ø´Â °æ¿ì 0 ´ë½Å '-'°¡ ³ª¿Â´Ù.
%...{Foobar}C¼­¹ö°¡ ¼ö½ÅÇÑ ¿äû¿¡¼­ Foobar ÄíÅ°ÀÇ + ³»¿ë.
%...D¿äûÀ» ó¸®Çϴµ¥ °É¸° ½Ã°£ (¸¶ÀÌÅ©·ÎÃÊ ´ÜÀ§).
%...{FOOBAR}eȯ°æº¯¼ö FOOBARÀÇ ³»¿ë
%...fÆÄÀϸí
%...h¿ø°Ý È£½ºÆ®
%...H¿äû ÇÁ·ÎÅäÄÝ
%...{Foobar}i¼­¹ö°¡ ¼ö½ÅÇÑ ¿äû¿¡¼­ Foobar: + Çì´õÀÇ ³»¿ë.
%...l(ÀÖ´Ù¸é identd°¡ Á¦°øÇÑ) ¿ø°Ý ·Î±×Àθí. + mod_ident°¡ ÀÖ°í IdentityCheck°¡ + OnÀÌ ¾Æ´Ï¸é »©±â±âÈ£¸¦ ±â·ÏÇÑ´Ù.
%...m¿äû ¸Þ½áµå
%...{Foobar}n´Ù¸¥ ¸ðµâÀÌ ±â·ÏÇÑ Foobar ³ëÆ®(note) + ³»¿ë.
%...{Foobar}oÀÀ´äÀÇ Foobar: Çì´õ ³»¿ë.
%...p¿äûÀ» ¼­ºñ½ºÇÏ´Â ¼­¹öÀÇ Á¤±Ô Æ÷Æ®
%...P¿äûÀ» ¼­ºñ½ºÇÏ´Â ÀÚ½ÄÀÇ ÇÁ·Î¼¼½º ID.
%...{format}P¿äûÀ» ¼­ºñ½ºÇÏ´Â ÀÚ½ÄÀÇ ÇÁ·Î¼¼½º ID ȤÀº ¾²·¹µå + ID. format¿¡´Â pid¿Í tid°¡ + °¡´ÉÇÏ´Ù. +
%...qÁúÀǹ®ÀÚ¿­ (ÁúÀǹ®ÀÚ¿­ÀÌ ÀÖ´Ù¸é ¾Õ¿¡ ?¸¦ + ºÙÀÌ°í, ¾ø´Ù¸é ºó ¹®ÀÚ¿­)
%...r¿äûÀÇ Ã¹¹ø° ÁÙ
%...s»óÅÂ(status). ³»ºÎ ¸®´ÙÀÌ·º¼ÇµÈ ¿äûÀÇ °æ¿ì *¿ø·¡* + ¿äûÀÇ »óÅÂÀÌ´Ù. ÃÖÁ¾ ¿äûÀÇ »óÅ´ %...>s.
%...tcommon log format ½Ã°£ Çü½Ä(Ç¥ÁØ ¿µ¾î Çü½Ä)ÀÇ ½Ã°£
%...{format}tstrftime(3) Çü½Ä formatÀÇ ½Ã°£. (Áö¿ª½Ã°£ÀÏ + ¼ö ÀÖÀ½)
%...T¿äûÀ» ó¸®Çϴµ¥ °É¸° ½Ã°£ (ÃÊ ´ÜÀ§).
%...u¿ø°Ý »ç¿ëÀÚ (auth°¡ Á¦°øÇϸç, »óÅÂ(%s)°¡ + 401ÀÎ °æ¿ì ÀÌ»óÇÑ °ªÀ» ³ª¿Ã ¼ö ÀÖÀ½)
%...UÁúÀǹ®ÀÚ¿­À» Á¦¿ÜÇÑ ¿äû URL °æ·Î.
%...v¿äûÀ» ¼­ºñ½ºÇÑ ¼­¹öÀÇ Á¤±Ô ServerName.
%...VUseCanonicalName + ¼³Á¤¿¡ µû¸¥ ¼­¹ö¸í.
%...XÀÀ´äÀ» ¸¶ÃÆÀ»¶§ ¿¬°á »óÅÂ. + + + + + + + + + +
X =ÀÀ´äÀ» ¸¶Ä¡±â Àü¿¡ ¿¬°áÀÌ ²÷¾îÁ³´Ù.
+ =ÀÀ´äÀ» º¸³½ÈÄ¿¡µµ ¿¬°áÀÌ »ì¾ÆÀÖ´Ù(keep alive).
- = ÀÀ´äÀ» º¸³½ÈÄ ¿¬°áÀÌ ²÷¾îÁ³´Ù.
+ +

(¾ÆÆÄÄ¡ 1.3 ÈÄ¹Ý ¹öÀü¿¡¼­ ÀÌ Áö½Ã¾î´Â + %...c¿´Áö¸¸, ÀüÅëÀûÀÎ ssl + %...{var}c ¹®¹ý°ú °ãÃļ­ + º¯°æÇß´Ù.)

%...I¿äû°ú Çì´õ¸¦ Æ÷ÇÔÇÑ ¼ö½Å ¹ÙÀÌÆ®¼ö·Î 0ÀÏ ¼ö ¾ø´Ù. + À̸¦ »ç¿ëÇÏ·Á¸é mod_logio°¡ ÇÊ¿äÇÏ´Ù.
%...OÇì´õ¸¦ Æ÷ÇÔÇÑ ¼Û½Å ¹ÙÀÌÆ®¼ö·Î 0ÀÏ ¼ö ¾ø´Ù. À̸¦ + »ç¿ëÇÏ·Á¸é mod_logio°¡ ÇÊ¿äÇÏ´Ù.
+ +

"..."¿¡´Â (¿¹¸¦ µé¾î, + "%h %u %r %s %b") ¾Æ¹«°Íµµ ¾ø°Å³ª, Ç׸ñÀ» Æ÷ÇÔÇÒ + Á¶°ÇÀÌ ³ª¿Â´Ù (Á¶°ÇÀ» ¸¸Á·ÇÏÁö ¾ÊÀ¸¸é ÀÚ¸®¿¡ "-"¸¦ ±â·ÏÇÑ´Ù). + Á¶°ÇÀº ¾Õ¿¡ "!"¸¦ ºÙÀ̰ųª ¾ÈºÙÀÎ HTTP »óÅÂÄÚµå ¸ñ·ÏÀ¸·Î + ÀÛ¼ºÇÑ´Ù. ¿¹¸¦ µé¾î, "%400,501{User-agent}i"´Â 400 (Bad + Request) ¿À·ù¿Í 501 (Not Implemented) ¿À·ùÀ϶§¸¸ + User-agent:¸¦ ·Î±×¿¡ ³²±â°í, + "%!200,304,302{Referer}i"´Â Á¤»óÀûÀÎ »óÅ°¡ ¾Æ´Ñ + ¸ðµç ¿äû¿¡ ´ëÇØ Referer:¸¦ ·Î±×¿¡ ³²±ä´Ù.

+ +

¼öÁ¤ÀÚ "<"¿Í ">"´Â ³»ºÎ ¸®´ÙÀÌ·º¼ÇµÈ ¿äû¿¡¼­ °¢°¢ + óÀ½ ¿äûÀ» ¸»ÇÒÁö ¸¶Áö¸· ¿äûÀ» ¸»ÇÒÁö ¼±ÅÃÇÑ´Ù. ±âº»ÀûÀ¸·Î + %s, %U, %T, %D, %rÀº óÀ½ ¿äûÀ» º¸°í, ³ª¸ÓÁö + % Áö½Ã¾î´Â ¸¶Áö¸· ¿äûÀ» º»´Ù. ±×·¡¼­ + %>s´Â ¿äûÀÇ ¸¶Áö¸· »óÅÂ(status)¸¦ ±â·ÏÇÏ°í, + %<u´Â ÀÎÁõÀ¸·Î º¸È£ÇÏÁö ¾Ê´Â ÀÚ¿øÀ¸·Î ³»ºÎ + ¶ó´ÙÀÌ·º¼ÇµÈ °æ¿ì¿¡µµ óÀ½¿¡ ÀÎÁõÇÑ »ç¿ëÀÚ¸¦ ±â·ÏÇÑ´Ù.

+ +

2.0.46 ÀÌÀüÀÇ httpd 2.0 ¹öÀüÀº %...r, + %...i, %...oÀÇ °á°ú ¹®ÀÚ¿­À» ±×´ë·Î + µÎ¾ú´Ù. ÀÌÀ¯´Â Common Log FormatÀÇ ¿ä±¸»çÇ×À» µû¸£±âÀ§Çؼ­¿´´Ù. + Áï, Ŭ¶óÀ̾ðÆ®°¡ Á¦¾î¹®ÀÚ¸¦ ·Î±×¿¡ Áý¾î³ÖÀ» ¼ö Àֱ⶧¹®¿¡ + ·Î±×ÆÄÀÏÀ» ±×´ë·Î ´Ù·ê ¶§´Â Á¶½ÉÇØ¾ß ÇÑ´Ù.

+ +

º¸¾È»ó ÀÌÀ¯·Î 2.0.46ºÎÅÍ Ãâ·ÂÇÒ ¼ö ¾ø´Â ¹®ÀÚ³ª ´Ù¸¥ Ư¼ö¹®ÀÚ¸¦ + \xhh·Î Ç¥ÇöÇÑ´Ù. ¿©±â¼­ hh´Â + ÇØ´ç ¹ÙÀÌÆ®ÀÇ 16Áø¼ö Ç¥ÇöÀ» ³ªÅ¸³½´Ù. ÀÌ ±ÔÄ¢ÀÇ ¿¹¿Ü´Â ¹é½½·¡½¬¸¦ + ¾Õ¿¡ ºÙÀÌ´Â "¿Í \, ±×¸®°í C¾ð¾î + Çü½ÄÀÇ °ø¹é¹®ÀÚµé(\n, \t µî)ÀÌ´Ù.

+ +

ÀϹÝÀûÀ¸·Î ¸¹ÀÌ »ç¿ëÇÏ´Â ·Î±× Çü½ÄÀº ´ÙÀ½°ú °°´Ù.

+ +
+
Common Log Format (CLF)
+
"%h %l %u %t \"%r\" %>s %b"
+ +
°¡»óÈ£½ºÆ® Á¤º¸¸¦ Æ÷ÇÔÇÑ Common Log Format
+
"%v %h %l %u %t \"%r\" %>s %b"
+ +
NCSA extended/combined ·Î±× Çü½Ä
+
"%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\""
+ +
Referer ·Î±× Çü½Ä
+
"%{Referer}i -> %U"
+ +
Agent (ºê¶ó¿ìÀú) ·Î±× Çü½Ä
+
"%{User-agent}i"
+
+ +

¿äûÀ» ¼­ºñ½ºÇÏ´Â ¼­¹öÀÇ Á¤±Ô ServerName°ú ListenÀº °¢°¢ %v¿Í + %p¸¦ »ç¿ëÇÑ´Ù. ·Î±×ºÐ¼® ÇÁ·Î±×·¥ÀÌ ½ÇÁ¦·Î ¿äûÀ» + ¼­ºñ½ºÇϴ ȣ½ºÆ®¸¦ ¾Ë±âÀ§ÇØ °¡»óÈ£½ºÆ® ã±â ¾Ë°í¸®ÁòÀ» + °¡Áú ÇÊ¿ä¾øµµ·Ï ÀÌµé °ªÀº UseCanonicalName ¼³Á¤°ú ¹«°üÇÏ´Ù.

+
top
+
+

º¸¾È»ó °í·ÁÇÒ Á¡

+

¼­¹ö¸¦ ½ÃÀÛÇÏ´Â »ç¿ëÀÚ¿Ü¿¡ ´Ù¸¥ »ç¿ëÀÚ°¡ ·Î±×ÆÄÀÏÀ» ÀúÀåÇÏ´Â + µð·ºÅ丮¿¡ ¾²±â ±ÇÇÑÀ» °¡Áú¶§ ¿Ö º¸¾È¿¡ ¹®Á¦°¡ »ý±â´ÂÁö + º¸¾È ÆÁ + ¹®¼­¸¦ Âü°íÇ϶ó.

+
+
top
+

CookieLog Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÄíÅ°¸¦ ·Î±×¿¡ ³²±â±âÀ§ÇØ »ç¿ëÇÒ ÆÄÀϸíÀ» ¼³Á¤ÇÑ´Ù
¹®¹ý:CookieLog filename
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_log_config
Áö¿ø:ÀÌ Áö½Ã¾î´Â »ç¿ëµÇÁö ¾Ê´Â´Ù.
+

CookieLog Áö½Ã¾î´Â ÄíÅ°¸¦ ·Î±×¿¡ + ³²±â±âÀ§ÇØ »ç¿ëÇÒ ÆÄÀϸíÀ» ¼³Á¤ÇÑ´Ù. ÆÄÀϸíÀº ServerRoot¿¡ »ó´ë°æ·ÎÀÌ´Ù. ÀÌ + Áö½Ã¾î´Â mod_cookies¿Í ȣȯÀ» À§ÇØ Æ÷ÇÔÇßÀ»»Ó, + ½ÇÁ¦ »ç¿ëµÇÁö ¾Ê´Â´Ù.

+ +
+
top
+

CustomLog Áö½Ã¾î

+ + + + + + +
¼³¸í:·Î±×ÆÄÀÏ À̸§°ú Çü½ÄÀ» ÁöÁ¤ÇÑ´Ù
¹®¹ý:CustomLog file|pipe +format|nickname +[env=[!]environment-variable]
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_log_config
+

¼­¹ö°¡ ¿äûÀ» ·Î±×¿¡ ³²±æ¶§ CustomLog + Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. ·Î±× Çü½ÄÀ» ÁöÁ¤ÇÏ°í, ȯ°æº¯¼ö¸¦ »ç¿ëÇÏ¿© + ¿äûÀÇ Æ¯Â¡¿¡ µû¶ó ¼±ÅÃÀûÀ¸·Î ·Î±×¸¦ ³²±æ ¼öµµ ÀÖ´Ù.

+ +

·Î±×¸¦ ±â·ÏÇÒ Àå¼Ò¸¦ ÁöÁ¤Çϴ ù¹ø° ¾Æ±Ô¸ÕÆ®¿¡´Â ´ÙÀ½ + µÑÁß Çϳª¸¦ »ç¿ëÇÑ´Ù.

+ +
+
file
+
ServerRoot¿¡ + »ó´ëÀûÀÎ ÆÄÀϸí.
+ +
pipe
+
ÆÄÀÌÇÁ¹®ÀÚ "|"µÚ¿¡ ·Î±× Á¤º¸¸¦ Ç¥ÁØÀÔ·ÂÀ¸·Î + ¹ÞÀ» ÇÁ·Î±×·¥ °æ·Î¸¦ Àû´Â´Ù. + +

º¸¾È:

+

ÇÁ·Î±×·¥À» »ç¿ëÇÑ´Ù¸é ÇÁ·Î±×·¥Àº À¥¼­¹ö¸¦ ½ÃÀÛÇÑ »ç¿ëÀÚ + ±ÇÇÑÀ¸·Î ½ÇÇàµÈ´Ù. ¼­¹ö¸¦ root·Î ½ÃÀÛÇÑ´Ù¸é ÇÁ·Î±×·¥µµ + root·Î ½ÇÇàÇϹǷΠÇÁ·Î±×·¥ÀÌ ¾ÈÀüÇÑÁö È®ÀÎÇ϶ó.

+
+

ÁÖÀÇ

+

À¯´Ð½º°¡ ¾Æ´Ñ Ç÷¡Æû¿¡¼­ ÆÄÀÏ°æ·Î¸¦ ÀÔ·ÂÇÒ¶§ Ç÷¡ÆûÀÌ + ¹é½½·¡½¬¸¦ »ç¿ëÇÏ´õ¶óµµ ¹Ýµå½Ã ½½·¡½¬¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù. + ÀϹÝÀûÀ¸·Î ¼³Á¤ÆÄÀÏ¿¡¼­´Â Ç×»ó ½½·¡½¬¸¦ »ç¿ëÇÏ´Â °ÍÀÌ + ÁÁ´Ù.

+
+
+ +

µÎ¹ø° ¾Æ±Ô¸ÕÆ®´Â ·Î±×ÆÄÀÏ¿¡ ±â·ÏÇÒ ³»¿ëÀ» ÁöÁ¤ÇÑ´Ù. + Àü¿¡ LogFormatÀ¸·Î + Á¤ÀÇÇÑ nicknameÀ» »ç¿ëÇϰųª Á÷Á¢ ·Î±× Çü½Ä Àý¿¡¼­ ¼³¸íÇÑ format + ¹®ÀÚ¿­À» »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

¿¹¸¦ µé¾î, ´ÙÀ½ µÎ Áö½Ã¾î´Â ¶È°°Àº ÀÏÀ» ÇÑ´Ù.

+ +

+ # Çü½Ä º°ÄªÀ» »ç¿ëÇÑ CustomLog
+ LogFormat "%h %l %u %t \"%r\" %>s %b" common
+ CustomLog logs/access_log common
+
+ # Á÷Á¢ Çü½Ä ¹®ÀÚ¿­À» »ç¿ëÇÑ CustomLog
+ CustomLog logs/access_log "%h %l %u %t \"%r\" %>s %b" +

+ +

¼¼¹ø° ¾Æ±Ô¸ÕÆ®´Â ¾ø¾îµµ µÇ¸ç, ƯÁ¤ ¼­¹ö ȯ°æº¯¼ö À¯¹«¿¡ + µû¶ó ¿äûÀ» ·Î±×¿¡ ±â·ÏÇÒÁö ¿©ºÎ¸¦ °áÁ¤ÇÑ´Ù. ¿äû¿¡ ÁöÁ¤ÇÑ + ȯ°æº¯¼ö°¡ Á¤ÀǵÇÀÖ´Ù¸é (ȤÀº + 'env=!name'¸¦ »ç¿ëÇÑ °æ¿ì ¾ø´Ù¸é) + ¿äûÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù.

+ +

mod_setenvif³ª mod_rewrite + ¸ðµâÀ» »ç¿ëÇÏ¿© ¿äûº°·Î ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ + µé¾î, ¼­¹ö°¡ GIF ±×¸²¿¡ ´ëÇÑ ¸ðµç ¿äûÀ» ÁÖ¼­¹ö ·Î±×°¡ ¾Æ´Ñ + ´Ù¸¥ ·Î±×ÆÄÀÏ¿¡ ±â·ÏÇÏ·Á¸é,

+ +

+ SetEnvIf Request_URI \.gif$ gif-image
+ CustomLog gif-requests.log common env=gif-image
+ CustomLog nongif-requests.log common env=!gif-image +

+ +
+
top
+

LogFormat Áö½Ã¾î

+ + + + + + + +
¼³¸í:·Î±×ÆÄÀÏ¿¡ »ç¿ëÇÒ Çü½ÄÀ» ±â¼úÇÑ´Ù
¹®¹ý:LogFormat format|nickname +[nickname]
±âº»°ª:LogFormat "%h %l %u %t \"%r\" %>s %b"
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_log_config
+

ÀÌ Áö½Ã¾î´Â Á¢±Ù ·Î±×ÆÄÀÏÀÇ Çü½ÄÀ» ÁöÁ¤ÇÑ´Ù.

+ +

LogFormat Áö½Ã¾î´Â µÎ°¡Áö Çü½ÄÀ¸·Î + »ç¿ëÇÑ´Ù. ù¹ø° Çü½ÄÀº ¾Æ±Ô¸ÕÆ®¸¦ ÇÑ°³¸¸ »ç¿ëÇÏ¿© ´ÙÀ½ + TransferLog Áö½Ã¾îµéÀÌ »ç¿ëÇÒ ·Î±× + Çü½ÄÀ» ÁöÁ¤ÇÑ´Ù. ÀÌ ¾Æ±Ô¸ÕÆ®¿¡ À§ÀÇ ·Î±× + Çü½Ä ÁöÁ¤Çϱâ Àý¿¡¼­ ¼³¸íÇÑ formatÀ» Á÷Á¢ + »ç¿ëÇϰųª, ´ÙÀ½¿¡ ¼³¸íÇÒ LogFormat + Áö½Ã¾î·Î ¹Ì¸® Á¤ÀÇÇÑ (·Î±× Çü½ÄÀ» ÁöĪÇÏ´Â) nicknameÀ» + »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

LogFormat Áö½Ã¾îÀÇ µÎ¹ø° Çü½ÄÀº + format°ú nicknameÀ» ¿¬°áÇÑ´Ù. ±×·¯¸é + µÚ¿¡¼­ »ç¿ëÇÏ´Â LogFormatÀ̳ª CustomLog Áö½Ã¾î¿¡ ¹Ýº¹Çؼ­ + Çü½Ä ¹®ÀÚ¿­À» ¸ðµÎ ÀÔ·ÂÇÏ´Â ´ë½Å nicknameÀ» »ç¿ëÇÒ + ¼ö ÀÖ´Ù. º°ÄªÀ» Á¤ÀÇÇÏ´Â LogFormat + Áö½Ã¾î´Â ÀÌ ¿Ü¿¡´Â ¾Æ¹« ±â´ÉÀ» ÇÏÁö ¾Ê´Â´Ù. + Áï, º°Äª¸¸À» Á¤ÀÇÇϸç, ½ÇÁ¦·Î Çü½ÄÀ» Àû¿ëÇϰųª + Çü½ÄÀ» ±âº»°ªÀ¸·Î ¸¸µéÁö ¾Ê´Â´Ù. ±×·¯¹Ç·Î ´ÙÀ½¿¡ ³ª¿À´Â + TransferLog + Áö½Ã¾î¿¡ ¿µÇâÀ» ÁÖÁö ¾Ê´Â´Ù. ¶Ç, + LogFormatÀº º°ÄªÀ¸·Î ´Ù¸¥ º°ÄªÀ» + Á¤ÀÇÇÒ ¼ö ÀÖ´Ù. º°Äª À̸§¿¡´Â ÆÛ¼¾Æ® ±âÈ£(%)¸¦ + »ç¿ëÇÒ ¼ö ¾øÀ½À» ÁÖÀÇÇ϶ó.

+ +

¿¹Á¦

+ LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common +

+ +
+
top
+

TransferLog Áö½Ã¾î

+ + + + + + +
¼³¸í:·Î±×ÆÄÀÏ À§Ä¡¸¦ ¼³Á¤ÇÑ´Ù
¹®¹ý:TransferLog file|pipe
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_log_config
+

ÀÌ Áö½Ã¾î´Â CustomLog Áö½Ã¾î¿Í ¾Æ±Ô¸ÕÆ®¿Í + ±â´ÉÀÌ ºñ½ÁÇÏÁö¸¸, ·Î±× Çü½ÄÀ» Á÷Á¢ ÁöÁ¤Çϰųª ¿äûÀ» Á¶°Ç¿¡ + µû¶ó ·Î±×¿¡ ³²±æ ¼ö ¾ø´Ù. ´ë½Å °¡Àå ÃÖ±Ù »ç¿ëÇÑ (º°ÄªÀ» + Á¤ÀÇÇÏÁö ¾ÊÀº) LogFormat Áö½Ã¾î°¡ ÁöÁ¤ÇÑ + ·Î±× Çü½ÄÀ» »ç¿ëÇÑ´Ù. ¹Ì¸® Çü½ÄÀ» ÁöÁ¤ÇÏÁö ¾Ê¾Ò´Ù¸é Common + Log FormatÀ» »ç¿ëÇÑ´Ù.

+ +

¿¹Á¦

+ LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\""
+ TransferLog logs/access_log +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_log_forensic.html b/docs/manual/mod/mod_log_forensic.html new file mode 100644 index 00000000..ede26709 --- /dev/null +++ b/docs/manual/mod/mod_log_forensic.html @@ -0,0 +1,7 @@ +URI: mod_log_forensic.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_log_forensic.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_log_forensic.html.en b/docs/manual/mod/mod_log_forensic.html.en new file mode 100644 index 00000000..4dc3d26c --- /dev/null +++ b/docs/manual/mod/mod_log_forensic.html.en @@ -0,0 +1,162 @@ + + + +mod_log_forensic - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_log_forensic

+
+

Available Languages:  en  | + ja 

+
+ + + + +
Description:Forensic Logging of the requests made to the server
Status:Extension
Module Identifier:log_forensic_module
Source File:mod_log_forensic.c
Compatibility:mod_unique_id is no longer required since +version 2.1
+

Summary

+ +

This module provides for forensic logging of client + requests. Logging is done before and after processing a request, so the + forensic log contains two log lines for each request. + The forensic logger is very strict, which means:

+ +
    +
  • The format is fixed. You cannot modify the logging format at + runtime.
    • +
  • If it cannot write its data, the child process + exits immediately and may dump core (depending on your + CoreDumpDirectory + configuration).
    • +
+ +

The check_forensic script, which can be found in the + distribution's support directory, may be helpful in evaluating the + forensic log output.

+
+ +
top
+
+

Forensic Log Format

+

Each request is logged two times. The first time is before it's + processed further (that is, after receiving the headers). The second log + entry is written after the request processing at the same time + where normal logging occurs.

+ +

In order to identify each request, a unique request ID is assigned. + This forensic ID can be cross logged in the normal transfer log using the + %{forensic-id}n format string. If you're using + mod_unique_id, its generated ID will be used.

+ +

The first line logs the forensic ID, the request line and all received + headers, separated by pipe characters (|). A sample line + looks like the following (all on one line):

+ +

+ +yQtJf8CoAB4AAFNXBIEAAAAA|GET /manual/de/images/down.gif + HTTP/1.1|Host:localhost%3a8080|User-Agent:Mozilla/5.0 (X11; + U; Linux i686; en-US; rv%3a1.6) Gecko/20040216 + Firefox/0.8|Accept:image/png, etc... +

+ +

The plus character at the beginning indicates that this is the first log + line of this request. The second line just contains a minus character and + the ID again:

+ +

+ -yQtJf8CoAB4AAFNXBIEAAAAA +

+ +

The check_forensic script takes as its argument the name + of the logfile. It looks for those +/- ID pairs + and complains if a request was not completed.

+
top
+
+

Security Considerations

+

See the security tips + document for details on why your security could be compromised + if the directory where logfiles are stored is writable by + anyone other than the user that starts the server.

+
+
top
+

ForensicLog Directive

+ + + + + + +
Description:Sets filename of the forensic log
Syntax:ForensicLog filename|pipe
Context:server config, virtual host
Status:Extension
Module:mod_log_forensic
+

The ForensicLog directive is used to + log requests to the server for forensic analysis. Each log entry + is assigned a unique ID which can be associated with the request + using the normal CustomLog + directive. mod_log_forensic creates a token called + forensic-id, which can be added to the transfer log + using the %{forensic-id}n format string.

+ +

The argument, which specifies the location to which + the logs will be written, can take one of the following two + types of values:

+ +
+
filename
+
A filename, relative to the ServerRoot.
+ +
pipe
+
The pipe character "|", followed by the path + to a program to receive the log information on its standard + input. The program name can be specified relative to the ServerRoot directive. + +

Security:

+

If a program is used, then it will be run as the user who + started httpd. This will be root if the server was + started by root; be sure that the program is secure or switches to a + less privileged user.

+
+ +

Note

+

When entering a file path on non-Unix platforms, care should be taken + to make sure that only forward slashed are used even though the platform + may allow the use of back slashes. In general it is a good idea to always + use forward slashes throughout the configuration files.

+
+
+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_log_forensic.html.ja.euc-jp b/docs/manual/mod/mod_log_forensic.html.ja.euc-jp new file mode 100644 index 00000000..05ed916e --- /dev/null +++ b/docs/manual/mod/mod_log_forensic.html.ja.euc-jp @@ -0,0 +1,163 @@ + + + +mod_log_forensic - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_log_forensic

+
+

Available Languages:  en  | + ja 

+
+ + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤ËÁ÷¤é¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î forensic ¥í¥®¥ó¥°
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:log_forensic_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_log_forensic.c
¸ß´¹À­:mod_unique_id ¤Ï¥Ð¡¼¥¸¥ç¥ó 2.1 ¤«¤é¤Ïɬ¿Ü¤Ç¤Ï +¤Ê¤¯¤Ê¤Ã¤¿
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥¯¥é¥¤¥¢¥ó¥È¥ê¥¯¥¨¥¹¥È¤Î forensic ¥í¥®¥ó¥°¤ò + ¹Ô¤Ê¤¤¤Þ¤¹¡£¥í¥°¼ý½¸¤Ï¥ê¥¯¥¨¥¹¥È¤Î½èÍý¤ÎÁ°¤È¸å¤Ë¹Ô¤Ê¤ï¤ì¤Þ¤¹¤Î¤Ç¡¢ + forensic ¥í¥°¤Ï³Æ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤ÆÆó¹Ô¥í¥°¼ý½¸¤·¤Þ¤¹¡£ + Forensic ¥í¥¬¡¼¤ÏÈó¾ï¤Ë¸·Ì©¤Ç¤¹¡£¤³¤ì¤Ï°Ê²¼¤Î¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹:

+ +
    +
  • ¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï¸ÇÄê¤Ç¤¹¡£¼Â¹Ô»þ¤Ë¥í¥®¥ó¥°¥Õ¥©¡¼¥Þ¥Ã¥È¤òÊѹ¹¤¹¤ë¤³¤È¤Ï + ¤Ç¤­¤Þ¤»¤ó¡£
    • +
  • ¥Ç¡¼¥¿¤ò½ñ¤±¤Ê¤¤¾ì¹ç¤Ï»Ò¥×¥í¥»¥¹¤Ï¤½¤Î¾ì¤Ç½ªÎ»¤·¡¢¤µ¤é¤Ë¥³¥¢¤ò + ¥À¥ó¥×¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó (CoreDumpDirectory ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀßÄê¤Ë°Í¤ê¤Þ¤¹)¡£
    • +
+ +

Forensic ¥í¥°¤Î½ÐÎϤò¸¡ºº¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ + ÇÛÉÛʪ¤Î support ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë check_forensic + ¥¹¥¯¥ê¥×¥È¤¬Ìò¤ËΩ¤Ä¤Ç¤·¤ç¤¦¡£

+
+ +
top
+
+

Forensic ¥í¥°¥Õ¥©¡¼¥Þ¥Ã¥È

+

³Æ¥ê¥¯¥¨¥¹¥È¤Ï2²ó¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹¡£ºÇ½é¤Ï¥ê¥¯¥¨¥¹¥È¤¬½èÍý¤µ¤ì¤ë + Á° (¤Ä¤Þ¤ê¡¢¥Ø¥Ã¥À¤ò¼õ¤±¼è¤Ã¤¿¸å) ¤Ç¤¹¡£2ÅÙÌÜ¤Î¥í¥°¤Ï + ¥ê¥¯¥¨¥¹¥È¤¬½èÍý¤µ¤ì¤¿¸å¡¢Ä̾ï¤Î¥í¥°¼ý½¸¤ÈƱ¤¸¤È¤­¤Ë + ¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£

+ +

³Æ¥ê¥¯¥¨¥¹¥È¤ò¼±Ê̤¹¤ë¤¿¤á¤Ë¡¢¥ê¥¯¥¨¥¹¥È¤Ë¤Ï + °ì°Õ¤Ê¥ê¥¯¥¨¥¹¥È ID ¤¬³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£¤³¤Î forensic ID ¤Ï + ¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó %{forensic-id}n ¤ò»È¤¦¤³¤È¤Ç + Ä̾ï¤Î transfer ¥í¥°¤Ë¥í¥°¼ý½¸¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + mod_unique_id ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢¤½¤ì¤¬À¸À®¤¹¤ë + ID ¤¬»È¤ï¤ì¤Þ¤¹¡£

+ +

ºÇ½é¤Î¹Ô¤Ï forensic ID¡¢¥ê¥¯¥¨¥¹¥È¹Ô¤È¼õ¤±¼è¤Ã¤¿¤¹¤Ù¤Æ¤Î¥Ø¥Ã¥À¤ò + ¥Ñ¥¤¥×ʸ»ú (|) ¤ÇʬΥ¤·¤Æ¥í¥°¼ý½¸¤·¤Þ¤¹¡£ + Î㤨¤Ð°Ê²¼¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹ (¼ÂºÝ¤Ï¤¹¤Ù¤ÆƱ¤¸¹Ô¤Ë¤Ê¤ê¤Þ¤¹):

+ +

+ +yQtJf8CoAB4AAFNXBIEAAAAA|GET /manual/de/images/down.gif + HTTP/1.1|Host:localhost%3a8080|User-Agent:Mozilla/5.0 (X11; + U; Linux i686; en-US; rv%3a1.6) Gecko/20040216 + Firefox/0.8|Accept:image/png, etc... +

+ +

ºÇ½é¤Î¥×¥é¥¹Ê¸»ú¤¬¤³¤Î¥í¥°¤ÏºÇ½é¤Î¥í¥°¤Ç¤¢¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ + ÆóÈÖÌܤιԤϥޥ¤¥Ê¥¹Ê¸»ú¤È ID ¤Î¤ß¤Ç¤¹:

+ +

+ -yQtJf8CoAB4AAFNXBIEAAAAA +

+ +

check_forensic ¥¹¥¯¥ê¥×¥È¤Ï°ú¿ô¤È¤·¤Æ¥í¥°¥Õ¥¡¥¤¥ë¤Î̾Á°¤ò + ¼è¤ê¤Þ¤¹¡£+/- ¤Î ID ¤ÎÁȤòÄ´¤Ù¡¢´°Î»¤·¤Æ¤¤¤Ê¤¤ + ¥ê¥¯¥¨¥¹¥È¤¬¤¢¤ë¾ì¹ç¤Ï·Ù¹ð¤òȯ¤·¤Þ¤¹¡£

+
top
+
+

¥»¥­¥å¥ê¥Æ¥£¤ÎÌäÂê

+

¥í¥°¥Õ¥¡¥¤¥ë¤¬Êݸ¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¤¬¥µ¡¼¥Ð¤òµ¯Æ°¤·¤¿¥æ¡¼¥¶ + °Ê³°¤Ç½ñ¤­¹þ¤ß²Äǽ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤È¤­¤Ë¥»¥­¥å¥ê¥Æ¥£¤¬Çˤé¤ì¤ë²ÄǽÀ­¤¬ + ¤¢¤ë¤³¤È¤Ë¤Ä¤¤¤Æ¤Î¾ÜºÙ¤Ï¥»¥­¥å¥ê¥Æ¥£¤Î¤³¤Ä¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+
top
+

ForensicLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:Forensic ¥í¥°¤Î¥Õ¥¡¥¤¥ë̾¤òÀßÄꤹ¤ë
¹½Ê¸:ForensicLog filename|pipe
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_log_forensic
+

ForensicLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï forensic ²òÀϤΤ¿¤á¤Î + ¥µ¡¼¥Ð¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò¥í¥°¼ý½¸¤Ë»È¤¤¤Þ¤¹¡£ + ³Æ¥í¥°¥¨¥ó¥È¥ê¤Ë¤Ï¡¢ÉáÄ̤ΠCustomLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¥ê¥¯¥¨¥¹¥È¤È´ØÏ¢ÉÕ¤±¤ë¤³¤È¤Î + ¤Ç¤­¤ë + °ì°Õ¤Ê ID ¤¬³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£mod_log_forensic ¤Ï + forensic-id ¤È¤¤¤¦¥È¡¼¥¯¥ó¤òºîÀ®¤·¡¢¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó + %{forensic-id}n ¤ò»È¤¦¤³¤È¤Ç¤½¤Î¥È¡¼¥¯¥ó¤ò transfer ¥í¥°¤Ë + Äɲ乤뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

°ú¿ô¤Ï¥í¥°¤¬½ñ¤­½Ð¤µ¤ì¤ë°ÌÃÖ¤ò»ØÄꤷ¡¢°Ê²¼¤Î 2¼ïÎà¤ÎÃͤΤɤÁ¤é¤«¤ò + ¼è¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +
+
filename
+
ServerRoot ¤«¤é¤Î + ÁêÂÐ¥Õ¥¡¥¤¥ë̾
+ +
pipe
+
¥Ñ¥¤¥×ʸ»ú "|" ¤È¡¢¤½¤Î¸å¤Ë¥í¥°¾ðÊó¤òɸ½àÆþÎϤ«¤é + ¼õ¤±¼è¤ë¥×¥í¥°¥é¥à¡£¥×¥í¥°¥é¥à̾¤Ï ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ¤â + »ØÄê¤Ç¤­¤Þ¤¹¡£ + +

¥»¥­¥å¥ê¥Æ¥£:

+

¥×¥í¥°¥é¥à¤ò»È¤¦¾ì¹ç¡¢¤½¤Î¥×¥í¥°¥é¥à¤Ï httpd ¤òµ¯Æ°¤·¤¿¥æ¡¼¥¶¤Ç + ¼Â¹Ô¤µ¤ì¤Þ¤¹¡£¤Ä¤Þ¤ê¡¢¥µ¡¼¥Ð¤¬ root ¤Ç¼Â¹Ô¤µ¤ì¤¿¾ì¹ç¤Ï root ¤Ç + ¼Â¹Ô¤µ¤ì¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£¥×¥í¥°¥é¥à¤¬°ÂÁ´¤Ç¤¢¤ë¤«¡¢¤è¤ê¸¢¸Â¤Î¾¯¤Ê¤¤ + ¥æ¡¼¥¶¤ËÀÚ¤êÂؤ¨¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤ò³Î¤«¤á¤Æ¤¯¤À¤µ¤¤¡£

+
+ +

Ãí

+

Unix °Ê³°¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¥Õ¥¡¥¤¥ë̾¤òÆþÎϤ¹¤ë¤È¤­¤Ï¡¢ + ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤¬¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¤Î»ÈÍѤòµö²Ä¤·¤Æ¤¤¤ë¾ì¹ç¤Ç¤â¡¢ + ¥¹¥é¥Ã¥·¥å¤Î¤ß¤¬»È¤ï¤ì¤ë¤è¤¦¤Ëµ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£ + ÉáÄ̤ÏÀßÄê¥Õ¥¡¥¤¥ë¤¹¤Ù¤Æ¤Ë¤ª¤¤¤Æ¡¢¥¹¥é¥Ã¥·¥å¤ÎÊý¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë + ¤·¤Æ¤¯¤À¤µ¤¤¡£

+
+
+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_logio.html b/docs/manual/mod/mod_logio.html new file mode 100644 index 00000000..225d49bf --- /dev/null +++ b/docs/manual/mod/mod_logio.html @@ -0,0 +1,11 @@ +URI: mod_logio.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_logio.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_logio.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_logio.html.en b/docs/manual/mod/mod_logio.html.en new file mode 100644 index 00000000..a74fa4af --- /dev/null +++ b/docs/manual/mod/mod_logio.html.en @@ -0,0 +1,91 @@ + + + +mod_logio - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_logio

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Logging of input and output bytes per request
Status:Extension
Module Identifier:logio_module
Source File:mod_logio.c
+

Summary

+ + +

This module provides the logging of input and output number of + bytes received/sent per request. The numbers reflect the actual bytes + as received on the network, which then takes into account the + headers and bodies of requests and responses. The counting is done + before SSL/TLS on input and after SSL/TLS on output, so the numbers + will correctly reflect any changes made by encryption.

+ +

This module requires mod_log_config.

+ +
+

Directives

+

This module provides no + directives.

+

Topics

+

See also

+
+
top
+
+

Custom Log Formats

+ + +

This modules adds two new logging directives. The characteristics of the + request itself are logged by placing "%" directives in + the format string, which are replaced in the log file by the values as + follows:

+ + + + + + + +
Format StringDescription
%...IBytes received, including request and headers, cannot be + zero.
%...OBytes sent, including headers, cannot be zero.
+ +

Usually, the functionality is used like this:

+ +
+
Combined I/O log format:
+
"%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\" %I %O"
+
+
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_logio.html.ja.euc-jp b/docs/manual/mod/mod_logio.html.ja.euc-jp new file mode 100644 index 00000000..171d21ef --- /dev/null +++ b/docs/manual/mod/mod_logio.html.ja.euc-jp @@ -0,0 +1,91 @@ + + + +mod_logio - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_logio

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥ÈËè¤ËÆþÎϥХ¤¥È¿ô¤È½ÐÎϥХ¤¥È¿ô¤È¤ò¥í¥®¥ó¥°
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:logio_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_logio.c
+

³µÍ×

+ + +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥ê¥¯¥¨¥¹¥È¤´¤È¤Ë¼õ¤±¼è¤Ã¤¿¥Ð¥¤¥È¿ô¤È + Á÷¿®¤·¤¿¥Ð¥¤¥È¿ô¤Î¥í¥®¥ó¥°¤ò¹Ô¤Ê¤¦µ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£ + µ­Ï¿¤µ¤ì¤ë¿ô»ú¤Ï¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¤È¥ì¥¹¥Ý¥ó¥¹¤ÎËÜÂΤò + È¿±Ç¤·¤¿¡¢¼ÂºÝ¤Ë¥Í¥Ã¥È¥ï¡¼¥¯¤Ç¼õ¤±¼è¤Ã¤¿¥Ð¥¤¥ÈÃͤǤ¹¡£ + ÆþÎÏ¤Ç¤Ï SSL/TLS ¤ÎÁ°¤Ë¡¢½ÐÎÏ¤Ç¤Ï SSL/TLS ¤Î¸å¤Ë¿ô¤¨¤ë¤Î¤Ç¡¢ + ¿ô»ú¤Ï°Å¹æ¤Ë¤è¤ëÊѲ½¤âÀµ¤·¤¯È¿±Ç¤·¤¿¤â¤Î¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Î»ÈÍÑ¤Ë¤Ï mod_log_config ¥â¥¸¥å¡¼¥ë¤¬ + ɬÍפǤ¹¡£

+ +
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+

¥È¥Ô¥Ã¥¯

+

»²¾È

+
+
top
+
+

¥«¥¹¥¿¥à¥í¥°½ñ¼°

+ + +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¿·¤·¤¤¥í¥®¥ó¥°Íѥǥ£¥ì¥¯¥Æ¥£¥Ö¤ò²Ã¤¨¤Þ¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¼«¿È¤ÎÆÃħ¤Ï¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤Ë¡¢°Ê²¼¤ÎÍͤËÃÖ´¹¤µ¤ì¤ë + "%" ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + Æþ¤ì¤ë¤³¤È¤Ç¥í¥°¼ý½¸¤µ¤ì¤Þ¤¹:

+ + + + + + + +
¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎóÀâÌÀ
%...I¥ê¥¯¥¨¥¹¥È¤È¥Ø¥Ã¥À¤ò´Þ¤à¡¢¼õ¤±¼è¤Ã¤¿¥Ð¥¤¥È¿ô¡£ + 0 ¤Ë¤Ï¤Ê¤é¤Ê¤¤¡£
%...O¥Ø¥Ã¥À¤ò´Þ¤à¡¢Á÷¿®¤·¤¿¥Ð¥¤¥È¿ô¡£0 ¤Ë¤Ï¤Ê¤é¤Ê¤¤¡£
+ +

Ä̾¤³¤Îµ¡Ç½¤Ï°Ê²¼¤ÎÍͤ˻ÈÍѤµ¤ì¤Þ¤¹:

+ +
+
·ë¹ç I/O ¥í¥°½ñ¼°:
+
"%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\" %I %O"
+
+
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_logio.html.ko.euc-kr b/docs/manual/mod/mod_logio.html.ko.euc-kr new file mode 100644 index 00000000..71000575 --- /dev/null +++ b/docs/manual/mod/mod_logio.html.ko.euc-kr @@ -0,0 +1,92 @@ + + + +mod_logio - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_logio

+
+

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

+
+ + + +
¼³¸í:¿äû´ç ÀÔÃâ·Â ¹ÙÀÌÆ®¼ö¸¦ ±â·Ï
»óÅÂ:Extension
¸ðµâ¸í:logio_module
¼Ò½ºÆÄÀÏ:mod_logio.c
+

¿ä¾à

+ + +

ÀÌ ¸ðµâÀº ¿äû´ç ÀÔÃâ·Â ¹ÙÀÌÆ®¼ö¸¦ ±â·ÏÇÑ´Ù. ¼ýÀÚ´Â + ³×Æ®¿÷¿¡¼­ ½ÇÁ¦·Î ÁÖ°í¹ÞÀº ¹ÙÀÌÆ®¼ö¸¦ ³ªÅ¸³»¸ç, ¿äû°ú ÀÀ´äÀÇ + Çì´õ¿Í ³»¿ëÀ» Æ÷ÇÔÇÑ´Ù. °³¼ö´Â ÀÔ·ÂÀÇ °æ¿ì SSL/TLS ÀÌÀü¿¡, + Ãâ·ÂÀÇ °æ¿ì SSL/TLS ÀÌÈÄ¿¡ ¼¼±â¶§¹®¿¡ ¾ÏȣȭÀÇ °á°úµµ + ¿Ã¹Ù·Î ¹Ý¿µµÈ´Ù.

+ +

ÀÌ ¸ðµâÀ» »ç¿ëÇÏ·Á¸é mod_log_configÀÌ + ÇÊ¿äÇÏ´Ù.

+ +
+

Áö½Ã¾îµé

+

ÀÌ ¸ðµâ¿¡´Â Áö½Ã¾î°¡ ¾ø½À´Ï´Ù.

+

ÁÖÁ¦

+

Âü°í

+
+
top
+
+

»ç¿ëÀÚÁ¤ÀÇ ·Î±× Çü½Ä

+ + +

ÀÌ ¸ðµâÀº µÎ°¡Áö »õ·Î¿î ·Î±×Áö½Ã¾î¸¦ Ãß°¡ÇÑ´Ù. ¿äûÀÚüÀÇ + Ư¼ºÀº Çü½Ä¹®ÀÚ¿­¿¡ "%" Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ±â·ÏÇÑ´Ù. + Áö½Ã¾î´Â ·Î±×ÆÄÀÏ¿¡ ´ÙÀ½°ú °°Àº °ªÀ» ±â·ÏÇÑ´Ù:

+ + + + + + + +
Çü½Ä¹®ÀÚ¿­¼³¸í
%...I¿äû°ú Çì´õ¸¦ Æ÷ÇÔÇÏ¿© ¹ÞÀº ¹ÙÀÌÆ®¼ö. 0ÀÏ ¼ö ¾ø´Ù.
%...OÇì´õ¸¦ Æ÷ÇÔÇÏ¿© º¸³½ ¹ÙÀÌÆ®¼ö. 0ÀÏ ¼ö ¾ø´Ù.
+ +

º¸Åë ´ÙÀ½°ú °°ÀÌ »ç¿ëÇÑ´Ù:

+ +
+ +
°áÇÕµÈ ÀÔÃâ·Â ·Î±× Çü½Ä:
+ +
"%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" + \"%{User-agent}i\" %I %O"
+ +
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_mem_cache.html b/docs/manual/mod/mod_mem_cache.html new file mode 100644 index 00000000..65ba4978 --- /dev/null +++ b/docs/manual/mod/mod_mem_cache.html @@ -0,0 +1,11 @@ +URI: mod_mem_cache.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_mem_cache.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_mem_cache.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_mem_cache.html.en b/docs/manual/mod/mod_mem_cache.html.en new file mode 100644 index 00000000..9722d9ec --- /dev/null +++ b/docs/manual/mod/mod_mem_cache.html.en @@ -0,0 +1,236 @@ + + + +mod_mem_cache - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_mem_cache

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Content cache keyed to URIs
Status:Extension
Module Identifier:mem_cache_module
Source File:mod_mem_cache.c
+

Summary

+ +

This module requires the service of mod_cache. It acts as a support module for mod_cache and provides a memory based storage manager. + mod_mem_cache can be configured to operate in two + modes: caching open file descriptors or caching objects in heap storage. + mod_mem_cache is most useful when used to cache locally + generated content or to cache backend server content for mod_proxy configured for ProxyPass (aka reverse proxy).

+ +

Content is stored in and retrieved from the cache using URI based + keys. Content with access protection is not cached.

+
+ + +
top
+

MCacheMaxObjectCount Directive

+ + + + + + + +
Description:The maximum number of objects allowed to be placed in the +cache
Syntax:MCacheMaxObjectCount value
Default:MCacheMaxObjectCount 1009
Context:server config
Status:Extension
Module:mod_mem_cache
+

The MCacheMaxObjectCount directive sets the + maximum number of objects to be cached. The value is used to create the + open hash table. If a new object needs to be inserted in the cache and + the maximum number of objects has been reached, an object will be + removed to allow the new object to be cached. The object to be removed + is selected using the algorithm specified by MCacheRemovalAlgorithm.

+ +

Example

+ MCacheMaxObjectCount 13001 +

+ +
+
top
+

MCacheMaxObjectSize Directive

+ + + + + + + +
Description:The maximum size (in bytes) of a document allowed in the +cache
Syntax:MCacheMaxObjectSize bytes
Default:MCacheMaxObjectSize 10000
Context:server config
Status:Extension
Module:mod_mem_cache
+

The MCacheMaxObjectSize directive sets the + maximum allowable size, in bytes, of a document for it to be considered + cacheable.

+ +

Example

+ MCacheMaxObjectSize 6400000 +

+ +

Note

+

The value of MCacheMaxObjectSize must be + greater than the value specified by the MCacheMinObjectSize directive.

+
+ +
+
top
+

MCacheMaxStreamingBuffer Directive

+ + + + + + + +
Description:Maximum amount of a streamed response to buffer in memory +before declaring the response uncacheable
Syntax:MCacheMaxStreamingBuffer size_in_bytes
Default:MCacheMaxStreamingBuffer the smaller of 100000 or MCacheMaxObjectSize
Context:server config
Status:Extension
Module:mod_mem_cache
+

The MCacheMaxStreamingBuffer directive + specifies the maximum number of bytes of a streamed response to + buffer before deciding that the response is too big to cache. + A streamed response is one in which the entire content is not + immediately available and in which the Content-Length + may not be known. Sources of streaming responses include proxied + responses and the output of CGI scripts. By default, a streamed + response will not be cached unless it has a + Content-Length header. The reason for this is to + avoid using a large amount of memory to buffer a partial response + that might end up being too large to fit in the cache. + The MCacheMaxStreamingBuffer directive allows + buffering of streamed responses that don't contain a + Content-Length up to the specified maximum amount of + space. If the maximum buffer space is reached, the buffered + content is discarded and the attempt to cache is abandoned.

+ +

Note:

+

Using a nonzero value for MCacheMaxStreamingBuffer + will not delay the transmission of the response to the client. + As soon as mod_mem_cache copies a block of streamed + content into a buffer, it sends the block on to the next output + filter for delivery to the client.

+
+ +

+ # Enable caching of streamed responses up to 64KB:
+ MCacheMaxStreamingBuffer 65536 +

+ +
+
top
+

MCacheMinObjectSize Directive

+ + + + + + + +
Description:The minimum size (in bytes) of a document to be allowed in the +cache
Syntax:MCacheMinObjectSize bytes
Default:MCacheMinObjectSize 0
Context:server config
Status:Extension
Module:mod_mem_cache
+

The MCacheMinObjectSize directive sets the + minimum size in bytes of a document for it to be considered + cacheable.

+ +

Example

+ MCacheMinObjectSize 10000 +

+ +
+
top
+

MCacheRemovalAlgorithm Directive

+ + + + + + + +
Description:The algorithm used to select documents for removal from the +cache
Syntax:MCacheRemovalAlgorithm LRU|GDSF
Default:MCacheRemovalAlgorithm GDSF
Context:server config
Status:Extension
Module:mod_mem_cache
+

The MCacheRemovalAlgorithm directive specifies + the algorithm used to select documents for removal from the cache. + Two choices are available:

+ +
+
LRU (Least Recently Used)
+
LRU removes the documents that have not been accessed + for the longest time.
+ +
GDSF (GreadyDual-Size)
+
GDSF assigns a priority to cached documents based + on the cost of a cache miss and the size of the document. Documents + with the lowest priority are removed first.
+
+ +

Example

+ MCacheRemovalAlgorithm GDSF
+ MCacheRemovalAlgorithm LRU +

+ +
+
top
+

MCacheSize Directive

+ + + + + + + +
Description:The maximum amount of memory used by the cache in +KBytes
Syntax:MCacheSize KBytes
Default:MCacheSize 100
Context:server config
Status:Extension
Module:mod_mem_cache
+

The MCacheSize directive sets the maximum + amount of memory to be used by the cache, in KBytes (1024-byte units). + If a new object needs to be inserted in the cache and the size of the + object is greater than the remaining memory, objects will be removed + until the new object can be cached. The object to be removed is + selected using the algorithm specified by MCacheRemovalAlgorithm.

+ +

Example

+ MCacheSize 700000 +

+ +

Note

+

The MCacheSize value must be greater than + the value specified by the MCacheMaxObjectSize directive.

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_mem_cache.html.ja.euc-jp b/docs/manual/mod/mod_mem_cache.html.ja.euc-jp new file mode 100644 index 00000000..77814b50 --- /dev/null +++ b/docs/manual/mod/mod_mem_cache.html.ja.euc-jp @@ -0,0 +1,234 @@ + + + +mod_mem_cache - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_mem_cache

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:URI ¤ò¥­¡¼¤Ë¤·¤¿¥³¥ó¥Æ¥ó¥Ä¤Î¥­¥ã¥Ã¥·¥å
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:mem_cache_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_mem_cache.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï mod_cache ¤òɬÍפȤ·¤Þ¤¹¡£ + ¤³¤ì¤Ï mod_cache ¤Î¥µ¥Ý¡¼¥È¥â¥¸¥å¡¼¥ë¤È¤·¤Æ + Æ°ºî¤·¡¢¥á¥â¥ê¤ò»ÈÍѤ·¤¿¥¹¥È¥ì¡¼¥¸´ÉÍýµ¡¹½¤òÄ󶡤·¤Þ¤¹¡£ + mod_mem_cache ¤ÏÆó¤Ä¤Î¥â¡¼¥É¤Î¤É¤Á¤é¤«¤ÇÆ°ºî¤¹¤ë¤è¤¦¤Ë + ÀßÄê¤Ç¤­¤Þ¤¹: ¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î¥­¥ã¥Ã¥·¥å¤«¥Ò¡¼¥×Ãæ¤Î¥ª¥Ö¥¸¥§¥¯¥È¤Î + ¥­¥ã¥Ã¥·¥å¤Ç¤¹¡£¥í¡¼¥«¥ë¤ÇÀ¸À®¤µ¤ì¤¿¥³¥ó¥Æ¥ó¥Ä¤ËÂФ·¤Æ¥­¥ã¥Ã¥·¥å¤¹¤ë¤È¤­¤ä¡¢ + mod_proxy ¤ò»È¤Ã¤Æ ProxyPass (¤Ä¤Þ¤ê¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¸þ¤±) ¤ËÀßÄꤷ¤¿¤È¤­¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤Î¥³¥ó¥Æ¥ó¥Ä¤ËÂФ·¤Æ + ¥­¥ã¥Ã¥·¥å¤ò¤¹¤ë¤È¤­¤Ë¡¢¤¿¤¤¤Ø¤ó¸ú²ÌŪ¤Ç¤¹¡£

+ +

¥³¥ó¥Æ¥ó¥Ä¤Î¥­¥ã¥Ã¥·¥å¤Ø¤ÎÊݸ¤È¼èÆÀ¤Ï URI ¤Ë´ð¤Å¤¤¤¿¥­¡¼¤¬»È¤ï¤ì¤Þ¤¹¡£ + ¥¢¥¯¥»¥¹Êݸî¤Î¤«¤±¤é¤ì¤Æ¤¤¤ë¥³¥ó¥Æ¥ó¥Ä¤Ï¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£

+
+ + +
top
+

MCacheMaxObjectCount ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤ËÊݴɤµ¤ì¤ë¥ª¥Ö¥¸¥§¥¯¥È¤ÎºÇÂç¿ô
¹½Ê¸:MCacheMaxObjectCount value
¥Ç¥Õ¥©¥ë¥È:MCacheMaxObjectCount 1009
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_mem_cache
+

MCacheMaxObjectCount ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥­¥ã¥Ã¥·¥å¤µ¤ì¤ë¥ª¥Ö¥¸¥§¥¯¥È¤ÎºÇÂç¿ô¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤³¤ÎÃͤϥϥå·¥å¥Æ¡¼¥Ö¥ë¤òºîÀ®¤¹¤ë¤È¤­¤Ë»È¤ï¤ì¤Þ¤¹¡£ + ¿·¤·¤¤¥ª¥Ö¥¸¥§¥¯¥È¤òÁÞÆþ¤¹¤ë¤È¤­¤Ë¡¢¥ª¥Ö¥¸¥§¥¯¥È¤ÎºÇÂç¿ô¤Ë + 㤷¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë¤È¤­¡¢¿·¤·¤¤¥ª¥Ö¥¸¥§¥¯¥È¤ò¥­¥ã¥Ã¥·¥å¤Ç¤­¤ë¤è¤¦¤Ë¡¢ + ¥ª¥Ö¥¸¥§¥¯¥È¤ò°ì¤Ä¾Ãµî¤·¤Þ¤¹¡£¥ª¥Ö¥¸¥§¥¯¥È¤Ï + MCacheRemovalAlgorithm + ¤Ç»ØÄꤵ¤ì¤¿¥¢¥ë¥´¥ê¥º¥à¤Ë½¾¤Ã¤Æºï½ü¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ MCacheMaxObjectCount 13001 +

+ +
+
top
+

MCacheMaxObjectSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤ËÊݴɤǤ­¤ë¥É¥­¥å¥á¥ó¥È¤ÎºÇÂ祵¥¤¥º (¥Ð¥¤¥È)
¹½Ê¸:MCacheMaxObjectSize bytes
¥Ç¥Õ¥©¥ë¥È:MCacheMaxObjectSize 10000
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_mem_cache
+

MCacheMaxObjectSize ¤Ï¥É¥­¥å¥á¥ó¥È¤ò + ¥­¥ã¥Ã¥·¥å¤¹¤ë¤«¤É¤¦¤«¤òȽÄꤹ¤ë¡¢ºÇÂç¤Î¥µ¥¤¥º¤ò¥Ð¥¤¥È¿ô¤ÇÀßÄꤷ¤Þ¤¹¡£

+ +

Îã

+ MCacheMaxObjectSize 6400000 +

+ +

Ãí

+

MCacheMaxObjectSize ¤ÎÃÍ¤Ï MCacheMinObjectSize + ¤Ç»ØÄꤷ¤¿Ãͤè¤ê¤âÂ礭¤¯¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
+ +
+
top
+

MCacheMaxStreamingBuffer ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¹¥È¥ê¡¼¥à¤µ¤ì¤Æ¤¤¤ë±þÅú¤ò¥­¥ã¥Ã¥·¥åÉÔǽ¤È·èÄꤹ¤ë¤Þ¤Ç¤Ë +¥á¥â¥ê¤Ë¥Ð¥Ã¥Õ¥¡¤¹¤ëºÇÂçÎÌ
¹½Ê¸:MCacheMaxStreamingBuffer size_in_bytes
¥Ç¥Õ¥©¥ë¥È:MCacheMaxStreamingBuffer of 100000 ¤« MCacheMaxObjectSize ¤Î¾¯¤¤Êý
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_mem_cache
+

MCacheMaxStreamingBuffer ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥µ¥¤¥º¤¬Â礭¤¹¤®¤Æ¥­¥ã¥Ã¥·¥å¤Ç¤­¤Ê¤¤¤ÈȽÃǤ¹¤ë¤Þ¤Ç¤Î¡¢ + ¥¹¥È¥ê¡¼¥à±þÅú¤Î¥Ð¥Ã¥Õ¥¡¤Î¤¿¤á¤ÎºÇÂç¥Ð¥¤¥È¿ô¤ò»ØÄꤷ¤Þ¤¹¡£ + ¥¹¥È¥ê¡¼¥à±þÅú¤È¤Ï¡¢¥³¥ó¥Æ¥ó¥Ä¤ÎÁ´ÂΤ¬¤¹¤°¤Ë¤ÏÆÀ¤é¤ì¤º¡¢ + Content-Length ¤¬¤ï¤«¤é¤Ê¤¤±þÅú¤ò»Ø¤·¤Þ¤¹¡£ + ¥¹¥È¥ê¡¼¥à±þÅú¤ò¹Ô¤Ê¤¦¤è¤¦¤Ê¤â¤Î¤Ë¤Ï¥×¥í¥­¥·¤µ¤ì¤¿±þÅú¤ä¡¢ + CGI ¥¹¥¯¥ê¥×¥È¤Î½ÐÎϤʤɤ¬¤¢¤ê¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥¹¥È¥ê¡¼¥à¤Î±þÅú¤Ï + Content-Length ¤¬¤Ê¤¤¸Â¤ê¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤»¤ó¡£ + ¤³¤Î¤è¤¦¤ÊÆ°ºî¤Ë¤Ê¤Ã¤Æ¤¤¤ëÍýͳ¤Ï¡¢·ë¶É¥­¥ã¥Ã¥·¥å¤Ë¼ý¤Þ¤ê¤­¤é¤Ê¤¤¤È + ȽÃǤ¹¤ë¤³¤È¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¦¤è¤¦¤Ê¡¢¥µ¥¤¥º¤ÎÂ礭¤Ê±þÅú¤Î¥Ð¥Ã¥Õ¥¡¥ê¥ó¥°¤Ë¡¢ + ÂçÎ̤Υá¥â¥ê¤¬¾ÃÈñ¤µ¤ì¤ë¤Î¤òÈò¤±¤ë¤¿¤á¤Ç¤¹¡£ + MCacheMaxStreamingBuffer ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤È¡¢ + Content-Length ¤ò´Þ¤Þ¤Ê¤¤±þÅú¤ËÂФ·¤Æ»ØÄꤵ¤ì¤¿ºÇÂçÎÌ¤Þ¤Ç + ¥Ð¥Ã¥Õ¥¡¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£¥Ð¥Ã¥Õ¥¡¤ò»È¤¤ÀÚ¤ë¤È¡¢¥Ð¥Ã¥Õ¥¡Ãæ¤Î + ¥³¥ó¥Æ¥ó¥Ä¤Ï¼Î¤Æ¤é¤ì¡¢¥­¥ã¥Ã¥·¥åÆ°ºî¤òÃæ»ß¤·¤Þ¤¹¡£

+ +

Ãí:

+

MCacheMaxStreamingBuffer ¤ËÈóÎí¤ÎÃͤò + »È¤Ã¤Æ¤â¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ø¤Î±þÅú¤ÎžÁ÷¤ËÆäËÃÙ±ä¤ÏȯÀ¸¤·¤Þ¤»¤ó¡£ + mod_mem_cache ¤Ï¥¹¥È¥ê¡¼¥à¥³¥ó¥Æ¥ó¥Ä¤ÎÃÇÊÒ¤ò + ¥Ð¥Ã¥Õ¥¡¤Ë¥³¥Ô¡¼¤·¤¿¸å¡¢Â¨ºÂ¤Ë¡¢¤½¤ÎÉôʬ¤ò¥¯¥é¥¤¥¢¥ó¥È¤Ø¤ÎÇÛÁ÷¤Î + ¼¡ÃʤνÐÎÏ¥Õ¥£¥ë¥¿¤ËÁ÷¤ê¤Þ¤¹¡£

+
+ +

+ # Enable caching of streamed responses up to 64KB:
+ MCacheMaxStreamingBuffer 65536 +

+ +
+
top
+

MCacheMinObjectSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤ËÊݴɤµ¤ì¤ë¥É¥­¥å¥á¥ó¥È¤ÎºÇ¾®¥µ¥¤¥º (¥Ð¥¤¥È)
¹½Ê¸:MCacheMinObjectSize bytes
¥Ç¥Õ¥©¥ë¥È:MCacheMinObjectSize 0
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_mem_cache
+

MCacheMinObjectSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤ò + ¥­¥ã¥Ã¥·¥å¤¹¤ë¤«¤É¤¦¤«¤òȽÄꤹ¤ë¡¢ºÇ¾®¤Î¥µ¥¤¥º¤ò¥Ð¥¤¥È¿ô¤ÇÀßÄꤷ¤Þ¤¹¡£

+ +

Îã

+ MCacheMinObjectSize 10000 +

+ +
+
top
+

MCacheRemovalAlgorithm ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤«¤éºï½ü¤¹¤ë¥É¥­¥å¥á¥ó¥È¤òÁª¤Ö¤¿¤á¤Î¥¢¥ë¥´¥ê¥º¥à
¹½Ê¸:MCacheRemovalAlgorithm LRU|GDSF
¥Ç¥Õ¥©¥ë¥È:MCacheRemovalAlgorithm GDSF
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_mem_cache
+

MCacheRemovalAlgorithm ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥­¥ã¥Ã¥·¥å¤«¤éºï½ü¤¹¤ë¥É¥­¥å¥á¥ó¥È¤òÁªÂò¤¹¤ë¤¿¤á¤Î¥¢¥ë¥´¥ê¥º¥à¤ò + »ØÄꤷ¤Þ¤¹¡£ÁªÂò»è¤ÏÆó¤Ä¤¢¤ê¤Þ¤¹:

+ +
+
LRU (Least Recently Used)
+
LRU °ìÈÖŤ¯¥¢¥¯¥»¥¹¤µ¤ì¤Æ¤¤¤Ê¤¤¥É¥­¥å¥á¥ó¥È¤òºï½ü¤·¤Þ¤¹¡£ +
+ +
GDSF (GreadyDual-Size)
+
GDSF ¤Ï¥­¥ã¥Ã¥·¥å¥ß¥¹¤Î¥³¥¹¥È¤È¥É¥­¥å¥á¥ó¥È¤Î¥µ¥¤¥º¤ò¤â¤È¤Ë¡¢ + ¥É¥­¥å¥á¥ó¥È¤Î¥­¥ã¥Ã¥·¥å¤ËÂФ·¤ÆÍ¥ÀèÅÙ¤ò¤Ä¤±¤Þ¤¹¡£ + Í¥ÀèÅ٤ΰìÈÖÄ㤤¥É¥­¥å¥á¥ó¥È¤¬ºÇ½é¤Ëºï½ü¤µ¤ì¤Þ¤¹¡£
+
+ +

Îã

+ MCacheRemovalAlgorithm GDSF
+ MCacheRemovalAlgorithm LRU +

+ +
+
top
+

MCacheSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥­¥ã¥Ã¥·¥å¤Ë»È¤ï¤ì¤ë¥á¥â¥ê¤ÎºÇÂçÎ̤ò¥Ð¥¤¥Èñ°Ì¤Ç»ØÄê
¹½Ê¸:MCacheSize KBytes
¥Ç¥Õ¥©¥ë¥È:MCacheSize 100
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_mem_cache
+

MCacheSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥­¥ã¥Ã¥·¥å¤Ë + »È¤ï¤ì¤ë¥á¥â¥ê¤ÎÂ礭¤µ¤ò¥­¥í¥Ð¥¤¥È (1024 ¥Ð¥¤¥Èñ°Ì) ¤ÇÀßÄꤷ¤Þ¤¹¡£ + ¿·¤·¤¤¥ª¥Ö¥¸¥§¥¯¥È¤ò¥­¥ã¥Ã¥·¥å¤ËÁÞÆþ¤¹¤ë¤³¤È¤Ë¤Ê¤ê¡¢¥ª¥Ö¥¸¥§¥¯¥È¤Î + ¥µ¥¤¥º¤¬»Ä¤ê¤Î¥á¥â¥ê¤è¤êÂ礭¤¤¾ì¹ç¤Ï¡¢¤½¤Î¿·¤·¤¤¥ª¥Ö¥¸¥§¥¯¥È¤ÎÁÞÆþ¤¬ + ²Äǽ¤Ë¤Ê¤ë¤Þ¤Ç¡¢¸Å¤¤¥ª¥Ö¥¸¥§¥¯¥È¤¬ºï½ü¤µ¤ì¤Æ¤¤¤­¤Þ¤¹¡£ + ¥ª¥Ö¥¸¥§¥¯¥È¤Ï MCacheRemovalAlgorithm + ¤Ç»ØÄꤷ¤¿¥¢¥ë¥´¥ê¥º¥à¤Ë½¾¤Ã¤Æºï½ü¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ MCacheSize 700000 +

+ +

Ãí

+

MCacheSize ¤ÎÃÍ¤Ï MCacheMaxObjectSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤷ¤¿Ãͤè¤ê + Â礭¤¯¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_mem_cache.html.ko.euc-kr b/docs/manual/mod/mod_mem_cache.html.ko.euc-kr new file mode 100644 index 00000000..5beb2726 --- /dev/null +++ b/docs/manual/mod/mod_mem_cache.html.ko.euc-kr @@ -0,0 +1,237 @@ + + + +mod_mem_cache - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_mem_cache

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:URI¸¦ Å°·Î »ç¿ëÇÏ¿© ³»¿ëÀ» ij½¬ÇÑ´Ù.
»óÅÂ:Experimental
¸ðµâ¸í:mem_cache_module
¼Ò½ºÆÄÀÏ:mod_mem_cache.c
+

¿ä¾à

+ +
+ ÀÌ ¸ðµâÀº ½ÇÇèÀûÀÎ »óÅÂÀÌ´Ù. ¹®¼­´Â ¾ÆÁ÷ ÀÛ¾÷ÁßÀÌ´Ù... +
+ +

ÀÌ ¸ðµâÀ» »ç¿ëÇÏ·Á¸é mod_cache°¡ + ÇÊ¿äÇÏ´Ù. ÀÌ ¸ðµâÀº mod_cache¸¦ + Áö¿øÇÏ¸ç ¸Þ¸ð¸®±â¹Ý ÀúÀå°ü¸®ÀÚ¸¦ Á¦°øÇÑ´Ù. + mod_mem_cache´Â ÆÄÀϱâ¼úÀÚ¸¦ ij½¬¿¡ ÀúÀåÇϰųª + °´Ã¼¸¦ Èü °ø°£¿¡ ij½¬ÇÏ´Â µÎ°¡Áö ¹æ½ÄÀ¸·Î µ¿ÀÛÇÑ´Ù. + mod_mem_cache´Â Á÷Á¢ ¼­¹ö°¡ »ý¼ºÇÑ ÆäÀÌÁö¸¦ + ij½¬Çϰųª ProxyPass·Î + ¼³Á¤ÇÑ (¿ªÇÁ·Ï½Ã(reverse proxy)) + mod_proxyÀÇ µÞ´Ü ¼­¹ö³»¿ëÀ» ij½¬ÇÒ¶§ ÁÖ·Î + »ç¿ëÇÑ´Ù.

+ +

³»¿ëÀº URI¸¦ Å°·Î »ç¿ëÇÏ¿© ij½¬¿¡ ÀúÀåÇÏ°í °¡Á®¿Â´Ù. + Á¢±ÙÀ» Á¦¾îÇÏ´Â ³»¿ëÀº ij½¬¿¡ ÀúÀåÇÏÁö ¾Ê´Â´Ù.

+
+ + +
top
+

MCacheMaxObjectCount Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬¿¡ ÀúÀåÇÒ ¼ö ÀÖ´Â ÃÖ´ë °´Ã¼°³¼ö
¹®¹ý:MCacheMaxObjectCount value
±âº»°ª:MCacheMaxObjectCount 1009
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_mem_cache
+

MCacheMaxObjectCount Áö½Ã¾î´Â + ij½¬ÇÒ ¼ö ÀÖ´Â ÃÖ´ë °´Ã¼°³¼ö¸¦ ¼³Á¤ÇÑ´Ù. ÀÌ °ªÀº Çؽ¬Å×À̺íÀ» + ¸¸µé¶§ »ç¿ëÇÑ´Ù. »õ·Î¿î °´Ã¼¸¦ ij½¬¿¡ Ãß°¡ÇØ¾ß Çϴµ¥ ÃÖ´ë + °´Ã¼°³¼ö¿¡ µµ´ÞÇÏ¿´´Ù¸é, »õ·Î¿î °´Ã¼¸¦ ij½¬ÇÒ ¼ö ÀÖµµ·Ï + ´Ù¸¥ °´Ã¼¸¦ Á¦°ÅÇÑ´Ù. MCacheRemovalAlgorithmÀ¸·Î + ÁöÁ¤ÇÑ ¾Ë°í¸®ÁòÀ» »ç¿ëÇÏ¿© Á¦°ÅÇÒ °´Ã¼¸¦ ¼±ÅÃÇÑ´Ù.

+ +

¿¹Á¦

+ MCacheMaxObjectCount 13001 +

+ +
+
top
+

MCacheMaxObjectSize Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬¿¡ ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ´ë Å©±â (¹ÙÀÌÆ® ´ÜÀ§)
¹®¹ý:MCacheMaxObjectSize bytes
±âº»°ª:MCacheMaxObjectSize 10000
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_mem_cache
+

MCacheMaxObjectSize Áö½Ã¾î´Â ij½¬¿¡ + ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ´ë Å©±â¸¦ ¹ÙÀÌÆ® ´ÜÀ§·Î ÁöÁ¤ÇÑ´Ù.

+ +

¿¹Á¦

+ MCacheMaxObjectSize 6400000 +

+ +

Note

+

MCacheMaxObjectSize °ªÀº MCacheMinObjectSize + Áö½Ã¾î·Î ÁöÁ¤ÇÑ °ªº¸´Ù Ä¿¾ß ÇÑ´Ù.

+
+ +
+
top
+

MCacheMaxStreamingBuffer Áö½Ã¾î

+ + + + + + + +
¼³¸í:ÀÀ´äÀ» ij½¬¾ÈÇÑ´Ù°í °áÁ¤Çϱâ Àü±îÁö ¸Þ¸ð¸® ¹öÆÛ¿¡ +ÀúÀåÇÒ ½ºÆ®¸² ÀÀ´äÀÇ ÃÖ´ë Å©±â
¹®¹ý:MCacheMaxStreamingBuffer size_in_bytes
±âº»°ª:MCacheMaxStreamingBuffer 100000°ú MCacheMaxObjectSize +Áß¿¡ ÀÛÀº °ª
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_mem_cache
+

MCacheMaxStreamingBuffer Áö½Ã¾î´Â + ÀÀ´äÀÌ ³Ê¹« Ä¿¼­ ij½¬ÇÒ ¼ö ¾øÀ»¶§±îÁö ¹öÆÛ¿¡ ÀúÀåÇÒ ½ºÆ®¸² + ÀÀ´äÀÇ ÃÖ´ë ¹ÙÀÌÆ®¼ö¸¦ ¼³Á¤ÇÑ´Ù. ½ºÆ®¸² ÀÀ´ä(streamed response)Àº + Àüü ³»¿ëÀ» Áï½Ã ¾Ë ¼ö ¾ø°í Content-Lengthµµ + ¸ð¸£´Â ÀÀ´äÀÌ´Ù. ÇÁ·Ï½ÃµÈ ÀÀ´äÀ̳ª CGI ½ºÅ©¸³Æ®ÀÇ Ãâ·ÂÀÌ + ½ºÆ®¸² ÀÀ´ä¿¡ ¼ÓÇÑ´Ù. ±âº»ÀûÀ¸·Î Content-Length + Çì´õ°¡ ¾ø´Ù¸é ½ºÆ®¸² ÀÀ´äÀ» ij½¬¿¡ ÀúÀåÇÏÁö ¾Ê´Â´Ù. + ÀÌÀ¯´Â ij½¬¿¡ ÀúÀåÇϱ⿡ ³Ê¹« Å« ÀÀ´äÀÇ ÀϺθ¦ ¹öÆÛ¿¡ + ÀúÀåÇϱâÀ§ÇØ ¸¹Àº ¸Þ¸ð¸®¸¦ ³¶ºñÇÏÁö ¾Ê±âÀ§Çؼ­ÀÌ´Ù. + MCacheMaxStreamingBuffer Áö½Ã¾î¸¦ + »ç¿ëÇϸé Content-Length°¡ ¾ø´Â ½ºÆ®¸² ÀÀ´äÀ» + ÁöÁ¤ÇÑ Å©±â±îÁö¸¸ ¹öÆÛ¿¡ ÀúÀåÇÑ´Ù. ÃÖ´ë Å©±â¸¦ ³Ñ¾î¼­¸é + ¹öÆÛ ³»¿ëÀ» ¹ö¸®°í ij½¬ÇÏÁö ¾Ê´Â´Ù.

+ +

ÁÖÀÇ:

+

MCacheMaxStreamingBuffer¿¡ 0ÀÌ + ¾Æ´Ñ °ªÀ» ¼³Á¤ÇÏ¿©µµ Ŭ¶óÀ̾ðÆ®·Î ÀÀ´äÀ» ´Ê°Ô º¸³»Áö ¾Ê´Â´Ù. + mod_mem_cache´Â ½ºÆ®¸² ÀÀ´äÀÇ ÀϺθ¦ + ¹öÆÛ¿¡ º¹»çÇÏÀÚ¸¶ÀÚ Å¬¶óÀ̾ðÆ®·Î º¸³»±âÀ§ÇØ ´ÙÀ½ Ãâ·ÂÇÊÅÍ·Î + º¸³½´Ù.

+
+ +

+ # ½ºÆ®¸² ÀÀ´äÀ» 64KB±îÁö ij½¬ÇÑ´Ù:
+ MCacheMaxStreamingBuffer 65536 +

+ +
+
top
+

MCacheMinObjectSize Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬¿¡ ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ¼Ò Å©±â (¹ÙÀÌÆ® ´ÜÀ§)
¹®¹ý:MCacheMinObjectSize bytes
±âº»°ª:MCacheMinObjectSize 0
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_mem_cache
+

MCacheMinObjectSize Áö½Ã¾î´Â ij½¬¿¡ + ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ¼Ò Å©±â¸¦ ¹ÙÀÌÆ® ´ÜÀ§·Î ÁöÁ¤ÇÑ´Ù.

+ +

¿¹Á¦

+ MCacheMinObjectSize 10000 +

+ +
+
top
+

MCacheRemovalAlgorithm Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬¿¡¼­ Á¦°ÅÇÒ ¹®¼­¸¦ ã´Â ¾Ë°í¸®Áò
¹®¹ý:MCacheRemovalAlgorithm LRU|GDSF
±âº»°ª:MCacheRemovalAlgorithm GDSF
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_mem_cache
+

MCacheRemovalAlgorithm Áö½Ã¾î´Â + ij½¬¿¡¼­ Á¦°ÅÇÒ ¹®¼­¸¦ ã´Â ¾Ë°í¸®ÁòÀ» ÁöÁ¤ÇÑ´Ù.

+ +
+
LRU (Least Recently Used)
+
LRU´Â °¡Àå ¿À·¡µ¿¾È Á¢±ÙÇÏÁö ¾ÊÀº ¹®¼­¸¦ + ¸ÕÀú Á¦°ÅÇÑ´Ù.
+ +
GDSF (GreadyDual-Size)
+
GDSF´Â ij½¬ ½ÇÆÐ(cache miss) ºñ¿ë°ú ¹®¼­ÀÇ + Å©±â¸¦ °¡Áö°í ij½¬ÇÑ ¹®¼­¿¡ ¿ì¼±¼øÀ§¸¦ ºÎ¿©ÇÑ´Ù. °¡Àå + ¿ì¼±¼øÀ§°¡ ³·Àº ¹®¼­¸¦ ¸ÕÀú Á¦°ÅÇÑ´Ù.
+
+ +

¿¹Á¦

+ MCacheRemovalAlgorithm GDSF
+ MCacheRemovalAlgorithm LRU +

+ +
+
top
+

MCacheSize Áö½Ã¾î

+ + + + + + + +
¼³¸í:ij½¬¿¡ »ç¿ëÇÒ ÃÖ´ë ¸Þ¸ð¸®·® (KByte ´ÜÀ§)
¹®¹ý:MCacheSize KBytes
±âº»°ª:MCacheSize 100
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Experimental
¸ðµâ:mod_mem_cache
+

MCacheSize Áö½Ã¾î´Â ij½¬¿¡ »ç¿ëÇÒ + ÃÖ´ë ¸Þ¸ð¸®·®À» KByte ´ÜÀ§·Î (1024 ¹ÙÀÌÆ® ´ÜÀ§) ¼³Á¤ÇÑ´Ù. + »õ·Î¿î °´Ã¼À» ij½¬¿¡ Ãß°¡ÇØ¾ß Çϴµ¥ °´Ã¼ÀÇ Å©±â°¡ ³²Àº + ¸Þ¸ð¸®º¸´Ù Å©´Ù¸é »õ·Î¿î °´Ã¼À» ij½¬ÇÒ ¼ö ÀÖÀ»¶§±îÁö ´Ù¸¥ + °´Ã¼¸¦ Á¦°ÅÇÑ´Ù. MCacheRemovalAlgorithmÀ¸·Î + ÁöÁ¤ÇÑ ¾Ë°í¸®ÁòÀ» »ç¿ëÇÏ¿© Á¦°ÅÇÒ °´Ã¼¸¦ ¼±ÅÃÇÑ´Ù.

+ +

¿¹Á¦

+ MCacheSize 700000 +

+ +

ÁÖÀÇ

+

MCacheSize °ªÀº MCacheMaxObjectSize + Áö½Ã¾î·Î ÁöÁ¤ÇÑ °ªº¸´Ù Ä¿¾ß ÇÑ´Ù.

+
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_mime.html b/docs/manual/mod/mod_mime.html new file mode 100644 index 00000000..09e9184e --- /dev/null +++ b/docs/manual/mod/mod_mime.html @@ -0,0 +1,7 @@ +URI: mod_mime.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_mime.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_mime.html.en b/docs/manual/mod/mod_mime.html.en new file mode 100644 index 00000000..053ac453 --- /dev/null +++ b/docs/manual/mod/mod_mime.html.en @@ -0,0 +1,943 @@ + + + +mod_mime - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_mime

+
+

Available Languages:  en  | + ja 

+
+ + + +
Description:Associates the requested filename's extensions + with the file's behavior (handlers and filters) + and content (mime-type, language, character set and + encoding)
Status:Base
Module Identifier:mime_module
Source File:mod_mime.c
+

Summary

+ +

This module is used to associate various bits of "meta + information" with files by their filename extensions. This + information relates the filename of the document to it's + mime-type, language, character set and encoding. This + information is sent to the browser, and participates in content + negotiation, so the user's preferences are respected when + choosing one of several possible files to serve. See + mod_negotiation for more information + about content negotiation.

+ +

The directives AddCharset, AddEncoding, AddLanguage and AddType are all used to map file + extensions onto the meta-information for that file. Respectively + they set the character set, content-encoding, content-language, + and MIME-type (content-type) of documents. The directive TypesConfig is used to specify a + file which also maps extensions onto MIME types.

+ +

In addition, mod_mime may define the handler and filters that originate and process + content. The directives AddHandler, AddOutputFilter, and AddInputFilter control the modules + or scripts that serve the document. The MultiviewsMatch directive allows + mod_negotiation to consider these file extensions + to be included when testing Multiviews matches.

+ +

While mod_mime associates meta-information + with filename extensions, the core server + provides directives that are used to associate all the files in a + given container (e.g., <Location>, <Directory>, or <Files>) with particular + meta-information. These directives include ForceType, SetHandler, SetInputFilter, and SetOutputFilter. The core directives + override any filename extension mappings defined in + mod_mime.

+ +

Note that changing the meta-information for a file does not + change the value of the Last-Modified header. + Thus, previously cached copies may still be used by a client or + proxy, with the previous headers. If you change the + meta-information (language, content type, character set or + encoding) you may need to 'touch' affected files (updating + their last modified date) to ensure that all visitors are + receive the corrected content headers.

+
+ +
top
+
+

Files with Multiple Extensions

+

Files can have more than one extension, and the order of the + extensions is normally irrelevant. For example, if the + file welcome.html.fr maps onto content type + text/html and language French then the file + welcome.fr.html will map onto exactly the same + information. If more than one extension is given which maps onto + the same type of meta-information, then the one to the right will + be used, except for languages and content encodings. For example, + if .gif maps to the MIME-type + image/gif and .html maps to the + MIME-type text/html, then the file + welcome.gif.html will be associated with the + MIME-type text/html.

+ +

Languages and content encodings are treated accumulative, because one can assign + more than one language or encoding to a particular resource. For example, + the file welcome.html.en.de will be delivered with + Content-Language: en, de and Content-Type: + text/html.

+ +

Care should be taken when a file with multiple extensions + gets associated with both a MIME-type and a handler. This will + usually result in the request being by the module associated + with the handler. For example, if the .imap + extension is mapped to the handler imap-file (from + mod_imagemap) and the .html extension is + mapped to the MIME-type text/html, then the file + world.imap.html will be associated with both the + imap-file handler and text/html MIME-type. + When it is processed, the imap-file handler will be used, + and so it will be treated as a mod_imagemap imagemap + file.

+
top
+
+

Content encoding

+

A file of a particular MIME-type can additionally be encoded a + particular way to simplify transmission over the Internet. + While this usually will refer to compression, such as + gzip, it can also refer to encryption, such a + pgp or to an encoding such as UUencoding, which is + designed for transmitting a binary file in an ASCII (text) + format.

+ +

The HTTP/1.1 + RFC, section 14.11 puts it this way:

+ +
+

The Content-Encoding entity-header field is used as a modifier to + the media-type. When present, its value indicates what additional + content codings have been applied to the entity-body, and thus what + decoding mechanisms must be applied in order to obtain the media-type + referenced by the Content-Type header field. Content-Encoding is + primarily used to allow a document to be compressed without losing + the identity of its underlying media type.

+
+ +

By using more than one file extension (see section above about multiple file + extensions), you can indicate that a file is of a + particular type, and also has a particular + encoding.

+ +

For example, you may have a file which is a Microsoft Word + document, which is pkzipped to reduce its size. If the + .doc extension is associated with the Microsoft + Word file type, and the .zip extension is + associated with the pkzip file encoding, then the file + Resume.doc.zip would be known to be a pkzip'ed Word + document.

+ +

Apache sends a Content-encoding header with the + resource, in order to tell the client browser about the + encoding method.

+ +

Content-encoding: pkzip

+
top
+
+

Character sets and languages

+

In addition to file type and the file encoding, + another important piece of information is what language a + particular document is in, and in what character set the file + should be displayed. For example, the document might be written + in the Vietnamese alphabet, or in Cyrillic, and should be + displayed as such. This information, also, is transmitted in + HTTP headers.

+ +

The character set, language, encoding and mime type are all + used in the process of content negotiation (See + mod_negotiation) to determine + which document to give to the client, when there are + alternative documents in more than one character set, language, + encoding or mime type. All filename extensions associations + created with AddCharset, + AddEncoding, AddLanguage and AddType directives + (and extensions listed in the MimeMagicFile) participate in this select process. + Filename extensions that are only associated using the AddHandler, AddInputFilter or AddOutputFilter directives may be included or excluded + from matching by using the MultiviewsMatch directive.

+ +

Charset

+

To convey this further information, Apache optionally sends + a Content-Language header, to specify the language + that the document is in, and can append additional information + onto the Content-Type header to indicate the + particular character set that should be used to correctly + render the information.

+ +

+ Content-Language: en, fr
+ Content-Type: text/plain; charset=ISO-8859-1 +

+ +

The language specification is the two-letter abbreviation + for the language. The charset is the name of the + particular character set which should be used.

+ +
+
top
+

AddCharset Directive

+ + + + + + + +
Description:Maps the given filename extensions to the specified content +charset
Syntax:AddCharset charset extension +[extension] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

The AddCharset directive maps the given + filename extensions to the specified content charset. charset + is the MIME + charset parameter of filenames containing + extension. This mapping is added to any already in force, + overriding any mappings that already exist for the same + extension.

+ +

Example

+ AddLanguage ja .ja
+ AddCharset EUC-JP .euc
+ AddCharset ISO-2022-JP .jis
+ AddCharset SHIFT_JIS .sjis +

+ +

Then the document xxxx.ja.jis will be treated + as being a Japanese document whose charset is ISO-2022-JP + (as will the document xxxx.jis.ja). The + AddCharset directive is useful for both to + inform the client about the character encoding of the document so that + the document can be interpreted and displayed appropriately, and for content negotiation, + where the server returns one from several documents based on + the client's charset preference.

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +

See also

+ +
+
top
+

AddEncoding Directive

+ + + + + + + +
Description:Maps the given filename extensions to the specified encoding +type
Syntax:AddEncoding MIME-enc extension +[extension] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

The AddEncoding directive maps the given + filename extensions to the specified encoding type. MIME-enc + is the MIME encoding to use for documents containing the + extension. This mapping is added to any already in force, + overriding any mappings that already exist for the same + extension.

+ +

Example

+ AddEncoding x-gzip .gz
+ AddEncoding x-compress .Z +

+ +

This will cause filenames containing the .gz extension + to be marked as encoded using the x-gzip encoding, and + filenames containing the .Z extension to be marked as + encoded with x-compress.

+ +

Old clients expect x-gzip and x-compress, + however the standard dictates that they're equivalent to + gzip and compress respectively. Apache does + content encoding comparisons by ignoring any leading x-. + When responding with an encoding Apache will use whatever form + (i.e., x-foo or foo) the + client requested. If the client didn't specifically request a + particular form Apache will use the form given by the + AddEncoding directive. To make this long story + short, you should always use x-gzip and + x-compress for these two specific encodings. More + recent encodings, such as deflate should be + specified without the x-.

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +
+
top
+

AddHandler Directive

+ + + + + + + +
Description:Maps the filename extensions to the specified +handler
Syntax:AddHandler handler-name extension +[extension] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

Files having the name extension will be served by the + specified handler-name. This + mapping is added to any already in force, overriding any mappings that + already exist for the same extension. For example, to + activate CGI scripts with the file extension .cgi, you + might use:

+ +

+ AddHandler cgi-script .cgi +

+ +

Once that has been put into your httpd.conf file, any file containing + the .cgi extension will be treated as a CGI program.

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +

See also

+ +
+
top
+

AddInputFilter Directive

+ + + + + + + + +
Description:Maps filename extensions to the filters that will process +client requests
Syntax:AddInputFilter filter[;filter...] +extension [extension] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
Compatibility:AddInputFilter is only available in Apache 2.0.26 and +later.
+

AddInputFilter maps the filename extension + extension to the filters which + will process client requests and POST input when they are received by + the server. This is in addition to any filters defined elsewhere, + including the SetInputFilter + directive. This mapping is merged over any already in force, overriding + any mappings that already exist for the same extension.

+ +

If more than one filter is specified, they must be separated + by semicolons in the order in which they should process the + content. Both the filter and extension arguments are + case-insensitive, and the extension may be specified with or + without a leading dot.

+ +

See also

+ +
+
top
+

AddLanguage Directive

+ + + + + + + +
Description:Maps the given filename extension to the specified content +language
Syntax:AddLanguage MIME-lang extension +[extension] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

The AddLanguage directive maps the given + filename extension to the specified content language. + MIME-lang is the MIME language of filenames containing + extension. This mapping is added to any already in force, + overriding any mappings that already exist for the same + extension.

+ +

Example

+ AddEncoding x-compress .Z
+ AddLanguage en .en
+ AddLanguage fr .fr +

+ +

Then the document xxxx.en.Z will be treated as + being a compressed English document (as will the document + xxxx.Z.en). Although the content language is + reported to the client, the browser is unlikely to use this + information. The AddLanguage directive is + more useful for content + negotiation, where the server returns one from several documents + based on the client's language preference.

+ +

If multiple language assignments are made for the same + extension, the last one encountered is the one that is used. + That is, for the case of:

+ +

+ AddLanguage en .en
+ AddLanguage en-gb .en
+ AddLanguage en-us .en +

+ +

documents with the extension .en would be treated as + being en-us.

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +

See also

+ +
+
top
+

AddOutputFilter Directive

+ + + + + + + + +
Description:Maps filename extensions to the filters that will process +responses from the server
Syntax:AddOutputFilter filter[;filter...] +extension [extension] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
Compatibility:AddOutputFilter is only available in Apache 2.0.26 and +later.
+

The AddOutputFilter directive maps the + filename extension extension to the filters which will process responses + from the server before they are sent to the client. This is in + addition to any filters defined elsewhere, including SetOutputFilter and AddOutputFilterByType directive. This mapping is merged + over any already in force, overriding any mappings that already exist + for the same extension.

+ +

For example, the following configuration will process all + .shtml files for server-side includes and will then + compress the output using mod_deflate.

+ +

+ AddOutputFilter INCLUDES;DEFLATE shtml +

+ +

If more than one filter is specified, they must be separated + by semicolons in the order in which they should process the + content. Both the filter and extension arguments + are case-insensitive, and the extension may be specified with or + without a leading dot.

+ +

See also

+ +
+
top
+

AddType Directive

+ + + + + + + +
Description:Maps the given filename extensions onto the specified content +type
Syntax:AddType MIME-type extension +[extension] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

The AddType directive maps the given + filename extensions onto the specified content + type. MIME-type is the MIME + type to use for filenames containing + extension. This mapping is added to any already in + force, overriding any mappings that already exist for the same + extension. This directive can be used to add mappings + not listed in the MIME types file (see the TypesConfig directive).

+ +

Example

+ AddType image/gif .gif +

+ +
+ It is recommended that new MIME types be added using the + AddType directive rather than changing the + TypesConfig file. +
+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +

See also

+ +
+
top
+

DefaultLanguage Directive

+ + + + + + + +
Description:Sets all files in the given scope to the specified +language
Syntax:DefaultLanguage MIME-lang
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

The DefaultLanguage directive tells Apache + that all files in the directive's scope (e.g., all files + covered by the current <Directory> container) that don't have an explicit language + extension (such as .fr or .de as configured + by AddLanguage) should be + considered to be in the specified MIME-lang language. This + allows entire directories to be marked as containing Dutch content, for + instance, without having to rename each file. Note that unlike using + extensions to specify languages, DefaultLanguage + can only specify a single language.

+ +

If no DefaultLanguage directive is in force, + and a file does not have any language extensions as configured + by AddLanguage, then that file + will be considered to have no language attribute.

+ +

Example

+ DefaultLanguage en +

+ +

See also

+ +
+
top
+

ModMimeUsePathInfo Directive

+ + + + + + + + +
Description:Tells mod_mime to treat path_info +components as part of the filename
Syntax:ModMimeUsePathInfo On|Off
Default:ModMimeUsePathInfo Off
Context:directory
Status:Base
Module:mod_mime
Compatibility:Available in Apache 2.0.41 and later
+

The ModMimeUsePathInfo directive is used to + combine the filename with the path_info URL component to + apply mod_mime's directives to the request. The default + value is Off - therefore, the path_info + component is ignored.

+ +

This directive is recommended when you have a virtual filesystem.

+ +

Example

+ ModMimeUsePathInfo On +

+ +

If you have a request for /bar/foo.shtml where + /bar is a Location and ModMimeUsePathInfo is On, + mod_mime will treat the incoming request as + /bar/foo.shtml and directives like AddOutputFilter + INCLUDES .shtml will add the INCLUDES filter to the + request. If ModMimeUsePathInfo is not set, the + INCLUDES filter will not be added.

+ +

See also

+ +
+
top
+

MultiviewsMatch Directive

+ + + + + + + + + +
Description:The types of files that will be included when searching for +a matching file with MultiViews
Syntax:MultiviewsMatch Any|NegotiatedOnly|Filters|Handlers +[Handlers|Filters]
Default:MultiviewsMatch NegotiatedOnly
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
Compatibility:Available in Apache 2.0.26 and later.
+

MultiviewsMatch permits three different + behaviors for mod_negotiation's + Multiviews feature. Multiviews allows a request for a file, + e.g. index.html, to match any negotiated + extensions following the base request, e.g. + index.html.en, index.html.fr, or + index.html.gz.

+ +

The NegotiatedOnly option provides that every extension + following the base name must correlate to a recognized + mod_mime extension for content negotation, e.g. + Charset, Content-Type, Language, or Encoding. This is the strictest + implementation with the fewest unexpected side effects, and is the + default behavior.

+ +

To include extensions associated with Handlers and/or Filters, + set the MultiviewsMatch directive to either + Handlers, Filters, or both option keywords. + If all other factors are equal, the smallest file will be served, + e.g. in deciding between index.html.cgi of 500 + bytes and index.html.pl of 1000 bytes, the .cgi + file would win in this example. Users of .asis files + might prefer to use the Handler option, if .asis files are + associated with the asis-handler.

+ +

You may finally allow Any extensions to match, even if + mod_mime doesn't recognize the extension. This was the + behavior in Apache 1.3, and can cause unpredicatable results, such as + serving .old or .bak files the webmaster never expected to be served.

+ +

For example, the following configuration will allow handlers + and filters to participate in Multviews, but will exclude unknown + files:

+ +

+ MultiviewsMatch Handlers Filters +

+ +

See also

+ +
+
top
+

RemoveCharset Directive

+ + + + + + + + +
Description:Removes any character set associations for a set of file +extensions
Syntax:RemoveCharset extension [extension] +...
Context:virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
Compatibility:RemoveCharset is only available in Apache 2.0.24 and +later.
+

The RemoveCharset directive removes any + character set associations for files with the given extensions. + This allows .htaccess files in subdirectories to + undo any associations inherited from parent directories or the + server config files.

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +

Example

+ RemoveCharset .html .shtml +

+ +
+
top
+

RemoveEncoding Directive

+ + + + + + + +
Description:Removes any content encoding associations for a set of file +extensions
Syntax:RemoveEncoding extension [extension] +...
Context:virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

The RemoveEncoding directive removes any + encoding associations for files with the given extensions. This + allows .htaccess files in subdirectories to undo + any associations inherited from parent directories or the + server config files. An example of its use might be:

+ +

/foo/.htaccess:

+ AddEncoding x-gzip .gz
+ AddType text/plain .asc
+ <Files *.gz.asc>
+ + RemoveEncoding .gz
+ + </Files> +

+ +

This will cause foo.gz to be marked as being + encoded with the gzip method, but foo.gz.asc as an + unencoded plaintext file.

+ +

Note

+

RemoveEncoding directives are processed + after any AddEncoding + directives, so it is possible they may undo the effects of the latter + if both occur within the same directory configuration.

+
+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +
+
top
+

RemoveHandler Directive

+ + + + + + + +
Description:Removes any handler associations for a set of file +extensions
Syntax:RemoveHandler extension [extension] +...
Context:virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

The RemoveHandler directive removes any + handler associations for files with the given extensions. This allows + .htaccess files in subdirectories to undo any + associations inherited from parent directories or the server + config files. An example of its use might be:

+ +

/foo/.htaccess:

+ AddHandler server-parsed .html +

+ +

/foo/bar/.htaccess:

+ RemoveHandler .html +

+ +

This has the effect of returning .html files in + the /foo/bar directory to being treated as normal + files, rather than as candidates for parsing (see the mod_include module).

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +
+
top
+

RemoveInputFilter Directive

+ + + + + + + + +
Description:Removes any input filter associations for a set of file +extensions
Syntax:RemoveInputFilter extension [extension] +...
Context:virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
Compatibility:RemoveInputFilter is only available in Apache 2.0.26 and +later.
+

The RemoveInputFilter directive removes any + input filter associations for files with the given extensions. + This allows .htaccess files in subdirectories to + undo any associations inherited from parent directories or the + server config files.

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +

See also

+ +
+
top
+

RemoveLanguage Directive

+ + + + + + + + +
Description:Removes any language associations for a set of file +extensions
Syntax:RemoveLanguage extension [extension] +...
Context:virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
Compatibility:RemoveLanguage is only available in Apache 2.0.24 and +later.
+

The RemoveLanguage directive removes any + language associations for files with the given extensions. This + allows .htaccess files in subdirectories to undo + any associations inherited from parent directories or the + server config files.

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +
+
top
+

RemoveOutputFilter Directive

+ + + + + + + + +
Description:Removes any output filter associations for a set of file +extensions
Syntax:RemoveOutputFilter extension [extension] +...
Context:virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
Compatibility:RemoveOutputFilter is only available in Apache 2.0.26 and +later.
+

The RemoveOutputFilter directive removes any + output filter associations for files with the given extensions. + This allows .htaccess files in subdirectories to + undo any associations inherited from parent directories or the + server config files.

+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +

Example

+ RemoveOutputFilter shtml +

+ +

See also

+ +
+
top
+

RemoveType Directive

+ + + + + + + +
Description:Removes any content type associations for a set of file +extensions
Syntax:RemoveType extension [extension] +...
Context:virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_mime
+

The RemoveType directive removes any + MIME type associations for files with + the given extensions. This allows .htaccess files in + subdirectories to undo any associations inherited from parent + directories or the server config files. An example of its use + might be:

+ +

/foo/.htaccess:

+ RemoveType .cgi +

+ +

This will remove any special handling of .cgi + files in the /foo/ directory and any beneath it, + causing the files to be treated as being of the DefaultType.

+ +

Note

+

RemoveType directives are processed + after any AddType + directives, so it is possible they may undo the effects of the + latter if both occur within the same directory configuration.

+
+ +

The extension argument is case-insensitive, and can + be specified with or without a leading dot.

+ +
+
top
+

TypesConfig Directive

+ + + + + + + +
Description:The location of the mime.types file
Syntax:TypesConfig file-path
Default:TypesConfig conf/mime.types
Context:server config
Status:Base
Module:mod_mime
+

The TypesConfig directive sets the + location of the MIME types + configuration file. File-path is relative to the + ServerRoot. This file sets + the default list of mappings from filename extensions to content + types. Most administrators use the provided + mime.types file, which associates common filename + extensions with IANA registered content types. The current list is + maintained at http://www.iana.org/assignments/media-types/index.html. This + simplifies the httpd.conf file by providing the + majority of media-type definitions, and may be overridden by + AddType directives as + needed. You should not edit the mime.types file, + because it may be replaced when you upgrade your server.

+ +

The file contains lines in the format of the arguments to + an AddType directive:

+ +

+ MIME-type [extension] ... +

+ +

The case of the extension does not matter. Blank lines, and lines + beginning with a hash character (#) are ignored.

+ +
+ Please do not send requests to the Apache HTTP + Server Project to add any new entries in the distributed + mime.types file unless (1) they are already + registered with IANA, and (2) they use widely accepted, + non-conflicting filename extensions across platforms. + category/x-subtype requests will be automatically + rejected, as will any new two-letter extensions as they will + likely conflict later with the already crowded language and + character set namespace. +
+ +

See also

+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_mime.html.ja.euc-jp b/docs/manual/mod/mod_mime.html.ja.euc-jp new file mode 100644 index 00000000..b084bd82 --- /dev/null +++ b/docs/manual/mod/mod_mime.html.ja.euc-jp @@ -0,0 +1,939 @@ + + + +mod_mime - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_mime

+
+

Available Languages:  en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤È¥Õ¥¡¥¤¥ë¤Î¿¶¤ëÉñ¤¤ + (¥Ï¥ó¥É¥é¤È¥Õ¥£¥ë¥¿)¡¢ÆâÍÆ (MIME ¥¿¥¤¥×¡¢¸À¸ì¡¢Ê¸»ú¥»¥Ã¥È¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°) + ¤È¤ò´ØÏ¢ÉÕ¤±¤ë
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:mime_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_mime.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï³ÈÄ¥»Ò¤ò»È¤Ã¤Æ¤¤¤í¤¤¤í¤Ê¡Ö¥á¥¿¾ðÊó¡×¤ò¥Õ¥¡¥¤¥ë¤Ë + ´ØÏ¢ÉÕ¤±¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£¤³¤Î¾ðÊó¤Ï¥É¥­¥å¥á¥ó¥È¤Î¥Õ¥¡¥¤¥ë̾¤È + MIME ¥¿¥¤¥×¡¢¸À¸ì¡¢Ê¸»ú¥»¥Ã¥È¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤È¤ò´ØÏ¢ÉÕ¤±¤Þ¤¹¡£ + ¤³¤Î¾ðÊó¤Ï¥Ö¥é¥¦¥¶¤ËÁ÷¤é¤ì¤Þ¤¹¤·¡¢Ê£¿ô¤Î¥Õ¥¡¥¤¥ë¤ÎÃ椫¤é¥æ¡¼¥¶¤Î¹¥¤ß¤Î + ¤â¤Î¤¬Áª¤Ð¤ì¤ë¤è¤¦¤Ë¡¢¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Ç¤â»È¤ï¤ì¤Þ¤¹¡£ + ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó + ¤Ë´Ø¤¹¤ë¾Ü¤·¤¤¾ðÊó¤Ï mod_negotiation + ¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

AddCharset ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢ + AddEncoding ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢ + AddHandler ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢ + AddLanguage ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢ + AddType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¹¤Ù¤Æ¡¢ + ¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤ò¥á¥¿¾ðÊó¤Ë¥Þ¥Ã¥×¤¹¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£ + ¤½¤ì¤¾¤ì¡¢¥É¥­¥å¥á¥ó¥È¤Îʸ»ú¥»¥Ã¥È (ÌõÃí: charset)¡¢content-encoding, + content-language, MIME ¥¿¥¤¥× (content-type) ¤òÀßÄꤷ¤Þ¤¹¡£ + TypesConfig ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï³ÈÄ¥»Ò¤ò + MIME ¥¿¥¤¥×¤Ë¥Þ¥Ã¥×¤¹¤ë¥Õ¥¡¥¤¥ë¤ò»ØÄꤹ¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£

+ +

¤µ¤é¤Ë¡¢mod_mime ¤Ï¥³¥ó¥Æ¥ó¥Ä¤òºîÀ®¡¢½èÍý¤¹¤ë + ¥Ï¥ó¥É¥é ¤È ¥Õ¥£¥ë¥¿ + ¤òÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£AddHandler ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢AddOutputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢AddInputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥É¥­¥å¥á¥ó¥È¤ò°·¤¦¥â¥¸¥å¡¼¥ë¤ä¥¹¥¯¥ê¥×¥È¤òÀ©¸æ¤·¤Þ¤¹¡£ + MultiviewsMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬»ØÄꤷ¤¿¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤ò + mod_negotiation ¤¬ Multiviews ¤Î¥Þ¥Ã¥Á¤ò¤È¤ë¤È¤­¤Ë + ¹Íθ¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£

+ +

mod_mime ¤Ï¥á¥¿¾ðÊó¤ò¥Õ¥¡¥¤¥ë̾¤È´ØÏ¢ÉÕ¤±¤Þ¤¹¤¬¡¢ + core ¥µ¡¼¥Ð¤Ë¤Ï¤¢¤ë¥³¥ó¥Æ¥Ê + (¤¿¤È¤¨¤Ð, <Location>, <Directory>, <Files>) ¤ÎÃæ¤Î¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤òÆÃÄê¤Î + ¥á¥¿¾ðÊó¤È´ØÏ¢ÉÕ¤±¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤Ï + ForceType, SetHandler, SetInputFilter, SetOutputFilter ¤¬¤¢¤ê¤Þ¤¹¡£ + ¥³¥¢¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï mod_mime ¤Ë¤è¤êÄêµÁ¤µ¤ì¤¿ + ¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤Î¥Þ¥Ã¥Ô¥ó¥°¤¹¤Ù¤Æ¤ò¾å½ñ¤­¤·¤Þ¤¹¡£

+ +

¥Õ¥¡¥¤¥ë¤Î¥á¥¿¾ðÊó¤òÊѤ¨¤Æ¤â Last-Modified + ¥Ø¥Ã¥À¤ÎÃͤÏÊѤï¤é¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤Ç¤¹¤«¤é¡¢ + ¤½¤ì¤é¤òÊѹ¹¤·¤¿¾ì¹ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤ä¥×¥í¥­¥·¤Ç°ÊÁ°¤Ë¥­¥ã¥Ã¥·¥å¤µ¤ì¤¿ + ¥³¥Ô¡¼¤¬¤½¤Î¤È¤­¤Î¥Ø¥Ã¥À¤È¤È¤â¤Ë»È¤ï¤ì¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ + ¥á¥¿¾ðÊó (¸À¸ì¡¢¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¡¢Ê¸»ú¥»¥Ã¥È¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°) ¤ò + Êѹ¹¤·¤¿¤È¤­¤Ï¡¢¤¹¤Ù¤Æ¤ÎˬÌä¼Ô¤¬Àµ¤·¤¤¥³¥ó¥Æ¥ó¥È¥Ø¥Ã¥À¤ò + ¼õ¤±¼è¤ë¤è¤¦¤Ë¡¢±Æ¶Á¤ò¼õ¤±¤ë¥Õ¥¡¥¤¥ë¤Ë 'touch' ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë + (ºÇ½ª¹¹¿·Æü¤ò¹¹¿·¤¹¤ë) ɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+
+ +
top
+
+

Ê£¿ô¤Î³ÈÄ¥»Ò¤Î¤¢¤ë¥Õ¥¡¥¤¥ë

+

¥Õ¥¡¥¤¥ë¤ÏÊ£¿ô¤Î³ÈÄ¥»Ò¤ò»ý¤Ä¤³¤È¤¬¤Ç¤­¡¢³ÈÄ¥»Ò¤Î½çÈÖ¤ÏÄ̾ï¤Ï´Ø·¸¤¢¤ê¤Þ¤»¤ó¡£Î㤨¤Ð¡¢¥Õ¥¡¥¤¥ë welcome.html.fr + ¤¬¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤Ï text/html + ¤Ë¡¢¸À¸ì¤Ï¥Õ¥é¥ó¥¹¸ì¤Ë¥Þ¥Ã¥×¤µ¤ì¤ë¾ì¹ç¡¢welcome.fr.html + ¤â¤Þ¤Ã¤¿¤¯Æ±¤¸¾ðÊó¤Ë¥Þ¥Ã¥×¤µ¤ì¤Þ¤¹¡£ + Ʊ¤¸¥á¥¿¾ðÊó¤Ë¥Þ¥Ã¥×¤µ¤ì¤ë³ÈÄ¥»Ò¤¬Ê£¿ô¤¢¤ë¤È¤­¤Ë¤Ï¡¢¸À¸ì¤È + ¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ò½ü¤¤¤Æ¡¢ + ±¦Â¦¤Ë¤¢¤ë¤â¤Î¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢.gif ¤¬ MIME + ¥¿¥¤¥× image/gif ¤Ë¥Þ¥Ã¥×¤µ¤ì¡¢.html + ¤¬ MIME ¥¿¥¤¥× text/html + ¤Ë¥Þ¥Ã¥×¤µ¤ì¤ë¾ì¹ç¤Ï¡¢¥Õ¥¡¥¤¥ë welcome.gif.html ¤Ï + MIME ¥¿¥¤¥× text/html ¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤Þ¤¹¡£

+ +

¥ê¥½¡¼¥¹¤ËÊ£¿ô¤Î¸À¸ì¤ä¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ò´ØÏ¢ÉÕ¤±¤ë¤³¤È + ¤¬¤Ç¤­¤ë¤¿¤á¡¢ + ¸À¸ì¤È¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ÏÁ°¤Î¤â¤Î¤ËÄɲ䵤ì¤Æ¤¤¤­¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¡¢¥Õ¥¡¥¤¥ë welcome.html.en.de ¤Ï + Content-Language: en, de ¤È Content-Type: + text/html ¤È¤·¤ÆÁ÷¿®¤µ¤ì¤Þ¤¹¡£

+ +

Ê£¿ô¤Î³ÈÄ¥»Ò¤Î¤¢¤ë¥Õ¥¡¥¤¥ë¤¬ MIME + ¥¿¥¤¥×¤È¥Ï¥ó¥É¥é¤ÎξÊý¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤Æ¤¤¤ë¤È¤­¤ÏÃí°Õ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤½¤Î¾ì¹ç¡¢ÉáÄ̤ϥꥯ¥¨¥¹¥È¤¬¥Ï¥ó¥É¥é¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿ + ¥â¥¸¥å¡¼¥ë¤Ë¤è¤Ã¤Æ°·¤ï¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢³ÈÄ¥»Ò + .imap ¤¬ (mod_imagemap ¤Î) imap-file + ¤Ë¥Þ¥Ã¥×¤µ¤ì¤Æ¤¤¤Æ¡¢.html ¤¬ MIME ¥¿¥¤¥× text/html + ¤Ë¥Þ¥Ã¥×¤µ¤ì¤Æ¤¤¤ë¤È¤­¤Ï¡¢¥Õ¥¡¥¤¥ë world.imap.html ¤Ï + imap-file ¥Ï¥ó¥É¥é¤È text/html MIME + ¥¿¥¤¥×¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤Þ¤¹¡£¥Õ¥¡¥¤¥ë¤¬½èÍý¤µ¤ì¤ë¤È¤­¤Ï imap-file + ¥Ï¥ó¥É¥é¤¬»ÈÍѤµ¤ì¤Þ¤¹¤Î¤Ç¡¢¤½¤Î¥Õ¥¡¥¤¥ë¤Ï mod_imagemap + ¤Î¥¤¥á¡¼¥¸¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤È¤·¤Æ°·¤ï¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+
top
+
+

¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°

+

ÆÃÄê¤Î MIME ¥¿¥¤¥×¤Î¥Õ¥¡¥¤¥ë¤Ï¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Ç¤ÎžÁ÷¤ò´Êñ¤Ë¤¹¤ë¤¿¤á¤Ë¡¢ + ¤µ¤é¤ËÉä¹æ²½¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤ÏÄ̾ï¤Ï gzip ¤Î + ¤è¤¦¤Ê°µ½Ì¤Î¤³¤È¤ò»Ø¤·¤Þ¤¹¤¬¡¢pgp ¤Î¤è¤¦¤Ê°Å¹æ²½¤ä¡¢ + ¥Ð¥¤¥Ê¥ê¥Õ¥¡¥¤¥ë¤ò ASCII (¥Æ¥­¥¹¥È) ·Á¼°¤ÇÁ÷¤ë¤¿¤á¤Ë¹Í°Æ¤µ¤ì¤¿ + UUencoding ¤Î¤³¤È¤ò»Ø¤¹¤³¤È¤â¤¢¤ê¤Þ¤¹¡£

+ +

HTTP/1.1 RFC + 14.11 Àá¤Ç¤Ï¼¡¤Î¤è¤¦¤Ëµ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +
+

Content-Encoding ¥¨¥ó¥Æ¥£¥Æ¥£¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤Ï¥á¥Ç¥£¥¢¥¿¥¤¥×¤Î + ½¤¾þ»Ò¤È¤·¤Æ»È¤ï¤ì¤Þ¤¹¡£¤½¤ì¤¬Â¸ºß¤·¤Æ¤¤¤ì¤Ð¡¢Ãͤϥ¨¥ó¥Æ¥£¥Æ¥£¥Ü¥Ç¥£¤Ë + ¤É¤ÎÄɲäÎÉä¹æ²½¤¬Å¬ÍѤµ¤ì¤¿¤«¤ò¼¨¤·¡¢Content-Type ¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤Ë + ½ñ¤«¤ì¤Æ¤¤¤ë¥á¥Ç¥£¥¢¥¿¥¤¥×¤òÆÀ¤ë¤¿¤á¤Ë¤É¤ÎÉü¹æµ¡¹½¤òŬÍѤ¹¤Ù¤­¤«¡¢¤â + ¼¨¤·¤Æ¤¤¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£Content-Encoding ¤Ï¼ç¤Ë¡¢¸µ¤Î¥á¥Ç¥£¥¢¥¿¥¤¥×¤Î + Ʊ°ìÀ­¤ò¼º¤¦¤³¤È¤Ê¤¯¥É¥­¥å¥á¥ó¥È¤ò°µ½Ì¤¹¤ë¤³¤È¤ò²Äǽ¤Ë¤¹¤ë¤¿¤á¤Ë + »ÈÍѤµ¤ì¤Þ¤¹¡£

+
+ +

Ê£¿ô¤Î¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò (Ê£¿ô¤Î³ÈÄ¥»Ò¤Ë¤Ä¤¤¤Æ¤Ï ¾å¤ÎÀá ¤ò»²¾È) »È¤¦¤³¤È¤Ç¡¢ + ¥Õ¥¡¥¤¥ë¤Î¥¿¥¤¥×¤ä¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ò»ØÄꤹ¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+ +

¤¿¤È¤¨¤Ð¡¢Microsoft Word ¤Î¥É¥­¥å¥á¥ó¥È¤¬¤¢¤ê¡¢¥µ¥¤¥º¤ò¾®¤µ¤¯¤¹¤ë¤¿¤á¤Ë + pkzip ¤µ¤ì¤Æ¤¤¤ë¤È¤·¤Þ¤¹¡£.doc ³ÈÄ¥»Ò¤¬ Microsoft Word ¤Î + ¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤È´ØÏ¢ÉÕ¤±¤é¤ì¤Æ¤¤¤Æ¡¢.zip ³ÈÄ¥»Ò¤¬ + pkzip ¥Õ¥¡¥¤¥ë¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤È´ØÏ¢ÉÕ¤±¤é¤ì¤Æ¤¤¤ë¤È¡¢¥Õ¥¡¥¤¥ë + Resume.doc.zip ¤Ï pkzip ¤µ¤ì¤¿ Word ¥É¥­¥å¥á¥ó¥È¤Ç¤¢¤ë + ¤È¤¤¤¦¤³¤È¤¬¤ï¤«¤ê¤Þ¤¹¡£

+ +

¥¯¥é¥¤¥¢¥ó¥È¤Î¥Ö¥é¥¦¥¶¤Ë¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°ÊýË¡¤òÃΤ餻¤ë¤¿¤á¤Ë¡¢ + Apache ¤Ï¥ê¥½¡¼¥¹¤È¶¦¤Ë Content-Encoding ¥Ø¥Ã¥À¤ò + Á÷¤ê¤Þ¤¹¡£

+ +

Content-encoding: pkzip

+
top
+
+

ʸ»ú¥»¥Ã¥È¤È¸À¸ì

+

¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤È¥Õ¥¡¥¤¥ë¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Î¾¤Ë½ÅÍפʾðÊó¤Ï + ¥É¥­¥å¥á¥ó¥È¤Î½ñ¤«¤ì¤Æ¤¤¤ë¸À¸ì¤È¡¢¤É¤Îʸ»ú¥»¥Ã¥È¤Ç¥Õ¥¡¥¤¥ë¤¬É½¼¨ + ¤µ¤ì¤ë¤Ù¤­¤«¡¢¤È¤¤¤¦¤â¤Î¤Ç¤¹¡£¤¿¤È¤¨¤Ð¡¢¥É¥­¥å¥á¥ó¥È¤Ï¥Ù¥È¥Ê¥à¤Î + ¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È¤ä¥­¥ê¥ëʸ»ú¤Ç½ñ¤«¤ì¤Æ¤¤¤Æ¡¢¤½¤Î¤è¤¦¤Ëɽ¼¨¤µ¤ì¤ë + ɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¤³¤Î¾ðÊó¤â¤Þ¤¿¡¢HTTP ¥Ø¥Ã¥À¤Ç + Á÷¿®¤µ¤ì¤Þ¤¹¡£

+ +

ʸ»ú¥»¥Ã¥È¡¢¸À¸ì¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¡¢mime ¥¿¥¤¥×¤Ï¤¹¤Ù¤Æ + ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó (mod_negotiation »²¾È) + ¤ÎºÇÃæ¤Ë¡¢Ê£¿ô¤Îʸ»ú¥»¥Ã¥È¡¢¸À¸ì¡¢¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¡¢MIME ¥¿¥¤¥×¤«¤é¤Ê¤ë + ÂåÂØʪ¤¬¤¢¤ë¤È¤­¤Ë¤É¤Î¥É¥­¥å¥á¥ó¥È¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ë¤Î¤«¤ò + ·èÄꤹ¤ë¤È¤­¤Ë»È¤ï¤ì¤Þ¤¹¡£AddCharset, + AddEncoding, AddLanguage, + AddType ¤Î³Æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇºîÀ®¤µ¤ì¤¿ + ³ÈÄ¥»Ò¤Î´ØÏ¢ÉÕ¤± (¤È MimeMagicFile ¤Ç¥ê¥¹¥È¤µ¤ì¤Æ¤¤¤ë + ³ÈÄ¥»Ò) ¤¬¤³¤ÎÁªÂò¤Ë»²²Ã¤·¤Þ¤¹¡£AddHandler, + AddInputFilter, + AddOutputFilter ¤Î + ³Æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Î¤ß´ØÏ¢ÉÕ¤±¤é¤ì¤Æ¤¤¤ë³ÈÄ¥»Ò¤Ï + MultiviewsMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤¦¤³¤È¤Ç¥Þ¥Ã¥Á¤Î + ½èÍý¤Ë´Þ¤á¤ë¤³¤È¤â³°¤¹¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

Charset

+

¤µ¤é¤Ë¾ðÊó¤òÅÁ¤¨¤ë¤¿¤á¤Ë¡¢Apache ¤Ïʸ½ñ¤Î¸À¸ì¤ò + Content-Language ¥Ø¥Ã¥À¤ÇÁ÷¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£ + ¤Þ¤¿¡¢¾ðÊó¤òÀµ¤·¤¯É½¼¨¤¹¤ë¤¿¤á¤Ë»ÈÍѤ¹¤Ù¤­Ê¸»ú¥»¥Ã¥È¤ò¼¨¤¹¤¿¤á¤Ë + Conten-Type ¥Ø¥Ã¥À¤Ë¾ðÊó¤òÄɲ乤뤳¤È¤â¤¢¤ê¤Þ¤¹¡£

+ +

+ Content-Language: en, fr
+ Content-Type: text/plain; charset=ISO-8859-1 +

+ +

¸À¸ì¤Î»ØÄê¤ÏÆóʸ»ú¤Îû½Ì·Á¤Ç¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£charset ¤¬ + »ÈÍѤ¹¤Ù¤­Ê¸»ú¥»¥Ã¥È¤Î̾Á°¤Ç¤¹¡£

+ +
+
top
+

AddCharset ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿Ê¸»ú¥»¥Ã¥È¤Ë¥Þ¥Ã¥×¤¹¤ë
¹½Ê¸:AddCharset charset extension +[extension] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

AddCharset ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + Í¿¤¨¤é¤ì¤¿³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿ charset ¤Ë¥Þ¥Ã¥×¤·¤Þ¤¹¡£charset + ¤Ï¡¢³ÈÄ¥»Ò extension ¤ò´Þ¤ó¤Ç¤¤¤ë¥Õ¥¡¥¤¥ë̾¤Î + MIME charset + ¥Ñ¥é¥á¡¼¥¿¤Ç¤¹¡£¿·¤·¤¤¥Þ¥Ã¥Ô¥ó¥°¤Ï´û¤Ë¤¢¤ë¾¤Î¥Þ¥Ã¥Ô¥ó¥°¤ËÄɲ䵤졢Ʊ¤¸³ÈÄ¥»Ò + extension ¤Î¤¿¤á¤Î¥Þ¥Ã¥Ô¥ó¥°¤ò¾å½ñ¤­¤·¤Þ¤¹¡£

+ +

Îã

+ AddLanguage ja .ja
+ AddCharset EUC-JP .euc
+ AddCharset ISO-2022-JP .jis
+ AddCharset SHIFT_JIS .sjis +

+ +

¤³¤Î¾ì¹ç¡¢¥É¥­¥å¥á¥ó¥È xxxx.ja.jis ¤Ï charset ¤¬ + ISO-2022-JP ¤ÎÆüËܸì¤Î¥É¥­¥å¥á¥ó¥È¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹ + (xxxx.jis.ja ¤âƱÍÍ)¡£AddCharset + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤¬Å¬Àڤ˲ò¼á¤µ¤ìɽ¼¨¤µ¤ì¤ë¤è¤¦¤Ë¡¢ + ¥É¥­¥å¥á¥ó¥È¤Î charset ¤Î¾ðÊó¤ò¥¯¥é¥¤¥¢¥ó¥È¤Ë¶µ¤¨¤ë¤¿¤á¤ËÌò¤ËΩ¤Á¤Þ¤¹¡£ + ¤Þ¤¿¡¢¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤Î charset + ¤ÎÍ¥ÀèÅ٤˴ð¤Å¤¤¤ÆÊ£¿ô¤Î¥É¥­¥å¥á¥ó¥È¤ÎÃ椫¤é¥É¥­¥å¥á¥ó¥È¤òÁª¤Ö¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î¤¿¤á¤Ë¤âÌò¤ËΩ¤Á¤Þ¤¹¡£

+ +

°ú¿ô extension¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¡¢ + ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

»²¾È

+ +
+
top
+

AddEncoding ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿¥¨¥ó¥³¡¼¥Ç¥£¥ó¥° +¤Ë¥Þ¥Ã¥×¤¹¤ë
¹½Ê¸:AddEncoding MIME-enc extension +[extension] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

AddEncoding ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + Í¿¤¨¤é¤ì¤¿³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ë¥Þ¥Ã¥×¤·¤Þ¤¹¡£ + MIME-enc ¤Ï¡¢³ÈÄ¥»Ò extension + ¤ò´Þ¤ó¤À¥É¥­¥å¥á¥ó¥È¤Ë»ÈÍѤ¹¤ë MIME ¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ç¤¹¡£ + ¤³¤Î¿·¤·¤¤¥Þ¥Ã¥Ô¥ó¥°¤Ï´û¤Ë¤¢¤ë¾¤Î¥Þ¥Ã¥Ô¥ó¥°¤ËÄɲ䵤졢 + Ʊ¤¸³ÈÄ¥»Ò extension ¤Î¤¿¤á¤Î¥Þ¥Ã¥Ô¥ó¥°¤ò¾å½ñ¤­¤·¤Þ¤¹¡£

+ +

Îã

+ AddEncoding x-gzip .gz
+ AddEncoding x-compress .Z +

+ +

¤³¤ì¤Ï¡¢³ÈÄ¥»Ò .gz ¤ò´Þ¤à¥Õ¥¡¥¤¥ë̾¤¬ x-gzip + ¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ò»È¤Ã¤Æ¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë¤³¤È¤È¡¢³ÈÄ¥»Ò .Z + ¤ò´Þ¤à¥Õ¥¡¥¤¥ë̾¤¬ x-compress + ¤Ç¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ò»ØÄꤷ¤Þ¤¹¡£

+ +

¸Å¤¤¥¯¥é¥¤¥¢¥ó¥È¤Ï x-zip ¤È x-compress + ¤¬Ê֤äƤ¯¤ë¤³¤È¤ò´üÂÔ¤·¤Þ¤¹¤¬¡¢É¸½àµ¬³Ê¤Ç¤Ï¤½¤ì¤¾¤ì + gzip ¤È compress + ¤ÈÅù²Á¤Ç¤¢¤ë¤³¤È¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£Apache + ¤Ï¡¢¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ÎÈæ³Ó¤ò¤¹¤ë¤È¤­¤Ë¤Ï¡¢ÀèƬ¤Ë¤¢¤ë + x- ¤ò̵»ë¤·¤Þ¤¹¡£Apache + ¤¬¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°ÉÕ¤­¤Ç±þÅú¤òÊÖ¤¹¤È¤­¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬Í׵ᤷ¤¿·Á¼° + (¤¹¤Ê¤ï¤Á¡¢x-foo ¤ä foo) + ¤ò»ÈÍѤ·¤Þ¤¹¡£Íפ¹¤ë¤Ë¡¢¤³¤ÎÆó¤Ä¤Î¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Î¾ì¹ç¤Ï¾ï¤Ë + x-gzip ¤È x-compress + ¤ò»È¤¦¤Ù¤­¤Ç¤¢¤ë¡¢¤È¤¤¤¦¤³¤È¤Ç¤¹¡£deflate + ¤Î¤è¤¦¤Ê¤è¤ê¿·¤·¤¤¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ç¤Ï¡¢x- + ¤Ê¤·¤Ç»ØÄꤷ¤Æ¤¯¤À¤µ¤¤¡£ +

+ +

°ú¿ô extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¡¢ + ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +
+
top
+

AddHandler ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿¥Ï¥ó¥É¥é¤Ë¥Þ¥Ã¥×¤¹¤ë
¹½Ê¸:AddHandler handler-name extension +[extension] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

³ÈÄ¥»Ò extension ¤¬Ì¾Á°¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¤Ï»ØÄꤵ¤ì¤¿ handler-name ¤Ë°·¤ï¤ì¤Þ¤¹¡£ + ¤³¤Î¿·¤·¤¤¥Þ¥Ã¥Ô¥ó¥°¤Ï´û¤Ë¤¢¤ë¾¤Î¥Þ¥Ã¥Ô¥ó¥°¤ËÄɲ䵤졢 + Ʊ¤¸³ÈÄ¥»Ò extension + ¤Î¤¿¤á¤Î¥Þ¥Ã¥Ô¥ó¥°¤ò¾å½ñ¤­¤·¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢³ÈÄ¥»Ò + ".cgi" ¤Ç½ª¤ï¤ë¥Õ¥¡¥¤¥ë¤ò CGI + ¥¹¥¯¥ê¥×¥È¤È¤·¤Æ°·¤¤¤¿¤¤¤È¤­¤Ï¡¢°Ê²¼¤ÎÀßÄê¤ò¤·¤Þ¤¹¡£

+ +

+ AddHandler cgi-script .cgi +

+ +

¤³¤ì¤ò httpd.conf ¥Õ¥¡¥¤¥ë¤Ëµ­½Ò¤¹¤ë¤³¤È¤Ç¡¢³ÈÄ¥»Ò + ".cgi" ¤Î¥Õ¥¡¥¤¥ë¤Ï CGI ¥×¥í¥°¥é¥à¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£ +

+ +

°ú¿ô extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¡¢ + ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

»²¾È

+ +
+
top
+

AddInputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤ò¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤¹¤ë + ¥Õ¥£¥ë¥¿¤Ë¥Þ¥Ã¥×¤¹¤ë
¹½Ê¸:AddInputFilter filter[;filter...] +extension [extension] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
¸ß´¹À­:2.0.26 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

AddInputFilter ¤Ï¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò + extension ¤ò¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ä POST ¤¬¥µ¡¼¥Ð¤ËÍ褿¤È¤­¤Ë + ½èÍý¤ò¤¹¤ë¥Õ¥£¥ë¥¿¤Ë¥Þ¥Ã¥×¤·¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢SetInputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤â + ´Þ¤á¡¢Â¾¤Î¾ì½ê¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë¥Õ¥£¥ë¥¿¤Ë²Ã¤¨¤é¤ì¤Þ¤¹¡£ + ¤³¤Î¥Þ¥Ã¥Ô¥ó¥°¤Ï¤¹¤Ç¤Ë¤¢¤ë¤â¤Î¤è¤êÍ¥À褵¤ì¤Æ¥Þ¡¼¥¸¤µ¤ì¡¢ + Ʊ¤¸ extension ¤ËÂФ¹¤ë´û¸¤Î¥Þ¥Ã¥Ô¥ó¥°¤ò¾å½ñ¤­¤·¤Þ¤¹¡£

+ +

Ê£¿ô¤Î¥Õ¥£¥ë¥¿¤ò»ØÄꤹ¤ë¤È¤­¤Ï¡¢¥Ç¡¼¥¿¤ò½èÍý¤¹¤ë½çÈ֤˥»¥ß¥³¥í¥ó¤Ç + ·Ò¤¤¤Ç½ñ¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£¥Õ¥£¥ë¥¿¤È extension ¤È¤Î + ξÊý¤Î°ú¿ô¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¡¢³ÈÄ¥»Ò¤ÎºÇ½é¤Î¥É¥Ã¥È¤Ï + ¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

»²¾È

+ +
+
top
+

AddLanguage ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë̾¤ò»ØÄꤵ¤ì¤¿¸À¸ì¤Ë¥Þ¥Ã¥×
¹½Ê¸:AddLanguage MIME-lang extension +[extension] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

AddLanguage ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Í¿¤¨¤é¤ì¤¿³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿ + content language ¤Ë¥Þ¥Ã¥×¤·¤Þ¤¹¡£MIME-lang ¤Ï¡¢³ÈÄ¥»Ò + extension ¤ò´Þ¤ó¤Ç¤¤¤ë¥Õ¥¡¥¤¥ë̾¤Î MIME ¤Ë¤ª¤±¤ë¸À¸ì¤Ç¤¹¡£ + ¤³¤Î¿·¤·¤¤¥Þ¥Ã¥Ô¥ó¥°¤Ï´û¤Ë¤¢¤ë¥Þ¥Ã¥Ô¥ó¥°¤ËÄɲ䵤졢Ʊ¤¸³ÈÄ¥»Ò + extension ¤Î¤¿¤á¤Î¥Þ¥Ã¥Ô¥ó¥°¤ò¾å½ñ¤­¤·¤Þ¤¹¡£

+ +

Îã

+ AddEncoding x-compress .Z
+ AddLanguage en .en
+ AddLanguage fr .fr +

+ +

¤³¤Î¾ì¹ç¡¢xxxx.en.Z ¥É¥­¥å¥á¥ó¥È¤Ï compress + ¤µ¤ì¤¿±Ñ¸ì¤Î¥É¥­¥å¥á¥ó¥È¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹ (xxxx.Z.en + ¤âƱÍÍ)¡£content language ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÄÌÃΤµ¤ì¤Þ¤¹¤¬¡¢ + ¥Ö¥é¥¦¥¶¤¬¤³¤Î¾ðÊó¤ò»È¤¦¤³¤È¤Ï¤ª¤½¤é¤¯¤¢¤ê¤Þ¤»¤ó¡£ + AddLanguage + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤Î¸À¸ì¤ÎÍ¥ÀèÅ٤˴ð¤Å¤¤¤ÆÊ£¿ô¤Î + ¥É¥­¥å¥á¥ó¥È¤ÎÃ椫¤é¥É¥­¥å¥á¥ó¥È¤òÁª¤Ö¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î¤¿¤á¤Ë¤è¤êÌò¤ËΩ¤Á¤Þ¤¹¡£

+ +

Ê£¿ô¤Î¸À¸ì¤¬Æ±¤¸³ÈÄ¥»Ò¤Ë³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤ë¤È¤­¤Ï¡¢ + ºÇ¸å¤Î¤â¤Î¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£¤¹¤Ê¤ï¤Á¡¢¼¡¤Î¤è¤¦¤Ê¾ì¹ç¡¢

+ +

+ AddLanguage en .en
+ AddLanguage en-gb .en
+ AddLanguage en-us .en +

+ +

³ÈÄ¥»Ò .en ¤Î¤¢¤ë¥É¥­¥å¥á¥ó¥È¤Ï + en-us ¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£

+ +

°ú¿ô extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¡¢ + ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

»²¾È

+ +
+
top
+

AddOutputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò¥µ¡¼¥Ð¤«¤é¤Î±þÅú¤ò½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤Ë + ¥Þ¥Ã¥×¤¹¤ë
¹½Ê¸:AddOutputFilter filter[;filter...] +extension [extension] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
¸ß´¹À­:2.0.26 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

AddOutputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ³ÈÄ¥»Ò extension ¤ò¥µ¡¼¥Ð¤Î±þÅú¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤é¤ì¤ë + Á°¤Ë½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤òÄêµÁ¤·¤Þ¤¹¡£ + ¤³¤ì¤Ï SetOutputFilter + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È AddOutputFilterByType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤ò´Þ¤á¡¢Â¾¤Î¾ì½ê¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë¥Õ¥£¥ë¥¿¤Ë²Ã¤¨¤é¤ì¤Þ¤¹¡£ + ¤³¤Î¿·¤·¤¤¥Þ¥Ã¥Ô¥ó¥°¤Ï´û¤Ë¤¢¤ë¥Þ¥Ã¥Ô¥ó¥°¤ËÄɲ䵤졢Ʊ¤¸³ÈÄ¥»Ò + extension ¤Î¤¿¤á¤Î¥Þ¥Ã¥Ô¥ó¥°¤ò¾å½ñ¤­¤·¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢°Ê²¼¤ÎÀßÄê¤Ï¤¹¤Ù¤Æ¤Î .shtml ¥Õ¥¡¥¤¥ë¤ò SSI ¤Ç½èÍý¤·¡¢ + ¤½¤Î½ÐÎϤò mod_deflate ¤ò»È¤Ã¤Æ°µ½Ì¤·¤Þ¤¹¡£

+ +

+ AddOutputFilter INCLUDES;DEFLATE shtml +

+ +

Ê£¿ô¤Î¥Õ¥£¥ë¥¿¤ò»ØÄꤹ¤ë¤È¤­¤Ï¡¢¥Ç¡¼¥¿¤ò½èÍý¤¹¤ë½çÈ֤˥»¥ß¥³¥í¥ó¤Ç + ·Ò¤¤¤Ç½ñ¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£filter ¤È extension ¤Î + ξ°ú¿ô¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¡¢³ÈÄ¥»Ò¤ÎºÇ½é¤Î¥É¥Ã¥È¤Ï + ¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

»²¾È

+ +
+
top
+

AddType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤Ë¥Þ¥Ã¥×
¹½Ê¸:AddType MIME-type extension +[extension] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

AddType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + Í¿¤¨¤é¤ì¤¿³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤Ë¥Þ¥Ã¥×¤·¤Þ¤¹¡£ + MIME-type ¤Ï³ÈÄ¥»Ò extension + ¤ò´Þ¤ó¤À¥É¥­¥å¥á¥ó¥È¤Ë»ÈÍѤ¹¤ë MIME ¥¿¥¤¥×¤Ç¤¹¡£ + ¤³¤Î¿·¤·¤¤¥Þ¥Ã¥Ô¥ó¥°¤Ï´û¤Ë¤¢¤ë¥Þ¥Ã¥Ô¥ó¥°¤ËÄɲ䵤졢Ʊ¤¸³ÈÄ¥»Ò + extension ¤Î¤¿¤á¤Î¥Þ¥Ã¥Ô¥ó¥°¤ò¾å½ñ¤­¤·¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï MIME ¥¿¥¤¥×¥Õ¥¡¥¤¥ë (TypesConfig ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»²¾È) + ¤Ë̵¤¤¥Þ¥Ã¥Ô¥ó¥°¤òÄɲ乤뤿¤á¤Ë»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Îã

+ AddType image/gif .gif +

+ +
+ ¿·¤·¤¤ MIME ¥¿¥¤¥×¤Ï¡¢TypesConfig + ¥Õ¥¡¥¤¥ë¤òÊѹ¹¤¹¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢AddType + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤ÆÄɲ乤뤳¤È¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ +
+ +

°ú¿ô extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¡¢ + ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

»²¾È

+ +
+
top
+

DefaultLanguage ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¤¢¤ë¥¹¥³¡¼¥×¤Î¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò»ØÄꤵ¤ì¤¿¸À¸ì¤Ë +ÀßÄꤹ¤ë
¹½Ê¸:DefaultLanguage MIME-lang
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

DefaultLanguage ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Apache + ¤¬¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥¹¥³¡¼¥× (Î㤨¤Ð¡¢¤½¤Î»þÅÀ¤Î + <Directory> + ¤ÎÈÏ°Ï) ¤Ë¤¢¤ë¡¢ÌÀ¼¨Åª¤Ê¸À¸ì³ÈÄ¥»Ò + (AddLanguage ¤ÇÀßÄꤵ¤ì¤ë + .fr ¤ä .de) ¤Î¤Ê¤¤Á´¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò¡¢»ØÄꤵ¤ì¤¿ + MIME-lang ¸À¸ì¤Ç¤¢¤ë¤È¤ß¤Ê¤¹¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë̾¤òÊѤ¨¤ë¤³¤È¤Ê¤¯¡¢ + ¥Ç¥£¥ì¥¯¥È¥ê¤¬¥ª¥é¥ó¥À¸ì¤Î¥³¥ó¥Æ¥ó¥È¤ò´Þ¤ó¤Ç¤¤¤ë¡¢ + ¤È¤¤¤¦¤è¤¦¤Ê¤³¤È¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ³ÈÄ¥»Ò¤ò»ÈÍѤ·¤Æ¸À¸ì¤ò»ØÄꤹ¤ëÊýË¡¤È°ã¤¤¡¢ + DefaultLanguage + ¤Ï°ì¤Ä¤Î¸À¸ì¤·¤«»ØÄê¤Ç¤­¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

DefaultLanguage + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Í­¸ú¤Ç¤Ê¤¯¡¢¥Õ¥¡¥¤¥ë¤Ë + AddLanguage + ¤ÇÀßÄꤵ¤ì¤¿¸À¸ì¤Î³ÈÄ¥»Ò¤¬¤Ê¤¤¤È¤­¤Ï¡¢ + ¥Õ¥¡¥¤¥ë¤Ë¤Ï¸À¸ì°À­¤¬¤Ê¤¤¤È¤ß¤Ê¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ DefaultLanguage en +

+ +

»²¾È

+ +
+
top
+

ModMimeUsePathInfo ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:path_info ¥³¥ó¥Ý¡¼¥Í¥ó¥È¤ò¥Õ¥¡¥¤¥ë̾¤Î°ìÉô¤È¤·¤Æ°·¤¦¤è¤¦¤Ë +mod_mime ¤ËÄÌÃΤ¹¤ë
¹½Ê¸:ModMimeUsePathInfo On|Off
¥Ç¥Õ¥©¥ë¥È:ModMimeUsePathInfo Off
¥³¥ó¥Æ¥­¥¹¥È:¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
¸ß´¹À­:Apache 2.0.41 °Ê¹ß
+

ModMimeUsePathInfo ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + mod_mime ¤Î»ý¤Ä¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ¥ê¥¯¥¨¥¹¥È¤ËŬÍѤµ¤»¤ë¤¿¤á¤Ë¡¢¥Õ¥¡¥¤¥ë̾¤È path_info URL + ¥³¥ó¥Ý¡¼¥Í¥ó¥È¤ò·ë¹ç¤µ¤»¤ë¤¿¤á¤Ë»ÈÍѤ·¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡Ö Off ¡×¤Ç¡¢path_info + ¥³¥ó¥Ý¡¼¥Í¥ó¥È¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥Ð¡¼¥Á¥ã¥ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò»ÈÍѤ·¤Æ¤¤¤ëºÝ¤Ë + ¿ä¾©¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤¹¡£

+ +

Îã

+ ModMimeUsePathInfo On +

+ +

/bar ¤¬Â¸ºß¤·¤Æ (foo.shtml ¤Ï¸ºß¤·¤Ê¤¤) + ModMimeUsePathInfo ¤¬ On ¤Ç¤¢¤ë¤È¤·¤Æ¡¢ + /bar/foo.shtml ¤ËÂФ¹¤ë¥ê¥¯¥¨¥¹¥È¤òȯ¹Ô¤·¤¿¾ì¹ç¡¢ + mod_mime ¤ÏÆþ¤Ã¤Æ¤­¤¿¥ê¥¯¥¨¥¹¥È¤ò + /bar/foo.shtml ¤È¤·¤Æ°·¤¤¡¢ + AddOutputFileter INCLUDES .shtml ¤Î¤è¤¦¤Ê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + INCLUDES ¥Õ¥£¥ë¥¿¤ò¥ê¥¯¥¨¥¹¥È¤ËÉղ䵤»¤Þ¤¹¡£ + ModMimeUsePathInfo ¤¬ÀßÄꤵ¤ì¤Ê¤±¤ì¤Ð¡¢ + INCLUDES ¥Õ¥£¥ë¥¿¤ÏÉղ䵤ì¤Þ¤»¤ó¡£

+ +

»²¾È

+ +
+
top
+

MultiviewsMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:MultiViews ¤Ç¤Î¥Þ¥Ã¥Á¥ó¥°¤Î¸¡º÷¤Ë´Þ¤Þ¤»¤ë +¥Õ¥¡¥¤¥ë¤Î¥¿¥¤¥×¤ò»ØÄꤹ¤ë
¹½Ê¸:MultiviewsMatch Any|NegotiatedOnly|Filters|Handlers +[Handlers|Filters]
¥Ç¥Õ¥©¥ë¥È:MultiviewsMatch NegotiatedOnly
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
¸ß´¹À­:2.0.26 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

MultiviewsMatch ¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢ + mod_negotiation ¤Î + Multiviews ¤Ë 3 ¼ïÎà¤Î°Û¤Ê¤ëµóÆ°¤ò¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + Multiviews ¤ò»ÈÍѤ¹¤ë¤È¡¢¥Õ¥¡¥¤¥ë (Îã index.html) + ¤ËÂФ¹¤ë¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¡¢¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤¹¤ë³ÈÄ¥»Ò¤¬¥Ù¡¼¥¹¤ËÉÕ¤¤¤¿¤â¤Î + (index.html.en, index.html.fr ¤ä + index.html.gz) + ¤ò¥Þ¥Ã¥Á¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

NegotiatedOnly ¥ª¥×¥·¥ç¥ó¤Ç¤Ï¡¢¥Ù¡¼¥¹Ì¾¤Ë³¤¯³ÈÄ¥»ÒÁ´¤Æ¤¬ + ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Ç mod_mime + ¤¬Ç§¼±¤¹¤ë³ÈÄ¥»Ò (Îã ʸ»ú¥»¥Ã¥È¡¢¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¡¢¸À¸ì¤ä¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°) + ¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤³¤ì¤ÏÉûºîÍѤκǤ⾯¤Ê¤¤ + ºÇ¤âŪ³Î¤Ê¼ÂÁõ¤Ç¡¢¥Ç¥Õ¥©¥ë¥È¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

¥Ï¥ó¥É¥é¤È¥Õ¥£¥ë¥¿¤ÎξÊý¤â¤·¤¯¤ÏÊÒÊý¤È´ØÏ¢ÉÕ¤±¤é¤ì¤¿³ÈÄ¥»Ò¤ò´Þ¤á¤ë¤Ë¤Ï¡¢ + MultiviewsMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë Handlers, + Filters ¤Þ¤¿¤Ï¤½¤ÎξÊý¤Î¥ª¥×¥·¥ç¥ó¤ò¥»¥Ã¥È¤·¤Þ¤¹¡£ + ¤â¤·Â¾¤Î¾ò·ï¤¬Æ±¤¸¤Ç¤¢¤ì¤Ð¡¢ºÇ¤â¾®¤µ¤¤¥Õ¥¡¥¤¥ë¤¬Á÷¿®¤µ¤ì¤Þ¤¹¡£ + Î㤨¤Ð¡¢500 ʸ»ú¤Î index.html.cgi ¤È 1000 ¥Ð¥¤¥È¤Î + index.html.pl ¤Ç¤¢¤ì¤Ð¡¢.cgi + ¤Î¥Õ¥¡¥¤¥ë¤¬Í¥À褵¤ì¤Þ¤¹¡£.asis ¥Õ¥¡¥¤¥ë¤òÍøÍѤ·¤Æ¤¤¤ë¥æ¡¼¥¶¤Ï¡¢ + .asis ¥Õ¥¡¥¤¥ë¤¬ asis-handler ¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤Æ¤¤¤ë¤È¤­¤Ë¤Ï¡¢ + ¥Ï¥ó¥É¥é¥ª¥×¥·¥ç¥ó¤Î»ÈÍѤò¹¥¤à¤Ç¤·¤ç¤¦¡£

+ +

ºÇ¸å¤Ë¡¢mod_mime ¤¬Ç§¼±¤·¤Ê¤¤³ÈÄ¥»Ò¤Ç¤¢¤í¤¦¤È¤â¡¢ + ¤É¤ó¤Ê³ÈÄ¥»Ò¤Ç¤â¥Þ¥Ã¥Á¤µ¤»¤ë Any ¤¬»ÈÍѤǤ­¤Þ¤¹¡£ + ¤³¤ÎµóÆ°¤Ï Apache 1.3 ¤Î¤È¤­¤ÈƱ¤¸¤â¤Î¤Ç¡¢Í½´ü¤·¤Ê¤¤Æ°ºî¡¢Î㤨¤Ð .old ¤ä + .bak ¥Õ¥¡¥¤¥ë¤È¤¤¤Ã¤¿¥¦¥§¥Ö¥Þ¥¹¥¿¤¬Á÷¿®¤ò°Õ¿Þ¤·¤Æ¤¤¤Ê¤¤ + ¥Õ¥¡¥¤¥ë¤òÁ÷¿®¤¹¤ë¡¢¤È¤¤¤Ã¤¿Æ°ºî¤ò¹Ô¤Ê¤¦²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£

+ +

Î㤨¤Ð¼¡¤ÎÀßÄê¤Ç¤Ï¡¢¥Ï¥ó¥É¥é¤ä¥Õ¥£¥ë¥¿¤¬ Multiviews ¤Ë»²²Ã¤¹¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¤·¡¢Ì¤ÃΤΥե¡¥¤¥ë¤Ï½ü³°¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

+ MultiviewsMatch Handlers Filters +

+ + +

»²¾È

+ +
+
top
+

RemoveCharset ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¤¹¤Ù¤Æ¤Îʸ»ú¥»¥Ã¥È +¤ò²ò½ü¤¹¤ë
¹½Ê¸:RemoveCharset extension [extension] +...
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
¸ß´¹À­:2.0.24 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

RemoveCharset ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤ÏÍ¿¤¨¤é¤ì¤¿³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿Ê¸»ú¥»¥Ã¥È¤ò¼è¤ê¾Ã¤·¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë .htaccess + ¥Õ¥¡¥¤¥ë¤¬¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤ä¥µ¡¼¥Ð¤ÎÀßÄê¥Õ¥¡¥¤¥ë + ¤«¤é·Ñ¾µ¤·¤¿´ØÏ¢ÉÕ¤±¤ò¼è¤ê¾Ã¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð:

+ +

extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£ + ¤Þ¤¿¡¢ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

Îã

+ RemoveCharset .html .shtml +

+ +
+
top
+

RemoveEncoding ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¤¹¤Ù¤Æ¤Î¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥° +¤ò²ò½ü¤¹¤ë
¹½Ê¸:RemoveEncoding extension [extension] +...
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

RemoveEncoding ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + Í¿¤¨¤é¤ì¤¿³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ò¼è¤ê¾Ã¤·¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë .htaccess + ¥Õ¥¡¥¤¥ë¤¬¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤ä¥µ¡¼¥Ð¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤«¤é·Ñ¾µ¤·¤¿´ØÏ¢ÉÕ¤±¤ò + ¼è¤ê¾Ã¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

/foo/.htaccess:

+ AddEncoding x-gzip .gz
+ AddType text/plain .asc
+ <Files *.gz.asc>
+ + RemoveEncoding .gz
+ + </Files> +

+ +

¤³¤ì¤Ï¡¢foo.gz ¤Ï gzip + ¤Ç¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ò»ØÄꤷ¤Þ¤¹¤¬¡¢foo.gz.asc + ¤Ï¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤Ê¤¤¥×¥ì¡¼¥ó¥Æ¥­¥¹¥È¤Î + ¥Õ¥¡¥¤¥ë¤Ç¤¢¤ë¤È¤¤¤¦¤³¤È¤ò»ØÄꤷ¤Þ¤¹¡£

+ +

Ãí°Õ

+

RemoveEncoding ¤Ï + AddEncoding + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¸å¤Ç½èÍý¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢ + Ʊ¤¸¥Ç¥£¥ì¥¯¥È¥ê¤ÎÀßÄêÃæ¤ËξÊý¤¬¸½¤ì¤ë¤È¡¢ + ¸å¼Ô¤Î¸ú²Ì¤¬ÂǤÁ¾Ã¤µ¤ì¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£

+
+ +

extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£ + ¤Þ¤¿¡¢ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +
+
top
+

RemoveHandler ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¤¹¤Ù¤Æ¤Î¥Ï¥ó¥É¥é¤ò +²ò½ü¤¹¤ë
¹½Ê¸:RemoveHandler extension [extension] +...
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

RemoveHandler ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤ÏÍ¿¤¨¤é¤ì¤¿³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¥Ï¥ó¥É¥é¤ò¼è¤ê¾Ã¤·¤Þ¤¹¡£ + ¤³¤ì¤Ë¤è¤ê¡¢¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë .htaccess + ¥Õ¥¡¥¤¥ë¤¬¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤ä¥µ¡¼¥Ð¤ÎÀßÄê¥Õ¥¡¥¤¥ë + ¤«¤é·Ñ¾µ¤·¤¿´ØÏ¢ÉÕ¤±¤ò¼è¤ê¾Ã¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤¿¤È¤¨¤Ð:

+ +

/foo/.htaccess:

+ AddHandler server-parsed .html +

+ +

/foo/bar/.htaccess:

+ RemoveHandler .html +

+ +

¤³¤ì¤Ï¡¢/foo/bar ¥Ç¥£¥ì¥¯¥È¥ê¤Î .html + ¥Õ¥¡¥¤¥ë¤Ï SSI (mod_include ¥â¥¸¥å¡¼¥ë»²¾È) ¤Ç¤Ï¤Ê¤¯¡¢ + ÉáÄ̤Υե¡¥¤¥ë¤È¤·¤Æ°·¤ï¤ì¤ë¤è¤¦¤Ë¤¹¤ë¸ú²Ì¤¬¤¢¤ê¤Þ¤¹¡£ +

+ +

extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£ + ¤Þ¤¿¡¢ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +
+
top
+

RemoveInputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿ÆþÎÏ¥Õ¥£¥ë¥¿¤ò²ò½ü¤¹¤ë
¹½Ê¸:RemoveInputFilter extension [extension] +...
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
¸ß´¹À­:2.0.26 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

RemoveInputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + »ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿ÆþÎÏ¥Õ¥£¥ë¥¿¤ò²ò½ü¤·¤Þ¤¹¡£ + ¤³¤ì¤òÍøÍѤ¹¤ë¤³¤È¤Ç¡¢¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤ä¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤«¤é + ·Ñ¾µ¤·¤¿´ØÏ¢ÉÕ¤±¤ò ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ë¤ª¤¤¤Æ + .htaccess ¥Õ¥¡¥¤¥ë¤Ç¼è¤ê¾Ã¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

extension °ú¿ô¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£¤Þ¤¿¡¢ + ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

»²¾È

+ +
+
top
+

RemoveLanguage ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¸À¸ì¤ò²ò½ü¤¹¤ë
¹½Ê¸:RemoveLanguage extension [extension] +...
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
¸ß´¹À­:2.0.24 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

RemoveLanguage ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + »ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¸À¸ì¤ò²ò½ü¤·¤Þ¤¹¡£ + ¤³¤ì¤òÍøÍѤ¹¤ë¤³¤È¤Ç¡¢¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤ä¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤«¤é + ·Ñ¾µ¤·¤¿´ØÏ¢ÉÕ¤±¤ò ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ë¤ª¤¤¤Æ + .htaccess ¥Õ¥¡¥¤¥ë¤Ç¼è¤ê¾Ã¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

extension °ú¿ô¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£¤Þ¤¿¡¢ + ºÇ½é¤Î¥É¥Ã¥È¤Ï¤Ä¤¤¤Æ¤â¤Ä¤«¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +
+
top
+

RemoveOutputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿½ÐÎÏ¥Õ¥£¥ë¥¿¤ò²ò½ü¤¹¤ë
¹½Ê¸:RemoveOutputFilter extension [extension] +...
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
¸ß´¹À­:2.0.26 °Ê¹ß¤Ç¤Î¤ß»ÈÍѲÄǽ
+

RemoveOutputFilter ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + »ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿½ÐÎÏ¥Õ¥£¥ë¥¿¤ò²ò½ü¤·¤Þ¤¹¡£ + ¤³¤ì¤òÍøÍѤ¹¤ë¤³¤È¤Ç¡¢¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤ä¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë¤«¤é + ·Ñ¾µ¤·¤¿´ØÏ¢ÉÕ¤±¤ò ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥êÆâ¤Ë¤ª¤¤¤Æ + .htaccess ¥Õ¥¡¥¤¥ë¤Ç¼è¤ê¾Ã¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£ + ¤Þ¤¿¡¢ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +

Îã

+ RemoveOutputFilter shtml +

+ +

»²¾È

+ +
+
top
+

RemoveType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤È´ØÏ¢ÉÕ¤±¤é¤ì¤¿¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ò +²ò½ü¤¹¤ë
¹½Ê¸:RemoveType extension [extension] +...
¥³¥ó¥Æ¥­¥¹¥È:¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

RemoveType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÍ¿¤¨¤é¤ì¤¿³ÈÄ¥»Ò¤Î + MIME ¥¿¥¤¥×¤Î´ØÏ¢ÉÕ¤±¤ò¼è¤ê¾Ã¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢ + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë .htaccess + ¥Õ¥¡¥¤¥ë¤¬¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤ä¥µ¡¼¥Ð¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤«¤é·Ñ¾µ¤·¤¿ + ´ØÏ¢ÉÕ¤±¤ò¼è¤ê¾Ã¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤¿¤È¤¨¤Ð:

+ +

/foo/.htaccess:

+ RemoveType .cgi +

+ +

¤³¤ì¤Ï /foo/ ¥Ç¥£¥ì¥¯¥È¥ê°Ê²¼¤Î .cgi + ¥Õ¥¡¥¤¥ë¤ÎÆÃÊ̤ʰ·¤¤¤ò¼è¤ê¾Ã¤·¤Þ¤¹¡£¥Õ¥¡¥¤¥ë¤Ï DefaultType ¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£

+ +

Ãí°Õ

+

RemoveType ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + AddType + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¸å¤Ë½èÍý¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢ + ξÊý¤¬Æ±¤¸¥Ç¥£¥ì¥¯¥È¥ê¤ÎÀßÄêÃæ¤Ë¸½¤ì¤¿¾ì¹ç¡¢ + ¸å¼Ô¤Î¸ú²Ì¤¬ÂǤÁ¾Ã¤µ¤ì¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£

+
+ +

extension ¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤»¤ó¡£ + ¤Þ¤¿¡¢ºÇ½é¤Î¥É¥Ã¥È¤Ï¤¢¤Ã¤Æ¤â¤Ê¤¯¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£

+ +
+
top
+

TypesConfig ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:mime.types ¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ
¹½Ê¸:TypesConfig file-path
¥Ç¥Õ¥©¥ë¥È:TypesConfig conf/mime.types
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:¥Ù¡¼¥¹
¥â¥¸¥å¡¼¥ë:mod_mime
+

TypesConfig ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢MIME + ¥¿¥¤¥×ÀßÄê¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ¤òÀßÄꤷ¤Þ¤¹¡£filename ¤Ï + ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤Ç¤¹¡£ + ¤³¤Î¥Õ¥¡¥¤¥ë¤Ï¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤«¤é¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤Ø¤Î + ¥Ç¥Õ¥©¥ë¥È¤Î¥Þ¥Ã¥Ô¥ó¥°¤òÀßÄꤷ¤Þ¤¹¡£ + ¤Û¤È¤ó¤É¤Î´ÉÍý¼Ô¤Ï¡¢¤è¤¯»È¤ï¤ì¤ë¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò + IANA ¤ËÅÐÏ¿¤µ¤ì¤¿¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤Ë´ØÏ¢ÉÕ¤±¤Æ¤¤¤ë¡¢ + Apache ¤Î mime.types ¥Õ¥¡¥¤¥ë¤ò»È¤¤¤Þ¤¹¡£ + ¸½ºß¤Î°ìÍ÷¤Ï http://www.iana.org/assignments/media-types/index.html + ¤Ç´ÉÍý¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ï¡¢¼çÍפʥá¥Ç¥£¥¢¥¿¥¤¥×¤ÎÄêµÁ¤òÄ󶡤·¤Æ¡¢ + ɬÍפȤ³¤í¤ò AddType ¤Ç + ¾å½ñ¤­¤¹¤ë¡¢¤È¤¤¤¦ÊýË¡¤Ç httpd.conf ¤ò´Êά¤Ë¤·¤Þ¤¹¡£ + mime.types ¤Ï¥µ¡¼¥Ð¤ò¥¢¥Ã¥×¥°¥ì¡¼¥É¤·¤¿¤È¤­¤Ë + ÃÖ¤­´¹¤¨¤é¤ì¤ë¤«¤â¤·¤ì¤Ê¤¤¤Î¤Ç¡¢¤½¤Î¥Õ¥¡¥¤¥ë¤òľÀÜ + ÊÔ½¸¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£

+ +

¥Õ¥¡¥¤¥ë¤Ï¡¢AddType + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô¤ÈƱ¤¸·Á¼°¤Î¹Ô¤Ç¹½À®¤µ¤ì¤Þ¤¹¡£

+ +

+ MIME-type [extension] ... +

+ +

³ÈÄ¥»Ò¤ÎÂçʸ»ú¾®Ê¸»ú¤Ï¶èÊ̤µ¤ì¤Þ¤»¤ó¡£¶õ¹Ô¤ä¥Ï¥Ã¥·¥å (`#') + ¤Ç»Ï¤Þ¤ë¹Ô¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£

+ +
+ (1) IANA ¤Ë´û¤ËÅÐÏ¿¤µ¤ì¤Æ¤¤¤ë¡¢¤¢¤ë¤¤¤Ï (2) + ¹­¤¯¼õ¤±Æþ¤ì¤é¤ì¤Æ¤¤¤Æ¥×¥é¥Ã¥È¥Û¡¼¥à´Ö¤Ç¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë¾×Æͤ¬¤Ê¤¤¡¢ + ¤È¤¤¤¦¾ì¹ç¤Ç¤Ê¤±¤ì¤Ð¡¢ÇÛÉÛÃæ¤Î mime.types + ¥Õ¥¡¥¤¥ë¤Ë¿·¤¿¤Ê¤â¤Î¤òÅÐÏ¿¤¹¤ë¤è¤¦¤Ë + Apache HTTP Server Project ¤Ë¥ê¥¯¥¨¥¹¥È¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + category/x-subtype ¤Î¥ê¥¯¥¨¥¹¥È¤Ï¼«Æ°Åª¤ËµÑ²¼¤µ¤ì¤Þ¤¹¤·¡¢ + ¸À¸ì¤äʸ»ú¥»¥Ã¥È¤Î̾Á°¶õ´Ö¤Ç´û¤Ë»ÈÍѤµ¤ì¤Æ¤¤¤Æ¡¢¾×ÆͤβÄǽÀ­¤Î¤¢¤ë + 2 ʸ»ú¤Î³ÈÄ¥»Ò¤âµÑ²¼¤µ¤ì¤Þ¤¹¡£ +
+ +

»²¾È

+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_mime_magic.html b/docs/manual/mod/mod_mime_magic.html new file mode 100644 index 00000000..f413ffe9 --- /dev/null +++ b/docs/manual/mod/mod_mime_magic.html @@ -0,0 +1,3 @@ +URI: mod_mime_magic.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_mime_magic.html.en b/docs/manual/mod/mod_mime_magic.html.en new file mode 100644 index 00000000..475f2645 --- /dev/null +++ b/docs/manual/mod/mod_mime_magic.html.en @@ -0,0 +1,275 @@ + + + +mod_mime_magic - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_mime_magic

+
+

Available Languages:  en 

+
+ + + +
Description:Determines the MIME type of a file + by looking at a few bytes of its contents
Status:Extension
Module Identifier:mime_magic_module
Source File:mod_mime_magic.c
+

Summary

+ +

This module determines the MIME + type of files in the same way the Unix + file(1) command works: it looks at the first few + bytes of the file. It is intended as a "second line of defense" + for cases that mod_mime can't resolve.

+ +

This module is derived from a free version of the + file(1) command for Unix, which uses "magic + numbers" and other hints from a file's contents to figure out + what the contents are. This module is active only if the magic + file is specified by the MimeMagicFile directive.

+
+ +
top
+
+

Format of the Magic File

+ +

The contents of the file are plain ASCII text in 4-5 + columns. Blank lines are allowed but ignored. Commented lines + use a hash mark (#). The remaining lines are parsed for + the following columns:

+ + + + + + + + + + + + +
ColumnDescription
1byte number to begin checking from
+ ">" indicates a dependency upon the previous + non-">" line
2

type of data to match

+ + + + + + + + + + + + + + + + + + + + + + + + +
bytesingle character
shortmachine-order 16-bit integer
longmachine-order 32-bit integer
stringarbitrary-length string
datelong integer date (seconds since Unix epoch/1970)
beshortbig-endian 16-bit integer
belongbig-endian 32-bit integer
bedatebig-endian 32-bit integer date
leshortlittle-endian 16-bit integer
lelonglittle-endian 32-bit integer
ledatelittle-endian 32-bit integer date
3contents of data to match
4MIME type if matched
5MIME encoding if matched (optional)
+ +

For example, the following magic file lines would recognize + some audio formats:

+ + 
# Sun/NeXT audio data
+0      string      .snd
+>12    belong      1       audio/basic
+>12    belong      2       audio/basic
+>12    belong      3       audio/basic
+>12    belong      4       audio/basic
+>12    belong      5       audio/basic
+>12    belong      6       audio/basic
+>12    belong      7       audio/basic
+>12    belong     23       audio/x-adpcm
+ +

Or these would recognize the difference between *.doc + files containing Microsoft Word or FrameMaker documents. (These are + incompatible file formats which use the same file suffix.)

+ + 
# Frame
+0  string  \<MakerFile        application/x-frame
+0  string  \<MIFFile          application/x-frame
+0  string  \<MakerDictionary  application/x-frame
+0  string  \<MakerScreenFon   application/x-frame
+0  string  \<MML              application/x-frame
+0  string  \<Book             application/x-frame
+0  string  \<Maker            application/x-frame
+
+# MS-Word
+0  string  \376\067\0\043            application/msword
+0  string  \320\317\021\340\241\261  application/msword
+0  string  \333\245-\0\0\0           application/msword
+ +

An optional MIME encoding can be included as a fifth column. + For example, this can recognize gzipped files and set the + encoding for them.

+ + 
# gzip (GNU zip, not to be confused with
+#       [Info-ZIP/PKWARE] zip archiver)
+
+0  string  \037\213  application/octet-stream  x-gzip
+
top
+
+

Performance Issues

+

This module is not for every system. If your system is barely + keeping up with its load or if you're performing a web server + benchmark, you may not want to enable this because the + processing is not free.

+ +

However, an effort was made to improve the performance of + the original file(1) code to make it fit in a busy web + server. It was designed for a server where there are thousands of users + who publish their own documents. This is probably very common + on intranets. Many times, it's helpful if the server can make + more intelligent decisions about a file's contents than the + file name allows ...even if just to reduce the "why doesn't my + page work" calls when users improperly name their own files. + You have to decide if the extra work suits your + environment.

+
top
+
+

Notes

+

The following notes apply to the mod_mime_magic + module and are included here for compliance with contributors' + copyright restrictions that require their acknowledgment.

+ +
+

mod_mime_magic: MIME type lookup via file magic numbers
+ Copyright (c) 1996-1997 Cisco Systems, Inc.

+ +

This software was submitted by Cisco Systems to the Apache Group + in July 1997. Future revisions and derivatives of this source code + must acknowledge Cisco Systems as the original contributor of this + module. All other licensing and usage conditions are those of the + Apache Group.

+ +

Some of this code is derived from the free version of the file + command originally posted to comp.sources.unix. Copyright info for + that program is included below as required.

+
+ +
+

- Copyright (c) Ian F. Darwin, 1987. Written by Ian F. Darwin.

+ +

This software is not subject to any license of the American + Telephone and Telegraph Company or of the Regents of the University + of California.

+ +

Permission is granted to anyone to use this software for any + purpose on any computer system, and to alter it and redistribute it + freely, subject to the following restrictions:

+ +
    +
  1. The author is not responsible for the consequences of use of + this software, no matter how awful, even if they arise from flaws + in it.
    2. + +
  2. The origin of this software must not be misrepresented, either + by explicit claim or by omission. Since few users ever read + sources, credits must appear in the documentation.
    3. + +
  3. Altered versions must be plainly marked as such, and must not + be misrepresented as being the original software. Since few users + ever read sources, credits must appear in the documentation.
    4. + +
  4. This notice may not be removed or altered.
    5. +
+
+ +
+

For compliance with Mr Darwin's terms: this has been very + significantly modified from the free "file" command.

+ +
    +
  • all-in-one file for compilation convenience when moving from + one version of Apache to the next.
    • + +
  • Memory allocation is done through the Apache API's pool + structure.
    • + +
  • All functions have had necessary Apache API request or server + structures passed to them where necessary to call other Apache API + routines. (i.e., usually for logging, files, or memory + allocation in itself or a called function.)
    • + +
  • struct magic has been converted from an array to a single-ended + linked list because it only grows one record at a time, it's only + accessed sequentially, and the Apache API has no equivalent of + realloc().
    • + +
  • Functions have been changed to get their parameters from the + server configuration instead of globals. (It should be reentrant + now but has not been tested in a threaded environment.)
    • + +
  • Places where it used to print results to stdout now saves them + in a list where they're used to set the MIME type in the Apache + request record.
    • + +
  • Command-line flags have been removed since they will never be + used here.
    • +
+
+
+
top
+

MimeMagicFile Directive

+ + + + + + +
Description:Enable MIME-type determination based on file contents +using the specified magic file
Syntax:MimeMagicFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_mime_magic
+

The MimeMagicFile directive can be used to + enable this module, the default file is distributed at + conf/magic. Non-rooted paths are relative to the + ServerRoot. Virtual hosts will use + the same file as the main server unless a more specific setting is + used, in which case the more specific setting overrides the main + server's file.

+ +

Example

+ MimeMagicFile conf/magic +

+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_negotiation.html b/docs/manual/mod/mod_negotiation.html new file mode 100644 index 00000000..c4e86d3a --- /dev/null +++ b/docs/manual/mod/mod_negotiation.html @@ -0,0 +1,7 @@ +URI: mod_negotiation.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_negotiation.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_negotiation.html.en b/docs/manual/mod/mod_negotiation.html.en new file mode 100644 index 00000000..41bdfae3 --- /dev/null +++ b/docs/manual/mod/mod_negotiation.html.en @@ -0,0 +1,307 @@ + + + +mod_negotiation - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_negotiation

+
+

Available Languages:  en  | + ja 

+
+ + + +
Description:Provides for content negotiation
Status:Base
Module Identifier:negotiation_module
Source File:mod_negotiation.c
+

Summary

+ +

Content negotiation, or more accurately content selection, is + the selection of the document that best matches the clients + capabilities, from one of several available documents. There + are two implementations of this.

+ +
    +
  • A type map (a file with the handler + type-map) which explicitly lists the files + containing the variants.
    • + +
  • A MultiViews search (enabled by the MultiViews + Options), where the server does + an implicit filename pattern match, and choose from amongst the + results.
    • +
+
+ +
top
+
+

Type maps

+

A type map has a format similar to RFC822 mail headers. It + contains document descriptions separated by blank lines, with + lines beginning with a hash character ('#') treated as + comments. A document description consists of several header + records; records may be continued on multiple lines if the + continuation lines start with spaces. The leading space will be + deleted and the lines concatenated. A header record consists of + a keyword name, which always ends in a colon, followed by a + value. Whitespace is allowed between the header name and value, + and between the tokens of value. The headers allowed are:

+ +
+
Content-Encoding:
+
The encoding of the file. Apache only recognizes + encodings that are defined by an AddEncoding directive. + This normally includes the encodings x-compress + for compress'd files, and x-gzip for gzip'd + files. The x- prefix is ignored for encoding + comparisons.
+ +
Content-Language:
+
The language(s) of the variant, as an Internet standard + language tag (RFC 1766). An example is en, + meaning English. If the variant contains more than one + language, they are separated by a comma.
+ +
Content-Length:
+
The length of the file, in bytes. If this header is not + present, then the actual length of the file is used.
+ +
Content-Type:
+ +
+ The MIME media type of + the document, with optional parameters. Parameters are + separated from the media type and from one another by a + semi-colon, with a syntax of name=value. Common + parameters include: + +
+
level
+
an integer specifying the version of the media type. + For text/html this defaults to 2, otherwise + 0.
+ +
qs
+
a floating-point number with a value in the range 0.0 + to 1.0, indicating the relative 'quality' of this variant + compared to the other available variants, independent of + the client's capabilities. For example, a jpeg file is + usually of higher source quality than an ascii file if it + is attempting to represent a photograph. However, if the + resource being represented is ascii art, then an ascii + file would have a higher source quality than a jpeg file. + All qs values are therefore specific to a given + resource.
+
+ +

Example

+ Content-Type: image/jpeg; qs=0.8 +

+
+ +
URI:
+
uri of the file containing the variant (of the given + media type, encoded with the given content encoding). These + are interpreted as URLs relative to the map file; they must + be on the same server (!), and they must refer to files to + which the client would be granted access if they were to be + requested directly.
+ +
Body:
+
New in Apache 2.0, the actual content of the resource may + be included in the type-map file using the Body header. This + header must contain a string that designates a delimiter for + the body content. Then all following lines in the type map + file will be considered part of the resource body until the + delimiter string is found. + +

Example:

+ Body:----xyz----
+ <html>
+ <body>
+ <p>Content of the page.</p>
+ </body>
+ </html>
+ ----xyz---- +

+
+
+
top
+
+

MultiViews

+

A MultiViews search is enabled by the MultiViews + Options. If the server receives a + request for /some/dir/foo and + /some/dir/foo does not exist, then the + server reads the directory looking for all files named + foo.*, and effectively fakes up a type map which + names all those files, assigning them the same media types and + content-encodings it would have if the client had asked for one + of them by name. It then chooses the best match to the client's + requirements, and returns that document.

+ +

The MultiViewsMatch + directive configures whether Apache will consider files + that do not have content negotiation meta-information assigned + to them when choosing files.

+
+
top
+

CacheNegotiatedDocs Directive

+ + + + + + + + +
Description:Allows content-negotiated documents to be +cached by proxy servers
Syntax:CacheNegotiatedDocs On|Off
Default:CacheNegotiatedDocs Off
Context:server config, virtual host
Status:Base
Module:mod_negotiation
Compatibility:The syntax changed in version 2.0.
+

If set, this directive allows content-negotiated documents + to be cached by proxy servers. This could mean that clients + behind those proxys could retrieve versions of the documents + that are not the best match for their abilities, but it will + make caching more efficient.

+ +

This directive only applies to requests which come from + HTTP/1.0 browsers. HTTP/1.1 provides much better control over + the caching of negotiated documents, and this directive has no + effect in responses to HTTP/1.1 requests.

+ +

Prior to version 2.0, + CacheNegotiatedDocs did not take an + argument; it was turned on by the presence of the directive by + itself.

+ +
+
top
+

ForceLanguagePriority Directive

+ + + + + + + + + +
Description:Action to take if a single acceptable document is not +found
Syntax:ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]
Default:ForceLanguagePriority Prefer
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_negotiation
Compatibility:Available in version 2.0.30 and later
+

The ForceLanguagePriority directive uses + the given LanguagePriority to satisfy + negotation where the server could otherwise not return a single + matching document.

+ +

ForceLanguagePriority Prefer uses + LanguagePriority to serve a one valid result, rather + than returning an HTTP result 300 (MULTIPLE CHOICES) when there + are several equally valid choices. If the directives below were + given, and the user's Accept-Language header assigned + en and de each as quality .500 + (equally acceptable) then the first matching variant, en, + will be served.

+ +

+ LanguagePriority en fr de
+ ForceLanguagePriority Prefer +

+ +

ForceLanguagePriority Fallback uses + LanguagePriority to + serve a valid result, rather than returning an HTTP result 406 + (NOT ACCEPTABLE). If the directives below were given, and the user's + Accept-Language only permitted an es + language response, but such a variant isn't found, then the first + variant from the LanguagePriority list below will be served.

+ +

+ LanguagePriority en fr de
+ ForceLanguagePriority Fallback +

+ +

Both options, Prefer and Fallback, may be + specified, so either the first matching variant from LanguagePriority will be served if + more than one variant is acceptable, or first available document will + be served if none of the variants matched the client's acceptable list + of languages.

+ +

See also

+ +
+
top
+

LanguagePriority Directive

+ + + + + + + +
Description:The precendence of language variants for cases where +the client does not express a preference
Syntax:LanguagePriority MIME-lang [MIME-lang] +...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_negotiation
+

The LanguagePriority sets the precedence + of language variants for the case where the client does not + express a preference, when handling a MultiViews request. The list + of MIME-lang are in order of decreasing preference.

+ +

Example:

+ LanguagePriority en fr de +

+ +

For a request for foo.html, where + foo.html.fr and foo.html.de both + existed, but the browser did not express a language preference, + then foo.html.fr would be returned.

+ +

Note that this directive only has an effect if a 'best' + language cannot be determined by any other means or the ForceLanguagePriority directive + is not None. In general, the client determines the + language preference, not the server.

+ +

See also

+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_negotiation.html.ja.euc-jp b/docs/manual/mod/mod_negotiation.html.ja.euc-jp new file mode 100644 index 00000000..11b29147 --- /dev/null +++ b/docs/manual/mod/mod_negotiation.html.ja.euc-jp @@ -0,0 +1,302 @@ + + + +mod_negotiation - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_negotiation

+
+

Available Languages:  en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó + µ¡Ç½¤òÄ󶡤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:negotiation_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_negotiation.c
+

³µÍ×

+ +

¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¡¢¤è¤êÀµ³Î¤Ë¤Ï¥³¥ó¥Æ¥ó¥Ä¤ÎÁªÂòµ¡Ç½¤Ï¡¢ + Ê£¿ôÍÑ°Õ¤µ¤ì¤Æ¤¤¤ë¥É¥­¥å¥á¥ó¥È¤«¤é¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÎǽÎϤ˰ìÈÖ¹ç¤Ã¤¿ + ¥É¥­¥å¥á¥ó¥È¤òÁªÂò¤¹¤ëµ¡Ç½¤Ç¤¹¡£¤³¤Î¼ÂÁõ¤ÏÆó¤Ä¤¢¤ê¤Þ¤¹¡£

+ +
    +
  • ¥¿¥¤¥×¥Þ¥Ã¥× (type-map + ¥Ï¥ó¥É¥é¤Ç°·¤ï¤ì¤ë¥Õ¥¡¥¤¥ë)¡£¤³¤ì¤Ï variants + ¤ò´Þ¤ó¤Ç¤¤¤ë¥Õ¥¡¥¤¥ë¤òÌÀ¼¨Åª¤Ë»ØÄꤷ¤Þ¤¹¡£
    • + +
  • MultiViews ¤Îõº÷ (MultiViews Option ¤ÇÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹)¡£ + ¥µ¡¼¥Ð¤¬°ÅÌÛ¤ÎÆâ¤Ë¥Õ¥¡¥¤¥ë̾¤Î¥Ñ¥¿¡¼¥ó¥Þ¥Ã¥Á¤ò¹Ô¤Ê¤¤¡¢ + ¤½¤Î·ë²Ì¤«¤éÁªÂò¤·¤Þ¤¹¡£
    • +
+
+ +
top
+
+

¥¿¥¤¥×¥Þ¥Ã¥×

+

¥¿¥¤¥×¥Þ¥Ã¥×¤Ï RFC 822 ¤Î¥á¡¼¥ë¥Ø¥Ã¥À¤ËÎà»÷¤·¤¿½ñ¼°¤Ç¤¹¡£ + ¥É¥­¥å¥á¥ó¥È¤Îµ­½Ò¤¬¶õ¹Ô¤ÇʬΥ¤µ¤ì¤Æ½ñ¤«¤ì¤Æ¤¤¤Æ¡¢¥Ï¥Ã¥·¥åʸ»ú + ('#') ¤Ç»Ï¤Þ¤ë¹Ô¤Ï¥³¥á¥ó¥È¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£ + ¥É¥­¥å¥á¥ó¥È¤ÎÀâÌÀ¤ÏÊ£¿ô¤Î¥Ø¥Ã¥À¥ì¥³¡¼¥É¤«¤é¹½À®¤µ¤ì¤Þ¤¹¡£ + ¥ì¥³¡¼¥É¤Ï¡¢Â³¤­¤Î¹Ô¤¬¶õÇò¤Ç»Ï¤Þ¤Ã¤Æ¤¤¤ë¤ÈÊ£¿ô¤Î¹Ô¤Ë¤Þ¤¿¤¬¤ê¤Þ¤¹¡£ + ºÇ½é¤Î¶õÇò¤¬¾Ãµî¤µ¤ì¤Æ¡¢Á°¤Î¹Ô¤È¤Ä¤Ê¤²¤Æ 1 ¹Ô¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£ + ¥Ø¥Ã¥À¥ì¥³¡¼¥É¤Ï¥­¡¼¥ï¡¼¥É̾¤Î¸å¤ËÃͤ¬Â³¤¯¤È¤¤¤¦·Á¼°¤Ç¡¢ + ¥­¡¼¥ï¡¼¥É̾¤Ï¾ï¤Ë¥³¥í¥ó¤Ç½ª¤ï¤ê¤Þ¤¹¡£¶õÇò¤Ï¥Ø¥Ã¥À̾¤ÈÃͤδ֡¢ + ÃͤΥȡ¼¥¯¥ó¤Î´Ö¤ËÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + »ÈÍѲÄǽ¤Ê¥Ø¥Ã¥À¤Ï°Ê²¼¤Î¤È¤ª¤ê¤Ç¤¹:

+ +
+
Content-Encoding:
+
¥Õ¥¡¥¤¥ë¤Î¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¡£Apache ¤Ï AddEncoding ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤ÇÄêµÁ¤µ¤ì¤¿¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤À¤±¤òǧ¼±¤·¤Þ¤¹¡£Ä̾ï compress + ¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î¤¿¤á¤Î x-compress ¤È gzip + ¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î¤¿¤á¤Î x-gzip ¤ò´Þ¤ß¤Þ¤¹¡£ + ¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤ÎÈæ³Ó¤ò¤¹¤ë¤È¤­¤Ï¡¢ÀÜƬ¼­ x- + ¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£
+ +
Content-Language:
+
¥¤¥ó¥¿¡¼¥Í¥Ã¥Èɸ½à¤Î¸À¸ì¥¿¥° + (RFC 1766) + ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë¸À¸ì¤Î¼ïÎà¡£Î㤨¤Ð¡¢en + ¤Ï±Ñ¸ì¤òɽ¤·¤Þ¤¹¡£ + Ê£¿ô¤Î¸À¸ì¤¬³ÊǼ¤µ¤ì¤ë¾ì¹ç¤Ï¥³¥ó¥Þ¤Ç¶èÀÚ¤é¤ì¤Þ¤¹¡£
+ +
Content-Length:
+
¥Õ¥¡¥¤¥ë¤ÎŤµ (¥Ð¥¤¥È¿ô)¡£ + ¤³¤Î¥Ø¥Ã¥À¤¬¤Ê¤¤¾ì¹ç¡¢¥Õ¥¡¥¤¥ë¤Î¼ÂºÝ¤ÎŤµ¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£
+ +
Content-Type:
+
¥É¥­¥å¥á¥ó¥È¤Î MIME + ¥á¥Ç¥£¥¢¥¿¥¤¥×¡¢¥ª¥×¥·¥ç¥Ê¥ë¤Ê¥Ñ¥é¥á¡¼¥¿ÉÕ¤­¡£¥Ñ¥é¥á¡¼¥¿¤Î¹½Ê¸¤Ï + name=value + ¤Ç¡¢¥á¥Ç¥£¥¢¥¿¥¤¥×¤ä¾¤Î¥Ñ¥é¥á¡¼¥¿¤È¤Ï¥»¥ß¥³¥í¥ó¤ÇʬΥ¤µ¤ì¤Þ¤¹¡£ + ¶¦Ä̤Υѥé¥á¡¼¥¿¤Ï°Ê²¼¤Î¤È¤ª¤ê: + +
+
level
+
¥á¥Ç¥£¥¢¥¿¥¤¥×¤Î¥Ð¡¼¥¸¥ç¥ó¤ò¼¨¤¹À°¿ô¡£ + text/html ¤Ç¤Ï 2 ¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¡¢¤½¤Î¾¤Î¾ì¹ç¤Ï + 0 ¤¬¥Ç¥Õ¥©¥ë¥È¤Ç¤¹¡£
+ +
qs
+
¥¯¥é¥¤¥¢¥ó¥È¤ÎǽÎϤ˴ط¸¤Ê¤¯¡¢variant + ¤ò¾¤ÈÈæ³Ó¤·¤¿¤È¤­¤ÎÁêÂÐŪ¤Ê¡ÖÉʼÁ¡×¤Ç¡¢0.0 ¤«¤é 1.0 + ¤ÎÈϰϤÎÉâÆ°ÅÀ¾®¿ô¡£ + Î㤨¤Ð¡¢¼Ì¿¿¤òɽ¸½¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤È¤­¤ÏÉáÄÌ¤Ï JPEG + ¥Õ¥¡¥¤¥ë¤ÎÊý¤¬ ASCII ¥Õ¥¡¥¤¥ë¤è¤ê¤â¹â¤¤ÉʼÁ¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤·¤«¤·¡¢¥ê¥½¡¼¥¹¤¬ ASCII ¥¢¡¼¥È¤Çɽ¸½¤µ¤ì¤Æ¤¤¤ë¤È¤­¤Ï¡¢ASCII + ¥Õ¥¡¥¤¥ë¤ÎÊý¤¬ JPEG + ¥Õ¥¡¥¤¥ë¤è¤ê¤â¹â¤¤ÉʼÁ¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤Î¤è¤¦¤Ë¡¢qs + ¤Ï¥ê¥½¡¼¥¹Ëè¤ËÆÃÍ­¤ÎÃͤò¼è¤ê¤Þ¤¹¡£ +
+
+ +

Îã

+ Content-Type: image/jpeg; qs=0.8 +

+
+ +
URI:
+
(»ØÄê¤Î¥á¥Ç¥£¥¢¥¿¥¤¥×¡¢¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Î) variant ¤Î + ¥Õ¥¡¥¤¥ë¤Î uri. ¤³¤ì¤Ï¡¢¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤«¤é¤ÎÁêÂÐ URL ¤È¤·¤Æ + ²ò¼á¤µ¤ì¤Þ¤¹¡£Æ±¤¸¥µ¡¼¥Ð¤Ë¸ºß¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤º¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬ + ľÀܥꥯ¥¨¥¹¥È¤·¤¿¤È¤­¤Ë¥¢¥¯¥»¥¹¤òµö²Ä¤µ¤ì¤ë¤â¤Î¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
+ +
Body:
+
Apache 2.0 ¤Ç¿·Àߤµ¤ì¤¿¤³¤Î Body ¥Ø¥Ã¥À¤ò»È¤Ã¤Æ¡¢ + ¥ê¥½¡¼¥¹¤Î¼ÂºÝ¤ÎÆâÍƤò¥¿¥¤¥×¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¥Ø¥Ã¥À¤ÏËÜʸ¤ÎÆâÍƤζèÀÚ¤ê¤È¤Ê¤ëʸ»úÎó¤Ç»Ï¤Þ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¥¿¥¤¥×¥Þ¥Ã¥×¥Õ¥¡¥¤¥ë¤Î³¤¯¹Ô¤Ï¡¢¶èÀÚ¤êʸ»úÎ󤬸«¤Ä¤«¤ë¤Þ¤Ç¡¢ + ¥ê¥½¡¼¥¹¤ÎËÜʸ¤Ë¤Ê¤ê¤Þ¤¹¡£ + +

Example:

+ Body:----xyz----
+ <html>
+ <body>
+ <p>Content of the page.</p>
+ </body>
+ </html>
+ ----xyz---- +

+
+
+
top
+
+

MultiViews

+

MultiViews õº÷¤Ï¡¢Multiviews Options ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤êÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤¬ /some/dir/foo + ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤ê¡¢/some/dir/foo ¤¬Â¸ºß + ¤·¤Ê¤¤¾ì¹ç¡¢¥µ¡¼¥Ð¤Ï¥Ç¥£¥ì¥¯¥È¥ê¤òÆɤó¤Ç¡¢ + foo.* ¤Ë¤¢¤Æ¤Ï¤Þ¤ëÁ´¤Æ¤Î¥Õ¥¡¥¤¥ë¤òõ¤·¡¢ + »ö¼Â¾å¤½¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤ò¥Þ¥Ã¥×¤¹¤ë¥¿¥¤¥×¥Þ¥Ã¥×¤òºî¤ê¤Þ¤¹¡£ + ¤½¤Î¤È¤­¡¢¥á¥Ç¥£¥¢¥¿¥¤¥×¤È¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥°¤Ï¡¢ + ¤½¤Î¥Õ¥¡¥¤¥ë̾¤òľÀÜ»ØÄꤷ¤¿¤È¤­¤ÈƱ¤¸¤â¤Î¤¬³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£ + ¤½¤ì¤«¤é¥¯¥é¥¤¥¢¥ó¥È¤ÎÍ×µá¤Ë°ìÈֹ礦¤â¤Î¤òÁª¤Ó¡¢ + ¤½¤Î¥É¥­¥å¥á¥ó¥È¤òÊÖ¤·¤Þ¤¹¡£

+ +

¥Õ¥¡¥¤¥ë¤òÁªÂò¤¹¤ëºÝ¤Ë¡¢´ØÏ¢¤¹¤ë¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î + ¥á¥¿¾ðÊó¤ò»ý¤¿¤Ê¤¤¥Õ¥¡¥¤¥ë¤Ë¤Ä¤¤¤Æ¡¢È½Äê¤ò¹Ô¤¦¤«¤É¤¦¤«¤ò + MultiViewsMatch + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤷ¤Þ¤¹¡£

+
+
top
+

CacheNegotiatedDocs ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤µ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤ò¥×¥í¥­¥·¥µ¡¼¥Ð¤¬ +¥­¥ã¥Ã¥·¥å¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë
¹½Ê¸:CacheNegotiatedDocs On|Off
¥Ç¥Õ¥©¥ë¥È:CacheNegotiatedDocs Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_negotiation
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.0¤Ç¹½Ê¸¤¬ÊѤï¤ê¤Þ¤·¤¿
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó + ¤ò¤·¤¿·ë²Ì¤Î¥É¥­¥å¥á¥ó¥È¤Î¥­¥ã¥Ã¥·¥å¤òµö²Ä¤·¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥×¥í¥­¥·¤Î¸å¤í¤Ë¤¤¤ë¥¯¥é¥¤¥¢¥ó¥È¤¬Ç½ÎϤ˰ìÈÖ¹ç¤Ã¤¿ + ¥É¥­¥å¥á¥ó¥È¤Ç¤Ï¤Ê¤¯¡¢ + ¥­¥ã¥Ã¥·¥å¤ò¤è¤ê¸ú²ÌŪ¤Ë¤¹¤ë¤â¤Î¤òÆÀ¤ë²ÄǽÀ­¤¬¤¢¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï HTTP/1.0 ¥Ö¥é¥¦¥¶¤«¤é¤Î¥ê¥¯¥¨¥¹¥È + ¤Î¤ß¤ËŬÍѤµ¤ì¤Þ¤¹¡£HTTP/1.1 ¤Ï¡¢ + ¸ò¾Ä¤µ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤Î¥­¥ã¥Ã¥·¥å¤ËÂФ·¤Æ¤º¤Ã¤È¤è¤¤À©¸æ¤¬²Äǽ¤Ê¤Î¤Ç¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï HTTP/1.1 ¤Î¥ê¥¯¥¨¥¹¥È¤Ë¤Ï±Æ¶Á¤·¤Þ¤»¤ó¡£

+

2.0 ¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢ + CacheNegotiatedDocs ¤Ï°ú¿ô¤ò¼è¤é¤º¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Â¸ºß¤¹¤ë¤³¤È¤Ç on ¤ÎÆ°ºî¤ò¤·¤Æ¤¤¤Þ¤·¤¿¡£

+ +
+
top
+

ForceLanguagePriority ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:Í×µá¤Ë¹ç¤¦Ã±ÆȤΥɥ­¥å¥á¥ó¥È¤¬¸«¤Ä¤«¤é¤Ê¤«¤Ã¤¿¤È¤­¤Ë¹Ô¤Ê¤¦¤³¤È¤ò»ØÄê +
¹½Ê¸:ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback]
¥Ç¥Õ¥©¥ë¥È:ForceLanguagePriority Prefer
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_negotiation
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.0.30 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

ForceLanguagePriority ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + Í×µá¤Ë¹ç¤¦¥É¥­¥å¥á¥ó¥È¤ò°ì¤Ä¤À¤±ÊÖ¤¹¤³¤È¤¬¤Ç¤­¤Ê¤¤¤È¤­¤Ë¡¢ + LanguagePriority + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î·ë²Ì¤òÊÖ¤·¤Þ¤¹¡£

+ +

ForceLanguagePriority Prefer ¤Ï¡¢Æ±Åù¤ÎÁªÂò»è¤¬ + ¤¤¤¯¤Ä¤«¤¢¤ë¤È¤­¤Ë¡¢HTTP ¤Î 300 (MULTIPLE CHOICES) ¤òÊÖ¤¹Âå¤ï¤ê¤Ë¡¢ + LanguagePriority ¤ò»È¤Ã¤Æ°ì¤Ä¤À¤±¥É¥­¥å¥á¥ó¥È¤òÊÖ¤¹¤è¤¦¤Ë + ¤·¤Þ¤¹¡£°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬»ØÄꤵ¤ì¤Æ¤¤¤Æ¡¢¥æ¡¼¥¶¤Î Accept-Language + ¥Ø¥Ã¥À¤Ç¤Ï en ¤È de ¤ÎÉʼÁ¤¬¶¦¤Ë + .500 (Ʊ¤¸¤¯¤é¤¤µöÍÆ) ¤Ç¤¢¤ë¤È¤­¤Ï¡¢ + ºÇ½é¤Ë¥Þ¥Ã¥Á¤¹¤ë variant ¤Î en ¤¬Á÷¤é¤ì¤Þ¤¹¡£

+ +

+ LanguagePriority en fr de
+ ForceLanguagePriority Prefer +

+ +

ForceLanguagePriority Fallback ¤Ç¤Ï¡¢HTTP 406 + (NOT ACCEPTABLE) ¤òÁ÷¿®¤¹¤ëÂå¤ï¤ê¤Ë¡¢ + LanguagePriority + ¤¬Àµ¤·¤¤·ë²Ì¤òÁ÷¤ê¤Þ¤¹¡£ + °Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬»ØÄꤵ¤ì¤Æ¤¤¤Æ¡¢¥æ¡¼¥¶¤Î Accept-Language + ¤¬ es ¸À¸ì¤Î¤ß¤òµö²Ä¤·¤Æ¤¤¤Æ¡¢¤µ¤é¤Ë¤½¤Î¤è¤¦¤Ê variant ¤¬¤Ê¤¤¤È¤­¤Ë¤Ï¡¢ + °Ê²¼¤Î LanguagePriority + ¤Î¥ê¥¹¥È¤ÎºÇ½é¤Î variant ¤¬Á÷¤ì¤ì¤Þ¤¹¡£

+ +

+ LanguagePriority en fr de
+ ForceLanguagePriority Fallback +

+ +

Prefer ¤È Fallback ¤ÎξÊý¤Î¥ª¥×¥·¥ç¥ó¤ò + Ʊ»þ¤Ë»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢Ê£¿ô¤Î variant ¤¬¤¢¤ë¤È¤­¤Ï + LanguagePriority ¤ÎºÇ½é¤Î + variant ¤¬Á÷¤é¤ì¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÎµöÍƸÀ¸ì¤Ë¹ç¤¦ vaiant ¤¬¤Ê¤¤¤È¤­¤Ï + ¸ºß¤¹¤ë¥É¥­¥å¥á¥ó¥È¤ÇºÇ½é¤Î¤â¤Î¤¬Á÷¤é¤ì¤ë¡¢¤È¤¤¤¦Íͤˤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

LanguagePriority ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤¬Í¥ÀèÅÙ¤ò¼¨¤µ¤Ê¤«¤Ã¤¿¤È¤­¤Î¸À¸ì¤Î variant ¤ÎÍ¥ÀèÅÙ¤ò +»ØÄê
¹½Ê¸:LanguagePriority MIME-lang [MIME-lang] +...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_negotiation
+

LanguagePriority ¤Ï¡¢MultiViews + ¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤È¤­¤Ë¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬Í¥Àè½ç°Ì¤òÄ󶡤·¤Æ¤¤¤Ê¤¤¾ì¹ç¤Î + ¸À¸ì¤ÎÍ¥Àè½ç°Ì¤òÀßÄꤷ¤Þ¤¹¡£MIME-lang + ¤Î¥ê¥¹¥È¤¬Í¥ÀèÅ٤ι߽ç¤ËʤӤޤ¹¡£

+ +

Example:

+ LanguagePriority en fr de +

+ +

foo.html ¤¬¥ê¥¯¥¨¥¹¥È¤µ¤ì¡¢foo.html.fr + ¤È foo.html.de ¤¬Î¾Êý¸ºß¤·¡¢ + ¥Ö¥é¥¦¥¶¤¬¸À¸ì¤ÎÍ¥Àè½ç°Ì¤òÄ󶡤·¤Æ¤Ê¤¤¾ì¹ç¤Ï + foo.html.fr ¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¾¤ÎÊýË¡¤Ç¡ÖºÇÁ±¡× + ¤Î¸À¸ì¤¬·èÄê¤Ç¤­¤Ê¤¤¤È¤­¤«¡¢ForceLanguagePriority ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + None °Ê³°¤Î¤È¤­¤Ë¤Î¤ß¸ú²Ì¤¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + °ìÈÌŪ¤Ë¤Ï¡¢¥µ¡¼¥Ð¦¤Ç¤Ï¤Ê¤¯¥¯¥é¥¤¥¢¥ó¥È¦¤Ç¹¥¤ß¤Î¸À¸ì¤ò·èÄꤷ¤Þ¤¹¡£

+ +

»²¾È

+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_nw_ssl.html b/docs/manual/mod/mod_nw_ssl.html new file mode 100644 index 00000000..24adb0f8 --- /dev/null +++ b/docs/manual/mod/mod_nw_ssl.html @@ -0,0 +1,3 @@ +URI: mod_nw_ssl.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_nw_ssl.html.en b/docs/manual/mod/mod_nw_ssl.html.en new file mode 100644 index 00000000..bb85e929 --- /dev/null +++ b/docs/manual/mod/mod_nw_ssl.html.en @@ -0,0 +1,97 @@ + + + +mod_nw_ssl - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_nw_ssl

+
+

Available Languages:  en 

+
+ + + + +
Description:Enable SSL encryption for NetWare
Status:Base
Module Identifier:nwssl_module
Source File:mod_nw_ssl.c
Compatibility:NetWare only
+

Summary

+ +

This module enables SSL encryption for a specified port. It + takes advantage of the SSL encryption functionality that is + built into the NetWare operating system.

+
+ + +
top
+

NWSSLTrustedCerts Directive

+ + + + + + +
Description:List of additional client certificates
Syntax:NWSSLTrustedCerts filename [filename] ...
Context:server config
Status:Base
Module:mod_nw_ssl
+

Specifies a list of client certificate files (DER format) + that are used when creating a proxied SSL connection. Each + client certificate used by a server must be listed separately + in its own .der file.

+ +
+
top
+

NWSSLUpgradeable Directive

+ + + + + + +
Description:Allows a connection to be upgraded to an SSL connection upon request
Syntax:NWSSLUpgradeable [IP-address:]portnumber
Context:server config
Status:Base
Module:mod_nw_ssl
+

Allow a connection that was created on the specified address + and/or port to be upgraded to an SSL connection upon request from + the client. The address and/or port must have already be defined + previously with a Listen + directive.

+ +
+
top
+

SecureListen Directive

+ + + + + + +
Description:Enables SSL encryption for the specified port
Syntax:SecureListen [IP-address:]portnumber +Certificate-Name [MUTUAL]
Context:server config
Status:Base
Module:mod_nw_ssl
+

Specifies the port and the eDirectory based certificate name + that will be used to enable SSL encryption. An optional third + parameter also enables mutual authentication.

+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy.html b/docs/manual/mod/mod_proxy.html new file mode 100644 index 00000000..2e413ab6 --- /dev/null +++ b/docs/manual/mod/mod_proxy.html @@ -0,0 +1,7 @@ +URI: mod_proxy.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_proxy.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en new file mode 100644 index 00000000..de1253cc --- /dev/null +++ b/docs/manual/mod/mod_proxy.html.en @@ -0,0 +1,1131 @@ + + + +mod_proxy - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_proxy

+
+

Available Languages:  en  | + ja 

+
+ + + +
Description:HTTP/1.1 proxy/gateway server
Status:Extension
Module Identifier:proxy_module
Source File:mod_proxy.c
+

Summary

+ +

Warning

+

Do not enable proxying with ProxyRequests until you have secured your server. Open proxy servers are dangerous both to your + network and to the Internet at large.

+
+ +

This module implements a proxy/gateway for Apache. It implements + proxying capability for AJP13 (Apache JServe Protocol + version 1.3), FTP, CONNECT (for SSL), + HTTP/0.9, HTTP/1.0, and HTTP/1.1. + The module can be configured to connect to other proxy modules for these + and other protocols.

+ +

Apache's proxy features are divided into several modules in + addition to mod_proxy: + mod_proxy_http, mod_proxy_ftp, + mod_proxy_ajp, mod_proxy_balancer, + and mod_proxy_connect. Thus, if you want to use + one or more of the particular proxy functions, load + mod_proxy and the appropriate module(s) + into the server (either statically at compile-time or dynamically + via the LoadModule + directive).

+ +

In addition, extended features are provided by other modules. + Caching is provided by mod_cache and related + modules. The ability to contact remote servers using the SSL/TLS + protocol is provided by the SSLProxy* directives of + mod_ssl. These additional modules will need + to be loaded and configured to take advantage of these features.

+
+ +
top
+
+

Forward and Reverse Proxies

+

Apache can be configured in both a forward and + reverse proxy mode.

+ +

An ordinary forward proxy is an intermediate + server that sits between the client and the origin + server. In order to get content from the origin server, + the client sends a request to the proxy naming the origin server + as the target and the proxy then requests the content from the + origin server and returns it to the client. The client must be + specially configured to use the forward proxy to access other + sites.

+ +

A typical usage of a forward proxy is to provide Internet + access to internal clients that are otherwise restricted by a + firewall. The forward proxy can also use caching (as provided + by mod_cache) to reduce network usage.

+ +

The forward proxy is activated using the ProxyRequests directive. Because + forward proxys allow clients to access arbitrary sites through + your server and to hide their true origin, it is essential that + you secure your server so that only + authorized clients can access the proxy before activating a + forward proxy.

+ +

A reverse proxy, by contrast, appears to the + client just like an ordinary web server. No special + configuration on the client is necessary. The client makes + ordinary requests for content in the name-space of the reverse + proxy. The reverse proxy then decides where to send those + requests, and returns the content as if it was itself the + origin.

+ +

A typical usage of a reverse proxy is to provide Internet + users access to a server that is behind a firewall. Reverse + proxies can also be used to balance load among several back-end + servers, or to provide caching for a slower back-end server. + In addition, reverse proxies can be used simply to bring + several servers into the same URL space.

+ +

A reverse proxy is activated using the ProxyPass directive or the + [P] flag to the RewriteRule directive. It is + not necessary to turn ProxyRequests on in order to + configure a reverse proxy.

+
top
+
+

Basic Examples

+ +

The examples below are only a very basic idea to help you + get started. Please read the documentation on the individual + directives.

+ +

In addition, if you wish to have caching enabled, consult + the documentation from mod_cache.

+ +

Forward Proxy

+ ProxyRequests On
+ ProxyVia On
+
+ <Proxy *>
+ + Order deny,allow
+ Deny from all
+ Allow from internal.example.com
+ + </Proxy> +

+ +

Reverse Proxy

+ ProxyRequests Off
+
+ <Proxy *>
+ + Order deny,allow
+ Allow from all
+ + </Proxy>
+
+ ProxyPass /foo http://foo.example.com/bar
+ ProxyPassReverse /foo http://foo.example.com/bar +

+
top
+
+

Controlling access to your proxy

+

You can control who can access your proxy via the <Proxy> control block as in + the following example:

+ +

+ <Proxy *>
+ + Order Deny,Allow
+ Deny from all
+ Allow from 192.168.0
+ + </Proxy> +

+ +

For more information on access control directives, see + mod_authz_host.

+ +

Strictly limiting access is essential if you are using a + forward proxy (using the ProxyRequests directive). + Otherwise, your server can be used by any client to access + arbitrary hosts while hiding his or her true identity. This is + dangerous both for your network and for the Internet at large. + When using a reverse proxy (using the ProxyPass directive with + ProxyRequests Off), access control is less + critical because clients can only contact the hosts that you + have specifically configured.

+ +
top
+
+

Slow Startup

+

If you're using the ProxyBlock directive, hostnames' IP addresses are looked up + and cached during startup for later match test. This may take a few + seconds (or more) depending on the speed with which the hostname lookups + occur.

+
top
+
+

Intranet Proxy

+

An Apache proxy server situated in an intranet needs to forward + external requests through the company's firewall (for this, configure + the ProxyRemote directive + to forward the respective scheme to the firewall proxy). + However, when it has to + access resources within the intranet, it can bypass the firewall when + accessing hosts. The NoProxy + directive is useful for specifying which hosts belong to the intranet and + should be accessed directly.

+ +

Users within an intranet tend to omit the local domain name from their + WWW requests, thus requesting "http://somehost/" instead of + http://somehost.example.com/. Some commercial proxy servers + let them get away with this and simply serve the request, implying a + configured local domain. When the ProxyDomain directive is used and the server is configured for proxy service, Apache can return + a redirect response and send the client to the correct, fully qualified, + server address. This is the preferred method since the user's bookmark + files will then contain fully qualified hosts.

+
top
+
+

Protocol Adjustments

+

For circumstances where mod_proxy is sending + requests to an origin server that doesn't properly implement + keepalives or HTTP/1.1, there are two environment variables that can force the + request to use HTTP/1.0 with no keepalive. These are set via the + SetEnv directive.

+ +

These are the force-proxy-request-1.0 and + proxy-nokeepalive notes.

+ +

+ <Location /buggyappserver/>
+ + ProxyPass http://buggyappserver:7001/foo/
+ SetEnv force-proxy-request-1.0 1
+ SetEnv proxy-nokeepalive 1
+ + </Location> +

+ +
top
+
+

Request Bodys

+ +

Some request methods such as POST include a request body. + The HTTP protocol requires that requests which include a body + either use chunked transfer encoding or send a + Content-Length request header. When passing these + requests on to the origin server, mod_proxy_http + will always attempt to send the Content-Length. But + if the body is large and the original request used chunked + encoding, then chunked encoding may also be used in the upstream + request. You can control this selection using environment variables. Setting + proxy-sendcl ensures maximum compatibility with + upstream servers by always sending the + Content-Length, while setting + proxy-sendchunked minimizes resource usage by using + chunked encoding.

+ +
+
top
+

AllowCONNECT Directive

+ + + + + + + +
Description:Ports that are allowed to CONNECT through the +proxy
Syntax:AllowCONNECT port [port] ...
Default:AllowCONNECT 443 563
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

The AllowCONNECT directive specifies a list + of port numbers to which the proxy CONNECT method may + connect. Today's browsers use this method when a https + connection is requested and proxy tunneling over HTTP is in effect.

+ +

By default, only the default https port (443) and the + default snews port (563) are enabled. Use the + AllowCONNECT directive to override this default and + allow connections to the listed ports only.

+ +

Note that you'll need to have mod_proxy_connect present + in the server in order to get the support for the CONNECT at + all.

+ +
+
top
+

NoProxy Directive

+ + + + + + +
Description:Hosts, domains, or networks that will be connected to +directly
Syntax:NoProxy host [host] ...
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

This directive is only useful for Apache proxy servers within + intranets. The NoProxy directive specifies a + list of subnets, IP addresses, hosts and/or domains, separated by + spaces. A request to a host which matches one or more of these is + always served directly, without forwarding to the configured + ProxyRemote proxy server(s).

+ +

Example

+ ProxyRemote * http://firewall.mycompany.com:81
+ NoProxy .mycompany.com 192.168.112.0/21 +

+ +

The host arguments to the NoProxy + directive are one of the following type list:

+ +
+ +
Domain
+
+

A Domain is a partially qualified DNS domain name, preceded + by a period. It represents a list of hosts which logically belong to the + same DNS domain or zone (i.e., the suffixes of the hostnames are + all ending in Domain).

+ +

Examples

+ .com .apache.org. +

+ +

To distinguish Domains from Hostnames (both syntactically and semantically; a DNS domain can + have a DNS A record, too!), Domains are always written with a + leading period.

+ +

Note

+

Domain name comparisons are done without regard to the case, and + Domains are always assumed to be anchored in the root of the + DNS tree, therefore two domains .MyDomain.com and + .mydomain.com. (note the trailing period) are considered + equal. Since a domain comparison does not involve a DNS lookup, it is much + more efficient than subnet comparison.

+
+ + +
SubNet
+
+

A SubNet is a partially qualified internet address in + numeric (dotted quad) form, optionally followed by a slash and the netmask, + specified as the number of significant bits in the SubNet. It is + used to represent a subnet of hosts which can be reached over a common + network interface. In the absence of the explicit net mask it is assumed + that omitted (or zero valued) trailing digits specify the mask. (In this + case, the netmask can only be multiples of 8 bits wide.) Examples:

+ +
+
192.168 or 192.168.0.0
+
the subnet 192.168.0.0 with an implied netmask of 16 valid bits + (sometimes used in the netmask form 255.255.0.0)
+
192.168.112.0/21
+
the subnet 192.168.112.0/21 with a netmask of 21 + valid bits (also used in the form 255.255.248.0)
+
+ +

As a degenerate case, a SubNet with 32 valid bits is the + equivalent to an IPAddr, while a SubNet with zero + valid bits (e.g., 0.0.0.0/0) is the same as the constant + _Default_, matching any IP address.

+ + +
IPAddr
+
+

A IPAddr represents a fully qualified internet address in + numeric (dotted quad) form. Usually, this address represents a host, but + there need not necessarily be a DNS domain name connected with the + address.

+

Example

+ 192.168.123.7 +

+ +

Note

+

An IPAddr does not need to be resolved by the DNS system, so + it can result in more effective apache performance.

+
+ + +
Hostname
+
+

A Hostname is a fully qualified DNS domain name which can + be resolved to one or more IPAddrs via the + DNS domain name service. It represents a logical host (in contrast to + Domains, see above) and must be resolvable + to at least one IPAddr (or often to a list + of hosts with different IPAddrs).

+ +

Examples

+ prep.ai.mit.edu
+ www.apache.org +

+ +

Note

+

In many situations, it is more effective to specify an IPAddr in place of a Hostname since a + DNS lookup can be avoided. Name resolution in Apache can take a remarkable + deal of time when the connection to the name server uses a slow PPP + link.

+

Hostname comparisons are done without regard to the case, + and Hostnames are always assumed to be anchored in the root + of the DNS tree, therefore two hosts WWW.MyDomain.com + and www.mydomain.com. (note the trailing period) are + considered equal.

+
+
+ +

See also

+ +
+
top
+

<Proxy> Directive

+ + + + + + +
Description:Container for directives applied to proxied resources
Syntax:<Proxy wildcard-url> ...</Proxy>
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

Directives placed in <Proxy> + sections apply only to matching proxied content. Shell-style wildcards are + allowed.

+ +

For example, the following will allow only hosts in + yournetwork.example.com to access content via your proxy + server:

+ +

+ <Proxy *>
+ + Order Deny,Allow
+ Deny from all
+ Allow from yournetwork.example.com
+ + </Proxy> +

+ +

The following example will process all files in the foo + directory of example.com through the INCLUDES + filter when they are sent through the proxy server:

+ +

+ <Proxy http://example.com/foo/*>
+ + SetOutputFilter INCLUDES
+ + </Proxy> +

+ + +
+
top
+

ProxyBadHeader Directive

+ + + + + + + + +
Description:Determines how to handle bad header lines in a +response
Syntax:ProxyBadHeader IsError|Ignore|StartBody
Default:ProxyBadHeader IsError
Context:server config, virtual host
Status:Extension
Module:mod_proxy
Compatibility:available in Apache 2.0.44 and later
+

The ProxyBadHeader directive determines the + behaviour of mod_proxy if it receives syntactically invalid + header lines (i.e. containing no colon). The following arguments + are possible:

+ +
+
IsError
+
Abort the request and end up with a 502 (Bad Gateway) response. This is + the default behaviour.
+ +
Ignore
+
Treat bad header lines as if they weren't sent.
+ +
StartBody
+
When receiving the first bad header line, finish reading the headers and + treat the remainder as body. This helps to work around buggy backend servers + which forget to insert an empty line between the headers and the body.
+
+ +
+
top
+

ProxyBlock Directive

+ + + + + + +
Description:Words, hosts, or domains that are banned from being +proxied
Syntax:ProxyBlock *|word|host|domain +[word|host|domain] ...
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

The ProxyBlock directive specifies a list of + words, hosts and/or domains, separated by spaces. HTTP, HTTPS, and + FTP document requests to sites whose names contain matched words, + hosts or domains are blocked by the proxy server. The proxy + module will also attempt to determine IP addresses of list items which + may be hostnames during startup, and cache them for match test as + well. That may slow down the startup time of the server.

+ +

Example

+ ProxyBlock joes-garage.com some-host.co.uk rocky.wotsamattau.edu +

+ +

rocky.wotsamattau.edu would also be matched if referenced by + IP address.

+ +

Note that wotsamattau would also be sufficient to match + wotsamattau.edu.

+ +

Note also that

+ +

+ ProxyBlock * +

+ +

blocks connections to all sites.

+ +
+
top
+

ProxyDomain Directive

+ + + + + + +
Description:Default domain name for proxied requests
Syntax:ProxyDomain Domain
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

This directive is only useful for Apache proxy servers within + intranets. The ProxyDomain directive specifies + the default domain which the apache proxy server will belong to. If a + request to a host without a domain name is encountered, a redirection + response to the same host with the configured Domain appended + will be generated.

+ +

Example

+ ProxyRemote * http://firewall.mycompany.com:81
+ NoProxy .mycompany.com 192.168.112.0/21
+ ProxyDomain .mycompany.com +

+ +
+
top
+

ProxyErrorOverride Directive

+ + + + + + + + +
Description:Override error pages for proxied content
Syntax:ProxyErrorOverride On|Off
Default:ProxyErrorOverride Off
Context:server config, virtual host
Status:Extension
Module:mod_proxy
Compatibility:Available in version 2.0 and later
+

This directive is useful for reverse-proxy setups, where you want to + have a common look and feel on the error pages seen by the end user. + This also allows for included files (via + mod_include's SSI) to get + the error code and act accordingly (default behavior would display + the error page of the proxied server, turning this on shows the SSI + Error message).

+ +
+
top
+

ProxyIOBufferSize Directive

+ + + + + + + +
Description:Determine size of internal data throughput buffer
Syntax:ProxyIOBufferSize bytes
Default:ProxyIOBufferSize 8192
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

The ProxyIOBufferSize directive adjusts the size + of the internal buffer, which is used as a scratchpad for the data between + input and output. The size must be less or equal 8192.

+ +

In almost every case there's no reason to change that value.

+ +
+
top
+

<ProxyMatch> Directive

+ + + + + + +
Description:Container for directives applied to regular-expression-matched +proxied resources
Syntax:<ProxyMatch regex> ...</ProxyMatch>
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

The <ProxyMatch> directive is + identical to the <Proxy> directive, except it matches URLs + using regular expressions.

+ +
+
top
+

ProxyMaxForwards Directive

+ + + + + + + + +
Description:Maximium number of proxies that a request can be forwarded +through
Syntax:ProxyMaxForwards number
Default:ProxyMaxForwards 10
Context:server config, virtual host
Status:Extension
Module:mod_proxy
Compatibility:Available in Apache 2.0 and later
+

The ProxyMaxForwards directive specifies the + maximum number of proxies through which a request may pass, if there's no + Max-Forwards header supplied with the request. This is + set to prevent infinite proxy loops, or a DoS attack.

+ +

Example

+ ProxyMaxForwards 15 +

+ +
+
top
+

ProxyPass Directive

+ + + + + + +
Description:Maps remote servers into the local server URL-space
Syntax:ProxyPass [path] !|url [key=value key=value ...]]
Context:server config, virtual host, directory
Status:Extension
Module:mod_proxy
+

This directive allows remote servers to be mapped into the space of + the local server; the local server does not act as a proxy in the + conventional sense, but appears to be a mirror of the remote + server. path is the name of a local virtual path; url + is a partial URL for the remote server and cannot include a query + string.

+ +
The ProxyRequests directive should + usually be set off when using + ProxyPass.
+ +

Suppose the local server has address http://example.com/; + then

+ +

+ ProxyPass /mirror/foo/ http://backend.example.com/ +

+ +

will cause a local request for + http://example.com/mirror/foo/bar to be internally converted + into a proxy request to http://backend.example.com/bar.

+ +

The ! directive is useful in situations where you don't want + to reverse-proxy a subdirectory, e.g.

+ +

+ ProxyPass /mirror/foo/i !
+ ProxyPass /mirror/foo http://backend.example.com +

+ +

will proxy all requests to /mirror/foo to + backend.example.com except requests made to + /mirror/foo/i.

+ +

Note

+

Order is important. you need to put the exclusions before the + general ProxyPass directive.

+
+ +

As of Apache 2.1, the ability to use pooled connections to a backend + server is available. Using the key=value parameters it is + possible to tune this connection pooling. The default for a Hard + Maximum for the number of connections is the number of threads per + process in the active MPM. In the Prefork MPM, this is always 1, while with + the Worker MPM it is controlled by the + ThreadsPerChild.

+ +

Setting min will determine how many connections will always + be open to the backend server. Upto the Soft Maximum or smax + number of connections will be created on demand. Any connections above + smax are subject to a time to live or ttl. Apache + will never create more than the Hard Maximum or max connections + to the backend server.

+ +

+ ProxyPass /example http://backend.example.com smax=5 max=20 ttl=120 retry=300 +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterDefaultDescription
min0Minumum number of connections that will always + be open to the backend server.
max1...nHard Maximum number of connections that will be + allowed to the backend server. The default for a Hard Maximum + for the number of connections is the number of threads per process in the + active MPM. In the Prefork MPM, this is always 1, while with the Worker MPM + it is controlled by the ThreadsPerChild. + Apache will never create more than the Hard Maximum connections + to the backend server.
smaxmaxUpto the Soft Maximum + number of connections will be created on demand. Any connections above + smax are subject to a time to live or ttl. +
ttl-Time To Live for the inactive connections above the + smax connections in seconds. Apache will close all + connections that has not been used inside that time period. +
timeoutTimeoutConnection timeout in seconds. + If not set the Apache will wait until the free connection + is available. This directive is used for limiting the number + of connections to the backend server together with max + parameter. +
acquire-If set this will be the maximum time to wait for a free + connection in the connection pool. If there are no free connections + in the pool the Apache will return SERVER_BUSY status to + the client. +
keepaliveOffThis parameter should be used when you have a firewall between your + Apache and the backend server, who tend to drop inactive connections. + This flag will tell the Operating System to send KEEP_ALIVE + messages on inactive connections (interval depends on global OS settings, + generally 120ms), and thus prevent the firewall to drop the connection. + To enable keepalive set this property value to On. +
retry60Connection pool worker retry timeout in seconds. + If the connection pool worker to the backend server is in the error state, + Apache will not forward any requests to that server until the timeout + expires. This enables to shut down the backend server for maintenance, + and bring it back online later. +
loadfactor1Worker load factor. Used with BalancerMember. + It is a number between 1 and 100 and defines the normalized weighted + load applied to the worker. +
route-Route of the worker when used inside load balancer. + The route is a value appended to seesion id. +
redirect-Redirection Route of the worker. This value is usually + set dynamically to enable safe removal of the node from + the cluster. If set all requests without session id will be + redirected to the BalancerMember that has route parametar + equal as this value. +
+ +

If the Proxy directive scheme starts with the + balancer:// then a virtual worker that does not really + communicate with the backend server will be created. Instead it is responsible + for the management of several "real" workers. In that case the special set of + parameters can be add to this virtual worker. +

+ + + + + + + + + + + + + + + + + + + + +
ParameterDefaultDescription
lbmethod-Balancer load-balance method. Select the load-balancing scheduler + method to use. Either byrequests, to perform weighted + request counting or bytraffic, to perform weighted + traffic byte count balancing. Default is byrequests. +
stickysession-Balancer sticky session name. The value is usually set to something + like JSESSIONID or PHPSESSIONID, + and it depends on the backend application server that support sessions. +
nofailoverOffIf set to On the session will break if the worker is in + error state or disabled. Set this value to On if backend servers do not + support session replication. +
timeout0Balancer timeout in seconds. If set this will be the maximum time + to wait for a free worker. Default is not to wait. +
maxattempts1Maximum number of failover attempts before giving up. +
+

+ ProxyPass /special-area http://special.example.com/ smax=5 max=10
+ ProxyPass / balancer://mycluster stickysession=jsessionid nofailover=On
+ <Proxy balancer://mycluster>
+ + BalancerMember http://1.2.3.4:8009
+ BalancerMember http://1.2.3.5:8009 smax=10
+ # Less powerful server, don't send as many requests there
+ BalancerMember http://1.2.3.6:8009 smax=1 loadfactor=20
+ + </Proxy> +

+ +

When used inside a <Location> section, the first argument is omitted and the local + directory is obtained from the <Location>.

+ +

If you require a more flexible reverse-proxy configuration, see the + RewriteRule directive with the + [P] flag.

+ +
+
top
+

ProxyPassReverse Directive

+ + + + + + +
Description:Adjusts the URL in HTTP response headers sent from a reverse +proxied server
Syntax:ProxyPassReverse [path] url
Context:server config, virtual host, directory
Status:Extension
Module:mod_proxy
+

This directive lets Apache adjust the URL in the Location, + Content-Location and URI headers on HTTP redirect + responses. This is essential when Apache is used as a reverse proxy to avoid + by-passing the reverse proxy because of HTTP redirects on the backend + servers which stay behind the reverse proxy.

+ +

Only the HTTP response headers specifically mentioned above + will be rewritten. Apache will not rewrite other response + headers, nor will it rewrite URL references inside HTML pages. + This means that if the proxied content contains absolute URL + references, they will by-pass the proxy. A third-party module + that will look inside the HTML and rewrite URL references is Nick + Kew's mod_proxy_html.

+ +

path is the name of a local virtual path. url is a + partial URL for the remote server - the same way they are used for the + ProxyPass directive.

+ +

For example, suppose the local server has address + http://example.com/; then

+ +

+ ProxyPass /mirror/foo/ http://backend.example.com/
+ ProxyPassReverse /mirror/foo/ http://backend.example.com/
+ ProxyPassReverseCookieDomain backend.example.com public.example.com
+ ProxyPassReverseCookiePath / /mirror/foo/ +

+ +

will not only cause a local request for the + http://example.com/mirror/foo/bar to be internally converted + into a proxy request to http://backend.example.com/bar + (the functionality ProxyPass provides here). It also takes care + of redirects the server backend.example.com sends: when + http://backend.example.com/bar is redirected by him to + http://backend.example.com/quux Apache adjusts this to + http://example.com/mirror/foo/quux before forwarding the HTTP + redirect response to the client. Note that the hostname used for + constructing the URL is chosen in respect to the setting of the UseCanonicalName directive.

+ +

Note that this ProxyPassReverse directive can + also be used in conjunction with the proxy pass-through feature + (RewriteRule ... [P]) from mod_rewrite + because it doesn't depend on a corresponding ProxyPass directive.

+ +

When used inside a <Location> section, the first argument is omitted and the local + directory is obtained from the <Location>.

+ +
+
top
+

ProxyPassReverseCookieDomain Directive

+ + + + + + +
Description:Adjusts the Domain string in Set-Cookie headers from a reverse- +proxied server
Syntax:ProxyPassReverseCookieDomain internal-domain public-domain
Context:server config, virtual host, directory
Status:Extension
Module:mod_proxy
+

Usage is basically similar to +ProxyPassReverse, but instead of +rewriting headers that are a URL, this rewrites the domain +string in Set-Cookie headers.

+ +
+
top
+

ProxyPassReverseCookiePath Directive

+ + + + + + +
Description:Adjusts the Path string in Set-Cookie headers from a reverse- +proxied server
Syntax:ProxyPassReverseCookiePath internal-path public-path
Context:server config, virtual host, directory
Status:Extension
Module:mod_proxy
+

Usage is basically similar to +ProxyPassReverse, but instead of +rewriting headers that are a URL, this rewrites the path +string in Set-Cookie headers.

+ +
+
top
+

ProxyPreserveHost Directive

+ + + + + + + + +
Description:Use incoming Host HTTP request header for proxy +request
Syntax:ProxyPreserveHost On|Off
Default:ProxyPreserveHost Off
Context:server config, virtual host
Status:Extension
Module:mod_proxy
Compatibility:Available in Apache 2.0.31 and later.
+

When enabled, this option will pass the Host: line from the incoming + request to the proxied host, instead of the hostname specified in the + ProxyPass line.

+ +

This option should normally be turned Off. It is mostly + useful in special configurations like proxied mass name-based virtual + hosting, where the original Host header needs to be evaluated by the + backend server.

+ +
+
top
+

ProxyReceiveBufferSize Directive

+ + + + + + + +
Description:Network buffer size for proxied HTTP and FTP +connections
Syntax:ProxyReceiveBufferSize bytes
Default:ProxyReceiveBufferSize 0
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

The ProxyReceiveBufferSize directive specifies an + explicit (TCP/IP) network buffer size for proxied HTTP and FTP connections, + for increased throughput. It has to be greater than 512 or set + to 0 to indicate that the system's default buffer size should + be used.

+ +

Example

+ ProxyReceiveBufferSize 2048 +

+ +
+
top
+

ProxyRemote Directive

+ + + + + + +
Description:Remote proxy used to handle certain requests
Syntax:ProxyRemote match remote-server
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

This defines remote proxies to this proxy. match is either the + name of a URL-scheme that the remote server supports, or a partial URL + for which the remote server should be used, or * to indicate + the server should be contacted for all requests. remote-server is + a partial URL for the remote server. Syntax:

+ +

+ remote-server = + scheme://hostname[:port] +

+ +

scheme is effectively the protocol that should be used to + communicate with the remote server; only http is supported by + this module.

+ +

Example

+ ProxyRemote http://goodguys.com/ http://mirrorguys.com:8000
+ ProxyRemote * http://cleversite.com
+ ProxyRemote ftp http://ftpproxy.mydomain.com:8080 +

+ +

In the last example, the proxy will forward FTP requests, encapsulated + as yet another HTTP proxy request, to another proxy which can handle + them.

+ +

This option also supports reverse proxy configuration - a backend + webserver can be embedded within a virtualhost URL space even if that + server is hidden by another forward proxy.

+ +
+
top
+

ProxyRemoteMatch Directive

+ + + + + + +
Description:Remote proxy used to handle requests matched by regular +expressions
Syntax:ProxyRemoteMatch regex remote-server
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

The ProxyRemoteMatch is identical to the + ProxyRemote directive, except the + first argument is a regular expression + match against the requested URL.

+ +
+
top
+

ProxyRequests Directive

+ + + + + + + +
Description:Enables forward (standard) proxy requests
Syntax:ProxyRequests On|Off
Default:ProxyRequests Off
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

This allows or prevents Apache from functioning as a forward proxy + server. (Setting ProxyRequests to Off does not disable use of + the ProxyPass directive.)

+ +

In a typical reverse proxy configuration, this option should be set to + Off.

+ +

In order to get the functionality of proxying HTTP or FTP sites, you + need also mod_proxy_http or mod_proxy_ftp + (or both) present in the server.

+ +

Warning

+

Do not enable proxying with ProxyRequests until you have secured your server. Open proxy servers are dangerous + both to your network and to the Internet at large.

+
+ +
+
top
+

ProxyTimeout Directive

+ + + + + + + + +
Description:Network timeout for proxied requests
Syntax:ProxyTimeout seconds
Default:ProxyTimeout 300
Context:server config, virtual host
Status:Extension
Module:mod_proxy
Compatibility:Available in Apache 2.0.31 and later
+

This directive allows a user to specifiy a timeout on proxy requests. + This is useful when you have a slow/buggy appserver which hangs, and you + would rather just return a timeout and fail gracefully instead of waiting + however long it takes the server to return.

+ +
+
top
+

ProxyVia Directive

+ + + + + + + +
Description:Information provided in the Via HTTP response +header for proxied requests
Syntax:ProxyVia On|Off|Full|Block
Default:ProxyVia Off
Context:server config, virtual host
Status:Extension
Module:mod_proxy
+

This directive controls the use of the Via: HTTP + header by the proxy. Its intended use is to control the flow of + proxy requests along a chain of proxy servers. See RFC 2616 (HTTP/1.1), section + 14.45 for an explanation of Via: header lines.

+ +
    +
  • If set to Off, which is the default, no special processing + is performed. If a request or reply contains a Via: header, + it is passed through unchanged.
    • + +
  • If set to On, each request and reply will get a + Via: header line added for the current host.
    • + +
  • If set to Full, each generated Via: header + line will additionally have the Apache server version shown as a + Via: comment field.
    • + +
  • If set to Block, every proxy request will have all its + Via: header lines removed. No new Via: header will + be generated.
    • +
+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy.html.ja.euc-jp b/docs/manual/mod/mod_proxy.html.ja.euc-jp new file mode 100644 index 00000000..2c7660b1 --- /dev/null +++ b/docs/manual/mod/mod_proxy.html.ja.euc-jp @@ -0,0 +1,1204 @@ + + + +mod_proxy - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_proxy

+
+

Available Languages:  en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:HTTP/1.1 ¥×¥í¥­¥·/¥²¡¼¥È¥¦¥§¥¤¥µ¡¼¥Ð
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:proxy_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_proxy.c
+

³µÍ×

+ +

·Ù¹ð

+

¥µ¡¼¥Ð¤ò°ÂÁ´¤Ë¤¹¤ë¤Þ¤Ç ProxyRequests ¤ÏÍ­¸ú¤Ë¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + ¥ª¡¼¥×¥ó¥×¥í¥­¥·¥µ¡¼¥Ð¤Ï¤¢¤Ê¤¿¼«¿È¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤È¤Ã¤Æ¤â¡¢ + ¥¤¥ó¥¿¡¼¥Í¥Ã¥ÈÁ´ÂΤˤȤäƤâ´í¸±¤Ç¤¹¡£

+
+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï Apache ¤Î¥×¥í¥­¥·/¥²¡¼¥È¥¦¥§¥¤µ¡Ç½¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£ + AJP13 (Apache JServe Protocol version 1.3), + FTP, CONNECT (SSL ÍÑ), + HTTP/0.9, HTTP/1.0, HTTP/1.1 + ¤Î¥×¥í¥­¥·µ¡Ç½¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤é¤Î¥×¥í¥È¥³¥ë¤ä¤½¤Î¾¤Î¥×¥í¥È¥³¥ëÍѤΠ+ ¥×¥í¥­¥·µ¡Ç½¤ò»ý¤Ã¤¿¡¢Â¾¤Î¥â¥¸¥å¡¼¥ë¤ËÀܳ¤¹¤ë¤è¤¦¤Ë¤âÀßÄê¤Ç¤­¤Þ¤¹¡£

+ +

Apache ¤Î¥×¥í¥­¥·µ¡Ç½¤Ï mod_proxy ¤Î¾¤Ë¡¢ + ¤¤¤¯¤Ä¤«¤Î¥â¥¸¥å¡¼¥ë¤Ëʬ³ä¤µ¤ì¤Æ¤¤¤Þ¤¹: + mod_proxy_http, mod_proxy_ftp, + mod_proxy_ajp, mod_proxy_balancer, + mod_proxy_connect ¤Ç¤¹¡£¤Ç¤¹¤«¤é¡¢ + ÆÃÄê¤Î¥×¥í¥­¥·¤Îµ¡Ç½¤ò»È¤¤¤¿¤¤¾ì¹ç¤Ï¡¢mod_proxy ¤È + ³ºÅö¤¹¤ë¥â¥¸¥å¡¼¥ë¤ò¥µ¡¼¥Ð¤Ë (¥³¥ó¥Ñ¥¤¥ë»þ¤ËÀÅŪ¤Ë¹Ô¤Ê¤¦¤« + LoadModule ¤ÇưŪ¤ËÆɤ߹þ¤à¤«¤·¤Æ) + ÁȤ߹þ¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

¤³¤ì¤Ë²Ã¤¨¤Æ¡¢Â¾¤Î¥â¥¸¥å¡¼¥ë¤Ë¤è¤Ã¤Æ³ÈÄ¥µ¡Ç½¤¬Ä󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¥­¥ã¥Ã¥·¥å¤Ï mod_cache ¤È´ØÏ¢¥â¥¸¥å¡¼¥ë¤Ç + Ä󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£SSL/TLS ¤Ç±ó³Ö¥µ¡¼¥Ð¤ËÀܳ¤¹¤ëµ¡Ç½¤Ï + mod_ssl ¤Î SSLProxy* ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + Ä󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤é¤Îµ¡Ç½¤òÍøÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢³ºÅö¤¹¤ë¥â¥¸¥å¡¼¥ë¤ò + ÁȤ߹þ¤ó¤ÇÀßÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
+ +
top
+
+

¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤È¥ê¥Ð¡¼¥¹¥×¥í¥­¥·

+

Apache ¤Ï¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤È¤·¤Æ¤â¡¢ + ¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤È¤·¤Æ¤âÀßÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Ä̾ï¤Î¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤Ï¥¯¥é¥¤¥¢¥ó¥È¤È + ¥ª¥ê¥¸¥ó¥µ¡¼¥Ð (ÌõÃí: ¥³¥ó¥Æ¥ó¥ÄÀ¸À®¸µ¤Î¥µ¡¼¥Ð) + ¤Î´Ö¤Ë°ÌÃÖ¤¹¤ëÃæ´Ö¥µ¡¼¥Ð¤Ç¤¹¡£ + ¥ª¥ê¥¸¥ó¥µ¡¼¥Ð¤«¤é¥³¥ó¥Æ¥ó¥Ä¤ò¼èÆÀ¤¹¤ë²áÄø¤Ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï + ¹Ô¤­Àè¤È¤·¤Æ¥ª¥ê¥¸¥ó¥µ¡¼¥Ð¤ò»ØÄꤷ¤Ä¤Ä¥×¥í¥­¥·¤Ë¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ê¡¢ + ¥×¥í¥­¥·¤Ï¥ª¥ê¥¸¥ó¥µ¡¼¥Ð¤«¤é¥³¥ó¥Æ¥ó¥Ä¼èÆÀ¤Î¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ê¡¢ + ¥³¥ó¥Æ¥ó¥Ä¤¬¼èÆÀ¤Ç¤­¤ì¤Ð¤½¤ì¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤·¤Þ¤¹¡£ + ¥¯¥é¥¤¥¢¥ó¥È¤¬Â¾¤Î¥µ¥¤¥È¤Ë¥Õ¥©¥ï¡¼¥É¥×¥í¥¯¥··Ðͳ¤Ç¥¢¥¯¥»¥¹¤¹¤ë¤Ë¤Ï¡¢ + ÆÃÊ̤ˤ½¤ìÍѤÎÀßÄê¤ò¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤Î°ìÈÌŪ¤Ê»ÈÍÑÊýË¡¤Ï¡¢¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Ë¤è¤Ã¤Æ + À©¸Â¤µ¤ì¤Æ¤¤¤ëÆâÉô¤Î¥¯¥é¥¤¥¢¥ó¥È¤Ë¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Ø¤Î¥¢¥¯¥»¥¹¤ò + Ä󶡤¹¤ë¤â¤Î¤Ç¤¹¡£¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¤Î»ÈÍÑÎ̤ò + ¸º¤é¤¹¤¿¤á¤Ë (mod_cache ¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë) + ¥­¥ã¥Ã¥·¥åµ¡Ç½¤òÍѤ¤¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤Ï ProxyRequests ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + Í­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤Ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÏËÜÅö¤Î¿È¸µ¤ò + ±£¤·¤ÆǤ°Õ¤Î¥µ¥¤¥È¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ë¤¿¤á¡¢¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤ò + Í­¸ú¤Ë¤¹¤ëÁ°¤Ë¡¢¾µÇ§¤µ¤ì¤¿¥¯¥é¥¤¥¢¥ó¥È¤Î¤ß¤¬¥×¥í¥­¥·¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë + ¥µ¡¼¥Ð¤ò°ÂÁ´¤Ë¤¹¤ë¤³¤È¤¬½ÅÍפǤ¹¡£

+ +

°ìÊý¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ë¤ÏÉáÄ̤Π+ ¥¦¥§¥Ö¥µ¡¼¥Ð¤Î¤è¤¦¤Ë¸«¤¨¤Þ¤¹¡£¥¯¥é¥¤¥¢¥ó¥È¦¤ËÆÃÊ̤ÊÀßÄê¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£ + ¥¯¥é¥¤¥¢¥ó¥È¤Ï¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤Î̾Á°¶õ´Ö¤ËÂФ·¤ÆÄ̾ï¤Î¥³¥ó¥Æ¥ó¥Ä¤Ø¤Î + ¥ê¥¯¥¨¥¹¥È¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£¥×¥í¥­¥·¤Ï¥ê¥¯¥¨¥¹¥È¤ò¤É¤³¤ËÁ÷¤ì¤ÐÎɤ¤¤«¤òȽÄꤷ¡¢ + ¤¢¤¿¤«¤â¼«Ê¬¼«¿È¤¬¥ª¥ê¥¸¥ó¥µ¡¼¥Ð¤Ç¤¢¤Ã¤¿¤«¤Î¤è¤¦¤Ë¥¯¥é¥¤¥¢¥ó¥È¤Ë + ¥³¥ó¥Æ¥ó¥Ä¤òÊÖ¤·¤Þ¤¹¡£

+ +

¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤Î¤è¤¯¤¢¤ëÍøÍÑÊýË¡¤Ï¡¢¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥æ¡¼¥¶¤Ë + ¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤ÎÃæ¤Ë¤¢¤ë¥µ¡¼¥Ð¤Ë¥¢¥¯¥»¥¹¤òÍ¿¤¨¤ë¤È¤¤¤¦¤â¤Î¤Ç¤¹¡£ + ¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤ÏÊ£¿ô¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤ØÉé²Ùʬ»¶¤ò¤¹¤ë¤¿¤á¤Ë + »È¤Ã¤¿¤ê¡¢ÃÙ¤¤¥Ð¥Ã¥¯¥¨¥ó¥É¥¨¥ó¥É¥µ¡¼¥Ð¤Î¤¿¤á¤Ë¥­¥ã¥Ã¥·¥åµ¡Ç½¤òÄ󶡤·¤¿¤ê + ¤¹¤ë¤¿¤á¤Ë»È¤¨¤Þ¤¹¡£¤Þ¤¿¡¢¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤ÏÊ£¿ô¤Î¥µ¡¼¥Ð¤ò + Ʊ¤¸ URL ¶õ´Ö¤Ë¤Þ¤È¤á¤ë¤¿¤á¤Ë»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ +

¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤Ï ProxyPass ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä + RewriteRule ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + [P] ¥Õ¥é¥°¤ò»È¤¦¤³¤È¤ÇÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤Î + ÀßÄê¤Î¤¿¤á¤Ë ProxyRequests ¤òÀßÄꤹ¤ëɬÍ×¤Ï + ¤¢¤ê¤Þ¤»¤ó¡£

+
top
+
+

´ðËܤÎÎã

+ +

°Ê²¼¤ÎÎã¤Ï¼ê»Ï¤á¤Î´Êñ¤ÊÎã¤Ç¤¹¡£¸Ä¡¹¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ÕÌ£¤Ï + ¤½¤ì¤¾¤ì¤ÎÀâÌÀ¤ò¤ªÆɤߤ¯¤À¤µ¤¤¡£

+ +

¤Þ¤¿¥­¥ã¥Ã¥·¥åµ¡Ç½¤òÍ­¸ú¤Ë¤·¤¿¤¤¾ì¹ç¤Ï¡¢mod_cache + ¤ÎÀâÌÀ¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£

+ +

¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·

+ ProxyRequests On
+ ProxyVia On
+
+ <Proxy *>
+ + Order deny,allow
+ Deny from all
+ Allow from internal.example.com
+ + </Proxy> +

+ +

¥ê¥Ð¡¼¥¹¥×¥í¥­¥·

+ ProxyRequests Off
+
+ <Proxy *>
+ + Order deny,allow
+ Allow from all
+ + </Proxy>
+
+ ProxyPass /foo http://foo.example.com/bar
+ ProxyPassReverse /foo http://foo.example.com/bar +

+
top
+
+

¥×¥í¥­¥·¤Ø¤Î¥¢¥¯¥»¥¹À©¸æ

+

¥×¥í¥­¥·¤Î¥¢¥¯¥»¥¹¤Ï°Ê²¼¤Î¤è¤¦¤Ë <Proxy> ¥³¥ó¥Æ¥Ê¤ÎÃæ¤Ë + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¯¤³¤È¤ÇÀ©¸æ¤Ç¤­¤Þ¤¹:

+ +

+ <Proxy *>
+ + Order Deny,Allow
+ Deny from all
+ Allow from 192.168.0
+ + </Proxy> +

+ +

¥¢¥¯¥»¥¹À©¸æ¤Î¤¿¤á¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï + mod_authz_host ¤ò¤ªÆɤߤ¯¤À¤µ¤¤¡£

+ +

(ProxyRequests ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤Ã¤Æ) ¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤òÀßÄꤷ¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢¸·¤·¤¯¥¢¥¯¥»¥¹ + À©¸Â¤ò¹Ô¤Ê¤¦¤³¤È¤¬Èó¾ï¤ËÂçÀڤǤ¹¡£¤½¤¦¤·¤Ê¤¤¤È¡¢Ç¤°Õ¤Î¥¯¥é¥¤¥¢¥ó¥È¤¬ + ¿È¸µ¤òÌÀ¤«¤¹¤³¤È¤Ê¤¯Ç¤°Õ¤Î¥Û¥¹¥È¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë¥µ¡¼¥Ð¤ò»È¤¦¤³¤È¤¬ + ¤Ç¤­¤Æ¤·¤Þ¤¤¤Þ¤¹¡£¤³¤ì¤Ï¤¢¤Ê¤¿¼«¿È¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤È¤Ã¤Æ¤â¡¢¥¤¥ó¥¿¡¼¥Í¥Ã¥È + Á´ÂΤˤȤäƤâ´í¸±¤Ê¤³¤È¤Ç¤¹¡£(ProxyRequests Off ¤Ë¤·¤Æ + ProxyPass ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ) + ¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï¤¢¤Ê¤¿¤¬ÌÀ¼¨Åª¤Ë + ÀßÄꤷ¤¿¥Û¥¹¥È¤Ë¤·¤«¥¢¥¯¥»¥¹¤Ç¤­¤Ê¤¤¤¿¤á¡¢¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¤Î¤È¤­ + ¤Û¤É¥¢¥¯¥»¥¹À©¸æ¤ËÎϤòÃí¤¬¤Ê¤¯¤Æ¤âÂç¾æÉפǤ¹¡£

+ +
top
+
+

FTP ¥×¥í¥­¥·

+ + +

¤É¤¦¤·¤Æ¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤¬ xxx + ¤Î¥Õ¥¡¥¤¥ë¤ò FTP ¤Ç¥À¥¦¥ó¥í¡¼¥É¤Ç¤­¤Ê¤¤¤Î?

+

¤ª¤½¤é¤¯¡¢¥×¥í¥­¥·¤Î mime.types ÀßÄê¥Õ¥¡¥¤¥ë¤Ç¤½¤Î¥Õ¥¡¥¤¥ë¥¿¥¤¥×¤¬ + application/octet-stream ¤Ç¤¢¤ë¤ÈÄêµÁ¤µ¤ì¤Æ¤¤¤Ê¤¤¤Î¤Ç¤·¤ç¤¦¡£ + °Ê²¼¤Î¤è¤¦¤Ê¤â¤Î¤¬Ìò¤ËΩ¤Ä¤«¤â¤·¤ì¤Þ¤»¤ó:

+ + 
application/octet-stream   bin dms lha lzh exe class tgz taz
+

Ê̤ÎÊýË¡¤È¤·¤Æ¡¢¤¹¤Ù¤Æ¤Î¥Ç¥Õ¥©¥ë¥È¤ò¥Ð¥¤¥Ê¥ê¤Ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹:

+ 
DefaultType application/octet-stream
+ + +

¥Õ¥¡¥¤¥ë xxx ¤ò FTP ¤Î ASCII ¥À¥¦¥ó¥í¡¼¥É + ¤Ë¤µ¤»¤ë¤Î¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Î?

+

¤Þ¤ì¤Ë¡¢(¥Ç¥Õ¥©¥ë¥È¤ÎžÁ÷¤Ï binary ¥â¡¼¥É¤Ç) ÆÃÄê¤Î + ¥Õ¥¡¥¤¥ë¤Î¤ß FTP ¤Î ASCII žÁ÷ÊýË¡¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤ + ¾ì¹ç¤Ë¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤ÎºÇ¸å¤Ë ;type=a ¤òÉÕ¤±¤ë¤³¤È¤Ç + mod_proxy ¤Ë ASCII žÁ÷¤ò¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + (¤¿¤À¤·¡¢FTP ¤Î¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤Ï¾ï¤Ë ASCII ¥â¡¼¥É¤Ç¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£)

+ + +

FTP ¤Î¥¢¥Ã¥×¥í¡¼¥É¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Î?

+

¸½»þÅÀ¤Ç¤Ï¡¢mod_proxy ¤Î FTP ¥µ¥Ý¡¼¥È¤Ï GET ¤Î¤ß¤Ç¤¹¡£¤â¤Á¤í¤ó + Apache ¤Î ¥×¥í¥­¥·¤ò»È¤Ã¤Æ HTTP ¤Î¥¢¥Ã¥×¥í¡¼¥É (POST ¤ä PUT) ¤ò + ¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤¹¡£

+ + +

¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Î³°¤Î FTP ¥Õ¥¡¥¤¥ë¤Ë + ¥¢¥¯¥»¥¹¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Î?

+

FTP URI ¤Ï¥í¥°¥¤¥ó¤·¤Æ¤¤¤ë¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¤Î + ÁêÂХѥ¹¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£»ÄÇ°¤Ê¤³¤È¤Ë¡¢/../ ¤Ï¥Ö¥é¥¦¥¶¤Ë¤è¤ê²ò¼á¤µ¤ì¡¢ + ¼ÂºÝ¤Ë FTP ¥µ¡¼¥Ð¤Ë¤ÏÁ÷¤é¤ì¤Ê¤¤¤¿¤á¡¢/../ ¤ò»È¤Ã¤Æ¾å°Ì¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë + Åþ㤹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£¤³¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Ë¡¢¤¤¤ï¤æ¤ë + Squid %2f ¥Ï¥Ã¥¯ ¤ò Apache ¤Î FTP ¥×¥í¥­¥·¤Ï¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£ + ¤³¤ì¤Ï Squid Proxy ¥­¥ã¥Ã¥·¥å ¤Î¤è¤¦¤Ê + ¾¤Î¤è¤¯»È¤ï¤ì¤Æ¤¤¤ë¥×¥í¥­¥·¥µ¡¼¥Ð¤Ç¤â¼è¤é¤ì¤Æ¤¤¤ëÊýË¡¤Ç¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¤Î¥Ñ¥¹¤ÎÀèƬ¤Ë /%2f ¤òÉÕ¤±¤ë¤³¤È¤Ç¡¢¥×¥í¥­¥·¤Ë + FTP ¤Î³«»Ï¥Ç¥£¥ì¥¯¥È¥ê¤ò (¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤ÎÂå¤ï¤ê¤Ë) / + ¤ËÊѤ¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¡¢/etc/motd ¤ò¼èÆÀ¤¹¤ë¤¿¤á¤Ë¤Ï + ¼¡¤Î URL ¤ò»È¤¤¤Þ¤¹:

+ +

+ ftp://user@host/%2f/etc/motd +

+ + +

¥Ö¥é¥¦¥¶¤Î URL ɽ¼¨¤Ç FTP ¤Îʿʸ¥Ñ¥¹¥ï¡¼¥É¤ò + ±£¤¹¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Î?

+

FTP ¥µ¡¼¥Ð¤Ë¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤ò»È¤Ã¤Æ¥í¥°¥¤¥ó¤¹¤ë¤¿¤á¤Ë¡¢ + Apache ¤Ï°Û¤Ê¤ëÊýË¡¤ò»È¤¤¤Þ¤¹¡£URL ¤Ë¥æ¡¼¥¶Ì¾¤È¥Ñ¥¹¥ï¡¼¥É¤¬¤Þ¤Ã¤¿¤¯ + ¤Ê¤¤¾ì¹ç¤Ï¡¢Apache ¤Ï FTP ¥µ¡¼¥Ð¤Ë anonymous ¥í¥°¥¤¥ó¤òÁ÷¤ê¤Þ¤¹¡£ + ¤Ä¤Þ¤ê¡¢

+ +

+ user: anonymous
+ password: apache_proxy@ +

+ +

¤³¤ì¤Ï anonymous ¥¢¥¯¥»¥¹¤¬ÀßÄꤵ¤ì¤¿ + ¤¹¤Ù¤Æ¤Î FTP ¥µ¡¼¥Ð¤ËÂФ·¤ÆÆ°ºî¤·¤Þ¤¹¡£

+ +

¥æ¡¼¥¶Ì¾¤ò»È¤Ã¤¿¸Ä¿ÍÊÌ¤Î¥í¥°¥¤¥ó¤Ë¤Ï¡¢URL ¤Ë¥æ¡¼¥¶Ì¾¤òÆþ¤ì¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹:

+ +

+ ftp://username@host/myfile +

+ +

¤³¤Î¥æ¡¼¥¶Ì¾¤¬Í¿¤¨¤é¤ì¤¿¤È¤­¤Ë¡¢FTP ¥µ¡¼¥Ð¤¬¥Ñ¥¹¥ï¡¼¥É¤òÍ׵᤹¤ì¤Ð + (¤â¤Á¤í¤ó¤½¤¦¤¹¤Ù¤­¤Ê¤Î¤Ç¤¹¤¬)¡¢Apache ¤Ï 401 + (Authorization required) ¤òÊÖ¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢¥Ö¥é¥¦¥¶¤Ï¥æ¡¼¥¶Ì¾ + ¥Ñ¥¹¥ï¡¼¥É¤ÎÆþÎÏ¥À¥¤¥¢¥í¥°¤òɽ¼¨¤·¤Þ¤¹¡£¥Ñ¥¹¥ï¡¼¥É¤¬ÆþÎϤµ¤ì¤¿¸å¡¢ + ºÆ¤ÓÀܳ¤ò»î¤ß¡¢À®¸ù¤¹¤ì¤Ð¥ê¥¯¥¨¥¹¥È¤·¤¿¥ê¥½¡¼¥¹¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£ + ¤³¤ÎÊýË¡¤ÎÍøÅÀ¤Ï¥Ö¥é¥¦¥¶¤¬¥Ñ¥¹¥ï¡¼¥É¤òʿʸ¤Çɽ¼¨¤·¤Ê¤¤¤³¤È¤Ç¤¹¡£ + (¤â¤·ºÇ½é¤«¤é

+ +

+ ftp://username:password@host/myfile +

+ +

¤ÈÆþÎϤ·¤¿¾ì¹ç¤Ë¤Ïɽ¼¨¤µ¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹¡£)

+ +

Ãí

+

Á÷¿®¤µ¤ì¤ë¥Ñ¥¹¥ï¡¼¥É¤Ï¡¢°Å¹æ²½¤µ¤ì¤ÆÁ÷¤é¤ì¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¥Ö¥é¥¦¥¶¤È Apache ¥×¥í¥­¥·¥µ¡¼¥Ð¤Ï base64 ¤ÇÉä¹æ²½¤µ¤ì¤¿ + ʸ»úÎó¤È¤·¤Æ¡¢Apache ¥×¥í¥­¥·¤È FTP ¥µ¡¼¥Ð¤Î´Ö¤Ïʿʸ¤È¤·¤ÆÁ÷¤é¤ì¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢HTTP ¤ò»È¤Ã¤Æ HTTP ¤ò¥¢¥¯¥»¥¹¤¹¤ëÁ° (¤â¤·¤¯¤Ï¡¢¤½¤â¤½¤â + ¸Ä¿ÍŪ¤Ê¥Õ¥¡¥¤¥ë¤ò FTP ¤Ç¥¢¥¯¥»¥¹¤¹¤ëÁ°) ¤Ë¤è¤¯¹Í¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + °ÂÁ´¤Ç¤Ê¤¤ÄÌ¿®Ï©¤ò»È¤Ã¤¿¾ì¹ç¤Ï¡¢ÅðÄ°¼Ô¤ËÅÓÃæ¤Ç¥Ñ¥¹¥ï¡¼¥É¤òÅð¤Þ¤ì¤ë + ²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£

+
+ +
top
+
+

ÃÙ¤¤µ¯Æ°

+

ProxyBlock ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢ + ¸å¤Î¥Æ¥¹¥È¤Î¤¿¤á¤Ëµ¯Æ°»þ¤Ë¥Û¥¹¥È¤Î + IP ¥¢¥É¥ì¥¹¤¬Ä´¤Ù¤é¤ì¤Æ¥­¥ã¥Ã¥·¥å¤µ¤ì¤Þ¤¹¡£¥Û¥¹¥È̾¤Î¥ë¥Ã¥¯¥¢¥Ã¥×¤Î + ®¤µ¤Ë¤è¤Ã¤Æ¤Ï¡¢¿ôÉà (¤«¤½¤ì°Ê¾å) ¤«¤«¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+
top
+
+

¥¤¥ó¥È¥é¥Í¥Ã¥È¥×¥í¥­¥·

+

¥¤¥ó¥È¥é¥Í¥Ã¥È¤Ë¤¢¤ë Apache ¥×¥í¥­¥·¥µ¡¼¥Ð¤Ï³°Éô¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò + ²ñ¼Ò¤Î¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤òÄ̤·¤ÆÁ÷¤é¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£(¤³¤Î¤¿¤á¤Ë¤Ï + ¸Ä¡¹¤Î scheme ¤Ë¤Ä¤¤¤Æ¤½¤ì¤¾¤ì¡¢¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î + ¥×¥í¥­¥·¤Ë¥Õ¥©¥ï¡¼¥É¤µ¤ì¤ë¤è¤¦¤Ë + ProxyRemote ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ÀßÄꤷ¤Æ¤¯¤À¤µ¤¤)¡£¤·¤«¤·¥¤¥ó¥È¥é¥Í¥Ã¥ÈÆâ¤Î¥ê¥½¡¼¥¹¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤È¤­¤Ï¡¢ + ¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤òÄ̤µ¤Ê¤¤¤Ç¤â¥¢¥¯¥»¥¹¤Ç¤­¤Þ¤¹¡£ + ¤É¤Î¥Û¥¹¥È¤¬¥¤¥ó¥È¥é¥Í¥Ã¥È¤Ë°¤·¡¢Ä¾ÀÜ¥¢¥¯¥»¥¹¤¹¤Ù¤­¤«¤ò»ØÄꤹ¤ë¤Ë¤Ï¡¢ + NoProxy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + Ìò¤ËΩ¤Á¤Þ¤¹¡£

+ +

¥¤¥ó¥È¥é¥Í¥Ã¥ÈÆâ¤Î¥æ¡¼¥¶¤Ï WWW ¤Î¥ê¥¯¥¨¥¹¥È¤Ç¥í¡¼¥«¥ë¥É¥á¥¤¥ó¤ò + ¾Êά¤¹¤ë¤³¤È¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£http://somehost.example.com/ + ¤È¤¤¤¦¥ê¥¯¥¨¥¹¥È¤ÎÂå¤ï¤ê¤Ë "http://somehost/" ¤ò¥ê¥¯¥¨¥¹¥È¤·¤¿¤ê¤·¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Ê¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¡¢¥µ¡¼¥Ð¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¥í¡¼¥«¥ë¥É¥á¥¤¥ó¤¬ + °ÅÌۤΤ¦¤Á¤Ë»È¤ï¤ì¤Æ¤¤¤ë¤È²ò¼á¤·¤Æ¡¢Ã±½ã¤Ë¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤¹¤ë¤â¤Î¤â + ¾¦ÍÑ¥×¥í¥­¥·¥µ¡¼¥Ð¤ÎÃæ¤Ë¤Ï¤¢¤ê¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤¬ ¥×¥í¥­¥·¤Î¥µ¡¼¥Ó¥¹ÍѤËÀßÄꤵ¤ì¤Æ¤¤¤Æ + ProxyDomain ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + »ÈÍѤµ¤ì¤¿¾ì¹ç¤Ë¤Ï¡¢Apache ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Ë¥ê¥À¥¤¥ì¥¯¥È±þÅú¤òÁ÷¤Ã¤Æ¡¢ + Àµ¤·¤¤¡¢´°Á´¤Ê ((ÌõÃí: fully qualified)) + ¥µ¡¼¥Ð¤Î¥¢¥É¥ì¥¹¤ËÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤Î¤è¤¦¤Ë + ¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤È¡¢¥æ¡¼¥¶¤Î¥Ö¥Ã¥¯¥Þ¡¼¥¯¤¬Àµ¤·¤¤´°Á´¤Ê¥Û¥¹¥È̾¤ò´Þ¤à + ¤³¤È¤Ë¤â¤Ê¤ë¤¿¤á¡¢¤è¤ê¹¥¤Þ¤·¤¤ÊýË¡¤È¸À¤¨¤ë¤Ç¤·¤ç¤¦¡£

+
top
+
+

¥×¥í¥È¥³¥ë¤ÎÄ´À°

+

Keepalive ¤ä HTTP/1.1 ¤òŬÀڤ˼ÂÁõ¤·¤Æ¤¤¤Ê¤¤¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¥µ¡¼¥Ð¤¬ + ¤¢¤ë¾õ¶·¤Ç¡¢HTTP/1.0 ¤Ç keepalive ¤ò̵¤·¤Ë¤·¤Æ¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ë¤¿¤á¤Î + ´Ä¶­ÊÑ¿ô¤¬Æó¤Ä¤¢¤ê¤Þ¤¹¡£¤³¤ì¤é¤Ï SetEnv ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤷ¤Þ¤¹¡£

+ +

force-proxy-request-1.0 ¤È proxy-nokeepalive + ¤¬¤½¤Î´Ä¶­ÊÑ¿ô¤Ç¤¹¡£

+ +

+ <Location /buggyappserver/>
+ + ProxyPass http://buggyappserver:7001/foo/
+ SetEnv force-proxy-request-1.0 1
+ SetEnv proxy-nokeepalive 1
+ + </Location> +

+
+
top
+

AllowCONNECT ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥×¥í¥­¥·¤ò·Ðͳ¤·¤Æ¡¢¤É¤Î¥Ý¡¼¥È¤Ë CONNECT +¤Ç¤­¤ë¤«¤ò»ØÄꤹ¤ë
¹½Ê¸:AllowCONNECT port [port] ...
¥Ç¥Õ¥©¥ë¥È:AllowCONNECT 443 563
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

AllowCONNECT ¤Ï¥×¥í¥­¥·¤Î CONNECT + ¥á¥½¥Ã¥É¤¬Àܳ¤òµö²Ä¤¹¤ë¥Ý¡¼¥ÈÈÖ¹æ¤Î¥ê¥¹¥È¤ò»ØÄꤷ¤Þ¤¹¡£ + º£Æü¤Î¥Ö¥é¥¦¥¶¤Ï¡¢https ¥³¥Í¥¯¥·¥ç¥ó¤¬Í׵ᤵ¤ì¤Æ¤¤¤Æ¡¢ + HTTP ¾å¤Ç¤Î¥×¥í¥­¥·¤Ë¤è¤ë¥È¥ó¥Í¥ê¥ó¥°¤¬¤Ç¤­¤ë¤È¤­¤Ë¡¢ + ¤³¤Î¥á¥½¥Ã¥É¤ò»È¤¤¤Þ¤¹¡£

+ +

¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Ç¤Ï¡¢https ¤Î¥Ç¥Õ¥©¥ë¥È¥Ý¡¼¥È (443) ¤È + ¥Ç¥Õ¥©¥ë¥È¤Î snews ¥Ý¡¼¥È (563) ¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¥Ç¥Õ¥©¥ë¥È¤ò¾å½ñ¤­¤·¤Æ¡¢¥ê¥¹¥È¤Ëµ­ºÜ¤·¤¿¥Ý¡¼¥È¤Ë¤Î¤ßÀܳ¤òµö²Ä¤·¤¿¤¤¾ì¹ç¡¢ + AllowCONNECT ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Þ¤¹¡£

+ +

CONNECT ¤ò»ÈÍѤ¹¤ë¤Ë¤Ï¡¢mod_proxy_connect + ¤¬¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
top
+

NoProxy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:ľÀÜÀܳ¤¹¤ë ¥Û¥¹¥È¡¢¥É¥á¥¤¥ó¡¢¥Í¥Ã¥È¥ï¡¼¥¯
¹½Ê¸:NoProxy host [host] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¤¥ó¥È¥é¥Í¥Ã¥ÈÃæ¤Î Apache ¥×¥í¥­¥·¥µ¡¼¥Ð¤Ë¤Î¤ß + Í­ÍѤǤ¹¡£NoProxy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¶õÇò¶èÀÚ¤ê¤Ç¡¢ + ¥µ¥Ö¥Í¥Ã¥È¡¢IP ¥¢¥É¥ì¥¹¡¢¥Û¥¹¥È¡¢¥É¥á¥¤¥ó¤Î¥ê¥¹¥È¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤³¤ì¤é¤Î¤É¤ì¤«¤Ë¥Þ¥Ã¥Á¤¹¤ë¥Û¥¹¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï ProxyRemote ¤ÇÀßÄꤵ¤ì¤¿¥×¥í¥­¥·¥µ¡¼¥Ð¤Ë + ¥Õ¥©¥ï¡¼¥É¤µ¤ì¤º¡¢Ä¾ÀܽèÍý¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ ProxyRemote * http://firewall.mycompany.com:81
+ NoProxy .mycompany.com 192.168.112.0/21 +

+ +

NoProxy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î host °ú¿ô¤Ï + °Ê²¼¤Î¼ïÎà¤Î¤É¤ì¤«¤Ç¤¹:

+ +
+ +
Domain
+
+

Domain ¤ÏÀèƬ¤Ë¥Ô¥ê¥ª¥É¤ÎÃ夤¤¿Éôʬ DNS ¥É¥á¥¤¥ó̾¤Ç¤¹¡£ + Ʊ°ì DNS ¥É¥á¥¤¥óµÚ¤Ó¥¾¡¼¥ó (¤¹¤Ê¤ï¤Á¡¢¥Û¥¹¥È̾¤ÎËöÈø¤¬¤¹¤Ù¤Æ + Domain ¤Ç½ª¤ï¤Ã¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È) ¤Ë°¤¹¤ë¥Û¥¹¥È¤Î¥ê¥¹¥È¤ò + ɽ¤·¤Þ¤¹)¡£

+ +

Îã

+ .com .apache.org. +

+ +

Domain ¤ò Hostname ¤È¶èÊ̤¹¤ë¤¿¤á¤Ë (°Ọ̃Ū¤Ë¤â¹½Ê¸Åª¤Ë¤â¡£DNS ¥É¥á¥¤¥ó¤â + DNS ¤Î A ¥ì¥³¡¼¥É¤ò»ý¤Ä¤³¤È¤¬¤Ç¤­¤ë¤Î¤Ç¤¹!)¡¢Domain ¤Ï + ¾ï¤Ë¥Ô¥ê¥ª¥É¤Ç»Ï¤Þ¤ê¤Þ¤¹¡£

+ +

Ãí

+

¥É¥á¥¤¥ó̾¤ÎÈæ³Ó¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¤Ë¹Ô¤Ê¤ï¤ì¡¢Domain + ¤Ï¾ï¤Ë DNS ¥Ä¥ê¡¼¤Î¥ë¡¼¥È¤«¤é»Ï¤Þ¤ë¤â¤Î¤È¤ß¤Ê¤µ¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢ + ¼¡¤ÎÆó¤Ä¤Î¥É¥á¥¤¥ó .MyDomain.com ¤È + .mydomain.com. (ºÇ¸å¤Î¥Ô¥ê¥ª¥É¤ËÃíÌÜ) ¤ÏƱ°ì¤Ç¤¢¤ë¤È + ¤ß¤Ê¤µ¤ì¤Þ¤¹¡£¥É¥á¥¤¥ó¤ÎÈæ³Ó¤Ï DNS ¥ë¥Ã¥¯¥¢¥Ã¥×¤Ê¤·¤Ç¹Ô¤Ê¤ï¤ì¤ë¤¿¤á¡¢ + ¥µ¥Ö¥Í¥Ã¥È¤ÎÈæ³Ó¤è¤ê¤â¤º¤Ã¤È¸úΨŪ¤Ç¤¹¡£

+
+ + +
SubNet
+
+

SubNet ¤Ï¿ôÃÍ·Á¼° (¥É¥Ã¥È¤Ç¶èÀÚ¤é¤ì¤¿»Í¤Ä¤Î¿ô»ú) ¤Î + Éôʬ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥¢¥É¥ì¥¹¤Ç¤¹¡£¸å¤Ë¥¹¥é¥Ã¥·¥å¤È Subnet + ¤Î°ÕÌ£¤Î¤¢¤ë¥Ó¥Ã¥È¿ô¤ò»ØÄꤹ¤ë¥Í¥Ã¥È¥Þ¥¹¥¯¤È¤ò³¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¶¦Ä̤Υͥåȥ¥¯¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»È¤Ã¤ÆÅþ㤹¤ë¤³¤È¤Î¤Ç¤­¤ë¥µ¥Ö¥Í¥Ã¥È¤ò + ɽ¤¹¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£ÌÀ¼¨Åª¤Ë¥Í¥Ã¥È¥Þ¥¹¥¯¤ò»ØÄꤷ¤Ê¤¤¾ì¹ç¤Ï + ºÇ¸å¤Î¾Êά¤µ¤ì¤¿ (¤â¤·¤¯¤ÏÃͤ¬ 0 ¤Î) ¿ô»ú¤¬¥Þ¥¹¥¯¤ò»ØÄꤷ¤Þ¤¹¡£ + (¤³¤Î¾ì¹ç¤Ï¡¢¥Í¥Ã¥È¥Þ¥¹¥¯¤Ï 8 ¥Ó¥Ã¥Èñ°Ì¤Ç¤·¤«»ØÄê¤Ç¤­¤Þ¤»¤ó¡£) + Îã:

+ +
+
192.168 ¤â¤·¤¯¤Ï 192.168.0.0
+
¥µ¥Ö¥Í¥Ã¥È 192.168.0.0 ¤È°ÅÌۤΠ16 ¥Ó¥Ã¥ÈÍ­¸ú¤Ê¥Í¥Ã¥È¥Þ¥¹¥¯ + (255.255.0.0 ¤È¤¤¤¦¥Í¥Ã¥È¥Þ¥¹¥¯¤Î·Á¼°¤Ç»È¤ï¤ì¤ë¤³¤È¤â + ¤¢¤ê¤Þ¤¹)
+
192.168.112.0/21
+
¥µ¥Ö¥Í¥Ã¥È192.168.112.0/21 ¤È 21 ¥Ó¥Ã¥ÈÍ­¸ú¤Ê + ¥Í¥Ã¥È¥Þ¥¹¥¯ (255.255.248.0 ¤È¤¤¤¦·Á¼°¤Ç»È¤ï¤ì¤ë¤³¤È¤â + ¤¢¤ê¤Þ¤¹)
+
+ +

ÆÃÊ̤ʾì¹ç¤Ë¡¢32 ¥Ó¥Ã¥ÈÍ­¸ú¤Ê SubNet ¤Ï + IPAddr ¤ÈƱÅù¤Ç¡¢ + 0 ¥Ó¥Ã¥ÈÍ­¸ú¤Ê SubNet (Î㤨¤Ð¡¢0.0.0.0/0) ¤Ï + ¤¹¤Ù¤Æ¤Î IP ¥¢¥É¥ì¥¹¤Ë¥Þ¥Ã¥Á¤¹¤ëÄê¿ô _Default_ ¤ÈƱ¤¸¤Ç¤¹¡£

+
+ + +
IPAddr
+
+

IPAddr ¤Ï¿ôÃÍ·Á¼° (¥É¥Ã¥È¤Ç¶èÀÚ¤é¤ì¤¿»Í¤Ä¤Î¿ô»ú) ¤Î + ´°Á´¥¤¥ó¥¿¡¼¥Í¥Ã¥È¥¢¥É¥ì¥¹¤Ç¤¹¡£Ä̾ï¤Ï¤³¤Î¥¢¥É¥ì¥¹¤Ï¥Û¥¹¥È¤ò + ɽ¤·¤Þ¤¹¤¬¡¢É¬¤º¤·¤â¥¢¥É¥ì¥¹¤ËÂбþ¤¹¤ë DNS ¥É¥á¥¤¥ó̾¤¬¤¢¤ë¤ï¤±¤Ç¤Ï + ¤¢¤ê¤Þ¤»¤ó¡£

+ +

Îã

+ 192.168.123.7 +

+ +

Ãí

+

IPAddr ¤Ï DNS ¥·¥¹¥Æ¥à¤Ë¤è¤ê²ò·è¤µ¤ì¤ëɬÍפ¬¤Ê¤¤¤Î¤Ç¡¢ + apache ¤ÎÀ­Ç½¤¬¸þ¾å¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+
+ + +
Hostname
+
+

Hostname ¤Ï DNS ¥É¥á¥¤¥ó¥µ¡¼¥Ó¥¹¤Ë¤è¤ê°ì¤Ä¤â¤·¤¯¤Ï + Ê£¿ô¤Î IPAddr ¤Ë²ò·è²Äǽ¤Ê + ´°Á´¤Ê DNS ¥É¥á¥¤¥ó̾¤Ç¤¹¡£¤³¤ì¤Ï (Domain + ¤È°ã¤Ã¤Æ¡¢ÀâÌÀ¤Ï¾åµ­¤ò»²¾È) ÏÀÍýŪ¤Ê¥Û¥¹¥È¤òɽ¤·¡¢¾¯¤¯¤È¤â°ì¤Ä¤Î + IPAddr (¤â¤·¤¯¤Ï°ã¤¦ + IPAddr ¤Î¥Û¥¹¥È¤Î¥ê¥¹¥È) ¤Ë²ò·è + ¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó)¡£

+ +

Îã

+ prep.ai.mit.edu
+ www.apache.org +

+ +

Ãí

+

¿¤¯¤Î¾ì¹ç¡¢Hostname ¤ÎÂå¤ï¤ê¤Ë IPAddr ¤ò»ØÄꤷ¤¿Êý¤¬¡¢DNS ¥ë¥Ã¥¯¥¢¥Ã¥×¤ò + Èò¤±¤ë¤³¤È¤¬¤Ç¤­¤ë¤¿¤á¡¢¸úΨ¤¬Îɤ¯¤Ê¤ê¤Þ¤¹¡£Apache ¤Î̾Á°²ò·è¤Ï + ¥Í¡¼¥à¥µ¡¼¥Ð¤Ø¤ÎÀܳ¤¬ÃÙ¤¤ PPP ¾å¤Î¾ì¹ç¤Ê¤É¤Ë¤«¤Ê¤ê»þ´Ö¤ò¼è¤é¤ì¤ë + ¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£

+

Hostname ¤ÎÈæ³Ó¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¤Ë¹Ô¤Ê¤ï¤ì¡¢ + Hostname ¤Ï¾ï¤Ë DNS ¥Ä¥ê¡¼¤Î¥ë¡¼¥È¤«¤é»Ï¤Þ¤ë¤â¤Î¤È¤ß¤Ê¤µ¤ì¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢Æó¤Ä¤Î¥É¥á¥¤¥ó WWW.MyDomain.com ¤È + www.mydomain.com. (ºÇ¸å¤Î¥Ô¥ê¥ª¥É¤ËÃíÌÜ) ¤ÏƱ°ì¤Ç¤¢¤ë¤È + ¤ß¤Ê¤µ¤ì¤Þ¤¹¡£

+
+
+ +

»²¾È

+ +
+
top
+

<Proxy> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥×¥í¥­¥·¤µ¤ì¤ë¥ê¥½¡¼¥¹¤ËŬÍѤµ¤ì¤ë¥³¥ó¥Æ¥Ê
¹½Ê¸:<Proxy wildcard-url> ...</Proxy>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

<Proxy> ¥»¥¯¥·¥ç¥óÃæ¤Î + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Þ¥Ã¥Á¤¹¤ë¥×¥í¥­¥·¤µ¤ì¤ë¥³¥ó¥Æ¥ó¥Ä¤Ë¤Î¤ßŬÍѤµ¤ì¤Þ¤¹¡£ + ¥·¥§¥ë·Á¼°¤Î¥ï¥¤¥ë¥É¥«¡¼¥É¤¬»È¤¨¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢¼¡¤ÎÀßÄê¤Ï yournetwork.example.com ¤Î + ¥Û¥¹¥È¤Ë¤Î¤ß¥×¥í¥­¥·¥µ¡¼¥Ð¤ò·Ðͳ¤·¤¿¥¢¥¯¥»¥¹¤òµö²Ä¤·¤Þ¤¹:

+ +

+ <Proxy *>
+ + Order Deny,Allow
+ Deny from all
+ Allow from yournetwork.example.com
+ + </Proxy> +

+ +

¼¡¤ÎÎã¤Ï example.com ¤Î foo ¥Ç¥£¥ì¥¯¥È¥ê¤Î + ¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æ¡¢¥×¥í¥­¥·¥µ¡¼¥Ð¤òÄ̤·¤ÆÁ÷¤é¤ì¤¿¤È¤­¤Ë¤Ï + INCLUDES ¥Õ¥£¥ë¥¿¤òÄ̤·¤ÆÁ÷¤ë¤è¤¦¤ËÀßÄꤷ¤Þ¤¹:

+ +

+ <Proxy http://example.com/foo/*>
+ + SetOutputFilter INCLUDES
+ + </Proxy> +

+ + + +
+
top
+

ProxyBadHeader ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:±þÅú¤Ë¤ª¤«¤·¤Ê¥Ø¥Ã¥À¤¬¤¢¤ë¾ì¹ç¤Î°·¤¤Êý¤ò·è¤á¤ë
¹½Ê¸:ProxyBadHeader IsError|Ignore|StartBody
¥Ç¥Õ¥©¥ë¥È:ProxyBadHeader IsError
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
¸ß´¹À­:2.0.44 °Ê¹ß
+

ProxyBadHeader ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¹½Ê¸Åª¤Ë + ´Ö°ã¤Ã¤¿¥Ø¥Ã¥À (¤Ä¤Þ¤ê ¥³¥í¥ó¤ò´Þ¤Þ¤Ê¤¤¤â¤Î) ¤ò¼õ¤±¼è¤Ã¤¿¤È¤­¤Ë + mod_proxy ¤¬¤É¤¦¿¶¤ëÉñ¤¦¤«¤ò·è¤á¤Þ¤¹¡£°Ê²¼¤Î°ú¿ô¤ò + ¼è¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +
+
IsError
+
¥ê¥¯¥¨¥¹¥È¤òÃæ»ß¤·¤Æ 502 (Bad Gateway) ±þÅú¤òÊÖ¤¹¡£ + ¤³¤ì¤¬¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤Ç¤¹¡£
+ +
Ignore
+
´Ö°ã¤Ã¤¿¥Ø¥Ã¥À¹Ô¤ò¤½¤â¤½¤â¸ºß¤·¤Ê¤«¤Ã¤¿¤â¤Î¤È¤·¤Æ°·¤¦¡£
+ +
StartBody
+
´Ö°ã¤Ã¤¿¥Ø¥Ã¥À¹Ô¤ò¼õ¤±¼è¤Ã¤¿¤é¡¢¥Ø¥Ã¥À¤ÎÆɤ߹þ¤ß¤ò½ªÎ»¤·¤Æ¡¢ + ¤½¤ì°Ê¹ß¤Î»Ä¤ê¤ò¥Ü¥Ç¥£¤È¤·¤Æ°·¤¦¡£¤³¤ì¤Ï¥Ø¥Ã¥À¤È¥Ü¥Ç¥£¤Î´Ö¤Ë¶õ¹Ô¤òÆþ¤ì˺¤ì¤Æ + ¤·¤Þ¤Ã¤Æ¤¤¤ë¤è¤¦¤Ê¡¢¤­¤Á¤ó¤ÈÆ°ºî¤·¤Æ¤¤¤Ê¤¤¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤¬¤¢¤ë¤È¤­¤Ë¡¢ + ÌäÂê¤ò²óÈò¤¹¤ë¤Î¤ËÌò¤ËΩ¤Á¤Þ¤¹¡£
+
+ +
+
top
+

ProxyBlock ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥×¥í¥­¥·Àܳ¤ò¶Ø»ß¤¹¤ë¸ì¶ç¡¢¥Û¥¹¥È̾¡¢¥É¥á¥¤¥ó¤ò»ØÄꤹ¤ë
¹½Ê¸:ProxyBlock *|word|host|domain +[word|host|domain] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

ProxyBlock ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¶õÇò¤Ç¶èÀÚ¤é¤ì¤¿ + ¸ì¶ç¡¢¥Û¥¹¥È̾¡¢¥É¥á¥¤¥ó¤Î¥ê¥¹¥È¤ò»ØÄꤷ¤Þ¤¹¡£¥µ¥¤¥È̾¤Ë¤½¤Î¸ì¶ç¡¢¥Û¥¹¥È̾¡¢ + ¥É¥á¥¤¥ó¤ò´Þ¤à¥µ¥¤¥È¤Ø¤Î HTTP¡¢HTTPS¡¢FTP ¤Ë¤è¤ë¥É¥­¥å¥á¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤Ï + ¥×¥í¥­¥·¥µ¡¼¥Ð¤Ë¤è¤ê¥Ö¥í¥Ã¥¯¤µ¤ì¤Þ¤¹¡£¥×¥í¥­¥·¥â¥¸¥å¡¼¥ë¤Ï + µ¯Æ°»þ¤Ë¥Û¥¹¥È̾¤È»×¤·¤­¹àÌܤΠIP ¥¢¥É¥ì¥¹¤òÄ´¤Ù¡¢¸å¤Î¥Æ¥¹¥È¤Î¤¿¤á¤Ë + ¥­¥ã¥Ã¥·¥å¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢¥µ¡¼¥Ð¤Îµ¯Æ°¤¬¾¯¤·ÃÙ¤¯¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ +

Example

+ ProxyBlock joes-garage.com some-host.co.uk rocky.wotsamattau.edu +

+ +

rocky.wotsamattau.edu ¤¬ IP ¥¢¥É¥ì¥¹¤Ç»²¾È¤µ¤ì¤¿¤È¤­¤Ç¤â + ¥Þ¥Ã¥Á¤·¤Þ¤¹¡£

+ +

wotsamattau.edu ¤Î¥Þ¥Ã¥Á¤Ë¤Ï wotsamattau + ¤À¤±¤Ç¤â½½Ê¬¤Ç¤¹¡£

+ +

+ ProxyBlock * +

+ +

¤Ï¤¹¤Ù¤Æ¤Î¥µ¥¤¥È¤Ø¤ÎÀܳ¤ò¥Ö¥í¥Ã¥¯¤¹¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
top
+

ProxyDomain ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥×¥í¥­¥·¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î¥Ç¥Õ¥©¥ë¥È¤Î¥É¥á¥¤¥ó̾
¹½Ê¸:ProxyDomain Domain
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¤¥ó¥È¥é¥Í¥Ã¥ÈÆâ¤Î Apache ¥×¥í¥­¥·¥µ¡¼¥Ð¤Ë¤Î¤ß + Í­ÍѤǤ¹¡£ProxyDomain ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + apache ¥×¥í¥­¥·¥µ¡¼¥Ð¤¬Â°¤¹¤ë¥Ç¥Õ¥©¥ë¥È¤Î¥É¥á¥¤¥ó¤ò»ØÄꤷ¤Þ¤¹¡£ + ¥É¥á¥¤¥ó̾¤Î̵¤¤¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¤¿¾ì¹ç¡¢ÀßÄꤵ¤ì¤¿ Domain + ¤¬Äɲ䵤줿Ʊ¤¸¥Û¥¹¥È¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È±þÅú¤¬ÊÖ¤µ¤ì¤Þ¤¹¡£

+ +

Îã

+ ProxyRemote * http://firewall.mycompany.com:81
+ NoProxy .mycompany.com 192.168.112.0/21
+ ProxyDomain .mycompany.com +

+ +
+
top
+

ProxyErrorOverride ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥×¥í¥­¥·¤µ¤ì¤¿¥³¥ó¥Æ¥ó¥Ä¤Î¥¨¥é¡¼¥Ú¡¼¥¸¤ò¾å½ñ¤­¤¹¤ë
¹½Ê¸:ProxyErrorOverride On|Off
¥Ç¥Õ¥©¥ë¥È:ProxyErrorOverride Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.0 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤ò»ÈÍѤ·¤Æ¤¤¤Æ¡¢ + ¥¨¥ó¥É¥æ¡¼¥¶¤ËÁ÷¤é¤ì¤ë¥¨¥é¡¼¥Ú¡¼¥¸¤Î³°¸«¤ò¶¦Ä̤Τâ¤Î¤Ë¤·¤¿¤¤¤È¤­¤Ë + Í­ÍѤǤ¹¡£¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï (mod_include ¤Î SSI ¤Ë¤è¤Ã¤Æ) + ¥¤¥ó¥¯¥ë¡¼¥É¤µ¤ì¤¿¥Õ¥¡¥¤¥ë¤¬¥¨¥é¡¼¥³¡¼¥É¤ò¼èÆÀ¤·¤Æ¡¢Àµ¤·¤¯Æ°ºî¤ò + ¤¹¤ë¤è¤¦¤Ë¤â¤·¤Þ¤¹ (¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤Ï¡¢¥×¥í¥­¥·¤µ¤ì¤¿¥µ¡¼¥Ð¤Î + ¥¨¥é¡¼¥Ú¡¼¥¸¤Îɽ¼¨¤Ç¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÍ­¸ú¤Ë¤¹¤ë¤È SSI ¤Î¥¨¥é¡¼ + ¥á¥Ã¥»¡¼¥¸¤òɽ¼¨¤·¤Þ¤¹)¡£

+ +
+
top
+

ProxyIOBufferSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:ÆâÉô¥Ç¡¼¥¿¥¹¥ë¡¼¥×¥Ã¥È¥Ð¥Ã¥Õ¥¡¤Î¥µ¥¤¥º¤ò·èÄꤹ¤ë
¹½Ê¸:ProxyIOBufferSize bytes
¥Ç¥Õ¥©¥ë¥È:ProxyIOBufferSize 8192
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

ProxyIOBufferSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÆþÎÏ¤È + ½ÐÎÏÍѤΰì»þ¥á¥â¥ê¤È¤·¤Æ»È¤ï¤ì¤ëÆâÉô¥Ð¥Ã¥Õ¥¡¤Î¥µ¥¤¥º¤òÄ´À°¤·¤Þ¤¹¡£ + ¥µ¥¤¥º¤Ï 8192 °Ê²¼¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

¤Û¤È¤ó¤É¤¹¤Ù¤Æ¤Î¾ì¹ç¡¢¤³¤ÎÃͤòÊѹ¹¤¹¤ëÍýͳ¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +
+
top
+

<ProxyMatch> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:Àµµ¬É½¸½¤Ç¤Î¥Þ¥Ã¥Á¤Ë¤è¤ë¥×¥í¥­¥·¥ê¥½¡¼¥¹ÍѤΥǥ£¥ì¥¯¥Æ¥£¥Ö¥³¥ó¥Æ¥Ê
¹½Ê¸:<ProxyMatch regex> ...</ProxyMatch>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

<ProxyMatch> ¤Ï URL ¤Î¥Þ¥Ã¥Á¤Ë + Àµµ¬É½¸½¤òÍѤ¤¤ë¤³¤È¤ò½ü¤¤¤Æ <Proxy> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈƱ¤¸¤Ç¤¹¡£

+ +
+
top
+

ProxyMaxForwards ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤¬¥Õ¥©¥ï¡¼¥É¤µ¤ì¤ë¥×¥í¥­¥·¤ÎºÇÂç¿ô
¹½Ê¸:ProxyMaxForwards number
¥Ç¥Õ¥©¥ë¥È:ProxyMaxForwards 10
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
¸ß´¹À­:Apache 2.0 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

ProxyMaxForwards ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥ê¥¯¥¨¥¹¥È¤Ë Max-Forwards ¥Ø¥Ã¥À¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ë + ¥ê¥¯¥¨¥¹¥È¤¬Ä̲á²Äǽ¤Ê¥×¥í¥­¥·¤ÎºÇÂç¿ô¤òÀßÄꤷ¤Þ¤¹¡£¤³¤ì¤Ï + ¥×¥í¥­¥·¤Î̵¸Â¥ë¡¼¥×¤ä DoS ¹¶·â¤òËɤ°¤¿¤á¤ËÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

Îã

+ ProxyMaxForwards 15 +

+ +
+
top
+

ProxyPass ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥ê¥â¡¼¥È¥µ¡¼¥Ð¤ò¥í¡¼¥«¥ë¥µ¡¼¥Ð¤Î URL ¶õ´Ö¤Ë¥Þ¥Ã¥×¤¹¤ë
¹½Ê¸:ProxyPass [path] !|url [key=value key=value ...]]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥ê¥â¡¼¥È¥µ¡¼¥Ð¤ò¥í¡¼¥«¥ë¥µ¡¼¥Ð¤Î̾Á°¶õ´Ö¤Ë + ¥Þ¥Ã¥×¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£¥í¡¼¥«¥ë¥µ¡¼¥Ð¤ÏÄ̾ï¤Î°ÕÌ£¤Ç¤Î¥×¥í¥­¥·¤È + ¤·¤Æ¤ÏÆ°ºî¤»¤º¡¢¥ê¥â¡¼¥È¥µ¡¼¥Ð¤Î¥ß¥é¡¼¤È¤·¤Æ¿¶¤ëÉñ¤¤¤Þ¤¹¡£ + path ¤Ï¥í¡¼¥«¥ë¤Î²¾Áۥѥ¹¤Î̾Á°¤Ç¤¹¡£url ¤Ï + ¥ê¥â¡¼¥È¥µ¡¼¥Ð¤ÎÉôʬ URL ¤Ë¤Ê¤ê¡¢¥¯¥¨¥ê¡¼Ê¸»úÎó¤ò´Þ¤à¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£

+ +
ProxyPass ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤Ã¤Æ¤¤¤ë¤È¤­¤Ï ProxyRequests ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÄ̾ï¤Ï + off ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤Ù¤­¤Ç¤¹¡£
+ +

¥í¡¼¥«¥ë¥µ¡¼¥Ð¤Î¥¢¥É¥ì¥¹¤¬ http://example.com/ ¤Ç¤¢¤ë¤È + ¤·¤Þ¤¹¡£¤¹¤ë¤È¡¢

+ +

+ ProxyPass /mirror/foo/ http://backend.example.com/ +

+ +

¤ÈÀßÄꤹ¤ë¤È http://example.com/mirror/foo/bar ¤Ø¤Î + ¥ê¥¯¥¨¥¹¥È¤¬ÆâÉôŪ¤Ë http://backend.example.com/bar ¤Ø¤Î + ¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤ËÊÑ´¹¤µ¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ò¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤·¤¿¤¯¤Ê¤¤¤È¤­¤Ë ! ¤Ï + Ìò¤ËΩ¤Á¤Þ¤¹¡£Î㤨¤Ð¡¢

+ +

+ ProxyPass /mirror/foo/i !
+ ProxyPass /mirror/foo http://backend.example.com +

+ +

¤Ï /mirror/foo/i ¤ò½ü¤¯ + /mirror/foo ¤Ø¤Î¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤ò + backend.example.com ¤Ë¥×¥í¥­¥·¤·¤Þ¤¹¡£

+ +

Ãí

+

½çÈ֤ϽÅÍפǤ¹¡£°ìÈÌŪ¤Ê ProxyPass + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÁ°¤Ë + ½ü³°¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÃÖ¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£

+
+ +

2.1 ¤Î¿·µ¡Ç½¤Ç¡¢¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È¤ÎÀܳ¤Ë¥×¡¼¥ë¤µ¤ì¤¿¥³¥Í¥¯¥·¥ç¥ó¤ò + »È¤¨¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£key=value ·Á¼°¤Î¥Ñ¥é¥á¡¼¥¿¤Ç + ¤³¤Î¥³¥Í¥¯¥·¥ç¥ó¥×¡¼¥ê¥ó¥°¤ÎÄ´À°¤¬¤Ç¤­¤Þ¤¹¡£Hard Maximum + ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤϡ¢Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë MPM ¤Ç¤Î¥×¥í¥»¥¹Åö¤¿¤ê¤Î¥¹¥ì¥Ã¥É¿ô¤È + Ʊ¤¸¿ô¤Î¥³¥Í¥¯¥·¥ç¥ó¿ô¤Ç¤¹¡£prefork MPM ¤Ç¤ÏÄ̾ï¤Ï 1 ¤Ç¡¢worker MPM ¤Ç¤Ï + ThreadsPerChild ¤ÇÄ´À°¤µ¤ì¤Þ¤¹¡£

+ +

min ¤ÎÀßÄê¤Ç¡¢¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È¤Î´Ö¤Ë²¿ËܤΥ³¥Í¥¯¥·¥ç¥ó¤ò + ¾ï»þ³«¤¯¤«¤¬·è¤Þ¤ê¤Þ¤¹¡£Soft Maximum smax ¤Î¿ô¤Ë + 㤹¤ë¤Þ¤ÇɬÍפ˱þ¤¸¤Æ¥³¥Í¥¯¥·¥ç¥ó¤ÏÀ¸À®¤µ¤ì¤Þ¤¹¡£smax + ¤òĶ¤¨¤¿¿ô¤Î¥³¥Í¥¯¥·¥ç¥ó¤Ï¡¢À¸Â¸»þ´Ö ttl ¤ÇÀÚÃǤµ¤ì¤Þ¤¹¡£ + ¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È Hard Maximum max ¤Î¿ô°Ê¾å¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò + À¸À®¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +

+ ProxyPass /example http://backend.example.com smax=5 max=20 ttl=120 retry=300 +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¥Ñ¥é¥á¡¼¥¿¥Ç¥Õ¥©¥ë¥ÈÃÍÀâÌÀ
min0¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È¤ÎÀܳ¤Ç + ¾ï¤Ë³«¤¤¤Æ¤¤¤ë¥³¥Í¥¯¥·¥ç¥ó¿ô¤ÎºÇ¾®ÃÍ
max1...n¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È¤ÎÀܳ¿ô¤Î Hard Maximum + (ÌõÃí: ¥Ï¡¼¥É¥ê¥ß¥Ã¥È)¡£ + ¥Ç¥Õ¥©¥ë¥ÈÃͤϡ¢»ÈÍѤ·¤Æ¤¤¤ë MPM ¤Î¥×¥í¥»¥¹¤¢¤¿¤ê¤Î¥¹¥ì¥Ã¥É¿ô¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + Prefork MPM ¤Ç¤Ï¾ï¤Ë 1 ¤Ç¡¢Worker MPM ¤Ç¤Ï ThreadsPerChild + ¤ÇÄ´Àá¤Ç¤­¤Þ¤¹¡£Hard Maximum °Ê¾å¤Ë¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò + À¸À®¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
smaxmaxÀܳ¿ô¤Î Soft Maximum (ÌõÃí: ¥½¥Õ¥È¥ê¥ß¥Ã¥È)¤Þ¤Ç¡¢ + ¥³¥Í¥¯¥·¥ç¥ó¤ÏɬÍפ˱þ¤¸¤ÆÀ¸À®¤µ¤ì¤Þ¤¹¡£ + smax ¤òĶ¤¨¤¿¿ô¤Î¥³¥Í¥¯¥·¥ç¥ó¤ÏÀ¸Â¸»þ´Ö ttl + ¤ÇÀÚÃǤµ¤ì¤Þ¤¹¡£ +
ttl-smax ¿ô¤òĶ¤¨¤¿Èó³èÆ°¾õÂ֤Υ³¥Í¥¯¥·¥ç¥ó¤ÎÀ¸Â¸»þ´Ö¤ò¡¢ + ÉäǻØÄꤷ¤Þ¤¹¡£¤³¤Î´ü´ÖÆâ¤Ë»ÈÍѤµ¤ì¤Ê¤«¤Ã¤¿¥³¥Í¥¯¥·¥ç¥ó¤Ï¡¢ + Á´¤ÆÊĤ¸¤é¤ì¤Þ¤¹¡£ +
timeoutTimeout¥³¥Í¥¯¥·¥ç¥ó¥¿¥¤¥à¥¢¥¦¥È¤òÉäǻØÄꤷ¤Þ¤¹¡£Æä˻ØÄꤵ¤ì¤Ê¤±¤ì¤Ð¡¢ + ¥Õ¥ê¡¼¤Ê¥³¥Í¥¯¥·¥ç¥ó¤ò¼èÆÀ¤Ç¤­¤ë¤Þ¤ÇÂÔ¤Á¤Þ¤¹¡£¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + max ¥Ñ¥é¥á¡¼¥¿¤È¹ç¤ï¤»¤Æ»È¤¦¤³¤È¤Ç¡¢¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È¤Î + Àܳ¿ô¤òÀ©¸æ¤¹¤ë¤Î¤Ë»È¤¤¤Þ¤¹¡£ +
acquire-ÀßÄꤹ¤ë¤È¡¢¥³¥Í¥¯¥·¥ç¥ó¥×¡¼¥ë¤«¤é¥Õ¥ê¡¼¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò¼èÆÀ¤¹¤ë¤¿¤á¤Ë + ÂÔµ¡¤¹¤ëÂÔ¤Á»þ´Ö¤ÎºÇÂçÃͤˤʤê¤Þ¤¹¡£¥Õ¥ê¡¼¤Î¥³¥Í¥¯¥·¥ç¥ó¤¬¥×¡¼¥ë¤Ë¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï¡¢ + SERVER_BUSY ¥¹¥Æ¡¼¥¿¥¹¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤µ¤ì¤Þ¤¹¡£ +
keepaliveOff¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È Apache ¤Î´Ö¤Ë¥Õ¥¡¥¤¥¢¡¼¥¦¥©¡¼¥ë¤¬¤¢¤ë¾ì¹ç¤Ë¤Ï¡¢ + ¤³¤Î¥Ñ¥é¥á¡¼¥¿¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Ï±ý¡¹¤Ë¤·¤Æ¡¢ + Èó³èÆ°¾õÂ֤Υ³¥Í¥¯¥·¥ç¥ó¤òÍî¤È¤½¤¦¤È¤·¤Þ¤¹¡£ + ¤³¤Î¥Õ¥é¥°¤Ï OS ¤Ë»Ø¼¨¤·¤Æ¡¢KEEP_ALIVE ¥á¥Ã¥»¡¼¥¸¤òÈó³èÆ°¾õÂ֤Π+ ¥³¥Í¥¯¥·¥ç¥ó¤Ç¤âÁ÷¤ë¤è¤¦¤Ë¤·¤Þ¤¹ (´Ö³Ö¤Ï OS ¤Î¥°¥í¡¼¥Ð¥ëÀßÄê¤Ë°Í¸¤·¡¢ + Ä̾ï¤Ï 120ms ´Ö³Ö) ¡£¤³¤ì¤Ë¤è¤Ã¤Æ¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Ë¤è¤Ã¤Æ¥³¥Í¥¯¥·¥ç¥ó¤¬ + Íî¤È¤µ¤ì¤ë¤³¤È¤òËɤ²¤Þ¤¹¡£keepalive ¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢¤³¤Î¥×¥í¥Ñ¥Æ¥£¤ò + On ¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ +
retry60¥³¥Í¥¯¥·¥ç¥ó¤ò¥×¡¼¥ê¥ó¥°¤¹¤ë¤¿¤á¤Î¡¢¥ê¥È¥é¥¤¤Î¥¿¥¤¥à¥¢¥¦¥È¤òÉÃ¤Ç + »ØÄꤷ¤Þ¤¹¡£¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤Ø¤Î¥³¥Í¥¯¥·¥ç¥ó¥×¡¼¥ê¥ó¥°¤¬¼ºÇÔ¤·¤¿¾ì¹ç¤Ï¡¢ + ¥¿¥¤¥à¥¢¥¦¥È¤Î´ü´Ö¤¬²á¤®¤ë¤Þ¤Ç¡¢¤½¤Î¥µ¡¼¥Ð¤Ë¥ê¥¯¥¨¥¹¥È¤ò¥Õ¥©¥ï¡¼¥É¤·¤Þ¤»¤ó¡£ + ¤³¤Îµ¡Ç½¤ò»È¤¦¤È¡¢¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤ò¥á¥ó¥Æ¥Ê¥ó¥¹¤Î¤¿¤á¤Ë¥·¥ã¥Ã¥È¥À¥¦¥ó¤·¡¢ + ¸å¤Ç¥ª¥ó¥é¥¤¥ó¤ËÉüµ¢¤µ¤»¤ë¤È¤¤¤Ã¤¿¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +
loadfactor1¥ï¡¼¥«¡¼¤¢¤¿¤ê¤ÎÉé²Ù·¸¿ô¤Ç¤¹¡£BalancerMember ¤Ç»È¤¤¤Þ¤¹¡£ + 1 ¤«¤é 100 ¤Þ¤Ç¤Î¿ô»ú¤Ç¤½¤Î¥ï¡¼¥«¡¼¤ËÂФ¹¤ëÀµµ¬²½¤µ¤ì¤¿Éé²ÙΨ¤ò»ØÄꤷ¤Þ¤¹¡£ +
route-¥í¡¼¥É¥Ð¥é¥ó¥µ¤Ç»È¤Ã¤¿¾ì¹ç¡¢¥ï¡¼¥«¡¼¤Î¥ë¡¼¥Æ¥£¥ó¥°¤ò¤·¤Þ¤¹¡£ + ¥ë¡¼¥È¤Ï¥»¥Ã¥·¥ç¥ó ID ¤ËÉղ䵤줿Ãͤˤʤê¤Þ¤¹¡£ +
redirect-¥ï¡¼¥«¡¼¤Î¥ê¥À¥¤¥ì¥¯¥·¥ç¥ó·ÐÏ©¤Ç¤¹¡£¤³¤ÎÃͤÏÄ̾ï¤Ï¡¢ + °ÂÁ´¤Ë¥¯¥é¥¹¥¿¤«¤é¥Î¡¼¥É¤ò¼è¤êµî¤ëÀßÄê¤òưŪ¤ËÆþ¤ì¤ë¤¿¤á¤Ë»È¤¤¤Þ¤¹¡£ + ¥»¥Ã¥·¥ç¥ó ID ¤Î̵¤¤¥ê¥¯¥¨¥¹¥ÈÁ´¤Æ¤ò»ØÄꤷ¤¿¾ì¹ç¤Ï¡¢ + ¤³¤ÎÃͤÈƱ¤¸¥ë¡¼¥Æ¥£¥ó¥°¥Ñ¥é¥á¡¼¥¿¤ò»ý¤Ä + BalancerMember ¤Ë¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤Þ¤¹¡£ +
+ +

Proxy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥¹¥­¡¼¥à¤¬ balancer:// ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + ¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤È¼ÂºÝ¤Ë¤ÏÄÌ¿®¤·¤Ê¤¤²¾Áۥ¥«¡¼¤¬À¸À®¤µ¤ì¤Þ¤¹¡£ + ¤³¤Î¥ï¡¼¥«¡¼¤Ï´ö¤Ä¤«¤Î "ËÜʪ¤Î" ¥ï¡¼¥«¡¼¤Î´ÉÍý¤ò¤Ä¤«¤µ¤É¤ê¤Þ¤¹¡£ + ¤³¤Î¾ì¹ç¥Ñ¥é¥á¡¼¥¿¤Ï¡¢¤³¤Î²¾Áۥ¥«¡¼¤ËÂФ·¤ÆÀßÄꤵ¤ì¤Þ¤¹¡£ +

+ + + + + + + + + + + + + + + + + + + + +
¥Ñ¥é¥á¡¼¥¿¥Ç¥Õ¥©¥ë¥ÈÃÍÀâÌÀ
lbmethod-Balancer ¤Î¥í¡¼¥É¥Ð¥é¥ó¥¹ÊýË¡¡£»ÈÍѤ¹¤ë¥í¡¼¥É¥Ð¥é¥ó¥¹¤Î + ¥¹¥±¥¸¥å¡¼¥ê¥ó¥°ÊýË¡¤òÁª¤Ó¤Þ¤¹¡£½èÍý¤·¤¿¥ê¥¯¥¨¥¹¥È¤Î¿ô¤Ç½Å¤ßÉÕ¤±¤¹¤ë + byrequests ¤«¡¢Å¾Á÷Î̤ΥХ¤¥È¿ô¤Ç½Å¤ßÉÕ¤±¤¹¤ë + bytraffic ¤òÀßÄê¤Ç¤­¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Ï + byrequests ¤Ç¤¹¡£ +
stickysession-¥Ð¥é¥ó¥µ¡¼¤Î¥¹¥Æ¥£¥Ã¥­¡¼¥»¥Ã¥·¥ç¥ó̾¤Ç¤¹¡£Ä̾ï¤Ï¤³¤ÎÃÍ¤Ï JSESSIONID + ¤ä PHPSESSIONID ¤È¤¤¤Ã¤¿¤â¤Î¤Ë¤Ê¤ê¤Þ¤¹¤¬¡¢¤³¤ÎÃÍ¤Ï + ¥Ð¥Ã¥¯¥¨¥ó¥É¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¥µ¥Ý¡¼¥È¤¹¤ë¥»¥Ã¥·¥ç¥ó¤Ë°Í¸¤·¤Þ¤¹¡£ +
nofailoverOffOn ¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤È¡¢¥ï¡¼¥«¡¼¤¬¥¨¥é¡¼¤òµ¯¤³¤·¤¿¤ê + ̵¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¥»¥Ã¥·¥ç¥ó¤¬ÀÚ¤ì¤Þ¤¹¡£ + ¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤¬¥»¥Ã¥·¥ç¥ó¥ì¥×¥ê¥±¡¼¥·¥ç¥ó¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Ê¤¤¾ì¹ç¤Ï¡¢ + On ¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ +
timeout0¥Ð¥é¥ó¥µ¡¼¤Î¥¿¥¤¥à¥¢¥¦¥È¤òÉäǻØÄꤷ¤Þ¤¹¡£ + ¤³¤ÎÃͤòÀßÄꤹ¤ë¤È¡¢¥Õ¥ê¡¼¤Î¥ï¡¼¥«¡¼¤ò¼èÆÀ¤¹¤ë¤Þ¤Ç¤ÎºÇÂçÂÔµ¡»þ´Ö¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤ÏÂÔµ¡¤·¤Þ¤»¤ó¡£ +
maxattempts1¥Õ¥§¥¤¥ë¥ª¡¼¥Ð¡¼¤ò»î¤ß¤ëºÇÂç¤Î²ó¿ô¤ò»ØÄꤷ¤Þ¤¹¡£ +
+

+ ProxyPass /special-area http://special.example.com/ smax=5 max=10
+ ProxyPass / balancer://mycluster stickysession=jsessionid nofailover=On
+ <Proxy balancer://mycluster>
+ + BalancerMember http://1.2.3.4:8009
+ BalancerMember http://1.2.3.5:8009 smax=10
+ # Less powerful server, don't send as many requests there
+ BalancerMember http://1.2.3.6:8009 smax=1 loadfactor=20
+ + </Proxy> +

+ +

<Location> ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤Ç»È¤ï¤ì¤¿¾ì¹ç¡¢ºÇ½é¤Î°ú¿ô¤Ï + ¾Êά¤µ¤ì¡¢¥í¡¼¥«¥ë¥Ç¥£¥ì¥¯¥È¥ê¤Ï <Location> ¤«¤é¼èÆÀ¤µ¤ì¤Þ¤¹¡£

+ +

¤è¤ê½ÀÆð¤Ê¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤ÎÀßÄ꤬ɬÍפʾì¹ç¤Ï¡¢[P] + ¥Õ¥é¥°ÉÕ¤­¤Î RewriteRule + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
top
+

ProxyPassReverse ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤µ¤ì¤¿¥µ¡¼¥Ð¤«¤éÁ÷¤é¤ì¤¿ HTTP ±þÅú¥Ø¥Ã¥À¤Î +URL ¤òÄ´À°¤¹¤ë
¹½Ê¸:ProxyPassReverse [path] url
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache ¤Ë HTTP ¥ê¥À¥¤¥ì¥¯¥È±þÅú¤Î + Location, Content-Location, URI + ¥Ø¥Ã¥À¤ÎÄ´À°¤ò¤µ¤»¤Þ¤¹¡£¤³¤ì¤Ï¡¢Apache ¤¬¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤È¤·¤Æ»È¤ï¤ì¤Æ¤¤¤ë + ¤È¤­¤Ë¡¢¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤òÄ̤µ¤Ê¤¤¤Ç¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤òËɤ°¤¿¤á¤Ë + ½ÅÍפǤ¹¡£¤³¤ì¤Ë¤è¤ê¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤Î HTTP ¥ê¥À¥¤¥ì¥¯¥È¤¬ + ¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤È¥Ð¥Ã¥¯¥¨¥ó¥É¤Î´Ö¤Ç°·¤ï¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÌÀ¼¨¤µ¤ì¤Æ¤¤¤ë HTTP ±þÅú¥Ø¥Ã¥À¤Î¤ß¤¬½ñ¤­´¹¤¨¤é¤ì¤Þ¤¹¡£ + Apache ¤Ï¾¤Î±þÅú¥Ø¥Ã¥À¤ò½ñ¤­´¹¤¨¤¿¤ê¡¢HTML ¥Ú¡¼¥¸¤ÎÃæ¤Î URL »²¾È¤ò + ½ñ¤­´¹¤¨¤¿¤ê¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£HTML ¤ÎÃæ¤ò¸«¤Æ¡¢URL »²¾È¤ò½ñ¤­´¹¤¨¤ë + ¥â¥¸¥å¡¼¥ë¤Ë Nick Kew ¤µ¤ó¤Î mod_proxy_html ¤¬¤¢¤ê¤Þ¤¹¡£

+ +

path ¤Ï¥í¡¼¥«¥ë²¾Áۥѥ¹¤Î̾Á°¤Ç¤¹¡£url ¤Ï + ¥ê¥â¡¼¥È¥µ¡¼¥Ð¤ÎÉôʬ URL ¤Ç¤¹¡£¤³¤ì¤é¤Ï ProxyPass ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈƱÍͤǤ¹¡£

+ +

Î㤨¤Ð¡¢¥í¡¼¥«¥ë¥µ¡¼¥Ð¤Î¥¢¥É¥ì¥¹¤¬ http://example.com/ + ¤À¤È¤·¤Þ¤¹¡£¤¹¤ë¤È

+ +

+ ProxyPass /mirror/foo/ http://backend.example.com/
+ ProxyPassReverse /mirror/foo/ http://backend.example.com/
+ ProxyPassReverseCookieDomain backend.example.com public.example.com
+ ProxyPassReverseCookiePath / /mirror/foo/ +

+ +

¤È¤¤¤¦ÀßÄê¤ò¤¹¤ë¤È¡¢http://example.com/mirror/foo/bar + ¤Ø¤Î¥í¡¼¥«¥ë¥ê¥¯¥¨¥¹¥È¤¬ http://backend.example.com/bar + ¤Ø¤Î¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤ËÆâÉô¤Ç¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤ë¤À¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó + (¤³¤ì¤Ï ProxyPass ¤Îµ¡Ç½¤Ç¤¹)¡£backend.example.com + ¤¬Á÷¤ë¥ê¥À¥¤¥ì¥¯¥È¤ÎÌÌÅݤâ¤ß¤Þ¤¹¡£http://backend.example.com/bar + ¤¬ http://backend.example.com/quux ¤Ë¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤¿¤È¤­¡¢ + Apache ¤Ï HTTP ¥ê¥À¥¤¥ì¥¯¥È±þÅú¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ëÁ°¤Ë¡¢ + http://example.com/mirror/foo/quux ¤ËÊѹ¹¤·¤Þ¤¹¡£ + URL ¤ò¹½À®¤¹¤ë¤Î¤Ë»È¤ï¤ì¤ë¥Û¥¹¥È̾¤Ï UseCanonicalName ¤ÎÀßÄê¤Ë±þ¤¸¤ÆÁªÂò¤µ¤ì¤ë¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

ProxyPassReverse ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + Âбþ¤¹¤ë ProxyPass ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤Ï°Í¸¤·¤Ê¤¤¤¿¤á¡¢ + mod_rewrite ¤Î¥×¥í¥­¥·Ä̲ᵡǽ + (RewriteRule ... [P]) ¤ÈÊ»¤»¤Æ»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

<Location> ¥»¥¯¥·¥ç¥ó¤ÎÃæ¤Ç»È¤ï¤ì¤¿¾ì¹ç¤Ï¡¢ + ºÇ½é¤Î°ú¿ô¤Ï¾Êά¤µ¤ì¡¢¥í¡¼¥«¥ë¥Ç¥£¥ì¥¯¥È¥ê¤Ï <Location> ¤«¤é¼èÆÀ¤µ¤ì¤Þ¤¹¡£

+ +
+
top
+

ProxyPassReverseCookieDomain ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¥µ¡¼¥Ð¤«¤é¤Î Set-Cookie ¥Ø¥Ã¥À¤Î Domain ʸ»úÎó¤ò +Ä´À°¤¹¤ë
¹½Ê¸:ProxyPassReverseCookieDomain internal-domain public-domain
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

»ÈÍÑË¡¤Ï´ðËÜŪ¤Ë +ProxyPassReverse ¤ÈƱ¤¸¤Ç¤¹¤¬¡¢ +¥Ø¥Ã¥À¤Î URL ¤ÎÂå¤ï¤ê¤Ë Set-Cookie ¥Ø¥Ã¥À¤Î +domain ʸ»úÎó¤ò½ñ¤­´¹¤¨¤Þ¤¹¡£

+ +
+
top
+

ProxyPassReverseCookiePath ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:Reverse ¥×¥í¥­¥·¥µ¡¼¥Ð¤«¤é¤Î Set-Cookie ¥Ø¥Ã¥À¤Î Path ʸ»úÎó¤ò +Ä´À°¤¹¤ë
¹½Ê¸:ProxyPassReverseCookiePath internal-path public-path
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

»ÈÍÑË¡¤Ï´ðËÜŪ¤Ë +ProxyPassReverse ¤ÈƱ¤¸¤Ç¤¹¤¬¡¢ +¥Ø¥Ã¥À¤Î URL ¤ÎÂå¤ï¤ê¤Ë Set-Cookie ¥Ø¥Ã¥À¤Î +path ʸ»úÎó¤ò½ñ¤­´¹¤¨¤Þ¤¹¡£

+ +
+
top
+

ProxyPreserveHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤Ë¡¢¼õ¤±ÉÕ¤±¤¿ Host HTTP ¥Ø¥Ã¥À¤ò»È¤¦
¹½Ê¸:ProxyPreserveHost On|Off
¥Ç¥Õ¥©¥ë¥È:ProxyPreserveHost Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
¸ß´¹À­:Apache 2.0.31 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

¤³¤Î¥ª¥×¥·¥ç¥ó¤¬Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¡¢ProxyPass + ¤Ç»ØÄꤷ¤¿¥Û¥¹¥È̾¤ÎÂå¤ï¤ê¤Ë¡¢¼õ¤±ÉÕ¤±¤¿¥ê¥¯¥¨¥¹¥È¤Î Host: ¹Ô¤ò + ¥×¥í¥­¥·Àè¤Î¥Û¥¹¥È¤ËÁ÷¤ê¤Þ¤¹¡£

+ +

¤³¤Î¥ª¥×¥·¥ç¥ó¤ÏÄ̾ï¤Ï Off ¤ËÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£ + ¤Û¤È¤ó¤É¤Î¾ì¹ç¡¢¤³¤ì¤ÏÂçÎ̤Î̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥Æ¥£¥ó¥°¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤Æ¡¢ + ¸µ¡¹¤Î Host ¥Ø¥Ã¥À¤ò¥Ð¥Ã¥¯¥¨¥ó¥É¥µ¡¼¥Ð¤¬²ò¼á¤¹¤ëɬÍפΤ¢¤ë¤È¤­¤Î¤è¤¦¤Ê¡¢ + ÆÃÊ̤ÊÀßÄ꤬ɬÍפʾì¹ç¤Ë¤Î¤ßÍ­ÍѤǤ¹¡£

+ +
+
top
+

ProxyReceiveBufferSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥×¥í¥­¥·¤µ¤ì¤ë HTTP ¤È FTP Àܳ¤Î¤¿¤á¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥Ð¥Ã¥Õ¥¡¥µ¥¤¥º
¹½Ê¸:ProxyReceiveBufferSize bytes
¥Ç¥Õ¥©¥ë¥È:ProxyReceiveBufferSize 0
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

ProxyReceiveBufferSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥¹¥ë¡¼¥×¥Ã¥È¤ò¾å¤²¤ë¤¿¤á¤ËÌÀ¼¨Åª¤Ë (TCP/IP) ¥Í¥Ã¥È¥ï¡¼¥¯¥Ð¥Ã¥Õ¥¡¤Î¥µ¥¤¥º¤ò + ÀßÄꤷ¤Þ¤¹¡£ÃÍ¤Ï 512 °Ê¾å¤«¡¢¥·¥¹¥Æ¥à¤Î¥Ç¥Õ¥©¥ë¥È¤Î¥Ð¥Ã¥Õ¥¡ + ¥µ¥¤¥º¤ò°ÕÌ£¤¹¤ë 0 ¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

Îã

+ ProxyReceiveBufferSize 2048 +

+ +
+
top
+

ProxyRemote ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:ÆÃÄê¤Î¥ê¥¯¥¨¥¹¥È¤ò°·¤¦»þ¤Ë»È¤ï¤ì¤ë¥ê¥â¡¼¥È¥×¥í¥­¥·¤ò»ØÄꤹ¤ë
¹½Ê¸:ProxyRemote match remote-server
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤³¤Î¥×¥í¥­¥·¤ËÂФ¹¤ë¥ê¥â¡¼¥È¥×¥í¥­¥·¤òÄêµÁ¤·¤Þ¤¹¡£ + match ¤Ï¥ê¥â¡¼¥È¥µ¡¼¥Ð¤¬¥µ¥Ý¡¼¥È¤¹¤ë URL ¥¹¥­¡¼¥à¡¢ + ¥ê¥â¡¼¥È¥µ¡¼¥Ð¤¬»È¤¦¤Ï¤º¤Î URL ¤Î°ìÉôʬ¡¢¥µ¡¼¥Ð¤¬¤¹¤Ù¤Æ¤Î + ¥ê¥¯¥¨¥¹¥È¤Ë»È¤ï¤ì¤ë¤³¤È¤ò¼¨¤¹ * ¤Î¤É¤ì¤«¤Ë¤Ê¤ê¤Þ¤¹¡£ + remote-server ¤Ï¥ê¥â¡¼¥È¥µ¡¼¥Ð¤ÎÉôʬ URL ¤Ç¤¹¡£¹½Ê¸:

+ +

+ remote-server = + scheme://hostname[:port] +

+ +

scheme ¤Ï¼ÂºÝ¾å¥ê¥â¡¼¥È¥µ¡¼¥Ð¤È¤ÎÄÌ¿®¤Ë»È¤ï¤ì¤ë¥×¥í¥È¥³¥ë¤ò + ·èÄꤷ¤Þ¤¹¡£¤³¤Î¥â¥¸¥å¡¼¥ë¤Ç¤Ï http ¤À¤±¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ + ¤¤¤Þ¤¹¡£

+ +

Îã

+ ProxyRemote http://goodguys.com/ http://mirrorguys.com:8000
+ ProxyRemote * http://cleversite.com
+ ProxyRemote ftp http://ftpproxy.mydomain.com:8080 +

+ +

¤³¤ÎÎã¤Ç¤Ï¡¢¥×¥í¥­¥·¤Ï FTP ¥ê¥¯¥¨¥¹¥È¤òÊ̤ΠHTTP ¥ê¥¯¥¨¥¹¥È¤ÇÊñ¤ó¤Ç + ¤½¤Î¤è¤¦¤Ê¥ê¥¯¥¨¥¹¥È¤ò°·¤¨¤ëÊÌ¤Î¥×¥í¥­¥·¤ËžÁ÷¤·¤Þ¤¹¡£

+ +

¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤ÎÀßÄê¤â¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤¬Ê̤Υե©¥ï¡¼¥É¥×¥í¥­¥·¤Î¸å¤í¤Ë±£¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ç¤â + ¥Ð¥Ã¥¯¥¨¥ó¥É¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î URL ¶õ´Ö¤ËÆþ¤ì¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+ +
+
top
+

ProxyRemoteMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:Àµµ¬É½¸½¤Ç¤Î¥Þ¥Ã¥Á¤Ë¤è¤ë¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¥ê¥â¡¼¥È¥×¥í¥­¥·¤Î»ØÄê
¹½Ê¸:ProxyRemoteMatch regex remote-server
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

ProxyRemoteMatch ¤ÏºÇ½é¤Î°ú¿ô¤¬¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿ + URL ¤Ë¥Þ¥Ã¥Á¤¹¤ëÀµµ¬É½¸½¤Ç¤¢¤ë¤³¤È¤ò½ü¤±¤Ð ProxyRemote ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈƱ¤¸¤Ç¤¹¡£

+ +
+
top
+

ProxyRequests ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Õ¥©¥ï¡¼¥É (ɸ½à¤Î) ¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤òÍ­¸ú¤Ë¤¹¤ë
¹½Ê¸:ProxyRequests On|Off
¥Ç¥Õ¥©¥ë¥È:ProxyRequests Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

¤³¤ì¤Ï Apache ¤Î¥Õ¥©¥ï¡¼¥É¥×¥í¥­¥·¥µ¡¼¥Ð¤È¤·¤Æ¤ÎÆ°ºî¤ò + Í­¸ú¤â¤·¤¯¤Ï̵¸ú¤Ë¤·¤Þ¤¹¡£(ProxyRequests ¤ò Off ¤Ë + ÀßÄꤷ¤Æ¤â¡¢ProxyPass + ¤ÎÀßÄê¤Ï̵¸ú¤Ë¤Ê¤ê¤Þ¤»¤ó¡£)

+ +

Ä̾ï¤Î¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤ÎÀßÄê¤Ç¤Ï¡¢¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï Off + ¤ËÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£

+ +

HTTP ¤ä FTP ¥µ¥¤¥È¤Ø¤Î¥×¥í¥­¥·¤Îµ¡Ç½¤òÍ­¸ú¤Ë¤·¤¿¤¤¾ì¹ç¤Ï¡¢ + mod_proxy_http ¤ä mod_proxy_ftp ¤¬ + ¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

·Ù¹ð

+

¥µ¡¼¥Ð¤ò°ÂÁ´¤Ë¤¹¤ë¤Þ¤Ç ProxyRequests ¤ÏÍ­¸ú¤Ë¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + ¥ª¡¼¥×¥ó¥×¥í¥­¥·¥µ¡¼¥Ð¤Ï¤¢¤Ê¤¿¼«¿È¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤È¤Ã¤Æ¤â¡¢ + ¥¤¥ó¥¿¡¼¥Í¥Ã¥ÈÁ´ÂΤˤȤäƤâ´í¸±¤Ç¤¹¡£

+
+ +
+
top
+

ProxyTimeout ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥×¥í¥­¥·¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¿¥¤¥à¥¢¥¦¥È
¹½Ê¸:ProxyTimeout seconds
¥Ç¥Õ¥©¥ë¥È:ProxyTimeout 300
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
¸ß´¹À­:Apache 2.0.31 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥æ¡¼¥¶¤¬¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤Î¥¿¥¤¥à¥¢¥¦¥È¤ò + »ØÄê¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£¤³¤ì¤Ï¥Ï¥ó¥°¤·¤Æ¤·¤Þ¤¦ÃÙ¤¤¡¢¤â¤·¤¯¤ÏµóÆ°¤Î + ²ø¤·¤¤¥µ¡¼¥Ð¤¬¤¢¤ê¡¢¥µ¡¼¥Ð¤¬¥Ç¡¼¥¿¤òÊÖ¤¹¤Þ¤Ç¤Ò¤¿¤¹¤éÂÔ¤Á³¤±¤ë¤è¤ê¤â + ¥¿¥¤¥à¥¢¥¦¥È¤òÊÖ¤·¤Æ¤è¤ê´Ë¤ä¤«¤Ë(ÌõÃí: graceful ¤Ë) + ¼ºÇÔ¤µ¤»¤¿¤¤¾ì¹ç¤ËÌò¤ËΩ¤Á¤Þ¤¹¡£

+ +
+
top
+

ProxyVia ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥×¥í¥­¥·¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î Via HTTP ±þÅú¥Ø¥Ã¥À +¤Ë¤è¤êÄ󶡤µ¤ì¤ë¾ðÊó
¹½Ê¸:ProxyVia On|Off|Full|Block
¥Ç¥Õ¥©¥ë¥È:ProxyVia Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_proxy
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥×¥í¥­¥·¤Î Via: HTTP ¥Ø¥Ã¥À¤Î»ÈÍѤò + À©¸æ¤·¤Þ¤¹¡£ÁÛÄꤵ¤ì¤Æ¤¤¤ë»È¤¤Êý¤Ï¡¢¥×¥í¥­¥·¥µ¡¼¥Ð¤¬¤¤¤¯¤Ä¤â·Ò¤¬¤Ã¤Æ¤¤¤ë¤È¤­¤Ë + ¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤Îή¤ì¤òÀ©¸æ¤¹¤ë¤³¤È¤Ç¤¹¡£Via: ¥Ø¥Ã¥À¹Ô¤Î + ÀâÌÀ¤Ï RFC 2616 (HTTP/1.1) + ¤Î 14.45 Àá¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£

+ +
    +
  • ¥Ç¥Õ¥©¥ë¥È¤Î Off ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¡¢ÆÃÊ̤ʽèÍý¤Ï + ¹Ô¤Ê¤ï¤ì¤Þ¤»¤ó¡£¥ê¥¯¥¨¥¹¥È¤ä¥ê¥×¥é¥¤¤Ë Via: ¥Ø¥Ã¥À¤¬¤¢¤ì¤Ð¡¢ + Êѹ¹¤µ¤ì¤º¤Ë¤½¤Î¤Þ¤ÞÅϤ·¤Þ¤¹¡£
    • + +
  • On ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢³Æ¥ê¥¯¥¨¥¹¥È¤È¥ê¥×¥é¥¤¤Ë + Via: ¹Ô¤¬Äɲ䵤ì¤Þ¤¹¡£
    • + +
  • Full ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢Via: ¥Ø¥Ã¥À¤Ï + ¥³¥á¥ó¥ÈÉôʬ¤Ë Apache ¥µ¡¼¥Ð¤Î¥Ð¡¼¥¸¥ç¥ó¤â´Þ¤à¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
    • + +
  • Block ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢¤¹¤Ù¤Æ¤Î¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤«¤é + Via: ¥Ø¥Ã¥À¤¬¼è¤ê½ü¤«¤ì¤Þ¤¹¡£¿·¤¿¤Ë Via: ¤¬ + À¸À®¤µ¤ì¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
    • +
+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy_ajp.html b/docs/manual/mod/mod_proxy_ajp.html new file mode 100644 index 00000000..2e2bf126 --- /dev/null +++ b/docs/manual/mod/mod_proxy_ajp.html @@ -0,0 +1,7 @@ +URI: mod_proxy_ajp.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_proxy_ajp.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_proxy_ajp.html.en b/docs/manual/mod/mod_proxy_ajp.html.en new file mode 100644 index 00000000..9903cb3b --- /dev/null +++ b/docs/manual/mod/mod_proxy_ajp.html.en @@ -0,0 +1,556 @@ + + + +mod_proxy_ajp - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_proxy_ajp

+
+

Available Languages:  en  | + ja 

+
+ + + + +
Description:AJP support module for +mod_proxy
Status:Extension
Module Identifier:proxy_ajp_module
Source File:proxy_ajp.c
Compatibility:Available in version 2.1 and later
+

Summary

+ +

This module requires the service of mod_proxy. It provides support for the + Apache JServ Protocol version 1.3 (hereafter + AJP13).

+ +

Thus, in order to get the ability of handling AJP13 + protocol, mod_proxy and + mod_proxy_ajp have to be present in the server.

+ +

Warning

+

Do not enable proxying until you have secured your server. Open proxy + servers are dangerous both to your network and to the Internet at + large.

+
+
+

Directives

+

This module provides no + directives.

+

Topics

+

See also

+
+
top
+
+

Overview of the protocol

+

The AJP13 protocol is packet-oriented. A binary format + was presumably chosen over the more readable plain text for reasons of + performance. The web server communicates with the servlet container over + TCP connections. To cut down on the expensive process of socket creation, + the web server will attempt to maintain persistent TCP connections to the + servlet container, and to reuse a connection for multiple request/response + cycles.

+

Once a connection is assigned to a particular request, it will not be + used for any others until the request-handling cycle has terminated. In + other words, requests are not multiplexed over connections. This makes + for much simpler code at either end of the connection, although it does + cause more connections to be open at once.

+

Once the web server has opened a connection to the servlet container, + the connection can be in one of the following states:

+
    +
  • Idle
    No request is being handled over this connection.
    • +
  • Assigned
    The connecton is handling a specific request.
    • +
+

Once a connection is assigned to handle a particular request, the basic + request informaton (e.g. HTTP headers, etc) is sent over the connection in + a highly condensed form (e.g. common strings are encoded as integers). + Details of that format are below in Request Packet Structure. If there is a + body to the request (content-length > 0), that is sent in a + separate packet immediately after.

+

At this point, the servlet container is presumably ready to start + processing the request. As it does so, it can send the + following messages back to the web server:

+
    +
  • SEND_HEADERS
    Send a set of headers back to the browser.
    • +
  • SEND_BODY_CHUNK
    Send a chunk of body data back to the browser. +
    • +
  • GET_BODY_CHUNK
    Get further data from the request if it hasn't all + been transferred yet. This is necessary because the packets have a fixed + maximum size and arbitrary amounts of data can be included the body of a + request (for uploaded files, for example). (Note: this is unrelated to + HTTP chunked tranfer).
    • +
  • END_RESPONSE
    Finish the request-handling cycle.
    • +
+

Each message is accompanied by a differently formatted packet of data. + See Response Packet Structures below for details.

+
top
+
+

Basic Packet Structure

+

There is a bit of an XDR heritage to this protocol, but it differs + in lots of ways (no 4 byte alignment, for example).

+

Byte order: I am not clear about the endian-ness of the individual + bytes. I'm guessing the bytes are little-endian, because that's what + XDR specifies, and I'm guessing that sys/socket library is magically + making that so (on the C side). If anyone with a better knowledge of + socket calls can step in, that would be great.

+

There are four data types in the protocol: bytes, booleans, + integers and strings.

+
+
Byte
A single byte.
+
Boolean
+
A single byte, 1 = true, 0 = false. + Using other non-zero values as true (i.e. C-style) may work in some places, + but it won't in others.
+
Integer
+
A number in the range of 0 to 2^16 (32768). Stored in + 2 bytes with the high-order byte first.
+
String
+
A variable-sized string (length bounded by 2^16). Encoded with + the length packed into two bytes first, followed by the string + (including the terminating '\0'). Note that the encoded length does + not include the trailing '\0' -- it is like + strlen. This is a touch confusing on the Java side, which + is littered with odd autoincrement statements to skip over these + terminators. I believe the reason this was done was to allow the C + code to be extra efficient when reading strings which the servlet + container is sending back -- with the terminating \0 character, the + C code can pass around references into a single buffer, without copying. + if the \0 was missing, the C code would have to copy things out in order + to get its notion of a string.
+
+ +

Packet Size

+

According to much of the code, the max packet size is + 8 * 1024 bytes (8K). The actual length of the packet is encoded in + the header.

+ +

Packet Headers

+

Packets sent from the server to the container begin with + 0x1234. Packets sent from the container to the server + begin with AB (that's the ASCII code for A followed by the + ASCII code for B). After those first two bytes, there is an integer + (encoded as above) with the length of the payload. Although this might + suggest that the maximum payload could be as large as 2^16, in fact, the + code sets the maximum to be 8K.

+ + + + + + + + + + + + + + + + + + + +
Packet Format (Server->Container)
Byte01234...(n+3)
Contents0x120x34Data Length (n)Data
+ + + + + + + + + + + + + + + + + + + +
Packet Format (Container->Server)
Byte01234...(n+3)
ContentsABData Length (n)Data
+

For most packets, the first byte of the payload encodes the type of + message. The exception is for request body packets sent from the server to + the container -- they are sent with a standard packet header ( + 0x1234 and then length of the packet), but without any prefix code + after that.

+

The web server can send the following messages to the servlet + container:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeType of PacketMeaning
2Forward RequestBegin the request-processing cycle with the following data
7ShutdownThe web server asks the container to shut itself down.
8PingThe web server asks the container to take control + (secure login phase).
10CPingThe web server asks the container to respond quickly with a CPong. +
noneDataSize (2 bytes) and corresponding body data.
+

To ensure some basic security, the container will only actually do the + Shutdown if the request comes from the same machine on which + it's hosted.

+

The first Data packet is send immediatly after the + Forward Request by the web server.

+

The servlet container can send the following types of messages to the + webserver:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeType of PacketMeaning
3Send Body ChunkSend a chunk of the body from the servlet container to the web + server (and presumably, onto the browser).
4Send HeadersSend the response headers from the servlet container to the web + server (and presumably, onto the browser).
5End ResponseMarks the end of the response (and thus the request-handling cycle). +
6Get Body ChunkGet further data from the request if it hasn't all been + transferred yet.
9CPong ReplyThe reply to a CPing request
+

Each of the above messages has a different internal structure, detailed + below.

+ +
top
+
+

Request Packet Structure

+

For messages from the server to the container of type + Forward Request:

+ 
+AJP13_FORWARD_REQUEST :=
+    prefix_code      (byte) 0x02 = JK_AJP13_FORWARD_REQUEST
+    method           (byte)
+    protocol         (string)
+    req_uri          (string)
+    remote_addr      (string)
+    remote_host      (string)
+    server_name      (string)
+    server_port      (integer)
+    is_ssl           (boolean)
+    num_headers      (integer)
+    request_headers *(req_header_name req_header_value)
+    attributes      *(attribut_name attribute_value)
+    request_terminator (byte) OxFF
+
+

The request_headers have the following structure: + 

+req_header_name := 
+    sc_req_header_name | (string)  [see below for how this is parsed]
+
+sc_req_header_name := 0xA0xx (integer)
+
+req_header_value := (string)
+
+

The attributes are optional and have the following + structure:

+ 
+attribute_name := sc_a_name | (sc_a_req_attribute string)
+
+attribute_value := (string)
+
+
+

Not that the all-important header is content-length, + because it determines whether or not the container looks for another + packet immediately.

+

Detailed description of the elements of Forward Request +

+

Request prefix

+

For all requests, this will be 2. See above for details on other Prefix + codes.

+ +

Method

+

The HTTP method, encoded as a single byte:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Command NameCode
OPTIONS1
GET2
HEAD3
POST4
PUT5
DELETE6
TRACE7
PROPFIND8
PROPPATCH9
MKCOL10
COPY11
MOVE12
LOCK13
UNLOCK14
ACL15
REPORT16
VERSION-CONTROL17
CHECKIN18
CHECKOUT19
UNCHECKOUT20
SEARCH21
MKWORKSPACE22
UPDATE23
LABEL24
MERGE25
BASELINE_CONTROL26
MKACTIVITY27
+

Later version of ajp13, will transport + additional methods, even if they are not in this list.

+ +

protocol, req_uri, remote_addr, remote_host, server_name, + server_port, is_ssl

+

These are all fairly self-explanatory. Each of these is required, and + will be sent for every request.

+ +

Headers

+

The structure of request_headers is the following: + First, the number of headers num_headers is encoded. + Then, a series of header name req_header_name / value + req_header_value pairs follows. + Common header names are encoded as integers, + to save space. If the header name is not in the list of basic headers, + it is encoded normally (as a string, with prefixed length). The list of + common headers sc_req_header_nameand their codes + is as follows (all are case-sensitive):

+ + + + + + + + + + + + + + + + + + + +
NameCode valueCode name
accept0xA001SC_REQ_ACCEPT
accept-charset0xA002SC_REQ_ACCEPT_CHARSET +
accept-encoding0xA003SC_REQ_ACCEPT_ENCODING +
accept-language0xA004SC_REQ_ACCEPT_LANGUAGE +
authorization0xA005SC_REQ_AUTHORIZATION
connection0xA006SC_REQ_CONNECTION
content-type0xA007SC_REQ_CONTENT_TYPE
content-length0xA008SC_REQ_CONTENT_LENGTH
cookie0xA009SC_REQ_COOKIE
cookie20xA00ASC_REQ_COOKIE2
host0xA00BSC_REQ_HOST
pragma0xA00CSC_REQ_PRAGMA
referer0xA00DSC_REQ_REFERER
user-agent0xA00ESC_REQ_USER_AGENT
+

The Java code that reads this grabs the first two-byte integer and if + it sees an '0xA0' in the most significant + byte, it uses the integer in the second byte as an index into an array of + header names. If the first byte is not 0xA0, it assumes that + the two-byte integer is the length of a string, which is then read in.

+

This works on the assumption that no header names will have length + greater than 0x9999 (==0xA000 - 1), which is perfectly + reasonable, though somewhat arbitrary.

+

Note:

+ The content-length header is extremely + important. If it is present and non-zero, the container assumes that + the request has a body (a POST request, for example), and immediately + reads a separate packet off the input stream to get that body. +
+ +

Attributes

+

The attributes prefixed with a ? + (e.g. ?context) are all optional. For each, there is a + single byte code to indicate the type of attribute, and then a string to + give its value. They can be sent in any order (thogh the C code always + sends them in the order listed below). A special terminating code is + sent to signal the end of the list of optional attributes. The list of + byte codes is:

+ + + + + + + + + + + + + + +
InformationCode ValueNote
?context0x01Not currently implemented +
?servlet_path0x02Not currently implemented +
?remote_user0x03
?auth_type0x04
?query_string0x05
?jvm_route0x06
?ssl_cert0x07
?ssl_cipher0x08
?ssl_session0x09
?req_attribute0x0AName (the name of the + attribute follows)
?ssl_key_size0x0B
are_done0xFFrequest_terminator
+

The context and servlet_path are not + currently set by the C code, and most of the Java code completely ignores + whatever is sent over for those fields (and some of it will actually break + if a string is sent along after one of those codes). I don't know if this + is a bug or an unimplemented feature or just vestigial code, but it's + missing from both sides of the connection.

+

The remote_user and auth_type presumably + refer to HTTP-level authentication, and communicate the remote user's + username and the type of authentication used to establish their identity + (e.g. Basic, Digest).

+

The query_string, ssl_cert, + ssl_cipher, and ssl_session refer to the + corresponding pieces of HTTP and HTTPS.

+

The jvm_route, is used to support sticky + sessions -- associating a user's sesson with a particular Tomcat instance + in the presence of multiple, load-balancing servers.

+

Beyond this list of basic attributes, any number of other attributes + can be sent via the req_attribute code 0x0A. + A pair of strings to represent the attribute name and value are sent + immediately after each instance of that code. Environment values are passed + in via this method.

+

Finally, after all the attributes have been sent, the attribute + terminator, 0xFF, is sent. This signals both the end of the + list of attributes and also then end of the Request Packet.

+ +
top
+
+

Response Packet Structure

+

for messages which the container can send back to the server.

+ 
+AJP13_SEND_BODY_CHUNK :=
+  prefix_code   3
+  chunk_length  (integer)
+  chunk        *(byte)
+
+
+AJP13_SEND_HEADERS :=
+  prefix_code       4
+  http_status_code  (integer)
+  http_status_msg   (string)
+  num_headers       (integer)
+  response_headers *(res_header_name header_value)
+
+res_header_name :=
+    sc_res_header_name | (string)   [see below for how this is parsed]
+
+sc_res_header_name := 0xA0 (byte)
+
+header_value := (string)
+
+AJP13_END_RESPONSE :=
+  prefix_code       5
+  reuse             (boolean)
+
+
+AJP13_GET_BODY_CHUNK :=
+  prefix_code       6
+  requested_length  (integer)
+
+

Details:

+

Send Body Chunk

+

The chunk is basically binary data, and is sent directly back to the + browser.

+ +

Send Headers

+

The status code and message are the usual HTTP things + (e.g. 200 and OK). The response header names are + encoded the same way the request header names are. See header_encoding above + for details about how the the codes are distinguished from the strings.
+ The codes for common headers are:

+ + + + + + + + + + + + + +
NameCode value
Content-Type0xA001
Content-Language0xA002
Content-Length0xA003
Date0xA004
Last-Modified0xA005
Location0xA006
Set-Cookie0xA007
Set-Cookie20xA008
Servlet-Engine0xA009
Status0xA00A
WWW-Authenticate0xA00B
+

After the code or the string header name, the header value is + immediately encoded.

+ +

End Response

+

Signals the end of this request-handling cycle. If the + reuse flag is true (==1), this TCP connection can + now be used to handle new incoming requests. If reuse is false + (anything other than 1 in the actual C code), the connection should + be closed.

+ +

Get Body Chunk

+

The container asks for more data from the request (If the body was + too large to fit in the first packet sent over or when the request is + chuncked). The server will send a body packet back with an amount of data + which is the minimum of the request_length, the maximum send + body size (8186 (8 Kbytes - 6)), and the number of bytes + actually left to send from the request body.
+ If there is no more data in the body (i.e. the servlet container is + trying to read past the end of the body), the server will send back an + empty packet, which is a body packet with a payload length of 0. + (0x12,0x34,0x00,0x00)

+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy_ajp.html.ja.euc-jp b/docs/manual/mod/mod_proxy_ajp.html.ja.euc-jp new file mode 100644 index 00000000..5e4dd872 --- /dev/null +++ b/docs/manual/mod/mod_proxy_ajp.html.ja.euc-jp @@ -0,0 +1,542 @@ + + + +mod_proxy_ajp - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_proxy_ajp

+
+

Available Languages:  en  | + ja 

+
+ + + +
ÀâÌÀ:mod_proxy ¤Ç AJP +¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤¿¤á¤Î¥â¥¸¥å¡¼¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:proxy_ajp_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:proxy_ajp.c
+

³µÍ×

+ +

Ëܥ⥸¥å¡¼¥ë¤Ë¤Ï mod_proxy ¤¬É¬ÍפǤ¹¡£ + Apache JServ Protocol version 1.3 (°Ê¹ß AJP13) + ¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£

+ +

AJP13 ¥×¥í¥È¥³¥ë¤ò°·¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï + mod_proxy ¤È mod_proxy_ajp + ¤ò¥µ¡¼¥Ð¤ËÁȤ߹þ¤àɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

·Ù¹ð

+

°ÂÁ´¤Ê¥µ¡¼¥Ð¤Ë¤¹¤ë¤Þ¤Ç¥×¥í¥¯¥·µ¡Ç½¤ÏÍ­¸ú¤Ë¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + ¥ª¡¼¥×¥ó¥×¥í¥­¥·¥µ¡¼¥Ð¤Ï¤¢¤Ê¤¿¼«¿È¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤È¤Ã¤Æ¤â¡¢ + ¥¤¥ó¥¿¡¼¥Í¥Ã¥ÈÁ´ÂΤˤȤäƤâ´í¸±¤Ç¤¹¡£

+
+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+

¥È¥Ô¥Ã¥¯

+

»²¾È

+
+
top
+
+

¥×¥í¥È¥³¥ë¤Î³µÍ×

+

AJP13 ¥×¥í¥È¥³¥ë¤Ï¥Ñ¥±¥Ã¥È»Ø¸þ¤Ç¤¹¡£ + ²ÄÆɤʥץ졼¥ó¥Æ¥­¥¹¥È·Á¼°¤Ç¤Ï¤Ê¤¯¥Ð¥¤¥Ê¥ê·Á¼°¤Ë¤Ê¤Ã¤¿¤Î¤Ï¡¢ + ¤ª¤½¤é¤¯¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¾å¤ÎÍýͳ¤Ë¤è¤ê¤Þ¤¹¡£ + ¥¦¥§¥Ö¥µ¡¼¥Ð¤Ï¥µ¡¼¥Ö¥ì¥Ã¥È¥³¥ó¥Æ¥Ê¤È TCP ¥³¥Í¥¯¥·¥ç¥ó¤ÇÄÌ¿®¤·¤Þ¤¹¡£ + ¥½¥±¥Ã¥ÈÀ¸À®¤Ï½Å¤¤½èÍý¤Ê¤Î¤Ç¡¢Éé²Ù¤ò¸º¤é¤¹¤¿¤á¤Ë¡¢¥µ¡¼¥Ö¥ì¥Ã¥È¥³¥ó¥Æ¥Ê¤È¤Î + TCP Àܳ¤ò°Ý»ý¤·¡¢Ê£¿ô¤Î¥ê¥¯¥¨¥¹¥È¡¦¥ì¥¹¥Ý¥ó¥¹½èÍý¥µ¥¤¥¯¥ë¤ËÂФ·¤Æ°ì¤Ä¤Î + ¥³¥Í¥¯¥·¥ç¥ó¤ò»È¤¤¤Þ¤ï¤¹¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+

¤¢¤ë¥ê¥¯¥¨¥¹¥È¤Ë¥³¥Í¥¯¥·¥ç¥ó¤¬³ä¤êÅö¤Æ¤é¤ì¤ë¤È¡¢¤½¤Î½èÍý¥µ¥¤¥¯¥ë¤¬ + ´°Î»¤¹¤ë¤Þ¤Ç¾¤Î¤â¤Î¤Ë»È¤ï¤ì¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¤Ä¤Þ¤ê¥³¥Í¥¯¥·¥ç¥ó¾å¤Ç¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤ÎƱ»þ½èÍý¤Ï¹Ô¤ï¤ì¤Þ¤»¤ó¡£ + ¤³¤Î¤¿¤á¡¢¥³¥Í¥¯¥·¥ç¥óξü¤Ç¤Î¼Â¹Ô¤¹¤ë¥³¡¼¥É¤ò´Ê·é¤Ë¤Ç¤­¤ë°ìÊý¤Ç¡¢ + Ʊ»þ¤Ë³«¤¯¥³¥Í¥¯¥·¥ç¥ó¤Ï¿¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+

¥µ¡¼¥Ö¥ì¥Ã¥È¥³¥ó¥Æ¥Ê¤Ø¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò³«¤¤¤¿¸å¤Ï¡¢¥³¥Í¥¯¥·¥ç¥ó¤Î¾õÂÖ¤Ï + ¼¡¤Î¤É¤ì¤«¤Ë¤Ê¤ê¤Þ¤¹:

+
    +
  • Idle
    ¥³¥Í¥¯¥·¥ç¥ó¾å¤Ç½èÍý¤µ¤ì¤Æ¤¤¤ë¥ê¥¯¥¨¥¹¥È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
    • +
  • Assigned
    ¥³¥Í¥¯¥·¥ç¥ó¤Ï¥ê¥¯¥¨¥¹¥È¤ò½èÍýÃæ¤Ç¤¹¡£
    • +
+

¥³¥Í¥¯¥·¥ç¥ó¤¬ÆÃÄê¤Î¥ê¥¯¥¨¥¹¥È¤Ë¥¢¥µ¥¤¥ó¤µ¤ì¤ë¤È¡¢´ðËÜŪ¤Ê¾ðÊó (Î㤨¤Ð + HTTP ¥Ø¥Ã¥ÀÅù) ¤¬°µ½Ì¤µ¤ì¤¿·Á (Î㤨¤ÐÄ̾ï¤Îʸ»úÎó¤ÏÀ°¿ô¤Ë¥¨¥ó¥³¡¼¥É¤µ¤ì¤Þ¤¹) + ¤ÇžÁ÷¤µ¤ì¤Þ¤¹¡£¾ÜºÙ¤Ï²¼µ­¤Î¡Ö¥ê¥¯¥¨¥¹¥È¥Ñ¥±¥Ã¥È¤Î¹½Â¤¡×¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¥ê¥¯¥¨¥¹¥È¤Ë¥Ü¥Ç¥£¤¬Â¸ºß (content-length > 0) ¤¹¤ì¤Ð¡¢ + ´ðËÜŪ¤Ê¾ðÊó¤Îľ¸å¤ËÊ̥ѥ±¥Ã¥È¤ÇžÁ÷¤µ¤ì¤Þ¤¹¡£

+

¤³¤Î»þÅÀ¤Ç¤ª¤½¤é¤¯¡¢¥µ¡¼¥Ö¥ì¥Ã¥È¥³¥ó¥Æ¥Ê¤Ï½èÍý¤ò³«»Ï¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤Ç¤¹¤Î¤Ç¡¢¼¡¤Î¥á¥Ã¥»¡¼¥¸¤ò¥¦¥§¥Ö¥µ¡¼¥Ð¤ËÌᤷ¤ÆÃΤ餻¤é¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+
    +
  • SEND_HEADERS
    ¥Ö¥é¥¦¥¶¤Ë¥Ø¥Ã¥À¤òÁ÷¿®¤·¤Þ¤¹¡£
    • +
  • SEND_BODY_CHUNK
    ¥Ö¥é¥¦¥¶¤Ë¥Ü¥Ç¥£¥Ç¡¼¥¿¤Î¥Á¥ã¥ó¥¯¤òÁ÷¤ê¤Þ¤¹¡£ +
    • +
  • GET_BODY_CHUNK
    ¥ê¥¯¥¨¥¹¥È¤Î¥Ç¡¼¥¿¤òÁ´¤Æ¼õ¤±¼è¤ê½ª¤ï¤Ã¤Æ¤¤¤Ê¤¤¤È¤­¤Ë¡¢ + »Ä¤Ã¤Æ¤¤¤ë¥Ç¡¼¥¿¤ò¼õ¤±¼è¤ê¤Þ¤¹¡£¥Ñ¥±¥Ã¥È¤Ë¤¢¤ëÄê¤Þ¤Ã¤¿ºÇÂ獬¤¢¤ê¡¢Ç¤°Õ¤Î + Â礭¤µ¤Î¥Ç¡¼¥¿¤¬¥ê¥¯¥¨¥¹¥È¤Î¥Ü¥Ç¥£¤È¤·¤Æ´Þ¤Þ¤ì¤¦¤ë¾ì¹ç + (Î㤨¤Ð¥Õ¥¡¥¤¥ë¤Î¥¢¥Ã¥×¥í¡¼¥É¤Î¾ì¹ç) ¤ËɬÍפȤʤê¤Þ¤¹¡£ + (Ãí: HTTP ¤Î¥Á¥ã¥ó¥¯Å¾Á÷¤È¤Ï´ØÏ¢¤¢¤ê¤Þ¤»¤ó¡£)
    • +
  • END_RESPONSE
    ¥ê¥¯¥¨¥¹¥È½èÍý¥µ¥¤¥¯¥ë¤ò½ªÎ»¤·¤Þ¤¹¡£
    • +
+

¸Ä¡¹¤Î¥á¥Ã¥»¡¼¥¸¤Ï¤½¤ì¤¾¤ì°Û¤Ê¤ë¥Ç¡¼¥¿¥Ñ¥±¥Ã¥È·Á¼°¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¸å½Ò¤Î¡Ö¥ì¥¹¥Ý¥ó¥¹¥Ñ¥±¥Ã¥È¤Î¹½Â¤¡×¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

´ðËܥѥ±¥Ã¥È¹½Â¤

+

¤³¤Î¥×¥í¥È¥³¥ë¤Ë¤Ï XDR ¤«¤é¼õ¤±·Ñ¤¤¤ÀÉôʬ¤¬¾¯¤·¤¢¤ê¤Þ¤¹¤¬¡¢Â¿¤¯¤ÎÅÀ¤Ç + °Û¤Ê¤ê¤Þ¤¹ (Î㤨¤Ð 4 ¥Ð¥¤¥È¥¢¥é¥¤¥á¥ó¥È¤Ç¤Ê¤¤¤³¤È¤Ê¤É) ¡£

+

¥Ð¥¤¥È¥ª¡¼¥À¡¼: ¸Ä¡¹¤Î¥Ð¥¤¥È¤Î¥¨¥ó¥Ç¥£¥¢¥ó¤¬¤É¤¦¤Ê¤Ã¤Æ¤¤¤ë¤«¤Ï¡¢ + »ä¤Ï¾Ü¤·¤¯¤Ê¤¤¤Î¤Ç¤¹¤¬¡¢¥ê¥È¥ë¥¨¥ó¥Ç¥£¥¢¥ó¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤È»×¤¤¤Þ¤¹¡£ + XDR »ÅÍͤǤ½¤¦¤Ê¤Ã¤Æ¤¤¤ë¤Î¤È¡¢ÁÇÀ²¤é¤·¤¤¤³¤È¤Ë sys/socket ¥é¥¤¥Ö¥é¥ê¤¬ + (C ¤Ç) ¤½¤¦¤¤¤¦É÷¤Ë¤Ç¤­¤Æ¤¤¤ë¤Î¤Ç¤½¤¦¤Ê¤Î¤À¤È»×¤¤¤Þ¤·¤¿¡£ + ¥½¥±¥Ã¥È¸Æ¤Ó½Ð¤·¤ÎÆâÉô¤Ë¤Ä¤¤¤Æ¤è¤ê¾Ü¤·¤¤Êý¤¬¤¤¤é¤Ã¤·¤ã¤¤¤Þ¤·¤¿¤é¡¢ + ¤´¶µ¼ø¤¯¤À¤µ¤¤¡£

+

¥×¥í¥È¥³¥ë¤Ë¤Ï 4 ¤Ä¤Î¥Ç¡¼¥¿¥¿¥¤¥×¤¬¤¢¤ê¤Þ¤¹: byte, boolean, + integer, string ¤Ç¤¹¡£

+
+
Byte
¥Ð¥¤¥È°ì¤Ä¤Ç¤¹¡£
+
Boolean
+
¥Ð¥¤¥È°ì¤Ä¤Ç¡¢1 = true, 0 = false ¤Ç¤¹¡£ + (C ¤Î¤è¤¦¤Ë) ÈóÎí¤ò¿¿¤È¤·¤Æ°·¤Ã¤Æ¤·¤Þ¤¦¤È¡¢¤¢¤ë¾ì¹ç¤ÏÆ°¤¯¤«¤â¤·¤ì¤Þ¤»¤ó¤·¡¢ + Æ°¤«¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
+
Integer
+
0 ¤«¤é 2^16 (32768) ¤ÎÈϰϤοô»ú¡£¹â¼¡¤Î 2 ¥Ð¥¤¥È¤¬ + Àè¤Ë³ÊǼ¤µ¤ì¤Þ¤¹¡£
+
String
+
²ÄÊÑŤÎʸ»úÎó (2^16 ¤¬Ä¹¤µ¤Î¾å¸Â) ¡£Ä¹¤µ¾ðÊó¤Î¥Ñ¥±¥Ã¥È 2 ¥Ð¥¤¥È¤Î¸å¤Ë + ʸ»úÎó (½ªÃ¼Ê¸»ú '\0' ¤ò´Þ¤à) ¤¬Â³¤¯·Á¼°¤Ç¥¨¥ó¥³¡¼¥É¤µ¤ì¤Þ¤¹¡£ + ¥¨¥ó¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ëŤµ¾ðÊó¤ÏºÇ¸å¤Î '\0' ¤ò¥«¥¦¥ó¥È¤·¤Ê¤¤ + ¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡½¡½¤³¤ì¤Ï strlen ¤ÈƱÍͤǤ¹¡£ + ¤³¤ì¤é¤Î½ªÃ¼Ê¸»ú¤ò¥¹¥­¥Ã¥×¤¹¤ë¤¿¤á¤Ë¡¢¤¢¤Þ¤ê°ÕÌ£¤Î̵¤¤¥¤¥ó¥¯¥ê¥á¥ó¥Èʸ + ¤ò¤¿¤¯¤µ¤ó½ñ¤«¤Ê¤¤¤È¤¤¤±¤Ê¤¤¤Î¤Ï¡¢ + Java ¤Î¦¤«¤é¸«¤ë¤È¾¯¤·Ê¶¤é¤ï¤·¤¯´¶¤¸¤é¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤³¤¦¤Ê¤Ã¤¿Íýͳ¤Ï¤ª¤½¤é¤¯¡¢Servlet ¥³¥ó¥Æ¥Ê¤«¤éÊÖ¤µ¤ì¤ëʸ»úÎó¤òÆɤ߽Ф¹»þ¤Ë¡¢ + ¸úΨ¤è¤¯ C ¤Î¥³¡¼¥É¤ò½ñ¤±¤ë¤è¤¦¤Ë¤¹¤ë¡½¡½¥µ¡¼¥Ö¥ì¥Ã¥È¤«¤éÊÖ¤µ¤ì¤ë + ʸ»úÎó¤Ï \0 ʸ»ú¤Ç½ªÃ¼¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢C ¤Î¥³¡¼¥É¤Ç¤Ï¤ï¤¶¤ï¤¶¥³¥Ô¡¼¤ò¤»¤º¤Ë¡¢ + °ì¤Ä¤Î¥Ð¥Ã¥Õ¥¡¤Ø¤Î¥ê¥Õ¥¡¥ì¥ó¥¹¤ò¼è¤ê²ó¤¹¤è¤¦¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¤ë¡½¡½ + ¤¿¤á¤À¤È»×¤ï¤ì¤Þ¤¹¡£ + '\0' ʸ»ú¤¬¤Ê¤¤¾ì¹ç¤Ï¡¢C ¤Ç¤Ïʸ»úÎó¤Îµ¬Â§¤Ë¹ç¤¦¤è¤¦¤Ë¥³¥Ô¡¼¤·¤Ê¤±¤ì¤Ð + ¤¤¤±¤Ê¤¯¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
+
+ +

¥Ñ¥±¥Ã¥È¥µ¥¤¥º

+

¿¤¯¤Î¥³¡¼¥É¤Ç¤½¤¦¤Ê¤Ã¤Æ¤¤¤ë¤Î¤Ç¤¹¤¬¡¢¥Ñ¥±¥Ã¥È¥µ¥¤¥º¤ÎºÇÂ祵¥¤¥º¤Ï + 8 * 1024 (8K) ¤Ç¤¹¡£¥Ñ¥±¥Ã¥È¤Î¼ÂºÝ¤ÎŤµ¤Ï¥Ø¥Ã¥À¤Ë + ¥¨¥ó¥³¡¼¥É¤µ¤ì¤ÆÆþ¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

¥Ñ¥±¥Ã¥È¥Ø¥Ã¥À

+

¥µ¡¼¥Ð¤«¤é¥³¥ó¥Æ¥Ê¤ËÁ÷½Ð¤µ¤ì¤ë¥Ñ¥±¥Ã¥È¤Ï 0x1234 ¤Ç»Ï¤Þ¤ê¤Þ¤¹¡£ + ¥³¥ó¥Æ¥Ê¤«¤é¥µ¡¼¥Ð¤ËÁ÷¤é¤ì¤ë¥Ñ¥±¥Ã¥È¤Ï AB (ASCII ¥³¡¼¥É A ¤È + ASCII ¥³¡¼¥É B) ¤Ç»Ï¤Þ¤ê¤Þ¤¹¡£¤³¤ÎÆó¥Ð¥¤¥È¤Î¸å¤Ë¡¢¥Ú¥¤¥í¡¼¥ÉŤ¬ (¾åµ­¤Î·Á¼°¤Ç) + ³¤­¤Þ¤¹¡£¤³¤Î¤¿¤á¡¢¥Ú¥¤¥í¡¼¥ÉĹ¤ÎºÇÂçÃÍ¤Ï 2^16 ¤Ë¤Ç¤­¤ë¤è¤¦¤Ë»×¤¨¤Þ¤¹¤¬¡¢ + ¼ÂºÝ¤Ë¤Ï¥³¡¼¥É¤Ç¤ÏºÇÂçÃÍ¤Ï 8K ¤ËÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£

+ + + + + + + + + + + + + + + + + + + +
¥Ñ¥±¥Ã¥È·Á¼° (Server->Container)
Byte01234...(n+3)
Contents0x120x34¥Ç¡¼¥¿Ä¹ (n)Data
+ + + + + + + + + + + + + + + + + + + +
¥Ñ¥±¥Ã¥È·Á¼° (Container->Server)
Byte01234...(n+3)
ContentsAB¥Ç¡¼¥¿Ä¹ (n)Data
+

¤Û¤È¤ó¤É¤Î¥Ñ¥±¥Ã¥È¤Ç¡¢¥Ú¥¤¥í¡¼¥É¤ÎºÇ½é¤Î¥Ð¥¤¥È¤¬¥á¥Ã¥»¡¼¥¸¤Î·¿¤ò¥¨¥ó¥³¡¼¥É + ¤·¤Æ¤¤¤Þ¤¹¡£Îã³°¤Ï¥µ¡¼¥Ð¤«¤é¥³¥ó¥Æ¥Ê¤ËÁ÷¤é¤ì¤ë¥ê¥¯¥¨¥¹¥È¥Ü¥Ç¥£¥Ñ¥±¥Ã¥È¤Ç¤¹ + ¡½¡½¤³¤ì¤é¤Ïɸ½àŪ¤Ê¥Ñ¥±¥Ã¥È·Á¼° (0x1234 ¤È¥Ñ¥±¥Ã¥ÈĹ) + ¤Ç¤¹¤¬¡¢¤½¤Î¸å¤Ë³¤¯¥×¥ì¥Õ¥£¥Ã¥¯¥¹¥³¡¼¥É¤¬¤¢¤ê¤Þ¤»¤ó¡£

+

¥¦¥§¥Ö¥µ¡¼¥Ð¤Ï¼¡¤Î¥á¥Ã¥»¡¼¥¸¤ò¥µ¡¼¥Ö¥ì¥Ã¥È¥³¥ó¥Æ¥Ê¤ËÁ÷½Ð¤Ç¤­¤Þ¤¹¡£

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¥³¡¼¥É¥Ñ¥±¥Ã¥È¤Î·¿°ÕÌ£
2Forward Request¥ê¥¯¥¨¥¹¥È½èÍý¥µ¥¤¥¯¥ë¤ò¸å³¤Î¥Ç¡¼¥¿¤È¤È¤â¤Ë³«»Ï¤¹¤ë¡£
7Shutdown¥¦¥§¥Ö¥µ¡¼¥Ð¤¬¥³¥ó¥Æ¥Ê¤Ë¡¢¥³¥ó¥Æ¥Ê¤ò½ªÎ»¤¹¤ë¤è¤¦¤ËÅÁ¤¨¤ë¡£
8Ping¥¦¥§¥Ö¥µ¡¼¥Ð¤¬¥³¥ó¥Æ¥Ê¤ËÀ©¸æ¤ò¼õ¤±»ý¤Ä¤è¤¦¤ËÅÁ¤¨¤ë + (¥»¥­¥å¥¢¥í¥°¥¤¥ó¥Õ¥§¡¼¥º) ¡£
10CPing¥¦¥§¥Ö¥µ¡¼¥Ð¤¬¥³¥ó¥Æ¥Ê¤Ë CPong ¤Ç¨ºÂ¤Ë±þÅú¤¹¤ë¤è¤¦¤ËÅÁ¤¨¤ë¡£
noneData¥µ¥¤¥º (2 ¥Ð¥¤¥È) ¤È¤½¤ì¤Ë³¤¯¥Ü¥Ç¥£¥Ç¡¼¥¿¡£
+

´ðËÜŪ¤Ê¥»¥­¥å¥ê¥Æ¥£¤ò³ÎÊݤ¹¤ë¤¿¤á¡¢¥Û¥¹¥È¤µ¤ì¤Æ¤¤¤ë¥Þ¥·¥ó¤ÈƱ°ì¤Î + ¥Þ¥·¥ó¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¤Î¤ß¡¢¥³¥ó¥Æ¥Ê¤Ï¼ÂºÝ¤Ë Shutdown + ¤ò¼Â¹Ô¤·¤Þ¤¹¡£

+

ºÇ½é¤Î Data ¥Ñ¥±¥Ã¥È¤Ï¡¢Forward Request + ¤Îľ¸å¤Ë¥¦¥§¥Ö¥µ¡¼¥Ð¤«¤éÁ÷¤é¤ì¤Þ¤¹¡£

+

¥µ¡¼¥Ö¥ì¥Ã¥È¥³¥ó¥Æ¥Ê¤Ï¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë¡¢¼¡¤Î¥¿¥¤¥×¤Î¥á¥Ã¥»¡¼¥¸¤òÁ÷¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹ :

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¥³¡¼¥É¥Ñ¥±¥Ã¥È¤Î·¿°ÕÌ£
3Send Body Chunk¥µ¡¼¥Ö¥ì¥Ã¥È¥³¥ó¥Æ¥Ê¤«¤é¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë + (¤½¤·¤Æ¤ª¤½¤é¤¯¤½¤Î¤Þ¤Þ¥Ö¥é¥¦¥¶¤Ë)¡¢¥Ü¥Ç¥£¤Î¥Á¥ã¥ó¥¯¤òÁ÷¤ë¡£
4Send Headers¥µ¡¼¥Ö¥ì¥Ã¥È¥³¥ó¥Æ¥Ê¤«¤é¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë (¤½¤·¤Æ¤ª¤½¤é¤¯¤½¤Î¤Þ¤Þ¥Ö¥é¥¦¥¶¤Ë) + ¥ì¥¹¥Ý¥ó¥¹¥Ø¥Ã¥À¤òÁ÷¤ë¡£
5End Response¥ì¥¹¥Ý¥ó¥¹ (¤Ä¤Þ¤ê¥ê¥¯¥¨¥¹¥È½èÍý¥µ¥¤¥¯¥ë) ½ªÎ»¤ÎÌÜ°õ¤òÁ÷¤ë¡£ +
6Get Body Chunk¤Þ¤ÀÁ´¤ÆžÁ÷¤µ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢»Ä¤Ã¤Æ¤¤¤ë¥ê¥¯¥¨¥¹¥È¤Î¥Ç¡¼¥¿¤ò¼õ¤±¼è¤ë¡£ +
9CPong ±þÅúCPing ¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¡£
+

¾åµ­¥á¥Ã¥»¡¼¥¸¤Ï¡¢¤½¤ì¤¾¤ìÆâÉô¹½Â¤¤¬°Û¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£¾ÜºÙ¤Ï²¼µ­¤ò¤´Í÷¤¯¤À¤µ¤¤¡£ +

+ +
top
+
+

¥ê¥¯¥¨¥¹¥È¥Ñ¥±¥Ã¥È¹½Â¤

+

¥µ¡¼¥Ð¤«¤é¥³¥ó¥Æ¥Ê¤ØÁ÷¤é¤ì¤ë¥á¥Ã¥»¡¼¥¸¤¬ + Forward Request ·¿¤Î¾ì¹ç :

+ 
+AJP13_FORWARD_REQUEST :=
+    prefix_code      (byte) 0x02 = JK_AJP13_FORWARD_REQUEST
+    method           (byte)
+    protocol         (string)
+    req_uri          (string)
+    remote_addr      (string)
+    remote_host      (string)
+    server_name      (string)
+    server_port      (integer)
+    is_ssl           (boolean)
+    num_headers      (integer)
+    request_headers *(req_header_name req_header_value)
+    attributes      *(attribut_name attribute_value)
+    request_terminator (byte) OxFF
+
+

request_headers ¤Ï¼¡¤Î¤è¤¦¤Ê¹½Â¤¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹ : + 

+req_header_name := 
+    sc_req_header_name | (string)  [see below for how this is parsed]
+
+sc_req_header_name := 0xA0xx (integer)
+
+req_header_value := (string)
+
+

°À­ ¤Ï¥ª¥×¥·¥ç¥ó¤Ç¡¢¼¡¤Î¤è¤¦¤Ê¹½Â¤¤ò¤·¤Æ¤¤¤Þ¤¹ :

+ 
+attribute_name := sc_a_name | (sc_a_req_attribute string)
+
+attribute_value := (string)
+
+
+

¤â¤Ã¤È¤â½ÅÍפʥإåÀ¤Ï content-length ¤À¤È¤¤¤¦¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¥³¥ó¥Æ¥Ê¤Ï¼¡¤Î¥Ñ¥±¥Ã¥È¤òõ¤¹¤«¤É¤¦¤«¤ò¡¢ + ¤½¤ì¤ò¸«¤Æ·è¤á¤ë¤«¤é¤Ç¤¹¡£

+

Forward Request Í×ÁǤξܺ٤ÊÀâÌÀ +

+

Request prefix

+

¥ê¥¯¥¨¥¹¥È¤Ë¤Ä¤¤¤Æ¤ÏÁ´¤Æ¡¢¤³¤ÎÃÍ¤Ï 2 ¤Ë¤Ê¤ê¤Þ¤¹¡£Â¾¤Î Prefix ¥³¡¼¥É¤Î¾ÜºÙ¤Ï + ¾åµ­¤ò¤´Í÷¤¯¤À¤µ¤¤¡£

+ +

Method

+

HTTP ¥á¥½¥Ã¥É¤Ï 1 ¥Ð¥¤¥È¤Ë¥¨¥ó¥³¡¼¥É¤µ¤ì¤Þ¤¹ :

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Command NameCode
OPTIONS1
GET2
HEAD3
POST4
PUT5
DELETE6
TRACE7
PROPFIND8
PROPPATCH9
MKCOL10
COPY11
MOVE12
LOCK13
UNLOCK14
ACL15
REPORT16
VERSION-CONTROL17
CHECKIN18
CHECKOUT19
UNCHECKOUT20
SEARCH21
MKWORKSPACE22
UPDATE23
LABEL24
MERGE25
BASELINE_CONTROL26
MKACTIVITY27
+

º£¸å¤Î ajp13 ¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢¤³¤Î°ìÍ÷¤Ë¤Ê¤¤¡¢º£¸åÄɲ䵤ì¤ë¥á¥½¥Ã¥É¤ò + Á÷¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ +

protocol, req_uri, remote_addr, remote_host, server_name, + server_port, is_ssl

+

¤³¤ì¤é¤Ï¤Þ¤µ¤Ëʸ»úÄ̤ê¤Î¤â¤Î¤Ç¤¹¡£¤É¤ì¤âɬÍפǡ¢¥ê¥¯¥¨¥¹¥È¤ÎËè²ó¤Ë¤Ä¤­ + Á÷¤é¤ì¤Þ¤¹¡£

+ +

Headers

+

request_headers ¤Î¹½Â¤¤Ï¼¡¤Î¤è¤¦¤Ê¤â¤Î¤Ç¤¹ : + ¤Þ¤º¥Ø¥Ã¥À¤Î¿ô num_headers ¤¬¥¨¥ó¥³¡¼¥É¤µ¤ì¤Þ¤¹¡£ + ¼¡¤Ë¥Ø¥Ã¥À̾ req_header_name / ÃÍ req_header_value + ¤ÎÁȤ¬Â³¤­¤Þ¤¹¡£¸úΨ¤Î¤¿¤á¡¢°ìÈÌŪ¤Ê¥Ø¥Ã¥À¤ÏÀ°¿ô¤Ç¥¨¥ó¥³¡¼¥É¤·¤ÆžÁ÷¤·¤Þ¤¹¡£ + ¥Ø¥Ã¥À̾¤¬´ðËܥإåÀ¤Î°ìÍ÷¤Ë̵¤¤¾ì¹ç¤Ï¡¢Ä̾ïÄ̤ê (ʸ»úÎó¤È¤·¤Æ¡¢Ä¹¤µ + ¥×¥ì¥Õ¥£¥Ã¥¯¥¹ÉÕ¤­¤Ç) žÁ÷¤µ¤ì¤Þ¤¹¡£°ìÈÌŪ¤Ê¥Ø¥Ã¥À + sc_req_header_name ¤Î°ìÍ÷¤È¤½¤Î¥³¡¼¥É¤Ï¼¡¤ÎÄ̤ê¤Ç¤¹ + (¤É¤ì¤âÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Þ¤¹) :

+ + + + + + + + + + + + + + + + + + + +
̾Á°¥³¡¼¥É¤ÎÃÍ¥³¡¼¥É̾
accept0xA001SC_REQ_ACCEPT
accept-charset0xA002SC_REQ_ACCEPT_CHARSET +
accept-encoding0xA003SC_REQ_ACCEPT_ENCODING +
accept-language0xA004SC_REQ_ACCEPT_LANGUAGE +
authorization0xA005SC_REQ_AUTHORIZATION
connection0xA006SC_REQ_CONNECTION
content-type0xA007SC_REQ_CONTENT_TYPE
content-length0xA008SC_REQ_CONTENT_LENGTH
cookie0xA009SC_REQ_COOKIE
cookie20xA00ASC_REQ_COOKIE2
host0xA00BSC_REQ_HOST
pragma0xA00CSC_REQ_PRAGMA
referer0xA00DSC_REQ_REFERER
user-agent0xA00ESC_REQ_USER_AGENT
+

¤³¤ì¤òÆɤ߹þ¤à Java ¤Î¥³¡¼¥É¤Ç¤Ï¡¢ºÇ½é¤Î 2 ¥Ð¥¤¥ÈÀ°¿ô¤ò¼è¤ê¹þ¤ß¡¢ + ÌÜ°õ¤Ë¤Ê¤ë¥Ð¥¤¥È '0xA0' ¤Ç¤¢¤ì¤Ð¡¢¥Ø¥Ã¥À̾¤ÎÇÛÎó¤Î + ¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤¤¤Þ¤¹¡£ÀèƬ¥Ð¥¤¥È¤¬ 0xA0 ¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢ + ÀèƬ 2 ¥Ð¥¤¥È¤Ïʸ»úÎóŤòɽ¤¹À°¿ô¤Ç¤¢¤ë¤È²ò¼á¤·¡¢Æɤ߹þ¤ß¤Ï¤¸¤á¤Þ¤¹¡£

+

¥Ø¥Ã¥À̾¤ÎŤµ¤Ï 0x9999 (==0xA000 -1) °Ê¾å¤Ë¤Ê¤é¤Ê¤¤¤È¤¤¤¦ + ²¾Äê¤Î²¼¤ËÆ°¤¤¤Æ¤¤¤Æ¡¢¾¯¤·¤¢¤¤¤Þ¤¤¤Ç¤¹¤¬¹çÍýŪ¤ÊµóÆ°¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+

Ãí:

+ content-length ¥Ø¥Ã¥À¤Ï¤È¤Æ¤â½ÅÍפǤ¹¡£ + ¸ºß¤·¤Æ¤¤¤ÆÈó¥¼¥í¤Ç¤¢¤ì¤Ð¡¢¥ê¥¯¥¨¥¹¥È¤Ë¤Ï¥Ü¥Ç¥£¤¬¤¢¤ë (Î㤨¤Ð POST + ¥ê¥¯¥¨¥¹¥È) ¤È¿ä¬¤·¡¢¤½¤Î¥Ü¥Ç¥£¤ò¼è¤ê¹þ¤à¤¿¤á¤Ë + ľ¸å¤Î¥Ñ¥±¥Ã¥È¤òÆþÎÏ¥¹¥È¥ê¡¼¥à¤«¤éÆɤ߹þ¤ß¤Ï¤¸¤á¤Þ¤¹¡£ +
+ +

°À­

+

? ¥×¥ì¥Õ¥£¥Ã¥¯¥¹¤Ç»Ï¤Þ¤ë°À­ (Îã ?context) + ¤Ï¡£¾Êά²Äǽ¤Ç¤¹¡£¤½¤ì¤¾¤ì°À­¤Î·¿¤ò¼¨¤¹ 1 ¥Ð¥¤¥È¤Î¥³¡¼¥É¤È¡¢ + ÃͤÎʸ»úÎó¤¬Â³¤­¤Þ¤¹¡£ + ¤³¤ì¤é¤Ï½çÉÔƱ¤ÇÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹ (C ¤Î¥³¡¼¥É¤Ï¾ï¤Ë²¼¤Î°ìÍ÷½ç¤Ë + Á÷¤ë¤è¤¦¤Ç¤¹¤¬) ¡£ + ¥ª¥×¥·¥ç¥ó¤Î°À­¤Î¥ê¥¹¥È¤ÎºÇ¸å¤Ë¤Ï¡¢ÆÃÊ̤ʽªÎ»¥³¡¼¥É¤¬Á÷¤é¤ì¤Þ¤¹¡£ + ¥³¡¼¥É¤Î°ìÍ÷¤Ï :

+ + + + + + + + + + + + + + +
InformationCode ValueNote
?context0x01̤¼ÂÁõ +
?servlet_path0x02̤¼ÂÁõ +
?remote_user0x03
?auth_type0x04
?query_string0x05
?jvm_route0x06
?ssl_cert0x07
?ssl_cipher0x08
?ssl_session0x09
?req_attribute0x0AName (the name of the + attribute follows)
?ssl_key_size0x0B
are_done0xFFrequest_terminator
+

context ¤È servlet_path ¤Ï¸½ºß¤Î C ¤Î + ¥³¡¼¥É¤Ç¤Ï¥»¥Ã¥È¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£¤Þ¤¿¡¢¤Û¤È¤ó¤É¤Î Java ¤Î¥³¡¼¥É¤Ç¤â¡¢ + ¤³¤Î¥Õ¥£¡¼¥ë¥É¤Ç²¿¤¬Á÷¤é¤ì¤Æ¤â̵»ë¤µ¤ì¤Þ¤¹ (¤³¤ì¤é¤Î¥³¡¼¥É¤Î¸å¤Ëʸ»úÎó¤¬ + Á÷¤é¤ì¤ë¤È²õ¤ì¤ë¤â¤Î¤â¤¢¤ê¤Þ¤¹)¡£ + ¤³¤ì¤¬¥Ð¥°¤Ê¤Î¤«¡¢Ã±¤Ë̤¼ÂÁõ¤Ê¤Î¤«¡¢Îò»ËŪ·Ð°Þ¤Ç»Ä¤Ã¤Æ¤¤¤ë¥³¡¼¥É¤Ê¤Î¤« + ʬ¤«¤ê¤Þ¤»¤ó¤¬¡¢¥³¥Í¥¯¥·¥ç¥ó¤Îξ¦¤È¤â¤Ç¸«Åö¤¿¤ê¤Þ¤»¤ó¡£

+

remote_user ¤È auth_type ¤Ï¤ª¤½¤é¤¯ + HTTP ¥ì¥Ù¥ë¤Îǧ¾Ú¤ò»²¾È¤·¤Æ¤¤¤Æ¡¢¥ê¥â¡¼¥È¥æ¡¼¥¶¤Î¥æ¡¼¥¶Ì¾¤Èǧ¾Ú¤Ë»ÈÍѤ·¤¿ + ¥¿¥¤¥× (Îã Basic, Digest) ¤Ë¤Ä¤¤¤Æ¤ä¤ê¼è¤ê¤·¤Þ¤¹¡£

+

query_string, ssl_cert, + ssl_cipher, ssl_session + ¤Ï HTTP ¤È HTTPS ¤ÎÂбþ¤¹¤ëÉôʬ¤ò»²¾È¤·¤Þ¤¹¡£

+

jvm_route ¤Ï¥¹¥Æ¥£¥Ã¥­¡¼¥»¥Ã¥·¥ç¥ó¤Î¥µ¥Ý¡¼¥È¡½¡½ + ¥í¡¼¥É¥Ð¥é¥ó¥¹¤·¤Æ¤¤¤ëÊ£¿ô¤Î¥µ¡¼¥ÐÃæ¤ÎÆÃÄê¤Î Tomcat ¥¤¥ó¥¹¥¿¥ó¥¹¤È¡¢ + ¥æ¡¼¥¶¤Î¥»¥Ã¥·¥ç¥ó¤È¤òɳÉÕ¤±¤ëµ¡Ç½¡½¡½¤Ë»È¤ï¤ì¤Þ¤¹¡£

+

¤³¤Î´ðËÜ°À­°ìÍ÷¤Ë̵¤¤¤â¤Î¤Ë¤Ä¤¤¤Æ¤Ï¡¢req_attribute + ¥³¡¼¥É 0x0A ·Ðͳ¤Ç°À­¤ò²¿¸Ä¤Ç¤âÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + °À­¤Î̾Á°¤ÈÃͤÎʸ»úÎó¤ÎÁȤò¡¢¤½¤ì¤¾¤ì¤³¤Î¥³¡¼¥É¤Îľ¸å¤ËÁ÷¤ê¤Þ¤¹¡£ + ´Ä¶­ÊÑ¿ô¤Ï¤³¤ÎÊýË¡¤ÇÅÁ¤¨¤é¤ì¤Þ¤¹¡£

+

ºÇ¸å¤Ë°À­¤¬Á´¤ÆÁ÷¿®¤µ¤ì¤¿¸å¤Ë¡¢Â°À­¤Î½ªÃ¼¤ò¼¨¤¹ 0xFF + ¤¬Á÷½Ð¤µ¤ì¤Þ¤¹¡£¤³¤Î¿®¹æ¤Ï°À­¤Î°ìÍ÷¤Î½ª¤ï¤ê¤ò¼¨¤¹¤ÈƱ»þ¤Ë¡¢¥ê¥¯¥¨¥¹¥È + ¥Ñ¥±¥Ã¥È¤Î½ªÃ¼¤ò¤â¼¨¤·¤Æ¤¤¤Þ¤¹¡£

+ +
top
+
+

¥ì¥¹¥Ý¥ó¥¹¥Ñ¥±¥Ã¥È¹½Â¤

+

¥³¥ó¥Æ¥Ê¤¬¥µ¡¼¥Ð¤ËÁ÷¤êÊÖ¤¹¤³¤È¤Î¤Ç¤­¤ë¥á¥Ã¥»¡¼¥¸:

+ 
+AJP13_SEND_BODY_CHUNK :=
+  prefix_code   3
+  chunk_length  (integer)
+  chunk        *(byte)
+
+
+AJP13_SEND_HEADERS :=
+  prefix_code       4
+  http_status_code  (integer)
+  http_status_msg   (string)
+  num_headers       (integer)
+  response_headers *(res_header_name header_value)
+
+res_header_name :=
+    sc_res_header_name | (string)   [see below for how this is parsed]
+
+sc_res_header_name := 0xA0 (byte)
+
+header_value := (string)
+
+AJP13_END_RESPONSE :=
+  prefix_code       5
+  reuse             (boolean)
+
+
+AJP13_GET_BODY_CHUNK :=
+  prefix_code       6
+  requested_length  (integer)
+
+

¾ÜºÙ :

+

Send Body Chunk

+

¥Á¥ã¥ó¥¯¤Ï´ðËÜŪ¤Ë¤Ï¥Ð¥¤¥Ê¥ê¥Ç¡¼¥¿¤Ç¡¢¥Ö¥é¥¦¥¶¤ËľÀÜÁ÷¤é¤ì¤Þ¤¹¡£

+ +

Send Headers

+

¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É¤È¥á¥Ã¥»¡¼¥¸¤¬Ä̾ï¤Î HTTP ¤ÎÄÌ¿®¤Ë¤Ï¤¢¤ê¤Þ¤¹ (Îã + 200 ¤È OK)¡£¥ì¥¹¥Ý¥ó¥¹¥Ø¥Ã¥À̾¤Ï¡¢ + ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À̾¤ÈƱÍͤÎÊýË¡¤Ç¥¨¥ó¥³¡¼¥É¤µ¤ì¤Þ¤¹¡£ + ¥³¡¼¥É¤Èʸ»úÎó¤ÎȽÊÌÊýË¡¤Î¾ÜºÙ¤Ë´Ø¤·¤Æ¤Ï¡¢¾åµ­¤Î header_encoding + ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ + °ìÈÌŪ¤Ê¥Ø¥Ã¥À¤Î¥³¡¼¥É¤Ï :

+ + + + + + + + + + + + + +
̾Á°¥³¡¼¥É¤ÎÃÍ
Content-Type0xA001
Content-Language0xA002
Content-Length0xA003
Date0xA004
Last-Modified0xA005
Location0xA006
Set-Cookie0xA007
Set-Cookie20xA008
Servlet-Engine0xA009
Status0xA00A
WWW-Authenticate0xA00B
+

¥³¡¼¥É¤«¥Ø¥Ã¥Àʸ»úÎó¤Îľ¸å¤Ë¤Ï¡¢¥Ø¥Ã¥À¤ÎÃͤ¬¥¨¥ó¥³¡¼¥É¤µ¤ì¤Þ¤¹¡£

+ +

End Response

+

¥ê¥¯¥¨¥¹¥È½èÍý¥µ¥¤¥¯¥ë¤Î½ªÎ»¤òÃΤ餻¤Þ¤¹¡£reuse ¥Õ¥é¥°¤¬¿¿ + (==1) ¤Î¾ì¹ç¡¢¸½ºß»ÈÍѤ·¤Æ¤¤¤ë TCP ¥³¥Í¥¯¥·¥ç¥ó¤Ï¼¡¤Î¿·¤·¤¤ + ¥ê¥¯¥¨¥¹¥È¤Ë»È¤¨¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£reuse ¤¬µ¶ (C ¤Î¥³¡¼¥É¤Ç¤Ï + 1 °Ê³°¤ÎÁ´¤Æ) ¤Î¾ì¹ç¤Ï¡¢¥³¥Í¥¯¥·¥ç¥ó¤òÊĤ¸¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Get Body Chunk

+

(¥Ü¥Ç¥£¤Î¥µ¥¤¥º¤¬Â礭¤¹¤®¤ÆºÇ½é¤Î¥Ñ¥±¥Ã¥È¤Ë¼ý¤Þ¤é¤Ê¤¤¾ì¹ç¤ä¡¢ + ¥ê¥¯¥¨¥¹¥È¤¬¥Á¥ã¥ó¥¯Å¾Á÷¤µ¤ì¤¿¾ì¹ç¤Ê¤É¤Ë¤Ï¡¢) ¥³¥ó¥Æ¥Ê¤Ï¥ê¥¯¥¨¥¹¥È¤«¤é¤Î + ¥Ç¡¼¥¿Æɤ߹þ¤ßÍ×µá¤ò¤·¤Þ¤¹¡£¥µ¡¼¥Ð¦¤Ï¤½¤ì¤ËÂФ·¤Æ¡¢ºÇ¾® + request_length ºÇÂç (8186 (8 Kbytes - 6)) + ¤ÎÈϰϤǡ¢Ì¤Å¾Á÷¤Ç»Ä¤Ã¤Æ¤¤¤ë¥ê¥¯¥¨¥¹¥È¥Ü¥Ç¥£¤ÎÂ礭¤µ¤Î¥Ç¡¼¥¿¤ò + Á÷¤êÊÖ¤·¤Þ¤¹¡£
+ ¥Ü¥Ç¥£¤Ë¤½¤ì°Ê¾å¥Ç¡¼¥¿¤¬»Ä¤Ã¤Æ¤¤¤Ê¤¤¾ì¹ç (¤Ä¤Þ¤ê¥µ¡¼¥Ö¥ì¥Ã¥È¤¬ + ¥Ü¥Ç¥£¤ÎºÇ¸å¤òĶ¤¨¤ÆÆɤ߹þ¤â¤¦¤È¤·¤¿¾ì¹ç) ¡¢¥µ¡¼¥Ð¤Ï + ¥Ú¥¤¥í¡¼¥ÉĹ 0 ¤Î¶õ¥Ñ¥±¥Ã¥È(0x12,0x34,0x00,0x00) + ¤òÁ÷¤êÊÖ¤·¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy_balancer.html b/docs/manual/mod/mod_proxy_balancer.html new file mode 100644 index 00000000..bca5d274 --- /dev/null +++ b/docs/manual/mod/mod_proxy_balancer.html @@ -0,0 +1,7 @@ +URI: mod_proxy_balancer.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_proxy_balancer.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mod_proxy_balancer.html.en b/docs/manual/mod/mod_proxy_balancer.html.en new file mode 100644 index 00000000..a857b429 --- /dev/null +++ b/docs/manual/mod/mod_proxy_balancer.html.en @@ -0,0 +1,316 @@ + + + +mod_proxy_balancer - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_proxy_balancer

+
+

Available Languages:  en  | + ja 

+
+ + + + +
Description:mod_proxy extension for load balancing
Status:Extension
Module Identifier:proxy_balancer_module
Source File:proxy_balancer.c
Compatibility:Available in version 2.1 and later
+

Summary

+ +

This module requires the service of mod_proxy. It provides load balancing support for + HTTP, FTP and AJP13 protocols +

+ +

Thus, in order to get the ability of load balancing, + mod_proxy and mod_proxy_balancer + have to be present in the server.

+ +

Warning

+

Do not enable proxying until you have secured your server. Open proxy + servers are dangerous both to your network and to the Internet at + large.

+
+
+ +
top
+
+

Load balancer scheduler algorithm

+ +

At present, there are 2 load balancer scheduler algorithms available + for use: Request Counting and Weighted Traffic Counting. These are controlled + via the lbmethod value of the Balancer definition. See + the Proxy directive for + more information.

+ +
top
+
+

Request Counting Algorithm

+ +

Enabled via lbmethod=byrequests, the idea behind this + scheduler is that we distribute the requests among the + various workers to ensure that each gets their configured share + of the number of requests. It works as follows:

+ +

lbfactor is how much we expect this worker + to work, or the workers's work quota. This is + a normalized value representing their "share" of the amount of + work to be done.

+ +

lbstatus is how urgent this worker has to work + to fulfill its quota of work.

+ +

The worker is a member of the load balancer, + usually a remote host serving one of the supported protocols.

+ +

We distribute each worker's work quota to the worker, and then look + which of them needs to work most urgently (biggest lbstatus). This + worker is then selected for work, and its lbstatus reduced by the + total work quota we distributed to all workers. Thus the sum of all + lbstatus does not change(*) and we distribute the requests + as desired.

+ +

If some workers are disabled, the others will + still be scheduled correctly.

+ + 
for each worker in workers
+    worker lbstatus += worker lbfactor
+    total factor    += worker lbfactor
+    if worker lbstatus > candidate lbstatus
+        candidate = worker
+
+candidate lbstatus -= total factor
+ +

If a balancer is configured as follows:

+ + + + + + + + + + + + + + + + +
workerabcd
lbfactor25252525
lbstatus0000
+ +

And b gets disabled, the following schedule is produced:

+ + + + + + + + + + + + + + + + + + + + + + +
workerabcd
lbstatus-5002525
lbstatus-250-2550
lbstatus0000
(repeat)
+ +

That is it schedules: a c d + a c d a c + d ... Please note that:

+ + + + + + + + + + + +
workerabcd
lbfactor25252525
+ +

Has the exact same behavior as:

+ + + + + + + + + + + +
workerabcd
lbfactor1111
+ +

This is because all values of lbfactor are normalized + with respect to the others. For:

+ + + + + + + + + +
workerabc
lbfactor141
+ +

worker b will, on average, get 4 times the requests + that a and c will.

+ +

The following asymmetric configuration works as one would expect:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
workerab
lbfactor7030
 
lbstatus-3030
lbstatus40-40
lbstatus10-10
lbstatus-2020
lbstatus-5050
lbstatus20-20
lbstatus-1010
lbstatus-4040
lbstatus30-30
lbstatus00
(repeat)
+ +

That is after 10 schedules, the schedule repeats and 7 a + are selected with 3 b interspersed.

+
top
+
+

Weighted Traffic Counting Algorithm

+ +

Enabled via lbmethod=bytraffic, the idea behind this + scheduler is very similar to the Request Counting method, with + the following changes:

+ +

lbfactor is how much traffic, in bytes, we want + this worker to handle. This is also a normalized value + representing their "share" of the amount of work to be done, + but instead of simply counting the number of requests, we take + into account the amount of traffic this worker has seen.

+ +

If a balancer is configured as follows:

+ + + + + + + + + +
workerabc
lbfactor121
+ +

Then we mean that we want b to process twice the + amount of bytes than a or c should. It does + not necessarily mean that b would handle twice as + many requests, but it would process twice the I/O. Thus, the + size of the request and response are applied to the weighting + and selection algorithm.

+ +
top
+
+

Enabling Balancer Manager Support

+ +

This module requires the service of + mod_status. + Balancer manager enables dynamic update of balancer + members. You can use balancer manager to change the balance + factor or a particular member, or put it in the off line + mode. +

+ +

Thus, in order to get the ability of load balancer management, + mod_status and mod_proxy_balancer + have to be present in the server.

+ +

To enable load balancer management for browsers from the foo.com + domain add this code to your httpd.conf + configuration file

+

+ <Location /balancer-manager>
+ SetHandler balancer-manager
+
+ Order Deny,Allow
+ Deny from all
+ Allow from .foo.com
+ </Location> +

+ +

You can now access load balancer manager by using a Web browser + to access the page + http://your.server.name/balancer-manager

+
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy_balancer.html.ja.euc-jp b/docs/manual/mod/mod_proxy_balancer.html.ja.euc-jp new file mode 100644 index 00000000..6ba878eb --- /dev/null +++ b/docs/manual/mod/mod_proxy_balancer.html.ja.euc-jp @@ -0,0 +1,319 @@ + + + +mod_proxy_balancer - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_proxy_balancer

+
+

Available Languages:  en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + + +
ÀâÌÀ:Éé²Ùʬ»¶¤Î¤¿¤á¤Î mod_proxy ³ÈÄ¥
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:proxy_balancer_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:proxy_balancer.c
¸ß´¹À­:2.1 °Ê¹ß
+

³µÍ×

+ +

Ëܥ⥸¥å¡¼¥ë¤Ë¤Ï mod_proxy ¤¬É¬ÍפǤ¹¡£ + HTTP, FTP ¤È AJP13 + ¥×¥í¥È¥³¥ë¤Î¥í¡¼¥É¥Ð¥é¥ó¥¹µ¡Ç½¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

¤Ç¤¹¤«¤é¡¢ ¥í¡¼¥É¥Ð¥é¥ó¥¹¤òÍ­¸ú¤Ë¤¹¤ë¾ì¹ç mod_proxy + ¤È mod_proxy_balancer ¤¬¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ + ¤¤¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£

+ +

·Ù¹ð

+

°ÂÁ´¤Ê¥µ¡¼¥Ð¤Ë¤¹¤ë¤Þ¤Ç¥×¥í¥¯¥·µ¡Ç½¤ÏÍ­¸ú¤Ë¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + ¥ª¡¼¥×¥ó¥×¥í¥­¥·¥µ¡¼¥Ð¤Ï¤¢¤Ê¤¿¼«¿È¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤Ë¤È¤Ã¤Æ¤â¡¢ + ¥¤¥ó¥¿¡¼¥Í¥Ã¥ÈÁ´ÂΤˤȤäƤâ´í¸±¤Ç¤¹¡£

+
+
+ +
top
+
+

¥í¡¼¥É¥Ð¥é¥ó¥µ¤Î¥¹¥±¥¸¥å¡¼¥é¤Î¥¢¥ë¥´¥ê¥º¥à

+ +

¸½»þÅÀ¤Ç¤Ï 2 ¼ïÎà¤Î¥í¡¼¥É¥Ð¥é¥ó¥µ¥¹¥±¥¸¥å¡¼¥é¥¢¥ë¥´¥ê¥º¥à¤«¤éÁª¤Ù¤Þ¤¹¡£ + ¥ê¥¯¥¨¥¹¥È²ó¿ô¤Ë¤è¤ë¤â¤Î (ÌõÃí: Request Counting) + ¤È¡¢¥È¥é¥Õ¥£¥Ã¥¯Î̤ˤè¤ë¤â¤Î (ÌõÃí: Weighted Traffic Counting) + ¤¬¤¢¤ê¤Þ¤¹¡£¥Ð¥é¥ó¥µ¤ÎÀßÄê lbmethod Ãͤǡ¢¤É¤Á¤é¤ò»È¤¦¤«»ØÄꤷ¤Þ¤¹¡£ + ¾ÜºÙ¤Ï Proxy ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
top
+
+

Request Counting ¥¢¥ë¥´¥ê¥º¥à

+ +

lbmethod=byrequests ¤ÇÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤Î¥¹¥±¥¸¥å¡¼¥é¤ÎÇطʤˤ¢¤ë¹Í¤¨Êý¤Ï¡¢ÍÍ¡¹¤Ê¥ï¡¼¥«¡¼¤¬¤½¤ì¤¾¤ì¡¢ + ÀßÄꤵ¤ì¤Æ¤¤¤ëʬô¥ê¥¯¥¨¥¹¥È¿ô¤ò¤­¤Á¤ó¤È¼õ¤±¼è¤ì¤ë¤è¤¦¤Ë¡¢ + ¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤È¤¤¤¦¹Í¤¨Êý¤Ç¤¹¡£¼¡¤Î¤è¤¦¤ËÆ°ºî¤·¤Þ¤¹:

+ +

lbfactor ¤Ï¡¢¤É¤ÎÄøÅ٥¥«¡¼¤Ë»Å»ö¤ò¿¶¤ë¤« + ¤Ä¤Þ¤ê¥ï¡¼¥«¡¼¤Î¥¯¥ª¡¼¥¿¤ò»Ø¤·¤Þ¤¹¡£¤³¤ÎÃÍ¤Ï "ʬô" + Î̤òɽ¤¹Àµµ¬²½¤µ¤ì¤¿ÃͤǤ¹¡£

+ +

lbstatus ¤Ï¡¢¥ï¡¼¥«¡¼¤Î¥¯¥ª¡¼¥¿¤òËþ¤¿¤¹¤¿¤á¤Ë + ¤É¤Î¤°¤é¤¤µÞ¤®¤ÇƯ¤«¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤ò»Ø¤·¤Þ¤¹¡£

+ +

¥ï¡¼¥«¡¼¤Ï¥í¡¼¥É¥Ð¥é¥ó¥µ¤Î¥á¥ó¥Ð¤Ç¡¢Ä̾ï¤Ï¡¢ + ¥µ¥Ý¡¼¥È¤µ¤ì¤ë¥×¥í¥È¥³¥ë¤Î¤¦¤Á¤Î°ì¤Ä¤òÄ󶡤·¤Æ¤¤¤ë¥ê¥â¡¼¥È¥Û¥¹¥È¤Ç¤¹¡£ +

+ +

¤Þ¤º¸Ä¡¹¤Î¥ï¡¼¥«¡¼¤Ë¥ï¡¼¥«¡¼¥¯¥ª¡¼¥¿¤ò³ä¤ê¿¶¤ê¡¢¤É¤Î¥ï¡¼¥«¡¼¤¬ºÇ¤âµÞ¤®¤Ç + Ư¤«¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤« (lbstatus ¤¬ºÇÂç¤Î¤â¤Î) ¤òÄ´¤Ù¤Þ¤¹¡£ + ¼¡¤Ë»Å»ö¤ò¤¹¤ë¤è¤¦¤Ë¤³¤Î¥ï¡¼¥«¡¼¤òÁªÂò¤·¡¢ÁªÂò¤·¤¿¥ï¡¼¥«¡¼¤Î lbstatus + ¤òÁ´ÂΤ˳ä¤ê¿¶¤Ã¤¿¤Ö¤ó¤À¤±º¹¤·°ú¤­¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢lbstatus ¤ÎÁíÎÌ¤Ï + ·ë²ÌŪ¤ËÊѲ½¤·¤Þ¤»¤ó(*)¤·¡¢¥ê¥¯¥¨¥¹¥È¤Ï´üÂÔÄ̤ê¤Ëʬ»¶¤µ¤ì¤Þ¤¹¡£

+ +

¤¢¤ë¥ï¡¼¥«¡¼¤¬Ìµ¸ú¤Ë¤Ê¤Ã¤Æ¤â¡¢Â¾¤Î¤â¤Î¤ÏÀµ¾ï¤Ë¥¹¥±¥¸¥å¡¼¥ë¤µ¤ì³¤±¤Þ¤¹¡£ +

+ + 
for each worker in workers
+    worker lbstatus += worker lbfactor
+    total factor    += worker lbfactor
+    if worker lbstatus > candidate lbstatus
+        candidate = worker
+
+candidate lbstatus -= total factor
+ +

¥Ð¥é¥ó¥µ¤ò¼¡¤Î¤è¤¦¤ËÀßÄꤷ¤¿¾ì¹ç:

+ + + + + + + + + + + + + + + + +
workerabcd
lbfactor25252525
lbstatus0000
+ +

¤½¤·¤Æ b ¤¬Ìµ¸ú¤Ë¤Ê¤Ã¤¿¾ì¹ç¡¢¼¡¤Î¤è¤¦¤Ê¥¹¥±¥¸¥å¡¼¥ë¤¬ + ¹Ô¤ï¤ì¤Þ¤¹¡£

+ + + + + + + + + + + + + + + + + + + + + + +
workerabcd
lbstatus-5002525
lbstatus-250-2550
lbstatus0000
(repeat)
+ +

¤Ä¤Þ¤ê¤³¤Î¤è¤¦¤Ë¥¹¥±¥¸¥å¡¼¥ë¤µ¤ì¤Þ¤¹: a c + d a c d a + c d ... ¼¡¤ÎÅÀ¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤:

+ + + + + + + + + + + +
workerabcd
lbfactor25252525
+ +

¤³¤ÎµóÆ°¤Ï¡¢¼¡¤ÎÀßÄê¤ÈÁ´¤¯Æ±¤¸¤Ë¤Ê¤ê¤Þ¤¹:

+ + + + + + + + + + + +
workerabcd
lbfactor1111
+ +

This is because all values of lbfactor are normalized + with respect to the others. For:

+

lbfactor ¤ÏÁ´¤ÆÀµµ¬²½¤µ¤ì¤¿¤â¤Î¤Ç¡¢ + ¾¤È¤ÎÁêÂÐÃͤÀ¤«¤é¤Ç¤¹¡£¼¡¤ÎÀßÄê¤Ç¤Ï:

+ + + + + + + + + +
workerabc
lbfactor141
+ +

¥ï¡¼¥«¡¼ b ¤Ï¡¢Ê¿¶Ñ¤·¤Æ¡¢a ¤È c + ¤Î 4 Çܤοô¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±»ý¤Ä¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¼¡¤Î¤è¤¦¤ÊÈóÂоΤÊÀßÄê¤Ç¤Ï¡¢¤³¤¦¤Ê¤ë¤ÈͽÁÛ¤µ¤ì¤ë¤Ç¤·¤ç¤¦:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
workerab
lbfactor7030
 
lbstatus-3030
lbstatus40-40
lbstatus10-10
lbstatus-2020
lbstatus-5050
lbstatus20-20
lbstatus-1010
lbstatus-4040
lbstatus30-30
lbstatus00
(repeat)
+ +

¥¹¥±¥¸¥å¡¼¥ë¤Ï 10 ¥¹¥±¥¸¥å¡¼¥ë¸å¤Ë·«¤êÊÖ¤µ¤ì¡¢a 7 ²ó¤È + b 3 ²ó¤Ç¤Þ¤Ð¤é¤ËÁª¤Ð¤ì¤Þ¤¹¡£

+
top
+
+

Weighted Traffic Counting ¥¢¥ë¥´¥ê¥º¥à

+ +

lbmethod=bytraffic ¤ÇÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤Î¥¹¥±¥¸¥å¡¼¥é¤ÎÇطʤˤ¢¤ë¹Í¤¨Êý¤Ï¡¢Request Counting + ¤ÈÈó¾ï¤Ë»÷¤Æ¤¤¤Þ¤¹¤¬¡¢¼¡¤Î°ã¤¤¤¬¤¢¤ê¤Þ¤¹:

+ +

lbfactor ¤Ï ¤É¤ì¤À¤±¤Î¥Ð¥¤¥È¿ô¤Î¥È¥é¥Õ¥£¥Ã¥¯Î̤ò¡¢ + ¤³¤Î¥ï¡¼¥«¡¼¤Ë½èÍý¤·¤Æ¤â¤é¤¤¤¿¤¤¤« ¤òɽ¤·¤Þ¤¹¡£ + ¤³¤ÎÃͤâƱÍͤËÀµµ¬²½¤µ¤ì¤¿Ãͤǡ¢¥ï¡¼¥«¡¼Á´ÂΤΤ¦¤Á¤Ç¤Î "ʬô" + Î̤òɽ¸½¤·¤Æ¤¤¤Þ¤¹¡£¥ê¥¯¥¨¥¹¥È¿ô¤òñ½ã¤Ë¿ô¤¨¤ëÂå¤ï¤ê¤Ë¡¢ + ¤É¤ì¤À¤±¤ÎžÁ÷Î̤ò½èÍý¤·¤¿¤«¤ò¿ô¤¨¤Þ¤¹¡£

+ +

¼¡¤Î¤è¤¦¤Ë¥Ð¥é¥ó¥µ¤òÀßÄꤷ¤¿¾ì¹ç:

+ + + + + + + + + +
workerabc
lbfactor121
+ +

b ¤Ë¤Ï a ¤ä c ¤Î 2 ÇÜ + ½èÍý¤·¤Æ¤Û¤·¤¤¤È¤¤¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + b ¤Ï 2 ÇܤΠI/O ¤ò½èÍý¤¹¤ë¤È¤¤¤¦°ÕÌ£¤Ë¤Ê¤ê¡¢ + 2 ÇܤΥꥯ¥¨¥¹¥È¿ô¤ò½èÍý¤¹¤ë¤È¤¤¤¦¤³¤È¤Ë¤Ï¤Ê¤ê¤Þ¤»¤ó¡£ + ¤Ç¤¹¤«¤é¥ê¥¯¥¨¥¹¥È¤È¥ì¥¹¥Ý¥ó¥¹¤Î¥µ¥¤¥º¤¬¡¢ + ½Å¤ßÉÕ¤±¤È¿¶¤êʬ¤±¤Î¥¢¥ë¥´¥ê¥º¥à¤Ë¸ú¤¤¤Æ¤¤¤Þ¤¹¡£

+ +
top
+
+

¥Ð¥é¥ó¥µ¥Þ¥Í¡¼¥¸¥ã¤Î¥µ¥Ý¡¼¥È¤òÍ­¸ú¤Ë¤¹¤ë

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï mod_status ¤Î¥µ¡¼¥Ó¥¹¤ò + ɬÍפȤ·¤Þ¤¹¡£ + ¥Ð¥é¥ó¥µ¥Þ¥Í¡¼¥¸¥ã¤ò»È¤¦¤È¡¢¥Ð¥é¥ó¥µ¤Î¥á¥ó¥Ð¡¼¤ÎưŪ¤Ê¹¹¿·¤¬ + ¤Ç¤­¤Þ¤¹¡£¥Ð¥é¥ó¥µ¥Þ¥Í¡¼¥¸¥ã¤ò»È¤Ã¤Æ¡¢¥Ð¥é¥ó¥¹·¸¿ô (lbfactor) + ¤òÊѹ¹¤·¤¿¤ê¡¢¥á¥ó¥Ð¡¼¤òÊѹ¹¤·¤¿¤ê¡¢ÆÃÄê¤Î¥á¥ó¥Ð¡¼¤ò + ¥ª¥Õ¥é¥¤¥ó¥â¡¼¥É¤Ë¤·¤¿¤ê¤Ç¤­¤Þ¤¹¡£

+ +

¤Ç¤¹¤«¤é¡¢¥í¡¼¥É¥Ð¥é¥ó¥µ´ÉÍýµ¡Ç½¤ò»È¤¤¤¿¤±¤ì¤Ð¡¢ + mod_status ¤È mod_proxy_balancer + ¤ò¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

foo.com ¥É¥á¥¤¥ó¤Î¥Ö¥é¥¦¥¶¤«¤é¥í¡¼¥É¥Ð¥é¥ó¥µ´ÉÍýµ¡Ç½¤ò + »È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ê¥³¡¼¥É¤ò httpd.conf + ¤ËÄɲä·¤Þ¤¹¡£

+

+ <Location /balancer-manager>
+ SetHandler balancer-manager
+
+ Order Deny,Allow
+ Deny from all
+ Allow from .foo.com
+ </Location> +

+ +

¤³¤¦¤¹¤ë¤È¡¢http://your.server.name/balancer-manager + ¤Î¥Ú¡¼¥¸·Ðͳ¤Ç¡¢¥¦¥§¥Ö¥Ö¥é¥¦¥¶¤«¤é¥í¡¼¥É¥Ð¥é¥ó¥µ¥Þ¥Í¡¼¥¸¥ã¤Ë + ¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy_connect.html b/docs/manual/mod/mod_proxy_connect.html new file mode 100644 index 00000000..315f683c --- /dev/null +++ b/docs/manual/mod/mod_proxy_connect.html @@ -0,0 +1,3 @@ +URI: mod_proxy_connect.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_proxy_connect.html.en b/docs/manual/mod/mod_proxy_connect.html.en new file mode 100644 index 00000000..62b077e4 --- /dev/null +++ b/docs/manual/mod/mod_proxy_connect.html.en @@ -0,0 +1,62 @@ + + + +mod_proxy_connect - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_proxy_connect

+
+

Available Languages:  en 

+
+ + + +
Description:mod_proxy extension for +CONNECT request handling
Status:Extension
Module Identifier:proxy_connect_module
Source File:proxy_connect.c
+

Summary

+ +

This module requires the service of mod_proxy. It provides support for the CONNECT + HTTP method. This method is mainly used to tunnel SSL requests + through proxy servers.

+ +

Thus, in order to get the ability of handling CONNECT + requests, mod_proxy and + mod_proxy_connect have to be present in the server.

+ +

Warning

+

Do not enable proxying until you have secured your server. Open proxy + servers are dangerous both to your network and to the Internet at + large.

+
+
+

Directives

+

This module provides no + directives.

+

See also

+
+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy_ftp.html b/docs/manual/mod/mod_proxy_ftp.html new file mode 100644 index 00000000..a0f912a2 --- /dev/null +++ b/docs/manual/mod/mod_proxy_ftp.html @@ -0,0 +1,3 @@ +URI: mod_proxy_ftp.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_proxy_ftp.html.en b/docs/manual/mod/mod_proxy_ftp.html.en new file mode 100644 index 00000000..a5488a01 --- /dev/null +++ b/docs/manual/mod/mod_proxy_ftp.html.en @@ -0,0 +1,163 @@ + + + +mod_proxy_ftp - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_proxy_ftp

+
+

Available Languages:  en 

+
+ + + +
Description:FTP support module for +mod_proxy
Status:Extension
Module Identifier:proxy_ftp_module
Source File:proxy_ftp.c
+

Summary

+ +

This module requires the service of mod_proxy. It provides support for the proxying + FTP sites. Note that FTP support is currently limited to + the GET method.

+ +

Thus, in order to get the ability of handling FTP proxy requests, + mod_proxy and mod_proxy_ftp + have to be present in the server.

+ +

Warning

+

Do not enable proxying until you have secured your server. Open proxy + servers are dangerous both to your network and to the Internet at + large.

+
+
+ +
top
+
+

Why doesn't file type xxx + download via FTP?

+

You probably don't have that particular file type defined as + application/octet-stream in your proxy's mime.types + configuration file. A useful line can be

+ + 
application/octet-stream   bin dms lha lzh exe class tgz taz
+

Alternatively you may prefer to default everything to binary:

+ 
DefaultType application/octet-stream
+
top
+
+

How can I force an FTP ASCII download of + File xxx?

+

In the rare situation where you must download a specific file using the + FTP ASCII transfer method (while the default transfer is in + binary mode), you can override mod_proxy's + default by suffixing the request with ;type=a to force an + ASCII transfer. (FTP Directory listings are always executed in ASCII mode, + however.)

+
top
+
+

How can I do FTP upload?

+

Currently, only GET is supported for FTP in mod_proxy. You can + of course use HTTP upload (POST or PUT) through an Apache proxy.

+
top
+
+

How can I access FTP files outside + of my home directory?

+

An FTP URI is interpreted relative to the home directory of the user + who is logging in. Alas, to reach higher directory levels you cannot + use /../, as the dots are interpreted by the browser and not actually + sent to the FTP server. To address this problem, the so called Squid + %2f hack was implemented in the Apache FTP proxy; it is a + solution which is also used by other popular proxy servers like the Squid Proxy Cache. By + prepending /%2f to the path of your request, you can make + such a proxy change the FTP starting directory to / (instead + of the home directory). For example, to retrieve the file + /etc/motd, you would use the URL:

+ +

+ ftp://user@host/%2f/etc/motd +

+
top
+
+

How can I hide the FTP cleartext password + in my browser's URL line?

+

To log in to an FTP server by username and password, Apache uses + different strategies. In absense of a user name and password in the URL + altogether, Apache sends an anonymous login to the FTP server, + i.e.,

+ +

+ user: anonymous
+ password: apache_proxy@ +

+ +

This works for all popular FTP servers which are configured for + anonymous access.

+ +

For a personal login with a specific username, you can embed the user + name into the URL, like in:

+ +

+ ftp://username@host/myfile +

+ +

If the FTP server asks for a password when given this username (which + it should), then Apache will reply with a 401 (Authorization + required) response, which causes the Browser to pop up the + username/password dialog. Upon entering the password, the connection + attempt is retried, and if successful, the requested resource is + presented. The advantage of this procedure is that your browser does not + display the password in cleartext (which it would if you had used

+ +

+ ftp://username:password@host/myfile +

+ +

in the first place).

+ +

Note

+

The password which is transmitted in such a way is not encrypted on + its way. It travels between your browser and the Apache proxy server in + a base64-encoded cleartext string, and between the Apache proxy and the + FTP server as plaintext. You should therefore think twice before + accessing your FTP server via HTTP (or before accessing your personal + files via FTP at all!) When using unsecure channels, an eavesdropper + might intercept your password on its way.

+
+
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_proxy_http.html b/docs/manual/mod/mod_proxy_http.html new file mode 100644 index 00000000..5be29102 --- /dev/null +++ b/docs/manual/mod/mod_proxy_http.html @@ -0,0 +1,3 @@ +URI: mod_proxy_http.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_proxy_http.html.en b/docs/manual/mod/mod_proxy_http.html.en new file mode 100644 index 00000000..f0b68e10 --- /dev/null +++ b/docs/manual/mod/mod_proxy_http.html.en @@ -0,0 +1,65 @@ + + + +mod_proxy_http - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_proxy_http

+
+

Available Languages:  en 

+
+ + + +
Description:HTTP support module for +mod_proxy
Status:Extension
Module Identifier:proxy_http_module
Source File:proxy_http.c
+

Summary

+ +

This module requires the service of mod_proxy. It provides the features used for + proxying HTTP requests. mod_proxy_http + supports HTTP/0.9, HTTP/1.0 and HTTP/1.1. It does not + provide any caching abilities. If you want to set up a caching + proxy, you might want to use the additional service of the + mod_cache module.

+ +

Thus, in order to get the ability of handling HTTP proxy requests, + mod_proxy and mod_proxy_http + have to be present in the server.

+ +

Warning

+

Do not enable proxying until you have secured your server. Open proxy + servers are dangerous both to your network and to the Internet at + large.

+
+
+

Directives

+

This module provides no + directives.

+

See also

+
+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_rewrite.html b/docs/manual/mod/mod_rewrite.html new file mode 100644 index 00000000..5b651b93 --- /dev/null +++ b/docs/manual/mod/mod_rewrite.html @@ -0,0 +1,3 @@ +URI: mod_rewrite.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_rewrite.html.en b/docs/manual/mod/mod_rewrite.html.en new file mode 100644 index 00000000..47f9c7e9 --- /dev/null +++ b/docs/manual/mod/mod_rewrite.html.en @@ -0,0 +1,1564 @@ + + + +mod_rewrite - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_rewrite

+
+

Available Languages:  en 

+
+ + + + +
Description:Provides a rule-based rewriting engine to rewrite requested +URLs on the fly
Status:Extension
Module Identifier:rewrite_module
Source File:mod_rewrite.c
Compatibility:Available in Apache 1.3 and later
+

Summary

+ +

This module uses a rule-based rewriting engine (based on a + regular-expression parser) to rewrite requested URLs on the + fly. It supports an unlimited number of rules and an + unlimited number of attached rule conditions for each rule, to + provide a really flexible and powerful URL manipulation + mechanism. The URL manipulations can depend on various tests, + of server variables, environment variables, HTTP + headers, or time stamps. Even external database lookups in + various formats can be used to achieve highly granular URL + matching.

+ +

This module operates on the full URLs (including the + path-info part) both in per-server context + (httpd.conf) and per-directory context + (.htaccess) and can generate query-string + parts on result. The rewritten result can lead to internal + sub-processing, external request redirection or even to an + internal proxy throughput.

+ +

Further details, discussion, and examples, are provided in the + detailed mod_rewrite documentation.

+
+ +
top
+
+

Quoting Special Characters

+ +

As of Apache 1.3.20, special characters in + TestString and Substitution strings can be + escaped (that is, treated as normal characters without their + usual special meaning) by prefixing them with a slash ('\') + character. In other words, you can include an actual + dollar-sign character in a Substitution string by + using '\$'; this keeps mod_rewrite from trying + to treat it as a backreference.

+
top
+
+

Environment Variables

+ +

This module keeps track of two additional (non-standard) + CGI/SSI environment variables named SCRIPT_URL + and SCRIPT_URI. These contain the + logical Web-view to the current resource, while the + standard CGI/SSI variables SCRIPT_NAME and + SCRIPT_FILENAME contain the physical + System-view.

+ +

Notice: These variables hold the URI/URL as they were + initially requested, that is, before any + rewriting. This is important to note because the rewriting process is + primarily used to rewrite logical URLs to physical + pathnames.

+ +

Example

+SCRIPT_NAME=/sw/lib/w3s/tree/global/u/rse/.www/index.html
+SCRIPT_FILENAME=/u/rse/.www/index.html
+SCRIPT_URL=/u/rse/
+SCRIPT_URI=http://en1.engelschall.com/u/rse/
+
+ +
top
+
+

Practical Solutions

+ +

For numerous examples of common, and not-so-common, uses for + mod_rewrite, see the Rewrite + Guide, and the Advanced Rewrite + Guide documents.

+ +
+
top
+

RewriteBase Directive

+ + + + + + + + +
Description:Sets the base URL for per-directory rewrites
Syntax:RewriteBase URL-path
Default:See usage for information.
Context:directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_rewrite
+

The RewriteBase directive explicitly + sets the base URL for per-directory rewrites. As you will see + below, RewriteRule + can be used in per-directory config files + (.htaccess). In such a case, it will act locally, + stripping the local directory prefix before processing, and applying + rewrite rules only to the remainder. When processing is complete, the + prefix is automatically added back to the + path. The default setting is; RewriteBase physical-directory-path

+ +

When a substitution occurs for a new URL, this module has + to re-inject the URL into the server processing. To be able + to do this it needs to know what the corresponding URL-prefix + or URL-base is. By default this prefix is the corresponding + filepath itself. However, for most websites, URLs are NOT + directly related to physical filename paths, so this + assumption will often be wrong! Therefore, you can + use the RewriteBase directive to specify the + correct URL-prefix.

+ +
If your webserver's URLs are not directly +related to physical file paths, you will need to use +RewriteBase in every .htaccess +file where you want to use RewriteRule directives. +
+ +

For example, assume the following per-directory config file:

+ +
+#
+#  /abc/def/.htaccess -- per-dir config file for directory /abc/def
+#  Remember: /abc/def is the physical path of /xyz, i.e., the server
+#            has a 'Alias /xyz /abc/def' directive e.g.
+#
+
+RewriteEngine On
+
+#  let the server know that we were reached via /xyz and not
+#  via the physical path prefix /abc/def
+RewriteBase   /xyz
+
+#  now the rewriting rules
+RewriteRule   ^oldstuff\.html$  newstuff.html
+
+ +

In the above example, a request to + /xyz/oldstuff.html gets correctly rewritten to + the physical file /abc/def/newstuff.html.

+ +

For Apache Hackers

+

The following list gives detailed information about + the internal processing steps:

+
+Request:
+  /xyz/oldstuff.html
+
+Internal Processing:
+  /xyz/oldstuff.html     -> /abc/def/oldstuff.html  (per-server Alias)
+  /abc/def/oldstuff.html -> /abc/def/newstuff.html  (per-dir    RewriteRule)
+  /abc/def/newstuff.html -> /xyz/newstuff.html      (per-dir    RewriteBase)
+  /xyz/newstuff.html     -> /abc/def/newstuff.html  (per-server Alias)
+
+Result:
+  /abc/def/newstuff.html
+
+

This seems very complicated, but is in fact + correct Apache internal processing. Because the + per-directory rewriting comes late in the + process, the rewritten request + has to be re-injected into the Apache kernel. + This is not the serious overhead it may seem to be - + this re-injection is completely internal to the + Apache server (and the same procedure is used by + many other operations within Apache).

+
+ + +
+
top
+

RewriteCond Directive

+ + + + + + + +
Description:Defines a condition under which rewriting will take place +
Syntax: RewriteCond + TestString CondPattern
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_rewrite
+

The RewriteCond directive defines a + rule condition. One or more RewriteCond + can precede a RewriteRule + directive. The following rule is then only used if both + the current state of the URI matches its pattern, and if these conditions are met.

+ +

TestString is a string which can contain the + following expanded constructs in addition to plain text:

+ +
    +
  • + RewriteRule backreferences: These are + backreferences of the form $N + (0 <= N <= 9), which provide access to the grouped + parts (in parentheses) of the pattern, from the + RewriteRule which is subject to the current + set of RewriteCond conditions.. +
    • +
  • + RewriteCond backreferences: These are + backreferences of the form %N + (1 <= N <= 9), which provide access to the grouped + parts (again, in parentheses) of the pattern, from the last matched + RewriteCond in the current set + of conditions. +
    • +
  • + RewriteMap expansions: These are + expansions of the form ${mapname:key|default}. + See the documentation for + RewriteMap for more details. +
    • +
  • + Server-Variables: These are variables of + the form + %{ NAME_OF_VARIABLE + } + where NAME_OF_VARIABLE can be a string taken + from the following list: + + + + + + + + + + + + + + + + + + + + + + + + +
    HTTP headers: connection & request: +
    + HTTP_USER_AGENT
    + HTTP_REFERER
    + HTTP_COOKIE
    + HTTP_FORWARDED
    + HTTP_HOST
    + HTTP_PROXY_CONNECTION
    + HTTP_ACCEPT
    +     		+ REMOTE_ADDR
    + REMOTE_HOST
    + REMOTE_PORT
    + REMOTE_USER
    + REMOTE_IDENT
    + REQUEST_METHOD
    + SCRIPT_FILENAME
    + PATH_INFO
    + QUERY_STRING
    + AUTH_TYPE
    +     		+
    server internals: date and time: specials:
    + DOCUMENT_ROOT
    + SERVER_ADMIN
    + SERVER_NAME
    + SERVER_ADDR
    + SERVER_PORT
    + SERVER_PROTOCOL
    + SERVER_SOFTWARE
    +     		+ TIME_YEAR
    + TIME_MON
    + TIME_DAY
    + TIME_HOUR
    + TIME_MIN
    + TIME_SEC
    + TIME_WDAY
    + TIME
    +     		+ API_VERSION
    + THE_REQUEST
    + REQUEST_URI
    + REQUEST_FILENAME
    + IS_SUBREQ
    + HTTPS
    +
    + +

    These variables all + correspond to the similarly named HTTP + MIME-headers, C variables of the Apache server or + struct tm fields of the Unix system. + Most are documented elsewhere in the Manual or in + the CGI specification. Those that are special to + mod_rewrite include those below.

    +
    +
    +
    IS_SUBREQ
    + +
    Will contain the text "true" if the request + currently being processed is a sub-request, + "false" otherwise. Sub-requests may be generated + by modules that need to resolve additional files + or URIs in order to complete their tasks.
    + +
    API_VERSION
    + +
    This is the version of the Apache module API + (the internal interface between server and + module) in the current httpd build, as defined in + include/ap_mmn.h. The module API version + corresponds to the version of Apache in use (in + the release version of Apache 1.3.14, for + instance, it is 19990320:10), but is mainly of + interest to module authors.
    + +
    THE_REQUEST
    + +
    The full HTTP request line sent by the + browser to the server (e.g., "GET + /index.html HTTP/1.1"). This does not + include any additional headers sent by the + browser.
    + +
    REQUEST_URI
    + +
    The resource requested in the HTTP request + line. (In the example above, this would be + "/index.html".)
    + +
    REQUEST_FILENAME
    + +
    The full local filesystem path to the file or + script matching the request.
    + +
    HTTPS
    + +
    Will contain the text "on" if the connection is + using SSL/TLS, or "off" otherwise. (This variable + can be safely used regardless of whether or not + mod_ssl is loaded).
    + +
    +
    +
    • +
+ +

Other things you should be aware of:

+ +
    +
  1. The variables SCRIPT_FILENAME and REQUEST_FILENAME + contain the same value - the value of the + filename field of the internal + request_rec structure of the Apache server. + The first name is the commonly known CGI variable name + while the second is the appropriate counterpart of + REQUEST_URI (which contains the value of the + uri field of request_rec).
    2. + +
  2. + %{ENV:variable}, where variable can be + any environment variable, is also available. + This is looked-up via internal + Apache structures and (if not found there) via + getenv() from the Apache server process.
    3. + +
  3. + %{SSL:variable}, where variable is the + name of an SSL environment + variable, can be used whether or not + mod_ssl is loaded, but will always expand to + the empty string if it is not. Example: + %{SSL:SSL_CIPHER_USEKEYSIZE} may expand to + 128.
    4. + +
  4. + %{HTTP:header}, where header can be + any HTTP MIME-header name, can always be used to obtain the + value of a header sent in the HTTP request. + Example: %{HTTP:Proxy-Connection} is + the value of the HTTP header + ``Proxy-Connection:''.
    5. + +
  5. + %{LA-U:variable} can be used for look-aheads which perform + an internal (URL-based) sub-request to determine the final + value of variable. This can be used to access + variable for rewriting which is not available at the current + stage, but will be set in a later phase. +

    For instance, to rewrite according to the + REMOTE_USER variable from within the + per-server context (httpd.conf file) you must + use %{LA-U:REMOTE_USER} - this + variable is set by the authorization phases, which come + after the URL translation phase (during which mod_rewrite + operates).

    +

    On the other hand, because mod_rewrite implements + its per-directory context (.htaccess file) via + the Fixup phase of the API and because the authorization + phases come before this phase, you just can use + %{REMOTE_USER} in that context.

    6. + +
  6. + %{LA-F:variable} can be used to perform an internal + (filename-based) sub-request, to determine the final value + of variable. Most of the time, this is the same as + LA-U above.
    7. +
+ +

CondPattern is the condition pattern, + a regular expression which is applied to the + current instance of the TestString. + TestString is first evaluated, before being matched against + CondPattern.

+ +

Remember: CondPattern is a + perl compatible regular expression with some + additions:

+ +
    +
  1. You can prefix the pattern string with a + '!' character (exclamation mark) to specify a + non-matching pattern.
    2. + +
  2. + There are some special variants of CondPatterns. + Instead of real regular expression strings you can also + use one of the following: + +
      +
    • '<CondPattern' (lexicographically + precedes)
      + Treats the CondPattern as a plain string and + compares it lexicographically to TestString. True if + TestString lexicographically precedes + CondPattern.
      • + +
    • '>CondPattern' (lexicographically + follows)
      + Treats the CondPattern as a plain string and + compares it lexicographically to TestString. True if + TestString lexicographically follows + CondPattern.
      • + +
    • '=CondPattern' (lexicographically + equal)
      + Treats the CondPattern as a plain string and + compares it lexicographically to TestString. True if + TestString is lexicographically equal to + CondPattern (the two strings are exactly + equal, character for character). If CondPattern + is "" (two quotation marks) this + compares TestString to the empty string.
      • + +
    • '-d' (is + directory)
      + Treats the TestString as a pathname and tests + whether or not it exists, and is a directory.
      • + +
    • '-f' (is regular + file)
      + Treats the TestString as a pathname and tests + whether or not it exists, and is a regular file.
      • + +
    • '-s' (is regular file, with + size)
      + Treats the TestString as a pathname and tests + whether or not it exists, and is a regular file with size greater + than zero.
      • + +
    • '-l' (is symbolic + link)
      + Treats the TestString as a pathname and tests + whether or not it exists, and is a symbolic link.
      • + +
    • '-x' (has executable + permissions)
      + Treats the TestString as a pathname and tests + whether or not it exists, and has executable permissions. + These permissions are determined according to + the underlying OS.
      • + +
    • '-F' (is existing file, via + subrequest)
      + Checks whether or not TestString is a valid file, + accessible via all the server's currently-configured + access controls for that path. This uses an internal + subrequest to do the check, so use it with care - + it can impact your server's performance!
      • + +
    • '-U' (is existing URL, via + subrequest)
      + Checks whether or not TestString is a valid URL, + accessible via all the server's currently-configured + access controls for that path. This uses an internal + subrequest to do the check, so use it with care - + it can impact your server's performance!
      • +
    + +

    Note:

    + All of these tests can + also be prefixed by an exclamation mark ('!') to + negate their meaning. +
    +
    3. + +
  3. You can also set special flags for + CondPattern by appending + [flags] + as the third argument to the RewriteCond + directive, where flags is a comma-separated list of any of the + following flags: + +
      +
    • 'nocase|NC' + (no case)
      + This makes the test case-insensitive - differences + between 'A-Z' and 'a-z' are ignored, both in the + expanded TestString and the CondPattern. + This flag is effective only for comparisons between + TestString and CondPattern. It has no + effect on filesystem and subrequest checks.
      • + +
    • + 'ornext|OR' + (or next condition)
      + Use this to combine rule conditions with a local OR + instead of the implicit AND. Typical example: + +
      +RewriteCond %{REMOTE_HOST}  ^host1.*  [OR]
+RewriteCond %{REMOTE_HOST}  ^host2.*  [OR]
+RewriteCond %{REMOTE_HOST}  ^host3.*
+RewriteRule ...some special stuff for any of these hosts...
+
      + + Without this flag you would have to write the condition/rule + pair three times. +
      • +
    +
    4. +
+ +

Example:

+ +

To rewrite the Homepage of a site according to the + ``User-Agent:'' header of the request, you can + use the following:

+ +
+RewriteCond  %{HTTP_USER_AGENT}  ^Mozilla.*
+RewriteRule  ^/$                 /homepage.max.html  [L]
+
+RewriteCond  %{HTTP_USER_AGENT}  ^Lynx.*
+RewriteRule  ^/$                 /homepage.min.html  [L]
+
+RewriteRule  ^/$                 /homepage.std.html  [L]
+
+ +

Explanation: If you use a browser which identifies itself + as 'Mozilla' (including Netscape Navigator, Mozilla etc), then you + get the max homepage (which could include frames, or other special + features). + If you use the Lynx browser (which is terminal-based), then + you get the min homepage (which could be a version designed for + easy, text-only browsing). + If neither of these conditions apply (you use any other browser, + or your browser identifies itself as something non-standard), you get + the std (standard) homepage.

+ + +
+
top
+

RewriteEngine Directive

+ + + + + + + + +
Description:Enables or disables runtime rewriting engine
Syntax:RewriteEngine on|off
Default:RewriteEngine off
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_rewrite
+ +

The RewriteEngine directive enables or + disables the runtime rewriting engine. If it is set to + off this module does no runtime processing at + all. It does not even update the SCRIPT_URx + environment variables.

+ +

Use this directive to disable the module instead of + commenting out all the RewriteRule directives!

+ +

Note that, by default, rewrite configurations are not + inherited. This means that you need to have a + RewriteEngine on directive for each virtual host + in which you wish to use it.

+ +
+
top
+

RewriteLock Directive

+ + + + + + +
Description:Sets the name of the lock file used for RewriteMap +synchronization
Syntax:RewriteLock file-path
Context:server config
Status:Extension
Module:mod_rewrite
+

This directive sets the filename for a synchronization + lockfile which mod_rewrite needs to communicate with RewriteMap + programs. Set this lockfile to a local path (not on a + NFS-mounted device) when you want to use a rewriting + map-program. It is not required for other types of rewriting + maps.

+ +
+
top
+

RewriteLog Directive

+ + + + + + +
Description:Sets the name of the file used for logging rewrite engine +processing
Syntax:RewriteLog file-path
Context:server config, virtual host
Status:Extension
Module:mod_rewrite
+

The RewriteLog directive sets the name + of the file to which the server logs any rewriting actions it + performs. If the name does not begin with a slash + ('/') then it is assumed to be relative to the + Server Root. The directive should occur only once per + server config.

+ +
To disable the logging of + rewriting actions it is not recommended to set + Filename to /dev/null, because + although the rewriting engine does not then output to a + logfile it still creates the logfile output internally. + This will slow down the server with no advantage + to the administrator! To disable logging either + remove or comment out the RewriteLog + directive or use RewriteLogLevel 0! +
+ +

Security

+ +See the Apache Security Tips +document for details on how your security could be compromised if the +directory where logfiles are stored is writable by anyone other than +the user that starts the server. +
+ +

Example

+RewriteLog "/usr/local/var/apache/logs/rewrite.log" +

+ + +
+
top
+

RewriteLogLevel Directive

+ + + + + + + +
Description:Sets the verbosity of the log file used by the rewrite +engine
Syntax:RewriteLogLevel Level
Default:RewriteLogLevel 0
Context:server config, virtual host
Status:Extension
Module:mod_rewrite
+

The RewriteLogLevel directive sets the + verbosity level of the rewriting logfile. The default level 0 + means no logging, while 9 or more means that practically all + actions are logged.

+ +

To disable the logging of rewriting actions simply set + Level to 0. This disables all rewrite action + logs.

+ +
Using a high value for + Level will slow down your Apache server + dramatically! Use the rewriting logfile at a + Level greater than 2 only for debugging! +
+ +

Example

+RewriteLogLevel 3 +

+ + +
+
top
+

RewriteMap Directive

+ + + + + + + +
Description:Defines a mapping function for key-lookup
Syntax:RewriteMap MapName MapType:MapSource +
Context:server config, virtual host
Status:Extension
Module:mod_rewrite
Compatibility:The choice of different dbm types is available in +Apache 2.0.41 and later
+

The RewriteMap directive defines a + Rewriting Map which can be used inside rule + substitution strings by the mapping-functions to + insert/substitute fields through a key lookup. The source of + this lookup can be of various types.

+ +

The MapName is + the name of the map and will be used to specify a + mapping-function for the substitution strings of a rewriting + rule via one of the following constructs:

+ +

+ ${ MapName : + LookupKey }
+ ${ MapName : + LookupKey | DefaultValue + } +

+ +

When such a construct occurs, the map MapName is + consulted and the key LookupKey is looked-up. If the + key is found, the map-function construct is substituted by + SubstValue. If the key is not found then it is + substituted by DefaultValue or by the empty string + if no DefaultValue was specified.

+ +

For example, you might define a + RewriteMap as:

+ +

+ RewriteMap examplemap txt:/path/to/file/map.txt +

+ +

You would then be able to use this map in a + RewriteRule as follows:

+ +

+ RewriteRule ^/ex/(.*) ${examplemap:$1} +

+ +

The following combinations for MapType and + MapSource can be used:

+ +
    +
  • + Standard Plain Text
    + MapType: txt, MapSource: Unix filesystem + path to valid regular file + +

    This is the standard rewriting map feature where the + MapSource is a plain ASCII file containing + either blank lines, comment lines (starting with a '#' + character) or pairs like the following - one per + line.

    + +

    + MatchingKey + SubstValue +

    + +

    Example

    +##
+##  map.txt -- rewriting map
+##
+
+Ralf.S.Engelschall    rse   # Bastard Operator From Hell
+Mr.Joe.Average        joe   # Mr. Average
+
    + +

    +RewriteMap real-to-user txt:/path/to/file/map.txt +

    +
    • + +
  • + Randomized Plain Text
    + MapType: rnd, MapSource: Unix filesystem + path to valid regular file + +

    This is identical to the Standard Plain Text variant + above but with a special post-processing feature: After + looking up a value it is parsed according to contained + ``|'' characters which have the meaning of + ``or''. In other words they indicate a set of + alternatives from which the actual returned value is + chosen randomly. For example, you might use the following map + file and directives to provide a random load balancing between + several back-end server, via a reverse-proxy. Images are sent + to one of the servers in the 'static' pool, while everything + else is sent to one of the 'dynamic' pool.

    +

    Example:

    + +

    Rewrite map file

    +##
+##  map.txt -- rewriting map
+##
+
+static   www1|www2|www3|www4
+dynamic  www5|www6
+
    + +

    Configuration directives

    +RewriteMap servers rnd:/path/to/file/map.txt
    +
    +RewriteRule ^/(.*\.(png|gif|jpg)) http://${servers:static}/$1 +[NC,P,L]
    +RewriteRule ^/(.*) http://${servers:dynamic}/$1 [P,L] +

    +
    • + +
  • + Hash File
    MapType: + dbm[=type], MapSource: Unix filesystem + path to valid regular file + +

    Here the source is a binary format DBM file containing + the same contents as a Plain Text format file, but + in a special representation which is optimized for really + fast lookups. The type can be sdbm, gdbm, ndbm, or + db depending on compile-time + settings. If the type is omitted, the + compile-time default will be chosen. You can create such a + file with any DBM tool or with the following Perl + script. Be sure to adjust it to create the appropriate + type of DBM. The example creates an NDBM file.

    + +
    +#!/path/to/bin/perl
+##
+##  txt2dbm -- convert txt map to dbm format
+##
+
+use NDBM_File;
+use Fcntl;
+
+($txtmap, $dbmmap) = @ARGV;
+
+open(TXT, "<$txtmap") or die "Couldn't open $txtmap!\n";
+tie (%DB, 'NDBM_File', $dbmmap,O_RDWR|O_TRUNC|O_CREAT, 0644)
+  or die "Couldn't create $dbmmap!\n";
+
+while (<TXT>) {
+  next if (/^\s*#/ or /^\s*$/);
+  $DB{$1} = $2 if (/^\s*(\S+)\s+(\S+)/);
+}
+
+untie %DB;
+close(TXT);
+
    + +

    +$ txt2dbm map.txt map.db +

    +
    • + +
  • + Internal Function
    + MapType: int, MapSource: Internal Apache + function + +

    Here, the source is an internal Apache function. + Currently you cannot create your own, but the following + functions already exist:

    + +
      +
    • toupper:
      + Converts the key to all upper case.
      • + +
    • tolower:
      + Converts the key to all lower case.
      • + +
    • escape:
      + Translates special characters in the key to + hex-encodings.
      • + +
    • unescape:
      + Translates hex-encodings in the key back to + special characters.
      • +
    +
    • + +
  • + External Rewriting Program
    + MapType: prg, MapSource: Unix filesystem + path to valid regular file + +

    Here the source is a program, not a map file. To + create it you can use a language of your choice, but + the result has to be an executable program (either + object-code or a script with the magic cookie trick + '#!/path/to/interpreter' as the first + line).

    + +

    This program is started once, when the Apache server + is started, and then communicates with the rewriting engine + via its stdin and stdout + file-handles. For each map-function lookup it will + receive the key to lookup as a newline-terminated string + on stdin. It then has to give back the + looked-up value as a newline-terminated string on + stdout or the four-character string + ``NULL'' if it fails (i.e., there + is no corresponding value for the given key). A trivial + program which will implement a 1:1 map (i.e., + key == value) could be:

    + +
    +#!/usr/bin/perl
+$| = 1;
+while (<STDIN>) {
+    # ...put here any transformations or lookups...
+    print $_;
+}
+
    + +

    But be very careful:

    + +
      +
    1. ``Keep it simple, stupid'' (KISS). + If this program hangs, it will cause Apache to hang + when trying to use the relevant rewrite rule.
      2. + +
    2. A common mistake is to use buffered I/O on + stdout. Avoid this, as it will cause a deadloop! + ``$|=1'' is used above, to prevent this.
      3. + +
    3. The RewriteLock directive can + be used to define a lockfile which mod_rewrite can use to synchronize + communication with the mapping program. By default no such + synchronization takes place.
      4. +
    +
    • +
+

The RewriteMap directive can occur more than + once. For each mapping-function use one + RewriteMap directive to declare its rewriting + mapfile. While you cannot declare a map in + per-directory context it is of course possible to + use this map in per-directory context.

+ +

Note

For plain text and DBM format files the +looked-up keys are cached in-core until the mtime of the +mapfile changes or the server does a restart. This way you can have +map-functions in rules which are used for every +request. This is no problem, because the external lookup only happens +once! +
+ + +
+
top
+

RewriteOptions Directive

+ + + + + + + + +
Description:Sets some special options for the rewrite engine
Syntax:RewriteOptions Options
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_rewrite
Compatibility:MaxRedirects is no longer available in version 2.1 and +later
+ +

The RewriteOptions directive sets some + special options for the current per-server or per-directory + configuration. The Option string can currently + only be one of the following:

+ +
+
inherit
+
This forces the current configuration to inherit the + configuration of the parent. In per-virtual-server context, + this means that the maps, conditions and rules of the main + server are inherited. In per-directory context this means + that conditions and rules of the parent directory's + .htaccess configuration are inherited.
+
+ +
+
top
+

RewriteRule Directive

+ + + + + + + + +
Description:Defines rules for the rewriting engine
Syntax:RewriteRule + Pattern Substitution
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_rewrite
Compatibility:The cookie-flag is available in Apache 2.0.40 and later.
+

The RewriteRule directive is the real + rewriting workhorse. The directive can occur more than once, + with each instance defining a single rewrite rule. The + order in which these rules are defined is important - this is the order + in which they will be applied at run-time.

+ +

Pattern is + a perl compatible regular + expression, which is applied to the current URL. + ``Current'' means the value of the URL when this rule is + applied. This may not be the originally requested URL, + which may already have matched a previous rule, and have been + altered.

+ +

Some hints on the syntax of regular + expressions:

+ +
+Text:
+  .           Any single character
+  [chars]     Character class: Any character of the class ``chars''
+  [^chars]    Character class: Not a character of the class ``chars''
+  text1|text2 Alternative: text1 or text2
+
+Quantifiers:
+  ?           0 or 1 occurrences of the preceding text
+  *           0 or N occurrences of the preceding text (N > 0)
+  +           1 or N occurrences of the preceding text (N > 1)
+
+Grouping:
+  (text)      Grouping of text
+              (used either to set the borders of an alternative as above, or
+              to make backreferences, where the Nth group can 
+              be referred to on the RHS of a RewriteRule as $N)
+
+Anchors:
+  ^           Start-of-line anchor
+  $           End-of-line anchor
+
+Escaping:
+  \char       escape the given char
+              (for instance, to specify the chars ".[]()" etc.)
+
+ +

For more information about regular expressions, have a look at the + perl regular expression manpage ("perldoc + perlre"). If you are interested in more detailed + information about regular expressions and their variants + (POSIX regex etc.) the following book is dedicated to this topic:

+ +

+ Mastering Regular Expressions, 2nd Edition
+ Jeffrey E.F. Friedl
+ O'Reilly & Associates, Inc. 2002
+ ISBN 0-596-00289-0
+

+ +

In mod_rewrite, the NOT character + ('!') is also available as a possible pattern + prefix. This enables you to negate a pattern; to say, for instance: + ``if the current URL does NOT match this + pattern''. This can be used for exceptional cases, where + it is easier to match the negative pattern, or as a last + default rule.

+ +

Note

+When using the NOT character to negate a pattern, you cannot include +grouped wildcard parts in that pattern. This is because, when the +pattern does NOT match (ie, the negation matches), there are no +contents for the groups. Thus, if negated patterns are used, you +cannot use $N in the substitution string! +
+ +

The substitution of a + rewrite rule is the string which is substituted for (or + replaces) the original URL which Pattern + matched. In addition to plain text, it can include

+ +
    +
  1. back-references ($N) to the RewriteRule + pattern
    2. + +
  2. back-references (%N) to the last matched + RewriteCond pattern
    3. + +
  3. server-variables as in rule condition test-strings + (%{VARNAME})
    4. + +
  4. mapping-function calls + (${mapname:key|default})
    5. +
+

Back-references are identifiers of the form + $N + (N=0..9), which will be replaced + by the contents of the Nth group of the + matched Pattern. The server-variables are the same + as for the TestString of a RewriteCond + directive. The mapping-functions come from the + RewriteMap directive and are explained there. + These three types of variables are expanded in the order above.

+ +

As already mentioned, all rewrite rules are + applied to the Substitution (in the order in which + they are defined + in the config file). The URL is completely + replaced by the Substitution and the + rewriting process continues until all rules have been applied, + or it is explicitly terminated by a + L flag.

+ +

There is a special substitution string named + '-' which means: NO + substitution! This is useful in providing + rewriting rules which only match + URLs but do not substitute anything for them. It is commonly used + in conjunction with the C (chain) flag, in order + to apply more than one pattern before substitution occurs.

+ + +

Additionally you can set special flags for Substitution by + appending [flags] + as the third argument to the RewriteRule + directive. Flags is a comma-separated list of any of the + following flags:

+ +
    +
  • 'chain|C' + (chained with next rule)
    + This flag chains the current rule with the next rule + (which itself can be chained with the following rule, + and so on). This has the following effect: if a rule + matches, then processing continues as usual - + the flag has no effect. If the rule does + not match, then all following chained + rules are skipped. For instance, it can be used to remove the + ``.www'' part, inside a per-directory rule set, + when you let an external redirect happen (where the + ``.www'' part should not occur!).
    • + +
  • + 'cookie|CO=NAME:VAL:domain[:lifetime[:path]]' + (set cookie)
    + This sets a cookie in the client's browser. The cookie's name + is specified by NAME and the value is + VAL. The domain field is the domain of the + cookie, such as '.apache.org', the optional lifetime + is the lifetime of the cookie in minutes, and the optional + path is the path of the cookie
    • + +
  • + 'env|E=VAR:VAL' + (set environment variable)
    + This forces an environment variable named VAR to + be set to the value VAL, where VAL can + contain regexp backreferences ($N and + %N) which will be expanded. You can use this + flag more than once, to set more than one variable. The + variables can later be dereferenced in many situations, most commonly + from within XSSI (via <!--#echo + var="VAR"-->) or CGI ($ENV{'VAR'}). + You can also dereference the variable in a later RewriteCond pattern, using + %{ENV:VAR}. Use this to strip + information from URLs, while maintaining a record of that information.
    • + +
  • 'forbidden|F' (force URL + to be forbidden)
    + This forces the current URL to be forbidden - it immediately + sends back a HTTP response of 403 (FORBIDDEN). + Use this flag in conjunction with + appropriate RewriteConds to conditionally block some + URLs.
    • + +
  • 'gone|G' (force URL to be + gone)
    + This forces the current URL to be gone - it + immediately sends back a HTTP response of 410 (GONE). Use + this flag to mark pages which no longer exist as gone.
    • + +
  • + 'handler|H=Content-handler' + (force Content handler)
    + Force the Content-handler of the target file to be + Content-handler. For instance, this can be used to + simulate the mod_alias directive + ScriptAlias, + which internally forces all files + inside the mapped directory to have a handler of + ``cgi-script''.
    • + +
  • 'last|L' + (last rule)
    + Stop the rewriting process here and don't apply any more + rewrite rules. This corresponds to the Perl + last command or the break command + in C. Use this flag to prevent the currently + rewritten URL from being rewritten further by following + rules. For example, use it to rewrite the root-path URL + ('/') to a real one, e.g., + '/e/www/'.
    • + +
  • 'next|N' + (next round)
    + Re-run the rewriting process (starting again with the + first rewriting rule). This time, the URL to match is no longer + the original URL, but rather the URL returned by the last rewriting rule. + This corresponds to the Perl next command or + the continue command in C. Use + this flag to restart the rewriting process - + to immediately go to the top of the loop.
    + Be careful not to create an infinite + loop!
    • + +
  • 'nocase|NC' + (no case)
    + This makes the Pattern case-insensitive, + ignoring difference between 'A-Z' and + 'a-z' when Pattern is matched against the current + URL.
    • + +
  • + 'noescape|NE' + (no URI escaping of + output)
    + This flag prevents mod_rewrite from applying the usual URI + escaping rules to the result of a rewrite. Ordinarily, + special characters (such as '%', '$', ';', and so on) + will be escaped into their hexcode equivalents ('%25', + '%24', and '%3B', respectively); this flag prevents this + from happening. This allows percent symbols to appear in + the output, as in +

    + RewriteRule /foo/(.*) /bar?arg=P1\%3d$1 [R,NE] +

    + which would turn '/foo/zed' into a safe + request for '/bar?arg=P1=zed'. +
    • + +
  • + 'nosubreq|NS' + (not for internal + sub-requests)
    + This flag forces the rewriting engine to skip a + rewriting rule if the current request is an internal + sub-request. For instance, sub-requests occur internally + in Apache when mod_include tries to find out + information about possible directory default files + (index.xxx files). On sub-requests it is not + always useful, and can even cause errors, if + the complete set of rules are applied. Use this flag to + exclude some rules.
    + To decide whether or not to use this rule: if you + prefix URLs with CGI-scripts, to force them to be + processed by the CGI-script, it's likely that you + will run into problems (or significant overhead) on + sub-requests. In these cases, use this flag. +
    • + +
  • + 'proxy|P' (force + proxy)
    + This flag forces the substitution part to be internally + sent as a proxy request and immediately (rewrite + processing stops here) put through the proxy module. You must make + sure that the substitution string is a valid URI + (typically starting with + http://hostname) which can be + handled by the Apache proxy module. If not, you will get an + error from the proxy module. Use this flag to achieve a + more powerful implementation of the ProxyPass directive, + to map remote content into the namespace of the local + server. + +

    Note: mod_proxy must be enabled in order + to use this flag.

    +
    • + +
  • + 'passthrough|PT' + (pass through to next + handler)
    + This flag forces the rewrite engine to set the + uri field of the internal + request_rec structure to the value of the + filename field. This flag is just a hack to + enable post-processing of the output of + RewriteRule directives, using + Alias, ScriptAlias, + Redirect, and other directives from + various URI-to-filename translators. For example, to rewrite + /abc to /def using + mod_rewrite, and then + /def to /ghi using + mod_alias: +

    + RewriteRule ^/abc(.*) /def$1 [PT]
    + Alias /def /ghi +

    + If you omit the PT flag, + mod_rewrite will rewrite + uri=/abc/... to + filename=/def/... as a full API-compliant + URI-to-filename translator should do. Then + mod_alias will try to do a + URI-to-filename transition, which will fail. + +

    Note: You must use this flag if you want to + mix directives from different modules which allow + URL-to-filename translators. The typical example + is the use of mod_alias and + mod_rewrite.

    +
    • + +
  • 'qsappend|QSA' + (query string + append)
    + This flag forces the rewrite engine to append a query + string part of the substitution string to the existing string, + instead of replacing it. Use this when you want to add more + data to the query string via a rewrite rule.
    • + +
  • 'redirect|R + [=code]' (force redirect)
    + Prefix Substitution with + http://thishost[:thisport]/ (which makes the + new URL a URI) to force a external redirection. If no + code is given, a HTTP response of 302 (MOVED + TEMPORARILY) will be returned. If you want to use other response + codes in the range 300-400, simply specify the appropriate number + or use one of the following symbolic names: + temp (default), permanent, + seeother. Use this for rules to + canonicalize the URL and return it to the client - to + translate ``/~'' into + ``/u/'', or to always append a slash to + /u/user, etc.
    + Note: When you use this flag, make + sure that the substitution field is a valid URL! Otherwise, + you will be redirecting to an invalid location. Remember + that this flag on its own will only prepend + http://thishost[:thisport]/ to the URL, and rewriting + will continue. Usually, you will want to stop rewriting at this point, + and redirect immediately. To stop rewriting, you should add + the 'L' flag. +
    • + +
  • 'skip|S=num' + (skip next rule(s))
    + This flag forces the rewriting engine to skip the next + num rules in sequence, if the current rule + matches. Use this to make pseudo if-then-else constructs: + The last rule of the then-clause becomes + skip=N, where N is the number of rules in the + else-clause. (This is not the same as the + 'chain|C' flag!)
    • + +
  • + 'type|T=MIME-type' + (force MIME type)
    + Force the MIME-type of the target file to be + MIME-type. This can be used to + set up the content-type based on some conditions. + For example, the following snippet allows .php files to + be displayed by mod_php if they are called with + the .phps extension: +

    + RewriteRule ^(.+\.php)s$ $1 [T=application/x-httpd-php-source] +

    +
    • +
+ +

Per-directory Rewrites

+ +

The rewrite engine may be used in .htaccess files. To enable the +rewrite engine for these files you need to set +"RewriteEngine On" and +"Options FollowSymLinks" must be enabled. If your +administrator has disabled override of FollowSymLinks for +a user's directory, then you cannot use the rewrite engine. This +restriction is required for security reasons.

+ +

When using the rewrite engine in .htaccess files the +per-directory prefix (which always is the same for a specific +directory) is automatically removed for the pattern matching +and automatically added after the substitution has been +done. This feature is essential for many sorts of rewriting; without +this, you would always have to match the parent directory, which is +not always possible. There is one exception: If a substitution string +starts with http://, then the directory prefix will +not be added, and an external redirect (or proxy +throughput, if using flag P) is forced. See the +RewriteBase directive for +more information.

+ +

The rewrite engine may also be used in <Directory> sections with the same +prefix-matching rules as would be applied to .htaccess +files. It is usually simpler, however, to avoid the prefix substitution +complication by putting the rewrite rules in the main server or +virtual host context, rather than in a <Directory> section.

+ +

Although rewrite rules are syntactically permitted in <Location> sections, this +should never be necessary and is unsupported.

+ +
+ +

Note: Substitution of Absolute URLs

+

+ When you prefix a substitution field with + http://thishost[:thisport], mod_rewrite will automatically strip that + out. This auto-reduction on URLs with an implicit + external redirect is most useful in + combination with a mapping-function which generates the + hostname part.

+ +

Remember: An unconditional external + redirect to your own server will not work with the prefix + http://thishost because of this feature. To + achieve such a self-redirect, you have to use the + R-flag.

+
+ +

Note: Query String

+

The Pattern will not be matched against the query string. + To do this, you must use a RewriteCond with the + %{QUERY_STRING} variable. You can, however, create + URLs in the substitution string, containing a query string + part. Simply use a question mark inside the substitution string, to + indicate that the following text should be re-injected into the + query string. When you want to erase an existing query string, + end the substitution string with just a question mark. To + combine new and old query strings, use the + [QSA] flag.

+
+ +

Here are all possible substitution combinations and their + meanings:

+ +

Inside per-server configuration + (httpd.conf)
+ for request ``GET + /somepath/pathinfo'':
+

+ +
+Given Rule                                      Resulting Substitution
+----------------------------------------------  ----------------------------------
+^/somepath(.*) otherpath$1                      invalid, not supported
+
+^/somepath(.*) otherpath$1  [R]                 invalid, not supported
+
+^/somepath(.*) otherpath$1  [P]                 invalid, not supported
+----------------------------------------------  ----------------------------------
+^/somepath(.*) /otherpath$1                     /otherpath/pathinfo
+
+^/somepath(.*) /otherpath$1 [R]                 http://thishost/otherpath/pathinfo
+                                                via external redirection
+
+^/somepath(.*) /otherpath$1 [P]                 doesn't make sense, not supported
+----------------------------------------------  ----------------------------------
+^/somepath(.*) http://thishost/otherpath$1      /otherpath/pathinfo
+
+^/somepath(.*) http://thishost/otherpath$1 [R]  http://thishost/otherpath/pathinfo
+                                                via external redirection
+
+^/somepath(.*) http://thishost/otherpath$1 [P]  doesn't make sense, not supported
+----------------------------------------------  ----------------------------------
+^/somepath(.*) http://otherhost/otherpath$1     http://otherhost/otherpath/pathinfo
+                                                via external redirection
+
+^/somepath(.*) http://otherhost/otherpath$1 [R] http://otherhost/otherpath/pathinfo
+                                                via external redirection
+                                                (the [R] flag is redundant)
+
+^/somepath(.*) http://otherhost/otherpath$1 [P] http://otherhost/otherpath/pathinfo
+                                                via internal proxy
+
+ +

Inside per-directory configuration for + /somepath
+ (/physical/path/to/somepath/.htacccess, with + RewriteBase /somepath)
+ for request ``GET + /somepath/localpath/pathinfo'':
+

+ +
+Given Rule                                      Resulting Substitution
+----------------------------------------------  ----------------------------------
+^localpath(.*) otherpath$1                      /somepath/otherpath/pathinfo
+
+^localpath(.*) otherpath$1  [R]                 http://thishost/somepath/otherpath/pathinfo
+                                                via external redirection
+
+^localpath(.*) otherpath$1  [P]                 doesn't make sense, not supported
+----------------------------------------------  ----------------------------------
+^localpath(.*) /otherpath$1                     /otherpath/pathinfo
+
+^localpath(.*) /otherpath$1 [R]                 http://thishost/otherpath/pathinfo
+                                                via external redirection
+
+^localpath(.*) /otherpath$1 [P]                 doesn't make sense, not supported
+----------------------------------------------  ----------------------------------
+^localpath(.*) http://thishost/otherpath$1      /otherpath/pathinfo
+
+^localpath(.*) http://thishost/otherpath$1 [R]  http://thishost/otherpath/pathinfo
+                                                via external redirection
+
+^localpath(.*) http://thishost/otherpath$1 [P]  doesn't make sense, not supported
+----------------------------------------------  ----------------------------------
+^localpath(.*) http://otherhost/otherpath$1     http://otherhost/otherpath/pathinfo
+                                                via external redirection
+
+^localpath(.*) http://otherhost/otherpath$1 [R] http://otherhost/otherpath/pathinfo
+                                                via external redirection
+                                                (the [R] flag is redundant)
+
+^localpath(.*) http://otherhost/otherpath$1 [P] http://otherhost/otherpath/pathinfo
+                                                via internal proxy
+
+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_setenvif.html b/docs/manual/mod/mod_setenvif.html new file mode 100644 index 00000000..0a1cf29b --- /dev/null +++ b/docs/manual/mod/mod_setenvif.html @@ -0,0 +1,11 @@ +URI: mod_setenvif.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_setenvif.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_setenvif.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_setenvif.html.en b/docs/manual/mod/mod_setenvif.html.en new file mode 100644 index 00000000..7a6e251f --- /dev/null +++ b/docs/manual/mod/mod_setenvif.html.en @@ -0,0 +1,285 @@ + + + +mod_setenvif - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_setenvif

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Allows the setting of environment variables based +on characteristics of the request
Status:Base
Module Identifier:setenvif_module
Source File:mod_setenvif.c
+

Summary

+ + +

The mod_setenvif module allows you to set + environment variables according to whether different aspects of + the request match regular expressions you specify. These + environment variables can be used by other parts of the server + to make decisions about actions to be taken.

+ +

The directives are considered in the order they appear in + the configuration files. So more complex sequences can be used, + such as this example, which sets netscape if the + browser is mozilla but not MSIE.

+ +

+ BrowserMatch ^Mozilla netscape
+ BrowserMatch MSIE !netscape
+

+
+ + +
top
+

BrowserMatch Directive

+ + + + + + + +
Description:Sets environment variables conditional on HTTP User-Agent +
Syntax:BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_setenvif
+

The BrowserMatch is a special cases of the + SetEnvIf directive that + sets environment variables conditional on the + User-Agent HTTP request header. The following two + lines have the same effect:

+

+ BrowserMatchNoCase Robot is_a_robot
+ SetEnvIfNoCase User-Agent Robot is_a_robot
+

+ +

Some additional examples:

+

+ BrowserMatch ^Mozilla forms jpeg=yes browser=netscape
+ BrowserMatch "^Mozilla/[2-3]" tables agif frames javascript
+ BrowserMatch MSIE !javascript
+

+ +
+
top
+

BrowserMatchNoCase Directive

+ + + + + + + + +
Description:Sets environment variables conditional on User-Agent without +respect to case
Syntax:BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_setenvif
Compatibility:Apache 1.2 and + above (in Apache 1.2 this directive was found in the + now-obsolete mod_browser module)
+ +

The BrowserMatchNoCase directive is + semantically identical to the BrowserMatch directive. + However, it provides for case-insensitive matching. For + example:

+

+ BrowserMatchNoCase mac platform=macintosh
+ BrowserMatchNoCase win platform=windows
+

+ +

The BrowserMatch and + BrowserMatchNoCase directives are special cases of + the SetEnvIf and SetEnvIfNoCase + directives. The following two lines have the same effect:

+

+ BrowserMatchNoCase Robot is_a_robot
+ SetEnvIfNoCase User-Agent Robot is_a_robot
+

+ +
+
top
+

SetEnvIf Directive

+ + + + + + + +
Description:Sets environment variables based on attributes of the request +
Syntax:SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_setenvif
+

The SetEnvIf directive defines + environment variables based on attributes of the request. The + attribute specified in the first argument can be one of three + things:

+ +
    +
  1. An HTTP request header field (see RFC2616 + for more information about these); for example: Host, + User-Agent, Referer, and + Accept-Language. A regular expression may be + used to specify a set of request headers.
    2. + +
  2. One of the following aspects of the request: +
      +
    • Remote_Host - the hostname (if available) of + the client making the request
      • + +
    • Remote_Addr - the IP address of the client + making the request
      • + +
    • Server_Addr - the IP address of the server + on which the request was received (only with versions later + than 2.0.43)
      • + +
    • Request_Method - the name of the method + being used (GET, POST, et + cetera)
      • + +
    • Request_Protocol - the name and version of + the protocol with which the request was made (e.g., + "HTTP/0.9", "HTTP/1.1", etc.)
      • + +
    • Request_URI - the resource requested on the HTTP + request line -- generally the portion of the URL + following the scheme and host portion without the query string
      • +
    +
    3. + +
  3. The name of an environment variable in the list of those +associated with the request. This allows +SetEnvIf directives to test against the result +of prior matches. Only those environment variables defined by earlier +SetEnvIf[NoCase] directives are available for testing in +this manner. 'Earlier' means that they were defined at a broader scope +(such as server-wide) or previously in the current directive's scope. +Environment variables will be considered only if there was no match +among request characteristics and a regular expression was not +used for the attribute.
    4. +
+ +

The second argument (regex) is a regular expression. If the regex +matches against the attribute, then the remainder of the +arguments are evaluated.

+ +

The rest of the arguments give the names of variables to set, and +optionally values to which they should be set. These take the form +of

+ +
    +
  1. varname, or
    2. + +
  2. !varname, or
    3. + +
  3. varname=value
    4. +
+ +

In the first form, the value will be set to "1". The second + will remove the given variable if already defined, and the + third will set the variable to the literal value given by + value. Since version 2.0.51 Apache will + recognize occurrences of $1..$9 within + value and replace them by parenthesized subexpressions + of regex.

+ +

Example:

+ + SetEnvIf Request_URI "\.gif$" object_is_image=gif
+ SetEnvIf Request_URI "\.jpg$" object_is_image=jpg
+ SetEnvIf Request_URI "\.xbm$" object_is_image=xbm
+ :
+ SetEnvIf Referer www\.mydomain\.com intra_site_referral
+ :
+ SetEnvIf object_is_image xbm XBIT_PROCESSING=1
+ :
+ SetEnvIf ^TS* ^[a-z].* HAVE_TS
+

+ +

The first three will set the environment variable + object_is_image if the request was for an image + file, and the fourth sets intra_site_referral if + the referring page was somewhere on the + www.mydomain.com Web site.

+ +

The last example will set environment variable + HAVE_TS if the request contains any headers that + begin with "TS" whose values begins with any character in the + set [a-z].

+ +

See also

+ +
+
top
+

SetEnvIfNoCase Directive

+ + + + + + + + +
Description:Sets environment variables based on attributes of the request +without respect to case
Syntax:SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Base
Module:mod_setenvif
Compatibility:Apache 1.3 and above
+ +

The SetEnvIfNoCase is semantically identical to + the SetEnvIf directive, + and differs only in that the regular expression matching is + performed in a case-insensitive manner. For example:

+

+ SetEnvIfNoCase Host Apache\.Org site=apache +

+ +

This will cause the site environment variable + to be set to "apache" if the HTTP request header + field Host: was included and contained + Apache.Org, apache.org, or any other + combination.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_setenvif.html.ja.euc-jp b/docs/manual/mod/mod_setenvif.html.ja.euc-jp new file mode 100644 index 00000000..ef63bcc5 --- /dev/null +++ b/docs/manual/mod/mod_setenvif.html.ja.euc-jp @@ -0,0 +1,282 @@ + + + +mod_setenvif - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_setenvif

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤ÎÆÃħ¤Ë´ð¤Å¤¤¤¿´Ä¶­ÊÑ¿ô¤ÎÀßÄê¤ò²Äǽ¤Ë¤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:setenvif_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_setenvif.c
+

³µÍ×

+ + +

mod_setenvif + ¥â¥¸¥å¡¼¥ë¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤Î¤¢¤ë¦Ì̤¬»ØÄꤵ¤ì¤¿Àµµ¬É½¸½ + ¤Ë¹ç¤¦¤«¤É¤¦¤«¤Ë¤è¤Ã¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ëµ¡Ç½¤òÄ󶡤·¤Þ¤¹¡£ + ¤³¤ì¤é¤Î´Ä¶­ÊÑ¿ô¤ò»ÈÍѤ·¤Æ¡¢¥µ¡¼¥Ð¤Î¾¤ÎÉôʬ¤¬¤É¤Î¤è¤¦¤ÊÆ°ºî¤ò¤¹¤ë¤«¤ò + ·èÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤¬Ä󶡤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ÀßÄê¥Õ¥¡¥¤¥ë¤Ë¸½¤ì¤ë½çÈÖ¤ËŬÍѤµ¤ì¤Þ¤¹¡£ + ¤½¤ì¤ò»È¤Ã¤Æ¡¢¼¡¤ÎÎã¤Î¤è¤¦¤Ë¤è¤êÊ£»¨¤ÊÀßÄê¤ò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥Ö¥é¥¦¥¶¤¬ mozilla ¤Ç¤Ï¤¢¤ë¤±¤ì¤É¡¢MSIE ¤Ç¤Ï¤Ê¤¤¤È¤­¤Ë + netscape ¤òÀßÄꤷ¤Þ¤¹¡£

+

+ BrowserMatch ^Mozilla netscape
+ BrowserMatch MSIE !netscape
+

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

BrowserMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:HTTP User-Agent ¤Ë´ð¤Å¤¤¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë +
¹½Ê¸:BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_setenvif
+

BrowserMatch ¤Ï + SetEnvIf ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ÆÃÎã¤Ç¡¢User-Agent HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Ë´ð¤Å¤¤¤Æ + ´Ä¶­ÊÑ¿ô¤òÀßÄꤷ¤Þ¤¹¡£°Ê²¼¤Î 2 ¹Ô¤Î¸ú²Ì¤ÏƱ¤¸¤Ë¤Ê¤ê¤Þ¤¹:

+ +

+ BrowserMatchNoCase Robot is_a_robot
+ SetEnvIfNoCase User-Agent Robot is_a_robot
+

+ +

¤½¤Î¾¤ÎÎã:

+

+ BrowserMatch ^Mozilla forms jpeg=yes browser=netscape
+ BrowserMatch "^Mozilla/[2-3]" tables agif frames javascript
+ BrowserMatch MSIE !javascript
+

+ +
+
top
+

BrowserMatchNoCase ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:HTTP User-Agent ¤Ë´ð¤Å¤¤¤ÆÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¤Ë +´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë
¹½Ê¸:BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_setenvif
¸ß´¹À­:Apache 1.2 °Ê¹ß + (Apache 1.2 ¤Ç¤Ï¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤â¤¦ÍѤ¤¤é¤ì¤Æ¤¤¤Ê¤¤ + mod_browser ¥â¥¸¥å¡¼¥ë¤Ë¤¢¤ê¤Þ¤·¤¿)
+ +

BrowserMatchNoCase ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + °Ọ̃Ū¤Ë¤Ï BrowserMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + Ʊ¤¸¤Ç¤¹¡£¤¿¤À¤·¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Ê¤¤ + ¥Þ¥Ã¥Á¥ó¥°¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£Î㤨¤Ð:

+ +

+ BrowserMatchNoCase mac platform=macintosh
+ BrowserMatchNoCase win platform=windows
+

+ +

BrowserMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + BrowserMatchNoCase ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + SetEnvIf ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + SetEnvIfNoCase ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ÆÃÎã¤Ç¤¹¡£°Ê²¼¤Î 2 ¹Ô¤Î¸ú²Ì¤ÏƱ¤¸¤Ç¤¹:

+ +

+ BrowserMatchNoCase Robot is_a_robot
+ SetEnvIfNoCase User-Agent Robot is_a_robot
+

+ +
+
top
+

SetEnvIf ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤Î°À­¤Ë´ð¤Å¤¤¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë +
¹½Ê¸:SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_setenvif
+

SetEnvIf + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤Î°À­¤Ë´ð¤Å¤¤¤Æ´Ä¶­ÊÑ¿ô¤òÄêµÁ¤·¤Þ¤¹¡£ + ºÇ½é¤Î°ú¿ô¤Ç»ØÄê¤Ç¤­¤ë attribute ¤Ï°Ê²¼¤Î»°¤Ä¤Î¤É¤ì¤«¤Ç¤¹:

+ +
    +
  1. HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É (¾Ü¤·¤¤¾ðÊó¤Ï RFC 2616 ¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤)¡£Î㤨¤Ð¡¢Host, + User-Agent, Referer, + Accept-Language ¤Ç¤¹¡£¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Î½¸¹ç¤ò¸½¤¹¤¿¤á¤Ë + Àµµ¬É½¸½¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
    2. + +
  2. °Ê²¼¤Î¥ê¥¯¥¨¥¹¥È¤Î°ìÉôʬ¤Î¤É¤ì¤«: + +
      +
    • Remote_Host - + ¥ê¥¯¥¨¥¹¥È¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤ë¥¯¥é¥¤¥¢¥ó¥È¤Î¥Û¥¹¥È̾ (¤â¤·¤¢¤ì¤Ð)
      • + +
    • Remote_Addr - + ¥ê¥¯¥¨¥¹¥È¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤ë¥¯¥é¥¤¥¢¥ó¥È¤Î IP ¥¢¥É¥ì¥¹
      • + +
    • Server_Addr - + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤Ã¤¿¥µ¡¼¥Ð¤Î IP ¥¢¥É¥ì¥¹ + (2.0.43 °Ê¹ß¤Î¤ß)
      • + +
    • Request_Method - + »ÈÍѤµ¤ì¤Æ¤¤¤ë¥á¥½¥Ã¥É̾ (GET, POST + ¤Ê¤É)
      • + +
    • Request_Protocol - + ¥ê¥¯¥¨¥¹¥È¤¬¹Ô¤Ê¤ï¤ì¤¿¥×¥í¥È¥³¥ë¤Î̾Á°¤È¥Ð¡¼¥¸¥ç¥ó + (Î㤨¤Ð¡¢"HTTP/0.9", "HTTP/1.1" ¤Ê¤É¡£)
      • + +
    • Request_URI - + URL ¤Î¥¹¥­¡¼¥à¤È¥Û¥¹¥È¤Î¸å¤ÎÉôʬ
      • +
    +
    3. + +
  3. ¥ê¥¯¥¨¥¹¥È¤È´ØÏ¢ÉÕ¤±¤é¤ì¤ë´Ä¶­ÊÑ¿ô¤Î¥ê¥¹¥È¡£¤³¤ì¤Ë¤è¤ê +SetEnvIf ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬°ÊÁ°¤Î¥Þ¥Ã¥Á¤Î·ë²Ì¤ò +»È¤¦¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤ÎÊýË¡¤Î¥Æ¥¹¥È¤Ç¤ÏÁ°¤ÎÉôʬ¤Ë¤¢¤ë +SetEnvIf[NoCase] ¤Î·ë²Ì¤Î¤ß¤ò»ÈÍѲÄǽ¤Ç¤¹¡£¡ÖÁ°¡×¤È¤Ï¡¢ +¤è¤ê¹­¤¤ÈϰϤËÂФ·¤ÆÄêµÁ¤µ¤ì¤Æ¤¤¤ë (¥µ¡¼¥ÐÁ´ÂΤΤ褦¤Ë) ¤«¡¢¸½ºß¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î +ÈϰϤǤè¤êÁ°¤ÎÉôʬ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë¤«¡¢¤È¤¤¤¦¤³¤È¤Ç¤¹¡£ +´Ä¶­ÊÑ¿ô¤Ç¤¢¤ë²ÄǽÀ­¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤ÎÆÃÀ­¤ËÂФ¹¤ë¥Þ¥Ã¥Á¤¬Â¸ºß¤»¤º¡¢ +attribute ¤ËÀµµ¬É½¸½¤¬»È¤ï¤ì¤Ê¤«¤Ã¤¿¤È¤­¤Ë¤Î¤ß¹Í褵¤ì¤Þ¤¹¡£
    4. +
+ +

Æó¤ÄÌܤΰú¿ô (regex) ¤Ï Perl ¸ß´¹¤ÎÀµµ¬É½¸½¤Ç¤¹¡£ +¤³¤ì¤Ï POSIX.2 ¤Î egrep ·Á¼°¤ÎÀµµ¬É½¸½¤È»÷¤Æ¤¤¤Þ¤¹¡£regex ¤¬ +attribute ¤Ë¥Þ¥Ã¥Á¤¹¤ë¾ì¹ç¤Ï¡¢»Ä¤ê¤Î°ú¿ô¤¬É¾²Á¤µ¤ì¤Þ¤¹¡£

+ +

»Ä¤ê¤Î°ú¿ô¤ÏÀßÄꤹ¤ëÊÑ¿ô¤Î̾Á°¤Ç¡¢ÀßÄꤵ¤ì¤ëÃͤò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ +¤³¤ì¤Ï¡¢

+ +
    +
  1. varname
    2. + +
  2. !varname
    3. + +
  3. varname=value
    4. +
+ +

¤Î¤É¤ì¤«¤Î·Á¼°¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

ºÇ½é¤Î·Á¼°¤Ç¤Ï¡¢ÃÍ¤Ï "1" ¤ËÀßÄꤵ¤ì¤Þ¤¹¡£ + Æó¤ÄÌܤϤ⤷Ãͤ¬ÄêµÁ¤µ¤ì¤Æ¤¤¤ì¤Ð¤½¤ì¤ò¼è¤ê½ü¤­¤Þ¤¹¡£ + »°¤ÄÌܤÏÊÑ¿ô¤ò value ¤ÎÍ¿¤¨¤é¤ì¤¿ÃͤËÀßÄꤷ¤Þ¤¹¡£ + 2.0.51 °Ê¹ß¤Ç¤Ï¡¢regex Æâ¤Ë $1..$9 + ¤¬Â¸ºß¤¹¤ì¤Ð¤½¤ì¤òǧ¼±¤·¡¢regex ¤ÎÂбþ¤¹¤ë´Ý³ç¸Ì¤Ç°Ï¤Þ¤ì¤¿Éôʬ¤Ç + ÃÖ´¹¤·¤Þ¤¹¡£

+ +

Îã:

+ + SetEnvIf Request_URI "\.gif$" object_is_image=gif
+ SetEnvIf Request_URI "\.jpg$" object_is_image=jpg
+ SetEnvIf Request_URI "\.xbm$" object_is_image=xbm
+ :
+ SetEnvIf Referer www\.mydomain\.com intra_site_referral
+ :
+ SetEnvIf object_is_image xbm XBIT_PROCESSING=1
+ :
+ SetEnvIf ^TS* ^[a-z].* HAVE_TS
+

+ +

½é¤á¤Î»°¤Ä¤Ï¥ê¥¯¥¨¥¹¥È¤¬²èÁü¤Ç¤¢¤ë¤È¤­¤Ë´Ä¶­ÊÑ¿ô + object_is_image ¤òÀßÄꤷ¤Þ¤¹¡£»Í¤ÄÌÜ¤Ï + »²¾È¸µ¤Î¥Ú¡¼¥¸¤¬¥¦¥§¥Ö¥µ¥¤¥È www.mydomain.com ¤Ë¤¢¤ë¤È¤­¤Ë + intra_site_referral ¤òÀßÄꤷ¤Þ¤¹¡£

+ +

ºÇ¸å¤ÎÎã¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤Ë "TS" ¤Ç»Ï¤Þ¤ê¡¢Ãͤ¬½¸¹ç [a-z] ¤Î¤É¤ì¤«¤Ç + »Ï¤Þ¤ë¥Ø¥Ã¥À¤¬¤¢¤ë¤È¤­¤Ë HAVE_TS ¤òÀßÄꤷ¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

SetEnvIfNoCase ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤Î°À­¤Ë´ð¤Å¤¤¤ÆÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¤Ë´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë
¹½Ê¸:SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:FileInfo
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_setenvif
¸ß´¹À­:Apache 1.3 °Ê¹ß
+ +

SetEnvIfNoCase ¤Ï°Ọ̃Ū¤Ë¤Ï + SetEnvIf ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + Ʊ¤¸¤Ç¤¹¡£°ã¤¤¤Ï¡¢Àµµ¬É½¸½¤Î¥Þ¥Ã¥Á¥ó¥°¤¬Âçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Ê¤¤¤Ç + ¹Ô¤Ê¤ï¤ì¤ë¤³¤È¤Ç¤¹¡£Î㤨¤Ð:

+ +

+ SetEnvIfNoCase Host Apache\.Org site=apache +

+ +

¤³¤ì¤Ï HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤Ë¥Õ¥£¡¼¥ë¥É Host: ¤¬ + ¤¢¤ê¡¢¤½¤ÎÃͤ¬ Apache.Org ¤ä apache.org¡¢ + ¤½¤Î¾¤ÎÂçʸ»ú¾®Ê¸»ú¤ÎÁȤ߹ç¤ï¤»¤Ç¤¢¤Ã¤¿¤È¤­¤Ë site + ´Ä¶­ÊÑ¿ô¤ò "apache" ¤ËÀßÄꤷ¤Þ¤¹¡£

+ + +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_setenvif.html.ko.euc-kr b/docs/manual/mod/mod_setenvif.html.ko.euc-kr new file mode 100644 index 00000000..bc71ba20 --- /dev/null +++ b/docs/manual/mod/mod_setenvif.html.ko.euc-kr @@ -0,0 +1,259 @@ + + + +mod_setenvif - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_setenvif

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:¿äûÀÇ ¼º°Ý¿¡ µû¶ó ȯ°æº¯¼ö ¼³Á¤À» º¯°æÇÑ´Ù
»óÅÂ:Base
¸ðµâ¸í:setenvif_module
¼Ò½ºÆÄÀÏ:mod_setenvif.c
+

¿ä¾à

+ + +

mod_setenvif ¸ðµâÀº ¿äûÀÇ ¼º°ÝÀÌ + Á¤±ÔÇ¥Çö½Ä¿¡ ÇØ´çÇÏ´ÂÁö ¿©ºÎ·Î ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù. ¼­¹öÀÇ + ´Ù¸¥ ºÎºÐÀÌ ÇൿÀ» °áÁ¤ÇÒ¶§ ÀÌ È¯°æº¯¼ö¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

¼³Á¤ÆÄÀÏ¿¡ ³ª¿À´Â ¼ø¼­´ë·Î Áö½Ã¾î¸¦ ó¸®ÇÑ´Ù. ±×·¡¼­ + ºê¶ó¿ìÀú°¡ MSIE°¡ ¾Æ´Ï¶ó mozillaÀÎ °æ¿ì netscape¸¦ + ¼³Á¤ÇÏ´Â ¾Æ·¡ ¿¹¿Í °°ÀÌ ¿©·¯ Áö½Ã¾î¸¦ ÇÔ²² »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

+ BrowserMatch ^Mozilla netscape
+ BrowserMatch MSIE !netscape
+

+
+ + +
top
+

BrowserMatch Áö½Ã¾î

+ + + + + + + +
¼³¸í:HTTP User-Agent¿¡ µû¶ó ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù
¹®¹ý:BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_setenvif
+

BrowserMatch´Â SetEnvIf Áö½Ã¾îÀÇ Æ¯º°ÇÑ + °æ¿ì·Î, HTTP ¿äû Çì´õ User-Agent¿¡ µû¶ó ȯ°æº¯¼ö¸¦ + ¼³Á¤ÇÑ´Ù. ´ÙÀ½ µÎ ÁÙÀº °°´Ù:

+

+ BrowserMatchNoCase Robot is_a_robot
+ SetEnvIfNoCase User-Agent Robot is_a_robot
+

+ +

Ãß°¡ ¿¹Á¦:

+

+ BrowserMatch ^Mozilla forms jpeg=yes browser=netscape
+ BrowserMatch "^Mozilla/[2-3]" tables agif frames javascript
+ BrowserMatch MSIE !javascript
+

+ +
+
top
+

BrowserMatchNoCase Áö½Ã¾î

+ + + + + + + + +
¼³¸í:´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾Ê°í User-Agent¿¡ µû¶ó ȯ°æº¯¼ö¸¦ +¼³Á¤ÇÑ´Ù
¹®¹ý:BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_setenvif
Áö¿ø:¾ÆÆÄÄ¡ 1.2 ÀÌ»ó (¾ÆÆÄÄ¡ 1.2¿¡¼­ ÀÌ Áö½Ã¾î´Â ÇöÀç + ¾ø¾îÁø mod_browser ¸ðµâ¿¡ ÀÖ¾ú´Ù)
+ +

BrowserMatchNoCase Áö½Ã¾î´Â BrowserMatch Áö½Ã¾î¿Í + ÀÇ¹Ì»ó °°´Ù. ±×·¯³ª ÀÌ Áö½Ã¾î´Â ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾Ê´Â´Ù. + ¿¹¸¦ µé¾î:

+

+ BrowserMatchNoCase mac platform=macintosh
+ BrowserMatchNoCase win platform=windows
+

+ +

BrowserMatch¿Í + BrowserMatchNoCase Áö½Ã¾î´Â + SetEnvIf¿Í + SetEnvIfNoCase + Áö½Ã¾îÀÇ Æ¯º°ÇÑ °æ¿ì´Ù. ´ÙÀ½ ÁÖ ÁÙÀº °°´Ù:

+

+ BrowserMatchNoCase Robot is_a_robot
+ SetEnvIfNoCase User-Agent Robot is_a_robot
+

+ +
+
top
+

SetEnvIf Áö½Ã¾î

+ + + + + + + +
¼³¸í:¿äûÀÇ ¼ºÁú¿¡ µû¶ó ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù
¹®¹ý:SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_setenvif
+

SetEnvIf Áö½Ã¾î´Â ¿äûÀÇ ¼ºÁú¿¡ + µû¶ó ȯ°æº¯¼ö¸¦ Á¤ÀÇÇÑ´Ù. ù¹ø° ¾Æ±Ô¸ÕÆ® attribute´Â + ´ÙÀ½ ¼¼°¡ÁöÁß Çϳª´Ù:

+ +
    +
  1. HTTP ¿äû Çì´õ (´õ ÀÚ¼¼ÇÑ Á¤º¸´Â RFC2616 + Âü°í); ¿¹¸¦ µé¾î: Host, User-Agent, + Referer, Accept-Language. Á¤±ÔÇ¥Çö½ÄÀ» + »ç¿ëÇÏ¿© ¿©·¯ ¿äû Çì´õ¸¦ ÁöĪÇÒ ¼ö ÀÖ´Ù.
    2. + +
  2. ¿äûÀÇ ´ÙÀ½ ¼ºÁúÁß Çϳª: +
      +
    • Remote_Host - (ÀÖ´Ù¸é) ¿äûÇϴ Ŭ¶óÀ̾ðÆ®ÀÇ + È£½ºÆ®¸í
      • + +
    • Remote_Addr - ¿äûÇϴ Ŭ¶óÀ̾ðÆ®ÀÇ IP ÁÖ¼Ò
      • + +
    • Server_Addr - ¿äûÀ» ¹Þ´Â ¼­¹öÀÇ IP ÁÖ¼Ò + (2.0.43 ¹öÀü ÀÌÈÄ¿¡¸¸)
      • + +
    • Request_Method - »ç¿ëÇÑ ¸Þ½áµå À̸§ + (GET, POST, µîµî)
      • + +
    • Request_Protocol - ¿äûÀÇ ÇÁ·ÎÅäÄÝ À̸§°ú + ¹öÀü (¿¹¸¦ µé¾î, "HTTP/0.9", "HTTP/1.1", µî.)
      • + +
    • Request_URI - HTTP ¿äû¿¡¼­ ¿äûÇÑ ÀÚ¿ø + -- ÀϹÝÀûÀ¸·Î URL¿¡¼­ ÁúÀǹ®ÀÚ¿­À» Á¦¿ÜÇÑ ½ºÅ´(scheme)°ú + È£½ºÆ® ÀÌÈÄ ºÎºÐ
      • +
    +
    3. + +
  3. ¿äû°ú ¿¬°üµÈ ȯ°æº¯¼ö À̸§. ±×·¡¼­ SetEnvIf +Áö½Ã¾î´Â ÀÌÀü Áö½Ã¾îÀÇ °á°ú¸¦ °Ë»çÇÒ ¼ö ÀÖ´Ù. ÀÌÀü¿¡ +SetEnvIf[NoCase] Áö½Ã¾î·Î Á¤ÀÇÇÑ È¯°æº¯¼ö¸¸À» +°Ë»çÇÒ ¼ö ÀÖ´Ù. 'ÀÌÀü'À̶õ (¼­¹öÀü¿ª°ú °°ÀÌ) ´õ ³ÐÀº ¿µ¿ª ȤÀº +Áö½Ã¾îÀÇ ÇöÀç ¿µ¿ª ÀÌÀüÀ» ¶æÇÑ´Ù. ¿äû ¼ºÁúÀÌ ¾Æ´Ï°í Á¤±ÔÇ¥Çö½ÄÀÌ +¾Æ´Ñ attribute´Â ȯ°æº¯¼ö·Î Ãë±ÞÇÑ´Ù.
    4. +
+ +

µÎ¹ø° ¾Æ±Ô¸ÕÆ®´Â (regex) Perl ȣȯ Á¤±ÔÇ¥Çö½ÄÀÌ´Ù. +ÀÌ´Â POSIX.2 egrepÀÇ Á¤±ÔÇ¥Çö½Ä°ú ºñ½ÁÇÏ´Ù. regex°¡ +attribute¿¡ ´ëÀÀÇÏ¸é ³ª¸ÓÁö ¾Æ±Ô¸ÕÆ®¸¦ ó¸®ÇÑ´Ù.

+ +

³ª¸ÓÁö ¾Æ±Ô¸ÕÆ®´Â ¼³Á¤ÇÒ º¯¼ö¸í°ú (¼±ÅÃÀûÀÎ) ¼³Á¤°ªµéÀÌ´Ù. +´ÙÀ½°ú °°Àº Çü½ÄÀÌ´Ù

+ +
    +
  1. varname, ȤÀº
    2. + +
  2. !varname, ȤÀº
    3. + +
  3. varname=value
    4. +
+ +

ù¹ø° ÇüÅ´ °ªÀ¸·Î "1"À» »ç¿ëÇÑ´Ù. µÎ¹ø° ÇüÅ´ º¯¼ö°¡ + ÀÌ¹Ì Á¤ÀÇµÈ °æ¿ì º¯¼ö¸¦ Á¦°ÅÇÏ°í, ¼¼¹ø°´Â º¯¼öÀÇ °ªÀ¸·Î + value¸¦ ¼³Á¤ÇÑ´Ù. ¾ÆÆÄÄ¡ 2.0.51ºÎÅÍ + value¿¡ ÀÖ´Â $1..$9¸¦ + regexÀÇ °ýȣģ ÇÏÀ§Ç¥Çö½ÄÀ¸·Î ´ëüÇÑ´Ù.

+ +

¿¹Á¦:

+ + SetEnvIf Request_URI "\.gif$" object_is_image=gif
+ SetEnvIf Request_URI "\.jpg$" object_is_image=jpg
+ SetEnvIf Request_URI "\.xbm$" object_is_image=xbm
+ :
+ SetEnvIf Referer www\.mydomain\.com intra_site_referral
+ :
+ SetEnvIf object_is_image xbm XBIT_PROCESSING=1
+ :
+ SetEnvIf ^TS* ^[a-z].* HAVE_TS
+

+ +

óÀ½ ¼¼ ÁÙÀº À̹ÌÁö ÆÄÀÏÀ» ¿äûÇÑ °æ¿ì ȯ°æº¯¼ö + object_is_image¸¦ ¼³Á¤ÇÑ´Ù. ³×¹ø° ÁÙÀº ÆäÀÌÁö¸¦ + www.mydomain.com À¥»çÀÌÆ®¿¡¼­ ÂüÁ¶ÇÑ °æ¿ì + intra_site_referralÀ» ¼³Á¤ÇÑ´Ù.

+ +

¸¶Áö¸· ¿¹´Â ¿äû¿¡ À̸§¿¡ "TS"·Î ½ÃÀÛÇÏ°í °ªÀÌ [a-z] + Áß Çϳª·Î ½ÃÀÛÇÏ´Â Çì´õ°¡ ÀÖ´Â °æ¿ì ȯ°æº¯¼ö + HAVE_TS¸¦ ¼³Á¤ÇÑ´Ù.

+ +

Âü°í

+ +
+
top
+

SetEnvIfNoCase Áö½Ã¾î

+ + + + + + + + +
¼³¸í:´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾Ê°í ¿äûÀÇ ¼ºÁú¿¡ µû¶ó ȯ°æº¯¼ö¸¦ +¼³Á¤ÇÑ´Ù
¹®¹ý:SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:FileInfo
»óÅÂ:Base
¸ðµâ:mod_setenvif
Áö¿ø:¾ÆÆÄÄ¡ 1.3 ÀÌÈÄ
+ +

SetEnvIfNoCase´Â Àǹ̻ó SetEnvIf Áö½Ã¾î¿Í °°Áö¸¸, + ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾Ê°í Á¤±ÔÇ¥Çö½ÄÀ» ã´Â´Ù. ¿¹¸¦ µé¾î:

+

+ SetEnvIfNoCase Host Apache\.Org site=apache +

+ +

ÀÌ °æ¿ì HTTP ¿äû Çì´õ Host:°¡ + Apache.Org, apache.org µîÀ» Æ÷ÇÔÇϸé + site ȯ°æº¯¼ö¸¦ "apache"·Î ¼³Á¤ÇÑ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_so.html b/docs/manual/mod/mod_so.html new file mode 100644 index 00000000..1053634f --- /dev/null +++ b/docs/manual/mod/mod_so.html @@ -0,0 +1,11 @@ +URI: mod_so.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_so.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_so.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_so.html.en b/docs/manual/mod/mod_so.html.en new file mode 100644 index 00000000..5b62f791 --- /dev/null +++ b/docs/manual/mod/mod_so.html.en @@ -0,0 +1,190 @@ + + + +mod_so - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_so

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Loading of executable code and +modules into the server at start-up or restart time
Status:Extension
Module Identifier:so_module
Source File:mod_so.c
Compatibility:This is a Base module (always included) on +Windows
+

Summary

+ + +

On selected operating systems this module can be used to + load modules into Apache at runtime via the Dynamic Shared Object (DSO) mechanism, + rather than requiring a recompilation.

+ +

On Unix, the loaded code typically comes from shared object + files (usually with .so extension), on Windows + this may either the .so or .dll + extension.

+ +

Warning

+

Apache 1.3 modules cannot be directly used + with Apache 2.0 - the module must be modified to dynamically + load or compile into Apache 2.0.

+
+
+ +
top
+
+

Creating Loadable Modules for Windows

+ +

Note

+

The module name format changed for Windows + with Apache 1.3.15 and 2.0 - the modules are now named as + mod_foo.so

+ +

While mod_so still loads modules with + ApacheModuleFoo.dll names, the new naming convention is + preferred; if you are converting your loadable module for 2.0, + please fix the name to this 2.0 convention.

+ +

The Apache module API is unchanged between the Unix and + Windows versions. Many modules will run on Windows with no or + little change from Unix, although others rely on aspects of the + Unix architecture which are not present in Windows, and will + not work.

+ +

When a module does work, it can be added to the server in + one of two ways. As with Unix, it can be compiled into the + server. Because Apache for Windows does not have the + Configure program of Apache for Unix, the module's + source file must be added to the ApacheCore project file, and + its symbols must be added to the + os\win32\modules.c file.

+ +

The second way is to compile the module as a DLL, a shared + library that can be loaded into the server at runtime, using + the LoadModule + directive. These module DLLs can be distributed and run on any + Apache for Windows installation, without recompilation of the + server.

+ +

To create a module DLL, a small change is necessary to the + module's source file: The module record must be exported from + the DLL (which will be created later; see below). To do this, + add the AP_MODULE_DECLARE_DATA (defined in the + Apache header files) to your module's module record definition. + For example, if your module has:

+ +

+ module foo_module; +

+ +

Replace the above with:

+

+ module AP_MODULE_DECLARE_DATA foo_module; +

+ +

Note that this will only be activated on Windows, so the + module can continue to be used, unchanged, with Unix if needed. + Also, if you are familiar with .DEF files, you can + export the module record with that method instead.

+ +

Now, create a DLL containing your module. You will need to + link this against the libhttpd.lib export library that is + created when the libhttpd.dll shared library is compiled. You + may also have to change the compiler settings to ensure that + the Apache header files are correctly located. You can find + this library in your server root's modules directory. It is + best to grab an existing module .dsp file from the tree to + assure the build environment is configured correctly, or + alternately compare the compiler and link options to your + .dsp.

+ +

This should create a DLL version of your module. Now simply + place it in the modules directory of your server + root, and use the LoadModule + directive to load it.

+ +
+
top
+

LoadFile Directive

+ + + + + + +
Description:Link in the named object file or library
Syntax:LoadFile filename [filename] ...
Context:server config
Status:Extension
Module:mod_so
+ +

The LoadFile directive links in the named object files or + libraries when the server is started or restarted; this is used + to load additional code which may be required for some module + to work. Filename is either an absolute path or + relative to ServerRoot.

+ +

For example:

+ +

LoadFile libexec/libxmlparse.so

+ + +
+
top
+

LoadModule Directive

+ + + + + + +
Description:Links in the object file or library, and adds to the list +of active modules
Syntax:LoadModule module filename
Context:server config
Status:Extension
Module:mod_so
+

The LoadModule directive links in the object file or library + filename and adds the module structure named + module to the list of active modules. Module + is the name of the external variable of type + module in the file, and is listed as the Module Identifier + in the module documentation. Example:

+ +

+ LoadModule status_module modules/mod_status.so +

+ +

loads the named module from the modules subdirectory of the + ServerRoot.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_so.html.ja.euc-jp b/docs/manual/mod/mod_so.html.ja.euc-jp new file mode 100644 index 00000000..5ac1c938 --- /dev/null +++ b/docs/manual/mod/mod_so.html.ja.euc-jp @@ -0,0 +1,190 @@ + + + +mod_so - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_so

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:µ¯Æ°»þ¤äºÆµ¯Æ°»þ¤Ë¼Â¹Ô¥³¡¼¥É¤È¥â¥¸¥å¡¼¥ë¤ò¥µ¡¼¥Ð¤Ë¥í¡¼¥É¤¹¤ë +
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:so_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_so.c
¸ß´¹À­:¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï Window ¤Ç¤Ï (¾ï¤Ë´Þ¤Þ¤ì¤Æ¤¤¤ë) Base +¥â¥¸¥å¡¼¥ë¤Ç¤¹
+

³µÍ×

+ + +

¤¤¤¯¤Ä¤«¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ç¤Ï¡¢¥µ¡¼¥Ð¤ÎºÆ¥³¥ó¥Ñ¥¤¥ë¤ò¤¹¤ëÂå¤ï¤ê¤Ë¡¢ + ¤³¤Î¥â¥¸¥å¡¼¥ë¤ò»ÈÍѤ·¤Æ + ưŪ¶¦Í­¥ª¥Ö¥¸¥§¥¯¥È + (DSO) µ¡¹½¤Ë¤è¤ê¡¢¼Â¹Ô»þ¤Ë Apache ¤Ë¥â¥¸¥å¡¼¥ë¤òÆɤ߹þ¤Þ¤»¤ë¤³¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£

+ +

Unix ¾å¤Ç¤Ï¡¢Æɤ߹þ¤Þ¤ì¤ë¥³¡¼¥É¤ÏÄ̾ï¤Ï¶¦Í­¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë + (ÉáÄÌ .so ¤È¤¤¤¦³ÈÄ¥»Ò¤¬ÉÕ¤¤¤Æ¤¤¤Þ¤¹) ¤«¤é¤Ç¤¹¡£ + Windows ¾å¤Ç¤Ï¤³¤Î¥â¥¸¥å¡¼¥ë¤Î³ÈÄ¥»Ò¤Ï .so ¤« .dll + ¤Ç¤¹¡£

+ +

·Ù¹ð

+

Apache 1.3 ¤Î¥â¥¸¥å¡¼¥ë¤òľÀÜ Apache 2.0 ¤Ç»È¤¦¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó + ¡½ ¥â¥¸¥å¡¼¥ë¤Ï Apache 2.0 ÍѤËưŪ¤Ë¥í¡¼¥É¤µ¤ì¤ë¤«¡¢ + ľÀÜÁȤ߹þ¤Þ¤ì¤ë¤¿¤á¤Ë½¤Àµ¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+
+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

¥È¥Ô¥Ã¥¯

+
    +
  • Windows ÍÑ¤Î¥í¡¼¥É²Äǽ¤Ê¥â¥¸¥å¡¼¥ë¤òºîÀ®¤¹¤ë
    • +
+
top
+
+

Windows ÍÑ¤Î¥í¡¼¥É²Äǽ¤Ê¥â¥¸¥å¡¼¥ë¤òºîÀ®¤¹¤ë

+ +

Ãí

+

Apache 1.3.15 ¤È 2.0 ¤È¤Ç Windows ¤Î¥â¥¸¥å¡¼¥ë̾¤Î·Á¼°¤ÏÊѹ¹¤µ¤ì¤Þ¤·¤¿ + ¡½ ¥â¥¸¥å¡¼¥ë¤Ï mod_foo.so ¤È¤¤¤¦Ì¾Á°¤Ë¤Ê¤ê¤Þ¤·¤¿¡£

+ +

¤Þ¤À mod_so ¤Ç ApacheModuleFoo.dll ¤È¤¤¤¦Ì¾Á°¤Î¥â¥¸¥å¡¼¥ë¤â + ¥í¡¼¥É¤µ¤ì¤Þ¤¹¤¬¡¢¿·¤·¤¤Ì¾Á°¤ÎÉÕ¤±Êý¤ò»È¤¦Êý¤¬¹¥¤Þ¤ì¤Þ¤¹¡£¥â¥¸¥å¡¼¥ë¤ò + 2.0 ÍѤ˰ܿ¢¤·¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢2.0 ¤Î½¬´·¤Ë¹ç¤¦¤è¤¦¤Ë̾Á°¤ò + ½¤Àµ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Apache ¤Î¥â¥¸¥å¡¼¥ë API ¤Ï UNIX ¤È Windows ´Ö¤Ç¤ÏÊѹ¹¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£ + ¿¤¯¤Î¥â¥¸¥å¡¼¥ë¤ÏÁ´¤¯Êѹ¹¤Ê¤·¡¢¤â¤·¤¯¤Ï´Êñ¤ÊÊѹ¹¤Ë¤è¤ê Windows + ¤Ç¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£¤¿¤À¤·¡¢¤½¤ì°Ê³°¤Î Windows ¤Ë¤Ï̵¤¤ Unix + ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¡¼¤Îµ¡Ç½¤Ë°Í¸¤·¤¿¥â¥¸¥å¡¼¥ë¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£

+ +

¥â¥¸¥å¡¼¥ë¤¬¼ÂºÝ¤ËÆ°ºî¤¹¤ë¤È¤­¤Ï¡¢ + Æó¤Ä¤ÎÊýË¡¤Î¤É¤Á¤é¤«¤Ç¥µ¡¼¥Ð¤ËÄɲ乤뤳¤È¤¬¤Ç¤­¤Þ¤¹¡£¤Þ¤º¡¢Unix + ¤ÈƱÍͤ˥µ¡¼¥Ð¤Ë¥³¥ó¥Ñ¥¤¥ë¤·¤ÆÁȤ߹þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Windows + ÍѤΠApache ¤Ï Unix ÍѤΠApache ¤Ë¤¢¤ë Configure + ¥×¥í¥°¥é¥à¤¬¤¢¤ê¤Þ¤»¤ó¤Î¤Ç¡¢¥â¥¸¥å¡¼¥ë¤Î¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤ò + ApacheCore ¥×¥í¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ËÄɲä·¡¢¥·¥ó¥Ü¥ë¤ò + os\win32\modules.c ¥Õ¥¡¥¤¥ë¤ËÄɲ乤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

Æó¤ÄÌܤϥ⥸¥å¡¼¥ë¤ò DLL ¤È¤·¤Æ¥³¥ó¥Ñ¥¤¥ë¤¹¤ëÊýË¡¤Ç¤¹¡£ + DLL ¤Ï¶¦Í­¥é¥¤¥Ö¥é¥ê¤Ç¡¢¼Â¹Ô»þ¤Ë + LoadModule + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¥µ¡¼¥Ð¤ËÆɤ߹þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤é¤Î¥â¥¸¥å¡¼¥ë + DLL ¤Ï¤½¤Î¤Þ¤ÞÇÛÉÛ¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¡¢¥µ¡¼¥Ð¤òºÆ¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤³¤È¤Ê¤¯¡¢Windows + ÍѤΠApache ¤Î¤¹¤Ù¤Æ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ç¼Â¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¥â¥¸¥å¡¼¥ë DLL ¤òºîÀ®¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ + ¥â¥¸¥å¡¼¥ë¤ÎºîÀ®¤Ë¾®¤µ¤ÊÊѹ¹¤ò¹Ô¤Ê¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£ + ¤Ä¤Þ¤ê¡¢¥â¥¸¥å¡¼¥ë¤Î¥ì¥³¡¼¥É (¤³¤ì¤Ï¸å¤ÇºîÀ®¤µ¤ì¤Þ¤¹¡£ + °Ê²¼¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤) ¤¬ DLL ¤«¤é¥¨¥¯¥¹¥Ý¡¼¥È¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤³¤ì¤ò¹Ô¤Ê¤¦¤Ë¤Ï¡¢AP_MODULE_DECLARE_DATA (Apache + ¤Î¥Ø¥Ã¥À¥Õ¥¡¥¤¥ë¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹) ¤ò¥â¥¸¥å¡¼¥ë¤Î¥â¥¸¥å¡¼¥ë¥ì¥³¡¼¥É + ÄêµÁ¤ÎÉôʬ¤ËÄɲ䷤Ƥ¯¤À¤µ¤¤¡£¤¿¤È¤¨¤Ð¡¢¥â¥¸¥å¡¼¥ë¤Ë

+

+ module foo_module; +

+ +

¤¬¤¢¤ë¤È¤¹¤ë¤È¡¢¤½¤ì¤ò¼¡¤Î¤â¤Î¤ÇÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£

+

+ module AP_MODULE_DECLARE_DATA foo_module; +

+ +

Unix ¾å¤Ç¤â¤³¤Î¥â¥¸¥å¡¼¥ë¤ò + Êѹ¹Ìµ¤·¤Ç»È¤¤Â³¤±¤é¤ì¤ë¤è¤¦¤Ë¡¢¤³¤Î¥Þ¥¯¥í¤Ï Windows + ¾å¤Ç¤Î¤ß¸úÎϤò»ý¤Á¤Þ¤¹¡£.DEF + ¥Õ¥¡¥¤¥ë¤ÎÊý¤òÎɤ¯ÃΤäƤ¤¤ë¤È¤¤¤¦¾ì¹ç¤Ï¡¢ + Âå¤ï¤ê¤Ë¤½¤ì¤ò»È¤Ã¤Æ¥â¥¸¥å¡¼¥ë¥ì¥³¡¼¥É¤ò + ¥¨¥¯¥¹¥Ý¡¼¥È¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+

¤µ¤¢¡¢¤¢¤Ê¤¿¤Î¥â¥¸¥å¡¼¥ë¤Î DLL ¤òºîÀ®¤·¤Þ¤·¤ç¤¦¡£¤³¤ì¤ò¡¢ + libhttpd.lib ¶¦Í­¥é¥¤¥Ö¥é¥ê¤¬¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤¿¤È¤­¤ËºîÀ®¤µ¤ì¤¿ + ibhttpd.lib ¥¨¥¯¥¹¥Ý¡¼¥È¥é¥¤¥Ö¥é¥ê¤È¥ê¥ó¥¯¤·¤Æ¤¯¤À¤µ¤¤¡£¤³¤Î»þ¤Ë¡¢ + Apache ¤Î¥Ø¥Ã¥À¥Õ¥¡¥¤¥ë¤¬Àµ¤·¤¤°ÌÃ֤ˤ¢¤ë¤è¤¦¤Ë¡¢ + ¥³¥ó¥Ñ¥¤¥é¤ÎÀßÄê¤òÊѤ¨¤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤³¤Î¥é¥¤¥Ö¥é¥ê¤Ï¥µ¡¼¥Ð¥ë¡¼¥È¤Î modules ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ê¤Þ¤¹¡£ + ¥Ó¥ë¥É´Ä¶­¤¬Àµ¤·¤¯ÀßÄꤵ¤ì¤ë¤è¤¦¤Ë¡¢´û¸¤Î¥â¥¸¥å¡¼¥ëÍѤΠ.dsp ¤ò + ¼è¤Ã¤Æ¤¯¤ë¤Î¤¬°ìÈÖÎɤ¤¤Ç¤·¤ç¤¦¡£¤â¤·¤¯¤Ï¡¢¤¢¤Ê¤¿¤Î .dsp ¤È + ¥³¥ó¥Ñ¥¤¥é¤È¥ê¥ó¥¯¤Î¥ª¥×¥·¥ç¥ó¤òÈæ³Ó¤¹¤ë¡¢¤È¤¤¤¦¤â¤Î¤Ç¤âÎɤ¤¤Ç¤¹¡£

+ +

¤³¤ì¤Ç DLL ÈǤΥ⥸¥å¡¼¥ë¤¬ºîÀ®¤µ¤ì¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£ + ¥µ¡¼¥Ð¥ë¡¼¥È¤Î modules + ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥â¥¸¥å¡¼¥ë¤òÃÖ¤¤¤Æ¡¢ + LoadModule + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤ÆÆɤ߹þ¤ó¤Ç¤¯¤À¤µ¤¤¡£

+
+
top
+

LoadFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:»ØÄꤵ¤ì¤¿¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ä¥é¥¤¥Ö¥é¥ê¤ò¥ê¥ó¥¯¤¹¤ë
¹½Ê¸:LoadFile filename [filename] ...
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_so
+ +

LoadFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥µ¡¼¥Ð¤¬µ¯Æ°¤µ¤ì¤¿¤È¤­¤äºÆµ¯Æ°¤µ¤ì¤¿¤È¤­¤Ë¡¢ + »ØÄꤵ¤ì¤¿¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ä¥é¥¤¥Ö¥é¥ê¤ò¥ê¥ó¥¯¤·¤Þ¤¹¡£ + ¤³¤ì¤Ï¥â¥¸¥å¡¼¥ë¤¬Æ°ºî¤¹¤ë¤¿¤á¤ËɬÍפˤʤ뤫¤â¤·¤ì¤Ê¤¤ÄɲäΠ+ ¥³¡¼¥É¤òÆɤ߹þ¤à¤¿¤á¤Ë»ÈÍѤµ¤ì¤Þ¤¹¡£Filename ¤ÏÀäÂХѥ¹¤«¡¢ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤Ç¤¹¡£

+ +

Îã:

+ +

LoadFile libexec/libxmlparse.so

+ + +
+
top
+

LoadModule ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ä¥é¥¤¥Ö¥é¥ê¤ò¥ê¥ó¥¯¤·¡¢»ÈÍѥ⥸¥å¡¼¥ë¤Î +¥ê¥¹¥È¤ËÄɲ乤ë
¹½Ê¸:LoadModule module filename
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_so
+ +

LoadModule ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï filename + ¤È¤¤¤¦¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ª¤è¤Ó¥é¥¤¥Ö¥é¥ê¤ò¥ê¥ó¥¯¤·¡¢module + ¤È¤¤¤¦Ì¾Á°¤Î¥â¥¸¥å¡¼¥ë¤Î¹½Â¤¤ò¥¢¥¯¥Æ¥£¥Ö¤Ê¥â¥¸¥å¡¼¥ë¤Î¥ê¥¹¥È¤ËÄɲä·¤Þ¤¹¡£ + Module ¤Ï¥Õ¥¡¥¤¥ëÃæ¤Î module + ·¿¤Î³°ÉôÊÑ¿ô¤Î̾Á°¤Ç¡¢¥â¥¸¥å¡¼¥ë¤Î¥É¥­¥å¥á¥ó¥È¤Ë + ¥â¥¸¥å¡¼¥ë¼±Ê̻ҤȤ·¤Æ½ñ¤«¤ì¤Æ¤¤¤ë¤â¤Î¤Ç¤¹¡£Îã :

+ +

+ LoadModule status_module modules/mod_status.so +

+ +

¤³¤ì¤Ï ServerRoot ¤Î modules ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤«¤é»ØÄꤵ¤ì¤¿Ì¾Á°¤Î + ¥â¥¸¥å¡¼¥ë¤ò¥í¡¼¥É¤·¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_so.html.ko.euc-kr b/docs/manual/mod/mod_so.html.ko.euc-kr new file mode 100644 index 00000000..a30e21fe --- /dev/null +++ b/docs/manual/mod/mod_so.html.ko.euc-kr @@ -0,0 +1,174 @@ + + + +mod_so - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_so

+
+

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

+
+ + + + +
¼³¸í:½ÃÀÛÇÒ¶§ ȤÀº Àç½ÃÀÛÇÒ¶§ ½ÇÇà°¡´ÉÇÑ ÄÚµå¿Í ¸ðµâÀ» +¼­¹ö·Î ÀоîµéÀδÙ
»óÅÂ:Extension
¸ðµâ¸í:so_module
¼Ò½ºÆÄÀÏ:mod_so.c
Áö¿ø:À©µµ¿ìÁî¿¡¼­ (Ç×»ó Æ÷ÇÔÇÏ´Â) Base ¸ðµâÀÌ´Ù.
+

¿ä¾à

+ + +

¸î¸î ¿î¿µÃ¼Á¦¿¡¼­ ¾ÆÆÄÄ¡´Â µ¿Àû°øÀ¯°´Ã¼ + (DSO) ±â¼úÀ» »ç¿ëÇÏ¿© ¼­¹ö¸¦ ´Ù½Ã ÄÄÆÄÀÏÇÏÁö ¾Ê°íµµ ½ÇÇàÁß¿¡ + ¸ðµâÀ» ÀоîµéÀÏ ¼ö ÀÖ´Ù.

+ +

ÀоîµéÀÏ ÄÚµå´Â, À¯´Ð½º¿¡¼­´Â (.so È®ÀåÀÚ¸¦ + °¡Áø) ÀϹÝÀûÀÎ °øÀ¯°´Ã¼ÆÄÀÏÀÌ°í, À©µµ¿ìÁî¿¡¼­´Â .so + ȤÀº .dll È®ÀåÀÚ¸¦ °¡Áø´Ù.

+ +

°æ°í

+

¾ÆÆÄÄ¡ 1.3 ¸ðµâÀ» ¾ÆÆÄÄ¡ 2.0¿¡¼­ »ç¿ëÇÒ ¼ö ¾ø´Ù. + ¾ÆÆÄÄ¡ 2.0ÀÌ µ¿ÀûÀ¸·Î ÀоîµéÀ̰ųª ¾ÆÆÄÄ¡¿Í °°ÀÌ ÄÄÆÄÀÏÇÏ·Á¸é + ¸ðµâÀ» ¼öÁ¤ÇØ¾ß ÇÑ´Ù.

+
+
+ +
top
+
+

À©µµ¿ìÁî¿¡¼­ ÀоîµéÀÏ ¸ðµâ ¸¸µé±â

+ +

ÁÖÀÇ

+

À©µµ¿ìÁîÀÇ ¸ðµâ¸í Çü½ÄÀº ¾ÆÆÄÄ¡ 1.3.15¿Í 2.0¿¡¼­ º¯°æµÇ¾ú´Ù. + ¸ðµâ¸íÀº ÀÌÁ¦ mod_foo.so½ÄÀÌ´Ù.

+ +

mod_so´Â ¾ÆÁ÷µµ ApacheModuleFoo.dll ½ÄÀÇ ¸ðµâÀ» ÀоîµéÀÏ + ¼ö ÀÖÁö¸¸, »õ·Î¿î À̸§ ±ÔÄ¢À» ¼±È£ÇÑ´Ù. ¸ðµâÀ» 2.0¿¡ ¸Â°Ô + ¼öÁ¤ÇÑ´Ù¸é À̸§À» 2.0 ±ÔÄ¢¿¡ ¾Ë¸Â°Ô °íÄ¡±æ ¹Ù¶õ´Ù.

+ +

¾ÆÆÄÄ¡ ¸ðµâ API´Â À¯´Ð½º ¹öÀüÀ̰ųª À©µµ¿ìÁî ¹öÀüÀ̰ųª + °°´Ù. ¸î¸î API´Â À©µµ¿ìÁî¿¡ ¾ø´Â À¯´Ð½º ±¸Á¶¿¡ ÀÇÁ¸Çϱ⶧¹®¿¡ + »ç¿ëÇÒ ¼ö ¾øÁö¸¸, À¯´Ð½º¿¡¼­ ½ÇÇàµÇ´Â ¸¹Àº ¸ðµâÀ» ¼öÁ¤¾øÀÌ + ȤÀº Á¶±Ý ¼öÁ¤ÇÏ¿© À©µµ¿ìÁî¿¡¼­ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

¸ðµâÀº µÎ°¡Áö ¹æ¹ýÀ¸·Î ¼­¹ö¿¡ Ãß°¡ÇÒ ¼ö ÀÖ´Ù. À¯´Ð½º¿¡¼­´Â + ¸ðµâÀ» ¼­¹ö¿Í °°ÀÌ ÄÄÆÄÀÏÇÒ ¼ö ÀÖ´Ù. À©µµ¿ìÁî¿ë ¾ÆÆÄÄ¡´Â + À¯´Ð½º¿Í ´Þ¸® Configure ÇÁ·Î±×·¥ÀÌ ¾ø±â¶§¹®¿¡ + ¸ðµâÀÇ ¼Ò½ºÆÄÀÏÀ» ApacheCore ÇÁ·ÎÁ§Æ® ÆÄÀÏ¿¡ Ãß°¡ÇÏ°í, ½Éº¼À» + os\win32\modules.c ÆÄÀÏ¿¡ Ãß°¡ÇØ¾ß ÇÑ´Ù.

+ +

µÎ¹ø° ¹æ¹ýÀº ¸ðµâÀ» ¼­¹ö°¡ + LoadModule Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© ½ÃÀÛÇÒ¶§ ÀоîµéÀÏ ¼ö ÀÖ´Â °øÀ¯¶óÀ̺귯¸® DLL·Î + ¸¸µå´Â °ÍÀÌ´Ù. ÀÌ ¸ðµâ DLLÀ» ¹èÆ÷ÇÏ¸é ¼­¹ö¸¦ ÀçÄÄÆÄÀÏÇÏÁö + ¾Ê°í ¾î¶² À©µµ¿ìÁî¿ë ¾ÆÆÄÄ¡¿¡¼­µµ ¸ðµâÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù.

+ +

¸ðµâ DLLÀ» ¸¸µé±âÀ§Çؼ­´Â ¸ðµâÀÇ ¼Ò½ºÆÄÀÏÀ» Á¶±Ý ¼öÁ¤ÇØ¾ß + ÇÑ´Ù. DLLÀº module record¸¦ exportÇØ¾ß ÇÑ´Ù. (¾Æ·¡ Âü°í) + À̸¦ À§ÇØ ¸ðµâÀÇ module record Á¤ÀÇ¿¡ (¾ÆÆÄÄ¡ Çì´õÆÄÀÏ¿¡ + Á¤ÀǵÈ) AP_MODULE_DECLARE_DATA¸¦ Ãß°¡ÇÑ´Ù. + ¿¹¸¦ µé¾î, ´ÙÀ½°ú °°Àº ¸ðµâÀÌ ÀÖ´Ù¸é:

+ +

+ module foo_module; +

+ +

´ÙÀ½°ú °°ÀÌ ¼öÁ¤ÇÑ´Ù:

+

+ module AP_MODULE_DECLARE_DATA foo_module; +

+ +

ÀÌ ºÎºÐÀº À©µµ¿ìÁî¿¡¼­¸¸ »ç¿ëÇϱ⶧¹®¿¡ º¯°æÇÏ¿©µµ À¯´Ð½º¿¡¼­ + ¼Ò½º¸¦ ±×´ë·Î »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¶Ç, .DEF ÆÄÀÏ¿¡ + Àͼ÷ÇÏ´Ù¸é ´ë½Å ÀÌ ÆÄÀÏÀ» »ç¿ëÇÏ¿© module record¸¦ exportÇÒ + ¼öµµ ÀÖ´Ù.

+ +

ÀÌÁ¦ ¸ðµâÀ» Æ÷ÇÔÇÑ DLLÀ» ¸¸µç´Ù. À̸¦ °øÀ¯¶óÀ̺귯¸® + libhttpd.dllÀ» ÄÄÆÄÀÏÇÒ¶§ ¸¸µç libhttpd.lib export ¶óÀ̺귯¸®¿Í + ¸µÅ©ÇÑ´Ù. ¾ÆÆÄÄ¡ Çì´õÆÄÀÏÀ» ¿Ã¹Ù·Î ãµµ·Ï ÄÄÆÄÀÏ·¯ ¼³Á¤À» + ¼öÁ¤ÇØ¾ß ÇÒÁöµµ ¸ð¸¥´Ù. ¼­¹öÀÇ modules µð·ºÅ丮¿¡¼­ ÀÌ + ¶óÀ̺귯¸®¸¦ ãÀ» ¼ö ÀÖ´Ù. ÄÄÆÄÀÏȯ°æÀ» ¿Ã¹Ù·Î ¼³Á¤ÇϱâÀ§ÇØ + ±âÁ¸ ¸ðµâÀÇ .dsp ÆÄÀÏÀ» °¡Á®´Ù ¾²°Å³ª Á÷Á¢ ¸¸µç .dsp¿Í + ÄÄÆÄÀÏ·¯/¸µÄ¿ ¿É¼ÇÀ» ºñ±³ÇÏ´Â °ÍÀÌ ÁÁ´Ù.

+ +

ÀÌÁ¦ ¸ðµâÀ» DLL·Î ¸¸µç´Ù. ÀÌ°ÍÀ» ¼­¹öÀÇ + modules µð·ºÅ丮¿¡ µÎ°í, + LoadModule Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ÀоîµéÀδÙ.

+ +
+
top
+

LoadFile Áö½Ã¾î

+ + + + + + +
¼³¸í:ÁöÁ¤ÇÑ ¸ñÀûÆÄÀÏÀ̳ª ¶óÀ̺귯¸®¸¦ ÀоîµéÀδÙ
¹®¹ý:LoadFile filename [filename] ...
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Extension
¸ðµâ:mod_so
+ +

LoadFile Áö½Ã¾î´Â ¼­¹ö°¡ ½ÃÀÛÇϰųª Àç½ÃÀÛÇÒ¶§ ÁöÁ¤ÇÑ + ¸ñÀûÆÄÀÏÀ̳ª ¶óÀ̺귯¸®¸¦ ÀоîµéÀδÙ(link in). ÀÌ Áö½Ã¾î´Â + ¾î¶² ¸ðµâÀÌ µ¿ÀÛÇϱâÀ§ÇØ ÇÊ¿äÇÑ Äڵ带 Ãß°¡·Î ÀоîµéÀ϶§ + »ç¿ëÇÑ´Ù. FilenameÀº Àý´ë°æ·ÎÀ̰ųª ServerRoot¿¡ ´ëÇÑ »ó´ë°æ·ÎÀÌ´Ù.

+ +

¿¹¸¦ µé¾î:

+ +

LoadFile libexec/libxmlparse.so

+ + +
+
top
+

LoadModule Áö½Ã¾î

+ + + + + + +
¼³¸í:¸ñÀûÆÄÀÏÀ̳ª ¶óÀ̺귯¸®¸¦ ÀоîµéÀÌ°í, »ç¿ë°¡´ÉÇÑ +¸ðµâ ¸ñ·Ï¿¡ Ãß°¡ÇÑ´Ù
¹®¹ý:LoadModule module filename
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Extension
¸ðµâ:mod_so
+

LoadModule Áö½Ã¾î´Â ¸ñÀûÆÄÀÏ È¤Àº ¶óÀ̺귯¸® filenameÀ» + ÀоîµéÀÌ°í, »ç¿ë°¡´ÉÇÑ ¸ðµâ ¸ñ·Ï¿¡ moduleÀ̶ó´Â + ¸ðµâ ±¸Á¶Ã¼¸¦ Ãß°¡ÇÑ´Ù. ModuleÀº ÆÄÀÏÀÇ + module ÀÚ·áÇü ¿ÜºÎº¯¼ö¸íÀ̸ç, ¸ðµâ ¹®¼­ÀÇ ¸ðµâ¸í¿¡ + ³ª¿Â´Ù. ¿¹¸¦ µé¸é:

+ +

+ LoadModule status_module modules/mod_status.so +

+ +

ServerRootÀÇ modules ÇÏÀ§µð·ºÅ丮¿¡¼­ ÁöÁ¤ÇÑ ¸ðµâÀ» ÀоîµéÀδÙ.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_speling.html b/docs/manual/mod/mod_speling.html new file mode 100644 index 00000000..bcda93f5 --- /dev/null +++ b/docs/manual/mod/mod_speling.html @@ -0,0 +1,11 @@ +URI: mod_speling.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_speling.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_speling.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_speling.html.en b/docs/manual/mod/mod_speling.html.en new file mode 100644 index 00000000..a9f754b4 --- /dev/null +++ b/docs/manual/mod/mod_speling.html.en @@ -0,0 +1,128 @@ + + + +mod_speling - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_speling

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Attempts to correct mistaken URLs that +users might have entered by ignoring capitalization and by +allowing up to one misspelling
Status:Extension
Module Identifier:speling_module
Source File:mod_speling.c
+

Summary

+ + +

Requests to documents sometimes cannot be served by the core + apache server because the request was misspelled or + miscapitalized. This module addresses this problem by trying to + find a matching document, even after all other modules gave up. + It does its work by comparing each document name in the + requested directory against the requested document name + without regard to case, and allowing + up to one misspelling (character insertion / + omission / transposition or wrong character). A list is built + with all document names which were matched using this + strategy.

+ +

If, after scanning the directory,

+ +
    +
  • no matching document was found, Apache will proceed as + usual and return a "document not found" error.
    • + +
  • only one document is found that "almost" matches the + request, then it is returned in the form of a redirection + response.
    • + +
  • more than one document with a close match was found, then + the list of the matches is returned to the client, and the + client can select the correct candidate.
    • +
+ +
+

Directives

+ +
+ +
top
+

CheckSpelling Directive

+ + + + + + + + + +
Description:Enables the spelling +module
Syntax:CheckSpelling on|off
Default:CheckSpelling Off
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Extension
Module:mod_speling
Compatibility:CheckSpelling was available as a separately available +module for Apache 1.1, but was limited to miscapitalizations. As +of Apache 1.3, it is part of the Apache distribution. Prior to Apache +1.3.2, the CheckSpelling directive was only available in the +"server" and "virtual host" contexts.
+

This directive enables or disables the spelling module. When + enabled, keep in mind that

+ +
    +
  • the directory scan which is necessary for the spelling + correction will have an impact on the server's performance + when many spelling corrections have to be performed at the + same time.
    • + +
  • the document trees should not contain sensitive files + which could be matched inadvertently by a spelling + "correction".
    • + +
  • the module is unable to correct misspelled user names (as + in http://my.host/~apahce/), just file names or + directory names.
    • + +
  • spelling corrections apply strictly to existing files, so + a request for the <Location /status> may + get incorrectly treated as the negotiated file + "/stats.html".
    • +
+ + +

mod_speling should not be enabled in DAV + enabled directories, because it will try to "spell fix" newly created + resource names against existing filenames, e.g., when trying to upload + a new document doc43.html it might redirect to an existing + document doc34.html, which is not what was intended. +

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_speling.html.ja.euc-jp b/docs/manual/mod/mod_speling.html.ja.euc-jp new file mode 100644 index 00000000..e78f7b7e --- /dev/null +++ b/docs/manual/mod/mod_speling.html.ja.euc-jp @@ -0,0 +1,127 @@ + + + +mod_speling - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_speling

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:¥æ¡¼¥¶¤¬ÆþÎϤ·¤¿¤Ç¤¢¤í¤¦´Ö°ã¤Ã¤¿ URL ¤ò¡¢ +Âçʸ»ú¾®Ê¸»ú¤Î¶èÊ̤ò̵»ë¤¹¤ë¤³¤È¤È°ì¤Ä°Ê²¼¤ÎÄÖ¤ê´Ö°ã¤¤¤òµöÍƤ¹¤ë¤³¤È¤Ç +½¤Àµ¤ò»î¤ß¤ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:speling_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_speling.c
+

³µÍ×

+ + +

¥ê¥¯¥¨¥¹¥È¤ÎÄ֤꤬´Ö°ã¤Ã¤Æ¤¤¤¿¤ê¡¢ + Âçʸ»ú¾®Ê¸»ú¤¬°ã¤Ã¤Æ¤¤¤¿¤ê¤¹¤ë¤¿¤á¤Ë¡¢Apache ¤Î¥³¥¢¥µ¡¼¥Ð¤¬ + ¥É¥­¥å¥á¥ó¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ø¤Î±þÅú¤òÀµ¤·¤¯Ä󶡤Ǥ­¤Ê¤¤¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢Â¾¤Î¤¹¤Ù¤Æ¤Î¥â¥¸¥å¡¼¥ë¤¬¤¢¤­¤é¤á¤¿¸å¤Ç¤¢¤Ã¤¿¤È¤·¤Æ¤â¡¢ + ¥ê¥¯¥¨¥¹¥È¤Ë¹ç¤¦¥É¥­¥å¥á¥ó¥È¤ò¸«¤Ä¤±¤è¤¦¤È¤¹¤ë¤³¤È¤Ë¤è¤ê¤³¤ÎÌäÂê¤Î + ²ò·è¤ò»î¤ß¤Þ¤¹¡£¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë + ¤½¤ì¤¾¤ì¤Î¥É¥­¥å¥á¥ó¥È¤Î̾Á°¤È¡¢¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤Î̾Á°¤È¤ò + Âçʸ»ú¾®Ê¸»ú¤Î¶èÊ̤ò̵»ë¤·¡¢°ìʸ»ú¤Þ¤Ç¤Î + ÄÖ¤ê¤Î´Ö°ã¤¤ (ʸ»ú¤ÎÁÞÆþ/¾Êά/Îٹ礦ʸ»ú¤ÎÃÖ´¹¡¢´Ö°ã¤Ã¤¿Ê¸»ú) + ¤òµö²Ä¤·¤ÆÈæ³Ó¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢ÌÜŪ¤òãÀ®¤·¤è¤¦¤È¤·¤Þ¤¹¡£ + ¤³¤ÎÊýË¡¤Ç¥ê¥¯¥¨¥¹¥È¤Ë¹ç¤¦¥É¥­¥å¥á¥ó¥È¤Î°ìÍ÷¤¬ºîÀ®¤µ¤ì¤Þ¤¹¡£

+ +

¥Ç¥£¥ì¥¯¥È¥ê¤ò¥¹¥­¥ã¥ó¤·¤¿¸å¤Ë¡¢

+ +
    +
  • ŬÀڤʥɥ­¥å¥á¥ó¥È¤¬¸«¤Ä¤«¤é¤Ê¤«¤Ã¤¿¾ì¹ç¡¢ + Apache ¤Ï¤¤¤Ä¤â¤ÈƱ¤¸¤è¤¦¤Ë½èÍý¤ò¤·¡¢ + ¡Ö¥É¥­¥å¥á¥ó¥È¤¬¸«¤Ä¤«¤é¤Ê¤¤¡×¤È¤¤¤¦¥¨¥é¡¼¤òÊÖ¤·¤Þ¤¹¡£
    • + +
  • ¥ê¥¯¥¨¥¹¥È¤Ë¡Ö¤Û¤È¤ó¤É¡×¹ç¤¦¥É¥­¥å¥á¥ó¥È¤¬°ì¤Ä¤À¤±¸«¤Ä¤«¤Ã¤¿¾ì¹ç¡¢ + ¤½¤ì¤¬¥ê¥À¥¤¥ì¥¯¥È±þÅú¤È¤·¤ÆÊÖ¤µ¤ì¤Þ¤¹¡£
    • + +
  • ¤è¤¯»÷¤¿¥É¥­¥å¥á¥ó¥È¤¬Ê£¿ô¸«¤Ä¤«¤Ã¤¿¾ì¹ç¡¢ + ¤½¤Î¥ê¥¹¥È¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤µ¤ì¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤¬Àµ¤·¤¤¸õÊä¤òÁªÂò¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
    • +
+ +
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +
+ +
top
+

CheckSpelling ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + + +
ÀâÌÀ:spelling ¥â¥¸¥å¡¼¥ë¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë¤¹¤ë
¹½Ê¸:CheckSpelling on|off
¥Ç¥Õ¥©¥ë¥È:CheckSpelling Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:Options
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_speling
¸ß´¹À­:CheckSpelling ¤Ï Apache 1.1 ¤Ç¤ÏÊÌÇÛÉۤΥ⥸¥å¡¼¥ë¤Ç¡¢ +Âçʸ»ú¾®Ê¸»ú¤Î´Ö°ã¤¤¤Î¤ß¤Îµ¡Ç½¤Ç¤·¤¿¡£Apache 1.3 ¤Ç Apache ¤ÎÇÛÉÛ¤Ë +´Þ¤Þ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£Apache 1.3.2 ¤è¤êÁ°¤Ç¤Ï CheckSpelling +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡Ö¥µ¡¼¥Ð¡×¤È¡Ö¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¡×¥³¥ó¥Æ¥­¥¹¥È¤Ç¤Î¤ß +»ÈÍѲÄǽ¤Ç¤·¤¿
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÄÖ¤êÍѤΥ⥸¥å¡¼¥ë¤ò»ÈÍѤ¹¤ë¤«¤É¤¦¤«¤ò + ·è¤á¤Þ¤¹¡£»ÈÍÑ»þ¤Ë¤Ï¡¢°Ê²¼¤Î¤³¤È¤ò³Ð¤¨¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤

+ +
    +
  • Ʊ»þ¤Ë¤¿¤¯¤µ¤ó¤ÎÄÖ¤ê¤ÎÄûÀµ¤ò¹Ô¤Ê¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤È¤­¤Ï¡¢ + ¤½¤Î¤¿¤á¤Ë¹Ô¤Ê¤ï¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Î¥¹¥­¥ã¥ó¤¬¥µ¡¼¥Ð¤ÎÀ­Ç½¤Ë + ±Æ¶Á¤òÍ¿¤¨¤Þ¤¹¡£
    • + +
  • ¥É¥­¥å¥á¥ó¥È¤ÎÃæ¤ËÄÖ¤ê¤Î¡ÖÄûÀµ¡×¤Ë¤è¤ê + °Õ¿Þ¤»¤º¹ç¤Ã¤Æ¤·¤Þ¤¦¤è¤¦¤Ê½ÅÍפʥե¡¥¤¥ë¤¬¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ +
    • + +
  • ¥â¥¸¥å¡¼¥ë¤Ï¥æ¡¼¥¶Ì¾¤ÎÄÖ¤ê¤Î´Ö°ã¤¤ + (http://my.host/~apahce/ ¤Î¤è¤¦¤Ë) + ¤òÄûÀµ¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ + ÄûÀµ¤Ç¤­¤ë¤Î¤Ï¥Õ¥¡¥¤¥ë̾¤È¥Ç¥£¥ì¥¯¥È¥ê̾¤À¤±¤Ç¤¹¡£
    • + +
  • ÄÖ¤ê¤ÎÄûÀµ¤Ï¸ºß¤¹¤ë¥Õ¥¡¥¤¥ë¤Ë¸·Ì©¤ËŬÍѤµ¤ì¤Þ¤¹¤Î¤Ç¡¢ + <Location /status> + ¤Ï¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤Î·ë²Ì¤Î¥Õ¥¡¥¤¥ë "/stats.html" + ¤È¤·¤Æ´Ö°ã¤Ã¤Æ°·¤ï¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
    • +
+ + +

DAV ¤¬Í­¸ú¤Ê¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤Ï + mod_speling ¤ÏÍ­¸ú¤Ë¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ + ¿·¤·¤¯ºîÀ®¤·¤¿¥ê¥½¡¼¥¹Ì¾¤ò´û¤Ë¸ºß¤¹¤ë¥Õ¥¡¥¤¥ë̾¤Ë¡Ö½¤Àµ¡×¤·¤è¤¦¤È¤¹¤ë¡¢ + Î㤨¤Ð¡¢¿·µ¬¥É¥­¥å¥á¥ó¥È doc43.html ¤¬´û¤Ë¸ºß¤¹¤ë + doc34.html ¤Ë¥ê¥À¥¤¥ì¥¯¥È¤µ¤ì¤Æ¡¢ + ´üÂԤȤϰ㤦µóÆ°¤Ë¤Ê¤ë¤«¤é¤Ç¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_speling.html.ko.euc-kr b/docs/manual/mod/mod_speling.html.ko.euc-kr new file mode 100644 index 00000000..8837a347 --- /dev/null +++ b/docs/manual/mod/mod_speling.html.ko.euc-kr @@ -0,0 +1,118 @@ + + + +mod_speling - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_speling

+
+

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

+
+ + + +
¼³¸í:»ç¿ëÀÚ°¡ ´ë¼Ò¹®ÀÚ¸¦ À߸ø »ç¿ëÇϰųª ¸ÂÃã¹ýÀÌ Æ²¸®´Â +°ÍÀ» Çѹø±îÁö Çã¿ëÇÏ¿© À߸øµÈ URLÀ» °íÄ¡·Á°í ½ÃµµÇÑ´Ù
»óÅÂ:Extension
¸ðµâ¸í:speling_module
¼Ò½ºÆÄÀÏ:mod_speling.c
+

¿ä¾à

+ + +

Á¾Á¾ ¸ÂÃã¹ýÀÌ Æ²¸®°Å³ª ´ë¼Ò¹®ÀÚ¸¦ À߸ø »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡°¡ + ¹®¼­ ¿äûÀ» ¼­ºñ½ºÇÒ ¼ö ¾ø´Â °æ¿ì°¡ ÀÖ´Ù. ÀÌ ¸ðµâÀº ´Ù¸¥ + ¸ðµç ¸ðµâµéÀÌ Æ÷±âÇÑ ¿äû¿¡ ÇØ´çÇÏ´Â ¹®¼­¸¦ ã´Â´Ù. ¸ðµâÀº + ¿äûÇÑ µð·ºÅ丮 ¾È¿¡ ÀÖ´Â ¸ðµç ¹®¼­¸¦ ¿äûÇÑ ¹®¼­À̸§°ú + ´ë¼Ò¹®ÀÚ ±¸º°¾øÀÌ (¹®ÀÚ Ã·°¡ / »ý·« / ±³Ã¼ + ȤÀº À߸øµÈ ¹®ÀÚ ) ¸ÂÃã¹ýÀÌ Çѹø±îÁö Ʋ·Áµµ + ºÁÁÖ¸ç ºñ±³ÇÑ´Ù. ÀÌ·± ¹æ¹ýÀ¸·Î ¹®¼­¸ñ·ÏÀ» ¸¸µç´Ù.

+ +

µð·ºÅ丮¸¦ »ìÆ캻 ÈÄ¿¡,

+ +
    +
  • ¹®¼­¸¦ ãÁö¸øÇϸé, ¾ÆÆÄÄ¡´Â ÀϹÝÀûÀÎ "document not + found (¹®¼­¸¦ ãÀ» ¼ö ¾øÀ½)" ¿À·ù¸¦ ¹ÝȯÇÑ´Ù.
    • + +
  • ¿äû¿¡ "°ÅÀÇ" ÀÏÄ¡ÇÏ´Â ¹®¼­¸¦ Çϳª¸¸ ãÀº °æ¿ì, ±× + ¹®¼­·Î ¸®´ÙÀÌ·º¼Ç ÀÀ´äÀ» ÇÑ´Ù.
    • + +
  • ±ÙÁ¢ÇÑ ¹®¼­¸¦ ¿©·¯°³ ãÀº °æ¿ì, Ŭ¶óÀ̾ðÆ®°¡ ¿Ã¹Ù¸¥ + ¹®¼­¸¦ ¼±ÅÃÇÒ ¼ö ÀÖµµ·Ï ¹®¼­¸ñ·ÏÀ» º¸³½´Ù.
    • +
+ +
+

Áö½Ã¾îµé

+ +
+ +
top
+

CheckSpelling Áö½Ã¾î

+ + + + + + + + + +
¼³¸í:¸ÂÃã¹ý ¸ðµâÀ» »ç¿ëÇÑ´Ù
¹®¹ý:CheckSpelling on|off
±âº»°ª:CheckSpelling Off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:Options
»óÅÂ:Extension
¸ðµâ:mod_speling
Áö¿ø:¾ÆÆÄÄ¡ 1.1Àº CheckSpellingÀ» º°µµ·Î Á¦°øÇÏ¿´Áö¸¸, +´ë¼Ò¹®ÀÚ°¡ ´Ù¸¥ °æ¿ì¸¸À» ó¸®ÇÒ ¼ö ÀÖ¾ú´Ù. ¾ÆÆÄÄ¡ 1.3¿¡¼­ ¾ÆÆÄÄ¡ +¹èÆ÷º»ÀÇ ÀϺΰ¡ µÇ¾ú´Ù. ¾ÆÆÄÄ¡ 1.3.2 ÀÌÀü¿¡´Â +CheckSpelling Áö½Ã¾î¸¦ "ÁÖ¼­¹ö"¿Í "°¡»óÈ£½ºÆ®" +»ç¿ëÀå¼Ò¿¡¼­¸¸ »ç¿ëÇÒ ¼ö ÀÖ¾ú´Ù.
+

ÀÌ Áö½Ã¾î´Â ¸ÂÃã¹ý ¸ðµâÀÇ »ç¿ë¿©ºÎ¸¦ °áÁ¤ÇÑ´Ù. »ç¿ëÇÑ´Ù¸é + ´ÙÀ½À» ÁÖÀÇÇ϶ó

+ +
    +
  • ¸ÂÃã¹ý ±³Á¤À» À§ÇØ µð·ºÅ丮¸¦ »ìÆ캸´Â ÀÛ¾÷À» µ¿½Ã¿¡ + ¿©·¯¹ø ÇÒ °æ¿ì ¼­¹ö ¼º´É¿¡ ¿µÇâÀ» ÁØ´Ù.
    • + +
  • ¹®¼­Áß¿¡ ¸ÂÃã¹ý "±³Á¤"À¸·Î ¿ì¿¬È÷ º¸¿©Áú ¼ö ÀÖ´Â + ±â¹Ð¹®¼­°¡ ¾ø¾î¾ß ÇÑ´Ù.
    • + +
  • ¸ðµâÀº ÆÄÀϸí°ú µð·ºÅ丮¸í¸¸À» ±³Á¤ÇÒ ¼ö ÀÖÀ¸¸ç, + (http://my.host/~apahce/¿Í °°ÀÌ) ¸ÂÃã¹ýÀÌ + Ʋ¸° »ç¿ëÀÚ¸íÀ» ±³Á¤ÇÏÁö ¸øÇÑ´Ù.
    • + +
  • ¸ÂÃã¹ý ±³Á¤Àº Á¸ÀçÇÏ´Â ÆÄÀÏ¿¡¸¸ Àû¿ëµÈ´Ù. ±×·¡¼­ + <Location /status>¿¡ ´ëÇÑ ¿äûÀ» + ³»¿ëÇù»óÀ» °ÅÄ£ "/stats.html" ÆÄÀÏ·Î ¿ÀÀÎÇÒ + ¼ö ÀÖ´Ù.
    • +
+ + +

DAV¸¦ »ç¿ëÇÏ´Â µð·ºÅ丮¿¡ + mod_spelingÀ» »ç¿ëÇÏ¸é ¾ÈµÈ´Ù. ÀÌÀ¯´Â »õ·Î ¾÷·ÎµåÇÏ·Á´Â + doc43.html ¹®¼­¸¦ ¾û¶×ÇÏ°Ô ±âÁ¸ÀÇ + doc34.html ÆÄÀÏ·Î ¸®´ÙÀÌ·ºÆ®ÇÏ´Â µî, DAV°¡ + »õ·Î ¸¸µå´Â ¸®¼Ò½º¸íÀ» ±âÁ¸ÀÇ ÆÄÀϸíÀ¸·Î "¸ÂÃã¹ý ±³Á¤"À» + ½ÃµµÇϱ⠶§¹®ÀÌ´Ù. +

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_ssl.html b/docs/manual/mod/mod_ssl.html new file mode 100644 index 00000000..1b692ba6 --- /dev/null +++ b/docs/manual/mod/mod_ssl.html @@ -0,0 +1,3 @@ +URI: mod_ssl.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en new file mode 100644 index 00000000..26b9bc0a --- /dev/null +++ b/docs/manual/mod/mod_ssl.html.en @@ -0,0 +1,1722 @@ + + + +mod_ssl - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_ssl

+
+

Available Languages:  en 

+
+ + + +
Description:Strong cryptography using the Secure Sockets +Layer (SSL) and Transport Layer Security (TLS) protocols
Status:Extension
Module Identifier:ssl_module
Source File:mod_ssl.c
+

Summary

+ +

This module provides SSL v2/v3 and TLS v1 support for the Apache +HTTP Server. It was contributed by Ralf S. Engeschall based on his +mod_ssl project and originally derived from work by Ben Laurie.

+ +

This module relies on OpenSSL +to provide the cryptography engine.

+ +

Further details, discussion, and examples are provided in the +SSL documentation.

+
+ +
top
+
+

Environment Variables

+ +

This module provides a lot of SSL information as additional environment +variables to the SSI and CGI namespace. The generated variables are listed in +the table below. For backward compatibility the information can +be made available under different names, too. Look in the Compatibility chapter for details on the +compatibility variables.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Variable Name:Value Type:Description:
HTTPS flag HTTPS is being used.
SSL_PROTOCOL string The SSL protocol version (SSLv2, SSLv3, TLSv1)
SSL_SESSION_ID string The hex-encoded SSL session id
SSL_CIPHER string The cipher specification name
SSL_CIPHER_EXPORT string true if cipher is an export cipher
SSL_CIPHER_USEKEYSIZE number Number of cipher bits (actually used)
SSL_CIPHER_ALGKEYSIZE number Number of cipher bits (possible)
SSL_COMPRESS_METHOD string SSL compression method negotiated
SSL_VERSION_INTERFACE string The mod_ssl program version
SSL_VERSION_LIBRARY string The OpenSSL program version
SSL_CLIENT_M_VERSION string The version of the client certificate
SSL_CLIENT_M_SERIAL string The serial of the client certificate
SSL_CLIENT_S_DN string Subject DN in client's certificate
SSL_CLIENT_S_DN_x509 string Component of client's Subject DN
SSL_CLIENT_I_DN string Issuer DN of client's certificate
SSL_CLIENT_I_DN_x509 string Component of client's Issuer DN
SSL_CLIENT_V_START string Validity of client's certificate (start time)
SSL_CLIENT_V_END string Validity of client's certificate (end time)
SSL_CLIENT_V_REMAIN string Number of days until client's certificate expires
SSL_CLIENT_A_SIG string Algorithm used for the signature of client's certificate
SSL_CLIENT_A_KEY string Algorithm used for the public key of client's certificate
SSL_CLIENT_CERT string PEM-encoded client certificate
SSL_CLIENT_CERT_CHAIN_n string PEM-encoded certificates in client certificate chain
SSL_CLIENT_VERIFY string NONE, SUCCESS, GENEROUS or FAILED:reason
SSL_SERVER_M_VERSION string The version of the server certificate
SSL_SERVER_M_SERIAL string The serial of the server certificate
SSL_SERVER_S_DN string Subject DN in server's certificate
SSL_SERVER_S_DN_x509 string Component of server's Subject DN
SSL_SERVER_I_DN string Issuer DN of server's certificate
SSL_SERVER_I_DN_x509 string Component of server's Issuer DN
SSL_SERVER_V_START string Validity of server's certificate (start time)
SSL_SERVER_V_END string Validity of server's certificate (end time)
SSL_SERVER_A_SIG string Algorithm used for the signature of server's certificate
SSL_SERVER_A_KEY string Algorithm used for the public key of server's certificate
SSL_SERVER_CERT string PEM-encoded server certificate
+ +

x509 specifies a component of an X.509 DN; one of +C,ST,L,O,OU,CN,T,I,G,S,D,UID,Email. In Apache 2.1 and +later, x509 may also include a numeric _n +suffix. If the DN in question contains multiple attributes of the +same name, this suffix is used as an index to select a particular +attribute. For example, where the server certificate subject DN +included two OU fields, SSL_SERVER_S_DN_OU_0 and +SSL_SERVER_S_DN_OU_1 could be used to reference each.

+ +

SSL_CLIENT_V_REMAIN is only available in version 2.1 +and later.

+ +
top
+
+

Custom Log Formats

+ +

When mod_ssl is built into Apache or at least +loaded (under DSO situation) additional functions exist for the Custom Log Format of +mod_log_config. First there is an +additional ``%{varname}x'' +eXtension format function which can be used to expand any variables +provided by any module, especially those provided by mod_ssl which can +you find in the above table.

+

+For backward compatibility there is additionally a special +``%{name}c'' cryptography format function +provided. Information about this function is provided in the Compatibility chapter.

+

Example

+CustomLog logs/ssl_request_log \ + "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" +

+
+
top
+

SSLCACertificateFile Directive

+ + + + + + +
Description:File of concatenated PEM-encoded CA Certificates +for Client Auth
Syntax:SSLCACertificateFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the all-in-one file where you can assemble the +Certificates of Certification Authorities (CA) whose clients you deal +with. These are used for Client Authentication. Such a file is simply the +concatenation of the various PEM-encoded Certificate files, in order of +preference. This can be used alternatively and/or additionally to +SSLCACertificatePath.

+

Example

+SSLCACertificateFile /usr/local/apache2/conf/ssl.crt/ca-bundle-client.crt +

+ +
+
top
+

SSLCACertificatePath Directive

+ + + + + + +
Description:Directory of PEM-encoded CA Certificates for +Client Auth
Syntax:SSLCACertificatePath directory-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the directory where you keep the Certificates of +Certification Authorities (CAs) whose clients you deal with. These are used to +verify the client certificate on Client Authentication.

+

+The files in this directory have to be PEM-encoded and are accessed through +hash filenames. So usually you can't just place the Certificate files +there: you also have to create symbolic links named +hash-value.N. And you should always make sure this directory +contains the appropriate symbolic links. Use the Makefile which +comes with mod_ssl to accomplish this task.

+

Example

+SSLCACertificatePath /usr/local/apache2/conf/ssl.crt/ +

+ +
+
top
+

SSLCADNRequestFile Directive

+ + + + + + +
Description:File of concatenated PEM-encoded CA Certificates +for defining acceptable CA names
Syntax:SSLCADNRequestFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

When a client certificate is requested by mod_ssl, a list of +acceptable Certificate Authority names is sent to the client +in the SSL handshake. These CA names can be used by the client to +select an appropriate client certificate out of those it has +available.

+ +

If neither of the directives SSLCADNRequestPath or SSLCADNRequestFile are given, then the +set of acceptable CA names sent to the client is the names of all the +CA certificates given by the SSLCACertificateFile and SSLCACertificatePath directives; in other +words, the names of the CAs which will actually be used to verify the +client certificate.

+ +

In some circumstances, it is useful to be able to send a set of +acceptable CA names which differs from the actual CAs used to verify +the client certificate - for example, if the client certificates are +signed by intermediate CAs. In such cases, SSLCADNRequestPath and/or SSLCADNRequestFile can be used; the +acceptable CA names are then taken from the complete set of +certificates in the directory and/or file specified by this pair of +directives.

+ +

SSLCADNRequestFile must +specify an all-in-one file containing a concatenation of +PEM-encoded CA certificates.

+ +

Example

+SSLCADNRequestFile /usr/local/apache2/conf/ca-names.crt +

+ +
+
top
+

SSLCADNRequestPath Directive

+ + + + + + +
Description:Directory of PEM-encoded CA Certificates for +defining acceptable CA names
Syntax:SSLCADNRequestPath directory-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+ +

This optional directive can be used to specify the set of +acceptable CA names which will be sent to the client when a +client certificate is requested. See the SSLCADNRequestFile directive for more +details.

+ +

The files in this directory have to be PEM-encoded and are accessed +through hash filenames. So usually you can't just place the +Certificate files there: you also have to create symbolic links named +hash-value.N. And you should always make sure +this directory contains the appropriate symbolic links. Use the +Makefile which comes with mod_ssl to accomplish this +task.

+

Example

+SSLCADNRequestPath /usr/local/apache2/conf/ca-names.crt/ +

+ +
+
top
+

SSLCARevocationFile Directive

+ + + + + + +
Description:File of concatenated PEM-encoded CA CRLs for +Client Auth
Syntax:SSLCARevocationFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the all-in-one file where you can +assemble the Certificate Revocation Lists (CRL) of Certification +Authorities (CA) whose clients you deal with. These are used +for Client Authentication. Such a file is simply the concatenation of +the various PEM-encoded CRL files, in order of preference. This can be +used alternatively and/or additionally to SSLCARevocationPath.

+

Example

+SSLCARevocationFile /usr/local/apache2/conf/ssl.crl/ca-bundle-client.crl +

+ +
+
top
+

SSLCARevocationPath Directive

+ + + + + + +
Description:Directory of PEM-encoded CA CRLs for +Client Auth
Syntax:SSLCARevocationPath directory-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the directory where you keep the Certificate Revocation +Lists (CRL) of Certification Authorities (CAs) whose clients you deal with. +These are used to revoke the client certificate on Client Authentication.

+

+The files in this directory have to be PEM-encoded and are accessed through +hash filenames. So usually you have not only to place the CRL files there. +Additionally you have to create symbolic links named +hash-value.rN. And you should always make sure this directory +contains the appropriate symbolic links. Use the Makefile which +comes with mod_ssl to accomplish this task.

+

Example

+SSLCARevocationPath /usr/local/apache2/conf/ssl.crl/ +

+ +
+
top
+

SSLCertificateChainFile Directive

+ + + + + + +
Description:File of PEM-encoded Server CA Certificates
Syntax:SSLCertificateChainFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the optional all-in-one file where you can +assemble the certificates of Certification Authorities (CA) which form the +certificate chain of the server certificate. This starts with the issuing CA +certificate of of the server certificate and can range up to the root CA +certificate. Such a file is simply the concatenation of the various +PEM-encoded CA Certificate files, usually in certificate chain order.

+

+This should be used alternatively and/or additionally to SSLCACertificatePath for explicitly +constructing the server certificate chain which is sent to the browser +in addition to the server certificate. It is especially useful to +avoid conflicts with CA certificates when using client +authentication. Because although placing a CA certificate of the +server certificate chain into SSLCACertificatePath has the same effect +for the certificate chain construction, it has the side-effect that +client certificates issued by this same CA certificate are also +accepted on client authentication. That's usually not one expect.

+

+But be careful: Providing the certificate chain works only if you are using a +single (either RSA or DSA) based server certificate. If you are +using a coupled RSA+DSA certificate pair, this will work only if actually both +certificates use the same certificate chain. Else the browsers will be +confused in this situation.

+

Example

+SSLCertificateChainFile /usr/local/apache2/conf/ssl.crt/ca.crt +

+ +
+
top
+

SSLCertificateFile Directive

+ + + + + + +
Description:Server PEM-encoded X.509 Certificate file
Syntax:SSLCertificateFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive points to the PEM-encoded Certificate file for the server and +optionally also to the corresponding RSA or DSA Private Key file for it +(contained in the same file). If the contained Private Key is encrypted the +Pass Phrase dialog is forced at startup time. This directive can be used up to +two times (referencing different filenames) when both a RSA and a DSA based +server certificate is used in parallel.

+

Example

+SSLCertificateFile /usr/local/apache2/conf/ssl.crt/server.crt +

+ +
+
top
+

SSLCertificateKeyFile Directive

+ + + + + + +
Description:Server PEM-encoded Private Key file
Syntax:SSLCertificateKeyFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive points to the PEM-encoded Private Key file for the +server. If the Private Key is not combined with the Certificate in the +SSLCertificateFile, use this additional directive to +point to the file with the stand-alone Private Key. When +SSLCertificateFile is used and the file +contains both the Certificate and the Private Key this directive need +not be used. But we strongly discourage this practice. Instead we +recommend you to separate the Certificate and the Private Key. If the +contained Private Key is encrypted, the Pass Phrase dialog is forced +at startup time. This directive can be used up to two times +(referencing different filenames) when both a RSA and a DSA based +private key is used in parallel.

+

Example

+SSLCertificateKeyFile /usr/local/apache2/conf/ssl.key/server.key +

+ +
+
top
+

SSLCipherSuite Directive

+ + + + + + + + +
Description:Cipher Suite available for negotiation in SSL +handshake
Syntax:SSLCipherSuite cipher-spec
Default:SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
Context:server config, virtual host, directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
+

+This complex directive uses a colon-separated cipher-spec string +consisting of OpenSSL cipher specifications to configure the Cipher Suite the +client is permitted to negotiate in the SSL handshake phase. Notice that this +directive can be used both in per-server and per-directory context. In +per-server context it applies to the standard SSL handshake when a connection +is established. In per-directory context it forces a SSL renegotation with the +reconfigured Cipher Suite after the HTTP request was read but before the HTTP +response is sent.

+

+An SSL cipher specification in cipher-spec is composed of 4 major +attributes plus a few extra minor ones:

+
    +
  • Key Exchange Algorithm:
    + RSA or Diffie-Hellman variants. +
    • +
  • Authentication Algorithm:
    + RSA, Diffie-Hellman, DSS or none. +
    • +
  • Cipher/Encryption Algorithm:
    + DES, Triple-DES, RC4, RC2, IDEA or none. +
    • +
  • MAC Digest Algorithm:
    + MD5, SHA or SHA1. +
    • +
+

An SSL cipher can also be an export cipher and is either a SSLv2 or SSLv3/TLSv1 +cipher (here TLSv1 is equivalent to SSLv3). To specify which ciphers to use, +one can either specify all the Ciphers, one at a time, or use aliases to +specify the preference and order for the ciphers (see Table +1).

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Tag Description
Key Exchange Algorithm:
kRSA RSA key exchange
kDHr Diffie-Hellman key exchange with RSA key
kDHd Diffie-Hellman key exchange with DSA key
kEDH Ephemeral (temp.key) Diffie-Hellman key exchange (no cert)
Authentication Algorithm:
aNULL No authentication
aRSA RSA authentication
aDSS DSS authentication
aDH Diffie-Hellman authentication
Cipher Encoding Algorithm:
eNULL No encoding
DES DES encoding
3DES Triple-DES encoding
RC4 RC4 encoding
RC2 RC2 encoding
IDEA IDEA encoding
MAC Digest Algorithm:
MD5 MD5 hash function
SHA1 SHA1 hash function
SHA SHA hash function
Aliases:
SSLv2 all SSL version 2.0 ciphers
SSLv3 all SSL version 3.0 ciphers
TLSv1 all TLS version 1.0 ciphers
EXP all export ciphers
EXPORT40 all 40-bit export ciphers only
EXPORT56 all 56-bit export ciphers only
LOW all low strength ciphers (no export, single DES)
MEDIUM all ciphers with 128 bit encryption
HIGH all ciphers using Triple-DES
RSA all ciphers using RSA key exchange
DH all ciphers using Diffie-Hellman key exchange
EDH all ciphers using Ephemeral Diffie-Hellman key exchange
ADH all ciphers using Anonymous Diffie-Hellman key exchange
DSS all ciphers using DSS authentication
NULL all ciphers using no encryption
+

+Now where this becomes interesting is that these can be put together +to specify the order and ciphers you wish to use. To speed this up +there are also aliases (SSLv2, SSLv3, TLSv1, EXP, LOW, MEDIUM, +HIGH) for certain groups of ciphers. These tags can be joined +together with prefixes to form the cipher-spec. Available +prefixes are:

+
    +
  • none: add cipher to list
    • +
  • +: add ciphers to list and pull them to current location in list
    • +
  • -: remove cipher from list (can be added later again)
    • +
  • !: kill cipher from list completely (can not be added later again)
    • +
+

A simpler way to look at all of this is to use the ``openssl ciphers +-v'' command which provides a nice way to successively create the +correct cipher-spec string. The default cipher-spec string +is ``ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP'' which +means the following: first, remove from consideration any ciphers that do not +authenticate, i.e. for SSL only the Anonymous Diffie-Hellman ciphers. Next, +use ciphers using RC4 and RSA. Next include the high, medium and then the low +security ciphers. Finally pull all SSLv2 and export ciphers to the +end of the list.

+
+$ openssl ciphers -v 'ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP'
+NULL-SHA                SSLv3 Kx=RSA      Au=RSA  Enc=None      Mac=SHA1
+NULL-MD5                SSLv3 Kx=RSA      Au=RSA  Enc=None      Mac=MD5
+EDH-RSA-DES-CBC3-SHA    SSLv3 Kx=DH       Au=RSA  Enc=3DES(168) Mac=SHA1
+...                     ...               ...     ...           ...
+EXP-RC4-MD5             SSLv3 Kx=RSA(512) Au=RSA  Enc=RC4(40)   Mac=MD5  export
+EXP-RC2-CBC-MD5         SSLv2 Kx=RSA(512) Au=RSA  Enc=RC2(40)   Mac=MD5  export
+EXP-RC4-MD5             SSLv2 Kx=RSA(512) Au=RSA  Enc=RC4(40)   Mac=MD5  export
+
+

The complete list of particular RSA & DH ciphers for SSL is given in Table 2.

+

Example

+SSLCipherSuite RSA:!EXP:!NULL:+HIGH:+MEDIUM:-LOW +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Cipher-Tag Protocol Key Ex. Auth. Enc. MAC Type
RSA Ciphers:
DES-CBC3-SHA SSLv3 RSA RSA 3DES(168) SHA1
DES-CBC3-MD5 SSLv2 RSA RSA 3DES(168) MD5
IDEA-CBC-SHA SSLv3 RSA RSA IDEA(128) SHA1
RC4-SHA SSLv3 RSA RSA RC4(128) SHA1
RC4-MD5 SSLv3 RSA RSA RC4(128) MD5
IDEA-CBC-MD5 SSLv2 RSA RSA IDEA(128) MD5
RC2-CBC-MD5 SSLv2 RSA RSA RC2(128) MD5
RC4-MD5 SSLv2 RSA RSA RC4(128) MD5
DES-CBC-SHA SSLv3 RSA RSA DES(56) SHA1
RC4-64-MD5 SSLv2 RSA RSA RC4(64) MD5
DES-CBC-MD5 SSLv2 RSA RSA DES(56) MD5
EXP-DES-CBC-SHA SSLv3 RSA(512) RSA DES(40) SHA1 export
EXP-RC2-CBC-MD5 SSLv3 RSA(512) RSA RC2(40) MD5 export
EXP-RC4-MD5 SSLv3 RSA(512) RSA RC4(40) MD5 export
EXP-RC2-CBC-MD5 SSLv2 RSA(512) RSA RC2(40) MD5 export
EXP-RC4-MD5 SSLv2 RSA(512) RSA RC4(40) MD5 export
NULL-SHA SSLv3 RSA RSA None SHA1
NULL-MD5 SSLv3 RSA RSA None MD5
Diffie-Hellman Ciphers:
ADH-DES-CBC3-SHA SSLv3 DH None 3DES(168) SHA1
ADH-DES-CBC-SHA SSLv3 DH None DES(56) SHA1
ADH-RC4-MD5 SSLv3 DH None RC4(128) MD5
EDH-RSA-DES-CBC3-SHA SSLv3 DH RSA 3DES(168) SHA1
EDH-DSS-DES-CBC3-SHA SSLv3 DH DSS 3DES(168) SHA1
EDH-RSA-DES-CBC-SHA SSLv3 DH RSA DES(56) SHA1
EDH-DSS-DES-CBC-SHA SSLv3 DH DSS DES(56) SHA1
EXP-EDH-RSA-DES-CBC-SHA SSLv3 DH(512) RSA DES(40) SHA1 export
EXP-EDH-DSS-DES-CBC-SHA SSLv3 DH(512) DSS DES(40) SHA1 export
EXP-ADH-DES-CBC-SHA SSLv3 DH(512) None DES(40) SHA1 export
EXP-ADH-RC4-MD5 SSLv3 DH(512) None RC4(40) MD5 export
+ +
+
top
+

SSLCryptoDevice Directive

+ + + + + + + + +
Description:Enable use of a cryptographic hardware accelerator
Syntax:SSLCryptoDevice engine
Default:SSLCryptoDevice builtin
Context:server config
Status:Extension
Module:mod_ssl
Compatibility:Available if mod_ssl is built using -DSSL_ENGINE_EXPERIMENTAL
+

+This directive enables use of a cryptographic hardware accelerator +board to offload some of the SSL processing overhead. This directive +can only be used if the SSL toolkit is built with "engine" support; +OpenSSL 0.9.7 and later releases have "engine" support by default, the +separate "-engine" releases of OpenSSL 0.9.6 must be used.

+ +

To discover which engine names are supported, run the command +"openssl engine".

+ +

Example

+# For a Broadcom accelerator:
+SSLCryptoDevice ubsec +

+ +
+
top
+

SSLEngine Directive

+ + + + + + + +
Description:SSL Engine Operation Switch
Syntax:SSLEngine on|off|optional
Default:SSLEngine off
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive toggles the usage of the SSL/TLS Protocol Engine. This +is usually used inside a <VirtualHost> section to enable SSL/TLS for a +particular virtual host. By default the SSL/TLS Protocol Engine is +disabled for both the main server and all configured virtual hosts.

+

Example

+<VirtualHost _default_:443>
+SSLEngine on
+...
+</VirtualHost> +

+

In Apache 2.1 and later, SSLEngine can be set to +optional. This enables support for +RFC 2817, Upgrading to TLS +Within HTTP/1.1. At this time no web browsers support RFC 2817.

+ +
+
top
+

SSLHonorCipherOrder Directive

+ + + + + + + +
Description:Option to prefer the server's cipher preference order
Syntax:SSLHonorCiperOrder flag
Context:server config, virtual host
Status:Extension
Module:mod_ssl
Compatibility:Available in Apache 2.1 and later, if using OpenSSL 0.9.7 or later
+

When choosing a cipher during an SSLv3 or TLSv1 handshake, normally +the client's preference is used. If this directive is enabled, the +server's preference will be used instead.

+

Example

+SSLHonorCipherOrder on +

+ +
+
top
+

SSLMutex Directive

+ + + + + + + +
Description:Semaphore for internal mutual exclusion of +operations
Syntax:SSLMutex type
Default:SSLMutex none
Context:server config
Status:Extension
Module:mod_ssl
+

+This configures the SSL engine's semaphore (aka. lock) which is used for mutual +exclusion of operations which have to be done in a synchronized way between the +pre-forked Apache server processes. This directive can only be used in the +global server context because it's only useful to have one global mutex. +This directive is designed to closely match the +AcceptMutex directive.

+

+The following Mutex types are available:

+
    +
  • none | no +

    + This is the default where no Mutex is used at all. Use it at your own + risk. But because currently the Mutex is mainly used for synchronizing + write access to the SSL Session Cache you can live without it as long + as you accept a sometimes garbled Session Cache. So it's not recommended + to leave this the default. Instead configure a real Mutex.

    • +
  • posixsem +

    + This is an elegant Mutex variant where a Posix Semaphore is used when possible. + It is only available when the underlying platform + and APR supports it.

    • +
  • sysvsem +

    + This is a somewhat elegant Mutex variant where a SystemV IPC Semaphore is used when + possible. It is possible to "leak" SysV semaphores if processes crash before + the semaphore is removed. It is only available when the underlying platform + and APR supports it.

    • +
  • sem +

    + This directive tells the SSL Module to pick the "best" semaphore implementation + available to it, choosing between Posix and SystemV IPC, in that order. It is only + available when the underlying platform and APR supports at least one of the 2.

    • +
  • pthread +

    + This directive tells the SSL Module to use Posix thread mutexes. It is only available + if the underlying platform and APR supports it.

    • +
  • fcntl:/path/to/mutex +

    + This is a portable Mutex variant where a physical (lock-)file and the fcntl() + fucntion are used as the Mutex. + Always use a local disk filesystem for /path/to/mutex and never a file + residing on a NFS- or AFS-filesystem. It is only available when the underlying platform + and APR supports it. Note: Internally, the Process ID (PID) of the + Apache parent process is automatically appended to + /path/to/mutex to make it unique, so you don't have to worry + about conflicts yourself. Notice that this type of mutex is not available + under the Win32 environment. There you have to use the semaphore + mutex.

    • +
  • flock:/path/to/mutex +

    + This is similar to the fcntl:/path/to/mutex method with the + exception that the flock() function is used to provide file + locking. It is only available when the underlying platform + and APR supports it.

    • +
  • file:/path/to/mutex +

    + This directive tells the SSL Module to pick the "best" file locking implementation + available to it, choosing between fcntl and flock, + in that order. It is only available when the underlying platform and APR supports + at least one of the 2.

    • +
  • default | yes +

    + This directive tells the SSL Module to pick the default locking implementation + as determined by the platform and APR.

    • +
+

Example

+SSLMutex file:/usr/local/apache/logs/ssl_mutex +

+ +
+
top
+

SSLOptions Directive

+ + + + + + + +
Description:Configure various SSL engine run-time options
Syntax:SSLOptions [+|-]option ...
Context:server config, virtual host, directory, .htaccess
Override:Options
Status:Extension
Module:mod_ssl
+

+This directive can be used to control various run-time options on a +per-directory basis. Normally, if multiple SSLOptions +could apply to a directory, then the most specific one is taken +completely; the options are not merged. However if all the +options on the SSLOptions directive are preceded by a +plus (+) or minus (-) symbol, the options +are merged. Any options preceded by a + are added to the +options currently in force, and any options preceded by a +- are removed from the options currently in force.

+

+The available options are:

+
    +
  • StdEnvVars +

    + When this option is enabled, the standard set of SSL related CGI/SSI + environment variables are created. This per default is disabled for + performance reasons, because the information extraction step is a + rather expensive operation. So one usually enables this option for + CGI and SSI requests only.

    +
    • +
  • CompatEnvVars +

    + When this option is enabled, additional CGI/SSI environment variables are + created for backward compatibility to other Apache SSL solutions. Look in + the Compatibility chapter for details + on the particular variables generated.

    +
    • +
  • ExportCertData +

    + When this option is enabled, additional CGI/SSI environment variables are + created: SSL_SERVER_CERT, SSL_CLIENT_CERT and + SSL_CLIENT_CERT_CHAIN_n (with n = 0,1,2,..). + These contain the PEM-encoded X.509 Certificates of server and client for + the current HTTPS connection and can be used by CGI scripts for deeper + Certificate checking. Additionally all other certificates of the client + certificate chain are provided, too. This bloats up the environment a + little bit which is why you have to use this option to enable it on + demand.

    +
    • +
  • FakeBasicAuth +

    + When this option is enabled, the Subject Distinguished Name (DN) of the + Client X509 Certificate is translated into a HTTP Basic Authorization + username. This means that the standard Apache authentication methods can + be used for access control. The user name is just the Subject of the + Client's X509 Certificate (can be determined by running OpenSSL's + openssl x509 command: openssl x509 -noout -subject -in + certificate.crt). Note that no password is + obtained from the user. Every entry in the user file needs this password: + ``xxj31ZMTZzkVA'', which is the DES-encrypted version of the + word `password''. Those who live under MD5-based encryption + (for instance under FreeBSD or BSD/OS, etc.) should use the following MD5 + hash of the same word: ``$1$OXLyS...$Owx8s2/m9/gfkcRVXzgoE/''.

    +
    • +
  • StrictRequire +

    + This forces forbidden access when SSLRequireSSL or + SSLRequire successfully decided that access should be + forbidden. Usually the default is that in the case where a ``Satisfy + any'' directive is used, and other access restrictions are passed, + denial of access due to SSLRequireSSL or + SSLRequire is overridden (because that's how the Apache + Satisfy mechanism should work.) But for strict access restriction + you can use SSLRequireSSL and/or SSLRequire in + combination with an ``SSLOptions +StrictRequire''. Then an + additional ``Satisfy Any'' has no chance once mod_ssl has + decided to deny access.

    +
    • +
  • OptRenegotiate +

    + This enables optimized SSL connection renegotiation handling when SSL + directives are used in per-directory context. By default a strict + scheme is enabled where every per-directory reconfiguration of + SSL parameters causes a full SSL renegotiation handshake. When this + option is used mod_ssl tries to avoid unnecessary handshakes by doing more + granular (but still safe) parameter checks. Nevertheless these granular + checks sometimes maybe not what the user expects, so enable this on a + per-directory basis only, please.

    +
    • +
+

Example

+SSLOptions +FakeBasicAuth -StrictRequire
+<Files ~ "\.(cgi|shtml)$">
+ SSLOptions +StdEnvVars +CompatEnvVars -ExportCertData
+<Files> +

+ +
+
top
+

SSLPassPhraseDialog Directive

+ + + + + + + +
Description:Type of pass phrase dialog for encrypted private +keys
Syntax:SSLPassPhraseDialog type
Default:SSLPassPhraseDialog builtin
Context:server config
Status:Extension
Module:mod_ssl
+

+When Apache starts up it has to read the various Certificate (see +SSLCertificateFile) and +Private Key (see SSLCertificateKeyFile) files of the +SSL-enabled virtual servers. Because for security reasons the Private +Key files are usually encrypted, mod_ssl needs to query the +administrator for a Pass Phrase in order to decrypt those files. This +query can be done in two ways which can be configured by +type:

+
    +
  • builtin +

    + This is the default where an interactive terminal dialog occurs at startup + time just before Apache detaches from the terminal. Here the administrator + has to manually enter the Pass Phrase for each encrypted Private Key file. + Because a lot of SSL-enabled virtual hosts can be configured, the + following reuse-scheme is used to minimize the dialog: When a Private Key + file is encrypted, all known Pass Phrases (at the beginning there are + none, of course) are tried. If one of those known Pass Phrases succeeds no + dialog pops up for this particular Private Key file. If none succeeded, + another Pass Phrase is queried on the terminal and remembered for the next + round (where it perhaps can be reused).

    +

    + This scheme allows mod_ssl to be maximally flexible (because for N encrypted + Private Key files you can use N different Pass Phrases - but then + you have to enter all of them, of course) while minimizing the terminal + dialog (i.e. when you use a single Pass Phrase for all N Private Key files + this Pass Phrase is queried only once).

    • + +
  • |/path/to/program [args...] + +

    This mode allows an external program to be used which acts as a + pipe to a particular input device; the program is sent the standard + prompt text used for the builtin mode on + stdin, and is expected to write password strings on + stdout. If several passwords are needed (or an + incorrect password is entered), additional prompt text will be + written subsequent to the first password being returned, and more + passwords must then be written back.

    • + +
  • exec:/path/to/program +

    + Here an external program is configured which is called at startup for each + encrypted Private Key file. It is called with two arguments (the first is + of the form ``servername:portnumber'', the second is either + ``RSA'' or ``DSA''), which indicate for which + server and algorithm it has to print the corresponding Pass Phrase to + stdout. The intent is that this external program first runs + security checks to make sure that the system is not compromised by an + attacker, and only when these checks were passed successfully it provides + the Pass Phrase.

    +

    + Both these security checks, and the way the Pass Phrase is determined, can + be as complex as you like. Mod_ssl just defines the interface: an + executable program which provides the Pass Phrase on stdout. + Nothing more or less! So, if you're really paranoid about security, here + is your interface. Anything else has to be left as an exercise to the + administrator, because local security requirements are so different.

    +

    + The reuse-algorithm above is used here, too. In other words: The external + program is called only once per unique Pass Phrase.

    • +
+

Example

+SSLPassPhraseDialog exec:/usr/local/apache/sbin/pp-filter +

+ +
+
top
+

SSLProtocol Directive

+ + + + + + + + +
Description:Configure usable SSL protocol flavors
Syntax:SSLProtocol [+|-]protocol ...
Default:SSLProtocol all
Context:server config, virtual host
Override:Options
Status:Extension
Module:mod_ssl
+

+This directive can be used to control the SSL protocol flavors mod_ssl should +use when establishing its server environment. Clients then can only connect +with one of the provided protocols.

+

+The available (case-insensitive) protocols are:

+
    +
  • SSLv2 +

    + This is the Secure Sockets Layer (SSL) protocol, version 2.0. It is the + original SSL protocol as designed by Netscape Corporation.

    • + +
  • SSLv3 +

    + This is the Secure Sockets Layer (SSL) protocol, version 3.0. It is the + successor to SSLv2 and the currently (as of February 1999) de-facto + standardized SSL protocol from Netscape Corporation. It's supported by + almost all popular browsers.

    • + +
  • TLSv1 +

    + This is the Transport Layer Security (TLS) protocol, version 1.0. It is the + successor to SSLv3 and currently (as of February 1999) still under + construction by the Internet Engineering Task Force (IETF). It's still + not supported by any popular browsers.

    • + +
  • All +

    + This is a shortcut for ``+SSLv2 +SSLv3 +TLSv1'' and a + convinient way for enabling all protocols except one when used in + combination with the minus sign on a protocol as the example above + shows.

    • +
+

Example

+# enable SSLv3 and TLSv1, but not SSLv2
+SSLProtocol all -SSLv2 +

+ +
+
top
+

SSLProxyCACertificateFile Directive

+ + + + + + +
Description:File of concatenated PEM-encoded CA Certificates +for Remote Server Auth
Syntax:SSLProxyCACertificateFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the all-in-one file where you can assemble the +Certificates of Certification Authorities (CA) whose remote servers you deal +with. These are used for Remote Server Authentication. Such a file is simply the +concatenation of the various PEM-encoded Certificate files, in order of +preference. This can be used alternatively and/or additionally to +SSLProxyCACertificatePath.

+

Example

+SSLProxyCACertificateFile /usr/local/apache2/conf/ssl.crt/ca-bundle-remote-server.crt +

+ +
+
top
+

SSLProxyCACertificatePath Directive

+ + + + + + +
Description:Directory of PEM-encoded CA Certificates for +Remote Server Auth
Syntax:SSLProxyCACertificatePath directory-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the directory where you keep the Certificates of +Certification Authorities (CAs) whose remote servers you deal with. These are used to +verify the remote server certificate on Remote Server Authentication.

+

+The files in this directory have to be PEM-encoded and are accessed through +hash filenames. So usually you can't just place the Certificate files +there: you also have to create symbolic links named +hash-value.N. And you should always make sure this directory +contains the appropriate symbolic links. Use the Makefile which +comes with mod_ssl to accomplish this task.

+

Example

+SSLProxyCACertificatePath /usr/local/apache2/conf/ssl.crt/ +

+ +
+
top
+

SSLProxyCARevocationFile Directive

+ + + + + + +
Description:File of concatenated PEM-encoded CA CRLs for +Remote Server Auth
Syntax:SSLProxyCARevocationFile file-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the all-in-one file where you can +assemble the Certificate Revocation Lists (CRL) of Certification +Authorities (CA) whose remote servers you deal with. These are used +for Remote Server Authentication. Such a file is simply the concatenation of +the various PEM-encoded CRL files, in order of preference. This can be +used alternatively and/or additionally to SSLProxyCARevocationPath.

+

Example

+SSLProxyCARevocationFile /usr/local/apache2/conf/ssl.crl/ca-bundle-remote-server.crl +

+ +
+
top
+

SSLProxyCARevocationPath Directive

+ + + + + + +
Description:Directory of PEM-encoded CA CRLs for +Remote Server Auth
Syntax:SSLProxyCARevocationPath directory-path
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the directory where you keep the Certificate Revocation +Lists (CRL) of Certification Authorities (CAs) whose remote servers you deal with. +These are used to revoke the remote server certificate on Remote Server Authentication.

+

+The files in this directory have to be PEM-encoded and are accessed through +hash filenames. So usually you have not only to place the CRL files there. +Additionally you have to create symbolic links named +hash-value.rN. And you should always make sure this directory +contains the appropriate symbolic links. Use the Makefile which +comes with mod_ssl to accomplish this task.

+

Example

+SSLProxyCARevocationPath /usr/local/apache2/conf/ssl.crl/ +

+ +
+
top
+

SSLProxyCipherSuite Directive

+ + + + + + + + +
Description:Cipher Suite available for negotiation in SSL +proxy handshake
Syntax:SSLProxyCipherSuite cipher-spec
Default:SSLProxyCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
Context:server config, virtual host, directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
+

Equivalent to SSLCipherSuite, but for the proxy connection. +Please refer to SSLCipherSuite +for additional information.

+ +
+
top
+

SSLProxyEngine Directive

+ + + + + + + +
Description:SSL Proxy Engine Operation Switch
Syntax:SSLProxyEngine on|off
Default:SSLProxyEngine off
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive toggles the usage of the SSL/TLS Protocol Engine for proxy. This +is usually used inside a <VirtualHost> section to enable SSL/TLS for proxy +usage in a particular virtual host. By default the SSL/TLS Protocol Engine is +disabled for proxy image both for the main server and all configured virtual hosts.

+

Example

+<VirtualHost _default_:443>
+SSLProxyEngine on
+...
+</VirtualHost> +

+ +
+
top
+

SSLProxyMachineCertificateFile Directive

+ + + + + + + +
Description:File of concatenated PEM-encoded client certificates and keys to be used by the proxy
Syntax:SSLProxyMachineCertificateFile filename
Context:server config
Override:Not applicable
Status:Extension
Module:mod_ssl
+

+This directive sets the all-in-one file where you keep the certificates and +keys used for authentication of the proxy server to remote servers. +

+

+This referenced file is simply the concatenation of the various PEM-encoded +certificate files, in order of preference. Use this directive alternatively +or additionally to SSLProxyMachineCertificatePath. +

+
+

Currently there is no support for encrypted private keys

+
+

Example

+SSLProxyMachineCertificateFile /usr/local/apache2/conf/ssl.crt/proxy.pem +

+ +
+
top
+

SSLProxyMachineCertificatePath Directive

+ + + + + + + +
Description:Directory of PEM-encoded client certificates and keys to be used by the proxy
Syntax:SSLProxyMachineCertificatePath directory
Context:server config
Override:Not applicable
Status:Extension
Module:mod_ssl
+

+This directive sets the directory where you keep the certificates and +keys used for authentication of the proxy server to remote servers. +

+

The files in this directory must be PEM-encoded and are accessed through +hash filenames. Additionally, you must create symbolic links named +hash-value.N. And you should always make sure this +directory contains the appropriate symbolic links. Use the Makefile which +comes with mod_ssl to accomplish this task. +

+
+

Currently there is no support for encrypted private keys

+
+

Example

+SSLProxyMachineCertificatePath /usr/local/apache2/conf/proxy.crt/ +

+ +
+
top
+

SSLProxyProtocol Directive

+ + + + + + + + +
Description:Configure usable SSL protocol flavors for proxy usage
Syntax:SSLProxyProtocol [+|-]protocol ...
Default:SSLProxyProtocol all
Context:server config, virtual host
Override:Options
Status:Extension
Module:mod_ssl
+ +

+This directive can be used to control the SSL protocol flavors mod_ssl should +use when establishing its server environment for proxy . It will only connect +to servers using one of the provided protocols.

+

Please refer to SSLProtocol +for additional information. +

+ +
+
top
+

SSLProxyVerify Directive

+ + + + + + + + +
Description:Type of remote server Certificate verification
Syntax:SSLProxyVerify level
Default:SSLProxyVerify none
Context:server config, virtual host, directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
+ +

When a proxy is configured to forward requests to a remote SSL +server, this directive can be used to configure certificate +verification of the remote server. Notice that this directive can be +used both in per-server and per-directory context. In per-server +context it applies to the remote server authentication process used in +the standard SSL handshake when a connection is established by the +proxy. In per-directory context it forces a SSL renegotation with the +reconfigured remote server verification level after the HTTP request +was read but before the HTTP response is sent.

+ +
+

Note that even when certificate verification is enabled, +mod_ssl does not check whether the +commonName (hostname) attribute of the server certificate +matches the hostname used to connect to the server. In other words, +the proxy does not guarantee that the SSL connection to the backend +server is "secure" beyond the fact that the certificate is signed by +one of the CAs configured using the +SSLProxyCACertificatePath and/or +SSLProxyCACertificateFile directives.

+
+ +

+The following levels are available for level:

+
    +
  • none: + no remote server Certificate is required at all
    • +
  • optional: + the remote server may present a valid Certificate
    • +
  • require: + the remote server has to present a valid Certificate
    • +
  • optional_no_ca: + the remote server may present a valid Certificate
    + but it need not to be (successfully) verifiable.
    • +
+

In practice only levels none and +require are really interesting, because level +optional doesn't work with all servers and level +optional_no_ca is actually against the idea of +authentication (but can be used to establish SSL test pages, etc.)

+

Example

+SSLProxyVerify require +

+ +
+
top
+

SSLProxyVerifyDepth Directive

+ + + + + + + + +
Description:Maximum depth of CA Certificates in Remote Server +Certificate verification
Syntax:SSLProxyVerifyDepth number
Default:SSLProxyVerifyDepth 1
Context:server config, virtual host, directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
+

+This directive sets how deeply mod_ssl should verify before deciding that the +remote server does not have a valid certificate. Notice that this directive can be +used both in per-server and per-directory context. In per-server context it +applies to the client authentication process used in the standard SSL +handshake when a connection is established. In per-directory context it forces +a SSL renegotation with the reconfigured remote server verification depth after the +HTTP request was read but before the HTTP response is sent.

+

+The depth actually is the maximum number of intermediate certificate issuers, +i.e. the number of CA certificates which are max allowed to be followed while +verifying the remote server certificate. A depth of 0 means that self-signed +remote server certificates are accepted only, the default depth of 1 means +the remote server certificate can be self-signed or has to be signed by a CA +which is directly known to the server (i.e. the CA's certificate is under +SSLProxyCACertificatePath), etc.

+

Example

+SSLProxyVerifyDepth 10 +

+ +
+
top
+

SSLRandomSeed Directive

+ + + + + + +
Description:Pseudo Random Number Generator (PRNG) seeding +source
Syntax:SSLRandomSeed context source +[bytes]
Context:server config
Status:Extension
Module:mod_ssl
+

+This configures one or more sources for seeding the Pseudo Random Number +Generator (PRNG) in OpenSSL at startup time (context is +startup) and/or just before a new SSL connection is established +(context is connect). This directive can only be used +in the global server context because the PRNG is a global facility.

+

+The following source variants are available:

+
    +
  • builtin +

    This is the always available builtin seeding source. It's usage + consumes minimum CPU cycles under runtime and hence can be always used + without drawbacks. The source used for seeding the PRNG contains of the + current time, the current process id and (when applicable) a randomly + choosen 1KB extract of the inter-process scoreboard structure of Apache. + The drawback is that this is not really a strong source and at startup + time (where the scoreboard is still not available) this source just + produces a few bytes of entropy. So you should always, at least for the + startup, use an additional seeding source.

    • +
  • file:/path/to/source +

    + This variant uses an external file /path/to/source as the + source for seeding the PRNG. When bytes is specified, only the + first bytes number of bytes of the file form the entropy (and + bytes is given to /path/to/source as the first + argument). When bytes is not specified the whole file forms the + entropy (and 0 is given to /path/to/source as + the first argument). Use this especially at startup time, for instance + with an available /dev/random and/or + /dev/urandom devices (which usually exist on modern Unix + derivates like FreeBSD and Linux).

    +

    + But be careful: Usually /dev/random provides only as + much entropy data as it actually has, i.e. when you request 512 bytes of + entropy, but the device currently has only 100 bytes available two things + can happen: On some platforms you receive only the 100 bytes while on + other platforms the read blocks until enough bytes are available (which + can take a long time). Here using an existing /dev/urandom is + better, because it never blocks and actually gives the amount of requested + data. The drawback is just that the quality of the received data may not + be the best.

    +

    + On some platforms like FreeBSD one can even control how the entropy is + actually generated, i.e. by which system interrupts. More details one can + find under rndcontrol(8) on those platforms. Alternatively, when + your system lacks such a random device, you can use tool + like EGD + (Entropy Gathering Daemon) and run it's client program with the + exec:/path/to/program/ variant (see below) or use + egd:/path/to/egd-socket (see below).

    • + +
  • exec:/path/to/program +

    + This variant uses an external executable + /path/to/program as the source for seeding the + PRNG. When bytes is specified, only the first + bytes number of bytes of its stdout contents + form the entropy. When bytes is not specified, the + entirety of the data produced on stdout form the + entropy. Use this only at startup time when you need a very strong + seeding with the help of an external program (for instance as in + the example above with the truerand utility you can + find in the mod_ssl distribution which is based on the AT&T + truerand library). Using this in the connection context + slows down the server too dramatically, of course. So usually you + should avoid using external programs in that context.

    • +
  • egd:/path/to/egd-socket (Unix only) +

    + This variant uses the Unix domain socket of the + external Entropy Gathering Daemon (EGD) (see http://www.lothar.com/tech + /crypto/) to seed the PRNG. Use this if no random device exists + on your platform.

    • +
+

Example

+SSLRandomSeed startup builtin
+SSLRandomSeed startup file:/dev/random
+SSLRandomSeed startup file:/dev/urandom 1024
+SSLRandomSeed startup exec:/usr/local/bin/truerand 16
+SSLRandomSeed connect builtin
+SSLRandomSeed connect file:/dev/random
+SSLRandomSeed connect file:/dev/urandom 1024
+

+ +
+
top
+

SSLRequire Directive

+ + + + + + + +
Description:Allow access only when an arbitrarily complex +boolean expression is true
Syntax:SSLRequire expression
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
+

+This directive specifies a general access requirement which has to be +fulfilled in order to allow access. It is a very powerful directive because the +requirement specification is an arbitrarily complex boolean expression +containing any number of access checks.

+
+

The implementation of SSLRequire is not thread safe. + Using SSLRequire inside .htaccess files + on a threaded MPM may cause random crashes. +

+
+

+The expression must match the following syntax (given as a BNF +grammar notation):

+
+
+expr     ::= "true" | "false"
+           | "!" expr
+           | expr "&&" expr
+           | expr "||" expr
+           | "(" expr ")"
+           | comp
+
+comp     ::= word "==" word | word "eq" word
+           | word "!=" word | word "ne" word
+           | word "<"  word | word "lt" word
+           | word "<=" word | word "le" word
+           | word ">"  word | word "gt" word
+           | word ">=" word | word "ge" word
+           | word "in" "{" wordlist "}"
+           | word "in" "OID(" word ")"
+           | word "=~" regex
+           | word "!~" regex
+
+wordlist ::= word
+           | wordlist "," word
+
+word     ::= digit
+           | cstring
+           | variable
+           | function
+
+digit    ::= [0-9]+
+cstring  ::= "..."
+variable ::= "%{" varname "}"
+function ::= funcname "(" funcargs ")"
+
+
+

while for varname any variable from Table 3 can be used. Finally for +funcname the following functions are available:

+
    +
  • file(filename) +

    + This function takes one string argument and expands to the contents of the + file. This is especially useful for matching this contents against a + regular expression, etc.

    +
    • +
+

Notice that expression is first parsed into an internal machine +representation and then evaluated in a second step. Actually, in Global and +Per-Server Class context expression is parsed at startup time and +at runtime only the machine representation is executed. For Per-Directory +context this is different: here expression has to be parsed and +immediately executed for every request.

+

Example

+SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)-/ \
+ and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
+ and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
+ and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
+ and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
+ or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ +

+

The OID() function expects to find zero or more instances +of the given OID in the client certificate, and compares the left-hand side +string against the value of matching OID attributes. Every matching OID is +checked, until a match is found. +

+ +

Standard CGI/1.0 and Apache variables:

+
+HTTP_USER_AGENT        PATH_INFO             AUTH_TYPE
+HTTP_REFERER           QUERY_STRING          SERVER_SOFTWARE
+HTTP_COOKIE            REMOTE_HOST           API_VERSION
+HTTP_FORWARDED         REMOTE_IDENT          TIME_YEAR
+HTTP_HOST              IS_SUBREQ             TIME_MON
+HTTP_PROXY_CONNECTION  DOCUMENT_ROOT         TIME_DAY
+HTTP_ACCEPT            SERVER_ADMIN          TIME_HOUR
+HTTP:headername        SERVER_NAME           TIME_MIN
+THE_REQUEST            SERVER_PORT           TIME_SEC
+REQUEST_METHOD         SERVER_PROTOCOL       TIME_WDAY
+REQUEST_SCHEME         REMOTE_ADDR           TIME
+REQUEST_URI            REMOTE_USER           ENV:variablename
+REQUEST_FILENAME
+
+

SSL-related variables:

+
+HTTPS                  SSL_CLIENT_M_VERSION   SSL_SERVER_M_VERSION
+                       SSL_CLIENT_M_SERIAL    SSL_SERVER_M_SERIAL
+SSL_PROTOCOL           SSL_CLIENT_V_START     SSL_SERVER_V_START
+SSL_SESSION_ID         SSL_CLIENT_V_END       SSL_SERVER_V_END
+SSL_CIPHER             SSL_CLIENT_S_DN        SSL_SERVER_S_DN
+SSL_CIPHER_EXPORT      SSL_CLIENT_S_DN_C      SSL_SERVER_S_DN_C
+SSL_CIPHER_ALGKEYSIZE  SSL_CLIENT_S_DN_ST     SSL_SERVER_S_DN_ST
+SSL_CIPHER_USEKEYSIZE  SSL_CLIENT_S_DN_L      SSL_SERVER_S_DN_L
+SSL_VERSION_LIBRARY    SSL_CLIENT_S_DN_O      SSL_SERVER_S_DN_O
+SSL_VERSION_INTERFACE  SSL_CLIENT_S_DN_OU     SSL_SERVER_S_DN_OU
+                       SSL_CLIENT_S_DN_CN     SSL_SERVER_S_DN_CN
+                       SSL_CLIENT_S_DN_T      SSL_SERVER_S_DN_T
+                       SSL_CLIENT_S_DN_I      SSL_SERVER_S_DN_I
+                       SSL_CLIENT_S_DN_G      SSL_SERVER_S_DN_G
+                       SSL_CLIENT_S_DN_S      SSL_SERVER_S_DN_S
+                       SSL_CLIENT_S_DN_D      SSL_SERVER_S_DN_D
+                       SSL_CLIENT_S_DN_UID    SSL_SERVER_S_DN_UID
+                       SSL_CLIENT_S_DN_Email  SSL_SERVER_S_DN_Email
+                       SSL_CLIENT_I_DN        SSL_SERVER_I_DN
+                       SSL_CLIENT_I_DN_C      SSL_SERVER_I_DN_C
+                       SSL_CLIENT_I_DN_ST     SSL_SERVER_I_DN_ST
+                       SSL_CLIENT_I_DN_L      SSL_SERVER_I_DN_L
+                       SSL_CLIENT_I_DN_O      SSL_SERVER_I_DN_O
+                       SSL_CLIENT_I_DN_OU     SSL_SERVER_I_DN_OU
+                       SSL_CLIENT_I_DN_CN     SSL_SERVER_I_DN_CN
+                       SSL_CLIENT_I_DN_T      SSL_SERVER_I_DN_T
+                       SSL_CLIENT_I_DN_I      SSL_SERVER_I_DN_I
+                       SSL_CLIENT_I_DN_G      SSL_SERVER_I_DN_G
+                       SSL_CLIENT_I_DN_S      SSL_SERVER_I_DN_S
+                       SSL_CLIENT_I_DN_D      SSL_SERVER_I_DN_D
+                       SSL_CLIENT_I_DN_UID    SSL_SERVER_I_DN_UID
+                       SSL_CLIENT_I_DN_Email  SSL_SERVER_I_DN_Email
+                       SSL_CLIENT_A_SIG       SSL_SERVER_A_SIG
+                       SSL_CLIENT_A_KEY       SSL_SERVER_A_KEY
+                       SSL_CLIENT_CERT        SSL_SERVER_CERT
+                       SSL_CLIENT_CERT_CHAIN_n
+                       SSL_CLIENT_VERIFY
+
+ +
+
top
+

SSLRequireSSL Directive

+ + + + + + + +
Description:Deny access when SSL is not used for the +HTTP request
Syntax:SSLRequireSSL
Context:directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
+

+This directive forbids access unless HTTP over SSL (i.e. HTTPS) is enabled for +the current connection. This is very handy inside the SSL-enabled virtual +host or directories for defending against configuration errors that expose +stuff that should be protected. When this directive is present all requests +are denied which are not using SSL.

+

Example

+SSLRequireSSL +

+ +
+
top
+

SSLSessionCache Directive

+ + + + + + + +
Description:Type of the global/inter-process SSL Session +Cache
Syntax:SSLSessionCache type
Default:SSLSessionCache none
Context:server config
Status:Extension
Module:mod_ssl
+

+This configures the storage type of the global/inter-process SSL Session +Cache. This cache is an optional facility which speeds up parallel request +processing. For requests to the same server process (via HTTP keep-alive), +OpenSSL already caches the SSL session information locally. But because modern +clients request inlined images and other data via parallel requests (usually +up to four parallel requests are common) those requests are served by +different pre-forked server processes. Here an inter-process cache +helps to avoid unneccessary session handshakes.

+

+The following four storage types are currently supported:

+
    +
  • none + +

    This disables the global/inter-process Session Cache. This + will incur a noticeable speed penalty and may cause problems if + using certain browsers, particularly if client certificates are + enabled. This setting is not recommended.

    • + +
  • nonenotnull + +

    This disables any global/inter-process Session Cache. However + it does force OpenSSL to send a non-null session ID to + accommodate buggy clients that require one.

    • + +
  • dbm:/path/to/datafile + +

    This makes use of a DBM hashfile on the local disk to + synchronize the local OpenSSL memory caches of the server + processes. This session cache may suffer reliability issues under + high load.

    • + +
  • shm:/path/to/datafile[(size)] + +

    This makes use of a high-performance cyclic buffer + (approx. size bytes in size) inside a shared memory + segment in RAM (established via /path/to/datafile) to + synchronize the local OpenSSL memory caches of the server + processes. This is the recommended session cache.

    • + +
  • dc:UNIX:/path/to/socket + +

    This makes use of the distcache distributed session + caching libraries. The argument should specify the location of + the server or proxy to be used using the distcache address syntax; + for example, UNIX:/path/to/socket specifies a UNIX + domain socket (typically a local dc_client proxy); + IP:server.example.com:9001 specifies an IP + address.

    • + +
+

Examples

+SSLSessionCache dbm:/usr/local/apache/logs/ssl_gcache_data
+SSLSessionCache shm:/usr/local/apache/logs/ssl_gcache_data(512000) +

+ +
+
top
+

SSLSessionCacheTimeout Directive

+ + + + + + + +
Description:Number of seconds before an SSL session expires +in the Session Cache
Syntax:SSLSessionCacheTimeout seconds
Default:SSLSessionCacheTimeout 300
Context:server config, virtual host
Status:Extension
Module:mod_ssl
+

+This directive sets the timeout in seconds for the information stored in the +global/inter-process SSL Session Cache and the OpenSSL internal memory cache. +It can be set as low as 15 for testing, but should be set to higher +values like 300 in real life.

+

Example

+SSLSessionCacheTimeout 600 +

+ +
+
top
+

SSLUserName Directive

+ + + + + + + + +
Description:Variable name to determine user name
Syntax:SSLUserName varname
Context:server config, directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
Compatibility:Available in Apache 2.0.51 and later
+

+This directive sets the "user" field in the Apache request object. +This is used by lower modules to identify the user with a character +string. In particular, this may cause the environment variable +REMOTE_USER to be set. The varname can be +any of the SSL environment variables.

+ +

Note that this directive has no effect if the +FakeBasic option is used (see SSLOptions).

+ +

Example

+SSLUserName SSL_CLIENT_S_DN_CN +

+ +
+
top
+

SSLVerifyClient Directive

+ + + + + + + + +
Description:Type of Client Certificate verification
Syntax:SSLVerifyClient level
Default:SSLVerifyClient none
Context:server config, virtual host, directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
+

+This directive sets the Certificate verification level for the Client +Authentication. Notice that this directive can be used both in per-server and +per-directory context. In per-server context it applies to the client +authentication process used in the standard SSL handshake when a connection is +established. In per-directory context it forces a SSL renegotation with the +reconfigured client verification level after the HTTP request was read but +before the HTTP response is sent.

+

+The following levels are available for level:

+
    +
  • none: + no client Certificate is required at all
    • +
  • optional: + the client may present a valid Certificate
    • +
  • require: + the client has to present a valid Certificate
    • +
  • optional_no_ca: + the client may present a valid Certificate
    + but it need not to be (successfully) verifiable.
    • +
+

In practice only levels none and +require are really interesting, because level +optional doesn't work with all browsers and level +optional_no_ca is actually against the idea of +authentication (but can be used to establish SSL test pages, etc.)

+

Example

+SSLVerifyClient require +

+ +
+
top
+

SSLVerifyDepth Directive

+ + + + + + + + +
Description:Maximum depth of CA Certificates in Client +Certificate verification
Syntax:SSLVerifyDepth number
Default:SSLVerifyDepth 1
Context:server config, virtual host, directory, .htaccess
Override:AuthConfig
Status:Extension
Module:mod_ssl
+

+This directive sets how deeply mod_ssl should verify before deciding that the +clients don't have a valid certificate. Notice that this directive can be +used both in per-server and per-directory context. In per-server context it +applies to the client authentication process used in the standard SSL +handshake when a connection is established. In per-directory context it forces +a SSL renegotation with the reconfigured client verification depth after the +HTTP request was read but before the HTTP response is sent.

+

+The depth actually is the maximum number of intermediate certificate issuers, +i.e. the number of CA certificates which are max allowed to be followed while +verifying the client certificate. A depth of 0 means that self-signed client +certificates are accepted only, the default depth of 1 means the client +certificate can be self-signed or has to be signed by a CA which is directly +known to the server (i.e. the CA's certificate is under +SSLCACertificatePath), etc.

+

Example

+SSLVerifyDepth 10 +

+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_status.html b/docs/manual/mod/mod_status.html new file mode 100644 index 00000000..64e6ac3d --- /dev/null +++ b/docs/manual/mod/mod_status.html @@ -0,0 +1,11 @@ +URI: mod_status.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_status.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_status.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_status.html.en b/docs/manual/mod/mod_status.html.en new file mode 100644 index 00000000..059cd2da --- /dev/null +++ b/docs/manual/mod/mod_status.html.en @@ -0,0 +1,162 @@ + + + +mod_status - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_status

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Provides information on server activity and +performance
Status:Base
Module Identifier:status_module
Source File:mod_status.c
+

Summary

+ +

The Status module allows a server administrator to find out + how well their server is performing. A HTML page is presented + that gives the current server statistics in an easily readable + form. If required this page can be made to automatically + refresh (given a compatible browser). Another page gives a + simple machine-readable list of the current server state.

+ +

The details given are:

+ +
    +
  • The number of worker serving requests
    • + +
  • The number of idle worker
    • + +
  • The status of each worker, the number of requests that + worker has performed and the total number of bytes served by + the worker (*)
    • + +
  • A total number of accesses and byte count served (*)
    • + +
  • The time the server was started/restarted and the time it + has been running for
    • + +
  • Averages giving the number of requests per second, the + number of bytes served per second and the average number of + bytes per request (*)
    • + +
  • The current percentage CPU used by each worker and in + total by Apache (*)
    • + +
  • The current hosts and requests being processed (*)
    • +
+ +

A compile-time option must be used to display the details + marked "(*)" as the instrumentation required for obtaining + these statistics does not exist within standard Apache.

+
+ +
top
+
+

Enabling Status Support

+ + +

To enable status reports only for browsers from the foo.com + domain add this code to your httpd.conf + configuration file

+

+ <Location /server-status>
+ SetHandler server-status
+
+ Order Deny,Allow
+ Deny from all
+ Allow from .foo.com
+ </Location> +

+ +

You can now access server statistics by using a Web browser + to access the page + http://your.server.name/server-status

+
top
+
+

Automatic Updates

+ + +

You can get the status page to update itself automatically if + you have a browser that supports "refresh". Access the page + http://your.server.name/server-status?refresh=N to + refresh the page every N seconds.

+ +
top
+
+

Machine Readable Status File

+ + +

A machine-readable version of the status file is available by + accessing the page + http://your.server.name/server-status?auto. This + is useful when automatically run, see the Perl program in the + /support directory of Apache, + log_server_status.

+ +
+ It should be noted that if mod_status is + compiled into the server, its handler capability is available + in all configuration files, including + per-directory files (e.g., + .htaccess). This may have security-related + ramifications for your site. +
+ +
+
top
+

ExtendedStatus Directive

+ + + + + + + + +
Description:Keep track of extended status information for each +request
Syntax:ExtendedStatus On|Off
Default:ExtendedStatus Off
Context:server config
Status:Base
Module:mod_status
Compatibility:ExtendedStatus is only available in Apache 1.3.2 and +later.
+

This setting applies to the entire server, and cannot be + enabled or disabled on a virtualhost-by-virtualhost basis. + The collection of extended status information can slow down + the server.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_status.html.ja.euc-jp b/docs/manual/mod/mod_status.html.ja.euc-jp new file mode 100644 index 00000000..de7cfecb --- /dev/null +++ b/docs/manual/mod/mod_status.html.ja.euc-jp @@ -0,0 +1,154 @@ + + + +mod_status - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_status

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:¥µ¡¼¥Ð¤Î³èÆ°¾õ¶·¤ÈÀ­Ç½¤Ë´Ø¤¹¤ë¾ðÊó¤òÄ󶡤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:status_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_status.c
+

³µÍ×

+ +

¤³¤Î Status ¥â¥¸¥å¡¼¥ë¤Ë¤è¤ê¥µ¡¼¥Ð´ÉÍý¼Ô¤Ï¥µ¡¼¥Ð¤¬¤É¤Î¤¯¤é¤¤ + ¤ÎÀ­Ç½¤ÇÆ°ºî¤·¤Æ¤¤¤ë¤«¤òÃΤ뤳¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¸½»þÅÀ¤Ç¤Î¥µ¡¼¥Ð¤ÎÅý·×¾ðÊó¤òÆɤߤ䤹¤¤·Á¼°¤Çɽ¤·¤¿ HTML ¥Ú¡¼¥¸¤¬ + ɽ¼¨¤µ¤ì¤Þ¤¹¡£É¬ÍפǤ¢¤ì¤Ð¡¢¤³¤Î¥Ú¡¼¥¸¤Ï¼«Æ°Åª¤Ë¥ê¥Õ¥ì¥Ã¥·¥å¤µ¤»¤ë + ¤³¤È¤â¤Ç¤­¤Þ¤¹ (¸ß´¹À­¤Î¤¢¤ë¥Ö¥é¥¦¥¶¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç)¡£ + Ê̤ˡ¢¸½»þÅÀ¤Ç¤Î¥µ¡¼¥Ð¤Î¾õÂÖ¤òñ½ã¤Êµ¡³£Æɤ߼è¤ê²Äǽ¤Ê¥ê¥¹¥È¤Ç + ɽ¤¹¥Ú¡¼¥¸¤â¤¢¤ê¤Þ¤¹¡£

+ +

ɽ¼¨¤µ¤ì¤ë¾ðÊó¤Ï:

+ +
    +
  • ¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤Æ¤¤¤ë¥ï¡¼¥«¡¼¤Î¿ô
    • + +
  • ¥¢¥¤¥É¥ë (ÌõÃí: ¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤Æ¤¤¤Ê¤¤) ¥ï¡¼¥«¡¼¤Î¿ô
    • + +
  • ³Æ¥ï¡¼¥«¡¼¤Î¾õÂÖ¡¢¥ï¡¼¥«¡¼¤¬°·¤Ã¤¿¥ê¥¯¥¨¥¹¥È¤Î¿ô¡¢ + ¥ï¡¼¥«¡¼¤¬Á÷¤Ã¤¿Áí¥Ð¥¤¥È¿ô (*)
    • + +
  • Áí¥¢¥¯¥»¥¹¿ô¤ÈÁí¥Ð¥¤¥È¿ô (*)
    • + +
  • ¥µ¡¼¥Ð¤¬µ¯Æ°¤â¤·¤¯¤ÏºÆµ¯Æ°¤µ¤ì¤¿»þ¹ï¤ÈÆ°ºî¤·¤Æ¤¤¤ë»þ´Ö
    • + +
  • Ê¿¶Ñ¤Î 1 É䢤¿¤ê¤Î¥ê¥¯¥¨¥¹¥È¿ô¡¢1 É䢤¿¤ê¤ÎÁ÷¤é¤ì¤¿¥Ð¥¤¥È¿ô¡¢ + ¥ê¥¯¥¨¥¹¥È¤¢¤¿¤ê¤Î¥Ð¥¤¥È¿ô (*)
    • + +
  • ³Æ¥ï¡¼¥«¡¼¤È Apache Á´ÂΤǻÈÍѤµ¤ì¤Æ¤¤¤ë CPU ¤Î³ä¹ç (*)
    • + +
  • ¸½»þÅÀ¤Î¥Û¥¹¥È¤È½èÍý¤µ¤ì¤Æ¤¤¤ë¥ê¥¯¥¨¥¹¥È (*)
    • +
+ +

"(*)" ¤ÎÉÕ¤¤¤Æ¤¤¤ë¾ðÊó¤òɽ¼¨¤¹¤ë¤¿¤á¤Ë¤Ï¥³¥ó¥Ñ¥¤¥ë»þ¤Î¥ª¥×¥·¥ç¥ó + ¤ò»ÈÍѤ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤é¤ÎÅý·×¾ðÊó¤òÆÀ¤ë¤¿¤á¤ËɬÍ×¤Ê + ¥³¡¼¥É¤Ïɸ½à¤Î Apache ¤Ë¤Ï´Þ¤Þ¤ì¤Æ¤¤¤Þ¤»¤ó¡£

+
+ +
top
+
+

Status ¤ò»ÈÍѲÄǽ¤Ë¤¹¤ë

+ + +

foo.com ¥É¥á¥¤¥ó¤«¤é¤Î¥Ö¥é¥¦¥¶¤Î¤ß¤ËÂФ·¤Æ + ¥¹¥Æ¡¼¥¿¥¹¤ÎÊó¹ð¤ò»ÈÍѲÄǽ¤Ë¤¹¤ë¤Ë¤Ï + °Ê²¼¤Î¥³¡¼¥É¤ò httpd.conf ÀßÄê¥Õ¥¡¥¤¥ë¤ËÄɲä·¤Þ¤¹

+

+ <Location /server-status>
+ SetHandler server-status
+
+ Order Deny,Allow
+ Deny from all
+ Allow from .foo.com
+ </Location> +

+ +

¤³¤ì¤Ç¡¢¥µ¡¼¥Ð¤ÎÅý·×¾ðÊó¤ò¥¦¥§¥Ö¥Ö¥é¥¦¥¶¤ò»È¤Ã¤Æ + http://your.server.name/server-status ¤ò¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤Ë¤è¤ê + ÃΤ뤳¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+
top
+
+

¼«Æ°¹¹¿·

+ + +

¥Ö¥é¥¦¥¶¤¬¡Ö¥ê¥Õ¥ì¥Ã¥·¥å¡×µ¡Ç½¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ì¤Ð¡¢¥¹¥Æ¡¼¥¿¥¹¥Ú¡¼¥¸¤ò + ¼«Æ°Åª¤Ë¹¹¿·¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£N ÉÃËè¤Ë¹¹¿·¤µ¤»¤ë¤¿¤á¤Ë¤Ï + http://your.server.name/server-status?refresh=N + ¤È¤¤¤¦¥Ú¡¼¥¸¤ò¥¢¥¯¥»¥¹¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
top
+
+

µ¡³£Æɤ߼è¤ê²Äǽ¤Ê¥¹¥Æ¡¼¥¿¥¹¥Õ¥¡¥¤¥ë

+ + +

http://your.server.name/server-status?auto ¤ò + ¥¢¥¯¥»¥¹¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢¥¹¥Æ¡¼¥¿¥¹¥Õ¥¡¥¤¥ë¤Îµ¡³£Æɤ߼è¤ê²Äǽ¤Ê¥Ð¡¼¥¸¥ç¥ó¤ò + ÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤Ï¼«Æ°Åª¤Ë¼Â¹Ô¤µ¤ì¤ë¤È¤­¤ËÊØÍø¤Ç¤¹¡£ + Apache ¤Î /support ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë + Perl ¥×¥í¥°¥é¥à log_server_status ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£

+ +
+ mod_status ¤¬¥µ¡¼¥Ð¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë + ¾ì¹ç¡¢¥Ï¥ó¥É¥é¤Îµ¡Ç½¤Ï¥Ç¥£¥ì¥¯¥È¥êËè¤Î¥Õ¥¡¥¤¥ë + (¤¹¤Ê¤ï¤Á¡¢.htaccess) ¤â´Þ¤à¤¹¤Ù¤Æ¤Î + ÀßÄê¥Õ¥¡¥¤¥ë¤Ç»ÈÍѲÄǽ¤Ë¤Ê¤ë¤³¤È¤Ë¤ÏÃí°Õ¤ò¤·¤Æ¤ª¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¥µ¥¤¥È¤Ë¤è¤Ã¤Æ¤Ï¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤¹¤ë˾¤Þ¤·¤¯¤Ê¤¤·ë²Ì¤ò + ¤â¤¿¤é¤¹¤³¤È¤¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ +
+ +
+
top
+

ExtendedStatus ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:³Æ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ³ÈÄ¥¥¹¥Æ¡¼¥¿¥¹¾ðÊó¤òÊݸ¤¹¤ë
¹½Ê¸:ExtendedStatus On|Off
¥Ç¥Õ¥©¥ë¥È:ExtendedStatus Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_status
¸ß´¹À­:ExtendedStatus ¤Ï Apache 1.3.2 °Ê¹ß¤Ç¤Î¤ß»ÈÍѲÄǽ
+

¤³¤ÎÀßÄê¤Ï¥µ¡¼¥ÐÁ´ÂΤËÂФ·¤ÆŬÍѤµ¤ì¡¢¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈËè¤Ë + Êѹ¹¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£³ÈÄ¥¥¹¥Æ¡¼¥¿¥¹¾ðÊó¤Î¼ý½¸¤Ï¥µ¡¼¥Ð¤Î + Æ°ºî¤òÃÙ¤¯¤¹¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_status.html.ko.euc-kr b/docs/manual/mod/mod_status.html.ko.euc-kr new file mode 100644 index 00000000..e64148cc --- /dev/null +++ b/docs/manual/mod/mod_status.html.ko.euc-kr @@ -0,0 +1,148 @@ + + + +mod_status - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_status

+
+

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

+
+ + + +
¼³¸í:¼­¹ö È°µ¿°ú ¼º´É¿¡ ´ëÇÑ Á¤º¸¸¦ Á¦°øÇÑ´Ù
»óÅÂ:Base
¸ðµâ¸í:status_module
¼Ò½ºÆÄÀÏ:mod_status.c
+

¿ä¾à

+ +

Status ¸ðµâÀº ¼­¹ö °ü¸®ÀÚ¿¡°Ô ¼­¹öÀÇ »óŸ¦ º¸¿©ÁØ´Ù. + ½±°Ô ÀÐÀ» ¼ö ÀÖ´Â HTML ÆäÀÌÁö·Î ÇöÀç ¼­¹öÅë°è¸¦ º¸¿©ÁØ´Ù. + ÇÊ¿äÇÏ´Ù¸é (Ç¥ÁØÀ» µû¸£´Â ºê¶ó¿ìÀú¿¡¼­) ÆäÀÌÁö¸¦ ÀÚµ¿À¸·Î + °»½ÅÇÒ ¼ö ÀÖ´Ù. ÇöÀç ¼­¹ö »óŸ¦ ÄÄÇ»ÅÍ°¡ ÀÐÀ» ¼ö ÀÖ´Â + °£´ÜÇÑ ¸ñ·ÏÀ¸·Î º¸¿©ÁÙ ¼öµµ ÀÖ´Ù.

+ +

¾Ë·ÁÁÖ´Â Á¤º¸´Â:

+ +
    +
  • ¿äûÀ» ¼­ºñ½ºÇÏ´Â workerÀÇ °³¼ö
    • + +
  • ½¬°í ÀÖ´Â(idle) workerÀÇ °³¼ö
    • + +
  • °¢ workerµéÀÇ »óÅÂ, worker°¡ ó¸®ÇÑ ¿äûÀÇ °³¼ö¿Í + worker°¡ ¼­ºñ½ºÇÑ Àüü ¹ÙÀÌÆ®¼ö (*)
    • + +
  • ÃÑ Á¢±Ù Ƚ¼ö¿Í ¼­ºñ½ºÇÑ ¹ÙÀÌÆ®¼ö (*)
    • + +
  • ¼­¹ö°¡ ½ÃÀÛȤÀº Àç½ÃÀÛÇÑ ½Ã°£°ú µ¿ÀÛÇÑ ½Ã°£
    • + +
  • ÃÊ´ç ¿äû¼ö Æò±Õ, ÃÊ´ç ¼­ºñ½ºÇÑ ¹ÙÀÌÆ®¼ö¿Í ¿äû´ç + ¹ÙÀÌÆ®¼ö Æò±Õ (*)
    • + +
  • ÇöÀç ¾ÆÆÄÄ¡ Àüü¿Í °¢ workerµéÀÇ CPU ºñÀ² (*)
    • + +
  • ÇöÀç ó¸®ÇÏ°í Àִ ȣ½ºÆ®¿Í ¿äû (*)
    • +
+ +

Ç¥ÁØ ¾ÆÆÄÄ¡¿¡´Â "(*)"·Î Ç¥½ÃÇÑ Åë°è¸¦ ¾òÀ» ¼ö ¾ø´Ù. + ÀÌ Á¤º¸¸¦ º¸·Á¸é ÄÄÆÄÀϽà ¿É¼ÇÀ» »ç¿ëÇØ¾ß ÇÑ´Ù.

+
+ +
top
+
+

Status »ç¿ëÇϱâ

+ + +

foo.com µµ¸ÞÀο¡¼­ Á¢±ÙÇÑ ºê¶ó¿ìÀú¿¡°Ô¸¸ »óŸ¦ º¸¿©ÁÖ·Á¸é + httpd.conf ¼³Á¤ÆÄÀÏ¿¡ ´ÙÀ½°ú °°ÀÌ Ãß°¡ÇÑ´Ù

+

+ <Location /server-status>
+ SetHandler server-status
+
+ Order Deny,Allow
+ Deny from all
+ Allow from .foo.com
+ </Location> +

+ +

ÀÌÁ¦ À¥ºê¶ó¿ìÀú·Î + http://your.server.name/server-status ÆäÀÌÁö¿¡ + Á¢±ÙÇÏ¸é ¼­¹ö Åë°è¸¦ º¼ ¼ö ÀÖ´Ù.

+
top
+
+

ÀÚµ¿ °»½Å

+ + +

ºê¶ó¿ìÀú°¡ "Àç°»½Å"À» Áö¿øÇÑ´Ù¸é status ÆäÀÌÁö¸¦ ÀÚµ¿À¸·Î + °»½ÅÇÒ ¼ö ÀÖ´Ù. N Ãʸ¶´Ù °»½ÅÇÏ·Á¸é + http://your.server.name/server-status?refresh=N + ÆäÀÌÁö¸¦ »ç¿ëÇ϶ó.

+ +
top
+
+

ÄÄÇ»ÅÍ°¡ ÀÐÀ» ¼ö ÀÖ´Â Status ÆÄÀÏ

+ + +

http://your.server.name/server-status?auto¿¡¼­ + ÄÄÇ»ÅÍ°¡ ½±°Ô ÀÐÀ» ¼ö ÀÖ´Â status ÆÄÀÏÀ» ¾òÀ» ¼ö ÀÖ´Ù. ÀÌ + Çü½ÄÀº ¾ÆÆÄÄ¡ /support µð·ºÅ丮¿¡ ÀÖ´Â + log_server_status Perl ÇÁ·Î±×·¥°ú °°ÀÌ ÀÚµ¿À¸·Î + ½ÇÇàÇÏ´Â ÇÁ·Î±×·¥¿¡ À¯¿ëÇÏ´Ù.

+ +
+ mod_status¸¦ ¼­¹ö¿Í °°ÀÌ + ÄÄÆÄÀÏÇÏ¿´´Ù¸é µð·ºÅ丮º° ¼³Á¤ÆÄÀÏÀ» (¿¹¸¦ + µé¾î, .htaccess) Æ÷ÇÔÇÏ¿© ¸ðµç + ¼³Á¤ÆÄÀÏ¿¡¼­ Çڵ鷯¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù. ±×·¡¼­ »çÀÌÆ®¿¡ + º¸¾È ¹®Á¦°¡ ¹ß»ýÇÒ ¼ö ÀÖ´Ù. +
+ +
+
top
+

ExtendedStatus Áö½Ã¾î

+ + + + + + + + +
¼³¸í:°¢ ¿äû¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ »óÅ Á¤º¸¸¦ ±â·ÏÇÑ´Ù
¹®¹ý:ExtendedStatus On|Off
±âº»°ª:ExtendedStatus Off
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤
»óÅÂ:Base
¸ðµâ:mod_status
Áö¿ø:ExtendedStatus´Â ¾ÆÆÄÄ¡ 1.3.2 ÀÌÈÄ¿¡¸¸ ÀÖ´Ù.
+

ÀÌ ¼³Á¤Àº ¼­¹ö Àüü¿¡ Àû¿ëµÇ¸ç, °¡»óÈ£½ºÆ®º°·Î Å°°í ²ø + ¼ö ¾ø´Ù. ÀÚ¼¼ÇÑ »óÅ Á¤º¸¸¦ ¸ðÀ¸¸é ¼­¹ö°¡ ´À·ÁÁú ¼ö ÀÖ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_suexec.html b/docs/manual/mod/mod_suexec.html new file mode 100644 index 00000000..4be81b75 --- /dev/null +++ b/docs/manual/mod/mod_suexec.html @@ -0,0 +1,11 @@ +URI: mod_suexec.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_suexec.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_suexec.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_suexec.html.en b/docs/manual/mod/mod_suexec.html.en new file mode 100644 index 00000000..440ff462 --- /dev/null +++ b/docs/manual/mod/mod_suexec.html.en @@ -0,0 +1,80 @@ + + + +mod_suexec - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_suexec

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Allows CGI scripts to run as a specified user +and Group
Status:Extension
Module Identifier:suexec_module
Source File:mod_suexec.c
Compatibility:Available in Apache 2.0 and later
+

Summary

+ +

This module, in combination with the suexec support program allows + CGI scripts to run as a specified user and Group.

+
+

Directives

+ +

See also

+
+ +
top
+

SuexecUserGroup Directive

+ + + + + + + +
Description:User and group permissions for CGI programs
Syntax:SuexecUserGroup User Group
Context:server config, virtual host
Status:Extension
Module:mod_suexec
Compatibility:SuexecUserGroup is only available in 2.0 and +later.
+

The SuexecUserGroup directive allows you + to specify a user and group for CGI programs to run as. Non-CGI + requests are still processes with the user specified in the User + directive. This directive replaces the Apache 1.3 configuration of + using the User and Group directives inside of VirtualHosts.

+ +

Example

+ + SuexecUserGroup nobody nogroup +

+ + +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_suexec.html.ja.euc-jp b/docs/manual/mod/mod_suexec.html.ja.euc-jp new file mode 100644 index 00000000..34df4c91 --- /dev/null +++ b/docs/manual/mod/mod_suexec.html.ja.euc-jp @@ -0,0 +1,79 @@ + + + +mod_suexec - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_suexec

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
ÀâÌÀ:»ØÄꤵ¤ì¤¿¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤Ç CGI ¥¹¥¯¥ê¥×¥È¤ò¼Â¹Ô¤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:³ÈÄ¥
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:suexec_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_suexec.c
¸ß´¹À­:Apache 2.0 °Ê¹ß¤Ç»ÈÍѲÄǽ
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤È suexec ¥µ¥Ý¡¼¥È¥×¥í¥°¥é¥à + ¤Ë¤è¤ê¡¢CGI ¥¹¥¯¥ê¥×¥È¤¬»ØÄꤵ¤ì¤¿¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤Ç + ¼Â¹Ô¤µ¤ì¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +

»²¾È

+
+ +
top
+

SuexecUserGroup ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:CGI ¥×¥í¥°¥é¥à¤Î¥æ¡¼¥¶¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¡¢¥°¥ë¡¼¥×¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó
¹½Ê¸:SuexecUserGroup User Group
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:³ÈÄ¥
¥â¥¸¥å¡¼¥ë:mod_suexec
¸ß´¹À­:SuexecUserGroup ¤Ï 2.0 °Ê¹ß¤Ç¤Î¤ß»ÈÍѲÄǽ¡£
+

SuexecUserGroup ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï CGI ¥×¥í¥°¥é¥à + ¤¬¼Â¹Ô¤µ¤ì¤ë¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤ò»ØÄê¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£CGI °Ê³°¤Î + ¥ê¥¯¥¨¥¹¥È¤Ï User ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿¥æ¡¼¥¶¤Î¤Þ¤Þ¤Ç½èÍý¤µ¤ì¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache 1.3 ¤Ë¤ª¤±¤ë VirtualHosts ¤ÎÃæ¤Ç + User ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È Group ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦ÍÑË¡¤ÎÂå¤ï¤ê¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Îã

+ + SuexecUserGroup nobody nogroup +

+ + +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_suexec.html.ko.euc-kr b/docs/manual/mod/mod_suexec.html.ko.euc-kr new file mode 100644 index 00000000..48c488fa --- /dev/null +++ b/docs/manual/mod/mod_suexec.html.ko.euc-kr @@ -0,0 +1,81 @@ + + + +mod_suexec - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_suexec

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:CGI ½ºÅ©¸³Æ®¸¦ ƯÁ¤ »ç¿ëÀÚ¿Í ±×·ì ±ÇÇÑÀ¸·Î ½ÇÇàÇÑ´Ù
»óÅÂ:Extension
¸ðµâ¸í:suexec_module
¼Ò½ºÆÄÀÏ:mod_suexec.c
Áö¿ø:¾ÆÆÄÄ¡ 2.0 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀº suexec Áö¿ø + ÇÁ·Î±×·¥À» »ç¿ëÇÏ¿© CGI ½ºÅ©¸³Æ®¸¦ ƯÁ¤ »ç¿ëÀÚ¿Í ±×·ì + ±ÇÇÑÀ¸·Î ½ÇÇàÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +

Âü°í

+
+ +
top
+

SuexecUserGroup Áö½Ã¾î

+ + + + + + + +
¼³¸í:CGI ÇÁ·Î±×·¥ÀÌ »ç¿ëÇÒ »ç¿ëÀÚ¿Í ±×·ì ±ÇÇÑ
¹®¹ý:SuexecUserGroup User Group
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Extension
¸ðµâ:mod_suexec
Áö¿ø:SuexecUserGroupÀº 2.0 ÀÌÈÄ¿¡¸¸ ÀÖ´Ù.
+

SuexecUserGroup Áö½Ã¾î´Â CGI ÇÁ·Î±×·¥ÀÌ + »ç¿ëÇÒ »ç¿ëÀÚ¿Í ±×·ìÀ» ¼³Á¤ÇÑ´Ù. CGI°¡ ¾Æ´Ñ ¿äûÀº °è¼Ó + User Áö½Ã¾î·Î ÁöÁ¤ÇÑ »ç¿ëÀÚ°¡ ó¸®ÇÑ´Ù. ÀÌ Áö½Ã¾î´Â ¾ÆÆÄÄ¡ + 1.3¿¡¼­ VirtualHost ¾È¿¡ »ç¿ëÇÑ User¿Í Group Áö½Ã¾î¸¦ + ´ëüÇÑ´Ù.

+ +

¿¹Á¦

+ + SuexecUserGroup nobody nogroup +

+ + +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_unique_id.html b/docs/manual/mod/mod_unique_id.html new file mode 100644 index 00000000..1dae85cf --- /dev/null +++ b/docs/manual/mod/mod_unique_id.html @@ -0,0 +1,11 @@ +URI: mod_unique_id.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_unique_id.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_unique_id.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_unique_id.html.en b/docs/manual/mod/mod_unique_id.html.en new file mode 100644 index 00000000..40872ffb --- /dev/null +++ b/docs/manual/mod/mod_unique_id.html.en @@ -0,0 +1,216 @@ + + + +mod_unique_id - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_unique_id

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:Provides an environment variable with a unique +identifier for each request
Status:Extension
Module Identifier:unique_id_module
Source File:mod_unique_id.c
+

Summary

+ + +

This module provides a magic token for each request which is + guaranteed to be unique across "all" requests under very + specific conditions. The unique identifier is even unique + across multiple machines in a properly configured cluster of + machines. The environment variable UNIQUE_ID is + set to the identifier for each request. Unique identifiers are + useful for various reasons which are beyond the scope of this + document.

+
+

Directives

+

This module provides no + directives.

+

Topics

+
+
top
+
+

Theory

+ + +

First a brief recap of how the Apache server works on Unix + machines. This feature currently isn't supported on Windows NT. + On Unix machines, Apache creates several children, the children + process requests one at a time. Each child can serve multiple + requests in its lifetime. For the purpose of this discussion, + the children don't share any data with each other. We'll refer + to the children as httpd processes.

+ +

Your website has one or more machines under your + administrative control, together we'll call them a cluster of + machines. Each machine can possibly run multiple instances of + Apache. All of these collectively are considered "the + universe", and with certain assumptions we'll show that in this + universe we can generate unique identifiers for each request, + without extensive communication between machines in the + cluster.

+ +

The machines in your cluster should satisfy these + requirements. (Even if you have only one machine you should + synchronize its clock with NTP.)

+ +
    +
  • The machines' times are synchronized via NTP or other + network time protocol.
    • + +
  • The machines' hostnames all differ, such that the module + can do a hostname lookup on the hostname and receive a + different IP address for each machine in the cluster.
    • +
+ +

As far as operating system assumptions go, we assume that + pids (process ids) fit in 32-bits. If the operating system uses + more than 32-bits for a pid, the fix is trivial but must be + performed in the code.

+ +

Given those assumptions, at a single point in time we can + identify any httpd process on any machine in the cluster from + all other httpd processes. The machine's IP address and the pid + of the httpd process are sufficient to do this. So in order to + generate unique identifiers for requests we need only + distinguish between different points in time.

+ +

To distinguish time we will use a Unix timestamp (seconds + since January 1, 1970 UTC), and a 16-bit counter. The timestamp + has only one second granularity, so the counter is used to + represent up to 65536 values during a single second. The + quadruple ( ip_addr, pid, time_stamp, counter ) is + sufficient to enumerate 65536 requests per second per httpd + process. There are issues however with pid reuse over time, and + the counter is used to alleviate this issue.

+ +

When an httpd child is created, the counter is initialized + with ( current microseconds divided by 10 ) modulo 65536 (this + formula was chosen to eliminate some variance problems with the + low order bits of the microsecond timers on some systems). When + a unique identifier is generated, the time stamp used is the + time the request arrived at the web server. The counter is + incremented every time an identifier is generated (and allowed + to roll over).

+ +

The kernel generates a pid for each process as it forks the + process, and pids are allowed to roll over (they're 16-bits on + many Unixes, but newer systems have expanded to 32-bits). So + over time the same pid will be reused. However unless it is + reused within the same second, it does not destroy the + uniqueness of our quadruple. That is, we assume the system does + not spawn 65536 processes in a one second interval (it may even + be 32768 processes on some Unixes, but even this isn't likely + to happen).

+ +

Suppose that time repeats itself for some reason. That is, + suppose that the system's clock is screwed up and it revisits a + past time (or it is too far forward, is reset correctly, and + then revisits the future time). In this case we can easily show + that we can get pid and time stamp reuse. The choice of + initializer for the counter is intended to help defeat this. + Note that we really want a random number to initialize the + counter, but there aren't any readily available numbers on most + systems (i.e., you can't use rand() because you need + to seed the generator, and can't seed it with the time because + time, at least at one second resolution, has repeated itself). + This is not a perfect defense.

+ +

How good a defense is it? Suppose that one of your machines + serves at most 500 requests per second (which is a very + reasonable upper bound at this writing, because systems + generally do more than just shovel out static files). To do + that it will require a number of children which depends on how + many concurrent clients you have. But we'll be pessimistic and + suppose that a single child is able to serve 500 requests per + second. There are 1000 possible starting counter values such + that two sequences of 500 requests overlap. So there is a 1.5% + chance that if time (at one second resolution) repeats itself + this child will repeat a counter value, and uniqueness will be + broken. This was a very pessimistic example, and with real + world values it's even less likely to occur. If your system is + such that it's still likely to occur, then perhaps you should + make the counter 32 bits (by editing the code).

+ +

You may be concerned about the clock being "set back" during + summer daylight savings. However this isn't an issue because + the times used here are UTC, which "always" go forward. Note + that x86 based Unixes may need proper configuration for this to + be true -- they should be configured to assume that the + motherboard clock is on UTC and compensate appropriately. But + even still, if you're running NTP then your UTC time will be + correct very shortly after reboot.

+ +

The UNIQUE_ID environment variable is + constructed by encoding the 112-bit (32-bit IP address, 32 bit + pid, 32 bit time stamp, 16 bit counter) quadruple using the + alphabet [A-Za-z0-9@-] in a manner similar to MIME + base64 encoding, producing 19 characters. The MIME base64 + alphabet is actually [A-Za-z0-9+/] however + + and / need to be specially encoded + in URLs, which makes them less desirable. All values are + encoded in network byte ordering so that the encoding is + comparable across architectures of different byte ordering. The + actual ordering of the encoding is: time stamp, IP address, + pid, counter. This ordering has a purpose, but it should be + emphasized that applications should not dissect the encoding. + Applications should treat the entire encoded + UNIQUE_ID as an opaque token, which can be + compared against other UNIQUE_IDs for equality + only.

+ +

The ordering was chosen such that it's possible to change + the encoding in the future without worrying about collision + with an existing database of UNIQUE_IDs. The new + encodings should also keep the time stamp as the first element, + and can otherwise use the same alphabet and bit length. Since + the time stamps are essentially an increasing sequence, it's + sufficient to have a flag second in which all machines + in the cluster stop serving and request, and stop using the old + encoding format. Afterwards they can resume requests and begin + issuing the new encodings.

+ +

This we believe is a relatively portable solution to this + problem. It can be extended to multithreaded systems like + Windows NT, and can grow with future needs. The identifiers + generated have essentially an infinite life-time because future + identifiers can be made longer as required. Essentially no + communication is required between machines in the cluster (only + NTP synchronization is required, which is low overhead), and no + communication between httpd processes is required (the + communication is implicit in the pid value assigned by the + kernel). In very specific situations the identifier can be + shortened, but more information needs to be assumed (for + example the 32-bit IP address is overkill for any site, but + there is no portable shorter replacement for it).

+
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_unique_id.html.ja.euc-jp b/docs/manual/mod/mod_unique_id.html.ja.euc-jp new file mode 100644 index 00000000..a34f57f9 --- /dev/null +++ b/docs/manual/mod/mod_unique_id.html.ja.euc-jp @@ -0,0 +1,214 @@ + + + +mod_unique_id - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_unique_id

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:¤½¤ì¤¾¤ì¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë°ì°Õ¤Ê¼±Ê̻ҤÎÆþ¤Ã¤¿´Ä¶­ÊÑ¿ô¤ò +Ä󶡤¹¤ë
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:unique_id_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_unique_id.c
+

³µÍ×

+ + +

¤³¤Î¥â¥¸¥å¡¼¥ë¤ÏÈó¾ï¤ËÀ©¸Â¤µ¤ì¤¿¾ò·ï²¼¤Ç¡¢ + ¤½¤ì¤¾¤ì¤Î¥ê¥¯¥¨¥¹¥È¤Ë¡Ö¤¹¤Ù¤Æ¡×¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ + °ì°Õ¤Ë·è¤Þ¤ë¤³¤È¤¬Êݾڤµ¤ì¤Æ¤¤¤ëËâË¡¤Î¥È¡¼¥¯¥ó¤òÄ󶡤·¤Þ¤¹¡£ + ¤³¤Î°ì°Õ¤Ê¼±Ê̻Ҥϡ¢Å¬ÀÚ¤ËÀßÄꤵ¤ì¤¿¥¯¥é¥¹¥¿¤Ç¤ÏÊ£¿ô¤Î + ¥Þ¥·¥ó¤Î´Ö¤Ç¤µ¤¨¤â°ì°Õ¤Ë¤Ê¤ê¤Þ¤¹¡£¤½¤ì¤¾¤ì¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ´Ä¶­ÊÑ¿ô + UNIQUE_ID ¤Ë¼±Ê̻Ҥ¬ÀßÄꤵ¤ì¤Þ¤¹¡£ + °ì°Õ¤Ê¼±Ê̻Ҥ¬ÊØÍø¤ÊÍýͳ¤Ï¤¤¤í¤¤¤í¤¢¤ê¤Þ¤¹¤¬¡¢ + ¤³¤Î¥É¥­¥å¥á¥ó¥È¤ÎÌÜŪ¤«¤é¤Ï³°¤ì¤ë¤¿¤á¡¢¤³¤³¤Ç¤ÏÀâÌÀ¤·¤Þ¤»¤ó¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+

¥È¥Ô¥Ã¥¯

+
+
top
+
+

ÍýÏÀ

+ + +

¤Þ¤º¤Ï¤¸¤á¤Ë¡¢Apache ¥µ¡¼¥Ð¤¬ Unix + ¥Þ¥·¥ó¤Ç¤É¤Î¤è¤¦¤ËÆ°ºî¤ò¤¹¤ë¤«¤ò´Êñ¤ËÀâÌÀ¤·¤Þ¤¹¡£ + ¤³¤Îµ¡Ç½¤Ï¸½»þÅÀ¤Ç¤Ï Windows NT ¤Ç¤Ï¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£ + Unix ¥Þ¥·¥ó¤Ç¤Ï Apache ¤Ï¤¤¤¯¤Ä¤«¤Î»Ò¥×¥í¥»¥¹¤òºîÀ®¤·¡¢ + ¤½¤Î»Ò¥×¥í¥»¥¹¤¬°ì¤Ä¤º¤Ä¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤·¤Þ¤¹¡£¤½¤ì¤¾¤ì¤Î»Ò¥×¥í¥»¥¹¤Ï¡¢ + À¸Â¸´ü´ÖÃæ¤ËÊ£¿ô¤Î¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ÎµÄÏÀ¤Ç¤Ï»Ò¥×¥í¥»¥¹´Ö¤Ç¤Ï°ìÀڥǡ¼¥¿¤ò¶¦Í­¤·¤Ê¤¤¤³¤È¤Ë¤·¤Þ¤¹¡£ + °Ê¸å¡¢¤³¤Î»Ò¥×¥í¥»¥¹¤Î¤³¤È¤ò httpd ¥×¥í¥»¥¹ ¤È¸Æ¤Ó¤Þ¤¹¡£

+ +

¤¢¤Ê¤¿¤Î¥¦¥§¥Ö¥µ¥¤¥È¤Ë¤Ï¤¢¤Ê¤¿¤¬´ÉÍý¤¹¤ë¤¤¤¯¤Ä¤«¤Î¥Þ¥·¥ó¤¬¤¢¤ë¤È¤·¤Þ¤¹¡£ + ¤½¤ì¤é¤ò¤Þ¤È¤á¤Æ¥¯¥é¥¹¥¿¤È¸Æ¤Ö¤³¤È¤Ë¤·¤Þ¤¹¡£¤½¤ì¤¾¤ì¤Î¥Þ¥·¥ó¤ÏÊ£¿ô¤Î + Apache ¤ò¼Â¹Ô¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤é¤¹¤Ù¤Æ¤ò¤Þ¤È¤á¤¿¤â¤Î¤¬¡Ö±§Ãè¡×¤Ç¤¢¤ë¤È¹Í¤¨¤é¤ì¤Þ¤¹¡£ + ¤¤¤¯¤Ä¤«¤Î²¾Äê¤Î²¼¤Ç¡¢¥¯¥é¥¹¥¿¤Î¥Þ¥·¥ó´Ö¤¬¤¿¤¯¤µ¤óÄÌ¿®¤ò¤¹¤ë¤³¤È¤Ê¤¯¡¢ + ¤³¤Î±§Ãè¤ÎÃæ¤Ç¤½¤ì¤¾¤ì¤Î¥ê¥¯¥¨¥¹¥È¤Ë°ì°Õ¤Ê¼±Ê̻ҤòÀ¸À®¤Ç¤­¤ë¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ +

+ +

¥¯¥é¥¹¥¿¤Ë¤¢¤ë¥Þ¥·¥ó¤Ï°Ê²¼¤ÎÍ×µá¤ò¸«¤¿¤µ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + (¥Þ¥·¥ó¤¬°ì¤Ä¤À¤±¤À¤È¤·¤Æ¤â¡¢NTP ¤Ç»þ·×¤ò¹ç¤ï¤»¤ëÊý¤¬Îɤ¤¤Ç¤¹¡£)

+ +
    +
  • NTP ¤ä¾¤Î¥Í¥Ã¥È¥ï¡¼¥¯¾å¤Ç»þ´Ö¤ò¹ç¤ï¤»¤ë¥×¥í¥È¥³¥ë¤Ë¤è¤Ã¤Æ + ³Æ¥Þ¥·¥ó¤Î»þ´Ö¤ÎƱ´ü¤¬¼è¤é¤ì¤Æ¤¤¤ë¤³¤È¡£
    • + +
  • ¥â¥¸¥å¡¼¥ë¤¬¥Û¥¹¥È̾¤ò°ú¤¤¤Æ°ã¤¦ IP + ¥¢¥É¥ì¥¹¤ò¼õ¤±¼è¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¡¢ + ¥¯¥é¥¹¥¿¤Î¤½¤ì¤¾¤ì¤Î¥Þ¥·¥ó¤Î¥Û¥¹¥È̾¤¬°ã¤¦¤³¤È¡£
    • +
+ +

¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ë¤ª¤¤¤Æ¤Ï¡¢pid (¥×¥í¥»¥¹ ID) ¤¬ + 32 ¥Ó¥Ã¥È¤ÎÈÏ°ÏÆâ¤Ç¤¢¤ë¤³¤È¤ò²¾Äꤷ¤Þ¤¹¡£¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î + pid ¤¬ 32 ¥Ó¥Ã¥È¤òĶ¤¨¤ë¾ì¹ç¤Ï¡¢´Êñ¤Ê½¤Àµ¤Ç¤Ï¤¢¤ê¤Þ¤¹¤¬¡¢ + ¥³¡¼¥É¤òÊѹ¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

¤³¤ì¤é¤Î²¾Ä꤬Ëþ¤¿¤µ¤ì¤Æ¤¤¤ë¤È¡¢¤¢¤ë»þÅÀ¤Ë¤ª¤¤¤Æ¡¢ + ¥¯¥é¥¹¥¿Æâ¤Î¤É¤Î¥Þ¥·¥ó¤Î¤É¤Î httpd + ¥×¥í¥»¥¹¤Ç¤â¡¢°ì°Õ¤ËƱÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤Ï¥Þ¥·¥ó¤Î IP + ¥¢¥É¥ì¥¹¤È httpd ¥×¥í¥»¥¹¤Î pid ¤Ç½½Ê¬¤Ë¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢¥ê¥¯¥¨¥¹¥È¤Ë°ì°Õ¤Ê¼±Ê̻ҤòÀ¸À®¤¹¤ë¤¿¤á¤Ë¤Ï¡¢ + »þ¹ï¤ò¶èÊ̤¹¤ëɬÍפ¬¤¢¤ë¤À¤±¤Ç¤¹¡£

+ +

»þ¹ï¤ò¶èÊ̤¹¤ë¤¿¤á¤Ë¡¢Unix ¤Î¥¿¥¤¥à¥¹¥¿¥ó¥× (UTC ¤Î 1970 ǯ + 1 ·î 1 Æü¤«¤é¤ÎÉÿô) ¤È¡¢16 ¥Ó¥Ã¥È¤Î¥«¥¦¥ó¥¿¤ò»È¤¤¤Þ¤¹¡£ + ¥¿¥¤¥à¥¹¥¿¥ó¥×¤ÎγÅ٤ϰìÉäǤ¹¤Î¤Ç¡¢°ìÉô֤Π65536 + ¤Þ¤Ç¤ÎÃͤòɽ¸½¤¹¤ë¤¿¤á¤Ë¥«¥¦¥ó¥¿¤ò»ÈÍѤ·¤Þ¤¹¡£»Í¤Ä¤ÎÃÍ + ( ip_addr, pid, time_stamp, counter ) ¤Ç³Æ httpd + ¥×¥í¥»¥¹¤Ç°ìÉÃ¤Î´Ö¤Ë 65536 ¥ê¥¯¥¨¥¹¥È¤ò¿ô¤¨¤¢¤²¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + »þ´Ö¤¬·Ð¤Ä¤È pid ¤¬ºÆÍøÍѤµ¤ì¤ë¤È¤¤¤¦ÌäÂ꤬¤¢¤ê¤Þ¤¹¤¬¡¢ + ¤³¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Ë¥«¥¦¥ó¥¿¤¬»ÈÍѤµ¤ì¤Þ¤¹¡£

+ +

httpd ¤Î»Ò¥×¥í¥»¥¹¤¬ºîÀ®¤µ¤ì¤ë¤È¡¢¥«¥¦¥ó¥¿¤Ï + (¤½¤Î»þÅÀ¤Î¥Þ¥¤¥¯¥íÉà ¡à 10) modulo 65536 ¤Ç½é´ü²½¤µ¤ì¤Þ¤¹ + (¤³¤Î¼°¤Ï¤¤¤¯¤Ä¤«¤Î¥·¥¹¥Æ¥à¤Ë¤¢¤ë¡¢¥Þ¥¤¥¯¥íÉäΠ+ ¥¿¥¤¥Þ¤Î²¼°Ì¥Ó¥Ã¥È¤¬°Û¤Ê¤ë¤È¤¤¤¦ÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤ËÁª¤Ð¤ì¤Þ¤·¤¿)¡£ + °ì°Õ¤Ê¼±Ê̻Ҥ¬À¸À®¤µ¤ì¤¿¤È¤­¡¢»ÈÍѤµ¤ì¤ë¥¿¥¤¥à¥¹¥¿¥ó¥×¤Ï + ¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë¥ê¥¯¥¨¥¹¥È¤¬ÅþÃ夷¤¿»þ¹ï¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¥«¥¦¥ó¥¿¤Ï¼±Ê̻Ҥ¬À¸À®¤µ¤ì¤ë¤¿¤Ó¤ËÁý²Ã¤·¤Þ¤¹ + (¤¢¤Õ¤ì¤¿¾ì¹ç¤Ï 0 ¤ËÌá¤ê¤Þ¤¹)¡£

+ +

¥«¡¼¥Í¥ë¤Ï¥×¥í¥»¥¹¤ò¥Õ¥©¡¼¥¯¤¹¤ë¤È¡¢¤½¤ì¤¾¤ì¤Î¥×¥í¥»¥¹¤Î¤¿¤á¤Ë + pid ¤òÀ¸À®¤·¤Þ¤¹¡£pid ¤Ï·«¤êÊÖ¤µ¤ì¤ë¤³¤È¤¬µö²Ä¤µ¤ì¤Æ¤¤¤Þ¤¹ + (pid ¤ÎÃͤÏ¿¤¯¤Î Unix ¤Ç¤Ï 16 ¥Ó¥Ã¥È¤Ç¤¹¤¬¡¢¿·¤·¤¤¥·¥¹¥Æ¥à¤Ç¤Ï + 32 ¥Ó¥Ã¥È¤Ë³ÈÄ¥¤µ¤ì¤Æ¤¤¤Þ¤¹)¡£ + ¤Ç¤¹¤«¤é¡¢¤¢¤ëÄøÅ٤λþ´Ö¤¬·Ð²á¤¹¤ë¤ÈƱ¤¸ pid ¤¬ºÆ¤Ó»ÈÍѤµ¤ì¤Þ¤¹¡£ + ¤·¤«¤·¡¢°ìÉÃÆâ¤ËºÆ»ÈÍѤµ¤ì¤Ê¤±¤ì¤Ð¡¢ + »Í¤Ä¤ÎÃͤΰì°ÕÀ­¤ÏÊݤ¿¤ì¤Þ¤¹¡£¤Ä¤Þ¤ê¡¢²æ¡¹¤Ï¥·¥¹¥Æ¥à¤¬°ìÉÃ´Ö + ¤Ë 65536 ¸Ä¤Î¥×¥í¥»¥¹¤òµ¯Æ°¤·¤Ê¤¤¤È²¾Äꤷ¤Æ¤¤¤Þ¤¹ (¤¤¤¯¤Ä¤«¤Î Unix + ¤Ç¤Ï 32768 ¥×¥í¥»¥¹¤Ç¤¹¤¬¡¢¤½¤ì¤Ç¤¹¤é¤Û¤È¤ó¤É¤¢¤êÆÀ¤Ê¤¤¤Ç¤·¤ç¤¦)¡£

+ +

²¿¤é¤«¤ÎÍýͳ¤Ç¡¢Æ±¤¸»þ¹ï¤¬·«¤êÊÖ¤µ¤ì¤¿¤È¤·¤Þ¤·¤ç¤¦¡£ + ¤Ä¤Þ¤ê¡¢¥·¥¹¥Æ¥à¤Î»þ·×¤¬¶¸¤Ã¤Æ¤¤¤Æ¡¢¤â¤¦°ìÅÙ²áµî¤Î»þ¹ï¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤¿ + (¤â¤·¤¯¤Ï¿Ê¤ß¤¹¤®¤Æ¤¤¤¿¤È¤­¤Ë¡¢ + Àµ¤·¤¤»þ¹ï¤ËÌᤷ¤¿¤¿¤á¤ËºÆ¤Ó¾­Íè¤Î»þ¹ï¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤¿) ¤È¤·¤Þ¤¹¡£ + ¤³¤Î¾ì¹ç¡¢pid ¤È¥¿¥¤¥à¥¹¥¿¥ó¥×¤¬ºÆ»ÈÍѤµ¤ì¤ë¤³¤È¤¬´Êñ¤Ë¼¨¤µ¤ì¤Þ¤¹¡£ + ¥«¥¦¥ó¥¿½é´ü²½ÍѤδؿô¤Ï¡¢¤³¤ÎÌäÂê¤Î²óÈò¤ò¼ê½õ¤±¤·¤è¤¦¤ÈÁªÂò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ËÜÅö¤Ï¥«¥¦¥ó¥¿¤Î½é´ü²½¤ò¤¹¤ë¤¿¤á¤Ë¥é¥ó¥À¥à¤Ê¿ô»ú¤ò»È¤¤¤¿¤¤¤Î¤Ç¤¹¤¬¡¢ + ¤Û¤È¤ó¤É¤Î¥·¥¹¥Æ¥à¤Ç¤Ï´Êñ¤Ë»ÈÍѤǤ­¤ë¿ô¤Ï̵¤¤¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤ + (¤¹¤Ê¤ï¤Á¡¢rand ()¤Ï»È¤¨¤Þ¤»¤ó¡£rand () ¤Ë¤Ï seed + ¤òÍ¿¤¨¤ëɬÍפ¬¤¢¤ê¡¢seed ¤Ë¤Ï»þ¹ï¤ò»È¤¨¤Þ¤»¤ó¡£°ìÉÃñ°Ì¤Ç¤Ï¡¢ + ¤½¤Î»þ¹ï¤Ï¤¹¤Ç¤Ë·«¤êÊÖ¤µ¤ì¤Æ¤¤¤ë¤«¤é¤Ç¤¹)¡£ + ¤³¤ì¤Ï¡¢´°àú¤ÊÂкö¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +

¤³¤ÎÂкö¤Ï¤É¤Î¤¯¤é¤¤¸ú²Ì¤¬¤¢¤ë¤Ç¤·¤ç¤¦¤«? + ¤³¤³¤Ç¤Ï¡¢¥Þ¥·¥ó·²¤ÎÃæ¤Î°ì¤Ä¤ÏºÇÂç¤Ç°ìÉÃ¤Ë 500 + ¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤È²¾Äꤷ¤Þ¤¹ (¤³¤ì¤ò½ñ¤¤¤Æ¤¤¤ë»þÅÀ¤Ç¤ÏÂÅÅö¤Ê¾å¸Â¤Ç¤¹¡£ + Ä̾亮¥¹¥Æ¥à¤¬¤¹¤ë¤³¤È¤ÏÀÅŪ¤Ê¥Õ¥¡¥¤¥ë¤ò¼è¤ê¤À¤¹¤À¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤«¤é)¡£ + ¤½¤ì¤ò¹Ô¤Ê¤¦¤¿¤á¤Ë¡¢¤½¤Î¥Þ¥·¥ó¤ÏʹԤ·¤ÆÍè¤ë¥¯¥é¥¤¥¢¥ó¥È¤Î¿ô¤Ë + ±þ¤¸¤¿¿ô¤Î»Ò¥×¥í¥»¥¹¤òÍ׵ᤷ¤Þ¤¹¡£ + ¤·¤«¤·¤Ê¤¬¤é¡¢Èá´ÑŪ¤Ë¹Í¤¨¤Æ¡¢°ì¤Ä¤Î»Ò¥×¥í¥»¥¹¤¬°ìÉÃ¤Ë 500 + ¥ê¥¯¥¨¥¹¥È¤ò°·¤¨¤ë¤È¤·¤Þ¤¹¡£¤½¤¦¤¹¤ë¤È¡¢(°ìÉäÎÀºÅ٤ˤª¤¤¤Æ) + »þ¹ï¤¬Æ±¤¸»þ¤ò·«¤êÊÖ¤¹¤È¡¢¤³¤Î»Ò¥×¥í¥»¥¹¤¬¥«¥¦¥ó¥¿¤ÎÃͤòºÆ¤Ó»È¤¤¡¢ + °ì°ÕÀ­¤¬²õ¤ì¤ë²ÄǽÀ­¤¬ 1.5% ¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤ÏÈó¾ï¤ËÈá´ÑŪ¤ÊÎã¤Ç¡¢¼ÂÀ¤³¦¤ÎÃͤǤϡ¢¤Û¤È¤ó¤Éµ¯¤³¤ê¤½¤¦¤Ë¤¢¤ê¤Þ¤»¤ó¡£ + ¤½¤ì¤Ç¤â¤³¤ì¤¬µ¯¤³¤ë²ÄǽÀ­¤Î¤¢¤ë¤è¤¦¤Ê¥·¥¹¥Æ¥à¤Ê¤é¡¢ + (¥×¥í¥°¥é¥à¥³¡¼¥É¤òÊÔ½¸¤·¤Æ) + ¥«¥¦¥ó¥¿¤ò 32 ¥Ó¥Ã¥È¤Ë¤¹¤ë¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£ +

+ +

¥µ¥Þ¡¼¥¿¥¤¥à¤Ë¤è¤ê»þ·×¤¬¡ÖÌᤵ¤ì¤ë¡×¤³¤È¤òµ¤¤Ë¤·¤Æ¤¤¤ë¿Í¤¬ + ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¤³¤³¤Ç»ÈÍѤµ¤ì¤ë»þ´Ö¤Ï UTC ¤Ç¤¢¤ê¡¢ + ¤½¤ì¤Ï¡Ö¾ï¤Ë¡×¿Ê¤à¤Î¤Ç¤³¤³¤Ç¤ÏÌäÂê¤Ë¤Ê¤ê¤Þ¤»¤ó¡£x86 ¾å¤Î Unix + ¤Ï¤³¤Î¾ò·ï¤òËþ¤¿¤¹¤¿¤á¤ËŬÀÚ¤ÊÀßÄ꤬ɬÍפ«¤â¤·¤ì¤Ê¤¤¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¥Þ¥¶¡¼¥Ü¡¼¥É¤Î»þ·×¤Ï UTC ¤Ë¤Ê¤Ã¤Æ¤¤¤Æ¡¢ + ¾¤Î»þ´Ö¤Ï¤½¤³¤«¤éŬÀÚ¤ËÊäÀµ¤µ¤ì¤ë¤³¤È¤ò²¾Äê¤Ç¤­¤ë¤è¤¦¤Ë + ÀßÄꤵ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤½¤Î¤è¤¦¤Ê¾ì¹ç¤Ç¤µ¤¨¡¢NTP + ¤ò»È¤Ã¤Æ¤¤¤ë¤Ê¤é¤Ð¥ê¥Ö¡¼¥È¸å¤Ë¤¹¤°Àµ¤·¤¤ UTC ¤Î»þ´Ö¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£

+ +

UNIQUE_ID ´Ä¶­ÊÑ¿ô¤Ï 112 ¥Ó¥Ã¥È (32 ¥Ó¥Ã¥È IP + ¥¢¥É¥ì¥¹¡¢32 ¥Ó¥Ã¥È pid, 32 ¥Ó¥Ã¥È¥¿¥¤¥à¥¹¥¿¥ó¥×¡¢16 + ¥Ó¥Ã¥È¥«¥¦¥ó¥¿¤Î»Í¤Ä¤ÎÁÈ) ¤ò¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È [A-Za-z0-9@-] + ¤òÍѤ¤¤Æ MIME ¤Î base64 Éä¹æ²½¤ÈƱÍͤÎÊýË¡¤Ë¤è¤êÉä¹æ²½¤·¡¢19 + ¤Îʸ»ú¤òÀ¸À®¤¹¤ë¤³¤È¤Ë¤è¤êºîÀ®¤µ¤ì¤Þ¤¹¡£MIME ¤Î base64 + ¤Î¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È¤Ï¼ÂºÝ¤Ï [A-Za-z0-9+/] ¤Ç¤¹¤¬¡¢ + + ¤È / ¤È¤Ï URL + ¤Ç¤ÏÆÃÊ̤ÊÉä¹æ²½¤¬É¬ÍפʤΤǡ¢¤¢¤Þ¤ê˾¤Þ¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£ + Á´¤Æ¤ÎÃͤϥͥåȥ¥¯¥Ð¥¤¥È¥ª¡¼¥À¤ÇÉä¹æ²½¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢ + Éä¹æ¤Ï°ã¤Ã¤¿¥Ð¥¤¥È¥ª¡¼¥À¤Î¥¢¡¼¥­¥Æ¥¯¥Á¥ã´Ö¤ÇÈæ³Ó²Äǽ¤Ç¤¹¡£ + ¼ÂºÝ¤ÎÉä¹æ²½¤Î½çÈÖ¤Ï: ¥¿¥¤¥à¥¹¥¿¥ó¥×¡¢IP ¥¢¥É¥ì¥¹¡¢pid, + ¥«¥¦¥ó¥¿¤Ç¤¹¡£¤³¤Î½ç¤Ë¤ÏÌÜŪ¤¬¤¢¤ê¤Þ¤¹¤¬¡¢ + ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ÏÉä¹æ¤ò²òÀϤ¹¤ë¤Ù¤­¤Ç¤Ï¤Ê¤¤¤³¤È¤ò¶¯Ä´¤·¤Æ¤ª¤­¤Þ¤¹¡£ + ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ÏÉä¹æ²½¤µ¤ì¤¿ UNIQUE_ID + Á´ÂΤòÆ©²áŪ¤Ê¥È¡¼¥¯¥ó¤È¤·¤Æ°·¤¦¤Ù¤­¤Ç¤¹¡£ + UNIQUE_ID ¤Ï¾¤Î UNIQUE_ID + ¤È¤ÎÅù²ÁÀ­¤òÄ´¤Ù¤ë¤¿¤á¤À¤±¤Ë¤Î¤ß»ÈÍѤǤ­¤Þ¤¹¡£

+ +

¤³¤Î½çÈ֤Ͼ­Íè¡¢´û¸¤Î UNIQUE_ID + ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤È¤Î¾×Æͤò¿´ÇÛ¤¹¤ë¤³¤È¤Ê¤¯Éä¹æ¤òÊѹ¹¤¹¤ë¤³¤È¤¬ + ²Äǽ¤Ë¤Ê¤ë¤è¤¦¤ËÁªÂò¤·¤Æ¤¤¤Þ¤¹¡£ + ¿·¤·¤¤Éä¹æ¤Ï¥¿¥¤¥à¥¹¥¿¥ó¥×¤òºÇ½é¤ÎÍ×ÁǤȤ·¤Æ»Ä¤¹¤Î¤¬Ë¾¤Þ¤·¤¯¡¢ + ¤½¤ì°Ê³°¤ÏƱ¤¸¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È¤È¥Ó¥Ã¥ÈŤò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¥¿¥¤¥à¥¹¥¿¥ó¥×¤ÏËܼÁŪ¤ËÁý²Ã·ÏÎó¤Ç¤¹¤Î¤Ç¡¢ + ¥¯¥é¥¹¥¿¤ÎÁ´¤Æ¤Î¥Þ¥·¥ó¤¬¥ê¥¯¥¨¥¹¥È¤È¥µ¡¼¥Ðµ¡Ç½¤òÄä»ß¤·¤Æ¡¢ + ¸Å¤¤Éä¹æ²½Êý¼°¤ò»ÈÍѤ¹¤ë¤Î¤ò¤ä¤á¤ë¥Õ¥é¥°É䬤¢¤ì¤Ð½½Ê¬¤Ç¤¹¡£ + ¤½¤Î¸å¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤òºÆ³«¤·¡¢ + ¿·¤·¤¤Éä¹æ¤òȯ¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

²æ¡¹¤Ï¤³¤ì¤¬¡¢ + ¤³¤ÎÌäÂê¤ËÂФ¹¤ëÈæ³ÓŪ°Ü¿¢À­¤Î¹â¤¤²ò·èË¡¤À¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£ + Windows NT ¤Î¤è¤¦¤Ê¥Þ¥ë¥Á¥¹¥ì¥Ã¥É¤Î¥·¥¹¥Æ¥à¤Ë³ÈÄ¥¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤·¡¢ + ¾­ÍèɬÍפˤʤì¤Ð¤µ¤é¤ËÁý¤ä¤¹¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + ID ¤ÏɬÍפ˱þ¤¸¤ÆŤ¯¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤Î¤Ç¡¢À¸À®¤µ¤ì¤¿ ID + ¤Ï¼Â¼Á¾å¡¢Ìµ¸Â¤ËÍ­¸ú¤Ç¤¹¡£¤Þ¤¿¡¢¥¯¥é¥¹¥¿¤Î¥Þ¥·¥ó´Ö¤ÎÄÌ¿®¤â»ö¼Â¾åɬÍפʤ¯ + (NTP ¤Ë¤è¤ëƱ´ü¤Î¤ß¤¬É¬Íפǡ¢¤³¤ì¤Ï¥ª¡¼¥Ð¥Ø¥Ã¥É¤Ï¤¢¤Þ¤ê¤¢¤ê¤Þ¤»¤ó)¡¢httpd + ¥×¥í¥»¥¹´Ö¤ÎÄÌ¿®¤âɬÍפ¢¤ê¤Þ¤»¤ó (ÄÌ¿®¤Ï¥«¡¼¥Í¥ë¤Ë¤è¤ê³ä¤êÅö¤Æ¤é¤ì¤¿ + pid ¤ÎÃͤˤè¤ê°ÅÌÛ¤ÎÆâ¤Ë¹Ô¤Ê¤ï¤Æ¤¤¤Þ¤¹)¡£ + ¤µ¤é¤Ë¸Â¤é¤ì¤¿¾õ¶·²¼¤Ç¤Ï¡¢ID ¤Ï¤µ¤é¤Ëû¤¯¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢ + ¤è¤ê¿¤¯¤Î¾ðÊó¤ò²¾Äꤹ¤ëɬÍפ¬¤Ç¤Æ¤­¤Þ¤¹ (Î㤨¤Ð¡¢32 ¥Ó¥Ã¥È + IP ¥¢¥É¥ì¥¹¤Ï¤É¤Î¥µ¥¤¥È¤Ë¤ª¤¤¤Æ¤â²á¾ê¤Ê¾ðÊó¤Ç¤¹¤¬¡¢ + ¤½¤ì¤ÎÂå¤ï¤ê¤Ë¤Ê¤ë°Ü¿¢À­¤Î¤¢¤ë¤â¤Î¤Ï¤¢¤ê¤Þ¤»¤ó)¡£

+
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_unique_id.html.ko.euc-kr b/docs/manual/mod/mod_unique_id.html.ko.euc-kr new file mode 100644 index 00000000..52adeffc --- /dev/null +++ b/docs/manual/mod/mod_unique_id.html.ko.euc-kr @@ -0,0 +1,191 @@ + + + +mod_unique_id - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_unique_id

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:°¢ ¿äû¸¶´Ù À¯ÀÏÇÑ ½Äº°ÀÚ¸¦ °¡Áö´Â ȯ°æº¯¼ö¸¦ +Á¦°øÇÑ´Ù
»óÅÂ:Extension
¸ðµâ¸í:unique_id_module
¼Ò½ºÆÄÀÏ:mod_unique_id.c
+

¿ä¾à

+ + +

ÀÌ ¸ðµâÀº ¾î¶² Ưº°ÇÑ »óȲ¿¡¼­µµ "¸ðµç" ¿äûÁß¿¡¼­ + À¯ÀÏÇϵµ·Ï º¸ÀåµÈ ½Äº°ÀÚ(identifier)¸¦ ¸ðµç ¿äû¿¡ Á¦°øÇÑ´Ù. + ½ÉÁö¾î ÀÌ ½Äº°Àڴ Ưº°ÇÏ°Ô ±¸¼ºÇÑ Å¬·¯½ºÅÍÀÇ ¿©·¯ ÄÄÇ»Å͵é + Áß¿¡¼­µµ À¯ÀÏÇÏ´Ù. °¢ ¿äû¸¶´Ù ȯ°æº¯¼ö + UNIQUE_ID¸¦ ¼³Á¤ÇÑ´Ù. À¯ÀÏÇÑ ½Äº°ÀÚ´Â ¿©·¯°¡Áö + ¿ëµµ·Î »ç¿ëÇÒ ¼ö ÀÖÁö¸¸, ¼³¸íÀº ÀÌ ¹®¼­ÀÇ ¹üÀ§¸¦ ³Ñ¾î¼±´Ù.

+
+

Áö½Ã¾îµé

+

ÀÌ ¸ðµâ¿¡´Â Áö½Ã¾î°¡ ¾ø½À´Ï´Ù.

+

ÁÖÁ¦

+
+
top
+
+

ÀÌ·Ð

+ + +

¸ÕÀú À¯´Ð½º ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡ ¼­¹ö°¡ ¾î¶»°Ô µ¿ÀÛÇÏ´ÂÁö + °£·«È÷ »ìÆ캸ÀÚ. Windows NT´Â ÇöÀç ÀÌ ±â´ÉÀ» Áö¿øÇÏÁö ¾Ê´Â´Ù. + À¯´Ð½º¿¡¼­ ¾ÆÆÄÄ¡´Â ¿©·¯ ÀÚ½ÄÀ» ¸¸µé°í, ÀÚ½Ä ÇÁ·Î¼¼½º´Â + Çѹø¿¡ ÇÑ ¿äû¾¿ ó¸®ÇÑ´Ù. ÀÚ½ÄÀº ½ÇÇàÁß¿¡ ¿©·¯ ¿äûÀ» + ó¸®ÇÑ´Ù. ¿©±â¼­ Áß¿äÇÑ °ÍÀº ÀڽĵéÀÌ ¼­·Î ÀڷḦ + °øÀ¯ÇÏÁö ¾Ê´Â´Ù´Â Á¡ÀÌ´Ù. ¾ÕÀ¸·Î ÀÚ½ÄÀ» httpd ÇÁ·Î¼¼½º¶ó°í + ÇÑ´Ù.

+ +

¿©·¯ ÄÄÇ»ÅÍ·Î À¥»çÀÌÆ®¸¦ ¼­ºñ½ºÇÑ´Ù¸é Ŭ·¯½ºÅÍ(cluster)¶ó°í + ºÎ¸¥´Ù. °¢ ÄÄÇ»ÅÍ´Â ¿©·¯ ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Ù. ÀÌµé ¸ðµÎ¸¦ + "¿ìÁÖ"·Î º¸¸é, Ŭ·¯½ºÅÍ¿¡ ÀÖ´Â ÄÄÇ»Å͵鰣¿¡ ¸¹Àº Åë½Å¾øÀÌ + °¢ ¿äû¸¶´Ù ¿ìÁÖ¿¡¼­ À¯ÀÏÇÑ ½Äº°ÀÚ¸¦ ¸¸µé ¼ö ÀÖ´Ù.

+ +

Ŭ·¯½ºÅÍ¿¡ ÀÖ´Â ÄÄÇ»ÅÍ´Â ´ÙÀ½ ¿ä±¸»çÇ×À» ¸¸Á·ÇØ¾ß ÇÑ´Ù. + (ÄÄÇ»Å͸¦ ÇѴ븸 »ç¿ëÇÏ´õ¶óµµ ÄÄÇ»ÅÍ ½Ã°£À» NTP¿Í µ¿±âÇØ¾ß + ÇÑ´Ù.)

+ +
    +
  • ÄÄÇ»ÅÍ ½Ã°£Àº NTP³ª ´Ù¸¥ ³×Æ®¿÷ ½Ã°£ ÇÁ·ÎÅäÄÝ°ú + µ¿±âÈ­µÈ´Ù.
    • + +
  • ÄÄÇ»ÅÍÀÇ È£½ºÆ®¸íÀÌ ¸ðµÎ ´Ù¸£´Ù. ±×·¡¼­ ¸ðµâÀÌ + È£½ºÆ®¸íÀ¸·Î ãÀ¸¸é Ŭ·¯½ºÅÍ¿¡ ÀÖ´Â °¢ ÄÄÇ»Å͸¶´Ù ´Ù¸¥ + IP ÁÖ¼Ò¸¦ ¾ò´Â´Ù.
    • +
+ +

¿î¿µÃ¼Á¦¿¡¼­ pid (ÇÁ·Î¼¼½º id)°¡ 32ºñÆ®¿¡ µé¾î°£´Ù°í + °¡Á¤ÇÑ´Ù. ¿î¿µÃ¼Á¦°¡ pid·Î 32ºñÆ® ÀÌ»óÀ» »ç¿ëÇÑ´Ù¸é °£´ÜÇÏÁö¸¸ + Äڵ带 ¼öÁ¤ÇØ¾ß ÇÑ´Ù.

+ +

ÀÌ·± °¡Á¤ÇÏ¿¡ ¿ì¸®´Â ¾î¶² ½ÃÁ¡¿¡¼­ Ŭ·¯½ºÅÍÀÇ ¾î¶² ÄÄÇ»ÅÍ¿¡ + ÀÖ´Â ¾î¶² httpd ÇÁ·Î¼¼½º¸¦ ´Ù¸¥ ¸ðµç httpd ÇÁ·Î¼¼½ºµé°ú + ±¸º°ÇÒ ¼ö ÀÖ´Ù. ÄÄÇ»ÅÍÀÇ IP ÁÖ¼Ò¿Í httpd ÇÁ·Î¼¼½ºÀÇ pid¸¸À¸·Îµµ + ÃæºÐÈ÷ ±¸º°ÇÒ ¼ö ÀÖ´Ù. ±×·¡¼­ ¿äû¿¡ ´ëÇØ À¯ÀÏÇÑ ±¸º°ÀÚ¸¦ + ¸¸µå·Á¸é ½Ã°£Â÷¸¦ ±¸º°ÇÒ ¼ö¸¸ ÀÖÀ¸¸é µÈ´Ù.

+ +

½Ã°£À» ±¸º°ÇϱâÀ§ÇØ À¯´Ð½º ½Ã°£(timestamp, ¼¼°è Ç¥Áؽ÷Π+ 1970³â 1¿ù 1ÀÏ ÀÌÈÄ Áö³­ ÃÊ)°ú 16ºñÆ® Ä«¿îÅ͸¦ »ç¿ëÇÑ´Ù. + À¯´Ð½º ½Ã°£Àº ÃÊ´ÜÀ§ÀÌ°í, Ä«¿îÅÍ´Â ÀÏ Ãʵ¿¾È 65536±îÁö + Áõ°¡ÇÑ´Ù. ( ip_addr, pid, time_stamp, counter ) + ¹­À½Àº ¾î¶² httpd ÇÁ·Î¼¼½º¿¡¼­ ÀÏ Ãʵ¿¾È 65536 ¿äûÀ» ±¸º°ÇÒ + ¼ö ÀÖ´Ù. ±×·¯³ª Ä«¿îÅÍ´Â pid¸¦ Àç»ç¿ëÇÏ´Â ¹®Á¦¸¦ ÇØ°áÇØ¾ß + ÇÑ´Ù.

+ +

httpd ÀÚ½ÄÀ» ¸¸µé¸é Ä«¿îÅÍ´Â ( ÇöÀç ¹Ð¸®ÃÊ ³ª´©±â 10 )À» + 65536À¸·Î ³ª´« ³ª¸ÓÁö°¡ µÈ´Ù. (¸î¸î ½Ã½ºÅÛÀÇ ¹Ð¸®ÃÊ ½Ã°£¿¡¼­ + ÇÏÀ§ ºñÆ®°¡ ÀÏÄ¡ÇÏÁö¾Ê´Â ¹®Á¦¶§¹®¿¡ ÀÌ °ø½ÄÀ» ¸¸µé¾ú´Ù.) + À¯ÀÏÇÑ ½Äº°ÀÚ¸¦ ¸¸µé¶§ »ç¿ëÇÏ´Â ½Ã°£Àº À¥¼­¹ö°¡ ¿äûÀ» ¹ÞÀº + ½Ã°£ÀÌ´Ù. Ä«¿îÅÍ´Â ½Äº°ÀÚ¸¦ ¸¸µé¶§¸¶´Ù Áõ°¡ÇÑ´Ù (±×¸®°í + ´Ù½Ã ½ÃÀÛÇÑ´Ù).

+ +

Ä¿³ÎÀº ÇÁ·Î¼¼½º¸¦ Æ÷Å©ÇÒ¶§(fork) °¢ ÇÁ·Î¼¼½º¿¡ pid¸¦ + ÇÒ´çÇÏ°í, pid´Â ´Ù½Ã ½ÃÀÛÇÒ ¼ö ÀÖ´Ù. (pid´Â ¸¹Àº À¯´Ð½º¿¡¼­ + 16ºñÆ®ÀÌÁö¸¸, ÃÖ±Ù ½Ã½ºÅÛÀº 32ºñÆ®·Î È®ÀåÇß´Ù.) ±×·¡¼­ ½Ã°£ÀÌ + Áö³ª¸é °°Àº pid¸¦ Àç»ç¿ëÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª °°Àº ½Ã°£¿¡ pid¸¦ + Àç»ç¿ëÇÏÁö ¾Ê´Â´Ù¸é À§ÀÇ ¹­À½Àº À¯ÀÏÇÏ´Ù. Áï, ¿ì¸®´Â ½Ã½ºÅÛÀÌ + ÀÏÃʵ¿¾È ÇÁ·Î¼¼½º¸¦ 65536°³ ÀÌ»ó ¸¸µéÁö ¾Ê´Â´Ù°í °¡Á¤ÇÑ´Ù. + (¾î¶² À¯´Ð½º¿¡¼­´Â 32768°³ ÀÌ»ó ÇÁ·Î¼¼½º¸¦ ¸¸µé¸é pid Àç»ç¿ë + ¹®Á¦°¡ ¹ß»ýÇÒ ¼ö ÀÖÁö¸¸, ÀÌ°ÍÁ¶Â÷µµ ÀϾ °Í°°Áö ¾Ê´Ù.)

+ +

½Ã°£ÀÌ ¾î¶² ÀÌÀ¯¿¡¼­°Ç ¹Ýº¹µÈ´Ù°í °¡Á¤Çغ¸ÀÚ. Áï, ½Ã½ºÅÛ + ½Ã°è°¡ ²¿¿©¼­ ½Ã°£ÀÌ °ú°Å·Î µ¹¾Æ°¡´Â (ȤÀº ½Ã°è°¡ ³Ê¹« ¾Õ¼­°¡¼­ + ¿Ã¹Ù·Î Àç¼³Á¤ÇÑÈÄ ¹Ì·¡¿¡ °°Àº ½Ã°£ÀÌ µÇ´Â) °æ¿ì´Ù. ÀÌ °æ¿ì + pid¿Í ½Ã°£À» ¸ðµÎ Àç»ç¿ëÇÒ ¼ö ÀÖ´Ù. Ä«¿îÅÍÀÇ ÃʱâÈ­ °ø½ÄÀº + ÀÌ ¹®Á¦¸¦ ÇØ°áÇÏ·Á°í °í¾ÈµÇ¾ú´Ù. ¿ì¸®´Â ½ÇÁ¦ ¹«ÀÛÀ§ ¼ýÀÚ·Î + Ä«¿îÅ͸¦ ÃʱâÈ­ÇÏ±æ ¿øÇÏÁö¸¸, ¸¹Àº ½Ã½ºÅÛ¿¡¼­ ÀÌ·± ¼ö¸¦ + ½±°Ô ¾òÀ» ¼ö ¾ø´Ù. (¿¹¸¦ µé¾î, seed°¡ ÇÊ¿äÇϱ⶧¹®¿¡ + rand()¸¦ »ç¿ëÇÒ ¼ö ¾ø°í, ½Ã°£Àº ÃÖ¼ÒÇÑ ÀÏÃÊ ´ÜÀ§À̱⶧¹®¿¡ + ½Ã°£À¸·Î seed·Î »ç¿ëÇÒ ¼ö ¾ø´Ù.) Áï ¿Ïº®ÇÑ ÇØ°áÃ¥ÀÌ ¾ø´Ù.

+ +

±×·³ ÀÌ ¹æ¹ýÀº ¾ó¸¶³ª ±¦ÂúÀ»±î? ÄÄÇ»ÅÍÁß Çϳª°¡ ¿äûÀ» + ÃÊ´ç ÃÖ´ë 500°³ (½Ã½ºÅÛÀº ÀϹÝÀûÀ¸·Î Á¤ÀûÀÎ ÆÄÀÏÀ» Àü¼ÛÇÏ´Â + °Í ÀÌ»óÀÇ ÀÛ¾÷À» ÇϹǷΠÀÌ ±ÛÀ» ¾²´Â ½ÃÁ¡¿¡¼­ »ó´çÈ÷ ³ôÀº + °ªÀÌ´Ù.) ¼­ºñ½ºÇÑ´Ù°í °¡Á¤ÇÏÀÚ. µ¿½Ã¿¡ ¾ó¸¶¸¸Å­ÀÇ Å¬¶óÀ̾ðÆ®¸¦ + ó¸®Çϴ°¡¿¡ µû¶ó ÀÚ½ÄÀÇ °³¼ö°¡ °áÁ¤µÈ´Ù. ±×·¯³ª ¿ì¸®´Â + ºñ°üÀûÀ¸·Î ÇÑ ÀÚ½ÄÀÌ ¿äûÀ» ÃÊ´ç 500°³ ó¸®ÇÒ ¼ö ÀÖ´Ù°í + °¡Á¤ÇÑ´Ù. Àç»ç¿ëÇÑ pid¸¦ °¡Áø ÀÚ½ÄÀÇ 500°³ ¿äû°ú ÀÌÀü ÀÚ½ÄÀÇ + 500°³ ¿äûÀÇ Ä«¿îÅÍ°ªÀÌ °ãÄ¥ ¼ö ÀÖ´Â Ä«¿îÅÍ ½ÃÀÛ°ª °æ¿ì¼ö´Â + 1000°³ÀÌ´Ù. ±×·¡¼­ (ÃÊ´ÜÀ§¿¡¼­) ÀÚ½ÄÀÌ Ä«¿îÅÍ°ªÀ» ¹Ýº¹ÇÏ¿© + À¯ÀϼºÀÌ ±úÁú È®·üÀº 1.5%ÀÌ´Ù. ÀÌ°ÍÀº ¸Å¿ì ºñ°üÀûÀÎ °¡Á¤À̸ç, + ½ÇÁ¦ ÀÌ·² °æ¿ì´Â »ó´çÈ÷ ´õ ³·´Ù. ±×·¡µµ ½Ã½ºÅÛ¿¡¼­ ÀÌ·± + ÀÏÀÌ ¹ß»ýÇÒ °Í °°´Ù¸é (¼Ò½º¸¦ ¼öÁ¤ÇÏ¿©) Ä«¿îÅ͸¦ 32ºñÆ®·Î + ¸¸µé¾î¶ó.

+ +

¼¶¸ÓŸÀÓ¶§¹®¿¡ ½Ã°è°¡ "µÚ·Î °¡´Â" °ÍÀ» °ÆÁ¤ÇÒÁöµµ ¸ð¸¥´Ù. + ±×·¯³ª ¿©±â¼­ »ç¿ëÇÏ´Â ½Ã°£Àº ±¹Á¦ Ç¥ÁؽÃ(UTC), Áï ½Ã°£ÀÌ + "Ç×»ó" ¾ÕÀ¸·Î °¡¹Ç·Î ¹®Á¦°¡ ¾ø´Ù. x86±â¹Ý À¯´Ð½º¿¡¼­´Â + ÀûÀýÇÑ ¼³Á¤ÀÌ ÇÊ¿äÇÏ´Ù. ¸ÞÀκ¸µå ½Ã°è°¡ UTC¸¦ »ç¿ëÇϵµ·Ï + ¼³Á¤ÇØ¾ß ÇÑ´Ù. ±×·¯³ª NTP¸¦ »ç¿ëÇÑ´Ù¸é Àç½ÃÀÛÈÄ Á¶±Ý Áö³ª¸é + UTC ½Ã°£¿¡ ¿Ã¹Ù·Î ¸ÂÃá´Ù.

+ +

ȯ°æº¯¼ö UNIQUE_ID´Â MIME base64 ÀÎÄÚµù°ú + ºñ½ÁÇÑ ¹æ¹ýÀ¸·Î 112ºñÆ® (32ºñÆ® IP ÁÖ¼Ò, 32ºñÆ® pid, 32ºñÆ® + ½Ã°£, 16ºñÆ® Ä«¿îÅÍ) ¹­À½À» ¾ËÆĺª [A-Za-z0-9@-]·Î + Ç¥ÇöÇÑ´Ù. ½ÇÁ¦ MIME base64 ¾ËÆĺªÀº + [A-Za-z0-9+/]ÀÌÁö¸¸ +¿Í + /´Â URL¿¡¼­ Ưº°ÇÑ Àǹ̷Π»ç¿ëÇϹǷΠÁ¦¿ÜÇß´Ù. + ¸ðµç °ªÀ» ³×Æ®¿÷ ¹ÙÀÌÆ®¼ø¼­·Î ÀÎÄÚµùÇϱ⶧¹®¿¡ ´Ù¸¥ ¹ÙÀÌÆ®¼ø¼­¸¦ + »ç¿ëÇÏ´Â ¾ÆÅ°ÅØÃÄ°£¿¡ °ªÀÌ °°´Ù. ½ÇÁ¦ ÀÎÄÚµù ¼ø¼­´Â + ½Ã°£, IP ÁÖ¼Ò, pid, Ä«¿îÅÍ ¼ø¼­ÀÌ´Ù. ÀÌ ¼ø¼­¿¡´Â ¾î¶² ¸ñÀûÀÌ + ÀÖÁö¸¸, ÇÁ·Î±×·¥Àº ÀÎÄÚµù ¼ø¼­¿¡ ÀÇÁ¸ÇÏ¿© °ªµéÀ» ºÐ¼®Çϸé + ¾ÈµÊÀ» °­Á¶ÇÑ´Ù. ÇÁ·Î±×·¥Àº ÀÎÄÚµùµÈ UNIQUE_ID + Àüü¸¦ ÇÑ ´ÜÀ§·Î »ý°¢ÇÏ°í, ´Ù¸¥ UNIQUE_ID¿Í + µ¿ÀÏÇÑÁö¸¸ ºñ±³ÇÒ ¼ö ÀÖ´Ù.

+ +

¼ø¼­´Â ¾ÕÀ¸·Î ±âÁ¸ÀÇ UNIQUE_ID µ¥ÀÌÅͺ£À̽º¿Í + Ãæµ¹À» ¿°·ÁÇÏÁö¾Ê°í ÀÎÄÚµùÀ» º¯°æÇÒ ¼ö ÀÖµµ·Ï °í¾ÈÇß´Ù. + »õ·Î¿î ÀÎÄÚµùÀº ù Ç׸ñÀ¸·Î ½Ã°£À» »ç¿ëÇϰųª, °°Àº ¾ËÆĺª°ú + ºñÆ® ±æÀ̸¦ »ç¿ëÇÒ ¼öµµ ÀÖ´Ù. ½Ã°£ÀÌ ±âº»ÀûÀ¸·Î Áõ°¡ÇÏ´Â °ªÀ̹ǷΠ+ Ŭ·¯½ºÅÍ¿¡ ÀÖ´Â ¸ðµç ÄÄÇ»ÅÍ°¡ ¿äû ¼­ºñ½º¸¦ Áß´ÜÇÏ°í ÀÌÀü + ÀÎÄÚµù Çü½ÄÀ» ±×¸¸ »ç¿ëÇϱâÀ§ÇØ ±âÁØ ÃÊ(flag second)¸¸À¸·Î + ÃæºÐÇÏ´Ù. ÀÌÈÄ ¿äûÀ» Àç°ÔÇÏ°í »õ·Î¿î ÀÎÄÚµùÀ» ½ÃÀÛÇÒ ¼ö + ÀÖ´Ù.

+ +

¿ì¸®´Â ÀÌ ¹æ¹ýÀÌ ÀÌ ¹®Á¦¿¡ ´ëÇÏ¿© »ó´ëÀûÀ¸·Î Æ÷Æð¡´ÉÇÑ + ÇØ°áÃ¥À̶ó°í ¹Ï´Â´Ù. ÀÌ ¹æ¹ýÀº Windows NT¿Í °°Àº ¸ÖƼ¾²·¹µå + ½Ã½ºÅÛÀ¸·Î È®ÀåÇÒ ¼ö ÀÖ°í, ¾ÕÀ¸·Î ¿ëµµ¿¡ µû¶ó È®ÀåÇÒ ¼ö + ÀÖ´Ù. ¹Ì·¡¿¡ ÇÊ¿äÇѸ¸Å­ ´õ ±ä ½Äº°ÀÚ¸¦ ¸¸µé ¼ö Àֱ⶧¹®¿¡ + »ý¼ºÇÑ ½Äº°ÀÚ´Â ±âº»ÀûÀ¸·Î ¿µ¿øÇÑ ¼ö¸íÀ» °¡Áø´Ù. ±âº»ÀûÀ¸·Î + Ŭ·¯½ºÅÍÀÇ ÄÄÇ»ÅÍµé »çÀÌ¿¡ Åë½ÅÀÌ ÇÊ¿ä¾ø°í (ºÎÇÏ°¡ ÀÛÀº + NTP µ¿±â¸¸ ÇÊ¿äÇÏ´Ù), httpd ÇÁ·Î¼¼½º »çÀÌ¿¡ Åë½Åµµ ÇÊ¿ä¾ø´Ù + (Ä¿³ÎÀÌ ºÎ¿©ÇÏ´Â pid°ªÀÌ ¾Ï¹¬ÀûÀÎ Åë½ÅÀÌ´Ù). ¸Å¿ì ƯÀÌÇÑ + »óȲÀ̶ó¸é ÀνÄÀÚ Å©±â¸¦ ÁÙÀÏ ¼ö ÀÖÁö¸¸ ´õ ¸¹Àº Á¤º¸¸¦ + °¡Á¤ÇØ¾ß ÇÑ´Ù. (¿¹¸¦ µé¾î, ¾î¶² »çÀÌÆ®¿¡¼­ 32ºñÆ® IP ÁÖ¼Ò + ±¸ºÐÀº ºÒÇÊ¿äÇÏ°Ô Å©Áö¸¸, À̸¦ ÁÙÀÌ´Â ¹æ¹ýÀº »óȲ¿¡ µû¶ó + ´Ù¸£´Ù.)

+
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_userdir.html b/docs/manual/mod/mod_userdir.html new file mode 100644 index 00000000..897ef832 --- /dev/null +++ b/docs/manual/mod/mod_userdir.html @@ -0,0 +1,11 @@ +URI: mod_userdir.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_userdir.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_userdir.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_userdir.html.en b/docs/manual/mod/mod_userdir.html.en new file mode 100644 index 00000000..70ce1966 --- /dev/null +++ b/docs/manual/mod/mod_userdir.html.en @@ -0,0 +1,175 @@ + + + +mod_userdir - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_userdir

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
Description:User-specific directories
Status:Base
Module Identifier:userdir_module
Source File:mod_userdir.c
+

Summary

+ +

This module allows user-specific directories to be accessed using the +http://example.com/~user/ syntax.

+
+ + +
top
+

UserDir Directive

+ + + + + + +
Description:Location of the user-specific directories
Syntax:UserDir directory-filename
Context:server config, virtual host
Status:Base
Module:mod_userdir
+ +

The UserDir directive sets the real + directory in a user's home directory to use when a request for a + document for a user is received. Directory-filename is + one of the following:

+ +
    +
  • The name of a directory or a pattern such as those shown + below.
    • + +
  • The keyword disabled. This turns off + all username-to-directory translations except those + explicitly named with the enabled keyword (see + below).
    • + +
  • The keyword disabled followed by a + space-delimited list of usernames. Usernames that appear in + such a list will never have directory translation + performed, even if they appear in an enabled + clause.
    • + +
  • The keyword enabled followed by a + space-delimited list of usernames. These usernames will have + directory translation performed even if a global disable is + in effect, but not if they also appear in a + disabled clause.
    • +
+ +

If neither the enabled nor the + disabled keywords appear in the + Userdir directive, the argument is treated as a + filename pattern, and is used to turn the name into a directory + specification. A request for + http://www.foo.com/~bob/one/two.html will be + translated to:

+ + + + + + + +
UserDir directive usedTranslated path
UserDir public_html~bob/public_html/one/two.html
UserDir /usr/web/usr/web/bob/one/two.html
UserDir /home/*/www/home/bob/www/one/two.html
+ +

The following directives will send redirects to the client:

+ + + + + + + +
UserDir directive usedTranslated path
UserDir http://www.foo.com/usershttp://www.foo.com/users/bob/one/two.html
UserDir +http://www.foo.com/*/usrhttp://www.foo.com/bob/usr/one/two.html
UserDir +http://www.foo.com/~*/http://www.foo.com/~bob/one/two.html
+ +
+ Be careful when using this directive; for instance, + "UserDir ./" would map "/~root" to + "/" - which is probably undesirable. It is strongly + recommended that your configuration include a "UserDir + disabled root" declaration. See also the Directory directive and the Security Tips page for + more information. +
+ +

Additional examples:

+ +

To allow a few users to have UserDir directories, but +not anyone else, use the following:

+ +

+UserDir disabled
+UserDir enabled user1 user2 user3 +

+ +

To allow most users to have UserDir directories, but +deny this to a few, use the following:

+ +

+UserDir enabled
+UserDir disabled user4 user5 user6 +

+ +

It is also possible to specify alternative user directories. +If you use a command like:

+

+Userdir public_html /usr/web http://www.foo.com/ +

+

With a request for http://www.foo.com/~bob/one/two.html, will try to +find the page at ~bob/public_html/one/two.html first, then +/usr/web/bob/one/two.html, and finally it will send a redirect +to http://www.foo.com/bob/one/two.html.

+

If you add a redirect, it must be the last alternative in the list. +Apache cannot determine if the redirect succeeded or not, so if you have +the redirect earlier in the list, that will always be the alternative +that is used.

+ +

User directory substitution is not active by default in versions +2.1.4 and later. In earlier versions, UserDir public_html +was assumed if no UserDir +directive was present.

+ + +

See also

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_userdir.html.ja.euc-jp b/docs/manual/mod/mod_userdir.html.ja.euc-jp new file mode 100644 index 00000000..542dcafe --- /dev/null +++ b/docs/manual/mod/mod_userdir.html.ja.euc-jp @@ -0,0 +1,185 @@ + + + +mod_userdir - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_userdir

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + +
ÀâÌÀ:¥æ¡¼¥¶ÀìÍѤΥǥ£¥ì¥¯¥È¥ê¤òÄó¶¡ +
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:userdir_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_userdir.c
+

³µÍ×

+ +

¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢ +http://example.com/~user/ +¹½Ê¸¤ò»È¤Ã¤Æ¥æ¡¼¥¶ÀìÍѥǥ£¥ì¥¯¥È¥ê¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£

+
+ + +
top
+

UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + +
ÀâÌÀ:¥æ¡¼¥¶ÀìÍѥǥ£¥ì¥¯¥È¥ê¤Î°ÌÃÖ
¹½Ê¸:UserDir directory-filename
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
¥¹¥Æ¡¼¥¿¥¹:Base
¥â¥¸¥å¡¼¥ë:mod_userdir
+ +

UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥æ¡¼¥¶¤Î¥É¥­¥å¥á¥ó¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¤¿»þ¤Ë»È¤¦ + ¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥êÃæ¤Î¡¢¼ÂºÝ¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ò + ÀßÄꤷ¤Þ¤¹¡£ + directory-filename ¤Ë¤Ï¼¡¤Î¤É¤ì¤«¤ò»ØÄꤷ¤Þ¤¹:

+ +
    +
  • ¥Ç¥£¥ì¥¯¥È¥ê̾¤«²¼¤Ë¼¨¤¹¤è¤¦¤Ê¥Ñ¥¿¡¼¥ó¡£
    • + +
  • disabled ¥­¡¼¥ï¡¼¥É¡£ + enabled ¥­¡¼¥ï¡¼¥É (²¼µ­»²¾È) ¤ÇÌÀ¼¨Åª¤Ë + »ØÄꤵ¤ì¤¿¥æ¡¼¥¶°Ê³°¤Î + Á´¤Æ¤Î¥æ¡¼¥¶Ì¾-¥Ç¥£¥ì¥¯¥È¥êÊÑ´¹¤ò + ¤·¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£
    • + +
  • disabled ¥­¡¼¥ï¡¼¥É¤È¡¢¥¹¥Ú¡¼¥¹¶èÀÚ¤ê¤Î¥æ¡¼¥¶Ì¾¥ê¥¹¥È¡£ + ¤³¤Î¥ê¥¹¥ÈÃæ¤Ë´Þ¤Þ¤ì¤ë¥æ¡¼¥¶Ì¾¤ËÂФ·¤Æ¤Ï¡¢¤¿¤È¤¨ + enabled Àá¤Ë¤¢¤Ã¤¿¤È¤·¤Æ¤â¡¢ + ·è¤·¤Æ¥Ç¥£¥ì¥¯¥È¥êÊÑ´¹¤Ï¹Ô¤ï¤ì¤Þ¤»¤ó¡£
    • + +
  • enebled ¥­¡¼¥ï¡¼¥É¤È¥¹¥Ú¡¼¥¹¶èÀÚ¤ê¤Î¥æ¡¼¥¶Ì¾¥ê¥¹¥È¡£ + Á´ÂΤǤÏÊÑ´¹¤¬Ìµ¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢ + ¤³¤ì¤é¤Î¥æ¡¼¥¶Ì¾¤Ë¤Ï¥Ç¥£¥ì¥¯¥È¥êÊÑ´¹¤¬¹Ô¤ï¤ì¤Þ¤¹¡£ + ¤¿¤À¤·¡¢disabled Àá¤Ë¤â¤¢¤ì¤ÐÊÑ´¹¤Ï¤µ¤ì¤Þ¤»¤ó¡£ +
    • +
+ +

¤â¤· enabled ¤â disabled + ¥­¡¼¥ï¡¼¥É¤â UserDir ¤Ë¸½¤ï¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢ + °ú¿ô¤Ï¥Õ¥¡¥¤¥ë̾¥Ñ¥¿¡¼¥ó¤È¤·¤Æ°·¤ï¤ì¡¢ + ̾Á°¤«¤é¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤ÎÊÑ´¹¤Î»ØÄê¤ò¹Ô¤Ê¤¦»þ¤Ë»È¤ï¤ì¤Þ¤¹¡£ + http://www.foo.com/~bob/one/two.html + ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï¼¡¤Î¤è¤¦¤ËÊÑ´¹¤µ¤ì¤Þ¤¹:

+ + + + + + + +
UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥ÖÊÑ´¹¸å¤Î¥Ñ¥¹
UserDir public_html~bob/public_html/one/two.html
UserDir /usr/web/usr/web/bob/one/two.html
UserDir /home/*/www/home/bob/www/one/two.html
+ +

¼¡¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ·¤Æ¥ê¥À¥¤¥ì¥¯¥È¤ò + Á÷¿®¤·¤Þ¤¹:

+ + + + + + + +
UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥ÖÊÑ´¹¸å¤Î¥Ñ¥¹
UserDir http://www.foo.com/usershttp://www.foo.com/users/bob/one/two.html
UserDir +http://www.foo.com/*/usrhttp://www.foo.com/bob/usr/one/two.html
UserDir +http://www.foo.com/~*/http://www.foo.com/~bob/one/two.html
+ +
+ ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤È¤­¤ÏÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤; + "UserDir ./" ¤Ï + "/~root" ¤«¤é "/" ¤Ø¥Þ¥Ã¥×¤·¤Þ¤¹¤¬¡¢ + ¤³¤ì¤Ï˾¤Þ¤·¤¤Æ°ºî¤Ç¤Ï¤Ê¤¤¤Ç¤·¤ç¤¦¡£ + "UserDir disabled root" Àë¸À¤ò + ÀßÄê¤ÎÃæ¤Ë´Þ¤á¤Æ¤ª¤¯¤³¤È¤ò¶¯¤¯¤ªÁ¦¤á¤·¤Þ¤¹¡£ + ÄɲþðÊó¤Ë Directory + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä + ¥»¥­¥å¥ê¥Æ¥£ + Tips ¤Î¥Ú¡¼¥¸¤â¤´Í÷²¼¤µ¤¤¡£ +
+ +

ÄɲäÎÎã:

+ +

¾¯¿ô¤Î¥æ¡¼¥¶¤Î¤ß¤¬ UserDir +¥Ç¥£¥ì¥¯¥È¥ê¤òÍøÍѤ·¡¢¤½¤ì°Ê³°¤Ë¤ÏÍøÍѤµ¤»¤¿¤¯¤Ê¤¤¾ì¹ç¤Ï +¼¡¤ò»È¤¤¤Þ¤·¤ç¤¦:

+ +

+UserDir disabled
+UserDir enabled user1 user2 user3 +

+ +

ÂçÉôʬ¤Î¥æ¡¼¥¶¤Ï UserDir ¥Ç¥£¥ì¥¯¥È¥ê¤òÍøÍѤ¹¤ë¤±¤ì¤É¡¢ +¾¯¿ô¤Î¿Í¤ÏÉÔµö²Ä¤Ë¤·¤¿¤¤¾ì¹ç¤Ï¡¢¼¡¤ò»È¤¤¤Þ¤·¤ç¤¦:

+ +

+UserDir enabled
+UserDir disabled user4 user5 user6 +

+ +

¾¤Î¥æ¡¼¥¶¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ +¼¡¤Î¤è¤¦¤Ê¥³¥Þ¥ó¥É¤ò»È¤¦¤È:

+ +

+Userdir public_html /usr/web http://www.foo.com/ +

+ +

http://www.foo.com/~bob/one/two.html ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï¤Þ¤º +~bob/public_html/one/two.html ¤Î¥Ú¡¼¥¸¤òÄ´¤Ù¡¢¤½¤Î¼¡¤Ë +/usr/web/bob/one/two.html ¤òÄ´¤Ù¡¢ºÇ¸å¤Ë http://www.foo.com/bob/one/two.html +¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷¤ê¤Þ¤¹¡£

+ +

¥ê¥À¥¤¥ì¥¯¥È¤ò²Ã¤¨¤ë¾ì¹ç¤Ï¡¢¥ê¥¹¥È¤ÎºÇ¸å¤ÎÁªÂò»è¤Ç¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ +Apache ¤Ï¥ê¥À¥¤¥ì¥¯¥È¤¬À®¸ù¤¹¤ë¤«¤É¤¦¤«¤ò·è¤á¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¤Î¤Ç¡¢ +¥ê¥¹¥È¤ÎÁ°¤ÎÊý¤Ë¥ê¥À¥¤¥ì¥¯¥È¤ò½ñ¤¯¤È¡¢¤½¤ì¤¬É¬¤º»ÈÍѤµ¤ì¤ëÁªÂò»è¤Ë +¤Ê¤Ã¤Æ¤·¤Þ¤¤¤Þ¤¹¡£

+ +

2.1.4 °Ê¹ß¤Ç¤Ï¡¢¥æ¡¼¥¶¥Ç¥£¥ì¥¯¥È¥êÃÖ´¹µ¡Ç½¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤Ïµ¯Æ°¤·¤Þ¤»¤ó¡£ +¤½¤ì°ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢UserDir +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Â¸ºß¤·¤Ê¤±¤ì¤Ð¡¢UserDir public_html +¤Ç¤¢¤ë¤È²¾Äꤵ¤ì¤Æ¤¤¤Þ¤·¤¿¡£

+ + +

»²¾È

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_userdir.html.ko.euc-kr b/docs/manual/mod/mod_userdir.html.ko.euc-kr new file mode 100644 index 00000000..9547a239 --- /dev/null +++ b/docs/manual/mod/mod_userdir.html.ko.euc-kr @@ -0,0 +1,161 @@ + + + +mod_userdir - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_userdir

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + +
¼³¸í:»ç¿ëÀÚº° µð·ºÅ丮
»óÅÂ:Base
¸ðµâ¸í:userdir_module
¼Ò½ºÆÄÀÏ:mod_userdir.c
+

¿ä¾à

+ +

ÀÌ ¸ðµâÀ» »ç¿ëÇϸé http://example.com/~user/ ½ÄÀ¸·Î +»ç¿ëÀÚº° µð·ºÅ丮¿¡ Á¢±ÙÇÒ ¼ö ÀÖ´Ù.

+
+ + +
top
+

UserDir Áö½Ã¾î

+ + + + + + + +
¼³¸í:»ç¿ëÀÚº° µð·ºÅ丮 À§Ä¡
¹®¹ý:UserDir directory-filename
±âº»°ª:UserDir public_html
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®
»óÅÂ:Base
¸ðµâ:mod_userdir
+ +

UserDir Áö½Ã¾î´Â »ç¿ëÀÚÀÇ ¹®¼­¿¡ ´ëÇÑ +¿äûÀ» ¹ÞÀ»¶§ »ç¿ëÀÚ È¨µð·ºÅ丮 ¾È¿¡¼­ »ç¿ëÇÒ ½ÇÁ¦ µð·ºÅ丮¸¦ +ÁöÁ¤ÇÑ´Ù. Directory-filenameÀº ´ÙÀ½ Áß ÇϳªÀÌ´Ù:

+ +
    +
  • ¾Æ·¡¿Í °°Àº µð·ºÅ丮¸í ȤÀº ÆÐÅÏ.
    • + +
  • disabled Å°¿öµå. +enabled Å°¿öµå·Î (¾Æ·¡ Âü°í) Á÷Á¢ À̸§À» ÁöÁ¤ÇÏÁö ¾Ê¾Ò´Ù¸é +¸ðµç »ç¿ëÀÚ¸í-µð·ºÅ丮 º¯È¯À» ÇÏÁö ¾Ê´Â´Ù.
    • + +
  • disabled Å°¿öµå µÚ¿¡ °ø¹éÀ¸·Î ±¸ºÐÇÑ »ç¿ëÀÚ¸í ¸ñ·Ï. +»ç¿ëÀÚ¸íÀÌ enabled ±¸¹®¿¡ ÀÖ´Ù°í ÇÏ´õ¶óµµ, ÀÌ ¸ñ·Ï¿¡ +ÀÖ´Â »ç¿ëÀÚ¸íÀº µð·ºÅ丮 º¯È¯À» ÇÏÁö ¾Ê´Â´Ù.
    • + +
  • enabled Å°¿öµå µÚ¿¡ °ø¹éÀ¸·Î ±¸ºÐÇÑ »ç¿ëÀÚ¸í ¸ñ·Ï. +Àüü disableÀ» »ç¿ëÇÏ°í »ç¿ëÀÚ¸íÀÌ disabled ±¸¹®¿¡ +¾ø´õ¶óµµ, »ç¿ëÀÚ¸íÀ» µð·ºÅ丮 º¯È¯ÇÑ´Ù.
    • +
+ +

Userdir Áö½Ã¾î¿¡ enabled³ª +disabled Å°¿öµå¸¦ »ç¿ëÇÏÁö ¾ÊÀ¸¸é, ¾Æ±Ô¸ÕÆ®¸¦ +ÆÄÀϸí ÆÐÅÏÀ¸·Î ó¸®ÇÏ¿© µð·ºÅ丮·Î º¯È¯ÇÑ´Ù. +http://www.foo.com/~bob/one/two.html¿¡ ´ëÇÑ ¿äûÀº +´ÙÀ½°ú °°ÀÌ º¯È¯µÈ´Ù:

+ + + + + + + +
»ç¿ëÇÑ UserDir Áö½Ã¾îº¯È¯ÇÑ °æ·Î
UserDir public_html~bob/public_html/one/two.html
UserDir /usr/web/usr/web/bob/one/two.html
UserDir /home/*/www/home/bob/www/one/two.html
+ +

´ÙÀ½ Áö½Ã¾î´Â Ŭ¶óÀ̾ðÆ®¿¡°Ô ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù:

+ + + + + + + +
»ç¿ëÇÑ UserDir Áö½Ã¾îº¯È¯ÇÑ °æ·Î
UserDir http://www.foo.com/usershttp://www.foo.com/users/bob/one/two.html
UserDir +http://www.foo.com/*/usrhttp://www.foo.com/bob/usr/one/two.html
UserDir +http://www.foo.com/~*/http://www.foo.com/~bob/one/two.html
+ +
+ ÀÌ Áö½Ã¾î¸¦ »ç¿ëÇÒ¶§ ÁÖÀÇÇ϶ó; ¿¹¸¦ µé¾î, +"UserDir ./"´Â "/~root"¸¦ ¾Æ¸¶µµ ¹Ù¶÷Á÷ÇÏÁö ¾Ê°Ô +"/"·Î º¯È¯ÇÑ´Ù. ¼³Á¤¿¡ "UserDir + disabled root"¸¦ Æ÷ÇÔÇÏ±æ °­·ÂÈ÷ ±ÇÇÑ´Ù. ÀÚ¼¼ÇÑ Á¤º¸¸¦ ¾Ë·Á¸é +Directory Áö½Ã¾î¿Í º¸¾È ÆÁµµ Âü°íÇ϶ó. +
+ +

Ãß°¡ ¿¹Á¦:

+ +

¸î¸î »ç¿ëÀÚ¿¡°Ô¸¸ UserDir µð·ºÅ丮¸¦ Çã¿ëÇÑ´Ù¸é, +´ÙÀ½°ú °°´Ù:

+ +

+UserDir disabled
+UserDir enabled user1 user2 user3 +

+ +

´ëºÎºÐÀÇ »ç¿ëÀÚ¿¡°Ô UserDir µð·ºÅ丮¸¦ Çã¿ëÇÏ°í +ÀϺθ¸ °ÅºÎÇÑ´Ù¸é, ´ÙÀ½°ú °°´Ù:

+ +

+UserDir enabled
+UserDir disabled user4 user5 user6 +

+ +

´Ù¸¥ »ç¿ëÀÚ µð·ºÅ丮¸¦ ÁöÁ¤ÇÒ ¼öµµ ÀÖ´Ù. +´ÙÀ½°ú °°Àº ¸í·É¾î¸¦ »ç¿ëÇÑ´Ù¸é:

+

+Userdir public_html /usr/web http://www.foo.com/ +

+

http://www.foo.com/~bob/one/two.html ¿äûÀ» Çϸé, +¸ÕÀú ~bob/public_html/one/two.html ÆäÀÌÁö¸¦ ã°í, +/usr/web/bob/one/two.htmlÀ» ãÀº ÈÄ, ¸¶Áö¸·À¸·Î +http://www.foo.com/bob/one/two.htmlÀ¸·Î ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù.

+

¸®´ÙÀÌ·º¼ÇÀ» »ç¿ëÇÑ´Ù¸é ¸ñ·ÏÀÇ ¸¶Áö¸·¿¡ µÎ¾î¾ß ÇÑ´Ù. +¾ÆÆÄÄ¡´Â ¸®´ÙÀÌ·º¼ÇÀÌ ¼º°øÇß´ÂÁö ¾Ë ¼ö ¾ø±â¶§¹®¿¡, ¸®´ÙÀÌ·º¼ÇÀ» +¸ñ·Ï ¾Õ¿¡ µÎ¸é Ç×»ó ¸®´ÙÀÌ·º¼ÇÀ» »ç¿ëÇÏ°Ô µÈ´Ù.

+ + +

Âü°í

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_usertrack.html b/docs/manual/mod/mod_usertrack.html new file mode 100644 index 00000000..0d24c8e0 --- /dev/null +++ b/docs/manual/mod/mod_usertrack.html @@ -0,0 +1,3 @@ +URI: mod_usertrack.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_usertrack.html.en b/docs/manual/mod/mod_usertrack.html.en new file mode 100644 index 00000000..f4164514 --- /dev/null +++ b/docs/manual/mod/mod_usertrack.html.en @@ -0,0 +1,252 @@ + + + +mod_usertrack - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_usertrack

+
+

Available Languages:  en 

+
+ + + +
Description: +Clickstream logging of user activity on a site +
Status:Extension
Module Identifier:usertrack_module
Source File:mod_usertrack.c
+

Summary

+ +

Previous releases of Apache have included a module which + generates a 'clickstream' log of user activity on a site using + cookies. This was called the "cookies" module, mod_cookies. In + Apache 1.2 and later this module has been renamed the "user + tracking" module, mod_usertrack. This module has been + simplified and new directives added.

+
+ +
top
+
+

Logging

+ + +

Previously, the cookies module (now the user tracking + module) did its own logging, using the CookieLog + directive. In this release, this module does no logging at all. + Instead, a configurable log format file should be used to log + user click-streams. This is possible because the logging module + now allows multiple log files. The cookie itself is logged by + using the text %{cookie}n in the log file format. For + example:

+

+CustomLog logs/clickstream "%{cookie}n %r %t" +

+ +

For backward compatibility the configurable log module + implements the old CookieLog directive, but this + should be upgraded to the above CustomLog directive.

+
top
+
+

2-digit or 4-digit dates for cookies?

+ + +

(the following is from message + <022701bda43d$9d32bbb0$1201a8c0@christian.office.sane.com> + in the new-httpd archives)

+
+From: "Christian Allen" <christian@sane.com>
+Subject: Re: Apache Y2K bug in mod_usertrack.c
+Date: Tue, 30 Jun 1998 11:41:56 -0400
+
+Did some work with cookies and dug up some info that might be useful.
+
+True, Netscape claims that the correct format NOW is four digit dates, and
+four digit dates do in fact work... for Netscape 4.x (Communicator), that
+is.  However, 3.x and below do NOT accept them.  It seems that Netscape
+originally had a 2-digit standard, and then with all of the Y2K hype and
+probably a few complaints, changed to a four digit date for Communicator.
+Fortunately, 4.x also understands the 2-digit format, and so the best way to
+ensure that your expiration date is legible to the client's browser is to
+use 2-digit dates.
+
+However, this does not limit expiration dates to the year 2000; if you use
+an expiration year of "13", for example, it is interpreted as 2013, NOT
+1913!  In fact, you can use an expiration year of up to "37", and it will be
+understood as "2037" by both MSIE and Netscape versions 3.x and up (not sure
+about versions previous to those).  Not sure why Netscape used that
+particular year as its cut-off point, but my guess is that it was in respect
+to UNIX's 2038 problem.  Netscape/MSIE 4.x seem to be able to understand
+2-digit years beyond that, at least until "50" for sure (I think they
+understand up until about "70", but not for sure).
+
+Summary:  Mozilla 3.x and up understands two digit dates up until "37"
+(2037).  Mozilla 4.x understands up until at least "50" (2050) in 2-digit
+form, but also understands 4-digit years, which can probably reach up until
+9999.  Your best bet for sending a long-life cookie is to send it for some
+time late in the year "37".
+
+ +
+
top
+

CookieDomain Directive

+ + + + + + + +
Description:The domain to which the tracking cookie applies
Syntax:CookieDomain domain
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_usertrack
+ +

This directive controls the setting of the domain to which + the tracking cookie applies. If not present, no domain is + included in the cookie header field.

+ +

The domain string must begin with a dot, and + must include at least one embedded dot. That is, + .foo.com is legal, but foo.bar.com and + .com are not.

+ +
Most browsers in use today will not allow cookies to be set + for a two-part top level domain, such as .co.uk, + although such a domain ostensibly fulfills the requirements + above.
+ + These domains are equivalent to top level domains such as + .com, and allowing such cookies may be a security + risk. Thus, if you are under a two-part top level domain, you + should still use your actual domain, as you would with any other top + level domain (for example, use .foo.co.uk). +
+ + +
+
top
+

CookieExpires Directive

+ + + + + + + +
Description:Expiry time for the tracking cookie
Syntax:CookieExpires expiry-period
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_usertrack
+

When used, this directive sets an expiry time on the cookie + generated by the usertrack module. The expiry-period + can be given either as a number of seconds, or in the format + such as "2 weeks 3 days 7 hours". Valid denominations are: + years, months, weeks, days, hours, minutes and seconds. If the expiry + time is in any format other than one number indicating the + number of seconds, it must be enclosed by double quotes.

+ +

If this directive is not used, cookies last only for the + current browser session.

+ +
+
top
+

CookieName Directive

+ + + + + + + + +
Description:Name of the tracking cookie
Syntax:CookieName token
Default:CookieName Apache
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_usertrack
+

This directive allows you to change the name of the cookie + this module uses for its tracking purposes. By default the + cookie is named "Apache".

+ +

You must specify a valid cookie name; results are + unpredictable if you use a name containing unusual characters. + Valid characters include A-Z, a-z, 0-9, "_", and "-".

+ +
+
top
+

CookieStyle Directive

+ + + + + + + + +
Description:Format of the cookie header field
Syntax:CookieStyle + Netscape|Cookie|Cookie2|RFC2109|RFC2965
Default:CookieStyle Netscape
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_usertrack
+

This directive controls the format of the cookie header + field. The three formats allowed are:

+ +
    +
  • Netscape, which is the original but now deprecated + syntax. This is the default, and the syntax Apache has + historically used.
    • + +
  • Cookie or RFC2109, which is the syntax that + superseded the Netscape syntax.
    • + +
  • Cookie2 or RFC2965, which is the most + current cookie syntax.
    • +
+ +

Not all clients can understand all of these formats. but you + should use the newest one that is generally acceptable to your + users' browsers. At the time of writing, most browsers only fully + support CookieStyle Netscape.

+ +
+
top
+

CookieTracking Directive

+ + + + + + + + +
Description:Enables tracking cookie
Syntax:CookieTracking on|off
Default:CookieTracking off
Context:server config, virtual host, directory, .htaccess
Override:FileInfo
Status:Extension
Module:mod_usertrack
+

When mod_usertrack is loaded, and + CookieTracking on is set, Apache will send a + user-tracking cookie for all new requests. This directive can + be used to turn this behavior on or off on a per-server or + per-directory basis. By default, enabling + mod_usertrack will not + activate cookies.

+ + +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_version.html b/docs/manual/mod/mod_version.html new file mode 100644 index 00000000..ee3abd15 --- /dev/null +++ b/docs/manual/mod/mod_version.html @@ -0,0 +1,11 @@ +URI: mod_version.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mod_version.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mod_version.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/mod_version.html.en b/docs/manual/mod/mod_version.html.en new file mode 100644 index 00000000..bb270bfb --- /dev/null +++ b/docs/manual/mod/mod_version.html.en @@ -0,0 +1,151 @@ + + + +mod_version - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_version

+
+

Available Languages:  en  | + ja  | + ko 

+
+ + + + +
Description:Version dependent configuration
Status:Extension
Module Identifier:version_module
Source File:mod_version.c
Compatibility:Available in version 2.0.56 and later
+

Summary

+ +

This module is designed for the use in test suites and large + networks which have to deal with different httpd versions and + different configurations. It provides a new container -- <IfVersion>, which + allows a flexible version checking including numeric comparisons and + regular expressions.

+ +

Examples

+ <IfVersion 2.1.0>
+ + # current httpd version is exactly 2.1.0
+ + </IfVersion>
+
+ <IfVersion >= 2.2>
+ + # use really new features :-)
+ + </IfVersion> +

+ +

See below for further possibilities.

+
+

Directives

+ +
+ +
top
+

<IfVersion> Directive

+ + + + + + + +
Description:contains version dependent configuration
Syntax:<IfVersion [[!]operator] version> ... +</IfVersion>
Context:server config, virtual host, directory, .htaccess
Override:All
Status:Extension
Module:mod_version
+

The <IfVersion> section encloses + configuration directives which are executed only if the + httpd version + matches the desired criteria. For normal (numeric) comparisons the + version argument has the format + major[.minor[.patch]], e.g. + 2.1.0 or 2.2. minor and + patch are optional. If these numbers are omitted, they are + assumed to be zero. The following numerical operators are + possible:

+ + + + + + + + + + + + +
operatordescription
= or ==httpd version is equal
>httpd version is greater than
>=httpd version is greater or equal
<httpd version is less than
<=httpd version is less or equal
+ +

Example

+ <IfVersion >= 2.1>
+ + # this happens only in versions greater or
+ # equal 2.1.0.
+ + </IfVersion> +

+ +

Besides the numerical comparison it is possible to match a + regular expression + against the httpd version. There are two ways to write it:

+ + + + + + +
operatordescription
= or ==version has the form + /regex/
~version has the form + regex
+ +

Example

+ <IfVersion = /^2.1.[01234]$/>
+ + # e.g. workaround for buggy versions + + </IfVersion> +

+ +

In order to reverse the meaning, all operators can be preceded by an + exclamation mark (!):

+ +

+ <IfVersion !~ ^2.1.[01234]$>
+ + # not for those versions
+ + </IfVersion> +

+ +

If the operator is omitted, it is assumed to be + =.

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_version.html.ja.euc-jp b/docs/manual/mod/mod_version.html.ja.euc-jp new file mode 100644 index 00000000..53b1fa81 --- /dev/null +++ b/docs/manual/mod/mod_version.html.ja.euc-jp @@ -0,0 +1,150 @@ + + + +mod_version - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache ¥â¥¸¥å¡¼¥ë mod_version

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + + +
ÀâÌÀ:¥Ð¡¼¥¸¥ç¥ó°Í¸¤ÎÀßÄê
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:version_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mod_version.c
¸ß´¹À­:¥Ð¡¼¥¸¥ç¥ó 2.1 °Ê¹ß
+

³µÍ×

+ +

ÍÍ¡¹¤Ê¥Ð¡¼¥¸¥ç¥ó¤Î httpd ¤Î°Û¤Ê¤ëÀßÄê¤ò°·¤¦¤³¤È¤Ë¤Ê¤ë¡¢ + ¥Æ¥¹¥È¥¹¥¤¡¼¥È¤äÂ絬Ìϥͥåȥ¥¯¤Ç¤Î»ÈÍѤΤ¿¤á¤ËÀ߷פµ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¿·¤·¤¤¥³¥ó¥Æ¥Ê ¡½ <IfVersion> ¤ò + Ä󶡤·¤Þ¤¹¡£¤³¤ì¤ò»È¤¦¤È¡¢¿ô»ú¤ÎÈæ³Ó¤äÀµµ¬É½¸½¤Ë¤è¤ë½ÀÆð¤Ê + ¥Ð¡¼¥¸¥ç¥ó¥Á¥§¥Ã¥¯¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Îã

+ <IfVersion 2.1.0>
+ + # current httpd version is exactly 2.1.0
+ + </IfVersion>
+
+ <IfVersion >= 2.2>
+ + # use really new features :-)
+ + </IfVersion> +

+ +

¾ÜºÙ¤Ï°Ê²¼¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£

+
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ +
+ +
top
+

<IfVersion> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Ð¡¼¥¸¥ç¥ó°Í¸¤ÎÀßÄê¤òÆþ¤ì¤ë
¹½Ê¸:<IfVersion [[!]operator] version> ... +</IfVersion>
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë, ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È, ¥Ç¥£¥ì¥¯¥È¥ê, .htaccess
¾å½ñ¤­:All
¥¹¥Æ¡¼¥¿¥¹:Extension
¥â¥¸¥å¡¼¥ë:mod_version
+

<IfVersion> ¤Ï httpd ¤Î¥Ð¡¼¥¸¥ç¥ó + ¤¬´ð½à¤òËþ¤¿¤·¤¿¤È¤­¤Ë¤Î¤ß¼Â¹Ô¤µ¤»¤¿¤¤¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤ß¤Þ¤¹¡£ + Ä̾ï¤Î (¿ôÃÍ) Èæ³Ó¤Î¤È¤­¤Ï version °ú¿ô¤Ï + major[.minor[.patch]] ¤È¤¤¤¦ + ·Á¼°¡¢Î㤨¤Ð¡¢2.1.0 ¤ä 2.2 ¤È¤Ê¤ê¤Þ¤¹¡£ + minor ¤È patch ¤Ï¾Êά²Äǽ¤Ç¤¹¡£¾Êά¤µ¤ì¤¿¾ì¹ç¤Ï¡¢ + 0 ¤ò»ØÄꤷ¤¿¤â¤Î¤È¤ß¤Ê¤µ¤ì¤Þ¤¹¡£Èæ³Ó¤Ë¤Ï¼¡¤Î¿ôÃÍ operator ¤ò + »ØÄê¤Ç¤­¤Þ¤¹:

+ + + + + + + + + + + + +
operatorÀâÌÀ
= ¤È ==Ʊ¤¸ httpd ¥Ð¡¼¥¸¥ç¥ó
>¤è¤êÂ礭¤¤ httpd ¥Ð¡¼¥¸¥ç¥ó
>=»ØÄê°Ê¾å¤Î httpd ¥Ð¡¼¥¸¥ç¥ó
<»ØÄê̤Ëþ¤Î httpd ¥Ð¡¼¥¸¥ç¥ó
<=»ØÄê°Ê²¼¤Î httpd ¥Ð¡¼¥¸¥ç¥ó
+ +

Îã

+ <IfVersion >= 2.1>
+ + # this happens only in versions greater or
+ # equal 2.1.0.
+ + </IfVersion> +

+ +

¿ôÃÍÈæ³Ó¤Ë²Ã¤¨¤Æ¡¢http ¤Î¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤ËÂФ·¤ÆÀµµ¬É½¸½¤Ë¤è¤ë + ¥Þ¥Ã¥Á¥ó¥°¤¬¤Ç¤­¤Þ¤¹¡£Æó¼ïÎà¤Î½ñ¤­Êý¤¬¤¢¤ê¤Þ¤¹:

+ + + + + + +
operatorÀâÌÀ
= or ==version ¤Ï + /regex/ ·Á¼°
~version ¤Ï + regex ·Á¼°
+ +

Îã

+ <IfVersion = /^2.1.[01234]$/>
+ + # e.g. workaround for buggy versions + + </IfVersion> +

+ +

¥Þ¥Ã¥Á¥ó¥°¤ÎÈÝÄê¤òɽ¸½¤¹¤ë¤¿¤á¤Ë¡¢¤¹¤Ù¤Æ¤Î¥ª¥Ú¥ì¡¼¥¿¤ÏÁ°¤Ë + ´¶Ã²Éä (!)¤òÉÕ¤±¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

+ <IfVersion !~ ^2.1.[01234]$>
+ + # not for those versions
+ + </IfVersion> +

+ +

operator ¤¬¾Êά¤µ¤ì¤¿¤È¤­¤Ï = ¤È + ¤ß¤Ê¤µ¤ì¤Þ¤¹¡£

+ +
+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_version.html.ko.euc-kr b/docs/manual/mod/mod_version.html.ko.euc-kr new file mode 100644 index 00000000..521d0984 --- /dev/null +++ b/docs/manual/mod/mod_version.html.ko.euc-kr @@ -0,0 +1,150 @@ + + + +mod_version - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+
+

¾ÆÆÄÄ¡ ¸ðµâ mod_version

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + + + +
¼³¸í:¹öÀüº° ¼³Á¤
»óÅÂ:Extension
¸ðµâ¸í:version_module
¼Ò½ºÆÄÀÏ:mod_version.c
Áö¿ø:¾ÆÆÄÄ¡ 2.1 ÀÌÈĺÎÅÍ
+

¿ä¾à

+ +

¿©·¯ ´Ù¸¥ À¥¼­¹ö ¹öÀü°ú ±¸¼ºÀ» ´Ù·ç¾î¾ß ÇÒ Å« ³×Æ®¿÷°ú + Å×½ºÆ®¿ëÀ¸·Î »ç¿ëÇϱâÀ§ÇØ ÀÌ ¸ðµâÀ» ¸¸µé¾ú´Ù. ÀÌ ¸ðµâÀº + ¼ýÀÚ ºñ±³³ª Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ¿© ÀÚÀ¯·Î¿î ¹öÀü °Ë»ç°¡ °¡´ÉÇÑ + <IfVersion>À» + Á¦°øÇÑ´Ù.

+ +

¿¹Á¦

+ <IfVersion 2.1.0>
+ + # ÇöÀç À¥¼­¹ö ¹öÀüÀº Á¤È®È÷ 2.1.0ÀÌ´Ù
+ + </IfVersion>
+
+ <IfVersion >= 2.2>
+ + # ÁøÂ¥ »õ·Î¿î ±â´ÉÀ» »ç¿ëÇÑ´Ù :-)
+ + </IfVersion> +

+ +

´Ù¸¥ »ç¿ë¹ýÀº ¾Æ·¡¸¦ Âü°íÇÑ´Ù.

+
+

Áö½Ã¾îµé

+ +
+ +
top
+

<IfVersion> Áö½Ã¾î

+ + + + + + + +
¼³¸í:¹öÀüº° ¼³Á¤À» ¹­´Â´Ù
¹®¹ý:<IfVersion [[!]operator] version> ... +</IfVersion>
»ç¿ëÀå¼Ò:ÁÖ¼­¹ö¼³Á¤, °¡»óÈ£½ºÆ®, directory, .htaccess
Override ¿É¼Ç:All
»óÅÂ:Extension
¸ðµâ:mod_version
+

<IfVersion> ¼½¼ÇÀº + À¥¼­¹ö ¹öÀüÀÌ ¿øÇÏ´Â Á¶°ÇÀ» ¸¸Á·ÇÒ¶§¸¸ ½ÇÇàÇÒ ¼³Á¤ Áö½Ã¾î¸¦ + ¹­´Â´Ù. ÀϹÝÀûÀÎ (¼ýÀÚ) ºñ±³ÀÇ °æ¿ì version ¾Æ±Ô¸ÕÆ®´Â + 2.1.0À̳ª 2.2¿Í °°ÀÌ + major[.minor[.patch]] + Çü½ÄÀÌ´Ù. minor¿Í patch´Â ¾ø¾îµµ µÈ´Ù. + ÀÌµé ¼ýÀÚ°¡ ¾ø´Ù¸é 0À̶ó°í °¡Á¤ÇÑ´Ù. ´ÙÀ½°ú °°Àº ¼ýÀÚ + operator°¡ °¡´ÉÇÏ´Ù.

+ + + + + + + + + + + + +
operator¼³¸í
= ȤÀº ==µ¿ÀÏÇÑ À¥¼­¹ö ¹öÀü
>º¸´Ù Å« À¥¼­¹ö ¹öÀü
>=Å©°Å³ª °°Àº À¥¼­¹ö ¹öÀü
<º¸´Ù ÀÛÀº À¥¼­¹ö ¹öÀü
<=À۰ųª °°Àº À¥¼­¹ö ¹öÀü
+ +

¿¹Á¦

+ <IfVersion >= 2.1>
+ + # ¹öÀüÀÌ 2.1.0 º¸´Ù Å©°Å³ª °°À»¶§¸¸
+ # ½ÇÇàÇÑ´Ù.
+ + </IfVersion> +

+ +

¼ýÀÚ ºñ±³¿Ü¿¡µµ Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ¿© À¥¼­¹ö ¹öÀüÀ» ÁöÁ¤ÇÒ + ¼ö ÀÖ´Ù. ¿©±â¿¡´Â µÎ°¡Áö ¹æ¹ýÀÌ ÀÖ´Ù.

+ + + + + + +
operator¼³¸í
= ȤÀº ==versionÀº + /regex/ Çü½ÄÀÌ´Ù
~versionÀº + regex Çü½ÄÀÌ´Ù
+ +

¿¹Á¦

+ <IfVersion = /^2.1.[01234]$/>
+ + # ¿¹¸¦ µé¾î, ¿©±â¿¡ ¹ö±×°¡ Àִ ƯÁ¤ ¹öÀü¿¡ ´ëÇÑ ÇØ°áÃ¥ÀÌ ³ª¿Â´Ù + + </IfVersion> +

+ +

¿¬»êÀÚ ¾Õ¿¡ ´À³¦Ç¥(!)¸¦ ¾²¸é Àǹ̸¦ ¹Ý´ë·Î + Çؼ®ÇÑ´Ù.

+ +

+ <IfVersion !~ ^2.1.[01234]$>
+ + # ÀÌ ¹öÀüÀÌ ¾Æ´Ï¸é
+ + </IfVersion> +

+ +

operator¸¦ »ý·«Çϸé =À̶ó°í + »ý°¢ÇÑ´Ù.

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mod_vhost_alias.html b/docs/manual/mod/mod_vhost_alias.html new file mode 100644 index 00000000..75b54925 --- /dev/null +++ b/docs/manual/mod/mod_vhost_alias.html @@ -0,0 +1,3 @@ +URI: mod_vhost_alias.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mod_vhost_alias.html.en b/docs/manual/mod/mod_vhost_alias.html.en new file mode 100644 index 00000000..c1fbed85 --- /dev/null +++ b/docs/manual/mod/mod_vhost_alias.html.en @@ -0,0 +1,312 @@ + + + +mod_vhost_alias - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache Module mod_vhost_alias

+
+

Available Languages:  en 

+
+ + + +
Description:Provides for dynamically configured mass virtual +hosting
Status:Extension
Module Identifier:vhost_alias_module
Source File:mod_vhost_alias.c
+

Summary

+ +

This module creates dynamically configured virtual hosts, by + allowing the IP address and/or the Host: header of + the HTTP request to be used as part of the pathname to + determine what files to serve. This allows for easy use of a + huge number of virtual hosts with similar configurations.

+ +

Note

+

If mod_alias or mod_userdir are + used for translating URIs to filenames, they will override the + directives of mod_vhost_alias described below. For + example, the following configuration will map + /cgi-bin/script.pl to + /usr/local/apache2/cgi-bin/script.pl in all cases:

+ +

+ ScriptAlias /cgi-bin/ /usr/local/apache2/cgi-bin/
+ VirtualScriptAlias /never/found/%0/cgi-bin/ +

+
+
+ +
top
+
+

Directory Name Interpolation

+ + +

All the directives in this module interpolate a string into + a pathname. The interpolated string (henceforth called the + "name") may be either the server name (see the UseCanonicalName + directive for details on how this is determined) or the IP + address of the virtual host on the server in dotted-quad + format. The interpolation is controlled by specifiers inspired + by printf which have a number of formats:

+ + + + + + + + + + + + +
%%insert a %
%pinsert the port number of the virtual host
%N.Minsert (part of) the name
+ +

N and M are used to specify + substrings of the name. N selects from the + dot-separated components of the name, and M + selects characters within whatever N has selected. + M is optional and defaults to zero if it isn't + present; the dot must be present if and only if M + is present. The interpretation is as follows:

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
0the whole name
1the first part
2the second part
-1the last part
-2the penultimate part
2+the second and all subsequent parts
-2+the penultimate and all preceding parts
1+ and -1+the same as 0
+ +

If N or M is greater than the number + of parts available a single underscore is interpolated.

+ +
top
+
+

Examples

+ + +

For simple name-based virtual hosts you might use the + following directives in your server configuration file:

+ +

+ UseCanonicalName Off
+ VirtualDocumentRoot /usr/local/apache/vhosts/%0 +

+ +

A request for + http://www.example.com/directory/file.html will be + satisfied by the file + /usr/local/apache/vhosts/www.example.com/directory/file.html. +

+ +

For a very large number of virtual hosts it is a good idea + to arrange the files to reduce the size of the + vhosts directory. To do this you might use the + following in your configuration file:

+ +

+ UseCanonicalName Off
+ VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2 +

+ +

A request for + http://www.domain.example.com/directory/file.html + will be satisfied by the file + /usr/local/apache/vhosts/example.com/d/o/m/domain/directory/file.html.

+ +

A more even spread of files can be achieved by hashing from the + end of the name, for example:

+ +

+ VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.-1/%2.-2/%2.-3/%2 +

+ +

The example request would come from + /usr/local/apache/vhosts/example.com/n/i/a/domain/directory/file.html.

+ +

Alternatively you might use:

+ +

+ VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2.4+ +

+ +

The example request would come from + /usr/local/apache/vhosts/example.com/d/o/m/ain/directory/file.html.

+ +

For IP-based virtual hosting you might use the following in + your configuration file:

+ +

+ UseCanonicalName DNS
+ VirtualDocumentRootIP /usr/local/apache/vhosts/%1/%2/%3/%4/docs
+ VirtualScriptAliasIP /usr/local/apache/vhosts/%1/%2/%3/%4/cgi-bin +

+ +

A request for + http://www.domain.example.com/directory/file.html + would be satisfied by the file + /usr/local/apache/vhosts/10/20/30/40/docs/directory/file.html + if the IP address of www.domain.example.com were + 10.20.30.40. A request for + http://www.domain.example.com/cgi-bin/script.pl would + be satisfied by executing the program + /usr/local/apache/vhosts/10/20/30/40/cgi-bin/script.pl.

+ +

If you want to include the . character in a + VirtualDocumentRoot directive, but it clashes with + a % directive, you can work around the problem in + the following way:

+ +

+ VirtualDocumentRoot /usr/local/apache/vhosts/%2.0.%3.0 +

+ +

A request for + http://www.domain.example.com/directory/file.html + will be satisfied by the file + /usr/local/apache/vhosts/domain.example/directory/file.html.

+ +

The LogFormat + directives %V and %A are useful + in conjunction with this module.

+
+
top
+

VirtualDocumentRoot Directive

+ + + + + + + +
Description:Dynamically configure the location of the document root +for a given virtual host
Syntax:VirtualDocumentRoot interpolated-directory|none
Default:VirtualDocumentRoot none
Context:server config, virtual host
Status:Extension
Module:mod_vhost_alias
+ +

The VirtualDocumentRoot directive allows you to + determine where Apache will find your documents based on the + value of the server name. The result of expanding + interpolated-directory is used as the root of the + document tree in a similar manner to the DocumentRoot directive's argument. + If interpolated-directory is none then + VirtualDocumentRoot is turned off. This directive + cannot be used in the same context as VirtualDocumentRootIP.

+ + +
+
top
+

VirtualDocumentRootIP Directive

+ + + + + + + +
Description:Dynamically configure the location of the document root +for a given virtual host
Syntax:VirtualDocumentRootIP interpolated-directory|none
Default:VirtualDocumentRootIP none
Context:server config, virtual host
Status:Extension
Module:mod_vhost_alias
+ +

The VirtualDocumentRootIP directive is like the + VirtualDocumentRoot + directive, except that it uses the IP address of the server end + of the connection for directory interpolation instead of the server + name.

+ +
+
top
+

VirtualScriptAlias Directive

+ + + + + + + +
Description:Dynamically configure the location of the CGI directory for +a given virtual host
Syntax:VirtualScriptAlias interpolated-directory|none
Default:VirtualScriptAlias none
Context:server config, virtual host
Status:Extension
Module:mod_vhost_alias
+ +

The VirtualScriptAlias directive allows you to + determine where Apache will find CGI scripts in a similar + manner to VirtualDocumentRoot does for other documents. It matches + requests for URIs starting /cgi-bin/, much like ScriptAlias + /cgi-bin/ would.

+ + +
+
top
+

VirtualScriptAliasIP Directive

+ + + + + + + +
Description:Dynamically configure the location of the cgi directory for +a given virtual host
Syntax:VirtualScriptAliasIP interpolated-directory|none
Default:VirtualScriptAliasIP none
Context:server config, virtual host
Status:Extension
Module:mod_vhost_alias
+ +

The VirtualScriptAliasIP directive is like the + VirtualScriptAlias + directive, except that it uses the IP address of the server end + of the connection for directory interpolation instead of the server + name.

+ + +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/module-dict.html b/docs/manual/mod/module-dict.html new file mode 100644 index 00000000..61d6c0f9 --- /dev/null +++ b/docs/manual/mod/module-dict.html @@ -0,0 +1,11 @@ +URI: module-dict.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: module-dict.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: module-dict.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mod/module-dict.html.en b/docs/manual/mod/module-dict.html.en new file mode 100644 index 00000000..a5106f98 --- /dev/null +++ b/docs/manual/mod/module-dict.html.en @@ -0,0 +1,117 @@ + + + +Terms Used to Describe Modules - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Terms Used to Describe Modules

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

This document describes the terms that are used to describe + each Apache module.

+
+ +
top
+
+

Description

+ +

A brief description of the purpose of the module.

+
top
+
+

Status

+ +

This indicates how tightly bound into the Apache Web server + the module is; in other words, you may need to recompile the + server in order to gain access to the module and its + functionality. Possible values for this attribute are:

+ +
+
MPM
+ +
A module with status "MPM" is a Multi-Processing Module. Unlike the + other types of modules, Apache must have one and only one MPM + in use at any time. This type of module is responsible for + basic request handling and dispatching.
+ +
Base
+ +
A module labeled as having "Base" status is compiled and + loaded into the server by default, and is therefore normally + available unless you have taken steps to remove the module + from your configuration.
+ +
Extension
+ +
A module with "Extension" status is not normally compiled + and loaded into the server. To enable the module and its + functionality, you may need to change the server build + configuration files and re-compile Apache.
+ +
Experimental
+ +
"Experimental" status indicates that the module is + available as part of the Apache kit, but you are on your own + if you try to use it. The module is being documented for + completeness, and is not necessarily supported.
+ +
External
+ +
Modules which are not included with the base Apache + distribution ("third-party modules") may use the "External" + status. We are not responsible for, nor do we support such + modules.
+
+
top
+
+

Source File

+ +

This quite simply lists the name of the source file which + contains the code for the module. This is also the name used by + the <IfModule> + directive.

+
top
+
+

Module Identifier

+ +

This is a string which identifies the module for use in the + LoadModule directive when + dynamically loading modules. In particular, it is the name of + the external variable of type module in the source file.

+
top
+
+

Compatibility

+ +

If the module was not part of the original Apache version 2 + distribution, the version in which it was introduced should be + listed here. In addition, if the module is limited to + particular platforms, the details will be listed here.

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/module-dict.html.ja.euc-jp b/docs/manual/mod/module-dict.html.ja.euc-jp new file mode 100644 index 00000000..60eeaf66 --- /dev/null +++ b/docs/manual/mod/module-dict.html.ja.euc-jp @@ -0,0 +1,119 @@ + + + +Apache ¥â¥¸¥å¡¼¥ë¤Î²òÀâ¤Ç»ÈÍѤ¹¤ëÍѸì - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

Apache ¥â¥¸¥å¡¼¥ë¤Î²òÀâ¤Ç»ÈÍѤ¹¤ëÍѸì

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

¤³¤Îʸ½ñ¤Ï Apache ¤Î³Æ ¥â¥¸¥å¡¼¥ë ¤òÀâÌÀ¤¹¤ë¤¿¤á¤Ë + »È¤ï¤ì¤Æ¤¤¤ëÍѸì¤òÀâÌÀ¤·¤Þ¤¹¡£

+
+ +
top
+
+

ÀâÌÀ

+ +

¥â¥¸¥å¡¼¥ë¤ÎÌÜŪ¤Îû¤¤ÀâÌÀ¡£

+
top
+
+

¥¹¥Æ¡¼¥¿¥¹

+ +

¤³¤ì¤Ï¡¢¤½¤Î¥â¥¸¥å¡¼¥ë¤¬ Apache + ¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë¤É¤ì¤¯¤é¤¤Ì©ÀܤËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤«¤ò¼¨¤·¤Þ¤¹¡£ + ¸À¤¤´¹¤¨¤ì¤Ð¡¢¥â¥¸¥å¡¼¥ë¤òÁȤ߹þ¤ß¡¢¤½¤Îµ¡Ç½¤òÍøÍѤ¹¤ë¤¿¤á¤Ë¡¢ + ¥µ¡¼¥Ð¤òºÆ¥³¥ó¥Ñ¥¤¥ë¤¹¤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Ê¤¤¤È¤¤¤¦¤³¤È¤ò¼¨¤·¤Þ¤¹¡£ + ¤³¤Î°À­¤¬¼è¤êÆÀ¤ëÃͤϰʲ¼¤Î¤â¤Î¤Ç¤¹:

+
+
MPM
+ +
¥¹¥Æ¡¼¥¿¥¹¤¬ "MPM" ¤Î¥â¥¸¥å¡¼¥ë¤Ï¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë¤Ç¤¹¡£ + ¾¤Î¼ïÎà¤Î¥â¥¸¥å¡¼¥ë¤È¤Ï°ã¤Ã¤Æ¡¢Apache ¤Ï¾ï¤Ë MPM ¤ò°ì¤Ä¤À¤± + »ÈÍѤ·Â³¤±¤Þ¤¹¡£¤³¤Î¼ïÎà¤Î¥â¥¸¥å¡¼¥ë¤Ï´ðËÜŪ¤Ê¥ê¥¯¥¨¥¹¥È¤Î°·¤¤¤È + ¥Ç¥£¥¹¥Ñ¥Ã¥Á¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£
+ +
Base
+ +
¥¹¥Æ¡¼¥¿¥¹¤¬ "Base" + ¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤ï¤¶¤ï¤¶ÀßÄ꤫¤é + ¥â¥¸¥å¡¼¥ë¤òºï½ü¤·¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢Ä̾ï¤ÏÍøÍѲÄǽ¤Ç¤¹¡£ +
+ +
Extension
+ +
¥¹¥Æ¡¼¥¿¥¹¤¬ "Extension" ¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤º¡¢¥µ¡¼¥Ð¤Ë¤âÆɤ߹þ¤Þ¤ì¤Þ¤»¤ó¡£ + ¤½¤Î¥â¥¸¥å¡¼¥ë¤È¤½¤Îµ¡Ç½¤òÍ­¸ú¤Ë¤¹¤ë¤Ë¤Ï¡¢ + ¥µ¡¼¥Ð¤ò¥Ó¥ë¥É¤¹¤ë¤¿¤á¤ÎÀßÄê¤òÊѹ¹¤·¤Æ¡¢Apache + ¤òºÆ¥³¥ó¥Ñ¥¤¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
+
Experimental
+ +
¥¹¥Æ¡¼¥¿¥¹¤¬ "Experimental" ¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢ + Apache ÇÛÉÛʪ¤ËƱº­¤µ¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢ + »ÈÍѤ¹¤ë¾ì¹ç¤Ï¼«¸ÊÀÕǤ¤Ç¹Ô¤Ê¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£ + ¤½¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤â´°À®¤Ë¸þ¤±¤ÆºîÀ®Ãæ¤Ç¤¹¤·¡¢ + ¥µ¥Ý¡¼¥È¤µ¤ì¤ë¤Æ¤¤¤ë¤È¤Ï¸Â¤ê¤Þ¤»¤ó¡£
+
External
+ +
¥¹¥Æ¡¼¥¿¥¹¤¬ "External" ¤Î¥â¥¸¥å¡¼¥ë¤Ï¡¢´ðËÜ Apache + ÇÛÉÛ¤ËƱº­¤µ¤ì¤Þ¤»¤ó ("¥µ¡¼¥É¥Ñ¡¼¥Æ¥£¡¼¥â¥¸¥å¡¼¥ë")¡£ + ¤½¤Î¤¿¤á¡¢²æ¡¹¤ËÀÕǤ¤Ï¤¢¤ê¤Þ¤»¤ó¤·¡¢ + ¤½¤Î¥â¥¸¥å¡¼¥ë¤Î¥µ¥Ý¡¼¥È¤â¤·¤Æ¤¤¤Þ¤»¤ó¡£
+
+
top
+
+

¥½¡¼¥¹¥Õ¥¡¥¤¥ë

+ +

¤³¤ì¤Ïñ½ã¤Ë¡¢ + ¤½¤Î¥â¥¸¥å¡¼¥ë¤ËɬÍפʥ³¡¼¥É¤ò´Þ¤à¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÎóµó¤·¤¿¤â¤Î¤Ç¤¹¡£ + ¤³¤ì¤Ï¡¢<IfModule> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ÈÍѤµ¤ì¤ë̾Á°¤Ç¤â¤¢¤ê¤Þ¤¹¡£ +

+
top
+
+

¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò

+ +

¤³¤Îʸ»úÎó¤Ï¡¢¥â¥¸¥å¡¼¥ë¤ÎưŪÆɤ߹þ¤ß¤ò¹Ô¤Ê¤¦¤È¤­¤Ë»ÈÍѤ¹¤ë LoadModule + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤ª¤¤¤Æ»ÈÍѤµ¤ì¤ë¥â¥¸¥å¡¼¥ë¤Î¼±Ê̻ҤǤ¹¡£ + ¾Ü¤·¤¯½ñ¤¯¤È¡¢¥½¡¼¥¹¥Õ¥¡¥¤¥ëÆâ¤Î module ¥¿¥¤¥×¤Î³°ÉôÊÑ¿ô¤Î̾Á°¤Ç¤¹¡£ +

+
top
+
+

¸ß´¹À­

+ +

¤¢¤ë¥â¥¸¥å¡¼¥ë¤¬ Apache ¥Ð¡¼¥¸¥ç¥ó 2 + ¤ÎÇÛÉۤ˴ޤޤì¤Æ¤¤¤Ê¤«¤Ã¤¿¾ì¹ç¡¢ + ¤½¤Î¥â¥¸¥å¡¼¥ë¤¬Æ³Æþ¤µ¤ì¤¿¥Ð¡¼¥¸¥ç¥ó¤¬¤³¤³¤Ë½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤Þ¤¿¡¢¥â¥¸¥å¡¼¥ë¤¬ÆÃÄê¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ë¤Î¤ß¸ºß¤¹¤ë¤È¤­¤â + ¾ÜºÙ¤Ï¤³¤³¤Ë½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/module-dict.html.ko.euc-kr b/docs/manual/mod/module-dict.html.ko.euc-kr new file mode 100644 index 00000000..ad71c9ac --- /dev/null +++ b/docs/manual/mod/module-dict.html.ko.euc-kr @@ -0,0 +1,109 @@ + + + +¸ðµâÀ» ¼³¸íÇϱâÀ§ÇØ »ç¿ëÇÑ ¿ë¾îµé - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¸ðµâÀ» ¼³¸íÇϱâÀ§ÇØ »ç¿ëÇÑ ¿ë¾îµé

+
+

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

+
+ +

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ ¸ðµâÀ» ¼³¸íÇϱâÀ§ÇØ + »ç¿ëÇÑ ¿ë¾î¸¦ ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

¼³¸í

+ +

¸ðµâ ¸ñÀû¿¡ ´ëÇÑ °£´ÜÇÑ ¼³¸í.

+
top
+
+

»óÅÂ

+ +

¸ðµâÀÌ ¾ÆÆÄÄ¡ À¥¼­¹ö¿Í ¾ó¸¶³ª ¹ÐÁ¢È÷ ¿¬°üµÇÀÖ´ÂÁö ³ªÅ¸³½´Ù. + Áï, ƯÁ¤ ¸ðµâ°ú ¸ðµâÀÇ ±â´ÉÀ» »ç¿ëÇϱâÀ§Çؼ­ ¼­¹ö¸¦ ´Ù½Ã + ÄÄÆÄÀÏÇØ¾ß ÇÒ °æ¿ì°¡ ÀÖ´Ù. ÀÌ ¼Ó¼ºÀÇ °ªÀº:

+ +
+
MPM
+ +
»óÅ°¡ "MPM"ÀÎ ¸ðµâÀº ´ÙÁßó¸® + ¸ðµâÀÌ´Ù. ´Ù¸¥ Á¾·ùÀÇ ¸ðµâ°ú ´Þ¸® ¾ÆÆÄÄ¡´Â ¿ÀÁ÷ ÇÑ + MPM¸¸À» »ç¿ëÇÑ´Ù. ÀÌ·± Á¾·ùÀÇ ¸ðµâÀº ±âº»ÀûÀÎ ¿äû ó¸®¿Í + ºÐ¹è¸¦ ´ã´çÇÑ´Ù.
+ +
Base
+ +
»óÅ°¡ "Base"ÀÎ ¸ðµâÀº ±âº»ÀûÀ¸·Î ¼­¹ö¿Í °°ÀÌ ÄÄÆÄÀϵǹǷÎ, + ¼³Á¤¿¡¼­ ¸ðµâÀ» Á¦°ÅÇÏÁö ¾Ê´Â ÇÑ º¸Åë »ç¿ëÇÒ ¼ö ÀÖ´Ù.
+ +
Extension
+ +
»óÅ°¡ "Extension"ÀÎ ¸ðµâÀº º¸Åë ¼­¹ö¿Í °°ÀÌ ÄÄÆÄÀϵÇÁö + ¾Ê´Â´Ù. ¸ðµâ°ú ¸ðµâÀÇ ±â´ÉÀ» »ç¿ëÇÏ·Á¸é ¼­¹ö ÄÄÆÄÀÏ + ±¸¼ºÆÄÀÏÀ» º¯°æÇÏ°í ¾ÆÆÄÄ¡¸¦ ´Ù½Ã ÄÄÆÄÀÏÇØ¾ß ÇÑ´Ù.
+ +
Experimental
+ +
"Experimental" »óÅ´ ¸ðµâÀÌ ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡ Æ÷ÇÔµÇÀÖÁö¸¸, + »ç¿ëÇÏ·Á¸é À§ÇèÀ» °¨¼öÇØ¾ß ÇÑ´Ù. ¸ðµâ¿¡ ´ëÇÑ ¹®¼­°¡ ÀÖÁö¸¸, + ¸ðµâÀ» Áö¿øÇÑ´Ù´Â ¸»Àº ¾Æ´Ï´Ù.
+ +
External
+ +
"External" »óÅ´ ±âº» ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡ Æ÷ÇÔµÇÁö ¾ÊÀº + ¸ðµâ("Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâ")ÀÌ´Ù. ¿ì¸®´Â ÀÌ·± ¸ðµâ¿¡ Ã¥ÀÓÀÌ + ¾ø°í Áö¿øÇÏÁöµµ ¾Ê´Â´Ù.
+
+
top
+
+

¼Ò½ºÆÄÀÏ

+ +

°£´ÜÇÏ°Ô ¸»Çؼ­ ¸ðµâ ¼Ò½ºÄڵ尡 ÀÖ´Â ¼Ò½ºÆÄÀϸíÀÌ´Ù. + <IfModule> + Áö½Ã¾î¿¡¼­ »ç¿ëÇÏ´Â À̸§À̱⵵ ÇÏ´Ù.

+
top
+
+

¸ðµâ¸í

+ +

¸ðµâÀ» ÁöĪÇÏ´Â ¹®ÀÚ¿­·Î, ¸ðµâÀ» µ¿ÀûÀ¸·Î ÀоîµéÀÌ´Â + LoadModule Áö½Ã¾î¿¡¼­ + »ç¿ëÇÑ´Ù. Á¤È®È÷ ¸»ÇÏ¸é ¼Ò½ºÆÄÀÏ¿¡¼­ module ÇüÀÇ ¿ÜºÎº¯¼ö + À̸§ÀÌ´Ù.

+
top
+
+

Áö¿ø

+ +

¸ðµâÀÌ ¿ø·¡ ¾ÆÆÄÄ¡ ¹öÀü 2 ¹èÆ÷º»¿¡ Æ÷ÇÔµÇÁö ¾Ê¾Ò´Ù¸é, + ¸ðµâÀ» óÀ½ ¼Ò°³ÇÑ ¹öÀüÀ» ¾Ë·ÁÁØ´Ù. ¶Ç, ¸ðµâÀÌ Æ¯Á¤ + Ç÷¡Æû¿ëÀ̶ó¸é »ó¼¼È÷ ¼³¸íÇÑ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mpm_common.html b/docs/manual/mod/mpm_common.html new file mode 100644 index 00000000..f76c5828 --- /dev/null +++ b/docs/manual/mod/mpm_common.html @@ -0,0 +1,11 @@ +URI: mpm_common.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: mpm_common.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mpm_common.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mpm_common.html.de b/docs/manual/mod/mpm_common.html.de new file mode 100644 index 00000000..6d1dfe34 --- /dev/null +++ b/docs/manual/mod/mpm_common.html.de @@ -0,0 +1,988 @@ + + + +mpm_common - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module
+
+

Allgemeine Direktiven der Apache-MPMs

+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+
Diese Übersetzung ist möglicherweise + nicht mehr aktuell. Bitte prüfen Sie die englische Version auf + die neuesten Änderungen.
+ +
Beschreibung:Eine Sammlung von Direktiven, die in mehr als einem + Multi-Processing-Modul (MPM) implementiert sind.
Status:MPM
+
+ + +
top
+

AcceptMutex-Direktive

+ + + + + + + +
Beschreibung:Vom Apache verwendete Methode zur Serialisierung mehrerer + Kindprozesse, die Anfragen an Netzwerk-Sockets entgegennehmen.
Syntax:AcceptMutex Default|Methode
Voreinstellung:AcceptMutex Default
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, perchild, prefork, threadpool, worker
+

Die Direktive AcceptMutex bestimmt die + Methode, die der Apache zur Serialisierung mehrerer Kindprozesse + verwendet, welche Anfragen an Netzwerk-Sockets entgegennehmen. Vor + Apache 2.0 war diese Methode nur zur Kompilierungszeit einstellbar. + Die optimale Methode ist sehr stark von der Architektur und + Plattform abhängig. Lesen Sie bitte Perfomance-Hinweise für + weitere Details.

+ +

Wenn die Direktive auf Default eingestellt ist, dann + wird die zur Kompilierungszeit gewählte Voreinstellung verwendet. + Weitere mögliche Methoden sind unten angegeben. Beachten Sie, dass + nicht alle Methoden auf allen Plattformen verfügbar sind. Wird + eine Methode angegeben, die nicht verfügbar ist, dann wird + eine Nachricht in das Fehlerprotokoll geschrieben, welche die + verfügbaren Methoden auflistet.

+ +
+
flock
+
verwendet die Systemfunktion flock(2), um die + durch die LockFile-Direktive definierte Datei zu sperren.
+ +
fcntl
+
verwendet die Systemfunktion fcntl(2), um die + durch die LockFile-Direktive definierte Datei zu sperren.
+ +
posixsem
+
verwendet POSIX-kompatible Semaphore, um den Mutex zu + implementieren.
+ +
pthread
+
verwendet gemäß der POSIX-Thread-Spezifikation + implementierte POSIX-Mutexe.
+ +
sysvsem
+
verwendet Semaphoren des SysV-Typs, um den Mutex zu + implementieren.
+
+ +

Um die bei der Kompilierung gewählte Voreinstellung für + Ihr System herauszufinden, können Sie Ihr LogLevel auf debug setzen. Dann wird der + voreingestellte AcceptMutex ins ErrorLog geschrieben.

+ +

Warnung

+

Auf den meisten Systemen stoppt der Server mit der Beantwortung von + Anfragen, wenn die Option pthread ausgewählt wurde und + ein Kindprozess unkontrolliert endet während er den + AcceptCntl-Mutex hält. In diesem Fall muss der Server + manuell neu gestartet werden, um wieder weiter zu arbeiten.

+

Eine Ausnahme stellt Solaris dar, da es einen Mechanismus anbietet, den + der Apache verwendet und der üblicherweise die Freigabe des Mutex + erlaubt, nachdem ein Kindprozess, der gerade einen Mutex hält, + abgestürzt ist.

+

Wenn Ihr System die Funktion + pthread_mutexattr_setrobust_np() bereitstellt, können + Sie wahrscheinlich die Option pthread problemlos + verwenden.

+
+ +
+
top
+

CoreDumpDirectory-Direktive

+ + + + + + + +
Beschreibung:Verzeichnis, in das der Apache zu wechseln versucht, bevor er + einen Hauptspeicherauszug erstellt
Syntax:CoreDumpDirectory Verzeichnis
Voreinstellung:Für die Voreinstellung siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_winnt, perchild, prefork, threadpool, worker
+

Dies beeinflusst das Verzeichnis, in welches der Apache zu wechseln + versucht, bevor er einen Hauptspeicherauszug (Anm.d.Ü.: einen + so genannten Core-Dump) erstellt. Die Voreinstellung ist das + ServerRoot-Verzeichnis. Da dieses + jedoch nicht für den Benutzer beschreibbar sein soll, unter dem + der Server läuft, werden normalerweise keine + Hauptspeicherauszüge geschrieben. Wenn Sie zum Debuggen + einen Hauptspeicherauszug haben möchten, können Sie + ihn mit dieser Direktive an einem anderen Ort ablegen lassen.

+ +

Hauptspeicherauszüge unter Linux

+

Wenn Apache als root startet und zu einem anderen Benutzer + wechselt, deaktiviert der Linux-Kernel Hauptspeicherauszüge + auch dann, wenn der Prozess in dem Verzeichnis schreiben darf. Ab Linux + 2.4 reaktiviert Apache (ab 2.0.46) Hauptspeicherauszüge wieder, + jedoch nur dann, wenn Sie explizit + CoreDumpDirectory konfigurieren.

+
+ +
+
top
+

EnableExceptionHook-Direktive

+ + + + + + + + +
Beschreibung:Aktiviert einen Hook, der nach einem Absturz noch +Ausnahmefehler behandeln lassen kann
Syntax:EnableExceptionHook On|Off
Voreinstellung:EnableExceptionHook Off
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, perchild, prefork, threadpool, worker
Kompatibilität:Verfügbar seit Version 2.0.49
+

Diese Direktive ist aus Sicherheitsgründen nur verfügbar, + wenn der Server mit der Option --enable-exception-hook + konfiguriert wurde. Sie aktiviert einen Hook, der es externen Modulen + erlaubt, sich dort einzuhängen und nach dem Absturz eines + Kindprozesses noch Aktionen durchzuführen.

+ +

Es existieren bereits zwei Module, mod_whatkilledus und + mod_backtrace, welche diesen Hook verwenden. Weitere + Informationen hierzu finden Sie auf Jeff Trawicks EnableExceptionHook-Seite.

+ +
+
top
+

Group-Direktive

+ + + + + + + + +
Beschreibung:Benutzergruppe, unter welcher der Server Anfragen + beantwortet
Syntax:Group Unix-Gruppe
Voreinstellung:Group #-1
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpmt_os2, perchild, prefork, threadpool, worker
Kompatibilität:Seit Apache 2.0 nur in der globalen Server-Konfiguration + gültig
+

Die Direktive Group bestimmt die + Benutzergruppe, unter welcher der Server Anfragen beantwortet. + Um diese Direktive zu verwenden, muss der Server als root gestartet + werden. Wenn Sie den Server unter einem nicht-root-Benutzer starten, + wird er nicht zur angegebenen Gruppe wechseln können und statt + dessen weiter mit der Gruppe des ursprünglichen Benutzers + laufen. Unix-Gruppe kann sein:

+ +
+
Ein Gruppenname
+
Verweist auf die durch den Namen angegebene Gruppe.
+ +
# gefolgt von einer Gruppennummer.
+
Verweist auf die durch ihre Nummer angegebene Gruppe.
+
+ +

Beispiel

+ Group www-group +

+ +

Es wird empfohlen, dass Sie eine neue Gruppe speziell zum Betrieb + des Servers erstellen. Einige Administratoren verwenden den Benutzer + nobody. Dies ist jedoch nicht immer möglich + oder gewünscht.

+ +

Sicherheit

+

Setzen Sie Group (oder User) nicht auf root, + solange Sie nicht ganz genau wissen, was Sie tun und welche Gefahren + Sie eingehen.

+
+ +

Wichtiger Hinweis: Die Verwendung der Direktive innerhalb von + <VirtualHost> + wird nicht länger unterstützt. Benutzen Sie SuexecUserGroup um Ihren Server + für suexec einzurichten.

+ +

Anmerkung

+

Obwohl die Direktive Group in den MPMs + beos und mpmt_os2 existiert, ist + sie dort tatsächlich eine Leeranweisung und exisitert nur + aus Kompatibilitätsgründen.

+
+ +
+
top
+

Listen-Direktive

+ + + + + + + +
Beschreibung:IP-Adressen und Ports, an denen der Server lauscht
Syntax:Listen [IP-Addresse:]Port
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_netware, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
Kompatibilität:Seit Apache 2.0 vorgeschrieben
+

Die Direktive Listen weist den Apache an, + nur an den angegebenen IP-Adressen oder Ports zu lauschen. + Standardmäßig antwortet er auf alle Anfragen an allen + IP-Interfaces. Listen ist nun eine notwendige + Anweisung. Wenn sie nicht in der Konfigurationsdatei enthalten ist, + wird der Server-Start fehlschlagen. Dies ist eine Änderung + gegenüber früheren Versionen des Apache.

+ +

Die Direktive Listen weist den Server an, + ankommende Anfragen am angegebenen Port oder der + Kombination aus Adresse und Port entgegenzunehmen. Wenn nur eine Portnummer + angegeben ist, dann lauscht der Server am angegebenen Port an allen + Interfaces. Wenn sowohl eine IP-Adresse als auch ein Port angegeben + sind, dann lauscht der Server am angegeben Port und Interface.

+ +

Es können mehrere Listen-Anweisungen + verwendet werden, um eine Reihe von Adressen und Port anzugeben, an + denen gelauscht werden soll. Der Server antwortet auf Anfragen von + jedem der aufgeführten Adressen und Ports.

+ +

Um beispielsweise den Server Verbindungen an den beiden Ports 80 und + 8000 annehmen zu lassen, verwenden Sie:

+ +

+ Listen 80
+ Listen 8000 +

+ +

Um den Server Verbindungen an zwei angegebenen Interfaces und Ports + annehmen zu lassen, verwenden Sie:

+ +

+ Listen 192.170.2.1:80
+ Listen 192.170.2.5:8000 +

+ +

IPv6-Adressen müssen wie in dem folgenden Beispiel in eckige + Klammern eingeschlossen werden:

+ +

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

+ +

Fehlermöglichkeit

+ Mehrere Listen-Direktiven für gleiche + IP-Adresse und Port führen zur Fehlermeldung + Address already in use (Anm.d.Ü.: Adresse schon in + Benutzung). +
+ +

Siehe auch

+ +
+
top
+

ListenBackLog-Direktive

+ + + + + + + +
Beschreibung:Maximale Länge der Warteschlange schwebender + Verbindungen
Syntax:ListenBacklog backlog
Voreinstellung:ListenBacklog 511
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_netware, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
+

Die maximale Länge der Warteschlange schwebender Verbindungen. + Üblicherweise ist keine Feineinstellung notwendig oder sinnvoll, + auf einigen System kann es jedoch gewünscht sein, diesen Wert bei + TCP-SYN-Angriffen zu erhöhen. Beachten Sie auch die Beschreibung des + backlog-Parameters der Systemfunktion listen(2).

+ +

Der Wert wird vom Betriebssystem oft auf eine niedrigere + Einstellung begrenzt. Dies variiert von Betriebssystem zu Betriebssystem. + Beachten Sie auch, dass viele Betriebssyteme nicht genau beachten, + was für backlog angegeben ist, jedoch einen Wert basierend auf der + Angabe (normalerweiseweise jedoch größer als diese) verwenden.

+ +
+
top
+

LockFile-Direktive

+ + + + + + + +
Beschreibung:Ablageort der Lock-Datei für die Serialisierung von +entgegengenommenen Anfragen
Syntax:LockFile Dateiname
Voreinstellung:LockFile logs/accept.lock
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, perchild, prefork, threadpool, worker
+

Die Direktive LockFile legt den Pfad zur + Lock-Datei fest, die verwendet wird, wenn der Apache mit einer der + AcceptMutex-Einstellungen + fcntl oder flock verwendet wird. Die Anweisung + sollte normalerweise bei der Voreinstellung belassen werden. + Der Hauptgrund, sie zu ändern, ist, wenn das + logs-Verzeichnis auf einem per NFS-eingebundenen Laufwerk + liegt, da die Lock-Datei auf einer lokalen Platte abgelegt sein + muss. Die PID (Anm.d.Ü.: Prozess-ID) des + Hauptserverprozesses wird automatisch an den Dateinamen angehängt.

+ +

Sicherheit

+

Es ist am besten, die Ablage in einem allgemein (Anm.d.Ü.: für + jedermann) beschreibbaren + Verzeichnis wie /var/tmp zu vermeiden, da + ein Denial-of-Servide-Angriff gestartet werden könnte und der + Server am Start gehindert werden könnte, indem eine Lock-Datei + mit dem gleichen Namen erstellt wird, wie der Server sie zu erstellen + versuchen würde.

+
+ +

Siehe auch

+ +
+
top
+

MaxClients-Direktive

+ + + + + + + +
Beschreibung:Maximale Anzahl der Kindprozesse, die zur Bedienung von Anfragen + gestartet wird
Syntax:MaxClients Anzahl
Voreinstellung:Für Details siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, prefork, threadpool, worker
+

Die Direktive MaxClients setzt die Grenze + für die Anzahl gleichzeitig bedienter Anfragen. Jeder + Verbindungsversuch oberhalb der MaxClients-Begrenzung wird üblicherweise in eine + Warteschlange gestellt, bis zu einer Anzahl basierend auf der + ListenBacklog-Anweisung. + Sobald ein Kindprozess am Ende einer anderen Anfrage freigegeben wird, + wird die Verbindung bedient.

+ +

Für Server ohne Thread-Unterstützung (z.B. + prefork) wird MaxClients als + maximale Anzahl der Kindprozesse verstanden, die zur Bedienung von + Anfragen gestartet werden. Die Voreinstellung ist 256. Um + diesen Wert zu erhöhen, muss auch ServerLimit angehoben werden.

+ +

Bei Servern mit Thread-Unterstützung und bei Hybrid-Servern + (z.B. beos oder worker) + begrenzt MaxClients die Gesamtzahl der Threads, + die für die Bedienung von Anfragen verfügbar sind. + Die Voreinstellung für beos ist 50. + Bei Hybrid-MPMs ist die Voreinstellung 16 (ServerLimit) multipliziert mit + dem Wert 25 (ThreadsPerChild). Um MaxClients + auf einen Wert zu erhöhen, der mehr als 16 Prozesse erfordert, + müssen Sie daher auch ServerLimit anheben.

+ +
+
top
+

MaxMemFree-Direktive

+ + + + + + + +
Beschreibung:Maximale Menge des Arbeitsspeichers, den die + Haupt-Zuteilungsroutine verwalten darf, ohne free() + aufzurufen
Syntax:MaxMemFree KBytes
Voreinstellung:MaxMemFree 0
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_netware, prefork, threadpool, worker, mpm_winnt
+

Die Direktive MaxMemFree gibt die maximale + Menge freier Kilobytes an, welche die Haupt-Zuteilungsroutine verwalten + darf, ohne free() aufzurufen. Wenn keine Angabe gemacht wird, + oder Null angegeben ist, wird dieser Wert nicht eingeschränkt.

+ +
+
top
+

MaxRequestsPerChild-Direktive

+ + + + + + + +
Beschreibung:Obergrenze für die Anzahl von Anfragen, die ein einzelner + Kindprozess während seines Lebens bearbeitet
Syntax:MaxRequestsPerChild number
Voreinstellung:MaxRequestsPerChild 10000
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, mpm_netware, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
+

Die Direktive MaxRequestsPerChild legt die + Grenze für die Anzahl von Anfragen fest, die ein einzelner + Kinprozess während seines Lebens bearbeitet. Nach + MaxRequestsPerChild Anfragen stirbt der + Kindprozess. Wenn MaxRequestsPerChild + 0 ist, endet der Prozess niemals.

+ +

Abweichende Voreinstellungen

+

Die Voreinstellung für mpm_netware und + mpm_winnt ist 0.

+
+ +

Die Begrenzung von MaxRequestsPerChild auf einen + Wert ungleich Null hat zwei vorteilhafte Auswirkungen:

+ +
    +
  • sie begrenzt die Menge an Arbeitsspeicher, die ein Prozess + durch (versehentliche) Speicherlecks verbrauchen kann.
    • + +
  • das Festlegen einer endlichen Lebensdauer von Prozessen hilft, die + Anzahl von Prozessen zu reduzieren, wenn die Serverlast + zurückgeht.
    • +
+ +

Anmerkung

+

Bei KeepAlive-Anfragen + wird nur die erste Anfrage für diese begrenzung gezählt. + Eigentlich wird nur die Begrenzung für die Anzahl der + Verbindungen pro Kindprozess geändert.

+
+ +
+
top
+

MaxSpareThreads-Direktive

+ + + + + + + +
Beschreibung:Maximale Anzahl unbeschäftigter Threads
Syntax:MaxSpareThreads Anzahl
Voreinstellung:Für Details siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_netware, mpmt_os2, perchild, threadpool, worker
+

Maximale Anzahl unbeschäftigter Threads. Die verschiedenen MPMs + behandeln diese Anweisung unterschiedlich.

+ +

Die Voreinstellung für perchild ist + MaxSpareThreads 10. Das MPM überwacht die Anzahl der + unbeschäftigten Threads auf der Basis einzelner Kindprozesse. Wenn + zu viele unbeschäftigte Threads in einem Kindprozess existieren, + beendet der Server Threads innerhalb dieses Kindprozesses.

+ +

Die Voreinstellung für worker, + leader und threadpool ist + MaxSpareThreads 250. Diese MPMs behandeln Threads + auf einer serverweiten Basis. Wenn zu viele unbeschäftigte Threads + im Server existieren, dann werden solange Kindprozesse beendet, bis + die Anzahl der unbeschäftigten Threads kleiner als der + angegebene Wert ist.

+ +

Die Voreinstellung für mpm_netware ist + MaxSpareThreads 100. Da dieses MPM nur einen einzigen + Prozess ausführt, ist die Zählung überschüssiger + Threads ebenfalls serverweit.

+ +

beos and mpmt_os2 arbeiten + ähnlich wie mpm_netware. Die Voreinstellung + für beos ist MaxSpareThreads 50. + Die Voreinstellung für mpmt_os2 ist + 10.

+ +

Restriktionen

+

Der Wertebereich von MaxSpareThreads + ist eingeschränkt. Apache korrigiert den angegebenen Wert + automatisch gemäß den folgenden Regeln:

+ +
+ +

Siehe auch

+ +
+
top
+

MinSpareThreads-Direktive

+ + + + + + + +
Beschreibung:Minimale Anzahl unbeschäftigter Threads, die zur + Bedienung von Anfragespitzen zur Verfügung stehen
Syntax:MinSpareThreads Anzahl
Voreinstellung:Für Details siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_netware, mpmt_os2, perchild, threadpool, worker
+

Minimale Anzahl unbeschäftigter Threads, um Anfragespitzen + zu bedienen. Die verschiedenen MPMs behandeln die Anweisung + unterschiedlich.

+ +

perchild verwendet die Voreinstellung + MinSpareThreads 5 und überwacht die Anzahl der + unbeschäftigten Threads auf der Basis einzelner Kindprozesse. Wenn + in einem Kindprozess nicht genügend unbeschäftigte + Threads vorhanden sind, erstellt der Server neue Threads innerhalb + dieses Kindprozesses. Wenn Sie also NumServers auf 10 und MinSpareThreads auf einen Wert von 5 setzen, + haben Sie mindestens 50 unbeschäftigte Threads auf Ihrem + System.

+ +

worker, leader und + threadpool verwenden eine Voreinstellung von + MinSpareThreads 75 und behandeln unbeschäftigte + Threads auf serverweiter Basis. Wenn nicht genügend + unbeschäftigte Threads im Server vorhanden sind, dann + werden solange Kindprozesse erzeugt, bis die Anzahl unbeschäftigter + Threads größer als der angegebene Wert ist.

+ +

mpm_netware verwendet die Voreinstellung + MinSpareThreads 10 und verfolgt dies serverweit, da + es ein Einzelprozess-MPM ist.

+ +

beos und mpmt_os2 arbeiten + ähnlich wie mpm_netware. Die Voreinstellung + für beos ist MinSpareThreads 1. + Die Voreinstellung für mpmt_os2 ist + 5.

+ + +

Siehe auch

+ +
+
top
+

PidFile-Direktive

+ + + + + + + +
Beschreibung:Datei, in welcher der Server die Prozess-ID des Daemons +ablegt
Syntax:PidFile Dateiname
Voreinstellung:PidFile logs/httpd.pid
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
+

Die Direktive PidFile bestimmt die Datei, + in welcher der Server die Prozess-ID des Daemons ablegt. Wenn der + Dateiname nicht absolut angegeben wird, wird er relativ zu + ServerRoot interpretiert.

+ +

Beispiel

+ PidFile /var/run/apache.pid +

+ +

Es ist oft hilfreich, dem Server ein Signal senden zu können, + damit er seine ErrorLogs und + TransferLogs + schließt und dann neu öffnet und seine + Konfigurationsdateien neu einliest. Dies kann durch Senden eines + SIGHUP-Signals (kill -1) an die Prozess-ID geschehen, die im + PidFile eingetragen ist.

+ +

Die PidFile-Datei unterliegt den + gleichen Warnungen über die Ablage von Protokolldateien + und Sicherheit.

+ +

Anmerkung

+

Ab Apache 2 wird empfohlen, nur das Skript apachectl zum (Neu-)Starten und Stoppen des Servers zu + verwenden.

+
+ +
+
top
+

ScoreBoardFile-Direktive

+ + + + + + + +
Beschreibung:Ablageort der Datei, die zur Speicherung von Daten zur + Koordinierung der Kindprozesse verwendet wird
Syntax:ScoreBoardFile Dateipfad
Voreinstellung:ScoreBoardFile logs/apache_status
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_winnt, perchild, prefork, threadpool, worker
+

Apache verwendet ein Scoreboard zur Kommunikation zwischen + seinen Eltern- und Kindprozessen. Einige Architekturen erfordern + eine Datei zur Unterstützung der Kommunikation. Wenn die Datei + undefiniert bleibt, versucht der Apache zuerst, das Scoreboard im + Arbeitsspeicher zu erstellen (Verwendung von anonymem Shared-Memory), + und versucht bei einem Fehlschlag anschließend die Datei auf + der Festplatte zu erstellen (Verwendung von Datei-basiertem + Shared-Memory). Die Angabe dieser Direktive veranlaßt den + Apache stets, die Datei auf der Festplatte zu erstellen.

+ +

Beispiel

+ ScoreBoardFile /var/run/apache_status +

+ +

Datei-basiertes Shared-Memory ist für Applikationen von + Drittanbietern hilfreich, die direkten Zugriff auf das Scoreboard + benötigen.

+ +

Wenn Sie eine ScoreBoardFile-Anweisung + verwenden, erreichen Sie eventuell eine höhere Geschwindigkeit, wenn + Sie die Datei auf einer RAM-Disk ablegen. Achten Sie darauf, die + gleichen Warnungen wie über die Ablage von Protokolldateien und + Sicherheit zu beherzigen.

+ +

Siehe auch

+ +
+
top
+

SendBufferSize-Direktive

+ + + + + + + +
Beschreibung:Größe des TCP-Puffers
Syntax:SendBufferSize Bytes
Voreinstellung:SendBufferSize 0
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, leader, mpm_netware, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
+

Der Server setzt die Größe des TCP-Puffers auf die + angegebene Anzahl Bytes. Dies ist sehr hilfreich, um Voreinstellungen + alter Standardbetriebssysteme für Hochgeschwindigkeitsverbindungen + mit hoher Latenzzeit anzuheben (d.h. 100ms oder so, wie bei + Interkontinentalverbindungen).

+ +

Wird der Wert auf 0 gesetzt, dann verwendet der Server + die Voreinstellung des Betriebssystems.

+ +
+
top
+

ServerLimit-Direktive

+ + + + + + + +
Beschreibung:Obergrenze für die konfigurierbare Anzahl von + Prozessen
Syntax:ServerLimit Anzahl
Voreinstellung:Für Details siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, perchild, prefork, threadpool, worker
+

Bei dem MPM prefork bestimmt die Direktive + den während der Lebensdauer des Apache-Prozesses maximal + einstellbaren Wert für MaxClients. Beim MPM + worker bestimmt die Direktive in Verbindung mit + ThreadLimit den Maximalwert + für MaxClients + für die Lebensdauer des Apache-Prozesses. Jeder Versuch, diese + Anweisung während eines Neustarts zu ändern, wird ignoriert. + MaxClients kann jedoch + während eines Neustarts geändert werden.

+ +

Lassen Sie besondere Vorsicht bei der Verwendung dieser Direktive + walten. Wenn ServerLimit auf einen Wert deutlich + höher als notwendig gesetzt wird, wird zusätzliches, + unbenutztes Shared-Memory belegt. Wenn sowohl + ServerLimit als auch MaxClients auf Werte gesetzt werden, die + größer sind, als das System sie handhaben kann, dann kann + der Apache möglicherweise nicht starten, oder das System kann + instabil werden.

+ +

Verwenden Sie die Direktive bei dem MPM prefork + nur, wenn Sie MaxClients + auf mehr als 256 (Voreinstellung) setzen müssen. Setzen Sie den + Wert nicht höher als den Wert, den Sie für MaxClients angeben möchten.

+ +

Verwenden Sie die Direktive bei worker, + leader und threadpool nur, wenn Ihre + MaxClients- und + ThreadsPerChild-Einstellungen + mehr als 16 Serverprozesse (Voreinstellung) erfordern. Setzen Sie den + Wert dieser Direktive nicht höher, als die Anzahl der Serverprozesse, + die dafür erforderlich ist, was Sie bei MaxClients und + ThreadsPerChild angeben + möchten.

+ +

Verwenden Sie die Direktive beim MPM perchild nur, + wenn Sie NumServers auf einen + Wert größer als 8 (Voreinstellung) setzen müssen.

+ +

Anmerkung

+

Eine feste Begrenzung von ServerLimit 20000 ist in den + Server einkompiliert (bei dem MPM prefork 200000). + Dies soll unangenehme Effekte durch Tippfehler verhindern.

+
+ +

Siehe auch

+ +
+
top
+

StartServers-Direktive

+ + + + + + + +
Beschreibung:Anzahl der Kindprozesse des Servers, die beim Start erstellt + werden
Syntax:StartServers Anzahl
Voreinstellung:Für Details siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, mpmt_os2, prefork, threadpool, worker
+

Die Direktive StartServers bestimmt + die Anzahl der Kindprozesse des Servers, die beim Start erstellt + werden. Da die Anzahl der Prozesse abhängig von der Last + dynamisch kontrolliert wird, besteht normalerweise wenig + Grund für eine Änderung dieses Parameters.

+ +

Die Voreinstellung unterscheidet sich von MPM zu MPM. Bei + leader, threadpool und + worker ist die Voreinstellung + StartServers 3. Die Voreinstellung bei + prefork ist 5 und bei + mpmt_os2 2.

+ +
+
top
+

StartThreads-Direktive

+ + + + + + + +
Beschreibung:Anzahl der Threads, die beim Start erstellt werden
Syntax:StartThreads Anzahl
Voreinstellung:Für Details siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:beos, mpm_netware, perchild
+

Anzahl der Threads, die beim Start erstellt werden. Da die Anzahl + der Threads abhängig von der Last dynamisch kontrolliert wird, + besteht normalerweise wenig Grund für eine Änderung + dieses Parameters.

+ +

Die Voreinstellung für perchild ist + StartThreads 5. Die Direktive setzt während des + Starts die Anzahl der Threads pro Prozess.

+ +

Die Voreinstellung bei mpm_netware ist + StartThreads 50. Da hier lediglich ein einzelner Prozess + existiert, ist dies die Gesamtzahl der Threads, die beim Start + erstellt wird, um Anfragen zu bedienen.

+ +

Die Voreinstellung für beos ist StartThreads + 10. Die Einstellung reflektiert ebenfalls die Gesamtzahl der Threads, die + beim Start erstellt werden, um Anfragen zu bedienen.

+ +
+
top
+

ThreadLimit-Direktive

+ + + + + + + + +
Beschreibung:Bestimmt die Obergrenze der konfigurierbaren Anzahl von Threads + pro Kindprozess
Syntax:ThreadLimit Anzahl
Voreinstellung:Für Details siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, mpm_winnt, perchild, threadpool, worker
Kompatibilität:Verfügbar für mpm_winnt ab + Apache 2.0.41
+

Die Direktive bestimmt den während der Lebensdauer des + Apache-Prozesses maximal einstellbaren Wert für + ThreadsPerChild. Jeder + Versuch, diese Direktive während eines Neustarts zu ändern, + wird ignoriert. ThreadsPerChild + kann jedoch während eines Neustarts modifiziert werden bis zu dem + Wert dieser Anweisung.

+ +

Lassen Sie besondere Vorsicht bei der Verwendung dieser Direktive + walten. Wenn ThreadLimit auf einen Wert + deutlich höher als ThreadsPerChild gesetzt wird, wird + zusätzliches, ungenutztes Shared-Memory belegt. Wenn sowohl + ThreadLimit als auch ThreadsPerChild auf Werte gesetzt werden, + die größer sind, als das System sie handhaben kann, dann kann + der Apache möglicherweise nicht starten oder das System kann + instabil werden. Setzen Sie den Wert dieser Direktive nicht höher + als Ihre größte erwartete Einstellung für + ThreadsPerChild + während der aktuellen Ausführung des Apache.

+ +

Die Voreinstellung für ThreadLimit ist + 1920 wenn sie zusammen mit mpm_winnt + verwendet wird, und 64 bei der Verwendung mit anderen + MPMs.

+ +

Anmerkung

+

Eine feste Begrenzung von ThreadLimit 20000 + (oder ThreadLimit 15000 bei mpm_winnt) + ist in den Server einkompiliert. Dies soll unangenehme Effekte durch + Tippfehler verhindern.

+
+ +
+
top
+

ThreadsPerChild-Direktive

+ + + + + + + +
Beschreibung:Anzahl der Threads, die mit jedem Kindprozess gestartet + werden
Syntax:ThreadsPerChild Anzahl
Voreinstellung:Für Details siehe Beschreibung
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, mpm_winnt, threadpool, worker
+

Die Direktive legt die Anzahl der Threads fest, die mit jedem + Kindprozess gestartet werden. Der Kindprozess erstellt diese Threads + beim Start und erstellt später keine weiteren mehr. Wenn Sie ein + MPM wie mpm_winnt verwenden, wo nur ein + Kindprozess existiert, dann sollte diese Angabe hoch genug sein, + die gesamte Last des Servers zu bewältigen. Wenn Sie ein MPM + wie worker verwenden, wo mehrere Kindprozesse + existieren, dann sollte die Gesamtzahl der Thread groß + genug sein, die übliche Last auf dem Server zu bewältigen.

+ +

Die Voreinstellung für ThreadsPerChild ist + 64, wenn mpm_winnt verwendet wird, und + 25 bei der Verwendung der anderen MPMs.

+ +
+
top
+

ThreadStackSize-Direktive

+ + + + + + + + +
Beschreibung:Die Größe des Stacks in Bytes, der von Threads +verwendet wird, die Client-Verbindungen bearbeiten.
Syntax:ThreadStackSize size
Voreinstellung:65536 unter NetWare; variiert bei anderen Betriebssystemen.
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, mpm_netware, mpm_winnt, perchild, threadpool, worker
Kompatibilität:Verfügbar seit Version 2.1
+

Die Direktive ThreadStackSize legt die + Größe des Stacks (für Autodaten) der Threads fest, die + Client-Verbindungen bearbeiten und Module aufrufen, welche bei der + Verarbeitung dieser Verbindungen helfen. In den meisten Fällen ist die + Voreinstellung des Betriebssystems angemessen, doch unter bestimmten + Umständen kann es sinnvoll sein, den Wert anzupassen:

+ +
    +
  • Auf Plattformen mit einer relativ kleinen Voreingestellung für + die Größe des Thread-Stacks (z.B. HP-UX) kann der Apache bei + der Verwendung einiger Drittanbietermodule, die einen relativ hohen Bedarf + an Speicherplatz haben, abstürzen. Ebendiese Module arbeiten + möglicherweise problemlos auf anderen Plattformen, wo der + voreingestellte Thread-Stack größer ist. Derartige + Abstürze können Sie vermeiden, indem Sie + ThreadStackSize auf einen höheren Wert als die + Betriebssystemvoreinstellung setzen. Eine solche Anpassung ist nur + notwendig, wenn es vom Anbieter des Moduls so spezifiziert wurde oder die + Diagnose eines Apache-Absturzes ergeben hat, das die + Thread-Stackgröße zu klein war.
    • + +
  • Auf Plattformen, wo die voreingestellte Thread-Stackgröße + für die Webserverkonfiguration deutlich größer als + notwendig ist, kann eine größere Anzahl von Threads pro + Kindprozess erreicht werden, wenn ThreadStackSize + auf einen Wert kleiner als die Betriebssystemvoreinstellung gesetzt wird. + Da es einzelne Anfragen geben kann, die mehr Stack zur Verarbeitung + benötigen, sollte eine derartige Korrektur ausschließlich in + Testumgebungen zum Einsatz kommen, auf denen die gesamte + Webserververarbeitung ausprobiert werden kann. Eine Änderung der + Webserverkonfiguration kann den aktuellen Wert der + ThreadStackSize ungültig machen.
    • +
+ +
+
top
+

User-Direktive

+ + + + + + + + +
Beschreibung:Die Benutzerkennung, unter welcher der Server Anfragen + beantwortet
Syntax:User Unix-User-ID
Voreinstellung:User #-1
Kontext:Serverkonfiguration
Status:MPM
Modul:leader, perchild, prefork, threadpool, worker
Kompatibilität:Seit Apache 2.0 nur in der globalen Server-Konfiguration +gültig
+

Die Direktive User legt die Benutzerkennung + fest, mit der der Server Anfragen beantwortet. Um diese Anweisung + zu verwenden, muss der Server als root gestartet werden. + Wenn Sie den Server unter einem nicht-root-Benutzer starten, kann + er nicht zu dem minder privilegierten Benutzer wechseln und wird statt + dessen weiter mit der ursprünglichen Benutzerkennung laufen. + Wenn Sie den Server als root starten, dann ist es normal, + dass der Elternprozess als root weiterläuft. + Unix-User-ID kann sein:

+ +
+
Ein Benutzername
+
Verweist auf den durch Namen angegebenen Benutzer.
+ +
# gefolgt von einer Benutzernummer.
+
Verweist auf einen durch eine Nummer angegebenen Benutzer.
+
+ +

Der Benutzer sollte keine Rechte besitzen, die dazu führen, + dass er in der Lage ist, auf Dateien zuzugreifen, die nicht dafür + bestimmt sind, für die Außenwelt sichtbar zu sein. + Gleichermaßen sollte der Benutzer nicht in der Lage sein, + Code auszuführen, der nicht für HTTP-Anfragen bestimmt ist. + Es wird empfohlen, einen neuen Benutzer und eine neue Gruppe speziell + zur Ausführung des Servers zu erstellen. Einige Administratoren + verwenden den Benutzer nobody. Dies ist jedoch nicht + immer wünschenswert, da der Benuter nobody andere + Rechte auf dem System besitzen kann.

+ +

Sicherheit

+

Setzen Sie User (oder Group) nicht auf root, + solange Sie nicht genau wissen, was Sie tun, und welches die Gefahren + sind.

+
+ +

Beim MPM perchild, das dafür gedacht ist, + virtuelle Hosts unter verschiedenen Benutzerkennungen auszuführen, + bestimmt die Direktive User die + Benutzerkennung für den Hauptserver und bildet den Rückfallwert + für <VirtualHost>-Abschnitte ohne eine + AssignUserID-Anweisung.

+ +

Wichtiger Hinweis: Die Verwendung dieser Direktive innerhalb von + <VirtualHost> wird + nicht mehr unterstützt. Benutzen Sie SuexecUserGroup, um Ihren Server + für suexec einzurichten.

+ +

Anmerkung

+

Obwohl die Direktive User in den MPMs + beos und mpmt_os2 existiert, ist + sie dort tatsächlich eine Leeranweisung und exisitert nur + aus Kompatibilitätsgründen.

+
+ +
+
+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mpm_common.html.en b/docs/manual/mod/mpm_common.html.en new file mode 100644 index 00000000..da778487 --- /dev/null +++ b/docs/manual/mod/mpm_common.html.en @@ -0,0 +1,941 @@ + + + +mpm_common - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache MPM Common Directives

+
+

Available Languages:  de  | + en  | + ja 

+
+ +
Description:A collection of directives that are implemented by +more than one multi-processing module (MPM)
Status:MPM
+
+ + +
top
+

AcceptMutex Directive

+ + + + + + + +
Description:Method that Apache uses to serialize multiple children +accepting requests on network sockets
Syntax:AcceptMutex Default|method
Default:AcceptMutex Default
Context:server config
Status:MPM
Module:prefork, worker
+

The AcceptMutex directives sets the + method that Apache uses to serialize multiple children accepting + requests on network sockets. Prior to Apache 2.0, the method was + selectable only at compile time. The optimal method to use is + highly architecture and platform dependent. For further details, + see the performance tuning + documentation.

+ +

If this directive is set to Default, then the + compile-time selected default will be used. Other possible + methods are listed below. Note that not all methods are + available on all platforms. If a method is specified which is + not available, a message will be written to the error log + listing the available methods.

+ +
+
flock
+
uses the flock(2) system call to lock the + file defined by the LockFile directive.
+ +
fcntl
+
uses the fcntl(2) system call to lock the + file defined by the LockFile directive.
+ +
posixsem
+
uses POSIX compatible semaphores to implement the mutex.
+ +
pthread
+
uses POSIX mutexes as implemented by the POSIX Threads + (PThreads) specification.
+ +
sysvsem
+
uses SySV-style semaphores to implement the mutex.
+
+ +

If you want to find out the compile time chosen default + for your system, you may set your LogLevel to debug. Then the default AcceptMutex will be written into the ErrorLog.

+ +

Warning

+

On most systems, when the pthread option + is selected, if a child process terminates abnormally + while holding the AcceptCntl mutex the + server will stop responding to requests. When this + occurs, the server will require a manual restart to + recover.

+

Solaris is a notable exception as it provides a + mechanism, used by Apache, which usually allows the + mutex to be recovered after a child process terminates + abnormally while holding a mutex.

+

If your system implements the + pthread_mutexattr_setrobust_np() function, + you may be able to use the pthread option safely.

+
+ +
+
top
+

CoreDumpDirectory Directive

+ + + + + + + +
Description:Directory where Apache attempts to +switch before dumping core
Syntax:CoreDumpDirectory directory
Default:See usage for the default setting
Context:server config
Status:MPM
Module:beos, mpm_winnt, prefork, worker
+

This controls the directory to which Apache attempts to + switch before dumping core. The default is in the + ServerRoot directory, however + since this should not be writable by the user the server runs + as, core dumps won't normally get written. If you want a core + dump for debugging, you can use this directive to place it in a + different location.

+ +

Core Dumps on Linux

+

If Apache starts as root and switches to another user, the + Linux kernel disables core dumps even if the directory is + writable for the process. Apache (2.0.46 and later) reenables core dumps + on Linux 2.4 and beyond, but only if you explicitly configure a CoreDumpDirectory.

+
+ +
+
top
+

EnableExceptionHook Directive

+ + + + + + + + +
Description:Enables a hook that runs exception handlers +after a crash
Syntax:EnableExceptionHook On|Off
Default:EnableExceptionHook Off
Context:server config
Status:MPM
Module:prefork, worker
Compatibility:Available in version 2.0.49 and later
+

For safety reasons this directive is only available if the server was + configured with the --enable-exception-hook option. It + enables a hook that allows external modules to plug in and do something + after a child crashed.

+ +

There are already two modules, mod_whatkilledus and + mod_backtrace that make use of this hook. Please have a + look at Jeff Trawick's EnableExceptionHook site for more information about these.

+ +
+
top
+

GracefulShutdownTimeout Directive

+ + + + + + + + +
Description:Specify a timeout after which a gracefully shutdown server +will exit.
Syntax:GracefulShutDownTimeout seconds
Default:GracefulShutDownTimeout 0
Context:server config
Status:MPM
Module:prefork, worker, event
Compatibility:Available in version 2.2 and later
+

The GracefulShutdownTimeout specifies + how many seconds after receiving a "graceful-stop" signal, a + server should continue to run, handling the existing connections.

+ +

Setting this value to zero means that the server will wait + indefinitely until all remaining requests have been fully served.

+ +
+
top
+

Group Directive

+ + + + + + + + +
Description:Group under which the server will answer +requests
Syntax:Group unix-group
Default:Group #-1
Context:server config
Status:MPM
Module:beos, mpmt_os2, prefork, worker
Compatibility:Only valid in global server config since Apache +2.0
+

The Group directive sets the group under + which the server will answer requests. In order to use this + directive, the server must be run initially as root. If + you start the server as a non-root user, it will fail to change to the + specified group, and will instead continue to run as the group of the + original user. Unix-group is one of:

+ +
+
A group name
+
Refers to the given group by name.
+ +
# followed by a group number.
+
Refers to a group by its number.
+
+ +

Example

+ Group www-group +

+ +

It is recommended that you set up a new group specifically for + running the server. Some admins use user nobody, + but this is not always possible or desirable.

+ +

Security

+

Don't set Group (or User) to root unless + you know exactly what you are doing, and what the dangers are.

+
+ +

Special note: Use of this directive in <VirtualHost> is no longer supported. To + configure your server for suexec use + SuexecUserGroup.

+ +

Note

+

Although the Group directive is present + in the beos and mpmt_os2 MPMs, + it is actually a no-op there and only exists for compatibility + reasons.

+
+ +
+
top
+

Listen Directive

+ + + + + + + +
Description:IP addresses and ports that the server +listens to
Syntax:Listen [IP-address:]portnumber [protocol]
Context:server config
Status:MPM
Module:beos, mpm_netware, mpm_winnt, mpmt_os2, prefork, worker, event
Compatibility:Required directive since Apache 2.0
+The protocol argument was added in 2.1.5
+

The Listen directive instructs Apache to + listen to only specific IP addresses or ports; by default it + responds to requests on all IP interfaces. Listen + is now a required directive. If it is not in the config file, the + server will fail to start. This is a change from previous versions + of Apache.

+ +

The Listen directive tells the server to + accept incoming requests on the specified port or address-and-port + combination. If only a port number is specified, the server listens to + the given port on all interfaces. If an IP address is given as well + as a port, the server will listen on the given port and + interface.

+ +

Multiple Listen directives may be used to + specify a number of addresses and ports to listen to. The server will + respond to requests from any of the listed addresses and ports.

+ +

For example, to make the server accept connections on both + port 80 and port 8000, use:

+ +

+ Listen 80
+ Listen 8000 +

+ +

To make the server accept connections on two specified + interfaces and port numbers, use

+ +

+ Listen 192.170.2.1:80
+ Listen 192.170.2.5:8000 +

+ +

IPv6 addresses must be surrounded in square brackets, as in the + following example:

+ +

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

+ +

The optional protocol argument is not required for most + configurations. If not specified, https is the default for + port 443 and http the default for all other ports. The + protocol is used to determine which module should handle a request, and + to apply protocol specific optimizations with the + AcceptFilter directive.

+ +

You only need to set the protocol if you are running on non-standard + ports. For example, running an https site on port 8443:

+ +

+ Listen 192.170.2.1:8443 https +

+ +

Error condition

+ Multiple Listen directives for the same ip + address and port will result in an Address already in use + error message. +
+ + +

See also

+ +
+
top
+

ListenBackLog Directive

+ + + + + + + +
Description:Maximum length of the queue of pending connections
Syntax:ListenBacklog backlog
Default:ListenBacklog 511
Context:server config
Status:MPM
Module:beos, mpm_netware, mpm_winnt, mpmt_os2, prefork, worker
+

The maximum length of the queue of pending connections. + Generally no tuning is needed or desired, however on some + systems it is desirable to increase this when under a TCP SYN + flood attack. See the backlog parameter to the + listen(2) system call.

+ +

This will often be limited to a smaller number by the + operating system. This varies from OS to OS. Also note that + many OSes do not use exactly what is specified as the backlog, + but use a number based on (but normally larger than) what is + set.

+ +
+
top
+

LockFile Directive

+ + + + + + + +
Description:Location of the accept serialization lock file
Syntax:LockFile filename
Default:LockFile logs/accept.lock
Context:server config
Status:MPM
Module:prefork, worker
+

The LockFile directive sets the path to + the lockfile used when Apache is used with an AcceptMutex value of either + fcntl or flock. This directive should + normally be left at its default value. The main reason for changing + it is if the logs directory is NFS mounted, since + the lockfile must be stored on a local disk. The PID + of the main server process is automatically appended to the + filename.

+ +

Security

+

It is best to avoid putting this file in a world writable + directory such as /var/tmp because someone could create + a denial of service attack and prevent the server from starting by + creating a lockfile with the same name as the one the server will try + to create.

+
+ +

See also

+ +
+
top
+

MaxClients Directive

+ + + + + + + +
Description:Maximum number of child processes that will be created +to serve requests
Syntax:MaxClients number
Default:See usage for details
Context:server config
Status:MPM
Module:beos, prefork, worker
+

The MaxClients directive sets the limit + on the number of simultaneous requests that will be served. Any + connection attempts over the MaxClients + limit will normally be queued, up to a number based on the + ListenBacklog + directive. Once a child process is freed at the end of a different + request, the connection will then be serviced.

+ +

For non-threaded servers (i.e., prefork), + MaxClients translates into the maximum + number of child processes that will be launched to serve requests. + The default value is 256; to increase it, you must also raise + ServerLimit.

+ +

For threaded and hybrid servers (e.g. beos + or worker) MaxClients restricts + the total number of threads that will be available to serve clients. + The default value for beos is 50. For + hybrid MPMs the default value is 16 (ServerLimit) multiplied by the value of + 25 (ThreadsPerChild). Therefore, to increase MaxClients to a value that requires more than 16 processes, + you must also raise ServerLimit.

+ +
+
top
+

MaxMemFree Directive

+ + + + + + + +
Description:Maximum amount of memory that the main allocator is allowed +to hold without calling free()
Syntax:MaxMemFree KBytes
Default:MaxMemFree 0
Context:server config
Status:MPM
Module:beos, mpm_netware, prefork, worker, mpm_winnt
+

The MaxMemFree directive sets the + maximum number of free Kbytes that the main allocator is allowed + to hold without calling free(). When not set, or when set + to zero, the threshold will be set to unlimited.

+ +
+
top
+

MaxRequestsPerChild Directive

+ + + + + + + +
Description:Limit on the number of requests that an individual child server +will handle during its life
Syntax:MaxRequestsPerChild number
Default:MaxRequestsPerChild 10000
Context:server config
Status:MPM
Module:mpm_netware, mpm_winnt, mpmt_os2, prefork, worker
+

The MaxRequestsPerChild directive sets + the limit on the number of requests that an individual child + server process will handle. After + MaxRequestsPerChild requests, the child + process will die. If MaxRequestsPerChild is + 0, then the process will never expire.

+ +

Different default values

+

The default value for mpm_netware and + mpm_winnt is 0.

+
+ +

Setting MaxRequestsPerChild to a + non-zero limit has two beneficial effects:

+ +
    +
  • it limits the amount of memory that process can consume + by (accidental) memory leakage;
    • + +
  • by giving processes a finite lifetime, it helps reduce + the number of processes when the server load reduces.
    • +
+ +

Note

+

For KeepAlive requests, only + the first request is counted towards this limit. In effect, it + changes the behavior to limit the number of connections per + child.

+
+ +
+
top
+

MaxSpareThreads Directive

+ + + + + + + +
Description:Maximum number of idle threads
Syntax:MaxSpareThreads number
Default:See usage for details
Context:server config
Status:MPM
Module:beos, mpm_netware, mpmt_os2, worker
+

Maximum number of idle threads. Different MPMs deal with this + directive differently.

+ +

For worker, + the default is MaxSpareThreads 250. + These MPMs deal with idle threads on a server-wide basis. If there + are too many idle threads in the server then child processes are + killed until the number of idle threads is less than this number.

+ +

For mpm_netware the default is + MaxSpareThreads 100. Since this MPM runs a + single-process, the spare thread count is also server-wide.

+ +

beos and mpmt_os2 work + similar to mpm_netware. The default for + beos is MaxSpareThreads 50. For + mpmt_os2 the default value is 10.

+ +

Restrictions

+

The range of the MaxSpareThreads value + is restricted. Apache will correct the given value automatically + according to the following rules:

+ +
+ +

See also

+ +
+
top
+

MinSpareThreads Directive

+ + + + + + + +
Description:Minimum number of idle threads available to handle request +spikes
Syntax:MinSpareThreads number
Default:See usage for details
Context:server config
Status:MPM
Module:beos, mpm_netware, mpmt_os2, worker
+

Minimum number of idle threads to handle request spikes. + Different MPMs deal with this directive + differently.

+ + +

worker + uses a default of MinSpareThreads + 75 and deal with idle threads on a server-wide basis. If + there aren't enough idle threads in the server then child + processes are created until the number of idle threads is greater + than number.

+ +

mpm_netware uses a default of + MinSpareThreads 10 and, since it is a single-process + MPM, tracks this on a server-wide bases.

+ +

beos and mpmt_os2 work + similar to mpm_netware. The default for + beos is MinSpareThreads 1. For + mpmt_os2 the default value is 5.

+ +

See also

+ +
+
top
+

PidFile Directive

+ + + + + + + +
Description:File where the server records the process ID +of the daemon
Syntax:PidFile filename
Default:PidFile logs/httpd.pid
Context:server config
Status:MPM
Module:beos, mpm_winnt, mpmt_os2, prefork, worker
+

The PidFile directive sets the file to + which the server records the process id of the daemon. If the + filename is not absolute then it is assumed to be relative to the + ServerRoot.

+ +

Example

+ PidFile /var/run/apache.pid +

+ +

It is often useful to be able to send the server a signal, + so that it closes and then re-opens its ErrorLog and TransferLog, and + re-reads its configuration files. This is done by sending a + SIGHUP (kill -1) signal to the process id listed in the + PidFile.

+ +

The PidFile is subject to the same + warnings about log file placement and security.

+ +

Note

+

As of Apache 2 it is recommended to use only the apachectl script for (re-)starting or stopping the server.

+
+ +
+
top
+

ReceiveBufferSize Directive

+ + + + + + + +
Description:TCP receive buffer size
Syntax:ReceiveBufferSize bytes
Default:ReceiveBufferSize 0
Context:server config
Status:MPM
Module:beos, mpm_netware, mpm_winnt, mpmt_os2, prefork, worker
+

The server will set the TCP receive buffer size to the number of + bytes specified.

+ +

If set to the value of 0, the server will use the + OS default.

+ +
+
top
+

ScoreBoardFile Directive

+ + + + + + + +
Description:Location of the file used to store coordination data for +the child processes
Syntax:ScoreBoardFile file-path
Default:ScoreBoardFile logs/apache_status
Context:server config
Status:MPM
Module:beos, mpm_winnt, prefork, worker
+

Apache uses a scoreboard to communicate between its parent + and child processes. Some architectures require a file to facilitate + this communication. If the file is left unspecified, Apache first + attempts to create the scoreboard entirely in memory (using anonymous + shared memory) and, failing that, will attempt to create the file on + disk (using file-based shared memory). Specifying this directive causes + Apache to always create the file on the disk.

+ +

Example

+ ScoreBoardFile /var/run/apache_status +

+ +

File-based shared memory is useful for third-party applications + that require direct access to the scoreboard.

+ +

If you use a ScoreBoardFile then + you may see improved speed by placing it on a RAM disk. But be + careful that you heed the same warnings about log file placement + and security.

+ +

See also

+ +
+
top
+

SendBufferSize Directive

+ + + + + + + +
Description:TCP buffer size
Syntax:SendBufferSize bytes
Default:SendBufferSize 0
Context:server config
Status:MPM
Module:beos, mpm_netware, mpm_winnt, mpmt_os2, prefork, worker
+

The server will set the TCP send buffer size to the number of bytes + specified. Very useful to increase past standard OS defaults on + high speed high latency (i.e., 100ms or so, such as + transcontinental fast pipes).

+ +

If set to the value of 0, the server will use the + OS default.

+ +
+
top
+

ServerLimit Directive

+ + + + + + + +
Description:Upper limit on configurable number of processes
Syntax:ServerLimit number
Default:See usage for details
Context:server config
Status:MPM
Module:prefork, worker
+

For the prefork MPM, this directive sets the + maximum configured value for MaxClients for the lifetime of the + Apache process. For the worker MPM, this directive + in combination with ThreadLimit sets + the maximum configured value for MaxClients for the lifetime of the + Apache process. Any attempts to change this directive during a + restart will be ignored, but MaxClients can be modified during + a restart.

+ +

Special care must be taken when using this directive. If + ServerLimit is set to a value much higher + than necessary, extra, unused shared memory will be allocated. If + both ServerLimit and MaxClients are set to values + higher than the system can handle, Apache may not start or the + system may become unstable.

+ +

With the prefork MPM, use this directive only + if you need to set MaxClients higher than 256 (default). + Do not set the value of this directive any higher than what you + might want to set MaxClients to.

+ +

With worker + use this directive only + if your MaxClients and + ThreadsPerChild + settings require more than 16 server processes (default). Do not set + the value of this directive any higher than the number of server + processes required by what you may want for MaxClients and ThreadsPerChild.

+ +

Note

+

There is a hard limit of ServerLimit 20000 compiled + into the server (for the prefork MPM 200000). This is + intended to avoid nasty effects caused by typos.

+
+ +

See also

+ +
+
top
+

StartServers Directive

+ + + + + + + +
Description:Number of child server processes created at startup
Syntax:StartServers number
Default:See usage for details
Context:server config
Status:MPM
Module:mpmt_os2, prefork, worker
+

The StartServers directive sets the + number of child server processes created on startup. As the number + of processes is dynamically controlled depending on the load, + there is usually little reason to adjust this parameter.

+ +

The default value differs from MPM to MPM. For + worker the default is StartServers 3. + For prefork defaults to 5 and for + mpmt_os2 to 2.

+ +
+
top
+

StartThreads Directive

+ + + + + + + +
Description:Number of threads created on startup
Syntax:StartThreads number
Default:See usage for details
Context:server config
Status:MPM
Module:beos, mpm_netware
+

Number of threads created on startup. As the + number of threads is dynamically controlled depending on the + load, there is usually little reason to adjust this + parameter.

+ +

For mpm_netware the default is + StartThreads 50 and, since there is only a single + process, this is the total number of threads created at startup to + serve requests.

+ +

For beos the default is StartThreads + 10. It also reflects the total number of threads created + at startup to serve requests.

+ +
+
top
+

ThreadLimit Directive

+ + + + + + + + +
Description:Sets the upper limit on the configurable number of threads +per child process
Syntax:ThreadLimit number
Default:See usage for details
Context:server config
Status:MPM
Module:mpm_winnt, worker
Compatibility:Available for mpm_winnt in Apache 2.0.41 +and later
+

This directive sets the maximum configured value for ThreadsPerChild for the lifetime + of the Apache process. Any attempts to change this directive + during a restart will be ignored, but ThreadsPerChild can be modified + during a restart up to the value of this directive.

+ +

Special care must be taken when using this directive. If + ThreadLimit is set to a value much higher + than ThreadsPerChild, + extra unused shared memory will be allocated. If both + ThreadLimit and ThreadsPerChild are set to values + higher than the system can handle, Apache may not start or the + system may become unstable. Do not set the value of this directive + any higher than your greatest predicted setting of ThreadsPerChild for the + current run of Apache.

+ +

The default value for ThreadLimit is + 1920 when used with mpm_winnt and + 64 when used with the others.

+ +

Note

+

There is a hard limit of ThreadLimit 20000 (or + ThreadLimit 15000 with mpm_winnt) + compiled into the server. This is intended to avoid nasty effects + caused by typos.

+
+ +
+
top
+

ThreadsPerChild Directive

+ + + + + + + +
Description:Number of threads created by each child process
Syntax:ThreadsPerChild number
Default:See usage for details
Context:server config
Status:MPM
Module:mpm_winnt, worker
+

This directive sets the number of threads created by each + child process. The child creates these threads at startup and + never creates more. If using an MPM like mpm_winnt, + where there is only one child process, this number should be high + enough to handle the entire load of the server. If using an MPM + like worker, where there are multiple child processes, + the total number of threads should be high enough to handle + the common load on the server.

+ +

The default value for ThreadsPerChild is + 64 when used with mpm_winnt and + 25 when used with the others.

+ +
+
top
+

ThreadStackSize Directive

+ + + + + + + + +
Description:The size in bytes of the stack used by threads handling +client connections
Syntax:ThreadStackSize size
Default:65536 on NetWare; varies on other operating systems
Context:server config
Status:MPM
Module:mpm_netware, mpm_winnt, worker
Compatibility:Available in Apache 2.1 and later
+

The ThreadStackSize directive sets the + size of the stack (for autodata) of threads which handle client + connections and call modules to help process those connections. + In most cases the operating system default for stack size is + reasonable, but there are some conditions where it may need to be + adjusted:

+ +
    +
  • On platforms with a relatively small default thread stack size + (e.g., HP-UX), Apache may crash when using some third-party modules + which use a relatively large amount of autodata storage. Those + same modules may have worked fine on other platforms where the + default thread stack size is larger. This type of crash is + resolved by setting ThreadStackSize to a + value higher than the operating system default. This type of + adjustment is necessary only if the provider of the third-party + module specifies that it is required, or if diagnosis of an Apache + crash indicates that the thread stack size was too small.
    • + +
  • On platforms where the default thread stack size is + significantly larger than necessary for the web server + configuration, a higher number of threads per child process + will be achievable if ThreadStackSize is + set to a value lower than the operating system default. This type + of adjustment should only be made in a test environment which allows + the full set of web server processing can be exercised, as there + may be infrequent requests which require more stack to process. + A change in the web server configuration can invalidate the + current ThreadStackSize setting.
    • +
+ +
+
top
+

User Directive

+ + + + + + + + +
Description:The userid under which the server will answer +requests
Syntax:User unix-userid
Default:User #-1
Context:server config
Status:MPM
Module:prefork, worker
Compatibility:Only valid in global server config since Apache +2.0
+

The User directive sets the user ID as + which the server will answer requests. In order to use this + directive, the server must be run initially as root. + If you start the server as a non-root user, it will fail to change + to the lesser privileged user, and will instead continue to run as + that original user. If you do start the server as root, + then it is normal for the parent process to remain running as root. + Unix-userid is one of:

+ +
+
A username
+
Refers to the given user by name.
+ +
# followed by a user number.
+
Refers to a user by its number.
+
+ +

The user should have no privileges that result in it being + able to access files that are not intended to be visible to the + outside world, and similarly, the user should not be able to + execute code that is not meant for HTTP requests. It is + recommended that you set up a new user and group specifically for + running the server. Some admins use user nobody, but + this is not always desirable, since the nobody user + can have other uses on the system.

+ +

Security

+

Don't set User (or Group) to root unless + you know exactly what you are doing, and what the dangers are.

+
+ +

Special note: Use of this directive in <VirtualHost> is no longer supported. To + configure your server for suexec use + SuexecUserGroup.

+ +

Note

+

Although the User directive is present + in the beos and mpmt_os2 MPMs, + it is actually a no-op there and only exists for compatibility + reasons.

+
+ +
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mpm_common.html.ja.euc-jp b/docs/manual/mod/mpm_common.html.ja.euc-jp new file mode 100644 index 00000000..93c174cb --- /dev/null +++ b/docs/manual/mod/mpm_common.html.ja.euc-jp @@ -0,0 +1,997 @@ + + + +mpm_common - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache MPM ¶¦Ḁ̈ǥ£¥ì¥¯¥Æ¥£¥Ö

+
+

Available Languages:  de  | + en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +
ÀâÌÀ:Æó¤Ä°Ê¾å¤Î¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM) +¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥³¥ì¥¯¥·¥ç¥ó
¥¹¥Æ¡¼¥¿¥¹:MPM
+
+ + +
top
+

AcceptMutex ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:Ê£¿ô¤Î»Ò¥×¥í¥»¥¹¤¬¥Í¥Ã¥È¥ï¡¼¥¯¥½¥±¥Ã¥È¤Ç¥ê¥¯¥¨¥¹¥È¤ò +accept ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤È¤­¤Ë¡¢Apache ¤¬¤½¤ì¤é¤Î»Ò¥×¥í¥»¥¹¤òľÎ󲽤¹¤ë¤¿¤á¤Ë +»È¤¦ÊýË¡
¹½Ê¸:AcceptMutex default|method
¥Ç¥Õ¥©¥ë¥È:AcceptMutex default
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, perchild, prefork, threadpool, worker
+

AcceptMutex ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥Í¥Ã¥È¥ï¡¼¥¯¥½¥±¥Ã¥È¤Î¥ê¥¯¥¨¥¹¥È¤ò accept ¤·¤è¤¦¤È¤·¤Æ¤¤¤ëÊ£¿ô¤Î»Ò¥×¥í¥»¥¹¤ò + Apache ¤¬Ä¾Î󲽤¹¤ë¤¿¤á¤Ë»È¤¦ÊýË¡¤òÀßÄꤷ¤Þ¤¹¡£ + Apache 2.0 °ÊÁ°¤Ï¡¢¤³¤Î¥á¥½¥Ã¥É¤Ï¥³¥ó¥Ñ¥¤¥ë»þ¤Ë¤Î¤ßÁªÂò¤Ç¤­¤Þ¤·¤¿¡£ + ºÇŬ¤ÊÊýË¡¤Ï¡¢¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤ä¥×¥é¥Ã¥È¥Û¡¼¥à¤ËÂ礭¤¯°Í¸¤·¤Þ¤¹¡£ + ¾ÜºÙ¤Ë´Ø¤·¤Æ¤Ï¡¢À­Ç½¤Î¥Á¥å¡¼¥Ë¥ó¥° + ¥É¥­¥å¥á¥ó¥È¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ Default + ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ì¤Ð¡¢¥³¥ó¥Ñ¥¤¥ë»þ¤ËÁªÂò¤µ¤ì¤¿¥Ç¥Õ¥©¥ë¥ÈÃͤ¬»È¤ï¤ì¤Þ¤¹¡£ + ¾¤Î»ÈÍѲÄǽ¤Ê¥á¥½¥Ã¥É¤Î°ìÍ÷¤Ï²¼¤Ë¤¢¤ê¤Þ¤¹¡£ + Á´¤Æ¤Î¥á¥½¥Ã¥É¤¬Á´¤Æ¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç»ÈÍѲÄǽ¤Ç¤¢¤ë¤ï¤±¤Ç¤Ï¤Ê¤¤¡¢ + ¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + »ÈÍѲÄǽ¤Ç¤Ê¤¤¥á¥½¥Ã¥É¤¬»ØÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢ + »ÈÍѲÄǽ¤Ê¥á¥½¥Ã¥É¤Î°ìÍ÷¤ò´Þ¤ó¤À¥á¥Ã¥»¡¼¥¸¤¬ + ¥¨¥é¡¼¥í¥°¤Ë½ÐÎϤµ¤ì¤Þ¤¹¡£

+ +
+
flock
+
LockFile + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÄêµÁ¤·¤¿¥Õ¥¡¥¤¥ë¤Î¥í¥Ã¥¯¤Ë¡¢ + flock(2) ¥·¥¹¥Æ¥à¥³¡¼¥ë¤ò»È¤¤¤Þ¤¹¡£
+ +
fcntl
+
LockFile + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÄêµÁ¤·¤¿¥Õ¥¡¥¤¥ë¤Î¥í¥Ã¥¯¤Ë¡¢ + fcntl(2) ¥·¥¹¥Æ¥à¥³¡¼¥ë¤ò»È¤¤¤Þ¤¹¡£
+ +
posixsem
+
ÇÓ¾½èÍý¤Î¼ÂÁõ¤Ë POSIX ¸ß´¹¥»¥Þ¥Õ¥©¤ò»ÈÍѤ·¤Þ¤¹
+ +
pthread
+
POSIX Threads (PThreads) µ¬³Ê¤Ç¼ÂÁõ¤µ¤ì¤Æ¤¤¤ë + POSIX ÇÓ¾½èÍý¤ò»È¤¤¤Þ¤¹¡£
+ +
sysvsem
+
ÇÓ¾½èÍý¤Î¼ÂÁõ¤Ë SySV ·Á¼°¤Î¥»¥Þ¥Õ¥©¤ò»È¤¤¤Þ¤¹¡£
+
+ +

¥³¥ó¥Ñ¥¤¥ë»þ¤Ë¥·¥¹¥Æ¥à¤Î¥Ç¥Õ¥©¥ë¥È¤ËÁª¤Ð¤ì¤¿¤â¤Î¤¬²¿¤«¤ò¸«¤¿¤¤¾ì¹ç¤Ï¡¢ + LogLevel ¤ò debug + ¤ËÀßÄꤹ¤ë¤È¤è¤¤¤Ç¤·¤ç¤¦¡£¥Ç¥Õ¥©¥ë¥È¤Î AcceptMutex + ¤¬ ErrorLog ¤Ë½ñ¤­¹þ¤Þ¤ì¤Þ¤¹¡£

+ +

·Ù¹ð

+

¤Û¤È¤ó¤É¤Î¥·¥¹¥Æ¥à¤Ë¤ª¤¤¤Æ¤Ï¡¢pthread ¥ª¥×¥·¥ç¥ó¤¬ + Áª¤Ð¤ì¤Æ¤¤¤ë¤È¡¢»Ò¥×¥í¥»¥¹¤¬ AcceptCntl mutex ¤ò + ÊÝ»ý¤·¤Æ¤¤¤ë¤È¤­¤Ë°Û¾ï½ªÎ»¤·¤¿¾ì¹ç¡¢¥µ¡¼¥Ð¤Ï¥ê¥¯¥¨¥¹¥È¤Ø¤Î±þÅú¤ò + Ää»ß¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¡£¤³¤ì¤¬È¯À¸¤·¤¿¾ì¹ç¤Ï¡¢¥µ¡¼¥Ð¤òÉüµì¤µ¤»¤ë¤¿¤á¤Ë¤Ï + ¼êÆ°¤ÇºÆµ¯Æ°¤µ¤»¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

Solaris ¤ÏÎã³°¤Ç¡¢Apache ¤â»ÈÍѤ·¤Æ¤¤¤ë¡¢»Ò¥×¥í¥»¥¹¤¬ mutex ¤ò + ÊÝ»ý¤·¤Æ°Û¾ï½ªÎ»¤·¤¿¸å¤Ë mutex ¤òÉüµì¤µ¤»¤ë¤¿¤á¤Îµ¡¹½¤òÄ󶡤ò¤·¤Æ¤¤¤Þ¤¹¡£

+

¸æ»ÈÍѤΥ·¥¹¥Æ¥à¤¬ pthread_mutexattr_setrobust_np() ´Ø¿ô¤ò + ¼ÂÁõ¤·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢pthread ¥ª¥×¥·¥ç¥ó¤ò°ÂÁ´¤Ë»ÈÍѤǤ­¤ë + ²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£

+
+ +
+
top
+

CoreDumpDirectory ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:Apache ¤¬¥³¥¢¥À¥ó¥×¤¹¤ëÁ°¤Ë°ÜÆ°¤ò»î¤ß¤ë¥Ç¥£¥ì¥¯¥È¥ê +
¹½Ê¸:CoreDumpDirectory directory
¥Ç¥Õ¥©¥ë¥È:¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤ÏÀâÌÀʸ¤òÆɤó¤Ç¤¯¤À¤µ¤¤
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_winnt, perchild, prefork, threadpool, worker
+

Apache ¤¬¥³¥¢¥À¥ó¥×¤¹¤ëÁ°¤Ë°ÜÆ°¤ò»î¤ß¤ë¥Ç¥£¥ì¥¯¥È¥ê¤òÀ©¸æ¤·¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï ServerRoot + ¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¹¤¬¡¢¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ï¥µ¡¼¥Ð¤Î¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¥æ¡¼¥¶¸¢¸Â¤Ç + ½ñ¤­¹þ¤ß²Äǽ¤Ç¤¢¤ë¤Ù¤­¤Ç¤Ï¤Ê¤¤¤Î¤Ç¡¢Ä̾ï¤Ï¥³¥¢¥À¥ó¥×¤Ï½ñ¤­¹þ¤Þ¤ì¤Þ¤»¤ó¡£ + ¥Ç¥Ð¥Ã¥°¤Î¤¿¤á¤Ë¥³¥¢¥À¥ó¥×¤¬É¬ÍפǤ¢¤ì¤Ð¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¾¤Î°ÌÃ֤˥³¥¢¥À¥ó¥×¤ò½ñ¤­½Ð¤¹¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£

+ +

Linux ¤Ç¤Î¥³¥¢¥À¥ó¥×

+

Apache ¤¬ root ¤È¤·¤Æµ¯Æ°¤µ¤ì¤Æ¡¢Ê̤Υ桼¥¶¤Î¸¢¸Â¤Ë°Ê¹ß¤·¤¿¾ì¹ç¤Ï + Linux ¤Î¥«¡¼¥Í¥ë¤Ï¥Ç¥£¥ì¥¯¥È¥ê¤¬¥×¥í¥»¥¹¤Î¸¢¸Â¤Ç½ñ¤­¹þ¤ß²Äǽ¤Ê¾ì¹ç¤Ç¤µ¤¨¤â + ¥³¥¢¥À¥ó¥×¤ò̵¸ú¤Ë¤·¤Þ¤¹¡£Apache (2.0.46 °Ê¹ß) ¤Ï + Linux 2.4 °Ê¹ß¤Ç¤Ï¥³¥¢¥À¥ó¥×¤ò¹Ô¤Ê¤¦¤è¤¦¤ËºÆ»ØÄꤷ¤Þ¤¹¤¬¡¢¤½¤ì¤Ï + CoreDumpDirectory ¤òÌÀ¼¨Åª¤ËÀßÄꤷ¤¿¤È¤­¤Ë + ¸Â¤ê¤Þ¤¹¡£

+
+ +
+
top
+

EnableExceptionHook ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥¯¥é¥Ã¥·¥å¤Î¸å¤ËÎã³°¥Ï¥ó¥É¥é¤ò¼Â¹Ô¤¹¤ë¥Õ¥Ã¥¯¤òÍ­¸ú¤Ë¤¹¤ë
¹½Ê¸:EnableExceptionHook On|Off
¥Ç¥Õ¥©¥ë¥È:EnableExceptionHook Off
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, perchild, prefork, threadpool, worker
¸ß´¹À­:2.0.49 °Ê¹ß
+

°ÂÁ´¾å¤ÎÍýͳ¤«¤é¡¢--enable-exception-hook configure + ¥ª¥×¥·¥ç¥ó¤òÍ­¸ú¤Ë¤·¤¿¾ì¹ç¤Ë¤Î¤ß¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÍøÍѤǤ­¤Þ¤¹¡£ + ³°Éô¥â¥¸¥å¡¼¥ë¤ò¥×¥é¥°¥¤¥ó¤·¤Æ¡¢»Ò¤¬¥¯¥é¥Ã¥·¥å¤·¤¿¸å¤Ë²¿¤«¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ê + ¥Õ¥Ã¥¯¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£

+ +

¤³¤Î¤è¤¦¤Ê³°Éô¥â¥¸¥å¡¼¥ë¤Ï¡¢´û¤ËÆó¤Ä¸ºß¤·¤Æ¤¤¤Æ¡¢ + mod_whatkilledus ¤È mod_backtrace + ¤¬¤³¤Î¥Õ¥Ã¥¯¤ò³èÍѤ·¤Þ¤¹¡£¤³¤ì¤é¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï Jeff Trawick + ¤µ¤ó¤Î EnableExceptionHook site ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
top
+

Group ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ëºÝ¤Ë½ê°¤¹¤ë¥°¥ë¡¼¥×
¹½Ê¸:Group unix-group
¥Ç¥Õ¥©¥ë¥È:Group #-1
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpmt_os2, perchild, prefork, threadpool, worker
¸ß´¹À­:Apache 2.0 °Ê¹ß¤Ç¡¢¥°¥í¡¼¥Ð¥ëÀßÄê¤Ç¤Î¤ßÍ­¸ú¤Ç¤¹¡£
+

Group ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¡¢ + ¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ëºÝ¤Ë½ê°¤·¤Æ¤ª¤¯¥°¥ë¡¼¥×¤òÀßÄꤷ¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢ + ¥µ¡¼¥Ð¤ÏºÇ½é¤Ë root ¸¢¸Â¤Çµ¯Æ°¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + Èó root ¥æ¡¼¥¶¤Ç¥µ¡¼¥Ð¤òµ¯Æ°¤·¤¿¾ì¹ç¤Ï¡¢»ØÄꤷ¤¿¥°¥ë¡¼¥×¤ËÊѲ½¤Ç¤­¤º¤Ë¡¢ + ·ë²ÌŪ¤Ëµ¯Æ°¤·¤¿¥æ¡¼¥¶¤Î°¤¹¤ë¥°¥ë¡¼¥×¤Ç¼Â¹Ô¤µ¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + unix-group ¤Ï¼¡¤Î¤¦¤Á¤Î¤¤¤º¤ì¤«¤Ç¤¹:

+ +
+
¥°¥ë¡¼¥×̾
+
¥°¥ë¡¼¥×¤ò̾Á°¤Ç»²¾È¤·¤Þ¤¹
+ +
# ¤Ë³¤¤¤Æ¥°¥ë¡¼¥×ÈÖ¹æ
+
¥°¥ë¡¼¥×¤ò¤òÈÖ¹æ¤Ç»²¾È¤·¤Þ¤¹¡£
+
+ +

Îã

+ Group www-group +

+ +

¥µ¡¼¥Ð¤ò¼Â¹Ô¤¹¤ë¤¿¤á¤ËÆÃÄê¤Î¿·¤·¤¤¥°¥ë¡¼¥×¤òÀßÄꤹ¤ë¤³¤È¤ò + ¤ªÁ¦¤á¤·¤Þ¤¹¡£nobody ¤ò»ÈÍѤ¹¤ë´ÉÍý¼Ô¤â¤¤¤Þ¤¹¤¬¡¢ + ²Äǽ¤Ç¤¢¤Ã¤¿¤ê˾¤Þ¤·¤¤Ìõ¤Ç¤Ïɬ¤º¤·¤â¤¢¤ê¤Þ¤»¤ó¡£

+ +

¥»¥­¥å¥ê¥Æ¥£

+

Àµ³Î¤Ë¤É¤ó¤Ê¤³¤È¤ò¤ä¤Ã¤Æ¤¤¤ë¤Î¤«¡¢¤½¤Î´í¸±À­¤òÃΤé¤Ê¤¤¤Ç¡¢ + Group (¤ä User) ¤ò + root ¤Ë ÀßÄꤷ¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£

+
+ +

Æõ­»ö¹à: ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + <VirtualHost> + ¤Ç»ÈÍѤ¹¤ë¤³¤È¤Ï¥µ¥Ý¡¼¥È¤µ¤ì¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿¡£Apache 2.0 ¤Ç + suexec ¤òÀßÄꤷ¤¿¤¤¾ì¹ç¤Ï¡¢ + SuexecUserGroup + ¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Ãí°Õ

+

Group ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + beos ¤È mpmt_os2 MPM + ¤Ë¤â¸ºß¤·¤Þ¤¹¤¬¡¢¼Â¼ÁŪ¤Ë̵¸ú¤Ç¡¢¸ß´¹À­¤Î¤¿¤á¤À¤±¤Ë¸ºß¤·¤Þ¤¹¡£

+
+ +
+
top
+

Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥µ¡¼¥Ð¤¬ listen ¤¹¤ëIP ¥¢¥É¥ì¥¹¤È¥Ý¡¼¥ÈÈÖ¹æ
¹½Ê¸:Listen [IP-address:]portnumber [protocol]
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_netware, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker, event
¸ß´¹À­:Apache 2.0 ¤«¤éɬ¿Ü¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡£protocol +°ú¿ô¤Ï 2.1.5 ¤ÇÄɲá£
+

Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache + ¤¬ÆÃÄê¤Î IP ¥¢¥É¥ì¥¹¤ä¥Ý¡¼¥ÈÈÖ¹æ¤À¤±¤ò listen ¤¹¤ë¤è¤¦¤Ë»ØÄꤷ¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Ç¤ÏÁ´¤Æ¤Î IP ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Î¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤·¤Þ¤¹¡£ + Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¸½ºß¤Ïɬ¿Ü¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤Ê¤ê¤Þ¤·¤¿¡£ + ¤â¤·ÀßÄê¥Õ¥¡¥¤¥ë¤Ë¤Ê¤±¤ì¤Ð¡¢¥µ¡¼¥Ð¤Ïµ¯Æ°¤Ë¼ºÇÔ¤·¤Þ¤¹¡£ + ¤³¤ì¤Ï°ÊÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤Î Apache ¤«¤éÊѹ¹¤Î¤¢¤Ã¤¿Éôʬ¤Ç¤¹¡£

+ +

Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï¡¢ÆÃÄê¤Î¥Ý¡¼¥È¤¢¤ë¤¤¤Ï + ¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ÎÁȤ߹ç¤ï¤»¤«¤éÆþ¤Ã¤Æ¤¯¤ë¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ + ±þÅú¤¹¤ë¤è¤¦¤Ë»ØÄꤷ¤Þ¤¹¡£ + ¤â¤·¥Ý¡¼¥ÈÈÖ¹æ¤À¤±¤¬»ØÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢¥µ¡¼¥Ð¤ÏÁ´¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Î + »ØÄꤵ¤ì¤¿¥Ý¡¼¥ÈÈÖ¹æ¤ËÂФ·¤Æ listen ¤·¤Þ¤¹¡£ + IP ¥¢¥É¥ì¥¹¤¬¥Ý¡¼¥È¤È¤È¤â¤Ë»ØÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢ + ¥µ¡¼¥Ð¤Ï»ØÄꤵ¤ì¤¿¥Ý¡¼¥È¤È¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤ËÂФ·¤Æ listen + ¤·¤Þ¤¹¡£

+ +

Ê£¿ô¤Î¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ËÂФ·¤Æ listen ¤¹¤ë¤è¤¦¤Ë¡¢ + Ê£¿ô¤Î Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤ÏÎóµó¤µ¤ì¤¿¥¢¥É¥ì¥¹¤È¥Ý¡¼¥ÈÁ´¤Æ¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ + ±þÅú¤·¤Þ¤¹¡£

+ +

Î㤨¤Ð¡¢¥µ¡¼¥Ð¤¬ 80 È֥ݡ¼¥È¤È 8000 È֥ݡ¼¥È¤ÎξÊý¤Î + ¥³¥Í¥¯¥·¥ç¥ó¤ò¼õ¤±Æþ¤ì¤ë¾ì¹ç¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

+ Listen 80
+ Listen 8000 +

+ +

Æó¤Ä¤ÎÆÃÄê¤Î¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤È¥Ý¡¼¥ÈÈֹ椫¤é¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò + ¼õ¤±Æþ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

+ Listen 192.170.2.1:80
+ Listen 192.170.2.5:8000 +

+ +

IPv6 ¥¢¥É¥ì¥¹¤Ï³Ñ³ç¸Ì¤Ç°Ï¤Þ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + Î㤨¤Ð¼¡¤ÎÎã¤Î¤è¤¦¤Ë¤Ç¤¹¡£

+ +

+ Listen [2001:db8::a00:20ff:fea7:ccea]:80 +

+ +

protocol ¥ª¥×¥·¥ç¥ó°ú¿ô¤ÏÄ̾ï¤ÎÀßÄê¤Ç¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£ + ̵»ØÄê¤Î¾ì¹ç¡¢443 È֥ݡ¼¥È¤Ë¤Ï https ¤¬¡¢Â¾¤Î¥Ý¡¼¥È¤Ë¤Ï + http ¤¬¥Ç¥Õ¥©¥ë¥ÈÃͤȤ·¤Æ»ÈÍѤµ¤ì¤Þ¤¹¡£ + protocol »ØÄê¤Ï¡¢¤É¤Î¥â¥¸¥å¡¼¥ë¤¬¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤¹¤ë¤«¤ò·èÄꤷ¡¢ + AcceptFilter + ¤Ë¤è¤ë¥×¥í¥È¥³¥ëÆÃÍ­¤ÎºÇŬ²½¤ò¹Ô¤¦¤è¤¦¤Ë¤·¤Þ¤¹¡£

+ +

Èóɸ½à¤Ê¥Ý¡¼¥È¤Ç±¿ÍѤ·¤Æ¤¤¤ëºÝ¤Ë¤Î¤ß protocol »ØÄ꤬ɬÍפˤʤê¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð https ¤Ê¥µ¥¤¥È¤ò 8443 È֥ݡ¼¥È¤Ç±¿ÍѤ·¤Æ¤¤¤ë¾ì¹ç :

+ +

+ Listen 192.170.2.1:8443 https +

+ +

¥¨¥é¡¼¾ò·ï

+ Ʊ°ì IP ¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ÎÁȤˡ¢Ê£¿ô¤Î Listen + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ØÄꤷ¤Æ¤·¤Þ¤¦¤È¡¢Address already in use + ¤È¤¤¤¦¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ +
+ + +

»²¾È

+ +
+
top
+

ListenBackLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:ÊÝα¾õÂ֤Υ³¥Í¥¯¥·¥ç¥ó¤Î¥­¥å¡¼¤ÎºÇÂçĹ
¹½Ê¸:ListenBacklog backlog
¥Ç¥Õ¥©¥ë¥È:ListenBacklog 511
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_netware, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
+

ÊÝα¾õÂ֤Υ³¥Í¥¯¥·¥ç¥ó¤Î¥­¥å¡¼¤ÎºÇÂçŤǤ¹¡£ + °ìÈÌŪ¤Ë¤ÏÄ´À°¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¤·¡¢Ä´À°¤Ï˾¤Þ¤·¤¯¤¢¤ê¤Þ¤»¤ó¡£ + ¤·¤«¤·¡¢TCP SYN ¥Õ¥é¥Ã¥É¥¢¥¿¥Ã¥¯¤Î¾õ¶·²¼¤Ë¤ª¤«¤ì¤ë¾ì¹ç¤Ë¡¢ + Áý¤ä¤·¤¿Êý¤¬Ë¾¤Þ¤·¤¤¥·¥¹¥Æ¥à¤â¤¢¤ê¤Þ¤¹¡£ + listen(2) ¥·¥¹¥Æ¥à¥³¡¼¥ë¤Î¥Ð¥Ã¥¯¥í¥°¥Ñ¥é¥á¡¼¥¿¤ò + ¤´Í÷²¼¤µ¤¤¡£

+ +

¤³¤ÎÃÍ¤Ï OS ¤Ë¤è¤ê¡¢¾®¤µ¤Ê¿ô¤ËÍÞ¤¨¤é¤ì¤Þ¤¹¡£ + ÃÍ¤Ï OS Ëè¤Ë°Û¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£¤Þ¤¿Â¿¤¯¤Î OS ¤Ç¤Ï¡¢ + ¥Ð¥Ã¥¯¥í¥°¤È¤·¤Æ»ØÄꤵ¤ì¤Æ¤¤¤ëÃͤÁ¤ç¤¦¤É¤Þ¤Ç»È¤Ã¤Æ¤¤¤ë¤ï¤±¤Ç¤Ï¤Ê¤¯¡¢ + ÀßÄꤵ¤ì¤Æ¤¤¤ëÃͤ˴ð¤Å¤¤¤Æ (Ä̾ï¤ÏÀßÄêÃͤè¤ê¤âÂ礭¤ÊÃͤò) + »È¤Ã¤Æ¤¤¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
+
top
+

LockFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¼õÉÕ¤òľÎ󲽤¹¤ë¤¿¤á¤Î¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ
¹½Ê¸:LockFile filename
¥Ç¥Õ¥©¥ë¥È:LockFile logs/accept.lock
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, perchild, prefork, threadpool, worker
+

AcceptMutex + ¤¬ fcntl ¤ä flock + ¤ËÀßÄꤵ¤ì¤Æ»ÈÍѤµ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ë¡¢»ÈÍѤµ¤ì¤ë¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Ø¤Î¥Ñ¥¹¤ò + LockFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤷ¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÄ̾ï¤Ï¤½¤Î¤Þ¤Þ¤Ë¤·¤Æ¤ª¤­¤Þ¤¹¡£ + ¼ç¤Ë logs ¥Ç¥£¥ì¥¯¥È¥ê¤¬ NFS + ¤Ç¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ê¤É¤ËÃͤòÊѤ¨¤Þ¤¹¡£ + ¤Ê¤¼¤Ê¤é¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Ï¥í¡¼¥«¥ë¥Ç¥£¥¹¥¯¤Ë + Êݸ¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤é¤Ç¤¹¡£ + ¥á¥¤¥ó¥µ¡¼¥Ð¥×¥í¥»¥¹¤Î PID ¤¬¥Õ¥¡¥¤¥ë̾¤Ë¼«Æ°Åª¤ËÉղ䵤ì¤Þ¤¹¡£

+ +

¥»¥­¥å¥ê¥Æ¥£

+

/var/tmp + ¤È¤¤¤Ã¤¿¡¢Ã¯¤Ç¤â½ñ¤­¹þ¤á¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥Õ¥¡¥¤¥ë¤ò + ÃÖ¤«¤Ê¤¤Êý¤¬¤è¤¤¤Ç¤¹¡£¤Ê¤¼¤Ê¤é¡¢¥µ¡¼¥Ð¤¬µ¯Æ°»þ¤ËºîÀ®¤¹¤ë + ¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤ÎºîÀ®¼«ÂΤò˸³²¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢ + ï¤Ç¤â¥µ¡¼¥Ó¥¹µñÈÝ¥¢¥¿¥Ã¥¯¤ò°ú¤­µ¯¤³¤¹¤³¤È¤¬¤Ç¤­¤ë¤«¤é¤Ç¤¹¡£

+
+ +

»²¾È

+ +
+
top
+

MaxClients ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¤¿¤á¤ËºîÀ®¤µ¤ì¤ë +»Ò¥×¥í¥»¥¹¤ÎºÇÂç¸Ä¿ô
¹½Ê¸:MaxClients number
¥Ç¥Õ¥©¥ë¥È:¾ÜºÙ¤Ï»ÈÍÑË¡¤ò¤´Í÷²¼¤µ¤¤¡£
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, prefork, threadpool, worker
+

MaxClients ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ±þÅú¤¹¤ë¤³¤È¤Î¤Ç¤­¤ëƱ»þ¥ê¥¯¥¨¥¹¥È¿ô¤òÀßÄꤷ¤Þ¤¹¡£ + MaxClients À©¸Â¿ô¤ò±Û¤¨¤ë¥³¥Í¥¯¥·¥ç¥ó¤ÏÄ̾ + ListenBacklog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤷ¤¿¿ô¤Þ¤Ç¥­¥å¡¼¤ËÆþ¤ê¤Þ¤¹¡£ + ¾¤Î¥ê¥¯¥¨¥¹¥È¤ÎºÇ¸å¤Þ¤Ç㤷¤Æ»Ò¥×¥í¥»¥¹¤¬¶õ¤¯¤È¡¢ + ¼¡¤Î¥³¥Í¥¯¥·¥ç¥ó¤Ë±þÅú¤·¤Þ¤¹¡£

+ +

¥¹¥ì¥Ã¥É¤òÍѤ¤¤Ê¤¤¥µ¡¼¥Ð (¤¹¤Ê¤ï¤Á prefork) + ¤Ç¤Ï¡¢MaxClients + ¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¤¿¤á¤Ëµ¯Æ°¤µ¤ì¤ë + »Ò¥×¥í¥»¥¹¤ÎºÇÂç¿ô¤È¤Ê¤ê¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 256 ¤Ç¡¢¤³¤ì¤òÁý²Ã¤µ¤»¤¿¤¤¾ì¹ç¤Ï¡¢ + ServerLimit + ¤ÎÃͤâÁý²Ã¤µ¤»¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

¥¹¥ì¥Ã¥É¤òÍѤ¤¤ë¥µ¡¼¥Ð¤ä¡¢¥Ï¥¤¥Ö¥ê¥Ã¥É¥µ¡¼¥Ð (¤¹¤Ê¤ï¤Á + beos worker) + ¤Ç¤Ï¡¢MaxClients + ¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ë±þÅú¤Ç¤­¤ë¥¹¥ì¥Ã¥É¤ÎÁí¿ô¤òÀ©¸Â¤·¤Þ¤¹¡£ + beos ¤Ç¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 50 ¤Ç¤¹¡£ + ¥Ï¥¤¥Ö¥ê¥Ã¥É MPM ¤Ç¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 16 + ServerLimit + ¤Î 25 ÇÜ (ThreadsPerChild) ¤Ç¤¹¡£ + MaxClients + ¤ò 16 ¥×¥í¥»¥¹°Ê¾åɬÍפÊÃͤޤÇÁý²Ã¤µ¤»¤¿¤¤¾ì¹ç¤Ï¡¢ + ServerLimit + ¤âÁý²Ã¤µ¤»¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +
+
top
+

MaxMemFree ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:free() ¤¬¸Æ¤Ð¤ì¤Ê¤¤¸Â¤ê¡¢ +¼ç¥á¥â¥ê¥¢¥í¥±¡¼¥¿¤¬ÊÝ»ý¤·Â³¤±¤é¤ì¤ë¥á¥â¥ê¤ÎºÇÂçÎÌ
¹½Ê¸:MaxMemFree KBytes
¥Ç¥Õ¥©¥ë¥È:MaxMemFree 0
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_netware, prefork, threadpool, worker, mpm_winnt
+

MaxMemFree ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + free() ¤¬¸Æ¤Ð¤ì¤Ê¤¤¸Â¤ê¡¢ + ¼ç¥¢¥í¥±¡¼¥¿¤¬ÊÝ»ý¤Ç¤­¤ë¶õ¤Î¥á¥â¥ê¤ÎºÇÂçÃͤò¥­¥í¥Ð¥¤¥Èñ°Ì¤ÇÀßÄꤷ¤Þ¤¹¡£ + ÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤«¡¢Îí¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¤È¤­¤Ï¡¢ÌµÀ©¸Â¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +
+
top
+

MaxRequestsPerChild ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¸Ä¡¹¤Î»Ò¥µ¡¼¥Ð¤¬²ÔƯÃæ¤Ë°·¤¦¥ê¥¯¥¨¥¹¥È¿ô¤Î¾å¸Â
¹½Ê¸:MaxRequestsPerChild number
¥Ç¥Õ¥©¥ë¥È:MaxRequestsPerChild 10000
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, mpm_netware, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
+

MaxRequestsPerChild ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¸Ä¡¹¤Î»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤¬°·¤¦¤³¤È¤Î¤Ç¤­¤ë¥ê¥¯¥¨¥¹¥È¤ÎÀ©¸Â¿ô¤ò + ÀßÄꤷ¤Þ¤¹¡£MaxRequestsPerChild + ¸Ä¤Î¥ê¥¯¥¨¥¹¥È¤Î¸å¤Ë¡¢»Ò¥×¥í¥»¥¹¤Ï½ªÎ»¤·¤Þ¤¹¡£ + MaxRequestsPerChild ¤¬ 0 + ¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢¥×¥í¥»¥¹¤Ï´ü¸ÂÀÚ¤ì¤Ë¤è¤ê½ªÎ»¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +

¤½¤Î¾¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ

+

mpm_netware ¤È mpm_winnt + ¤Ç¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 0 ¤Ç¤¹¡£

+
+ +

MaxRequestsPerChild + ¤òÈó¥¼¥í¤ËÀ©¸Â¤¹¤ë¤³¤È¤Ë¤Ï¡¢Æó¤Ä¤ÎÍøÅÀ¤¬¤¢¤ê¤Þ¤¹:

+ +
    +
  • (¶öȯŪ¤Ê) ¥á¥â¥ê¡¼¥ê¡¼¥¯¤¬µ¯¤³¤Ã¤¿¾ì¹ç¤Ë + ¥×¥í¥»¥¹¤¬¾ÃÈñ¤¹¤ë¥á¥â¥ê¤ÎÁíÎ̤òÀ©¸Â¤Ç¤­¤ë
    • + +
  • ¥×¥í¥»¥¹¤ËÍ­¸Â¤Î¥é¥¤¥Õ¥¿¥¤¥à¤òÀßÄꤹ¤ë¤³¤È¤Ç¡¢ + ¥µ¡¼¥ÐÉé²Ù¤¬²¼¤¬¤Ã¤¿»þ¤Ë¥×¥í¥»¥¹¿ô¤ò¾¯¤Ê¤¯¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë
    • +
+ +

Ãí

+

KeepAlive ¥ê¥¯¥¨¥¹¥È¤Î¾ì¹ç¤Ï¡¢ + °ì¤ÄÌܤΥꥯ¥¨¥¹¥È¤À¤±¤¬¤³¤ÎÀ©¸Â¤Ë³ºÅö¤·¤Þ¤¹¡£ + ¼Â¸úŪ¤Ë¤Ï¡¢°ì¤Ä¤Î»Ò¥×¥í¥»¥¹¤¢¤¿¤ê¤Î¥³¥Í¥¯¥·¥ç¥ó¿ô¤ò + À©¸Â¤¹¤ë¤è¤¦¤ËµóÆ°¤¬ÊѲ½¤·¤Þ¤¹¡£

+
+ +
+
top
+

MaxSpareThreads ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¤ÎºÇÂç¿ô
¹½Ê¸:MaxSpareThreads number
¥Ç¥Õ¥©¥ë¥È:¾ÜºÙ¤Ï»ÈÍÑË¡¤ò¤´Í÷²¼¤µ¤¤¡£
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_netware, mpmt_os2, perchild, threadpool, worker
+

¥¢¥¤¥É¥ë¤Ê¥¹¥ì¥Ã¥É¤ÎºÇÂç¿ô¤Ç¤¹¡£°Û¤Ê¤ë MPM ¤Ç¤Ï¤½¤ì¤¾¤ì¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï°Û¤Ê¤ë¼è¤ê°·¤ï¤ìÊý¤ò¤µ¤ì¤Þ¤¹¡£

+ +

perchild ¤Ç¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ï MaxSpareThreads 10 ¤Ç¤¹¡£ + ¤³¤Î MPM ¤Ï¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¿ô¤ò¡¢¤½¤ì¤¾¤ì¤Î»Ò¥×¥í¥»¥¹¤´¤È¤Ë´Æ»ë¤·¤Þ¤¹¡£ + »Ò¥×¥í¥»¥¹¤Ë¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¤¬Â¿¤¹¤®¤ë¾ì¹ç¤Ï¡¢ + ¥µ¡¼¥Ð¤Ï¤½¤Î»Ò¥×¥í¥»¥¹¤Ë´Þ¤Þ¤ì¤ë¥¹¥ì¥Ã¥É¤ò½ªÎ»¤·»Ï¤á¤Þ¤¹¡£

+ +

worker, leader, + threadpool ¤Ç¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ï MaxSpareThreads 250 ¤Ç¤¹¡£ + ¤³¤Î MPM ¤Ï¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¿ô¤ò¥µ¡¼¥ÐÁ´ÂΤǴƻ뤷¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤Ç¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¿ô¤¬Â¿¤¹¤®¤ë¾ì¹ç¤Ï¡¢ + ¤³¤Î¿ô»ú¤è¤ê¤â¾¯¤Ê¤¤¿ô¤Ë¤Ê¤ë¤Þ¤Ç»Ò¥×¥í¥»¥¹¤ò½ªÎ»¤·¤Þ¤¹¡£

+ +

mpm_netware ¤Ç¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ï MaxSpareThreads 100 ¤Ç¤¹¡£ + ¤³¤Î MPM ¤Ï¥·¥ó¥°¥ë¥×¥í¥»¥¹¤Ç¼Â¹Ô¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢ + ¥¹¥Ú¥¢¥¹¥ì¥Ã¥É¿ô¤â¥µ¡¼¥ÐÁ´ÂΤǴªÄꤷ¤Þ¤¹¡£

+ +

beos ¤È mpmt_os2 ¤Ï + mpm_netware ¤È»÷¤¿µóÆ°¤ò¤·¤Þ¤¹¡£ + beos ¤Ç¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï MaxSpareThreads 50 + ¤Ç¤¹¡£mpmt_os2 ¤Ç¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 10 + ¤Ç¤¹¡£

+ +

À©¸Â»ö¹à

+

MaxSpareThreads ¤Î¼è¤ëÃͤˤÏÀ©¸Â¤¬¤¢¤ê¤Þ¤¹¡£ + Apache ¤Ï¼¡¤Îµ¬Â§¤Ë½¾¤Ã¤Æ¼«Æ°Åª¤ËÊäÀµ¤·¤Þ¤¹¡£

+ +
+ +

»²¾È

+ +
+
top
+

MinSpareThreads ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¤³¤È¤Î¤Ç¤­¤ë +¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¿ô¤ÎºÇ¾®¿ô
¹½Ê¸:MinSpareThreads number
¥Ç¥Õ¥©¥ë¥È:¾ÜºÙ¤Ï»ÈÍÑÊýË¡¤ò¤´Í÷²¼¤µ¤¤¡£
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_netware, mpmt_os2, perchild, threadpool, worker
+

¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¥¹¥ì¥Ã¥É¿ô¤ÎºÇ¾®ÃͤǤ¹¡£ + °Û¤Ê¤ë MPM ¤Ç¤Ï¤½¤ì¤¾¤ì¡¢ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï°Û¤Ê¤ë¼è¤ê°·¤ï¤ìÊý¤ò¤·¤Þ¤¹¡£

+ +

perchild ¤Ç¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ï MinSpareThreads 5 ¤Ç¡¢ + ¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¿ô¤ò»Ò¥×¥í¥»¥¹Ëè¤Ë´Æ»ë¤·¤Þ¤¹¡£ + ¤â¤·»Ò¥×¥í¥»¥¹¤Ë½½Ê¬¤Ê¿ô¤Î¥¹¥ì¥Ã¥É¤¬¤Ê¤±¤ì¤Ð¡¢ + ¥µ¡¼¥Ð¤Ï¤½¤Î»Ò¥×¥í¥»¥¹¤Ë¿·¤·¤¤¥¹¥ì¥Ã¥É¤òºî¤ê»Ï¤á¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢NumServers + ¤ò 10 ¤Ë¡¢MinSpareThreads ¤ò + 5 ¤Ë¤·¤¿¾ì¹ç¤Ï¡¢ºÇ¾®¤Ç¤â 50 ¤Î¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¤¬ + ¥·¥¹¥Æ¥à¾å¤Ë¤¢¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

worker, leader, + threadpool ¤Ç¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ï MinSpareThreads 75 ¤Ç¡¢ + ¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¿ô¤ò¥µ¡¼¥ÐÁ´ÂΤǴƻ뤷¤Þ¤¹¡£ + ¤â¤·¥µ¡¼¥Ð¤Ë½½Ê¬¤Ê¿ô¤Î¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¤¬¤Ê¤±¤ì¤Ð¡¢ + ¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¿ô¤¬¤³¤Î¿ô¤è¤ê¤âÂ礭¤¯¤Ê¤ë¤Þ¤Ç + ¿·¤·¤¤»Ò¥×¥í¥»¥¹¤¬À¸À®¤µ¤ì¤Þ¤¹¡£

+ +

mpm_netware ¤Ç¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Ï MinSpareThreads 10 ¤Ç¡¢ + ¥·¥ó¥°¥ë¥×¥í¥»¥¹ MPM ¤Ç¤¹¤Î¤Ç¡¢¥µ¡¼¥ÐÁ´ÂΤǴÉÍý¤µ¤ì¤Þ¤¹¡£

+ +

beos ¤È mpmt_os2 ¤Ï¡¢ + mpm_netware¤Ë¤è¤¯»÷¤Æ¤¤¤Þ¤¹¡£ + beos ¤Ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ï MinSpareThreads 1 + ¤Ç¤¹¡£mpmt_os2 ¤Ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ï + 5 ¤Ç¤¹¡£

+ +

»²¾È

+ +
+
top
+

PidFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥Ç¡¼¥â¥ó¤Î¥×¥í¥»¥¹ ID +¤ò¥µ¡¼¥Ð¤¬µ­Ï¿¤¹¤ë¤¿¤á¤Î¥Õ¥¡¥¤¥ë
¹½Ê¸:PidFile filename
¥Ç¥Õ¥©¥ë¥È:PidFile logs/httpd.pid
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
+

PidFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¡¢ + ¥Ç¡¼¥â¥ó¤Î¥×¥í¥»¥¹ ID ¤ò¥µ¡¼¥Ð¤¬µ­Ï¿¤¹¤ë¥Õ¥¡¥¤¥ë¤òÀßÄꤷ¤Þ¤¹¡£ + ¥Õ¥¡¥¤¥ë̾¤¬ÀäÂХѥ¹¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢ + ServerRoot + ¤«¤é¤ÎÁêÂÐŪ¤Ê¤â¤Î¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£

+ +

Îã

+ PidFile /var/run/apache.pid +

+ +

¥µ¡¼¥Ð¤¬ ErrorLog + ¤ä TransferLog + ¤òÊĤ¸¤Æ³«¤­Ä¾¤·¤¿¤ê¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤ò + ºÆÆɹþ¤·¤¿¤ê¤µ¤»¤ë¤¿¤á¤Ë¡¢¥µ¡¼¥Ð¤Ë¥·¥°¥Ê¥ë¤òÁ÷¤ë¤³¤È¤¬¤Ç¤­¤ë¤È + ÊØÍø¤Ê¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï SIGHUP (kill -1) ¥·¥°¥Ê¥ë¤ò PidFile + ¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¥×¥í¥»¥¹ ID ¤ËÁ÷¤ë¤³¤È¤Ç¤Ç¤­¤Þ¤¹¡£

+ +

PidFile ¤Ë¤Ï¡¢¥í¥°¥Õ¥¡¥¤¥ë¤ÎÀßÃÖ°ÌÃÖ¤ä + ¥»¥­¥å¥ê¥Æ¥£ + ¤ÈÁ´¤¯Æ±¤¸Ãí°ÕÅÀ¤¬¤¢¤ê¤Þ¤¹¡£

+ +

Ãí°Õ

+

Apache 2 ¤Ç¤Ï¡¢ + apachectl + ¥¹¥¯¥ê¥×¥È¤Î¤ß¤ò»ÈÍѤ·¤Æ¥µ¡¼¥Ð¤Î (ºÆ) µ¯Æ°¤äÄä»ß¤ò + ¹Ô¤Ê¤¦¤³¤È¤ò¿ä¾©¤·¤Æ¤¤¤Þ¤¹¡£

+
+ +
+
top
+

ScoreBoardFile ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:»Ò¥×¥í¥»¥¹¤ÈÏ¢·È¤¹¤ë¤¿¤á¤Î¥Ç¡¼¥¿¤òÊݸ¤¹¤ë +¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ
¹½Ê¸:ScoreBoardFile file-path
¥Ç¥Õ¥©¥ë¥È:ScoreBoardFile logs/apache_status
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_winnt, perchild, prefork, threadpool, worker
+

Apache ¤Ï¿Æ¥×¥í¥»¥¹¤È»Ò¥×¥í¥»¥¹´Ö¤ÎÄÌ¿®¤Ë¥¹¥³¥¢¥Ü¡¼¥É¤òÍѤ¤¤Þ¤¹¡£ + ¤³¤ÎÄÌ¿®µ¡Ç½¤Ë¥Õ¥¡¥¤¥ë¤òɬÍפȤ¹¤ë¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤â¤¢¤ê¤Þ¤¹¡£ + ¥Õ¥¡¥¤¥ë¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢Apache ¤Ï¤Þ¤º¥á¥â¥ê¾å + (ƿ̾¶¦Í­¥á¥â¥ê) ¤Ë¥¹¥³¥¢¥Ü¡¼¥É¤òºî¤í¤¦¤È¤·¡¢¤½¤ì¤¬¼ºÇÔ¤¹¤ë¤È + ¥Ç¥£¥¹¥¯¾å¤Ë¥Õ¥¡¥¤¥ë (¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¤Î¶¦Í­¥á¥â¥ê) ¤òºî¤í¤¦¤È¤·¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ØÄꤹ¤ë¤È¡¢Apache + ¤Ïɬ¤º¥Ç¥£¥¹¥¯¤Ë¥Õ¥¡¥¤¥ë¤òÀ¸À®¤·¤Þ¤¹¡£

+ +

Îã

+ ScoreBoardFile /var/run/apache_status +

+ +

¥Õ¥¡¥¤¥ë¥Ù¡¼¥¹¤Î¶¦Í­¥á¥â¥ê¤Ï¡¢¥µ¡¼¥É¥Ñ¡¼¥Æ¥£¡¼À½¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ç + ¥¹¥³¥¢¥Ü¡¼¥É¤ËľÀÜ¥¢¥¯¥»¥¹¤¹¤ëɬÍפ¬¤¢¤ë¾ì¹ç¤ËÌò¤ËΩ¤Á¤Þ¤¹¡£

+ +

ScoreBoardFile ¤ò»È¤¦¾ì¹ç¡¢ + RAM ¥Ç¥£¥¹¥¯¾å¤ËÃÖ¤¯¤È¥¹¥Ô¡¼¥É¤¬¸þ¾å¤¹¤ë¤Ç¤·¤ç¤¦¡£ + ¤·¤«¤·¡¢¥í¥°¥Õ¥¡¥¤¥ë¤ÎÀßÃÖ°ÌÃÖ¤ä + ¥»¥­¥å¥ê¥Æ¥£ + ¤ÈƱÍͤÎÃí°ÕÅÀ¤¬¤¢¤ë¤Î¤Ç¡¢Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

»²¾È

+ +
+
top
+

SendBufferSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:TCP ¥Ð¥Ã¥Õ¥¡¥µ¥¤¥º
¹½Ê¸:SendBufferSize bytes
¥Ç¥Õ¥©¥ë¥È:SendBufferSize 0
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, leader, mpm_netware, mpm_winnt, mpmt_os2, perchild, prefork, threadpool, worker
+

¥µ¡¼¥Ð¤Ï TCP ¥Ð¥Ã¥Õ¥¡¥µ¥¤¥º¤ò»ØÄꤵ¤ì¤¿¥Ð¥¤¥È¿ô¤ËÀßÄꤷ¤Þ¤¹¡£ + ¹â®¤Ç¹â¥ì¥¤¥Æ¥ó¥·¤Ê´Ä¶­¤Ç + (Îã 100ms ÄøÅÙ¡¢ÂçΦ²£Ãǹâ®ÄÌ¿®Ï©¤Ê¤É) + ¸Å¤¤°ìÈÌŪ¤Ê OS ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤòÁý¤ä¤¹¤Î¤ËÈó¾ï¤ËÊØÍø¤Ç¤¹¡£

+ +

0¤Ë¤·¤¿¾ì¹ç¡¢OS ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤ¬»ÈÍѤµ¤ì¤Þ¤¹¡£

+ +
+
top
+

ServerLimit ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:ÀßÄê²Äǽ¤Ê¥µ¡¼¥Ð¥×¥í¥»¥¹¿ô¤Î¾å¸Â
¹½Ê¸:ServerLimit number
¥Ç¥Õ¥©¥ë¥È:¾ÜºÙ¤Ï»ÈÍÑË¡¤ò»²¾È
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, perchild, prefork, threadpool, worker
+

prefork MPM ¤Î¾ì¹ç¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + Apache ¥×¥í¥»¥¹²ÔƯÃæ¤Ë¤ª¤±¤ë + MaxClients + ¤ËÀßÄê²Äǽ¤Ê¾å¸ÂÃͤòÀßÄꤹ¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹ + (ÌõÃí: prefork ¤Î¾ì¹ç¤ÏƱ»þ¥¯¥é¥¤¥¢¥ó¥È¿ô = ¥µ¡¼¥Ð¥×¥í¥»¥¹¿ô¤Ê¤Î¤Ç) ¡£ + worker MPM ¤Î¾ì¹ç¤Ë¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ThreadLimit + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÈÁȤ߹ç¤ï¤»¤Æ¡¢ + Apache ¥×¥í¥»¥¹²ÔƯÃæ¤Ë¤ª¤±¤ë + MaxClients + ¤ËÀßÄê²Äǽ¤Ê¾å¸ÂÃͤòÀßÄꤹ¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ºÆµ¯Æ°Ãæ¤Ë¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÊѹ¹¤·¤Æ¤â̵»ë¤µ¤ì¤Þ¤¹¤¬¡¢ + MaxClients + ¤ÏºÆµ¯Æ°Ãæ¤Ë½¤Àµ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ëºÝ¤ÏÆäËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ServerLimit ¤¬É¬Íװʾå¤ËÂ礭¤ÊÃÍ¤Ë + ÀßÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢Í¾·×¤Ê̤»ÈÍѶ¦Í­¥á¥â¥ê¤¬³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£ + ServerLimit ¤È + MaxClients + ¤¬¥·¥¹¥Æ¥à¤Î°·¤¨¤ëÈϰϤò±Û¤¨¤¿ÀßÄêÃͤˤʤäƤ¤¤ë¤È¡¢ + Apache ¤Ïµ¯Æ°¤·¤Ê¤¤¤«¡¢µ¯Æ°¤·¤Æ¤âÉÔ°ÂÄê¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£

+ +

prefork MPM ¤Ç¤Ï¡¢ + MaxClients + ¤ò 256 (¥Ç¥Õ¥©¥ë¥È) ¤è¤ê¤âÂ礭¤ÊÃͤËÀßÄꤹ¤ëɬÍפ¬¤¢¤ë»þ¤Ë¤À¤±»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£ + ´õ˾¤Î MaxClients + ¿ô¤È¤¯¤é¤Ù¤Æ¡¢É¬Íװʾå¤ËÂ礭¤ÊÃͤò»ØÄꤹ¤ë¤³¤È¤ÏÈò¤±¤Æ¤¯¤À¤µ¤¤¡£

+ +

worker, leader, + threadpool MPM ¤Ç¤Ï¡¢ + MaxClients ¤È + ThreadsPerChild + ¤ÎÀßÄê¤Ç 16 ¥µ¡¼¥Ð¥×¥í¥»¥¹ (¥Ç¥Õ¥©¥ë¥È) + °Ê¾åɬÍפˤʤë¾ì¹ç¤Ë¤Î¤ß»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£´õ˾¤Î + MaxClients ¤È + ThreadsPerChild + ¤È¤¯¤é¤Ù¤Æ¡¢É¬ÍפȤʤ륵¡¼¥Ð¥×¥í¥»¥¹¿ô°Ê¾å¤ËÂ礭¤ÊÃͤò + ÀßÄꤹ¤ë¤³¤È¤ÏÈò¤±¤Æ¤¯¤À¤µ¤¤¡£

+ +

perchild MPM ¤Ç¤Ï¡¢ + NumServers ¤ò 8 (¥Ç¥Õ¥©¥ë¥È) + ¤è¤í¤¤¤âÂ礭¤ÊÃͤËÀßÄꤹ¤ëɬÍפ¬¤¢¤ë¤È¤­¤Ë¤Î¤ß»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Ãí°Õ

+

ServerLimit 20000 ¤È¤¤¤¦À©¸ÂÉÕ¤­¤Ç¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤Þ¤¹ + (prefork MPM ¤Ç¤Ï 200000) ¡£ + ¤³¤ì¤Ï¥¹¥Ú¥ë¥ß¥¹¤Ë¤è¤Ã¤Æ¸í¤Ã¤Æ¹ó¤¤¾õ¶·¤Ë¤Ê¤ë¤Î¤ò¡¢ + ²óÈò¤¹¤ë¤¿¤á¤Î½èÃ֤Ǥ¹¡£

+
+ +

»²¾È

+ +
+
top
+

StartServers ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:µ¯Æ°»þ¤ËÀ¸À®¤µ¤ì¤ë»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤Î¿ô
¹½Ê¸:StartServers number
¥Ç¥Õ¥©¥ë¥È:¾ÜºÙ¤Ï»ÈÍÑÊýË¡¤ò»²¾È
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, mpmt_os2, prefork, threadpool, worker
+

StartServers ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + µ¯Æ°»þ¤ËÀ¸À®¤µ¤ì¤ë»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤Î¿ô¤òÀßÄꤷ¤Þ¤¹¡£ + ¥×¥í¥»¥¹¿ô¤ÏÉé²Ù¤Ë±þ¤¸¤ÆưŪ¤ËÀ©¸æ¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢ + Ä̾ï¤Ï¤³¤ÎÃͤòÄ´À°¤¹¤ëÍýͳ¤Ï¤¢¤Þ¤ê¤Ê¤¤¤Ç¤·¤ç¤¦¡£

+ +

¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï MPM ¤´¤È¤Ë°Û¤Ê¤ê¤Þ¤¹¡£ + leader, threadpool, + worker ¤Ï StartServers 3 ¤Ç¤¹¡£ + prefork ¤Ï 5 ¤Ç¡¢ + mpmt_os2 ¤Ï 2 ¤Ç¤¹¡£

+ +
+
top
+

StartThreads ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:µ¯Æ°»þ¤ËÀ¸À®¤µ¤ì¤ë¥¹¥ì¥Ã¥É¤Î¿ô
¹½Ê¸:StartThreads number
¥Ç¥Õ¥©¥ë¥È:¾ÜºÙ¤Ï»ÈÍÑÊýË¡¤ò»²¾È
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:beos, mpm_netware, perchild
+

µ¯Æ°»þ¤ËÀ¸À®¤µ¤ì¤ë¥¹¥ì¥Ã¥É¤Î¿ô¤Ç¤¹¡£ + ¥¹¥ì¥Ã¥É¿ô¤ÏÉé²Ù¤Ë±þ¤¸¤ÆưŪ¤ËÀ©¸æ¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢ + Ä̾ï¤Ï¤³¤ÎÃͤòÄ´À°¤¹¤ëÍýͳ¤Ï¤¢¤Þ¤ê¤Ê¤¤¤Ç¤·¤ç¤¦¡£

+ +

perchild ¤Ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ï + StartThreads 5 ¤Ç¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïµ¯Æ°»þ¤Ë + ¥×¥í¥»¥¹Ëè¤Î¥¹¥ì¥Ã¥É¿ô¤òÄÉÀפ·¤Þ¤¹¡£

+ +

mpm_netware ¤Ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ï + StartThreads 50 ¤Ç¡¢ + ¤³¤Î¾ì¹ç¥×¥í¥»¥¹¤Ï°ì¤Ä¤·¤«¤Ê¤¤¤Î¤Ç¡¢ + µ¯Æ°»þ¤Ë¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¥¹¥ì¥Ã¥É¤ÎÁí¿ô¤È¤Ê¤ê¤Þ¤¹¡£

+ +

beos ¤Ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ï StartThreads + 10 ¤Ç¤¹¡£ + ¤Þ¤¿¡¢µ¯Æ°»þ¤ËÀ¸À®¤µ¤ì¤ë¥¹¥ì¥Ã¥É¤ÎÁí¿ô¤Ë¤âÈ¿±Ç¤µ¤ì¤Þ¤¹¡£

+ +
+
top
+

ThreadLimit ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:ÀßÄê²Äǽ¤Ê»Ò¥×¥í¥»¥¹Ëè¤Î¥¹¥ì¥Ã¥É¿ô¤Î¾å¸Â¤ò +ÀßÄꤷ¤Þ¤¹
¹½Ê¸:ThreadLimit number
¥Ç¥Õ¥©¥ë¥È:¾ÜºÙ¤Ï»ÈÍÑÊýË¡¤ò»²¾È
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, mpm_winnt, perchild, threadpool, worker
¸ß´¹À­:Apache 2.0.41 ¤È¤½¤ì°Ê¹ß¤Î mpm_winnt +¤ÇÍøÍѲÄǽ
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + Apache ¥×¥í¥»¥¹²ÔƯÃæ¤Ë¤ª¤±¤ë + ThreadsPerChild + ¤ËÀßÄê²Äǽ¤Ê¾å¸ÂÃͤòÀßÄꤷ¤Þ¤¹¡£ºÆµ¯Æ°»þ¤Ë¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃͤò + Êѹ¹¤·¤Æ¤â̵»ë¤µ¤ì¤Þ¤¹¤¬¡¢ + ThreadsPerChild + ¤ÏºÆµ¯Æ°Ãæ¤Ë¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿¾å¸ÂÃÍ¤Þ¤Ç + Êѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ëºÝ¤ÏÆäËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ThreadLimit ¤¬ + ThreadsPerChild + ¤è¤ê¤â¤º¤Ã¤ÈÂ礭¤ÊÃͤËÀßÄꤵ¤ì¤¿¾ì¹ç¤Ï¡¢ + ;·×¤Ê̤»ÈÍѶ¦Í­¥á¥â¥ê¤¬³ä¤êÅö¤Æ¤é¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹¡£ + ThreadLimit ¤¬ + ThreadsPerChild + ¤ÎξÊý¤¬¥·¥¹¥Æ¥à¤Î°·¤¨¤ëÈϰϤòĶ¤¨¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + Apache ¤Ïµ¯Æ°¤·¤Ê¤¤¤«¡¢µ¯Æ°¤·¤¿¤È¤·¤Æ¤âÉÔ°ÂÄê¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃͤϺ£»ÈÍѤ·¤Æ¤¤¤ë Apache ¤Î ThreadsPerChild ¤ÎͽÁÛ¾å¸ÂÃͤò + Ķ¤¨¤¿ÃͤˤÏÀßÄꤷ¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£ +

+ +

ThreadLimit ¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï + mpm_winnt ¤Î¤È¤­¤Ï 1920 ¤Ç¡¢ + ¾¤Î¾ì¹ç¤Ï 64 ¤Ç¤¹¡£

+ +

Ãí°Õ

+

ThreadLimit 20000 (mpm_winnt + ¤Î¾ì¹ç¤Ï ThreadLimit 15000 ) + ¤È¤¤¤¦À©¸ÂÉÕ¤­¤Ç¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤³¤ì¤Ï¥¹¥Ú¥ë¥ß¥¹¤Ë¤è¤Ã¤Æ¸í¤Ã¤Æ¹ó¤¤¾õ¶·¤Ë¤Ê¤ë¤Î¤ò¡¢ + ²óÈò¤¹¤ë¤¿¤á¤Î½èÃ֤Ǥ¹¡£

+
+ +
+
top
+

ThreadsPerChild ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:»Ò¥×¥í¥»¥¹¤½¤ì¤¾¤ì¤ËÀ¸À®¤µ¤ì¤ë¥¹¥ì¥Ã¥É¿ô
¹½Ê¸:ThreadsPerChild number
¥Ç¥Õ¥©¥ë¥È:¾ÜºÙ¤Ï»ÈÍÑÊýË¡¤ò»²¾È
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, mpm_winnt, threadpool, worker
+

¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¤½¤ì¤¾¤ì¤Î»Ò¥×¥í¥»¥¹¤ÇÀ¸À®¤µ¤ì¤ë + ¥¹¥ì¥Ã¥É¿ô¤òÀßÄꤷ¤Þ¤¹¡£ + »Ò¥×¥í¥»¥¹¤Ï³«»Ï»þ¤Ë¤³¤ì¤é¤Î¥¹¥ì¥Ã¥É¤òÀ¸À®¤·¤Æ¡¢ + ¤½¤Î¸å¤ÏÀ¸À®¤·¤Þ¤»¤ó¡£mpm_winnt ¤Î¤è¤¦¤Ê¡¢ + »Ò¥×¥í¥»¥¹¤¬°ì¤Ä¤·¤«¤Ê¤¤¤è¤¦¤Ê MPM ¤òÍøÍѤ·¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¤³¤ÎÃͤϥµ¡¼¥Ð¤ÎÉé²ÙÁ´ÂΤò½½Ê¬¼è¤ê°·¤¨¤ëÄøÅ٤ˡ¢ + Â礭¤¯¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£worker ¤Î¤è¤¦¤Ê¡¢ + »Ò¥×¥í¥»¥¹¤¬Ê£¿ô¤¢¤ë¤è¤¦¤Ê MPM ¤òÍøÍѤ·¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¥µ¡¼¥Ð¤ÎÄ̾ïÉé²Ù¤ò½½Ê¬°·¤¨¤ëÄøÅ٤ˡ¢ + ¥¹¥ì¥Ã¥ÉÁí¿ô¤¬Â¿¤¯¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

mpm_winnt¤Ç¤Î ThreadsPerChild + ¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 64 ¤Ç¡¢Â¾¤Î¾ì¹ç¤Ï + 25 ¤Ç¤¹¡£

+ +
+
top
+

ThreadStackSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥¯¥é¥¤¥¢¥ó¥È¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò¼õ¤±»ý¤Ä¥¹¥ì¥Ã¥É¤¬»ÈÍѤ¹¤ë +¥¹¥¿¥Ã¥¯¤Î¥Ð¥¤¥È¿ô
¹½Ê¸:ThreadStackSize size
¥Ç¥Õ¥©¥ë¥È:NetWare ¤Ç¤Ï 65536¡£Â¾¤Î OS ¤Ç¤Ï°ã¤Ã¤¿ÃÍ
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, mpm_netware, mpm_winnt, perchild, threadpool, worker
¸ß´¹À­:2.1 °Ê¹ß
+

¥¯¥é¥¤¥¢¥ó¥È¥³¥Í¥¯¥·¥ç¥ó¤ò¼õ¤±»ý¤Á¡¢¥³¥Í¥¯¥·¥ç¥ó½èÍý¤ËɬÍפʥ⥸¥å¡¼¥ë¤Î + ¸Æ¤Ó½Ð¤·¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤ë¥¹¥ì¥Ã¥É¤Î¡¢(¼«Æ°ÊÑ¿ôÍѤÎ) ¥¹¥¿¥Ã¥¯¥µ¥¤¥º¤Ï + ThreadStackSize ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤷ¤Þ¤¹¡£ + ÂçÄñ¤Î¾ì¹ç OS ¤Î»ØÄꤷ¤Æ¤¤¤ë¥¹¥¿¥Ã¥¯¥µ¥¤¥º¤Î¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï + ŬÀڤʤâ¤Î¤Ç¤¹¤¬¡¢Ä´À°¤¬É¬Íפˤʤë¾ì¹ç¤â¤¢¤ê¤Þ¤¹:

+ +
    +
  • ¥¹¥ì¥Ã¥É¥¹¥¿¥Ã¥¯¥µ¥¤¥º¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤ¬Èæ³ÓŪ¾®¤µ¤¯ÀßÄꤵ¤ì¤Æ¤¤¤ë + ¥×¥é¥Ã¥È¥Û¡¼¥à (Î㤨¤Ð HP-UX) ¤Ç¤Ï¡¢¼«Æ°ÊÑ¿ôÍѤÎÎΰè¤ÇÂ礭¤ÊÍÆÎ̤ò + »ÈÍѤ¹¤ë¥µ¡¼¥É¥Ñ¡¼¥Æ¥£À½¥â¥¸¥å¡¼¥ë¤Î¤¿¤á¤Ë Apache ¤¬¥¯¥é¥Ã¥·¥å¤¹¤ë + ¾ì¹ç¤â¤¢¤ê¤Þ¤¹¡£¤½¤Î¥â¥¸¥å¡¼¥ë¤Ï¾¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤Ï + ¥¹¥¿¥Ã¥¯¥µ¥¤¥º¤¬Â礭¤¤¤¿¤á¤Ë¡¢²÷Ä´¤ËÆ°ºî¤¹¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤³¤Î¥¿¥¤¥×¤Î¥¯¥é¥Ã¥·¥å¤Ï¡¢ThreadStackSize + ¤Ç OS ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤè¤êÂ礭¤ÊÃͤò»ØÄꤹ¤ë¤³¤È¤Ç²ò·è¤·¤Þ¤¹¡£ + ¥µ¡¼¥É¥Ñ¡¼¥Æ¥£À½¥â¥¸¥å¡¼¥ë¤Ç¤³¤Î½èÃÖ¤¬É¬ÍפǤ¢¤ë¤Èµ­ºÜ¤µ¤ì¤Æ¤¤¤ë + ¾ì¹ç¤«¡¢Apache ¤Î½ÐÎϤ¹¤ë¥á¥Ã¥»¡¼¥¸¤Ç¥¹¥ì¥Ã¥É¥¹¥¿¥Ã¥¯¥µ¥¤¥º¤¬ + ¾®¤µ¤¹¤®¤ë¤È»ØŦ¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ë¤Î¤ß¡¢¤³¤ÎÄ´À°¤ò¤·¤Æ¤¯¤À¤µ¤¤¡£
    • + +
  • ¥Ç¥Õ¥©¥ë¥È¥¹¥ì¥Ã¥É¥¹¥¿¥Ã¥¯¥µ¥¤¥º¤¬¡¢Web ¥µ¡¼¥ÐÍÑÅÓ¤ËɬÍפÊÎ̤è¤ê¤â + ÌÀ¤é¤«¤ËÂ礭¤¹¤®¤ë¾ì¹ç¡¢ThreadStackSize + ¤ò OS ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤè¤ê¤â¾®¤µ¤ÊÃͤˤ¹¤ë¤³¤È¤Ç¡¢»Ò¥×¥í¥»¥¹¤¢¤¿¤ê¤Î + ¥¹¥ì¥Ã¥É¿ô¤ò¤è¤ê¿¤¯»ý¤¿¤»¤é¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤³¤Î¥¿¥¤¥×¤ÎÄ´À°¤Ï¡¢¥Æ¥¹¥È´Ä¶­¤Ç¥¦¥§¥Ö¥µ¡¼¥Ð¤ò´°Á´¤Ë + ¥Æ¥¹¥È¤Ç¤­¤ë¾ì¹ç¤Ë¸Â¤Ã¤Æ¹Ô¤Ê¤¦¤Ù¤­¤Ç¤¹¡£ + ¤Þ¤ì¤Ë¿¿ô¤Î¥¹¥¿¥Ã¥¯¤¬Í׵ᤵ¤ì¤ë¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¤ë¤³¤È¤¬¤¢¤ë¤«¤â + ¤·¤ì¤Ê¤¤¤«¤é¤Ç¤¹¡£ + Web ¥µ¡¼¥Ð¤ÎÀßÄê¤òÊѹ¹¤¹¤ë¤È¡¢¸½ºß¤Î ThreadStackSize + ¤ÎÀßÄ꤬¼è¤ê¾Ã¤µ¤ì¤ë¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£
    • +
+ +
+
top
+

User ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ëºÝ¤ËÍѤ¤¤ë¥æ¡¼¥¶ ID
¹½Ê¸:User unix-userid
¥Ç¥Õ¥©¥ë¥È:User #-1
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:leader, perchild, prefork, threadpool, worker
¸ß´¹À­:Apache 2.0 °Ê¹ß¤Ç¡¢¥°¥í¡¼¥Ð¥ëÀßÄê¤Ç¤Î¤ßÍ­¸ú¤Ç¤¹¡£ +
+

User ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥µ¡¼¥Ð¤¬¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ëºÝ¤ËÍѤ¤¤ë¥æ¡¼¥¶ ID ¤òÀßÄꤷ¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢¥¹¥¿¥ó¥É¥¢¥í¥ó·¿¤Î + ¥µ¡¼¥Ð¤ÏºÇ½é¤Ë root ¸¢¸Â¤Çµ¯Æ°¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + Èó root ¥æ¡¼¥¶¤Ç¥µ¡¼¥Ð¤òµ¯Æ°¤·¤¿¾ì¹ç¤Ï¡¢ + ¸¢¸Â¤ÎÄ㤤¥æ¡¼¥¶¤Ø¤ÈÊѤï¤ë¤³¤È¤¬¤Ç¤­¤º¡¢ + ·ë¶É¸µ¤Î¥æ¡¼¥¶¤Î¥×¥í¥»¥¹¤È¤·¤Æ¼Â¹Ô¤µ¤ì³¤±¤Þ¤¹¡£ + root ¤Çµ¯Æ°¤·¤¿¾ì¹ç¤Ë¿Æ¥×¥í¥»¥¹¤¬ root + ¤È¤·¤Æ¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¤Î¤ÏÀµ¾ï¤ÊÆ°ºî¤Ç¤¹¡£ + Unix-userid ¤Ï¼¡¤Î¤É¤ì¤«¤Ç¤¹¡£

+ +
+
¥æ¡¼¥¶Ì¾
+
¥æ¡¼¥¶¤ò̾Á°¤Ç»²¾È¤·¤Þ¤¹¡£
+ +
# ¤Ë³¤¤¤Æ¥æ¡¼¥¶ÈÖ¹æ
+
¥æ¡¼¥¶¤òÈÖ¹æ¤Ç»²¾È¤·¤Þ¤¹¡£
+
+ +

¤³¤Î¥æ¡¼¥¶¤Ï¡¢³°Éô¤Ë¸«¤»¤ë¤è¤¦¤Ë°Õ¿Þ¤·¤Æ¤¤¤Ê¤¤¥Õ¥¡¥¤¥ë¤Ë¡¢ + ¥¢¥¯¥»¥¹²Äǽ¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¦¤è¤¦¤Ê¸¢¸Â¤ò»ý¤Ä¤Ù¤­¤Ç¤Ï¤Ê¤¤¤Ç¤¹¤·¡¢ + ƱÍÍ¤Ë HTTP ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ±þÅú¤¹¤ë¤è¤¦¤Ë°Õ¿Þ¤·¤Æ¤¤¤Ê¤¤ + ¼Â¹Ô¥³¡¼¥É¤ò¡¢¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ê¸¢¸Â¤ò»ý¤Ä¤Ù¤­¤Ç¤Ï¤Ê¤¤¤Ç¤¹¡£ + ¥µ¡¼¥Ð¤ò¼Â¹Ô¤¹¤ë¤¿¤á¤ËÆÃÄê¤Î¿·¤·¤¤¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤ò + ÀßÄꤹ¤ë¤³¤È¤ò¤ªÁ¦¤á¤¤¤¿¤·¤Þ¤¹¡£ + nobody ¥æ¡¼¥¶¤ò»ÈÍѤ¹¤ë´ÉÍý¼Ô¤â¤¤¤Þ¤¹¤¬¡¢ + ¤³¤ì¤¬¾ï¤Ë˾¤Þ¤·¤¤¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¤Ê¤¼¤Ê¤é nobody ¥æ¡¼¥¶¤Ï¡¢¥·¥¹¥Æ¥à¤Ç + ¾¤ÎÌò³ä¤òô¤Ã¤Æ¤¤¤ë¤«¤âÃΤì¤Ê¤¤¤«¤é¤Ç¤¹¡£

+ +

¥»¥­¥å¥ê¥Æ¥£

+

Àµ³Î¤Ë¤É¤ó¤Ê¤³¤È¤ò¤ä¤Ã¤Æ¤¤¤ë¤Î¤«¡¢¤½¤Î´í¸±À­¤òÃΤé¤Ê¤¤¤Ç¡¢ + User (¤ä Group) ¤ò root ¤Ë + ÀßÄꤷ¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£

+
+ +

perchild MPM ¤Ç¤Ï¡¢°Û¤Ê¤ë¥æ¡¼¥¶ ID + ¤ÇÊ£¿ô¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤òÆ°¤«¤¹¤³¤È¤òÌÜŪ¤È¤·¤Æ¤¤¤Þ¤¹¤¬¡¢ + User ¤Ï¡¢¼ç¥µ¡¼¥Ð¤Î¥æ¡¼¥¶ ID + ¤È¡¢AssignUserID + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ý¤¿¤Ê¤¤ <VirtualHost> ¥»¥¯¥·¥ç¥ó¤Ø¤Î + ¥Õ¥©¡¼¥ë¥Ð¥Ã¥¯¤È¤òÄêµÁ¤¹¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

Æõ­»ö¹à: ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + <VirtualHost> + ¤Ç»ÈÍѤ¹¤ë¤³¤È¤Ï¥µ¥Ý¡¼¥È¤µ¤ì¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿¡£ + suexec ¸þ¤±¤Ë¥µ¡¼¥Ð¤òÀßÄꤹ¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + SuexecUserGroup + ¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Ãí°Õ

+

User ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + beos ¤È mpmt_os2 MPM + ¤Ë¤â¸ºß¤·¤Þ¤¹¤¬¡¢¼Â¼ÁŪ¤Ë̵¸ú¤Ç¡¢¸ß´¹À­¤Î¤¿¤á¤À¤±¤Ë¸ºß¤·¤Þ¤¹¡£

+
+ +
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mpm_netware.html b/docs/manual/mod/mpm_netware.html new file mode 100644 index 00000000..03b1ca93 --- /dev/null +++ b/docs/manual/mod/mpm_netware.html @@ -0,0 +1,3 @@ +URI: mpm_netware.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mpm_netware.html.en b/docs/manual/mod/mpm_netware.html.en new file mode 100644 index 00000000..ed5919ec --- /dev/null +++ b/docs/manual/mod/mpm_netware.html.en @@ -0,0 +1,110 @@ + + + +mpm_netware - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache MPM netware

+
+

Available Languages:  en 

+
+ + + +
Description:Multi-Processing Module implementing an exclusively threaded web + server optimized for Novell NetWare
Status:MPM
Module Identifier:mpm_netware_module
Source File:mpm_netware.c
+

Summary

+ +

This Multi-Processing Module (MPM) implements an exclusively + threaded web server that has been optimized for Novell + NetWare.

+ +

The main thread is responsible for launching child + worker threads which listen for connections and serve them when they + arrive. Apache always tries to maintain several spare + or idle worker threads, which stand ready to serve incoming + requests. In this way, clients do not need to wait for a new + child threads to be spawned before their requests can be + served.

+ +

The StartThreads, + MinSpareThreads, + MaxSpareThreads, and + MaxThreads + regulate how the main thread creates worker threads to serve + requests. In general, Apache is very self-regulating, so most + sites do not need to adjust these directives from their default + values. Sites with limited memory may need to decrease MaxThreads to keep the server from + thrashing (spawning and terminating idle threads). More information + about tuning process creation is provided in the performance hints + documentation.

+ +

MaxRequestsPerChild + controls how frequently the server recycles processes by killing old + ones and launching new ones. On the NetWare OS it is highly + recommended that this directive remain set to 0. This allows worker + threads to continue servicing requests indefinitely.

+
+ + +
top
+

MaxThreads Directive

+ + + + + + + +
Description:Set the maximum number of worker threads
Syntax:MaxThreads number
Default:MaxThreads 2048
Context:server config
Status:MPM
Module:mpm_netware
+

The MaxThreads directive sets the desired + maximum number worker threads allowable. The default value is + also the compiled in hard limit. Therefore it can only be lowered, + for example:

+ +

+ MaxThreads 512 +

+ +
+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mpm_winnt.html b/docs/manual/mod/mpm_winnt.html new file mode 100644 index 00000000..c5d89ac9 --- /dev/null +++ b/docs/manual/mod/mpm_winnt.html @@ -0,0 +1,11 @@ +URI: mpm_winnt.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: mpm_winnt.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mpm_winnt.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/mpm_winnt.html.de b/docs/manual/mod/mpm_winnt.html.de new file mode 100644 index 00000000..3bc22d03 --- /dev/null +++ b/docs/manual/mod/mpm_winnt.html.de @@ -0,0 +1,94 @@ + + + +mpm_winnt - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module
+
+

Apache-MPM winnt

+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+ + + +
Beschreibung: Das Multi-Processing-Modul ist optimiert für + Windows NT.
Status:MPM
Modulbezeichner:mpm_winnt_module
Quelltext-Datei:mpm_winnt.c
+

Zusammenfassung

+ +

Dieses Multi-Processing-Modul (MPM) ist die Voreinstellung + für das Betriebssystem Windows NT. Es verwendet einen einzelnen + Steuerprozess, der einen einzelnen Kindprozess startet, welcher + wiederum Threads zur Bedienung von Anfragen erstellt.

+
+ + +
top
+

Win32DisableAcceptEx-Direktive

+ + + + + + + + +
Beschreibung:Für die Annahme von Netzwerkverbindungen wird accept() anstelle von AcceptEx() verwendet
Syntax:Win32DisableAcceptEx
Voreinstellung:AcceptEx() ist standardmäßig aktiviert. Verwenden Sie diese +Direktive, um den Gebrauch von AcceptEx() zu deaktivieren.
Kontext:Serverkonfiguration
Status:MPM
Modul:mpm_winnt
Kompatibilität:Verfügbar ab Version 2.0.49
+

AcceptEx() ist eine Schnittstelle zu Microsoft Winsock v2, + die unter bestimmten Umständen einige Leistungsverbesserungen + gegenüber der accept()-API von BSD bietet. Einige beliebte + Windows-Produkte, typischerweise Virenscanner oder VPN-Pakete, besitzen + jedoch Fehler, welche den einwandfreien Betrieb von AcceptEx() + stören. Wenn Sie einen Fehler wie:

+ +

+ [error] (730038)An operation was attempted on something that is + not a socket.: winnt_accept: AcceptEx failed. Attempting to recover. +

+ +

erhalten, sollten Sie diese Direktive verwenden, um den Gebrauch von + AcceptEx() zu unterbinden.

+ +
+
+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mpm_winnt.html.en b/docs/manual/mod/mpm_winnt.html.en new file mode 100644 index 00000000..f4bb962c --- /dev/null +++ b/docs/manual/mod/mpm_winnt.html.en @@ -0,0 +1,94 @@ + + + +mpm_winnt - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache MPM winnt

+
+

Available Languages:  de  | + en  | + ja 

+
+ + + +
Description:This Multi-Processing Module is optimized for Windows +NT.
Status:MPM
Module Identifier:mpm_winnt_module
Source File:mpm_winnt.c
+

Summary

+ +

This Multi-Processing Module (MPM) is the default for the + Windows NT operating systems. It uses a single control process + which launches a single child process which in turn creates + threads to handle requests

+
+ + +
top
+

Win32DisableAcceptEx Directive

+ + + + + + + + +
Description:Use accept() rather than AcceptEx() to accept network connections
Syntax:Win32DisableAcceptEx
Default:AcceptEx() is enabled by default. Use this directive to disable use of + AcceptEx()
Context:server config
Status:MPM
Module:mpm_winnt
Compatibility:Available in Version 2.0.49 and later
+

AcceptEx() is a Microsoft WinSock v2 API that provides + some performance improvements over the use of the BSD style + accept() API in certain circumstances. Some popular Windows + products, typically virus scanning or virtual private network + packages, have bugs that interfere with the proper operation of + AcceptEx(). If you encounter an error condition like:

+ +

+ [error] (730038)An operation was attempted on something that is + not a socket.: winnt_accept: AcceptEx failed. Attempting to recover. +

+ +

you should use this directive to disable the use of + AcceptEx().

+ +
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mpm_winnt.html.ja.euc-jp b/docs/manual/mod/mpm_winnt.html.ja.euc-jp new file mode 100644 index 00000000..9b62a01d --- /dev/null +++ b/docs/manual/mod/mpm_winnt.html.ja.euc-jp @@ -0,0 +1,93 @@ + + + +mpm_winnt - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache MPM winnt

+
+

Available Languages:  de  | + en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:Windows NT +¸þ¤±¤ËºÇŬ²½¤µ¤ì¤¿¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:mpm_winnt_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:mpm_winnt.c
+

³µÍ×

+ +

¤³¤Î¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM) + ¤Ï Windows NT ¤Ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ë¤Ê¤ê¤Þ¤¹¡£ + °ì¤Ä¤ÎÀ©¸æÍÑ¥×¥í¥»¥¹¤òÍѤ¤¡¢¤³¤ì¤¬°ì¤Ä¤Î»Ò¥×¥í¥»¥¹¤òµ¯Æ°¤·¡¢ + ¤½¤·¤Æ»Ò¥×¥í¥»¥¹¤¬¥ê¥¯¥¨¥¹¥È¤ò¼è¤ê°·¤¦¤¿¤á¤Ë¥¹¥ì¥Ã¥É¤ò + µ¯Æ°¤·¤Þ¤¹¡£

+
+ + +
top
+

Win32DisableAcceptEx ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + + +
ÀâÌÀ:¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤Î¼õ¤±ÉÕ¤±¤Ë accept() ¤òAcceptEx ¤ÎÂå¤ï¤ê¤Ë»È¤¦
¹½Ê¸:Win32DisableAcceptEx
¥Ç¥Õ¥©¥ë¥È:AcceptEx() ¤Ï¥Ç¥Õ¥©¥ë¥È¤ÇÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£AcceptEx() ¤ò̵¸ú¤Ë¤¹¤ë +¤¿¤á¤Ë¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¤¤Þ¤¹¡£
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:mpm_winnt
¸ß´¹À­:2.0.49 ¥Ð¡¼¥¸¥ç¥ó°Ê¹ß¤Ç»ÈÍѲÄǽ
+

AcceptEx() ¤Ï Microsoft WinSock v2 API ¤Ç¡¢¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï + BSD ·Á¼°¤Î accept() API ¤è¤ê¤â¤è¤¤À­Ç½¤òȯ´ø¤·¤Þ¤¹¡£ + ¤è¤¯»È¤ï¤ì¤Æ¤¤¤ë Windows À½ÉʤÎÃæ¤Ç¡¢Æä˥¦¥£¥ë¥¹¥¹¥­¥ã¥Ê¤ä VPN ¥Ñ¥Ã¥±¡¼¥¸ + ¤ÎÃæ¤Ë¤Ï¡¢¥Ð¥°¤¬¸¶°ø¤Ç AcceptEx() ¤ÎŬÀÚ¤ÊÆ°ºî¤ò˸¤²¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£ + °Ê²¼¤Î¤è¤¦¤Ê¥¨¥é¡¼¤ËÁø¶ø¤·¤¿¾ì¹ç¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ + AcceptEx() ¤ò»ÈÍѤ·¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

+ [error] (730038)An operation was attempted on something that is + not a socket.: winnt_accept: AcceptEx failed. Attempting to recover. +

+ +
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/mpmt_os2.html b/docs/manual/mod/mpmt_os2.html new file mode 100644 index 00000000..df2b37df --- /dev/null +++ b/docs/manual/mod/mpmt_os2.html @@ -0,0 +1,3 @@ +URI: mpmt_os2.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/mod/mpmt_os2.html.en b/docs/manual/mod/mpmt_os2.html.en new file mode 100644 index 00000000..f0d23cfe --- /dev/null +++ b/docs/manual/mod/mpmt_os2.html.en @@ -0,0 +1,73 @@ + + + +mpmt_os2 - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache MPM os2

+
+

Available Languages:  en 

+
+ + + +
Description:Hybrid multi-process, multi-threaded MPM for OS/2
Status:MPM
Module Identifier:mpm_mpmt_os2_module
Source File:mpmt_os2.c
+

Summary

+ +

The Server consists of a main, parent process and a small, static + number of child processes.

+ +

The parent process's job is to manage the child processes. This + involves spawning children as required to ensure there are always + StartServers processes + accepting connections.

+ +

Each child process consists of a a pool of worker threads and a + main thread that accepts connections and passes them to the workers via + a work queue. The worker thread pool is dynamic, managed by a + maintenance thread so that the number of idle threads is kept between + MinSpareThreads and + MaxSpareThreads.

+
+ + +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/prefork.html b/docs/manual/mod/prefork.html new file mode 100644 index 00000000..4676cc4f --- /dev/null +++ b/docs/manual/mod/prefork.html @@ -0,0 +1,11 @@ +URI: prefork.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: prefork.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: prefork.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/prefork.html.de b/docs/manual/mod/prefork.html.de new file mode 100644 index 00000000..52e9e5b8 --- /dev/null +++ b/docs/manual/mod/prefork.html.de @@ -0,0 +1,191 @@ + + + +prefork - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module
+
+

Apache-MPM prefork

+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+ + + +
Beschreibung:Implementiert einen im Voraus forkenden Webserver ohne + Thread-Unterstützung
Status:MPM
Modulbezeichner:mpm_prefork_module
Quelltext-Datei:prefork.c
+

Zusammenfassung

+ +

Dieses Multi-Processing-Modul (MPM) implementiert einen + im Voraus forkenden Webserver ohne Thread-Unterstützung, der Anfragen + auf ähnliche Weise behandelt wie der Apache 1.3. Es ist für + Angebote geeignet, die aus Kompatibilitätsgründen mit + nicht-Thread-sicheren Bibliotheken Threading vermeiden müssen. + Es ist außerdem das geeignetste MPM, um jede Anfrage isoliert + zu bearbeiten, so dass Probleme mit einem einzelnen Prozess keinen + anderen beeinflussen.

+ +

Das MPM ist stark selbstregulierend, so dass es selten + notwendig ist, seine Konfigurationseinstellungen zu justieren. Das + Wichtigste ist, dass MaxClients + gross genug ist, so viele gleichzeitige Anfragen zu bedienen, wie Sie + erwarten, aber klein genug, um sicherzustellen, dass genug physischer + Arbeitsspeicher für alle Prozesse vorhanden ist.

+
+ +
top
+
+

Arbeitsweise

+

Ein einzelner Steuerprozess ist für den Start von + Kindprozessen verantwortlich, die auf Verbindungen warten und diese + bedienen, sobald sie eintreffen. Der Apache versucht immer, mehrere + freie oder unbeschäftigte Serverprozesse vorzuhalten, + die zur Bedienung eingehender Anfragen bereit stehen. Auf diese Weise + müssen Clients nicht darauf warten, dass neue Kindprozesse + geforkt werden, bevor ihre Anfrage bearbeitet werden kann.

+ +

StartServers, + MinSpareServers, + MaxSpareServers und + MaxClients regulieren, + wie der Elternprozess Kindprozesse zur Bedienung von Anfragen erstellt. + Im Allgemeinen ist der Apache sehr selbstregulierend, so dass die meisten + Angebote die Voreinstellung dieser Direktiven nicht verändern + müssen. Systeme, die mehr als 256 gleichzeitige Anfragen bedienen + müssen, können MaxClients erhöhen, während + Systeme mit begrenztem Arbeitsspeicher möglicherweise + MaxClients heruntersetzen + müssen, um den Server vor Flatterverhalten (Arbeitsspeicherinhalte auf + Platte auslagern - und zurück) zu schützen. Weitere + Informationen zur Feinabstimmung der Prozesserstellung sind in den + Performance-Hinweisen zu + finden.

+ +

Währen der Elternprozess unter Unix normalerweise als + root gestartet wird, um sich an Port 80 binden zu können, + werden die Kindprozesse unter einem weniger privilegierten Benutzer + gestartet. Die Direktiven User + und Group werden dazu + verwendet, die Privilegien der Apache-Kindprozesse festzulegen. Die + Kindprozesse müssen in der Lage sein, alle Inhalte zu lesen, die + sie ausliefern sollen, sollten darüber hinaus jedoch so wenig wie + möglich Rechte besitzen.

+ +

MaxRequestsPerChild + bestimmt, wie häufig der Server Prozesse erneuert, indem er alte + beendet und neue startet.

+
+
top
+

MaxSpareServers-Direktive

+ + + + + + + +
Beschreibung:Maximale Anzahl der unbeschäftigten Kindprozesse des + Servers
Syntax:MaxSpareServers Anzahl
Voreinstellung:MaxSpareServers 10
Kontext:Serverkonfiguration
Status:MPM
Modul:prefork
+

Die Direktive MaxSpareServers bestimmt das + gewünschte Maximum an unbeschäftigten + Kindprozessen des Servers. Ein unbeschäftiger Prozess ist einer, der + keine Anfrage bedient. Wenn mehr als MaxSpareServers + Prozesse unbeschäftigt sind, wird der Elternprozess die + überschüssigen Prozesse beenden.

+ +

Eine Feineinstellung dieses Parameters sollte nur bei sehr + beschäftigten Angeboten notwendig sein. Es ist nahezu immer eine + schlechte Idee, den Parameter auf einen hohen Wert zu setzen. Wenn Sie + versuchen, den Wert kleiner oder gleich MinSpareServers zu setzen, wird der Apache + ihn automatisch auf MinSpareServers + 1 + korrigieren.

+ +

Siehe auch

+ +
+
top
+

MinSpareServers-Direktive

+ + + + + + + +
Beschreibung:Minimale Anzahl der unbeschäftigten Kindprozesse des + Servers
Syntax:MinSpareServers Anzahl
Voreinstellung:MinSpareServers 5
Kontext:Serverkonfiguration
Status:MPM
Modul:prefork
+

Die Direktive MinSpareServers bestimmt das + gewünschte Minimum der unbeschäftigten + Kindprozesse des Servers. Ein unbeschäftigter Prozess ist einer, der + keine Anfrage bedient. Wenn weniger als + MinSpareServers Prozesse unbeschäftigt sind, + dann erstellt der Elternprozess neue mit einer maximalen Rate von 1 + pro Sekunde.

+ +

Die Feineinstellung des Parameters sollte nur bei sehr + beschäftigten Angeboten notwendig sein. Es ist nahezu immer eine + schlechte ide, den Parameter auf einen hohen Wert zu setzen.

+ +

Siehe auch

+ +
+
+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/prefork.html.en b/docs/manual/mod/prefork.html.en new file mode 100644 index 00000000..508c6fec --- /dev/null +++ b/docs/manual/mod/prefork.html.en @@ -0,0 +1,176 @@ + + + +prefork - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache MPM prefork

+
+

Available Languages:  de  | + en  | + ja 

+
+ + + +
Description:Implements a non-threaded, pre-forking web server
Status:MPM
Module Identifier:mpm_prefork_module
Source File:prefork.c
+

Summary

+ +

This Multi-Processing Module (MPM) implements a non-threaded, + pre-forking web server that handles requests in a manner similar + to Apache 1.3. It is appropriate for sites that need to avoid + threading for compatibility with non-thread-safe libraries. It + is also the best MPM for isolating each request, so that a problem + with a single request will not affect any other.

+ +

This MPM is very self-regulating, so it is rarely necessary to + adjust its configuration directives. Most important is that + MaxClients be big enough to + handle as many simultaneous requests as you expect to receive, but + small enough to assure that there is enough physical RAM for all + processes.

+
+ +
top
+
+

How it Works

+

A single control process is responsible for launching child + processes which listen for connections and serve them when they + arrive. Apache always tries to maintain several spare + or idle server processes, which stand ready to serve incoming + requests. In this way, clients do not need to wait for a new + child processes to be forked before their requests can be + served.

+ +

The StartServers, + MinSpareServers, + MaxSpareServers, and + MaxClients regulate how + the parent process creates children to serve requests. In general, + Apache is very self-regulating, so most sites do not need to + adjust these directives from their default values. Sites which + need to serve more than 256 simultaneous requests may need to + increase MaxClients, + while sites with limited memory may need to decrease MaxClients to keep the server from + thrashing (swapping memory to disk and back). More information + about tuning process creation is provided in the performance hints + documentation.

+ +

While the parent process is usually started as root + under Unix in order to bind to port 80, the child processes are + launched by Apache as a less-privileged user. The User and Group directives are used to set + the privileges of the Apache child processes. The child processes + must be able to read all the content that will be served, but + should have as few privileges beyond that as possible.

+ +

MaxRequestsPerChild + controls how frequently the server recycles processes by killing + old ones and launching new ones.

+
+
top
+

MaxSpareServers Directive

+ + + + + + + +
Description:Maximum number of idle child server processes
Syntax:MaxSpareServers number
Default:MaxSpareServers 10
Context:server config
Status:MPM
Module:prefork
+

The MaxSpareServers directive sets the + desired maximum number of idle child server processes. An + idle process is one which is not handling a request. If there are + more than MaxSpareServers idle, then the + parent process will kill off the excess processes.

+ +

Tuning of this parameter should only be necessary on very + busy sites. Setting this parameter to a large number is almost + always a bad idea. If you are trying to set the value equal to or lower than + MinSpareServers, Apache + will automatically adjust it to MinSpareServers + 1.

+ +

See also

+ +
+
top
+

MinSpareServers Directive

+ + + + + + + +
Description:Minimum number of idle child server processes
Syntax:MinSpareServers number
Default:MinSpareServers 5
Context:server config
Status:MPM
Module:prefork
+

The MinSpareServers directive sets the + desired minimum number of idle child server processes. An + idle process is one which is not handling a request. If there are + fewer than MinSpareServers idle, then the parent + process creates new children at a maximum rate of 1 per second.

+ +

Tuning of this parameter should only be necessary on very + busy sites. Setting this parameter to a large number is almost + always a bad idea.

+ +

See also

+ +
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/prefork.html.ja.euc-jp b/docs/manual/mod/prefork.html.ja.euc-jp new file mode 100644 index 00000000..9761725b --- /dev/null +++ b/docs/manual/mod/prefork.html.ja.euc-jp @@ -0,0 +1,189 @@ + + + +prefork - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache MPM prefork

+
+

Available Languages:  de  | + en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥¹¥ì¥Ã¥É¤ò»È¤ï¤º¡¢Àè¹Ô¤·¤Æ fork ¤ò¹Ô¤Ê¤¦¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¼ÂÁõ +
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:mpm_prefork_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:prefork.c
+

³µÍ×

+ +

¤³¤Î¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM) ¤Ï¡¢ + Unix ¾å¤Ç¤Î Apache 1.3 ¤Î¥Ç¥Õ¥©¥ë¥È¤ÎµóÆ°¤ÈÈó¾ï¤Ë¤è¤¯»÷¤¿ÊýË¡¤Ç + ¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤¹¤ë¡¢¥¹¥ì¥Ã¥É¤ò»È¤ï¤º¡¢Àè¹Ô¤·¤Æ fork ¤ò¹Ô¤Ê¤¦ + ¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£ + ¥¹¥ì¥Ã¥É¥»¡¼¥Õ¤Ç¤Ê¤¤¥é¥¤¥Ö¥é¥ê¤È¤Î¸ß´¹À­¤ò¤È¤ë¤¿¤á¤Ë¡¢ + ¥¹¥ì¥Ã¥É¤òÈò¤±¤ëɬÍפΤ¢¤ë¥µ¥¤¥È¤Ç¤Ï¡¢¤³¤Î¥â¥¸¥å¡¼¥ë¤Î»ÈÍѤ¬Å¬ÀڤǤ·¤ç¤¦¡£ + ¤¢¤ë¥ê¥¯¥¨¥¹¥È¤ÇȯÀ¸¤·¤¿ÌäÂ꤬¾¤Î¥ê¥¯¥¨¥¹¥È¤Ë±Æ¶Á¤·¤Ê¤¤¤è¤¦¤Ë¡¢ + ¸Ä¡¹¤Î¥ê¥¯¥¨¥¹¥È¤òñΥ¤¹¤ë¤Î¤Ë¤â¡¢ºÇŬ¤Ê MPM ¤Ç¤¹¡£

+ +

¤³¤Î MPM ¤ÏÈó¾ï¤Ë¼«Î§Åª¤Ê¤Î¤Ç¡¢¤³¤Î MPM ¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + Ä´À°¤¹¤ëɬÍפϤۤȤó¤É¤Ê¤¤¤Ç¤·¤ç¤¦¡£¤â¤Ã¤È¤â½ÅÍפʤ³¤È¤Ï¡¢ + MaxClients + ¤¬¡¢Í½ÁÛ¤µ¤ì¤ëƱ»þ¥ê¥¯¥¨¥¹¥È¿ô¤ò½½Ê¬°·¤¨¤ë¤°¤é¤¤¤ÏÂ礭¤¤¤±¤ì¤É¤â¡¢ + Á´¥×¥í¥»¥¹¤Ë½½Ê¬¤ÊʪÍý¥á¥â¥ê¤¬³Î¼Â¤Ë¹Ô¤­ÅϤëÄøÅ٤ˤϾ®¤µ¤¤Ãͤˤ¹¤ë¡¢ + ¤È¤¤¤¦¤³¤È¤Ç¤¹¡£

+ +
+ +
top
+
+

Æ°ºîÊýË¡

+

°ì¤Ä¤Î¥³¥ó¥È¥í¡¼¥ë¥×¥í¥»¥¹¤¬¡¢ + ¥³¥Í¥¯¥·¥ç¥ó¤ËÂФ·¤Æ listen ¤·¤Æ¡¢¤·¤«¤ë¤Ù¤­»þ¤Ë±þÅú¤¹¤ë + »Ò¥×¥í¥»¥¹¤òµ¯Æ°¤·¤Þ¤¹¡£Apache ¤Ï¾ï¤Ë´ö¤Ä¤«¤Î¥¹¥Ú¥¢ + ¤«¥¢¥¤¥É¥ë¤Ê¥µ¡¼¥Ð¥×¥í¥»¥¹¤ò°Ý»ý¤·¤Æ¤¤¤Æ¡¢¤½¤ì¤é¤ÏÆþ¤Ã¤Æ¤­¤¿ + ¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤Ç¤­¤ë¤è¤¦¤ËÂÔµ¡¤·¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Ë¤·¤Æ¥¯¥é¥¤¥¢¥ó¥È¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤¬±þÅú¤µ¤ì¤ëÁ°¤Ë¡¢ + ¿·¤·¤¤»Ò¥×¥í¥»¥¹¤¬ fork ¤µ¤ì¤ë¤Î¤òÂÔ¤¿¤Ê¤¯¤Æ¤â¤è¤¤¤è¤¦¤Ë + ¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£

+ +

¿Æ¥×¥í¥»¥¹¤¬¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¤Î»Ò¥×¥í¥»¥¹¤ò + ¤É¤Î¤è¤¦¤ËÀ¸À®¤¹¤ë¤«¤Ï¡¢ + StartServers, + MinSpareServers, + MaxSpareServers, + MaxClients + ¤ÇÄ´À°¤·¤Þ¤¹¡£°ìÈÌŪ¤Ë¡¢Apache ¤ÏÈó¾ï¤Ë¼«Î§Åª¤Ê¤Î¤Ç¡¢ + ÂçÄñ¤Î¥µ¥¤¥È¤Ç¤Ï¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¥Ç¥Õ¥©¥ë¥ÈÃͤ«¤éÄ´À°¤¹¤ë + ɬÍפϤʤ¤¤Ç¤·¤ç¤¦¡£ + Ʊ»þ¤Ë 256 ¤òĶ¤¨¤ë¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤·¤Ê¤¤¤È¤¤¤±¤Ê¤¤¥µ¥¤¥È¤Ç¤Ï¡¢ + MaxClients + ¤òÁý¤ä¤¹É¬Íפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£ + °ìÊý¡¢¥á¥â¥ê¤Î¸Â¤é¤ì¤Æ¤¤¤ë¥µ¥¤¥È¤Ç¤Ï¡¢¥¹¥é¥Ã¥·¥ó¥° + (¥á¥â¥ê¤È¥Ç¥£¥¹¥¯´Ö¤Ç²¿Å٤⥹¥ï¥Ã¥×) ¤¬µ¯¤³¤ë¤Î¤òËɤ°¤¿¤á¤Ë + MaxClients + ¤ò¸º¤é¤¹É¬Íפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£¥×¥í¥»¥¹À¸À®¤Î¥Á¥å¡¼¥Ë¥ó¥°¤Ë´Ø¤¹¤ë + ¾Ü¤·¤¤¾ðÊó¤Ï¡¢À­Ç½¤Ë´Ø¤¹¤ë¥Ò¥ó¥È + ¤Ë¤¢¤ê¤Þ¤¹¡£

+ +

Ä̾ï Unix ¤Ç¤Ï¿Æ¥×¥í¥»¥¹¤Ï 80 È֥ݡ¼¥È¤Ë¥Ð¥¤¥ó¥É¤¹¤ë¤¿¤á¤Ë + root ¤Çµ¯Æ°¤µ¤ì¤Þ¤¹¤¬¡¢»Ò¥×¥í¥»¥¹¤ä¥¹¥ì¥Ã¥É¤Ï + ¤â¤Ã¤ÈÄ㤤¸¢¸Â¤Î¥æ¡¼¥¶¤Ç Apache ¤Ë¤è¤Ã¤Æµ¯Æ°¤µ¤ì¤Þ¤¹¡£ + User ¤È + Group + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + Apache ¤Î»Ò¥×¥í¥»¥¹¤Î¸¢¸Â¤òÀßÄꤹ¤ë¤Î¤ËÍѤ¤¤é¤ì¤Þ¤¹¡£ + »Ò¥×¥í¥»¥¹¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ë¥³¥ó¥Æ¥ó¥ÄÁ´¤Æ¤òÆɤá¤Ê¤¤¤È¤¤¤±¤Þ¤»¤ó¤¬¡¢ + ²Äǽ¤Ê¸Â¤êɬÍ׺Ǿ®¸Â¤Î¸¢¸Â¤Î¤ß¤ò»ý¤Ã¤Æ¤¤¤ë¤è¤¦¤Ë¤¹¤ë¤Ù¤­¤Ç¤¹¡£

+ +

MaxRequestsPerChild + ¤Ï¡¢¸Å¤¤¥×¥í¥»¥¹¤òÄä»ß¤·¤Æ¿·¤·¤¤¥×¥í¥»¥¹¤òµ¯Æ°¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢ + ¤É¤ÎÄøÅÙ¤ÎÉÑÅ٤ǥµ¡¼¥Ð¤¬¥×¥í¥»¥¹¤ò¥ê¥µ¥¤¥¯¥ë¤¹¤ë¤«¤òÀ©¸æ¤·¤Þ¤¹¡£

+
+
top
+

MaxSpareServers ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¢¥¤¥É¥ë¤Ê»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤ÎºÇÂç¸Ä¿ô
¹½Ê¸:MaxSpareServers number
¥Ç¥Õ¥©¥ë¥È:MaxSpareServers 10
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:prefork
+

MaxSpareServers ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥¢¥¤¥É¥ë¤Ê»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤Î´õ˾ºÇÂç¸Ä¿ô¤òÀßÄꤷ¤Þ¤¹¡£ + ¥¢¥¤¥É¥ë¥×¥í¥»¥¹¤È¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤Æ¤¤¤Ê¤¤¥×¥í¥»¥¹¤Ç¤¹¡£ + MaxSpareServers ¤è¤ê¤â¿¤¤¿ô¤¬¥¢¥¤¥É¥ë¤Ç¤¢¤ì¤Ð¡¢ + ¿Æ¥×¥í¥»¥¹¤ÏĶ²á¥×¥í¥»¥¹¤ò kill ¤·¤Þ¤¹¡£

+ +

Èó¾ï¤Ëº®¤ó¤Ç¤¤¤ë¥µ¥¤¥È¤Ç¤Î¤ß¡¢¤³¤Î¥Ñ¥é¥á¡¼¥¿¤ò¥Á¥å¡¼¥Ë¥ó¥°¤¹¤ë¤Ù¤­¤Ç¤¹¡£ + ¤³¤Î¥Ñ¥é¥á¡¼¥¿¤òÂ礭¤¯¤¹¤ë¤È¤¤¤¦¤³¤È¤Ï¡¢ÂçÄñ¤Î¾ì¹ç¤Ï°­¤¤È¯ÁۤǤ¹¡£ + MinSpareServers + °Ê²¼¤ËÀßÄꤷ¤¿¾ì¹ç¡¢MinSpareServers + +1 ¤Ë¼«Æ°Ä´À°¤µ¤ì¤Þ¤¹¡£

+ +

»²¾È

+ +
+
top
+

MinSpareServers ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

+ + + + + + + +
ÀâÌÀ:¥¢¥¤¥É¥ë¤Ê»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤ÎºÇ¾®¸Ä¿ô
¹½Ê¸:MinSpareServers number
¥Ç¥Õ¥©¥ë¥È:MinSpareServers 5
¥³¥ó¥Æ¥­¥¹¥È:¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë:prefork
+

MaxSpareServers ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥¢¥¤¥É¥ë¤Ê»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤Î´õ˾ºÇ¾®¸Ä¿ô¤òÀßÄꤷ¤Þ¤¹¡£ + ¥¢¥¤¥É¥ë¥×¥í¥»¥¹¤È¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤ò°·¤Ã¤Æ¤¤¤Ê¤¤¥×¥í¥»¥¹¤Ç¤¹¡£ + MinSpareServers ¤è¤ê¤â¾¯¤Ê¤¤¿ô¤¬¥¢¥¤¥É¥ë¤Ç¤¢¤ì¤Ð¡¢ + ¿Æ¥×¥í¥»¥¹¤ÏºÇ¹â¤Ç 1 ÉäˤĤ­ 1 ¸Ä¤Î³ä¹ç¤Ç¿·¤·¤¤»Ò¥×¥í¥»¥¹¤òÀ¸À®¤·¤Þ¤¹¡£

+ +

Èó¾ï¤Ëº®¤ó¤Ç¤¤¤ë¥µ¥¤¥È¤Ç¤Î¤ß¡¢¤³¤Î¥Ñ¥é¥á¡¼¥¿¤ò¥Á¥å¡¼¥Ë¥ó¥°¤¹¤ë¤Ù¤­¤Ç¤¹¡£ + ¤³¤Î¥Ñ¥é¥á¡¼¥¿¤òÂ礭¤¯¤¹¤ë¤È¤¤¤¦¤³¤È¤Ï¡¢ÂçÄñ¤Î¾ì¹ç¤Ï°­¤¤È¯ÁۤǤ¹¡£

+ +

»²¾È

+ +
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/quickreference.html b/docs/manual/mod/quickreference.html new file mode 100644 index 00000000..d0378571 --- /dev/null +++ b/docs/manual/mod/quickreference.html @@ -0,0 +1,23 @@ +URI: quickreference.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: quickreference.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: quickreference.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: quickreference.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: quickreference.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: quickreference.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R diff --git a/docs/manual/mod/quickreference.html.de b/docs/manual/mod/quickreference.html.de new file mode 100644 index 00000000..73d117d8 --- /dev/null +++ b/docs/manual/mod/quickreference.html.de @@ -0,0 +1,764 @@ + + + +Kurzreferenz der Direktiven - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module
+

Kurzreferenz der Direktiven

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

Die Kurzreferenz der Direktiven zeigt die Verwendung, + Voreinstellung, den Status und den Kontext aller + Apache-Konfigurationsanweisungen. Für weitergehende Informationen + schauen Sie bitte im Verzeichnis der Direktiven.

+ +

Die erste Spalte enthält den Namen und die Verwendung. + Die zweite Spalte zeigt die Voreinstellung der Direktive, sofern + eine Voreinstellung existiert. Wenn die Voreinstellung zu breit + für die Anzeige ist, werden die ersten Buchstaben angegeben, + gefolgt von einem "+".

+ +

Die dritte und vierte Spalte geben den Kontext an, in dem die + Direktive erlaubt ist, sowie den Status der Direktive entsprechend + der Legende.

+
+
+ + + +
 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X  + + + + + +
sServerkonfiguration
vVirtual Host
dVerzeichnis
h.htaccess
 + + + + + + +
CCore
MMPM
BBasis
EErweiterung
Xexperimentell
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
AcceptMutex Default|Methode Default sM
Vom Apache verwendete Methode zur Serialisierung mehrerer + Kindprozesse, die Anfragen an Netzwerk-Sockets entgegennehmen.
AcceptPathInfo On|Off|Default Default svdhC
Ressourcen lassen angehängte Pfadangaben zu
AccessFileName Dateiname [Dateiname] ... .htaccess svC
Name der dezentralen Konfigurationsdateien
Action Aktionsart CGI-Skript [virtual]svdhB
Aktiviert ein CGI-Skript für einen bestimmten Handler oder + Content-Type
AddAlt string file [file] ...svdhB
Alternate text to display for a file, instead of an +icon selected by filename
AddAltByEncoding string MIME-encoding +[MIME-encoding] ...svdhB
Alternate text to display for a file instead of an icon +selected by MIME-encoding
AddAltByType string MIME-type +[MIME-type] ...svdhB
Alternate text to display for a file, instead of an +icon selected by MIME content-type
AddCharset charset extension +[extension] ...svdhB
Maps the given filename extensions to the specified content +charset
AddDefaultCharset On|Off|Zeichenkodierung Off svdhC
Standard-Charset-Parameter, der bei Antworten vom Content-Type + text/plain oder text/html hinzugefügt wird +
AddDescription string file [file] ...svdhB
Description to display for a file
AddEncoding MIME-enc extension +[extension] ...svdhB
Maps the given filename extensions to the specified encoding +type
AddHandler handler-name extension +[extension] ...svdhB
Maps the filename extensions to the specified +handler
AddIcon icon name [name] +...svdhB
Icon to display for a file selected by name
AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...svdhB
Icon to display next to files selected by MIME +content-encoding
AddIconByType icon MIME-type +[MIME-type] ...svdhB
Icon to display next to files selected by MIME +content-type
AddInputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +client requests
AddLanguage MIME-lang extension +[extension] ...svdhB
Maps the given filename extension to the specified content +language
AddModuleInfo module-name stringsvE
Adds additional information to the module +information displayed by the server-info handler
AddOutputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +responses from the server
AddOutputFilterByType Filter[;Filter...] +MIME-Type [MIME-Type] ...svdhC
einen Ausgabefilter einem bestimmten MIME-Type +zuordnen
AddType MIME-type extension +[extension] ...svdhB
Maps the given filename extensions onto the specified content +type
Alias URL-path +file-path|directory-pathsvB
Maps URLs to filesystem locations
AliasMatch regex +file-path|directory-pathsvB
Maps URLs to filesystem locations using regular +expressions
Allow from all|host|env=env-variable +[host|env=env-variable] ...dhB
Controls which hosts can access an area of the +server
AllowCONNECT port [port] ... 443 563 svE
Ports that are allowed to CONNECT through the +proxy
AllowEncodedSlashes On|Off Off svC
Legt fest, ob kodierte Pfadtrennzeichen in URLs durchgereicht +werden dürfen
AllowOverride All|None|Direktiven-Typ +[Direktiven-Typ] ... All dC
Direktiven-Typen, die in .htaccess-Dateien +erlaubt sind.
Anonymous user [user] ...dhE
Specifies userIDs that are allowed access without +password verification
Anonymous_LogEmail On|Off On dhE
Sets whether the password entered will be logged in the +error log
Anonymous_MustGiveEmail On|Off On dhE
Specifies whether blank passwords are allowed
Anonymous_NoUserID On|Off Off dhE
Sets whether the userID field may be empty
Anonymous_VerifyEmail On|Off Off dhE
Sets whether to check the password field for a correctly +formatted email address
AuthBasicAuthoritative On|Off On dhB
Sets whether authorization and authentication are passed to +lower level modules
AuthBasicProvider provider-name +[provider-name] ... file dhB
Sets the authentication provider(s) for this location
AuthDBDUserPWQuery querydE
SQL query to look up a password for a user
AuthDBDUserRealmQuery querydE
SQL query to look up a password hash for a user and realm. +
AuthDBMGroupFile file-pathdhE
Sets the name of the database file containing the list +of user groups for authorization
AuthDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store passwords
AuthDBMUserFile file-pathdhE
Sets the name of a database file containing the list of users and +passwords for authentication
AuthDefaultAuthoritative On|Off On dhB
Sets whether authentication is passed to lower level +modules
AuthDigestAlgorithm MD5|MD5-sess MD5 dhX
Selects the algorithm used to calculate the challenge and +response hashes in digest authentication
AuthDigestDomain URI [URI] ...dhX
URIs that are in the same protection space for digest +authentication
AuthDigestNcCheck On|Off Off sX
Enables or disables checking of the nonce-count sent by the +server
AuthDigestNonceFormat formatdhX
Determines how the nonce is generated
AuthDigestNonceLifetime seconds 300 dhX
How long the server nonce is valid
AuthDigestProvider provider-name +[provider-name] ... file dhX
Sets the authentication provider(s) for this location
AuthDigestQop none|auth|auth-int [auth|auth-int] auth dhX
Determines the quality-of-protection to use in digest +authentication
AuthDigestShmemSize size 1000 sX
The amount of shared memory to allocate for keeping track +of clients
AuthGroupFile file-pathdhB
Sets the name of a text file containing the list +of user groups for authorization
AuthLDAPBindDN distinguished-namedhE
Optional DN to use in binding to the LDAP server
AuthLDAPBindPassword passworddhE
Password used in conjuction with the bind DN
AuthLDAPCharsetConfig file-pathsE
Language to charset conversion configuration file
AuthLDAPCompareDNOnServer on|off on dhE
Use the LDAP server to compare the DNs
AuthLDAPDereferenceAliases never|searching|finding|always Always dhE
When will the module de-reference aliases
AuthLDAPGroupAttribute attributedhE
LDAP attributes used to check for group membership
AuthLDAPGroupAttributeIsDN on|off on dhE
Use the DN of the client username when checking for +group membership
AuthLDAPRemoteUserIsDN on|off off dhE
Use the DN of the client username to set the REMOTE_USER +environment variable
AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]dhE
URL specifying the LDAP search parameters
AuthName auth-BereichdhC
Autorisierungsbereich zur Verwendung in der +HTTP-Authentisierung
<AuthnProviderAlias baseProvider Alias> +... </AuthnProviderAlias>svE
Enclose a group of directives that represent an +extension of a base authentication provider and referenced by +the specified alias
AuthType Basic|DigestdhC
Art der Authentisierung
AuthUserFile file-pathdhB
Sets the name of a text file containing the list of users and +passwords for authentication
AuthzDBMAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store list of user groups
AuthzDefaultAuthoritative On|Off On dhB
Sets whether authorization is passed to lower level +modules
AuthzGroupFileAuthoritative On|Off On dhB
Sets whether authorization will be passed on to lower level +modules
AuthzLDAPAuthoritative on|off on dhE
Prevent other authentication modules from +authenticating the user if this one fails
AuthzOwnerAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzUserAuthoritative On|Off On dhB
Sets whether authorization will be passed on to lower level +modules
BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...svdhB
Sets environment variables conditional on HTTP User-Agent +
BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables conditional on User-Agent without +respect to case
BufferedLogs On|Off Off sB
Buffer log entries in memory before writing to disk
CacheDefaultExpire seconds 3600 (one hour) svE
The default duration to cache a document when no expiry date is specified.
CacheDirLength length 2 svE
The number of characters in subdirectory names
CacheDirLevels levels 3 svE
The number of levels of subdirectories in the +cache.
CacheDisable url-stringsvE
Disable caching of specified URLs
CacheEnable cache_type url-stringsvE
Enable caching of specified URLs using a specified storage +manager
CacheFile file-path [file-path] ...sX
Cache a list of file handles at startup time
CacheIgnoreCacheControl On|Off Off svE
Ignore request to not serve cached content to client
CacheIgnoreHeaders header-string [header-string] ... None svE
Do not store the given HTTP header(s) in the cache. +
CacheIgnoreNoLastMod On|Off Off svE
Ignore the fact that a response has no Last Modified +header.
CacheLastModifiedFactor float 0.1 svE
The factor used to compute an expiry date based on the +LastModified date.
CacheMaxExpire seconds 86400 (one day) svE
The maximum time in seconds to cache a document
CacheMaxFileSize bytes 1000000 svE
The maximum size (in bytes) of a document to be placed in the +cache
CacheMinFileSize bytes 1 svE
The minimum size (in bytes) of a document to be placed in the +cache
CacheNegotiatedDocs On|Off Off svB
Allows content-negotiated documents to be +cached by proxy servers
CacheRoot directorysvE
The directory root under which cache files are +stored
CacheStoreNoStore On|Off Off svE
Attempt to cache requests or responses that have been marked as no-store.
CacheStorePrivate On|Off Off svE
Attempt to cache responses that the server has marked as private
CGIMapExtension CGI-Pfad .EndungdhC
Technik zur Bestimmung des Interpreters für +CGI-Skripte
CharsetDefault charsetsvdhX
Charset to translate into
CharsetOptions option [option] ... DebugLevel=0 NoImpl +svdhX
Configures charset translation behavior
CharsetSourceEnc charsetsvdhX
Source charset of files
CheckSpelling on|off Off svdhE
Enables the spelling +module
ContentDigest On|Off Off svdhC
Aktiviert die Generierung von Content-MD5 +HTTP-Response-Headern
CookieDomain domainsvdhE
The domain to which the tracking cookie applies
CookieExpires expiry-periodsvdhE
Expiry time for the tracking cookie
CookieLog filenamesvB
Sets filename for the logging of cookies
CookieName token Apache svdhE
Name of the tracking cookie
CookieStyle + Netscape|Cookie|Cookie2|RFC2109|RFC2965 Netscape svdhE
Format of the cookie header field
CookieTracking on|off off svdhE
Enables tracking cookie
CoreDumpDirectory VerzeichnissM
Verzeichnis, in das der Apache zu wechseln versucht, bevor er + einen Hauptspeicherauszug erstellt
CustomLog file|pipe +format|nickname +[env=[!]environment-variable]svB
Sets filename and format of log file
Dav On|Off|provider-name Off dE
Enable WebDAV HTTP methods
DavDepthInfinity on|off off svdE
Allow PROPFIND, Depth: Infinity requests
DavGenericLockDB file-pathsvdE
Location of the DAV lock database
DavLockDB file-pathsvE
Location of the DAV lock database
DavMinTimeout seconds 0 svdE
Minimum amount of time the server holds a lock on +a DAV resource
DBDExptime time-in-secondssvE
Keepalive time for idle connections
DBDKeep numbersvE
Maximum sustained number of connections
DBDMax numbersvE
Maximum number of connections
DBDMin numbersvE
Minimum number of connections
DBDParams +param1=value1[,param2=value2]svE
Parameters for database connection
DBDPersist 0|1svE
Whether to use persistent connections
DBDPrepareSQL "SQL statement" labelsvE
Define an SQL prepared statement
DBDriver namesvE
Specify an SQL driver
DefaultIcon url-pathsvdhB
Icon to display for files when no specific icon is +configured
DefaultLanguage MIME-langsvdhB
Sets all files in the given scope to the specified +language
DefaultType MIME-Type text/plain svdhC
MIME-Content-Type, der gesendet wird, wenn der Server den Typ +nicht auf andere Weise ermitteln kann.
DeflateBufferSize value 8096 svE
Fragment size to be compressed at one time by zlib
DeflateCompressionLevel valuesvE
How much compression do we apply to the output
DeflateFilterNote [type] notenamesvE
Places the compression ratio in a note for logging
DeflateMemLevel value 9 svE
How much memory should be used by zlib for compression
DeflateWindowSize value 15 svE
Zlib compression window size
Deny from all|host|env=env-variable +[host|env=env-variable] ...dhB
Controls which hosts are denied access to the +server
<Directory Verzeichnispfad> +... </Directory>svC
Umschließt eine Gruppe von Direktiven, die nur auf +das genannte Verzeichnis des Dateisystems und Unterverzeichnisse angewendet +werden
DirectoryIndex + local-url [local-url] ... index.html svdhB
List of resources to look for when the client requests +a directory
<DirectoryMatch regex> +... </DirectoryMatch>svC
Umschließt eine Gruppe von Direktiven, die auf + Verzeichnisse des Dateisystems und ihre Unterverzeichnisse abgebildet + werden, welche auf einen regulären Ausdruck passen
DirectorySlash On|Off On svdhB
Toggle trailing slash redirects on or off
DocumentRoot Verzeichnis /usr/local/apache/h +svC
Verzeichnis, welches den Haupt-Dokumentenbaum bildet, der im +Web sichtbar ist.
DumpIOInput On|Off Off sE
Dump all input data to the error log
DumpIOOutput On|Off Off sE
Dump all output data to the error log
EnableExceptionHook On|Off Off sM
Aktiviert einen Hook, der nach einem Absturz noch +Ausnahmefehler behandeln lassen kann
EnableMMAP On|Off On svdhC
Verwende Memory-Mapping, um Dateien während der +Auslieferung zu lesen
EnableSendfile On|Off On svdhC
Verwende die sendfile-Unterstützung des Kernels, um +Dateien an den Client auszuliefern
ErrorDocument Fehlercode DokumentsvdhC
Das, was der Server im Fehlerfall an den Client +zurückgibt
ErrorLog Dateiname|syslog[:facility] logs/error_log (Uni +svC
Ablageort, an dem der Server Fehler protokolliert
ExamplesvdhX
Demonstration directive to illustrate the Apache module +API
ExpiresActive On|OffsvdhE
Enables generation of Expires +headers
ExpiresByType MIME-type +<code>secondssvdhE
Value of the Expires header configured +by MIME type
ExpiresDefault <code>secondssvdhE
Default algorithm for calculating expiration time
ExtendedStatus On|Off Off sB
Keep track of extended status information for each +request
ExtFilterDefine filtername parameterssE
Define an external filter
ExtFilterOptions option [option] ... DebugLevel=0 NoLogS +dE
Configure mod_ext_filter options
FileETag Komponente ... INode MTime Size svdhC
Dateiattribute, die zur Erstellung des HTTP-Response-Headers +ETag verwendet werden
<Files Dateiname> ... </Files>svdhC
Enthält Direktiven, die sich nur auf passende Dateinamen +beziehen
<FilesMatch regex> ... </FilesMatch>svdhC
Enthält Direktiven, die für Dateinamen gelten, die + auf einen regulären Ausdruck passen
FilterChain [+=-@!]filter-name ...svdhB
Configure the filter chain
FilterDeclare filter-name [type]svdhB
Declare a smart filter
FilterProtocol filter-name [provider-name] + proto-flagssvdhB
Deal with correct HTTP protocol handling
FilterProvider filter-name provider-name + [req|resp|env]=dispatch matchsvdhB
Register a content filter
FilterTrace filter-name levelsvdB
Get debug/diagnostic information from + mod_filter
ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback] Prefer svdhB
Action to take if a single acceptable document is not +found
ForceType MIME-Type|NonedhC
Erzwingt die Auslieferung aller passendenden Dateien mit dem +angegebenen MIME-Content-Type
ForensicLog filename|pipesvE
Sets filename of the forensic log
Group Unix-Gruppe #-1 sM
Benutzergruppe, unter welcher der Server Anfragen + beantwortet
Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]svdhE
Configure HTTP response headers
HeaderName filenamesvdhB
Name of the file that will be inserted at the top +of the index listing
HostnameLookups On|Off|Double Off svdC
Aktiviert DNS-Lookups auf Client-IP-Adressen
IdentityCheck On|Off Off svdE
Enables logging of the RFC 1413 identity of the remote +user
IdentityCheckTimeout seconds 30 svdE
Determines the timeout duration for ident requests
<IfDefine [!]Parametername> ... + </IfDefine>svdhC
Schließt Direktiven ein, die nur ausgeführt werden, +wenn eine Testbedingung beim Start wahr ist
<IfModule [!]Modulname|Modulbezeichner> + ... </IfModule>svdhC
Schließt Direktiven ein, die abhängig vom +Vorhandensein oder Fehlen eines speziellen Moduls ausgeführt +werden
<IfVersion [[!]operator] version> ... +</IfVersion>svdhE
contains version dependent configuration
ImapBase map|referer|URL http://servername/ svdhB
Default base for imagemap files
ImapDefault error|nocontent|map|referer|URL nocontent svdhB
Default action when an imagemap is called with coordinates +that are not explicitly mapped
ImapMenu none|formatted|semiformatted|unformattedsvdhB
Action if no coordinates are given when calling +an imagemap
Include Dateiname|VerzeichnissvdC
Fügt andere Konfigurationsdateien innerhalb der +Server-Konfigurationsdatei ein
IndexIgnore file [file] ...svdhB
Adds to the list of files to hide when listing +a directory
IndexOptions [+|-]option [[+|-]option] +...svdhB
Various configuration settings for directory +indexing
IndexOrderDefault Ascending|Descending +Name|Date|Size|Description Ascending Name svdhB
Sets the default ordering of the directory index
IndexStyleSheet url-pathsvdhB
Adds a CSS stylesheet to the directory index
ISAPIAppendLogToErrors on|off off svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the error log
ISAPIAppendLogToQuery on|off on svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the query field
ISAPICacheFile file-path [file-path] +...svB
ISAPI .dll files to be loaded at startup
ISAPIFakeAsync on|off off svdhB
Fake asynchronous support for ISAPI callbacks
ISAPILogNotSupported on|off off svdhB
Log unsupported feature requests from ISAPI +extensions
ISAPIReadAheadBuffer size 49152 svdhB
Size of the Read Ahead Buffer sent to ISAPI +extensions
KeepAlive On|Off On svC
Aktiviert persistente HTTP-Verbindungen
KeepAliveTimeout Sekunden 5 svC
Zeitspanne, die der Server während persistenter Verbindungen +auf nachfolgende Anfragen wartet
LanguagePriority MIME-lang [MIME-lang] +...svdhB
The precendence of language variants for cases where +the client does not express a preference
LDAPCacheEntries number 1024 sE
Maximum number of entries in the primary LDAP cache
LDAPCacheTTL seconds 600 sE
Time that cached items remain valid
LDAPConnectionTimeout secondssE
Specifies the socket connection timeout in seconds
LDAPOpCacheEntries number 1024 sE
Number of entries used to cache LDAP compare +operations
LDAPOpCacheTTL seconds 600 sE
Time that entries in the operation cache remain +valid
LDAPSharedCacheFile directory-path/filenamesE
Sets the shared memory cache file
LDAPSharedCacheSize bytes 102400 sE
Size in bytes of the shared-memory cache
LDAPTrustedClientCert type directory-path/filename/nickname [password]svdhE
Sets the file containing or nickname referring to a per +connection client certificate. Not all LDAP toolkits support per +connection client certificates.
LDAPTrustedGlobalCert type directory-path/filename [password]sE
Sets the file or database containing global trusted +Certificate Authority or global client certificates
LDAPTrustedMode typesvE
Specifies the SSL/TLS mode to be used when connecting to an LDAP server.
LDAPVerifyServerCert On|Off On sE
Force server certificate verification
<Limit Methode [Methode] ... > ... + </Limit>svdhC
Beschränkt die eingeschlossenen Zugriffskontrollen auf +bestimmte HTTP-Methoden
<LimitExcept Methode [Methode] ... > ... + </LimitExcept>svdhC
Beschränkt Zugriffskontrollen auf alle HTTP-Methoden +außer den genannten
LimitInternalRecursion Zahl [Zahl] 10 svC
Bestimmt die maximale Anzahl interner Umleitungen und + verschachtelter Unteranfragen
LimitRequestBody Bytes 0 svdhC
Begrenzt die Gesamtgröße des vom Client gesendeten +HTTP-Request-Body
LimitRequestFields Anzahl 100 sC
Begrenzt die Anzahl der HTTP-Request-Header, die vom Client +entgegengenommen werden
LimitRequestFieldsize BytessC
Begrenzt die Länge des vom Client gesendeten +HTTP-Request-Headers
LimitRequestLine Bytes 8190 sC
Begrenzt die Länge der vom Client entgegengenommenen +HTTP-Anfragezeile
LimitXMLRequestBody Bytes 1000000 svdhC
Begrenzt die Größe eines XML-basierten +Request-Bodys
Listen [IP-Addresse:]PortsM
IP-Adressen und Ports, an denen der Server lauscht
ListenBacklog backlogsM
Maximale Länge der Warteschlange schwebender + Verbindungen
LoadFile filename [filename] ...sE
Link in the named object file or library
LoadModule module filenamesE
Links in the object file or library, and adds to the list +of active modules
<Location + URL-Pfad|URL> ... </Location>svC
Wendet die enthaltenen Direktiven nur auf die entsprechenden +URLs an
<LocationMatch + regex> ... </LocationMatch>svC
Wendet die enthaltenen Direktiven nur auf URLs an, die auf +reguläre Ausdrücke passen
LockFile Dateiname logs/accept.lock sM
Ablageort der Lock-Datei für die Serialisierung von +entgegengenommenen Anfragen
LogFormat format|nickname +[nickname] "%h %l %u %t \"%r\" +svB
Describes a format for use in a log file
LogLevel Level warn svC
Steuert die Ausführlichkeit des Fehlerprotokolls
MaxClients AnzahlsM
Maximale Anzahl der Kindprozesse, die zur Bedienung von Anfragen + gestartet wird
MaxKeepAliveRequests Anzahl 100 svC
Anzahl der Anfragen, die bei einer persistenten Verbindung +zulässig sind
MaxMemFree KBytes 0 sM
Maximale Menge des Arbeitsspeichers, den die + Haupt-Zuteilungsroutine verwalten darf, ohne free() + aufzurufen
MaxRequestsPerChild number 10000 sM
Obergrenze für die Anzahl von Anfragen, die ein einzelner + Kindprozess während seines Lebens bearbeitet
MaxRequestsPerThread Anzahl 0 sM
Die maximale Anzahl von Anfragen, die ein einzelner Thread + während seiner Lebensdauer bedient.
MaxSpareServers Anzahl 10 sM
Maximale Anzahl der unbeschäftigten Kindprozesse des + Servers
MaxSpareThreads AnzahlsM
Maximale Anzahl unbeschäftigter Threads
MaxThreads number 2048 sM
Set the maximum number of worker threads
MCacheMaxObjectCount value 1009 sE
The maximum number of objects allowed to be placed in the +cache
MCacheMaxObjectSize bytes 10000 sE
The maximum size (in bytes) of a document allowed in the +cache
MCacheMaxStreamingBuffer size_in_bytes the smaller of 1000 +sE
Maximum amount of a streamed response to buffer in memory +before declaring the response uncacheable
MCacheMinObjectSize bytes 0 sE
The minimum size (in bytes) of a document to be allowed in the +cache
MCacheRemovalAlgorithm LRU|GDSF GDSF sE
The algorithm used to select documents for removal from the +cache
MCacheSize KBytes 100 sE
The maximum amount of memory used by the cache in +KBytes
MetaDir directory .web svdhE
Name of the directory to find CERN-style meta information +files
MetaFiles on|off off svdhE
Activates CERN meta-file processing
MetaSuffix suffix .meta svdhE
File name suffix for the file containg CERN-style +meta information
MimeMagicFile file-pathsvE
Enable MIME-type determination based on file contents +using the specified magic file
MinSpareServers Anzahl 5 sM
Minimale Anzahl der unbeschäftigten Kindprozesse des + Servers
MinSpareThreads AnzahlsM
Minimale Anzahl unbeschäftigter Threads, die zur + Bedienung von Anfragespitzen zur Verfügung stehen
MMapFile file-path [file-path] ...sX
Map a list of files into memory at startup time
ModMimeUsePathInfo On|Off Off dB
Tells mod_mime to treat path_info +components as part of the filename
MultiviewsMatch Any|NegotiatedOnly|Filters|Handlers +[Handlers|Filters] NegotiatedOnly svdhB
The types of files that will be included when searching for +a matching file with MultiViews
NameVirtualHost Adresse[:Port]sC
Bestimmt eine IP-Adresse für den Betrieb namensbasierter +virtueller Hosts
NoProxy host [host] ...svE
Hosts, domains, or networks that will be connected to +directly
NWSSLTrustedCerts filename [filename] ...sB
List of additional client certificates
NWSSLUpgradeable [IP-address:]portnumbersB
Allows a connection to be upgraded to an SSL connection upon request
Options + [+|-]Option [[+|-]Option] ... All svdhC
Definiert, welche Eigenschaften oder Funktionen in einem +bestimmten Verzeichnis verfügbar sind
Order ordering Deny,Allow dhB
Controls the default access state and the order in which +Allow and Deny are +evaluated.
PassEnv env-variable [env-variable] +...svdhB
Passes environment variables from the shell
PidFile Dateiname logs/httpd.pid sM
Datei, in welcher der Server die Prozess-ID des Daemons +ablegt
ProtocolEcho On|OffsvX
Turn the echo server on or off
<Proxy wildcard-url> ...</Proxy>svE
Container for directives applied to proxied resources
ProxyBadHeader IsError|Ignore|StartBody IsError svE
Determines how to handle bad header lines in a +response
ProxyBlock *|word|host|domain +[word|host|domain] ...svE
Words, hosts, or domains that are banned from being +proxied
ProxyDomain DomainsvE
Default domain name for proxied requests
ProxyErrorOverride On|Off Off svE
Override error pages for proxied content
ProxyIOBufferSize bytes 8192 svE
Determine size of internal data throughput buffer
<ProxyMatch regex> ...</ProxyMatch>svE
Container for directives applied to regular-expression-matched +proxied resources
ProxyMaxForwards number 10 svE
Maximium number of proxies that a request can be forwarded +through
ProxyPass [path] !|url [key=value key=value ...]]svdE
Maps remote servers into the local server URL-space
ProxyPassReverse [path] urlsvdE
Adjusts the URL in HTTP response headers sent from a reverse +proxied server
ProxyPassReverseCookieDomain internal-domain public-domainsvdE
Adjusts the Domain string in Set-Cookie headers from a reverse- +proxied server
ProxyPassReverseCookiePath internal-path public-pathsvdE
Adjusts the Path string in Set-Cookie headers from a reverse- +proxied server
ProxyPreserveHost On|Off Off svE
Use incoming Host HTTP request header for proxy +request
ProxyReceiveBufferSize bytes 0 svE
Network buffer size for proxied HTTP and FTP +connections
ProxyRemote match remote-serversvE
Remote proxy used to handle certain requests
ProxyRemoteMatch regex remote-serversvE
Remote proxy used to handle requests matched by regular +expressions
ProxyRequests On|Off Off svE
Enables forward (standard) proxy requests
ProxyTimeout seconds 300 svE
Network timeout for proxied requests
ProxyVia On|Off|Full|Block Off svE
Information provided in the Via HTTP response +header for proxied requests
ReadmeName filenamesvdhB
Name of the file that will be inserted at the end +of the index listing
Redirect [status] URL-path +URLsvdhB
Sends an external redirect asking the client to fetch +a different URL
RedirectMatch [status] regex +URLsvdhB
Sends an external redirect based on a regular expression match +of the current URL
RedirectPermanent URL-path URLsvdhB
Sends an external permanent redirect asking the client to fetch +a different URL
RedirectTemp URL-path URLsvdhB
Sends an external temporary redirect asking the client to fetch +a different URL
RemoveCharset extension [extension] +...vdhB
Removes any character set associations for a set of file +extensions
RemoveEncoding extension [extension] +...vdhB
Removes any content encoding associations for a set of file +extensions
RemoveHandler extension [extension] +...vdhB
Removes any handler associations for a set of file +extensions
RemoveInputFilter extension [extension] +...vdhB
Removes any input filter associations for a set of file +extensions
RemoveLanguage extension [extension] +...vdhB
Removes any language associations for a set of file +extensions
RemoveOutputFilter extension [extension] +...vdhB
Removes any output filter associations for a set of file +extensions
RemoveType extension [extension] +...vdhB
Removes any content type associations for a set of file +extensions
RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]svdhE
Configure HTTP request headers
Require Name [Name] ...dhC
Wählt die authentisierten Benutzer aus, die auf eine +Ressource zugreifen können
RewriteBase URL-pathdhE
Sets the base URL for per-directory rewrites
RewriteCond + TestString CondPatternsvdhE
Defines a condition under which rewriting will take place +
RewriteEngine on|off off svdhE
Enables or disables runtime rewriting engine
RewriteLock file-pathsE
Sets the name of the lock file used for RewriteMap +synchronization
RewriteLog file-pathsvE
Sets the name of the file used for logging rewrite engine +processing
RewriteLogLevel Level 0 svE
Sets the verbosity of the log file used by the rewrite +engine
RewriteMap MapName MapType:MapSource +svE
Defines a mapping function for key-lookup
RewriteOptions OptionssvdhE
Sets some special options for the rewrite engine
RewriteRule + Pattern SubstitutionsvdhE
Defines rules for the rewriting engine
RLimitCPU Sekunden|max [Sekunden|max]svdhC
Begrenzt den CPU-Verbrauch von Prozessen, die von +Apache-Kindprozessen gestartet wurden
RLimitMEM Bytes|max [Bytes|max]svdhC
Begrenzt den Speicherverbrauch von Prozessen, die von +Apache-Kindprozessen gestartet wurden
RLimitNPROC Zahl|max [Zahl|max]svdhC
Begrenzt die Anzahl der Prozesse, die von Prozessen gestartet +werden können, der ihrerseits von Apache-Kinprozessen gestartet +wurden
Satisfy Any|All All dhC
Zusammenspiel von rechnerbasierter Zugriffskontrolle und +Benutzerauthentisierung
ScoreBoardFile Dateipfad logs/apache_status sM
Ablageort der Datei, die zur Speicherung von Daten zur + Koordinierung der Kindprozesse verwendet wird
Script Methode CGI-SkriptsvdB
Aktiviert ein CGI-Skript für eine bestimmte + Anfragemethode.
ScriptAlias URL-path +file-path|directory-pathsvB
Maps a URL to a filesystem location and designates the +target as a CGI script
ScriptAliasMatch regex +file-path|directory-pathsvB
Maps a URL to a filesystem location using a regular expression +and designates the target as a CGI script
ScriptInterpreterSource Registry|Registry-Strict|Script Script svdhC
Methode zur Ermittlung des Interpreters von +CGI-Skripten
ScriptLog file-pathsvB
Location of the CGI script error logfile
ScriptLogBuffer bytes 1024 svB
Maximum amount of PUT or POST requests that will be recorded +in the scriptlog
ScriptLogLength bytes 10385760 svB
Size limit of the CGI script logfile
ScriptSock file-path logs/cgisock svB
The filename prefix of the socket to use for communication with +the cgi daemon
SecureListen [IP-address:]portnumber +Certificate-Name [MUTUAL]sB
Enables SSL encryption for the specified port
SendBufferSize Bytes 0 sM
Größe des TCP-Puffers
ServerAdmin E-Mail-Adresse|URLsvC
E-Mail-Adresse, die der Server in Fehlermeldungen einfügt, +welche an den Client gesendet werden
ServerAlias Hostname [Hostname] ...vC
Alternativer Name für einen Host, der verwendet wird, wenn +Anfragen einem namensbasierten virtuellen Host zugeordnet werden
ServerLimit AnzahlsM
Obergrenze für die konfigurierbare Anzahl von + Prozessen
ServerName +voll-qualifizierter-Domainname[:port]svC
Rechnername und Port, die der Server dazu verwendet, sich +selbst zu identifizieren
ServerPath URL-PfadvC
Veralteter URL-Pfad für einen namensbasierten +virtuellen Host, auf den von einem inkompatiblen Browser zugegriffen +wird
ServerRoot Verzeichnis /usr/local/apache sC
Basisverzeichnis der Serverinstallation
ServerSignature On|Off|EMail Off svdhC
Konfiguriert die Fußzeile von servergenerierten +Dokumenten
ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full Full sC
Konfiguriert den HTTP-Response-Header +Server
SetEnv env-variable valuesvdhB
Sets environment variables
SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables based on attributes of the request +
SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables based on attributes of the request +without respect to case
SetHandler Handlername|NonesvdhC
Erzwingt die Verarbeitung aller passenden Dateien durch +einen Handler
SetInputFilter Filter[;Filter...]svdhC
Bestimmt die Filter, die Client-Anfragen und POST-Eingaben +verarbeiten
SetOutputFilter Filter[;Filter...]svdhC
Bestimmt die Filter, die Antworten des Servers verarbeiten
SSIEndTag tag "-->" svB
String that ends an include element
SSIErrorMsg message "[an error occurred +svdhB
Error message displayed when there is an SSI +error
SSIStartTag tag "<!--#" svB
String that starts an include element
SSITimeFormat formatstring "%A, %d-%b-%Y %H:%M +svdhB
Configures the format in which date strings are +displayed
SSIUndefinedEcho string "(none)" svdhB
String displayed when an unset variable is echoed
SSLCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Client Auth
SSLCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Client Auth
SSLCADNRequestFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for defining acceptable CA names
SSLCADNRequestPath directory-pathsvE
Directory of PEM-encoded CA Certificates for +defining acceptable CA names
SSLCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Client Auth
SSLCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Client Auth
SSLCertificateChainFile file-pathsvE
File of PEM-encoded Server CA Certificates
SSLCertificateFile file-pathsvE
Server PEM-encoded X.509 Certificate file
SSLCertificateKeyFile file-pathsvE
Server PEM-encoded Private Key file
SSLCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +handshake
SSLCryptoDevice engine builtin sE
Enable use of a cryptographic hardware accelerator
SSLEngine on|off|optional off svE
SSL Engine Operation Switch
SSLHonorCiperOrder flagsvE
Option to prefer the server's cipher preference order
SSLMutex type none sE
Semaphore for internal mutual exclusion of +operations
SSLOptions [+|-]option ...svdhE
Configure various SSL engine run-time options
SSLPassPhraseDialog type builtin sE
Type of pass phrase dialog for encrypted private +keys
SSLProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors
SSLProxyCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Remote Server Auth
SSLProxyCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Remote Server Auth
SSLProxyCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +proxy handshake
SSLProxyEngine on|off off svE
SSL Proxy Engine Operation Switch
SSLProxyMachineCertificateFile filenamesE
File of concatenated PEM-encoded client certificates and keys to be used by the proxy
SSLProxyMachineCertificatePath directorysE
Directory of PEM-encoded client certificates and keys to be used by the proxy
SSLProxyProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors for proxy usage
SSLProxyVerify level none svdhE
Type of remote server Certificate verification
SSLProxyVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Remote Server +Certificate verification
SSLRandomSeed context source +[bytes]sE
Pseudo Random Number Generator (PRNG) seeding +source
SSLRequire expressiondhE
Allow access only when an arbitrarily complex +boolean expression is true
SSLRequireSSLdhE
Deny access when SSL is not used for the +HTTP request
SSLSessionCache type none sE
Type of the global/inter-process SSL Session +Cache
SSLSessionCacheTimeout seconds 300 svE
Number of seconds before an SSL session expires +in the Session Cache
SSLUserName varnamesdhE
Variable name to determine user name
SSLVerifyClient level none svdhE
Type of Client Certificate verification
SSLVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Client +Certificate verification
StartServers AnzahlsM
Anzahl der Kindprozesse des Servers, die beim Start erstellt + werden
StartThreads AnzahlsM
Anzahl der Threads, die beim Start erstellt werden
SuexecUserGroup User GroupsvE
User and group permissions for CGI programs
ThreadLimit AnzahlsM
Bestimmt die Obergrenze der konfigurierbaren Anzahl von Threads + pro Kindprozess
ThreadsPerChild AnzahlsM
Anzahl der Threads, die mit jedem Kindprozess gestartet + werden
ThreadStackSize sizesM
Die Größe des Stacks in Bytes, der von Threads +verwendet wird, die Client-Verbindungen bearbeiten.
TimeOut Sekunden 300 sC
Zeitspanne, die der Server auf verschiedene Ereignisse wartet, +bevor er die Anfrage abbricht
TransferLog file|pipesvB
Specify location of a log file
TypesConfig file-path conf/mime.types sB
The location of the mime.types file
UnsetEnv env-variable [env-variable] +...svdhB
Removes variables from the environment
UseCanonicalName On|Off|DNS Off svdC
Bestimmt, wie der Server seinen eigenen Namen und Port +ermittelt
User Unix-User-ID #-1 sM
Die Benutzerkennung, unter welcher der Server Anfragen + beantwortet
UserDir directory-filenamesvB
Location of the user-specific directories
VirtualDocumentRoot interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
VirtualDocumentRootIP interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
<VirtualHost + Adresse[:Port] [Adresse[:Port]] + ...> ... </VirtualHost>sC
Enthält Direktiven, die nur auf bestimmte Hostnamen oder +IP-Adressen angewendet werden
VirtualScriptAlias interpolated-directory|none none svE
Dynamically configure the location of the CGI directory for +a given virtual host
VirtualScriptAliasIP interpolated-directory|none none svE
Dynamically configure the location of the cgi directory for +a given virtual host
Win32DisableAcceptExsM
Für die Annahme von Netzwerkverbindungen wird accept() anstelle von AcceptEx() verwendet
XBitHack on|off|full off svdhB
Parse SSI directives in files with the execute bit +set
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/quickreference.html.en b/docs/manual/mod/quickreference.html.en new file mode 100644 index 00000000..0dd29910 --- /dev/null +++ b/docs/manual/mod/quickreference.html.en @@ -0,0 +1,753 @@ + + + +Directive Quick Reference - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+

Directive Quick Reference

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

The directive quick reference shows the usage, default, status, + and context of each Apache configuration directive. For more + information about each of these, see the Directive Dictionary.

+ +

The first column gives the directive name and usage. The second + columns shows the default value of the directive, if a default exists. + If the default is too large to display, the first characters will be + followed by "+".

+ +

The third and fourth columns list the contexts where the directive + is allowed and the status of the directive according to the legend + tables below.

+
+
+ + + +
 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X  + + + + + +
sserver config
vvirtual host
ddirectory
h.htaccess
 + + + + + + +
CCore
MMPM
BBase
EExtension
XExperimental
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
AcceptFilter protocol accept_filtersC
Configures optimizations for a Protocol's Listener Sockets
AcceptMutex Default|method Default sM
Method that Apache uses to serialize multiple children +accepting requests on network sockets
AcceptPathInfo On|Off|Default Default svdhC
Resources accept trailing pathname information
AccessFileName filename [filename] ... .htaccess svC
Name of the distributed configuration file
Action action-type cgi-script [virtual]svdhB
Activates a CGI script for a particular handler or +content-type
AddAlt string file [file] ...svdhB
Alternate text to display for a file, instead of an +icon selected by filename
AddAltByEncoding string MIME-encoding +[MIME-encoding] ...svdhB
Alternate text to display for a file instead of an icon +selected by MIME-encoding
AddAltByType string MIME-type +[MIME-type] ...svdhB
Alternate text to display for a file, instead of an +icon selected by MIME content-type
AddCharset charset extension +[extension] ...svdhB
Maps the given filename extensions to the specified content +charset
AddDefaultCharset On|Off|charset Off svdhC
Default charset parameter to be added when a response +content-type is text/plain or text/html
AddDescription string file [file] ...svdhB
Description to display for a file
AddEncoding MIME-enc extension +[extension] ...svdhB
Maps the given filename extensions to the specified encoding +type
AddHandler handler-name extension +[extension] ...svdhB
Maps the filename extensions to the specified +handler
AddIcon icon name [name] +...svdhB
Icon to display for a file selected by name
AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...svdhB
Icon to display next to files selected by MIME +content-encoding
AddIconByType icon MIME-type +[MIME-type] ...svdhB
Icon to display next to files selected by MIME +content-type
AddInputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +client requests
AddLanguage MIME-lang extension +[extension] ...svdhB
Maps the given filename extension to the specified content +language
AddModuleInfo module-name stringsvE
Adds additional information to the module +information displayed by the server-info handler
AddOutputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +responses from the server
AddOutputFilterByType filter[;filter...] +MIME-type [MIME-type] ...svdhC
assigns an output filter to a particular MIME-type
AddType MIME-type extension +[extension] ...svdhB
Maps the given filename extensions onto the specified content +type
Alias URL-path +file-path|directory-pathsvB
Maps URLs to filesystem locations
AliasMatch regex +file-path|directory-pathsvB
Maps URLs to filesystem locations using regular +expressions
Allow from all|host|env=env-variable +[host|env=env-variable] ...dhB
Controls which hosts can access an area of the +server
AllowCONNECT port [port] ... 443 563 svE
Ports that are allowed to CONNECT through the +proxy
AllowEncodedSlashes On|Off Off svC
Determines whether encoded path separators in URLs are allowed to +be passed through
AllowOverride All|None|directive-type +[directive-type] ... All dC
Types of directives that are allowed in +.htaccess files
Anonymous user [user] ...dhE
Specifies userIDs that are allowed access without +password verification
Anonymous_LogEmail On|Off On dhE
Sets whether the password entered will be logged in the +error log
Anonymous_MustGiveEmail On|Off On dhE
Specifies whether blank passwords are allowed
Anonymous_NoUserID On|Off Off dhE
Sets whether the userID field may be empty
Anonymous_VerifyEmail On|Off Off dhE
Sets whether to check the password field for a correctly +formatted email address
AuthBasicAuthoritative On|Off On dhB
Sets whether authorization and authentication are passed to +lower level modules
AuthBasicProvider provider-name +[provider-name] ... file dhB
Sets the authentication provider(s) for this location
AuthDBDUserPWQuery querydE
SQL query to look up a password for a user
AuthDBDUserRealmQuery querydE
SQL query to look up a password hash for a user and realm. +
AuthDBMGroupFile file-pathdhE
Sets the name of the database file containing the list +of user groups for authorization
AuthDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store passwords
AuthDBMUserFile file-pathdhE
Sets the name of a database file containing the list of users and +passwords for authentication
AuthDefaultAuthoritative On|Off On dhB
Sets whether authentication is passed to lower level +modules
AuthDigestAlgorithm MD5|MD5-sess MD5 dhX
Selects the algorithm used to calculate the challenge and +response hashes in digest authentication
AuthDigestDomain URI [URI] ...dhX
URIs that are in the same protection space for digest +authentication
AuthDigestNcCheck On|Off Off sX
Enables or disables checking of the nonce-count sent by the +server
AuthDigestNonceFormat formatdhX
Determines how the nonce is generated
AuthDigestNonceLifetime seconds 300 dhX
How long the server nonce is valid
AuthDigestProvider provider-name +[provider-name] ... file dhX
Sets the authentication provider(s) for this location
AuthDigestQop none|auth|auth-int [auth|auth-int] auth dhX
Determines the quality-of-protection to use in digest +authentication
AuthDigestShmemSize size 1000 sX
The amount of shared memory to allocate for keeping track +of clients
AuthGroupFile file-pathdhB
Sets the name of a text file containing the list +of user groups for authorization
AuthLDAPBindDN distinguished-namedhE
Optional DN to use in binding to the LDAP server
AuthLDAPBindPassword passworddhE
Password used in conjuction with the bind DN
AuthLDAPCharsetConfig file-pathsE
Language to charset conversion configuration file
AuthLDAPCompareDNOnServer on|off on dhE
Use the LDAP server to compare the DNs
AuthLDAPDereferenceAliases never|searching|finding|always Always dhE
When will the module de-reference aliases
AuthLDAPGroupAttribute attributedhE
LDAP attributes used to check for group membership
AuthLDAPGroupAttributeIsDN on|off on dhE
Use the DN of the client username when checking for +group membership
AuthLDAPRemoteUserIsDN on|off off dhE
Use the DN of the client username to set the REMOTE_USER +environment variable
AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]dhE
URL specifying the LDAP search parameters
AuthName auth-domaindhC
Authorization realm for use in HTTP +authentication
<AuthnProviderAlias baseProvider Alias> +... </AuthnProviderAlias>svE
Enclose a group of directives that represent an +extension of a base authentication provider and referenced by +the specified alias
AuthType Basic|DigestdhC
Type of user authentication
AuthUserFile file-pathdhB
Sets the name of a text file containing the list of users and +passwords for authentication
AuthzDBMAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store list of user groups
AuthzDefaultAuthoritative On|Off On dhB
Sets whether authorization is passed to lower level +modules
AuthzGroupFileAuthoritative On|Off On dhB
Sets whether authorization will be passed on to lower level +modules
AuthzLDAPAuthoritative on|off on dhE
Prevent other authentication modules from +authenticating the user if this one fails
AuthzOwnerAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzUserAuthoritative On|Off On dhB
Sets whether authorization will be passed on to lower level +modules
BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...svdhB
Sets environment variables conditional on HTTP User-Agent +
BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables conditional on User-Agent without +respect to case
BufferedLogs On|Off Off sB
Buffer log entries in memory before writing to disk
CacheDefaultExpire seconds 3600 (one hour) svE
The default duration to cache a document when no expiry date is specified.
CacheDirLength length 2 svE
The number of characters in subdirectory names
CacheDirLevels levels 3 svE
The number of levels of subdirectories in the +cache.
CacheDisable url-stringsvE
Disable caching of specified URLs
CacheEnable cache_type url-stringsvE
Enable caching of specified URLs using a specified storage +manager
CacheFile file-path [file-path] ...sX
Cache a list of file handles at startup time
CacheIgnoreCacheControl On|Off Off svE
Ignore request to not serve cached content to client
CacheIgnoreHeaders header-string [header-string] ... None svE
Do not store the given HTTP header(s) in the cache. +
CacheIgnoreNoLastMod On|Off Off svE
Ignore the fact that a response has no Last Modified +header.
CacheLastModifiedFactor float 0.1 svE
The factor used to compute an expiry date based on the +LastModified date.
CacheMaxExpire seconds 86400 (one day) svE
The maximum time in seconds to cache a document
CacheMaxFileSize bytes 1000000 svE
The maximum size (in bytes) of a document to be placed in the +cache
CacheMinFileSize bytes 1 svE
The minimum size (in bytes) of a document to be placed in the +cache
CacheNegotiatedDocs On|Off Off svB
Allows content-negotiated documents to be +cached by proxy servers
CacheRoot directorysvE
The directory root under which cache files are +stored
CacheStoreNoStore On|Off Off svE
Attempt to cache requests or responses that have been marked as no-store.
CacheStorePrivate On|Off Off svE
Attempt to cache responses that the server has marked as private
CGIMapExtension cgi-path .extensiondhC
Technique for locating the interpreter for CGI +scripts
CharsetDefault charsetsvdhX
Charset to translate into
CharsetOptions option [option] ... DebugLevel=0 NoImpl +svdhX
Configures charset translation behavior
CharsetSourceEnc charsetsvdhX
Source charset of files
CheckSpelling on|off Off svdhE
Enables the spelling +module
ContentDigest On|Off Off svdhC
Enables the generation of Content-MD5 HTTP Response +headers
CookieDomain domainsvdhE
The domain to which the tracking cookie applies
CookieExpires expiry-periodsvdhE
Expiry time for the tracking cookie
CookieLog filenamesvB
Sets filename for the logging of cookies
CookieName token Apache svdhE
Name of the tracking cookie
CookieStyle + Netscape|Cookie|Cookie2|RFC2109|RFC2965 Netscape svdhE
Format of the cookie header field
CookieTracking on|off off svdhE
Enables tracking cookie
CoreDumpDirectory directorysM
Directory where Apache attempts to +switch before dumping core
CustomLog file|pipe +format|nickname +[env=[!]environment-variable]svB
Sets filename and format of log file
Dav On|Off|provider-name Off dE
Enable WebDAV HTTP methods
DavDepthInfinity on|off off svdE
Allow PROPFIND, Depth: Infinity requests
DavGenericLockDB file-pathsvdE
Location of the DAV lock database
DavLockDB file-pathsvE
Location of the DAV lock database
DavMinTimeout seconds 0 svdE
Minimum amount of time the server holds a lock on +a DAV resource
DBDExptime time-in-secondssvE
Keepalive time for idle connections
DBDKeep numbersvE
Maximum sustained number of connections
DBDMax numbersvE
Maximum number of connections
DBDMin numbersvE
Minimum number of connections
DBDParams +param1=value1[,param2=value2]svE
Parameters for database connection
DBDPersist 0|1svE
Whether to use persistent connections
DBDPrepareSQL "SQL statement" labelsvE
Define an SQL prepared statement
DBDriver namesvE
Specify an SQL driver
DefaultIcon url-pathsvdhB
Icon to display for files when no specific icon is +configured
DefaultLanguage MIME-langsvdhB
Sets all files in the given scope to the specified +language
DefaultType MIME-type text/plain svdhC
MIME content-type that will be sent if the +server cannot determine a type in any other way
DeflateBufferSize value 8096 svE
Fragment size to be compressed at one time by zlib
DeflateCompressionLevel valuesvE
How much compression do we apply to the output
DeflateFilterNote [type] notenamesvE
Places the compression ratio in a note for logging
DeflateMemLevel value 9 svE
How much memory should be used by zlib for compression
DeflateWindowSize value 15 svE
Zlib compression window size
Deny from all|host|env=env-variable +[host|env=env-variable] ...dhB
Controls which hosts are denied access to the +server
<Directory directory-path> +... </Directory>svC
Enclose a group of directives that apply only to the +named file-system directory and sub-directories
DirectoryIndex + local-url [local-url] ... index.html svdhB
List of resources to look for when the client requests +a directory
<DirectoryMatch regex> +... </DirectoryMatch>svC
Enclose directives that apply to +file-system directories matching a regular expression and their +subdirectories
DirectorySlash On|Off On svdhB
Toggle trailing slash redirects on or off
DocumentRoot directory-path /usr/local/apache/h +svC
Directory that forms the main document tree visible +from the web
DumpIOInput On|Off Off sE
Dump all input data to the error log
DumpIOOutput On|Off Off sE
Dump all output data to the error log
EnableExceptionHook On|Off Off sM
Enables a hook that runs exception handlers +after a crash
EnableMMAP On|Off On svdhC
Use memory-mapping to read files during delivery
EnableSendfile On|Off On svdhC
Use the kernel sendfile support to deliver files to the client
ErrorDocument error-code documentsvdhC
What the server will return to the client +in case of an error
ErrorLog file-path|syslog[:facility] logs/error_log (Uni +svC
Location where the server will log errors
ExamplesvdhX
Demonstration directive to illustrate the Apache module +API
ExpiresActive On|OffsvdhE
Enables generation of Expires +headers
ExpiresByType MIME-type +<code>secondssvdhE
Value of the Expires header configured +by MIME type
ExpiresDefault <code>secondssvdhE
Default algorithm for calculating expiration time
ExtendedStatus On|Off Off sB
Keep track of extended status information for each +request
ExtFilterDefine filtername parameterssE
Define an external filter
ExtFilterOptions option [option] ... DebugLevel=0 NoLogS +dE
Configure mod_ext_filter options
FileETag component ... INode MTime Size svdhC
File attributes used to create the ETag +HTTP response header
<Files filename> ... </Files>svdhC
Contains directives that apply to matched +filenames
<FilesMatch regex> ... </FilesMatch>svdhC
Contains directives that apply to regular-expression matched +filenames
FilterChain [+=-@!]filter-name ...svdhB
Configure the filter chain
FilterDeclare filter-name [type]svdhB
Declare a smart filter
FilterProtocol filter-name [provider-name] + proto-flagssvdhB
Deal with correct HTTP protocol handling
FilterProvider filter-name provider-name + [req|resp|env]=dispatch matchsvdhB
Register a content filter
FilterTrace filter-name levelsvdB
Get debug/diagnostic information from + mod_filter
ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback] Prefer svdhB
Action to take if a single acceptable document is not +found
ForceType MIME-type|NonedhC
Forces all matching files to be served with the specified +MIME content-type
ForensicLog filename|pipesvE
Sets filename of the forensic log
GracefulShutDownTimeout secondssM
Specify a timeout after which a gracefully shutdown server +will exit.
Group unix-group #-1 sM
Group under which the server will answer +requests
Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]svdhE
Configure HTTP response headers
HeaderName filenamesvdhB
Name of the file that will be inserted at the top +of the index listing
HostnameLookups On|Off|Double Off svdC
Enables DNS lookups on client IP addresses
IdentityCheck On|Off Off svdE
Enables logging of the RFC 1413 identity of the remote +user
IdentityCheckTimeout seconds 30 svdE
Determines the timeout duration for ident requests
<IfDefine [!]parameter-name> ... + </IfDefine>svdhC
Encloses directives that will be processed only +if a test is true at startup
<IfModule [!]module-file|module-identifier> ... + </IfModule>svdhC
Encloses directives that are processed conditional on the +presence or absence of a specific module
<IfVersion [[!]operator] version> ... +</IfVersion>svdhE
contains version dependent configuration
ImapBase map|referer|URL http://servername/ svdhB
Default base for imagemap files
ImapDefault error|nocontent|map|referer|URL nocontent svdhB
Default action when an imagemap is called with coordinates +that are not explicitly mapped
ImapMenu none|formatted|semiformatted|unformattedsvdhB
Action if no coordinates are given when calling +an imagemap
Include file-path|directory-pathsvdC
Includes other configuration files from within +the server configuration files
IndexIgnore file [file] ...svdhB
Adds to the list of files to hide when listing +a directory
IndexOptions [+|-]option [[+|-]option] +...svdhB
Various configuration settings for directory +indexing
IndexOrderDefault Ascending|Descending +Name|Date|Size|Description Ascending Name svdhB
Sets the default ordering of the directory index
IndexStyleSheet url-pathsvdhB
Adds a CSS stylesheet to the directory index
ISAPIAppendLogToErrors on|off off svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the error log
ISAPIAppendLogToQuery on|off on svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the query field
ISAPICacheFile file-path [file-path] +...svB
ISAPI .dll files to be loaded at startup
ISAPIFakeAsync on|off off svdhB
Fake asynchronous support for ISAPI callbacks
ISAPILogNotSupported on|off off svdhB
Log unsupported feature requests from ISAPI +extensions
ISAPIReadAheadBuffer size 49152 svdhB
Size of the Read Ahead Buffer sent to ISAPI +extensions
KeepAlive On|Off On svC
Enables HTTP persistent connections
KeepAliveTimeout seconds 5 svC
Amount of time the server will wait for subsequent +requests on a persistent connection
LanguagePriority MIME-lang [MIME-lang] +...svdhB
The precendence of language variants for cases where +the client does not express a preference
LDAPCacheEntries number 1024 sE
Maximum number of entries in the primary LDAP cache
LDAPCacheTTL seconds 600 sE
Time that cached items remain valid
LDAPConnectionTimeout secondssE
Specifies the socket connection timeout in seconds
LDAPOpCacheEntries number 1024 sE
Number of entries used to cache LDAP compare +operations
LDAPOpCacheTTL seconds 600 sE
Time that entries in the operation cache remain +valid
LDAPSharedCacheFile directory-path/filenamesE
Sets the shared memory cache file
LDAPSharedCacheSize bytes 102400 sE
Size in bytes of the shared-memory cache
LDAPTrustedClientCert type directory-path/filename/nickname [password]svdhE
Sets the file containing or nickname referring to a per +connection client certificate. Not all LDAP toolkits support per +connection client certificates.
LDAPTrustedGlobalCert type directory-path/filename [password]sE
Sets the file or database containing global trusted +Certificate Authority or global client certificates
LDAPTrustedMode typesvE
Specifies the SSL/TLS mode to be used when connecting to an LDAP server.
LDAPVerifyServerCert On|Off On sE
Force server certificate verification
<Limit method [method] ... > ... + </Limit>svdhC
Restrict enclosed access controls to only certain HTTP +methods
<LimitExcept method [method] ... > ... + </LimitExcept>svdhC
Restrict access controls to all HTTP methods +except the named ones
LimitInternalRecursion number [number] 10 svC
Determine maximum number of internal redirects and nested +subrequests
LimitRequestBody bytes 0 svdhC
Restricts the total size of the HTTP request body sent +from the client
LimitRequestFields number 100 sC
Limits the number of HTTP request header fields that +will be accepted from the client
LimitRequestFieldsize bytessC
Limits the size of the HTTP request header allowed from the +client
LimitRequestLine bytes 8190 sC
Limit the size of the HTTP request line that will be accepted +from the client
LimitXMLRequestBody bytes 1000000 svdhC
Limits the size of an XML-based request body
Listen [IP-address:]portnumber [protocol]sM
IP addresses and ports that the server +listens to
ListenBacklog backlogsM
Maximum length of the queue of pending connections
LoadFile filename [filename] ...sE
Link in the named object file or library
LoadModule module filenamesE
Links in the object file or library, and adds to the list +of active modules
<Location + URL-path|URL> ... </Location>svC
Applies the enclosed directives only to matching +URLs
<LocationMatch + regex> ... </LocationMatch>svC
Applies the enclosed directives only to regular-expression +matching URLs
LockFile filename logs/accept.lock sM
Location of the accept serialization lock file
LogFormat format|nickname +[nickname] "%h %l %u %t \"%r\" +svB
Describes a format for use in a log file
LogLevel level warn svC
Controls the verbosity of the ErrorLog
MaxClients numbersM
Maximum number of child processes that will be created +to serve requests
MaxKeepAliveRequests number 100 svC
Number of requests allowed on a persistent +connection
MaxMemFree KBytes 0 sM
Maximum amount of memory that the main allocator is allowed +to hold without calling free()
MaxRequestsPerChild number 10000 sM
Limit on the number of requests that an individual child server +will handle during its life
MaxRequestsPerThread number 0 sM
Limit on the number of requests that an individual thread +will handle during its life
MaxSpareServers number 10 sM
Maximum number of idle child server processes
MaxSpareThreads numbersM
Maximum number of idle threads
MaxThreads number 2048 sM
Set the maximum number of worker threads
MCacheMaxObjectCount value 1009 sE
The maximum number of objects allowed to be placed in the +cache
MCacheMaxObjectSize bytes 10000 sE
The maximum size (in bytes) of a document allowed in the +cache
MCacheMaxStreamingBuffer size_in_bytes the smaller of 1000 +sE
Maximum amount of a streamed response to buffer in memory +before declaring the response uncacheable
MCacheMinObjectSize bytes 0 sE
The minimum size (in bytes) of a document to be allowed in the +cache
MCacheRemovalAlgorithm LRU|GDSF GDSF sE
The algorithm used to select documents for removal from the +cache
MCacheSize KBytes 100 sE
The maximum amount of memory used by the cache in +KBytes
MetaDir directory .web svdhE
Name of the directory to find CERN-style meta information +files
MetaFiles on|off off svdhE
Activates CERN meta-file processing
MetaSuffix suffix .meta svdhE
File name suffix for the file containg CERN-style +meta information
MimeMagicFile file-pathsvE
Enable MIME-type determination based on file contents +using the specified magic file
MinSpareServers number 5 sM
Minimum number of idle child server processes
MinSpareThreads numbersM
Minimum number of idle threads available to handle request +spikes
MMapFile file-path [file-path] ...sX
Map a list of files into memory at startup time
ModMimeUsePathInfo On|Off Off dB
Tells mod_mime to treat path_info +components as part of the filename
MultiviewsMatch Any|NegotiatedOnly|Filters|Handlers +[Handlers|Filters] NegotiatedOnly svdhB
The types of files that will be included when searching for +a matching file with MultiViews
NameVirtualHost addr[:port]sC
Designates an IP address for name-virtual +hosting
NoProxy host [host] ...svE
Hosts, domains, or networks that will be connected to +directly
NWSSLTrustedCerts filename [filename] ...sB
List of additional client certificates
NWSSLUpgradeable [IP-address:]portnumbersB
Allows a connection to be upgraded to an SSL connection upon request
Options + [+|-]option [[+|-]option] ... All svdhC
Configures what features are available in a particular +directory
Order ordering Deny,Allow dhB
Controls the default access state and the order in which +Allow and Deny are +evaluated.
PassEnv env-variable [env-variable] +...svdhB
Passes environment variables from the shell
PidFile filename logs/httpd.pid sM
File where the server records the process ID +of the daemon
ProtocolEcho On|OffsvX
Turn the echo server on or off
<Proxy wildcard-url> ...</Proxy>svE
Container for directives applied to proxied resources
ProxyBadHeader IsError|Ignore|StartBody IsError svE
Determines how to handle bad header lines in a +response
ProxyBlock *|word|host|domain +[word|host|domain] ...svE
Words, hosts, or domains that are banned from being +proxied
ProxyDomain DomainsvE
Default domain name for proxied requests
ProxyErrorOverride On|Off Off svE
Override error pages for proxied content
ProxyIOBufferSize bytes 8192 svE
Determine size of internal data throughput buffer
<ProxyMatch regex> ...</ProxyMatch>svE
Container for directives applied to regular-expression-matched +proxied resources
ProxyMaxForwards number 10 svE
Maximium number of proxies that a request can be forwarded +through
ProxyPass [path] !|url [key=value key=value ...]]svdE
Maps remote servers into the local server URL-space
ProxyPassReverse [path] urlsvdE
Adjusts the URL in HTTP response headers sent from a reverse +proxied server
ProxyPassReverseCookieDomain internal-domain public-domainsvdE
Adjusts the Domain string in Set-Cookie headers from a reverse- +proxied server
ProxyPassReverseCookiePath internal-path public-pathsvdE
Adjusts the Path string in Set-Cookie headers from a reverse- +proxied server
ProxyPreserveHost On|Off Off svE
Use incoming Host HTTP request header for proxy +request
ProxyReceiveBufferSize bytes 0 svE
Network buffer size for proxied HTTP and FTP +connections
ProxyRemote match remote-serversvE
Remote proxy used to handle certain requests
ProxyRemoteMatch regex remote-serversvE
Remote proxy used to handle requests matched by regular +expressions
ProxyRequests On|Off Off svE
Enables forward (standard) proxy requests
ProxyTimeout seconds 300 svE
Network timeout for proxied requests
ProxyVia On|Off|Full|Block Off svE
Information provided in the Via HTTP response +header for proxied requests
ReadmeName filenamesvdhB
Name of the file that will be inserted at the end +of the index listing
ReceiveBufferSize bytes 0 sM
TCP receive buffer size
Redirect [status] URL-path +URLsvdhB
Sends an external redirect asking the client to fetch +a different URL
RedirectMatch [status] regex +URLsvdhB
Sends an external redirect based on a regular expression match +of the current URL
RedirectPermanent URL-path URLsvdhB
Sends an external permanent redirect asking the client to fetch +a different URL
RedirectTemp URL-path URLsvdhB
Sends an external temporary redirect asking the client to fetch +a different URL
RemoveCharset extension [extension] +...vdhB
Removes any character set associations for a set of file +extensions
RemoveEncoding extension [extension] +...vdhB
Removes any content encoding associations for a set of file +extensions
RemoveHandler extension [extension] +...vdhB
Removes any handler associations for a set of file +extensions
RemoveInputFilter extension [extension] +...vdhB
Removes any input filter associations for a set of file +extensions
RemoveLanguage extension [extension] +...vdhB
Removes any language associations for a set of file +extensions
RemoveOutputFilter extension [extension] +...vdhB
Removes any output filter associations for a set of file +extensions
RemoveType extension [extension] +...vdhB
Removes any content type associations for a set of file +extensions
RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]svdhE
Configure HTTP request headers
Require entity-name [entity-name] ...dhC
Selects which authenticated users can access +a resource
RewriteBase URL-pathdhE
Sets the base URL for per-directory rewrites
RewriteCond + TestString CondPatternsvdhE
Defines a condition under which rewriting will take place +
RewriteEngine on|off off svdhE
Enables or disables runtime rewriting engine
RewriteLock file-pathsE
Sets the name of the lock file used for RewriteMap +synchronization
RewriteLog file-pathsvE
Sets the name of the file used for logging rewrite engine +processing
RewriteLogLevel Level 0 svE
Sets the verbosity of the log file used by the rewrite +engine
RewriteMap MapName MapType:MapSource +svE
Defines a mapping function for key-lookup
RewriteOptions OptionssvdhE
Sets some special options for the rewrite engine
RewriteRule + Pattern SubstitutionsvdhE
Defines rules for the rewriting engine
RLimitCPU seconds|max [seconds|max]svdhC
Limits the CPU consumption of processes launched +by Apache children
RLimitMEM bytes|max [bytes|max]svdhC
Limits the memory consumption of processes launched +by Apache children
RLimitNPROC number|max [number|max]svdhC
Limits the number of processes that can be launched by +processes launched by Apache children
Satisfy Any|All All dhC
Interaction between host-level access control and +user authentication
ScoreBoardFile file-path logs/apache_status sM
Location of the file used to store coordination data for +the child processes
Script method cgi-scriptsvdB
Activates a CGI script for a particular request +method.
ScriptAlias URL-path +file-path|directory-pathsvB
Maps a URL to a filesystem location and designates the +target as a CGI script
ScriptAliasMatch regex +file-path|directory-pathsvB
Maps a URL to a filesystem location using a regular expression +and designates the target as a CGI script
ScriptInterpreterSource Registry|Registry-Strict|Script Script svdhC
Technique for locating the interpreter for CGI +scripts
ScriptLog file-pathsvB
Location of the CGI script error logfile
ScriptLogBuffer bytes 1024 svB
Maximum amount of PUT or POST requests that will be recorded +in the scriptlog
ScriptLogLength bytes 10385760 svB
Size limit of the CGI script logfile
ScriptSock file-path logs/cgisock sB
The filename prefix of the socket to use for communication with +the cgi daemon
SecureListen [IP-address:]portnumber +Certificate-Name [MUTUAL]sB
Enables SSL encryption for the specified port
SendBufferSize bytes 0 sM
TCP buffer size
ServerAdmin email-address|URLsvC
Email address that the server includes in error +messages sent to the client
ServerAlias hostname [hostname] ...vC
Alternate names for a host used when matching requests +to name-virtual hosts
ServerLimit numbersM
Upper limit on configurable number of processes
ServerName [scheme://]fully-qualified-domain-name[:port]svC
Hostname and port that the server uses to identify +itself
ServerPath URL-pathvC
Legacy URL pathname for a name-based virtual host that +is accessed by an incompatible browser
ServerRoot directory-path /usr/local/apache sC
Base directory for the server installation
ServerSignature On|Off|EMail Off svdhC
Configures the footer on server-generated documents
ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full Full sC
Configures the Server HTTP response +header
SetEnv env-variable valuesvdhB
Sets environment variables
SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables based on attributes of the request +
SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables based on attributes of the request +without respect to case
SetHandler handler-name|NonesvdhC
Forces all matching files to be processed by a +handler
SetInputFilter filter[;filter...]svdhC
Sets the filters that will process client requests and POST +input
SetOutputFilter filter[;filter...]svdhC
Sets the filters that will process responses from the +server
SSIEndTag tag "-->" svB
String that ends an include element
SSIErrorMsg message "[an error occurred +svdhB
Error message displayed when there is an SSI +error
SSIStartTag tag "<!--#" svB
String that starts an include element
SSITimeFormat formatstring "%A, %d-%b-%Y %H:%M +svdhB
Configures the format in which date strings are +displayed
SSIUndefinedEcho string "(none)" svdhB
String displayed when an unset variable is echoed
SSLCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Client Auth
SSLCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Client Auth
SSLCADNRequestFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for defining acceptable CA names
SSLCADNRequestPath directory-pathsvE
Directory of PEM-encoded CA Certificates for +defining acceptable CA names
SSLCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Client Auth
SSLCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Client Auth
SSLCertificateChainFile file-pathsvE
File of PEM-encoded Server CA Certificates
SSLCertificateFile file-pathsvE
Server PEM-encoded X.509 Certificate file
SSLCertificateKeyFile file-pathsvE
Server PEM-encoded Private Key file
SSLCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +handshake
SSLCryptoDevice engine builtin sE
Enable use of a cryptographic hardware accelerator
SSLEngine on|off|optional off svE
SSL Engine Operation Switch
SSLHonorCiperOrder flagsvE
Option to prefer the server's cipher preference order
SSLMutex type none sE
Semaphore for internal mutual exclusion of +operations
SSLOptions [+|-]option ...svdhE
Configure various SSL engine run-time options
SSLPassPhraseDialog type builtin sE
Type of pass phrase dialog for encrypted private +keys
SSLProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors
SSLProxyCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Remote Server Auth
SSLProxyCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Remote Server Auth
SSLProxyCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +proxy handshake
SSLProxyEngine on|off off svE
SSL Proxy Engine Operation Switch
SSLProxyMachineCertificateFile filenamesE
File of concatenated PEM-encoded client certificates and keys to be used by the proxy
SSLProxyMachineCertificatePath directorysE
Directory of PEM-encoded client certificates and keys to be used by the proxy
SSLProxyProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors for proxy usage
SSLProxyVerify level none svdhE
Type of remote server Certificate verification
SSLProxyVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Remote Server +Certificate verification
SSLRandomSeed context source +[bytes]sE
Pseudo Random Number Generator (PRNG) seeding +source
SSLRequire expressiondhE
Allow access only when an arbitrarily complex +boolean expression is true
SSLRequireSSLdhE
Deny access when SSL is not used for the +HTTP request
SSLSessionCache type none sE
Type of the global/inter-process SSL Session +Cache
SSLSessionCacheTimeout seconds 300 svE
Number of seconds before an SSL session expires +in the Session Cache
SSLUserName varnamesdhE
Variable name to determine user name
SSLVerifyClient level none svdhE
Type of Client Certificate verification
SSLVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Client +Certificate verification
StartServers numbersM
Number of child server processes created at startup
StartThreads numbersM
Number of threads created on startup
SuexecUserGroup User GroupsvE
User and group permissions for CGI programs
ThreadLimit numbersM
Sets the upper limit on the configurable number of threads +per child process
ThreadsPerChild numbersM
Number of threads created by each child process
ThreadStackSize sizesM
The size in bytes of the stack used by threads handling +client connections
TimeOut seconds 300 sC
Amount of time the server will wait for +certain events before failing a request
TraceEnable [on|off|extended] on sC
Determines the behaviour on TRACE +requests
TransferLog file|pipesvB
Specify location of a log file
TypesConfig file-path conf/mime.types sB
The location of the mime.types file
UnsetEnv env-variable [env-variable] +...svdhB
Removes variables from the environment
UseCanonicalName On|Off|DNS Off svdC
Configures how the server determines its own name and +port
UseCanonicalPhysicalPort On|Off Off svdC
Configures how the server determines its own name and +port
User unix-userid #-1 sM
The userid under which the server will answer +requests
UserDir directory-filenamesvB
Location of the user-specific directories
VirtualDocumentRoot interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
VirtualDocumentRootIP interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
<VirtualHost + addr[:port] [addr[:port]] + ...> ... </VirtualHost>sC
Contains directives that apply only to a specific +hostname or IP address
VirtualScriptAlias interpolated-directory|none none svE
Dynamically configure the location of the CGI directory for +a given virtual host
VirtualScriptAliasIP interpolated-directory|none none svE
Dynamically configure the location of the cgi directory for +a given virtual host
Win32DisableAcceptExsM
Use accept() rather than AcceptEx() to accept network connections
XBitHack on|off|full off svdhB
Parse SSI directives in files with the execute bit +set
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/quickreference.html.es b/docs/manual/mod/quickreference.html.es new file mode 100644 index 00000000..3fc00c0b --- /dev/null +++ b/docs/manual/mod/quickreference.html.es @@ -0,0 +1,756 @@ + + + +Guía Rápida de Referencia de Directivas - Servidor HTTP Apache + + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2 > Módulos
+

Guía Rápida de Referencia de Directivas

+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

La Guía Rápida de Referencia de Directivas muestra el uso, las + opciones por defecto, el estado y el contexto de cada directiva de + configuración de Apache. Para más información sobre cada + directiva, consulte el Diccionario + de Directivas.

+ +

La primera columna muestra el nombre y el uso de la directiva. + La segunda columna muestra el valor por defecto de la directiva, + si existe ese valor por defecto. Si el valor por defecto es + demasiado largo para mostrarlo, el primer caracter va seguido de + un signo "+".

+ +

La tercera y la cuarta columna listan los contextos en los que + la directiva puede funcionar y el estado de la directiva de + acuerdo con las notas que detallan más abajo.

+
+
+ + + +
 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X  + + + + + +
sserver config
vvirtual host
ddirectory
h.htaccess
 + + + + + + +
CCore
MMPM
BBase
EExtensión
XExperimental
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
AcceptFilter protocol accept_filtersC
Configures optimizations for a Protocol's Listener Sockets
AcceptMutex Default|method Default sM
Method that Apache uses to serialize multiple children +accepting requests on network sockets
AcceptPathInfo On|Off|Default Default svdhC
Resources accept trailing pathname information
AccessFileName filename [filename] ... .htaccess svC
Name of the distributed configuration file
Action action-type cgi-script [virtual]svdhB
Activates a CGI script for a particular handler or +content-type
AddAlt string file [file] ...svdhB
Alternate text to display for a file, instead of an +icon selected by filename
AddAltByEncoding string MIME-encoding +[MIME-encoding] ...svdhB
Alternate text to display for a file instead of an icon +selected by MIME-encoding
AddAltByType string MIME-type +[MIME-type] ...svdhB
Alternate text to display for a file, instead of an +icon selected by MIME content-type
AddCharset charset extension +[extension] ...svdhB
Maps the given filename extensions to the specified content +charset
AddDefaultCharset On|Off|charset Off svdhC
Default charset parameter to be added when a response +content-type is text/plain or text/html
AddDescription string file [file] ...svdhB
Description to display for a file
AddEncoding MIME-enc extension +[extension] ...svdhB
Maps the given filename extensions to the specified encoding +type
AddHandler handler-name extension +[extension] ...svdhB
Maps the filename extensions to the specified +handler
AddIcon icon name [name] +...svdhB
Icon to display for a file selected by name
AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...svdhB
Icon to display next to files selected by MIME +content-encoding
AddIconByType icon MIME-type +[MIME-type] ...svdhB
Icon to display next to files selected by MIME +content-type
AddInputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +client requests
AddLanguage MIME-lang extension +[extension] ...svdhB
Maps the given filename extension to the specified content +language
AddModuleInfo module-name stringsvE
Adds additional information to the module +information displayed by the server-info handler
AddOutputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +responses from the server
AddOutputFilterByType filter[;filter...] +MIME-type [MIME-type] ...svdhC
assigns an output filter to a particular MIME-type
AddType MIME-type extension +[extension] ...svdhB
Maps the given filename extensions onto the specified content +type
Alias URL-path +file-path|directory-pathsvB
Maps URLs to filesystem locations
AliasMatch regex +file-path|directory-pathsvB
Maps URLs to filesystem locations using regular +expressions
Allow from all|host|env=env-variable +[host|env=env-variable] ...dhB
Controls which hosts can access an area of the +server
AllowCONNECT port [port] ... 443 563 svE
Ports that are allowed to CONNECT through the +proxy
AllowEncodedSlashes On|Off Off svC
Determines whether encoded path separators in URLs are allowed to +be passed through
AllowOverride All|None|directive-type +[directive-type] ... All dC
Types of directives that are allowed in +.htaccess files
Anonymous user [user] ...dhE
Specifies userIDs that are allowed access without +password verification
Anonymous_LogEmail On|Off On dhE
Sets whether the password entered will be logged in the +error log
Anonymous_MustGiveEmail On|Off On dhE
Specifies whether blank passwords are allowed
Anonymous_NoUserID On|Off Off dhE
Sets whether the userID field may be empty
Anonymous_VerifyEmail On|Off Off dhE
Sets whether to check the password field for a correctly +formatted email address
AuthBasicAuthoritative On|Off On dhB
Sets whether authorization and authentication are passed to +lower level modules
AuthBasicProvider provider-name +[provider-name] ... file dhB
Sets the authentication provider(s) for this location
AuthDBDUserPWQuery querydE
SQL query to look up a password for a user
AuthDBDUserRealmQuery querydE
SQL query to look up a password hash for a user and realm. +
AuthDBMGroupFile file-pathdhE
Sets the name of the database file containing the list +of user groups for authorization
AuthDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store passwords
AuthDBMUserFile file-pathdhE
Sets the name of a database file containing the list of users and +passwords for authentication
AuthDefaultAuthoritative On|Off On dhB
Sets whether authentication is passed to lower level +modules
AuthDigestAlgorithm MD5|MD5-sess MD5 dhX
Selects the algorithm used to calculate the challenge and +response hashes in digest authentication
AuthDigestDomain URI [URI] ...dhX
URIs that are in the same protection space for digest +authentication
AuthDigestNcCheck On|Off Off sX
Enables or disables checking of the nonce-count sent by the +server
AuthDigestNonceFormat formatdhX
Determines how the nonce is generated
AuthDigestNonceLifetime seconds 300 dhX
How long the server nonce is valid
AuthDigestProvider provider-name +[provider-name] ... file dhX
Sets the authentication provider(s) for this location
AuthDigestQop none|auth|auth-int [auth|auth-int] auth dhX
Determines the quality-of-protection to use in digest +authentication
AuthDigestShmemSize size 1000 sX
The amount of shared memory to allocate for keeping track +of clients
AuthGroupFile file-pathdhB
Sets the name of a text file containing the list +of user groups for authorization
AuthLDAPBindDN distinguished-namedhE
Optional DN to use in binding to the LDAP server
AuthLDAPBindPassword passworddhE
Password used in conjuction with the bind DN
AuthLDAPCharsetConfig file-pathsE
Language to charset conversion configuration file
AuthLDAPCompareDNOnServer on|off on dhE
Use the LDAP server to compare the DNs
AuthLDAPDereferenceAliases never|searching|finding|always Always dhE
When will the module de-reference aliases
AuthLDAPGroupAttribute attributedhE
LDAP attributes used to check for group membership
AuthLDAPGroupAttributeIsDN on|off on dhE
Use the DN of the client username when checking for +group membership
AuthLDAPRemoteUserIsDN on|off off dhE
Use the DN of the client username to set the REMOTE_USER +environment variable
AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]dhE
URL specifying the LDAP search parameters
AuthName auth-domaindhC
Authorization realm for use in HTTP +authentication
<AuthnProviderAlias baseProvider Alias> +... </AuthnProviderAlias>svE
Enclose a group of directives that represent an +extension of a base authentication provider and referenced by +the specified alias
AuthType Basic|DigestdhC
Type of user authentication
AuthUserFile file-pathdhB
Sets the name of a text file containing the list of users and +passwords for authentication
AuthzDBMAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store list of user groups
AuthzDefaultAuthoritative On|Off On dhB
Sets whether authorization is passed to lower level +modules
AuthzGroupFileAuthoritative On|Off On dhB
Sets whether authorization will be passed on to lower level +modules
AuthzLDAPAuthoritative on|off on dhE
Prevent other authentication modules from +authenticating the user if this one fails
AuthzOwnerAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzUserAuthoritative On|Off On dhB
Sets whether authorization will be passed on to lower level +modules
BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...svdhB
Sets environment variables conditional on HTTP User-Agent +
BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables conditional on User-Agent without +respect to case
BufferedLogs On|Off Off sB
Buffer log entries in memory before writing to disk
CacheDefaultExpire seconds 3600 (one hour) svE
The default duration to cache a document when no expiry date is specified.
CacheDirLength length 2 svE
The number of characters in subdirectory names
CacheDirLevels levels 3 svE
The number of levels of subdirectories in the +cache.
CacheDisable url-stringsvE
Disable caching of specified URLs
CacheEnable cache_type url-stringsvE
Enable caching of specified URLs using a specified storage +manager
CacheFile file-path [file-path] ...sX
Cache a list of file handles at startup time
CacheIgnoreCacheControl On|Off Off svE
Ignore request to not serve cached content to client
CacheIgnoreHeaders header-string [header-string] ... None svE
Do not store the given HTTP header(s) in the cache. +
CacheIgnoreNoLastMod On|Off Off svE
Ignore the fact that a response has no Last Modified +header.
CacheLastModifiedFactor float 0.1 svE
The factor used to compute an expiry date based on the +LastModified date.
CacheMaxExpire seconds 86400 (one day) svE
The maximum time in seconds to cache a document
CacheMaxFileSize bytes 1000000 svE
The maximum size (in bytes) of a document to be placed in the +cache
CacheMinFileSize bytes 1 svE
The minimum size (in bytes) of a document to be placed in the +cache
CacheNegotiatedDocs On|Off Off svB
Allows content-negotiated documents to be +cached by proxy servers
CacheRoot directorysvE
The directory root under which cache files are +stored
CacheStoreNoStore On|Off Off svE
Attempt to cache requests or responses that have been marked as no-store.
CacheStorePrivate On|Off Off svE
Attempt to cache responses that the server has marked as private
CGIMapExtension cgi-path .extensiondhC
Technique for locating the interpreter for CGI +scripts
CharsetDefault charsetsvdhX
Charset to translate into
CharsetOptions option [option] ... DebugLevel=0 NoImpl +svdhX
Configures charset translation behavior
CharsetSourceEnc charsetsvdhX
Source charset of files
CheckSpelling on|off Off svdhE
Enables the spelling +module
ContentDigest On|Off Off svdhC
Enables the generation of Content-MD5 HTTP Response +headers
CookieDomain domainsvdhE
The domain to which the tracking cookie applies
CookieExpires expiry-periodsvdhE
Expiry time for the tracking cookie
CookieLog filenamesvB
Sets filename for the logging of cookies
CookieName token Apache svdhE
Name of the tracking cookie
CookieStyle + Netscape|Cookie|Cookie2|RFC2109|RFC2965 Netscape svdhE
Format of the cookie header field
CookieTracking on|off off svdhE
Enables tracking cookie
CoreDumpDirectory directorysM
Directory where Apache attempts to +switch before dumping core
CustomLog file|pipe +format|nickname +[env=[!]environment-variable]svB
Sets filename and format of log file
Dav On|Off|provider-name Off dE
Enable WebDAV HTTP methods
DavDepthInfinity on|off off svdE
Allow PROPFIND, Depth: Infinity requests
DavGenericLockDB file-pathsvdE
Location of the DAV lock database
DavLockDB file-pathsvE
Location of the DAV lock database
DavMinTimeout seconds 0 svdE
Minimum amount of time the server holds a lock on +a DAV resource
DBDExptime time-in-secondssvE
Keepalive time for idle connections
DBDKeep numbersvE
Maximum sustained number of connections
DBDMax numbersvE
Maximum number of connections
DBDMin numbersvE
Minimum number of connections
DBDParams +param1=value1[,param2=value2]svE
Parameters for database connection
DBDPersist 0|1svE
Whether to use persistent connections
DBDPrepareSQL "SQL statement" labelsvE
Define an SQL prepared statement
DBDriver namesvE
Specify an SQL driver
DefaultIcon url-pathsvdhB
Icon to display for files when no specific icon is +configured
DefaultLanguage MIME-langsvdhB
Sets all files in the given scope to the specified +language
DefaultType MIME-type text/plain svdhC
MIME content-type that will be sent if the +server cannot determine a type in any other way
DeflateBufferSize value 8096 svE
Fragment size to be compressed at one time by zlib
DeflateCompressionLevel valuesvE
How much compression do we apply to the output
DeflateFilterNote [type] notenamesvE
Places the compression ratio in a note for logging
DeflateMemLevel value 9 svE
How much memory should be used by zlib for compression
DeflateWindowSize value 15 svE
Zlib compression window size
Deny from all|host|env=env-variable +[host|env=env-variable] ...dhB
Controls which hosts are denied access to the +server
<Directory directory-path> +... </Directory>svC
Enclose a group of directives that apply only to the +named file-system directory and sub-directories
DirectoryIndex + local-url [local-url] ... index.html svdhB
List of resources to look for when the client requests +a directory
<DirectoryMatch regex> +... </DirectoryMatch>svC
Enclose directives that apply to +file-system directories matching a regular expression and their +subdirectories
DirectorySlash On|Off On svdhB
Toggle trailing slash redirects on or off
DocumentRoot directory-path /usr/local/apache/h +svC
Directory that forms the main document tree visible +from the web
DumpIOInput On|Off Off sE
Dump all input data to the error log
DumpIOOutput On|Off Off sE
Dump all output data to the error log
EnableExceptionHook On|Off Off sM
Enables a hook that runs exception handlers +after a crash
EnableMMAP On|Off On svdhC
Use memory-mapping to read files during delivery
EnableSendfile On|Off On svdhC
Use the kernel sendfile support to deliver files to the client
ErrorDocument error-code documentsvdhC
What the server will return to the client +in case of an error
ErrorLog file-path|syslog[:facility] logs/error_log (Uni +svC
Location where the server will log errors
ExamplesvdhX
Demonstration directive to illustrate the Apache module +API
ExpiresActive On|OffsvdhE
Enables generation of Expires +headers
ExpiresByType MIME-type +<code>secondssvdhE
Value of the Expires header configured +by MIME type
ExpiresDefault <code>secondssvdhE
Default algorithm for calculating expiration time
ExtendedStatus On|Off Off sB
Keep track of extended status information for each +request
ExtFilterDefine filtername parameterssE
Define an external filter
ExtFilterOptions option [option] ... DebugLevel=0 NoLogS +dE
Configure mod_ext_filter options
FileETag component ... INode MTime Size svdhC
File attributes used to create the ETag +HTTP response header
<Files filename> ... </Files>svdhC
Contains directives that apply to matched +filenames
<FilesMatch regex> ... </FilesMatch>svdhC
Contains directives that apply to regular-expression matched +filenames
FilterChain [+=-@!]filter-name ...svdhB
Configure the filter chain
FilterDeclare filter-name [type]svdhB
Declare a smart filter
FilterProtocol filter-name [provider-name] + proto-flagssvdhB
Deal with correct HTTP protocol handling
FilterProvider filter-name provider-name + [req|resp|env]=dispatch matchsvdhB
Register a content filter
FilterTrace filter-name levelsvdB
Get debug/diagnostic information from + mod_filter
ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback] Prefer svdhB
Action to take if a single acceptable document is not +found
ForceType MIME-type|NonedhC
Forces all matching files to be served with the specified +MIME content-type
ForensicLog filename|pipesvE
Sets filename of the forensic log
GracefulShutDownTimeout secondssM
Specify a timeout after which a gracefully shutdown server +will exit.
Group unix-group #-1 sM
Group under which the server will answer +requests
Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]svdhE
Configure HTTP response headers
HeaderName filenamesvdhB
Name of the file that will be inserted at the top +of the index listing
HostnameLookups On|Off|Double Off svdC
Enables DNS lookups on client IP addresses
IdentityCheck On|Off Off svdE
Enables logging of the RFC 1413 identity of the remote +user
IdentityCheckTimeout seconds 30 svdE
Determines the timeout duration for ident requests
<IfDefine [!]parameter-name> ... + </IfDefine>svdhC
Encloses directives that will be processed only +if a test is true at startup
<IfModule [!]module-file|module-identifier> ... + </IfModule>svdhC
Encloses directives that are processed conditional on the +presence or absence of a specific module
<IfVersion [[!]operator] version> ... +</IfVersion>svdhE
contains version dependent configuration
ImapBase map|referer|URL http://servername/ svdhB
Default base for imagemap files
ImapDefault error|nocontent|map|referer|URL nocontent svdhB
Default action when an imagemap is called with coordinates +that are not explicitly mapped
ImapMenu none|formatted|semiformatted|unformattedsvdhB
Action if no coordinates are given when calling +an imagemap
Include file-path|directory-pathsvdC
Includes other configuration files from within +the server configuration files
IndexIgnore file [file] ...svdhB
Adds to the list of files to hide when listing +a directory
IndexOptions [+|-]option [[+|-]option] +...svdhB
Various configuration settings for directory +indexing
IndexOrderDefault Ascending|Descending +Name|Date|Size|Description Ascending Name svdhB
Sets the default ordering of the directory index
IndexStyleSheet url-pathsvdhB
Adds a CSS stylesheet to the directory index
ISAPIAppendLogToErrors on|off off svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the error log
ISAPIAppendLogToQuery on|off on svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the query field
ISAPICacheFile file-path [file-path] +...svB
ISAPI .dll files to be loaded at startup
ISAPIFakeAsync on|off off svdhB
Fake asynchronous support for ISAPI callbacks
ISAPILogNotSupported on|off off svdhB
Log unsupported feature requests from ISAPI +extensions
ISAPIReadAheadBuffer size 49152 svdhB
Size of the Read Ahead Buffer sent to ISAPI +extensions
KeepAlive On|Off On svC
Enables HTTP persistent connections
KeepAliveTimeout seconds 5 svC
Amount of time the server will wait for subsequent +requests on a persistent connection
LanguagePriority MIME-lang [MIME-lang] +...svdhB
The precendence of language variants for cases where +the client does not express a preference
LDAPCacheEntries number 1024 sE
Maximum number of entries in the primary LDAP cache
LDAPCacheTTL seconds 600 sE
Time that cached items remain valid
LDAPConnectionTimeout secondssE
Specifies the socket connection timeout in seconds
LDAPOpCacheEntries number 1024 sE
Number of entries used to cache LDAP compare +operations
LDAPOpCacheTTL seconds 600 sE
Time that entries in the operation cache remain +valid
LDAPSharedCacheFile directory-path/filenamesE
Sets the shared memory cache file
LDAPSharedCacheSize bytes 102400 sE
Size in bytes of the shared-memory cache
LDAPTrustedClientCert type directory-path/filename/nickname [password]svdhE
Sets the file containing or nickname referring to a per +connection client certificate. Not all LDAP toolkits support per +connection client certificates.
LDAPTrustedGlobalCert type directory-path/filename [password]sE
Sets the file or database containing global trusted +Certificate Authority or global client certificates
LDAPTrustedMode typesvE
Specifies the SSL/TLS mode to be used when connecting to an LDAP server.
LDAPVerifyServerCert On|Off On sE
Force server certificate verification
<Limit method [method] ... > ... + </Limit>svdhC
Restrict enclosed access controls to only certain HTTP +methods
<LimitExcept method [method] ... > ... + </LimitExcept>svdhC
Restrict access controls to all HTTP methods +except the named ones
LimitInternalRecursion number [number] 10 svC
Determine maximum number of internal redirects and nested +subrequests
LimitRequestBody bytes 0 svdhC
Restricts the total size of the HTTP request body sent +from the client
LimitRequestFields number 100 sC
Limits the number of HTTP request header fields that +will be accepted from the client
LimitRequestFieldsize bytessC
Limits the size of the HTTP request header allowed from the +client
LimitRequestLine bytes 8190 sC
Limit the size of the HTTP request line that will be accepted +from the client
LimitXMLRequestBody bytes 1000000 svdhC
Limits the size of an XML-based request body
Listen [IP-address:]portnumber [protocol]sM
IP addresses and ports that the server +listens to
ListenBacklog backlogsM
Maximum length of the queue of pending connections
LoadFile filename [filename] ...sE
Link in the named object file or library
LoadModule module filenamesE
Links in the object file or library, and adds to the list +of active modules
<Location + URL-path|URL> ... </Location>svC
Applies the enclosed directives only to matching +URLs
<LocationMatch + regex> ... </LocationMatch>svC
Applies the enclosed directives only to regular-expression +matching URLs
LockFile filename logs/accept.lock sM
Location of the accept serialization lock file
LogFormat format|nickname +[nickname] "%h %l %u %t \"%r\" +svB
Describes a format for use in a log file
LogLevel level warn svC
Controls the verbosity of the ErrorLog
MaxClients numbersM
Maximum number of child processes that will be created +to serve requests
MaxKeepAliveRequests number 100 svC
Number of requests allowed on a persistent +connection
MaxMemFree KBytes 0 sM
Maximum amount of memory that the main allocator is allowed +to hold without calling free()
MaxRequestsPerChild number 10000 sM
Limit on the number of requests that an individual child server +will handle during its life
MaxRequestsPerThread number 0 sM
Limita el número de peticiones que una hebra (thread) puede +atender durante su vida
MaxSpareServers number 10 sM
Maximum number of idle child server processes
MaxSpareThreads numbersM
Maximum number of idle threads
MaxThreads number 2048 sM
Set the maximum number of worker threads
MCacheMaxObjectCount value 1009 sE
The maximum number of objects allowed to be placed in the +cache
MCacheMaxObjectSize bytes 10000 sE
The maximum size (in bytes) of a document allowed in the +cache
MCacheMaxStreamingBuffer size_in_bytes the smaller of 1000 +sE
Maximum amount of a streamed response to buffer in memory +before declaring the response uncacheable
MCacheMinObjectSize bytes 0 sE
The minimum size (in bytes) of a document to be allowed in the +cache
MCacheRemovalAlgorithm LRU|GDSF GDSF sE
The algorithm used to select documents for removal from the +cache
MCacheSize KBytes 100 sE
The maximum amount of memory used by the cache in +KBytes
MetaDir directory .web svdhE
Name of the directory to find CERN-style meta information +files
MetaFiles on|off off svdhE
Activates CERN meta-file processing
MetaSuffix suffix .meta svdhE
File name suffix for the file containg CERN-style +meta information
MimeMagicFile file-pathsvE
Enable MIME-type determination based on file contents +using the specified magic file
MinSpareServers number 5 sM
Minimum number of idle child server processes
MinSpareThreads numbersM
Minimum number of idle threads available to handle request +spikes
MMapFile file-path [file-path] ...sX
Map a list of files into memory at startup time
ModMimeUsePathInfo On|Off Off dB
Tells mod_mime to treat path_info +components as part of the filename
MultiviewsMatch Any|NegotiatedOnly|Filters|Handlers +[Handlers|Filters] NegotiatedOnly svdhB
The types of files that will be included when searching for +a matching file with MultiViews
NameVirtualHost addr[:port]sC
Designates an IP address for name-virtual +hosting
NoProxy host [host] ...svE
Hosts, domains, or networks that will be connected to +directly
NWSSLTrustedCerts filename [filename] ...sB
List of additional client certificates
NWSSLUpgradeable [IP-address:]portnumbersB
Allows a connection to be upgraded to an SSL connection upon request
Options + [+|-]option [[+|-]option] ... All svdhC
Configures what features are available in a particular +directory
Order ordering Deny,Allow dhB
Controls the default access state and the order in which +Allow and Deny are +evaluated.
PassEnv env-variable [env-variable] +...svdhB
Passes environment variables from the shell
PidFile filename logs/httpd.pid sM
File where the server records the process ID +of the daemon
ProtocolEcho On|OffsvX
Turn the echo server on or off
<Proxy wildcard-url> ...</Proxy>svE
Container for directives applied to proxied resources
ProxyBadHeader IsError|Ignore|StartBody IsError svE
Determines how to handle bad header lines in a +response
ProxyBlock *|word|host|domain +[word|host|domain] ...svE
Words, hosts, or domains that are banned from being +proxied
ProxyDomain DomainsvE
Default domain name for proxied requests
ProxyErrorOverride On|Off Off svE
Override error pages for proxied content
ProxyIOBufferSize bytes 8192 svE
Determine size of internal data throughput buffer
<ProxyMatch regex> ...</ProxyMatch>svE
Container for directives applied to regular-expression-matched +proxied resources
ProxyMaxForwards number 10 svE
Maximium number of proxies that a request can be forwarded +through
ProxyPass [path] !|url [key=value key=value ...]]svdE
Maps remote servers into the local server URL-space
ProxyPassReverse [path] urlsvdE
Adjusts the URL in HTTP response headers sent from a reverse +proxied server
ProxyPassReverseCookieDomain internal-domain public-domainsvdE
Adjusts the Domain string in Set-Cookie headers from a reverse- +proxied server
ProxyPassReverseCookiePath internal-path public-pathsvdE
Adjusts the Path string in Set-Cookie headers from a reverse- +proxied server
ProxyPreserveHost On|Off Off svE
Use incoming Host HTTP request header for proxy +request
ProxyReceiveBufferSize bytes 0 svE
Network buffer size for proxied HTTP and FTP +connections
ProxyRemote match remote-serversvE
Remote proxy used to handle certain requests
ProxyRemoteMatch regex remote-serversvE
Remote proxy used to handle requests matched by regular +expressions
ProxyRequests On|Off Off svE
Enables forward (standard) proxy requests
ProxyTimeout seconds 300 svE
Network timeout for proxied requests
ProxyVia On|Off|Full|Block Off svE
Information provided in the Via HTTP response +header for proxied requests
ReadmeName filenamesvdhB
Name of the file that will be inserted at the end +of the index listing
ReceiveBufferSize bytes 0 sM
TCP receive buffer size
Redirect [status] URL-path +URLsvdhB
Sends an external redirect asking the client to fetch +a different URL
RedirectMatch [status] regex +URLsvdhB
Sends an external redirect based on a regular expression match +of the current URL
RedirectPermanent URL-path URLsvdhB
Sends an external permanent redirect asking the client to fetch +a different URL
RedirectTemp URL-path URLsvdhB
Sends an external temporary redirect asking the client to fetch +a different URL
RemoveCharset extension [extension] +...vdhB
Removes any character set associations for a set of file +extensions
RemoveEncoding extension [extension] +...vdhB
Removes any content encoding associations for a set of file +extensions
RemoveHandler extension [extension] +...vdhB
Removes any handler associations for a set of file +extensions
RemoveInputFilter extension [extension] +...vdhB
Removes any input filter associations for a set of file +extensions
RemoveLanguage extension [extension] +...vdhB
Removes any language associations for a set of file +extensions
RemoveOutputFilter extension [extension] +...vdhB
Removes any output filter associations for a set of file +extensions
RemoveType extension [extension] +...vdhB
Removes any content type associations for a set of file +extensions
RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]svdhE
Configure HTTP request headers
Require entity-name [entity-name] ...dhC
Selects which authenticated users can access +a resource
RewriteBase URL-pathdhE
Sets the base URL for per-directory rewrites
RewriteCond + TestString CondPatternsvdhE
Defines a condition under which rewriting will take place +
RewriteEngine on|off off svdhE
Enables or disables runtime rewriting engine
RewriteLock file-pathsE
Sets the name of the lock file used for RewriteMap +synchronization
RewriteLog file-pathsvE
Sets the name of the file used for logging rewrite engine +processing
RewriteLogLevel Level 0 svE
Sets the verbosity of the log file used by the rewrite +engine
RewriteMap MapName MapType:MapSource +svE
Defines a mapping function for key-lookup
RewriteOptions OptionssvdhE
Sets some special options for the rewrite engine
RewriteRule + Pattern SubstitutionsvdhE
Defines rules for the rewriting engine
RLimitCPU seconds|max [seconds|max]svdhC
Limits the CPU consumption of processes launched +by Apache children
RLimitMEM bytes|max [bytes|max]svdhC
Limits the memory consumption of processes launched +by Apache children
RLimitNPROC number|max [number|max]svdhC
Limits the number of processes that can be launched by +processes launched by Apache children
Satisfy Any|All All dhC
Interaction between host-level access control and +user authentication
ScoreBoardFile file-path logs/apache_status sM
Location of the file used to store coordination data for +the child processes
Script method cgi-scriptsvdB
Activates a CGI script for a particular request +method.
ScriptAlias URL-path +file-path|directory-pathsvB
Maps a URL to a filesystem location and designates the +target as a CGI script
ScriptAliasMatch regex +file-path|directory-pathsvB
Maps a URL to a filesystem location using a regular expression +and designates the target as a CGI script
ScriptInterpreterSource Registry|Registry-Strict|Script Script svdhC
Technique for locating the interpreter for CGI +scripts
ScriptLog file-pathsvB
Location of the CGI script error logfile
ScriptLogBuffer bytes 1024 svB
Maximum amount of PUT or POST requests that will be recorded +in the scriptlog
ScriptLogLength bytes 10385760 svB
Size limit of the CGI script logfile
ScriptSock file-path logs/cgisock svB
The filename prefix of the socket to use for communication with +the cgi daemon
SecureListen [IP-address:]portnumber +Certificate-Name [MUTUAL]sB
Enables SSL encryption for the specified port
SendBufferSize bytes 0 sM
TCP buffer size
ServerAdmin email-address|URLsvC
Email address that the server includes in error +messages sent to the client
ServerAlias hostname [hostname] ...vC
Alternate names for a host used when matching requests +to name-virtual hosts
ServerLimit numbersM
Upper limit on configurable number of processes
ServerName fully-qualified-domain-name[:port]svC
Hostname and port that the server uses to identify +itself
ServerPath URL-pathvC
Legacy URL pathname for a name-based virtual host that +is accessed by an incompatible browser
ServerRoot directory-path /usr/local/apache sC
Base directory for the server installation
ServerSignature On|Off|EMail Off svdhC
Configures the footer on server-generated documents
ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full Full sC
Configures the Server HTTP response +header
SetEnv env-variable valuesvdhB
Sets environment variables
SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables based on attributes of the request +
SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables based on attributes of the request +without respect to case
SetHandler handler-name|NonesvdhC
Forces all matching files to be processed by a +handler
SetInputFilter filter[;filter...]svdhC
Sets the filters that will process client requests and POST +input
SetOutputFilter filter[;filter...]svdhC
Sets the filters that will process responses from the +server
SSIEndTag tag "-->" svB
String that ends an include element
SSIErrorMsg message "[an error occurred +svdhB
Error message displayed when there is an SSI +error
SSIStartTag tag "<!--#" svB
String that starts an include element
SSITimeFormat formatstring "%A, %d-%b-%Y %H:%M +svdhB
Configures the format in which date strings are +displayed
SSIUndefinedEcho string "(none)" svdhB
String displayed when an unset variable is echoed
SSLCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Client Auth
SSLCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Client Auth
SSLCADNRequestFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for defining acceptable CA names
SSLCADNRequestPath directory-pathsvE
Directory of PEM-encoded CA Certificates for +defining acceptable CA names
SSLCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Client Auth
SSLCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Client Auth
SSLCertificateChainFile file-pathsvE
File of PEM-encoded Server CA Certificates
SSLCertificateFile file-pathsvE
Server PEM-encoded X.509 Certificate file
SSLCertificateKeyFile file-pathsvE
Server PEM-encoded Private Key file
SSLCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +handshake
SSLCryptoDevice engine builtin sE
Enable use of a cryptographic hardware accelerator
SSLEngine on|off|optional off svE
SSL Engine Operation Switch
SSLHonorCiperOrder flagsvE
Option to prefer the server's cipher preference order
SSLMutex type none sE
Semaphore for internal mutual exclusion of +operations
SSLOptions [+|-]option ...svdhE
Configure various SSL engine run-time options
SSLPassPhraseDialog type builtin sE
Type of pass phrase dialog for encrypted private +keys
SSLProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors
SSLProxyCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Remote Server Auth
SSLProxyCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Remote Server Auth
SSLProxyCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +proxy handshake
SSLProxyEngine on|off off svE
SSL Proxy Engine Operation Switch
SSLProxyMachineCertificateFile filenamesE
File of concatenated PEM-encoded client certificates and keys to be used by the proxy
SSLProxyMachineCertificatePath directorysE
Directory of PEM-encoded client certificates and keys to be used by the proxy
SSLProxyProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors for proxy usage
SSLProxyVerify level none svdhE
Type of remote server Certificate verification
SSLProxyVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Remote Server +Certificate verification
SSLRandomSeed context source +[bytes]sE
Pseudo Random Number Generator (PRNG) seeding +source
SSLRequire expressiondhE
Allow access only when an arbitrarily complex +boolean expression is true
SSLRequireSSLdhE
Deny access when SSL is not used for the +HTTP request
SSLSessionCache type none sE
Type of the global/inter-process SSL Session +Cache
SSLSessionCacheTimeout seconds 300 svE
Number of seconds before an SSL session expires +in the Session Cache
SSLUserName varnamesdhE
Variable name to determine user name
SSLVerifyClient level none svdhE
Type of Client Certificate verification
SSLVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Client +Certificate verification
StartServers numbersM
Number of child server processes created at startup
StartThreads numbersM
Number of threads created on startup
SuexecUserGroup User GroupsvE
User and group permissions for CGI programs
ThreadLimit numbersM
Sets the upper limit on the configurable number of threads +per child process
ThreadsPerChild numbersM
Number of threads created by each child process
ThreadStackSize sizesM
The size in bytes of the stack used by threads handling +client connections
TimeOut seconds 300 sC
Amount of time the server will wait for +certain events before failing a request
TraceEnable [on|off|extended] on sC
Determines the behaviour on TRACE +requests
TransferLog file|pipesvB
Specify location of a log file
TypesConfig file-path conf/mime.types sB
The location of the mime.types file
UnsetEnv env-variable [env-variable] +...svdhB
Removes variables from the environment
UseCanonicalName On|Off|DNS Off svdC
Configures how the server determines its own name and +port
UseCanonicalPhysicalPort On|Off Off svdC
Configures how the server determines its own name and +port
User unix-userid #-1 sM
The userid under which the server will answer +requests
UserDir directory-filenamesvB
Location of the user-specific directories
VirtualDocumentRoot interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
VirtualDocumentRootIP interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
<VirtualHost + addr[:port] [addr[:port]] + ...> ... </VirtualHost>sC
Contains directives that apply only to a specific +hostname or IP address
VirtualScriptAlias interpolated-directory|none none svE
Dynamically configure the location of the CGI directory for +a given virtual host
VirtualScriptAliasIP interpolated-directory|none none svE
Dynamically configure the location of the cgi directory for +a given virtual host
Win32DisableAcceptExsM
Use accept() rather than AcceptEx() to accept network connections
XBitHack on|off|full off svdhB
Parse SSI directives in files with the execute bit +set
+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/quickreference.html.ja.euc-jp b/docs/manual/mod/quickreference.html.ja.euc-jp new file mode 100644 index 00000000..264d0303 --- /dev/null +++ b/docs/manual/mod/quickreference.html.ja.euc-jp @@ -0,0 +1,684 @@ + + + +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö ¥¯¥¤¥Ã¥¯¥ê¥Õ¥¡¥ì¥ó¥¹ - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö ¥¯¥¤¥Ã¥¯¥ê¥Õ¥¡¥ì¥ó¥¹

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

¥Ç¥£¥ì¥¯¥Æ¥£¥Ö ¥¯¥¤¥Ã¥¯¥ê¥Õ¥¡¥ì¥ó¥¹¤Ç¤Ï¡¢³Æ Apache ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + »ÈÍÑÊýË¡¡¢¥Ç¥Õ¥©¥ë¥ÈÃÍ¡¢¥¹¥Æ¡¼¥¿¥¹¤È¥³¥ó¥Æ¥­¥¹¥È¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£ + ³Æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¡¢¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ë´Ø¤·¤Æ¤Ï + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¼­½ñ¤ò + ¤´Í÷²¼¤µ¤¤¡£

+ +

Âè 1 ÎóÌܤϥǥ£¥ì¥¯¥Æ¥£¥Ö¤Î̾Á°¤È»ÈÍÑÊýË¡¤Ç¤¹¡£ + Âè 2 ÎóÌÜ¤Ï (¤â¤·¤¢¤ì¤Ð) ¥Ç¥Õ¥©¥ë¥ÈÃͤȤʤäƤ¤¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥ÈÃͤ¬Ä¹¤¹¤®¤Æɽ¼¨¤·¤­¤ì¤Ê¤¤¾ì¹ç¤Ï¡¢ºÇ½é¤Îʸ»úÎó¤Î¸å¤í¤Ë + ¡Ö + ¡×¤¬Â³¤­¤Þ¤¹¡£

+ +

Âè 3, 4 Îó¤Ï¡¢²¼¤Îɽ¤ÎÃí¼á¤Ë½¾¤Ã¤Æ¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î»ÈÍѤǤ­¤ë¥³¥ó¥Æ¥­¥¹¥È¤È¡¢ + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥¹¥Æ¡¼¥¿¥¹¤¬¼¨¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+
+
+ + + +
 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X  + + + + + +
s¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ë
v¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È
d¥Ç¥£¥ì¥¯¥È¥ê
h.htaccess
 + + + + + + +
CCore
MMPM
BBase
EExtension
XExperimental
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
AcceptFilter protocol accept_filtersC
¥×¥í¥È¥³¥ë¤ò Listen ¤·¤Æ¤¤¤ë¥½¥±¥Ã¥È¤ÎºÇŬ²½¤òÀßÄꤹ¤ë
AcceptMutex default|method default sM
Ê£¿ô¤Î»Ò¥×¥í¥»¥¹¤¬¥Í¥Ã¥È¥ï¡¼¥¯¥½¥±¥Ã¥È¤Ç¥ê¥¯¥¨¥¹¥È¤ò +accept ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤È¤­¤Ë¡¢Apache ¤¬¤½¤ì¤é¤Î»Ò¥×¥í¥»¥¹¤òľÎ󲽤¹¤ë¤¿¤á¤Ë +»È¤¦ÊýË¡
AcceptPathInfo On|Off|Default Default svdhC
¸å¤Ë³¤¯¥Ñ¥¹Ì¾¾ðÊó¤ò¼õ¤±ÉÕ¤±¤ë¥ê¥½¡¼¥¹¤Î»ØÄê
AccessFileName filename [filename] ... .htaccess svC
ʬ»¶ÀßÄê¥Õ¥¡¥¤¥ë¤Î̾Á°
Action action-type cgi-script [virtual]svdhB
ÆÃÄê¤Î¥Ï¥ó¥É¥é¤ä¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ËÂФ·¤Æ CGI ¤ò¼Â¹Ô¤¹¤ë¤è¤¦¤Ë +ÀßÄê
AddAlt string file [file] ...svdhB
¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ë +ɽ¼¨¤µ¤ì¤ë¡¢¥Õ¥¡¥¤¥ë̾¤ÇÁªÂò¤µ¤ì¤¿ÂåÂإƥ­¥¹¥È
AddAltByEncoding string MIME-encoding +[MIME-encoding] ...svdhB
¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ëɽ¼¨¤µ¤ì¤ë¡¢MIME Éä¹æ²½ÊýË¡¤ÇÁªÂò¤µ¤ì¤¿ +ÂåÂإƥ­¥¹¥È
AddAltByType string MIME-type +[MIME-type] ...svdhB
¥¢¥¤¥³¥ó¤ÎÂå¤ï¤ê¤Ë +ɽ¼¨¤µ¤ì¤ë¡¢MIME ¥¿¥¤¥×¤ÇÁªÂò¤µ¤ì¤¿ÂåÂإƥ­¥¹¥È
AddCharset charset extension +[extension] ...svdh
¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿Ê¸»ú¥»¥Ã¥È¤Ë¥Þ¥Ã¥×¤¹¤ë
AddDefaultCharset On|Off|charset Off svdhC
¥ì¥¹¥Ý¥ó¥¹¤Î¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤¬ text/plain ¤¢¤ë¤¤¤Ï +text/html ¤Î¾ì¹ç¤ËÄɲ乤ë¥Ç¥Õ¥©¥ë¥È¤Î charset ¥Ñ¥é¥á¡¼¥¿
AddDescription string file [file] ...svdhB
¥Õ¥¡¥¤¥ë¤ËÂФ·¤Æɽ¼¨¤¹¤ëÀâÌÀ
AddEncoding MIME-enc extension +[extension] ...svdh
¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿¥¨¥ó¥³¡¼¥Ç¥£¥ó¥° +¤Ë¥Þ¥Ã¥×¤¹¤ë
AddHandler handler-name extension +[extension] ...svdh
¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿¥Ï¥ó¥É¥é¤Ë¥Þ¥Ã¥×¤¹¤ë
AddIcon icon name +[name] ...svdhB
¥Õ¥¡¥¤¥ë¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤ò̾Á°¤ÇÁªÂò
AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...svdhB
¥Õ¥¡¥¤¥ë¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤ò MIME +Éä¹æ²½ÊýË¡¤ÇÁªÂò
AddIconByType icon MIME-type +[MIME-type] ...svdhB
¥Õ¥¡¥¤¥ë¤ÎÎÙ¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó¤ò +MIME ¥¿¥¤¥×¤Ë¤è¤Ã¤ÆÁªÂò
AddInputFilter filter[;filter...] +extension [extension] ...svdh
¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤ò¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤¹¤ë + ¥Õ¥£¥ë¥¿¤Ë¥Þ¥Ã¥×¤¹¤ë
AddLanguage MIME-lang extension +[extension] ...svdh
¥Õ¥¡¥¤¥ë̾¤ò»ØÄꤵ¤ì¤¿¸À¸ì¤Ë¥Þ¥Ã¥×
AddModuleInfo module-name stringsvE
server-info ¥Ï¥ó¥É¥é¤Ë¤è¤êɽ¼¨¤µ¤ì¤ë¥â¥¸¥å¡¼¥ë¤Î¾ðÊó¤Ë +ÄɲäξðÊó¤òÉÕ¤±²Ã¤¨¤ë
AddOutputFilter filter[;filter...] +extension [extension] ...svdh
¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò¥µ¡¼¥Ð¤«¤é¤Î±þÅú¤ò½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤Ë + ¥Þ¥Ã¥×¤¹¤ë
AddOutputFilterByType filter[;filter...] MIME-type +[MIME-type] ...svdhC
MIME-type ¤Ë½ÐÎÏ¥Õ¥£¥ë¥¿¤ò³ä¤êÅö¤Æ¤ë
AddType MIME-type extension +[extension] ...svdh
¥Õ¥¡¥¤¥ë̾¤Î³ÈÄ¥»Ò¤ò»ØÄꤵ¤ì¤¿¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤Ë¥Þ¥Ã¥×
Alias URL-path +file-path|directory-pathsvB
URL ¤ò¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤˥ޥåפ¹¤ë
AliasMatch regex +file-path|directory-pathsvB
Àµµ¬É½¸½¤ò»È¤Ã¤Æ URL ¤ò¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤˥ޥåפ¹¤ë
Allow from all|host|env=env-variable +[host|env=env-variable] ...dhB
¥µ¡¼¥Ð¤Î¤¢¤ëÎΰè¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¥Û¥¹¥È¤òÀ©¸æ¤¹¤ë
AllowCONNECT port [port] ... 443 563 svE
¥×¥í¥­¥·¤ò·Ðͳ¤·¤Æ¡¢¤É¤Î¥Ý¡¼¥È¤Ë CONNECT +¤Ç¤­¤ë¤«¤ò»ØÄꤹ¤ë
AllowEncodedSlashes On|Off Off svC
URL Ãæ¤ÎÉä¹æ²½¤µ¤ì¤¿¥Ñ¥¹Ê¬Î¥Ê¸»ú¤¬Àè¤ËÅÁ¤¨¤é¤ì¤ë¤Î¤òµö²Ä¤¹¤ë¤«¤É¤¦¤«¤ò +·èÄꤹ¤ë
AllowOverride All|None|directive-type +[directive-type] ... All dC
.htaccess ¤Çµö²Ä¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¼ïÎà
Anonymous user [user] ...dhE
¥Ñ¥¹¥ï¡¼¥É¤Î¸¡ººÌµ¤·¤Ç¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë userID ¤ò»ØÄꤹ¤ë +
Anonymous_LogEmail On|Off On dhE
ÆþÎϤµ¤ì¤¿¥Ñ¥¹¥ï¡¼¥É¤¬¥¨¥é¡¼¥í¥°¤Ë¥í¥®¥ó¥°¤µ¤ì¤ë¤«¤É¤¦¤«¤ò +ÀßÄꤹ¤ë
Anonymous_MustGiveEmail On|Off On dhE
¶õ¥Ñ¥¹¥ï¡¼¥É¤òµö²Ä¤¹¤ë¤«¤É¤¦¤«¤ò»ØÄꤹ¤ë
Anonymous_NoUserID On|Off Off dhE
¶õ userID ¤òµö²Ä¤¹¤ë¤«¤ò»ØÄꤹ¤ë
Anonymous_VerifyEmail On|Off Off dhE
¥Ñ¥¹¥ï¡¼¥ÉÍó¤¬Àµ¤·¤¤·Á¼°¤ÎÅŻҥ᡼¥ë¥¢¥É¥ì¥¹¤Ç¤¢¤ë¤³¤È¤ò +Ä´¤Ù¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
AuthBasicAuthoritative On|Off On dhB
ǧ¾Ú¤È¾µÇ§¤ò¡¢¤è¤êÄ㤤¥ì¥Ù¥ë¤Î¥â¥¸¥å¡¼¥ë¤Ë°Ü¹Ô¤µ¤»¤ë¤«¤ò +ÀßÄꤷ¤Þ¤¹¡£
AuthBasicProvider On|Off|provider-name +[provider-name] ... On dhB
¤³¤Î°ÌÃÖ¤ËÂФ¹¤ëǧ¾Ú¥×¥í¥Ð¥¤¥À¤òÀßÄꤷ¤Þ¤¹¡£
AuthDBDUserPWQuery querydE
SQL query to look up a password for a user
AuthDBDUserRealmQuery querydE
SQL query to look up a password hash for a user and realm. +
AuthDBMGroupFile file-pathdhE
Sets the name of the database file containing the list +of user groups for authorization
AuthDBMType default|SDBM|GDBM|NDBM|DB default dhE
¥Ñ¥¹¥ï¡¼¥É¤òÊݸ¤¹¤ë¤¿¤á¤ËɬÍפʥǡ¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤Î¼ïÎà¤ò +ÀßÄꤹ¤ë
AuthDBMUserFile file-pathdhE
ǧ¾ÚÍѤΥ桼¥¶¤È¥Ñ¥¹¥ï¡¼¥É¤Î¥ê¥¹¥È¤òÊÝ»ý¤·¤Æ¤¤¤ë +¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë̾¤òÀßÄꤹ¤ë
AuthDefaultAuthoritative On|Off On dhB
¼¡¤ÎÄ㼡¥ì¥Ù¥ë¤Îǧ¾Ú¥â¥¸¥å¡¼¥ë¤ËÀ©¸æ¤òÅϤ¹¤«¤É¤¦¤«¤ò +ÀßÄꤷ¤Þ¤¹
AuthDigestAlgorithm MD5|MD5-sess MD5 dhX
Selects the algorithm used to calculate the challenge and +response hashes in digest authentication
AuthDigestDomain URI [URI] ...dhX
URIs that are in the same protection space for digest +authentication
AuthDigestNcCheck On|Off Off sX
Enables or disables checking of the nonce-count sent by the +server
AuthDigestNonceFormat formatdhX
Determines how the nonce is generated
AuthDigestNonceLifetime seconds 300 dhX
How long the server nonce is valid
AuthDigestProvider provider-name +[provider-name] ... file dhX
Sets the authentication provider(s) for this location
AuthDigestQop none|auth|auth-int [auth|auth-int] auth dhX
Determines the quality-of-protection to use in digest +authentication
AuthDigestShmemSize size 1000 sX
The amount of shared memory to allocate for keeping track +of clients
AuthGroupFile file-pathdhB
¾Úǧ¤Ë»ÈÍѤ¹¤ë¥æ¡¼¥¶¥°¥ë¡¼¥×¤Î°ìÍ÷¤¬³ÊǼ¤µ¤ì¤Æ¤¤¤ë¡¢ +¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤹ¤ë
AuthLDAPBindDN distinguished-namedhE
Optional DN to use in binding to the LDAP server
AuthLDAPBindPassword passworddhE
Password used in conjuction with the bind DN
AuthLDAPCharsetConfig file-pathsE
Language to charset conversion configuration file
AuthLDAPCompareDNOnServer on|off on dhE
Use the LDAP server to compare the DNs
AuthLDAPDereferenceAliases never|searching|finding|always Always dhE
When will the module de-reference aliases
AuthLDAPGroupAttribute attributedhE
LDAP attributes used to check for group membership
AuthLDAPGroupAttributeIsDN on|off on dhE
Use the DN of the client username when checking for +group membership
AuthLDAPRemoteUserIsDN on|off off dhE
Use the DN of the client username to set the REMOTE_USER +environment variable
AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]dhE
URL specifying the LDAP search parameters
AuthName auth-domaindhC
HTTP ǧ¾Ú¤Îǧ²ÄÎΰè (ÌõÃí: realm)
<AuthnProviderAlias baseProvider Alias> +... </AuthnProviderAlias>svE
Enclose a group of directives that represent an +extension of a base authentication provider and referenced by +the specified alias
AuthType Basic|DigestdhC
¥æ¡¼¥¶Ç§¾Ú¤Î¼ïÎà
AuthUserFile file-pathdhB
ǧ¾Ú¤Ë»ÈÍѤ¹¤ë¥æ¡¼¥¶¤È¥Ñ¥¹¥ï¡¼¥É¤Î°ìÍ÷¤¬³ÊǼ¤µ¤ì¤Æ¤¤¤ë¡¢ +¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤Î̾Á°¤òÀßÄꤹ¤ë
AuthzDBMAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store list of user groups
AuthzDefaultAuthoritative On|Off On dhB
¾µÇ§¤¬Äã°Ì¤Î¥â¥¸¥å¡¼¥ë¤ËÅϤµ¤ì¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
AuthzGroupFileAuthoritative On|Off On dhB
¾µÇ§¤¬²¼°Ì¤Î¥â¥¸¥å¡¼¥ë¤ËÅϤµ¤ì¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
AuthzLDAPAuthoritative on|off on dhE
Prevent other authentication modules from +authenticating the user if this one fails
AuthzOwnerAuthoritative On|Off On dhE
¾µÇ§¤¬²¼°Ì¾µÇ§¥â¥¸¥å¡¼¥ë¤ËÅϤµ¤ì¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
AuthzUserAuthoritative On|Off On dhB
¾µÇ§¤¬²¼°Ì¤Î¥â¥¸¥å¡¼¥ë¤ËÅϤµ¤ì¤ë¤«¤É¤¦¤«¤òÀßÄꤹ¤ë
BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...svdhB
HTTP User-Agent ¤Ë´ð¤Å¤¤¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë +
BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
HTTP User-Agent ¤Ë´ð¤Å¤¤¤ÆÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¤Ë +´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë
BufferedLogs On|Off Off sB
¥Ç¥£¥¹¥¯¤Ë½ñ¤­½Ð¤¹Á°¤Ë¥á¥â¥ê¤Ë¥í¥°¥¨¥ó¥È¥ê¤ò¥Ð¥Ã¥Õ¥¡¤¹¤ë
CacheDefaultExpire seconds 3600 (1»þ´Ö) svE
´üÆü¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤È¤­¤Ë¥É¥­¥å¥á¥ó¥È¤ò¥­¥ã¥Ã¥·¥å¤¹¤ë¥Ç¥Õ¥©¥ë¥È¤Î´ü´Ö
CacheDirLength length 2 svE
¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê̾¤Îʸ»ú¿ô
CacheDirLevels levels 3 svE
¥­¥ã¥Ã¥·¥å¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Î¿¼¤µ¤Î¿ô
CacheDisable url-stringsvE
ÆÃÄê¤Î URL ¤ò¥­¥ã¥Ã¥·¥å¤·¤Ê¤¤
CacheEnable cache_type url-stringsvE
»ØÄꤷ¤¿¥¹¥È¥ì¡¼¥¸´ÉÍýÊý¼°¤ò»È¤Ã¤Æ¤Î¥­¥ã¥Ã¥·¥å¤òÍ­¸ú¤Ë¤¹¤ë
CacheFile file-path [file-path] ...sX
Cache a list of file handles at startup time
CacheIgnoreCacheControl On|Off Off svE
¥­¥ã¥Ã¥·¥å¤µ¤ì¤Æ¤¤¤ë¥³¥ó¥Æ¥ó¥Ä¤òÊÖ¤µ¤Ê¤¤¤è¤¦¤Ë¥¯¥é¥¤¥¢¥ó¥È¤«¤é +¥ê¥¯¥¨¥¹¥È¤µ¤ì¤Æ¤â̵»ë¤¹¤ë
CacheIgnoreHeaders header-string [header-string] ... None svE
»ØÄꤵ¤ì¤¿ HTTP ¥Ø¥Ã¥À¤ò¥­¥ã¥Ã¥·¥å¤ËÊݸ¤·¤Ê¤¤¡£ +
CacheIgnoreNoLastMod On|Off Off svE
±þÅú¤Ë Last Modified ¤¬Ìµ¤¯¤Æ¤âµ¤¤Ë¤·¤Ê¤¤¤è¤¦¤Ë¤¹¤ë
CacheLastModifiedFactor float 0.1 svE
LastModified ¤ÎÆüÉդ˴ð¤Å¤¤¤ÆÍ­¸ú´ü¸Â (expiry) +¤ò·×»»¤¹¤ë¤¿¤á¤Î½Å¤ß¤ò»ØÄꤹ¤ë +
CacheMaxExpire seconds 86400 (°ìÆü) svE
¥É¥­¥å¥á¥ó¥È¤ò¥­¥ã¥Ã¥·¥å¤¹¤ëºÇÂç»þ´Ö¤òÉÿô¤Ç¸½¤·¤¿¤â¤Î
CacheMaxFileSize bytes 1000000 svE
¥­¥ã¥Ã¥·¥å¤ËÊݴɤµ¤ì¤ë¥É¥­¥å¥á¥ó¥È¤ÎºÇÂç¤Î (¥Ð¥¤¥È¤Ç¤Î) ¥µ¥¤¥º
CacheMinFileSize bytes 1 svE
¥­¥ã¥Ã¥·¥å¤ËÊݴɤµ¤ì¤ë¥É¥­¥å¥á¥ó¥È¤ÎºÇ¾®¸Â¤Î (¥Ð¥¤¥È¤Ç¤Î) Â礭¤µ
CacheNegotiatedDocs On|Off Off svB
¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤µ¤ì¤¿¥É¥­¥å¥á¥ó¥È¤ò¥×¥í¥­¥·¥µ¡¼¥Ð¤¬ +¥­¥ã¥Ã¥·¥å¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë
CacheRoot directorysvE
¥­¥ã¥Ã¥·¥å¥Õ¥¡¥¤¥ë¤¬Êݴɤµ¤ì¤ë¥ë¡¼¥È¥Ç¥£¥ì¥¯¥È¥ê
CacheStoreNoStore On|Off Off svE
no-store ¤È»ØÄꤵ¤ì¤Æ¤¤¤ë¥ì¥¹¥Ý¥ó¥¹¤Î¥­¥ã¥Ã¥·¥å¤ò»î¤ß¤ë¡£
CacheStorePrivate On|Off Off svE
private ¤È»ØÄꤵ¤ì¤Æ¤¤¤ë¥ì¥¹¥Ý¥ó¥¹¤Î¥­¥ã¥Ã¥·¥å¤ò»î¤ß¤ë¡£
CGIMapExtension cgi-path .extensiondhC
CGI ¥¹¥¯¥ê¥×¥È¤Î¥¤¥ó¥¿¡¼¥×¥ê¥¿¤Î°ÌÃÖ¤òÄ´¤Ù¤ë¤¿¤á¤Î¼êË¡
CharsetDefault charsetsvdhX
Charset to translate into
CharsetOptions option [option] ... DebugLevel=0 NoImpl +svdhX
Configures charset translation behavior
CharsetSourceEnc charsetsvdhX
Source charset of files
CheckSpelling on|off Off svdhE
spelling ¥â¥¸¥å¡¼¥ë¤ò»ÈÍѤ¹¤ë¤è¤¦¤Ë¤¹¤ë
ContentDigest On|Off Off svdhC
Content-MD5 HTTP ±þÅú¥Ø¥Ã¥À¤ÎÀ¸À®¤òÍ­¸ú¤Ë¤¹¤ë
CookieDomain domainsvdhE
The domain to which the tracking cookie applies
CookieExpires expiry-periodsvdhE
Expiry time for the tracking cookie
CookieLog filenamesvB
¥¯¥Ã¥­¥ó¥°¤Î¥í¥®¥ó¥°¤Î¤¿¤á¤Î¥Õ¥¡¥¤¥ë̾¤òÀßÄꤹ¤ë
CookieName token Apache svdhE
Name of the tracking cookie
CookieStyle + Netscape|Cookie|Cookie2|RFC2109|RFC2965 Netscape svdhE
Format of the cookie header field
CookieTracking on|off off svdhE
Enables tracking cookie
CoreDumpDirectory directorysM
Apache ¤¬¥³¥¢¥À¥ó¥×¤¹¤ëÁ°¤Ë°ÜÆ°¤ò»î¤ß¤ë¥Ç¥£¥ì¥¯¥È¥ê +
CustomLog file|pipe +format|nickname +[env=[!]environment-variable]svB
¥í¥°¥Õ¥¡¥¤¥ë¤Î̾Á°¤È½ñ¼°¤òÀßÄꤹ¤ë
Dav On|Off|provider-name Off dE
WebDAV HTTP ¥á¥½¥Ã¥É¤òÍ­¸ú¤Ë¤·¤Þ¤¹
DavDepthInfinity on|off off svdE
PROPFIND, Depth: Infinity ¥ê¥¯¥¨¥¹¥È¤òµö²Ä¤·¤Þ¤¹
DavGenericLockDB file-pathsvdE
DAV ¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¾ì½ê
DavLockDB file-pathsvE
DAV ¥í¥Ã¥¯¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î°ÌÃÖ
DavMinTimeout seconds 0 svdE
¥µ¡¼¥Ð¤¬ DAV ¥ê¥½¡¼¥¹¤Î¥í¥Ã¥¯¤ò°Ý»ý¤¹¤ëºÇ¾®»þ´Ö¤Ç¤¹¡£ +
DBDExptime time-in-secondssvE
Keepalive time for idle connections
DBDKeep numbersvE
Maximum sustained number of connections
DBDMax numbersvE
Maximum number of connections
DBDMin numbersvE
Minimum number of connections
DBDParams +param1=value1[,param2=value2]svE
Parameters for database connection
DBDPersist 0|1svE
Whether to use persistent connections
DBDPrepareSQL "SQL statement" labelsvE
Define an SQL prepared statement
DBDriver namesvE
Specify an SQL driver
DefaultIcon url-pathsvdhB
ÆÃÄê¤Î¥¢¥¤¥³¥ó¤¬²¿¤âÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤»þ¤Ë +¥Õ¥¡¥¤¥ë¤Ëɽ¼¨¤¹¤ë¥¢¥¤¥³¥ó
DefaultLanguage MIME-langsvdh
¤¢¤ë¥¹¥³¡¼¥×¤Î¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò»ØÄꤵ¤ì¤¿¸À¸ì¤Ë +ÀßÄꤹ¤ë
DefaultType MIME-type text/plain svdhC
¥µ¡¼¥Ð¤¬¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ò·èÄê¤Ç¤­¤Ê¤¤¤È¤­¤Ë +Á÷¤é¤ì¤ë MIME ¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×
DeflateBufferSize value 8096 svE
zlib ¤¬°ìÅ٤˰µ½Ì¤¹¤ë²ô¤ÎÂ礭¤µ
DeflateCompressionLevel valuesvE
½ÐÎϤËÂФ·¤Æ¹Ô¤Ê¤¦°µ½Ì¤ÎÄøÅÙ
DeflateFilterNote [type] notenamesvE
¥í¥®¥ó¥°ÍѤ˰µ½ÌÈæ¤ò¥á¥â¤ËÄɲÃ
DeflateMemLevel value 9 svE
zlib ¤¬°µ½Ì¤Ë»È¤¦¥á¥â¥ê¤Î¥ì¥Ù¥ë¤ò»ØÄê
DeflateWindowSize value 15 svE
Zlib ¤Î°µ½ÌÍÑ¥¦¥£¥ó¥É¥¦¤ÎÂ礭¤µ
Deny from all|host|env=env-variable +[host|env=env-variable] ...dhB
¥µ¡¼¥Ð¤¬¥¢¥¯¥»¥¹¤òµñÈݤ¹¤ë¥Û¥¹¥È¤òÀ©¸æ¤¹¤ë
<Directory directory-path> +... </Directory>svC
»ØÄê¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ç¥£¥ì¥¯¥È¥ê¤È¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤È¤Î¤ß¤Ë +ŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
DirectoryIndex + local-url [local-url] ... index.html svdhB
¥¯¥é¥¤¥¢¥ó¥È¤¬¥Ç¥£¥ì¥¯¥È¥ê¤ò¥ê¥¯¥¨¥¹¥È¤·¤¿¤È¤­¤ËÄ´¤Ù¤ë +¥ê¥½¡¼¥¹¤Î¥ê¥¹¥È
<DirectoryMatch regex> +... </DirectoryMatch>svC
Àµµ¬É½¸½¤Ë¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ç¥£¥ì¥¯¥È¥ê¤È +¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤È¤Î¤ß¤ËŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
DirectorySlash On|Off On svdhB
¥Ñ¥¹ËöÈø¤Î¥¹¥é¥Ã¥·¥å¤Ç¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤«¤É¤¦¤«¤Î¥ª¥ó¥ª¥Õ¤ò¥È¥°¥ë¤µ¤»¤ë
DocumentRoot directory-path /usr/local/apache/h +svC
¥¦¥§¥Ö¤«¤é¸«¤¨¤ë¥á¥¤¥ó¤Î¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼¤Ë¤Ê¤ë +¥Ç¥£¥ì¥¯¥È¥ê
DumpIOInput On|Off Off sE
¥¨¥é¡¼¥í¥°¤Ë¤¹¤Ù¤Æ¤ÎÆþÎϥǡ¼¥¿¤ò¥À¥ó¥×
DumpIOOutput On|Off Off sE
¥¨¥é¡¼¥í¥°¤Ë¤¹¤Ù¤Æ¤Î½ÐÎϥǡ¼¥¿¤ò¥À¥ó¥×
EnableExceptionHook On|Off Off sM
¥¯¥é¥Ã¥·¥å¤Î¸å¤ËÎã³°¥Ï¥ó¥É¥é¤ò¼Â¹Ô¤¹¤ë¥Õ¥Ã¥¯¤òÍ­¸ú¤Ë¤¹¤ë
EnableMMAP On|Off On svdhC
ÇÛÁ÷Ãæ¤Ë¥Õ¥¡¥¤¥ë¤òÆɤ߹þ¤à¤¿¤á¤Ë¥á¥â¥ê¥Þ¥Ã¥Ô¥ó¥°¤ò +»È¤¦¤«¤É¤¦¤«
EnableSendfile On|Off On svdhC
¥Õ¥¡¥¤¥ë¤Î¥¯¥é¥¤¥¢¥ó¥È¤Ø¤ÎÇÛÁ÷»þ¤Ë¥«¡¼¥Í¥ë¤Î sendfile ¥µ¥Ý¡¼¥È¤ò +»È¤¦¤«¤É¤¦¤«
ErrorDocument error-code documentsvdhC
¥¨¥é¡¼¤¬È¯À¸¤·¤¿¤È¤­¤Ë¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ë¤â¤Î
ErrorLog file-path|syslog[:facility] logs/error_log (Uni +svC
¥µ¡¼¥Ð¤¬¥¨¥é¡¼¤ò¥í¥°¼ý½¸¤¹¤ë¾ì½ê
ExamplesvdhX
Demonstration directive to illustrate the Apache module +API
ExpiresActive On|OffsvdhE
Expires ¥Ø¥Ã¥À¤ÎÀ¸À®¤òÍ­¸ú¤Ë¤¹¤ë
ExpiresByType MIME-type +<code>secondssvdhE
MIME ¥¿¥¤¥×¤Ë¤è¤Ã¤ÆÀßÄꤵ¤ì¤ë Expires ¥Ø¥Ã¥À¤ÎÃÍ
ExpiresDefault <code>secondssvdhE
´ü¸ÂÀÚ¤ì´üÆü¤ò·×»»¤¹¤ë¥Ç¥Õ¥©¥ë¥È¥¢¥ë¥´¥ê¥º¥à
ExtendedStatus On|Off Off sB
³Æ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ³ÈÄ¥¥¹¥Æ¡¼¥¿¥¹¾ðÊó¤òÊݸ¤¹¤ë
ExtFilterDefine filtername parameterssE
³°Éô¥Õ¥£¥ë¥¿¤òÄêµÁ
ExtFilterOptions option [option] ... DebugLevel=0 NoLogS +dE
mod_ext_filter ¤Î¥ª¥×¥·¥ç¥ó¤òÀßÄê
FileETag component ... INode MTime Size svdhC
ETag HTTP ±þÅú¥Ø¥Ã¥À¤òºîÀ®¤¹¤ë¤¿¤á¤Ë»ÈÍѤµ¤ì¤ë +¥Õ¥¡¥¤¥ë¤Î°À­
<Files filename> ... </Files>svdhC
¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë̾¤ËŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
<FilesMatch regex> ... </FilesMatch>svdhC
Àµµ¬É½¸½¤Ë¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë̾¤ËŬÍѤµ¤ì¤ë +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
FilterChain [+=-@!]filter-name ...svdhB
Configure the filter chain
FilterDeclare filter-name [type]svdhB
Declare a smart filter
FilterProtocol filter-name [provider-name] + proto-flagssvdhB
Deal with correct HTTP protocol handling
FilterProvider filter-name provider-name + [req|resp|env]=dispatch matchsvdhB
Register a content filter
FilterTrace filter-name levelsvdB
Get debug/diagnostic information from + mod_filter
ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback] Prefer svdhB
Í×µá¤Ë¹ç¤¦Ã±ÆȤΥɥ­¥å¥á¥ó¥È¤¬¸«¤Ä¤«¤é¤Ê¤«¤Ã¤¿¤È¤­¤Ë¹Ô¤Ê¤¦¤³¤È¤ò»ØÄê +
ForceType MIME-type|NonedhC
¤¹¤Ù¤Æ¤Î¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë¤¬»ØÄê¤Î MIME ¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤Ç +Á÷¤é¤ì¤ë¤è¤¦¤Ë¤¹¤ë
ForensicLog filename|pipesvE
Forensic ¥í¥°¤Î¥Õ¥¡¥¤¥ë̾¤òÀßÄꤹ¤ë
Group unix-group #-1 sM
¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ëºÝ¤Ë½ê°¤¹¤ë¥°¥ë¡¼¥×
Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]svdhE
HTTP ±þÅú¥Ø¥Ã¥À¤ÎÀßÄê
HeaderName filenamesvdhB
+¥¤¥ó¥Ç¥Ã¥¯¥¹°ìÍ÷¤ÎÀèƬ¤ËÁÞÆþ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°
HostnameLookups On|Off|Double Off svdC
¥¯¥é¥¤¥¢¥ó¥È¤Î IP ¥¢¥É¥ì¥¹¤Î DNS ¥ë¥Ã¥¯¥¢¥Ã¥×¤ò +Í­¸ú¤Ë¤¹¤ë
IdentityCheck On|Off Off svdE
Enables logging of the RFC 1413 identity of the remote +user
IdentityCheckTimeout seconds 30 svdE
Determines the timeout duration for ident requests
<IfDefine [!]parameter-name> ... + </IfDefine>svdhC
µ¯Æ°»þ¤Ë¥Æ¥¹¥È¤¬¿¿¤Ç¤¢¤ë¤È¤­¤Î¤ß¤Ë½èÍý¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò +°Ï¤à
<IfModule [!]module-file|module-identifier> ... + </IfModule>svdhC
¥â¥¸¥å¡¼¥ë¤Î¸ºß¤¹¤ë¤«¤·¤Ê¤¤¤«¤Ë±þ¤¸¤Æ½èÍý¤µ¤ì¤ë +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à
<IfVersion [[!]operator] version> ... +</IfVersion>svdhE
¥Ð¡¼¥¸¥ç¥ó°Í¸¤ÎÀßÄê¤òÆþ¤ì¤ë
ImapBase map|referer|URL http://servername/ svdhB
Default base for imagemap files
ImapDefault error|nocontent|map|referer|URL nocontent svdhB
Default action when an imagemap is called with coordinates +that are not explicitly mapped
ImapMenu none|formatted|semiformatted|unformattedsvdhB
Action if no coordinates are given when calling +an imagemap
Include file-path|directory-pathsvdC
¥µ¡¼¥ÐÀßÄê¥Õ¥¡¥¤¥ëÃ椫¤é¾¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò¼è¤ê¹þ¤à
IndexIgnore file [file] ...svdhB
¥Ç¥£¥ì¥¯¥È¥ê°ìÍ÷¤ò¹Ô¤Ê¤¦ºÝ¤Ë̵»ë¤¹¤Ù¤­ +¥Õ¥¡¥¤¥ë¥ê¥¹¥È¤ËÄɲÃ
IndexOptions [+|-]option [[+|-]option] ...svdhB
¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤ÎÍÍ¡¹¤ÊÀßÄê¹àÌÜ +
IndexOrderDefault Ascending|Descending +Name|Date|Size|Description Ascending Name svdhB
+¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤Îɸ½à¤Î½çÈÖÉÕ¤±¤òÀßÄê
IndexStyleSheet url-pathsvdhB
¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ë CSS ¥¹¥¿¥¤¥ë¥·¡¼¥È¤òÄɲ乤ë
ISAPIAppendLogToErrors on|off off svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the error log
ISAPIAppendLogToQuery on|off on svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the query field
ISAPICacheFile file-path [file-path] +...svB
ISAPI .dll files to be loaded at startup
ISAPIFakeAsync on|off off svdhB
Fake asynchronous support for ISAPI callbacks
ISAPILogNotSupported on|off off svdhB
Log unsupported feature requests from ISAPI +extensions
ISAPIReadAheadBuffer size 49152 svdhB
Size of the Read Ahead Buffer sent to ISAPI +extensions
KeepAlive On|Off On svC
HTTP ¤Î»ý³Ū¤ÊÀܳ¤òÍ­¸ú¤Ë¤¹¤ë
KeepAliveTimeout seconds 5 svC
»ý³Ū¤ÊÀܳ¤Ç¼¡¤Î¥ê¥¯¥¨¥¹¥È¤¬Íè¤ë¤Þ¤Ç¥µ¡¼¥Ð¤¬ÂԤĻþ´Ö
LanguagePriority MIME-lang [MIME-lang] +...svdhB
¥¯¥é¥¤¥¢¥ó¥È¤¬Í¥ÀèÅÙ¤ò¼¨¤µ¤Ê¤«¤Ã¤¿¤È¤­¤Î¸À¸ì¤Î variant ¤ÎÍ¥ÀèÅÙ¤ò +»ØÄê
LDAPCacheEntries number 1024 sE
Maximum number of entries in the primary LDAP cache
LDAPCacheTTL seconds 600 sE
Time that cached items remain valid
LDAPConnectionTimeout secondssE
Specifies the socket connection timeout in seconds
LDAPOpCacheEntries number 1024 sE
Number of entries used to cache LDAP compare +operations
LDAPOpCacheTTL seconds 600 sE
Time that entries in the operation cache remain +valid
LDAPSharedCacheFile directory-path/filenamesE
Sets the shared memory cache file
LDAPSharedCacheSize bytes 102400 sE
Size in bytes of the shared-memory cache
LDAPTrustedClientCert type directory-path/filename/nickname [password]svdhE
Sets the file containing or nickname referring to a per +connection client certificate. Not all LDAP toolkits support per +connection client certificates.
LDAPTrustedGlobalCert type directory-path/filename [password]sE
Sets the file or database containing global trusted +Certificate Authority or global client certificates
LDAPTrustedMode typesvE
Specifies the SSL/TLS mode to be used when connecting to an LDAP server.
LDAPVerifyServerCert On|Off On sE
Force server certificate verification
<Limit method [method] ... > ... + </Limit>svdhC
°Ï¤¤¤ÎÃæ¤Ë¤¢¤ë¥¢¥¯¥»¥¹À©¸æ¤ÎŬÍѤòÆÃÄê¤Î HTTP ¥á¥½¥Ã¥É¤Î¤ß¤Ë +À©¸Â¤¹¤ë
<LimitExcept method [method] ... > ... + </LimitExcept>svdhC
»ØÄꤵ¤ì¤¿¤â¤Î°Ê³°¤Î HTTP ¥á¥½¥Ã¥É¤Ë¥¢¥¯¥»¥¹À©¸æ¤ò +À©¸Â¤¹¤ë
LimitInternalRecursion number [number] 10 svC
ÆâÉô¥ê¥À¥¤¥ì¥¯¥È¤ÈÆþ¤ì»Ò¤Ë¤Ê¤Ã¤¿¥µ¥Ö¥ê¥¯¥¨¥¹¥È¤ÎºÇÂç¿ô¤ò·èÄꤹ¤ë
LimitRequestBody bytes 0 svdhC
¥¯¥é¥¤¥¢¥ó¥È¤«¤éÁ÷¤é¤ì¤ë HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ü¥Ç¥£¤Î +ÁíÎ̤òÀ©¸Â¤¹¤ë
LimitRequestFields number 100 sC
¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤Î¿ô¤ò +À©¸Â¤¹¤ë
LimitRequestFieldsize bytessC
¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î HTTP ¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¤Î +¥µ¥¤¥º¤òÀ©¸Â¤¹¤ë
LimitRequestLine bytes 8190 sC
¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î HTTP ¥ê¥¯¥¨¥¹¥È¹Ô¤Î¥µ¥¤¥º¤òÀ©¸Â¤¹¤ë
LimitXMLRequestBody bytes 1000000 svdhC
XML ·Á¼°¤Î¥ê¥¯¥¨¥¹¥È¤Î¥Ü¥Ç¥£¤Î¥µ¥¤¥º¤òÀ©¸Â¤¹¤ë
Listen [IP-address:]portnumber [protocol]sM
¥µ¡¼¥Ð¤¬ listen ¤¹¤ëIP ¥¢¥É¥ì¥¹¤È¥Ý¡¼¥ÈÈÖ¹æ
ListenBacklog backlogsM
ÊÝα¾õÂ֤Υ³¥Í¥¯¥·¥ç¥ó¤Î¥­¥å¡¼¤ÎºÇÂçĹ
LoadFile filename [filename] ...sE
»ØÄꤵ¤ì¤¿¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ä¥é¥¤¥Ö¥é¥ê¤ò¥ê¥ó¥¯¤¹¤ë
LoadModule module filenamesE
¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ä¥é¥¤¥Ö¥é¥ê¤ò¥ê¥ó¥¯¤·¡¢»ÈÍѥ⥸¥å¡¼¥ë¤Î +¥ê¥¹¥È¤ËÄɲ乤ë
<Location + URL-path|URL> ... </Location>svC
°Ï¤ó¤À¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¥Þ¥Ã¥Á¤¹¤ë URL ¤Î¤ß¤ËŬÍÑ
<LocationMatch + regex> ... </LocationMatch>svC
°Ï¤ó¤À¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÀµµ¬É½¸½¤Ë¥Þ¥Ã¥Á¤¹¤ë URL ¤Î¤ß¤Ë +ŬÍÑ
LockFile filename logs/accept.lock sM
¼õÉÕ¤òľÎ󲽤¹¤ë¤¿¤á¤Î¥í¥Ã¥¯¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ
LogFormat format|nickname +[nickname] "%h %l %u %t \"%r\" +svB
¥í¥°¥Õ¥¡¥¤¥ë¤Ç»ÈÍѤ¹¤ë½ñ¼°¤òÀßÄꤹ¤ë
LogLevel level warn svC
ErrorLog ¤Î¾éĹÀ­¤òÀ©¸æ¤¹¤ë
MaxClients numbersM
¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¤¿¤á¤ËºîÀ®¤µ¤ì¤ë +»Ò¥×¥í¥»¥¹¤ÎºÇÂç¸Ä¿ô
MaxKeepAliveRequests number 100 svC
»ý³Ū¤ÊÀܳ¾å¤Çµö²Ä¤µ¤ì¤ë¥ê¥¯¥¨¥¹¥È¤Î¿ô
MaxMemFree KBytes 0 sM
free() ¤¬¸Æ¤Ð¤ì¤Ê¤¤¸Â¤ê¡¢ +¼ç¥á¥â¥ê¥¢¥í¥±¡¼¥¿¤¬ÊÝ»ý¤·Â³¤±¤é¤ì¤ë¥á¥â¥ê¤ÎºÇÂçÎÌ
MaxRequestsPerChild number 10000 sM
¸Ä¡¹¤Î»Ò¥µ¡¼¥Ð¤¬²ÔƯÃæ¤Ë°·¤¦¥ê¥¯¥¨¥¹¥È¿ô¤Î¾å¸Â
MaxRequestsPerThread number 0 sM
Limit on the number of requests that an individual thread +will handle during its life
MaxSpareServers number 10 sM
¥¢¥¤¥É¥ë¤Ê»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤ÎºÇÂç¸Ä¿ô
MaxSpareThreads numbersM
¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¤ÎºÇÂç¿ô
MaxThreads number 2048 sM
Set the maximum number of worker threads
MCacheMaxObjectCount value 1009 sE
¥­¥ã¥Ã¥·¥å¤ËÊݴɤµ¤ì¤ë¥ª¥Ö¥¸¥§¥¯¥È¤ÎºÇÂç¿ô
MCacheMaxObjectSize bytes 10000 sE
¥­¥ã¥Ã¥·¥å¤ËÊݴɤǤ­¤ë¥É¥­¥å¥á¥ó¥È¤ÎºÇÂ祵¥¤¥º (¥Ð¥¤¥È)
MCacheMaxStreamingBuffer size_in_bytes of 100000 ¤« MCacheM +sE
¥¹¥È¥ê¡¼¥à¤µ¤ì¤Æ¤¤¤ë±þÅú¤ò¥­¥ã¥Ã¥·¥åÉÔǽ¤È·èÄꤹ¤ë¤Þ¤Ç¤Ë +¥á¥â¥ê¤Ë¥Ð¥Ã¥Õ¥¡¤¹¤ëºÇÂçÎÌ
MCacheMinObjectSize bytes 0 sE
¥­¥ã¥Ã¥·¥å¤ËÊݴɤµ¤ì¤ë¥É¥­¥å¥á¥ó¥È¤ÎºÇ¾®¥µ¥¤¥º (¥Ð¥¤¥È)
MCacheRemovalAlgorithm LRU|GDSF GDSF sE
¥­¥ã¥Ã¥·¥å¤«¤éºï½ü¤¹¤ë¥É¥­¥å¥á¥ó¥È¤òÁª¤Ö¤¿¤á¤Î¥¢¥ë¥´¥ê¥º¥à
MCacheSize KBytes 100 sE
¥­¥ã¥Ã¥·¥å¤Ë»È¤ï¤ì¤ë¥á¥â¥ê¤ÎºÇÂçÎ̤ò¥Ð¥¤¥Èñ°Ì¤Ç»ØÄê
MetaDir directory .web svdhE
Name of the directory to find CERN-style meta information +files
MetaFiles on|off off svdhE
Activates CERN meta-file processing
MetaSuffix suffix .meta svdhE
File name suffix for the file containg CERN-style +meta information
MimeMagicFile file-pathsvE
Enable MIME-type determination based on file contents +using the specified magic file
MinSpareServers number 5 sM
¥¢¥¤¥É¥ë¤Ê»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤ÎºÇ¾®¸Ä¿ô
MinSpareThreads numbersM
¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¤³¤È¤Î¤Ç¤­¤ë +¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¿ô¤ÎºÇ¾®¿ô
MMapFile file-path [file-path] ...sX
Map a list of files into memory at startup time
ModMimeUsePathInfo On|Off Off d
path_info ¥³¥ó¥Ý¡¼¥Í¥ó¥È¤ò¥Õ¥¡¥¤¥ë̾¤Î°ìÉô¤È¤·¤Æ°·¤¦¤è¤¦¤Ë +mod_mime ¤ËÄÌÃΤ¹¤ë
MultiviewsMatch Any|NegotiatedOnly|Filters|Handlers +[Handlers|Filters] NegotiatedOnly svdh
MultiViews ¤Ç¤Î¥Þ¥Ã¥Á¥ó¥°¤Î¸¡º÷¤Ë´Þ¤Þ¤»¤ë +¥Õ¥¡¥¤¥ë¤Î¥¿¥¤¥×¤ò»ØÄꤹ¤ë
NameVirtualHost addr[:port]sC
̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¤¿¤á¤Î IP ¥¢¥É¥ì¥¹¤ò»ØÄê
NoProxy host [host] ...svE
ľÀÜÀܳ¤¹¤ë ¥Û¥¹¥È¡¢¥É¥á¥¤¥ó¡¢¥Í¥Ã¥È¥ï¡¼¥¯
NWSSLTrustedCerts filename [filename] ...sB
List of additional client certificates
NWSSLUpgradeable [IP-address:]portnumbersB
Allows a connection to be upgraded to an SSL connection upon request
Options + [+|-]option [[+|-]option] ... All svdhC
¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ·¤Æ»ÈÍѲÄǽ¤Êµ¡Ç½¤òÀßÄꤹ¤ë
Order ordering Deny,Allow dhB
¥Ç¥Õ¥©¥ë¥È¤Î¥¢¥¯¥»¥¹²Äǽ¤Ê¾õÂ֤ȡ¢Allow ¤È +Deny ¤¬É¾²Á¤µ¤ì¤ë½çÈÖ¤òÀ©¸æ¤¹¤ë
PassEnv env-variable [env-variable] +...svdhB
¥·¥§¥ë¤«¤é¤Î´Ä¶­ÊÑ¿ô¤òÅϤ¹
PidFile filename logs/httpd.pid sM
¥Ç¡¼¥â¥ó¤Î¥×¥í¥»¥¹ ID +¤ò¥µ¡¼¥Ð¤¬µ­Ï¿¤¹¤ë¤¿¤á¤Î¥Õ¥¡¥¤¥ë
ProtocolEcho On|OffsvX
¥¨¥³¡¼¥µ¡¼¥Ð¤ÎÍ­¸ú̵¸ú¤òÀßÄꤷ¤Þ¤¹¡£
<Proxy wildcard-url> ...</Proxy>svE
¥×¥í¥­¥·¤µ¤ì¤ë¥ê¥½¡¼¥¹¤ËŬÍѤµ¤ì¤ë¥³¥ó¥Æ¥Ê
ProxyBadHeader IsError|Ignore|StartBody IsError svE
±þÅú¤Ë¤ª¤«¤·¤Ê¥Ø¥Ã¥À¤¬¤¢¤ë¾ì¹ç¤Î°·¤¤Êý¤ò·è¤á¤ë
ProxyBlock *|word|host|domain +[word|host|domain] ...svE
¥×¥í¥­¥·Àܳ¤ò¶Ø»ß¤¹¤ë¸ì¶ç¡¢¥Û¥¹¥È̾¡¢¥É¥á¥¤¥ó¤ò»ØÄꤹ¤ë
ProxyDomain DomainsvE
¥×¥í¥­¥·¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î¥Ç¥Õ¥©¥ë¥È¤Î¥É¥á¥¤¥ó̾
ProxyErrorOverride On|Off Off svE
¥×¥í¥­¥·¤µ¤ì¤¿¥³¥ó¥Æ¥ó¥Ä¤Î¥¨¥é¡¼¥Ú¡¼¥¸¤ò¾å½ñ¤­¤¹¤ë
ProxyIOBufferSize bytes 8192 svE
ÆâÉô¥Ç¡¼¥¿¥¹¥ë¡¼¥×¥Ã¥È¥Ð¥Ã¥Õ¥¡¤Î¥µ¥¤¥º¤ò·èÄꤹ¤ë
<ProxyMatch regex> ...</ProxyMatch>svE
Àµµ¬É½¸½¤Ç¤Î¥Þ¥Ã¥Á¤Ë¤è¤ë¥×¥í¥­¥·¥ê¥½¡¼¥¹ÍѤΥǥ£¥ì¥¯¥Æ¥£¥Ö¥³¥ó¥Æ¥Ê
ProxyMaxForwards number 10 svE
¥ê¥¯¥¨¥¹¥È¤¬¥Õ¥©¥ï¡¼¥É¤µ¤ì¤ë¥×¥í¥­¥·¤ÎºÇÂç¿ô
ProxyPass [path] !|url [key=value key=value ...]]svdE
¥ê¥â¡¼¥È¥µ¡¼¥Ð¤ò¥í¡¼¥«¥ë¥µ¡¼¥Ð¤Î URL ¶õ´Ö¤Ë¥Þ¥Ã¥×¤¹¤ë
ProxyPassReverse [path] urlsvdE
¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤µ¤ì¤¿¥µ¡¼¥Ð¤«¤éÁ÷¤é¤ì¤¿ HTTP ±þÅú¥Ø¥Ã¥À¤Î +URL ¤òÄ´À°¤¹¤ë
ProxyPassReverseCookieDomain internal-domain public-domainsvdE
¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¥µ¡¼¥Ð¤«¤é¤Î Set-Cookie ¥Ø¥Ã¥À¤Î Domain ʸ»úÎó¤ò +Ä´À°¤¹¤ë
ProxyPassReverseCookiePath internal-path public-pathsvdE
Reverse ¥×¥í¥­¥·¥µ¡¼¥Ð¤«¤é¤Î Set-Cookie ¥Ø¥Ã¥À¤Î Path ʸ»úÎó¤ò +Ä´À°¤¹¤ë
ProxyPreserveHost On|Off Off svE
¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤Ë¡¢¼õ¤±ÉÕ¤±¤¿ Host HTTP ¥Ø¥Ã¥À¤ò»È¤¦
ProxyReceiveBufferSize bytes 0 svE
¥×¥í¥­¥·¤µ¤ì¤ë HTTP ¤È FTP Àܳ¤Î¤¿¤á¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥Ð¥Ã¥Õ¥¡¥µ¥¤¥º
ProxyRemote match remote-serversvE
ÆÃÄê¤Î¥ê¥¯¥¨¥¹¥È¤ò°·¤¦»þ¤Ë»È¤ï¤ì¤ë¥ê¥â¡¼¥È¥×¥í¥­¥·¤ò»ØÄꤹ¤ë
ProxyRemoteMatch regex remote-serversvE
Àµµ¬É½¸½¤Ç¤Î¥Þ¥Ã¥Á¤Ë¤è¤ë¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¥ê¥â¡¼¥È¥×¥í¥­¥·¤Î»ØÄê
ProxyRequests On|Off Off svE
¥Õ¥©¥ï¡¼¥É (ɸ½à¤Î) ¥×¥í¥­¥·¥ê¥¯¥¨¥¹¥È¤òÍ­¸ú¤Ë¤¹¤ë
ProxyTimeout seconds 300 svE
¥×¥í¥­¥·¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¿¥¤¥à¥¢¥¦¥È
ProxyVia On|Off|Full|Block Off svE
¥×¥í¥­¥·¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î Via HTTP ±þÅú¥Ø¥Ã¥À +¤Ë¤è¤êÄ󶡤µ¤ì¤ë¾ðÊó
ReadmeName filenamesvdhB
¥¤¥ó¥Ç¥Ã¥¯¥¹°ìÍ÷¤ÎºÇ¸å¤ËÁÞÆþ¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¤Î̾Á°
Redirect [status] URL-path +URLsvdhB
¥¯¥é¥¤¥¢¥ó¥È¤¬°ã¤¦ URL ¤ò¼èÆÀ¤¹¤ë¤è¤¦¤Ë³°Éô¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤ò +Á÷¤ë
RedirectMatch [status] regex +URLsvdhB
¸½ºß¤Î URL ¤Ø¤ÎÀµµ¬É½¸½¤Î¥Þ¥Ã¥Á¤Ë¤è¤ê +³°Éô¤Ø¤Î¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷¤ë
RedirectPermanent URL-path URLsvdhB
¥¯¥é¥¤¥¢¥ó¥È¤¬°ã¤¦ URL ¤ò¼èÆÀ¤¹¤ë¤è¤¦¤Ë³°Éô¤Ø¤Î±Êµ×Ū¤Ê +¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷¤ë
RedirectTemp URL-path URLsvdhB
¥¯¥é¥¤¥¢¥ó¥È¤¬°ã¤¦ URL ¤ò¼èÆÀ¤¹¤ë¤è¤¦¤Ë³°Éô¤Ø¤Î°ì»þŪ¤Ê +¥ê¥À¥¤¥ì¥¯¥È¤òÁ÷¤ë
RemoveCharset extension [extension] +...vdh
¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¤¹¤Ù¤Æ¤Îʸ»ú¥»¥Ã¥È +¤ò²ò½ü¤¹¤ë
RemoveEncoding extension [extension] +...vdh
¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¤¹¤Ù¤Æ¤Î¥³¥ó¥Æ¥ó¥È¥¨¥ó¥³¡¼¥Ç¥£¥ó¥° +¤ò²ò½ü¤¹¤ë
RemoveHandler extension [extension] +...vdh
¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¤¹¤Ù¤Æ¤Î¥Ï¥ó¥É¥é¤ò +²ò½ü¤¹¤ë
RemoveInputFilter extension [extension] +...vdh
¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿ÆþÎÏ¥Õ¥£¥ë¥¿¤ò²ò½ü¤¹¤ë
RemoveLanguage extension [extension] +...vdh
¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿¸À¸ì¤ò²ò½ü¤¹¤ë
RemoveOutputFilter extension [extension] +...vdh
¥Õ¥¡¥¤¥ë³ÈÄ¥»Ò¤Ë´ØÏ¢ÉÕ¤±¤é¤ì¤¿½ÐÎÏ¥Õ¥£¥ë¥¿¤ò²ò½ü¤¹¤ë
RemoveType extension [extension] +...vdh
¥Õ¥¡¥¤¥ë¤Î³ÈÄ¥»Ò¤È´ØÏ¢ÉÕ¤±¤é¤ì¤¿¥³¥ó¥Æ¥ó¥È¥¿¥¤¥×¤ò +²ò½ü¤¹¤ë
RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]svdhE
HTTP ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤ÎÀßÄê
Require entity-name [entity-name] ...dhC
¤É¤Îǧ¾ÚºÑ¤ß¥æ¡¼¥¶¤¬¥ê¥½¡¼¥¹¤ò¥¢¥¯¥»¥¹¤Ç¤­¤ë¤«¤òÁªÂò¤¹¤ë
RewriteBase URL-pathdhE
Sets the base URL for per-directory rewrites
RewriteCond + TestString CondPatternsvdhE
Defines a condition under which rewriting will take place +
RewriteEngine on|off off svdhE
Enables or disables runtime rewriting engine
RewriteLock file-pathsE
Sets the name of the lock file used for RewriteMap +synchronization
RewriteLog file-pathsvE
Sets the name of the file used for logging rewrite engine +processing
RewriteLogLevel Level 0 svE
Sets the verbosity of the log file used by the rewrite +engine
RewriteMap MapName MapType:MapSource +svE
Defines a mapping function for key-lookup
RewriteOptions OptionssvdhE
Sets some special options for the rewrite engine
RewriteRule + Pattern SubstitutionsvdhE
Defines rules for the rewriting engine
RLimitCPU seconds|max [seconds|max]svdhC
Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤éµ¯Æ°¤µ¤ì¤¿¥×¥í¥»¥¹¤Î CPU ¾ÃÈñÎ̤ò +À©¸Â¤¹¤ë
RLimitMEM bytes|max [bytes|max]svdhC
Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤éµ¯Æ°¤µ¤ì¤¿¥×¥í¥»¥¹¤Î¥á¥â¥ê¾ÃÈñÎ̤ò +À©¸Â¤¹¤ë
RLimitNPROC number|max [number|max]svdhC
Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤éµ¯Æ°¤µ¤ì¤¿¥×¥í¥»¥¹¤¬µ¯Æ°¤¹¤ë¥×¥í¥»¥¹¤Î +¿ô¤òÀ©¸Â¤¹¤ë
Satisfy Any|All All dhC
¥Û¥¹¥È¥ì¥Ù¥ë¤Î¥¢¥¯¥»¥¹À©¸æ¤È¥æ¡¼¥¶Ç§¾Ú¤È¤ÎÁê¸ßºîÍѤò»ØÄê
ScoreBoardFile file-path logs/apache_status sM
»Ò¥×¥í¥»¥¹¤ÈÏ¢·È¤¹¤ë¤¿¤á¤Î¥Ç¡¼¥¿¤òÊݸ¤¹¤ë +¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ
Script method cgi-scriptsvdB
ÆÃÄê¤Î¥ê¥¯¥¨¥¹¥È¥á¥½¥Ã¥É¤ËÂФ·¤Æ CGI ¥¹¥¯¥ê¥×¥È¤ò +¼Â¹Ô¤¹¤ë¤è¤¦¤ËÀßÄê
ScriptAlias URL-path +file-path|directory-pathsvB
URL ¤ò¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤إޥåפ·¡¢¥Þ¥Ã¥×Àè¤ò +CGI ¥¹¥¯¥ê¥×¥È¤Ë»ØÄê
ScriptAliasMatch regex +file-path|directory-pathsvB
URL ¤òÀµµ¬É½¸½¤ò»È¤Ã¤Æ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ÌÃ֤إޥåפ·¡¢¥Þ¥Ã¥×Àè¤ò +CGI ¥¹¥¯¥ê¥×¥È¤Ë»ØÄê
ScriptInterpreterSource Registry|Registry-Strict|Script Script svdhC
CGI ¥¹¥¯¥ê¥×¥È¤Î¥¤¥ó¥¿¡¼¥×¥ê¥¿¤Î°ÌÃÖ¤òÄ´¤Ù¤ë¤¿¤á¤Î¼êË¡
ScriptLog file-pathsvB
CGI ¥¹¥¯¥ê¥×¥È¤Î¥¨¥é¡¼¥í¥°¥Õ¥¡¥¤¥ë¤Î¾ì½ê
ScriptLogBuffer bytes 1024 svB
¥¹¥¯¥ê¥×¥È¥í¥°¤Ëµ­Ï¿¤µ¤ì¤ë PUT ¤ä POST ¥ê¥¯¥¨¥¹¥È¤ÎÆâÍƤξå¸Â
ScriptLogLength bytes 10385760 svB
CGI ¥¹¥¯¥ê¥×¥È¤Î¥í¥°¥Õ¥¡¥¤¥ë¤ÎÂ礭¤µ¤Î¾å¸Â
ScriptSock file-path logs/cgisock svB
CGI ¥Ç¡¼¥â¥ó¤È¤ÎÄÌ¿®¤Ë»È¤ï¤ì¤ë¥½¥±¥Ã¥È¤Î̾Á°
SecureListen [IP-address:]portnumber +Certificate-Name [MUTUAL]sB
Enables SSL encryption for the specified port
SendBufferSize bytes 0 sM
TCP ¥Ð¥Ã¥Õ¥¡¥µ¥¤¥º
ServerAdmin email-address|URLsvC
¥µ¡¼¥Ð¤¬¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ë¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Ë´Þ¤á¤ëÅŻҥ᡼¥ë¤Î +¥¢¥É¥ì¥¹
ServerAlias hostname [hostname] ...vC
¥ê¥¯¥¨¥¹¥È¤ò̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¥Þ¥Ã¥Á¤µ¤»¤Æ¤¤¤ë¤È¤­¤Ë +»ÈÍѤµ¤ì¤ë¥Û¥¹¥È¤ÎÊÌ̾
ServerLimit numbersM
ÀßÄê²Äǽ¤Ê¥µ¡¼¥Ð¥×¥í¥»¥¹¿ô¤Î¾å¸Â
ServerName fully-qualified-domain-name[:port]svC
¥µ¡¼¥Ð¤¬¼«Ê¬¼«¿È¤ò¼¨¤¹¤È¤­¤Ë»È¤¦¥Û¥¹¥È̾¤È¥Ý¡¼¥È
ServerPath URL-pathvC
Èó¸ß´¹¤Î¥Ö¥é¥¦¥¶¤¬Ì¾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¥¢¥¯¥»¥¹¤·¤¿¤È¤­¤Î +¤¿¤á¤Î¸ß´¹ÍÑ URL ¥Ñ¥¹Ì¾
ServerRoot directory-path /usr/local/apache sC
¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤¿¥µ¡¼¥Ð¤Î¥Ù¡¼¥¹¥Ç¥£¥ì¥¯¥È¥ê
ServerSignature On|Off|EMail Off svdhC
¥µ¡¼¥Ð¤¬À¸À®¤¹¤ë¥É¥­¥å¥á¥ó¥È¤Î¥Õ¥Ã¥¿¤òÀßÄê
ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full Full sC
Server HTTP ±þÅú¥Ø¥Ã¥À¤òÀßÄꤹ¤ë
SetEnv env-variable valuesvdhB
´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë
SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
¥ê¥¯¥¨¥¹¥È¤Î°À­¤Ë´ð¤Å¤¤¤Æ´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë +
SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
¥ê¥¯¥¨¥¹¥È¤Î°À­¤Ë´ð¤Å¤¤¤ÆÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¤Ë´Ä¶­ÊÑ¿ô¤òÀßÄꤹ¤ë
SetHandler handler-name|NonesvdhC
¥Þ¥Ã¥Á¤¹¤ë¥Õ¥¡¥¤¥ë¤¬¥Ï¥ó¥É¥é¤Ç½èÍý¤µ¤ì¤ë¤è¤¦¤Ë¤¹¤ë
SetInputFilter filter[;filter...]svdhC
¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ä POST ¤ÎÆþÎϤò½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤òÀßÄꤹ¤ë
SetOutputFilter filter[;filter...]svdhC
¥µ¡¼¥Ð¤Î±þÅú¤ò½èÍý¤¹¤ë¥Õ¥£¥ë¥¿¤òÀßÄꤹ¤ë
SSIEndTag tag "-->" svB
include Í×ÁǤò½ªÎ»¤µ¤»¤ëʸ»úÎó
SSIErrorMsg message "[an error occurred +svdhB
SSI ¤Î¥¨¥é¡¼¤¬¤¢¤Ã¤¿¤È¤­¤Ëɽ¼¨¤µ¤ì¤ë¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸
SSIStartTag tag "<!--#" svB
include Í×ÁǤò³«»Ï¤¹¤ëʸ»úÎó
SSITimeFormat formatstring "%A, %d-%b-%Y %H:%M +svdhB
ÆüÉÕ¤±¤ò¸½¤¹Ê¸»úÎó¤Î½ñ¼°¤òÀßÄꤹ¤ë
SSIUndefinedEcho string "(none)" svdhB
̤ÄêµÁ¤ÎÊÑ¿ô¤¬ echo ¤µ¤ì¤¿¤È¤­¤Ëɽ¼¨¤µ¤ì¤ëʸ»úÎó
SSLCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Client Auth
SSLCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Client Auth
SSLCADNRequestFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for defining acceptable CA names
SSLCADNRequestPath directory-pathsvE
Directory of PEM-encoded CA Certificates for +defining acceptable CA names
SSLCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Client Auth
SSLCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Client Auth
SSLCertificateChainFile file-pathsvE
File of PEM-encoded Server CA Certificates
SSLCertificateFile file-pathsvE
Server PEM-encoded X.509 Certificate file
SSLCertificateKeyFile file-pathsvE
Server PEM-encoded Private Key file
SSLCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +handshake
SSLCryptoDevice engine builtin sE
Enable use of a cryptographic hardware accelerator
SSLEngine on|off|optional off svE
SSL Engine Operation Switch
SSLHonorCiperOrder flagsvE
Option to prefer the server's cipher preference order
SSLMutex type none sE
Semaphore for internal mutual exclusion of +operations
SSLOptions [+|-]option ...svdhE
Configure various SSL engine run-time options
SSLPassPhraseDialog type builtin sE
Type of pass phrase dialog for encrypted private +keys
SSLProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors
SSLProxyCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Remote Server Auth
SSLProxyCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Remote Server Auth
SSLProxyCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +proxy handshake
SSLProxyEngine on|off off svE
SSL Proxy Engine Operation Switch
SSLProxyMachineCertificateFile filenamesE
File of concatenated PEM-encoded client certificates and keys to be used by the proxy
SSLProxyMachineCertificatePath directorysE
Directory of PEM-encoded client certificates and keys to be used by the proxy
SSLProxyProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors for proxy usage
SSLProxyVerify level none svdhE
Type of remote server Certificate verification
SSLProxyVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Remote Server +Certificate verification
SSLRandomSeed context source +[bytes]sE
Pseudo Random Number Generator (PRNG) seeding +source
SSLRequire expressiondhE
Allow access only when an arbitrarily complex +boolean expression is true
SSLRequireSSLdhE
Deny access when SSL is not used for the +HTTP request
SSLSessionCache type none sE
Type of the global/inter-process SSL Session +Cache
SSLSessionCacheTimeout seconds 300 svE
Number of seconds before an SSL session expires +in the Session Cache
SSLUserName varnamesdhE
Variable name to determine user name
SSLVerifyClient level none svdhE
Type of Client Certificate verification
SSLVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Client +Certificate verification
StartServers numbersM
µ¯Æ°»þ¤ËÀ¸À®¤µ¤ì¤ë»Ò¥µ¡¼¥Ð¥×¥í¥»¥¹¤Î¿ô
StartThreads numbersM
µ¯Æ°»þ¤ËÀ¸À®¤µ¤ì¤ë¥¹¥ì¥Ã¥É¤Î¿ô
SuexecUserGroup User Groupsv
CGI ¥×¥í¥°¥é¥à¤Î¥æ¡¼¥¶¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¡¢¥°¥ë¡¼¥×¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó
ThreadLimit numbersM
ÀßÄê²Äǽ¤Ê»Ò¥×¥í¥»¥¹Ëè¤Î¥¹¥ì¥Ã¥É¿ô¤Î¾å¸Â¤ò +ÀßÄꤷ¤Þ¤¹
ThreadsPerChild numbersM
»Ò¥×¥í¥»¥¹¤½¤ì¤¾¤ì¤ËÀ¸À®¤µ¤ì¤ë¥¹¥ì¥Ã¥É¿ô
ThreadStackSize sizesM
¥¯¥é¥¤¥¢¥ó¥È¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò¼õ¤±»ý¤Ä¥¹¥ì¥Ã¥É¤¬»ÈÍѤ¹¤ë +¥¹¥¿¥Ã¥¯¤Î¥Ð¥¤¥È¿ô
TimeOut seconds 300 sC
³Æ¥¤¥Ù¥ó¥È¤Ë¤Ä¤¤¤Æ¡¢¥ê¥¯¥¨¥¹¥È¤ò¼ºÇÔ¤µ¤»¤ë¤Þ¤Ç¤Ë¥µ¡¼¥Ð¤¬ +ÂԤĻþ´Ö¤òÀßÄê
TraceEnable [on|off|extended] on sC
TRACE ¥á¥½¥Ã¥É¤Î¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë±þÅúÊýË¡¤ò·è¤á¤ë +
TransferLog file|pipesvB
¥í¥°¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ¤ò»ØÄê
TypesConfig file-path conf/mime.types s
mime.types ¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ
UnsetEnv env-variable [env-variable] +...svdhB
´Ä¶­¤«¤éÊÑ¿ô¤ò¼è¤ê½ü¤¯
UseCanonicalName On|Off|Dns Off svdC
¥µ¡¼¥Ð¤¬¼«Ê¬¼«¿È¤Î̾Á°¤È¥Ý¡¼¥È¤ò·èÄꤹ¤ëÊýË¡¤òÀßÄꤹ¤ë
UseCanonicalPhysicalPort On|Off Off svdC
¥µ¡¼¥Ð¤Î̾Á°¤È¥Ý¡¼¥È¤Î²ò·èÊýË¡¤òÀßÄꤹ¤ë
User unix-userid #-1 sM
¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ëºÝ¤ËÍѤ¤¤ë¥æ¡¼¥¶ ID
UserDir directory-filenamesvB
¥æ¡¼¥¶ÀìÍѥǥ£¥ì¥¯¥È¥ê¤Î°ÌÃÖ
VirtualDocumentRoot interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
VirtualDocumentRootIP interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
<VirtualHost + addr[:port] [addr[:port]] + ...> ... </VirtualHost>sC
ÆÃÄê¤Î¥Û¥¹¥È̾¤ä IP ¥¢¥É¥ì¥¹¤Î¤ß¤ËŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò +°Ï¤à
VirtualScriptAlias interpolated-directory|none none svE
Dynamically configure the location of the CGI directory for +a given virtual host
VirtualScriptAliasIP interpolated-directory|none none svE
Dynamically configure the location of the cgi directory for +a given virtual host
Win32DisableAcceptExsM
¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤Î¼õ¤±ÉÕ¤±¤Ë accept() ¤òAcceptEx ¤ÎÂå¤ï¤ê¤Ë»È¤¦
XBitHack on|off|full off svdhB
¼Â¹Ô¥Ó¥Ã¥È¤¬ÀßÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤Î SSI ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò +²òÀϤ¹¤ë
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/quickreference.html.ko.euc-kr b/docs/manual/mod/quickreference.html.ko.euc-kr new file mode 100644 index 00000000..41c9a3f8 --- /dev/null +++ b/docs/manual/mod/quickreference.html.ko.euc-kr @@ -0,0 +1,699 @@ + + + +Áö½Ã¾î ºü¸¥ÂüÁ¶ - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > ¸ðµâ
+

Áö½Ã¾î ºü¸¥ÂüÁ¶

+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ ¼³Á¤Áö½Ã¾î °¢°¢ÀÇ ¿ëµµ, ±âº»°ª, »óÅÂ, + »ç¿ëÀå¼Ò¸¦ º¸¿©ÁØ´Ù. À̵éÀº Áö½Ã¾î »çÀü¿¡¼­ ¼³¸íÇÑ´Ù.

+ +

ù¹ø° ¿­Àº Áö½Ã¾î À̸§°ú ¿ëµµ¸¦ ¾Ë·ÁÁØ´Ù. µÎ¹ø° ¿­Àº + Áö½Ã¾î¿¡ ±âº»°ªÀÌ ÀÖ´Ù¸é ±âº»°ªÀ» º¸¿©ÁØ´Ù. ¸¸¾à ±âº»°ªÀÌ + ³Ê¹« ±æ´Ù¸é, "+" ±âÈ£·Î »ý·«ÇßÀ½À» ¾Ë¸°´Ù.

+ +

¼¼¹ø°¿Í ³×¹ø° ¿­Àº °¢°¢ ¾Æ·¡ Ç¥¿¡ µû¶ó Áö½Ã¾î¸¦ »ç¿ëÇÒ + ¼ö ÀÖ´Â Àå¼Ò¿Í Áö½Ã¾îÀÇ »óŸ¦ ³ªÅ¸³½´Ù.

+
+
+ + + +
 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X  + + + + + +
sÁÖ¼­¹ö¼³Á¤
v°¡»óÈ£½ºÆ®
ddirectory
h.htaccess
 + + + + + + +
CCore
MMPM
BBase
EExtension
XExperimental
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
AcceptFilter protocol accept_filtersC
Configures optimizations for a Protocol's Listener Sockets
AcceptMutex Default|method Default sM
Method that Apache uses to serialize multiple children +accepting requests on network sockets
AcceptPathInfo On|Off|Default Default svdhC
Resources accept trailing pathname information
AccessFileName filename [filename] ... .htaccess svC
Name of the distributed configuration file
Action action-type cgi-script [virtual]svdhB
ƯÁ¤ Çڵ鷯³ª content-type¿¡ ´ëÇØ CGI ½ºÅ©¸³Æ®¸¦ +»ç¿ëÇÑ´Ù
AddAlt string file [file] ...svdhB
ÆÄÀϸíÀ¸·Î ¼±ÅÃÇÑ ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ÆÄÀÏ ¼³¸í±Û
AddAltByEncoding string MIME-encoding +[MIME-encoding] ...svdhB
MIME-encodingÀ¸·Î ¼±ÅÃÇÑ ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ÆÄÀÏ +¼³¸í±Û
AddAltByType string MIME-type +[MIME-type] ...svdhB
MIME content-typeÀ¸·Î ¼±ÅÃÇÑ ¾ÆÀÌÄÜ´ë½Å »ç¿ëÇÒ ÆÄÀÏ +¼³¸í±Û
AddCharset charset extension +[extension] ...svdhB
Maps the given filename extensions to the specified content +charset
AddDefaultCharset On|Off|charset Off svdhC
Default charset parameter to be added when a response +content-type is text/plain or text/html
AddDescription string file [file] ...svdhB
ÆÄÀÏ¿¡ ´ëÇÑ ¼³¸í
AddEncoding MIME-enc extension +[extension] ...svdhB
Maps the given filename extensions to the specified encoding +type
AddHandler handler-name extension +[extension] ...svdhB
Maps the filename extensions to the specified +handler
AddIcon icon name [name] +...svdhB
À̸§À¸·Î ¼±ÅÃÇÑ ÆÄÀÏ¿¡ »ç¿ëÇÒ ¾ÆÀÌÄÜ
AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...svdhB
MIME content-encodingÀ¸·Î ¼±ÅÃÇÑ ÆÄÀÏ¿¡ »ç¿ëÇÒ ¾ÆÀÌÄÜ
AddIconByType icon MIME-type +[MIME-type] ...svdhB
MIME content-typeÀ¸·Î ¼±ÅÃÇÑ ÆÄÀÏ¿¡ »ç¿ëÇÒ ¾ÆÀÌÄÜ
AddInputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +client requests
AddLanguage MIME-lang extension +[extension] ...svdhB
Maps the given filename extension to the specified content +language
AddModuleInfo module-name stringsvE
¸ðµâ¿¡ ´ëÇÑ Ãß°¡ Á¤º¸¸¦ server-info Çڵ鷯°¡ º¸¿©ÁÖµµ·Ï +Ãß°¡ÇÑ´Ù
AddOutputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +responses from the server
AddOutputFilterByType filter[;filter...] +MIME-type [MIME-type] ...svdhC
assigns an output filter to a particular MIME-type
AddType MIME-type extension +[extension] ...svdhB
Maps the given filename extensions onto the specified content +type
Alias URL-path +file-path|directory-pathsvB
URLÀ» ƯÁ¤ ÆÄÀϽýºÅÛ Àå¼Ò·Î ´ëÀÀÇÑ´Ù
AliasMatch regex +file-path|directory-pathsvB
Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ¿© URLÀ» ÆÄÀϽýºÅÛ Àå¼Ò·Î +´ëÀÀÇÑ´Ù
Allow from all|host|env=env-variable +[host|env=env-variable] ...dhB
¼­¹öÀÇ ÀϺο¡ Á¢±ÙÇÒ ¼ö Àִ ȣ½ºÆ®¸¦ ÁöÁ¤ÇÑ´Ù
AllowCONNECT port [port] ... 443 563 svE
Ports that are allowed to CONNECT through the +proxy
AllowEncodedSlashes On|Off Off svC
Determines whether encoded path separators in URLs are allowed to +be passed through
AllowOverride All|None|directive-type +[directive-type] ... All dC
Types of directives that are allowed in +.htaccess files
Anonymous user [user] ...dhE
¾ÏÈ£°Ë»ç¾øÀÌ Á¢±ÙÀ» Çã¿ëÇÒ »ç¿ëÀÚ ¾ÆÀ̵ðµéÀ» +ÁöÁ¤ÇÑ´Ù
Anonymous_LogEmail On|Off On dhE
ÀÔ·ÂÇÑ ¾ÏÈ£¸¦ ¿À·ù·Î±×¿¡ ±â·ÏÇÒÁö ¿©ºÎ
Anonymous_MustGiveEmail On|Off On dhE
¾ÏÈ£°¡ ¾ø¾îµµ °¡´ÉÇÑÁö ¿©ºÎ
Anonymous_NoUserID On|Off Off dhE
»ç¿ëÀÚ ¾ÆÀ̵𰡠¾ø¾îµµ °¡´ÉÇÏÁö ¿©ºÎ
Anonymous_VerifyEmail On|Off Off dhE
¾ÏÈ£°¡ ¿Ã¹Ù¸¥ Çü½ÄÀÇ ÀüÀÚ¿ìÆí ÁÖ¼ÒÀÎÁö °Ë»ç +¿©ºÎ
AuthBasicAuthoritative On|Off On dhB
ÀÎÁõ°ú ±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ¿¡ ³Ñ°ÜÁÙÁö °áÁ¤ÇÑ´Ù
AuthBasicProvider On|Off|provider-name +[provider-name] ... On dhB
ÀÌ À§Ä¡¿¡ ´ëÇÑ ÀÎÁõÁ¦°øÀÚ¸¦ ÁöÁ¤ÇÑ´Ù
AuthDBDUserPWQuery querydE
SQL query to look up a password for a user
AuthDBDUserRealmQuery querydE
SQL query to look up a password hash for a user and realm. +
AuthDBMGroupFile file-pathdhE
ÀÎÁõ¿¡ »ç¿ëÇÒ »ç¿ëÀÚ ±×·ì ¸ñ·ÏÀ» ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º +ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù
AuthDBMType default|SDBM|GDBM|NDBM|DB default dhE
¾ÏÈ£¸¦ ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º ÆÄÀÏ Á¾·ù¸¦ +ÁöÁ¤ÇÑ´Ù
AuthDBMUserFile file-pathdhE
ÀÎÁõÇÒ »ç¿ëÀÚ¿Í ¾ÏÈ£ ¸ñ·ÏÀ» ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º +ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù
AuthDefaultAuthoritative On|Off On dhB
ÀÎÁõÀ» Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
AuthDigestAlgorithm MD5|MD5-sess MD5 dhX
digest authentication¿¡¼­ challenge¿Í response +hash¸¦ °è»êÇÏ´Â ¾Ë°í¸®ÁòÀ» ¼±ÅÃÇÑ´Ù
AuthDigestDomain URI [URI] ...dhX
digest authentication¿¡¼­ °°Àº º¸È£¿µ¿ª¿¡ ¼ÓÇÏ´Â +URIµé
AuthDigestNcCheck On|Off Off sX
¼­¹ö°¡ º¸³»´Â nonce-count¸¦ °Ë»çÇÒÁö ¿©ºÎ
AuthDigestNonceFormat formatdhX
nonce¸¦ ¸¸µå´Â ¹æ¹ýÀ» °áÁ¤ÇÑ´Ù
AuthDigestNonceLifetime seconds 300 dhX
¼­¹ö nonce°¡ À¯È¿ÇÑ ±â°£
AuthDigestProvider On|Off|provider-name +[provider-name] ... On dhX
ÀÌ À§Ä¡¿¡ ´ëÇÑ ÀÎÁõÁ¦°øÀÚ¸¦ ÁöÁ¤ÇÑ´Ù
AuthDigestQop none|auth|auth-int [auth|auth-int] auth dhX
digest authentication°¡ »ç¿ëÇÒ +º¸È£¼öÁØ(quality-of-protection)À» ÁöÁ¤ÇÑ´Ù.
AuthDigestShmemSize size 1000 sX
Ŭ¶óÀ̾ðÆ®¸¦ ÃßÀûÇϱâÀ§ÇØ ÇÒ´çÇÏ´Â °øÀ¯¸Þ¸ð¸®·®
AuthGroupFile file-pathdhB
ÀÎÁõ¿¡ »ç¿ëÇÒ »ç¿ëÀÚ ±×·ì ¸ñ·ÏÀ» ÀúÀåÇÏ´Â ¹®ÀÚÆÄÀϸíÀ» +ÁöÁ¤ÇÑ´Ù
AuthLDAPBindDN distinguished-namedhE
Optional DN to use in binding to the LDAP server
AuthLDAPBindPassword passworddhE
Password used in conjuction with the bind DN
AuthLDAPCharsetConfig file-pathsE
Language to charset conversion configuration file
AuthLDAPCompareDNOnServer on|off on dhE
Use the LDAP server to compare the DNs
AuthLDAPDereferenceAliases never|searching|finding|always Always dhE
When will the module de-reference aliases
AuthLDAPGroupAttribute attributedhE
LDAP attributes used to check for group membership
AuthLDAPGroupAttributeIsDN on|off on dhE
Use the DN of the client username when checking for +group membership
AuthLDAPRemoteUserIsDN on|off off dhE
Use the DN of the client username to set the REMOTE_USER +environment variable
AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]dhE
URL specifying the LDAP search parameters
AuthName auth-domaindhC
Authorization realm for use in HTTP +authentication
<AuthnProviderAlias baseProvider Alias> +... </AuthnProviderAlias>svE
Enclose a group of directives that represent an +extension of a base authentication provider and referenced by +the specified alias
AuthType Basic|DigestdhC
Type of user authentication
AuthUserFile file-pathdhB
ÀÎÁõÇÒ »ç¿ëÀÚ¸í¿Í ¾ÏÈ£ ¸ñ·ÏÀ» ÀúÀåÇÏ´Â ¹®ÀÚÆÄÀϸíÀ» +ÁöÁ¤ÇÑ´Ù
AuthzDBMAuthoritative On|Off On dhE
±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
AuthzDBMType default|SDBM|GDBM|NDBM|DB default dhE
¾ÏÈ£¸¦ ÀúÀåÇÏ´Â µ¥ÀÌÅͺ£À̽º ÆÄÀÏ Á¾·ù¸¦ ÁöÁ¤ÇÑ´Ù
AuthzDefaultAuthoritative On|Off On dhB
±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
AuthzGroupFileAuthoritative On|Off On dhB
±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
AuthzLDAPAuthoritative on|off on dhE
Prevent other authentication modules from +authenticating the user if this one fails
AuthzOwnerAuthoritative On|Off On dhE
±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
AuthzUserAuthoritative On|Off On dhB
±ÇÇѺο©¸¦ Àú¼öÁØ ¸ðµâ·Î ³Ñ°ÜÁÙÁö ¿©ºÎ
BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...svdhB
HTTP User-Agent¿¡ µû¶ó ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù
BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾Ê°í User-Agent¿¡ µû¶ó ȯ°æº¯¼ö¸¦ +¼³Á¤ÇÑ´Ù
CacheDefaultExpire seconds 3600 (one hour) svX
¸¸±â½Ã°£À» ÁöÁ¤ÇÏÁö¾ÊÀº ¹®¼­¸¦ ij½¬ÇÒ ±âº» ±â°£.
CacheDirLength length 2 svX
ÇÏÀ§µð·ºÅ丮¸íÀÇ ¹®ÀÚ°³¼ö
CacheDirLevels levels 3 svX
ij½¬ÀÇ ÇÏÀ§µð·ºÅ丮 ±íÀÌ.
CacheDisable url-stringsvX
ƯÁ¤ URLÀ» ij½¬ÇÏÁö ¾Ê´Â´Ù
CacheEnable cache_type url-stringsvX
ÁöÁ¤ÇÑ ÀúÀå°ü¸®ÀÚ¸¦ »ç¿ëÇÏ¿© ÁöÁ¤ÇÑ URLÀ» ij½¬ÇÑ´Ù
CacheFile file-path [file-path] ...sX
½ÃÀ۽à ¿©·¯ ÆÄÀÏ ÇÚµéÀ» ij½¬ÇÑ´Ù
CacheIgnoreCacheControl On|Off Off svX
Ŭ¶óÀ̾ðÆ®°¡ ij½¬ÇÏÁö¾Ê´Â ³»¿ëÀ» ¿äûÇÔÀ» ¹«½ÃÇÑ´Ù.
CacheIgnoreHeaders header-string [header-string] ... None svX
ij½¬¿¡ ÁöÁ¤ÇÑ HTTP Çì´õ(µé)¸¦ ÀúÀåÇÏÁö ¾Ê´Â´Ù +
CacheIgnoreNoLastMod On|Off Off svX
ÀÀ´ä¿¡ Last Modified Çì´õ°¡ ¾ø´Ù´Â »ç½ÇÀ» ¹«½ÃÇÑ´Ù.
CacheLastModifiedFactor float 0.1 svX
LastModified ½Ã°£À¸·Î ¸¸±â½Ã°£À» °è»êÇϴµ¥ »ç¿ëÇÏ´Â +°è¼ö.
CacheMaxExpire seconds 86400 (ÇÏ·ç) svX
¹®¼­¸¦ ij½¬ÇÏ´Â ÃÊ´ÜÀ§ ÃÖ´ë½Ã°£
CacheMaxFileSize bytes 1000000 svX
ij½¬¿¡ ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ´ëÅ©±â (¹ÙÀÌÆ® ´ÜÀ§)
CacheMinFileSize bytes 1 svX
ij½¬¿¡ ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ¼ÒÅ©±â (¹ÙÀÌÆ® ´ÜÀ§)
CacheNegotiatedDocs On|Off Off svB
Allows content-negotiated documents to be +cached by proxy servers
CacheRoot directorysvX
ij½¬ ÆÄÀÏÀ» ÀúÀåÇÒ µð·ºÅ丮 root
CGIMapExtension cgi-path .extensiondhC
Technique for locating the interpreter for CGI +scripts
CharsetDefault charsetsvdhX
º¯È¯ÇÒ ¹®ÀÚÁýÇÕ
CharsetOptions option [option] ... DebugLevel=0 NoImpl +svdhX
¹®ÀÚÁýÇÕ º¯È¯ ±â´ÉÀ» ¼³Á¤
CharsetSourceEnc charsetsvdhX
ÆÄÀÏ ¿øº»ÀÇ ¹®ÀÚÁýÇÕ
CheckSpelling on|off Off svdhE
¸ÂÃã¹ý ¸ðµâÀ» »ç¿ëÇÑ´Ù
ContentDigest On|Off Off svdhC
Enables the generation of Content-MD5 HTTP Response +headers
CookieDomain domainsvdhE
The domain to which the tracking cookie applies
CookieExpires expiry-periodsvdhE
Expiry time for the tracking cookie
CookieLog filenamesvB
ÄíÅ°¸¦ ·Î±×¿¡ ³²±â±âÀ§ÇØ »ç¿ëÇÒ ÆÄÀϸíÀ» ¼³Á¤ÇÑ´Ù
CookieName token Apache svdhE
Name of the tracking cookie
CookieStyle + Netscape|Cookie|Cookie2|RFC2109|RFC2965 Netscape svdhE
Format of the cookie header field
CookieTracking on|off off svdhE
Enables tracking cookie
CoreDumpDirectory directorysM
Directory where Apache attempts to +switch before dumping core
CustomLog file|pipe +format|nickname +[env=[!]environment-variable]svB
·Î±×ÆÄÀÏ À̸§°ú Çü½ÄÀ» ÁöÁ¤ÇÑ´Ù
Dav On|Off|provider-name Off dE
WebDAV HTTP ¸Þ½áµå¸¦ ½ÃÀÛÇÑ´Ù
DavDepthInfinity on|off off svdE
PROPFINDÀÇ Depth: Infinity ¿äûÀ» Çã°¡ÇÑ´Ù
DavGenericLockDB file-pathsvdE
Location of the DAV lock database
DavLockDB file-pathsvE
DAV Àá±Ý µ¥ÀÌÅͺ£À̽º À§Ä¡
DavMinTimeout seconds 0 svdE
¼­¹ö°¡ DAV ÀÚ¿ø¿¡ ´ëÇØ À¯ÁöÇÒ Àá±ÝÀÇ Ãּҽð£
DBDExptime time-in-secondssvE
Keepalive time for idle connections
DBDKeep numbersvE
Maximum sustained number of connections
DBDMax numbersvE
Maximum number of connections
DBDMin numbersvE
Minimum number of connections
DBDParams +param1=value1[,param2=value2]svE
Parameters for database connection
DBDPersist 0|1svE
Whether to use persistent connections
DBDPrepareSQL "SQL statement" labelsvE
Define an SQL prepared statement
DBDriver namesvE
Specify an SQL driver
DefaultIcon url-pathsvdhB
ƯÁ¤ ¾ÆÀÌÄÜÀ» ¼³Á¤ÇÏÁö¾ÊÀº ÆÄÀÏ¿¡ »ç¿ëÇÒ ¾ÆÀÌÄÜ
DefaultLanguage MIME-langsvdhB
Sets all files in the given scope to the specified +language
DefaultType MIME-type text/plain svdhC
MIME content-type that will be sent if the +server cannot determine a type in any other way
DeflateBufferSize value 8096 svE
zlibÀÌ Çѹø¿¡ ¾ÐÃàÇÒ Å©±â
DeflateCompressionLevel valuesvE
Ãâ·ÂÀ» ¾î´ÀÁ¤µµ ¾ÐÃàÇϴ°¡
DeflateFilterNote [type] notenamesvE
¾ÐÃà·üÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù
DeflateMemLevel value 9 svE
zlibÀÌ ¾ÐÃàÇÒ¶§ »ç¿ëÇÏ´Â ¸Þ¸ð¸®·®
DeflateWindowSize value 15 svE
Zlib ¾ÐÃà window size
Deny from all|host|env=env-variable +[host|env=env-variable] ...dhB
¼­¹ö Á¢±ÙÀ» °ÅºÎÇÒ È£½ºÆ®¸¦ ÁöÁ¤ÇÑ´Ù
<Directory directory-path> +... </Directory>svC
Enclose a group of directives that apply only to the +named file-system directory and sub-directories
DirectoryIndex + local-url [local-url] ... index.html svdhB
Ŭ¶óÀ̾ðÆ®°¡ µð·ºÅ丮¸¦ ¿äûÇÒ¶§ ã¾Æº¼ ÀÚ¿ø ¸ñ·Ï
<DirectoryMatch regex> +... </DirectoryMatch>svC
Enclose directives that apply to +file-system directories matching a regular expression and their +subdirectories
DirectorySlash On|Off On svdhB
¸¶Áö¸· ½½·¡½¬ ¸®´ÙÀÌ·º¼ÇÀ» Å°°í ²ö´Ù
DocumentRoot directory-path /usr/local/apache/h +svC
Directory that forms the main document tree visible +from the web
DumpIOInput On|Off Off sE
Dump all input data to the error log
DumpIOOutput On|Off Off sE
Dump all output data to the error log
EnableExceptionHook On|Off Off sM
Enables a hook that runs exception handlers +after a crash
EnableMMAP On|Off On svdhC
Use memory-mapping to read files during delivery
EnableSendfile On|Off On svdhC
Use the kernel sendfile support to deliver files to the client
ErrorDocument error-code documentsvdhC
What the server will return to the client +in case of an error
ErrorLog file-path|syslog[:facility] logs/error_log (Uni +svC
Location where the server will log errors
ExamplesvdhX
¾ÆÆÄÄ¡ ¸ðµâ API¸¦ ¼³¸íÇϱâÀ§ÇÑ ¿¹Á¦ Áö½Ã¾î
ExpiresActive On|OffsvdhE
Expires Çì´õ¸¦ »ý¼ºÇÑ´Ù
ExpiresByType MIME-type +<code>secondssvdhE
MIME typeÀ¸·Î Expires Çì´õ°ªÀ» ¼³Á¤ÇÑ´Ù
ExpiresDefault <code>secondssvdhE
¸¸±â½Ã°£À» °è»êÇÏ´Â ±âº» ¾Ë°í¸®Áò
ExtendedStatus On|Off Off sB
°¢ ¿äû¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ »óÅ Á¤º¸¸¦ ±â·ÏÇÑ´Ù
ExtFilterDefine filtername parameterssE
¿ÜºÎ ÇÊÅ͸¦ Á¤ÀÇÇÑ´Ù
ExtFilterOptions option [option] ... DebugLevel=0 NoLogS +dE
mod_ext_filter ¿É¼ÇÀ» ¼³Á¤ÇÑ´Ù
FileETag component ... INode MTime Size svdhC
File attributes used to create the ETag +HTTP response header
<Files filename> ... </Files>svdhC
Contains directives that apply to matched +filenames
<FilesMatch regex> ... </FilesMatch>svdhC
Contains directives that apply to regular-expression matched +filenames
FilterChain [+=-@!]filter-name ...svdhB
Configure the filter chain
FilterDeclare filter-name [type]svdhB
Declare a smart filter
FilterProtocol filter-name [provider-name] + proto-flagssvdhB
Deal with correct HTTP protocol handling
FilterProvider filter-name provider-name + [req|resp|env]=dispatch matchsvdhB
Register a content filter
FilterTrace filter-name levelsvdB
Get debug/diagnostic information from + mod_filter
ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback] Prefer svdhB
Action to take if a single acceptable document is not +found
ForceType MIME-type|NonedhC
Forces all matching files to be served with the specified +MIME content-type
ForensicLog filename|pipesvE
Sets filename of the forensic log
GracefulShutDownTimeout secondssM
Specify a timeout after which a gracefully shutdown server +will exit.
Group unix-group #-1 sM
Group under which the server will answer +requests
Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]svdhE
HTTP ÀÀ´ä Çì´õ¸¦ ±¸¼ºÇÑ´Ù
HeaderName filenamesvdhB
ÆÄÀϸñ·Ï À§¿¡ »ðÀÔÇÒ ÆÄÀÏÀÇ À̸§
HostnameLookups On|Off|Double Off svdC
Enables DNS lookups on client IP addresses
IdentityCheck On|Off Off svdE
¿ø°Ý »ç¿ëÀÚÀÇ RFC 1413 ½Å¿øÀ» ·Î±×¿¡ ±â·ÏÇÑ´Ù
IdentityCheckTimeout seconds 30 svdE
ident ¿äûÀÇ ½Ã°£Á¦ÇÑÀ» ÁöÁ¤ÇÑ´Ù
<IfDefine [!]parameter-name> ... + </IfDefine>svdhC
Encloses directives that will be processed only +if a test is true at startup
<IfModule [!]module-file|module-identifier> ... + </IfModule>svdhC
Encloses directives that are processed conditional on the +presence or absence of a specific module
<IfVersion [[!]operator] version> ... +</IfVersion>svdhE
¹öÀüº° ¼³Á¤À» ¹­´Â´Ù
ImapBase map|referer|URL http://servername/ svdhB
À̹ÌÁö¸Ê ÆÄÀÏ¿¡¼­ base ±âº»°ª
ImapDefault error|nocontent|map|referer|URL nocontent svdhB
À̹ÌÁö¸Ê¿¡ ¾î´À ¿µ¿ª¿¡µµ ÇØ´çÇÏÁö ¾Ê´Â ÁÂÇ¥¸¦ ÁØ +°æ¿ì ±âº» Çൿ
ImapMenu none|formatted|semiformatted|unformattedsvdhB
ÁÂÇ¥¾øÀÌ À̹ÌÁö¸Ê ¿äû½Ã ÃëÇÒ Çൿ
Include file-path|directory-pathsvdC
Includes other configuration files from within +the server configuration files
IndexIgnore file [file] ...svdhB
µð·ºÅ丮 ¸ñ·Ï¿¡¼­ ¼û±æ ÆÄÀϸñ·ÏÀ» Ãß°¡ÇÑ´Ù
IndexOptions [+|-]option [[+|-]option] +...svdhB
µð·ºÅ丮 ¸ñ·ÏÀÇ ¿©·¯ ¼³Á¤µé
IndexOrderDefault Ascending|Descending +Name|Date|Size|Description Ascending Name svdhB
µð·ºÅ丮 ¸ñ·ÏÀÇ ±âº» ¼ø¼­¸¦ ¼³Á¤ÇÑ´Ù
IndexStyleSheet url-pathsvdhB
µð·ºÅ丮 ¸ñ·Ï¿¡ CSS ½ºÅ¸ÀϽ¬Æ®¸¦ Ãß°¡ÇÑ´Ù
ISAPIAppendLogToErrors on|off off svdhB
ISAPI exntensionÀÇ HSE_APPEND_LOG_PARAMETER +¿äûÀ» ¿À·ù ·Î±×¿¡ ±â·ÏÇÑ´Ù
ISAPIAppendLogToQuery on|off on svdhB
ISAPI exntensionÀÇ HSE_APPEND_LOG_PARAMETER +¿äûÀ» ÁúÀǹ®ÀÚ¿­¿¡ ±â·ÏÇÑ´Ù
ISAPICacheFile file-path [file-path] +...svB
¼­¹ö°¡ ½ÃÀÛÇÒ¶§ ¸Þ¸ð¸®·Î ÀоîµéÀÏ ISAPI .dll ÆÄÀϵé
ISAPIFakeAsync on|off off svdhB
ºñµ¿±â ISAPI ÄݹéÀ» Áö¿øÇϴ ôÇÑ´Ù
ISAPILogNotSupported on|off off svdhB
ISAPI extensionÀÌ Áö¿øÇÏÁö ¾Ê´Â ±â´ÉÀ» ¿äûÇϸé +·Î±×¿¡ ±â·ÏÇÑ´Ù
ISAPIReadAheadBuffer size 49152 svdhB
ISAPI extensionÀÇ ¹Ì¸®Àбâ¹öÆÛ(read ahead buffer) +Å©±â
KeepAlive On|Off On svC
Enables HTTP persistent connections
KeepAliveTimeout seconds 5 svC
Amount of time the server will wait for subsequent +requests on a persistent connection
LanguagePriority MIME-lang [MIME-lang] +...svdhB
The precendence of language variants for cases where +the client does not express a preference
LDAPCacheEntries number 1024 sE
Maximum number of entries in the primary LDAP cache
LDAPCacheTTL seconds 600 sE
Time that cached items remain valid
LDAPConnectionTimeout secondssE
Specifies the socket connection timeout in seconds
LDAPOpCacheEntries number 1024 sE
Number of entries used to cache LDAP compare +operations
LDAPOpCacheTTL seconds 600 sE
Time that entries in the operation cache remain +valid
LDAPSharedCacheFile directory-path/filenamesE
Sets the shared memory cache file
LDAPSharedCacheSize bytes 102400 sE
Size in bytes of the shared-memory cache
LDAPTrustedClientCert type directory-path/filename/nickname [password]svdhE
Sets the file containing or nickname referring to a per +connection client certificate. Not all LDAP toolkits support per +connection client certificates.
LDAPTrustedGlobalCert type directory-path/filename [password]sE
Sets the file or database containing global trusted +Certificate Authority or global client certificates
LDAPTrustedMode typesvE
Specifies the SSL/TLS mode to be used when connecting to an LDAP server.
LDAPVerifyServerCert On|Off On sE
Force server certificate verification
<Limit method [method] ... > ... + </Limit>svdhC
Restrict enclosed access controls to only certain HTTP +methods
<LimitExcept method [method] ... > ... + </LimitExcept>svdhC
Restrict access controls to all HTTP methods +except the named ones
LimitInternalRecursion number [number] 10 svC
Determine maximum number of internal redirects and nested +subrequests
LimitRequestBody bytes 0 svdhC
Restricts the total size of the HTTP request body sent +from the client
LimitRequestFields number 100 sC
Limits the number of HTTP request header fields that +will be accepted from the client
LimitRequestFieldsize bytessC
Limits the size of the HTTP request header allowed from the +client
LimitRequestLine bytes 8190 sC
Limit the size of the HTTP request line that will be accepted +from the client
LimitXMLRequestBody bytes 1000000 svdhC
Limits the size of an XML-based request body
Listen [IP-address:]portnumber [protocol]sM
IP addresses and ports that the server +listens to
ListenBacklog backlogsM
Maximum length of the queue of pending connections
LoadFile filename [filename] ...sE
ÁöÁ¤ÇÑ ¸ñÀûÆÄÀÏÀ̳ª ¶óÀ̺귯¸®¸¦ ÀоîµéÀδÙ
LoadModule module filenamesE
¸ñÀûÆÄÀÏÀ̳ª ¶óÀ̺귯¸®¸¦ ÀоîµéÀÌ°í, »ç¿ë°¡´ÉÇÑ +¸ðµâ ¸ñ·Ï¿¡ Ãß°¡ÇÑ´Ù
<Location + URL-path|URL> ... </Location>svC
Applies the enclosed directives only to matching +URLs
<LocationMatch + regex> ... </LocationMatch>svC
Applies the enclosed directives only to regular-expression +matching URLs
LockFile filename logs/accept.lock sM
Location of the accept serialization lock file
LogFormat format|nickname +[nickname] "%h %l %u %t \"%r\" +svB
·Î±×ÆÄÀÏ¿¡ »ç¿ëÇÒ Çü½ÄÀ» ±â¼úÇÑ´Ù
LogLevel level warn svC
Controls the verbosity of the ErrorLog
MaxClients numbersM
Maximum number of child processes that will be created +to serve requests
MaxKeepAliveRequests number 100 svC
Number of requests allowed on a persistent +connection
MaxMemFree KBytes 0 sM
Maximum amount of memory that the main allocator is allowed +to hold without calling free()
MaxRequestsPerChild number 10000 sM
Limit on the number of requests that an individual child server +will handle during its life
MaxRequestsPerThread number 0 sM
ÇÑ ¾²·¹µå°¡ ½ÇÇàÇÏ´Â µ¿¾È ó¸®ÇÒ ¿äû°³¼ö ÇÑ°è
MaxSpareServers number 10 sM
Maximum number of idle child server processes
MaxSpareThreads numbersM
Maximum number of idle threads
MaxThreads number 2048 sM
Set the maximum number of worker threads
MCacheMaxObjectCount value 1009 sX
ij½¬¿¡ ÀúÀåÇÒ ¼ö ÀÖ´Â ÃÖ´ë °´Ã¼°³¼ö
MCacheMaxObjectSize bytes 10000 sX
ij½¬¿¡ ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ´ë Å©±â (¹ÙÀÌÆ® ´ÜÀ§)
MCacheMaxStreamingBuffer size_in_bytes 100000°ú MCacheMaxOb +sX
ÀÀ´äÀ» ij½¬¾ÈÇÑ´Ù°í °áÁ¤Çϱâ Àü±îÁö ¸Þ¸ð¸® ¹öÆÛ¿¡ +ÀúÀåÇÒ ½ºÆ®¸² ÀÀ´äÀÇ ÃÖ´ë Å©±â
MCacheMinObjectSize bytes 0 sX
ij½¬¿¡ ÀúÀåÇÒ ¹®¼­ÀÇ ÃÖ¼Ò Å©±â (¹ÙÀÌÆ® ´ÜÀ§)
MCacheRemovalAlgorithm LRU|GDSF GDSF sX
ij½¬¿¡¼­ Á¦°ÅÇÒ ¹®¼­¸¦ ã´Â ¾Ë°í¸®Áò
MCacheSize KBytes 100 sX
ij½¬¿¡ »ç¿ëÇÒ ÃÖ´ë ¸Þ¸ð¸®·® (KByte ´ÜÀ§)
MetaDir directory .web svdhE
CERN ¸ÞŸÁ¤º¸¸¦ ãÀ» µð·ºÅ丮 À̸§
MetaFiles on|off off svdhE
CERN ¸ÞŸÆÄÀÏÀ» ó¸®ÇÑ´Ù
MetaSuffix suffix .meta svdhE
CERN ¸ÞŸÁ¤º¸¸¦ ÀúÀåÇÏ´Â ÆÄÀÏÀÇ Á¢¹Ì»ç
MimeMagicFile file-pathsvE
Enable MIME-type determination based on file contents +using the specified magic file
MinSpareServers number 5 sM
Minimum number of idle child server processes
MinSpareThreads numbersM
Minimum number of idle threads available to handle request +spikes
MMapFile file-path [file-path] ...sX
½ÃÀ۽à ¿©·¯ ÆÄÀÏÀ» ¸Þ¸ð¸®¿¡ ´ëÀÀÇÑ´Ù
ModMimeUsePathInfo On|Off Off dB
Tells mod_mime to treat path_info +components as part of the filename
MultiviewsMatch Any|NegotiatedOnly|Filters|Handlers +[Handlers|Filters] NegotiatedOnly svdhB
The types of files that will be included when searching for +a matching file with MultiViews
NameVirtualHost addr[:port]sC
Designates an IP address for name-virtual +hosting
NoProxy host [host] ...svE
Hosts, domains, or networks that will be connected to +directly
NWSSLTrustedCerts filename [filename] ...sB
List of additional client certificates
NWSSLUpgradeable [IP-address:]portnumbersB
Allows a connection to be upgraded to an SSL connection upon request
Options + [+|-]option [[+|-]option] ... All svdhC
Configures what features are available in a particular +directory
Order ordering Deny,Allow dhB
±âº»ÀûÀ¸·Î Á¢±ÙÀ» Çã¿ëÇÒÁö °ÅºÎÇÒÁö ¿©ºÎ¿Í +Allow¿Í Deny +󸮼ø¼­¸¦ Á¤ÇÑ´Ù.
PassEnv env-variable [env-variable] +...svdhB
½©¿¡¼­ ȯ°æº¯¼ö¸¦ °¡Á®¿Â´Ù
PidFile filename logs/httpd.pid sM
File where the server records the process ID +of the daemon
ProtocolEcho On|OffsvX
echo ¼­¹ö¸¦ Å°°í ²ö´Ù
<Proxy wildcard-url> ...</Proxy>svE
Container for directives applied to proxied resources
ProxyBadHeader IsError|Ignore|StartBody IsError svE
Determines how to handle bad header lines in a +response
ProxyBlock *|word|host|domain +[word|host|domain] ...svE
Words, hosts, or domains that are banned from being +proxied
ProxyDomain DomainsvE
Default domain name for proxied requests
ProxyErrorOverride On|Off Off svE
Override error pages for proxied content
ProxyIOBufferSize bytes 8192 svE
Determine size of internal data throughput buffer
<ProxyMatch regex> ...</ProxyMatch>svE
Container for directives applied to regular-expression-matched +proxied resources
ProxyMaxForwards number 10 svE
Maximium number of proxies that a request can be forwarded +through
ProxyPass [path] !|url [key=value key=value ...]]svdE
Maps remote servers into the local server URL-space
ProxyPassReverse [path] urlsvdE
Adjusts the URL in HTTP response headers sent from a reverse +proxied server
ProxyPassReverseCookieDomain internal-domain public-domainsvdE
Adjusts the Domain string in Set-Cookie headers from a reverse- +proxied server
ProxyPassReverseCookiePath internal-path public-pathsvdE
Adjusts the Path string in Set-Cookie headers from a reverse- +proxied server
ProxyPreserveHost On|Off Off svE
Use incoming Host HTTP request header for proxy +request
ProxyReceiveBufferSize bytes 0 svE
Network buffer size for proxied HTTP and FTP +connections
ProxyRemote match remote-serversvE
Remote proxy used to handle certain requests
ProxyRemoteMatch regex remote-serversvE
Remote proxy used to handle requests matched by regular +expressions
ProxyRequests On|Off Off svE
Enables forward (standard) proxy requests
ProxyTimeout seconds 300 svE
Network timeout for proxied requests
ProxyVia On|Off|Full|Block Off svE
Information provided in the Via HTTP response +header for proxied requests
ReadmeName filenamesvdhB
ÆÄÀϸñ·Ï ¸¶Áö¸·¿¡ »ðÀÔÇÒ ÆÄÀÏÀÇ À̸§
ReceiveBufferSize bytes 0 sM
TCP receive buffer size
Redirect [status] URL-path +URLsvdhB
Ŭ¶óÀ̾ðÆ®°¡ ´Ù¸¥ URL¿¡ Á¢¼ÓÇϵµ·Ï ¿äûÇÏ´Â ¿ÜºÎ +¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù
RedirectMatch [status] regex +URLsvdhB
ÇöÀç URLÀÌ Á¤±ÔÇ¥Çö½Ä¿¡ ÇØ´çÇÏ¸é ¿ÜºÎ ¸®´ÙÀÌ·º¼ÇÀ» +º¸³½´Ù
RedirectPermanent URL-path URLsvdhB
Ŭ¶óÀ̾ðÆ®°¡ ´Ù¸¥ URL¿¡ Á¢¼ÓÇϵµ·Ï ¿äûÇÏ´Â ¿ÜºÎ +¿µ±¸ ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù
RedirectTemp URL-path URLsvdhB
Ŭ¶óÀ̾ðÆ®°¡ ´Ù¸¥ URL¿¡ Á¢¼ÓÇϵµ·Ï ¿äûÇÏ´Â ¿ÜºÎ +Àӽà ¸®´ÙÀÌ·º¼ÇÀ» º¸³½´Ù
RemoveCharset extension [extension] +...vdhB
Removes any character set associations for a set of file +extensions
RemoveEncoding extension [extension] +...vdhB
Removes any content encoding associations for a set of file +extensions
RemoveHandler extension [extension] +...vdhB
Removes any handler associations for a set of file +extensions
RemoveInputFilter extension [extension] +...vdhB
Removes any input filter associations for a set of file +extensions
RemoveLanguage extension [extension] +...vdhB
Removes any language associations for a set of file +extensions
RemoveOutputFilter extension [extension] +...vdhB
Removes any output filter associations for a set of file +extensions
RemoveType extension [extension] +...vdhB
Removes any content type associations for a set of file +extensions
RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]svdhE
HTTP ¿äû Çì´õ¸¦ ±¸¼ºÇÑ´Ù
Require entity-name [entity-name] ...dhC
Selects which authenticated users can access +a resource
RewriteBase URL-pathdhE
Sets the base URL for per-directory rewrites
RewriteCond + TestString CondPatternsvdhE
Defines a condition under which rewriting will take place +
RewriteEngine on|off off svdhE
Enables or disables runtime rewriting engine
RewriteLock file-pathsE
Sets the name of the lock file used for RewriteMap +synchronization
RewriteLog file-pathsvE
Sets the name of the file used for logging rewrite engine +processing
RewriteLogLevel Level 0 svE
Sets the verbosity of the log file used by the rewrite +engine
RewriteMap MapName MapType:MapSource +svE
Defines a mapping function for key-lookup
RewriteOptions OptionssvdhE
Sets some special options for the rewrite engine
RewriteRule + Pattern SubstitutionsvdhE
Defines rules for the rewriting engine
RLimitCPU seconds|max [seconds|max]svdhC
Limits the CPU consumption of processes launched +by Apache children
RLimitMEM bytes|max [bytes|max]svdhC
Limits the memory consumption of processes launched +by Apache children
RLimitNPROC number|max [number|max]svdhC
Limits the number of processes that can be launched by +processes launched by Apache children
Satisfy Any|All All dhC
Interaction between host-level access control and +user authentication
ScoreBoardFile file-path logs/apache_status sM
Location of the file used to store coordination data for +the child processes
Script method cgi-scriptsvdB
ƯÁ¤ ¿äû¸Þ¼­µå¿¡ ´ëÇØ CGI ½ºÅ©¸³Æ®¸¦ +»ç¿ëÇÑ´Ù.
ScriptAlias URL-path +file-path|directory-pathsvB
URLÀ» ƯÁ¤ ÆÄÀϽýºÅÛ Àå¼Ò·Î ´ëÀÀÇÏ°í ´ë»óÀÌ CGI +½ºÅ©¸³Æ®¶ó°í ¾Ë¸°´Ù
ScriptAliasMatch regex +file-path|directory-pathsvB
Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ¿© URLÀ» ƯÁ¤ ÆÄÀϽýºÅÛ Àå¼Ò·Î +´ëÀÀÇÏ°í ´ë»óÀÌ CGI ½ºÅ©¸³Æ®¶ó°í ¾Ë¸°´Ù
ScriptInterpreterSource Registry|Registry-Strict|Script Script svdhC
Technique for locating the interpreter for CGI +scripts
ScriptLog file-pathsvB
CGI ½ºÅ©¸³Æ® ¿À·ù·Î±×ÆÄÀÏÀÇ À§Ä¡
ScriptLogBuffer bytes 1024 svB
½ºÅ©¸³Æ® ·Î±×¿¡ ±â·ÏÇÒ PUT ȤÀº POST ¿äûÀÇ ÃÖ´ë·®
ScriptLogLength bytes 10385760 svB
CGI ½ºÅ©¸³Æ® ·Î±×ÆÄÀÏÀÇ Å©±â Á¦ÇÑ
ScriptSock file-path logs/cgisock svB
cgi µ¥¸ó°ú Åë½ÅÀ» À§ÇØ »ç¿ëÇÒ ¼ÒÄÏÀÇ À̸§
SecureListen [IP-address:]portnumber +Certificate-Name [MUTUAL]sB
Enables SSL encryption for the specified port
SendBufferSize bytes 0 sM
TCP buffer size
ServerAdmin email-address|URLsvC
Email address that the server includes in error +messages sent to the client
ServerAlias hostname [hostname] ...vC
Alternate names for a host used when matching requests +to name-virtual hosts
ServerLimit numbersM
Upper limit on configurable number of processes
ServerName fully-qualified-domain-name[:port]svC
Hostname and port that the server uses to identify +itself
ServerPath URL-pathvC
Legacy URL pathname for a name-based virtual host that +is accessed by an incompatible browser
ServerRoot directory-path /usr/local/apache sC
Base directory for the server installation
ServerSignature On|Off|EMail Off svdhC
Configures the footer on server-generated documents
ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full Full sC
Configures the Server HTTP response +header
SetEnv env-variable valuesvdhB
ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù
SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
¿äûÀÇ ¼ºÁú¿¡ µû¶ó ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÑ´Ù
SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾Ê°í ¿äûÀÇ ¼ºÁú¿¡ µû¶ó ȯ°æº¯¼ö¸¦ +¼³Á¤ÇÑ´Ù
SetHandler handler-name|NonesvdhC
Forces all matching files to be processed by a +handler
SetInputFilter filter[;filter...]svdhC
Sets the filters that will process client requests and POST +input
SetOutputFilter filter[;filter...]svdhC
Sets the filters that will process responses from the +server
SSIEndTag tag "-->" svB
String that ends an include element
SSIErrorMsg message "[an error occurred +svdhB
Error message displayed when there is an SSI +error
SSIStartTag tag "<!--#" svB
String that starts an include element
SSITimeFormat formatstring "%A, %d-%b-%Y %H:%M +svdhB
Configures the format in which date strings are +displayed
SSIUndefinedEcho string "(none)" svdhB
String displayed when an unset variable is echoed
SSLCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Client Auth
SSLCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Client Auth
SSLCADNRequestFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for defining acceptable CA names
SSLCADNRequestPath directory-pathsvE
Directory of PEM-encoded CA Certificates for +defining acceptable CA names
SSLCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Client Auth
SSLCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Client Auth
SSLCertificateChainFile file-pathsvE
File of PEM-encoded Server CA Certificates
SSLCertificateFile file-pathsvE
Server PEM-encoded X.509 Certificate file
SSLCertificateKeyFile file-pathsvE
Server PEM-encoded Private Key file
SSLCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +handshake
SSLCryptoDevice engine builtin sE
Enable use of a cryptographic hardware accelerator
SSLEngine on|off|optional off svE
SSL Engine Operation Switch
SSLHonorCiperOrder flagsvE
Option to prefer the server's cipher preference order
SSLMutex type none sE
Semaphore for internal mutual exclusion of +operations
SSLOptions [+|-]option ...svdhE
Configure various SSL engine run-time options
SSLPassPhraseDialog type builtin sE
Type of pass phrase dialog for encrypted private +keys
SSLProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors
SSLProxyCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Remote Server Auth
SSLProxyCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Remote Server Auth
SSLProxyCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +proxy handshake
SSLProxyEngine on|off off svE
SSL Proxy Engine Operation Switch
SSLProxyMachineCertificateFile filenamesE
File of concatenated PEM-encoded client certificates and keys to be used by the proxy
SSLProxyMachineCertificatePath directorysE
Directory of PEM-encoded client certificates and keys to be used by the proxy
SSLProxyProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors for proxy usage
SSLProxyVerify level none svdhE
Type of remote server Certificate verification
SSLProxyVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Remote Server +Certificate verification
SSLRandomSeed context source +[bytes]sE
Pseudo Random Number Generator (PRNG) seeding +source
SSLRequire expressiondhE
Allow access only when an arbitrarily complex +boolean expression is true
SSLRequireSSLdhE
Deny access when SSL is not used for the +HTTP request
SSLSessionCache type none sE
Type of the global/inter-process SSL Session +Cache
SSLSessionCacheTimeout seconds 300 svE
Number of seconds before an SSL session expires +in the Session Cache
SSLUserName varnamesdhE
Variable name to determine user name
SSLVerifyClient level none svdhE
Type of Client Certificate verification
SSLVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Client +Certificate verification
StartServers numbersM
Number of child server processes created at startup
StartThreads numbersM
Number of threads created on startup
SuexecUserGroup User GroupsvE
CGI ÇÁ·Î±×·¥ÀÌ »ç¿ëÇÒ »ç¿ëÀÚ¿Í ±×·ì ±ÇÇÑ
ThreadLimit numbersM
Sets the upper limit on the configurable number of threads +per child process
ThreadsPerChild numbersM
Number of threads created by each child process
ThreadStackSize sizesM
The size in bytes of the stack used by threads handling +client connections
TimeOut seconds 300 sC
Amount of time the server will wait for +certain events before failing a request
TraceEnable [on|off|extended] on sC
Determines the behaviour on TRACE +requests
TransferLog file|pipesvB
·Î±×ÆÄÀÏ À§Ä¡¸¦ ¼³Á¤ÇÑ´Ù
TypesConfig file-path conf/mime.types sB
The location of the mime.types file
UnsetEnv env-variable [env-variable] +...svdhB
ȯ°æº¯¼ö¸¦ Á¦°ÅÇÑ´Ù
UseCanonicalName On|Off|DNS Off svdC
Configures how the server determines its own name and +port
UseCanonicalPhysicalPort On|Off Off svdC
Configures how the server determines its own name and +port
User unix-userid #-1 sM
The userid under which the server will answer +requests
UserDir directory-filename public_html svB
»ç¿ëÀÚº° µð·ºÅ丮 À§Ä¡
VirtualDocumentRoot interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
VirtualDocumentRootIP interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
<VirtualHost + addr[:port] [addr[:port]] + ...> ... </VirtualHost>sC
Contains directives that apply only to a specific +hostname or IP address
VirtualScriptAlias interpolated-directory|none none svE
Dynamically configure the location of the CGI directory for +a given virtual host
VirtualScriptAliasIP interpolated-directory|none none svE
Dynamically configure the location of the cgi directory for +a given virtual host
Win32DisableAcceptExsM
Use accept() rather than AcceptEx() to accept network connections
XBitHack on|off|full off svdhB
Parse SSI directives in files with the execute bit +set
+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/quickreference.html.ru.koi8-r b/docs/manual/mod/quickreference.html.ru.koi8-r new file mode 100644 index 00000000..5b2830cc --- /dev/null +++ b/docs/manual/mod/quickreference.html.ru.koi8-r @@ -0,0 +1,755 @@ + + + +ëÒÁÔËÉÊ ÓÐÒÁ×ÏÞÎÉË ÐÏ ÄÉÒÅËÔÉ×ÁÍ - HTTP ÓÅÒ×ÅÒ Apache + + + + + +
+

íÏÄÕÌÉ | äÉÒÅËÔÉ×Ù | FAQ | çÌÏÓÓÁÒÉÊ | ëÁÒÔÁ ÓÁÊÔÁ

+

HTTP ÓÅÒ×ÅÒ Apache ×ÅÒÓÉÉ 2.2

+
+
<-
+
+Apache > HTTP ÓÅÒ×ÅÒ > äÏËÕÍÅÎÔÁÃÉÑ > ÷ÅÒÓÉÑ 2.2 > íÏÄÕÌÉ
+

ëÒÁÔËÉÊ ÓÐÒÁ×ÏÞÎÉË ÐÏ ÄÉÒÅËÔÉ×ÁÍ

+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ +

÷ ËÒÁÔËÏÍ ÓÐÒÁ×ÏÞÎÉËÅ ÐÏ ÄÉÒÅËÔÉ×ÁÍ ×Ù ÎÁÊÄ£ÔÅ ÉÎÆÏÒÍÁÃÉÀ + Ï ÔÏÍ, ËÁË ÉÓÐÏÌØÚÏ×ÁÔØ ÔÕ ÉÌÉ ÉÎÕÀ ÄÉÒÅËÔÉ×Õ, Å£ ÚÎÁÞÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ, ÓÔÁÔÕÓ + É ËÏÎÔÅËÓÔ. äÌÑ ÒÁÓÛÉÆÒÏ×ËÉ ÐÏÎÑÔÉÊ «ÓÔÁÔÕÓ» É «ËÏÎÔÅËÓÔ», ÏÂÒÁÔÉÔÅÓØ + Ë óÌÏ×ÁÒÀ.

+ +

÷ ÐÅÒ×ÏÊ ËÏÌÏÎËÅ ÐÒÉ×ÏÄÉÔÓÑ ÎÁÚ×ÁÎÉÅ ÄÉÒÅËÔÉ×Ù É ÏÐÉÓÁÎÉŠţ + ÉÓÐÏÌØÚÏ×ÁÎÉÑ. ÷Ï ×ÔÏÒÏÊ - ÚÎÁÞÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ, ÅÓÌÉ ÔÁËÏ×ÏÅ + ÅÓÔØ Õ ÄÉÒÅËÔÉ×Ù. åÓÌÉ ÜÔÏ ÚÎÁÞÅÎÉÅ ÓÌÉÛËÏÍ ×ÅÌÉËÏ, ÔÏ ÐÏÓÌÅ + ÐÅÒ×ÙÈ ÂÕË× ÉÄÅÔ ÚÎÁÞ£Ë «+».

+ +

÷ ÔÒÅÔØÅÊ É ÞÅÔ×£ÒÔÏÊ ËÏÌÏÎËÁÈ ÄÁÀÔÓÑ ÚÎÁÞÅÎÉÑ ËÏÎÔÅËÓÔÁ, × + ËÏÔÏÒÏÍ ÄÁÎÎÁÑ ÄÉÒÅËÔÉ×Á ÉÍÅÅÔ ÓÍÙÓÌ (ÍÏÖÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ), É + Å£ ÓÔÁÔÕÓ. ÷ÓÅ ÓÏËÒÁÝÅÎÉÑ, ÉÓÐÏÌØÚÕÅÍÙÅ ÐÒÉ ÜÔÏÍ, ÒÁÓÛÉÆÒÏ×Ù×ÁÀÔÓÑ + × ÓÌÅÄÕÀÝÅÊ ÔÁÂÌÉÃÅ.

+
+
+ + + +
 A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  K  |  L  |  M  |  N  |  O  |  P  |  R  |  S  |  T  |  U  |  V  |  W  |  X  + + + + + +
sserver config
vvirtual host
ddirectory
h.htaccess
 + + + + + + +
CCore
MMPM
BBase
EExtension
XExperimental
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
AcceptFilter protocol accept_filtersC
Configures optimizations for a Protocol's Listener Sockets
AcceptMutex Default|method Default sM
Method that Apache uses to serialize multiple children +accepting requests on network sockets
AcceptPathInfo On|Off|Default Default svdhC
Resources accept trailing pathname information
AccessFileName filename [filename] ... .htaccess svC
Name of the distributed configuration file
Action action-type cgi-script [virtual]svdhB
Activates a CGI script for a particular handler or +content-type
AddAlt string file [file] ...svdhB
Alternate text to display for a file, instead of an +icon selected by filename
AddAltByEncoding string MIME-encoding +[MIME-encoding] ...svdhB
Alternate text to display for a file instead of an icon +selected by MIME-encoding
AddAltByType string MIME-type +[MIME-type] ...svdhB
Alternate text to display for a file, instead of an +icon selected by MIME content-type
AddCharset charset extension +[extension] ...svdhB
Maps the given filename extensions to the specified content +charset
AddDefaultCharset On|Off|charset Off svdhC
Default charset parameter to be added when a response +content-type is text/plain or text/html
AddDescription string file [file] ...svdhB
Description to display for a file
AddEncoding MIME-enc extension +[extension] ...svdhB
Maps the given filename extensions to the specified encoding +type
AddHandler handler-name extension +[extension] ...svdhB
Maps the filename extensions to the specified +handler
AddIcon icon name [name] +...svdhB
Icon to display for a file selected by name
AddIconByEncoding icon MIME-encoding +[MIME-encoding] ...svdhB
Icon to display next to files selected by MIME +content-encoding
AddIconByType icon MIME-type +[MIME-type] ...svdhB
Icon to display next to files selected by MIME +content-type
AddInputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +client requests
AddLanguage MIME-lang extension +[extension] ...svdhB
Maps the given filename extension to the specified content +language
AddModuleInfo module-name stringsvE
Adds additional information to the module +information displayed by the server-info handler
AddOutputFilter filter[;filter...] +extension [extension] ...svdhB
Maps filename extensions to the filters that will process +responses from the server
AddOutputFilterByType filter[;filter...] +MIME-type [MIME-type] ...svdhC
assigns an output filter to a particular MIME-type
AddType MIME-type extension +[extension] ...svdhB
Maps the given filename extensions onto the specified content +type
Alias URL-path +file-path|directory-pathsvB
Maps URLs to filesystem locations
AliasMatch regex +file-path|directory-pathsvB
Maps URLs to filesystem locations using regular +expressions
Allow from all|host|env=env-variable +[host|env=env-variable] ...dhB
Controls which hosts can access an area of the +server
AllowCONNECT port [port] ... 443 563 svE
Ports that are allowed to CONNECT through the +proxy
AllowEncodedSlashes On|Off Off svC
Determines whether encoded path separators in URLs are allowed to +be passed through
AllowOverride All|None|directive-type +[directive-type] ... All dC
Types of directives that are allowed in +.htaccess files
Anonymous user [user] ...dhE
Specifies userIDs that are allowed access without +password verification
Anonymous_LogEmail On|Off On dhE
Sets whether the password entered will be logged in the +error log
Anonymous_MustGiveEmail On|Off On dhE
Specifies whether blank passwords are allowed
Anonymous_NoUserID On|Off Off dhE
Sets whether the userID field may be empty
Anonymous_VerifyEmail On|Off Off dhE
Sets whether to check the password field for a correctly +formatted email address
AuthBasicAuthoritative On|Off On dhB
Sets whether authorization and authentication are passed to +lower level modules
AuthBasicProvider provider-name +[provider-name] ... file dhB
Sets the authentication provider(s) for this location
AuthDBDUserPWQuery querydE
SQL query to look up a password for a user
AuthDBDUserRealmQuery querydE
SQL query to look up a password hash for a user and realm. +
AuthDBMGroupFile file-pathdhE
Sets the name of the database file containing the list +of user groups for authorization
AuthDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store passwords
AuthDBMUserFile file-pathdhE
Sets the name of a database file containing the list of users and +passwords for authentication
AuthDefaultAuthoritative On|Off On dhB
Sets whether authentication is passed to lower level +modules
AuthDigestAlgorithm MD5|MD5-sess MD5 dhX
Selects the algorithm used to calculate the challenge and +response hashes in digest authentication
AuthDigestDomain URI [URI] ...dhX
URIs that are in the same protection space for digest +authentication
AuthDigestNcCheck On|Off Off sX
Enables or disables checking of the nonce-count sent by the +server
AuthDigestNonceFormat formatdhX
Determines how the nonce is generated
AuthDigestNonceLifetime seconds 300 dhX
How long the server nonce is valid
AuthDigestProvider provider-name +[provider-name] ... file dhX
Sets the authentication provider(s) for this location
AuthDigestQop none|auth|auth-int [auth|auth-int] auth dhX
Determines the quality-of-protection to use in digest +authentication
AuthDigestShmemSize size 1000 sX
The amount of shared memory to allocate for keeping track +of clients
AuthGroupFile file-pathdhB
Sets the name of a text file containing the list +of user groups for authorization
AuthLDAPBindDN distinguished-namedhE
Optional DN to use in binding to the LDAP server
AuthLDAPBindPassword passworddhE
Password used in conjuction with the bind DN
AuthLDAPCharsetConfig file-pathsE
Language to charset conversion configuration file
AuthLDAPCompareDNOnServer on|off on dhE
Use the LDAP server to compare the DNs
AuthLDAPDereferenceAliases never|searching|finding|always Always dhE
When will the module de-reference aliases
AuthLDAPGroupAttribute attributedhE
LDAP attributes used to check for group membership
AuthLDAPGroupAttributeIsDN on|off on dhE
Use the DN of the client username when checking for +group membership
AuthLDAPRemoteUserIsDN on|off off dhE
Use the DN of the client username to set the REMOTE_USER +environment variable
AuthLDAPUrl url [NONE|SSL|TLS|STARTTLS]dhE
URL specifying the LDAP search parameters
AuthName auth-domaindhC
Authorization realm for use in HTTP +authentication
<AuthnProviderAlias baseProvider Alias> +... </AuthnProviderAlias>svE
Enclose a group of directives that represent an +extension of a base authentication provider and referenced by +the specified alias
AuthType Basic|DigestdhC
Type of user authentication
AuthUserFile file-pathdhB
Sets the name of a text file containing the list of users and +passwords for authentication
AuthzDBMAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzDBMType default|SDBM|GDBM|NDBM|DB default dhE
Sets the type of database file that is used to +store list of user groups
AuthzDefaultAuthoritative On|Off On dhB
Sets whether authorization is passed to lower level +modules
AuthzGroupFileAuthoritative On|Off On dhB
Sets whether authorization will be passed on to lower level +modules
AuthzLDAPAuthoritative on|off on dhE
Prevent other authentication modules from +authenticating the user if this one fails
AuthzOwnerAuthoritative On|Off On dhE
Sets whether authorization will be passed on to lower level +modules
AuthzUserAuthoritative On|Off On dhB
Sets whether authorization will be passed on to lower level +modules
BrowserMatch regex [!]env-variable[=value] +[[!]env-variable[=value]] ...svdhB
Sets environment variables conditional on HTTP User-Agent +
BrowserMatchNoCase regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables conditional on User-Agent without +respect to case
BufferedLogs On|Off Off sB
Buffer log entries in memory before writing to disk
CacheDefaultExpire seconds 3600 (one hour) svE
The default duration to cache a document when no expiry date is specified.
CacheDirLength length 2 svE
The number of characters in subdirectory names
CacheDirLevels levels 3 svE
The number of levels of subdirectories in the +cache.
CacheDisable url-stringsvE
Disable caching of specified URLs
CacheEnable cache_type url-stringsvE
Enable caching of specified URLs using a specified storage +manager
CacheFile file-path [file-path] ...sX
Cache a list of file handles at startup time
CacheIgnoreCacheControl On|Off Off svE
Ignore request to not serve cached content to client
CacheIgnoreHeaders header-string [header-string] ... None svE
Do not store the given HTTP header(s) in the cache. +
CacheIgnoreNoLastMod On|Off Off svE
Ignore the fact that a response has no Last Modified +header.
CacheLastModifiedFactor float 0.1 svE
The factor used to compute an expiry date based on the +LastModified date.
CacheMaxExpire seconds 86400 (one day) svE
The maximum time in seconds to cache a document
CacheMaxFileSize bytes 1000000 svE
The maximum size (in bytes) of a document to be placed in the +cache
CacheMinFileSize bytes 1 svE
The minimum size (in bytes) of a document to be placed in the +cache
CacheNegotiatedDocs On|Off Off svB
Allows content-negotiated documents to be +cached by proxy servers
CacheRoot directorysvE
The directory root under which cache files are +stored
CacheStoreNoStore On|Off Off svE
Attempt to cache requests or responses that have been marked as no-store.
CacheStorePrivate On|Off Off svE
Attempt to cache responses that the server has marked as private
CGIMapExtension cgi-path .extensiondhC
Technique for locating the interpreter for CGI +scripts
CharsetDefault charsetsvdhX
Charset to translate into
CharsetOptions option [option] ... DebugLevel=0 NoImpl +svdhX
Configures charset translation behavior
CharsetSourceEnc charsetsvdhX
Source charset of files
CheckSpelling on|off Off svdhE
Enables the spelling +module
ContentDigest On|Off Off svdhC
Enables the generation of Content-MD5 HTTP Response +headers
CookieDomain domainsvdhE
The domain to which the tracking cookie applies
CookieExpires expiry-periodsvdhE
Expiry time for the tracking cookie
CookieLog filenamesvB
Sets filename for the logging of cookies
CookieName token Apache svdhE
Name of the tracking cookie
CookieStyle + Netscape|Cookie|Cookie2|RFC2109|RFC2965 Netscape svdhE
Format of the cookie header field
CookieTracking on|off off svdhE
Enables tracking cookie
CoreDumpDirectory directorysM
Directory where Apache attempts to +switch before dumping core
CustomLog file|pipe +format|nickname +[env=[!]environment-variable]svB
Sets filename and format of log file
Dav On|Off|provider-name Off dE
Enable WebDAV HTTP methods
DavDepthInfinity on|off off svdE
Allow PROPFIND, Depth: Infinity requests
DavGenericLockDB file-pathsvdE
Location of the DAV lock database
DavLockDB file-pathsvE
Location of the DAV lock database
DavMinTimeout seconds 0 svdE
Minimum amount of time the server holds a lock on +a DAV resource
DBDExptime time-in-secondssvE
Keepalive time for idle connections
DBDKeep numbersvE
Maximum sustained number of connections
DBDMax numbersvE
Maximum number of connections
DBDMin numbersvE
Minimum number of connections
DBDParams +param1=value1[,param2=value2]svE
Parameters for database connection
DBDPersist 0|1svE
Whether to use persistent connections
DBDPrepareSQL "SQL statement" labelsvE
Define an SQL prepared statement
DBDriver namesvE
Specify an SQL driver
DefaultIcon url-pathsvdhB
Icon to display for files when no specific icon is +configured
DefaultLanguage MIME-langsvdhB
Sets all files in the given scope to the specified +language
DefaultType MIME-type text/plain svdhC
MIME content-type that will be sent if the +server cannot determine a type in any other way
DeflateBufferSize value 8096 svE
Fragment size to be compressed at one time by zlib
DeflateCompressionLevel valuesvE
How much compression do we apply to the output
DeflateFilterNote [type] notenamesvE
Places the compression ratio in a note for logging
DeflateMemLevel value 9 svE
How much memory should be used by zlib for compression
DeflateWindowSize value 15 svE
Zlib compression window size
Deny from all|host|env=env-variable +[host|env=env-variable] ...dhB
Controls which hosts are denied access to the +server
<Directory directory-path> +... </Directory>svC
Enclose a group of directives that apply only to the +named file-system directory and sub-directories
DirectoryIndex + local-url [local-url] ... index.html svdhB
List of resources to look for when the client requests +a directory
<DirectoryMatch regex> +... </DirectoryMatch>svC
Enclose directives that apply to +file-system directories matching a regular expression and their +subdirectories
DirectorySlash On|Off On svdhB
Toggle trailing slash redirects on or off
DocumentRoot directory-path /usr/local/apache/h +svC
Directory that forms the main document tree visible +from the web
DumpIOInput On|Off Off sE
Dump all input data to the error log
DumpIOOutput On|Off Off sE
Dump all output data to the error log
EnableExceptionHook On|Off Off sM
Enables a hook that runs exception handlers +after a crash
EnableMMAP On|Off On svdhC
Use memory-mapping to read files during delivery
EnableSendfile On|Off On svdhC
Use the kernel sendfile support to deliver files to the client
ErrorDocument error-code documentsvdhC
What the server will return to the client +in case of an error
ErrorLog file-path|syslog[:facility] logs/error_log (Uni +svC
Location where the server will log errors
ExamplesvdhX
Demonstration directive to illustrate the Apache module +API
ExpiresActive On|OffsvdhE
Enables generation of Expires +headers
ExpiresByType MIME-type +<code>secondssvdhE
Value of the Expires header configured +by MIME type
ExpiresDefault <code>secondssvdhE
Default algorithm for calculating expiration time
ExtendedStatus On|Off Off sB
Keep track of extended status information for each +request
ExtFilterDefine filtername parameterssE
Define an external filter
ExtFilterOptions option [option] ... DebugLevel=0 NoLogS +dE
Configure mod_ext_filter options
FileETag component ... INode MTime Size svdhC
File attributes used to create the ETag +HTTP response header
<Files filename> ... </Files>svdhC
Contains directives that apply to matched +filenames
<FilesMatch regex> ... </FilesMatch>svdhC
Contains directives that apply to regular-expression matched +filenames
FilterChain [+=-@!]filter-name ...svdhB
Configure the filter chain
FilterDeclare filter-name [type]svdhB
Declare a smart filter
FilterProtocol filter-name [provider-name] + proto-flagssvdhB
Deal with correct HTTP protocol handling
FilterProvider filter-name provider-name + [req|resp|env]=dispatch matchsvdhB
Register a content filter
FilterTrace filter-name levelsvdB
Get debug/diagnostic information from + mod_filter
ForceLanguagePriority None|Prefer|Fallback [Prefer|Fallback] Prefer svdhB
Action to take if a single acceptable document is not +found
ForceType MIME-type|NonedhC
Forces all matching files to be served with the specified +MIME content-type
ForensicLog filename|pipesvE
Sets filename of the forensic log
GracefulShutDownTimeout secondssM
Specify a timeout after which a gracefully shutdown server +will exit.
Group unix-group #-1 sM
Group under which the server will answer +requests
Header [condition] set|append|add|unset|echo +header [value] [early|env=[!]variable]svdhE
Configure HTTP response headers
HeaderName filenamesvdhB
Name of the file that will be inserted at the top +of the index listing
HostnameLookups On|Off|Double Off svdC
Enables DNS lookups on client IP addresses
IdentityCheck On|Off Off svdE
Enables logging of the RFC 1413 identity of the remote +user
IdentityCheckTimeout seconds 30 svdE
Determines the timeout duration for ident requests
<IfDefine [!]parameter-name> ... + </IfDefine>svdhC
Encloses directives that will be processed only +if a test is true at startup
<IfModule [!]module-file|module-identifier> ... + </IfModule>svdhC
Encloses directives that are processed conditional on the +presence or absence of a specific module
<IfVersion [[!]operator] version> ... +</IfVersion>svdhE
contains version dependent configuration
ImapBase map|referer|URL http://servername/ svdhB
Default base for imagemap files
ImapDefault error|nocontent|map|referer|URL nocontent svdhB
Default action when an imagemap is called with coordinates +that are not explicitly mapped
ImapMenu none|formatted|semiformatted|unformattedsvdhB
Action if no coordinates are given when calling +an imagemap
Include file-path|directory-pathsvdC
Includes other configuration files from within +the server configuration files
IndexIgnore file [file] ...svdhB
Adds to the list of files to hide when listing +a directory
IndexOptions [+|-]option [[+|-]option] +...svdhB
Various configuration settings for directory +indexing
IndexOrderDefault Ascending|Descending +Name|Date|Size|Description Ascending Name svdhB
Sets the default ordering of the directory index
IndexStyleSheet url-pathsvdhB
Adds a CSS stylesheet to the directory index
ISAPIAppendLogToErrors on|off off svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the error log
ISAPIAppendLogToQuery on|off on svdhB
Record HSE_APPEND_LOG_PARAMETER requests from +ISAPI extensions to the query field
ISAPICacheFile file-path [file-path] +...svB
ISAPI .dll files to be loaded at startup
ISAPIFakeAsync on|off off svdhB
Fake asynchronous support for ISAPI callbacks
ISAPILogNotSupported on|off off svdhB
Log unsupported feature requests from ISAPI +extensions
ISAPIReadAheadBuffer size 49152 svdhB
Size of the Read Ahead Buffer sent to ISAPI +extensions
KeepAlive On|Off On svC
Enables HTTP persistent connections
KeepAliveTimeout seconds 5 svC
Amount of time the server will wait for subsequent +requests on a persistent connection
LanguagePriority MIME-lang [MIME-lang] +...svdhB
The precendence of language variants for cases where +the client does not express a preference
LDAPCacheEntries number 1024 sE
Maximum number of entries in the primary LDAP cache
LDAPCacheTTL seconds 600 sE
Time that cached items remain valid
LDAPConnectionTimeout secondssE
Specifies the socket connection timeout in seconds
LDAPOpCacheEntries number 1024 sE
Number of entries used to cache LDAP compare +operations
LDAPOpCacheTTL seconds 600 sE
Time that entries in the operation cache remain +valid
LDAPSharedCacheFile directory-path/filenamesE
Sets the shared memory cache file
LDAPSharedCacheSize bytes 102400 sE
Size in bytes of the shared-memory cache
LDAPTrustedClientCert type directory-path/filename/nickname [password]svdhE
Sets the file containing or nickname referring to a per +connection client certificate. Not all LDAP toolkits support per +connection client certificates.
LDAPTrustedGlobalCert type directory-path/filename [password]sE
Sets the file or database containing global trusted +Certificate Authority or global client certificates
LDAPTrustedMode typesvE
Specifies the SSL/TLS mode to be used when connecting to an LDAP server.
LDAPVerifyServerCert On|Off On sE
Force server certificate verification
<Limit method [method] ... > ... + </Limit>svdhC
Restrict enclosed access controls to only certain HTTP +methods
<LimitExcept method [method] ... > ... + </LimitExcept>svdhC
Restrict access controls to all HTTP methods +except the named ones
LimitInternalRecursion number [number] 10 svC
Determine maximum number of internal redirects and nested +subrequests
LimitRequestBody bytes 0 svdhC
Restricts the total size of the HTTP request body sent +from the client
LimitRequestFields number 100 sC
Limits the number of HTTP request header fields that +will be accepted from the client
LimitRequestFieldsize bytessC
Limits the size of the HTTP request header allowed from the +client
LimitRequestLine bytes 8190 sC
Limit the size of the HTTP request line that will be accepted +from the client
LimitXMLRequestBody bytes 1000000 svdhC
Limits the size of an XML-based request body
Listen [IP-address:]portnumber [protocol]sM
IP addresses and ports that the server +listens to
ListenBacklog backlogsM
Maximum length of the queue of pending connections
LoadFile filename [filename] ...sE
Link in the named object file or library
LoadModule module filenamesE
Links in the object file or library, and adds to the list +of active modules
<Location + URL-path|URL> ... </Location>svC
Applies the enclosed directives only to matching +URLs
<LocationMatch + regex> ... </LocationMatch>svC
Applies the enclosed directives only to regular-expression +matching URLs
LockFile filename logs/accept.lock sM
Location of the accept serialization lock file
LogFormat format|nickname +[nickname] "%h %l %u %t \"%r\" +svB
Describes a format for use in a log file
LogLevel level warn svC
Controls the verbosity of the ErrorLog
MaxClients numbersM
Maximum number of child processes that will be created +to serve requests
MaxKeepAliveRequests number 100 svC
Number of requests allowed on a persistent +connection
MaxMemFree KBytes 0 sM
Maximum amount of memory that the main allocator is allowed +to hold without calling free()
MaxRequestsPerChild number 10000 sM
Limit on the number of requests that an individual child server +will handle during its life
MaxRequestsPerThread number 0 sM
Limit on the number of requests that an individual thread +will handle during its life
MaxSpareServers number 10 sM
Maximum number of idle child server processes
MaxSpareThreads numbersM
Maximum number of idle threads
MaxThreads number 2048 sM
Set the maximum number of worker threads
MCacheMaxObjectCount value 1009 sE
The maximum number of objects allowed to be placed in the +cache
MCacheMaxObjectSize bytes 10000 sE
The maximum size (in bytes) of a document allowed in the +cache
MCacheMaxStreamingBuffer size_in_bytes the smaller of 1000 +sE
Maximum amount of a streamed response to buffer in memory +before declaring the response uncacheable
MCacheMinObjectSize bytes 0 sE
The minimum size (in bytes) of a document to be allowed in the +cache
MCacheRemovalAlgorithm LRU|GDSF GDSF sE
The algorithm used to select documents for removal from the +cache
MCacheSize KBytes 100 sE
The maximum amount of memory used by the cache in +KBytes
MetaDir directory .web svdhE
Name of the directory to find CERN-style meta information +files
MetaFiles on|off off svdhE
Activates CERN meta-file processing
MetaSuffix suffix .meta svdhE
File name suffix for the file containg CERN-style +meta information
MimeMagicFile file-pathsvE
Enable MIME-type determination based on file contents +using the specified magic file
MinSpareServers number 5 sM
Minimum number of idle child server processes
MinSpareThreads numbersM
Minimum number of idle threads available to handle request +spikes
MMapFile file-path [file-path] ...sX
Map a list of files into memory at startup time
ModMimeUsePathInfo On|Off Off dB
Tells mod_mime to treat path_info +components as part of the filename
MultiviewsMatch Any|NegotiatedOnly|Filters|Handlers +[Handlers|Filters] NegotiatedOnly svdhB
The types of files that will be included when searching for +a matching file with MultiViews
NameVirtualHost addr[:port]sC
Designates an IP address for name-virtual +hosting
NoProxy host [host] ...svE
Hosts, domains, or networks that will be connected to +directly
NWSSLTrustedCerts filename [filename] ...sB
List of additional client certificates
NWSSLUpgradeable [IP-address:]portnumbersB
Allows a connection to be upgraded to an SSL connection upon request
Options + [+|-]option [[+|-]option] ... All svdhC
Configures what features are available in a particular +directory
Order ordering Deny,Allow dhB
Controls the default access state and the order in which +Allow and Deny are +evaluated.
PassEnv env-variable [env-variable] +...svdhB
Passes environment variables from the shell
PidFile filename logs/httpd.pid sM
File where the server records the process ID +of the daemon
ProtocolEcho On|OffsvX
Turn the echo server on or off
<Proxy wildcard-url> ...</Proxy>svE
Container for directives applied to proxied resources
ProxyBadHeader IsError|Ignore|StartBody IsError svE
Determines how to handle bad header lines in a +response
ProxyBlock *|word|host|domain +[word|host|domain] ...svE
Words, hosts, or domains that are banned from being +proxied
ProxyDomain DomainsvE
Default domain name for proxied requests
ProxyErrorOverride On|Off Off svE
Override error pages for proxied content
ProxyIOBufferSize bytes 8192 svE
Determine size of internal data throughput buffer
<ProxyMatch regex> ...</ProxyMatch>svE
Container for directives applied to regular-expression-matched +proxied resources
ProxyMaxForwards number 10 svE
Maximium number of proxies that a request can be forwarded +through
ProxyPass [path] !|url [key=value key=value ...]]svdE
Maps remote servers into the local server URL-space
ProxyPassReverse [path] urlsvdE
Adjusts the URL in HTTP response headers sent from a reverse +proxied server
ProxyPassReverseCookieDomain internal-domain public-domainsvdE
Adjusts the Domain string in Set-Cookie headers from a reverse- +proxied server
ProxyPassReverseCookiePath internal-path public-pathsvdE
Adjusts the Path string in Set-Cookie headers from a reverse- +proxied server
ProxyPreserveHost On|Off Off svE
Use incoming Host HTTP request header for proxy +request
ProxyReceiveBufferSize bytes 0 svE
Network buffer size for proxied HTTP and FTP +connections
ProxyRemote match remote-serversvE
Remote proxy used to handle certain requests
ProxyRemoteMatch regex remote-serversvE
Remote proxy used to handle requests matched by regular +expressions
ProxyRequests On|Off Off svE
Enables forward (standard) proxy requests
ProxyTimeout seconds 300 svE
Network timeout for proxied requests
ProxyVia On|Off|Full|Block Off svE
Information provided in the Via HTTP response +header for proxied requests
ReadmeName filenamesvdhB
Name of the file that will be inserted at the end +of the index listing
ReceiveBufferSize bytes 0 sM
TCP receive buffer size
Redirect [status] URL-path +URLsvdhB
Sends an external redirect asking the client to fetch +a different URL
RedirectMatch [status] regex +URLsvdhB
Sends an external redirect based on a regular expression match +of the current URL
RedirectPermanent URL-path URLsvdhB
Sends an external permanent redirect asking the client to fetch +a different URL
RedirectTemp URL-path URLsvdhB
Sends an external temporary redirect asking the client to fetch +a different URL
RemoveCharset extension [extension] +...vdhB
Removes any character set associations for a set of file +extensions
RemoveEncoding extension [extension] +...vdhB
Removes any content encoding associations for a set of file +extensions
RemoveHandler extension [extension] +...vdhB
Removes any handler associations for a set of file +extensions
RemoveInputFilter extension [extension] +...vdhB
Removes any input filter associations for a set of file +extensions
RemoveLanguage extension [extension] +...vdhB
Removes any language associations for a set of file +extensions
RemoveOutputFilter extension [extension] +...vdhB
Removes any output filter associations for a set of file +extensions
RemoveType extension [extension] +...vdhB
Removes any content type associations for a set of file +extensions
RequestHeader set|append|add|unset header +[value] [early|env=[!]variable]svdhE
Configure HTTP request headers
Require entity-name [entity-name] ...dhC
Selects which authenticated users can access +a resource
RewriteBase URL-pathdhE
Sets the base URL for per-directory rewrites
RewriteCond + TestString CondPatternsvdhE
Defines a condition under which rewriting will take place +
RewriteEngine on|off off svdhE
Enables or disables runtime rewriting engine
RewriteLock file-pathsE
Sets the name of the lock file used for RewriteMap +synchronization
RewriteLog file-pathsvE
Sets the name of the file used for logging rewrite engine +processing
RewriteLogLevel Level 0 svE
Sets the verbosity of the log file used by the rewrite +engine
RewriteMap MapName MapType:MapSource +svE
Defines a mapping function for key-lookup
RewriteOptions OptionssvdhE
Sets some special options for the rewrite engine
RewriteRule + Pattern SubstitutionsvdhE
Defines rules for the rewriting engine
RLimitCPU seconds|max [seconds|max]svdhC
Limits the CPU consumption of processes launched +by Apache children
RLimitMEM bytes|max [bytes|max]svdhC
Limits the memory consumption of processes launched +by Apache children
RLimitNPROC number|max [number|max]svdhC
Limits the number of processes that can be launched by +processes launched by Apache children
Satisfy Any|All All dhC
Interaction between host-level access control and +user authentication
ScoreBoardFile file-path logs/apache_status sM
Location of the file used to store coordination data for +the child processes
Script method cgi-scriptsvdB
Activates a CGI script for a particular request +method.
ScriptAlias URL-path +file-path|directory-pathsvB
Maps a URL to a filesystem location and designates the +target as a CGI script
ScriptAliasMatch regex +file-path|directory-pathsvB
Maps a URL to a filesystem location using a regular expression +and designates the target as a CGI script
ScriptInterpreterSource Registry|Registry-Strict|Script Script svdhC
Technique for locating the interpreter for CGI +scripts
ScriptLog file-pathsvB
Location of the CGI script error logfile
ScriptLogBuffer bytes 1024 svB
Maximum amount of PUT or POST requests that will be recorded +in the scriptlog
ScriptLogLength bytes 10385760 svB
Size limit of the CGI script logfile
ScriptSock file-path logs/cgisock svB
The filename prefix of the socket to use for communication with +the cgi daemon
SecureListen [IP-address:]portnumber +Certificate-Name [MUTUAL]sB
Enables SSL encryption for the specified port
SendBufferSize bytes 0 sM
TCP buffer size
ServerAdmin email-address|URLsvC
Email address that the server includes in error +messages sent to the client
ServerAlias hostname [hostname] ...vC
Alternate names for a host used when matching requests +to name-virtual hosts
ServerLimit numbersM
Upper limit on configurable number of processes
ServerName fully-qualified-domain-name[:port]svC
Hostname and port that the server uses to identify +itself
ServerPath URL-pathvC
Legacy URL pathname for a name-based virtual host that +is accessed by an incompatible browser
ServerRoot directory-path /usr/local/apache sC
Base directory for the server installation
ServerSignature On|Off|EMail Off svdhC
Configures the footer on server-generated documents
ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full Full sC
Configures the Server HTTP response +header
SetEnv env-variable valuesvdhB
Sets environment variables
SetEnvIf attribute + regex [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables based on attributes of the request +
SetEnvIfNoCase attribute regex + [!]env-variable[=value] + [[!]env-variable[=value]] ...svdhB
Sets environment variables based on attributes of the request +without respect to case
SetHandler handler-name|NonesvdhC
Forces all matching files to be processed by a +handler
SetInputFilter filter[;filter...]svdhC
Sets the filters that will process client requests and POST +input
SetOutputFilter filter[;filter...]svdhC
Sets the filters that will process responses from the +server
SSIEndTag tag "-->" svB
String that ends an include element
SSIErrorMsg message "[an error occurred +svdhB
Error message displayed when there is an SSI +error
SSIStartTag tag "<!--#" svB
String that starts an include element
SSITimeFormat formatstring "%A, %d-%b-%Y %H:%M +svdhB
Configures the format in which date strings are +displayed
SSIUndefinedEcho string "(none)" svdhB
String displayed when an unset variable is echoed
SSLCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Client Auth
SSLCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Client Auth
SSLCADNRequestFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for defining acceptable CA names
SSLCADNRequestPath directory-pathsvE
Directory of PEM-encoded CA Certificates for +defining acceptable CA names
SSLCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Client Auth
SSLCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Client Auth
SSLCertificateChainFile file-pathsvE
File of PEM-encoded Server CA Certificates
SSLCertificateFile file-pathsvE
Server PEM-encoded X.509 Certificate file
SSLCertificateKeyFile file-pathsvE
Server PEM-encoded Private Key file
SSLCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +handshake
SSLCryptoDevice engine builtin sE
Enable use of a cryptographic hardware accelerator
SSLEngine on|off|optional off svE
SSL Engine Operation Switch
SSLHonorCiperOrder flagsvE
Option to prefer the server's cipher preference order
SSLMutex type none sE
Semaphore for internal mutual exclusion of +operations
SSLOptions [+|-]option ...svdhE
Configure various SSL engine run-time options
SSLPassPhraseDialog type builtin sE
Type of pass phrase dialog for encrypted private +keys
SSLProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors
SSLProxyCACertificateFile file-pathsvE
File of concatenated PEM-encoded CA Certificates +for Remote Server Auth
SSLProxyCACertificatePath directory-pathsvE
Directory of PEM-encoded CA Certificates for +Remote Server Auth
SSLProxyCARevocationFile file-pathsvE
File of concatenated PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCARevocationPath directory-pathsvE
Directory of PEM-encoded CA CRLs for +Remote Server Auth
SSLProxyCipherSuite cipher-spec ALL:!ADH:RC4+RSA:+H +svdhE
Cipher Suite available for negotiation in SSL +proxy handshake
SSLProxyEngine on|off off svE
SSL Proxy Engine Operation Switch
SSLProxyMachineCertificateFile filenamesE
File of concatenated PEM-encoded client certificates and keys to be used by the proxy
SSLProxyMachineCertificatePath directorysE
Directory of PEM-encoded client certificates and keys to be used by the proxy
SSLProxyProtocol [+|-]protocol ... all svE
Configure usable SSL protocol flavors for proxy usage
SSLProxyVerify level none svdhE
Type of remote server Certificate verification
SSLProxyVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Remote Server +Certificate verification
SSLRandomSeed context source +[bytes]sE
Pseudo Random Number Generator (PRNG) seeding +source
SSLRequire expressiondhE
Allow access only when an arbitrarily complex +boolean expression is true
SSLRequireSSLdhE
Deny access when SSL is not used for the +HTTP request
SSLSessionCache type none sE
Type of the global/inter-process SSL Session +Cache
SSLSessionCacheTimeout seconds 300 svE
Number of seconds before an SSL session expires +in the Session Cache
SSLUserName varnamesdhE
Variable name to determine user name
SSLVerifyClient level none svdhE
Type of Client Certificate verification
SSLVerifyDepth number 1 svdhE
Maximum depth of CA Certificates in Client +Certificate verification
StartServers numbersM
Number of child server processes created at startup
StartThreads numbersM
Number of threads created on startup
SuexecUserGroup User GroupsvE
User and group permissions for CGI programs
ThreadLimit numbersM
Sets the upper limit on the configurable number of threads +per child process
ThreadsPerChild numbersM
Number of threads created by each child process
ThreadStackSize sizesM
The size in bytes of the stack used by threads handling +client connections
TimeOut seconds 300 sC
Amount of time the server will wait for +certain events before failing a request
TraceEnable [on|off|extended] on sC
Determines the behaviour on TRACE +requests
TransferLog file|pipesvB
Specify location of a log file
TypesConfig file-path conf/mime.types sB
The location of the mime.types file
UnsetEnv env-variable [env-variable] +...svdhB
Removes variables from the environment
UseCanonicalName On|Off|DNS Off svdC
Configures how the server determines its own name and +port
UseCanonicalPhysicalPort On|Off Off svdC
Configures how the server determines its own name and +port
User unix-userid #-1 sM
The userid under which the server will answer +requests
UserDir directory-filenamesvB
Location of the user-specific directories
VirtualDocumentRoot interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
VirtualDocumentRootIP interpolated-directory|none none svE
Dynamically configure the location of the document root +for a given virtual host
<VirtualHost + addr[:port] [addr[:port]] + ...> ... </VirtualHost>sC
Contains directives that apply only to a specific +hostname or IP address
VirtualScriptAlias interpolated-directory|none none svE
Dynamically configure the location of the CGI directory for +a given virtual host
VirtualScriptAliasIP interpolated-directory|none none svE
Dynamically configure the location of the cgi directory for +a given virtual host
Win32DisableAcceptExsM
Use accept() rather than AcceptEx() to accept network connections
XBitHack on|off|full off svdhB
Parse SSI directives in files with the execute bit +set
+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + es  | + ja  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/worker.html b/docs/manual/mod/worker.html new file mode 100644 index 00000000..1d429299 --- /dev/null +++ b/docs/manual/mod/worker.html @@ -0,0 +1,11 @@ +URI: worker.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: worker.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: worker.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/mod/worker.html.de b/docs/manual/mod/worker.html.de new file mode 100644 index 00000000..4dd3fbb3 --- /dev/null +++ b/docs/manual/mod/worker.html.de @@ -0,0 +1,170 @@ + + + +worker - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2 > Module
+
+

Apache-MPM worker

+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+ + + +
Beschreibung:Multi-Processing-Modul, das einen Hybrid-Webserver mit + Multi-Thread und Multi-Prozess-Unterstützung implementiert
Status:MPM
Modulbezeichner:mpm_worker_module
Quelltext-Datei:worker.c
+

Zusammenfassung

+ +

Dieses Multi-Processing-Modul (MPM) implementiert einen Hybrid-Server + mit Multi-Thread und Multi-Prozess-Unterstützung. Durch die Verwendung + von Threads für die Bedienung von Anfragen ist er in der Lage, + eine große Anzahl von Anfragen mit weniger Systemressourcen als + ein Prozess-basierter Server zu bedienen. Er behält jedoch viel von + der Stabilität eines Prozess-basierten Servers bei, indem er + mehrere Prozesse verfügbar hält, jeden mit etlichen Threads.

+ +

Die wichtigsten Direktiven zur Steuerung des MPMs sind ThreadsPerChild, welche die Anzahl + der Threads beeinflusst, die von jedem Kindprozess verwendet werden, und + MaxClients, welche die + maximale Gesamtzahl an Threads regelt, die gestartet werden + können.

+
+ +
top
+
+

Arbeitsweise

+

Ein einzelner Steuerprozess (der Elternprozess) ist für den + Start der Kindprozesse verantwortlich. Jeder Kindprozess erstellt eine + feste Anzahl von Server-Threads, wie durch die ThreadsPerChild-Direktive + angegeben, sowie einen "Listener-Thread", der auf Verbindungen wartet und + diese an einen Server-Thread zur Bearbeitung weiterreicht, sobald sie + eintreffen.

+ +

Der Apache versucht immer, einen Vorrat von freien oder + unbeschäftigten Threads zu verwalten, die zur Bedienung + hereinkommender Anfragen bereit stehen. Auf diese Weise brauchen + Clients nicht auf die Erstellung eines neuen Threads oder Prozesses + zu warten, bevor ihre Anfrage bedient werden kann. Die Anzahl der + Prozesse, die anfangs gestartet wird, wird mit der Direktive + StartServers festgelegt. + Dann, während des Betriebes, berechnet der Apache die Gesamtzahl + der unbeschäftigten Threads und forkt oder beendet Prozesse, um diese + Anzahl innerhalb der durch MinSpareThreads und MaxSpareThreads angegebenen Grenzen + zu halten. Da dieser Prozess sehr selbstregulierend ist, ist es nur selten + notwendig, die Voreinstellung dieser Direktiven zu ändern. Die + maximale Anzahl Clients, die gleichzeitig bedient werden kann (d.h. + die maximale Gesamtzahl der Threads in allen Prozessen), wird mit der + Direktive MaxClients + festgelegt. Die maximale Anzahl der aktiven Kindprozesse ergibt sich aus + MaxClients dividiert durch + ThreadsPerChild.

+ +

Zwei Direktiven legen harte Limits für die Anzahl der aktiven + Kindprozesse fest und können nur geändert werden, indem der Server + komplett gestoppt und dann wieder neu gestartet wird. ServerLimit stellt die obere Grenze für + die Anzahl der aktiven Kindprozesse dar und muss größer oder + gleich dem Quotienten aus MaxClients und ThreadsPerChild sein. ThreadLimit ist die obere Grenze für + die Anzahl der Server-Threads und muss größer oder gleich + ThreadsPerChild sein. Sofern für + diese Direktiven keine Voreinstellungen verwendet werden, sollten sie vor + allen anderen worker-Direktiven platziert werden.

+ +

Neben den normalen aktiven Kindprozessen gibt es möglicherweise noch + zusätzliche Kindprozesse, welche gerade beendet werden, wo allerdings + zumindest noch ein Server-Thread eine existierende Verbindung bearbeitet. + Obwohl die tatsächlich zu erwartende Anzahl deutlich kleiner ist, + können bis zu MaxClients + solcher Prozesse auftreten. Dieses Verhalten können Sie vermeiden, + indem Sie die Terminierung einzelner Kindprozesse wie folgt abschalten:

+ + + +

Eine typische Konfiguration der Prozess-Thread-Steuerung für + das MPM worker könnte wie folgt aussehen:

+ +

+ ServerLimit 16
+ StartServers 2
+ MaxClients 150
+ MinSpareThreads 25
+ MaxSpareThreads 75
+ ThreadsPerChild 25 +

+ +

Während der Elternprozess unter Unix normalerweise als + root gestartet wird, um sich an Port 80 binden zu können, + werden die Kindprozesse und Threads unter einem weniger privilegierten + Benutzer gestartet. Die Direktiven User und Group werden dazu verwendet, die + Privilegien der Apache-Kindprozesse festzulegen. Die Kindprozesse + müssen in der Lage sein, alle Inhalte zu lesen, die sie ausliefern + sollen, sollten darüber hinaus jedoch so wenig wie möglich Rechte + besitzen. Zusätzlich, solange nicht suexec verwendet wird, legen diese + Direktiven auch die Privilegien fest, die von CGI-Skripts + geerbt werden.

+ +

MaxRequestsPerChild + bestimmt, wie häufig der Server Prozesse erneuert, indem er alte + beendet und neue startet.

+
+
+
+

Verfügbare Sprachen:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/worker.html.en b/docs/manual/mod/worker.html.en new file mode 100644 index 00000000..55ac3595 --- /dev/null +++ b/docs/manual/mod/worker.html.en @@ -0,0 +1,177 @@ + + + +worker - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Modules
+
+

Apache MPM worker

+
+

Available Languages:  de  | + en  | + ja 

+
+ + + +
Description:Multi-Processing Module implementing a hybrid + multi-threaded multi-process web server
Status:MPM
Module Identifier:mpm_worker_module
Source File:worker.c
+

Summary

+ +

This Multi-Processing Module (MPM) implements a hybrid + multi-process multi-threaded server. By using threads to serve + requests, it is able to serve a large number of requests with + fewer system resources than a process-based server. However, it + retains much of the stability of a process-based server by + keeping multiple processes available, each with many threads.

+ +

The most important directives used to control this MPM are + ThreadsPerChild, which + controls the number of threads deployed by each child process and + MaxClients, which + controls the maximum total number of threads that may be + launched.

+
+ +
top
+
+

How it Works

+

A single control process (the parent) is responsible for launching + child processes. Each child process creates a fixed number of server + threads as specified in the ThreadsPerChild directive, as well + as a listener thread which listens for connections and passes them + to a server thread for processing when they arrive.

+ +

Apache always tries to maintain a pool of spare or + idle server threads, which stand ready to serve incoming + requests. In this way, clients do not need to wait for a new + threads or processes to be created before their requests can be + served. The number of processes that will initially launched is + set by the StartServers + directive. During operation, Apache assesses the total number + of idle threads in all processes, and forks or kills processes to + keep this number within the boundaries specified by MinSpareThreads and MaxSpareThreads. Since this + process is very self-regulating, it is rarely necessary to modify + these directives from their default values. The maximum number of + clients that may be served simultaneously (i.e., the maximum total + number of threads in all processes) is determined by the + MaxClients directive. + The maximum number of active child processes is determined by + the MaxClients + directive divided by the + ThreadsPerChild directive.

+ +

Two directives set hard limits on the number of active child + processes and the number of server threads in a child process, + and can only be changed by fully stopping the server and then + starting it again. ServerLimit + is a hard limit on the number of active child + processes, and must be greater than or equal to the + MaxClients + directive divided by the + ThreadsPerChild directive. + ThreadLimit is a hard + limit of the number of server threads, and must be greater than + or equal to the ThreadsPerChild directive. If + non-default values are specified for these directives, they + should appear before other worker directives.

+ +

In addition to the set of active child processes, there may + be additional child processes which are terminating, but where at + least one server thread is still handling an existing client + connection. Up to MaxClients terminating processes + may be present, though the actual number can be expected to be + much smaller. This behavior can be avoided by disabling the + termination of individual child processes, which is achieved using + the following:

+ + + +

A typical configuration of the process-thread controls in + the worker MPM could look as follows:

+ +

+ ServerLimit 16
+ StartServers 2
+ MaxClients 150
+ MinSpareThreads 25
+ MaxSpareThreads 75
+ ThreadsPerChild 25 +

+ +

While the parent process is usually started as root + under Unix in order to bind to port 80, the child processes and threads + are launched by Apache as a less-privileged user. The User and Group directives are used to set + the privileges of the Apache child processes. The child processes + must be able to read all the content that will be served, but + should have as few privileges beyond that as possible. In + addition, unless suexec is used, + these directives also set the privileges which will be inherited + by CGI scripts.

+ +

MaxRequestsPerChild + controls how frequently the server recycles processes by killing + old ones and launching new ones.

+
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mod/worker.html.ja.euc-jp b/docs/manual/mod/worker.html.ja.euc-jp new file mode 100644 index 00000000..f2599576 --- /dev/null +++ b/docs/manual/mod/worker.html.ja.euc-jp @@ -0,0 +1,187 @@ + + + +worker - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > ¥â¥¸¥å¡¼¥ë
+
+

Apache MPM worker

+
+

Available Languages:  de  | + en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ + + +
ÀâÌÀ:¥Þ¥ë¥Á¥¹¥ì¥Ã¥É¤È¥Þ¥ë¥Á¥×¥í¥»¥¹¤Î¥Ï¥¤¥Ö¥ê¥Ã¥É·¿ +¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¼ÂÁõ¤·¤¿¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë
¥¹¥Æ¡¼¥¿¥¹:MPM
¥â¥¸¥å¡¼¥ë¼±ÊÌ»Ò:mpm_worker_module
¥½¡¼¥¹¥Õ¥¡¥¤¥ë:worker.c
+

³µÍ×

+ +

¤³¤Î¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM) + ¤Ï¡¢¥Þ¥ë¥Á¥¹¥ì¥Ã¥É¤È¥Þ¥ë¥Á¥×¥í¥»¥¹¤Î¥Ï¥¤¥Ö¥ê¥Ã¥É·¿¥µ¡¼¥Ð¤ò + ¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£¥ê¥¯¥¨¥¹¥È¤Î±þÅú¤Ë¥¹¥ì¥Ã¥É¤ò»È¤¦¤È¡¢ + ¥×¥í¥»¥¹¥Ù¡¼¥¹¤Î¥µ¡¼¥Ð¤è¤ê¤â¾¯¤Ê¤¤¥·¥¹¥Æ¥à»ñ¸»¤Ç¡¢ + ¿¤¯¤Î¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤µ¤é¤Ë¡¢Â¿¤¯¤Î¥¹¥ì¥Ã¥É¤ò»ý¤Ã¤¿Ê£¿ô¤Î¥×¥í¥»¥¹¤ò°Ý»ý¤¹¤ë¤³¤È¤Ç¡¢ + ¥×¥í¥»¥¹¥Ù¡¼¥¹¤Î¥µ¡¼¥Ð¤Î»ý¤Ä°ÂÄêÀ­¤òÊÝ»ý¤·¤Æ¤¤¤Þ¤¹¡£

+ +

¤³¤Î MPM ¤òÀ©¸æ¤¹¤ë¤Î¤Ë»È¤ï¤ì¤ëºÇ¤â½ÅÍפʥǥ£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ThreadsPerChild ¤È + MaxClients ¤Ç¤¹¡£ + ThreadsPerChild ¤Ï + ³Æ»Ò¥×¥í¥»¥¹¤ÇÍÑ°Õ¤µ¤ì¤ë¥¹¥ì¥Ã¥É¿ô¤òÀ©¸æ¤·¤Æ¡¢ + MaxClients ¤Ï + µ¯Æ°¤µ¤ì¤ë¥¹¥ì¥Ã¥É¤ÎÁí¿ô¤ÎºÇÂçÃͤòÀ©¸Â¤·¤Þ¤¹¡£

+
+ +
top
+
+

Æ°ºîÊýË¡

+

°ì¤Ä¤ÎÀ©¸æÍÑ¥×¥í¥»¥¹ (¿Æ) ¤¬»Ò¥×¥í¥»¥¹¤òµ¯Æ°¤·¤Þ¤¹¡£ + »Ò¥×¥í¥»¥¹¤Ï + ThreadsPerChild + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤵ¤ì¤¿°ìÄê¿ô¤Î¥µ¡¼¥Ð¥¹¥ì¥Ã¥É¤ÈÀܳ¤ò + listen ¤¹¤ë¥¹¥ì¥Ã¥É¤ò°ì¤Äºî¤ê¤Þ¤¹¡£ + Listener ¥¹¥ì¥Ã¥É¤ÏÀܳ¤¬Í褿¤È¤­¤Ë¥µ¡¼¥Ð¥×¥í¥»¥¹¤ËÅϤ·¤Þ¤¹¡£

+ +

Apache ¤Ï¥¹¥Ú¥¢¤Î¡¢¤Ä¤Þ¤ê¥¢¥¤¥É¥ë¤Ê¥µ¡¼¥Ð¥¹¥ì¥Ã¥É¤Î + ¥×¡¼¥ë¤ò¾ï¤Ë°Ý»ý¤·¤Æ¤¤¤Æ¡¢¤½¤ì¤é¤ÏÆþ¤Ã¤Æ¤¯¤ë¥ê¥¯¥¨¥¹¥È¤Ë + Åú¤¨¤é¤ì¤ë¤è¤¦¤ËÂÔµ¡¤·¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Ë¤·¤Æ¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï¥ê¥¯¥¨¥¹¥È¤Î±þÅú¤¬ÆÀ¤é¤ì¤ë¤è¤¦¤Ë¤Ê¤ë¤¿¤á¤Ë + ¿·¤·¤¤¥¹¥ì¥Ã¥É¤ä¥×¥í¥»¥¹¤¬À¸À®¤µ¤ì¤ë¤Î¤ò + ÂÔ¤¿¤Ê¤¯¤Æ¤â¤è¤¤¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + µ¯Æ°½é´ü»þ¤Î¥×¥í¥»¥¹Áí¿ô¤Ï¡¢ + StartServers + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤵ¤ì¤Þ¤¹¡£¤½¤Î¸å¤Î²ÔƯÃæ¤Ë¡¢ + Apache ¤ÏÁ´¥×¥í¥»¥¹¤Î¥¢¥¤¥É¥ë¥¹¥ì¥Ã¥É¤Î¹ç·×¿ô¤ò¸«ÀѤâ¤Ã¤Æ¡¢ + MinSpareThreads ¤È + MaxSpareThreads + ¤Ç»ØÄꤵ¤ì¤¿ÈϰϤÎÃæ¤Ë¤³¤Î¿ô¤¬¼ý¤Þ¤ë¤è¤¦¤Ë fork ¤·¤¿¤ê + kill ¤·¤¿¤ê¤·¤Þ¤¹¡£¤³¤ÎÁàºî¤ÏÈó¾ï¤Ë¼«Î§Åª¤Ê¤Î¤Ç¡¢ + ¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¥Ç¥Õ¥©¥ë¥ÈÃͤ«¤éÊѹ¹¤¹¤ëɬÍ×¤Ï + ¤á¤Ã¤¿¤Ë¤Ê¤¤¤Ç¤·¤ç¤¦¡£ + Ʊ»þ¤Ë±þÅú¤¹¤ë¤³¤È¤Î¤Ç¤­¤ë¥¯¥é¥¤¥¢¥ó¥È¿ô¤ÎºÇÂç¿ô + (¤Ä¤Þ¤êÁ´¥×¥í¥»¥¹Ãæ¤ÎÁí¥¹¥ì¥Ã¥É¿ô¤ÎºÇÂçÃÍ) ¤Ï + MaxClients + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç·èÄꤵ¤ì¤Þ¤¹¡£ + ³èÆ°Ãæ¤Î»Ò¥×¥í¥»¥¹¿ô¤ÎºÇÂçÃÍ¤Ï + MaxClients ¤ò + ThreadsPerChild ¤Ç³ä¤Ã¤¿ + ¤â¤Î¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

³èÆ°Ãæ¤Î»Ò¥×¥í¥»¥¹¤Î¿ô¤È»Ò¥×¥í¥»¥¹Ãæ¤Î¥µ¡¼¥Ð¥¹¥ì¥Ã¥É¤Î¿ô¤Î±Û¤¨¤é¤ì¤Ê¤¤ + ¾å¸Â¤òÀßÄꤹ¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Æó¤Ä¤¢¤ê¤Þ¤¹¡£¤³¤ì¤é¤Ï¥µ¡¼¥Ð¤ò + ´°Á´¤ËÄä»ß¤·¤Æ¡¢ºÆµ¯Æ°¤¹¤ë¤³¤È¤Ç¤·¤«Êѹ¹¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ + ServerLimit + ¤Ï³èÆ°Ãæ¤Î»Ò¥×¥í¥»¥¹¤Î±Û¤¨¤é¤ì¤Ê¤¤¾å¸Â¤òÀßÄꤷ¡¢ + MaxClients ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤ÎÃͤò + ThreadsPerChild ¤ÎÃͤdzä¤Ã¤¿ÃͰʾå¤Ç¤¢¤ë + ɬÍפ¬¤¢¤ê¤Þ¤¹¡£ThreadLimit ¤Ï + ¥µ¡¼¥Ð¥¹¥ì¥Ã¥É¤Î±Û¤¨¤é¤ì¤Ê¤¤¾å¸Â¤Ç¡¢ThreadsPerChild ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î + ÃͰʾå¤Ç¤¢¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È°Ê³°¤ÎÃͤò»ØÄꤹ¤ë¾ì¹ç¤Ï + ¾¤Î worker ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤è¤ê¤âÁ°¤Ë½ñ¤«¤ì¤Æ¤¤¤ë + ɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

³èÆ°Ãæ¤Î»Ò¥×¥í¥»¥¹·²¤Ë²Ã¤¨¤Æ¡¢¾¯¤Ê¤¯¤È¤â°ì¤Ä¤Î¥µ¡¼¥Ð¥¹¥ì¥Ã¥É¤¬ + ´û¸¤Î¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤ÎÀܳ¤ò°·¤Ã¤Æ¤¤¤ë½ªÎ»¤·¤è¤¦¤È¤·¤Æ¤¤¤ë + »Ò¥×¥í¥»¥¹¤¬¤¢¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£½ªÎ»Ãæ¤Î¥×¥í¥»¥¹¤Ï MaxClients ¤Ç»ØÄꤵ¤ì¤¿¿ô¤Þ¤Ç + ¸ºß¤Ç¤­¤Þ¤¹¤¬¡¢¼ÂºÝ¤Ë´üÂÔ¤µ¤ì¤ë¿ô¤Ï¤º¤Ã¤È¾¯¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£¤³¤Î + ¿¶Éñ¤¤¤Ï³Æ»Ò¥×¥í¥»¥¹¤ò½ªÎ»¤µ¤»¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ç²óÈò¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ï°Ê²¼¤ÎÍͤˤ·¤Æ¼Â¸½¤Ç¤­¤Þ¤¹¡£

+ + + +

worker MPM ¤Îŵ·¿Åª¤Ê¥×¥í¥»¥¹¡¦¥¹¥ì¥Ã¥ÉÀ©¸æ¤Î + ÀßÄê¤Ç¤Ï¡¢¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

+ ServerLimit 16
+ StartServers 2
+ MaxClients 150
+ MinSpareThreads 25
+ MaxSpareThreads 75
+ ThreadsPerChild 25 +

+ +

Ä̾ï Unix ¤Ç¤Ï¿Æ¥×¥í¥»¥¹¤Ï 80 È֥ݡ¼¥È¤Ë¥Ð¥¤¥ó¥É¤¹¤ë¤¿¤á¤Ë + root ¤Çµ¯Æ°¤µ¤ì¤Þ¤¹¤¬¡¢»Ò¥×¥í¥»¥¹¤ä¥¹¥ì¥Ã¥É¤Ï + ¤â¤Ã¤ÈÄ㤤¸¢¸Â¤Î¥æ¡¼¥¶¤Ç Apache ¤Ë¤è¤Ã¤Æµ¯Æ°¤µ¤ì¤Þ¤¹¡£ + User ¤È + Group ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + Apache ¤Î»Ò¥×¥í¥»¥¹¤Î¸¢¸Â¤òÀßÄꤹ¤ë¤Î¤ËÍѤ¤¤é¤ì¤Þ¤¹¡£ + »Ò¥×¥í¥»¥¹¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤ë¥³¥ó¥Æ¥ó¥ÄÁ´¤Æ¤òÆɤá¤Ê¤¤¤È¤¤¤±¤Þ¤»¤ó¤¬¡¢ + ²Äǽ¤Ê¸Â¤êɬÍ׺Ǿ®¸Â¤Î¸¢¸Â¤Î¤ß¤ò»ý¤Ã¤Æ¤¤¤ë¤è¤¦¤Ë¤¹¤ë¤Ù¤­¤Ç¤¹¡£ + ¤µ¤é¤Ë¡¢suexec + ¤¬»ÈÍѤµ¤ì¤Æ¤¤¤Ê¤¤¸Â¤ê¡¢¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + CGI ¥¹¥¯¥ê¥×¥È¤Ç·Ñ¾µ¤µ¤ì¤ë¸¢¸Â¤âÀßÄꤷ¤Þ¤¹¡£

+ +

MaxRequestsPerChild + ¤Ï¡¢¸Å¤¤¥×¥í¥»¥¹¤òÄä»ß¤·¤Æ¿·¤·¤¤¥×¥í¥»¥¹¤òµ¯Æ°¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢ + ¤É¤ÎÄøÅÙ¤ÎÉÑÅ٤ǥµ¡¼¥Ð¤¬¥×¥í¥»¥¹¤ò¥ê¥µ¥¤¥¯¥ë¤¹¤ë¤«¤òÀ©¸æ¤·¤Þ¤¹¡£

+
+
+
+

Available Languages:  de  | + en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/mpm.html b/docs/manual/mpm.html new file mode 100644 index 00000000..c34f5f04 --- /dev/null +++ b/docs/manual/mpm.html @@ -0,0 +1,19 @@ +URI: mpm.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: mpm.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mpm.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: mpm.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: mpm.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/mpm.html.de b/docs/manual/mpm.html.de new file mode 100644 index 00000000..66b6b086 --- /dev/null +++ b/docs/manual/mpm.html.de @@ -0,0 +1,125 @@ + + + +Multi-Processing-Module (MPMs) - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Multi-Processing-Module (MPMs)

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko 

+
+ +

Das Dokument beschreibt, was ein Multi-Processing-Modul ist und wie solche + Module beim Apache HTTP Server verwendet werden.

+
+ +
top
+
+

Einführung

+ +

Der Apache HTTP Server wurde als leistungsfähiger und flexibler Webserver + konzipiert, der auf einer Vielzahl von Plattformen in einer + Reihe unterschiedlicher Umgebungen arbeiten kann. Unterschiedliche + Plattformen und unterschiedliche Umgebungen verlangen oftmals verschiedene + Fähigkeiten oder kennen verschiedene Wege, die gleiche + Funktionaltät sehr effizient zu implementieren. Der Apache hat durch + seinen modularen Aufbau schon immer eine breite Auswahl von Umgebungen + unterstützt. Dieses Design erlaubt es dem Webmaster, durch Auswahl der + Module, die zur Kompilierungszeit oder zur Laufzeit geladen werden, die + Features auszuwählen, die in den Server intregiert werden.

+ +

Der Apache 2.0 erweitert dieses modulare Design auf die grundlegenden + Funktionen eines Webservers. Der Server wird mit einer Auswahl von + Multi-Processing-Modulen (MPMs) ausgeliefert, die für die Bindung an + Netzwerkports der Maschine, die Annahme von Anfragen und die Abfertigung von + Kindprozessen zur Behandlung der Anfragen zuständig sind.

+ +

Die Erweiterung des modularen Aufbaus auf diese Ebene des Servers + bringt zwei wesentliche Vorteile:

+ +
    +
  • Der Apache kann nun eine Vielfalt von Betriebssystemen sauberer und + effizienter unterstützen. Insbesondere die Windows-Version des Apache + ist jetzt deutlich effizienter, da mpm_winnt native + Netzwerkfähigkeiten anstelle der im Apache 1.3 verwendeten + POSIX-Schicht benutzen kann. Dieser Vorteil gilt auch für andere + Betriebssysteme, für die spezielle MPMs implementiert sind.
    • + +
  • Der Server läßt sich besser auf die Bedürfnisse der + jeweiligen Website anpassen. Sites beispielsweise, die eine hohe + Skalierbarkeit benötigen, können ein Threaded-MPM wie + worker oder event wählen, + während Sites, die Stabilität oder Kompatibilität mit + älterer Software erfordern, prefork wählen + können.
    • +
+ +

Auf Anwenderebene erscheinen MPMs fast wie andere Apache-Module. Der + Hauptunterschied ist, dass jeweils nur ein einziges MPM in den Server + geladen werden kann. Die Liste der verfügbaren MPMs finden Sie im Modul-Index.

+ +
top
+
+

Auswahl eines MPMs

+ +

MPMs müssen während der + (Anm.d.Ü.: Quelltext-)Konfiguration ausgewählt und in den + Server einkompiliert werden. Compiler sind in der Lage eine Reihe von + Funktionen zu optimieren, wenn Threads verwendet werden. Sie können + dies allerdings nur, wenn sie wissen, dass Threads benutzt werden.

+ +

Um das gewünschte MPM tatsächlich auszuwählen, verwenden Sie + beim configure-Skript das Argument + --with-mpm=NAME. NAME ist der Name des + gewünschten MPMs.

+ +

Ist der Server kompiliert, so ist es mittels ./httpd -l + möglich, das ausgewählte MPM zu ermitteln. Dieser Befehl listet + alle in den Server einkompilierten Module auf, einschließlich des + MPM.

+
top
+
+

MPM-Voreinstellungen

+ +

Die folgende Tabelle gibt die voreingestellten MPMs für verschiedene + Betriebssysteme an. Wenn Sie während der Kompilierung keine andere + Auswahl treffen, wird dieses MPM gewählt.

+ + + + + + + + +
BeOSbeos
Netwarempm_netware
OS/2mpmt_os2
Unixprefork
Windowsmpm_winnt
+
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mpm.html.en b/docs/manual/mpm.html.en new file mode 100644 index 00000000..c8e5e03a --- /dev/null +++ b/docs/manual/mpm.html.en @@ -0,0 +1,125 @@ + + + +Multi-Processing Modules (MPMs) - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Multi-Processing Modules (MPMs)

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ +

This document describes what a Multi-Processing Module is and +how they are used by the Apache HTTP Server.

+
+ +
top
+
+

Introduction

+ +

The Apache HTTP Server is designed to be a powerful and + flexible web server that can work on a very wide variety of + platforms in a range of different environments. Different + platforms and different environments often require different + features, or may have different ways of implementing the same + feature most efficiently. Apache has always accommodated a wide + variety of environments through its modular design. This design + allows the webmaster to choose which features will be included + in the server by selecting which modules to load either at + compile-time or at run-time.

+ +

Apache 2.0 extends this modular design to the most basic + functions of a web server. The server ships with a selection of + Multi-Processing Modules (MPMs) which are responsible for + binding to network ports on the machine, accepting requests, + and dispatching children to handle the requests.

+ +

Extending the modular design to this level of the server + allows two important benefits:

+ +
    +
  • Apache can more cleanly and efficiently support a wide + variety of operating systems. In particular, the Windows + version of Apache is now much more efficient, since + mpm_winnt can use native + networking features in place of the POSIX layer used in + Apache 1.3. This benefit also extends to other operating + systems that implement specialized MPMs.
    • + +
  • The server can be better customized for the needs of the + particular site. For example, sites that need a great deal of + scalability can choose to use a threaded MPM like + worker or event, while sites requiring + stability or compatibility with older software can use a + prefork.
    • +
+ +

At the user level, MPMs appear much like other Apache + modules. The main difference is that one and only one MPM must + be loaded into the server at any time. The list of available + MPMs appears on the module index page.

+ +
top
+
+

Choosing an MPM

+ +

MPMs must be chosen during configuration, and compiled into + the server. Compilers are capable of optimizing a lot of + functions if threads are used, but only if they know that + threads are being used.

+ +

To actually choose the desired MPM, use the argument + --with-mpm=NAME with the + configure script. NAME is the name of the + desired MPM.

+ +

Once the server has been compiled, it is possible to + determine which MPM was chosen by using ./httpd + -l. This command will list every module that is compiled + into the server, including the MPM.

+
top
+
+

MPM Defaults

+ +

The following table lists the default MPMs for various operating +systems. This will be the MPM selected if you do not make another +choice at compile-time.

+ + + + + + + + +
BeOSbeos
Netwarempm_netware
OS/2mpmt_os2
Unixprefork
Windowsmpm_winnt
+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mpm.html.es b/docs/manual/mpm.html.es new file mode 100644 index 00000000..dcdfa364 --- /dev/null +++ b/docs/manual/mpm.html.es @@ -0,0 +1,139 @@ + + + +Módulos de MultiProcesamiento (MPMs) - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

Módulos de MultiProcesamiento (MPMs)

+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ +

Este documento describe que es un Módulo de Multiprocesamiento y +como los usa Apache.

+
+ +
top
+
+

Introducción

+ +

Apache está diseñado para ser un servidor web potente + y flexible que pueda funcionar en la más amplia variedad de + plataformas y entornos. Las diferentes plataformas y los + diferentes entornos, hacen que a menudo sean necesarias diferentes + características o funcionalidades, o que una misma + característica o funcionalidad sea implementada de diferente + manera para obtener una mayor eficiencia. Apache se ha adaptado + siempre a una gran variedad de entornos a través de su + diseño modular. Este diseño permite a los + administradores de sitios web elegir que características van + a ser incluidas en el servidor seleccionando que módulos se + van a cargar, ya sea al compilar o al ejecutar el servidor.

+ +

Apache 2.0 extiende este diseño modular hasta las + funciones más básicas de un servidor web. El servidor + viene con una serie de Módulos de MultiProcesamiento que son + responsables de conectar con los puertos de red de la + máquina, acceptar las peticiones, y generar los procesos hijo + que se encargan de servirlas.

+ +

La extensión del diseño modular a este nivel del + servidor ofrece dos beneficios importantes:

+ +
    +
  • Apache puede soportar de una forma más fácil y + eficiente una amplia variedad de sistemas operativos. En + concreto, la versión de Windows de Apache es mucho más + eficiente, porque el módulo mpm_winnt + puede usar funcionalidades nativas de red en lugar de usar la + capa POSIX como hace Apache 1.3. Este beneficio se extiende + también a otros sistemas operativos que implementan sus + respectivos MPMs.
    • + +
  • El servidor puede personalizarse mejor para las necesidades + de cada sitio web. Por ejemplo, los sitios web que necesitan + más que nada escalibildad pueden usar un MPM hebrado como + worker, mientras que los sitios web que + requieran por encima de otras cosas estabilidad o compatibilidad + con software antiguo pueden usar + prefork. Además, se pueden configurar + funcionalidades especiales como servir diferentes hosts con + diferentes identificadores de usuario + (perchild).
    • +
+ +

A nivel de usuario, los MPMs son como cualquier otro + módulo de Apache. La diferencia más importante es que + solo un MPM puede estar cargado en el servidor en un determinado + momento. La lista de MPMs disponibles está en la sección índice de Módulos.

+ +
top
+
+

Cómo Elegir un MPM

+ +

Los MPMs deben elegirse durante el proceso de + configuración, y deben ser compilados en el servidor. Los + compiladores son capaces de optimizar muchas funciones si se usan + hebras, pero solo si se sabe que se están usando hebras. Como + algunos MPM usan hebras en Unix y otros no, Apache tendrá un + mejor rendimiento si el MPM es elegido en el momento de compilar y + está incorporado en el servidor.

+ +

Para elegir el MPM deseado, use el argumento --with-mpm= + NAME con el script ./configure. NAME es el + nombre del MPM deseado.

+ +

Una vez que el servidor ha sido compilado, es posible + determinar que MPM ha sido elegido usando ./httpd + -l. Este comando lista todos los módulos compilados en + el servidor, incluido en MPM.

+
top
+
+

MPM por defecto

+ +

En la siguiente tabla se muestran los MPMs por defecto para varios +sistemas operativos. Estos serán los MPM seleccionados si no se +especifica lo contrario al compilar.

+ + + + + + + + +
BeOSbeos
Netwarempm_netware
OS/2mpmt_os2
Unixprefork
Windowsmpm_winnt
+
+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mpm.html.ja.euc-jp b/docs/manual/mpm.html.ja.euc-jp new file mode 100644 index 00000000..38aebda6 --- /dev/null +++ b/docs/manual/mpm.html.ja.euc-jp @@ -0,0 +1,130 @@ + + + +¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM) - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM)

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ +

¤³¤Îʸ½ñ¤Ç¤Ï¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë¤¬¤É¤Î¤è¤¦¤Ê¤â¤Î¤Ç¡¢ +Apache HTTP ¥µ¡¼¥Ð¤Ç¤É¤Î¤è¤¦¤Ë»ÈÍѤµ¤ì¤ë¤«¤Ë¤Ä¤¤¤Æ²òÀ⤷¤Æ¤¤¤Þ¤¹¡£

+
+ +
top
+
+

¤Ï¤¸¤á¤Ë

+ +

Apache HTTP ¥µ¡¼¥Ð¤Ï°Û¤Ê¤ëÉý¹­¤¤´Ä¶­¡¢Â¿¼ï¿Íͤʥץé¥Ã¥È¥Û¡¼¥à¤Ç + Æ°ºî¤¹¤ë¤è¤¦¤Ë¡¢¥Ñ¥ï¥Õ¥ë¤Ç½ÀÆðÀ­¤ËÉÙ¤ó¤ÀÀ߷פˤʤäƤ¤¤Þ¤¹¡£ + °Û¤Ê¤ë¥×¥é¥Ã¥È¥Û¡¼¥à¡¦°Û¤Ê¤ë´Ä¶­¤Ç¤Ï¤·¤Ð¤·¤Ð¡¢ + °Û¤Ê¤ëµ¡Ç½¤¬É¬Íפˤʤ俤ꡢ + Ʊ¤¸µ¡Ç½¤Ç¤â¸úΨ¤Î¤¿¤á¤Ë°Û¤Ê¤ë¼ÂÁõ¤¬É¬Íפˤʤ俤ꤷ¤Þ¤¹¡£ + Apache ¤Ç¤Ï¥â¥¸¥å¡¼¥ë²½¤µ¤ì¤¿À߷פˤè¤êÉý¹­¤¤´Ä¶­¤ËŬ±þ¤·¤Æ¤­¤Þ¤·¤¿¡£ + ¤³¤ÎÀ߷פΤª¤«¤²¤Ç¡¢´ÉÍý¼Ô¤Ï + ¥³¥ó¥Ñ¥¤¥ë»þ¤Þ¤¿¤Ï¼Â¹Ô»þ¤Ë¤É¤Î¥â¥¸¥å¡¼¥ë¤ò¥í¡¼¥É¤¹¤ë¤«Áª¤Ö¤³¤È¤Ë¤è¤Ã¤Æ¡¢ + ¤É¤Îµ¡Ç½¤ò¥µ¡¼¥Ð¤Ë¼è¤ê¹þ¤à¤«ÁªÂò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

Apache 2.0 ¤Ç¤Ï¡¢ + ¤³¤Î¥â¥¸¥å¡¼¥ë²½¤µ¤ì¤¿À߷פò¥µ¡¼¥Ð¤Î´ðËܵ¡Ç½¤Ë¤Þ¤Ç³ÈÄ¥¤·¤Þ¤·¤¿¡£ + ¥µ¡¼¥Ð¤Ë¤ÏÀºÁª¤µ¤ì¤¿¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM) + ¤¬ÉÕ¤¤¤Æ¤­¤Æ¡¢¤³¤ì¤é¤Ï¥Þ¥·¥ó¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥Ý¡¼¥È¤ò¥Ð¥¤¥ó¥É¤·¤¿¤ê¡¢ + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤¿¤ê¡¢¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤è¤¦»Ò¥×¥í¥»¥¹¤Ë³ä¤êÅö¤Æ¤¿¤ê¡¢ + ¤È¤¤¤Ã¤¿Ìò³ä¤ò»ý¤Á¤Þ¤¹¡£

+ +

¥â¥¸¥å¡¼¥ë²½¤µ¤ì¤¿À߷פò¥µ¡¼¥Ð¤Î¤³¤Î¥ì¥Ù¥ë¤Þ¤Ç³ÈÄ¥¤¹¤ë¤³¤È¤Ç + Æó¤Ä¤Î½ÅÍפÊÍøÅÀ¤¬À¸¤Þ¤ì¤Þ¤¹:

+ +
    +
  • Apache ¤ÏÉý¹­¤¤¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ò + ¤è¤êÈþ¤·¤¯¸úΨŪ¤Ë¥µ¥Ý¡¼¥È¤Ç¤­¤Þ¤¹¡£ + ÆÃ¤Ë Windows ÈǤΠApache ¤Ï¿ïʬ¸úΨŪ¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + ¤Ê¤¼¤Ê¤é mpm_winnt + ¤Ë¤è¤Ã¤Æ¡¢Apache 1.3 ¤ÇÍѤ¤¤é¤ì¤Æ¤¤¤¿ POSIX + ¥ì¥¤¥ä¤ÎÂå¤ï¤ê¤Ë¥Í¥¤¥Æ¥£¥Ö¤Î¥Í¥Ã¥È¥ï¡¼¥¯µ¡Ç½¤ò + ÍøÍѤǤ­¤ë¤«¤é¤Ç¤¹¡£ + ÆÃÊ̲½¤µ¤ì¤¿ MPM + ¤ò¼ÂÁõ¤·¤¿Â¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ç¤â¡¢ + ƱÍͤˤ³¤ÎÍøÅÀ¤ÏÀ¸¤Þ¤ì¤Þ¤¹¡£
    • + +
  • ¥µ¡¼¥Ð¤ÏÆÃÄê¤Î¥µ¥¤¥È¸þ¤±¤Ë¡¢¤è¤ê¾å¼ê¤Ë¥«¥¹¥¿¥Þ¥¤¥º¤Ç¤­¤Þ¤¹¡£ + Î㤨¤Ð¡¢Èó¾ï¤ËÂ礭¤Ê¥¹¥±¡¼¥é¥Ó¥ê¥Æ¥£¤òɬÍפȤ¹¤ë¥µ¥¤¥È¤Ç¤Ï¡¢ + worker ¤ä event ¤È¤¤¤Ã¤¿¥¹¥ì¥Ã¥É²½¤µ¤ì¤¿ + MPM ¤òÍøÍѤǤ­¤ë°ìÊý¤Ç¡¢°ÂÄêÀ­¤ä¸Å¤¤¥½¥Õ¥È¥¦¥§¥¢¤È¤Î¸ß´¹À­¤ò + ɬÍפȤ¹¤ë¥µ¥¤¥È¤Ç¤Ï prefork + ¤¬ÍøÍѤǤ­¤Þ¤¹¡£
    • +
+ +

¥æ¡¼¥¶¥ì¥Ù¥ë¤Ç¤Ï¡¢MPM ¤Ï¾¤Î Apache + ¥â¥¸¥å¡¼¥ë¤ÈƱÅù¤Ë¸«¤¨¤Þ¤¹¡£ + ¼ç¤Ê°ã¤¤¤Ï¡¢¤¤¤Ä¤Ç¤âÍ£°ì¤Î MPM + ¤¬¥í¡¼¥É¤µ¤ì¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤È¤¤¤¦ÅÀ¤Ç¤¹¡£ + ÍøÍѲÄǽ¤Ê MPM ¤Ï + module ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ë¤¢¤ê¤Þ¤¹¡£

+ +
top
+
+

MPM ¤òÁª¤Ö

+ +

MPM ¤ÏÀßÄêÃæ¤ËÁªÂò¤·¤Æ¡¢¥µ¡¼¥ÐÆâÉô¤Ë¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤Ê¤±¤ì¤Ð + ¤Ê¤ê¤Þ¤»¤ó¡£ + ¥³¥ó¥Ñ¥¤¥é¤Ï¡¢¥¹¥ì¥Ã¥É¤¬»ÈÍѤµ¤ì¤Æ¤¤¤ë¾ì¹ç¤ËÍÍ¡¹¤Êµ¡Ç½¤òºÇŬ²½¤Ç¤­¤Þ¤¹¤¬¡¢ + ¤½¤Î¤¿¤á¤Ë¤Ï¤½¤â¤½¤â¥¹¥ì¥Ã¥É¤¬»È¤ï¤ì¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È¤òÃΤëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

˾¤ß¤Î MPM ¤ò¼ÂºÝ¤ËÁª¤Ö¤¿¤á¤Ë¤Ï¡¢configure ¥¹¥¯¥ê¥×¥È¤Ç + --with-mpm=NAME °ú¿ô¤òÍѤ¤¤Æ¤¯¤À¤µ¤¤¡£ + NAME ¤Ï˾¤ß¤Î MPM ¤Î̾Á°¤Ç¤¹¡£

+ +

¥µ¡¼¥Ð¥³¥ó¥Ñ¥¤¥ë¸å¤Ï¡¢¤É¤Î MPM ¤¬ÁªÂò¤µ¤ì¤¿¤«¤ò + ./httpd -l ¤Ç³Î¤«¤á¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤Î¥³¥Þ¥ó¥É¤Ï¡¢MPM + ¤ò´Þ¤á¡¢¥µ¡¼¥Ð¤Ë¥³¥ó¥Ñ¥¤¥ë¤ÇÁȤ߹þ¤Þ¤ì¤¿¥â¥¸¥å¡¼¥ëÁ´¤Æ¤ò + Îóµó¤·¤Þ¤¹¡£

+
top
+
+

MPM ¥Ç¥Õ¥©¥ë¥ÈÃÍ

+ +

¼¡É½¤ËÍÍ¡¹¤Ê OS ¸þ¤±¤Î¥Ç¥Õ¥©¥ë¥È¤Î MPM °ìÍ÷¤ò·ÇºÜ¤·¤Æ¤¤¤Þ¤¹¡£ +¥³¥ó¥Ñ¥¤¥ë»þ¤Ë°Õ¿ÞŪ¤Ë¾¤òÁªÂò¤·¤Ê¤±¤ì¤Ð¡¢¼«Æ°Åª¤Ë¤³¤ì¤é¤Î MPM +¤¬ÁªÂò¤µ¤ì¤Þ¤¹¡£

+ + + + + + + + +
BeOSbeos
Netwarempm_netware
OS/2mpmt_os2
Unixprefork
Windowsmpm_winnt
+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/mpm.html.ko.euc-kr b/docs/manual/mpm.html.ko.euc-kr new file mode 100644 index 00000000..96bffede --- /dev/null +++ b/docs/manual/mpm.html.ko.euc-kr @@ -0,0 +1,122 @@ + + + +´ÙÁßó¸® ¸ðµâ (MPM) - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

´ÙÁßó¸® ¸ðµâ (MPM)

+
+

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

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

ÀÌ ¹®¼­´Â ´ÙÁßó¸® ¸ðµâ (Multi-Processing Module)ÀÌ ¹«¾ùÀ̸ç, +¾ÆÆÄÄ¡ À¥¼­¹ö°¡ À̸¦ ¾î¶»°Ô »ç¿ëÇÏ´ÂÁö ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

¼Ò°³

+ +

¾ÆÆÄÄ¡ À¥¼­¹ö´Â ´Ù¾çÇÑ È¯°æÀÇ ´Ù¾çÇÑ Ç÷¡Æû¿¡¼­ µ¿ÀÛÇÒ + ¼ö ÀÖµµ·Ï °­·ÂÇÏ°í À¯¿¬ÇÏ°Ô ¼³°èµÇ¾ú´Ù. ´Ù¸¥ Ç÷¡Æû°ú ´Ù¸¥ + ȯ°æÀº º¸Åë ´Ù¸¥ ±â´ÉÀ» ¿ä±¸Çϸç, ¾î¶² ±â´ÉÀ» °¡Àå È¿À²ÀûÀ¸·Î + ±¸ÇöÇÏ´Â ¹æ¹ýÀÌ ´Ù¸¦ ¼ö ÀÖ´Ù. ¾ÆÆÄÄ¡´Â ¸ðµâÈ­µÈ ¼³°è·Î ÀÌ·± + ´Ù¾çÇÑ È¯°æ¿¡ Ç×»ó ÀûÀÀÇØ¿Ô´Ù. ±×·¡¼­ À¥¸¶½ºÅÍ´Â ÄÄÆÄÀϽà + ȤÀº ½ÇÇà½Ã ¾î¶² ¸ðµâÀ» ÀоîµéÀÏÁö ¼±ÅÃÇÏ¿© ¼­¹ö¿¡ Æ÷ÇÔÇÒ + ±â´ÉÀ» °áÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +

Apache 2.0Àº ÀÌ·± ¸ðµâÈ­µÈ ¼³°è¸¦ À¥¼­¹öÀÇ °¡Àå ±âº»ÀûÀÎ + ºÎºÐ¿¡±îÁö È®ÀåÇß´Ù. ¼­¹ö´Â ½Ã½ºÅÛÀÇ ³×Æ®¿÷ Æ÷Æ®¿¡ ¿¬°áÇÏ°í, + ¿äûÀ» ¹Þ¾ÆµéÀ̸ç, ¹Þ¾ÆµéÀÎ ¿äûÀ» ó¸®ÇϱâÀ§ÇØ Àڽĵ鿡°Ô + ºÐ¹èÇÏ´Â ´ÙÁßó¸® ¸ðµâ (Multi-Processing Modules, MPMs)À» + ¼±ÅÃÇÒ ¼ö ÀÖ´Ù.

+ +

¼­¹ö¸¦ ÀÌ Á¤µµ·Î ¸ðµâÈ­ÇÏ¸é µÎ°¡Áö Áß¿äÇÑ ÀåÁ¡ÀÌ + ÀÖ´Ù:

+ +
    +
  • mpm_winnt°¡ Apache 1.3¿¡¼­ »ç¿ëÇÑ + POSIXÃþ ´ë½Å ÀÚü ³×Æ®¿÷ ±â´ÉÀ» »ç¿ëÇÒ ¼ö ÀÖ´Â µî, + ¾ÆÆÄÄ¡´Â ¿©·¯ ´Ù¾çÇÑ ¿î¿µÃ¼Á¦¸¦ ´õ ±ò²ûÇÏ°í È¿À²ÀûÀ¸·Î + Áö¿øÇÒ ¼ö ÀÖ´Ù. ÀÌ ÀåÁ¡Àº ƯȭµÈ MPMÀ» ±¸ÇöÇÑ ´Ù¸¥ + ¿î¿µÃ¼Á¦¿¡µµ Àû¿ëµÈ´Ù.
    • + +
  • ¼­¹ö´Â ƯÁ¤ »çÀÌÆ®ÀÇ ¿ä±¸Á¶°Ç¿¡ ´õ ƯȭµÉ ¼ö ÀÖ´Ù. + ¿¹¸¦ µé¾î ³ôÀº È®Àå°¡´É¼º(scalability)ÀÌ ÇÊ¿äÇÑ »çÀÌÆ®´Â + worker¿Í °°Àº ¾²·¹µå MPMÀ» »ç¿ëÇÏ°í, + ¾ÈÁ¤¼º°ú ¿À·¡µÈ ¼ÒÇÁÆ®¿þ¾î¿ÍÀÇ È£È¯¼ºÀÌ ÇÊ¿äÇÑ »çÀÌÆ®´Â + preforking MPMÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. + Ãß°¡·Î ´Ù¸¥ »ç¿ëÀÚ¾ÆÀ̵ð·Î ¿©·¯ È£½ºÆ®¸¦ ¼­ºñ½ºÇÏ´Â + °Í(perchild)°ú °°Àº Ưº°ÇÑ ±â´Éµµ + Á¦°øµÈ´Ù.
    • +
+ +

»ç¿ëÀÚ°¡ º¸±â¿¡ MPMÀº ´Ù¸¥ ¾ÆÆÄÄ¡ ¸ðµâ°ú °ÅÀÇ ºñ½ÁÇØ + º¸ÀδÙ. ÁÖµÈ Â÷ÀÌ´Â ¼­¹ö´Â Çѹø¿¡ ¿ÀÁ÷ ÇÑ MPM¸¸À» »ç¿ëÇØ¾ß + ÇÑ´Ù´Â Á¡ÀÌ´Ù. »ç¿ë°¡´ÉÇÑ MPM ¸ñ·ÏÀº ¸ðµâ + ¸ñ·Ï ÆäÀÌÁö¿¡ ÀÖ´Ù.

+ +
top
+
+

MPM ¼±ÅÃÇϱâ

+ +

MPMs´Â ±¸¼ºÁß¿¡ ¼±ÅÃÇÏ¿© ¼­¹ö¿¡ ÄÄÆÄÀÏµÇ¾ß ÇÑ´Ù. + ¾²·¹µå¸¦ »ç¿ëÇÏ´Â °ÍÀ» ÄÄÆÄÀÏ·¯°¡ ¾Ë¸é ¸¹Àº ÇÔ¼ö¸¦ + ÃÖÀûÈ­ÇÒ ¼ö ÀÖ´Ù. À¯´Ð½º¿¡¼­ ¸î¸î MPMÀº ¾²·¹µå¸¦ ¾²°í + ³ª¸ÓÁö´Â ¾Æ´Ï¹Ç·Î, MPMÀÌ ±¸¼ºÁß¿¡ ¼±ÅÃµÇ¾î ¾ÆÆÄÄ¡¿¡ + ÄÄÆÄÀϵɶ§ ¾ÆÆÄÄ¡´Â ´õ ºü¸¥ ¼Óµµ¸¦ ³½´Ù.

+ +

¿øÇÏ´Â MPMÀ» ¼±ÅÃÇÏ·Á¸é ./configure ½ºÅ©¸³Æ®¿¡ + with-mpm= NAME ¾Æ±Ô¸ÕÆ®¸¦ »ç¿ëÇ϶ó. NAMEÀº + ¿øÇÏ´Â MPM À̸§ÀÌ´Ù.

+ +

¼­¹ö¸¦ ÄÄÆÄÀÏÇÑÈÄ ./httpd -l ¸í·É¾î·Î ¼±ÅÃÇÑ + MPMÀ» ¾Ë ¼ö ÀÖ´Ù. ÀÌ ¸í·É¾î´Â MPMÀ» Æ÷ÇÔÇÏ¿© ¼­¹ö¿¡ ÄÄÆÄÀÏµÈ + ¸ðµç ¸ðµâÀ» ¾Ë·ÁÁØ´Ù.

+
top
+
+

MPM ±âº»°ª

+ +

´ÙÀ½ Ç¥´Â ¿©·¯ ¿î¿µÃ¼Á¦ÀÇ ±âº» MPMÀ» º¸¿©ÁØ´Ù. ÄÄÆÄÀϽà +´Ù¸£°Ô ¼±ÅÃÇÏÁö ¾ÊÀ¸¸é ÀÌ MPMÀÌ ¼±ÅõȴÙ.

+ + + + + + + + +
BeOSbeos
Netwarempm_netware
OS/2mpmt_os2
À¯´Ð½ºprefork
À©µµ¿ìÁîmpm_winnt
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_0.html b/docs/manual/new_features_2_0.html new file mode 100644 index 00000000..798ba8a5 --- /dev/null +++ b/docs/manual/new_features_2_0.html @@ -0,0 +1,27 @@ +URI: new_features_2_0.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: new_features_2_0.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: new_features_2_0.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: new_features_2_0.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: new_features_2_0.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: new_features_2_0.html.pt-br +Content-Language: pt-br +Content-type: text/html; charset=ISO-8859-1 + +URI: new_features_2_0.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R diff --git a/docs/manual/new_features_2_0.html.de b/docs/manual/new_features_2_0.html.de new file mode 100644 index 00000000..dadd4617 --- /dev/null +++ b/docs/manual/new_features_2_0.html.de @@ -0,0 +1,263 @@ + + + +Übersicht der neuen Funktionen in Apache 2.0 - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Übersicht der neuen Funktionen in Apache 2.0

+
+

Verfügbare Sprachen:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ +

Dieses Dokument beschreibt einige der wichtigsten Änderungen + des Apache HTTP Servers 2.0 gegenüber der Version 1.3.

+
+ +
top
+
+

Core-Erweiterungen

+ + +
+
Unix-Threading
+ +
Auf Unix-Systemen mit Unterstützung für POSIX-Threads, + kann Apache jetzt in einem Multi-Process, Multi-Threaded Hybrid-Mode + gestartet werden. Dies verbessert die Skalierfähigkeit für + viele, jedoch nicht unbedingt alle Konfigurationen.
+ +
Neues Build-System
+ +
Das Build-System wurde komplett auf der Basis von + autoconf und libtool neu geschrieben. Dadurch + wird das Apache-Konfigurationssystem dem vieler anderer Packages + ähnlicher.
+ +
Multi-Protokoll-Unterstützung
+ +
Apache stellt jetzt die notwendigen Grundfunktionalitäten + bereit, um mehrere Protokolle unterstützen und verarbeiten zu + können. mod_echo wurde hierfür als + Beispiel geschrieben.
+ +
Bessere Unterstützung von + Nicht-Unix-Plattformen
+ +
Apache 2.0 ist schneller und stabiler auf Nicht-Unix-Plattformen + wie BeOS, OS/2 und Windows. Mit der Einführung von + Plattform-spezifischen Multi-Processing Modulen + (MPMs) und der Apache Portable Runtime (APR), sind diese Plattformen + jetzt in ihrem nativen API implementiert, wodurch die Verwendung der + häufig fehlerbehafteten und schlecht funktionierenden + POSIX-Emulation-Layer vermieden wird.
+ +
Neues Apache API
+ +
Das API für Module hat sich in 2.0 stark verändert. + Die meisten der Sortierungs-/Prioritätsprobleme von Modulen bei + 1.3 sollten nun verschwunden sein. In 2.0 wird hiervon vieles + automatisch durchgeführt. Die Modulsortierung wird jetzt + über einen pre-hook vorgenommen, um mehr Flexibilität + zu bieten. Außerdem wurden neue API-Calls hinzugefügt, + die zusätzliche Modulfähigkeiten zur Verfügung stellen, + ohne den Apache-Kern anpassen zu müssen.
+ +
IPv6-Unterstützung
+ +
Auf Systemen, bei denen die zugrundeliegende Apache Portable + Runtime-Bibliothek IPv6 unterstützt, bekommt Apache + standarmäßig IPv6 Listening Sockets. Zusätzlich + unterstützen die Konfigurationsanweisungen Listen, NameVirtualHost und VirtualHost numerische IPv6-Adressangaben + (z.B., "Listen [2001:db8::1]:8080").
+ +
Filterung
+ +
Apache-Module können jetzt als Filter entwickelt und zur + Filterung des rein- und rausgehenden Datenstroms des Servers + eingesetzt werden. Hierdurch kann beispielsweise die Ausgabe von + CGI-Skripten durch den INCLUDES-Filter von + mod_include bearbeitet werden und so Server-Side + Include-Anweisungen ausgeführt werden. Das Modul + mod_ext_filter erlaubt externen Programmen + als Filter zu agieren, in der gleichen Weise wie CGI-Programme als + Eingabe dienen können.
+ +
Mehrsprachige Fehlermeldungen
+ +
Fehlermeldungen die an den Browser rausgehen, stehen jetzt als + SSI-Dokumente in verschiedenen Sprachen zur Verfügung. Sie + können bei Bedarf durch den Administrator angepasst werden, + um ein einheitliches Design zu erreichen.
+ +
Vereinfachte Konfiguration
+ +
Viele der verwirrenden Konfigurationsanweisungen wurden vereinfacht. + Die oft für Verwirrung sorgenden Port- und + BindAddress-Anweisungen wurden entfernt. + Ausschließlich die Listen-Anweisung wird nun zum + Setzen von IP-Addressen und Portnummern benutzt. + Der Servername und die Portnummer, die für Weiterleitungen und + zur Erkennung virtueller Server verwendet werden, werden über + die ServerName-Anweisung + konfiguriert.
+ +
Native Windows NT Unicode-Unterstützung
+ +
Apache 2.0 auf Windows NT benutzt jetzt utf-8 für alle + Dateinamen-Kodierungen. Diese werden direkt auf das zugrundeliegende + Unicode-Dateisystem abgebildet, wodurch Mehrsprach-Unterstützung + für alle Windows NT-basierten Installationen, inklusive Windows + 2000 und Windows XP, zur Verfügung gestellt wird. + Diese Unterstützung ist nicht auf Windows 95, 98 oder ME + verfügbar. Hier wird weiterhin die jeweils lokale Codepage des + Rechners für den Zugriff auf das Dateisystem verwendet.
+ +
Bibliothek für reguläre Ausdrücke aktualisiert
+ +
Apache 2.0 enthält die "Perl Compatible + Regular Expression Library" (PCRE). + Bei der Auswertung aller regulären Ausdrücke wird nun + die leistungsfähigere Syntax von Perl 5 verwendet.
+ +
+
top
+
+

Modul-Erweiterungen

+ + +
+
mod_ssl
+ +
Neues Modul in Apache 2.0. Dieses Modul ist ein Interface + zu den von OpenSSL bereitgestellten SSL/TLS + Verschlüsselungs-Protokollen.
+ +
mod_dav
+ +
Neues Modul in Apache 2.0. Dieses Modul implementiert die HTTP + Distributed Authoring and Versioning (DAV) Spezifikation zur + Erzeugung und Pflege von Web-Inhalten.
+ +
mod_deflate
+ +
Neues Modul in Apache 2.0. Dieses Modul erlaubt es Browsern, die + dies unterstützen, eine Komprimierung des Inhaltes vor der + Auslieferung anzufordern, um so Netzwerk-Bandbreite zu sparen.
+ +
mod_auth_ldap
+ +
Neues Modul in Apache 2.0.41. Diese Modul ermöglicht + die Verwendung einer LDAP-Datenbank zur Speicherung von + Berechtigungsdaten für die HTTP-Basic-Authentication. + Ein Begleitmodul, mod_ldap, stellt einen + Verbindungs-Pool und die Pufferung von Abfrageergebnissen zur + Verfügung. +
+ +
mod_auth_digest
+ +
Zusätzliche Unterstützung für + prozessübergreifendes Session-Caching mittels Shared-Memory. +
+ +
mod_charset_lite
+ +
Neues Modul in Apache 2.0. + Dieses experimentelle Modul erlaubt Zeichensatz-Übersetzungen oder + -Umschlüsselung.
+ +
mod_file_cache
+ +
Neues Modul in Apache 2.0. Dieses Modul beinhaltet die + Funktionalität von mod_mmap_static aus Apache 1.3, + plus einige weitere Caching-Funktionen.
+ +
mod_headers
+ +
Dieses Modul ist in Apache 2.0 deutlich flexibler geworden. Es + kann jetzt die von mod_proxy genutzten Request-Header + manipulieren und es ist möglich Response-Header auf Basis von + definierten Bedingungen zu verändern.
+ +
mod_proxy
+ +
Das Proxy Modul wurde komplett neu geschrieben um die + Möglichkeiten der neuen Filter-Funktionalität + auszuschöpfen und um einen zuverlässigen Proxy zu haben, der + den HTTP/1.1-Spezifikationen entspricht. Neue <Proxy> + -Konfigurationsabschnitte bieten eine besser lesbare (und intern + schnellere) Kontrolle der vermittelten Seiten. + Die überladenen <Directory + "proxy:...">-Konfigurationen werden nicht + mehr unterstützt. Das Modul ist nun in mehrere Module + unterteilt, die jeweils ein bestimmtes Übertragungsprotokoll + unterstützen, wie proxy_connect, + proxy_ftp und proxy_http.
+ +
mod_negotiation
+ +
Die neue Konfigurationsanweisung ForceLanguagePriority + kann benutzt werden, um sicherzustellen, dass ein Client auf jeden + Fall ein einzelnes Dokument, anstatt einer NOT ACCEPTABLE- oder + MULTIPLE CHOICES-Antwort, bekommt. Zusätzlich wurden die + Negotiation- und Multiview-Algorithmen angepasst um einheitlichere + Ergebnisse zu liefern. Außerdem wird ein neues + Type-Map-Format bereitgestellt, das Dokumenteninhalte direkt + enthalten kann.
+ +
mod_autoindex
+ +
Automatisch erzeugte Verzeichnisindizes können zur besseren + Übersichtlichkeit durch HTML-Tabellen dargestellt werden. + Genauere Sortierungen, wie Sortierung nach Versionsnummer und + Wildcard-Filterung des Verzeichnisindizes werden unterstützt.
+ +
mod_include
+ +
Neue Anweisungen erlauben es, die Standard Start- und Endtags von + SSI-Elementen zu ändern. Zudem können die Default-Formate + für Fehlermeldungen und Zeitangaben nun ebenfalls in der + Serverkonfiguration vorgenommen werden. Auf die Ergebnisse der + Auswertung und Gruppierung von regulären Ausdrücken (jetzt + auf Basis der Perl-Syntax für reguläre Ausdrücke) kann + über die mod_include Variablen $0 + bis $9 zugegriffen werden.
+ +
mod_auth_dbm
+ +
DBM-ähnliche Datenbanken werden jetzt durch die + Konfigurationsaweisung AuthDBMType unterstützt.
+
+
+
+

Verfügbare Sprachen:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_0.html.en b/docs/manual/new_features_2_0.html.en new file mode 100644 index 00000000..42e9ed4c --- /dev/null +++ b/docs/manual/new_features_2_0.html.en @@ -0,0 +1,243 @@ + + + +Overview of new features in Apache 2.0 - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Overview of new features in Apache 2.0

+
+

Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ +

This document describes some of the major changes between the + 1.3 and 2.0 versions of the Apache HTTP Server.

+
+ +
top
+
+

Core Enhancements

+ + +
+
Unix Threading
+ +
On Unix systems with POSIX threads support, Apache can + now run in a hybrid multiprocess, multithreaded mode. This + improves scalability for many, but not all configurations.
+ +
New Build System
+ +
The build system has been rewritten from scratch to be + based on autoconf and libtool. + This makes Apache's configuration system more similar to + that of other packages.
+ +
Multiprotocol Support
+ +
Apache now has some of the infrastructure in place to + support serving multiple protocols. mod_echo has + been written as an example.
+ +
Better support for non-Unix + platforms
+ +
Apache 2.0 is faster and more stable on non-Unix + platforms such as BeOS, OS/2, and Windows. With the + introduction of platform-specific multi-processing modules (MPMs) and the + Apache Portable Runtime (APR), these platforms are now + implemented in their native API, avoiding the often buggy and + poorly performing POSIX-emulation layers.
+ +
New Apache API
+ +
The API for modules has changed significantly for 2.0. + Many of the module-ordering/-priority problems from 1.3 should + be gone. 2.0 does much of this automatically, and module ordering + is now done per-hook to allow more flexibility. Also, new calls + have been added that provide additional module capabilities + without patching the core Apache server.
+ +
IPv6 Support
+ +
On systems where IPv6 is supported by the underlying + Apache Portable Runtime library, Apache gets IPv6 listening + sockets by default. Additionally, the Listen, NameVirtualHost, and VirtualHost directives support + IPv6 numeric address strings (e.g., "Listen + [2001:db8::1]:8080").
+ +
Filtering
+ +
Apache modules may now be written as filters which act on + the stream of content as it is delivered to or from the + server. This allows, for example, the output of CGI scripts to + be parsed for Server Side Include directives using the + INCLUDES filter in mod_include. The + module mod_ext_filter allows external programs to + act as filters in much the same way that CGI programs can act as + handlers.
+ +
Multilanguage Error Responses
+ +
Error response messages to the browser are now provided in + several languages, using SSI documents. They may be customized + by the administrator to achieve a consistent look and feel.
+ +
Simplified configuration
+ +
Many confusing directives have been simplified. The often + confusing Port and BindAddress directives + are gone; only the Listen + directive is used for IP address binding; the ServerName directive specifies the + server name and port number only for redirection and vhost + recognition.
+ +
Native Windows NT Unicode Support
+ +
Apache 2.0 on Windows NT now uses utf-8 for all filename + encodings. These directly translate to the underlying Unicode + file system, providing multilanguage support for all Windows + NT-based installations, including Windows 2000 and Windows XP. + This support does not extend to Windows 95, 98 or ME, which + continue to use the machine's local codepage for filesystem + access.
+ +
Regular Expression Library Updated
+ +
Apache 2.0 includes the Perl + Compatible Regular Expression Library (PCRE). All regular + expression evaluation now uses the more powerful Perl 5 + syntax.
+ +
+
top
+
+

Module Enhancements

+ + +
+
mod_ssl
+ +
New module in Apache 2.0. This module is an interface + to the SSL/TLS encryption protocols provided by + OpenSSL.
+ +
mod_dav
+ +
New module in Apache 2.0. This module implements the HTTP + Distributed Authoring and Versioning (DAV) specification for + posting and maintaining web content.
+ +
mod_deflate
+ +
New module in Apache 2.0. This module allows supporting + browsers to request that content be compressed before delivery, + saving network bandwidth.
+ +
mod_auth_ldap
+ +
New module in Apache 2.0.41. This module allows an LDAP + database to be used to store credentials for HTTP Basic + Authentication. A companion module, mod_ldap + provides connection pooling and results caching.
+ +
mod_auth_digest
+ +
Includes additional support for session caching across + processes using shared memory.
+ +
mod_charset_lite
+ +
New module in Apache 2.0. This experimental module allows + for character set translation or recoding.
+ +
mod_file_cache
+ +
New module in Apache 2.0. This module includes the + functionality of mod_mmap_static in Apache 1.3, + plus adds further caching abilities.
+ +
mod_headers
+ +
This module is much more flexible in Apache 2.0. It can now + modify request headers used by mod_proxy, and + it can conditionally set response headers.
+ +
mod_proxy
+ +
The proxy module has been completely rewritten to take + advantage of the new filter infrastructure and to implement a + more reliable, HTTP/1.1 compliant proxy. In addition, new + <Proxy> + configuration sections provide more readable (and internally + faster) control of proxied sites; overloaded <Directory + "proxy:..."> configuration are not supported. The module + is now divided into specific protocol support modules including + proxy_connect, proxy_ftp and + proxy_http.
+ +
mod_negotiation
+ +
A new ForceLanguagePriority directive can be used to assure that + the client receives a single document in all cases, rather than + NOT ACCEPTABLE or MULTIPLE CHOICES responses. In addition, the + negotiation and MultiViews algorithms have been cleaned up to + provide more consistent results and a new form of type map that + can include document content is provided.
+ +
mod_autoindex
+ +
Autoindex'ed directory listings can now be configured to + use HTML tables for cleaner formatting, and allow finer-grained + control of sorting, including version-sorting, and wildcard + filtering of the directory listing.
+ +
mod_include
+ +
New directives allow the default start and end tags for SSI elements + to be changed and allow for error and time format configuration + to take place in the main configuration file rather than in the + SSI document. Results from regular expression parsing and grouping + (now based on Perl's regular expression syntax) can be retrieved + using mod_include's variables $0 + .. $9.
+ +
mod_auth_dbm
+ +
Now supports multiple types of DBM-like databases using the + AuthDBMType + directive.
+ +
+
+
+

Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_0.html.fr b/docs/manual/new_features_2_0.html.fr new file mode 100644 index 00000000..35e88069 --- /dev/null +++ b/docs/manual/new_features_2_0.html.fr @@ -0,0 +1,251 @@ + + + +Vue d'ensemble des nouvelles fonctionnalités d'Apache 2.0 - Serveur Apache HTTP + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur Apache HTTP Version 2.2

+
+
<-
+
+Apache > Serveur HTTP > Documentation > Version 2.2

Vue d'ensemble des nouvelles fonctionnalités d'Apache 2.0

+
+

Langues Disponibles:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ +

Ce document décrit les changements majeurs apportés entre les + versions 1.3 et 2.0 du serveur HTTP Apache.

+
+ +
top
+
+

Améliorations du Système de Base

+ + +
+
Threading Unix
+ +
Sur les systèmes Unix qui supportent les threads POSIX, Apache + peut à présent tourner en mode hybride multi-processus et + multi-threadé, ce qui augmente l'extensibilité et la performance + du serveur pour la plupart des configurations.
+ +
Nouveau Système de Compilation
+ +
Le processus de compilation a été refait de A à Z; + il utilise à présent autoconf et libtool, + ce qui rend la compilation d'Apache plus familière aux utilisateurs + d'autre logiciels de mème type.
+ +
Support Multiprotocole
+ +
Apache dispose désormais de l'infrastructure nécessaire pour supporter + d'autres protocoles. Le module mod_echo illustre ces + possibilités.
+ +
Support amélioré des Plate-formes non-Unix
+ +
Apache 2.0 se montre plus rapide et plus stable sur les plate-formes + non Unix, telles BeOS, OS/2, NetWare et Windows. L'apparition des + Modules Multi-Processus (MPMs), ainsi que de + la bibliothèque "Apache Portable Runtime" (APR) permet a Apache de + tirer parti des API natives de ces plate-formes, sans s'appuyer sur leurs + couches POSIX souvent boguées et peu optimisées.
+ +
Nouvelle API Apache
+ +
L'Interface de Programmation (API) des modules a beaucoup changé + avec le passage à la version 2.0. + Les problèmes d'ordre et de priorité des modules, rencontrés + avec la version 1.3, devraient maintenant être résolus. Apache 2.0 + gère ces problèmes de façon automatique. L'ordre des modules + est géré au moyen de "crochets" (hooks), ce qui rend la gestion + flexible. De nouveaux appels ont été également créés + afin de permettre l'implémentation d'autres fonctions dans les modules, + sans devoir corriger le noyau du serveur Apache.
+ +
Support IPv6
+ +
Sur les systèmes où la bibliothèque Apache Portable Runtime + supporte IPv6, Apache peut par défaut écouter sur des interfaces + de connexions IPv6. Les directives Listen, + NameVirtualHost et + VirtualHost supportent également + les adresses IPv6 (comme par exemple, dans "Listen[2001:db8::1]:8080").
+ +
Filtering
+ +
Il est maintenant possible d'écrire des modules Apache pour filtrer + les flux de données entrant ou sortant du serveur. A titre d'exemple, + il est possible de filtrer des directives Server Side Include de la sortie + standard d'un script CGI, au moyen du filtre INCLUDES fourni + par le module mod_include. Le module + mod_ext_filter permet quant à lui l'utilisation comme + filtres de programmes externes à Apache, de la même manière + qu'on peut utiliser des programmes CGI comme Handlers.
+ +
Réponses d'Erreurs Multilangues
+ +
Les messages d'erreur envoyés au navigateur existent à présent en + plusieurs langues avec des documents SSI. Ces messages peuvent être + personnalisés par l'administrateur afin de s'intégrer avec le site web.
+ +
Simplification de la Configuration
+ +
Beaucoup de directives, auparavant peu claires, ont été simplifiées. + Les directives Port et BindAddress, souvent + sources d'incompréhension, ont disparus. Désormais seule la directive + Listen sert de liaison pour les + adresses IP; la directive ServerName ne + précise le nom du serveur et son port que pour les redirections et la + gestion des hôtes virtuels.
+ +
Support natif de l'Unicode sous Windows NT
+ +
Apache 2.0 sur Windows NT utilise à présent l'utf-8 pour tous les + noms de fichiers. Ces noms de fichiers sont directement traduits vers + l'encodage Unicode du système de fichiers, ce qui permet le support + multilangue pour toutes les installations sur la famille NT de Windows, y + compris Windows 2000 et Windows XP.Ce support n'est pas fonctionnel + pour Windows 95, 98 ni ME, qui utilisent les pages de code locales pour + les accès au système de fichiers, comme auparavant.
+ +
Mise à jour de la Bibliothèque d'Expressions Rationnelles
+ +
Apache 2.0 contient la bibliothèque + d'expressions rationnelles compatible Perl (Perl Compatible Regular + Expression Library - PCRE). Toutes les expressions rationnelles sont dont + gérées avec la syntaxe de Perl 5, plus puissante.
+ +
+
top
+
+

Amélioration des Modules

+ + +
+
mod_ssl
+ +
Apparu dans Apache 2.0, ce module est une interface aux protocoles de + criffrement SSL/TLS fournis par OpenSSL.
+ +
mod_dav
+ +
Apparu dans Apache 2.0, ce module implémente les spécifications HTTP de + gestion distribuée de versions et de rédaction (Distributed Authoring and + Versioning - DAV), destinées à la mise en ligne et à la maintenance des + contenus Web.
+ +
mod_deflate
+ +
Module apparu dans Apachge 2.0, mod_deflate permet aux navigateurs qui + le supportent de demander la compression des contenus envoyés par le serveur. + Cela à l'avantage de réduite l'occupation de la bande passante.
+ +
mod_auth_ldap
+ +
Apparu dans Apache 2.0.41, ce module permet aux administrateurs + d'utiliser un arbre LDAP pour gérer la base d'utilisateurs pour les + Authentifications Basiques HTTP. Un module voisin, + mod_ldap, permet de globaliser les connexions à l'arbre LDAP + et de garder en mémoire cache ces accès.
+ +
mod_auth_digest
+ +
Améliore les fonctions de cache sur une session entre les différents + processus, en utilisant de la mémoire partagée.
+ +
mod_charset_lite
+ +
Apparu dans Apache 2.0, ce module expérimental permet la conversion + et l'enregistrement entre jeux de caractères.
+ +
mod_file_cache
+ +
Apparu dans Apache 2.0, ce module implémente les fonctionnalités du + module mod_mmap_static présent dans Apache 1.3, et offre des + fonctions plus avancées pour la gestion de la cache.
+ +
mod_headers
+ +
Ce module gagne beaucoup de flexibilité avec Apache 2.0 : on peut + désormais l'utiliser pour modifier les en-têtes des requêtes + utilisés par mod_proxy, et peut aussi positionner les + en-têtes des réponses de manière conditionnelle.
+ +
mod_proxy
+ +
Le module proxy a été réécrit de A à Z. Il tire + maintenant avantage de la nouvelle infrastructure de filtrage, et implémente + un mandataire plus fiable, et conforme aux normes HTTP/1.1. De nouvelles + sections de configuration ajoutées à + <Proxy> + donnent un contrôle plus lisible et un traitement plus rapide des requêtes + proxifiés; les configurations surcharchées <Directory + "proxy:..."> ne sont pas supportées. Le module a aussi été + fragmenté en plusieurs modules qui gérent chacun leur protocole : + proxy_connect, proxy_ftp et + proxy_http.
+ +
mod_negotiation
+ +
Une nouvelles directive, ForceLanguagePriority a été ajoutée, + elle permet de garantir que le client reçoit un seul document dans tous les + cas, au lieu de réponses NOT ACCEPTABLE ou MULTIPLE CHOICES. Les + algorithmes gérant la négociation et les vues multiples (MultiViews) ont + été nettoyés et donnent des réponses plus logiques. Un nouveau format de + carte de types (map type) qui peut aussi gérer le contenu de documents a + aussi été ajouté.
+ +
mod_autoindex
+ +
Les listes auto-générés par Autoindex sont à présent + configurables, et peuvent utiliser des tables HTML pour une mise en forme plus propre. + L'ordre d'affichage des fichiers est également finement paramètrable, + comme pour le tri par version, et le filtrage par caractères jokers du + listage du répertoire.
+ +
mod_include
+ +
De nouvelles directives permettent de modifier la valeur par défaut + des drapeaux start et end des éléments SSI. Ces directives + permettent à la configuration d'affichage de dates et heures d'être + effectuée dans le fichier de configuration principal, plutôt que dans le + document SSI. Les réponses données par des recherches par expressions + rationnelles (qui gèrent à présent les regex Perl) sont + recupérés au moyen des variables $0 à $9.
+ +
mod_auth_dbm
+ +
Plusieurs bases de données DBM sont supportées, et sélectionnables + au moyen de la directive AuthDBMType.
+
+
+
+

Langues Disponibles:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_0.html.ja.euc-jp b/docs/manual/new_features_2_0.html.ja.euc-jp new file mode 100644 index 00000000..aae647dd --- /dev/null +++ b/docs/manual/new_features_2_0.html.ja.euc-jp @@ -0,0 +1,253 @@ + + + +Apache 2.0 ¤Î¿·µ¡Ç½¤Î³µÍ× - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

Apache 2.0 ¤Î¿·µ¡Ç½¤Î³µÍ×

+
+

Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ +

¤³¤Îʸ½ñ¤Ç¤Ï¡¢Apache HTTP ¥µ¡¼¥Ð¥Ð¡¼¥¸¥ç¥ó 1.3 ¤È 2.0 + ¤Î¼ç¤Ê°ã¤¤¤Ë¤Ä¤¤¤Æµ­½Ò¤·¤Æ¤¤¤Þ¤¹¡£

+
+ +
top
+
+

¥³¥¢µ¡Ç½¤Î³ÈÄ¥

+ + +
+
Unix ¤Î¥¹¥ì¥Ã¥É
+ +
POSIX ¥¹¥ì¥Ã¥É¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë Unix ¥·¥¹¥Æ¥à¾å¤Ç¤Ï¡¢ + Apache ¤Ï¥Þ¥ë¥Á¥×¥í¥»¥¹¡¢¥Þ¥ë¥Á¥¹¥ì¥Ã¥É¤Î¥Ï¥¤¥Ö¥ê¥Ã¥É¥â¡¼¥É¤Ç + ¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£¤³¤ì¤Ë¤è¤ê + ¿¤¯¤ÎÀßÄê¤Ë¤ª¤¤¤Æ¥¹¥±¡¼¥é¥Ó¥ê¥Æ¥£¤¬¸þ¾å¤·¤Þ¤¹¡£
+ +
¿·¤·¤¤¥Ó¥ë¥É¥·¥¹¥Æ¥à
+ +
¥Ó¥ë¥É¥·¥¹¥Æ¥à¤Ï autoconf ¤È libtool + ¤Ë´ð¤Å¤¤¤¿¤â¤Î¤Ë¤Ê¤ë¤è¤¦¤Ë¡¢ + ¿·¤·¤¯½ñ¤­Ä¾¤µ¤ì¤Þ¤·¤¿¡£¤³¤ì¤Ë¤è¤ê¡¢Apache ¤Î configure ¤Î¥·¥¹¥Æ¥à¤Ï + ¾¤Î¥Ñ¥Ã¥±¡¼¥¸¤È»÷¤¿¤â¤Î¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
+ +
¥Þ¥ë¥Á¥×¥í¥È¥³¥ë¥µ¥Ý¡¼¥È
+ +
Apache ¤ËÊ£¿ô¤Î¥×¥í¥È¥³¥ë¤ò°·¤¦¤¿¤á¤Îµ¡¹½¤¬È÷¤ï¤ê¤Þ¤·¤¿¡£ + Îã¤È¤·¤Æ mod_echo ¤¬½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£
+ +
Unix °Ê³°¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Î¥µ¥Ý¡¼¥È¤Î²þÁ±
+ +
Apache 2.0 ¤Ï BeOS¡¢OS/2¡¢Windows ¤Ê¤É¤Î Unix °Ê³°¤Î + ¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¡¢¤è¤ê®¤¯¡¢¤è¤ê°ÂÄꤷ¤ÆÆ°ºî¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + ¥×¥é¥Ã¥È¥Õ¥©¡¼¥àÆÃÍ­¤Î ¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥°¥â¥¸¥å¡¼¥ë (MPM) ¤È + Apache Portable Runtime (APR) ¤ÎƳÆþ¤Ë¤è¤ê¡¢ + ¥Í¥¤¥Æ¥£¥ô¤Î API ¤Ç¼ÂÁõ¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¡¢ + ¥Ð¥°¤¬Â¿¤¯¡¢À­Ç½¤Î°­¤¤¤³¤È¤¬Â¿¤¤ POSIX ¥¨¥ß¥å¥ì¡¼¥·¥ç¥ó¥ì¥¤¥ä¤Î»ÈÍѤò + ²óÈò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤·¤¿¡£
+ +
¿·¤·¤¤ Apache API
+ +
2.0 ¤Ç¤Ï¥â¥¸¥å¡¼¥ë¤Î API ¤¬Â礭¤¯ÊѤï¤ê¤Þ¤·¤¿¡£ + 1.3 ¤Ë¤¢¤Ã¤¿¥â¥¸¥å¡¼¥ë¤Î½çÈÖ/Í¥ÀèÅÙ¤ÎÌäÂê¤Î¿¤¯¤Ï + ¤Ê¤¯¤Ê¤Ã¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£2.0 ¤ÏÍ¥ÀèÅÙ¤ÎÁªÂò¤ò¤Û¤È¤ó¤É¤ò¼«Æ°Åª¤Ë¹Ô¤Ê¤¤¡¢ + ¥â¥¸¥å¡¼¥ë¤Î½çÈ֤Ϥè¤ê½ÀÆðÀ­¤ò¹â¤á¤ë¤¿¤á¤Ë¥Õ¥Ã¥¯Ëè¤Ë¹Ô¤Ê¤ï¤ì¤ë¤è¤¦¤Ë + ¤Ê¤ê¤Þ¤·¤¿¡£¤Þ¤¿¡¢¥³¥¢ Apache ¥µ¡¼¥Ð¤Ë¥Ñ¥Ã¥Á¤ò¤¢¤Æ¤ë¤³¤È¤Ê¤¯ + ÄɲäΥ⥸¥å¡¼¥ëµ¡Ç½¤òÄ󶡤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¿·¤·¤¤´Ø¿ô¤¬ + Äɲ䵤ì¤Þ¤·¤¿¡£
+ +
IPv6 ¥µ¥Ý¡¼¥È
+ +
Apache ¤¬»ÈÍѤ·¤Æ¤¤¤ë Apache Portable Runtime library ¤¬ + IPv6 ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤Ç¤Ï Apache ¤Ï ¥Ç¥Õ¥©¥ë¥È¤Ç + IPv6 ¤Î¥½¥±¥Ã¥È¤ò listen ¤·¤Þ¤¹¡£¤µ¤é¤Ë¡¢ + Listen, + NameVirtualHost, + VirtualHost + ¤Î³Æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ IPv6 ¤Î¥¢¥É¥ì¥¹¤ò + ¥µ¥Ý¡¼¥È¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿ (Î㤨¤Ð¡¢ + "Listen [2001:db8::1]:8080")¡£
+ +
¥Õ¥£¥ë¥¿
+ +
Apache ¤Î¥â¥¸¥å¡¼¥ë¤Ï¥µ¡¼¥Ð¤«¤éÁ÷¤é¤ì¤Æ¤­¤¿¤ê¡¢¥µ¡¼¥Ð¤Ø + Á÷¤ë¥¹¥È¥ê¡¼¥à¤ËÂФ·¤ÆÆ°ºî¤¹¤ë¥Õ¥£¥ë¥¿¤È¤·¤Æ½ñ¤¯¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë + ¤Ê¤ê¤Þ¤·¤¿¡£¤³¤ì¤Ë¤è¤ê¡¢Î㤨¤Ð CGI ¥¹¥¯¥ê¥×¥È¤Î½ÐÎϤò + mod_include ¤Î INCLUDES ¥Õ¥£¥ë¥¿¤ò»È¤Ã¤Æ + Server Side Include ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò²òÀϤ¹¤ë¡¢ + ¤È¤¤¤¦¤è¤¦¤Ê¤³¤È¤¬²Äǽ¤Ë¤Ê¤ê¤Þ¤·¤¿¡£mod_ext_filter + ¤Ç³°Éô¥×¥í¥°¥é¥à¤ò¥Õ¥£¥ë¥¿¤È¤·¤ÆÆ°ºî¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤Ï CGI ¥×¥í¥°¥é¥à¤ò¥Ï¥ó¥É¥é¤È¤·¤ÆÆ°ºî¤µ¤»¤ë¤Î¤È + ¤è¤¯»÷¤¿ÊýË¡¤Ç¤Ç¤­¤Þ¤¹¡£
+ +
¿¸À¸ì¥¨¥é¡¼±þÅú
+ +
¥Ö¥é¥¦¥¶¤Ø¤Î¥¨¥é¡¼±þÅú¤Î¥á¥Ã¥»¡¼¥¸¤¬¡¢SSI ¤Îʸ½ñ¤ò»È¤Ã¤Æ + Ê£¿ô¤Î¸À¸ì¤ÇÄ󶡤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£¸«¤¿¤á¤Î°ì´ÓÀ­¤òÊݤĤ¿¤á¤Ë + ´ÉÍý¼Ô¤¬¥«¥¹¥¿¥Þ¥¤¥º¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
+ +
ÀßÄê¤Î´ÊÁDz½
+ +
¿¤¯¤Îº®Íð¤ò¾·¤­¤¬¤Á¤Ê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬´ÊÁDz½¤µ¤ì¤Þ¤·¤¿¡£ + ¤è¤¯º®Íð¤ò°ú¤­µ¯¤³¤·¤Æ¤¤¤¿ Port ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + Bind ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿¡£Listen + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¤ß¤¬ IP ¥¢¥É¥ì¥¹¤Î¥Ð¥¤¥ó¥É¤Ë»È¤ï¤ì¤Þ¤¹¡£ + ServerName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï + ¥ê¥À¥¤¥ì¥¯¥È¤È vhost ¤Îǧ¼±¤Î¤¿¤á¤À¤±¤Ë¥µ¡¼¥Ð¤Î̾Á°¤È¥Ý¡¼¥ÈÈÖ¹æ¤ò + »ØÄꤷ¤Þ¤¹¡£
+ +
Windows NT ¤Î¥Í¥¤¥Æ¥£¥ô Unicode ¥µ¥Ý¡¼¥È
+ +
Windows NT ¾å¤Î Apache 2.0 ¤Ï¥Õ¥¡¥¤¥ë̾¤Îʸ»ú¥¨¥ó¥³¡¼¥ÉÁ´¤Æ¤Ë + utf-8 ¤ò»È¤¦¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£¤³¤ì¤é¤Ï Unicode ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë + ľÀÜÊÑ´¹¤µ¤ì¤ë¤Î¤Ç¡¢Windows 2000 ¤È Windows XP ¤ò´Þ¤à¡¢Á´¤Æ¤Î + Windows NT ·Ï¤Ç¿¸À¸ì¥µ¥Ý¡¼¥È¤¬Ä󶡤µ¤ì¤Þ¤¹¡£ + ¤³¤Î¥µ¥Ý¡¼¥È¤Ï¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¢¥¯¥»¥¹»þ¤Ë¥í¡¼¥«¥ë¤Î + ¥³¡¼¥É¥Ú¡¼¥¸¤ò»È¤¦ Windows 95, 98, ME ¤Ë¤ÏŬÍѤµ¤ì¤Þ¤»¤ó¡£
+ +
Àµµ¬É½¸½¥é¥¤¥Ö¥é¥ê¤Î¥¢¥Ã¥×¥Ç¡¼¥È
+ +
Apache 2.0 ¤Ï Perl + ¸ß´¹Àµµ¬É½¸½¥é¥¤¥Ö¥é¥ê (PCRE) ¤ò´Þ¤ó¤Ç¤¤¤Þ¤¹¡£ + Àµµ¬É½¸½¤Îɾ²Á¤Ë¤Ï¡¢¤è¤ê¶¯ÎϤˤʤä¿ Perl 5 + ¹½Ê¸¤ò»ÈÍѤ·¤Þ¤¹¡£
+ +
+
top
+
+

¥â¥¸¥å¡¼¥ë¤Î³ÈÄ¥

+ + +
+
mod_ssl
+ +
Apache 2.0 ¤Î¿·¥â¥¸¥å¡¼¥ë¡£¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï OpenSSL ¤¬ + Ä󶡤¹¤ë SSL/TLS °Å¹æ¥×¥í¥È¥³¥ë¤Ø¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ç¤¹¡£
+ +
mod_dav
+ +
Apache 2.0 ¤Î¿·¥â¥¸¥å¡¼¥ë¡£¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¥¦¥§¥Ö¥³¥ó¥Æ¥ó¥Ä¤ò + Á÷¤ê¡¢°Ý»ý¤¹¤ë¤¿¤á¤Îµ¬³Ê + HTTP Distributed Authoring and Versioning (DAV) ¤ò¼ÂÁõ¤·¤Æ¤¤¤Þ¤¹¡£
+ +
mod_deflate
+ +
Apache 2.0 ¤Î¿·¥â¥¸¥å¡¼¥ë¡£Á÷¿®Á°¤ËÁ÷¿®ÆâÍƤò°µ½Ì¤·¤Æ + ¥Í¥Ã¥È¥ï¡¼¥¯ÂÓ°è¤òÀáÌ󤹤롢¤È¤¤¤¦¥ê¥¯¥¨¥¹¥È¤ò¥Ö¥é¥¦¥¶¤¬ + Í×µá¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
+ +
mod_auth_ldap
+ +
Apache 2.0.41 ¤Î¿·¥â¥¸¥å¡¼¥ë¡£HTTP ´ðËÜǧ¾Ú¤Î¾ÚÌÀ½ñ¤òÊݸ¤¹¤ë¤Î¤Ë¡¢ + LDAP ¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»ÈÍѤǤ­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ + ´ØÏ¢¥â¥¸¥å¡¼¥ë¤Î mod_ldap ¤Ç¡¢ + ¥³¥Í¥¯¥·¥ç¥ó¤Î¥×¡¼¥ëµ¡Ç½¤È·ë²Ì¤Î¥­¥ã¥Ã¥·¥åµ¡Ç½¤¬Ä󶡤µ¤ì¤Þ¤¹¡£
+ +
mod_auth_digest
+ +
¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï¶¦Í­¥á¥â¥ê¤ò»È¤¦¤³¤È¤Ë¤è¤ê¡¢¥×¥í¥»¥¹¤ò¤Þ¤¿¤¤¤À + ¥»¥Ã¥·¥ç¥ó¤Î¥­¥ã¥Ã¥·¥å¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
+ +
mod_charset_lite
+ +
Apache 2.0 ¤Î¿·¥â¥¸¥å¡¼¥ë¡£¤³¤Î¼Â¸³Åª¤Ê¥â¥¸¥å¡¼¥ë¤Ï + ¥­¥ã¥é¥¯¥¿¥»¥Ã¥È¤ÎÊÑ´¹¤äºÆÉä¹æ²½¤ò²Äǽ¤Ë¤·¤Þ¤¹¡£
+ +
mod_file_cache
+ +
Apache 2.0 ¤Î¿·¥â¥¸¥å¡¼¥ë¡£¤³¤Î¥â¥¸¥å¡¼¥ë¤Ë¤Ï¡¢ + Apache 1.3 ¤Ë¤ª¤±¤ë mod_mmap_static µ¡Ç½¤¬´Þ¤Þ¤ì¡¢ + ¤Þ¤¿¡¢ÄɲäΥ­¥ã¥Ã¥·¥åµ¡Ç½¤¬²Ã¤ï¤Ã¤Æ¤¤¤Þ¤¹¡£
+ +
mod_headers
+ +
¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï Apache 2.0 ¤ÇÈó¾ï¤Ë½ÀÆðÀ­¤¬ + ¹â¤¯¤Ê¤ê¤Þ¤·¤¿¡£mod_proxy + ¤Ç»È¤ï¤ì¤ë¥ê¥¯¥¨¥¹¥È¤Î¥Ø¥Ã¥À¤òÊѹ¹¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¤·¡¢ + ±þÅú¥Ø¥Ã¥À¤ò¾ò·ï¤Ë±þ¤¸¤ÆÀßÄê¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
+ +
mod_proxy
+ +
proxy ¥â¥¸¥å¡¼¥ë¤Ï¿·¤·¤¤¥Õ¥£¥ë¥¿¤Îµ¡¹½¤òÍøÍѤ¹¤ë¤¿¤á¤È¡¢ + ¤è¤ê¿®Íê¤Ç¤­¤ë¡¢HTTP/1.1 ¤Ë½àµò¤·¤¿ proxy ¤ò¼ÂÁõ¤¹¤ë¤¿¤á¤Ë + ´°Á´¤Ë½ñ¤­Ä¾¤µ¤ì¤Þ¤·¤¿¡£¤µ¤é¤Ë¡¢¿·¤·¤¤ + <Proxy> + ÀßÄꥻ¥¯¥·¥ç¥ó¤¬proxy ¤µ¤ì¤ë¥µ¥¤¥È¤Î¤è¤êÆɤߤ䤹¤¯ (ÆâÉôŪ¤Ë¤â¤è¤ê®¤¤) + ÀßÄê¤òÄ󶡤·¤Þ¤¹¡£¥ª¡¼¥Ð¡¼¥í¡¼¥É¤µ¤ì¤¿ + <Directory "proxy:... > + ÀßÄê¤Ï¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£¤³¤Î¥â¥¸¥å¡¼¥ë¤Ï proxy_connect, + proxy_ftp, proxy_http + ¤È¤¤¤Ã¤¿¡¢ÆÃÄê¤Î¥×¥í¥È¥³¥ë¤ò¥µ¥Ý¡¼¥È¤¹¤ë + ¥â¥¸¥å¡¼¥ë¤Ëʬ³ä¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
+ +
mod_negotiation
+ +
¥¯¥é¥¤¥¢¥ó¥È¤¬ NOT ACCEPTABLE ¤ä MULTIPLE CHOICES ±þÅú¤Î + Âå¤ï¤ê¤Ë¾ï¤ËñÆȤÎʸ½ñ¤ò¼õ¤±¤È¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¡¢¿·¤·¤¤¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ForceLanguagePriority + ¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + ¤µ¤é¤Ë¡¢¤è¤ê°ì´ÓÀ­¤Î¤¢¤ë·ë²Ì¤òÄ󶡤¹¤ë¤¿¤á¤Ë + ¥Í¥´¥·¥¨¡¼¥·¥ç¥ó¤È MultiViews ¤Î¥¢¥ë¥´¥ê¥º¥à¤¬²þÁ±¤µ¤ì¡¢ + ʸ½ñ¤ÎÆâÍƤò´Þ¤á¤ë¤³¤È¤Î¤Ç¤­¤ë¡¢¿·¤·¤¤·Á¼°¤Î¥¿¥¤¥×¥Þ¥Ã¥×¤¬ + Ä󶡤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
+ +
mod_autoindex
+ +
Autoindex ¤µ¤ì¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ÎÆâÍÆ°ìÍ÷¤¬¡¢ + ¤­¤ì¤¤¤Ëɽ¼¨¤µ¤ì¤ë¤¿¤á¤Ë HTML ¤Î¥Æ¡¼¥Ö¥ë¤ò»È¤¦¤è¤¦¤Ë + ÀßÄê¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£¤Þ¤¿¡¢¥Ð¡¼¥¸¥ç¥ó¤Ë¤è¤ë¥½¡¼¥Æ¥£¥ó¥°¤Ê¤É¡¢ + ¤è¤êºÙ¤«¤¤¥½¡¼¥Æ¥£¥ó¥°¤ÎÀ©¸æ¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¡¢¥Ç¥£¥ì¥¯¥È¥ê + ¤ÎÆâÍÆ°ìÍ÷¤ò¥ï¥¤¥ë¥É¥«¡¼¥É¤Ë¤è¤êÁªÊ̤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤â¤Ê¤ê¤Þ¤·¤¿¡£
+ +
mod_include
+ +
¿·¤·¤¤¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¡¢SSI ¤Î¥Ç¥Õ¥©¥ë¥È¤Î³«»Ï¥¿¥°¤È½ªÎ»¥¿¥°¤ò + Êѹ¹¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£¤Þ¤¿¡¢¥¨¥é¡¼¤È»þ¹ï¤Î·Á¼°¤ÎÀßÄ꤬ SSI ¤Î + ʸ½ñÃæ¤Ç¤Ï¤Ê¤¯¡¢¼çÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Ç¹Ô¤Ê¤¨¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + Àµµ¬É½¸½¤Î²òÀϤȥ°¥ë¡¼¥×²½¤Î·ë²Ì (Perl ¤ÎÀµµ¬É½¸½¤Î¹½Ê¸¤Ë + ´ð¤Å¤¤¤¿¤â¤Î¤Ë¤Ê¤ê¤Þ¤·¤¿) ¤ò mod_include + ¤ÎÊÑ¿ô $0 .. $9 ¤Ë¤è¤ê¼èÆÀ¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
+ +
mod_auth_dbm
+ +
AuthDBMType + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¡¢Ê£¿ô¤Î DBM ·¿¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò¥µ¥Ý¡¼¥È¤¹¤ë + ¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
+ +
+
+
+

Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_0.html.ko.euc-kr b/docs/manual/new_features_2_0.html.ko.euc-kr new file mode 100644 index 00000000..b2d02f17 --- /dev/null +++ b/docs/manual/new_features_2_0.html.ko.euc-kr @@ -0,0 +1,233 @@ + + + +Apache 2.0ÀÇ »õ·Î¿î ±â´É °³¿ä - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Apache 2.0ÀÇ »õ·Î¿î ±â´É °³¿ä

+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ +

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ À¥¼­¹ö 1.3 ¹öÀü°ú 2.0 ¹öÀü°£ÀÇ ÁÖµÈ Â÷ÀÌÁ¡À» + ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

ÇÙ½É ºÎºÐ¿¡¼­ ³ª¾ÆÁø Á¡

+ + +
+
À¯´Ð½º ¾²·¹µå
+ +
POSIX ¾²·¹µå¸¦ Áö¿øÇÏ´Â À¯´Ð½º ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡¸¦ + ¿©·¯ ÇÁ·Î¼¼½º¿Í ¿©·¯ ¾²·¹µå·Î È¥ÇÕÇؼ­ ½ÇÇàÇÒ ¼ö ÀÖ´Ù. + ÀüºÎ´Â ¾Æ´ÏÁö¸¸ ¸¹Àº °æ¿ì È®Àå°¡´É¼º(scalability)À» ³ôÀδÙ.
+ +
»õ·Î¿î ÄÄÆÄÀÏ ½Ã½ºÅÛ
+ +
ÄÄÆÄÀÏ ½Ã½ºÅÛÀÌ autoconf¿Í libtoolÀ» + »ç¿ëÇϵµ·Ï ÀçÀÛ¼ºµÇ¾ú´Ù. ±×·¡¼­ ¾ÆÆÄÄ¡ ±¸¼º ½Ã½ºÅÛÀÌ ´Ù¸¥ + ÆÐÅ°Áöµé°ú Á»´õ ºñ½ÁÇØÁ³´Ù.
+ +
¿©·¯ ÇÁ·ÎÅäÄÝ Áö¿ø
+ +
ÀÌÁ¦ ¾ÆÆÄÄ¡´Â ¿©·¯ ÇÁ·ÎÅäÄÝÀ» ¼­ºñ½ºÇÒ ¼ö ÀÖ´Â ±¸Á¶¸¦ + °®Ãè´Ù. mod_echo°¡ ±× ¿¹·Î ÀÛ¼ºµÇ¾ú´Ù.
+ +
ºñÀ¯´Ð½º Ç÷¡Æû¿¡ ´ëÇÑ ´õ ³ªÀº Áö¿ø
+ +
Apache 2.0´Â BeOS, OS/2, À©µµ¿ìÁî¿Í °°Àº ºñÀ¯´Ð½º + Ç÷¡Æû¿¡¼­ ´õ ºü¸£°í ¾ÈÁ¤È­µÇ¾ú´Ù. ÀÌÁ¦ ¾ÆÆÄÄ¡´Â À̵é + Ç÷¡Æû¿¡¼­ ¹ö±×°¡ ¸¹°í ¼º´ÉÀÌ ´À·È´ø POSIX ȣȯÃþ ´ë½Å + ÀÚü API·Î ±¸ÇöµÈ Ç÷¡Æû ƯÀ¯ÀÇ ´ÙÁßó¸® ¸ðµâ + (MPM)°ú Apache Portable Runtime (APR)À» »ç¿ëÇÏ¿© ±¸ÇöµÈ´Ù.
+ +
»õ·Î¿î ¾ÆÆÄÄ¡ API
+ +
¸ðµâ API°¡ 2.0¿¡¼­ »ó´çÈ÷ º¯Çß´Ù. 1.3ÀÇ ¿©·¯ ¸ðµâ + ¼ø¼­¿Í ¿ì¼±¼øÀ§ ¹®Á¦°¡ »ç¶óÁ³´Ù. 2.0Àº À̸¦ ´ëºÎºÐ ÀÚµ¿À¸·Î + ó¸®Çϸç, ¸ðµâ ¼ø¼­´Â ÀÌÁ¦ ´õ À¯¿¬ÇÑ ÈÅ(hook) ´ÜÀ§·Î ÁöÁ¤ÇÑ´Ù. + ¶Ç, ¾ÆÆÄÄ¡ ¼­¹ö ÇÙ½É ºÎºÐÀ» ¼öÁ¤ÇÏÁö ¾Ê°í »õ·Î¿î ¸ðµâ ±â´ÉÀ» + Á¦°øÇÏ´Â ÇÔ¼ö°¡ Ãß°¡µÇ¾ú´Ù.
+ +
IPv6 Áö¿ø
+ +
ÇÏÀ§ Apache Portable Runtine ¶óÀ̺귯¸®°¡ IPv6¸¦ Áö¿øÇÏ´Â + ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡´Â ±âº»ÀûÀ¸·Î IPv6 ¼ÒÄÏÀ» ±â´Ù¸°´Ù. ¶Ç, + Listen, + NameVirtualHost, + VirtualHost Áö½Ã¾î°¡ + IPv6 ¼ýÀÚ ÁÖ¼Ò¸¦ Áö¿øÇÑ´Ù. (¿¹, + "Listen [2001:db8::1]:8080").
+ +
ÇÊÅ͸µ
+ +
ÀÌÁ¦ ¾ÆÆÄÄ¡ ¸ðµâÀ» ¼­¹ö·Î ¿À°í°¡´Â È帧¿¡ ´ëÇÑ + ÇÊÅÍ·Î »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î mod_includeÀÇ + INCLUDES ÇÊÅ͸¦ »ç¿ëÇÏ¿© CGI ½ºÅ©¸³Æ® Ãâ·Â¿¡¼­ + Server Side Include Áö½Ã¾î¸¦ ó¸®ÇÒ ¼ö ÀÖ´Ù. + mod_ext_filter ¸ðµâÀº CGI ÇÁ·Î±×·¥À» + Çڵ鷯·Î »ç¿ëÇÏ´Â °Í°ú °°ÀÌ ¿ÜºÎ ÇÁ·Î±×·¥À» ÇÊÅÍ·Î + »ç¿ëÇÒ ¼ö ÀÖ°Ô ÇÑ´Ù.
+ +
´Ù±¹¾î ¿À·ù ÀÀ´ä
+ +
ºê¶ó¿ìÀú·Î º¸³»´Â ¿À·ù ÀÀ´ä¹®ÀÌ ÀÌÁ¦ SSI ¹®¼­¸¦ + »ç¿ëÇÏ¿© ´Ù±¹¾î·Î Á¦°øµÈ´Ù. °ü¸®ÀÚ´Â ÅëÀÏµÈ ¿Ü°üÀ» À§ÇØ + ÀÌ ¹®¼­¸¦ ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.
+ +
°£´ÜÇØÁø ¼³Á¤
+ +
È¥¶õÀ» ÁÖ´ø ¸¹Àº Áö½Ã¾îµéÀÌ °£´ÜÇØÁ³´Ù. ÀÚÁÖ È¥¶õÀ» + ÁÖ´ø Port¿Í BindAddress Áö½Ã¾î´Â + ¾ø¾îÁö°í IP ÁÖ¼Ò ¿¬°á¿¡ + Listen Áö½Ã¾î¸¸À» + »ç¿ëÇÑ´Ù. ServerName + Áö½Ã¾î´Â ¸®´ÙÀÌ·º¼Ç°ú °¡»óÈ£½ºÆ® ÀνĿ¡¸¸ »ç¿ëµÉ ¼­¹ö¸í°ú + Æ÷Æ®¸¦ ÁöÁ¤ÇÑ´Ù.
+ +
Windows NT À¯´ÏÄÚµå ÀÚü Áö¿ø
+ +
Windows NT¿¡¼­ Apache 2.0Àº ÀÌÁ¦ ¸ðµç ÆÄÀϸí ÀÎÄÚµù¿¡ + utf-8À» »ç¿ëÇÑ´Ù. ÆÄÀϸíÀº ÇÏÀ§ À¯´ÏÄÚµå ÆÄÀϽýºÅÛÀ¸·Î Á÷Á¢ + º¯¿ªµÇ¾î, Windows 2000°ú Windows XP¸¦ Æ÷ÇÔÇÑ ¸ðµç Windows NT±â¹Ý + ½Ã½ºÅÛ¿¡ ´Ù±¹¾î Áö¿øÀ» Á¦°øÇÑ´Ù. ÀÌ ±â´ÉÀº Windows 95, + 98, ME¿¡´Â Áö¿øµÇÁö¾Ê°í, ÆÄÀϽýºÅÛ Á¢±Ù¿¡ Àü°ú °°ÀÌ ½Ã½ºÅÛÀÇ + Áö¿ª ÄÚµåÆäÀÌÁö¸¦ »ç¿ëÇÑ´Ù.
+ +
Á¤±ÔÇ¥Çö½Ä ¶óÀ̺귯¸® Updated
+ +
Apache 2.0Àº Perlȣȯ + Á¤±ÔÇ¥Çö½Ä ¶óÀ̺귯¸® (Perl Compatible Regular Expression + Library) (PCRE)¸¦ Æ÷ÇÔÇÑ´Ù. ÀÌÁ¦ ¸ðµç Á¤±ÔÇ¥Çö½Ä¿¡ + ´õ °­·ÂÇÑ Perl 5 ¹®¹ýÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù.
+ +
+
top
+
+

¸ðµâ¿¡¼­ ³ª¾ÆÁø Á¡

+ + +
+
mod_ssl
+ +
Apache 2.0¿¡¼­ »õ·Î Ãß°¡µÇ¾ú´Ù. ÀÌ ¸ðµâÀº OpenSSLÀÌ + Á¦°øÇÏ´Â SSL/TLS ¾Ïȣȭ ÇÁ·ÎÅäÄÝÀÇ ÀÎÅ×ÆäÀ̽º´Ù.
+ +
mod_dav
+ +
Apache 2.0¿¡¼­ »õ·Î Ãß°¡µÇ¾ú´Ù. ÀÌ ¸ðµâÀº À¥ÄÁÅÙÃ÷¸¦ + ¿Ã¸®°í °ü¸®ÇϱâÀ§ÇÑ HTTP Distributed Authoring and Versioning + (DAV) Ç¥ÁØÀ» ±¸ÇöÇÑ´Ù.
+ +
mod_deflate
+ +
Apache 2.0¿¡¼­ »õ·Î Ãß°¡µÇ¾ú´Ù. ³×Æ®¿÷ »ç¿ë·®À» + ÁÙÀ̱âÀ§ÇØ ºê¶ó¿ìÀú¿¡°Ô ÄÁÅÙÃ÷¸¦ ¾ÐÃàÇؼ­ º¸³»¶ó°í ¿äûÇÒ + ¼ö ÀÖ´Ù.
+ +
mod_auth_ldap
+ +
Apache 2.0.41¿¡¼­ »õ·Î Ãß°¡µÇ¾ú´Ù. ÀÌ ¸ðµâÀº HTTP + Basic Authentication¿¡ »ç¿ëÇÏ´Â Á¤º¸¸¦ LDAP µ¥ÀÌÅͺ£À̽º¿¡ + ÀúÀåÇÑ´Ù. °ü·ÃµÈ mod_ldap ¸ðµâÀº + ¿¬°áÇ®(connection pool)À» Á¦°øÇÏ°í, °á°ú¸¦ ij½ÌÇÑ´Ù.
+ +
mod_auth_digest
+ +
°øÀ¯¸Þ¸ð¸®¸¦ »ç¿ëÇÏ¿© ÇÁ·Î¼¼½º°£ ¼¼¼Ç ij½ÌÀ» Áö¿øÇÑ´Ù.
+ +
mod_charset_lite
+ +
Apache 2.0¿¡¼­ »õ·Î Ãß°¡µÇ¾ú´Ù. ÀÌ ½ÇÇèÀûÀÎ ¸ðµâÀº + ¹®ÀÚÁýÇÕ º¯È¯°ú ¹®ÀÚÁýÇÕ ÀçÀÛ¼º ±â´ÉÀ» Á¦°øÇÑ´Ù.
+ +
mod_file_cache
+ +
Apache 2.0¿¡¼­ »õ·Î Ãß°¡µÇ¾ú´Ù. ÀÌ ¸ðµâÀº Apache 1.3ÀÇ + mod_mmap_static ±â´É¿¡ ´õ ³ªÀº ij½¬ ±â´ÉÀ» + Ãß°¡Çß´Ù.
+ +
mod_headers
+ +
ÀÌ ¸ðµâÀº Apache 2.0¿¡¼­ ´õ À¯¿¬ÇØÁ³´Ù. ÀÌÁ¦ + mod_proxy°¡ »ç¿ëÇÏ´Â ¿äû Çì´õ¸¦ ¼öÁ¤ÇÒ + ¼ö ÀÖ°í, °æ¿ì¿¡ µû¶ó¼­ ÀÀ´ä Çì´õ¸¦ ¼³Á¤ÇÒ ¼öµµ ÀÖ´Ù.
+ +
mod_proxy
+ +
ÀÌ ÇÁ·Ï½Ã ¸ðµâÀº »õ·Î¿î ÇÊÅÍ ±¸Á¶¸¦ ÀÌ¿ëÇÏ°í ´õ ¹ÏÀ»¸¸ÇÑ + HTTP/1.1 ÇÁ·Ï½Ã¸¦ ±¸ÇöÇϱâÀ§ÇØ ¿ÏÀüÈ÷ ÀçÀÛ¼ºµÇ¾ú´Ù. Ãß°¡·Î + »õ·Î¿î <Proxy> + ¼³Á¤ ¼½¼ÇÀº ÇÁ·Ï½Ã ¼³Á¤À» ´õ ½±°Ô (±×¸®°í ³»ºÎÀûÀ¸·Î ´õ + ºü¸£°Ô) ¸¸µç´Ù. °ú°Å <Directory "proxy:..."> + ¼³Á¤Àº ÀÌÁ¦ Áö¿øÇÏÁö ¾Ê´Â´Ù. ¸ðµâÀº proxy_connect, + proxy_ftp, proxy_http¿Í °°ÀÌ + Áö¿øÇÏ´Â ÇÁ·ÎÅäÄÝ º°·Î ³ª´²Á³´Ù.
+ +
mod_negotiation
+ +
»õ·Î¿î ForceLanguagePriority + Áö½Ã¾î´Â Ŭ¶óÀ̾ðÆ®°¡ NOT ACCEPTABLEÀ̳ª MULTIPLE CHOICES + ÀÀ´ä ´ë½Å ¸ðµç °æ¿ì ÇÑ ¹®¼­¸¦ ¹ÞÀ½À» º¸ÀåÇÑ´Ù. Ãß°¡·Î + Çù»ó ¾Ë°í¸®Áò°ú MultiViews ¾Ë°í¸®ÁòÀÌ ´õ ÀÏ°üµÈ °á°ú¸¦ + ³»µµ·Ï ¼öÁ¤µÇ¾ú°í, ¹®¼­ ³»¿ëÀ» Æ÷ÇÔÇÒ ¼ö ÀÖ´Â »õ·Î¿î Çü½ÄÀÇ + type mapÀÌ Ãß°¡µÇ¾ú´Ù.
+ +
mod_autoindex
+ +
ÀÚµ¿À¸·Î »ý¼ºµÈ µð·ºÅ丮 ¸ñ·ÏÀÌ ÀÌÁ¦ ´õ ±ò²ûÇÑ Çü½ÄÀ» + À§ÇØ HTML Ç¥¸¦ »ç¿ëÇÒ ¼ö ÀÖ°Ô µÇ¾ú°í, ¹öÀü Á¤·ÄÀ» Æ÷ÇÔÇÏ¿© + Á¤·Ä¼ø¼­¸¦ ÀÚ¼¼È÷ Á¶ÀýÇÒ ¼ö ÀÖÀ¸¸ç, µð·ºÅ丮 ¸ñ·ÏÀ» ¿ÍÀϵåÄ«µå·Î + °É·¯³¾ ¼ö ÀÖ´Ù.
+ +
mod_include
+ +
»õ·Î¿î Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© SSI ¿ä¼ÒÀÇ ±âº» ½ÃÀÛ ÅÂ±×¿Í + ¸¶Ä§ ű׸¦ º¯°æÇÒ ¼ö ÀÖ°í, ¿À·ù¿Í ½Ã°£Çü½ÄÀ» SSI ¹®¼­¿Ü¿¡ + ÁÖ ¼³Á¤ÆÄÀÏ¿¡¼­µµ ¼³Á¤ÇÒ ¼ö ÀÖ°Ô µÇ¾ú´Ù. mod_include¿¡¼­ (ÀÌÁ¦ + Perl Á¤±ÔÇ¥Çö½Ä ¹®¹ýÀ¸·Î) Á¤±ÔÇ¥Çö½Ä ÆĽ̰ú ±×·ìÀÇ + °á°ú¸¦ mod_includeÀÇ $0 + ... $9 º¯¼ö·Î ¾òÀ» ¼ö ÀÖ´Ù.
+ +
mod_auth_dbm
+ +
ÀÌÁ¦ AuthDBMType + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ¿©·¯ DBM·ù µ¥ÀÌÅͺ£À̽º¸¦ Áö¿øÇÑ´Ù.
+ +
+
+
+

°¡´ÉÇÑ ¾ð¾î:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_0.html.pt-br b/docs/manual/new_features_2_0.html.pt-br new file mode 100644 index 00000000..db18bf15 --- /dev/null +++ b/docs/manual/new_features_2_0.html.pt-br @@ -0,0 +1,242 @@ + + + +Descrição das novas funcionalidades do Apache 2.0 - Servidor HTTP Apache + + + + +
+

Módulos | Diretrizes | FAQ | Glossário | Mapa do site

+

Servidor HTTP Apache Versão 2.2

+
+
<-
+
+Apache > Servidor HTTP > Documentação > Versão 2.2

Descrição das novas funcionalidades do Apache 2.0

+
+

Línguas Disponíveis:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ +

Esse documento descreve algumas das mudanças principais + entre as versões 1.3 e 2.0 do Servidor HTTP Apache.

+
+ +
top
+
+

Principais Melhorias

+ + +
+
Threading Unix
+ +
Em sistemas Unix com suporte a threads POSIX, o Apache pode + funcionar em modo híbrido multiprocesso e multithread. Não funciona + em todas configurações, mas melhora a escalabilidade em muitas.
+ +
Novo Sistema de Compilação
+ +
O sistema de compilação foi reescrito do zero para utilizar o + autoconf e o libtool, tornando a + configuração do sistema Apache mais similar a de outros + pacotes.
+ +
Suporte Multi-protocolo
+ +
O Apache possui agora uma infraestrutura feita para suportar + múltiplos protocolos. O módulo mod_echo é um + exemplo ilustrativo de sua utilização.
+ +
Suporte Aperfeiçoado para Plataformas Não-Unix
+ +
O Apache 2.0 está mais rápido e mais estável em plataformas + Não-Unix como BeOS, OS/2 e Windows. Com a introdução de módulos + multi-processamento (MPMs) específicos e a + Apache Portable Runtime (APR), essas plataformas estão implementando + as suas APIs nativas, evitando as camadas de emulação POSIX que se + mostravam lentas e defeituosas.
+ +
Nova API Apache
+ +
A API para módulos mudou significativamente na versão 2.0. + Muitos dos problemas de ordenamento/prioridade da versão + 1.3 foram resolvidos. A versão 2.0 faz o ordenamento automático + "per-hook" para permitir mais flexibilidade. Novas chamadas foram + adicionadas para fornecer capacidades adicionais sem a necessidade + de se aplicar nenhum patch ao servidor Apache principal.
+ +
Suporte IPv6
+ +
Em sistemas onde o IPv6 é suportado pela biblioteca de base + Apache Portable Runtime, o Apache monitora por padrão + as interfaces IPv6. Em adição as diretrizes Listen, NameVirtualHost e VirtualHost, suportam correntes (strings) de + endereços numéricos do tipo IPv6. (ex. "Listen + [2001:db8::1]:8080").
+ +
Filtrando
+ +
Os módulos do Apache agora são feito filtros que + agem na corrente do conteúdo na medida que este é entregue, tanto + na entrada quando na saída de dados do servidor. É possível então, + por exemplo, que o retorno de dados de scripts CGI sejam analisados + pelas diretrizes do "Server Side Include" usando o filtro INCLUDES do mod_include. O módulo mod_ext_filter, permite que programas externos trabalhem + como filtros do mesmo modo que aplicações CGI funcionam como + manipuladores.
+ +
Respostas de Erro Multi-linguais
+ +
Mensagens de erro para o navegador agora são fornecidas em + diversas línguas, usando documentos SSI. Podem ser personalizadas + pelo administrador que desejar definir seus próprios + padrões.
+ +
Configuração Simplificada
+ +
Muitas diretrizes confusas foram simplificadas. Entre elas, + Port e BindAddress não existem + mais; apenas a diretriz Listen + é usada para direcionar endereços IP; a diretriz ServerName especifica o nome do servidor + e o número da porta apenas para redirecionamento e reconhecimento + de hospedeiros virtuais.
+ +
Suporte Nativo ao Unicode do Windows NT
+ +
O Apache 2.0 para Windows NT agora usa utf-8 para codificação + de todos os nomes de arquivos. A tradução para o sistema + base Unicode, torna possível o suporte multi-lingual para todas + as instalações da família NT, incluindo o Windows 2000 e Windows XP. + Esse suporte não se estende ao Windows 95, 98 ou ME, que + continuam usando o código de páginas da máquina local para o + acesso ao sistema de arquivos.
+ +
Biblioteca de Expressões Regulares Atualizada
+ +
O Apache 2.0 inclui a Biblioteca + de Expressões Regulares Compatíveis Perl (PCRE). Todas as + avaliações de expressões regulares usam a mais poderosa sintaxe + do Perl 5.
+ +
+
top
+
+

Melhorias nos Módulos

+ + +
+
mod_ssl
+ +
Novo módulo no Apache 2.0. Esse módulo é uma interface + para os protocolos de codificação SSL/TLS fornecidos pela + OpenSSL.
+ +
mod_dav
+ +
Novo módulo no Apache 2.0. Este módulo implementa as + especificações de Autoria Distribuída e Versões (Distributed + Authoring and Versioning - DAV) para HTTP, para a publicação + e a manutenção de conteúdo da web.
+ +
mod_deflate
+ +
Novo módulo no Apache 2.0. Esse módulo permite o suporte + a navegadores que solicitam que o conteúdo seja comprimido antes + da entrega, economizando banda da rede.
+ +
mod_auth_ldap
+ +
Novo módulo no Apache 2.0.41. Este módulo permite que + bancos de dados LDAP sejam usados para armazenar credenciais + para Autenticação Básica HTTP. Um módulo que o acompanha mod_ldap, fornece a conciliação de conexões e armazenamento + de resultados.
+ +
mod_auth_digest
+ +
Inclui suporte adicional para armazenamento de sessões + através de processos que usam memória compartilhada.
+ +
mod_charset_lite
+ +
Novo módulo no Apache 2.0. Este modo experimental permite a + tradução de tabelas de caracteres ou re-codificação.
+ +
mod_file_cache
+ +
Novo módulo no Apache 2.0. Esse módulo inclui a funcionalidade + do mod_mmap_static do Apache 1.3, além de disponibilizar + outras possibilidades de armazenamento.
+ +
mod_headers
+ +
Este módulo está muito mais flexível no Apache 2.0. Pode + modificar pedidos de cabeçalhos usados pelo mod_proxy, e incondicionalmente pode ajustar cabeçalhos de respostas.
+ +
mod_proxy
+ +
O módulo proxy foi totalmente reescrito para levar vantagem + da nova infraestrutura de filtro e implementar um proxy mais fiel e + de acordo com o padrão HTTP/1.1. Além disso, uma nova seção + de configuração <Proxy> fornece controles mais legíveis (e internamente + mais rápidos) para sites com proxies; configurações + sobrecarregadas <Directory "proxy:...">, não + são suportadas. O módulo agora é dividido em suporte + de protocolos específicos incluindo proxy_connect, + proxy_ftp e proxy_http.
+ +
mod_negotiation
+ +
A nova diretriz ForceLanguagePriority pode ser usada para assegurar que + o cliente receba um único documento em todos os casos, ao invés de + respostas "NOT ACCEPTABLE" ou "MULTIPLE CHOICES". Novos algoritmos + de negociação e visões múltiplas (MultiViews) foram organizados para + obter resultados mais consistentes e uma nova forma de tipo de mapa + (map type) que podem incluir o conteúdo de documentos é fornecido.
+ +
mod_autoindex
+ +
As listagens de diretórios automáticas podem ser + configuradas para usar tabelas HTML para formatações mais limpas + e permitir controles mais acurados de classificação, incluindo + ordenação por versão e filtro da lista de + diretórios através de caracteres-coringa.
+ +
mod_include
+ +
Novas diretrizes permitem que as tags padrões start e + end para elementos SSI, possam ser alteradas e permitir que + as configurações de formatos de erro e hora sejam incluídos no + arquivo de configuração principal, ao invés de serem adicionadas + ao documento SSI. Resultados de análises de expressões regulares + e agrupamento (baseadas na sintaxe de expressões regulares do Perl) + podem ser obtidas usando as variáveis do módulo mod_include, de $0 a $9.
+ +
mod_auth_dbm
+ +
Agora suporta múltiplos tipos de banco de dados similares ao DBM, + usando a diretriz AuthDBMType + .
+ +
+
+
+

Línguas Disponíveis:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_0.html.ru.koi8-r b/docs/manual/new_features_2_0.html.ru.koi8-r new file mode 100644 index 00000000..74285c51 --- /dev/null +++ b/docs/manual/new_features_2_0.html.ru.koi8-r @@ -0,0 +1,250 @@ + + + +ïÂÚÏÒ ÎÏ×ÙÈ ×ÏÚÍÏÖÎÏÓÔÅÊ × Apache 2.0 - HTTP ÓÅÒ×ÅÒ Apache + + + + +
+

íÏÄÕÌÉ | äÉÒÅËÔÉ×Ù | FAQ | çÌÏÓÓÁÒÉÊ | ëÁÒÔÁ ÓÁÊÔÁ

+

HTTP ÓÅÒ×ÅÒ Apache ×ÅÒÓÉÉ 2.2

+
+
<-
+
+Apache > HTTP ÓÅÒ×ÅÒ > äÏËÕÍÅÎÔÁÃÉÑ > ÷ÅÒÓÉÑ 2.2

ïÂÚÏÒ ÎÏ×ÙÈ ×ÏÚÍÏÖÎÏÓÔÅÊ × Apache 2.0

+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ +

üÔÏÔ ÄÏËÕÍÅÎÔ ÏÐÉÓÙ×ÁÅÔ ÏÓÎÏ×ÎÙÅ ÒÁÚÌÉÞÉÑ ÍÅÖÄÕ ×ÅÒÓÉÑÍÉ 1.3 É 2.0 HTTP ÓÅÒ×ÅÒÁ Apache

+
+ +
top
+
+

õÌÕÞÛÅÎÉÑ × ÑÄÒÅ ÓÅÒ×ÅÒÁ

+ + +
+
íÎÏÇÏÐÏÔÏÞÎÏÓÔØ × UNIX
+ +
îÁ UNIX ÓÉÓÔÅÍÁÈ, ËÏÔÏÒÙÅ ÐÏÄÄÅÒÖÉ×ÁÀÔ ÐÏÔÏËÉ (ÎÉÔÉ) ÓÔÁÎÄÁÒÔÁ POSIX, + Apache ÔÅÐÅÒØ ÍÏÖÅÔ ×ÙÐÏÌÎÑÔØÓÑ × ÇÉÂÒÉÄÎÏÍ ÍÎÏÇÏÐÒÏÃÅÓÓÏ×Ï-ÍÎÏÇÏÐÏÔÏÞÎÏÍ ÒÅÖÉÍÅ. + üÔÏ ÓÐÏÓÏÂÓÔ×ÕÅÔ ÒÁÓÛÉÒÑÅÍÏÓÔÉ + ÓÉÓÔÅÍÙ ÄÌÑ ÍÎÏÇÉÈ, ÎÏ ÎÅ ÄÌÑ ×ÓÅÈ ËÏÎÆÉÇÕÒÁÃÉÊ.
+ +
îÏ×ÁÑ ÓÉÓÔÅÍÁ ÓÂÏÒËÉ
+ +
óÉÓÔÅÍÁ ÓÂÏÒËÉ ÂÙÌÁ ÐÏÌÎÏÓÔØÀ ÉÚÍÅÎÅÎÁ, É ÔÅÐÅÒØ ÏÓÎÏ×Ù×ÁÅÔÓÑ ÎÁ autoconf É libtool. + üÔÏ ÄÅÌÁÅÔ ÐÒÏÃÅÓÓ ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÑ Apache ÂÏÌÅÅ ÐÏÈÏÖÉÍ ÎÁ ÁÎÁÌÏÇÉÞÎÙÊ ÐÒÏÃÅÓÓ × ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍÎÙÈ + ÐÒÏÄÕËÔÁÈ.
+ +
ðÏÄÄÅÒÖËÁ ÒÁÚÌÉÞÎÙÈ ÐÒÏÔÏËÏÌÏ×
+ +
Apache ÔÅÐÅÒØ ÉÍÅÅÔ ÓÐÅÃÉÁÌØÎÕÀ ÉÎÆÒÁÓÔÒÕËÔÕÒÕ, + ÓÐÏÓÏÂÎÕÀ ÏÂÓÌÕÖÉ×ÁÔØ ÒÁÚÌÉÞÎÙÅ ÐÒÏÔÏËÏÌÙ. + íÏÄÕÌØ mod_echo ÂÙÌ ÎÁÐÉÓÁÎ × ËÁÞÅÓÔ×Å + ÐÒÉÍÅÒÁ ÜÔÏÍÕ.
+ +
õÌÕÞÛÅÎÎÁÑ ÐÏÄÄÅÒÖËÁ ÏÔÌÉÞÎÙÈ ÏÔ UNIX + ÐÌÁÔÆÏÒÍ
+ +
Apache 2.0 ÓÔÁÌ ÒÁÂÏÔÁÔØ ÂÙÓÔÒÅÅ É ÎÁÄÅÖÎÅÅ + ÎÁ ÏÔÌÉÞÎÙÈ ÏÔ UNIX ÐÌÁÔÆÏÒÍÁÈ, ÔÁËÉÈ ËÁË: BeOS, + OS/2 É Windows. ó ××ÅÄÅÎÉÅÍ ÎÏ×ÙÈ ÓÐÅÃÉÆÉÞÎÙÈ + ÄÌÑ ËÁÖÄÏÊ ÐÌÁÔÆÏÒÍÙ ÍÕÌØÔÉ-ÐÒÏÃÅÓÓÎÙÈ ÍÏÄÕÌÅÊ (MPMs) É + ÂÉÂÌÉÏÔÅËÉ Apache Portable Runtime (APR), ÜÔÉ ÐÌÁÔÆÏÒÍÙ + ÔÅÐÅÒØ ÐÏÄÄÅÒÖÉ×ÁÀÔÓÑ Ó ÐÏÍÏÝØÀ ÉÈ ÓÏÂÓÔ×ÅÎÎÙÈ API, ÞÔÏ + ÐÏÚ×ÏÌÑÅÔÓÑ ÉÚÂÅÖÁÔØ ××ÅÄÅÎÉÑ ÚÁÞÁÓÔÕÀ ÎÅÐÒÁ×ÉÌØÎÏ ÒÁÂÏÔÁÀÝÉÈ + ÉÚ-ÚÁ ÂÏÌØÛÏÇÏ ËÏÌÉÞÅÓÔ×Á ÏÛÉÂÏË POSIX - ÜÍÕÌÉÒÕÀÝÉÈ ÓÌÏÅ×.
+ +
îÏ×ÙÊ API ÄÌÑ Apache
+ +
API ÄÌÑ ÎÁÐÉÓÁÎÉÑ ÍÏÄÕÌÅÊ ÚÎÁÞÉÔÅÌØÎÏ ÉÚÍÅÎÉÌÓÑ × ×ÅÒÓÉÉ 2.0. + íÎÏÇÉÅ ÉÚ ÐÒÏÂÌÅÍ ×ÅÒÓÉÉ 1.3, Ó×ÑÚÁÎÎÙÅ Ó ÐÏÒÑÄËÏÍ ÓÌÅÄÏ×ÁÎÉÑ + ÍÏÄÕÌÅÊ É ÉÈ ÐÒÉÏÒÉÔÅÔÁÍÉ, ÄÏÌÖÎÙ ÉÓÞÅÚÎÕÔØ. ÷ ×ÅÒÓÉÉ 2.0 + ÂÏÌØÛÁÑ ÞÁÓÔØ ÄÁÎÎÏÊ ÒÁÂÏÔÙ ÔÅÐÅÒØ ÄÅÌÁÅÔÓÑ ÓÅÒ×ÅÒÏÍ Á×ÔÏÍÁÔÉÞÅÓËÉ, + Á ÐÏÒÑÄÏË ÓÌÅÄÏ×ÁÎÉÑ ÍÏÄÕÌÅÊ ÏÐÒÅÄÅÌÑÅÔÓÑ ÏÔÄÅÌØÎÏ × ËÁÖÄÏÍ + ÈÕËÅ (hook), ÞÔÏ ÄÅÌÁÅÔ ÐÒÏÃÅÓÓ ÂÏÌÅÅ ÇÉÂËÉÍ É ËÏÎÆÉÇÕÒÉÒÕÅÍÙÍ. + ôÁËÖÅ ÂÙÌÉ ÄÏÂÁ×ÌÅÎÙ ÎÏ×ÙÅ ÆÕÎËÃÉÉ, ËÏÔÏÒÙÅ + ÐÒÅÄÏÓÔÁ×ÌÑÀÔ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÍÏÄÕÌÅÊ, + ÉÚÂÁ×ÌÑÑ ÏÔ ÎÅÏÂÈÏÄÉÍÏÓÔÉ ×ÎÅÓÅÎÉÑ ËÁËÉÈ-ÌÉÂÏ ÉÚÍÅÎÅÎÉÊ × ÑÄÒÏ + ÓÅÒ×ÅÒÁ.
+ +
ðÏÄÄÅÒÖËÁ ÐÒÏÔÏËÏÌÁ IPv6
+ +
÷ ÓÉÓÔÅÍÁÈ, ÇÄÅ ÐÒÏÔÏËÏÌ IPv6 ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ + ÎÉÖÅÌÅÖÁÝÅÊ ÂÉÂÌÉÏÔÅËÏÊ Apache Portable Runtime, Apache + ÐÏ ÕÍÏÌÞÁÎÉÀ ÐÏÌÕÞÁÅÔ ×ÏÚÍÏÖÎÏÓÔØ ÓÌÕÛÁÔØ IPv6 ÓÏËÅÔÙ. + ÷ ÄÏÂÁ×ÏË Ë ÜÔÏÍÕ ÄÉÒÅËÔÉ×Ù Listen, NameVirtualHost É VirtualHost ÍÏÇÕÔ ÒÁÂÏÔÁÔØ Ó ÁÄÒÅÓÎÙÍÉ ÓÔÒÏËÁÍÉ, + ÚÁÄÁÎÎÙÍÉ × ÆÏÒÍÁÔÅ IPv6 (Ô.Å. ÎÁÐÒÉÍÅÒ "Listen [2001:db8::1]:8080").
+ +
éÓÐÏÌØÚÏ×ÁÎÉÅ ÆÉÌØÔÒÏ×
+ +
íÏÄÕÌÉ Apache ÔÅÐÅÒØ ÍÏÖÎÏ ÎÁÐÉÓÁÔØ ÔÁË, ÞÔÏ + ÏÎÉ ÂÕÄÕÔ ÉÓÐÏÌÎÑÔØ ÒÏÌØ ÆÉÌØÔÒÏ×, + ÏÂÒÁÂÁÔÙ×ÁÀÝÉÈ ÐÏÔÏËÉ ÄÁÎÎÙÈ, ËÏÔÏÒÙÅ ÐÒÉÈÏÄÑÔ ÉÌÉ ÕÈÏÄÑÔ + ÉÚ ÓÅÒ×ÅÒÁ. üÔÏ ÐÏÚ×ÏÌÑÅÔ, Ë ÐÒÉÍÅÒÕ, ÄÁÎÎÙÍ, Ñ×ÌÑÀÝÉÍÓÑ + ÒÅÚÕÌØÔÁÔÏÍ ÒÁÂÏÔÙ CGI-ÓËÒÉÐÔÁ, ÂÙÔØ ÏÂÒÁÂÏÔÁÎÎÙÍÉ SSI + ÆÉÌØÔÒÏÍ INCLUDES, ÐÒÅÄÏÓÔÁ×ÌÑÅÍÙÍ ÍÏÄÕÌÅÍ + mod_include. íÏÄÕÌØ mod_ext_filter + ÐÏÚ×ÏÌÑÅÔ ×ÎÅÛÎÉÍ ÐÒÏÇÒÁÍÍÁÍ ÉÓÐÏÌÎÑÔØ ÒÏÌØ ÆÉÌØÔÒÏ× ÔÏÞÎÏ ÔÁËÉÍ ÖÅ ÏÂÒÁÚÏÍ, + ËÁËÉÍ CGI ÐÒÏÇÒÁÍÍÙ ÄÅÊÓÔ×ÕÀÔ × ËÁÞÅÓÔ×Å ÏÂÒÁÂÏÔÞÉËÏ× (handlers).
+ +
óÏÏÂÝÅÎÉÑ ÏÂ ÏÛÉÂËÁÈ ÎÁ ÒÁÚÎÙÈ ÑÚÙËÁÈ
+ +
óÏÏÂÝÅÎÉÑ Ï ÏÛÉÂËÁÈ, ÐÏÓÙÌÁÅÍÙÅ ÂÒÁÕÚÅÒÕ, ÔÅÐÅÒØ + ÐÒÅÄÓÔÁ×ÌÅÎÙ ÎÁ ÎÅÓËÏÌØËÉÈ ÑÚÙËÁÈ É ÉÓÐÏÌØÚÕÀÔ SSI + ÔÅÈÎÏÌÏÇÉÀ. ïÎÉ ÍÏÇÕÔ ÂÙÔØ ÌÅÇËÏ ÏÔÒÅÄÁËÔÉÒÏ×ÁÎÙ + ÁÄÍÉÎÉÓÔÒÁÔÏÒÏÍ ÐÏÄ Ó×ÏÉ ÎÕÖÄÙ.
+ +
õÐÒÏÝÅÎÎÁÑ ËÏÎÆÉÇÕÒÁÃÉÑ
+ +
íÎÏÇÉÅ ÚÁÐÕÔÁÎÎÙÅ ÄÉÒÅËÔÉ×Ù ÂÙÌÉ ÕÐÒÏÝÅÎÙ. îÁÉÂÏÌÅÅ + ÓÂÉ×ÁÀÝÉÅ Ó ÔÏÌËÕ Port É BindAddress ÂÙÌÉ ÕÂÒÁÎÙ; + ÄÌÑ ÐÒÉ×ÑÚËÉ Ë IP ÁÄÒÅÓÕ ÉÓÐÏÌØÚÕÅÔÓÑ ÔÏÌØËÏ ÄÉÒÅËÔÉ×Á + Listen; ÄÉÒÅËÔÉ×Á + ServerName ÏÐÒÅÄÅÌÑÅÔ ÉÍÑ ÓÅÒ×ÅÒÁ É ÎÏÍÅÒ ÐÏÒÔÁ + ÔÅÐÅÒØ ÔÏÌØËÏ ÄÌÑ ÐÅÒÅÎÁÐÒÁ×ÌÅÎÉÊ É ÒÁÂÏÔÙ Ó ×ÉÒÔÕÁÌØÎÙÍÉ ÈÏÓÔÁÍÉ.
+ +
ðÏÄÄÅÒÖËÁ ÀÎÉËÏÄÁ Windows NT
+ +
Apache 2.0 ÎÁ Windows NT ÔÅÐÅÒØ ÉÓÐÏÌØÚÕÅÔ ËÏÄÉÒÏ×ËÕ utf-8 + ÄÌÑ ÒÁÂÏÔÙ Ó ÉÍÅÎÁÍÉ ÆÁÊÌÏ×. üÔÏ ÐÏÚ×ÏÌÑÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ + ÎÉÖÅÌÅÖÁÝÕÀ ÆÁÊÌÏ×ÕÀ ÓÉÓÔÅÍÕ, ÒÁÂÏÔÁÀÝÕÀ × ÆÏÒÍÁÔÅ Unicode, + ÞÔÏ ÐÒÅÄÏÓÔÁ×ÌÑÅÔ ÐÏÄÄÅÒÖËÕ ÓÅÒ×ÅÒÏÍ ÍÎÏÇÏÑÚÙÞÎÏÓÔÉ ÄÌÑ ×ÓÅÈ NT- + ÓÉÓÔÅÍ, ×ËÌÀÞÁÑ Windows 2000 É Windows XP. + üÔÏ ÎÅ ÒÁÓÐÒÏÓÔÒÁÎÑÅÔÓÑ ÎÁ ÔÁËÉÅ ÏÐÅÒÁÃÉÏÎÎÙÅ ÓÉÓÔÅÍÙ, ËÁË + Windows 95, 98 ÉÌÉ ME, ËÏÔÏÒÙÅ ÄÌÑ ÏÂÒÁÝÅÎÉÑ Ë ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÅ + ÉÓÐÏÌØÚÕÀÔ ÌÏËÁÌØÎÙÅ ËÏÄÏ×ÙÅ ÓÔÒÁÎÉÃÙ.
+ +
îÏ×ÁÑ ÂÉÂÌÉÏÔÅËÁ ÄÌÑ ÒÁÂÏÔÙ Ó ÒÅÇÕÌÑÒÎÙÍÉ ×ÙÒÁÖÅÎÉÑÍÉ
+ +
÷ ÓÏÓÔÁ× Apache 2.0 ÂÙÌÁ ×ËÌÀÞÅÎÁ + ÂÉÂÌÉÏÔÅËÁ ÄÌÑ ÒÁÂÏÔÙ Ó Perl-ÓÏ×ÍÅÓÔÉÍÙÍÉ ÒÅÇÕÌÑÒÎÙÍÉ ×ÙÒÁÖÅÎÑÍÉ (PCRE). + ÷ÓÅ ÒÅÇÕÌÑÒÎÙÅ ×ÙÒÁÖÅÎÉÑ ÔÅÐÅÒØ ÉÓÐÏÌØÚÕÀÔ ÂÏÌÅÅ ÍÏÝÎÙÊ ÓÉÎÔÁËÓÉÓ Perl 5.
+ +
+
top
+
+

õÌÕÞÛÅÎÉÑ × ÍÏÄÕÌÑÈ ÓÅÒ×ÅÒÁ

+ + +
+
mod_ssl
+ +
îÏ×ÙÊ ÍÏÄÕÌØ × Apache 2.0. üÔÏÔ ÍÏÄÕÌØ Ñ×ÌÑÅÔÓÑ ÉÎÔÅÒÆÅÊÓÏÍ + Ë ÐÒÏÔÏËÏÌÁÍ ÛÉÆÒÏ×ÁÎÉÑ SSL/TLS, ÐÒÅÄÏÓÔÁ×ÌÑÅÍÙÍÉ OpenSSL.
+ +
mod_dav
+ +
îÏ×ÙÊ ÍÏÄÕÌØ × Apache 2.0. üÔÏÔ ÍÏÄÕÌØ ×ÎÅÄÒÑÅÔ ÓÐÅÃÉÆÉËÁÃÉÀ + Distributed Authoring and Versioning (DAV), ÐÏÚ×ÏÌÑÀÝÕÀ ÕÐÒÁ×ÌÑÔØ + ÓÏÄÅÒÖÉÍÙÍ ÓÁÊÔÁ ÐÏÓÒÅÄÓÔ×ÏÍ ÒÁÓÛÉÒÅÎÎÏÇÏ ÐÒÏÔÏËÏÌÁ HTTP.
+ +
mod_deflate
+ +
îÏ×ÙÊ ÍÏÄÕÌØ × Apache 2.0. üÔÏÔ ÍÏÄÕÌØ ÐÏÚ×ÏÌÑÅÔ ÂÒÁÕÚÅÒÁÍ, ÐÏÄÄÅÒÖÉ×ÁÀÝÉÍ + ÄÁÎÎÕÀ ÔÅÈÎÏÌÏÇÉÀ, ÚÁÐÒÁÛÉ×ÁÔØ ÄÁÎÎÙÅ × ÓÖÁÔÏÍ ×ÉÄÅ, ÞÔÏ ÓÏËÒÁÝÁÅÔ ÎÁÇÒÕÚËÕ ÎÁ + ÓÅÔØ.
+ +
mod_auth_ldap
+ +
îÏ×ÙÊ ÍÏÄÕÌØ × Apache 2.0.41. üÔÏÔ ÍÏÄÕÌØ ÐÏÚ×ÏÌÑÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÂÁÚÕ ÄÁÎÎÙÈ LDAP + ÄÌÑ ÈÒÁÎÅÎÉÑ ÉÍÅÎ É ÐÁÒÏÌÅÊ ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ÎÅÏÂÈÏÄÉÍÙÈ ÐÒÉ ÁÕÔÅÎÔÉÆÉËÁÃÉÉ ÐÏ ÍÅÔÏÄÕ + Basic. óÏÐÕÔÓÔ×ÕÀÝÉÊ ÅÍÕ ÍÏÄÕÌØ mod_ldap ÏÂÅÓÐÅÞÉ×ÁÅÔ ×ÏÚÍÏÖÎÏÓÔØ + ÓÏÚÄÁÎÉÑ ÏÞÅÒÅÄÅÊ ÐÏÄËÌÀÞÅÎÉÊ (connection pools) É ËÜÛÉÒÏ×ÁÎÉÑ ÒÅÚÕÌØÔÁÔÏ×.
+ +
mod_auth_digest
+ +
÷ËÌÀÞÁÅÔ ÄÏÐÏÌÎÉÔÅÌØÎÕÀ ÐÏÄÄÅÒÖËÕ ËÜÛÉÒÏ×ÁÎÉÑ ÓÅÓÓÉÊ + ÐÒÏÃÅÓÓÁÍÉ, ÂÌÁÇÏÄÁÒÑ ÉÓÐÏÌØÚÏ×ÁÎÉÀ ÏÂÝÅÊ ÏÂÌÁÓÔÉ ÐÁÍÑÔÉ (ÒÁÚÄÅÌÅÎÉÀ + ÐÁÍÑÔÉ).
+ +
mod_charset_lite
+ +
îÏ×ÙÊ ÍÏÄÕÌØ × Apache 2.0. üÔÏÔ ÜËÓÐÅÒÉÍÅÎÔÁÌØÎÙÊ ÍÏÄÕÌØ ÐÏÚ×ÏÌÑÅÔ + ÏÓÕÝÅÓÔ×ÌÑÔØ ÐÅÒÅ×ÏÄ ÉÚ ÏÄÎÏÇÏ ÎÁÂÏÒÁ ÓÉÍ×ÏÌÏ× (character set) × ÄÒÕÇÏÊ É ÉÚ ÏÄÎÏÊ + ËÏÄÉÒÏ×ËÉ × ÄÒÕÇÕÀ.
+ +
mod_file_cache
+ +
îÏ×ÙÊ ÍÏÄÕÌØ × Apache 2.0. üÔÏÔ ÍÏÄÕÌØ ×ËÌÀÞÁÅÔ × ÓÅÂÑ + ÆÕÎËÃÉÏÎÁÌØÎÏÓÔØ ÍÏÄÕÌÑ mod_mmap_static ÉÚ Apache 1.3 + ÐÌÀÓ ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ ËÜÛÉÒÏ×ÁÎÉÑ.
+ +
mod_headers
+ +
üÔÏÔ ÍÏÄÕÌØ ÓÔÁÌ ÂÏÌÅÅ ÇÉÂËÉÍ × Apache 2.0. ïÎ ÐÏÚ×ÏÌÑÅÔ + ÍÏÄÉÆÉÃÉÒÏ×ÁÔØ ÚÁÇÏÌÏ×ËÉ ÚÁÐÒÏÓÏ×, ÉÓÐÏÌØÚÕÅÍÙÈ ÍÏÄÕÌÅÍ + mod_proxy, É ÍÏÖÅÔ ×ËÌÀÞÁÔØ × ÏÔ×ÅÔ ÓÅÒ×ÅÒÁ ÚÁÇÏÌÏ×ËÉ × + ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÒÁÚÌÉÞÎÙÈ ÕÓÌÏ×ÉÊ.
+ +
mod_proxy
+ +
ðÒÏËÓÉ ÍÏÄÕÌØ ÂÙÌ ÐÏÌÎÏÓÔØÀ ÐÅÒÅÐÉÓÁÎ, É ÔÅÐÅÒØ ×ËÌÀÞÁÅÔ + × ÓÅÂÑ ÐÒÅÉÍÕÝÅÓÔ×Á ÎÏ×ÏÊ ÆÉÌØÔÒÏ×ÏÊ ÉÎÆÒÁÓÔÒÕËÔÕÒÙ É ÉÓÐÏÌØÚÕÅÔ + ÂÏÌÅÅ ÎÁÄÅÖÎÕÀ, ÓÏ×ÍÅÓÔÉÍÕÀ Ó HTTP/1.1 ÐÒÏËÓÉ-ÔÅÈÎÏÌÏÇÉÀ. ÷ ÄÏÂÁ×ÏË + Ë ÜÔÏÍÕ ÂÙÌÁ ××ÅÄÅÎÁ ÎÏ×ÁÑ ÓÅËÃÉÑ <Proxy>, ËÏÔÏÒÕÀ ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ × ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÁÈ, ÞÔÏ + ÏÂÅÓÐÅÞÉ×ÁÅÔ ÂÏÌÅÅ ÕÄÏÂÎÙÊ (É ÂÏÌÅÅ ÂÙÓÔÒÙÊ ÄÌÑ ÑÄÒÁ ÓÅÒ×ÅÒÁ) ËÏÎÔÒÏÌØ ÎÁÄ ÓÁÊÔÁÍÉ, + ÉÓÐÏÌØÚÕÀÝÉÍÉ proxy-ÔÅÈÎÏÌÏÇÉÀ. ðÅÒÅÇÒÕÖÅÎÎÁÑ ËÏÎÆÉÇÕÒÁÃÉÑ <Directory "proxy:..."> + ÂÏÌÅÅ ÎÅ ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ. íÏÄÕÌØ ÔÅÐÅÒØ ÒÁÚÄÅÌÅÎ ÎÁ ÏÔÄÅÌØÎÙÅ ÓÐÅÃÉÆÉÞÎÙÅ ÍÏÄÕÌÉ, + ÐÏÄÄÅÒÖÉ×ÁÀÝÉÅ ÒÁÚÌÉÞÎÙÅ ÐÒÏÔÏËÏÌÙ. üÔÉ ÍÏÄÕÌÉ ×ËÌÀÞÁÀÔ × ÓÅÂÑ proxy_connect, proxy_ftp + É proxy_http.
+ +
mod_negotiation
+ +
äÏÂÁ×ÌÅÎÁ ÎÏ×ÁÑ ÄÉÒÅËÔÉ×Á ForceLanguagePriority, ÄÌÑ ÔÏÇÏ ÞÔÏÂÙ ×ÍÅÓÔÏ ÏÔ×ÅÔÏ× ÓÅÒ×ÅÒÁ + NOT ACCEPTABLE ÉÌÉ MULTIPLE CHOICES ×ÓÅÇÄÁ ÐÒÅÄÏÓÔÁ×ÌÑÔØ ÐÏÌØÚÏ×ÁÔÅÌÀ + ÏÐÒÅÄÅÌÅÎÎÙÊ ÄÏËÕÍÅÎÔ. ÷ ÄÏÐÏÌÎÅÎÉÅ Ë ÜÔÏÍÕ ÁÌÇÏÒÉÔÍÙ + ÎÅÇÏÃÉÁÃÉÉ (negotiation) É MultiViews ÂÙÌÉ ×ÙÞÉÝÅÎÙ É ÉÓÐÒÁ×ÌÅÎÙ, ÄÌÑ + ÏÂÅÓÐÅÞÅÎÉÑ ÂÏÌÅÅ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÇÏ ÒÅÚÕÌØÔÁÔÁ, Á ÔÁËÖÅ ÐÏÑ×ÉÌÁÓØ ×ÏÚÍÏÖÎÏÓÔØ + ×ËÌÀÞÅÎÉÑ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ ÓÏÄÅÒÖÉÍÏÇÏ ÄÏËÕÍÅÎÔÏ× × ËÁÒÔÕ ÔÉÐÏ× (type map).
+ +
mod_autoindex
+ +
ìÉÓÔÉÎÇÉ Á×ÔÏÉÎÄÅËÓÉÒÕÅÍÙÈ ËÁÔÁÌÏÇÏ× ÔÅÐÅÒØ ÍÏÇÕÔ ×ÙÄÁ×ÁÔØÓÑ × ×ÉÄÅ + HTML-ÔÁÂÌÉÃ. ðÏÑ×ÉÌÁÓØ ×ÏÚÍÏÖÎÏÓÔØ ÂÏÌÅÅ ÇÉÂËÏÊ ÓÏÒÔÉÒÏ×ËÉ, ×ËÌÀÞÁÑ ÓÏÒÔÉÒÏ×ËÕ ÐÏ ×ÅÒÓÉÑÍ É + ÓÏÒÔÉÒÏ×ËÕ Ó ÉÓÐÏÌØÚÏ×ÁÎÉÅÍ ÛÁÂÌÏÎÎÙÈ ÓÉÍ×ÏÌÏ× (wildcard).
+ +
mod_include
+ +
÷×ÅÄÅÎÙ ÎÏ×ÙÅ ÄÉÒÅËÔÉ×Ù, ËÏÔÏÒÙÅ ÐÏÚ×ÏÌÑÀÔ ÉÚÍÅÎÉÔØ ÎÁÞÁÌØÎÙÊ É ËÏÎÅÞÎÙÊ + ÔÅÇÉ SSI ÜÌÅÍÅÎÔÏ×, ÚÁÄÁ×ÁÅÍÙÅ ÐÏ ÕÍÏÌÞÁÎÉÀ, Á ÔÁËÖÅ ÐÒÅÄÏÓÔÁ×ÌÑÀÔ ×ÏÚÍÏÖÎÏÓÔØ + ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÑ ÆÏÒÍÁÔÁ ÓÏÏÂÝÅÎÉÊ Ï ÏÛÉÂËÁÈ É ×ÒÅÍÅÎÉ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ + × ÇÌÁ×ÎÏÍ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÍ ÆÁÊÌÅ, Á ÎÅ × SSI ÄÏËÕÍÅÎÔÅ. òÅÚÕÌØÔÁÔÙ + ÏÂÒÁÂÏÔËÉ ÒÅÇÕÌÑÒÎÙÈ ×ÙÒÁÖÅÎÉÊ (ÔÅÐÅÒØ ÏÓÎÏ×Ù×ÁÀÝÉÈÓÑ ÎÁ ÓÉÎÔÁËÓÉÓÅ + ÒÅÇÕÌÑÒÎÙÈ ×ÙÒÁÖÅÎÉÊ ÑÚÙËÁ Perl) ÍÏÇÕÔ ÂÙÔØ ÐÏÌÕÞÅÎÙ ÐÒÉ ÐÏÍÏÝÉ ÐÅÒÅÍÅÎÎÙÈ + $0 .. $9 ÍÏÄÕÌÑ mod_include.
+ +
mod_auth_dbm
+ +
ôÅÐÅÒØ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÍÎÏÇÏÞÉÓÌÅÎÎÙÅ ÔÉÐÙ DBM-ÐÏÄÏÂÎÙÈ ÂÁÚ ÄÁÎÎÙÈ ÐÏÓÒÅÄÓÔ×ÏÍ + ÄÉÒÅËÔÉ×Ù AuthDBMType.
+ +
+
+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + fr  | + ja  | + ko  | + pt-br  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_2.html b/docs/manual/new_features_2_2.html new file mode 100644 index 00000000..b79e2041 --- /dev/null +++ b/docs/manual/new_features_2_2.html @@ -0,0 +1,11 @@ +URI: new_features_2_2.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: new_features_2_2.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: new_features_2_2.html.pt-br +Content-Language: pt-br +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/new_features_2_2.html.en b/docs/manual/new_features_2_2.html.en new file mode 100644 index 00000000..c5c37bfb --- /dev/null +++ b/docs/manual/new_features_2_2.html.en @@ -0,0 +1,272 @@ + + + +Overview of new features in Apache 2.2 - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Overview of new features in Apache 2.2

+
+

Available Languages:  en  | + ko  | + pt-br 

+
+ +

This document describes some of the major changes between the + 2.0 and 2.2 versions of the Apache HTTP Server. For new features since + version 1.3, see the 2.0 new features + document.

+
+ +
top
+
+

Core Enhancements

+ +
+ +
Authn/Authz
+
The bundled authentication and authorization modules have + been refactored. The new mod_authn_alias module + can greatly simplify certain authentication configurations. + See module name changes, and + the developer changes for more + information about how these changes affects users and module + writers.
+ +
Caching
+
mod_cache, mod_disk_cache, and + mod_mem_cache have undergone a lot of changes, and + are now considered production-quality. htcacheclean + has been introduced to clean up mod_disk_cache + setups.
+ +
Configuration
+
The default configuration layout has been simplified and + modularised. Configuration snippets which can be used to + enable commonly-used features are now bundled with Apache, and + can be easily added to the main server config.
+ +
Graceful stop
+
The prefork, worker and + event MPMs now allow httpd + to be shutdown gracefully via the + graceful-stop + signal. The GracefulShutdownTimeout directive + has been added to specify an optional timeout, after which + httpd will terminate regardless of the status + of any requests being served.
+ +
Proxying
+
The new mod_proxy_balancer module provides + load balancing services for mod_proxy. + The new mod_proxy_ajp module adds support for the + Apache JServ Protocol version 1.3 used by + Apache Tomcat.
+ +
Regular Expression Library Updated
+
Version 5.0 of the + Perl Compatible Regular Expression + Library (PCRE) is now included. httpd can be + configured to use a system installation of PCRE by passing the + --with-pcre flag to configure.
+ +
Smart Filtering
+
mod_filter introduces dynamic configuration + to the output filter chain. It enables filters to be conditionally + inserted, based on any Request or Response header or environment + variable, and dispenses with the more problematic dependencies and + ordering problems in the 2.0 architecture.
+ +
Large File Support
+ +
httpd is now built with support for files larger than 2GB on + modern 32-bit Unix systems. Support for handling >2GB request + bodies has also been added.
+ +
Event MPM
+
The event MPM uses a seperate thread to handle + Keep Alive requests and accepting connections. Keep Alive requests + have traditionally required httpd to dedicate a worker to handle it. + This dedicated worker could not be used again until the Keep Alive + timeout was reached.
+ +
SQL Database Support
+

mod_dbd, together with the apr_dbd framework, + brings direct SQL support to modules that need it. Supports + connection pooling in threaded MPMs.

+

Windows Users please note that this is not + yet included in the standard windows build. If you try to use + it on the Windows platform, please let us know how you get on.

+
+ +
+
top
+
+

Module Enhancements

+ +
+
Authn/Authz
+
Modules in the aaa directory have been renamed and offer + better support for digest authentication. For example, mod_auth + is now split into mod_auth_basic and + mod_authn_file; mod_auth_dbm is now called + mod_authn_dbm; mod_access has been renamed + mod_authz_host. There is also a new + mod_authn_alias module for simplifying + certain authentication configurations. +
+ +
mod_authnz_ldap
+
This module is a port of the 2.0 + mod_auth_ldap module to the 2.2 Authn/Authz + framework. New features include using LDAP attribute values and + complicated search filters in the + Require directive.
+ +
mod_authz_owner
+
A new module that authorizes access to files based + on the owner of the file on the file system
+ +
mod_version
+
A new module that allows configuration blocks to be enabled based on the + version number of the running server.
+ +
mod_info
+
Added a new ?config argument which will show + the configuration directives as parsed by Apache, including + their file name and line number. The module also + shows the order of all request hooks and additional + build information, similar to httpd -V.
+ +
mod_ssl
+ +
Added a support for + RFC 2817, which + allows connections to upgrade from clear text to TLS encryption.
+ +
mod_imagemap
+
mod_imap has been renamed to mod_imagemap to avoid + user confusion.
+
+ +
top
+
+

Program Enhancements

+ +
+
httpd
+
A new command line option -M has been added that + lists all modules that are loaded based on the current + configuration. Unlike the -l option, this list + includes DSOs loaded via mod_so.
+
httxt2dbm
+
A new program used to generate dbm files from text input, + for use in RewriteMap + with the dbm map type.
+
+
top
+
+

Module Developer Changes

+ +
+
APR 1.0 API
+ +
Apache 2.2 uses the APR 1.0 API. All deprecated functions and + symbols have been removed from APR and + APR-Util. For details, see the + APR Website.
+ +
Authn/Authz
+
The bundled authentication and authorization modules have + been renamed along the following lines: +
    +
  • mod_auth_* -> Modules that implement an HTTP authentication mechanism
    • +
  • mod_authn_* -> Modules that provide a backend authentication provider
    • +
  • mod_authz_* -> Modules that implement authorization (or access)
    • +
  • mod_authnz_*-> Module that implements both authentication & authorization
    • +
+ There is a new authentication backend provider + scheme which greatly eases the construction of new authentication + backends.
+ +
Connection Error Logging
+ +
A new function, ap_log_cerror has been added to log + errors that occur with the client's connection. When logged, + the message includes the client IP address.
+ +
Test Configuration Hook Added
+ +
A new hook, test_config has been added to aid + modules that want to execute special code only when the user passes + -t to httpd.
+ +
Set Threaded MPM's Stacksize
+ +
A new directive, ThreadStackSize has been added to + set the stack size on all threaded MPMs. This is required + for some third-party modules on platforms with small default + thread stack size.
+ +
Protocol handling for output filters
+ +
In the past, every filter has been responsible for ensuring + that it generates the correct response headers where it affects + them. Filters can now delegate common protocol management to + mod_filter, using the + ap_register_output_filter_protocol or + ap_filter_protocol calls.
+ +
Monitor hook added
+
Monitor hook enables modules to run regular/scheduled jobs + in the parent (root) process.
+ +
Regular expression API changes
+ +
The pcreposix.h header is no longer available; + it is replaced by the new ap_regex.h header. The + POSIX.2 regex.h implementation exposed by the old + header is now available under the ap_ namespace + from ap_regex.h. Calls to regcomp, + regexec and so on can be replaced by calls to + ap_regcomp, ap_regcomp.
+ +
DBD Framework (SQL Database API)
+ +

With Apache 1.x and 2.0, modules requiring an SQL backend + had to take responsibility for managing it themselves. Apart + from reinventing the wheel, this can be very inefficient, for + example when several modules each maintain their own connections.

+

Apache 2.1 and later provides the ap_dbd API for + managing database connections (including optimised strategies + for threaded and unthreaded MPMs), while APR 1.2 and later provides + the apr_dbd API for interacting with the database.

+

New modules SHOULD now use these APIs for all SQL database + operations. Existing applications SHOULD be upgraded to use it + where feasible, either transparently or as a recommended option + to their users.

+
+
+
+

Available Languages:  en  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_2.html.ko.euc-kr b/docs/manual/new_features_2_2.html.ko.euc-kr new file mode 100644 index 00000000..2c62870c --- /dev/null +++ b/docs/manual/new_features_2_2.html.ko.euc-kr @@ -0,0 +1,126 @@ + + + +¾ÆÆÄÄ¡ 2.2ÀÇ »õ·Î¿î ±â´É °³¿ä - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¾ÆÆÄÄ¡ 2.2ÀÇ »õ·Î¿î ±â´É °³¿ä

+
+

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

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

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ À¥¼­¹ö 2.0 ¹öÀü°ú 2.2 ¹öÀü°£ÀÇ ÁÖµÈ Â÷ÀÌÁ¡À» + ¼³¸íÇÑ´Ù. 1.3 ¹öÀü ÀÌÈÄÀÇ »õ·Î¿î ±â´ÉÀº 2.0 »õ·Î¿î ±â´É ¹®¼­¸¦ + Âü°íÇ϶ó.

+
+ +
top
+
+

ÇÙ½É ºÎºÐ¿¡¼­ ³ª¾ÆÁø Á¡

+ +
+ +
Authn/Authz
+
...
+ +
ij½¬
+
...
+ +
ÇÁ·Ï½Ã
+
»õ·Î¿î mod_proxy_balancer ¸ðµâÀÌ + mod_proxy¸¦ À§ÇÑ ºÎÇÏºÐ»ê ¼­ºñ½º¸¦ Á¦°øÇÑ´Ù. + »õ·Î¿î mod_proxy_ajp ¸ðµâÀº ¾ÆÆÄÄ¡ ÅèĹÀÌ + »ç¿ëÇÏ´Â Apache JServ Protocol 1.3 ¹öÀüÀ» + Áö¿øÇÑ´Ù.
+ +
¶È¶ÈÇÑ ÇÊÅÍ
+
mod_filter´Â Ãâ·ÂÇÊÅͼø¼­¸¦ µ¿ÀûÀ¸·Î + ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ±×·¡¼­ ¿äû Çì´õ, ÀÀ´ä Çì´õ, ȯ°æº¯¼ö¿¡ + µû¶ó ¼±ÅÃÀûÀ¸·Î ÇÊÅ͸¦ »ç¿ëÇÒ ¼ö ÀÖ°í, 2.0 ±¸Á¶ÀÇ Àǽɽº·¯¿î + ÀÇÁ¸°ü°è¿Í ¼ø¼­ ¹®Á¦¸¦ ´ú¾îÁØ´Ù.
+ +
+
top
+
+

¸ðµâ¿¡¼­ ³ª¾ÆÁø Á¡

+ +
+
mod_authnz_ldap
+
ÀÌ ¸ðµâÀº 2.0ÀÇ mod_auth_ldap ¸ðµâÀ» + 2.2ÀÇ Authn/Authz ±¸Á¶·Î ¿Å±ä °ÍÀÌ´Ù. Require Áö½Ã¾î¿¡¼­ LDAP + ¼Ó¼º(attribute) °ª°ú º¹ÀâÇÑ °Ë»ö ÇÊÅ͸¦ »ç¿ëÇÒ ¼ö ÀÖ´Â + ±â´ÉÀÌ Ãß°¡µÇ¾ú´Ù.
+ +
mod_info
+
¾ÆÆÄÄ¡°¡ ÀоîµéÀÎ ¼³Á¤Áö½Ã¾î¸¦ ÆÄÀϸí°ú ÁÙ¹øÈ£¿Í °°ÀÌ + º¸¿©ÁÖ´Â ?config ¾Æ±Ô¸ÕÆ®°¡ Ãß°¡µÇ¾ú´Ù. ¸ðµâÀº + ¸ðµç ¿äû ÈÅ(hook)ÀÇ ¼ø¼­¿Í httpd -V¿Í ºñ½ÁÇÑ + ÄÄÆÄÀÏ Á¤º¸µµ º¸¿©ÁØ´Ù.
+
+
top
+
+

¸ðµâ °³¹ßÀÚ¿¡°Ô ´Þ¶óÁø Á¡

+ +
+
APR 1.0 API
+ +
¾ÆÆÄÄ¡ 2.2´Â APR 1.0 API¸¦ »ç¿ëÇÑ´Ù. APR°ú + APR-Util¿¡¼­ ¾ø¾îÁö±â·Î ¿¹Á¤µÇ¾ú´ø ÇÔ¼ö¿Í + ½Éº¼ÀÌ ¸ðµÎ ¾ø¾îÁ³´Ù. ÀÚ¼¼ÇÑ ³»¿ëÀº APR À¥»çÀÌÆ®¸¦ Âü°íÇ϶ó.
+ +
¿¬°á ¿À·ù ·Î±× ±â·Ï
+ +
Ŭ¶óÀ̾ðÆ®¿Í ¿¬°á¿¡ ¹ß»ýÇÑ ¿À·ù¸¦ ·Î±×¿¡ ±â·ÏÇϱâÀ§ÇØ + ÇÔ¼ö ap_log_cerror¸¦ »õ·Î Ãß°¡Çß´Ù. ·Î±×¿¡ + ±â·ÏÇÏ¸é ¹®±¸¿¡ Ŭ¶óÀ̾ðÆ® IP ÁÖ¼Ò°¡ ³ª¿Â´Ù.
+ +
¼³Á¤ Å×½ºÆ®¿ë ÈÅ Ãß°¡
+ +
»ç¿ëÀÚ°¡ httpd¿¡ -t ¿É¼ÇÀ» »ç¿ëÇÑ °æ¿ì¿¡¸¸ + ¸ðµâÀÌ Æ¯º°ÇÑ Äڵ带 ½ÇÇàÇϵµ·Ï ÈÅ test_config¸¦ + »õ·Î Ãß°¡Çß´Ù.
+ +
¾²·¹µå±â¹Ý MPMÀÇ ½ºÅÃÅ©±â ÁöÁ¤
+ +
¸ðµç ¾²·¹µå±â¹Ý MPMÀÇ ½ºÅÃÅ©±â¸¦ ÁöÁ¤ÇϱâÀ§ÇØ + ThreadStackSize Áö½Ã¾î¸¦ »õ·Î Ãß°¡Çß´Ù. ¾²·¹µå + ½ºÅÃÅ©±â ±âº»°ªÀÌ ÀÛÀº Ç÷¹Æû¿¡¼­ ÀϺΠÁ¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀ» + »ç¿ëÇÒ °æ¿ì¿¡ ÇÊ¿äÇÏ´Ù.
+ +
Ãâ·ÂÇÊÅ͸¦ À§ÇÑ ÇÁ·ÎÅäÄÝ Ã³¸®
+ +
Àü¿¡´Â ¸ðµç ÇÊÅÍ¿¡°Ô ÀÚ½ÅÀÌ Ã³¸®ÇÑ ÀÀ´ä¿¡ ¿Ã¹Ù¸¥ ÀÀ´ä + Çì´õ¸¦ »ý¼ºÇÏ´ÂÁö È®ÀÎÇÒ Ã¥ÀÓÀÌ ÀÖ¾ú´Ù. ÀÌÁ¦ ÇÊÅÍ´Â + ap_register_output_filter_protocol ȤÀº + ap_filter_protocol È£ÃâÀ» »ç¿ëÇÏ¿© ÀÏ»óÀûÀÎ + ÇÁ·ÎÅäÄÝ °ü¸®¸¦ mod_filter¿¡°Ô ¶°³Ñ±æ + ¼ö ÀÖ´Ù.
+
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/new_features_2_2.html.pt-br b/docs/manual/new_features_2_2.html.pt-br new file mode 100644 index 00000000..1c105ed9 --- /dev/null +++ b/docs/manual/new_features_2_2.html.pt-br @@ -0,0 +1,135 @@ + + + +Descrição das novas funcionalidades do Apache 2.2 - Servidor HTTP Apache + + + + +
+

Módulos | Diretrizes | FAQ | Glossário | Mapa do site

+

Servidor HTTP Apache Versão 2.2

+
+
<-
+
+Apache > Servidor HTTP > Documentação > Versão 2.2

Descrição das novas funcionalidades do Apache 2.2

+
+

Línguas Disponíveis:  en  | + ko  | + pt-br 

+
+
Esta tradução pode estar desatualizada. + Verifique a versão em Inglês para mudanças recentes.
+ +

Esse documento descreve algumas das principais mudanças + entre as versões 2.0 e 2.2 do Servidor HTTP Apache. + Para a lista de mudanças desde a versão 1.3, veja a página + de documentação novas funcionalidades + do Apache 2.0.

+
+ +
top
+
+

Principais Melhorias

+ +
+ +
Authn/Authz
+
...
+ +
Caching
+
...
+ +
Proxying
+
O novo módulo mod_proxy_balancer fornece + serviços de carregamento de balenceamento para mod_proxy. O novo módulo mod_proxy_ajp oferece suporte para o Protocolo Apache JServ + versão 1.3, usado pelo Apache Tomcat.
+ +
Filtragem Inteligente (Smart Filtering)
+
O mod_filter introduz configuração dinâmica para + o filtro de saída de dados. Permitindo que os filtros sejam + condicionalmente inseridos, baseando-se nos cabeçalhos Request ou Response ou em variáveis do + ambiente, ele acaba com os problemas de dependências e pedidos + da arquitetura 2.0.
+ +
+
top
+
+

Melhorias nos Módulos

+ +
+
mod_authnz_ldap
+
Este módulo é uma migração do mod_auth_ldap, + da versão 2.0 para a estrutura 2.2 de Authn/Authz. + As novas funcionalidades incluem o uso de atributos LDAP e + filtros de procura complexos na diretriz Require.
+ +
mod_info
+
Adicionado um novo argumento ?config que + mostra a configuração das diretrizes analisadas pelo + Apache, incluindo o nome do arquivo e o número da linha. + Esse módulo também mostra a ordem de todos os ganchos de + pedidos (request hooks) e informações adicionais sobre + a compilação, similar ao comando httpd -V.
+
+
top
+
+

Mudanças ao Desenvolvedor de Módulos

+ +
+
API do APR 1.0
+ +
O Apache 2.2 utiliza a API do APR 1.0. Todas as funções e + símbolos antigos foram removidos do APR e + APR-Util. Para mais detalhes, visite o + Website do APR.
+ +
Registros de Erros de Conexão (logs)
+ +
Uma nova função ap_log_cerror, foi adicionada + para registrar erros que ocorrem na conexão do cliente. + Quando documentado no diário de log, a mensagem inclui o + endereço IP do cliente.
+ +
Adicionado Gancho de Teste de Configuração
+ +
Um novo gancho (hook), test_config foi + adicionado para auxiliar módulos que querem executar + códigos especiais apenas quando o usuário passa o + parâmetro -t para o httpd.
+ +
Ajustar o Stacksize dos "Threaded MPM's"
+ +
Uma nova diretriz chamada ThreadStackSize, + foi adicionada para ajustar o tamanho das stacks em todos + os threadeds MPMs. Essa é uma prática necessário para alguns + módulos de terceiros em plataformas com tamanhos de stacks + pequenos por padrão.
+ +
Negociação de Protocolo para filtros de saída
+ +
No passado, todo filtro era responsável por garantir + a geração de cabeçalhos de resposta correto que os afetava. + Os filtros agora podem delegar o gerenciamento de protocolos + comuns para mod_filter, usando chamadas + de ap_register_output_filter_protocol ou + ap_filter_protocol.
+ +
+ +
+
+

Línguas Disponíveis:  en  | + ko  | + pt-br 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/ebcdic.html b/docs/manual/platform/ebcdic.html new file mode 100644 index 00000000..f9b208e4 --- /dev/null +++ b/docs/manual/platform/ebcdic.html @@ -0,0 +1,7 @@ +URI: ebcdic.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: ebcdic.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/ebcdic.html.en b/docs/manual/platform/ebcdic.html.en new file mode 100644 index 00000000..c2a9443c --- /dev/null +++ b/docs/manual/platform/ebcdic.html.en @@ -0,0 +1,584 @@ + + + +The Apache EBCDIC Port - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

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. +
+ +
+ +
top
+
+

Overview of the 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 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.

+ +
top
+
+

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.

+ +
top
+
+

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)
    • +
+ +
top
+
+

Porting Notes

+ + + +
    +
  1. +

    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.

    +
    +
    +
    2. + +
  2. +

    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)

    +
    3. + +
  3. +

    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.

    +
    4. + +
  4. +

    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.

    +
    5. + +
  5. +

    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.

    +
    6. + +
  6. +

    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.

    +
    7. + +
  7. +

    Server parsed files are always assumed to be in native + (i.e., EBCDIC) format as used on the machine, and + are converted after processing.

    +
    8. + +
  8. +

    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.

    +
    9. + +
+ +
top
+
+

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.

+ + + +
top
+
+

Apache Modules' Status

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ModuleStatusNotes
core+ +
mod_access+ +
mod_actions+ +
mod_alias+ +
mod_asis+ +
mod_auth+ +
mod_auth_anon+ +
mod_auth_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
+ +
top
+
+

Third Party Modules' Status

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ModuleStatusNotes
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 00000000..c7b2b5ad --- /dev/null +++ b/docs/manual/platform/ebcdic.html.ko.euc-kr @@ -0,0 +1,559 @@ + + + +¾ÆÆÄÄ¡ EBCDIC Æ÷Æà - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ

+
+

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

+
+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.
+ + +
ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ À¥¼­¹ö 2.0 ¹öÀü¿¡¼­ + º¯°æµÈ ³»¿ëÀ» ´ã°íÀÖÁö ¾Ê´Ù. ¾ÆÁ÷µµ À¯È¿ÇÑ Á¤º¸°¡ ÀÖÁö¸¸, + ÁÖÀÇÇؼ­ »ç¿ëÇÏ±æ ¹Ù¶õ´Ù. +
+ +
+ +
top
+
+

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

+ + + +

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

+ +

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

+ +

Æ÷ÆÃÀº óÀ½¿¡ ´ÙÀ½°ú °°Àº ¸ñÀû¿¡¼­ ½ÃÀ۵Ǿú´Ù

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

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

+ +
top
+
+

¼³°è ¸ñÇ¥

+ + + +

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

+ +
top
+
+

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

+ + + +

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

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

Æ÷Æÿ¡ ´ëÇؼ­

+ + + +
    +
  1. +

    ¼Ò½ºÀÇ º¯È­´Â µÎ°¡Áö #ifdef·Î ±¸ºÐÇÒ + ¼ö ÀÖ´Ù:

    + +
    +
    #ifdef + CHARSET_EBCDIC
    + +
    +

    ¸ðµç EBCDIC±â¹Ý ÄÄÇ»ÅÍ¿¡ ÇÊ¿äÇÑ ÄÚµå. ¹®ÀÚº¯È¯, + µÎ ¹®ÀÚÁýÇÕ°£ÀÇ ¿¬¼ÓµÈ ¹®ÀÚ°ª Â÷ÀÌ, ¾î¶² HTTP ÇÁ·ÎÅäÄÝ + ºÎºÐÀÌ º¯È¯µÇ¾ß ÇÏ´ÂÁö¸¦ ¾Ë·ÁÁִ ǥ½Ã µî.

    +
    + +
    #ifdef _OSD_POSIX
    + +
    +

    SIEMENS BS2000/OSD ¸ÞÀÎÇ÷¹ÀÓ Ç÷¹Æû¿¡¸¸ ÇÊ¿äÇÑ + ÄÚµå. BS2000/OSD Ç÷¹Æû¿¡¸¸ ÇÊ¿äÇÑ Çì´õÆÄÀÏ Â÷ÀÌ¿Í + ¼ÒÄÏ ±¸Çö ¹®Á¦¸¦ ´Ù·é´Ù.

    +
    +
    +
    2. + +
  2. +

    ¼ÒÄÏ ¼öÁØ¿¡¼­ ASCII¿Í EBCDIC°£ º¯È­´Â (BS2000 POSIX¿¡´Â + ÀÌ ±â´ÉÀ» Áö¿øÇÏ´Â ¼ÒÄÏ ¿É¼ÇÀÌ ÀÖ´Ù) HTTP ÇÁ·ÎÅäÄÝ ¼öÁØ¿¡¼­ + Àü¼ÛµÇ´Â ÀÚ·á¿¡ ÇÁ·ÎÅäÄÝ°ü·Ã ¹®ÀÚ¿­°ú ÇÁ·ÎÅäÄÝ°ú ¹«°üÇÑ + ÀϹÝÆÄÀÏÀÌ ¼¯¿©Àֱ⶧¹®¿¡ ÀǵµÀûÀ¸·Î »ç¿ëÇÏÁö + ¾Ê¾Ò´Ù. HTTP ÇÁ·ÎÅäÄÝ ¹®ÀÚ¿­Àº (GET + ¿äû, Header: ÁÙ, ±âŸ Á¤º¸ µî.) Ç×»ó ASCII + Çü½ÄÀÌ°í, ÆÄÀÏÀü¼Û ºÎºÐÀº (Áï, GIF ±×¸², CGI + Ãâ·Â µî.) ¼­¹ö°¡ Ç×»ó "º¯È¯ÇÏÁö¾Ê°í ±×³É" º¸³»¾ß + ÇÑ´Ù. ¼­¹ö ÄÚµå´Â "ÇÁ·ÎÅäÄÝ ¹®ÀÚ¿­"°ú "ÀÏ¹Ý ÀÚ·á"¸¦, + ¹®ÀÚ¿­¿¡´Â bgets()³ª rvputs(), + ¹ÙÀ̳ʸ® ÀÚ·á¿¡´Â bgets()³ª + rvputs() ÇÔ¼ö¸¦ »ç¿ëÇÏ¿© ±¸º°ÇÑ´Ù. ±×·¯¹Ç·Î + ¹«Á¶°Ç ¸ðµç °ÍÀ» º¯È¯ÇÏ´Â °ÍÀº ÀûÀýÇÏÁö ¾Ê´Ù.

    + +

    (¹°·Ð ¹®ÀÚÆÄÀÏÀÇ °æ¿ì EBCDIC ¹®¼­¸¦ Ç×»ó ASCII·Î + ¼­ºñ½ºÇϵµ·Ï ÁغñÇØ¾ß ÇÑ´Ù)

    +
    3. + +
  3. +

    ±×·¡¼­ Æ÷Æÿ¡´Â (ÄÄÆÄÀÏ·¯°¡ EBCDIC ¹®ÀÚ¿­·Î º¯È¯ÇÑ) + ¼­¹ö ³»ºÎ ¹®ÀÚ¿­°ú ¼­¹ö°¡ »ý¼ºÇÑ ¹®¼­¸¦ ±âº» ÇÁ·ÎÅäÄÝ + ¼öÁØ¿¡¼­ º¯È¯ÇÏ´Â ±â´ÉÀÌ ÀÖ´Ù. ¼­¹ö Äڵ忡 »êÀçµÈ ASCII + escape¹®ÀÚ \012¿Í \015´Â ¿¹¿Ü´Ù: + À̵éÀÌ ÀÌ¹Ì ASCII \n°ú \rÀÇ + ¹ÙÀ̳ʸ® °ªÀ̱⶧¹®¿¡ ASCII·Î µÎ¹ø º¯È¯ÇÏ¸é ¾ÈµÈ´Ù. + ÀÌ ¿¹¿Ü´Â ¼­¹ö°¡ »ý¼ºÇÑ ¹®ÀÚ¿­¿¡¸¸ Àû¿ëµÈ´Ù; ¿ÜºÎ + EBCDIC ¹®¼­´Â ASCII Áٹٲ޹®ÀÚ¸¦ Æ÷ÇÔÇÏ¸é ¾ÈµÈ´Ù.

    +
    4. + +
  4. +

    BUFF °ü¸®ÇÔ¼ö¸¦ »ç¿ëÇÏ´Â ¹æ¹ýÀ» »ìÆ캻 ÈÄ ³ª´Â ¸ðµç + puts/write/get/gets°¡ °ÅÄ¡°ÔµÇ´Â "ebcdic/ascii º¯È¯ + °èÃþ"À» Ãß°¡ÇÏ°í, µ¿ÀûÀ¸·Î º¯È¯À¯¹«¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Â + º¯È¯ Ç¥½Ã¸¦ Ãß°¡Çß´Ù. ¹®¼­°¡ ¿øº»(ÆÄÀÏÀ̳ª CGI Ãâ·Â)¿¡¼­ + ´ë»ó(¿äûÇÑ Å¬¶óÀ̾ðÆ®)À¸·Î À̵¿ÇÒ¶§ Ç×»ó ÀÌ °èÃþÀ» + µÎ¹ø Áö³­´Ù: ÆÄÀÏ -> ¾ÆÆÄÄ¡, ¾ÆÆÄÄ¡ + -> Ŭ¶óÀ̾ðÆ®.

    + +

    ¼­¹ö´Â ÀÌÁ¦ EBCDIC Çü½ÄÀ¸·Î µÈ CGI ½ºÅ©¸³Æ® Ãâ·ÂÀÇ + Çì´õÁÙÀ» Àаí, ³ª¸ÓÁö ½ºÅ©¸³Æ® Ãâ·ÂÀÌ ASCIIÀÓÀ» ¾Ë¾Æ³¾ + ¼ö ÀÖ´Ù (WWW ¹æ¹®ÀÚ¼ö¸¦ ¼¼´Â ÇÁ·Î±×·¥°ú °°Àº °æ¿ì: ¹®¼­ + ³»¿ëÀº GIF ±×¸²ÀÌ´Ù). ±âº» EBCDIC Çü½ÄÀ¸·Î ¸ðµç Çì´õ¸¦ + ó¸®ÇÑ´Ù; ±×·± ´ÙÀ½ ¼­ºñ½ºÇÒ ¹®¼­ÀÇ type¿¡ µû¶ó ¼­¹ö´Â + ¹®¼­ ³»¿ëÀÌ ÀÌ¹Ì ASCIIÀÎÁö ȤÀº EBCDIC¿¡¼­ º¯È¯À» ÇØ¾ß + ÇÏ´ÂÁö °áÁ¤ÇÑ´Ù.

    +
    5. + +
  5. +

    (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"·Î ¼­ºñ½ºÇÒ ¼ö ÀÖ´Ù.

    +
    6. + +
  6. +

    ³»¿ëÀÌ ÀÏ¹Ý ¹®ÀÚ°¡ ¾Æ´Ñ ¹®¼­´Â º¯È¯¾øÀÌ Ç×»ó "¹ÙÀ̳ʸ®"·Î + ¼­ºñ½ºÇÑ´Ù. ¿¹¸¦ µé¾î, GIF/ZIP/AU ÆÄÀÏÇü½Ä¿¡ + °¡Àå ÀûÇÕÇÑ ¼±ÅÃÀÌ´Ù. ¹°·Ð »ç¿ëÀÚ´Â "rcp -b" + ¹ÙÀ̳ʸ® ¿É¼ÇÀ» »ç¿ëÇÏ¿© ÆÄÀÏÀ» ¸ÞÀÎÇ÷¹ÀÓ È£½ºÆ®·Î + º¹»çÇß¾î¾ß ÇÑ´Ù.

    +
    7. + +
  7. +

    ¼­¹öÆÄ½Ì ÆÄÀÏÀº Ç×»ó ÄÄÇ»ÅÍ°¡ »ç¿ëÇÏ´Â ±âº» Çü½ÄÀ¸·Î + (Áï, EBCDIC) ÀúÀåµÇ¾ú´Ù°í °¡Á¤ÇÏ°í, ó¸®ÈÄ¿¡ + º¯È¯ÇÑ´Ù.

    +
    8. + +
  8. +

    CGI Ãâ·ÂÀÇ °æ¿ì CGI ½ºÅ©¸³Æ®°¡ º¯È¯ÀÌ ÇÊ¿äÇÑÁö °áÁ¤ÇÑ´Ù: + ÀûÀýÇÑ Content-TypeÀ» ¼³Á¤ÇÏ¿©, ¹®ÀÚÆÄÀÏÀº º¯È¯ÇÏ°í, + GIF Ãâ·ÂÀº º¯È¯¾øÀÌ º¸³¾ ¼ö ÀÖ´Ù. ¿ì¸®°¡ Æ÷ÆÃÇÑ wwwcount + ÇÁ·Î±×·¥ÀÌ ÈÄÀÚÀÇ °æ¿ì´Ù.

    +
    9. + +
+ +
top
+
+

¹®¼­ ÀúÀå¿¡ ´ëÇؼ­

+ + + +

¹ÙÀ̳ʸ® ÆÄÀÏ

+ + + +

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

+ +

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

+ + + +

¹®ÀÚ ¹®¼­

+ + + +

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

+ + + +

Server Side Include ¹®¼­

+ + + +

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

+ + + +
top
+
+

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

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¸ðµâ»óźñ°í
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?Å×½ºÆ®¾ÈµÊ
+ +
top
+
+

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

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¸ðµâ»óźñ°í
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/index.html b/docs/manual/platform/index.html new file mode 100644 index 00000000..5b7bb86f --- /dev/null +++ b/docs/manual/platform/index.html @@ -0,0 +1,7 @@ +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/index.html.en b/docs/manual/platform/index.html.en new file mode 100644 index 00000000..f4b58def --- /dev/null +++ b/docs/manual/platform/index.html.en @@ -0,0 +1,94 @@ + + + +Platform Specific Notes - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Platform Specific Notes

+
+

Available Languages:  en  | + ko 

+
+
+ +
top
+
+

Microsoft Windows

+ + + +
+
Using Apache
+
+

This document explains how to install, configure and run Apache 2.0 + under Microsoft Windows.

+ +

See: Using Apache with Microsoft Windows

+
+
+ +
+
Compiling Apache
+
+

There are many important points before you begin compiling Apache. + This document explain them.

+ +

See: Compiling Apache for Microsoft Windows

+
+
+ +
top
+
+

Other Platforms

+ + + +
+
Novell NetWare
+
+

This document explains how to install, configure and run Apache 2.0 + under Novell NetWare 5.1 and above.

+ +

See: Using Apache With Novell NetWare

+
+
+ +
+
EBCDIC
+
+

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.

+ +
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.
+ +

See: The Apache EBCDIC Port

+
+
+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/index.html.ko.euc-kr b/docs/manual/platform/index.html.ko.euc-kr new file mode 100644 index 00000000..58214d5c --- /dev/null +++ b/docs/manual/platform/index.html.ko.euc-kr @@ -0,0 +1,94 @@ + + + +Ç÷¡Æûº° ¼³¸í - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Ç÷¡Æûº° ¼³¸í

+
+

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

+
+
+ +
top
+
+

Microsoft Windows

+ + + +
+
¾ÆÆÄÄ¡ »ç¿ë¹ý
+
+

ÀÌ ¹®¼­´Â Microsoft Windows¿¡¼­ ¾ÆÆÄÄ¡ 2.0À» ¼³Ä¡, + ¼³Á¤, ½ÇÇàÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù.

+ +

¹®¼­: Microsoft Windows¿¡¼­ + ¾ÆÆÄÄ¡ »ç¿ë¹ý

+
+
+ +
+
¾ÆÆÄÄ¡ ÄÄÆÄÀÏ
+
+

¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇϱâ Àü¿¡ ÁÖÀÇÇÒ Á¡ÀÌ ¸¹´Ù. ÀÌ ¹®¼­´Â + ÀÌÁ¡À» ¼³¸íÇÑ´Ù.

+ +

¹®¼­: Microsoft Windows¿ë ¾ÆÆÄÄ¡ ÄÄÆÄÀÏ

+
+
+ +
top
+
+

±âŸ Ç÷¡Æû

+ + + +
+
Novell NetWare
+
+

ÀÌ ¹®¼­´Â Novell NetWare 5.1 À̻󿡼­ ¾ÆÆÄÄ¡ 2.0À» + ¼³Ä¡, ¼³Á¤, ½ÇÇàÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù.

+ +

¹®¼­: Novell NetWare¿¡¼­ ¾ÆÆÄÄ¡ + »ç¿ëÇϱâ

+
+
+ +
+
EBCDIC
+
+

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

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

¹®¼­: ¾ÆÆÄÄ¡ EBCDIC Æ÷ÆÃ

+
+
+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/platform/netware.html b/docs/manual/platform/netware.html new file mode 100644 index 00000000..cb2d4221 --- /dev/null +++ b/docs/manual/platform/netware.html @@ -0,0 +1,7 @@ +URI: netware.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: netware.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/netware.html.en b/docs/manual/platform/netware.html.en new file mode 100644 index 00000000..1172d29d --- /dev/null +++ b/docs/manual/platform/netware.html.en @@ -0,0 +1,655 @@ + + + +Using Apache With Novell NetWare - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

Using Apache With Novell NetWare

+
+

Available Languages:  en  | + ko 

+
+ + +

This document explains how to install, configure and run + Apache 2.0 under Novell NetWare 6.0 and above. If you find any bugs, + or wish to contribute in other ways, please use our + bug reporting + page.

+ +

The bug reporting page and dev-httpd mailing list are not + provided to answer questions about configuration or running Apache. + Before you submit a bug report or request, first consult this document, the + Frequently Asked Questions page and the other + relevant documentation topics. If you still have a question or problem, + post it to the + novell.devsup.webserver newsgroup, where many Apache users are more than + willing to answer new and obscure questions about using Apache on NetWare.

+ +

Most of this document assumes that you are installing Apache + from a binary distribution. If you want to compile Apache + yourself (possibly to help with development, or to track down + bugs), see the section on Compiling Apache for + NetWare below.

+ +
+ +
top
+
+

Requirements

+ + + +

Apache 2.0 is designed to run on NetWare 6.0 service pack 3 + and above. If you are running a service pack less + than SP3, you must install the latest + NetWare Libraries + for C (LibC).

+ +

NetWare service packs are available here.

+ +

Apache 2.0 for NetWare can also be run in a NetWare 5.1 environment + as long as the latest service pack or the latest version + of the NetWare Libraries + for C (LibC) has been installed . WARNING: Apache 2.0 + for NetWare has not been targeted for or tested in this environment.

+ +
top
+
+

Downloading Apache for NetWare

+ + + +

Information on the latest version of Apache can be found on + the Apache web server at http://www.apache.org/. This + will list the current release, any more recent alpha or + beta-test releases, together with details of mirror web and + anonymous ftp sites. Binary builds of the latest releases of + Apache 2.0 for NetWare can be downloaded from + here.

+ +
top
+
+

Installing Apache for NetWare

+ + + +

There is no Apache install program for NetWare currently. If you + are building Apache 2.0 for NetWare from source, you will need to + copy the files over to the server manually.

+ +

Follow these steps to install Apache on NetWare from the + binary download (assuming you will install to + sys:/apache2):

+ +
    +
  • Unzip the binary download file to the root of the SYS: + volume (may be installed to any volume)
    • + +
  • Edit the httpd.conf file setting ServerRoot and ServerName along with any file path values + to reflect your correct server settings
    • + +
  • Add SYS:/APACHE2 to the search path, for example: +

    SEARCH ADD SYS:\APACHE2

    +
    • + +
+ +

Follow these steps to install Apache on NetWare manually + from your own build source (assuming you will install to + sys:/apache2):

+ +
    +
  • Create a directory called Apache2 on a + NetWare volume
    • + +
  • Copy APACHE2.NLM, APRLIB.NLM + to SYS:/APACHE2
    • + +
  • Create a directory under SYS:/APACHE2 + called BIN
    • + +
  • Copy HTDIGEST.NLM, HTPASSWD.NLM, + HTDBM.NLM, LOGRES.NLM, ROTLOGS.NLM + to SYS:/APACHE2/BIN
    • + +
  • Create a directory under SYS:/APACHE2 + called CONF
    • + +
  • Copy the HTTPD-STD.CONF file to the + SYS:/APACHE2/CONF directory and rename to + HTTPD.CONF
    • + +
  • Copy the MIME.TYPES, CHARSET.CONV and + MAGIC files to SYS:/APACHE2/CONF directory
    • + +
  • Copy all files and subdirectories in \HTTPD-2.0\DOCS\ICONS + to SYS:/APACHE2/ICONS
    • + +
  • Copy all files and subdirectories in \HTTPD-2.0\DOCS\MANUAL + to SYS:/APACHE2/MANUAL
    • + +
  • Copy all files and subdirectories in \HTTPD-2.0\DOCS\ERROR + to SYS:/APACHE2/ERROR
    • + +
  • Copy all files and subdirectories in \HTTPD-2.0\DOCS\DOCROOT + to SYS:/APACHE2/HTDOCS
    • + +
  • Create the directory SYS:/APACHE2/LOGS + on the server
    • + +
  • Create the directory SYS:/APACHE2/CGI-BIN + on the server
    • + +
  • Create the directory SYS:/APACHE2/MODULES + and copy all nlm modules into the modules directory
    • + +
  • Edit the HTTPD.CONF file searching for all + @@Value@@ markers and replacing them with the + appropriate setting
    • + +
  • Add SYS:/APACHE2 to the search path, for example: +

    SEARCH ADD SYS:\APACHE2

    +
    • +
+ +

Apache may be installed to other volumes besides the default SYS volume.

+ +

During the build process, adding the keyword "install" to the makefile command line + will automatically produce a complete distribution package under the subdirectory + DIST. Install Apache by simply copying the distribution that was produced + by the makfiles to the root of a NetWare volume (see: Compiling Apache for + NetWare below).

+ +
top
+
+

Running Apache for NetWare

+ + + +

To start Apache just type apache at the + console. This will load apache in the OS address space. If you + prefer to load Apache in a protected address space you may + specify the address space with the load statement as follows:

+ +

+ load address space = apache2 apache2 +

+ +

This will load Apache into an address space called apache2. + Running multiple instances of Apache concurrently on NetWare is + possible by loading each instance into its own protected + address space.

+ +

After starting Apache, it will be listening to port 80 + (unless you changed the Listen + directive in the configuration files). + To connect to the server and access the default page, + launch a browser and enter the server's name or address. This + should respond with a welcome page, and a link to the Apache + manual. If nothing happens or you get an error, look in the + error_log file in the logs + directory.

+ +

Once your basic installation is working, you should + configure it properly by editing the files in the + conf directory.

+ +

To unload Apache running in the OS address space just type + the following at the console:

+ +

+ unload apache2 +

+ +

or

+ +

+ apache2 shutdown +

+ +

If apache is running in a protected address space specify the + address space in the unload statement:

+ +

+ unload address space = apache2 apache2 +

+ +

When working with Apache it is important to know how it will + find the configuration files. You can specify a configuration + file on the command line in two ways:

+ +
    +
  • -f specifies a path to a particular + configuration file
    • +
+ +

+ apache2 -f "vol:/my server/conf/my.conf" +

+ +

+ apache -f test/test.conf +

+ +

In these cases, the proper ServerRoot + should be set in the configuration file.

+ +

If you don't specify a configuration file name with -f, + Apache will use the file name compiled into the server, usually + conf/httpd.conf. Invoking Apache with the -V + switch will display this value labeled as SERVER_CONFIG_FILE. + Apache will then determine its ServerRoot + by trying the following, in this order:

+ +
    +
  • A ServerRoot directive via a + -C switch.
    • + +
  • The -d switch on the command line.
    • + +
  • Current working directory
    • + +
  • The server root compiled into the server.
    • +
+ +

The server root compiled into the server is usually sys:/apache2. + invoking apache with the -V switch will display this value labeled as + HTTPD_ROOT.

+ +

Apache 2.0 for NetWare includes a set of command line directives that can + be used to modify or display information about the running instance of the + web server. These directives are only available while Apache is running. Each + of these directives must be preceded by the keyword APACHE2.

+ +
+
RESTART
+
Instructs Apache to terminate all running worker + threads as they become idle, reread the configuration file and restart each + worker thread based on the new configuration.
+ +
VERSION
+
Displays version information about the currently + running instance of Apache.
+ +
MODULES
+
Displays a list of loaded modules both built-in + and external.
+ +
DIRECTIVES
+
Displays a list of all available directives.
+ +
SETTINGS
+
Enables or disables the thread status display + on the console. When enabled, the state of each running threads is displayed + on the Apache console screen.
+ +
SHUTDOWN
+
Terminates the running instance of the Apache + web server.
+ +
HELP
+
Describes each of the runtime directives.
+
+ +

By default these directives are issued against the instance of Apache running + in the OS address space. To issue a directive against a specific instance running + in a protected address space, include the -p parameter along with the name of the + address space. For more information type "apache2 Help" on the command line.

+ +
top
+
+

Configuring Apache for NetWare

+ + + +

Apache is configured by reading configuration files usually stored + in the conf directory. These are the same as files used + to configure the Unix version, but there are a few different directives for + Apache on NetWare. See the Apache + documentation for all the available directives.

+ +

The main differences in Apache for NetWare are:

+ +
    +
  • +

    Because Apache for NetWare is multithreaded, it does not + use a separate process for each request, as Apache does on some Unix + implementations. Instead there are only threads running: a parent + thread, and multiple child or worker threads which handle the requests.

    + +

    Therefore the "process"-management directives are different:

    + +

    MaxRequestsPerChild - + Like the Unix directive, this controls how many requests + a worker thread will serve before exiting. The recommended default, + MaxRequestsPerChild 0, causes the thread to continue servicing + request indefinitely. It is recommended on NetWare, unless there is some + specific reason, that this directive always remain set to 0.

    + +

    StartThreads - + This directive tells the server how many threads it should start initially. + The recommended default is StartThreads 50.

    + +

    MinSpareThreads - + This directive instructs the server to spawn additional worker threads + if the number of idle threads ever falls below this value. The recommended + default is MinSpareThreads 10.

    + +

    MaxSpareThreads - + This directive instructs the server to begin terminating worker threads + if the number of idle threads ever exceeds this value. The recommended + default is MaxSpareThreads 100.

    + +

    MaxThreads - + This directive limits the total number of work threads to a maximum + value. The recommended default is ThreadsPerChild 250.

    + +

    ThreadStackSize - + This directive tells the server what size of stack to use + for the individual worker thread. The recommended default + is ThreadStackSize 65536.

    +
    • + +
  • +

    The directives that accept filenames as arguments must use + NetWare filenames instead of Unix names. However, because Apache + uses Unix-style names internally, forward slashes must be used + rather than backslashes. It is recommended that all rooted file paths + begin with a volume name. If omitted, Apache will assume the + SYS: volume which may not be correct.

    +
    • + +
  • +

    Apache for NetWare has the ability to load modules at + runtime, without recompiling the server. If Apache is + compiled normally, it will install a number of optional + modules in the \Apache2\modules directory. + To activate these, or other modules, the LoadModule directive + must be used. For example, to active the status module, use + the following:

    + +

    + LoadModule status_module modules/status.nlm +

    + +

    Information on creating loadable + modules is also available.

    +
    • +
+ +

Additional NetWare specific directives:

+ + + +
    +
  • CGIMapExtension - + This directive maps a CGI file extension to a script interpreter.
    • +
+
    +
  • SecureListen - + Enables SSL encryption for a specified port.
    • +
+
    +
  • NWSSLTrustedCerts - + Adds trusted certificates that are used to create secure connections to proxied servers.
    • +
+
    +
  • NWSSLUpgradeable - + Allow a connection created on the specified address/port to be upgraded to an SSL connection.
    • +
+ + + +
top
+
+

Compiling Apache for NetWare

+ + + +

Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once + Apache has been built, it can be installed to the root of any NetWare + volume. The default is the sys:/Apache2 directory.

+ +

Before running the server you must fill out the conf + directory. Copy the file HTTPD-STD.CONF from the distribution + conf directory and rename it to HTTPD.CONF. + Edit the HTTPD.CONF file searching for all @@Value@@ + markers and replacing them with the appropriate setting. Copy over + the conf/magic and conf/mime.types files as well. + Alternatively, a complete distribution can be built by including the keyword + install when invoking the makefiles.

+ +

Requirements:

+ + + +

The following development tools are required to build + Apache 2.0 for NetWare:

+ + + + + +

Building Apache using the NetWare makefiles:

+ + + +
    +
  • Set the environment variable NOVELLLIBC to the + location of the NetWare Libraries for C SDK, for example: +

    Set NOVELLLIBC=c:\novell\ndk\libc

    +
    • + +
  • Set the environment variable METROWERKS to the + location where you installed the Metrowerks CodeWarrior compiler, + for example: +

    Set METROWERKS=C:\Program Files\Metrowerks\CodeWarrior

    + If you installed to the default location C:\Program + Files\Metrowerks\CodeWarrior, you don't need to set this.
    • + +
  • Set the environment variable LDAPSDK to the + location where you installed the LDAP Libraries for C, for example: +

    Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc

    +
    • + +
  • Set the environment variable ZLIBSDK to the + location where you installed the source code for the ZLib Library, + for example: +

    Set ZLIBSDK=D:\NOVELL\zlib

    +
    • + +
  • Set the environment variable AP_WORK to the full path of + the httpd source code directory. +

    Set AP_WORK=D:\httpd-2.0.x

    +
    • + +
  • Set the environment variable APR_WORK to the full path of + the apr source code directory. Typically \httpd\srclib\apr + but the APR project can be outside of the httpd directory structure. +

    Set APR_WORK=D:\apr-1.x.x

    +
    • + +
  • Set the environment variable APU_WORK to the full path of + the apr-util source code directory. Typically \httpd\srclib\apr-util + but the APR-UTIL project can be outside of the httpd directory structure. +

    Set APU_WORK=D:\apr-util-1.x.x

    +
    • + +
  • Make sure that the path to the AWK utility and the GNU make utility + (gmake.exe) have been included in the system's + PATH environment variable.
    • + +
  • Download the source code and unzip to an appropriate directory on + your workstation.
    • + +
  • Change directory to \httpd-2.0 and build the prebuild utilities + by running "gmake -f nwgnumakefile prebuild". This target will create + the directory \httpd-2.0\nwprebuild and copy each of the utilities + to this location that are necessary to complete the following build steps. +
    • + +
  • Copy the files \httpd-2.0\nwprebuild\GENCHARS.nlm and + \httpd-2.0\nwprebuild\DFTABLES.nlm to the SYS: volume of a + NetWare server and run them using the following commands: +

    + SYS:\genchars > sys:\test_char.h
    + SYS:\dftables sys:\chartables.c
    +

    +
    • + +
  • Copy the files test_char.h and chartables.c + to the directory \httpd-2.0\os\netware on the build machine.
    • + +
  • Change directory to \httpd-2.0 and build Apache by running + "gmake -f nwgnumakefile". You can create a distribution directory by + adding an install parameter to the command, for example: +

    gmake -f nwgnumakefile install

    +
    • +
+ + + +

Additional make options

+ + + +
    +
  • gmake -f nwgnumakefile

    Builds release versions of all of the + binaries and copies them to a \release destination directory.

    • + +
  • gmake -f nwgnumakefile DEBUG=1

    Builds debug versions of all of the + binaries and copies them to a \debug destination directory.

    • + +
  • gmake -f nwgnumakefile install

    Creates a complete Apache + distribution with binaries, docs and additional support files in a + \dist\Apache2 directory.

    • + +
  • gmake -f nwgnumakefile prebuild

    Builds all of the prebuild utilities + and copies them to the \nwprebuild directory.

    • + +
  • gmake -f nwgnumakefile installdev

    Same as install but also creates a + \lib and \include directory in the destination directory + and copies headers and import files.

    • + +
  • gmake -f nwgnumakefile clean

    Cleans all object files and binaries + from the \release.o or \debug.o build areas depending on whether + DEBUG has been defined.

    • + +
  • gmake -f nwgnumakefile clobber_all

    Same as clean and also deletes + the distribution directory if it exists.

    • +
+ + + +

Additional environment variable options

+ + + +
    +
  • To build all of the experimental modules, set the environment + variable EXPERIMENTAL: +

    Set EXPERIMENTAL=1

    +
    • + +
  • To build Apache using standard BSD style sockets rather than + Winsock, set the environment variable USE_STDSOCKETS: +

    Set USE_STDSOCKETS=1

    +
    • + +
+ + + +

Building mod_ssl for the NetWare platform

+ + + +

By default Apache for NetWare uses the built-in module + mod_nw_ssl to provide SSL services. This module + simply enables the native SSL services implemented in NetWare OS + to handle all encryption for a given port. Alternatively, mod_ssl + can also be used in the same manner as on other platforms.

+ +

Before mod_ssl can be built for the NetWare platform, the OpenSSL + libraries must be provided. This can be done through the following + steps:

+ +
    +
  • Download the latest NetWare patch for OpenSSL from the + OpenSSL Contribution + page.
    • + +
  • Download the corresponding OpenSSL source code from the + OpenSSL Source + page.
    • + +
  • At the root of the OpenSSL source directory, apply the NetWare + patch using the "patch" utility, for example: +

    patch -p 1 -i netwarepatch-0.9.7g.diff

    • + +
  • Edit the file NetWare/set_env.bat and modify any + tools and utilities paths so that they correspond to your build + environment.
    • + +
  • From the root of the OpenSSL source directory, run the following + scripts: +

    + Netware/set_env netware-libc
    + Netware/build netware-libc +

    • + +
  • Before building Apache, set the environment variable + OSSLSDK to the full path to the root of the openssl + source code directory. +

    Set OSSLSDK=d:\openssl-0.9.7x

    • + +
+ + + +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/netware.html.ko.euc-kr b/docs/manual/platform/netware.html.ko.euc-kr new file mode 100644 index 00000000..a8347f1d --- /dev/null +++ b/docs/manual/platform/netware.html.ko.euc-kr @@ -0,0 +1,581 @@ + + + +Novell NetWare¿¡¼­ ¾ÆÆÄÄ¡ »ç¿ëÇϱâ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

Novell NetWare¿¡¼­ ¾ÆÆÄÄ¡ »ç¿ëÇϱâ

+
+

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

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

ÀÌ ¹®¼­´Â Novell NetWare 6.0 À̻󿡼­ ¾ÆÆÄÄ¡ 2.0À» ¼³Ä¡, + ¼³Á¤, ½ÇÇàÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù. ¹ö±×¸¦ ã¾Ò°Å³ª ´Ù¸¥ ¹æ¹ýÀ¸·Î + µ½°í½Í´Ù¸é, ¹ö±× + º¸°í ÆäÀÌÁö¸¦ ÀÌ¿ëÇÏ±æ ¹Ù¶õ´Ù.

+ +

¹ö±× º¸°í ÆäÀÌÁö³ª dev-httpd ¸ÞÀϸµ¸®½ºÆ®´Â ¾ÆÆÄÄ¡ ¼³Á¤°ú + ½ÇÇà¿¡ ´ëÇÑ Áú¹®À» ´äÇÏÁö ¾Ê´Â´Ù. ¹ö±×¸¦ º¸°íÇϱâ + Àü¿¡ ¸ÕÀú ÀÌ ¹®¼­¿Í ÀÚÁÖ ¹°¾îº¸´Â Áú¹® + (FAQ) ÆäÀÌÁö, ´Ù¸¥ °ü·Ã¹®¼­¸¦ »ìÆìºÁ¶ó. ±×·¡µµ ±Ã±ÝÇÑ + Á¡À̳ª ¹®Á¦°¡ ÀÖ´Ù¸é, NetWare¿¡¼­ ¾ÆÆÄÄ¡ »ç¿ë¿¡ ´ëÇÑ ¾î·Æ°í + »õ·Î¿î Áú¹®À» ´äÇØÁÙ ¸¹Àº ¾ÆÆÄÄ¡ »ç¿ëÀÚ°¡ ÀÖ´Â + novell.devsup.webserver ´º½º±×·ì¿¡ ±ÛÀ» ¿Ã¸®±æ ¹Ù¶õ´Ù.

+ +

ÀÌ ¹®¼­´Â ¹ÙÀ̳ʸ® ¹èÆ÷º»À¸·Î ¾ÆÆÄÄ¡¸¦ ¼³Ä¡Çß´Ù°í °¡Á¤ÇÑ´Ù. + (¾Æ¸¶µµ °³¹ß¿¡ µµ¿òÀ» Áְųª ¹ö±×¸¦ ã±âÀ§ÇØ) Á÷Á¢ ¾ÆÆÄÄ¡¸¦ + ÄÄÆÄÀÏÇÏ·Á¸é ¾Æ·¡ NetWare¿¡¼­ ¾ÆÆÄÄ¡ + ÄÄÆÄÀÏÇϱâ ÀýÀ» Âü°íÇ϶ó.

+ +
+ +
top
+
+

¿ä±¸Á¶°Ç

+ + + +

¾ÆÆÄÄ¡ 2.0Àº NetWare 6.0 service pack 3 À̻󿡼­ µ¿ÀÛÇϵµ·Ï + ¼³°èµÇ¾ú´Ù. SP3º¸´Ù ³·Àº service packÀ» »ç¿ëÇÑ´Ù¸é ÃֽŠ+ NetWare + Libraries for C (LibC)¸¦ ¼³Ä¡ÇØ¾ß ÇÑ´Ù.

+ +

NetWare service packÀº ¿©±â¿¡ + ÀÖ´Ù.

+ +

ÃֽŠservice packÀ̳ª ÃֽŠ¹öÀü NetWare + Libraries for C (LibC)¸¦ ¼³Ä¡Çß´Ù¸é NetWare 5.1 ȯ°æ¿¡¼­µµ + NetWare¿ë ¾ÆÆÄÄ¡ 2.0À» ½ÇÇàÇÒ ¼ö ÀÖ´Ù. °æ°í: + NetWare¿ë ¾ÆÆÄÄ¡ 2.0Àº ÀÌ È¯°æÀ» °í·ÁÇÏÁö ¾Ê¾Ò°í Å×½ºÆ®ÇÏÁö + ¾Ê¾Ò´Ù.

+ +
top
+
+

NetWare¿ë ¾ÆÆÄÄ¡ ´Ù¿î¹Þ±â

+ + + +

¾ÆÆÄÄ¡ ÃֽŠ¹öÀü¿¡ ´ëÇÑ Á¤º¸´Â http://www.apache.org/¿¡¼­ + (¾ÆÆÄÄ¡ À¥¼­¹ö) ãÀ» ¼ö ÀÖ´Ù. ¿©±â¿¡´Â ÇöÀç ¹öÀü°ú ÃÖ±Ù + ¾ËÆÄ/º£Å¸Å×½ºÆ® ¹öÀü, ¹Ì·¯ À¥»çÀÌÆ®¿Í ftp »çÀÌÆ® Á¤º¸°¡ + ÀÖ´Ù. NetWare¿ë ¾ÆÆÄÄ¡ 2.0ÀÇ ÃֽŠ¹ÙÀ̳ʸ® ¹èÆ÷º»Àº ¿©±â¿¡¼­ + ´Ù¿î¹ÞÀ» ¼ö ÀÖ´Ù.

+ +
top
+
+

NetWare¿ë ¾ÆÆÄÄ¡ ¼³Ä¡Çϱâ

+ + + +

ÇöÀç NetWare¿ë ¾ÆÆÄÄ¡ ¼³Ä¡ÇÁ·Î±×·¥Àº ¾ø´Ù. NetWare¿ë + ¾ÆÆÄÄ¡ 2.0 ¼Ò½º¸¦ Á÷Á¢ ÄÄÆÄÀÏÇÑ´Ù¸é ÆÄÀÏÀ» ¼­¹ö·Î Á÷Á¢ + º¹»çÇØÁà¾ß ÇÑ´Ù.

+ +

¹ÙÀ̳ʸ®·Î ´Ù¿î¹ÞÀº NetWare¿ë ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÏ´Â °úÁ¤Àº + ´ÙÀ½°ú °°´Ù (sys:/apache2¿¡ ¼³Ä¡ÇÑ´Ù°í °¡Á¤ÇÑ´Ù):

+ +
    +
  • ¹ÙÀ̳ʸ®·Î ´Ù¿î¹ÞÀº ¾ÐÃàÆÄÀÏÀ» SYS: º¼·ý + ÃÖ»óÀ§ µð·ºÅ丮¿¡ Ǭ´Ù (´Ù¸¥ º¼·ý¿¡ ¼³Ä¡Çصµ µÈ´Ù)
    • + +
  • httpd.conf ÆÄÀÏÀ» ¼öÁ¤ÇÏ¿© ServerRoot¿Í ServerName°ú ÆÄÀÏ°æ·Î °ªÀ» ¼­¹ö¿¡ + ¾Ë¸Â°Ô ÁöÁ¤ÇÑ´Ù
    • + +
  • ¿¹¸¦ µé¾î

    SEARCH ADD SYS:\APACHE2

    ¿Í + °°ÀÌ °Ë»ö°æ·Î¿¡ SYS:/APACHE2¸¦ Ãß°¡ÇÑ´Ù +
    • + +
+ +

Á÷Á¢ ¼Ò½º¸¦ ÄÄÆÄÀÏÇÑ °æ¿ì NetWare¿¡ ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÏ´Â + ¹æ¹ýÀº ´ÙÀ½°ú °°´Ù (sys:/apache2¿¡ ¼³Ä¡ÇÑ´Ù°í + °¡Á¤ÇÑ´Ù):

+ +
    +
  • NetWare º¼·ý¿¡ Apache2¶ó´Â µð·ºÅ丮¸¦ + ¸¸µç´Ù
    • + +
  • APACHE2.NLM°ú APRLIB.NLMÀ» + SYS:/APACHE2¿¡ º¹»çÇÑ´Ù
    • + +
  • SYS:/APACHE2 ¾Æ·¡¿¡ BINÀ̶ó´Â + µð·ºÅ丮¸¦ ¸¸µç´Ù
    • + +
  • HTDIGEST.NLM, HTPASSWD.NLM, + HTDBM.NLM, LOGRES.NLM, + ROTLOGS.NLMÀ» SYS:/APACHE2/BIN¿¡ + º¹»çÇÑ´Ù
    • + +
  • SYS:/APACHE2 ¾Æ·¡¿¡ CONF¶ó´Â + µð·ºÅ丮¸¦ ¸¸µç´Ù
    • + +
  • HTTPD-STD.CONF ÆÄÀÏÀ» + SYS:/APACHE2/CONF¿¡ º¹»çÇÏ°í ÆÄÀϸíÀ» + HTTPD.CONF·Î º¯°æÇÑ´Ù
    • + +
  • MIME.TYPES, CHARSET.CONV, + MAGIC ÆÄÀÏÀ» SYS:/APACHE2/CONF + µð·ºÅ丮¿¡ º¹»çÇÑ´Ù
    • + +
  • \HTTPD-2.0\DOCS\ICONS¿¡ ÀÖ´Â ¸ðµç ÆÄÀÏ°ú + ÇÏÀ§µð·ºÅ丮¸¦ SYS:/APACHE2/ICONS·Î º¹»çÇÑ´Ù
    • + +
  • \HTTPD-2.0\DOCS\MANUAL¿¡ ÀÖ´Â ¸ðµç ÆÄÀÏ°ú + ÇÏÀ§µð·ºÅ丮¸¦ SYS:/APACHE2/MANUAL·Î º¹»çÇÑ´Ù
    • + +
  • \HTTPD-2.0\DOCS\ERROR¿¡ ÀÖ´Â ¸ðµç ÆÄÀÏ°ú + ÇÏÀ§µð·ºÅ丮¸¦ SYS:/APACHE2/ERROR·Î º¹»çÇÑ´Ù
    • + +
  • \HTTPD-2.0\DOCS\DICROOT¿¡ ÀÖ´Â ¸ðµç ÆÄÀÏ°ú + ÇÏÀ§µð·ºÅ丮¸¦ SYS:/APACHE2/HTDOCS·Î º¹»çÇÑ´Ù
    • + +
  • ¼­¹ö¿¡ SYS:/APACHE2/LOGS µð·ºÅ丮¸¦ ¸¸µç´Ù
    • + +
  • ¼­¹ö¿¡ SYS:/APACHE2/APACHE2/CGI-BINÀ̶õ + µð·ºÅ丮¸¦ ¸¸µç´Ù
    • + +
  • SYS:/APACHE2/MODULES µð·ºÅ丮¸¦ ¸¸µé°í + ¸ðµç nlm ¸ðµâÀ» modules µð·ºÅ丮·Î º¹»çÇÑ´Ù
    • + +
  • HTTPD.CONF ÆÄÀÏÀÇ ¸ðµç @@Value@@ + Ç¥½Ã¸¦ ÀûÀýÇÑ ¼³Á¤À¸·Î ´ëüÇÑ´Ù
    • + +

  • SEARCH ADD SYS:\APACHE2

    °°ÀÌ °Ë»ö°æ·Î¿¡ + SYS:/APACHE2¸¦ Ãß°¡ÇÑ´Ù +
    • +
+ +

±âº» SYS º¼·ýÀÌ ¾Æ´Ñ ´Ù¸¥ º¼·ý¿¡µµ ¾ÆÆÄÄ¡¸¦ + ¼³Ä¡ÇÒ ¼ö ÀÖ´Ù.

+ +

makefile ¸í·É¾î¿¡ "install" Å°¿öµå¸¦ »ç¿ëÇϸé ÄÄÆÄÀϽà + ÀÚµ¿À¸·Î DIST ÇÏÀ§µð·ºÅ丮¿¡ ¿ÏÀüÇÑ ¹èÆ÷º»À» + ¸¸µç´Ù. makefile·Î ¸¸µç ¹èÆ÷º»À» NetWare º¼·ý ÃÖ»óÀ§ µð·ºÅ丮·Î + º¹»çÇÏ¸é ¾ÆÆÄÄ¡°¡ ¼³Ä¡µÈ´Ù (¾Æ·¡ NetWare¿ë + ¾ÆÆÄÄ¡ ÄÄÆÄÀÏÇϱâ Âü°í).

+ +
top
+
+

NetWare¿ë ¾ÆÆÄÄ¡ ½ÇÇàÇϱâ

+ + + +

¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇÏ·Á¸é Äֿܼ¡¼­ apache¸¦ ÀÔ·ÂÇϸé + µÈ´Ù. ±×·¯¸é ¿î¿µÃ¼Á¦ ÁÖ¼Ò¿µ¿ª¿¡ ¾ÆÆÄÄ¡¸¦ ÀоîµéÀδÙ. + º¸È£ÁÖ¼Ò¿µ¿ª¿¡ ¾ÆÆÄÄ¡¸¦ ÀоîµéÀÌ·Á¸é ´ÙÀ½°ú °°ÀÌ load ¸í·É¾î·Î + ÁÖ¼Ò¿µ¿ªÀ» ÁöÁ¤ÇÑ´Ù:

+ +

+ load address space = apache2 apache2 +

+ +

±×·¯¸é ¾ÆÆÄÄ¡¸¦ apache2¶ó´Â ÁÖ¼Ò¿µ¿ª¿¡ ÀоîµéÀδÙ. + NetWare´Â ¿©·¯ ¾ÆÆÄÄ¡¸¦ °¢°¢ ´Ù¸¥ º¸È£ÁÖ¼Ò¿µ¿ª¿¡ Àоîµé¿©¼­ + ¿©·¯ ¾ÆÆÄÄ¡¸¦ µ¿½Ã¿¡ ½ÇÇàÇÒ ¼ö ÀÖ´Ù.

+ +

¾ÆÆÄÄ¡°¡ ½ÃÀÛÇϸé (¼³Á¤ÆÄÀÏ¿¡¼­ Listen Áö½Ã¾î¸¦ ¼öÁ¤ÇÏÁö + ¾Ê´ÂÇÑ) Æ÷Æ® 80¹øÀ» ±â´Ù¸°´Ù. ºê¶ó¿ìÀú¸¦ ½ÃÀÛÇÏ¿© ¼­¹ö¸í + ȤÀº ¼­¹ö ÁÖ¼Ò¸¦ ÀÔ·ÂÇÏ¸é ¼­¹ö¿¡ Á¢¼ÓÇÏ¿© ±âº»ÆäÀÌÁö¿¡ + Á¢±ÙÇÑ´Ù. ¾ÆÆÄÄ¡ ¼³¸í¼­ ¸µÅ©°¡ Àִ ȯ¿µÆäÀÌÁö°¡ ³ª¿Í¾ß + ÇÑ´Ù. ¾Æ¹« Àϵµ ¾ø°Å³ª ¿À·ù°¡ ¹ß»ýÇϸé logs + µð·ºÅ丮¿¡ ÀÖ´Â error_log ÆÄÀÏÀ» »ìÆìºÁ¶ó.

+ +

±âº» ¼³Ä¡°¡ µ¿ÀÛÇϸé conf µð·ºÅ丮¿¡ ÀÖ´Â + ÆÄÀÏÀ» ÀûÀýÈ÷ ¼³Á¤ÇÑ´Ù.

+ +

¿î¿µÃ¼Á¦ ÁÖ¼Ò¿µ¿ª¿¡¼­ ½ÇÇàÁßÀÎ ¾ÆÆÄÄ¡¸¦ ³»¸±·Á¸é Äֿܼ¡ + ´ÙÀ½°ú °°ÀÌ ÀÔ·ÂÇÑ´Ù:

+ +

+ unload apache2 +

+ +

ȤÀº

+ +

+ apache2 shutdown +

+ +

º¸È£ÁÖ¼Ò¿µ¿ª¿¡¼­ ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇß´Ù¸é unload ¸í·É¾î¿¡ + ÁÖ¼Ò¿µ¿ªÀ» ÁöÁ¤ÇÑ´Ù:

+ +

+ unload address space = apache2 apache2 +

+ +

¾ÆÆÄÄ¡°¡ ¼³Á¤ÆÄÀÏ À§Ä¡¸¦ ã´Â ¹æ¹ýÀ» ¾Ë¾ÆµÎ¾î¾ß ÇÑ´Ù. + ¸í·ÉÇà¿¡¼­ ¼³Á¤ÆÄÀÏÀ» ÁöÁ¤ÇÏ´Â ¹æ¹ýÀº µÎ°¡Áö´Ù:

+ +
    +
  • -f´Â ƯÁ¤ ¼³Á¤ÆÄÀÏ °æ·Î¸¦ ÁöÁ¤ÇÑ´Ù
    • +
+ +

+ apache2 -f "vol:/my server/conf/my.conf" +

+ +

+ apache -f test/test.conf +

+ +

ÀÌ °æ¿ì ¼³Á¤ÆÄÀÏÀº ¿Ã¹Ù¸¥ ServerRoot¸¦ ¼³Á¤ÇØ¾ß ÇÑ´Ù.

+ +

-f·Î ¼³Á¤ÆÄÀϸíÀ» ÁöÁ¤ÇÏÁö ¾ÊÀ¸¸é, ¾ÆÆÄÄ¡´Â + ¼­¹ö¿¡ ÄÄÆÄÀÏµÈ ÆÄÀϸíÀ» (º¸Åë conf/httpd.conf) + »ç¿ëÇÑ´Ù. -V ¿É¼ÇÀ¸·Î ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇϸé + SERVER_CONFIG_FILEÀ̶ó´Â Ç׸ñÀ» º¸¿©ÁØ´Ù. + ¾ÆÆÄÄ¡´Â ´ÙÀ½ ¼ø¼­´ë·Î ServerRoot¸¦ ã´Â´Ù:

+ +
    +
  • -C ¿É¼ÇÀÇ ServerRoot Áö½Ã¾î.
    • + +
  • ¸í·ÉÇàÀÇ -d ¿É¼Ç.
    • + +
  • ÇöÀç µð·ºÅ丮
    • + +
  • ¼­¹ö¿¡ ÄÄÆÄÀÏµÈ server root.
    • +
+ +

¼­¹ö¿¡ ÄÄÆÄÀÏµÈ server root´Â º¸Åë + sys:/apache2ÀÌ´Ù. -V ¿É¼ÇÀ¸·Î + ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇϸé HTTPD_ROOT¶ó´Â Ç׸ñÀ» º¸¿©ÁØ´Ù.

+ +

NetWare¿ë ¾ÆÆÄÄ¡ 2.0¿¡´Â ½ÇÇàÁßÀÎ À¥¼­¹ö¸¦ Á×À̰ųª Á¤º¸¸¦ + ¾Ë·ÁÁÖ´Â ¸í·ÉÇà Áö½Ã¾î°¡ ÀÖ´Ù. À̵é Áö½Ã¾î´Â ¾ÆÆÄÄ¡ µ¿ÀÛÁß¿¡¸¸ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. Áö½Ã¾î ¾Õ¿¡´Â APACHE2 Å°¿öµå¸¦ + ºÙ¿©¾ß ÇÑ´Ù.

+ +
+
RESTART
+
¸ðµç ¾²·¹µå°¡ ½¬´Â »óÅÂÀ϶§ ¾ÆÆÄÄ¡¸¦ Á×ÀÌ°í, ¼³Á¤ÆÄÀÏÀ» + ´Ù½Ã ÀÐÀºÈÄ »õ·Î¿î ¼³Á¤¿¡ µû¶ó worker ¾²·¹µåµéÀ» Àç½ÃÀÛÇÑ´Ù.
+ +
VERSION
+
ÇöÀç ½ÇÇàÁßÀÎ ¾ÆÆÄÄ¡ ¹öÀü Á¤º¸¸¦ Ãâ·ÂÇÑ´Ù.
+ +
MODULES
+
±âº» ¸ðµâ°ú ¿ÜºÎ ¸ðµâ ¸ñ·ÏÀ» Ãâ·ÂÇÑ´Ù.
+ +
DIRECTIVES
+
¸ðµç Áö½Ã¾î ¸ñ·ÏÀ» Ãâ·ÂÇÑ´Ù.
+ +
SETTINGS
+
Äֿܼ¡ ¾²·¹µå »óÅ ǥ½Ã¸¦ º¸À̰ųª ¾ø¾Ø´Ù. »óŸ¦ + º¸À̸é, ¾ÆÆÄÄ¡ ÄܼÖâ¿¡ µ¿ÀÛÇÏ´Â ¾²·¹µåµéÀÇ »óÅ°¡ ³ª¿Â´Ù.
+ +
SHUTDOWN
+
½ÇÇàÁßÀÎ ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ Á×ÀδÙ.
+ +
HELP
+
½ÇÇà ¿É¼ÇµéÀ» ¼³¸íÇÑ´Ù.
+
+ +

±âº»ÀûÀ¸·Î ÀÌ Áö½Ã¾îµéÀº ¿î¿µÃ¼Á¦ ÁÖ¼Ò¿µ¿ª¿¡¼­ ½ÇÇàÁßÀÎ + ¾ÆÆÄÄ¡¸¦ ´ë»óÀ¸·Î ÇÑ´Ù. ¾ÆÆÄÄ¡°¡ º¸È£ÁÖ¼Ò¿µ¿ª¿¡¼­ ½ÇÇàÁßÀ̶ó¸é, + -p¿Í ÁÖ¼Ò¿µ¿ª À̸§À» Ãß°¡ÇÑ´Ù. ´õ ¸¹Àº Á¤º¸¸¦ º¸·Á¸é ¸í·ÉÇà¿¡ + "apache2 Help"¸¦ ÀÔ·ÂÇÑ´Ù.

+ +
top
+
+

NetWare¿ë ¾ÆÆÄÄ¡ ¼³Á¤Çϱâ

+ + + +

¾ÆÆÄÄ¡´Â º¸Åë conf µð·ºÅ丮¿¡ ÀÖ´Â ¼³Á¤ÆÄÀÏ·Î + ¼³Á¤ÇÑ´Ù. ÀÌ ÆÄÀÏÀº À¯´Ð½º¿ë°ú °°Áö¸¸, NetWare¿ë ¾ÆÆÄÄ¡¿¡´Â + Á¶±Ý ´Ù¸¥ Áö½Ã¾îµéÀÌ ÀÖ´Ù. »ç¿ë°¡´ÉÇÑ ¸ðµç Áö½Ã¾î¿¡ ´ëÇؼ­´Â + ¾ÆÆÄÄ¡ ¹®¼­¸¦ Âü°íÇ϶ó.

+ +

NetWare¿ë ¾ÆÆÄÄ¡ÀÇ ÁÖµÈ Â÷ÀÌÁ¡Àº:

+ +
    +
  • +

    NetWare¿ë ¾ÆÆÄÄ¡´Â ´ÙÁß¾²·¹µå ¹æ½ÄÀ» »ç¿ëÇϱ⶧¹®¿¡, + À¯´Ð½º¿Í °°ÀÌ ¿äû¸¶´Ù ´Ù¸¥ ÇÁ·Î¼¼½º¸¦ »ç¿ëÇÏÁö ¾Ê´Â´Ù. + ´ë½Å ¿©·¯ ¾²·¹µå¸¦ ½ÇÇàÇÑ´Ù: ºÎ¸ð ¾²·¹µå¿Í ¿äûÀ» ó¸®ÇÏ´Â + ¿©·¯ ÀÚ½Ä È¤Àº worker ¾²·¹µåµé.

    + +

    ±×·¯¹Ç·Î "ÇÁ·Î¼¼½º"-°ü¸® Áö½Ã¾î°¡ ´Ù¸£´Ù:

    + +

    MaxRequestsPerChild - + À¯´Ð½º¿Í °°ÀÌ worker ¾²·¹µå°¡ ¿äûÀ» ¾ó¸¶¸¸Å­ ó¸®ÇÏ°í + Á×À»Áö¸¦ Á¶Á¤ÇÑ´Ù. ±ÇÀåÇÏ´Â ±âº»°ª + MaxRequestsPerChild 0À» »ç¿ëÇÏ¸é ¾²·¹µå´Â + Á×Áö¾Ê°í ¿µ¿øÈ÷ ¿äûÀ» ¼­ºñ½ºÇÑ´Ù. Ưº°ÇÑ ÀÌÀ¯°¡ ¾ø´Ù¸é + NetWare¿¡¼­´Â ÀÌ Áö½Ã¾î¸¦ 0À¸·Î ¼³Á¤Çϱæ + ±ÇÇÑ´Ù.

    + +

    StartThreads - + ÀÌ Áö½Ã¾î´Â ¼­¹ö°¡ óÀ½¿¡ ½ÃÀÛÇÒ ¾²·¹µå °³¼ö¸¦ °áÁ¤ÇÑ´Ù. + ±ÇÀåÇÏ´Â ±âº»°ªÀº StartThreads 50ÀÌ´Ù.

    + +

    MinSpareThreads - + ¼­¹ö´Â ½¬´Â(idle) ¾²·¹µå °³¼ö°¡ ÀÌ °ªº¸´Ù ÀûÀ¸¸é worker + ¾²·¹µå¸¦ ´õ ¸¸µç´Ù. ±ÇÀåÇÏ´Â ±âº»°ªÀº + MinSpareThreads 10ÀÌ´Ù.

    + +

    MaxSpareThreads - + ¼­¹ö´Â ½¬´Â ¾²·¹µå °³¼ö°¡ ÀÌ °ªº¸´Ù ¸¹À¸¸é worker ¾²·¹µå¸¦ + Á×À̱⠽ÃÀÛÇÑ´Ù. ±ÇÀåÇÏ´Â ±âº»°ªÀº + MaxSpareThreads 100ÀÌ´Ù.

    + +

    MaxThreads - + ÀÌ Áö½Ã¾î´Â worker ¾²·¹µåÀÇ ÃÖ´ë °³¼ö¸¦ Á¦ÇÑÇÑ´Ù. ±ÇÀåÇÏ´Â + ±âº»°ªÀº ThreadsPerChild 250ÀÌ´Ù.

    + +

    ThreadStackSize - + ÇÑ worker ¾²·¹µå°¡ »ç¿ëÇÒ ½ºÅà ũ±â¸¦ Áö½ÃÇÑ´Ù. ±ÇÀåÇÏ´Â + ±âº»°ªÀº ThreadStackSize 65536ÀÌ´Ù.

    +
    • + +
  • +

    ¾Æ±Ô¸ÕÆ®·Î ÆÄÀϸíÀ» ¹Þ´Â Áö½Ã¾î¿¡´Â À¯´Ð½º ÆÄÀϸíÀÌ + ¾Æ´Ñ NetWare ÆÄÀϸíÀ» »ç¿ëÇØ¾ß ÇÑ´Ù. ±×·¯³ª ¾ÆÆÄÄ¡°¡ + ³»ºÎÀûÀ¸·Î À¯´Ð½º½Ä ÆÄÀϸíÀ» »ç¿ëÇϱ⶧¹®¿¡ ¹é½½·¡½¬ + ´ë½Å ½½·¡½¬¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù. ¸ðµç Àý´ë°æ·Î¿¡ º¼·ý¸íÀ» + Æ÷ÇÔÇÏ±æ ¹Ù¶õ´Ù. º¼·ý¸íÀ» »ý·«ÇÏ¸é ¾ÆÆÄÄ¡´Â + SYS: º¼·ýÀ̶ó°í À߸ø °¡Á¤ÇÒ ¼ö ÀÖ´Ù.

    +
    • + +
  • +

    NetWare¿ë ¾ÆÆÄÄ¡´Â ¼­¹ö¸¦ ´Ù½Ã ÄÄÆÄÀÏÇÏÁö ¾Ê°í ½ÇÇàÇÒ¶§ + ¸ðµâÀ» ÀоîµéÀÏ ¼ö ÀÖ´Ù. º¸Åë ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇϸé + \Apache2\modules µð·ºÅ丮¿¡ ¿©·¯ Ãß°¡ ¸ðµâÀ» + ¼³Ä¡ÇÑ´Ù. À̵é ȤÀº ´Ù¸¥ ¸ðµâÀ» »ç¿ëÇÏ·Á¸é LoadModule Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. + ¿¹¸¦ µé¾î status ¸ðµâÀ» »ç¿ëÇÑ´Ù¸é:

    + +

    + LoadModule status_module modules/status.nlm +

    + +

    ÀоîµéÀÏ ¼ö + ÀÖ´Â ¸ðµâ ¸¸µé±â¿¡ ´ëÇÑ Á¤º¸µµ ÀÖ´Ù.

    +
    • +
+ +

ÀÌ¿ÜÀÇ NetWare Àü¿ë Áö½Ã¾îµé:

+ + + +
    +
  • CGIMapExtension - + CGI ÆÄÀÏ È®ÀåÀÚ¸¦ ½ºÅ©¸³Æ® ÀÎÅÍÇÁ¸®ÅÍ¿Í ¿¬°áÇÑ´Ù.
    • +
+
    +
  • SecureListen - + ƯÁ¤ Æ÷Æ®¸¦ SSL ¾ÏȣȭÇÑ´Ù.
    • +
+
    +
  • NWSSLTrustedCerts - + ÇÁ·Ï½ÃÇÏ´Â ¼­¹ö¿¡ º¸¾È¿¬°áÇÒ¶§ »ç¿ëÇÒ ½Å·ÚÇÏ´Â + ÀÎÁõ¼­(certificate)¸¦ Ãß°¡ÇÑ´Ù.
    • +
+
    +
  • NWSSLUpgradeable - + ƯÁ¤ ÁÖ¼Ò/Æ÷Æ®·Î ¸Î¾îÁø ¿¬°áÀ» SSL ¿¬°á·Î º¯°æÇÒ ¼ö + ÀÖ´Ù.
    • +
+ + + +
top
+
+

Netware¿ë ¾ÆÆÄÄ¡ ÄÄÆÄÀÏÇϱâ

+ + + +

¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÏ·Á¸é MetroWerks CodeWarrior 6.x ÀÌ»óÀÌ + ÇÊ¿äÇÏ´Ù. ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÏ¸é ¾î¶² Netware º¼·ý¿¡¶óµµ ¼³Ä¡ÇÒ + ¼ö ÀÖ´Ù. ±âº»°ªÀº sys:/Apache2 µð·ºÅ丮´Ù.

+ +

¼­¹ö¸¦ ½ÇÇàÇϱâ Àü¿¡ conf µð·ºÅ丮¸¦ ÀÛ¼ºÇØ¾ß + ÇÑ´Ù. ¹èÆ÷º»ÀÇ conf µð·ºÅ丮¿¡ ÀÖ´Â + HTTPD-STD.CONF ÆÄÀϸíÀ» HTTPD.CONF·Î + º¯°æÇÑ´Ù. HTTPD.CONF ÆÄÀÏ¿¡¼­ @@Value@@ + Ç¥½Ã¸¦ ã¾Æ¼­ ÀûÀýÇÑ ¼³Á¤À¸·Î ´ëüÇÑ´Ù. conf/magic°ú + conf/mime.types ÆÄÀϵµ º¹»çÇÑ´Ù. ¾Æ´Ï¸é makefileÀ» + ½ÇÇàÇÒ¶§ install Å°¿öµå¸¦ »ç¿ëÇÏ¸é ¿ÏÀüÇÑ ¹èÆ÷º»À» + ¸¸µç´Ù.

+ +

¿ä±¸»çÇ×:

+ + + +

NetWare¿ë ¾ÆÆÄÄ¡ 2.0À» ÄÄÆÄÀÏÇÏ·Á¸é ´ÙÀ½ °³¹ßµµ±¸°¡ + ÇÊ¿äÇÏ´Ù:

+ + + + + +

NetWare makefileÀ» »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡ ÄÄÆÄÀÏÇϱâ:

+ + + +
    +
  • NOVELLLIBC ȯ°æº¯¼ö¸¦ +

    Set NOVELLLIBC=c:\novell\ndk\libc

    ¿Í + °°ÀÌ NetWare Libraries for C SDK À§Ä¡·Î ¼³Á¤ÇÑ´Ù. +
    • + +
  • METROWERKS ȯ°æº¯¼ö¸¦ +

    Set METROWERKS=C:\Program Files\Metrowerks\CodeWarrior

    ¿Í + °°ÀÌ Metrowerks CodeWarrior ÄÄÆÄÀÏ·¯¸¦ ¼³Ä¡ÇÑ À§Ä¡·Î + ¼³Á¤ÇÑ´Ù. ±âº» À§Ä¡ÀÎ + C:\Program Files\Metrowerks\CodeWarrior¿¡ + ¼³Ä¡ÇÏ¿´´Ù¸é, ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÒ ÇÊ¿ä´Â ¾ø´Ù.
    • + +
  • LDAPSDK ȯ°æº¯¼ö¸¦ +

    Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc

    ¿Í + °°ÀÌ LDAP Libraries for C¸¦ ¼³Ä¡ÇÑ À§Ä¡·Î ¼³Á¤ÇÑ´Ù. +
    • + +
  • ZLIBSDK ȯ°æº¯¼ö¸¦ +

    Set ZLIBSDK=D:\NOVELL\zlib

    °ú °°ÀÌ + ZLib ¶óÀ̺귯¸® ¼Ò½ºÄÚµå À§Ä¡·Î ¼³Á¤ÇÑ´Ù. +
    • + +
  • AP_WORK ȯ°æº¯¼ö¸¦ \httpd-2.0 + µð·ºÅ丮ÀÇ Àüü °æ·Î·Î ¼³Á¤ÇÑ´Ù.
    • + +
  • APR_WORK ȯ°æº¯¼ö¸¦ + \httpd-2.0\srclib\apr µð·ºÅ丮ÀÇ Àüü °æ·Î·Î + ¼³Á¤ÇÑ´Ù.
    • + +
  • AWK µµ±¸¿Í GNU make (gmake.exe) µµ±¸°¡ + ½Ã½ºÅÛÀÇ PATH ȯ°æº¯¼ö¿¡ Æ÷ÇÔµÇÀÖ´ÂÁö + È®ÀÎÇÑ´Ù.
    • + +
  • ¼Ò½ºÄڵ带 ´Ù¿î¹Þ¾Æ Àû´çÇÑ µð·ºÅ丮¿¡ ¾ÐÃàÀ» Ǭ´Ù.
    • + +
  • \httpd-2.0\srclib\apr-util\uri µð·ºÅ丮¿¡¼­ + "gmake -f nwgnumakefile"À» ½ÇÇàÇÏ¿© + GENURI.nlmÀ» ÄÄÆÄÀÏÇÑ´Ù.
    • + +
  • GENURI.nlm ÆÄÀÏÀ» NetWare ¼­¹öÀÇ + SYS: º¼·ýÀ¸·Î º¹»çÇÏ°í +

    SYS:\genuri > sys:\uri_delims.h

    + ¸í·ÉÀ» ½ÇÇàÇÑ´Ù. +
    • + +
  • uri_delims.h ÆÄÀÏÀ» ÄÄÆÄÀÏÇÏ´Â ÄÄÇ»ÅÍÀÇ + \httpd-2.0\srclib\apr-util\uri µð·ºÅ丮·Î + º¹»çÇÑ´Ù.
    • + +
  • \httpd-2.0\srclib\apr µð·ºÅ丮¿¡¼­ + "gmake -f nwgnumakefile"À» ½ÇÇàÇÏ¿© APRÀ» + ÄÄÆÄÀÏÇÑ´Ù.
    • + +
  • \httpd-2.0\srclib\pcre µð·ºÅ丮¿¡¼­ + "gmake -f nwgnumakefile"À» ½ÇÇàÇÏ¿© + DFTABLES.nlmÀ» ÄÄÆÄÀÏÇÑ´Ù.
    • + +
  • \httpd-2.0\server µð·ºÅ丮¿¡¼­ + "gmake -f nwgnumakefile"À» ½ÇÇàÇÏ¿© + GENCHARS.nlmÀ» ÄÄÆÄÀÏÇÑ´Ù.
    • + +
  • °¢ µð·ºÅ丮ÀÇ GENCHARS.nlm°ú + DFTABLES.nlm ÆÄÀÏÀ» NetWare ¼­¹öÀÇ + SYS: º¼·ýÀ¸·Î º¹»çÇÏ°í ´ÙÀ½°ú °°ÀÌ ½ÇÇàÇÑ´Ù: +

    + SYS:\genchars > sys:\test_char.h
    + SYS:\dftables > sys:\chartables.c
    +

    +
    • + +
  • test_char.h¿Í chartables.c + ÆÄÀÏÀ» ÄÄÆÄÀÏÇÏ´Â ÄÄÇ»ÅÍÀÇ \httpd-2.0\os\netware + µð·ºÅ丮·Î º¹»çÇÑ´Ù.
    • + +
  • \httpd-2.0 µð·ºÅ丮¿¡¼­ + "gmake -f nwgnumakefile"À» ½ÇÇàÇÏ¿© ¾ÆÆÄÄ¡¸¦ + ÄÄÆÄÀÏÇÑ´Ù. +

    gmake -f nwgnumakefile install

    °ú + °°ÀÌ install ÆĶó¹ÌÅ͸¦ Ãß°¡ÇÏ¸é ¹èÆ÷¿ë µð·ºÅ丮¸¦ ¸¸µé + ¼ö ÀÖ´Ù. +
    • +
+ + + +

Ãß°¡ make ¿É¼Ç

+ + + +
    +
  • gmake -f nwgnumakefile

    ÀÏ¹Ý ½ÇÇàÆÄÀÏÀ» + ÄÄÆÄÀÏÇÏ¿© \release µð·ºÅ丮·Î º¹»çÇÑ´Ù.

    • + +
  • gmake -f nwgnumakefile DEBUG=1

    µð¹ö±×¿ë + ½ÇÇàÆÄÀÏÀ» ÄÄÆÄÀÏÇÏ¿© \debug µð·ºÅ丮·Î + º¹»çÇÑ´Ù.

    • + +
  • gmake -f nwgnumakefile install +

    \dist\Apache2 µð·ºÅ丮¿¡ ½ÇÇàÆÄÀÏ, ¹®¼­, + Ãß°¡ Áö¿øÆÄÀÏÀ» Æ÷ÇÔÇÑ ¿ÏÀüÇÑ ¾ÆÆÄÄ¡ ¹èÆ÷º»À» ¸¸µç´Ù.

    • + +
  • gmake -f nwgnumakefile installdev +

    install°ú ºñ½ÁÇÏÁö¸¸, \lib°ú + \include µð·ºÅ丮¸¦ ¸¸µé°í Çì´õÆÄÀÏ°ú import + ÆÄÀÏÀ» º¹»çÇÑ´Ù.

    • + +
  • gmake -f nwgnumakefile clean +

    DEBUG Á¤ÀÇ À¯¹«¿¡ µû¶ó \release³ª + \debug¿¡ ÀÖ´Â ¿ÀºêÁ§Æ®ÆÄÀÏ°ú ½ÇÇàÆÄÀÏÀ» + ¸ðµÎ Áö¿î´Ù.

    • + +
  • gmake -f nwgnumakefile clobber_all

    clean°ú + ºñ½ÁÇÏÁö¸¸ µð·ºÅ丮µµ Áö¿î´Ù.

    • +
+ + + +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/platform/perf-hp.html b/docs/manual/platform/perf-hp.html new file mode 100644 index 00000000..23995ca4 --- /dev/null +++ b/docs/manual/platform/perf-hp.html @@ -0,0 +1,7 @@ +URI: perf-hp.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: perf-hp.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/perf-hp.html.en b/docs/manual/platform/perf-hp.html.en new file mode 100644 index 00000000..ec75a0a9 --- /dev/null +++ b/docs/manual/platform/perf-hp.html.en @@ -0,0 +1,105 @@ + + + +Running a High-Performance Web Server on HPUX - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

Running a High-Performance Web Server on HPUX

+
+

Available Languages:  en  | + ko 

+
+ + +
+Date: Wed, 05 Nov 1997 16:59:34 -0800
+From: Rick Jones <raj@cup.hp.com>
+Reply-To: raj@cup.hp.com
+Organization: Network Performance
+Subject: HP-UX tuning tips
+
+ +

Here are some tuning tips for HP-UX to add to the tuning page.

+ +

For HP-UX 9.X: Upgrade to 10.20
+ For HP-UX 10.[00|01|10]: Upgrade to 10.20

+ +

For HP-UX 10.20:

+ +

Install the latest cumulative ARPA Transport Patch. This + will allow you to configure the size of the TCP connection + lookup hash table. The default is 256 buckets and must be set + to a power of two. This is accomplished with adb against the + *disc* image of the kernel. The variable name is tcp_hash_size. + Notice that it's critically important that you use "W" + to write a 32 bit quantity, not "w" to write a 16 bit + value when patching the disc image because the tcp_hash_size + variable is a 32 bit quantity.

+ +

How to pick the value? Examine the output of ftp://ftp.cup.hp.com/dist/networking/tools/connhist + and see how many total TCP connections exist on the system. You + probably want that number divided by the hash table size to be + reasonably small, say less than 10. Folks can look at HP's + SPECweb96 disclosures for some common settings. These can be + found at http://www.specbench.org/. + If an HP-UX system was performing at 1000 SPECweb96 connections + per second, the TIME_WAIT time of 60 seconds would mean + 60,000 TCP "connections" being tracked.

+ +

Folks can check their listen queue depths with ftp://ftp.cup.hp.com/dist/networking/misc/listenq.

+ +

If folks are running Apache on a PA-8000 based system, they + should consider "chatr'ing" the Apache executable to have a + large page size. This would be "chatr +pi L <BINARY>". + The GID of the running executable must have MLOCK privileges. + Setprivgrp(1m) should be consulted for assigning + MLOCK. The change can be validated by running Glance + and examining the memory regions of the server(s) to make sure that + they show a non-trivial fraction of the text segment being locked.

+ +

If folks are running Apache on MP systems, they might + consider writing a small program that uses mpctl() + to bind processes to processors. A simple pid % numcpu + algorithm is probably sufficient. This might even go into the + source code.

+ +

If folks are concerned about the number of FIN_WAIT_2 + connections, they can use nettune to shrink the value of + tcp_keepstart. However, they should be careful there - + certainly do not make it less than oh two to four minutes. If + tcp_hash_size has been set well, it is probably OK to + let the FIN_WAIT_2's take longer to timeout (perhaps + even the default two hours) - they will not on average have a big + impact on performance.

+ +

There are other things that could go into the code base, but + that might be left for another email. Feel free to drop me a + message if you or others are interested.

+ +

sincerely,

+ +

rick jones

+ +

http://www.cup.hp.com/netperf/NetperfPage.html

+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/perf-hp.html.ko.euc-kr b/docs/manual/platform/perf-hp.html.ko.euc-kr new file mode 100644 index 00000000..1ff682c4 --- /dev/null +++ b/docs/manual/platform/perf-hp.html.ko.euc-kr @@ -0,0 +1,100 @@ + + + +HPUX¿¡¼­ °í¼º´É À¥¼­¹ö ½ÇÇàÇϱâ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

HPUX¿¡¼­ °í¼º´É À¥¼­¹ö ½ÇÇàÇϱâ

+
+

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

+
+ + +
+Date: Wed, 05 Nov 1997 16:59:34 -0800
+From: Rick Jones <raj@cup.hp.com>
+Reply-To: raj@cup.hp.com
+Organization: Network Performance
+Subject: HP-UX tuning tips
+
+ +

ÀÌ ±ÛÀº ¼º´ÉÇâ»ó ÆäÀÌÁö¿¡ Ãß°¡ÇÒ HP-UX ¼º´ÉÇâ»ó ÆÁÀÌ´Ù.

+ +

HP-UX 9.X´Â: 10.20À¸·Î ¾÷±×·¹À̵åÇ϶ó
+ HP-UX 10.[00|01|10]Àº: 10.20À¸·Î ¾÷±×·¹À̵åÇ϶ó

+ +

HP-UX 10.20˼:

+ +

ÃÖ±Ù ARPA Transport ÆÐÄ¡ ¸ðÀ½À» ¼³Ä¡ÇÑ´Ù. ±×·¯¸é TCP + ¿¬°áã±â Çؽ¬Å×À̺í Å©±â¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. ±âº»°ªÀº + 256 °³ÀÌ°í, 2ÀÇ °ÅµìÁ¦°ö°ªÀ¸·Î ÁöÁ¤ÇØ¾ß ÇÑ´Ù. adb·Î Ä¿³ÎÀÇ + *disc* À̹ÌÁö¸¦ ¼öÁ¤ÇÏ¿© ¼³Á¤ÇÑ´Ù. º¯¼ö¸íÀº + tcp_hash_sizeÀÌ´Ù. tcp_hash_size + º¯¼ö°ªÀÌ 32ºñÆ®À̹ǷΠdisc À̹ÌÁö¸¦ ¼öÁ¤ÇÒ¶§ ¹Ýµå½Ã 16ºñÆ® + °ªÀ» ±â·ÏÇÏ´Â "w" ´ë½Å 32ºñÆ® °ªÀ» ±â·ÏÇÏ´Â + "W"¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù.

+ +

¾î¶² °ªÀ» °í¸¦±î? ftp://ftp.cup.hp.com/dist/networking/tools/connhistÀÇ + °á°ú¸¦ º¸°í, ½Ã½ºÅÛ¿¡ Á¸ÀçÇÏ´Â TCP ¿¬°á ÃÑ°³¼ö¸¦ »ìÆìºÁ¶ó. + ÀÌ ¼ýÀÚ¸¦ Çؽ¬Å×À̺í Å©±â·Î ³ª´« °ªÀÌ »ó´çÈ÷ (10 ÀÌÇÏ) ÀÛÀ¸¸é + ÁÁ´Ù. HPÀÇ SPECweb96 °á°ú¿¡¼­ ÀϹÝÀûÀÎ ¼³Á¤À» º¼ ¼ö ÀÖ´Ù. + °á°ú´Â http://www.specbench.org/¿¡ + ÀÖ´Ù. HP-UX ½Ã½ºÅÛÀÌ ÃÊ´ç 1000¹ø SPECweb96 ¿¬°áÀ» ÇÏ´Â °æ¿ì + TIME_WAIT°¡ 60Ãʶó¸é 60,000°³ÀÇ TCP "¿¬°á"À» + ÃßÀûÇÑ´Ù´Â ¶æÀÌ´Ù.

+ +

ftp://ftp.cup.hp.com/dist/networking/misc/listenq¸¦ + ½ÇÇàÇÏ¿© ½Ã½ºÅÛÀÇ ¿¬°á´ë±âÇà·Ä ±íÀ̸¦ ¾Ë ¼ö ÀÖ´Ù.

+ +

PA-8000±â¹Ý ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÑ´Ù¸é, ¾ÆÆÄÄ¡ + ½ÇÇàÆÄÀÏÀÌ Å« ÆäÀÌÁöÅ©±â¸¦ »ç¿ëÇϵµ·Ï "chatr"ÇÑ´Ù. ¸í·ÉÀº + "chatr +pi L <½ÇÇàÆÄÀÏ>"ÀÌ´Ù. ½ÇÇàÆÄÀÏÀ» + ½ÇÇàÇÏ´Â GID¿¡ MLOCK ±ÇÇÑÀÌ ¹Ýµå½Ã ÇÊ¿äÇÏ´Ù. + MLOCK ºÎ¿©¿¡ ´ëÇؼ­´Â Setprivgrp(1m)¸¦ + Âü°íÇ϶ó. ¼öÁ¤ÈÄ Glance¸¦ ½ÇÇàÇÏ¿© ¼­¹öÀÇ ¸Þ¸ð¸®¿µ¿ªÀ» »ìÆ캸¸é + »ó´çÇÑ text ¼¼±×¸ÕÆ®°¡ Àá°ÜÀÖÀ½À» È®ÀÎÇÒ ¼ö ÀÖ´Ù.

+ +

´ÙÁßÇÁ·Î¼¼½º ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÑ´Ù¸é, ÇÁ·Î¼¼½º¸¦ + ÇÁ·Î¼¼½º¿¡ ¹èÁ¤ÇÏ´Â mpctl()¸¦ »ç¿ëÇÑ ÀÛÀº + ÇÁ·Î±×·¥À» ÀÛ¼ºÇغÁ¶ó. ´Ü¼øÇÑ pid % numcpu + ¾Ë°í¸®ÁòÀ¸·Îµµ ÃæºÐÇÒ °ÍÀÌ´Ù. ÀÌ ºÎºÐÀº ¾ÕÀ¸·Î ¼Ò½ºÄڵ忡 + Æ÷Ç﵃ ¼ö ÀÖ´Ù.

+ +

FIN_WAIT_2 ¿¬°áÀÇ °³¼ö°¡ °ÆÁ¤½º·´´Ù¸é, + nettuneÀ» »ç¿ëÇÏ¿© tcp_keepstart °ªÀ» ÁÙÀÏ + ¼ö ÀÖ´Ù. ±×·¯³ª Á¶½ÉÇØ¾ß ÇÑ´Ù - 4ºÐ º¸´Ù ÀÛ°Ô ¼³Á¤ÇÏÁö ¸¶¶ó. + tcp_hash_size¸¦ Àß ¼³Á¤ÇÏ¿´´Ù¸é, + FIN_WAIT_2 °ªÀÌ Ä¿µµ (½ÉÁö¾î ±âº»°ªÀÎ 2½Ã°£µµ) + ¹®Á¦¾ø´Ù - º¸Åë ¼º´É¿¡ Å« ¿µÇâÀ» ÁÖÁö ¾Ê´Â´Ù.

+ +

¾ÕÀ¸·Î ¼Ò½ºÄڵ忡 Æ÷Ç﵃ ºÎºÐÀÌ ´õ ÀÖÁö¸¸, ¿©±â¼­ ÁÙÀδÙ. + °ü½ÉÀÌ ÀÖ´Ù¸é ¸ÞÀÏÀ» ÁÖ±æ ¹Ù¶õ´Ù.

+ +

±×·³ À̸¸,

+ +

rick jones

+ +

http://www.cup.hp.com/netperf/NetperfPage.html

+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/platform/win_compiling.html b/docs/manual/platform/win_compiling.html new file mode 100644 index 00000000..6f9885da --- /dev/null +++ b/docs/manual/platform/win_compiling.html @@ -0,0 +1,7 @@ +URI: win_compiling.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: win_compiling.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/win_compiling.html.en b/docs/manual/platform/win_compiling.html.en new file mode 100644 index 00000000..140eac15 --- /dev/null +++ b/docs/manual/platform/win_compiling.html.en @@ -0,0 +1,435 @@ + + + +Compiling Apache for Microsoft Windows - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

Compiling Apache for Microsoft Windows

+
+

Available Languages:  en  | + ko 

+
+ + +

There are many important points before you begin compiling + Apache. See Using Apache with Microsoft + Windows before you begin.

+ +
+ +
top
+
+

Requirements

+ + + +

Compiling Apache requires the following environment to be + properly installed:

+ +
    +
  • +

    Disk Space

    +

    Make sure you have at least 50 MB of free disk space + available. After installation Apache requires approximately + 10 MB of disk space, plus space for log and cache files, + which can grow rapidly. The actual disk space requirements + will vary considerably based on your chosen configuration and + any third-party modules or libraries.

    +
    • + +
  • +

    Microsoft Visual C++ 5.0 or higher.

    +

    Apache can be built using the command line tools, or from + within the Visual Studio IDE Workbench. The command line + build requires the environment to reflect the PATH, + INCLUDE, LIB and other variables + that can be configured with the vcvars32 batch file:

    + +

    + "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat" +

    +
    • + +
  • +

    The Windows Platform SDK.

    +

    Visual C++ 5.0 builds require an updated Microsoft Windows + Platform SDK to enable some Apache features. For command line + builds, the Platform SDK environment is prepared by the + setenv batch file:

    + +

    + "c:\Program Files\Platform SDK\setenv.bat" +

    + +

    The Platform SDK files distributed with Visual C++ 6.0 and + later are sufficient, so users of later version may skip + this requirement.

    + +
    Note that the Windows Platform SDK update is required + to enable all supported mod_isapi features. + Without a recent update, Apache will issue warnings under + MSVC++ 5.0 that some mod_isapi features + will be disabled. Look for the update at http://msdn.microsoft.com/downloads/sdks/platform/platform.asp.
    +
    • + +
  • +

    The awk utility (awk, gawk or similar).

    +

    To install Apache within the build system, several files are + modified using the awk.exe utility. awk was chosen since it + is a very small download (compared with Perl or WSH/VB) and + accomplishes the task of generating files. Brian Kernighan's + http://cm.bell-labs.com/cm/cs/who/bwk/ + site has a compiled native Win32 binary, + http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe which + you must save with the name awk.exe rather than + awk95.exe.

    + +
    Note that Developer Studio IDE will only find + awk.exe from the Tools menu Options... Directories + tab (the Projects - VC++ Directories pane in Developer Studio 7.0) + listing Executable file paths. Add the path for awk.exe + to this list, and your system PATH environment variable, + as needed.
    + +
    Also note that if you are using Cygwin (http://www.cygwin.com/) the awk utility is named gawk.exe and + that the file awk.exe is really a symlink to the gawk.exe + file. The Windows command shell does not recognize symlinks, and because of that + building InstallBin will fail. A workaround is to delete awk.exe from + the cygwin installation and rename gawk.exe to awk.exe.
    +
    • + +
  • +

    [Optional] OpenSSL libraries (for mod_ssl + and ab.exe with ssl support)

    +

    Caution: there are significant restrictions and + prohibitions on the use and distribution of strong cryptography + and patented intellectual property throughout the world. + OpenSSL includes strong cryptography controlled by both export + regulations and domestic law, as well as intellectual property + protected by patent, in the United States and elsewhere. Neither + the Apache Software Foundation nor the OpenSSL project can provide + legal advise regarding possession, use, or distribution of the code + provided by the OpenSSL project. Consult your own legal + counsel, you are responsible for your own actions.

    + +

    OpenSSL must be installed into a srclib subdirectory named + openssl, obtained from http://www.openssl.org/source/, in order to compile mod_ssl + or the abs project (ab.exe with SSL support.) To prepare OpenSSL + for both release and debug builds of Apache, and + disable the patent protected features in OpenSSL, you might use the following + build commands:

    + +

    + perl Configure VC-WIN32
    + perl util\mkfiles.pl >MINFO
    + perl util\mk1mf.pl dll no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.rel
    + perl util\mk1mf.pl dll debug no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.dbg
    + perl util\mkdef.pl 32 libeay no-asm no-mdc2 no-rc5 no-idea >ms\libeay32.def
    + perl util\mkdef.pl 32 ssleay no-asm no-mdc2 no-rc5 no-idea >ms\ssleay32.def
    + nmake -f makefile.rel
    + nmake -f makefile.dbg +

    + +

    Note; you can use the scripts in the ms\ subdirectory, however, + it's rather tricky to force ms\do_masm.bat, for example, to perform + the patent encumberances as mentioned above. Patches to add the $* argument list + to the appropriate .bat lines in these scripts aren't incorporated, thus far.

    +
    • + +
  • +

    [Optional] zlib library (for mod_deflate)

    +

    Zlib must be installed into a srclib subdirectory named + zlib. This must be built in-place. Zlib can be obtained + from http://www.zlib.net/ -- the + mod_deflate is confirmed to work correctly with + version 1.2.3.

    + +

    + nmake -f win32\Makefile.msc
    + nmake -f win32\Makefile.msc test +

    +
    • + +
+ +
top
+
+

Command-Line Build

+ + + +

First, unpack the Apache distribution into an appropriate + directory. Open a command-line prompt and cd to that + directory.

+ +

The master Apache makefile instructions are contained in the + Makefile.win file. To compile Apache on Windows + NT, simply use one of the following commands to compiled the + release or debug build, respectively:

+ + 
+nmake /f Makefile.win _apacher
+
+nmake /f Makefile.win _apached
+
+ +

Either command will compile Apache. The latter will include + debugging information in the resulting files, making it easier + to find bugs and track down problems.

+ +
top
+
+

Developer Studio Workspace IDE Build

+ + + +

Apache can also be compiled using VC++'s Visual Studio + development environment. To simplify this process, a + Visual Studio workspace, Apache.dsw, is provided. + This workspace exposes the entire list of working .dsp + projects that are required for the complete Apache binary release. + It includes dependencies between the projects to assure that they + are built in the appropriate order.

+ +

Open the Apache.dsw workspace, and select + InstallBin (Release or Debug build, + as desired) as the Active Project. InstallBin causes all + related project to be built, and then invokes Makefile.win to + move the compiled executables and dlls. You may personalize the + INSTDIR= choice by changing InstallBin's Settings, + General tab, Build command line entry. INSTDIR defaults to the + /Apache2 directory. If you only want a test compile (without + installing) you may build the BuildBin project instead.

+ +

The .dsp project files are distributed in Visual + C++ 6.0 format. Visual C++ 5.0 (97) will recognize them. Visual C++ + 7.0 (.net) must convert Apache.dsw plus the .dsp + files into an Apache.sln plus .msproj files, + be sure you reconvert the .msproj file if any of the source + .dsp files change! This is really trivial, just open + Apache.dsw in the VC++ 7.0 IDE once again.

+ +

Visual C++ 7.0 (.net) users should also use the Build + menu, Configuration Manager dialog to uncheck both the Debug + and Release Solution modules abs, mod_ssl + and mod_deflate. + These modules are built by invoking nmake or the IDE directly + with the BinBuild target to build those modules explicitly, + only if the srclib directories openssl + and/or zlib exist.

+ +

Exported .mak files pose a greater hassle, but they are + required for Visual C++ 5.0 users to build mod_ssl, + abs (ab with SSL support) and/or + mod_deflate. + VC++ 7.0 (.net) users also benefit, nmake builds + are faster than binenv builds. + Build the entire project from within the VC++ 5.0 or 6.0 IDE, + then use the Project Menu Export for all makefiles. + You must build the projects first in order to create all dynamic + auto-generated targets, so that dependencies can be parsed + correctly. Run the following command to fix the paths so they + will build anywhere:

+ +

+ perl srclib\apr\build\fixwin32mak.pl +

+ +

You must type this command from the top level + directory of the httpd source tree. Every + .mak and .dep project file within + the current directory and below will be corrected, and the + timestamps adjusted to reflect the .dsp.

+ +

If you contribute back a patch that revises project files, we + must commit project files in Visual Studio 6.0 format. Changes + should be simple, with minimal compilation and linkage flags that + will be recognized by all VC++ 5.0 through 7.0 environments.

+ +
top
+
+

Project Components

+ + + +

The Apache.dsw workspace and makefile.win + nmake script both build the .dsp projects + of the Apache server in the following sequence:

+ +
    +
  1. srclib\apr\apr.dsp
    2. + +
  2. srclib\apr\libapr.dsp
    3. + +
  3. srclib\apr-util\uri\gen_uri_delims.dsp
    4. + +
  4. srclib\apr-util\xml\expat\lib\xml.dsp
    5. + +
  5. srclib\apr-util\aprutil.dsp
    6. + +
  6. srclib\apr-util\libaprutil.dsp
    7. + +
  7. srclib\pcre\dftables.dsp
    8. + +
  8. srclib\pcre\pcre.dsp
    9. + +
  9. srclib\pcre\pcreposix.dsp
    10. + +
  10. server\gen_test_char.dsp
    11. + +
  11. libhttpd.dsp
    12. + +
  12. Apache.dsp
    13. +
+ +

In addition, the modules\ subdirectory tree contains + project files for the majority of the modules.

+ +

The support\ directory contains project files for + additional programs that are not part of the Apache runtime, + but are used by the administrator to test Apache and maintain + password and log files. Windows-specific support projects are + broken out in the support\win32\ directory.

+ +
    +
  1. support\ab.dsp
    2. + +
  2. support\htdigest.dsp
    3. + +
  3. support\htpasswd.dsp
    4. + +
  4. support\logresolve.dsp
    5. + +
  5. support\rotatelogs.dsp
    6. + +
  6. support\win32\ApacheMonitor.dsp
    7. + +
  7. support\win32\wintty.dsp
    8. +
+ +

Once Apache has been compiled, it needs to be installed in + its server root directory. The default is the + \Apache2 directory, of the same drive.

+ +

To build and install all the files into the desired folder + dir automatically, use one of the following + nmake commands:

+ + 
+nmake /f Makefile.win installr INSTDIR=dir
+
+nmake /f Makefile.win installd INSTDIR=dir
+
+ +

The dir argument to INSTDIR gives + the installation directory; it can be omitted if Apache is + to be installed into \Apache2.

+ +

This will install the following:

+ +
    +
  • dir\bin\Apache.exe - Apache + executable
    • + +
  • dir\bin\ApacheMonitor.exe - Service + monitor taskbar icon utility
    • + +
  • dir\bin\htdigest.exe - Digest auth + password file utility
    • + +
  • dir\bin\htdbm.exe - SDBM auth + database password file utility
    • + +
  • dir\bin\htpasswd.exe - Basic auth + password file utility
    • + +
  • dir\bin\logresolve.exe - Log file + dns name lookup utility
    • + +
  • dir\bin\rotatelogs.exe - Log file + cycling utility
    • + +
  • dir\bin\wintty.exe - Console window + utility
    • + +
  • dir\bin\libapr.dll - Apache + Portable Runtime shared library
    • + +
  • dir\bin\libaprutil.dll - Apache + Utility Runtime shared library
    • + +
  • dir\bin\libhttpd.dll - Apache Core + library
    • + +
  • dir\modules\mod_*.so - Loadable + Apache modules
    • + +
  • dir\conf - Configuration + directory
    • + +
  • dir\logs - Empty logging + directory
    • + +
  • dir\include - C language header + files
    • + +
  • dir\lib - Link library files
    • +
+ +

Warning about building Apache from the development tree

+ + + +
Note only the .dsp files are maintained between release + builds. The .mak files are NOT regenerated, due to the tremendous + waste of reviewer's time. Therefore, you cannot rely on the NMAKE + commands above to build revised .dsp project files unless you + then export all .mak files yourself from the project. This is + unnecessary if you build from within the Microsoft + Developer Studio environment.
+ +
Also note it is very worthwhile to build the BuildBin + target project (or the command line _apacher or + _apached target) prior to exporting the make files. + Many files are autogenerated in the build process. Only a full + build provides all of the dependent files required to build proper + dependency trees for correct build behavior.
+ +

In order to create distribution .mak files, always review + the generated .mak (or .dep) dependencies for + Platform SDK or other garbage includes. The DevStudio\SharedIDE\bin\ + (VC5) or DevStudio\Common\MSDev98\bin\ (VC6) directory contains + the sysincl.dat file, which must list all exceptions. Update this + file (including both forward and backslashed paths, such as both + sys/time.h and sys\time.h) to include such dependencies. + Including local-install paths in a distributed .mak file will + cause the build to fail completely. And don't forget to run + srclib/apr/build/fixwin32mak.pl in order to fix absolute + paths within the .mak files.

+ + + +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/win_compiling.html.ko.euc-kr b/docs/manual/platform/win_compiling.html.ko.euc-kr new file mode 100644 index 00000000..1e0dd281 --- /dev/null +++ b/docs/manual/platform/win_compiling.html.ko.euc-kr @@ -0,0 +1,423 @@ + + + +Microsoft Windows¿ë ¾ÆÆÄÄ¡ ÄÄÆÄÀÏ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

Microsoft Windows¿ë ¾ÆÆÄÄ¡ ÄÄÆÄÀÏ

+
+

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

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

¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇϱâ Àü¿¡ ÁÖÀÇÇÒ Á¡ÀÌ ¸¹´Ù. ¹Ì¸® Microsoft Windows¿¡¼­ ¾ÆÆÄÄ¡ »ç¿ë¹ýÀ» + Âü°íÇ϶ó.

+ +
+ +
top
+
+

¿ä±¸»çÇ×

+ + + +

¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÏ·Á¸é ´ÙÀ½ÀÌ Á¤»óÀûÀ¸·Î ¼³Ä¡µÇ¾ß ÇÑ´Ù:

+ +
    +
  • +

    µð½ºÅ© °ø°£

    +

    ³²Àº µð½ºÅ© °ø°£ÀÌ ÃÖ¼ÒÇÑ 50 MB´Â µÇ¾ß ÇÑ´Ù. ¾ÆÆÄÄ¡ + ¼³Ä¡ÈÄ¿¡´Â »¡¸® Áõ°¡ÇÏ´Â ·Î±×¿Í ij½¬ÆÄÀÏÀ» Á¦¿ÜÇÏ°í + ¾à 10 MB Á¤µµ°¡ ÇÊ¿äÇÏ´Ù. ½ÇÁ¦ µð½ºÅ© »ç¿ë·®Àº ¼±ÅÃÇÑ + ±¸¼º°ú Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâ ȤÀº ¶óÀ̺귯¸®¿¡ µû¶ó Å©°Ô + ´Ù¸£´Ù.

    +
    • + +
  • +

    Microsoft Visual C++ 5.0 ÀÌ»ó.

    +

    ¾ÆÆÄÄ¡´Â ¸í·ÉÇà µµ±¸¸¦ »ç¿ëÇϰųª Visual Studio IDE + Workbench ¾È¿¡¼­ ÄÄÆÄÀÏÇÒ ¼ö ÀÖ´Ù. ¸í·ÉÇà¿¡¼­ ÄÄÆÄÀÏÇÑ´Ù¸é + vcvars32 ¹èÄ¡ÆÄÀÏÀÌ ¼³Á¤ÇÏ´Â PATH, + INCLUDE, LIB µî ȯ°æº¯¼ö°¡ + ÇÊ¿äÇÏ´Ù:

    + +

    + "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat" +

    +
    • + +
  • +

    Windows Platform SDK.

    +

    ¾î¶² ¾ÆÆÄÄ¡ ±â´ÉÀ» »ç¿ëÇÏ·Á¸é Visual C++ 5.0¿¡ Ãß°¡·Î + ÃֽŠMicrosoft Windows Platform SDK°¡ ÇÊ¿äÇÏ´Ù. ¸í·ÉÇà¿¡¼­ + ÄÄÆÄÀÏÇÑ´Ù¸é setenv ¹èÄ¡ÆÄÀÏÀÌ Platform + SDK ȯ°æÀ» ¸¸µç´Ù:

    + +

    + "c:\Program Files\Platform SDK\setenv.bat" +

    + +

    Visual C++ 6.0 ÀÌ»ó¿¡ Æ÷ÇÔµÈ Platform SDK ÆÄÀÏÀº + ÃæºÐÇÏ´Ù. ÀÌ ¹öÀüÀ» »ç¿ëÇÏ´Â »ç¿ëÀÚ´Â ÀÌ °úÁ¤À» »ý·«Çصµ + µÈ´Ù.

    + +
    ¸ðµç mod_isapi ±â´ÉÀ» »ç¿ëÇÏ·Á¸é + ÃֽŠWindows Platform SDK°¡ ÇÊ¿äÇÏ´Ù. ÃֽŠ¹öÀüÀÌ ¾Æ´Ï¸é + MSVC++ 5.0Àº mod_isapi ±â´ÉÀÇ ÀϺθ¦ + »ç¿ëÇÒ ¼ö ¾ø´Ù°í °æ°íÇÑ´Ù. http://msdn.microsoft.com/downloads/sdks/platform/platform.asp¿¡ + ÃֽŠ¹öÀüÀÌ ÀÖ´Ù.
    +
    • + +
  • +

    awk µµ±¸ (awk, gawk µî).

    +

    ÄÄÆÄÀÏÇÑ ½Ã½ºÅÛ¿¡ ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÏ·Á¸é + awk.exe µµ±¸¸¦ »ç¿ëÇÏ¿© ¿©·¯ ÆÄÀÏÀ» ¼öÁ¤ÇØ¾ß + ÇÑ´Ù. (PerlÀ̳ª WSH/VB°ú ºñ±³ÇÏ¿©) ´Ù¿î¹Þ±â¿¡ ¸Å¿ì ÀÛ°í + ÆÄÀÏ »ý¼º ÀÛ¾÷ÀÌ °¡´ÉÇÏ¿© awk¸¦ ¼±ÅÃÇß´Ù. Brian KernighanÀÇ + http://cm.bell-labs.com/cm/cs/who/bwk/ »çÀÌÆ®¿¡ + ÄÄÆÄÀÏµÈ Win32 ½ÇÇàÆÄÀÏ http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exeÀÌ + ÀÖ´Ù. À̸§À» awk95.exe ´ë½Å + awk.exe·Î º¯°æÇØ¾ß ÇÑ´Ù.

    + +
    Developer Studio IDE´Â Tools ¸Þ´º Options... + Directories ÅÇÀÇ (Developer Studio 7.0À̶ó¸é Projects + - VC++ Directories pane) Executable files °æ·Î ¸ñ·Ï¿¡¼­¸¸ + awk.exe¸¦ ã´Â´Ù. ÀÌ ¸ñ·Ï¿¡ awk.exe + °æ·Î¸¦ Ãß°¡ÇÏ°í, ÇÊ¿äÇÏ´Ù¸é PATH ȯ°æº¯¼ö¿¡µµ + Ãß°¡ÇÑ´Ù.
    + +
    CygwinÀ» (http://www.cygwin.com/) »ç¿ëÇÑ´Ù¸é + gawk.exe¶ó´Â À̸§À¸·Î awk µµ±¸°¡ ÀÖÀ¸¸ç, + awk.exe ÆÄÀÏÀº gawk.exe ÆÄÀÏÀÇ + ½Éº¼¸µÅ©ÀÓÀ» ÁÖÀÇÇ϶ó. Windows ¸í·É ÇÁ·ÒÇÁÆ®°¡ ½Éº¼¸µÅ©¸¦ + ÀνÄÇÏÁö ¸øÇϱ⶧¹®¿¡ InstallBinÀ» ÄÄÆÄÀÏÇÒ¶§ ½ÇÆÐÇÑ´Ù. + ÇØ°áÃ¥Àº cygwin¿¡¼­ awk.exe¸¦ »èÁ¦ÇÏ°í + gawk.exe À̸§À» awk.exe·Î + ¹Ù²Û´Ù.
    +
    • + +
  • +

    [¼±ÅÃÀûÀÎ] OpenSSL ¶óÀ̺귯¸® (mod_ssl°ú + ab.exeÀÇ ssl Áö¿ø¿¡ »ç¿ë)

    +

    ÁÖÀÇ: °­·ÂÇÑ ¾Ïȣȭ¿Í ƯÇã°¡ °É¸° ÁöÀûÀç»ê±ÇÀ» + Àü¼¼°è¿¡ ¹èÆ÷Çϴµ¥´Â »ó´çÇÑ Á¦¾àÀÌ ÀÖ´Ù. + OpenSSLÀº ¹Ì±¹ ¼öÃâ±ÔÁ¦¹ýÀÌ ±ÔÁ¦ÇÏ¸ç ¹Ì±¹°ú ±âŸ Áö¿ª¿¡¼­ + ƯÇã·Î º¸È£µÇ´Â ÁöÀûÀç»ê±ÇÀÎ °­·ÂÇÑ ¾Ïȣȭ¸¦ Æ÷ÇÔÇÑ´Ù. + Apache Software Foundation°ú OpenSSL ÇÁ·ÎÁ§Æ®´Â OpenSSL + ÇÁ·ÎÁ§Æ®°¡ Á¦°øÇÏ´Â Äڵ带 ¼ÒÀ¯, »ç¿ë, ¹èÆ÷Çϴµ¥ µû¸¥ + ¹ýÀû ÀÚ¹®À» Á¦°øÇÏÁö ¾Ê´Â´Ù. Á÷Á¢ ¹ý·ü »ó´ãÀ» + ¹Þ±æ ¹Ù¶õ´Ù. ´ç½Å ÇൿÀÇ Ã¥ÀÓÀº ´ç½Å¿¡°Ô ÀÖ´Ù.

    + +

    mod_sslÀ̳ª (SSLÀ» Áö¿øÇÏ´Â + ab.exe) abs ÇÁ·ÎÁ§Æ®¸¦ ÄÄÆÄÀÏÇÏ·Á¸é, OpenSSLÀ» + http://www.openssl.org/source/¿¡¼­ ´Ù¿î¹Þ¾Æ¼­ + srclibÀÇ opensslÀ̶ó´Â + ÇÏÀ§µð·ºÅ丮¿¡ ¼³Ä¡ÇØ¾ß ÇÑ´Ù. release¿Í + debug·Î ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÒ¶§ »ç¿ëÇϸç 0.9.7 + ¹öÀü¿¡ Àִ ƯÇã°¡ °É¸° ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù¸é, ¾Æ·¡ + ÄÄÆÄÀÏ ¸í·É¾î¸¦ »ç¿ëÇÑ´Ù:

    + +

    + perl Configure VC-WIN32
    + perl util\mkfiles.pl >MINFO
    + perl util\mk1mf.pl dll no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile
    + perl util\mk1mf.pl dll debug no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.dbg
    + perl util\mkdef.pl 32 libeay no-asm no-mdc2 no-rc5 no-idea >ms\libeay32.def
    + perl util\mkdef.pl 32 ssleay no-asm no-mdc2 no-rc5 no-idea >ms\ssleay32.def
    + nmake
    + nmake -f makefile.dbg +

    + +
    • + +
  • +

    [¼±ÅÃÀûÀÎ] zlib ¼Ò½º (mod_deflate¿¡ + »ç¿ë)

    +

    ZlibÀ» srclibÀÇ zlib¶ó´Â + ÇÏÀ§µð·ºÅ丮¿¡ ¼³Ä¡ÇØ¾ß ÇÏÁö¸¸, ¼Ò½º¸¦ ¹Ì¸® ÄÄÆÄÀÏÇÒ + ÇÊ¿ä´Â ¾ø´Ù. ÄÄÆÄÀÏ ½Ã½ºÅÛÀº ÀÌ ¾ÐÃà¼Ò½º¸¦ + mod_deflate ¸ðµâ°ú °°ÀÌ ÄÄÆÄÀÏÇÑ´Ù. + ZlibÀº http://www.gzip.org/zlib/¿¡¼­ ±¸ÇÒ ¼ö ÀÖ´Ù -- + mod_deflate´Â 1.1.4 ¹öÀü°ú Á¤»óÀûÀ¸·Î + ÄÄÆÄÀϵǾú´Ù.

    +
    • + +
+ +
top
+
+

¸í·ÉÇà¿¡¼­ ÄÄÆÄÀÏÇϱâ

+ + + +

¸ÕÀú Àû´çÇÑ µð·ºÅ丮¿¡ ¾ÆÆÄÄ¡ ¹èÆ÷º» ¾ÐÃàÀ» Ǭ´Ù. ¸í·ÉÇà + ÇÁ·ÒÇÁÆ®¸¦ ¿­°í ±× µð·ºÅ丮·Î cdÇÑ´Ù.

+ +

Makefile.win ÆÄÀÏ¿¡ ¾ÆÆÄÄ¡ makefile ¸í·ÉÀÌ + ÀÖ´Ù. Windows NT¿¡¼­ release¿Í debug + ÄÄÆÄÀÏÇÏ´Â ¸í·É¾î´Â °¢°¢ ´ÙÀ½°ú °°´Ù:

+ + 
+nmake /f Makefile.win _apacher
+
+nmake /f Makefile.win _apached
+
+ +

µÎ ¸í·É¾î ¸ðµÎ ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÑ´Ù. ÈÄÀÚ´Â °á°úÆÄÀÏ¿¡ + µð¹ö±ë Á¤º¸¸¦ Æ÷ÇÔÇÏ¿© ¹ö±×¸¦ ã°í ¹®Á¦¸¦ ÃßÀûÇϱ⠽±°Ô + ÇÑ´Ù.

+ +
top
+
+

Developer Studio Workspace IDE¿¡¼­ ÄÄÆÄÀÏÇϱâ

+ + + +

VC++ÀÇ Visual Studio °³¹ß ȯ°æÀ» »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÒ + ¼öµµ ÀÖ´Ù. °úÁ¤À» ½±°Ô ÇÏ·Á°í Visual Studio workspace + Apache.dsw¸¦ Á¦°øÇÑ´Ù. ÀÌ workspace´Â ¿ÏÀüÇÑ + ¾ÆÆÄÄ¡ ¹ÙÀ̳ʸ® ¹èÆ÷º»¿¡ ÇÊ¿äÇÑ .dsp ÇÁ·ÎÁ§Æ® + ¸ñ·ÏÀ» ´ã°íÀÖ´Ù. ¶Ç, ¾Ë¸ÂÀº ¼ø¼­·Î ÄÄÆÄÀÏÇϱâÀ§ÇÑ ÇÁ·ÎÁ§Æ®°£ + ÀÇÁ¸¼º Á¤º¸µµ Æ÷ÇÔÇÑ´Ù.

+ +

Apache.dsw workspace¸¦ ¿­°í + InstallBinÀ» (Release³ª + Debug Áß ¿øÇÏ´Â °ÍÀ») Active Project·Î ¼±ÅÃÇÑ´Ù. + InstallBinÀº °ü·ÃµÈ ¸ðµç ÇÁ·ÎÁ§Æ®¸¦ ÄÄÆÄÀÏÇÏ°í, + ÄÄÆÄÀÏµÈ ½ÇÇàÆÄÀÏ°ú dllÀ» ¿Å±â´Â Makefile.winÀ» + È£ÃâÇÑ´Ù. InstallBinÀÇ Settings, General ÅÇ, + Build command line Ç׸ñÀ» ¼öÁ¤ÇÏ¿© INSTDIR=À» + º¯°æÇÒ ¼ö ÀÖ´Ù. INSTDIR= ±âº»°ªÀº + /Apache2 µð·ºÅ丮ÀÌ´Ù. (¼³Ä¡ÇÏÁö¾Ê°í) Å×½ºÆ®·Î + ÄÄÆÄÀϸ¸ Çغ¸·Á¸é ´ë½Å BuildBin ÇÁ·ÎÁ§Æ®¸¦ + »ç¿ëÇÑ´Ù.

+ +

.dsp ÇÁ·ÎÁ§Æ® ÆÄÀÏÀº Visual C++ 6.0 Çü½ÄÀÌ´Ù. + Visual C++ 5.0 (97)¿¡¼­µµ ÀÌ ÆÄÀÏÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. Visual + C++ 7.0 (.net)Àº Apache.dsw¿Í .dsp + ÆÄÀϵéÀ» Apache.sln°ú .msproj + ÆÄÀϵé·Î º¯È¯ÇÑ´Ù. .dsp ¼Ò½ºÆÄÀÏÀ» ¼öÁ¤Çϸé + ¹Ýµå½Ã .msproj ÆÄÀÏ·Î ´Ù½Ã º¯È¯Ç϶ó! ±×³É VC++ + 7.0 IDE¿¡¼­ Apache.dsw¸¦ ´Ù½Ã ¿­±â¸¸ ÇÏ¸é µÈ´Ù.

+ +

¶Ç, Visual C++ 7.0 (.net) »ç¿ëÀÚ´Â Build ¸Þ´º, Configuration + Manager ´ëȭâ¿¡¼­ Debug¿Í ReleaseÀÇ + abs, mod_ssl, mod_deflate + Solution modules ¼±ÅÃÀ» ÇØÁ¦ÇØ¾ß ÇÑ´Ù. srclib¿¡ + opensslÀ̳ª zlib µð·ºÅ丮°¡ ÀÖ´Â + °æ¿ì¿¡¸¸ nmake¸¦ ½ÇÇàÇϰųª (ÀÌ ¸ðµâÀ» ¸í½ÃÀûÀ¸·Î + ÄÄÆÄÀÏÇÏ´Â) IDE BinBuild ´ë»óÀ» »ç¿ëÇÏ¿© ¸ðµâÀ» + ÄÄÆÄÀÏ ÇÒ ¼ö ÀÖ´Ù.

+ +

ExportÇÑ .mak ÆÄÀϵéÀÌ È¥¶õ½º·´Áö¸¸, Visual + C++ 5.0 »ç¿ëÀÚ°¡ mod_ssl, abs (SSLÀ» Áö¿øÇÏ´Â + ab), mod_deflate¸¦ ÄÄÆÄÀÏÇÒ¶§ ÇÊ¿äÇÏ´Ù. + VC++ 7.0 (.net) »ç¿ëÀÚ¿¡°Ôµµ binenv º¸´Ù + nmake¸¦ »ç¿ëÇϸé ÄÄÆÄÀÏÀÌ ´õ ºü¸£´Ù. VC++ 5.0À̳ª + 6.0 IDE¿¡¼­ Àüü ÇÁ·ÎÁ§Æ®¸¦ ÄÄÆÄÀÏÇÏ°í, Project ¸Þ´ºÀÇ Export + for all makefiles¸¦ »ç¿ëÇ϶ó. µ¿ÀûÀ¸·Î ÀÚµ¿ »ý¼ºÇÏ´Â ´ë»óÀ» + ¸ðµÎ ÄÄÆÄÀÏÇÏ°í ¿Ã¹Ù¸¥ ÀÇÁ¸¼º Á¤º¸¸¦ ¾ò±âÀ§Çؼ­´Â ¸ÕÀú + ÇÁ·ÎÁ§Æ®¸¦ ÄÄÆÄÀÏÇØ¾ß ÇÑ´Ù. ´ÙÀ½ ¸í·É¾î¸¦ »ç¿ëÇÏ¿© °æ·Î¸¦ + ¼öÁ¤ÇÏ¸é ¾î¶² °æ·Î¿¡¼­µµ ÄÄÆÄÀÏÇÒ ¼ö ÀÖ´Ù:

+ +

+ perl srclib\apr\build\fixwin32mak.pl +

+ +

httpd ¼Ò½º ÃÖ»óÀ§ µð·ºÅ丮¿¡¼­ + ¸í·É¾î¸¦ ½ÇÇàÇØ¾ß ÇÑ´Ù. ÇöÀç µð·ºÅ丮¿Í ÇÏÀ§µð·ºÅ丮¿¡ ÀÖ´Â + ¸ðµç .mak¿Í .dep ÇÁ·ÎÁ§Æ®ÆÄÀÏÀ» + ¼öÁ¤ÇÏ°í, .dsp¸¦ °í·ÁÇÏ¿© ÆÄÀϽð£À» ¼öÁ¤ÇÑ´Ù.

+ +

ÇÁ·ÎÁ§Æ®ÆÄÀÏÀ» ´Ùµë¾î¼­ ÆÐÄ¡¸¦ º¸³½´Ù¸é, ÇÁ·ÎÁ§Æ®ÆÄÀÏÀ» + Visual Studio 6.0 Çü½ÄÀ¸·Î ¸¸µé¾î¾ß ÇÑ´Ù. º¯°æÀº °£´ÜÇÏ°í, + VC++ 5.0¿¡¼­ 7.0±îÁö ¸ðµç ȯ°æ¿¡¼­ ÀνÄÇÏ´Â ÃÖ¼ÒÇÑÀÇ ÄÄÆÄÀÏ + ¿É¼Ç°ú ¸µÄ¿ ¿É¼ÇÀ» »ç¿ëÇØ¾ß ÇÑ´Ù.

+ +
top
+
+

ÇÁ·ÎÁ§Æ® ±¸¼º¿ä¼Ò

+ + + +

Apache.dsw workspace¿Í makefile.win + nmake ½ºÅ©¸³Æ®´Â ´ÙÀ½ ¼ø¼­´ë·Î ¾ÆÆÄÄ¡ ¼­¹ö + .dsp ÇÁ·ÎÁ§Æ®¸¦ ÄÄÆÄÀÏÇÑ´Ù:

+ +
    +
  1. srclib\apr\apr.dsp
    2. + +
  2. srclib\apr\libapr.dsp
    3. + +
  3. srclib\apr-util\uri\gen_uri_delims.dsp
    4. + +
  4. srclib\apr-util\xml\expat\lib\xml.dsp
    5. + +
  5. srclib\apr-util\aprutil.dsp
    6. + +
  6. srclib\apr-util\libaprutil.dsp
    7. + +
  7. srclib\pcre\dftables.dsp
    8. + +
  8. srclib\pcre\pcre.dsp
    9. + +
  9. srclib\pcre\pcreposix.dsp
    10. + +
  10. server\gen_test_char.dsp
    11. + +
  11. libhttpd.dsp
    12. + +
  12. Apache.dsp
    13. +
+ +

¶Ç, modules\ ÇÏÀ§µð·ºÅ丮 ¾Æ·¡ ´ëºÎºÐÀÇ + ¸ðµâ¿¡´Â ÇÁ·ÎÁ§Æ®ÆÄÀÏÀÌ ÀÖ´Ù.

+ +

support\ µð·ºÅ丮¿¡´Â ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇϴµ¥ + ÇÊ¿äÇÏÁö´Â ¾ÊÁö¸¸, °ü¸®ÀÚ°¡ ¾ÆÆÄÄ¡¸¦ °Ë»çÇϰųª ¾ÏÈ£ÆÄÀÏ°ú + ·Î±×ÆÄÀÏÀ» °ü¸®Çϴµ¥ »ç¿ëÇÒ Ãß°¡ ÇÁ·Î±×·¥µéÀÇ ÇÁ·ÎÁ§Æ®ÆÄÀÏÀÌ + ÀÖ´Ù. Windows Àü¿ë Áö¿ø ÇÁ·Î±×·¥Àº support\win32\ + µð·ºÅ丮¿¡ µû·Î ÀÖ´Ù.

+ +
    +
  1. support\ab.dsp
    2. + +
  2. support\htdigest.dsp
    3. + +
  3. support\htpasswd.dsp
    4. + +
  4. support\logresolve.dsp
    5. + +
  5. support\rotatelogs.dsp
    6. + +
  6. support\win32\ApacheMonitor.dsp
    7. + +
  7. support\win32\wintty.dsp
    8. +
+ +

¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇϸé server root µð·ºÅ丮¿¡ ¼³Ä¡ÇØ¾ß ÇÑ´Ù. + ±âº»°ªÀº °°Àº µð½ºÅ©ÀÇ \Apache2 µð·ºÅ丮ÀÌ´Ù.

+ +

ÄÄÆÄÀÏÇÏ°í ¸ðµç ÆÄÀÏÀ» ¿øÇÏ´Â Æú´õ dir¿¡ ÀÚµ¿À¸·Î + ¼³Ä¡ÇÏ·Á¸é ´ÙÀ½ nmake ¸í·É¾îÁß Çϳª¸¦ »ç¿ëÇÑ´Ù:

+ + 
+nmake /f Makefile.win installr INSTDIR=dir
+
+nmake /f Makefile.win installd INSTDIR=dir
+
+ +

INSTDIRÀÇ dir ¾Æ±Ô¸ÕÆ®´Â ¼³Ä¡µð·ºÅ丮¸¦ + ¶æÇÑ´Ù. »ý¶ôÇϸé \Apache2¿¡ ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÑ´Ù.

+ +

´ÙÀ½°ú °°ÀÌ ¼³Ä¡ÇÑ´Ù:

+ +
    +
  • dir\bin\Apache.exe - ¾ÆÆÄÄ¡ + ½ÇÇàÆÄÀÏ
    • + +
  • dir\bin\ApacheMonitor.exe - + ¼­ºñ½º °¨½Ã¿ë ÀÛ¾÷Ç¥½ÃÁÙ ¾ÆÀÌÄÜ µµ±¸
    • + +
  • dir\bin\htdigest.exe - Digest + auth ¾ÏÈ£ÆÄÀÏ µµ±¸
    • + +
  • dir\bin\htdbm.exe - SDBM auth + µ¥ÀÌÅͺ£À̽º ¾ÏÈ£ÆÄÀÏ µµ±¸
    • + +
  • dir\bin\htpasswd.exe - Basic + auth ¾ÏÈ£ÆÄÀÏ µµ±¸
    • + +
  • dir\bin\logresolve.exe - ·Î±×ÆÄÀÏ¿¡¼­ + dns À̸§À» ã´Â µµ±¸
    • + +
  • dir\bin\rotatelogs.exe - ·Î±×ÆÄÀÏ + ¼øȯ µµ±¸
    • + +
  • dir\bin\wintty.exe - ÄܼÖâ + µµ±¸
    • + +
  • dir\bin\libapr.dll - Apache + Portable Runtime °øÀ¯ ¶óÀ̺귯¸®
    • + +
  • dir\bin\libaprutil.dll - Apache + Utility Runtime °øÀ¯ ¶óÀ̺귯¸®
    • + +
  • dir\bin\libhttpd.dll - Apache + Core ¶óÀ̺귯¸®
    • + +
  • dir\modules\mod_*.so - ÀоîµéÀÏ + ¼ö ÀÖ´Â ¾ÆÆÄÄ¡ ¸ðµâ
    • + +
  • dir\conf - ¼³Á¤ µð·ºÅ丮
    • + +
  • dir\logs - ºñ¾îÀÖ´Â ·Î±× + µð·ºÅ丮
    • + +
  • dir\include - C ¾ð¾î Çì´õÆÄÀÏ
    • + +
  • dir\lib - ¸µÅ© ¶óÀ̺귯¸®ÆÄÀÏ
    • +
+ +

°³¹ßÁßÀÎ ¾ÆÆÄÄ¡ ¹öÀüÀ» ÄÄÆÄÀÏÇÒ¶§ °æ°í

+ + + +
.dsp ÆÄÀÏÀº release¸¶´Ù + »õ·Î ¸¸µé¾îÁø´Ù. °³¹ßÀÚÀÇ ½Ã°£³¶ºñ¸¦ ¸·±âÀ§ÇØ + .mak ÆÄÀÏÀº »õ·Î ¸¸µéÁö ¾Ê´Â´Ù. ±×·¯¹Ç·Î + NMAKE ¸í·É¾î¸¦ »ç¿ëÇÏ¿© »õ·Î¿î .dsp + ÇÁ·ÎÁ§Æ®ÆÄÀÏÀ» ÄÄÆÄÀÏÇÒ ¼ö ¾ø´Ù. ÇÁ·ÎÁ§Æ®¿¡¼­ Á÷Á¢ ¸ðµç + .mak ÆÄÀÏÀ» exportÇØ¾ß ÇÑ´Ù. Microsoft Developer + Studio ȯ°æ¿¡¼­ ÄÄÆÄÀÏÇÑ´Ù¸é ÀÌ ÀÛ¾÷ÀÌ ÇÊ¿ä¾ø´Ù.
+ +
¶Ç, makefileÀ» exportÇϱâ Àü¿¡ BuildBin + ÇÁ·ÎÁ§Æ®¸¦ (ȤÀº _apacher³ª _apached + ¸í·ÉÇà ´ë»ó) ÄÄÆÄÀÏÇÏ¸é ¸Å¿ì µµ¿òÀÌ µÈ´Ù. ÄÄÆÄÀÏÁß¿¡ ¸¹Àº + ÆÄÀÏÀÌ ÀÚµ¿À¸·Î ¸¸µé¾îÁø´Ù. Àüü¸¦ ÄÄÆÄÀÏÇؾ߸¸ Á¤»óÀûÀ¸·Î + ÄÄÆÄÀÏÇÒ¶§ ÇÊ¿äÇÑ ÀÇÁ¸ÆÄÀÏÀ» ¸ðµÎ ¸¸µç´Ù.
+ +

¹èÆ÷¿ë .mak ÆÄÀÏÀ» ¸¸µå·Á¸é Ç×»ó + .mak (ȤÀº .dep)¿¡¼­ Platform + SDK µîÀÇ ÀÇÁ¸¼ºÀ» Á¡°ËÇ϶ó. + DevStudio\SharedIDE\bin\ (VC5)³ª + DevStudio\Common\MSDev98\bin\ (VC6) µð·ºÅ丮¿¡´Â + ¸ðµç ¿¹¿Ü ¸ñ·ÏÀÌ ´ã±ä sysincl.dat ÆÄÀÏÀÌ + ÀÖ´Ù. ÀÌ ÆÄÀÏ¿¡ ÀÇÁ¸¼º Á¤º¸¸¦ Ãß°¡ÇÑ´Ù + (sys/time.h¿Í sys\time.h¿Í °°ÀÌ, + °æ·Î´Â ½½·¡½¬¸¦ »ç¿ëÇÑ °Í°ú ¹é½½·¡½¬¸¦ »ç¿ëÇÑ °Í ¸ðµÎ¸¦ + Ãß°¡ÇÑ´Ù). ¹èÆ÷ÇÒ .mak ÆÄÀÏ¿¡ ÇöÀç ÄÄÇ»ÅÍ¿¡¸¸ + ÇØ´çÇÏ´Â ¼³Ä¡°æ·Î°¡ ÀÖ´Ù¸é ÄÄÆÄÀÏÀÌ ¿ÏÀüÈ÷ ½ÇÆÐÇÑ´Ù. + ±×·¯¹Ç·Î srclib/apr/build/fixwin32mak.plÀ» + ½ÇÇàÇØÇÏ¿© .mak ÆÄÀÏ¿¡ ÀÖ´Â Àý´ë°æ·Î¸¦ ¾ø¾Ö¾ß + ÇÑ´Ù.

+ + + +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/platform/windows.html b/docs/manual/platform/windows.html new file mode 100644 index 00000000..dbcab1c6 --- /dev/null +++ b/docs/manual/platform/windows.html @@ -0,0 +1,7 @@ +URI: windows.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: windows.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/windows.html.en b/docs/manual/platform/windows.html.en new file mode 100644 index 00000000..11ae4b46 --- /dev/null +++ b/docs/manual/platform/windows.html.en @@ -0,0 +1,737 @@ + + + +Using Apache with Microsoft Windows - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

Using Apache with Microsoft Windows

+
+

Available Languages:  en  | + ko 

+
+ + +

This document explains how to install, configure and run + Apache 2.0 under Microsoft Windows. If you find any bugs, or + wish to contribute in other ways, please use our bug reporting + page.

+ +

This document assumes that you are installing a binary + distribution of Apache. If you want to compile Apache yourself + (possibly to help with development or tracking down bugs), + see Compiling Apache for Microsoft + Windows.

+ +

Because of the current versioning policies on Microsoft + Windows operating system families, this document assumes the + following:

+
    +
  • Windows NT: This means all versions of + Windows that are based on the Windows NT kernel. Includes Windows + NT, Windows 2000, Windows XP and Windows .Net Server 2003.
    • +
  • Windows 9x: This means older, + consumer-oriented versions of Windows. Includes Windows 95 (also + OSR2), Windows 98 and Windows ME.
    • +
+ +
+ +
top
+
+

Operating System Requirements

+ + +

The primary Windows platform for running Apache 2.0 is Windows + NT. The binary installer only works with the x86 family of + processors, such as Intel and AMD processors. Running Apache on + Windows 9x is not thoroughly tested, and it is never recommended on + production systems. +

+ +

On all operating systems, TCP/IP networking must be installed + and working. If running on Windows 95, the Winsock 2 upgrade must + be installed. Winsock 2 for Windows 95 can be downloaded from here. +

+ +

On Windows NT 4.0, installing Service Pack 6 is strongly + recommended, as Service Pack 4 created known issues with TCP/IP + and Winsock integrity that were resolved in later Service Packs.

+
top
+
+

Downloading Apache for Windows

+ + +

Information on the latest versions of Apache can be found on the + web site of the Apache web server at + http://httpd.apache.org/download.cgi. + There you will find the current release, as well as more recent alpha + or beta test versions, and a list of HTTP and FTP mirrors from which + you can download the Apache web server. Please use a mirror near to + you for a fast and reliable download.

+ +

For Windows installations you should download the version of + Apache for Windows with the .msi extension. This is a + single Microsoft Installer file, which contains a ready-to-run + version of Apache. There is a separate .zip file, + which contains only the source code. You can compile Apache + yourself with the Microsoft Visual C++ (Visual Studio) tools.

+
top
+
+

Installing Apache for Windows

+ + +

You need Microsoft Installer 1.2 or above for the installation + to work. On Windows 9x you can update your Microsoft Installer to + version 2.0 here + and on Windows NT 4.0 and 2000 the version 2.0 update can be found + here. + Windows XP does not need this update.

+ +

Note that you cannot install two versions of Apache 2.0 on the + same computer with the binary installer. You can, however, install + a version of the 1.3 series and a version of the + 2.0 series on the same computer without problems. If you need to + have two different 2.0 versions on the same computer, you have to + compile and install Apache from the + source.

+ +

Run the Apache .msi file you downloaded above. The + installation will ask you for these things:

+ +
    +

  1. Network Domain. Enter the DNS domain in which + your server is or will be registered in. For example, if your + server's full DNS name is server.mydomain.net, you would + type mydomain.net here.

    2. + +

  2. Server Name. Your server's full DNS name. + From the example above, you would type server.mydomain.net + here.

    3. + +

  3. Administrator's Email Address. Enter the + server administrator's or webmaster's email address here. This + address will be displayed along with error messages to the client + by default.

    4. + +

  4. For whom to install Apache Select for + All Users, on Port 80, as a Service - Recommended if you'd + like your new Apache to listen at port 80 for incoming traffic. + It will run as a service (that is, Apache will run even if no one + is logged in on the server at the moment) Select only for + the Current User, on Port 8080, when started Manually if + you'd like to install Apache for your personal experimenting or + if you already have another WWW server running on port 80.

    5. + +

  5. The installation type. Select Typical + for everything except the source code and libraries for module + development. With Custom you can specify what to + install. A full install will require about 13 megabytes of free + disk space. This does not include the size of your web + site(s).

    6. + +

  6. Where to install. The default path is + C:\Program Files\Apache Software Foundation + under which a directory called + Apache2.2 will be created by default.

    7. +
+ +

During the installation, Apache will configure the files in the + conf subdirectory to reflect the chosen installation + directory. However, if any of the configuration files in this + directory already exist, they will not be overwritten. Instead, the + new copy of the corresponding file will be left with the extension + .default. So, for example, if conf\httpd.conf + already exists, it will be renamed as conf\httpd.conf.default. + After the installation you should manually check to see what new + settings are in the .default file, and if necessary, + update your existing configuration file.

+ +

Also, if you already have a file called htdocs\index.html, + it will not be overwritten (and no index.html.default + will be installed either). This means it should be safe to install + Apache over an existing installation, although you would have to + stop the existing running server before doing the installation, and + then start the new one after the installation is finished.

+ +

After installing Apache, you must edit the configuration files + in the conf subdirectory as required. These files + will be configured during the installation so that Apache is ready + to be run from the directory it was installed into, with the + documents server from the subdirectory htdocs. There + are lots of other options which you should set before you really + start using Apache. However, to get started quickly, the files + should work as installed.

+
top
+
+

Customizing Apache for Windows

+ + +

Apache is configured by the files in the conf + subdirectory. These are the same files used to configure the Unix + version, but there are a few different directives for Apache on + Windows. See the directive index + for all the available directives.

+ +

The main differences in Apache for Windows are:

+
    +

  • Because Apache for Windows is multithreaded, it does not + use a separate process for each request, as Apache does on Unix. + Instead there are usually only two Apache processes running: a + parent process, and a child which handles the requests. Within + the child process each request is handled by a separate thread. +

    + +

    The process management directives are also different:

    + +

    MaxRequestsPerChild: + Like the Unix directive, this controls how many requests a single + child process will serve before exiting. However, unlike on Unix, + a single process serves all the requests at once, not just one. + If this is set, it is recommended that a very high number is + used. The recommended default, MaxRequestsPerChild 0, + causes the child process to never exit.

    + +
    Warning: The server configuration + file is reread when a new child process is started. If you have + modified httpd.conf, the new child may not start or + you may receive unexpected results.
    + +

    ThreadsPerChild: + This directive is new. It tells the server how many threads it + should use. This is the maximum number of connections the server + can handle at once, so be sure to set this number high enough for + your site if you get a lot of hits. The recommended default is + ThreadsPerChild 50.

    • + +

  • The directives that accept filenames as arguments must use + Windows filenames instead of Unix ones. However, because Apache + uses Unix-style names internally, you must use forward slashes, + not backslashes. Drive letters can be used; if omitted, the drive + with the Apache executable will be assumed.

    • + +

  • Apache for Windows contains the ability to load modules at + runtime, without recompiling the server. If Apache is compiled + normally, it will install a number of optional modules in the + \Apache2\modules directory. To activate these or + other modules, the new LoadModule + directive must be used. For example, to activate the status + module, use the following (in addition to the status-activating + directives in access.conf):

    + +

    + LoadModule status_module modules/mod_status.so +

    + +

    Information on creating + loadable modules is also available.

    • + +

  • Apache can also load ISAPI (Internet Server Application + Programming Interface) extensions (i.e. internet server + applications), such as those used by Microsoft IIS and other + Windows servers. More information + is available. Note that Apache cannot load + ISAPI Filters.

    • + +

  • When running CGI scripts, the method Apache uses to find + the interpreter for the script is configurable using the + ScriptInterpreterSource + directive.

    • + +

  • Since it is often difficult to manage files with names + like .htaccess in Windows, you may find it useful to + change the name of this per-directory configuration file using + the AccessFilename + directive.

    • + +

  • Any errors during Apache startup are logged into the + Windows event log when running on Windows NT. This mechanism + acts as a backup for those situations where Apache cannot even + access the normally used error.log file. You can + view the Windows event log by using the Event Viewer application + on Windows NT 4.0, and the Event Viewer MMC snap-in on newer + versions of Windows.

    + +
    Note that there is no startup error logging on + Windows 9x because no Windows event log exists on those operating + systems.
    • +
+ +
top
+
+

Running Apache as a Service

+ + +

Apache can be run as a service on Windows NT. There is some + highly experimental support for similar behavior on Windows 9x.

+ +

You can install Apache as a service automatically during the + installation. If you chose to install for all users, the + installation will create an Apache service for you. If you specify + to install for yourself only, you can manually register Apache as a + service after the installation. You have to be a member of the + Administrators group for the service installation to succeed.

+ +

Apache comes with a utility called the Apache Service Monitor. + With it you can see and manage the state of all installed Apache + services on any machine on your network. To be able to manage an + Apache service with the monitor, you have to first install the + service (either automatically via the installation or manually). +

+ +

You can install Apache as a Windows NT service as follows from + the command prompt at the Apache bin subdirectory:

+ +

+ httpd -k install +

+ +

If you need to specify the name of the service you want to + install, use the following command. You have to do this if you + have several different service installations of Apache on your + computer.

+ +

+ httpd -k install -n "MyServiceName" +

+ +

If you need to have specifically named configuration files for + different services, you must use this:

+ +

+ httpd -k install -n "MyServiceName" -f "c:\files\my.conf" +

+ +

If you use the first command without any special parameters except + -k install, the service will be called Apache2 + and the configuration will be assumed to be conf\httpd.conf. +

+ +

Removing an Apache service is easy. Just use:

+ +

+ httpd -k uninstall +

+ +

The specific Apache service to be uninstalled can be specified by using:

+ +

+ httpd -k uninstall -n "MyServiceName" +

+ +

Normal starting, restarting and shutting down of an Apache + service is usually done via the Apache Service Monitor, by using + commands like NET START Apache2 and NET STOP + Apache2 or via normal Windows service management. Before + starting Apache as a service by any means, you should test the + service's configuration file by using:

+ +

+ httpd -n "MyServiceName" -t +

+ +

You can control an Apache service by its command line switches, + too. To start an installed Apache service you'll use this:

+ +

+ httpd -k start +

+ +

To stop an Apache service via the command line switches, use + this:

+ +

+ httpd -k stop +

+ +

or

+ +

+ httpd -k shutdown +

+ +

You can also restart a running service and force it to reread + its configuration file by using:

+ +

+ httpd -k restart +

+ +

By default, all Apache services are registered to run as the + system user (the LocalSystem account). The + LocalSystem account has no privileges to your network + via any Windows-secured mechanism, including the file system, named + pipes, DCOM, or secure RPC. It has, however, wide privileges locally. +

+ +
Never grant any network privileges to + the LocalSystem account! If you need Apache to be able + to access network resources, create a separate account for Apache as + noted below.
+ +

You may want to create a separate account for running Apache + service(s). Especially, if you have to access network resources + via Apache, this is strongly recommended.

+ +
    +
  1. Create a normal domain user account, and be sure to + memorize its password.
    2. + +
  2. Grant the newly-created user a privilege of Log on + as a service and Act as part of the operating + system. On Windows NT 4.0 these privileges are granted via + User Manager for Domains, but on Windows 2000 and XP you probably + want to use Group Policy for propagating these settings. You can + also manually set these via the Local Security Policy MMC snap-in. +
    3. + +
  3. Confirm that the created account is a member of the Users + group.
    4. + +
  4. Grant the account read and execute (RX) rights to all document + and script folders (htdocs and cgi-bin + for example).
    5. + +
  5. Grant the account change (RWXD) rights to the + Apache logs directory.
    6. + +
  6. Grant the account read and execute (RX) rights to the + Apache.exe binary executable.
    7. +
+ +
It is usually a good practice to grant the user the Apache + service runs as read and execute (RX) access to the whole Apache2 + directory, except the logs subdirectory, where the + user has to have at least change (RWXD) rights.
+ +

If you allow the account to log in as a user and as a service, + then you can log on with that account and test that the account has the + privileges to execute the scripts, read the web pages, and that + you can start Apache in a console window. If this works, and you + have followed the steps above, Apache should execute as a service + with no problems.

+ +
Error code 2186 is a good indication that + you need to review the "Log On As" configuration for the service, + since Apache cannot access a required network resource. Also, pay + close attention to the privileges of the user Apache is + configured to run as.
+ +

When starting Apache as a service you may encounter an error + message from the Windows Service Control Manager. For example, + if you try to start Apache by using the Services applet in the + Windows Control Panel, you may get the following message:

+ +

+ Could not start the Apache2 service on \\COMPUTER
+ Error 1067; The process terminated unexpectedly. +

+ +

You will get this generic error if there is any problem with + starting the Apache service. In order to see what is really causing + the problem you should follow the instructions for Running Apache + for Windows from the Command Prompt.

+ +

There is some support for Apache on Windows 9x to behave in a + similar manner as a service on Windows NT. It is highly + experimental. It is not of production-class reliability, + and its future is not guaranteed. It can be mostly regarded as + a risky thing to play with - proceed with caution!

+ +

There are some differences between the two kinds of services + you should be aware of:

+ +
    +

  • Apache will attempt to start and if successful it will run + in the background. If you run the command

    + +

    + httpd -n "MyServiceName" -k start +

    + +

    via a shortcut on your desktop, for example, then if the + service starts successfully, a console window will flash up but + it immediately disappears. If Apache detects any errors on startup + such as incorrect entries in the httpd.conf configuration file, + the console window will remain visible. This will display an error + message which will be useful in tracking down the cause of the + problem.

    • + +

  • Windows 9x does not support NET START or + NET STOP commands. You must control the Apache + service on the command prompt via the -k switches. +

    • + +

  • Apache and Windows 9x offer no support for running Apache + as a specific user with network privileges. In fact, Windows 9x + offers no security on the local machine, either. This is the + simple reason because of which the Apache Software Foundation + never endorses use of a Windows 9x -based system as a public + Apache server. The primitive support for Windows 9x exists only + to assist the user in developing web content and learning the + Apache server, and perhaps as an intranet server on a secured, + private network.

    • + +
+ +

Once you have confirmed that Apache runs correctly as a + console application you can install, control and uninstall the + pseudo-service with the same commands as on Windows NT. You can + also use the Apache Service Monitor to manage Windows 9x + pseudo-services.

+ +
top
+
+

Running Apache as a Console Application

+ + +

Running Apache as a service is usually the recommended way to + use it, but it is sometimes easier to work from the command line + (on Windows 9x running Apache from the command line is the + recommended way due to the lack of reliable service support.)

+ +

To run Apache from the command line as a console application, + use the following command:

+ +

+ apache +

+ +

Apache will execute, and will remain running until it is stopped + by pressing Control-C.

+ +

You can also run Apache via the shortcut Start Apache in Console + placed to Start Menu --> Programs --> Apache HTTP Server + 2.0.xx --> Control Apache Server during the installation. + This will open a console window and start Apache inside it. If you + don't have Apache installed as a service, the window will remain + visible until you stop Apache by pressing Control-C in the console + window where Apache is running in. The server will exit in a few + seconds. However, if you do have Apache installed as a service, the + shortcut starts the service. If the Apache service is running + already, the shortcut doesn't do anything.

+ +

You can tell a running Apache to stop by opening another console + window and entering:

+ +

+ httpd -k shutdown +

+ +

This should be preferred over pressing Control-C because this + lets Apache end any current operations and clean up gracefully.

+ +

You can also tell Apache to restart. This forces it to reread + the configuration file. Any operations in progress are allowed to + complete without interruption. To restart Apache, use:

+ +

+ httpd -k restart +

+ +
Note for people familiar with the Unix version of Apache: + these commands provide a Windows equivalent to kill -TERM + pid and kill -USR1 pid. The + command line option used, -k, was chosen as a reminder + of the kill command used on Unix.
+ +

If the Apache console window closes immediately or unexpectedly + after startup, open the Command Prompt from the Start Menu --> + Programs. Change to the folder to which you installed Apache, type + the command httpd, and read the error message. Then + change to the logs folder, and review the error.log + file for configuration mistakes. If you accepted the defaults when + you installed Apache, the commands would be:

+ +

+ c:
+ cd "\Program Files\Apache Software Foundation\Apache2.2\bin"
+ httpd +

+ +

Then wait for Apache to stop, or press Control-C. Then enter the + following:

+ +

+ cd ..\logs
+ more < error.log +

+ +

When working with Apache it is important to know how it will + find the configuration file. You can specify a configuration file + on the command line in two ways:

+ +
    +

  • -f specifies an absolute or relative path to + a particular configuration file:

    + +

    + httpd -f "c:\my server files\anotherconfig.conf" +

    + +

    or

    + +

    + httpd -f files\anotherconfig.conf +

    • + +

  • -n specifies the installed Apache service + whose configuration file is to be used:

    + +

    + httpd -n "MyServiceName" +

    +
    • +
+ +

In both of these cases, the proper + ServerRoot should be set in + the configuration file.

+ +

If you don't specify a configuration file with -f + or -n, Apache will use the file name compiled into the + server, such as conf\httpd.conf. This built-in path + is relative to the installation directory. You can verify the compiled + file name from a value labelled as SERVER_CONFIG_FILE when + invoking Apache with the -V switch, like this:

+ +

+ httpd -V +

+ +

Apache will then try to determine its + ServerRoot by trying the following, in this order:

+ +
    +
  1. A ServerRoot directive + via the -C command line switch.
    2. + +
  2. The -d switch on the command line.
    3. + +
  3. Current working directory.
    4. + +
  4. A registry entry which was created if you did a binary + installation.
    5. + +
  5. The server root compiled into the server. This is + /apache by default, you can verify it by using + httpd -V and looking for a value labelled as + HTTPD_ROOT.
    6. +
+ +

During the installation, a version-specific registry key is + created in the Windows registry. The location of this key depends + on the type of the installation. If you chose to install Apache + for all users, the key is located under the + HKEY_LOCAL_MACHINE hive, like this (the version + numbers will of course vary between different versions of Apache: +

+ +

+ HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Apache\2.2.2 +

+ +

Correspondingly, if you chose to install Apache for the current + user only, the key is located under the HKEY_CURRENT_USER + hive, the contents of which are dependent of the user currently + logged on:

+ +

+ HKEY_CURRENT_USER\SOFTWARE\Apache Software Foundation\Apache\2.2.2 +

+ +

This key is compiled into the server and can enable you to test + new versions without affecting the current version. Of course, you + must take care not to install the new version in the same + directory as another version.

+ +

If you did not do a binary install, Apache will in some + scenarios complain about the missing registry key. This warning can + be ignored if the server was otherwise able to find its + configuration file.

+ +

The value of this key is the + ServerRoot directory which + contains the conf subdirectory. When Apache starts it + reads the httpd.conf file from that directory. If + this file contains a ServerRoot + directive which contains a different directory from the one + obtained from the registry key above, Apache will forget the + registry key and use the directory from the configuration file. If + you copy the Apache directory or configuration files to a new + location it is vital that you update the + ServerRoot directive in the + httpd.conf file to reflect the new location.

+ +
top
+
+

Testing the Installation

+ + +

After starting Apache (either in a console window or as a + service) it will be listening on port 80 (unless you changed the + Listen directive in the + configuration files or installed Apache only for the current user). + To connect to the server and access the default page, launch a + browser and enter this URL:

+ +

+ http://localhost/ +

+ +

Apache should respond with a welcome page and a link to the + Apache manual. If nothing happens or you get an error, look in the + error.log file in the logs subdirectory. + If your host is not connected to the net, or if you have serious + problems with your DNS (Domain Name Service) configuration, you + may have to use this URL:

+ +

+ http://127.0.0.1/ +

+ +

If you happen to be running Apache on an alternate port, you + need to explicitly put that in the URL:

+ +

+ http://127.0.0.1:8080/ +

+ +

Once your basic installation is working, you should configure it + properly by editing the files in the conf subdirectory. + Again, if you change the configuration of the Windows NT service + for Apache, first attempt to start it from the command line to + make sure that the service starts with no errors.

+ +

Because Apache cannot share the same port with + another TCP/IP application, you may need to stop, uninstall or reconfigure + certain other services before running Apache. These conflicting + services include other WWW servers and some firewall implementations. +

+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/windows.html.ko.euc-kr b/docs/manual/platform/windows.html.ko.euc-kr new file mode 100644 index 00000000..be6e9f49 --- /dev/null +++ b/docs/manual/platform/windows.html.ko.euc-kr @@ -0,0 +1,688 @@ + + + +Microsoft Windows¿¡¼­ ¾ÆÆÄÄ¡ »ç¿ë¹ý - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Platform Specific Notes

Microsoft Windows¿¡¼­ ¾ÆÆÄÄ¡ »ç¿ë¹ý

+
+

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

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

ÀÌ ¹®¼­´Â Microsoft Windows¿¡¼­ ¾ÆÆÄÄ¡ 2.0À» ¼³Ä¡, ¼³Á¤, + ½ÇÇàÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù. À߸øµÈ ºÎºÐÀÌ Àְųª ´Ù¸¥ ¹æ¹ýÀ¸·Î + µµ¿òÀ» ÁÖ·Á¸é, ¹ö±× º¸°í + ÆäÀÌÁö¸¦ »ç¿ëÇÏ±æ ¹Ù¶õ´Ù.

+ +

ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ ¹ÙÀ̳ʸ® ¹èÆ÷º»À» ¼³Ä¡ÇÑ´Ù°í °¡Á¤ÇÑ´Ù. + (¾Æ¸¶µµ °³¹ß ȤÀº ¹ö±×¸¦ ã±âÀ§ÇØ) Á÷Á¢ ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÏ·Á¸é + Microsoft Windows¿ë ¾ÆÆÄÄ¡ + ÄÄÆÄÀÏÀ» Âü°íÇ϶ó.

+ +

ÇöÀç Microsoft Windows ¿î¿µÃ¼Á¦±ºÀÇ ¹öÀü Á¤Ã¥»ó + ÀÌ ¹®¼­´Â ´ÙÀ½°ú °°ÀÌ ±¸ºÐÇÑ´Ù:

+
    +
  • Windows NT: Windows NT Ä¿³ÎÀ» ±â¹ÝÀ¸·Î + ÇÏ´Â ¸ðµç Windows ¹öÀüÀ» ÀǹÌÇÑ´Ù. Windows NT, Windows + 2000, Windows XP, Windows .Net Server 2003À» ÁöĪÇÑ´Ù.
    • +
  • Windows 9x: ¼ÒºñÀÚ Áß½ÉÀÇ ¿À·¡µÈ + Windows ¹öÀüÀ» ¶æÇÑ´Ù. Windows 95 (OSR2 Æ÷ÇÔ), Windows + 98, Windows ME¸¦ ÁöĪÇÑ´Ù.
    • +
+ +
+ +
top
+
+

¿î¿µÃ¼Á¦ ¿ä±¸Á¶°Ç

+ + +

¾ÆÆÄÄ¡ 2.0À» ½ÇÇàÇϱâÀ§ÇÑ ±âº» Windows Ç÷¡ÆûÀº Windows + NTÀÌ´Ù. ¹ÙÀ̳ʸ® ¼³Ä¡ÇÁ·Î±×·¥Àº Intel°ú AMD¿Í °°Àº x86 °³¿­ + ÇÁ·Î¼¼¼­¿¡¼­¸¸ µ¿ÀÛÇÑ´Ù. ¾ÆÆÄÄ¡´Â Windows 9x¿¡¼­ ÃæºÐÈ÷ + °Ë»çÇÏÁö ¾Ê¾Ò±â¶§¹®¿¡ Àý´ë·Î ½ÇÁ¦ ¼­ºñ½º¿¡ »ç¿ëÇÏÁö ¾Ê±æ + ¹Ù¶õ´Ù. +

+ +

¿î¿µÃ¼Á¦¿¡ ¼³Ä¡ÇÑ TCP/IP ³×Æ®¿öÅ©°¡ µ¿ÀÛÇØ¾ß ÇÑ´Ù. Windows + 95¿¡¼­ ½ÇÇàÇÑ´Ù¸é, Winsock 2 ¾÷±×·¹À̵带 ¼³Ä¡ÇØ¾ß ÇÑ´Ù. + Windows 95¿ë Winsock 2´Â ¿©±â¿¡¼­ + ´Ù¿î¹ÞÀ» ¼ö ÀÖ´Ù. +

+ +

Windows NT 4.0À» »ç¿ëÇÑ´Ù¸é ¼­ºñ½ºÆÑ 4ÀÇ TCP/IP ¹®Á¦¿Í + Winsock ¹®Á¦°¡ ´ÙÀ½ ¼­ºñ½ºÆÑ¿¡¼­ ÇØ°áµÇ¾ú±â¶§¹®¿¡, ¼­ºñ½ºÆÑ + 6À» ¼³Ä¡Çϱæ Àû±Ø ±ÇÇÑ´Ù.

+
top
+
+

Windows¿ë ¾ÆÆÄÄ¡ ´Ù¿î·Îµå

+ + +

¾ÆÆÄÄ¡ À¥¼­¹ö http://httpd.apache.org/download.cgi¿¡¼­ + ¾ÆÆÄÄ¡ ÃֽŠ¹öÀü¿¡ ´ëÇÑ Á¤º¸¸¦ ¾òÀ» ¼ö ÀÖ´Ù. ¿©±â¿¡´Â ÃֽŠ+ ¹ßÇ¥ÆÇ°ú ¾ËÆÄ È¤Àº º£Å¸ Å×½ºÆ®¹öÀü°ú, ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ´Ù¿î·ÎµåÇÒ + ¼ö ÀÖ´Â HTTP ¹Ì·¯¿Í FTP ¹Ì·¯ ¸ñ·ÏÀÌ ÀÖ´Ù. ºü¸£°í ¾ÈÁ¤ÇÏ°Ô + ´Ù¿î¹ÞÀ¸·Á¸é °¡±î¿î ¹Ì·¯¸¦ »ç¿ëÇÏ±æ ¹Ù¶õ´Ù.

+ +

Windows¿¡ ¼³Ä¡ÇÏ·Á¸é È®ÀåÀÚ°¡ .msiÀÎ Windows¿ë + ¾ÆÆÄÄ¡ ¹öÀüÀ» ´Ù¿î¹Þ¾Æ¾ß ÇÑ´Ù. ÀÌ ÆÄÀÏÀº ¸·¹Ù·Î ½ÇÇàÇÒ ¼ö + ÀÖ´Â ¾ÆÆÄÄ¡¸¦ ÀúÀåÇÑ Microsoft ¼³Ä¡ÆÄÀÏÀÌ´Ù. µû·Î ¼Ò½ºÄڵ常 + ¹­¾îµÐ .zip ÆÄÀÏÀÌ ÀÖ´Ù. Microsoft Visual C++ + (Visual Studio)À» »ç¿ëÇÏ¿© Á÷Á¢ ¾ÆÆÄÄ¡¸¦ ÄÄÆÄÀÏÇÒ ¼öµµ ÀÖ´Ù.

+
top
+
+

Windows¿ë ¾ÆÆÄÄ¡ ¼³Ä¡Çϱâ

+ + +

¼³Ä¡ÇÏ·Á¸é Microsoft Installer 1.2 ÀÌ»ó ¹öÀüÀÌ ÇÊ¿äÇÏ´Ù. + Windows 9x¸¦ »ç¿ëÇÑ´Ù¸é ¿©±â¿¡¼­ + Microsoft Installer¸¦ 2.0 ¹öÀüÀ¸·Î ¾÷±×·¹À̵åÇÒ ¼ö ÀÖ°í, + Windows NT 4.0°ú 2000À» »ç¿ëÇÑ´Ù¸é ¿©±â¿¡¼­ + 2.0 ¹öÀü ¾÷µ¥ÀÌÆ®¸¦ ±¸ÇÒ ¼ö ÀÖ´Ù. Windows XP´Â ¾÷µ¥ÀÌÆ®ÇÒ + ÇÊ¿ä°¡ ¾ø´Ù.

+ +

¹ÙÀ̳ʸ® ¼³Ä¡ÆÄÀϷδ °°Àº ÄÄÇ»ÅÍ¿¡ ¼­·Î ´Ù¸¥ ¾ÆÆÄÄ¡ + 2.0 ¹öÀüÀ» ¼³Ä¡ÇÒ ¼ö ¾øÀ½À» ÁÖÀÇÇ϶ó. ±×·¯³ª 1.3 + ¹öÀü°ú 2.0 ¹öÀüÀº °°Àº ÄÄÇ»ÅÍ¿¡ ¾Æ¹« ¹®Á¦¾øÀÌ + ¼³Ä¡ÇÒ ¼ö ÀÖ´Ù. °°Àº ÄÄÇ»ÅÍ¿¡ µÎ°¡Áö ´Ù¸¥ 2.0 ¹öÀüÀ» ¼³Ä¡ÇÏ·Á¸é + ¼Ò½º¸¦ ÄÄÆÄÀÏÇÏ¿© ¾ÆÆÄÄ¡¸¦ + ¼³Ä¡ÇØ¾ß ÇÑ´Ù.

+ +

À§¿¡¼­ ´Ù¿î¹ÞÀº ¾ÆÆÄÄ¡ .msi ÆÄÀÏÀ» ½ÇÇàÇÑ´Ù. + ¼³Ä¡ÇÒ¶§ ´ÙÀ½°ú °°Àº °ÍÀ» ¹°¾îº»´Ù:

+ +
    +

  1. ³×Æ®¿öÅ© µµ¸ÞÀÎ (Network Domain). + µî·ÏµÈ ¼­¹öÀÇ DNS µµ¸ÞÀÎÀ» ÀÔ·ÂÇÑ´Ù. ¿¹¸¦ µé¾î, ¼­¹öÀÇ + Àüü DNS À̸§ÀÌ server.mydomain.netÀ̶ó¸é + ¿©±â¿¡ mydomain.netÀ» ÀÔ·ÂÇÑ´Ù.

    2. + +

  2. ¼­¹ö¸í (Server Name). ¼­¹öÀÇ Àüü + DNS À̸§. À§ÀÇ °æ¿ì ¿©±â¿¡ server.mydomain.netÀ» + ÀÔ·ÂÇÑ´Ù.

    3. + +

  3. °ü¸®ÀÚ ÀüÀÚ¿ìÆí ÁÖ¼Ò (Administrator's Email + Address). ¿©±â¿¡ ¼­¹ö °ü¸®ÀÚ³ª À¥¸¶½ºÅÍÀÇ ÀüÀÚ¿ìÆí + ÁÖ¼Ò¸¦ ÀÔ·ÂÇÑ´Ù. ±âº»ÀûÀ¸·Î Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³»´Â ¿À·ù¹®¿¡ + ÀÌ ÁÖ¼Ò¸¦ ±â·ÏÇÑ´Ù.

    4. + +

  4. »ç¿ëÀÚ ´ë»ó (For whom to install + Apache) »õ·Î ¼³Ä¡ÇÏ´Â ¾ÆÆÄÄ¡°¡ 80¹ø Æ÷Æ®¿¡¼­ + ¿äûÀ» ±â´Ù¸®°Ô ÇÏ·Á¸é for All Users, on Port 80, + as a Service - Recommended (¸ðµç »ç¿ëÀÚ, 80¹ø Æ÷Æ®, + service·Î - Ãßõ)¸¦ ¼±ÅÃÇÑ´Ù. ¾ÆÆÄÄ¡¸¦ service·Î ½ÇÇàÇÑ´Ù + (Áï, ¾ÆÆÄÄ¡´Â ¼­¹ö¿¡ ·Î±×ÀÎÇÑ »ç¶÷ÀÌ ¾ø¾îµµ ½ÇÇàµÈ´Ù). + °³ÀÎÀûÀ¸·Î Å×½ºÆ®Çغ¸°Å³ª ÀÌ¹Ì 80¹ø Æ÷Æ®¸¦ »ç¿ëÇÏ´Â ´Ù¸¥ + À¥¼­¹ö°¡ ÀÖ´Ù¸é only for the Current User, on Port + 8080, when started Manually (ÇöÀç »ç¿ëÀÚ¸¸, 8080¹ø + Æ÷Æ®, Á÷Á¢ ½ÃÀÛ)¸¦ ¼±ÅÃÇÑ´Ù.

    5. + +

  5. ¼³Ä¡ Á¾·ù (The installation type). + ¸ðµâ °³¹ß¿¡ ÇÊ¿äÇÑ ¼Ò½ºÄÚµå¿Í ¶óÀ̺귯¸®¸¦ Á¦¿ÜÇÑ ¸ðµç + °ÍÀ» ¼³Ä¡ÇÏ·Á¸é TypicalÀ» ¼±ÅÃÇÑ´Ù. + CustomÀ» ¼±ÅÃÇÏ¸é ¼³Ä¡ÇÒ ³»¿ëÀ» ÁöÁ¤ÇÒ ¼ö + ÀÖ´Ù. Àüü ¼³Ä¡½Ã µð½ºÅ©¿¡ ºó °ø°£ÀÌ ¾à 13 ¸Þ°¡¹ÙÀÌÆ® + Á¤µµ ÇÊ¿äÇÏ´Ù. ÀÌ ¼öÄ¡´Â À¥»çÀÌÆ® Å©±â¸¦ Á¦¿ÜÇÑ + °ÍÀÌ´Ù.

    6. + +

  6. ¼³Ä¡ Àå¼Ò (Where to install). + ±âº» °æ·Î´Â C:\Program Files\Apache GroupÀÌ°í, + ÀÌ°÷¿¡ Apache2¶ó´Â µð·ºÅ丮¸¦ ¸¸µç´Ù.

    7. +
+ +

¼³Ä¡ÇÒ µ¿¾È ¾ÆÆÄÄ¡´Â conf ÇÏÀ§µð·ºÅ丮¿¡ + ÀÖ´Â ÆÄÀϵéÀ» ¼±ÅÃÇÑ ¼³Ä¡ µð·ºÅ丮¿¡ ¸Â°Ô ±¸¼ºÇÑ´Ù. ±×·¯³ª + ÀÌ µð·ºÅ丮¿¡ ¼³Á¤ÆÄÀÏÀÌ ÀÌ¹Ì ÀÖ´Ù¸é ±×´ë·Î µÐ´Ù. ´ë½Å, + ÇØ´ç ÆÄÀÏÀÇ »õ·Î¿î º¹»çº»¿¡ È®ÀåÀÚ .default¸¦ + ºÙÀδÙ. ¿¹¸¦ µé¾î, conf\httpd.conf°¡ ÀÌ¹Ì ÀÖ´Ù¸é + conf\httpd.conf.default·Î À̸§À» º¯°æÇÑ´Ù. + ¼³Ä¡ÈÄ .default ÆÄÀÏÀÇ ¼³Á¤À» Á÷Á¢ »ìÆ캸°í, + ÇÊ¿äÇÏ´Ù¸é ±âÁ¸ ¼³Á¤ÆÄÀÏÀ» ¼öÁ¤ÇØ¾ß ÇÑ´Ù.

+ +

¶Ç, ÀÌ¹Ì htdocs\index.htmlÀ̶ó´Â ÆÄÀÏÀÌ + ÀÖ´Ù¸é ±×´ë·Î µÐ´Ù (index.html.default¶ó°í + º¹»çÇÏÁöµµ ¾Ê´Â´Ù). Áï, ±âÁ¸¿¡ ¾ÆÆÄÄ¡°¡ ¼³Ä¡µÇÀÖ´õ¶óµµ ¾ÈÀüÇÏ°Ô + ¾ÆÆÄÄ¡¸¦ »õ·Î ¼³Ä¡ÇÒ ¼ö ÀÖ´Ù. ¹°·Ð ¼³Ä¡Çϱâ Àü¿¡ ¼­¹ö¸¦ + Áß´ÜÇÏ°í, ¼³Ä¡ÈÄ »õ·Î¿î ¼­¹ö¸¦ ½ÃÀÛÇØ¾ß ÇÑ´Ù.

+ +

¾ÆÆÄÄ¡ ¼³Ä¡ÈÄ ÇÊ¿äÇÏ´Ù¸é conf ÇÏÀ§µð·ºÅ丮¿¡ + ÀÖ´Â ¼³Á¤ÆÄÀÏÀ» ¼öÁ¤ÇØ¾ß ÇÑ´Ù. ÆÄÀÏÀº ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÑ µð·ºÅ丮ÀÇ + htdocs ÇÏÀ§µð·ºÅ丮¿¡ ÀÖ´Â ¹®¼­¸¦ ¼­ºñ½ºÇϵµ·Ï + ¼³Á¤µÇÀÖ´Ù. ½ÇÁ¦·Î ¾ÆÆÄÄ¡¸¦ »ç¿ëÇϱâ Àü¿¡ ¼³Á¤ÇØ¾ß ÇÒ ¿É¼ÇÀÌ + ¸¹´Ù. ±×·¯³ª »¡¸® ½ÇÇàÇغ¼ ¼ö ÀÖµµ·Ï ±âº» ¼³Á¤ÆÄÀϷεµ µ¿ÀÛÇÑ´Ù.

+
top
+
+

Windows¿ë ¾ÆÆÄÄ¡ ¼³Á¤Çϱâ

+ + +

¾ÆÆÄÄ¡´Â conf ÇÏÀ§µð·ºÅ丮¿¡ ÀÖ´Â ÆÄÀÏ·Î + ¼³Á¤ÇÑ´Ù. ÀÌ ÆÄÀÏÀº À¯´Ð½º¿ë°ú °°Áö¸¸, Windows¿ë ¾ÆÆÄÄ¡ + ƯÀ¯ÀÇ Áö½Ã¾î°¡ ¸î°³ ÀÖ´Ù. »ç¿ë°¡´ÉÇÑ ¸ðµç Áö½Ã¾î¸¦ º¸·Á¸é + Áö½Ã¾î ¸ñ·ÏÀ» Âü°íÇ϶ó.

+ +

Windows¿ë ¾ÆÆÄÄ¡ÀÇ ÁÖµÈ Â÷ÀÌÁ¡Àº:

+
    +

  • Windows¿ë ¾ÆÆÄÄ¡´Â ´ÙÁß¾²·¹µå ¹æ½ÄÀ» »ç¿ëÇϱ⶧¹®¿¡, + À¯´Ð½º¿Í ´Þ¸® ¿äû¸¶´Ù ´Ù¸¥ ÇÁ·Î¼¼½º¸¦ »ç¿ëÇÏÁö ¾Ê´Â´Ù. + ´ë½Å ¾ÆÆÄÄ¡ ÇÁ·Î¼¼½º´Â Ç×»ó, ºÎ¸ð ÇÁ·Î¼¼½º¿Í ¿äûÀ» ó¸®ÇÏ´Â + ÀÚ½Ä ÇÁ·Î¼¼½º, 2°³ÀÌ´Ù. ÀÚ½Ä ÇÁ·Î¼¼½º¿¡ ÀÖ´Â ¿©·¯ ¾²·¹µåµéÀÌ + ¿äûµéÀ» ó¸®ÇÑ´Ù. +

    + +

    ÇÁ·Î¼¼½º °ü¸® Áö½Ã¾îµµ ´Ù¸£´Ù:

    + +

    MaxRequestsPerChild: À¯´Ð½º¿Í + °°ÀÌ, ÀÚ½Ä ÇÁ·Î¼¼½º°¡ ¿äûÀ» ¾ó¸¶¸¸Å­ ó¸®ÇÏ°í Á×À»Áö¸¦ + Á¶Á¤ÇÑ´Ù. ±×·¯³ª À¯´Ð½º¿Í ´Þ¸® ÇÁ·Î¼¼½º°¡ Çѹø¿¡ ÇÑ ¿äû¸¸À» + ó¸®ÇÏÁö¾Ê°í Çѹø¿¡ ¸ðµç ¿äûÀ» ¼­ºñ½ºÇϱ⶧¹®¿¡, ¼³Á¤ÇÑ´Ù¸é + ¸Å¿ì Å« °ªÀ» ¼³Á¤ÇÏ±æ ±ÇÇÑ´Ù. ±ÇÀåÇÏ´Â ±âº»°ª + MaxRequestsPerChild 0À» »ç¿ëÇϸé ÀÚ½Ä ÇÁ·Î¼¼½º´Â + Á×Áö¾Ê°í ¿µ¿øÈ÷ ¿äûÀ» ¼­ºñ½ºÇÑ´Ù.

    + +
    °æ°í: ÀÚ½Ä ÇÁ·Î¼¼½º´Â »õ·Î + ½ÃÀÛÇÒ ¶§¸¶´Ù ¼­¹ö¼³Á¤ÆÄÀÏÀ» »õ·Î Àд´Ù. + httpd.conf¸¦ ¼öÁ¤Çß´Ù¸é, ÀÚ½Ä ÇÁ·Î¼¼½º°¡ + ½ÃÀÛÇÏÁö ¾Ê°Å³ª ¿¹±âÄ¡¾ÊÀº °á°ú°¡ ¹ß»ýÇÒ ¼ö ÀÖ´Ù.
    + +

    ThreadsPerChild: + ÀÌ Áö½Ã¾î´Â »õ·Î Ãß°¡µÇ¾ú´Ù. ÀÌ Áö½Ã¾î´Â ¼­¹ö°¡ »ç¿ëÇÒ + ¾²·¹µå °³¼ö¸¦ ÁöÁ¤ÇÑ´Ù. ÀÌ °ªÀÌ ¼­¹ö°¡ Çѹø¿¡ ó¸®ÇÒ ¼ö + ÀÖ´Â ÃÖ´ë ¿¬°á°³¼öÀ̱⶧¹®¿¡, »çÀÌÆ®¿¡ Á¢¼Ó·®ÀÌ ¸¹´Ù¸é + ÃæºÐÈ÷ Å« °ªÀ» ¼³Á¤ÇØ¾ß ÇÑ´Ù. ±ÇÀåÇÏ´Â ±âº»°ªÀº + ThreadsPerChild 50ÀÌ´Ù.

    • + +

  • ÆÄÀϸíÀ» ¾Æ±Ô¸ÕÆ®·Î ¹Þ´Â Áö½Ã¾î´Â À¯´Ð½º ÆÄÀϸíÀÌ + ¾Æ´Ñ Windows ÆÄÀϸíÀ» »ç¿ëÇØ¾ß ÇÑ´Ù. ±×·¯³ª ¾ÆÆÄÄ¡ ³»ºÎ¿¡¼­ + À¯´Ð½º½Ä À̸§À» »ç¿ëÇϱ⶧¹®¿¡ ¹é½½·¡½¬°¡ ¾Æ´Ñ ½½·¡½¬¸¦ + »ç¿ëÇØ¾ß ÇÑ´Ù. µå¶óÀÌºê ¹®ÀÚ¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù. µå¶óÀ̺긦 + ÁöÁ¤ÇÏÁö ¾ÊÀ¸¸é ¾ÆÆÄÄ¡ ½ÇÇàÆÄÀÏÀÌ ÀÖ´Â µå¶óÀ̺긦 + »ç¿ëÇÑ´Ù.

    • + +

  • Windows¿ë ¾ÆÆÄÄ¡´Â ¼­¹ö¸¦ ´Ù½Ã ÄÄÆÄÀÏÇÏÁö ¾Ê°í + ½ÇÇàÁß¿¡ ¸ðµâÀ» ÀоîµéÀÏ ¼ö ÀÖ´Ù. ±âº»°ªÀ¸·Î ¾ÆÆÄÄ¡¸¦ + ÄÄÆÄÀÏÇϸé \Apache2\modules µð·ºÅ丮¿¡ ¿©·¯ + ¼±Åð¡´ÉÇÑ ¸ðµâÀ» ¼³Ä¡ÇÑ´Ù. ÀÌ ¸ðµâ ȤÀº ´Ù¸¥ ¸ðµâÀ» + »ç¿ëÇÏ·Á¸é »õ·Î »ý±ä LoadModule Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. + ¿¹¸¦ µé¾î, status ¸ðµâÀ» »ç¿ëÇÑ´Ù¸é + (access.conf¿¡ status°ü·Ã Áö½Ã¾î¿Í ÇÔ²²) + ¾Æ·¡¿Í °°ÀÌ ¼³Á¤ÇÑ´Ù:

    + +

    + LoadModule status_module modules/mod_status.so +

    + +

    ÀоîµéÀÏ ¼ö ÀÖ´Â + ¸ðµâ ¸¸µé±â¿¡ ´ëÇÑ Á¤º¸µµ ÀÖ´Ù.

    • + +

  • ¾ÆÆÄÄ¡´Â Microsoft IIS¿Í ´Ù¸¥ Windows ¼­¹ö°¡ »ç¿ëÇÏ´Â + ISAPI (Internet Server Application Programming Interface) + È®ÀåÀ» (Áï, ÀÎÅÍ³Ý ¼­¹ö ÇÁ·Î±×·¥) ÀоîµéÀÏ ¼öµµ ÀÖ´Ù. + ´õ ÀÚ¼¼ÇÑ Á¤º¸°¡ ÀÖ´Ù. + ¾ÆÆÄÄ¡´Â ISAPI ÇÊÅ͸¦ ÀоîµéÀÏ ¼ö ¾øÀ½À» + ÁÖÀÇÇ϶ó.

    • + +

  • CGI ½ºÅ©¸³Æ®¸¦ »ç¿ëÇÑ´Ù¸é ScriptInterpreterSource Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡°¡ ½ºÅ©¸³Æ®ÀÇ ÀÎÅÍÇÁ¸®Å͸¦ ã´Â ¹æ¹ýÀ» + ¼³Á¤ÇÒ ¼ö ÀÖ´Ù.

    • + +

  • Windows¿¡¼­ .htaccess¿Í °°Àº ÆÄÀϸíÀ» + ´Ù·ç±â Èûµå¹Ç·Î, AccessFilename Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + µð·ºÅ丮º° ¼³Á¤ÆÄÀÏ À̸§À» º¯°æÇϸé ÆíÇÏ´Ù.

    • + +

  • Windows NT¶ó¸é ¾ÆÆÄÄ¡ ½ÃÀ۽à ¹ß»ýÇÑ ¿À·ù¸¦ Windows + À̺¥Æ® ·Î±×¿¡ ±â·ÏÇÑ´Ù. ±×·¡¼­ ¾ÆÆÄÄ¡°¡ º¸Åë »ç¿ëÇÏ´Â + error.log ÆÄÀÏÀ» »ç¿ëÇÒ ¼ö ¾ø´Â °æ¿ì¿¡ ´ëºñÇÑ´Ù. + Windows À̺¥Æ® ·Î±×´Â Windows NT 4.0¿¡¼­´Â À̺¥Æ® ºä¾î + ÇÁ·Î±×·¥À¸·Î, ÃֽŠWindows ¹öÀü¿¡¼­´Â À̺¥Æ® ºä¾î MMC + ½º³ÀÀο¡¼­ º¼ ¼ö ÀÖ´Ù.

    + +
    Windows 9x¿¡´Â Windows À̺¥Æ® ·Î±×°¡ ¾ø±â¶§¹®¿¡ + ½ÃÀ۽à ¹ß»ýÇÑ ¿À·ù¸¦ ±â·ÏÇÏÁö ¾Ê´Â´Ù.
    • +
+ +
top
+
+

¾ÆÆÄÄ¡¸¦ Service·Î ½ÇÇàÇϱâ

+ + +

Windows NT¿¡¼­´Â ¾ÆÆÄÄ¡¸¦ service·Î ½ÇÇàÇÒ ¼ö ÀÖ´Ù. Windows + 9x¿¡´Â ¸Å¿ì ½ÇÇèÀûÀÎ ¹æ¹ýÀ¸·Î ºñ½ÁÇÑ ±â´ÉÀ» Áö¿øÇÑ´Ù.

+ +

¼³Ä¡½Ã ÀÚµ¿À¸·Î ¾ÆÆÄÄ¡¸¦ service·Î ¼³Ä¡ÇÒ ¼ö ÀÖ´Ù. "¸ðµç + »ç¿ëÀÚ"¸¦ ¼±ÅÃÇϸé, ¾ÆÆÄÄ¡ service°¡ ¸¸µé¾îÁø´Ù. "ÇöÀç + »ç¿ëÀÚ¸¸"À» ¼±ÅÃÇÏ´õ¶óµµ ¼³Ä¡ÈÄ Á÷Á¢ ¾ÆÆÄÄ¡¸¦ service·Î + µî·ÏÇÒ ¼ö ÀÖ´Ù. service¸¦ ¼³Ä¡ÇÏ·Á¸é Administrators ±×·ìÀÇ + ±¸¼º¿øÀ̾î¾ß ÇÑ´Ù.

+ +

¾ÆÆÄÄ¡¿¡´Â Apache Service Monitor¶ó´Â µµ±¸°¡ ÀÖ´Ù. ÀÌ + µµ±¸¸¦ »ç¿ëÇÏ¸é ³×Æ®¿÷¿¡ ÀÖ´Â ´Ù¸¥ ÄÄÇ»ÅÍ¿¡ ¼³Ä¡µÈ ¾ÆÆÄÄ¡ + »óŵµ È®ÀÎÇÏ°í °ü¸®ÇÒ ¼ö ÀÖ´Ù. monitor·Î ¾ÆÆÄÄ¡ service¸¦ + °ü¸®ÇÏ·Á¸é ¸ÕÀú service¸¦ (¼³Ä¡½Ã ÀÚµ¿À¸·Î ȤÀº Á÷Á¢) ¼³Ä¡ÇØ¾ß + ÇÑ´Ù. +

+ +

¾ÆÆÄÄ¡ bin ÇÏÀ§µð·ºÅ丮¿¡¼­ ¸í·ÉÇà ÇÁ·ÒÇÁÆ®¿¡ + ´ÙÀ½°ú °°ÀÌ ÀÔ·ÂÇÏ¸é ¾ÆÆÄÄ¡¸¦ Windows NT service·Î ¼³Ä¡ÇÑ´Ù:

+ +

+ apache -k install +

+ +

¼³Ä¡ÇÒ service À̸§À» ÁöÁ¤ÇÏ°í ½Í´Ù¸é ´ÙÀ½ ¸í·É¾î¸¦ »ç¿ëÇÑ´Ù. + ÄÄÇ»ÅÍ¿¡ ¾ÆÆÄÄ¡°¡ ¿©·¯°³ ¼³Ä¡µÇÀÖ´Ù¸é À̸§À» ´Ù¸£°Ô ÁÖ¾î¾ß + ÇÑ´Ù.

+ +

+ apache -k install -n "MyServiceName" +

+ +

service°¡ »ç¿ëÇÒ ¼³Á¤ÆÄÀÏÀ» Á÷Á¢ ÁöÁ¤ÇÏ·Á¸é ´ÙÀ½°ú °°ÀÌ + ÇÑ´Ù:

+ +

+ apache -k install -n "MyServiceName" -f "c:\files\my.conf" +

+ +

-k install ¿Ü¿¡ ´Ù¸¥ ÆĶó¹ÌÅ͸¦ »ç¿ëÇÏÁö + ¾ÊÀ¸¸é, service À̸§Àº Apache2°¡ µÇ°í ¼³Á¤ÆÄÀÏÀº + conf\httpd.conf°¡ µÈ´Ù. +

+ +

¾ÆÆÄÄ¡ service¸¦ Á¦°ÅÇϱ⠽±´Ù. °£´ÜÈ÷:

+ +

+ apache -k uninstall +

+ +

´ÙÀ½°ú °°ÀÌ Á¦°ÅÇÒ ¾ÆÆÄÄ¡ service¸¦ ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù:

+ +

+ apache -k uninstall -n "MyServiceName" +

+ +

º¸Åë ¾ÆÆÄÄ¡ service ½ÃÀÛ, Àç½ÃÀÛ, Á¾·á´Â Apache Service + Monitor³ª NET START Apache2, NET STOP + Apache2 °°Àº ¸í·É¾î ȤÀº Windows ¼­ºñ½º °ü¸®Ã¢¿¡¼­ + ÇÑ´Ù. ¾î¶² ¹æ¹ýÀ» »ç¿ëÇϵçÁö ¾ÆÆÄÄ¡ service¸¦ ½ÃÀÛÇϱâ Àü¿¡ + ¼³Á¤ÆÄÀÏÀ» °Ë»çÇغÁ¾ß ÇÑ´Ù:

+ +

+ apache -n "MyServiceName" -t +

+ +

¸í·ÉÇà ¿É¼ÇÀ¸·Îµµ ¾ÆÆÄÄ¡ service¸¦ Á¶Á¤ÇÒ ¼ö ÀÖ´Ù. ¼³Ä¡ÇÑ + ¾ÆÆÄÄ¡ serivce¸¦ ½ÃÀÛÇÏ·Á¸é:

+ +

+ apache -k start +

+ +

¸í·ÉÇà ¿É¼ÇÀ¸·Î ¾ÆÆÄÄ¡ service¸¦ Á¾·áÇÏ·Á¸é:

+ +

+ apache -k stop +

+ +

ȤÀº

+ +

+ apache -k shutdown +

+ +

½ÇÇàÁßÀÎ service¸¦ Àç½ÃÀÛÇÏ¿© ¼³Á¤ÆÄÀÏÀ» ´Ù½Ã Àеµ·Ï + ÇÒ ¼ö ÀÖ´Ù:

+ +

+ apache -k restart +

+ +

±âº»ÀûÀ¸·Î ¸ðµç ¾ÆÆÄÄ¡ service´Â ½Ã½ºÅÛ »ç¿ëÀÚ + (LocalSystem °èÁ¤) ±ÇÇÑÀ¸·Î ½ÇÇàÇϵµ·Ï µî·ÏµÈ´Ù. + Windows º¸¾È±¸Á¶»ó LocalSystem °èÁ¤Àº ÆÄÀϽýºÅÛ, + named pipes, DCOM, secure RPC µî ¾î¶² ¹æ¹ýÀ» »ç¿ëÇϵçÁö + ³×Æ®¿÷¿¡ Á¢±ÙÇÒ ¼ö ¾ø´Ù. ±×·¯³ª ÇØ´ç ÄÄÇ»ÅÍ¿¡¼­´Â ¸¹Àº ±ÇÇÑÀ» + °¡Áø´Ù. +

+ +
LocalSystem °èÁ¤¿¡°Ô + ³×Æ®¿÷ ±ÇÇÑÀ» Àý´ë·Î ÁÖÁö ¸¶¶ó! ¾ÆÆÄÄ¡°¡ ³×Æ®¿÷ ÀÚ¿ø¿¡ Á¢±ÙÇØ¾ß + ÇÑ´Ù¸é, ¾Æ·¡¿¡¼­ ¼³¸íÇÏ´Â ¹æ¹ýÀ¸·Î ¾ÆÆÄÄ¡¸¦ À§ÇÑ º°µµÀÇ + °èÁ¤À» ¸¸µé¾î¶ó.
+ +

¾ÆÆÄÄ¡ service¸¦ ½ÇÇàÇϱâÀ§ÇÑ º°µµÀÇ °èÁ¤À» ¸¸µé ¼öµµ + ÀÖ´Ù. ƯÈ÷ ¾ÆÆÄÄ¡°¡ ³×Æ®¿÷ ÀÚ¿ø¿¡ Á¢±ÙÇØ¾ß ÇÑ´Ù¸é ÀÌ ¹æ¹ýÀ» + °­·ÂÈ÷ ±ÇÇÑ´Ù.

+ +
    +
  1. ÀÏ¹Ý µµ¸ÞÀÎ »ç¿ëÀÚ °èÁ¤À» ¸¸µé°í ¾ÏÈ£¸¦ ±â¾ïÇ϶ó.
    2. + +
  2. »õ·Î ¸¸µç °èÁ¤¿¡ ¼­ºñ½º·Î ·Î±×¿Â¿Í + ¿î¿µ üÁ¦ÀÇ ÀϺηΠȰµ¿ ±ÇÇÑÀ» + ºÎ¿©ÇÑ´Ù. Windows NT 4.0¿¡¼­´Â User Manager for Domains¿¡¼­ + ±ÇÇÑÀ» ºÎ¿©ÇÒ ¼ö ÀÖ°í, Windows 2000°ú XP¿¡¼­´Â ¾Æ¸¶µµ + "±×·ì Á¤Ã¥"À» »ç¿ëÇØ¾ß ÇÑ´Ù. "·ÎÄà º¸¾È ¼³Á¤" MMC + ½º³ÀÀο¡¼­ Á÷Á¢ ¼³Á¤ÇØÁÙ ¼öµµ ÀÖ´Ù. +
    3. + +
  3. »õ·Î ¸¸µç °èÁ¤ÀÌ Users ±×·ì¿¡ ¼ÓÇÏ´ÂÁö È®ÀÎÇÑ´Ù.
    4. + +
  4. ¸ðµç ¹®¼­¿Í ½ºÅ©¸³Æ® Æú´õ¿¡ (¿¹¸¦ µé¾î + htdocs¿Í cgi-bin) ´ëÇØ ÀÐ±â ¹× + ½ÇÇà (RX) ±ÇÇÑÀ» ºÎ¿©ÇÑ´Ù.
    5. + +
  5. ¾ÆÆÄÄ¡ logs µð·ºÅ丮¿¡ ¼öÁ¤ (RWXD) ±ÇÇÑÀ» + ºÎ¿©ÇÑ´Ù.
    6. + +
  6. Apache.exe ½ÇÇàÆÄÀÏ¿¡ ÀÐ±â ¹× ½ÇÇà (RX) + ±ÇÇÑÀ» ºÎ¿©ÇÑ´Ù.
    7. +
+ +
¾ÆÆÄÄ¡ service¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚ¿¡°Ô ÃÖ¼ÒÇÑ ¼öÁ¤ (RWXD) + ±ÇÇÑÀÌ ÇÊ¿äÇÑ logs ÇÏÀ§µð·ºÅ丮¸¦ Á¦¿ÜÇÏ°í + Apache2 µð·ºÅ丮 Àüü¿¡ ÀÐ±â ¹× ½ÇÇà (RX) ±ÇÇÑÀ» ºÎ¿©ÇÏ´Â + °ÍÀÌ ÁÁ´Ù.
+ +

°èÁ¤¿¡ "·ÎÄà ·Î±×¿Â"°ú "¼­ºñ½º·Î ·Î±×¿Â" ±ÇÇÑÀÌ ÀÖ´Ù¸é, + ±× °èÁ¤À¸·Î ·Î±×¿ÂÇÏ¿© °èÁ¤ÀÌ ½ºÅ©¸³Æ®¸¦ ½ÇÇàÇÏ°í À¥ÆäÀÌÁö¸¦ + ÀÐÀ¸¸ç ÄܼÖâ¿¡¼­ ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇÒ ¼ö ÀÖ´ÂÁö °Ë»çÇغ¼ ¼ö + ÀÖ´Ù. ¿©±â¼­ ¹®Á¦°¡ ¾ø´Ù¸é ¾ÆÆÄÄ¡¸¦ service·Î ½ÇÇàÇصµ ¹®Á¦°¡ + ¾ø´Ù.

+ +
Error code 2186Àº ¾ÆÆÄÄ¡°¡ ÇÊ¿äÇÑ + ³×Æ®¿÷ ÀÚ¿ø¿¡ Á¢±ÙÇÒ ¼ö ¾ø´Ù´Â ¸»·Î serviceÀÇ "·Î±×¿Â" + ¼³Á¤À» È®ÀÎÇ϶ó. ¶Ç, ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏ´Â °èÁ¤ÀÇ ±ÇÇÑÀ» + »ìÆìºÁ¶ó.
+ +

¾ÆÆÄÄ¡¸¦ service·Î ½ÇÇàÇϸé Windows Service Control + Manager¿¡¼­ ¿À·ù¹®À» º¼ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, Á¦¾îÆÇ¿¡¼­ + "¼­ºñ½º"¸¦ »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇÏ´Â °æ¿ì ´ÙÀ½°ú °°Àº ¹®±¸°¡ + ³ª¿Ã ¼ö ÀÖ´Ù:

+ +

+ Could not start the Apache2 service on \\COMPUTER
+ Error 1067; The process terminated unexpectedly. +

+ +

¾ÆÆÄÄ¡ service¸¦ ½ÃÀÛÇÒ¶§ ¹®Á¦°¡ ÀÖÀ¸¸é ÀϹÝÀûÀÎ ÀÌ·± + ¿À·ù°¡ ³ª¿Â´Ù. ½ÇÁ¦ ¾îµð°¡ ¹®Á¦ÀÎÁö ¾Ë·Á¸é ¾ÆÆÄÄ¡¸¦ ÄÜ¼Ö + ÇÁ·Î±×·¥À¸·Î ½ÇÇàÇغ¸¶ó.

+ +

Windows 9x¿¡¼­ ¾ÆÆÄÄ¡´Â Windows NTÀÇ service¿Í ºñ½ÁÇÑ + ¹æ¹ýÀ» Áö¿øÇÑ´Ù. ±×·¯³ª ¸Å¿ì ½ÇÇèÀûÀÎ ±â´ÉÀÌ´Ù. + ½ÇÁ¦ ¼­ºñ½º¿¡ »ç¿ëÇÒ¸¸Å­ ¾ÈÁ¤ÀûÀÌÁö ¾Ê°í ¾ÕÀ¸·Î °³¼±µÉÁö + º¸ÀåÇÒ ¼öµµ ¾ø´Ù. À§ÇèÇϹǷΠȤ½Ã³ª »ç¿ëÇÑ´Ù¸é ÁÖÀÇÇؼ­ + »ç¿ëÇØ¾ß ÇÑ´Ù!

+ +

µÎ°¡Áö serviceÀÇ Áß¿äÇÑ Â÷ÀÌÁ¡Àº ´ÙÀ½°ú °°´Ù:

+ +
    +

  • ¾ÆÆÄÄ¡°¡ ¼º°øÀûÀ¸·Î ½ÃÀÛÇÏ¸é ¹è°æ¿¡¼­ ½ÇÇàÇÑ´Ù. + ¿¹¸¦ µé¾î, µ¥½ºÅ©Å¾¿¡ ¹Ù·Î°¡±â¸¦ ¸¸µé¾î¼­ ´ÙÀ½ ¸í·ÉÀ» + ½ÇÇàÇÏ´Â °æ¿ì,

    + +

    + apache -n "MyServiceName" -k start +

    + +

    service°¡ ¼º°øÀûÀ¸·Î ½ÃÀÛÇϸé ÄܼÖâÀÌ »ý°å´Ù°¡ ±Ý¹æ + »ç¶óÁø´Ù. httpd.conf ¼³Á¤ÆÄÀÏ¿¡ À߸øµÈ ³»¿ëÀÌ ÀÖ´Â µî + ¾ÆÆÄÄ¡ ½ÃÀ۽à ¿À·ù°¡ ¹ß»ýÇϸé ÄܼÖâÀ» °è¼Ó º¸ÀδÙ. ÄܼÖâÀº + ¹®Á¦ÀÇ ¿øÀÎÀ» ÆľÇÇϴµ¥ µµ¿òÀ» ÁÖ´Â ¿À·ù¹®À» º¸¿©ÁØ´Ù.

    • + +

  • Windows 9x´Â NET START¿Í NET + STOP ¸í·É¾î¸¦ Áö¿øÇÏÁö ¾Ê´Â´Ù. ¸í·ÉÇÁ·ÒÇÁÆ®¿¡¼­ + -k ¿É¼ÇÀ» »ç¿ëÇÏ¿© ¾ÆÆÄÄ¡ service¸¦ Á¶Á¤ÇØ¾ß + ÇÑ´Ù. +

    • + +

  • + ¾ÆÆÄÄ¡¿Í Windows 9x´Â ³×Æ®¿÷ ±ÇÇÑÀ» °¡Áø ƯÁ¤ »ç¿ëÀÚ·Î + ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏÁö ¸øÇÑ´Ù. »ç½Ç Windows 9x´Â º¸¾ÈÀ» Á¦°øÇÏÁöµµ + ¾Ê´Â´Ù. ÀÌ°ÍÀÌ ¹Ù·Î Apache Software FoundationÀÌ Windows + 9x ½Ã½ºÅÛÀ» °ø°³ À¥¼­¹ö·Î »ç¿ëÇÏ±æ ±ÇÇÏÁö ¾Ê´Â ÀÌÀ¯´Ù. + »ç¿ëÀÚ°¡ À¥ ÄÁÅÙÃ÷¸¦ °³¹ßÇÏ°í ¾ÆÆÄÄ¡ ¼­¹ö ÇнÀÀ» µ½±âÀ§ÇØ, + ¾Æ´Ï¸é ¾ÈÀüÇÑ »ç¼³ ³×Æ®¿÷¿¡ À§Ä¡ÇÒ ÀÎÆ®¶ó³Ý ¼­¹ö¸¦ À§ÇØ, + Windows 9x¸¦ Áö¿øÇÒ »ÓÀÌ´Ù.

    • + +
+ +

¾ÆÆÄÄ¡°¡ ÄÜ¼Ö ÇÁ·Î±×·¥À¸·Î µ¿ÀÛÇÔÀ» È®ÀÎÇÏ¿´´Ù¸é Windows + NT¿¡¼­¿Í °°Àº ¸í·É¾î·Î °¡»ó service¸¦ ¼³Ä¡, Á¶Àý, Á¦°ÅÇÒ + ¼ö ÀÖ´Ù. ¶Ç, Apache Service Monitor¸¦ »ç¿ëÇÏ¿© Windows 9x + °¡»ó service¸¦ °ü¸®ÇÒ ¼ö ÀÖ´Ù.

+ +
top
+
+

¾ÆÆÄÄ¡¸¦ ÄÜ¼Ö ÇÁ·Î±×·¥À¸·Î ½ÇÇàÇϱâ

+ + +

ÀϹÝÀûÀ¸·Î ¾ÆÆÄÄ¡¸¦ service·Î ½ÇÇàÇÏ±æ ±ÇÇÑ´Ù. ±×·¯³ª + ¸í·ÉÇà¿¡¼­ ½ÇÇàÇÏ´Â°Ô ÆíÇÑ °æ¿ì°¡ ÀÖ´Ù (Windows 9x¿¡¼­´Â + service¸¦ ¾ÈÁ¤ÀûÀ¸·Î Áö¿øÇÏÁö ¾Ê±â¶§¹®¿¡ ¸í·ÉÇà¿¡¼­ ¾ÆÆÄÄ¡¸¦ + ½ÇÇàÇÏ´Â ¹æ¹ýÀ» ±ÇÇÑ´Ù).

+ +

¾ÆÆÄÄ¡¸¦ ÄÜ¼Ö ÇÁ·Î±×·¥À¸·Î ½ÇÇàÇÏ·Á¸é, ¸í·ÉÇà¿¡¼­ ´ÙÀ½ + ¸í·É¾î¸¦ »ç¿ëÇÑ´Ù:

+ +

+ apache +

+ +

¾ÆÆÄÄ¡´Â Control-C¸¦ ´­·¯¼­ Á¤ÁöÇÒ ¶§±îÁö ½ÇÇàµÈ´Ù.

+ +

¶Ç, ½ÃÀÛ ¸Þ´º --> ÇÁ·Î±×·¥ --> Apache HTTP + Server 2.0.xx --> Control Apache Server¿¡ ¼³Ä¡µÈ + Start Apache in Console ¹Ù·Î°¡±â·Î ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÒ ¼ö ÀÖ´Ù. + ¹Ù·Î°¡±â¸¦ ½ÇÇàÇϸé ÄܼÖâÀ» ¿­°í ±× ¾È¿¡¼­ ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÑ´Ù. + ¾ÆÆÄÄ¡¸¦ service·Î ¼³Ä¡ÇÏÁö ¾Ê¾Ò´Ù¸é, ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏ´Â + ÄܼÖâ¿¡¼­ Control-C¸¦ ´­·¯ ¾ÆÆÄÄ¡¸¦ Áß´ÜÇÒ¶§±îÁö âÀÌ ¶°ÀÖ´Ù. + ÀÌ °æ¿ì ¼­¹ö´Â ¸îÃʾȿ¡ Á¾·áÇÑ´Ù. ±×·¯³ª, ¾ÆÆÄÄ¡¸¦ service·Î + ¼³Ä¡ÇÏ¿´´Ù¸é ¹Ù·Î°¡±â´Â service¸¦ ½ÃÀÛÇÑ´Ù. ¾ÆÆÄÄ¡ service°¡ + ÀÌ¹Ì ½ÇÇàÁßÀ̶ó¸é ¹Ù·Î°¡±â´Â ¾Æ¹«Àϵµ ÇÏÁö ¾Ê´Â´Ù.

+ +

´Ù¸¥ ÄܼÖâÀ» ¿­°í ´ÙÀ½°ú °°ÀÌ ÀÔ·ÂÇÏ¿© ½ÇÇàÁßÀÎ ¾ÆÆÄÄ¡¸¦ + Á¾·áÇÒ ¼ö ÀÖ´Ù:

+ +

+ apache -k shutdown +

+ +

ÀÌ ¹æ¹ýÀº ¾ÆÆÄÄ¡°¡ ÇöÀç ÀÛ¾÷À» ¸¶Ä¡°í Á¡ÀÝ°Ô Á¾·áÇÒ ¼ö + Àֱ⶧¹®¿¡ Control-C º¸´Ù ³´´Ù.

+ +

¶Ç, ¾ÆÆÄÄ¡¸¦ Àç½ÃÀÛÇÒ ¼ö ÀÖ´Ù. ÀÌ °æ¿ì ¼³Á¤ÆÄÀÏÀ» ´Ù½Ã + Àд´Ù. ÁøÇàÁßÀÎ ÀÛ¾÷À» Áß°£¿¡ ²÷Áö¾Ê°í ¿Ï·áÇÑ´Ù. ¾ÆÆÄÄ¡¸¦ + Àç½ÃÀÛÇÏ·Á¸é:

+ +

+ apache -k restart +

+ +
À¯´Ð½º¿ë ¾ÆÆÄÄ¡¿¡ Àͼ÷ÇÑ »ç¶÷À» À§ÇØ: ÀÌ ¸í·É¾î´Â + kill -TERM pid³ª kill -USR1 + pidÀÇ WindowsÆÇÀÌ´Ù. ¸í·ÉÇà ¿É¼Ç + -k´Â À¯´Ð½º kill ¸í·É¾î À̸§À» + º»µû Áö¾ú´Ù.
+ +

¾ÆÆÄÄ¡ ÄܼÖâÀÌ Áï½Ã ȤÀº ½ÃÀÛÈÄ °©Àڱ⠴ÝÄ¡¸é ½ÃÀÛ ¸Þ´º + --> ÇÁ·Î±×·¥ÀÇ ¸í·É ÇÁ·ÒÇÁÆ®¸¦ ½ÇÇàÇÑ´Ù. ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÑ + Æú´õ·Î °¡¼­ apache ¸í·É¾î¸¦ ½ÇÇàÇغ¸°í ¹ß»ýÇÑ + ¿À·ù¹®À» »ìÆ캻´Ù. ±×¸®°í logs Æú´õ·Î °¡¼­, ¼³Á¤ÆÄÀÏÀÌ + À߸øµÇ¾ú´ÂÁö error.log ÆÄÀÏÀ» »ìÆ캻´Ù. ¾ÆÆÄÄ¡¸¦ + ¼³Ä¡ÇÒ¶§ ±âº»°ªÀ» »ç¿ëÇß´Ù¸é ´ÙÀ½°ú °°´Ù:

+ +

+ c:
+ cd "\Program Files\Apache Group\Apache2\bin"
+ apache +

+ +

¾ÆÆÄÄ¡°¡ Á¤ÁöÇÒ ¶§±îÁö ±â´Ù¸®°Å³ª Control-C¸¦ ´©¸¥´Ù. + ±×¸®°í ´ÙÀ½°ú °°ÀÌ ÀÔ·ÂÇÑ´Ù:

+ +

+ cd ..\logs
+ more < error.log +

+ +

¾ÆÆÄÄ¡¸¦ ´Ù·ê¶§ ¾ÆÆÄÄ¡°¡ ¾î¶»°Ô ¼³Á¤ÆÄÀÏÀ» ã´ÂÁö ¾Æ´Â + °ÍÀÌ Áß¿äÇÏ´Ù. µÎ°¡Áö ¹æ¹ýÀ¸·Î ¸í·ÉÇà¿¡¼­ ¼³Á¤ÆÄÀÏÀ» ÁöÁ¤ÇÒ + ¼ö ÀÖ´Ù:

+ +
    +

  • -f´Â ¼³Á¤ÆÄÀÏÀÇ Àý´ë°æ·Î ȤÀº »ó´ë°æ·Î¸¦ + ÁöÁ¤ÇÑ´Ù:

    + +

    + apache -f "c:\my server files\anotherconfig.conf" +

    + +

    ȤÀº

    + +

    + apache -f files\anotherconfig.conf +

    • + +

  • -nÀº ¾ÆÆÄÄ¡ service¸¦ ¼±ÅÃÇÏ°í, ÇØ´ç + serviceÀÇ ¼³Á¤ÆÄÀÏÀ» »ç¿ëÇÑ´Ù:

    + +

    + apache -n "MyServiceName" +

    +
    • +
+ +

µÎ °æ¿ì ¸ðµÎ ¼³Á¤ÆÄÀÏÀÌ ÀûÀýÇÑ ServerRoot¸¦ ÁöÁ¤ÇØ¾ß ÇÑ´Ù.

+ +

-f³ª -nÀ¸·Î ¼³Á¤ÆÄÀÏÀ» ÁöÁ¤ÇÏÁö + ¾ÊÀ¸¸é, ¾ÆÆÄÄ¡´Â conf\httpd.conf¿Í °°ÀÌ ¼­¹ö¿¡ + ÄÄÆÄÀÏµÈ ÆÄÀϸíÀ» »ç¿ëÇÑ´Ù. ÀÌ ±âº» °æ·Î´Â ¼³Ä¡ µð·ºÅ丮¿¡ + »ó´ëÀûÀÌ´Ù. ´ÙÀ½°ú °°ÀÌ -V ¿É¼ÇÀ¸·Î ¾ÆÆÄÄ¡¸¦ + ½ÇÇàÇϸé SERVER_CONFIG_FILEÀ̶õ Ç׸ñ¿¡¼­ ¼­¹ö°¡ + »ç¿ëÇÒ ¼³Á¤ÆÄÀÏÀ» ¾Ë ¼ö ÀÖ´Ù:

+ +

+ apache -V +

+ +

¾ÆÆÄÄ¡´Â ´ÙÀ½ ¼ø¼­´ë·Î ServerRoot¸¦ ã´Â´Ù:

+ +
    +
  1. -C ¸í·ÉÇà ¿É¼Ç¿¡ »ç¿ëÇÑ ServerRoot Áö½Ã¾î.
    2. + +
  2. -d ¸í·ÉÇà ¿É¼Ç.
    3. + +
  3. ÇöÀç ÀÛ¾÷ µð·ºÅ丮.
    4. + +
  4. ¹ÙÀ̳ʸ® ¼³Ä¡¸¦ Çß´Ù¸é ¼³Ä¡ÇÒ¶§ ¸¸µç registry Ç׸ñ.
    5. + +
  5. ¼­¹ö¿¡ ÄÄÆÄÀÏµÈ server root. ±âº»°ªÀº + /apacheÀÌ°í, apache -V¸¦ ½ÇÇàÇϸé + HTTPD_ROOT¶ó´Â Ç׸ñ¿¡¼­ È®ÀÎÇÒ ¼ö ÀÖ´Ù.
    6. +
+ +

¼³Ä¡ÇÒ¶§ À©µµ¿ìÁî ·¹Áö½ºÆ®¸®¿¡ ¹öÀü ƯÀ¯ÀÇ ·¹Áö½ºÆ®¸® + Å°¸¦ ¸¸µç´Ù. Å°ÀÇ À§Ä¡´Â ¼³Ä¡ Á¾·ù¿¡ µû¶ó ´Ù¸£´Ù. install + Apache for all users¸¦ ¼±ÅÃÇÏ¿´´Ù¸é + HKEY_LOCAL_MACHINE ¾Æ·¡¿¡ ´ÙÀ½°ú °°Àº Å°¸¦ + ¸¸µç´Ù (¹°·Ð ¹öÀü¹øÈ£´Â ¾ÆÆÄÄ¡ ¹öÀü¸¶´Ù ´Ù¸£´Ù): +

+ +

+ HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache\2.0.43 +

+ +

"¸ðµç »ç¿ëÀÚ"¸¦ ´ë»óÀ¸·Î ¾ÆÆÄÄ¡¸¦ ¼³Ä¡ÇÏ¿´´Ù¸é + HKEY_CURRENT_USER ¾Æ·¡ Å°°¡ »ý±ä´Ù. ³»¿ëÀº + ÇöÀç ·Î±×¿ÂÇÑ »ç¿ëÀÚ¿¡ µû¶ó ´Ù¸£´Ù:

+ +

+ HKEY_CURRENT_USER\SOFTWARE\Apache Group\Apache\2.0.43 +

+ +

Å° À̸§ÀÌ ¼­¹ö¿¡ ÄÄÆÄÀϵDZ⶧¹®¿¡ ÇöÀç ¹öÀüÀ» °Çµå¸®Áö¾Ê°í + »õ·Î¿î ¹öÀüÀ» ¼³Ä¡ÇÏ¿© Å×½ºÆ®Çغ¼ ¼ö ÀÖ´Ù. ¹°·Ð »õ ¹öÀüÀ» + ´Ù¸¥ ¹öÀü°ú °°Àº µð·ºÅ丮¿¡ ¼³Ä¡ÇÏÁö¾Êµµ·Ï ÁÖÀÇÇØ¾ß ÇÑ´Ù.

+ +

¹ÙÀ̳ʸ® ¼³Ä¡¸¦ ÇÏÁö ¾ÊÀº °æ¿ì ¾ÆÆÄÄ¡´Â ·¹Áö½ºÆ®¸® Å°°¡ + ¾ø´Ù°í ºÒÆòÇÒ ¼ö ÀÖ´Ù. ¼­¹ö°¡ ´Ù¸¥ ¹æ¹ýÀ¸·Î ¼³Á¤ÆÄÀÏÀ» ãÀ» + ¼ö ÀÖ´Ù¸é ÀÌ °æ°í¸¦ ¹«½ÃÇصµ µÈ´Ù.

+ +

Å°ÀÇ °ªÀº ServerRoot + µð·ºÅ丮À̸ç, ÀÌ µð·ºÅ丮¿¡ conf¶ó´Â ÇÏÀ§µð·ºÅ丮°¡ + ÀÖ´Ù. ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇϸé ÀÌ ÇÏÀ§µð·ºÅ丮¿¡¼­ + httpd.conf ÆÄÀÏÀ» Àд´Ù. ÀÌ ÆÄÀÏ¿¡ ³ª¿À´Â + ServerRoot Áö½Ã¾î°¡ + ·¹Áö½ºÆ®¸® Å°¿¡ ³ª¿Â µð·ºÅ丮¿Í ´Ù¸£´Ù¸é, ¾ÆÆÄÄ¡´Â ·¹Áö½ºÆ®¸®¿¡¼­ + ¾òÀº °ªÀ» ¹«½ÃÇÏ°í ¾ÕÀ¸·Î ¼³Á¤ÆÄÀÏ¿¡ ³ª¿Â µð·ºÅ丮¸¦ »ç¿ëÇÑ´Ù. + ¾ÆÆÄÄ¡ µð·ºÅ丮³ª ¼³Á¤ÆÄÀÏÀ» ´Ù¸¥ Àå¼Ò·Î º¹»çÇÏ¸é ¹Ýµå½Ã + httpd.conf ÆÄÀÏ¿¡ ÀÖ´Â ServerRoot Áö½Ã¾î¸¦ ±× À§Ä¡·Î + ¼öÁ¤Ç϶ó.

+ +
top
+
+

Á¤»óÀûÀ¸·Î ¼³Ä¡µÇ¾ú´ÂÁö °Ë»çÇϱâ

+ + +

(ÄܼÖâÀ̳ª service¸¦ ÅëÇØ) ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇϸé (¼³Á¤ÆÄÀÏÀÇ + Listen Áö½Ã¾î¸¦ + ¼öÁ¤Çϰųª ¾ÆÆÄÄ¡¸¦ "ÇöÀç »ç¿ëÀÚ¸¸" ´ë»óÀ¸·Î ¼³Ä¡ÇÏÁö ¾Ê´Â + °æ¿ì) 80¹ø Æ÷Æ®¸¦ ±â´Ù¸°´Ù. ºê¶ó¿ìÀú¸¦ ½ÃÀÛÇÏ°í URLÀ» ÀÔ·ÂÇÏ¿© + ¼­¹öÀÇ ±âº» ÆäÀÌÁö¿¡ Á¢±ÙÇÏ´Ù:

+ +

+ http://localhost/ +

+ +

¾ÆÆÄÄ¡´Â ¾ÆÆÄÄ¡ ¼³¸í¼­ ¸µÅ©°¡ Àִ ȯ¿µÆäÀÌÁö¸¦ º¸¿©Áà¾ß + ÇÑ´Ù. ¾Æ¹« Àϵµ ÀϾÁö ¾Ê°Å³ª ¿À·ù°¡ ³ª¿À¸é, logs + ÇÏÀ§µð·ºÅ丮¿¡ ÀÖ´Â error.log ÆÄÀÏÀ» »ìÆìºÁ¶ó. + È£½ºÆ®°¡ ³×Æ®¿÷¿¡ ¿¬°áµÇÀÖÁö ¾Ê°Å³ª DNS (Domain Name Service) + ¼³Á¤¿¡ ¹®Á¦°¡ ÀÖ´Ù¸é ´ÙÀ½ URLÀ» »ç¿ëÇØ¾ß ÇÑ´Ù:

+ +

+ http://127.0.0.1/ +

+ +

±âº» ¼³Ä¡°¡ µ¿ÀÛÇϸé conf ÇÏÀ§µð·ºÅ丮¿¡ + ÀÖ´Â ÆÄÀÏÀ» ÀûÀýÈ÷ ¼³Á¤ÇÑ´Ù. ¶Ç, Windows NT ¾ÆÆÄÄ¡ service + ¼³Á¤À» ¼öÁ¤ÇÑ °æ¿ì ¸ÕÀú ¸í·ÉÇà¿¡¼­ ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇÏ¿© ¿À·ù°¡ + ¹ß»ýÇÏÁö¾Ê´ÂÁö È®ÀÎÇØ¾ß ÇÑ´Ù.

+ +

¾ÆÆÄÄ¡°¡ ´Ù¸¥ TCP/IP ÇÁ·Î±×·¥°ú °°Àº Æ÷Æ®¸¦ °øÀ¯ÇÒ ¼ö + ¾ø±â¶§¹®¿¡ ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇϱâ Àü¿¡ ´Ù¸¥ + ¼­ºñ½º¸¦ Áß´Ü, Á¦°Å, Àç¼³Á¤ÇØ¾ß ÇÒÁöµµ ¸ð¸¥´Ù. ´Ù¸¥ À¥¼­¹ö³ª + ƯÁ¤ ¹æÈ­º® ¼­¹ö½º¿Í Ãæµ¹ÇÒ ¼ö ÀÖ´Ù. +

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/ab.html b/docs/manual/programs/ab.html new file mode 100644 index 00000000..3ba123c4 --- /dev/null +++ b/docs/manual/programs/ab.html @@ -0,0 +1,7 @@ +URI: ab.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: ab.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/ab.html.en b/docs/manual/programs/ab.html.en new file mode 100644 index 00000000..ece248b4 --- /dev/null +++ b/docs/manual/programs/ab.html.en @@ -0,0 +1,198 @@ + + + +ab - Apache HTTP server benchmarking tool - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

ab - Apache HTTP server benchmarking tool

+
+

Available Languages:  en  | + ko 

+
+ +

ab is a tool for benchmarking your Apache Hypertext + Transfer Protocol (HTTP) server. It is designed to give you an impression + of how your current Apache installation performs. This especially shows + you how many requests per second your Apache installation is capable of + serving.

+
+

See also

+
top
+
+

Synopsis

+

ab + [ -A auth-username:password ] + [ -c concurrency ] + [ -C cookie-name=value ] + [ -d ] + [ -e csv-file ] + [ -g gnuplot-file ] + [ -h ] + [ -H custom-header ] + [ -i ] + [ -k ] + [ -n requests ] + [ -p POST-file ] + [ -P proxy-auth-username:password ] + [ -q ] + [ -s ] + [ -S ] + [ -t timelimit ] + [ -T content-type ] + [ -v verbosity] + [ -V ] + [ -w ] + [ -x <table>-attributes ] + [ -X proxy[:port] ] + [ -y <tr>-attributes ] + [ -z <td>-attributes ] + [http://]hostname[:port]/path

+
top
+
+

Options

+
+
-A auth-username:password
+
Supply BASIC Authentication credentials to the server. The username and + password are separated by a single : and sent on the wire + base64 encoded. The string is sent regardless of whether the server needs + it (i.e., has sent an 401 authentication needed).
+ +
-c concurrency
+
Number of multiple requests to perform at a time. Default is one + request at a time.
+ +
-C cookie-name=value
+
Add a Cookie: line to the request. The argument is + typically in the form of a name=value + pair. This field is repeatable.
+ +
-d
+
Do not display the "percentage served within XX [ms] table". (legacy + support).
+ +
-e csv-file
+
Write a Comma separated value (CSV) file which contains for each + percentage (from 1% to 100%) the time (in milliseconds) it took to serve + that percentage of the requests. This is usually more useful than the + 'gnuplot' file; as the results are already 'binned'.
+ +
-g gnuplot-file
+
Write all measured values out as a 'gnuplot' or TSV (Tab separate + values) file. This file can easily be imported into packages like Gnuplot, + IDL, Mathematica, Igor or even Excel. The labels are on the first line of + the file.
+ +
-h
+
Display usage information.
+ +
-H custom-header
+
Append extra headers to the request. The argument is typically in + the form of a valid header line, containing a colon-separated field-value + pair (i.e., "Accept-Encoding: zip/zop;8bit").
+ +
-i
+
Do HEAD requests instead of GET.
+ +
-k
+
Enable the HTTP KeepAlive feature, i.e., perform multiple + requests within one HTTP session. Default is no KeepAlive.
+ +
-n requests
+
Number of requests to perform for the benchmarking session. The default + is to just perform a single request which usually leads to + non-representative benchmarking results.
+ +
-p POST-file
+
File containing data to POST.
+ +
-P proxy-auth-username:password
+
Supply BASIC Authentication credentials to a proxy en-route. The + username and password are separated by a single : and sent on + the wire base64 encoded. The string is sent regardless of whether the + proxy needs it (i.e., has sent an 407 proxy authentication + needed).
+ +
-q
+
When processing more than 150 requests, ab outputs a + progress count on stderr every 10% or 100 requests or so. The + -q flag will suppress these messages.
+ +
-s
+
When compiled in (ab -h will show you) use the SSL + protected https rather than the http protocol. + This feature is experimental and very rudimentary. You probably + do not want to use it.
+ +
-S
+
Do not display the median and standard deviation values, nor display + the warning/error messages when the average and median are more than + one or two times the standard deviation apart. And default to the + min/avg/max values. (legacy support).
+ +
-t timelimit
+
Maximum number of seconds to spend for benchmarking. This implies a + -n 50000 internally. Use this to benchmark the server within a + fixed total amount of time. Per default there is no timelimit.
+ +
-T content-type
+
Content-type header to use for POST data.
+ +
-v verbosity
+
Set verbosity level - 4 and above prints information on + headers, 3 and above prints response codes (404, 200, etc.), + 2 and above prints warnings and info.
+ +
-V
+
Display version number and exit.
+ +
-w
+
Print out results in HTML tables. Default table is two columns wide, + with a white background.
+ +
-x <table>-attributes
+
String to use as attributes for <table>. Attributes + are inserted <table here >.
+ +
-X proxy[:port]
+
Use a proxy server for the requests.
+ +
-y <tr>-attributes
+
String to use as attributes for <tr>.
+ +
-z <td>-attributes
+
String to use as attributes for <td>.
+
+
top
+
+

Bugs

+

There are various statically declared buffers of fixed length. Combined + with the lazy parsing of the command line arguments, the response headers + from the server and other external inputs, this might bite you.

+ +

It does not implement HTTP/1.x fully; only accepts some 'expected' forms + of responses. The rather heavy use of strstr(3) shows up top + in profile, which might indicate a performance problem; i.e., you + would measure the ab performance rather than the server's.

+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/ab.html.ko.euc-kr b/docs/manual/programs/ab.html.ko.euc-kr new file mode 100644 index 00000000..1d47e404 --- /dev/null +++ b/docs/manual/programs/ab.html.ko.euc-kr @@ -0,0 +1,201 @@ + + + +ab - ¾ÆÆÄÄ¡ À¥¼­¹ö ¼º´É°Ë»ç µµ±¸ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

ab - ¾ÆÆÄÄ¡ À¥¼­¹ö ¼º´É°Ë»ç µµ±¸

+
+

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

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

ab´Â ¾ÆÆÄÄ¡ ÇÏÀÌÆÛÅؽºÆ® Àü¼Û ÇÁ·ÎÅäÄÝ (HTTP) + ¼­¹öÀÇ ¼º´ÉÀ» °Ë»çÇÏ´Â(benchmarking) µµ±¸ÀÌ´Ù. ÇöÀç ¾ÆÆÄÄ¡°¡ + ¾î¶»°Ô µ¿ÀÛÇÏ´ÂÁö ¾Ë·ÁÁØ´Ù. ƯÈ÷ ¾ÆÆÄÄ¡°¡ ÇöÀç ÃÊ´ç ¸î°³ÀÇ + ¿äûÀ» ¼­ºñ½ºÇÏ´ÂÁö ¾Ë·ÁÁØ´Ù.

+
+ +
top
+
+

°³¿ä

+

ab + [ -A auth-username:password ] + [ -c concurrency ] + [ -C cookie-name=value ] + [ -d ] + [ -e csv-file ] + [ -g gnuplot-file ] + [ -h ] + [ -H custom-header ] + [ -i ] + [ -k ] + [ -n requests ] + [ -p POST-file ] + [ -P proxy-auth-username:password ] + [ -q ] + [ -s ] + [ -S ] + [ -t timelimit ] + [ -T content-type ] + [ -v verbosity] + [ -V ] + [ -w ] + [ -x <table>-attributes ] + [ -X proxy[:port] ] + [ -y <tr>-attributes ] + [ -z <td>-attributes ] + [http://]hostname[:port]/path

+
top
+
+

¿É¼Ç

+
+
-A auth-username:password
+
¼­¹ö¿¡°Ô BASIC Authentication Á¤º¸¸¦ Á¦°øÇÑ´Ù. + :À¸·Î ±¸ºÐÇÑ »ç¿ëÀÚ¸í°ú ¾ÏÈ£¸¦ base64 ÀÎÄÚµùÇÏ¿© + Àü¼ÛÇÑ´Ù. ¼­¹ö°¡ Á¤º¸¸¦ ¿ä±¸ÇÏ´ÂÁö (¿¹¸¦ µé¾î, + 401 ÀÎÁõ Çʿ並 º¸³»´ÂÁö) °ü°è¾øÀÌ ¹®ÀÚ¿­À» Àü¼ÛÇÑ´Ù.
+ +
-c concurrency
+
µ¿½Ã¿¡ ¿äûÇÏ´Â ¿äû¼ö. ±âº»ÀûÀ¸·Î Çѹø¿¡ ÇÑ ¿äû¸¸À» + º¸³½´Ù.
+ +
-C cookie-name=value
+
¿äû¿¡ Cookie: Çì´õ¸¦ Ãß°¡ÇÑ´Ù. ¾Æ±Ô¸ÕÆ®´Â + º¸Åë name=value¿Í °°Àº + ½ÖÀÌ´Ù. ÀÌ ¿É¼ÇÀº ¿©·¯¹ø »ç¿ëÇÒ ¼ö ÀÖ´Ù.
+ +
-d
+
"percentage served within XX [ms] table"À» Ãâ·ÂÇÏÁö + ¾Ê´Â´Ù. (ȣȯ¼ºÀ» À§ÇØ).
+ +
-e csv-file
+
¿äûÀ» ó¸®Çϴµ¥ °É¸° (¹Ð¸®ÃÊ ´ÜÀ§) ½Ã°£µéÀÇ (1%¿¡¼­ + 100%) ´©Àû¹éºÐÀ²À» ½°Ç¥·Î ±¸ºÐÇÑ Çü½Ä(CSV)À¸·Î Ãâ·ÂÇÑ´Ù. + °á°ú¸¦ ÀÌ¹Ì 'Á¤¸®'ÇÏ¿´±â¶§¹®¿¡ 'gnuplot' ÆÄÀϺ¸´Ù º¸Åë ´õ + À¯¿ëÇÏ´Ù.
+ +
-g gnuplot-file
+
ÃøÁ¤ÇÑ ¸ðµç °ªÀ» 'gnuplot' ȤÀº TSV (Tab separate values, + ÅÇÀ¸·Î ±¸ºÐÇÑ °ª) ÆÄÀÏ¿¡ ±â·ÏÇÑ´Ù. Gnuplot, IDL, Mathematica, + Igor, ½ÉÁö¾î Excel °°Àº ÇÁ·Î±×·¥¿¡¼­µµ ÀÌ·± ÆÄÀÏÀ» ½±°Ô + ÀÐÀ» ¼ö ÀÖ´Ù. ÆÄÀÏÀÇ Ã¹¹ø° ÁÙ¿¡ Ç׸ñÀ̸§ÀÌ ³ª¿Â´Ù.
+ +
-h
+
»ç¿ë¹ýÀ» Ãâ·ÂÇÑ´Ù.
+ +
-H custom-header
+
¿äû¿¡ Çì´õ¸¦ Ãß°¡ÇÑ´Ù. ¾Æ±Ô¸ÕÆ®´Â º¸Åë ÄÝ·ÐÀ¸·Î ±¸ºÐÇÑ + ½ÖÀÎ (¿¹¸¦ µé¾î, + "Accept-Encoding: zip/zop;8bit") À¯È¿ÇÑ + Çì´õÁÙÀÌ´Ù.
+ +
-i
+
GET ´ë½Å HEAD ¿äûÀ» ÇÑ´Ù.
+ +
-k
+
HTTP KeepAlive ±â´ÉÀ» »ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î, + ÇÑ HTTP ¼¼¼Ç¿¡¼­ ¿©·¯ ¿äûÀ» ÇÑ´Ù. ±âº»ÀûÀ¸·Î KeepAlive¸¦ + »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
-n requests
+
¼º´ÉÀ» °Ë»çÇϱâÀ§ÇØ º¸³»´Â ¿äû¼ö. ±âº»°ªÀ¸·Î ¿äûÀ» + Çѹø¸¸ º¸³»±â¶§¹®¿¡ ÀϹÝÀûÀÎ ¼º´É°Ë»ç °á°ú¸¦ ¾òÀ» ¼ö ¾ø´Ù.
+ +
-p POST-file
+
POST ÀÚ·á ÆÄÀÏ.
+ +
-P proxy-auth-username:password
+
ÇÁ·Ï½Ã¸¦ ÅëÇØ BASIC Authentication Á¤º¸¸¦ Á¦°øÇÑ´Ù. + :·Î ±¸ºÐÇÑ »ç¿ëÀÚ¸í°ú ¾ÏÈ£¸¦ base64 ÀÎÄÚµùÇÏ¿© + Àü¼ÛÇÑ´Ù. ÇÁ·Ï½Ã°¡ Á¤º¸¸¦ ¿ä±¸ÇÏ´ÂÁö (¿¹¸¦ µé¾î, + 401 ÀÎÁõ Çʿ並 º¸³»´ÂÁö) °ü°è¾øÀÌ ¹®ÀÚ¿­À» Àü¼ÛÇÑ´Ù.
+ +
-q
+
150°³ ÀÌ»ó ¿äûÀ» º¸³¾¶§ ab´Â 10% ȤÀº + ¸Å 100 ¿äû´ç Ç¥ÁØ¿À·ù¿¡ ÁøÇà»óȲÀ» Ãâ·ÂÇÑ´Ù. + -q ¿É¼ÇÀº ÀÌ ¹®±¸¸¦ Ãâ·ÂÇÏÁö ¾Ê´Â´Ù.
+ +
-s
+
±â´ÉÀ» Ãß°¡ÇÏ¿© ÄÄÆÄÀÏÇÏ¿´´Ù¸é (ab -h·Î + È®ÀÎÇÒ ¼ö ÀÖ´Ù) http ÇÁ·ÎÅäÄÝ ´ë½Å SSLÀ» »ç¿ëÇÑ + https ÇÁ·ÎÅäÄÝÀ» »ç¿ëÇÑ´Ù. ÀÌ ±â´ÉÀº ½ÇÇèÀûÀÌ°í + ¸Å¿ì ±âÃÊÀûÀÌ´Ù. ¾Æ¸¶µµ »ç¿ëÀ» ²¨·ÁÇÒ °ÍÀÌ´Ù.
+ +
-S
+
Áß°£°ª°ú Ç¥ÁØÆíÂ÷¸¦ Ãâ·ÂÇÏÁö ¾Ê°í, Æò±Õ°ú Áß°£°ªÀÇ Â÷ÀÌ°¡ + Ç¥ÁØÆíÂ÷º¸´Ù Å©´õ¶óµµ °æ°í/¿À·ù¸¦ Ãâ·ÂÇÏÁö ¾Ê´Â´Ù. + ÃÖ¼Ò/Æò±Õ/ÃÖ´ë °ªÀ» Ãâ·ÂÇÑ´Ù. (ȣȯ¼ºÀ» À§ÇØ).
+ +
-t timelimit
+
¼º´ÉÀ» °Ë»çÇÏ´Â ÃÖ´ë ÃÊ´ÜÀ§ ½Ã°£. ³»ºÎÀûÀ¸·Î + -n 50000À» °¡Á¤ÇÑ´Ù. Á¤ÇØÁø ½Ã°£µ¿¾È ¼­¹ö ¼º´ÉÀ» + °Ë»çÇÒ¶§ »ç¿ëÇÑ´Ù. ±âº»ÀûÀ¸·Î ½Ã°£Á¦ÇÑ ¾øÀÌ °Ë»çÇÑ´Ù.
+ +
-T content-type
+
POST ÀÚ·áÀÇ Content-type Çì´õ.
+ +
-v verbosity
+
Ãâ·ÂÀÇ ÀÚ¼¼ÇÔ ¼öÁØÀ» ÁöÁ¤ÇÑ´Ù. 4 ÀÌ»óÀ̸é + Çì´õ¿¡ ´ëÇÑ Á¤º¸¸¦, 3 ÀÌ»óÀ̸é (404, 202, µî) + ÀÀ´äÄڵ带, 2 ÀÌ»óÀÌ¸é °æ°í(warning)¿Í + Á¤º¸(info)¸¦ Ãâ·ÂÇÑ´Ù.
+ +
-V
+
¹öÀüÀ» Ãâ·ÂÇÏ°í Á¾·áÇÑ´Ù.
+ +
-w
+
°á°ú¸¦ HTML Ç¥·Î Ãâ·ÂÇÑ´Ù. ±âº»ÀûÀ¸·Î Ç¥¸¦ Èò ¹è°æ¿¡ + µÎ ¿­·Î ÀÛ¼ºÇÑ´Ù.
+ +
-x <table>-attributes
+
<table>ÀÇ ¼Ó¼ºÀ¸·Î »ç¿ëÇÒ ¹®ÀÚ¿­. + ¼Ó¼ºÀ» <table ¿©±â¿¡ > + Ãß°¡ÇÑ´Ù.
+ +
-X proxy[:port]
+
ÇÁ·Ï½Ã ¼­¹ö¸¦ »ç¿ëÇÏ¿© ¿äûÇÑ´Ù.
+ +
-y <tr>-attributes
+
<tr>ÀÇ ¼Ó¼ºÀ¸·Î »ç¿ëÇÒ ¹®ÀÚ¿­.
+ +
-z <td>-attributes
+
<td>ÀÇ ¼Ó¼ºÀ¸·Î »ç¿ëÇÒ ¹®ÀÚ¿­.
+
+
top
+
+

¹ö±×

+

Á¤ÀûÀ¸·Î ±æÀÌ°¡ °íÁ¤µÈ ¹öÆÛ¸¦ ¸¹ÀÌ »ç¿ëÇÑ´Ù. ¸í·ÉÇà + ¾Æ±Ô¸ÕÆ®, ¼­¹öÀÇ ÀÀ´ä Çì´õ, ´Ù¸¥ ¿ÜºÎ ÀԷµéÀ» °°ÀÌ + ÀоîµéÀ̸鼭 ¹®Á¦°¡ ¹ß»ýÇÒ ¼ö ÀÖ´Ù.

+ +

ÀÌ ÇÁ·Î±×·¥Àº HTTP/1.x¸¦ ¿ÏÀüÈ÷ ±¸ÇöÇÏÁö ¾Ê´Â´Ù; ´ÜÁö + '±â´ëÇÏ´Â' Çü½ÄÀÇ ÀÀ´ä¸¸À» ¹Þ´Â´Ù. strstr(3)À» + ¸Å¿ì ¸¹ÀÌ »ç¿ë±â¶§¹®¿¡ ¼Óµµ°¡ ¹®Á¦°¡ µÉ ¼ö ÀÖ´Ù; Áï, + ¼­¹ö ¼º´Éº¸´Ù´Â ab ¼º´ÉÀ» ÃøÁ¤ÇÏ°Ô µÉ ¼öµµ + ÀÖ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/apachectl.html b/docs/manual/programs/apachectl.html new file mode 100644 index 00000000..b3966d8d --- /dev/null +++ b/docs/manual/programs/apachectl.html @@ -0,0 +1,7 @@ +URI: apachectl.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: apachectl.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/apachectl.html.en b/docs/manual/programs/apachectl.html.en new file mode 100644 index 00000000..8f7c14c2 --- /dev/null +++ b/docs/manual/programs/apachectl.html.en @@ -0,0 +1,158 @@ + + + +apachectl - Apache HTTP Server Control Interface - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

apachectl - Apache HTTP Server Control Interface

+
+

Available Languages:  en  | + ko 

+
+ +

apachectl is a front end to the Apache HyperText + Transfer Protocol (HTTP) server. It is designed to help the + administrator control the functioning of the Apache + httpd daemon.

+ +

The apachectl script can operate in two modes. + First, it can act as a simple front-end to the httpd + command that simply sets any necessary environment variables and + then invokes httpd, passing through any command line + arguments. Second, apachectl can act as a SysV init + script, taking simple one-word arguments like start, + restart, and stop, and translating them + into appropriate signals to httpd.

+ +

If your Apache installation uses non-standard paths, you will + need to edit the apachectl script to set the + appropriate paths to the httpd binary. You can also + specify any necessary httpd command line arguments. + See the comments in the script for details.

+ +

The apachectl script returns a 0 exit value on + success, and >0 if an error occurs. For more details, view + the comments in the script.

+
+ +
top
+
+

Synopsis

+ +

When acting in pass-through mode, apachectl can take +all the arguments available for the httpd +binary.

+ +

apachectl [ httpd-argument ]

+ +

When acting in SysV init mode, apachectl takes simple, +one-word commands, defined below.

+ +

apachectl command

+ +
top
+
+

Options

+ +

Only the SysV init-style options are defined here. Other arguments +are defined on the httpd manual page.

+ +
+ +
start
+ +
Start the Apache httpd daemon. Gives an error if it +is already running. This is equivalent to apachectl -k +start.
+ +
stop
+ +
Stops the Apache httpd daemon. This is equivalent to +apachectl -k stop.
+ +
restart
+ +
Restarts the Apache httpd daemon. If the daemon is +not running, it is started. This command automatically checks the +configuration files as in configtest before initiating +the restart to make sure the daemon doesn't die. This is equivalent +to apachectl -k restart.
+ +
fullstatus
+ +
Displays a full status report from mod_status. +For this to work, you need to have mod_status enabled +on your server and a text-based browser such as lynx +available on your system. The URL used to access the status report +can be set by editing the STATUSURL variable in the +script.
+ +
status
+ +
Displays a brief status report. Similar to the +fullstatus option, except that the list of requests +currently being served is omitted.
+ +
graceful
+ +
Gracefully restarts the Apache httpd daemon. If the +daemon is not running, it is started. This differs from a normal +restart in that currently open connections are not aborted. A side +effect is that old log files will not be closed immediately. This +means that if used in a log rotation script, a substantial delay may +be necessary to ensure that the old log files are closed before +processing them. This command automatically checks the configuration +files as in configtest before initiating the +restart to make sure Apache doesn't die. This is equivalent to +apachectl -k graceful.
+ +
graceful-stop
+ +
Gracefully stops the Apache httpd daemon. +This differs from a normal stop in that currently open connections are not +aborted. A side effect is that old log files will not be closed immediately. +This is equivalent to apachectl -k graceful-stop.
+ +
configtest
+ +
Run a configuration file syntax test. It parses the configuration +files and either reports Syntax Ok +or detailed information about the particular syntax error. This is +equivalent to apachectl -t.
+ +
+ +

The following option was available in earlier versions but has been removed.

+ +
+ +
startssl
+ +
To start httpd with SSL support, you should edit +your configuration file to include the relevant directives and then +use the normal apachectl start.
+ +
+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/apachectl.html.ko.euc-kr b/docs/manual/programs/apachectl.html.ko.euc-kr new file mode 100644 index 00000000..11d17675 --- /dev/null +++ b/docs/manual/programs/apachectl.html.ko.euc-kr @@ -0,0 +1,144 @@ + + + +apachectl - ¾ÆÆÄÄ¡ À¥¼­¹ö Á¶Àý ÀÎÅÍÆäÀ̽º - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

apachectl - ¾ÆÆÄÄ¡ À¥¼­¹ö Á¶Àý ÀÎÅÍÆäÀ̽º

+
+

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

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

apachectlÀº ¾ÆÆÄÄ¡ ÇÏÀÌÆÛÅؽºÆ® Àü¼Û + ÇÁ·ÎÅäÄÝ (HTTP) ¼­¹öÀÇ ¾Õ´ÜÀÌ´Ù. ÀÌ ÇÁ·Î±×·¥Àº °ü¸®ÀÚ°¡ + ¾ÆÆÄÄ¡ httpd µ¥¸óÀ» Á¶Á¤Çϵµ·Ï + µ½´Â´Ù.

+ +

apachectl ½ºÅ©¸³Æ®´Â µÎ°¡Áö ¹æ¹ýÀ¸·Î ½ÇÇàÇÑ´Ù. + ù¹ø° ¹æ¹ýÀº httpdÀ» ºÎ¸£´Â °£´ÜÇÑ ½ºÅ©¸³Æ® + ¿ªÇÒÀ» ÇÏ¿©, ÇÊ¿äÇÑ È¯°æº¯¼ö¸¦ ¼³Á¤ÇÏ°í ¹ÞÀº ¸í·ÉÇà ¾Æ±Ô¸ÕÆ®¸¦ + °¡Áö°í httpd¸¦ ½ÇÇàÇÑ´Ù. µÎ¹ø° ¹æ¹ýÀº + apachectl¸¦ SysV init ½ºÅ©¸³Æ®·Î »ç¿ëÇÏ¿©, + start, restart, stop + °°Àº ÇÑ´Ü¾î ¾Æ±Ô¸ÕÆ®¸¦ ¹Þ¾Æ¼­ httpd¿¡°Ô + ÀûÀýÇÑ ½ÅÈ£¸¦ º¸³½´Ù.

+ +

¾ÆÆÄÄ¡¸¦ ÀϹÝÀûÀÎ °æ·Î¿¡ ¼³Ä¡ÇÏÁö ¾Ê¾Ò´Ù¸é, ÀûÀýÇÑ + httpd °æ·Î·Î apachectl ½ºÅ©¸³Æ®¸¦ + ¼öÁ¤ÇØ¾ß ÇÑ´Ù. ¶Ç, httpd ¸í·ÉÇà ¾Æ±Ô¸ÕÆ®¸¦ + Ãß°¡·Î ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù. ÀÚ¼¼ÇÑ ³»¿ëÀº ½ºÅ©¸³Æ®ÀÇ ÁÖ¼®À» + Âü°íÇ϶ó.

+ +

apachectl ½ºÅ©¸³Æ®´Â ¼º°ø½Ã Á¾·áÄÚµå 0À», + ¿À·ù½Ã >0À» ¹ÝȯÇÑ´Ù. ÀÚ¼¼ÇÑ ³»¿ëÀº ½ºÅ©¸³Æ®ÀÇ ÁÖ¼®À» + Âü°íÇ϶ó.

+
+ +
top
+
+

°³¿ä

+ +

°£´ÜÇÑ ½ÇÇà ½ºÅ©¸³Æ®·Î µ¿ÀÛÇϸé, apachectlÀº +httpd ½ÇÇàÆÄÀÏÀÇ ¸ðµç ¾Æ±Ô¸ÕÆ®¸¦ ¹Þ´Â´Ù.

+ +

apachectl [ httpd-argument ]

+ +

SysV init ¹æ½ÄÀ¸·Î µ¿ÀÛÇϸé, apachectlÀº ¾Æ·¡¼­ +¼³¸íÇÒ °£´ÜÇÑ ÇÑ´Ü¾î ¸í·É¾î¸¦ ¹Þ´Â´Ù.

+ +

apachectl command

+ +
top
+
+

¿É¼Ç

+ +

¿©±â¼­´Â SysV init-½Ä ¿É¼Ç¸¸ ¼³¸íÇÑ´Ù. ´Ù¸¥ ¿É¼ÇÀº httpd manpage¿¡¼­ ¼³¸íÇÑ´Ù.

+ +
+ +
start
+ +
¾ÆÆÄÄ¡ httpd µ¥¸óÀ» ½ÃÀÛÇÑ´Ù. ÀÌ¹Ì ½ÇÇàÁßÀ̶ó¸é +¿À·ù¸¦ ³½´Ù. apachectl -k start¿Í °°´Ù.
+ +
stop
+ +
¾ÆÆÄÄ¡ httpd µ¥¸óÀ» Áß´ÜÇÑ´Ù. apachectl +-k stop°ú °°´Ù.
+ +
restart
+ +
¾ÆÆÄÄ¡ httpd µ¥¸óÀ» Àç½ÃÀÛÇÑ´Ù. µ¥¸óÀÌ ½ÇÇàÁßÀÌ +¾Æ´Ï¶ó¸é, ½ÃÀÛÇÑ´Ù. µ¥¸óÀÌ Àç½ÃÀ۽à ½ÇÆÐÇÏÁö ¾ÊÀ½À» È®ÀÎÇϱâÀ§ÇØ +Àç½ÃÀÛ Àü¿¡ ÀÚµ¿À¸·Î configtest ¸í·É°ú °°ÀÌ ¼³Á¤ÆÄÀÏÀ» +°Ë»çÇÑ´Ù. apachectl -k restart¿Í °°´Ù.
+ +
fullstatus
+ +
mod_statusÀÇ ¸ðµç »óÅ Á¤º¸¸¦ Ãâ·ÂÇÑ´Ù. +ÀÌ ¸í·ÉÀ» »ç¿ëÇϱâÀ§Çؼ­´Â ¼­¹ö°¡ mod_status¸¦ +»ç¿ëÇÏ°í, ½Ã½ºÅÛ¿¡ lynx °°Àº ¹®ÀÚ±â¹Ý ºê¶ó¿ìÀú°¡ +ÇÊ¿äÇÏ´Ù. »óÅ Á¤º¸¿¡ Á¢±ÙÇÏ´Â URLÀº ½ºÅ©¸³Æ®ÀÇ +STATUSURL º¯¼ö¸¦ ¼öÁ¤ÇÏ¿© ¼³Á¤ÇÒ ¼ö ÀÖ´Ù.
+ +
status
+ +
°£´ÜÇÑ »óÅ Á¤º¸¸¦ Ãâ·ÂÇÑ´Ù. fullstatus ¿É¼Ç°ú +ºñ½ÁÇÏÁö¸¸, ÇöÀç ¼­ºñ½ºÁßÀÎ ¿äû ¸ñ·ÏÀ» Ãâ·ÂÇÏÁö ¾Ê´Â´Ù.
+ +
graceful
+ +
¾ÆÆÄÄ¡ httpd µ¥¸óÀ» Á¡ÀÝ°Ô(gracefully) Àç½ÃÀÛÇÑ´Ù. +µ¥¸óÀÌ ½ÇÇàÁßÀÌ ¾Æ´Ï¶ó¸é, ½ÃÀÛÇÑ´Ù. ÀϹÝÀûÀÎ Àç½ÃÀÛ°ú ´Þ¸® ÇöÀç +¿­·ÁÀÖ´Â ¿¬°áÀ» ²÷Áö¾Ê´Â´Ù. ¶Ç, ÀÌÀü ·Î±×ÆÄÀÏÀ» Áï½Ã ´ÝÁö ¾Ê´Â´Ù. +Áï, ·Î±×¼øȯ ½ºÅ©¸³Æ®¿¡¼­ ÀÌ ¸í·ÉÀ» »ç¿ëÇÑ´Ù¸é, ÀÌÀü ·Î±×ÆÄÀÏÀ» +ó¸®ÇϱâÀü¿¡ ·Î±×ÆÄÀÏÀ» ´ÝÇûÀ½À» º¸ÀåÇϱâÀ§ÇØ »ó´çÈ÷ ±â´Ù·Á¾ß +ÇÑ´Ù. ¾ÆÆÄÄ¡°¡ Àç½ÃÀ۽à ½ÇÆÐÇÏÁö ¾ÊÀ½À» È®ÀÎÇϱâÀ§ÇØ Àç½ÃÀÛ +Àü¿¡ ÀÚµ¿À¸·Î configtest ¸í·É°ú °°ÀÌ ¼³Á¤ÆÄÀÏÀ» +°Ë»çÇÑ´Ù. apachectl -k graceful°ú °°´Ù.
+ +
configtest
+ +
¼³Á¤ÆÄÀÏÀÇ ¹®¹ýÀ» °Ë»çÇÑ´Ù. ¼³Á¤ÆÄÀÏÀ» Àаí Syntax +Ok ȤÀº ƯÁ¤ ¼³Á¤¿À·ù¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ Á¤º¸¸¦ ¾Ë·ÁÁØ´Ù. +apachectl -t¿Í °°´Ù.
+ +
+ +

¾Æ·¡ ¿É¼ÇÀ» »ç¿ëÇÒ ¼ö ÀÖÁö¸¸, ¾ÕÀ¸·Î »ç¶óÁú °ÍÀÌ´Ù.

+ +
+ +
startssl
+ +
apachectl -k start -DSSL°ú °°´Ù. ¿ì¸®´Â Á÷Á¢ +¾ÕÀÇ ¸í·É¾î¸¦ »ç¿ëÇϰųª Ç×»ó SSLÀ» »ç¿ëÇϵµ·Ï +httpd.conf¿¡¼­ <IfDefine> ¼½¼ÇÀ» Á¦°ÅÇÏ±æ ±ÇÇÑ´Ù.
+ +
+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/apxs.html b/docs/manual/programs/apxs.html new file mode 100644 index 00000000..b6d6d1de --- /dev/null +++ b/docs/manual/programs/apxs.html @@ -0,0 +1,7 @@ +URI: apxs.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: apxs.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/apxs.html.en b/docs/manual/programs/apxs.html.en new file mode 100644 index 00000000..991b3c88 --- /dev/null +++ b/docs/manual/programs/apxs.html.en @@ -0,0 +1,330 @@ + + + +apxs - APache eXtenSion tool - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

apxs - APache eXtenSion tool

+
+

Available Languages:  en  | + ko 

+
+ +

apxs is a tool for building and installing extension + modules for the Apache HyperText Transfer Protocol (HTTP) server. This is + achieved by building a dynamic shared object (DSO) from one or more source + or object files which then can be loaded into the Apache server + under runtime via the LoadModule + directive from mod_so.

+ +

So to use this extension mechanism your platform has to support the DSO + feature and your Apache httpd binary has to be built with the + mod_so module. The apxs tool automatically + complains if this is not the case. You can check this yourself by manually + running the command

+ +

+ $ httpd -l +

+ +

The module mod_so should be part of the displayed list. + If these requirements are fulfilled you can easily extend your Apache + server's functionality by installing your own modules with the DSO mechanism + by the help of this apxs tool:

+ +

+ $ apxs -i -a -c mod_foo.c
+ gcc -fpic -DSHARED_MODULE -I/path/to/apache/include -c mod_foo.c
+ ld -Bshareable -o mod_foo.so mod_foo.o
+ cp mod_foo.so /path/to/apache/modules/mod_foo.so
+ chmod 755 /path/to/apache/modules/mod_foo.so
+ [activating module `foo' in /path/to/apache/etc/httpd.conf]
+ $ apachectl restart
+ /path/to/apache/sbin/apachectl restart: httpd not running, trying to start
+ [Tue Mar 31 11:27:55 1998] [debug] mod_so.c(303): loaded module foo_module
+ /path/to/apache/sbin/apachectl restart: httpd started
+ $ _ +

+ +

The arguments files can be any C source file (.c), a object + file (.o) or even a library archive (.a). The apxs tool + automatically recognizes these extensions and automatically used the C + source files for compilation while just using the object and archive files + for the linking phase. But when using such pre-compiled objects make sure + they are compiled for position independent code (PIC) to be able to use them + for a dynamically loaded shared object. For instance with GCC you always + just have to use -fpic. For other C compilers consult its + manual page or at watch for the flags apxs uses to compile the + object files.

+ +

For more details about DSO support in Apache read the documentation of + mod_so or perhaps even read the + src/modules/standard/mod_so.c source file.

+
+ +
top
+
+

Synopsis

+

apxs -g + [ -S name=value ] + -n modname

+ +

apxs -q + [ -S name=value ] + query ...

+ +

apxs -c + [ -S name=value ] + [ -o dsofile ] + [ -I incdir ] + [ -D name=value ] + [ -L libdir ] + [ -l libname ] + [ -Wc,compiler-flags ] + [ -Wl,linker-flags ] + files ...

+ +

apxs -i + [ -S name=value ] + [ -n modname ] + [ -a ] + [ -A ] + dso-file ...

+ +

apxs -e + [ -S name=value ] + [ -n modname ] + [ -a ] + [ -A ] + dso-file ...

+
top
+
+

Options

+

Common Options

+
+
-n modname
+
This explicitly sets the module name for the -i (install) + and -g (template generation) option. Use this to explicitly + specify the module name. For option -g this is required, for + option -i the apxs tool tries to determine the + name from the source or (as a fallback) at least by guessing it from the + filename.
+
+ + +

Query Options

+
+
-q
+
Performs a query for apxs's knowledge about certain + settings. The query parameters can be one or more of the + following strings: CC, CFLAGS, + CFLAGS_SHLIB, INCLUDEDIR, LD_SHLIB, + LDFLAGS_SHLIB, LIBEXECDIR, + LIBS_SHLIB, SBINDIR, SYSCONFDIR, + TARGET. + +

Use this for manually determining settings. For instance use

+

+ INC=-I`apxs -q INCLUDEDIR` +

+ +

inside your own Makefiles if you need manual access to Apache's C + header files.

+
+ + +

Configuration Options

+
+
-S name=value
+
This option changes the apxs settings described above.
+
+ + +

Template Generation Options

+
+
-g
+
This generates a subdirectory name (see option + -n) and there two files: A sample module source file named + mod_name.c which can be used as a template for + creating your own modules or as a quick start for playing with the + apxs mechanism. And a corresponding Makefile for even easier + build and installing of this module.
+
+ + +

DSO Compilation Options

+
+
-c
+
This indicates the compilation operation. It first compiles the C + source files (.c) of files into corresponding object files (.o) + and then builds a dynamically shared object in dsofile by + linking these object files plus the remaining object files (.o and .a) of + files. If no -o option is specified the output + file is guessed from the first filename in files and thus + usually defaults to mod_name.so.
+ +
-o dsofile
+
Explicitly specifies the filename of the created dynamically shared + object. If not specified and the name cannot be guessed from the + files list, the fallback name mod_unknown.so is + used.
+ +
-D name=value
+
This option is directly passed through to the compilation command(s). + Use this to add your own defines to the build process.
+ +
-I incdir
+
This option is directly passed through to the compilation command(s). + Use this to add your own include directories to search to the build + process.
+ +
-L libdir
+
This option is directly passed through to the linker command. Use this + to add your own library directories to search to the build process.
+ +
-l libname
+
This option is directly passed through to the linker command. Use this + to add your own libraries to search to the build process.
+ +
-Wc,compiler-flags
+
This option passes compiler-flags as additional flags to + the libtool --mode=compile command. Use this to add local + compiler-specific options.
+ +
-Wl,linker-flags
+
This option passes linker-flags as additional + flags to the libtool --mode=link command. Use this + to add local linker-specific options.
+
+ + +

DSO Installation and Configuration Options

+ +
+
-i
+
This indicates the installation operation and installs one or more + dynamically shared objects into the server's modules + directory.
+ +
-a
+
This activates the module by automatically adding a corresponding + LoadModule line to Apache's + httpd.conf configuration file, or by enabling it if it + already exists.
+ +
-A
+
Same as option -a but the created LoadModule directive is prefixed with a hash + sign (#), i.e., the module is just prepared for + later activation but initially disabled.
+ +
-e
+
This indicates the editing operation, which can be used with the + -a and -A options similarly to the + -i operation to edit Apache's httpd.conf + configuration file without attempting to install the module.
+
+ +
top
+
+

Examples

+

Assume you have an Apache module named mod_foo.c available + which should extend Apache's server functionality. To accomplish this you + first have to compile the C source into a shared object suitable for loading + into the Apache server under runtime via the following command:

+ +

+ $ apxs -c mod_foo.c
+ /path/to/libtool --mode=compile gcc ... -c mod_foo.c
+ /path/to/libtool --mode=link gcc ... -o mod_foo.la mod_foo.slo
+ $ _ +

+ +

Then you have to update the Apache configuration by making sure a + LoadModule directive is present to + load this shared object. To simplify this step apxs provides + an automatic way to install the shared object in its "modules" directory + and updating the httpd.conf file accordingly. This can be + achieved by running:

+ +

+ $ apxs -i -a mod_foo.la
+ /path/to/instdso.sh mod_foo.la /path/to/apache/modules
+ /path/to/libtool --mode=install cp mod_foo.la /path/to/apache/modules + ... + chmod 755 /path/to/apache/modules/mod_foo.so
+ [activating module `foo' in /path/to/apache/conf/httpd.conf]
+ $ _ +

+ +

This way a line named

+ +

+ LoadModule foo_module modules/mod_foo.so +

+ +

is added to the configuration file if still not present. If you want to + have this disabled per default use the -A option, + i.e.

+ +

+ $ apxs -i -A mod_foo.c +

+ +

For a quick test of the apxs mechanism you can create a sample Apache + module template plus a corresponding Makefile via:

+ +

+ $ apxs -g -n foo
+ Creating [DIR] foo
+ Creating [FILE] foo/Makefile
+ Creating [FILE] foo/modules.mk
+ Creating [FILE] foo/mod_foo.c
+ Creating [FILE] foo/.deps
+ $ _ +

+ +

Then you can immediately compile this sample module into a shared object + and load it into the Apache server:

+ +

+ $ cd foo
+ $ make all reload
+ apxs -c mod_foo.c
+ /path/to/libtool --mode=compile gcc ... -c mod_foo.c
+ /path/to/libtool --mode=link gcc ... -o mod_foo.la mod_foo.slo
+ apxs -i -a -n "foo" mod_foo.la
+ /path/to/instdso.sh mod_foo.la /path/to/apache/modules
+ /path/to/libtool --mode=install cp mod_foo.la /path/to/apache/modules + ... + chmod 755 /path/to/apache/modules/mod_foo.so
+ [activating module `foo' in /path/to/apache/conf/httpd.conf]
+ apachectl restart
+ /path/to/apache/sbin/apachectl restart: httpd not running, trying to start
+ [Tue Mar 31 11:27:55 1998] [debug] mod_so.c(303): loaded module foo_module
+ /path/to/apache/sbin/apachectl restart: httpd started
+ $ _ +

+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/apxs.html.ko.euc-kr b/docs/manual/programs/apxs.html.ko.euc-kr new file mode 100644 index 00000000..25d086fe --- /dev/null +++ b/docs/manual/programs/apxs.html.ko.euc-kr @@ -0,0 +1,324 @@ + + + +apxs - APache eXtenSion µµ±¸ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

apxs - APache eXtenSion µµ±¸

+
+

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

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

apxs´Â ¾ÆÆÄÄ¡ ÇÏÀÌÆÛÅؽºÆ® Àü¼Û ÇÁ·ÎÅäÄÝ + (HTTP) ¼­¹öÀÇ È®Àå¸ðµâÀ» ÄÄÆÄÀÏÇÏ°í ¼³Ä¡ÇÏ´Â µµ±¸ÀÌ´Ù. ÀÌ + µµ±¸´Â ¿©·¯ ¼Ò½º¿Í ¿ÀºêÁ§Æ®ÆÄÀÏÀ» °¡Áö°í, + mod_soÀÇ LoadModule Áö½Ã¾î·Î ½ÇÇàÁß¿¡ + ¾ÆÆÄÄ¡ ¼­¹ö·Î ÀоîµéÀÏ ¼ö ÀÖ´Â µ¿Àû°øÀ¯°´Ã¼(DSO)¸¦ ¸¸µç´Ù.

+ +

±×·¡¼­ ÀÌ·± È®Àå¹æ½ÄÀ» »ç¿ëÇÏ·Á¸é Ç÷¡ÆûÀÌ DSO ±â´ÉÀ» + Áö¿øÇÏ°í ¾ÆÆÄÄ¡ httpd ½ÇÇàÆÄÀÏÀ» + mod_so ¸ðµâ°ú °°ÀÌ ÄÄÆÄÀÏÇØ¾ß ÇÑ´Ù. + apxs µµ±¸´Â ÀÌ Á¶°ÇÀÌ ¸¸Á·ÇÏÁö¾ÊÀ¸¸é ½ÇÇàÇÏÁö + ¾Ê´Â´Ù. Á÷Á¢ ¸í·É¾î¸¦ ½ÇÇàÇÏ¿© Á¶°ÇÀÌ ¸¸Á·ÇÏ´ÂÁö ¾Ë¾Æº¼ + ¼ö ÀÖ´Ù

+ +

+ $ httpd -l +

+ +

¸ñ·Ï¿¡ mod_so ¸ðµâÀÌ ³ª¿Í¾ß ÇÑ´Ù. Á¶°ÇÀ» + ¸¸Á·Çϸé apxs µµ±¸·Î DSO ¸ðµâÀ» ¼³Ä¡ÇÏ¿© + ¾ÆÆÄÄ¡¼­¹öÀÇ ±â´ÉÀ» ½±°Ô È®ÀåÇÒ ¼ö ÀÖ´Ù:

+ +

+ $ apxs -i -a -c mod_foo.c
+ gcc -fpic -DSHARED_MODULE -I/path/to/apache/include -c mod_foo.c
+ ld -Bshareable -o mod_foo.so mod_foo.o
+ cp mod_foo.so /path/to/apache/modules/mod_foo.so
+ chmod 755 /path/to/apache/modules/mod_foo.so
+ [activating module `foo' in /path/to/apache/etc/httpd.conf]
+ $ apachectl restart
+ /path/to/apache/sbin/apachectl restart: httpd not running, trying to start
+ [Tue Mar 31 11:27:55 1998] [debug] mod_so.c(303): loaded module foo_module
+ /path/to/apache/sbin/apachectl restart: httpd started
+ $ _ +

+ +

¾Æ±Ô¸ÕÆ® files¿¡´Â C ¼Ò½ºÆÄÀÏ (.c) À̳ª + ¿ÀºêÁ§Æ®ÆÄÀÏ (.o), ¶óÀ̺귯¸®¸ðÀ½ (.a)À» »ç¿ëÇÒ ¼ö ÀÖ´Ù. + apxs µµ±¸´Â È®ÀåÀÚ¸¦ º¸°í ÀÚµ¿À¸·Î C ¼Ò½ºÆÄÀÏÀº + ÄÄÆÄÀÏÇÏ°í, ¿ÀºêÁ§Æ®¿Í ¸ðÀ½ÆÄÀÏÀº ¸µÅ©¿¡¸¸ »ç¿ëÇÑ´Ù. ±×·¯³ª + ÄÄÆÄÀÏÇÑ ¿ÀºêÁ§Æ®¸¦ »ç¿ëÇÏ·Á¸é µ¿ÀûÀ¸·Î ÀоîµéÀÏ ¼ö ÀÖ´Â + °øÀ¯°´Ã¼·Î »ç¿ëÇϱâÀ§ÇØ ¹Ýµå½Ã ¿ÀºêÁ§Æ®¸¦ À§Ä¡µ¶¸³ÄÚµå(PIC, + position independent code)·Î ÄÄÆÄÀÏÇØ¾ß ÇÑ´Ù. GCCÀÇ °æ¿ì + -fpicÀ» »ç¿ëÇÏ¸é µÈ´Ù. ´Ù¸¥ C ÄÄÆÄÀÏ·¯´Â ¼³¸í¼­¸¦ + Âü°íÇϰųª apxs°¡ ¿ÀºêÁ§Æ®ÆÄÀÏÀ» ÄÄÆÄÀÏÇÒ¶§ + »ç¿ëÇÏ´Â ¿É¼ÇÀ» Âü°íÇ϶ó.

+ +

¾ÆÆÄÄ¡ÀÇ DSO Áö¿ø¿¡ ´ëÇÑ ´õ ÀÚ¼¼ÇÑ ³»¿ëÀº + mod_so ¹®¼­¸¦ Âü°íÇϰųª + src/modules/standard/mod_so.c ¼Ò½ºÆÄÀÏÀ» ÀоîºÁ¶ó.

+
+ +
top
+
+

°³¿ä

+

apxs -g + [ -S name=value ] + -n modname

+ +

apxs -q + [ -S name=value ] + query ...

+ +

apxs -c + [ -S name=value ] + [ -o dsofile ] + [ -I incdir ] + [ -D name=value ] + [ -L libdir ] + [ -l libname ] + [ -Wc,compiler-flags ] + [ -Wl,linker-flags ] + files ...

+ +

apxs -i + [ -S name=value ] + [ -n modname ] + [ -a ] + [ -A ] + dso-file ...

+ +

apxs -e + [ -S name=value ] + [ -n modname ] + [ -a ] + [ -A ] + dso-file ...

+
top
+
+

¿É¼Ç

+

°øÅë ¿É¼Ç

+
+
-n modname
+
-i (install)°ú -g (template + generation) ¿É¼ÇÀ» »ç¿ëÇÒ¶§ Á÷Á¢ ¸ðµâ¸íÀ» ÁöÁ¤ÇÑ´Ù. ÀÌ + ¿É¼ÇÀ» »ç¿ëÇÏ¿© ¸ðµâ¸íÀ» Á÷Á¢ ÁöÁ¤ÇÑ´Ù. -g + ¿É¼ÇÀ» »ç¿ëÇÑ´Ù¸é ÀÌ ¿É¼ÇÀ» ¹Ýµå½Ã »ç¿ëÇؾßÇÏ°í, + -i ¿É¼ÇÀ» »ç¿ëÇÑ´Ù¸é apxs µµ±¸´Â + ¼Ò½º³ª (¸¶Áö¸· ½Ãµµ·Î) ÆÄÀϸíÀ» °¡Áö°í À̸§À» ÃßÃøÇÑ´Ù.
+
+ + +

ÁúÀÇ ¿É¼Ç

+
+
-q
+
apxsÀÇ ¼³Á¤°ªÀ» ¾Ë¾Æ³½´Ù. query¿¡´Â + ´ÙÀ½À» »ç¿ëÇÒ ¼ö ÀÖ´Ù: CC, CFLAGS, + CFLAGS_SHLIB, INCLUDEDIR, + LD_SHLIB, LDFLAGS_SHLIB, + LIBEXECDIR, LIBS_SHLIB, + SBINDIR, SYSCONFDIR, TARGET. + +

¼³Á¤À» Á÷Á¢ ¾Ë¾Æ³¾¶§ »ç¿ëÇÑ´Ù.

+

+ INC=-I`apxs -q INCLUDEDIR` +

+ +

¿¹¸¦ µé¾î, ¾ÆÆÄÄ¡ C Çì´õÆÄÀÏÀ» Á÷Á¢ Á¢±ÙÇÑ´Ù¸é + Makefile¿¡¼­ À§¿Í °°ÀÌ »ç¿ëÇÑ´Ù.

+
+ + +

¼³Á¤ ¿É¼Ç

+
+
-S name=value
+
ÀÌ ¿É¼ÇÀº À§¿¡¼­ ¼³¸íÇÑ apxs ¼³Á¤À» º¯°æÇÑ´Ù.
+
+ + +

°ßº»(template) »ý¼º ¿É¼Ç

+
+
-g
+
ÇÏÀ§µð·ºÅ丮 nameÀ» ¸¸µé°í (-n + ¿É¼Ç Âü°í) ±×°÷¿¡ ÆÄÀÏ µÎ°³¸¦ ¸¸µç´Ù: ÇÑ ÆÄÀÏÀº + mod_name.c¶ó´Â °ßº» ¸ðµâ¼Ò½ºÆÄÀÏ·Î, + ÀÚ½ÅÀÇ ¸ðµâÀ» ¸¸µé¶§ °ßº»À¸·Î »ç¿ëÇϰųª apxs ±â´ÉÀ» + ½ÃÇèÇغ¼¶§ »ç¿ëÇÑ´Ù. ´Ù¸¥ ÆÄÀÏÀº ÀÌ ¸ðµâÀ» ½±°Ô ÄÄÆÄÀÏÇÏ°í + ¼³Ä¡ÇϱâÀ§ÇÑ MakefileÀÌ´Ù.
+
+ + +

DSO ÄÄÆÄÀÏ ¿É¼Ç

+
+
-c
+
ÄÄÆÄÀÏÀ» Áö½ÃÇÑ´Ù. ¸ÕÀú files¿¡¼­ C + ¼Ò½ºÆÄÀϵé(.c)À» ¿ÀºêÁ§Æ®ÆÄÀÏ(.o)·Î ÄÄÆÄÀÏÇÏ°í, + filesÀÇ ³ª¸ÓÁö ¿ÀºêÁ§Æ®ÆÄÀϵé(.o°ú .a)°ú + ¸µÅ©ÇÏ¿© µ¿Àû°øÀ¯°´Ã¼ dsofileÀ» ¸¸µç´Ù. + -o ¿É¼ÇÀ» »ç¿ëÇÏÁö¾ÊÀ¸¸é filesÀÇ + ù¹ø° ÆÄÀÏ¸í¿¡¼­ À̸§À» ÃßÃøÇÏ¿© º¸Åë + mod_name.so¸¦ »ç¿ëÇÑ´Ù.
+ +
-o dsofile
+
»ý¼ºÇÒ µ¿Àû°øÀ¯°´Ã¼ ÆÄÀϸíÀ» Á÷Á¢ ÁöÁ¤ÇÑ´Ù. À̸§À» + ÁöÁ¤ÇÏÁö¾Ê°í files ¸ñ·Ï¿¡¼­ À̸§À» ÃßÃøÇÏÁö + ¸øÇÏ¸é ¸¶Áö¸·À¸·Î mod_unknown.so¸¦ À̸§À¸·Î + »ç¿ëÇÑ´Ù.
+ +
-D name=value
+
ÀÌ ¿É¼ÇÀ» ÄÄÆÄÀÏ ¸í·É¾î·Î Á÷Á¢ Àü´ÞÇÑ´Ù. + ÄÄÆÄÀ϶§ ÀÚ½ÅÀÇ defineÀ» Ãß°¡ÇÑ´Ù.
+ +
-I incdir
+
ÀÌ ¿É¼ÇÀ» ÄÄÆÄÀÏ ¸í·É¾î·Î Á÷Á¢ Àü´ÞÇÑ´Ù. + ÄÄÆÄÀ϶§ include¸¦ ãÀ» µð·ºÅ丮¸¦ Ãß°¡ÇÑ´Ù.
+ +
-L libdir
+
ÀÌ ¿É¼ÇÀ» ¸µÄ¿ ¸í·É¾î·Î Á÷Á¢ Àü´ÞÇÑ´Ù. + ÄÄÆÄÀ϶§ ¶óÀ̺귯¸®¸¦ ãÀ» µð·ºÅ丮¸¦ Ãß°¡ÇÑ´Ù.
+ +
-l libname
+
ÀÌ ¿É¼ÇÀ» ¸µÄ¿ ¸í·É¾î·Î Á÷Á¢ Àü´ÞÇÑ´Ù. + ÄÄÆÄÀ϶§ »ç¿ëÇÒ ¶óÀ̺귯¸®¸¦ Ãß°¡ÇÑ´Ù.
+ +
-Wc,compiler-flags
+
ÀÌ ¿É¼ÇÀº Ãß°¡ ¿É¼Ç compiler-flags¸¦ + libtool --mode=compile ¸í·É¾î·Î Àü´ÞÇÑ´Ù. + ÄÄÆÄÀÏ·¯ ƯÀ¯ÀÇ ¿É¼ÇÀ» Ãß°¡ÇÒ¶§ »ç¿ëÇÑ´Ù.
+ +
-Wl,linker-flags
+
ÀÌ ¿É¼ÇÀº Ãß°¡ ¿É¼Ç linker-flags¸¦ + libtool --mode=link ¸í·É¾î·Î Àü´ÞÇÑ´Ù. ¸µÄ¿ + ƯÀ¯ÀÇ ¿É¼ÇÀ» Ãß°¡ÇÒ¶§ »ç¿ëÇÑ´Ù.
+
+ + +

DSO ¼³Ä¡°ú ¼³Á¤ ¿É¼Ç

+ +
+
-i
+
¼³Ä¡¸¦ Áö½ÃÇÑ´Ù. ¿©·¯ µ¿Àû°øÀ¯°´Ã¼¸¦ ¼­¹öÀÇ + modules µð·ºÅ丮¿¡ ¼³Ä¡ÇÑ´Ù.
+ +
-a
+
¾ÆÆÄÄ¡ httpd.conf ¼³Á¤ÆÄÀÏ¿¡ ÀûÀýÇÑ + LoadModule ÁÙÀ» + Ãß°¡Çϰųª ÀÌ¹Ì ÀÖ´Ù¸é È°¼ºÈ­ÇÏ¿© ¸ðµâÀ» »ç¿ëÇϵµ·Ï + ¸¸µç´Ù.
+ +
-A
+
-a¿Í ºñ½ÁÇÏÁö¸¸, LoadModule Áö½Ã¾î ¾Õ¿¡ + ¿ì¹°Á¤ÀÚ(#)¸¦ ºÙÀδÙ. Áï, ÇöÀç´Â + »ç¿ëÇÏÁö¾ÊÁö¸¸ ³ªÁß¿¡ »ç¿ëÇÒ ¼ö ÀÖµµ·Ï ¸ðµâÀ» ÁغñÇÑ´Ù.
+ +
-e
+
ÆíÁýÀ» Áö½ÃÇÑ´Ù. -a ȤÀº -A + ¿É¼Ç°ú °°ÀÌ »ç¿ëÇÒ ¼ö ÀÖÀ¸¸ç, -i ¸í·É°ú + ºñ½ÁÇÏÁö¸¸ ¸ðµâÀ» ¼³Ä¡ÇÏÁö¾Ê°í ¾ÆÆÄÄ¡ + httpd.conf ¼³Á¤ÆÄÀϸ¸ ÆíÁýÇÑ´Ù.
+
+ +
top
+
+

¿¹Á¦

+

¾ÆÆÄÄ¡¼­¹öÀÇ ±â´ÉÀ» È®ÀåÇÏ´Â mod_foo.c¶ó´Â + ¾ÆÆÄÄ¡ ¸ðµâÀÌ ÀÖ´Ù°í °¡Á¤ÇÏÀÚ. ¸ÕÀú ´ÙÀ½ ¸í·É¾î¸¦ »ç¿ëÇÏ¿© + C ¼Ò½º¸¦ ¾ÆÆÄÄ¡ ¼­¹ö°¡ ÀоîµéÀÏ °øÀ¯°´Ã¼·Î ÄÄÆÄÀÏÇÑ´Ù:

+ +

+ $ apxs -c mod_foo.c
+ /path/to/libtool --mode=compile gcc ... -c mod_foo.c
+ /path/to/libtool --mode=link gcc ... -o mod_foo.la mod_foo.slo
+ $ _ +

+ +

±×¸®°í ÀÌ °øÀ¯°´Ã¼¸¦ ÀоîµéÀÌ´Â LoadModule Áö½Ã¾î¸¦ ¾ÆÆÄÄ¡ + ¼³Á¤¿¡ Ãß°¡ÇÑ´Ù. apxs´Â ÀÚµ¿À¸·Î °øÀ¯°´Ã¼¸¦ + "modules" µð·ºÅ丮¿¡ ¼³Ä¡ÇÏ°í httpd.conf ÆÄÀÏÀ» + ¾Ë¸Â°Ô ¼öÁ¤ÇÏ¿© °£´ÜÈ÷ ÀÛ¾÷À» ¸¶Ä£´Ù. ´ÙÀ½ °°ÀÌ ½ÇÇàÇÑ´Ù:

+ +

+ $ apxs -i -a mod_foo.la
+ /path/to/instdso.sh mod_foo.la /path/to/apache/modules
+ /path/to/libtool --mode=install cp mod_foo.la /path/to/apache/modules + ... + chmod 755 /path/to/apache/modules/mod_foo.so
+ [/path/to/apache/conf/httpd.conf¿¡¼­ `foo' ¸ðµâÀ» È°¼ºÈ­ÇÑ´Ù]
+ $ _ +

+ +

±×·¯¸é ´ÙÀ½°ú °°Àº ÁÙÀ»

+ +

+ LoadModule foo_module modules/mod_foo.so +

+ +

¼³Á¤ÆÄÀÏ¿¡ ¾ø´Ù¸é Ãß°¡ÇÑ´Ù. ÀÌ ¼³Á¤À» ±âº»ÀûÀ¸·Î »ç¿ëÇÏÁö + ¾Ê´Â´Ù¸é -A ¿É¼ÇÀ» »ç¿ëÇÑ´Ù. Áï

+ +

+ $ apxs -i -A mod_foo.c +

+ +

apxs¸¦ ½±°Ô »ç¿ëÇÏ·Á°í ´ÙÀ½°ú °°ÀÌ ¾ÆÆÄÄ¡ ¸ðµâ °ßº»°ú + MakefileÀ» ¸¸µé ¼ö ÀÖ´Ù:

+ +

+ $ apxs -g -n foo
+ Creating [DIR] foo
+ Creating [FILE] foo/Makefile
+ Creating [FILE] foo/modules.mk
+ Creating [FILE] foo/mod_foo.c
+ Creating [FILE] foo/.deps
+ $ _ +

+ +

±×·±ÈÄ ¹Ù·Î °ßº» ¸ðµâÀ» °øÀ¯°´Ã¼·Î ÄÄÆÄÀÏÇÏ¿© ¾ÆÆÄÄ¡ + ¼­¹ö°¡ Àеµ·ÏÇÑ´Ù:

+ +

+ $ cd foo
+ $ make all reload
+ apxs -c mod_foo.c
+ /path/to/libtool --mode=compile gcc ... -c mod_foo.c
+ /path/to/libtool --mode=link gcc ... -o mod_foo.la mod_foo.slo
+ apxs -i -a -n "foo" mod_foo.la
+ /path/to/instdso.sh mod_foo.la /path/to/apache/modules
+ /path/to/libtool --mode=install cp mod_foo.la /path/to/apache/modules + ... + chmod 755 /path/to/apache/modules/mod_foo.so
+ [/path/to/apache/conf/httpd.conf¿¡¼­ `foo' ¸ðµâÀ» È°¼ºÈ­ÇÑ´Ù]
+ apachectl restart
+ /path/to/apache/sbin/apachectl restart: httpd not running, trying to start
+ [Tue Mar 31 11:27:55 1998] [debug] mod_so.c(303): loaded module foo_module
+ /path/to/apache/sbin/apachectl restart: httpd started
+ $ _ +

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/configure.html b/docs/manual/programs/configure.html new file mode 100644 index 00000000..9f569079 --- /dev/null +++ b/docs/manual/programs/configure.html @@ -0,0 +1,7 @@ +URI: configure.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: configure.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/configure.html.en b/docs/manual/programs/configure.html.en new file mode 100644 index 00000000..63f66e9a --- /dev/null +++ b/docs/manual/programs/configure.html.en @@ -0,0 +1,937 @@ + + + +configure - Configure the source tree - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

configure - Configure the source tree

+
+

Available Languages:  en  | + ko 

+
+ +

The configure script configures the source tree + for compiling and installing the Apache HTTP Server on your + particular platform. Various options allow the compilation of a + server corresponding to your personal requirements.

+ +

This script, included in the root directory of the source + distribution, is for compilation on Unix and Unix-like systems + only. For other platforms, see the platform documentation.

+
+ +
top
+
+

Synopsis

+

You should call the configure script from within the + root directory of the distribution.

+ +

./configure [OPTION]... + [VAR=VALUE]...

+ +

To assign environment variables (e.g. CC, + CFLAGS ...), specify them as + VAR=VALUE. See below + for descriptions of some of the useful variables.

+
top
+
+

Options

+ + +

Configuration options

+ +

The following options influence the behavior of + configure itself.

+ +
+
-C
+
--config-cache
+
This is an alias for --cache-file=config.cache
+ +
--cache-file=FILE
+
The test results will be cached in file FILE. + This option is disabled by default.
+ +
-h
+
--help [short|recursive]
+
Output the help and exit. With the argument short only + options specific to this package will displayed. The argument + recursive displays the short help of all the included + packages.
+ +
-n
+
--no-create
+
The configure script is run normally but does + not create output files. This is useful to check the test results + before generating makefiles for compilation.
+ +
-q
+
--quiet
+
Do not print checking ... messages during the + configure process.
+ +
--srcdir=DIR
+
Defines directory DIR to be the source file directory. + Default is the directory, where configure is located, or the parent + directory ...
+ +
--silent
+
Same as --quiet
+ +
-V
+
--version
+
Display copyright information and exit.
+
+ + +

Installation + directories

+ +

These options define the installation directory. The installation + tree depends on the selected layout.

+ +
+
--prefix=PREFIX
+
Install architecture-independent files in PREFIX. + By default the installation directory is set to + /usr/local/apache2.
+ +
--exec-prefix=EPREFIX
+
Install architecture-dependent files in EPREFIX. + By default the installation directory is set to the + PREFIX directory.
+
+ +

By default, make install will install all the files in + /usr/local/apache2/bin, /usr/local/apache2/lib + etc. You can specify an installation prefix other than + /usr/local/apache2 using --prefix, + for instance --prefix=$HOME.

+ +

Define a directory layout

+
+
--enable-layout=LAYOUT
+
Configure the source code and build scripts to assume an + installation tree based on the layout LAYOUT. This allows + you to separately specify the locations for each type of file within + the Apache HTTP Server installation. The config.layout + file contains several example configurations, and you can also create + your own custom configuration following the examples. The different + layouts in this file are grouped into <Layout + FOO>...</Layout> sections and referred to by name as + in FOO. The default layout is Apache.
+
+ + +

Fine tuning of the installation + directories

+ +

For better control of the installation directories, use the options + below. Please note that the directory defaults are set by + autoconf and be overwritten by the corresponding layout + setting.

+ +
+ +
--bindir=DIR
+
Install user executables in DIR. The user executables + are supporting programs like htpasswd, + dbmmanage, etc. which are useful for site + administrators. By default DIR is set to + EPREFIX/bin.
+ +
--datadir=DIR
+
Install read-only architecture-independent data in DIR. + By default datadir is set to + PREFIX/share. This option is offered by + autoconf and currently unused.
+ +
--includedir=DIR
+
Install C header files in DIR. By default + includedir is set to + EPREFIX/include.
+ +
--infodir=DIR
+
Install info documentation in DIR. + By default infodir is set to + PREFIX/info. This option is currently + unused.
+ +
--libdir=DIR
+
Install object code libraries in DIR. By default + libdir is set to + EPREFIX/lib.
+ +
--libexecdir=DIR
+
Install the program executables (i.e., shared modules) in + DIR. By default libexecdir is set to + EPREFIX/libexec.
+ +
--localstatedir=DIR
+
Install modifiable single-machine data in DIR. + By default localstatedir is set to + PREFIX/var. This option is offered by + autoconf and currently unused.
+ +
--mandir=DIR
+
Install the man documentation in DIR. By default + mandir is set to + EPREFIX/man.
+ +
--oldincludedir=DIR
+
Install C header files for non-gcc in DIR. + By default oldincludedir is set to + /usr/include. This option is offered by + autoconf and currently unused.
+ +
--sbindir=DIR
+
Install the system administrator executables in DIR. + Those are server programs like httpd, + apachectl, suexec, etc. which + are neccessary to run the Apache HTTP Server. By default + sbindir is set to + EPREFIX/sbin.
+ +
--sharedstatedir=DIR
+
Install modifiable architecture-independent data in DIR. + By default sharedstatedir is set to + PREFIX/com. This option is offered by + autoconf and currently unused.
+ +
--sysconfdir=DIR
+
Install read-only single-machine data like the server configuration + files httpd.conf, mime.types, etc. in + DIR. By default sysconfdir is set to + PREFIX/etc.
+
+ + + +

System types

+ +

These options are used to cross-compile the Apache HTTP Server to run on + another system. In normal cases, when building and running the server on + the same system, these options are not used.

+ +
+
--build=BUILD
+
Defines the system type of the system on which the tools are being + built. It defaults to the result of the script + config.guess.
+ +
--host=HOST
+
Defines the system type of the system on which the server will run. + HOST defaults to BUILD.
+ +
--target=TARGET
+
Configure for building compilers for the system type + TARGET. It defaults to HOST. This option is + offered by autoconf and not necessary for the Apache HTTP + Server.
+
+ + +

Optional Features

+ +

These options are used to fine tune the features your HTTP server will + have.

+ +

General syntax

+

Generally you can use the following syntax to enable or disable a + feature:

+ +
+
--disable-FEATURE
+
Do not include FEATURE. This is the same as + --enable-FEATURE=no.
+ +
--enable-FEATURE[=ARG]
+
Include FEATURE. The default value for ARG + is yes.
+ +
--enable-MODULE=shared
+
The corresponding module will be build as DSO module.
+ +
--enable-MODULE=static
+
By default enabled modules are linked statically. You can force + this explicitly.
+
+ +

Note

+ configure will not complain about + --enable-foo even if foo doesn't + exist, so you need to type carefully. +
+ + + +

Modules enabled by default

+

Some modules are compiled by default and have to be disabled + explicitly. Use the following options to remove discrete modules from + the compilation process.

+ +
+
--disable-actions
+
Disable action triggering on requests, which is provided by + mod_actions.
+ +
--disable-alias
+
Disable the mapping of requests to different parts of the + filesystem, which is provided by mod_alias.
+ +
--disable-asis
+
Disable support for as-is filetypes, which is provided by + mod_asis.
+ +
--disable-auth
+
Disable user-based access control provided by + mod_auth. This module provides for HTTP Basic + Authentication, where the usernames and passwords are stored in + plain text files.
+ +
--disable-autoindex
+
Disable the directory listing functionality provided by + mod_autoindex.
+ +
--disable-access
+
Disable host-based access control provided by + mod_access.
+ +
--disable-cgi
+
mod_cgi, which provides support for CGI scripts, + is enabled by default when using a non-threaded MPM. Use this + option to disable CGI support.
+ +
--disable-cgid
+
When using the threaded MPMs worker + support for CGI scripts is provided by + mod_cgid by default. To disable CGI support use + this option.
+ +
--disable-charset-lite
+
Disable character set translation provided by + mod_charset_lite. This module will be installed by + default only on EBCDIC systems.
+ +
--disable-dir
+
Disable directory request handling provided by + mod_dir.
+ +
--disable-env
+
Enable setting and clearing of environment variables, which is + provided by mod_env.
+ + +
--disable-http
+
Disable the HTTP protocol handling. The http + module is a basic one, enabling the server to function as an + HTTP server. It is only useful to disable it if you want to use + another protocol module instead. Don't disable this + module unless you are really sure what you are doing. +
+ Note: This module will always be linked statically.
+ +
--disable-imagemap
+
Disable support for server based imagemaps, which provided by + mod_imagemap.
+ +
--disable-include
+
Disable Server Side Includes provided by + mod_include.
+ +
--disable-log-config
+
Disable the logging configuration provided by + mod_log_config. You won't be able to log requests + to the server without this module.
+ +
--disable-mime
+
mod_mime associates the requested + filename's extensions with the file's behavior and content + (mime-type, language, character set and + encoding). Disabling this module is normally not recommended.
+ +
--disable-negotiation
+
Disable content negotiation provided by + mod_negotiation.
+ +
--disable-setenvif
+
Disable support for basing environment variables on headers, + which is provided by mod_setenvif.
+ +
--disable-status
+
Enable the process/thread monitoring, which is provided by + mod_status.
+ +
--disable-userdir
+
Disable the mapping of requests to user-specific directories, + which is provided by mod_userdir.
+
+ + +

Modules, disabled by default

+

Some modules are compiled by default and have to be enabled + explicitly or by using the keywords most or + all (see --enable-mods-shared below for + further explanation) to be available. Therefore use the options + below.

+ +
+
--enable-auth-anon
+
Enable anonymous user access provided by + mod_auth_anon.
+ +
--enable-auth-dbm
+
mod_auth_dbm provides for HTTP Basic + Authentication, where the usernames and passwords are stored in DBM + type database files. Use this option to enable the module.
+ +
--enable-auth-digest
+
Enable RFC2617 Digest authentication provided by + mod_auth_digest. This module uses plain text files + to store the credentials.
+ +
--enable-authnz-ldap
+
Enable LDAP based authentication provided by + mod_authnz_ldap.
+ +
--enable-cache
+
Enable dynamic file caching provided by + mod_cache. This experimental module may be + interesting for servers with high load or caching proxy servers. At + least one storage management module (e.g. + mod_disk_cache or mod_mem_cache) + is also necessary.
+ +
--enable-cern-meta
+
Enable the CERN-type meta files support provided by + mod_cern_meta.
+ +
--enable-charset-lite
+
Enable character set translation provided by + mod_charset_lite. This module will be installed by + default only on EBCDIC systems. On other systems, you have to enable + it.
+ +
--enable-dav
+
Enable the WebDAV protocol handling provided by + mod_dav. Support for filesystem resources is + provided by the separate module mod_dav_fs. This + module is also automatically enabled with + --enable-dav.
+ Note: mod_dav can only be used together with the + http protocol module.
+ +
--enable-dav-fs
+
Enable DAV support for filesystem resources, which is provided by + mod_dav_fs. This module is a provider for the + mod_dav module, so you should also use + --enable-dav.
+ +
--enable-dav-lock
+
Enable mod_dav_lock which provides generic DAV + locking support for backend modules. This module needs at least + mod_dav to function, so you should also use + --enable-dav.
+ +
--enable-deflate
+
Enable deflate transfer encoding provided by + mod_deflate.
+ +
--enable-disk-cache
+
Enable disk caching provided by + mod_disk_cache.
+ +
--enable-expires
+
Enable Expires header control provided by + mod_expires.
+ +
--enable-ext-filter
+
Enable the external filter support provided by + mod_ext_filter.
+ +
--enable-file-cache
+
Enable the file cache provided by + mod_file_cache.
+ +
--enable-headers
+
Enable control of HTTP headers provided by + mod_headers.
+ +
--enable-info
+
Enable the server information provided by + mod_info.
+ +
--enable-ldap
+
Enable LDAP caching and connection pooling services provided by + mod_ldap.
+ +
--enable-logio
+
Enable logging of input and output bytes including headers provided + by mod_logio.
+ +
--enable-mem-cache
+
Enable memory caching provided by + mod_mem_cache.
+ +
--enable-mime-magic
+
Enable + automatical determining of MIME + types, which is provided by + mod_mime_magic.
+ +
--enable-isapi
+
Enable the isapi extension support provided by + mod_isapi.
+ +
--enable-proxy
+
Enable the proxy/gateway functionality provided by + mod_proxy. The proxying capabilities for + AJP13, CONNECT, FTP, + HTTP and the balancer are provided by the separate + modules mod_proxy_ajp, + mod_proxy_connect, mod_proxy_ftp, + mod_proxy_http and + mod_proxy_balancer. + These five modules are also automatically enabled with + --enable-proxy.
+ +
--enable-proxy-ajp
+
Enable proxy support for AJP13 (Apache JServ Protocol 1.3) + request handling, which is provided by mod_proxy_ajp. + This module is an extension for the mod_proxy module, + so you should also use --enable-proxy.
+ +
--enable-proxy-balancer
+
Enable load balancing support for the AJP13, + FTP and HTTP protocols, which is provided by + mod_proxy_balancer. This module is an extension for the + mod_proxy module, so you should also use + --enable-proxy.
+ +
--enable-proxy-connect
+
Enable proxy support for CONNECT request handling, + which is provided by mod_proxy_connect. This module + is an extension for the mod_proxy module, so you + should also use --enable-proxy.
+ +
--enable-proxy-ftp
+
Enable proxy support for FTP requests, which is + provided by mod_proxy_ftp. This module + is an extension for the mod_proxy module, so you + should also use --enable-proxy.
+ +
--enable-proxy-http
+
Enable proxy support for HTTP requests, which is + provided by mod_proxy_http. This module + is an extension for the mod_proxy module, so you + should also use --enable-proxy.
+ +
--enable-rewrite
+
Enable rule based URL manipulation provided by + mod_rewrite.
+ +
--enable-so
+
Enable DSO capability provided by mod_so. This + module will be automatically enabled if you use the + --enable-mods-shared option.
+ +
--enable-speling
+
Enable the functionality to correct common URL misspellings, which + is provided by mod_speling.
+ +
--enable-ssl
+
Enable support for SSL/TLS provided by + mod_ssl.
+ +
--enable-unique-id
+
Enable the generation of per-request unique ids, which is provided + by mod_unique_id.
+ +
--enable-usertrack
+
Enable user-session tracking provided by + mod_usertrack.
+ +
--enable-vhost-alias
+
Enable mass virtual hosting provided by + mod_vhost_alias.
+
+ + +

Modules for developers

+

The following modules are useful only for developers and testing + purposes and are disabled by default. Use the following options to + enable them. If you are not sure whether you need one of these + modules, omit them.

+ +
+ +
--enable-bucketeer
+
Enable the manipulation filter for buckets, which is provided by + mod_bucketeer.
+ + +
--enable-case-filter
+
Enable the example uppercase conversion output filter support of + mod_case_filter.
+ + +
--enable-case-filter-in
+
Enable the example uppercase conversion input filter support of + mod_case_filter_in.
+ +
--enable-echo
+
Enable the ECHO server provided by + mod_echo.
+ +
--enable-example
+
Enable the example and demo module + mod_example.
+ + +
--enable-optional-fn-export
+
Enable the example for an optional function exporter, which is + provided by mod_optional_fn_export.
+ + +
--enable-optional-fn-import
+
Enable the example for an optional function importer, which is + provided by mod_optional_fn_import.
+ + +
--enable-optional-hook-export
+
Enable the example for an optional hook exporter, which is provided + by mod_optional_hook_export.
+ + +
--enable-optional-hook-import
+
Enable the example optional hook importer, which is provided by + mod_optional_hook_import.
+
+ + +

MPMs and third-party modules

+

To add the necessary Multi Processing Module and additional third-party + modules use the following options:

+ +
+
--with-module=module-type:module-file[, + module-type:module-file]
+

Add one or more third-party modules to the list of statically linked + modules. The module source file module-file + will be searched in the modules/module-type + subdirectory of your Apache HTTP server source tree. If it is not found + there configure is considering module-file to be + an absolute file path and tries to copy the source file into the + module-type subdirectory. If the subdirectory doesn't + exist it will be created and populated with a standard + Makefile.in.

+

This option is useful to add small external modules consisting of + one source file. For more complex modules you should read the + vendor's documentation.

+

Note

+ If you want to build a DSO module instead of a statically linked + use apxs.
+
+ +
--with-mpm=MPM
+
Choose the process model for your server. You have to select + exactly one Multi-Processing Module. + Otherwise the default MPM for + your operating system will be taken. Possible MPMs are + beos, + mpmt_os2, + prefork, and + worker.
+
+ + +

Cumulative and other options

+
+
--enable-maintainer-mode
+
Turn on debugging and compile time warnings.
+ +
--enable-mods-shared=MODULE-LIST
+
+

Defines a list of modules to be enabled and build as dynamic + shared modules. This mean, these module have to be loaded + dynamically by using the LoadModule directive.

+

MODULE-LIST is a space separated list of modulenames + enclosed by quotation marks. The module names are given without the + preceding mod_. For example:

+

+ --enable-mods-shared='headers rewrite dav' +

+

Additionally you can use the special keywords all and + most. For example,

+

+ --enable-mods-shared=most +

+

will compile most modules and build them as DSO modules. +

+
+ +
--enable-modules=MODULE-LIST
+
This option behaves similar to --enable-mods-shared, + but will link the given modules statically. This mean, these modules + will always be present while running httpd. They need + not be loaded with LoadModule.
+ +
--enable-v4-mapped
+
Allow IPv6 sockets to handle IPv4 connections.
+ +
--with-port=PORT
+
This defines the port on which httpd will listen. + This port number is used when generating the configuration file + httpd.conf. The default is 80.
+ +
--with-program-name
+
Define an alternative executable name. The default is + httpd.
+
+ + + +

Optional packages

+

These options are used to define optional packages.

+ +

General syntax

+

Generally you can use the following syntax to define an optional + package:

+ +
+
--with-PACKAGE[=ARG]
+
Use the package PACKAGE. The default value for + ARG isyes.
+ +
--without-PACKAGE
+
Do not use the package PACKAGE. This is the same as + --with-PACKAGE=no. This option is provided by + autoconf but not very useful for the Apache HTTP + Server.
+
+ + + + +

Specific packages

+
+
--with-apr=DIR|FILE
+
The Apache Portable Runtime (APR) + is part of the httpd + source distribution and will automatically be build together with the + HTTP server. If you want to use an already installed APR instead you + have to tell configure the path to the + apr-config script. You may set the absolute path and name + or the directory to the installed APR. apr-config must + exists within this directory or the subdirectory + bin.
+ +
--with-apr-util=DIR|FILE
+
The Apache Portable Runtime Utilities (APU) are part of the + httpd source distribution and will automatically be build + together with the HTTP server. If you want to use an already installed + APU instead you have to tell configure the path to the + apu-config script. You may set the absolute path and name + or the directory to the installed APU. apu-config must + exists within this directory or the subdirectory + bin.
+ +
--with-ssl=DIR
+
If mod_ssl has been enabled configure + searches for an installed OpenSSL. You can set the directory path + to the SSL/TLS toolkit instead.
+ +
--with-z=DIR
+
configure searches automatically for an installed + zlib library if your source configuration requires one + (e.g., when mod_deflate is enabled). You can set the + directory path to the compression library instead.
+
+ +

Several features of the Apache HTTP Server, including + mod_authn_dbm and mod_rewrite's DBM + RewriteMap use simple + key/value databases for quick lookups of information. SDBM is included + in the APU, so this database is always available. If you would like to + use other database types, use the following options to enable + them:

+ +
+
--with-gdbm[=path]
+
If no path is specified, configure will + search for the include files and libraries of a GNU DBM + installation in the usual search paths. An explicit + path will cause configure to look in + path/lib and + path/include for the relevant files. + Finally, the path may specify specific include and + library paths separated by a colon.
+ +
--with-ndbm[=path]
+
Like --with-gdbm, bur searches for a New DBM + installation.
+ +
--with-berkeley-db[=path]
+
Like --with-gdbm, but searches for a Berkeley DB + installation.
+
+ +

Note

+

The DBM options are provided by the APU and passed through to its + configuration script. They are useless when using an already + installed APU defined by --with-apr-util.

+

You may use more then one DBM implementation together with your + HTTP server. The appropriated DBM type will be configured within + the runtime configuration at each time.

+
+ + + +

Options for support programs

+
+
--enable-static-support
+
Build a statically linked version of the support binaries. This + means, a stand-alone executable will be built with all the necessary + libraries integrated. Otherwise the support binaries are linked + dynamically by default.
+ +
--enable-suexec
+
Use this option to enable suexec, which allows you to set + uid and gid for spawned processes. Do not use this + option unless you understand all the security implications of + running a suid binary on your server. Further options + to configure suexec are described below.
+ +

It is possible to create a statically linked binary of a single + support program by using the following options:

+ +
+
--enable-static-ab
+
Build a statically linked version of ab.
+ + +
--enable-static-checkgid
+
Build a statically linked version of checkgid.
+ +
--enable-static-htdbm
+
Build a statically linked version of htdbm.
+ +
--enable-static-htdigest
+
Build a statically linked version of htdigest.
+ +
--enable-static-htpasswd
+
Build a statically linked version of htpasswd.
+ +
--enable-static-logresolve
+
Build a statically linked version of logresolve.
+ +
--enable-static-rotatelogs
+
Build a statically linked version of rotatelogs.
+
+ +

suexec configuration options

+

The following options are used to fine tune the behavior of suexec. See Configuring and installing suEXEC + for further information.

+ +
+
--with-suexec-bin
+
This defines the path to suexec binary. Default is + --sbindir (see Fine + tuning of installation directories).
+ +
--with-suexec-caller
+
This defines the user allowed to call suexec. + It should be the same as the user under which httpd + normally runs.
+ +
--with-suexec-docroot
+
This defines the directory tree under which suexec access is allowed for executables. Default value is + --datadir/htdocs.
+ +
--with-suexec-gidmin
+
Define this as the lowest GID allowed to be a target user for + suexec. The default value is 100.
+ +
--with-suexec-logfile
+
This defines the filename of the suexec logfile. + By default the logfile is named suexec_log and located in + --logfiledir.
+ +
--with-suexec-safepath
+
Define the value of the environment variable PATH to + be set for processes started by suexec. Default + value is /usr/local/bin:/usr/bin:/bin.
+ +
--with-suexec-userdir
+
This defines the subdirectory under the user's directory that + contains all executables for which suexec access + is allowed. This setting is necessary when you want to use + suexec together with user-specific directories (as + provided by mod_userdir). The default is + public_html.
+ +
--with-suexec-uidmin
+
Define this as the lowest UID allowed to be a target user for + suexec. The default value is 100.
+ +
--with-suexec-umask
+
Set umask for processes started by + suexec. It defaults to your system settings.
+
+ + +
top
+
+

Environment variables

+

There are some useful environment variables to override the choices made by + configure or to help it to find libraries and programs with + nonstandard names or locations.

+ + +
+
CC
+
Define the C compiler command to be used for compilation.
+ +
CFLAGS
+
Set C compiler flags you want to use for compilation.
+ +
CPP
+
Define the C preprocessor command to be used.
+ +
CPPFLAGS
+
Set C/C++ preprocessor flags, e.g. -Iincludedir + if you have headers in a nonstandard directory includedir.
+ +
LDFLAGS
+
Set linker flags, e.g. -Llibdir if you have + libraries in a nonstandard directory libdir.
+
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/configure.html.ko.euc-kr b/docs/manual/programs/configure.html.ko.euc-kr new file mode 100644 index 00000000..faf6aeb4 --- /dev/null +++ b/docs/manual/programs/configure.html.ko.euc-kr @@ -0,0 +1,930 @@ + + + +configure - ¼Ò½º Æ®¸®¸¦ ±¸¼ºÇÑ´Ù - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

configure - ¼Ò½º Æ®¸®¸¦ ±¸¼ºÇÑ´Ù

+
+

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

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

configure ½ºÅ©¸³Æ®´Â ƯÁ¤ Ç÷¡Æû¿¡¼­ ¾ÆÆÄÄ¡ + À¥¼­¹ö¸¦ ÄÄÆÄÀÏÇÏ°í ¼³Ä¡ÇϱâÀ§ÇØ ¼Ò½º Æ®¸®¸¦ ±¸¼ºÇÑ´Ù. ¿©·¯ + ¿É¼ÇÀ» »ç¿ëÇÏ¿© ¿øÇÏ´Â ¿ä±¸Á¶°Ç¿¡ ¸Â°Ô ¼­¹ö¸¦ ÄÄÆÄÀÏÇÒ ¼ö + ÀÖ´Ù.

+ +

¼Ò½º ¹èÆ÷º»ÀÇ ÃÖ»óÀ§ µð·ºÅ丮¿¡ ÀÖ´Â ÀÌ ½ºÅ©¸³Æ®´Â À¯´Ð½º¿Í + À¯´Ð½º·ù ½Ã½ºÅÛ¿¡¼­¸¸ »ç¿ëÇÑ´Ù. ´Ù¸¥ Ç÷¡ÆûÀ» »ç¿ëÇÑ´Ù¸é + Ç÷¡Æû ¹®¼­¸¦ Âü°íÇ϶ó.

+
+ +
top
+
+

°³¿ä

+

configure ½ºÅ©¸³Æ®´Â ¹èÆ÷º»ÀÇ ÃÖ»óÀ§ + µð·ºÅ丮¿¡¼­ ½ÇÇàÇØ¾ß ÇÑ´Ù.

+ +

./configure [OPTION]... + [VAR=VALUE]...

+ +

ȯ°æº¯¼ö¸¦ (¿¹¸¦ µé¾î, CC, CFLAGS, + ...) ÁöÁ¤ÇÏ·Á¸é, VAR=VALUE¿Í + °°ÀÌ Áö½ÃÇÑ´Ù. ¾Æ·¡¿¡¼­ À¯¿ëÇÑ È¯°æº¯¼öµéÀ» + ¼³¸íÇÑ´Ù.

+
top
+
+

¿É¼Ç

+ + +

±¸¼º ¿É¼Ç

+ +

ÀÌ ¿É¼ÇµéÀº configure ÀÚü Çൿ¿¡ ¿µÇâÀ» + ÁØ´Ù.

+ +
+
-C
+
--config-cache
+
--cache-file=config.cache¿Í °°´Ù.
+ +
--cache-file=FILE
+
°Ë»ç °á°ú¸¦ FILE ÆÄÀÏ¿¡ ij½ÌÇÑ´Ù. + ±âº»°ªÀº °Ë»ç °á°ú¸¦ ±â·ÏÇÏÁö ¾Ê´Â´Ù.
+ +
-h
+
--help [short|recursive]
+
µµ¿ò¸»À» Ãâ·ÂÇÏ°í Á¾·áÇÑ´Ù. short ¾Æ±Ô¸ÕÆ®´Â + ÀÌ ÆÐÅ°Áö ƯÀ¯ÀÇ ¿É¼Ç¸¸À» Ãâ·ÂÇÑ´Ù. recursive + ¾Æ±Ô¸ÕÆ®´Â Æ÷ÇÔµÈ ¸ðµç ÆÐÅ°Áö¿¡ ´ëÇÑ ÂªÀº µµ¿ò¸»À» + º¸¿©ÁØ´Ù.
+ +
-n
+
--no-create
+
configure ½ºÅ©¸³Æ®¸¦ Á¤»óÀûÀ¸·Î ½ÇÇàÇÏÁö¸¸, + Ãâ·ÂÆÄÀÏÀ» ¸¸µéÁö ¾Ê´Â´Ù. ÀÌ ¿É¼ÇÀº ÄÄÆÄÀÏÀ» À§ÇÑ makefileÀ» + ¸¸µé±â ÀÌÀü¿¡ °Ë»ç °á°ú¸¦ È®ÀÎÇغ¼¶§ À¯¿ëÇÏ´Ù.
+ +
-q
+
--quiet
+
½ÇÇàÁß¿¡ checking ... ¹®±¸¸¦ Ãâ·ÂÇÏÁö + ¾Ê´Â´Ù.
+ +
--srcdir=DIR
+
DIR µð·ºÅ丮¸¦ ¼Ò½ºÆÄÀÏ µð·ºÅ丮·Î ÁöÁ¤ÇÑ´Ù. + ±âº»°ªÀº configure°¡ ÀÖ´Â µð·ºÅ丮 ȤÀº »óÀ§µð·ºÅ丮 + ..ÀÌ´Ù.
+ +
--silent
+
--quiet¿Í °°´Ù.
+ +
-V
+
--version
+
ÀúÀÛ±Ç Á¤º¸¸¦ Ãâ·ÂÇÏ°í Á¾·áÇÑ´Ù.
+
+ + +

¼³Ä¡ µð·ºÅ丮

+ +

ÀÌ ¿É¼ÇµéÀº ¼³Ä¡ µð·ºÅ丮¸¦ ÁöÁ¤ÇÑ´Ù. ¼³Ä¡ À§Ä¡´Â + ¼±ÅÃÇÑ ±¸Á¶(layout)¿¡ µû¶ó ´Ù¸£´Ù.

+ +
+
--prefix=PREFIX
+
¾ÆÅ°ÅØÃÄ¿¡ µ¶¸³ÀûÀÎ ÆÄÀÏÀ» PREFIX¿¡ ¼³Ä¡ÇÑ´Ù. + ±âº»°ªÀº /usr/local/apache2ÀÌ´Ù.
+ +
--exec-prefix=EPREFIX
+
¾ÆÅ°ÅØÃÄ¿¡ ÀÇÁ¸ÀûÀÎ ÆÄÀÏÀ» EPREFIX¿¡ ¼³Ä¡ÇÑ´Ù. + ±âº»°ªÀº PREFIX µð·ºÅ丮ÀÌ´Ù.
+
+ +

±âº»ÀûÀ¸·Î make installÀº + /usr/local/apache2/bin, + /usr/local/apache2/lib¿Í °°Àº À§Ä¡¿¡ ¸ðµç + ÆÄÀÏÀ» ¼³Ä¡ÇÑ´Ù. --prefix=$HOME°ú °°ÀÌ + --prefix ¿É¼ÇÀ» »ç¿ëÇÏ¿© + /usr/local/apache2 ÀÌ¿ÜÀÇ ¼³Ä¡ »óÀ§µð·ºÅ丮¸¦ + ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +

µð·ºÅ丮 ±¸Á¶ ÁöÁ¤

+
+
--enable-layout=LAYOUT
+
¼³Ä¡ À§Ä¡¸¦ LAYOUT ±¸Á¶¿¡ µû¸£µµ·Ï + ¼Ò½ºÄÚµå¿Í ÄÄÆÄÀÏ ½ºÅ©¸³Æ®¸¦ ±¸¼ºÇÑ´Ù. ±¸Á¶¸¦ »ç¿ëÇϸé + ÆÄÀÏ Á¾·ù¿¡ µû¶ó ¼³Ä¡ À§Ä¡¸¦ µû·Î ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù. + config.layout ÆÄÀÏ¿¡ ¿©·¯ ¼³Á¤ ¿¹°¡ ÀÖ°í, + À̸¦ Âü°íÇÏ¿© Á÷Á¢ ¼³Á¤À» ¸¸µé ¼öµµ ÀÖ´Ù. ÆÄÀÏ¿¡¼­ + °¢ ±¸Á¶´Â <Layout + FOO>...</Layout>·Î ±¸ºÐµÇ¸ç, ÀÌ + ºÎºÐÀº FOO¶ó´Â À̸§ÀÇ ±¸Á¶¸¦ ³ªÅ¸³½´Ù. + ±¸Á¶ÀÇ ±âº»°ªÀº ApacheÀÌ´Ù.
+
+ + +

¼³Ä¡ µð·ºÅ丮ÀÇ + ÀÚ¼¼ÇÑ Á¶Á¤

+ +

¼³Ä¡ µð·ºÅ丮¸¦ ´õ ¼öÁ¤ÇÑ´Ù¸é ¾Æ·¡ ¿É¼ÇÀ» »ç¿ëÇÑ´Ù. + °¢ µð·ºÅ丮ÀÇ ±âº»°ªÀº autoconf°¡ ÁöÁ¤Çϸç, + ¼±ÅÃÇÑ ±¸Á¶¿¡ µû¶ó ´Ù¸§À» ÁÖÀÇÇ϶ó.

+ +
+ +
--bindir=DIR
+
»ç¿ëÀÚ ½ÇÇàÆÄÀÏÀ» DIR¿¡ ¼³Ä¡ÇÑ´Ù. »ç¿ëÀÚ + ½ÇÇàÆÄÀÏ¿¡´Â »çÀÌÆ® °ü¸®ÀÚ¿¡°Ô À¯¿ëÇÑ + htpasswd¿Í dbmmanage °°Àº + Áö¿ø ÇÁ·Î±×·¥µµ Æ÷ÇԵȴÙ. DIRÀÇ ±âº»°ªÀº + EPREFIX/binÀÌ´Ù.
+ +
--datadir=DIR
+
¾ÆÅ°ÅØÃÄ µ¶¸³ÀûÀÎ ÀбâÀü¿ë ÀڷḦ DIR¿¡ + ¼³Ä¡ÇÑ´Ù. datadirÀÇ ±âº»°ªÀº + PREFIX/shareÀÌ´Ù. + autoconf¿¡ ÀÌ ¿É¼ÇÀÌ ÀÖÁö¸¸ ÇöÀç »ç¿ëÇÏÁö + ¾Ê´Â´Ù.
+ +
--includedir=DIR
+
C Çì´õÆÄÀÏÀ» DIR¿¡ ¼³Ä¡ÇÑ´Ù. + includedirÀÇ ±âº»°ªÀº + EPREFIX/includeÀÌ´Ù.
+ +
--infodir=DIR
+
info ¹®¼­¸¦ DIR¿¡ ¼³Ä¡ÇÑ´Ù. + infodirÀÇ ±âº»°ªÀº + PREFIX/infoÀÌ´Ù. ÇöÀç ÀÌ ¿É¼ÇÀº + »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--libdir=DIR
+
¿ÀºêÁ§Æ®ÄÚµå ¶óÀ̺귯¸®¸¦ DIR¿¡ ¼³Ä¡ÇÑ´Ù. + libdirÀÇ ±âº»°ªÀº + EPREFIX/libÀÌ´Ù.
+ +
--libexecdir=DIR
+
ÇÁ·Î±×·¥ ½ÇÇàÆÄÀÏÀ» (Áï, °øÀ¯¸ðµâ) DIR¿¡ + ¼³Ä¡ÇÑ´Ù. libexecdirÀÇ ±âº»°ªÀº + EPREFIX/libexecÀÌ´Ù.
+ +
--localstatedir=DIR
+
º¯°æµÇ´Â ¸Ó½®º° Á¤º¸¸¦ DIR¿¡ ¼³Ä¡ÇÑ´Ù. + localstatedirÀÇ ±âº»°ªÀº + PREFIX/varÀÌ´Ù. + autoconf¿¡ ÀÌ ¿É¼ÇÀÌ ÀÖÁö¸¸ ÇöÀç »ç¿ëÇÏÁö + ¾Ê´Â´Ù.
+ +
--mandir=DIR
+
man ¹®¼­¸¦ DIR¿¡ ¼³Ä¡ÇÑ´Ù. + mandirÀÇ ±âº»°ªÀº + EPREFIX/manÀÌ´Ù.
+ +
--oldincludedir=DIR
+
gcc°¡ ¾Æ´Ñ ÄÄÆÄÀÏ·¯¸¦ À§ÇÑ C Çì´õÆÄÀÏÀ» DIR¿¡ + ¼³Ä¡ÇÑ´Ù. oldincludedirÀÇ ±âº»°ªÀº + /usr/includeÀÌ´Ù. autoconf¿¡ + ÀÌ ¿É¼ÇÀÌ ÀÖÁö¸¸ ÇöÀç »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--sbindir=DIR
+
½Ã½ºÅÛ °ü¸®ÀÚ¿ë ½ÇÇàÆÄÀÏÀ» DIR¿¡ ¼³Ä¡ÇÑ´Ù. + ½Ã½ºÅÛ °ü¸®ÀÚ¿ë ½ÇÇàÆÄÀÏÀ̶õ ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ½ÇÇàÇϴµ¥ + ÇÊ¿äÇÑ httpd, apachectl, + suexec µî ¼­¹ö ÇÁ·Î±×·¥À» ¸»ÇÑ´Ù. + sbindirÀÇ ±âº»°ªÀº + EPREFIX/sbinÀÌ´Ù.
+ +
--sharedstatedir=DIR
+
º¯°æµÇ´Â ¾ÆÅ°ÅØÃÄ µ¶¸³ÀûÀÎ ÀڷḦ DIR¿¡ + ¼³Ä¡ÇÑ´Ù. sharedstatedirÀÇ ±âº»°ªÀº + PREFIX/comÀÌ´Ù. + autoconf¿¡ ÀÌ ¿É¼ÇÀÌ ÀÖÁö¸¸ ÇöÀç »ç¿ëÇÏÁö + ¾Ê´Â´Ù.
+ +
--sysconfdir=DIR
+
¼­¹ö ¼³Á¤ÆÄÀÏ httpd.conf, + mime.types¿Í °°Àº ÀбâÀü¿ë ¸Ó½®º° ÀڷḦ + DIR¿¡ ¼³Ä¡ÇÑ´Ù. sysconfdirÀÇ + ±âº»°ªÀº PREFIX/etcÀÌ´Ù.
+
+ + + +

½Ã½ºÅÛ Á¾·ù

+ +

´Ù¸¥ ½Ã½ºÅÛ¿¡¼­ ½ÇÇàÇÒ ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ + ±³Â÷ÄÄÆÄÀÏÇϱâ(cross-compile)Çϱâ À§ÇÑ ¿É¼ÇµéÀÌ´Ù. ¼­¹ö¸¦ + ÄÄÆÄÀÏÇÑ ½Ã½ºÅÛ¿¡¼­ ¼­¹ö¸¦ ½ÇÇàÇÏ´Â ÀϹÝÀûÀÎ °æ¿ì, ÀÌ + ¿É¼ÇÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.

+ +
+
--build=BUILD
+
µµ±¸¸¦ ÄÄÆÄÀÏÇÏ´Â ½Ã½ºÅÛÀÇ Á¾·ù¸¦ ÁöÁ¤ÇÑ´Ù. ±âº»°ªÀº + config.guess ½ºÅ©¸³Æ®ÀÇ °á°úÀÌ´Ù.
+ +
--host=HOST
+
¼­¹ö¸¦ ½ÇÇàÇÒ ½Ã½ºÅÛÀÇ Á¾·ù¸¦ ÁöÁ¤ÇÑ´Ù. HOSTÀÇ + ±âº»°ªÀº BUILDÀÌ´Ù.
+ +
--target=TARGET
+
TARGET ½Ã½ºÅÛ Á¾·ù¸¦ À§ÇÑ ÄÄÆÄÀÏ·¯¸¦ ¸¸µé¶§ + »ç¿ëÇÑ´Ù. ±âº»°ªÀº HOSTÀÌ´Ù. + autoconf¿¡ ÀÌ ¿É¼ÇÀÌ ÀÖÁö¸¸ ¾ÆÆÄÄ¡ À¥¼­¹ö¿Í´Â + °ü·ÃÀÌ ¾ø´Ù.
+
+ + +

±â´É ¼±ÅÃ

+ +

ÀÌ ¿É¼ÇÀº À¥¼­¹öÀÇ ¼¼ºÎ ±â´ÉÀ» Á¶ÀýÇÑ´Ù.

+ +

ÀϹÝÀûÀÎ ¹®¹ý

+

ÀϹÝÀûÀ¸·Î ´ÙÀ½ ¹®¹ýÀ» »ç¿ëÇÏ¿© ±â´ÉÀ» Æ÷ÇÔÇÏ°í »«´Ù:

+ +
+
--disable-FEATURE
+
FEATURE ±â´ÉÀ» »«´Ù. + --enable-FEATURE=no¿Í °°´Ù.
+ +
--enable-FEATURE[=ARG]
+
FEATURE ±â´ÉÀ» Æ÷ÇÔÇÑ´Ù. ARGÀÇ + ±âº»°ªÀº yesÀÌ´Ù.
+ +
--enable-MODULE=shared
+
ÇØ´ç ¸ðµâÀ» DSO ¸ðµâ·Î ÄÄÆÄÀÏÇÑ´Ù.
+ +
--enable-MODULE=static
+
Æ÷ÇÔÇÏ´Â ¸ðµâÀº ±âº»ÀûÀ¸·Î Á¤ÀûÀ¸·Î ¸µÅ©µÈ´Ù. ÀÌ + ¿É¼ÇÀº ¸í½ÃÀûÀ¸·Î Á¤Àû ¸µÅ©¸¦ °­Á¦ÇÑ´Ù.
+
+ +

ÁÖÀÇ

+ configure´Â foo°¡ ¾ø´Â °æ¿ì + --enable-foo¸¦ »ç¿ëÇصµ ÀÌ »ç½ÇÀ» + ¾Ë·ÁÁÖÁö ¾ÊÀ¸¹Ç·Î ÁÖÀÇÇؼ­ ÀÔ·ÂÇØ¾ß ÇÑ´Ù. +
+ + + +

±âº»ÀûÀ¸·Î Æ÷ÇÔÇÏ´Â ¸ðµâ

+

¾î¶² ¸ðµâÀº ±âº»ÀûÀ¸·Î ÄÄÆÄÀϵDZ⶧¹®¿¡ »ç¿ëÇÏÁö ¾Ê´Â´Ù¸é + ¸í½ÃÀûÀ¸·Î »©Áà¾ß ÇÑ´Ù. ´ÙÀ½ ¿É¼ÇÀº ƯÁ¤ ¸ðµâÀ» ÄÄÆÄÀÏ + °úÁ¤¿¡¼­ Á¦¿ÜÇÑ´Ù.

+ +
+
--disable-actions
+
mod_actions°¡ Á¦°øÇÏ´Â ¿äû¿¡ ´ëÇÑ + Çൿ ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-alias
+
mod_alias°¡ Á¦°øÇÏ´Â ¿äûÀ» + ÆÄÀϽýºÅÛÀÇ ´Ù¸¥ ºÎºÐÀ¸·Î ´ëÀÀÇÏ´Â ±â´ÉÀ» »ç¿ëÇÏÁö + ¾Ê´Â´Ù.
+ +
--disable-asis
+
mod_asis°¡ Á¦°øÇÏ´Â as-is ÆÄÀÏÇüÀ» + Áö¿øÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-auth
+
mod_auth°¡ Á¦°øÇÏ´Â »ç¿ëÀÚº° Á¢±ÙÁ¦¾î + ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù. ÀÌ ¸ðµâÀº »ç¿ëÀÚ¸í°ú ¾ÏÈ£¸¦ + ÀÏ¹Ý ¹®ÀÚÆÄÀÏ¿¡ ÀúÀåÇÏ´Â HTTP Basic Authentication¿¡¼­ + »ç¿ëÇÑ´Ù.
+ +
--disable-autoindex
+
mod_autoindex°¡ Á¦°øÇÏ´Â µð·ºÅ丮 + ¸ñ·Ï ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-access
+
mod_access°¡ Á¦°øÇϴ ȣ½ºÆ®º° + Á¢±ÙÁ¦¾î ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-cgi
+
ºñ¾²·¹µå MPMÀ» »ç¿ëÇÏ´Â °æ¿ì CGI ½ºÅ©¸³Æ®¸¦ Áö¿øÇÏ´Â + mod_cgi¸¦ ±âº»ÀûÀ¸·Î Æ÷ÇÔÇÑ´Ù. ÀÌ + ¿É¼ÇÀ» »ç¿ëÇϸé CGI¸¦ Áö¿øÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-cgid
+
¾²·¹µå MPMÀÎ worker³ª + perchild¸¦ »ç¿ëÇÏ´Â °æ¿ì ±âº»ÀûÀ¸·Î + mod_cgid°¡ CGI ½ºÅ©¸³Æ®¸¦ Áö¿øÇÑ´Ù. + ÀÌ ¿É¼ÇÀ» »ç¿ëÇϸé CGI¸¦ Áö¿øÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-charset-lite
+
mod_charset_lite°¡ Á¦°øÇÏ´Â ¹®ÀÚÁýÇÕ + º¯È¯ ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù. ÀÌ ¸ðµâÀº EBCDIC ½Ã½ºÅÛ¿¡¼­¸¸ + ±âº»ÀûÀ¸·Î Æ÷ÇÔÇÑ´Ù.
+ +
--disable-dir
+
mod_dirÀÌ Á¦°øÇÏ´Â µð·ºÅ丮 ¿äû + ó¸® ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-env
+
mod_env°¡ Á¦°øÇϴ ȯ°æº¯¼ö ¼³Á¤/ÇØÁ¦ + ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ + +
--disable-http
+
HTTP ÇÁ·ÎÅäÄÝÀ» ó¸®ÇÏÁö ¾Ê´Â´Ù. http + ¸ðµâÀº ¼­¹ö°¡ À¥¼­¹ö·Î µ¿ÀÛÇϴµ¥ ±âº»ÀûÀÎ ¸ðµâÀÌ´Ù. + ´ë½Å ´Ù¸¥ ÇÁ·ÎÅäÄÝ ¸ðµâÀ» »ç¿ëÇÒ °æ¿ì¿¡¸¸ ÀÌ ¸ðµâÀÌ + À¯¿ëÇÏ´Ù. ÀÚ½ÅÀÌ ¹«¾ùÀ» ÇÏ´ÂÁö È®½ÇÈ÷ ¾ËÁö + ¸øÇÑ´Ù¸é ÀÌ ¿É¼ÇÀ» »©Áö ¸¶¶ó +
+ ÁÖÀÇ: ÀÌ ¸ðµâÀº Ç×»ó Á¤ÀûÀ¸·Î ¸µÅ©µÈ´Ù.
+ +
--disable-imagemap
+
mod_imagemapÀÌ Á¦°øÇÏ´Â ¼­¹ö±â¹Ý imagemap + ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-include
+
mod_include°¡ Á¦°øÇÏ´Â Server Side + Includes ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-log-config
+
mod_log_config°¡ Á¦°øÇÏ´Â ·Î±× + ¼³Á¤À» »ç¿ëÇÏÁö ¾Ê´Â´Ù. ÀÌ ¸ðµâÀÌ ¾øÀ¸¸é ¼­¹öÀÇ ¿äûÀ» + ·Î±×¿¡ ±â·ÏÇÒ ¼ö ¾ø´Ù.
+ +
--disable-mime
+
mod_mimeÀº ¿äûÇÑ ÆÄÀϸíÀÇ È®ÀåÀÚ¿¡ + µû¶ó ÆÄÀÏÀÇ Çൿ°ú ³»¿ë(mime-type, ¾ð¾î, ¹®ÀÚÁýÇÕ, + ÀÎÄÚµù)À» °áÁ¤ÇÑ´Ù. (ÀÌ ¸ðµâÀ» Á¦°ÅÇÏ¿©) ÆÄÀÏ È®ÀåÀÚ¸¦ + MIME°ú ¿¬°üÇÏÁö ¾Ê´Â °ÍÀ» ÀϹÝÀûÀ¸·Î ÃßõÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-negotiation
+
mod_negotiationÀÌ Á¦°øÇÏ´Â ³»¿ëÇù»ó + ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-setenvif
+
mod_setenvif°¡ Á¦°øÇÏ´Â Çì´õ¿¡ + µû¶ó ȯ°æº¯¼ö¸¦ ¼³Á¤ÇÏ´Â ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-status
+
mod_status°¡ Á¦°øÇÏ´Â ÇÁ·Î¼¼½º/¾²·¹µå + °¨½Ã ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+ +
--disable-userdir
+
mod_userdirÀÌ Á¦°øÇÏ´Â ¿äûÀ» »ç¿ëÀÚº° + µð·ºÅ丮¿¡ ´ëÀÀÇÏ´Â ±â´ÉÀ» »ç¿ëÇÏÁö ¾Ê´Â´Ù.
+
+ + +

±âº»ÀûÀ¸·Î Æ÷ÇÔÇÏÁö ¾Ê´Â ¸ðµâ

+

±âº»ÀûÀ¸·Î ÄÄÆÄÀϵǴ ¸ðµâµµ ÀÖÁö¸¸, ¸ðµâÀ» »ç¿ëÇÏ·Á¸é + Á÷Á¢ ȤÀº most³ª all Å°¿öµå¸¦ + »ç¿ëÇÏ¿© ¸í½ÃÀûÀ¸·Î Æ÷ÇÔÇØ¾ß ÇÏ´Â ¸ðµâÀÌ ÀÖ´Ù. ±×·¡¼­ + ¾Æ·¡ ¿É¼ÇµéÀ» »ç¿ëÇÑ´Ù.

+ +
+
--enable-auth-anon
+
mod_auth_anonÀÌ Á¦°øÇÏ´Â À͸í»ç¿ëÀÚ + Á¢±Ù ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-auth-dbm
+
mod_auth_dbmÀº »ç¿ëÀÚ¸í°ú ¾ÏÈ£¸¦ + DBMÇü½ÄÀÇ µ¥ÀÌÅͺ£À̽º ÆÄÀÏ¿¡ ÀúÀåÇÏ´Â HTTP Basic + Authentication¿¡¼­ »ç¿ëÇÑ´Ù. ¸ðµâÀ» »ç¿ëÇÏ·Á¸é ÀÌ + ¿É¼ÇÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-auth-digest
+
mod_auth_digest°¡ Á¦°øÇÏ´Â RFC2617 + Digest authenticationÀ» »ç¿ëÇÑ´Ù. ÀÌ ¸ðµâÀº Á¤º¸¸¦ + ÀÏ¹Ý ¹®ÀÚÆÄÀÏ¿¡ ÀúÀåÇÑ´Ù.
+ +
--enable-authnz-ldap
+
mod_authnz_ldapÀÌ Á¦°øÇÏ´Â LDAP±â¹Ý + ÀÎÁõ ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-cache
+
mod_cache°¡ Á¦°øÇÏ´Â µ¿ÀûÀ¸·Î »ý¼ºÇÏ´Â + ÆÄÀÏÀÇ Ä³½Ì ±â´ÉÀ» »ç¿ëÇÑ´Ù. ¸Å¿ì ºÎÇÏ°¡ ¸¹°Å³ª ÇÁ·Ï½Ã + ¼­¹ö¸¦ ij½ÌÇÏ´Â ¼­¹ö¿¡°Ô ÀÌ ½ÇÇèÀûÀÎ ¸ðµâÀÌ À¯¿ëÇÒ + ¼ö ÀÖ´Ù. ÃÖ¼ÒÇÑ ÇÑ°¡Áö ÀúÀå°ü¸®¸ðµâ(storage management + module)À» (¿¹¸¦ µé¾î, mod_disk_cache³ª + mod_mem_cache) °°ÀÌ »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
--enable-cern-meta
+
mod_cern_meta°¡ Á¦°øÇÏ´Â CERN ¸ÞŸÆÄÀÏ + Áö¿ø ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-charset-lite
+
mod_charset_lite°¡ Á¦°øÇÏ´Â ¹®ÀÚÁýÇÕ + º¯È¯ ±â´ÉÀ» »ç¿ëÇÑ´Ù. ÀÌ ¸ðµâÀº EBCDIC ½Ã½ºÅÛ¿¡¼­¸¸ + ±âº»ÀûÀ¸·Î Æ÷ÇԵȴÙ. ´Ù¸¥ ½Ã½ºÅÛ¿¡¼­´Â Á÷Á¢ Æ÷ÇÔ½ÃÄÑÁà¾ß + ÇÑ´Ù.
+ +
--enable-dav
+
mod_dav°¡ Á¦°øÇÏ´Â WebDAV ÇÁ·ÎÅäÄÝ + ó¸® ±â´ÉÀ» »ç¿ëÇÑ´Ù. µ¶¸³µÈ mod_dav_fs + ¸ðµâÀÌ ÆÄÀϽýºÅÛ ÀÚ¿øÀ» Áö¿øÇÑ´Ù. ÀÌ ¸ðµâÀº + --enable-dav¸¦ »ç¿ëÇϸé ÀÚµ¿À¸·Î Æ÷ÇÔÇÑ´Ù.
+ ÁÖÀÇ: mod_dav´Â http + ÇÁ·ÎÅäÄÝ ¸ðµâ°ú °°ÀÌ »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
--enable-dav-fs
+
mod_dav_fs°¡ Á¦°øÇÏ´Â DAVÀÇ ÆÄÀϽýºÅÛ + ÀÚ¿ø Áö¿ø ±â´ÉÀ» »ç¿ëÇÑ´Ù. ÀÌ ¸ðµâÀº + mod_dav ¸ðµâÀ» À§ÇÑ Á¦°øÀÚÀ̱⠶§¹®¿¡ + --enable-davµµ »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
--enable-deflate
+
mod_deflate°¡ Á¦°øÇÏ´Â ¾ÐÃàÀü¼Û + ÀÎÄÚµù ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-disk-cache
+
mod_disk_cache°¡ Á¦°øÇÏ´Â µð½ºÅ© + ij½Ì ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-expires
+
mod_expires°¡ Á¦°øÇÏ´Â Expires + Çì´õ Á¶Àý ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-ext-filter
+
mod_ext_filter°¡ Á¦°øÇÏ´Â ¿ÜºÎ + ÇÊÅÍ Áö¿ø ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-file-cache
+
mod_file_cache°¡ Á¦°øÇÏ´Â ÆÄÀÏ + ij½Ì ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-headers
+
mod_headers°¡ Á¦°øÇÏ´Â HTTP Çì´õ + Á¶Àý ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-info
+
mod_info°¡ Á¦°øÇÏ´Â ¼­¹öÁ¤º¸ ±â´ÉÀ» + »ç¿ëÇÑ´Ù.
+ +
--enable-ldap
+
mod_ldapÀÌ Á¦°øÇÏ´Â LDAP ij½Ì°ú + ¿¬°áÇ® ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-logio
+
mod_logio°¡ Á¦°øÇÏ´Â ·Î±×¿¡ Çì´õ¿Í + ÀÔÃâ·Â ¹ÙÀÌÆ®¼ö¸¦ ±â·ÏÇÏ´Â ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-mem-cache
+
mod_mem_cache°¡ Á¦°øÇÏ´Â ¸Þ¸ð¸® + ij½Ì ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-mime-magic
+
mod_mime_magicÀÌ Á¦°øÇÏ´Â MIME + type ÀÚµ¿ ÀÎ½Ä ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-isapi
+
mod_isapi°¡ Á¦°øÇÏ´Â isapi È®ÀåÀ» + Áö¿øÇÑ´Ù.
+ +
--enable-proxy
+
mod_proxy°¡ Á¦°øÇÏ´Â ÇÁ·Ï½Ã/°ÔÀÌÆ®¿þÀÌ + ±â´ÉÀ» »ç¿ëÇÑ´Ù. CONNECT, FTP, + HTTP¿¡ ´ëÇÑ ÇÁ·Ï½Ã ±â´ÉÀ» °¢°¢ + mod_proxy_connect, + mod_proxy_ftp, + mod_proxy_http + ¸ðµâÀÌ Á¦°øÇÑ´Ù. --enable-proxy¸¦ »ç¿ëÇϸé + ÀÌ ¼¼ ¸ðµâÀ» ÀÚµ¿À¸·Î Æ÷ÇÔÇÑ´Ù.
+ +
--enable-proxy-connect
+
mod_proxy_connect°¡ Á¦°øÇÏ´Â + CONNECT ¿äû¿¡ ´ëÇÑ ÇÁ·Ï½Ã Áö¿ø ±â´ÉÀ» + »ç¿ëÇÑ´Ù. ÀÌ ¸ðµâÀº mod_proxy ¸ðµâÀÇ + È®ÀåÀ̹ǷÎ, --enable-proxyµµ °°ÀÌ »ç¿ëÇØ¾ß + ÇÑ´Ù.
+ +
--enable-proxy-ftp
+
mod_proxy_ftp°¡ Á¦°øÇÏ´Â + FTP ¿äû¿¡ ´ëÇÑ ÇÁ·Ï½Ã Áö¿ø ±â´ÉÀ» »ç¿ëÇÑ´Ù. + ÀÌ ¸ðµâÀº mod_proxy ¸ðµâÀÇ È®ÀåÀ̹ǷÎ, + --enable-proxyµµ °°ÀÌ »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
--enable-proxy-http
+
mod_proxy_http°¡ Á¦°øÇÏ´Â + HTTP ¿äû¿¡ ´ëÇÑ ÇÁ·Ï½Ã Áö¿ø ±â´ÉÀ» »ç¿ëÇÑ´Ù. + ÀÌ ¸ðµâÀº mod_proxy ¸ðµâÀÇ È®ÀåÀ̹ǷÎ, + --enable-proxyµµ °°ÀÌ »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
--enable-rewrite
+
mod_rewrite°¡ Á¦°øÇÏ´Â ±ÔÄ¢±â¹Ý + URL Á¶ÀÛ ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-so
+
mod_so°¡ Á¦°øÇÏ´Â DSO ±â´ÉÀ» »ç¿ëÇÑ´Ù. + --enable-mods-shared ¿É¼ÇÀ» »ç¿ëÇϸé + ÀÚµ¿À¸·Î ÀÌ ¸ðµâÀ» Æ÷ÇÔÇÑ´Ù.
+ +
--enable-speling
+
mod_spellingÀÌ Á¦°øÇÏ´Â URL¿¡¼­ + ÀϹÝÀûÀÎ ¸ÂÃã¹ý ½Ç¼ö¸¦ °íÄ¡´Â ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-ssl
+
mod_sslÀÌ Á¦°øÇÏ´Â SSL/TLS ±â´ÉÀ» + »ç¿ëÇÑ´Ù.
+ +
--enable-unique-id
+
mod_unique_id°¡ Á¦°øÇÏ´Â ¿äû¸¶´Ù + À¯ÀÏÇÑ ½Äº°ÀÚ¸¦ ¸¸µå´Â ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-usertrack
+
mod_usertrackÀÌ Á¦°øÇÏ´Â »ç¿ëÀÚ¼¼¼Ç + ÃßÀû ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+ +
--enable-vhost-alias
+
mod_vhost_alias°¡ Á¦°øÇÏ´Â ´ë·® + °¡»óÈ£½ºÆ® ±â´ÉÀ» »ç¿ëÇÑ´Ù.
+
+ + +

°³¹ßÀÚ¸¦ À§ÇÑ ¸ðµâ

+

´ÙÀ½ ¸ðµâÀº Å×½ºÆ®¿ëÀ¸·Î °³¹ßÀÚ¿¡°Ô¸¸ À¯¿ëÇϸç, ±âº»ÀûÀ¸·Î + Æ÷ÇÔÇÏÁö ¾Ê´Â´Ù. ÀÌ ¸ðµâÀ» »ç¿ëÇÏ·Á¸é ´ÙÀ½ ¿É¼ÇÀ» »ç¿ëÇÑ´Ù. + ÀÌ ¸ðµâÀÌ ÇÊ¿äÇÑÁö È®½ÇÄ¡¾Ê´Ù¸é »ç¿ëÇÏÁö ¸¶¶ó.

+ +
+ +
--enable-bucketeer
+
mod_bucketeer°¡ Á¦°øÇÏ´Â ¹öŶ(bucket) + Á¶ÀÛ ÇÊÅ͸¦ »ç¿ëÇÑ´Ù.
+ + +
--enable-case-filter
+
mod_case_filterÀÇ ´ë¹®ÀÚº¯È¯ Ãâ·ÂÇÊÅÍ + °ßº»À» »ç¿ëÇÑ´Ù.
+ + +
--enable-case-filter-in
+
mod_case_filter_inÀÇ ´ë¹®ÀÚº¯È¯ ÀÔ·ÂÇÊÅÍ + °ßº»À» »ç¿ëÇÑ´Ù.
+ +
--enable-echo
+
mod_echo°¡ Á¦°øÇÏ´Â ECHO ¼­¹ö¸¦ + »ç¿ëÇÑ´Ù.
+ +
--enable-example
+
°ßº» ¿¹Á¦¸ðµâÀÎ mod_exampleÀ» + »ç¿ëÇÑ´Ù.
+ + +
--enable-optional-fn-export
+
mod_optional_fn_export°¡ Á¦°øÇÏ´Â ¼±ÅÃÀûÀÎ + ÇÔ¼ö ¿¢½ºÆ÷Æ®(exporter)ÀÇ ¿¹¸¦ »ç¿ëÇÑ´Ù.
+ + +
--enable-optional-fn-import
+
mod_optional_fn_import°¡ Á¦°øÇÏ´Â ¼±ÅÃÀûÀÎ + ÇÔ¼ö ÀÓÆ÷Æ®(importer)ÀÇ ¿¹¸¦ »ç¿ëÇÑ´Ù.
+ + +
--enable-optional-hook-export
+
mod_optional_hook_export°¡ Á¦°øÇÏ´Â + ¼±ÅÃÀûÀÎ ÈÅ(hook) ¿¢½ºÆ÷Æ®ÀÇ ¿¹¸¦ »ç¿ëÇÑ´Ù.
+ + +
--enable-optional-hook-import
+
mod_optional_hook_import°¡ Á¦°øÇÏ´Â + ¼±ÅÃÀûÀÎ ÈÅ ÀÓÆ÷Æ®ÀÇ ¿¹¸¦ »ç¿ëÇÑ´Ù.
+
+ + +

MPM°ú Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâ

+

´ÙÀ½ ¿É¼ÇÀ» »ç¿ëÇÏ¿© ÇÊ¿äÇÑ ´ÙÁß󸮸ðµâ°ú Á¦»ïÀÚ°¡ + ¸¸µç ¸ðµâÀ» Ãß°¡ÇÑ´Ù:

+ +
+
--with-module=module-type:module-file +
+

Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâÀ» Á¤ÀûÀ¸·Î ¸µÅ©ÇÒ ¸ðµâ ¸ñ·Ï¿¡ + Ãß°¡ÇÑ´Ù. ¾ÆÆÄÄ¡ À¥¼­¹ö ¼Ò½º Æ®¸®ÀÇ + modules/module-type¿¡¼­ ¸ðµâÀÇ + ¼Ò½ºÆÄÀÏ module-fileÀ» ã±â¶§¹®¿¡ + ±×°÷¿¡ ¼Ò½ºÆÄÀÏÀÌ ÀÖ¾î¾ß ÇÑ´Ù. ±×°÷¿¡ ÆÄÀÏÀÌ ¾ø´Ù¸é + configure´Â module-fileÀÌ + Àý´ëÆÄÀÏ°æ·Î¶ó°í °¡Á¤ÇÏ°í ¼Ò½ºÆÄÀÏÀ» + module-type ÇÏÀ§µð·ºÅ丮¿¡ º¹»çÇÏ·Á°í + ½ÃµµÇÑ´Ù.

+

ÀÌ ¿É¼ÇÀº ¼Ò½ºÆÄÀÏÀÌ ÇÑ°³ÀÎ ÀÛÀº ¿ÜºÎ ¸ðµâÀ» Ãß°¡Çϴµ¥ + À¯¿ëÇÏ´Ù. ´õ º¹ÀâÇÑ ¸ðµâÀº °³¹ß»ç°¡ Á¦°øÇÑ ¹®¼­¸¦ + Âü°íÇØ¾ß ÇÑ´Ù.

+

ÁÖÀÇ

+ Á¤ÀûÀ¸·Î ¸µÅ©µÈ ¸ðµâÀÌ ¾Æ´Ñ DSO ¸ðµâÀ» ¿øÇÑ´Ù¸é + apxs¸¦ »ç¿ëÇ϶ó.
+
+ +
--with-mpm=MPM
+
¼­¹öÀÇ µ¿ÀÛ¹æ½ÄÀ» ¼±ÅÃÇÑ´Ù. Á¤È®È÷ ÇÑ°¡Áö ´ÙÁß󸮸ðµâ¸¸À» ¼±ÅÃÇØ¾ß ÇÑ´Ù. + ¼±ÅÃÇÏÁö ¾ÊÀ¸¸é »ç¿ëÇÏ´Â ¿î¿µÃ¼Á¦ÀÇ ±âº» MPMÀ» »ç¿ëÇÑ´Ù. + »ç¿ëÇÒ ¼ö ÀÖ´Â MPM¿¡´Â beos, + leader, mpmt_os2, + perchild, prefork, + threadpool, worker°¡ + ÀÖ´Ù.
+
+ + +

±âŸ ¿É¼Ç

+
+
--enable-maintainer-mode
+
µð¹ö±ë ¸ðµå¿Í ÄÄÆÄÀϽà °æ°í¸¦ ÀÛµ¿ÇÑ´Ù.
+ +
--enable-mods-shared=MODULE-LIST
+
+

µ¿Àû°øÀ¯¸ðµâ·Î ÄÄÆÄÀÏÇÒ ¸ðµâ ¸ñ·ÏÀ» ÁöÁ¤ÇÑ´Ù. Áï, + ÀÌ ¸ðµâµéÀº LoadModule Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© µ¿ÀûÀ¸·Î Àоîµé¿©¾ß ÇÑ´Ù.

+

MODULE-LIST´Â °ø¹éÀ¸·Î ±¸ºÐÇÑ ¸ðµâ¸íµéÀ» + µû¿ÈÇ¥·Î ¹­Àº ¸ñ·ÏÀÌ´Ù. ¸ðµâ¸í¿¡¼­ ¾Õ¿¡ + mod_´Â »«´Ù. ¿¹¸¦ µé¾î:

+

+ --enable-mods-shared='headers rewrite dav' +

+

¶Ç, Ưº°ÇÑ Å°¿öµå all°ú most¸¦ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î,

+

+ --enable-mods-shared=most +

+

´Â ´ëºÎºÐÀÇ ¸ðµâÀ» DSO ¸ðµâ·Î ÄÄÆÄÀÏÇÑ´Ù. +

+
+ +
--enable-modules=MODULE-LIST
+
--enable-mods-shared¿Í ºñ½ÁÇÏÁö¸¸, + ÀÌ ¿É¼ÇÀº ¿­°ÅÇÑ ¸ðµâµéÀ» Á¤ÀûÀ¸·Î ¸µÅ©ÇÑ´Ù. Áï, ÀÌ + ¸ðµâµéÀº httpd ½ÇÇàÇÏ¸é ¾ðÁ¦³ª »ç¿ëÇÒ + ¼ö ÀÖ´Ù. LoadModule·Î ÀоîµéÀÏ + ÇÊ¿ä°¡ ¾ø´Ù.
+ +
--enable-v4-mapped
+
IPv6 ¼ÒÄÏÀÌ IPv4 ¿¬°áÀ» ó¸®ÇÒ ¼ö ÀÖµµ·Ï ÇÑ´Ù.
+ +
--with-port=PORT
+
httpd°¡ ±â´Ù¸± Æ÷Æ®¸¦ ÁöÁ¤ÇÑ´Ù. ÀÌ + Æ÷Æ®¹øÈ£´Â ¼³Á¤ÆÄÀÏ httpd.conf¸¦ ¸¸µé¶§ + ¾²ÀδÙ. ±âº»°ªÀº 80ÀÌ´Ù.
+ +
--with-program-name
+
´Ù¸¥ ½ÇÇàÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù. ±âº»°ªÀº + httpdÀÌ´Ù.
+
+ + + +

Ãß°¡ ÆÐÅ°Áö ¼±ÅÃ

+

´ÙÀ½ ¿É¼ÇÀº Ãß°¡ ÆÐÅ°Áö¸¦ ¼±ÅÃÇÑ´Ù.

+ +

ÀϹÝÀûÀÎ ¹®¹ý

+

ÀϹÝÀûÀ¸·Î ´ÙÀ½°ú °°Àº ¹®¹ýÀ» »ç¿ëÇÏ¿© Ãß°¡ ÆÐÅ°Áö¸¦ + ´Ù·é´Ù:

+ +
+
--with-PACKAGE[=ARG]
+
ÆÐÅ°Áö PACKAGE¸¦ »ç¿ëÇÑ´Ù. + ARGÀÇ ±âº»°ªÀº yesÀÌ´Ù.
+ +
--without-PACKAGE
+
ÆÐÅ°Áö PACKAGE¸¦ »ç¿ëÇÏÁö ¾Ê´Â´Ù. + --with-PACKAGE=no¿Í °°´Ù. + autoconf¿¡ ÀÌ ¿É¼ÇÀÌ ÀÖÁö¸¸ ¾ÆÆÄÄ¡ À¥¼­¹ö¿Í´Â + °ü°è°¡ ¾ø´Ù.
+
+ + + + +

ƯÁ¤ ÆÐÅ°Áö

+
+
--with-apr=DIR|FILE
+
httpd ¼Ò½º ¹èÆ÷º»¿¡ Æ÷ÇÔµÈ Apache Portable + Runtime (APR)Àº ÀÚµ¿À¸·Î À¥¼­¹ö¿Í °°ÀÌ ÄÄÆÄÀϵȴÙ. + ¸¸¾à ÀÌ¹Ì ¼³Ä¡µÈ APRÀ» ´ë½Å »ç¿ëÇÏ°í ½Í´Ù¸é + configure¿¡°Ô apr-config + ½ºÅ©¸³Æ®ÀÇ °æ·Î¸¦ ¾Ë·ÁÁÖ¾î¾ß ÇÑ´Ù. APR°¡ ¼³Ä¡µÈ Àý´ë°æ·Î, + ÆÄÀϸí, µð·ºÅ丮¸íÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. ÁöÁ¤ÇÑ µð·ºÅ丮³ª + ±× µð·ºÅ丮ÀÇ ÇÏÀ§µð·ºÅ丮 bin¿¡ + apr-config°¡ ÀÖ¾î¾ß ÇÑ´Ù.
+ +
--with-apr-util=DIR|FILE
+
httpd ¼Ò½º ¹èÆ÷º»¿¡ Æ÷ÇÔµÈ Apache Portable + Runtime Utilities (APU)´Â ÀÚµ¿À¸·Î À¥¼­¹ö¿Í °°ÀÌ + ÄÄÆÄÀϵȴÙ. ¸¸¾à ÀÌ¹Ì ¼³Ä¡µÈ APUÀ» ´ë½Å »ç¿ëÇÏ°í ½Í´Ù¸é + configure¿¡°Ô apu-config + ½ºÅ©¸³Æ®ÀÇ °æ·Î¸¦ ¾Ë·ÁÁÖ¾î¾ß ÇÑ´Ù. APU°¡ ¼³Ä¡µÈ Àý´ë°æ·Î, + ÆÄÀϸí, µð·ºÅ丮¸íÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. ÁöÁ¤ÇÑ µð·ºÅ丮³ª + ±× µð·ºÅ丮ÀÇ ÇÏÀ§µð·ºÅ丮 bin¿¡ + apu-config°¡ ÀÖ¾î¾ß ÇÑ´Ù.
+ +
--with-ssl=DIR
+
mod_sslÀ» »ç¿ëÇÏ´Â °æ¿ì + configure´Â ¼³Ä¡µÈ OpenSSLÀ» ã´Â´Ù. + ´ë½Å ÀÌ ¿É¼ÇÀ» »ç¿ëÇÏ¿© SSL/TLS µµ±¸ÀÇ µð·ºÅ丮°æ·Î¸¦ + ¾Ë·ÁÁÙ ¼ö ÀÖ´Ù.
+ +
--with-z=DIR
+
(mod_deflate¸¦ »ç¿ëÇÏ´Â °æ¿ì¿Í + °°ÀÌ) ±¸¼º¿¡ ÇÊ¿äÇÏ´Ù¸é ÀÚµ¿À¸·Î configure´Â + ¼³Ä¡µÈ zlib ¶óÀ̺귯¸®¸¦ ã´Â´Ù. ´ë½Å + ÀÌ ¿É¼ÇÀ» »ç¿ëÇÏ¿© ¾ÐÃà ¶óÀ̺귯¸®ÀÇ µð·ºÅ丮°æ·Î¸¦ + ¾Ë·ÁÁÙ ¼ö ÀÖ´Ù.
+
+ +

mod_authn_dbm°ú + mod_rewriteÀÇ DBM RewriteMap °°Àº ¾ÆÆÄÄ¡ + À¥¼­¹öÀÇ ÀϺΠ±â´ÉÀº Á¤º¸¸¦ »¡¸® ã±âÀ§ÇØ °£´ÜÇÑ Å°/°ª + µ¥ÀÌÅͺ£À̽º¸¦ »ç¿ëÇÑ´Ù. APU¿¡ SDBMÀÌ µé¾îÀ־ ¾ðÁ¦³ª + ÃÖ¼ÒÇÑ ÀÌ µ¥ÀÌÅͺ£À̽º´Â »ç¿ëÇÒ ¼ö ÀÖ´Ù. ´Ù¸¥ Á¾·ùÀÇ + µ¥ÀÌÅͺ£À̽º¸¦ »ç¿ëÇÏ°í ½Í´Ù¸é ¾Æ·¡ ¿É¼ÇÀ» »ç¿ëÇÑ´Ù:

+ +
+
--with-gdbm[=path]
+
path¸¦ ÁöÁ¤ÇÏÁö ¾ÊÀ¸¸é, + configure´Â ÀϹÝÀûÀÎ °Ë»ö°æ·Î¿¡¼­ ¼³Ä¡µÈ + GNU DBM Çì´õÆÄÀÏ°ú ¶óÀ̺귯¸®¸¦ ã´Â´Ù. Á÷Á¢ + path¸¦ ÁöÁ¤Çϸé configure´Â + path/lib°ú + path/include¿¡¼­ ÇÊ¿äÇÑ ÆÄÀÏÀ» + ã´Â´Ù. ¸¶Áö¸·À¸·Î path¿¡ Çì´õÆÄÀÏ °æ·Î¿Í + ¶óÀ̺귯¸® °æ·Î¸¦ ÄÝ·ÐÀ» »çÀÌ¿¡ µÎ°í °°ÀÌ ÀûÀ» ¼ö + ÀÖ´Ù.
+ +
--with-ndbm[=path]
+
--with-gdbm°ú °°Áö¸¸ ¼³Ä¡µÈ New DBMÀ» + ã´Â´Ù.
+ +
--with-berkeley-db[=path]
+
--with-gdbm°ú °°Áö¸¸ ¼³Ä¡µÈ Berkeley + DB¸¦ ã´Â´Ù.
+
+ +

ÁÖÀÇ

+

DBM ¿É¼ÇÀº APU°¡ Á¦°øÇϸç APU ±¸¼º½ºÅ©¸³Æ®·Î Á÷Á¢ + Àü´ÞµÈ´Ù. ±×·¡¼­ --with-apr-utilÀ» »ç¿ëÇÏ¿© + ÀÌ¹Ì ¼³Ä¡µÈ APU¸¦ »ç¿ëÇÑ´Ù¸é DBM ¿É¼ÇÀº ¼Ò¿ëÀÌ ¾ø´Ù.

+

À¥¼­¹ö´Â ¿©·¯ DBM ±¸ÇöÀ» °°ÀÌ »ç¿ëÇÒ ¼ö ÀÖ´Ù. ½ÇÇà½Ã + ÀûÀýÇÑ DBM Á¾·ù¸¦ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù.

+
+ + + +

Áö¿ø ÇÁ·Î±×·¥À» À§ÇÑ ¿É¼Ç

+
+
--enable-static-support
+
Áö¿ø ÇÁ·Î±×·¥À» Á¤ÀûÀ¸·Î ¸µÅ©µÈ ½ÇÇàÆÄÀÏ·Î ¸¸µç´Ù. + Áï, ÇÊ¿äÇÑ ¶óÀ̺귯¸®¸¦ ¸ðµÎ Æ÷ÇÔÇϵµ·Ï ½ÇÇàÆÄÀÏÀ» + ÄÄÆÄÀÏÇÑ´Ù. ÀÌ ¿É¼ÇÀ» »ç¿ëÇÏÁö ¾ÊÀ¸¸é ±âº»°ªÀ¸·Î Áö¿ø + ÇÁ·Î±×·¥À» µ¿ÀûÀ¸·Î ¸µÅ©ÇÑ´Ù.
+ +
--enable-suexec
+
À¥¼­¹ö°¡ ½ÇÇàÇÏ´Â ÇÁ·Î¼¼½ºÀÇ uid¿Í gid¸¦ ¼³Á¤ÇÏ´Â + suexec¸¦ »ç¿ëÇÏ·Á¸é + ÀÌ ¿É¼ÇÀ» »ç¿ëÇÑ´Ù. suid ½ÇÇàÆÄÀÏÀÇ º¸¾È»ó À§ÇèÀ» + ¸ðµÎ ¾ËÁö ¸øÇÑ´Ù¸é ÀÌ ¿É¼ÇÀ» »ç¿ëÇÏÁö ¸¶¶ó. + suexec¸¦ ±¸¼ºÇÏ´Â ¿É¼ÇÀº + ¾Æ·¡¿¡¼­ ¼³¸íÇÑ´Ù.
+
+ +

´ÙÀ½ ¿É¼ÇÀ» »ç¿ëÇÏ¿© Áö¿ø ÇÁ·Î±×·¥º°·Î Á¤ÀûÀ¸·Î ¸µÅ©µÈ + ½ÇÇàÆÄÀÏÀ» ¸¸µé ¼ö ÀÖ´Ù:

+ +
+
--enable-static-ab
+
ab¸¦ Á¤ÀûÀ¸·Î ¸µÅ©µÈ + ½ÇÇàÆÄÀÏ·Î ÄÄÆÄÀÏÇÑ´Ù.
+ + +
--enable-static-checkgid
+
checkgid¸¦ Á¤ÀûÀ¸·Î ¸µÅ©µÈ ½ÇÇàÆÄÀÏ·Î + ÄÄÆÄÀÏÇÑ´Ù.
+ + +
--enable-static-htdbm
+
htdbmÀ» Á¤ÀûÀ¸·Î ¸µÅ©µÈ ½ÇÇàÆÄÀÏ·Î + ÄÄÆÄÀÏÇÑ´Ù.
+ +
--enable-static-htdigest
+
htdigest¸¦ + Á¤ÀûÀ¸·Î ¸µÅ©µÈ ½ÇÇàÆÄÀÏ·Î ÄÄÆÄÀÏÇÑ´Ù.
+ +
--enable-static-htpasswd
+
htpasswd¸¦ + Á¤ÀûÀ¸·Î ¸µÅ©µÈ ½ÇÇàÆÄÀÏ·Î ÄÄÆÄÀÏÇÑ´Ù.
+ +
--enable-static-logresolve
+
logresolve¸¦ + Á¤ÀûÀ¸·Î ¸µÅ©µÈ ½ÇÇàÆÄÀÏ·Î ÄÄÆÄÀÏÇÑ´Ù.
+ +
--enable-static-rotatelogs
+
rotatelogs¸¦ + Á¤ÀûÀ¸·Î ¸µÅ©µÈ ½ÇÇàÆÄÀÏ·Î ÄÄÆÄÀÏÇÑ´Ù.
+
+ +

suexec ¼³Á¤ ¿É¼Ç

+

¾Æ·¡ ¿É¼ÇÀº suexec¸¦ ÀÚ¼¼È÷ ¼³Á¤ÇÑ´Ù. + ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â suEXEC + ±¸¼º°ú ¼³Ä¡¸¦ Âü°íÇ϶ó.

+ +
+
--with-suexec-bin
+
suexec ½ÇÇàÆÄÀÏÀÇ °æ·Î¸¦ ÁöÁ¤ÇÑ´Ù. ±âº»°ªÀº + --sbindirÀÌ´Ù (¼³Ä¡ µð·ºÅ丮ÀÇ ÀÚ¼¼ÇÑ + Á¶Á¤ Âü°í).
+ +
--with-suexec-caller
+
suexec¸¦ ½ÇÇàÇÒ »ç¿ëÀÚ¸¦ ÁöÁ¤ÇÑ´Ù. + ÀÌ »ç¿ëÀÚ´Â º¸Åë httpd¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚ¿Í + °°¾Æ¾ß ÇÑ´Ù.
+ +
--with-suexec-docroot
+
suexec´Â ÀÌ ¿É¼ÇÀ¸·Î ÁöÁ¤ÇÑ µð·ºÅ丮 + ¾Æ·¡¿¡ ÀÖ´Â ½ÇÇàÆÄÀϸ¸À» ½ÇÇàÇÒ ¼ö ÀÖ´Ù. ±âº»°ªÀº + --datadir/htdocs´Ù.
+ +
--with-suexec-gidmin
+
suexec¿¡¼­ ÁöÁ¤°¡´ÉÇÑ ÃÖ¼Ò GID¸¦ ¼³Á¤ÇÑ´Ù. + ±âº»°ªÀº 100ÀÌ´Ù.
+ +
--with-suexec-logfile
+
suexec ·Î±×ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù. ·Î±×ÆÄÀϸíÀÇ + ±âº»°ªÀº suexec_logÀÌ°í, + --logfiledir¿¡ À§Ä¡ÇÑ´Ù.
+ +
--with-suexec-safepath
+
suexec°¡ ½ÃÀÛÇÏ´Â ÇÁ·Î¼¼½ºÀÇ + PATH ȯ°æº¯¼ö°ªÀ» ÁöÁ¤ÇÑ´Ù. ±âº»°ªÀº + /usr/local/bin:/usr/bin:/binÀÌ´Ù.
+ +
--with-suexec-userdir
+
»ç¿ëÀÚ µð·ºÅ丮¿¡¼­ suexec°¡ Á¢±ÙÇÒ + ¼ö ÀÖ´Â (½ÇÇàÆÄÀÏÀÌ ÀÖ´Â) ÇÏÀ§µð·ºÅ丮¸¦ ÁöÁ¤ÇÑ´Ù. + ÀÌ ¼³Á¤Àº suexec¿Í + (mod_userdirÀÌ Á¦°øÇÏ´Â) »ç¿ëÀÚº° + µð·ºÅ丮¸¦ °°ÀÌ »ç¿ëÇÒ¶§ ÇÊ¿äÇÏ´Ù. ±âº»°ªÀº + public_htmlÀÌ´Ù.
+ +
--with-suexec-uidmin
+
suexec¿¡¼­ ÁöÁ¤°¡´ÉÇÑ ÃÖ¼Ò UID¸¦ ¼³Á¤ÇÑ´Ù. + ±âº»°ªÀº 100ÀÌ´Ù.
+ +
--with-suexec-umask
+
suexec°¡ ½ÇÇàÇÏ´Â ÇÁ·Î¼¼½ºÀÇ + umask¸¦ ÁöÁ¤ÇÑ´Ù. ±âº»°ªÀº »ç¿ëÇÏ´Â ½Ã½ºÅÛÀÇ + ±âº» ¼³Á¤°ú °°´Ù.
+
+ + +
top
+
+

ȯ°æº¯¼ö

+

configureÀÇ ¼±ÅÃÀ» ¹«½ÃÇϰųª °ü·Ê¿Í ´Ù¸¥ + À̸§À̳ª À§Ä¡¿¡ ÀÖ´Â ¶óÀ̺귯¸®¿Í ÇÁ·Î±×·¥À» ãµµ·Ï µµ¿ÍÁÖ´Â + À¯¿ëÇÑ È¯°æº¯¼öµéÀÌ ÀÖ´Ù.

+ + +
+
CC
+
ÄÄÆÄÀÏ¿¡ »ç¿ëÇÒ C ÄÄÆÄÀÏ·¯ ¸í·É¾î¸¦ ÁöÁ¤ÇÑ´Ù.
+ +
CFLAGS
+
ÄÄÆÄÀ϶§ »ç¿ëÇÏ±æ ¹Ù¶ó´Â C ÄÄÆÄÀÏ·¯ ¿É¼ÇÀ» ÁöÁ¤ÇÑ´Ù.
+ +
CPP
+
»ç¿ëÇÒ C ¼±Ã³¸®±â ¸í·É¾î¸¦ ÁöÁ¤ÇÑ´Ù.
+ +
CPPFLAGS
+
C/C++ ¼±Ã³¸®±â ¿É¼Ç. ¿¹¸¦ µé¾î, Çì´õÆÄÀÏÀÌ °ü·Ê¿Í ´Þ¸® + includedir µð·ºÅ丮¿¡ ÀÖ´Ù¸é + -IincludedirÀ» »ç¿ëÇÑ´Ù.
+ +
LDFLAGS
+
¸µÄ¿ ¿É¼Ç. ¿¹¸¦ µé¾î, ¶óÀ̺귯¸®°¡ °ü·Ê¿Í ´Þ¸® + libdir µð·ºÅ丮¿¡ ÀÖ´Ù¸é + -LlibdirÀ» »ç¿ëÇÑ´Ù.
+
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/dbmmanage.html b/docs/manual/programs/dbmmanage.html new file mode 100644 index 00000000..443de47d --- /dev/null +++ b/docs/manual/programs/dbmmanage.html @@ -0,0 +1,7 @@ +URI: dbmmanage.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: dbmmanage.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/dbmmanage.html.en b/docs/manual/programs/dbmmanage.html.en new file mode 100644 index 00000000..faf787f6 --- /dev/null +++ b/docs/manual/programs/dbmmanage.html.en @@ -0,0 +1,191 @@ + + + +dbmmanage - Manage user authentication files in DBM format - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

dbmmanage - Manage user authentication files in DBM format

+
+

Available Languages:  en  | + ko 

+
+ +

dbmmanage is used to create and update the DBM format files + used to store usernames and password for basic authentication of HTTP users + via mod_authn_dbm. + Resources available from the Apache HTTP server can be restricted to just + the users listed in the files created by dbmmanage. This + program can only be used when the usernames are stored in a DBM file. To + use a flat-file database see htpasswd.

+ +

This manual page only lists the command line arguments. For details of + the directives necessary to configure user authentication in + httpd see the httpd manual, which is part of + the Apache distribution or can be found at http://httpd.apache.org/.

+
+ +
top
+
+

Synopsis

+

dbmmanage [ encoding ] + filename add|adduser|check|delete|update + username + [ encpasswd + [ group[,group...] + [ comment ] ] ]

+ +

dbmmanage filename + view [ username ]

+ +

dbmmanage filename import

+
top
+
+

Options

+
+
filename
+
The filename of the DBM format file. Usually without the extension + .db, .pag, or .dir.
+ +
username
+
The user for which the operations are performed. The username + may not contain a colon (:).
+ +
encpasswd
+
This is the already encrypted password to use for the + update and add commands. You may use a hyphen + (-) if you want to get prompted for the password, but fill + in the fields afterwards. Additionally when using the update + command, a period (.) keeps the original password + untouched.
+ +
group
+
A group, which the user is member of. A groupname may not contain a + colon (:). You may use a hyphen (-) if you don't + want to assign the user to a group, but fill in the comment field. + Additionally when using the update command, a period + (.) keeps the original groups untouched.
+ +
comment
+
This is the place for your opaque comments about the user, like + realname, mailaddress or such things. The server will ignore this + field.
+
+ +

Encodings

+
+
-d
+
crypt encryption (default, except on Win32, Netware)
+ +
-m
+
MD5 encryption (default on Win32, Netware)
+ +
-s
+
SHA1 encryption
+ +
-p
+
plaintext (not recommended)
+
+ + +

Commands

+
+
add
+
Adds an entry for username to filename using the + encrypted password encpasswd. + +

dbmmanage passwords.dat add rbowen foKntnEF3KSXA

+
+ +
adduser
+
Asks for a password and then adds an entry for username to + filename. + +

dbmmanage passwords.dat adduser krietz

+
+ +
check
+
Asks for a password and then checks if username is in + filename and if it's password matches the specified one. + +

dbmmanage passwords.dat check rbowen

+
+ +
delete
+
Deletes the username entry from filename. + +

dbmmanage passwords.dat delete rbowen

+
+ +
import
+
Reads username:password entries + (one per line) from STDIN and adds them to + filename. The passwords already have to be crypted.
+ +
update
+
Same as the adduser command, except that it makes + sure username already exists in filename. + +

dbmmanage passwords.dat update rbowen

+
+ +
view
+
Just displays the contents of the DBM file. If you specify a + username, it displays the particular record only. + +

dbmmanage passwords.dat view

+
+
+ +
top
+
+

Bugs

+

One should be aware that there are a number of different DBM file formats + in existence, and with all likelihood, libraries for more than one format + may exist on your system. The three primary examples are SDBM, NDBM, the GNU + project's GDBM, and Berkeley DB 2. Unfortunately, all these libraries use + different file formats, and you must make sure that the file format used + by filename is the same format that dbmmanage + expects to see. dbmmanage currently has no way of determining + what type of DBM file it is looking at. If used against the wrong format, + will simply return nothing, or may create a different DBM file with a + different name, or at worst, it may corrupt the DBM file if you were + attempting to write to it.

+ +

dbmmanage has a list of DBM format preferences, defined by + the @AnyDBM::ISA array near the beginning of the program. Since + we prefer the Berkeley DB 2 file format, the order in which + dbmmanage will look for system libraries is Berkeley DB 2, + then NDBM, then GDBM and then SDBM. The first library found will be the + library dbmmanage will attempt to use for all DBM file + transactions. This ordering is slightly different than the standard + @AnyDBM::ISA ordering in Perl, as well as the ordering used by + the simple dbmopen() call in Perl, so if you use any other + utilities to manage your DBM files, they must also follow this preference + ordering. Similar care must be taken if using programs in other languages, + like C, to access these files.

+ +

One can usually use the file program supplied with most + Unix systems to see what format a DBM file is in.

+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/dbmmanage.html.ko.euc-kr b/docs/manual/programs/dbmmanage.html.ko.euc-kr new file mode 100644 index 00000000..a02f2f24 --- /dev/null +++ b/docs/manual/programs/dbmmanage.html.ko.euc-kr @@ -0,0 +1,172 @@ + + + +dbmmanage - DBM Çü½ÄÀÇ »ç¿ëÀÚÀÎÁõ ÆÄÀÏÀ» °ü¸®ÇÑ´Ù - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

dbmmanage - DBM Çü½ÄÀÇ »ç¿ëÀÚÀÎÁõ ÆÄÀÏÀ» °ü¸®ÇÑ´Ù

+
+

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

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

dbmmanage´Â HTTP basic authentication¿¡ + »ç¿ëÇÒ »ç¿ëÀÚ¸í°ú ¾ÏÈ£¸¦ ÀúÀåÇÏ´Â DBMÇü½ÄÀÇ ÆÄÀÏÀ» ¸¸µé°í + ¼öÁ¤ÇÑ´Ù. ¾ÆÆÄÄ¡ À¥¼­¹ö´Â ÀÚ¿øÀ» dbmmanage·Î + ¸¸µç ÆÄÀÏ¿¡ ±â·ÏÇÑ »ç¿ëÀÚ¿¡°Ô¸¸ º¸¿©ÁÙ ¼ö ÀÖ´Ù. »ç¿ëÀÚ¸íÀÌ + DBM ÆÄÀÏ¿¡ ±â·ÏµÇÀÖÀ»¶§¸¸ ÀÌ ÇÁ·Î±×·¥À» »ç¿ëÇÒ ¼ö ÀÖ´Ù. + ÀϹÝÆÄÀÏÀ» µ¥ÀÌÅͺ£À̽º·Î »ç¿ëÇÏ·Á¸é htpasswd¸¦ Âü°íÇ϶ó.

+ +

ÀÌ manpage´Â ¸í·ÉÇà ¿É¼Ç¸¸À» ¼³¸íÇÑ´Ù. httpd¿¡¼­ »ç¿ëÀÚÀÎÁõÀ» ¼³Á¤ÇÏ´Â Áö½Ã¾î¿¡ + ´ëÇÑ ¼³¸íÀº ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡ Æ÷ÇÔµÇÀÖ°í http://httpd.apache.org/¿¡¼­µµ + º¼ ¼ö ÀÖ´Â ¾ÆÆÄÄ¡ ¼³¸í¼­¸¦ Âü°íÇ϶ó.

+
+ +
top
+
+

°³¿ä

+

dbmmanage [ encoding ] + filename add|adduser|check|delete|update + username + [ encpasswd + [ group[,group...] + [ comment ] ] ]

+ +

dbmmanage filename + view [ username ]

+ +

dbmmanage filename import

+
top
+
+

¿É¼Ç

+
+
filename
+
DBMÇü½Ä ÆÄÀÏÀÇ ÆÄÀϸí. º¸Åë .db, + .pag, .dir È®ÀåÀÚ¸¦ »«´Ù.
+ +
username
+
ÀÛ¾÷ÇÒ »ç¿ëÀÚ¸í. username¿¡ ÄÝ·Ð(:)À» + »ç¿ëÇÒ ¼ö ¾ø´Ù.
+ +
encpasswd
+
update³ª add ¸í·É¿¡ »ç¿ëÇÒ + ÀÌ¹Ì ¾ÏȣȭµÈ ¾ÏÈ£ÀÌ´Ù. ¾ÏÈ£¸¦ ³ªÁß¿¡ ÁöÁ¤ÇÏ°í ½ÍÀº °æ¿ì + »©±â±âÈ£(-)¸¦ »ç¿ëÇÑ´Ù. ¶Ç, update + ¸í·ÉÀ» »ç¿ëÇÒ¶§ ¸¶Ä§Ç¥(.)¸¦ »ç¿ëÇÏ¸é ¿ø·¡ + ¾ÏÈ£¸¦ ±×´ë·Î µÐ´Ù.
+ +
group
+
»ç¿ëÀÚ°¡ ¼ÓÇÑ ±×·ì. ±×·ì¸í¿¡ ÄÝ·Ð(:)À» + »ç¿ëÇÒ ¼ö ¾ø´Ù. »ç¿ëÀÚ¸¦ ±×·ì¿¡ Ãß°¡ÇÏÁö´Â ¾ÊÁö¸¸ ¼³¸í¶õÀ» + ä¿ì°í ½Í´Ù¸é »©±â±âÈ£(-)¸¦ »ç¿ëÇÑ´Ù. ¶Ç, + update ¸í·ÉÀ» »ç¿ëÇÒ¶§ ¸¶Ä§Ç¥(.)¸¦ + »ç¿ëÇÑ´Ù¸é ¿ø·¡ ±×·ìÀ» ±×´ë·Î µÐ´Ù.
+ +
comment
+
½ÇÁ¦ À̸§, ¸ÞÀÏ ÁÖ¼Ò µî »ç¿ëÀÚ¿¡ ´ëÇÑ ¼³¸íÀ» Àû´Â ¶õÀÌ´Ù. + ¼­¹ö´Â ÀÌ Ç׸ñÀ» ¹«½ÃÇÑ´Ù.
+
+ +

ÀÎÄÚµù

+
+
-d
+
crypt ¾Ïȣȭ (Win32³ª Netware°¡ ¾Æ´Ï¶ó¸é ±âº»°ª)
+ +
-m
+
MD5 ¾Ïȣȭ (Win32°ú Netware¿¡¼­ ±âº»°ª)
+ +
-s
+
SHA1 ¾Ïȣȭ
+ +
-p
+
¾ÏÈ£¸¦ ±×´ë·Î ±â·Ï (ÃßõÇÏÁö ¾ÊÀ½)
+
+ + +

¸í·É

+
+
add
+
¾ÏȣȭµÈ ¾ÏÈ£ encpasswd¸¦ »ç¿ëÇÏ¿© + filename¿¡ username Ç׸ñÀ» Ãß°¡ÇÑ´Ù.
+ +
adduser
+
¾ÏÈ£¸¦ ¹°¾îº¸°í filename¿¡ + username Ç׸ñÀ» Ãß°¡ÇÑ´Ù.
+ +
check
+
¾ÏÈ£¸¦ ¹°¾îº»ÈÄ filename¿¡ + usernameÀÌ ÀÖ°í ¾ÏÈ£°¡ ÀÏÄ¡ÇÏ´ÂÁö °Ë»çÇÑ´Ù.
+ +
delete
+
filename¿¡¼­ username Ç׸ñÀ» + »èÁ¦ÇÑ´Ù.
+ +
import
+
STDIN¿¡¼­ + username:password Ç׸ñÀ» + (ÇÑÁÙ¿¡ Çϳª¾¿) Àо filename¿¡ Ãß°¡ÇÑ´Ù. + ¾ÏÈ£´Â ÀÌ¹Ì ¾ÏȣȭµÇÀÖ¾î¾ß ÇÑ´Ù.
+ +
update
+
adduser ¸í·É°ú ºñ½ÁÇÏÁö¸¸, + filename¿¡ ÀÌ¹Ì usernameÀÌ ÀÖ´ÂÁö + È®ÀÎÇÑ´Ù.
+ +
view
+
DBM ÆÄÀÏ ³»¿ëÀ» Ãâ·ÂÇÑ´Ù. usernameÀ» + ÁöÁ¤Çϸé ƯÁ¤ Ç׸ñ¸¸À» Ãâ·ÂÇÑ´Ù.
+
+ +
top
+
+

¹ö±×

+

¿©·¯ ´Ù¸¥ DBM ÆÄÀÏÇü½ÄµéÀÌ ÀÖ°í ´ç½ÅÀÇ ½Ã½ºÅÛ¿¡ ¿©·¯ + Çü½Ä¿¡ ´ëÇÑ ºñ½ÁÇÑ ¶óÀ̺귯¸®µéÀÌ ÀÖÀ½À» ÁÖÀÇÇØ¾ß ÇÑ´Ù. + °¡Àå ´ëÇ¥ÀûÀÎ ³×°¡Áö°¡ SDBM, NDBM, GNU ÇÁ·ÎÁ§Æ®ÀÇ GDBM, + Berkeley DB 2ÀÌ´Ù. ºÒÇàÈ÷µµ ÀÌ ¶óÀ̺귯¸®µéÀº ¸ðµÎ ´Ù¸¥ + ÆÄÀÏÇü½ÄÀ» »ç¿ëÇÑ´Ù. ±×·¡¼­ filenameÀÌ »ç¿ëÇÏ´Â + ÆÄÀÏÇü½ÄÀÌ dbmmanage°¡ ¿øÇÏ´Â Çü½Ä°ú °°ÀºÁö + È®ÀÎÇØ¾ß ÇÑ´Ù. dbmmanage´Â DBM ÆÄÀÏÀÇ Çü½ÄÀ» + ¾Ë¾Æ³»Áö ¸øÇÑ´Ù. ´Ù¸¥ Çü½ÄÀ» »ç¿ëÇÏ¸é ¾Æ¹«Àϵµ ÇÏÁö ¾Ê°Å³ª, + ´Ù¸§ À̸§ÀÇ DBM ÆÄÀÏÀ» ¸¸µé°Å³ª, ÃÖ¾ÇÀÇ °æ¿ì ÆÄÀÏÀ» ±â·ÏÇÏ¿© + DBM ÆÄÀÏÀ» ¸ÁÄ¥ ¼ö ÀÖ´Ù.

+ +

dbmmanage ÇÁ·Î±×·¥ ¾ÕºÎºÐ¿¡ ÀÖ´Â + @AnyDBM::ISA ¹è¿­ÀÌ DBMÇü½Ä ¼±È£¼ø¼­ÀÌ´Ù. + ¿ì¸®´Â Berkeley DB 2 ÆÄÀÏÇü½ÄÀ» ¼±È£ÇϹǷΠ+ dbmmanage°¡ ½Ã½ºÅÛ ¶óÀ̺귯¸®¸¦ ã´Â ¼ø¼­´Â + Berkeley DB 2, NDBM, GDBM, SDBM ¼øÀÌ´Ù. dbmmanage´Â + Á¦ÀÏ ¸ÕÀú ãÀº ¶óÀ̺귯¸®¸¦ »ç¿ëÇÏ¿© ¸ðµç DBM ÆÄÀÏ ÀÛ¾÷À» + ÇÑ´Ù. ÀÌ ¼ø¼­´Â PerlÀÇ °£´ÜÇÑ dbmopen() È£ÃâÀÌ + »ç¿ëÇÏ´Â ¼ø¼­³ª PerlÀÇ Ç¥ÁØ @AnyDBM::ISA ¼ø¼­¿Í + Á¶±Ý ´Ù¸£´Ù. ±×·¡¼­ ´Ù¸¥ µµ±¸¸¦ »ç¿ëÇÏ¿© DBM ÆÄÀÏÀ» °ü¸®ÇÑ´Ù¸é + ÀÌ ¼ø¼­¸¦ µû¶ó¾ß ÇÑ´Ù. C¿Í °°ÀÌ ´Ù¸¥ ¾ð¾î·Î ÀÛ¼ºÇÑ ÇÁ·Î±×·¥À» + »ç¿ëÇÏ¿© ÆÄÀÏÀ» ´Ù·ç´Â °æ¿ì¿¡µµ ¸¶Âù°¡Áö´Ù.

+ +

´ëºÎºÐÀÇ À¯´Ð½º ½Ã½ºÅÛ¿¡¼­ file ÇÁ·Î±×·¥À¸·Î + DBM ÆÄÀÏÇü½ÄÀ» È®ÀÎÇÒ ¼ö ÀÖ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/htcacheclean.html b/docs/manual/programs/htcacheclean.html new file mode 100644 index 00000000..454c0046 --- /dev/null +++ b/docs/manual/programs/htcacheclean.html @@ -0,0 +1,7 @@ +URI: htcacheclean.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: htcacheclean.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/htcacheclean.html.en b/docs/manual/programs/htcacheclean.html.en new file mode 100644 index 00000000..a56ccaf9 --- /dev/null +++ b/docs/manual/programs/htcacheclean.html.en @@ -0,0 +1,120 @@ + + + +htcacheclean - Clean up the disk cache - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

htcacheclean - Clean up the disk cache

+
+

Available Languages:  en  | + ko 

+
+ +

htcacheclean is used to keep the size of + mod_disk_cache's storage within a certain limit. This + tool can run either manually or in daemon mode. When running in + daemon mode, it sleeps in the background and checks the cache directories + at regular intervals for cached content to be removed. You can stop the daemon + cleanly by sending it a TERM or INT signal.

+
+ +
top
+
+

Synopsis

+

htcacheclean + [ -D ] + [ -v ] + [ -t ] + [ -r ] + [ -n ] + -ppath + -llimit

+ +

htcacheclean -b + [ -n ] + [ -t ] + [ -i ] + -dinterval + -ppath + -llimit

+
top
+
+

Options

+
+
-dinterval
+
Daemonize and repeat cache cleaning every interval minutes. + This option is mutually exclusive with the -D, -v + and -r options. To shutdown the daemon cleanly, just send it + a SIGTERM or SIGINT.
+ +
-D
+
Do a dry run and don't delete anything. This option is mutually + exclusive with the -d option.
+ +
-v
+
Be verbose and print statistics. This option is mutually exclusive + with the -d option.
+ +
-r
+
Clean thoroughly. This assumes that the Apache web server is + not running (otherwise you may get garbage in the cache). This option + is mutually exclusive with the -d option and implies + the -t option.
+ +
-n
+
Be nice. This causes slower processing in favour of other + processes. htcacheclean will sleep from time to time + so that (a) the disk IO will be delayed and (b) the kernel can schedule + other processes in the meantime.
+ +
-t
+
Delete all empty directories. By default only cache files are + removed, however with some configurations the large number of + directories created may require attention. If your configuration + requires a very large number of directories, to the point that + inode or file allocation table exhaustion may become an issue, use + of this option is advised.
+ +
-ppath
+
Specify path as the root directory of the disk cache. This + should be the same value as specified with the CacheRoot directive.
+ +
-llimit
+
Specify limit as the total disk cache size limit. The value + is expressed in bytes by default (or attaching B to the + number). Attach K for Kbytes or M for + MBytes.
+ +
-i
+
Be intelligent and run only when there was a modification of the disk + cache. This option is only possible together with the -d + option.
+
+
top
+
+

Exit Status

+

htcacheclean returns a zero status ("true") if all + operations were successful, 1 otherwise.

+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/htcacheclean.html.ko.euc-kr b/docs/manual/programs/htcacheclean.html.ko.euc-kr new file mode 100644 index 00000000..ea2cfc0c --- /dev/null +++ b/docs/manual/programs/htcacheclean.html.ko.euc-kr @@ -0,0 +1,113 @@ + + + +htcacheclean - µð½ºÅ© ij½¬¸¦ û¼ÒÇÑ´Ù - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

htcacheclean - µð½ºÅ© ij½¬¸¦ û¼ÒÇÑ´Ù

+
+

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

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

htcachecleanÀº mod_disk_cache°¡ + »ç¿ëÇÏ´Â ÀúÀå¼Ò ¿ë·®À» ÀÏÁ¤ Çѵµ·Î À¯ÁöÇÑ´Ù. ÀÌ µµ±¸´Â Á÷Á¢ + ½ÇÇàÇϰųª µ¥¸ó(daemon)À¸·Î ½ÇÇàÇÒ ¼ö ÀÖ´Ù. ÇÁ·Î±×·¥À» µ¥¸óÀ¸·Î + ½ÇÇàÇÏ¸é ¹é±×¶ó¿îµå¿¡¼­ ÀáÀÚ°í ÀÖ´Ù°¡ ÀÏÁ¤ ÁÖ±â·Î ij½¬ + µð·ºÅ丮¿¡¼­ Áö¿ï °ÍÀÌ ÀÖ´ÂÁö °Ë»çÇÑ´Ù. µ¥¸ó¿¡°Ô TERMÀ̳ª + INT ½Ã±×³ÎÀ» º¸³»¸é ¾ÈÀüÇÏ°Ô Á¾·áÇÑ´Ù.

+
+ +
top
+
+

°³¿ä

+

htcacheclean + [ -D ] + [ -v ] + [ -r ] + [ -n ] + -ppath + -llimit

+ +

htcacheclean -b + [ -n ] + [ -i ] + -dinterval + -ppath + -llimit

+
top
+
+

¿É¼Ç

+
+
-dinterval
+
µ¥¸óÀ¸·Î ½ÇÇàÇÏ¿© interval ºÐ¸¶´Ù ij½¬¸¦ + û¼ÒÇÑ´Ù. ÀÌ ¿É¼ÇÀº -D, -v, + -r ¿É¼Ç°ú ÇÔ²² »ç¿ëÇÒ ¼ö ¾ø´Ù. µ¥¸óÀ» ¾ÈÀüÇÏ°Ô + Á¾·áÇÏ·Á¸é µ¥¸ó¿¡°Ô SIGTERM ȤÀº + SIGINT ½Ã±×³ÎÀ» º¸³»¸é µÈ´Ù.
+ +
-D
+
°Ë»ç¸¸ ÇÏ°í ½ÇÁ¦ ¾Æ¹«°Íµµ Áö¿ìÁö ¾Ê´Â´Ù. ÀÌ ¿É¼ÇÀº + -d ¿É¼Ç°ú ÇÔ²² »ç¿ëÇÒ ¼ö ¾ø´Ù.
+ +
-v
+
ÀÚ¼¼ÇÑ Åë°è¸¦ Ãâ·ÂÇÑ´Ù. ÀÌ ¿É¼ÇÀº -d ¿É¼Ç°ú + ÇÔ²² »ç¿ëÇÒ ¼ö ¾ø´Ù.
+ +
-r
+
¿ÏÀüÈ÷ û¼ÒÇÑ´Ù. ¾ÆÆÄÄ¡ À¥¼­¹ö°¡ µ¿ÀÛÇÏÁö ¾Ê´Â´Ù°í °¡Á¤ÇÑ´Ù + (¸¸¾à µ¿ÀÛÇÑ´Ù¸é ij½¬¿¡ ÀÌ»óÇÑ °ªÀÌ ÀúÀåµÈ´Ù). ÀÌ ¿É¼ÇÀº + -d ¿É¼Ç°ú ÇÔ²² »ç¿ëÇÒ ¼ö ¾ø´Ù.
+ +
-n
+
Ä£ÀýÇÏ°Ô(nice) µ¿ÀÛÇÑ´Ù. ´Ù¸¥ ÇÁ·Î¼¼½º¸¦ À§ÇØ ´À¸®°Ô + µ¿ÀÛÇÑ´Ù. htcacheclean°¡ ÀÚÁÖ ÀáÀ» ÀڰԵǿ© + (1) µð½ºÅ© ÀÔÃâ·ÂÀÌ Áö¿¬µÇ°í (2) ±×µ¿¾È Ä¿³ÎÀº ´Ù¸¥ ÇÁ·Î¼¼½º¸¦ + ½ºÄÉÁÙÇÒ ¼ö ÀÖ´Ù.
+ +
-ppath
+
path¸¦ µð½ºÅ© ij½¬ÀÇ ÃÖ»óÀ§ µð·ºÅ丮·Î ÁöÁ¤ÇÑ´Ù. + CacheRoot + Áö½Ã¾î¿¡ »ç¿ëÇÑ °ª°ú µ¿ÀÏÇÑ °ªÀ» »ç¿ëÇØ¾ß ÇÑ´Ù.
+ +
-llimit
+
Àüü µð½ºÅ© ij½¬ ¿ë·® Á¦ÇÑÀ» limit·Î Á¦ÇÑÇÑ´Ù. + °ªÀº ±âº»ÀûÀ¸·Î (ȤÀº ¼ýÀÚ¿¡ B¸¦ ºÙÀ̸é) ¹ÙÀÌÆ® + ´ÜÀ§ÀÌ´Ù. ų·Î¹ÙÀÌÆ®´Â K¸¦, ¸Þ°¡¹ÙÀÌÆ®´Â + MÀ» µÚ¿¡ ºÙÀδÙ.
+ +
-i
+
Áö´ÉÀûÀ¸·Î µð½ºÅ© ij½¬°¡ º¯°æµÈ °æ¿ì¿¡¸¸ µ¿ÀÛÇÑ´Ù. ÀÌ + ¿É¼ÇÀº -d ¿É¼Ç°ú ÇÔ²²¸¸ »ç¿ëÇÒ ¼ö ÀÖ´Ù.
+
+
top
+
+

Á¾·áÄÚµå

+

htcacheclean´Â ¸ðµç ÀÛ¾÷ÀÌ ¼º°øÇÑ °æ¿ì¿¡ + ("Âü") Á¾·áÄÚµå 0À» ¹ÝȯÇÏ°í, ½ÇÆÐÇÑ °æ¿ì¿¡´Â 1À» + ¹ÝȯÇÑ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/htdbm.html b/docs/manual/programs/htdbm.html new file mode 100644 index 00000000..ad1f2a28 --- /dev/null +++ b/docs/manual/programs/htdbm.html @@ -0,0 +1,3 @@ +URI: htdbm.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/programs/htdbm.html.en b/docs/manual/programs/htdbm.html.en new file mode 100644 index 00000000..08cbff51 --- /dev/null +++ b/docs/manual/programs/htdbm.html.en @@ -0,0 +1,281 @@ + + + +htdbm - Manipulate DBM password databases - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

htdbm - Manipulate DBM password databases

+
+

Available Languages:  en 

+
+ +

htdbm is used to manipulate the DBM format files used to + store usernames and password for basic authentication of HTTP users via + mod_auth_dbm. See the dbmmanage + documentation for more information about these DBM files.

+
+ +
top
+
+

Synopsis

+

htdbm + [ -TDBTYPE ] + [ -c ] + [ -m | + -d | + -p | + -s ] + [ -t ] + [ -v ] + [ -x ] + filename username

+ +

htdbm -b + [ -TDBTYPE ] + [ -c ] + [ -m | + -d | + -p | + -s ] + [ -t ] + [ -v ] + filename username password

+ +

htdbm -n + [ -c ] + [ -m | + -d | + -p | + -s ] + [ -t ] + [ -v ] + username

+ +

htdbm -nb + [ -c ] + [ -m | + -d | + -p | + -s ] + [ -t ] + [ -v ] + username password

+ +

htdbm -v + [ -TDBTYPE ] + [ -c ] + [ -m | + -d | + -p | + -s ] + [ -t ] + [ -v ] + filename username

+ +

htdbm -vb + [ -TDBTYPE ] + [ -c ] + [ -m | + -d | + -p | + -s ] + [ -t ] + [ -v ] + filename username password

+ +

htdbm -x + [ -TDBTYPE ] + [ -m | + -d | + -p | + -s ] + filename username

+ +

htdbm -l + [ -TDBTYPE ] +

+
top
+
+

Options

+
+
-b
+
Use batch mode; i.e., get the password from the command line + rather than prompting for it. This option should be used with extreme care, + since the password is clearly visible on the command + line.
+ +
-c
+
Create the passwdfile. If passwdfile already + exists, it is rewritten and truncated. This option cannot be combined with + the -n option.
+ +
-n
+
Display the results on standard output rather than updating a + database. This option changes the syntax of the command line, since the + passwdfile argument (usually the first one) is omitted. It + cannot be combined with the -c option.
+ +
-m
+
Use MD5 encryption for passwords. On Windows, Netware and TPF, this is + the default.
+ +
-d
+
Use crypt() encryption for passwords. The default on all + platforms but Windows, Netware and TPF. Though possibly supported by + htdbm on all platforms, it is not supported by the + httpd server on Windows, Netware and TPF.
+ +
-s
+
Use SHA encryption for passwords. Facilitates migration from/to Netscape + servers using the LDAP Directory Interchange Format (ldif).
+ +
-p
+
Use plaintext passwords. Though htdbm will support + creation on all platforms, the httpd daemon will + only accept plain text passwords on Windows, Netware and TPF.
+ +
-l
+
Print each of the usernames and comments from the database on + stdout.
+ +
-t
+
Interpret the final parameter as a comment. When this option is + specified, an additional string can be appended to the command line; this + string will be stored in the "Comment" field of the database, associated + with the specified username.
+ +
-v
+
Verify the username and password. The program will print a message + indicating whether the supplied password is valid. If the password is + invalid, the program exits with error code 3.
+ +
-x
+
Delete user. If the username exists in the specified DBM file, it + will be deleted.
+ +
filename
+
The filename of the DBM format file. Usually without the extension + .db, .pag, or .dir. If + -c is given, the DBM file is created if it does not already + exist, or updated if it does exist.
+ +
username
+
The username to create or update in passwdfile. If + username does not exist in this file, an entry is added. If it + does exist, the password is changed.
+ +
password
+
The plaintext password to be encrypted and stored in the DBM file. + Used only with the -b flag.
+ +
-TDBTYPE
+
Type of DBM file (SDBM, GDBM, DB, or "default").
+
+
top
+
+

Bugs

+

One should be aware that there are a number of different DBM file + formats in existence, and with all likelihood, libraries for more than + one format may exist on your system. The three primary examples are + SDBM, NDBM, GNU GDBM, and Berkeley/Sleepycat DB 2/3/4. Unfortunately, + all these libraries use different file formats, and you must make sure + that the file format used by filename is the same format that + htdbm expects to see. htdbm currently has + no way of determining what type of DBM file it is looking at. If used + against the wrong format, will simply return nothing, or may create a + different DBM file with a different name, or at worst, it may corrupt + the DBM file if you were attempting to write to it.

+ +

One can usually use the file program supplied with most + Unix systems to see what format a DBM file is in.

+
top
+
+

Exit Status

+

htdbm returns a zero status ("true") if the username and + password have been successfully added or updated in the DBM File. + htdbm returns 1 if it encounters some problem + accessing files, 2 if there was a syntax problem with the + command line, 3 if the password was entered interactively and + the verification entry didn't match, 4 if its operation was + interrupted, 5 if a value is too long (username, filename, + password, or final computed record), 6 if the username + contains illegal characters (see the Restrictions + section), and 7 if the file is not a valid DBM password + file.

+
top
+
+

Examples

+

+ htdbm /usr/local/etc/apache/.htdbm-users jsmith +

+ +

Adds or modifies the password for user jsmith. The user + is prompted for the password. If executed on a Windows system, the password + will be encrypted using the modified Apache MD5 algorithm; otherwise, the + system's crypt() routine will be used. If the file does not + exist, htdbm will do nothing except return an error.

+ +

+ htdbm -c /home/doe/public_html/.htdbm jane +

+ +

Creates a new file and stores a record in it for user jane. + The user is prompted for the password. If the file exists and cannot be + read, or cannot be written, it is not altered and htdbm + will display a message and return an error status.

+ +

+ htdbm -mb /usr/web/.htdbm-all jones Pwd4Steve +

+ +

Encrypts the password from the command line (Pwd4Steve) + using the MD5 algorithm, and stores it in the specified file.

+
top
+
+

Security Considerations

+

Web password files such as those managed by htdbm should + not be within the Web server's URI space -- that is, they should + not be fetchable with a browser.

+ +

The use of the -b option is discouraged, since when it is + used the unencrypted password appears on the command line.

+
top
+
+

Restrictions

+

On the Windows and MPE platforms, passwords encrypted with + htdbm are limited to no more than 255 + characters in length. Longer passwords will be truncated to 255 + characters.

+ +

The MD5 algorithm used by htdbm is specific to the Apache + software; passwords encrypted using it will not be usable with other Web + servers.

+ +

Usernames are limited to 255 bytes and may not include the + character :.

+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/htdigest.html b/docs/manual/programs/htdigest.html new file mode 100644 index 00000000..bb29be39 --- /dev/null +++ b/docs/manual/programs/htdigest.html @@ -0,0 +1,7 @@ +URI: htdigest.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: htdigest.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/htdigest.html.en b/docs/manual/programs/htdigest.html.en new file mode 100644 index 00000000..e050f2f3 --- /dev/null +++ b/docs/manual/programs/htdigest.html.en @@ -0,0 +1,72 @@ + + + +htdigest - manage user files for digest authentication - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

htdigest - manage user files for digest authentication

+
+

Available Languages:  en  | + ko 

+
+ +

htdigest is used to create and update the flat-files used + to store usernames, realm and password for digest authentication of HTTP + users. Resources available from the Apache HTTP server can be restricted + to just the users listed in the files created by htdigest.

+ +

This manual page only lists the command line arguments. For details of + the directives necessary to configure digest authentication in + httpd see the Apache manual, which is part + of the Apache distribution or can be found at + http://httpd.apache.org/.

+
+ +
top
+
+

Synopsis

+

htdigest [ -c ] + passwdfile realm username

+
top
+
+

Options

+
+
-c
+
Create the passwdfile. If passwdfile already + exists, it is deleted first.
+ +
passwdfile
+
Name of the file to contain the username, realm and password. If + -c is given, this file is created if it does not already + exist, or deleted and recreated if it does exist.
+ +
realm
+
The realm name to which the user name belongs.
+ +
username
+
The user name to create or update in passwdfile. If + username does not exist is this file, an entry is added. If it + does exist, the password is changed.
+
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/htdigest.html.ko.euc-kr b/docs/manual/programs/htdigest.html.ko.euc-kr new file mode 100644 index 00000000..4d23e906 --- /dev/null +++ b/docs/manual/programs/htdigest.html.ko.euc-kr @@ -0,0 +1,75 @@ + + + +htdigest - digest authentication¿¡ »ç¿ëÇÒ »ç¿ëÀÚÆÄÀÏÀ» +°ü¸®ÇÑ´Ù - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

htdigest - digest authentication¿¡ »ç¿ëÇÒ »ç¿ëÀÚÆÄÀÏÀ» +°ü¸®ÇÑ´Ù

+
+

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

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

htdigest´Â HTTP »ç¿ëÀÚÀÇ digest authentication¿¡ + »ç¿ëÇÒ »ç¿ëÀÚ¸í, ¿µ¿ª, ¾ÏÈ£¸¦ ÀúÀåÇÏ´Â ÀϹÝÆÄÀÏÀ» ¸¸µé°í + ¼öÁ¤ÇÑ´Ù. ¾ÆÆÄÄ¡ À¥¼­¹ö´Â ÀÚ¿øÀ» htdigest·Î + ¸¸µç ÆÄÀÏ¿¡ ±â·ÏÇÑ »ç¿ëÀÚ¿¡°Ô¸¸ º¸¿©ÁÙ ¼ö ÀÖ´Ù.

+ +

ÀÌ manpage´Â ¸í·ÉÇà ¿É¼Ç¸¸À» ¼³¸íÇÑ´Ù. httpd¿¡¼­ digest authenticationÀ» + ¼³Á¤ÇÏ´Â Áö½Ã¾î¿¡ ´ëÇÑ ¼³¸íÀº ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡ Æ÷ÇÔµÇÀÖ°í + http://httpd.apache.org/¿¡¼­µµ + º¼ ¼ö ÀÖ´Â ¾ÆÆÄÄ¡ ¼³¸í¼­¸¦ Âü°íÇ϶ó.

+
+ +
top
+
+

°³¿ä

+

htdigest [ -c ] + passwdfile realm username

+
top
+
+

¿É¼Ç

+
+
-c
+
passwdfileÀ» ¸¸µç´Ù. passwdfileÀÌ + ÀÌ¹Ì ÀÖ´Ù¸é ¸ÕÀú Áö¿ì°í ¸¸µç´Ù.
+ +
passwdfile
+
»ç¿ëÀÚ¸í, ¿µ¿ª, ¾ÏÈ£¸¦ ÀúÀåÇÒ ÆÄÀϸí. -c¸¦ + °°ÀÌ »ç¿ëÇÑ °æ¿ì ÆÄÀÏÀÌ ¾ø´Ù¸é ¸¸µé°í, ÀÖ´Ù¸é ÆÄÀÏÀ» Áö¿ì°í + ´Ù½Ã ¸¸µç´Ù.
+ +
realm
+
»ç¿ëÀÚ¸íÀÌ ¼ÓÇÑ ¿µ¿ªÀ̸§.
+ +
username
+
passwdfile¿¡ ¸¸µé°Å³ª ¼öÁ¤ÇÒ »ç¿ëÀÚ¸í. ÆÄÀÏ¿¡ + usernameÀÌ ¾ø´Ù¸é Ç׸ñÀ» Ãß°¡ÇÑ´Ù. ÀÖ´Ù¸é ¾ÏÈ£¸¦ + ¼öÁ¤ÇÑ´Ù.
+
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/htpasswd.html b/docs/manual/programs/htpasswd.html new file mode 100644 index 00000000..5462afe3 --- /dev/null +++ b/docs/manual/programs/htpasswd.html @@ -0,0 +1,7 @@ +URI: htpasswd.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: htpasswd.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/htpasswd.html.en b/docs/manual/programs/htpasswd.html.en new file mode 100644 index 00000000..391d57fc --- /dev/null +++ b/docs/manual/programs/htpasswd.html.en @@ -0,0 +1,215 @@ + + + +htpasswd - Manage user files for basic authentication - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

htpasswd - Manage user files for basic authentication

+
+

Available Languages:  en  | + ko 

+
+ +

htpasswd is used to create and update the flat-files used to + store usernames and password for basic authentication of HTTP users. If + htpasswd cannot access a file, such as not being able to write + to the output file or not being able to read the file in order to update it, + it returns an error status and makes no changes.

+ +

Resources available from the Apache HTTP server can be restricted to + just the users listed in the files created by htpasswd. This + program can only manage usernames and passwords stored in a flat-file. It + can encrypt and display password information for use in other types of data + stores, though. To use a DBM database see dbmmanage.

+ +

htpasswd encrypts passwords using either a version of MD5 + modified for Apache, or the system's crypt() routine. Files + managed by htpasswd may contain both types of passwords; some + user records may have MD5-encrypted passwords while others in the same file + may have passwords encrypted with crypt().

+ +

This manual page only lists the command line arguments. For details of + the directives necessary to configure user authentication in + httpd see the Apache manual, which is part of the + Apache distribution or can be found at http://httpd.apache.org/.

+
+

See also

  • httpd
  • The scripts in support/SHA1 which come with the +distribution.
+
top
+
+

Synopsis

+

htpasswd + [ -c ] + [ -m ] + [ -D ] passwdfile username

+ +

htpasswd -b + [ -c ] + [ -m | + -d | + -p | + -s ] + [ -D ] passwdfile username + password

+ +

htpasswd -n + [ -m | + -d | + -s | + -p ] username

+ +

htpasswd -nb + [ -m | + -d | + -s | + -p ] username password

+
top
+
+

Options

+
+
-b
+
Use batch mode; i.e., get the password from the command line + rather than prompting for it. This option should be used with extreme care, + since the password is clearly visible on the command + line.
+ +
-c
+
Create the passwdfile. If passwdfile already + exists, it is rewritten and truncated. This option cannot be combined with + the -n option.
+ +
-n
+
Display the results on standard output rather than updating a file. + This is useful for generating password records acceptable to Apache for + inclusion in non-text data stores. This option changes the syntax of the + command line, since the passwdfile argument (usually the first + one) is omitted. It cannot be combined with the -c option.
+ +
-m
+
Use MD5 encryption for passwords. On Windows, Netware and TPF, this is + the default.
+ +
-d
+
Use crypt() encryption for passwords. The default on all + platforms but Windows, Netware and TPF. Though possibly supported by + htpasswd on all platforms, it is not supported by the + httpd server on Windows, Netware and TPF.
+ +
-s
+
Use SHA encryption for passwords. Facilitates migration from/to Netscape + servers using the LDAP Directory Interchange Format (ldif).
+ +
-p
+
Use plaintext passwords. Though htpasswd will support + creation on all platforms, the httpd daemon will + only accept plain text passwords on Windows, Netware and TPF.
+ +
-D
+
Delete user. If the username exists in the specified htpasswd file, it + will be deleted.
+ +
passwdfile
+
Name of the file to contain the user name and password. If + -c is given, this file is created if it does not already exist, + or rewritten and truncated if it does exist.
+ +
username
+
The username to create or update in passwdfile. If + username does not exist in this file, an entry is added. If it + does exist, the password is changed.
+ +
password
+
The plaintext password to be encrypted and stored in the file. Only + used with the -b flag.
+
+
top
+
+

Exit Status

+

htpasswd returns a zero status ("true") if the username and + password have been successfully added or updated in the + passwdfile. htpasswd returns 1 if it + encounters some problem accessing files, 2 if there was a + syntax problem with the command line, 3 if the password was + entered interactively and the verification entry didn't match, + 4 if its operation was interrupted, 5 if a value + is too long (username, filename, password, or final computed record), + 6 if the username contains illegal characters (see the + Restrictions section), and 7 + if the file is not a valid password file.

+
top
+
+

Examples

+

+ htpasswd /usr/local/etc/apache/.htpasswd-users jsmith +

+ +

Adds or modifies the password for user jsmith. The user + is prompted for the password. If executed on a Windows system, the password + will be encrypted using the modified Apache MD5 algorithm; otherwise, the + system's crypt() routine will be used. If the file does not + exist, htpasswd will do nothing except return an error.

+ +

+ htpasswd -c /home/doe/public_html/.htpasswd jane +

+ +

Creates a new file and stores a record in it for user jane. + The user is prompted for the password. If the file exists and cannot be + read, or cannot be written, it is not altered and htpasswd + will display a message and return an error status.

+ +

+ htpasswd -mb /usr/web/.htpasswd-all jones Pwd4Steve +

+ +

Encrypts the password from the command line (Pwd4Steve) + using the MD5 algorithm, and stores it in the specified file.

+
top
+
+

Security Considerations

+

Web password files such as those managed by htpasswd should + not be within the Web server's URI space -- that is, they should + not be fetchable with a browser.

+ +

The use of the -b option is discouraged, since when it is + used the unencrypted password appears on the command line.

+
top
+
+

Restrictions

+

On the Windows and MPE platforms, passwords encrypted with + htpasswd are limited to no more than 255 + characters in length. Longer passwords will be truncated to 255 + characters.

+ +

The MD5 algorithm used by htpasswd is specific to the Apache + software; passwords encrypted using it will not be usable with other Web + servers.

+ +

Usernames are limited to 255 bytes and may not include the + character :.

+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/htpasswd.html.ko.euc-kr b/docs/manual/programs/htpasswd.html.ko.euc-kr new file mode 100644 index 00000000..e4da1146 --- /dev/null +++ b/docs/manual/programs/htpasswd.html.ko.euc-kr @@ -0,0 +1,217 @@ + + + +htpasswd - basic authentication¿¡ »ç¿ëÇÒ »ç¿ëÀÚÆÄÀÏÀ» + °ü¸®ÇÑ´Ù - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

htpasswd - basic authentication¿¡ »ç¿ëÇÒ »ç¿ëÀÚÆÄÀÏÀ» + °ü¸®ÇÑ´Ù

+
+

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

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

htpasswd´Â HTTP basic authentication¿¡ »ç¿ëÇÒ + »ç¿ëÀÚ¸í°ú ¾ÏÈ£¸¦ ÀúÀåÇÏ´Â ÀϹÝÆÄÀÏÀ» »ý¼ºÇÏ°í ¼öÁ¤ÇÑ´Ù. + htpasswd°¡ ÆÄÀÏÀ» ¾²°Å³ª ÀÐÀ» ¼ö ¾ø´Ù¸é, + ¿À·ù»óŸ¦ ¹ÝȯÇÏ°í ¾Æ¹«°Íµµ ¼öÁ¤ÇÏÁö ¾Ê´Â´Ù.

+ +

¾ÆÆÄÄ¡ À¥¼­¹ö´Â ÀÚ¿øÀ» htpasswd·Î ¸¸µç ÆÄÀÏ¿¡ + ±â·ÏÇÑ »ç¿ëÀÚ¿¡°Ô¸¸ º¸¿©ÁÙ ¼ö ÀÖ´Ù. ÀÌ ÇÁ·Î±×·¥Àº »ç¿ëÀÚ¸í°ú + ¾ÏÈ£¸¦ ÀúÀåÇÏ´Â ÀÏ¹Ý ÆÄÀÏÀ» °ü¸®ÇÑ´Ù. ±×·¯³ª ´Ù¸¥ ÀÚ·áÀúÀå + ¹æ½ÄÀ» À§ÇØ ¾ÏÈ£ Á¤º¸¸¦ ¾ÏȣȭÇÏ¿© ÀúÀåÇÒ ¼ö ÀÖ´Ù. DBM + µ¥ÀÌÅͺ£À̽º¸¦ »ç¿ëÇÏ·Á¸é dbmmanage¸¦ Âü°íÇ϶ó.

+ +

htpasswd´Â ¾ÆÆÄÄ¡ ƯÀ¯ÀÇ MD5 ȤÀº ½Ã½ºÅÛÀÇ + crypt()¸¦ »ç¿ëÇÏ¿© ¾ÏÈ£¸¦ ¾ÏȣȭÇÑ´Ù. + htpasswd°¡ °ü¸®ÇÏ´Â ÆÄÀÏÀº µÎ Á¾·ùÀÇ ¾ÏÈ£¸¦ + ¸ðµÎ ÀúÀåÇÒ ¼ö ÀÖ´Ù. Áï, °°Àº ÆÄÀÏ¿¡ MD5·Î ¾ÏȣȭÇÑ ¾ÏÈ£¸¦ + »ç¿ëÇÏ´Â »ç¿ëÀÚ¿Í crypt()·Î ¾ÏȣȭÇÑ ¾ÏÈ£¸¦ + »ç¿ëÇÏ´Â »ç¿ëÀÚ Á¤º¸ ¸ðµÎ ³ª¿Ã ¼ö ÀÖ´Ù.

+ +

ÀÌ manpage´Â ¸í·ÉÇà ¿É¼Ç¸¸À» ¼³¸íÇÑ´Ù. httpd¿¡¼­ »ç¿ëÀÚÀÎÁõÀ» ¼³Á¤ÇÏ´Â Áö½Ã¾î¿¡ + ´ëÇÑ ¼³¸íÀº ¾ÆÆÄÄ¡ ¹èÆ÷º»¿¡ Æ÷ÇÔµÇÀÖ°í http://httpd.apache.org/¿¡¼­µµ + º¼ ¼ö ÀÖ´Â ¾ÆÆÄÄ¡ ¼³¸í¼­¸¦ Âü°íÇ϶ó.

+
+

Âü°í

  • httpd
  • ¹èÆ÷º»¿¡´Â SHA1À» Áö¿øÇÏ´Â ½ºÅ©¸³Æ®µµ ÀÖ´Ù.
+
top
+
+

°³¿ä

+

htpasswd + [ -c ] + [ -m ] + [ -D ] passwdfile username

+ +

htpasswd -b + [ -c ] + [ -m | + -d | + -p | + -s ] + [ -D ] passwdfile username + password

+ +

htpasswd -n + [ -m | + -d | + -s | + -p ] username

+ +

htpasswd -nb + [ -m | + -d | + -s | + -p ] username password

+
top
+
+

¿É¼Ç

+
+
-b
+
¹èÄ¡(batch) ¸ðµå¸¦ »ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î, ¾ÏÈ£¸¦ + ¹°¾îº¸Áö¾Ê°í ¸í·ÉÇà¿¡¼­ ¹Þ´Â´Ù. ¸í·ÉÇà¿¡ ¾ÏÈ£°¡ + Á÷Á¢ µå·¯³ª¹Ç·Î, ÀÌ ¿É¼ÇÀº ¸Å¿ì Á¶½ÉÇؼ­ »ç¿ëÇØ¾ß + ÇÑ´Ù.
+ +
-c
+
passwdfileÀ» ¸¸µç´Ù. passwdfileÀÌ + ÀÌ¹Ì Á¸ÀçÇÑ´Ù¸é, µ¤¾î¾´´Ù. ÀÌ ¿É¼ÇÀ» -n ¿É¼Ç°ú + °°ÀÌ »ç¿ëÇÒ ¼ö ¾ø´Ù.
+ +
-n
+
ÆÄÀÏÀ» ¼öÁ¤ÇÏÁö¾Ê°í °á°ú¸¦ Ç¥ÁØÃâ·ÂÀ¸·Î Ãâ·ÂÇÑ´Ù. + ¾ÆÆÄÄ¡°¡ ¹®¼­ÀÌ¿ÜÀÇ °÷¿¡ »ý¼ºÇÑ ¾ÏÈ£¸¦ ÀúÀåÇÒ¶§ À¯¿ëÇÏ´Ù. + (Ç×»ó ù¹ø° ¾Æ±Ô¸ÕÆ®ÀÎ) passwdfile ¾Æ±Ô¸ÕÆ®°¡ + ¾ø±â¶§¹®¿¡ ¸í·ÉÇà ¹®¹ýÀÌ ´Ù¸£´Ù. -c ¿É¼Ç°ú + °°ÀÌ »ç¿ëÇÒ ¼ö ¾ø´Ù.
+ +
-m
+
MD5¸¦ »ç¿ëÇÏ¿© ¾ÏÈ£¸¦ ¾ÏȣȭÇÑ´Ù. Windows, Netware, + TPF¿¡¼­ ±âº»°ªÀÌ´Ù.
+ +
-d
+
crypt()¸¦ »ç¿ëÇÏ¿© ¾ÏÈ£¸¦ ¾ÏȣȭÇÑ´Ù. + Windows, Netware, TPF¸¦ Á¦¿ÜÇÑ ¸ðµç Ç÷¡Æû¿¡¼­ ±âº»°ªÀÌ´Ù. + ¸ðµç Ç÷¡ÆûÀÇ htpasswd°¡ ÀÌ Çü½ÄÀ» Áö¿øÇÒ ¼ö´Â + ÀÖÁö¸¸, Windows, Netware, TPFÀÇ httpd + ¼­¹ö´Â ÀÌ Çü½ÄÀ» Áö¿øÇÏÁö ¾Ê´Â´Ù.
+ +
-s
+
¾ÏÈ£¸¦ SHA ¾ÏȣȭÇÑ´Ù. LDAP µð·ºÅ丮±³È¯Çü½Ä(ldif)À» + »ç¿ëÇÏ¿© Netscape ¼­¹ö·Î Á¤º¸¸¦ º¸³»°Å³ª °ÅÁ®¿Ã¶§ À¯¿ëÇÏ´Ù.
+ +
-p
+
¾ÏÈ£¸¦ ±×´ë·Î »ç¿ëÇÑ´Ù. ¸ðµç Ç÷¡ÆûÀÇ htpasswd°¡ + Áö¿øÇÏÁö¸¸, Windows, Netware, TPFÀÇ httpd + µ¥¸ó¸¸ÀÌ ÀÏ¹Ý ¾ÏÈ£¸¦ ¹Þ´Â´Ù.
+ +
-D
+
»ç¿ëÀÚ¸¦ »èÁ¦ÇÑ´Ù. htpasswd ÆÄÀÏ¿¡ »ç¿ëÀÚ¸íÀÌ ÀÖ´Ù¸é + »èÁ¦ÇÑ´Ù.
+ +
passwdfile
+
»ç¿ëÀÚ¸í°ú ¾ÏÈ£¸¦ ÀúÀåÇÏ´Â ÆÄÀϸí. -c¸¦ + »ç¿ëÇÑ °æ¿ì ÆÄÀÏÀÌ ¾ø´Ù¸é »õ·Î ¸¸µé°í, ÀÖ´Ù¸é µ¤¾î¾´´Ù.
+ +
username
+
passwdfile¿¡ ¸¸µé°Å³ª ¼öÁ¤ÇÒ »ç¿ëÀÚ¸í. + usernameÀÌ ÀÌ ÆÄÀÏ¿¡ ¾ø´Ù¸é Ç׸ñÀ» Ãß°¡ÇÑ´Ù. + ÀÖ´Ù¸é ¾ÏÈ£¸¦ ¼öÁ¤ÇÑ´Ù.
+ +
password
+
¾ÏȣȭÇÏ¿© ÆÄÀÏ¿¡ ÀúÀåÇÒ ¾ÏÈ£. ¿ÀÁ÷ -b + ¿É¼Ç°ú °°ÀÌ »ç¿ëÇÒ ¼ö ÀÖ´Ù.
+
+
top
+
+

Á¾·áÄÚµå

+

htpasswd´Â passwdfile¿¡ »ç¿ëÀÚ¸í°ú + ¾ÏÈ£¸¦ ¼º°øÀûÀ¸·Î Ãß°¡Çϰųª ¼öÁ¤ÇÑ °æ¿ì ("Âü") Á¾·áÄÚµå + 0À» ¹ÝȯÇÑ´Ù. htpasswd´Â ÆÄÀÏ¿¡ Á¢±ÙÇÒ¶§ ¹®Á¦°¡ + ¹ß»ýÇÑ °æ¿ì 1À», ¸í·ÉÇà Çü½ÄÀÌ À߸øµÈ °æ¿ì + 2¸¦, ÀÔ·ÂÇÑ ¾ÏÈ£¿Í È®ÀÎÂ÷ ´Ù½Ã ÀÔ·ÂÇÑ °ªÀÌ + ÀÏÄ¡ÇÏÁö ¾ÊÀº °æ¿ì 3À», ¸í·ÉÀÌ Áß´ÜµÈ °æ¿ì + 4¸¦, (»ç¿ëÀÚ¸í, ÆÄÀϸí, ¾ÏÈ£, ÃÖÁ¾ °è»ê°á°ú) + °ªÀÌ ³Ê¹« ±ä °æ¿ì 5¸¦, »ç¿ëÀÚ¸í¿¡ Çã¿ëÇÏÁö¾Ê´Â + ¹®ÀÚ°¡ Æ÷ÇÔµÈ °æ¿ì Á¦ÇÑ Àý Âü°í) + 6¸¦, ÆÄÀÏÀÌ ¿Ã¹Ù¸¥ ¾ÏÈ£ÆÄÀÏÀÌ ¾Æ´Ñ °æ¿ì + 7À» ¹ÝȯÇÑ´Ù.

+
top
+
+

¿¹Á¦

+

+ htpasswd /usr/local/etc/apache/.htpasswd-users jsmith +

+ +

»ç¿ëÀÚ jsmithÀÇ ¾ÏÈ£¸¦ Ãß°¡Çϰųª ¼öÁ¤ÇÑ´Ù. + »ç¿ëÀÚ¿¡°Ô ¾ÏÈ£¸¦ ¹°¾îº»´Ù. Windows ½Ã½ºÅÛ¿¡¼­ ½ÇÇàÇϸé + ¾ÏÈ£¸¦ ¾ÆÆÄÄ¡ ƯÀ¯ÀÇ MD5 ¾Ë°í¸®ÁòÀ» »ç¿ëÇÏ¿© ¾ÏȣȭÇÏ°í, + ¾Æ´Ï¸é ½Ã½ºÅÛÀÇ crypt() ÇÔ¼ö¸¦ »ç¿ëÇÑ´Ù. ÆÄÀÏÀÌ + ¾ø´Ù¸é htpasswd´Â ¾Æ¹« Àϵµ ÇÏÁö¾Ê°í ¿À·ù¸¦ + ³½´Ù.

+ +

+ htpasswd -c /home/doe/public_html/.htpasswd jane +

+ +

»õ·Î ÆÄÀÏÀ» ¸¸µé°í ±× ÆÄÀÏ¿¡ »ç¿ëÀÚ janeÀ» + Ãß°¡ÇÑ´Ù. »ç¿ëÀÚ¿¡°Ô ¾ÏÈ£¸¦ ¹°¾îº»´Ù. ÆÄÀÏÀÌ ÀÖÁö¸¸ Àаųª + ¾µ ¼ö ¾ø´Ù¸é, htpasswd´Â ÆÄÀÏÀ» ¼öÁ¤ÇÏÁö¾Ê°í + ¹®±¸¸¦ Ãâ·ÂÇÑÈÄ ¿À·ù»óŸ¦ ¹ÝȯÇÑ´Ù.

+ +

+ htpasswd -mb /usr/web/.htpasswd-all jones Pwd4Steve +

+ +

¸í·ÉÇàÀÇ ¾ÏÈ£(Pwd4Steve)¸¦ MD5 ¾Ë°í¸®ÁòÀ¸·Î + ¾ÏȣȭÇÏ¿© ÁöÁ¤ÇÑ ÆÄÀÏ¿¡ ÀúÀåÇÑ´Ù.

+
top
+
+

º¸¾È»ó °í·ÁÇÒ Á¡

+

htpasswd µîÀÌ °ü¸®ÇÏ´Â À¥ ¾ÏÈ£ÆÄÀÏÀÌ À¥¼­¹öÀÇ + URI °ø°£¿¡ ÀÖÀ¸¸é ¾ÈµÈ´Ù. Áï, ºê¶ó¿ìÀú°¡ ÀÌ ÆÄÀÏÀ» + º¼ ¼ö ¾ø¾î¾ß ÇÑ´Ù.

+ +

¸í·ÉÇà¿¡ ¾ÏȣȭÇÏÁö¾ÊÀº ¾ÏÈ£¸¦ »ç¿ëÇϱ⶧¹®¿¡ -b + ¿É¼ÇÀ» ÃßõÇÏÁö ¾Ê´Â´Ù.

+
top
+
+

Á¦ÇÑ

+

Windows¿Í MPE Ç÷¡ÆûÀº htpasswd°¡ ¾ÏȣȭÇÏ´Â + ¾ÏÈ£ÀÇ ±æÀ̸¦ 255 ¹®ÀÚ·Î Á¦ÇÑÇÑ´Ù. ´õ ±ä ¾ÏÈ£´Â + 255ÀÚ¿¡¼­ ©¸°´Ù.

+ +

htpasswd°¡ »ç¿ëÇÏ´Â MD5 ¾Ë°í¸®ÁòÀº ¾ÆÆÄÄ¡ + ¼ÒÇÁÆ®¿þ¾î ƯÀ¯ÀÇ °ÍÀÌ´Ù. À̸¦ »ç¿ëÇÏ¿© ¾ÏȣȭÇÑ ¾ÏÈ£¸¦ + ´Ù¸¥ À¥¼­¹ö¿¡¼­ »ç¿ëÇÒ ¼ö ¾ø´Ù.

+ +

»ç¿ëÀÚ¸íÀº 255 ¹ÙÀÌÆ®·Î Á¦Çѵǰí : + ¹®ÀÚ¸¦ Æ÷ÇÔÇÒ ¼ö ¾ø´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/httpd.html b/docs/manual/programs/httpd.html new file mode 100644 index 00000000..7d7ff916 --- /dev/null +++ b/docs/manual/programs/httpd.html @@ -0,0 +1,7 @@ +URI: httpd.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: httpd.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/httpd.html.en b/docs/manual/programs/httpd.html.en new file mode 100644 index 00000000..666bd18a --- /dev/null +++ b/docs/manual/programs/httpd.html.en @@ -0,0 +1,193 @@ + + + +httpd - Apache Hypertext Transfer Protocol Server - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

httpd - Apache Hypertext Transfer Protocol Server

+
+

Available Languages:  en  | + ko 

+
+ +

httpd is the Apache HyperText Transfer Protocol + (HTTP) server program. It is designed to be run as a standalone + daemon process. When used like this it will create a pool of + child processes or threads to handle requests.

+ +

In general, httpd should not be invoked directly, + but rather should be invoked via apachectl on Unix-based systems or as a service on Windows NT, + 2000 and XP and as + a console application on Windows 9x and ME.

+
+ +
top
+
+

Synopsis

+

httpd [ -d + serverroot ] [ -f config ] + [ -C directive ] [ -c + directive ] [ -D parameter ] + [ -e level ] [ -E + file ] + [ -k start|restart|graceful|stop|graceful-stop ] + [ -R directory ] [ -h ] + [ -l ] [ -L ] [ -S ] + [ -t ] [ -v ] [ -V ] + [ -X ] [ -M ]

+ +

On Windows systems, the + following additional arguments are available:

+ +

httpd [ -k + install|config|uninstall ] [ -n name ] + [ -w ]

+
top
+
+

Options

+ +
+
-d serverroot
+ +
Set the initial value for the ServerRoot directive to +serverroot. This can be overridden by the ServerRoot +directive in the configuration file. The default is +/usr/local/apache2.
+ +
-f config
+ +
Uses the directives in the file config on startup. If +config does not begin with a /, then it is taken to be a +path relative to the ServerRoot. The default is +conf/httpd.conf.
+ +
-k start|restart|graceful|stop|graceful-stop
+ +
Signals httpd to start, restart, or stop. See Stopping Apache for more information.
+ +
-C directive
+ +
Process the configuration directive before reading +config files.
+ +
-c directive
+ +
Process the configuration directive after reading config +files.
+ + +
-D parameter
+ +
Sets a configuration parameter which can be used with +<IfDefine> sections +in the configuration files to conditionally skip or process +commands at server startup and restart.
+ +
-e level
+ +
Sets the LogLevel to +level during server startup. This is useful for +temporarily increasing the verbosity of the error messages to find +problems during startup.
+ +
-E file
+ +
Send error messages during server startup to file.
+ +
-R directory
+ +
When the server is compiled using the SHARED_CORE +rule, this specifies the directory for the shared +object files.
+ +
-h
+ +
Output a short summary of available command line options.
+ +
-l
+ +
Output a list of modules compiled into the server. This will +not list dynamically loaded modules included using +the LoadModule directive.
+ +
-L
+ +
Output a list of directives together with expected arguments and +places where the directive is valid.
+ +
-M
+ +
Dump a list of loaded Static and Shared Modules.
+ +
-S
+ +
Show the settings as parsed from the config file (currently only +shows the virtualhost settings).
+ +
-t
+ +
Run syntax tests for configuration files only. The program +immediately exits after these syntax parsing tests with either a return code +of 0 (Syntax OK) or return code not equal to 0 (Syntax Error). If -D +DUMP_VHOSTS is also set, details of the virtual host +configuration will be printed. If -D DUMP_MODULES is +set, all loaded modules will be printed.
+ +
-v
+ +
Print the version of httpd, and then exit.
+ +
-V
+ +
Print the version and build parameters of httpd, and +then exit.
+ +
-X
+ +
Run httpd in debug mode. Only one worker will be started and the +server will not detach from the console.
+ +
+ +

The following arguments are available only on the Windows platform:

+ +
+ +
-k install|config|uninstall
+ +
Install Apache as a Windows NT service; change startup options for +the Apache service; and uninstall the Apache service.
+ +
-n name
+ +
The name of the Apache service to signal.
+ +
-w
+ +
Keep the console window open on error so that the error message can +be read.
+ +
+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/httpd.html.ko.euc-kr b/docs/manual/programs/httpd.html.ko.euc-kr new file mode 100644 index 00000000..cfd46b14 --- /dev/null +++ b/docs/manual/programs/httpd.html.ko.euc-kr @@ -0,0 +1,188 @@ + + + +httpd - ¾ÆÆÄÄ¡ ÇÏÀÌÆÛÅؽºÆ® Àü¼Û ÇÁ·ÎÅäÄÝ ¼­¹ö - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

httpd - ¾ÆÆÄÄ¡ ÇÏÀÌÆÛÅؽºÆ® Àü¼Û ÇÁ·ÎÅäÄÝ ¼­¹ö

+
+

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

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

httpd´Â ¾ÆÆÄÄ¡ ÇÏÀÌÆÛÅؽºÆ® Àü¼Û ÇÁ·ÎÅäÄÝ + (HTTP) ¼­¹ö ÇÁ·Î±×·¥ÀÌ´Ù. ÀÚü(standalone) µ¥¸ó ÇÁ·Î¼¼½º·Î + ½ÇÇàÇϵµ·Ï ¼³°èµÇ¾ú´Ù. ¿øÇÑ´Ù¸é ¿äûÀ» ó¸®ÇϱâÀ§ÇØ ÀÚ½Ä + ÇÁ·Î¼¼½º¿Í ¾²·¹µåµéÀ» ¸¸µç´Ù.

+ +

ÀϹÝÀûÀ¸·Î httpd¸¦ Á÷Á¢ ½ÇÇàÇϱ⺸´Ù´Â + À¯´Ð½º±â¹Ý ½Ã½ºÅÛ¿¡¼­´Â apachectlÀ» ÅëÇØ, 2000, XP¿¡¼­´Â + ¼­ºñ½º·Î, Windows + 9x¿Í ME¿¡¼­´Â ÄÝ¼Ö ÇÁ·Î±×·¥À¸·Î ½ÇÇàÇØ¾ß ÇÑ´Ù.

+
+ +
top
+
+

°³¿ä

+

httpd [ -d + serverroot ] [ -f config ] + [ -C directive ] [ -c + directive ] [ -D parameter ] + [ -e level ] [ -E + file ] [ -k start|restart|graceful|stop ] + [ -R directory ] [ -h ] + [ -l ] [ -L ] [ -S ] + [ -t ] [ -v ] [ -V ] + [ -X ] [ -M ]

+ +

Windows ½Ã½ºÅÛ¿¡¼­´Â + ´ÙÀ½ ¾Æ±Ô¸ÕÆ®¸¦ Ãß°¡·Î »ç¿ëÇÒ ¼ö ÀÖ´Ù:

+ +

httpd [ -k + install|config|uninstall ] [ -n name ] + [ -w ]

+
top
+
+

¿É¼Ç

+ +
+
-d serverroot
+ +
ServerRoot Áö½Ã¾îÀÇ +±âº»°ªÀ» serverroot·Î ¼³Á¤ÇÑ´Ù. ¼³Á¤ÆÄÀÏ¿¡¼­ ServerRoot +Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ÀÌ °ªÀ» ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù. ±âº»°ªÀº +/usr/local/apache2ÀÌ´Ù.
+ +
-f config
+ +
½ÃÀÛÇÒ¶§ config ÆÄÀÏ¿¡ ÀÖ´Â Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù. +config°¡ /·Î ½ÃÀÛÇÏÁö ¾ÊÀ¸¸é ServerRoot¿¡ »ó´ë°æ·ÎÀÌ´Ù. ±âº»°ªÀº +conf/httpd.confÀÌ´Ù.
+ +
-k start|restart|graceful|stop
+ +
httpd¸¦ ½ÃÀÛ, Àç½ÃÀÛ, Áß´ÜÇÑ´Ù. ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â +¾ÆÆÄÄ¡ Áß´ÜÇϱ⸦ Âü°íÇ϶ó.
+ +
-C directive
+ +
¼³Á¤ÆÄÀÏÀ» ÀбâÀü¿¡ directive Áö½Ã¾î¸¦ ó¸®ÇÑ´Ù.
+ +
-c directive
+ +
¼³Á¤ÆÄÀÏÀ» ÀбâÀü¿¡ directive Áö½Ã¾î¸¦ ó¸®ÇÑ´Ù.
+ + +
-D parameter
+ +
¼­¹ö ½ÃÀÛ È¤Àº Àç½ÃÀ۽à ¼±ÅÃÀûÀ¸·Î ¸í·É¾î¸¦ ó¸®ÇϱâÀ§ÇØ +¼³Á¤ÆÄÀÏÀÇ <IfDefine> +¼½¼Ç¿¡ »ç¿ëÇÒ parameter¸¦ ¼³Á¤ÇÑ´Ù.
+ +
-e level
+ +
¼­¹ö°¡ ½ÃÀÛÇϴµ¿¾È LogLevelÀ» +level·Î ¼³Á¤ÇÑ´Ù. ÀÌ´Â ½ÃÀÛÁß ¹®Á¦¸¦ ã±âÀ§ÇØ Àá½Ã +´õ ÀÚ¼¼ÇÑ ¿À·ù¹®À» ¾òÀ»¶§ À¯¿ëÇÏ´Ù.
+ +
-E file
+ +
¼­¹ö°¡ ½ÃÀÛÇϴµ¿¾È file·Î ¿À·ù¹®À» º¸³½´Ù.
+ +
-R directory
+ +
¼­¹ö¸¦ SHARED_CORE ±ÔÄ¢À» »ç¿ëÇÏ¿© ÄÄÆÄÀÏÇÑ +°æ¿ì °øÀ¯¿ÀºêÁ§Æ®ÆÄÀÏ directory¸¦ ÁöÁ¤ÇÑ´Ù.
+ +
-h
+ +
»ç¿ëÇÒ ¼ö ÀÖ´Â ¸í·ÉÇà ¿É¼ÇµéÀÇ ÂªÀº ¿ä¾àÀ» Ãâ·ÂÇÑ´Ù.
+ +
-l
+ +
¼­¹ö¿¡ °°ÀÌ ÄÄÆÄÀÏÇÑ ¸ðµâ ¸ñ·ÏÀ» Ãâ·ÂÇÑ´Ù. LoadModule Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© µ¿ÀûÀ¸·Î +ÀоîµéÀÌ´Â ¸ðµâÀº Ãâ·ÂÇÏÁö ¾Ê´Â´Ù.
+ +
-L
+ +
Áö½Ã¾î ¸ñ·ÏÀ» Áö½Ã¾î°¡ ¹Þ´Â ¾Æ±Ô¸ÕÆ®¿Í Áö½Ã¾î »ç¿ëÀå¼Ò¿Í +°°ÀÌ Ãâ·ÂÇÑ´Ù.
+ +
-M
+ +
ÀоîµéÀÎ Á¤Àû ¸ðµâ°ú °øÀ¯ ¸ðµâ ¸ñ·ÏÀ» Ãâ·ÂÇÑ´Ù.
+ +
-S
+ +
¼³Á¤ÆÄÀÏ¿¡¼­ ÀоîµéÀÎ ¼³Á¤À» º¸¿©ÁØ´Ù (ÇöÀç´Â °¡»óÈ£½ºÆ® +¼³Á¤¸¸À» º¸¿©ÁØ´Ù).
+ +
-t
+ +
¼³Á¤ÆÄÀÏÀÇ ¹®¹ý°Ë»ç¸¸ ÇÑ´Ù. ÇÁ·Î±×·¥Àº ¹®¹ýÀ» °Ë»çÇÑÈÄ +(¹®¹ýÀÌ ¿Ã¹Ù¸¥ °æ¿ì) 0À̳ª (¹®¹ý¿¡ ¹®Á¦°¡ ÀÖ´Â °æ¿ì) 0ÀÌ ¾Æ´Ñ +Á¾·áÄÚµå·Î Áï½Ã Á¾·áÇÑ´Ù. -D DUMP_VHOSTSÀ» +»ç¿ëÇÏ¸é °¡»óÈ£½ºÆ® ¼³Á¤À» ÀÚ¼¼È÷ Ãâ·ÂÇÑ´Ù. -D +DUMP_MODULES¸¦ »ç¿ëÇϸé ÀоîµéÀÎ ¸ðµâ +¸ñ·ÏÀ» Ãâ·ÂÇÑ´Ù.
+ +
-v
+ +
httpdÀÇ ¹öÀüÀ» Ãâ·ÂÇÏ°í Á¾·áÇÑ´Ù.
+ +
-V
+ +
httpdÀÇ ¹öÀü°ú ÄÄÆÄÀÏ ÆĶó¹ÌÅ͸¦ Ãâ·ÂÇÏ°í +Á¾·áÇÑ´Ù.
+ +
-X
+ +
µð¹ö±× »óÅ·ΠÀ¥¼­¹ö¸¦ ½ÇÇàÇÑ´Ù. ¿ÀÁ÷ ÇÑ ÇÁ·Î¼¼½º³ª ¾²·¹µå·Î¸¸ +¼­ºñ½ºÇÏ°í, ¼­¹ö´Â Äֿܼ¡¼­ ¶³¾îÁöÁö ¾Ê´Â´Ù.
+ +
+ +

´ÙÀ½ ¾Æ±Ô¸ÕÆ®´Â Windows +Ç÷¡Æû¿¡¼­¸¸ »ç¿ëÇÒ ¼ö ÀÖ´Ù:

+ +
+ +
-k install|config|uninstall
+ +
¾ÆÆÄÄ¡¸¦ Windows NT ¼­ºñ½º·Î ¼³Ä¡ÇÑ´Ù; ¾ÆÆÄÄ¡ ¼­ºñ½ºÀÇ ½ÃÀÛ +¿É¼ÇÀ» ¼öÁ¤ÇÑ´Ù; ¾ÆÆÄÄ¡ ¼­ºñ½º ¼³Ä¡¸¦ Áö¿î´Ù.
+ +
-n name
+ +
¾ÆÆÄÄ¡ ¼­ºñ½ºÀÇ name.
+ +
-w
+ +
¿À·ù°¡ ¹ß»ýÇϸé ÄܼÖâÀ» ¿­¾î¼­ ¿À·ù¹®À» º¸¿©ÁØ´Ù.
+ +
+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/httxt2dbm.html b/docs/manual/programs/httxt2dbm.html new file mode 100644 index 00000000..c6222ab2 --- /dev/null +++ b/docs/manual/programs/httxt2dbm.html @@ -0,0 +1,3 @@ +URI: httxt2dbm.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/programs/httxt2dbm.html.en b/docs/manual/programs/httxt2dbm.html.en new file mode 100644 index 00000000..925dfd97 --- /dev/null +++ b/docs/manual/programs/httxt2dbm.html.en @@ -0,0 +1,82 @@ + + + +httxt2dbm - Generate dbm files for use with RewriteMap - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

httxt2dbm - Generate dbm files for use with RewriteMap

+
+

Available Languages:  en 

+
+ +

httxt2dbm is used to generate dbm files from text input, for + use in RewriteMap with the dbm map type. +

+
+ +
top
+
+

Synopsis

+

httxt2dbm + [ -v ] + [ -f DBM_TYPE ] + -i SOURCE_TXT + -o OUTPUT_DBM +

+
top
+
+

Options

+
+
-v
+
More verbose output
+ +
-f
+
Specify the DBM type to be used for the output. If not specified, will + use the APR Default. Available types are:
+ GDBM for GDBM files
+ SDBM for SDBM files
+ DB for berkeley DB files
+ NDBM for NDBM files
+ default for the default DBM type +
+ +
-i
+
Input file from which the dbm is to be created. The file should be formated + with one record per line, of the form:
+ key value
+ See the documentation for RewriteMap for + further details of this file's format and meaning. +
+ +
-o
+
Name of the output dbm files.
+
+
top
+
+

Examples

+

+ httxt2dbm -i rewritemap.txt -o rewritemap.dbm
+ httxt2dbm -f SDBM -i rewritemap.txt -o rewritemap.dbm
+

+
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/index.html b/docs/manual/programs/index.html new file mode 100644 index 00000000..01f64142 --- /dev/null +++ b/docs/manual/programs/index.html @@ -0,0 +1,15 @@ +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: index.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R diff --git a/docs/manual/programs/index.html.en b/docs/manual/programs/index.html.en new file mode 100644 index 00000000..97dfb56f --- /dev/null +++ b/docs/manual/programs/index.html.en @@ -0,0 +1,106 @@ + + + +Server and Supporting Programs - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Server and Supporting Programs

+
+

Available Languages:  en  | + es  | + ko  | + ru 

+
+ +

This page documents all the executable programs included + with the Apache HTTP Server.

+
+
top
+
+

Index

+ +
+
httpd
+ +
Apache hypertext transfer protocol server
+ +
apachectl
+ +
Apache HTTP server control interface
+ +
ab
+ +
Apache HTTP server benchmarking tool
+ +
apxs
+ +
APache eXtenSion tool
+ +
configure
+ +
Configure the source tree
+ +
dbmmanage
+ +
Create and update user authentication files in DBM format + for basic authentication
+ +
htcacheclean
+
Clean up the disk cache
+ +
htdigest
+ +
Create and update user authentication files for digest + authentication
+ +
htdbm
+ +
Manipulate DBM password databases.
+ +
htpasswd
+ +
Create and update user authentication files for basic + authentication
+ +
httxt2dbm
+ +
Create dbm files for use with RewriteMap
+ +
logresolve
+ +
Resolve hostnames for IP-addresses in Apache + logfiles
+ +
rotatelogs
+ +
Rotate Apache logs without having to kill the server
+ +
suexec
+ +
Switch User For Exec
+ +
Other Programs
+
Support tools with no own manual page.
+
+
+
+

Available Languages:  en  | + es  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/index.html.es b/docs/manual/programs/index.html.es new file mode 100644 index 00000000..5647ef8c --- /dev/null +++ b/docs/manual/programs/index.html.es @@ -0,0 +1,102 @@ + + + +El Servidor Apache y Programas de Soporte - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

El Servidor Apache y Programas de Soporte

+
+

Idiomas disponibles:  en  | + es  | + ko  | + ru 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ +

Esta página contiene toda la documentación sobre los programas + ejecutables incluidos en el servidor Apache.

+
+
top
+
+

Índice

+ +
+
httpd
+ +
Servidor Apache del Protocolo de Transmisión de + Hipertexto (HTTP)
+ +
apachectl
+ +
Interfaz de control del servidor HTTP Apache
+ +
ab
+ +
Herramienta de benchmarking del Servidor HTTP Apache
+ +
apxs
+ +
Herramienta de Extensión de Apache
+ +
configure
+ +
Configuración de la estructura de directorios de Apache
+ +
dbmmanage
+ +
Crea y actualiza los archivos de autentificación de usuarios + en formato DBM para autentificación básica
+ +
htdigest
+ +
Crea y actualiza los ficheros de autentificación de usuarios + para autentificación tipo digest
+ +
htpasswd
+ +
Crea y actualiza los ficheros de autentificación de usuarios + para autentificación básica
+ +
logresolve
+ +
Resuelve los nombres de host para direcciones IP que estén + en los ficheros log de Apache
+ +
rotatelogs
+ +
Renueva los logs de Apache sin parar el servidor
+ +
suexec
+ +
Switch User For Exec. Programa para cambiar la identidad de + usuario con la que se ejecuta un CGI
+ +
Otros Programas
+
Herramientas de soporte sin sección propia en la + documentación.
+
+
+
+

Idiomas disponibles:  en  | + es  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/index.html.ko.euc-kr b/docs/manual/programs/index.html.ko.euc-kr new file mode 100644 index 00000000..a5485357 --- /dev/null +++ b/docs/manual/programs/index.html.ko.euc-kr @@ -0,0 +1,98 @@ + + + +¼­¹ö¿Í Áö¿ø ÇÁ·Î±×·¥ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¼­¹ö¿Í Áö¿ø ÇÁ·Î±×·¥

+
+

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

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

¾ÆÆÄÄ¡ À¥¼­¹ö¿¡ Æ÷ÇÔµÈ ÇÁ·Î±×·¥µéÀÌ´Ù.

+
+
top
+
+

¸ñ·Ï

+ +
+
httpd
+ +
¾ÆÆÄÄ¡ ÇÏÀÌÆÛÅؽºÆ® Àü¼Û ÇÁ·ÎÅäÄÝ ¼­¹ö
+ +
apachectl
+ +
¾ÆÆÄÄ¡ À¥¼­¹ö Á¶Àý ÀÎÅÍÆäÀ̽º
+ +
ab
+ +
¾ÆÆÄÄ¡ À¥¼­¹ö ¼º´É°Ë»ç µµ±¸
+ +
apxs
+ +
¾ÆÆÄÄ¡ È®Àå µµ±¸ (APache eXtenSion tool)
+ +
configure
+ +
¼Ò½º Æ®¸®¸¦ ±¸¼ºÇÑ´Ù
+ +
dbmmanage
+ +
basic authentication¿¡ »ç¿ëÇÒ DBM Çü½ÄÀÇ »ç¿ëÀÚ + ÀÎÁõÆÄÀÏÀ» ¸¸µé°í ¼öÁ¤ÇÑ´Ù
+ +
htcacheclean
+
µð½ºÅ© ij½¬¸¦ û¼ÒÇÑ´Ù
+ +
htdigest
+ +
digest authentication¿¡ »ç¿ëÇÒ »ç¿ëÀÚ ÀÎÁõÆÄÀÏÀ» + ¸¸µé°í ¼öÁ¤ÇÑ´Ù
+ +
htpasswd
+ +
basic authentication¿¡ »ç¿ëÇÒ »ç¿ëÀÚ ÀÎÁõÆÄÀÏÀ» ¸¸µé°í + ¼öÁ¤ÇÑ´Ù
+ +
logresolve
+ +
¾ÆÆÄÄ¡ ·Î±×ÆÄÀÏÀÇ IP-ÁÖ¼Ò¸¦ È£½ºÆ®¸íÀ¸·Î º¯È¯ÇÑ´Ù
+ +
rotatelogs
+ +
¼­¹ö¸¦ Á×ÀÌÁö¾Ê°í ¾ÆÆÄÄ¡ ·Î±×¸¦ ¼øȯÇÑ´Ù
+ +
suexec
+ +
½ÇÇàÀ» À§ÇØ »ç¿ëÀÚ¸¦ º¯°æÇÑ´Ù (Switch User For Exec)
+ +
´Ù¸¥ ÇÁ·Î±×·¥µé
+
manpage°¡ ¾ø´Â Áö¿ø µµ±¸µé.
+
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/index.html.ru.koi8-r b/docs/manual/programs/index.html.ru.koi8-r new file mode 100644 index 00000000..3028e00f --- /dev/null +++ b/docs/manual/programs/index.html.ru.koi8-r @@ -0,0 +1,100 @@ + + + +óÅÒ×ÅÒ É ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÐÒÏÇÒÁÍÍÙ - HTTP ÓÅÒ×ÅÒ Apache + + + + +
+

íÏÄÕÌÉ | äÉÒÅËÔÉ×Ù | FAQ | çÌÏÓÓÁÒÉÊ | ëÁÒÔÁ ÓÁÊÔÁ

+

HTTP ÓÅÒ×ÅÒ Apache ×ÅÒÓÉÉ 2.2

+
+
<-
+
+Apache > HTTP ÓÅÒ×ÅÒ > äÏËÕÍÅÎÔÁÃÉÑ > ÷ÅÒÓÉÑ 2.2

óÅÒ×ÅÒ É ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÐÒÏÇÒÁÍÍÙ

+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  en  | + es  | + ko  | + ru 

+
+ +

üÔÏÔ ÄÏËÕÍÅÎÔ ÏÐÉÓÙ×ÁÅÔ ÎÁÚÎÁÞÅÎÉÅ É ÉÐÏÌØÚÏ×ÁÎÉÅ + ×ÓÅÈ ÉÓÐÏÌÎÑÅÍÙÈ ÆÁÊÌÏ× HTTP ÓÅÒ×ÅÒÁ Apache.

+
+
top
+
+

õËÁÚÁÔÅÌØ

+ +
+
httpd
+ +
HTTP ÓÅÒ×ÅÒ Apache
+ +
apachectl
+ +
éÎÔÅÒÆÅÊÓ ÕÐÒÁ×ÌÅÎÉÑ HTTP ÓÅÒ×ÅÒÏÍ Apache
+ +
ab
+ +
õÔÉÌÉÔÁ ÄÌÑ ÔÅÓÔÉÒÏ×ÁÎÉÑ HTTP ÓÅÒ×ÅÒÁ Apache
+ +
apxs
+ +
õÔÉÌÉÔÁ APache eXtenSion
+ +
dbmmanage
+ +
óÏÚÄÁÎÉÅ É ÏÂÎÏ×ÌÅÎÉÅ ÆÁÊÌÏ× ÐÁÒÏÌÅÊ ÐÏÌØÚÏ×ÁÔÅÌÅÊ × ÆÏÒÍÁÔÅ DBM, + ÎÅÏÂÈÏÄÉÍÙÈ ÄÌÑ ÂÁÚÏ×ÏÊ ÁÕÔÅÎÔÉÆÉËÁÃÉÉ (basic authentification)
+ +
htcacheclean
+
ïÞÉÓÔÉÔØ ËÜÛ ÎÁ ÄÉÓËÅ
+ +
htdigest
+ +
óÏÚÄÁÎÉÅ É ÏÂÎÏ×ÌÅÎÉÅ ÆÁÊÌÏ× ÐÁÒÏÌÅÊ ÐÏÌØÚÏ×ÁÔÅÌÅÊ ÄÌÑ + ÄÁÊÄÖÅÓÔÎÏÊ ÁÕÔÅÎÔÉÆÉËÁÃÉÉ (digest authentification)
+ +
htpasswd
+ +
óÏÚÄÁÎÉÅ É ÏÂÎÏ×ÌÅÎÉÅ ÆÁÊÌÏ× ÐÁÒÏÌÅÊ ÐÏÌØÚÏ×ÁÔÅÌÅÊ + ÄÌÑ ÂÁÚÏ×ÏÊ ÁÕÔÅÎÔÉÆÉËÁÃÉÉ (basic authentification)
+ +
httxt2dbm
+ +
óÏÚÄÁÎÉÅ dbm ÆÁÊÌÏ× ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ Ó RewriteMap
+ +
logresolve
+ +
õÔÉÌÉÔÁ ÄÌÑ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ IP-ÁÄÒÅÓÏ× × ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÅ + ÉÍ ÉÍÅÎÁ ÈÏÓÔÏ× × ÌÏÇ-ÆÁÊÌÁÈ Apache
+ +
rotatelogs
+ +
õÔÉÌÉÔÁ, ÐÏÚ×ÏÌÑÀÝÁÑ ÐÒÏÉÚ×ÏÄÉÔØ ÒÏÔÁÃÉÀ ÌÏÇ-ÆÁÊÌÏ× Apache ÂÅÚ + ÏÓÔÁÎÏ×ËÉ ÓÅÒ×ÅÒÁ
+ +
suexec
+ +
Switch User For Exec - ÕÔÉÌÉÔÁ, ÐÏÚ×ÏÌÑÀÝÁÑ ×ÙÐÏÌÎÑÔØ CGI-ÓËÒÉÐÔ ÏÔ ÉÍÅÎÉ + ÄÒÕÇÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ
+ +
äÒÕÇÉÅ ÐÒÏÇÒÁÍÍÙ
+
÷ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÕÔÉÌÉÔÙ, ÎÅ ÉÍÅÀÝÉÅ Ó×ÏÉÈ ÓÏÂÓÔ×ÅÎÎÙÈ ÓÐÒÁ×ÏÞÎÙÈ ÒÕËÏ×ÏÄÓÔ×
+
+
+
+

äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  en  | + es  | + ko  | + ru 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/logresolve.html b/docs/manual/programs/logresolve.html new file mode 100644 index 00000000..6c1b8a70 --- /dev/null +++ b/docs/manual/programs/logresolve.html @@ -0,0 +1,7 @@ +URI: logresolve.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: logresolve.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/logresolve.html.en b/docs/manual/programs/logresolve.html.en new file mode 100644 index 00000000..cde89c86 --- /dev/null +++ b/docs/manual/programs/logresolve.html.en @@ -0,0 +1,72 @@ + + + +logresolve - Resolve IP-addresses to hostnames in Apache + log files - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

logresolve - Resolve IP-addresses to hostnames in Apache + log files

+
+

Available Languages:  en  | + ko 

+
+ +

logresolve is a post-processing program to + resolve IP-addresses in Apache's access logfiles. To minimize + impact on your nameserver, logresolve has its very own internal + hash-table cache. This means that each IP number will only be + looked up the first time it is found in the log file.

+ +

Takes an Apache log file on standard input. The IP addresses + must be the first thing on each line and must be separated from + the remainder of the line by a space.

+
+ +
top
+
+

Synopsis

+ +

logresolve [ -s + filename ] [ -c ] < + access_log > access_log.new

+
top
+
+

Options

+ +
+ +
-s filename
+ +
Specifies a filename to record statistics.
+ +
-c
+ +
This causes logresolve to apply some DNS checks: +after finding the hostname from the IP address, it looks up the IP +addresses for the hostname and checks that one of these matches the +original address.
+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/logresolve.html.ko.euc-kr b/docs/manual/programs/logresolve.html.ko.euc-kr new file mode 100644 index 00000000..5cc22286 --- /dev/null +++ b/docs/manual/programs/logresolve.html.ko.euc-kr @@ -0,0 +1,69 @@ + + + +logresolve - ¾ÆÆÄÄ¡ ·Î±×ÆÄÀÏÀÇ IP-ÁÖ¼Ò¸¦ È£½ºÆ®¸íÀ¸·Î + º¯È¯ÇÑ´Ù - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

logresolve - ¾ÆÆÄÄ¡ ·Î±×ÆÄÀÏÀÇ IP-ÁÖ¼Ò¸¦ È£½ºÆ®¸íÀ¸·Î + º¯È¯ÇÑ´Ù

+
+

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

+
+ +

logresolve´Â ¾ÆÆÄÄ¡ Á¢±Ù·Î±×ÆÄÀÏ¿¡ ÀÖ´Â + IP-ÁÖ¼Ò¸¦ ã´Â ÈÄó¸® ÇÁ·Î±×·¥ÀÌ´Ù. ³×ÀÓ¼­¹öÀÇ ºÎÇϸ¦ + ÃÖ¼ÒÈ­ÇϱâÀ§ÇØ logresolve´Â ³»ºÎÀûÀ¸·Î Çؽ¬Å×À̺í ij½¬¸¦ + »ç¿ëÇÑ´Ù. Áï, IP ÁÖ¼Ò°¡ ·Î±×ÆÄÀÏ¿¡ óÀ½ ³ª¿Ã¶§¸¸ ã´Â´Ù.

+ +

Ç¥ÁØÀÔ·ÂÀ¸·Î ¾ÆÆÄÄ¡ ·Î±×ÆÄÀÏÀ» Àд´Ù. °¢ ÁÙÀÇ Ã¹¹ø° + Ç׸ñÀÌ IP ÁÖ¼ÒÀÌ°í, ³ª¸ÓÁö ºÎºÐ°ú °ø¹éÀ¸·Î ±¸ºÐµÇ¾ß ÇÑ´Ù.

+
+ +
top
+
+

°³¿ä

+ +

logresolve [ -s + filename ] [ -c ] < + access_log > access_log.new

+
top
+
+

¿É¼Ç

+ +
+ +
-s filename
+ +
Åë°è¸¦ ±â·ÏÇÒ ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù.
+ +
-c
+ +
logresolve°¡ ¸î°¡Áö DNS °Ë»ç¸¦ Çϵµ·Ï ÇÑ´Ù: +IP ÁּҷΠȣ½ºÆ®¸íÀ» ãÀºÈÄ ±× È£½ºÆ®¸íÀ¸·Î ´Ù½Ã IP ÁÖ¼ÒµéÀ» +ã¾Æ¼­ ±×Áß Çϳª°¡ ¿ø·¡ ÁÖ¼Ò¿Í ÀÏÄ¡ÇÏ´ÂÁö °Ë»çÇÑ´Ù.
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/other.html b/docs/manual/programs/other.html new file mode 100644 index 00000000..2f947740 --- /dev/null +++ b/docs/manual/programs/other.html @@ -0,0 +1,7 @@ +URI: other.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: other.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/other.html.en b/docs/manual/programs/other.html.en new file mode 100644 index 00000000..e8d518d4 --- /dev/null +++ b/docs/manual/programs/other.html.en @@ -0,0 +1,59 @@ + + + +Other Programs - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

Other Programs

+
+

Available Languages:  en  | + ko 

+
+ +

The following programs are simple support programs included with the + Apache HTTP Server which do not have their own manual pages. They are not + installed automatically. You can find them after the configuration process + in the support/ directory.

+
+ +
top
+
+

log_server_status

+

This perl script is designed to be run at a frequent interval by + something like cron. It connects to the server and downloads the status + information. It reformats the information to a single line and logs it to + a file. Adjust the variables at the top of the script to specify the + location of the resulting logfile.

+
top
+
+

split-logfile

+

This perl script will take a combined Web server access log file and + break its contents into separate files. It assumes that the first field of + each line is the virtual host identity (put there by "%v"), and + that the logfiles should be named that + ".log" in the current + directory.

+ +

The combined log file is read from stdin. Records read will be appended + to any existing log files.

+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/other.html.ko.euc-kr b/docs/manual/programs/other.html.ko.euc-kr new file mode 100644 index 00000000..de3d0805 --- /dev/null +++ b/docs/manual/programs/other.html.ko.euc-kr @@ -0,0 +1,57 @@ + + + +Other Programs - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

Other Programs

+
+

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

+
+ +

´ÙÀ½Àº °£´ÜÇÏ¿© manpage°¡ ¾ø´Â, ¾ÆÆÄÄ¡ À¥¼­¹ö¿¡ Æ÷ÇÔµÈ + Áö¿ø ÇÁ·Î±×·¥µéÀÌ´Ù. ÀÚµ¿À¸·Î À̵éÀ» ¼³Ä¡ÇÏÁö ¾Ê´Â´Ù. + ±¸¼º°úÁ¤ÈÄ support/ µð·ºÅ丮¿¡¼­ ÀÌ ÇÁ·Î±×·¥µéÀ» + ãÀ» ¼ö ÀÖ´Ù.

+
+ +
top
+
+

log_server_status

+

ÀÌ perl ½ºÅ©¸³Æ®´Â cron µî¿¡¼­ ÀÚÁÖ ½ÇÇàÇϵµ·Ï ¼³°èµÇ¾ú´Ù. + ÀÌ ½ºÅ©¸³Æ®¸¦ ¼­¹ö¿¡ ¿¬°áÇÏ¿© »óÅ Á¤º¸¸¦ ´Ù¿î·ÎµåÇÑ´Ù. + ±×·±ÈÄ ÀÌ Á¤º¸¸¦ ÇÑÁÙ·Î Á¤¸®ÇÏ¿© ÆÄÀÏ¿¡ ±â·ÏÇÑ´Ù. ·Î±×ÆÄÀÏÀÇ + À§Ä¡¸¦ ÁöÁ¤ÇÏ·Á¸é ½ºÅ©¸³Æ® ¾ÕºÎºÐÀÇ º¯¼ö¸¦ ¼öÁ¤ÇÑ´Ù.

+
top
+
+

split-logfile

+

ÀÌ perl ½ºÅ©¸³Æ®´Â °áÇÕµÈ À¥¼­¹ö Á¢±Ù·Î±×ÆÄÀÏÀÇ ³»¿ëÀ» + ¿©·¯ ÆÄÀÏ·Î ³ª´«´Ù. °¢ ÁÙÀÇ Ã¹¹ø° Ç׸ñÀÌ ("%v"·Î + Ãß°¡ÇÑ) °¡»óÈ£½ºÆ® Á¤º¸ÀÌ°í, ·Î±×ÆÄÀϸíÀº ÇöÀç µð·ºÅ丮¿¡ + °¡»óÈ£½ºÆ®¸í + ".log"¶ó°í °¡Á¤ÇÑ´Ù.

+ +

°áÇÕµÈ ·Î±×ÆÄÀÏÀ» Ç¥ÁØÀÔ·ÂÀ¸·Î Àд´Ù. ÀÐÀº ³»¿ëÀ» ±âÁ¸ÀÇ + ·Î±×ÆÄÀϵ鿡 Ãß°¡ÇÑ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/rotatelogs.html b/docs/manual/programs/rotatelogs.html new file mode 100644 index 00000000..d4b500ff --- /dev/null +++ b/docs/manual/programs/rotatelogs.html @@ -0,0 +1,7 @@ +URI: rotatelogs.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: rotatelogs.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/rotatelogs.html.en b/docs/manual/programs/rotatelogs.html.en new file mode 100644 index 00000000..c06ed87d --- /dev/null +++ b/docs/manual/programs/rotatelogs.html.en @@ -0,0 +1,146 @@ + + + +rotatelogs - Piped logging program to rotate Apache logs - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

rotatelogs - Piped logging program to rotate Apache logs

+
+

Available Languages:  en  | + ko 

+
+ +

rotatelogs is a simple program for use in + conjunction with Apache's piped logfile feature. For example:

+ +

+ CustomLog "|bin/rotatelogs /var/logs/logfile 86400" common +

+ +

This creates the files /var/logs/logfile.nnnn where nnnn is + the system time at which the log nominally starts (this time + will always be a multiple of the rotation time, so you can + synchronize cron scripts with it). At the end of each rotation + time (here after 24 hours) a new log is started.

+ +

+ CustomLog "|bin/rotatelogs /var/logs/logfile 5M" common +

+ +

This configuration will rotate the logfile whenever it reaches + a size of 5 megabytes.

+ +

+ ErrorLog "|bin/rotatelogs /var/logs/errorlog.%Y-%m-%d-%H_%M_%S 5M" +

+

This configuration will rotate the error logfile whenever it + reaches a size of 5 megabytes, and the suffix to the logfile name + will be created of the form + errorlog.YYYY-mm-dd-HH_MM_SS.

+ +
+ +
top
+
+

Synopsis

+ +

rotatelogs + [ -l ] + logfile + [ rotationtime [ offset ]] | + [ filesizeM ]

+
top
+
+

Options

+ +
+ +
-l
+
Causes the use of local time rather than GMT as the base for the +interval. Note that using -l in an environment which changes the +GMT offset (such as for BST or DST) can lead to unpredictable results!
+ +
logfile
+ +
The path plus basename of the logfile. If logfile +includes any '%' characters, it is treated as a format string for +strftime(3). Otherwise, the suffix +.nnnnnnnnnn is automatically added and is the time in +seconds. Both formats compute the start time from the beginning of +the current period.
+ +
rotationtime
+ +
The time between log file rotations in seconds.
+ +
offset
+ +
The number of minutes offset from UTC. If omitted, zero is +assumed and UTC is used. For example, to use local time in the zone +UTC -5 hours, specify a value of -300 for this argument.
+ +
filesizeM
+ +
The maximum file size in megabytes followed by the letter +M to specify size rather than time. Use this parameter +in place of both rotationtime and offset.
+
+
top
+
+

Portability

+ +

The following logfile format string substitutions should be +supported by all strftime(3) implementations, see +the strftime(3) man page for library-specific +extensions.

+ + + + + + + + + + + + + + + + + + + + + + + +
%Afull weekday name (localized)
%a3-character weekday name (localized)
%Bfull month name (localized)
%b3-character month name (localized)
%cdate and time (localized)
%d2-digit day of month
%H2-digit hour (24 hour clock)
%I2-digit hour (12 hour clock)
%j3-digit day of year
%M2-digit minute
%m2-digit month
%pam/pm of 12 hour clock (localized)
%S2-digit second
%U2-digit week of year +(Sunday first day of week)
%W2-digit week of year +(Monday first day of week)
%w1-digit weekday +(Sunday first day of week)
%Xtime (localized)
%xdate (localized)
%Y4-digit year
%y2-digit year
%Ztime zone name
%%literal `%'
+ +
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/rotatelogs.html.ko.euc-kr b/docs/manual/programs/rotatelogs.html.ko.euc-kr new file mode 100644 index 00000000..c12b8cb8 --- /dev/null +++ b/docs/manual/programs/rotatelogs.html.ko.euc-kr @@ -0,0 +1,143 @@ + + + +rotatelogs - ¾ÆÆÄÄ¡ ·Î±×¸¦ ¼øȯÇϱâÀ§ÇØ ÆÄÀÌÇÁ·Î ¿¬°áÇÒ + ·Î±× ÇÁ·Î±×·¥ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

rotatelogs - ¾ÆÆÄÄ¡ ·Î±×¸¦ ¼øȯÇϱâÀ§ÇØ ÆÄÀÌÇÁ·Î ¿¬°áÇÒ + ·Î±× ÇÁ·Î±×·¥

+
+

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

+
+ +

rotatelogs´Â ¾ÆÆÄÄ¡ÀÇ ÆÄÀÌÇÁ ·Î±×ÆÄÀÏ ±â´ÉÀ» + À§ÇÑ °£´ÜÇÑ ÇÁ·Î±×·¥ÀÌ´Ù. ¿¹¸¦ µé¾î:

+ +

+ CustomLog "|bin/rotatelogs /var/logs/logfile 86400" common +

+ +

±×·¯¸é /var/logs/logfile.nnnn ÆÄÀÏÀ» ¸¸µç´Ù. nnnnÀº + ·Î±×¸¦ ½ÃÀÛÇÑ ½Ã½ºÅ۽ð£ÀÌ´Ù (ÀÌ ½Ã°£Àº Ç×»ó ¼øȯ±â°£ÀÇ + ¹è¼öÀÌ´Ù. ±×·¡¼­ cron ½ºÅ©¸³Æ®·Î ó¸®Çϱ⠽±´Ù). ¼øȯ±â°£ + (¿©±â¼­´Â 24 ½Ã°£) ¸¶´Ù »õ·Î¿î ·Î±×¸¦ ½ÃÀÛÇÑ´Ù.

+ +

+ CustomLog "|bin/rotatelogs /var/logs/logfile 5M" common +

+ +

ÀÌ ¼³Á¤Àº ·Î±×ÆÄÀÏ Å©±â°¡ 5 ¸Þ°¡¹ÙÀÌÆ®°¡ µÉ¶§¸¶´Ù + ¼øȯÇÑ´Ù.

+ +

+ ErrorLog "|bin/rotatelogs /var/logs/errorlog.%Y-%m-%d-%H_%M_%S 5M" +

+

ÀÌ ¼³Á¤Àº ¿À·ù·Î±× ÆÄÀÏ Å©±â°¡ 5 ¸Þ°¡¹ÙÀÌÆ®°¡ µÉ¶§¸¶´Ù + errorlog.YYYY-mm-dd-HH_MM_SS¿Í °°Àº ÆÄÀÏÀ» + ¸¸µé¾î¼­ ¿À·ù·Î±× ÆÄÀÏÀ» ¼øȯÇÑ´Ù.

+ +
+ +
top
+
+

°³¿ä

+ +

rotatelogs + [ -l ] + logfile + [ rotationtime [ offset ]] | + [ filesizeM ]

+
top
+
+

¿É¼Ç

+ +
+ +
-l
+
¼øȯÁÖ±â·Î GMT ´ë½Å Áö¿ª½Ã°£À» »ç¿ëÇÑ´Ù. (BST³ª DST¿Í °°ÀÌ) +GMT ½Ã°£Â÷°¡ º¯Çϴ ȯ°æ¿¡¼­ -lÀ» »ç¿ëÇÏ¸é ¿¹±âÄ¡ +¾ÊÀº °á°ú°¡ ¹ß»ýÇÒ ¼ö ÀÖ´Ù!
+ +
logfile
+ +
·Î±×ÆÄÀÏÀÇ °æ·Î¿Í À̸§. logfile¿¡ '%' ¹®ÀÚ°¡ +ÀÖ´Ù¸é strftime(3)ÀÇ Çü½Ä¹®ÀÚ¿­°ú °°ÀÌ Ã³¸®ÇÑ´Ù. +'%' ¹®ÀÚ°¡ ¾ø´Ù¸é µÚ¿¡ ÃÊ´ÜÀ§ ½Ã°£ .nnnnnnnnnnÀ» +ÀÚµ¿À¸·Î ºÙÀδÙ. µÎ Çü½Ä ¸ðµÎ ÇöÀç ±â°£ºÎÅÍ ½ÃÀ۽ð£À» °è»êÇÑ´Ù.
+ +
rotationtime
+ +
·Î±×ÆÄÀÏÀ» ¼øȯÇÒ ÃÊ´ÜÀ§ ½Ã°£.
+ +
offset
+ +
UTC¿¡¼­ ºÐ´ÜÀ§ ½Ã°£Â÷ÀÌ. »ý·«Çϸé 0À¸·Î °¡Á¤ÇÏ¿© UTC¸¦ +»ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î, UTC -5 ½Ã°£´ëÀÇ Áö¿ª½Ã°£À» »ç¿ëÇÑ´Ù¸é +¾Æ±Ô¸ÕÆ®·Î -300À» ÁöÁ¤ÇÑ´Ù.
+ +
filesizeM
+ +
½Ã°£ÀÌ ¾Æ´Ñ Å©±â¸¦ ÁöÁ¤ÇÒ¶§ ¸Þ°¡¹ÙÀÌÆ®´ÜÀ§ ÃÖ´ë ÆÄÀÏÅ©±â +µÚ¿¡ MÀ» ºÙÀδÙ. rotationtime°ú offset ´ë½Å ÀÌ +ÆĶó¹ÌÅ͸¦ »ç¿ëÇÑ´Ù.
+
+
top
+
+

Æ÷Æð¡´É¼º

+ +

´ÙÀ½ ·Î±×ÆÄÀÏ Çü½Ä¹®ÀÚ¿­ Ç¥ÇöÀº ¸ðµç strftime(3) +±¸ÇöÀÌ Áö¿øÇØ¾ß ÇÑ´Ù. ¶óÀ̺귯¸® ƯÀ¯ÀÇ È®ÀåÀº +strftime(3) manpage¸¦ Âü°íÇ϶ó.

+ + + + + + + + + + + + + + + + + + + + + + + +
%A(Áö¿ªÈ­µÈ) ¿ÏÀüÇÑ ¿äÀÏ À̸§
%a(Áö¿ªÈ­µÈ) 3-¹®ÀÚ ¿äÀÏ À̸§
%B(Áö¿ªÈ­µÈ) ¿ÏÀüÇÑ ´Þ À̸§
%b(Áö¿ªÈ­µÈ) 3-¹®ÀÚ ´Þ À̸§
%c(Áö¿ªÈ­µÈ) ³¯Â¥¿Í ½Ã°£
%d2-ÀÚ¸® ÀÏ
%H2-ÀÚ¸® ½Ã°£ (24 ½Ã°£ ½Ã°è)
%I2-ÀÚ¸® ½Ã°£ (12 ½Ã°£ ½Ã°è)
%j3-ÀÚ¸® ³¯Â¥¼ö
%M2-ÀÚ¸® ºÐ
%m2-ÀÚ¸® ´Þ
%p(Áö¿ªÈ­µÈ) 12 ½Ã°£ ½Ã°èÀÇ am/pm
%S2-ÀÚ¸® ÃÊ
%U2-ÀÚ¸® ÁÖÀϼö (ÁÖÀÇ Ã¹¹øÀç ³¯Àº +ÀÏ¿äÀÏ)
%W2-ÀÚ¸® ÁÖÀϼö (ÁÖÀÇ Ã¹¹øÀç ³¯Àº +¿ù¿äÀÏ)
%w1-ÀÚ¸® ¿äÀϼö (ÁÖÀÇ Ã¹¹ø° ³¯Àº +ÀÏ¿äÀÏ)
%X(Áö¿ªÈ­µÈ) ½Ã°£
%x(Áö¿ªÈ­µÈ) ³¯Â¥
%Y4-ÀÚ¸® ¿¬µµ
%y2-ÀÚ¸® ¿¬µµ
%Z½Ã°£´ë À̸§
%%¹®ÀÚ±×´ë·Î `%'
+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/programs/suexec.html b/docs/manual/programs/suexec.html new file mode 100644 index 00000000..f9408988 --- /dev/null +++ b/docs/manual/programs/suexec.html @@ -0,0 +1,7 @@ +URI: suexec.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: suexec.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/programs/suexec.html.en b/docs/manual/programs/suexec.html.en new file mode 100644 index 00000000..e635bea1 --- /dev/null +++ b/docs/manual/programs/suexec.html.en @@ -0,0 +1,61 @@ + + + +suexec - Switch user before executing external programs - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

suexec - Switch user before executing external programs

+
+

Available Languages:  en  | + ko 

+
+ +

suexec is used by the Apache HTTP Server to switch + to another user before executing CGI programs. In order to achieve this, + it must run as root. Since the HTTP daemon normally doesn't + run as root, the suexec executable needs the + setuid bit set and must be owned by root. It should never be + writable for any other person than root.

+ +

For further information about the concepts and and the security model + of suexec please refer to the suexec documentation (http://httpd.apache.org/docs/2.2/suexec.html).

+
+ +
top
+
+

Synopsis

+

suexec -V

+
top
+
+

Options

+ +
+
-V
+ +
If you are root, this option displays the compile options of +suexec. For security reasons all configuration options are +changeable only at compile time.
+ +
+
+
+

Available Languages:  en  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/programs/suexec.html.ko.euc-kr b/docs/manual/programs/suexec.html.ko.euc-kr new file mode 100644 index 00000000..d205eb24 --- /dev/null +++ b/docs/manual/programs/suexec.html.ko.euc-kr @@ -0,0 +1,62 @@ + + + +suexec - ¿ÜºÎ ÇÁ·Î±×·¥À» ½ÇÇàÇϱâ Àü¿¡ »ç¿ëÀÚ¸¦ º¯°æÇÑ´Ù - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > Programs

suexec - ¿ÜºÎ ÇÁ·Î±×·¥À» ½ÇÇàÇϱâ Àü¿¡ »ç¿ëÀÚ¸¦ º¯°æÇÑ´Ù

+
+

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

+
+ +

¾ÆÆÄÄ¡ À¥¼­¹ö´Â CGI ÇÁ·Î±×·¥À» ½ÇÇàÇϱâ Àü¿¡ ´Ù¸¥ »ç¿ëÀÚ·Î + ÀüȯÇϱâÀ§ÇØ suexec¸¦ »ç¿ëÇÑ´Ù. À̸¦ »ç¿ëÇÏ·Á¸é + ¼­¹ö¸¦ root °èÁ¤À¸·Î ½ÇÇàÇØ¾ß ÇÑ´Ù. º¸Åë À¥ + µ¥¸óÀ» root °èÁ¤À¸·Î ½ÇÇàÇÏÁö ¾Ê±â¶§¹®¿¡ + suexec ½ÇÇàÆÄÀÏ¿¡ setuid ºñÆ®¸¦ ¼³Á¤ÇÏ°í + root°¡ ¼ÒÀ¯ÁÖÀ̾î¾ß ÇÑ´Ù. rootÀÌ¿ÜÀÇ + ´Ù¸¥ »ç¿ëÀÚ°¡ ¾²±â±ÇÇÑÀ» °¡Áö¸é ¾ÈµÈ´Ù.

+ +

suexecÀÇ °³³ä°ú º¸¾È¸ðµ¨¿¡ ´ëÇÑ Á¤º¸´Â suexec ¹®¼­¸¦ + (http://httpd.apache.org/docs/2.2/suexec.html) Âü°íÇ϶ó.

+
+ +
top
+
+

°³¿ä

+

suexec -V

+
top
+
+

¿É¼Ç

+ +
+
-V
+ +
root°¡ ½ÇÇàÇϸé suexecÀÇ ÄÄÆÄÀÏ +¿É¼ÇÀ» Ãâ·ÂÇÑ´Ù. º¸¾È»ó ÀÌÀ¯·Î ¸ðµç ¼³Á¤¿É¼ÇÀº ÄÄÆÄÀÏÇÒ ¶§¸¸ +ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù.
+ +
+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/rewrite/index.html b/docs/manual/rewrite/index.html new file mode 100644 index 00000000..5f97bff8 --- /dev/null +++ b/docs/manual/rewrite/index.html @@ -0,0 +1,3 @@ +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/rewrite/index.html.en b/docs/manual/rewrite/index.html.en new file mode 100644 index 00000000..f53b27dc --- /dev/null +++ b/docs/manual/rewrite/index.html.en @@ -0,0 +1,96 @@ + + + +Apache mod_rewrite - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Apache mod_rewrite

+
+

Available Languages:  en 

+
+ +
+

``The great thing about mod_rewrite is it gives you + all the configurability and flexibility of Sendmail. + The downside to mod_rewrite is that it gives you all + the configurability and flexibility of Sendmail.''

+ +

-- Brian Behlendorf
+ Apache Group

+ +
+ +
+

`` Despite the tons of examples and docs, + mod_rewrite is voodoo. Damned cool voodoo, but still + voodoo.''

+ +

-- Brian Moore
+ bem@news.cmc.net

+ +
+ +

Welcome to mod_rewrite, the Swiss Army Knife of URL + manipulation!

+ +

This module uses a rule-based rewriting engine (based on a + regular-expression parser) to rewrite requested URLs on the + fly. It supports an unlimited number of rules and an + unlimited number of attached rule conditions for each rule to + provide a really flexible and powerful URL manipulation + mechanism. The URL manipulations can depend on various tests, + for instance server variables, environment variables, HTTP + headers, time stamps and even external database lookups in + various formats can be used to achieve granular URL + matching.

+ +

This module operates on the full URLs (including the + path-info part) both in per-server context + (httpd.conf) and per-directory context + (.htaccess) and can even generate query-string + parts on result. The rewritten result can lead to internal + sub-processing, external request redirection or even to an + internal proxy throughput.

+ +

But all this functionality and flexibility has its + drawback: complexity. So don't expect to understand this + entire module in just one day.

+ +
+ +
top
+
+

Documentation

+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/rewrite/rewrite_guide.html b/docs/manual/rewrite/rewrite_guide.html new file mode 100644 index 00000000..49f623e9 --- /dev/null +++ b/docs/manual/rewrite/rewrite_guide.html @@ -0,0 +1,3 @@ +URI: rewrite_guide.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/rewrite/rewrite_guide.html.en b/docs/manual/rewrite/rewrite_guide.html.en new file mode 100644 index 00000000..2dd428bb --- /dev/null +++ b/docs/manual/rewrite/rewrite_guide.html.en @@ -0,0 +1,789 @@ + + + +URL Rewriting Guide - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

URL Rewriting Guide

+
+

Available Languages:  en 

+
+ + +

This document supplements the mod_rewrite + reference documentation. + It describes how one can use Apache's mod_rewrite + to solve typical URL-based problems with which webmasters are + commonony confronted. We give detailed descriptions on how to + solve each problem by configuring URL rewriting rulesets.

+ +
ATTENTION: Depending on your server configuration + it may be necessary to slightly change the examples for your + situation, e.g. adding the [PT] flag when + additionally using mod_alias and + mod_userdir, etc. Or rewriting a ruleset + to fit in .htaccess context instead + of per-server context. Always try to understand what a + particular ruleset really does before you use it. This + avoids many problems.
+ +
+ +
top
+
+

Canonical URLs

+ + + +
+
Description:
+ +
+

On some webservers there are more than one URL for a + resource. Usually there are canonical URLs (which should be + actually used and distributed) and those which are just + shortcuts, internal ones, etc. Independent of which URL the + user supplied with the request he should finally see the + canonical one only.

+
+ +
Solution:
+ +
+

We do an external HTTP redirect for all non-canonical + URLs to fix them in the location view of the Browser and + for all subsequent requests. In the example ruleset below + we replace /~user by the canonical + /u/user and fix a missing trailing slash for + /u/user.

+ +
+RewriteRule   ^/~([^/]+)/?(.*)    /u/$1/$2  [R]
+RewriteRule   ^/([uge])/([^/]+)$  /$1/$2/   [R]
+
+
+
+ +
top
+
+

Canonical Hostnames

+ +
+
Description:
+ +
The goal of this rule is to force the use of a particular + hostname, in preference to other hostnames which may be used to + reach the same site. For example, if you wish to force the use + of www.example.com instead of + example.com, you might use a variant of the + following recipe.
+ +
Solution:
+ +
+

For sites running on a port other than 80:

+
+RewriteCond %{HTTP_HOST}   !^fully\.qualified\.domain\.name [NC]
+RewriteCond %{HTTP_HOST}   !^$
+RewriteCond %{SERVER_PORT} !^80$
+RewriteRule ^/(.*)         http://fully.qualified.domain.name:%{SERVER_PORT}/$1 [L,R]
+
+ +

And for a site running on port 80

+
+RewriteCond %{HTTP_HOST}   !^fully\.qualified\.domain\.name [NC]
+RewriteCond %{HTTP_HOST}   !^$
+RewriteRule ^/(.*)         http://fully.qualified.domain.name/$1 [L,R]
+
+
+
+ +
top
+
+

Moved DocumentRoot

+ + + +
+
Description:
+ +
+

Usually the DocumentRoot +of the webserver directly relates to the URL "/". +But often this data is not really of top-level priority. For example, +you may wish for visitors, on first entering a site, to go to a +particular subdirectory /about/. This may be accomplished +using the following ruleset:

+
+ +
Solution:
+ +
+

We redirect the URL / to + /about/: +

+ +
+RewriteEngine on
+RewriteRule   ^/$  /about/  [R]
+
+ +

Note that this can also be handled using the RedirectMatch directive:

+ +

+RedirectMatch ^/$ http://example.com/e/www/ +

+
+
+ +
top
+
+

Trailing Slash Problem

+ + + +
+
Description:
+ +

The vast majority of "trailing slash" problems can be dealt + with using the techniques discussed in the FAQ + entry. However, occasionally, there is a need to use mod_rewrite + to handle a case where a missing trailing slash causes a URL to + fail. This can happen, for example, after a series of complex + rewrite rules.

+
+ +
Solution:
+ +
+

The solution to this subtle problem is to let the server + add the trailing slash automatically. To do this + correctly we have to use an external redirect, so the + browser correctly requests subsequent images etc. If we + only did a internal rewrite, this would only work for the + directory page, but would go wrong when any images are + included into this page with relative URLs, because the + browser would request an in-lined object. For instance, a + request for image.gif in + /~quux/foo/index.html would become + /~quux/image.gif without the external + redirect!

+ +

So, to do this trick we write:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo$  foo/  [R]
+
+ +

Alternately, you can put the following in a + top-level .htaccess file in the content directory. + But note that this creates some processing overhead.

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteCond    %{REQUEST_FILENAME}  -d
+RewriteRule    ^(.+[^/])$           $1/  [R]
+
+
+
+ +
top
+
+

Move Homedirs to Different Webserver

+ + + +
+
Description:
+ +
+

Many webmasters have asked for a solution to the + following situation: They wanted to redirect just all + homedirs on a webserver to another webserver. They usually + need such things when establishing a newer webserver which + will replace the old one over time.

+
+ +
Solution:
+ +
+

The solution is trivial with mod_rewrite. + On the old webserver we just redirect all + /~user/anypath URLs to + http://newserver/~user/anypath.

+ +
+RewriteEngine on
+RewriteRule   ^/~(.+)  http://newserver/~$1  [R,L]
+
+
+
+ +
top
+
+

Search pages in more than one directory

+ + + +
+
Description:
+ +
+

Sometimes it is necessary to let the webserver search + for pages in more than one directory. Here MultiViews or + other techniques cannot help.

+
+ +
Solution:
+ +
+

We program a explicit ruleset which searches for the + files in the directories.

+ +
+RewriteEngine on
+
+#   first try to find it in custom/...
+#   ...and if found stop and be happy:
+RewriteCond         /your/docroot/dir1/%{REQUEST_FILENAME}  -f
+RewriteRule  ^(.+)  /your/docroot/dir1/$1  [L]
+
+#   second try to find it in pub/...
+#   ...and if found stop and be happy:
+RewriteCond         /your/docroot/dir2/%{REQUEST_FILENAME}  -f
+RewriteRule  ^(.+)  /your/docroot/dir2/$1  [L]
+
+#   else go on for other Alias or ScriptAlias directives,
+#   etc.
+RewriteRule   ^(.+)  -  [PT]
+
+
+
+ +
top
+
+

Set Environment Variables According To URL Parts

+ + + +
+
Description:
+ +
+

Perhaps you want to keep status information between + requests and use the URL to encode it. But you don't want + to use a CGI wrapper for all pages just to strip out this + information.

+
+ +
Solution:
+ +
+

We use a rewrite rule to strip out the status information + and remember it via an environment variable which can be + later dereferenced from within XSSI or CGI. This way a + URL /foo/S=java/bar/ gets translated to + /foo/bar/ and the environment variable named + STATUS is set to the value "java".

+ +
+RewriteEngine on
+RewriteRule   ^(.*)/S=([^/]+)/(.*)    $1/$3 [E=STATUS:$2]
+
+
+
+ +
top
+
+

Virtual User Hosts

+ + + +
+
Description:
+ +
+

Assume that you want to provide + www.username.host.domain.com + for the homepage of username via just DNS A records to the + same machine and without any virtualhosts on this + machine.

+
+ +
Solution:
+ +
+

For HTTP/1.0 requests there is no solution, but for + HTTP/1.1 requests which contain a Host: HTTP header we + can use the following ruleset to rewrite + http://www.username.host.com/anypath + internally to /home/username/anypath:

+ +
+RewriteEngine on
+RewriteCond   %{HTTP_HOST}                 ^www\.[^.]+\.host\.com$
+RewriteRule   ^(.+)                        %{HTTP_HOST}$1          [C]
+RewriteRule   ^www\.([^.]+)\.host\.com(.*) /home/$1$2
+
+
+
+ +
top
+
+

Redirect Homedirs For Foreigners

+ + + +
+
Description:
+ +
+

We want to redirect homedir URLs to another webserver + www.somewhere.com when the requesting user + does not stay in the local domain + ourdomain.com. This is sometimes used in + virtual host contexts.

+
+ +
Solution:
+ +
+

Just a rewrite condition:

+ +
+RewriteEngine on
+RewriteCond   %{REMOTE_HOST}  !^.+\.ourdomain\.com$
+RewriteRule   ^(/~.+)         http://www.somewhere.com/$1 [R,L]
+
+
+
+ +
top
+
+

Redirecting Anchors

+ + + +
+
Description:
+ +
+

By default, redirecting to an HTML anchor doesn't work, + because mod_rewrite escapes the # character, + turning it into %23. This, in turn, breaks the + redirection.

+
+ +
Solution:
+ +
+

Use the [NE] flag on the + RewriteRule. NE stands for No Escape. +

+
+
+ +
top
+
+

Time-Dependent Rewriting

+ + + +
+
Description:
+ +
+

When tricks like time-dependent content should happen a + lot of webmasters still use CGI scripts which do for + instance redirects to specialized pages. How can it be done + via mod_rewrite?

+
+ +
Solution:
+ +
+

There are a lot of variables named TIME_xxx + for rewrite conditions. In conjunction with the special + lexicographic comparison patterns <STRING, + >STRING and =STRING we can + do time-dependent redirects:

+ +
+RewriteEngine on
+RewriteCond   %{TIME_HOUR}%{TIME_MIN} >0700
+RewriteCond   %{TIME_HOUR}%{TIME_MIN} <1900
+RewriteRule   ^foo\.html$             foo.day.html
+RewriteRule   ^foo\.html$             foo.night.html
+
+ +

This provides the content of foo.day.html + under the URL foo.html from + 07:00-19:00 and at the remaining time the + contents of foo.night.html. Just a nice + feature for a homepage...

+
+
+ +
top
+
+

Backward Compatibility for YYYY to XXXX migration

+ + + +
+
Description:
+ +
+

How can we make URLs backward compatible (still + existing virtually) after migrating document.YYYY + to document.XXXX, e.g. after translating a + bunch of .html files to .phtml?

+
+ +
Solution:
+ +
+

We just rewrite the name to its basename and test for + existence of the new extension. If it exists, we take + that name, else we rewrite the URL to its original state.

+ + +
+#   backward compatibility ruleset for
+#   rewriting document.html to document.phtml
+#   when and only when document.phtml exists
+#   but no longer document.html
+RewriteEngine on
+RewriteBase   /~quux/
+#   parse out basename, but remember the fact
+RewriteRule   ^(.*)\.html$              $1      [C,E=WasHTML:yes]
+#   rewrite to document.phtml if exists
+RewriteCond   %{REQUEST_FILENAME}.phtml -f
+RewriteRule   ^(.*)$ $1.phtml                   [S=1]
+#   else reverse the previous basename cutout
+RewriteCond   %{ENV:WasHTML}            ^yes$
+RewriteRule   ^(.*)$ $1.html
+
+
+
+ +
top
+
+

Content Handling

+ + + +

From Old to New (intern)

+ + + +
+
Description:
+ +
+

Assume we have recently renamed the page + foo.html to bar.html and now want + to provide the old URL for backward compatibility. Actually + we want that users of the old URL even not recognize that + the pages was renamed.

+
+ +
Solution:
+ +
+

We rewrite the old URL to the new one internally via the + following rule:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  bar.html
+
+
+
+ + + +

From Old to New (extern)

+ + + +
+
Description:
+ +
+

Assume again that we have recently renamed the page + foo.html to bar.html and now want + to provide the old URL for backward compatibility. But this + time we want that the users of the old URL get hinted to + the new one, i.e. their browsers Location field should + change, too.

+
+ +
Solution:
+ +
+

We force a HTTP redirect to the new URL which leads to a + change of the browsers and thus the users view:

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  bar.html  [R]
+
+
+
+ + + +

From Static to Dynamic

+ + + +
+
Description:
+ +
+

How can we transform a static page + foo.html into a dynamic variant + foo.cgi in a seamless way, i.e. without notice + by the browser/user.

+
+ +
Solution:
+ +
+

We just rewrite the URL to the CGI-script and force the + correct MIME-type so it gets really run as a CGI-script. + This way a request to /~quux/foo.html + internally leads to the invocation of + /~quux/foo.cgi.

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^foo\.html$  foo.cgi  [T=application/x-httpd-cgi]
+
+
+
+ + +
top
+
+

Access Restriction

+ + + +

Blocking of Robots

+ + + +
+
Description:
+ +
+

How can we block a really annoying robot from + retrieving pages of a specific webarea? A + /robots.txt file containing entries of the + "Robot Exclusion Protocol" is typically not enough to get + rid of such a robot.

+
+ +
Solution:
+ +
+

We use a ruleset which forbids the URLs of the webarea + /~quux/foo/arc/ (perhaps a very deep + directory indexed area where the robot traversal would + create big server load). We have to make sure that we + forbid access only to the particular robot, i.e. just + forbidding the host where the robot runs is not enough. + This would block users from this host, too. We accomplish + this by also matching the User-Agent HTTP header + information.

+ +
+RewriteCond %{HTTP_USER_AGENT}   ^NameOfBadRobot.*
+RewriteCond %{REMOTE_ADDR}       ^123\.45\.67\.[8-9]$
+RewriteRule ^/~quux/foo/arc/.+   -   [F]
+
+
+
+ + + +

Blocked Inline-Images

+ + + +
+
Description:
+ +
+

Assume we have under http://www.quux-corp.de/~quux/ + some pages with inlined GIF graphics. These graphics are + nice, so others directly incorporate them via hyperlinks to + their pages. We don't like this practice because it adds + useless traffic to our server.

+
+ +
Solution:
+ +
+

While we cannot 100% protect the images from inclusion, + we can at least restrict the cases where the browser + sends a HTTP Referer header.

+ +
+RewriteCond %{HTTP_REFERER} !^$
+RewriteCond %{HTTP_REFERER} !^http://www.quux-corp.de/~quux/.*$ [NC]
+RewriteRule .*\.gif$        -                                    [F]
+
+ +
+RewriteCond %{HTTP_REFERER}         !^$
+RewriteCond %{HTTP_REFERER}         !.*/foo-with-gif\.html$
+RewriteRule ^inlined-in-foo\.gif$   -                        [F]
+
+
+
+ + + +

Proxy Deny

+ + + +
+
Description:
+ +
+

How can we forbid a certain host or even a user of a + special host from using the Apache proxy?

+
+ +
Solution:
+ +
+

We first have to make sure mod_rewrite + is below(!) mod_proxy in the Configuration + file when compiling the Apache webserver. This way it gets + called before mod_proxy. Then we + configure the following for a host-dependent deny...

+ +
+RewriteCond %{REMOTE_HOST} ^badhost\.mydomain\.com$
+RewriteRule !^http://[^/.]\.mydomain.com.*  - [F]
+
+ +

...and this one for a user@host-dependent deny:

+ +
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST}  ^badguy@badhost\.mydomain\.com$
+RewriteRule !^http://[^/.]\.mydomain.com.*  - [F]
+
+
+
+ + + +
top
+
+

Other

+ + + +

External Rewriting Engine

+ + + +
+
Description:
+ +
+

A FAQ: How can we solve the FOO/BAR/QUUX/etc. + problem? There seems no solution by the use of + mod_rewrite...

+
+ +
Solution:
+ +
+

Use an external RewriteMap, i.e. a program which acts + like a RewriteMap. It is run once on startup of Apache + receives the requested URLs on STDIN and has + to put the resulting (usually rewritten) URL on + STDOUT (same order!).

+ +
+RewriteEngine on
+RewriteMap    quux-map       prg:/path/to/map.quux.pl
+RewriteRule   ^/~quux/(.*)$  /~quux/${quux-map:$1}
+
+ +
+#!/path/to/perl
+
+#   disable buffered I/O which would lead
+#   to deadloops for the Apache server
+$| = 1;
+
+#   read URLs one per line from stdin and
+#   generate substitution URL on stdout
+while (<>) {
+    s|^foo/|bar/|;
+    print $_;
+}
+
+ +

This is a demonstration-only example and just rewrites + all URLs /~quux/foo/... to + /~quux/bar/.... Actually you can program + whatever you like. But notice that while such maps can be + used also by an average user, only the + system administrator can define it.

+
+
+ + + +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/rewrite/rewrite_guide_advanced.html b/docs/manual/rewrite/rewrite_guide_advanced.html new file mode 100644 index 00000000..07850dd6 --- /dev/null +++ b/docs/manual/rewrite/rewrite_guide_advanced.html @@ -0,0 +1,3 @@ +URI: rewrite_guide_advanced.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/rewrite/rewrite_guide_advanced.html.en b/docs/manual/rewrite/rewrite_guide_advanced.html.en new file mode 100644 index 00000000..b020eaa2 --- /dev/null +++ b/docs/manual/rewrite/rewrite_guide_advanced.html.en @@ -0,0 +1,1289 @@ + + + +URL Rewriting Guide - Advanced topics - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

URL Rewriting Guide - Advanced topics

+
+

Available Languages:  en 

+
+ + +

This document supplements the mod_rewrite + reference documentation. + It describes how one can use Apache's mod_rewrite + to solve typical URL-based problems with which webmasters are + commonony confronted. We give detailed descriptions on how to + solve each problem by configuring URL rewriting rulesets.

+ +
ATTENTION: Depending on your server configuration + it may be necessary to slightly change the examples for your + situation, e.g. adding the [PT] flag when + additionally using mod_alias and + mod_userdir, etc. Or rewriting a ruleset + to fit in .htaccess context instead + of per-server context. Always try to understand what a + particular ruleset really does before you use it. This + avoids many problems.
+ +
+ +
top
+
+

Webcluster through Homogeneous URL Layout

+ + + +
+
Description:
+ +
+

We want to create a homogeneous and consistent URL + layout over all WWW servers on a Intranet webcluster, i.e. + all URLs (per definition server local and thus server + dependent!) become actually server independent! + What we want is to give the WWW namespace a consistent + server-independent layout: no URL should have to include + any physically correct target server. The cluster itself + should drive us automatically to the physical target + host.

+
+ +
Solution:
+ +
+

First, the knowledge of the target servers come from + (distributed) external maps which contain information + where our users, groups and entities stay. The have the + form

+ +
+user1  server_of_user1
+user2  server_of_user2
+:      :
+
+ +

We put them into files map.xxx-to-host. + Second we need to instruct all servers to redirect URLs + of the forms

+ +
+/u/user/anypath
+/g/group/anypath
+/e/entity/anypath
+
+ +

to

+ +
+http://physical-host/u/user/anypath
+http://physical-host/g/group/anypath
+http://physical-host/e/entity/anypath
+
+ +

when the URL is not locally valid to a server. The + following ruleset does this for us by the help of the map + files (assuming that server0 is a default server which + will be used if a user has no entry in the map):

+ +
+RewriteEngine on
+
+RewriteMap      user-to-host   txt:/path/to/map.user-to-host
+RewriteMap     group-to-host   txt:/path/to/map.group-to-host
+RewriteMap    entity-to-host   txt:/path/to/map.entity-to-host
+
+RewriteRule   ^/u/([^/]+)/?(.*)   http://${user-to-host:$1|server0}/u/$1/$2
+RewriteRule   ^/g/([^/]+)/?(.*)  http://${group-to-host:$1|server0}/g/$1/$2
+RewriteRule   ^/e/([^/]+)/?(.*) http://${entity-to-host:$1|server0}/e/$1/$2
+
+RewriteRule   ^/([uge])/([^/]+)/?$          /$1/$2/.www/
+RewriteRule   ^/([uge])/([^/]+)/([^.]+.+)   /$1/$2/.www/$3\
+
+
+
+ +
top
+
+

Structured Homedirs

+ + + +
+
Description:
+ +
+

Some sites with thousands of users usually use a + structured homedir layout, i.e. each homedir is in a + subdirectory which begins for instance with the first + character of the username. So, /~foo/anypath + is /home/f/foo/.www/anypath + while /~bar/anypath is + /home/b/bar/.www/anypath.

+
+ +
Solution:
+ +
+

We use the following ruleset to expand the tilde URLs + into exactly the above layout.

+ +
+RewriteEngine on
+RewriteRule   ^/~(([a-z])[a-z0-9]+)(.*)  /home/$2/$1/.www$3
+
+
+
+ +
top
+
+

Filesystem Reorganization

+ + + +
+
Description:
+ +
+

This really is a hardcore example: a killer application + which heavily uses per-directory + RewriteRules to get a smooth look and feel + on the Web while its data structure is never touched or + adjusted. Background: net.sw is + my archive of freely available Unix software packages, + which I started to collect in 1992. It is both my hobby + and job to to this, because while I'm studying computer + science I have also worked for many years as a system and + network administrator in my spare time. Every week I need + some sort of software so I created a deep hierarchy of + directories where I stored the packages:

+ +
+drwxrwxr-x   2 netsw  users    512 Aug  3 18:39 Audio/
+drwxrwxr-x   2 netsw  users    512 Jul  9 14:37 Benchmark/
+drwxrwxr-x  12 netsw  users    512 Jul  9 00:34 Crypto/
+drwxrwxr-x   5 netsw  users    512 Jul  9 00:41 Database/
+drwxrwxr-x   4 netsw  users    512 Jul 30 19:25 Dicts/
+drwxrwxr-x  10 netsw  users    512 Jul  9 01:54 Graphic/
+drwxrwxr-x   5 netsw  users    512 Jul  9 01:58 Hackers/
+drwxrwxr-x   8 netsw  users    512 Jul  9 03:19 InfoSys/
+drwxrwxr-x   3 netsw  users    512 Jul  9 03:21 Math/
+drwxrwxr-x   3 netsw  users    512 Jul  9 03:24 Misc/
+drwxrwxr-x   9 netsw  users    512 Aug  1 16:33 Network/
+drwxrwxr-x   2 netsw  users    512 Jul  9 05:53 Office/
+drwxrwxr-x   7 netsw  users    512 Jul  9 09:24 SoftEng/
+drwxrwxr-x   7 netsw  users    512 Jul  9 12:17 System/
+drwxrwxr-x  12 netsw  users    512 Aug  3 20:15 Typesetting/
+drwxrwxr-x  10 netsw  users    512 Jul  9 14:08 X11/
+
+ +

In July 1996 I decided to make this archive public to + the world via a nice Web interface. "Nice" means that I + wanted to offer an interface where you can browse + directly through the archive hierarchy. And "nice" means + that I didn't wanted to change anything inside this + hierarchy - not even by putting some CGI scripts at the + top of it. Why? Because the above structure should be + later accessible via FTP as well, and I didn't want any + Web or CGI stuff to be there.

+
+ +
Solution:
+ +
+

The solution has two parts: The first is a set of CGI + scripts which create all the pages at all directory + levels on-the-fly. I put them under + /e/netsw/.www/ as follows:

+ +
+-rw-r--r--   1 netsw  users    1318 Aug  1 18:10 .wwwacl
+drwxr-xr-x  18 netsw  users     512 Aug  5 15:51 DATA/
+-rw-rw-rw-   1 netsw  users  372982 Aug  5 16:35 LOGFILE
+-rw-r--r--   1 netsw  users     659 Aug  4 09:27 TODO
+-rw-r--r--   1 netsw  users    5697 Aug  1 18:01 netsw-about.html
+-rwxr-xr-x   1 netsw  users     579 Aug  2 10:33 netsw-access.pl
+-rwxr-xr-x   1 netsw  users    1532 Aug  1 17:35 netsw-changes.cgi
+-rwxr-xr-x   1 netsw  users    2866 Aug  5 14:49 netsw-home.cgi
+drwxr-xr-x   2 netsw  users     512 Jul  8 23:47 netsw-img/
+-rwxr-xr-x   1 netsw  users   24050 Aug  5 15:49 netsw-lsdir.cgi
+-rwxr-xr-x   1 netsw  users    1589 Aug  3 18:43 netsw-search.cgi
+-rwxr-xr-x   1 netsw  users    1885 Aug  1 17:41 netsw-tree.cgi
+-rw-r--r--   1 netsw  users     234 Jul 30 16:35 netsw-unlimit.lst
+
+ +

The DATA/ subdirectory holds the above + directory structure, i.e. the real + net.sw stuff and gets + automatically updated via rdist from time to + time. The second part of the problem remains: how to link + these two structures together into one smooth-looking URL + tree? We want to hide the DATA/ directory + from the user while running the appropriate CGI scripts + for the various URLs. Here is the solution: first I put + the following into the per-directory configuration file + in the DocumentRoot + of the server to rewrite the announced URL + /net.sw/ to the internal path + /e/netsw:

+ +
+RewriteRule  ^net.sw$       net.sw/        [R]
+RewriteRule  ^net.sw/(.*)$  e/netsw/$1
+
+ +

The first rule is for requests which miss the trailing + slash! The second rule does the real thing. And then + comes the killer configuration which stays in the + per-directory config file + /e/netsw/.www/.wwwacl:

+ +
+Options       ExecCGI FollowSymLinks Includes MultiViews
+
+RewriteEngine on
+
+#  we are reached via /net.sw/ prefix
+RewriteBase   /net.sw/
+
+#  first we rewrite the root dir to
+#  the handling cgi script
+RewriteRule   ^$                       netsw-home.cgi     [L]
+RewriteRule   ^index\.html$            netsw-home.cgi     [L]
+
+#  strip out the subdirs when
+#  the browser requests us from perdir pages
+RewriteRule   ^.+/(netsw-[^/]+/.+)$    $1                 [L]
+
+#  and now break the rewriting for local files
+RewriteRule   ^netsw-home\.cgi.*       -                  [L]
+RewriteRule   ^netsw-changes\.cgi.*    -                  [L]
+RewriteRule   ^netsw-search\.cgi.*     -                  [L]
+RewriteRule   ^netsw-tree\.cgi$        -                  [L]
+RewriteRule   ^netsw-about\.html$      -                  [L]
+RewriteRule   ^netsw-img/.*$           -                  [L]
+
+#  anything else is a subdir which gets handled
+#  by another cgi script
+RewriteRule   !^netsw-lsdir\.cgi.*     -                  [C]
+RewriteRule   (.*)                     netsw-lsdir.cgi/$1
+
+ +

Some hints for interpretation:

+ +
    +
  1. Notice the L (last) flag and no + substitution field ('-') in the forth part
    2. + +
  2. Notice the ! (not) character and + the C (chain) flag at the first rule + in the last part
    3. + +
  3. Notice the catch-all pattern in the last rule
    4. +
+
+
+ +
top
+
+

Redirect Failing URLs To Other Webserver

+ + + +
+
Description:
+ +
+

A typical FAQ about URL rewriting is how to redirect + failing requests on webserver A to webserver B. Usually + this is done via ErrorDocument CGI-scripts in Perl, but + there is also a mod_rewrite solution. + But notice that this performs more poorly than using an + ErrorDocument + CGI-script!

+
+ +
Solution:
+ +
+

The first solution has the best performance but less + flexibility, and is less error safe:

+ +
+RewriteEngine on
+RewriteCond   /your/docroot/%{REQUEST_FILENAME} !-f
+RewriteRule   ^(.+)                             http://webserverB.dom/$1
+
+ +

The problem here is that this will only work for pages + inside the DocumentRoot. While you can add more + Conditions (for instance to also handle homedirs, etc.) + there is better variant:

+ +
+RewriteEngine on
+RewriteCond   %{REQUEST_URI} !-U
+RewriteRule   ^(.+)          http://webserverB.dom/$1
+
+ +

This uses the URL look-ahead feature of mod_rewrite. + The result is that this will work for all types of URLs + and is a safe way. But it does a performance impact on + the webserver, because for every request there is one + more internal subrequest. So, if your webserver runs on a + powerful CPU, use this one. If it is a slow machine, use + the first approach or better a ErrorDocument CGI-script.

+
+
+ +
top
+
+

Archive Access Multiplexer

+ + + +
+
Description:
+ +
+

Do you know the great CPAN (Comprehensive Perl Archive + Network) under http://www.perl.com/CPAN? + This does a redirect to one of several FTP servers around + the world which carry a CPAN mirror and is approximately + near the location of the requesting client. Actually this + can be called an FTP access multiplexing service. While + CPAN runs via CGI scripts, how can a similar approach + implemented via mod_rewrite?

+
+ +
Solution:
+ +
+

First we notice that from version 3.0.0 + mod_rewrite can + also use the "ftp:" scheme on redirects. + And second, the location approximation can be done by a + RewriteMap + over the top-level domain of the client. + With a tricky chained ruleset we can use this top-level + domain as a key to our multiplexing map.

+ +
+RewriteEngine on
+RewriteMap    multiplex                txt:/path/to/map.cxan
+RewriteRule   ^/CxAN/(.*)              %{REMOTE_HOST}::$1                 [C]
+RewriteRule   ^.+\.([a-zA-Z]+)::(.*)$  ${multiplex:$1|ftp.default.dom}$2  [R,L]
+
+ +
+##
+##  map.cxan -- Multiplexing Map for CxAN
+##
+
+de        ftp://ftp.cxan.de/CxAN/
+uk        ftp://ftp.cxan.uk/CxAN/
+com       ftp://ftp.cxan.com/CxAN/
+ :
+##EOF##
+
+
+
+ +
top
+
+

Content Handling

+ + + +

Browser Dependent Content

+ + + +
+
Description:
+ +
+

At least for important top-level pages it is sometimes + necessary to provide the optimum of browser dependent + content, i.e. one has to provide a maximum version for the + latest Netscape variants, a minimum version for the Lynx + browsers and a average feature version for all others.

+
+ +
Solution:
+ +
+

We cannot use content negotiation because the browsers do + not provide their type in that form. Instead we have to + act on the HTTP header "User-Agent". The following condig + does the following: If the HTTP header "User-Agent" + begins with "Mozilla/3", the page foo.html + is rewritten to foo.NS.html and and the + rewriting stops. If the browser is "Lynx" or "Mozilla" of + version 1 or 2 the URL becomes foo.20.html. + All other browsers receive page foo.32.html. + This is done by the following ruleset:

+ +
+RewriteCond %{HTTP_USER_AGENT}  ^Mozilla/3.*
+RewriteRule ^foo\.html$         foo.NS.html          [L]
+
+RewriteCond %{HTTP_USER_AGENT}  ^Lynx/.*         [OR]
+RewriteCond %{HTTP_USER_AGENT}  ^Mozilla/[12].*
+RewriteRule ^foo\.html$         foo.20.html          [L]
+
+RewriteRule ^foo\.html$         foo.32.html          [L]
+
+
+
+ + + +

Dynamic Mirror

+ + + +
+
Description:
+ +
+

Assume there are nice webpages on remote hosts we want + to bring into our namespace. For FTP servers we would use + the mirror program which actually maintains an + explicit up-to-date copy of the remote data on the local + machine. For a webserver we could use the program + webcopy which acts similar via HTTP. But both + techniques have one major drawback: The local copy is + always just as up-to-date as often we run the program. It + would be much better if the mirror is not a static one we + have to establish explicitly. Instead we want a dynamic + mirror with data which gets updated automatically when + there is need (updated data on the remote host).

+
+ +
Solution:
+ +
+

To provide this feature we map the remote webpage or even + the complete remote webarea to our namespace by the use + of the Proxy Throughput feature + (flag [P]):

+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^hotsheet/(.*)$  http://www.tstimpreso.com/hotsheet/$1  [P]
+
+ +
+RewriteEngine  on
+RewriteBase    /~quux/
+RewriteRule    ^usa-news\.html$   http://www.quux-corp.com/news/index.html  [P]
+
+
+
+ + + +

Reverse Dynamic Mirror

+ + + +
+
Description:
+ +
...
+ +
Solution:
+ +
+
+RewriteEngine on
+RewriteCond   /mirror/of/remotesite/$1           -U
+RewriteRule   ^http://www\.remotesite\.com/(.*)$ /mirror/of/remotesite/$1
+
+
+
+ + + +

Retrieve Missing Data from Intranet

+ + + +
+
Description:
+ +
+

This is a tricky way of virtually running a corporate + (external) Internet webserver + (www.quux-corp.dom), while actually keeping + and maintaining its data on a (internal) Intranet webserver + (www2.quux-corp.dom) which is protected by a + firewall. The trick is that on the external webserver we + retrieve the requested data on-the-fly from the internal + one.

+
+ +
Solution:
+ +
+

First, we have to make sure that our firewall still + protects the internal webserver and that only the + external webserver is allowed to retrieve data from it. + For a packet-filtering firewall we could for instance + configure a firewall ruleset like the following:

+ +
+ALLOW Host www.quux-corp.dom Port >1024 --> Host www2.quux-corp.dom Port 80
+DENY  Host *                 Port *     --> Host www2.quux-corp.dom Port 80
+
+ +

Just adjust it to your actual configuration syntax. + Now we can establish the mod_rewrite + rules which request the missing data in the background + through the proxy throughput feature:

+ +
+RewriteRule ^/~([^/]+)/?(.*)          /home/$1/.www/$2
+RewriteCond %{REQUEST_FILENAME}       !-f
+RewriteCond %{REQUEST_FILENAME}       !-d
+RewriteRule ^/home/([^/]+)/.www/?(.*) http://www2.quux-corp.dom/~$1/pub/$2 [P]
+
+
+
+ + + +

Load Balancing

+ + + +
+
Description:
+ +
+

Suppose we want to load balance the traffic to + www.foo.com over www[0-5].foo.com + (a total of 6 servers). How can this be done?

+
+ +
Solution:
+ +
+

There are a lot of possible solutions for this problem. + We will discuss first a commonly known DNS-based variant + and then the special one with mod_rewrite:

+ +
    +
  1. + DNS Round-Robin + +

    The simplest method for load-balancing is to use + the DNS round-robin feature of BIND. + Here you just configure www[0-9].foo.com + as usual in your DNS with A(address) records, e.g.

    + +
    +www0   IN  A       1.2.3.1
+www1   IN  A       1.2.3.2
+www2   IN  A       1.2.3.3
+www3   IN  A       1.2.3.4
+www4   IN  A       1.2.3.5
+www5   IN  A       1.2.3.6
+
    + +

    Then you additionally add the following entry:

    + +
    +www    IN  CNAME   www0.foo.com.
+       IN  CNAME   www1.foo.com.
+       IN  CNAME   www2.foo.com.
+       IN  CNAME   www3.foo.com.
+       IN  CNAME   www4.foo.com.
+       IN  CNAME   www5.foo.com.
+       IN  CNAME   www6.foo.com.
+
    + +

    Notice that this seems wrong, but is actually an + intended feature of BIND and can be used + in this way. However, now when www.foo.com gets + resolved, BIND gives out www0-www6 + - but in a slightly permutated/rotated order every time. + This way the clients are spread over the various + servers. But notice that this not a perfect load + balancing scheme, because DNS resolve information + gets cached by the other nameservers on the net, so + once a client has resolved www.foo.com + to a particular wwwN.foo.com, all + subsequent requests also go to this particular name + wwwN.foo.com. But the final result is + ok, because the total sum of the requests are really + spread over the various webservers.

    +
    2. + +
  2. + DNS Load-Balancing + +

    A sophisticated DNS-based method for + load-balancing is to use the program + lbnamed which can be found at + http://www.stanford.edu/~schemers/docs/lbnamed/lbnamed.html. + It is a Perl 5 program in conjunction with auxilliary + tools which provides a real load-balancing for + DNS.

    +
    3. + +
  3. + Proxy Throughput Round-Robin + +

    In this variant we use mod_rewrite + and its proxy throughput feature. First we dedicate + www0.foo.com to be actually + www.foo.com by using a single

    + +
    +www    IN  CNAME   www0.foo.com.
+
    + +

    entry in the DNS. Then we convert + www0.foo.com to a proxy-only server, + i.e. we configure this machine so all arriving URLs + are just pushed through the internal proxy to one of + the 5 other servers (www1-www5). To + accomplish this we first establish a ruleset which + contacts a load balancing script lb.pl + for all URLs.

    + +
    +RewriteEngine on
+RewriteMap    lb      prg:/path/to/lb.pl
+RewriteRule   ^/(.+)$ ${lb:$1}           [P,L]
+
    + +

    Then we write lb.pl:

    + +
    +#!/path/to/perl
+##
+##  lb.pl -- load balancing script
+##
+
+$| = 1;
+
+$name   = "www";     # the hostname base
+$first  = 1;         # the first server (not 0 here, because 0 is myself)
+$last   = 5;         # the last server in the round-robin
+$domain = "foo.dom"; # the domainname
+
+$cnt = 0;
+while (<STDIN>) {
+    $cnt = (($cnt+1) % ($last+1-$first));
+    $server = sprintf("%s%d.%s", $name, $cnt+$first, $domain);
+    print "http://$server/$_";
+}
+
+##EOF##
+
    + +
    A last notice: Why is this useful? Seems like + www0.foo.com still is overloaded? The + answer is yes, it is overloaded, but with plain proxy + throughput requests, only! All SSI, CGI, ePerl, etc. + processing is completely done on the other machines. + This is the essential point.
    +
    4. + +
  4. + Hardware/TCP Round-Robin + +

    There is a hardware solution available, too. Cisco + has a beast called LocalDirector which does a load + balancing at the TCP/IP level. Actually this is some + sort of a circuit level gateway in front of a + webcluster. If you have enough money and really need + a solution with high performance, use this one.

    +
    5. +
+
+
+ + + +

New MIME-type, New Service

+ + + +
+
Description:
+ +
+

On the net there are a lot of nifty CGI programs. But + their usage is usually boring, so a lot of webmaster + don't use them. Even Apache's Action handler feature for + MIME-types is only appropriate when the CGI programs + don't need special URLs (actually PATH_INFO + and QUERY_STRINGS) as their input. First, + let us configure a new file type with extension + .scgi (for secure CGI) which will be processed + by the popular cgiwrap program. The problem + here is that for instance we use a Homogeneous URL Layout + (see above) a file inside the user homedirs has the URL + /u/user/foo/bar.scgi. But + cgiwrap needs the URL in the form + /~user/foo/bar.scgi/. The following rule + solves the problem:

+ +
+RewriteRule ^/[uge]/([^/]+)/\.www/(.+)\.scgi(.*) ...
+... /internal/cgi/user/cgiwrap/~$1/$2.scgi$3  [NS,T=application/x-http-cgi]
+
+ +

Or assume we have some more nifty programs: + wwwlog (which displays the + access.log for a URL subtree and + wwwidx (which runs Glimpse on a URL + subtree). We have to provide the URL area to these + programs so they know on which area they have to act on. + But usually this ugly, because they are all the times + still requested from that areas, i.e. typically we would + run the swwidx program from within + /u/user/foo/ via hyperlink to

+ +
+/internal/cgi/user/swwidx?i=/u/user/foo/
+
+ +

which is ugly. Because we have to hard-code + both the location of the area + and the location of the CGI inside the + hyperlink. When we have to reorganize the area, we spend a + lot of time changing the various hyperlinks.

+
+ +
Solution:
+ +
+

The solution here is to provide a special new URL format + which automatically leads to the proper CGI invocation. + We configure the following:

+ +
+RewriteRule   ^/([uge])/([^/]+)(/?.*)/\*  /internal/cgi/user/wwwidx?i=/$1/$2$3/
+RewriteRule   ^/([uge])/([^/]+)(/?.*):log /internal/cgi/user/wwwlog?f=/$1/$2$3
+
+ +

Now the hyperlink to search at + /u/user/foo/ reads only

+ +
+HREF="*"
+
+ +

which internally gets automatically transformed to

+ +
+/internal/cgi/user/wwwidx?i=/u/user/foo/
+
+ +

The same approach leads to an invocation for the + access log CGI program when the hyperlink + :log gets used.

+
+
+ + + +

On-the-fly Content-Regeneration

+ + + +
+
Description:
+ +
+

Here comes a really esoteric feature: Dynamically + generated but statically served pages, i.e. pages should be + delivered as pure static pages (read from the filesystem + and just passed through), but they have to be generated + dynamically by the webserver if missing. This way you can + have CGI-generated pages which are statically served unless + one (or a cronjob) removes the static contents. Then the + contents gets refreshed.

+
+ +
Solution:
+ +
+ This is done via the following ruleset: + +
+RewriteCond %{REQUEST_FILENAME}   !-s
+RewriteRule ^page\.html$          page.cgi   [T=application/x-httpd-cgi,L]
+
+ +

Here a request to page.html leads to a + internal run of a corresponding page.cgi if + page.html is still missing or has filesize + null. The trick here is that page.cgi is a + usual CGI script which (additionally to its STDOUT) + writes its output to the file page.html. + Once it was run, the server sends out the data of + page.html. When the webmaster wants to force + a refresh the contents, he just removes + page.html (usually done by a cronjob).

+
+
+ + + +

Document With Autorefresh

+ + + +
+
Description:
+ +
+

Wouldn't it be nice while creating a complex webpage if + the webbrowser would automatically refresh the page every + time we write a new version from within our editor? + Impossible?

+
+ +
Solution:
+ +
+

No! We just combine the MIME multipart feature, the + webserver NPH feature and the URL manipulation power of + mod_rewrite. First, we establish a new + URL feature: Adding just :refresh to any + URL causes this to be refreshed every time it gets + updated on the filesystem.

+ +
+RewriteRule   ^(/[uge]/[^/]+/?.*):refresh  /internal/cgi/apache/nph-refresh?f=$1
+
+ +

Now when we reference the URL

+ +
+/u/foo/bar/page.html:refresh
+
+ +

this leads to the internal invocation of the URL

+ +
+/internal/cgi/apache/nph-refresh?f=/u/foo/bar/page.html
+
+ +

The only missing part is the NPH-CGI script. Although + one would usually say "left as an exercise to the reader" + ;-) I will provide this, too.

+ +
+#!/sw/bin/perl
+##
+##  nph-refresh -- NPH/CGI script for auto refreshing pages
+##  Copyright (c) 1997 Ralf S. Engelschall, All Rights Reserved.
+##
+$| = 1;
+
+#   split the QUERY_STRING variable
+@pairs = split(/&/, $ENV{'QUERY_STRING'});
+foreach $pair (@pairs) {
+    ($name, $value) = split(/=/, $pair);
+    $name =~ tr/A-Z/a-z/;
+    $name = 'QS_' . $name;
+    $value =~ s/%([a-fA-F0-9][a-fA-F0-9])/pack("C", hex($1))/eg;
+    eval "\$$name = \"$value\"";
+}
+$QS_s = 1 if ($QS_s eq '');
+$QS_n = 3600 if ($QS_n eq '');
+if ($QS_f eq '') {
+    print "HTTP/1.0 200 OK\n";
+    print "Content-type: text/html\n\n";
+    print "&lt;b&gt;ERROR&lt;/b&gt;: No file given\n";
+    exit(0);
+}
+if (! -f $QS_f) {
+    print "HTTP/1.0 200 OK\n";
+    print "Content-type: text/html\n\n";
+    print "&lt;b&gt;ERROR&lt;/b&gt;: File $QS_f not found\n";
+    exit(0);
+}
+
+sub print_http_headers_multipart_begin {
+    print "HTTP/1.0 200 OK\n";
+    $bound = "ThisRandomString12345";
+    print "Content-type: multipart/x-mixed-replace;boundary=$bound\n";
+    &print_http_headers_multipart_next;
+}
+
+sub print_http_headers_multipart_next {
+    print "\n--$bound\n";
+}
+
+sub print_http_headers_multipart_end {
+    print "\n--$bound--\n";
+}
+
+sub displayhtml {
+    local($buffer) = @_;
+    $len = length($buffer);
+    print "Content-type: text/html\n";
+    print "Content-length: $len\n\n";
+    print $buffer;
+}
+
+sub readfile {
+    local($file) = @_;
+    local(*FP, $size, $buffer, $bytes);
+    ($x, $x, $x, $x, $x, $x, $x, $size) = stat($file);
+    $size = sprintf("%d", $size);
+    open(FP, "&lt;$file");
+    $bytes = sysread(FP, $buffer, $size);
+    close(FP);
+    return $buffer;
+}
+
+$buffer = &readfile($QS_f);
+&print_http_headers_multipart_begin;
+&displayhtml($buffer);
+
+sub mystat {
+    local($file) = $_[0];
+    local($time);
+
+    ($x, $x, $x, $x, $x, $x, $x, $x, $x, $mtime) = stat($file);
+    return $mtime;
+}
+
+$mtimeL = &mystat($QS_f);
+$mtime = $mtime;
+for ($n = 0; $n &lt; $QS_n; $n++) {
+    while (1) {
+        $mtime = &mystat($QS_f);
+        if ($mtime ne $mtimeL) {
+            $mtimeL = $mtime;
+            sleep(2);
+            $buffer = &readfile($QS_f);
+            &print_http_headers_multipart_next;
+            &displayhtml($buffer);
+            sleep(5);
+            $mtimeL = &mystat($QS_f);
+            last;
+        }
+        sleep($QS_s);
+    }
+}
+
+&print_http_headers_multipart_end;
+
+exit(0);
+
+##EOF##
+
+
+
+ + + +

Mass Virtual Hosting

+ + + +
+
Description:
+ +
+

The <VirtualHost> feature of Apache is nice + and works great when you just have a few dozens + virtual hosts. But when you are an ISP and have hundreds of + virtual hosts to provide this feature is not the best + choice.

+
+ +
Solution:
+ +
+

To provide this feature we map the remote webpage or even + the complete remote webarea to our namespace by the use + of the Proxy Throughput feature (flag [P]):

+ +
+##
+##  vhost.map
+##
+www.vhost1.dom:80  /path/to/docroot/vhost1
+www.vhost2.dom:80  /path/to/docroot/vhost2
+     :
+www.vhostN.dom:80  /path/to/docroot/vhostN
+
+ +
+##
+##  httpd.conf
+##
+    :
+#   use the canonical hostname on redirects, etc.
+UseCanonicalName on
+
+    :
+#   add the virtual host in front of the CLF-format
+CustomLog  /path/to/access_log  "%{VHOST}e %h %l %u %t \"%r\" %>s %b"
+    :
+
+#   enable the rewriting engine in the main server
+RewriteEngine on
+
+#   define two maps: one for fixing the URL and one which defines
+#   the available virtual hosts with their corresponding
+#   DocumentRoot.
+RewriteMap    lowercase    int:tolower
+RewriteMap    vhost        txt:/path/to/vhost.map
+
+#   Now do the actual virtual host mapping
+#   via a huge and complicated single rule:
+#
+#   1. make sure we don't map for common locations
+RewriteCond   %{REQUEST_URI}  !^/commonurl1/.*
+RewriteCond   %{REQUEST_URI}  !^/commonurl2/.*
+    :
+RewriteCond   %{REQUEST_URI}  !^/commonurlN/.*
+#
+#   2. make sure we have a Host header, because
+#      currently our approach only supports
+#      virtual hosting through this header
+RewriteCond   %{HTTP_HOST}  !^$
+#
+#   3. lowercase the hostname
+RewriteCond   ${lowercase:%{HTTP_HOST}|NONE}  ^(.+)$
+#
+#   4. lookup this hostname in vhost.map and
+#      remember it only when it is a path
+#      (and not "NONE" from above)
+RewriteCond   ${vhost:%1}  ^(/.*)$
+#
+#   5. finally we can map the URL to its docroot location
+#      and remember the virtual host for logging puposes
+RewriteRule   ^/(.*)$   %1/$1  [E=VHOST:${lowercase:%{HTTP_HOST}}]
+    :
+
+
+
+ + + +
top
+
+

Access Restriction

+ + + +

Host Deny

+ + + +
+
Description:
+ +
+

How can we forbid a list of externally configured hosts + from using our server?

+
+ +
Solution:
+ +
+

For Apache >= 1.3b6:

+ +
+RewriteEngine on
+RewriteMap    hosts-deny  txt:/path/to/hosts.deny
+RewriteCond   ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR]
+RewriteCond   ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND} !=NOT-FOUND
+RewriteRule   ^/.*  -  [F]
+
+ +

For Apache <= 1.3b6:

+ +
+RewriteEngine on
+RewriteMap    hosts-deny  txt:/path/to/hosts.deny
+RewriteRule   ^/(.*)$ ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND}/$1
+RewriteRule   !^NOT-FOUND/.* - [F]
+RewriteRule   ^NOT-FOUND/(.*)$ ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND}/$1
+RewriteRule   !^NOT-FOUND/.* - [F]
+RewriteRule   ^NOT-FOUND/(.*)$ /$1
+
+ +
+##
+##  hosts.deny
+##
+##  ATTENTION! This is a map, not a list, even when we treat it as such.
+##             mod_rewrite parses it for key/value pairs, so at least a
+##             dummy value "-" must be present for each entry.
+##
+
+193.102.180.41 -
+bsdti1.sdm.de  -
+192.76.162.40  -
+
+
+
+ + + +

Proxy Deny

+ + + +
+
Description:
+ +
+

How can we forbid a certain host or even a user of a + special host from using the Apache proxy?

+
+ +
Solution:
+ +
+

We first have to make sure mod_rewrite + is below(!) mod_proxy in the Configuration + file when compiling the Apache webserver. This way it gets + called before mod_proxy. Then we + configure the following for a host-dependent deny...

+ +
+RewriteCond %{REMOTE_HOST} ^badhost\.mydomain\.com$
+RewriteRule !^http://[^/.]\.mydomain.com.*  - [F]
+
+ +

...and this one for a user@host-dependent deny:

+ +
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST}  ^badguy@badhost\.mydomain\.com$
+RewriteRule !^http://[^/.]\.mydomain.com.*  - [F]
+
+
+
+ + + +

Special Authentication Variant

+ + + +
+
Description:
+ +
+

Sometimes a very special authentication is needed, for + instance a authentication which checks for a set of + explicitly configured users. Only these should receive + access and without explicit prompting (which would occur + when using the Basic Auth via mod_auth).

+
+ +
Solution:
+ +
+

We use a list of rewrite conditions to exclude all except + our friends:

+ +
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend1@client1.quux-corp\.com$
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend2@client2.quux-corp\.com$
+RewriteCond %{REMOTE_IDENT}@%{REMOTE_HOST} !^friend3@client3.quux-corp\.com$
+RewriteRule ^/~quux/only-for-friends/      -                                 [F]
+
+
+
+ + + +

Referer-based Deflector

+ + + +
+
Description:
+ +
+

How can we program a flexible URL Deflector which acts + on the "Referer" HTTP header and can be configured with as + many referring pages as we like?

+
+ +
Solution:
+ +
+

Use the following really tricky ruleset...

+ +
+RewriteMap  deflector txt:/path/to/deflector.map
+
+RewriteCond %{HTTP_REFERER} !=""
+RewriteCond ${deflector:%{HTTP_REFERER}} ^-$
+RewriteRule ^.* %{HTTP_REFERER} [R,L]
+
+RewriteCond %{HTTP_REFERER} !=""
+RewriteCond ${deflector:%{HTTP_REFERER}|NOT-FOUND} !=NOT-FOUND
+RewriteRule ^.* ${deflector:%{HTTP_REFERER}} [R,L]
+
+ +

... in conjunction with a corresponding rewrite + map:

+ +
+##
+##  deflector.map
+##
+
+http://www.badguys.com/bad/index.html    -
+http://www.badguys.com/bad/index2.html   -
+http://www.badguys.com/bad/index3.html   http://somewhere.com/
+
+ +

This automatically redirects the request back to the + referring page (when "-" is used as the value + in the map) or to a specific URL (when an URL is specified + in the map as the second argument).

+
+
+ + + +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/rewrite/rewrite_intro.html b/docs/manual/rewrite/rewrite_intro.html new file mode 100644 index 00000000..607f1c18 --- /dev/null +++ b/docs/manual/rewrite/rewrite_intro.html @@ -0,0 +1,3 @@ +URI: rewrite_intro.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/rewrite/rewrite_intro.html.en b/docs/manual/rewrite/rewrite_intro.html.en new file mode 100644 index 00000000..78bfde42 --- /dev/null +++ b/docs/manual/rewrite/rewrite_intro.html.en @@ -0,0 +1,196 @@ + + + +Apache mod_rewrite Introduction - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Apache mod_rewrite Introduction

+
+

Available Languages:  en 

+
+ +

This document supplements the mod_rewrite +reference documentation. It +describes the basic concepts necessary for use of +mod_rewrite. Other documents go into greater detail, +but this doc should help the beginner get their feet wet. +

+
+ +
top
+
+

Introduction

+

The Apache module mod_rewrite is a very powerful and +sophisticated module which provides a way to do URL manipulations. With +it, you can do nearly all types of URL rewriting that you may need. It +is, however, somewhat complex, and may be intimidating to the beginner. +There is also a tendency to treat rewrite rules as magic incantation, +using them without actually understanding what they do.

+ +

This document attempts to give sufficient background so that what +follows is understood, rather than just copied blindly. +

+
top
+
+

Regular Expressions

+ +

mod_rewrite uses the Perl Compatible +Regular Expression vocabulary. In this document, we do not attempt +to provide a detailed reference to regular expressions. For that, we +recommend the PCRE man pages, the +Perl regular +expression man page, and Mastering +Regular Expressions, by Jeffrey Friedl.

+ +

In this document, we attempt to provide enough of a regex vocabulary +to get you started, without being overwhelming, in the hope that +RewriteRules will be scientific +formulae, rather than magical incantations.

+ +

Regex vocabulary

+ +

The following are the minimal building blocks you will need, in order +to write regular expressions and RewriteRules. They certainly do not +represent a complete regular expression vocabulary, but they are a good +place to start, and should help you read basic regular expressions, as +well as write your own.

+ + + + + + + + + + + + + + + + + + + +
CharacterMeaningExample
.Matches any +characterc.t will match cat, +cot, cut, etc.
+Repeats the previous match one or more +timesa+ matches a, aa, +aaa, etc
*Repeats the previous match zero or more +times.a* matches all the same things +a+ matches, but will also match an empty string.
?Makes the match optional.
.Matches any +charactercolou?r will match color and +colour.
^Called an anchor, matches the beginning +of the string^a matches a string that begins with +a
$The other anchor, this matches the end of +the string.a$ matches a string that ends with +a.
( )Groups several characters into a single +unit, and captures a match for use in a backreference.(ab)+ +matches ababab - that is, the + applies to the group. +For more on backreferences see below.
[ ]A character class - matches one of the +charactersc[uoa]t matches cut, +cot or cat.
!NotNegates a match - that is, +ensures that it does not match.
+ + + +

Regex Back-Reference Availability

+ +

One important thing here has to be remembered: Whenever you + use parentheses in Pattern or in one of the + CondPattern, back-references are internally created + which can be used with the strings $N and + %N (see below). These are available for creating + the strings Substitution and TestString. + Figure 2 shows to which locations the back-references are + transferred for expansion.

+ +

+ [Needs graphics capability to display]
+ Figure 2: The back-reference flow through a rule. +

+ + +
top
+
+

RewriteRule basics

+

+Basic anatomy of a RewriteRule, with exhaustively annotated simple +examples. +

+
top
+
+

Rewrite Flags

+

Discussion of the flags to RewriteRule, and when and why one might +use them.

+
top
+
+

Rewrite conditions

+

Discussion of RewriteCond, looping, and other related concepts. +

+
top
+
+

Rewrite maps

+

Discussion of RewriteMap, including simple, but heavily annotated, +examples.

+
top
+
+

.htaccess files

+

Discussion of the differences between rewrite rules in httpd.conf and +in .htaccess files.

+
top
+
+

Environment Variables

+ +

This module keeps track of two additional (non-standard) +CGI/SSI environment variables named SCRIPT_URL +and SCRIPT_URI. These contain the +logical Web-view to the current resource, while the +standard CGI/SSI variables SCRIPT_NAME and +SCRIPT_FILENAME contain the physical +System-view.

+ +

Notice: These variables hold the URI/URL as they were +initially requested, i.e., before any +rewriting. This is important because the rewriting process is +primarily used to rewrite logical URLs to physical +pathnames.

+ +

Example

+SCRIPT_NAME=/sw/lib/w3s/tree/global/u/rse/.www/index.html
+SCRIPT_FILENAME=/u/rse/.www/index.html
+SCRIPT_URL=/u/rse/
+SCRIPT_URI=http://en1.engelschall.com/u/rse/
+
+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/rewrite/rewrite_tech.html b/docs/manual/rewrite/rewrite_tech.html new file mode 100644 index 00000000..4e06869f --- /dev/null +++ b/docs/manual/rewrite/rewrite_tech.html @@ -0,0 +1,3 @@ +URI: rewrite_tech.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/rewrite/rewrite_tech.html.en b/docs/manual/rewrite/rewrite_tech.html.en new file mode 100644 index 00000000..943a8c7a --- /dev/null +++ b/docs/manual/rewrite/rewrite_tech.html.en @@ -0,0 +1,167 @@ + + + +Apache mod_rewrite Technical Details - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Apache mod_rewrite Technical Details

+
+

Available Languages:  en 

+
+ +

This document discusses some of the technical details of mod_rewrite +and URL matching.

+
+ +
top
+
+

Internal Processing

+ +

The internal processing of this module is very complex but + needs to be explained once even to the average user to avoid + common mistakes and to let you exploit its full + functionality.

+
top
+
+

API Phases

+ +

First you have to understand that when Apache processes a + HTTP request it does this in phases. A hook for each of these + phases is provided by the Apache API. Mod_rewrite uses two of + these hooks: the URL-to-filename translation hook which is + used after the HTTP request has been read but before any + authorization starts and the Fixup hook which is triggered + after the authorization phases and after the per-directory + config files (.htaccess) have been read, but + before the content handler is activated.

+ +

So, after a request comes in and Apache has determined the + corresponding server (or virtual server) the rewriting engine + starts processing of all mod_rewrite directives from the + per-server configuration in the URL-to-filename phase. A few + steps later when the final data directories are found, the + per-directory configuration directives of mod_rewrite are + triggered in the Fixup phase. In both situations mod_rewrite + rewrites URLs either to new URLs or to filenames, although + there is no obvious distinction between them. This is a usage + of the API which was not intended to be this way when the API + was designed, but as of Apache 1.x this is the only way + mod_rewrite can operate. To make this point more clear + remember the following two points:

+ +
    +
  1. Although mod_rewrite rewrites URLs to URLs, URLs to + filenames and even filenames to filenames, the API + currently provides only a URL-to-filename hook. In Apache + 2.0 the two missing hooks will be added to make the + processing more clear. But this point has no drawbacks for + the user, it is just a fact which should be remembered: + Apache does more in the URL-to-filename hook than the API + intends for it.
    2. + +
  2. + Unbelievably mod_rewrite provides URL manipulations in + per-directory context, i.e., within + .htaccess files, although these are reached + a very long time after the URLs have been translated to + filenames. It has to be this way because + .htaccess files live in the filesystem, so + processing has already reached this stage. In other + words: According to the API phases at this time it is too + late for any URL manipulations. To overcome this chicken + and egg problem mod_rewrite uses a trick: When you + manipulate a URL/filename in per-directory context + mod_rewrite first rewrites the filename back to its + corresponding URL (which is usually impossible, but see + the RewriteBase directive below for the + trick to achieve this) and then initiates a new internal + sub-request with the new URL. This restarts processing of + the API phases. + +

    Again mod_rewrite tries hard to make this complicated + step totally transparent to the user, but you should + remember here: While URL manipulations in per-server + context are really fast and efficient, per-directory + rewrites are slow and inefficient due to this chicken and + egg problem. But on the other hand this is the only way + mod_rewrite can provide (locally restricted) URL + manipulations to the average user.

    +
    3. +
+ +

Don't forget these two points!

+
top
+
+

Ruleset Processing

+ +

Now when mod_rewrite is triggered in these two API phases, it + reads the configured rulesets from its configuration + structure (which itself was either created on startup for + per-server context or during the directory walk of the Apache + kernel for per-directory context). Then the URL rewriting + engine is started with the contained ruleset (one or more + rules together with their conditions). The operation of the + URL rewriting engine itself is exactly the same for both + configuration contexts. Only the final result processing is + different.

+ +

The order of rules in the ruleset is important because the + rewriting engine processes them in a special (and not very + obvious) order. The rule is this: The rewriting engine loops + through the ruleset rule by rule (RewriteRule directives) and + when a particular rule matches it optionally loops through + existing corresponding conditions (RewriteCond + directives). For historical reasons the conditions are given + first, and so the control flow is a little bit long-winded. See + Figure 1 for more details.

+

+ [Needs graphics capability to display]
+ Figure 1:The control flow through the rewriting ruleset +

+

As you can see, first the URL is matched against the + Pattern of each rule. When it fails mod_rewrite + immediately stops processing this rule and continues with the + next rule. If the Pattern matches, mod_rewrite looks + for corresponding rule conditions. If none are present, it + just substitutes the URL with a new value which is + constructed from the string Substitution and goes on + with its rule-looping. But if conditions exist, it starts an + inner loop for processing them in the order that they are + listed. For conditions the logic is different: we don't match + a pattern against the current URL. Instead we first create a + string TestString by expanding variables, + back-references, map lookups, etc. and then we try + to match CondPattern against it. If the pattern + doesn't match, the complete set of conditions and the + corresponding rule fails. If the pattern matches, then the + next condition is processed until no more conditions are + available. If all conditions match, processing is continued + with the substitution of the URL with + Substitution.

+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/sections.html b/docs/manual/sections.html new file mode 100644 index 00000000..02645f01 --- /dev/null +++ b/docs/manual/sections.html @@ -0,0 +1,11 @@ +URI: sections.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: sections.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: sections.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/sections.html.en b/docs/manual/sections.html.en new file mode 100644 index 00000000..06580ccc --- /dev/null +++ b/docs/manual/sections.html.en @@ -0,0 +1,477 @@ + + + +Configuration Sections - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Configuration Sections

+
+

Available Languages:  en  | + ja  | + ko 

+
+

Directives in the configuration files may apply to the +entire server, or they may be restricted to apply only to particular +directories, files, hosts, or URLs. This document describes how to +use configuration section containers or .htaccess files +to change the scope of other configuration directives.

+
+ +
top
+
+

Types of Configuration Section Containers

+ +
Related ModulesRelated Directives
+ +

There are two basic types of containers. Most containers are +evaluated for each request. The enclosed directives are applied only +for those requests that match the containers. The <IfDefine>, <IfModule>, and +<IfVersion> +containers, on the other hand, are evaluated only at server startup +and restart. If their conditions are true at startup, then the +enclosed directives will apply to all requests. If the conditions are +not true, the enclosed directives will be ignored.

+ +

The <IfDefine> directive +encloses directives that will only be applied if an appropriate +parameter is defined on the httpd command line. For example, +with the following configuration, all requests will be redirected +to another site only if the server is started using +httpd -DClosedForNow:

+ +

+<IfDefine ClosedForNow>
+Redirect / http://otherserver.example.com/
+</IfDefine> +

+ +

The <IfModule> +directive is very similar, except it encloses directives that will +only be applied if a particular module is available in the server. +The module must either be statically compiled in the server, or it +must be dynamically compiled and its LoadModule line must be earlier in the +configuration file. This directive should only be used if you need +your configuration file to work whether or not certain modules are +installed. It should not be used to enclose directives that you want +to work all the time, because it can suppress useful error messages +about missing modules.

+ +

In the following example, the MimeMagicFiles directive will be +applied only if mod_mime_magic is available.

+ +

+<IfModule mod_mime_magic.c>
+MimeMagicFile conf/magic
+</IfModule> +

+ +

The <IfVersion> +directive is very similar to <IfDefine> and <IfModule>, except it encloses directives that will +only be applied if a particular version of the server is executing. This +module is designed for the use in test suites and large networks which have to +deal with different httpd versions and different configurations.

+ +

+ <IfVersion >= 2.1>
+ + # this happens only in versions greater or
+ # equal 2.1.0.
+ + </IfVersion> +

+ +

<IfDefine>, +<IfModule>, and the +<IfVersion> +can apply negative conditions by preceding their test with "!". +Also, these sections can be nested to achieve more complex +restrictions.

+
top
+
+

Filesystem and Webspace

+ +

The most commonly used configuration section containers are the +ones that change the configuration of particular places in the +filesystem or webspace. First, it is important to understand the +difference between the two. The filesystem is the view of your disks +as seen by your operating system. For example, in a default install, +Apache resides at /usr/local/apache2 in the Unix +filesystem or "c:/Program Files/Apache Group/Apache2" in +the Windows filesystem. (Note that forward slashes should always be +used as the path separator in Apache, even for Windows.) In contrast, +the webspace is the view of your site as delivered by the web server +and seen by the client. So the path /dir/ in the +webspace corresponds to the path +/usr/local/apache2/htdocs/dir/ in the filesystem of a +default Apache install on Unix. The webspace need not map directly to +the filesystem, since webpages may be generated dynamically +from databases or other locations.

+ +

Filesystem Containers

+ +

The <Directory> +and <Files> +directives, along with their regex +counterparts, apply directives to +parts of the filesystem. Directives enclosed in a <Directory> section apply to +the named filesystem directory and all subdirectories of that +directory. The same effect can be obtained using .htaccess files. For example, in the +following configuration, directory indexes will be enabled for the +/var/web/dir1 directory and all subdirectories.

+ +

+<Directory /var/web/dir1>
+Options +Indexes
+</Directory> +

+ +

Directives enclosed in a <Files> section apply to any file with +the specified name, regardless of what directory it lies in. +So for example, the following configuration directives will, +when placed in the main section of the configuration file, +deny access to any file named private.html regardless +of where it is found.

+ +

+<Files private.html>
+Order allow,deny
+Deny from all
+</Files> +

+ +

To address files found in a particular part of the filesystem, the +<Files> and +<Directory> sections +can be combined. For example, the following configuration will deny +access to /var/web/dir1/private.html, +/var/web/dir1/subdir2/private.html, +/var/web/dir1/subdir3/private.html, and any other instance +of private.html found under the /var/web/dir1/ +directory.

+ +

+<Directory /var/web/dir1>
+<Files private.html>
+Order allow,deny
+Deny from all
+</Files>
+</Directory> +

+ + +

Webspace Containers

+ +

The <Location> +directive and its regex counterpart, on the +other hand, change the +configuration for content in the webspace. For example, the following +configuration prevents access to any URL-path that begins in /private. +In particular, it will apply to requests for +http://yoursite.example.com/private, +http://yoursite.example.com/private123, and +http://yoursite.example.com/private/dir/file.html as well +as any other requests starting with the /private string.

+ +

+<Location /private>
+Order Allow,Deny
+Deny from all
+</Location> +

+ +

The <Location> +directive need not have anything to do with the filesystem. +For example, the following example shows how to map a particular +URL to an internal Apache handler provided by mod_status. +No file called server-status needs to exist in the +filesystem.

+ +

+<Location /server-status>
+SetHandler server-status
+</Location> +

+ + +

Wildcards and Regular Expressions

+ +

The <Directory>, +<Files>, and +<Location> +directives can each use shell-style wildcard characters as in +fnmatch from the C standard library. The character "*" +matches any sequence of characters, "?" matches any single character, +and "[seq]" matches any character in seq. The "/" +character will not be matched by any wildcard; it must be specified +explicitly.

+ +

If even more flexible matching is required, each +container has a regular expression (regex) counterpart <DirectoryMatch>, <FilesMatch>, and <LocationMatch> that allow +perl-compatible +regular expressions +to be used in choosing the matches. But see the section below on +configuration merging to find out how using regex sections will change +how directives are applied.

+ +

A non-regex wildcard section that changes the configuration of +all user directories could look as follows:

+ +

+<Directory /home/*/public_html>
+Options Indexes
+</Directory> +

+ +

Using regex sections, we can deny access to many types of image files +at once:

+

+<FilesMatch \.(?i:gif|jpe?g|png)$>
+Order allow,deny
+Deny from all
+</FilesMatch> +

+ + + +

What to use When

+ +

Choosing between filesystem containers and webspace containers is +actually quite easy. When applying directives to objects that reside +in the filesystem always use <Directory> or <Files>. When applying directives to objects +that do not reside in the filesystem (such as a webpage generated from +a database), use <Location>.

+ +

It is important to never use <Location> when trying to restrict +access to objects in the filesystem. This is because many +different webspace locations (URLs) could map to the same filesystem +location, allowing your restrictions to be circumvented. +For example, consider the following configuration:

+ +

+<Location /dir/>
+Order allow,deny
+Deny from all
+</Location> +

+ +

This works fine if the request is for +http://yoursite.example.com/dir/. But what if you are on +a case-insensitive filesystem? Then your restriction could be easily +circumvented by requesting +http://yoursite.example.com/DIR/. The <Directory> directive, in +contrast, will apply to any content served from that location, +regardless of how it is called. (An exception is filesystem links. +The same directory can be placed in more than one part of the +filesystem using symbolic links. The <Directory> directive will follow the symbolic +link without resetting the pathname. Therefore, for the highest level +of security, symbolic links should be disabled with the appropriate +Options directive.)

+ +

If you are, perhaps, thinking that none of this applies to you +because you use a case-sensitive filesystem, remember that there are +many other ways to map multiple webspace locations to the same +filesystem location. Therefore you should always use the filesystem +containers when you can. There is, however, one exception to this +rule. Putting configuration restrictions in a <Location +/> section is perfectly safe because this section will apply +to all requests regardless of the specific URL.

+ + +
top
+
+

Virtual Hosts

+ +

The <VirtualHost> +container encloses directives that apply to specific hosts. +This is useful when serving multiple hosts from the same machine +with a different configuration for each. For more information, +see the Virtual Host Documentation.

+
top
+
+

Proxy

+ +

The <Proxy> +and <ProxyMatch> +containers apply enclosed configuration directives only +to sites accessed through mod_proxy's proxy server +that match the specified URL. For example, the following configuration +will prevent the proxy server from being used to access the +cnn.com website.

+ +

+<Proxy http://cnn.com/*>
+Order allow,deny
+Deny from all
+</Proxy> +

+
top
+
+

What Directives are Allowed?

+ +

To find out what directives are allowed in what types of +configuration sections, check the Context of the directive. +Everything that is allowed in +<Directory> +sections is also syntactically allowed in +<DirectoryMatch>, +<Files>, +<FilesMatch>, +<Location>, +<LocationMatch>, +<Proxy>, +and <ProxyMatch> +sections. There are some exceptions, however:

+ + +
top
+
+

How the sections are merged

+ +

The configuration sections are applied in a very particular order. +Since this can have important effects on how configuration directives +are interpreted, it is important to understand how this works.

+ +

The order of merging is:

+ +
    +
  1. <Directory> (except regular expressions) + and .htaccess done simultaneously (with + .htaccess, if allowed, overriding + <Directory>)
    2. + +
  2. <DirectoryMatch> + (and <Directory ~>)
    3. + +
  3. <Files> and <FilesMatch> done + simultaneously
    4. + +
  4. <Location> + and <LocationMatch> done simultaneously
    5. +
+ +

Apart from <Directory>, each group is processed in + the order that they appear in the configuration files. <Directory> (group 1 above) + is processed in the order shortest directory component to longest. + So for example, <Directory /var/web/dir> will + be processed before <Directory + /var/web/dir/subdir>. If multiple <Directory> sections apply + to the same directory they are processed in the configuration file + order. Configurations included via the Include directive will be treated as if + they were inside the including file at the location of the + Include directive.

+ +

Sections inside <VirtualHost> sections + are applied after the corresponding sections outside + the virtual host definition. This allows virtual hosts to + override the main server configuration.

+ +

When the request is served by mod_proxy, the + <Proxy> + container takes the place of the <Directory> container in the processing + order.

+ +

Later sections override earlier ones.

+ +

Technical Note

+ There is actually a + <Location>/<LocationMatch> + sequence performed just before the name translation phase + (where Aliases and DocumentRoots + are used to map URLs to filenames). The results of this + sequence are completely thrown away after the translation has + completed. +
+ +

Some Examples

+ +

Below is an artificial example to show the order of +merging. Assuming they all apply to the request, the directives in +this example will be applied in the order A > B > C > D > +E.

+ +

+<Location />
+E
+</Location>
+
+<Files f.html>
+D
+</Files>
+
+<VirtualHost *>
+<Directory /a/b>
+B
+</Directory>
+</VirtualHost>
+
+<DirectoryMatch "^.*b$">
+C
+</DirectoryMatch>
+
+<Directory /a/b>
+A
+</Directory>
+
+

+ +

For a more concrete example, consider the following. Regardless of +any access restrictions placed in <Directory> sections, the <Location> section will be +evaluated last and will allow unrestricted access to the server. In +other words, order of merging is important, so be careful!

+ +

+<Location />
+Order deny,allow
+Allow from all
+</Location>
+
+# Woops! This <Directory> section will have no effect
+<Directory />
+Order allow,deny
+Allow from all
+Deny from badguy.example.com
+</Directory> +

+ + + +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/sections.html.ja.euc-jp b/docs/manual/sections.html.ja.euc-jp new file mode 100644 index 00000000..73ad7303 --- /dev/null +++ b/docs/manual/sections.html.ja.euc-jp @@ -0,0 +1,468 @@ + + + +¥»¥¯¥·¥ç¥ó¤ÎÀßÄê - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥»¥¯¥·¥ç¥ó¤ÎÀßÄê

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+

ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï +¥µ¡¼¥ÐÁ´ÂΤËŬÍѤµ¤ì¤¿¤ê¡¢ÆÃÄê¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ä¥Õ¥¡¥¤¥ë¡¢¥Û¥¹¥È¡¢URL ¤Ë¤Î¤ß +ŬÍѤµ¤ì¤ë¤è¤¦¤ËÀ©¸Â¤·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤Îʸ½ñ¤ÏÀßÄêÍѤΥ»¥¯¥·¥ç¥ó¤Î +¥³¥ó¥Æ¥Ê¤ä .htaccess ¥Õ¥¡¥¤¥ë¤ò»È¤Ã¤Æ¾¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î +¥¹¥³¡¼¥×¤òÊѹ¹¤¹¤ëÊýË¡¤òÀâÌÀ¤·¤Þ¤¹¡£

+
+ +
top
+
+

ÀßÄêÍÑ¥»¥¯¥·¥ç¥ó¥³¥ó¥Æ¥Ê¤Î¼ïÎà

+ +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

¥³¥ó¥Æ¥Ê¤Ë¤ÏÆó¤Ä¤Î´ðËܤȤʤë¼ïÎब¤¢¤ê¤Þ¤¹¡£¤Û¤È¤ó¤É¤Î¥³¥ó¥Æ¥Ê¤Ï +³Æ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æɾ²Á¤µ¤ì¤Þ¤¹¡£¤½¤Î¾ì¹ç¡¢¥³¥ó¥Æ¥ÊÃæ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï +¥³¥ó¥Æ¥Ê¤Ë¥Þ¥Ã¥Á¤¹¤ë¥ê¥¯¥¨¥¹¥È¤Ë¤Î¤ßŬÍѤµ¤ì¤Þ¤¹¡£ +°ìÊý¡¢<IfDefine> ¥³¥ó¥Æ¥Ê¤È <IfModule> ¥³¥ó¥Æ¥Ê¤Ï +¥µ¡¼¥Ð¤Îµ¯Æ°»þ¤ÈºÆµ¯Æ°»þ¤Ë¤Î¤ßɾ²Á¤µ¤ì¤Þ¤¹¡£µ¯Æ°»þ¤Ë¾ò·ï¤¬¿¿¤Ç¤¢¤ì¤Ð¡¢ +¥³¥ó¥Æ¥ÊÃæ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤ËŬÍѤµ¤ì¤Þ¤¹¡£¾ò·ï¤¬ +µ¶¤Ç¤¢¤ì¤Ð¡¢¥³¥ó¥Æ¥ÊÃæ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï̵»ë¤µ¤ì¤Þ¤¹¡£

+ +

<IfDefine> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï +httpd ¥³¥Þ¥ó¥É¥é¥¤¥ó¤ÇŬÀڤʥѥé¥á¡¼¥¿¤¬ÄêµÁ¤µ¤ì¤¿¤È¤­¤Ë¤Î¤ß +ŬÍѤµ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤¤¤Þ¤¹¡£Î㤨¤Ð¼¡¤ÎÀßÄê¤Ç¤Ï¡¢¥µ¡¼¥Ð¤¬ +httpd -DClosedForNow ¤ò»È¤Ã¤Æµ¯Æ°¤µ¤ì¤¿¤È¤­¤À¤±¤¹¤Ù¤Æ¤Î +¥ê¥¯¥¨¥¹¥È¤òÊ̤Υµ¥¤¥È¤Ë¥ê¥À¥¤¥ì¥¯¥È¤·¤Þ¤¹:

+ +

+<IfDefine ClosedForNow>
+Redirect / http://otherserver.example.com/
+</IfDefine> +

+ +

<IfModule> ¤Ï +Èó¾ï¤Ë»÷¤Æ¤¤¤Þ¤¹¤¬¡¢Âå¤ï¤ê¤Ë¥µ¡¼¥Ð¾å¤Ç¥â¥¸¥å¡¼¥ë¤¬»ÈÍѲÄǽ¤Ê¾ì¹ç¤Ë¤Î¤ß +ŬÍѲÄǽ¤Ê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤¤¤Þ¤¹¡£¥â¥¸¥å¡¼¥ë¤Ï¥µ¡¼¥Ð¤Ë +ÀÅŪ¤ËÁȤ߹þ¤Þ¤ì¤Æ¤¤¤ë¤«¡¢Æ°Åª¤ËÁȤ߹þ¤à¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Æ¡¢ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Ç +LoadModule ¤Î¹Ô¤¬¤è¤êÁ°¤Î +Éôʬ¤Ë½ñ¤«¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÆÃÄê¤Î¥â¥¸¥å¡¼¥ë¤Î +¸ºß¤Ë´Ø¤ï¤é¤ºÀßÄê¥Õ¥¡¥¤¥ë¤¬Æ°ºî¤¹¤ëɬÍפ¬¤¢¤ë¾ì¹ç¤Ë¤Î¤ß»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£ +¾ï¤ËÆ°ºî¤·¤ÆÍߤ·¤¤¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò°Ï¤à¤¿¤á¤Ë»È¤¦¤Ù¤­¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ +¸ºß¤·¤Ê¤¤¥â¥¸¥å¡¼¥ë¤Ë´Ø¤¹¤ëÍ­ÍѤʥ¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ÎȯÀ¸¤òÍÞÀ©¤·¤Æ¤·¤Þ¤¤¤Þ¤¹¤Î¤Ç¡£ +

+ +

¼¡¤ÎÎã¤Ç¤Ï¡¢mod_mime_magic ¤¬¤¢¤ë¤È¤­¤Ë¤Î¤ß MimeMagicFiles ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ +ŬÍѤµ¤ì¤Þ¤¹¡£

+ +

+<IfModule mod_mime_magic.c>
+MimeMagicFile conf/magic
+</IfModule> +

+ +

<IfDefine> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È +<IfModule> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï +¥Æ¥¹¥È¤ÎÁ°¤Ë "!" ¤òÉÕ¤±¤ë¤³¤È¤ÇÈÝÄê¤Î¾ò·ï¤òŬÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +¤Þ¤¿¡¢¤³¤ì¤é¤Î¥»¥¯¥·¥ç¥ó¤Ï¤è¤êÊ£»¨¤ÊÀ©¸Â¤ò²Ý¤¹¤¿¤á¤ËÆþ¤ì»Ò¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +

+
top
+
+

¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤È¥¦¥§¥Ö¶õ´Ö

+ +

ºÇ¤â¤è¤¯»È¤ï¤ì¤ëÀßÄê¤Î¥»¥¯¥·¥ç¥ó¥³¥ó¥Æ¥Ê¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ä¥¦¥§¥Ö¶õ´Ö¤Î +ÆÃÄê¤Î¾ì½ê¤ÎÀßÄê¤òÊѹ¹¤¹¤ë¤â¤Î¤Ç¤¹¡£¤Þ¤º¡¢¤³¤ÎÆó¤Ä¤Î°ã¤¤¤òÍý²ò¤¹¤ë¤³¤È¤¬ +ÂçÀڤǤ¹¡£¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤«¤é¸«¤¿¥Ç¥£¥¹¥¯¤ÎÆâÍƤǤ¹¡£ +¤¿¤È¤¨¤Ð¡¢¥Ç¥Õ¥©¥ë¥È¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤Ï Apache ¤Ï Unix ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤Ï +/usr/local/apache2 ¤Ë¡¢Windows ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤Ï +"c:/Program Files/Apache Group/Apache2" ¤Ë¸ºß¤·¤Þ¤¹¡£ +(Apache ¤Ç¤Ï Windows ¤Ç¤â¥Ñ¥¹¥»¥Ñ¥ì¡¼¥¿¤È¤·¤Æ¥¹¥é¥Ã¥·¥å¤ò»È¤¦¤³¤È¤Ë +µ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£) ÂоÈŪ¤Ë¡¢¥¦¥§¥Ö¶õ´Ö¤Ï¤¢¤Ê¤¿¤Î¥µ¥¤¥È¤ò +¥¦¥§¥Ö¥µ¡¼¥Ð¤«¤éÇÛ¿®¤µ¤ì¤ë¤â¤Î¤È¤·¤Æ¸«¤¿¤â¤Î¤Ç¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ë¸«¤¨¤ë¤â¤Î¤Ç¤¹¡£ +¥Ç¥Õ¥©¥ë¥È¤Î Unix ¾å¤Î Apache ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤Ï¥¦¥§¥Ö¶õ´Ö¤Î +/dir/ ¤È¤¤¤¦¥Ñ¥¹¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î +/usr/local/apache2/htdocs/dir/ ¤È¤¤¤¦¥Ñ¥¹¤ËÂбþ¤·¤Þ¤¹¡£ +¥¦¥§¥Ö¥Ú¡¼¥¸¤Ï¥Ç¡¼¥¿¥Ù¡¼¥¹¤ä¾¤Î¾ì½ê¤«¤éưŪ¤ËÀ¸À®¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¤Î¤Ç¡¢ +¥¦¥§¥Ö¶õ´Ö¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËľÀܥޥåפ¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£

+ +

¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥³¥ó¥Æ¥Ê

+ +

<Directory> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È +<Files> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢¤½¤ì¤È +¤½¤ì¤é¤ÎÀµµ¬É½¸½ÈǤϥǥ£¥ì¥¯¥Æ¥£¥Ö¤ò¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°ìÉôʬ¤ËÂФ·¤ÆŬÍѤ·¤Þ¤¹¡£ +<Directory> ¥»¥¯¥·¥ç¥ó¤Î +Ãæ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï»ØÄꤵ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤È¤½¤Î¤¹¤Ù¤Æ¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤Ë +ŬÍѤµ¤ì¤Þ¤¹¡£.htaccess ¥Õ¥¡¥¤¥ë¤ò +»È¤¦¤³¤È¤Ç¤âƱ¤¸¸ú²Ì¤òÆÀ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¡¢¼¡¤ÎÀßÄê¤Ç¤Ï +/var/web/dir1 ¤È¤¹¤Ù¤Æ¤Î¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ËÂФ·¤Æ +¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£

+ +

+<Directory /var/web/dir1>
+Options +Indexes
+</Directory> +

+ +

<Files> ¥»¥¯¥·¥ç¥ó¤Î +Ãæ¤Ë¤¢¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤É¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë¤«¤Ë´Ø¤ï¤é¤º¡¢»ØÄꤵ¤ì¤¿Ì¾Á°¤Î +¤¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ËŬÍѤµ¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤éÎ㤨¤Ð°Ê²¼¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ +ÀßÄê¥Õ¥¡¥¤¥ë¤Î¼ç¥»¥¯¥·¥ç¥ó¤Ë½ñ¤«¤ì¤¿¤È¤­¤Ë¤Ï¡¢¤¹¤Ù¤Æ¤Î¾ì½ê¤Î +private.html ¤È¤¤¤¦Ì¾Á°¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î¥¢¥¯¥»¥¹¤òµñÈݤ·¤Þ¤¹¡£

+ +

+<Files private.html>
+Order allow,deny
+Deny from all
+</Files> +

+ +

¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÆÃÄê¤Î¾ì½ê¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¤ò»ØÄꤹ¤ë¤¿¤á¤Ë¡¢ +<Files> ¥»¥¯¥·¥ç¥ó¤È +<Directory> ¥»¥¯¥·¥ç¥ó¤ò +ÁȤ߹ç¤ï¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£Î㤨¤Ð¡¢¼¡¤ÎÀßÄê¤Ç¤Ï +/var/web/dir1/private.html, +/var/web/dir1/subdir2/private.html, +/var/web/dir1/subdir3/private.html ¤Ê¤É¡¢ +/var/web/dir1/ ¥Ç¥£¥ì¥¯¥È¥ê¤Î²¼¤Ë¤¢¤ë¤¹¤Ù¤Æ¤Î +private.html ¤Ø¤Î¥¢¥¯¥»¥¹¤òµñÈݤ·¤Þ¤¹¡£

+ +

+<Directory /var/web/dir1>
+<Files private.html>
+Order allow,deny
+Deny from all
+</Files>
+</Directory> +

+ + +

¥¦¥§¥Ö¶õ´Ö¥³¥ó¥Æ¥Ê

+ +

°ìÊý¡¢<Location> +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¤½¤ÎÀµµ¬É½¸½ÈǤϥ¦¥§¥Ö¶õ´Ö¾å¤ÎÆâÍƤËÂФ·¤ÆÀßÄê¤òÊѹ¹¤·¤Þ¤¹¡£ +¤¿¤È¤¨¤Ð¡¢¼¡¤ÎÀßÄê¤Ç¤Ï /private ¤Ç»Ï¤Þ¤ë URL ¥Ñ¥¹¤Ø¤Î¥¢¥¯¥»¥¹¤òÀ©¸Â¤·¤Þ¤¹¡£ +¶ñÂÎŪ¤Ë¤Ï¡¢ +http://yoursite.example.com/private, +http://yoursite.example.com/private123, +http://yoursite.example.com/private/dir/file.html +¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ä¡¢ +¾¤ÎƱÍÍ¤Ë /private ʸ»úÎó¤Ç»Ï¤Þ¤ë¥ê¥¯¥¨¥¹¥È¤Ë +ŬÍѤµ¤ì¤Þ¤¹¡£

+ +

+<Location /private>
+Order Allow,Deny
+Deny from all
+</Location> +

+ +

<Location> +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤È´Ø·¸¤¢¤ëɬÍפ¬Á´¤¯¤¢¤ê¤Þ¤»¤ó¡£ +¤¿¤È¤¨¤Ð¼¡¤ÎÎã¤Ç¤Ï¡¢¤É¤Î¤è¤¦¤Ë¤·¤ÆÆÃÄê¤Î URL ¤ò +mod_status¤ÇÄ󶡤µ¤ì¤Æ¤¤¤ë Apache +ÆâÉô¥Ï¥ó¥É¥é¤Ë¥Þ¥Ã¥×¤¹¤ë¤«¤ò¼¨¤·¤Æ¤¤¤Þ¤¹¡£¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë +server-status ¤È¤¤¤¦¥Õ¥¡¥¤¥ë¤¬Â¸ºß¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£

+ +

+<Location /server-status>
+SetHandler server-status
+</Location> +

+ + +

¥ï¥¤¥ë¥É¥«¡¼¥É¤ÈÀµµ¬É½¸½

+ +

<Directory>, +<Files>, +<Location> +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¤Ï¡¢ C ɸ½à¥é¥¤¥Ö¥é¥ê¤Î fnmatch ¤Î¤è¤¦¤Ë +shell ¥¹¥¿¥¤¥ë¤Î¥ï¥¤¥ë¥É¥«¡¼¥É¥­¥ã¥é¥¯¥¿¤¬»ÈÍѤǤ­¤Þ¤¹¡£ +"*" ʸ»ú¤ÏǤ°Õ¤Îʸ»úÎó¤Ë¥Þ¥Ã¥Á¤·¡¢"?" ʸ»ú¤ÏǤ°Õ¤Î 1 ʸ»ú¤Ë¥Þ¥Ã¥Á¤·¡¢ +"[seq]" ¤Ï seq ¤ÎǤ°Õ¤Îʸ»ú¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¡£ +"/" ʸ»ú¤Ï¤É¤Î¥ï¥¤¥ë¥É¥«¡¼¥É¤Ç¤â¥Þ¥Ã¥Á¤µ¤ì¤Þ¤»¤ó¡£ +ÌÀ¼¨Åª¤Ë»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+ +

¤³¤ì¤è¤ê½ÀÆð¤Ê¥Þ¥Ã¥Á¥ó¥°¤¬É¬Íפʾì¹ç¤Ï¡¢¤³¤ì¤é¤Î¥³¥ó¥Æ¥Ê¤ËÀµµ¬É½¸½ +(regex) ÈǤǤ¢¤ë +<DirectoryMatch>, +<FilesMatch>, +<LocationMatch> +¤¬¤¢¤ê¡¢¥Þ¥Ã¥Á¤òÁªÂò¤¹¤ë¤Î¤Ë perl ¸ß´¹Àµµ¬É½¸½¤ò»ÈÍѤǤ­¤Þ¤¹¡£¤·¤«¤·¡¢¼¡¤ÎÀßÄê¤Î¥Þ¡¼¥¸¤ËÌܤòÄ̤·¤Æ¡¢ +regex ¥»¥¯¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎŬÍѤ¬¤É¤Î¤è¤¦¤Ë +ÊѲ½¤¹¤ë¤«ÇÄ°®¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£

+ +

Á´¥æ¡¼¥¶¥Ç¥£¥ì¥¯¥È¥ê¤ÎÀßÄê¤òÊѹ¹¤¹¤ë¡¢Èó regex +¥ï¥¤¥ë¥É¥«¡¼¥É¥»¥¯¥·¥ç¥ó¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

+<Directory /home/*/public_html>
+Options Indexes
+</Directory> +

+ +

regex ¥»¥¯¥·¥ç¥ó¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¡¢²èÁü¥Õ¥¡¥¤¥ë¤Î¿¤¯¤Î¥¿¥¤¥×¤ËÂФ¹¤ë +¥¢¥¯¥»¥¹¤ò°ìÅ٤˵ñÈݤǤ­¤Þ¤¹¡£

+

+<FilesMatch \.(?i:gif|jpe?g|png)$>
+Order allow,deny
+Deny from all
+</FilesMatch> +

+ + + +

¤¤¤Ä²¿¤ò»È¤¦¤«

+ +

¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥³¥ó¥Æ¥Ê¤È¥¦¥§¥Ö¶õ´Ö¥³¥ó¥Æ¥Ê¤ò»È¤¤Ê¬¤±¤ë¤Î¤Ï¡¢ +¼ÂºÝ¤Ë¤ÏÈó¾ï¤Ë´Êñ¤Ç¤¹¡£¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë°Í¸¤¹¤ë +¥ª¥Ö¥¸¥§¥¯¥È¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òŬ±þ¤¹¤ë¾ì¹ç¤Ï¡¢É¬¤º +<Directory> ¤« +<Files> +¤ò»ÈÍѤ·¤Þ¤¹¡£¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë°Í¸¤·¤Ê¤¤¥ª¥Ö¥¸¥§¥¯¥È +(¥Ç¡¼¥¿¥Ù¡¼¥¹¤«¤éÀ¸À®¤µ¤ì¤ë¥¦¥§¥Ö¥Ú¡¼¥¸¤Ê¤É) +¤Ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òŬÍѤ¹¤ëºÝ¤Ë¤Ï¡¢ +<Location> +¤ò»ÈÍѤ·¤Þ¤¹¡£

+ +

¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î¥ª¥Ö¥¸¥§¥¯¥È¤Ø¤Î¥¢¥¯¥»¥¹¤òÀ©¸Â¤¹¤ë¤¿¤á¤Ë¡¢ +<Location> +¤ò·è¤·¤Æ»ÈÍѤʤ¤¤è¤¦¤Ë¤·¤Þ¤·¤ç¤¦¡£ +Ʊ°ì¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à°ÌÃ֤˥ޥåפ·¤Æ¤¤¤ë¡¢¥¦¥§¥Ö¶õ´Ö°ÌÃÖ (URL) +¤¬Â¿¿ô¤¢¤Ã¤Æ¡¢ÀßÄꤷ¤¿À©¸Â¤ò±ª²ó¤µ¤ì¤Æ¤·¤Þ¤¦¤«¤â¤·¤ì¤Ê¤¤¤«¤é¤Ç¤¹¡£ +Î㤨¤Ð¼¡¤ÎÀßÄê¤ò¹Í¤¨¤Æ¤ß¤Þ¤·¤ç¤¦¡£

+ +

+<Location /dir/>
+Order allow,deny
+Deny from all
+</Location> +

+ +

http://yoursite.example.com/dir/ +¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ç¤Ï¾å¼ê¤¯Æ°ºî¤·¤Þ¤¹¡£¤·¤«¤·Âçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤·¤Ê¤¤ +¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò»È¤Ã¤Æ¤¤¤¿¤é¤É¤¦¤Ê¤ë¤Ç¤·¤ç¤¦? +http://yoursite.example.com/DIR/ +¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ç´Êñ¤Ë¥¢¥¯¥»¥¹À©¸Â¤ò±ª²ó¤µ¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹¡£¤³¤ì¤ËÂФ·¤Æ +<Directory> +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ë¤È¡¢¤É¤Î¤è¤¦¤Ë¸Æ¤Ó½Ð¤µ¤ì¤¿¤«¤Ë´Ø¤ï¤é¤º +¤½¤Î¾ì½ê¤«¤éÄ󶡤µ¤ì¤ëÆâÍƤËŬÍѤµ¤ì¤Þ¤¹¡£ +(Îã³°¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥ê¥ó¥¯¤Ç¤¹¡£¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò»È¤Ã¤Æ¡¢ +Ʊ°ì¤Î¥Ç¥£¥ì¥¯¥È¥ê¤òÊ£¿ô¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÀßÃ֤Ǥ­¤Þ¤¹¡£ +<Directory> +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Ñ¥¹Ì¾¤ò¥ê¥»¥Ã¥È¤¹¤ë¤³¤È¤Ê¤¯¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò +é¤ê¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢¹âÅ٤ʥ»¥­¥å¥ê¥Æ¥£¤¬Í׵ᤵ¤ì¤ë¾ì¹ç¤Ï¡¢ +ŬÀÚ¤Ë Options +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ·¤Æ¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò̵¸ú¤Ë¤¹¤ë¤Ù¤­¤Ç¤¹¡£)

+ +

Âçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤¹¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò»ÈÍѤ·¤Æ¤¤¤ë¤«¤é¾åµ­¤Î¤³¤È¤Ï +̵´Ø·¸¤À¤È»×¤ï¤ì¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢ +Ʊ°ì¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à°ÌÃÖ¤ËÊ£¿ô¤Î¥¦¥§¥Ö¶õ´Ö°ÌÃÖ¤ò¥Þ¥Ã¥×¤¹¤ëÊýË¡¤Ï¡¢ +¾¤Ë¤¤¤¯¤é¤Ç¤â¤¢¤ë¤È¤¤¤¦¤³¤È¤ò³Ð¤¨¤Æ¤¤¤Æ¤¯¤À¤µ¤¤¡£ +¤Ç¤¹¤«¤é¤Ç¤­¤ë¸Â¤ê¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥³¥ó¥Æ¥Ê¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£ +¤·¤«¤·¤Ê¤¬¤é°ì¤Ä¤À¤±Îã³°¤¬¤¢¤ê¤Þ¤¹¡£ +<Location /> ¥»¥¯¥·¥ç¥ó¤Ï¤É¤ó¤Ê URL +¤Ë¤â´Ø¤ï¤é¤ºÅ¬ÍѤµ¤ì¤ë¤Î¤Ç¡¢´°Á´¤Ë°ÂÁ´¤Ç¤¹¡£

+ + +
top
+
+

¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È

+ +

<VirtualHost> +¥³¥ó¥Æ¥Ê¤ÏÆÃÄê¤Î¥Û¥¹¥È¤ËŬÍѤ¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò³ÊǼ¤·¤Þ¤¹¡£ +°ìÂæ¤Î¥Þ¥·¥ó¤ÇÊ£¿ô¤Î¥Û¥¹¥È¤ò°Û¤Ê¤ëÀßÄê¤ÇÄ󶡤·¤¿¤¤¤È¤­¤ËÍ­ÍѤǤ¹¡£ +¾ÜºÙ¤Ë´Ø¤·¤Æ¤Ï¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¥É¥­¥å¥á¥ó¥È¤ò +¤´Í÷²¼¤µ¤¤¡£

+
top
+
+

¥×¥í¥¯¥·

+ +

<Proxy> +¤È <ProxyMatch> +¥³¥ó¥Æ¥Ê¤Ï¡¢ÆÃÄê¤Î URL ¤Ë¥Þ¥Ã¥Á¤¹¤ë mod_proxy +¥×¥í¥¯¥·¥µ¡¼¥Ð¤ò·Ðͳ¤·¤Æ¥¢¥¯¥»¥¹¤·¤¿¥µ¥¤¥È¤ËÂФ·¤Æ¤Î¤ßŬÍѤµ¤ì¤ë +ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò³ÊǼ¤·¤Þ¤¹¡£Î㤨¤Ð¼¡¤ÎÀßÄê¤Ï¡¢cnn.com +¥¦¥§¥Ö¥µ¥¤¥È¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤ËÍѤ¤¤é¤ì¤ë¥×¥í¥¯¥·¥µ¡¼¥Ð¤ò +À©¸Â¤·¤Þ¤¹¡£

+ +

+<Proxy http://cnn.com/*>
+Order allow,deny
+Deny from all
+</Proxy> +

+
top
+
+

¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬»È¤¨¤ë¤Î?

+ +

¤É¤Î¥¿¥¤¥×¤ÎÀßÄꥻ¥¯¥·¥ç¥ó¤Ç¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬»ÈÍѤǤ­¤ë¤«¤Ï¡¢ +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î Context +¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£ +<Directory> +¤Ç»ÈÍѲÄǽ¤Ê¤â¤Î¤ÏÁ´¤Æ¡¢Æ±ÍÍ¤Ë +<DirectoryMatch>, +<Files>, +<FilesMatch>, +<Location>, +<LocationMatch>, +<Proxy>, +<ProxyMatch> +¥»¥¯¥·¥ç¥ó¤Ç»ÈÍѲÄǽ¤Ç¤¹¡£¤·¤«¤·¤Ê¤¬¤é´ö¤Ä¤«Îã³°¤â¸ºß¤·¤Þ¤¹¡£

+ +
    +
  • AllowOverride ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï +<Directory> +¥»¥¯¥·¥ç¥ó¤Ç¤Î¤ß»ÈÍѲÄǽ¤Ç¤¹¡£
    • + +
  • FollowSymLinks ¤È SymLinksIfOwnerMatch ¤Î +Options ¤Ï¡¢ +<Directory> +¥»¥¯¥·¥ç¥ó¤« .htaccess ¥Õ¥¡¥¤¥ë¤Ç¤Î¤ß»ÈÍѲÄǽ¤Ç¤¹¡£
    • + +
  • Options ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ +<Files> +¤È <FilesMatch> +¥»¥¯¥·¥ç¥ó¤Ç¤Ï»ÈÍѤǤ­¤Þ¤»¤ó¡£
    • +
+
top
+
+

¥»¥¯¥·¥ç¥ó¤Î¥Þ¡¼¥¸ÊýË¡

+ +

¥Þ¡¼¥¸¤Î½çÈ֤ϰʲ¼¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹:

+ +
    +
  1. <Directory> (Àµµ¬É½¸½Ìµ¤·) ¤È + .htaccess ¤òƱ»þ¤Ë (.htaccess ¤¬µö²Ä¤µ¤ì¤Æ¤¤¤ì¤Ð¡¢¤½¤ì¤¬ + <Directory> ¤ò¾å½ñ¤­¤·¤Þ¤¹) +
    2. + +
  2. <DirectoryMatch> + (¤È <Directory ~>
    3. + +
  3. <Files> ¤È + <FilesMatch> ¤òƱ»þ¤Ë
    4. + +
  4. <Location> ¤È + <LocationMatch> ¤òƱ»þ¤Ë
    5. +
+ +

<Directory> + °Ê³°¤Ï¡¢¤½¤ì¤¾¤ì¤Î¥°¥ë¡¼¥×¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤Ë¸½¤ì¤¿½çÈ֤˽èÍý¤µ¤ì¤Þ¤¹¡£ + <Directory> (¾å¤Î¥°¥ë¡¼¥× 1) + ¤Ï¥Ç¥£¥ì¥¯¥È¥ê¤¬Ã»¤¤¤â¤Î¤«¤éŤ¤¤â¤Î¤Ø¤È½èÍý¤µ¤ì¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢ + Î㤨¤Ð <Directory /var/web/dir1> ¤Ï + <Directory /var/web/dir/subdir> ¤ÎÁ°¤Ë½èÍý¤µ¤ì¤Þ¤¹¡£Ê£¿ô¤Î + <Directory> ¥»¥¯¥·¥ç¥ó¤¬ + Ʊ¤¸¥Ç¥£¥ì¥¯¥È¥ê¤Ë + ŬÍѤµ¤ì¤ë¾ì¹ç¤Ï¡¢ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î½çÈ֤˽¾¤Ã¤Æ½èÍý¤µ¤ì¤Þ¤¹¡£ + Include + ¤Ë¤è¤Ã¤ÆÁÞÆþ¤µ¤ì¤¿ÀßÄê¤Ï ÁÞÆþ¤·¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¤Î + Include + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ÌÃ֤ˤ¢¤Ã¤¿¤«¤Î¤è¤¦¤Ë°·¤ï¤ì¤Þ¤¹¡£

+ +

<VirtualHost> ¥»¥¯¥·¥ç¥óÃæ¤Î¥»¥¯¥·¥ç¥ó¤Ï + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÄêµÁ¤Î³°Â¦¤ÎÂбþ¤¹¤ë¥»¥¯¥·¥ç¥ó¤Î + ¸å¤ËŬÍѤµ¤ì¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬ + ¥á¥¤¥ó¤Î¥µ¡¼¥ÐÀßÄê¤ò¾å½ñ¤­¤Ç¤­¤ë¤è¤¦¤Ê¤ê¤Þ¤¹¡£

+ +

mod_proxy ¤Ç¥ê¥¯¥¨¥¹¥È¤¬½èÍý¤µ¤ì¤ë¾ì¹ç¤Ï¡¢ + ½èÍý½çÈ֤Τ¦¤Á¡¢<Directory> ¥³¥ó¥Æ¥Ê¤ÎÉôʬ¤¬ + <Proxy> + ¥³¥ó¥Æ¥Ê¤Ë¼è¤Ã¤ÆÂå¤ï¤é¤ì¤Þ¤¹¡£

+ +

¸å¤Î¥»¥¯¥·¥ç¥ó¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬Á°¤Î¥»¥¯¥·¥ç¥ó¤Î¤â¤Î¤ò¾å½ñ¤­¤·¤Þ¤¹¡£

+ + +

µ»½Ñ¥á¥â

+ ¼ÂºÝ¤Ë¤Ï¡¢Ì¾Á°¤òÊÑ´¹¤¹¤ëÃʳ¬ (URL + ¤ò¥Õ¥¡¥¤¥ë̾¤Ë¥Þ¥Ã¥×¤¹¤ë¤¿¤á¤Ë Alias ¤ä + DocumentRoot ¤¬»ÈÍѤµ¤ì¤ë¤È¤³¤í) ¤ÎľÁ°¤Ë + <Location>/<LocationMatch> + ¤¬¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£ + ¤³¤ì¤é¤òŬÍѤ·¤¿·ë²Ì¤ÏÊÑ´¹¤¬½ª¤ï¤Ã¤¿¸å¤Ë´°Á´¤Ë¼Î¤Æ¤é¤ì¤Þ¤¹¡£ +
+

Îã

+ +

¼¡¤Ï¥Þ¡¼¥¸¤Î½çÈÖ¤ò¼¨¤¹¤¿¤á¤Î×ó°ÕŪ¤ÊÎã¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ +¥ê¥¯¥¨¥¹¥ÈÁ´¤Æ¤ËŬÍѤµ¤ì¤ë¤È¤·¤Æ¡¢ËÜÎã¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï +A > B > C > D > E ¤Î½çÈÖ¤ËŬÍѤµ¤ì¤Þ¤¹¡£

+ +

+<Location />
+E
+</Location>
+
+<Files f.html>
+D
+</Files>
+
+<VirtualHost *>
+<Directory /a/b>
+B
+</Directory>
+</VirtualHost>
+
+<DirectoryMatch "^.*b$">
+C
+</DirectoryMatch>
+
+<Directory /a/b>
+A
+</Directory>
+
+

+ +

¤â¤Ã¤È¶ñÂÎŪ¤Ê¡¢¼¡¤ÎÎã¤ò¹Í¤¨¤Æ¤ß¤Þ¤·¤ç¤¦¡£ +<Directory> +¥»¥¯¥·¥ç¥ó¤ËÀßÃÖ¤µ¤ì¤¿¥¢¥¯¥»¥¹À©¸Â¤Ë´Ø¤ï¤é¤º¡¢ +<Location> +¥»¥¯¥·¥ç¥ó¤¬ºÇ¸å¤Ëɾ²Á¤µ¤ì¤Æ¡¢¥µ¡¼¥Ð¤Ø¤Î¥¢¥¯¥»¥¹¤ÏÀ©¸Â¤µ¤ì¤Þ¤»¤ó¡£ +¸À¤¤´¹¤¨¤ì¤Ð¡¢¥Þ¡¼¥¸¤Î½çÈ֤ϽÅÍפǡ¢Ãí°Õ¤·¤Æ»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤!

+ +

+<Location />
+Order deny,allow
+Allow from all
+</Location>
+
+# Woops! This <Directory> section will have no effect
+<Directory />
+Order allow,deny
+Allow from all
+Deny from badguy.example.com
+</Directory> +

+ + + +
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/sections.html.ko.euc-kr b/docs/manual/sections.html.ko.euc-kr new file mode 100644 index 00000000..b9b691d7 --- /dev/null +++ b/docs/manual/sections.html.ko.euc-kr @@ -0,0 +1,422 @@ + + + +¼½¼Ç ¼³Á¤ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¼½¼Ç ¼³Á¤

+
+

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

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

¼³Á¤ÆÄÀÏ¿¡ ÀÖ´Â +Áö½Ã¾î´Â ¼­¹ö Àüü¿¡ Àû¿ëµÇ°Å³ª, ƯÁ¤ µð·ºÅ丮, ÆÄÀÏ, È£½ºÆ®, +URL¿¡¸¸ Àû¿ëµÉ ¼ö ÀÖ´Ù. ÀÌ ¹®¼­´Â ´Ù¸¥ Áö½Ã¾îÀÇ Àû¿ë¹üÀ§¸¦ +Á¦ÇÑÇϱâÀ§ÇØ ¼³Á¤ ¼½¼ÇÀ̳ª .htaccess ÆÄÀÏÀ» +»ç¿ëÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

¼³Á¤ ¼½¼ÇÀÇ Á¾·ù

+ +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

¼½¼Ç¿¡´Â µÎ°¡Áö Á¾·ù°¡ ÀÖ´Ù. ´ëºÎºÐÀº ¸Å¿äû¸¶´Ù 󸮵ȴÙ. +ÇØ´çÇÏ´Â ¿äû¿¡¸¸ ¾È¿¡ Æ÷ÇÔÇÑ Áö½Ã¾î¸¦ Àû¿ëÇÑ´Ù. ¹Ý´ë·Î, <IfDefine>°ú <IfModule>Àº ¼­¹ö°¡ +½ÃÀÛÇÒ¶§¿Í ²¨Áú¶§¸¸ ó¸®ÇÑ´Ù. ½ÃÀÛÇÒ¶§ »óÅ°¡ ÂüÀÌ¸é ¾È¿¡ ÀÖ´Â +Áö½Ã¾î°¡ ¸ðµç ¿äû¿¡ Àû¿ëµÈ´Ù. ÂüÀÌ ¾Æ´Ï¸é ¾È¿¡ ÀÖ´Â Áö½Ã¾î´Â +¹«½ÃÇÑ´Ù.

+ +

<IfDefine> +Áö½Ã¾î´Â httpd ¸í·ÉÇà¿¡ ÀûÀýÇÑ ÆĶó¹ÌÅÍ°¡ ÀÖ´Â +°æ¿ì¿¡¸¸ ¾È¿¡ Æ÷ÇÔÇÑ Áö½Ã¾î¸¦ Àû¿ëÇÑ´Ù. ´ÙÀ½ ¼³Á¤À» ¿¹·Î µé¸é, +¼­¹ö¸¦ httpd -DClosedForNow·Î ½ÃÀÛÇÒ °æ¿ì¿¡¸¸ +¸ðµç ¿äûÀÌ ´Ù¸¥ »çÀÌÆ®·Î ¸®´ÙÀÌ·º¼ÇµÈ´Ù:

+ +

+<IfDefine ClosedForNow>
+Redirect / http://otherserver.example.com/
+</IfDefine> +

+ +

<IfModule> +Áö½Ã¾îµµ ƯÁ¤ ¸ðµâÀÌ ¼­¹ö¿¡ Æ÷ÇÔµÈ °æ¿ì¿¡¸¸ ¾È¿¡ µç Áö½Ã¾î¸¦ +Àû¿ëÇÑ´Ù´Â Á¡À» Á¦¿ÜÇÏ°í´Â ¸Å¿ì ºñ½ÁÇÏ´Ù. ¸ðµâÀ» ¼­¹ö¿¡ Á¤ÀûÀ¸·Î +ÄÄÆÄÀÏÇϰųª µ¿ÀûÀ¸·Î ÄÄÆÄÀÏÇÑÈÄ ¼³Á¤ÆÄÀÏ ¾Õ¿¡ LoadModule ÁÙÀÌ ÀÖ¾î¾ß ÇÑ´Ù. ÀÌ +Áö½Ã¾î´Â ƯÁ¤ ¸ðµâÀÇ ¼³Ä¡À¯¹«¿¡ µû¶ó ¼³Á¤ÆÄÀÏÀÌ ´Ù¸¦ ÇÊ¿ä°¡ +ÀÖÀ»¶§¸¸ »ç¿ëÇØ¾ß ÇÑ´Ù. ¸ðµâÀÌ ¾ø´Â °æ¿ì À¯¿ëÇÑ ¿À·ù¹®ÀÌ ³ª¿ÀÁö¾ÊÀ» +¼ö Àֱ⠶§¹®¿¡ ¾ðÁ¦³ª »ç¿ëÇÏ±æ ¿øÇÏ´Â Áö½Ã¾î¸¦ ¾È¿¡ µÎ¸é ¾ÈµÈ´Ù.

+ +

´ÙÀ½ ¿¹¿¡¼­ mod_mime_magicÀÌ ÀÖÀ»¶§¸¸ MimeMagicFiles Áö½Ã¾î¸¦ +ó¸®ÇÑ´Ù.

+ +

+<IfModule mod_mime_magic.c>
+MimeMagicFile conf/magic
+</IfModule> +

+ +

<IfDefine>°ú +<IfModule>ÀÇ +°Ë»ç ¾Õ¿¡ "!"À» ºÙ¿© Á¶°ÇÀ» ¿ªÀ¸·Î ÇÒ ¼ö ÀÖ´Ù. ¶Ç, ¿©·¯ ¼½¼ÇµéÀ» +°ãÃļ­ »ç¿ëÇÏ¿© ´õ º¹ÀâÇÑ È¿°ú¸¦ ¾òÀ» ¼ö ÀÖ´Ù.

+
top
+
+

ÆÄÀϽýºÅÛ°ú À¥°ø°£

+ +

°¡Àå ÀÚÁÖ »ç¿ëµÇ´Â ¼³Á¤ ¼½¼ÇÀº ÆÄÀϽýºÅÛ°ú À¥°ø°£(webspace)ÀÇ +ƯÁ¤ Àå¼Ò¿¡ ´ëÇÑ ¼³Á¤À» º¯°æÇÏ´Â °ÍµéÀÌ´Ù. ¸ÕÀú ÀÌ µÑÀÇ Â÷À̸¦ +ÀÌÇØÇÏ´Â °ÍÀÌ Áß¿äÇÏ´Ù. ÆÄÀϽýºÅÛÀº ¿î¿µÃ¼Á¦ ÀÔÀå¿¡¼­ µð½ºÅ©¸¦ +º¸´Â °üÁ¡ÀÌ´Ù. ¿¹¸¦ µé¾î, ±âº»°ªÀ¸·Î ¾ÆÆÄÄ¡¸¦ ¼³Ä¡¸¦ Çϸé À¯´Ð½º +ÆÄÀϽýºÅÛÀÇ °æ¿ì /usr/local/apache2, À©µµ¿ìÁî +ÆÄÀϽýºÅÛÀÇ °æ¿ì "c:/Program Files/Apache +Group/Apache2"¿¡ ¼³Ä¡µÈ´Ù. (¾ÆÆÄÄ¡´Â À©µµ¿ìÁî¿¡¼­ Á¶Â÷ +Ç×»ó, ¿ª½½·¡½¬°¡ ¾Æ´Ñ, ½½·¡½¬¸¦ »ç¿ëÇÔÀ» ÁÖÀÇÇ϶ó.) ¹Ý´ë·Î +À¥°ø°£Àº À¥¼­¹ö°¡ Á¦°øÇÏ°í Ŭ¶óÀ̾ðÆ®°¡ º¸°ÔµÉ »çÀÌÆ®ÀÇ °üÁ¡ÀÌ´Ù. +±×·¡¼­ À¯´Ð½º¿¡¼­ ±âº» ¾ÆÆÄÄ¡ ¼³Ä¡¸¦ ÇÑ °æ¿ì À¥°æ·ÎÀÇ °æ·Î +/dir/Àº ÆÄÀϽýºÅÛ °æ·Î +/usr/local/apache2/htdocs/dir/¿¡ ÇØ´çÇÑ´Ù. À¥°ø°£Àº +µ¥ÀÌŸº£À̽º µî¿¡¼­ µ¿ÀûÀ¸·Î »ý¼ºµÉ ¼ö Àֱ⶧¹®¿¡ ¹Ýµå½Ã +ÆÄÀϽýºÅÛ¿¡ Á÷Á¢ ´ëÀÀµÉ ÇÊ¿ä´Â ¾ø´Ù.

+ +

ÆÄÀϽýºÅÛ ¼½¼Ç

+ +

<Directory>¿Í +<Files> Áö½Ã¾î¿Í +Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ´Â Áö½Ã¾î´Â ÆÄÀϽýºÅÛÀÇ Æ¯Á¤ ºÎºÐ¿¡ Áö½Ã¾î¸¦ +Àû¿ëÇÑ´Ù. <Directory> Áö½Ã¾î¿¡ Æ÷ÇÔµÈ Áö½Ã¾îµéÀº +ÁöÁ¤ÇÑ ÆÄÀϽýºÅÛ µð·ºÅ丮¿Í ±× ÇÏÀ§ µð·ºÅ丮¿¡ Àû¿ëµÈ´Ù. .htaccess ÆÄÀÏÀ» »ç¿ëÇصµ °á°ú´Â +°°´Ù. ´ÙÀ½ ¼³Á¤À» ¿¹·Î µé¸é, µð·ºÅ丮 ¸ñ·Ï(index)ÀÌ +/var/web/dir1 ÀÌÇÏ µð·ºÅ丮¿¡¼­ µð·ºÅ丮 ¸ñ·Ï(index)ÀÌ +°¡´ÉÇÏ´Ù.

+ +

+<Directory /var/web/dir1>
+Options +Indexes
+</Directory> +

+ +

<Files> ¼½¼Ç¿¡ Æ÷ÇÔµÈ Áö½Ã¾îµéÀº ¾î¶² +µð·ºÅ丮¿¡ ÀÖ´ÂÁö °ü°è¾øÀÌ ÁöÁ¤ÇÑ À̸§À» °¡Áø ÆÄÀÏ¿¡ Àû¿ëµÈ´Ù. +¼³Á¤ÆÄÀÏÀÇ ÁÖ¼³Á¤ºÎºÐ¿¡ ÀÖ´Â ´ÙÀ½ ¼³Á¤À» ¿¹·Î µé¸é, Àå¼Ò¿Í +°ü°è¾øÀÌ private.htmlÀ̶õ À̸§À» ÇÑ ÆÄÀÏÀÇ Á¢±ÙÀ» +°ÅºÎÇÑ´Ù.

+ +

+<Files private.html>
+Order allow,deny
+Deny from all
+</Files> +

+ +

ÆÄÀϽýºÅÛÀÇ Æ¯Á¤ ºÎºÐ¿¡ ÀÖ´Â ÆÄÀÏÀ» ÁöĪÇϱâÀ§ÇØ <Files>¿Í <Directory> ¼½¼ÇÀ» °°ÀÌ +»ç¿ëÇÑ´Ù. ´ÙÀ½ ¼³Á¤À» ¿¹·Î µé¸é, +/var/web/dir1/private.html, +/var/web/dir1/subdir2/private.html, +/var/web/dir1/subdir3/private.html °°ÀÌ +/var/web/dir1/ µð·ºÅ丮 ¾Æ·¡¿¡ ÀÖ´Â À̸§ÀÌ +private.htmlÀÎ ÆÄÀÏÀÇ Á¢±ÙÀ» °ÅºÎÇÑ´Ù.

+ +

+<Directory /var/web/dir1>
+<Files private.html>
+Order allow,deny
+Deny from all
+</Files>
+</Directory> +

+ + +

À¥°ø°£ ¼½¼Ç

+ +

<Location> +Áö½Ã¾î¿Í ÀÌ¿¡ ÇØ´çÇÏ´Â Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ´Â Áö½Ã¾î´Â ¹Ý´ë·Î +ƯÁ¤ À¥°ø°£ÀÇ ¼³Á¤À» ¹Ù²Û´Ù. ´ÙÀ½ ¼³Á¤À» ¿¹·Î µé¸é, /privateÀ¸·Î +½ÃÀÛÇÏ´Â URL-°æ·ÎÀÇ Á¢±ÙÀÌ °ÅºÎµÈ´Ù. ¿©±â¿¡´Â +http://yoursite.example.com/private, +http://yoursite.example.com/private123, +http://yoursite.example.com/private/dir/file.html +°°ÀÌ /private ¹®ÀÚ¿­·Î ½ÃÀÛÇÏ´Â ¿äûÀÌ ÇØ´çµÈ´Ù.

+ +

+<Location /private>
+Order Allow,Deny
+Deny from all
+</Location> +

+ +

<Location> +Áö½Ã¾î´Â ÆÄÀϽýºÅÛ¿¡ ´ëÀÀÇÒ ÇÊ¿ä°¡ ¾ø´Ù. ´ÙÀ½ ¿¹´Â ¾î¶»°Ô ƯÁ¤ +URLÀ» mod_status°¡ Á¦°øÇÏ´Â ¾ÆÆÄÄ¡ ³»ºÎ Çڵ鷯·Î +´ëÀÀ½ÃÅ°´ÂÁö¸¦ º¸¿©ÁØ´Ù. ÆÄÀϽýºÅÛ¿¡ server-status¶ó´Â +ÆÄÀÏÀº ÇÊ¿ä¾ø´Ù.

+ +

+<Location /server-status>
+SetHandler server-status
+</Location> +

+ + +

¿ÍÀϵåÄ«µå¿Í Á¤±ÔÇ¥Çö½Ä

+ +

<Directory>, +<Files>, +<Location> +Áö½Ã¾î¿¡¼­ C Ç¥ÁØ ÆÄÀ̺귯¸®ÀÇ fnmatch¿Í °°Àº +½©¿¡¼­ »ç¿ëÇÏ´Â ¿ÍÀϵåÄ«µå ¹®ÀÚ¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù. +"*" ¹®ÀÚ´Â ¾î¶² ¹®ÀÚ¿­ÀÌ¶óµµ ³ªÅ¸³»°í, "?" ¹®ÀÚ´Â ¾î¶² ¹®ÀÚ ÇÑ°³¸¦ +³ªÅ¸³»¸ç, "[seq]"´Â seq Áß¿¡ ÇÑ ¹®ÀÚ¸¦ ³ªÅ¸³½´Ù. +¾î¶² ¿ÍÀϵåÄ«µåµµ "/" ¹®ÀÚ¸¦ ³ªÅ¸³»Áö´Â ¸øÇÑ´Ù. ±×·¡¼­ ÀÌ ¹®ÀÚ´Â +Á÷Á¢ »ç¿ëÇØ¾ß ÇÑ´Ù.

+ +

´õ À¯¿¬ÇÑ ¼³Á¤ÀÌ ÇÊ¿äÇϸé perlȣȯ Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏ´Â <DirectoryMatch>, <FilesMatch>, <LocationMatch>¸¦ »ç¿ëÇÒ +¼ö ÀÖ´Ù. ±×·¯³ª ¾Æ·¡ ¼³Á¤ÀÇ °áÇÕ¿¡ °üÇÑ Àý¿¡¼­ Á¤±ÔÇ¥Çö½Ä ¼½¼ÇÀ» +»ç¿ëÇϸé Áö½Ã¾î°¡ Àû¿ëµÇ´Â ¹æ¹ýÀÌ ¾î¶»°Ô º¯ÇÏ´ÂÁö »ìÆìºÁ¶ó.

+ +

¸ðµç »ç¿ëÀÚ µð·ºÅ丮 ¼³Á¤À» º¯°æÇÏ´Â ºñÁ¤±ÔÇ¥Çö½Ä ¿ÍÀϵåÄ«µå +¼½¼ÇÀº ´ÙÀ½°ú °°´Ù:

+ +

+<Directory /home/*/public_html>
+Options Indexes
+</Directory> +

+ +

Á¤±ÔÇ¥Çö½Ä ¼½¼ÇÀ» »ç¿ëÇÏ¿© Çѹø¿¡ ¿©·¯ Á¾·ùÀÇ ±×¸²ÆÄÀÏ¿¡ +´ëÇÑ Á¢±ÙÀ» °ÅºÎÇÒ ¼ö ÀÖ´Ù:

+

+<FilesMatch \.(?i:gif|jpe?g|png)$>
+Order allow,deny
+Deny from all
+</FilesMatch> +

+ + + +

¹«¾ùÀ» »ç¿ëÇϳª

+ +

ÆÄÀϽýºÅÛ ¼½¼Ç°ú À¥°ø°£ ¼½¼Ç Áß Çϳª¸¦ ¼±ÅÃÇÏ´Â °ÍÀº ½ÇÁ¦·Î +¸Å¿ì ½±´Ù. ÆÄÀϽýºÅÛ¿¡ ÀÖ´Â °´Ã¼¿¡ Áö½Ã¾î¸¦ Àû¿ëÇÒ¶§´Â Ç×»ó +<Directory>³ª +<Files>¸¦ +»ç¿ëÇÑ´Ù. (µ¥ÀÌŸº£À̽º¿¡¼­ »ý¼ºÇÑ À¥ÆäÀÌÁö¿Í °°ÀÌ) ÆÄÀϽýºÅÛ¿¡ +ÀÖÁö ¾Ê´Â °´Ã¼¿¡ Áö½Ã¾î¸¦ Àû¿ëÇÒ¶§´Â <Location>À» »ç¿ëÇÑ´Ù.

+ +

ÆÄÀϽýºÅÛ¿¡ ÀÖ´Â °´Ã¼ÀÇ Á¢±ÙÀ» Á¦ÇÑÇϱâÀ§ÇØ <Location>À» »ç¿ëÇϸé +Àý´ë ¾ÈµÈ´Ù. ¿©·¯ ´Ù¸¥ À¥°ø°£ Àå¼Ò(URL)°¡ °°Àº ÆÄÀϽýºÅÛ Àå¼Ò¿¡ +´ëÀÀµÉ ¼ö ÀÖÀ¸¹Ç·Î, °É¾îµÐ Á¦ÇÑÀ» ¿ìȸÇÒ ¼ö Àֱ⠶§¹®ÀÌ´Ù. ´ÙÀ½ +¼³Á¤ÀÇ ¿¹¸¦ »ìÆ캸ÀÚ:

+ +

+<Location /dir/>
+Order allow,deny
+Deny from all
+</Location> +

+ +

ÀÌ ¼³Á¤Àº http://yoursite.example.com/dir/À» +¿äûÇÑ´Ù¸é Àß ÀÛµ¿ÇÑ´Ù. ±×·¯³ª ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾Ê´Â ÆÄÀϽýºÅÛÀ» +»ç¿ëÇÑ´Ù¸é ¾î¶»°ÔµÇ³ª? +http://yoursite.example.com/DIR/À» ¿äûÇÏ¿© ½±°Ô +Á¦ÇÑÀ» ¿ìȸÇÒ ¼ö ÀÖ´Ù. ¹Ý´ë·Î <Directory> Áö½Ã¾î´Â ¾î¶»°Ô ¿äûÇÏ¿´´ÂÁö +°ü°è¾øÀÌ ±× Àå¼Ò¿¡¼­ ¼­ºñ½ºµÇ´Â ³»¿ë¿¡ Àû¿ëµÈ´Ù. (¿¹¿Ü´Â ÆÄÀϽýºÅÛ +¸µÅ©¸¦ »ç¿ëÇÏ´Â °æ¿ì´Ù. ½Éº¼¸µÅ©¸¦ »ç¿ëÇÏ¿© ÇÑ µð·ºÅ丮¸¦ +ÆÄÀϽýºÅÛÀÇ ¿©·¯ Àå¼Ò¿¡ µÑ ¼ö ÀÖ´Ù. <Directory> Áö½Ã¾î´Â ½Éº¼¸µÅ©¸¦ µû¶ó°£´Ù. +±×·¯¹Ç·Î ³ôÀº ¼öÁØÀÇ º¸¾ÈÀ» À§Çؼ­´Â ÀûÀýÇÑ Options Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ½Éº¼¸µÅ©¸¦ +¹«½ÃÇØ¾ß ÇÑ´Ù.)

+ +

¾Æ¸¶µµ ´ç½ÅÀº ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏ´Â ÆÄÀϽýºÅÛÀ» »ç¿ëÇϹǷΠ+ÀÌ·± ÀÏÀÌ ÀϾÁö ¾Ê´Â´Ù°í »ý°¢ÇÒÁöµµ ¸ð¸¥´Ù. ±×·¯³ª ´Ù¸¥ +¹æ¹ýÀ¸·Îµµ ¿©·¯ À¥°ø°£ À§Ä¡°¡ ÇÑ ÆÄÀϽýºÅÛ À§Ä¡¿¡ ´ëÀÀµÉ ¼ö +ÀÖÀ½À» ±â¾ïÇ϶ó. ±×·¡¼­ °¡´ÉÇϸé Ç×»ó ÆÄÀϽýºÅÛ ¼½¼ÇÀ» »ç¿ëÇØ¾ß +ÇÑ´Ù. ±×·¯³ª ÀÌ ±ÔÄ¢¿¡ ¿¹¿Ü°¡ Çϳª ÀÖ´Ù. ¼³Á¤ Á¦ÇÑÀ» +<Location /> ¼½¼Ç¿¡ µÎ¸é ÀÌ ¼½¼ÇÀÌ Æ¯Á¤ +URLÀÌ ¾Æ´Ñ ¸ðµç ¿äû¿¡ Àû¿ëµÇ¹Ç·Î ¿Ïº®ÇÏ°Ô ¾ÈÀüÇÏ´Ù.

+ + +
top
+
+

°¡»óÈ£½ºÆ®

+ +

<VirtualHost> +¼½¼ÇÀº ƯÁ¤ È£½ºÆ®¿¡ Àû¿ëµÇ´Â Áö½Ã¾îµéÀ» Æ÷ÇÔÇÑ´Ù. ÀÌ´Â ÇÑ +ÄÄÇ»ÅÍ¿¡¼­ °¢°¢ ´Ù¸¥ ¼³Á¤À» »ç¿ëÇÑ ¿©·¯ È£½ºÆ®¸¦ ¼­ºñ½ºÇÒ¶§ +À¯¿ëÇÏ´Ù. ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â °¡»óÈ£½ºÆ® ¹®¼­¸¦ +Âü°íÇ϶ó.

+
top
+
+

ÇÁ·Ï½Ã

+ +

<Proxy>¿Í +<ProxyMatch> +¼½¼ÇÀº ÁöÁ¤ÇÑ URL¿¡ ´ëÇØ mod_proxy ÇÁ·Ï½Ã ¼­¹ö¸¦ +°ÅÃÄ Á¢±ÙÇÏ´Â °æ¿ì¿¡¸¸ Àû¿ëµÈ´Ù. ´ÙÀ½ ¼³Á¤À» ¿¹·Î µé¸é, ÇÁ·Ï½Ã +¼­¹ö¸¦ ÅëÇØ cnn.com À¥»çÀÌÆ®¿¡ Á¢±ÙÇÒ ¼ö ¾ø´Ù.

+ +

+<Proxy http://cnn.com/*>
+Order allow,deny
+Deny from all
+</Proxy> +

+
top
+
+

¾È¿¡ ¾î¶² Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö +ÀÖ³ª?

+ +

¾î¶² ¼³Á¤ ¼½¼Ç¾È¿¡ »ç¿ëÇÒ ¼ö ÀÖ´Â Áö½Ã¾î¸¦ ¾Ë·Á¸é Áö½Ã¾îÀÇ +»ç¿ëÀå¼Ò¸¦ È®ÀÎÇ϶ó. +<Directory>¿¡¼­ +»ç¿ë°¡´ÉÇÑ Áö½Ã¾î´Â <DirectoryMatch>, <Files>, <FilesMatch>, <Location>, <LocationMatch>, <Proxy>, <ProxyMatch> ¼½¼Ç¿¡¼­µµ »ç¿ë°¡´ÉÇÏ´Ù. +±×·¯³ª, ¿¹¿Ü°¡ ÀÖ´Ù:

+ +
    +
  • AllowOverride Áö½Ã¾î´Â +<Directory> +¼½¼Ç¿¡¼­¸¸ »ç¿ëÇÒ ¼ö ÀÖ´Ù.
    • + +
  • FollowSymLinks, SymLinksIfOwnerMatch, +Options´Â <Directory> ¼½¼ÇÀ̳ª +.htaccess ÆÄÀÏ¿¡¼­¸¸ »ç¿ëÇÒ ¼ö ÀÖ´Ù.
    • + +
  • Options Áö½Ã¾î´Â +<Files>°ú +<FilesMatch> +¼½¼Ç¿¡¼­ »ç¿ëÇÒ ¼ö ¾ø´Ù.
    • +
+
top
+
+

¼½¼ÇµéÀÌ °áÇÕÇÏ´Â ¹æ¹ý

+ +

¼³Á¤ ¼½¼ÇÀº ¸Å¿ì Ưº°ÇÑ ¹æ¹ýÀ¸·Î Àû¿ëµÈ´Ù. ÀÌ ¼ø¼­°¡ ¼³Á¤ +Áö½Ã¾î¸¦ Çؼ®ÇÏ´Â ¹æ¹ý¿¡ Áß¿äÇÑ ¿µÇâÀ» Áֱ⶧¹®¿¡ ÀÌ ¹æ¹ýÀ» +ÀÌÇØÇÏ´Â °ÍÀÌ Áß¿äÇÏ´Ù.

+ +

°áÇÕÇÏ´Â ¼ø¼­´Â:

+ +
    +
  1. (Á¤±ÔÇ¥Çö½ÄÀ» »ç¿ëÇÏÁö¾Ê´Â) <Directory>¿Í .htaccess´Â + µ¿½Ã¿¡ ÀϾ´Ù (°æ¿ì¿¡ µû¶ó .htaccessÀÌ + <Directory>¸¦ + ¹«½ÃÇϵµ·Ï ¼³Á¤ÇÒ ¼ö ÀÖ´Ù)
    2. + +
  2. <DirectoryMatch> (±×¸®°í + <Directory ~>)
    3. + +
  3. <Files>¿Í <FilesMatch>´Â µ¿½Ã¿¡ ÀϾ´Ù
    4. + +
  4. <Location>°ú <LocationMatch>´Â µ¿½Ã¿¡ ÀϾ´Ù
    5. +
+ +

<Directory>¸¦ Á¦¿ÜÇÏ°í °¢ ¼½¼ÇµéÀ» + ¼³Á¤ÆÄÀÏ¿¡ ³ª¿Â ¼ø¼­´ë·Î 󸮵ȴÙ. (À§ÀÇ ¼ø¼­ 1) <Directory>´Â µð·ºÅ丮 + ³»¿ëÀÌ °¡Àå ªÀº °Í¿¡¼­ ±äÂÊÀ¸·Î 󸮵ȴÙ. ±×·¡¼­ ¿¹¸¦ µé¾î, + <Directory /var/web/dir>À» + <Directory /var/web/dir/subdir> ÀÌÀü¿¡ + ó¸®ÇÑ´Ù. °°Àº µð·ºÅ丮¸¦ ÁöĪÇÏ´Â ¿©·¯ <Directory> ¼½¼ÇÀÌ + ÀÖ´Ù¸é À̵éÀ» ¼³Á¤ÆÄÀÏ ¼ø¼­´ë·Î ó¸®ÇÑ´Ù. Include Áö½Ã¾î·Î Æ÷ÇÔÇÑ ¼³Á¤Àº + Include Áö½Ã¾î À§Ä¡¿¡ + Æ÷ÇÔÇÑ ÆÄÀÏ ³»¿ëÀÌ ÀÖ´Â °Íó·³ ó¸®ÇÑ´Ù.

+ +

<VirtualHost> ¼½¼Ç ¾È¿¡ Æ÷ÇÔµÈ ¼½¼ÇÀº + °¡»óÈ£½ºÆ® Á¤ÀÇ ¹Û¿¡ ÀÖ´Â ÇØ´ç ¼½¼Ç ÀÌÈÄ¿¡ Àû¿ëµÈ´Ù. + ±×·¡¼­ °¡»óÈ£½ºÆ® ¾È¿¡¼­ ÁÖ¼­¹öÀÇ ¼³Á¤»çÇ×À» ¼öÁ¤ÇÒ ¼ö ÀÖ´Ù.

+ +

mod_proxy°¡ ¿äû ¼­ºñ½ºÇÒ¶§, <Proxy> ¼½¼ÇÀÇ + 󸮼ø¼­´Â <Directory> ¼½¼Ç°ú °°´Ù.

+ +

´ÙÀ½¿¡ ³ª¿À´Â ¼½¼ÇÀº ÀÌÀü ¼½¼ÇÀÇ °á°ú¸¦ ¼öÁ¤ÇÑ´Ù.

+ +

±â¼úÀû ÁÖÀÇ

+ ½ÇÁ¦·Î + <Location>/<LocationMatch>´Â + (Aliases¿Í DocumentRoot¸¦ »ç¿ëÇÏ¿© + URLÀ» ÆÄÀϸíÀ¸·Î º¯È¯ÇÏ´Â) À̸§¹ø¿ª ´Ü°è ÀÌÀü¿¡ 󸮵ȴÙ. + º¯¿ªÀÌ ³¡³­ ÀÌÈÄ¿¡´Â ¿ÏÀüÈ÷ ¹«½ÃÇÑ´Ù. +
+ +

¿¹Á¦

+ +

´ÙÀ½Àº °ãÇÕÇÏ´Â ¼ø¼­¸¦ ¼³¸íÇÏ´Â ¿¹´Ù. ÀÌµé ¸ðµÎ ¿äû¿¡ +Àû¿ëµÈ´Ù°í °¡Á¤Çϸé Áö½Ã¾î´Â A > B > C > D > E +¼ø¼­·Î 󸮵ȴÙ.

+ +

+<Location />
+E
+</Location>
+
+<Files f.html>
+D
+</Files>
+
+<VirtualHost *>
+<Directory /a/b>
+B
+</Directory>
+</VirtualHost>
+
+<DirectoryMatch "^.*b$">
+C
+</DirectoryMatch>
+
+<Directory /a/b>
+A
+</Directory>
+
+

+ +

´õ Çö½ÇÀûÀÎ ¿¹´Â ´ÙÀ½°ú °°´Ù. <Location> ¼½¼ÇÀ» ³ªÁß¿¡ ó¸®ÇϹǷΠ+<Directory> +¼½¼Ç¿¡ ÀÖ´Â Á¢±ÙÁ¦ÇÑ°ú °ü°è¾øÀÌ ¼­¹ö¿¡ ¹«Á¦ÇÑ Á¢±ÙÀ» °¡´ÉÇÏ´Ù. +Áï, °áÇÕÇÏ´Â ¼ø¼­´Â Áß¿äÇϹǷΠÁÖÀÇÇ϶ó!

+ +

+<Location />
+Order deny,allow
+Allow from all
+</Location>
+
+# ¾Ç! ÀÌ <Directory> ¼½¼ÇÀº ¾Æ¹«·± È¿°ú°¡ ¾ø´Ù
+<Directory />
+Order allow,deny
+Allow from all
+Deny from badguy.example.com
+</Directory> +

+ + + +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/server-wide.html b/docs/manual/server-wide.html new file mode 100644 index 00000000..d43014c0 --- /dev/null +++ b/docs/manual/server-wide.html @@ -0,0 +1,11 @@ +URI: server-wide.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: server-wide.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: server-wide.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/server-wide.html.en b/docs/manual/server-wide.html.en new file mode 100644 index 00000000..3ee398f9 --- /dev/null +++ b/docs/manual/server-wide.html.en @@ -0,0 +1,100 @@ + + + +Server-Wide Configuration - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Server-Wide Configuration

+
+

Available Languages:  en  | + ja  | + ko 

+
+ +

This document explains some of the directives provided by +the core server which are used to configure +the basic operations of the server.

+
+ +
top
+
+

Server Identification

+ + +
Related ModulesRelated Directives
+ +

The ServerAdmin and + ServerTokens directives + control what information about the server will be presented + in server-generated documents such as error messages. The + ServerTokens directive + sets the value of the Server HTTP response header field.

+ +

The ServerName, + UseCanonicalName and + UseCanonicalPhysicalPort + directives are used by the server to determine how to construct + self-referential URLs. For example, when a client requests a + directory, but does not include the trailing slash in the + directory name, Apache must redirect the client to the full + name including the trailing slash so that the client will + correctly resolve relative references in the document.

+
top
+
+

File Locations

+ + +
Related ModulesRelated Directives
+ +

These directives control the locations of the various files + that Apache needs for proper operation. When the pathname used + does not begin with a slash (/), the files are located relative + to the ServerRoot. Be careful + about locating files in paths which are writable by non-root users. + See the security tips + documentation for more details.

+
top
+
+

Limiting Resource Usage

+ + +
Related ModulesRelated Directives
+ +

The LimitRequest* + directives are used to place limits on the amount of resources + Apache will use in reading requests from clients. By limiting + these values, some kinds of denial of service attacks can be + mitigated.

+ +

The RLimit* directives + are used to limit the amount of resources which can be used by + processes forked off from the Apache children. In particular, + this will control resources used by CGI scripts and SSI exec + commands.

+ +

The ThreadStackSize + directive is used with some platforms to control the stack size.

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/server-wide.html.ja.euc-jp b/docs/manual/server-wide.html.ja.euc-jp new file mode 100644 index 00000000..1fd9d599 --- /dev/null +++ b/docs/manual/server-wide.html.ja.euc-jp @@ -0,0 +1,101 @@ + + + +¥µ¡¼¥ÐÁ´ÂΤÎÀßÄê - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

¥µ¡¼¥ÐÁ´ÂΤÎÀßÄê

+
+

Available Languages:  en  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +

¤³¤Î¥É¥­¥å¥á¥ó¥È¤Ç¤Ïcore +¥µ¡¼¥Ð¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃæ¤Ç¡¢ +´ðËÜÆ°ºî¤òÀßÄꤹ¤ë¤¿¤á¤Î¤â¤Î¤òÀâÌÀ¤·¤Þ¤¹¡£

+
+ +
top
+
+

¥µ¡¼¥Ð ID

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

ServerAdmin ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + ServerTokens + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Ê¤É¤Î¥µ¡¼¥Ð¤¬ºî¤ë¥É¥­¥å¥á¥ó¥È¤Ë¡¢ + ¤É¤Î¤è¤¦¤Ê¥µ¡¼¥Ð¤Î¾ðÊó¤òɽ¼¨¤¹¤ë¤«¤òÀ©¸æ¤·¤Þ¤¹¡£ + ServerTokens ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Server HTTP + ¥ì¥¹¥Ý¥ó¥¹¥Ø¥Ã¥À¥Õ¥£¡¼¥ë¥É¤ÎÃͤòÀßÄꤷ¤Þ¤¹¡£

+ +

ServerName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + UseCanonicalName + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥µ¡¼¥Ð¤¬¼«Ê¬¼«¿È¤ò»²¾È¤¹¤ë URL + ¤òºî¤ë¤È¤­¤Ë»È¤ï¤ì¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬¥Ç¥£¥ì¥¯¥È¥ê¤òÍ׵ᤷ¤Æ¡¢ + ¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê̾¤ÎºÇ¸å¤Ë¥¹¥é¥Ã¥·¥å¤¬ÉÕ¤¤¤Æ¤¤¤Ê¤¤¤è¤¦¤Ê¾ì¹ç¤Ë¤Ï¡¢ + ¥É¥­¥å¥á¥ó¥È¤ÎÁêÂÐŪ¤Ê»²¾È¤òÀµ¤·¤¯²ò·è¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¡¢ + Apache ¤ÏºÇ¸å¤Î¥¹¥é¥Ã¥·¥å¤ò´Þ¤ó¤À´°Á´¤Ê¥Ñ¥¹¤Ë¥¯¥é¥¤¥¢¥ó¥È¤ò + ¥ê¥À¥¤¥ì¥¯¥È¤µ¤»¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

+
top
+
+

¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache + ¤¬Å¬ÀÚ¤ÊÆ°ºî¤ò¤¹¤ë¤¿¤á¤ËɬÍפʳƼï¥Õ¥¡¥¤¥ë¤Î°ÌÃÖ¤òÀ©¸æ¤·¤Þ¤¹¡£ + ¥Ñ¥¹¤¬¥¹¥é¥Ã¥·¥å (/) ¤Ç»Ï¤Þ¤Ã¤Æ¤¤¤Ê¤¤¤È¤­¤Ï¡¢¥Õ¥¡¥¤¥ë¤Ï + ServerRoot ¤«¤é¤ÎÁêÂХѥ¹¤È¤·¤Æ + õ¤µ¤ì¤Þ¤¹¡£root + °Ê³°¤Î¥æ¡¼¥¶¤¬½ñ¤­¹þ¤ß²Äǽ¤Ê¥Ñ¥¹¤Ë¥Õ¥¡¥¤¥ë¤òÃÖ¤¯¾ì¹ç¤ÏÃí°Õ¤¬É¬ÍפǤ¹¡£ + ¾ÜºÙ¤Ï¡Ö¥»¥­¥å¥ê¥Æ¥£¾ðÊó¡× + ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+
top
+
+

¥ê¥½¡¼¥¹¤ÎÀ©¸Â

+ + +
´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
+ +

LimitRequest* ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache + ¤¬¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¥ê¥¯¥¨¥¹¥ÈÆɤ߹þ¤ß¤Ç»È¤¦ + ¥ê¥½¡¼¥¹¤òÀ©¸Â¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£¤³¤ì¤é¤ÎÃͤòÀ©¸Â¤¹¤ë¤³¤È¤Ç¡¢ + ¤¤¤¯¤Ä¤«¤Î¥µ¡¼¥Ó¥¹µñÈݹ¶·â¤Ï±Æ¶Á¤òϤ餲¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ +

RLimit* ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Apache ¤Î»Ò¥×¥í¥»¥¹¤«¤é + fork ¤µ¤ì¤¿¥×¥í¥»¥¹¤¬»ÈÍѤ¹¤ë¥ê¥½¡¼¥¹¤òÀ©¸Â¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£ + Æäˡ¢¤³¤ì¤Ï CGI ¥¹¥¯¥ê¥×¥È¤È SSI exec + ¥³¥Þ¥ó¥É¤Ç»È¤ï¤ì¤ë¥ê¥½¡¼¥¹¤òÀ©¸æ¤·¤Þ¤¹¡£

+ +

ThreadStackSize ¤Ï Netware + ¤Ç¤Î¤ß¡¢¥¹¥¿¥Ã¥¯¤ÎÂ礭¤µ¤òÀ©¸æ¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£

+
+
+

Available Languages:  en  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/server-wide.html.ko.euc-kr b/docs/manual/server-wide.html.ko.euc-kr new file mode 100644 index 00000000..d50e6231 --- /dev/null +++ b/docs/manual/server-wide.html.ko.euc-kr @@ -0,0 +1,95 @@ + + + +¼­¹ö Àü¿ª ¼³Á¤ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

¼­¹ö Àü¿ª ¼³Á¤

+
+

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

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

ÀÌ ¹®¼­´Â core ¼­¹ö°¡ ¼­¹öÀÇ ±âº» ÇൿÀ» +¼³Á¤ÇϱâÀ§ÇØ Á¦°øÇÏ´Â Áö½Ã¾îÁß ÀϺθ¦ ¼³¸íÇÑ´Ù.

+
+ +
top
+
+

¼­¹ö ½Äº°

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

ServerAdmin°ú + ServerTokens Áö½Ã¾î´Â + ¿À·ù¹® µî ¼­¹ö°¡ »ý¼ºÇÏ´Â ¹®¼­¿¡ ³ª¿Ã ¼­¹ö¿¡ ´ëÇÑ Á¤º¸¸¦ + ¼³Á¤ÇÑ´Ù. ServerTokens + Áö½Ã¾î´Â ¼­¹ö HTTP ÀÀ´ä Çì´õ¸¦ ¼³Á¤ÇÑ´Ù.

+ +

¼­¹ö´Â ServerName°ú + UseCanonicalName + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ÀÚ±âÂüÁ¶ URLÀ» ¸¸µç´Ù. ¿¹¸¦ µé¾î, + Ŭ¶óÀ̾ðÆ®°¡ µð·ºÅ丮¸¦ ¿äûÇßÁö¸¸ µð·ºÅ丮¸í µÚ¿¡ ½½·¡½¬¸¦ + ºÙÀÌÁö¾ÊÀº °æ¿ì ¾ÆÆÄÄ¡´Â µÚ¿¡ ½½·¡½¬¸¦ ºÙÀÎ Àüü À̸§À» + Ŭ¶óÀ̾ðÆ®¿¡°Ô ¸®´ÙÀÌ·ºÆ®ÇÏ¿©, Ŭ¶óÀ̾ðÆ®°¡ ¹®¼­ÀÇ »ó´ëÂüÁ¶¸¦ + ¿Ã¹Ù·Î ã°Ô ÇÑ´Ù.

+
top
+
+

ÆÄÀÏ À§Ä¡

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

ÀÌ Áö½Ã¾îµéÀº ¾ÆÆÄÄ¡°¡ Á¤»óÀûÀ¸·Î µ¿ÀÛÇϱâÀ§ÇØ ÇÊ¿äÇÑ + ¿©·¯ ÆÄÀϵéÀÇ À§Ä¡¸¦ ¼³Á¤ÇÑ´Ù. °æ·Î¸íÀÌ ½½·¡½¬(/)·Î ½ÃÀÛÇÏÁö + ¾ÊÀ¸¸é, ServerRoot¿¡ + »ó´ëÀûÀÎ ÆÄÀÏÀ» ã´Â´Ù. root°¡ ¾Æ´Ñ »ç¿ëÀÚ¿¡°Ô ¾²±â±ÇÇÑÀÌ + ÀÖ´Â °æ·Î¿¡ ÆÄÀÏÀ» µÎÁö¾Êµµ·Ï Á¶½ÉÇضó. ´õ ÀÚ¼¼ÇÑ Á¤º¸´Â + º¸¾È ÆÁ + ¹®¼­¸¦ Âü°íÇ϶ó.

+
top
+
+

ÀÚ¿ø»ç¿ë Á¦ÇÑ

+ + +
°ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
+ +

LimitRequest* Áö½Ã¾î´Â ¾ÆÆÄÄ¡°¡ + Ŭ¶óÀ̾ðÆ®ÀÇ ¿äûÀ» ÀÐÀ» ¶§ »ç¿ëÇÒ ÀÚ¿ø·®À» Á¦ÇÑÇÑ´Ù. ÀÌ·± + °ªµéÀ» Á¦ÇÑÇÏ¿© ¼­ºñ½º°ÅºÎ(denial of service)·ù °ø°ÝÀ» + ÁÙÀÏ ¼ö ÀÖ´Ù.

+ +

RLimit* Áö½Ã¾î´Â ¾ÆÆÄÄ¡ ÀÚ½ÄÀÌ + »ý¼ºÇÏ´Â ÇÁ·Î¼¼½º°¡ »ç¿ëÇÒ ÀÚ¿ø·®À» Á¦ÇÑÇÑ´Ù. ƯÈ÷ CGI + ½ºÅ©¸³Æ®³ª SSI exec ¸í·É¾î°¡ »ç¿ëÇÒ ÀÚ¿øÀ» Á¦ÇÑÇÑ´Ù.

+ +

ThreadStackSize + Áö½Ã¾î´Â ½ºÅà ũ±â¸¦ Á¶ÀýÇϱâÀ§ÇØ Netware¿¡¼­¸¸ »ç¿ëÇÑ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/sitemap.html b/docs/manual/sitemap.html new file mode 100644 index 00000000..84947e10 --- /dev/null +++ b/docs/manual/sitemap.html @@ -0,0 +1,19 @@ +URI: sitemap.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: sitemap.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: sitemap.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: sitemap.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: sitemap.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/sitemap.html.de b/docs/manual/sitemap.html.de new file mode 100644 index 00000000..128faf79 --- /dev/null +++ b/docs/manual/sitemap.html.de @@ -0,0 +1,266 @@ + + + +Seitenindex - Apache HTTP Server + + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2
+

Seitenindex

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko 

+
+ +

Diese Seite verzeichnet die zur Zeit verfügbaren Dokumente der +Dokumentation zum Apache HTTP Server Version +2.2.

+
+ +
top
+

Hinweise zur Version

+ +
top
+

Bedienung des Apache HTTP Servers

+ +
top
+

Apache-Dokumentation zu virtuellen Hosts

+ +
top
+

Häufig gestellte Fragen (FAQ)

+ +
top
+

SSL/TLS-Verschlüsselung des Apache

+ +
top
+

Praxis / Anleitungen

+ +
top
+

Plattform-spezifische Anmerkungen

+ +
top
+

Apache HTTP Server und Hilfsprogramme

+ +
top
+

Weitere Apache-Dokumentationen

+ +
top
+

Apache-Module

+ +
top
+

Dokumentation für Entwickler

+ +
top
+

Glossar und Index

+ +
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/sitemap.html.en b/docs/manual/sitemap.html.en new file mode 100644 index 00000000..e3796b6a --- /dev/null +++ b/docs/manual/sitemap.html.en @@ -0,0 +1,264 @@ + + + +Sitemap - Apache HTTP Server + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2
+

Sitemap

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ +

This page lists the currently available documents of the +Apache HTTP Server Version 2.2 +Documentation.

+
+ +
top
+

Release Notes

+ +
top
+

Using the Apache HTTP Server

+ +
top
+

Apache Virtual Host documentation

+ +
top
+

Apache Server Frequently Asked Questions

+ +
top
+

Apache SSL/TLS Encryption

+ +
top
+

Guides, Tutorials, and HowTos

+ +
top
+

Platform-specific Notes

+ +
top
+

Apache HTTP Server and Supporting Programs

+ +
top
+

Apache Miscellaneous Documentation

+ +
top
+

Apache modules

+ +
top
+

Developer Documentation

+ +
top
+

Glossary and Index

+ +
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/sitemap.html.es b/docs/manual/sitemap.html.es new file mode 100644 index 00000000..cf8cae8f --- /dev/null +++ b/docs/manual/sitemap.html.es @@ -0,0 +1,269 @@ + + + +Mapa de este sitio web - Servidor HTTP Apache + + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2
+

Mapa de este sitio web

+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ +

Esta página contiene la lista con los documentos actualmente +disponibles de la Versión 2.2 de la +Documentación del Servidor HTTP Apache.

+
+ +
top
+

Notas de la Versión

+ +
top
+

Funcionamiento del Servidor HTTP Apache

+ +
top
+

Documuentación sobre Hosting Virtual en Apache

+ +
top
+

Preguntas Más Frecuentes sobre Apache

+ +
top
+

Encriptado SSL/TLS con Apache

+ +
top
+

Guías, Tutoriales, y HowTos

+ +
top
+

Notas específicas sobre plataformas

+ +
top
+

Programas de soporte y el Servidor HTTP Apache

+ +
top
+

Documentación adicional sobre Apache

+ +
top
+

Módulos de Apache

+ +
top
+

Documentación para desarrolladores

+ +
top
+

Glosario e Índice

+ +
+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/sitemap.html.ja.euc-jp b/docs/manual/sitemap.html.ja.euc-jp new file mode 100644 index 00000000..088073b1 --- /dev/null +++ b/docs/manual/sitemap.html.ja.euc-jp @@ -0,0 +1,263 @@ + + + +Site Map - Apache HTTP ¥µ¡¼¥Ð + + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2
+

Site Map

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +

¤³¤Î¥Ú¡¼¥¸¤Ï¸½»þÅÀ¤ÇÍøÍѲÄǽ¤Ê +Apache HTTP ¥µ¡¼¥Ð¥Ð¡¼¥¸¥ç¥ó 2.2 ¤Î¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó +¤Î°ìÍ÷¤Ç¤¹¡£

+
+ +
top
+

¥ê¥ê¡¼¥¹¤Î¥á¥â

+ +
top
+

Apache HTTP ¥µ¡¼¥Ð¤Î»ÈÍÑ

+ +
top
+

Apache ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¥É¥­¥å¥á¥ó¥È

+ +
top
+

Apache ¥µ¡¼¥Ð¤Î¤è¤¯¤¢¤ë¼ÁÌä

+ +
top
+

Apache ¤Î SSL/TLS °Å¹æ²½

+ +
top
+

¥¬¥¤¥É¡¢¥Á¥å¡¼¥È¥ê¥¢¥ë¡¢¥Ï¥¦¥Ä¡¼

+ +
top
+

¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¸ÇÍ­¤Î¾ðÊó

+ +
top
+

Apache HTTP ¥µ¡¼¥Ð¤È¥µ¥Ý¡¼¥È¥×¥í¥°¥é¥à

+ +
top
+

Apache ¤½¤Î¾

+ +
top
+

Apache ¥â¥¸¥å¡¼¥ë

+ +
top
+

³«È¯¼Ô¤Î¤¿¤á¤Î¥É¥­¥å¥á¥ó¥È

+ +
top
+

ÍѸ콸¤Èº÷°ú

+ +
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/sitemap.html.ko.euc-kr b/docs/manual/sitemap.html.ko.euc-kr new file mode 100644 index 00000000..411bf227 --- /dev/null +++ b/docs/manual/sitemap.html.ko.euc-kr @@ -0,0 +1,267 @@ + + + +»çÀÌÆ®¸Ê - Apache HTTP Server + + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2
+

»çÀÌÆ®¸Ê

+
+

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

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

ÀÌ ÆäÀÌÁö´Â ÇöÀç +Apache HTTP Server Version 2.2 +¹®¼­ ¸ñ·ÏÀ» º¸¿©ÁØ´Ù.

+
+ +
top
+

¹ßÇ¥¹®

+ +
top
+

¾ÆÆÄÄ¡ À¥¼­¹ö »ç¿ëÇϱâ

+ +
top
+

¾ÆÆÄÄ¡ °¡»óÈ£½ºÆ® ¹®¼­

+ +
top
+

¾ÆÆÄÄ¡ ¼­¹ö¿¡ ´ëÇØ ÀÚÁÖ ¹°¾îº¸´Â Áú¹®

+ +
top
+

¾ÆÆÄÄ¡ SSL/TLS ¾Ïȣȭ

+ +
top
+

Áöħ¼­, ÅõÅ丮¾ó, HowTo

+ +
top
+

Ç÷¡Æûº° ¼³¸í

+ +
top
+

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

+ +
top
+

±âŸ ¾ÆÆÄÄ¡ ¹®¼­

+ +
top
+

¾ÆÆÄÄ¡ ¸ðµâ

+ +
top
+

°³¹ßÀÚ ¹®¼­

+ +
top
+

¿ë¾î¿Í »öÀÎ

+ +
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/ssl/index.html b/docs/manual/ssl/index.html new file mode 100644 index 00000000..39629cac --- /dev/null +++ b/docs/manual/ssl/index.html @@ -0,0 +1,7 @@ +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/ssl/index.html.en b/docs/manual/ssl/index.html.en new file mode 100644 index 00000000..86476391 --- /dev/null +++ b/docs/manual/ssl/index.html.en @@ -0,0 +1,57 @@ + + + +Apache SSL/TLS Encryption - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Apache SSL/TLS Encryption

+
+

Available Languages:  en  | + ja 

+
+ +

The Apache HTTP Server module mod_ssl +provides an interface to the OpenSSL library, which provides +Strong Encryption using the Secure Sockets Layer and Transport Layer +Security protocols. The module and this documentation are based on +Ralf S. Engelschall's mod_ssl project.

+
+ +
top
+
+

Documentation

+ +
top
+
+

mod_ssl

+

Extensive documentation on the directives and environment variables +provided by this module is provided in the mod_ssl reference documentation. +

+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/ssl/index.html.ja.euc-jp b/docs/manual/ssl/index.html.ja.euc-jp new file mode 100644 index 00000000..bfa1c7e8 --- /dev/null +++ b/docs/manual/ssl/index.html.ja.euc-jp @@ -0,0 +1,59 @@ + + + +Apache ¤Î SSL/TLS °Å¹æ²½ - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

Apache ¤Î SSL/TLS °Å¹æ²½

+
+

Available Languages:  en  | + ja 

+
+ +

Apache HTTP ¥µ¡¼¥Ð¥â¥¸¥å¡¼¥ë mod_ssl ¤¬ +OpenSSL +¥é¥¤¥Ö¥é¥ê¤Ø¤Î¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¤¬¡¢¤³¤ì¤Ï +Secure Sockts Layer ¤È Transport Layer Security +¥×¥í¥È¥³¥ë¤òÍѤ¤¤¿¶¯ÎϤʰŹ沽¤òÄ󶡤·¤Þ¤¹¡£ +¤³¤Î¥â¥¸¥å¡¼¥ë¤ä¤³¤Îʸ½ñ¤Ï Ralf S. Engelschall ¤Î mod_ssl +¥×¥í¥¸¥§¥¯¥È¤Ë´ð¤Å¤¤¤Æ¤¤¤Þ¤¹¡£

+
+ +
top
+
+

Documentation

+ +
top
+
+

mod_ssl

+

¤³¤Î¥â¥¸¥å¡¼¥ë¤ÇÄ󶡤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä´Ä¶­ÊÑ¿ô¤Ë´Ø¤¹¤ë +¾Ü¤·¤¤Ê¸½ñ¤Ï¡¢mod_ssl +¥ê¥Õ¥¡¥ì¥ó¥¹¤ò¤´Í÷²¼¤µ¤¤¡£

+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/ssl/ssl_compat.html b/docs/manual/ssl/ssl_compat.html new file mode 100644 index 00000000..3a8ed1be --- /dev/null +++ b/docs/manual/ssl/ssl_compat.html @@ -0,0 +1,3 @@ +URI: ssl_compat.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/ssl/ssl_compat.html.en b/docs/manual/ssl/ssl_compat.html.en new file mode 100644 index 00000000..be0865f0 --- /dev/null +++ b/docs/manual/ssl/ssl_compat.html.en @@ -0,0 +1,226 @@ + + + +SSL/TLS Strong Encryption: Compatibility - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > SSL/TLS

SSL/TLS Strong Encryption: Compatibility

+
+

Available Languages:  en 

+
+ +
+

All PCs are compatible. But some of +them are more compatible than others.

+

-- Unknown

+
+ +

+This page covers backwards compatibility between mod_ssl and other +SSL solutions. mod_ssl is not the only SSL solution for Apache; four +additional products are (or were) also available: Ben Laurie's freely +available Apache-SSL (from +where mod_ssl were originally derived in 1998), Red Hat's commercial +Secure +Web Server (which was based on mod_ssl), Covalent's commercial Raven SSL Module (also based on +mod_ssl) and finally C2Net's (now Red Hat's) commercial product Stronghold (based +on a different evolution branch named Sioux up to Stronghold 2.x and +based on mod_ssl since Stronghold 3.x).

+ +

+mod_ssl mostly provides a superset of the functionality of all the other +solutions, so it's simple to migrate from one of the older modules to +mod_ssl. The configuration directives and environment variable names +used by the older SSL solutions vary from those used in mod_ssl; +mapping tables are included here to give the equivalents used by mod_ssl.

+
+ +
top
+
+

Configuration Directives

+

The mapping between configuration directives used by Apache-SSL +1.x and mod_ssl 2.0.x is given in Table +1. The mapping from Sioux 1.x and Stronghold 2.x is only partial +because of special functionality in these interfaces which mod_ssl +doesn't provide.

+ + +

Table 1: Configuration Directive Mapping

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Old Directivemod_ssl DirectiveComment
Apache-SSL 1.x & mod_ssl 2.0.x compatibility:
SSLEnableSSLEngine oncompactified
SSLDisableSSLEngine offcompactified
SSLLogFile fileSSLLog filecompactified
SSLRequiredCiphers specSSLCipherSuite specrenamed
SSLRequireCipher c1 ...SSLRequire %{SSL_CIPHER} in {"c1", +...}generalized
SSLBanCipher c1 ...SSLRequire not (%{SSL_CIPHER} in {"c1", +...})generalized
SSLFakeBasicAuthSSLOptions +FakeBasicAuthmerged
SSLCacheServerPath dir-functionality removed
SSLCacheServerPort integer-functionality removed
Apache-SSL 1.x compatibility:
SSLExportClientCertificatesSSLOptions +ExportCertDatamerged
SSLCacheServerRunDir dir-functionality not supported
Sioux 1.x compatibility:
SSL_CertFile fileSSLCertificateFile filerenamed
SSL_KeyFile fileSSLCertificateKeyFile filerenamed
SSL_CipherSuite argSSLCipherSuite argrenamed
SSL_X509VerifyDir argSSLCACertificatePath argrenamed
SSL_Log fileSSLLogFile filerenamed
SSL_Connect flagSSLEngine flagrenamed
SSL_ClientAuth argSSLVerifyClient argrenamed
SSL_X509VerifyDepth argSSLVerifyDepth argrenamed
SSL_FetchKeyPhraseFrom arg-not directly mappable; use SSLPassPhraseDialog
SSL_SessionDir dir-not directly mappable; use SSLSessionCache
SSL_Require expr-not directly mappable; use SSLRequire
SSL_CertFileType arg-functionality not supported
SSL_KeyFileType arg-functionality not supported
SSL_X509VerifyPolicy arg-functionality not supported
SSL_LogX509Attributes arg-functionality not supported
Stronghold 2.x compatibility:
StrongholdAccelerator engineSSLCryptoDevice enginerenamed
StrongholdKey dir-functionality not needed
StrongholdLicenseFile dir-functionality not needed
SSLFlag flagSSLEngine flagrenamed
SSLSessionLockFile fileSSLMutex filerenamed
SSLCipherList specSSLCipherSuite specrenamed
RequireSSLSSLRequireSSLrenamed
SSLErrorFile file-functionality not supported
SSLRoot dir-functionality not supported
SSL_CertificateLogDir dir-functionality not supported
AuthCertDir dir-functionality not supported
SSL_Group name-functionality not supported
SSLProxyMachineCertPath dirSSLProxyMachineCertificatePath dirrenamed
SSLProxyMachineCertFile fileSSLProxyMachineCertificateFile filerenamed
SSLProxyCipherList specSSLProxyCipherSpec specrenamed
+ +
top
+
+

Environment Variables

+ +

The mapping between environment variable names used by the older +SSL solutions and the names used by mod_ssl is given in Table 2.

+ +

Table 2: Environment Variable Derivation

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Old Variablemod_ssl VariableComment
SSL_PROTOCOL_VERSIONSSL_PROTOCOLrenamed
SSLEAY_VERSIONSSL_VERSION_LIBRARYrenamed
HTTPS_SECRETKEYSIZESSL_CIPHER_USEKEYSIZErenamed
HTTPS_KEYSIZESSL_CIPHER_ALGKEYSIZErenamed
HTTPS_CIPHERSSL_CIPHERrenamed
HTTPS_EXPORTSSL_CIPHER_EXPORTrenamed
SSL_SERVER_KEY_SIZESSL_CIPHER_ALGKEYSIZErenamed
SSL_SERVER_CERTIFICATESSL_SERVER_CERTrenamed
SSL_SERVER_CERT_STARTSSL_SERVER_V_STARTrenamed
SSL_SERVER_CERT_ENDSSL_SERVER_V_ENDrenamed
SSL_SERVER_CERT_SERIALSSL_SERVER_M_SERIALrenamed
SSL_SERVER_SIGNATURE_ALGORITHMSSL_SERVER_A_SIGrenamed
SSL_SERVER_DNSSL_SERVER_S_DNrenamed
SSL_SERVER_CNSSL_SERVER_S_DN_CNrenamed
SSL_SERVER_EMAILSSL_SERVER_S_DN_Emailrenamed
SSL_SERVER_OSSL_SERVER_S_DN_Orenamed
SSL_SERVER_OUSSL_SERVER_S_DN_OUrenamed
SSL_SERVER_CSSL_SERVER_S_DN_Crenamed
SSL_SERVER_SPSSL_SERVER_S_DN_SPrenamed
SSL_SERVER_LSSL_SERVER_S_DN_Lrenamed
SSL_SERVER_IDNSSL_SERVER_I_DNrenamed
SSL_SERVER_ICNSSL_SERVER_I_DN_CNrenamed
SSL_SERVER_IEMAILSSL_SERVER_I_DN_Emailrenamed
SSL_SERVER_IOSSL_SERVER_I_DN_Orenamed
SSL_SERVER_IOUSSL_SERVER_I_DN_OUrenamed
SSL_SERVER_ICSSL_SERVER_I_DN_Crenamed
SSL_SERVER_ISPSSL_SERVER_I_DN_SPrenamed
SSL_SERVER_ILSSL_SERVER_I_DN_Lrenamed
SSL_CLIENT_CERTIFICATESSL_CLIENT_CERTrenamed
SSL_CLIENT_CERT_STARTSSL_CLIENT_V_STARTrenamed
SSL_CLIENT_CERT_ENDSSL_CLIENT_V_ENDrenamed
SSL_CLIENT_CERT_SERIALSSL_CLIENT_M_SERIALrenamed
SSL_CLIENT_SIGNATURE_ALGORITHMSSL_CLIENT_A_SIGrenamed
SSL_CLIENT_DNSSL_CLIENT_S_DNrenamed
SSL_CLIENT_CNSSL_CLIENT_S_DN_CNrenamed
SSL_CLIENT_EMAILSSL_CLIENT_S_DN_Emailrenamed
SSL_CLIENT_OSSL_CLIENT_S_DN_Orenamed
SSL_CLIENT_OUSSL_CLIENT_S_DN_OUrenamed
SSL_CLIENT_CSSL_CLIENT_S_DN_Crenamed
SSL_CLIENT_SPSSL_CLIENT_S_DN_SPrenamed
SSL_CLIENT_LSSL_CLIENT_S_DN_Lrenamed
SSL_CLIENT_IDNSSL_CLIENT_I_DNrenamed
SSL_CLIENT_ICNSSL_CLIENT_I_DN_CNrenamed
SSL_CLIENT_IEMAILSSL_CLIENT_I_DN_Emailrenamed
SSL_CLIENT_IOSSL_CLIENT_I_DN_Orenamed
SSL_CLIENT_IOUSSL_CLIENT_I_DN_OUrenamed
SSL_CLIENT_ICSSL_CLIENT_I_DN_Crenamed
SSL_CLIENT_ISPSSL_CLIENT_I_DN_SPrenamed
SSL_CLIENT_ILSSL_CLIENT_I_DN_Lrenamed
SSL_EXPORTSSL_CIPHER_EXPORTrenamed
SSL_KEYSIZESSL_CIPHER_ALGKEYSIZErenamed
SSL_SECKEYSIZESSL_CIPHER_USEKEYSIZErenamed
SSL_SSLEAY_VERSIONSSL_VERSION_LIBRARYrenamed
SSL_STRONG_CRYPTO-Not supported by mod_ssl
SSL_SERVER_KEY_EXP-Not supported by mod_ssl
SSL_SERVER_KEY_ALGORITHM-Not supported by mod_ssl
SSL_SERVER_KEY_SIZE-Not supported by mod_ssl
SSL_SERVER_SESSIONDIR-Not supported by mod_ssl
SSL_SERVER_CERTIFICATELOGDIR-Not supported by mod_ssl
SSL_SERVER_CERTFILE-Not supported by mod_ssl
SSL_SERVER_KEYFILE-Not supported by mod_ssl
SSL_SERVER_KEYFILETYPE-Not supported by mod_ssl
SSL_CLIENT_KEY_EXP-Not supported by mod_ssl
SSL_CLIENT_KEY_ALGORITHM-Not supported by mod_ssl
SSL_CLIENT_KEY_SIZE-Not supported by mod_ssl
+ +
top
+
+

Custom Log Functions

+

+When mod_ssl is enabled, additional functions exist for the Custom Log Format of +mod_log_config as documented in the Reference +Chapter. Beside the ``%{varname}x'' +eXtension format function which can be used to expand any variables provided +by any module, an additional Cryptography +``%{name}c'' cryptography format function +exists for backward compatibility. The currently implemented function calls +are listed in Table 3.

+ +

Table 3: Custom Log Cryptography Function

+ + + + + + + + + + + + +
Function CallDescription
%...{version}c SSL protocol version
%...{cipher}c SSL cipher
%...{subjectdn}c Client Certificate Subject Distinguished Name
%...{issuerdn}c Client Certificate Issuer Distinguished Name
%...{errcode}c Certificate Verification Error (numerical)
%...{errstr}c Certificate Verification Error (string)
+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/ssl/ssl_faq.html b/docs/manual/ssl/ssl_faq.html new file mode 100644 index 00000000..c6d2ea13 --- /dev/null +++ b/docs/manual/ssl/ssl_faq.html @@ -0,0 +1,3 @@ +URI: ssl_faq.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/ssl/ssl_faq.html.en b/docs/manual/ssl/ssl_faq.html.en new file mode 100644 index 00000000..0526f619 --- /dev/null +++ b/docs/manual/ssl/ssl_faq.html.en @@ -0,0 +1,1044 @@ + + + +SSL/TLS Strong Encryption: FAQ - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > SSL/TLS

SSL/TLS Strong Encryption: FAQ

+
+

Available Languages:  en 

+
+ +
+

The wise man doesn't give the right answers, +he poses the right questions.

+

-- Claude Levi-Strauss

+ +
+

This chapter is a collection of frequently asked questions (FAQ) and +corresponding answers following the popular USENET tradition. Most of these +questions occurred on the Newsgroup comp.infosystems.www.servers.unix or the mod_ssl Support +Mailing List modssl-users@modssl.org. They are collected at this place +to avoid answering the same questions over and over.

+ +

Please read this chapter at least once when installing mod_ssl or at least +search for your problem here before submitting a problem report to the +author.

+
+ +
top
+
+

About The Module

+ + +

What is the history of mod_ssl?

+

The mod_ssl v1 package was initially created in April 1998 by Ralf S. Engelschall via porting Ben Laurie's Apache-SSL 1.17 source patches for + Apache 1.2.6 to Apache 1.3b6. Because of conflicts with Ben + Laurie's development cycle it then was re-assembled from scratch for + Apache 1.3.0 by merging the old mod_ssl 1.x with the newer Apache-SSL + 1.18. From this point on mod_ssl lived its own life as mod_ssl v2. The + first publicly released version was mod_ssl 2.0.0 from August 10th, + 1998.

+ +

After US export restrictions on cryptographic software were + loosened, mod_ssl became part of the Apache HTTP + Server with the release of Apache httpd 2.

+ + +

Is mod_ssl affected by the Wassenaar Arrangement?

+

First, let us explain what Wassenaar and its Arrangement on + Export Controls for Conventional Arms and Dual-Use Goods and + Technologies is: This is a international regime, established in 1995, to + control trade in conventional arms and dual-use goods and technology. It + replaced the previous CoCom regime. Further details on + both the Arrangement and its signatories are available at http://www.wassenaar.org/.

+ +

In short, the aim of the Wassenaar Arrangement is to prevent the build up + of military capabilities that threaten regional and international security + and stability. The Wassenaar Arrangement controls the export of + cryptography as a dual-use good, that is, something that has both military and + civilian applications. However, the Wassenaar Arrangement also provides an + exemption from export controls for mass-market software and free software.

+ +

In the current Wassenaar List of Dual Use Goods and Technologies And + Munitions, under GENERAL SOFTWARE NOTE (GSN) it says + The Lists do not control "software" which is either: 1. [...] 2. "in + the public domain". And under DEFINITIONS OF TERMS USED IN + THESE LISTS we find In the public + domain defined as "technology" or "software" which has been made + available without restrictions upon its further dissemination. Note: + Copyright restrictions do not remove "technology" or "software" from being + "in the public domain".

+ +

So, both mod_ssl and OpenSSL are in the public domain for the purposes + of the Wassenaar Arrangement and its List of Dual Use Goods and + Technologies And Munitions List, and thus not affected by its provisions.

+ + +
top
+
+

Installation

+ + +

Why do I get permission errors related to + SSLMutex when I start Apache?

+

Errors such as ``mod_ssl: Child could not open + SSLMutex lockfile /opt/apache/logs/ssl_mutex.18332 (System error follows) + [...] System: Permission denied (errno: 13)'' are usually + caused by overly restrictive permissions on the parent directories. + Make sure that all parent directories (here /opt, + /opt/apache and /opt/apache/logs) have the x-bit + set for, at minimum, the UID under which Apache's children are running (see + the User directive).

+ + +

Why does mod_ssl stop with the error + "Failed to generate temporary 512 bit RSA private key", when I start + Apache?

+

Cryptographic software needs a source of unpredictable data + to work correctly. Many open source operating systems provide + a "randomness device" that serves this purpose (usually named + /dev/random). On other systems, applications have to + seed the OpenSSL Pseudo Random Number Generator (PRNG) manually with + appropriate data before generating keys or performing public key + encryption. As of version 0.9.5, the OpenSSL functions that need + randomness report an error if the PRNG has not been seeded with + at least 128 bits of randomness.

+

To prevent this error, mod_ssl has to provide + enough entropy to the PRNG to allow it to work correctly. This can + be done via the SSLRandomSeed + directives.

+ +
top
+
+

Configuration

+ + +

Is it possible to provide HTTP and HTTPS + from the same server?

+

Yes. HTTP and HTTPS use different server ports (HTTP binds to + port 80, HTTPS to port 443), so there is no direct conflict between + them. You can either run two separate server instances bound to + these ports, or use Apache's elegant virtual hosting facility to + create two virtual servers over one instance of Apache - one + responding to requests on port 80 and speaking HTTP and the other + responding to requests on port 443 speaking HTTPS.

+ + +

Which port does HTTPS use?

+

You can run HTTPS on any port, but the standards specify port 443, which + is where any HTTPS compliant browser will look by default. You can force + your browser to look on a different port by specifying it in the URL like + this (for port 666): https://secure.server.dom:666/

+ + +

How do I speak HTTPS manually for testing purposes?

+

While you usually just use

+ +

$ telnet localhost 80
+ GET / HTTP/1.0

+ +

for simple testing of Apache via HTTP, it's not so easy for + HTTPS because of the SSL protocol between TCP and HTTP. With the + help of OpenSSL's s_client command, however, you can + do a similar check for HTTPS:

+ +

$ openssl s_client -connect localhost:443 -state -debug
+ GET / HTTP/1.0

+ +

Before the actual HTTP response you will receive detailed + information about the SSL handshake. For a more general command + line client which directly understands both HTTP and HTTPS, can + perform GET and POST operations, can use a proxy, supports byte + ranges, etc. you should have a look at the nifty + cURL tool. Using this, you can + check that Apache is responding correctly on ports 80 and 443 as + follows:

+ +

$ curl http://localhost/
+ $ curl https://localhost/

+ + +

Why does the connection hang when I connect + to my SSL-aware Apache server?

+

Because you connected with HTTP to the HTTPS port, i.e. you used an URL of + the form ``http://'' instead of ``https://''. + This also happens the other way round when you connect via HTTPS to a HTTP + port, i.e. when you try to use ``https://'' on a server that + doesn't support SSL (on this port). Make sure you are connecting to a + virtual server that supports SSL, which is probably the IP associated with + your hostname, not localhost (127.0.0.1).

+ + +

Why do I get ``Connection Refused'' messages, + when trying to access my newly installed Apache+mod_ssl server via HTTPS?

+

This can happen for various reasons. The most common mistakes + include starting Apache with just apachectl start (or + httpd) instead of apachectl startssl (or + httpd -DSSL). Your configuration may also be incorrect. + Please make sure that your Listen directives match your + <VirtualHost> + directives. If all else fails, please start afresh, using the default + configuration provided by mod_ssl.

+ + +

Why are the SSL_XXX variables + not available to my CGI & SSI scripts?

+

Please make sure you have ``SSLOptions +StdEnvVars'' + enabled for the context of your CGI/SSI requests.

+ + +

How can I switch between HTTP and HTTPS in relative + hyperlinks?

+ +

Usually, to switch between HTTP and HTTPS, you have to use + fully-qualified hyperlinks (because you have to change the URL + scheme). Using mod_rewrite however, you can + manipulate relative hyperlinks, to achieve the same effect.

+

+ RewriteEngine on
+ RewriteRule ^/(.*):SSL$ https://%{SERVER_NAME}/$1 [R,L]
+ RewriteRule ^/(.*):NOSSL$ http://%{SERVER_NAME}/$1 [R,L] +

+ +

This rewrite ruleset lets you use hyperlinks of the form + <a href="document.html:SSL">, to switch to HTTPS + in a relative link.

+ +
top
+
+

Certificates

+ + +

What are RSA Private Keys, CSRs and Certificates?

+

An RSA private key file is a digital file that you can use to decrypt + messages sent to you. It has a public component which you distribute (via + your Certificate file) which allows people to encrypt those messages to + you.

+

A Certificate Signing Request (CSR) is a digital file which contains + your public key and your name. You send the CSR to a Certifying Authority + (CA), who will convert it into a real Certificate, by signing it.

+

A Certificate contains your + RSA public key, your name, the name of the CA, and is digitally signed by + the CA. Browsers that know the CA can verify the signature on that + Certificate, thereby obtaining your RSA public key. That enables them to + send messages which only you can decrypt.

+

See the Introduction chapter for a general + description of the SSL protocol.

+ + +

Is there a difference on startup between + the original Apache and an SSL-aware Apache?

+

Yes. In general, starting Apache with + mod_ssl built-in is just like starting Apache + without it. However, if you have a passphrase on your SSL private + key file, a startup dialog will pop up which asks you to enter the + pass phrase.

+ +

Having to manually enter the passphrase when starting the server + can be problematic - for example, when starting the server from the + system boot scripts. In this case, you can follow the steps + below to remove the passphrase from + your private key.

+ + +

How do I create a self-signed SSL +Certificate for testing purposes?

+
    +
  1. Make sure OpenSSL is installed and in your PATH.
    +
    +
    2. +
  2. Run the following command, to create server.key and + server.crt files:
    + $ openssl req -new -x509 -nodes -out server.crt + -keyout server.key
    + These can be used as follows in your httpd.conf + file: + 
    +             SSLCertificateFile    /path/to/this/server.crt
+             SSLCertificateKeyFile /path/to/this/server.key
+
    +
    3. +
  3. It is important that you are aware that this + server.key does not have any passphrase. + To add a passphrase to the key, you should run the following + command, and enter & verify the passphrase as requested.
    +

    $ openssl rsa -des3 -in server.key -out + server.key.new
    + $ mv server.key.new server.key

    + Please backup the server.key file, and the passphrase + you entered, in a secure location. +
    4. +
+ + +

How do I create a real SSL Certificate?

+

Here is a step-by-step description:

+
    +
  1. Make sure OpenSSL is installed and in your PATH. +
    +
    +
    2. +
  2. Create a RSA private key for your Apache server + (will be Triple-DES encrypted and PEM formatted):
    +
    + $ openssl genrsa -des3 -out server.key 1024
    +
    + Please backup this server.key file and the + pass-phrase you entered in a secure location. + You can see the details of this RSA private key by using the command:
    + +
    + $ openssl rsa -noout -text -in server.key
    +
    + If necessary, you can also create a decrypted PEM version (not + recommended) of this RSA private key with:
    +
    + $ openssl rsa -in server.key -out server.key.unsecure
    +
    + +
    3. +
  3. Create a Certificate Signing Request (CSR) with the server RSA private + key (output will be PEM formatted):
    +
    + $ openssl req -new -key server.key -out server.csr
    +
    + Make sure you enter the FQDN ("Fully Qualified Domain Name") of the + server when OpenSSL prompts you for the "CommonName", i.e. when you + generate a CSR for a website which will be later accessed via + https://www.foo.dom/, enter "www.foo.dom" here. + You can see the details of this CSR by using
    + +
    + $ openssl req -noout -text -in server.csr
    +
    +
    4. +
  4. You now have to send this Certificate Signing Request (CSR) to + a Certifying Authority (CA) to be signed. Once the CSR has been + signed, you will have a real Certificate, which can be used by + Apache. You can have a CSR signed by a commercial CA, or you can + create your own CA to sign it.
    + Commercial CAs usually ask you to post the CSR into a web form, + pay for the signing, and then send a signed Certificate, which + you can store in a server.crt file. For more information about + commercial CAs see the following locations:
    +
    +
      +
    1. Verisign
      + + http://digitalid.verisign.com/server/apacheNotice.htm + +
      2. +
    2. Thawte
      + http://www.thawte.com/ +
      3. +
    3. CertiSign Certificadora Digital Ltda.
      + + http://www.certisign.com.br + +
      4. +
    4. IKS GmbH
      + + http://www.iks-jena.de/leistungen/ca/ + +
      5. +
    5. Uptime Commerce Ltd.
      + + http://www.uptimecommerce.com + +
      6. +
    6. BelSign NV/SA
      + + http://www.belsign.be + +
      7. +
    + + For details on how to create your own CA, and use this to sign + a CSR, see below.
    + + Once your CSR has been signed, you can see the details of the + Certificate as follows:
    +
    + $ openssl x509 -noout -text -in server.crt
    + +
    5. +
  5. You should now have two files: server.key and + server.crt. These can be used as follows in your + httpd.conf file: + 
    +       SSLCertificateFile    /path/to/this/server.crt
+       SSLCertificateKeyFile /path/to/this/server.key
+
    + The server.csr file is no longer needed. +
    6. + +
+ + +

How do I create and use my own Certificate Authority (CA)?

+

The short answer is to use the CA.sh or CA.pl + script provided by OpenSSL. Unless you have a good reason not to, + you should use these for preference. If you cannot, you can create a + self-signed Certificate as follows:

+ +
    +
  1. Create a RSA private key for your server + (will be Triple-DES encrypted and PEM formatted):
    +
    + $ openssl genrsa -des3 -out server.key 1024
    +
    + Please backup this host.key file and the + pass-phrase you entered in a secure location. + You can see the details of this RSA private key by using the + command:
    + $ openssl rsa -noout -text -in server.key
    +
    + If necessary, you can also create a decrypted PEM version (not + recommended) of this RSA private key with:
    +
    + $ openssl rsa -in server.key -out server.key.unsecure
    +
    +
    2. +
  2. Create a self-signed Certificate (X509 structure) + with the RSA key you just created (output will be PEM formatted):
    +
    + $ openssl req -new -x509 -nodes -sha1 -days 365 + -key server.key -out server.crt
    +
    + This signs the server CSR and results in a server.crt file.
    + You can see the details of this Certificate using:
    +
    + $ openssl x509 -noout -text -in server.crt
    +
    +
    3. +
+ + +

How can I change the pass-phrase on my private key file?

+

You simply have to read it with the old pass-phrase and write it again, + specifying the new pass-phrase. You can accomplish this with the following + commands:

+ + +

$ openssl rsa -des3 -in server.key -out server.key.new
+ $ mv server.key.new server.key

+ +

The first time you're asked for a PEM pass-phrase, you should + enter the old pass-phrase. After that, you'll be asked again to + enter a pass-phrase - this time, use the new pass-phrase. If you + are asked to verify the pass-phrase, you'll need to enter the new + pass-phrase a second time.

+ + +

How can I get rid of the pass-phrase dialog at Apache startup time?

+

The reason this dialog pops up at startup and every re-start + is that the RSA private key inside your server.key file is stored in + encrypted format for security reasons. The pass-phrase is needed decrypt + this file, so it can be read and parsed. Removing the pass-phrase + removes a layer of security from your server - proceed with caution!

+
    +
  1. Remove the encryption from the RSA private key (while + keeping a backup copy of the original file):
    +
    + $ cp server.key server.key.org
    + $ openssl rsa -in server.key.org -out server.key
    + +
    +
    2. +
  2. Make sure the server.key file is only readable by root:
    +
    + $ chmod 400 server.key
    +
    +
    3. +
+ +

Now server.key contains an unencrypted copy of the key. + If you point your server at this file, it will not prompt you for a + pass-phrase. HOWEVER, if anyone gets this key they will be able to + impersonate you on the net. PLEASE make sure that the permissions on this + file are such that only root or the web server user can read it + (preferably get your web server to start as root but run as another + user, and have the key readable only by root).

+ +

As an alternative approach you can use the ``SSLPassPhraseDialog + exec:/path/to/program'' facility. Bear in mind that this is + neither more nor less secure, of course.

+ + +

How do I verify that a private key matches its Certificate?

+

A private key contains a series of numbers. Two of these numbers form + the "public key", the others are part of the "private key". The "public + key" bits are included when you generate a CSR, and subsequently form + part of the associated Certificate.

+

To check that the public key in your Certificate matches the public + portion of your private key, you simply need to compare these numbers. + To view the Certificate and the key run the commands:

+ +

$ openssl x509 -noout -text -in server.crt
+ $ openssl rsa -noout -text -in server.key

+ +

The `modulus' and the `public exponent' portions in the key and the + Certificate must match. As the public exponent is usually 65537 + and it's difficult to visually check that the long modulus numbers + are the same, you can use the following approach:

+ +

$ openssl x509 -noout -modulus -in server.crt | openssl md5
+ $ openssl rsa -noout -modulus -in server.key | openssl md5

+ +

This leaves you with two rather shorter numbers to compare. It is, + in theory, possible that these numbers may be the same, without the + modulus numbers being the same, but the chances of this are + overwhelmingly remote.

+

Should you wish to check to which key or certificate a particular + CSR belongs you can perform the same calculation on the CSR as + follows:

+ +

$ openssl req -noout -modulus -in server.csr | openssl md5

+ + +

Why do connections fail with an "alert +bad certificate" error?

+

Errors such as OpenSSL: error:14094412: SSL + routines:SSL3_READ_BYTES:sslv3 alert bad certificate in the SSL + logfile, are usually caused a browser which is unable to handle the server + certificate/private-key. For example, Netscape Navigator 3.x is + unable to handle RSA key lengths not equal to 1024 bits.

+ + +

Why does my 2048-bit private key not work?

+

The private key sizes for SSL must be either 512 or 1024 bits, for compatibility + with certain web browsers. A keysize of 1024 bits is recommended because + keys larger than 1024 bits are incompatible with some versions of Netscape + Navigator and Microsoft Internet Explorer, and with other browsers that + use RSA's BSAFE cryptography toolkit.

+ + +

Why is client authentication broken after upgrading from +SSLeay version 0.8 to 0.9?

+

The CA certificates under the path you configured with + SSLCACertificatePath are found by SSLeay through hash + symlinks. These hash values are generated by the `openssl x509 -noout + -hash' command. However, the algorithm used to calculate the hash for a + certificate changed between SSLeay 0.8 and 0.9. You will need to remove + all old hash symlinks and create new ones after upgrading. Use the + Makefile provided by mod_ssl.

+ + +

How can I convert a certificate from PEM to DER format?

+

The default certificate format for SSLeay/OpenSSL is PEM, which is simply + Base64 encoded DER, with header and footer lines. For some applications + (e.g. Microsoft Internet Explorer) you need the certificate in plain DER + format. You can convert a PEM file cert.pem into the + corresponding DER file cert.der using the following command: + $ openssl x509 -in cert.pem -out cert.der -outform DER

+ + +

Why can't I find the +getca or getverisign programs mentioned by +Verisign, for installing my Verisign certificate?

+

Verisign has never provided specific instructions + for Apache+mod_ssl. The instructions provided are for C2Net's + Stronghold (a commercial Apache based server with SSL support).

+

To install your certificate, all you need to do is to save the + certificate to a file, and give the name of that file to the + SSLCertificateFile directive. + You will also need to give it the key file. For more information, + see the SSLCertificateKeyFile + directive.

+ + +

Can I use the Server Gated Cryptography (SGC) +facility (aka Verisign Global ID) with mod_ssl?

+

Yes. mod_ssl has included support for the SGC + facility since version 2.1. No special configuration is required - + just use the Global ID as your server certificate. The + step up of the clients is then automatically handled by + mod_ssl at run-time.

+ + +

Why do browsers complain that they cannot +verify my Verisign Global ID server certificate?

+

Verisign uses an intermediate CA certificate between the root CA + certificate (which is installed in the browsers) and the server + certificate (which you installed on the server). You should have + received this additional CA certificate from Verisign. + If not, complain to them. Then, configure this certificate with the + SSLCertificateChainFile + directive. This ensures that the intermediate CA certificate is + sent to the browser, filling the gap in the certificate chain.

+ +
top
+
+

The SSL Protocol

+ + +

Why do I get lots of random SSL protocol +errors under heavy server load?

+

There can be a number of reasons for this, but the main one + is problems with the SSL session Cache specified by the + SSLSessionCache directive. The DBM session + cache is the most likely source of the problem, so using the SHM session cache (or + no cache at all) may help.

+ + +

Why does my webserver have a higher load, now +that it serves SSL encrypted traffic?

+

SSL uses strong cryptographic encryption, which necessitates a lot of + number crunching. When you request a webpage via HTTPS, everything (even + the images) is encrypted before it is transferred. So increased HTTPS + traffic leads to load increases.

+ + +

Why do HTTPS connections to my server +sometimes take up to 30 seconds to establish a connection?

+

This is usually caused by a /dev/random device for + SSLRandomSeed which blocks the + read(2) call until enough entropy is available to service the + request. More information is available in the reference + manual for the SSLRandomSeed + directive.

+ + +

What SSL Ciphers are supported by mod_ssl?

+

Usually, any SSL ciphers supported by the version of OpenSSL in use, + are also supported by mod_ssl. Which ciphers are + available can depend on the way you built OpenSSL. Typically, at + least the following ciphers are supported:

+ +
    +
  1. RC4 with MD5
    2. +
  2. RC4 with MD5 (export version restricted to 40-bit key)
    3. +
  3. RC2 with MD5
    4. +
  4. RC2 with MD5 (export version restricted to 40-bit key)
    5. +
  5. IDEA with MD5
    6. +
  6. DES with MD5
    7. +
  7. Triple-DES with MD5
    8. +
+ +

To determine the actual list of ciphers available, you should run + the following:

+

$ openssl ciphers -v

+ + +

Why do I get ``no shared cipher'' errors, when +trying to use Anonymous Diffie-Hellman (ADH) ciphers?

+

By default, OpenSSL does not allow ADH ciphers, for security + reasons. Please be sure you are aware of the potential side-effects + if you choose to enable these ciphers.

+

In order to use Anonymous Diffie-Hellman (ADH) ciphers, you must + build OpenSSL with ``-DSSL_ALLOW_ADH'', and then add + ``ADH'' into your SSLCipherSuite.

+ + +

Why do I get a 'no shared ciphers' +error when connecting to my newly installed server?

+

Either you have made a mistake with your + SSLCipherSuite + directive (compare it with the pre-configured example in + httpd.conf-dist) or you chose to use DSA/DH + algorithms instead of RSA when you generated your private key + and ignored or overlooked the warnings. If you have chosen + DSA/DH, then your server cannot communicate using RSA-based SSL + ciphers (at least until you configure an additional RSA-based + certificate/key pair). Modern browsers like NS or IE can only + communicate over SSL using RSA ciphers. The result is the + "no shared ciphers" error. To fix this, regenerate your server + certificate/key pair, using the RSA algorithm.

+ + +

Why can't I use SSL with name-based/non-IP-based virtual hosts?

+

The reason is very technical, and a somewhat "chicken and egg" problem. + The SSL protocol layer stays below the HTTP protocol layer and + encapsulates HTTP. When an SSL connection (HTTPS) is established + Apache/mod_ssl has to negotiate the SSL protocol parameters with the + client. For this, mod_ssl has to consult the configuration of the virtual + server (for instance it has to look for the cipher suite, the server + certificate, etc.). But in order to go to the correct virtual server + Apache has to know the Host HTTP header field. To do this, the + HTTP request header has to be read. This cannot be done before the SSL + handshake is finished, but the information is needed in order to + complete the SSL handshake phase. Bingo!

+ + +

Why is it not possible to use Name-Based +Virtual Hosting to identify different SSL virtual hosts?

+

Name-Based Virtual Hosting is a very popular method of identifying + different virtual hosts. It allows you to use the same IP address and + the same port number for many different sites. When people move on to + SSL, it seems natural to assume that the same method can be used to have + lots of different SSL virtual hosts on the same server.

+ +

It comes as rather a shock to learn that it is impossible.

+ +

The reason is that the SSL protocol is a separate layer which + encapsulates the HTTP protocol. So the SSL session is a separate + transaction, that takes place before the HTTP session has begun. + The server receives an SSL request on IP address X and port Y + (usually 443). Since the SSL request does not contain any Host: + field, the server has no way to decide which SSL virtual host to use. + Usually, it will just use the first one it finds, which matches the + port and IP address specified.

+ +

You can, of course, use Name-Based Virtual Hosting to identify many + non-SSL virtual hosts (all on port 80, for example) and then + have a single SSL virtual host (on port 443). But if you do this, + you must make sure to put the non-SSL port number on the NameVirtualHost + directive, e.g.

+ +

+ NameVirtualHost 192.168.1.1:80 +

+ +

Other workaround solutions include:

+ +

Using separate IP addresses for different SSL hosts. + Using different port numbers for different SSL hosts.

+ + +

How do I get SSL compression working?

+

Although SSL compression negotiation was defined in the specification +of SSLv2 and TLS, it took until May 2004 for RFC 3749 to define DEFLATE as +a negotiable standard compression method. +

+

OpenSSL 0.9.8 started to support this by default when compiled with the +zlib option. If both the client and the server support compression, +it will be used. However, most clients still try to initially connect with an +SSLv2 Hello. As SSLv2 did not include an array of prefered compression algorithms +in its handshake, compression cannot be negotiated with these clients. +If the client disables support for SSLv2, either an SSLv3 or TLS Hello +may be sent, depending on which SSL library is used, and compression may +be set up. You can verify whether clients make use of SSL compression by +logging the %{SSL_COMPRESS_METHOD}x variable. +

+ + +

When I use Basic Authentication over HTTPS +the lock icon in Netscape browsers stays unlocked when the dialog pops up. +Does this mean the username/password is being sent unencrypted?

+

No, the username/password is transmitted encrypted. The icon in + Netscape browsers is not actually synchronized with the SSL/TLS layer. + It only toggles to the locked state when the first part of the actual + webpage data is transferred, which may confuse people. The Basic + Authentication facility is part of the HTTP layer, which is above + the SSL/TLS layer in HTTPS. Before any HTTP data communication takes + place in HTTPS, the SSL/TLS layer has already completed its handshake + phase, and switched to encrypted communication. So don't be + confused by this icon.

+ + +

Why do I get I/O errors when connecting via +HTTPS to an Apache+mod_ssl server with Microsoft Internet Explorer (MSIE)?

+

The first reason is that the SSL implementation in some MSIE versions has + some subtle bugs related to the HTTP keep-alive facility and the SSL close + notify alerts on socket connection close. Additionally the interaction + between SSL and HTTP/1.1 features are problematic in some MSIE versions. + You can work around these problems by forcing Apache not to use HTTP/1.1, + keep-alive connections or send the SSL close notify messages to MSIE clients. + This can be done by using the following directive in your SSL-aware + virtual host section:

+

+ SetEnvIf User-Agent ".*MSIE.*" \
+ nokeepalive ssl-unclean-shutdown \
+ downgrade-1.0 force-response-1.0 +

+

Further, some MSIE versions have problems with particular ciphers. + Unfortunately, it is not possible to implement a MSIE-specific + workaround for this, because the ciphers are needed as early as the + SSL handshake phase. So a MSIE-specific + SetEnvIf won't solve these + problems. Instead, you will have to make more drastic + adjustments to the global parameters. Before you decide to do + this, make sure your clients really have problems. If not, do not + make these changes - they will affect all your clients, MSIE + or otherwise.

+ +

The next problem is that 56bit export versions of MSIE 5.x + browsers have a broken SSLv3 implementation, which interacts badly + with OpenSSL versions greater than 0.9.4. You can accept this and + require your clients to upgrade their browsers, you can downgrade to + OpenSSL 0.9.4 (not advised), or you can work around this, accepting + that your workaround will affect other browsers too:

+

SSLProtocol all -SSLv3

+

will completely disables the SSLv3 protocol and allow those + browsers to work. A better workaround is to disable only those + ciphers which cause trouble.

+

SSLCipherSuite + ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP +

+ +

This also allows the broken MSIE versions to work, but only removes the + newer 56bit TLS ciphers.

+ +

Another problem with MSIE 5.x clients is that they refuse to connect to + URLs of the form https://12.34.56.78/ (where IP-addresses are used + instead of the hostname), if the server is using the Server Gated + Cryptography (SGC) facility. This can only be avoided by using the fully + qualified domain name (FQDN) of the website in hyperlinks instead, because + MSIE 5.x has an error in the way it handles the SGC negotiation.

+ +

And finally there are versions of MSIE which seem to require that + an SSL session can be reused (a totally non standard-conforming + behaviour, of course). Connecting with those MSIE versions only work + if a SSL session cache is used. So, as a work-around, make sure you + are using a session cache (see the SSLSessionCache directive).

+ + +

Why do I get I/O errors, or the message "Netscape has +encountered bad data from the server", when connecting via +HTTPS to an Apache+mod_ssl server with Netscape Navigator?

+

+ This usually occurs when you have created a new server certificate for + a given domain, but had previously told your browser to always accept + the old server certificate. Once you clear the entry for the old + certificate from your browser, everything should be fine. Netscape's SSL + implementation is correct, so when you encounter I/O errors with Netscape + Navigator it is usually caused by the configured certificates.

+ +
top
+
+

mod_ssl Support

+ + +

What information resources are available in case of mod_ssl problems?

+

The following information resources are available. + In case of problems you should search here first.

+ +
+
Answers in the User Manual's F.A.Q. List (this)
+
+ http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html
+ First check the F.A.Q. (this text). If your problem is a common + one, it may have been answered several times before, and been included + in this doc. +
+
Postings from the modssl-users Support Mailing List + http://www.modssl.org/support/
+
Search for your problem in the archives of the modssl-users mailing list. + You're probably not the first person to have had this problem! +
+
+ + +

What support contacts are available in case +of mod_ssl problems?

+

The following lists all support possibilities for mod_ssl, in order of + preference. Please go through these possibilities + in this order - don't just pick the one you like the look of.

+
    +
  1. Send a Problem Report to the modssl-users Support Mailing List
    + + modssl-users@modssl.org
    + This is the preferred way of submitting your problem report, because this way, + others can see the problem, and learn from any answers. You must subscribe to + the list first, but you can then easily discuss your problem with both the + author and the whole mod_ssl user community. +
    2. + +
  2. Send a Problem Report to the Apache httpd Users Support Mailing List
    + + users@httpd.apache.org
    + This is the second way of submitting your problem report. Again, you must + subscribe to the list first, but you can then easily discuss your problem + with the whole Apache httpd user community. +
    3. + +
  3. Write a Problem Report in the Bug Database
    + + http://httpd.apache.org/bug_report.html
    + This is the last way of submitting your problem report. You should only + do this if you've already posted to the mailing lists, and had no success. + Please follow the instructions on the above page carefully. +
    4. +
+ + +

What information should I +provide when writing a bug report?

+

You should always provide at least the following information:

+ +
+
Apache and OpenSSL version information
+
The Apache version can be determined + by running httpd -v. The OpenSSL version can be + determined by running openssl version. Alternatively, if + you have Lynx installed, you can run the command lynx -mime_header + http://localhost/ | grep Server to gather this information in a + single step. +
+ +
The details on how you built and installed Apache+mod_ssl+OpenSSL
+
For this you can provide a logfile of your terminal session which shows + the configuration and install steps. If this is not possible, you + should at least provide the configure command line you used. +
+ +
In case of core dumps please include a Backtrace
+
If your Apache+mod_ssl+OpenSSL dumps its core, please attach + a stack-frame ``backtrace'' (see below + for information on how to get this). Without this information, the + reason for your core dump cannot be found +
+ +
A detailed description of your problem
+
Don't laugh, we really mean it! Many problem reports don't + include a description of what the actual problem is. Without this, + it's very difficult for anyone to help you. So, it's in your own + interest (you want the problem be solved, don't you?) to include as + much detail as possible, please. Of course, you should still include + all the essentials above too. +
+
+ + +

I had a core dump, can you help me?

+

In general no, at least not unless you provide more details about the code + location where Apache dumped core. What is usually always required in + order to help you is a backtrace (see next question). Without this + information it is mostly impossible to find the problem and help you in + fixing it.

+ + +

How do I get a backtrace, to help find +the reason for my core dump?

+

Following are the steps you will need to complete, to get a backtrace:

+
    +
  1. Make sure you have debugging symbols available, at least + in Apache. On platforms where you use GCC/GDB, you will have to build + Apache+mod_ssl with ``OPTIM="-g -ggdb3"'' to get this. On + other platforms at least ``OPTIM="-g"'' is needed. +
    2. + +
  2. Start the server and try to reproduce the core-dump. For this you may + want to use a directive like ``CoreDumpDirectory /tmp'' to + make sure that the core-dump file can be written. This should result + in a /tmp/core or /tmp/httpd.core file. If you + don't get one of these, try running your server under a non-root UID. + Many modern kernels do not allow a process to dump core after it has + done a setuid() (unless it does an exec()) for + security reasons (there can be privileged information left over in + memory). If necessary, you can run /path/to/httpd -X + manually to force Apache to not fork. +
    3. + +
  3. Analyze the core-dump. For this, run gdb /path/to/httpd + /tmp/httpd.core or a similar command. In GDB, all you + have to do then is to enter bt, and voila, you get the + backtrace. For other debuggers consult your local debugger manual. +
    4. +
+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/ssl/ssl_howto.html b/docs/manual/ssl/ssl_howto.html new file mode 100644 index 00000000..ca42f094 --- /dev/null +++ b/docs/manual/ssl/ssl_howto.html @@ -0,0 +1,3 @@ +URI: ssl_howto.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 diff --git a/docs/manual/ssl/ssl_howto.html.en b/docs/manual/ssl/ssl_howto.html.en new file mode 100644 index 00000000..8c514409 --- /dev/null +++ b/docs/manual/ssl/ssl_howto.html.en @@ -0,0 +1,294 @@ + + + +SSL/TLS Strong Encryption: How-To - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > SSL/TLS

SSL/TLS Strong Encryption: How-To

+
+

Available Languages:  en 

+
+ +
+

The solution to this problem is trivial +and is left as an exercise for the reader.

+ +

-- Standard textbook cookie

+
+ +

How to solve particular security problems for an SSL-aware +webserver is not always obvious because of the interactions between SSL, +HTTP and Apache's way of processing requests. This chapter gives +instructions on how to solve some typical situations. Treat it as a first +step to find out the final solution, but always try to understand the +stuff before you use it. Nothing is worse than using a security solution +without knowing its restrictions and how it interacts with other systems.

+
+ +
top
+
+

Cipher Suites and Enforcing Strong Security

+ + + +

How can I create a real SSLv2-only server?

+ +

The following creates an SSL server which speaks only the SSLv2 protocol and + its ciphers.

+ +

httpd.conf

+ SSLProtocol -all +SSLv2
+ SSLCipherSuite SSLv2:+HIGH:+MEDIUM:+LOW:+EXP
+

+ + +

How can I create an SSL server which accepts strong encryption +only?

+ +

The following enables only the seven strongest ciphers:

+

httpd.conf

+ SSLProtocol all
+ SSLCipherSuite HIGH:MEDIUM
+

+ + +

How can I create an SSL server which accepts strong encryption +only, but allows export browsers to upgrade to stronger encryption?

+ +

This facility is called Server Gated Cryptography (SGC) and requires + a Global ID server certificate, signed by a special CA certificate + from Verisign. This enables strong encryption in 'export' versions of + browsers, which traditionally could not support it (because of US export + restrictions).

+

When a browser connects with an export cipher, the server sends its Global + ID certificate. The browser verifies this, and can then upgrade its + cipher suite before any HTTP communication takes place. The problem + lies in allowing browsers to upgrade in this fashion, but still requiring + strong encryption. In other words, we want browsers to either start a + connection with strong encryption, or to start with export ciphers but + upgrade to strong encryption before beginning HTTP communication.

+

This can be done as follows:

+

httpd.conf

+ # allow all ciphers for the initial handshake,
+ # so export browsers can upgrade via SGC facility
+ SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
+
+ <Directory /usr/local/apache2/htdocs>
+ # but finally deny all browsers which haven't upgraded
+ SSLRequire %{SSL_CIPHER_USEKEYSIZE} >= 128
+ </Directory> +

+ + +

How can I create an SSL server which accepts all types of ciphers +in general, but requires a strong ciphers for access to a particular +URL?

+ +

Obviously, a server-wide SSLCipherSuite which restricts + ciphers to the strong variants, isn't the answer here. However, + mod_ssl can be reconfigured within Location + blocks, to give a per-directory solution, and can automatically force + a renegotiation of the SSL parameters to meet the new configuration. + This can be done as follows:

+

+ # be liberal in general
+ SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
+
+ <Location /strong/area>
+ # but https://hostname/strong/area/ and below
+ # requires strong ciphers
+ SSLCipherSuite HIGH:MEDIUM
+ </Location> +

+ +
top
+
+

Client Authentication and Access Control

+ + + +

How can I force clients to authenticate using certificates?

+ + +

When you know all of your users (eg, as is often the case on a corporate + Intranet), you can require plain certificate authentication. All you + need to do is to create client certificates signed by your own CA + certificate (ca.crt) and then verify the clients against this + certificate.

+

httpd.conf

+ # require a client certificate which has to be directly
+ # signed by our CA certificate in ca.crt
+ SSLVerifyClient require
+ SSLVerifyDepth 1
+ SSLCACertificateFile conf/ssl.crt/ca.crt +

+ + +

How can I force clients to authenticate using certificates for a + particular URL, but still allow arbitrary clients to access the rest of the server?

+ + +

To force clients to authenticate using certificates for a particular URL, + you can use the per-directory reconfiguration features of mod_ssl:

+ +

httpd.conf

+ SSLVerifyClient none
+ SSLCACertificateFile conf/ssl.crt/ca.crt
+
+ <Location /secure/area>
+ SSLVerifyClient require
+ SSLVerifyDepth 1
+ </Location>
+

+ + +

How can I allow only clients who have certificates to access a + particular URL, but allow all clients to access the rest of the server?

+ + +

The key to doing this is checking that part of the client certificate + matches what you expect. Usually this means checking all or part of the + Distinguished Name (DN), to see if it contains some known string. + There are two ways to do this, using either mod_auth_basic or + SSLRequire.

+ +

The mod_auth_basic method is generally required when + the certificates are completely arbitrary, or when their DNs have + no common fields (usually the organisation, etc.). In this case, + you should establish a password database containing all + clients allowed, as follows:

+ +

httpd.conf

+SSLVerifyClient      none
+<Directory /usr/local/apache2/htdocs/secure/area>
+
+SSLVerifyClient      require
+SSLVerifyDepth       5
+SSLCACertificateFile conf/ssl.crt/ca.crt
+SSLCACertificatePath conf/ssl.crt
+SSLOptions           +FakeBasicAuth
+SSLRequireSSL
+AuthName             "Snake Oil Authentication"
+AuthType             Basic
+AuthBasicProvider    file
+AuthUserFile         /usr/local/apache2/conf/httpd.passwd
+require              valid-user
+</Directory>
+ +

httpd.passwd

+/C=DE/L=Munich/O=Snake Oil, Ltd./OU=Staff/CN=Foo:xxj31ZMTZzkVA
+/C=US/L=S.F./O=Snake Oil, Ltd./OU=CA/CN=Bar:xxj31ZMTZzkVA
+/C=US/L=L.A./O=Snake Oil, Ltd./OU=Dev/CN=Quux:xxj31ZMTZzkVA
+ +

When your clients are all part of a common hierarchy, which is encoded + into the DN, you can match them more easily using SSLRequire, as follows:

+ + +

httpd.conf

+SSLVerifyClient      none
+<Directory /usr/local/apache2/htdocs/secure/area>
+
+  SSLVerifyClient      require
+  SSLVerifyDepth       5
+  SSLCACertificateFile conf/ssl.crt/ca.crt
+  SSLCACertificatePath conf/ssl.crt
+  SSLOptions           +FakeBasicAuth
+  SSLRequireSSL
+  SSLRequire       %{SSL_CLIENT_S_DN_O}  eq "Snake Oil, Ltd." \
+               and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"}
+</Directory>
+ + +

How can I require HTTPS with strong ciphers, and either basic +authentication or client certificates, for access to part of the +Intranet website, for clients coming from the Internet? I still want to allow +plain HTTP access for clients on the Intranet.

+ + +

These examples presume that clients on the Intranet have IPs in the range + 192.160.1.0/24, and that the part of the Intranet website you want to allow + internet access to is /usr/local/apache2/htdocs/subarea. + This configuration should remain outside of your HTTPS virtual host, so + that it applies to both HTTPS and HTTP.

+ +

httpd.conf

+SSLCACertificateFile conf/ssl.crt/company-ca.crt
+
+<Directory /usr/local/apache2/htdocs>
+#   Outside the subarea only Intranet access is granted
+Order                deny,allow
+Deny                 from all
+Allow                from 192.168.1.0/24
+</Directory>
+
+<Directory /usr/local/apache2/htdocs/subarea>
+#   Inside the subarea any Intranet access is allowed
+#   but from the Internet only HTTPS + Strong-Cipher + Password
+#   or the alternative HTTPS + Strong-Cipher + Client-Certificate
+
+#   If HTTPS is used, make sure a strong cipher is used.
+#   Additionally allow client certs as alternative to basic auth.
+SSLVerifyClient      optional
+SSLVerifyDepth       1
+SSLOptions           +FakeBasicAuth +StrictRequire
+SSLRequire           %{SSL_CIPHER_USEKEYSIZE} >= 128
+
+#   Force clients from the Internet to use HTTPS
+RewriteEngine        on
+RewriteCond          %{REMOTE_ADDR} !^192\.168\.1\.[0-9]+$
+RewriteCond          %{HTTPS} !=on
+RewriteRule          .* - [F]
+
+#   Allow Network Access and/or Basic Auth
+Satisfy              any
+
+#   Network Access Control
+Order                deny,allow
+Deny                 from all
+Allow                192.168.1.0/24
+
+#   HTTP Basic Authentication
+AuthType             basic
+AuthName             "Protected Intranet Area"
+AuthBasicProvider    file
+AuthUserFile         conf/protected.passwd
+Require              valid-user
+</Directory>
+ +
+
+

Available Languages:  en 

+
+ \ No newline at end of file diff --git a/docs/manual/ssl/ssl_intro.html b/docs/manual/ssl/ssl_intro.html new file mode 100644 index 00000000..263c0f21 --- /dev/null +++ b/docs/manual/ssl/ssl_intro.html @@ -0,0 +1,7 @@ +URI: ssl_intro.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: ssl_intro.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP diff --git a/docs/manual/ssl/ssl_intro.html.en b/docs/manual/ssl/ssl_intro.html.en new file mode 100644 index 00000000..85d047bd --- /dev/null +++ b/docs/manual/ssl/ssl_intro.html.en @@ -0,0 +1,650 @@ + + + +SSL/TLS Strong Encryption: An Introduction - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2 > SSL/TLS

SSL/TLS Strong Encryption: An Introduction

+
+

Available Languages:  en  | + ja 

+
+ +
+

The nice thing about standards is that there are so many to choose +from. And if you really don't like all the standards you just have to +wait another year until the one arises you are looking for.

+ +

-- A. Tanenbaum, "Introduction to +Computer Networks"

+
+ +

As an introduction this chapter is aimed at readers who are familiar +with the Web, HTTP, and Apache, but are not security experts. It is not +intended to be a definitive guide to the SSL protocol, nor does it discuss +specific techniques for managing certificates in an organization, or the +important legal issues of patents and import and export restrictions. +Rather, it is intended to provide a common background to mod_ssl users by pulling together various concepts, definitions, +and examples as a starting point for further exploration.

+ +

The presented content is mainly derived, with the author's permission, +from the article Introducing +SSL and Certificates using SSLeay by Frederick J. Hirsch, of The +Open Group Research Institute, which was published in Web Security: A Matter of +Trust, World Wide Web Journal, Volume 2, Issue 3, Summer 1997. +Please send any positive feedback to Frederick Hirsch (the original +article author) and all negative feedback to Ralf S. Engelschall (the +mod_ssl author).

+
+ +
top
+
+

Cryptographic Techniques

+ +

Understanding SSL requires an understanding of cryptographic +algorithms, message digest functions (aka. one-way or hash functions), and +digital signatures. These techniques are the subject of entire books (see +for instance [AC96]) and provide the basis for privacy, +integrity, and authentication.

+ +

Cryptographic Algorithms

+ +

Suppose Alice wants to send a message to her bank to transfer some + money. Alice would like the message to be private, since it will + include information such as her account number and transfer amount. One + solution is to use a cryptographic algorithm, a technique that would + transform her message into an encrypted form, unreadable until it is + decrypted. Once in this form, the message can only be + decrypted by using a secret key. Without the key the message is useless: + good cryptographic algorithms make it so difficult + for intruders to decode the original text that it isn't worth their + effort.

+ +

There are two categories of cryptographic algorithms: conventional + and public key.

+ +
+
Conventional cryptography
+
also known as symmetric cryptography, requires the sender and + receiver to share a key: a secret piece of information that may be + used to encrypt or decrypt a message. As long as this key is kept + secret, nobody other than the sender or recipient can read the message. + If Alice and the bank know a secret key, then they can send each other + private messages. The task of sharing a key between sender and recipient + before communicating, while also keeping it secret from others, can be + problematic.
+ +
Public key cryptography
+
also known as asymmetric cryptography, solves the key exchange + problem by defining an algorithm which uses two keys, each of which + may be used to encrypt a message. If one key is used to encrypt a + message then the other must be used to decrypt it. This makes it + possible to receive secure messages by simply publishing one key + (the public key) and keeping the other secret (the private key).
+
+ +

Anyone can encrypt a message using the public key, but only the + owner of the private key will be able to read it. In this way, Alice + can send private messages to the owner of a key-pair (the bank), by + encrypting it using their public key. Only the bank will be able to + decrypt it.

+ + +

Message Digests

+ +

Although Alice may encrypt her message to make it private, there + is still a concern that someone might modify her original message or + substitute it with a different one, in order to transfer the money + to themselves, for instance. One way of guaranteeing the integrity + of Alice's message is for her to create a concise summary of her + message and send this to the bank as well. Upon receipt of the message, + the bank creates its own summary and compares it with the one Alice + sent. If the summaries are the same then the message has been received + intact.

+ +

A summary such as this is called a message digest, one-way + function or hash function. Message digests are used to create + a short, fixed-length representation of a longer, variable-length message. + Digest algorithms are designed to produce a unique digests for each + message. Message digests are designed to make it impractically difficult + to determine the message from the digest, and (in theory) impossible to + find two different messages which create the same digest -- thus + eliminating the possibility of substituting one message for another while + maintaining the same digest.

+ +

Another challenge that Alice faces is finding a way to send the digest + to the bank securely; if the digest is not sent securely, its integrity may + be compromised, and with it, the possibility for the bank to determine the + integrity of the original message. Only if the digest is sent securely can + the integrity of the associated message be determined.

+ +

One way to send the digest securely is to include it in a digital + signature.

+ + +

Digital Signatures

+

When Alice sends a message to the bank, the bank needs to ensure that the +message is really from her, so an intruder cannot request a transaction +involving her account. A digital signature, created by Alice and +included with the message, serves this purpose.

+ +

Digital signatures are created by encrypting a digest of the message, +and other information (such as a sequence number) with the sender's +private key. Though anyone can decrypt the signature using the public +key, only the sender knows the private key. This means that only they can +have signed it. Including the digest in the signature means the signature is +only good for that message; it also ensures the integrity of the message since +no one can change the digest and still sign it.

+

To guard against interception and reuse of the signature by an intruder at a +later date, the signature contains a unique sequence number. This protects +the bank from a fraudulent claim from Alice that she did not send the message +-- only she could have signed it (non-repudiation).

+ +
top
+
+

Certificates

+ +

Although Alice could have sent a private message to the bank, signed +it, and ensured the integrity of the message, she still needs to be sure +that she is really communicating with the bank. This means that she needs +to be sure that the public key she is using is part of the bank's key-pair, +and not an intruder's. Similarly, the bank needs to verify that the message +signature really was signed by the private key that belongs to Alice.

+ +

If each party has a certificate which validates the other's identity, +confirms the public key, and is signed by a trusted agency, then both +can be assured that they are communicating with whom they think they are. +Such a trusted agency is called a Certificate Authority, and +certificates are used for authentication.

+ +

Certificate Contents

+ +

A certificate associates a public key with the real identity of + an individual, server, or other entity, known as the subject. As + shown in Table 1, information about the subject + includes identifying information (the distinguished name), and the + public key. It also includes the identification and signature of the + Certificate Authority that issued the certificate, and the period of + time during which the certificate is valid. It may have additional + information (or extensions) as well as administrative information + for the Certificate Authority's use, such as a serial number.

+ +

Table 1: Certificate Information

+ + + + + + + + + + + + + +
SubjectDistinguished Name, Public Key
IssuerDistinguished Name, Signature
Period of ValidityNot Before Date, Not After Date
Administrative InformationVersion, Serial Number
Extended InformationBasic Constraints, Netscape Flags, etc.
+ + +

A distinguished name is used to provide an identity in a specific + context -- for instance, an individual might have a personal + certificate as well as one for their identity as an employee. + Distinguished names are defined by the X.509 standard [X509], which defines the fields, field names, and + abbreviations used to refer to the fields (see Table + 2).

+ +

Table 2: Distinguished Name Information

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
DN FieldAbbrev.DescriptionExample
Common NameCNName being certifiedCN=Joe Average
Organization or CompanyOName is associated with this
organization		O=Snake Oil, Ltd.
Organizational UnitOUName is associated with this
organization unit, such + as a department		OU=Research Institute
City/LocalityLName is located in this CityL=Snake City
State/ProvinceSTName is located in this State/ProvinceST=Desert
CountryCName is located in this Country (ISO code)C=XZ
+ + +

A Certificate Authority may define a policy specifying which + distinguished field names are optional, and which are required. It + may also place requirements upon the field contents, as may users of + certificates. For example, a Netscape browser requires that the + Common Name for a certificate representing a server matches a wildcard + pattern for the domain name of that server, such + as *.snakeoil.com.

+ +

The binary format of a certificate is defined using the ASN.1 + notation [X208] [PKCS]. This + notation defines how to specify the contents, and encoding rules + define how this information is translated into binary form. The binary + encoding of the certificate is defined using Distinguished Encoding + Rules (DER), which are based on the more general Basic Encoding Rules + (BER). For those transmissions which cannot handle binary, the binary + form may be translated into an ASCII form by using Base64 encoding + [MIME]. When placed between begin and end delimiter + lines (as below), this encoded version is called a PEM ("Privacy Enhanced + Mail") encoded certificate.

+ +

Example of a PEM-encoded certificate (snakeoil.crt)

-----BEGIN CERTIFICATE-----
+MIIC7jCCAlegAwIBAgIBATANBgkqhkiG9w0BAQQFADCBqTELMAkGA1UEBhMCWFkx
+FTATBgNVBAgTDFNuYWtlIERlc2VydDETMBEGA1UEBxMKU25ha2UgVG93bjEXMBUG
+A1UEChMOU25ha2UgT2lsLCBMdGQxHjAcBgNVBAsTFUNlcnRpZmljYXRlIEF1dGhv
+cml0eTEVMBMGA1UEAxMMU25ha2UgT2lsIENBMR4wHAYJKoZIhvcNAQkBFg9jYUBz
+bmFrZW9pbC5kb20wHhcNOTgxMDIxMDg1ODM2WhcNOTkxMDIxMDg1ODM2WjCBpzEL
+MAkGA1UEBhMCWFkxFTATBgNVBAgTDFNuYWtlIERlc2VydDETMBEGA1UEBxMKU25h
+a2UgVG93bjEXMBUGA1UEChMOU25ha2UgT2lsLCBMdGQxFzAVBgNVBAsTDldlYnNl
+cnZlciBUZWFtMRkwFwYDVQQDExB3d3cuc25ha2VvaWwuZG9tMR8wHQYJKoZIhvcN
+AQkBFhB3d3dAc25ha2VvaWwuZG9tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKB
+gQDH9Ge/s2zcH+da+rPTx/DPRp3xGjHZ4GG6pCmvADIEtBtKBFAcZ64n+Dy7Np8b
+vKR+yy5DGQiijsH1D/j8HlGE+q4TZ8OFk7BNBFazHxFbYI4OKMiCxdKzdif1yfaa
+lWoANFlAzlSdbxeGVHoT0K+gT5w3UxwZKv2DLbCTzLZyPwIDAQABoyYwJDAPBgNV
+HRMECDAGAQH/AgEAMBEGCWCGSAGG+EIBAQQEAwIAQDANBgkqhkiG9w0BAQQFAAOB
+gQAZUIHAL4D09oE6Lv2k56Gp38OBDuILvwLg1v1KL8mQR+KFjghCrtpqaztZqcDt
+2q2QoyulCgSzHbEGmi0EsdkPfg6mp0penssIFePYNI+/8u9HT4LuKMJX15hxBam7
+dUHzICxBVC1lnHyYGjDuAMhe396lYAn8bCld1/L4NMGBCQ==
+-----END CERTIFICATE-----
+ + +

Certificate Authorities

+ +

By verifying the information in a certificate request + before granting the certificate, the Certificate Authority assures + itself of the identity of the private key owner of a key-pair. + For instance, if Alice requests a personal certificate, the + Certificate Authority must first make sure that Alice really is the + person the certificate claims she is.

+ +

Certificate Chains

+ +

A Certificate Authority may also issue a certificate for + another Certificate Authority. When examining a certificate, + Alice may need to examine the certificate of the issuer, for each + parent Certificate Authority, until reaching one which she has + confidence in. She may decide to trust only certificates with a + limited chain of issuers, to reduce her risk of a "bad" certificate + in the chain.

+ + +

Creating a Root-Level CA

+ +

As noted earlier, each certificate requires an issuer to assert + the validity of the identity of the certificate subject, up to + the top-level Certificate Authority (CA). This presents a problem: + who can vouch for the certificate of the top-level + authority, which has no issuer? In this unique case, the + certificate is "self-signed", so the issuer of the certificate is + the same as the subject. Browsers are preconfigured to trust well-known + certificate authorities, but it is important to exercise extra care in + trusting a self-signed certificate. The wide publication of a + public key by the root authority reduces the risk in trusting this + key -- it would be obvious if someone else publicized a key + claiming to be the authority.

+ +

A number of companies, such as Thawte and VeriSign + have established themselves as Certificate Authorities. These + companies provide the following services:

+ +
    +
  • Verifying certificate requests
    • +
  • Processing certificate requests
    • +
  • Issuing and managing certificates
    • +
+ +

It is also possible to create your own Certificate Authority. + Although risky in the Internet environment, it may be useful + within an Intranet where the organization can easily verify the + identities of individuals and servers.

+ + +

Certificate Management

+ +

Establishing a Certificate Authority is a responsibility which + requires a solid administrative, technical, and management + framework. Certificate Authorities not only issue certificates, + they also manage them -- that is, they determine for how long + certificates remain valid, they renew them, and they keep lists of + certificates that were issued in the past but are no longer valid + (Certificate Revocation Lists, or CRLs).

+ +

For example, if Alice is entitled to a certificate as an + employee of a company, but has now left + that company, her certificate may need to be revoked. + Because certificates are only issued after the subject's identity has + been verified, and can then be passed around to all those with whom + the subject may communicate, it is impossible to tell from the + certificate alone that it has been revoked. + When examining certificates for validity, therefore, + it is necessary to contact the issuing Certificate Authority to + check CRLs -- this is usually not an automated part of the process.

+ +

Note

+

If you use a Certificate Authority that browsers are not configured + to trust by default, it is necessary to load the Certificate + Authority certificate into the browser, enabling the browser to + validate server certificates signed by that Certificate Authority. + Doing so may be dangerous, since once loaded, the browser will + accept all certificates signed by that Certificate Authority.

+
+ + + +
top
+
+

Secure Sockets Layer (SSL)

+ +

The Secure Sockets Layer protocol is a protocol layer which may be +placed between a reliable connection-oriented network layer protocol +(e.g. TCP/IP) and the application protocol layer (e.g. HTTP). SSL provides +for secure communication between client and server by allowing mutual +authentication, the use of digital signatures for integrity, and encryption +for privacy.

+ +

The protocol is designed to support a range of choices for specific +algorithms used for cryptography, digests, and signatures. This allows +algorithm selection for specific servers to be made based on legal, export +or other concerns, and also enables the protocol to take advantage of new +algorithms. Choices are negotiated between client and server at the start +of establishing a protocol session.

+ +

Table 4: Versions of the SSL protocol

+ + + + + + + + + + + + + + + + + + + +
VersionSourceDescriptionBrowser Support
SSL v2.0Vendor Standard (from Netscape Corp.) [SSL2]First SSL protocol for which implementations exists- NS Navigator 1.x/2.x
+ - MS IE 3.x
+ - Lynx/2.8+OpenSSL
SSL v3.0Expired Internet Draft (from Netscape Corp.) [SSL3]Revisions to prevent specific security attacks, add non-RSA + ciphers, and support for certificate chains- NS Navigator 2.x/3.x/4.x
+ - MS IE 3.x/4.x
+ - Lynx/2.8+OpenSSL
TLS v1.0Proposed Internet Standard (from IETF) [TLS1]Revision of SSL 3.0 to update the MAC layer to HMAC, add block + padding for block ciphers, message order standardization and more + alert messages.- Lynx/2.8+OpenSSL
+ + +

There are a number of versions of the SSL protocol, as shown in +Table 4. As noted there, one of the benefits in +SSL 3.0 is that it adds support of certificate chain loading. This feature +allows a server to pass a server certificate along with issuer certificates +to the browser. Chain loading also permits the browser to validate the +server certificate, even if Certificate Authority certificates are not +installed for the intermediate issuers, since they are included in the +certificate chain. SSL 3.0 is the basis for the Transport Layer Security +[TLS] protocol standard, currently in development by +the Internet Engineering Task Force (IETF).

+ +

Establishing a Session

+ +

The SSL session is established by following a handshake sequence + between client and server, as shown in Figure 1. This sequence may vary, depending on whether the server + is configured to provide a server certificate or request a client + certificate. Although cases exist where additional handshake steps + are required for management of cipher information, this article + summarizes one common scenario. See the SSL specification for the full + range of possibilities.

+ +

Note

+

Once an SSL session has been established, it may be reused. This + avoids the performance penalty of repeating the many steps needed + to start a session. To do this, the server assigns each SSL session a + unique session identifier which is cached in the server and which the + client can use in future connections to reduce the handshake time + (until the session identifer expires from the cache of the server).

+
+ +

+
+ Figure 1: Simplified SSL + Handshake Sequence

+ +

The elements of the handshake sequence, as used by the client and + server, are listed below:

+ +
    +
  1. Negotiate the Cipher Suite to be used during data transfer
    2. +
  2. Establish and share a session key between client and server
    3. +
  3. Optionally authenticate the server to the client
    4. +
  4. Optionally authenticate the client to the server
    5. +
+ +

The first step, Cipher Suite Negotiation, allows the client and + server to choose a Cipher Suite supported by both of them. The SSL3.0 + protocol specification defines 31 Cipher Suites. A Cipher Suite is + defined by the following components:

+ +
    +
  • Key Exchange Method
    • +
  • Cipher for Data Transfer
    • +
  • Message Digest for creating the Message Authentication Code (MAC)
    • +
+ +

These three elements are described in the sections that follow.

+ + +

Key Exchange Method

+ +

The key exchange method defines how the shared secret symmetric + cryptography key used for application data transfer will be agreed + upon by client and server. SSL 2.0 uses RSA key exchange only, while + SSL 3.0 supports a choice of key exchange algorithms including + RSA key exchange (when certificates are used), and Diffie-Hellman key + exchange (for exchanging keys without certificates, or without prior + communication between client and server).

+ +

One variable in the choice of key exchange methods is digital + signatures -- whether or not to use them, and if so, what kind of + signatures to use. Signing with a private key provides protection + against a man-in-the-middle-attack during the information exchange + used to generating the shared key [AC96, p516].

+ + +

Cipher for Data Transfer

+ +

SSL uses conventional symmetric cryptography, as described earlier, + for encrypting messages in a session. + There are nine choices of how to encrypt, including the option not to + encrypt:

+ +
    +
  • No encryption
    • +
  • Stream Ciphers +
      +
    • RC4 with 40-bit keys
      • +
    • RC4 with 128-bit keys
      • +
    • +
  • CBC Block Ciphers +
    • RC2 with 40 bit key
      • +
    • DES with 40 bit key
      • +
    • DES with 56 bit key
      • +
    • Triple-DES with 168 bit key
      • +
    • Idea (128 bit key)
      • +
    • Fortezza (96 bit key)
      • +
    • +
+ +

"CBC" refers to Cipher Block Chaining, which means that a + portion of the previously encrypted cipher text is used in the + encryption of the current block. "DES" refers to the Data Encryption + Standard [AC96, ch12], which has a number of + variants (including DES40 and 3DES_EDE). "Idea" is currently one of + the best and cryptographically strongest algorithms available, + and "RC2" is a proprietary algorithm from RSA DSI [AC96, ch13].

+ + +

Digest Function

+ +

The choice of digest function determines how a digest is created + from a record unit. SSL supports the following:

+ +
    +
  • No digest (Null choice)
    • +
  • MD5, a 128-bit hash
    • +
  • Secure Hash Algorithm (SHA-1), a 160-bit hash
    • +
+ +

The message digest is used to create a Message Authentication Code + (MAC) which is encrypted with the message to verify integrity and to + protect against replay attacks.

+ + +

Handshake Sequence Protocol

+ +

The handshake sequence uses three protocols:

+ +
    +
  • The SSL Handshake Protocol + for performing the client and server SSL session establishment.
    • +
  • The SSL Change Cipher Spec Protocol for actually + establishing agreement on the Cipher Suite for the session.
    • +
  • The SSL Alert Protocol for conveying SSL error + messages between client and server.
    • +
+ +

These protocols, as well as application protocol data, are + encapsulated in the SSL Record Protocol, as shown in + Figure 2. An encapsulated protocol is + transferred as data by the lower layer protocol, which does not + examine the data. The encapsulated protocol has no knowledge of the + underlying protocol.

+ +

+
+ Figure 2: SSL Protocol Stack +

+ +

The encapsulation of SSL control protocols by the record protocol + means that if an active session is renegotiated the control protocols + will be transmitted securely. If there was no previous session, + the Null cipher suite is used, which means there will be no encryption and + messages will have no integrity digests, until the session has been + established.

+ + +

Data Transfer

+ +

The SSL Record Protocol, shown in Figure 3, + is used to transfer application and SSL Control data between the + client and server, where necessary fragmenting this data into smaller units, + or combining multiple higher level protocol data messages into single + units. It may compress, attach digest signatures, and encrypt these + units before transmitting them using the underlying reliable transport + protocol (Note: currently, no major SSL implementations include support + for compression).

+ +

+
+ Figure 3: SSL Record Protocol +

+ + +

Securing HTTP Communication

+ +

One common use of SSL is to secure Web HTTP communication between + a browser and a webserver. This does not preclude the use of + non-secured HTTP - the secure version (called HTTPS) is the same as + plain HTTP over SSL, but uses the URL scheme https + rather than http, and a different server port (by default, + port 443). This functionality is a large part of what mod_ssl provides for the Apache webserver.

+ +
top
+
+

References

+ +
+
[AC96]
+
Bruce Schneier, Applied Cryptography, 2nd Edition, Wiley, +1996. See http://www.counterpane.com/ for various other materials by Bruce +Schneier.
+ +
[X208]
+
ITU-T Recommendation X.208, Specification of Abstract Syntax Notation +One (ASN.1), 1988. See for instance http://www.itu.int/rec/recommendation.asp?type=items&lang=e&parent=T-REC-X.208-198811-I. +
+ +
[X509]
+
ITU-T Recommendation X.509, The Directory - Authentication +Framework. See for instance http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-X.509. +
+ +
[PKCS]
+
Public Key Cryptography Standards (PKCS), +RSA Laboratories Technical Notes, See http://www.rsasecurity.com/rsalabs/pkcs/.
+ +
[MIME]
+
N. Freed, N. Borenstein, Multipurpose Internet Mail Extensions +(MIME) Part One: Format of Internet Message Bodies, RFC2045. +See for instance http://ietf.org/rfc/rfc2045.txt.
+ +
[SSL2]
+
Kipp E.B. Hickman, The SSL Protocol, 1995. See http://www.netscape.com/eng/security/SSL_2.html.
+ +
[SSL3]
+
Alan O. Freier, Philip Karlton, Paul C. Kocher, The SSL Protocol +Version 3.0, 1996. See http://www.netscape.com/eng/ssl3/draft302.txt.
+ +
[TLS1]
+
Tim Dierks, Christopher Allen, The TLS Protocol Version 1.0, +1999. See http://ietf.org/rfc/rfc2246.txt.
+
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/ssl/ssl_intro.html.ja.euc-jp b/docs/manual/ssl/ssl_intro.html.ja.euc-jp new file mode 100644 index 00000000..285ea4c8 --- /dev/null +++ b/docs/manual/ssl/ssl_intro.html.ja.euc-jp @@ -0,0 +1,697 @@ + + + +SSL/TLS °Å¹æ²½: ¤Ï¤¸¤á¤Ë - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2 > SSL/TLS

SSL/TLS °Å¹æ²½: ¤Ï¤¸¤á¤Ë

+
+

Available Languages:  en  | + ja 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +
+

ɸ½àµ¬³Ê¤ÎÎɤ¤½ê¤Ï¡¢¤¿¤¯¤µ¤ó¤Îµ¬³Ê¤«¤éÁª¤Ù¤ë¤È¤¤¤¦¤³¤È¤À¡£ +¤½¤·¤Æ¡¢¤â¤·ËÜÅö¤Ë¤É¤Îµ¬³Ê¤âµ¤¤ËÆþ¤é¤Ê¤±¤ì¤Ð¡¢ +°ìǯÂԤĤÀ¤±¤Çõ¤·¤Æ¤¤¤¿µ¬³Ê¤¬¸½¤ì¤ë¡£

+ +

-- A. Tanenbaum, "Introduction to +Computer Networks"

+
+ +

+ÆþÌç¤È¤¤¤¦¤³¤È¤Ç¡¢¤³¤Î¾Ï¤Ï Web¡¢HTTP¡¢Apache ¤ËÄ̤¸¤Æ¤¤¤ë +ÆɼԸþ¤±¤Ç¤¹¤¬¡¢¥»¥­¥å¥ê¥Æ¥£ÀìÌç²È¸þ¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ +SSL ¥×¥í¥È¥³¥ë¤Î·èÄêŪ¤Ê¼ê°ú¤­¤Ç¤¢¤ë¤Ä¤â¤ê¤Ï¤¢¤ê¤Þ¤»¤ó¡£ +¤Þ¤¿¡¢ÁÈ¿¥Æâ¤Îǧ¾Ú´ÉÍý¤Î¤¿¤á¤ÎÆÃÄê¤Î¥Æ¥¯¥Ë¥Ã¥¯¤ä¡¢ +Æõö¤äÍ¢½Ðµ¬À©¤Ê¤É¤Î½ÅÍפÊˡŪ¤ÊÌäÂê¤Ë¤Ä¤¤¤Æ¤â°·¤¤¤Þ¤»¤ó¡£ +¤à¤·¤í¡¢¹¹¤Ê¤ë¸¦µæ¤Ø¤Î½ÐȯÅÀ¤È¤·¤Æ¿§¡¹¤Ê³µÇ°¡¢ÄêµÁ¡¢Îã¤òʤ٤뤳¤È¤Ç + mod_ssl ¤Î¥æ¡¼¥¶¤Ë´ðÁÃÃ챤òÄ󶡤¹¤ë»ö¤òÌÜŪ¤È¤·¤Æ¤¤¤Þ¤¹¡£

+ +

¤³¤³¤Ë¼¨¤µ¤ì¤¿ÆâÍƤϼç¤Ë¡¢¸¶Ãø¼Ô¤Îµö²Ä¤Î²¼ +The Open Group Research Institute ¤Î Frederick J. Hirsch + »á¤Îµ­»ö +Introducing SSL and Certificates using SSLeay ¤ò´ð¤Ë¤·¤Æ¤¤¤Þ¤¹¡£ +»á¤Îµ­»ö¤Ï Web Security: A Matter of +Trust, World Wide Web Journal, Volume 2, Issue 3, Summer 1997 +¤Ë·ÇºÜ¤µ¤ì¤Þ¤·¤¿¡£ +¹ÎÄêŪ¤Ê°Õ¸«¤Ï Frederick Hirsch »á + (¸µµ­»ö¤ÎÃø¼Ô) ¤ØÁ´¤Æ¤Î¶ì¾ð¤Ï Ralf S. Engelschall ( +mod_ssl ¤Îºî¼Ô) ¤Ø¤ª´ê¤¤¤·¤Þ¤¹¡£ +[ÌõÃí: Ìõ¤Ë¤Ä¤¤¤Æ¤Ï +Apache ¥É¥­¥å¥á¥ó¥ÈËÝÌõ¥×¥í¥¸¥§¥¯¥È +¤Ø¤ª´ê¤¤¤·¤Þ¤¹¡£]

+
+ +
top
+
+

°Å¹æ²½µ»½Ñ

+ +

SSL ¤òÍý²ò¤¹¤ë¤Ë¤Ï¡¢°Å¹æ¥¢¥ë¥´¥ê¥º¥à¡¢ +¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È´Ø¿ô(ÊÌ̾: °ìÊý¸þ´Ø¿ô¡¢¥Ï¥Ã¥·¥å´Ø¿ô)¡¢ +ÅŻҽð̾¤Ê¤É¤Ø¤ÎÍý²ò¤¬É¬ÍפǤ¹¡£ +¤³¤ì¤é¤Îµ»½Ñ¤ÏËܤ¬´Ý¤´¤ÈɬÍפÊÂêÌÜ¤Ç +(Î㤨¤Ð [AC96] ¤ò»²¾È)¡¢ +¥×¥é¥¤¥Ð¥·¡¼¡¢¿®ÍÑ¡¢Ç§¾Ú¤Ê¤É¤Îµ»½Ñ¤Î´ðÁäȤʤäƤ¤¤Þ¤¹¡£

+ +

°Å¹æ¥¢¥ë¥´¥ê¥º¥à

+ +

Î㤨¤Ð¡¢¥¢¥ê¥¹¤¬Á÷¶â¤Î¤¿¤á¤Ë¶ä¹Ô¤Ë¥á¥Ã¥»¡¼¥¸¤òÁ÷¤ê¤¿¤¤¤È¤·¤Þ¤¹¡£ + ¸ýºÂÈÖ¹æ¤äÁ÷¶â¤Î¶â³Û¤¬´Þ¤Þ¤ì¤ë¤¿¤á¡¢ + ¥¢¥ê¥¹¤Ï¤½¤Î¥á¥Ã¥»¡¼¥¸¤òÈëÌ©¤Ë¤·¤¿¤¤¤È»×¤¤¤Þ¤¹¡£ + ²ò·èÊýË¡¤Î°ì¤Ä¤Ï°Å¹æ¥¢¥ë¥´¥ê¥º¥à¤ò»È¤Ã¤Æ¡¢¥á¥Ã¥»¡¼¥¸¤ò + Æɤޤ»¤¿¤¤¿Í°Ê³°¤ÏÆɤळ¤È¤¬¤Ç¤­¤Ê¤¤°Å¹æ²½¤µ¤ì¤¿ + ·ÁÂÖ¤ËÊѤ¨¤Æ¤·¤Þ¤¦¤³¤È¤Ç¤¹¡£ + ¤½¤Î·ÁÂ֤ˤʤë¤È¡¢ + ¥á¥Ã¥»¡¼¥¸¤ÏÈëÌ©¤Î¸°¤Ë¤è¤Ã¤Æ¤Î¤ß²ò¼á¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¸°¤Ê¤·¤Ç¤Ï¡¢¥á¥Ã¥»¡¼¥¸¤ÏÌò¤ËΩ¤Á¤Þ¤»¤ó¡£ + Îɤ¤°Å¹æ¥¢¥ë¥´¥ê¥º¥à¤Ï¡¢¿¯Æþ¼Ô¤¬¸µ¤Î¥Æ¥­¥¹¥È¤ò²òÆɤ¹¤ë¤³¤È¤ò + Èó¾ï¤ËÆñ¤·¤¯¤¹¤ë¤¿¤á¡¢ÅØÎϤ¬³ä¤Ë¹ç¤ï¤Ê¤¯¤µ¤»¤Þ¤¹¡£

+ +

°Å¹æ¥¢¥ë¥´¥ê¥º¥à¤Ë¤Ï + ½¾Íè·¿¤È¸ø³«¸°¤ÎÆó¤Ä¤Î¼ïÎब¤¢¤ê¤Þ¤¹¡£

+ +
+
½¾Íè·¿°Å¹æ
+
ÂоΰŹæ¤È¤·¤Æ¤âÃΤé¤ì¡¢ + Á÷¿®¼Ô¤È¼õ¿®¼Ô¤¬¸°¤ò¶¦Í­¤¹¤ë¤³¤È¤¬É¬ÍפǤ¹¡£ + ¸°¤È¤Ï¡¢¥á¥Ã¥»¡¼¥¸¤ò°Å¹æ²½¤·¤¿¤êÉü¹æ¤¹¤ë¤Î¤Ë»È¤ï¤ì¤ëÈëÌ© + ¤Î¾ðÊó¤Î¤³¤È¤Ç¤¹¡£ + ¤â¤·¡¢¤³¤Î¸°¤¬ÈëÌ©¤Ê¤é¡¢Á÷¿®¼Ô¤È¼õ¿®¼Ô°Ê³°¤Ïï¤â¥á¥Ã¥»¡¼¥¸¤òÆÉ + ¤à¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¡£ + ¤â¤·¤â¡¢¥¢¥ê¥¹¤È¶ä¹Ô¤¬ÈëÌ©¤Î¸°¤òÃΤäƤ¤¤ë¤Ê¤é¡¢ + Èà¤é¤Ï¤ª¸ß¤¤¤ËÈëÌ©¤Î¥á¥Ã¥»¡¼¥¸¤òÁ÷¤ë¤³¤È¤¬¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£ + ¤¿¤À¤·¡¢»öÁ°¤ËÆâÌ©¤Ë¸°¤òÁª¤Ö¤È¤¤¤¦»Å»ö¤ÏÌäÂê¤ò´Þ¤ó¤Ç¤¤¤Þ¤¹¡£
+ +
¸ø³«¸°°Å¹æ
+
ÈóÂоΰŹæ¤È¤·¤Æ¤âÃΤé¤ì¡¢ + ¥á¥Ã¥»¡¼¥¸¤ò°Å¹æ²½¤¹¤ë¤³¤È¤Î¤Ç¤­¤ëÆó¤Ä¤Î¸° + ¤ò»ÈÍѤ¹¤ë¥¢¥ë¥´¥ê¥º¥à¤òÄêµÁ¤¹¤ë¤³¤È¤Ç¸°¤Î¤ä¤ê¼è¤ê¤ÎÌäÂê¤ò²ò·è + ¤·¤Þ¤¹¡£ + ¤â¤·¡¢¤¢¤ë¸°¤¬°Å¹æ²½¤Ë»È¤ï¤ì¤¿¤Ê¤é¡¢ + ¤â¤¦ÊÒÊý¤Î¸°¤ÇÉü¹æ¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£ + ¤³¤ÎÊý¼°¤Ë¤è¤Ã¤Æ¡¢°ì¤Ä¤Î¸°¤ò¸øɽ¤·¤Æ(¸ø³«¸°)¡¢ + ¤â¤¦ÊÒÊý¤òÈëÌ©¤Ë¤·¤Æ¤ª¤¯(ÈëÌ©¸°)¤À¤±¤Ç¡¢ + °ÂÁ´¤Ê¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¼è¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
+
+ +

ï¤â¤¬°Å¹æ²½¤µ¤ì¤¿¥á¥Ã¥»¡¼¥¸¤ò¸ø³«¸°¤Ë¤è¤Ã¤Æ°Å¹æ²½ + ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢ÈëÌ©¸°¤Î»ý¤Á¼ç¤À¤±¤¬¤½¤ì¤òÆɤळ¤È¤¬ + ¤Ç¤­¤Þ¤¹¡£ + ¤³¤ÎÊýË¡¤Ç¡¢¶ä¹Ô¤Î¸ø³«¸°¤ò»È¤Ã¤Æ°Å¹æ²½¤¹¤ë¤³¤È¤Ç¡¢ + ¥¢¥ê¥¹¤ÏÈëÌ©¤Î¥á¥Ã¥»¡¼¥¸¤òÁ÷¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¶ä¹Ô¤Î¤ß¤¬Éü¹æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+ + +

¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È

+ +

¥¢¥ê¥¹¤Ï¥á¥Ã¥»¡¼¥¸¤òÈëÌ©¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢ + 狼¤¬Î㤨¤Ð¼«Ê¬¤ËÁ÷¶â¤¹¤ë¤è¤¦¤Ë¥á¥Ã¥»¡¼¥¸¤òÊѹ¹¤·¤¿¤ê¡¢ + Ê̤Τâ¤Î¤ËÃÖ¤­´¹¤¨¤Æ¤·¤Þ¤¦¤«¤â¤·¤ì¤Ê¤¤¤È¤¤¤¦ÌäÂ꤬¤¢¤ê¤Þ¤¹¡£ + ¥¢¥ê¥¹¤Î¥á¥Ã¥»¡¼¥¸¤Î¿®ÍѤòÊݾڤ¹¤ëÊýË¡¤Î°ì¤Ä¤Ï¡¢ + ¥á¥Ã¥»¡¼¥¸¤Î´Ê·é¤Ê¥À¥¤¥¸¥§¥¹¥È¤òºî¤Ã¤Æ¡¢¤½¤ì¤â¶ä¹Ô¤ËÁ÷¤ë¤È¤¤¤¦¤â¤Î¤Ç¤¹¡£ + ¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¼è¤ë¤È¶ä¹Ô¤â¥À¥¤¥¸¥§¥¹¥È¤òºîÀ®¤·¡¢ + ¥¢¥ê¥¹¤¬Á÷¤Ã¤¿¤â¤Î¤ÈÈæ¤Ù¤Þ¤¹¡£¤â¤·°ìÃפ·¤¿¤Ê¤é¡¢ + ¼õ¤±¼è¤Ã¤¿¥á¥Ã¥»¡¼¥¸¤Ï̵½ý¤À¤È¤¤¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£

+ +

¤³¤Î¤è¤¦¤ÊÍ×Ìó¤Ï¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È¡¢ + °ìÊý¹Ô´Ø¿ô¡¢¤Þ¤¿¤Ï¥Ï¥Ã¥·¥å´Ø¿ô¤È¸Æ¤Ð¤ì¤Þ¤¹¡£ + ¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È¤ÏŤ¤²ÄÊÑĹ¤Î¥á¥Ã¥»¡¼¥¸¤«¤é + û¤¤¸ÇÄêŤÎɽ¸½¤òºî¤ë¤Î¤Ë»È¤ï¤ì¤Þ¤¹¡£ + ¥À¥¤¥¸¥§¥¹¥È¥¢¥ë¥´¥ê¥º¥à¤Ï¥á¥Ã¥»¡¼¥¸¤«¤é + °ì°Õ¤Ê¥À¥¤¥¸¥§¥¹¥È¤òÀ¸À®¤¹¤ë¤è¤¦¤Ëºî¤é¤ì¤Æ¤¤¤Þ¤¹¡£ + ¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È¤Ï¥À¥¤¥¸¥§¥¹¥È¤«¤é¸µ¤Î¥á¥Ã¥»¡¼¥¸¤ò + ȽÄꤹ¤ë¤Î¤¬¤È¤Æ¤âÆñ¤·¤¤¤è¤¦¤Ë¤Ç¤­¤Æ¤¤¤Þ¤¹¡£ + ¤Þ¤¿¡¢Æ±¤¸Í×Ìó¤òºîÀ®¤¹¤ëÆó¤Ä¤Î¥á¥Ã¥»¡¼¥¸¤òõ¤¹¤Î¤ÏÉÔ²Äǽ¤Ç¤¹¡£ + ¤è¤Ã¤Æ¡¢Æ±¤¸Í×Ìó¤ò»È¤Ã¤Æ¥á¥Ã¥»¡¼¥¸¤òÃÖ¤­´¹¤¨¤ë¤È¤¤¤¦ + ²ÄǽÀ­¤òÇÓ½ü¤·¤Æ¤¤¤Þ¤¹¡£

+ +

¥¢¥ê¥¹¤Ø¤Î¤â¤¦°ì¤Ä¤ÎÌäÂê¤Ï¡¢¤³¤Î¥À¥¤¥¸¥§¥¹¥È¤ò°ÂÁ´¤ËÁ÷¤ëÊýË¡¤òõ¤¹¤³¤È¤Ç¤¹¡£ +¤³¤ì¤¬¤Ç¤­¤ì¤Ð¡¢¥á¥Ã¥»¡¼¥¸¤Î¿®ÍѤ¬Êݾڤµ¤ì¤Þ¤¹¡£ +°ì¤Ä¤ÎÊýË¡¤Ï¤³¤Î¥À¥¤¥¸¥§¥¹¥È¤ËÅŻҽð̾¤ò´Þ¤à¤³¤È¤Ç¤¹¡£

+ + +

ÅŻҽð̾

+

¥¢¥ê¥¹¤¬¶ä¹Ô¤Ë¥á¥Ã¥»¡¼¥¸¤òÁ÷¤Ã¤¿¤È¤­¡¢¶ä¹Ô¤Ï¡¢ +¿¯Æþ¼Ô¤¬Èà½÷¤Ë¤Ê¤ê¤¹¤Þ¤·¤ÆÈà½÷¤Î¸ýºÂ¤Ø¤Î¼è°ú¤ò¿½ÀÁ¤·¤Æ¤¤¤Ê¤¤¤«¡¢ +¥á¥Ã¥»¡¼¥¸¤¬ËÜÅö¤ËÈà½÷¤«¤é¤Î¤â¤Î¤«³Î¼Â¤Ëʬ¤«¤é¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£ +¥¢¥ê¥¹¤Ë¤è¤Ã¤ÆºîÀ®¤µ¤ì¡¢¥á¥Ã¥»¡¼¥¸¤Ë´Þ¤Þ¤ì¤¿ +ÅŻҽð̾¤¬¤³¤³¤ÇÌò¤ËΩ¤Á¤Þ¤¹¡£

+ +

ÅŻҽð̾¤Ï¥á¥Ã¥»¡¼¥¸¤Î¥À¥¤¥¸¥§¥¹¥È¤ä¤½¤Î¾¤Î¾ðÊó(½èÍýÈÖ¹æ¤Ê¤É)¤ò +Á÷¿®¼Ô¤ÎÈëÌ©¸°¤Ç°Å¹æ²½¤¹¤ë¤³¤È¤Çºî¤é¤ì¤Þ¤¹¡£ +ï¤â¤¬¸ø³«¸°¤ò»È¤Ã¤Æ½ð̾¤òÉü¹æ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢ +½ð̾¼Ô¤Î¤ß¤¬ÈëÌ©¸°¤òÃΤäƤ¤¤Þ¤¹¡£ +¤³¤ì¤Ï¡¢Èà¤é¤Î¤ß¤¬½ð̾¤·¤¨¤¿¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ +¥À¥¤¥¸¥§¥¹¥È¤òÅŻҽð̾¤Ë´Þ¤à¤³¤È¤Ï¡¢ +¤½¤Î½ð̾¤¬¤½¤Î¥á¥Ã¥»¡¼¥¸¤Î¤ß¤ËÍ­¸ú¤Ç¤¢¤ë¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ +¤³¤ì¤Ï¡¢Ã¯¤â¥À¥¤¥¸¥§¥¹¥È¤òÊѤ¨¤Æ½ð̾¤ò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Ê¤¤¤¿¤á¡¢ +¥á¥Ã¥»¡¼¥¸¤Î¿®ÍѤâÊݾڤ·¤Þ¤¹¡£

+ +

¿¯Æþ¼Ô¤¬½ð̾¤ò˵¼õ¤·¤Æ¸åÆü¤ËºÆÍøÍѤ¹¤ë¤Î¤òËɤ°¤¿¤á +ÅŻҽð̾¤Ë¤Ï°ì°Õ¤Ê½èÍýÈֹ椬´Þ¤Þ¤ì¤Þ¤¹¡£ +¤³¤ì¤Ï¡¢¥¢¥ê¥¹¤¬¤½¤ó¤Ê¥á¥Ã¥»¡¼¥¸¤ÏÁ÷¤Ã¤Æ¤¤¤Ê¤¤¤È¸À¤¦º¾µ½ +¤«¤é¶ä¹Ô¤ò¼é¤ê¤Þ¤¹¡£ +Èà½÷¤À¤±¤¬½ð̾¤·¤¨¤¿¤«¤é¤Ç¤¹¡£(ÈÝǧËÉ»ß)

+ +
top
+
+

¾ÚÌÀ½ñ

+ +

¥¢¥ê¥¹¤ÏÈëÌ©¤Î¥á¥Ã¥»¡¼¥¸¤ò¶ä¹Ô¤ËÁ÷¤ê¡¢ +½ð̾¤ò¤·¤Æ¡¢¥á¥Ã¥»¡¼¥¸¤Î¿®ÍѤòÊݾڤ¹¤ë¤³¤È¤¬¤Ç¤­¤ë¤ª¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¤¬¡¢ +ÄÌ¿®¤·¤Æ¤¤¤ëÁê¼ê¤¬ËÜÅö¤Ë¶ä¹Ô¤Ê¤Î¤«³Î¤«¤á¤Ê¤¯¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ +¤³¤ì¤Ï¡¢Èà½÷¤¬»È¤¦¸ø³«¸°¤¬¶ä¹Ô¤ÎÈëÌ©¸°¤ÈÂФˤʤäƤ¤¤ë¤â¤Î¤«¡¢ +Èà½÷¤Ï³Î¤«¤á¤Ê¤¯¤Æ¤Ï¤¤¤±¤Ê¤¤¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ +ƱÍͤˡ¢¶ä¹Ô¤Ï¥á¥Ã¥»¡¼¥¸¤Î½ð̾¤¬ËÜÅö¤Ë¥¢¥ê¥¹¤Î½ð̾¤«³Îǧ¤¹¤ëɬÍפ¬ +¤¢¤ê¤Þ¤¹¡£

+ +

¤â¤·Î¾¼Ô¤Ë¿È¸µ¤ò¾ÚÌÀ¤·¡¢¸ø³«¸°¤ò³Îǧ¤·¡¢¤Þ¤¿¿®Íꤵ¤ì¤¿µ¡´Ø¤¬½ð̾ +¤·¤¿¾ÚÌÀ½ñ¤¬¤¢¤ì¤Ð¡¢Î¾¼Ô¤È¤âÄÌ¿®Áê¼ê¤Ë¤Ä¤¤¤ÆÀµ¤·¤¤Áê¼ê¤À¤È +³Î¿®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +¤½¤Î¤è¤¦¤Ê¿®Íꤵ¤ì¤¿µ¡´Ø¤Ïǧ¾Ú¶É + (Certificate Authority ¤Þ¤¿¤Ï CA) ¤È¸Æ¤Ð¤ì¡¢ +¾ÚÌÀ½ñ (certificate) ¤¬Ç§¾Ú (authentication) ¤Ë»È¤ï¤ì¤Þ¤¹¡£

+ +

¾ÚÌÀ½ñ¤ÎÆâÍÆ

+ +

¾ÚÌÀ½ñ¤Ï¸ø³«¸°¤È¸Ä¿Í¡¢¥µ¡¼¥Ð¡¢¤½¤Î¾¤Î¼çÂΤμºߤοȸµ¤ò + ´ØÏ¢ÉÕ¤±¤Þ¤¹¡£ + ɽ1¤Ë¼¨¤µ¤ì¤ë¤è¤¦¤Ë¾ÚÌÀÂоݤξðÊó¤Ï + ¿È¸µ¾ÚÌÀ¤Î¾ðÊó(¼±ÊÌ̾)¤È¸ø³«¸°¤¬´Þ¤Þ¤ì¤Þ¤¹¡£ + ¾ÚÌÀ½ñ¤Ï¤Þ¤¿¡¢Ç§¾Ú¶É¤Î¿È¸µ¾ÚÌÀ¤È½ð̾¡¢¤½¤·¤Æ¾ÚÌÀ½ñ¤ÎÍ­¸ú´ü´Ö¤ò + ´Þ¤ß¤Þ¤¹¡£ + ¥·¥ê¥¢¥ë¥Ê¥ó¥Ð¡¼¤Ê¤É¤Îǧ¾Ú¶É¤Î´ÉÍý¾å¤Î¾ðÊó¤ä + ¤½¤Î¾¤ÎÄɲäξðÊ󤬴ޤޤì¤Æ¤¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ +

ɽ1: ¾ÚÌÀ½ñ¾ðÊó

+ + + + + + + + + + + + + +
¾ÚÌÀÂоݼ±ÊÌ̾¡¢¸ø³«¸°
ȯ¹Ô¼Ô¼±ÊÌ̾¡¢¸ø³«¸°
Í­¸ú´ü´Ö³«»ÏÆü¡¢¼º¸úÆü
´ÉÍý¾ðÊó¥Ð¡¼¥¸¥ç¥ó¡¢¥·¥ê¥¢¥ë¥Ê¥ó¥Ð¡¼
³ÈÄ¥¾ðÊó´ðËÜŪ¤ÊÀ©Ì󡢥ͥåȥ¹¥±¡¼¥×¥Õ¥é¥Ã¥°¡¢¤½¤Î¾
+ + +

¼±ÊÌ̾(¥Ç¥£¥¹¥Æ¥£¥ó¥°¥¤¥Ã¥·¥å¡¦¥Í¡¼¥à)¤ÏÆÃÄê¤Î¾õ¶·¤Ë¤ª¤±¤ë + ¿Èʬ¾ÚÌÀ¤òÄ󶡤¹¤ë¤Î¤Ë»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£Î㤨¤Ð¡¢¤¢¤ë¿Í¤Ï + »äÍѤȲñ¼Ò¤È¤ÇÊÌ¡¹¤Î¿Èʬ¾ÚÌÀ¤ò»ý¤Ä¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + + ¼±ÊÌ̾¤Ï X.509 ɸ½àµ¬³Ê [X509] ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + X.509 ɸ½àµ¬³Ê¤Ï¡¢¹àÌÜ¡¢¹àÌÜ̾¡¢¤½¤·¤Æ¹àÌܤÎά¾Î¤òÄêµÁ¤·¤Æ¤¤¤Þ¤¹¡£(ɽ + 2 »²¾È)

+ +

ɽ 2: ¼±ÊÌ̾¾ðÊó

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
¼±ÊÌ̾¹àÌÜά¾ÎÀâÌÀÎã
Common Name (¥³¥â¥ó¥Í¡¼¥à)CNǧ¾Ú¤µ¤ì¤ë̾Á°
+ SSLÀܳ¤¹¤ëURL		CN=www.example.com
Organization or Company (ÁÈ¿¥Ì¾)OÃÄÂΤÎÀµ¼°±Ñ¸ìÁÈ¿¥Ì¾O=Example Japan K.K.
Organizational Unit (ÉôÌç̾)OUÉô½ð̾¤Ê¤ÉOU=Customer Service
City/Locality (»Ô¶èĮ¼)L½êºß¤·¤Æ¤ë»Ô¶èĮ¼L=Sapporo
State/Province (ÅÔÆ»Éܸ©)ST½êºß¤·¤Æ¤ëÅÔÆ»Éܸ©ST=Hokkaido
Country(¹ñ)C½êºß¤·¤Æ¤¤¤ë¹ñ̾¤Î ISO ¥³¡¼¥É
+ ÆüËܤξì¹ç JP + 		C=JP
+ + +

ǧ¾Ú¶É¤Ï¤É¤Î¹àÌܤ¬¾Êά²Äǽ¤Ç¤É¤ì¤¬É¬¿Ü¤«¤ÎÊý¿Ë¤òÄêµÁ¤¹¤ë + ¤«¤â¤·¤ì¤Þ¤»¤ó¡£¹àÌܤÎÆâÍƤˤĤ¤¤Æ¤âǧ¾Ú¶É¤ä¾ÚÌÀ½ñ¤Î¥æ¡¼¥¶¤«¤é¤Î + Í׷郎¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + Î㤨¤Ð¡¢¥Í¥Ã¥È¥¹¥±¡¼¥×¤Î¥Ö¥é¥¦¥¶¤Ï¥µ¡¼¥Ð¤Î¾ÚÌÀ½ñ¤Î + Common Name (¥³¥â¥ó¥Í¡¼¥à)¤¬¥µ¡¼¥Ð¤Î¥É¥á¥¤¥ó̾¤Î + *.example.com + ¤È¤¤¤¦¤è¤¦¤Ê¥ï¥¤¥ë¥É¥«¡¼¥É¤Î¥Ñ¥¿¡¼¥ó¤Ë¥Þ¥Ã¥Á¤¹¤ë¤³¤È + ¤òÍ׵ᤷ¤Þ¤¹¡£

+ +

¥Ð¥¤¥Ê¥ê·Á¼°¤Î¾ÚÌÀ½ñ¤Ï ASN.1 ɽµ­Ë¡ + [X208] [PKCS] ¤Ç + ÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Îɽµ­Ë¡¤ÏÆâÍƤò¤É¤Î¤è¤¦¤Ëµ­½Ò¤¹¤ë¤«¤òÄêµÁ¤·¡¢ + Éä¹æ²½¤Îµ¬Ä꤬¤³¤Î¾ðÊ󤬤ɤΤ褦¤Ë¥Ð¥¤¥Ê¥ê·Á¼°¤ËÊÑ´¹¤µ¤ì¤ë¤«¤ò + ÄêµÁ¤·¤Þ¤¹¡£ + ¾ÚÌÀ½ñ¤Î¥Ð¥¤¥Ê¥êÉä¹æ²½¤Ï Distinguished Encoding + Rules (DER) ¤ÇÄêµÁ¤µ¤ì¡¢¤½¤ì¤Ï¤è¤ê°ìÈÌŪ¤Ê Basic Encoding Rules + (BER) ¤Ë´ð¤Å¤¤¤Æ¤¤¤Þ¤¹¡£ + ¥Ð¥¤¥Ê¥ê·Á¼°¤ò°·¤¦¤³¤È¤Î¤Ç¤­¤Ê¤¤Á÷¿®¤Ç¤Ï¡¢ + ¥Ð¥¤¥Ê¥ê·Á¼°¤Ï Base64 Éä¹æ²½ [MIME] ¤Ç + ASCII ·Á¼°¤ËÊÑ´¹¤µ¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤ËÉä¹æ²½¤µ¤ì¡¢°Ê²¼¤ÎÎã¤Ë¼¨¤µ¤ì¤ë¤è¤¦¤Ë¶èÀÚ¤ê¹Ô¤Ë + ¶´¤Þ¤ì¤¿¤â¤Î¤Ï PEM Éä¹æ²½¤µ¤ì¤¿¤È¸À¤¤¤Þ¤¹¡£ + (PEM ¤Î̾Á°¤Ï "Privacy Enhanced Mail" ¤ËͳÍ褷¤Þ¤¹)

+ +

PEM Éä¹æ²½¤µ¤ì¤¿¾ÚÌÀ½ñ¤ÎÎã (example.crt)

-----BEGIN CERTIFICATE-----
+MIIC7jCCAlegAwIBAgIBATANBgkqhkiG9w0BAQQFADCBqTELMAkGA1UEBhMCWFkx
+FTATBgNVBAgTDFNuYWtlIERlc2VydDETMBEGA1UEBxMKU25ha2UgVG93bjEXMBUG
+A1UEChMOU25ha2UgT2lsLCBMdGQxHjAcBgNVBAsTFUNlcnRpZmljYXRlIEF1dGhv
+cml0eTEVMBMGA1UEAxMMU25ha2UgT2lsIENBMR4wHAYJKoZIhvcNAQkBFg9jYUBz
+bmFrZW9pbC5kb20wHhcNOTgxMDIxMDg1ODM2WhcNOTkxMDIxMDg1ODM2WjCBpzEL
+MAkGA1UEBhMCWFkxFTATBgNVBAgTDFNuYWtlIERlc2VydDETMBEGA1UEBxMKU25h
+a2UgVG93bjEXMBUGA1UEChMOU25ha2UgT2lsLCBMdGQxFzAVBgNVBAsTDldlYnNl
+cnZlciBUZWFtMRkwFwYDVQQDExB3d3cuc25ha2VvaWwuZG9tMR8wHQYJKoZIhvcN
+AQkBFhB3d3dAc25ha2VvaWwuZG9tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKB
+gQDH9Ge/s2zcH+da+rPTx/DPRp3xGjHZ4GG6pCmvADIEtBtKBFAcZ64n+Dy7Np8b
+vKR+yy5DGQiijsH1D/j8HlGE+q4TZ8OFk7BNBFazHxFbYI4OKMiCxdKzdif1yfaa
+lWoANFlAzlSdbxeGVHoT0K+gT5w3UxwZKv2DLbCTzLZyPwIDAQABoyYwJDAPBgNV
+HRMECDAGAQH/AgEAMBEGCWCGSAGG+EIBAQQEAwIAQDANBgkqhkiG9w0BAQQFAAOB
+gQAZUIHAL4D09oE6Lv2k56Gp38OBDuILvwLg1v1KL8mQR+KFjghCrtpqaztZqcDt
+2q2QoyulCgSzHbEGmi0EsdkPfg6mp0penssIFePYNI+/8u9HT4LuKMJX15hxBam7
+dUHzICxBVC1lnHyYGjDuAMhe396lYAn8bCld1/L4NMGBCQ==
+-----END CERTIFICATE-----
+ + +

ǧ¾Ú¶É

+ +

¤Þ¤º¾ÚÌÀ½ñ¤Î¿½ÀÁ¤Î¾ðÊó¤ò³Îǧ¤¹¤ë¤³¤È¤Ç¡¢ + ǧ¾Ú¶É¤ÏÈëÌ©¸°¤Î»ý¤Á¼ç¤Î¿È¸µ¤òÊݾڤ·¤Þ¤¹¡£ + Î㤨¤Ð¡¢¥¢¥ê¥¹¤¬¸Ä¿Í¾ÚÌÀ½ñ¤ò¿½ÀÁ¤·¤¿¤È¤¹¤ë¤È¡¢ + ǧ¾Ú¶É¤Ï¥¢¥ê¥¹¤¬¾ÚÌÀ½ñ¤Î¿½ÀÁ¤¬¼çÄ¥¤¹¤ëÄ̤ê¤Î + ¿Íʪ¤À¤È¤¤¤¦¤³¤È¤ò³Îǧ¤·¤Ê¤¯¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£

+ +

¾ÚÌÀ½ñ³¬Áع½Â¤

+ +

ǧ¾Ú¶É¤Ï¾¤Îǧ¾Ú¶É¤Ø¤Î¾ÚÌÀ½ñ¤òȯ¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ̤ÃΤξÚÌÀ½ñ¤òÄ´¤Ù¤ë»þ¤Ë¡¢¥¢¥ê¥¹¤Ï¤½¤Î¾ÚÌÀ½ñ¤Îȯ¹Ô¼Ô + ¤Ë¼«¿®¤¬»ý¤Æ¤ë¤Þ¤Ç¡¢È¯¹Ô¼Ô¤Î¾ÚÌÀ½ñ¤ò + ¤½¤Î¾å°Ì³¬ÁؤÎǧ¾Ú¶É¤ò¤¿¤É¤Ã¤ÆÄ´¤Ù¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¡Ö°­¼Á¤Ê¡×¾ÚÌÀ½ñ¤Î´í¸±À­¤ò¸º¤é¤¹¤¿¤á¡¢ + Èà½÷¤Ï¸Â¤é¤ì¤¿Ï¢º¿¤Îȯ¹Ô¼Ô¤Î¤ß¿®Íꤹ¤ë¤è¤¦¤Ë + ·è¤á¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

+ + +

ºÇ¾å°Ìǧ¾Ú¶É¤ÎºîÀ®

+ +

Á°¤Ë½Ò¤Ù¤¿¤è¤¦¤Ë¡¢Á´¤Æ¤Î¾ÚÌÀ½ñ¤Ë¤Ä¤¤¤Æ¡¢ + ºÇ¾å°Ì¤Îǧ¾Ú¶É(CA)¤Þ¤Ç¤½¤ì¤¾¤ì¤Îȯ¹Ô¼Ô¤¬ + Âоݤοȸµ¾ÚÌÀ¤ÎÍ­¸úÀ­¤òÌÀ¤é¤«¤Ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ÌäÂê¤Ï¡¢Ã¯¤¬¤½¤ÎºÇ¾å°Ì¤Îǧ¾Úµ¡´Ø¤Î¾ÚÌÀ½ñ¤òÊݾڤ¹¤ë¤Î¤«¡¢ + ¤È¤¤¤¦¤³¤È¤Ç¤¹¡£ + ¤³¤Î¤è¤¦¤Ê¾ì¹ç¤Ë¸Â¤ê¡¢¾ÚÌÀ½ñ¤Ï¡Ö¼«¸Ê½ð̾¡×¤µ¤ì¤Þ¤¹¡£ + ¤Ä¤Þ¤ê¡¢¾ÚÌÀ½ñ¤Îȯ¹Ô¼Ô¤È¾ÚÌÀÂоݤ¬Æ±¤¸¤È¤¤¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤½¤Î·ë²Ì¡¢¼«¸Ê½ð̾¤µ¤ì¤¿¾ÚÌÀ½ñ¤ò¿®ÍѤ¹¤ë¤Ë¤Ï + ºÙ¿´¤ÎÃí°Õ¤¬É¬ÍפǤ¹¡£ + ºÇ¾å°Ìǧ¾Ú¶É¤¬¸ø³«¸°¤ò¹­¤¯¸øɽ¤¹¤ë¤³¤È¤Ç¡¢ + ¤½¤Î¸°¤ò¿®Íꤹ¤ë¥ê¥¹¥¯¤òÄ㤯¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤â¤·¡¢Â¾¿Í¤¬¤½¤Îǧ¾Ú¶É¤Ë¤Ê¤ê¤¹¤Þ¤·¤¿»þ¤Ë¡¢¤½¤ì¤¬Ïª¸«¤·¤ä + ¤¹¤¤¤«¤é¤Ç¤¹¡£ + ¿¤¯¤Î¥Ö¥é¥¦¥¶¤Ïͭ̾¤Êǧ¾Ú¶É¤ò¿®Íꤹ¤ë¤è¤¦¤Ë + ÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£

+ +

Thawte + ¤ä VeriSign + ¤Î¤è¤¦¤Ê¿¤¯¤Î²ñ¼Ò¤¬Ç§¾Ú¶É¤È¤·¤Æ³«Àߤ·¤Þ¤·¤¿¡£ + ¤³¤Î¤è¤¦¤Ê²ñ¼Ò¤Ï°Ê²¼¤Î¥µ¡¼¥Ó¥¹¤òÄ󶡤·¤Þ¤¹:

+ +
    +
  • ¾ÚÌÀ½ñ¿½ÀÁ¤Î³Îǧ
    • +
  • ¾ÚÌÀ½ñ¿½ÀÁ¤Î½èÍý
    • +
  • ¾ÚÌÀ½ñ¤Îȯ¹Ô¤È´ÉÍý
    • +
+ +

¼«Ê¬¤Çǧ¾Ú¶É¤òºî¤ë¤³¤È¤â²Äǽ¤Ç¤¹¡£ + ¥¤¥ó¥¿¡¼¥Í¥Ã¥È´Ä¶­¤Ç¤Ï´í¸±¤Ç¤¹¤¬¡¢ + ¸Ä¿Í¤ä¥µ¡¼¥Ð¤Î¿È¸µ¾ÚÌÀ¤¬´Êñ¤Ë¹Ô¤¨¤ëÁÈ¿¥¤Î + ¥¤¥ó¥È¥é¥Í¥Ã¥ÈÆâ¤Ç¤ÏÌò¤ËΩ¤Ä¤«¤â¤·¤ì¤Þ¤»¤ó¡£

+ + +

¾ÚÌÀ½ñ´ÉÍý

+ +

ǧ¾Ú¶É¤Î³«ÀߤÏÅ°Ä줷¤¿´ÉÍý¡¢µ»½Ñ¡¢±¿ÍѤÎÂÎÀ©¤òɬÍפȤ¹¤ë + ÀÕǤ¤Î¤¢¤ë»Å»ö¤Ç¤¹¡£ + ǧ¾Ú¶É¤Ï¾ÚÌÀ½ñ¤òȯ¹Ô¤¹¤ë¤À¤±¤Ç¤Ê¤¯¡¢ + ´ÉÍý¤â¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¶ñÂÎŪ¤Ë¤Ï¡¢¾ÚÌÀ½ñ¤¬¤¤¤Ä¤Þ¤ÇÍ­¸ú¤«¤ò·èÄꤷ¡¢¹¹¿·¤·¡¢ + ¤Þ¤¿´û¤Ëȯ¹Ô¤µ¤ì¤¿¤¬¼º¸ú¤·¤¿¾ÚÌÀ½ñ¤Î¥ê¥¹¥È + (Certificate Revocation Lists ¤Þ¤¿¤Ï CRL) + ¤ò´ÉÍý¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£ + Î㤨¤Ð¡¢¥¢¥ê¥¹¤¬²ñ¼Ò¤«¤é¼Ò°÷¤È¤·¤Æ¾ÚÌÀ½ñ¤òÍ¿¤¨¤é¤ì¤¿¤È¤·¤Þ¤¹¡£ + ¤½¤·¤Æ¡¢¥¢¥ê¥¹¤¬²ñ¼Ò¤ò¼­¤á¤ë¤È¤­¤Ë¤Ï¾ÚÌÀ½ñ¤ò¼è¤ê¾Ã¤µ¤Ê¤±¤ì¤Ð + ¤¤¤±¤Ê¤¤¤È¤·¤Þ¤¹¡£ + ¾ÚÌÀ½ñ¤Ï¼¡¡¹¤È¿Í¤ËÅϤµ¤ì¤Æ¤¤¤¯¤â¤Î¤Ê¤Î¤Ç¡¢ + ¾ÚÌÀ½ñ¤½¤Î¤â¤Î¤«¤é¡¢¤½¤ì¤¬¼è¤ê¾Ã¤µ¤ì¤¿¤«È½ÃǤ¹¤ë¤³¤È¤Ï + ÉÔ²Äǽ¤Ç¤¹¡£ + ¤è¤Ã¤Æ¡¢¾ÚÌÀ½ñ¤ÎÍ­¸úÀ­¤òÄ´¤Ù¤ë¤È¤­¤Ë¤Ï¡¢ + ǧ¾Ú¶É¤ËÏ¢Íí¤·¤Æ CRL ¤ò¾È¹ç¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ÉáÄ̤³¤Î²áÄø¤Ï¼«Æ°²½¤µ¤ì¤Æ¤¤¤ë¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£

+ +

Ãí°Õ

+

¥Ç¥Õ¥©¥ë¥È¤Ç¥Ö¥é¥¦¥¶¤ËÀßÄꤵ¤ì¤Æ¤¤¤Ê¤¤Ç§¾Ú¶É¤ò»È¤Ã¤¿¾ì¹ç¡¢ + ǧ¾Ú¶É¤Î¾ÚÌÀ½ñ¤ò¥Ö¥é¥¦¥¶¤ËÆɤ߹þ¤ó¤Ç¡¢ + ¥Ö¥é¥¦¥¶¤¬¤½¤Îǧ¾Ú¶É¤Ë¤è¤Ã¤Æ½ð̾¤µ¤ì¤¿¥µ¡¼¥Ð¤Î¾ÚÌÀ½ñ¤ò + Í­¸ú²½¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + °ìÅÙÆɤ߹þ¤Þ¤ì¤ë¤È¡¢¤½¤Îǧ¾Ú¶É¤Ë¤è¤Ã¤Æ½ð̾¤µ¤ì¤¿Á´¤Æ¤Î + ¾ÚÌÀ½ñ¤ò¼õ¤±Æþ¤ì¤ë¤¿¤á¡¢´í¸±¤òȼ¤¤¤Þ¤¹¡£

+
+ + + +
top
+
+

Secure Sockets Layer (SSL)

+ +

Secure Sockets Layer ¥×¥í¥È¥³¥ë¤Ï¿®ÍêÀ­¤Î¤¢¤ë¥³¥Í¥¯¥·¥ç¥ó·¿¤Î +¥Í¥Ã¥È¥ï¡¼¥¯ÁؤΥץí¥È¥³¥ë(Î㤨¤Ð¡¢TCP/IP)¤È +¥¢¥×¥ê¥±¡¼¥·¥ç¥óÁؤΥץí¥È¥³¥ë(Î㤨¤Ð¡¢HTTP) +¤Î´Ö¤ËÃÖ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +SSL ¤Ï¡¢Áê¸ßǧ¾Ú¤Ë¤è¤Ã¤Æ¥µ¡¼¥Ð¤È¥¯¥é¥¤¥¢¥ó¥È´Ö¤Î°ÂÁ´¤ÊÄÌ¿®¤ò¡¢ +ÅŻҽð̾¤Ë¤è¤Ã¤Æ¥Ç¡¼¥¿¤Î´°Á´À­¤ò¡¢ +¤½¤·¤Æ°Å¹æ²½¤Ë¤è¤Ã¤Æ¥×¥é¥¤¥Ð¥·¤òÄ󶡤·¤Þ¤¹¡£

+ +

SSL ¥×¥í¥È¥³¥ë¤Ï°Å¹æ²½¡¢¥À¥¤¥¸¥§¥¹¥È¡¢ÅŻҽð̾¤Ë¤Ä¤¤¤Æ¡¢ +ÍÍ¡¹¤Ê¥¢¥ë¥´¥ê¥º¥à¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Æ¤¤¤Þ¤¹¡£ +¤³¤¦¤¹¤ë¤³¤È¤Ç¡¢Ë¡¤äÍ¢½Ð¤Îµ¬À©¤ò¹Íθ¤ËÆþ¤ì¤Æ¡¢¥µ¡¼¥Ð¤Ë¹ç¤ï¤»¤¿ +¥¢¥ë¥´¥ê¥º¥à¤òÁª¤Ö¤³¤È¤¬¤Ç¤­¡¢¤Þ¤¿¡¢¿·¤·¤¤¥¢¥ë¥´¥ê¥º¥à¤ò +ÍøÍѤ·¤Æ¤¤¤¯¤³¤È¤â²Äǽ¤Ë¤·¤Æ¤¤¤Þ¤¹¡£ +¥¢¥ë¥´¥ê¥º¥à¤ÎÁªÂò¤Ï¥×¥í¥È¥³¥ë¥»¥Ã¥·¥ç¥ó³«»Ï»þ¤Ë +¥µ¡¼¥Ð¤È¥¯¥é¥¤¥¢¥ó¥È´Ö¤Ç¼è¤ê·è¤á¤é¤ì¤Þ¤¹¡£

+ +

ɽ4: SSL ¥×¥í¥È¥³¥ë¤Î¥Ð¡¼¥¸¥ç¥ó

+ + + + + + + + + + + + + + + + + + + +
¥Ð¡¼¥¸¥ç¥ó½ÐŵÀâÌÀ¥Ö¥é¥¦¥¶¤Î¥µ¥Ý¡¼¥È
SSL v2.0Vendor Standard (Netscape Corp. ¤è¤ê) [SSL2]¼ÂÁõ¤¬¸½Â¸¤¹¤ë½é¤á¤Æ¤Î SSL ¥×¥í¥È¥³¥ë- NS Navigator 1.x/2.x
+ - MS IE 3.x
+ - Lynx/2.8+OpenSSL
SSL v3.0Expired Internet Draft (Netscape Corp. ¤è¤ê) [SSL3]ÆÃÄê¤Î¥»¥­¥å¥ê¥Æ¥£¹¶·â¤òËɤ°¤¿¤á¤Î²þÄû¡¢ + ÈóRSA °Å¹æ¤ÎÄɲᢾÚÌÀ½ñ³¬Áع½Â¤¤Î¥µ¥Ý¡¼¥È- NS Navigator 2.x/3.x/4.x
+ - MS IE 3.x/4.x
+ - Lynx/2.8+OpenSSL
TLS v1.0Proposed Internet Standard (IETF ¤è¤ê) [TLS1]MAC ¥ì¥¤¥ä¤ò HMAC ¤Ø¹¹¿·¡¢¥Ö¥í¥Ã¥¯°Å¹æ¤Î block + padding¡¢¥á¥Ã¥»¡¼¥¸½ç½ø¤Îɸ½à²½¡¢·Ù¹ðʸ¤Î½¼¼Â¤Ê¤É¤Î¤¿¤á + SSL 3.0 ¤ò²þÄû¡£- Lynx/2.8+OpenSSL
+ + +

ɽ4¤Ë¼¨¤µ¤ì¤ë¤È¤ª¤ê¡¢SSL ¥×¥í¥È¥³¥ë¤Ë¤Ï +¤¤¤¯¤Ä¤â¤Î¥Ð¡¼¥¸¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£ +ɽ¤Ë¤â½ñ¤«¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¡¢SSL 3.0 ¤ÎÍøÅÀ¤Î°ì¤Ä¤Ï +¾ÚÌÀ½ñ³¬Áع½Â¤¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤³¤È¤Ç¤¹¡£ +¤³¤Îµ¡Ç½¤Ë¤è¤Ã¤Æ¡¢¥µ¡¼¥Ð¤Ï¼«Ê¬¤Î¾ÚÌÀ½ñ¤Ë²Ã¤¨¤Æ¡¢ +ȯ¹Ô¼Ô¤Î¾ÚÌÀ½ñ¤ò¥Ö¥é¥¦¥¶¤ËÅϤ¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +¾ÚÌÀ½ñ³¬Áع½Â¤¤Ë¤è¤Ã¤Æ¡¢ +¥Ö¥é¥¦¥¶¤Ëȯ¹Ô¼Ô¤Î¾ÚÌÀ½ñ¤¬Ä¾ÀÜÅÐÏ¿¤µ¤ì¤Æ¤¤¤Ê¤¯¤Æ¤â¡¢ +³¬ÁؤÎÃæ¤Ë´Þ¤Þ¤ì¤Æ¤¤¤ì¤Ð¡¢ +¥Ö¥é¥¦¥¶¤Ï¥µ¡¼¥Ð¤Î¾ÚÌÀ½ñ¤òÍ­¸ú²½¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ +SSL 3.0 ¤Ï¸½ºß Internet Engineering Task Force (IETF) +¤Ë¤è¤Ã¤Æ³«È¯¤µ¤ì¤Æ¤¤¤ë Transport Layer Security +[TLS] ¥×¥í¥È¥³¥ëɸ½àµ¬³Ê¤Î´ðÁäȤʤäƤ¤¤Þ¤¹¡£

+ +

¥»¥Ã¥·¥ç¥ó¤Î³ÎΩ

+ +

¿Þ1¤Ç¼¨¤µ¤ì¤ë¤è¤¦¤Ë¡¢ + ¥»¥Ã¥·¥ç¥ó¤Î³ÎΩ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð´Ö¤Î + ¥Ï¥ó¥É¥·¥§¡¼¥¯¥·¡¼¥¯¥¨¥ó¥¹¤Ë¤è¤Ã¤Æ¹Ô¤Ê¤ï¤ì¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤¬¾ÚÌÀ½ñ¤òÄ󶡤¹¤ë¤«¡¢¥¯¥é¥¤¥¢¥ó¥È¤Î¾ÚÌÀ½ñ¤ò¥ê¥¯¥¨¥¹¥È¤¹¤ë¤« + ¤È¤¤¤¦¥µ¡¼¥Ð¤ÎÀßÄê¤Ë¤è¤ê¡¢¤³¤Î¥·¡¼¥¯¥¨¥ó¥¹¤Ï°Û¤Ê¤ë¤â¤Î¤È¤Ê¤ê¤Þ¤¹¡£ + °Å¹æ¾ðÊó¤Î´ÉÍý¤Î¤¿¤á¤Ë¡¢ÄɲäΥϥó¥É¥·¥§¡¼¥¯²áÄø¤¬É¬Íפˤʤë + ¾ì¹ç¤â¤¢¤ê¤Þ¤¹¤¬¡¢¤³¤Îµ­»ö¤Ç¤Ï + ¤è¤¯¤¢¤ë¥·¥Ê¥ê¥ª¤ò¼êû¤ËÀâÌÀ¤·¤Þ¤¹¡£ + Á´¤Æ¤Î²ÄǽÀ­¤Ë¤Ä¤¤¤Ï¡¢SSL »ÅÍͽñ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

Ãí°Õ

+

°ìÅÙ SSL ¥»¥Ã¥·¥ç¥ó¤¬³ÎΩ¤¹¤ë¤È¡¢¥»¥Ã¥·¥ç¥ó¤òºÆÍøÍѤ¹¤ë¤³¤È¤Ç¡¢ + ¥»¥Ã¥·¥ç¥ó¤ò³«»Ï¤¹¤ë¤¿¤á¤Î¿¤¯¤Î²áÄø¤ò·«¤êÊÖ¤¹¤È¤¤¤¦ + ¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤Î»¼º¤òËɤ®¤Þ¤¹¡£ + ¤½¤Î¤¿¤á¡¢¥µ¡¼¥Ð¤ÏÁ´¤Æ¤Î¥»¥Ã¥·¥ç¥ó¤Ë°ì°Õ¤Ê¥»¥Ã¥·¥ç¥ó¼±ÊÌ̾¤ò + ³ä¤êÅö¤Æ¡¢¥µ¡¼¥Ð¤Ë¥­¥ã¥Ã¥·¥å¤·¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï¼¡²ó¤«¤é + (¼±ÊÌ̾¤¬¥µ¡¼¥Ð¤Î¥­¥ã¥Ã¥·¥å¤Ç´ü¸ÂÀÚ¤ì¤Ë¤Ê¤ë¤Þ¤Ç¤Ï) + ¥Ï¥ó¥É¥·¥§¡¼¥¯¤Ê¤·¤ÇÀܳ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

+
+ +

+
+ ¿Þ1: SSL + ¥Ï¥ó¥É¥·¥§¡¼¥¯¥·¡¼¥¯¥¨¥ó¥¹³µÎ¬

+ +

¥µ¡¼¥Ð¤È¥¯¥é¥¤¥¢¥ó¥È¤Ç»È¤ï¤ì¤ë + ¥Ï¥ó¥É¥·¥§¡¼¥¯¥·¡¼¥¯¥¨¥ó¥¹¤ÎÍ×ÁǤò°Ê²¼¤Ë¼¨¤·¤Þ¤¹:

+ +
    +
  1. ¥Ç¡¼¥¿ÄÌ¿®¤Ë»È¤ï¤ì¤ë°Å¹æ¥¹¥¤¡¼¥È¤Î¼è¤ê·è¤á
    2. +
  2. ¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð´Ö¤Ç¤Î¥»¥Ã¥·¥ç¥ó¸°¤Î³ÎΩ¤È¶¦Í­
    3. +
  3. ¥ª¥×¥·¥ç¥ó¤È¤·¤Æ¡¢¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ¹¤ë¥µ¡¼¥Ð¤Îǧ¾Ú
    4. +
  4. ¥ª¥×¥·¥ç¥ó¤È¤·¤Æ¡¢¥µ¡¼¥Ð¤ËÂФ¹¤ë¥¯¥é¥¤¥¢¥ó¥È¤Îǧ¾Ú
    5. +
+ +

Âè°ì¥¹¥Æ¥Ã¥×¤Î°Å¹æ¥¹¥¤¡¼¥È¼è¤ê·è¤á¤Ë¤è¤Ã¤Æ¡¢ + ¥µ¡¼¥Ð¤È¥¯¥é¥¤¥¢¥ó¥È¤Ï¤½¤ì¤¾¤ì¤Ë¤¢¤Ã¤¿ + °Å¹æ¥¹¥¤¡¼¥È¤òÁª¤Ö¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + SSL3.0 ¥×¥í¥È¥³¥ë¤Î»ÅÍͽñ¤Ï 31 ¤Î°Å¹æ¥¹¥¤¡¼¥È¤òÄêµÁ¤·¤Æ¤¤¤Þ¤¹¡£ + °Å¹æ¥¹¥¤¡¼¥È¤Ï°Ê²¼¤Î¥³¥ó¥Ý¡¼¥Í¥ó¥È¤Ë¤è¤êÄêµÁ¤µ¤ì¤Æ¤¤¤Þ¤¹:

+ +
    +
  • ¸°¤Î¸ò´¹¼êÃÊ
    • +
  • ¥Ç¡¼¥¿ÄÌ¿®¤Î°Å¹æ½Ñ
    • +
  • Message Authentication Code (MAC) ºîÀ®¤Î¤¿¤á¤Î + ¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È
    • +
+ +

¤³¤ì¤é¤Î»°¤Ä¤ÎÍ×ÁǤϰʲ¼¤Î¥»¥¯¥·¥ç¥ó¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

+ + +

¸°¤Î¸ò´¹¼êÃÊ

+ +

¸°¤Î¸ò´¹¼êÃʤϥ¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¥Ç¡¼¥¿ÄÌ¿®¤Ë»È¤ï¤ì¡¢ + ¶¦Í­¤µ¤ì¤ëÂоΰŹ渰¤ò¤É¤Î¤è¤¦¤Ë¤¬¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¤Ç + ¼è¤ê·è¤á¤ë¤«¤òÄêµÁ¤·¤Þ¤¹¡£ + SSL 2.0 ¤Ï RSA ¸°¸ò´¹¤·¤«»È¤¤¤Þ¤»¤ó¤¬¡¢ + SSL 3.0 ¤Ï¾ÚÌÀ½ñ¤¬»È¤ï¤ì¤ë¤È¤­¤Ï RSA ¸°¸ò´¹¤ò»È¤¤¡¢ + ¾ÚÌÀ½ñ¤¬Ìµ¤¯¡¢¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð¤Î»öÁ°¤ÎÄÌ¿®¤¬Ìµ¤¤¾ì¹ç¤Ï + Diffie-Hellman ¸°¸ò´¹¤ò»È¤¦ + ¤Ê¤ÉÍÍ¡¹¤Ê¸°¸ò´¹¥¢¥ë¥´¥ê¥º¥à¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£

+ +

¸°¤Î¸ò´¹ÊýË¡¤Ë¤ª¤±¤ë°ì¤Ä¤ÎÁªÂò»è¤ÏÅŻҽð̾¤Ç¤¹¡£ + ÅŻҽð̾¤ò»È¤¦¤«¤É¤¦¤«¡¢¤Þ¤¿¡¢ + ¤É¤Î¼ïÎà¤Î½ð̾¤ò»È¤¦¤«¤È¤¤¤¦ÁªÂò¤¬¤¢¤ê¤Þ¤¹¡£ + ÈëÌ©¸°¤Ç½ð̾¤¹¤ë¤³¤È¤Ç¶¦Í­¸°¤òÀ¸À®¤¹¤·¡¢¾ðÊó¸ò´¹¤¹¤ë»þ¤Î + ¥Þ¥ó¡¦¥¤¥ó¡¦¥¶¡¦¥ß¥É¥ë¹¶·â¤òËɤ°¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + [AC96, p516]

+ + +

¥Ç¡¼¥¿ÄÌ¿®¤Î°Å¹æ½Ñ

+ +

SSL ¤Ï¥»¥Ã¥·¥ç¥ó¤Î¥á¥Ã¥»¡¼¥¸¤Î°Å¹æ²½¤ËÁ°½Ò¤·¤¿ + ½¾Íè·¿°Å¹æ(ÂоΰŹæ)¤òÍѤ¤¤Þ¤¹¡£ + °Å¹æ²½¤·¤Ê¤¤¤È¤¤¤¦ÁªÂò»è¤â´Þ¤á¶å¤Ä¤ÎÁªÂò»è¤¬¤¢¤ê¤Þ¤¹:

+ +
    +
  • °Å¹æ²½¤Ê¤·
    • +
  • ¥¹¥È¥ê¡¼¥à°Å¹æ +
      +
    • 40-bit ¸°¤Ç¤Î RC4
      • +
    • 128-bit ¸°¤Ç¤Î RC4
      • +
    • +
  • CBC ¥Ö¥í¥Ã¥¯°Å¹æ +
    • 40 bit ¸°¤Ç¤Î RC2
      • +
    • 40 bit ¸°¤Ç¤Î DES
      • +
    • 56 bit ¸°¤Ç¤Î DES
      • +
    • 168 bit ¸°¤Ç¤Î Triple-DES
      • +
    • Idea (128 bit ¸°)
      • +
    • Fortezza (96 bit ¸°)
      • +
    • +
+ +

¤³¤³¤Ç¤Î CBC ¤È¤Ï°Å¹æ¥Ö¥í¥Ã¥¯Ï¢º¿ (Cipher Block Chaining) + ¤Îά¤Ç¡¢°ì¤ÄÁ°¤Î°Å¹æ²½¤µ¤ì¤¿°Å¹æʸ¤Î°ìÉô¤¬ + ¥Ö¥í¥Ã¥¯¤Î°Å¹æ²½¤Ë»È¤ï¤ì¤ë¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ + DES ¤Ï¥Ç¡¼¥¿°Å¹æ²½É¸½àµ¬³Ê (Data Encryption Standard) + [AC96, ch12] ¤Îά¤Ç¡¢ + DES40 ¤ä 3DES_EDE ¤ò´Þ¤à¤¤¤¯¤Ä¤â¤Î¼ïÎब¤¢¤ê¤Þ¤¹¡£ + Idea ¤ÏºÇ¹â¤Ê¤â¤Î¤Î°ì¤Ä¤Ç¡¢°Å¹æ½ÑŪ¤Ë¤Ï¸½ºß¤¢¤ëÃæ¤Ç + ºÇ¤â¶¯ÎϤʤâ¤Î¤Ç¤¹¡£ + RC2 ¤Ï RSA DSI ¤Ë¤è¤ëÆÈÀêŪ¤Ê¥¢¥ë¥´¥ê¥º¥à¤Ç¤¹¡£ + [AC96, + ch13]

+ + +

¥À¥¤¥¸¥§¥¹¥È´Ø¿ô

+ +

+ ¥À¥¤¥¸¥§¥¹¥È´Ø¿ô¤ÎÁªÂò¤Ï¥ì¥³¡¼¥É¥æ¥Ë¥Ã¥È¤«¤é¤É¤Î¤è¤¦¤Ë¥À¥¤¥¸¥§¥¹¥È¤¬À¸À®¤µ¤ì¤ë¤«¤ò·èÄꤷ¤Þ¤¹¡£ + SSL ¤Ï°Ê²¼¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹:

+ +
    +
  • ¥À¥¤¥¸¥§¥¹¥È¤Ê¤·
    • +
  • MD5 (128-bit ¥Ï¥Ã¥·¥å)
    • +
  • Secure Hash Algorithm (SHA-1) (160-bit ¥Ï¥Ã¥·¥å)
    • +
+ +

¥á¥Ã¥»¡¼¥¸¥À¥¤¥¸¥§¥¹¥È¤Ï Message Authentication Code (MAC) + ¤ÎÀ¸À®¤Ë»È¤ï¤ì¡¢¥á¥Ã¥»¡¼¥¸¤È¶¦¤Ë°Å¹æ²½¤µ¤ì¡¢¥á¥Ã¥»¡¼¥¸¤Î¿®ÍѤò + Ä󶡤·¡¢¥ê¥×¥ì¥¤¹¶·â¤òËɤ®¤Þ¤¹¡£

+ + +

¥Ï¥ó¥É¥·¥§¡¼¥¯¥·¡¼¥¯¥¨¥ó¥¹¥×¥í¥È¥³¥ë

+ +

¥Ï¥ó¥É¥·¥§¡¼¥¯¥·¡¼¥¯¥¨¥ó¥¹¤Ï»°¤Ä¤Î¥×¥í¥È¥³¥ë¤ò»È¤¤¤Þ¤¹:

+ +
    +
  • SSL ¥Ï¥ó¥É¥·¥§¡¼¥¯¥×¥í¥È¥³¥ë¤Ï + ¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð´Ö¤Ç¤Î SSL ¥»¥Ã¥·¥ç¥ó¤Î³ÎΩ¤Ë»È¤ï¤ì¤Þ¤¹¡£
    • +
  • SSL °Å¹æ»ÅÍÍÊѹ¹¥×¥í¥È¥³¥ë¤Ï + ¥»¥Ã¥·¥ç¥ó¤Ç¤Î°Å¹æ¥¹¥¤¡¼¥È¤Î¼è¤ê·è¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£
    • +
  • SSL ·Ù¹ð¥×¥í¥È¥³¥ë¤Ï + ¥¯¥é¥¤¥¢¥ó¥È¥µ¡¼¥Ð´Ö¤Ç SSL ¥¨¥é¡¼¤òÅÁ㤹¤ë¤Î¤Ë»È¤ï¤ì¤Þ¤¹¡£
    • +
+ +

»°¤Ä¤Î¥×¥í¥È¥³¥ë¤Ï¡¢¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¥×¥í¥È¥³¥ë¥Ç¡¼¥¿¤È¤È¤â¤Ë¡¢ + ¿Þ2¤Ë¼¨¤¹¤È¤ª¤ê SSL ¥ì¥³¡¼¥É¥×¥í¥È¥³¥ë + ¤Ç¥«¥×¥»¥ë²½¤µ¤ì¤Þ¤¹¡£ + ¥«¥×¥»¥ë²½¤µ¤ì¤¿¥×¥í¥È¥³¥ë¤Ï¥Ç¡¼¥¿¤ò¸¡ºº¤·¤Ê¤¤ + ²¼ÁؤΥץí¥È¥³¥ë¤Ë¤è¤Ã¤Æ¥Ç¡¼¥¿¤È¤·¤ÆÅÁ㤵¤ì¤Þ¤¹¡£ + ¥«¥×¥»¥ë²½¤µ¤ì¤¿¥×¥í¥È¥³¥ë¤Ï²¼ÁؤΥץí¥È¥³¥ë¤Ë´Ø¤·¤Æ°ìÀÚ´ØÃΤ·¤Þ¤»¤ó¡£

+ +

+
+ ¿Þ2: SSL ¥×¥í¥È¥³¥ë¥¹¥¿¥Ã¥¯ +

+ +

+ ¥ì¥³¡¼¥É¥×¥í¥È¥³¥ë¤Ë¤è¤ë SSL ¥³¥ó¥È¥í¡¼¥ë¥×¥í¥È¥³¥ë¤Î¥«¥×¥»¥ë²½¤Ï¡¢ + ¥¢¥¯¥Æ¥£¥Ö¤Ê¥»¥Ã¥·¥ç¥ó¤ÎÆó²óÌܤÎÄÌ¿®¤¬¤¢¤Ã¤¿¾ì¹ç¡¢ + ¥³¥ó¥È¥í¡¼¥ë¥×¥í¥È¥³¥ë¤¬°ÂÁ´¤Ç¤¢¤ë¤³¤È¤ò°ÕÌ£¤·¤Þ¤¹¡£ + ´û¤Ë¥»¥Ã¥·¥ç¥ó¤¬Ìµ¤¤¾ì¹ç¤Ï¡¢Null °Å¹æ¥¹¥¤¡¼¥È¤¬»È¤ï¤ì¡¢ + °Å¹æ²½¤Ï¹Ô¤Ê¤ï¤ì¤º¡¢¥»¥Ã¥·¥ç¥ó¤¬³ÎΩ¤¹¤ë¤Þ¤Ç¤Ï + ¥À¥¤¥¸¥§¥¹¥È¤â̵¤¤¾õÂ֤Ȥʤê¤Þ¤¹¡£

+ + +

¥Ç¡¼¥¿ÄÌ¿®

+ +

¿Þ3¤Ë¼¨¤µ¤ì¤ë SSL ¥ì¥³¡¼¥É¥×¥í¥È¥³¥ë + ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤È¥µ¡¼¥Ð´Ö¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ä + SSL ¥³¥ó¥È¥í¡¼¥ë¥Ç¡¼¥¿¤ÎÄÌ¿®¤Ë»È¤ï¤ì¤Þ¤¹¡£ + ¤³¤Î¥Ç¡¼¥¿¤Ï¤è¤ê¾®¤µ¤¤¥æ¥Ë¥Ã¥È¤Ëʬ¤±¤é¤ì¤¿¤ê¡¢ + ¤¤¤¯¤Ä¤«¤Î¹âµé¥×¥í¥È¥³¥ë¤ò¤Þ¤È¤á¤Æ°ì¥æ¥Ë¥Ã¥È¤È¤·¤ÆÄÌ¿®¤¬ + ¹Ô¤Ê¤ï¤ì¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£ + ¥Ç¡¼¥¿¤ò°µ½Ì¤·¡¢¥À¥¤¥¸¥§¥¹¥È½ð̾¤òźÉÕ¤·¤Æ¡¢ + ¤³¤ì¤é¤Î¥æ¥Ë¥Ã¥È¤ò°Å¹æ²½¤·¤¿¤Î¤Á¡¢¥Ù¡¼¥¹¤È¤Ê¤Ã¤Æ¤¤¤ë + ¿®ÍêÀ­¤Î¤¢¤ë¥È¥é¥ó¥¹¥Ý¡¼¥È¥×¥í¥È¥³¥ë¤òÍѤ¤¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + (Ãí°Õ: ¸½ºß¥á¥¸¥ã¡¼¤Ê SLL ¼ÂÁõ¤Ç°µ½Ì¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¤â¤Î¤Ï¤¢¤ê¤Þ¤»¤ó)

+ +

+
+ ¿Þ 3: SSL ¥ì¥³¡¼¥É¥×¥í¥È¥³¥ë +

+ + +

HTTP ÄÌ¿®¤Î°ÂÁ´²½

+ +

¤è¤¯¤¢¤ë SSL ¤Î»È¤¤Êý¤Ï¥Ö¥é¥¦¥¶¤È¥¦¥§¥Ö¥µ¡¼¥Ð´Ö¤Î HTTP ÄÌ¿® + ¤Î°ÂÁ´²½¤Ç¤¹¡£ + ¤³¤ì¤Ï¡¢½¾Íè¤Î°ÂÁ´¤Ç¤Ï¤Ê¤¤ HTTP ¤Î»ÈÍѤò½ü³°¤¹¤ë¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + °ÂÁ´²½¤µ¤ì¤¿¤â¤Î¤Ï¼ç¤Ë SSH ¾å¤ÎÉáÄ̤ΠHTTP ¤Ç¡¢HTTPS ¤È¸Æ¤Ð¤ì¤Þ¤¹¡£ + Â礭¤Ê°ã¤¤¤Ï¡¢URL ¥¹¥­¡¼¥à¤Ë http ¤ÎÂå¤ï¤ê¤Ë https + ¤òÍѤ¤¡¢¥µ¡¼¥Ð¤¬Ê̤Υݡ¼¥È¤ò»È¤¦¤³¤È¤Ç¤¹ (¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï443)¡£ + ¤³¤ì¤¬¼ç¤Ë mod_ssl ¤¬ Apache ¥¦¥§¥Ö¥µ¡¼¥Ð¤ËÄ󶡤¹¤ëµ¡Ç½¤Ç¤¹¡£

+ +
top
+
+

»²¹Íʸ¸¥

+ +
+
[AC96]
+
Bruce Schneier, Applied Cryptography, 2nd Edition, Wiley, +1996. See http://www.counterpane.com/ for various other materials by Bruce +Schneier.
+ +
[X208]
+
ITU-T Recommendation X.208, Specification of Abstract Syntax Notation +One (ASN.1), 1988. See for instance http://www.itu.int/rec/recommendation.asp?type=items&lang=e&parent=T-REC-X.208-198811-I. +
+ +
[X509]
+
ITU-T Recommendation X.509, The Directory - Authentication +Framework. See for instance http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-X.509. +
+ +
[PKCS]
+
Public Key Cryptography Standards (PKCS), +RSA Laboratories Technical Notes, See http://www.rsasecurity.com/rsalabs/pkcs/.
+ +
[MIME]
+
N. Freed, N. Borenstein, Multipurpose Internet Mail Extensions +(MIME) Part One: Format of Internet Message Bodies, RFC2045. +See for instance http://ietf.org/rfc/rfc2045.txt.
+ +
[SSL2]
+
Kipp E.B. Hickman, The SSL Protocol, 1995. See http://www.netscape.com/eng/security/SSL_2.html.
+ +
[SSL3]
+
Alan O. Freier, Philip Karlton, Paul C. Kocher, The SSL Protocol +Version 3.0, 1996. See http://www.netscape.com/eng/ssl3/draft302.txt.
+ +
[TLS1]
+
Tim Dierks, Christopher Allen, The TLS Protocol Version 1.0, +1999. See http://ietf.org/rfc/rfc2246.txt.
+
+
+
+

Available Languages:  en  | + ja 

+
+ \ No newline at end of file diff --git a/docs/manual/stopping.html b/docs/manual/stopping.html new file mode 100644 index 00000000..ceae3608 --- /dev/null +++ b/docs/manual/stopping.html @@ -0,0 +1,19 @@ +URI: stopping.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: stopping.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: stopping.html.es +Content-Language: es +Content-type: text/html; charset=ISO-8859-1 + +URI: stopping.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: stopping.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/stopping.html.de b/docs/manual/stopping.html.de new file mode 100644 index 00000000..44c2e749 --- /dev/null +++ b/docs/manual/stopping.html.de @@ -0,0 +1,306 @@ + + + +Beenden und Neustarten - Apache HTTP Server + + + + +
+

Module | Direktiven | FAQ | Glossar | Seitenindex

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP-Server > Dokumentation > Version 2.2

Beenden und Neustarten

+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko 

+
+
Diese Übersetzung ist möglicherweise + nicht mehr aktuell. Bitte prüfen Sie die englische Version auf + die neuesten Änderungen.
+ +

Dieses Dokument umfasst das Beenden und Neustarten des + Apache auf Unix-ähnlichen Systemen. Anwender von Windows NT, 2000 + und XP sollten Betreiben + des Apache als Dienst lesen, während hingegen Anwender von + Windows 9x sowie ME Betreiben + des Apache als Konsolenanwendung lesen sollten, um mehr Informationen + zur Handhabung des Apache auf diesen Systemen zu erhalten.

+
+ +
top
+
+

Einleitung

+ +

Um den Apache zu stoppen oder neu zu starten, müssen Sie + ein Signal an den laufenden httpd-Prozess senden. Es gibt + zwei Möglichkeiten, diese Signale zu senden. Zum einen können + Sie den Unix-Befehl kill verwenden, um den Prozessen + direkt Signale zu senden. Sie werden feststellen, dass auf Ihrem + System mehrere httpd-Programme laufen. Sie sollten + jedoch nicht jedem dieser Prozesse ein Signal senden, sondern nur dem + Elternprozess, dessen PID im PidFile steht. Das heißt, Sie + sollten es niemals nötig haben, einem anderen Prozess, als dem + Elternprozess, ein Signal zu senden. Es gibt drei Signale, die Sie an den + Elternprozess senden können: TERM, + HUP und + USR1, die nachfolgend beschrieben + werden.

+ +

Um dem Elternprozess ein Signal zu senden, verwenden Sie einen + Befehl wie z.B.:

+ +

kill -TERM `cat /usr/local/apache2/logs/httpd.pid`

+ +

Die zweite Methode, dem httpd-Prozess zu + signalisieren, ist die Verwendung der -k-Befehlszeilenoptionen + stop, restart, graceful und + graceful-stop, wie unten beschrieben. Dies sind Argumente des + httpd-Programms, es wird jedoch empfohlen, sie unter + Verwendung des Steuerskripts apachectl zu senden, + welches diese an httpd durchreicht.

+ +

Nachdem Sie httpd signalisiert haben, können Sie + dessen Fortschritt beobachten, indem Sie eingeben:

+ +

tail -f /usr/local/apache2/logs/error_log

+ +

Passen Sie diese Beispiele entsprechend Ihren ServerRoot- und PidFile-Einstellungen an.

+
top
+
+

Beenden

+ +
Signal: TERM
+
apachectl -k stop
+
+ +

Das Senden des TERM- oder stop-Signals an + den Elternprozess veranlasst diesen, sofort zu versuchen, alle seine + Kindprozesse zu beenden. Es kann einige Sekunden dauern, bis alle + Kindprozesse komplett beendet sind. Danach beendet sich der Elternprozess + selbst. Alle gerade bearbeiteten Anfragen werden abgebrochen. + Es werden keine weiteren Anfragen mehr bedient.

+
top
+
+

Unterbrechungsfreier Neustart

+ +
Signal: USR1
+
apachectl -k graceful
+
+ +

Das USR1- oder graceful-Signal + veranlasst den Elternprozess, die Kinder anzuweisen, sich + nach Abschluß ihrer momentanen bearbeiteten Anfrage zu beenden + (oder sich sofort zu beenden, wenn sie gerade keine Anfrage bedienen). + Der Elternprozess liest seine Konfigurationsdateien erneut ein und + öffnet seine Logdateien neu. Wenn ein Kindprozess stirbt, + ersetzt der Elternprozess ihn durch ein Kind der neuen + Konfigurations-Generation. Dieses beginnt sofort damit, + neue Anfragen zu bedienen.

+ +

Der Code ist dafür ausgelegt, stets die MPM-Direktiven + zur Prozesssteuerung zu beachten, so dass die Anzahl der Prozesse + und Threads, die zur Bedienung der Clients bereitstehen, während + des Neustarts auf die entsprechenden Werte gesetzt werden. + Weiterhin wird StartServers + auf folgende Art und Weise interpretiert: Wenn nach einer Sekunde + nicht mindestens StartServers + neue Kindprozesse erstellt wurden, dann werden, um den Durchsatz zu + beschleunigen, entsprechend weitere erstellt. Auf diese Weise versucht + der Code sowohl die Anzahl der Kinder entsprechend der Serverlast + anzupassen als auch Ihre Wünsche hinsichtlich des Parameters + StartServers zu + berücksichtigen.

+ +

Benutzer von mod_status werden feststellen, + dass die Serverstatistiken nicht auf Null + zurückgesetzt werden, wenn ein USR1 gesendet + wurde. Der Code wurde so geschrieben, dass sowohl die Zeit minimiert + wird, in der der Server nicht in der Lage ist, neue Anfragen zu + bedienen (diese werden vom Betriebssystem in eine Warteschlange + gestellt, so dass sie auf keinen Fall verloren gehen) als auch + Ihre Parameter zur Feinabstimmung berücksichtigt werden. + Um dies zu erreichen, muss die Statustabelle (Scoreboard), + die dazu verwendet wird, alle Kinder über mehrere Generationen + zu verfolgen, erhalten bleiben.

+ +

Das Statusmodul benutzt außerdem ein G, um + diejenigen Kinder zu kennzeichen, die noch immer Anfragen bedienen, + welche gestartet wurden, bevor ein unterbrechungsfreier Neustart + veranlaßt wurde.

+ +

Derzeit gibt es keine Möglichkeit für ein + Log-Rotationsskript, das USR1 verwendet, sicher + festzustellen, dass alle Kinder, die in ein vor dem Neustart + geöffnetes Log schreiben, beendet sind. Wir schlagen vor, dass + Sie nach dem Senden des Signals USR1 eine angemessene + Zeitspanne warten, bevor Sie das alte Log anfassen. Wenn beispielsweise + die meisten Ihrer Zugriffe bei Benutzern mit niedriger Bandbreite + weniger als 10 Minuten für eine vollständige Antwort + benötigen, dann könnten Sie 15 Minuten warten, bevor Sie auf + das alte Log zugreifen.

+ +
Wenn Ihre Konfigurationsdatei Fehler enthält, während + Sie einen Neustart anweisen, dann wird Ihr Elternprozess nicht neu starten, + sondern sich mit einem Fehler beenden. Im Falle eines unterbrechungsfreien + Neustarts läßt er die Kinder weiterlaufen, wenn er sich beendet. + (Dies sind die Kinder, die sich "sanft beenden", indem sie ihre letzte + Anfrage erledigen.) Das verursacht Probleme, wenn Sie versuchen, + den Server neu zu starten -- er ist nicht in der Lage, sich an die Ports zu + binden, an denen er lauschen soll. Bevor Sie einen Neustart + durchführen, können Sie die Syntax der Konfigurationsdateien + mit dem Befehlszeilenargument -t überprüfen + (siehe auch httpd). Das garantiert + allerdings nicht, dass der Server korrekt starten wird. Um sowohl die + Syntax als auch die Semantik der Konfigurationsdateien zu prüfen, + können Sie versuchen, httpd als nicht-root-Benutzer + zu starten. Wenn dabei keine Fehler auftreten, wird er versuchen, seine + Sockets und Logdateien zu öffnen und fehlschlagen, da er nicht root + ist (oder weil sich der gegenwärtig laufende httpd + bereits diese Ports gebunden hat). Wenn er aus einem anderen Grund + fehlschlägt, dann liegt wahrscheinlich ein Konfigurationsfehler vor. + Der Fehler sollte behoben werden, bevor der unterbrechungsfreie Neustart + angewiesen wird.
+
top
+
+

Neustarten

+ +
Signal: HUP
+
apachectl -k restart
+
+ +

Das Senden des Signals HUP oder restart + veranlaßt den Elternprozess, wie bei TERM alle seine + Kinder zu beenden. Der Elternprozess beendet sich jedoch nicht. Er liest + seine Konfigurationsdateien neu ein und öffnet alle Logdateien + erneut. Dann erzeugt er einen neuen Satz Kindprozesse und setzt die + Bedienung von Zugriffen fort.

+ +

Benutzer von mod_status werden feststellen, dass + die Serverstatistiken auf Null gesetzt werden, wenn ein HUP + gesendet wurde.

+ +
Wenn Ihre Konfigurationsdatei einen Fehler enthält, + während Sie einen Neustart anweisen, dann wird Ihr Elternprozess + nicht neu starten, sondern sich mit einem Fehler beenden. Lesen Sie oben, + wie Sie das vermeiden können.
+
top
+
+

Rücksichtsvolles Beenden

+ +
+
Signal: WINCH
+
apachectl -k gracefull stop
+
+ +

Das WINCH- oder graceful-stop-Signal + veranlasst den Elternprozess, die Kinder anzuweisen, sich nach + Abschluß ihrer momentan bearbeiteten Anfrage zu beenden (oder sich + sofort zu beenden, wenn sie gerade nichts bedienen). Der Elternprozess + entfernt dann sein PidFile und + stellt das Lauschen auf allen Ports ein. Er läuft weiter und + beobachtet alle Kindprozesse, die noch Anfragen bearbeiten. Sobald alle + Kindprozesse fertig sind und beendet haben oder die mit GracefulShutdownTimeout definierte + Zeitüberschreitung erreicht wurde, beendet sich der Elternprozess + ebenfalls. Jedem verbliebenen Kindprozess wird beim Erreichen der + Zeitüberschreitung das TERM-Signal gesendet, um diesen + zum Beenden zu zwingen.

+ +

Ein TERM-Signal beendet den Elternprozess und alle + Kindprozesse unverzüglich, wenn sie sich im "graceful"-Status + (Anm.d.Ü.: wörtl. "gnädiger" Status) befinden. Da jedoch das + PidFiledann schon gelöscht + ist, werden Sie dieses Signal nicht mehr mit apachectl oder + httpd senden können.

+ +

Das Signal graceful-stop ermöglicht Ihnen den + Betrieb mehrerer identisch konfigurierter Instanzen von httpd + zur gleichen Zeit. Dies ist eine mächtige Funktionalität bei der + Aufrüstung des Apache. Sie kann jedoch bei einigen Konfigurationen + auch zur gegenseitigen Blockierung und zu Wettlaufsituationen + führen.

+ +

Es ist besonders darauf zu achten, dass auf Festplatte gespeicherte + Dateien wie Lockfile und ScriptSock die Server-PID enthalten und ohne + Probleme nebeneinander existieren müssen. Wann auch immer eine + Konfigurationsanweisung, ein Drittanbieter-Modul oder ein persistentes + CGI-Skript irgend eine Sperre oder eine Statusdatei auf Festplatte + speichert, muss besonders darauf geachtet werden, dass mehrere + gleichzeitig laufende Instanzen von httpd sich nicht + gegenseitig die Dateien zerstören.

+ +

Sie sollten ebenfalls vorsichtig mit möglichen Wettlaufsituationen + sein, wie beispielsweise der Verwendung von weitergeleiteter + Protokollierung nach der Art von rotatelogs. Mehrere + gleichzeitig laufende Instanzen von rotatelogs, die + versuchen, die gleichen Protokolldateien zu rotieren, können sich + gegenseitig die Protokolldateien zerstören.

+ +
top
+
+

Anhang: Signale und Wettlaufsituationen

+ +

Vor der Version 1.2b9 des Apache existierten verschiedene + Wettlaufsituationen (Anm.d.Ü.: engl.: race + conditions), die den Neustart und die Signale beeinflußt + haben (einfach gesagt, eine Wettlaufstituation ist ein zeitabhängiges + Problem - wenn etwas zum falschen Zeitpunkt oder in der falschen + Reihenfolge geschieht, kommt es zu nicht erwünschten Ergebnissen. + Geschehen die gleichen Dinge zur rechten Zeit, ist alles in Ordnung). Bei + Architekturen mit dem "richtigen" (Anm.d.Ü.: im Sinne von + "geeignet") Funktionsumfang haben wir so viele eliminiert wie + wir nur konnten. Dennoch sollte beachtet werden, dass noch immer + Wettlaufsituationen auf bestimmten Architekturen existieren.

+ +

Bei Architekturen, die ein ScoreBoardFile auf Platte verwenden, + kann die Statustabelle beschädigt werden. + Das kann zu "bind: Address already in use" ("bind: Adresse wird + bereits verwendet", nach einem HUP) oder "long lost + child came home!" ("Der verlorene Sohn ist heimgekehrt", nach einem + USR1) führen. Ersteres ist ein schwerer Fehler, + wärend letzteres lediglich bewirkt, dass der Server einen Eintrag + in der Statustabelle verliert. So kann es ratsam sein, unterbrechungsfreie + Neustarts zusammen mit einem gelegentlichen harten Neustart zu verwenden. + Diese Probleme lassen sich nur sehr schwer umgehen, aber + glücklicherweise benötigen die meisten Architekturen keine + Statustabelle in Form einer Datei. Bitte lesen Sie für Architekturen, + die sie benötigen, die Dokumentation zu ScoreBoardFile.

+ +

Alle Architekturen haben in jedem Kindprozess eine kleine + Wettlaufsituation, welche die zweite und nachfolgende Anfragen + einer persistenten HTTP-Verbindung (KeepAlive) umfaßt. Der Prozess + kann nach dem Lesen der Anfragezeile aber vor dem Lesen der Anfrage-Header + enden. Es existiert eine Korrektur, die für 1.2 zu spät kam. + Theoretisch sollte das kein Problem darstellen, da + der KeepAlive-Client derartige Ereignisse aufgrund von + Netzwerk-Latenzzeiten und Auszeiten des Servers erwarten sollte. + In der Praxis scheint keiner von beiden beeinflußt zu werden + -- in einem Testfall wurde der Server zwanzig mal + pro Sekunde neu gestartet, während Clients das Angebot abgegrast + haben, ohne kaputte Bilder oder leere Dokumente zu erhalten.

+
+
+

Verfügbare Sprachen:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/stopping.html.en b/docs/manual/stopping.html.en new file mode 100644 index 00000000..f4f95337 --- /dev/null +++ b/docs/manual/stopping.html.en @@ -0,0 +1,233 @@ + + + +Stopping and Restarting - Apache HTTP Server + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Stopping and Restarting

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ +

This document covers stopping and restarting Apache on + Unix-like systems. Windows NT, 2000 and XP users should see + Running Apache as a + Service and Windows 9x and ME users should see Running Apache as a + Console Application for information on how to control + Apache on those platforms.

+
+ +
top
+
+

Introduction

+ +

In order to stop or restart Apache, you must send a signal to + the running httpd processes. There are two ways to + send the signals. First, you can use the unix kill + command to directly send signals to the processes. You will + notice many httpd executables running on your system, + but you should not send signals to any of them except the parent, + whose pid is in the PidFile. That is to say you + shouldn't ever need to send signals to any process except the + parent. There are four signals that you can send the parent: + TERM, + USR1, + HUP, and + WINCH, which + will be described in a moment.

+ +

To send a signal to the parent you should issue a command + such as:

+ +

kill -TERM `cat /usr/local/apache2/logs/httpd.pid`

+ +

The second method of signaling the httpd processes + is to use the -k command line options: stop, + restart, graceful and graceful-stop, + as described below. These are arguments to the httpd binary, but we recommend that + you send them using the apachectl control script, which + will pass them through to httpd.

+ +

After you have signaled httpd, you can read about + its progress by issuing:

+ +

tail -f /usr/local/apache2/logs/error_log

+ +

Modify those examples to match your ServerRoot and PidFile settings.

+
top
+
+

Stop Now

+ +
Signal: TERM
+
apachectl -k stop
+
+ +

Sending the TERM or stop signal to + the parent causes it to immediately attempt to kill off all of its + children. It may take it several seconds to complete killing off + its children. Then the parent itself exits. Any requests in + progress are terminated, and no further requests are served.

+
top
+
+

Graceful Restart

+ +
Signal: USR1
+
apachectl -k graceful
+
+ +

The USR1 or graceful signal causes + the parent process to advise the children to exit after + their current request (or to exit immediately if they're not + serving anything). The parent re-reads its configuration files and + re-opens its log files. As each child dies off the parent replaces + it with a child from the new generation of the + configuration, which begins serving new requests immediately.

+ +

This code is designed to always respect the process control + directive of the MPMs, so the number of processes and threads + available to serve clients will be maintained at the appropriate + values throughout the restart process. Furthermore, it respects + StartServers in the + following manner: if after one second at least StartServers new children have not + been created, then create enough to pick up the slack. Hence the + code tries to maintain both the number of children appropriate for + the current load on the server, and respect your wishes with the + StartServers + parameter.

+ +

Users of mod_status + will notice that the server statistics are not + set to zero when a USR1 is sent. The code was + written to both minimize the time in which the server is unable + to serve new requests (they will be queued up by the operating + system, so they're not lost in any event) and to respect your + tuning parameters. In order to do this it has to keep the + scoreboard used to keep track of all children across + generations.

+ +

The status module will also use a G to indicate + those children which are still serving requests started before + the graceful restart was given.

+ +

At present there is no way for a log rotation script using + USR1 to know for certain that all children writing + the pre-restart log have finished. We suggest that you use a + suitable delay after sending the USR1 signal + before you do anything with the old log. For example if most of + your hits take less than 10 minutes to complete for users on + low bandwidth links then you could wait 15 minutes before doing + anything with the old log.

+ +
If your configuration file has errors + in it when you issue a restart then your parent will not + restart, it will exit with an error. In the case of graceful + restarts it will also leave children running when it exits. + (These are the children which are "gracefully exiting" by + handling their last request.) This will cause problems if you + attempt to restart the server -- it will not be able to bind to + its listening ports. Before doing a restart, you can check the + syntax of the configuration files with the -t + command line argument (see httpd). This still will not + guarantee that the server will restart correctly. To check the + semantics of the configuration files as well as the syntax, you + can try starting httpd as a non-root user. If there + are no errors it will attempt to open its sockets and logs and fail + because it's not root (or because the currently running + httpd already has those ports bound). If it fails + for any other reason then it's probably a config file error and the error + should be fixed before issuing the graceful restart.
+
top
+
+

Restart Now

+ +
Signal: HUP
+
apachectl -k restart
+
+ +

Sending the HUP or restart signal to + the parent causes it to kill off its children like in + TERM, but the parent doesn't exit. It re-reads its + configuration files, and re-opens any log files. Then it spawns a + new set of children and continues serving hits.

+ +

Users of mod_status + will notice that the server statistics are set to zero when a + HUP is sent.

+ +
If your configuration file has errors in it when you issue a +restart then your parent will not restart, it will exit with an +error. See above for a method of avoiding this.
+
top
+
+

Graceful Stop

+ +
Signal: WINCH
+
apachectl -k graceful-stop
+
+ +

The WINCH or graceful-stop signal causes + the parent process to advise the children to exit after + their current request (or to exit immediately if they're not + serving anything). The parent will then remove its PidFile and cease listening on + all ports. The parent will continue to run, and monitor children + which are handling requests. Once all children have finalised + and exited or the timeout specified by the GracefulShutdownTimeout has been + reached, the parent will also exit. If the timeout is reached, + any remaining children will be sent the TERM signal + to force them to exit.

+ +

A TERM signal will immediately terminate the + parent process and all children when in the "graceful" state. However + as the PidFile will + have been removed, you will not be able to use + apachectl or httpd to send this signal.

+ +

The graceful-stop signal allows you to run multiple + identically configured instances of httpd at the + same time. This is a powerful feature when performing graceful + upgrades of Apache, however it can also cause deadlocks and race + conditions with some configurations.

+ +

Care has been taken to ensure that on-disk files + such as the Lockfile and ScriptSock files contain the server + PID, and should coexist without problem. However, if a configuration + directive, third-party module or persistent CGI utilises any other on-disk + lock or state files, care should be taken to ensure that multiple running + instances of httpd do not clobber each others files.

+ +

You should also be wary of other potential race conditions, such as + using rotatelogs style piped logging. Multiple running + instances of rotatelogs attempting to rotate the same + logfiles at the same time may destroy each other's logfiles.

+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/stopping.html.es b/docs/manual/stopping.html.es new file mode 100644 index 00000000..c066eec1 --- /dev/null +++ b/docs/manual/stopping.html.es @@ -0,0 +1,267 @@ + + + +Iniciar y Parar el servidor Apache - Servidor HTTP Apache + + + + +
+

Módulos | Directivas | Preguntas Frecuentes | Glosario | Mapa de este sitio web

+

Versión 2.2 del Servidor HTTP Apache

+
+
<-
+
+Apache > Servidor HTTP > Documentación > Versión 2.2

Iniciar y Parar el servidor Apache

+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko 

+
+
Esta traducción podría estar + obsoleta. Consulte la versión en inglés de la + documentación para comprobar si se han producido cambios + recientemente.
+ +

Este documento explica como iniciar y parar el servidor Apache + en sistemas tipo Unix. Los usuarios de Windows NT, 2000 y XP + deben consultar la sección Ejecutar Apache como un + servicio y los usuario de Windows 9x y ME deben consultar Ejecutar Apache como una + Aplicación de Consola para obtener información + sobre como controlar Apache en esas plataformas.

+
+ +
top
+
+

Introducción

+ +

Para parar y reiniciar Apache, hay que enviar la señal + apropiada al proceso padre httpd que se esté + ejecutando. Hay dos maneras de enviar estas señales. En + primer lugar, puede usar el comando de Unix kill que + envía señales directamente a los procesos. Puede que + tenga varios procesos httpd ejecutandose en su + sistema, pero las señales deben enviarse solamente al proceso + padre, cuyo pid está especificado en la directiva PidFile. Esto quiere decir que no + debe necesitar enviar señales a ningún proceso excepto + al proceso padre. Hay tres señales que puede enviar al + proceso padre: TERM, HUP, y USR1, que van a ser descritas a + continuación.

+ +

Para enviar una señal al proceso padre debe escribir un + comando como el que se muestra en el ejemplo:

+ +

kill -TERM `cat /usr/local/apache2/logs/httpd.pid`

+ +

La segunda manera de enviar señales a los procesos + httpd es usando las opciones de línea de + comandos -k: stop, restart, + y graceful, como se muestra más abajo. Estas + opciones se le pueden pasar al binario httpd, pero se recomienda que se + pasen al script de control apachectl, que a su vez los + pasará a httpd.

+ +

Después de haber enviado las señales que desee a + httpd, puede ver como progresa el proceso + escribiendo:

+ +

tail -f /usr/local/apache2/logs/error_log

+ +

Modifique estos ejemplos para que coincidan con la + configuración que tenga especificada en las directivas + ServerRoot y PidFile en su fichero principal de + configuración.

+
top
+
+

Parar Apache

+ +
Señal: TERM
+
apachectl -k stop
+
+ +

Enviar las señales TERM o stop + al proceso padre hace que se intenten eliminar todos los procesos + hijo inmediatamente. Esto puede tardar algunos minutos. Una vez + que hayan terminado todos los procesos hijo, terminará el + proceso padre. Cualquier petición en proceso terminará + inmediatanmente, y ninguna petición posterior será + atendida.

+
top
+
+

Reinicio Graceful

+ +
Señal: USR1
+
apachectl -k graceful
+
+ +

Las señales USR1 o graceful + hacen que el proceso padre indique a sus hijos que + terminen después de servir la petición que estén + atendiendo en ese momento (o de inmediato si no están + sirviendo ninguna petición). El proceso padre lee de nuevo + sus ficheros de configuración y vuelve a abrir sus ficheros + log. Conforme cada hijo va terminando, el proceso padre lo va + sustituyendo con un hijo de una nueva generación con + la nueva configuración, que empeciezan a servir peticiones + inmediatamente.

+ +
En algunas plataformas que no permiten usar + USR1 para reinicios graceful, puede usarse una + señal alternativa (como WINCH). Tambien puede + usar apachectl graceful y el script de control + enviará la señal adecuada para su plataforma.
+ +

Apache está diseñado para respetar en todo momento la + directiva de control de procesos de los MPM, así como para + que el número de procesos y hebras disponibles para servir a + los clientes se mantenga en los valores adecuados durante el + proceso de reinicio. Aún más, está diseñado + para respetar la directiva StartServers de la siguiente + manera: si después de al menos un segundo el nuevo hijo de la + directiva StartServers + no ha sido creado, entonces crea los suficientes para se atienda + el trabajo que queda por hacer. Así, se intenta mantener + tanto el número de hijos adecuado para el trabajo que el + servidor tenga en ese momento, como respetar la configuración + determinada por los parámetros de la directiva + StartServers.

+ +

Los usuarios del módulo mod_status + notarán que las estadísticas del servidor + no se ponen a cero cuando se usa la señal + USR1. Apache fue escrito tanto para minimizar el + tiempo en el que el servidor no puede servir nuevas peticiones + (que se pondrán en cola por el sistema operativo, de modo que + se no se pierda ningún evento), como para respetar sus + parámetros de ajuste. Para hacer esto, tiene que guardar el + scoreboard usado para llevar el registro de los procesos + hijo a través de las distintas generaciones.

+ +

El mod_status también usa una G para indicar + que esos hijos están todavía sirviendo peticiones + previas al reinicio graceful.

+ +

Actualmente no existe ninguna manera de que un script con un + log de rotación usando USR1 sepa con seguridad + que todos los hijos que se registraron en el log con anterioridad + al reinicio han terminado. Se aconseja que se use un retardo + adecuado después de enviar la señal USR1 + antes de hacer nada con el log antiguo. Por ejemplo, si la mayor + parte las visitas que recibe de usuarios que tienen conexiones de + baja velocidad tardan menos de 10 minutos en completarse, entoces + espere 15 minutos antes de hacer nada con el log antiguo.

+ +
Si su fichero de configuración tiene errores cuando + haga el reinicio, entonces el proceso padre no se reinciciará + y terminará con un error. En caso de un reinicio graceful, + también dejará a los procesos hijo ejecutandose mientras + existan. (Estos son los hijos de los que se está saliendo de + forma graceful y que están sirviendo sus últimas + peticiones.) Esto provocará problemas si intenta reiniciar el + servidor -- no será posible conectarse a la lista de puertos + de escucha. Antes de reiniciar, puede comprobar que la sintaxis de + sus ficheros de configuracion es correcta con la opción de + línea de comandos -t (consulte httpd). No obstante, esto no + garantiza que el servidor se reinicie correctamente. Para + comprobar que no hay errores en los ficheros de + configuración, puede intentar iniciar httpd con + un usuario diferente a root. Si no hay errores, intentará + abrir sus sockets y logs y fallará porque el usuario no es + root (o porque el httpd que se está ejecutando + en ese momento ya está conectado a esos puertos). Si falla + por cualquier otra razón, entonces casi seguro que hay + algún error en alguno de los ficheros de configuración y + debe corregir ese o esos errores antes de hacer un reinicio + graceful.
+
top
+
+

Reiniciar Apache

+ +
Señal: HUP
+
apachectl -k restart
+
+ +

El envío de las señales HUP o + restart al proceso padre hace que los procesos hijo + terminen como si le enviá ramos la señal + TERM, para eliminar el proceso padre. La diferencia + está en que estas señales vuelven a leer los archivos de + configuración y vuelven a abrir los ficheros log. Se genera + un nuevo conjunto de hijos y se continúa sirviendo + peticiones.

+ +

Los usuarios del módulo mod_status + notarán que las estadísticas del servidor se ponen a + cero cuando se envía la señal HUP.

+ +
Si su fichero de configuración contiene errores, cuando +intente reiniciar, el proceso padre del servidor no se +reiniciará, sino que terminará con un error. Consulte +más arriba cómo puede solucionar este problema.
+
top
+
+

Apéndice: señales y race conditions

+ +

Con anterioridad a la versión de Apache 1.2b9 había + varias race conditions implicadas en las señales + para parar y reiniciar procesos (una descripción sencilla de + una race condition es: un problema relacionado con el momento en + que suceden las cosas, como si algo sucediera en momento en que no + debe, y entonces el resultado esperado no se corresponde con el + obtenido). Para aquellas arquitecturas que tienen el conjunto de + características "adecuadas", se han eliminado tantas race + conditions como ha sido posible. Pero hay que tener en cuenta que + todavía existen race conditions en algunas arquitecturas.

+ +

En las arquitecturas que usan un ScoreBoardFile en disco, existe la + posibilidad de que se corrompan los scoreboards. Esto puede hacer + que se produzca el error "bind: Address already in use" + (después de usarHUP) o el error "long lost child + came home!" (después de usar USR1). En el + primer caso se trata de un error irrecuperable, mientras que en el + segundo, solo ocurre que el servidor pierde un slot del + scoreboard. Por lo tanto, sería aconsejable usar reinicios + graceful, y solo hacer reinicios normales de forma + ocasional. Estos problemas son bastante complicados de solucionar, + pero afortunadamente casi ninguna arquitectura necesita un fichero + scoreboard. Consulte la documentación de la directiva + ScoreBoardFile para ver + las arquitecturas que la usan.

+ +

Todas las arquitecturas tienen una pequeña race condition + en cada proceso hijo implicada en la segunda y subsiguientes + peticiones en una conexión HTTP persistente + (KeepAlive). Puede ser que el servidor termine después de + leer la línea de petición pero antes de leer cualquiera + de las cebeceras de petición. Hay una solución que fue + descubierta demasiado tarde para la incluirla en versión + 1.2. En teoria esto no debe suponer ningún problema porque el + cliente KeepAlive ha de esperar que estas cosas pasen debido a los + retardos de red y a los timeouts que a veces dan los + servidores. En la practica, parece que no afecta a nada más + -- en una sesión de pruebas, un servidor se reinició + veinte veces por segundo y los clientes pudieron navegar sin + problemas por el sitio web sin encontrar problemas ni para + descargar una sola imagen ni encontrar un solo enlace roto.

+
+
+

Idiomas disponibles:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/stopping.html.ja.euc-jp b/docs/manual/stopping.html.ja.euc-jp new file mode 100644 index 00000000..1cdc51c9 --- /dev/null +++ b/docs/manual/stopping.html.ja.euc-jp @@ -0,0 +1,256 @@ + + + +Ää»ß¤ÈºÆµ¯Æ° - Apache HTTP ¥µ¡¼¥Ð + + + + +
+

¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

+

Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

+
+
<-
+
+Apache > HTTP ¥µ¡¼¥Ð > ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó > ¥Ð¡¼¥¸¥ç¥ó 2.2

Ää»ß¤ÈºÆµ¯Æ°

+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+
This translation may be out of date. Check the + English version for recent changes.
+ +

¤³¤Îʸ½ñ¤Ç¤Ï Unix ¤ËÎà»÷¤·¤¿¥·¥¹¥Æ¥à¤Ç¤Î + Apache ¤ÎÄä»ß¤ÈºÆµ¯Æ°¤Ë¤Ä¤¤¤Æ°·¤Ã¤Æ¤¤¤Þ¤¹¡£ + Windows NT, 2000, XP ¥æ¡¼¥¶¤Ï¥µ¡¼¥Ó¥¹¤È¤·¤Æ + Apache ¤ò¼Â¹Ô¤¹¤ë¤Ç¡¢Windows 9x, ME¥æ¡¼¥¶¤Ï¥³¥ó¥½¡¼¥ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤È¤·¤Æ + Apache ¤ò¼Â¹Ô¤¹¤ë¤Ç¡¢ + ¤³¤ì¤é¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤Î»ÈÍÑÊýË¡¤ò¤´Í÷²¼¤µ¤¤¡£

+
+ +
top
+
+

¥¤¥ó¥È¥í¥À¥¯¥·¥ç¥ó

+ +

Apache ¤òÄä»ß¤·¤¿¤êºÆµ¯Æ°¤·¤¿¤ê¤¹¤ë¤¿¤á¤Ë¤Ï¡¢¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë + httpd ¥×¥í¥»¥¹¤Ë¥·¥°¥Ê¥ë¤òÁ÷¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¥·¥°¥Ê¥ë¤òÁ÷¤ë¤Ë¤ÏÆó¤Ä¤ÎÊýË¡¤¬¤¢¤ê¤Þ¤¹¡£ + °ì¤ÄÌÜ¤Ï¥×¥í¥»¥¹¤ËľÀÜ¥·¥°¥Ê¥ë¤òÁ÷¤ë unix ¤Î kill + ¥³¥Þ¥ó¥É¤ò»ÈÍѤ¹¤ëÊýË¡¤Ç¤¹¡£ + ¥·¥¹¥Æ¥à¤ò¸«¤ì¤Ð¤¿¤¯¤µ¤ó¤Î httpd ¤¬ + ¼Â¹Ô¤µ¤ì¤Æ¤¤¤ë¤Î¤Ëµ¤¤¬ÉÕ¤¯¤Ç¤·¤ç¤¦¤¬¡¢¥·¥°¥Ê¥ë¤òÁ÷¤ë¤Î¤Ï + ¿Æ¥×¥í¥»¥¹¤À¤±¤Ç¡¢¤½¤ì°Ê³°¤Î¸Ä¡¹¤Î¥×¥í¥»¥¹¤Ë¤Ï + ¥·¥°¥Ê¥ë¤òÁ÷¤é¤Ê¤¤¤Ç²¼¤µ¤¤¡£¤½¤Î¿Æ¥×¥í¥»¥¹¤Î pid ¤Ï + PidFile + ¤Ë½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ï¤Ä¤Þ¤ê¡¢¿Æ°Ê³°¤Î¥×¥í¥»¥¹¤Ë + ¥·¥°¥Ê¥ë¤òÁ÷¤ëɬÍפ¹¤é¤Ê¤¤¡¢¤È¤¤¤¦¤³¤È¤Ç¤¹¡£ + ¿Æ¥×¥í¥»¥¹¤ËÁ÷¤ë¤³¤È¤¬¤Ç¤­¤ë 3 ¼ïÎà¤Î¥·¥°¥Ê¥ë¤¬¤¢¤ê¤Þ¤¹: + TERM, + HUP, + USR1 + ¤Ç¤¹¡£¤³¤ì¤é¤ÎÀâÌÀ¤Ë¤Ä¤¤¤Æ¤Ï³¤­¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

¿Æ¥×¥í¥»¥¹¤Ë¥·¥°¥Ê¥ë¤òÁ÷¤ë¤Ë¤Ï¡¢ + ¼¡¤Î¤è¤¦¤Ê¥³¥Þ¥ó¥É¤òȯ¹Ô¤·¤Æ²¼¤µ¤¤:

+ +

kill -TERM `cat /usr/local/apache2/logs/httpd.pid`

+ +

httpd ¥×¥í¥»¥¹¤Ë¥·¥°¥Ê¥ë¤òÁ÷¤ë 2 ÈÖÌܤÎÊýË¡¤Ï + -k ¤È¤¤¤¦¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¿ô¤ò»ÈÍѤ¹¤ë¤³¤È¤Ç¤¹¡£ + ²¼¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¡¢stop, restart, + graceful ¤ò»ØÄê¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤é¤Ï httpd ¤Î°ú¿ô¤Ç¤¹¤¬¡¢ + À©¸æÍѤΥ¹¥¯¥ê¥×¥È apachectl ¤Ï¤½¤ì¤é¤Î°ú¿ô¤ò¤½¤Î¤Þ¤Þ + httpd ¤ËÅϤ·¤Þ¤¹¡£

+ +

httpd ¤Ë¥·¥°¥Ê¥ë¤òÁ÷¤Ã¤¿¸å¡¢ + ¼Â¹Ô¾õ¶·¤ò¼¡¤Î¥³¥Þ¥ó¥É¤ÇÆɤळ¤È¤¬¤Ç¤­¤Þ¤¹:

+ +

tail -f /usr/local/apache2/logs/error_log

+

¤³¤³¤Ëµó¤²¤¿Îã¤Ï¡¢³Æ¼«¤Î + ServerRoot + ¤È + PidFile + ¤ÎÀßÄê¤ËŬ¹ç¤¹¤ë¤è¤¦¤ËŬµ¹½¤Àµ¤·¤Æ²¼¤µ¤¤¡£

+
top
+
+

µÞ¤ÊÄä»ß

+ +
¥·¥°¥Ê¥ë: TERM
+
apachectl -k stop
+
+ +

TERM ¤¢¤ë¤¤¤Ï stop + ¥·¥°¥Ê¥ë¤ò¿Æ¥×¥í¥»¥¹¤ËÁ÷¤ë¤È¡¢Â¨ºÂ¤Ë»Ò¥×¥í¥»¥¹Á´¤Æ¤ò kill ¤·¤è¤¦¤È¤·¤Þ¤¹¡£ + »Ò¥×¥í¥»¥¹¤ò´°Á´¤Ë kill ¤·½ª¤ï¤ë¤Þ¤Ç¤Ë¿ôÉ䫤«¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¤½¤Î¸å¡¢¿Æ¥×¥í¥»¥¹¼«¿È¤¬½ªÎ»¤·¤Þ¤¹¡£ + ½èÍýÃæ¤Î¥ê¥¯¥¨¥¹¥È¤ÏÁ´¤ÆÄä»ß¤µ¤ì¡¢¤â¤Ï¤ä¥ê¥¯¥¨¥¹¥È¤ËÂФ¹¤ë + ±þÅú¤Ï¤µ¤ì¤Þ¤»¤ó¡£

+
top
+
+

´Ë¤ä¤«¤ÊºÆµ¯Æ°

+ +
¥·¥°¥Ê¥ë: USR1
+
apachectl -k graceful
+
+ +

¿Æ¥×¥í¥»¥¹¤Ï USR1 ¤¢¤ë¤¤¤Ï graceful + ¥·¥°¥Ê¥ë¤ò¼õ¤±¼è¤ë¤È¡¢»Ò¥×¥í¥»¥¹¤Ë¸½ºß¤Î¥ê¥¯¥¨¥¹¥È¤Î½èÍý¤Î¸å¤Ë½ªÎ»¤¹¤ë + (¤¢¤ë¤¤¤Ï²¿¤â¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¤¹¤°¤Ë½ªÎ»¤¹¤ë) + ¤è¤¦¤Ë½õ¸À¤·¤Þ¤¹¡£ + ¿Æ¥×¥í¥»¥¹¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤òºÆÆɹþ¤·¤Æ¡¢¥í¥°¥Õ¥¡¥¤¥ë¤ò³«¤­Ä¾¤·¤Þ¤¹¡£ + »Ò¥×¥í¥»¥¹¤¬½ù¡¹¤Ë¤Ê¤¯¤Ê¤ë¤Ë½¾¤Ã¤Æ¡¢ + ¿·¤·¤¤À¤Âå¤ÎÀßÄê¤Ë¤è¤ë»Ò¥×¥í¥»¥¹¤ËÃÖ¤­´¹¤¨¤Æ¤¤¤­¤Þ¤¹¡£ + ¤½¤·¤Æ¡¢¤³¤ì¤é¤¬¿·¤¿¤Ê¥ê¥¯¥¨¥¹¥È¤Ë¨ºÂ¤Ë±þÅú¤·»Ï¤á¤Þ¤¹¡£

+ +
ÆÃÄê¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤Ï USR1 + ¤ò´Ë¤ä¤«¤ÊºÆµ¯Æ°¤Î¤¿¤á¤Ë»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó¤¬¡¢Âå¤ï¤ê¤Î¥·¥°¥Ê¥ë + (Î㤨¤Ð WINCH) ¤¬»ÈÍѤǤ­¤ë¤Ç¤·¤ç¤¦¡£ + apachectl graceful + ¤È¤¤¤¦¥³¥Þ¥ó¥É¤Ï¥×¥é¥Ã¥È¥Û¡¼¥à¤Ë¹ç¤Ã¤¿¥·¥°¥Ê¥ë¤òÁ÷¤ê¤Þ¤¹¡£
+ +

¤³¤Î¥³¡¼¥É¤Ï¾ï¤Ë + MPM ¤Î¥×¥í¥»¥¹À©¸æ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀßÄê¤ò½Å»ë¤·¤Þ¤¹¤Î¤Ç¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤Î¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¥×¥í¥»¥¹¤È¥¹¥ì¥Ã¥É¤Î¿ô¤òºÆµ¯Æ°¤Î½èÍýÃæ¤â + ŬÀÚ¤ÊÃͤ˰ݻý¤µ¤ì¤Þ¤¹¡£¡£¤Þ¤¿¡¢¼¡¤Î¤è¤¦¤Ë¤·¤Æ + StartServers + ¤ò¼é¤ê¤Þ¤¹: + ¾¯¤Ê¤¯¤È¤â 1 Éøå¤Ë StartServers ¸Ä¤Î¿·¤·¤¤»Ò¥×¥í¥»¥¹¤¬ + À¸À®¤µ¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢¤½¤Î¿ô¤Ë¤Ê¤ë¤è¤¦¤ËŬµ¹¥×¥í¥»¥¹¤òÀ¸À®¤·¤Þ¤¹¡£ + ¤³¤ÎµóÆ°¤Ï¸½ºß¤ÎÉé²Ù¤ËÂФ·¤ÆŬÀÚ¤Ê»Ò¥×¥í¥»¥¹¤Î¿ô¤È + StartServers ¥Ñ¥é¥á¡¼¥¿¤Ç¤Î + ´õ˾¤Î¿ô¤ÎξÊý¤ò°Ý»ý¤·¤è¤¦¤È¤·¤Æ¤¤¤Þ¤¹¡£

+ +

mod_status ¤ò + »ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢USR1 ¥·¥°¥Ê¥ë¤¬Á÷¤é¤ì¤¿ºÝ¤Ë + ¥µ¡¼¥ÐÅý·×¤¬¥¼¥í¤ËÀßÄꤵ¤ì¤Ê¤¤¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¥µ¡¼¥Ð¤¬¿·¤·¤¤¥ê¥¯¥¨¥¹¥È¤Ë±þÅúÉÔǽ¤Ê»þ´Ö¤òºÇ¾®¤Ë¤¹¤ë¤è¤¦¤Ë + (¥ê¥¯¥¨¥¹¥È¤Ï OS ¤Ë¤è¤Ã¤Æ¥­¥å¡¼¤ËÄɲ䵤ì¤ë¤Î¤ÇÀäÂФËʶ¼º¤Ï¤·¤Þ¤»¤ó)¡¢ + ¤Þ¤¿Æ±»þ¤Ë¡¢´õ˾¤Î¥Á¥å¡¼¥Ë¥ó¥°¥Ñ¥é¥á¡¼¥¿¤ò¼é¤ë¤è¤¦¤Ë + ¥³¡¼¥É¤Ï½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¡¢À¤Âå¤ò¤Þ¤¿¤¬¤Ã¤¿Á´»Ò¥×¥í¥»¥¹¤ÎÄÉÀפ˻Ȥï¤ì¤Æ¤¤¤ë + ¥¹¥³¥¢¥Ü¡¼¥É¤ò°Ý»ý¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

+ +

status ¥â¥¸¥å¡¼¥ë¤Ï¡¢´Ë¤ä¤«¤ÊºÆµ¯Æ°°ÊÁ°¤«¤é³«»Ï¤·¤Æ + ¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤·Â³¤±¤Æ¤¤¤ë»Ò¥×¥í¥»¥¹¤òÆÃÄꤹ¤ë¤¿¤á¤Ë¡¢ + G ¤ò»È¤¦¤³¤È¤â¤·¤Þ¤¹¡£

+ +

¸½ºß¡¢USR1 ¤ò»È¤¦¥í¥°°ÜÆ°¥¹¥¯¥ê¥×¥È¤Ç¤Ï¡¢ + ºÆµ¯Æ°Á°¤Î»Ò¥×¥í¥»¥¹¤¬¥í¥°¤ò½ñ¤­½ª¤ï¤Ã¤¿¤³¤È¤ò³Î¾Ú¤¹¤ëÊýË¡¤¬ + ¤¢¤ê¤Þ¤»¤ó¡£¸Å¤¤¥í¥°¤ËÂФ·¤Æ²¿¤«¤¹¤ëÁ°¤Ë¡¢ + USR1 ¥·¥°¥Ê¥ë¤òÁ÷¤Ã¤¿¸å¤¤¤¯¤é¤«Å¬Åö¤Ê»þ´ÖÂԤĤ³¤È¤ò + Äó°Æ¤·¤Þ¤¹¡£Î㤨¤Ð¡¢ÂÓ°è¤Î¶¹¤¤ÄÌ¿®Ï©¤Î¥æ¡¼¥¶¤Î¥ê¥¯¥¨¥¹¥È¤Î¤Û¤È¤ó¤É¤¬ 10 + ʬ°Ê²¼¤Ç´°Î»¤·¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È¤¬Ê¬¤«¤Ã¤Æ¤¤¤ì¤Ð¡¢ + ¸Å¤¤¥í¥°¤Ë²¿¤«¤¹¤ëÁ°¤Ë 15 ʬÂԤĤȤ¤¤¦¤³¤È¤Ç¤¹¡£

+ +
ºÆµ¯Æ°»þ¤ËÀßÄê¥Õ¥¡¥¤¥ë¤Ë¸í¤ê¤¬¤¢¤ë¤È¡¢ + ¿Æ¥×¥í¥»¥¹¤ÏºÆµ¯Æ°¤»¤º¤Ë¥¨¥é¡¼¤È¤È¤â¤Ë½ªÎ»¤·¤Þ¤¹¡£ + ´Ë¤ä¤«¤ÊºÆµ¯Æ°¤Î¾ì¹ç¤Ï¡¢¿Æ¥×¥í¥»¥¹¤¬½ªÎ»¤·¤¿¸å¤Ç¤â»Ò¥×¥í¥»¥¹¤¬ + ¼Â¹Ô¤µ¤ì¤¿¤Þ¤ÞÊüÃÖ¤µ¤ì¤¿¤ê¤â¤·¤Þ¤¹¡£ + (ºÇ¸å¤Î¥ê¥¯¥¨¥¹¥È¤ò½èÍý¤·¤¿¸å¡Ö´Ë¤ä¤«¤Ë½ªÎ»¡×¤¹¤ë + »Ò¥×¥í¥»¥¹¤È¤Ê¤ê¤Þ¤¹¡£) + ¥µ¡¼¥Ð¤òºÆµ¯Æ°¤¹¤ëºÝ¤Ë¡¢¤³¤ì¤¬ÌäÂê¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó + -- ¥µ¡¼¥Ð¤Ï listen ¤¹¤ë¥Ý¡¼¥È¤Ë¥Ð¥¤¥ó¥É¤Ç¤­¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ºÆµ¯Æ°¤¹¤ëÁ°¤Ë¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤Î¹½Ê¸¤ò -t + ¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¿ô + (httpd ¤ò¤´Í÷²¼¤µ¤¤) + ¤ò»È¤Ã¤Æ¸¡¾Ú¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ÀßÄê¥Õ¥¡¥¤¥ë¤Î°Ọ̃Ū¤ÊÆâÍƤò¹½Ê¸¤ÈƱÍͤ˸¡¾Ú¤·¤¿¤¤¾ì¹ç¤Ï¡¢ + Èó root ¥æ¡¼¥¶¤Ç httpd ¤òµ¯Æ°¤·¤è¤¦¤È¤¹¤ì¤Ð¤ï¤«¤ê¤Þ¤¹¡£ + ¤â¤·¥¨¥é¡¼¤¬¤Ê¤±¤ì¤Ð¡¢¥½¥±¥Ã¥È¤ä¥í¥°¤ò³«¤³¤¦¤È¤·¤Æ + root ¤Ç¤Ê¤¤¤¿¤á + (¤â¤·¤¯¤Ï¼Â¹ÔÃæ¤Î httpd + ¤¬´û¤ËɬÍפʥݡ¼¥È¤Ë¥Ð¥¤¥ó¥É¤·¤Æ¤¤¤ë¤¿¤á) + ¤Ë¼ºÇÔ¤¹¤ë¤Ç¤·¤ç¤¦¡£ + ¤³¤ì°Ê³°¤ÎÍýͳ¤Çµ¯Æ°¤Ë¼ºÇÔ¤·¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¤½¤ì¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤Î¥¨¥é¡¼¤Ç¡¢ + ´Ë¤ä¤«¤ÊºÆµ¯Æ°¤ò¹Ô¤¦Á°¤Ë¤½¤Î¸í¤ê¤ò½¤Àµ¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
+
top
+
+

µÞ¤ÊºÆµ¯Æ°

+ +
¥·¥°¥Ê¥ë: HUP
+
apachectl -k restart
+
+ +

HUP ¤¢¤ë¤¤¤Ï restart ¥·¥°¥Ê¥ë¤ò¿Æ¥×¥í¥»¥¹¤ËÁ÷¤ë¤È¡¢ + TERM ¤ÈƱÍÍ¤Ë»Ò¥×¥í¥»¥¹¤ò kill ¤·¤Þ¤¹¤¬¡¢ + ¿Æ¥×¥í¥»¥¹¤Ï½ªÎ»¤·¤Þ¤»¤ó¡£ + ÀßÄê¥Õ¥¡¥¤¥ë¤òºÆÆɹþ¤·¤Æ¡¢¥í¥°¥Õ¥¡¥¤¥ëÁ´¤Æ¤ò³«¤­Ä¾¤·¤Þ¤¹¡£ + ¤½¤Î¸å¡¢¿·¤·¤¤»Ò¥×¥í¥»¥¹¤òµ¯Æ°¤·¤Æ±þÅú¤ò³¤±¤Þ¤¹¡£

+ +

mod_status + ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢HUP ¤¬Á÷¤é¤ì¤¿¾ì¹ç¤Ë + ¥µ¡¼¥ÐÅý·×¤¬¥¼¥í¤ËÀßÄꤵ¤ì¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +
ºÆµ¯Æ°»þ¤ËÀßÄê¥Õ¥¡¥¤¥ë¤Ë¸í¤ê¤¬¤¢¤ë¤È¡¢ + ¿Æ¥×¥í¥»¥¹¤ÏºÆµ¯Æ°¤»¤º¤Ë¥¨¥é¡¼¤È¤È¤â¤Ë½ªÎ»¤·¤Þ¤¹¡£ + ¤³¤ì¤òÈò¤±¤ë¤Ë¤Ï¼¡¤ÎÊýË¡¤ò¤´Í÷²¼¤µ¤¤¡£
+
top
+
+

ÉÕÏ¿: ¥·¥°¥Ê¥ë¤È¶¥¹ç¾õÂÖ

+ +

Apache 1.2b9 °ÊÁ°¤Ï¡¢ºÆµ¯Æ°¤äÄä»ß¤Î¥·¥°¥Ê¥ë¤ò´Þ¤à¶¥¹ç¾õÂÖ + (¶¥¹ç¾õÂÖ¤ò´Êñ¤ËÀâÌÀ¤¹¤ë¤È: ¥¿¥¤¥ß¥ó¤Ë¥°¤è¤ëÌäÂê¤Ç¡¢ + ¶ñ¹ç¤Î°­¤¤»þ´ÖÂӤˤÁ¤ç¤¦¤É²¿¤«¤¬µ¯¤³¤ë¤ÈͽÁÛ³°¤ÎÆ°ºî¤ò¤¹¤ë + ¤è¤¦¤Ê¤³¤È¤ò»Ø¤·¤Þ¤¹) ¤¬¤¢¤ê¤Þ¤·¤¿¡£ + ¡ÖÀµ¤·¤¤¡×µ¡Ç½¤ò»ý¤Ã¤Æ¤¤¤ë¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ç¤Ï¡¢¤Ç¤­¤ë¤À¤± + ¤³¤Î¤è¤¦¤Ê¤³¤È¤¬µ¯¤³¤é¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¤¤Þ¤¹¡£ + ¤·¤«¤·¡¢¤¢¤ë¼ï¤Î¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ç¤Ï¶¥¹ç¾õÂÖ¤Ï̤¤À³Î¼Â¤Ëµ¯¤³¤ê¤¨¤ë + ¤È¤¤¤¦¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£

+ +

¥Ç¥£¥¹¥¯¾å¤Ç + ScoreBoardFile + ¤ò»ÈÍѤ·¤Æ¤¤¤ë¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ç¤Ï¡¢ + ÀøºßŪ¤Ë¥¹¥³¥¢¥Ü¡¼¥É¤¬²õ¤ì¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ + ¥¹¥³¥¢¥Ü¡¼¥É¤¬²õ¤ì¤¿¾ì¹ç¤Ï¡¢ + "bind: Address already in use" (HUP ¸å) ¤ä + "long lost child came home!" (USR1 ¸å) + ¤È¤¤¤Ã¤¿·ë²Ì¤Ë¤Ê¤ê¤Þ¤¹¡£ + Á°¼Ô¤ÏÃ×̿Ū¤Ê¥¨¥é¡¼¤Ç¤¹¤¬¡¢ + ¸å¼Ô¤Ï¥¹¥³¥¢¥Ü¡¼¥É¥¹¥í¥Ã¥È¤ò¼º¤¦¤À¤±¤Ç¤¹¡£ + ¤Ç¤¹¤«¤é´Ë¤ä¤«¤ÊºÆµ¯Æ°¤Ï¡¢¤¿¤Þ¤Ë³Î¼Â¤ÊºÆµ¯Æ° (HUP) + ¤âÊ»ÍѤ·¤Æ»È¤Ã¤¿Êý¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£ + ¤³¤ì¤é¤ÎÌäÂê¤ò¹îÉþ¤¹¤ë¤Î¤ÏÈó¾ï¤ËÆñ¤·¤¤¤Î¤Ç¤¹¤¬¡¢ + ¹¬¤¤¤Ê¤³¤È¤ËÂçÉôʬ¤Î¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ç¤Ï¥¹¥³¥¢¥Ü¡¼¥É¤Î¥Õ¥¡¥¤¥ë¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£ + ¤³¤ì¤ò»ÈÍѤ¹¤ë¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ï¡¢ + ScoreBoardFile + ¤ò¤´Í÷²¼¤µ¤¤¡£

+ +

Á´¤Æ¤Î¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Ë¤ª¤¤¤Æ¡¢¸Ä¡¹¤Î»Ò¥×¥í¥»¥¹¤Ç + ·Ñ³Ū¤Ê HTTP ¥³¥Í¥¯¥·¥ç¥ó (KeepAlive) + ¤Ë´Ø¤¹¤ë¾®¤µ¤Ê¶¥¹ç¾õÂÖ¤¬µ¯¤³¤ê¤¨¤Þ¤¹¡£ + ¥ê¥¯¥¨¥¹¥È¹Ô¤òÆɤó¤À¸å¡¢¤½¤·¤Æ¥ê¥¯¥¨¥¹¥È¥Ø¥Ã¥À¤òÆɤàÁ°¤Ë + »Ò¥×¥í¥»¥¹¤Ï½ªÎ»¤¹¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£ + ¤³¤ì¤ËÂФ¹¤ë½¤Àµ¤¬¤¢¤ê¤Þ¤¹¤¬ 1.2 ¤Ç½¤Àµ¤¹¤ë¤Ë¤Ïȯ¸«¤¬ÃÙ¤¹¤®¤Þ¤·¤¿¡£ + ÍýÏÀŪ¤Ë¤Ï¡¢¤³¤ì¤ÏÌäÂê¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£ + ¤Ê¤¼¤Ê¤é KeepAlive ¤Î¥¯¥é¥¤¥¢¥ó¥È¤Ï¡¢¥Í¥Ã¥È¥ï¡¼¥¯ÃÙ±ä¤ä + ¥µ¡¼¥Ð¤Î¥¿¥¤¥à¥¢¥¦¥È¤Ê¤É¤ËÈ÷¤¨¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤é¤Ç¤¹¡£ + ¼ÂºÝ¤Ë¤â²¿¤«±Æ¶Á¤¬¤¢¤ë¤è¤¦¤Ë¤Ï¸«¤¨¤Þ¤»¤ó + -- ¥Æ¥¹¥È¥±¡¼¥¹¤Ç¥µ¡¼¥Ð¤ò 1 ÉÃ´Ö¤Ë 20 ²óºÆµ¯Æ°¤·¤Æ¤â + ¥¯¥é¥¤¥¢¥ó¥È¤Ï²õ¤ì¤¿²èÁü¤ä¶õ¤Î¥É¥­¥å¥á¥ó¥È¤ò¼õ¤±¼è¤ë¤³¤È¤Ê¤¯ + Àµ¾ï¤Ë±ÜÍ÷¤Ç¤­¤Æ¤¤¤Þ¤¹¡£

+
+
+

Available Languages:  de  | + en  | + es  | + ja  | + ko 

+
+ \ No newline at end of file diff --git a/docs/manual/stopping.html.ko.euc-kr b/docs/manual/stopping.html.ko.euc-kr new file mode 100644 index 00000000..dee50b40 --- /dev/null +++ b/docs/manual/stopping.html.ko.euc-kr @@ -0,0 +1,205 @@ + + + +Áß´Ü°ú Àç½ÃÀÛ - Apache HTTP Server + + + + +
+

¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

+

Apache HTTP Server Version 2.2

+
+
<-
+
+Apache > HTTP Server > Documentation > Version 2.2

Áß´Ü°ú Àç½ÃÀÛ

+
+

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

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

ÀÌ ¹®¼­´Â À¯´Ð½º·ù ½Ã½ºÅÛ¿¡¼­ ¾ÆÆÄÄ¡¸¦ Áß´ÜÇÏ°í Àç½ÃÀÛÇÏ´Â + ³»¿ëÀ» ´ã°íÀÖ´Ù. À©µµ¿ìÁî NT, 2000, XP »ç¿ëÀÚ´Â ¼­ºñ½º·Î ¾ÆÆÄÄ¡ + ½ÇÇàÇϱ⿡¼­, À©µµ¿ìÁî 9x¿Í ME »ç¿ëÀÚ´Â ÄÝ¼Ö ÇÁ·Î±×·¥À¸·Î + ¾ÆÆÄÄ¡ ½ÇÇàÇϱ⿡¼­ Ç÷¡Æûº° ¾ÆÆÄÄ¡ Á¶ÀÛ¹ýÀ» ¾Ë ¼ö ÀÖ´Ù.

+
+ +
top
+
+

¼Ò°³

+ +

¾ÆÆÄÄ¡¸¦ Áß´ÜÇÏ°í Àç½ÃÀÛÇÏ·Á¸é ½ÇÇàÇÏ°í ÀÖ´Â + httpd ÇÁ·Î¼¼½º¿¡ ½Ã±×³ÎÀ» º¸³»¾ß ÇÑ´Ù. ½Ã±×³ÎÀ» + º¸³»´Â ¹æ¹ýÀº µÎ°¡Áö´Ù. Çϳª´Â À¯´Ð½º kill + ¸í·É¾î¸¦ »ç¿ëÇÏ¿© ÇÁ·Î¼¼½º¿¡ Á÷Á¢ ½Ã±×³ÎÀ» º¸³»´Â ¹æ¹ýÀÌ´Ù. + ½Ã½ºÅÛ¿¡ ¸¹Àº httpd°¡ ½ÇÇàµÇÁö¸¸, PidFile¿¡ pid°¡ ±â·ÏµÈ ºÎ¸ð¿Ü¿¡ + ´Ù¸¥ ÇÁ·Î¼¼½º¿¡ ½Ã±×³Î(signal)À» º¸³»¸é ¾ÈµÈ´Ù. Áï, ºÎ¸ðÀÌ¿Ü¿¡ + ´Ù¸¥ ÇÁ·Î¼¼½º¿¡ ½Ã±×³ÎÀ» º¸³¾ ÇÊ¿ä°¡ ¾ø´Ù´Â ¸»ÀÌ´Ù. ºÎ¸ð¿¡°Ô + º¸³¾ ¼ö ÀÖ´Â ½Ã±×³ÎÀº ¼¼°¡Áö·Î, ÀÌÁ¦ ¼³¸íÇÒ TERM, HUP, USR1ÀÌ´Ù.

+ +

´ÙÀ½°ú °°ÀÌ ºÎ¸ð¿¡°Ô ½Ã±×³ÎÀ» º¸³½´Ù:

+ +

kill -TERM `cat /usr/local/apache2/logs/httpd.pid`

+ +

httpd ÇÁ·Î¼¼½º¿¡°Ô ½Ã±×³ÎÀ» º¸³»´Â ´Ù¸¥ ¹æ¹ýÀº + ¸í·ÉÇà ¿É¼Ç -k¸¦ »ç¿ëÇÏ´Â °ÍÀÌ´Ù. ¾Æ·¡¼­ ¼³¸íÇÒ + stop, restart, gracefulÀº + httpd ½ÇÇàÆÄÀÏÀÇ ¾Æ±Ô¸ÕÆ®µéÀÌ´Ù. + ±×·¯³ª ÀÌ ¾Æ±Ô¸ÕÆ®µé·Î httpd¸¦ ½ÇÇàÇÏ´Â, apachectl ½ºÅ©¸³Æ®¸¦ + »ç¿ëÇÏ±æ ±ÇÇÑ´Ù.

+ +

httpd¿¡ ½Ã±×³ÎÀ» º¸³½ÈÄ, ´ÙÀ½ ¸í·É¾î·Î + ÁøÇà»óȲÀ» ¾Ë ¼ö ÀÖ´Ù:

+ +

tail -f /usr/local/apache2/logs/error_log

+ +

À§ ¿¹¸¦ ´ç½ÅÀÇ ServerRoot¿Í PidFile ¼³Á¤¿¡ ¾Ë¸Â°Ô ¼öÁ¤Ç϶ó.

+
top
+
+

´çÀå Áß´Ü

+ +
½Ã±×³Î: TERM
+
apachectl -k stop
+
+ +

TERMÀ̳ª stop ½Ã±×³ÎÀ» ºÎ¸ð¿¡°Ô + º¸³»¸é Áï½Ã ¸ðµç ÀÚ½ÄÀ» Á×ÀδÙ. ÀÚ½ÄÀ» ¿ÏÀüÈ÷ Á×À̴µ¥´Â + ¸î ÃÊ°¡ °É¸± ¼ö ÀÖ´Ù. ±×·±ÈÄ ºÎ¸ð°¡ Á¾·áÇÑ´Ù. ó¸®ÁßÀÎ ¿äûÀº + Áߴܵǰí, ´õ ÀÌ»ó ¿äûÀ» ¹ÞÁö¾Ê´Â´Ù.

+
top
+
+

Á¡ÀÝÀº Àç½ÃÀÛ

+ +
½Ã±×³Î: USR1
+
apachectl -k graceful
+
+ +

USR1À̳ª graceful ½Ã±×³ÎÀ» + ºÎ¸ð¿¡°Ô º¸³»¸é ºÎ¸ð ÇÁ·Î¼¼½º´Â Àڽĵ鿡°Ô ÇöÀç ¿äûÀ» + ó¸®ÇÑÈÄ Á¾·áÇ϶ó°í (ȤÀº ÇöÀç ¾Æ¹«°Íµµ ó¸®ÇÏÁö ¾Ê´Ù¸é + Áï½Ã Á¾·áÇ϶ó°í) Á¶¾ðÇÑ´Ù. ºÎ¸ð´Â ¼³Á¤ÆÄÀÏÀ» + ´Ù½ÃÀÐ°í ·Î±×ÆÄÀϵµ ´Ù½Ã ¿¬´Ù. ÀÚ½ÄÀÌ Á×À»¶§¸¶´Ù ºÎ¸ð´Â + Á×Àº ÀڽĴë½Å »õ·Î¿î ¼³Á¤ ¼¼´ë¿¡ ±âÃÊÇÑ ÀÚ½ÄÀ» + ½ÇÇàÇÏ¿© Áï½Ã ¿äûÀ» ó¸®ÇÏ°Ô ÇÑ´Ù.

+ +
Á¡ÀÝÀº Àç½ÃÀÛ(graceful restart)À¸·Î USR1À» + »ç¿ëÇÒ ¼ö ¾ø´Â Ç÷¡Æû¿¡¼­´Â ´ë½Å (WINCH¿Í °°Àº) + ´Ù¸¥ ½Ã±×³ÎÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù. apachectl gracefulÀº + Ç÷¡Æû¿¡ ¾Ë¸ÂÀº ½Ã±×³ÎÀ» º¸³½´Ù.
+ +

Á¡ÀÝÀº Àç½ÃÀÛÀº Ç×»ó MPMÀÇ ÇÁ·Î¼¼½º Á¶Àý Áö½Ã¾î ¼³Á¤À» + °í·ÁÇÏ¿©, Àç½ÃÀÛµ¿¾È Ŭ¶óÀ̾ðÆ®¸¦ ¼­ºñ½ºÇÏ´Â ÇÁ·Î¼¼½º³ª ¾²·¹µå°¡ + Àû´çÇÑ ¼ö¸¦ À¯ÁöÇϵµ·Ï ¼³°èµÇ¾ú´Ù. °Ô´Ù°¡ StartServers´Â, ÀÏÃÊ ÈÄ + ÃÖ¼ÒÇÑ StartServers¸¸Å­ »õ·Î¿î ÀÚ½ÄÀÌ ¾È¸¸µé¾îÁö¸é ÀÚ½ÄÀÌ + StartServers °³°¡ µÇµµ·Ï »õ·Î ¸¸µç´Ù. Áï, ÇÁ·Î±×·¥Àº ¼­¹öÀÇ + ÇöÀç ºÎÇÏ¿¡ ¾Ë¸ÂÀº ÀÚ½ÄÀÇ °³¼ö¸¦ À¯ÁöÇϸç, + StartServers ÆĶó¹ÌÅÍ·Î ÁöÁ¤ÇÑ ´ç½ÅÀÇ + ±â´ë¸¦ Á¸ÁßÇÑ´Ù.

+ +

mod_status »ç¿ëÀÚ´Â USR1À» + ¹ÞÀ»¶§ ¼­¹ö Åë°è°¡ 0ÀÌ µÇÁö ¾ÊÀ½À» ºÃÀ» + °ÍÀÌ´Ù. ¼­¹ö´Â »õ·Î¿î ¿äûÀ» (¿î¿µÃ¼Á¦´Â À̵éÀ» Å¥¿¡ ´ã¾Æ¼­ + ¾î¶² °æ¿ì¿¡µµ ÀÒ¾î¹ö¸®Áö ¾Ê´Â´Ù) ó¸®ÇÏÁö ¸øÇÏ´Â ½Ã°£À» + ÃÖ¼ÒÈ­ÇÏ°í ´ç½ÅÀÇ Æ©´× ÆĶó¹ÌÅ͸¦ Á¸ÁßÇϵµ·Ï ¸¸µé¾îÁ³´Ù. + À̸¦ À§ÇØ ¼¼´ë°£ ¸ðµç ÀÚ½ÄÀ» ±â·ÏÇÏ´Â scoreboard¸¦ + À¯ÁöÇÑ´Ù.

+ +

status ¸ðµâÀº ¶ÇÇÑ Á¡ÀÝÀº Àç½ÃÀÛ Àü¿¡ ½ÃÀÛÇÏ¿© ¾ÆÁ÷µµ + ¿äûÀ» ó¸®ÇÏ°í ÀÖ´Â ÀÚ½ÄÀ» G·Î ¾Ë·ÁÁØ´Ù.

+ +

ÇöÀç·Î´Â USR1À» »ç¿ëÇÏ´Â ·Î±×¼øȯ ½ºÅ©¸³Æ®°¡ + Àç½ÃÀÛÀü¿¡ ¸ðµç ÀÚ½ÄÀÌ ·Î±×ÀÛ¼ºÀ» ¸¶ÃÆ´ÂÁö ¾Ë ¼ö ÀÖ´Â + ¹æ¹ýÀÌ ¾ø´Ù. ¿ì¸®´Â USR1 ½Ã±×³ÎÀ» º¸³»°í + Àû´çÇÑ ½Ã°£ÀÌ Áö³­ÈÄ ÀÌÀü ·Î±×¸¦ ´Ù·çµµ·Ï Á¦¾ÈÇÑ´Ù. ¿¹¸¦ + µé¾î ³·Àº ´ë¿ªÆø »ç¿ëÀÚÀÇ °æ¿ì Á¢¼Ó ´ëºÎºÐÀÌ ¸¶Ä¡´Âµ¥ 10ºÐÀÌ + ¾È°É¸°´Ù¸é, ÀÌÀü ·Î±×¸¦ ´Ù·ç±âÀü¿¡ 15ºÐ ±â´Ù¸°´Ù.

+ +
¼³Á¤ÆÄÀÏ¿¡ ¿À·ù°¡ ÀÖ´Ù¸é Àç½ÃÀ۽à ºÎ¸ð´Â Àç½ÃÀÛÇÏÁö + ¾Ê°í ¿À·ù¸¦ ³»¸ç Á¾·áÇÑ´Ù. ¶Ç, Á¡ÀÝÀº Àç½ÃÀÛÀÇ °æ¿ì Á¾·áÇÒ¶§ + ÀÚ½ÄÀÌ ½ÇÇàµÇµµ·Ï ³öµÐ´Ù. (ÀڽĵéÀº ÀÚ½ÅÀÇ ¸¶Áö¸· ¿äûÀ» + ó¸®ÇÏ°í "Á¡ÀÝ°Ô Á¾·áÇÑ´Ù".) ÀÌ´Â ¼­¹ö¸¦ Àç½ÃÀÛÇÒ¶§ + ¹®Á¦°¡ µÈ´Ù. ¼­¹ö´Â ÀÚ½ÅÀÌ ±â´Ù¸± Æ÷Æ®¿¡ ¿¬°áÇÏÁö ¸øÇÑ´Ù. + Àç½ÃÀÛÀü¿¡ -t ¸í·ÉÇà ¿É¼Ç(httpd Âü°í)À¸·Î ¼³Á¤ÆÄÀÏ + ¹®¹ýÀ» °Ë»çÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª ÀÌ·± °Ë»çµµ ¼­¹ö°¡ ¿Ã¹Ù·Î + Àç½ÃÀÛÇÒÁö¸¦ º¸ÀåÇÏÁö ¸øÇÑ´Ù. ¼³Á¤ÆÄÀÏÀÇ ¹®¹ýÀÌ ¾Æ´Ñ Àǹ̸¦ + °Ë»çÇÏ·Á¸é root°¡ ¾Æ´Ñ »ç¿ëÀÚ·Î httpd¸¦ ½ÃÀÛÇغ¼ ¼ö ÀÖ´Ù. + root°¡ ¾Æ´Ï±â¶§¹®¿¡ (¾Æ´Ï¸é ÇöÀç ±× Æ÷Æ®¸¦ »ç¿ëÇÏ´Â + httpd°¡ ½ÇÇàµÇ±â¶§¹®¿¡) ¿À·ù°¡ ¾ø´Ù¸é ¼ÒÄÏ°ú + ·Î±×ÆÄÀÏÀ» ¿­·Á°í ½ÃµµÇÏ´Â °úÁ¤¿¡¼­ ½ÇÆÐÇÒ °ÍÀÌ´Ù. ´Ù¸¥ + ÀÌÀ¯¶§¹®¿¡ ½ÇÆÐÇÑ´Ù¸é ¾Æ¸¶µµ ¼³Á¤ÆÄÀÏ¿¡ ¿À·ù°¡ ÀÖÀ» °ÍÀÌ´Ù. + Á¡ÀÝÀº Àç½ÃÀÛÀ» ÇϱâÀü¿¡ ¿À·ù¸¦ °íÃľßÇÑ´Ù.
+
top
+
+

´çÀå Àç½ÃÀÛ

+ +
½Ã±×³Î: HUP
+
apachectl -k restart
+
+ +

HUPÀ̳ª restart ½Ã±×³ÎÀ» + ºÎ¸ð¿¡°Ô º¸³»¸é TERM°ú °°ÀÌ ¸ðµç ÀÚ½ÄÀ» + Á×ÀÌÁö¸¸ ºÎ¸ð´Â Á¾·áÇÏÁö ¾Ê´Â´Ù. ºÎ¸ð´Â ¼³Á¤ÆÄÀÏÀ» ´Ù½ÃÀаí + ·Î±×ÆÄÀÏÀ» ´Ù½Ã ¿¬´Ù. ±×¸®°í »õ·Î¿î ÀڽĵéÀ» ¸¸µé°í ¼­ºñ½º¸¦ + °è¼ÓÇÑ´Ù.

+ +

mod_status »ç¿ëÀÚ´Â HUP¸¦ + º¸³»¸é ¼­¹ö Åë°è°¡ 0ÀÌ µÊÀ» ¾Ë ¼ö ÀÖ´Ù.

+ +
¼³Á¤ÆÄÀÏ¿¡ ¿À·ù°¡ ÀÖ´Ù¸é Àç½ÃÀÛÀ» Çصµ ºÎ¸ð´Â Àç½ÃÀÛÇÏÁö +¾Ê°í ¿À·ù¸¦ ³»¸ç Á¾·áÇÒ °ÍÀÌ´Ù. À̸¦ ÇÇÇÏ´Â ¹æ¹ýÀº À§¸¦ Âü°íÇ϶ó.
+
top
+
+

ºÎ·Ï: ½Ã±×³Î°ú ·¹À̽º ÄÁµð¼Ç

+ +

Apache 1.2b9 ÀÌÀü¿¡´Â Àç½ÃÀÛ°ú Á¾·á ½Ã±×³Î¿¡ °ü°èµÈ + ·¹À̽º ÄÁµð¼Ç(race condition)ÀÌ ÀÖ¾ú´Ù. (·¹À̽º + ÄÁµð¼ÇÀº °£´ÜÇÑ ¼³¸íÇÏÀÚ¸é, ¾î¶² ÀÏÀÌ À߸øµÈ¶§ ÀϾ¼­ + ±â´ëÇÑ´ë·Î µ¿ÀÛÇÏÁö ¾Ê´Â ½Ã°£¿¡ ¹Î°¨ÇÑ ¹®Á¦´Ù.) "¿Ã¹Ù¸¥" + ±â´ÉÀÌ ÀÖ´Â ¾ÆÅ°ÅØÃÄ¿¡¼­ ¿ì¸®´Â ÀÌ·± ¹®Á¦¸¦ ÃÖ´ëÇÑ ÇØ°áÇß´Ù. + ±×·¯³ª ¾î¶² ¾ÆÅ°ÅØÃÄ¿¡´Â ¾ÆÁ÷µµ ·¹À̽º ÄÁµð¼ÇÀÌ Á¸ÀçÇÔÀ» + ÁÖÀÇÇ϶ó.

+ +

ScoreBoardFileÀ» + µð½ºÅ©¿¡ ÀúÀåÇÏ´Â ¾ÆÅ°ÅØÃÄ´Â scoreboard¸¦ ¸Á°¡Æ®¸± °¡´É¼ºÀÌ + ÀÖ´Ù. ±×·¯¸é (HUPÈÄ) "bind: Address already in use" + ȤÀº (USR1 ÈÄ) "long lost child came home!"ÀÌ + ¹ß»ýÇÒ ¼ö ÀÖ´Ù. ÀüÀÚ´Â ½É°¢ÇÑ ¿À·ùÀÌ°í, ÈÄÀÚ´Â ´ÜÁö ¼­¹ö°¡ + scoreboard slotÀ» ÀÒ°Ô ¸¸µç´Ù. ±×·¡¼­ °­Á¦ Àç½ÃÀÛÀ» ÁÙÀÌ°í + Á¡ÀÝÀº Àç½ÃÀÛÀ» »ç¿ëÇϱæ ÃßõÇÑ´Ù. ÀÌ ¹®Á¦´Â ÇØ°áÇϱ⠸ſì + Èûµé´Ù. ±×·¯³ª ´ÙÇàÈ÷µµ ´ëºÎºÐÀÇ ¾ÆÅ°ÅØÃÄ´Â scoreboard·Î ÆÄÀÏÀ» + »ç¿ëÇÏÁö ¾Ê´Â´Ù. ÆÄÀÏÀ» »ç¿ëÇÏ´Â ¾ÆÅ°ÅØÃĶó¸é ScoreBoardFile ¹®¼­¸¦ Âü°íÇ϶ó.

+ +

¸ðµç ¾ÆÅ°ÅØÃÄ¿¡´Â Áö¼ÓµÇ´Â HTTP ¿¬°á (KeepAlive)¿¡¼­ + µÎ¹ø° ÀÌÈÄ ¿äûÀ» ó¸®ÇÏ´Â ÀڽĿ¡ ¾à°£ÀÇ ·¹À̽º ÄÁµð¼ÇÀÌ + ÀÖ´Ù. ÀÚ½ÄÀº ¿äûÁÙÀ» ÀÐÀº ÈÄ ¿äû Çì´õ¸¦ ÀбâÀü¿¡ Á¾·áÇÒ ¼ö + ÀÖ´Ù. ÀÌ ¹®Á¦´Â ³Ê¹« ´Ê°Ô ¹ß°ßÇÏ¿© 1.2 ¹öÀüÀÌ ³ª¿ÂÈÄ¿¡¾ß + ¼öÁ¤µÇ¾ú´Ù. ±×·¯³ª ³×Æ®¿÷ Áö¿¬À̳ª ¼­¹ö ½Ã°£Á¦ÇѶ§¹®¿¡ KeepAlive + Ŭ¶óÀ̾ðÆ®´Â ÀÌ·± °æ¿ì¸¦ ¿¹»óÇؾßÇϱ⠶§¹®¿¡ ÀÌ·Ð»ó ¹®Á¦´Â + ¾ÈµÈ´Ù. ½ÇÁ¦·Î ¼­¹ö¸¦ °Ë»çÇϱâÀ§ÇØ ÀÏÃÊ¿¡ 20¹ø Àç½ÃÀÛÇÏ´Â µ¿¾È + Ŭ¶óÀ̾ðÆ®°¡ ±úÁø ±×¸²À̳ª ºó ¹®¼­¾øÀÌ »çÀÌÆ®¸¦ ¼º°øÀûÀ¸·Î + ÀоîµéÀÌ±æ ±â´ëÇÏÁö ¾Ê´Â´Ù¸é ¹®Á¦°¡ ¾ÈµÈ´Ù.

+
+
+

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

+
+ \ No newline at end of file diff --git a/docs/manual/style/build.properties b/docs/manual/style/build.properties new file mode 100644 index 00000000..b123dfb9 --- /dev/null +++ b/docs/manual/style/build.properties @@ -0,0 +1,4 @@ +# This file contains version specific properties + +# No xml files yet +# noxml.fr = upgrading.html.fr diff --git a/docs/manual/style/common.dtd b/docs/manual/style/common.dtd new file mode 100644 index 00000000..8bc6de73 --- /dev/null +++ b/docs/manual/style/common.dtd @@ -0,0 +1,191 @@ + + + + + + + +%HTMLlat1; + + +%HTMLsymbol; + + +%HTMLspecial; + + + + +%HTTPD-VERSION; + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/css/manual-chm.css b/docs/manual/style/css/manual-chm.css new file mode 100644 index 00000000..8471411b --- /dev/null +++ b/docs/manual/style/css/manual-chm.css @@ -0,0 +1,27 @@ +@import url(manual-loose-100pc.css); + +/* Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +html { + font-size: 95%; +} + +h1 { + margin: 0 0 0.5em 0; +} + +/* the end */ diff --git a/docs/manual/style/css/manual-loose-100pc.css b/docs/manual/style/css/manual-loose-100pc.css new file mode 100644 index 00000000..ffea7de6 --- /dev/null +++ b/docs/manual/style/css/manual-loose-100pc.css @@ -0,0 +1,155 @@ +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * manual.css - no sidebar, 100% normal font height + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +/* import the main CSS, so we + * have to adjust only a few things + */ +@import url(manual.css); + +html { + font-size: 100%; +} + +/* "sidebar" background is white here */ +div#quickview a:hover, +div#quickview a:active { + background-color: #f0f0f0; + color: #0073c7; +} + +div#quickview code.module a:hover, +div#quickview code.module a:active { + background-color: #f0f0f0; + color: #8b4513; +} + +div#quickview code.directive a:hover, +div#quickview code.directive a:active { + background-color: #f0f0f0; + color: #287f00; +} + +h1 { + font-size: 1.5em; +} + +h2 { + font-size: 1.2em; +} + +.category h2 { + font-size: 1em; +} + +h3 { + font-size: 1.1em; +} + +h4 { + font-size: 1em; +} + +div.example h3, +div.note h3, +div.warning h3 { + font-size: 1em; +} + +div#quickview h3, +div#quickview h3.directives { + margin: 1em 0 0.3em 0; + font-size: 1.1em; +} + +div#quickview h3.directives { + margin-top: 0; +} + +div#quickview li { + font-size: 1em; +} + +div#quickview ul { + margin-bottom: 1em; +} + +div#quickview ul#toc { + margin-left: 0; +} + +div#quickview li img { + display: inline; + margin-right: 19px; +} + +#module-index div#quickview ul#toc, +#manual-page div#quickview ul#toc, +div#quickview #topics { + padding-left: 0; +} + +div#quickview .seealso { + padding-left: 34px; +} + +#module-index div#quickview ul#toc li, +#manual-page div#quickview ul#toc li, +div#quickview #topics li, +div#quickview .seealso li { + margin: 0; + list-style-type: none; +} + +div#page-header p.menu, +div#path, +div#footer { + font-size: smaller; +} + +div#quickview { + position: static; + margin: 0 0 1em 30px; + padding: 0; + width: auto; + background-color: #fff; +} + +div#page-content { + margin-right: 0; + padding-right: 0; +} + +div.example pre, +div.example p > code { + font-size: 0.9em; +} + +div.note pre, +div.warning pre { + font-size: 0.9em; +} + +table.qref td.descr { + font-size: 0.9em; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * -> The End <- + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ diff --git a/docs/manual/style/css/manual-print.css b/docs/manual/style/css/manual-print.css new file mode 100644 index 00000000..0d0695d2 --- /dev/null +++ b/docs/manual/style/css/manual-print.css @@ -0,0 +1,717 @@ +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * manual.css for printers + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * mainframe ;-) + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ +html { + font-size: 11pt; +} + +body { + background-color: #fff; + color: #000; + padding: 0 0 0 0; + margin: 0; + font-family: "Times New Roman", serif; + font-weight: normal; +} + +pre, code { + font-family: "Courier New", Courier, monospace; +} + +strong { + font-weight: bold; +} + +q, em, var { + font-style: italic; +} + +span.transnote, span.phonetic { + font-weight: normal; + background-color: inherit; + color: #888; +} + +/* fixup IE & Opera + * otherwise they forget to inherit + * the computed font-size value + */ +table, code { + font-size: 1em; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Links + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* normal links */ +/* ====================== */ +a:link, +a:visited, +a:hover, +a:active { + color: #000; + background-color: inherit; + text-decoration: none; +} + +/* sidebar */ +div#quickview a:hover, +div#quickview a:active { + background-color: #fff; + color: #000; +} + +/* EXPERIMENTAL! I'm waiting for complaints... */ +#page-content p > a[href]:after { + content: " (\002197\0000A0" attr(href) ") "; + color: #036; +} + +/* code.module [links] */ +/* ====================== */ +code.module, +code.module a:link, +code.module a:visited, +code.module a:hover, +code.module a:active { + color: #8b4513; + background-color: inherit; + text-decoration: none; +} + +/* code.directive [links] */ +/* ====================== */ +code.directive, +code.directive a:link, +code.directive a:visited, +code.directive a:hover, +code.directive a:active { + color: #287f00; + background-color: inherit; + text-decoration: none; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Headings + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* h1 */ +/* ====================== */ +h1 { + padding: 0 0 0.2em 0; + margin: 1em 0 0.5em 0; + border-style: none none solid none; + border-bottom-width: 1px; + border-bottom-color: #405871; + background-color: inherit; + color: #000; + text-decoration: none; + font-size: 17pt; + font-weight: bold; + text-align: center; +} + +/* h2 */ +/* ====================== */ +h2 { + padding: 0.2em 0 0.2em 0.2em; + margin: 0 0 0.5em 0; + width: 80%; + text-decoration: none; + font-size: 15pt; + font-weight: bold; + border-bottom: 1px solid #000; + text-align: left; +} + +.section h2, +.directive-section h2, +.category h2 { + background-color: #fff; + color: #000; +} + +/* take care of s inside */ +h2 a, +h2 a:hover, +h2 a:active { + color: inherit; + background-color: inherit; + text-decoration: none; +} + +/* h3, h4 */ +/* ====================== */ +h3 { + background-color: inherit; + color: #000; + text-decoration: none; + font-weight: bold; + font-size: 13pt; + margin: 1.3em 0 0.4em 0; + padding: 0 0 0 0.2em; +} + +h4 { + background-color: inherit; + color: #000; + text-decoration: none; + font-weight: bold; + font-size: 11pt; + margin: 1.3em 0 0.2em 0; + padding: 0 0 0 0.2em; +} + +/* margin adjustment */ +h3 + *, h4 + * { + margin-top: 0; +} + +/* IE confuses the + * :-( + * so reset some things + */ +ul, .section table, .directive-section table { + margin-bottom: 1em; +} + +/* titles for + * examples, notes and warnings + */ +div.example h3, +div.note h3, +div.warning h3 { + margin: 0 0 0.5em 0; + text-align: left; + font-size: 11pt; +} + +/* sidebar */ +div#quickview h3 { + margin: 1em 0 0.3em 0; + font-size: 13pt; +} + +div#quickview h3.directives { + margin-top: 0; +} + +/* take care of s inside */ +h3 a, +h3 a:hover, +h3 a:active, +h4 a, +h4 a:hover, +h4 a:active { + color: inherit; + background-color: inherit; + text-decoration: none; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Up & Top helper images + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +div.up, +div.top { + display: none; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Tables + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* general */ +/* ====================== */ +table { + border: 1px solid #000; + border-collapse: collapse; + padding: 2px; + margin-top: 0.5em; + margin-bottom: 0; + margin-left: 1px; /* border-width == 1px */ +} + +td, th { + empty-cells: show; /* show border around empty cells */ + padding: 0.1em 0.2em; + vertical-align: top; + text-align: left; + line-height: 1.1em; +} + +th { + font-weight: bold; +} + +td.centered { + text-align: center; +} + +tr.header, tr.header th { + border-top: 1px solid #000; + border-bottom: 1px solid #000; +} + +/* bordered table cells */ +/* ====================== */ + +/* turn off borders in tables nested in + * bordered tables per default + */ +table.bordered table td, +table.bordered table th { + border-style: none; +} + +table.bordered td, +table.bordered th, +table table.bordered td, +table table.bordered th { + border: 1px solid #000; +} + +/* mod/dir. overview table and quick reference */ +/* ============================================ */ +table.module th, +table.directive th { + white-space: nowrap; +} + +table.qref { + border-collapse: collapse; + width: auto; +} + +table.qref td { + border-style: none solid; + border-color: #000; + border-width: 1px; +} + +table.qref td.descr { + padding-left: 1em; + font-size: 11pt; +} + +table#legend { + width: 100%; + border-style: none; + border-width: 0; + vertical-align: bottom; + padding: 0; + margin: 0; +} + +table#legend td { + vertical-align: bottom; + margin: 0; + padding: 0; +} + +table#legend table { + vertical-align: bottom; + margin: 0 0 0 0.4em; + padding: 0; + height: 7.5em; +} + +table#legend td.letters span { + display: none; +} + +table#legend table td, +table#legend table th { + vertical-align: middle; + padding: 0.1ex 0.2em; + line-height: 1em; +} + +/* related modules & dir. */ +/* ====================== */ + +/* assuming, all links are enclosed by + * or + * + */ + +table.related { + border-collapse: collapse; +} + +table.related th, +table.related td { + background-color: #fff; + color: #000; + padding: 0.2ex 0.4em; + border: 1px solid #000; +} + +table.related th { + vertical-align: middle; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Lists + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* list default values */ +/* ====================== */ +ul { + list-style-type: disc; +} + +ul ul { + list-style-type: square; +} + +ul ul ul { + list-style-type: circle; +} + +li, dt, dd { + line-height: 1.1em; +} + +dt { + margin-top: 0.5em; + font-weight: bold; +} + +ol li { + margin-top: 0.5em; +} + +ol.up-A { + list-style-type: upper-alpha; +} + +/* table of contents */ +/* ====================== */ +#toc, +#topics { + margin: 0; + padding: 0; +} + +#toc li, +#topics li { + list-style-type: square; + margin: 0 0 1em 0; + padding: 0; +} + +#toc li img, +#topics li img { + margin-right: 19px; +} + +/* see also */ +/* ====================== */ +.seealso { + margin: 0; + padding: 0; +} + +.seealso li { + list-style-type: square; + margin: 0 0 1em 0; + padding: 0 0 0 34px; +} + +/* related modules & dir. */ +/* ====================== */ +table.related td ul, +table.related td li { + list-style-type: none; + margin: 0; + padding: 0; +} + +/* list of all directives */ +/* ====================== */ +div#directive-list ul { + margin: 0; + padding: 0; +} + +/* quickview */ +/* ====================== */ +div#quickview li { + font-size: 11pt; +} + +div#quickview ul { + margin: 0; + padding: 0; +} + +div#quickview ul#toc { + margin: 0; + padding: 0; +} + +div#quickview ul#toc li { + margin: 0 0 0 1em; + padding: 0; + list-style-type: square; + list-style-position: outside; +} + +div#quickview li img { + display: none; +} + +#module-index div#quickview ul#toc, +#manual-page div#quickview ul#toc, +div#quickview #topics, +div#quickview .seealso { + padding-left: 0; +} + +#module-index div#quickview ul#toc li, +#manual-page div#quickview ul#toc li, +div#quickview #topics li, +div#quickview .seealso li { + margin: 0 0 2px 1em; + padding: 0; + list-style-type: square; + list-style-position: outside; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * main page sections + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* page header */ +/* ====================== */ +div#page-header { + margin-left: 0; +} + +div#page-header img { + display: none; +} + +div#page-header p.apache { + background-color: #fff; + color: #000; + padding: 0; + margin: 0; + text-align: center; + vertical-align: middle; + font-size: 20pt; + font-weight: bold; + line-height: 20pt; +} + +div#page-header p.menu { + display: none; +} + +/* breadcrumb navigation */ +div#path { + display: none; +} + +/* content sections */ +/* ====================== */ +div#preamble { + padding-bottom: 1em; + margin-left: 0; +} + +div.section, +div.directive-section { + margin: 0; + padding: 0; +} + +.section p, +.directive-section p { + margin: 0 0 1em 0; + padding: 0; +} + +/* look for this on directive + * list pages + */ +div#directive-list { + margin-left: 0; + padding: 0 0 1em 1em; +} + +div#directive-ref { + margin: -1em 0 0 1px; + padding: 0 0 1em 0; + width: auto; +} + +/* no sidebar */ +div#quickview { + position: static; + margin: 0 0 1em 0; + padding: 0; + width: auto; + background-color: #fff; + color: inherit; +} + +/* -> keep content wide */ +div#page-content { + padding-top: 0; + margin-right: 0; + padding-right: 0; +} + +/* in general */ +p { + line-height: 1.1em; +} + +/* page footer */ +/* ====================== */ +div#footer { + margin-left: 0; + font-size: 11pt; + border-top: 1px solid #000; + padding-top: 0.2em; +} + +div#footer p.apache { + float: none; + text-align: center; + padding: 0 0 1em 0; + margin-top: 0; + font-weight: bold; +} + +div.toplang, +div.bottomlang, +div#footer p.menu { + display: none; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * subsections (examples, notes, warnings) + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* examples */ +/* ====================== */ +div.example, +div.note div.example { + background-color: #fff; + color: #000; + padding: 0.5em; + margin: 1em; + border: 1px dotted #000; +} + +/* the following [block] elements + * may appear inside example... + */ +div.example p, +div.example pre, +div.example table { + padding: 0; + margin: 0; +} + +div.example p { + line-height: 1em; +} + +div.example pre, +div.example p > code { + font-size: 10pt; +} + +/* notes & warnings */ +/* ====================== */ +div.note, +div.warning { + background-color: #fff; + color: #000; + border: 1px solid #000; + padding: 0.5em; + margin: 1em; +} + +div.note p, +div.warning p { + margin: 0; + padding: 0; +} + +div.note pre, +div.warning pre { + font-size: 10pt; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * quotations, indented paragraphs and figures + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ +p.letters { + display: none; +} + +blockquote p { + font-style: italic; + margin: 0; +} + +blockquote p.cite { + font-style: normal; + margin-top: 0; + margin-left: 2em; +} + +blockquote p.cite cite { + font-style: normal; +} + +p.indent { + margin-left: 2em; + margin-top: 1em; +} + +#index-page form { + display: none; +} + +p.figure { + margin-left: 2em; + font-style: italic; +} + +p.figure img { + border: 1px solid #000; +} + +p.figure dfn { + font-weight: bold; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * -> The End <- + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ diff --git a/docs/manual/style/css/manual-zip-100pc.css b/docs/manual/style/css/manual-zip-100pc.css new file mode 100644 index 00000000..488d4600 --- /dev/null +++ b/docs/manual/style/css/manual-zip-100pc.css @@ -0,0 +1,23 @@ +@import url(manual-loose-100pc.css); + +/* Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +h1 { + margin: 0 0 0.5em 0; +} + +/* the end */ diff --git a/docs/manual/style/css/manual-zip.css b/docs/manual/style/css/manual-zip.css new file mode 100644 index 00000000..563a8243 --- /dev/null +++ b/docs/manual/style/css/manual-zip.css @@ -0,0 +1,24 @@ +@import url(manual.css); + +/* Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + + +h1 { + margin: 0 0 0.5em 0; +} + +/* the end */ diff --git a/docs/manual/style/css/manual.css b/docs/manual/style/css/manual.css new file mode 100644 index 00000000..c76fcfa0 --- /dev/null +++ b/docs/manual/style/css/manual.css @@ -0,0 +1,1026 @@ +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * manual.css + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * mainframe ;-) + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ +html { + font-size: 14px; +} + +body { + background-color: #fff; + color: #036; + padding: 0 1em 0 0; + margin: 0; + font-family: Arial, Helvetica, sans-serif; + font-weight: normal; +} + +pre, code { + font-family: "Courier New", Courier, monospace; +} + +strong { + font-weight: bold; +} + +q, em, var { + font-style: italic; +} + +span.transnote, span.phonetic { + font-weight: normal; + background-color: inherit; + color: #888; +} + +/* fixup IE & Opera + * otherwise they forget to inherit + * the computed font-size value + */ +table, code { + font-size: 1em; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Links + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* normal links */ +/* ====================== */ +a:link { + color: #0073c7; + background-color: inherit; +} + +a:visited { + color: #5A88B5; + background-color: inherit; +} + +a:link:hover, +a:link:active, +a:visited:hover, +a:visited:active { + color: #0073c7; + background-color: #f0f0f0; +} + +/* hover on non-white backgrounds */ +tr.odd a:hover, +tr.odd a:active, +tr.header a:hover, +tr.header a:active, +div.note a:hover, +div.note a:active, +div.example a:hover, +div.example a:active, +div.warning a:hover, +div.warning a:active, +div#quickview a:hover, +div#quickview a:active { + background-color: #fff; + color: #0073c7; +} + +/* code.module [links] */ +/* ====================== */ +code.module, +code.module a:link { + color: #8b4513; + background-color: inherit; +} + +code.module a:visited { + color: #bc8f8f; + background-color: inherit; +} + +code.module a:hover, +code.module a:active { + color: #8b4513; + background-color: #f0f0f0; +} + +/* hover on non-white backgrounds */ +tr.odd code.module a:hover, +tr.odd code.module a:active, +tr.header code.module a:hover, +tr.header code.module a:active, +div.note code.module a:hover, +div.note code.module a:active, +div.example code.module a:hover, +div.example code.module a:active, +div.warning code.module a:hover, +div.warning code.module a:active, +div#quickview code.module a:hover, +div#quickview code.module a:active { + background-color: #fff; + color: #8b4513; +} + +/* code.directive [links] */ +/* ====================== */ +code.directive, +code.directive a:link { + color: #287f00; + background-color: inherit; +} + +code.directive a:visited { + color: #35a500; + background-color: inherit; +} + +code.directive a:hover, +code.directive a:active { + color: #287f00; + background-color: #f0f0f0; +} + +/* hover on non-white backgrounds */ +tr.odd code.directive a:hover, +tr.odd code.directive a:active, +tr.header code.directive a:hover, +tr.header code.directive a:active, +div.note code.directive a:hover, +div.note code.directive a:active, +div.example code.directive a:hover, +div.example code.directive a:active, +div.warning code.directive a:hover, +div.warning code.directive a:active, +div#quickview code.directive a:hover, +div#quickview code.directive a:active { + background-color: #fff; + color: #287f00; +} + +/* glossary [links] */ +/* ====================== */ +.glossarylink { + cursor: help; + border-bottom: 1px dashed #0073c7; + text-decoration: none; +} + + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Headings + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* h1 */ +/* ====================== */ +h1 { + padding: 0.2em; + margin: 0; + border: 1px solid #405871; + background-color: inherit; + color: #036; + text-decoration: none; + font-size: 22px; + font-weight: bold; +} + +/* h2 */ +/* ====================== */ +h2 { + padding: 0.2em 0 0.2em 0.7em; + margin: 0 0 0.5em 0; + text-decoration: none; + font-size: 18px; + font-weight: bold; +} + +.section h2 { + background-color: #405871; + color: #fff; +} + +.directive-section h2 { + background-color: #557697; + color: #fff; +} + +.category h2 { + background-color: #e5ecf3; + color: #405871; + font-size: 14px; +} + +/* take care of s inside */ +h2 a, +h2 a:hover, +h2 a:active { + color: inherit; + background-color: inherit; + text-decoration: none; +} + +/* h3, h4 */ +/* ====================== */ +h3 { + background-color: inherit; + color: #036; + text-decoration: none; + font-weight: bold; + font-size: 16px; + margin: 1.3em 0 0.4em 0; + padding: 0; +} + +h4 { + background-color: inherit; + color: #036; + text-decoration: none; + font-weight: bold; + font-size: 14px; + margin: 1.3em 0 0.2em 0; + padding: 0; +} + +/* margin adjustment */ +h3 + *, h4 + * { + margin-top: 0; +} + +/* IE confuses the + * :-( + * so reset some things + */ +ul, .section table, .directive-section table { + margin-bottom: 1em; +} + +/* titles for + * examples, notes and warnings + */ +div.example h3, +div.note h3, +div.warning h3 { + margin: 0 0 0.5em 0; + text-align: left; + font-size: 14px; +} + +/* sidebar */ +div#quickview h3 { + margin: 1em 0 0.3em 0.5em; + font-size: 15px; +} + +div#quickview h3.directives { + margin-top: 0.3em; +} + +/* take care of s inside */ +h3 a, +h3 a:hover, +h3 a:active, +h4 a, +h4 a:hover, +h4 a:active { + color: inherit; + background-color: inherit; + text-decoration: none; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Up & Top helper images + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* arrow left */ +/* ====================== */ +div.up { + width: 30px; + height: 20px; + padding: 0; + margin: -20px 0 1px 0; + text-align: center; + vertical-align: top; +} + +div.up img { + vertical-align: top; + width: 11px; + height: 11px; + border-style: none; +} + +/* arrow up (to page top) */ +/* ====================== */ +div.top { + width: 30px; + padding: 0 0 0 30px; + margin: 0; +} + +div.top img { + margin-top: 0.5em; + vertical-align: bottom; + width: 11px; + height: 11px; + border-style: none; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Tables + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* general */ +/* ====================== */ +table { + border: 1px solid #aaa; + border-collapse: collapse; + padding: 2px; + margin-top: 0.5em; + margin-bottom: 0; +} + +td, th { + empty-cells: show; /* show border around empty cells */ + padding: 0.1em 0.2em; + vertical-align: top; + text-align: left; + line-height: 1.3em; +} + +th { + font-weight: bold; +} + +td.centered { + text-align: center; +} + +td.data { + font-family: monospace; + text-align: right; + padding-left: 1em; +} + +th.data { + text-align: right; +} + +tr.odd { /* for large tables alternating colors */ + background-color: #f2f2f2; +} + +tr.header, tr.header th { + background-color: #e2e2e2; + border-top: 1px solid #aaa; + border-bottom: 1px solid #aaa; +} + +/* bordered table cells */ +/* ====================== */ + +/* turn off borders in tables nested in + * bordered tables per default + */ +table.bordered table td, +table.bordered table th { + border-style: none; +} + +table.bordered td, +table.bordered th, +table table.bordered td, +table table.bordered th { + border: 1px solid #aaa; +} + +/* index page layout table */ +/* ======================= */ +body#index-page div#page-content { + width: 100%; /* IE fun */ +} + +body[id]#index-page div#page-content { + width: auto; /* reasonable browsers. */ +} + +table#indextable { + width: 100%; + border-collapse: collapse; + border: 0 none; +} + +table#indextable td { + width: 33.3%; + border-left: 1px solid #aaa; + padding-top: 0; + padding-bottom: 0; +} + +table#indextable td.col1 { + border-left: 0 none; + padding-left: 0; +} + +table#indextable td.col3 { + padding-right: 0; +} + +/* mod/dir. overview table and quick reference */ +/* ============================================ */ +table.module th, +table.directive th { + white-space: nowrap; +} + +table.qref { + border-collapse: collapse; + width: 100%; +} + +table.qref td { + border-style: none solid; + border-color: #aaa; + border-width: 1px; +} + +table.qref td.descr { + padding-left: 1em; + font-size: 13px; +} + +table#legend { + width: 100%; + border-style: none; + border-width: 0; + vertical-align: bottom; + padding: 0; + margin: 0; +} + +table#legend td { + vertical-align: bottom; + margin: 0; + padding: 0; +} + +table#legend td.letters { + width: 100%; + padding-bottom: 0.5em; +} + +table#legend table { + vertical-align: bottom; + margin: 0 0 0 0.4em; + padding: 0; + height: 7.5em; +} + +table#legend table td, +table#legend table th { + vertical-align: middle; + padding: 0.1ex 0.2em; + line-height: 1em; + white-space: nowrap; +} + +/* related modules & dir. */ +/* ====================== */ + +/* assuming, all links are enclosed by + * or + * + */ + +table.related { + border-collapse: separate; +} + +table.related th { + padding: 0.2ex 0.3em; + background-color: #e5ecf3; + color: #405871; + vertical-align: middle; +} + +table.related td { + padding: 0.2ex 0.3em; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * Lists + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* list default values */ +/* ====================== */ +ul { + list-style-type: disc; +} + +ul ul { + list-style-type: square; +} + +ul ul ul { + list-style-type: circle; +} + +li, dt, dd { + line-height: 1.3em; +} + +dt { + margin-top: 0.5em; + font-weight: bold; +} + +ol li { + margin-top: 0.5em; +} + +ol.up-A { + list-style-type: upper-alpha; +} + +ol.lo-A { + list-style-type: lower-alpha; +} + +dd.separate { + margin-bottom: 2em; +} + +li.separate { + margin-bottom: 1em; +} + +/* table of contents */ +/* ====================== */ +#toc, +#topics { + margin: 0 0 1em 0; + padding: 0; +} + +#toc li, +#topics li { + list-style-type: none; + margin: 0; + padding: 0; +} + +/* see also */ +/* ====================== */ +.seealso { + margin: 0 0 1em 0; + padding: 0; +} + +.seealso li { + list-style-type: none; + margin: 0; + padding: 0 0 0 34px; +} + +/* related modules & dir. */ +/* ====================== */ +table.related td ul, +table.related td li { + list-style-type: none; + margin: 0; + padding: 0; +} + +/* list of all directives */ +/* ====================== */ +div#directive-list ul { + margin: 0; + padding: 0; +} + +/* indextable */ +/* ========== */ +table#indextable td ul { + list-style-type: none; + margin: 0 0 1em 0.5em; + padding: 0 0 0 0; +} + +table#indextable td ul li { + margin-top: 0.3em; +} + +/* sidebar */ +/* ====================== */ +div#quickview li { + font-size: 13px; +} + +div#quickview ul { + margin: 0 0 15px 0; + padding: 0; +} + +div#quickview ul#toc { + margin: 0 0 0 0.5em; + padding: 0; +} + +#module-index div#quickview ul#toc, +#manual-page div#quickview ul#toc { + margin-left: 0; +} + +div#quickview ul#toc li { + margin: 0; + padding: 0; + list-style-type: none; +} + +div#quickview li img { + display: none; +} + +#module-index div#quickview ul#toc, +#manual-page div#quickview ul#toc, +div#quickview #topics, +div#quickview .seealso { + padding-left: 15px; +} + +#module-index div#quickview ul#toc li, +#manual-page div#quickview ul#toc li, +div#quickview #topics li, +div#quickview .seealso li { + margin: 0.4em 0 2px 0; + padding: 0; + list-style-type: square; + list-style-position: outside; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * main page sections + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* page header */ +/* ====================== */ +div#page-header { + margin-left: 30px; +} + +div#page-header img { + padding: 0; + display: block; + margin: -70px 0 1px 2em; + width: 248px; + height: 70px; +} + +div#page-header p.apache { + background-color: #405871; + color: #fff; + padding: 0 0 0 248px; + margin: 0; + text-align: center; + vertical-align: middle; + font-size: 16px; + font-weight: bold; + line-height: 29px; +} + +div#page-header p.menu { + text-align: right; + font-size: 13px; + margin: 30px 0 0.5em 0; + padding: 0; +} + +/* breadcrumb navigation */ +div#path { + margin: 0.2em 0 1.2em 30px; + padding: 0; + font-size: 13px; +} + +/* content sections */ +/* ====================== */ +div#preamble { + padding-bottom: 1em; + margin-left: 30px; +} + +div.section, +div.directive-section { + margin: -1.2em 0 0 60px; + padding: 0; +} + +.section p, +.directive-section p { + margin: 0 0 1em 0; + padding: 0; +} + +/* look for this on directive + * list pages + */ +div#directive-list { + margin-left: 30px; + padding: 0 0 1em 1em; +} + +div#directive-ref { + margin: -1em 0 0 0; + padding: 0 0 1em 30px; + width: 100%; /* IE is BAD (broken as designed) */ +} + +div[id]#directive-ref { /* a big sorry to ICab, Amaya (and old Konquerors?) */ + width: auto; /* other browsers are fine ;-) */ +} + +/* sidebar position: right */ +div#quickview { + position: absolute; + top: 5.5em; + right: 1em; + margin-left: 0; + margin-top: 40px; + padding: 4px; + width: 13.5em; + background-color: #f0f0f0; + color: inherit; +} + +/* -> move content left */ +div#page-content { + padding-top: 0; + margin-right: 13em; + padding-right: 30px; +} + +/* unsqueeze on some pages... */ +body.no-sidebar div#page-content, +body#index-page div#page-content { + margin-right: 0; + padding-right: 0; +} + +body#index-page div#page-content { + margin-left: 30px; + padding-bottom: 1em; +} + +/* in general */ +p { + line-height: 1.3em; +} + +/* translations */ +/* ====================== */ +.toplang { + padding: 0; + margin: 0.2em 0.2em 1em 0; +} + +.bottomlang { + padding: 0; + margin: 0 0.2em 0.2em 0; +} + +.toplang p, +.bottomlang p { + font-size: 13px; + text-align: right; + background-color: inherit; + color: #ccc; + margin: 0; + padding: 0; +} + +.toplang p span, +.bottomlang p span { + background-color: inherit; + color: #036; +} + +.toplang p a:link, +.toplang p a:visited, +.bottomlang p a:link, +.bottomlang p a:visited { + text-decoration: none; + font-weight: bold; +} + +.toplang p a:hover, +.toplang p a:active, +.bottomlang p a:hover, +.bottomlang p a:active { + font-weight: bold; +} + +/* page footer */ +/* ====================== */ +div#footer { + margin-left: 30px; + font-size: 13px; + border-top: 1px solid #405871; + padding-top: 0.2em; +} + +div#footer p.apache { + float: left; + text-align: left; + padding: 0 0 1em 0; + margin-top: 0; +} + +div#footer p.menu { + float: right; + text-align: right; + margin-top: 0; + padding: 0 0 1em 0; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * subsections (examples, notes, warnings) + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ + +/* examples */ +/* ====================== */ +div.example { + background-color: #e5ecf3; + color: #000; + padding: 0.5em; + margin: 1em 2em 1em 1em; +} + +/* example inside a note: + * blue in gray doesn't look good + * so simply draw a border around + * and keep it gray + */ +div.note div.example, +div.warning div.example { + border: 1px solid #aaa; + background-color: transparent; + color: inherit; + margin-right: 1em; +} + +/* example inside table */ +table div.example { + margin-right: 1em; +} + +/* the following [block] elements + * may appear inside example... + */ +div.example p, +div.example pre, +div.example table { + padding: 0; + margin: 0; +} + +div.example p { + line-height: 1em; +} + +div.example pre, +div.example p > code { + font-size: 13px; +} + +/* notes & warnings */ +/* ====================== */ +div.note, +div.warning { + background-color: #eee; + color: #036; + padding: 0.5em; + margin: 1em 2em 1em 1em; +} + +div.warning { + border: 1px solid #f00; +} + +div.note p, +div.warning p { + margin: 0.5em 0 0 0; + padding: 0; +} + +div.note pre, +div.warning pre { + font-size: 13px; +} + +/* inside table */ +table div.note, +table div.warning { + margin-right: 1em; +} + +div.outofdate { + background-color: #ffffe0; + color: #036; + padding: 0.5em; + margin: 1em 2em 1em 1em; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * quotations, indented paragraphs, forms and figures + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ +p.letters { + margin: 1em 0 0 0; +} + +p.centered { + text-align: center; +} + +.letters { + text-align: center; + background-color: inherit; + color: #ccc; +} + +.letters a:link, +.letters a:visited { + text-decoration: none; + font-weight: bold; +} + +.letters a:hover, +.letters a:active { + font-weight: bold; +} + +blockquote p { + font-style: italic; + margin: 0; +} + +blockquote p.cite { + font-style: normal; + margin-top: 0; + margin-left: 2em; +} + +blockquote p.cite cite { + font-style: normal; +} + +p.indent { + margin-left: 2em; + margin-top: 1em; +} + +span.indent { + padding-left: 1.5em; + display: block; +} + +#index-page form { + text-align: center; +} + +#index-page form p { + line-height: 1.1em; +} + +#index-page form input { + font-size: 1em; +} + +p.figure { + margin-left: 2em; + font-style: italic; +} + +p.figure img { + border: 1px solid #aaa; +} + +p.figure dfn { + font-weight: bold; +} + +/* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + * -> The End <- + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ */ diff --git a/docs/manual/style/faq.dtd b/docs/manual/style/faq.dtd new file mode 100644 index 00000000..9af4f113 --- /dev/null +++ b/docs/manual/style/faq.dtd @@ -0,0 +1,35 @@ + + + + + +%common; + + + + + + + + + + + diff --git a/docs/manual/style/lang.dtd b/docs/manual/style/lang.dtd new file mode 100644 index 00000000..422313c9 --- /dev/null +++ b/docs/manual/style/lang.dtd @@ -0,0 +1,24 @@ + + + + + +%HTTPD-VERSION; + + + diff --git a/docs/manual/style/latex/atbeginend.sty b/docs/manual/style/latex/atbeginend.sty new file mode 100644 index 00000000..79b555d7 --- /dev/null +++ b/docs/manual/style/latex/atbeginend.sty @@ -0,0 +1,80 @@ +% atbeginend.sty +% +% Licensed to the Apache Software Foundation (ASF) under one or more +% contributor license agreements. See the NOTICE file distributed with +% this work for additional information regarding copyright ownership. +% The ASF licenses this file to You under the Apache License, Version 2.0 +% (the "License"); you may not use this file except in compliance with +% the License. You may obtain a copy of the License at +% +% http://www.apache.org/licenses/LICENSE-2.0 +% +% Unless required by applicable law or agreed to in writing, software +% distributed under the License is distributed on an "AS IS" BASIS, +% WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +% See the License for the specific language governing permissions and +% limitations under the License. + +% defines +% \BeforeBegin{environment}{code-to-execute} +% \BeforeEnd {environment}{code-to-execute} +% \AfterBegin {environment}{code-to-execute} +% \AfterEnd {environment}{code-to-execute} +% +% Save \begin and \end to \BeginEnvironment and \EndEnvironment +\let\BeginEnvironment=\begin +\let\EndEnvironment=\end + +\def\IfUnDef#1{\expandafter\ifx\csname#1\endcsname\relax} + +% Null command needed to for \nothing{something}=.nothing. +\def\NullCom#1{} + +\def\begin#1{% +% +% if defined \BeforeBeg for this environment, execute it +\IfUnDef{BeforeBeg#1}\else\csname BeforeBeg#1\endcsname\fi% +% +% +% +\IfUnDef{AfterBeg#1}% This is done to skip the command for environments + % which can take arguments, like multicols; YOU MUST NOT + % USE \AfterBegin{...}{...} for such environments! + \let\SaveBegEng=\BeginEnvironment% +\else% + % Start this environment + \BeginEnvironment{#1}% + % and execute code after \begin{environment} + \csname AfterBeg#1\endcsname% + % + \let\SaveBegEng=\NullCom% +\fi% +\SaveBegEng{#1}% +} + + +\def\end#1{% +% +% execute code before \end{environment} +\IfUnDef{BeforeEnd#1}\else\csname BeforeEnd#1\endcsname\fi% +% +% close this environment +\EndEnvironment{#1}% +% +% and execute code after \begin{environment} +\IfUnDef{AfterEnd#1}\else\csname AfterEnd#1\endcsname\fi% +} + + +%% Now, define commands +% \BeforeBegin{environment}{code-to-execute} +% \BeforeEnd {environment}{code-to-execute} +% \AfterBegin {environment}{code-to-execute} +% \AfterEnd {environment}{code-to-execute} + +\def\BeforeBegin#1#2{\expandafter\gdef\csname BeforeBeg#1\endcsname +{#2}} +\def\BeforeEnd #1#2{\expandafter\gdef\csname BeforeEnd#1\endcsname +{#2}} +\def\AfterBegin #1#2{\expandafter\gdef\csname AfterBeg#1\endcsname {#2}} +\def\AfterEnd #1#2{\expandafter\gdef\csname AfterEnd#1\endcsname{#2}} diff --git a/docs/manual/style/latex/common.xsl b/docs/manual/style/latex/common.xsl new file mode 100644 index 00000000..a0f10cbb --- /dev/null +++ b/docs/manual/style/latex/common.xsl @@ -0,0 +1,244 @@ + + + + + + + + + + + + + + + + + + +\subsection*{ + +} + + + + + +\subsubsection*{ + +} + + + + + +\subsubsection*{ + +} + + + + + + + + + + +\label{ +: + +} + + + + + + + + + +\par\smallskip\begin{center} +\fbox{ +\begin{minipage}{.8\textwidth}\begin{flushleft} + +{\ttfamily\small +\noindent +} +\end{flushleft}\end{minipage} +} +\end{center}\par\smallskip + + + +\textbf{ + +}\\ + + + + + + + +\begin{list}{}{\topsep 0pt\rightmargin 0pt\leftmargin 2em} +\item[] + +\end{list} + + + + + + +\par\smallskip +{\Huge + + + \fbox{!} + + + $\Longrightarrow$ + + +}\begin{minipage}[t]{.8\textwidth} +\noindent + + +\end{minipage}\par\smallskip + + + +\textbf{ + +} \\ +\noindent + + + + + + + + + +\textsc{ + \textless{} + \hyperlink{/mod/ + + : + + }{ + + } + \textgreater{} +} + + + + + + + + +\textsc{\hyperlink{/mod/ + + }{ + + } +} + + + + + + + + + + +\fbox{\begin{tabular}{rr} +\begin{minipage}[t]{.49\linewidth} +\textbf{ + +} \\ + + + + \\ + + + +\end{minipage} & +\begin{minipage}[t]{.4\linewidth} +\textbf{ + +} \\ + + + + \\ + + + +\end{minipage} +\end{tabular}} +\smallskip + + + + + + + + + + \textbf{ + + }\begin{itemize} + + \item + + + + +\end{itemize} + + + + + + + + + +\section{ +} +\label{ +} + + + + + diff --git a/docs/manual/style/latex/directiveindex.xsl b/docs/manual/style/latex/directiveindex.xsl new file mode 100644 index 00000000..b97c346a --- /dev/null +++ b/docs/manual/style/latex/directiveindex.xsl @@ -0,0 +1,61 @@ + + + + + + + + + + + + + + + + + + + + + + \begin{itemize} + + + + + +\item + + (p.\ \pageref{/mod/ + : + + }) + + + \end{itemize} + + + + + diff --git a/docs/manual/style/latex/faq.xsl b/docs/manual/style/latex/faq.xsl new file mode 100644 index 00000000..5c00e7f2 --- /dev/null +++ b/docs/manual/style/latex/faq.xsl @@ -0,0 +1,43 @@ + + + + + +]> + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/latex/html.xsl b/docs/manual/style/latex/html.xsl new file mode 100644 index 00000000..c77f1ec3 --- /dev/null +++ b/docs/manual/style/latex/html.xsl @@ -0,0 +1,323 @@ + + + + + + + + + + + + +\begin{itemize} + + +\end{itemize} + + + + +\begin{enumerate} + + +\end{enumerate} + + + + +\item + + + + + + +\begin{description} + + +\end{description} + + + + +\item[ +] + + + + + + + + + + +\smallskip + + + + + \smallskip + + + + + \\ + + + + + + + + \\ + + + + + + + +\par + + + + +\texttt{ + +} + + + +\textbf{ + +} + + + +\textit{ + +} + + + + +\begin{verbatim} + + +\end{verbatim} + + + + +\begin{quotation} + + +\end{quotation} + + + + + + + + + longtable + tabular + + + +\begin{ +}{| + + + + l + + | + + + + + + l + + | + + + + +|}\hline + + +\hline\end{ + +} + + + + + + \\ + + \hline + + + + + + + + \begin{minipage}[t]{ + + + + + + + + + \textwidth}\small + + \end{minipage} + + & + + + + + + \begin{minipage}[t]{ + + + + + + + + + \textwidth}\bfseries + + \end{minipage} + + & + + + + + + + + + + + + + + + + + + + + + + + + \footnote{ + \href{ + + + + + + }{ + + + + }} + + + + + + + (p.\ \pageref{ + + + + + + + + + + + + + + + + + + + + + + }) + + + + + + + +\includegraphics{ + + + + + +} + + + diff --git a/docs/manual/style/latex/latex.xsl b/docs/manual/style/latex/latex.xsl new file mode 100644 index 00000000..76faf4a9 --- /dev/null +++ b/docs/manual/style/latex/latex.xsl @@ -0,0 +1,383 @@ + + + %HTTPD-VERSION; +]> + + + + + + + + + + + + + + + + + + + + + + + +\documentclass[10pt]{book} +\usepackage{times} +\usepackage{longtable} +\usepackage{style/latex/atbeginend} +\usepackage[pdftex]{graphicx} +\usepackage[colorlinks=true,letterpaper=true,linkcolor=blue,urlcolor=blue]{hyperref} + +% Let LaTeX be lenient about very-bad line wrapping. +\tolerance=9999 +\emergencystretch=60pt + +% Adjust margins to a reasonable level +\topmargin 0pt +\advance \topmargin by -\headheight +\advance \topmargin by -\headsep +\textheight 8.9in +\oddsidemargin 0pt +\evensidemargin \oddsidemargin +\marginparwidth 0.5in +\textwidth 6.5in + +% Keep paragraphs flush left (rather than the default of indenting +% the first line) and put a space between paragraphs. +\setlength{\parindent}{0ex} +\addtolength{\parskip}{1.2ex} + +% Shrink the inter-item spaces +\AfterBegin{itemize}{\setlength{\itemsep}{0em}} + +\pagestyle{headings} + +\hypersetup{ + pdftitle={ + + + + + + + +}, + pdfauthor={Apache Software Foundation} + } + +\title{ + + + + + + + +\\ \bigskip \bigskip +\includegraphics{images/feather}\\ \bigskip} +\author{Apache Software Foundation} +\date{\today} + +\begin{document} +\frontmatter +\maketitle + +\section*{About The PDF Documentation} + +Copyright \copyright 2005 The Apache Software Foundation + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at \href{http://www.apache.org/licenses/LICENSE-2.0}{http://www.apache.org/licenses/LICENSE-2.0} + +This version of the Apache HTTP Server Documentation is converted from +XML source files to \LaTeX\ using XSLT with the help of Apache Ant, +Apache XML Xalan, and Apache XML Xerces. + +Since the HTML version of the documentation is more commonly checked +during development, the PDF version may contain some errors and +inconsistencies, especially in formatting. If you have difficulty +reading a part of this file, please consult the HTML version +of the documentation on the Apache HTTP Server website at +\href{http://httpd.apache.org/docs/&httpd.docs;/}{http://httpd.apache.org/docs/&httpd.docs;/} + +The Apache HTTP Server Documentation is maintained by the Apache HTTP +Server Documentation Project. More information is available at +\href{http://httpd.apache.org/docs-project/}{http://httpd.apache.org/docs-project/} + +\tableofcontents +\mainmatter + + + + \chapter{ + + } + + + + + + + +\end{document} + + + +\include{ + + + + + + + + +} + + + + + + + + + + + + + + +\include{mod/ + +} + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/latex/manualpage.xsl b/docs/manual/style/latex/manualpage.xsl new file mode 100644 index 00000000..172e54b7 --- /dev/null +++ b/docs/manual/style/latex/manualpage.xsl @@ -0,0 +1,35 @@ + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/latex/moduleindex.xsl b/docs/manual/style/latex/moduleindex.xsl new file mode 100644 index 00000000..2824d607 --- /dev/null +++ b/docs/manual/style/latex/moduleindex.xsl @@ -0,0 +1,218 @@ + + + + + + + + + + + + + + + + + + + + + \subsection*{ + + } + +\begin{description} +\item[ + + ] (p.\ \pageref{/mod/ + + }) + + + + +\item[ + + + ] (p.\ \pageref{/mod/ + + }) + + + + + + + + + + + + + + + + +\item[ + + ] (p.\ \pageref{/mod/ + + }) + + + + + + \end{description} + + + + + + \section*{ + + } +\begin{description} + + + + + + + + + \end{description} + + + + + + + + + + + + + + + + + + + + + + +\item[ + +] (p.\ \pageref{/mod/ + +}) + + + + + + + + + + + + + + + + + + + + + + + +- + + + + + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/latex/quickreference.xsl b/docs/manual/style/latex/quickreference.xsl new file mode 100644 index 00000000..02a27e2a --- /dev/null +++ b/docs/manual/style/latex/quickreference.xsl @@ -0,0 +1,140 @@ + + + + + + + + + + + + + + + + + + + + + + + \footnotesize + + + \begin{longtable}{p{.60\textwidth}p{.25\textwidth}ll}\hline + + + + + + \texttt{ + + } + & + + + + + + + + + + + + + + + + + + + + + + + + + + + + + & + + s + v + d + h + + & + + B + M + C + E + X + + + \\* + + + \multicolumn{4}{l}{\begin{minipage}[t]{.95\textwidth} + + + + + + - + + + + \hfill p.\ \pageref{/mod/ + : + + } + + + \end{minipage}} \\ \hline + + + + + \end{longtable} +\normalsize + + + + + + + + diff --git a/docs/manual/style/latex/synopsis.xsl b/docs/manual/style/latex/synopsis.xsl new file mode 100644 index 00000000..74780ac9 --- /dev/null +++ b/docs/manual/style/latex/synopsis.xsl @@ -0,0 +1,346 @@ + + + + + + + + + + + + + +\section{ + + + + + + + + + + + + + + + + + + +}\label{ + +}\hypertarget{ + +}{} + + +\begin{tabular}{lp{.75\linewidth}} +\hline + + +: & + +\\ + + + +: & + +\\ + + + + +: & + +\\ + + + + + +: & + +\\ + + + + + +: & + + \\ + + +\hline \end{tabular} + + + + + \subsection*{ + + } + + + + + +\smallskip\textbf{ + + } + + + + + \begin{itemize} + + + \item + + \textless{} + + + + \textgreater{} + + + + (p.\ \pageref{/mod/ + + }) + + + + + \end{itemize} + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +\textless{} + +\textgreater{} + + + +\subsection*{ + + + + + + + + + + + +}\label{ + +}\hypertarget{ + +}{} + + + + + + + + +\begin{tabular}{lp{.8\linewidth}} +\hline + + +: & + +\\ + + + +: & {\ttfamily + +}\\ + + + + +: & {\ttfamily + +} \\ + + + + +: & + + \\ + + + + +: & + + \\ + + + + +: & + + \\ + + + +: & + + + + + + + + + \\ + + + + +: & + + \\ + + + +\hline +\end{tabular} + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + unknown context: + + + + + + , + + + + + + + + + + + + + , + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/manual.de.xsl b/docs/manual/style/manual.de.xsl new file mode 100644 index 00000000..0b1667ad --- /dev/null +++ b/docs/manual/style/manual.de.xsl @@ -0,0 +1,37 @@ + + + + + + + + + + +de + + + +ISO-8859-1 + + + + + + + \ No newline at end of file diff --git a/docs/manual/style/manual.en.xsl b/docs/manual/style/manual.en.xsl new file mode 100644 index 00000000..c3d88747 --- /dev/null +++ b/docs/manual/style/manual.en.xsl @@ -0,0 +1,37 @@ + + + + + + + + + + +en + + + +ISO-8859-1 + + + + + + + \ No newline at end of file diff --git a/docs/manual/style/manual.es.xsl b/docs/manual/style/manual.es.xsl new file mode 100644 index 00000000..e25c9703 --- /dev/null +++ b/docs/manual/style/manual.es.xsl @@ -0,0 +1,37 @@ + + + + + + + + + + +es + + + +ISO-8859-1 + + + + + + + \ No newline at end of file diff --git a/docs/manual/style/manual.fr.xsl b/docs/manual/style/manual.fr.xsl new file mode 100644 index 00000000..0a644415 --- /dev/null +++ b/docs/manual/style/manual.fr.xsl @@ -0,0 +1,37 @@ + + + + + + + + + + +fr + + + +ISO-8859-1 + + + + + + + \ No newline at end of file diff --git a/docs/manual/style/manual.ja.xsl b/docs/manual/style/manual.ja.xsl new file mode 100644 index 00000000..239141b2 --- /dev/null +++ b/docs/manual/style/manual.ja.xsl @@ -0,0 +1,37 @@ + + + + + + + + + + +ja + + + +EUC-JP + + + + + + + \ No newline at end of file diff --git a/docs/manual/style/manual.ko.xsl b/docs/manual/style/manual.ko.xsl new file mode 100644 index 00000000..b4e69d92 --- /dev/null +++ b/docs/manual/style/manual.ko.xsl @@ -0,0 +1,37 @@ + + + + + + + + + + +ko + + + +EUC-KR + + + + + + + \ No newline at end of file diff --git a/docs/manual/style/manual.pt-br.xsl b/docs/manual/style/manual.pt-br.xsl new file mode 100644 index 00000000..a6be5add --- /dev/null +++ b/docs/manual/style/manual.pt-br.xsl @@ -0,0 +1,37 @@ + + + + + + + + + + +pt-br + + + +ISO-8859-1 + + + + + + + \ No newline at end of file diff --git a/docs/manual/style/manual.ru.xsl b/docs/manual/style/manual.ru.xsl new file mode 100644 index 00000000..53adbad9 --- /dev/null +++ b/docs/manual/style/manual.ru.xsl @@ -0,0 +1,37 @@ + + + + + + + + + + +ru + + + +KOI8-R + + + + + + + \ No newline at end of file diff --git a/docs/manual/style/manualpage.dtd b/docs/manual/style/manualpage.dtd new file mode 100644 index 00000000..17742548 --- /dev/null +++ b/docs/manual/style/manualpage.dtd @@ -0,0 +1,27 @@ + + + + + +%common; + + + + + diff --git a/docs/manual/style/modulesynopsis.dtd b/docs/manual/style/modulesynopsis.dtd new file mode 100644 index 00000000..14f947a5 --- /dev/null +++ b/docs/manual/style/modulesynopsis.dtd @@ -0,0 +1,76 @@ + + + + + +%sitemap; + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/sitemap.dtd b/docs/manual/style/sitemap.dtd new file mode 100644 index 00000000..e47e8a9d --- /dev/null +++ b/docs/manual/style/sitemap.dtd @@ -0,0 +1,38 @@ + + + + + +%common; + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/version.ent b/docs/manual/style/version.ent new file mode 100644 index 00000000..0b722433 --- /dev/null +++ b/docs/manual/style/version.ent @@ -0,0 +1,24 @@ + + + + + + + + + diff --git a/docs/manual/style/xsl/common.xsl b/docs/manual/style/xsl/common.xsl new file mode 100644 index 00000000..993e301d --- /dev/null +++ b/docs/manual/style/xsl/common.xsl @@ -0,0 +1,1156 @@ + + + + + + +]> + + + + + + + + + + + + + + + + + + + + + + + p example note table ul ol dl pre img blockquote + + + + + + + + + + + + + + + + + + + + + + + + + + + index.html + + + + + + + + + + + + + + + + + + + + + + &lf; + + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + &lf; + + This file is generated from xml source: + DO NOT EDIT + &lf; + + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX + &lf; + + + + &lf; + + + <xsl:choose> + <xsl:when test="name"> + <xsl:value-of select="name"/> + </xsl:when> + + <xsl:otherwise> + <xsl:value-of select="title"/> + </xsl:otherwise> + </xsl:choose> + + <xsl:text> </xsl:text> + <xsl:value-of select="normalize-space($message[@id='apachetitle'])"/> + &lf; + + + + + + + + + &lf; + + + + &lf; + + + &lf; + + + + + &lf; + + + + + + + + + + + +
&lf; + &lf; + +

+ +

&lf; + + +
&lf; + +&lf; + +
&lf; + + + _blank + + + + + > + + + + _blank + + + + + > + + + + _blank + + + + + + > + + + + + + + + > + + + + + + + + > + + + + + + + + +
+ + + + + + + + + + &lf; +
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + +
&lf; +

+ + + : + + + + + + + + + + + + + + + + alternate + + + + + +   + +   + + + | + + +

&lf; +
+ + + + + + + + + + + + + + +&lf; +
&lf; + + +

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

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

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

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

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

+ + + + + + + + + + + + + + FATAL: exceeding maximum section nesting level. + &lf;&lf; + Perhaps you should consider to split your document into + &lf; + several ones... + &lf; + + + + + + + + + + + + + + + + + + + +
  • + + + + + + + + + + + + +
    • &lf; +     + + + + + + + +

    + + + + + | + + + + + + | + + + + + + | + + + + + + | + + + + +

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

    + + + + + +

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

    + +

    +     + + + + + + + + + + + + + + + + + + + +
    + + warning + + + +
    +     + + + + + + + +

    + +

    +     + + + + + + + + + + + + + + + + + + < + + > + + + + + < + + > + + + + + + + < + + > + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + + + +
    + +
      + +
    +     +     		+ +
      + +
    +     +
    +     + + + + + + + +
  • + +
    • +     +     + + + + + + + + +
  • + +
    • +     +     + + + + + + + + + + + bordered + + + + + + + + + + + + + +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + +&lf; + + + + + + + + + + + + + + + header + + + + odd + + + + +&lf; + + + + + + + + +
      + + + + up-A + + + lo-A + + + + +
    +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + top +
    +     + + + + + + + + + + ( + + + + + + ) + + + + + + + + + + + + [ + + ] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + Unknown element: + &lf; + Is the document valid (try `build validate-xml`)? + + + + + + + +
     + + + +

     +
     +
    •  +
     +
     +
     + + +
     + + + +
     + + + + + + + + + + + + + + + | + + + +   + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + _blank + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/xsl/convmap.xsl b/docs/manual/style/xsl/convmap.xsl new file mode 100644 index 00000000..da4444fe --- /dev/null +++ b/docs/manual/style/xsl/convmap.xsl @@ -0,0 +1,71 @@ + + + + + +]> + + + + + + + + + + + + + +# Mapping from directive names to URLs&lf; +# GENERATED FROM XML -- DO NOT EDIT&lf; +# You may use it as follows:&lf; +# RewriteEngine On&lf; +# RewriteMap dir2url +txt:/path/to/convenience.map&lf; +# RewriteCond ${dir2url:$1} (.+)&lf; +# RewriteRule ^/+([^/]+)$ /manual/%1 [R=301,NE,L]&lf;&lf; + + + + + + + + + + + + + + + mod/ + + .html# + + &lf; + + + + + diff --git a/docs/manual/style/xsl/directiveindex.xsl b/docs/manual/style/xsl/directiveindex.xsl new file mode 100644 index 00000000..1e13e7d6 --- /dev/null +++ b/docs/manual/style/xsl/directiveindex.xsl @@ -0,0 +1,130 @@ + + + + + +]> + + + + + + + + + &lf; + + + + + + + + + + + + + +
    +

    + +

    &lf; + + &lf; + + &lf; + + +

    + + + + +

    &lf; +
    &lf; + +
    +
      &lf; + + + + +
    +
    &lf; + + &lf; + + +     + + + + + + + + + + + + + + + +
  • + + + + + + + + + + + < + + > + +
    • &lf; +     + + + + + + + + + +     + + +     diff --git a/docs/manual/style/xsl/faq.xsl b/docs/manual/style/xsl/faq.xsl new file mode 100644 index 00000000..2cd3d3bb --- /dev/null +++ b/docs/manual/style/xsl/faq.xsl @@ -0,0 +1,199 @@ + + + + + +]> + + + + + + + + + &lf; + + + + + no-sidebar + + + + +
    +
    +

    + +

    &lf; + + &lf; + + +
    &lf; + + +
    + + +
      + +
    +     + + +
      +
    • + + + + + +
      • &lf; + + +
    +     +     + + +

    + +

    + +
      + +
    • + +
      • +       +
    +     +
    &lf; +     + + + + + +
    &lf; + + &lf; + + +     + + + + + + +&lf; + +
    &lf; + + +

    + + + +

    &lf; + +
    + +
    +
    + + + + +     + + + + + + + + + +
    + + + + + + + + + + + + + + +
    +
    + +
    &lf; +     + + + + + + + + + + +
  • + + + + + +
    • &lf; +     + + + + + + + + + + + + +     diff --git a/docs/manual/style/xsl/hhc.xsl b/docs/manual/style/xsl/hhc.xsl new file mode 100644 index 00000000..c9fde798 --- /dev/null +++ b/docs/manual/style/xsl/hhc.xsl @@ -0,0 +1,668 @@ + + + + + + + + + + + +]> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<html><head> +<title>Apache HTTP Server Documentation</title> +</head>&lf; + +<body>&lf; + + +<object type="text/site properties">&lf;&tab; + +<param name="Window Styles" value="0x800027">&lf;&tab; +<param name="Font" value=" + +">&lf; +</object>&lf; + +&ul.start; &lf; + + + &li.start; + + + + + + &li.end; &lf; + + + + &li.start; + + + &lf;&tab; + + &ul.start; &lf;&tab; + + + + + &ul.end; &lf; + &li.end; &lf;&tab; + &lf; + +&ul.end; &lf; + +</body></html>&lf; + + + + + + + + +&li.start; + + + + + + + + + + + + + + + + + sitemap.html + + + + + + + + + + + + + + + +&li.end; &lf;&tab; + + + + + + + + + + + + + sitemap.html + + + + + + + + + + + + + + + + + + + + + + + + + + + &lf;&tab;&tab;&tab; + &ul.start; &lf;&tab;&tab;&tab; + + + &li.start; + + + + + + + + + + + + &li.end; &lf;&tab;&tab; + + + &ul.end; &lf;&tab; + + + + + + + + + + + + + + - + + + + + + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +&li.start; + + + + + + + + + + + + + + + + + + + + + + + + + +&li.end; &lf;&tab; + + + + + + + + + + + +&li.start; + + + + + + + + + + + + + + + +&li.end; &lf;&tab; + + + + + + + + + + + + + &lf;&tab;&tab; + + &ul.start; &lf;&tab;&tab; + + + + &li.start; + + + + + + + + + + + + &li.end; &lf;&tab;&tab; + + + + + + &li.start; + + + + < + + > + + + + + + + + + + + + + + + + &li.end; &lf;&tab;&tab; + + + + + + &li.start; + + + + < + + > + + + + + + + + + + + + + + + + &li.end; &lf;&tab;&tab; + + + &ul.end; &lf;&tab; + + + + + + + + + + + + + + + + + + + + + + + + +<object type="text/sitemap">&lf; + + +<param name="Name" value=" + + + +">&lf; + + + + <param name="Local" value=" + + + + ">&lf; + + + +<param name="ImageNumber" value=" + + + + + + + + + + + + + + + + + + +">&lf; + + +</object> + + + + + + + + + + +<object type="text/sitemap">&lf;&tab;&tab; +<param name="Name" value=" + + + +">&lf;&tab; +</object> + + + + + + + + + + + + + + + + index.html# + + + + + index.html + + + + + + + + + + + + + + + + + + + + + + &amp; + + + + + + + + + + + + + + + + + + + + + + + + + &lt; + + + + + + + &gt; + + + + + + + &quot; + + + + + + + + + + + + diff --git a/docs/manual/style/xsl/hhp.xsl b/docs/manual/style/xsl/hhp.xsl new file mode 100644 index 00000000..369377e8 --- /dev/null +++ b/docs/manual/style/xsl/hhp.xsl @@ -0,0 +1,316 @@ + + + + + +]> + + + + + + + + + + + + + + + + + +[OPTIONS]&lf; +Binary TOC=No&lf; +Compatibility=1.0&lf; + + +Compiled file=httpd-docs- + +. + +.chm&lf; + +Contents file=toc.hhc&lf; +Default Window=Main&lf; +Default topic=index.html&lf; + + +Display compile progress=Yes&lf; +Enhanced decompilation=Yes&lf; + + +Full-text search=Yes&lf; +Language= +&lf; + + +Title= +&lf;&lf; + + +[WINDOWS]&lf; +Main= + + +" + +", + + +"toc.hhc", + + +, + + +"index.html", + + +"index.html", + + +,, + + +,, + + + + + +, + + +180, + + + + + +, + + +[0,0,600,380], + + + + + + +, + + +, + + +, + + +,,,0&lf;&lf; + + + +[FILES]&lf; + + +style\css\manual.css&lf; +style\css\manual-loose-100pc.css&lf; + + +manual.hhp&lf; + + + + + + + +&lf; + + + + + + + + + + + + + index.html + + + + index.html + + + + + + + +&lf; + + + + + + + + +mod\ + +.html&lf; + + + + + + + + + + + + + + + + + + + + + + + + 0x + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/style/xsl/indexpage.xsl b/docs/manual/style/xsl/indexpage.xsl new file mode 100644 index 00000000..d62814bf --- /dev/null +++ b/docs/manual/style/xsl/indexpage.xsl @@ -0,0 +1,211 @@ + + + + + +]> + + + + + + + + + + + + + + + + + + + &lf; + + &lf; + &lf; + +
    +

    + +

    &lf; + + &lf; + +
    + + &lf; + + + + + + + +
    + + + + + +
    +
    &lf; + + &lf; + + +     + + + + + + + +
  • + + separate + + + + + + + + + + + + + + + + +
    • &lf; +     + + + + + + + +
    + +

    + + + + + + + + + +

    &lf; + + +
      + +
    &lf; +
    +     + + + + + + + + +get +http://www.google.com/search + + _blank + + +

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

    +     + + +     diff --git a/docs/manual/style/xsl/language.xsl b/docs/manual/style/xsl/language.xsl new file mode 100644 index 00000000..8ef0b4a0 --- /dev/null +++ b/docs/manual/style/xsl/language.xsl @@ -0,0 +1,658 @@ + + + + + + +]> + + + + + + + + + + + + + + + + + &lf; + + + + + &lf; + + + + + + + + + + + + + + + + + + + + &lf; + + + + + + + + + + + + + + + + + &lf; + + + + + + &lf; + + + &lf; + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + &lf;&lf; + + + + + + + + , + + + + &lf; + + + + + zip- + + , + + + + &lf; + + + + + war- + + , + + + + &lf; + + + + + + + + + &lf; + + + + + + &lf; + &lf;&lf; + + + &lf; + + &lf; + + + &lf; + + + &lf; + + &lf; + + &lf; + + &lf; + + &lf; + + &lf; + + &lf; + + &lf; + + &lf; + + &lf; + + &lf; + + &lf; + + + &lf; + + &lf; + + &lf; + + + + &lf; + + &lf; + + &lf; + + + + &lf; + + &lf; + + &lf; + + + + &lf; + + + + + + + + + + + + + + + + &lf; + + + &lf; + + &lf; + + &lf; + + + + + + + &lf; + + + &lf; + + &lf; + + &lf; + + + &lf; + + + &lf; + + &lf;&lf; + + + + + + + + + + + &lf; + + + + + + ../../../mod/allmodules + + + &lf; + + + + + + + + + + + + + +This build file contains all operations that are necessary for building +the Apache httpd documentation. It is called by invoking build.bat (Win32) +or build.sh (/bin/sh systems) with a target argument (full list below). +For example, if you want to build the Japanese HTML files, type: + + ./build.sh ja + +Some targets have additional requirements: + +* 'metafiles' and 'modulelists' need perl in PATH. (It's checked automatically + and skipped if perl is not available) + +* 'chm-foo' targets need: + - the HTML Help compiler in PATH (or modify this build file). The + compiler (hhc.exe) is part of the HTML Help Workshop which is freely + available and can be downloaded from + http://msdn.microsoft.com/library/en-us/htmlhelp/html/hwMicrosoftHTMLHelpDownloads.asp + - The appropriate locale (e.g. Japanese) before invoking hhc.exe. Otherwise + the compiler is not able to build the fulltext search index correctly and + the TOC may be garbled, too. In particular: + + + + + + + + + + chm- + + : + + &lf; + + + &lf; + + + + + + + + + + + + + + 1.0 + &lf; + &lf; + + + + + + xml + + + text + + + + Unknown style type ' + + '! + + + + + + + + + + + + + + + + + + no + + + -//W3C//DTD XHTML 1.0 Strict//EN + + + + + http://www.w3.org/TR/xhtml1/DTD/ + xhtml1-strict.dtd + + + + yes + + + &lf;&lf; + + + Read the localized messages from the specified + language file + + &lf; + + + message + + document(' + ../ + lang/ + + .xml')/language/messages/message + + + &lf; + + + + doclang + + + &lf; + + allmodules + + document(' + ../ + xsl/util/allmodules.xml') + /items/item[@lang=$doclang] + + + &lf; + + &lf; + + + + some meta information have to be passed to + the transformation + + &lf; + + + + + output-encoding + + + + + + + + + + &lf; + + + + + is-chm + + + + true() + + + false() + + + + + &lf; + + + is-zip + + + + true() + + + false() + + + + + &lf;&lf; + + + + + toc-font + + + &lf; + + + xml-ext + + + &lf;&lf; + + + + + hhp-lang + + + &lf;&lf; + + + Now get the real guts of the stylesheet + &lf; + + + + + + ../xsl/common.xsl + + + ../xsl/hhc.xsl + + + ../xsl/hhp.xsl + + + ../xsl/nroff.xsl + + + xsl/common.xsl + + + + + &lf;&lf; + + + + + + + +&lf; + + Licensed to the Apache Software Foundation (ASF) under one or more + contributor license agreements. See the NOTICE file distributed with + this work for additional information regarding copyright ownership. + The ASF licenses this file to You under the Apache License, Version 2.0 + (the "License"); you may not use this file except in compliance with + the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. + +&lf;&lf; + + + + +============================================ +======================== + + + + + + + + + +&lf; + + + + + + + + + + + + + +&lf; + + + diff --git a/docs/manual/style/xsl/maf.xsl b/docs/manual/style/xsl/maf.xsl new file mode 100644 index 00000000..f7718bd6 --- /dev/null +++ b/docs/manual/style/xsl/maf.xsl @@ -0,0 +1,56 @@ + + + + + +]> + + + + + + + + + + + + + +&lf; + &lf; + &lf; + &lf; + + &lf; + + &lf; + &lf; +&lf; + + + + diff --git a/docs/manual/style/xsl/manualpage.xsl b/docs/manual/style/xsl/manualpage.xsl new file mode 100644 index 00000000..30cc9d10 --- /dev/null +++ b/docs/manual/style/xsl/manualpage.xsl @@ -0,0 +1,87 @@ + + + + + +]> + + + + + + + + + &lf; + + + + + no-sidebar + + + + +
    +
    +

    + +

    &lf; + + &lf; + + +
    &lf; + + +
    + +
      + +
    +     + + +

    + +

    +
      + +
    • + +
      • +       +
    +     +
    &lf; +     + + +
    &lf; + + &lf; + + +     + + +     diff --git a/docs/manual/style/xsl/moduleindex.xsl b/docs/manual/style/xsl/moduleindex.xsl new file mode 100644 index 00000000..e3651a45 --- /dev/null +++ b/docs/manual/style/xsl/moduleindex.xsl @@ -0,0 +1,333 @@ + + + + + +]> + + + + + + + + + &lf; + + + + +
    +
    +

    + +

    &lf; + + &lf; + + +
    &lf; + + +
    + + + + + +

    + +

    &lf; + +
      &lf; + +
    • + +
      • &lf; +       +
    +     +
    +     &lf; + + &lf; + +
    +

    + + + +

    &lf; + + +
    &lf; +
    + + + +
    +
    + +
    &lf; + + +
    + + + +
    +
    + +
    &lf; + + + + + + + + + + + + +
    + + + +
    +
    + +
    &lf; +     +
    +
    &lf; + + &lf; + +
    +

    + + + +

    &lf; + + + + + + + + + +

    + + + + +

    &lf; + +
    + + + + +
    +
    +
    &lf; + + &lf; + + +     + + + + + + + + + + + + + + + + + + + + + +
    + + + + + + + + + + + + +
    +
    + +
    &lf; +     + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +- + + + + + + + + + + - + + + + +     diff --git a/docs/manual/style/xsl/nroff.xsl b/docs/manual/style/xsl/nroff.xsl new file mode 100644 index 00000000..074d7fca --- /dev/null +++ b/docs/manual/style/xsl/nroff.xsl @@ -0,0 +1,448 @@ + + + + + + + +]> + + + + + + + + + + + + + + + + + + +.\" XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&lf; +.\" DO NOT EDIT! Generated from XML source.&lf; +.\" XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&lf; +.de Sh \" Subsection&lf; +.br&lf; +.if t .Sp&lf; +.ne 5&lf; +.PP&lf; +\fB\\$1\fR&lf; +.PP&lf; +..&lf; +.de Sp \" Vertical space (when we can't use .PP)&lf; +.if t .sp .5v&lf; +.if n .sp&lf; +..&lf; +.de Ip \" List item&lf; +.br&lf; +.ie \\n(.$>=3 .ne \\$3&lf; +.el .ne 3&lf; +.IP "\\$1" \\$2&lf; +..&lf; + + +.TH " + + +" + + + + " + + + +" " + + + +" " + + + +"&lf; + + +&lf; +&lf; +&lf; +&lf; + + + + + + + + + +&lf; +.SH NAME&lf; + + + + + + + \- + + + + + + + + + + +&lf; +.PP&lf; + + + + + + + + + + + + + + + + + + + + + + +&lf; + + + + + + + + + +&lf; +.SH " + + + +"&lf; + + + + + + + + + + + +&lf; +.SS " + + + +"&lf; + + + + + + + + + + +&lf; +.SH " + + + +"&lf; + + + + + + + + + + +\fI + +\fR + + + + + + + + +\fB + +\fR + + + + + + + +< + +> + + + + + + + +&lf; +&lf; + + + + + + + +&lf; +.TP&lf; + + + + +&lf; + + + + + + + + + + + + + + + + + +&lf; +.nf&lf; +&lf; +.fi&lf; + + + + + + + + + + +FATAL: only tables with two (2) columns are supported. + + + +&lf; +.Ip "\(bu \s-1 + + + + + +\s0 \- + + + +&lf; + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +FATAL: the behaviour of the <> +element was not tested. You need to modify +the XSLT stylesheet in order to get it work. + + + + + + + + + + + + + + + + + \\ + + + + + + + + + + + + + + + + + + + + + + + + + \&. + + + + + + + + + + + + diff --git a/docs/manual/style/xsl/quickreference.xsl b/docs/manual/style/xsl/quickreference.xsl new file mode 100644 index 00000000..cf255dcd --- /dev/null +++ b/docs/manual/style/xsl/quickreference.xsl @@ -0,0 +1,210 @@ + + + + + +]> + + + + + + + + + &lf; + + &lf; + &lf; + +
    +

    + +

    &lf; + + &lf; + + +
    &lf; + +
    + + + + + + + + + &lf; + + &lf; + &lf; + + &lf; +
    + + + + + + + + + + +
    &lf; + + &lf; + + + + + +
    +
    &lf; + + &lf; + + +     + + + + + + + + + + + + + + + + + + + + odd + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + s + v + d + h + + + + B + M + C + E + X + + + + + + odd + + + + + + + + + - + + + + &lf; + + + + + + + + + + + + + +     diff --git a/docs/manual/style/xsl/sitemap.xsl b/docs/manual/style/xsl/sitemap.xsl new file mode 100644 index 00000000..eaa2c413 --- /dev/null +++ b/docs/manual/style/xsl/sitemap.xsl @@ -0,0 +1,242 @@ + + + + + +]> + + + + + + + + + &lf; + + &lf; + &lf; + +
    +
    +

    + +

    &lf; + + &lf; + + +
    &lf; + + +
    + +
      &lf; + + + +
    • + + + + + +
      • &lf; +       + +
    • + + + +
      • &lf; +       +       +       +
    &lf; +     + + +

    + +

    &lf; + +
      &lf; + +
    • + +
      • &lf; +       +
    &lf; +     +
    &lf; +     + + +
    &lf; + + &lf; + + +     + + + + + + + +
  • + + separate + + + + + + + + + + + + + + + +
    • &lf; +     + + + + + + + +&lf; + +
    + +

    + + + + + + + + + + +

    &lf; + + +
      + +
    + + + + + + &lf; +
    +     + + + + + + + + + + - + + + + + + + + + + - + + + + + + + + + +     diff --git a/docs/manual/style/xsl/synopsis.xsl b/docs/manual/style/xsl/synopsis.xsl new file mode 100644 index 00000000..d0769012 --- /dev/null +++ b/docs/manual/style/xsl/synopsis.xsl @@ -0,0 +1,508 @@ + + + + + +]> + + + + + + + + + &lf; + + &lf; + &lf; + +
    &lf; +
    +

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

    &lf; + + &lf; + + + + + + + &lf; + + + + + + &lf; + + + + + + + &lf; + + + + + + + &lf; + + + + + +
    + + + : + + + +
    + + + : + + + +
    + + + : + + + +
    + + + : + + + +
    + + + : + + + +
    &lf; + + + + +

    + +

    &lf; + + +     +
    &lf; + + +
    + +

    + +

    &lf; + + + + &lf; + + + +

    + +

    &lf; +     +     + + +

    + +

    &lf; + +
      &lf; + +
    +     +     + + +

    + +

    &lf; + +
      &lf; + +
    • + +
      • &lf; +       +
    +     +
    +     &lf; + + + &lf; + + + + + +
    &lf; + + &lf; + + +     + + + + + + + + + &lf; + +
    + + + + +

    + + < + + > + + + + + + + + + + + + + + +

    &lf; + + + &lf; + + + + &lf; + + + + + + + &lf; + + + + + &lf; + + + + + + + &lf; + + + + + &lf; + + + + + &lf; + + + + + + + &lf; + + + + + &lf; +
    + + + : + + + +
    + + + : + + + + + +
    + + + : + + + + + +
    + + + : + + + +
    + + + : + + + +
    + + + : + + + +
    + + + : + + + + + + + + + + +
    + + + : + + + +
    + + &lf; + + +

    + +

    &lf; + +
      &lf; + +
    • + +
      • &lf; +       +
    &lf; +     +
    &lf; +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + unknown context: + + + + + + , + + + + + + + + + + + + + , + + + + + + + + + + + + + + + + + + + + + +     diff --git a/docs/manual/style/xsl/typemap.xsl b/docs/manual/style/xsl/typemap.xsl new file mode 100644 index 00000000..4429e7ab --- /dev/null +++ b/docs/manual/style/xsl/typemap.xsl @@ -0,0 +1,80 @@ + + + + + +]> + + + + + + + + + + + + + + + + + + + + + + + + + + + + +FATAL: missing designation data for language . +The XSLT-Stylesheet won't work without modification. + + + +URI: + +&lf; + +Content-Language: +&lf; + +Content-type: text/html; charset= +&lf; + +&lf; + + + + diff --git a/docs/manual/style/xsl/util/modtrans.xsl b/docs/manual/style/xsl/util/modtrans.xsl new file mode 100644 index 00000000..291f49ba --- /dev/null +++ b/docs/manual/style/xsl/util/modtrans.xsl @@ -0,0 +1,44 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/manual/suexec.html b/docs/manual/suexec.html new file mode 100644 index 00000000..9d5e3a86 --- /dev/null +++ b/docs/manual/suexec.html @@ -0,0 +1,11 @@ +URI: suexec.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: suexec.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: suexec.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/suexec.html.en b/docs/manual/suexec.html.en new file mode 100644 index 00000000..a73b7bc3 --- /dev/null +++ b/docs/manual/suexec.html.en @@ -0,0 +1,608 @@ + + + +suEXEC Support - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    suEXEC Support

    +
    +

    Available Languages:  en  | + ja  | + ko 

    +
    + +

    The suEXEC feature provides + Apache users the ability + to run CGI and SSI programs + under user IDs different from the user ID of the calling + web server. Normally, when a CGI or SSI program executes, it + runs as the same user who is running the web server.

    + +

    Used properly, this feature can reduce + considerably the security risks involved with allowing users to + develop and run private CGI or SSI programs. However, if suEXEC + is improperly configured, it can cause any number of problems + and possibly create new holes in your computer's security. If + you aren't familiar with managing setuid root programs + and the security issues they present, we highly recommend that + you not consider using suEXEC.

    +
    + +
    top
    +
    +

    Before we begin

    + +

    Before jumping head-first into this document, + you should be aware of the assumptions made on the part of the + Apache Group and this document.

    + +

    First, it is assumed that you are using a UNIX + derivative operating system that is capable of + setuid and setgid operations. + All command examples are given in this regard. Other platforms, + if they are capable of supporting suEXEC, may differ in their + configuration.

    + +

    Second, it is assumed you are familiar with + some basic concepts of your computer's security and its + administration. This involves an understanding of + setuid/setgid operations and the various + effects they may have on your system and its level of + security.

    + +

    Third, it is assumed that you are using an + unmodified version of suEXEC code. All code + for suEXEC has been carefully scrutinized and tested by the + developers as well as numerous beta testers. Every precaution + has been taken to ensure a simple yet solidly safe base of + code. Altering this code can cause unexpected problems and new + security risks. It is highly recommended you + not alter the suEXEC code unless you are well versed in the + particulars of security programming and are willing to share + your work with the Apache Group for consideration.

    + +

    Fourth, and last, it has been the decision of + the Apache Group to NOT make suEXEC part of + the default installation of Apache. To this end, suEXEC + configuration requires of the administrator careful attention + to details. After due consideration has been given to the + various settings for suEXEC, the administrator may install + suEXEC through normal installation methods. The values for + these settings need to be carefully determined and specified by + the administrator to properly maintain system security during + the use of suEXEC functionality. It is through this detailed + process that the Apache Group hopes to limit suEXEC + installation only to those who are careful and determined + enough to use it.

    + +

    Still with us? Yes? Good. Let's move on!

    +
    top
    +
    +

    suEXEC Security Model

    + +

    Before we begin configuring and installing + suEXEC, we will first discuss the security model you are about + to implement. By doing so, you may better understand what + exactly is going on inside suEXEC and what precautions are + taken to ensure your system's security.

    + +

    suEXEC is based on a setuid + "wrapper" program that is called by the main Apache web server. + This wrapper is called when an HTTP request is made for a CGI + or SSI program that the administrator has designated to run as + a userid other than that of the main server. When such a + request is made, Apache provides the suEXEC wrapper with the + program's name and the user and group IDs under which the + program is to execute.

    + +

    The wrapper then employs the following process + to determine success or failure -- if any one of these + conditions fail, the program logs the failure and exits with an + error, otherwise it will continue:

    + +
      +
    1. + Is the user executing this wrapper a valid user of + this system? + +

      + This is to ensure that the user executing the wrapper is + truly a user of the system. +

      +
      2. + +
    2. + Was the wrapper called with the proper number of + arguments? + +

      + The wrapper will only execute if it is given the proper + number of arguments. The proper argument format is known + to the Apache web server. If the wrapper is not receiving + the proper number of arguments, it is either being + hacked, or there is something wrong with the suEXEC + portion of your Apache binary. +

      +
      3. + +
    3. + Is this valid user allowed to run the + wrapper? + +

      + Is this user the user allowed to run this wrapper? Only + one user (the Apache user) is allowed to execute this + program. +

      +
      4. + +
    4. + Does the target CGI or SSI program have an unsafe + hierarchical reference? + +

      + Does the target CGI or SSI program's path contain a leading + '/' or have a '..' backreference? These are not allowed; the + target CGI/SSI program must reside within suEXEC's document + root (see --with-suexec-docroot=DIR + below). +

      +
      5. + +
    5. + Is the target user name valid? + +

      + Does the target user exist? +

      +
      6. + +
    6. + Is the target group name valid? + +

      + Does the target group exist? +

      +
      7. + +
    7. + Is the target user NOT superuser? + + +

      + Presently, suEXEC does not allow root + to execute CGI/SSI programs. +

      +
      8. + +
    8. + Is the target userid ABOVE the minimum ID + number? + +

      + The minimum user ID number is specified during + configuration. This allows you to set the lowest possible + userid that will be allowed to execute CGI/SSI programs. + This is useful to block out "system" accounts. +

      +
      9. + +
    9. + Is the target group NOT the superuser + group? + +

      + Presently, suEXEC does not allow the root + group to execute CGI/SSI programs. +

      +
      10. + +
    10. + Is the target groupid ABOVE the minimum ID + number? + +

      + The minimum group ID number is specified during + configuration. This allows you to set the lowest possible + groupid that will be allowed to execute CGI/SSI programs. + This is useful to block out "system" groups. +

      +
      11. + +
    11. + Can the wrapper successfully become the target user + and group? + +

      + Here is where the program becomes the target user and + group via setuid and setgid calls. The group access list + is also initialized with all of the groups of which the + user is a member. +

      +
      12. + +
    12. + Can we change directory to the one in which the target + CGI/SSI program resides? + +

      + If it doesn't exist, it can't very well contain files. If we + can't change directory to it, it might aswell not exist. +

      +
      13. + +
    13. + Is the directory within the Apache + webspace? + +

      + If the request is for a regular portion of the server, is + the requested directory within suEXEC's document root? If + the request is for a UserDir, is the requested directory + within the directory configured as suEXEC's userdir (see + suEXEC's configuration options)? +

      +
      14. + +
    14. + Is the directory NOT writable by anyone + else? + +

      + We don't want to open up the directory to others; only + the owner user may be able to alter this directories + contents. +

      +
      15. + +
    15. + Does the target CGI/SSI program exist? + +

      + If it doesn't exists, it can't very well be executed. +

      +
      16. + +
    16. + Is the target CGI/SSI program NOT writable + by anyone else? + +

      + We don't want to give anyone other than the owner the + ability to change the CGI/SSI program. +

      +
      17. + +
    17. + Is the target CGI/SSI program NOT setuid or + setgid? + +

      + We do not want to execute programs that will then change + our UID/GID again. +

      +
      18. + +
    18. + Is the target user/group the same as the program's + user/group? + +

      + Is the user the owner of the file? +

      +
      19. + +
    19. + Can we successfully clean the process environment + to ensure safe operations? + +

      + suEXEC cleans the process' environment by establishing a + safe execution PATH (defined during configuration), as + well as only passing through those variables whose names + are listed in the safe environment list (also created + during configuration). +

      +
      20. + +
    20. + Can we successfully become the target CGI/SSI program + and execute? + +

      + Here is where suEXEC ends and the target CGI/SSI program begins. +

      +
      21. +
    + +

    This is the standard operation of the + suEXEC wrapper's security model. It is somewhat stringent and + can impose new limitations and guidelines for CGI/SSI design, + but it was developed carefully step-by-step with security in + mind.

    + +

    For more information as to how this security + model can limit your possibilities in regards to server + configuration, as well as what security risks can be avoided + with a proper suEXEC setup, see the "Beware the Jabberwock" section of this + document.

    +
    top
    +
    +

    Configuring & Installing + suEXEC

    + +

    Here's where we begin the fun.

    + +

    suEXEC configuration + options
    +

    + +
    +
    --enable-suexec
    + +
    This option enables the suEXEC feature which is never + installed or activated by default. At least one + --with-suexec-xxxxx option has to be provided + together with the --enable-suexec option to let + APACI accept your request for using the suEXEC feature.
    + +
    --with-suexec-bin=PATH
    + +
    The path to the suexec binary must be hard-coded + in the server for security reasons. Use this option to override + the default path. e.g. + --with-suexec-bin=/usr/sbin/suexec
    + +
    --with-suexec-caller=UID
    + +
    The username under which + Apache normally runs. This is the only user allowed to + execute this program.
    + +
    --with-suexec-userdir=DIR
    + +
    Define to be the subdirectory under users' home + directories where suEXEC access should be allowed. All + executables under this directory will be executable by suEXEC + as the user so they should be "safe" programs. If you are + using a "simple" UserDir directive (ie. one without a "*" in + it) this should be set to the same value. suEXEC will not + work properly in cases where the UserDir directive points to + a location that is not the same as the user's home directory + as referenced in the passwd file. Default value is + "public_html".
    + If you have virtual hosts with a different UserDir for each, + you will need to define them to all reside in one parent + directory; then name that parent directory here. If + this is not defined properly, "~userdir" cgi requests will + not work!
    + +
    --with-suexec-docroot=DIR
    + +
    Define as the DocumentRoot set for Apache. This will be + the only hierarchy (aside from UserDirs) that can be used for + suEXEC behavior. The default directory is the --datadir + value with the suffix "/htdocs", e.g. if you configure + with "--datadir=/home/apache" the directory + "/home/apache/htdocs" is used as document root for the suEXEC + wrapper.
    + +
    --with-suexec-uidmin=UID
    + +
    Define this as the lowest UID allowed to be a target user + for suEXEC. For most systems, 500 or 100 is common. Default + value is 100.
    + +
    --with-suexec-gidmin=GID
    + +
    Define this as the lowest GID allowed to be a target + group for suEXEC. For most systems, 100 is common and + therefore used as default value.
    + +
    --with-suexec-logfile=FILE
    + +
    This defines the filename to which all suEXEC + transactions and errors are logged (useful for auditing and + debugging purposes). By default the logfile is named + "suexec_log" and located in your standard logfile directory + (--logfiledir).
    + +
    --with-suexec-safepath=PATH
    + +
    Define a safe PATH environment to pass to CGI + executables. Default value is + "/usr/local/bin:/usr/bin:/bin".
    +
    + +

    Compiling and installing the suEXEC + wrapper
    + If you have enabled the suEXEC feature with the + --enable-suexec option the suexec binary + (together with Apache itself) is automatically built if you execute + the make command.
    + After all components have been built you can execute the + command make install to install them. The binary image + suexec is installed in the directory defined by the + --sbindir option. The default location is + "/usr/local/apache2/sbin/suexec".
    + Please note that you need root + privileges for the installation step. In order + for the wrapper to set the user ID, it must be installed as + owner root and must have the setuserid + execution bit set for file modes.

    + +

    Setting paranoid permissions
    + Although the suEXEC wrapper will check to ensure that its + caller is the correct user as specified with the + --with-suexec-caller configure + option, there is + always the possibility that a system or library call suEXEC uses + before this check may be exploitable on your system. To counter + this, and because it is best-practise in general, you should use + filesystem permissions to ensure that only the group Apache + runs as may execute suEXEC.

    + +

    If for example, your web server is configured to run as:

    + +

    + User www
    + Group webgroup
    +

    + +

    and suexec is installed at + "/usr/local/apache2/sbin/suexec", you should run:

    + +

    + chgrp webgroup /usr/local/apache2/bin/suexec
    + chmod 4750 /usr/local/apache2/bin/suexec
    +

    + +

    This will ensure that only the group Apache runs as can even + execute the suEXEC wrapper.

    +
    top
    +
    +

    Enabling & Disabling + suEXEC

    + +

    Upon startup of Apache, it looks for the file + suexec in the directory defined by the + --sbindir option (default is + "/usr/local/apache/sbin/suexec"). If Apache finds a properly + configured suEXEC wrapper, it will print the following message + to the error log:

    + +

    + [notice] suEXEC mechanism enabled (wrapper: /path/to/suexec) +

    + +

    If you don't see this message at server startup, the server is + most likely not finding the wrapper program where it expects + it, or the executable is not installed setuid root.

    + +

    If you want to enable the suEXEC mechanism for the first time + and an Apache server is already running you must kill and + restart Apache. Restarting it with a simple HUP or USR1 signal + will not be enough.

    +

    If you want to disable suEXEC you should kill and restart + Apache after you have removed the suexec file.

    +
    top
    +
    +

    Using suEXEC

    + +

    Requests for CGI programs will call the suEXEC wrapper only if + they are for a virtual host containing a SuexecUserGroup directive or if + they are processed by mod_userdir.

    + +

    Virtual Hosts:
    One way to use the suEXEC + wrapper is through the SuexecUserGroup directive in + VirtualHost definitions. By + setting this directive to values different from the main server + user ID, all requests for CGI resources will be executed as the + User and Group defined for that <VirtualHost>. If this + directive is not specified for a <VirtualHost> then the main server userid + is assumed.

    + +

    User directories:
    Requests that are + processed by mod_userdir will call the suEXEC + wrapper to execute CGI programs under the userid of the requested + user directory. The only requirement needed for this feature to + work is for CGI execution to be enabled for the user and that the + script must meet the scrutiny of the security + checks above. See also the + --with-suexec-userdir compile + time option.

    top
    +
    +

    Debugging suEXEC

    + +

    The suEXEC wrapper will write log information + to the file defined with the --with-suexec-logfile + option as indicated above. If you feel you have configured and + installed the wrapper properly, have a look at this log and the + error_log for the server to see where you may have gone astray.

    + +
    top
    +
    +

    Beware the Jabberwock: + Warnings & Examples

    + +

    NOTE! This section may not be + complete. For the latest revision of this section of the + documentation, see the Apache Group's Online + Documentation version.

    + +

    There are a few points of interest regarding + the wrapper that can cause limitations on server setup. Please + review these before submitting any "bugs" regarding suEXEC.

    + +
      +
    • suEXEC Points Of Interest
      • + +
    • + Hierarchy limitations + +

      + For security and efficiency reasons, all suEXEC requests + must remain within either a top-level document root for + virtual host requests, or one top-level personal document + root for userdir requests. For example, if you have four + VirtualHosts configured, you would need to structure all + of your VHosts' document roots off of one main Apache + document hierarchy to take advantage of suEXEC for + VirtualHosts. (Example forthcoming.) +

      +
      • + +
    • + suEXEC's PATH environment variable + +

      + This can be a dangerous thing to change. Make certain + every path you include in this define is a + trusted directory. You don't want to + open people up to having someone from across the world + running a trojan horse on them. +

      +
      • + +
    • + Altering the suEXEC code + +

      + Again, this can cause Big Trouble if you + try this without knowing what you are doing. Stay away + from it if at all possible. +

      +
      • +
    + +
    +
    +

    Available Languages:  en  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/suexec.html.ja.euc-jp b/docs/manual/suexec.html.ja.euc-jp new file mode 100644 index 00000000..f49dae22 --- /dev/null +++ b/docs/manual/suexec.html.ja.euc-jp @@ -0,0 +1,609 @@ + + + +suEXEC ¥µ¥Ý¡¼¥È - Apache HTTP ¥µ¡¼¥Ð + + + + +
    +

    ¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

    +

    Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

    +
    +
    <-
    +

    suEXEC ¥µ¥Ý¡¼¥È

    +
    +

    Available Languages:  en  | + ja  | + ko 

    +
    + +

    suEXEC + µ¡Ç½¤Ë¤è¤ê¡¢Apache ¥æ¡¼¥¶¤Ï Web ¥µ¡¼¥Ð¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¥æ¡¼¥¶ ID ¤È¤Ï + °Û¤Ê¤ë¥æ¡¼¥¶ ID ¤Ç CGI ¥×¥í¥°¥é¥à¤ä SSI + ¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£CGI ¥×¥í¥°¥é¥à¤Þ¤¿¤Ï SSI + ¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ë¾ì¹ç¡¢Ä̾ï¤Ï web ¥µ¡¼¥Ð¤ÈƱ¤¸¥æ¡¼¥¶¤Ç¼Â¹Ô¤µ¤ì¤Þ¤¹¡£ +

    + +

    ŬÀڤ˻ÈÍѤ¹¤ë¤È¡¢¤³¤Îµ¡Ç½¤Ë¤è¤ê¥æ¡¼¥¶¤¬¸ÄÊ̤ΠCGI + ¤ä SSI ¥×¥í¥°¥é¥à¤ò³«È¯¤·¼Â¹Ô¤¹¤ë¤³¤È¤ÇÀ¸¤¸¤ë¥»¥­¥å¥ê¥Æ¥£¾å¤Î´í¸±¤ò¡¢ + ¤«¤Ê¤ê¸º¤é¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤·¤«¤·¡¢suEXEC ¤ÎÀßÄ꤬ÉÔŬÀÚ¤À¤È¡¢ + ¿¤¯¤ÎÌäÂ꤬À¸¤¸¡¢¤¢¤Ê¤¿¤Î¥³¥ó¥Ô¥å¡¼¥¿¤Ë¿·¤·¤¤¥»¥­¥å¥ê¥Æ¥£¥Û¡¼¥ë¤ò + ºî¤Ã¤Æ¤·¤Þ¤¦²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£¤¢¤Ê¤¿¤¬ setuid root + ¤µ¤ì¤¿¥×¥í¥°¥é¥à¤È¡¢¤½¤ì¤é¤«¤éÀ¸¤¸¤ë¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÌäÂê¤Î´ÉÍý¤Ë + ¾Ü¤·¤¯¤Ê¤¤¤è¤¦¤Ê¤é¡¢suEXEC ¤Î»ÈÍѤò¸¡Æ¤¤·¤Ê¤¤¤è¤¦¤Ë¶¯¤¯¿ä¾©¤·¤Þ¤¹¡£ +

    +
    + +
    top
    +
    +

    »Ï¤á¤ëÁ°¤Ë

    + +

    ¤³¤Îʸ½ñ¤ÎÀèƬ¤ËÈô¤ÖÁ°¤Ë¡¢Apache + ¥°¥ë¡¼¥×¤È¤³¤Îʸ½ñ¤Ç¤Î²¾Äê¤òÃΤäƤª¤¯¤Ù¤­¤Ç¤·¤ç¤¦¡£ +

    + +

    Âè 1 ¤Ë¡¢¤¢¤Ê¤¿¤¬ setuid ¤È + setgid Áàºî¤¬²Äǽ¤Ê UNIX + ͳÍè¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ò»È¤Ã¤Æ¤¤¤ë¤³¤È¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£ + ¤³¤ì¤Ï¡¢¤¹¤Ù¤Æ¤Î¥³¥Þ¥ó¥ÉÎã¤Ë¤¢¤Æ¤Ï¤Þ¤ê¤Þ¤¹¡£ + ¤½¤Î¾¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¤Ç¤Ï¡¢¤â¤· suEXEC + ¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤¿¤È¤·¤Æ¤âÀßÄê¤Ï°Û¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£

    + +

    Âè 2 ¤Ë¡¢¤¢¤Ê¤¿¤¬»ÈÍÑÃæ¤Î¥³¥ó¥Ô¥å¡¼¥¿¤Î + ¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤¹¤ë´ðËÜŪ¤Ê³µÇ°¤È¡¢¤½¤ì¤é¤Î´ÉÍý¤Ë¤Ä¤¤¤Æ¾Ü¤·¤¤¤³¤È¤ò + ÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ï¡¢setuid/setgid + Áàºî¡¢¤¢¤Ê¤¿¤Î¥·¥¹¥Æ¥à¾å¤Ç¤Î¤½¤ÎÁàºî¤Ë¤è¤ëÍÍ¡¹¤Ê¸ú²Ì¡¢ + ¥»¥­¥å¥ê¥Æ¥£¥ì¥Ù¥ë¤Ë¤Ä¤¤¤Æ¤¢¤Ê¤¿¤¬Íý²ò¤·¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È¤ò´Þ¤ß¤Þ¤¹¡£ +

    + +

    Âè 3 ¤Ë¡¢²þ¤¤µ¤ì¤Æ¤¤¤Ê¤¤ suEXEC + ¥³¡¼¥É¤Î»ÈÍѤòÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£suEXEC ¤Î¥³¡¼¥É¤Ï¡¢ + ¿¤¯¤Î¥Ù¡¼¥¿¥Æ¥¹¥¿¤À¤±¤Ç¤Ê¤¯¡¢³«È¯¼Ô¤Ë¤è¤Ã¤Æ¤âÃí°Õ¿¼¤¯Àººº¤µ¤ì + ¥Æ¥¹¥È¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤½¤ì¤é¤ÎÃí°Õ¤Ë¤è¤ê¡¢´Ê·é¤Ç¿®Íê¤Ç¤­¤ë°ÂÁ´¤Ê + ¥³¡¼¥É¤Î´ðÈפ¬Êݾڤµ¤ì¤Þ¤¹¡£¤³¤Î¥³¡¼¥É¤ò²þÊѤ¹¤ë¤³¤È¤Ç¡¢ + ͽ´ü¤µ¤ì¤Ê¤¤ÌäÂê¤ä¿·¤·¤¤¥»¥­¥å¥ê¥Æ¥£¾å¤Î´í¸±¤¬À¸¤¸¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¥»¥­¥å¥ê¥Æ¥£¥×¥í¥°¥é¥ß¥ó¥°¤Î¾ÜºÙ¤ËÄ̤¸¤Æ¤¤¤Æ¡¢ + º£¸å¤Î¸¡Æ¤¤Î¤¿¤á¤ËÀ®²Ì¤ò Apache + ¥°¥ë¡¼¥×¤È¶¦Í­¤·¤è¤¦¤È»×¤¦¤Î¤Ç¤Ê¤±¤ì¤Ð¡¢suEXEC + ¥³¡¼¥É¤ÏÊѤ¨¤Ê¤¤¤³¤È¤ò ¶¯¤¯¿ä¾©¤·¤Þ¤¹¡£

    + +

    Âè 4 ¤Ë¡¢¤³¤ì¤¬ºÇ¸å¤Ç¤¹¤¬¡¢suEXEC ¤ò Apache + ¤Î¥Ç¥Õ¥©¥ë¥È¥¤¥ó¥¹¥È¡¼¥ë¤Ë¤Ï´Þ¤á¤Ê¤¤¤³¤È¤¬ + Apache ¥°¥ë¡¼¥×¤Ç·èÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ï¡¢suEXEC + ¤ÎÀßÄê¤Ë¤Ï´ÉÍý¼Ô¤Î¾ÜºÙ¤Ë¤ï¤¿¤ë¿µ½Å¤ÊÃí°Õ¤¬É¬ÍפÀ¤«¤é¤Ç¤¹¡£ + suEXEC ¤ÎÍÍ¡¹¤ÊÀßÄê¤Ë¤Ä¤¤¤Æ¸¡Æ¤¤¬½ª¤ï¤ì¤Ð¡¢´ÉÍý¼Ô¤Ï suEXEC + ¤òÄ̾ï¤Î¥¤¥ó¥¹¥È¡¼¥ëÊýË¡¤Ç¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤³¤ì¤é¤ÎÀßÄêÃͤϡ¢suEXEC + µ¡Ç½¤Î»ÈÍÑÃæ¤Ë¥·¥¹¥Æ¥à¥»¥­¥å¥ê¥Æ¥£¤òŬÀÚ¤ËÊݤĤ¿¤á¤Ë¡¢ + ´ÉÍý¼Ô¤Ë¤è¤Ã¤Æ¿µ½Å¤Ë·èÄꤵ¤ì»ØÄꤵ¤ì¤ë¤³¤È¤¬É¬ÍפǤ¹¡£ + ¤³¤Î¾ÜºÙ¤Ê¼ê½ç¤Ë¤è¤ê¡¢Apache ¥°¥ë¡¼¥×¤Ï¡¢suEXEC + ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ë¤Ä¤¤¤Æ¡¢Ãí°Õ¿¼¤¯½½Ê¬¤Ë¸¡Æ¤¤·¤Æ¤½¤ì¤ò»ÈÍѤ¹¤ë¤³¤È¤ò + ·èÄꤷ¤¿¾ì¹ç¤Ë¸Â¤Ã¤Æ¤¤¤¿¤À¤­¤¿¤¤¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£ +

    + +

    ¤½¤ì¤Ç¤â¿Ê¤ß¤Þ¤¹¤«? ¤è¤í¤·¤¤¡£¤Ç¤Ï¡¢Àè¤Ø¿Ê¤ß¤Þ¤·¤ç¤¦!

    +
    top
    +
    +

    suEXEC ¥»¥­¥å¥ê¥Æ¥£¥â¥Ç¥ë

    + +

    suEXEC ¤ÎÀßÄê¤È¥¤¥ó¥¹¥È¡¼¥ë¤ò»Ï¤á¤ëÁ°¤Ë¡¢ + ¤Þ¤º¼ÂÁõ¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¥»¥­¥å¥ê¥Æ¥£¥â¥Ç¥ë¤Ë¤Ä¤¤¤ÆÏÀ¤¸¤Æ¤ª¤­¤Þ¤¹¡£ + ¤½¤ì¤Ë¤Ï¡¢suEXEC ¤ÎÆâÉô¤Ç¹Ô¤Ê¤ï¤ì¤Æ¤¤¤ë¤³¤È¡¢ + ¥·¥¹¥Æ¥à¤Î¥»¥­¥å¥ê¥Æ¥£¤òÊݾڤ¹¤ë¤¿¤á¤Ë·Ù¹ð¤µ¤ì¤ë¤³¤È¤ò + ¤è¤¯Íý²ò¤·¤Æ¤ª¤¤¤¿Êý¤¬¤è¤¤¤Ç¤·¤ç¤¦¡£

    + +

    suEXEC ¤Ï¡¢Apache web + ¥µ¡¼¥Ð¤«¤é¸Æ¤Ó½Ð¤µ¤ì¤ë setuid ¤µ¤ì¤¿ "wrapper" + ¥×¥í¥°¥é¥à¤¬´ðËܤȤʤäƤ¤¤Þ¤¹¡£À߷פ·¤¿ CGI¡¢¤Þ¤¿¤Ï SSI + ¥×¥í¥°¥é¥à¤Ø¤Î HTTP ¥ê¥¯¥¨¥¹¥È¤¬¤¢¤ë¤È¡¢¤³¤Î wrapper + ¤¬¸Æ¤Ó½Ð¤µ¤ì¤Þ¤¹¡£¤³¤Î¤è¤¦¤Ê¥ê¥¯¥¨¥¹¥È¤¬¤¢¤ë¤È¡¢Apache + ¤Ï¤½¤Î¥×¥í¥°¥é¥à¤¬¼Â¹Ô¤µ¤ì¤ëºÝ¤Î¥×¥í¥°¥é¥à̾¤È¥æ¡¼¥¶ ID ¤È¥°¥ë¡¼¥× + ID ¤ò»ØÄꤷ¤Æ suEXEC wrapper ¤ò¼Â¹Ô¤·¤Þ¤¹¡£ +

    + +

    ¤½¤ì¤«¤é¡¢wrapper ¤ÏÀ®¸ù¤Þ¤¿¤Ï¼ºÇÔ¤ò·èÄꤹ¤ë¤¿¤á + °Ê²¼¤Î½èÍý¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£¤³¤ì¤é¤Î¾õÂ֤Τ¦¤Á°ì¤Ä¤Ç¤â¼ºÇÔ¤·¤¿¾ì¹ç¡¢ + ¥×¥í¥°¥é¥à¤Ï¼ºÇÔ¤ò¥í¥°¤Ëµ­Ï¿¤·¤Æ¥¨¥é¡¼¤Ç½ªÎ»¤·¤Þ¤¹¡£ + ¤½¤¦¤Ç¤Ê¤±¤ì¤Ð¡¢¸å¤Î½èÍý¤¬Â³¤±¤é¤ì¤Þ¤¹¡£

    + +
      +
    1. + wrapper + ¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¥æ¡¼¥¶¤Ï¤³¤Î¥·¥¹¥Æ¥à¤ÎÀµÅö¤Ê¥æ¡¼¥¶¤«? + +

      + ¤³¤ì¤Ï¡¢wrapper ¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¥æ¡¼¥¶¤¬ + ËÜÅö¤Ë¥·¥¹¥Æ¥à¤ÎÍøÍѼԤǤ¢¤ë¤³¤È¤òÊݾڤ¹¤ë¤¿¤á¤Ç¤¹¡£ +

      +
      2. + + +
    2. + wrapper ¤¬Å¬Àڤʿô¤Î°ú¿ô¤Ç¸Æ¤Ó½Ð¤µ¤ì¤¿¤«? + + +

      + wrapper ¤ÏŬÀڤʿô¤Î°ú¿ô¤¬Í¿¤¨¤é¤ì¤¿¾ì¹ç¤Ë¤Î¤ß¼Â¹Ô¤µ¤ì¤Þ¤¹¡£ + ŬÀڤʰú¿ô¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï Apache Web ¥µ¡¼¥Ð¤Ë²ò¼á¤µ¤ì¤Þ¤¹¡£ + ŬÀڤʿô¤Î°ú¿ô¤ò¼õ¤±¼è¤é¤Ê¤±¤ì¤Ð¡¢¹¶·â¤ò¤µ¤ì¤¿¤« + ¤¢¤Ê¤¿¤Î Apache ¥Ð¥¤¥Ê¥ê¤Î suEXEC ¤ÎÉôʬ¤¬ + ¤É¤³¤«¤ª¤«¤·¤¤²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ +

      +
      3. + +
    3. + ¤³¤ÎÀµÅö¤Ê¥æ¡¼¥¶¤Ï wrapper + ¤Î¼Â¹Ô¤òµö²Ä¤µ¤ì¤Æ¤¤¤ë¤«? + +

      + ¤³¤Î¥æ¡¼¥¶¤Ï wrapper ¼Â¹Ô¤òµö²Ä¤µ¤ì¤¿¥æ¡¼¥¶¤Ç¤¹¤«? + ¤¿¤À°ì¿Í¤Î¥æ¡¼¥¶ (Apache ¥æ¡¼¥¶) ¤À¤±¤¬¡¢ + ¤³¤Î¥×¥í¥°¥é¥à¤Î¼Â¹Ô¤òµö²Ä¤µ¤ì¤Þ¤¹¡£ +

      +
      4. + +
    4. + ÂоݤΠCGI, SSI ¥×¥í¥°¥é¥à¤¬°ÂÁ´¤Ç¤Ê¤¤³¬Áؤλ²¾È¤ò¤·¤Æ¤¤¤ë¤«? + + +

      + ÂоݤΠCGI, SSI ¥×¥í¥°¥é¥à¤¬ '/' ¤«¤é»Ï¤Þ¤ë¡¢¤Þ¤¿¤Ï + '..' ¤Ë¤è¤ë»²¾È¤ò¹Ô¤Ê¤Ã¤Æ¤¤¤Þ¤¹¤«? ¤³¤ì¤é¤Ïµö²Ä¤µ¤ì¤Þ¤»¤ó¡£ + ÂÐ¾Ý¤Î¥×¥í¥°¥é¥à¤Ï suEXEC ¤Î¥É¥­¥å¥á¥ó¥È¥ë¡¼¥È + (²¼µ­¤Î --with-suexec-docroot=DIR ¤ò»²¾È) + Æâ¤Ë¸ºß¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ +

      +
      5. + +
    5. + ÂоݤȤʤë¥æ¡¼¥¶Ì¾¤ÏÀµÅö¤Ê¤â¤Î¤«? + +

      + ÂоݤȤʤë¥æ¡¼¥¶Ì¾¤Ï¸ºß¤·¤Æ¤¤¤Þ¤¹¤«? +

      +
      6. + +
    6. + ÂоݤȤʤ륰¥ë¡¼¥×̾¤ÏÀµÅö¤Ê¤â¤Î¤«? + +

      + ÂоݤȤʤ륰¥ë¡¼¥×̾¤Ï¸ºß¤·¤Æ¤¤¤Þ¤¹¤«? +

      +
      7. + +
    7. + ÌÜŪ¤Î¥æ¡¼¥¶¤Ï¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¤Ç¤Ï¤Ê¤¤¤«? + + +

      + º£¤Î¤È¤³¤í¡¢suEXEC ¤Ï root ¤Ë¤è¤ë CGI/SSI + ¥×¥í¥°¥é¥à¤Î¼Â¹Ô¤òµö²Ä¤·¤Æ¤¤¤Þ¤»¤ó¡£ +

      +
      8. + +
    8. + ÂоݤȤʤë¥æ¡¼¥¶ ID ¤Ï¡¢ºÇ¾®¤Î ID + ÈÖ¹æ¤è¤ê¤âÂ礭¤¤¤«? + +

      + ºÇ¾®¥æ¡¼¥¶ ID ÈÖ¹æ¤ÏÀßÄê»þ¤Ë»ØÄꤵ¤ì¤Þ¤¹¡£¤³¤ì¤Ï¡¢ + CGI/SSI ¥×¥í¥°¥é¥à¼Â¹Ô¤òµö²Ä¤µ¤ì¤ë¥æ¡¼¥¶ ID + ¤Î¤È¤ê¤¦¤ëºÇ¾®ÃͤǤ¹¡£¤³¤ì¤Ï + "system" ÍѤΥ¢¥«¥¦¥ó¥È¤òÊĤá½Ð¤¹¤Î¤ËÍ­¸ú¤Ç¤¹¡£ +

      +
      9. + +
    9. + ÂоݤȤʤ륰¥ë¡¼¥×¤Ï¥¹¡¼¥Ñ¡¼¥æ¡¼¥¶¤Î¥°¥ë¡¼¥×¤Ç¤Ï + ¤Ê¤¤¤«? + +

      + º£¤Î¤È¤³¤í¡¢suEXEC ¤Ï 'root' ¥°¥ë¡¼¥×¤Ë¤è¤ë CGI/SSI + ¥×¥í¥°¥é¥à¤Î¼Â¹Ô¤òµö²Ä¤·¤Æ¤¤¤Þ¤»¤ó¡£ +

      +
      10. + +
    10. + ÂоݤȤʤ륰¥ë¡¼¥× ID ¤ÏºÇ¾®¤Î ID + ÈÖ¹æ¤è¤ê¤âÂ礭¤¤¤«? + +

      + ºÇ¾®¥°¥ë¡¼¥× ID ÈÖ¹æ¤ÏÀßÄê»þ¤Ë»ØÄꤵ¤ì¤Þ¤¹¡£¤³¤ì¤Ï¡¢ + CGI/SSI ¥×¥í¥°¥é¥à¼Â¹Ô¤òµö²Ä¤µ¤ì¤ë¥°¥ë¡¼¥× + ID ¤Î¤È¤ê¤¦¤ëºÇ¾®ÃͤǤ¹¡£ + ¤³¤ì¤Ï "system" ÍѤΥ°¥ë¡¼¥×¤òÊĤá½Ð¤¹¤Î¤ËÍ­¸ú¤Ç¤¹¡£ +

      +
      11. + +
    11. + wrapper ¤¬Àµ¾ï¤ËÂоݤȤʤë¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤Ë¤Ê¤ì¤ë¤«? + + +

      + ¤³¤³¤Ç¡¢setuid ¤È setgid + ¤Îµ¯Æ°¤Ë¤è¤ê¥×¥í¥°¥é¥à¤ÏÂоݤȤʤë¥æ¡¼¥¶¤È¥°¥ë¡¼¥×¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¥°¥ë¡¼¥×¥¢¥¯¥»¥¹¥ê¥¹¥È¤Ï¡¢ + ¥æ¡¼¥¶¤¬Â°¤·¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¥°¥ë¡¼¥×¤Ç½é´ü²½¤µ¤ì¤Þ¤¹¡£ +

      +
      12. + +
    12. + CGI/SSI ¥×¥í¥°¥é¥à¤¬ÃÖ¤«¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Ë°ÜÆ° + (change directory) ¤Ç¤­¤ë¤«? + +

      + ¥Ç¥£¥ì¥¯¥È¥ê¤¬Â¸ºß¤·¤Ê¤¤¤Ê¤é¡¢¤½¤Î¥Õ¥¡¥¤¥ë¤â¸ºß¤·¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£ + ¥Ç¥£¥ì¥¯¥È¥ê¤Ë°ÜÆ°¤Ç¤­¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢¤ª¤½¤é¤¯Â¸ºß¤â¤·¤Ê¤¤¤Ç¤·¤ç¤¦¡£ +

      +
      13. + +
    13. + ¥Ç¥£¥ì¥¯¥È¥ê¤¬ Apache ¤Î¥É¥­¥å¥á¥ó¥È¥Ä¥ê¡¼Æâ¤Ë¤¢¤ë¤«? + + +

      + ¥ê¥¯¥¨¥¹¥È¤¬¥µ¡¼¥ÐÆâ¤Î¤â¤Î¤Ç¤¢¤ì¤Ð¡¢ + Í׵ᤵ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤¬ suEXEC ¤Î¥É¥­¥å¥á¥ó¥È¥ë¡¼¥ÈÇÛ²¼¤Ë¤¢¤ê¤Þ¤¹¤«? + ¥ê¥¯¥¨¥¹¥È¤¬ UserDir ¤Î¤â¤Î¤Ç¤¢¤ì¤Ð¡¢Í׵ᤵ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤¬ suEXEC + ¤Î¥æ¡¼¥¶¤Î¥É¥­¥å¥á¥ó¥È¥ë¡¼¥ÈÇÛ²¼¤Ë¤¢¤ê¤Þ¤¹¤«? + (suEXEC ÀßÄꥪ¥×¥·¥ç¥ó »²¾È) +

      +
      14. + +
    14. + ¥Ç¥£¥ì¥¯¥È¥ê¤ò¾¤Î¥æ¡¼¥¶¤¬½ñ¤­¹þ¤á¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ + ¤¤¤Ê¤¤¤«? + +

      + ¥Ç¥£¥ì¥¯¥È¥ê¤ò¾¥æ¡¼¥¶¤Ë³«Êü¤·¤Ê¤¤¤è¤¦¤Ë¤·¤Þ¤¹¡£ + ½êÍ­¥æ¡¼¥¶¤À¤±¤¬¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ÎÆâÍƤò²þÊѤǤ­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ +

      +
      15. + + +
    15. + ÂоݤȤʤë CGI/SSI ¥×¥í¥°¥é¥à¤Ï¸ºß¤¹¤ë¤«? + +

      + ¸ºß¤·¤Ê¤±¤ì¤Ð¼Â¹Ô¤Ç¤­¤Þ¤»¤ó¡£ +

      +
      16. + +
    16. + ÂоݤȤʤë CGI/SSI ¥×¥í¥°¥é¥à¥Õ¥¡¥¤¥ë¤¬Â¾¥¢¥«¥¦¥ó¥È¤«¤é + ½ñ¤­¹þ¤á¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤¤¤«? + +

      + ½êÍ­¼Ô°Ê³°¤Ë¤Ï CGI/SSI ¥×¥í¥°¥é¥à¤òÊѹ¹¤¹¤ë¸¢¸Â¤ÏÍ¿¤¨¤é¤ì¤Þ¤»¤ó¡£ +

      +
      17. + + +
    17. + ÂоݤȤʤë CGI/SSI ¥×¥í¥°¥é¥à¤¬ setuid ¤Þ¤¿¤Ï setgid + ¤µ¤ì¤Æ¤¤¤Ê¤¤¤«? + +

      + UID/GID ¤òºÆÅÙÊѹ¹¤·¤Æ¤Î¥×¥í¥°¥é¥à¼Â¹Ô¤Ï¤·¤Þ¤»¤ó +

      +
      18. + + +
    18. + ÂоݤȤʤë¥æ¡¼¥¶/¥°¥ë¡¼¥×¤¬¥×¥í¥°¥é¥à¤Î + ¥æ¡¼¥¶/¥°¥ë¡¼¥×¤ÈƱ¤¸¤«? + +

      + ¥æ¡¼¥¶¤¬¤½¤Î¥Õ¥¡¥¤¥ë¤Î½êÍ­¼Ô¤Ç¤¹¤«? +

      +
      19. + +
    19. + °ÂÁ´¤ÊÆ°ºî¤òÊݾڤ¹¤ë¤¿¤á¤Î´Ä¶­ÊÑ¿ô¥¯¥ê¥¢¤¬²Äǽ¤«? + + +

      + suEXEC ¤Ï¡¢°ÂÁ´¤Ê´Ä¶­ÊÑ¿ô¤Î¥ê¥¹¥È + (¤³¤ì¤é¤ÏÀßÄê»þ¤ËºîÀ®¤µ¤ì¤Þ¤¹) Æâ¤ÎÊÑ¿ô¤È¤·¤ÆÅϤµ¤ì¤ë°ÂÁ´¤Ê + PATH ÊÑ¿ô (ÀßÄê»þ¤Ë»ØÄꤵ¤ì¤Þ¤¹) ¤òÀßÄꤹ¤ë¤³¤È¤Ç¡¢ + ¥×¥í¥»¥¹¤Î´Ä¶­ÊÑ¿ô¤ò¥¯¥ê¥¢¤·¤Þ¤¹¡£ +

      +
      20. + + +
    20. + ÂоݤȤʤë CGI/SSI ¥×¥í¥°¥é¥à¤ò exec ¤·¤Æ¼Â¹Ô¤Ç¤­¤ë¤«? + + +

      + ¤³¤³¤Ç suEXEC ¤¬½ªÎ»¤·¡¢ÂоݤȤʤë¥×¥í¥°¥é¥à¤¬³«»Ï¤µ¤ì¤Þ¤¹¡£ +

      +
      21. +
    + +

    ¤³¤³¤Þ¤Ç¤¬ suEXEC ¤Î wrapper + ¤Ë¤ª¤±¤ë¥»¥­¥å¥ê¥Æ¥£¥â¥Ç¥ë¤Îɸ½àŪ¤ÊÆ°ºî¤Ç¤¹¡£¤â¤¦¾¯¤·¸·½Å¤Ë + CGI/SSI À߷פˤĤ¤¤Æ¤Î¿·¤·¤¤À©¸Â¤äµ¬Äê¤ò¼è¤êÆþ¤ì¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¤¬¡¢ + suEXEC ¤Ï¥»¥­¥å¥ê¥Æ¥£¤ËÃí°Õ¤·¤Æ¿µ½Å¤Ë¾¯¤·¤º¤Ä³«È¯¤µ¤ì¤Æ¤­¤Þ¤·¤¿¡£ +

    + +

    ¤³¤Î¥»¥­¥å¥ê¥Æ¥£¥â¥Ç¥ë¤òÍѤ¤¤Æ + ¥µ¡¼¥ÐÀßÄê»þ¤Ë¤É¤Î¤è¤¦¤Ëµö¤¹¤³¤È¤òÀ©¸Â¤¹¤ë¤«¡¢¤Þ¤¿¡¢suEXEC + ¤òŬÀÚ¤ËÀßÄꤹ¤ë¤È¤É¤Î¤è¤¦¤Ê¥»¥­¥å¥ê¥Æ¥£¾å¤Î´í¸±¤òÈò¤±¤é¤ì¤ë¤«¤Ë + ´Ø¤¹¤ë¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ë¤Ä¤¤¤Æ¤Ï¡¢"¤È¤«¤²¤ËÃí°Õ" + (Beware the Jabberwock) ¤Î¾Ï¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ +

    +
    top
    +
    +

    suEXEC + ¤ÎÀßÄê¤È¥¤¥ó¥¹¥È¡¼¥ë

    + +

    ¤³¤³¤«¤é³Ú¤·¤¯¤Ê¤ê¤Þ¤¹¡£

    + +

    suEXEC + ÀßÄꥪ¥×¥·¥ç¥ó
    +

    + +
    +
    --enable-suexec
    + +
    ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤º¡¢ + Í­¸ú¤Ë¤Ï¤Ê¤é¤Ê¤¤ suEXEC µ¡Ç½¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£ + suEXEC ¤ò»È¤¦¤è¤¦¤Ë APACI ¤ËÍ׵᤹¤ë¤Ë¤Ï¡¢--enable-suexec + ¥ª¥×¥·¥ç¥ó¤Ë¤¢¤ï¤»¤Æ¾¯¤Ê¤¯¤È¤â°ì¤Ä¤Ï --with-suexec-xxxxx + ¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
    + +
    --with-suexec-bin=PATH
    + +
    ¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÍýͳ¤Ë¤è¤ê¡¢suexec ¥Ð¥¤¥Ê¥ê¤Î¥Ñ¥¹¤Ï¥µ¡¼¥Ð¤Ë + ¥Ï¡¼¥É¥³¡¼¥É¤µ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤Î¥Ñ¥¹¤ò + ÊѤ¨¤¿¤¤¤È¤­¤Ï¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£Î㤨¤Ð¡¢ + --with-suexec-bin=/usr/sbin/suexec ¤Î¤è¤¦¤Ë¡£
    + +
    --with-suexec-caller=UID
    + +
    Apache ¤òÄ̾ïÆ°ºî¤µ¤»¤ë¥æ¡¼¥¶Ì¾¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤³¤Î¥æ¡¼¥¶¤À¤±¤¬ suexec ¤Î¼Â¹Ô¤òµö²Ä¤µ¤ì¤¿¥æ¡¼¥¶¤Ë¤Ê¤ê¤Þ¤¹¡£
    + +
    --with-suexec-userdir=DIR
    + +
    suEXEC ¤¬¥¢¥¯¥»¥¹¤òµö¤µ¤ì¤ë¥æ¡¼¥¶¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥êÇÛ²¼¤Î + ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê°Ê²¼¤ÎÁ´¼Â¹Ô¥Õ¥¡¥¤¥ë¤Ï¡¢"°ÂÁ´¤Ê"¥×¥í¥°¥é¥à¤Ë¤Ê¤ë¤è¤¦¡¢ + suEXEC ¤¬¤½¤Î¥æ¡¼¥¶¤È¤·¤Æ¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ + "ñ½ã¤Ê" UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç + (¤¹¤Ê¤ï¤Á "*" ¤ò´Þ¤Þ¤Ê¤¤¤â¤Î)¡¢¤³¤ì¤ÈƱ¤¸ÃͤòÀßÄꤹ¤Ù¤­¤Ç¤¹¡£ + Userdir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬¤½¤Î¥æ¡¼¥¶¤Î¥Ñ¥¹¥ï¡¼¥É¥Õ¥¡¥¤¥ëÆâ¤Î + ¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤ÈƱ¤¸¾ì½ê¤ò»Ø¤·¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢ + suEXEC ¤ÏŬÀÚ¤ËÆ°ºî¤·¤Þ¤»¤ó¡£¥Ç¥Õ¥©¥ë¥È¤Ï "public_html" ¤Ç¤¹¡£ +
    + ³Æ UserDir ¤¬°Û¤Ê¤Ã¤¿²¾ÁÛ¥Û¥¹¥È¤òÀßÄꤷ¤Æ¤¤¤ë¾ì¹ç¡¢ + ¤½¤ì¤é¤òÁ´¤Æ°ì¤Ä¤Î¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤Ë´Þ¤á¤Æ¡¢ + ¤½¤Î¿Æ¥Ç¥£¥ì¥¯¥È¥ê¤Î̾Á°¤ò¤³¤³¤Ç»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¤è¤¦¤Ë»ØÄꤵ¤ì¤Ê¤±¤ì¤Ð "~userdir" cgi + ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤¬Æ°ºî¤·¤Þ¤»¤ó¡£
    + +
    --with-suexec-docroot=DIR
    + +
    Apache ¤Î¥É¥­¥å¥á¥ó¥È¥ë¡¼¥È¤òÀßÄꤷ¤Þ¤¹¡£¤³¤ì¤¬ suEXEC + ¤ÎÆ°ºî¤Ç»ÈÍѤ¹¤ëÍ£°ì¤Î¥Ç¥£¥ì¥¯¥È¥ê³¬Áؤˤʤê¤Þ¤¹ (UserDir + ¤Î»ØÄê¤ÏÊÌ)¡£¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï --datedir ¤Ë "/htdocs" + ¤È¤¤¤¦¥µ¥Õ¥£¥Ã¥¯¥¹¤ò¤Ä¤±¤¿¤â¤Î¤Ç¤¹¡£ + "--datadir=/home/apache" ¤È¤·¤ÆÀßÄꤹ¤ë¤È¡¢ + suEXEC wrapper ¤Ë¤È¤Ã¤Æ "/home/apache/htdocs" + ¤¬¥É¥­¥å¥á¥ó¥È¥ë¡¼¥È¤È¤·¤Æ»È¤ï¤ì¤Þ¤¹¡£
    + +
    --with-suexec-uidmin=UID
    + +
    suEXEC ¤ÎÂоݥ桼¥¶¤È¤·¤Æµö¤µ¤ì¤ë UID ¤ÎºÇ¾®Ãͤò»ØÄꤷ¤Þ¤¹¡£ + ÂçÄñ¤Î¥·¥¹¥Æ¥à¤Ç¤Ï 500 ¤« 100 ¤¬°ìÈÌŪ¤Ç¤¹¡£ + ¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï 100 ¤Ç¤¹¡£
    + +
    --with-suexec-gidmin=GID
    + +
    suEXEC ¤ÎÂоݥ°¥ë¡¼¥×¤È¤·¤Æµö¤µ¤ì¤ë GID + ¤ÎºÇ¾®Ãͤò»ØÄꤷ¤Þ¤¹¡£ÂçÄñ¤Î¥·¥¹¥Æ¥à¤Ç¤Ï 100 ¤¬°ìÈÌŪ¤Ê¤Î¤Ç¡¢ + ¥Ç¥Õ¥©¥ë¥ÈÃͤȤ·¤Æ¤â 100 ¤¬»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
    + +
    --with-suexec-logfile=FILE
    + +
    suEXEC ¤Î½èÍý¤È¥¨¥é¡¼¤¬µ­Ï¿¤µ¤ì¤ë¥Õ¥¡¥¤¥ë̾¤ò»ØÄꤷ¤Þ¤¹¡£ + (´Æºº¤ä¥Ç¥Ð¥Ã¥°ÌÜŪ¤ËÍ­ÍÑ) + ¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¥í¥°¥Õ¥¡¥¤¥ë¤Ï "suexec_log" ¤È¤¤¤¦Ì¾Á°¤Ç¡¢ + ɸ½à¤Î¥í¥°¥Õ¥¡¥¤¥ë¥Ç¥£¥ì¥¯¥È¥ê (--logfiledir) ¤ËÃÖ¤«¤ì¤Þ¤¹¡£ +
    + +
    --with-suexec-safepath=PATH
    + +
    CGI ¼Â¹Ô¥Õ¥¡¥¤¥ë¤ËÅϤµ¤ì¤ë°ÂÁ´¤Ê PATH ´Ä¶­ÊÑ¿ô¤Ç¤¹¡£ + ¥Ç¥Õ¥©¥ë¥ÈÃÍ¤Ï "/usr/local/bin:/usr/bin:/bin" ¤Ç¤¹¡£ +
    +
    + +

    suEXEC wrapper + ¤Î¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë
    + --enable-suexec ¥ª¥×¥·¥ç¥ó¤Ç suEXEC µ¡Ç½¤òÍ­¸ú¤Ë¤¹¤ë¤È¡¢ + "make" ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤¿»þ¤Ë suexec ¤Î¥Ð¥¤¥Ê¥ê (Apache ¼«ÂΤâ) + ¤¬¼«Æ°Åª¤ËºîÀ®¤µ¤ì¤Þ¤¹¡£ +
    + ¤¹¤Ù¤Æ¤Î¹½À®Í×ÁǤ¬ºîÀ®¤µ¤ì¤ë¤È¡¢¤½¤ì¤é¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ë¤Ï + make install ¥³¥Þ¥ó¥É¤¬¼Â¹Ô¤Ç¤­¤Þ¤¹¡£¥Ð¥¤¥Ê¥ê¥¤¥á¡¼¥¸¤Î suexec + ¤Ï --sbindir ¥ª¥×¥·¥ç¥ó¤Ç»ØÄꤵ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£ + ¥Ç¥Õ¥©¥ë¥È¤Î¾ì½ê¤Ï "/usr/local/apache/sbin/suexec" ¤Ç¤¹¡£
    + ¥¤¥ó¥¹¥È¡¼¥ë»þ¤Ë¤Ï root + ¸¢¸Â¤¬É¬ÍפʤΤÇÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£wrapper ¤¬¥æ¡¼¥¶ ID + ¤òÀßÄꤹ¤ë¤¿¤á¤Ë¡¢½êÍ­¼Ô root + ¤Ç¤Î¥»¥Ã¥È¥æ¡¼¥¶ ID + ¥Ó¥Ã¥È¤ò¤½¤Î¥Õ¥¡¥¤¥ë¤Î¥â¡¼¥É¤ËÀßÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ +

    + +

    °ÂÁ´¤Ê¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤òÀßÄꤹ¤ë
    + suEXEC ¥é¥Ã¥Ñ¡¼¤Ï¡¢--with-suexec-caller configure + ¥ª¥×¥·¥ç¥ó¤Ç»ØÄꤷ¤¿Àµ¤·¤¤¥æ¡¼¥¶¤Çµ¯Æ°¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Þ¤¹¤¬¡¢ + ¥·¥¹¥Æ¥à¾å¤Ç¤³¤Î¥Á¥§¥Ã¥¯¤¬¹Ô¤Ê¤ï¤ì¤ëÁ°¤Ë¡¢ + suEXEC ¤¬¸Æ¤Ö¥·¥¹¥Æ¥à¤ä¥é¥¤¥Ö¥é¥ê¤¬Àȼå¤Ç¤¢¤ë²ÄǽÀ­¤Ï»Ä¤ê¤Þ¤¹¡£Âй³ºö¤È¤·¤Æ¡¢ + °ìÈ̤ËÎɤ¤½¬´·¤È¤â¤µ¤ì¤Æ¤¤¤Þ¤¹¤¬¡¢ + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥Ñ¡¼¥ß¥Ã¥·¥ç¥ó¤ò»È¤Ã¤Æ + Apache ¤Î¼Â¹Ô»þ¤Î¥°¥ë¡¼¥×¤Î¤ß¤¬ suEXEC ¤ò¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ë + ¤¹¤ë¤Î¤¬Îɤ¤¤Ç¤·¤ç¤¦¡£

    + +

    ¤¿¤È¤¨¤Ð¡¢¼¡¤Î¤è¤¦¤Ë¥µ¡¼¥Ð¤¬ÀßÄꤵ¤ì¤Æ¤¤¤¿¤È¤·¤Þ¤¹¡£

    + +

    + User www
    + Group webgroup
    +

    + +

    suexec ¤¬ "/usr/local/apache2/sbin/suexec" + ¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤¿¾ì¹ç¡¢¼¡¤Î¤è¤¦¤ËÀßÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£

    + +

    + chgrp webgroup /usr/local/apache2/bin/suexec
    + chmod 4750 /usr/local/apache2/bin/suexec
    +

    + +

    ¤³¤ì¤Ç Apache ¤¬¼Â¹Ô¤µ¤ì¤ë¥°¥ë¡¼¥×¤Î¤ß¤¬ + suEXEC ¥é¥Ã¥Ñ¡¼¤ò¼Â¹Ô¤Ç¤­¤ë¤È¤¤¤¦¤³¤È¤ò + ³Î¾Ú¤·¤Þ¤¹¡£

    +
    top
    +
    +

    suEXEC + ¤ÎÍ­¸ú²½¤È̵¸ú²½

    + +

    µ¯Æ°»þ¤Ë¡¢Apache ¤Ï --sbindir + ¥ª¥×¥·¥ç¥ó¤ÇÀßÄꤵ¤ì¤¿¥Ç¥£¥ì¥¯¥È¥ê¤Ç + suexec ¤òõ¤·¤Þ¤¹ + (¥Ç¥Õ¥©¥ë¥È¤Ï "/usr/local/apache/sbin/suexec") ¡£ + ŬÀÚ¤ËÀßÄꤵ¤ì¤¿ suEXEC ¤¬¤ß¤Ä¤«¤ë¤È¡¢ + ¥¨¥é¡¼¥í¥°¤Ë°Ê²¼¤Î¥á¥Ã¥»¡¼¥¸¤¬½ÐÎϤµ¤ì¤Þ¤¹¡£

    + +

    + [notice] suEXEC mechanism enabled (wrapper: /path/to/suexec) +

    + +

    ¥µ¡¼¥Ðµ¯Æ°»þ¤Ë¤³¤Î¥á¥Ã¥»¡¼¥¸¤¬½Ð¤Ê¤¤¾ì¹ç¡¢ + ÂçÄñ¤Ï¥µ¡¼¥Ð¤¬ÁÛÄꤷ¤¿¾ì½ê¤Ç wrapper ¥×¥í¥°¥é¥à¤¬¸«¤Ä¤«¤é¤Ê¤«¤Ã¤¿¤«¡¢ + setuid root ¤È¤·¤Æ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤Ê¤¤¤«¤Ç¤¹¡£

    + +

    suEXEC ¤Î»ÅÁȤߤò»ÈÍѤ¹¤ë¤Î¤¬½é¤á¤Æ¤Ç¡¢Apache ¤¬´û¤ËÆ°ºîÃæ¤Ç¤¢¤ì¤Ð¡¢ + Apache ¤ò kill ¤·¤Æ¡¢ºÆµ¯Æ°¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£HUP ¥·¥°¥Ê¥ë¤ä + USR1 ¥·¥°¥Ê¥ë¤Ë¤è¤ëñ½ã¤ÊºÆµ¯Æ°¤Ç¤ÏÉÔ½½Ê¬¤Ç¤¹¡£

    +

    suEXEC ¤ò̵¸ú¤Ë¤¹¤ë¾ì¹ç¤Ï¡¢suexec ¥Õ¥¡¥¤¥ë¤òºï½ü¤·¤Æ¤«¤é + Apache ¤ò kill ¤·¤ÆºÆµ¯Æ°¤·¤Þ¤¹¡£ +

    +
    top
    +
    +

    suEXEC ¤Î»ÈÍÑ

    + +

    CGI ¥×¥í¥°¥é¥à¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤¬ suEXEC ¥é¥Ã¥Ñ¡¼¤ò¸Æ¤Ö¤Î¤Ï¡¢ + SuexecUserGroup ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ´Þ¤à¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤«¡¢mod_userdir ¤Ë¤è¤ê + ½èÍý¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Î¾ì¹ç¤Ë¸Â¤ê¤Þ¤¹¡£

    + +

    ²¾ÁÛ¥Û¥¹¥È:
    + suEXEC wrapper ¤Î»È¤¤Êý¤È¤·¤Æ¡¢ + VirtualHost ÀßÄê¤Ç¤Î + SuexecUserGroup + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÄ̤·¤¿¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò¥á¥¤¥ó¥µ¡¼¥Ð¤Î¥æ¡¼¥¶ ID + ¤È°Û¤Ê¤ë¤â¤Î¤Ë¤¹¤ë¤È¡¢CGI ¥ê¥½¡¼¥¹¤Ø¤Î¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤Ï¡¢¤½¤Î + <VirtualHost> ¤Ç»ØÄꤵ¤ì¤¿ User ¤È + Group ¤È¤·¤Æ¼Â¹Ô¤µ¤ì¤Þ¤¹¡£<VirtualHost> + ¤Ç¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢ + ¥á¥¤¥ó¥µ¡¼¥Ð¤Î¥æ¡¼¥¶ ID ¤¬ÁÛÄꤵ¤ì¤Þ¤¹¡£

    + +

    ¥æ¡¼¥¶¥Ç¥£¥ì¥¯¥È¥ê:
    + mod_userdir ¤Ë¤è¤ê½èÍý¤µ¤ì¤¿¥ê¥¯¥¨¥¹¥È¤Ï + ¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥æ¡¼¥¶¥Ç¥£¥ì¥¯¥È¥ê¤Î¥æ¡¼¥¶ ID ¤Ç CGI ¥×¥í¥°¥é¥à¤ò + ¼Â¹Ô¤¹¤ë¤¿¤á¤Ë suEXEC ¥é¥Ã¥Ñ¡¼¤ò¸Æ¤Ó¤Þ¤¹¡£ + ¤³¤Îµ¡Ç½¤òÆ°ºî¤µ¤»¤ë¤¿¤á¤ËɬÍפʤ³¤È¤Ï¡¢CGI + ¤ò¤½¤Î¥æ¡¼¥¶¤Ç¼Â¹Ô¤Ç¤­¤ë¤³¤È¡¢¤½¤Î¥¹¥¯¥ê¥×¥È¤¬¾åµ­¤Î¥»¥­¥å¥ê¥Æ¥£¸¡ºº¤ò¥Ñ¥¹¤Ç¤­¤ë¤³¤È¤Ç¤¹¡£ + ¥³¥ó¥Ñ¥¤¥ë + »þ¤Î¥ª¥×¥·¥ç¥ó --with-suexec-userdir ¤â»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

    +
    top
    +
    +

    suEXEC ¤Î¥Ç¥Ð¥Ã¥°

    + +

    suEXEC wrapper ¤Ï¡¢¾åµ­¤Ç½Ò¤Ù¤¿ --with-suexec-logfile + ¥ª¥×¥·¥ç¥ó¤Ç»ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¤Ë¥í¥°¾ðÊó¤òµ­Ï¿¤·¤Þ¤¹¡£ + wrapper ¤òŬÀÚ¤ËÀßÄê¡¢¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Æ¤¤¤ë¤È»×¤¦¾ì¹ç¡¢ + ¤É¤³¤Ç̤äƤ¤¤ë¤«¸«¤è¤¦¤È¤¹¤ë¤Ê¤é¤³¤Î¥í¥°¤È¥µ¡¼¥Ð¤Î + ¥¨¥é¡¼¥í¥°¤ò¸«¤ë¤È¤è¤¤¤Ç¤·¤ç¤¦¡£

    +
    top
    +
    +

    ¤È¤«¤²¤ËÃí°Õ: ·Ù¹ð¤È»öÎã

    + +

    Ãí°Õ! + ¤³¤Î¾Ï¤Ï´°Á´¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤³¤Î¾Ï¤ÎºÇ¿·²þÄûÈǤˤĤ¤¤Æ¤Ï¡¢ + Apache ¥°¥ë¡¼¥×¤Î + ¥ª¥ó¥é¥¤¥ó¥É¥­¥å¥á¥ó¥ÈÈǤò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£ +

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê¤ËÀ©¸Â¤ò¤â¤¦¤±¤ë wrapper ¤Ë¤Ä¤¤¤Æ¡¢ + ¤¤¤¯¤Ä¤«¶½Ì£¿¼¤¤ÅÀ¤¬¤¢¤ê¤Þ¤¹¡£suEXEC ¤Ë´Ø¤¹¤ë "¥Ð¥°" + ¤òÊó¹ð¤¹¤ëÁ°¤Ë¤³¤ì¤é¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£

    + +
      +
    • suEXEC ¤Î¶½Ì£¿¼¤¤ÅÀ
      • + +
    • ³¬Áع½Â¤¤ÎÀ©¸Â + + +

      + ¥»¥­¥å¥ê¥Æ¥£¤È¸úΨ¤ÎÍýͳ¤«¤é¡¢suEXEC ¤ÎÁ´¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤Ï + ²¾ÁÛ¥Û¥¹¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ë¤ª¤±¤ëºÇ¾å°Ì¤Î¥É¥­¥å¥á¥ó¥È¥ë¡¼¥ÈÆ⤫¡¢ + ¥æ¡¼¥¶¥Ç¥£¥ì¥¯¥È¥ê¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ë¤ª¤±¤ë¸Ä¡¹¤Î¥æ¡¼¥¶¤ÎºÇ¾å°Ì¤Î + ¥É¥­¥å¥á¥ó¥È¥ë¡¼¥ÈÆâ¤Ë»Ä¤é¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + Î㤨¤Ð¡¢»Í¤Ä¤Î²¾ÁÛ¥Û¥¹¥È¤òÀßÄꤷ¤Æ¤¤¤ë¾ì¹ç¡¢ + ²¾ÁÛ¥Û¥¹¥È¤Î suEXEC ¤ËÍ­Íø¤Ê¤è¤¦¤Ë¡¢¥á¥¤¥ó¤Î Apache + ¥É¥­¥å¥á¥ó¥È³¬Áؤγ°Â¦¤ËÁ´¤Æ¤Î²¾ÁÛ¥Û¥¹¥È¤Î¥É¥­¥å¥á¥ó¥È¥ë¡¼¥È¤ò + ¹½ÃÛ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£(Îã¤Ï¸åÆüµ­ºÜ) +

      +
      • + +
    • suEXEC ¤Î PATH ´Ä¶­ÊÑ¿ô + + +

      + ¤³¤ì¤òÊѹ¹¤¹¤ë¤Î¤Ï´í¸±¤Ç¤¹¡£¤³¤Î»ØÄê¤Ë´Þ¤Þ¤ì¤ë³Æ¥Ñ¥¹¤¬ + ¿®Íê¤Ç¤­¤ë + ¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¢¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£ + À¤³¦¤«¤é¤Î¥¢¥¯¥»¥¹¤Ë¤è¤ê¡¢Ã¯¤«¤¬¥Û¥¹¥È¾å¤Ç¥È¥í¥¤¤ÎÌÚÇÏ + ¤ò¼Â¹Ô¤Ç¤­¤ë¤è¤¦¤Ë¤Ï¤·¤¿¤¯¤Ê¤¤¤Ç¤·¤ç¤¦¡£ +

      +
      • + +
    • suEXEC ¥³¡¼¥É¤Î²þ¤ + + +

      + ·«¤êÊÖ¤·¤Þ¤¹¤¬¡¢²¿¤ò¤ä¤í¤¦¤È¤·¤Æ¤¤¤ë¤«ÇÄ°®¤»¤º¤Ë¤³¤ì¤ò¤ä¤ë¤È + Â礭¤ÊÌäÂê¤ò°ú¤­µ¯¤³¤·¤«¤Í¤Þ¤»¤ó¡£ + ²Äǽ¤Ê¸Â¤êÈò¤±¤Æ¤¯¤À¤µ¤¤¡£ +

      +
      • +
    +
    +
    +

    Available Languages:  en  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/suexec.html.ko.euc-kr b/docs/manual/suexec.html.ko.euc-kr new file mode 100644 index 00000000..ac8a27ac --- /dev/null +++ b/docs/manual/suexec.html.ko.euc-kr @@ -0,0 +1,534 @@ + + + +suEXEC Áö¿ø - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    suEXEC Áö¿ø

    +
    +

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

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

    suEXEC ±â´ÉÀº ¾ÆÆÄÄ¡°¡ CGI¿Í + SSI ÇÁ·Î±×·¥À» À¥¼­¹ö¸¦ ½ÇÇàÇÑ »ç¿ëÀÚ ID°¡ + ¾Æ´Ñ ´Ù¸¥ »ç¿ëÀÚ ID·Î ½ÇÇàÇϵµ·Ï ÇÑ´Ù. º¸Åë CGI³ª SSI ÇÁ·Î±×·¥À» + ½ÇÇàÇϸé À¥¼­¹ö¸¦ ½ÇÇàÇÑ »ç¿ëÀÚ¿Í °°Àº »ç¿ëÀÚ·Î ½ÇÇàÇÑ´Ù.

    + +

    ÀÌ ±â´ÉÀ» ÀûÀýÈ÷ »ç¿ëÇÏ¸é »ç¿ëÀÚ°¡ Á÷Á¢ CGI³ª SSI ÇÁ·Î±×·¥À» + °³¹ßÇÏ°í ½ÇÇàÇÒ¶§ ¹ß»ýÇÒ ¼ö ÀÖ´Â º¸¾ÈÀ§ÇèÀ» »ó´çÈ÷ ÁÙÀÏ + ¼ö ÀÖ´Ù. ±×·¯³ª suEXEC°¡ ºÎÀûÀýÇÏ°Ô ¼³Á¤µÇ¸é ¸¹Àº ¹®Á¦¿Í + ÄÄÇ»ÅÍ¿¡ »õ·Î¿î º¸¾È ÇãÁ¡À» ¸¸µé ¼ö ÀÖ´Ù. ¸¸¾à setuid root + ÇÁ·Î±×·¥°ú ÀÌ·± ÇÁ·Î±×·¥ÀÇ º¸¾È ¹®Á¦¿¡ »ý¼ÒÇÏ´Ù¸é suEXEC¸¦ + »ç¿ëÇÏÁö¾Ê±æ Áø½ÉÀ¸·Î ¹Ù¶õ´Ù.

    +
    + +
    top
    +
    +

    ½ÃÀÛÇϱâ Àü¿¡

    + +

    ½ÃÀÛÇϱâ Àü¿¡ ¿ì¼± ¾ÆÆÄÄ¡±×·ì°ú ÀÌ ¹®¼­ÀÇ °¡Á¤À» ¹àÈù´Ù.

    + +

    ¸ÕÀú setuid¿Í setgid + ±â´ÉÀÌ °¡´ÉÇÑ À¯´Ð½º·ù ¿î¿µÃ¼Á¦¸¦ »ç¿ëÇÑ´Ù°í °¡Á¤ÇÑ´Ù. ¸ðµç + ¸í·É¾î ¿¹µéµµ °°Àº °¡Á¤À» ÇÑ´Ù. suEXEC¸¦ Áö¿øÇÏ´Â ´Ù¸¥ Ç÷¡ÆûÀ» + »ç¿ëÇÏ´Ù¸é ¼³Á¤ÀÌ ´Ù¸¦ ¼ö ÀÖ´Ù.

    + +

    µÎ¹ø°, ´ç½ÅÀÌ ÄÄÇ»ÅÍ º¸¾ÈÀÇ ±âº» °³³ä°ú °ü¸®¿¡ Àͼ÷ÇÏ´Ù°í + °¡Á¤ÇÑ´Ù. ¿©±â¿¡´Â setuid/setgid ±â´É°ú + À̵éÀÌ ½Ã½ºÅÛ°ú º¸¾È¿¡ ¹ÌÄ¡´Â ¿©·¯ ¿µÇâ¿¡ ´ëÇÑ ÀÌÇØ°¡ Æ÷ÇԵȴÙ.

    + +

    ¼¼¹ø°, suEXEC ÄÚµåÀÇ ¼öÁ¤ÇÏÁö¾ÊÀº + ¹öÀüÀ» »ç¿ëÇÑ´Ù°í °¡Á¤ÇÑ´Ù. °³¹ßÀÚ¿Í ¿©·¯ º£Å¸Å×½ºÅ͵éÀº + suEXEC¿Í °ü·ÃµÈ ¸ðµç Äڵ带 Á¶½É½º·´°Ô Á¶»çÇÏ°í °Ë»çÇß´Ù. + Äڵ带 °£´ÜÇÏ°Ô ÇÏ°í È®½ÇÇÑ ¾ÈÀüÀ» º¸ÀåÇϱâÀ§ÇØ ¸ðµç ÁÖÀǸ¦ + ±â¿ï¿´´Ù. ÀÌ Äڵ带 ¼öÁ¤ÇÏ¸é ¿¹»óÄ¡¸øÇÑ ¹®Á¦¿Í »õ·Î¿î º¸¾È + À§ÇèÀÌ ¹ß»ýÇÒ ¼ö ÀÖ´Ù. º¸¾È ÇÁ·Î±×·¡¹Ö¿¡ ´ëÇØ ¸Å¿ì Àß ¾Ë°í + Äڵ带 »ìÆ캸±âÀ§ÇØ ¾ÆÆÄÄ¡±×·ì°ú ÀÛ¾÷À» °øÀ¯ÇÒ Àǻ簡 ¾ø´Ù¸é + suEXEC Äڵ带 ¼öÁ¤ÇÏÁö¾Ê±æ °­·ÂÈ÷ ±ÇÇÑ´Ù.

    + +

    ³×¹ø°ÀÌÀÚ ¸¶Áö¸·À¸·Î, ¾ÆÆÄÄ¡±×·ìÀº suEXEC¸¦ ¾ÆÆÄÄ¡ + ±âº»¼³Ä¡¿¡ Æ÷ÇÔÇÏÁö ¾Ê±â·Î °áÁ¤Çß´Ù. °á±¹ + °ü¸®ÀÚ°¡ ÁÖÀǸ¦ ±â¿ï¿©¼­ suEXEC¸¦ ¼³Á¤ÇØ¾ß ÇÑ´Ù. suEXECÀÇ + ¿©·¯ ¼³Á¤À» Àß °í·ÁÇÑÈÄ °ü¸®ÀÚ´Â ÀϹÝÀûÀÎ ¼³Ä¡¹æ¹ýÀ» suEXEC¸¦ + ¼³Ä¡ÇÒ ¼ö ÀÖ´Ù. suEXEC ±â´ÉÀ» »ç¿ëÇÏ´Â ½Ã½ºÅÛÀÇ º¸¾ÈÀ» Ã¥ÀÓÁö´Â + °ü¸®ÀÚ´Â ÀÌ ¼³Á¤°ªµéÀ» ÁÖÀÇÀÖ°Ô »ìÆ캸°í ÁöÁ¤ÇØ¾ß ÇÑ´Ù. + ÀÌ·± »ó¼¼ÇÑ °úÁ¤Àº suEXEC¸¦ »ç¿ëÇÒ¸¸Å­ ÁÖÀÇÀÖ°í ´ÜÈ£ÇÑ + »ç¶÷¸¸ÀÌ suEXEC¸¦ »ç¿ëÇϵµ·Ï ¾ÆÆÄÄ¡±×·ìÀÌ ¿øÇϱ⠶§¹®ÀÌ´Ù.

    + +

    ¾ÆÁ÷µµ »ç¿ëÇÏ±æ ¿øÇϴ°¡? ±×·±°¡? ÁÁ´Ù. ÀÌÁ¦ ½ÃÀÛÇÏÀÚ!

    +
    top
    +
    +

    suEXEC º¸¾È¸ðµ¨

    + +

    suEXEC¸¦ ±¸¼ºÇÏ°í ¼³Ä¡Çϱâ Àü¿¡ ¿ì¸®´Â º¸¾È¸ðµ¨À» ¸ÕÀú + ¼³¸íÇÑ´Ù. À̸¦ ÅëÇØ Á¤È®È÷ suEXEC ¾È¿¡¼­´Â ¹«½¼ ÀÏÀÌ ÀϾ¸ç + ½Ã½ºÅÛÀÇ º¸¾ÈÀ» À§ÇØ ¹«¾ùÀ» Á¶½ÉÇØ¾ß ÇÒÁö ´õ Àß ÀÌÇØÇÒ ¼ö + ÀÖ´Ù.

    + +

    suEXEC´Â ¾ÆÆÄÄ¡ À¥¼­¹ö°¡ ºÎ¸£´Â setuid + "wrapper" ÇÁ·Î±×·¥À» ±â¹ÝÀ¸·Î ÇÑ´Ù. ÀÌ wrapper´Â °ü¸®ÀÚ°¡ + ÁÖ¼­¹ö¿Í ´Ù¸¥ userid·Î ½ÇÇàÇϵµ·Ï ¼³Á¤ÇÑ CGI³ª SSI ÇÁ·Î±×·¥¿¡ + HTTP ¿äûÀÌ ¿À¸é ºÒ¸°´Ù. ÀÌ·± ¿äûÀÌ ¿À¸é ¾ÆÆÄÄ¡´Â suEXEC + wrapper¿¡°Ô ÇÁ·Î±×·¥¸í°ú ÇÁ·Î±×·¥À» ½ÇÇàÇÒ »ç¿ëÀÚ¿Í ±×·ì + ID¸¦ Á¦°øÇÑ´Ù.

    + +

    ±×·¯¸é wrapper´Â ´ÙÀ½ °úÁ¤À» ÅëÇØ ¼º°ø°ú ½ÇÆи¦ °áÁ¤ÇÑ´Ù. + ÀÌ Á¶°ÇÁß Çϳª¶óµµ ½ÇÆÐÇϸé ÇÁ·Î±×·¥Àº ½ÇÆзΠ±â·ÏµÇ°í ¿À·ù¸¦ + ³»¸ç Á¾·áÇÑ´Ù. ½ÇÆÐÇÏÁö ¾ÊÀ¸¸é °úÁ¤À» °è¼ÓÇÑ´Ù:

    + +
      +
    1. + wrapper¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚ°¡ ½Ã½ºÅÛÀÇ Á¤»óÀûÀÎ + »ç¿ëÀÚÀΰ¡? + +

      + wrapper¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚ°¡ ½ÇÁ¦·Î ½Ã½ºÅÛÀÇ »ç¿ëÀÚÀÎÁö + È®ÀÎÇÑ´Ù. +

      +
      2. + +
    2. + ÀûÀýÇÑ ¼öÀÇ ¾Æ±Ô¸ÕÆ®·Î wrapper¸¦ ½ÇÇàÇϴ°¡? + +

      + wrapper´Â ÀûÀýÇÑ ¼öÀÇ ¾Æ±Ô¸ÕÆ®°¡ ÀÖ¾î¾ß¸¸ ½ÇÇàµÈ´Ù. + ¾ÆÆÄÄ¡ À¥¼­¹ö°¡ ÀÌ °³¼ö¸¦ ¾È´Ù. wrapper°¡ ÀûÀýÇÑ ¼öÀÇ + ¾Æ±Ô¸ÕÆ®¸¦ ¹ÞÁö¸øÇϸé ÇØÅ·µÇ¾ú°Å³ª ¾ÆÆÄÄ¡ÀÇ suEXEC¿¡ + ¹º°¡ ¹®Á¦°¡ ÀÖ´Â °ÍÀÌ´Ù. +

      +
      3. + +
    3. + ÀÌ »ç¿ëÀÚ°¡ wrapper¸¦ ½ÇÇàÇϵµ·Ï Çã¿ëµÇ¾ú³ª? + +

      + ÀÌ »ç¿ëÀÚ°¡ wrapper¸¦ ½ÇÇàÇϵµ·Ï Çã¿ëµÇ¾ú³ª? ¿ÀÁ÷ + ÇÑ »ç¿ëÀÚ(¾ÆÆÄÄ¡ »ç¿ëÀÚ)¸¸ÀÌ ÀÌ ÇÁ·Î±×·¥À» ½ÇÇàÇÒ + ¼ö ÀÖ´Ù. +

      +
      4. + +
    4. + ÁöÁ¤ÇÑ CGI³ª SSI ÇÁ·Î±×·¥ÀÌ ¾ÈÀüÇÏÁö¾ÊÀº °èÃþÂüÁ¶¸¦ + °¡Áö´Â°¡? + +

      + ÁöÁ¤ÇÑ CGI³ª SSI ÇÁ·Î±×·¥ÀÌ '/'·Î ½ÃÀÛÇϰųª µÞÂüÁ¶ + '..'À» °¡Áö´Â°¡? À̵éÀ» »ç¿ëÇÒ ¼ö ¾ø´Ù. ÁöÁ¤ÇÑ CGI/SSI + ÇÁ·Î±×·¥Àº suEXEC ¹®¼­ root (¾Æ·¡ + --with-suexec-docroot=DIR Âü°í) + ³»¿¡ ÀÖ¾î¾ß ÇÑ´Ù. +

      +
      5. + +
    5. + ÁöÁ¤ÇÑ »ç¿ëÀÚ¸íÀÌ À¯È¿ÇÑ°¡? + +

      + ÁöÁ¤ÇÑ »ç¿ëÀÚ°¡ Á¸ÀçÇϴ°¡? +

      +
      6. + +
    6. + ÁöÁ¤ÇÑ ±×·ì¸íÀÌ À¯È¿ÇÑ°¡? + +

      + ÁöÁ¤ÇÑ ±×·ìÀÌ Á¸ÀçÇϴ°¡? +

      +
      7. + +
    7. + ÁöÁ¤ÇÑ »ç¿ëÀÚ°¡ superuser°¡ ¾Æ´Ñ°¡? + + +

      + ÇöÀç suEXEC´Â root°¡ CGI/SSI + ÇÁ·Î±×·¥À» ½ÇÇàÇÒ ¼ö ¾øµµ·Ï ÇÑ´Ù. +

      +
      8. + +
    8. + ÁöÁ¤ÇÑ userid°¡ ÃÖ¼Ò ID ¼ýÀÚº¸´Ù Å«°¡? + +

      + ¼³Á¤¿¡¼­ ÃÖ¼Ò »ç¿ëÀÚ ID ¼ýÀÚ¸¦ ÁöÁ¤ÇÑ´Ù. ±×·¡¼­ CGI/SSI + ÇÁ·Î±×·¥À» ½ÇÇàÇÒ ¼ö ÀÖ´Â useridÀÇ ÃÖ¼ÒÄ¡¸¦ ÁöÁ¤ÇÒ + ¼ö ÀÖ´Ù. "½Ã½ºÅÛ¿ë" °èÁ¤À» Á¦¿ÜÇÒ¶§ À¯¿ëÇÏ´Ù. +

      +
      9. + +
    9. + ÁöÁ¤ÇÑ ±×·ìÀÌ superuser ±×·ìÀÌ ¾Æ´Ñ°¡? + +

      + ÇöÀç suEXEC´Â root ±×·ìÀÌ CGI/SSI + ÇÁ·Î±×·¥À» ½ÇÇàÇÒ ¼ö ¾øµµ·Ï ÇÑ´Ù. +

      +
      10. + +
    10. + ÁöÁ¤ÇÑ groupid°¡ ÃÖ¼Ò ID ¼ýÀÚº¸´Ù Å«°¡? + +

      + ¼³Á¤¿¡¼­ ÃÖ¼Ò ±×·ì ID ¼ýÀÚ¸¦ ÁöÁ¤ÇÑ´Ù. ±×·¡¼­ CGI/SSI + ÇÁ·Î±×·¥À» ½ÇÇàÇÒ ¼ö ÀÖ´Â groupidÀÇ ÃÖ¼ÒÄ¡¸¦ ÁöÁ¤ÇÒ + ¼ö ÀÖ´Ù. "½Ã½ºÅÛ¿ë" ±×·ìÀ» Á¦¿ÜÇÒ¶§ À¯¿ëÇÏ´Ù. +

      +
      11. + +
    11. + wrapper°¡ ¼º°øÀûÀ¸·Î ÁöÁ¤ÇÑ »ç¿ëÀÚ¿Í ±×·ìÀÌ + µÉ ¼ö Àִ°¡? + +

      + ÀÌ ´Ü°è¿¡¼­ ÇÁ·Î±×·¥Àº setuid¿Í setgid È£ÃâÀ» ÇÏ¿© + ÁöÁ¤ÇÑ »ç¿ëÀÚ¿Í ±×·ìÀÌ µÈ´Ù. ¶Ç, ±×·ì Á¢±Ù¸ñ·ÏÀº + »ç¿ëÀÚ°¡ ÇØ´çµÈ ¸ðµç ±×·ìÀ¸·Î ÃʱâÈ­µÈ´Ù. +

      +
      12. + +
    12. + CGI/SSI ÇÁ·Î±×·¥ÀÌ ÀÖ´Â µð·ºÅ丮·Î µð·ºÅ丮¸¦ + º¯°æÇÒ ¼ö Àִ°¡? + +

      + µð·ºÅ丮°¡ Á¸ÀçÇÏÁö ¾Ê´Ù¸é ÆÄÀÏÀÌ ÀÖÀ» ¼ö ¾ø´Ù. ÀÌ°÷À¸·Î + µð·ºÅ丮¸¦ º¯°æÇÒ ¼ö ¾ø´Ù¸é µð·ºÅ丮´Â Á¸ÀçÇÏÁö ¾ÊÀ» + °ÍÀÌ´Ù. +

      +
      13. + +
    13. + µð·ºÅ丮°¡ ¾ÆÆÄÄ¡ À¥°ø°£ ¾È¿¡ Àִ°¡? + +

      + ¼­¹öÀÇ ÀϹÝÀûÀÎ ºÎºÐÀ» ¿äûÇÒ °æ¿ì ¿äûÇÏ´Â µð·ºÅ丮°¡ + suEXEC ¹®¼­ root ¾Æ·¡ Àִ°¡? UserDirÀ» ¿äûÇÒ °æ¿ì + ¿äûÇÏ´Â µð·ºÅ丮°¡ suEXEC userdir·Î ¼³Á¤ÇÑ (suEXEC ¼³Á¤ ¿É¼Ç Âü°í) µð·ºÅ丮 + ¾Æ·¡¿¡ Àִ°¡? +

      +
      14. + +
    14. + ´Ù¸¥ ´©±¸µµ µð·ºÅ丮¿¡ ¾²±â±ÇÇÑÀÌ ¾ø´Â°¡? + +

      + µð·ºÅ丮¸¦ ´Ù¸¥ »ç¶÷¿¡°Ô ¿­¾îµÎ±æ ¿øÇÏÁö¾Ê´Â´Ù. ¿ÀÁ÷ + ¼ÒÀ¯ÀÚ¸¸ÀÌ µð·ºÅ丮 ³»¿ëÀ» º¯°æÇÒ ¼ö ÀÖ´Ù. +

      +
      15. + +
    15. + ÁöÁ¤ÇÑ CGI/SSI ÇÁ·Î±×·¥ÀÌ Á¸ÀçÇϴ°¡? + +

      + Á¸ÀçÇÏÁö¾Ê´Ù¸é ½ÇÇàÇÒ ¼öµµ ¾ø´Ù. +

      +
      16. + +
    16. + ´Ù¸¥ ´©±¸µµ ÁöÁ¤ÇÑ CGI/SSI ÇÁ·Î±×·¥¿¡ ¾²±â±ÇÇÑÀÌ + ¾ø´Â°¡? + +

      + ¼ÒÀ¯ÀÚ¿Ü ´©±¸µµ CGI/SSI ÇÁ·Î±×·¥À» º¯°æÇÏ±æ ¿øÇÏÁö¾Ê´Â´Ù. +

      +
      17. + +
    17. + ÁöÁ¤ÇÑ CGI/SSI ÇÁ·Î±×·¥ÀÌ setuid³ª setgid°¡ + ¾Æ´Ñ°¡? + +

      + ¿ì¸®´Â ÇÁ·Î±×·¥ÀÌ ´Ù½Ã UID/GID¸¦ º¯°æÇÏ±æ ¿øÇÏÁö¾Ê´Â´Ù. +

      +
      18. + +
    18. + ÁöÁ¤ÇÑ »ç¿ëÀÚ/±×·ìÀÌ ÇÁ·Î±×·¥ÀÇ »ç¿ëÀÚ/±×·ì°ú °°Àº°¡? + +

      + »ç¿ëÀÚ°¡ ÆÄÀÏÀÇ ¼ÒÀ¯ÀÚÀΰ¡? +

      +
      19. + +
    19. + ¾ÈÀüÇÑ µ¿ÀÛÀ» À§ÇØ ÇÁ·Î¼¼½ºÀÇ È¯°æº¯¼ö¸¦ û¼ÒÇÒ + ¼ö Àִ°¡? + +

      + suEXEC´Â (¼³Á¤¿¡¼­ Á¤ÀÇÇÑ) ¾ÈÀüÇÑ ½ÇÇà PATH¸¦ Àâ°í, + (À̰͵µ ¼³Á¤¿¡¼­ Á¤ÀÇ) ¾ÈÀüÇÑ È¯°æº¯¼ö ¸ñ·Ï¿¡ ¿­°ÅµÈ + º¯¼ö¸¸ ³²±â°í ÇÁ·Î¼¼½ºÀÇ È¯°æº¯¼ö¸¦ Áö¿î´Ù. +

      +
      20. + +
    20. + ¼º°øÀûÀ¸·Î ÁöÁ¤ÇÑ CGI/SSI ÇÁ·Î±×·¥À» ½ÇÇàÇÒ + ¼ö Àִ°¡? + +

      + ¿©±â¼­ suEXEC°¡ ³¡³ª°í ÁöÁ¤ÇÑ CGI/SSI ÇÁ·Î±×·¥ÀÌ ½ÃÀÛÇÑ´Ù. +

      +
      21. +
    + +

    ÀÌ°ÍÀÌ suEXEC wrapper º¸¾È¸ðµ¨ÀÇ Ç¥ÁØ µ¿ÀÛÀÌ´Ù. ´Ù¼Ò + ¾ö°ÝÇÏ°í CGI/SSI ¼³°è¿¡ »õ·Î¿î Á¦ÇÑÀÌ µÇÁö¸¸, º¸¾ÈÀ» ¿°µÎ¿¡ + µÎ°í ÇѴܰ辿 Á¶½É½º·´°Ô ¸¸µé¾îÁ³´Ù.

    + +

    ÀÌ º¸¾È ¸ðµ¨ÀÌ ¼­¹ö ¼³Á¤¿¡ ¾î¶² Á¦ÇÑÀ» ÁÖ´ÂÁö¿Í ÀûÀýÇÑ + suEXEC ¼³Á¤À¸·Î ¾î¶² º¸¾È À§ÇèÀ» ÇÇÇÒ ¼ö ÀÖ´ÂÁö¿¡ ´ëÇØ ÀÌ + ¹®¼­ÀÇ "´Ù½Ã Çѹø Á¶½ÉÇ϶ó" ÀýÀ» + Âü°íÇ϶ó.

    +
    top
    +
    +

    suEXEC ±¸¼º°ú ¼³Ä¡

    + +

    ÀÌÁ¦ Àç¹ÌÀÖ´Â ³»¿ëÀÌ ½ÃÀÛÇÑ´Ù.

    + +

    suEXEC ±¸¼º ¿É¼Ç
    +

    + +
    +
    --enable-suexec
    + +
    ÀÌ ¿É¼ÇÀº ±âº»ÀûÀ¸·Î ¼³Ä¡µÇ°Å³ª È°¼ºÈ­µÇÁö¾Ê´Â suEXEC + ±â´ÉÀ» È°¼ºÈ­ÇÑ´Ù. APACI°¡ suEXEC¸¦ ¹Þ¾ÆµéÀÌ·Á¸é + --enable-suexec ¿É¼Ç¿Ü¿¡ + --with-suexec-xxxxx ¿É¼ÇÀÌ ÃÖ¼ÒÇÑ ÇÑ°³ + ÇÊ¿äÇÏ´Ù.
    + +
    --with-suexec-bin=PATH
    + +
    suexec ¹ÙÀ̳ʸ® °æ·Î´Â º¸¾È»ó ÀÌÀ¯·Î + ¼­¹ö¿¡ ±â·ÏµÇ¾ß ÇÑ´Ù. °æ·Î ±âº»°ªÀ» ¹«½ÃÇÏ·Á¸é ÀÌ ¿É¼ÇÀ» + »ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î + --with-suexec-bin=/usr/sbin/suexec
    + +
    --with-suexec-caller=UID
    + +
    º¸Åë ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚ¸í. ÇÁ·Î±×·¥À» + ½ÇÇàÇÒ ¼ö ÀÖ´Â À¯ÀÏÇÑ »ç¿ëÀÚ´Ù.
    + +
    --with-suexec-userdir=DIR
    + +
    suEXEC Á¢±ÙÀÌ Çã¿ëµÇ´Â »ç¿ëÀÚ È¨µð·ºÅ丮ÀÇ ÇÏÀ§µð·ºÅ丮¸¦ + ÁöÁ¤ÇÑ´Ù. ÀÌ µð·ºÅ丮¿¡ ÀÖ´Â ¸ðµç ½ÇÇàÆÄÀÏÀ» »ç¿ëÀÚÀÇ + suEXEC·Î ½ÇÇà¹Ç·Î, ¸ðµç ÇÁ·Î±×·¥ÀÌ "¾ÈÀüÇؾß" ÇÑ´Ù. (¿¹¸¦ + µé¾î, °ª¿¡ "*"ÀÌ ¾ø´Â) "°£´ÜÇÑ" UserDir Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù¸é + °°Àº °ªÀ» ¼³Á¤ÇØ¾ß ÇÑ´Ù. UserDir Áö½Ã¾î°¡ passwd ÆÄÀÏ¿¡ + ³ª¿Â »ç¿ëÀÚ È¨µð·ºÅ丮¿Í ´Ù¸£¸é suEXEC´Â Á¤»óÀûÀ¸·Î + ÀÛµ¿ÇÏÁö ¾Ê´Â´Ù. ±âº»°ªÀº "public_html"ÀÌ´Ù.
    + °¡»óÈ£½ºÆ®µéÀÌ °¢°¢ ´Ù¸¥ UserDirÀ» »ç¿ëÇÑ´Ù¸é ¸ðµÎ ÇÑ + ºÎ¸ð µð·ºÅ丮 ¾È¿¡ ÀÖµµ·Ï Á¤ÀÇÇØ¾ß ÇÏ°í, ±× ºÎ¸ð µð·ºÅ丮¸íÀ» + ¿©±â Àû´Â´Ù. ÀÌ·¸°Ô Á¤ÀÇÇÏÁö ¾ÊÀ¸¸é, "~userdir" + cgi ¿äûÀÌ ÀÛµ¿ÇÏÁö ¾Ê´Â´Ù!
    + +
    --with-suexec-docroot=DIR
    + +
    ¾ÆÆÄÄ¡ÀÇ DocumentRoot¸¦ Á¤ÀÇÇÑ´Ù. ÀÌ´Â suEXEC°¡ »ç¿ëÇÒ + ¼ö ÀÖ´Â (UserDirsÀ» Á¦¿ÜÇÑ) À¯ÀÏÇÑ °ø°£ÀÌ´Ù. ±âº» µð·ºÅ丮´Â + --datadir °ª¿¡ "/htdocs"À» ºÙÀÎ °ÍÀÌ´Ù. + ¿¹¸¦ µé¾î "--datadir=/home/apache"·Î + ±¸¼ºÇß´Ù¸é suEXEC wrapper´Â document root·Î + "/home/apache/htdocs" µð·ºÅ丮¸¦ »ç¿ëÇÑ´Ù.
    + +
    --with-suexec-uidmin=UID
    + +
    suEXEC¿¡¼­ ÁöÁ¤°¡´ÉÇÑ »ç¿ëÀÚÀÇ ÃÖ¼Ò UID¸¦ Á¤ÀÇÇÑ´Ù. + ´ëºÎºÐÀÇ ½Ã½ºÅÛ¿¡¼­ 500À̳ª 100ÀÌ ÀûÀýÇÏ´Ù. ±âº»°ªÀº + 100ÀÌ´Ù.
    + +
    --with-suexec-gidmin=GID
    + +
    suEXEC¿¡¼­ ÁöÁ¤°¡´ÉÇÑ ±×·ìÀÇ ÃÖ¼Ò GID¸¦ Á¤ÀÇÇÑ´Ù. + ´ëºÎºÐÀÇ ½Ã½ºÅÛ¿¡¼­ 100ÀÌ ÀûÀýÇϹǷΠÀÌ °ªÀÌ ±âº»°ªÀÌ´Ù.
    + +
    --with-suexec-logfile=FILE
    + +
    ¸ðµç suEXEC ÀÛµ¿°ú ¿À·ù¸¦ (°¨½Ã³ª µð¹ö±ë ¸ñÀû¿¡ À¯¿ëÇÑ) + ±â·ÏÇÒ ·Î±×ÆÄÀϸíÀ» ÁöÁ¤ÇÑ´Ù. ±âº»ÀûÀ¸·Î ·Î±×ÆÄÀÏÀÇ À̸§Àº + "suexec_log"ÀÌ°í Ç¥ÁØ ·Î±×ÆÄÀÏ µð·ºÅ丮¿¡ + (--logfiledir) À§Ä¡ÇÑ´Ù.
    + +
    --with-suexec-safepath=PATH
    + +
    CGI ½ÇÇàÆÄÀÏ¿¡ ³Ñ°ÜÁú ¾ÈÀüÇÑ PATH ȯ°æº¯¼ö¸¦ Á¤ÀÇÇÑ´Ù. + ±âº»°ªÀº "/usr/local/bin:/usr/bin:/bin"ÀÌ´Ù.
    +
    + +

    suEXEC wrapper¸¦ ÄÄÆÄÀÏÇÏ°í ¼³Ä¡Çϱâ
    + --enable-suexec ¿É¼ÇÀ¸·Î suEXEC ±â´ÉÀ» °¡´ÉÇÏ°ÔÇÑ + °æ¿ì make ¸í·É¾î¸¦ ½ÇÇàÇϸé suexec + ½ÇÇàÆÄÀÏÀÌ (¾ÆÆÄÄ¡¿Í ÇÔ²²) ÀÚµ¿À¸·Î ¸¸µé¾îÁø´Ù.
    + ¸ðµç°ÍÀ» ÄÄÆÄÀÏÇÑ ÈÄ make install ¸í·É¾î¸¦ + ½ÇÇàÇÏ¿© ¼³Ä¡ÇÒ ¼ö ÀÖ´Ù. ¹ÙÀ̳ʸ®ÆÄÀÏ suexec´Â + --sbindir ¿É¼ÇÀ¸·Î ÁöÁ¤ÇÑ µð·ºÅ丮¿¡ ¼³Ä¡µÈ´Ù. + ±âº» À§Ä¡´Â "/usr/local/apache2/sbin/suexec"ÀÌ´Ù.
    + ¼³Ä¡ °úÁ¤¿¡ root ±ÇÇÑÀÌ ÇÊ¿äÇÔÀ» + ÁÖÀÇÇ϶ó. wrapper°¡ »ç¿ëÀÚ ID¸¦ ¼³Á¤ÇϱâÀ§Çؼ­´Â ¼ÒÀ¯ÀÚ°¡ + rootÀÌ°í ÆÄÀϸðµå·Î setuserid ½ÇÇàºñÆ®°¡ + ¼³Á¤µÇ¾ß ÇÑ´Ù.

    + +

    ÆíÁýÁõÀûÀÎ ±ÇÇѼ³Á¤
    + suEXEC wrapper´Â ÀÚ½ÅÀ» ½ÇÇàÇÑ »ç¿ëÀÚ°¡ ±¸¼º ¿É¼Ç + --with-suexec-caller·Î ÁöÁ¤ÇÑ ¿Ã¹Ù¸¥ »ç¿ëÀÚÀÎÁö + È®ÀÎÀ» ÇÏÁö¸¸, ÀÌ °Ë»ç ÀÌÀü¿¡ suEXEC°¡ »ç¿ëÇÏ´Â ½Ã½ºÅÛÈ£Ãâ + ȤÀº ¶óÀ̺귯¸® ÇÔ¼ö°¡ Á¶À۵ǾúÀ» ¼ö ÀÖ´Ù. À̸¦ ´ëºñÇϸç + ÀϹÝÀûÀ¸·Î ÁÁÀº ½À°üÀ̹ǷΠ¿ÀÁ÷ ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏ´Â ±×·ì¸¸ÀÌ + suEXEC¸¦ ½ÇÇàÇÒ ¼ö ÀÖµµ·Ï ÆÄÀϽýºÅÛ ±ÇÇÑÀ» ÁöÁ¤ÇØ¾ß ÇÑ´Ù.

    + +

    ¿¹¸¦ µé¾î, À¥¼­¹ö¸¦ ´ÙÀ½°ú °°ÀÌ ¼³Á¤ÇÏ°í:

    + +

    + User www
    + Group webgroup
    +

    + +

    suexec¸¦ "/usr/local/apache2/sbin/suexec"¿¡ + ¼³Ä¡ÇÏ¿´´Ù¸é, ´ÙÀ½À» ½ÇÇàÇØ¾ß ÇÑ´Ù:

    + +

    + chgrp webgroup /usr/local/apache2/bin/suexec
    + chmod 4750 /usr/local/apache2/bin/suexec
    +

    + +

    ±×·¯¸é ¿ÀÁ÷ ¾ÆÆÄÄ¡¸¦ ½ÇÇàÇÏ´Â ±×·ì¸¸ÀÌ suEXEC wrapper¸¦ + ½ÇÇàÇÒ ¼ö ÀÖ´Ù.

    +
    top
    +
    +

    suEXEC Å°°í ²ô±â

    + +

    ¾ÆÆÄÄ¡´Â ½ÃÀÛÇÒ¶§ --sbindir ¿É¼ÇÀ¸·Î ÁöÁ¤ÇÑ + µð·ºÅ丮¿¡¼­ suexec ÆÄÀÏÀ» (±âº»°ª + "/usr/local/apache2/sbin/suexec") ã´Â´Ù. ¾ÆÆÄÄ¡°¡ + Á¤»óÀûÀ¸·Î ±¸¼ºµÈ suEXEC wrapper¸¦ ¹ß°ßÇÏ¸é ¿À·ù ·Î±×(error + log)¿¡ ´ÙÀ½°ú °°ÀÌ Ãâ·ÂÇÑ´Ù:

    + +

    + [notice] suEXEC mechanism enabled (wrapper: /path/to/suexec) +

    + +

    ¼­¹ö ½ÃÀÛÁß¿¡ ÀÌ·± ¹®±¸¸¦ ¾ø´Ù¸é ¼­¹ö´Â ±â´ëÇÑ Àå¼Ò¿¡¼­ + wrapper ÇÁ·Î±×·¥À» ãÁö ¸øÇ߰ųª, ½ÇÇàÆÄÀÏÀÌ setuid + root·Î ¼³Ä¡µÇÁö¾Ê¾Ò±â ¶§¹®ÀÏ °ÍÀÌ´Ù.

    + +

    óÀ½À¸·Î suEXEC ±â´ÉÀ» »ç¿ëÇÏ°í ½Í°í ÀÌ¹Ì ¾ÆÆÄÄ¡ ¼­¹ö°¡ + ½ÇÇàÁßÀ̶ó¸é, ¾ÆÆÄÄ¡¸¦ Á×ÀÌ°í ´Ù½Ã ½ÃÀÛÇØ¾ß ÇÑ´Ù. °£´ÜÈ÷ + HUPÀ̳ª USR1 ½Ã±×³Î·Î Àç½ÃÀÛÇÏ´Â °ÍÀ¸·Î´Â ÃæºÐÇÏÁö ¾Ê´Ù.

    +

    suEXEC¸¦ ¾È»ç¿ëÇÏ·Á¸é suexec ÆÄÀÏÀ» Áö¿îÈÄ + ¾ÆÆÄÄ¡¸¦ Á×ÀÌ°í Àç½ÃÀÛÇØ¾ß ÇÑ´Ù.

    +
    top
    +
    +

    suEXEC »ç¿ëÇϱâ

    + +

    CGI ÇÁ·Î±×·¥ ¿äûÀÇ °æ¿ì SuexecUserGroup Áö½Ã¾î¸¦ + »ç¿ëÇÑ °¡»óÈ£½ºÆ®¿¡ ¿äûÀ» ÇÏ¿´°Å³ª mod_userdirÀÌ + ¿äûÀ» ó¸®ÇÏ´Â °æ¿ì¿¡¸¸ suEXEC wrapper¸¦ È£ÃâÇÑ´Ù.

    + +

    °¡»óÈ£½ºÆ®:
    suEXEC wrapper¸¦ + »ç¿ëÇÏ´Â ÇÑ°¡Áö ¹æ¹ýÀº VirtualHost Á¤ÀÇ¿¡ SuexecUserGroup Áö½Ã¾î¸¦ + »ç¿ëÇÏ´Â °ÍÀÌ´Ù. ÀÌ Áö½Ã¾î¸¦ ÁÖ¼­¹ö »ç¿ëÀÚ ID¿Í ´Ù¸£°Ô + ¼³Á¤Çϸé CGI ÀÚ¿øÀÇ ¸ðµç ¿äûÀÌ <VirtualHost>¿¡¼­ + ÁöÁ¤ÇÑ User¿Í GroupÀ¸·Î ½ÇÇàµÈ´Ù. ÀÌ + Áö½Ã¾îµéÀÌ <VirtualHost>¿¡ ¾øÀ¸¸é ÁÖ¼­¹ö + userid¸¦ »ç¿ëÇÑ´Ù.

    + +

    »ç¿ëÀÚ µð·ºÅ丮:
    + mod_userdirÀÌ ¿äûÀ» ó¸®ÇÑ´Ù¸é suEXEC + wrapper¸¦ È£ÃâÇÏ¿©, ¿äûÇÑ »ç¿ëÀÚ µð·ºÅ丮¿¡ ÇØ´çÇÏ´Â »ç¿ëÀÚ + ID·Î CGI ÇÁ·Î±×·¥À» ½ÇÇàÇÑ´Ù. ÀÌ ±â´ÉÀÌ µ¿ÀÛÇÏ·Á¸é »ç¿ëÀÚ + ID·Î CGI¸¦ ½ÇÇàÇÒ ¼ö ÀÖ°í ½ºÅ©¸³Æ®°¡ À§ÀÇ º¸¾È + °Ë»ç Ç׸ñÀ» ¸¸Á·ÇØ¾ß ÇÑ´Ù. ±¸¼º + ¿É¼Ç --with-suexec-userdirÀ» Âü°íÇ϶ó.

    top
    +
    +

    suEXEC µð¹ö±ëÇϱâ

    + +

    suEXEC wrapper´Â ·Î±× Á¤º¸¸¦ À§¿¡¼­ ´Ù·é + --with-suexec-logfile ¿É¼ÇÀ¸·Î ÁöÁ¤ÇÑ ÆÄÀÏ¿¡ + ¾´´Ù. wrapper¸¦ ¿Ã¹Ù·Î ±¸¼ºÇÏ°í ¼³Ä¡Çß´Ù¸é ¾îµð¼­ À߸øµÇ¾ú´ÂÁö + ÀÌ ·Î±×ÆÄÀÏ¿Í ¼­¹öÀÇ error_log¸¦ »ìÆìºÁ¶ó.

    + +
    top
    +
    +

    ´Ù½Ã Çѹø Á¶½ÉÇ϶ó: °æ°í¿Í ¿¹Á¦

    + +

    ÁÖÀÇ! ÀÌ ¼½¼ÇÀº ¿ÏÀüÇÏÁö ¾ÊÀ» ¼ö ÀÖ´Ù. + ¾ÆÆÄÄ¡±×·ìÀÇ ¿Â¶óÀÎ + ¹®¼­¿¡¼­ ÀÌ ¹®¼­ÀÇ ÃÖ½ÅÆÇÀ» Âü°íÇ϶ó.

    + +

    wrapper°¡ ¼­¹ö ¼³Á¤À» Á¦¾àÇÏ´Â ¸î°¡Áö Èï¹Ì·Î¿î Á¡ÀÌ ÀÖ´Ù. + suEXEC¿Í °ü·ÃµÈ "¹ö±×"¸¦ º¸°íÇϱâ Àü¿¡ À̵éÀ» »ìÆ캸±æ ¹Ù¶õ´Ù.

    + +
      +
    • suEXEC Á¦¾à »çÇ×
      • + +
    • + µð·ºÅ丮 ±¸Á¶ Á¦ÇÑ + +

      + º¸¾È°ú È¿À²¼ºÀ» À§ÇØ ¸ðµç suEXEC ¿äûÀº °¡»óÈ£½ºÆ®ÀÇ + °æ¿ì ÃÖ»óÀ§ document root ȤÀº userdir ¿äûÀÇ °æ¿ì + ÃÖ»óÀ§ °³ÀÎ document root ¾È¿¡¼­ ¹ß»ýÇØ¾ß ÇÑ´Ù. ¿¹¸¦ + µé¾î, °¡»óÈ£½ºÆ® ³×°³¸¦ ¼³Á¤Çß´Ù¸é °¡»óÈ£½ºÆ®¿¡¼­ + suEXEC¸¦ ÀÌ¿ëÇϱâÀ§ÇØ °¡»óÈ£½ºÆ®ÀÇ document root¸¦ + ÁÖ ¾ÆÆÄÄ¡ ¹®¼­ °èÃþ±¸Á¶ ¹Û¿¡ ¼³Á¤ÇÒ ÇÊ¿ä°¡ ÀÖ´Ù. + (¿¹Á¦´Â ´ÙÀ½¿¡.) +

      +
      • + +
    • + suEXECÀÇ PATH ȯ°æº¯¼ö + +

      + º¯°æÇϸé À§ÇèÇÒ ¼ö ÀÖ´Ù. ¿©±â¿¡ Æ÷ÇÔÇÏ´Â ¸ðµç °æ·Î°¡ + ¹ÏÀ» ¼ö ÀÖ´Â µð·ºÅ丮ÀÎÁö È®ÀÎÇ϶ó. + ÀÌ Áö±¸»óÀÇ ´©±º°¡°¡ ±×°÷¿¡ ÀÖ´Â Æ®·ÎÀ̸ñ¸¶¸¦ ½ÇÇàÇϱæ + ¿øÇÏÁö ¾ÊÀ» °ÍÀÌ´Ù. +

      +
      • + +
    • + suEXEC ÄÚµå ¼öÁ¤Çϱâ + +

      + ¹Ýº¹Çؼ­ ¸»ÇÏÁö¸¸, ´ç½ÅÀÌ ¹«¾ùÀ» ÇÏ´ÂÁö ¸ð¸£°í ½ÃµµÇÑ´Ù¸é + Å« ¹®Á¦°¡ ¹ß»ýÇÒ ¼ö ÀÖ´Ù. ¾î¶² °æ¿ì¿¡µµ + ¼öÁ¤ÇÏÁö¸¶¶ó. +

      +
      • +
    + +
    +
    +

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

    +
    + \ No newline at end of file diff --git a/docs/manual/upgrading.html b/docs/manual/upgrading.html new file mode 100644 index 00000000..e32040ec --- /dev/null +++ b/docs/manual/upgrading.html @@ -0,0 +1,23 @@ +URI: upgrading.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: upgrading.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: upgrading.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: upgrading.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: upgrading.html.pt-br +Content-Language: pt-br +Content-type: text/html; charset=ISO-8859-1 + +URI: upgrading.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R diff --git a/docs/manual/upgrading.html.de b/docs/manual/upgrading.html.de new file mode 100644 index 00000000..eaa88312 --- /dev/null +++ b/docs/manual/upgrading.html.de @@ -0,0 +1,120 @@ + + + +Upgrade von 2.0 auf 2.2 - Apache HTTP Server + + + + +
    +

    Module | Direktiven | FAQ | Glossar | Seitenindex

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Upgrade von 2.0 auf 2.2

    +
    +

    Verfügbare Sprachen:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    +
    Diese Übersetzung ist möglicherweise + nicht mehr aktuell. Bitte prüfen Sie die englische Version auf + die neuesten Änderungen.
    + +

    Dieses Dokument dient der Unterstützung beim Upgrade. Es + enthält die entscheidenden Informationen für bisherige + Apache-Nutzer. Diese sind als kurze Anmerkungen + gedacht. Weitere Informationen finden Sie entweder unter + Neue Funktionen oder in + den src/CHANGES-Dateien.

    + +

    Dieses Dokument beschreibt lediglich die Änderungen von Version + 2.2 gegenüber Version 2.0. Wenn Sie ein Upgrade von Version 1.3 + durchführen, sollten Sie auch Upgrade von 1.3 + auf 2.0 zu Rate ziehen.

    +
    + +
    top
    +
    +

    Änderungen der Konfiguration bei der Kompilierung

    + + +
    top
    +
    +

    Änderungen der Laufzeit-Konfiguration

    + + +
      +
    • Die mit dem Apache HTTP Server ausgelieferte Konfigurationsdatei + httpd.conf wurde stark vereinfacht, indem alle außer + den unbedingt notwendigen Konfigurationseinstellungen entfernt wurden. + Im conf/extra/-Verzeichnis Ihrer Installation finden Sie + eine Reihe von Konfigurationsbeispielen für erweiterte Funktionen. +
      • + +
    • Die apachectl-Option startssl gibt es + nicht mehr. Um SSL-Unterstützung zu aktivieren müssen Sie die + httpd.conf editieren und die entsprechenden + mod_ssl-Anweisungen einfügen und + anschließend den Server mit apachectl start starten. + Eine Beispielkonfiguration zum Aktivieren von mod_ssl + ist in conf/extra/httpd-ssl.conf enthalten. +
      • + +
    • Die Voreinstellung von UseCanonicalName ist jetzt Off. + Wenn diese Anweisung nicht in Ihrer Konfigurationsdatei enthalten ist, + können Sie UseCanonicalName On einfügen, um das + bisherige Verhalten beizubehalten. +
      • + +
    • Das Modul mod_userdir reagiert nicht länger auf + Anfragen, solange nicht in der Konfigurationsdatei eine UserDir-Anweisung enthalten ist, die + einen Verzeichnisnamen angibt. Fügen Sie Ihrer Konfigurationsdatei + die Anweisung UserDir public_html hinzu, um das + bisherige Verhalten wiederherzustellen. +
      • +
    +
    top
    +
    +

    Sonstige Änderungen

    + + +
    top
    +
    +

    Module von Drittanbietern

    + + +
    +
    +

    Verfügbare Sprachen:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/upgrading.html.en b/docs/manual/upgrading.html.en new file mode 100644 index 00000000..5924addf --- /dev/null +++ b/docs/manual/upgrading.html.en @@ -0,0 +1,156 @@ + + + +Upgrading to 2.2 from 2.0 - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Upgrading to 2.2 from 2.0

    +
    +

    Available Languages:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    + +

    In order to assist folks upgrading, we maintain a document + describing information critical to existing Apache users. These + are intended to be brief notes, and you should be able to find + more information in either the New Features document, or in + the src/CHANGES file.

    + +

    This document describes only the changes from 2.0 to 2.2. If you + are upgrading from version 1.3, you should also consult the 1.3 to 2.0 + upgrading document.

    + +
    + +
    top
    +
    +

    Compile-Time Configuration Changes

    + + +

    The compilation process is very similar to the one used in + version 2.0. Your old configure command line (as + found in build/config.nice in the installed server + directory) can be used in some cases. The most significant change + required will be to account for changes in module names, in + particular for the authentication and authorization modules. + Some details of changes:

    + + + +
    top
    +
    +

    Run-Time Configuration Changes

    + + +

    Your existing version 2.0 config files and startup scripts can + usually be used unchanged in version 2.2. Some small + adjustments may be necessary for particular configurations as + discussed below. In addition, if you dynamically load the + standard modules using the LoadModule directive, then you will + need to account for the module name changes mentioned above.

    + +

    If you choose to use the new default + configuration file for version 2.2, you will find that it has + been greatly simplified by removing all but the most essential + configuration settings. A set of example configuration settings + for more advanced features is present in the + conf/extra/ directory of the installed server. Default + configuration files are installed in the conf/original + directory.

    + +

    Some runtime configuration changes that you may notice:

    + +
      +
    • The apachectl option + startssl is no longer available. To enable SSL + support, you should edit httpd.conf to include the + relevant mod_ssl directives and then use + apachectl start to start the server. An example + configuration to activate mod_ssl has been + included in conf/extra/httpd-ssl.conf.
      • + +
    • The default setting of UseCanonicalName is now + Off. If you did not have this directive in your + config file, you can add UseCanonicalName On to + retain the old behavior.
      • + +
    • The module mod_userdir will no longer act + on requests unless a UserDir directive specifying a + directory name is present in the config file. To restore the + old default behavior, place the directive UserDir + public_html in your config file.
      • + +
    +
    top
    +
    +

    Misc Changes

    + + +
      +
    • The module mod_cache, which was + experimental in Apache 2.0, is now a standard module.
      • + +
    • The module mod_disk_cache, which was + experimental in Apache 2.0, is now a standard module.
      • + +
    • The module mod_mem_cache, which was + experimental in Apache 2.0, is now a standard module.
      • + +
    • The module mod_charset_lite, which was + experimental in Apache 2.0, is now a standard module.
      • + +
    • The module mod_dumpio, which was + experimental in Apache 2.0, is now a standard module.
      • + +
    +
    top
    +
    +

    Third Party Modules

    + + +

    Many third-party modules designed for version 2.0 will work + unchanged with the the Apache HTTP Server version 2.2. But all + modules must be recompiled before being loaded.

    + +
    +
    +

    Available Languages:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/upgrading.html.ja.euc-jp b/docs/manual/upgrading.html.ja.euc-jp new file mode 100644 index 00000000..f60f2aa1 --- /dev/null +++ b/docs/manual/upgrading.html.ja.euc-jp @@ -0,0 +1,222 @@ + + + +1.3 ¤«¤é 2.0 ¤Ø¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É - Apache HTTP ¥µ¡¼¥Ð + + + + +
    +

    ¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

    +

    Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

    +
    +
    <-
    +

    1.3 ¤«¤é 2.0 ¤Ø¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É

    +
    +

    Available Languages:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    +
    This translation may be out of date. Check the + English version for recent changes.
    + +

    ¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò´Êñ¤Ë¤¹¤ë¤¿¤á¤Ë¡¢´û¸¤Î Apache ¥æ¡¼¥¶¤Ë + Èó¾ï¤Ë½ÅÍפʾðÊó¤ò¤³¤Îʸ½ñ¤Ë¤Þ¤È¤á¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ïû¤¤ + Ãí°Õ½ñ¤­¤È¤·¤Æ½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï + ¿·µ¡Ç½¤Îʸ½ñ¤ä + src/CHANGES ¥Õ¥¡¥¤¥ë¤Ç¸«¤Ä¤±¤é¤ì¤ë¤È»×¤¤¤Þ¤¹¡£

    +
    + +
    top
    +
    +

    ¥³¥ó¥Ñ¥¤¥ë»þ¤ÎÀßÄê¤ÎÊѹ¹

    + + +
      +
    • Apache ¤Ï ¥Ó¥ë¥É½èÍý¤ÎÀßÄê + ¤Ë autoconf ¤È libtool ¤ò»È¤¦¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + ¤³¤Î¥·¥¹¥Æ¥à¤Ï Apache 1.3 ¤Î APACI ¥·¥¹¥Æ¥à¤È»÷¤Æ¤¤¤Þ¤¹¤¬¡¢ + ¤Þ¤Ã¤¿¤¯Æ±¤¸¤È¤¤¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
      • + +
    • Ä̾ï¤Î¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤«¤É¤¦¤«¤òÁªÂò¤Ç¤­¤ë¥â¥¸¥å¡¼¥ë·²¤Ë²Ã¤¨¤Æ¡¢ + Apache 2.0 ¤Ï + ¥ê¥¯¥¨¥¹¥È½èÍý¤Î¼ç¤ÊÉôʬ¤ò ¥Þ¥ë¥Á¥×¥í¥»¥Ã¥·¥ó¥° + ¥â¥¸¥å¡¼¥ë (MPM) ¤Ë°ÜÆ°¤·¤Þ¤·¤¿¡£
      • +
    +
    top
    +
    +

    ¼Â¹Ô»þ¤ÎÀßÄê¤ÎÊѹ¹

    + + +
      +
    • Apache 1.3 ¤Î»þ¤Ë¥³¥¢¥µ¡¼¥Ð¤Ë¤¢¤Ã¤¿Â¿¤¯¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + MPM ¤Ë°ÜÆ°¤·¤Þ¤·¤¿¡£¥µ¡¼¥Ð¤Ë Apache 1.3 ¤È¤Ç¤­¤ë¤À¤±Æ±¤¸¿¶¤ëÉñ¤¤¤ò + ¤µ¤»¤¿¤¤¾ì¹ç¤Ï¡¢prefork MPM ¤ò + Áª¤ó¤Ç¤¯¤À¤µ¤¤¡£Â¾¤Î MPM ¤Ï¥×¥í¥»¥¹¤ÎºîÀ®¤ä¥ê¥¯¥¨¥¹¥È¤Î½èÍý¤Î + À©¸æ¤Ë°Û¤Ê¤Ã¤¿¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¤¤Þ¤¹¡£
      • + +
    • Proxy ¥â¥¸¥å¡¼¥ë ¤Ï + HTTP/1.1 ¤ËÂбþ¤¹¤ë¤¿¤á¤ËºÆ¹½À®¤µ¤ì¤Þ¤·¤¿¡£½ÅÍפÊÊѹ¹ÅÀ¤È¤·¤Æ¤Ï¡¢ + ¥×¥í¥­¥·¤Î¥¢¥¯¥»¥¹À©¸æ¤¬ <Directory proxy:> ¥Ö¥í¥Ã¥¯¤Î + Âå¤ï¤ê¤Ë <Proxy> + ¥Ö¥í¥Ã¥¯¤ËÃÖ¤«¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã¤¿¡¢¤È¤¤¤¦¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
      • + +
    • ¥â¥¸¥å¡¼¥ë¤ÎÃæ¤Ë¤Ï¡¢PATH_INFO (ËÜÅö¤Î¥Õ¥¡¥¤¥ë̾¤Î¸å¤Ë³¤¯ + ¥Ñ¥¹¾ðÊó) ¤Î°·¤¤¤¬ÊѤï¤Ã¤¿¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£°ÊÁ°¤Ï¥Ï¥ó¥É¥é¤È¤·¤Æ + ¼ÂÁõ¤µ¤ì¤Æ¤¤¤¿¤â¤Î¤¬¥Õ¥£¥ë¥¿¤È¤·¤Æ¼ÂÁõ¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã¤¿¤â¤Î¤Ï + PATH_INFO ¤Î¤¢¤ë¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤Þ¤»¤ó¡£INCLUDES ¤ä + PHP ¤Ê¤É¤Î¥Õ¥£¥ë¥¿¤Ï + ¥³¥¢¥Ï¥ó¥É¥é¤Î¾å¤Ë¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¤Î¤Ç¡¢PATH_INFO + ÉÕ¤­¤Î¥ê¥¯¥¨¥¹¥È¤òµñÈݤ·¤Þ¤¹¡£ + AcceptPathInfo + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¥³¥¢¥Ï¥ó¥É¥é¤¬ PATH_INFO + ÉÕ¤­¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤ë¤è¤¦¤Ë¤Ç¤­¡¢¤½¤ì¤Ë¤è¤Ã¤Æ SSI Åù¤Ç + PATH_INFO ¤ò»È¤¦µ¡Ç½¤òÉü³è¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
      • + +
    • CacheNegotiatedDocs + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï on ¤â¤·¤¯¤Ï off ¤È¤¤¤¦°ú¿ô¤ò + ¼è¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£´û¤Ë¸ºß¤·¤Æ¤¤¤ë + CacheNegotiatedDocs ¤Ï + CacheNegotiatedDocs on + ¤ËÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£
      • + +
    • + ErrorDocument + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Æ¥­¥¹¥È¥á¥Ã¥»¡¼¥¸¤ò + ¼¨¤¹¤¿¤á¤Ë°ú¿ô¤ÎºÇ½é¤Ë»È¤ï¤ì¤Æ¤¤¤¿°úÍÑÉä¤ò»È¤ï¤Ê¤¤¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + Âå¤ï¤ê¤Ë¡¢¥á¥Ã¥»¡¼¥¸¤òÆó½Å°úÍÑÉä¤Ç°Ï¤à¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£ + Î㤨¤Ð¡¢´û¸¤Î + +

      + ErrorDocument 403 "Some Message +

      + ¤Ï + +

      + ErrorDocument 403 "Some Message" +

      + + ¤ËÃÖ¤­´¹¤¨¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ÆóÈÖÌܤΰú¿ô¤Ï¡¢Í­¸ú¤Ê URL ¤ä¥Ñ¥¹Ì¾¤Ç¤Ê¤¤¸Â¤ê + ¥Æ¥­¥¹¥È¥á¥Ã¥»¡¼¥¸¤È¤·¤Æ°·¤ï¤ì¤Þ¤¹¡£ +
      • + +
    • AccessConfig ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È + ResourceConfig ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïºï½ü¤µ¤ì¤Þ¤·¤¿¡£ + ¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏƱÅù¤Îµ¡Ç½¤ò»ý¤Ä + Include ¤Ç + ÃÖ¤­´¹¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ÀßÄê¥Õ¥¡¥¤¥ë¤Ë¼è¤ê¹þ¤àÂå¤ï¤ê¤Ë¡¢ + ¾å¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤò»È¤Ã¤Æ¤¤¤¿¾ì¹ç¤Ï¡¢ + httpd.conf ¤Ë Include conf/access.conf ¤È + Include conf/srm.conf ¤òÄɲ乤ëɬÍפ¬¤¢¤ë¤Ç¤·¤ç¤¦¡£ + °ÊÁ°¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ë½çÈ֤Τ褦¤Ë Apache ¤¬ÀßÄê¥Õ¥¡¥¤¥ë¤ò + Æɤ߹þ¤à¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢httpd.conf ¤ÎºÇ¸å¤Ë + srm.conf¡¢access.conf ¤Î½ç¤Ë¤½¤ì¤¾¤ì + Include + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¤¤Æ¤¯¤À¤µ¤¤¡£
      • + +
    • BindAddress ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È Port + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïºï½ü¤µ¤ì¤Þ¤·¤¿¡£Æ±Åù¤Îµ¡Ç½¤Ï¤è¤ê½ÀÆð¤Ê + Listen + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤êÄ󶡤µ¤ì¤Æ¤¤¤Þ¤¹¡£
      • + +
    • Port ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache-1.3 ¤Ë¤Ï¼«¸Ê»²¾È URL ¤Ç + »È¤ï¤ì¤ë¥Ý¡¼¥ÈÈÖ¹æ¤òÀßÄꤹ¤ë¡¢¤È¤¤¤¦»ÈÍÑË¡¤â¤¢¤ê¤Þ¤·¤¿¡£ + ¤³¤ì¤Ï Apache-2.0 ¤Ç¤Ï¿·¤·¤¤ + ServerName + ¹½Ê¸¤Ë¤è¤Ã¤Æ¹Ô¤Ê¤¤¤Þ¤¹¡£°ì¤Ä¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç¥Û¥¹¥È̾¤È + ¼«¸Ê»²¾È URL ¤ÎξÊý¤òÀßÄê¤Ç¤­¤ë¤è¤¦¤Ë¹½Ê¸¤¬Êѹ¹¤µ¤ì¤Þ¤·¤¿¡£
      • + +
    • ServerName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïºï½ü¤µ¤ì¤Þ¤·¤¿¡£ + ¥ê¥¯¥¨¥¹¥È¤ò°·¤¦ÊýË¡¤Ï MPM ¤ÎÁªÂò¤Ë¤è¤ê·èÄꤵ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£ + ¸½»þÅÀ¤Ç¤Ï inetd ¤«¤éµ¯Æ°¤µ¤ì¤ë¤è¤¦¤ËÀ߷פµ¤ì¤¿ MPM ¤Ï¤¢¤ê¤Þ¤»¤ó¡£
      • + +
    • AgentLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢ + RefererLog ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡¢ + RefererIgnore ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÄ󶡤·¤Æ¤¤¤¿ + mod_log_agent ¤È mod_log_referer + ¥â¥¸¥å¡¼¥ë¤Ïºï½ü¤µ¤ì¤Þ¤·¤¿¡£ + Agent ¥í¥°¤È refere ¥í¥°¤Ï mod_log_config ¤Î + CustomLog + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¼Â¸½²Äǽ¤Ç¤¹¡£
      • + +
    • AddModule ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È ClearModuleList + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïºï½ü¤µ¤ì¤Þ¤·¤¿¡£¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢ + ¥â¥¸¥å¡¼¥ë¤¬Àµ¤·¤¤½çÈ֤ǸƤФì¤ë¤è¤¦¤Ë¤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Æ¤¤¤Þ¤·¤¿¡£ + Apache 2.0 ¤Î¿· API ¤Ï¥â¥¸¥å¡¼¥ë¤¬ÌÀ¼¨Åª¤Ë½çÈÖ¤ò»ØÄê¤Ç¤­¤ë¤è¤¦¤Ë + ¤Ê¤Ã¤Æ¤ª¤ê¡¢¤³¤ì¤é¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏɬÍפʤ¯¤Ê¤ê¤Þ¤·¤¿¡£
      • + +
    • FancyIndexing ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ïºï½ü¤µ¤ì¤Þ¤·¤¿¡£ + Ʊ¤¸µ¡Ç½¤Ï IndexOptions + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î FancyIndexing ¥ª¥×¥·¥ç¥ó¤Ç + ¼Â¸½¤Ç¤­¤Þ¤¹¡£
      • + +
    • mod_negotiation ¤Ë¤è¤ë MultiViews + ¥³¥ó¥Æ¥ó¥È¥Í¥´¥·¥¨¡¼¥·¥ç¥óµ»½Ñ¤Ï¡¢ + ¥Ç¥Õ¥©¥ë¥È¤Î¥Õ¥¡¥¤¥ë¥Þ¥Ã¥Á¥ó¥°¤¬¤è¤ê¸·Ì©¤Ê¤â¤Î¤ËÊѹ¹¤µ¤ì¤Þ¤·¤¿¡£ + ¥Í¥´¥·¥¨¡¼¥È²Äǽ¤Ê¥Õ¥¡¥¤¥ë¤Î¾ì¹ç¤Ë¤Î¤ßÁªÂò¤µ¤ì¤Þ¤¹¡£ + °ÊÁ°¤ÎµóÆ°¤Ï¡¢MultiviewsMatch + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»ÈÍѤ¹¤ë¤³¤È¤ÇÉü³è¤Ç¤­¤Þ¤¹¡£
      • + +
    • (¥Ð¡¼¥¸¥ç¥ó 2.0.51 ¤«¤é) +

      ErrorHeader ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÉÔŬÀÚ¤Ê̾Á° + ¤À¤Ã¤¿¤¿¤á¤ËÇѻߤµ¤ì¡¢¤½¤Îµ¡Ç½¤Ï Header ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ËÅý¹ç¤µ¤ì¤Þ¤·¤¿¡£ + ˾¤ß¤ÎÆ°ºî¤òÆÀ¤ë¤¿¤á¤Ë¤Ï ErrorHeader ¤ÎÂå¤ï¤ê¤Ë

      + +

      + Header always set foo bar +

      + +

      ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£

      • +
    +
    top
    +
    +

    ¤½¤Î¾¤ÎÊѹ¹

    + + +
      +
    • Apache 1.3 ¤Ç¼Â¸³Åª¤Ê¥â¥¸¥å¡¼¥ë¤À¤Ã¤¿ + mod_auth_digest ¤Ï + ɸ½à¥â¥¸¥å¡¼¥ë¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
      • + +
    • Apache 1.3 ¤Ç¼Â¸³Åª¤Ê¥â¥¸¥å¡¼¥ë¤À¤Ã¤¿ mod_mmap_static ¤Ï + mod_file_cache ¤ÇÃÖ¤­´¹¤¨¤é¤ì¤Þ¤·¤¿¡£
      • + +
    • Apache ¤ÎÇÛÉÛ¤ÏÆÈΩ¤·¤¿ src ¥Ç¥£¥ì¥¯¥È¥ê¤¬ + ¤Ê¤¯¤Ê¤ë¤è¤¦¤Ë¡¢´°Á´¤ËºÆ¹½À®¤µ¤ì¤Þ¤·¤¿¡£¤½¤ÎÂå¤ï¤ê¤Ë¡¢ + ¥½¡¼¥¹¤Ï¼ç¥Ç¥£¥ì¥¯¥È¥ê¤ËÏÀÍýŪ¤ËÇÛÃÖ¤µ¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¡¢ + ¥³¥ó¥Ñ¥¤¥ë¤µ¤ì¤¿¥µ¡¼¥Ð¤Î¥¤¥ó¥¹¥È¡¼¥ë¤ÏÊ̥ǥ£¥ì¥¯¥È¥ê¤Ø + ¹Ô¤Ê¤¦¤è¤¦¤Ë¤Ê¤ê¤Þ¤·¤¿¡£
      • +
    +
    top
    +
    +

    ¥µ¡¼¥É¥Ñ¡¼¥Æ¥£¥â¥¸¥å¡¼¥ë

    + + +

    Apache 2.0 ¤Î¥µ¡¼¥Ð API ¤Ë¤Ï¿¤¯¤ÎÊѹ¹¤¬²Ã¤¨¤é¤ì¤Þ¤·¤¿¡£ + Apache 1.3 ÍѤδû¸¤Î¥â¥¸¥å¡¼¥ë¤Ï Apache 2.0 ¤Ç¤Ï½¤Àµ¤Ê¤·¤Ç¤Ï + Æ°¤­¤Þ¤»¤ó¡£¾ÜºÙ¤Ï ³«È¯¼Ô¸þ¤±Ê¸½ñ ¤Ë¤¢¤ê¤Þ¤¹¡£

    +
    +
    +

    Available Languages:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/upgrading.html.ko.euc-kr b/docs/manual/upgrading.html.ko.euc-kr new file mode 100644 index 00000000..315c5c2b --- /dev/null +++ b/docs/manual/upgrading.html.ko.euc-kr @@ -0,0 +1,204 @@ + + + +1.3¿¡¼­ 2.0À¸·Î ¾÷±×·¹À̵å - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    1.3¿¡¼­ 2.0À¸·Î ¾÷±×·¹À̵å

    +
    +

    °¡´ÉÇÑ ¾ð¾î:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

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

    ¿ì¸®´Â ±âÁ¸ ¾ÆÆÄÄ¡ »ç¿ëÀÚ°¡ ¾÷±×·¹À̵åÇÏ´Â °ÍÀ» µ½±âÀ§ÇØ + Áß¿äÇÑ Á¤º¸¸¦ ¾Ë·ÁÁÖ´Â ¹®¼­¸¦ Á¦°øÇÑ´Ù. ÀÌ ¹®¼­´Â °£´ÜÇÑ + ¿ä¾àÀ̹ǷÎ, »õ·Î¿î ±â´É + ¹®¼­³ª src/CHANGES ÆÄÀÏ¿¡¼­ Á¤º¸¸¦ ã¾ÆºÁ¾ß + ÇÑ´Ù.

    +
    + +
    top
    +
    +

    ÄÄÆÄÀϽà ±¸¼º º¯È­

    + + +
      +
    • ¾ÆÆÄÄ¡´Â ÀÌÁ¦ ¾ÆÆÄÄ¡ ÄÄÆÄÀÏ°ú ¼³Ä¡¸¦ À§ÇØ + autoconf¿Í libtool ½Ã½ºÅÛÀ» + »ç¿ëÇÑ´Ù. ÀÌ ½Ã½ºÅÛÀÇ »ç¿ë¹ýÀº Apache 1.3ÀÇ APACI ½Ã½ºÅÛ°ú + °°Áö´Â ¾ÊÁö¸¸ ºñ½ÁÇÏ´Ù.
      • + +
    • ÄÄÆÄÀÏ ¿©ºÎ¸¦ ¼±ÅÃÇÒ ¸ðµâ¿Ü¿¡ Apache 2.0Àº ¿äûÀ» + ó¸®ÇÏ´Â ÁÖ¿ä ºÎºÐÀ» ´ÙÁßó¸® ¸ðµâ + (Multi-Processing Modules) (MPM)·Î ¿Å°å´Ù.
      • +
    +
    top
    +
    +

    ½ÇÇà½Ã ¼³Á¤ º¯È­

    + + +
      +
    • Apache 1.3¿¡¼­ ¼­¹ö Çٽɿ¡ ÀÖ¾ú´ø ¸¹Àº Áö½Ã¾îµéÀÌ + ÀÌÁ¦´Â MPM¿¡ ÀÖ´Ù. ¼­¹ö°¡ Apache 1.3°ú ÃÖ´ëÇÑ ºñ½ÁÇÏ°Ô + µ¿ÀÛÇÏ±æ ¹Ù¶õ´Ù¸é prefork MPMÀ» ¼±ÅÃÇØ¾ß + ÇÑ´Ù. ´Ù¸¥ MPMÀº ´Ù¸¥ Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ÇÁ·Î¼¼½º »ý¼º°ú + ¿äûÀÇ Ã³¸®¸¦ Á¶ÀýÇÑ´Ù.
      • + +
    • proxy ¸ðµâÀº HTTP/1.1¿¡ + ¸ÂÃß¾î ¼öÁ¤µÇ¾ú´Ù. Áß¿äÇÑ º¯È­Áß Çϳª´Â ÀÌÁ¦ ÇÁ·Ï½Ã Á¢±ÙÁ¦¾î°¡ + <Directory proxy:> ºí·ÏÀÌ ¾Æ´Ï¶ó + <Proxy> + ºí·Ï¿¡ À§Ä¡ÇÏ´Â Á¡ÀÌ´Ù.
      • + +
    • ¸î¸î ¸ðµâ¿¡¼­ PATH_INFO (ÁøÂ¥ °æ·Î¸í + µÚ¿¡ ³ª¿À´Â °æ·Î Á¤º¸) ó¸® ¹æ½ÄÀÌ º¯°æµÇ¾ú´Ù. Àü¿¡ + Çڵ鷯¿´Áö¸¸ ÀÌÁ¦ ÇÊÅÍ·Î ±¸ÇöµÇ´Â ¸ðµâÀº ´õ ÀÌ»ó + PATH_INFO°¡ ÀÖ´Â ¿äûÀ» ¹Þ¾ÆµéÀÌÁö ¸øÇÑ´Ù. + INCLUDES³ª PHP¿Í °°Àº ÇÊÅÍ´Â + core Çڵ鷯 À§¿¡ ±¸ÇöµÇ±â¶§¹®¿¡ PATH_INFO°¡ + ÀÖ´Â ¿äûÀ» °ÅºÎÇÑ´Ù. core Çڵ鷯°¡ PATH_INFO°¡ + ÀÖ´Â ¿äûÀ» ¹Þ¾ÆµéÀÌ°í server-side include¿¡¼­ + PATH_INFO¸¦ »ç¿ëÇÏ°Ô ÇÏ·Á¸é, AcceptPathInfo Áö½Ã¾î¸¦ »ç¿ëÇØ¾ß + ÇÑ´Ù.
      • + +
    • CacheNegotiatedDocs + Áö½Ã¾î´Â ÀÌÁ¦ ¾Æ±Ô¸ÕÆ®·Î on°ú off¸¦ + ¹Þ´Â´Ù. ±âÁ¸ÀÇ CacheNegotiatedDocs´Â + CacheNegotiatedDocs onÀ¸·Î ¼öÁ¤ÇØ¾ß ÇÑ´Ù.
      • + +
    • + ErrorDocument Áö½Ã¾î´Â + ´õÀÌ»ó ¸Þ¼¼Áö¸¦ ³ªÅ¸³»´Â ¾Æ±Ô¸ÕÆ® ¾Õ¿¡ µû¿ÈÇ¥¸¦ »ç¿ëÇÏÁö + ¾Ê´Â´Ù. ´ë½Å ½Öµû¿ÈÇ¥·Î ¸Þ¼¼Áö¸¦ ¹­¾î¾ß ÇÑ´Ù. ¿¹¸¦ µé¾î °ú°Å + +

      + ErrorDocument 403 "Some Message +

      + ´Â ´ÙÀ½°ú °°ÀÌ ¼öÁ¤ÇØ¾ß ÇÑ´Ù. + +

      + ErrorDocument 403 "Some Message" +

      + µÎ¹ø° ¾Æ±Ô¸ÕÆ®°¡ À¯È¿ÇÑ URLÀ̳ª °æ·Î¸íÀÌ ¾Æ´Ï¶ó¸é ¸Þ¼¼Áö·Î + °£ÁÖÇÑ´Ù. +
      • + +
    • AccessConfig¿Í ResourceConfig + Áö½Ã¾î´Â »ç¶óÁ³´Ù. ±âÁ¸¿¡ »ç¿ëÇÏ´ø Áö½Ã¾î´Â °°Àº ±â´ÉÀ» + ÇÏ´Â Include Áö½Ã¾î·Î + ´ëüÇÒ ¼ö ÀÖ´Ù. °ú°Å¿¡ ¼³Á¤ÆÄÀÏ¿¡¼­ ÀÌ Áö½Ã¾îµéÀ» »ç¿ëÇÏÁö¾Ê°í + ÀÌ Áö½Ã¾îµéÀÇ ±âº»°ªÀ» »ç¿ëÇß´Ù¸é, http.conf¿¡ + Include conf/access.conf¿Í Include + conf/srm.conf¸¦ Ãß°¡ÇÒ ÇÊ¿ä°¡ ÀÖ´Ù. ¾ÆÆÄÄ¡°¡ ÀÌÀü + Áö½Ã¾î¿Í °°Àº ¼ø¼­·Î ¼³Á¤ÆÄÀÏÀ» ÀаÔÇÏ·Á¸é + Include Áö½Ã¾î¸¦ + httpd.conf ³¡¿¡ µÎ°í, srm.confÀÌ + access.conf ¾Õ¿¡ ³ª¿Í¾ß ÇÑ´Ù.
      • + +
    • BindAddress¿Í Port Áö½Ã¾î´Â + »ç¶óÁ³´Ù. ´õ À¯¿¬ÇÑ Listen + Áö½Ã¾î°¡ °°Àº ±â´ÉÀ» ÇÑ´Ù.
      • + +
    • Apache-1.3¿¡¼­ Port´Â ÀÚ±âÂüÁ¶ + URLÀÇ Æ÷Æ® ¹øÈ£¸¦ ¼³Á¤ÇÏ´Â Àϵµ Çß´Ù. Apache-2.0¿¡¼­ ÀÌ + ±â´ÉÀº »õ·Î¿î ServerNameÀ¸·Î + ÇÑ´Ù. ÇÑ Áö½Ã¾î¿¡ È£½ºÆ®¸í°ú ÀÚ±âÂüÁ¶ URLÀ» À§ÇÑ + Æ÷Æ® ¹øÈ£¸¦ °°ÀÌ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù.
      • + +
    • ServerType Áö½Ã¾î´Â »ç¶óÁ³´Ù. ¿äûÀ» + ¼­ºñ½ºÇÏ´Â ¹æ¹ýÀº ÀÌÁ¦ MPM ¼±Åÿ¡ ´Þ·È´Ù. ÇöÀç inetd¿¡¼­ + ½ÃÀÛÇϵµ·Ï ¼³°èµÈ MPMÀº ¾ø´Ù.
      • + +
    • AgentLog, RefererLog, + RefererIgnore Áö½Ã¾î¸¦ Á¦°øÇÑ + mod_log_agent¿Í mod_log_referer + ¸ðµâÀÌ ¾ø¾îÁ³´Ù. agent ·Î±×¿Í referer ·Î±×´Â + mod_log_configÀÇ CustomLog Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© °è¼Ó Á¦°øµÈ´Ù.
      • + +
    • AddModule°ú ClearModuleList + Áö½Ã¾î´Â »ç¶óÁ³´Ù. ÀÌ Áö½Ã¾îµéÀº ¸ðµâÀ» ¿Ã¹Ù¸¥ ¼ø¼­·Î + È°¼ºÈ­ÇÏ·Á°í »ç¿ëÇß´Ù. »õ·Î¿î Apache 2.0 API´Â ¸ðµâÀÌ + È°¼ºÈ­µÇ´Â ¼ø¼­¸¦ ¸í½ÃÀûÀ¸·Î ÁöÁ¤ÇÒ ¼ö À־, ÀÌ Áö½Ã¾îµéÀÌ + ÇÊ¿ä¾ø°Ô µÇ¾ú´Ù.
      • + +
    • FancyIndexing Áö½Ã¾î°¡ ¾ø¾îÁ³´Ù. + IndexOptions + Áö½Ã¾îÀÇ FancyIndexing ¿É¼ÇÀÌ °°Àº ±â´ÉÀ» ÇÑ´Ù.
      • + +
    • mod_negotiationÀÇ MultiViews ³»¿ëÇù»óÀÌ + ´õ ¾ö°ÝÇÏ°Ô ±âº»ÆÄÀÏÀ» ã´Â´Ù. ³»¿ëÇù»óÀº Çù»ó°¡´ÉÇÑ + ÆÄÀÏ Áß¿¡¼­¸¸ ¼±ÅÃÇÑ´Ù. MultiviewsMatch Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© ÀÌÀü°ú °°ÀÌ µ¿ÀÛÇÏ°Ô ÇÒ ¼ö ÀÖ´Ù.
      • + +
    • (2.0.51 ¹öÀü ÀÌÈÄ) +

      ErrorHeader Áö½Ã¾î´Â À߸øµÈ ¸íĪÀ¸·Î, + ÀÌ Áö½Ã¾î°¡ ´ã´çÇÑ ±â´ÉÀº Header Áö½Ã¾î·Îµµ °¡´ÉÇÏ´Ù. + ¿øÇÏ´Â ±â´ÉÀ» À§ÇØ,

      + +

      + Header always set ¾î¼°í Àú¼°í +

      + +

      ¿Í °°ÀÌ ¼³Á¤ÇÑ´Ù.

      • +
    +
    top
    +
    +

    ±âŸ º¯È­

    + + +
      +
    • Apache 1.3¿¡¼­ ½ÇÇèÀûÀÌ¿´´ø mod_auth_digest + ¸ðµâÀÌ ÀÌÁ¦ Ç¥ÁØ ¸ðµâÀÌ µÇ¾ú´Ù.
      • + +
    • Apache 1.3¿¡¼­ ½ÇÇèÀûÀÌ¿´´ø mod_mmap_static + ¸ðµâÀÌ mod_file_cache·Î ´ëüµÇ¾ú´Ù.
      • + +
    • ¹èÆ÷º»ÀÌ ¿ÏÀüÈ÷ »õ·Î ±¸¼ºµÇ¾î ´õÀÌ»ó µ¶¸³µÈ src + µð·ºÅ丮°¡ ¾ø´Ù. ´ë½Å ¼Ò½º´Â ÁÖ ¹èÆ÷º» µð·ºÅ丮 ¾Æ·¡ ³í¸®ÀûÀ¸·Î + ±¸¼ºµÇÀÖ°í, ÄÄÆÄÀÏÇÑ ¼­¹ö´Â ´Ù¸¥ µð·ºÅ丮·Î ¼³Ä¡µÈ´Ù.
      • +
    +
    top
    +
    +

    Á¦»ïÀÚ°¡ ¸¸µç ¸ðµâ

    + + +

    Apache 2.0¿¡¼­ ¼­¹ö API°¡ ¸¹ÀÌ º¯°æµÇ¾ú´Ù. Apache 1.3 API¿¡ + ¸ÂÃçÁø ±âÁ¸ ¸ðµâÀ» ¼öÁ¤¾øÀÌ Apache 2.0¿¡¼­ »ç¿ëÇÒ ¼ö + ¾ø´Ù. ÀÚ¼¼ÇÑ Á¤º¸´Â °³¹ßÀÚ + ¹®¼­¸¦ Âü°íÇ϶ó.

    +
    +
    +

    °¡´ÉÇÑ ¾ð¾î:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/upgrading.html.pt-br b/docs/manual/upgrading.html.pt-br new file mode 100644 index 00000000..6c718049 --- /dev/null +++ b/docs/manual/upgrading.html.pt-br @@ -0,0 +1,225 @@ + + + +Atualizando da versão 1.3 para 2.0 - Servidor HTTP Apache + + + + +
    +

    Módulos | Diretrizes | FAQ | Glossário | Mapa do site

    +

    Servidor HTTP Apache Versão 2.2

    +
    +
    <-
    +

    Atualizando da versão 1.3 para 2.0

    +
    +

    Línguas Disponíveis:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    +
    Esta tradução pode estar desatualizada. + Verifique a versão em Inglês para mudanças recentes.
    + +

    Com a finalidade de ajudar as pessoas na atualização do servidor, + nós mantemos um documento que descreve informações críticas para + os usuários já existentes do Apache. Essas informações tem o + intuito de serem breves notas e você deverá encontrar mais + informações no documento Novas Funcionalidades, ou no + arquivo src/CHANGES.

    +
    + +
    top
    +
    +

    Mudanças na Configuração em tempo de Compilação

    + + +
      +
    • O Apache agora usa o sistema autoconf + e libtool para + configurar o processo de construção. + A utilização desse sistema é similar, mas não o + mesmo, a usar o sistema APACI do Apache 1.3
      • + +
    • Além da seleção habitual de módulos que você + pode escolher para compilar, o Apache 2.0 mudou a parte + principal de processamentos de pedidos para os Módulos Multi-Processamento (MPMs).
      • +
    +
    top
    +
    +

    Mudanças na Configuração em tempo de Execução

    + + +
      +
    • Muitas diretrizes que estavam no núcleo do servidor + no Apache 1.3 estão agora nos MPMs. Se você desejar que + o funcionamento do servidor seja o mais similar possível ao + do Apache 1.3, você deve selecionar o MPM prefork. + Os outros MPMs terão diretrizes diferentes para controlar + a criação de processos e o processamento de pedidos.
      • + +
    • O módulo proxy foi reconstruído + para o padrão HTTP/1.1. Ao longo das mudanças importantes, + o controle de acesso ao proxy agora fica dentro de um bloco + <Proxy>, + ao invés de um bloco <Directory proxy:>.
      • + +
    • A operação com PATH_INFO (informação de + caminho procedente depois do nome do arquivo verdadeiro) mudou + para alguns módulos. Módulos que eram previamente implementados + como manipuladores mas agora são implementados como filtros + não podem mais aceitar pedidos com PATH_INFO. + Filtros como INCLUDES + ou PHP são implementados + no topo dos manipuladores principais, rejeitando pedidos + com PATH_INFO. Você pode usar a diretriz + AcceptPathInfo + para forçar o manipulador principal a aceitar pedidos + com PATH_INFO e assim restaurar a habilidade + de usá-lo em inclusões por parte do servidor (SSI).
      • + +
    • A diretriz CacheNegotiatedDocs agora aceita + o argumento on ou off. Instâncias + existentes de CacheNegotiatedDocs deverão + ser substituídas por CacheNegotiatedDocs on.
      • + +
    • + A diretriz ErrorDocument + não usa mais aspas no começo do argumento para indicar + mensagens de texto. Ao invés disso, você deve colocar + a mensagem inteira entre aspas. Por exemplo, instâncias + existentes de + +

      + ErrorDocument 403 "Alguma mensagem +

      + devem ser substituídas por + +

      + ErrorDocument 403 "Alguma mensagem" +

      + + Contanto que o segundo argumento não seja uma + URL válida ou um caminho de arquivo, irá ser + tratado como uma mensagem de texto. +
      • + +
    • As diretrizes AccessConfig e + ResourceConfig não existem mais. + Instâncias existentes dessas diretrizes podem ser substituídas + com a diretriz Include + que possui uma funcionalidade equivalente. Se você estava + fazendo uso dos valores padrões dessas diretrizes sem incluí-las + nos arquivos de configuração, você provavelmente terá + que adicionar Include conf/access.conf e + Include conf/srm.conf ao seu httpd.conf. + Com o fim de assegurar que o Apache leia os arquivos de + configuração na mesma ordem que as diretrizes velhas usavam, + a diretriz Include deve ser colocada + no final do httpd.conf, com uma entrada para + srm.conf antes de access.conf.
      • + +
    • As diretrizes BindAddress and Port + não existem mais. Uma funcionalidade equivalente é fornecida com + uma diretriz mais flexível Listen.
      • + +
    • Outro uso da diretriz Port no Apache-1.3 + era ajustar o número da porta usada em URLs auto-referenciáveis. + O equivalente no Apache-2.0 é a nova sintaxe ServerName: ela foi modificada para permitir que + sejam especificados ambos "hostname" e o número da porta + para URLs auto-referenciáveis em uma só diretriz.
      • + +
    • A diretriz ServerType não existe mais. + O método usado para atender pedidos é determinado pela + seleção de MPM. Atualmente não existe nenhuma MPM projetada + para ser executada pelo inetd.
      • + +
    • Os módulos mod_log_agent e mod_log_referer + que forneciam as diretrizes AgentLog, + RefererLog e RefererIgnore foram removidas. + Registros de agentes e referências ainda estão disponíveis + usando a diretriz CustomLog do + mod_log_config.
      • + +
    • As diretrizes AddModule e + ClearModuleList não existem mais. + Essas diretrizes eram usadas para garantir que módulos + pudessem ser habilitados na ordem correta. A nova API do + Apache 2.0 permite que os módulos especifiquem explicitamente + a sua ordem, eliminando a necessidade dessas diretrizes.
      • + +
    • A diretriz FancyIndexing foi removida. + A mesma funcionalidade está disponível através da + opção FancyIndexing da diretriz IndexOptions.
      • + +
    • A técnica de negociação de conteúdo (content-negotiation) + MultiViews fornecida pelo mod_negotiation + se tornou mais rigorosa em sua combinação de arquivo + padrão. Ela irá selecionar apenas arquivos negociáveis + (negotiable). O comportamento antigo pode ser restaurado usando a + diretriz MultiviewsMatch.
      • + +
    • (desde a versão 2.0.51) +

      A funcionalidade da diretriz ErrorHeader + foi colocada em conjunto com a diretriz Header, já que era um + uso de um nome impróprio. Utilize

      + +

      + Header always set foo bar +

      + +

      para obter o comportamento desejado.

      • +
    +
    top
    +
    +

    Mudanças Gerais

    + + +
      +
    • O módulo mod_auth_digest, que era + experimental no Apache 1.3, é agora um módulo padrão.
      • + +
    • O módulo mod_mmap_static, que era experimental no + Apache 1.3, foi substituído com mod_file_cache.
      • + +
    • A distribuição foi completamente reorganizada para + não conter mais um diretório src independente. + Em seu lugar, os fontes são organizados + logicamente no diretório principal da distribuição e + a instalação do servidor compilado deve ser direcionada + à um diretório separado.
      • +
    +
    top
    +
    +

    Módulos de Terceiros

    + + +

    Mudanças extensivas foram feitas na API do servidor + no Apache 2.0. Módulos existentes projetados para a API + do Apache 1.3, não funcionarão no Apache + 2.0 sem modificações. Detalhes serão fornecidos na + documentação do desenvolvedor.

    +
    +
    +

    Línguas Disponíveis:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/upgrading.html.ru.koi8-r b/docs/manual/upgrading.html.ru.koi8-r new file mode 100644 index 00000000..2421fd38 --- /dev/null +++ b/docs/manual/upgrading.html.ru.koi8-r @@ -0,0 +1,202 @@ + + + +ðÅÒÅÈÏÄ ÏÔ ×ÅÒÓÉÉ 1.3 Ë ×ÅÒÓÉÉ 2.0 - HTTP ÓÅÒ×ÅÒ Apache + + + + +
    +

    íÏÄÕÌÉ | äÉÒÅËÔÉ×Ù | FAQ | çÌÏÓÓÁÒÉÊ | ëÁÒÔÁ ÓÁÊÔÁ

    +

    HTTP ÓÅÒ×ÅÒ Apache ×ÅÒÓÉÉ 2.2

    +
    +
    <-
    +

    ðÅÒÅÈÏÄ ÏÔ ×ÅÒÓÉÉ 1.3 Ë ×ÅÒÓÉÉ 2.0

    +
    +

    äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    +
    üÔÏÔ ÐÅÒÅ×ÏÄ ÍÏÖÅÔ ÂÙÔØ ÕÓÔÁÒÅ×ÛÉÍ. óÍÏÔÒÉÔÅ + ÁÎÇÌÉÊÓËÕÀ ×ÅÒÓÉÀ ÄÌÑ ÏÚÎÁËÏÍÌÅÎÉÑ ÓÏ ×ÓÅÍÉ ÐÏÓÌÅÄÎÉÍÉ ÉÚÍÅÎÅÎÉÑÍÉ + × ÄÏËÕÍÅÎÔÅ.
    + +

    üÔÏÔ ÄÏËÕÍÅÎÔ ÎÅÏÂÈÏÄÉÍ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÏÍÏÞØ ÐÏÌØÚÏ×ÁÔÅÌÑÍ + ÐÅÒÅÊÔÉ Ë ÉÓÐÏÌØÚÏ×ÁÎÉÀ ÓÅÒ×ÅÒÁ ×ÅÒÓÉÉ 2.0. úÄÅÓØ ×Ù ÎÁÊÄÅÔÅ ÌÉÛØ + ËÒÁÔËÉÅ ÚÁÍÅÞÁÎÉÑ; ÂÏÌÅÅ ÐÏÄÒÏÂÎÕÀ ÉÎÆÏÒÍÁÃÉÀ Ï ÎÏ×Ï××ÅÄÅÎÉÑÈ ÍÏÖÎÏ + ÎÁÊÔÉ ÌÉÂÏ × ÄÏËÕÍÅÎÔÅ îÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ, ÌÉÂÏ × ÆÁÊÌÅ src/CHANGES.

    +
    + +
    top
    +
    +

    éÚÍÅÎÅÎÉÑ × ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÉ ÓÂÏÒËÉ ÓÅÒ×ÅÒÁ

    + + +
      +
    • Apache ÔÅÐÅÒØ ÉÓÐÏÌØÚÕÅÔ ÓÉÓÔÅÍÕ autoconf É + libtool ÄÌÑ ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÑ ÐÒÏÃÅÓÓÁ ÓÂÏÒËÉ. + éÓÐÏÌØÚÏ×ÁÎÉÅ ÜÔÏÊ ÓÉÓÔÅÍÙ ÐÏÈÏÖÅ ÎÁ ÉÓÐÏÌØÚÏ×ÁÎÉÅ + APACI × Apache 1.3, ÈÏÔÑ É ÎÅ Ñ×ÌÑÅÔÓÑ ÁÂÓÏÌÀÔÎÏ ÔÅÍ ÖÅ ÓÁÍÙÍ.
      • + +
    • ÷ ÄÏÂÁ×ÏË Ë ÏÂÙÞÎÏÍÕ ÓÐÉÓËÕ ÍÏÄÕÌÅÊ, ËÏÔÏÒÙÅ ×Ù ÍÏÖÅÔÅ + ×ÙÂÒÁÔØ ÐÒÉ ÓÂÏÒËÅ ÓÅÒ×ÅÒÁ, × Apache 2.0 ÐÏÑ×ÉÌÉÓØ ÍÕÌØÔÉ - ÐÒÏÃÅÓÓÎÙÅ ÍÏÄÕÌÉ (íð - ÍÏÄÕÌÉ), × ËÏÔÏÒÙÈ ÔÅÐÅÒØ + ÓËÏÎÃÅÎÔÒÉÒÏ×ÁÎÁ ÏÓÎÏ×ÎÁÑ ÞÁÓÔØ ËÏÄÁ, ÏÔ×ÅÞÁÀÝÅÇÏ ÚÁ ÏÂÒÁÂÏÔËÕ + ÚÁÐÒÏÓÏ×.
      • +
    +
    top
    +
    +

    éÚÍÅÎÅÎÉÑ × ËÏÎÆÉÇÕÒÉÒÏ×ÁÎÉÉ ÒÁÂÏÔÙ ÓÅÒ×ÅÒÁ

    + + +
      +
    • íÎÏÇÉÅ ÉÚ ÔÅÈ ÄÉÒÅËÔÉ×, ËÏÔÏÒÙÅ ÏÂÓÌÕÖÉ×ÁÌÉÓØ ÑÄÒÏÍ ÓÅÒ×ÅÒÁ + Apache 1.3, ÔÅÐÅÒØ ÐÅÒÅÎÅÓÅÎÙ × ÍÕÌØÔÉ - ÐÒÏÃÅÓÓÎÙÅ ÍÏÄÕÌÉ. åÓÌÉ ×Ù + ÈÏÔÉÔÅ, ÞÔÏÂÙ ÐÏ×ÅÄÅÎÉÅ ÓÅÒ×ÅÒÁ ÂÙÌÏ ÎÁÉÂÏÌÅÅ ÐÒÉÂÌÉÖÅÎÏ Ë ÐÏ×ÅÄÅÎÉÀ + Apache 1.3, ÔÏ ÐÒÉ ÓÂÏÒËÅ ×Ù ÄÏÌÖÎÙ ×ÙÂÒÁÔØ íð-ÍÏÄÕÌØ prefork. äÒÕÇÉÅ íð-ÍÏÄÕÌÉ ÐÒÅÄÏÓÔÁ×ÌÑÀÔ + ÉÎÙÅ ÄÉÒÅËÔÉ×Ù, ÏÔ×ÅÞÁÀÝÉÅ ÚÁ ÒÁÂÏÔÕ ÐÒÏÃÅÓÓÏ× ÓÅÒ×ÅÒÁ É ÏÂÒÁÂÏÔËÕ + ÚÁÐÒÏÓÏ×.
      • + +
    • ðÒÏËÓÉ ÍÏÄÕÌØ ÂÙÌ ÐÅÒÅÐÉÓÁÎ, + É ÔÅÐÅÒØ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÓÐÅÃÉÆÉËÁÃÉÀ HTTP/1.1. ïÄÎÉÍ ÉÚ ÎÁÉÂÏÌÅÅ + ×ÁÖÎÙÈ ÉÚÍÅÎÅÎÉÊ Ñ×ÌÑÅÔÓÑ ÔÏ, ÞÔÏ ÄÉÒÅËÔÉ×Ù, ËÏÎÔÒÏÌÉÒÕÀÝÉÅ ÒÁÂÏÔÕ + ÍÏÄÕÌÑ, ÔÅÐÅÒØ ÒÁÓÐÏÌÁÇÁÀÔÓÑ × ÓÅËÃÉÉ <Proxy>, Á ÎÅ × + <Directory proxy:>, ËÁË ÜÔÏ ÂÙÌÏ ÒÁÎÅÅ.
      • + +
    • ïÂÒÁÂÏÔËÁ PATH_INFO (ÐÕÔÅ×ÏÊ ÉÎÆÏÒÍÁÃÉÉ, ÓÌÅÄÕÀÝÅÊ ÚÁ + ÉÍÅÎÅÍ ÚÁÐÒÁÛÉ×ÁÅÍÏÇÏ ÄÏËÕÍÅÎÔÁ) ÉÚÍÅÎÉÌÁÓØ ÄÌÑ ÎÅËÏÔÏÒÙÈ ÍÏÄÕÌÅÊ. + íÏÄÕÌÉ, ËÏÔÏÒÙÅ ÒÁÎØÛÅ ÂÙÌÉ ÎÁÐÉÓÁÎÙ ËÁË ÏÂÒÁÂÏÔÞÉËÉ (handler), Á + ÔÅÐÅÒØ ×ÙÐÏÌÎÑÀÔ ÒÏÌØ ÆÉÌØÔÒÏ×, ÍÏÇÕÔ ÂÏÌÅÅ ÎÅ ÐÒÉÎÉÍÁÔØ ÚÁÐÒÏÓÙ, + ÓÏÄÅÒÖÁÝÉÅ PATH_INFO. ôÁËÉÅ ÆÉÌØÔÒÙ, ËÁË INCLUDES ÒÅÁÌÉÚÏ×ÁÎÙ ÐÅÒ×ÙÍÉ × ÂÁÚÏ×ÏÍ + ÏÂÒÁÂÏÔÞÉËÅ, ÔÁËÉÍ ÏÂÒÁÚÏÍ ÏÎÉ ÎÅ ÍÏÇÕÔ ÐÒÉÎÉÍÁÔØ ÚÁÐÒÏÓÙ, ÓÏÄÅÒÖÁÝÉÅ + PATH_INFO. ÷Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÉÒÅËÔÉ×Õ AcceptPathInfo, ÞÔÏÂÙ ÚÁÓÔÁ×ÉÔØ ÂÁÚÏ×ÙÊ + ÏÂÒÁÂÏÔÞÉË ÐÒÉÎÉÍÁÔØ ÐÏÄÏÂÎÙÅ ÚÁÐÒÏÓÙ, É ÔÁËÉÍ ÏÂÒÁÚÏÍ ×ÏÓÓÔÁÎÏ×ÉÔØ + ×ÏÚÍÏÖÎÏÓÔØ ÉÓÐÏÌØÚÏ×ÁÎÉÑ PATH_INFO × ÄÏËÕÍÅÎÔÁÈ, ÉÓÐÏÌØÚÕÀÝÉÈ ×ËÌÀÞÅÎÉÑ + ÎÁ ÓÔÏÒÏÎÅ ÓÅÒ×ÅÒÁ (SSI).
      • + +
    • äÉÒÅËÔÉ×Á CacheNegotiatedDocs + ÔÅÐÅÒØ ÍÏÖÅÔ ÐÒÉÎÉÍÁÔØ ÁÒÇÕÍÅÎÔÙ on É + off. õÖÅ ÓÕÝÅÓÔ×ÕÀÝÉÅ ÜËÚÅÍÐÌÑÒÙ ÄÉÒÅËÔÉ×Ù + CacheNegotiatedDocs ÄÏÌÖÎÙ ÂÙÔØ ÚÁÍÅÎÅÎÙ ÎÁ + CacheNegotiatedDocs on.
      • + +
    • + äÉÒÅËÔÉ×Á ErrorDocument + ÂÏÌÅÅ ÎÅ ÉÓÐÏÌØÚÕÅÔ ÏÔËÒÙ×ÁÀÝÕÀ ËÁ×ÙÞËÕ × ÎÁÞÁÌÅ ÁÒÇÕÍÅÎÔÁ + ÄÌÑ ÏÂÏÚÎÁÞÅÎÉÑ ÔÏÇÏ, ÞÔÏ ÁÒÇÕÍÅÎÔ Ñ×ÌÑÅÔÓÑ ÔÅËÓÔÏ×ÙÍ ÓÏÏÂÝÅÎÉÅÍ. + ÷ÍÅÓÔÏ ÜÔÏÇÏ ×ÁÍ ÎÅÏÂÈÏÄÉÍÏ ÚÁËÌÀÞÁÔØ ×ÅÓØ ÔÅËÓÔ ÓÏÏÂÝÅÎÉÑ + × Ä×ÏÊÎÙÅ ËÁ×ÙÞËÉ. îÁÐÒÉÍÅÒ, ÓÕÝÅÓÔ×ÕÀÝÉÅ ÄÉÒÅËÔÉ×Ù + +

      + ErrorDocument 403 "îÅËÏÔÏÒÏÅ ÓÏÏÂÝÅÎÉÅ +

      + ÄÏÌÖÎÙ ÂÙÔØ ÚÁÍÅÎÅÎÙ ÎÁ + +

      + ErrorDocument 403 "îÅËÏÔÏÒÏÅ ÓÏÏÂÝÅÎÉÅ" +

      + åÓÌÉ ×ÔÏÒÏÊ ÁÒÇÕÍÅÎÔ ÎÅ Ñ×ÌÑÅÔÓÑ ÐÒÁ×ÉÌØÎÏ ÏÆÏÒÍÌÅÎÎÙÍ + ÉÄÅÎÔÉÆÉËÁÔÏÒÏÍ ÒÅÓÕÒÓÁ (URL) ÉÌÉ ÐÕÔÅ×ÙÍ ÉÍÅÎÅÍ, ÔÏ ÏÎ + ÂÕÄÅÔ ÉÎÔÅÒÐÒÅÔÉÒÏ×ÁÔØÓÑ ËÁË ÔÅËÓÔÏ×ÏÅ ÓÏÏÂÝÅÎÉÅ. +
      • + +
    • äÉÒÅËÔÉ×Ù AccessConfig É + ResourceConfig ÂÏÌÅÅ ÎÅ ÓÕÝÅÓÔ×ÕÀÔ. + éÍÅÀÝÉÅÓÑ ÉÈ ËÏÐÉÉ ÍÏÇÕÔ ÂÙÔØ ÚÁÍÅÎÅÎÙ ÄÉÒÅËÔÉ×ÏÊ + Include, ËÏÔÏÒÁÑ ÉÍÅÅÔ + ÔÕ ÖÅ ÆÕÎËÃÉÏÎÁÌØÎÏÓÔØ. åÓÌÉ ÐÒÅÖÄÅ ×Ù ÎÅ ×ËÌÀÞÁÌÉ ÉÈ × ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ + ÆÁÊÌÙ, ÔÅÍ ÓÁÍÙÍ ÉÓÐÏÌØÚÕÑ ÉÈ ÚÎÁÞÅÎÉÑ ÐÏ ÕÍÏÌÞÁÎÉÀ, ÔÏ ÓÅÊÞÁÓ, + ÄÌÑ ÄÏÓÔÉÖÅÎÉÑ ÔÏÇÏ ÖÅ ÒÅÚÕÌØÔÁÔÁ, ×ÁÍ ÎÁÄÏ + ÄÏÂÁ×ÉÔØ ÓÌÅÄÕÀÝÉÅ ÓÔÒÏËÉ × ÆÁÊÌ httpd.conf: Include conf/access.conf É Include + conf/srm.conf. äÌÑ ÔÏÇÏ ÞÔÏÂÙ ÂÙÔØ Õ×ÅÒÅÎÎÙÍ × ÔÏÍ, ÞÔÏ + Apache ÓÞÉÔÙ×ÁÅÔ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ ÉÍÅÎÎÏ × ÔÏÍ ÐÏÒÑÄËÅ, + ËÏÔÏÒÙÊ ÂÙÌ ÐÒÅÄÕÓÍÏÔÒÅÎ ÓÔÁÒÙÍÉ ÄÉÒÅËÔÉ×ÁÍÉ, ÎÁÄÏ ÐÏÍÅÓÔÉÔØ + ÄÉÒÅËÔÉ×Ù Include × ËÏÎÃÅ ÆÁÊÌÁ httpd.conf, ÐÒÉÞÅÍ + ÓÐÅÒ×Á ÔÕ, ÞÔÏ ×ËÌÀÞÁÅÔ srm.conf, Á ÚÁÔÅÍ ÔÕ, ÞÔÏ + ×ËÌÀÞÁÅÔ access.conf.
      • + +
    • äÉÒÅËÔÉ×Ù BindAddress É Port + ÂÏÌÅÅ ÎÅ ÓÕÝÅÓÔ×ÕÀÔ. üË×É×ÁÌÅÎÔÎÁÑ ÆÕÎËÃÉÏÎÁÌØÎÏÓÔØ ÐÒÅÄÏÓÔÁ×ÌÑÅÔÓÑ + ÂÏÌÅÅ ÇÉÂËÏÊ ÄÉÒÅËÔÉ×ÏÊ Listen. +
      • + +
    • ÷ Apache 1.3 ÄÉÒÅËÔÉ×Á Port + ÉÓÐÏÌØÚÏ×ÁÌÁÓØ, ËÒÏÍÅ ×ÓÅÇÏ ÐÒÏÞÅÇÏ, ÄÌÑ ÔÏÇÏ ÞÔÏÂÙ ÓÅÒ×ÅÒ + ÍÏÇ ÆÏÒÍÉÒÏ×ÁÔØ ÐÒÁ×ÉÌØÎÙÅ ÓÓÙÌËÉ ÎÁ ÓÁÍÏÇÏ ÓÅÂÑ. ÷ Apache 2.0 ÄÌÑ + ÔÅÈ ÖÅ ÃÅÌÅÊ ÓÌÕÖÉÔ ÎÏ×ÙÊ ÓÉÎÔÁËÓÉÓ ÄÉÒÅËÔÉ×Ù ServerName: ÏÎ ÂÙÌ ÉÚÍÅÎÅÎ ÔÁËÉÍ ÏÂÒÁÚÏÍ, ÞÔÏ ÔÅÐÅÒØ + ÉÍÑ ÈÏÓÔÁ É ÎÏÍÅÒ ÐÏÒÔÁ ÍÏÖÎÏ ÕËÁÚÙ×ÁÔØ × ÏÄÎÏÊ ÜÔÏÊ ÄÉÒÅËÔÉ×Å.
      • + +
    • äÉÒÅËÔÉ×Á ServerType ÂÏÌÅÅ ÎÅ ÓÕÝÅÓÔ×ÕÅÔ. + íÅÔÏÄ ÏÂÒÁÂÏÔËÉ ÚÁÐÒÏÓÏ× ÔÅÐÅÒØ ÏÐÒÅÄÅÌÑÅÔÓÑ ÐÏÓÒÅÄÓÔ×ÏÍ + ×ÙÂÏÒÁ íð-ÍÏÄÕÌÑ. ÷ ÎÁÓÔÏÑÝÅÅ ×ÒÅÍÑ ÎÅÔ ÔÁËÏÇÏ íð-ÍÏÄÕÌÑ, + ËÏÔÏÒÙÊ ÍÏÇ ÂÙ ÚÁÐÕÓËÁÔØÓÑ ÐÏÓÒÅÄÓÔ×ÏÍ ÄÅÍÏÎÁ inetd.
      • + +
    • íÏÄÕÌÉ mod_log_agent É mod_log_referer, ËÏÔÏÒÙÅ ÐÒÅÄÏÓÔÁ×ÌÑÌÉ + ÔÁËÉÅ ÄÉÒÅËÔÉ×Ù, ËÁË AgentLog, RefererLog + É RefererIgnore, ÂÙÌÉ ÕÂÒÁÎÙ. ÷ÅÄÅÎÉÅ ÖÕÒÎÁÌÁ ÁÇÅÎÔÏ× + ÐÏÌØÚÏ×ÁÔÅÌÅÊ (agent logs) É ÏÔÐÒÁ×ÉÔÅÌÅÊ (referer logs) ÐÏ-ÐÒÅÖÎÅÍÕ + ×ÏÚÍÏÖÎÏ ÐÏÓÒÅÄÓÔ×ÏÍ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÄÉÒÅËÔÉ×Ù CustomLog ÍÏÄÕÌÑ mod_log_config.
      • + +
    • äÉÒÅËÔÉ×Ù AddModule É + ClearModuleList ÂÏÌÅÅ ÎÅ ÓÕÝÅÓÔ×ÕÀÔ. ïÎÉ ÉÓÐÏÌØÚÏ×ÁÌÉÓØ + ÄÌÑ ÏÂÅÓÐÅÞÅÎÉÑ ÐÒÁ×ÉÌØÎÏÇÏ ÐÏÒÑÄËÁ ÚÁÇÒÕÚËÉ ÍÏÄÕÌÅÊ. îÏ×ÙÊ API ÄÌÑ + Apache 2.0 ÐÏÚ×ÏÌÑÅÔ ÍÏÄÕÌÑÍ ÓÁÍÉÍ ÕËÁÚÙ×ÁÔØ ÐÏÒÑÄÏË ÉÈ ÚÁÇÒÕÚËÉ, ÞÔÏ + ÄÅÌÁÅÔ ÜÔÉ ÄÉÒÅËÔÉ×Ù ÎÅÎÕÖÎÙÍÉ.
      • + +
    • äÉÒÅËÔÉ×Á FancyIndexing ÂÙÌÁ ÕÂÒÁÎÁ. åÅ ÆÕÎËÃÉÏÎÁÌØÎÏÓÔØ + ÔÅÐÅÒØ ÏÂÅÓÐÅÞÉ×ÁÅÔÓÑ ÏÐÃÉÅÊ FancyIndexing × ÄÉÒÅËÔÉ×Å IndexOptions
      • +
    +
    top
    +
    +

    äÒÕÇÉÅ ÉÚÍÅÎÅÎÉÑ

    + + +
      +
    • ïÐÃÉÑ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ httpd -S, + ÐÏÚ×ÏÌÑ×ÛÁÑ ÒÁÓÐÅÞÁÔÙ×ÁÔØ ËÏÎÆÉÇÕÒÁÃÉÀ ×ÉÒÔÕÁÌØÎÙÈ ÈÏÓÔÏ×, ÔÅÐÅÒØ ÚÁÍÅÎÅÎÁ + ÏÐÃÉÅÊ -t -D DUMP_VHOSTS.
      • + +
    • íÏÄÕÌØ mod_auth_digest, ËÏÔÏÒÙÊ ÉÍÅÌ ÜËÓÐÅÒÉÍÅÎÔÁÌØÎÙÊ ÓÔÁÔÕÓ × + Apache 1.3, ÔÅÐÅÒØ Ñ×ÌÑÅÔÓÑ ÓÔÁÎÄÁÒÔÎÙÍ ÍÏÄÕÌÅÍ.
      • + +
    • íÏÄÕÌØ mod_mmap_static, ËÏÔÏÒÙÊ ÉÍÅÌ ÜËÓÐÅÒÉÍÅÎÔÁÌØÎÙÊ ÓÔÁÔÕÓ × + Apache 1.3, ÚÁÍÅÎÅÎ ÍÏÄÕÌÅÍ mod_file_cache.
      • + +
    • ïÒÇÁÎÉÚÁÃÉÑ ÄÉÓÔÒÉÂÕÔÉ×Á ÐÏÌÎÏÓÔØÀ ÉÚÍÅÎÅÎÁ É ÔÅÐÅÒØ + ÂÏÌÅÅ ÎÅ ÓÏÄÅÒÖÉÔ ÎÅÚÁ×ÉÓÉÍÏÇÏ ËÁÔÁÌÏÇÁ src. ÷ÍÅÓÔÏ ÜÔÏÇÏ + ÉÓÈÏÄÎÙÅ ËÏÄÙ ÌÏÇÉÞÅÓËÉ ÏÒÇÁÎÉÚÏ×ÁÎÙ × ÏÓÎÏ×ÎÏÍ ËÁÔÁÌÏÇÅ ÄÉÓÔÒÉÂÕÔÉ×Á, Á + ÕÓÔÁÎÏ×ËÁ ÓËÏÍÐÉÌÉÒÏ×ÁÎÎÏÇÏ ÓÅÒ×ÅÒÁ ÐÒÏÉÚ×ÏÄÉÔÓÑ × ÏÔÄÅÌØÎÙÊ ËÁÔÁÌÏÇ.
      • +
    +
    top
    +
    +

    íÏÄÕÌÉ ÔÒÅÔØÉÈ ÆÉÒÍ

    + + +

    úÎÁÞÉÔÅÌØÎÙÅ ÉÚÍÅÎÅÎÉÑ ÂÙÌÉ ×ÎÅÓÅÎÙ × API ÄÌÑ Apache 2.0. + óÕÝÅÓÔ×ÕÀÝÉÅ ÍÏÄÕÌÉ, ÎÁÐÉÓÁÎÎÙÅ Ó ÉÓÐÏÌØÚÏ×ÁÎÉÅÍ Apache 1.3 API, + ÎÅ ÂÕÄÕÔ ÒÁÂÏÔÁÔØ ÐÏÄ Apache 2.0, ÅÓÌÉ ÎÅ ×ÎÅÓÔÉ + × ÎÉÈ ÎÅÏÂÈÏÄÉÍÙÅ ÉÚÍÅÎÅÎÉÑ. âÏÌÅÅ ÐÏÄÒÏÂÎÁÑ ÉÎÆÏÒÍÁÃÉÑ ÐÏ ÜÔÏÍÕ ÐÏ×ÏÄÕ + ÄÏÓÔÕÐÎÁ × ÄÏËÕÍÅÎÔÁÃÉÉ ÄÌÑ ÒÁÚÒÁÂÏÔÞÉËÏ×.

    +
    +
    +

    äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + ja  | + ko  | + pt-br  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/urlmapping.html b/docs/manual/urlmapping.html new file mode 100644 index 00000000..5a9c3a92 --- /dev/null +++ b/docs/manual/urlmapping.html @@ -0,0 +1,11 @@ +URI: urlmapping.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: urlmapping.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: urlmapping.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/urlmapping.html.en b/docs/manual/urlmapping.html.en new file mode 100644 index 00000000..2174ce4f --- /dev/null +++ b/docs/manual/urlmapping.html.en @@ -0,0 +1,286 @@ + + + +Mapping URLs to Filesystem Locations - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Mapping URLs to Filesystem Locations

    +
    +

    Available Languages:  en  | + ja  | + ko 

    +
    + +

    This document explains how Apache uses the URL of a request + to determine the filesystem location from which to serve a + file.

    +
    + +
    top
    +
    +

    Related Modules and Directives

    + +
    Related ModulesRelated Directives
    +
    top
    +
    +

    DocumentRoot

    + +

    In deciding what file to serve for a given request, Apache's + default behavior is to take the URL-Path for the request (the part + of the URL following the hostname and port) and add it to the end + of the DocumentRoot specified + in your configuration files. Therefore, the files and directories + underneath the DocumentRoot + make up the basic document tree which will be visible from the + web.

    + +

    Apache is also capable of Virtual + Hosting, where the server receives requests for more than one + host. In this case, a different DocumentRoot can be specified for each + virtual host, or alternatively, the directives provided by the + module mod_vhost_alias can + be used to dynamically determine the appropriate place from which + to serve content based on the requested IP address or + hostname.

    +
    top
    +
    +

    Files Outside the DocumentRoot

    + +

    There are frequently circumstances where it is necessary to + allow web access to parts of the filesystem that are not strictly + underneath the DocumentRoot. Apache offers several + different ways to accomplish this. On Unix systems, symbolic links + can bring other parts of the filesystem under the DocumentRoot. For security reasons, + Apache will follow symbolic links only if the Options setting for the relevant + directory includes FollowSymLinks or + SymLinksIfOwnerMatch.

    + +

    Alternatively, the Alias directive will map any part + of the filesystem into the web space. For example, with

    + +

    Alias /docs /var/web

    + +

    the URL http://www.example.com/docs/dir/file.html + will be served from /var/web/dir/file.html. The + ScriptAlias directive + works the same way, with the additional effect that all content + located at the target path is treated as CGI scripts.

    + +

    For situations where you require additional flexibility, you + can use the AliasMatch + and ScriptAliasMatch + directives to do powerful regular + expression based matching and substitution. For + example,

    + +

    ScriptAliasMatch ^/~([a-zA-Z0-9]+)/cgi-bin/(.+) + /home/$1/cgi-bin/$2

    + +

    will map a request to + http://example.com/~user/cgi-bin/script.cgi to the + path /home/user/cgi-bin/script.cgi and will treat + the resulting file as a CGI script.

    +
    top
    +
    +

    User Directories

    + +

    Traditionally on Unix systems, the home directory of a + particular user can be referred to as + ~user/. The module mod_userdir + extends this idea to the web by allowing files under each user's + home directory to be accessed using URLs such as the + following.

    + +

    http://www.example.com/~user/file.html

    + +

    For security reasons, it is inappropriate to give direct + access to a user's home directory from the web. Therefore, the + UserDir directive + specifies a directory underneath the user's home directory + where web files are located. Using the default setting of + Userdir public_html, the above URL maps to a file + at a directory like + /home/user/public_html/file.html where + /home/user/ is the user's home directory as + specified in /etc/passwd.

    + +

    There are also several other forms of the + Userdir directive which you can use on systems + where /etc/passwd does not contain the location of + the home directory.

    + +

    Some people find the "~" symbol (which is often encoded on the + web as %7e) to be awkward and prefer to use an + alternate string to represent user directories. This functionality + is not supported by mod_userdir. However, if users' home + directories are structured in a regular way, then it is possible + to use the AliasMatch + directive to achieve the desired effect. For example, to make + http://www.example.com/upages/user/file.html map to + /home/user/public_html/file.html, use the following + AliasMatch directive:

    + +

    AliasMatch ^/upages/([a-zA-Z0-9]+)/?(.*) + /home/$1/public_html/$2

    +
    top
    +
    +

    URL Redirection

    + +

    The configuration directives discussed in the above sections + tell Apache to get content from a specific place in the filesystem + and return it to the client. Sometimes, it is desirable instead to + inform the client that the requested content is located at a + different URL, and instruct the client to make a new request with + the new URL. This is called redirection and is + implemented by the Redirect directive. For example, if + the contents of the directory /foo/ under the + DocumentRoot are moved + to the new directory /bar/, you can instruct clients + to request the content at the new location as follows:

    + +

    Redirect permanent /foo/ + http://www.example.com/bar/

    + +

    This will redirect any URL-Path starting in + /foo/ to the same URL path on the + www.example.com server with /bar/ + substituted for /foo/. You can redirect clients to + any server, not only the origin server.

    + +

    Apache also provides a RedirectMatch directive for more + complicated rewriting problems. For example, to redirect requests + for the site home page to a different site, but leave all other + requests alone, use the following configuration:

    + +

    RedirectMatch permanent ^/$ + http://www.example.com/startpage.html

    + +

    Alternatively, to temporarily redirect all pages on one site + to a particular page on another site, use the following:

    + +

    RedirectMatch temp .* + http://othersite.example.com/startpage.html

    +
    top
    +
    +

    Reverse Proxy

    + +

    Apache also allows you to bring remote documents into the URL space +of the local server. This technique is called reverse +proxying because the web server acts like a proxy server by +fetching the documents from a remote server and returning them to the +client. It is different from normal proxying because, to the client, +it appears the documents originate at the reverse proxy server.

    + +

    In the following example, when clients request documents under the +/foo/ directory, the server fetches those documents from +the /bar/ directory on internal.example.com +and returns them to the client as if they were from the local +server.

    + +

    +ProxyPass /foo/ http://internal.example.com/bar/
    +ProxyPassReverse /foo/ http://internal.example.com/bar/ +ProxyPassReverseCookieDomain internal.example.com public.example.com +ProxyPassReverseCookiePath /foo/ /bar/ +

    + +

    The ProxyPass configures +the server to fetch the appropriate documents, while the +ProxyPassReverse +directive rewrites redirects originating at +internal.example.com so that they target the appropriate +directory on the local server. Similarly, the +ProxyPassReverseCookieDomain +and ProxyPassReverseCookieDomain +rewrite cookies set by the backend server.

    +

    It is important to note, however, that +links inside the documents will not be rewritten. So any absolute +links on internal.example.com will result in the client +breaking out of the proxy server and requesting directly from +internal.example.com. A third-party module +mod_proxy_html +is available to rewrite links in HTML and XHTML.

    +
    top
    +
    +

    Rewriting Engine

    + +

    When even more powerful substitution is required, the rewriting + engine provided by mod_rewrite + can be useful. The directives provided by this module use + characteristics of the request such as browser type or source IP + address in deciding from where to serve content. In addition, + mod_rewrite can use external database files or programs to + determine how to handle a request. The rewriting engine is capable + of performing all three types of mappings discussed above: + internal redirects (aliases), external redirects, and proxying. + Many practical examples employing mod_rewrite are discussed in the + URL Rewriting Guide.

    +
    top
    +
    +

    File Not Found

    + +

    Inevitably, URLs will be requested for which no matching + file can be found in the filesystem. This can happen for + several reasons. In some cases, it can be a result of moving + documents from one location to another. In this case, it is + best to use URL redirection to inform + clients of the new location of the resource. In this way, you + can assure that old bookmarks and links will continue to work, + even though the resource is at a new location.

    + +

    Another common cause of "File Not Found" errors is + accidental mistyping of URLs, either directly in the browser, + or in HTML links. Apache provides the module + mod_speling (sic) to help with + this problem. When this module is activated, it will intercept + "File Not Found" errors and look for a resource with a similar + filename. If one such file is found, mod_speling will send an + HTTP redirect to the client informing it of the correct + location. If several "close" files are found, a list of + available alternatives will be presented to the client.

    + +

    An especially useful feature of mod_speling, is that it will + compare filenames without respect to case. This can help + systems where users are unaware of the case-sensitive nature of + URLs and the unix filesystem. But using mod_speling for + anything more than the occasional URL correction can place + additional load on the server, since each "incorrect" request + is followed by a URL redirection and a new request from the + client.

    + +

    If all attempts to locate the content fail, Apache returns + an error page with HTTP status code 404 (file not found). The + appearance of this page is controlled with the + ErrorDocument directive + and can be customized in a flexible manner as discussed in the + Custom error responses + document.

    +
    +
    +

    Available Languages:  en  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/urlmapping.html.ja.euc-jp b/docs/manual/urlmapping.html.ja.euc-jp new file mode 100644 index 00000000..b335a14f --- /dev/null +++ b/docs/manual/urlmapping.html.ja.euc-jp @@ -0,0 +1,286 @@ + + + +URL ¤«¤é¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î°ÌÃÖ¤Ø¤Î¥Þ¥Ã¥× - Apache HTTP ¥µ¡¼¥Ð + + + + +
    +

    ¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

    +

    Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

    +
    +
    <-
    +

    URL ¤«¤é¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î°ÌÃ֤ؤΥޥå×

    +
    +

    Available Languages:  en  | + ja  | + ko 

    +
    + +

    ¤³¤Îʸ½ñ¤Ï Apache ¤¬¥ê¥¯¥¨¥¹¥È¤Î URL ¤«¤éÁ÷¿®¤¹¤ë¥Õ¥¡¥¤¥ë¤Î + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î°ÌÃÖ¤ò·èÄꤹ¤ëÊýË¡¤òÀâÌÀ¤·¤Þ¤¹¡£

    +
    + +
    top
    +
    +

    ´ØÏ¢¤¹¤ë¥â¥¸¥å¡¼¥ë¤È¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

    + +
    ´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
    +
    top
    +
    +

    DocumentRoot

    + +

    ¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¤É¤Î¥Õ¥¡¥¤¥ë¤òÁ÷¿®¤¹¤ë¤«¤ò·èÄꤹ¤ë¤È¤­¤Î + Apache ¤Î¥Ç¥Õ¥©¥ë¥È¤ÎÆ°ºî¤Ï¡¢¥ê¥¯¥¨¥¹¥È¤Î URL-Path (URL ¤Î¥Û¥¹¥È̾¤È + ¥Ý¡¼¥ÈÈÖ¹æ¤Î¸å¤Ë³¤¯Éôʬ) ¤ò¼è¤ê½Ð¤·¤ÆÀßÄê¥Õ¥¡¥¤¥ë¤Ç»ØÄꤵ¤ì¤Æ¤¤¤ë + DocumentRoot + ¤ÎºÇ¸å¤ËÄɲ乤롢¤È¤¤¤¦¤â¤Î¤Ç¤¹¡£¤Ç¤¹¤«¤é¡¢ + DocumentRoot + ¤Î²¼¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ä¥Õ¥¡¥¤¥ë¤¬¥¦¥§¥Ö¤«¤é¸«¤¨¤ë´ðËܤΥɥ­¥å¥á¥ó¥È¤ÎÌÚ¹½Â¤¤ò + ¤Ê¤·¤Þ¤¹¡£

    + +

    Apache ¤Ë¤Ï¥µ¡¼¥Ð¤¬Ê£¿ô¤Î¥Û¥¹¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±¼è¤ë + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È ¤Îµ¡Ç½¤â¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¾ì¹ç¡¢¤½¤ì¤¾¤ì¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËÂФ·¤Æ°ã¤¦ + DocumentRoot + ¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤Þ¤¿¡¢mod_vhost_alias + ¥â¥¸¥å¡¼¥ë¤Ë¤è¤êÄ󶡤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¡¢ + Á÷¿®¤¹¤ë¤¿¤á¤Î¥³¥ó¥Æ¥ó¥Ä¤Î¾ì½ê¤ò¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿ IP + ¥¢¥É¥ì¥¹¤ä¥Û¥¹¥È̾¤«¤éưŪ¤Ë·è¤á¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£

    +
    top
    +
    +

    DocumentRoot ³°¤Î¥Õ¥¡¥¤¥ë

    + +

    ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î¡¢ + ¸·Ì©¤Ë¤Ï DocumentRoot + ¤Î²¼¤Ë¤Ï¤Ê¤¤Éôʬ¤Ø¤Î¥¦¥§¥Ö¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ëɬÍפ¬¤¢¤ë + ¾ì¹ç¤¬¤è¤¯¤¢¤ê¤Þ¤¹¡£Apache ¤Ï¤³¤Î¤¿¤á¤ËÊ£¿ô¤ÎÊýË¡¤òÍÑ°Õ¤·¤Æ¤¤¤Þ¤¹¡£ + Unix ¥·¥¹¥Æ¥à¤Ç¤Ï¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¾¤ÎÉôʬ¤ò¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò + »È¤Ã¤Æ DocumentRoot + ¤Î²¼¤Ë»ý¤Ã¤Æ¤¯¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÍýͳ¤Ë¤è¤ê¡¢ + Apache ¤Ï³ºÅö¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤Î + Options ¤ÎÀßÄê¤Ë + FollowSymLinks ¤« SymLinksIfOwnerMatch ¤¬ + ¤¢¤ë¾ì¹ç¤Ë¤Î¤ß¥·¥ó¥Ü¥ê¥Ã¥¯¥ê¥ó¥¯¤ò¤¿¤É¤ê¤Þ¤¹¡£

    + +

    Âå¤ï¤ê¤ÎÊýË¡¤È¤·¤Æ¡¢Alias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎǤ°Õ¤ÎÉôʬ¤ò¥¦¥§¥Ö¤Î¶õ´Ö¤Ë + ¥Þ¥Ã¥×¤Ç¤­¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢

    + +

    Alias /docs /var/web

    + +

    ¤È¤¤¤¦ÀßÄê¤Î¤È¤­¤Ï¡¢URL + http://www.example.com/docs/dir/file.html ¤Ë¤Ï + /var/web/dir/file.html ¤¬Á÷¿®¤µ¤ì¤Þ¤¹¡£ + ScriptAlias ¤â¡¢ + ÂоݤȤʤäƤ¤¤ë¥Ñ¥¹¤¬ CGI + ¥¹¥¯¥ê¥×¥È¤È¤·¤Æ°·¤ï¤ì¤ë¤È¤¤¤¦ÄɲäΠ+ ¸ú²Ì°Ê³°¤ÏƱ¤¸¤è¤¦¤ËÆ°ºî¤·¤Þ¤¹¡£

    + +

    ¤â¤Ã¤È½ÀÆð¤ÊÀßÄ꤬ɬÍפʾõ¶·¤Ç¤Ï¡¢ + AliasMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä + ScriptAliasMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö + ¤ò»È¤Ã¤Æ¶¯ÎϤÊÀµµ¬É½¸½¤Ë´ð¤Å¤¤¤¿¥Þ¥Ã¥Á¤È + ÃÖ´¹¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¡¢

    + +

    ScriptAliasMatch ^/~([a-zA-Z0-9]+)/cgi-bin/(.+) + /home/$1/cgi-bin/$2

    + +

    ¤Ï http://example.com/~user/cgi-bin/script.cgi ¤Ø¤Î + ¥ê¥¯¥¨¥¹¥È¤ò /home/user/cgi-bin/script.cgi ¤È¤¤¤¦¥Ñ¥¹¤Ø + ¥Þ¥Ã¥×¤·¡¢¤³¤Î¥Þ¥Ã¥×¤Î·ë²Ì¤È¤·¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò CGI ¥¹¥¯¥ê¥×¥È¤È¤·¤Æ + °·¤¤¤Þ¤¹¡£

    +
    top
    +
    +

    ¥æ¡¼¥¶¥Ç¥£¥ì¥¯¥È¥ê

    + +

    ÅÁÅýŪ¤Ë Unix ¥·¥¹¥Æ¥à¤Ç¤Ï¥æ¡¼¥¶ user ¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤ò + ~user/ ¤È¤·¤Æ»²¾È¤Ç¤­¤Þ¤¹¡£mod_userdir + ¥â¥¸¥å¡¼¥ë¤Ï¤³¤Î³µÇ°¤ò¥¦¥§¥Ö¤Ë³ÈÄ¥¤·¤Æ¡¢ + ¤½¤ì¤¾¤ì¤Î¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Î¥Õ¥¡¥¤¥ë¤ò + °Ê²¼¤Î¤è¤¦¤Ê URL ¤ò»È¤Ã¤Æ¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£

    + +

    http://www.example.com/~user/file.html

    + +

    ¥»¥­¥å¥ê¥Æ¥£¤Î´ÑÅÀ¤«¤é¡¢¥¦¥§¥Ö¤«¤é¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ø + ľÀÜ¥¢¥¯¥»¥¹¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤ÏŬÀڤǤϤ¢¤ê¤Þ¤»¤ó¡£¤Ç¤¹¤«¤é¡¢ + UserDir ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤Ï + ¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Î²¼¤Î¡¢¥¦¥§¥Ö¥Õ¥¡¥¤¥ë¤Î + ÃÖ¤«¤ì¤Æ¤¤¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ò»ØÄꤷ¤Þ¤¹¡£¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Î + Userdir public_html ¤ò»È¤¦¤È¡¢¾å¤Î URL ¤Ï + /home/user/public_html/file.html ¤È¤¤¤¦¤è¤¦¤Ê¥Õ¥¡¥¤¥ë¤Ë + ¥Þ¥Ã¥×¤µ¤ì¤Þ¤¹¡£¤³¤³¤Ç¡¢/home/user/ ¤Ï + /etc/passwd ¤Ç»ØÄꤵ¤ì¤Æ¤¤¤ë¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¹¡£

    + +

    Userdir ¤Ë¤Ï¡¢ + /etc/passwd ¤Ë¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤Î°ÌÃÖ¤¬½ñ¤«¤ì¤Æ¤¤¤Ê¤¤ + ¥·¥¹¥Æ¥à¤Ç¤â»È¤¦¤³¤È¤Î¤Ç¤­¤ë¾¤Î·Á¼°¤â¤¢¤ê¤Þ¤¹¡£

    + +

    Ãæ¤Ë¤Ï¥·¥ó¥Ü¥ë "~" (%7e ¤Î¤è¤¦¤ËÉä¹æ²½¤µ¤ì¤ë¤³¤È¤¬Â¿¤¤) + ¤ò³Ê¹¥¤¬°­¤¤¤È»×¤Ã¤Æ¡¢¥æ¡¼¥¶¤Î¥Ç¥£¥ì¥¯¥È¥ê¤òɽ¤¹¤¿¤á¤ËÊ̤Îʸ»úÎó¤Î + »ÈÍѤò¹¥¤à¿Í¤¬¤¤¤Þ¤¹¡£mod_userdir ¤Ï¤³¤Îµ¡Ç½¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤»¤ó¡£ + ¤·¤«¤·¡¢¥æ¡¼¥¶¤Î¥Û¡¼¥à¥Ç¥£¥ì¥¯¥È¥ê¤¬µ¬Â§Åª¤Ê¹½À®¤Î¤È¤­¤Ï¡¢ + AliasMatch ¤ò»È¤Ã¤Æ˾¤ß¤Î + ¸ú²Ì¤òãÀ®¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢ + http://www.example.com/upages/user/file.html ¤¬ + /home/user/public_html/file.html ¤Ë¥Þ¥Ã¥×¤µ¤ì¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢ + °Ê²¼¤Î¤è¤¦¤Ë AliasMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤¤¤Þ¤¹:

    + +

    AliasMatch ^/upages/([a-zA-Z0-9]+)/?(.*) + /home/$1/public_html/$2

    +
    top
    +
    +

    URL ¥ê¥À¥¤¥ì¥¯¥·¥ç¥ó

    + +

    ¾å¤ÎÀá¤ÇÀâÌÀ¤·¤¿ÀßÄêÍѤΥǥ£¥ì¥¯¥Æ¥£¥Ö¤Ï Apache ¤Ë + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÆÃÄê¤Î¾ì½ê¤«¤é¥³¥ó¥Æ¥ó¥Ä¤ò¼è¤Ã¤Æ¤­¤Æ + ¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤êÊÖ¤¹¤è¤¦¤Ë¤·¤Þ¤¹¡£¤È¤­¤Ë¤Ï¡¢¤½¤ÎÂå¤ï¤ê¤Ë + ¥¯¥é¥¤¥¢¥ó¥È¤Ë¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿¥³¥ó¥Æ¥ó¥Ä¤ÏÊ̤ΠURL ¤Ë¤¢¤ë¤³¤È¤ò + ÃΤ餻¤Æ¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬¿·¤·¤¤ URL ¤Ø¿·¤·¤¤¥ê¥¯¥¨¥¹¥È¤ò¹Ô¤Ê¤¦¤è¤¦¤Ë + ¤¹¤ëÊý¤¬Ë¾¤Þ¤·¤¤¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£¤³¤ì¤Ï¥ê¥À¥¤¥ì¥¯¥·¥ç¥ó¤È + ¸Æ¤Ð¤ì¤Æ¤¤¤Æ¡¢Redirect + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤è¤ê¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢ + DocumentRoot ¤Î²¼¤Î¥Ç¥£¥ì¥¯¥È¥ê + /foo/ ¤¬¿·¤·¤¤¥Ç¥£¥ì¥¯¥È¥ê /bar/ ¤Ë°ÜÆ°¤·¤¿¤È¤­¤Ï¡¢ + °Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ¥¯¥é¥¤¥¢¥ó¥È¤¬¿·¤·¤¤¾ì½ê¤Î¥³¥ó¥Æ¥ó¥Ä¤ò¥ê¥¯¥¨¥¹¥È¤¹¤ë¤è¤¦¤Ë + »Ø¼¨¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹:

    + +

    Redirect permanent /foo/ + http://www.example.com/bar/

    + +

    ¤³¤ì¤Ï¡¢/foo/ ¤Ç»Ï¤Þ¤ë¤¹¤Ù¤Æ¤Î URL-Path ¤ò¡¢ + www.example.com ¥µ¡¼¥Ð¤Î /bar/ ¤¬ + /foo/ ¤ËÃÖ´¹¤µ¤ì¤¿¤â¤Î¤Ë¥ê¥À¥¤¥ì¥¯¥È¤·¤Þ¤¹¡£ + ¥µ¡¼¥Ð¤Ï¼«Ê¬¼«¿È¤Î¥µ¡¼¥Ð¤À¤±¤Ç¤Ê¤¯¡¢¤É¤Î¥µ¡¼¥Ð¤Ë¤Ç¤â¥¯¥é¥¤¥¢¥ó¥È¤ò + ¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    + +

    Apache ¤Ï¤è¤êÊ£»¨¤Ê½ñ¤­´¹¤¨¤ÎÌäÂê¤Î¤¿¤á¤Ë¡¢ + RedirectMatch ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + Ä󶡤·¤Æ¤¤¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢¥µ¥¤¥È¤Î¥Û¡¼¥à¥Ú¡¼¥¸¤ò°ã¤¦¥µ¥¤¥È¤Ë¥ê¥À¥¤¥ì¥¯¥È + ¤¹¤ë¤±¤ì¤É¡¢Â¾¤Î¥ê¥¯¥¨¥¹¥È¤Ï¤½¤Î¤Þ¤Þ°·¤¦¡¢¤È¤¤¤¦¤È¤­¤Ï°Ê²¼¤ÎÀßÄê¤ò + »È¤¤¤Þ¤¹:

    + +

    RedirectMatch permanent ^/$ + http://www.example.com/startpage.html

    + +

    ¤¢¤ë¤¤¤Ï¡¢°ì»þŪ¤Ë¥µ¥¤¥È¤Î¤¹¤Ù¤Æ¤Î¥Ú¡¼¥¸¤ò¾¤Î¥µ¥¤¥È¤ÎÆÃÄê¤Î + ¥Ú¡¼¥¸¤Ø¥ê¥À¥¤¥ì¥¯¥È¤¹¤ë¤È¤­¤Ï¡¢°Ê²¼¤ò»È¤¤¤Þ¤¹:

    + +

    RedirectMatch temp .* + http://othersite.example.com/startpage.html

    +
    top
    +
    +

    ¥ê¥Ð¡¼¥¹¥×¥í¥­¥·

    + +

    Apache ¤Ï±ó³ÖÃϤˤ¢¤ë¥É¥­¥å¥á¥ó¥È¤ò¥í¡¼¥«¥ë¤Î¥µ¡¼¥Ð¤Î URL ¶õ´Ö¤Ë +»ý¤Ã¤Æ¤¯¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤³¤Î¼êË¡¤Ï¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¤È¸Æ¤Ð¤ì¤Æ¤¤¤Þ¤¹¡£ +¥¦¥§¥Ö¥µ¡¼¥Ð¤¬±ó³ÖÃϤΥɥ­¥å¥á¥ó¥È¤ò¼èÆÀ¤·¤Æ¥¯¥é¥¤¥¢¥ó¥È¤ËÁ÷¤êÊÖ¤¹¤Î¤¬ +¥×¥í¥­¥·¥µ¡¼¥Ð¤ÎÆ°ºî¤Î¤è¤¦¤Ë¸«¤¨¤ë¤«¤é¤Ç¤¹¡£¥¯¥é¥¤¥¢¥ó¥È¤Ë¤Ï¥É¥­¥å¥á¥ó¥È¤¬ +¥ê¥Ð¡¼¥¹¥×¥í¥­¥·¥µ¡¼¥Ð¤«¤éÁ÷¤é¤ì¤Æ¤­¤Æ¤¤¤ë¤è¤¦¤Ë¸«¤¨¤ëÅÀ¤¬Ä̾ï¤Î +¥×¥í¥­¥·¤È¤Ï°Û¤Ê¤ê¤Þ¤¹¡£

    + +

    ¼¡¤ÎÎã¤Ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤¬ /foo/ ¥Ç¥£¥ì¥¯¥È¥ê¤Î²¼¤Ë¤¢¤ë +¥É¥­¥å¥á¥ó¥È¤ò¥ê¥¯¥¨¥¹¥È¤¹¤ë¤È¡¢¥µ¡¼¥Ð¤¬ internal.example.com ¤Î +/bar/ ¥Ç¥£¥ì¥¯¥È¥ê¤«¤é¼èÆÀ¤·¤Æ¡¢¤µ¤â¥í¡¼¥«¥ë¥µ¡¼¥Ð¤«¤é¤Î +¥É¥­¥å¥á¥ó¥È¤Î¤è¤¦¤Ë¤·¤Æ¥¯¥é¥¤¥¢¥ó¥È¤ËÊÖ¤·¤Þ¤¹¡£

    + +

    +ProxyPass /foo/ http://internal.example.com/bar/
    +ProxyPassReverse /foo/ http://internal.example.com/bar/
    +ProxyPassReverseCookieDomain internal.example.com public.example.com
    +ProxyPassReverseCookiePath /foo/ /bar/ +

    + +

    ProxyPass ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï +¥µ¡¼¥Ð¤¬Å¬Àڤʥɥ­¥å¥á¥ó¥È¤ò¼èÆÀ¤¹¤ë¤è¤¦¤ËÀßÄꤷ¡¢ +ProxyPassReverse ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï +internal.example.com ¤«¤é¤Î¥ê¥À¥¤¥ì¥¯¥È¤¬¥í¡¼¥«¥ë¥µ¡¼¥Ð¤Î +ŬÀڤʥǥ£¥ì¥¯¥È¥ê¤ò»Ø¤¹¤è¤¦¤Ë½ñ¤­´¹¤¨¤Þ¤¹¡£ +ƱÍÍ¤Ë ProxyPassReverseCookieDomain +¤È ProxyPassReverseCookiePath +¤Ç¥Ð¥Ã¥¯¥¨¥ó¥É¦¥µ¡¼¥Ð¤Îȯ¹Ô¤·¤¿ Cookie ¤ò½ñ¤­´¹¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    +

    ¤¿¤À¤·¡¢¥É¥­¥å¥á¥ó¥È¤ÎÃæ¤Î¥ê¥ó¥¯¤Ï½ñ¤­´¹¤¨¤é¤ì¤Ê¤¤¡¢ +¤È¤¤¤¦¤³¤È¤ÏÃΤäƤª¤¤¤Æ¤¯¤À¤µ¤¤¡£ +¤Ç¤¹¤«¤é¡¢internal.example.com ¤Ø¤ÎÀäÂХѥ¹¤Ë¤è¤ë¥ê¥ó¥¯¤Ç¤Ï¡¢ +¥¯¥é¥¤¥¢¥ó¥È¤¬¥×¥í¥­¥·¥µ¡¼¥Ð¤òÈ´¤±½Ð¤·¤Æ internal.example.com ¤Ë +ľÀܥꥯ¥¨¥¹¥È¤òÁ÷¤ë¡¢¤È¤¤¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£ +¥µ¡¼¥É¥Ñ¡¼¥Æ¥£À½¥â¥¸¥å¡¼¥ë¤Î mod_proxy_html +¤Ï¡¢HTML ¤È XHTML Ãæ¤Î¥ê¥ó¥¯¤ò½ñ¤­´¹¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    +
    top
    +
    +

    ¥ê¥é¥¤¥È¥¨¥ó¥¸¥ó

    + +

    ¤è¤ê°ìÁض¯ÎϤÊÃÖ´¹¤¬É¬ÍפʤȤ­¤Ï¡¢mod_rewrite + ¤¬Ä󶡤¹¤ë¥ê¥é¥¤¥È¥¨¥ó¥¸¥ó¤¬Ìò¤ËΩ¤Ä¤Ç¤·¤ç¤¦¡£ + ¤³¤Î¥â¥¸¥å¡¼¥ë¤Ë¤è¤êÄ󶡤µ¤ì¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï + ¥Ö¥é¥¦¥¶¤Î¼ïÎà¡¢¥ê¥¯¥¨¥¹¥È¸µ¤Î IP ¥¢¥É¥ì¥¹¤Ê¤É¤Î¥ê¥¯¥¨¥¹¥È¤ÎÆÃħ¤ò + »È¤Ã¤ÆÁ÷¤êÊÖ¤¹¥³¥ó¥Æ¥ó¥Ä¤Î¾ì½ê¤ò·è¤á¤Þ¤¹¡£¤µ¤é¤Ë¡¢mod_rewrite + ¤Ï³°Éô¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤ä¥×¥í¥°¥é¥à¤ò»È¤Ã¤Æ¥ê¥¯¥¨¥¹¥È¤Î°·¤¤Êý¤ò + ·è¤á¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¥ê¥é¥¤¥È¥¨¥ó¥¸¥ó¤Ï¾å¤Çµó¤²¤é¤ì¤Æ¤¤¤ë»°¤Ä¤Î¥Þ¥Ã¥Ô¥ó¥° + ¤¹¤Ù¤Æ¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹: ÆâÉô¤Î¥ê¥À¥¤¥ì¥¯¥È (¥¨¥¤¥ê¥¢¥¹)¡¢ + ³°Éô¤Î¥ê¥À¥¤¥ì¥¯¥È¡¢¥×¥í¥­¥·¤Ç¤¹¡£mod_rewrite ¤ò»È¤¦Â¿¤¯¤Î¼ÂÍÑŪ¤ÊÎã¤Ï + URL ¥ê¥é¥¤¥È¥¬¥¤¥É + ¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£

    +
    top
    +
    +

    File Not Found

    + +

    ɬ¤º¡¢¥ê¥¯¥¨¥¹¥È¤µ¤ì¤¿ URL ¤ËÂбþ¤¹¤ë¥Õ¥¡¥¤¥ë¤¬¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ë + ̵¤¤¤È¤¤¤¦¾ì¹ç¤¬È¯À¸¤·¤Þ¤¹¡£¤³¤ì¤¬µ¯¤³¤ë¤Î¤Ë¤Ï¤¤¤¯¤Ä¤«¤ÎÍýͳ¤¬¤¢¤ê¤Þ¤¹¡£ + ¾ì¹ç¤Ë¤è¤Ã¤Æ¤Ï¡¢¥É¥­¥å¥á¥ó¥È¤òÊ̤ξì½ê¤Ë°ÜÆ°¤·¤¿·ë²Ì¤Ç¤¢¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Î¾ì¹ç¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ë¥ê¥½¡¼¥¹¤Î¿·¤·¤¤°ÌÃÖ¤òÃΤ餻¤ë¤¿¤á¤Ë + URL ¥ê¥À¥¤¥ì¥¯¥·¥ç¥ó¤ò»È¤¦¤Î¤¬ºÇÁ±¤ÎÊýË¡¤Ç¤¹¡£ + ¤½¤¦¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢¥ê¥½¡¼¥¹¤Ï¿·¤·¤¤°ÌÃ֤˰ÜÆ°¤·¤Æ¤¤¤ë¤±¤ì¤É¤â¡¢ + ¸Å¤¤¥Ö¥Ã¥¯¥Þ¡¼¥¯¤ä¥ê¥ó¥¯¤¬Æ°ºî¤·Â³¤±¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    + +

    "File Not Found" ¥¨¥é¡¼¤Î¤â¤¦°ì¤Ä¤Î¤è¤¯¤¢¤ëÍýͳ¤Ï¡¢ + ¥Ö¥é¥¦¥¶¤Ø¤ÎľÀÜÆþÎϤä HTML ¥ê¥ó¥¯¤«¤é¤Î¶öȯŪ¤Ê URL ¤ÎÆþÎϴְ㤤¤Ç¤¹¡£ + Apache ¤Ï¤³¤ÎÌäÂê¤ò²þÁ±¤¹¤ë¤¿¤á¤Ë¡¢mod_speling + ¥â¥¸¥å¡¼¥ë (°Õ¿ÞŪ¤ÊÄÖ¤ê´Ö°ã¤¤) + (ÌõÃí: Àµ¤·¤¯¤Ï spelling) ¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥â¥¸¥å¡¼¥ë¤¬ + »ÈÍѤµ¤ì¤Æ¤¤¤ë¤È¤­¤Ï¡¢"File Not Found" ¥¨¥é¡¼¤ò²£¼è¤ê¤·¤Æ¡¢ + »÷¤¿¥Õ¥¡¥¤¥ë̾¤Î¥ê¥½¡¼¥¹¤òõ¤·¤Þ¤¹¡£¤â¤·°ì¤Ä¤À¤±¸«¤Ä¤«¤Ã¤¿¾ì¹ç¤Ï + mod_speling ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ËÀµ¤·¤¤°ÌÃÖ¤òÃΤ餻¤ë¤¿¤á¤Ë HTTP ¥ê¥À¥¤¥ì¥¯¥È¤ò + Á÷¤ê¤Þ¤¹¡£¤â¤·Ê£¿ô¤Î¡Ö¶á¤¤¡×¥Õ¥¡¥¤¥ë¤¬¸«¤Ä¤«¤Ã¤¿¾ì¹ç¤Ï¡¢¤½¤ì¤é + ÂåÂؤȤʤꤨ¤ë¤â¤Î¤Î¥ê¥¹¥È¤¬¥¯¥é¥¤¥¢¥ó¥È¤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£

    + +

    mod_speling ¤ÎÈó¾ï¤ËÍ­ÍѤʵ¡Ç½¤Ï¡¢Âçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤»¤º¤Ë + ¥Õ¥¡¥¤¥ë̾¤òÈæ³Ó¤¹¤ë¤â¤Î¤Ç¤¹¡£¤³¤ì¤Ï URL ¤È unix ¤Î + ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬Î¾Êý¤È¤âÂçʸ»ú¾®Ê¸»ú¤ò¶èÊ̤¹¤ë¤â¤Î¤Ç¤¢¤ë¡¢ + ¤È¤¤¤¦¤³¤È¤ò¥æ¡¼¥¶¤¬ÃΤé¤Ê¤¤¥·¥¹¥Æ¥à¤ÇÌò¤ËΩ¤Á¤Þ¤¹¡£¤¿¤À¤·¡¢ + »þÀޤΠURL ÄûÀµÄøÅ٤ǺѤޤº¡¢mod_speling ¤ò¤è¤ê¿¤¯»ÈÍѤ¹¤ë¤È¡¢¥µ¡¼¥Ð¤Ë + ¤µ¤é¤Ê¤ëÉé²Ù¤¬¤«¤«¤ê¤Þ¤¹¡£¤¹¤Ù¤Æ¤Î¡ÖÀµ¤·¤¯¤Ê¤¤¡×¥ê¥¯¥¨¥¹¥È¤Î¸å¤Ë + URL ¤Î¥ê¥À¥¤¥ì¥¯¥È¤È¥¯¥é¥¤¥¢¥ó¥È¤«¤é¤Î¿·¤·¤¤¥ê¥¯¥¨¥¹¥È¤¬¤¯¤ë¤³¤È¤Ë + ¤Ê¤ê¤Þ¤¹¤«¤é¡£

    + +

    ¥³¥ó¥Æ¥ó¥Ä¤Î°ÌÃÖ¤ò·è¤á¤è¤¦¤È¤¹¤ë¤¹¤Ù¤Æ¤Î»î¤ß¤¬¼ºÇÔ¤¹¤ë¤È¡¢ + Apache ¤Ï¡¢HTTP ¥¹¥Æ¡¼¥¿¥¹¥³¡¼¥É 404 (file not found) ¤È¶¦¤Ë + ¥¨¥é¡¼¥Ú¡¼¥¸¤òÊÖ¤·¤Þ¤¹¡£¤³¤Î¥¨¥é¡¼¥Ú¡¼¥¸¤Î³°´Ñ¤Ï + ErrorDocument + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀ©¸æ¤µ¤ì¡¢ + ¥«¥¹¥¿¥à¥¨¥é¡¼¥ì¥¹¥Ý¥ó¥¹ ¤Ç + ÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ë¡¢½ÀÆð¤ÊÀßÄê¤ò¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    +
    +
    +

    Available Languages:  en  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/urlmapping.html.ko.euc-kr b/docs/manual/urlmapping.html.ko.euc-kr new file mode 100644 index 00000000..65fb5602 --- /dev/null +++ b/docs/manual/urlmapping.html.ko.euc-kr @@ -0,0 +1,247 @@ + + + +URLÀ» ÆÄÀϽýºÅÛ À§Ä¡·Î ´ëÀÀÇϱâ - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    URLÀ» ÆÄÀϽýºÅÛ À§Ä¡·Î ´ëÀÀÇϱâ

    +
    +

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

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

    ÀÌ ¹®¼­´Â ¿äûÀÇ URLÀ» °¡Áö°í ¾ÆÆÄÄ¡°¡ ¾î¶»°Ô ¼­ºñ½ºÇÒ + ÆÄÀÏÀÇ ÆÄÀϽýºÅÛ»ó À§Ä¡¸¦ ã´ÂÁö ¼³¸íÇÑ´Ù.

    +
    + +
    top
    +
    +

    °ü·ÃµÈ ¸ðµâ°ú Áö½Ã¾îµé

    + +
    °ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
    +
    top
    +
    +

    DocumentRoot

    + +

    ¿äûÀ» ¹ÞÀº ¾ÆÆÄÄ¡´Â ¾î¶² ÆÄÀÏÀ» ¼­ºñ½ºÇÒÁö °áÁ¤ÇϱâÀ§ÇØ + ±âº»ÀûÀ¸·Î ¿äûÀÇ URL-°æ·Î(URL¿¡¼­ È£½ºÆ®¸í°ú Æ÷Æ® µÚ¿¡ + ³ª¿À´Â ºÎºÐ)¸¦ ¼³Á¤ÆÄÀÏ¿¡¼­ ÁöÁ¤ÇÑ DocumentRoot µÚ¿¡ ºÙÀδÙ. ±×·¡¼­ + DocumentRoot ¾Æ·¡ÀÖ´Â + ÆÄÀÏ°ú µð·ºÅ丮µéÀº À¥¿¡¼­ º¸°ÔµÉ ±âº»ÀûÀÎ ³»¿ëÀÌ´Ù.

    +
    top
    +
    +

    DocumentRoot ¹Û¿¡ ÀÖ´Â ÆÄÀϵé

    + +

    Á¾Á¾ ÆÄÀϽýºÅÛ¿¡¼­ DocumentRoot ¾Æ·¡ ÀÖÁö¾ÊÀº ºÎºÐÀ» + À¥¿¡¼­ Á¢±ÙÇÒ ÇÊ¿ä°¡ ÀÖ´Ù. ¾ÆÆÄÄ¡´Â ÀÌ °æ¿ì ¿©·¯°¡Áö ¹æ¹ýÀ» + »ç¿ëÇÒ ¼ö ÀÖ´Ù. À¯´Ð½º ½Ã½ºÅÛ¿¡¼­ ½Éº¼¸µÅ©¸¦ »ç¿ëÇÏ¿© + ÆÄÀϽýºÅÛÀÇ ´Ù¸¥ ºÎºÐÀ» DocumentRoot ¾Æ·¡¿¡ µÑ ¼ö ÀÖ´Ù. + º¸¾ÈÀ» À§ÇØ ¾ÆÆÄÄ¡´Â ÇØ´ç µð·ºÅ丮ÀÇ Options ¼³Á¤¿¡ + FollowSymLinks³ª + SymLinksIfOwnerMatch°¡ ÀÖ´Â °æ¿ì¿¡¸¸ ½Éº¼¸µÅ©¸¦ + µû¶ó°£´Ù.

    + +

    ¶Ç, Alias + Áö½Ã¾î´Â ÆÄÀϽýºÅÛÀÇ Æ¯Á¤ ºÎºÐÀ» À¥°ø°£¿¡ ´ëÀÀÇÑ´Ù. ¿¹¸¦ + µé¾î ´ÙÀ½°ú °°´Ù¸é

    + +

    Alias /docs /var/web

    + +

    URL http://www.example.com/docs/dir/file.htmlÀº + /var/web/dir/file.htmlÀ» °¡Áö°í ¼­ºñ½ºÇÑ´Ù. + ÁöÁ¤ÇÑ °æ·Î¿¡ ÀÖ´Â ¸ðµç ³»¿ëÀ» CGI ½ºÅ©¸³Æ®·Î Ãë±ÞÇÏ´Â °ÍÀ» + Á¦¿ÜÇÏ°í´Â ScriptAlias + Áö½Ã¾îµµ °°Àº ÀÏÀ» ÇÑ´Ù.

    + +

    AliasMatch¿Í + ScriptAliasMatch + Áö½Ã¾îÀÇ °­·ÂÇÑ Á¤±ÔÇ¥Çö½Ä±â¹Ý ´ëÀÀ°ú ´ëÄ¡¸¦ »ç¿ëÇÏ¿© ´õ + À¯¿¬ÇÑ ¼³Á¤ÀÌ °¡´ÉÇÏ´Ù. ¿¹¸¦ µé¾î,

    + +

    ScriptAliasMatch ^/~([a-zA-Z0-9]+)/cgi-bin/(.+) + /home/$1/cgi-bin/$2

    + +

    ´Â http://example.com/~user/cgi-bin/script.cgi·ÎÀÇ + ¿äûÀ» °æ·Î /home/user/cgi-bin/script.cgi·Î + ´ëÀÀÇÏ°í, ÇØ´ç ÆÄÀÏÀ» CGI ½ºÅ©¸³Æ®·Î Ãë±ÞÇÑ´Ù.

    +
    top
    +
    +

    »ç¿ëÀÚ µð·ºÅ丮

    + +

    À¯´Ð½º ½Ã½ºÅÛÀº ÀüÅëÀûÀ¸·Î ƯÁ¤ »ç¿ëÀÚ userÀÇ + Ȩµð·ºÅ丮¸¦ ~user/·Î ÁöĪÇÑ´Ù. + mod_userdir ¸ðµâÀº ÀÌ °³³äÀ» À¥¿¡±îÁö + È®ÀåÇÏ¿©, ´ÙÀ½°ú °°Àº URLÀ» °¡Áö°í °¢ »ç¿ëÀÚ È¨µð·ºÅ丮 + ¾È¿¡ ÀÖ´Â ÆÄÀÏÀ» ¼­ºñ½ºÇÑ´Ù.

    + +

    http://www.example.com/~user/file.html

    + +

    º¸¾È»ó À¥¿¡¼­ »ç¿ëÀÚ È¨µð·ºÅ丮·Î Á÷Á¢ Á¢±ÙÇÒ ¼ö ÀÖÀ¸¸é + ¾ÈµÈ´Ù. ±×·¡¼­ UserDir + Áö½Ã¾î´Â »ç¿ëÀÚ È¨µð·ºÅ丮¿¡¼­ À¥¿ë ÆÄÀϵéÀÌ ÀÖÀ» µð·ºÅ丮¸¦ + ÁöÁ¤ÇÑ´Ù. ±âº» ¼³Á¤ Userdir public_htmlÀ» »ç¿ëÇÏ°í + /home/user/°¡ /etc/passwd¿¡ ÁöÁ¤µÈ + »ç¿ëÀÚ È¨µð·ºÅ丮¶ó¸é, À§ÀÇ URLÀº ÆÄÀÏ + /home/user/public_html/file.html¿¡ ´ëÀÀÇÑ´Ù.

    + +

    ¶Ç, Userdir Áö½Ã¾î´Â /etc/passwd¿¡ + Ȩµð·ºÅ丮ÀÇ À§Ä¡°¡ ÀúÀåµÇÁö¾Ê´Â ½Ã½ºÅÛÀ» À§ÇØ ¿©·¯ ´Ù¸¥ + ÇüŸ¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

    + +

    ¾î¶² »ç¶÷Àº (º¸Åë À¥¿¡¼­ %7e·Î ÀÎÄÚµùµÇ´Â) + "~" ±âÈ£°¡ ÀÌ»óÇÏ¿© ´Ù¸¥ ¹æ½ÄÀ¸·Î »ç¿ëÀÚ µð·ºÅ丮¸¦ ³ªÅ¸³»°í + ½Í¾îÇÑ´Ù. ÀÌ ±â´ÉÀº mod_userdirÀÌ Á¦°øÇÏÁö¾Ê´Â´Ù. ±×·¯³ª + »ç¿ëÀÚ È¨µð·ºÅ丮°¡ ±ÔÄ¢ÀûÀÎ ¹æ¹ýÀ¸·Î ±¸¼ºµÇÀÖ´Ù¸é, AliasMatch Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + ¿øÇÏ´Â È¿°ú¸¦ ¾òÀ» ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, ´ÙÀ½ÀÇ + AliasMatch Áö½Ã¾î¸¦ »ç¿ëÇϸé + http://www.example.com/upages/user/file.htmlÀÌ + /home/user/public_html/file.html¿¡ ´ëÀÀÇÑ´Ù:

    + +

    AliasMatch ^/upages/([a-zA-Z0-9]+)/?(.*) + /home/$1/public_html/$2

    +
    top
    +
    +

    URL ¸®´ÙÀÌ·º¼Ç(Redirection)

    + +

    ¾Õ¿¡¼­ ¼³¸íÇÑ ¼³Á¤ Áö½Ã¾îµéÀº ¾ÆÆÄÄ¡°¡ ÆÄÀϽýºÅÛÀÇ Æ¯Á¤ + Àå¼Ò¿¡ ÀÖ´Â ³»¿ëÀ» Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³»°Ô ¸¸µç´Ù. ±×·¯³ª + ¶§¶§·Î ¿äûÇÑ ³»¿ëÀÌ ´Ù¸¥ URL¿¡ ÀÖ´Ù°í Ŭ¶óÀ̾ðÆ®¿¡°Ô ¾Ë·ÁÁÖ¾î, + Ŭ¶óÀ̾ðÆ®°¡ »õ·Î ±× URLÀ» ¿äûÇϵµ·Ï ¸¸µå´Â °ÍÀÌ ÁÁÀ» ¶§°¡ + ÀÖ´Ù. À̸¦ ¸®´ÙÀÌ·º¼Ç(redirection)À̶ó°í Çϸç, + Redirect Áö½Ã¾î¸¦ + »ç¿ëÇÑ´Ù. ¿¹¸¦ µé¾î, DocumentRoot ¾Æ·¡ /foo/ + µð·ºÅ丮ÀÇ ³»¿ëÀ» »õ·Î /bar/ µð·ºÅ丮·Î ¿Å°å´Ù¸é + ´ÙÀ½°ú °°ÀÌ Å¬¶óÀ̾ðÆ®°¡ »õ·Î¿î À§Ä¡¸¦ ¿äûÇϵµ·Ï ÇÑ´Ù:

    + +

    Redirect permanent /foo/ + http://www.example.com/bar/

    + +

    ±×·¯¸é www.example.com ¼­¹öÀÇ /foo/·Î + ½ÃÀÛÇÏ´Â URL-°æ·Î´Â /foo/¸¦ /bar/·Î + ¹Ù²Û URL·Î ¸®´ÙÀÌ·º¼ÇµÈ´Ù. Ŭ¶óÀ̾ðÆ®¸¦ ¿ø·¡ ¼­¹ö¿Ü¿¡ ¾î¶² + ´Ù¸¥ ¼­¹ö·Îµµ ¸®´ÙÀÌ·º¼ÇÇÒ ¼ö ÀÖ´Ù.

    + +

    ¶Ç, ¾ÆÆÄÄ¡´Â ´õ º¹ÀâÇÑ ÀçÀÛ¼º ¹®Á¦¸¦ À§ÇØ + RedirectMatch + Áö½Ã¾î¸¦ Á¦°øÇÑ´Ù. ¿¹¸¦ µé¾î, ´Ù¸¥ ¿äûÀº ±×´ë·Î µÎ°í »çÀÌÆ® + ȨÆäÀÌÁö¿¡ ´ëÇÑ ¿äû¸¸À» ´Ù¸¥ »çÀÌÆ®·Î ¸®´ÙÀÌ·º¼ÇÇÏ·Á¸é:

    + +

    RedirectMatch permanent ^/$ + http://www.example.com/startpage.html

    + +

    Àӽ÷Π»çÀÌÆ®ÀÇ ¸ðµç ÆäÀÌÁö¸¦ ´Ù¸¥ »çÀÌÆ®ÀÇ Æ¯Á¤ ÆäÀÌÁö·Î + ¸®´ÙÀÌ·º¼ÇÇÏ·Á¸é:

    + +

    RedirectMatch temp .* + http://othersite.example.com/startpage.html

    +
    top
    +
    +

    ¿ªÇÁ·Ï½Ã(Reverse Proxy)

    + +

    ¾ÆÆÄÄ¡´Â ´Ù¸¥ ¼­¹ö¿¡ ÀÖ´Â ¹®¼­¸¦ ¼­¹öÀÇ URL °ø°£À¸·Î °¡Á®¿Ã +¼ö ÀÖ´Ù. ÀÌ °æ¿ì À¥¼­¹ö°¡ ¿ø°Ý ¼­¹ö¿¡¼­ ¹®¼­¸¦ °¡Á®¿Í¼­ +Ŭ¶óÀ̾ðÆ®¿¡°Ô Àü´ÞÇÏ´Â ÇÁ·Ï½Ã ¼­¹ö¿Í °°ÀÌ µ¿ÀÛÇϱ⶧¹®¿¡ ÀÌ·± +¹æ¹ýÀ» ¿ªÇÁ·Ï½Ã(reverse proxying)¶ó°í ÇÑ´Ù. Ŭ¶óÀ̾ðÆ®ÀÇ +ÀÔÀå¿¡¼­ ¿ªÇÁ·Ï½Ã ¼­¹ö°¡ ¹®¼­¸¦ º¸³»ÁÖ´Â °Íó·³ º¸À̹ǷΠÀÏ¹Ý +ÇÁ·Ï½Ã¿Í´Â ´Ù¸£´Ù.

    + +

    ¾Æ·¡ ¼³Á¤¿¡¼­ Ŭ¶óÀ̾ðÆ®°¡ /foo/¿¡ ÀÖ´Â ¹®¼­¸¦ +¿äûÇϸé, ¼­¹ö´Â internal.example.comÀÇ +/bar/ µð·ºÅ丮¿¡¼­ ¹®¼­¸¦ °¡Á®¿Í¼­ ¹®¼­°¡ ¸¶Ä¡ +¼­¹ö¿¡ ÀÖ¾ú´ø °Íó·³ Ŭ¶óÀ̾ðÆ®¿¡°Ô º¸³½´Ù.

    + +

    +ProxyPass /foo/ http://internal.example.com/bar/
    +ProxyPassReverse /foo/ http://internal.example.com/bar/ +

    + +

    ProxyPass´Â ¼­¹ö°¡ +ÀûÀýÇÑ ¹®¼­¸¦ °¡Á®¿Àµµ·Ï ¼³Á¤Çϸç, ProxyPassReverse Áö½Ã¾î´Â +internal.example.comÀÌ º¸³»´Â ¸®´ÙÀÌ·º¼ÇÀ» ÀçÀÛ¼ºÇÏ¿© +¸®´ÙÀÌ·º¼ÇÀÌ ÇöÀç ¼­¹öÀÇ ÀûÀýÇÑ µð·ºÅ丮¸¦ °¡¸®Å°µµ·Ï ÇÑ´Ù. +¶Ç, ProxyPassReverseCookieDomain°ú +ProxyPassReverseCookieDomainÀº +°°Àº ¹æ¹ýÀ¸·Î ¿ø·¡ ¼­¹ö°¡ º¸³½ ÄíÅ°¸¦ ÀçÀÛ¼ºÇÑ´Ù.

    +

    ±×·¯³ª ¹®¼­ ¾È¿¡ ÀÖ´Â ¸µÅ©´Â ÀçÀÛ¼ºÇÏÁö ¾ÊÀ½À» ÁÖÀÇÇ϶ó. +internal.example.com¿¡ ´ëÇÑ Àý´ë¸µÅ©´Â Ŭ¶óÀ̾ðÆ®°¡ +ÇÁ·Ï½Ã¼­¹ö°¡ ¾Æ´Ï¶ó internal.example.comÀ¸·Î Á÷Á¢ +¿äûÇÏ°Ô ÇÑ´Ù. Á¦»ïÀÚ°¡ ¸¸µç mod_proxy_html +¸ðµâÀ» »ç¿ëÇÏ¿© HTML°ú XHTML¿¡ ÀÖ´Â ¸µÅ©¸¦ ÀçÀÛ¼ºÇÒ ¼ö ÀÖ´Ù.

    +
    top
    +
    +

    ÀçÀÛ¼º ¿£Áø (Rewriting Engine)

    + +

    ´õ °­·ÂÇÑ Ä¡È¯ÀÌ ÇÊ¿äÇÒ¶§ mod_rewriteÀÇ + ÀçÀÛ¼º ¿£ÁøÀÌ µµ¿òÀÌ µÈ´Ù. ÀÌ ¸ðµâÀÇ Áö½Ã¾î´Â ºê¶ó¿ìÀú Á¾·ù³ª + Ŭ¶óÀ̾ðÆ®ÀÇ IP ÁÖ¼Ò µî ¿äûÀÇ Æ¯Â¡À» °¡Áö°í ¾îµð¿¡ ÀÖ´Â + ³»¿ëÀ» ¼­ºñ½ºÇÒÁö °áÁ¤ÇÒ ¼ö ÀÖ´Ù. ¶Ç, mod_rewrite´Â ¿äûÀ» + ¾î¶»°Ô ó¸®ÇÒÁö °áÁ¤ÇϱâÀ§ÇØ ¿ÜºÎ µ¥ÀÌÅͺ£À̽º ÆÄÀÏÀ̳ª + ÇÁ·Î±×·¥À» »ç¿ëÇÒ ¼ö ÀÖ´Ù. ÀçÀÛ¼º ¿£ÁøÀº À§¿¡¼­ ´Ù·é ¼¼ + Á¾·ù ´ëÀÀ, Áï, ³»ºÎ ¸®´ÙÀÌ·º¼Ç (alias), ¿ÜºÎ ¸®´ÙÀÌ·º¼Ç, + ÇÁ·Ï½Ã, ¸ðµÎ¸¦ Áö¿øÇÑ´Ù. mod_rewrite¸¦ »ç¿ëÇÏ´Â ½ÇÁ¦ ¿¹´Â + URL Á¦ÀÛ¼º Áöħ¼­¿¡¼­ + ¼³¸íÇÑ´Ù.

    +
    top
    +
    +

    File Not Found

    + +

    °á±¹ ¿äûÇÑ URL¿¡ ´ëÀÀÇÏ´Â ÆÄÀÏÀ» ÆÄÀϽýºÅÛ¿¡¼­ ãÁö + ¸øÇÑ °æ¿ìÀÌ´Ù. ¿©·¯ °¡Áö ÀÌÀ¯°¡ ÀÖ´Ù. ¾î¶² °æ¿ì ¹®¼­¸¦ + ´Ù¸¥ °÷À¸·Î ¿Å°å±â ¶§¹®ÀÏ ¼ö ÀÖ´Ù. ÀÌ °æ¿ì Ŭ¶óÀ̾ðÆ®¿¡°Ô + URL ¸®´ÙÀÌ·º¼ÇÀ¸·Î ÀÚ¿øÀÇ »õ·Î¿î + À§Ä¡¸¦ ¾Ë·ÁÁÖ´Â ¹æ¹ýÀÌ Á¦ÀÏ ÁÁ´Ù. ±×·¯¸é ÀÚ¿øÀ» ¿Å°Üµµ + ¿À·¡µÈ ºÏ¸¶Å©³ª ¸µÅ©°¡ °è¼Ó À¯È¿ÇÏ´Ù.

    + +

    "File Not Found" ¿À·ùÀÇ ´Ù¸¥ ÀϹÝÀûÀÎ ¿øÀÎÀº ºê¶ó¿ìÀú¿¡ + Á÷Á¢ ȤÀº HTML ¸µÅ©¿¡ URLÀÌ À߸ø ÀÔ·ÂµÈ °æ¿ìÀÌ´Ù. ¾ÆÆÄÄ¡´Â + mod_speling (¸ÂÃã¹ýÀÌ Æ²¸®Áö ¾Ê¾ÒÀ½) ¸ðµâ·Î + ÀÌ¿Í °°Àº ¹®Á¦¸¦ µ½´Â´Ù. ÀÌ ¸ðµâÀ» »ç¿ëÇϸé "File Not Found" + ¿À·ù°¡ ¹ß»ýÇÏ´Â °æ¿ì ºñ½ÁÇÑ ÆÄÀϸíÀ» °¡Áø ÀÚ¿øÀ» ã´Â´Ù. + ¸¸¾à ¹ß°ßÇϸé mod_spelingÀº Ŭ¶óÀ̾ðÆ®¸¦ ¿Ã¹Ù¸¥ À§Ä¡·Î + HTTP ¸®´ÙÀÌ·º¼ÇÇÑ´Ù. "ºñ½ÁÇÑ" ÆÄÀÏÀÌ ¿©·¯°³ ÀÖ´Ù¸é + Ŭ¶óÀ̾ðÆ®¿¡°Ô ¸ñ·ÏÀ» º¸³½´Ù.

    + +

    mod_spelingÀÇ Æ¯È÷ À¯¿ëÇÑ ÀåÁ¡Àº ´ë¼Ò¹®ÀÚ¸¦ ±¸º°ÇÏÁö¾Ê°í + ÆÄÀϸíÀ» ºñ±³ÇÏ´Â ±â´ÉÀÌ´Ù. ±×·¡¼­ À¯´Ð½º ÆÄÀϽýºÅÛ°ú URLÀÇ + ´ë¼Ò¹®ÀÚ ¼ºÁúÀ» ¾ËÁö¸øÇÏ´Â »ç¿ëÀÚ°¡ ÀÖ´Â ½Ã½ºÅÛ¿¡ µµ¿òÀÌ + µÈ´Ù. ±×·¯³ª mod_spelingÀÌ ÀÚÁÖ URLÀ» °íÃľßÇÑ´Ù¸é, "À߸øµÈ" + ¿äû¶§¸¶´Ù URL ¸®´ÙÀÌ·º¼Ç°ú Ŭ¶óÀ̾ðÆ®ÀÇ »õ·Î¿î ¿äûÀÌ + ÀϾ¹Ç·Î ¼­¹ö¿¡ ºÎ´ãÀÌ µÈ´Ù.

    + +

    ã´Â ½Ãµµ°¡ ¸ðµÎ ½ÇÆÐÇÏ¸é ¾ÆÆÄÄ¡´Â HTTP status code 404 + (file not found) ¿À·ùÆäÀÌÁö¸¦ º¸³½´Ù. ÀÌ ÆäÀÌÁöÀÇ ³»¿ëÀº + ErrorDocument Áö½Ã¾î·Î + Á¶ÀýÇϸç, »ç¿ëÀÚÁ¤ÀÇ ¿À·ù ÀÀ´ä + ¹®¼­¸¦ Âü°íÇÏ¿© »ç¿ëÀÚÁ¤ÀÇÇÒ ¼ö ÀÖ´Ù.

    +
    +
    +

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

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/details.html b/docs/manual/vhosts/details.html new file mode 100644 index 00000000..a15007e6 --- /dev/null +++ b/docs/manual/vhosts/details.html @@ -0,0 +1,11 @@ +URI: details.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: details.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: details.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/vhosts/details.html.en b/docs/manual/vhosts/details.html.en new file mode 100644 index 00000000..fb1ecb3c --- /dev/null +++ b/docs/manual/vhosts/details.html.en @@ -0,0 +1,442 @@ + + + +An In-Depth Discussion of Virtual Host Matching - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    An In-Depth Discussion of Virtual Host Matching

    +
    +

    Available Languages:  en  | + fr  | + ko 

    +
    + + +

    The virtual host code was completely rewritten in + Apache 1.3. This document attempts to explain + exactly what Apache does when deciding what virtual host to + serve a hit from. With the help of the new + NameVirtualHost + directive virtual host configuration should be a lot easier and + safer than with versions prior to 1.3.

    + +

    If you just want to make it work without + understanding how, here are some + examples.

    + +
    + +
    top
    +
    +

    Config File Parsing

    + +

    There is a main_server which consists of all the + definitions appearing outside of + <VirtualHost> sections. There are virtual + servers, called vhosts, which are defined by + <VirtualHost> + sections.

    + +

    The directives + Listen, + ServerName, + ServerPath, + and ServerAlias + can appear anywhere within the definition of a server. However, + each appearance overrides the previous appearance (within that + server).

    + +

    The default value of the Listen field for + main_server is 80. The main_server has no default + ServerPath, or ServerAlias. The + default ServerName is deduced from the server's IP + address.

    + +

    The main_server Listen directive has two functions. One + function is to determine the default network port Apache will + bind to. The second function is to specify the port number + which is used in absolute URIs during redirects.

    + +

    Unlike the main_server, vhost ports do not affect + what ports Apache listens for connections on.

    + +

    Each address appearing in the VirtualHost + directive can have an optional port. If the port is unspecified + it defaults to the value of the main_server's most recent + Listen statement. The special port * + indicates a wildcard that matches any port. Collectively the + entire set of addresses (including multiple A + record results from DNS lookups) are called the vhost's + address set.

    + +

    Unless a NameVirtualHost + directive is used for a specific IP address the first vhost + with that address is treated as an IP-based vhost. The IP + address can also be the wildcard *.

    + +

    If name-based vhosts should be used a + NameVirtualHost directive must appear + with the IP address set to be used for the name-based vhosts. + In other words, you must specify the IP address that holds the + hostname aliases (CNAMEs) for your name-based vhosts via a + NameVirtualHost directive in your configuration + file.

    + +

    Multiple NameVirtualHost directives can be used + each with a set of VirtualHost directives but only + one NameVirtualHost directive should be used for + each specific IP:port pair.

    + +

    The ordering of NameVirtualHost and + VirtualHost directives is not important which + makes the following two examples identical (only the order of + the VirtualHost directives for one + address set is important, see below):

    + + + + +

    + NameVirtualHost 111.22.33.44
    + <VirtualHost 111.22.33.44>
    + # server A
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.44>
    + # server B
    + ...
    + </VirtualHost>
    +
    + NameVirtualHost 111.22.33.55
    + <VirtualHost 111.22.33.55>
    + # server C
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # server D
    + ...
    + </VirtualHost> +

    + <VirtualHost 111.22.33.44>
    + # server A
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # server C
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.44>
    + # server B
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # server D
    + ...
    + </VirtualHost>
    +
    + NameVirtualHost 111.22.33.44
    + NameVirtualHost 111.22.33.55
    +
    +

    + + +

    (To aid the readability of your configuration you should + prefer the left variant.)

    + +

    After parsing the VirtualHost directive, the + vhost server is given a default Listen equal to the + port assigned to the first name in its VirtualHost + directive.

    + +

    The complete list of names in the VirtualHost + directive are treated just like a ServerAlias (but + are not overridden by any ServerAlias statement) + if all names resolve to the same address set. Note that + subsequent Listen statements for this vhost will not + affect the ports assigned in the address set.

    + +

    During initialization a list for each IP address is + generated and inserted into an hash table. If the IP address is + used in a NameVirtualHost directive the list + contains all name-based vhosts for the given IP address. If + there are no vhosts defined for that address the + NameVirtualHost directive is ignored and an error + is logged. For an IP-based vhost the list in the hash table is + empty.

    + +

    Due to a fast hashing function the overhead of hashing an IP + address during a request is minimal and almost not existent. + Additionally the table is optimized for IP addresses which vary + in the last octet.

    + +

    For every vhost various default values are set. In + particular:

    + +
      +
    1. If a vhost has no ServerAdmin, + ResourceConfig, + AccessConfig, + Timeout, + KeepAliveTimeout, + KeepAlive, + MaxKeepAliveRequests, + ReceiveBufferSize, + or SendBufferSize + directive then the respective value is inherited from the + main_server. (That is, inherited from whatever the final + setting of that value is in the main_server.)
      2. + +
    2. The "lookup defaults" that define the default directory + permissions for a vhost are merged with those of the + main_server. This includes any per-directory configuration + information for any module.
      3. + +
    3. The per-server configs for each module from the + main_server are merged into the vhost server.
      4. +
    + +

    Essentially, the main_server is treated as "defaults" or a + "base" on which to build each vhost. But the positioning of + these main_server definitions in the config file is largely + irrelevant -- the entire config of the main_server has been + parsed when this final merging occurs. So even if a main_server + definition appears after a vhost definition it might affect the + vhost definition.

    + +

    If the main_server has no ServerName at this + point, then the hostname of the machine that httpd + is running on is used instead. We will call the main_server address + set those IP addresses returned by a DNS lookup on the + ServerName of the main_server.

    + +

    For any undefined ServerName fields, a + name-based vhost defaults to the address given first in the + VirtualHost statement defining the vhost.

    + +

    Any vhost that includes the magic _default_ + wildcard is given the same ServerName as the + main_server.

    + +
    top
    +
    +

    Virtual Host Matching

    + +

    The server determines which vhost to use for a request as + follows:

    + +

    Hash table lookup

    + +

    When the connection is first made by a client, the IP + address to which the client connected is looked up in the + internal IP hash table.

    + +

    If the lookup fails (the IP address wasn't found) the + request is served from the _default_ vhost if + there is such a vhost for the port to which the client sent the + request. If there is no matching _default_ vhost + the request is served from the main_server.

    + +

    If the IP address is not found in the hash table then the + match against the port number may also result in an entry + corresponding to a NameVirtualHost *, which is + subsequently handled like other name-based vhosts.

    + +

    If the lookup succeeded (a corresponding list for the IP + address was found) the next step is to decide if we have to + deal with an IP-based or a name-base vhost.

    + + + +

    IP-based vhost

    + +

    If the entry we found has an empty name list then we have + found an IP-based vhost, no further actions are performed and + the request is served from that vhost.

    + + + +

    Name-based vhost

    + +

    If the entry corresponds to a name-based vhost the name list + contains one or more vhost structures. This list contains the + vhosts in the same order as the VirtualHost + directives appear in the config file.

    + +

    The first vhost on this list (the first vhost in the config + file with the specified IP address) has the highest priority + and catches any request to an unknown server name or a request + without a Host: header field.

    + +

    If the client provided a Host: header field the + list is searched for a matching vhost and the first hit on a + ServerName or ServerAlias is taken + and the request is served from that vhost. A Host: + header field can contain a port number, but Apache always + matches against the real port to which the client sent the + request.

    + +

    If the client submitted a HTTP/1.0 request without + Host: header field we don't know to what server + the client tried to connect and any existing + ServerPath is matched against the URI from the + request. The first matching path on the list is used and the + request is served from that vhost.

    + +

    If no matching vhost could be found the request is served + from the first vhost with a matching port number that is on the + list for the IP to which the client connected (as already + mentioned before).

    + + + +

    Persistent connections

    + +

    The IP lookup described above is only done once for a + particular TCP/IP session while the name lookup is done on + every request during a KeepAlive/persistent + connection. In other words a client may request pages from + different name-based vhosts during a single persistent + connection.

    + + + +

    Absolute URI

    + +

    If the URI from the request is an absolute URI, and its + hostname and port match the main server or one of the + configured virtual hosts and match the address and + port to which the client sent the request, then the + scheme/hostname/port prefix is stripped off and the remaining + relative URI is served by the corresponding main server or + virtual host. If it does not match, then the URI remains + untouched and the request is taken to be a proxy request.

    + + +

    Observations

    + +
      +
    • A name-based vhost can never interfere with an IP-base + vhost and vice versa. IP-based vhosts can only be reached + through an IP address of its own address set and never + through any other address. The same applies to name-based + vhosts, they can only be reached through an IP address of the + corresponding address set which must be defined with a + NameVirtualHost directive.
      • + +
    • ServerAlias and ServerPath + checks are never performed for an IP-based vhost.
      • + +
    • The order of name-/IP-based, the _default_ + vhost and the NameVirtualHost directive within + the config file is not important. Only the ordering of + name-based vhosts for a specific address set is significant. + The one name-based vhosts that comes first in the + configuration file has the highest priority for its + corresponding address set.
      • + +
    • For security reasons the port number given in a + Host: header field is never used during the + matching process. Apache always uses the real port to which + the client sent the request.
      • + +
    • If a ServerPath directive exists which is a + prefix of another ServerPath directive that + appears later in the configuration file, then the former will + always be matched and the latter will never be matched. (That + is assuming that no Host: header field was + available to disambiguate the two.)
      • + +
    • If two IP-based vhosts have an address in common, the + vhost appearing first in the config file is always matched. + Such a thing might happen inadvertently. The server will give + a warning in the error logfile when it detects this.
      • + +
    • A _default_ vhost catches a request only if + there is no other vhost with a matching IP address + and a matching port number for the request. The + request is only caught if the port number to which the client + sent the request matches the port number of your + _default_ vhost which is your standard + Listen by default. A wildcard port can be + specified (i.e., _default_:*) to catch + requests to any available port. This also applies to + NameVirtualHost * vhosts.
      • + +
    • The main_server is only used to serve a request if the IP + address and port number to which the client connected is + unspecified and does not match any other vhost (including a + _default_ vhost). In other words the main_server + only catches a request for an unspecified address/port + combination (unless there is a _default_ vhost + which matches that port).
      • + +
    • A _default_ vhost or the main_server is + never matched for a request with an unknown or + missing Host: header field if the client + connected to an address (and port) which is used for + name-based vhosts, e.g., in a + NameVirtualHost directive.
      • + +
    • You should never specify DNS names in + VirtualHost directives because it will force + your server to rely on DNS to boot. Furthermore it poses a + security threat if you do not control the DNS for all the + domains listed. There's more + information available on this and the next two + topics.
      • + +
    • ServerName should always be set for each + vhost. Otherwise A DNS lookup is required for each + vhost.
      • +
    + + +
    top
    +
    +

    Tips

    + +

    In addition to the tips on the DNS Issues page, here are + some further tips:

    + +
      +
    • Place all main_server definitions before any + VirtualHost definitions. (This is to aid the + readability of the configuration -- the post-config merging + process makes it non-obvious that definitions mixed in around + virtual hosts might affect all virtual hosts.)
      • + +
    • Group corresponding NameVirtualHost and + VirtualHost definitions in your configuration to + ensure better readability.
      • + +
    • Avoid ServerPaths which are prefixes of + other ServerPaths. If you cannot avoid this then + you have to ensure that the longer (more specific) prefix + vhost appears earlier in the configuration file than the + shorter (less specific) prefix (i.e., "ServerPath + /abc" should appear after "ServerPath /abc/def").
      • +
    + +
    +
    +

    Available Languages:  en  | + fr  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/details.html.fr b/docs/manual/vhosts/details.html.fr new file mode 100644 index 00000000..3e4fd6f7 --- /dev/null +++ b/docs/manual/vhosts/details.html.fr @@ -0,0 +1,459 @@ + + + +Détails sur le fonctionnement des serveurs virtuels - Serveur Apache HTTP + + + + +
    +

    Modules | Directives | FAQ | Glossaire | Plan du site

    +

    Serveur Apache HTTP Version 2.2

    +
    +
    <-
    +

    Détails sur le fonctionnement des serveurs virtuels

    +
    +

    Langues Disponibles:  en  | + fr  | + ko 

    +
    +
    Cette traduction peut être périmée. Verifiez la version + Anglaise pour les changements récents.
    + + +

    Le code gérant les serveurs virtuels a été réécrit à partir de + zéro dans Apache 1.3. Ce document vise à expliquer + dans le détail comment Apache procède lors du choix de l'utilisation + d'un serveur virtuel en fonction d'une requête reçue. L'apparition + de la directive NameVirtualHost + a rendu beaucoup plus facile et plus sûre la configuration des + serveurs virtuels par rapport aux versions précédant la 1.3.

    + +

    Si vous voulez juste que ça marche sans en + comprendre le fonctionnement, voici quelques + exemples.

    + +
    + +
    top
    +
    +

    Interprétation des fichiers +de configuration

    + +

    Un serveur principal (main_server) contient toutes + les définitions qui apparaissent en dehors des sections + <VirtualHost>. Les serveurs virtuels, aussi + appelés vhosts (pour virtual hosts), sont définis par les + sections <VirtualHost>.

    + +

    Les directives + Listen, + ServerName, + ServerPath, + et ServerAlias + peuvent être placées n'importe où dans le cadre de définition d'un + serveur. Cependant, chaque fois que l'une d'elles est lue, elle écrase + ses instances précédentes (dans le contexte du même serveur).

    + +

    La valeur par défaut du champ Listen pour le serveur + principal est de 80. Le serveur principal n'a pas de valeur par + défaut pour ServerPath ni pour ServerAlias. + La valeur par défaut de ServerName est déduite à partir + de l'adresses IP du serveur.

    + +

    La directive Listen associée au serveur principal a deux utilités. + La première détermine le port réseau sur lequel Apache va écouter. + La deuxième spécifie le port qui sera utilisé dans les URIs absolus + lors des redirections.

    + +

    À la différence du serveur principal, les ports des serveurs + virtuels n'affectent pas les ports sur lesquels + Apache se met à l'écoute.

    + +

    Chaque adresse incluse dans une directive VirtualHost + peut disposer d'un port optionnel. Si le port n'est pas précisé, il + prend par défaut la dernière valeur de Listen lue dans + la configuration du serveur principal. Le port particulier + * représente un joker qui correspond à tous les ports. + L'ensemble des adresses (y compris les résultats multiples + A issus des requêtes DNS) est appelé jeu + d'adresses du serveur virtuel.

    + +

    À moins qu'une directive + NameVirtualHost ne soit utilisée + pour une adresse IP spécifique, le premier serveur virtuel avec + cette adresse est considéré comme un serveur virtuel par-IP. + L'adresse IP peut également prendre la valeur joker *.

    + +

    Dans les cas où l'on souhaite utiliser un serveur virtuel + par nom, la directive NameVirtualHost doit + apparaître avec l'adresse IP choisie. En d'autres termes, vous devez + spécifier dans votre fichier de configuration l'adresse IP des noms + de domaine (CNAME) de vos serveurs virtuels par nom au moyen de + la directive NameVirtualHost.

    + +

    On peut utiliser plusieurs directives NameVirtualHost + pour un groupe de directives VirtualHost, mais seule + une directive NameVirtualHost doit être utilisée pour + chaque couple IP:port donné.

    + +

    L'ordre d'apparition des directives NameVirtualHost + et VirtualHost est sans importance, ce qui fait que + les deux exemples suivants ont des effets identiques (seul l'ordre + des directives VirtualHost pour un jeu + d'adresses est important, voir ci-dessous) :

    + + + + +

    + NameVirtualHost 111.22.33.44
    + <VirtualHost 111.22.33.44>
    + # serveur A
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.44>
    + # serveur B
    + ...
    + </VirtualHost>
    +
    + NameVirtualHost 111.22.33.55
    + <VirtualHost 111.22.33.55>
    + # serveur C
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # serveur D
    + ...
    + </VirtualHost> +

    + <VirtualHost 111.22.33.44>
    + # serveur A
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # serveur C
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.44>
    + # serveur B
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # serveur D
    + ...
    + </VirtualHost>
    +
    + NameVirtualHost 111.22.33.44
    + NameVirtualHost 111.22.33.55
    +
    +

    + + +

    (Il est conseillé d'adopter le choix de gauche pour faciliter + la lisibilité des fichiers de configuration.)

    + +

    Après la lecture de la directive VirtualHost, le + serveur virtuel se voit attribuer une valeur Listen + par défaut qui est la valeur du port associé au premier nom spécifié + dans sa directive VirtualHost.

    + +

    La liste complète des noms d'une directive VirtualHost + est gérée exactement comme des ServerAlias (mais ne + sont pas écrasés par d'autres ServerAlias) si tous + les noms sont résolus dans ce jeu d'adresse. À noter que les états + Listen de ce serveur virtuel sont sans incidence sur + les ports attibués au jeu d'adresses.

    + +

    Pendant la phase d'initialisation, une liste de chaque adresse + IP est générée et introduite dans une table de 'hash'. Si une + adresse IP est utilisée dans une directive NameVirtualHost, + cette liste contient les noms des serveurs virtuels pour cette + adresse. Si aucun serveur virtuel n'est défini pour cette adresse, + la directive NameVirtualHost est ignorée et un message + est envoyé au journal d'erreurs. Quand un serveur virtuel par IP + est utilisé, la table de 'hash' reste vide.

    + +

    La fonction de 'hash' étant rapide, le temps d'exécution d'un + 'hash' sur une adresse IP lors d'une requête est minimale et + quasiment imperceptible. De plus, la table est optimisée pour les + adresses IP dont le dernier octet est le seul à changer.

    + +

    Pour chaque serveur virtuel, diverses valeurs sont initialisées + par défaut. En particulier :

    + +
      +
    1. Dans le cas où un serveur virtuel ne contient pas de directives + ServerAdmin, + ResourceConfig, + AccessConfig, + Timeout, + KeepAliveTimeout, + KeepAlive, + MaxKeepAliveRequests, + ou SendBufferSize, + alors la valeur de chacun de ces paramètres est héritée de celle du + serveur principal. (C'est à dire, héritée de la valeur finale après + lecture de la configuration du serveur principal.)
      2. + +
    2. Les permissions par défaut sur les répertoires de chaque + serveur virtuel sont assemblées avec celles du serveur principal. + Elles concernent également toutes les informations de configuration + par répertoire pour tous les modules.
      3. + +
    3. Les configurations par serveur pour chaque module sont assemblées + à partir de celles du serveur principal.
      4. +
    + +

    L'essentiel des valeurs de configuration des serveurs virtuels + provient de valeurs par défaut issues du serveur principal. + Mais la position dans le fichier de configuration des directives + du serveur principal n'a pas d'importance -- l'ensemble de la + configuration du serveur principal est lu avant que ces valeurs par + défaut soient appliquées aux serveur virtuels. Ainsi, même si la + définition d'une valeur apparaît après celle d'un serveur virtuel, + cette valeur peut affecter la definition du serveur virtuel.

    + +

    Dans le cas où le serveur principal n'a pas de ServerName + à ce stade, le nom de la machine sur laquelle tourne le programme + httpd est utilisé à sa place. Nous appellerons + jeu d'adresses du serveur principal, les adresses IP + renvoyées par une résolution DNS sur le ServerName + du serveur principal.

    + +

    Pour tous les champs ServerName non définis, dans + le cas d'une configuration en serveur virtuel par nom, la valeur + adoptée par défaut est la première adresse donnée dans la section + VirtualHost qui définit le serveur virtuel.

    + +

    Si un serveur virtuel contient la valeur magique + _default_, il fonctionne sur le même ServerName + que le serveur principal.

    + +
    top
    +
    +

    Choix du serveur virtuel

    + +

    À la réception d'une requête, le serveur procède comme suit pour + déterminer quel serveur virtuel utiliser :

    + +

    Vérification dans la table de hash

    + +

    Après que le client se soit connecté, l'adresse + IP à laquelle le client s'est connecté est recherchée dans la + table de hash IP interne.

    + +

    Si la résolution de l'adresse IP n'aboutit pas (adresse IP non + trouvée), la requête est servie par le serveur virtuel + _default_ s'il est défini pour le port correspondant + à la requête. Sinon, elle est servie par le serveur principal.

    + +

    Si l'adresse IP n'est pas trouvée dans la table de hash, la + recherche du numéro de port peut aussi se terminer par une + correspondance à un NameVirtualHost * qui est géré + ensuite comme les autres serveur virtuels par noms.

    + +

    Si une liste est bien trouvée dans la table pour l'adresse + IP recherchée, l'étape suivante est de déterminer s'il s'agit + d'un serveur virtuel par nom ou par IP.

    + + + +

    Serveur virtuel par IP

    + +

    Si l'entrée trouvée dispose d'une liste de noms vide, c'est + qu'il s'agit d'un serveur virtuel par IP, et aucun autre choix + n'est plus à faire ; la requête est servie par ce serveur virtuel.

    + + + +

    Serveur virtuel par nom

    + +

    Si l'entrée trouvée correspond à un serveur virtuel par nom, + la liste de noms contient au moins une structure de serveurs + virtuels. Les serveurs virtuels se présentent dans cette liste + dans le même ordre que la lecture des directives VirtualHost + dans le fichier de configuration.

    + +

    Le premier serveur virtuel de cette liste (donc, le premier + serveur virtuel attribué à une adresse IP donnée dans le fichier + de configuration) se voit attribuer la plus grande priorité, ce + qui signifie que c'est lui qui traite les requêtes présentant un + nom de serveur invalide ou ne présentant pas de champ + Host: dans l'en-tête.

    + +

    Si un champ Host: est transmis dans l'en-tête de + la requête, son occurrence est recherchée dans la liste et le + premier serveur virtuel qui présente un ServerName + ou un ServerAlias correspondant est choisi pour + servir la requête. Il est possible que le champ Host: + contienne un numéro de port, mais Apache utilise toujours le + port sur lequel il a effectivement reçu la requête.

    + +

    Dans le cas où le client a envoyé une requête en HTTP/1.0 sans + un champ d'en-tête Host:, il est impossible de + déterminer le serveur auquel le client veut se connecter ; l'URI + de la requête est recherché dans tous les ServerPath + existants. Le premier chemin trouvé est utilisé et la requête est + servie par le serveur virtuel correspondant.

    + +

    Si aucun serveur virtuel n'est trouvé, la requête est servie + par le premier serveur virtuel qui écoute sur le port demandé et + qui est sur la liste associée à l'adresse IP vers laquelle la + requête a été envoyée (comme déjà précisé ci-avant).

    + + + +

    Connexions persistantes

    + +

    La recherche par adresse IP décrite ci-avant n'est faite + qu'une fois pour chaque session TCP/IP, alors que la + recherche par nom est réalisée pour chaque requête au + cours d'une connexion persistante (KeepAlive). En d'autres termes, + il est possible pour un client de faire des requêtes sur + différents serveurs virtuels par nom, au cours d'une unique + connexion persistante.

    + + + +

    URI absolu

    + +

    Au cas où l'URI de la requête est absolu, et que son nom de + serveur et son port correspondent au serveur principal (ou l'un + des serveurs virtuels configurés), et qu'ils correspondent + à l'adresse et au port de la requête, alors l'URI est amputé + de son préfixe protocole/nom de serveur/port et traité par le + serveur correspondant (principal ou virtuel). Si cette correspondance + n'existe pas, l'URI reste inchangé et la requête est considérée + comme une requête d'un serveur mandataire (proxy).

    + + +

    Observations

    + +
      +
    • Les serveurs virtuels par nom et par IP n'interfèrent + jamais entre eux. Les serveurs virtuels par IP ne sont joignables + qu'au travers de leur(s) adresse(s) IP propre(s), en aucun + cas par aucune autre adresse. Les serveurs virtuels par nom + ne sont accessibles que par leur(s) adresse(s) IP qui ne peuvent + être définies qu'au moyen de la directive + NameVirtualHost.
      • + +
    • Les vérifications sur ServerAlias et + ServerPath ne sont jamais réalisées pour les + serveurs virtuels par IP.
      • + +
    • L'ordre dans lequel sont agencés dans le fichier de + configuration le serveur virtuel _default_, les + serveurs virtuels par nom et par IP, et la directive + NameVirtualHost est sans incidence sur le + fonctionnement. Seul l'ordre des serveurs virtuels par nom + pour une adresse donnée a une importance. Le serveur virtuel + par nom qui est présent en premier dans la configuration se + voit attribué la priorité la plus haute pour les requêtes + arrivant sur son jeu d'adresses IP.
      • + +
    • Pour des raisons de sécurité, le numéro de port présenté + dans le champ d'en-tête Host: n'est jamais utilisé + pour les tests de correspondances. Apache ne prend en compte + que le numéro de port sur lequel le client a envoyé la requête.
      • + +
    • Si une directive ServerPath existe, et se + trouve être préfixe d'une autre directive ServerPath + qui apparaît plus loin dans la configuration, la première + sera toujours utilisée et la deuxième jamais. (Ceci ne se + produit que dans le cas où aucun champ Host: + n'a été présenté par le client pour distinguer les deux.)
      • + +
    • Dans le cas où deux serveurs virtuels par IP ont une + adresse en commun, le serveur virtuel qui apparaît en premier + dans la configuration est toujours choisi. Ce genre de chose + peut arriver par inadvertance. Le serveur envoie une alerte + dans le journal d'erreurs si ce cas se présente.
      • + +
    • Le serveur virtuel _default_ ne sert la requête + que si aucun autre serveur virtuel travaillant sur l'adresse + IP et le port demandés n'est trouvé. La requête n'est + traitée que si le numéro de port qui a reçu la requête est + associé au serveur virtuel _default_ (qui par + défaut, correspond à Listen). Un port joker peut + être spécifié (comme dans _default_:*) + pour récupérer les requêtes sur tous les ports ouverts. Ceci + est également applicable aux serveurs virtuels + NameVirtualHost *.
      • + +
    • Le serveur principal ne sert à servir les requêtes que + lorsque l'adresse IP et le port demandés par le client ne + correspondent à aucun serveur virtuel (y compris un serveur + virtuel _default_). En d'autres termes, le serveur + principal n'est utile que pour les combinaisons adresse/port + non spécifiées (sauf quand un serveur virtuel _default_ + correspond au port).
      • + +
    • Ni les serveurs virtuels _default_, ni le + serveur principal ne sont utilisés pour traiter une requête + avec un champ d'en-tête Host: manquant ou vide + lorsque l'adresse (et le port) de connexion correspondent à + des serveurs virtuels par nom, par exemple, dans une directive + NameVirtualHost.
      • + +
    • Il ne faut jamais employer de noms DNS dans des directives + VirtualHost, car cela oblige le serveur a s'appuyer + sur le DNS au moment du démarrage. De plus, vous vous exposez + à des problèmes de sécurité si vous n'avez pas la maîtrise du + DNS pour la totalité de vos domaines. Voir la documentation + disponible ici, ainsi que + les deux points précisés ci-après.
      • + +
    • Un nom de serveur ServerName devrait toujours + être indiqué pour chaque serveur virtuel. Sans cela, une + résolution DNS est nécessaire pour chaque serveur virtuel.
      • +
    + + +
    top
    +
    +

    Trucs et astuces

    + +

    En plus des points évoqués sur la page des + problèmes liés au DNS, + voici quelques points intéressants :

    + +
      +
    • Toujours positionner les définitions relatives au serveur + principal avant toute définition VirtualHost. + (Ceci améliore grandement la lisibilité de la configuration + -- la manière dont la configuration est interprétée après la + lecture des fichiers ne met pas en évidence le fait que les + définitions positionnées avant et surtout après les serveurs + virtuels peuvent impacter le fonctionnement des serveurs virtuels.)
      • + +
    • Toujours regrouper les définitions NameVirtualHost + et VirtualHost dans la configuration pour une + meilleure lisibilité.
      • + +
    • Éviter les ServerPaths qui sont préfixes + d'autres ServerPaths. Si cela ne peut être évité, + veillez à ce que le serveur virtuel contenant le préfixe le plus + long (donc le plus précis) apparaisse dans le fichier de + configuration avant le plus court. (par exemple, + "ServerPath /abc" est à spécifier après "ServerPath /abc/def").
      • +
    + +
    +
    +

    Langues Disponibles:  en  | + fr  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/details.html.ko.euc-kr b/docs/manual/vhosts/details.html.ko.euc-kr new file mode 100644 index 00000000..3b0efcc3 --- /dev/null +++ b/docs/manual/vhosts/details.html.ko.euc-kr @@ -0,0 +1,384 @@ + + + +°¡»óÈ£½ºÆ® ã±â¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸í - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    °¡»óÈ£½ºÆ® ã±â¿¡ ´ëÇÑ ÀÚ¼¼ÇÑ ¼³¸í

    +
    +

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

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

    °¡»óÈ£½ºÆ® ÄÚµå´Â ¾ÆÆÄÄ¡ 1.3¿¡¼­ °ÅÀÇ ´Ù½Ã + ÀÛ¼ºµÇ¾ú´Ù. ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡°¡ ¿äûÀ» ¹ÞÀ¸¸é ¾î¶² °¡»óÈ£½ºÆ®°¡ + ¼­ºñ½ºÇÒÁö °áÁ¤ÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù. »õ·Î¿î NameVirtualHost Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© + °¡»óÈ£½ºÆ® ¼³Á¤ÀÌ 1.3 ¹öÀü ÀÌÀüº¸´Ù ´õ ½±°í ¾ÈÀüÇØÁ³´Ù.

    + +

    ¾î¶»°Ô µ¿ÀÛÇÏ´ÂÁö ÀÌÇØÇÏÁö¾Ê°í ´ÜÁö µ¿ÀÛÇÏ°Ô¸¸ + ÇÏ°í ½Í´Ù¸é, ¿¹Á¦µéÀ» Âü°íÇ϶ó.

    + +
    + +
    top
    +
    +

    ¼³Á¤ÆÄÀÏ Àбâ

    + +

    <VirtualHost> ¼³Á¤À» Á¦¿ÜÇÑ ¼³Á¤ÀÌ + ÁÖ¼­¹ö¸¦ ¸¸µç´Ù. <VirtualHost> ¼½¼ÇÀ¸·Î Á¤ÀÇÇÑ + ºÎºÐÀ» °¡»óÈ£½ºÆ®¶ó°í ºÎ¸¥´Ù.

    + +

    Listen, + ServerName, + ServerPath, + ServerAlias Áö½Ã¾î´Â + ¼­¹ö Á¤ÀÇ ¾î´À°÷¿¡¼­µµ »ç¿ëÇÒ ¼ö ÀÖ´Ù. ±×·¯³ª °°Àº Áö½Ã¾î°¡ + ¿©·¯¹ø ³ª¿À¸é (±× ¼­¹ö¿¡¼­) ¸¶Áö¸· Áö½Ã¾î¸¸ÀÌ À¯È¿ÇÏ´Ù.

    + +

    ÁÖ¼­¹ö ListenÀÇ ±âº»°ªÀº 80ÀÌ´Ù. ÁÖ¼­¹öÀÇ + ServerPath³ª ServerAlias¿¡´Â + ±âº»°ªÀº ¾ø´Ù. ServerNameÀÇ ±âº»°ªÀº ¼­¹öÀÇ + IP ÁÖ¼ÒÀÌ´Ù.

    + +

    ÁÖ¼­¹öÀÇ Listen Áö½Ã¾î´Â µÎ°¡Áö ±â´ÉÀ» ÇÑ´Ù. ù°´Â + ¾ÆÆÄÄ¡°¡ ¿¬°áÇÒ ±âº» ³×Æ®¿÷ Æ÷Æ®¸¦ ÁöÁ¤ÇÏ´Â ÀÏÀÌ´Ù. µÑ°´Â + ¸®´ÙÀÌ·º¼ÇÇÒ Àý´ë URI¿¡ »ç¿ëÇÒ Æ÷Æ® ¹øÈ£¸¦ ÁöÁ¤ÇÏ´Â ÀÏÀÌ´Ù.

    + +

    ÁÖ¼­¹ö¿Í ´Þ¸® °¡»óÈ£½ºÆ®ÀÇ Æ÷Æ®´Â ¾ÆÆÄÄ¡°¡ ¿¬°áÀ» ±â´Ù¸®´Â + Æ÷Æ®¿¡ ¿µÇâÀ» ÁÖÁö ¾Ê´Â´Ù.

    + +

    VirtualHost Áö½Ã¾î¿¡ Æ÷Æ®¸¦ ÁöÁ¤ÇÒ ¼ö ÀÖ´Ù. + Æ÷Æ®¸¦ ÁöÁ¤ÇÏÁö¾ÊÀ¸¸é ÁÖ¼­¹öÀÇ °¡Àå ÃÖ±Ù Listen + °ªÀ» »ç¿ëÇÑ´Ù. Ưº°ÇÑ Æ÷Æ® *´Â ¾î¶² Æ÷Æ®¶óµµ + ÁöĪÇÏ´Â ¿ÍÀϵåÄ«µåÀÌ´Ù. (DNS °Ë»ö °á°úÀÇ ¿©·¯ A + ·¹Äڵ带 Æ÷ÇÔÇÏ¿©) °¡»óÈ£½ºÆ®ÀÇ ÁÖ¼Ò¸¦ ¸ðµÎ ÃÑĪÇÏ¿© °¡»óÈ£½ºÆ®ÀÇ + ÁÖ¼ÒÁýÇÕ(address set)À̶ó°í ºÎ¸¥´Ù.

    + +

    ƯÁ¤ IP ÁÖ¼Ò¿¡ ´ëÇÑ NameVirtualHost Áö½Ã¾î°¡ ¾ø´Ù¸é + ±× ÁÖ¼Ò¸¦ Æ÷ÇÔÇϴ ù¹ø° °¡»óÈ£½ºÆ®¸¦ IP±â¹Ý °¡»óÈ£½ºÆ®·Î Ãë±ÞÇÑ´Ù. + IP ÁÖ¼Ò¿¡ ¿ÍÀϵåÄ«µå *¸¦ »ç¿ëÇÒ ¼öµµ ÀÖ´Ù.

    + +

    À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÑ´Ù¸é À̸§±â¹Ý °¡»óÈ£½ºÆ®¿¡ + »ç¿ëÇÒ IP ÁÖ¼Ò¸¦ NameVirtualHost Áö½Ã¾î¿¡ + »ç¿ëÇØ¾ß ÇÑ´Ù. Áï, ¼³Á¤ÆÄÀÏÀÇ NameVirtualHost + Áö½Ã¾î¿¡ À̸§±â¹Ý °¡»óÈ£½ºÆ®ÀÇ È£½ºÆ®º°¸í(CNAME)¿¡ ÇØ´çÇÏ´Â + IP ÁÖ¼Ò¸¦ ÁöÁ¤ÇØ¾ß ÇÑ´Ù.

    + +

    ƯÁ¤ IP:Æ÷Æ® ½Ö¿¡ ´ëÇØ ¿ÀÁ÷ ÇÑ NameVirtualHost + Áö½Ã¾î¸¸À» »ç¿ëÇÑ´Ù¸é, ¿©·¯ NameVirtualHost Áö½Ã¾î¿Í + VirtualHost Áö½Ã¾î¸¦ ¼¯¾î¼­ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

    + +

    NameVirtualHost¿Í VirtualHost + Áö½Ã¾îÀÇ ¼ø¼­´Â Áß¿äÇÏÁö ¾Ê±â¶§¹®¿¡ ´ÙÀ½ µÎ ¿¹´Â °°´Ù (¿ÀÁ÷ + ÇÑ ÁÖ¼ÒÁýÇÕ¿¡ ´ëÇÑ VirtualHostÀÇ + ¼ø¼­°¡ Áß¿äÇÏ´Ù. ¾Æ·¡ Âü°í):

    + + + + +

    + NameVirtualHost 111.22.33.44
    + <VirtualHost 111.22.33.44>
    + # ¼­¹ö A
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.44>
    + # ¼­¹ö B
    + ...
    + </VirtualHost>
    +
    + NameVirtualHost 111.22.33.55
    + <VirtualHost 111.22.33.55>
    + # ¼­¹ö C
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # ¼­¹ö D
    + ...
    + </VirtualHost> +

    + <VirtualHost 111.22.33.44>
    + # ¼­¹ö A
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # ¼­¹ö C
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.44>
    + # ¼­¹ö B
    + ...
    + </VirtualHost>
    + <VirtualHost 111.22.33.55>
    + # ¼­¹ö D
    + ...
    + </VirtualHost>
    +
    + NameVirtualHost 111.22.33.44
    + NameVirtualHost 111.22.33.55
    +
    +

    + + +

    (¿ÞÂÊ ¼³Á¤ÀÌ ´õ Àбâ ÆíÇÏ´Ù.)

    + +

    VirtualHost Áö½Ã¾î¸¦ ÀÐÀ» ´ÙÀ½, °¡»óÈ£½ºÆ® + ¼­¹ö´Â VirtualHost Áö½Ã¾î¿¡ ÁöÁ¤ÇÑ Æ÷Æ®¸¦ ±âº» + ListenÀ¸·Î ÇÑ´Ù.

    + +

    VirtualHost Áö½Ã¾îÀÇ À̸§ÀÌ ¸ðµÎ °°Àº + ÁÖ¼ÒÁýÇÕ¿¡ ¼ÓÇÑ´Ù¸é ServerAlias¿Í °°ÀÌ Ãë±ÞÇÑ´Ù + (±×·¯³ª ´Ù¸¥ ServerAliasÀÇ ¿µÇâÀ» ¹ÞÁö ¾Ê´Â´Ù). + °¡»óÈ£½ºÆ®¿¡ Ãß°¡·Î »ç¿ëÇÑ ListenÀº ÁÖ¼ÒÁýÇÕÀÌ + ÁöÁ¤ÇÑ Æ÷Æ®¿¡ ¿µÇâÀ» ÁÖÁö ¾ÊÀ½À» ÁÖÀÇÇ϶ó.

    + +

    ½ÃÀÛÇÒ¶§ IP ÁÖ¼Ò ¸ñ·ÏÀ» ¸¸µé¾î Çؽ¬Å×ÀÌºí¿¡ Ãß°¡ÇÑ´Ù. + NameVirtualHost Áö½Ã¾î¿¡ IP ÁÖ¼Ò¸¦ »ç¿ëÇϸé + ¸ñ·ÏÀº ±× IP ÁÖ¼Ò¿¡ ´ëÇÑ ¸ðµç À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ Æ÷ÇÔÇÑ´Ù. + ±× ÁÖ¼Ò¿¡ ´ëÇÑ °¡»óÈ£½ºÆ®°¡ ¾ø´Ù¸é NameVirtualHost + Áö½Ã¾î¸¦ ¹«½ÃÇÏ°í ·Î±×¿¡ ¿À·ù¸¦ ±â·ÏÇÑ´Ù. IP±â¹Ý °¡»óÈ£½ºÆ®´Â + Çؽ¬Å×ÀÌºí¿¡ ¸ñ·ÏÀ» Ãß°¡ÇÏÁö ¾Ê´Â´Ù.

    + +

    ºü¸¥ Çؽ¬ÇÔ¼ö¸¦ »ç¿ëÇϱ⶧¹®¿¡ ¿äû½Ã IP ÁÖ¼Ò¸¦ ÇؽÌÇÏ´Â + ºÎ´ãÀº °ÅÀÇ ¾ø´Ù. ¶Ç Çؽ¬Å×À̺íÀº IP ÁÖ¼ÒÀÇ ¸¶Áö¸· ºÎºÐÀÇ + Â÷ÀÌ¿¡ ÃÖÀûÈ­µÇÀÖ´Ù.

    + +

    °¡»óÈ£½ºÆ®¿¡ ¿©·¯ ±âº»°ªÀÌ ¼³Á¤µÈ´Ù. ƯÈ÷:

    + +
      +
    1. °¡»óÈ£½ºÆ®¿¡ ServerAdmin, + ResourceConfig, + AccessConfig, + Timeout, + KeepAliveTimeout, + KeepAlive, + MaxKeepAliveRequests, + SendBufferSize + Áö½Ã¾î°¡ ¾ø´Ù¸é ÁÖ¼­¹ö¿¡¼­ ÇØ´ç °ªÀ» °¡Á®¿Â´Ù. (Áï, + ÁÖ¼­¹öÀÇ ¼³Á¤°ªÀ» »ç¿ëÇÑ´Ù.)
      2. + +
    2. °¡»óÈ£½ºÆ®ÀÇ µð·ºÅ丮 ±âº»±ÇÇÑÀ» Á¤ÀÇÇÏ´Â "ÂüÁ¶ + ±âº»°ª(lookup defaults)"Àº ÁÖ¼­¹öÀÇ ¼³Á¤°ú ÇÕÃÄÁø´Ù. + ¸ðµâÀÇ µð·ºÅ丮´ç ¼³Á¤(per-directory configuration)µµ + ¿©±â¿¡ ÇØ´çµÈ´Ù.
      3. + +
    3. °¢ ¸ðµâÀÇ ¼­¹ö´ç ¼³Á¤(per-server config)Àº ÁÖ¼­¹öÀÇ + ¼³Á¤°ú °¡»óÈ£½ºÆ®ÀÇ ¼³Á¤À» ÇÕÄ£´Ù.
      4. +
    + +

    ±âº»ÀûÀ¸·Î ÁÖ¼­¹ö´Â °¡»óÈ£½ºÆ®¸¦ ¸¸µå´Â "±âº»" ȤÀº "±â¹Ý"ÀÌ + µÈ´Ù. ±×·¯³ª ¼³Á¤ÆÄÀÏ¿¡¼­ ÁÖ¼­¹ö¸¦ Á¤ÀÇÇÏ´Â À§Ä¡´Â °ü°è¾ø´Ù. + ¸¶Áö¸·À¸·Î ¼³Á¤À» ÇÕÄ¡±â Àü¿¡ ÁÖ¼­¹öÀÇ ¸ðµç ¼³Á¤À» ÀоîµéÀδÙ. + ±×·¡¼­ ÁÖ¼­¹ö Á¤ÀÇ°¡ °¡»óÈ£½ºÆ® Á¤ÀÇ µÚ¿¡ ³ª¿Íµµ °¡»óÈ£½ºÆ® + Á¤ÀÇ¿¡ ¿µÇâÀ» ÁØ´Ù.

    + +

    ÁÖ¼­¹ö¿¡ ServerNameÀÌ ¾ø´Ù¸é À¥¼­¹ö¸¦ ½ÇÇàÇÏ´Â + ÄÄÇ»ÅÍÀÇ È£½ºÆ®¸íÀ» ´ë½Å »ç¿ëÇÑ´Ù. ÁÖ¼­¹öÀÇ + ServerNameÀ» DNS °Ì»öÇÏ¿© ¾òÀº IP ÁÖ¼ÒµéÀ» + ÁÖ¼­¹ö ÁÖ¼ÒÁýÇÕÀ̶ó°í ºÎ¸¥´Ù.

    + +

    À̸§±â¹Ý °¡»óÈ£½ºÆ®ÀÇ ServerNameÀ» Á¤ÀÇÇÏÁö + ¾ÊÀ¸¸é °¡»óÈ£½ºÆ®¸¦ Á¤ÀÇÇÏ´Â VirtualHost¿¡¼­ + óÀ½À¸·Î ³ª¿Â ÁÖ¼Ò¸¦ ±âº»°ªÀ¸·Î »ç¿ëÇÑ´Ù.

    + +

    Ưº°ÇÑ _default_ ¿ÍÀÏƮīµå¸¦ Æ÷ÇÔÇÏ´Â + °¡»óÈ£½ºÆ®´Â ÁÖ¼­¹ö¿Í °°Àº ServerNameÀ» °¡Áø´Ù.

    + +
    top
    +
    +

    °¡»óÈ£½ºÆ® ã±â

    + +

    ¼­¹ö´Â ¾Æ·¡¿Í °°Àº ¹æ¹ýÀ¸·Î ¾î¶² °¡»óÈ£½ºÆ®°¡ ¿äûÀ» + ó¸®ÇÒÁö °áÁ¤ÇÑ´Ù:

    + +

    Çؽ¬Å×À̺í ã±â

    + +

    Ŭ¶óÀ̾ðÆ®°¡ óÀ½ ¿¬°áÇÏ¸é ¿¬°áÇÑ IP ÁÖ¼Ò¸¦ ³»ºÎ IP + Çؽ¬Å×ÀÌºí¿¡¼­ ã´Â´Ù.

    + +

    IP ÁÖ¼Ò¸¦ ãÀ» ¼ö ¾ø°í Ŭ¶óÀ̾ðÆ®°¡ ¿äûÀ» º¸³½ Æ÷Æ®¿¡ + ÇØ´çÇÏ´Â °¡»óÈ£½ºÆ®°¡ ÀÖ´Ù¸é, _default_ °¡»óÈ£½ºÆ®°¡ + ¿äûÀ» ¼­ºñ½ºÇÑ´Ù. _default_ °¡»óÈ£½ºÆ®°¡ + ¾ø´Ù¸é ÁÖ¼­¹ö°¡ ¿äûÀ» ¼­ºñ½ºÇÑ´Ù.

    + +

    Çؽ¬Å×ÀÌºí¿¡ IP ÁÖ¼Ò°¡ ¾øÁö¸¸ Æ÷Æ® ¹øÈ£°¡ + NameVirtualHost *¿¡ ÇØ´çÇÒ ¼ö ÀÖ´Ù. ÀÌ °æ¿ì + À̸§±â¹Ý °¡»óÈ£½ºÆ®Ã³·³ ó¸®ÇÑ´Ù.

    + +

    ã¾Ò´Ù¸é (¸ñ·Ï¿¡¼­ IP ÁÖ¼Ò¿¡ ÇØ´çÇÏ´Â Ç׸ñÀ» ãÀ¸¸é), + IP±â¹Ý °¡»óÈ£½ºÆ®ÀÎÁö À̸§±â¹Ý °¡»óÈ£½ºÆ®ÀÎÁö °áÁ¤ÇÑ´Ù.

    + + + +

    IP±â¹Ý °¡»óÈ£½ºÆ®

    + +

    ãÀº Ç׸ñ¿¡ À̸§ ¸ñ·ÏÀÌ ¾ø´Ù¸é IP±â¹Ý °¡»óÈ£½ºÆ®ÀÌ´Ù. + ´õ ÀÌ»ó ÀÛ¾÷ÀÌ ÇÊ¿ä¾ø°í, ±× °¡»óÈ£½ºÆ®°¡ ¿äûÀ» ó¸®ÇÑ´Ù.

    + + + +

    À̸§±â¹Ý °¡»óÈ£½ºÆ®

    + +

    À̸§ ¸ñ·Ï¿¡ ÇÑ°³ ÀÌ»óÀÇ °¡»óÈ£½ºÆ® ±¸Á¶°¡ Æ÷ÇԵǸé + À̸§±â¹Ý °¡»óÈ£½ºÆ®ÀÌ´Ù. ÀÌ ¸ñ·Ï¿¡¼­ °¡»óÈ£½ºÆ®µéÀº ¼³Á¤ÆÄÀÏÀÇ + VirtualHost ¼ø¼­´ë·Î À§Ä¡ÇÑ´Ù.

    + +

    ¸ñ·Ï¿¡¼­ ù¹ø° °¡»óÈ£½ºÆ®(¼³Á¤ÆÄÀÏ¿¡¼­ ÇØ´ç IP ÁÖ¼Ò¸¦ + Æ÷ÇÔÇϴ ù¹ø° °¡»óÈ£½ºÆ®)´Â °¡Àå ³ôÀº ¿ì¼±¼øÀ§¸¦ °¡Áö¸ç, + ¼­¹ö¸íÀ» ¾Ë ¼ö ¾ø°Å³ª Host: Çì´õ°¡ ¾ø´Â ¿äûÀ» + ó¸®ÇÑ´Ù.

    + +

    Ŭ¶óÀ̾ðÆ®°¡ Host: Çì´õ¸¦ ÁÖ¸é, ¸ñ·Ï¿¡¼­ + ù¹ø°·Î ServerNameÀ̳ª + ServerAlias°¡ ´ëÀÀÇÏ´Â °¡»óÈ£½ºÆ®°¡ ¿äûÀ» + ¼­ºñ½ºÇÑ´Ù. Host: Çì´õ¿¡ Æ÷Æ® ¹øÈ£°¡ ³ª¿Ã ¼ö + ÀÖÁö¸¸, ¾ÆÆÄÄ¡´Â Ç×»ó Ŭ¶óÀ̾ðÆ®°¡ ¿äûÀ» º¸³½ ½ÇÁ¦ Æ÷Æ®¸¦ + ã´Â´Ù.

    + +

    Ŭ¶óÀ̾ðÆ®°¡ Host: Çì´õ¾øÀÌ HTTP/1.0 ¿äûÀ» + Çϸé Ŭ¶óÀ̾ðÆ®°¡ ¾î¶² ¼­¹ö¿¡ ¿¬°áÇÏ·Á´ÂÁö ¾Ë ¼ö ¾ø±â¶§¹®¿¡ + ¿äûÀÇ URI¿¡ ÇØ´çÇÏ´Â ServerPath°¡ ÀÖ´ÂÁö ã´Â´Ù. + ¸ñ·Ï¿¡¼­ Á¦ÀÏ ¸ÕÀú ãÀº °æ·Î¸¦ »ç¿ëÇÏ°í, ±× °¡»óÈ£½ºÆ®°¡ + ¿äûÀ» ¼­ºñ½ºÇÑ´Ù.

    + +

    ´ëÀÀÇÏ´Â °¡»óÈ£½ºÆ®¸¦ ãÀ» ¼ö ¾ø´Ù¸é, (ÀÌ¹Ì ¾Õ¿¡ ¸»ÇßµíÀÌ) + Ŭ¶óÀ̾ðÆ®°¡ ¿¬°áÇÑ IP¿¡ ´ëÇÑ ¸ñ·Ï¿¡¼­ ÀÏÄ¡ÇÏ´Â Æ÷Æ® ¹øÈ£¸¦ + Æ÷ÇÔÇϴ ù¹ø° °¡»óÈ£½ºÆ®°¡ ¿äûÀ» ¼­ºñ½ºÇÑ´Ù.

    + + + +

    Áö¼Ó ¿¬°á

    + +

    IP´Â À§¿¡¼­ ¼³¸íÇѵ¥·Î ƯÁ¤ TCP/IP ¼¼¼Ç´ç Çѹø¸¸ + ãÁö¸¸, À̸§Àº KeepAlive/Áö¼Ó ¿¬°áµ¿¾È ¸Å ¿äû¶§¸¶´Ù + ã´Â´Ù. Áï, Ŭ¶óÀ̾ðÆ®´Â Áö¼Ó ¿¬°áµ¿¾È ¿©·¯ À̸§±â¹Ý + °¡»óÈ£½ºÆ®ÀÇ ÆäÀÌÁö¸¦ ¿äûÇÒ ¼ö ÀÖ´Ù.

    + + + +

    Àý´ë URI

    + +

    ¿äûÀÇ URI°¡ Àý´ë URIÀÌ°í Ŭ¶óÀ̾ðÆ®°¡ º¸³½ ¿äûÀÇ + È£½ºÆ®¸í°ú Æ÷Æ®°¡ ÁÖ¼­¹ö³ª ƯÁ¤ °¡»óÈ£½ºÆ®¿¡ ÇØ´çÇϸé, + ±× ÁÖ¼­¹ö ȤÀº °¡»óÈ£½ºÆ®´Â URI ¾ÕÀÇ ½ºÅ´/È£½ºÆ®¸í/Æ÷Æ® + ºÎºÐÀ» Á¦¿ÜÇÑ ³ª¸ÓÁö »ó´ë URI¸¦ ¼­ºñ½ºÇÑ´Ù. ÇØ´çÇÏ´Â + ÁÖ¼­¹ö³ª °¡»óÈ£½ºÆ®°¡ ¾ø´Ù¸é URI¸¦ ±×´ë·Î µÎ°í ¿äûÀ» + ÇÁ·Ï½Ã ¿äûÀ¸·Î ó¸®ÇÑ´Ù.

    + + +

    ÁÖÀÇ

    + +
      +
    • À̸§±â¹Ý °¡»óÈ£½ºÆ®¿Í IP±â¹Ý °¡»óÈ£½ºÆ®´Â ¼­·Î¿¡°Ô + ¿µÇâÀ» ÁÖÁö ¾Ê´Â´Ù. IP±â¹Ý °¡»óÈ£½ºÆ®¸¦ ÀÚ½ÅÀÇ À̸§ÁýÇÕ + IP ÁÖ¼Ò¿Ü¿¡ ¾î¶² Áּҷεµ Á¢±ÙÇÒ ¼ö ¾ø´Ù. À̸§±â¹Ý + °¡»óÈ£½ºÆ®µµ ¸¶Âù°¡Áö´Ù. À̸§±â¹Ý °¡»óÈ£½ºÆ®´Â + NameVirtualHost Áö½Ã¾î·Î Á¤ÀÇÇÑ ÁÖ¼ÒÁýÇÕÀÇ + IP ÁÖ¼Ò¸¦ ÅëÇؼ­¸¸ Á¢±ÙÇÒ ¼ö ÀÖ´Ù.
      • + +
    • IP±â¹Ý °¡»óÈ£½ºÆ®´Â ServerAlias¿Í + ServerPath¸¦ Àý´ë·Î °Ë»çÇÏÁö ¾Ê´Â´Ù.
      • + +
    • ¼³Á¤ÆÄÀÏ¿¡¼­ À̸§±â¹Ý °¡»óÈ£½ºÆ®, IP±â¹Ý °¡»óÈ£½ºÆ®, + _default_ °¡»óÈ£½ºÆ®, NameVirtualHost + Áö½Ã¾îÀÇ ¼ø¼­´Â Áß¿äÇÏÁö ¾Ê´Ù. ƯÁ¤ ÁÖ¼ÒÁýÇÕ¿¡ ´ëÇÑ + À̸§±â¹Ý °¡»óÈ£½ºÆ®µéÀÇ ¼ø¼­¸¸ÀÌ Áß¿äÇÏ´Ù. ¼³Á¤ÆÄÀÏ¿¡¼­ + ¾Õ¿¡ ³ª¿À´Â À̸§±â¹Ý °¡»óÈ£½ºÆ®´Â ÀÚ½ÅÀÌ ¼ÓÇÑ ÁÖ¼ÒÁýÇÕ¿¡¼­ + °¡Àå ³ôÀº ¿ì¼±¼øÀ§¸¦ °¡Áø´Ù.
      • + +
    • º¸¾ÈÀ» À§ÇØ Host: Çì´õ¿¡ Æ÷ÇÔµÈ Æ÷Æ® + ¹øÈ£´Â Àý´ë·Î »ç¿ëÇÏÁö ¾Ê´Â´Ù. ¾ÆÆÄÄ¡´Â Ç×»ó Ŭ¶óÀ̾ðÆ®°¡ + ¿äûÀ» º¸³½ ½ÇÁ¦ Æ÷Æ®¸¦ »ç¿ëÇÑ´Ù.
      • + +
    • (µÑ »çÀ̸¦ ±¸º°ÇÒ Host: Çì´õ°¡ ¾ø´Ù°í + °¡Á¤Çϸé,) ServerPath Áö½Ã¾î°¡ ¼³Á¤ÆÄÀÏ¿¡¼­ + µÚ¿¡ ³ª¿À´Â ´Ù¸¥ ServerPath Áö½Ã¾îÀÇ ¾ÕºÎºÐÀ» + ÁöĪÇÏ´Â °æ¿ì Ç×»ó ¾Õ¿¡ ³ª¿Â Áö½Ã¾î¸¦ »ç¿ëÇÑ´Ù.
      • + +
    • µÎ IP±â¹Ý °¡»óÈ£½ºÆ®°¡ °°Àº ÁÖ¼Ò¸¦ °¡Áö¸é, Ç×»ó + ¼³Á¤ÆÄÀÏ¿¡¼­ ¾Õ¿¡ ³ª¿À´Â °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÑ´Ù. ÀÌ·± ÀÏÀº + ¾Æ¹«µµ ¸ð¸£°Ô ÀϾ ¼ö ÀÖ´Ù. ¼­¹ö°¡ ÀÌ·± »óȲÀ» ¹ß°ßÇϸé + ¿À·ù ·Î±×ÆÄÀÏ¿¡ °æ°í¸¦ ±â·ÏÇÑ´Ù.
      • + +
    • _default_ °¡»óÈ£½ºÆ®´Â ¿äûÀÇ IP ÁÖ¼Ò¿Í + Æ÷Æ® ¹øÈ£¿¡ ÇØ´çÇÏ´Â °¡»óÈ£½ºÆ®°¡ ¾øÀ»¶§¸¸ ¿äûÀ» ó¸®ÇÑ´Ù. + Ŭ¶óÀ̾ðÆ®°¡ ¿äûÀ» º¸³½ Æ÷Æ® ¹øÈ£°¡ _default_ + °¡»óÈ£½ºÆ®ÀÇ Æ÷Æ® ¹øÈ£(±âº»°ªÀº Listen)¿Í + °°À»¶§¸¸ ¿äûÀ» ó¸®ÇÑ´Ù. ¾î¶² Æ÷Æ®ÀÇ ¿äûÀÌ¶óµµ Àâ±âÀ§ÇØ + (¿¹¸¦ µé¾î, _default_:*) ¿ÍÀϵåÄ«µå + Æ÷Æ®¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù. NameVirtualHost * + °¡»óÈ£½ºÆ®µµ ¸¶Âù°¡Áö´Ù.
      • + +
    • ÁÖ¼­¹ö´Â Ŭ¶óÀ̾ðÆ®°¡ ¿¬°áÇÑ IP ÁÖ¼Ò¿Í Æ÷Æ® ¹øÈ£¿¡ + ÇØ´çÇÏ´Â (_default_ °¡»óÈ£½ºÆ®¸¦ Æ÷ÇÔÇÏ¿©) + °¡»óÈ£½ºÆ®°¡ ¾øÀ»¶§¸¸ ¿äûÀ» ¼­ºñ½ºÇÑ´Ù. Áï, ÁÖ¼­¹ö´Â + (±× Æ÷Æ®¿¡ ÇØ´çÇÏ´Â _default_ °¡»óÈ£½ºÆ®°¡ + ¾ø´Ù¸é) ÁöÁ¤ÇÏÁö¾ÊÀº ÁÖ¼Ò/Æ÷Æ® ½Ö¿¡ ´ëÇÑ ¿äû¸¸À» ó¸®ÇÑ´Ù.
      • + +
    • Ŭ¶óÀ̾ðÆ®°¡ (¿¹¸¦ µé¾î, NameVirtualHost + Áö½Ã¾î¿¡¼­) À̸§±â¹Ý °¡»óÈ£½ºÆ® ÁÖ¼Ò(¿Í Æ÷Æ®)¿¡ ¿¬°áÇÑ + °æ¿ì Host: Çì´õ¸¦ ¾Ë ¼ö ¾ø°Å³ª Çì´õ°¡ ¾ø´Â + ¿äûÀ» º¸³»¸é ¿äûÀº Àý´ë·Î _default_ + °¡»óÈ£½ºÆ®³ª ÁÖ¼­¹ö¿¡¼­ ó¸®ÇÏÁö ¾Ê´Â´Ù.
      • + +
    • ½ÃÀÛÇÒ¶§ ¼­¹ö°¡ DNS¸¦ ÀÇÁ¸ÇÏÁö ¾ÊÀ¸·Á¸é Àý´ë·Î + VirtualHost Áö½Ã¾î¿¡ DNS À̸§À» »ç¿ëÇÏÁö¸¶¶ó. + °Ô´Ù°¡ ¿­°ÅÇÑ ¸ðµç µµ¸ÞÀÎÀÇ DNS¸¦ ÅëÁ¦ÇÏÁö ¾Ê´Â´Ù¸é + º¸¾È»ó À§Çèµµ ÀÖ´Ù. ÀÌ¿¡ ´ëÇÑ Á¤º¸°¡ ÀÖ´Ù.
      • + +
    • °¢ °¡»óÈ£½ºÆ®¸¶´Ù ServerName¸¦ Ç×»ó + Á¤ÀÇÇØ¾ß ÇÑ´Ù. ¾È±×·¯¸é °¡»óÈ£½ºÆ®¸¶´Ù DNS¸¦ ã°Ô µÈ´Ù.
      • +
    + + +
    top
    +
    +

    ÆÁ

    + +

    DNS ¹®Á¦ ÆäÀÌÁöÀÇ + ÆÁ¿¡ Ãß°¡·Î ¾Æ·¡¿¡ ÆÁÀÌ ÀÖ´Ù:

    + +
      +
    • ¸ðµç ÁÖ¼­¹ö Á¤ÀǸ¦ VirtualHost Á¤ÀÇ ¾Õ¿¡ + µÎ¾î¶ó. (±×·¯¸é ¼³Á¤À» Àбâ ÆíÇÏ´Ù. ¾È±×·¯¸é ³ªÁß¿¡ ¼³Á¤ÀÌ + ÇÕÃÄÁú¶§ °¡»óÈ£½ºÆ®µé »çÀÌ¿¡ ¼¯ÀÎ Á¤ÀÇ°¡ ¸ðµç °¡»óÈ£½ºÆ®¿¡ + ¿µÇâÀ» ÁÙ ¼ö Àֱ⶧¹®¿¡ È¥¶õ½º·´´Ù.)
      • + +
    • Àбâ ÆíÇϵµ·Ï ¼³Á¤¿¡¼­ ÇØ´çÇÏ´Â NameVirtualHost°ú + VirtualHost Á¤ÀǵéÀ» ¹­¾î¶ó.
      • + +
    • ServerPath°¡ ´Ù¸¥ ServerPathÀÇ + ¾ÕºÎºÐÀ» ÁöĪÇÏ´Â °æ¿ì¸¦ ÇÇÇ϶ó. ÇÇÇÒ ¼ö ¾ø´Ù¸é ¼³Á¤ÆÄÀÏ¿¡¼­ + ¾ÕºÎºÐÀÌ ´õ ±ä (´õ ÀÚ¼¼ÇÑ) °¡»óÈ£½ºÆ®¸¦ ªÀº (´ú ÀÚ¼¼ÇÑ) + °¡»óÈ£½ºÆ®º¸´Ù ¾Õ¿¡ µÎ¾î¶ó. (¿¹¸¦ µé¾î, + "ServerPath /abc"´Â "ServerPath /abc/def" ´ÙÀ½¿¡ µÎ¾î¾ß + ÇÑ´Ù.
      • +
    + +
    +
    +

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

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/examples.html b/docs/manual/vhosts/examples.html new file mode 100644 index 00000000..0ed55e50 --- /dev/null +++ b/docs/manual/vhosts/examples.html @@ -0,0 +1,15 @@ +URI: examples.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: examples.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: examples.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: examples.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/vhosts/examples.html.en b/docs/manual/vhosts/examples.html.en new file mode 100644 index 00000000..b5e3729e --- /dev/null +++ b/docs/manual/vhosts/examples.html.en @@ -0,0 +1,660 @@ + + + +VirtualHost Examples - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    VirtualHost Examples

    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + + +

    This document attempts to answer the commonly-asked questions about + setting up virtual hosts. These scenarios are those involving multiple + web sites running on a single server, via name-based or IP-based virtual hosts. +

    + +
    + +
    top
    +
    +

    Running several name-based web + sites on a single IP address.

    + +

    Your server has a single IP address, and multiple aliases (CNAMES) + point to this machine in DNS. You want to run a web server for + www.example.com and www.example.org on this + machine.

    + +

    Note

    Creating virtual + host configurations on your Apache server does not magically + cause DNS entries to be created for those host names. You + must have the names in DNS, resolving to your IP + address, or nobody else will be able to see your web site. You + can put entries in your hosts file for local + testing, but that will work only from the machine with those + hosts entries.

    +
    + +

    Server configuration

    + + + # Ensure that Apache listens on port 80
    + Listen 80
    +
    + # Listen for virtual host requests on all IP addresses
    + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +
    + # Other directives here
    +
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +
    + # Other directives here
    +
    +     + </VirtualHost> +

    + +

    The asterisks match all addresses, so the main server serves no + requests. Due to the fact that www.example.com is first + in the configuration file, it has the highest priority and can be seen + as the default or primary server. That means + that if a request is received that does not match one of the specified + ServerName directives, it will be served by this first + VirtualHost.

    + +
    +

    Note

    + +

    You can, if you wish, replace * with the actual + IP address of the system. In that case, the argument to + VirtualHost must match the argument to + NameVirtualHost:

    + +

    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + # etc ... +

    + +

    However, it is additionally useful to use * + on systems where the IP address is not predictable - for + example if you have a dynamic IP address with your ISP, and + you are using some variety of dynamic DNS solution. Since + * matches any IP address, this configuration + would work without changes whenever your IP address + changes.

    +
    + +

    The above configuration is what you will want to use in almost + all name-based virtual hosting situations. The only thing that this + configuration will not work for, in fact, is when you are serving + different content based on differing IP addresses or ports.

    + +
    top
    +
    +

    Name-based hosts on more than one + IP address.

    + +
    +

    Note

    Any of the + techniques discussed here can be extended to any number of IP + addresses.

    +
    + +

    The server has two IP addresses. On one (172.20.30.40), we + will serve the "main" server, server.domain.com and on the + other (172.20.30.50), we will serve two or more virtual hosts.

    + +

    Server configuration

    + + + Listen 80
    +
    + # This is the "main" server running on 172.20.30.40
    + ServerName server.domain.com
    + DocumentRoot /www/mainserver
    +
    + # This is the other address
    + NameVirtualHost 172.20.30.50
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +
    + # Other directives here ...
    +
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +
    + # Other directives here ...
    +
    +     + </VirtualHost> +

    + +

    Any request to an address other than 172.20.30.50 will be + served from the main server. A request to 172.20.30.50 with an + unknown hostname, or no Host: header, will be served from + www.example.com.

    + +
    top
    +
    +

    Serving the same content on + different IP addresses (such as an internal and external + address).

    + +

    The server machine has two IP addresses (192.168.1.1 + and 172.20.30.40). The machine is sitting between an + internal (intranet) network and an external (internet) network. Outside + of the network, the name server.example.com resolves to + the external address (172.20.30.40), but inside the + network, that same name resolves to the internal address + (192.168.1.1).

    + +

    The server can be made to respond to internal and external requests + with the same content, with just one VirtualHost + section.

    + +

    Server configuration

    + + + NameVirtualHost 192.168.1.1
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 192.168.1.1 172.20.30.40>
    + + DocumentRoot /www/server1
    + ServerName server.example.com
    + ServerAlias server
    +     + </VirtualHost> +

    + +

    Now requests from both networks will be served from the same + VirtualHost.

    + +
    +

    Note:

    On the internal + network, one can just use the name server rather + than the fully qualified host name + server.example.com.

    + +

    Note also that, in the above example, you can replace the list + of IP addresses with *, which will cause the server to + respond the same on all addresses.

    +
    + +
    top
    +
    +

    Running different sites on different + ports.

    + +

    You have multiple domains going to the same IP and also want to + serve multiple ports. By defining the ports in the "NameVirtualHost" + tag, you can allow this to work. If you try using <VirtualHost + name:port> without the NameVirtualHost name:port or you try to use + the Listen directive, your configuration will not work.

    + +

    Server configuration

    + + + Listen 80
    + Listen 8080
    +
    + NameVirtualHost 172.20.30.40:80
    + NameVirtualHost 172.20.30.40:8080
    +
    + <VirtualHost 172.20.30.40:80>
    + + ServerName www.example.com
    + DocumentRoot /www/domain-80
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + ServerName www.example.com
    + DocumentRoot /www/domain-8080
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:80>
    + + ServerName www.example.org
    + DocumentRoot /www/otherdomain-80
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + ServerName www.example.org
    + DocumentRoot /www/otherdomain-8080
    +     + </VirtualHost> +

    + +
    top
    +
    +

    IP-based virtual hosting

    + +

    The server has two IP addresses (172.20.30.40 and + 172.20.30.50) which resolve to the names + www.example.com and www.example.org + respectively.

    + +

    Server configuration

    + + + Listen 80
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +     + </VirtualHost> +

    + +

    Requests for any address not specified in one of the + <VirtualHost> directives (such as + localhost, for example) will go to the main server, if + there is one.

    + +
    top
    +
    +

    Mixed port-based and ip-based virtual + hosts

    + +

    The server machine has two IP addresses (172.20.30.40 and + 172.20.30.50) which resolve to the names + www.example.com and www.example.org + respectively. In each case, we want to run hosts on ports 80 and + 8080.

    + +

    Server configuration

    + + + Listen 172.20.30.40:80
    + Listen 172.20.30.40:8080
    + Listen 172.20.30.50:80
    + Listen 172.20.30.50:8080
    +
    + <VirtualHost 172.20.30.40:80>
    + + DocumentRoot /www/example1-80
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + DocumentRoot /www/example1-8080
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50:80>
    + + DocumentRoot /www/example2-80
    + ServerName www.example.org
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50:8080>
    + + DocumentRoot /www/example2-8080
    + ServerName www.example.org
    +     + </VirtualHost> +

    + +
    top
    +
    +

    Mixed name-based and IP-based + vhosts

    + +

    On some of my addresses, I want to do name-based virtual hosts, and + on others, IP-based hosts.

    + +

    Server configuration

    + + + Listen 80
    +
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example3
    + ServerName www.example3.net
    +     + </VirtualHost>
    +
    + # IP-based
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example4
    + ServerName www.example4.edu
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.60>
    + + DocumentRoot /www/example5
    + ServerName www.example5.gov
    +     + </VirtualHost> +

    + +
    top
    +
    +

    Using Virtual_host and + mod_proxy together

    + +

    The following example allows a front-end machine to proxy a + virtual host through to a server running on another machine. In the + example, a virtual host of the same name is configured on a machine + at 192.168.111.2. The ProxyPreserveHost On directive is + used so that the desired hostname is passed through, in case we are + proxying multiple hostnames to a single machine.

    + +

    + <VirtualHost *:*>
    + ProxyPreserveHost On
    + ProxyPass / http://192.168.111.2
    + ProxyPassReverse / http://192.168.111.2/
    + ServerName hostname.example.com
    + </VirtualHost> +

    + +
    top
    +
    +

    Using _default_ + vhosts

    + +

    _default_ vhosts + for all ports

    + +

    Catching every request to any unspecified IP address and + port, i.e., an address/port combination that is not used for + any other virtual host.

    + +

    Server configuration

    + + + <VirtualHost _default_:*>
    + + DocumentRoot /www/default
    +     + </VirtualHost> +

    + +

    Using such a default vhost with a wildcard port effectively prevents + any request going to the main server.

    + +

    A default vhost never serves a request that was sent to an + address/port that is used for name-based vhosts. If the request + contained an unknown or no Host: header it is always + served from the primary name-based vhost (the vhost for that + address/port appearing first in the configuration file).

    + +

    You can use AliasMatch or + RewriteRule to rewrite any + request to a single information page (or script).

    + + +

    _default_ vhosts + for different ports

    + +

    Same as setup 1, but the server listens on several ports and we want + to use a second _default_ vhost for port 80.

    + +

    Server configuration

    + + + <VirtualHost _default_:80>
    + + DocumentRoot /www/default80
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost _default_:*>
    + + DocumentRoot /www/default
    + # ...
    +     + </VirtualHost> +

    + +

    The default vhost for port 80 (which must appear before any + default vhost with a wildcard port) catches all requests that were sent + to an unspecified IP address. The main server is never used to serve a + request.

    + + +

    _default_ vhosts + for one port

    + +

    We want to have a default vhost for port 80, but no other default + vhosts.

    + +

    Server configuration

    + + + <VirtualHost _default_:80>
    + DocumentRoot /www/default
    + ...
    + </VirtualHost> +

    + +

    A request to an unspecified address on port 80 is served from the + default vhost. Any other request to an unspecified address and port is + served from the main server.

    + + +
    top
    +
    +

    Migrating a name-based vhost to an + IP-based vhost

    + +

    The name-based vhost with the hostname + www.example.org (from our name-based example, setup 2) should get its own IP + address. To avoid problems with name servers or proxies who cached the + old IP address for the name-based vhost we want to provide both + variants during a migration phase.

    + +

    + The solution is easy, because we can simply add the new IP address + (172.20.30.50) to the VirtualHost + directive.

    + +

    Server configuration

    + + + Listen 80
    + ServerName www.example.com
    + DocumentRoot /www/example1
    +
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example3
    + ServerName www.example.net
    + ServerAlias *.example.net
    + # ...
    +     + </VirtualHost> +

    + +

    The vhost can now be accessed through the new address (as an + IP-based vhost) and through the old address (as a name-based + vhost).

    + +
    top
    +
    +

    Using the ServerPath + directive

    + +

    We have a server with two name-based vhosts. In order to match the + correct virtual host a client must send the correct Host: + header. Old HTTP/1.0 clients do not send such a header and Apache has + no clue what vhost the client tried to reach (and serves the request + from the primary vhost). To provide as much backward compatibility as + possible we create a primary vhost which returns a single page + containing links with an URL prefix to the name-based virtual + hosts.

    + +

    Server configuration

    + + + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + + # primary vhost
    + DocumentRoot /www/subdomain
    + RewriteEngine On
    + RewriteRule ^/.* /www/subdomain/index.html
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + DocumentRoot /www/subdomain/sub1
    + + ServerName www.sub1.domain.tld
    + ServerPath /sub1/
    + RewriteEngine On
    + RewriteRule ^(/sub1/.*) /www/subdomain$1
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/subdomain/sub2
    + ServerName www.sub2.domain.tld
    + ServerPath /sub2/
    + RewriteEngine On
    + RewriteRule ^(/sub2/.*) /www/subdomain$1
    + # ...
    +     + </VirtualHost> +

    + +

    Due to the ServerPath + directive a request to the URL + http://www.sub1.domain.tld/sub1/ is always served + from the sub1-vhost.
    A request to the URL + http://www.sub1.domain.tld/ is only + served from the sub1-vhost if the client sent a correct + Host: header. If no Host: header is sent the + client gets the information page from the primary host.

    + +

    Please note that there is one oddity: A request to + http://www.sub2.domain.tld/sub1/ is also served from the + sub1-vhost if the client sent no Host: header.

    + +

    The RewriteRule directives + are used to make sure that a client which sent a correct + Host: header can use both URL variants, i.e., + with or without URL prefix.

    + +
    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/examples.html.fr b/docs/manual/vhosts/examples.html.fr new file mode 100644 index 00000000..6c2cbc09 --- /dev/null +++ b/docs/manual/vhosts/examples.html.fr @@ -0,0 +1,679 @@ + + + +Exemples d'utilisations de VirtualHost - Serveur Apache HTTP + + + + +
    +

    Modules | Directives | FAQ | Glossaire | Plan du site

    +

    Serveur Apache HTTP Version 2.2

    +
    +
    <-
    +

    Exemples d'utilisations de VirtualHost

    +
    +

    Langues Disponibles:  en  | + fr  | + ja  | + ko 

    +
    + + +

    Le but de ce document est d'essayer de répondre aux questions + les plus répandues sur la configuration des serveurs virtuels. + Les scénarios présentés ici se rencontrent quand plusieurs + serveurs Webs doivent tourner sur une seule et même machine au + moyen de serveurs virtuels par nom + ou par IP.

    + +
    + +
    top
    +
    +

    Fonctionnement de plusieurs serveurs + virtuels par nom sur une seule adresse IP.

    + +

    Votre serveur ne dispose que d'une seule adresse IP, et de + nombreux alias (CNAMES) pointent vers cette adresse dans le DNS. + Pour l'exemple, www.example1.com et + www.example2.org doivent tourner sur cette machine.

    + +

    Note :

    La configuration de serveurs virtuels + sous Apache ne provoque pas leur apparition magique dans la + configuration du DNS. Il faut que leurs noms soient + définis dans le DNS, et qu'ils y soient résolus sur l'adresse IP + du serveur, faute de quoi personne ne pourra visiter votre site Web. + Il est possible d'ajouter des entrées dans le fichier + hosts pour tests locaux, mais qui ne fonctionneront + que sur la machine possédant ces entrées.

    +
    + +

    Configuration du serveur

    + + + # Apache doit écouter sur le port 80
    + Listen 80
    +
    + # Toutes les adresses IP doivent répondre aux requêtes sur les + # serveurs virtuels + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + DocumentRoot /www/example1
    + ServerName www.example1.com
    +
    + # Autres directives ici
    +
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + + DocumentRoot /www/example2
    + ServerName www.example2.org
    +
    + # Autres directives ici
    +
    +     + </VirtualHost> +

    + +

    Les astérisques correspondent à toutes les adresses, si bien que + le serveur principal ne répondra jamais à aucune requête. Comme + www.example1.com se trouve en premier dans le fichier + de configuration, il a la plus grande priorité et peut être vu + comme serveur par défaut ou primaire ; + ce qui signifie que toute requête reçue ne correspondant pas à une + des directives ServerName sera servie par ce premier + VirtualHost.

    + +
    +

    Note :

    + +

    Si vous le souhaitez, vous pouvez remplacer * + par l'adresse IP du système. Dans ce cas, l'argument de + VirtualHost doit correspondre à + l'argument de NameVirtualHost :

    + +

    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + # etc ... +

    + +

    En général, il est commode d'utiliser * sur + les systèmes dont l'adresse IP n'est pas constante - par + exemple, pour des serveurs dont l'adresse IP est attribuée + dynamiquement par le FAI, et où le DNS est géré au moyen + d'un DNS dynamique quelconque. Comme * signifie + n'importe quelle adresse, cette configuration + fonctionne sans devoir être modifiée quand l'adresse IP du + système est modifiée.

    +
    + +

    La configuration ci-dessus est en pratique utilisée dans la + plupart des cas pour les serveurs virtuels par nom. En fait, le + seul cas où cette configuration ne fonctionne pas est lorsque + différents contenus doivent être servis en fonction de l'adresse IP + et du port contactés par le client.

    + +
    top
    +
    +

    Serveurs virtuels par nom sur plus + d'une seule adresse IP.

    + +
    +

    Note :

    Toutes les techniques présentées ici + peuvent être étendues à un plus grand nombre d'adresses IP.

    +
    + +

    Le serveur a deux adresses IP. Sur l'une + (172.20.30.40), le serveur "principal" + server.domain.com doit répondre, et sur l'autre + (172.20.30.50), deux serveurs virtuels (ou plus) + répondront.

    + +

    Configuration du serveur

    + + + Listen 80
    +
    + # Serveur "principal" sur 172.20.30.40
    + ServerName server.domain.com
    + DocumentRoot /www/mainserver
    +
    + # l'autre adresse
    + NameVirtualHost 172.20.30.50
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example1
    + ServerName www.example1.com
    +
    + # D'autres directives ici ...
    +
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example2.org
    +
    + # D'autres directives ici ...
    +
    +     + </VirtualHost> +

    + +

    Toute requête arrivant sur une autre adresse que + 172.20.30.50 sera servie par le serveur principal. + Les requêtes vers 172.20.30.50 avec un nom de serveur + inconnu, ou sans en-tête Host:, seront servies par + www.example1.com.

    + +
    top
    +
    +

    Servir le même contenu sur des + adresses IP différentes (telle qu'une adresse interne et une + externe).

    + +

    La machine serveur dispose de deux adresses IP + (192.168.1.1 et 172.20.30.40). Cette + machine est placée à la fois sur le réseau interne (l'Intranet) + et le réseau externe (Internet). Sur Internet, le nom + server.example.com pointe vers l'adresse externe + (172.20.30.40), mais sur le réseau interne, ce même + nom pointe vers l'adresse interne (192.168.1.1).

    + +

    Le serveur peut être configuré pour répondre de la même manière + aux requêtes internes et externes, au moyen d'une seule section + VirtualHost.

    + +

    Configuration du serveur

    + + + NameVirtualHost 192.168.1.1
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 192.168.1.1 172.20.30.40>
    + + DocumentRoot /www/server1
    + ServerName server.example.com
    + ServerAlias server
    +     + </VirtualHost> +

    + +

    Ainsi, les requêtes en provenance de chacun des deux réseaux + seront servies par le même VirtualHost.

    + +
    +

    Note :

    Sur le réseau interne, il est possible + d'utiliser le nom raccourci server au lieu du nom + complet server.example.com.

    + +

    Notez également que dans l'exemple précédent, vous pouvez + remplacer la liste des adresses IP par des * afin + que le serveur réponde de la même manière sur toutes ses + adresses.

    +
    + +
    top
    +
    +

    Servir différents sites sur différents + ports.

    + +

    Vous disposez de plusieurs domaines pointant sur la même adresse + IP et vous voulez également servir de multiples ports. Vous y + parviendrez en définissant les ports dans la directive + "NameVirtualHost". Si vous tentez d'utiliser <VirtualHost + name:port> sans directive NameVirtualHost name:port, ou tentez + d'utiliser la directive Listen, votre configuration ne fonctionnera + pas.

    + +

    Configuration du serveur

    + + + Listen 80
    + Listen 8080
    +
    + NameVirtualHost 172.20.30.40:80
    + NameVirtualHost 172.20.30.40:8080
    +
    + <VirtualHost 172.20.30.40:80>
    + + ServerName www.example1.com
    + DocumentRoot /www/domain-80
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + ServerName www.example1.com
    + DocumentRoot /www/domain-8080
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:80>
    + + ServerName www.example2.org
    + DocumentRoot /www/otherdomain-80
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + ServerName www.example2.org
    + DocumentRoot /www/otherdomain-8080
    +     + </VirtualHost> +

    + +
    top
    +
    +

    Hébergement virtuel basé sur IP

    + +

    Le serveur dispose de deux adresses IP (172.20.30.40 + et 172.20.30.50) correspondant respectivement aux noms + www.example1.com et www.example2.org.

    + +

    Configuration du serveur

    + + + Listen 80
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example1
    + ServerName www.example1.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example2.org
    +     + </VirtualHost> +

    + +

    Les requêtes provenant d'adresses non spécifiées dans l'une des + directives <VirtualHost> (comme pour + localhost par exemple) seront dirigées vers le serveur + principal, s'il en existe un.

    + +
    top
    +
    +

    Hébergements virtuels mixtes basés sur + les ports et sur les IP

    + +

    Le serveur dispose de deux adresses IP (172.20.30.40 + et 172.20.30.50) correspondant respectivement aux noms + www.example1.com et www.example2.org. + Pour chacun d'eux, nous voulons un hébergement sur les ports 80 + et 8080.

    + +

    Configuration du serveur

    + + + Listen 172.20.30.40:80
    + Listen 172.20.30.40:8080
    + Listen 172.20.30.50:80
    + Listen 172.20.30.50:8080
    +
    + <VirtualHost 172.20.30.40:80>
    + + DocumentRoot /www/example1-80
    + ServerName www.example1.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + DocumentRoot /www/example1-8080
    + ServerName www.example1.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50:80>
    + + DocumentRoot /www/example2-80
    + ServerName www.example1.org
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50:8080>
    + + DocumentRoot /www/example2-8080
    + ServerName www.example2.org
    +     + </VirtualHost> +

    + +
    top
    +
    +

    Hébergements virtuels mixtes basé sur + les noms et sur IP

    + +

    Pour certaines adresses, des serveurs virtuels seront définis + par nom, et pour d'autres, ils seront définis par IP.

    + +

    Configuration du serveur

    + + + Listen 80
    +
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example1
    + ServerName www.example1.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example2
    + ServerName www.example2.org
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example3
    + ServerName www.example3.net
    +     + </VirtualHost>
    +
    + # "par-IP"
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example4
    + ServerName www.example4.edu
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.60>
    + + DocumentRoot /www/example5
    + ServerName www.example5.gov
    +     + </VirtualHost> +

    + +
    top
    +
    +

    Utilisation simultanée de + Virtual_host et de mod_proxy

    + +

    L'exemple suivant montre comment une machine peut mandater + un serveur virtuel fonctionnant sur le serveur d'une autre machine. + Dans cet exemple, un serveur virtuel de même nom est configuré sur + une machine à l'adresse 192.168.111.2. La directive + ProxyPreserveHost On est + employée pour permette au nom de domaine d'être préservé lors du + transfert, au cas où plusieurs noms de domaines cohabitent sur + une même machine.

    + +

    + <VirtualHost *:*>
    + ProxyPreserveHost On
    + ProxyPass / http://192.168.111.2
    + ProxyPassReverse / http://192.168.111.2/
    + ServerName hostname.example.com
    + </VirtualHost> +

    + +
    top
    +
    +

    Utilisation de serveurs virtuels + _default_

    + +

    Serveurs virtuels + _default_ pour tous les ports

    + +

    Exemple de capture de toutes les requêtes émanant + d'adresses IP ou de ports non connus, c'est-à-dire, d'un + couple adresse/port non traité par aucun autre serveur virtuel.

    + +

    Configuration du serveur

    + + + <VirtualHost _default_:*>
    + + DocumentRoot /www/default
    +     + </VirtualHost> +

    + +

    L'utilisation d'un tel serveur virtuel avec un joker pour le + port empêche de manière efficace qu'une requête n'atteigne le + serveur principal.

    + +

    Un serveur virtuel par défaut ne servira jamais une requête + qui est envoyée vers un couple adresse/port utilisée par un + serveur virtuel par nom. Si la requête contient un en-tête + Host: inconnu, ou si celui-ci est absent, elle + sera toujours servie par le serveur virtuel primaire par nom + (celui correspondant à ce couple adresse/port trouvé en premier + dans le fichier de configuration).

    + +

    Vous pouvez utiliser une directive + AliasMatch ou + RewriteRule afin de + réécrire une requête pour une unique page d'information (ou pour + un script).

    + + +

    Serveurs virtuels + _default_ pour des ports différents

    + +

    La configuration est similaire à l'exemple précédent, mais + le serveur écoute sur plusieurs ports et un second serveur virtuel + _default_ pour le port 80 est ajouté.

    + +

    Configuration du serveur

    + + + <VirtualHost _default_:80>
    + + DocumentRoot /www/default80
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost _default_:*>
    + + DocumentRoot /www/default
    + # ...
    +     + </VirtualHost> +

    + +

    Le serveur virtuel par défaut défini pour le port 80 (il doit + impérativement être placé avant un autre serveur virtuel par + défaut traitant tous les ports grâce au joker *) capture toutes + les requêtes envoyées sur une adresse IP non spécifiée. Le + serveur principal n'est jamais utilisé pour servir une requête.

    + + +

    Serveurs virtuels + _default_ pour un seul port

    + +

    Nous voulons créer un serveur virtuel par défaut seulement + pour le port 80.

    + +

    Configuration du serveur

    + + + <VirtualHost _default_:80>
    + DocumentRoot /www/default
    + ...
    + </VirtualHost> +

    + +

    Une requête vers une adresse non spécifiée sur le port 80 + sera servie par le serveur virtuel par défaut, et toute autre + requête vers une adresse et un port non spécifiés sera servie + par le serveur principal.

    + + +
    top
    +
    +

    Migration d'un serveur virtuel + par nom en un serveur virtuel par IP

    + +

    Le serveur virtuel par nom avec le nom de domaine + www.example2.org (de notre exemple + par nom) devrait obtenir sa propre adresse IP. Pendant la + phase de migration, il est possible d'éviter les problèmes avec + les noms de serveurs et autres serveurs mandataires qui mémorisent + les vielles adresses IP pour les serveurs virtuels par nom.
    + La solution est simple, car il suffit d'ajouter la nouvelle + adresse IP (172.20.30.50) dans la directive + VirtualHost.

    + +

    Configuration du serveur

    + + + Listen 80
    + ServerName www.example1.com
    + DocumentRoot /www/example1
    +
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example2.org
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example3
    + ServerName www.example3.net
    + ServerAlias *.example3.net
    + # ...
    +     + </VirtualHost> +

    + +

    Le serveur virtuel peut maintenant être joint par la nouvelle + adresse (comme un serveur virtuel par IP) et par l'ancienne + adresse (comme un serveur virtuel par nom).

    + +
    top
    +
    +

    Utilisation de la directive + ServerPath

    + +

    Dans le cas où vous disposez de deux serveurs virtuels par nom, + le client doit transmettre un en-tête Host: correct + pour déterminer le serveur concerné. Les vieux clients HTTP/1.0 + n'envoient pas un tel en-tête et Apache n'a aucun indice pour + connaître le serveur virtuel devant être joint (il sert la + requête à partir d'un serveur virtuel primaire). Dans un soucis + de préserver la compatibilité descendante, il suffit de créer + un serveur virtuel primaire chargé de retourner une page contenant + des liens dont les URLs auront un préfixe identifiant les serveurs + virtuels par nom.

    + +

    Configuration du serveur

    + + + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + + # Serveur virtuel primaire
    + DocumentRoot /www/subdomain
    + RewriteEngine On
    + RewriteRule ^/.* /www/subdomain/index.html
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + DocumentRoot /www/subdomain/sub1
    + + ServerName www.sub1.domain.tld
    + ServerPath /sub1/
    + RewriteEngine On
    + RewriteRule ^(/sub1/.*) /www/subdomain$1
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/subdomain/sub2
    + ServerName www.sub2.domain.tld
    + ServerPath /sub2/
    + RewriteEngine On
    + RewriteRule ^(/sub2/.*) /www/subdomain$1
    + # ...
    +     + </VirtualHost> +

    + +

    À cause de la directive + ServerPath, une requête sur + une URL http://www.sub1.domain.tld/sub1/ est + toujours servie par le serveur sub1-vhost.
    + Une requête sur une URL http://www.sub1.domain.tld/ n'est + servie par le serveur sub1-vhost que si le client envoie un en-tête + Host: correct. Si aucun en-tête Host: + n'est transmis, le serveur primaire sera utilisé.
    + Notez qu'il y a une singularité : une requête sur + http://www.sub2.domain.tld/sub1/ est également servie + par le serveur sub1-vhost si le client n'envoie pas d'en-tête + Host:.
    + Les directives RewriteRule + sont employées pour s'assurer que le client qui envoie un en-tête + Host: correct puisse utiliser d'autres variantes d'URLs, + c'est-à-dire avec ou sans préfixe d'URL.

    + +
    +
    +

    Langues Disponibles:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/examples.html.ja.euc-jp b/docs/manual/vhosts/examples.html.ja.euc-jp new file mode 100644 index 00000000..a162ee25 --- /dev/null +++ b/docs/manual/vhosts/examples.html.ja.euc-jp @@ -0,0 +1,648 @@ + + + +¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÎã - Apache HTTP ¥µ¡¼¥Ð + + + + +
    +

    ¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

    +

    Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

    +
    +
    <-
    +

    ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÎã

    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + + +

    ¤³¤Îʸ½ñ¤Ï¡¢¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÀßÄê¤ÎºÝ¤Ë + ¤è¤¯¤¢¤ë¼ÁÌä¤ËÅú¤¨¤ë¤â¤Î¤Ç¤¹¡£ÁÛÄꤷ¤Æ¤¤¤ëÂÐ¾Ý¤Ï Ì¾Á°¥Ù¡¼¥¹ ¤ä IP ¥Ù¡¼¥¹ ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò»È¤Ã¤Æ + °ì¤Ä¤Î¥µ¡¼¥Ð¤ÇÊ£¿ô¤Î¥¦¥§¥Ö¥µ¥¤¥È¤ò±¿ÍѤ·¤Æ¤¤¤ë¾õ¶·¤Ç¤¹¡£ +

    + +
    + +
    top
    +
    +

    °ì¤Ä¤Î IP ¥¢¥É¥ì¥¹¤Ç¤¤¤¯¤Ä¤«¤Î̾Á°¥Ù¡¼¥¹¤Î + ¥¦¥§¥Ö¥µ¥¤¥È¤ò¼Â¹Ô¤¹¤ë

    + +

    ¥µ¡¼¥Ð¤Ï IP ¥¢¥É¥ì¥¹¤ò°ì¤Ä³ä¤êÅö¤Æ¤é¤ì¤Æ¤¤¤Æ¡¢DNS ¤Ç¥Þ¥·¥ó¤Ë + Ê£¿ô¤Î̾Á° (CNAME) ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥Þ¥·¥ó¤Ç + www.example.com ¤È www.example.org + ¤Î¤¿¤á¤Î¥¦¥§¥Ö¥µ¡¼¥Ð¤ò¼Â¹Ô¤µ¤»¤¿¤¤¤È¤·¤Þ¤¹¡£

    + +

    Ãí

    + Apache ¥µ¡¼¥Ð¤ÎÀßÄê¤Ç¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÀßÄê¤ò¤·¤¿¤À¤±¤Ç¡¢ + ÃΤé¤Ê¤¤´Ö¤Ë¤½¤Î¥Û¥¹¥È̾¤ËÂбþ¤¹¤ë DNS ¤Î¥¨¥ó¥È¥ê¤¬ + ºîÀ®¤µ¤ì¤¿¤ê¤Ï¤·¤Þ¤»¤ó¡£¤½¤Î¥µ¡¼¥Ð¤Î IP ¥¢¥É¥ì¥¹¤Ë²ò·è¤µ¤ì¤ë + ¤è¤¦¤Ë DNS ¤Ë̾Á°¤òÅÐÏ¿¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤½¤¦¤Ç¤Ê¤¤¤Èï¤â¤¢¤Ê¤¿¤Î¥¦¥§¥Ö¥µ¥¤¥È¤ò¸«¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£ + ¥í¡¼¥«¥ë¤Ç¤Î¥Æ¥¹¥È¤Î¤¿¤á¤Ë hosts ¥Õ¥¡¥¤¥ë¤Ë + ¥¨¥ó¥È¥ê¤òÄɲ乤뤳¤È¤â¤Ç¤­¤Þ¤¹¤¬¡¢¤³¤Î¾ì¹ç¤Ï¤½¤Î + hosts ¥¨¥ó¥È¥ê¤Î¤¢¤ë¥Þ¥·¥ó¤«¤é¤·¤«Æ°ºî¤·¤Þ¤»¤ó¡£

    +
    + +

    ¥µ¡¼¥ÐÀßÄê

    + + + # Ensure that Apache listens on port 80
    + Listen 80
    +
    + # Listen for virtual host requests on all IP addresses
    + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +
    + # Other directives here
    +
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +
    + # Other directives here
    +
    +     + </VirtualHost> +

    + +

    ¥¢¥¹¥¿¥ê¥¹¥¯¤Ï¤¹¤Ù¤Æ¤Î¥¢¥É¥ì¥¹¤Ë¥Þ¥Ã¥Á¤·¤Þ¤¹¤Î¤Ç¡¢¼ç¥µ¡¼¥Ð¤Ï + ¥ê¥¯¥¨¥¹¥È¤ò°·¤¤¤Þ¤»¤ó¡£www.example.com ¤Ï + ºÇ½é¤Ë¤¢¤ë¤¿¤á¡¢Í¥Àè½ç°Ì¤Ï°ìÈֹ⤯¤Ê¤ê¡¢default ¤â¤·¤¯¤Ï + primary ¤Î¥µ¡¼¥Ð¤È¹Í¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤Ä¤Þ¤ê¡¢¥ê¥¯¥¨¥¹¥È¤¬ + ¤É¤Î ServerName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤â¥Þ¥Ã¥Á¤·¤Ê¤¤¾ì¹ç¡¢ + °ìÈֺǽé¤Î VirtualHost ¤Ë¤è¤ê°·¤ï¤ì¤Þ¤¹¡£

    + +

    Ãí

    + +

    * ¤ò¥·¥¹¥Æ¥à¤Î¼ÂºÝ¤Î IP ¥¢¥É¥ì¥¹¤ËÃÖ¤­´¹¤¨¤ë + ¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤½¤Î¾ì¹ç¤Ï VirtualHost ¤Î°ú¿ô¤Ï + NameVirtualHost ¤Î°ú¿ô¤ÈƱ¤¸¤Ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó + :

    + +

    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + # etc ... +

    + +

    ¤·¤«¤·¡¢IP ¥¢¥É¥ì¥¹¤¬Í½Â¬ÉÔ²Äǽ¤Ê¥·¥¹¥Æ¥à + ¡½¡½Î㤨¤Ð¥×¥í¥Ð¥¤¥À¤«¤éưŪ¤Ë IP ¥¢¥É¥ì¥¹¤ò¼èÆÀ¤·¤Æ²¿¤é¤«¤Î + ¥À¥¤¥Ê¥ß¥Ã¥¯ DNS ¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ê¤É¡½¡½¤Ë¤ª¤¤¤Æ¤Ï¡¢* + »ØÄê¤Ï¤µ¤é¤ËÊØÍø¤Ç¤¹¡£* ¤Ï¤¹¤Ù¤Æ¤Î IP ¥¢¥É¥ì¥¹¤Ë + ¥Þ¥Ã¥Á¤·¤Þ¤¹¤Î¤Ç¡¢¤³¤ÎÀßÄê¤Ë¤·¤Æ¤ª¤±¤Ð IP ¥¢¥É¥ì¥¹¤¬Êѹ¹¤µ¤ì¤Æ¤â + ÀßÄêÊѹ¹¤»¤º¤ËÆ°ºî¤·¤Þ¤¹¡£

    +
    + +

    ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥Æ¥£¥ó¥°¤Ç¤Ï¤Û¤Ü¤¹¤Ù¤Æ¤Î¾õ¶·¤Ç¡¢ + ¾åµ­¤ÎÀßÄê¤Ç´õ˾¤ÎÀßÄê¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤Ç¤·¤ç¤¦¡£ + ¼ÂºÝ¤³¤ÎÀßÄ꤬ưºî¤·¤Ê¤¤¤Î¤Ï¡¢IP ¥¢¥É¥ì¥¹¤ä¥Ý¡¼¥È¤Î°ã¤¤¤Ë¤è¤Ã¤Æ + °ã¤¦¥³¥ó¥Æ¥ó¥Ä¤òÁ÷¤ë¤È¤­¤À¤±¤Ç¤¹¡£

    + +
    top
    +
    +

    Ê£¿ô¤Î IP ¥¢¥É¥ì¥¹¤Î¤¢¤ë¥Û¥¹¥È¤Ç̾Á°¥Ù¡¼¥¹¤Î + ¥Û¥¹¥Æ¥£¥ó¥°¤ò¹Ô¤Ê¤¦

    + +
    +

    Ãí

    ¤³¤³¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ëÊýË¡¤Ï IP ¥¢¥É¥ì¥¹¤¬ + ²¿¸Ä¤¢¤Ã¤Æ¤âƱÍͤˤǤ­¤Þ¤¹¡£

    +
    + +

    ¥µ¡¼¥Ð¤Ë¤ÏÆó¤Ä IP ¥¢¥É¥ì¥¹¤¬¤Ä¤¤¤Æ¤¤¤Þ¤¹¡£°ì¤ÄÌÜ + (172.20.30.40) ¤Ç¤Ï¼ç¥µ¡¼¥Ð + server.domain.com ¤ò°·¤¤¡¢¤â¤¦°ìÊý + (172.20.30.50) ¤Ç¤ÏÆó¤Ä¤«¤½¤ì°Ê¾å¤Î¿ô¤Î + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò°·¤¤¤Þ¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + Listen 80
    +
    + # This is the "main" server running on 172.20.30.40
    + ServerName server.domain.com
    + DocumentRoot /www/mainserver
    +
    + # This is the other address
    + NameVirtualHost 172.20.30.50
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +
    + # Other directives here ...
    +
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +
    + # Other directives here ...
    +
    +     + </VirtualHost> +

    + +

    172.20.30.50 °Ê³°¤Î¥¢¥É¥ì¥¹¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï¼ç¥µ¡¼¥Ð + ¤¬°·¤¤¤Þ¤¹¡£172.20.30.50 ¤Ø¤Î¡¢Ì¤ÃΤΥۥ¹¥È̾¤Þ¤¿¤Ï + Host: ¥Ø¥Ã¥À¤Ê¤·¤Î¥ê¥¯¥¨¥¹¥È¤Ï www.example.com + ¤¬°·¤¤¤Þ¤¹¡£

    + +
    top
    +
    +

    °ã¤¦ IP ¥¢¥É¥ì¥¹ (Î㤨¤Ð¡¢ÆâÉô¤È³°Éô¥¢¥É¥ì¥¹) + ¤ÇƱ¤¸¥³¥ó¥Æ¥ó¥Ä¤òÁ÷¤ë

    + +

    ¥µ¡¼¥Ð¥Þ¥·¥ó¤Ï IP ¥¢¥É¥ì¥¹¤òÆó¤Ä (192.168.1.1 + ¤È 172.20.30.40) »ý¤Ã¤Æ¤¤¤Þ¤¹¡£¤³¤Î¥Þ¥·¥ó¤ÏÆâÉô + (¥¤¥ó¥È¥é¥Í¥Ã¥È) ¤È ³°Éô (¥¤¥ó¥¿¡¼¥Í¥Ã¥È) ¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤Î´Ö¤Ë + ¤¢¤ê¤Þ¤¹¡£server.example.com ¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¤Î³°¤«¤é¤Ï + ³°Éô¥¢¥É¥ì¥¹ (172.20.30.40) ¤È¤·¤Æ²ò·è¤µ¤ì¤Þ¤¹¤¬¡¢ + ¥Í¥Ã¥È¥ï¡¼¥¯¤ÎÃ椫¤é¤ÏÆâÉô¥¢¥É¥ì¥¹ (192.168.1.1) + ¤È¤·¤Æ²ò·è¤µ¤ì¤Þ¤¹¡£

    + +

    VirtualHost °ì¤Ä¤À¤±¤Ç¥µ¡¼¥Ð¤¬ÆâÉô¤Î¥ê¥¯¥¨¥¹¥È¤È + ³°Éô¤Î¥ê¥¯¥¨¥¹¥È¤ÎξÊý¤ËƱ¤¸¥³¥ó¥Æ¥ó¥Ä¤Ç±þÅú¤¹¤ë¤è¤¦¤Ë¤Ç¤­¤Þ¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + NameVirtualHost 192.168.1.1
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 192.168.1.1 172.20.30.40>
    + + DocumentRoot /www/server1
    + ServerName server.example.com
    + ServerAlias server
    +     + </VirtualHost> +

    + +

    ¤³¤ì¤Ç¤É¤Á¤é¤Î¥Í¥Ã¥È¥ï¡¼¥¯¤«¤é¤Î¥ê¥¯¥¨¥¹¥È¤âƱ¤¸ VirtualHost + ¤Ç°·¤ï¤ì¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£

    + +

    Ãí:

    ÆâÉô¥Í¥Ã¥È¥ï¡¼¥¯¤Ç¤Ï´°Á´¤Ê¥Û¥¹¥È̾¤Î + server.example.com ¤ÎÂå¤ï¤ê¤Ë¡¢Ã±¤Ë server + ¤ò»È¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    + +

    ¾å¤ÎÎã¤Ç¤Ï¡¢IP ¥¢¥É¥ì¥¹¤Î¥ê¥¹¥È¤ò¡¢¤¹¤Ù¤Æ¤Î¥¢¥É¥ì¥¹¤Ë + Ʊ¤¸¥³¥ó¥Æ¥ó¥Ä¤Ç±þÅú¤¹¤ë * ¤ËÃÖ¤­´¹¤¨¤é¤ì¤Þ¤¹¡£

    +
    + +
    top
    +
    +

    °ã¤¦¥Ý¡¼¥È¤Ç°ã¤¦¥µ¥¤¥È¤ò±¿±Ä¤¹¤ë

    + +

    Ʊ¤¸ IP ¤ËÊ£¿ô¤Î¥É¥á¥¤¥ó¤¬¤¢¤ê¡¢¤µ¤é¤ËÊ£¿ô¤Î¥Ý¡¼¥È¤ò»È¤Ã¤Æ + ¥ê¥¯¥¨¥¹¥È¤ò°·¤¤¤¿¤¤¤È¤­¤¬¤¢¤ê¤Þ¤¹¡£"NameVirtualHost" ¥¿¥°¤ÎÃæ¤Ç + ¥Ý¡¼¥È¤òÄêµÁ¤¹¤ë¤³¤È¤Ç¡¢¤³¤ì¤òÆ°ºî¤µ¤»¤é¤ì¤Þ¤¹¡£ + NameVirtualHost name:port ̵¤·¤ä Listen ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + <VirtualHost name:port> ¤ò»È¤ª¤¦¤È¤·¤Æ¤â¡¢¤½¤ÎÀßÄê¤ÏÆ°ºî¤·¤Þ¤»¤ó¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + Listen 80
    + Listen 8080
    +
    + NameVirtualHost 172.20.30.40:80
    + NameVirtualHost 172.20.30.40:8080
    +
    + <VirtualHost 172.20.30.40:80>
    + + ServerName www.example.com
    + DocumentRoot /www/domain-80
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + ServerName www.example.com
    + DocumentRoot /www/domain-8080
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:80>
    + + ServerName www.example.org
    + DocumentRoot /www/otherdomain-80
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + ServerName www.example.org
    + DocumentRoot /www/otherdomain-8080
    +     + </VirtualHost> +

    + +
    top
    +
    +

    IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥Æ¥£¥ó¥°

    + +

    ¥µ¡¼¥Ð¤Ï www.example.com ¤È www.example.org + ¤Ë¤½¤ì¤¾¤ì²ò·è¤µ¤ì¤ë¡¢Æó¤Ä¤Î IP ¥¢¥É¥ì¥¹ (172.20.30.40 ¤È + 172.20.30.50) ¤¬¤¢¤ê¤Þ¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + Listen 80
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +     + </VirtualHost> +

    + +

    <VirtualHost> ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î¤É¤ì¤Ç¤â + »ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¥¢¥É¥ì¥¹ (Î㤨¤Ð localhost) ¤Ï¡¢ + ¼ç¥µ¡¼¥Ð¤¬¤¢¤ì¤Ð¤½¤³¤Ë¹Ô¤­¤Þ¤¹¡£

    + +
    top
    +
    +

    ¥Ý¡¼¥È¥Ù¡¼¥¹¤È IP ¥Ù¡¼¥¹¤Îº®¤¶¤Ã¤¿ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È

    + +

    ¥µ¡¼¥Ð¥Þ¥·¥ó¤Ï¤½¤ì¤¾¤ì www.example.com ¤È + www.example.org ¤Ë¤½¤ì¤¾¤ì²ò·è¤µ¤ì¤ë¡¢IP ¥¢¥É¥ì¥¹¤òÆó¤Ä + (172.20.30.40 ¤È 172.20.30.50) »ý¤Ã¤Æ¤¤¤Þ¤¹¡£ + ¤É¤Á¤é¤â¥Ý¡¼¥È 80 ¤È 8080 ¤Ç¥Û¥¹¥È¤òÁö¤é¤»¤Þ¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + Listen 172.20.30.40:80
    + Listen 172.20.30.40:8080
    + Listen 172.20.30.50:80
    + Listen 172.20.30.50:8080
    +
    + <VirtualHost 172.20.30.40:80>
    + + DocumentRoot /www/example1-80
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + DocumentRoot /www/example1-8080
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50:80>
    + + DocumentRoot /www/example2-80
    + ServerName www.example.org
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50:8080>
    + + DocumentRoot /www/example2-8080
    + ServerName www.example.org
    +     + </VirtualHost> +

    + +
    top
    +
    +

    ̾Á°¥Ù¡¼¥¹¤È IP ¥Ù¡¼¥¹¤òº®¤¼¤¿ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È

    + +

    ¤¤¤¯¤Ä¤«¤Î¥Þ¥·¥ó¤Ç¤Ï̾Á°¥Ù¡¼¥¹¤Î¡¢¤½¤Î¾¤Ç¤Ï IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë + ¥Û¥¹¥È¤ò¤·¤Þ¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + Listen 80
    +
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example3
    + ServerName www.example3.net
    +     + </VirtualHost>
    +
    + # IP-based
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example4
    + ServerName www.example4.edu
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.60>
    + + DocumentRoot /www/example5
    + ServerName www.example5.gov
    +     + </VirtualHost> +

    + +
    top
    +
    +

    Virtual_host ¤È + mod_proxy ¤òÊ»ÍѤ¹¤ë

    + +

    ¼¡¤ÎÎã¤Ï¡¢¥Õ¥í¥ó¥È¦¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ç¾¤Î¥Þ¥·¥ó¤Ø¥×¥í¥¯¥·¤·¤Þ¤¹¡£ + Îã¤Ç¤Ï 192.168.111.2 ¤Î¥Þ¥·¥ó¤Ç¤Ï¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È̾¤Ï + Ʊ¤¸Ì¾Á°¤ÇÀßÄꤵ¤ì¤Æ¤¤¤Þ¤¹¡£Ê£¿ô¤Î¥Û¥¹¥È̾¤ò°ìÂæ¤Î¥Þ¥·¥ó¤Ë¥×¥í¥¯¥·¤¹¤ë + ¾ì¹ç¤Ï¡¢ProxyPreserveHost On + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¡¢´õ˾¤Î¥Û¥¹¥È̾¤òÅϤ»¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£ +

    + +

    + <VirtualHost *:*>
    + ProxyPreserveHost On
    + ProxyPass / http://192.168.111.2
    + ProxyPassReverse / http://192.168.111.2/
    + ServerName hostname.example.com
    + </VirtualHost> +

    + +
    top
    +
    +

    _default_ ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò + »È¤¦

    + +

    ¤¹¤Ù¤Æ¤Î¥Ý¡¼¥È¤ËÂФ¹¤ë + _default_ ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È

    + +

    ̤»ØÄê¤Î IP ¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¡¢¤Ä¤Þ¤ê¾¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë + »È¤ï¤ì¤Æ¤¤¤Ê¤¤¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ÎÁȤ߹ç¤ï¤»¡¢¤Ø¤Î¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤ò + ¼õ¤±¼è¤ê¤Þ¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + <VirtualHost _default_:*>
    + + DocumentRoot /www/default
    +     + </VirtualHost> +

    + +

    ¤³¤Î¤è¤¦¤Ë¥ï¥¤¥ë¥É¥«¡¼¥É¤Î¥Ý¡¼¥È¤Ç¥Ç¥Õ¥©¥ë¥È¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò + »ØÄꤹ¤ë¤È¡¢¼ç¥µ¡¼¥Ð¤Ë¥ê¥¯¥¨¥¹¥È¤¬¹Ô¤¯¤Î¤òËɤ²¤Þ¤¹¡£

    + +

    ¥Ç¥Õ¥©¥ë¥È¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ï̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë + »È¤ï¤ì¤Æ¤¤¤ë¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ÎÁȤËÁ÷¤é¤ì¤¿¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤³¤È¤Ï + ¤¢¤ê¤Þ¤»¤ó¡£¥ê¥¯¥¨¥¹¥È¤¬ÉÔÌÀ¤Ê Host: ¥Ø¥Ã¥À¤ä¤½¤Î + ¥Ø¥Ã¥À¤¬¤Ê¤«¤Ã¤¿¤ê¤¹¤ë¾ì¹ç¤Ï´ðËÜ̾Á°¥Ù¡¼¥¹¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È (¤½¤Î + ¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤ÇÀßÄê¥Õ¥¡¥¤¥ëÃæ¤ÇºÇ½é¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È) ¤Ë¤è¤ê + °·¤ï¤ì¤Þ¤¹¡£

    + +

    ¤É¤ó¤Ê¥ê¥¯¥¨¥¹¥È¤Ç¤â AliasMatch + ¤ä RewriteRule ¤ò»È¤Ã¤Æ + ñ°ì¤Î¾ðÊó¥Ú¡¼¥¸ (¤ä¥¹¥¯¥ê¥×¥È) ¤Ë½ñ¤­´¹¤¨¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    + + +

    °ã¤¦¥Ý¡¼¥È¤Î¤¿¤á¤Î + _default_ ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È

    + +

    °ì¤Ä¤á¤ÎÀßÄê¤È¤Û¤ÜƱ¤¸¤Ç¤¹¤¬¡¢¥µ¡¼¥Ð¤ÏÊ£¿ô¤Î¥Ý¡¼¥È¤ò listen ¤·¤Æ¤ª¤ê¡¢ + 80 È֥ݡ¼¥È¤ËÂФ·¤ÆÆó¤Ä¤á¤Î _default_ ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò + ÀßÄꤷ¤¿¤¤¾ì¹ç¤Ç¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + <VirtualHost _default_:80>
    + + DocumentRoot /www/default80
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost _default_:*>
    + + DocumentRoot /www/default
    + # ...
    +     + </VirtualHost> +

    + +

    80 È֥ݡ¼¥È¤Î¥Ç¥Õ¥©¥ë¥È¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È (¥ï¥¤¥ë¥É¥«¡¼¥É¥Ý¡¼¥È¤Î + ¥Ç¥Õ¥©¥ë¥È¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤è¤ê¤âÁ°¤Ë½ñ¤«¤ì¤Æ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó) ¤Ï + ̤»ØÄê¤Î IP ¥¢¥É¥ì¥¹¤ËÁ÷¤é¤ì¤¿¤¹¤Ù¤Æ¤Î¥ê¥¯¥¨¥¹¥È¤ò°·¤¤¤Þ¤¹¡£ + ¼ç¥µ¡¼¥Ð¤Ï¥ê¥¯¥¨¥¹¥È¤ò°·¤¤¤Þ¤»¤ó¡£

    + + +

    °ì¤Ä¤Î¥Ý¡¼¥È¤ËÂФ·¤Æ¤À¤±¤Î + _default_ ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È

    + +

    80 È֥ݡ¼¥È¤Ë¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬É¬Íפǡ¢Â¾¤Î + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ï¥Ç¥Õ¥©¥ë¥È¤¬É¬Íפʤ¤¾ì¹ç¤Ç¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + <VirtualHost _default_:80>
    + DocumentRoot /www/default
    + ...
    + </VirtualHost> +

    + +

    80 È֥ݡ¼¥È¤Ø¤Î¥¢¥É¥ì¥¹Ì¤»ØÄê¤Î¥ê¥¯¥¨¥¹¥È¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¥Ð¡¼¥Á¥ã¥ë + ¥Û¥¹¥È¤«¤éÁ÷¤é¤ì¤Þ¤¹¡£Â¾¤Î̤»ØÄê¤Î¥¢¥É¥ì¥¹¤È¥Ý¡¼¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï + ¼ç¥µ¡¼¥Ð¤«¤éÁ÷¤é¤ì¤Þ¤¹¡£

    + + +
    top
    +
    +

    ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤«¤é IP ¥Ù¡¼¥¹¤Î + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë°Ü¹Ô¤¹¤ë

    + +

    ¥Û¥¹¥È̾¤¬Ì¾Á° www.example.org ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È + (̾Á°¥Ù¡¼¥¹¤ÎÎã¤Î 2 ÈÖÌܤÎÀßÄê) ¤¬ÀìÍѤΠIP ¥¢¥É¥ì¥¹¤ò + ÆÀ¤¿¤È¤·¤Þ¤¹¡£Ì¾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¸Å¤¤ IP ¥¢¥É¥ì¥¹¤ò + ¥­¥ã¥Ã¥·¥å¤·¤Æ¤¤¤ë¥Í¡¼¥à¥µ¡¼¥Ð¤ä¥×¥í¥­¥·¤Î¤¿¤á¤Ë°Ü¹Ô´ü´ÖÃæ¤ÏξÊý¤Î + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤òÄ󶡤·¤¿¤¤¤È¤·¤Þ¤¹¡£

    + +

    Åú¤Ï´Êñ¤Ç¤¹¡£Ã±¤Ë¿·¤·¤¤ IP ¥¢¥É¥ì¥¹ (172.20.30.50) + ¤ò VirtualHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ËÄɲ乤뤳¤È¤Ç + ¤Ç¤­¤Þ¤¹¡£

    + +

    ¥µ¡¼¥ÐÀßÄê

    + + + Listen 80
    + ServerName www.example.com
    + DocumentRoot /www/example1
    +
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example3
    + ServerName www.example.net
    + ServerAlias *.example.net
    + # ...
    +     + </VirtualHost> +

    + +

    ¤³¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ï¿·¤·¤¤¥¢¥É¥ì¥¹ (IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤È¤·¤Æ) + ¤È¸Å¤¤¥¢¥É¥ì¥¹(̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤È¤·¤Æ) ¤ÎξÊý¤«¤é + ¥¢¥¯¥»¥¹¤Ç¤­¤Þ¤¹¡£

    + +
    top
    +
    +

    ServerPath ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + »È¤¦

    + +

    ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬Æó¤Ä¤¢¤ë¥µ¡¼¥Ð¤¬¤¢¤ë¤È¤·¤Þ¤¹¡£ + Àµ¤·¤¤¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤òÆÀ¤ë¤¿¤á¤Ë¤Ï¥¯¥é¥¤¥¢¥ó¥È¤ÏÀµ¤·¤¤ + Host: ¥Ø¥Ã¥À¤òÁ÷¤é¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¸Å¤¤ HTTP/1.0 ¤Ï¤½¤Î¤è¤¦¤Ê¥Ø¥Ã¥À¤òÁ÷¤é¤Ê¤¤¤Î¤Ç¡¢Apache ¤Ï¥¯¥é¥¤¥¢¥ó¥È¤¬ + ¤É¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò°Õ¿Þ¤·¤¿¤Î¤«¤µ¤Ã¤Ñ¤ê¤ï¤«¤ê¤Þ¤»¤ó + (¤Ê¤Î¤Ç¡¢¼ç¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ç¥ê¥¯¥¨¥¹¥È¤ò°·¤¤¤Þ¤¹)¡£ + ²Äǽ¤Ê¸Â¤ê¤Î²¼°Ì¸ß´¹À­¤òÆÀ¤ë¤¿¤á¡¢Ì¾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î + URL ÀÜƬ¼­¤Ø¤Î¥ê¥ó¥¯¤Î½ñ¤«¤ì¤¿¥Ú¡¼¥¸¤òÊÖ¤¹¡¢ + ¼ç¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬ºîÀ®¤µ¤ì¤Þ¤¹¡£

    + +

    ¥µ¡¼¥Ð¤ÎÀßÄê

    + + + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + + # primary vhost
    + DocumentRoot /www/subdomain
    + RewriteEngine On
    + RewriteRule ^/.* /www/subdomain/index.html
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + DocumentRoot /www/subdomain/sub1
    + + ServerName www.sub1.domain.tld
    + ServerPath /sub1/
    + RewriteEngine On
    + RewriteRule ^(/sub1/.*) /www/subdomain$1
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/subdomain/sub2
    + ServerName www.sub2.domain.tld
    + ServerPath /sub2/
    + RewriteEngine On
    + RewriteRule ^(/sub2/.*) /www/subdomain$1
    + # ...
    +     + </VirtualHost> +

    + +

    ServerPath ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÀßÄê¤Ë + ¤è¤ê¡¢URL http://www.sub1.domain.tld/sub1/ ¤Ï + ¾ï¤Ë sub1-vhost ¤Ë¤è¤ê°·¤ï¤ì¤Þ¤¹¡£URL + http://www.sub1.domain.tld/ ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï + ¥¯¥é¥¤¥¢¥ó¥È¤¬Àµ¤·¤¤ Host: ¥Ø¥Ã¥À¤òÁ÷¤Ã¤¿¤È¤­¤Ë¤Î¤ß + sub1-vhost ¤«¤éÁ÷¤é¤ì¤Þ¤¹¡£Host: ¥Ø¥Ã¥À¤¬¤Ê¤±¤ì¤Ð + ¥¯¥é¥¤¥¢¥ó¥È¤Ï¼ç¥Û¥¹¥È¤Î¾ðÊó¥Ú¡¼¥¸¤òÆÀ¤Þ¤¹¡£

    + +

    °ì¤Ä´ñ̯¤ÊÆ°ºî¤ò¤¹¤ëÅÀ¤¬¤¢¤ë¤³¤È¤Ï³Ð¤¨¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£ + http://www.sub2.domain.tld/sub1/ ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤â + Host: ¥Ø¥Ã¥À¤¬¤Ê¤±¤ì¤Ð sub1-vhost ¤Ë¤è¤ê°·¤ï¤ì¤Þ¤¹¡£

    + +

    Àµ¤·¤¤ Host: ¥Ø¥Ã¥À¤òÁ÷¤Ã¤¿¥¯¥é¥¤¥¢¥ó¥È¤Ï¤É¤Á¤é¤Î + URL¡¢¤Ä¤Þ¤êÀÜƬ¼­¤¬¤¢¤ëÊý¤â̵¤¤Êý¤â»È¤¨¤ë¤è¤¦¤Ë + RewriteRule ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ + »È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£

    +
    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/examples.html.ko.euc-kr b/docs/manual/vhosts/examples.html.ko.euc-kr new file mode 100644 index 00000000..99590889 --- /dev/null +++ b/docs/manual/vhosts/examples.html.ko.euc-kr @@ -0,0 +1,629 @@ + + + +°¡»óÈ£½ºÆ® ¿¹ - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    °¡»óÈ£½ºÆ® ¿¹

    +
    +

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

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

    ÀÌ ¹®¼­´Â ÀÚÁÖ ¹®ÀǵǴ °¡»óÈ£½ºÆ® + Áú¹®¿¡ ´äÀ» ÇÏ·Á°í ¾²¿©Á³´Ù. »óȲÀº À̸§±â¹ÝÀ̳ª IP±â¹Ý °¡»óÈ£½ºÆ®¸¦ ÅëÇØ ÇÑ ¼­¹ö¿¡¼­ + ¿©·¯ À¥»çÀÌÆ®¸¦ ¼­ºñ½ºÇÏ·Á´Â °æ¿ìÀÌ´Ù. ÇÑ ÇÁ·Ï½Ã ¼­¹ö µÚ¿¡¼­ + ¿©·¯ ¼­¹ö¸¦ »ç¿ëÇÏ¿© »çÀÌÆ®¸¦ ¿î¿µÇÏ´Â °æ¿ì¸¦ ´Ù·é ¹®¼­µµ + °ð ³ª¿Ã °ÍÀÌ´Ù.

    + +
    + +
    top
    +
    +

    IP ÁÖ¼Ò ÇÑ°³¿¡ ¿©·¯ À̸§±â¹Ý + À¥»çÀÌÆ® ¿î¿µÇϱâ.

    + +

    ¼­¹ö¿¡ IP ÁÖ¼Ò°¡ ÇÑ°³ ÀÖ°í, DNS¿¡¼­ ¿©·¯ ÁÖ¼Ò(CNAMES)°¡ + ÀÌ ÄÄÇ»Å͸¦ °¡¸®Å²´Ù. ÀÌ ÄÄÇ»ÅÍ¿¡¼­ www.example.com°ú + www.example.orgÀÇ À¥¼­¹ö¸¦ ½ÇÇàÇÏ°í ½Í´Ù.

    + +

    Note

    ¾ÆÆÄÄ¡ ¼­¹ö¿¡ °¡»óÈ£½ºÆ® ¼³Á¤À» + ÇÑ´Ù°í ±× È£½ºÆ®¸í¿¡ ´ëÇÑ DNS Ç׸ñÀÌ ÀÚµ¿ÀÌ·Î »ý¼ºµÇÁö + ¾Ê´Â´Ù. ¹Ýµå½Ã DNS¿¡ IP ÁÖ¼Ò¸¦ °¡¸®Å°´Â + À̸§ÀÌ ÀÖ¾î¾ß ÇÑ´Ù. ¾È±×·¯¸é ¾Æ¹«µµ À¥»çÀÌÆ®¸¦ º¼ + ¼ö ¾ø´Ù. °Ë»çÇغ¸±â À§ÇØ hosts ÆÄÀÏ¿¡ Ç׸ñÀ» + Ãß°¡ÇÒ ¼ö ÀÖÁö¸¸, ÀÌ´Â hosts Ç׸ñÀ» °¡Áø ÄÄÇ»ÅÍ¿¡¸¸ + ¹Ý¿µµÈ´Ù.

    +
    + +

    ¼­¹ö ¼³Á¤

    + + + # ¾ÆÆÄÄ¡°¡ Æ÷Æ® 80À» ±â´Ù¸°´Ù
    + Listen 80
    +
    + # ¸ðµç IP ÁÖ¼Ò¿¡¼­ °¡»óÈ£½ºÆ® ¿äûÀ» ±â´Ù¸°´Ù
    + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +
    + # ´Ù¸¥ Áö½Ã¾îµéµµ ÀÖ´Ù
    +
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +
    + # ´Ù¸¥ Áö½Ã¾îµéµµ ÀÖ´Ù
    +
    +     + </VirtualHost> +

    + +

    º°Ç¥´Â ¸ðµç ÁÖ¼Ò¸¦ °¡¸®Å°¹Ç·Î, ÁÖ¼­¹ö´Â ¾î¶² ¿äûµµ + ¼­ºñ½ºÇÏÁö ¾Ê´Â´Ù. www.example.comÀÌ + ¼³Á¤ÆÄÀÏ¿¡ óÀ½À¸·Î ³ª¿À¹Ç·Î °¡Àå ³ôÀº ¿ì¼±¼øÀ§¸¦ °¡Áö¸ç, + ±âº»È¤Àº Ãʱ⠼­¹ö°¡ µÈ´Ù. + ¾î¶² ServerName Áö½Ã¾î¿¡µµ ÇØ´çµÇÁö¾Ê´Â ¿äûÀº + ù¹ø° VirtualHost°¡ ¼­ºñ½ºÇÑ´Ù.

    + +
    +

    ÁÖÀÇ

    + +

    ¿øÇÑ´Ù¸é * ´ë½Å ½Ã½ºÅÛÀÇ ½ÇÁ¦ IP + ÁÖ¼Ò¸¦ »ç¿ëÇÒ ¼ö ÀÖ´Ù. ÀÌ °æ¿ì + VirtualHostÀÇ ¾Æ±Ô¸ÕÆ®´Â + NameVirtualHostÀÇ ¾Æ±Ô¸ÕÆ®¿Í ÀÏÄ¡ÇØ¾ß + ÇÑ´Ù:

    + +

    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + # »ý·« ... +

    + +

    ±×·¯³ª ISP¿¡¼­ µ¿ÀûÀ¸·Î IP ÁÖ¼Ò¸¦ °¡Á®¿À´Â µî + IP ÁÖ¼Ò¸¦ ¸ð¸£´Â °æ¿ì¿¡´Â *¸¦ »ç¿ëÇÏ´Â + °ÍÀÌ À¯¿ëÇÏ´Ù. *´Â ¸ðµç IP ÁÖ¼Ò¿¡ + ÇØ´çÇϹǷÎ, IP ÁÖ¼Ò°¡ º¯°æµÇ¾îµµ ¼³Á¤À» º¯°æÇÒ + ÇÊ¿ä°¡ ¾ø´Ù.

    +
    + +

    °ÅÀÇ ´ëºÎºÐÀÇ À̸§±â¹Ý °¡»óÈ£½ºÆ® ¼³Á¤Àº À§¿Í °°´Ù. + ¿¹¿Ü´Â ´Ù¸¥ IP ÁÖ¼Ò³ª Æ÷Æ®·Î ´Ù¸¥ ³»¿ëÀ» ¼­ºñ½ºÇÏ·Á´Â + °æ¿ìÀÌ´Ù.

    + +
    top
    +
    +

    ¿©·¯ IP ÁÖ¼Ò¿¡¼­ À̸§±â¹Ý + È£½ºÆ®.

    + +
    +

    ÁÖÀÇ

    ¿©±â¼­ ¼³¸íÇÑ ¹æ¹ýÀº IP ÁÖ¼Ò°¡ + ¸î°³¶óµµ Àû¿ë°¡´ÉÇÏ´Ù.

    +
    + +

    ¼­¹ö´Â IP ÁÖ¼Ò°¡ µÎ°³ÀÖ´Ù. Çϳª¿¡¼­ + (172.20.30.40) "ÁÖ" ¼­¹ö + server.domain.comÀ» ¼­ºñ½ºÇÏ°í, ´Ù¸¥ Çϳª¿¡¼­ + (172.20.30.50) ¿©·¯ °¡»óÈ£½ºÆ®¸¦ ¼­ºñ½ºÇÒ + °ÍÀÌ´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + Listen 80
    +
    + # 172.20.30.40¿¡¼­ ½ÇÇàÇÏ´Â "ÁÖ"¼­¹öÀÌ´Ù
    + ServerName server.domain.com
    + DocumentRoot /www/mainserver
    +
    + # ´Ù¸¥ ÁÖ¼Ò´Ù
    + NameVirtualHost 172.20.30.50
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +
    + # ´Ù¸¥ Áö½Ã¾îµéµµ ÀÖ´Ù ...
    +
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +
    + # ´Ù¸¥ Áö½Ã¾îµéµµ ÀÖ´Ù ...
    +
    +     + </VirtualHost> +

    + +

    172.20.30.50ÀÌ ¾Æ´Ñ ÁÖ¼Ò¿¡ ´ëÇÑ ¿äûÀº + ÁÖ¼­¹ö°¡ ¼­ºñ½ºÇÑ´Ù. È£½ºÆ®¸í ¾øÀÌ, Áï Host: + Çì´õ¾øÀÌ 172.20.30.50·Î ¿äûÇϸé + www.example.comÀÌ ¼­ºñ½ºÇÑ´Ù.

    + +
    top
    +
    +

    (³»ºÎ¿Í ¿ÜºÎ ÁÖ¼Ò¿Í °°ÀÌ) + ´Ù¸¥ IP ÁÖ¼Ò·Î °°Àº ³»¿ëÀ» ¼­ºñ½ºÇϱâ.

    + +

    ¼­¹ö ÄÄÇ»ÅÍ¿¡ IP ÁÖ¼Ò°¡ µÎ°³ (192.168.1.1°ú + 172.20.30.40) ÀÖ´Ù. ÄÄÇ»ÅÍ´Â ³»ºÎ (ÀÎÆ®¶ó³Ý) + ³×Æ®¿÷°ú ¿ÜºÎ (ÀÎÅͳÝ) ³×Æ®¿÷ »çÀÌ¿¡ À§Ä¡ÇÑ´Ù. ³×Æ®¿÷ ¹Û¿¡¼­ + server.example.comÀº ¿ÜºÎ ÁÖ¼Ò¸¦ + (172.20.30.40) ÀǹÌÇÏ°í, ³×Æ®¿÷ ³»ºÎ¿¡¼­ °°Àº + À̸§À» ³»ºÎ ÁÖ¼Ò·Î (192.168.1.1) »ç¿ëÇÑ´Ù.

    + +

    ¼­¹ö´Â VirtualHost ¼½¼Ç ÇÑ°³·Î ³»ºÎ¿Í ¿ÜºÎ + ÀÀ´ä¿¡ °°Àº ³»¿ëÀ» ¼­ºñ½ºÇÒ ¼ö ÀÖ´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + NameVirtualHost 192.168.1.1
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 192.168.1.1 172.20.30.40>
    + + DocumentRoot /www/server1
    + ServerName server.example.com
    + ServerAlias server
    +     + </VirtualHost> +

    + +

    ÀÌÁ¦ µÎ ³×Æ®¿÷¿¡¼­ µé¾î¿Â ¿äûÀ» °°Àº + VirtualHost¿¡¼­ ¼­ºñ½ºÇÑ´Ù.

    + +
    +

    ÁÖÀÇ:

    ³»ºÎ ³×Æ®¿÷¿¡¼­´Â ¿ÏÀüÇÑ È£½ºÆ®¸í + server.example.com ´ë½Å À̸§ + serverµµ °¡´ÉÇÏ´Ù.

    + +

    ¶ÇÇÑ À§ÀÇ ¿¹¿¡¼­ IP ÁÖ¼Ò ´ë½Å *À» + »ç¿ëÇÏ¿© ¼­¹ö°¡ ¸ðµç ÁÖ¼Ò¿¡ µ¿ÀÏÇÏ°Ô µ¿ÀÛÇÒ ¼ö + ÀÖ´Ù.

    +
    + +
    top
    +
    +

    ¿©·¯ Æ÷Æ®¿¡¼­ ¼­·Î ´Ù¸¥ »çÀÌÆ® + ¿î¿µÇϱâ.

    + +

    °°Àº IPÀÇ ¿©·¯ Æ÷Æ®¿¡¼­ ¼­·Î ´Ù¸¥ µµ¸ÞÀÎÀ» ¼­ºñ½ºÇÑ´Ù°í + °¡Á¤ÇÏÀÚ. ÀÌ´Â "NameVirtualHost" ű׿¡ Æ÷Æ®¸¦ Á¤ÀÇÇϸé + °¡´ÉÇÏ´Ù. NameVirtualHost name:port¾øÀÌ <VirtualHost + name:port>¸¸ ȤÀº Listen Áö½Ã¾î¸¸ »ç¿ëÇÏ¸é ¾ÈµÈ´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + Listen 80
    + Listen 8080
    +
    + NameVirtualHost 172.20.30.40:80
    + NameVirtualHost 172.20.30.40:8080
    +
    + <VirtualHost 172.20.30.40:80>
    + + ServerName www.example.com
    + DocumentRoot /www/domain-80
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + ServerName www.example.com
    + DocumentRoot /www/domain-8080
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:80>
    + + ServerName www.example.org
    + DocumentRoot /www/otherdomain-80
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + ServerName www.example.org
    + DocumentRoot /www/otherdomain-8080
    +     + </VirtualHost> +

    + +
    top
    +
    +

    IP±â¹Ý °¡»óÈ£½ºÆ®

    + +

    ¼­¹ö´Â °¢°¢ www.example.com°ú + www.example.org¿¡ ÇØ´çÇÏ´Â µÎ IP ÁÖ¼Ò¸¦ + (172.20.30.40°ú 172.20.30.50) + °¡Áø´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + Listen 80
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +     + </VirtualHost> +

    + +

    <VirtualHost> Áö½Ã¾î·Î ÁöÁ¤ÇÑ ÁÖ¼Ò¿¡ + ÇØ´çÇÏÁö¾Ê´Â ÁÖ¼Ò·Î (¿¹¸¦ µé¾î, localhost) + ¿äûÀÌ µé¾î¿À¸é ÁÖ¼­¹ö°¡ ÀÖ´Â °æ¿ì ÁÖ¼­¹ö°¡ ¼­ºñ½ºÇÑ´Ù.

    + +
    top
    +
    +

    Æ÷Æ®±â¹Ý°ú ip±â¹ÝÀÌ È¥ÇÕµÈ + °¡»óÈ£½ºÆ®

    + +

    ¼­¹ö´Â °¢°¢ www.example.com°ú + www.example.org¿¡ ÇØ´çÇÏ´Â µÎ IP ÁÖ¼Ò¸¦ + (172.20.30.40°ú 172.20.30.50) + °¡Áø´Ù. °¢ IPÀÇ 80¹ø°ú 8080¹ø Æ÷Æ®¿¡ °¡»óÈ£½ºÆ®¸¦ µ¹¸°´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + Listen 172.20.30.40:80
    + Listen 172.20.30.40:8080
    + Listen 172.20.30.50:80
    + Listen 172.20.30.50:8080
    +
    + <VirtualHost 172.20.30.40:80>
    + + DocumentRoot /www/example1-80
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40:8080>
    + + DocumentRoot /www/example1-8080
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50:80>
    + + DocumentRoot /www/example2-80
    + ServerName www.example.org
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.50:8080>
    + + DocumentRoot /www/example2-8080
    + ServerName www.example.org
    +     + </VirtualHost> +

    + +
    top
    +
    +

    À̸§±â¹Ý°ú IP±â¹ÝÀÌ È¥ÇÕµÈ + °¡»óÈ£½ºÆ®

    + +

    ÁÖ¼ÒÁß ¸î¸îÀº À̸§±â¹Ý °¡»óÈ£½ºÆ®·Î, ´Ù¸¥ °ÍÀº IP±â¹Ý + °¡»óÈ£½ºÆ®·Î ¼­ºñ½ºÇÏ°í ½Í´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + Listen 80
    +
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example1
    + ServerName www.example.com
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example3
    + ServerName www.example3.net
    +     + </VirtualHost>
    +
    + # IP-±â¹Ý
    + <VirtualHost 172.20.30.50>
    + + DocumentRoot /www/example4
    + ServerName www.example4.edu
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.60>
    + + DocumentRoot /www/example5
    + ServerName www.example5.gov
    +     + </VirtualHost> +

    + +
    top
    +
    +

    _default_ °¡»óÈ£½ºÆ® + »ç¿ëÇϱâ

    + +

    ¸ðµç Æ÷Æ®¿¡ ´ëÇÑ + _default_ °¡»óÈ£½ºÆ®

    + +

    ¾î¶² °¡»óÈ£½ºÆ®¿¡µµ ÇØ´çÇÏÁö¾ÊÀº IP ÁÖ¼Ò¿Í Æ÷Æ®¿¡ ´ëÇÑ + ¸ðµç ¿äûÀ» ó¸®Çϱâ.

    + +

    ¼­¹ö ¼³Á¤

    + + + <VirtualHost _default_:*>
    + + DocumentRoot /www/default
    +     + </VirtualHost> +

    + +

    default(±âº») °¡»óÈ£½ºÆ®ÀÇ Æ÷Æ®·Î ¿ÍÀϵåÄ«µå¸¦ »ç¿ëÇÏ¿© ¾î¶² ¿äûµµ + ÁÖ¼­¹ö·Î ¸ø°¡µµ·Ï ¸¸µç´Ù.

    + +

    default °¡»óÈ£½ºÆ®´Â Àý´ë·Î À̸§±â¹Ý °¡»óÈ£½ºÆ®°¡ »ç¿ëÇÏ´Â + ÁÖ¼Ò/Æ÷Æ®·ÎÀÇ ¿äûÀ» ¼­ºñ½ºÇÏÁö ¾Ê´Â´Ù. ¾Ë ¼ö ¾ø°Å³ª + Host: Çì´õ°¡ »ý·«µÈ ¿äûÀº Ç×»ó ÃÖÃÊÀÇ À̸§±â¹Ý + °¡»óÈ£½ºÆ®(¼³Á¤ÆÄÀÏ¿¡¼­ + ÁÖ¼Ò/Æ÷Æ®°¡ óÀ½À¸·Î ³ª¿Â °¡»óÈ£½ºÆ®)°¡ ¼­ºñ½ºÇÑ´Ù.

    + +

    AliasMatch³ª + RewriteRuleÀ» + »ç¿ëÇÏ¿© ¾î¶² ¿äûÀ» ƯÁ¤ ÆäÀÌÁö(ȤÀº ½ºÅ©¸³Æ®)·Î + ÀçÀÛ¼ºÇÒ(rewrite) ¼ö ÀÖ´Ù.

    + + +

    ¿©·¯ Æ÷Æ®¿¡ ´ëÇÑ + _default_ °¡»óÈ£½ºÆ®

    + +

    À§ÀÇ °æ¿ì¿Í °°Áö¸¸, ¼­¹ö´Â ¿©·¯ Æ÷Æ®¸¦ ±â´Ù¸®°í 80¹ø + Æ÷Æ®¿¡ ´ëÇؼ­ Ãß°¡·Î _default_ °¡»óÈ£½ºÆ®¸¦ + »ç¿ëÇÏ°í ½Í´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + <VirtualHost _default_:80>
    + + DocumentRoot /www/default80
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost _default_:*>
    + + DocumentRoot /www/default
    + # ...
    +     + </VirtualHost> +

    + +

    80¹ø Æ÷Æ®¿¡ ´ëÇÑ default °¡»óÈ£½ºÆ®´Â (¹Ýµå½Ã + ¿ÍÀϵåÄ«µå Æ÷Æ®¸¦ °¡Áø ±âº» °¡»óÈ£½ºÆ® ÀÌÀü¿¡ ³ª¿Í¾ß ÇÑ´Ù) + ÁöÁ¤ÇÏÁö¾ÊÀº IP ÁÖ¼Ò·Î º¸³»Áø ¸ðµç ¿äûÀ» ¼­ºñ½ºÇÑ´Ù. + ÁÖ¼­¹ö´Â Àý´ë·Î ¿äûÀ» ¼­ºñ½ºÇÏÁö ¸øÇÑ´Ù.

    + + +

    ÇÑ Æ÷Æ®¿¡ ´ëÇÑ + _default_ °¡»óÈ£½ºÆ®

    + +

    80¹ø Æ÷Æ®¿¡ ´ëÇؼ­¸¸ default °¡»óÈ£½ºÆ®¸¦ ¸¸µé°í ½Í´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + <VirtualHost _default_:80>
    + DocumentRoot /www/default
    + ...
    + </VirtualHost> +

    + +

    Æ÷Æ® 80¹ø¿¡ ÁöÁ¤ÇÏÁö¾ÊÀº ÁÖ¼Ò¿¡ ´ëÇÑ ¿äûÀº ±âº» + °¡»óÈ£½ºÆ®°¡ ¼­ºñ½ºÇÏ°í, ´Ù¸¥ ÁöÁ¤ÇÏÁö¾ÊÀº ÁÖ¼Ò¿Í Æ÷Æ®¸¦ + °¡Áø ¿äûÀº ÁÖ ¼­¹ö°¡ ¼­ºñ½ºÇÑ´Ù.

    + + +
    top
    +
    +

    À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ IP±â¹Ý + °¡»óÈ£½ºÆ®·Î ¿Å±â±â

    + +

    (À̸§±â¹ÝÀÇ Ã¹¹ø° ¿¹¿¡¼­) È£½ºÆ®¸í + www.example.org¿¡ ´ëÇÑ À̸§±â¹Ý °¡»óÈ£½ºÆ®´Â + ÀÚ½ÅÀÇ IP ÁÖ¼Ò¸¦ °¡Á®¾ß ÇÑ´Ù. À̸§±â¹Ý °¡»óÈ£½ºÆ®ÀÇ ÀÌÀü + IP ÁÖ¼Ò¸¦ ij½ÌÇÏ´Â ³×ÀÓ¼­¹ö³ª ÇÁ·Ï½Ã¿ÍÀÇ ¹®Á¦¸¦ ÇÇÇϱâÀ§ÇØ + ¿Å±â´Â µ¿¾È µÑ ¸ðµÎ¸¦ ¼­ºñ½ºÇÏ°í ½Í´Ù.

    + +

    + ¹æ¹ýÀº VirtualHost Áö½Ã¾î¿¡ »õ IP ÁÖ¼Ò¸¸À» + (172.20.30.50) Ãß°¡ÇϸéµÇ¹Ç·Î ½±´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + Listen 80
    + ServerName www.example.com
    + DocumentRoot /www/example1
    +
    + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40 172.20.30.50>
    + + DocumentRoot /www/example2
    + ServerName www.example.org
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/example3
    + ServerName www.example.net
    + ServerAlias *.example.net
    + # ...
    +     + </VirtualHost> +

    + +

    ÀÌÁ¦ (IP±â¹Ý °¡»óÈ£½ºÆ®¸¦ ÅëÇÑ) »õ·Î¿î ÁÖ¼Ò¿Í (À̸§±â¹Ý + °¡»óÈ£½ºÆ®¸¦ ÅëÇÑ) ÀÌÀü ÁÖ¼Ò ¸ðµÎ °¡»óÈ£½ºÆ®¿¡ Á¢±ÙÇÒ + ¼ö ÀÖ´Ù.

    + +
    top
    +
    +

    ServerPath + Áö½Ã¾î »ç¿ëÇϱâ

    + +

    µÎ À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ °¡Áø ¼­¹ö°¡ ÀÖ´Ù. ¿Ã¹Ù¸¥ + °¡»óÈ£½ºÆ®¸¦ ¼±ÅÃÇϱâÀ§ÇØ Å¬¶óÀ̾ðÆ®´Â ¿Ã¹Ù¸¥ + Host: Çì´õ¸¦ º¸³»¾ß ÇÑ´Ù. ¿À·¡µÈ HTTP/1.0 + Ŭ¶óÀ̾ðÆ®°¡ ÀÌ Çì´õ¸¦ º¸³»Áö ¸øÇÏ¸é ¾ÆÆÄÄ¡´Â Ŭ¶óÀ̾ðÆ®°¡ + ¾î¶² °¡»óÈ£½ºÆ®¸¦ º¸·Á°íÇÏ´ÂÁö ¾Ë ¼ö ¾ø´Ù (±×·¡¼­ ÃÖÃÊÀÇ + °¡»óÈ£½ºÆ®°¡ ¿äûÀ» ¼­ºñ½ºÇÑ´Ù). ¿À·¡µÈ ºê¶ó¿ìÀú¿Í °¡´ÉÇÑ È£È¯À» + À¯ÁöÇϱâÀ§ÇØ ÃÖÃÊÀÇ °¡»óÈ£½ºÆ®¸¦ ¸¸µé°í, ¿©±â¿¡ À̸§±â¹Ý + °¡»óÈ£½ºÆ®ÀÇ URL Á¢µÎ»ç¸¦ Æ÷ÇÔÇÏ´Â ¸µÅ© ¸ñ·Ï ÆäÀÌÁö¸¦ + µÐ´Ù.

    + +

    ¼­¹ö ¼³Á¤

    + + + NameVirtualHost 172.20.30.40
    +
    + <VirtualHost 172.20.30.40>
    + + # primary vhost
    + DocumentRoot /www/subdomain
    + RewriteEngine On
    + RewriteRule ^/.* /www/subdomain/index.html
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + DocumentRoot /www/subdomain/sub1
    + + ServerName www.sub1.domain.tld
    + ServerPath /sub1/
    + RewriteEngine On
    + RewriteRule ^(/sub1/.*) /www/subdomain$1
    + # ...
    +     + </VirtualHost>
    +
    + <VirtualHost 172.20.30.40>
    + + DocumentRoot /www/subdomain/sub2
    + ServerName www.sub2.domain.tld
    + ServerPath /sub2/
    + RewriteEngine On
    + RewriteRule ^(/sub2/.*) /www/subdomain$1
    + # ...
    +     + </VirtualHost> +

    + +

    ServerPath Áö½Ã¾î¶§¹®¿¡ + URL http://www.sub1.domain.tld/sub1/¿¡ ´ëÇÑ + ¿äûÀº Ç×»ó subl-°¡»óÈ£½ºÆ®°¡ ¼­ºñ½ºÇÑ´Ù.
    + Ŭ¶óÀ̾ðÆ®°¡ ¿Ã¹Ù¸¥ Host: Çì´õ¸¦ º¸³½´Ù¸é, + URL http://www.sub1.domain.tld/¿¡ ´ëÇÑ ¿äûÀº + subl-°¡»óÈ£½ºÆ®¿¡¼­¸¸ ¼­ºñ½ºÇÑ´Ù. ¸¸¾à Host: Çì´õ¸¦ + º¸³»Áö¾ÊÀ¸¸é Ŭ¶óÀ̾ðÆ®´Â ÃÖÃÊÀÇ È£½ºÆ®¿¡ ÀÖ´Â Á¤º¸ÆäÀÌÁö¸¦ + º¸°ÔµÈ´Ù.

    + +

    ¿©±â¿¡ ¹®Á¦°¡ ÀÖÀ½À» ÁÖÀÇÇ϶ó: Ŭ¶óÀ̾ðÆ®°¡ + Host: Çì´õ¸¦ º¸³»Áö¾ÊÀ¸¸é + http://www.sub2.domain.tld/sub1/¿¡ ´ëÇÑ ¿äûµµ + subl-°¡»óÈ£½ºÆ®°¡ ¼­ºñ½ºÇÑ´Ù.

    + +

    RewriteRule + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ¿Ã¹Ù¸¥ Host: Çì´õ¸¦ º¸³»´Â + Ŭ¶óÀ̾ðÆ®´Â (¿¹¸¦ µé¾î, URL ÀüÄ¡»ç°¡ Àְųª ¾ø´Â) + µÎ URLÀ» ¸ðµÎ »ç¿ëÇÒ ¼ö ÀÖ´Ù.

    + +
    +
    +

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

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/fd-limits.html b/docs/manual/vhosts/fd-limits.html new file mode 100644 index 00000000..932c75d7 --- /dev/null +++ b/docs/manual/vhosts/fd-limits.html @@ -0,0 +1,15 @@ +URI: fd-limits.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: fd-limits.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: fd-limits.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: fd-limits.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/vhosts/fd-limits.html.en b/docs/manual/vhosts/fd-limits.html.en new file mode 100644 index 00000000..3551a83e --- /dev/null +++ b/docs/manual/vhosts/fd-limits.html.en @@ -0,0 +1,128 @@ + + + +File Descriptor Limits - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    File Descriptor Limits

    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + + +

    When using a large number of Virtual Hosts, Apache may run + out of available file descriptors (sometimes called file + handles) if each Virtual Host specifies different log + files. The total number of file descriptors used by Apache is + one for each distinct error log file, one for every other log + file directive, plus 10-20 for internal use. Unix operating + systems limit the number of file descriptors that may be used + by a process; the limit is typically 64, and may usually be + increased up to a large hard-limit.

    + +

    Although Apache attempts to increase the limit as required, + this may not work if:

    + +
      +
    1. Your system does not provide the setrlimit() + system call.
      2. + +
    2. The setrlimit(RLIMIT_NOFILE) call does not + function on your system (such as Solaris 2.3)
      3. + +
    3. The number of file descriptors required exceeds the hard + limit.
      4. + +
    4. Your system imposes other limits on file descriptors, + such as a limit on stdio streams only using file descriptors + below 256. (Solaris 2)
      5. +
    + +

    In the event of problems you can:

    + +
      +
    • Reduce the number of log files; don't specify log files + in the <VirtualHost> + sections, but only log to the main log files. (See Splitting up your log files, below, for more + information on doing this.)
      • + +
    • + If you system falls into 1 or 2 (above), then increase the + file descriptor limit before starting Apache, using a + script like + +

      + #!/bin/sh
      + ulimit -S -n 100
      + exec httpd       +

      +
      • +
    + +
    +
    top
    +
    +

    Splitting up your log files

    + +

    If you want to log multiple virtual hosts to the same log file, you +may want to split up the log files afterwards in order to run +statistical analysis of the various virtual hosts. This can be +accomplished in the following manner.

    + +

    First, you will need to add the virtual host information to the log +entries. This can be done using the +LogFormat +directive, and the %v variable. Add this to the beginning +of your log format string:

    + +

    +LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost
    +CustomLog logs/multiple_vhost_log vhost +

    + +

    This will create a log file in the common log format, but with the +canonical virtual host (whatever appears in the +ServerName directive) prepended to +each line. (See Custom Log Formats for +more about customizing your log files.)

    + +

    When you wish to split your log file into its component parts (one +file per virtual host) you can use the program split-logfile to accomplish +this. You'll find this program in the support directory +of the Apache distribution.

    + +

    Run this program with the command:

    + +

    +split-logfile < /logs/multiple_vhost_log +

    + +

    This program, when run with the name of your vhost log file, will +generate one file for each virtual host that appears in your log file. +Each file will be called hostname.log.

    + +
    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/fd-limits.html.fr b/docs/manual/vhosts/fd-limits.html.fr new file mode 100644 index 00000000..20364164 --- /dev/null +++ b/docs/manual/vhosts/fd-limits.html.fr @@ -0,0 +1,141 @@ + + + +Limites des descripteurs de fichiers - Serveur Apache HTTP + + + + +
    +

    Modules | Directives | FAQ | Glossaire | Plan du site

    +

    Serveur Apache HTTP Version 2.2

    +
    +
    <-
    +

    Limites des descripteurs de fichiers

    +
    +

    Langues Disponibles:  en  | + fr  | + ja  | + ko 

    +
    + + +

    Quand de nombreux serveurs virtuels sont créés, Apache peut + dépasser les limites en descripteurs de fichiers ('file descriptors', + également appelés gestionnaires de fichiers) si chacun + des serveurs virtuels utilise ses propres fichiers journaux. Le + nombre total de descripteurs de fichiers utilisés par Apache est + d'un par fichier journal, un pour chacune des autres directives + de fichiers journaux, plus un nombre constant compris entre 10 et 20 + pour son fonctionnement interne. Les systèmes d'exploitation Unix + limitent le nombre de descripteurs de fichiers utilisables par + processus ; une valeur courante pour cette limite est de 64, et + cette valeur peut le plus souvent être augmentée.

    + +

    Apache tente d'accroître cette valeur limite si nécessaire, mais + sans y parvenir dans les cas suivants :

    + +
      +
    1. Le système d'exploitation ne permet pas l'utilisation d'appels + systèmes setrlimit().
      2. + +
    2. L'appel setrlimit(RLIMIT_NOFILE) ne fonctionne pas + sur votre système d'exploitation (c'est le cas sous Solaris 2.3).
      3. + +
    3. Le nombre de descripteurs de fichiers nécessaires à Apache + dépasse la limite physique du matériel.
      4. + +
    4. Le système impose d'autres limites sur l'utilisation des + descripteurs de fichiers, comme par exemple une limite sur les + flux stdio, utilisables uniquement sur les descripteurs de + fichiers inférieurs à 256. (sous Solaris 2).
      5. +
    + +

    En cas de problème, Vous pouvez :

    + +
      +
    • Réduire le nombre de fichiers journaux, en ne spécifiant + aucun fichier journal dans les sections + <VirtualHost>, + en donc en envoyant les informations aux fichiers journaux du + serveur principal (Voir Éclatement des + fichiers journaux ci-dessous pour plus d'informations sur + cette possibilité).
      • + +
    • + Dans les cas 1 ou 2 (évoqués ci-dessus), augmentez la limite sur + les descripteurs de fichiers avant le démarrage d'Apache, au + moyen d'un script comme + +

      + #!/bin/sh
      + ulimit -S -n 100
      + exec httpd       +

      +
      • +
    + + + +
    +
    top
    +
    +

    Éclatement des fichiers journaux

    + +

    Lorsque vous choisissez d'enregistrer les informations émanant de +plusieurs serveurs virtuels dans un même fichier journal, vous voudrez +ensuite pouvoir scinder ces informations à des fins de statistiques, par +exemple, sur les différents serveurs virtuels. Il est possible de procéder +de la manière suivante :

    + +

    Tout d'abord, vous devez ajouter le nom du serveur virtuel à chaque +entrée du journal. Ceci se paramètre au moyen de la directive + LogFormat et de la +variable %v. Ajoutez cette variable au début de la chaîne +de définition du format de journalisations :

    + +

    +LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost
    +CustomLog logs/multiple_vhost_log vhost +

    + +

    Cette configuration va provoquer la création d'un fichier de +journalisation au format standard (CLF : 'Common Log Format'), mais dont +chaque ligne débutera par le nom canonique du serveur virtuel (spécifié +par la directive ServerName). +(Voir Formats de journalisation +personnalisés pour d'autres informations sur la +personnalisation des fichiers journaux.)

    + +

    Au moment de séparer les informations du fichier journal en un fichier +par serveur virtuel, le programme +split-logfile peut être +utilisé. Ce programme peut être trouvé dans le répertoire +support de la distribution d'Apache.

    + +

    Exécutez ce programme au moyen de la commande :

    + +

    +split-logfile < /logs/multiple_vhost_log +

    + +

    Une fois exécuté avec le nom du fichier contenant tous les journaux, +ce programme va générer un fichier pour chacun des serveurs virtuels +qui apparaît dans le fichier d'entrée. Chaque fichier en sortie est +nommé nomduserveur.log.

    + +
    +
    +

    Langues Disponibles:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/fd-limits.html.ja.euc-jp b/docs/manual/vhosts/fd-limits.html.ja.euc-jp new file mode 100644 index 00000000..5a19a47a --- /dev/null +++ b/docs/manual/vhosts/fd-limits.html.ja.euc-jp @@ -0,0 +1,125 @@ + + + +¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î¸Â³¦ - Apache HTTP ¥µ¡¼¥Ð + + + + +
    +

    ¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

    +

    Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

    +
    +
    <-
    +

    ¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î¸Â³¦

    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + + +

    ¤¿¤¯¤µ¤ó¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò±¿ÍѤ¹¤ë¾ì¹ç¡¢¤â¤·¡¢ + ³Æ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤´¤È¤Ë°Û¤Ê¤ë¥í¥°¥Õ¥¡¥¤¥ë¤¬»ØÄꤷ¤Æ¤¢¤ë¤È¡¢ + Apache ¤¬¥Õ¥¡¥¤¥ëµ­½Ò»Ò (¥Õ¥¡¥¤¥ë¥Ï¥ó¥É¥ë¤È¤â¸Æ¤Ð¤ì¤Þ¤¹) + ¤ò»È¤¤ÀڤäƤ·¤Þ¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£Apache ¤¬»ÈÍѤ¹¤ë¥Õ¥¡¥¤¥ë + µ­½Ò»Ò¤Î¿ô¤Ï¡¢³Æ¥¨¥é¡¼¥í¥°¥Õ¥¡¥¤¥ë¤Ë¤Ä¤­ 1 ¤Ä¡¢Â¾¤Î¥í¥°¥Õ¥¡¥¤¥ë¤Î + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤Ä¤­ 1 ¤Ä¡¢¤µ¤é¤ËÆâÉô¤Ç»ÈÍѤ¹¤ë 10 ¤«¤é 20¡¢ + ¤Î¹ç·×¤Ë¤Ê¤ê¤Þ¤¹¡£Unix ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ç¤Ï¥×¥í¥»¥¹¤´¤È¤Ë + »ÈÍѲÄǽ¤Ê¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î¿ô¤òÀ©¸Â¤·¤Æ¤¤¤Þ¤¹¡£¤¿¤¤¤Æ¤¤¤Î¾ì¹ç¤Ï 64 ¤Ç¡¢ + ÉáÄ̤ÏÂ礭¤ÊÃͤΥϡ¼¥É¥ê¥ß¥Ã¥È¤Þ¤ÇÁý¤ä¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    + +

    Apache ¤ÏɬÍפ˱þ¤¸¤Æ¾å¸Â¤ò³ÈÂ礷¤è¤¦¤È»î¤ß¤Þ¤¹¤¬¡¢ + °Ê²¼¤Î¤è¤¦¤Ê¾ì¹ç¤Ë¤Ï¤¦¤Þ¤¯¤¤¤«¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£

    + +
      +
    1. ÍøÍѤ·¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤Ç setrlimit() + ¥·¥¹¥Æ¥à¥³¡¼¥ë¤¬Ä󶡤µ¤ì¤Æ¤¤¤Ê¤¤¡£
      2. + +
    2. ¥·¥¹¥Æ¥à¾å¤Ç setrlimit(RLIMIT_NOFILE) ¤¬Æ°ºî¤·¤Ê¤¤ + (¤¿¤È¤¨¤Ð Solaris 2.3 ¤Î¤è¤¦¤Ë)¡£
      3. + +
    3. Í׵ᤵ¤ì¤ë¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î¿ô¤¬ + ¥Ï¡¼¥É¥ê¥ß¥Ã¥È¤òĶ¤¨¤Æ¤·¤Þ¤¦¡£
      4. + +
    4. ¥·¥¹¥Æ¥à¤Ë¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Ë´Ø¤·¤ÆÊ̤ÎÀ©¸Â¤¬Â¸ºß¤·¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë¡£ + ¤¿¤È¤¨¤Ð¡¢stdio ¥¹¥È¥ê¡¼¥à¤Ç¤Ï¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤ò 256 °Ê¾å»È¤¨¤Ê¤¤ + (Solaris 2)¡¢¤Ê¤É¡£
      5. +
    + +

    ÌäÂ꤬ȯÀ¸¤·¤¿»þ¤Ë¼è¤êÆÀ¤ëÂнèÊýË¡¤Ï¼¡¤Î¤È¤ª¤ê:

    + +
      +
    • ¥í¥°¥Õ¥¡¥¤¥ë¤Î¿ô¤ò¸º¤é¤¹¡£<VirtualHost> + ¥»¥¯¥·¥ç¥ó¤Ç¥í¥°¥Õ¥¡¥¤¥ë¤ò»ØÄꤻ¤º¡¢¥á¥¤¥ó¤Î¥í¥°¥Õ¥¡¥¤¥ë¤Ë¤Î¤ßµ­Ï¿¤¹¤ë¡£ + (¤³¤ì¤Ë´Ø¤¹¤ë¾Ü¤·¤¤¾ðÊó¤Ï°Ê²¼¤Î¥í¥°¥Õ¥¡¥¤¥ë¤Îʬ³ä¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£)
      • + +
    • + ¤â¤·¡¢Á°½Ò¤Î 1 ¤Þ¤¿¤Ï 2 ¤Î¾ì¹ç¤Ç¤¢¤ì¤Ð¡¢ + Apache ¤òµ¯Æ°¤¹¤ëÁ°¤Ë¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤òÁý¤ä¤·¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¼¡¤Î¤è¤¦¤Ê¥¹¥¯¥ê¥×¥È¤ò»È¤¤¤Þ¤¹¡£ + +

      + #!/bin/sh
      + ulimit -S -n 100
      + exec httpd       +

      +
      • +
    +
    +
    top
    +
    +

    ¥í¥°¥Õ¥¡¥¤¥ë¤Îʬ³ä

    + +

    Ê£¿ô¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¥í¥°¤òƱ¤¸¥í¥°¥Õ¥¡¥¤¥ë¤Ë¼ý½¸¤·¤è¤¦¤È¤·¤Æ¤¤¤ë¤È¤­¤Ë¤Ï¡¢ +³Æ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¤Ä¤¤¤ÆÅý·×Ū¤Ê²òÀϤò¼Â¹Ô¤¹¤ë¤¿¤á¤Ë¸å¤Ç¥í¥°¥Õ¥¡¥¤¥ë¤ò +ʬ³ä¤·¤¿¤¯¤Ê¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£¤³¤ì¤Ï°Ê²¼¤Î¤è¤¦¤Ë¤·¤Æ¼Â¸½¤Ç¤­¤Þ¤¹¡£

    + +

    ¤Þ¤º¡¢¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¾ðÊó¤ò¥í¥°¤Î¥¨¥ó¥È¥ê¤ËÄɲ乤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ +¤³¤ì¤Ï LogFormat +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î %v ÊÑ¿ô¤ò»È¤¦¤³¤È¤Ç¤Ç¤­¤Þ¤¹¡£ +¤³¤ì¤ò¥í¥°¤Î¥Õ¥©¡¼¥Þ¥Ã¥Èʸ»úÎó¤ÎÀèƬ¤ËÄɲä·¤Þ¤¹:

    + +

    +LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost
    +CustomLog logs/multiple_vhost_log vhost +

    + +

    ¤³¤ì¤Ï common log format ¤Î¥í¥°¤òºîÀ®¤·¤Þ¤¹¤¬¡¢¤½¤ì¤¾¤ì¤Î¹Ô¤ÎÀèƬ¤Ë +Àµµ¬²½¤µ¤ì¤¿¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î̾Á° +(ServerName +¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¤â¤Î) ¤¬Éղ䵤ì¤Þ¤¹¡£ +(¥í¥°¥Õ¥¡¥¤¥ë¤Î¥«¥¹¥¿¥Þ¥¤¥º¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï Custom Log Formats ¤ò +Æɤó¤Ç¤¯¤À¤µ¤¤¡£)

    + +

    ¥í¥°¥Õ¥¡¥¤¥ë¤ò³ÆÉôʬ (¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈËè¤Ë 1 ¥Õ¥¡¥¤¥ë) ¤Ëʬ¤±¤¿¤¤¤È¤­¤Ï¡¢ +split-logfile +¤ò»È¤Ã¤Æ¹Ô¤Ê¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¥×¥í¥°¥é¥à¤Ï Apache ÇÛÉۤΠ+support ¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ê¤Þ¤¹¡£

    + +

    °Ê²¼¤Î¤è¤¦¤Ê¥³¥Þ¥ó¥É¤Ç¤³¤Î¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤·¤Þ¤¹:

    + +

    +split-logfile < /logs/multiple_vhost_log +

    + +

    ¤³¤Î¥×¥í¥°¥é¥à¤Ï¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¥í¥°¥Õ¥¡¥¤¥ë¤Î̾Á°¤È¤È¤â¤Ë¼Â¹Ô¤µ¤ì¡¢ +¥í¥°¥Õ¥¡¥¤¥ë¤Ë¸½¤ì¤ë¤½¤ì¤¾¤ì¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈËè¤Ë°ì¤Ä¤Î¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Þ¤¹¡£ +¤½¤ì¤¾¤ì¤Î¥Õ¥¡¥¤¥ë¤Ï ¥Û¥¹¥È̾.log ¤È¤¤¤¦Ì¾Á°¤Ë¤Ê¤ê¤Þ¤¹¡£

    + +
    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/fd-limits.html.ko.euc-kr b/docs/manual/vhosts/fd-limits.html.ko.euc-kr new file mode 100644 index 00000000..800359fb --- /dev/null +++ b/docs/manual/vhosts/fd-limits.html.ko.euc-kr @@ -0,0 +1,122 @@ + + + +ÆÄÀϱâ¼úÀÚ(file descriptor) ÇÑ°è - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    ÆÄÀϱâ¼úÀÚ(file descriptor) ÇÑ°è

    +
    +

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

    +
    + + +

    °¡»óÈ£½ºÆ®¸¦ ¸¹ÀÌ »ç¿ëÇÏ°í °¢ °¡»óÈ£½ºÆ®¿¡ ¼­·Î ´Ù¸¥ + ·Î±×ÆÄÀÏÀ» ÁöÁ¤Çϸé, ¾ÆÆÄÄ¡°¡ »ç¿ë°¡´ÉÇÑ ÆÄÀϱâ¼úÀÚ(file + descriptor, ÈçÈ÷ ÆÄÀÏÇÚµé(file handle)À̶ó°í + ºÎ¸§)¸¦ ´Ù ½á¹ö¸± ¼ö ÀÖ´Ù. ¾ÆÆÄÄ¡°¡ »ç¿ëÇÏ´Â ÆÄÀϱâ¼úÀÚÀÇ + ÃÑ °³¼ö´Â ¿À·ù ·Î±×ÆÄÀÏ´ç ÇÑ°³, ´Ù¸¥ ·Î±×ÆÄÀÏ Áö½Ã¾î´ç + ÇÑ°³, Ãß°¡·Î ³»ºÎ¿ëµµ·Î 10-20°³¸¦ ´õÇÑ ¼ö´Ù. À¯´Ð½º ¿î¿µÃ¼Á¦´Â + ÇÁ·Î¼¼½º°¡ »ç¿ëÇÒ ¼ö ÀÖ´Â ÆÄÀϱâ¼úÀÚ °³¼ö¸¦ Á¦ÇÑÇÑ´Ù. ÀÌ ÇÑ°è´Â + º¸Åë 64°³·Î, º¸Åë À̺¸´Ù Å« hard-limit±îÁö ´Ã¸± ¼ö ÀÖ´Ù.

    + +

    ¾ÆÆÄÄ¡´Â ÀÌ ÇѰ踦 ÇÊ¿äÇѸ¸Å­ ´Ã¸®·Á°í ÇÏÁö¸¸, ½ÇÆÐÇÏ´Â + °æ¿ì°¡ ÀÖ´Ù:

    + +
      +
    1. ½Ã½ºÅÛÀÌ setrlimit() ½Ã½ºÅÛÈ£ÃâÀ» + Á¦°øÇÏÁö ¾Ê´Â´Ù.
      2. + +
    2. (Solaris 2.3°ú °°ÀÌ) ½Ã½ºÅÛ¿¡¼­ + setrlimit(RLIMIT_NOFILE) ÇÔ¼ö°¡ µ¿ÀÛÇÏÁö + ¾Ê´Â´Ù.
      3. + +
    3. ÇÊ¿äÇÑ ÆÄÀϱâ¼úÀÚ °³¼ö°¡ hard limit º¸´Ù ¸¹´Ù.
      4. + +
    4. (Solaris 2) ½Ã½ºÅÛÀÌ stdio ½ºÆ®¸²À» 256ÀÌÇÏÀÇ + ÆÄÀϱâ¼úÀÚ¸¸À» »ç¿ëÇϵµ·Ï Á¦ÇÑÇÏ´Â µî ÆÄÀϱâ¼úÀÚ¿¡ + Á¦¾àÀ» °¡ÇÑ´Ù.
      5. +
    + +

    ÀÌ °æ¿ì ÇØ°áÃ¥Àº:

    + +
      +
    • ·Î±×ÆÄÀÏ °³¼ö¸¦ ÁÙÀδÙ. <VirtualHost> ¼½¼Ç¿¡¼­ ·Î±×ÆÄÀÏÀ» + ÁöÁ¤ÇÏÁö ¾Ê°í ÁÖ ·Î±×ÆÄÀÏÀ» »ç¿ëÇÑ´Ù. (´õ ÀÚ¼¼ÇÑ ¹æ¹ýÀº + ¾Æ·¡ ·Î±×ÆÄÀÏ ³ª´©±â¸¦ Âü°íÇ϶ó.)
      • + +
    • + »ç¿ëÇÏ´Â ½Ã½ºÅÛÀÌ (À§ÀÇ) 1¹ø°³ª 2¹ø° °æ¿ì¿¡ ÇØ´çÇÑ´Ù¸é, + ´ÙÀ½°ú °°Àº ½ºÅ©¸³Æ®·Î ¾ÆÆÄÄ¡¸¦ ½ÃÀÛÇϱâ Àü¿¡ ÆÄÀϱâ¼úÀÚ + ÇѰ踦 ´Ã¸°´Ù. + +

      + #!/bin/sh
      + ulimit -S -n 100
      + exec httpd       +

      +
      • +
    + +
    +
    top
    +
    +

    ·Î±×ÆÄÀÏ ³ª´©±â

    + +

    ¿©·¯ °¡»óÈ£½ºÆ®°¡ °°Àº ·Î±×ÆÄÀÏÀ» »ç¿ëÇÑ´Ù¸é ³ªÁß¿¡ °¢ +°¡»óÈ£½ºÆ®ÀÇ Åë°èºÐ¼®À» À§ÇØ ·Î±×ÆÄÀÏÀ» ³ª´©°í ½ÍÀ» °ÍÀÌ´Ù. +ÀÌ ÀÛ¾÷Àº ´ÙÀ½°ú °°ÀÌ ÇÒ ¼ö ÀÖ´Ù.

    + +

    ¸ÕÀú ·Î±× Ç׸ñ¿¡ °¡»óÈ£½ºÆ® Á¤º¸¸¦ Ãß°¡ÇÑ´Ù. À̸¦ À§ÇØ +LogFormat +Áö½Ã¾î¿Í %v º¯¼ö¸¦ »ç¿ëÇÑ´Ù. ÀÌ º¯¼ö¸¦ ·Î±× +Çü½Ä¹®ÀÚ¿­ ¾Õ¿¡ Ãß°¡ÇÑ´Ù:

    + +

    +LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost
    +CustomLog logs/multiple_vhost_log vhost +

    + +

    ±×·¯¸é common ·Î±×Çü½Ä ¾Õ¿¡ (ServerName Áö½Ã¾î¿¡ ³ª¿À´Â) Á¤±Ô +°¡»óÈ£½ºÆ®¸¦ Æ÷ÇÔÇÏ¿© ·Î±×ÆÄÀÏÀ» ±â·ÏÇÑ´Ù. (·Î±×ÆÄÀÏ +»ç¿ëÀÚÁ¤ÀÇ¿¡ °üÇÑ ³»¿ëÀº »ç¿ëÀÚÁ¤ÀÇ ·Î±×Çü½ÄÀ» +Âü°íÇ϶ó.)

    + +

    ·Î±×ÆÄÀÏÀ» (°¡»óÈ£½ºÆ®´ç ÇÑ ÆÄÀϾ¿) ³ª´©°í ½Í´Ù¸é split-logfile ÇÁ·Î±×·¥À» +»ç¿ëÇÑ´Ù. ÀÌ ÇÁ·Î±×·¥Àº ¾ÆÆÄÄ¡ ¹èÆ÷º»ÀÇ support +µð·ºÅ丮¿¡ ÀÖ´Ù.

    + +

    ´ÙÀ½°ú °°ÀÌ ÇÁ·Î±×·¥À» ½ÇÇàÇÑ´Ù:

    + +

    +split-logfile < /logs/multiple_vhost_log +

    + +

    °¡»óÈ£½ºÆ® ·Î±×ÆÄÀÏÀ» °¡Áö°í ÀÌ ÇÁ·Î±×·¥À» ½ÇÇàÇÏ¸é ·Î±×ÆÄÀÏ¿¡ +³ª¿À´Â °¢ °¡»óÈ£½ºÆ®´ç ÆÄÀÏÀ» Çϳª¾¿ ¸¸µç´Ù. °¢°¢ÀÇ ÆÄÀϸíÀº +hostname.logÀÌ´Ù.

    + +
    +
    +

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

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/index.html b/docs/manual/vhosts/index.html new file mode 100644 index 00000000..76ef9af7 --- /dev/null +++ b/docs/manual/vhosts/index.html @@ -0,0 +1,23 @@ +URI: index.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: index.html.ru.koi8-r +Content-Language: ru +Content-type: text/html; charset=KOI8-R diff --git a/docs/manual/vhosts/index.html.de b/docs/manual/vhosts/index.html.de new file mode 100644 index 00000000..7c9da916 --- /dev/null +++ b/docs/manual/vhosts/index.html.de @@ -0,0 +1,110 @@ + + + +Apache-Dokumentation zu virtuellen Hosts - Apache HTTP Server + + + + +
    +

    Module | Direktiven | FAQ | Glossar | Seitenindex

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Apache-Dokumentation zu virtuellen Hosts

    +
    +

    Verfügbare Sprachen:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + +

    Der Begriff virtueller Host (Anm.d.Ü.: engl. 'virtual + host') bezieht sich auf die Praxis, mehr als ein Webangebot + (z.B. www.company1.com und www.company2.com) + auf einer einzigen Maschine zu betreiben. Virtuelle Hosts können + "IP-basiert" sein, was bedeutet, dass jedes + Webangebot eine andere IP besitzt, oder "Namens-basiert", was bedeutet, dass + unter jeder IP-Adresse mehrere Namen laufen. Die Tatsache, dass sie + auf dem gleichen physischen Server laufen, ist für den Endbenutzer + nicht offensichtlich.

    + +

    Der Apache war einer der ersten Server, der IP-basierte + virtuelle Hosts von Haus aus direkt unterstützt hat. Seit Version 1.1 + unterstützt der Apache sowohl IP-basierte als auch namensbasierte + virtuelle Hosts (vhosts). Letzteres wird zuweilen auch + Host-basiert oder non-IP-Virtual-Host genannt.

    + +

    Nachfolgend finden Sie eine Liste von Dokumenten, die alle Details + der Unterstützung von virtuellen Hosts ab Apache Version 1.3 + beschreiben.

    + +
    + +
    top
    +
    +

    Unterstützung virtueller Hosts

    + + + +
    top
    +
    +

    Konfigurationsdirektiven

    + + + +

    Bei der Suche von Fehlern in Ihrer Virtual-Host-Konfiguration ist + die Apache-Befehlszeilenoption -S möglicherweise + hilfreich. Geben Sie dazu den folgenden Befehl ein:

    + +

    + /usr/local/apache2/bin/httpd -S +

    + +

    Diese Anweisung gibt eine Beschreibung aus, wie der Apache die + Konfigurationsdatei analysiert hat. Eine sorgfältige + Überprüfung der IP-Adressen und Servernamen kann helfen, + Konfigurationsfehler aufzudecken. (Lesen Sie die Dokumentation zum + httpd-Programm für weitere + Befehlszeilenoptionen.)

    +
    +
    +

    Verfügbare Sprachen:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/index.html.en b/docs/manual/vhosts/index.html.en new file mode 100644 index 00000000..40c460e5 --- /dev/null +++ b/docs/manual/vhosts/index.html.en @@ -0,0 +1,110 @@ + + + +Apache Virtual Host documentation - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Apache Virtual Host documentation

    +
    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + + +

    The term Virtual Host refers to the practice of + running more than one web site (such as + www.company1.com and www.company2.com) + on a single machine. Virtual hosts can be "IP-based", meaning that you have a + different IP address for every web site, or "name-based", meaning that you have + multiple names running on each IP address. The fact that they + are running on the same physical server is not apparent to the + end user.

    + +

    Apache was one of the first servers to support IP-based + virtual hosts right out of the box. Versions 1.1 and later of + Apache support both IP-based and name-based virtual hosts + (vhosts). The latter variant of virtual hosts is sometimes also + called host-based or non-IP virtual hosts.

    + +

    Below is a list of documentation pages which explain all + details of virtual host support in Apache version 1.3 and + later.

    + +
    + +
    top
    +
    +

    Virtual Host Support

    + + + +
    top
    +
    +

    Configuration directives

    + + + +

    If you are trying to debug your virtual host configuration, you + may find the Apache -S command line switch + useful. That is, type the following command:

    + +

    + /usr/local/apache2/bin/httpd -S +

    + +

    This command will dump out a description of how Apache parsed + the configuration file. Careful examination of the IP addresses and + server names may help uncover configuration mistakes. (See + the docs for the httpd program for + other command line options)

    + +
    +
    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/index.html.fr b/docs/manual/vhosts/index.html.fr new file mode 100644 index 00000000..96edb164 --- /dev/null +++ b/docs/manual/vhosts/index.html.fr @@ -0,0 +1,111 @@ + + + +Documentation sur les serveurs virtuels Apache - Serveur Apache HTTP + + + + +
    +

    Modules | Directives | FAQ | Glossaire | Plan du site

    +

    Serveur Apache HTTP Version 2.2

    +
    +
    <-
    +

    Documentation sur les serveurs virtuels Apache

    +
    +

    Langues Disponibles:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + + +

    Le principe des Serveurs Virtuels consiste à + faire fonctionner un ou plusieurs serveurs Web (comme + www.company1.com et www.company2.com) + sur une même machine. Les serveurs virtuels peuvent être soit + "par-IP" où une adresse IP est + attribuée pour chaque serveur Web, soit "par-nom" où plusieurs noms de domaine se côtoient sur + des mêmes adresses IP. L'utilisateur final ne perçoit pas + qu'en fait il s'agit d'un même serveur physique.

    + +

    Apache a été le précurseur des serveurs proposant cette + méthode de serveurs virtuels basés sur les adresses IP. Ses + versions 1.1 et suivantes ont toujours proposées ces deux + méthodes de serveurs virtuels par-IP et par-nom. Cette + deuxième méthode est parfois également appelée host-based + ou serveur virtuel non-IP.

    + +

    Vous trouverez ci-dessous une liste documentaire qui vous + expliquera en détails le fonctionnement des serveurs virtuels + sous Apache 1.3 et ses versions suivantes.

    + +
    + +
    top
    +
    +

    Support des serveurs virtuels

    + + + +
    top
    +
    +

    Directives de configuration

    + + + +

    Pour vérifier et analyser la configuration de vos serveurs + virtuels, vous pouvez utiliser l'argument -S sur + la ligne de commande lançant le programme Apache comme ceci :

    + +

    + /usr/local/apache2/bin/httpd -S +

    + +

    Cette commande affichera dans le détail comment Apache a + traité son fichier de configuration. Les erreurs de configuration + peuvent être corrigées par l'examen attentif des adresses IP et + des noms de serveurs. (Consultez la documentation du programme + httpd pour les autres arguments de la ligne de + commande)

    + +
    +
    +

    Langues Disponibles:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/index.html.ja.euc-jp b/docs/manual/vhosts/index.html.ja.euc-jp new file mode 100644 index 00000000..c49dfd92 --- /dev/null +++ b/docs/manual/vhosts/index.html.ja.euc-jp @@ -0,0 +1,105 @@ + + + +Apache ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈÀâÌÀ½ñ - Apache HTTP ¥µ¡¼¥Ð + + + + +
    +

    ¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

    +

    Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

    +
    +
    <-
    +

    Apache ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥ÈÀâÌÀ½ñ

    +
    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + + +

    ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤È¤¤¤¦ÍѸì¤Ï¡¢1 Âæ¤Î¥Þ¥·¥ó¾å¤Ç + (www.company1.com and www.company2.com ¤Î¤è¤¦¤Ê) + Æó¤Ä°Ê¾å¤Î¥¦¥§¥Ö¥µ¥¤¥È¤ò°·¤¦±¿ÍÑÊýË¡¤Î¤³¤È¤ò»Ø¤·¤Þ¤¹¡£ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¤Ï¡¢³Æ¥¦¥§¥Ö¥µ¥¤¥È¤Ë°ã¤¦ IP ¥¢¥É¥ì¥¹¤¬¤¢¤ë + ¡ÖIP ¥Ù¡¼¥¹¡×¤È¡¢¤½¤ì¤¾¤ì¤Î IP ¥¢¥É¥ì¥¹¤Ë + Ê£¿ô¤Î̾Á°¤¬¤¢¤ë¡Ö̾Á°¥Ù¡¼¥¹¡×¤È¤¬¤¢¤ê¤Þ¤¹¡£ + Ê£¿ô¤Î¥µ¥¤¥È¤¬ÊªÍýŪ¤ËƱ¤¸¥µ¡¼¥Ð¤Ç°·¤ï¤ì¤Æ¤¤¤ë¡¢¤È¤¤¤¦¤³¤È¤Ï¥¨¥ó¥É¥æ¡¼¥¶¤Ë¤Ï + ÌÀ¤é¤«¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£

    + +

    Apache ¤Ï¡¢Æä˼ê¤òÆþ¤ì¤Ê¤¤¾õÂÖ¤Ç IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È + ¤ò¥µ¥Ý¡¼¥È¤·¤¿ºÇ½é¤Î¥µ¡¼¥Ð¤Î°ì¤Ä¤Ç¤¹¡£¥Ð¡¼¥¸¥ç¥ó 1.1 °Ê¹ß¤Î Apache + ¤Ç¤Ï¡¢IP ¥Ù¡¼¥¹¤È¥Í¡¼¥à¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎξÊý¤ò¥µ¥Ý¡¼¥È + ¤·¤Æ¤¤¤Þ¤¹¡£¥Í¡¼¥à¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ï¡¢¥Û¥¹¥È¥Ù¡¼¥¹¤¢¤ë¤¤¤Ï + Èó IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤È¸Æ¤Ð¤ì¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£

    + +

    °Ê²¼¤Î¥Ú¡¼¥¸¤Ç¤Ï¡¢Apache ¥Ð¡¼¥¸¥ç¥ó 1.3 + °Ê¹ß¤Ç¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¥µ¥Ý¡¼¥È¤Ë¤Ä¤¤¤Æ¤Î¾ÜºÙ¤òÀâÌÀ¤·¤Þ¤¹¡£

    + +
    + +
    top
    +
    +

    ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¥µ¥Ý¡¼¥È

    + + + +
    top
    +
    +

    ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö

    + + + +

    ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÀßÄê¤Î¥Ç¥Ð¥Ã¥°¤ò¤¹¤ë¤Ë¤Ï + Apache ¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¥¹¥¤¥Ã¥Á -S ¤¬ÊØÍø¤Ç¤¹¡£ + ¤Ä¤Þ¤ê¡¢°Ê²¼¤Î¥³¥Þ¥ó¥É¤òÆþÎϤ·¤Þ¤¹:

    + +

    + /usr/local/apache2/bin/httpd -S +

    + +

    ¤³¤Î¥³¥Þ¥ó¥É¤Ï Apache ¤¬ÀßÄê¥Õ¥¡¥¤¥ë¤ò¤É¤¦²òÀϤ·¤¿¤«¤Ë¤Ä¤¤¤Æ½ÐÎϤ·¤Þ¤¹¡£ + IP ¥¢¥É¥ì¥¹¤È¥µ¡¼¥Ð̾¤òÃí°Õ¿¼¤¯Ä´¤Ù¤ì¤Ð¡¢ + ÀßÄê¤Î´Ö°ã¤¤¤ò¸«¤Ä¤±¤ë½õ¤±¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£ + (¾¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¤Î¥ª¥×¥·¥ç¥ó¤Ï httpd + ¥×¥í¥°¥é¥à¤ÎÀâÌÀʸ½ñ¤ò¸«¤Æ¤¯¤À¤µ¤¤)

    + +
    +
    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/index.html.ko.euc-kr b/docs/manual/vhosts/index.html.ko.euc-kr new file mode 100644 index 00000000..de49c5b2 --- /dev/null +++ b/docs/manual/vhosts/index.html.ko.euc-kr @@ -0,0 +1,108 @@ + + + +¾ÆÆÄÄ¡ °¡»óÈ£½ºÆ® ¹®¼­ - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    ¾ÆÆÄÄ¡ °¡»óÈ£½ºÆ® ¹®¼­

    +
    +

    °¡´ÉÇÑ ¾ð¾î:  de  | + en  | + fr  | + ja  | + ko  | + ru 

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

    °¡»óÈ£½ºÆ® (Virtual Host)´Â ÇÑ ÄÄÇ»ÅÍ¿¡¼­ + ¿©·¯ À¥»çÀÌÆ®¸¦ (¿¹¸¦ µé¾î, www.company1.com°ú + www.company2.com) ¼­ºñ½ºÇÔÀ» ¶æÇÑ´Ù. + °¡»óÈ£½ºÆ®¿¡´Â °¢ À¥»çÀÌÆ®¸¶´Ù ´Ù¸¥ IP ÁÖ¼Ò¸¦ »ç¿ëÇÏ´Â + "IP±â¹Ý (IP-based)" ¹æ½Ä°ú ÇÑ + IP ÁÖ¼Ò´ç ¿©·¯ À̸§À» °¡Áö´Â "À̸§±â¹Ý (name-based)" ¹æ½ÄÀÌ + ÀÖ´Ù. ¿©·¯ »çÀÌÆ®µéÀÌ °°Àº ¼­¹ö¿¡¼­ µ¹°íÀÖ´Ù´Â »ç½ÇÀ» À¥»ç¿ëÀÚ´Â + ´«Ä¡Ã¤Áö ¸øÇÑ´Ù.

    + +

    ¾ÆÆÄÄ¡´Â ±âº»À¸·Î IP±â¹Ý °¡»óÈ£½ºÆ®¸¦ Áö¿øÇÑ ÃÊâ±â + ¼­¹öµéÁß Çϳª´Ù. ¾ÆÆÄÄ¡ ¹öÀü 1.1 ÀÌ»óÀº IP±â¹Ý°ú À̸§±â¹Ý + °¡»óÈ£½ºÆ®¸¦ ¸ðµÎ Áö¿øÇÑ´Ù. À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ + È£½ºÆ®±â¹Ý (host-based) ¶Ç´Â ºñIP °¡»óÈ£½ºÆ® + (non-IP virtual hosts)¶ó°íµµ ºÎ¸¥´Ù.

    + +

    ´ÙÀ½Àº ¾ÆÆÄÄ¡ ¹öÀü 1.3 ÀÌ»óÀÇ °¡»óÈ£½ºÆ® Áö¿øÀ» ÀÚ¼¼È÷ + ¼³¸íÇÑ ¹®¼­µéÀÌ´Ù.

    + +
    + +
    top
    +
    +

    °¡»óÈ£½ºÆ® Áö¿ø

    + + + +
    top
    +
    +

    ¼³Á¤ Áö½Ã¾î

    + + + +

    °¡»óÈ£½ºÆ® ¼³Á¤À» Å×½ºÆ®ÇÒ¶§ ¾ÆÆÄÄ¡ÀÇ -S + ¸í·ÉÇà ¿É¼ÇÀÌ À¯¿ëÇÏ´Ù. Áï, ´ÙÀ½°ú °°ÀÌ ½ÇÇàÇÑ´Ù:

    + +

    + /usr/local/apache2/bin/httpd -S +

    + +

    ÀÌ ¸í·É¾î´Â ¾ÆÆÄÄ¡°¡ ÀÐÀº ¼³Á¤ÆÄÀÏ¿¡ ´ëÇÑ + Á¤º¸¸¦ Ãâ·ÂÇÑ´Ù. IP ÁÖ¼Ò¿Í ¼­¹ö¸íÀ» ÀÚ¼¼È÷ »ìÆ캸¸é ¼³Á¤¿¡¼­ + ½Ç¼ö¸¦ ¹ß°ßÇϴµ¥ µµ¿òÀÌ µÉ °ÍÀÌ´Ù. (´Ù¸¥ ¸í·ÉÇà ¿É¼ÇµéÀº + httpd ÇÁ·Î±×·¥ ¹®¼­¸¦ + Âü°íÇ϶ó.)

    + +
    +
    +

    °¡´ÉÇÑ ¾ð¾î:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/index.html.ru.koi8-r b/docs/manual/vhosts/index.html.ru.koi8-r new file mode 100644 index 00000000..42e86f00 --- /dev/null +++ b/docs/manual/vhosts/index.html.ru.koi8-r @@ -0,0 +1,105 @@ + + + +äÏËÕÍÅÎÔÁÃÉÑ ÐÏ ×ÉÒÔÕÁÌØÎÙÍ ÈÏÓÔÁÍ × Apache - HTTP ÓÅÒ×ÅÒ Apache + + + + +
    +

    íÏÄÕÌÉ | äÉÒÅËÔÉ×Ù | FAQ | çÌÏÓÓÁÒÉÊ | ëÁÒÔÁ ÓÁÊÔÁ

    +

    HTTP ÓÅÒ×ÅÒ Apache ×ÅÒÓÉÉ 2.2

    +
    +
    <-
    +

    äÏËÕÍÅÎÔÁÃÉÑ ÐÏ ×ÉÒÔÕÁÌØÎÙÍ ÈÏÓÔÁÍ × Apache

    +
    +

    äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + + +

    ôÅÒÍÉÎ ×ÉÒÔÕÁÌØÎÙÊ ÈÏÓÔ ÏÔÎÏÓÉÔÓÑ Ë ÐÒÁËÔÉËÅ + ÒÁÚÍÅÝÅÎÉÑ ÂÏÌÅÅ ÞÅÍ ÏÄÎÏÇÏ ×ÅÂ-ÓÁÊÔÁ (ÎÁÐÒÉÍÅÒ, + www.company1.com É www.company2.com) + ÎÁ ÏÄÎÏÊ ÍÁÛÉÎÅ. ÷ÉÒÔÕÁÌØÎÙÊ ÈÏÓÔ ÍÏÖÅÔ ÂÙÔØ ËÁË «ÐÒÉ×ÑÚÁÎÎÙÍ Ë IP-ÁÄÒÅÓÕ», ÞÔÏ ÏÚÎÁÞÁÅÔ + ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÏÔÄÅÌØÎÏÇÏ IP ÁÄÒÅÓÁ ÄÌÑ ËÁÖÄÏÇÏ ÓÁÊÔÁ, ÌÉÂÏ «ÐÒÉ×ÑÚÁÎÎÙÍ Ë ÉÍÅÎÉ», ÐÏÚ×ÏÌÑÑ ×ÁÍ + ÉÍÅÔØ ÎÅÓËÏÌØËÏ ÒÁÚÌÉÞÎÙÈ ÉͣΠÄÌÑ ËÁÖÄÏÇÏ IP-ÁÄÒÅÓÁ. æÁËÔ ÔÏÇÏ, + ÞÔÏ ÜÔÉ ÓÁÊÔÙ ÒÁÂÏÔÁÀÔ ÎÁ ÏÄÎÏÍ É ÔÏÍ ÖÅ ÆÉÚÉÞÅÓËÏÍ ÓÅÒ×ÅÒÅ, + ÎÅ ÏÞÅ×ÉÄÅÎ ËÏÎÅÞÎÙÍ ÐÏÌØÚÏ×ÁÔÅÌÑÍ.

    + +

    Apache ÂÙÌ ÏÄÎÉÍ ÉÚ ÐÅÒ×ÙÈ ÓÅÒ×ÅÒÏ×, ËÏÔÏÒÙÊ ÐÏÄÄÅÒÖÉ×ÁÌ IP-ÐÒÉ×ÑÚÁÎÎÙÅ + ×ÉÒÔÕÁÌØÎÙÅ ÈÏÓÔÙ. ÷ÅÒÓÉÉ Apache 1.1 É ÂÏÌÅÅ ÎÏ×ÙÅ ÐÏÄÄÅÒÖÉ×ÁÀÔ ËÁË + IP-ÐÒÉ×ÑÚÁÎÎÙÅ, ÔÁË É ×ÉÒÔÕÁÌØÎÙÅ ÈÏÓÔÙ, ÏÐÒÅÄÅÌÑÅÍÙÅ ÐÏ ÉÍÅÎÉ. + ðÏÓÌÅÄÎÉÊ ×ÁÒÉÁÎÔ ×ÉÒÔÕÁÌØÎÙÈ ÈÏÓÔÏ× ÔÁËÖÅ ÉÎÏÇÄÁ + ÎÁÚÙ×ÁÀÔ ÈÏÓÔ-ÐÒÉ×ÑÚÁÎÎÙÍÉ ÉÌÉ ÎÅ-IP ×ÉÒÔÕÁÌØÎÙÍÉ ÈÏÓÔÁÍÉ.

    + +

    îÉÖÅ ×Ù ×ÉÄÉÔÅ ÓÐÉÓÏË ÄÏËÕÍÅÎÔÏ×, ËÏÔÏÒÙÅ ÄÅÔÁÌØÎÏ ÏÂßÑÓÎÑÀÔ + ÐÏÄÄÅÒÖËÕ ×ÉÒÔÕÁÌØÎÙÈ ÈÏÓÔÏ× × Apache 1.3 É ×ÙÛÅ.

    + +
    + +
    top
    +
    +

    ðÏÄÄÅÒÖËÁ ×ÉÒÔÕÁÌØÎÙÈ ÈÏÓÔÏ×

    + + + +
    top
    +
    +

    ëÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÄÉÒÅËÔÉ×Ù

    + + + +

    åÓÌÉ ×Ù ÐÙÔÁÅÔÅÓØ ÏÔÌÁÖÉ×ÁÔØ ×ÁÛÕ ËÏÎÆÉÇÕÒÁÃÉÀ Ó ×ÉÒÔÕÁÌØÎÙÍÉ ÈÏÓÔÁÍÉ, ÔÏ + ËÌÀÞ ÄÌÑ ÚÁÐÕÓËÁ Apache ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ -S ÂÕÄÅÔ ËÒÁÊÎÅ ÐÏÌÅÚÅÎ. + ôÏ ÅÓÔØ, ÓÌÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÓÌÅÄÕÀÝÕÀ ËÏÍÁÎÄÕ:

    + +

    + /usr/local/apache2/bin/httpd -S +

    + +

    üÔÁ ËÏÍÁÎÄÁ ÒÁÓÐÅÞÁÔÁÅÔ ÏÐÉÓÁÎÉÅ ÔÏÇÏ, ËÁË Apache ÒÁÚÏÂÒÁÌ + ÆÁÊÌ ËÏÎÆÉÇÕÒÁÃÉÉ. ôÝÁÔÅÌØÎÏÅ ÉÚÕÞÅÎÉÅ IP ÁÄÒÅÓÏ× É ÉͣΠÓÅÒ×ÅÒÏ× + ÐÏÍÏÖÅÔ ÎÁÊÔÉ ÏÛÉÂËÉ ËÏÎÆÉÇÕÒÁÃÉÉ. (óÍÏÔÒÉÔÅ ÔÁËÖÅ + ÄÏËÕÍÅÎÔÁÃÉÀ Ë ÐÒÏÇÒÁÍÍÅ httpd ÄÌÑ + ÉÚÕÞÅÎÉÑ ÄÒÕÇÉÈ ÐÁÒÁÍÅÔÒÏ× ÄÌÑ ÚÁÐÕÓËÁ ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ.)

    + +
    +
    +

    äÏÓÔÕÐÎÙÅ ÑÚÙËÉ:  de  | + en  | + fr  | + ja  | + ko  | + ru 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/ip-based.html b/docs/manual/vhosts/ip-based.html new file mode 100644 index 00000000..c18fe7e0 --- /dev/null +++ b/docs/manual/vhosts/ip-based.html @@ -0,0 +1,15 @@ +URI: ip-based.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: ip-based.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: ip-based.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: ip-based.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/vhosts/ip-based.html.en b/docs/manual/vhosts/ip-based.html.en new file mode 100644 index 00000000..5bdf0ebb --- /dev/null +++ b/docs/manual/vhosts/ip-based.html.en @@ -0,0 +1,162 @@ + + + +Apache IP-based Virtual Host Support - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Apache IP-based Virtual Host Support

    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    +
    + +
    top
    +
    +

    System requirements

    + +

    As the term IP-based indicates, the server + must have a different IP address for each IP-based + virtual host. This can be achieved by the machine + having several physical network connections, or by use of + virtual interfaces which are supported by most modern operating + systems (see system documentation for details, these are + frequently called "ip aliases", and the "ifconfig" command is + most commonly used to set them up).

    + +
    top
    +
    +

    How to set up Apache

    + +

    There are two ways of configuring apache to support multiple + hosts. Either by running a separate httpd daemon for + each hostname, or by running a single daemon which supports all the + virtual hosts.

    + +

    Use multiple daemons when:

    + +
      +
    • There are security partitioning issues, such as company1 + does not want anyone at company2 to be able to read their + data except via the web. In this case you would need two + daemons, each running with different User, Group, Listen, and ServerRoot settings.
      • + +
    • You can afford the memory and file descriptor + requirements of listening to every IP alias on the + machine. It's only possible to Listen to the "wildcard" + address, or to specific addresses. So if you have a need to + listen to a specific address for whatever reason, then you + will need to listen to all specific addresses. (Although one + httpd could listen to N-1 of the addresses, and another could + listen to the remaining address.)
      • +
    + +

    Use a single daemon when:

    + +
      +
    • Sharing of the httpd configuration between virtual hosts + is acceptable.
      • + +
    • The machine services a large number of requests, and so + the performance loss in running separate daemons may be + significant.
      • +
    + +
    top
    +
    +

    Setting up multiple daemons

    + +

    Create a separate httpd installation for each + virtual host. For each installation, use the Listen directive in the + configuration file to select which IP address (or virtual host) + that daemon services. e.g.

    + +

    + Listen www.smallco.com:80 +

    + +

    It is recommended that you use an IP address instead of a + hostname (see DNS caveats).

    + +
    top
    +
    +

    Setting up a single daemon + with virtual hosts

    + +

    For this case, a single httpd will service + requests for the main server and all the virtual hosts. The VirtualHost directive + in the configuration file is used to set the values of ServerAdmin, ServerName, DocumentRoot, ErrorLog and TransferLog + or CustomLog + configuration directives to different values for each virtual + host. e.g.

    + +

    + <VirtualHost www.smallco.com>
    + ServerAdmin webmaster@mail.smallco.com
    + DocumentRoot /groups/smallco/www
    + ServerName www.smallco.com
    + ErrorLog /groups/smallco/logs/error_log
    + TransferLog /groups/smallco/logs/access_log
    + </VirtualHost>
    +
    + <VirtualHost www.baygroup.org>
    + ServerAdmin webmaster@mail.baygroup.org
    + DocumentRoot /groups/baygroup/www
    + ServerName www.baygroup.org
    + ErrorLog /groups/baygroup/logs/error_log
    + TransferLog /groups/baygroup/logs/access_log
    + </VirtualHost> +

    + +

    It is recommended that you use an IP address instead of a + hostname (see DNS caveats).

    + +

    Almost any configuration directive can be + put in the VirtualHost directive, with the exception of + directives that control process creation and a few other + directives. To find out if a directive can be used in the + VirtualHost directive, check the Context using the + directive index.

    + +

    SuexecUserGroup + may be used inside a + VirtualHost directive if the suEXEC + wrapper is used.

    + +

    SECURITY: When specifying where to write log files, + be aware of some security risks which are present if anyone + other than the user that starts Apache has write access to the + directory where they are written. See the security tips document + for details.

    + +
    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/ip-based.html.fr b/docs/manual/vhosts/ip-based.html.fr new file mode 100644 index 00000000..d442c40b --- /dev/null +++ b/docs/manual/vhosts/ip-based.html.fr @@ -0,0 +1,182 @@ + + + +Support Apache des serveurs virtuels par IP - Serveur Apache HTTP + + + + +
    +

    Modules | Directives | FAQ | Glossaire | Plan du site

    +

    Serveur Apache HTTP Version 2.2

    +
    +
    <-
    +

    Support Apache des serveurs virtuels par IP

    +
    +

    Langues Disponibles:  en  | + fr  | + ja  | + ko 

    +
    +
    + +
    top
    +
    +

    Système requis

    + +

    Comme l'indique le terme par IP, le serveur + doit disposer de différentes adresses IP pour chaque + serveur virtuel par IP. La machine peut posséder + plusieurs connexions physiques au réseau, ou utiliser des + interfaces virtuelles qui sont supportées par la plupart des + systèmes d'exploitation modernes (Consultez la documentation des + systèmes d'exploitation pour plus de détails, notamment les "alias + IP" et la commande "ifconfig" pour les activer).

    + +
    top
    +
    +

    Comment configurer Apache

    + +

    Il y a deux manières de configurer Apache pour le support de + multiples serveurs virtuels. Il suffit soit de faire tourner un + processus résident httpd pour chaque nom de + domaine, soit de faire tourner un unique processus résident qui + gère tous les serveurs virtuels.

    + +

    Utilisez des processus résidents multiples lorsque :

    + +
      +
    • il y a des problèmes de répartition de sécurité, tels + qu'une entreprise1 ne souhaite que personne d'une entreprise2 + ne puisse lire ses données excepté via le Web. Dans ce cas, + vous aurez besoin de deux processus résidents, chacun fonctionnant + avec des paramètres User, + Group, + Listen, et + ServerRoot différents.
      • + +
    • vous disposez suffisamment de mémoire et de + descripteurs de fichiers + pour l'écoute de chaque alias IP de la machine. Il est seulement + possible d'appliquer la directive + Listen, soit sur toutes + les adresses avec le joker "*", soit uniquement sur des adresses + spécifiques. Donc, si vous avez besoin d'écouter une adresse + en particulier, vous devrez le faire pour l'ensemble des + autres adresses (Bien qu'il soit plus simple de lancer un + processus httpd pour écouter N-1 adresses, + et un autre pour l'adresse restante).
      • +
    + +

    Utilisez un unique processus résident lorsque :

    + +
      +
    • le partage de la configuration httpd entre les serveurs + virtuels est acceptable.
      • + +
    • la machine assume déjà une grande quantité de requêtes, et + que l'ajout de processus résidents supplémentaires en affecterait + les performances.
      • +
    + +
    top
    +
    +

    Configuration de processus multiples

    + +

    Créez une installation indépendante du programme + httpd pour chaque serveur virtuel. Pour + chacune d'elle, utilisez la directive + Listen dans le fichier + de configuration pour définir l'adresse IP (ou serveur virtuel) + que le processus résident doit gérer. Par exemple :

    + +

    + Listen www.smallco.com:80 +

    + +

    Il est recommandé d'utiliser une adresse IP plutôt qu'un nom + de domaine (consultez Problèmes DNS + avec Apache).

    + +
    top
    +
    +

    Configuration d'un unique processus +résident pour des serveurs virtuels

    + +

    Dans ce cas, un unique processus httpd va gérer les requêtes + pour le serveur principal et tous les serveurs virtuels. Dans le + fichier de configuration, la directive + VirtualHost va servir à + définir les autres directives + ServerAdmin, + ServerName, + DocumentRoot, + ErrorLog et + TransferLog ou + CustomLog avec des + valeurs différentes pour chaque serveur virtuel. Par exemple :

    + +

    + <VirtualHost www.smallco.com>
    + ServerAdmin webmaster@mail.smallco.com
    + DocumentRoot /groups/smallco/www
    + ServerName www.smallco.com
    + ErrorLog /groups/smallco/logs/error_log
    + TransferLog /groups/smallco/logs/access_log
    + </VirtualHost>
    +
    + <VirtualHost www.baygroup.org>
    + ServerAdmin webmaster@mail.baygroup.org
    + DocumentRoot /groups/baygroup/www
    + ServerName www.baygroup.org
    + ErrorLog /groups/baygroup/logs/error_log
    + TransferLog /groups/baygroup/logs/access_log
    + </VirtualHost> +

    + +

    Il est recommandé d'utiliser une adresse IP plutôt qu'un nom + de domaine (consultez Problèmes DNS + avec Apache).

    + +

    Presque toutes les directives de configuration + peuvent être employées dans une directive VirtualHost, à l'exception + des directives qui contrôlent la création du processus et de + quelques autres. Pour connaître celles utilisables dans une + directive VirtualHost, vérifiez leur + Contexte en utilisant + l'Index des directives.

    + + +

    SuexecUserGroup peut être + utilisées à l'intérieur d'une directive VirtualHost si l'exécution se fait + sous suEXEC. (Voir suEXEC).

    + +

    SÉCURITÉ : lorsque vous spécifiez où écrire les + fichiers journaux, soyez attentif aux risques si quelqu'un d'autre + que celui qui a démarré Apache dispose des droits d'écriture + sur l'emplacement de ces fichiers. Consultez les + Conseils sur la sécurité + pour plus de détails.

    + +
    +
    +

    Langues Disponibles:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/ip-based.html.ja.euc-jp b/docs/manual/vhosts/ip-based.html.ja.euc-jp new file mode 100644 index 00000000..fc10309a --- /dev/null +++ b/docs/manual/vhosts/ip-based.html.ja.euc-jp @@ -0,0 +1,158 @@ + + + +Apache ¤Î IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¥µ¥Ý¡¼¥È - Apache HTTP ¥µ¡¼¥Ð + + + + +
    +

    ¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

    +

    Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

    +
    +
    <-
    +

    Apache ¤Î IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¥µ¥Ý¡¼¥È

    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    +
    + +
    top
    +
    +

    ¥·¥¹¥Æ¥àÍ×·ï

    + +

    IP ¥Ù¡¼¥¹ ¤È¤¤¤¦Ì¾Á°¤¬¼¨¤¹¤è¤¦¤Ë¡¢¥µ¡¼¥Ð¤Ë¤Ï + IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤½¤ì¤¾¤ì¤Ë¤Ä¤­¡¢ÊÌ¡¹¤Î IP ¥¢¥É¥ì¥¹¤¬ + ɬÍפǤ¹¡£Ê£¿ô¤ÎʪÍý¥³¥Í¥¯¥·¥ç¥ó¤ò»ý¤Ã¤Æ¤¤¤ë¥Þ¥·¥ó¤òÍÑ°Õ¤¹¤ë¤«¡¢ + ºÇ¶á¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ç¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¥Ð¡¼¥Á¥ã¥ë + ¥¤¥ó¥¿¥Õ¥§¡¼¥¹ (¾ÜºÙ¤Ï¥·¥¹¥Æ¥à¤ÎÀâÌÀ½ñ¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£¤¿¤¤¤Æ¤¤¤Ï + "ip ¥¨¥¤¥ê¥¢¥¹" ¤È¸Æ¤Ð¤ì¤Æ¤¤¤Æ¡¢ÀßÄê¤Ë¤ÏÉáÄÌ "ifconfig" ¥³¥Þ¥ó¥É¤ò + »È¤¤¤Þ¤¹) ¤ò»È¤¦¤«¤Ç¼Â¸½¤Ç¤­¤Þ¤¹¡£

    +
    top
    +
    +

    Apache ¤ÎÀßÄêÊýË¡

    + +

    Ê£¿ô¤Î¥Û¥¹¥È¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤è¤¦¤Ë Apache ¤òÀßÄꤹ¤ëÊýË¡¤Ï + ÆóÄ̤ꤢ¤ê¤Þ¤¹¡£Ê̤Πhttpd ¥Ç¡¼¥â¥ó¤ò³Æ¥Û¥¹¥ÈËè¤Ë¼Â¹Ô¤¹¤ë¤«¡¢ + ¤¹¤Ù¤Æ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò¥µ¥Ý¡¼¥È¤¹¤ë¥Ç¡¼¥â¥ó¤ò°ì¤Ä¼Â¹Ô¤¹¤ë¤«¤Ç¤¹¡£

    + +

    °Ê²¼¤Î¤È¤­¤Ë¤ÏÊ£¿ô¤Î¥Ç¡¼¥â¥ó¤ò»È¤¦¤ÈÎɤ¤¤Ç¤·¤ç¤¦:

    + +
      +
    • ²ñ¼Ò1 ¤Ï¥¦¥§¥Ö·Ðͳ°Ê³°¤Ç¤Ï²ñ¼Ò2 ¤«¤é¤Ï¥Ç¡¼¥¿¤òÆɤޤ줿¤¯¤Ê¤¤¡¢ + ¤È¤¤¤Ã¤¿¥»¥­¥å¥ê¥Æ¥£¤ÎʬΥ¤ÎÌäÂ꤬¤¢¤ë¤È¤­¡£¤³¤Î¾ì¹ç¡¢¤½¤ì¤¾¤ì + User, Group, Listen, ServerRoot ¤ÎÀßÄ꤬°ã¤¦Æó¤Ä¤Î¥Ç¡¼¥â¥ó¤ò + ¼Â¹Ô¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
      • + +
    • ¥Þ¥·¥ó¤Î¤¹¤Ù¤Æ¤Î IP ¥¨¥¤¥ê¥¢¥¹¤ò listen ¤¹¤ë¤À¤±¤Î + ¥á¥â¥ê¤È¥Õ¥¡¥¤¥ëµ­½Ò»Ò¤Î;͵¤¬¤¢¤ë¤È¤­¡£Listen ¤Ï¡Ö¥ï¥¤¥ë¥É¥«¡¼¥É¡× + ¥¢¥É¥ì¥¹¤«¡¢ÆÃÄê¤Î¥¢¥É¥ì¥¹¤Î¤ß¤ò listen ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤Ç¤¹¤«¤é¡¢²¿¤é¤«¤ÎÍýͳ¤ÇÆÃÄê¤Î¥¢¥É¥ì¥¹¤ò listen ¤·¤Ê¤±¤Ð¤Ê¤é¤Ê¤¤ + ¤È¤­¤Ï¡¢¤½¤ÎÆÃÄê¤Î¥¢¥É¥ì¥¹¤ò¤¹¤Ù¤Æ listen ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + (¤¿¤À¤·¡¢°ì¤Ä¤Î httpd ¤¬ N-1 ¸Ä¤Î¥¢¥É¥ì¥¹¤ò listen ¤·¡¢ + Ê̤Πhttpd ¤¬»Ä¤ê¤Î¥¢¥É¥ì¥¹¤ò listen ¤¹¤ë¤È¤¤¤Ã¤¿¤³¤È¤Ï²Äǽ¤Ç¤¹¡£)
      • +
    + +

    °Ê²¼¤Î¤È¤­¤Ë¤ÏñÆȤΥǡ¼¥â¥ó¤ò»È¤¦¤ÈÎɤ¤¤Ç¤·¤ç¤¦:

    + +
      +
    • ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È´Ö¤Ç¤Î httpd ¤ÎÀßÄê¤ò¶¦Í­¤·¤Æ¤â¤è¤¤¤È¤­¡£
      • + +
    • ¥Þ¥·¥ó¤¬Â¿¤¯¤Î¥ê¥¯¥¨¥¹¥È¤ò°·¤¦¤¿¤á¡¢Ê̥ǡ¼¥â¥ó¤ò¼Â¹Ô¤¹¤ë¤³¤È¤Ë¤è¤ë + À­Ç½¤ÎÄã²¼¤Î±Æ¶Á¤¬Ãø¤·¤¤¤È¤­¡£
      • +
    + +
    top
    +
    +

    Ê£¿ô¥Ç¡¼¥â¥ó¤ÎÀßÄê

    + +

    ³Æ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËÂФ·¤ÆÊ̤Πhttpd ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£ + ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤Î Listen + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¡¢ + ³Æ¥¤¥ó¥¹¥È¡¼¥ë¤Ç¥Ç¡¼¥â¥ó¤¬°·¤¦ IP ¥¢¥É¥ì¥¹ (¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È) + ¤òÁªÂò¤·¤Þ¤¹¡£Î㤨¤Ð

    + +

    + Listen www.smallco.com:80 +

    + +

    ¤³¤³¤Ç¡¢¥Û¥¹¥È̾¤ÎÂå¤ï¤ê¤Ë IP ¥¢¥É¥ì¥¹¤ò»È¤¦Êý¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤ë¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤ + (DNS ¤ÎÃí°Õ»ö¹à »²¾È)¡£

    + +
    top
    +
    +

    Ê£¿ô¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÀßÄê¤ò¤·¤¿ +¥Ç¡¼¥â¥ó¤ò°ì¤ÄÀßÄꤹ¤ë

    + +

    ¤³¤Î¾ì¹ç¤Ï¡¢°ì¤Ä¤Î httpd ¤¬¼ç¥µ¡¼¥Ð¤È¤¹¤Ù¤Æ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¥ê¥¯¥¨¥¹¥È¤ò + ½èÍý¤·¤Þ¤¹¡£ÀßÄê¥Õ¥¡¥¤¥ë¤Î VirtualHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤Æ¡¢ + ServerAdmin, ServerName, DocumentRoot, ErrorLog, TransferLog + ¤ä CustomLog + ÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃͤ¬³Æ¥Û¥¹¥ÈËè¤Ë°Û¤Ê¤ëÃͤËÀßÄꤵ¤ì¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£ + Î㤨¤Ð

    + +

    + <VirtualHost www.smallco.com>
    + ServerAdmin webmaster@mail.smallco.com
    + DocumentRoot /groups/smallco/www
    + ServerName www.smallco.com
    + ErrorLog /groups/smallco/logs/error_log
    + TransferLog /groups/smallco/logs/access_log
    + </VirtualHost>
    +
    + <VirtualHost www.baygroup.org>
    + ServerAdmin webmaster@mail.baygroup.org
    + DocumentRoot /groups/baygroup/www
    + ServerName www.baygroup.org
    + ErrorLog /groups/baygroup/logs/error_log
    + TransferLog /groups/baygroup/logs/access_log
    + </VirtualHost> +

    + +

    ¤³¤³¤Ç¡¢¥Û¥¹¥È̾¤ÎÂå¤ï¤ê¤Ë IP ¥¢¥É¥ì¥¹¤ò»È¤¦Êý¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤ë¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤ + (DNS ¤ÎÃí°Õ»ö¹à »²¾È)¡£

    + +

    ¥×¥í¥»¥¹À¸À®¤òÀ©¸æ¤¹¤ë¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ä¤½¤Î¾¤Î¤¤¤¯¤Ä¤«¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ½ü¤¤¤Æ¡¢¤Û¤Ü¤¹¤Ù¤Æ¤ÎÀßÄê¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò VirtualHost + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃæ¤Ë½ñ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤¬ VirtualHost + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ÈÍѤǤ­¤ë¤«¤É¤¦¤«¤Ï ¥Ç¥£¥ì¥¯¥Æ¥£¥Öº÷°ú¤ò»È¤Ã¤Æ¥³¥ó¥Æ¥­¥¹¥È¤Î + Íó¤òÄ´¤Ù¤Æ¤¯¤À¤µ¤¤¡£

    + +

    suEXEC¥é¥Ã¥Ñ¡¼¤ò»È¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢ + SuexecUserGroup + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò VirtualHost + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃæ¤Ç»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£

    + +

    ¥»¥­¥å¥ê¥Æ¥£: ¥í¥°¥Õ¥¡¥¤¥ë¤ò½ñ¤¯¾ì½ê¤ò»ØÄꤹ¤ë¤È¤­¤Ï¡¢ + Apache ¤òµ¯Æ°¤·¤¿¥æ¡¼¥¶°Ê³°¤¬¤½¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë½ñ¤­¹þ¤ß¸¢¸Â¤ò + »ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¥»¥­¥å¥ê¥Æ¥£¾å¤Î´í¸±¤¬¤¢¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¾ÜºÙ¤Ï¥»¥­¥å¥ê¥Æ¥£¤Î¤³¤Ä¥É¥­¥å¥á¥ó¥È¤ò + »²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£

    + +
    +
    +

    Available Languages:  en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/ip-based.html.ko.euc-kr b/docs/manual/vhosts/ip-based.html.ko.euc-kr new file mode 100644 index 00000000..68442f4d --- /dev/null +++ b/docs/manual/vhosts/ip-based.html.ko.euc-kr @@ -0,0 +1,152 @@ + + + +¾ÆÆÄÄ¡ IP±â¹Ý °¡»óÈ£½ºÆ® Áö¿ø - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    ¾ÆÆÄÄ¡ IP±â¹Ý °¡»óÈ£½ºÆ® Áö¿ø

    +
    +

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

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

    ½Ã½ºÅÛ ¿ä±¸»çÇ×

    + +

    IP±â¹ÝÀ̶õ ¸»ÀÌ ÀǹÌÇϵíÀÌ ¼­¹ö´Â + IP±â¹Ý °¡»óÈ£½ºÆ® °¢°¢¿¡ ´ëÇØ ´Ù¸¥ IP ÁÖ¼Ò¸¦ + °¡Á®¾ßÇÑ´Ù. ÀÌ´Â ÄÄÇ»Å͸¦ ¹°¸®ÀûÀ¸·Î ¿©·¯ ³×Æ®¿÷¿¡ + ¿¬°áÇϰųª, ÃÖ±Ù ¿î¿µÃ¼Á¦¿¡¼­ Áö¿øÇÏ´Â °¡»ó ÀÎÅÍÆäÀ̽º¸¦ + (ÀÚ¼¼ÇÑ ³»¿ëÀº ½Ã½ºÅÛ ¹®¼­¸¦ Âü°íÇ϶ó. ÈçÈ÷ "ip aliases"¶ó°í + Çϸç, º¸Åë "ifconfig" ¸í·É¾î·Î ¸¸µç´Ù) »ç¿ëÇÏ¿© °¡´ÉÇÏ´Ù.

    + +
    top
    +
    +

    ¾ÆÆÄÄ¡ ¼³Á¤¹æ¹ý

    + +

    ¿©·¯ È£½ºÆ®¸¦ Áö¿øÇϵµ·Ï ¾ÆÆÄÄ¡¸¦ ¼³Á¤ÇÏ´Â ¹æ¹ýÀº µÎ°¡Áö´Ù. + Çϳª´Â °¢ È£½ºÆ®¸¶´Ù º°µµÀÇ À¥¼­¹ö¸¦ ½ÇÇàÇÏ´Â + ¹ýÀÌ°í, ´Ù¸¥ Çϳª´Â ¸ðµç °¡»óÈ£½ºÆ®¸¦ Áö¿øÇÏ´Â ¼­¹ö ÇÑ°³¸¦ + ½ÇÇàÇÏ´Â ¹æ¹ýÀÌ´Ù.

    + +

    ¾ðÁ¦ ¿©·¯ ¼­¹ö¸¦ »ç¿ëÇϳª:

    + +
      +
    • ȸ»ç2ÀÇ »ç¿ëÀÚ°¡ À¥ÀÌ¿ÜÀÇ ¹æ¹ýÀ¸·Î ȸ»ç1ÀÇ ÀڷḦ ÀÐÀ» + ¼ö ¾ø°Ô ÇÏ´Â µî º¸¾È»ó ±¸ºÐÀÌ ÇÊ¿äÇÑ °æ¿ì. ÀÌ °æ¿ì + µÎ ¼­¹ö¸¦ °¢°¢ ´Ù¸¥ User, Group, Listen, ServerRoot ¼³Á¤À¸·Î ½ÇÇàÇØ¾ß ÇÑ´Ù.
      • + +
    • ÃæºÐÇÑ ¸Þ¸ð¸®°¡ ÀÖ°í, ÄÄÇ»ÅÍÀÇ ¸ðµç IP¸¦ ±â´Ù¸®±âÀ§ÇÑ + ÆÄÀϱâ¼úÀÚ(file descriptor) ¿ä±¸»çÇ×µµ ¸¸Á·ÇÑ´Ù. "¿ÍÀϵåÄ«µå"³ª + ƯÁ¤ ÁÖ¼Ò¸¦ ListenÇÒ ¼ö¸¸ ÀÖ´Ù. ±×·¡¼­ + ¾î¶² ÀÌÀ¯¿¡¼­°Ç ƯÁ¤ ÁÖ¼Ò¸¦ ±â´Ù¸± ÇÊ¿ä°¡ ÀÖ´Ù¸é, (ÇÑ + À¥¼­¹ö°¡ ÇÑ ÁÖ¼Ò¸¦ Á¦¿ÜÇÑ ¸ðµç ÁÖ¼Ò¸¦ ±â´Ù¸®°í ´Ù¸¥ ÇÑ + À¥¼­¹ö°¡ Á¦¿ÜÇÑ ÁÖ¼Ò¸¦ ±â´Ù¸± ¼ö ÀÖÁö¸¸) ÁöÁ¤ÇÑ ÁÖ¼Ò + ¸ðµÎ¸¦ ±â´Ù·Á¾ß ÇÑ´Ù.
      • +
    + +

    ¾ðÁ¦ ¼­¹ö ÇÑ°³¸¦ »ç¿ëÇϳª:

    + +
      +
    • °¡»óÈ£½ºÆ®µéÀÇ À¥¼­¹ö ¼³Á¤À» °øÀ¯ÇÒ ¼ö ÀÖ´Â °æ¿ì.
      • + +
    • ÄÄÇ»ÅÍ°¡ ¸Å¿ì ¸¹Àº ¿äûÀ» ¼­ºñ½ºÇÑ´Ù¸é ¿©·¯ ¼­¹ö¸¦ + ½ÇÇàÇϱ⿡ ¼Óµµ ¼Õ½ÇÀÌ Å¬ ¼ö ÀÖ´Ù.
      • +
    + +
    top
    +
    +

    ¿©·¯ ¼­¹ö¸¦ ½ÇÇàÇϱâ

    + +

    °¢ °¡»óÈ£½ºÆ®º°·Î À¥¼­¹ö¸¦ ¼³Ä¡ÇÑ´Ù. ¼³Á¤ÆÄÀÏÀÇ + Listen Áö½Ã¾î¿¡ + ¼­¹ö°¡ ¼­ºñ½ºÇÒ IP ÁÖ¼Ò(ȤÀº °¡»óÈ£½ºÆ®)¸¦ Àû¾îÁØ´Ù. ¿¹¸¦ + µé¸é,

    + +

    + Listen www.smallco.com:80 +

    + +

    È£½ºÆ®¸í º¸´Ù´Â IP ÁÖ¼Ò¸¦ »ç¿ëÇÏ±æ ¹Ù¶õ´Ù. + (DNS ¹®Á¦ Âü°í)

    + +
    top
    +
    +

    ¼­¹ö Çϳª·Î °¡»óÈ£½ºÆ® ½ÇÇàÇϱâ

    + +

    ÀÌ °æ¿ì À¥¼­¹ö ÇÑ°³·Î ÁÖ¼­¹ö¿Í ¸ðµç °¡»óÈ£½ºÆ®¿¡ ´ëÇÑ + ¿äûÀ» ¼­ºñ½ºÇÑ´Ù. ¼³Á¤ÆÄÀÏÀÇ VirtualHost Áö½Ã¾î¿¡ °¡»óÈ£½ºÆ®¸¶´Ù + ´Ù¸¥ ServerAdmin, + ServerName, DocumentRoot, ErrorLog, TransferLog, + CustomLog + Áö½Ã¾î °ªÀ» ¼³Á¤ÇÑ´Ù. ¿¹¸¦ µé¸é,

    + +

    + <VirtualHost www.smallco.com>
    + ServerAdmin webmaster@mail.smallco.com
    + DocumentRoot /groups/smallco/www
    + ServerName www.smallco.com
    + ErrorLog /groups/smallco/logs/error_log
    + TransferLog /groups/smallco/logs/access_log
    + </VirtualHost>
    +
    + <VirtualHost www.baygroup.org>
    + ServerAdmin webmaster@mail.baygroup.org
    + DocumentRoot /groups/baygroup/www
    + ServerName www.baygroup.org
    + ErrorLog /groups/baygroup/logs/error_log
    + TransferLog /groups/baygroup/logs/access_log
    + </VirtualHost> +

    + +

    È£½ºÆ®¸í º¸´Ù´Â IP ÁÖ¼Ò¸¦ »ç¿ëÇÏ±æ ¹Ù¶õ´Ù. + (DNS ¹®Á¦ Âü°í)

    + +

    VirtualHost Áö½Ã¾î ¾È¿¡¼­´Â ÇÁ·Î¼¼½º »ý¼º°ú ±âŸ ¸î¸î Áö½Ã¾î¸¦ + Á¦¿ÜÇÏ°í °ÅÀÇ ¸ðµç ¼³Á¤Áö½Ã¾î¸¦ »ç¿ëÇÒ + ¼ö ÀÖ´Ù. VirtualHost Áö½Ã¾î ¾È¿¡¼­ Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖ´ÂÁö + ¾Ë·Á¸é Áö½Ã¾î ¸ñ·Ï¿¡¼­ + »ç¿ëÀå¼Ò¸¦ + È®ÀÎÇ϶ó.

    + +

    suEXEC ÇÁ·Î±×·¥À» + »ç¿ëÇÑ´Ù¸é VirtualHost Áö½Ã¾î ¾È¿¡ User¿Í GroupÀ» »ç¿ëÇÒ ¼ö ÀÖ´Ù.

    + +

    º¸¾È: ¼­¹ö¸¦ ½ÇÇàÇÏ´Â »ç¿ëÀÚ¿Ü¿¡ ´Ù¸¥ »ç¶÷¿¡°Ô + ·Î±×ÆÄÀÏÀÌ ÀÖ´Â µð·ºÅ丮ÀÇ ¾²±â±ÇÇÑÀÌ ÀÖ´Ù¸é º¸¾È + ¹®Á¦¸¦ Á¶½ÉÇ϶ó. ÀÚ¼¼ÇÑ ³»¿ëÀº º¸¾È ÆÁÀ» Âü°íÇ϶ó.

    + +
    +
    +

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

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/mass.html b/docs/manual/vhosts/mass.html new file mode 100644 index 00000000..6c05d28e --- /dev/null +++ b/docs/manual/vhosts/mass.html @@ -0,0 +1,7 @@ +URI: mass.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: mass.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/vhosts/mass.html.en b/docs/manual/vhosts/mass.html.en new file mode 100644 index 00000000..25b2fe51 --- /dev/null +++ b/docs/manual/vhosts/mass.html.en @@ -0,0 +1,445 @@ + + + +Dynamically configured mass virtual hosting - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Dynamically configured mass virtual hosting

    +
    +

    Available Languages:  en  | + ko 

    +
    + + +

    This document describes how to efficiently serve an + arbitrary number of virtual hosts with Apache. +

    + +
    + +
    top
    +
    +

    Motivation

    + +

    The techniques described here are of interest if your + httpd.conf contains many + <VirtualHost> sections that are + substantially the same, for example:

    + +

    +NameVirtualHost 111.22.33.44
    +<VirtualHost 111.22.33.44>
    + + ServerName www.customer-1.com
    + DocumentRoot /www/hosts/www.customer-1.com/docs
    + ScriptAlias /cgi-bin/ /www/hosts/www.customer-1.com/cgi-bin
    +     +</VirtualHost>
    +<VirtualHost 111.22.33.44>
    + + ServerName www.customer-2.com
    + DocumentRoot /www/hosts/www.customer-2.com/docs
    + ScriptAlias /cgi-bin/ /www/hosts/www.customer-2.com/cgi-bin
    +     +</VirtualHost>
    +# blah blah blah
    +<VirtualHost 111.22.33.44>
    + + ServerName www.customer-N.com
    + DocumentRoot /www/hosts/www.customer-N.com/docs
    + ScriptAlias /cgi-bin/ /www/hosts/www.customer-N.com/cgi-bin
    +     +</VirtualHost> +

    + +

    The basic idea is to replace all of the static + <VirtualHost> configuration with a mechanism + that works it out dynamically. This has a number of + advantages:

    + +
      +
    1. Your configuration file is smaller so Apache starts + faster and uses less memory.
      2. + +
    2. Adding virtual hosts is simply a matter of creating the + appropriate directories in the filesystem and entries in the + DNS - you don't need to reconfigure or restart Apache.
      3. +
    + +

    The main disadvantage is that you cannot have a different + log file for each virtual host; however if you have very many + virtual hosts then doing this is dubious anyway because it eats + file descriptors. It is better to log to a pipe or a fifo and + arrange for the process at the other end to distribute the logs + to the customers (it can also accumulate statistics, etc.).

    + +
    top
    +
    +

    Overview

    + +

    A virtual host is defined by two pieces of information: its + IP address, and the contents of the Host: header + in the HTTP request. The dynamic mass virtual hosting technique + is based on automatically inserting this information into the + pathname of the file that is used to satisfy the request. This + is done most easily using mod_vhost_alias, + but if you are using a version of Apache up to 1.3.6 then you + must use mod_rewrite. + Both of these modules are disabled by default; you must enable + one of them when configuring and building Apache if you want to + use this technique.

    + +

    A couple of things need to be `faked' to make the dynamic + virtual host look like a normal one. The most important is the + server name which is used by Apache to generate + self-referential URLs, etc. It is configured with the + ServerName directive, and it is available to CGIs + via the SERVER_NAME environment variable. The + actual value used at run time is controlled by the UseCanonicalName + setting. With UseCanonicalName Off the server name + comes from the contents of the Host: header in the + request. With UseCanonicalName DNS it comes from a + reverse DNS lookup of the virtual host's IP address. The former + setting is used for name-based dynamic virtual hosting, and the + latter is used for IP-based hosting. If Apache cannot work out + the server name because there is no Host: header + or the DNS lookup fails then the value configured with + ServerName is used instead.

    + +

    The other thing to `fake' is the document root (configured + with DocumentRoot and available to CGIs via the + DOCUMENT_ROOT environment variable). In a normal + configuration this setting is used by the core module when + mapping URIs to filenames, but when the server is configured to + do dynamic virtual hosting that job is taken over by another + module (either mod_vhost_alias or + mod_rewrite) which has a different way of doing + the mapping. Neither of these modules is responsible for + setting the DOCUMENT_ROOT environment variable so + if any CGIs or SSI documents make use of it they will get a + misleading value.

    + +
    top
    +
    +

    Simple dynamic virtual hosts

    + +

    This extract from httpd.conf implements the + virtual host arrangement outlined in the Motivation section above, but in a + generic fashion using mod_vhost_alias.

    + +

    +# get the server name from the Host: header
    +UseCanonicalName Off
    +
    +# this log format can be split per-virtual-host based on the first field
    +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon
    +CustomLog logs/access_log vcommon
    +
    +# include the server name in the filenames used to satisfy requests
    +VirtualDocumentRoot /www/hosts/%0/docs
    +VirtualScriptAlias /www/hosts/%0/cgi-bin +

    + +

    This configuration can be changed into an IP-based virtual + hosting solution by just turning UseCanonicalName + Off into UseCanonicalName DNS. The server + name that is inserted into the filename is then derived from + the IP address of the virtual host.

    + +
    top
    +
    +

    A virtually hosted homepages system

    + +

    This is an adjustment of the above system tailored for an + ISP's homepages server. Using a slightly more complicated + configuration we can select substrings of the server name to + use in the filename so that e.g. the documents for + www.user.isp.com are found in + /home/user/. It uses a single cgi-bin + directory instead of one per virtual host.

    + +

    +# all the preliminary stuff is the same as above, then
    +
    +# include part of the server name in the filenames
    +VirtualDocumentRoot /www/hosts/%2/docs
    +
    +# single cgi-bin directory
    +ScriptAlias /cgi-bin/ /www/std-cgi/
    +

    + +

    There are examples of more complicated + VirtualDocumentRoot settings in the + mod_vhost_alias documentation.

    + +
    top
    +
    +

    Using more than + one virtual hosting system on the same server

    + +

    With more complicated setups you can use Apache's normal + <VirtualHost> directives to control the + scope of the various virtual hosting configurations. For + example, you could have one IP address for homepages customers + and another for commercial customers with the following setup. + This can of course be combined with conventional + <VirtualHost> configuration sections.

    + +

    +UseCanonicalName Off
    +
    +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon
    +
    +<Directory /www/commercial>
    + + Options FollowSymLinks
    + AllowOverride All
    +     +</Directory>
    +
    +<Directory /www/homepages>
    + + Options FollowSymLinks
    + AllowOverride None
    +     +</Directory>
    +
    +<VirtualHost 111.22.33.44>
    + + ServerName www.commercial.isp.com
    +
    + CustomLog logs/access_log.commercial vcommon
    +
    + VirtualDocumentRoot /www/commercial/%0/docs
    + VirtualScriptAlias /www/commercial/%0/cgi-bin
    +     +</VirtualHost>
    +
    +<VirtualHost 111.22.33.45>
    + + ServerName www.homepages.isp.com
    +
    + CustomLog logs/access_log.homepages vcommon
    +
    + VirtualDocumentRoot /www/homepages/%0/docs
    + ScriptAlias /cgi-bin/ /www/std-cgi/
    +     +</VirtualHost> +

    + +
    top
    +
    +

    More efficient IP-based virtual hosting

    + +

    After the first example I noted that + it is easy to turn it into an IP-based virtual hosting setup. + Unfortunately that configuration is not very efficient because + it requires a DNS lookup for every request. This can be avoided + by laying out the filesystem according to the IP addresses + themselves rather than the corresponding names and changing the + logging similarly. Apache will then usually not need to work + out the server name and so incur a DNS lookup.

    + +

    +# get the server name from the reverse DNS of the IP address
    +UseCanonicalName DNS
    +
    +# include the IP address in the logs so they may be split
    +LogFormat "%A %h %l %u %t \"%r\" %s %b" vcommon
    +CustomLog logs/access_log vcommon
    +
    +# include the IP address in the filenames
    +VirtualDocumentRootIP /www/hosts/%0/docs
    +VirtualScriptAliasIP /www/hosts/%0/cgi-bin
    +

    + +
    top
    +
    +

    Using older versions of Apache

    + +

    The examples above rely on mod_vhost_alias + which appeared after version 1.3.6. If you are using a version + of Apache without mod_vhost_alias then you can + implement this technique with mod_rewrite as + illustrated below, but only for Host:-header-based virtual + hosts.

    + +

    In addition there are some things to beware of with logging. + Apache 1.3.6 is the first version to include the + %V log format directive; in versions 1.3.0 - 1.3.3 + the %v option did what %V does; + version 1.3.4 has no equivalent. In all these versions of + Apache the UseCanonicalName directive can appear + in .htaccess files which means that customers can + cause the wrong thing to be logged. Therefore the best thing to + do is use the %{Host}i directive which logs the + Host: header directly; note that this may include + :port on the end which is not the case for + %V.

    + +
    top
    +
    +

    Simple dynamic + virtual hosts using mod_rewrite

    + +

    This extract from httpd.conf does the same + thing as the first example. The first + half is very similar to the corresponding part above but with + some changes for backward compatibility and to make the + mod_rewrite part work properly; the second half + configures mod_rewrite to do the actual work.

    + +

    There are a couple of especially tricky bits: By default, + mod_rewrite runs before the other URI translation + modules (mod_alias etc.) so if they are used then + mod_rewrite must be configured to accommodate + them. Also, some magic must be performed to do a + per-dynamic-virtual-host equivalent of + ScriptAlias.

    + +

    +# get the server name from the Host: header
    +UseCanonicalName Off
    +
    +# splittable logs
    +LogFormat "%{Host}i %h %l %u %t \"%r\" %s %b" vcommon
    +CustomLog logs/access_log vcommon
    +
    +<Directory /www/hosts>
    + + # ExecCGI is needed here because we can't force
    + # CGI execution in the way that ScriptAlias does
    + Options FollowSymLinks ExecCGI
    +     +</Directory>
    +
    +# now for the hard bit
    +
    +RewriteEngine On
    +
    +# a ServerName derived from a Host: header may be any case at all
    +RewriteMap lowercase int:tolower
    +
    +## deal with normal documents first:
    +# allow Alias /icons/ to work - repeat for other aliases
    +RewriteCond %{REQUEST_URI} !^/icons/
    +# allow CGIs to work
    +RewriteCond %{REQUEST_URI} !^/cgi-bin/
    +# do the magic
    +RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/docs/$1
    +
    +## and now deal with CGIs - we have to force a MIME type
    +RewriteCond %{REQUEST_URI} ^/cgi-bin/
    +RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/cgi-bin/$1 [T=application/x-httpd-cgi]
    +
    +# that's it! +

    + +
    top
    +
    +

    A + homepages system using mod_rewrite

    + +

    This does the same thing as the second + example.

    + +

    +RewriteEngine on
    +
    +RewriteMap lowercase int:tolower
    +
    +# allow CGIs to work
    +RewriteCond %{REQUEST_URI} !^/cgi-bin/
    +
    +# check the hostname is right so that the RewriteRule works
    +RewriteCond ${lowercase:%{SERVER_NAME}} ^www\.[a-z-]+\.isp\.com$
    +
    +# concatenate the virtual host name onto the start of the URI
    +# the [C] means do the next rewrite on the result of this one
    +RewriteRule ^(.+) ${lowercase:%{SERVER_NAME}}$1 [C]
    +
    +# now create the real file name
    +RewriteRule ^www\.([a-z-]+)\.isp\.com/(.*) /home/$1/$2
    +
    +# define the global CGI directory
    +ScriptAlias /cgi-bin/ /www/std-cgi/ +

    + +
    top
    +
    +

    Using a separate virtual + host configuration file

    + +

    This arrangement uses more advanced mod_rewrite + features to get the translation from virtual host to document + root from a separate configuration file. This provides more + flexibility but requires more complicated configuration.

    + +

    The vhost.map file contains something like + this:

    + +

    +www.customer-1.com /www/customers/1
    +www.customer-2.com /www/customers/2
    +# ...
    +www.customer-N.com /www/customers/N
    +

    + +

    The http.conf contains this:

    + +

    +RewriteEngine on
    +
    +RewriteMap lowercase int:tolower
    +
    +# define the map file
    +RewriteMap vhost txt:/www/conf/vhost.map
    +
    +# deal with aliases as above
    +RewriteCond %{REQUEST_URI} !^/icons/
    +RewriteCond %{REQUEST_URI} !^/cgi-bin/
    +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$
    +# this does the file-based remap
    +RewriteCond ${vhost:%1} ^(/.*)$
    +RewriteRule ^/(.*)$ %1/docs/$1
    +
    +RewriteCond %{REQUEST_URI} ^/cgi-bin/
    +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$
    +RewriteCond ${vhost:%1} ^(/.*)$
    +RewriteRule ^/(.*)$ %1/cgi-bin/$1 +

    + +
    +
    +

    Available Languages:  en  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/mass.html.ko.euc-kr b/docs/manual/vhosts/mass.html.ko.euc-kr new file mode 100644 index 00000000..7bd83eb2 --- /dev/null +++ b/docs/manual/vhosts/mass.html.ko.euc-kr @@ -0,0 +1,423 @@ + + + +´ë·®ÀÇ °¡»óÈ£½ºÆ®¸¦ µ¿ÀûÀ¸·Î ¼³Á¤Çϱâ - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    ´ë·®ÀÇ °¡»óÈ£½ºÆ®¸¦ µ¿ÀûÀ¸·Î ¼³Á¤Çϱâ

    +
    +

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

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

    ÀÌ ¹®¼­´Â ¾ÆÆÄÄ¡ 1.3¿¡¼­ ´ë·®ÀÇ °¡»óÈ£½ºÆ®¸¦ È¿À²ÀûÀ¸·Î + ¼­ºñ½ºÇÏ´Â ¹æ¹ýÀ» ¼³¸íÇÑ´Ù. +

    + +
    + +
    top
    +
    +

    µ¿±â

    + +

    ´ç½ÅÀÇ httpd.conf¿¡ ´ÙÀ½°ú °°ÀÌ ¼­·Î ºñ½ÁÇÑ + <VirtualHost> ¼½¼ÇµéÀ» ¸¹ÀÌ ÀÖ´Ù¸é ¿©±â¼­ + ¼³¸íÇÏ´Â ¹æ¹ýÀÌ µµ¿òÀÌ µÉ °ÍÀÌ´Ù:

    + +

    +NameVirtualHost 111.22.33.44
    +<VirtualHost 111.22.33.44>
    + + ServerName www.customer-1.com
    + DocumentRoot /www/hosts/www.customer-1.com/docs
    + ScriptAlias /cgi-bin/ /www/hosts/www.customer-1.com/cgi-bin
    +     +</VirtualHost>
    +<VirtualHost 111.22.33.44>
    + + ServerName www.customer-2.com
    + DocumentRoot /www/hosts/www.customer-2.com/docs
    + ScriptAlias /cgi-bin/ /www/hosts/www.customer-2.com/cgi-bin
    +     +</VirtualHost>
    +# ¹Ùº¸ ¹Ùº¸ ¹Ùº¸
    +<VirtualHost 111.22.33.44>
    + + ServerName www.customer-N.com
    + DocumentRoot /www/hosts/www.customer-N.com/docs
    + ScriptAlias /cgi-bin/ /www/hosts/www.customer-N.com/cgi-bin
    +     +</VirtualHost> +

    + +

    ±âº» °³³äÀº Á¤ÀûÀÎ <VirtualHost> + ¼³Á¤ ¸ðµÎ¸¦ µ¿ÀûÀ¸·Î ó¸®Çϵµ·Ï ´ëüÇÏ´Â °ÍÀÌ´Ù. + ±×·¯¸é ¸¹Àº ÀåÁ¡ÀÌ ÀÖ´Ù:

    + +
      +
    1. ¼³Á¤ÆÄÀÏÀÌ ÀÛ¾ÆÁ®¼­ ¾ÆÆÄÄ¡°¡ »¡¸® ½ÃÀÛÇÏ°í ¸Þ¸ð¸®¸¦ + Àû°Ô »ç¿ëÇÑ´Ù.
      2. + +
    2. °¡»óÈ£½ºÆ®¸¦ Ãß°¡ÇϱâÀ§ÇØ ÆÄÀϽýºÅÛ¿¡ Àû´çÇÑ + µð·ºÅ丮¸¦ ¸¸µé°í DNS¿¡ Ç׸ñÀ» Ãß°¡Çϱ⸸ ÇϸéµÈ´Ù. Áï, + ¾ÆÆÄÄ¡¸¦ Àç¼³Á¤ÇÏ°í Àç½ÃÀÛÇÒ ÇÊ¿ä°¡ ¾ø´Ù.
      3. +
    + +

    ´ÜÁ¡Àº °¢ °¡»óÈ£½ºÆ®º°·Î ´Ù¸¥ ·Î±×ÆÄÀÏÀ» »ç¿ëÇÒ ¼ö ¾ø´Ù´Â + Á¡ÀÌ´Ù. ±×·¯³ª ¸Å¿ì ¸¹Àº °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÑ´Ù¸é ÆÄÀϱâ¼úÀÚ¸¦ + ´Ù ½á¹ö¸®±â¶§¹®¿¡ ¼­·Î ´Ù¸¥ ·Î±×ÆÄÀÏÀ» »ç¿ëÇÒ ¼ö ¾ø´Ù. ÆÄÀÌÇÁ³ª + fifo·Î ·Î±×¸¦ º¸³»°í, ¹Þ´Â Æí¿¡¼­ ·Î±×¸¦ ó¸®ÇÏ¿© ³ª´©´Â + ¹æ¹ýÀÌ (Åë°è µîÀ» ¸ðÀ» ¼öµµ ÀÖ´Ù) ´õ ³´´Ù.

    + +
    top
    +
    +

    °³¿ä

    + +

    °¡»óÈ£½ºÆ®´Â IP ÁÖ¼Ò¿Í HTTP ¿äûÀÇ Host: + Çì´õ Á¤º¸·Î Á¤ÀÇÇÑ´Ù. ±âº»ÀûÀ¸·Î ´ë·®ÀÇ + µ¿Àû °¡»óÈ£½ºÆ® ±â¼úÀº ÀÚµ¿À¸·Î °¡»óÈ£½ºÆ® Á¤º¸¸¦ ¿äûÀÇ + ÆÄÀÏ°æ·Î¿¡ Æ÷ÇÔÇÑ´Ù. ÀÌ´Â ´ëºÎºÐ mod_vhost_alias¸¦ + »ç¿ëÇÏ¿© ½±°Ô ÇØ°áÇÒ ¼ö ÀÖÁö¸¸, ¾ÆÆÄÄ¡ 1.3.6 ÀÌÇϸ¦ »ç¿ëÇÑ´Ù¸é + mod_rewrite¸¦ »ç¿ëÇØ¾ß ÇÑ´Ù. ÀÌ µÎ ¸ðµâ + ¸ðµÎ ±âº»ÀûÀ¸·Î ¼­¹ö¿¡ Æ÷ÇÔµÇÁö ¾Ê´Â´Ù. ÀÌ ¹æ¹ýÀ» »ç¿ëÇÏ·Á¸é + ¾ÆÆÄÄ¡¸¦ ±¸¼ºÇÏ°í ÄÄÆÄÀÏÇÒ¶§ Æ÷ÇÔÇØ¾ß ÇÑ´Ù.

    + +

    µ¿Àû °¡»óÈ£½ºÆ®¸¦ ÀϹÝÀûÀÎ °¡»óÈ£½ºÆ®Ã³·³ º¸ÀÌ°ÔÇÏ·Á¸é + ¿©·¯°¡Áö¸¦ `¼Ó¿©¾ß' ÇÑ´Ù. °¡Àå Áß¿äÇÑ °ÍÀº ¾ÆÆÄÄ¡°¡ ÀÚ±âÂüÁ¶ + URL µîÀ» ¸¸µé¶§ »ç¿ëÇÒ ¼­¹ö¸íÀÌ´Ù. ¼­¹ö¸íÀº + ServerName Áö½Ã¾î·Î ¼³Á¤Çϸç, CGI¿¡´Â + SERVER_NAME ȯ°æº¯¼ö·Î ÁÖ¾îÁø´Ù. ½ÇÇàÁß ½ÇÁ¦ + ¼­¹ö¸íÀº UseCanonicalName ¼³Á¤¿¡ ´Þ·È´Ù. + UseCanonicalName OffÀÌ¸é ¿äûÀÇ Host: + Çì´õ ³»¿ëÀÌ ¼­¹ö¸íÀÌ µÈ´Ù. UseCanonicalName DNSÀ̸é + °¡»óÈ£½ºÆ®ÀÇ IP ÁÖ¼Ò¸¦ ¿ªDNS °Ë»öÇÏ¿© ¼­¹ö¸íÀ» ¾Ë¾Æ³½´Ù. + ÀüÀÚ´Â À̸§±â¹Ý µ¿Àû °¡»óÈ£½ºÆ®¿¡¼­ »ç¿ëÇÏ°í, ÈÄÀÚ´Â IP±â¹Ý + °¡»óÈ£½ºÆ®¿¡¼­ »ç¿ëÇÑ´Ù. Host: Çì´õ°¡ ¾ø°Å³ª + DNS °Ë»öÀÌ ½ÇÆÐÇÏ¿© ¾ÆÆÄÄ¡°¡ ¼­¹ö¸íÀ» ¾Ë¾Æ³»Áö ¸øÇϸé + ServerNameÀ¸·Î ¼³Á¤ÇÑ °ªÀ» ´ë½Å »ç¿ëÇÑ´Ù.

    + +

    ´Ù¸¥ `¼ÓÀÏ' °ÍÀº (DocumentRoot·Î ¼³Á¤Çϸç, + CGI¿¡´Â DOCUMENT_ROOT ȯ°æº¯¼ö·Î ÁÖ¾îÁö´Â) + ¹®¼­·çÆ®ÀÌ´Ù. ÀϹÝÀûÀÎ °æ¿ì core ¸ðµâÀÌ ÀÌ ¼³Á¤À» »ç¿ëÇÏ¿© + URI¿¡ ÇØ´çÇÏ´Â ÆÄÀϸíÀ» ãÁö¸¸, ¼­¹ö¸¦ µ¿Àû °¡»óÈ£½ºÆÃÀ» ÇÒ¶§´Â ´Ù¸¥ + ¸ðµâÀÌ (mod_vhost_alias³ª mod_rewrite) + ´Ù¸¥ ¹æ¹ýÀ¸·Î ÀÌ·± ÀÛ¾÷À» ÇÑ´Ù. µÎ ¸ðµâ ¸ðµÎ + DOCUMENT_ROOT ȯ°æº¯¼ö¸¦ »ç¿ëÇÏÁö ¾ÊÀ¸¹Ç·Î + CGI³ª SSI ¹®¼­°¡ ÀÌ °ªÀ» »ç¿ëÇÑ´Ù¸é À߸øµÈ °á°ú¸¦ ¾òÀ» ¼ö + ÀÖ´Ù.

    + +
    top
    +
    +

    °£´ÜÇÑ µ¿Àû °¡»óÈ£½ºÆ®

    + +

    À§ µ¿±â ÀýÀÇ °¡»óÈ£½ºÆ® + ¼³Á¤À» mod_vhost_alias¸¦ »ç¿ëÇÏ¿© ´õ ÀϹÝÀûÀ¸·Î + ±¸ÇöÇß´Ù.

    + +

    +# Host: Çì´õ¿¡¼­ ¼­¹ö¸íÀ» ¾Ë¾Æ³½´Ù
    +UseCanonicalName Off
    +
    +# ù¹ø° Çʵ带 »ç¿ëÇÏ¿© ÀÌ ·Î±×¸¦ °¡»óÈ£½ºÆ®º°·Î ³ª´­ ¼ö ÀÖ´Ù
    +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon
    +CustomLog logs/access_log vcommon
    +
    +# ¿äûÀ» ó¸®ÇϱâÀ§ÇØ ÆÄÀÏ¸í¿¡ ¼­¹ö¸íÀ» Æ÷ÇÔÇÑ´Ù
    +VirtualDocumentRoot /www/hosts/%0/docs
    +VirtualScriptAlias /www/hosts/%0/cgi-bin +

    + +

    ÀÌ ¼³Á¤¿¡¼­ UseCanonicalName Off¸¦ + UseCanonicalName DNS·Î º¯°æÇϱ⸸ Çϸé IP±â¹Ý + °¡»óÈ£½ºÆ®°¡ µÈ´Ù. °¡»óÈ£½ºÆ®ÀÇ IP ÁÖ¼Ò¸¦ °¡Áö°í + ÆÄÀÏ¸í¿¡ Ãß°¡ÇÒ ¼­¹ö¸íÀ» ¾Ë ¼ö ÀÖ´Ù.

    + +
    top
    +
    +

    °¡»óÀ¸·Î È£½ºÆ®Çϴ ȨÆäÀÌÁö ½Ã½ºÅÛ

    + +

    ISP ȨÆäÀÌÁö ¼­¹ö¸¦ À§ÇØ À§ÀÇ ¼³Á¤À» ¼öÁ¤Çß´Ù. Á¶±Ý ´õ + º¹ÀâÇÑ ¼³Á¤À» »ç¿ëÇϸé www.user.isp.comÀÇ ¹®¼­¸¦ + /home/user/¿¡ µÎ´Â ½ÄÀ¸·Î ¼­¹ö¸íÀÇ ÀϺθ¦ °¡Áö°í + ÆÄÀϸíÀ» ¸¸µé ¼ö ÀÖ´Ù. ÀÌ ¼³Á¤Àº + cgi-binÀ» °¢ °¡»óÈ£½ºÆ®°¡ µû·Î °¡ÁöÁö¾Ê°í + ¸ðµç °¡»óÈ£½ºÆ®°¡ °°ÀÌ »ç¿ëÇÑ´Ù.

    + +

    +# ±âº»ÀûÀÎ ³»¿ëÀº À§¿Í °°´Ù. ±×¸®°í
    +
    +# ÆÄÀÏ¸í¿¡ ¼­¹ö¸íÀÇ ÀϺθ¦ Æ÷ÇÔÇÑ´Ù
    +VirtualDocumentRoot /www/hosts/%2/docs
    +
    +# ÇϳªÀÇ cgi-bin µð·ºÅ丮
    +ScriptAlias /cgi-bin/ /www/std-cgi/
    +

    + +

    mod_vhost_alias ¹®¼­¿¡´Â ´õ º¹ÀâÇÑ + VirtualDocumentRoot ¼³Á¤ÀÇ ¿¹°¡ ÀÖ´Ù.

    + +
    top
    +
    +

    ÇÑ ¼­¹ö¿¡ ¿©·¯ °¡»óÈ£½ºÆ® + ½Ã½ºÅÛ »ç¿ëÇϱâ

    + +

    ´õ º¹ÀâÇÑ ¼³Á¤ÀÇ ¿¹·Î ¾ÆÆÄÄ¡ÀÇ ÀϹÝÀûÀÎ + <VirtualHost> Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© ¿©·¯ + °¡»óÈ£½ºÆ® ¼³Á¤ÀÇ ¹üÀ§¸¦ Á¶ÀýÇÒ ¼ö ÀÖ´Ù. ¿¹¸¦ µé¾î, ´ÙÀ½°ú + °°Àº ¼³Á¤Àº ȨÆäÀÌÁö °í°´¿¡ IP ÁÖ¼Ò ÇÑ°³, »ó¾÷ÀûÀÎ + °í°´¿¡°Ô ´Ù¸¥ IP ÁÖ¼Ò ÇÑ°³¸¦ ºÎ¿©ÇÑ´Ù. ¹°·Ð ÀÌÀüó·³ + <VirtualHost> ¼³Á¤ ¼½¼Ç¿¡ ¸ðµÎ ¹­À» ¼öµµ + ÀÖ´Ù.

    + +

    +UseCanonicalName Off
    +
    +LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon
    +
    +<Directory /www/commercial>
    + + Options FollowSymLinks
    + AllowOverride All
    +     +</Directory>
    +
    +<Directory /www/homepages>
    + + Options FollowSymLinks
    + AllowOverride None
    +     +</Directory>
    +
    +<VirtualHost 111.22.33.44>
    + + ServerName www.commercial.isp.com
    +
    + CustomLog logs/access_log.commercial vcommon
    +
    + VirtualDocumentRoot /www/commercial/%0/docs
    + VirtualScriptAlias /www/commercial/%0/cgi-bin
    +     +</VirtualHost>
    +
    +<VirtualHost 111.22.33.45>
    + + ServerName www.homepages.isp.com
    +
    + CustomLog logs/access_log.homepages vcommon
    +
    + VirtualDocumentRoot /www/homepages/%0/docs
    + ScriptAlias /cgi-bin/ /www/std-cgi/
    +     +</VirtualHost> +

    + +
    top
    +
    +

    ´õ È¿À²ÀûÀÎ IP±â¹Ý °¡»óÈ£½ºÆ®

    + +

    ù¹ø° ¿¹¿¡¼­ ³ª´Â ¼³Á¤À» °£´ÜÈ÷ + IP±â¹Ý °¡»óÈ£½ºÆ®·Î ¹Ù²Ü ¼ö ÀÖ´Ù°í ¸»Çß´Ù. ºÒÇàÈ÷µµ + ±×·± ¼³Á¤Àº ¸Å ¿äû¸¶´Ù DNS¸¦ ã¾Æ¾ßÇϹǷΠ¸Å¿ì ºñÈ¿À²ÀûÀÌ´Ù. + À̸§´ë½Å IP ÁÖ¼Ò·Î ÆÄÀϽýºÅÛÀ» ±¸¼ºÇÏ°í °°Àº ¹æ½ÄÀ¸·Î + ·Î±×¸¦ ¼öÁ¤ÇÏ¸é ¹®Á¦¸¦ ÇØ°áÇÒ ¼ö ÀÖ´Ù. ¾ÆÆÄÄ¡´Â ¼­¹ö¸íÀ» + ´Ù·ê ÇÊ¿ä°¡ ¾ø¾îÁö°í, DNS °Ë»öµµ ÇÏÁö ¾Ê°Ô µÈ´Ù.

    + +

    +# IP ÁÖ¼Ò¸¦ ¿ªDNS °Ë»öÇÏ¿© ¼­¹ö¸íÀ» ¾Ë¾Æ³½´Ù
    +UseCanonicalName DNS
    +
    +# ·Î±×¸¦ ³ª´­ ¼ö ÀÖµµ·Ï IP ÁÖ¼Ò¸¦ Æ÷ÇÔÇÑ´Ù
    +LogFormat "%A %h %l %u %t \"%r\" %s %b" vcommon
    +CustomLog logs/access_log vcommon
    +
    +# ÆÄÀÏ¸í¿¡ IP ÁÖ¼Ò¸¦ Æ÷ÇÔÇÑ´Ù
    +VirtualDocumentRootIP /www/hosts/%0/docs
    +VirtualScriptAliasIP /www/hosts/%0/cgi-bin
    +

    + +
    top
    +
    +

    ¾ÆÆÄÄ¡ ÀÌÀü ¹öÀü »ç¿ëÇϱâ

    + +

    À§ ¿¹µéÀº ¾ÆÆÄÄ¡ ¹öÀü 1.3.6 ÀÌÈÄ¿¡ Æ÷ÇÔµÈ + mod_vhost_aliasÀ» »ç¿ëÇÑ´Ù. + mod_vhost_alias°¡ ¾ø´Â ¾ÆÆÄÄ¡ ¹öÀüÀ» »ç¿ëÇÑ´Ù¸é + ÀÌ¹Ì ¸»ÇßµíÀÌ mod_rewrite¸¦ »ç¿ëÇÏ¿©, ´Ü + Host:-Çì´õ±â¹Ý °¡»óÈ£½ºÆ®¸¸À», ±¸ÇöÇÒ ¼ö ÀÖ´Ù.

    + +

    ¶Ç ·Î±×¿¡ °üÇÏ¿© ÁÖÀÇÇÒ Á¡ÀÌ ÀÖ´Ù. ¾ÆÆÄÄ¡ 1.3.6¿¡¼­ + ·Î±×Çü½Ä Áö½Ã¾î %V°¡ Æ÷ÇԵǾú°í, ¹öÀü 1.3.0 + - 1.3.3¿¡¼­ ÀÌ ±â´ÉÀ» %v ¿É¼ÇÀÌ ´ë½Å Çß´Ù. ±×·¯³ª + ¹öÀü 1.3.4¿¡´Â ÀÌ·± ±â´ÉÀÌ ¾ø´Ù. ¾î¶² ¾ÆÆÄÄ¡ ¹öÀü¿¡¼­µµ + .htaccess ÆÄÀÏ¿¡¼­ UseCanonicalName + Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖÀ¸¹Ç·Î ·Î±×¿¡ ÀÌ»óÇÑ ³»¿ëÀÌ ±â·ÏµÉ ¼ö ÀÖ´Ù. + ±×·¯¹Ç·Î °¡Àå ÁÁÀº ¹æ¹ýÀº %{Host}i Áö½Ã¾î¸¦ + »ç¿ëÇÏ¿© Host: Çì´õ¸¦ Á÷Á¢ ·Î±×¿¡ ³²±â´Â °ÍÀÌ´Ù. + ¶Ç, ÀÌ ¹æ¹ýÀº %V´Â Æ÷ÇÔÇÏÁö¾Ê´Â :port¸¦ + µÚ¿¡ Ãß°¡ÇÒ ¼ö ÀÖ´Ù.

    + +
    top
    +
    +

    mod_rewrite¸¦ + »ç¿ëÇÑ °£´ÜÇÑ µ¿Àû °¡»óÈ£½ºÆ®

    + +

    ´ÙÀ½Àº ù¹ø° ¿¹¿Í °°Àº ÀÏÀ» ÇÏ´Â + httpd.conf ¿¹ÀÌ´Ù. óÀ½ Àý¹ÝÀº ù¹ø° ¿¹¿Í + °ÅÀÇ ºñ½ÁÇÏÁö¸¸, ÀÌÀü ¹öÀü°úÀÇ È£È¯¼º°ú mod_rewriteÀÇ + ÀûÀýÇÑ µ¿ÀÛÀ» À§ÇØ ¼öÁ¤µÇ¾ú´Ù. ³ª¸ÓÁö Àý¹ÝÀº ½ÇÁ¦ ÀÛ¾÷À» + ÇÏ´Â mod_rewrite¸¦ ¼³Á¤ÇÑ´Ù.

    + +

    Ưº°È÷ ÁÖÀÇÇØ¾ß ÇÒ »çÇ×ÀÌ ÀÖ´Ù. ±âº»ÀûÀ¸·Î + mod_rewrite´Â (mod_alias µî) ´Ù¸¥ + URI ¹ø¿ª ¸ðµâ ÀÌÀü¿¡ ½ÇÇàµÈ´Ù. ±×·¡¼­ ´Ù¸¥ URI ¹ø¿ª ¸ðµâµé°ú + °°ÀÌ µ¿ÀÛÇÒ °ÍÀ» °í·ÁÇÏ¿© mod_rewrite¸¦ ¼³Á¤ÇØ¾ß ÇÑ´Ù. + ¶Ç, µ¿Àû °¡»óÈ£½ºÆ®¿¡¼­ ScriptAlias°ú °°Àº + ±â´ÉÀ» À§Çؼ­´Â Ưº°ÇÑ ÀÛ¾÷ÀÌ ÇÊ¿äÇÏ´Ù.

    + +

    +# Host: Çì´õ¿¡¼­ ¼­¹ö¸íÀ» ¾ò´Â´Ù
    +UseCanonicalName Off
    +
    +# splittable logs
    +LogFormat "%{Host}i %h %l %u %t \"%r\" %s %b" vcommon
    +CustomLog logs/access_log vcommon
    +
    +<Directory /www/hosts>
    + + # ScriptAlias ½ÄÀ¸·Î CGI ½ÇÇàÀ» °­Á¦ÇÒ ¼ö ¾ø±â¶§¹®¿¡
    + # ¿©±â¿¡ ExecCGI¸¦ »ç¿ëÇÑ´Ù
    + Options FollowSymLinks ExecCGI
    +     +</Directory>
    +
    +# ÀÌÁ¦ ¾î·Á¿î ºÎºÐÀÌ´Ù
    +
    +RewriteEngine On
    +
    +# Host: Çì´õ¿¡¼­ °¡Á®¿Â ¼­¹ö¸í¿¡´Â ´ë¼Ò¹®ÀÚ°¡ µÚ¼¯¿©ÀÖÀ» ¼ö ÀÖ´Ù
    +RewriteMap lowercase int:tolower
    +
    +## ÀÏ¹Ý ¹®¼­¸¦ ¸ÕÀú ó¸®ÇÑ´Ù:
    +# Alias /icons/ °¡ µ¿ÀÛÇϵµ·Ï - ´Ù¸¥ alias¿¡ ´ëÇؼ­µµ ¹Ýº¹
    +RewriteCond %{REQUEST_URI} !^/icons/
    +# CGI°¡ µ¿ÀÛÇϵµ·Ï
    +RewriteCond %{REQUEST_URI} !^/cgi-bin/
    +# Ưº°ÇÑ ÀÛ¾÷
    +RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/docs/$1
    +
    +## ÀÌÁ¦ CGI¸¦ ó¸®ÇÑ´Ù - MIME typeÀ» °­Á¦ÇØ¾ß ÇÑ´Ù
    +RewriteCond %{REQUEST_URI} ^/cgi-bin/
    +RewriteRule ^/(.*)$ /www/hosts/${lowercase:%{SERVER_NAME}}/cgi-bin/$1 [T=application/x-httpd-cgi]
    +
    +# ³¡! +

    + +
    top
    +
    +

    mod_rewrite¸¦ + »ç¿ëÇÑ È¨ÆäÀÌÁö ½Ã½ºÅÛ

    + +

    ´ÙÀ½Àº µÎ¹ø° ¿¹¿Í °°Àº ÀÏÀ» + ÇÑ´Ù.

    + +

    +RewriteEngine on
    +
    +RewriteMap lowercase int:tolower
    +
    +# CGI°¡ µ¿ÀÛÇϵµ·Ï
    +RewriteCond %{REQUEST_URI} !^/cgi-bin/
    +
    +# RewriteRuleÀÌ µ¿ÀÛÇϵµ·Ï È£½ºÆ®¸íÀÌ ¿Ã¹Ù¸¥Áö °Ë»çÇÑ´Ù
    +RewriteCond ${lowercase:%{SERVER_NAME}} ^www\.[a-z-]+\.isp\.com$
    +
    +# °¡»óÈ£½ºÆ®¸íÀ» URI ¾Õ¿¡ ºÙÀδÙ
    +# [C]´Â ÀÌ °á°ú¸¦ °¡Áö°í ´ÙÀ½ ÀçÀÛ¼ºÀ» ¼öÇàÇÔÀ» ¶æÇÑ´Ù
    +RewriteRule ^(.+) ${lowercase:%{SERVER_NAME}}$1 [C]
    +
    +# ÀÌÁ¦ ½ÇÁ¦ ÆÄÀϸíÀ» ¸¸µç´Ù
    +RewriteRule ^www\.([a-z-]+)\.isp\.com/(.*) /home/$1/$2
    +
    +# Àüü CGI µð·ºÅ丮¸¦ Á¤ÀÇÇÑ´Ù
    +ScriptAlias /cgi-bin/ /www/std-cgi/ +

    + +
    top
    +
    +

    º°µµÀÇ °¡»óÈ£½ºÆ® ¼³Á¤ÆÄÀÏ + »ç¿ëÇϱâ

    + +

    ´ÙÀ½Àº mod_rewriteÀÇ °í±Þ ±â´ÉÀ» »ç¿ëÇÏ¿© + º°µµÀÇ ¼³Á¤ÆÄÀÏÀ» °¡Áö°í °¡»óÈ£½ºÆ®ÀÇ ¹®¼­·çÆ®¸¦ ¾Ë¾Æ³½´Ù. + ´õ À¯¿¬ÇÏÁö¸¸ ´õ º¹ÀâÇÑ ¼³Á¤ÀÌ ÇÊ¿äÇÏ´Ù.

    + +

    vhost.map ÆÄÀÏÀº ´ÙÀ½°ú °°´Ù:

    + +

    +www.customer-1.com /www/customers/1
    +www.customer-2.com /www/customers/2
    +# ...
    +www.customer-N.com /www/customers/N
    +

    + +

    http.conf´Â ´ÙÀ½°ú °°´Ù:

    + +

    +RewriteEngine on
    +
    +RewriteMap lowercase int:tolower
    +
    +# ´ëÀÀÆÄÀÏÀ» Á¤ÀÇÇÑ´Ù
    +RewriteMap vhost txt:/www/conf/vhost.map
    +
    +# À§¿Í °°ÀÌ aliasµéÀ» ó¸®ÇÑ´Ù
    +RewriteCond %{REQUEST_URI} !^/icons/
    +RewriteCond %{REQUEST_URI} !^/cgi-bin/
    +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$
    +# ÆÄÀÏ ³»¿ëÀ» °¡Áö°í ã´Â´Ù
    +RewriteCond ${vhost:%1} ^(/.*)$
    +RewriteRule ^/(.*)$ %1/docs/$1
    +
    +RewriteCond %{REQUEST_URI} ^/cgi-bin/
    +RewriteCond ${lowercase:%{SERVER_NAME}} ^(.+)$
    +RewriteCond ${vhost:%1} ^(/.*)$
    +RewriteRule ^/(.*)$ %1/cgi-bin/$1 +

    + +
    +
    +

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

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/name-based.html b/docs/manual/vhosts/name-based.html new file mode 100644 index 00000000..ceb5e666 --- /dev/null +++ b/docs/manual/vhosts/name-based.html @@ -0,0 +1,19 @@ +URI: name-based.html.de +Content-Language: de +Content-type: text/html; charset=ISO-8859-1 + +URI: name-based.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: name-based.html.fr +Content-Language: fr +Content-type: text/html; charset=ISO-8859-1 + +URI: name-based.html.ja.euc-jp +Content-Language: ja +Content-type: text/html; charset=EUC-JP + +URI: name-based.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/vhosts/name-based.html.de b/docs/manual/vhosts/name-based.html.de new file mode 100644 index 00000000..e4f8d2c6 --- /dev/null +++ b/docs/manual/vhosts/name-based.html.de @@ -0,0 +1,268 @@ + + + +Unterstützung namensbasierter virtueller Hosts - Apache HTTP Server + + + + +
    +

    Module | Direktiven | FAQ | Glossar | Seitenindex

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Unterstützung namensbasierter virtueller Hosts

    +
    +

    Verfügbare Sprachen:  de  | + en  | + fr  | + ja  | + ko 

    +
    + +

    Das Dokument beschreibt, wann und wie namensbasierte virtuelle Hosts zu + verwenden sind.

    +
    + +
    top
    +
    +

    Namensbasierte gegenüber IP-basierten + virtuellen Hosts

    + +

    IP-basierte virtuelle Hosts verwenden die IP-Adresse der Verbindung, um den + korrekten virtuellen Host zur Bedienung einer Anfrage zu ermitteln. Folglich + benötigen Sie eine IP-Adresse für jeden virtuellen Host. Bei der + Verwendung von namensbasierten virtuellen Hosts verläßt sich der + Server darauf, dass der Client den Hostnamen als Bestandteil der HTTP-Header + angibt. Durch Anwendung dieser Technik können sich mehrere verschiedene + Hosts die gleiche IP-Adresse teilen.

    + +

    Die Verwendung von namensbasierten virtuellen Hosts ist gewöhnlich + einfacher. Sie müssen lediglich Ihren DNS-Server darauf einstellen, + jeden Hostnamen auf die richtige IP-Adresse abzubilden, und dann den Apache + HTTP Server so konfigurieren, dass er die verschiedenen Hostnamen erkennt. + Namensbasierte virtuelle Hosts entschärfen auch den Bedarf an + knappen IP-Adressen. Daher sollten Sie namensbasierte virtuelle Hosts + verwenden, sofern kein besonderer Grund dafür existiert, IP-basierte + virtuelle Hosts zu wählen. Mögliche Gründe für die + Verwendung IP-basierter virtueller Hosts sind:

    + +
      +
    • Einige antike Clients sind nicht kompatibel zu namensbasierten + virtuellen Hosts. Damit namensbasierte virtuelle Hosts funktionieren, + muss der Client den HTTP-Host-Header senden. Dies ist bei HTTP/1.1 + vorgeschrieben und in allen modernen HTTP/1.0-Browsern als Erweiterung + implementiert. Wenn Sie Unterstützung für veraltete Clients + benötigen und dennoch namensbasierte virtuelle Hosts verwenden, + dann finden Sie eine mögliche Lösung dafür am Ende des + Dokuments.
      • + +
    • Namensbasierte virtuelle Hosts können aufgrund der Natur des + SSL-Protokolls nicht mit SSL-gesicherten Servern verwendet werden.
      • + +
    • Einige Betriebssysteme und Netzwerkanlagen setzen Techniken zum + Bandbreiten-Management ein, die nicht zwischen Hosts unterscheiden + können, wenn diese nicht auf verschiedenen IP-Adressen liegen.
      • +
    + +
    top
    +
    +

    Die Verwendung von namensbasierten virtuellen Hosts

    + +
    Referenzierte ModuleReferenzierte Direktiven
    + +

    Um namensbasierte virtuelle Hosts zu verwenden, müssen Sie die + IP-Adresse (und möglicherweise den Port) des Servers benennen, an + der Anfragen für die Hosts entgegengenommen werden. Dies wird mit + der Direktive NameVirtualHost + eingestellt. Im Normalfall, wenn alle IP-Adressen des Server verwendet + werden sollen, können Sie * als Argument für + NameVirtualHost verwenden. Wenn Sie + vorhaben, mehrere Ports zu nutzen (etwa wenn SSL läuft), sollten + Sie dem Argument einen Port hinzufügen, wie zum Beispiel + *:80. Beachten Sie, + dass die Angabe einer IP-Adresse in einer NameVirtualHost-Anweisung den Server nicht + automatisch an dieser Adresse lauschen läßt. Lesen Sie bitte "Bestimmen der vom Apache verwendeten Adressen und + Ports" für weitere Details. Zusätzlich muss jede hier + angegebene IP-Adresse einer Netzwerkkarte des Servers zugeordnet sein.

    + +

    Der nächste Schritt ist die Erstellung eines <VirtualHost>-Blocks für jeden einzelnen + Host, den Sie bedienen wollen. Das Argument der Direktive <VirtualHost> sollte das gleiche + sein wie das Argument der NameVirtualHost-Anweisung (d.h. eine IP-Adresse + oder * für alle Adressen). Innerhalb jedes <VirtualHost>-Blocks benötigen + Sie zumindestens eine ServerName-Anweisung, um zu bestimmen, welcher + Host bedient wird, und eine DocumentRoot-Anweisung, um anzugeben, wo im + Dateisystem der Inhalt des Hosts abgelegt ist.

    + +

    Der Hauptserver verschwindet

    + Wenn Sie virtuelle Hosts zu einem bestehenden Webserver hinzufügen, + müssen Sie auch einen <VirtualHost>-Block für den bestehenden Host + (Anm.d.Ü.: und bisherigen Hauptserver) erstellen. + Die ServerName- und + DocumentRoot-Anweisungen zu diesem + virtuellen Host sollten die gleichen sein wie die globalen ServerName- und DocumentRoot-Anweisungen. Führen Sie diesen + virtuellen Host als erstes in der Konfigurationsdatei auf, so dass er als + Standard-Host fungiert. +
    + +

    Vorausgesetzt, Sie bedienen z.B. die Domain + www.domain.tld und möchten den virtuellen Host + www.otherdomain.tld hinzufügen, welcher auf + die gleiche IP-Adresse zeigt. Dann fügen Sie einfach Folgendes der + httpd.conf hinzu:

    + +

    + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + ServerName www.domain.tld
    + ServerAlias domain.tld *.domain.tld
    + DocumentRoot /www/domain
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + ServerName www.otherdomain.tld
    + DocumentRoot /www/otherdomain
    +     + </VirtualHost>
    +

    + +

    Sie können anstelle des * bei den beiden Anweisungen + NameVirtualHost und <VirtualHost> alternativ eine + eindeutige IP-Adresse angeben. Das kann man beispielsweise machen, um + einige namensbasierte virtuelle Hosts auf einer IP-Adresse zu betreiben und + entweder IP-basierte oder ein anderes Set von namensbasierten virtuellen + Hosts auf einer anderen Adresse.

    + +

    Viele Server wollen unter mehr als einem Namen erreichbar sein. Die + Direktive ServerAlias, die innerhalb + des <VirtualHost>-Abschnittes angegeben wird, + ermöglicht dies. Zum Beispiel zeigt die ServerAlias-Anweisung in dem ersten <VirtualHost>-Block oben an, dass die + aufgeführten Namen alternative Namen sind, die man verwenden kann, um + das gleiche Webangebot zu erreichen:

    + +

    + ServerAlias domain.tld *.domain.tld +

    + +

    Anfragen für alle Hosts der Domain domain.tld werden + von dem virtuellen Host www.domain.tld bedient. Die + Platzhalter * und ? können anstelle + entsprechender Namen verwendet werden. Natürlich können Sie nicht + einfach Namen erfinden und diese bei ServerName oder ServerAlias + angeben, Sie müssen zunächst Ihren DNS Server entsprechend + konfigurieren, dass er diese Namen auf die mit Ihrem Server verknüpfte + IP-Adresse abbildet.

    + +

    Und schlußendlich können Sie die Konfiguration der virtuellen + Hosts mittels Angabe weiterer Direktiven innherhalb der <VirtualHost>-Container + feineinstellen. Die meisten Direktiven können in diesen Containern + angegeben werden und verändern dann ausschließlich die + Konfiguration des entsprechenden virtuellen Hosts. Prüfen Sie den Kontext einer Direktive, um + herauszufinden, ob eine bestimmte Direktive zulässig ist. + Im Hauptserver-Kontext (außerhalb der <VirtualHost>-Container) definierte + Konfigurationsanweisungen werden nur dann angewendet, wenn sie nicht durch + Einstellungen des virtuellen Hosts außer Kraft gesetzt wurden.

    + +

    Wenn nun eine Anfrage eintrifft, prüft der Server zuerst, ob sie eine + IP-Adresse verwendet, die der NameVirtualHost-Anweisung entspricht. Ist dies der + Fall, dann sieht er sich jeden <VirtualHost>-Abschnitt mit einer passenden + IP-Adresse an und versucht den einen zu finden, dessen ServerName- oder ServerAlias-Anweisung mit dem gewünschten + Hostnamen übereinstimmt. Findet er einen, dann verwendet er die + Konfiguration dieses Servers. Wird kein passender virtueller Host gefunden, + dann wird der erste angegeben virtuelle Host verwendet, + dessen IP-Adresse paßt.

    + +

    Die Folge davon ist, dass der erste aufgeführte virtuelle Host der + Standard-Virtual-Host ist. Die DocumentRoot-Anweisung des Hauptservers + wird niemals verwendet, wenn eine IP-Adresse mit einer + NameVirtualHost-Anweisung + übereinstimmt. Wenn Sie eine spezielle Konfiguration für Anfragen + angeben möchten, die keinem bestimmten virtuellen Host entsprechen, + packen Sie diese Konfiguration einfach in einen <VirtualHost>-Container und führen diesen als + erstes in der Konfigurationsdatei auf.

    + +
    top
    +
    +

    Kompatibilität mit älteren Browsern

    + +

    Wie zuvor erwähnt gibt es einige Clients, die nicht die notwendigen + Daten senden, mit denen namensbasierte virtuelle Hosts korrekt + funktionieren. Diesen Clients werden stets die Seiten des ersten, für + diese IP-Adresse aufgeführten virtuellen Hosts gesendet werden (des + primären namensbasierten virtuellen Hosts).

    + +

    Was bedeutet älter?

    +

    Beachten Sie bitte, wenn wir von älter sprechen, meinen wir auch + älter. Es ist sehr unwahrscheinlich, dass sie einen dieser Browser + heutzutage in Verwendung finden werden. Alle aktuellen Browser-Versionen + senden den Host-Header, so wie er für namensbasierte + virtuelle Hosts benäötigt wird.

    +
    + +

    Mit der Direktive ServerPath existiert + eine mögliche Behelfskonstruktion, obgleich sie etwas schwerfällig + ist:

    + +

    Beispielkonfiguration:

    + +

    + NameVirtualHost 111.22.33.44
    +
    + <VirtualHost 111.22.33.44>
    + + ServerName www.domain.tld
    + ServerPath /domain
    + DocumentRoot /web/domain
    +     + </VirtualHost>
    +

    + +

    Was bedeutet das? Es bedeutet, dass eine Anfrage für eine mit + "/domain" beginnende URI von dem virtuellen Host + www.domain.tld bedient wird. Dies heißt, dass die Seiten + für alle Clients unter http://www.domain.tld/domain/ + abrufbar sind, wenngleich Clients, die den Header Host: + senden, auch über http://www.domain.tld/ auf sie zugreifen + können.

    + +

    Legen Sie einen Link auf der Seite Ihres primären virtuellen Hosts zu + http://www.domain.tld/domain/, um die Behelfslösung + verfügbar zu machen. Bei den Seiten der virtuellen Hosts müssen + Sie dann sicherstellen, entweder außschließlich relative Links + (z.B. "file.html" oder + "../icons/image.gif") zu verwenden oder Links, die das + einleitende /domain/ enthalten (z.B., + "http://www.domain.tld/domain/misc/file.html" oder + "/domain/misc/file.html").

    + +

    Dies erfordert etwas Disziplin, die Befolgung dieser Richtlinien stellt + jedoch größtenteils sicher, dass Ihre Seiten mit allen Browsern + funktionieren, alten wie neuen.

    + +
    +
    +

    Verfügbare Sprachen:  de  | + en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/name-based.html.en b/docs/manual/vhosts/name-based.html.en new file mode 100644 index 00000000..a520df33 --- /dev/null +++ b/docs/manual/vhosts/name-based.html.en @@ -0,0 +1,246 @@ + + + +Name-based Virtual Host Support - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    Name-based Virtual Host Support

    +
    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko 

    +
    + +

    This document describes when and how to use name-based virtual hosts.

    +
    + +
    top
    +
    +

    Name-based vs. IP-based Virtual Hosts

    + +

    IP-based virtual hosts use the IP address of the connection to + determine the correct virtual host to serve. Therefore you need to + have a separate IP address for each host. With name-based virtual + hosting, the server relies on the client to report the hostname as + part of the HTTP headers. Using this technique, many different hosts + can share the same IP address.

    + +

    Name-based virtual hosting is usually simpler, since you need + only configure your DNS server to map each hostname to the correct + IP address and then configure the Apache HTTP Server to recognize + the different hostnames. Name-based virtual hosting also eases + the demand for scarce IP addresses. Therefore you should use + name-based virtual hosting unless there is a specific reason to + choose IP-based virtual hosting. Some reasons why you might consider + using IP-based virtual hosting:

    + +
      +
    • Some ancient clients are not compatible with name-based virtual + hosting. For name-based virtual hosting to work, the client must send + the HTTP Host header. This is required by HTTP/1.1, and is + implemented by all modern HTTP/1.0 browsers as an extension. If you + need to support obsolete clients and still use name-based virtual + hosting, a possible technique is discussed at the end of this + document.
      • + +
    • Name-based virtual hosting cannot be used with SSL secure servers + because of the nature of the SSL protocol.
      • + +
    • Some operating systems and network equipment implement bandwidth + management techniques that cannot differentiate between hosts unless + they are on separate IP addresses.
      • +
    + +
    top
    +
    +

    Using Name-based Virtual Hosts

    + +
    Related ModulesRelated Directives
    + +

    To use name-based virtual hosting, you must designate the IP + address (and possibly port) on the server that will be accepting + requests for the hosts. This is configured using the NameVirtualHost directive. + In the normal case where any and all IP addresses on the server should + be used, you can use * as the argument to NameVirtualHost. If you're planning to use + multiple ports (e.g. running SSL) you should add a Port to the argument, + such as *:80. Note that mentioning an IP address in a + NameVirtualHost directive does not + automatically make the server listen to that IP address. See + Setting which addresses and ports Apache uses + for more details. In addition, any IP address specified here must be + associated with a network interface on the server.

    + +

    The next step is to create a <VirtualHost> block for + each different host that you would like to serve. The argument to the + <VirtualHost> directive + should be the same as the argument to the NameVirtualHost directive (ie, an IP address, + or * for all addresses). Inside each <VirtualHost> block, you will need at minimum a + ServerName directive to designate + which host is served and a DocumentRoot + directive to show where in the filesystem the content for that host + lives.

    + +

    Main host goes away

    +

    If you are adding virtual hosts to an existing web server, you + must also create a <VirtualHost> block for the existing host. The ServerName and DocumentRoot included in this virtual host should be the + same as the global ServerName and + DocumentRoot. List this virtual + host first in the configuration file so that it will act as the default + host.

    +
    + +

    For example, suppose that you are serving the domain + www.domain.tld and you wish to add the virtual host + www.otherdomain.tld, which points at the same IP address. + Then you simply add the following to httpd.conf:

    + +

    + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + ServerName www.domain.tld
    + ServerAlias domain.tld *.domain.tld
    + DocumentRoot /www/domain
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + ServerName www.otherdomain.tld
    + DocumentRoot /www/otherdomain
    +     + </VirtualHost>
    +

    + +

    You can alternatively specify an explicit IP address in place of the + * in both the NameVirtualHost and <VirtualHost> directives. For example, you might want to do this + in order to run some name-based virtual hosts on one IP address, and either + IP-based, or another set of name-based virtual hosts on another address.

    + +

    Many servers want to be accessible by more than one name. This is + possible with the ServerAlias + directive, placed inside the <VirtualHost> section. For example in the first <VirtualHost> block above, the + ServerAlias directive indicates that + the listed names are other names which people can use to see that same + web site:

    + +

    + ServerAlias domain.tld *.domain.tld +

    + +

    then requests for all hosts in the domain.tld domain will + be served by the www.domain.tld virtual host. The wildcard + characters * and ? can be used to match names. + Of course, you can't just make up names and place them in ServerName or ServerAlias. You must + first have your DNS server properly configured to map those names to an IP + address associated with your server.

    + +

    Finally, you can fine-tune the configuration of the virtual hosts + by placing other directives inside the <VirtualHost> containers. Most directives can be + placed in these containers and will then change the configuration only of + the relevant virtual host. To find out if a particular directive is allowed, + check the Context of the + directive. Configuration directives set in the main server context + (outside any <VirtualHost> + container) will be used only if they are not overridden by the virtual host + settings.

    + +

    Now when a request arrives, the server will first check if it is using + an IP address that matches the NameVirtualHost. If it is, then it will look at each <VirtualHost> section with a matching + IP address and try to find one where the ServerName or ServerAlias matches the requested + hostname. If it finds one, then it uses the configuration for that server. + If no matching virtual host is found, then the first listed virtual + host that matches the IP address will be used.

    + +

    As a consequence, the first listed virtual host is the default + virtual host. The DocumentRoot from + the main server will never be used when an IP + address matches the NameVirtualHost + directive. If you would like to have a special configuration for requests + that do not match any particular virtual host, simply put that configuration + in a <VirtualHost> + container and list it first in the configuration file.

    + +
    top
    +
    +

    Compatibility with Older Browsers

    + +

    As mentioned earlier, there are some clients + who do not send the required data for the name-based virtual + hosts to work properly. These clients will always be sent the + pages from the first virtual host listed for that IP address + (the primary name-based virtual host).

    + +

    How much older?

    +

    Please note that when we say older, we really do mean older. You are + very unlikely to encounter one of these browsers in use today. All + current versions of any browser send the Host header as + required for name-based virtual hosts.

    +
    + +

    There is a possible workaround with the ServerPath + directive, albeit a slightly cumbersome one:

    + +

    Example configuration:

    + +

    + NameVirtualHost 111.22.33.44
    +
    + <VirtualHost 111.22.33.44>
    + + ServerName www.domain.tld
    + ServerPath /domain
    + DocumentRoot /web/domain
    +     + </VirtualHost>
    +

    + +

    What does this mean? It means that a request for any URI + beginning with "/domain" will be served from the + virtual host www.domain.tld. This means that the + pages can be accessed as http://www.domain.tld/domain/ + for all clients, although clients sending a Host: header + can also access it as http://www.domain.tld/.

    + +

    In order to make this work, put a link on your primary + virtual host's page to + http://www.domain.tld/domain/. Then, in the virtual + host's pages, be sure to use either purely relative links + (e.g., "file.html" or + "../icons/image.gif") or links containing the + prefacing /domain/ (e.g., + "http://www.domain.tld/domain/misc/file.html" or + "/domain/misc/file.html").

    + +

    This requires a bit of discipline, but adherence to these + guidelines will, for the most part, ensure that your pages will + work with all browsers, new and old.

    + +
    +
    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/name-based.html.fr b/docs/manual/vhosts/name-based.html.fr new file mode 100644 index 00000000..ea41781a --- /dev/null +++ b/docs/manual/vhosts/name-based.html.fr @@ -0,0 +1,298 @@ + + + +Support Apache des serveurs virtuels par nom - Serveur Apache HTTP + + + + +
    +

    Modules | Directives | FAQ | Glossaire | Plan du site

    +

    Serveur Apache HTTP Version 2.2

    +
    +
    <-
    +

    Support Apache des serveurs virtuels par nom

    +
    +

    Langues Disponibles:  de  | + en  | + fr  | + ja  | + ko 

    +
    + +

    Ce document décrit quand et comment utiliser des serveurs + virtuels par nom.

    +
    + +
    top
    +
    +

    Serveurs virtuels par nom vs. par IP

    + +

    Les hébergements virtuels par IP utilisent l'adresse IP + de la connexion afin de déterminer quel serveur virtuel doit + répondre. Par conséquent, vous devez disposer d'adresses IP + différentes pour chaque nom de domaine complet (FQDN) que vous hébergez. + Avec un hébergement + virtuel par nom, le serveur s'appuit sur les informations + transmises par le client dans les en-têtes HTTP de ses requêtes. + La technique présentée ici vous permet de disposer de serveurs + virtuels différents partagés sur une même adresse IP.

    + +

    L'hébergement virtuel par nom est habituellement plus simple, + car il vous suffit de configurer votre serveur DNS pour que + chaque domaine pointe sur l'adresse IP dont vous disposez, et de + configurer votre serveur Apache HTTP afin qu'il reconnaisse + ces domaines. Il réduit aussi la pénurie en adresses IP. Par + conséquent, vous devriez utiliser l'hébergement virtuel par + nom à moins d'avoir une raison spécifique de préférer + l'hébergement virtuel par IP. Certaines de ces raisons vous + sont exposées ci-après :

    + +
      +
    • Certains anciens navigateurs ne sont pas compatibles + avec les serveurs virtuels par nom, car pour fonctionner, + un client doit transmettre un champ d'en-tête HTTP Host. + Cet en-tête est exigé pour HTTP/1.1, et peut être implémenté + sur des navigateurs modernes HTTP/1.0 grâce à une extension. + Si vous devez maintenir des clients obsolètes tout en + utilisant l'hébergement virtuel par nom, il existe une + technique qui est traitée à la fin de ce document.
      • + +
    • L'hébergement virtuel par nom ne peut pas être utilisé + avec des serveurs sécurisés SSL à cause de la nature même + du protocole SSL.
      • + +
    • Certains systèmes d'exploitation et équipements réseaux + emploient des techniques de gestion de la bande passante + qui ne peuvent pas différencier des domaines autrement que + par des adresses IP séparées.
      • +
    + +
    top
    +
    +

    Utilisation de serveurs virtuels par nom

    + +
    Modules ApparentésDirectives Apparentées
    + +

    Pour utiliser des serveurs virtuels par nom, vous devez + désigner l'adresse IP (et si possible le port) sur le serveur + devant accepter les requêtes pour des domaines. Cette + configuration utilise la directive + NameVirtualHost. Dans un + cas normal où n'importe quelle adresse IP peut être utilisée, + vous pouvez ajouter * comme argument de la directive + NameVirtualHost. Si vous + prévoyez d'utiliser de multiples ports (comme l'emploi de SSL), + vous devriez ajouter le port à cet argument tel que + *:80. Notez que la simple mention d'une adresse + IP dans une directive + NameVirtualHost ne suffit + pas à faire écouter le serveur sur cette IP. Consultez + la page sur les liaisons pour plus + de détails. Par ailleurs, chaque adresse IP spécifiée ici doit + être associée avec une interface réseau sur le serveur.

    + +

    L'étape suivante est la création d'une section + <VirtualHost> + pour chacun des serveurs à créer. L'argument de la directive + <VirtualHost> + doit être le même que celui de la directive + NameVirtualHost + (c'est-à-dire l'adresse IP ou * pour toutes les + adresses). Dans chaque section + <VirtualHost>, + vous devez définir au minimum une directive + ServerName pour désigner + le serveur concerné et une directive + DocumentRoot pour préciser + l'emplacement sur le système de fichiers du contenu de ce serveur.

    + +

    Le serveur principal disparaît

    +

    Si vous ajoutez des serveurs virtuels à un serveur Web + existant, vous devez également créer une section + <VirtualHost> + redéfinissant ce serveur existant. Les directives + ServerName et + DocumentRoot incluses + dans ce serveur virtuel doivent être les mêmes que pour + les directives globales + ServerName et + DocumentRoot. Positionnez + ce serveur virtuel en premier dans le fichier de configuration + pour en faire le serveur par défaut.

    +
    + +

    Par exemple, supposez que vous hébergez le domaine + www.domain.tld et que vous souhaitez ajouter le + serveur virtuel www.otherdomain.tld qui pointe sur + la même adresse IP. Il vous suffit d'ajouter la configuration + suivante à httpd.conf :

    + +

    + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + ServerName www.domain.tld
    + ServerAlias domain.tld *.domain.tld
    + DocumentRoot /www/domain
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + ServerName www.otherdomain.tld
    + DocumentRoot /www/otherdomain
    +     + </VirtualHost>
    +

    + +

    Autrement, vous pouvez spécifiez une adresse IP explicite + à la place de * dans les deux directives + NameVirtualHost et + <VirtualHost>. + Par exemple, cette méthode est utile si vous souhaitez faire + tourner quelques serveurs virtuels par nom sur une même adresse + IP, et d'autres, soit par IP, soit basés sur un autre jeu de + serveurs virtuels par nom sur une autre adresse IP.

    + +

    Plusieurs serveurs sont accessibles par plus d'un nom. Il + suffit de placer la directive + ServerAlias dans une section + <VirtualHost>. + Par exemple, dans la première section + <VirtualHost> + ci-dessus, la directive ServerAlias + indique aux utilisateurs les autres noms permis pour accéder au + même site Web :

    + +

    + ServerAlias domain.tld *.domain.tld +

    + +

    ainsi, toutes les requêtes portant sur un domaine + domain.tld seront servies par le serveur virtuel + www.domain.tld. Les caractères joker * + et ? peuvent être utilisés pour les correspondances. + Bien entendu, vous ne pouvez pas inventer des noms et les placer + dans une directive ServerName + ou ServerAlias. Tout d'abord, votre serveur DNS + doit être correctement configuré pour lier ces noms à une + adresse IP associée avec votre serveur.

    + +

    Finalement, vous pouvez affiner la configuration des serveurs + virtuels en plaçant d'autres directives à l'intérieur des sections + <VirtualHost>. + La plupart des directives peut être placée dans ces sections en + y changeant seulement la configuration du serveur virtuel associé. + Pour déterminer si une directive particulière est permise, + consultez la page de + contexte. Le jeu de directives configurées dans le contexte + du serveur principal (en dehors de toutes sections + <VirtualHost>) + sera utilisé seulement s'il n'y a pas de configuration contraire + par un serveur virtuel.

    + +

    Maintenant, lorsqu'une requête arrive, le serveur va d'abord + tester si elle utilise une adresse IP qui correspond à + NameVirtualHost. Si c'est + le cas, il regardera chaque section + <VirtualHost> + avec l'adresse correspondante et essaiera d'en trouver une où + le nom de domaine requis correspond à + ServerName ou + ServerAlias. S'il en trouve une, il utilisera + sa configuration pour le serveur. Si aucun serveur virtuel ne + correspond, alors le premier serveur virtuel listé + dont l'adresse IP correspond sera employé.

    + +

    En conséquence, le premier serveur virtuel listé est le + serveur virtuel default. La directive + DocumentRoot du + serveur principal ne sera + jamais employée lorsqu'une adresse IP + correspond dans une directive + NameVirtualHost. Si vous + ne voulez pas avoir de configuration spéciale pour les requêtes + qui ne sont pas attachées à un serveur virtuel en particulier, + mettez cette configuration dans une section + <VirtualHost> + que vous placerez en premier dans le fichier de configuration.

    + +
    top
    +
    +

    Compatibilité avec les navigateurs anciens

    + +

    Comme mentionné plus tôt, certains clients ne transmettent + pas les données nécessaires pour le bon fonctionnement des + serveurs virtuels. Ces clients recevront toujours les pages + du premier serveur virtuel listé pour cette adresse IP (le + serveur virtuel par nom primaire).

    + +

    De combien plus anciens ?

    +

    Veuillez noter que quand nous disons plus anciens, nous + disons vraiment plus anciens. Vous seriez malchanceux de rencontrer + de tels navigateurs encore utilisés de nos jours. Toutes les + versions actuelles des navigateurs transmettent leur en-tête + Host comme exigé par les serveurs virtuels par nom.

    +
    + +

    Il existe une solution avec la directive + ServerPath, bien que + légèrement complexe :

    + +

    Exemple de configuration :

    + +

    + NameVirtualHost 111.22.33.44
    +
    + <VirtualHost 111.22.33.44>
    + + ServerName www.domain.tld
    + ServerPath /domain
    + DocumentRoot /web/domain
    +     + </VirtualHost>
    +

    + +

    Qu'est-ce que cela signifie ? Il signifie qu'une requête + pour tout URI qui commence par "/domain" sera + servie par le serveur virtuel www.domain.tld. + Ainsi, les pages sont accessibles à + http://www.domain.tld/domain/ pour tous les + clients, bien que ceux qui transmettent un en-tête + Host: peuvent également y accéder à + http://www.domain.tld/.

    + +

    Pour rendre cette technique fonctionnelle, mettez un lien + dans votre serveur virtuel primaire vers + http://www.domain.tld/domain/. Ensuite, dans les + pages de ce serveur virtuel, assurez vous ne n'utiliser que + des liens relatifs (par exemple, "file.html" + ou "../icons/image.gif") ou des liens contenant + le préfixe /domain/ (par exemple, + "http://www.domain.tld/domain/misc/file.html" + ou "/domain/misc/file.html").

    + +

    Cela requiert un peu de discipline, mais si vous suivez + cette ligne de conduite, vous serez assuré que vos pages + s'afficheront dans tous les navigateurs, nouveaux et anciens.

    + +
    +
    +

    Langues Disponibles:  de  | + en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/name-based.html.ja.euc-jp b/docs/manual/vhosts/name-based.html.ja.euc-jp new file mode 100644 index 00000000..1bb94f38 --- /dev/null +++ b/docs/manual/vhosts/name-based.html.ja.euc-jp @@ -0,0 +1,271 @@ + + + +̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È - Apache HTTP ¥µ¡¼¥Ð + + + + +
    +

    ¥â¥¸¥å¡¼¥ë | ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö | FAQ | ÍѸì | ¥µ¥¤¥È¥Þ¥Ã¥×

    +

    Apache HTTP ¥µ¡¼¥Ð ¥Ð¡¼¥¸¥ç¥ó 2.2

    +
    +
    <-
    +

    ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È

    +
    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko 

    +
    + +

    ¤³¤Îʸ½ñ¤Ç¤Ï̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò¤É¤ó¤Ê¤È¤­¡¢ + ¤É¤¦¤ä¤Ã¤Æ»È¤¦¤«¤òÀâÌÀ¤·¤Þ¤¹¡£

    +
    + +
    top
    +
    +

    ̾Á°¥Ù¡¼¥¹¤È IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÈæ³Ó

    + +

    IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ç¤Ï¡¢±þÅú¤¹¤ë + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ø¤Î¥³¥Í¥¯¥·¥ç¥ó¤ò·èÄꤹ¤ë¤¿¤á¤Ë IP + ¥¢¥É¥ì¥¹¤ò»ÈÍѤ·¤Þ¤¹¡£¤Ç¤¹¤«¤é¡¢¤½¤ì¤¾¤ì¤Î¥Û¥¹¥È¤Ë¸Ä¡¹¤Ë IP + ¥¢¥É¥ì¥¹¤¬É¬Íפˤʤê¤Þ¤¹¡£¤³¤ì¤ËÂФ·¤Æ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ç¤Ï¡¢ + ¥¯¥é¥¤¥¢¥ó¥È¤¬ HTTP ¥Ø¥Ã¥À¤Î°ìÉô¤È¤·¤Æ¥Û¥¹¥È̾¤ò¹ð¤²¤ë¡¢ + ¤È¤¤¤¦¤³¤È¤Ë°Í¸¤·¤Þ¤¹¡£¤³¤Îµ»½Ñ¤ÇƱ°ì IP + ¥¢¥É¥ì¥¹¤ò°Û¤Ê¤ë¿¿ô¤Î¥Û¥¹¥È¤Ç¶¦Í­¤·¤Æ¤¤¤Þ¤¹¡£

    + +

    ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÏÄ̾ïñ½ã¤Ç¡¢¤½¤ì¤¾¤ì¤Î¥Û¥¹¥È̾¤È + ¤½¤ì¤ËÂбþ¤¹¤ëÀµ³Î¤Ê IP ¥¢¥É¥ì¥¹¤ò DNS ¤ÇÀßÄꤷ¡¢°Û¤Ê¤ë + ¥Û¥¹¥È̾¤ò¶èÊ̤¹¤ë¤è¤¦¤Ë Apache HTTP ¥µ¡¼¥Ð¤òÀßÄꤹ¤ë¤À¤±¤Ç¤¹¡£ + ¤µ¤é¤Ë¡¢Ì¾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÏÉÔ­¤¹¤ë IP + ¥¢¥É¥ì¥¹¤Î¼ûÍפò´ËϤ·¤Þ¤¹¡£¤·¤¿¤¬¤Ã¤Æ¡¢IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò + ÁªÂò¤¹¤Ù¤­ÆÃÄê¤ÎÍýͳ¤¬¤Ê¤±¤ì¤Ð̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò»È¤¦¤Ù¤­¤Ç¤¹¡£ + IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò»ÈÍѤ¹¤ë¤³¤È¤ò¹Íθ¤¹¤ëÍýͳ¤È¤·¤Æ¡¢

    + +
      +
    • ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËÂбþ¤·¤Æ¤¤¤Ê¤¤¸Å¤¤¥¯¥é¥¤¥¢¥ó¥È¤¬¤¢¤ë + ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬Æ¯¤¯¤¿¤á¤Ë¤Ï¡¢¥¯¥é¥¤¥¢¥ó¥È¤Ï + HTTP ¥Û¥¹¥È¥Ø¥Ã¥À¤òÁ÷¤Ã¤Æ¤³¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£ + ¤³¤ì¤Ï HTTP/1.1 ¤Î»ÅÍͤÇÍ׵ᤵ¤ì¤Æ¤¤¤Æ¡¢¤¹¤Ù¤Æ¤Î¸½ÂåŪ¤Ê + HTTP/1.0 ¥Ö¥é¥¦¥¶¤Ç¤â³ÈÄ¥¤È¤·¤Æ¼ÂÁõ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ + ¤È¤Æ¤â¸Å¤¤¥¯¥é¥¤¥¢¥ó¥È¤ò¥µ¥Ý¡¼¥È¤·¤Ä¤Ä¡¢Ì¾Á°¥Ù¡¼¥¹¤Î + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò¹Ô¤¤¤¿¤¤¾ì¹ç¤Ï¡¢¤³¤Îʸ½ñ¤ÎºÇ¸å¤ÎÊý¤Ë + ½ñ¤«¤ì¤Æ¤¤¤ë²ò·èºö¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Ê¤¤ÊýË¡¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£
      • + +
    • ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ï SSL ¥×¥í¥È¥³¥ë¤ÎÆÃħ¤Ë¤è¤ê¡¢ + SSL ¥»¥­¥å¥¢¥µ¡¼¥Ð¤Ë¤Ï»È¤¨¤Þ¤»¤ó¡£
      • + +
    • ¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ä¥Í¥Ã¥È¥ï¡¼¥¯ÁõÃ֤Τʤ«¤Ë¤Ï¡¢ + Ê̤ΠIP ¥¢¥É¥ì¥¹¾å¤Ç¤Ê¤¤¾ì¹ç¡¢Ê£¿ô¤Î¥Û¥¹¥È¤òÊÌ°·¤¤¤Ç¤­¤Ê¤¤¤è¤¦¤Ê + ÂÓ°è´ÉÍý¤ÎÊýË¡¤ò¼ÂÁõ¤·¤Æ¤¤¤ë¤â¤Î¤¬¤¢¤ê¤Þ¤¹¡£
      • +
    + +
    top
    +
    +

    ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤òÍøÍѤ¹¤ë

    + +
    ´ØÏ¢¥â¥¸¥å¡¼¥ë´ØÏ¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
    + +

    ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò»È¤¦¤Ë¤Ï¡¢¤½¤Î¥Û¥¹¥È¤Ø¤Î + ¥ê¥¯¥¨¥¹¥È¤ò¼õ¤±ÉÕ¤±¤ë¥µ¡¼¥Ð¤Î IP ¥¢¥É¥ì¥¹ (¤â¤·¤«¤·¤¿¤é¥Ý¡¼¥È¤â) + ¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤ì¤Ï NameVirtualHost + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÀßÄꤷ¤Þ¤¹¡£Ä̾NameVirtualHost ¤Ç + * ¤Î°À­¤ò»È¤Ã¤Æ¥µ¡¼¥Ð¤ÎÁ´¤Æ¤Î IP ¥¢¥É¥ì¥¹¤ò»È¤¤¤Þ¤¹¡£ + (Î㤨¤Ð SSL ¤Î»ÈÍѤʤɤÇ) Ê£¿ô¤Î¥Ý¡¼¥È¤ò»È¤¦¤³¤È¤ò·×²è¤·¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + °ú¿ô¤Ë *:80 ¤Î¤è¤¦¤Ë¥Ý¡¼¥È¤â´Þ¤á¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + NameVirtualHost ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç + IP ¥¢¥É¥ì¥¹¤ò½ñ¤¤¤Æ¤â¡¢ + ¼«Æ°Åª¤Ë¥µ¡¼¥Ð¤¬¤½¤Î IP ¥¢¥É¥ì¥¹¤ò¥ê¥Ã¥¹¥ó¤¹¤ë¤È¤¤¤¦¤³¤È¤Ï¤Ê¤¤¤³¤È¤Ë + Ãí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¾ÜºÙ¤Ï¡ÖApache ¤Î»È¤¦¥¢¥É¥ì¥¹¤È + ¥Ý¡¼¥È¤òÀßÄꤹ¤ë¡×¤òÆɤó¤Ç¤¯¤À¤µ¤¤¡£¤µ¤é¤Ë¡¢¤³¤³¤Ç»ØÄꤵ¤ì¤¿ + IP ¥¢¥É¥ì¥¹¤ÏÁ´¤Æ¥µ¡¼¥Ð¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤È´ØÏ¢ÉÕ¤±¤é¤ì¤Æ + ¤¤¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

    + +

    ¼¡¤Ï¡¢°·¤¦¥Û¥¹¥È¤½¤ì¤¾¤ì¤ËÂФ·¤Æ <VirtualHost> ¥Ö¥í¥Ã¥¯¤ò + ºîÀ®¤·¤Æ¤¯¤À¤µ¤¤¡£<VirtualHost> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô¤Ï NameVirtualHost + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î°ú¿ô¤ÈƱ¤¸¤Ë¤·¤Æ¤¯¤À¤µ¤¤ (¤¹¤Ê¤ï¤Á¡¢IP ¥¢¥É¥ì¥¹¤«¡¢Á´¤Æ¤Î¥¢¥É¥ì¥¹¤ò°ÕÌ£¤¹¤ë + *)¡£¤½¤ì¤¾¤ì¤Î <VirtualHost> + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÎÃæ¤Ë¤Ï¡¢ºÇÄã¸Â¡¢¤É¤Î¥Û¥¹¥È¤¬°·¤ï¤ì¤ë¤«¤ò¼¨¤¹ ServerName ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤È¡¢ + ¤½¤Î¥Û¥¹¥ÈÍѤΥ³¥ó¥Æ¥ó¥Ä¤¬¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¾å¤Î¤É¤³¤Ë¤¢¤ë¤«¤ò¼¨¤¹ + DocumentRoot ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò + ½ñ¤¯É¬Íפ¬¤¢¤ê¤Þ¤¹¡£

    + +

    ¥á¥¤¥ó¥Û¥¹¥È¤Ï¤Ê¤¯¤Ê¤ê¤Þ¤¹

    +

    ´û¤Ë¤¢¤ë¥¦¥§¥Ö¥µ¡¼¥Ð¤Ë¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤òÄɲ乤ë¾ì¹ç¡¢ + ´û¸¤Î¥¦¥§¥Ö¥µ¡¼¥Ð¤ËÂФ·¤Æ¤â <VirtualHost> + ¥Ö¥í¥Ã¥¯¤òºî¤é¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤³¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î + ServerName ¤È + DocumentRoot + ¤Ï¡¢¥°¥í¡¼¥Ð¥ë¤Ê ServerName ¤È + DocumentRoot + ¤ÈƱ¤¸¤â¤Î¤Ë¤·¤Þ¤¹¡£¤Þ¤¿¡¢¤³¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤òÀßÄê¥Õ¥¡¥¤¥ë¤ÎÃæ¤Ç + ÀèƬ¤ËÃÖ¤¤¤Æ¡¢¥Ç¥Õ¥©¥ë¥È¥Û¥¹¥È¤È¤·¤ÆÆ°ºî¤¹¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£

    +
    + +

    ¤¿¤È¤¨¤Ð¡¢www.domain.tld ¤òÆ°¤«¤·¤Æ¤¤¤Æ¡¢ + ¤µ¤é¤Ë¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È www.otherdomain.tld + ¤òÄɲ乤ë¤È¤·¤Þ¤·¤ç¤¦¡£¤³¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÏƱ°ì IP ¤ò»Ø¤·¤Æ¤¤¤ë¤È¤·¤Þ¤¹¡£ + ¤½¤Î¤è¤¦¤Ê¾ì¹ç¤Ï¡¢httpd.conf + ¤Ë°Ê²¼¤Î¤è¤¦¤Ê¥³¡¼¥É¤òÄɲ乤ë¤À¤±¤Ç¤¹

    + +

    + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + ServerName www.domain.tld
    + ServerAlias domain.tld *.domain.tld
    + DocumentRoot /www/domain
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + ServerName www.otherdomain.tld
    + DocumentRoot /www/otherdomain
    +     + </VirtualHost>
    +

    + +

    NameVirtualHost µÚ¤Ó + VirtualHost ¤Î¤É¤Á¤é¤Î¾ì¹ç¤â¡¢ + * ¤ÎÉôʬ¤Ë¤ÏÌÀ¼¨Åª¤Ë IP ¥¢¥É¥ì¥¹¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + Î㤨¤Ð¡¢¤¢¤ë IP ¥¢¥É¥ì¥¹¤Ç¤Ï̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò»È¤¤¤¿¤¤°ìÊý¤Ç¡¢ + Ê̤ΠIP ¥¢¥É¥ì¥¹¤Ç¤Ï¡¢Â¾¤Î IP ¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ä + ÊÌÁȤÎ̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ò»È¤¤¤¿¤¤¾ì¹ç¡¢ + ¤½¤¦ÀßÄꤹ¤ë¤³¤È¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£

    + +

    Ê£¿ô¤Î̾Á°¤Ç¥µ¡¼¥Ð¥¢¥¯¥»¥¹¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤·¤¿¤¤¤³¤È¤â¿¤¤¤Ç¤·¤ç¤¦¡£ + ¤³¤Î¤è¤¦¤Ê¤³¤È¤Ï¡¢ServerAlias ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò <VirtualHost> + ¥»¥¯¥·¥ç¥ó¤Ëµ­½Ò¤¹¤ë¤³¤È¤Ç¼Â¸½¤Ç¤­¤Þ¤¹¡£ + Î㤨¤Ð¾åµ­¤Î <VirtualHost> ¤ÎÎã¤Ç¤¢¤ì¤Ð¡¢ + ¼¡¤Î¤è¤¦¤Ë°ìÍ÷¤Ëµó¤²¤é¤ì¤¿Ì¾Á°¤¬¡¢ + ¥æ¡¼¥¶¤¬Æ±°ì¤Î¥¦¥§¥Ö¥µ¥¤¥È¤È¤·¤ÆÌܤˤ·¤Æ»ÈÍѤǤ­¤ë¥µ¡¼¥Ð̾¤Ç¤¢¤ë¡¢ + ¤È ServerAlias + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄê¤Ç¤­¤Þ¤¹¡£

    + +

    + ServerAlias domain.tld *.domain.tld +

    + +

    domain.tld ¥É¥á¥¤¥ó¤Ø¤ÎÁ´¤Æ¤Î¥Û¥¹¥È¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï + www.domain.tld ¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬½èÍý¤·¤Þ¤¹¡£ + ̾Á°¤ò¥Þ¥Ã¥Á¤µ¤»¤ë¤¿¤á¤Ë¡¢¥ï¥¤¥ë¥É¥«¡¼¥Éʸ»ú * ¤ä ? + ¤ò»ÈÍѤ¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤â¤Á¤í¤ó»×¤¤¤Ä¤­¤Î̾Á°¤òºî¤Ã¤Æ¡¢ + ServerName ¤ä + ServerAlias + ¤Ë¤½¤Î̾Á°¤ò½ñ¤¯¤È¤¤¤Ã¤¿¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£¤Þ¤º¤Ï¡¢ + ¤³¤ì¤é¤Î̾Á°¤¬ ¥µ¡¼¥Ð¤ËÉÕ¤±¤é¤ì¤¿ IP ¥¢¥É¥ì¥¹¤Ë¥Þ¥Ã¥×¤µ¤ì¤ë¤è¤¦¤Ë + DNS ¥µ¡¼¥Ð¤òŬÀÚ¤ËÀßÄꤷ¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£

    + +

    ºÇ¸å¤Ë¡¢<VirtualHost> ¥³¥ó¥Æ¥Ê¤ÎÃæ¤Ë + ¾¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¯¤³¤È¤Ç¡¢¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ÎÀßÄê¤òºÙ¤«¤¯Ä´À° + ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ + ¤Û¤È¤ó¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¤³¤ì¤é¤Î¥³¥ó¥Æ¥Ê¤ËÀßÃÖ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Æ¡¢ + Êѹ¹ÅÀ¤Ï¤½¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËÂФ·¤Æ¤Î¤ßÍ­¸ú¤Ë¤Ê¤ê¤Þ¤¹¡£ + ¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò½ñ¤¯¤³¤È¤¬¤Ç¤­¤ë¤«¤Ï¡¢¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Î ¥³¥ó¥Æ¥­¥¹¥È ¤ò + Ä´¤Ù¤Æ¤¯¤À¤µ¤¤¡£¼ç¥µ¡¼¥Ð¥³¥ó¥Æ¥­¥¹¥È + (<VirtualHost> + ¥³¥ó¥Æ¥Ê¤Î³°) ¤ÎÀßÄêÍѥǥ£¥ì¥¯¥Æ¥£¥Ö¤Ï¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ç¤ÎÀßÄê¤Ç + ¾å½ñ¤­¤µ¤ì¤Ê¤¤¾ì¹ç¤Î¤ß»ÈÍѤµ¤ì¤Þ¤¹¡£

    + +

    ¥ê¥¯¥¨¥¹¥È¤¬Íè¤ë¤È¡¢¥µ¡¼¥Ð¤Ï¤Þ¤ººÇ½é¤Ë <NameVirtualHost> + ¤Ë¥Þ¥Ã¥Á¤¹¤ë IP ¥¢¥É¥ì¥¹¤«¤É¤¦¤«¤ò¥Á¥§¥Ã¥¯¤·¤Þ¤¹¡£¥Þ¥Ã¥Á¤¹¤ì¤Ð + ¥Þ¥Ã¥Á¤·¤¿ IP ¥¢¥É¥ì¥¹¤Î <VirtualHost> + ¤Î¤½¤ì¤¾¤ì¤Î¥»¥¯¥·¥ç¥ó¤ÎÃ椫¤é + ServerName ¤« + ServerAlias + ¤ËÍ׵ᤵ¤ì¤¿¥Û¥¹¥È̾¤¬¤¢¤ë¤«Ãµ¤·¤Þ¤¹¡£ + ¸«¤Ä¤«¤ì¤Ð¤½¤Î¥µ¡¼¥ÐÍѤÎÀßÄê¤ò»È¤¤¤Þ¤¹¡£¥Þ¥Ã¥Á¤¹¤ë¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È + ¤¬¸«¤Ä¤«¤é¤Ê¤±¤ì¤Ð¡¢¥Þ¥Ã¥Á¤·¤¿ IP ¥¢¥É¥ì¥¹¤Î + ¥ê¥¹¥È¤ÎºÇ½é¤Ë¤¢¤ë¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È ¤¬»È¤ï¤ì¤Þ¤¹¡£

    + +

    ·ë²Ì¤È¤·¤Æ¡¢¥ê¥¹¥È¤ÎºÇ½é¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬ ¥Ç¥Õ¥©¥ë¥È ¤Î + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¤Ê¤ê¤Þ¤¹¡£IP ¥¢¥É¥ì¥¹¤¬ NameVirtualHost + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¥Þ¥Ã¥Á¤·¤¿¾ì¹ç¤Ï¡¢¥á¥¤¥ó¤Î¥µ¡¼¥Ð ¤Î + DocumentRoot + ¤Ï·è¤·¤Æ»È¤ï¤ì¤Þ¤»¤ó + ¤É¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Ë¤â¥Þ¥Ã¥Á¤·¤Ê¤¤¥ê¥¯¥¨¥¹¥È¤ËÂФ·¤Æ¡¢ + ÆÃÊ̤ÊÀßÄê¤ò¤·¤¿¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢ÀßÄê¥Õ¥¡¥¤¥ëÃæ¤ÎºÇ½é¤Î + <VirtualHost> ¥³¥ó¥Æ¥Ê¤Ë¤½¤ì¤òµ­½Ò¤·¤Æ¤¯¤À¤µ¤¤¡£

    + +
    top
    +
    +

    ¸Å¤¤¥Ö¥é¥¦¥¶¤È¤Î¸ß´¹À­

    + +

    °ÊÁ°½Ò¤Ù¤¿¤è¤¦¤Ë¡¢Ì¾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤¬Àµ¤·¤¯Æ°ºî¤¹¤ë + ¤¿¤á¤ËɬÍפʾðÊó¤òÁ÷¤Ã¤Æ¤³¤Ê¤¤¥¯¥é¥¤¥¢¥ó¥È¤¬°ÍÁ³¤È¤·¤Æ¸ºß¤·¤Æ¤¤¤Þ¤¹¡£ + ¤½¤Î¤è¤¦¤Ê¥¯¥é¥¤¥¢¥ó¥È¤ËÂФ·¤Æ¤Ï¡¢³ºÅö¤¹¤ë IP ¥¢¥É¥ì¥¹¤Ë¤Ä¤¤¤Æ¡¢ + °ìÈֺǽé¤ËÀßÄꤵ¤ì¤Æ¤¤¤ë¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È + (¥×¥é¥¤¥Þ¥ê¤Î̾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È) + ¤«¤é¥Ú¡¼¥¸¤¬Á÷¤êÊÖ¤µ¤ì¤Þ¤¹¡£

    + +

    ¤É¤Î¤°¤é¤¤¸Å¤¤¤Î ?

    +

    ¡Ö¸Å¤¤¡×¤Èɽ¸½¤·¤Æ¤¤¤ë¾ì¹ç¡¢ËÜÅö¤Ë¸Å¤¤¤³¤È¤ò°ÕÌ£¤·¤Æ»È¤Ã¤Æ¤¤¤Þ¤¹¡£ + ÉÔ¹¬¤Ë¤·¤Æº£¸½ºß¤Ç¤â¤³¤Î¤è¤¦¤Ê¸Å¤¤¥Ö¥é¥¦¥¶¤ËÁø¶ø¤¹¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£ + ¸½ºß¤Î¥Ö¥é¥¦¥¶¤ÏÁ´¤Æ¡¢Ì¾Á°¥Ù¡¼¥¹¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤ËɬÍ×¤Ê + Host ¥Ø¥Ã¥À¤òÁ÷¤ê¤Þ¤¹¡£

    +
    + +

    ServerPath + ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÂн褬²Äǽ¤Ç¤¹¡£¤Á¤ç¤Ã¤ÈÉԳʹ¥¤Ç¤¹¤±¤ì¤É¤â¡£

    + +

    ÀßÄêÎã

    + +

    + NameVirtualHost 111.22.33.44
    +
    + <VirtualHost 111.22.33.44>
    + + ServerName www.domain.tld
    + ServerPath /domain
    + DocumentRoot /web/domain
    +     + </VirtualHost>
    +

    + +

    ¤³¤ÎÎã¤Ë¤Ï¤É¤¦¤¤¤¦°ÕÌ£¤¬¤¢¤ë¤Ç¤·¤ç¤¦¤«? ¤³¤ì¤Ï + "/domain" ¤Ç»Ï¤Þ¤ë URI ¤Ø¤Î¥ê¥¯¥¨¥¹¥È¤Ï¤¹¤Ù¤Æ¡¢ + ¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È www.domain.tld ¤Ç½èÍý¤µ¤ì¤ë¡¢ + ¤È¤¤¤¦°ÕÌ£¤Ç¤¹¡£¤Ä¤Þ¤ê¡¢¤¹¤Ù¤Æ¤Î¥¯¥é¥¤¥¢¥ó¥È¤Ç + http://www.domain.tld/domain/ ¤Ç¥¢¥¯¥»¥¹¤Ç¤­¤ë¥Ú¡¼¥¸¤¬¡¢ + Host: ¥Ø¥Ã¥À¤òÁ÷¤Ã¤Æ¤¯¤ë¥¯¥é¥¤¥¢¥ó¥È¤Ç¤¢¤ì¤Ð + http://www.domain.tld/ ¤È¤·¤Æ¤â¥¢¥¯¥»¥¹¤Ç¤­¤ë¡¢ + ¤È¤¤¤¦°ÕÌ£¤Ç¤¹¡£

    + +

    ¤³¤ì¤¬Æ°ºî¤¹¤ë¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢ + ¥×¥é¥¤¥Þ¥ê¤Î¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¥Ú¡¼¥¸¤Ë + http://www.domain.tld/domain/ ¤Ø¤Î¥ê¥ó¥¯¤òÀßÃÖ¤·¤Þ¤¹¡£ + ¤½¤·¤Æ¡¢¥Ð¡¼¥Á¥ã¥ë¥Û¥¹¥È¤Î¥Ú¡¼¥¸¤Ç¤Ï¡¢½ã¿è¤ÊÁêÂÐ¥ê¥ó¥¯ (Îã: + "file.html" ¤ä "../icons/image.gif")¡¢ + ¤¢¤ë¤¤¤Ï /domain/ ¤Ç»Ï¤Þ¤ë¥ê¥ó¥¯ (Îã: + "http://www.domain.tld/domain/misc/file.html" ¤ä + "/domain/misc/file.html") ¤À¤±¤òÀßÃÖ¤·¤Þ¤¹¡£

    + +

    ¤³¤ì¤Ë¤Ï¡¢´öʬ¤«¤Îµ¬Î§¤¬É¬ÍפȤʤê¤Þ¤¹¤¬¡¢ + ¤³¤Î¤è¤¦¤Ê¥¬¥¤¥É¥é¥¤¥ó¤òÃé¼Â¤Ë¼é¤ë¤³¤È¤Ë¤è¤ê¡¢¤¿¤¤¤Æ¤¤¤Î¾ì¹ç¡¢ + ¤¹¤Ù¤Æ¤Î¥Ö¥é¥¦¥¶¤Ç ¡½ ¿·¤·¤¤¥Ö¥é¥¦¥¶¤Ç¤â¸Å¤¤¤â¤Î¤Ç¤â ¡½ + ºîÀ®¤·¤¿¥Ú¡¼¥¸¤¬¸«¤¨¤ë¤È¤¤¤¦¤³¤È¤òÊݾڤ·¤Þ¤¹¡£

    + +
    +
    +

    Available Languages:  de  | + en  | + fr  | + ja  | + ko 

    +
    + \ No newline at end of file diff --git a/docs/manual/vhosts/name-based.html.ko.euc-kr b/docs/manual/vhosts/name-based.html.ko.euc-kr new file mode 100644 index 00000000..9895c5a6 --- /dev/null +++ b/docs/manual/vhosts/name-based.html.ko.euc-kr @@ -0,0 +1,236 @@ + + + +À̸§±â¹Ý °¡»óÈ£½ºÆ® Áö¿ø - Apache HTTP Server + + + + +
    +

    ¸ðµâ | Áö½Ã¾îµé | FAQ | ¿ë¾î | »çÀÌÆ®¸Ê

    +

    Apache HTTP Server Version 2.2

    +
    +
    <-
    +

    À̸§±â¹Ý °¡»óÈ£½ºÆ® Áö¿ø

    +
    +

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

    +
    + +

    ÀÌ ¹®¼­´Â À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÏ´Â °æ¿ì¿Í ¹æ¹ýÀ» + ¼³¸íÇÑ´Ù.

    +
    + +
    top
    +
    +

    À̸§±â¹Ý ´ë IP±â¹Ý °¡»óÈ£½ºÆ®

    + +

    IP±â¹Ý °¡»óÈ£½ºÆ®´Â ¿¬°áÇÑ IP ÁÖ¼Ò¸¦ °¡Áö°í ¼­ºñ½ºÇÒ + °¡»óÈ£½ºÆ®¸¦ °áÁ¤ÇÑ´Ù. ±×·¡¼­ °¢ È£½ºÆ®´Â ¼­·Î ´Ù¸¥ IP ÁÖ¼Ò¸¦ + °¡Á®¾ß ÇÑ´Ù. À̸§±â¹Ý °¡»óÈ£½ºÆ®ÀÇ °æ¿ì ¼­¹ö´Â Ŭ¶óÀ̾ðÆ®°¡ + HTTP Çì´õ·Î È£½ºÆ®¸íÀ» ¾Ë·ÁÁÖ±æ ¹Ù¶õ´Ù. ÀÌ·± ¹æ¹ýÀ¸·Î ÇÑ + IP ÁÖ¼Ò·Î ¿©·¯ ´Ù¸¥ È£½ºÆ®¸¦ ¼­ºñ½ºÇÒ ¼ö ÀÖ´Ù.

    + +

    À̸§±â¹Ý °¡»óÈ£½ºÆ®´Â DNS ¼­¹ö°¡ °¢ È£½ºÆ®¸íÀÌ ¿Ã¹Ù¸¥ + IP ÁÖ¼Ò·Î ´ëÀÀÇϵµ·Ï °¡»óÈ£½ºÆ®¸¦ ¼³Á¤ÇÏ°í, ´Ù¸¥ È£½ºÆ®¸íÀ» ±¸º°ÇÒ + ¼ö ÀÖµµ·Ï ¾ÆÆÄÄ¡ À¥¼­¹ö¸¦ ¼³Á¤Çϱ⸸ ÇϸéµÇ¹Ç·Î ´õ °£´ÜÇÏ´Ù. À̸§±â¹Ý + °¡»óÈ£½ºÆ®´Â ¶Ç ¿©·¯ IP ÁÖ¼Ò°¡ ÇÊ¿ä¾ø´Ù. ±×·¯¹Ç·Î Ưº°È÷ + IP±â¹Ý °¡»óÈ£½ºÆ®¸¦ ¼±ÅÃÇÒ ÀÌÀ¯°¡ ¾ø´Ù¸é À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ + »ç¿ëÇØ¾ß ÇÑ´Ù. IP±â¹Ý °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇؾßÇÒ ÀÌÀ¯·Î´Â:

    + +
      +
    • À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ Áö¿øÇÏÁö¾Ê´Â ¿À·¡µÈ + Ŭ¶óÀ̾ðÆ®µéÀÌ ÀÖ´Ù. À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÏ·Á¸é + Ŭ¶óÀ̾ðÆ®°¡ HTTP Host Çì´õ¸¦ º¸³»¾ß ÇÑ´Ù. ÀÌ´Â + HTTP/1.1¿¡¼­´Â ÇʼöÀÌ°í, ÃÖ±Ù ¸ðµç HTTP/1.0 ºê¶ó¿ìÀúµéµµ + È®ÀåÀ¸·Î Áö¿øÇÑ´Ù. ¸¸¾à À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇϸ鼭 + ¿À·¡µÈ Ŭ¶óÀ̾ðÆ®¸¦ Áö¿øÇØ¾ß ÇÑ´Ù¸é ÀÌ ¹®¼­ ³¡¿¡ ÀÖ´Â + ¹æ¹ýÀ» »ìÆìºÁ¶ó.
      • + +
    • SSL ÇÁ·ÎÅäÄÝÀÇ ¼º°Ý»ó SSL º¸¾È¼­¹ö¿¡¼­ À̸§±â¹Ý + °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÒ ¼ö ¾ø´Ù.
      • + +
    • ¾î¶² ¿î¿µÃ¼Á¦³ª ³×Æ®¿÷ ÀåÄ¡´Â ´Ù¸¥ IP ÁÖ¼Ò¸¦ »ç¿ëÇÏÁö + ¾ÊÀ¸¸é È£½ºÆ®¸¦ ±¸º°ÇÏÁö ¸øÇÏ´Â ³×Æ®¿÷ »ç¿ë·®(bandwidth) + °ü¸®±â¼úÀ» »ç¿ëÇÑ´Ù.
      • +
    + +
    top
    +
    +

    À̸§±â¹Ý °¡»óÈ£½ºÆ® »ç¿ëÇϱâ

    + +
    °ü·ÃµÈ ¸ðµâ°ü·ÃµÈ Áö½Ã¾î
    + +

    À̸§±â¹Ý °¡»óÈ£½ºÆ®¸¦ »ç¿ëÇÏ·Á¸é ¼­¹ö´Â ¿¬°áÀ» ¹ÞÀ» + IP ÁÖ¼Ò¸¦ (¾Æ¸¶ Æ÷Æ®µµ) Á¤ÇØ¾ß ÇÑ´Ù. ÀÌ´Â NameVirtualHost Áö½Ã¾î·Î °¡´ÉÇÏ´Ù. + ÀϹÝÀûÀ¸·Î ¼­¹öÀÇ ¸ðµç IP ÁÖ¼Ò¸¦ »ç¿ëÇÑ´Ù¸é + NameVirtualHostÀÇ + ¾Æ±Ô¸ÕÆ®·Î *¸¦ »ç¿ëÇÑ´Ù. ¿©·¯ Æ÷Æ®¸¦ »ç¿ëÇÒ + (¿¹¸¦ µé¾î, SSLÀ» »ç¿ëÇÒ) °èȹÀ̶ó¸é *:80°ú + °°ÀÌ ¾Æ±Ô¸ÕÆ®¿¡ Æ÷Æ®¸¦ Ãß°¡ÇØ¾ß ÇÑ´Ù. NameVirtualHost Áö½Ã¾î¿¡ IP ÁÖ¼Ò¸¦ + Àû¾îÁÖ¾ú´Ù°í ¼­¹ö°¡ ÀÚµ¿À¸·Î ±× IP ÁÖ¼Ò¸¦ ±â´Ù¸®Áö ¾ÊÀ½À» + ÁÖÀÇÇ϶ó. ÀÚ¼¼ÇÑ ³»¿ëÀº ¾ÆÆÄÄ¡°¡ + »ç¿ëÇÒ ÁÖ¼Ò¿Í Æ÷Æ® ¼³Á¤Çϱ⸦ Âü°íÇ϶ó. ¶Ç, ¿©±â¼­ + ÁöÁ¤ÇÑ IP ÁÖ¼Ò´Â ¼­¹öÀÇ ³×Æ®¿÷ ÀÎÅÍÆäÀ̽ºÀ̾î¾ß ÇÑ´Ù.

    + +

    ´ÙÀ½ ´Ü°è´Â ¼­ºñ½ºÇÏ·Á´Â È£½ºÆ®º°·Î <VirtualHost> ºí·ÏÀ» + ¸¸µå´Â ÀÏÀÌ´Ù. <VirtualHost>> Áö½Ã¾îÀÇ ¾Æ±Ô¸ÕÆ®´Â + NameVirtualHost Áö½Ã¾îÀÇ + ¾Æ±Ô¸ÕÆ®(¿¹¸¦ µé¾î, IP ÁÖ¼Ò³ª ¸ðµç ÁÖ¼Ò¸¦ ¶æÇÏ´Â *)¿Í + °°¾Æ¾ß ÇÑ´Ù. <VirtualHost>> ºí·Ï ¾È¿¡´Â + ÃÖ¼ÒÇÑ ¼­ºñ½ºÇÒ È£½ºÆ®¸¦ ÁöÁ¤ÇÏ´Â ServerName Áö½Ã¾î¿Í È£½ºÆ®ÀÇ + ³»¿ëÀÌ ÆÄÀϽýºÅÛ ¾îµð¿¡ ÀÖ´ÂÁö¸¦ ÁöÁ¤ÇÏ´Â DocumentRoot Áö½Ã¾î°¡ ÇÊ¿äÇÏ´Ù.

    + +

    ÁÖ È£½ºÆ®°¡ ¾ø¾îÁø´Ù

    +

    ±âÁ¸¿¡ »ç¿ëÇÏ´ø À¥¼­¹ö¿¡ °¡»óÈ£½ºÆ®¸¦ Ãß°¡ÇÑ´Ù¸é + ±âÁ¸¿¡ »ç¿ëÇÏ´ø È£½ºÆ®¿¡ ´ëÇÑ <VirtualHost> ºí·Ïµµ Ãß°¡ÇØ¾ß + ÇÑ´Ù. ÀÌ ºí·Ï¿¡ Æ÷ÇÔÇÏ´Â ServerName°ú DocumentRoot´Â Àüü ServerName°ú DocumentRoot¿Í °°¾Æ¾ß ÇÑ´Ù. + ¼³Á¤ÆÄÀÏ¿¡¼­ ÀÌ °¡»óÈ£½ºÆ®¸¦ °¡Àå ¸ÕÀú ÀûÀ¸¸é ±âº» È£½ºÆ®°¡ + µÈ´Ù.

    +
    + +

    ¿¹¸¦ µé¾î www.domain.tld µµ¸ÞÀÎÀ» ¼­ºñ½ºÇÏ°í + ÀÖ¾ú´Âµ¥ °°Àº IP ÁÖ¼Ò¿¡ + www.otherdomain.tld¶õ °¡»óÈ£½ºÆ®¸¦ Ãß°¡ÇÏ°í + ½Í´Ù°í °¡Á¤ÇÏÀÚ. httpd.conf¿¡ ´ÙÀ½°ú °°ÀÌ + Ãß°¡ÇÏ¸é µÈ´Ù:

    + +

    + NameVirtualHost *:80
    +
    + <VirtualHost *:80>
    + + ServerName www.domain.tld
    + ServerAlias domain.tld *.domain.tld
    + DocumentRoot /www/domain
    +     + </VirtualHost>
    +
    + <VirtualHost *:80>
    + ServerName www.otherdomain.tld
    + DocumentRoot /www/otherdomain
    +     + </VirtualHost>
    +

    + +

    NameVirtualHost¿Í + <VirtualHost> + Áö½Ã¾î µÑ ¸ðµÎ * ´ë½Å Á÷Á¢ IP ÁÖ¼Ò¸¦ ÁöÁ¤ÇÒ + ¼öµµ ÀÖ´Ù. ¿¹¸¦ µé¾î, ÀÌ·±½ÄÀ¸·Î ÇÑ IP ÁÖ¼Ò¿¡ ¿©·¯ À̸§±â¹Ý + °¡»óÈ£½ºÆ®µéÀ» µ¹¸®°í, ´Ù¸¥ ÁÖ¼Ò¿¡ IP±â¹Ý ȤÀº À̸§±â¹Ý + °¡»óÈ£½ºÆ®µéÀ» µ¹¸± ¼ö ÀÖ´Ù.

    + +

    ¾î¶² ¼­¹ö´Â ¿©·¯ À̸§À¸·Î Á¢¼ÓÇÒ ¼ö ÀÖ±æ ¹Ù¶õ´Ù. ÀÌ´Â + <VirtualHost> + ¼½¼Ç ¾È¿¡ ServerAlias + Áö½Ã¾î¸¦ »ç¿ëÇÏ¿© °¡´ÉÇÏ´Ù. ¿¹¸¦ µé¾î À§ÀÇ Ã¹¹ø° <VirtualHost> ºí·Ï¿¡¼­ + ServerAlias Áö½Ã¾î¸¦ + »ç¿ëÇÏ¸é ¿­°ÅÇÑ À̸§À¸·Î °°Àº À¥»çÀÌÆ®¸¦ º¼ ¼ö ÀÖ´Ù:

    + +

    + ServerAlias domain.tld *.domain.tld +

    + +

    domain.tld µµ¸ÞÀο¡ ÀÖ´Â ¸ðµç È£½ºÆ®¿¡ ´ëÇÑ + ¿äûÀ» www.domain.tld °¡»óÈ£½ºÆ®°¡ ¼­ºñ½ºÇÑ´Ù. + À̸§À» ÁÙ¶§ ¿ÍÀϵåÄ«µå ¹®ÀÚ *¿Í ?¸¦ + »ç¿ëÇÒ ¼ö ÀÖ´Ù. ¹°·Ð ServerNameÀ̳ª ServerAlias¿¡ + À̸§À» Àû¾îÁÖ¾ú´Ù°í ³¡ÀÌ ¾Æ´Ï´Ù. ¸ÕÀú ÀÌ À̸§µéÀÌ ¼­¹öÀÇ + IP ÁÖ¼Ò·Î ´ëÀÀÇϵµ·Ï DNS ¼­¹ö¸¦ ¾Ë¸Â°Ô ¼³Á¤ÇØ¾ß ÇÑ´Ù.

    + +

    ¸¶Áö¸·À¸·Î <<VirtualHost>> ¾È¿¡ ´Ù¸¥ + Áö½Ã¾îµéÀ» »ç¿ëÇÏ¿© °¡»óÈ£½ºÆ®¸¦ ÀÚ¼¼È÷ ¼³Á¤ÇÒ ¼ö ÀÖ´Ù. + ´ëºÎºÐÀÇ Áö½Ã¾î¸¦ »ç¿ëÇÒ ¼ö ÀÖÀ¸¸ç, °ü·ÃµÈ °¡»óÈ£½ºÆ®ÀÇ ¼³Á¤¸¸À» + º¯°æÇÑ´Ù. ¾î¶² Áö½Ã¾î°¡ »ç¿ë°¡´ÉÇÑÁö ¾Ë·Á¸é Áö½Ã¾îÀÇ »ç¿ëÀå¼Ò¸¦ + È®ÀÎÇ϶ó. (<<VirtualHost>> ¾ÈÀÌ ¾Æ´Ñ) + ÁÖ¼­¹ö¼³Á¤¿¡¼­ ÁöÁ¤ÇÑ ¼³Á¤ Áö½Ã¾î´Â °¡»óÈ£½ºÆ®¿¡ + °°Àº ¼³Á¤ Áö½Ã¾î°¡ ¾ø´Â °æ¿ì¿¡¸¸ »ç¿ëµÈ´Ù.

    + +

    ¿äûÀ» ¹ÞÀ¸¸é ¼­¹ö´Â ¸ÕÀú NameVirtualHost¿¡¼­ ÁöÁ¤ÇÑ IP + ÁÖ¼ÒÀÎÁö °Ë»çÇÑ´Ù. ±×·¸´Ù¸é ±× IP ÁÖ¼Ò¸¦ °¡Áø <VirtualHost> + ¼½¼Çµé¿¡¼­ ¿äûÇÑ È£½ºÆ®¸í°ú ÀÏÄ¡ÇÏ´Â ServerNameÀ̳ª + ServerAlias¸¦ ã´Â´Ù. ãÀ¸¸é ±× ¼³Á¤À» »ç¿ëÇÑ´Ù. + ÀûÀýÇÑ °¡»óÈ£½ºÆ®¸¦ ãÁö¸øÇϸé, IP ÁÖ¼Ò¿¡ ÇØ´çÇÏ´Â + °¡»óÈ£½ºÆ®µéÁß Ã¹¹ø° °ÍÀ» »ç¿ëÇÑ´Ù.

    + +

    °á°úÀûÀ¸·Î óÀ½¿¡ ³ª¿Â °¡»óÈ£½ºÆ®°¡ ±âº» + °¡»óÈ£½ºÆ®°¡ µÈ´Ù. IP ÁÖ¼Ò°¡ NameVirtualHost Áö½Ã¾î¿¡ ÇØ´çÇϸé, + ÁÖ¼­¹öÀÇ DocumentRoot´Â + Àý´ë·Î »ç¿ëÇÏÁö ¾Ê´Â´Ù. ƯÁ¤ °¡»óÈ£½ºÆ®¿¡ + ÇØ´çÇÏÁö¾Ê´Â ¿äûÀ» ¼³Á¤ÇÏ·Á¸é ¼³Á¤À» <VirtualHost>¿¡ ´ã°í ¼³Á¤ÆÄÀÏ¿¡¼­ + ¸ÕÀú ³ª¿Àµµ·Ï ÇÏ¸é µÈ´Ù.

    + +
    top
    +
    +

    ¿À·¡µÈ ºê¶ó¿ìÀú¿Í ȣȯ

    + +

    ÀÌ¹Ì Àû¾úµíÀÌ À̸§±â¹Ý °¡»óÈ£½ºÆ®°¡ ¿Ã¹Ù·Î µ¿ÀÛÇϱâÀ§ÇØ + ÇÊ¿äÇÑ Á¤º¸¸¦ º¸³»Áö¾Ê´Â Ŭ¶óÀ̾ðÆ®°¡ ÀÖ´Ù. ÀÌ·± Ŭ¶óÀ̾ðÆ®´Â + Ç×»ó ¿äûÇÑ IP ÁÖ¼Ò¿¡ ´ëÇØ Ã¹¹ø°·Î ³ª¿À´Â °¡»óÈ£½ºÆ® + (ÃÖÃÊÀÇ À̸§±â¹Ý °¡»óÈ£½ºÆ®)°¡ + ¼­ºñ½ºÇÑ´Ù.

    + +

    ¾ó¸¶³ª ¿À·¡µÈ °ÍÀ» ¸»Çϴ°¡?

    +

    ¿©±â¼­ ¿À·¡µÇ¾úÀ½Àº ½ÇÁ¦·Î »ó´çÈ÷ ¿À·¡µÈ °ÍÀ» ¶æÇÑ´Ù. + ¿À´Ã³¯ ÀÌ·± ºê¶ó¿ìÀú¸¦ »ç¿ëÇÒ ÀÏÀº °ÅÀǾø´Ù. ¿äÁò + ºê¶ó¿ìÀú´Â ¸ðµÎ À̸§±â¹Ý °¡»óÈ£½ºÆ®¿¡ ÇÊ¿äÇÑ Host + Çì´õ¸¦ º¸³½´Ù.

    +
    + +

    ÀÌ ¹®Á¦´Â ¾à°£ °ÅÃßÀ彺·´Áö¸¸ ServerPath Áö½Ã¾î·Î ÇØ°áÇÒ ¼ö ÀÖ´Ù:

    + +

    ¼³Á¤ ¿¹:

    + +

    + NameVirtualHost 111.22.33.44
    +
    + <VirtualHost 111.22.33.44>
    + + ServerName www.domain.tld
    + ServerPath /domain
    + DocumentRoot /web/domain
    +     + </VirtualHost>
    +

    + +

    ÀÌ°Ô ¹«½¼ ¶æÀΰ¡? "/domain"·Î ½ÃÀÛÇÏ´Â + URI¿¡ ´ëÇÑ ¿äûÀº °¡»óÈ£½ºÆ® www.domain.tld°¡ + ¼­ºñ½ºÇÑ´Ù. Áï, Host: Çì´õ¸¦ º¸³»´Â Ŭ¶óÀ̾ðÆ®´Â + http://www.domain.tld/¸¸À¸·Îµµ Á¢±ÙÇÒ ¼ö ÀÖÁö¸¸, + http://www.domain.tld/domain/À¸·Î´Â ¸ðµç + Ŭ¶óÀ̾ðÆ®°¡ ÆäÀÌÁö¿¡ Á¢±ÙÇÒ ¼ö ÀÖ´Ù.

    + +

    À̸¦ À§ÇØ ÃÖÃÊÀÇ °¡»óÈ£½ºÆ®¿¡ ÀÖ´Â ÆäÀÌÁö¿¡ + http://www.domain.tld/domain/À¸·Î °¡´Â ¸µÅ©¸¦ + ³Ö´Â´Ù. ±×¸®°í °¡»óÈ£½ºÆ® ÆäÀÌÁö¿¡¼­´Â »ó´ë¸µÅ© (¿¹¸¦ µé¾î, + "file.html" À̳ª "../icons/image.gif") + ȤÀº ("http://www.domain.tld/domain/misc/file.html"À̳ª + "/domain/misc/file.html"°ú °°ÀÌ) ¾Õ¿¡ + /domain/ÀÌ ºÙÀº ¸µÅ©¸¸À» »ç¿ëÇÑ´Ù.

    + +

    Á¶±Ý ±ÔÄ¢ÀÌ ÇÊ¿äÇÏÁö¸¸ ÀÌ ±ÔÄ¢À» µû¸£¸é ´ëºÎºÐÀÇ °æ¿ì + ¿äÁò °ÍÀ̳ª ¿À·¡µÈ °ÍÀ̳ª °ü°è¾øÀÌ ¸ðµç ºê¶ó¿ìÀú·Î ÆäÀÌÁö¸¦ + º¼ ¼ö ÀÖ´Ù.

    + +
    +
    +

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

    +
    + \ No newline at end of file -- cgit v1.2.3
    + + + + + + + + + + + + <- + +