You can either install from source (you\'re looking at it), or from the WordPress plugin directory.

  1. To proceed with configuration you will need to sign up for Fastly and create and activate a new service (unless you already have one). Details of how to create and activate a new service can be found here. You will also need to find your Service ID and make a note of the string.
  2. You will need to create an API token with the Global API access option selected. Click here for token management screen.
  3. Set up the Fastly plugin inside your WordPress admin panel
  4. In your WordPress blog admin panel, Under Fastly->General, enter & save your Fastly API token and Service ID
  5. Verify connection by pressing TEST CONNECTION button.
  6. In order to get the most value out of Fastly we recommend you upload VCL snippets from These snippets will add code for following

– Force certain paths to be passed (not cached) e.g. wp-admin, wp-login.php
– Makes sure that logged in user sessions are never cached
– Handling for serving stale on error

You can upload them by hand or press Update VCL button in the UI.

For more information, or if you have any problems, please email us.

Note: you may have to disable other caching plugins like W3TotalCache or WP Rocket to avoid getting odd cache behaviour.

  • Pulls in the Fastly API
  • Integrates purging in post/page/taxonomies publishing
  • Includes an admin panel in wp-admin
  • Integrates some of the advanced purging options from Fastly API
  • Allows to monitor purging using webhooks for slack

Using this plugin means you won't have to purge content in Fastly when you make changes to your WordPress content. Purges will automatically happen with no need for manual intervention.


Edge Modules

Edge Modules are a framework that enables specific functions to be enabled on Fastly Edge without
the need to write VCL. Current list of functions that can be included includes

  • Enable Blackfire metrics and tracing
  • Set CORS headers
  • Enable support for bot detection partners such as Datadome/Netacea
  • Redirect one domain to another e.g. =>
  • Rewrite URLs going to a backend e.g. /sitemap.xml => /media/sitemap.xml
  • Domain masking an external backend/origin

More details can be found at

Image optimization

Image Optimization is a separately contracted feature. Please contact to request
pricing and activation.

Once activated on service level, you will be able to enable it in your blog under Fastly->Advanced.

Breakdown of IO options:
Enable Image Optimization in Fastly configuration – Activating this uploads VCL that steers image traffic to the image optimization service

Enable Image Optimization in WordPress - Main switch to activate IO which is needed for all other options to work.

Enable adaptive pixel ratios - Switch for adaptive pixel ratios implementation. This replaces adaptive pixels srcset to format which Fastly IO can parse and replace. Initially works only on inserted attachments like featured images, but can be applied on content images if enabled.

Adaptive pixel ratio sizes - Select pixel ratios that will be generated when creating image srcset html.

Enable image optimization for content images - Safe switch for Image optimization of content images (due to difference from featured images, those are processed differently). To fully utilize, insert full size images in content.

WordPress Hooks

Available wordpress hooks (add_action) on:

Editing purging keys output
functions: add_keys

Editing surrogate control headers output(max-age, stale-while-revalidate, stale-if-error)
functions: edit_headers, unset_headers

Edit cache control headers output (max-age)
functions: edit_headers, unset_headers

add_action(\'purgely_pre_send_surrogate_control\’, \'custom_headers_edit\’);
function custom_headers_edit($header_object)
$header_object->edit_headers(array(\'custom-header\’ => \'555\’, \'max-age\’ => \'99\’));

add_action(\'purgely_pre_send_keys\’, \'custom_surrogate_keys\’);
function custom_surrogate_keys($keys_object) {

Note: you may have to disable other caching plugins like W3TotalCache to avoid getting odd cache behaviour.

About Fastly

Fastly is the only real-time content delivery network designed to seamlessly integrate with your development stack.

Fastly provides real-time updating of content and the ability to cache dynamic as well as static content. For any content that is truly uncacheable, we'll accelerate it.

In addition we allow you to update your configuration in seconds, provide real time log and stats streaming, powerful edge scripting capabilities, and TLS termination (amongst many other features).

License WordPress Plugin
Copyright (C) 2011,2012,2013,2014,2015,2016,2017

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program. If not, see

Slike ekrana

  • Fastly General Tab
  • Fastly Advanced Tab
  • Fastly Webhooks Tab


Nema recenzija za ovaj dodatak.

Saradnici i programeri

“Fastly” is open source software. The following people have contributed to this plugin.


Prevedi “Fastly” na vaš jezik.

Zainteresirani za razvoj?

Pregledajte kôd, pogledajte SVN spremišteili se pretplatite na dnevnik razvoja od RSS.

Zapis promijena

= 1.2.26

  • Code cleanup, improvements in data sanitization and escaping input

= 1.2.25

  • Assignment fix for constants

= 1.2.24

  • Updates to Datadome and Netacea edge modules

= 1.2.23

  • Compatibility fixes for WordPress 6.2

= 1.2.22

  • Fixes for PHP 8.1

= 1.2.20

  • Another fix for PHP 8

= 1.2.19

  • Fixes for PHP 8

= 1.2.18

  • ‘front page’ should be automatically purged just like the ‘home’ page

= 1.2.17

  • Fix for edge modules with option values defaulting to a single value


  • Scheduling posts would purge content at submission and activation. Make sure we don't purge at submission time


  • Always purged keys sanitization callback was overly aggresive stripping underscores


  • Add missing files that were missing in 1.2.13 deploy


  • Introduce Edge Modules


  • Removed restart logic from VCL snippets as it may clash with Image Optimization


  • API token sanitization was too aggressive stripping off underscores which are now legitimate characters in a token


  • Remove a call to a now deprecated function


  • Added fix for scheduled posts transition to published


  • Minor fixes


  • Fixed duplicated API calls on admin page loads


  • Add Image Optimization configuration


  • Added fix for including only always purged keys if existing
  • Added fix for header surrogate key number larger than limit


  • Added fix for not yet existing pages not being purged (404 pages key issue)
  • Added admin entry for always purged keys
  • Make surrogate keys comply with multi-site configurations


  • wp_cli added configuration listing and updating functionality
  • Enabled setting of HTML for Maintenance/Error page (503)
  • Minor fixes


  • Action Hooks fix


  • Minor VCL clean up


  • Added purge by url
  • Changes regarding logging logic
  • VCL update User Interface changes
  • Fixed and enabled support for wp_cli


  • Some Purgely plugin functionalities integrated into Fastly (along with some advanced options)
  • Purging by Surrogate-Keys is used instead of purging by url
  • Added webhooks support (Slack focused) to log purges and other critical events
  • Added debugging logs option, purge all button for emergency
  • Advanced options: Surrogate Cache TTL, Cache TTL, Default Purge Type, Allow Full Cache Purges, Log purges in error log,
    Debug mode, Enable Stale while Revalidate, Stale while Revalidate TTL, Enable Stale if Error, Stale if Error TTL.
  • Fastly VCL update
  • Curl no longer needed


  • Include fixes for header sending
  • Enable \”soft\” purging


  • Mark as deprecated
  • Recommend Purgely from Condé Nast
  • Add in link to GitHub repo


  • Add a guard function for cURL prequisite
  • Bring up to date with WP Plugin repo standards


  • Security fixes for XSS/CSRF
  • Only load CSS/JS on admin page
  • Properly enqueue scripts and styles
  • Use WP HTTP API methods
  • Properly register scripts


  • Change to using PURGE not POST for purges
  • Correct URL building for comments purger


  • Fix bug in port addition


  • Make work in PHP 5.3


  • Fix comment purging


  • Fix url purging


  • Fix category purging


  • Remove bogus error_log call


  • Switch to using curl
  • Change PURGE methodology
  • Performance enhancements