Cgi Unicode C Reference Documentation
Cgi
Current Version: 9.5.0.97
Provides the ability to receive HTTP requests and all associated parameters, HTTP header fields, etc. A common use is for receiving HTTP uploads. Provides the ability to receive uploads that stream directly to disk, eliminating memory requirements for large files. Also provides the ability to receive uploaded files directly in memory.
Create/Dispose
HCkCgiW instance = CkCgiW_Create(); // ... CkCgiW_Dispose(instance);
Creates an instance of the HCkCgiW object and returns a handle ("void *" pointer). The handle is passed in the 1st argument for the functions listed on this page.
Objects created by calling CkCgiW_Create must be freed by calling this method. A memory leak occurs if a handle is not disposed by calling this function. Also, any handle returned by a Chilkat "C" function must also be freed by the application by calling the appropriate Dispose method, such as CkCgiW_Dispose.
Properties
AsyncBytesRead
To be documented soon...
topAsyncInProgress
To be documented soon...
topAsyncPostSize
To be documented soon...
topAsyncSuccess
To be documented soon...
topDebugLogFilePath
void CkCgiW_putDebugLogFilePath(HCkCgiW cHandle, const wchar_t *newVal);
const wchar_t *CkCgiW_debugLogFilePath(HCkCgiW cHandle);
If set to a file path, causes each Chilkat method or property call to automatically append it's LastErrorText to the specified log file. The information is appended such that if a hang or crash occurs, it is possible to see the context in which the problem occurred, as well as a history of all Chilkat calls up to the point of the problem. The VerboseLogging property can be set to provide more detailed information.
This property is typically used for debugging the rare cases where a Chilkat method call hangs or generates an exception that halts program execution (i.e. crashes). A hang or crash should generally never happen. The typical causes of a hang are:
- a timeout related property was set to 0 to explicitly indicate that an infinite timeout is desired,
- the hang is actually a hang within an event callback (i.e. it is a hang within the application code), or
- there is an internal problem (bug) in the Chilkat code that causes the hang.
HeartbeatMs
void CkCgiW_putHeartbeatMs(HCkCgiW cHandle, int newVal);
To be documented soon...
topIdleTimeoutMs
void CkCgiW_putIdleTimeoutMs(HCkCgiW cHandle, int newVal);
To be documented soon...
topLastErrorHtml
const wchar_t *CkCgiW_lastErrorHtml(HCkCgiW cHandle);
Provides information in HTML format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.
topLastErrorText
const wchar_t *CkCgiW_lastErrorText(HCkCgiW cHandle);
Provides information in plain-text format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.
LastErrorXml
const wchar_t *CkCgiW_lastErrorXml(HCkCgiW cHandle);
Provides information in XML format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.
topLastMethodSuccess
void CkCgiW_putLastMethodSuccess(HCkCgiW cHandle, BOOL newVal);
Indicate whether the last method call succeeded or failed. A value of TRUE indicates success, a value of FALSE indicates failure. This property is automatically set for method calls. It is not modified by property accesses. The property is automatically set to indicate success for the following types of method calls:
- Any method that returns a string.
- Any method returning a Chilkat object, binary bytes, or a date/time.
- Any method returning a standard boolean status value where success = TRUE and failure = FALSE.
- Any method returning an integer where failure is defined by a return value less than zero.
Note: Methods that do not fit the above requirements will always set this property equal to TRUE. For example, a method that returns no value (such as a "void" in C++) will technically always succeed.
topNumParams
To be documented soon...
topNumUploadFiles
To be documented soon...
topReadChunkSize
void CkCgiW_putReadChunkSize(HCkCgiW cHandle, int newVal);
To be documented soon...
topSizeLimitKB
void CkCgiW_putSizeLimitKB(HCkCgiW cHandle, int newVal);
To be documented soon...
topStreamToUploadDir
void CkCgiW_putStreamToUploadDir(HCkCgiW cHandle, BOOL newVal);
To be documented soon...
topUploadDir
void CkCgiW_putUploadDir(HCkCgiW cHandle, const wchar_t *newVal);
const wchar_t *CkCgiW_uploadDir(HCkCgiW cHandle);
To be documented soon...
topVerboseLogging
void CkCgiW_putVerboseLogging(HCkCgiW cHandle, BOOL newVal);
If set to TRUE, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is FALSE. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.
topVersion
const wchar_t *CkCgiW_version(HCkCgiW cHandle);
Methods
AbortAsync
To be documented soon...
topGetEnv
const wchar_t *CkCgiW_getEnv(HCkCgiW cHandle, const wchar_t *varName);
GetParam
const wchar_t *CkCgiW_getParam(HCkCgiW cHandle, const wchar_t *paramName);
GetParamName
const wchar_t *CkCgiW_getParamName(HCkCgiW cHandle, int index);
GetParamValue
const wchar_t *CkCgiW_getParamValue(HCkCgiW cHandle, int index);
GetRawPostData
GetUploadData
GetUploadFilename
const wchar_t *CkCgiW_getUploadFilename(HCkCgiW cHandle, int index);
GetUploadSize
To be documented soon...
topIsGet
To be documented soon...
topIsHead
To be documented soon...
topIsPost
To be documented soon...
topIsUpload
To be documented soon...
topReadRequest
To be documented soon...
topSaveNthToUploadDir
To be documented soon...
topSleepMs
To be documented soon...
topTestConsumeAspUpload
To be documented soon...
top