1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
12 >Server Configuration</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos Reference Manual"
20 HREF="ecos-ref.html"><LINK
22 TITLE="Embedded HTTP Server"
23 HREF="net-httpd-chapter.html"><LINK
25 TITLE="Server Organization"
26 HREF="net-httpd-organization.html"><LINK
28 TITLE="Support Functions and Macros"
29 HREF="net-httpd-html.html"></HEAD
40 SUMMARY="Header navigation table"
49 >eCos Reference Manual</TH
57 HREF="net-httpd-organization.html"
65 >Chapter 48. Embedded HTTP Server</TD
71 HREF="net-httpd-html.html"
85 NAME="NET-HTTPD-CONFIGURATION">Server Configuration</H1
87 >The HTTP server has a number of configuration options:</P
95 >CYGNUM_HTTPD_SERVER_PORT</TT
98 >This option defines the TCP port that the server will listen on. It
99 defaults to the standard HTTP port number 80. It may be changed to a
100 different number if, for example, another HTTP server is using the
110 >CYGDAT_HTTPD_SERVER_ID</TT
113 >This is the string that is reported to the client in the
114 "Server:" field of the HTTP header. </P
123 >CYGNUM_HTTPD_THREAD_COUNT</TT
126 >The HTTP server can be configured to use more than one thread to
127 service HTTP requests. If you expect to serve complex pages with many
128 images or other components that are fetched separately, or if any
129 pages may take a long time to send, then it may be useful to increase
130 the number of server threads. For most uses, however, the connection
131 queuing in the TCP/IP stack and the speed with which each page is
132 generated, means that a single thread is usually adequate.</P
141 >CYGNUM_HTTPD_THREAD_PRIORITY</TT
144 >The HTTP server threads can be run at any priority. The exact priority
145 depends on the importance of the server relative to the rest of the
146 system. The default is to put them in the middle of the priority range
147 to provide reasonable response without impacting genuine high priority
157 >CYGNUM_HTTPD_THREAD_STACK_SIZE</TT
160 >This is the amount of stack to be allocated for each of the HTTPD
161 threads. The actual stack size allocated will be this value plus the
164 >CYGNUM_HAL_STACK_SIZE_MINIMUM</TT
168 >CYGNUM_HTTPD_SERVER_BUFFER_SIZE</TT
178 >CYGNUM_HTTPD_SERVER_BUFFER_SIZE</TT
181 >This defines the size of the buffer used to receive the first line of
182 each HTTP request. If you expect to use particularly long URLs or have
183 very complex forms, this should be increased.</P
192 >CYGNUM_HTTPD_SERVER_DELAY</TT
195 >This defines the number of system clock ticks that the HTTP server
196 will wait before initializing itself and spawning any extra server
197 threads. This is to give the application a chance to initialize
198 properly without any interference from the HTTPD.</P
206 SUMMARY="Footer navigation table"
217 HREF="net-httpd-organization.html"
235 HREF="net-httpd-html.html"
245 >Server Organization</TD
251 HREF="net-httpd-chapter.html"
259 >Support Functions and Macros</TD