Cgi C++ Reference Documentation
CkCgi
Deprecated To be removed in a future version, and should no longer be used.
Current Version: 10.1.3
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.
Object Creation
// Local variable on the stack CkCgi obj; // Dynamically allocate/delete CkCgi *pObj = new CkCgi(); // ... delete pObj;
Properties
AsyncBytesRead
To be documented soon...
topAsyncInProgress
To be documented soon...
topAsyncPostSize
To be documented soon...
topAsyncSuccess
To be documented soon...
topDebugLogFilePath
const char *debugLogFilePath(void);
void put_DebugLogFilePath(const char *ansiOrUtf8Str);
If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.
Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.
Possible causes of hangs include:
- A timeout property set to 0, indicating an infinite timeout.
- A hang occurring within an event callback in the application code.
- An internal bug in the Chilkat code causing the hang.
HeartbeatMs
void put_HeartbeatMs(int newVal);
To be documented soon...
topIdleTimeoutMs
void put_IdleTimeoutMs(int newVal);
To be documented soon...
topLastErrorHtml
Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastErrorText
Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
LastErrorXml
Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastMethodSuccess
void put_LastMethodSuccess(bool newVal);
Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages.
topNumParams
To be documented soon...
topNumUploadFiles
To be documented soon...
topReadChunkSize
void put_ReadChunkSize(int newVal);
To be documented soon...
topSizeLimitKB
void put_SizeLimitKB(int newVal);
To be documented soon...
topStreamToUploadDir
void put_StreamToUploadDir(bool newVal);
To be documented soon...
topUploadDir
const char *uploadDir(void);
void put_UploadDir(const char *ansiOrUtf8Str);
To be documented soon...
topUtf8
void put_Utf8(bool newVal);
When set to true, all "const char *" arguments are interpreted as utf-8 strings. If set to false (the default), then "const char *" arguments are interpreted as ANSI strings. Also, when set to true, and Chilkat method returning a "const char *" is returning the utf-8 representation. If set to false, all "const char *" return values are ANSI strings.
topVerboseLogging
void put_VerboseLogging(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
Methods
AbortAsync
To be documented soon...
Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.
topAsyncReadRequest
To be documented soon...
topGetEnv
GetParam
const char *getParam(const char *paramName);
GetParamName
GetParamValue
GetRawPostData
GetUploadData
GetUploadFilename
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