RecoverExceptedWebshellSuspiciousObject
- Print
- PDF
RecoverExceptedWebshellSuspiciousObject
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in VPC
Recover suspected webshell files that have been quarantined by the user from exception-handled webshell behavior detection history.
Request
The following describes the request format for the endpoint. The request format is as follows:
Method | URI |
---|---|
PATCH | /exceptions/{exception-id}/suspicious-objects/{object-id}/recover |
Request headers
For headers common to all Webshell Behavior Detector APIs, see Common Webshell Behavior Detector headers.
Request path parameters
The following describes the parameters.
Field | Type | Required | Description |
---|---|---|---|
exception-id | Integer | Required | Exception-handled webshell behavior detection history ID
|
object-id | String | Required | ID of suspect file
|
Request example
The following is a sample request.
curl --location --request PATCH 'https://wbd.apigw.ntruss.com/api/v1/exceptions/2024072409172700000036/suspicious-objects/2024072409172700000036/recover' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \
--header 'Content-Type: application/json' \
--header 'X-NCP-USE_PLATFORM_TYPE: VPC'
Response
The following describes the response format.
Response body
The following describes the response body.
Field | Type | Required | Description |
---|---|---|---|
success | Boolean | - | Request handling status |
code | Integer | - | Response code |
message | String | - | Response message |
result | Object | - | Response result |
Response status codes
For response status codes common to all Webshell Behavior Detector APIs, see Common Webshell Behavior Detector response status codes.
Response example
The following is a sample example.
{
"success": true,
"code": 0,
"message": "success",
"result": null
}
Was this article helpful?