hotel-manage-stack/rates
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Try forcing TLS 1.2 max to fix DataImpulse residential IP handshake failures

Browse source 
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>
This commit is contained in:
jtricerolph 2026-07-10 10:48:56 +00:00
parent ef7c4790ca
commit 46eada16a3
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
backend/services/scraper_backends/playwright_hotel_page.py
View file

@ -229,6 +229,10 @@ class PlaywrightHotelPageBackend(ScraperBackend):
'--disable-infobars', '--disable-infobars',
'--disable-extensions', '--disable-extensions',
'--blink-settings=imagesEnabled=false', '--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',
], ],
) )