The CustomHTTPApp.c file demonstrates how to build a custom HTTP application on top of the HTTP2 server. All the features of the TCPIP Demo App web pages are implemented here. Examples can be found for handling Authentication, processing web forms (using HTTP GET and POST), and providing status information through the output of dynamic variables.
Topics
|
Name |
Description |
|
Dynamic variables allow the PIC to output custom data when serving a web page. | |
|
Authentication requires a correct username/password prompt before displaying select web pages. | |
|
Web forms are easier to process when using the GET method, but the amount of data is limited. | |
|
Forms using POST are more difficult to process, but large amounts of data can be submitted. | |
|
Cookies allow storage of session information in a user's browser. | |
|
The following table lists functions in this documentation. | |
|
The following table lists variables in this documentation. |
Functions
|
|
Name |
Description |
 |
This is function HTTPPostImage. | |
|
|
Processes the configuration form on config/index.htm | |
|
|
This is function HTTPPostSNMPCommunity. | |
|
|
Parsing and collecting http data received from http form. | |
|
|
Processes the e-mail form on email/index.htm | |
|
|
Processes the LCD form on forms.htm | |
|
|
Processes the file upload form on upload.htm |
Variables
|
|
Name |
Description |
 |
This is variable Flag_ImageUpdate_running. | |
|
|
Processes the file upload form on upload_Image.htm | |
|
|
RAM allocated for DDNS parameters | |
|
|
This is variable ImageUpdate_Checksum. | |
|
|
This is variable ImageUpdate_Size. | |
|
|
Stick status message variable. See lastSuccess for details. | |
|
|
Sticky status message variable. This is used to indicated whether or not the previous POST operation was successful. The application uses these to store status messages when a POST operation redirects. This lets the application provide status messages after a redirect, when connection instance data has already been lost. |