How the DNCA evaluates capture types

About this task

When hits are identified in the Pipeline tab, the DNCA performs the evaluation of the hit in the following order to determine if it must be captured:

Procedure

  1. Request:
    1. Checks Request for content encoding type. If the type matches the specified set of types to inflate, the request is inflated for processing. See Capture All Content-Encoding Types.
    2. Checks Request for the following internally known content types. See Default Captured Content Types.
    3. Set the request content and body types:
      1. Checks the XML POST Type list for POSTs of XML type to capture. See XML POST Types.
      2. Checks the Binary POST Type list for POSTs of binary type to capture. See Binary POST Types.
    4. Check file extension types list for included and excluded types:
  2. Response:
    1. Check the following content types lists for values:
    2. If no values are found in the lists, the DNCA checks its internal default list for response types. See Internal default response types.
    3. If there are values in the lists, check the following lists in the order that is mentioned .
  3. Request Body: If the Request and Response pass the previous tests to be included, then the Request body is processed.
    1. If Request content type is defined in one of the previous, then the DNCA processes its type accordingly.
    2. If the content type for the request body is still unknown after the previous checks, it checks the Capture All Post Types list.
      1. If the content type is found in list, the DNCA then processes the body as text in [RequestBody] section of the generated request.
      2. See Capture All POST Types.