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
  • Upgrading to Fastly 9.0.0 and above
Enforcer frameworksFastly VCLV9 and Below

Upgrading the Enforcer

Was this page helpful?
Previous

What's New

Next
Built with

To upgrade to a newer version of the HUMAN Fastly Enforcer, email Support or contact your customer success representative via Slack.
You will be asked to provide the following information for HUMAN to start work on upgrading the VCL:

  • Your current version of VCL
  • Copies of the following files:
    • main.vcl
    • px_custom.vcl
    • px_configs.vcl
    • px.vcl
  • Application name/ID

An alternative upgrade process would be to provide the Fastly API token with engineering permissions to our solution architects team to enable HUMAN to auto upgrade your VCL files directly in your Fastly account.

Upgrading to Fastly 9.0.0 and above

If your current Enforcer version is below 9.0.0, in addition to the above upgrade process you must:

  • Add HTTPS loggers that send activities to HUMAN’s servers. For more information, see Installing the Enforcer.
  • Delete the PX-Syslog syslog logger, which is no longer in use.
  • Delete the PX-Syslog-Condition condition, which is no longer in use.
  • If you implemented the px_custom_activity_headers function in the px_custom.vcl file, refactor it to fit the new format.
    See the comments as example.