Caching Purge with REST API

  • anshulr007

    (@anshulr007)


    12 months ago

    Hello,

    I need help with a caching issue while working with the REST API + FlyingPress + Cloudflare setup.

    I’m running a high-content WordPress site using the Newspaper theme where we’re publishing 20+ articles per hour via the WordPress REST API using a Python-based publishing tool.

    After extensive testing across multiple setups, here’s where things currently stand:✅ What’s Working:

    • FlyingPress plugin + Flying CDN (Cloudflare backend) delivers top-tier performance — excellent Core Web Vitals, snappy load times, and impressive image delivery.
    • When content is added manually (via WP Dashboard), caching is purged correctly and pages get updated in real time.
    • On another site using LiteSpeed Cache + QUIC.cloud, cache purging works flawlessly even via REST API — but the performance (especially image optimization and TTFB) is not on par with FlyingPress.

    ❌ The Problem:

    • When adding posts via REST API, FlyingPress does not purge the cache.
    • This means visitors still see stale content even though the REST API has added the new posts.
    • FlyingPress support has been unhelpful — they confirm the plugin doesn’t automatically handle REST-based post creation properly for cache purging.
    • I’ve tested several workaround plugins (like Purge Cache on REST Publish, custom WP hooks, etc.) — none worked reliably or at the scale I need.

    🔧 What I’ve Tried:

    • Hooking into rest_after_insert_post, save_post, and wp_insert_post manually via custom plugins/functions.
    • Disabling async caching in FlyingPress.
    • Manually hitting purge endpoints via REST — not scalable.
    • WP Cron-based solutions — not fast or reliable enough.

    💡 What I Need Help With:

    1. Is there a reliable way to trigger FlyingPress cache purge automatically when posts are published via REST API?
    2. Is there any hook or trigger that works with FlyingPress specifically and supports high-frequency REST publishing?
    3. **If not FlyingPress, is there any caching + CDN combo that:
      • Matches FlyingPress’s speed (especially image delivery)?
      • Purges cache accurately when posts are created via REST API?
      • Is production-grade for large-scale publishing sites?**

    This is a mission-critical issue, and I don’t want to move away from FlyingPress if I can help it. The performance is simply unmatched — but stale content is a major blocker.

    Really appreciate any thoughts, custom code tips, or plugin suggestions. 🙏

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator threadi

    (@threadi)

    11 months, 4 weeks ago

    I would recommend contacting the support forum at https://ww.wp.xz.cn/support/plugin/flying-pages/.

    Thread Starter anshulr007

    (@anshulr007)

    11 months, 4 weeks ago

    Hello,
    Thanks for the reply
    I’ve been extensively using the LiteSpeed Cache plugin combined with QUIC.cloud CDN and Image Optimization (Advanced Queue) across multiple WordPress sites. While the integration works decently for general performance, there’s a persistent issue that’s critically affecting Core Web Vitals:

    The Core Issues:

    1. Cache Purging Is Not Working Reliably via REST API

    I’ve already checked with Gijo (see: https://prnt.sc/CnRtVIOaxZ11)

    Their plugin or cache management layers cannot reliably purge both server cache + CDN cache together every time.

    2. Images in the First Viewport Are Not Being Delivered Optimally

    Even after paying for QUIC.cloud’s advanced image optimization and getting consistent 99+ PageSpeed scores, images in the first fold (above-the-fold) are not showing up immediately. They are either delayed or not rendered at all in the initial paint.

    Tested on multiple networks and devices. Lighthouse still shows missing key images in the treemap.

    3. Cloudflare Alternative — Also Ineffective

    I tested using Cloudflare Pro as an alternative CDN. APO/Polish/Image Offloading with Plugin
    Moreover, Cloudflare + LiteSpeed historically don’t play well together — too many cache layer conflicts.

    I considered offloading images via Cloudflare https://ww.wp.xz.cn/plugins/cf-images/while keeping QUIC.cloud for page-level CDN, but that leads to further complexity — especially since my DNS is managed by QUIC.cloud.


    What Has Already Been Checked:

    • All CSS/JS have been perfectly optimized (per Brian from Perfmatters: https://prnt.sc/i7iIMp4KbAy5).
    • Theme support (Newspaper) confirms no render-blocking or layout shifting assets.
    • Using native Lazy Load, LQIP, and async CSS settings appropriately.
    • Scores are great — e.g., https://prnt.sc/Ge-UTcE7Bic1 — but Core Web Vitals still fail due to image-related issues.

    • What I Need:
    • I want a bulletproof stack where:
    • Images in the first viewport load instantly from the nearest CDN POP.
    • Cache purge works flawlessly on every new post or update, via API or backend — server + CDN both.
    • Preferably works with QUIC.cloud or an alternative that’s compatible with LiteSpeed and supports dynamic purge reliably.
    • I’ve spent almost 2 years testing and trying all combinations. If anyone has solved this workflow or has a proven setup, I’m all ears.
    • Thanks in advance for your time and help.


Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Caching Purge with REST API’ is closed to new replies.

Tags