3.2.5 Message Processing Events and Sequencing Rules
The server MUST match ConfigurationId from the URL with ServerConfigurationId, ModuleName with ServerModuleName, and ModuleVersion with ServerModuleVersion of the ModuleTable. The server uses case-insensitive ordinal comparison to match ConfigurationId, ModuleName, and ModuleVersion. For a ServerConfigurationId, the server MUST have a unique combination of ServerModuleName and ServerModuleVersion. ServerModuleName in the ModuleTable MUST NOT be empty. If a match is found, the server returns ModuleData to the client with status code 200. If a match is not found, the server returns status code 404.
|
Resource |
Description |
|---|---|
|
Module(ConfigurationId={ConfigurationId},ModuleName={moduleName},ModuleVersion={moduleVersion})/ModuleContent |
Get the module from the server. |
The responses to all the methods can result in the following status codes.
|
Status code |
Reason phrase |
Description |
|---|---|---|
|
200 |
OK |
Request completed. |
|
400 |
BAD REQUEST |
The request could not be understood by the server due to malformed syntax. |
|
404 |
NOT FOUND |
Used in cases where the resource is not found. |
The response message for this operation contains the following HTTP headers.
|
Response header |
Usage |
Value |
|---|---|---|
|
Checksum |
Required |
As specified in section 2.2.2.2. |
|
ChecksumAlgorithm |
Required |
As specified in section 2.2.2.3. |