Error (2026-06-20)
is_status error: wreq::Error { kind: Status(404, None), uri: https://committees.westminster.gov.uk/mgError.aspx }
Duration: 6.5s
Investigation
The scraper's base_url in metadata.json is http://committees.westminster.gov.uk (HTTP). The framework constructs http://committees.westminster.gov.uk/mgWebService.asmx/GetCouncillorsByWard and the following redirect chain occurs:
http://committees.westminster.gov.uk/mgWebService.asmx/GetCouncillorsByWard → 301 → HTTPS
https://committees.westminster.gov.uk/mgWebService.asmx/GetCouncillorsByWard → 302 → mgError.aspx
https://committees.westminster.gov.uk/mgError.aspx → 404
This means the ModGov web service on Westminster's server is responding but the application is returning an error (redirect to mgError.aspx), and the error page itself isn't found (404). This is an application-level error, not a network or certificate issue.
Direct fetch of https://committees.westminster.gov.uk returns HTTP 403 (Cloudflare WAF), so the domain is live but behind Cloudflare. The ModGov service endpoint itself is returning an application error rather than councillor data.
Fix patterns ruled out
- HTTPS migration — Would fix the
http:// → https:// mismatch, but the HTTPS endpoint itself is broken (returning 302 → mgError.aspx)
verify_requests = False — Not a cert issue; the TLS handshake completes
http_lib = "playwright" — Might bypass the Cloudflare WAF on the main domain, but the underlying ModGov application error (redirect to error page) would still occur
- URL changes — Unknown; Westminster's main website may reference a new councillors URL or a different CMS
What needs to happen
- Check whether
committees.westminster.gov.uk is temporarily broken or if Westminster has migrated their ModGov instance or moved to a different CMS.
- If still on ModGov at a different subdomain, update
base_url in metadata.json.
- Also migrate
base_url from http:// to https:// regardless.
- Add
http_lib = "playwright" if the new URL is behind Cloudflare.
This requires visual inspection of Westminster's council website to find the current councillors URL.
Error (2026-06-20)
Investigation
The scraper's
base_urlinmetadata.jsonishttp://committees.westminster.gov.uk(HTTP). The framework constructshttp://committees.westminster.gov.uk/mgWebService.asmx/GetCouncillorsByWardand the following redirect chain occurs:http://committees.westminster.gov.uk/mgWebService.asmx/GetCouncillorsByWard→ 301 → HTTPShttps://committees.westminster.gov.uk/mgWebService.asmx/GetCouncillorsByWard→ 302 →mgError.aspxhttps://committees.westminster.gov.uk/mgError.aspx→ 404This means the ModGov web service on Westminster's server is responding but the application is returning an error (redirect to
mgError.aspx), and the error page itself isn't found (404). This is an application-level error, not a network or certificate issue.Direct fetch of
https://committees.westminster.gov.ukreturns HTTP 403 (Cloudflare WAF), so the domain is live but behind Cloudflare. The ModGov service endpoint itself is returning an application error rather than councillor data.Fix patterns ruled out
http://→https://mismatch, but the HTTPS endpoint itself is broken (returning 302 → mgError.aspx)verify_requests = False— Not a cert issue; the TLS handshake completeshttp_lib = "playwright"— Might bypass the Cloudflare WAF on the main domain, but the underlying ModGov application error (redirect to error page) would still occurWhat needs to happen
committees.westminster.gov.ukis temporarily broken or if Westminster has migrated their ModGov instance or moved to a different CMS.base_urlinmetadata.json.base_urlfromhttp://tohttps://regardless.http_lib = "playwright"if the new URL is behind Cloudflare.This requires visual inspection of Westminster's council website to find the current councillors URL.