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
      • AWS Lambda@Edge changelog
    • Callout Enforcer
    • Envoy Proxy
    • F5 BIGIP
    • Fastly JavaScript Compute@Edge
    • 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
  • May 27, 2026
  • 4.10.1
  • March 31, 2026
  • Version 4.10.0
  • March 8, 2026
  • Version 4.9.0
  • January 27, 2026
  • Version 4.8.1
  • November 9, 2025
  • Version 4.8.0
  • October 16, 2025
  • Version 4.7.0
  • August 20, 2025
  • Version 4.6.0
  • May 31, 2025
  • Version 4.5.0
  • March 25, 2025
  • Version 4.4.0
  • November 7, 2024
  • Version 4.3.2
Enforcer frameworksAWS Lambda@Edge

AWS Lambda@Edge changelog

May 27, 2026
May 27, 2026

March 31, 2026
March 31, 2026

March 8, 2026
March 8, 2026

January 27, 2026
January 27, 2026

November 9, 2025
November 9, 2025

October 16, 2025
October 16, 2025

August 20, 2025
August 20, 2025

May 31, 2025
May 31, 2025

March 25, 2025
March 25, 2025

November 7, 2024
November 7, 2024

Older posts

Next
Built with

4.10.1

Added

  • Pass request object to response custom parameters custom function
  • Custom block on error message configuration support

Version 4.10.0

  • MCP Protection support
  • Send original vid from cookie on all activities under orig_cookie_vid

Version 4.9.0

  • Added Hard Block support, which lets you customize the Hard Block page that’s displayed to users when a request is blocked without a challenge. Hard Block customization options use the same configuration options as the regular Challenge page. Be sure to update the appropriate configuration options to customize the Hard Block page, not the block page template. The relevant configuration options are:
    • px_custom_logo: Adds a custom logo to the Challenge and Hard Block pages. Maps to {{customLogo}} in the block page template.
    • px_css_ref: Adds a custom CSS file to the Challenge and Hard Block pages. Maps to {{cssRef}} in the block page template.
    • px_js_ref: Adds a custom JS file to the Challenge and Hard Block pages. Maps to {{jsRef}} in the block page template.
    • px_first_party_enabled: A boolean flag to enable first party mode. Maps to {{firstPartyEnabled}} in the block page template.

Version 4.8.1

  • Added compression for px-context header to avoid AWS CloudFront request size limits (20KB) for HumanActivities Lambda

Version 4.8.0

  • Added is_sensitive_route field to risk api and async activities
  • Added request_id to telemetry activity details
  • Telemetry activity update_reason field updated to reflect the reason for telemetry activity:
    • command - incoming telemetry request received
    • risk - telemetry triggered via risk response field

Version 4.7.0

  • Added internal tool for generating deployment manifests

Version 4.6.0

  • Support for adding a data enrichment header (new px_data_enrichment_header_name configuration)
  • Added response custom parameters to supported features and supported it in the CI workflows
  • Added Documentation enforcement workflow - verify that the documentation is up to date with the latest changes in the codebase

Version 4.5.0

  • Improvements to request RTT and Lambda execution time by sending async HTTP requests in subsequent Lambda invocations
  • Added support for interpreting regex-formatted strings (e.g., "/^/regex/path$/i") as regular expressions for the following configurations:
    • px_sensitive_routes
    • px_monitored_routes
    • px_enforced_routes
    • px_graphql_routes
    • px_filter_by_route
    • px_filter_by_user_agent
    • px_graphql_keywords
    • px_sensitive_graphql_operation_names
    • px_login_credentials_extraction object fields path (when path_type is "regex") and login_successful_body_regex

Version 4.4.0

  • Added px_token_version configuration to enable support for cookie v2 (cookie v3 is default)
  • Support for regular expressions in px_filter_by_user_agent
  • Extracting GraphQL operationName and variables even if the query field is not present
  • Fixed issue where telemetry would fail if px_cookie_secret was an array of cookie strings

Version 4.3.2

  • Fixed a bug where malformed URLs resulted in an uncaught exception