Enforcer frameworksFastly Rust Compute@Edge

Fastly Rust Compute@Edge changelog

May 7, 2026

Version 1.2.7

Changed

  • Fix is_sensitive_request_fn callback overwriting prior sensitivity detection from sensitive_routes configuration and GraphQL inspection. The callback’s result is now OR-ed with the existing value, so it can only escalate (never demote) a request’s sensitivity.
April 30, 2026

Version 1.2.6

Added

  • px_graphql_body_max_length configuration to set GraphQL max body length
  • Included missing fields in all activities

Fixed

  • Optimized processing of GraphQL requests with large bodies
April 24, 2026

Version 1.2.5

Added

  • CORS support configurations: -px_cors_support_enabled -px_cors_preflight_request_filter_enabled
  • Callback functions: -cors_custom_preflight_handler_fn() -cors_create_custom_block_response_headers_fn()

Changed

  • Updated dependencies
March 10, 2026

Version 1.2.4

Added

  • Implemented Access Cookie feature, which adds support for extracting the _pxac cookie (or custom cookies defined in px_extracted_cookies)
September 17, 2025

Version 1.2.3

Changed

  • Updated to Fastly v1.11.5 (due to a bug in Fastly v1.11.6)

Version 1.2.2

Added

  • Support for data enrichment feature
  • px_data_enrichment_header_name configuration
  • additional_activity_handler callback function to be executed after sending page_requested or block activity to the collector
  • Support for pxcts cookie

Changed

  • Updated dependencies
  • Updated documentation
  • Updated example code
September 11, 2025

Version 1.2.1

Added

  • is_filtered_request callback function to filter out requests that should not be verified by Enforcer
  • px.set_module_mode() to change module mode at runtime

Version 1.2.0

Added

  • is_sensitive_request callback function to identify sensitive requests

Changed

  • Hid Enforcer internal API
  • Allowed read-only access to PXConfig, PXContext, and PXEnforcer members using getters
September 26, 2024

Version 1.1.5

Changed

  • Logging reworked. It now uses Level::Info level
  • Do not call log::set_max_level(), to avoid “panic!” in the application
  • wasm32-wasi target was renamed to wasm32-wasip1