rates/backend/services
jtricerolph 46eada16a3 Try forcing TLS 1.2 max to fix DataImpulse residential IP handshake failures
Some DataImpulse residential IPs drop Chromium's TLS 1.3 GREASE/key_share
extensions mid-handshake (EOF error), while TLS 1.2 negotiation succeeds.
Booking.com supports TLS 1.2 so this should not affect scrape results.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-07-10 10:48:56 +00:00
..
direct_profiles
scraper_backends Try forcing TLS 1.2 max to fix DataImpulse residential IP handshake failures 2026-07-10 10:48:56 +00:00
__init__.py
booking_scraper.py Retry page load timeouts: treat as blocks, bump max retries to 4 2026-07-10 02:19:16 +00:00
central_settings.py
direct_scraper.py Extract shared proxy module; make it available to direct scraper; remove dead code 2026-07-05 22:55:24 +00:00
newbook_rates_client.py
proxy.py Block images via Chrome flag, not route interception; restore DataImpulse URL auth 2026-07-10 09:14:36 +00:00