AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to check if certain allowed URLs or domains have mixed content types. Specifically, the "Allowed Urls Has Mixed" operation verifies whether the allowed URLs associated with a given policy contain mixed content (e.g., both secure and non-secure elements). This is useful for security teams managing web filtering policies to ensure that allowed URLs comply with security standards.

Practical scenarios include:

  • Validating URL filters in a policy to detect mixed content issues.
  • Auditing allowed URLs before applying or updating DNS filtering policies.
  • Automating compliance checks on allowed URLs within network security configurations.

Properties

Name Meaning
Policy Id The unique identifier of the policy whose allowed URLs/domains are being checked.
Additional Query Parameters Optional filters for the query:
• Search: Text to search within URL values and notes.
• Type: Filter by type, valid options are url, pattern, domain, tld.
Additional Body Fields Optional additional fields sent in the request body:
• Ids: JSON array of specific URL filter IDs to check, overrides other filters.
• Exclude Ids: JSON array of URL filter IDs to exclude when using filters.

Output

The node outputs JSON data representing the result of the "Allowed Urls Has Mixed" check. This typically includes information about whether the specified allowed URLs have mixed content and details about those URLs or filters.

If binary data were involved (not indicated here), it would represent related file or media content, but this node focuses on JSON responses from the API.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter API.
  • The node sends HTTP requests to https://api.dnsfilter.com.
  • No additional external dependencies beyond the API access and n8n's HTTP request capabilities.

Troubleshooting

  • Common Issues:

    • Invalid or missing Policy Id: Ensure the Policy Id is correct and exists in the DNSFilter system.
    • Incorrect JSON format in "Ids" or "Exclude Ids": These must be valid JSON arrays; otherwise, parsing errors may occur.
    • Network or authentication errors: Verify the API key credential is correctly configured and has necessary permissions.
  • Error Messages:

    • Authentication failures usually indicate invalid or expired API keys.
    • Validation errors may arise if required parameters are missing or malformed.
    • API rate limits could cause temporary failures; retry after some time.

Links and References

Discussion