3.1.5 Message Processing Events and Sequencing Rules
The server MUST match the ConfigurationId from the URL and, if specified, the ConfigurationName from the headers with the ServerConfigurationId in the ConfigurationTable. The server MUST use case-insensitive ordinal comparison to match the ConfigurationId (section 2.2.3.1) and ConfigurationName (section 2.2.2.4). If a match is found, the server MUST return ConfigurationData to the client with status code 200. If a match is not found, the server MUST return status code 404.
|
Resource |
Description |
|---|---|
|
Action(ConfigurationId={ConfigurationId})/ConfigurationContent |
Gets the configuration from the server. |
|
Request header |
Usage |
Value |
|---|---|---|
|
ConfigurationName |
Optional |
As specified in section 2.2.2.4. |
The responses to all the methods can result in the following status codes.
|
Status code |
Reason phrase |
Description |
|---|---|---|
|
200 |
OK |
Returned when the request is completed. |
|
400 |
BAD REQUEST |
The request could not be understood by the server due to malformed syntax. |
|
404 |
NOT FOUND |
Returned when 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. |