Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle bot traffic #52

Closed
2 tasks done
chadokruse opened this issue Dec 31, 2018 · 0 comments
Closed
2 tasks done

Handle bot traffic #52

chadokruse opened this issue Dec 31, 2018 · 0 comments

Comments

@chadokruse
Copy link
Member

chadokruse commented Dec 31, 2018

  • Goal is to limit unnecessary hits to third party services (e.g. Stitch)

  • 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.

Discussion here.

@chadokruse chadokruse added ready and removed ready labels Jan 4, 2019
@chadokruse chadokruse changed the title Add rate limiting to insights Stitch call Handle bot traffic Jan 10, 2019
@chadokruse chadokruse reopened this Jan 11, 2019
@chadokruse chadokruse removed the ready label Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant