For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
  • General
    • About Enforcers
    • Support first-party HUMAN calls
    • Troubleshoot Enforcer configurations
  • Enforcer frameworks
    • Akamai ESI
    • Apache - C Module
    • ASP.NET
    • Callout Enforcer
    • Envoy Proxy
    • F5 BIGIP
    • Fastly JavaScript Compute@Edge
      • Fastly VCL changelog
        • Installing the Enforcer
        • GraphQL Support
        • Sensitive GraphQL Operations
        • Basic Configuration
        • Customized Subroutines
        • Additional Activity Handler
        • Advanced Blocking Response
        • Creating and Configuring the Edge-Dictionary
        • Custom CSS
        • Custom First Party Sensor Endpoint
        • Custom Logo
        • Custom JS Script
        • Custom Parameters
        • Filter Requests
        • Filter by HTTP Method
        • Filter by Route
        • Filter by Extension
        • Filter by IP
        • Filter by User Agent
        • Data Enrichment
        • First Party
        • First Party Snippet
        • Enforced Routes
        • Login Credentials Extraction
        • Modify First Party Response
        • Module Context Object
        • Module Enabled
        • Module Mode
        • Monitored Routes
        • Returning A Custom Block Page
        • Sensitive Routes
        • Test Block Flow on Monitoring Mode - Bypass Monitor Header
        • Upgrading the Enforcer
    • Google Cloud Platform (GCP) Callout Enforcer
    • Kong Plugin
    • NGINX - C Module
    • NGINX - LUA Module
    • PHP
    • Python
    • Ruby
    • Salesforce Commerce Cloud Cartridge
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Creating and Configuring the Edge-Dictionary
Enforcer frameworksFastly VCLV9 and Below

Creating and Configuring the Edge-Dictionary

Was this page helpful?
Previous

Custom CSS

Next
Built with

Creating and Configuring the Edge-Dictionary

In order to support Code Defender CSP Capability in Fastly Enforcer the following configurations are required:

  1. The Fastly Enforcer module should be upgraded to v6.0.0 or higher.
  2. Create an edge-dictionary named px_csp_rdata to contain the CSP data with the following command.
1curl -X POST -H 'Fastly-Key: FASTLY_API_TOKEN' -d 'name=px_csp_rdata' https://api.fastly.com/service/<service_id>/version/<version_number>/dictionary

See the Fastly documentation for more information on edge-dictionaries.

    3a. In the px_config.vcl, create the cs_data dictionary with a Fastly API key with Engineering permission. and the px_csp_rdata dictionary ID

or

    3b. Create the cs_data dictionary as an edge-dictionary with a Fastly API key with Engineering permission and the px_csp_rdata dictionary ID

1table cs_data {
2 "eng_key": "1234567",
3 "px_csp_rdata_id": "12345678"
4}

The HUMAN team will take over the rest of the integration process once your edge-dictionary is configured.

When the our back-end work is finished, CSP is integrated on your site, and you can enable and disable the policy from your console.