[x] Goal is to limit unnecessary hits to third party services (e.g. Stitch)
[x] Secondary goal is to limit false positives on Bugsnag (e.g. Stitch Network Errors
=> Option 1: Handle w/in Stitch Function
via Custom HTTP Header (will solve most current scenarios)
Option 2: Handle at Cloudflare level
Per Cloudflare:
Rate limiting will only apply to requests to your origin, so if you’re utilizing Cloudflare’s caching then your css, js and images would (typically) already be in cache.
...
Just to clarify, by default the rate limiting only applies to non-cached requests.
[x] Goal is to limit unnecessary hits to third party services (e.g. Stitch)
[x] Secondary goal is to limit false positives on Bugsnag (e.g. Stitch Network Errors
=> Option 1: Handle w/in Stitch Function via Custom HTTP Header (will solve most current scenarios)
Option 2: Handle at Cloudflare level Per Cloudflare:
Discussion here.