Functions

The following table lists functions in this documentation.

	Name	Description
	AddHttpData	Add another bit of data to the block. After adding data, ProcessHttp should be called to see if the data has completed a packet.
	CreateHttpServer	HTTP_EXPORT PTEXT result PostHttp( PTEXT site, PTEXT resource, PTEXT content );
	CreateHttpServerEx	This is function sack::containers::text::http::CreateHttpServerEx.
	CreateHttpState	Creates an empty http state, the next operation should be AddHttpData.
	DestroyHttpState	Destroys a http state, releasing all resources associated with it.
	EndHttp	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.
	GetHttpContent	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)
	GetHttpRequest	Gets the specific request code at the header of the packet - http 2.0 OK sort of thing.
	GetHttpResponce	Gets the specific result code at the header of the packet - http 2.0 OK sort of thing.
	ProcessCGIFields	Enumerates the various http header fields by passing them each sequentially to the specified callback.
	ProcessHttp	returns TRUE if completed until content-length if content-length is not specified, data is still collected, but the status never results TRUE.
	ProcessHttpFields	Enumerates the various http header fields by passing them each sequentially to the specified callback.

Namespace

sack::containers::text::http Namespace

Links

Functions, sack::containers::text::http Namespace, Legend

Created with a commercial version of

Doc-O-Matic. In order to make this message disappear you need to register this software. If you have problems registering this software please contact us at

support@toolsfactory.com.

Contents | Index | Reference | Home

What do you think about this topic? Send feedback!