JayBizzle / Crawler-Detect / #2024 / 1
100%
master: 100%

DEFAULT BRANCH: master
Ran
Files 5
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 100.0%. Remained the same
#2024.1

push

web-flow 
Remove ^Amazon CloudFront crawler signature (#602)

* Remove ^Amazon CloudFront crawler signature

CloudFront's dominant traffic pattern at the origin is reverse-proxy
fetches on behalf of real end users (cache miss / origin shield), not
crawler activity. Classifying it as a crawler causes silent
analytics/auth/rate-limit bugs for any site hosted behind CloudFront.

The signature has flip-flopped (added 2020, removed 2020, re-added
2023 with anecdotal "getting tons of this lately" justification — see
#392, #410, #504). The 2020 removal had clear technical reasoning that
still applies. Removing again, with a regression guard in devices.txt
to lock in the decision.

`^Amazon Simple Notification Service Agent$` and
`^Amazon-Route53-Health-Check-Service` remain in the list — those are
unambiguously bots.

Fixes #594.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Add dedicated regression test for Amazon CloudFront

The fixture line in devices.txt was easy to delete by accident in a
future change. Replacing it with a named test that explicitly documents
the decision and the issue history, so a future re-add PR will fail
with a clearly-named assertion that prompts a deliberate choice instead
of a silent revert.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

40 of 40 relevant lines covered (100.0%)

14.85 hits per line

Source Files on job #2024.1