Sack Library Documentation
|
Simple HTTP Packet processing state. Its only intelligence is that there are fields of http header, and that one of those fields might be content-length; so it can seperate individual fields name-value pairs and the packet content.
|
Name |
Description |
|
Add another bit of data to the block. After adding data, ProcessHttp should be called to see if the data has completed a packet. | |
| ||
|
This is function sack::containers::text::http::CreateHttpServerEx. | |
|
Creates an empty http state, the next operation should be AddHttpData. | |
|
Destroys a http state, releasing all resources associated with it. | |
|
Resets a processing state, so it can start collecting the next state. After a ProcessHttp results with true, this should be called after processing the packet content. | |
|
Returns the body of the HTTP packet (the part of data specified by content-length or by termination of the connection(? think I didn't implement that right) | |
|
Gets the specific request code at the header of the packet - http 2.0 OK sort of thing. | |
|
Gets the specific result code at the header of the packet - http 2.0 OK sort of thing. | |
|
Enumerates the various http header fields by passing them each sequentially to the specified callback. | |
| ||
|
Enumerates the various http header fields by passing them each sequentially to the specified callback. |
Name |
Description |
receives events for either GET or POST if aspecific OnHttpRequest has not been defined for the specific resource Return TRUE if processed, otherwise will attempt to match other Get Handlers | |
define a specific handler for a specific resource name on a host |
Name |
Description |
This is type sack::containers::text::http::ProcessHttpRequest. |
Copyright (c) 2000+. All rights reserved.
|
What do you think about this topic? Send feedback!
|