📄 boa.html
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html><head> <title></title> <link rel="stylesheet" media="screen" type="text/css" href="./style.css" /> <link rel="stylesheet" media="screen" type="text/css" href="./design.css" /> <link rel="stylesheet" media="print" type="text/css" href="./print.css" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body><a href=start.html>start</a></br><div class="toc"><div class="tocheader toctoggle" id="toc__header">Table of Contents</div><div id="toc__inside"><ul class="toc"><li class="level1"><div class="li"><span class="li"><a href="#boa_-_a_single_tasking_http_server" class="toc">boa - a single tasking HTTP server</a></span></div><ul class="toc"><li class="level2"><div class="li"><span class="li"><a href="#what_is_boa" class="toc">What is boa</a></span></div></li><li class="level2"><div class="li"><span class="li"><a href="#howto_man_pages" class="toc">HowTo & man pages</a></span></div></li><li class="level2"><div class="li"><span class="li"><a href="#boa_in_uclinux" class="toc">boa in uClinux</a></span></div></li><li class="level2"><div class="li"><span class="li"><a href="#boa.conf_directives" class="toc">boa.conf Directives</a></span></div></li><li class="level2"><div class="li"><span class="li"><a href="#for_more_information" class="toc">For more information</a></span></div></li></ul></li></ul></div></div><h1><a name="boa_-_a_single_tasking_http_server" id="boa_-_a_single_tasking_http_server">boa - a single tasking HTTP server</a></h1><div class="level1"></div><!-- SECTION [1-50] --><h2><a name="what_is_boa" id="what_is_boa">What is boa</a></h2><div class="level2"><p><strong>Boa</strong> is a single-tasking <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> server. That means that unlike traditional web servers, it does not fork for each incoming connection, nor does it fork many copies of itself to handle multiple connections. It internally multiplexes all of the ongoing <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> connections, and forks only for <acronym title="Common Gateway Interface">CGI</acronym> programs (which must be separate processes), automatic directory generation, and automatic file gunzipping. Preliminary tests show Boa is capable of handling several thousand hits per second on a 300 <acronym title="Megahertz">MHz</acronym> Pentium and dozens of hits per second on a lowly 20 <acronym title="Megahertz">MHz</acronym> 386/SX. </p><p>The primary design goals of Boa are speed and security. Security, in the sense of can’t be subverted by a malicious user, not fine grained access control and encrypted communications. Boa is not intended as a feature-packed server; if you want one of those, check out WN (<a href="http://hopf.math.nwu.edu/" class="urlextern" title="http://hopf.math.nwu.edu/" rel="nofollow">http://hopf.math.nwu.edu/</a>) from John Franks. Modifications to Boa that improve its speed, security, robustness, and portability, are eagerly sought. Other features may be added if they can be achieved without hurting the primary goals. </p><p>Boa was created in 1991 by Paul Phillips (psp@well.com). It is now being maintained and enhanced by Larry Doolittle (ldoolitt@boa.org) and Jon Nelson (jnelson@boa.org). Please see the acknowledgement section for further details. </p><p>Boa is very low on hardware usage and is therefore used on many embedded systems, including routers and portable devices. </p><p>Boa does handle <acronym title="Common Gateway Interface">CGI</acronym>, but not <acronym title="Hypertext Preprocessor">PHP</acronym> or <acronym title="Active Server Pages">ASP</acronym>. </p></div><!-- SECTION [51-1545] --><h2><a name="howto_man_pages" id="howto_man_pages">HowTo & man pages</a></h2><div class="level2"><ul><li class="level1"><div class="li"> boa websites: <a href="http://www.boa.org" class="urlextern" title="http://www.boa.org" rel="nofollow">http://www.boa.org</a> </div></li><li class="level1"><div class="li"> bao at SourceForge: <a href="https://sourceforge.net/projects/boa/" class="urlextern" title="https://sourceforge.net/projects/boa/" rel="nofollow">https://sourceforge.net/projects/boa/</a></div></li><li class="level1"><div class="li"> documentation: <a href="http://www.boa.org/documentation/" class="urlextern" title="http://www.boa.org/documentation/" rel="nofollow">http://www.boa.org/documentation/</a> </div></li></ul></div><!-- SECTION [1546-1736] --><h2><a name="boa_in_uclinux" id="boa_in_uclinux">boa in uClinux</a></h2><div class="level2"><ul><li class="level1"><div class="li"> <strong>Build</strong></div></li></ul><p> In menuconfig of uClinux, select <strong>Kernel/Library/Defaults Selection</strong> → <strong>Customize Vendor/User Settings (NEW)</strong> → <strong>Network Applications</strong> → <strong>boa-new(ver 0.94.14)</strong> , then save your selection and exit menuconfig, run make command. </p><ul><li class="level1"><div class="li"> <strong>Configure</strong></div><ul><li class="level2"><div class="li"> Choose a user and server port under which Boa can run. The traditional port is 80, and user nobody (create if you need to) is often a good selection for security purposes. If you don’t have (or choose not to use) root privileges, you can not use port numbers less than 1024, nor can you switch user id. </div></li><li class="level2"><div class="li"> Choose a server root. The conf directory within the server root must hold your copy of the configuration file boa.conf </div></li><li class="level2"><div class="li"> Choose locations for log files, <acronym title="Common Gateway Interface">CGI</acronym> programs (if any), and the base of your <acronym title="Uniform Resource Locator">URL</acronym> tree.</div></li><li class="level2"><div class="li"> Set the location of the mime.types file.</div></li><li class="level2"><div class="li"> Edit conf/boa.conf according to your choices above (this file documents itself). Read through this file to see what other features you can configure</div></li></ul></li></ul><ul><li class="level1"><div class="li"> <strong>Start</strong></div><ul><li class="level2"><div class="li"> Start Boa. If you didn’t build the right SERVER_ROOT into the binary, you can specify it on the command line with the -c option (command line takes precedence). </div><ul><li class="level3"><div class="li"> Example: ./boa -c /usr/local/boa</div></li><li class="level3"><div class="li"> Example: boa -c /etc &</div></li></ul></li></ul></li></ul><ul><li class="level1"><div class="li"> <strong>Test</strong></div><ul><li class="level2"><div class="li"> At this point the server should run and serve documents. If not, check the error_log file for clues.</div></li></ul></li></ul><ul><li class="level1"><div class="li"> <strong>Files Used by Boa</strong></div><ul><li class="level2"><div class="li"> <strong>boa.conf</strong> This file is the sole configuration file for Boa. The directives in this file are defined in the DIRECTIVES section. </div></li><li class="level2"><div class="li"> <strong>mime.types</strong> The MimeTypes <filename> defines what Content-Type Boa will send in an <acronym title="Hyper Text Transfer Protocol">HTTP</acronym>/1.0 or better transaction. </div></li></ul></li></ul></div><!-- SECTION [1737-3439] --><h2><a name="boa.conf_directives" id="boa.conf_directives">boa.conf Directives</a></h2><div class="level2"><p>The Boa configuration file is parsed with a lex/yacc or flex/bison generated parser. If it reports an error, the line number will be provided; it should be easy to spot. The syntax of each of these rules is very simple, and they can occur in any order. Where possible, these directives mimic those of NCSA httpd 1.3; I (Paul Phillips) saw no reason to introduce gratuitous differences. </p><p>“<strong>ServerRoot</strong>” </p><p>The following directives are contained in the boa.conf file, and most, but not all, are required. </p>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -