From 46eada16a3684e66b803f8671f4a76ed6e839220 Mon Sep 17 00:00:00 2001 From: jtricerolph Date: Fri, 10 Jul 2026 10:48:56 +0000 Subject: [PATCH] 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 --- backend/services/scraper_backends/playwright_hotel_page.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/backend/services/scraper_backends/playwright_hotel_page.py b/backend/services/scraper_backends/playwright_hotel_page.py index 93d7328..feb4f33 100644 --- a/backend/services/scraper_backends/playwright_hotel_page.py +++ b/backend/services/scraper_backends/playwright_hotel_page.py @@ -229,6 +229,10 @@ class PlaywrightHotelPageBackend(ScraperBackend): '--disable-infobars', '--disable-extensions', '--blink-settings=imagesEnabled=false', + # Some DataImpulse residential IPs drop Chromium's TLS 1.3 + # GREASE/key_share extensions mid-handshake. Force TLS 1.2 + # to use a simpler handshake those IPs can handle. + '--ssl-version-max=tls1.2', ], )