This chapter contains a description of various issues related to installation, setup, and usage of the NetX Duo HTTP component.
NetX Duo can be obtained from our public source code repository at https://github.com/eclipse-threadx/netxduo/.
-
nxd_http_client.h Header file for HTTP Client for NetX Duo
-
nxd_http_server.h Header file for HTTP Server for NetX Duo
-
nxd_http_client.c C Source file for HTTP Client for NetX Duo
-
nxd_http_server.c C Source file for HTTP Server for NetX Duo
-
nx_md5.c MD5 digest algorithms
-
filex_stub.h Stub file if FileX is not present
-
nxd_http.pdf Description of HTTP for NetX Duo
-
demo_netxduo_http.c NetX Duo HTTP demonstration
In order to use HTTP for NetX Duo, the entire distribution mentioned previously should be copied to the same directory where NetX Duo is installed. For example, if NetX Duo is installed in the directory "\threadx\arm7\green" then the nxd_http_client.h and nxd_http_client.c for NetX Duo HTTP Client applications, and nxd_http_server.h and nxd_http_server.c for NetX Duo HTTP Server applications. nx_md5.c should be copied into this directory. For the demo 'ram driver' application NetX Duo HTTP Client and Server files should be copied into the same directory.
Using HTTP for NetX Duo is easy. Basically, the application code must include nxd_http_client.h and/or nxd_http_server.h after it includes tx_api.h, fx_api.h, and nx_api.h, in order to use ThreadX, FileX, and NetX Duo, respectively. Once the HTTP header files are included, the application code is then able to make the HTTP function calls specified later in this guide. The application must also include nxd_http_client.c, nxd_http_server.c, and md5.c in the build process. These files must be compiled in the same manner as other application files and its object form must be linked along with the files of the application. This is all that is required to use NetX Duo HTTP.
|
Note
|
If NX_HTTP_DIGEST_ENABLE is not specified in the build process, the md5.c file does not need to be added to the application. Similarly, if no HTTP Client capabilities are required, the nxd_http_client.c file may be omitted. |
|
Note
|
Since HTTP utilizes NetX Duo TCP services, TCP must be enabled with the nx_tcp_enable call prior to using HTTP. |
An example of how easy it is to use NetX Duo HTTP is described below. This example works with the ‘duo’ services available in NetX Duo HTTP placement of #define USE_DUO on line 23. Otherwise it uses the legacy NetX HTTP equivalent (limited to IPv4 only). Developers are encouraged to migrate existing applications to using the NetX Duo HTTP services.
To specify IPv6 communication, the application defines IPTYPE to IPv6 in line 24.
In this example, the HTTP include files nxd_http_client.h and nxd_http_server.h are brought in at line 8 and 9. Next, the helper HTTP Server thread, packet pool and IP instance are created in lines 89 — 112. The HTTP Server IP instance must be TCP enabled, as seen in line 137. The HTTP Server is then itself is created in at line 159.
Next the HTTP Client is created. First the client thread is created in line 172 followed by packet pool and IP instance, similar to the HTTP Server, in lines 186 — 200. Again the HTTP Client IP instance must be TCP enabled (line 217).
The HTTP Server thread runs and its first task is validate its IP address with NetX Duo which it does in lines 423 - 450. Now the HTTP Server is ready to take requests.
The HTTP Client thread’s first task is create and format the FileX media (lines 236 and 260. After the media is initialized, the HTTP Client is created in line 271. This must be done before the HTTP server can service HTTP requests. It must then validate its IP address with NetX Duo which it does in lines 282 — 316. The HTTP Client then creates and sends the file client_test.html to the HTTP Server, waits briefly, then attempts to read the file back from the HTTP Server.
|
Note
|
The HTTP Client API uses a different service if IPv6 is not enabled (nx_http_client_put_start in line 343 and nx_http_client_get_start in line 399). This enables NetX Duo to support existing NetX HTTP Client applications. |
|
Note
|
The HTTP Client API calls are made with relatively short timeouts. It may be necessary to extend those timeouts if an HTTP client is communicating with a busy server or remote server on a slower processor. |
1 /* This is a small demo of the NetX Duo HTTP Client Server API running on a
2 high-performance NetX Duo TCP/IP stack. This demo is applicable for
3 either IPv4 or IPv6 enabled applications. */
4
5 #include "tx_api.h"
6 #include "fx_api.h"
7 #include "nx_api.h"
8 #include "nxd_http_client.h"
9 #include "nxd_http_server.h"
10
11 #define DEMO_STACK_SIZE 2048
12
13 /* Set up FileX and file memory resources. */
14 CHAR *ram_disk_memory;
15 FX_MEDIA ram_disk;
16 unsigned char media_memory[512];
17
18 /* Define device drivers. */
19 extern void _fx_ram_driver(FX_MEDIA *media_ptr);
20 VOID _nx_ram_network_driver(NX_IP_DRIVER *driver_req_ptr);
22
23 #define USE_DUO /* Use the duo service (not legacy netx) */
24 #define IPTYPE 6 /* Send packets over IPv6 */
25
26 /* Set up the HTTP client. */
27 TX_THREAD client_thread;
28 NX_PACKET_POOL client_pool;
29 NX_HTTP_CLIENT my_client;
30 NX_IP client_ip;
31 #define CLIENT_PACKET_SIZE (NX_HTTP_SERVER_MIN_PACKET_SIZE * 2)
32 void thread_client_entry(ULONG thread_input);
33
34 #define HTTP_SERVER_ADDRESS IP_ADDRESS(1,2,3,4)
35 #define HTTP_CLIENT_ADDRESS IP_ADDRESS(1,2,3,5)
36
37 /* Set up the HTTP server */
38
39 NX_HTTP_SERVER my_server;
40 NX_PACKET_POOL server_pool;
41 TX_THREAD server_thread;
42 NX_IP server_ip;
43 #define SERVER_PACKET_SIZE (NX_HTTP_SERVER_MIN_PACKET_SIZE * 2)
44
45 void thread_server_entry(ULONG thread_input);
46 #ifdef FEATURE_NX_IPV6
47 NXD_ADDRESS server_ip_address;
48 #endif
49
50
51 /* Define the application's authentication check. This is called by
52 the HTTP server whenever a new request is received. */
53 UINT authentication_check(NX_HTTP_SERVER *server_ptr, UINT request_type,
54 CHAR *resource, CHAR **name, CHAR **password, CHAR **realm)
55 {
56
57 /* Just use a simple name, password, and realm for all
58 requests and resources. */
59 *name = "name";
60 *password = "password";
61 *realm = "NetX Duo HTTP demo";
62
63 /* Request basic authentication. */
64 return(NX_HTTP_BASIC_AUTHENTICATE);
65 }
66
67 /* Define main entry point. */
68
69 int main()
70 {
71
72 /* Enter the ThreadX kernel. */
73 tx_kernel_enter();
74 }
75
76
77 /* Define what the initial system looks like. */
78 void tx_application_define(void *first_unused_memory)
79 {
80
81 CHAR *pointer;
82 UINT status;
83
84
85 /* Setup the working pointer. */
86 pointer = (CHAR *) first_unused_memory;
87
88 /* Create a helper thread for the server. */
89 tx_thread_create(&server_thread, "HTTP Server thread", thread_server_entry, 0,
90 pointer, DEMO_STACK_SIZE,
91 1, 1, TX_NO_TIME_SLICE, TX_AUTO_START);
92
93 pointer = pointer + DEMO_STACK_SIZE;
94
95 /* Initialize the NetX system. */
96 nx_system_initialize();
97
98 /* Create the server packet pool. */
99 status = nx_packet_pool_create(&server_pool, "HTTP Server Packet Pool",
SERVER_PACKET_SIZE, pointer, SERVER_PACKET_SIZE*4);
100
101
102 pointer = pointer + SERVER_PACKET_SIZE * 4;
103
104 /* Check for pool creation error. */
105 if (status)
106 {
107
108 return;
109 }
110
111 /* Create an IP instance. */
112 status = nx_ip_create(&server_ip, "HTTP Server IP", HTTP_SERVER_ADDRESS,
113 0xFFFFFF00UL, &server_pool, _nx_ram_network_driver,
114 pointer, 4096, 1);
115
116 pointer = pointer + 4096;
117
118 /* Check for IP create errors. */
119 if (status)
120 {
121 printf("nx_ip_create failed. Status 0x%x\n", status);
122 return;
123 }
124
125 /* Enable ARP and supply ARP cache memory for the server IP instance. */
126 status = nx_arp_enable(&server_ip, (void *) pointer, 1024);
127
128 /* Check for ARP enable errors. */
129 if (status)
130 {
131 return;
132 }
133
134 pointer = pointer + 1024;
135
136 /* Enable TCP traffic. */
137 status = nx_tcp_enable(&server_ip);
138
139 if (status)
140 {
141 return;
142 }
143
144 #if (IP_TYPE==6)
145
146 /* Set up HTTPv6 server, but we have to wait till its address has been
147 validated before we can start the thread_server_entry thread. */
148
149 /* Set up the server's IPv6 address here. */
150 server_ip_address.nxd_ip_address.v6[3] = 0x105;
151 server_ip_address.nxd_ip_address.v6[2] = 0x0;
152 server_ip_address.nxd_ip_address.v6[1] = 0x0000f101;
153 server_ip_address.nxd_ip_address.v6[0] = 0x20010db8;
154 server_ip_address.nxd_ip_version = NX_IP_VERSION_V6;
155
156 #endif
157
158 /* Create the NetX HTTP Server. */
159 status = nx_http_server_create(&my_server, "My HTTP Server", &server_ip,
&ram_disk, pointer, 2048, &server_pool, authentication_check,
NX_NULL);
160
161 if (status)
162 {
163 return;
164 }
165
166 pointer = pointer + 2048;
167
168 /* Save the memory pointer for the RAM disk. */
169 ram_disk_memory = pointer;
170
171 /* Create the HTTP client thread. */
172 status = tx_thread_create(&client_thread, "HTTP Client", thread_client_entry, 0,
173 pointer, DEMO_STACK_SIZE,
174 2, 2, TX_NO_TIME_SLICE, TX_AUTO_START);
175
176 pointer = pointer + DEMO_STACK_SIZE;
177
178 /* Check for thread create error. */
179 if (status)
180 {
181
182 return;
183 }
184
185 /* Create the Client packet pool. */
186 status = nx_packet_pool_create(&client_pool, "HTTP Client Packet Pool",
SERVER_PACKET_SIZE, pointer, SERVER_PACKET_SIZE*4);
187
188
189 pointer = pointer + SERVER_PACKET_SIZE * 4;
190
191 /* Check for pool creation error. */
192 if (status)
193 {
194
195 return;
196 }
197
198
199 /* Create an IP instance. */
200 status = nx_ip_create(&client_ip, "HTTP Client IP", HTTP_CLIENT_ADDRESS,
201 0xFFFFFF00UL, &client_pool, _nx_ram_network_driver,
202 pointer, 2048, 1);
203
204 pointer = pointer + 2048;
205
206 /* Check for IP create errors. */
207 if (status)
208 {
209 return;
210 }
211
212 nx_arp_enable(&client_ip, (void *) pointer, 1024);
213
214 pointer = pointer + 2048;
215
216 /* Enable TCP traffic. */
217 nx_tcp_enable(&client_ip);
218
219 return;
220 }
221
222
223 VOID thread_client_entry(ULONG thread_input)
224 {
225
226 UINT status;
227 NX_PACKET *my_packet;
228 #ifdef FEATURE_NX_IPV6
229 NXD_ADDRESS client_ip_address;
230 UINT address_index;
230 #endif
231
232
233 /* Format the RAM disk - the memory for the RAM disk was setup in
234 tx_application_define above. This must be set up before the client(s) start
235 sending requests. */
236 status = fx_media_format(&ram_disk,
237 _fx_ram_driver, // Driver entry
238 ram_disk_memory, // RAM disk memory pointer
239 media_memory, // Media buffer pointer
240 sizeof(media_memory), // Media buffer size
241 "MY_RAM_DISK", // Volume Name
242 1, // Number of FATs
243 32, // Directory Entries
244 0, // Hidden sectors
245 256, // Total sectors
246 128, // Sector size
247 1, // Sectors per cluster
248 1, // Heads
249 1); // Sectors per track
250
251 /* Check the media format status. */
252 if (status != FX_SUCCESS)
253 {
254
255 /* Error, bail out. */
256 return ;
257 }
258
259 /* Open the RAM disk. */
260 status = fx_media_open(&ram_disk, "RAM DISK", _fx_ram_driver, ram_disk_memory,
media_memory, sizeof(media_memory));
261
262 /* Check the media open status. */
263 if (status != FX_SUCCESS)
264 {
265
266 /* Error, bail out. */
267 return ;
268 }
269
270 /* Create an HTTP client instance. */
271 status = nx_http_client_create(&my_client, "HTTP Client", &client_ip,
&client_pool, 600);
272
273 /* Check status. */
274 if (status != NX_SUCCESS)
275 {
276 return;
277 }
278
279 /* Attempt to upload a file to the HTTP server. */
280
281
282 #if (IPTYPE== 6)
283
284 /* Relinquish control so the HTTP server can get set up...*/
285 tx_thread_relinquish();
286
287 /* Set up the client's IPv6 address here. */
288 client_ip_address.nxd_ip_address.v6[3] = 0x101;
289 client_ip_address.nxd_ip_address.v6[2] = 0x0;
290 client_ip_address.nxd_ip_address.v6[1] = 0x0000f101;
291 client_ip_address.nxd_ip_address.v6[0] = 0x20010db1;
292 client_ip_address.nxd_ip_version = NX_IP_VERSION_V6;
293
294 /* Here's where we make the HTTP Client IPv6 enabled. */
295
296 nxd_ipv6_enable(&client_ip);
298 nxd_icmp_enable(&client_ip);
299
300 /* Wait till the IP task thread has set the device MAC address. */
302 tx_thread_sleep(100);
303
305 /* Now update NetX Duo the Client's link local and global IPv6 address. */
306 nxd_ipv6_address_set(&server_ip, 0, NX_NULL, 10, &address_index)
307 nxd_ipv6_ address_set(&server_ip, 0, &client_ip_address, 64, &address_index);
311
313 /* Then make sure NetX Duo has had time to validate the addresses. */
314
316 tx_thread_sleep(400);
317
321 /* Now upload an HTML file to the HTTPv6 server. */
322 status = nxd_http_client_put_start(&my_client, &server_ip_address,
323 "/client_test.htm", "name", "password", 103, 500);
324
325
326 /* Check status. */
327 if (status != NX_SUCCESS)
328 {
329
330 return;
331 }
332
333
334 #else
335
336 /* Relinquish control so the HTTP server can get set up...*/
337 tx_thread_relinquish();
338
339 do
340 {
341
342 /* Attempt to upload to the HTTP IPv4 server. */
343 status = nx_http_client_put_start(&my_client, HTTP_SERVER_ADDRESS,
"/client_test.htm", "name", "password", 103, 500);
344
345
346 /* Check status. */
347 if (status != NX_SUCCESS)
348 {
349 tx_thread_sleep(100);
350 }
351
352 } while (status != NX_SUCCESS);
353
354
355 #endif /* (IPTYPE== 6) */
356
357
358 /* Allocate a packet. */
359 status = nx_packet_allocate(&client_pool, &my_packet, NX_TCP_PACKET,
NX_WAIT_FOREVER);
360
361 /* Check status. */
362 if (status != NX_SUCCESS)
363 {
364 return;
365 }
366
367 /* Build a simple 103-byte HTML page. */
368 nx_packet_data_append(my_packet, "<HTML>\r\n", 8,
369 &client_pool, NX_WAIT_FOREVER);
370 nx_packet_data_append(my_packet,
371 "<HEAD><TITLE>NetX HTTP Test</TITLE></HEAD>\r\n", 44,
372 &client_pool, NX_WAIT_FOREVER);
373 nx_packet_data_append(my_packet, "<BODY>\r\n", 8,
374 &client_pool, NX_WAIT_FOREVER);
375 nx_packet_data_append(my_packet, "<H1>Another NetX Test Page!</H1>\r\n", 25,
376 &client_pool, NX_WAIT_FOREVER);
377 nx_packet_data_append(my_packet, "</BODY>\r\n", 9,
378 &client_pool, NX_WAIT_FOREVER);
379 nx_packet_data_append(my_packet, "</HTML>\r\n", 9,
380 &client_pool, NX_WAIT_FOREVER);
381
382 /* Complete the PUT by writing the total length. */
383 status = nx_http_client_put_packet(&my_client, my_packet, 50);
384
385 /* Check status. */
386 if (status != NX_SUCCESS)
387 {
388 return;
389 }
390
391 /* Now GET the test file */
392
393 #ifdef USE_DUO
394
395 status = nxd_http_client_get_start(&my_client, &server_ip_address,
396 "/client_test.htm", NX_NULL, 0, "name", "password", 50);
397 #else
398
399 status = nx_http_client_get_start(&my_client, HTTP_SERVER_ADDRESS,
"/client_test.htm", NX_NULL, 0, "name", "password", 50);
400
401 #endif
402
403 /* Check status. */
404 if (status != NX_SUCCESS)
405 {
406 return;
407 }
408
409 status = nx_http_client_delete(&my_client);
410
411 return;
413 }
414
416 /* Define the helper HTTP server thread. */
417 void thread_server_entry(ULONG thread_input)
418 {
419
420 UINT status;
421 #if (IPTYPE == 6)
422 UINT address_index
423 NXD_ADDRESS ip_address
424
425 /* Allow time for the IP task to initialize the driver. */
426 tx_thread_sleep(100);
427
428 ip_address.nxd_ip_version = NX_IP_VERSION_V6;
429 ip_address.nxd_ip_address.v6[0] = 0x20010000;
430 ip_address.nxd_ip_address.v6[1] = 0;
431 ip_address.nxd_ip_address.v6[2] = 0;
432 ip_address.nxd_ip_address.v6[3] = 4;
433
434 /* Here's where we make the HTTP server IPv6 enabled. */
435 nxd_ipv6_enable(&server_ip);
436 nxd_icmp_enable(&server_ip);
437
438 /* Wait till the IP task thread has set the device MAC address. */
439 while (server_ip.nx_ip_arp_physical_address_msw == 0 ||
440 server_ip.nx_ip_arp_physical_address_lsw == 0)
441 {
442 tx_thread_sleep(30);
443 }
444
445 nxd_ipv6_address_set(&server_ip, 0, NX_NULL, 10, &address_index)
446 nxd_ipv6_ address_set(&server_ip, 0, &ip_address, 64, &address_index);
447
448 /* Wait for NetX Duo to validate server address. */
449 tx_thread_sleep(400);
450
451 #endif /* (IPTYPE == 6) */
452
453 /* OK to start the HTTPv6 Server. */
454 status = nx_http_server_start(&my_server);
455
456 if (status != NX_SUCCESS)
457 {
458 return;
459 }
460
461 /* HTTP server ready to take requests! */
462
463 /* Let the IP threads execute. */
464 tx_thread_relinquish();
465
466 return;
467 }There are several configuration options for building HTTP for NetX Duo. Following is a list of all options, where each is described in detail. The default values are listed, but can be redefined prior to inclusion of nxd_http_client.h and nxd_http_server.h:
-
NX_DISABLE_ERROR_CHECKING Defined, this option removes the basic HTTP error checking. It is typically used after the application has been debugged
-
NX_HTTP_SERVER_PRIORITY The priority of the HTTP Server thread. By default, this value is defined as 16 to specify priority 16.
-
NX_HTTP_NO_FILEX Defined, this option provides a stub for FileX dependencies. The HTTP Client will function without any change if this option is defined. The HTTP Server will need to either be modified or the user will have to create a handful of FileX services in order to function properly.
-
NX_HTTP_TYPE_OF_SERVICE Type of service required for the HTTP TCP requests. By default, this value is defined as NX_IP_NORMAL to indicate normal IP packet service.
-
NX_HTTP_SERVER_THREAD_TIME_SLICE The number of timer ticks the Server thread is allowed to run before yielding to threads of the same priority. The default value is 2.
-
NX_HTTP_FRAGMENT_OPTION Fragment enable for HTTP TCP requests. By default, this value is NX_DONT_FRAGMENT to disable HTTP TCP fragmenting.
-
NX_HTTP_SERVER_WINDOW_SIZE Server socket window size. By default, this value is 2048 bytes
-
NX_HTTP_TIME_TO_LIVE Specifies the number of routers this packet can pass before it is discarded. The default value is set to 0x80.
-
NX_HTTP_SERVER_TIMEOUT Specifies the number of ThreadX ticks that internal services will suspend for. The default value is set to 10 seconds (10 * NX_IP_PERIODIC_RATE).
-
NX_HTTP_SERVER_TIMEOUT_ACCEPT Specifies the number of ThreadX ticks that internal services will suspend for in internal nx_tcp_server_socket_accept calls. The default value is set to (10 * NX_IP_PERIODIC_RATE).
-
NX_HTTP_SERVER_TIMEOUT_DISCONNECT Specifies the number of ThreadX ticks that internal services will suspend for in internal nx_tcp_socket_disconnect calls. The default value is set to 10 seconds (10 * NX_IP_PERIODIC_RATE).
-
NX_HTTP_SERVER_TIMEOUT_RECEIVE Specifies the number of ThreadX ticks that internal services will suspend for in internal nx_tcp_socket_receive calls. The default value is set to 10 seconds (10 * NX_IP_PERIODIC_RATE).
-
NX_HTTP_SERVER_TIMEOUT_SEND Specifies the number of ThreadX ticks that internal services will suspend for in internal nx_tcp_socket_send calls. The default value is set to 10 seconds (10 * NX_IP_PERIODIC_RATE).
-
NX_HTTP_MAX_HEADER_FIELD Specifies the maximum size of the HTTP header field. The default value is 256.
-
NX_HTTP_MULTIPART_ENABLE If defined, enables HTTP Server to support multipart HTTP requests.
-
NX_HTTP_SERVER_MAX_PENDING Specifies the number of connections that can be queued for the HTTP Server. The default value is set to 5.
-
NX_HTTP_MAX_RESOURCE Specifies the number of bytes allowed in a client supplied resource name. The default value is set to 40.
-
NX_HTTP_MAX_NAME Specifies the number of bytes allowed in a client supplied username. The default value is set to 20.
-
NX_HTTP_MAX_PASSWORD Specifies the number of bytes allowed in a client supplied password. The default value is set to 20.
-
NX_HTTP_SERVER_MIN_PACKET_SIZE Specifies the minimum size of the packets in the pool specified at Server creation. The minimum size is needed to ensure the complete HTTP header can be contained in one packet. The default value is set to 600.
-
NX_HTTP_CLIENT_MIN_PACKET_SIZE Specifies the minimum size of the packets in the pool specified at Client creation. The minimum size is needed to ensure the complete HTTP header can be contained in one packet. The default value is set to 300.
-
NX_HTTP_SERVER_RETRY_SECONDS Set the Server socket retransmission timeout in seconds. The default value is set to 2.
-
NX_HTTP_SERVER_ RETRY_MAX This sets the maximum number of retransmissions on Server socket. The default value is set to 10.
-
NX_HTTP_SERVER_ RETRY_SHIFT This value is used to set the next retransmission timeout. The current timeout is multiplied by the number of retransmissions thus far, shifted by the value of the socket timeout shift. The default value is set to 1 for doubling the timeout.
-
NX_HTTP_SERVER_TRANSMIT_QUEUE_DEPTH This specifies the maximum number of packets that can be enqueued on the Server socket retransmission queue. If the number of packets enqueued reaches this number, no more packets can be sent until one or more enqueued packets are released. The default value is set to 20.