Fix FIF (Fife) scraper#419
Open
symroe wants to merge 2 commits into
Open
Conversation
fife.gov.uk returns HTTP 403 to wreq's Firefox133 TLS fingerprint but serves the councillors page correctly to browser clients. The WAF drops the connection when it detects the non-browser TLS client-hello. This is the same WAF fingerprint block pattern seen on ELN (PR #410), HAL (#400), TON (#402), and others. Adding http_lib = "playwright" switches from wreq to headless Chromium, whose Chrome TLS fingerprint passes the WAF. The scraper has been failing for 10 consecutive days (2026-06-23 through 2026-07-02).
Remove stray '[' from .councillor-social mailto selector that would have caused an invalid CSS selector error at runtime.
Member
Author
Re-scrape after 6938062Added A local scrape cannot be confirmed from this environment — the WAF blocks all non-Chromium HTTP clients (curl, requests, wreq) used in pre-Lambda testing. Counts will be populated on the next scheduled Lambda run.
Generated by Claude Code |
symroe
pushed a commit
that referenced
this pull request
Jul 10, 2026
…int block www.cne-siar.gov.uk returns HTTP 403 to wreq's Firefox133 TLS fingerprint. The existing verify_requests=False addresses a certificate trust issue but does not bypass the WAF's TLS fingerprint check. Adding http_lib="playwright" switches to headless Chromium's Chrome TLS fingerprint, which passes the WAF and allows the councillors page and individual detail pages to load correctly. Same fix pattern as ELN (#410), FIF (#419), and other recently fixed councils.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What broke
www.fife.gov.ukreturns HTTP 403 to wreq's Firefox133 TLS fingerprint but serves the councillors page correctly to browser clients. The WAF drops the connection when it detects the non-browser TLS client-hello, causing the scraper to fail. The scraper has been failing for 10 consecutive days (2026-06-23 through 2026-07-02). This is the same WAF fingerprint block pattern seen on ELN (PR #410), HAL (#400), TON (#402), MON (#401), and others.What was fixed
http_lib = "playwright"to the Scraper class — headless Chromium's Chrome TLS fingerprint passes the WAF check, allowing the councillors page and individual councillor detail pages to be fetched correctly.Scrape results
The endpoint serves valid HTML to browser clients (confirmed). Counts will be confirmed after the next Lambda run.
Generated by Claude Code