Fix LBH (Lambeth) scraper#363
Open
symroe wants to merge 1 commit into
Open
Conversation
Lambeth's ModernGov server (moderngov.lambeth.gov.uk) responds in ~5s for standard clients (curl) but wreq's Firefox133 TLS fingerprint times out from Lambda. Playwright (Chromium) uses a standard Chrome TLS fingerprint that passes the server's WAF, bypassing the block.
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
2 participants
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
Lambeth's ModernGov endpoint (
moderngov.lambeth.gov.uk) responds in ~5 seconds for standard clients (curl, system SSL — HTTP 200 with valid XML) but wreq's Firefox133 TLS fingerprint times out after 30 seconds from Lambda. The server completes the TLS handshake for standard fingerprints but stalls on wreq's specific client hello, consistent with WAF-level TLS fingerprint filtering.What was fixed
http_lib = "playwright"— Playwright uses Chromium's standard Chrome TLS fingerprint, bypassing the WAF that blocks wreq's Firefox133 fingerprint. The server cert is valid and trusted by Chromium, so no additional cert flags are needed.Scrape results
Cannot run locally (TLS inspection proxy in the build environment). The endpoint returns HTTP 200 with valid councillor XML from a clean IP.
Generated by Claude Code