Resource Search Order
154
SWRU455A – February 2017 – Revised March 2017
Copyright © 2017, Texas Instruments Incorporated
HTTP Server
9.6.2 POST Request Search Order
A POST request is processed according to the flow in
.
Figure 9-9. POST Request Flow
9.6.3 PUT and DELETE Request Search Order
PUT and DELETE requests are always deferred to host regardless of resource name, as shown in
Figure 9-10. PUT and DELETE Request Flow
9.7
Host HTTP Requests Processing
All HTTP requests transferred to the host are processed through the macro slcb_NetAppRequestHdlr,
which should be mapped to a user function by user.h. The function receives two parameters (and returns
void): A pointer to the request structure containing the parameters and type of the HTTP request, and a
pointer to the response structure which should be populated with the desired HTTP response.
The HTTP headers are transferred to the host as TLVs (type length value) in the metadata section of the
request. The HTTP message (if present) transferred as is, and should be parsed and processed by the
user function. The HTTP user handler is invoked from the SimpleLink driver context, and must therefore
return quickly and without calling any other SimpleLink APIs. If the response cannot be determined
immediately by the handler, it should set the response status to pending and return. The application must
then generate and send a response from its own context.