rates/backend
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
..
api Fix proxy test: URL-encode httpx credentials, use Proxy object, improve error detail 2026-07-10 08:57:25 +00:00
jobs Fix bookability column timestamps showing stale 'last changed' dates 2026-07-10 08:41:58 +00:00
services Try forcing TLS 1.2 max to fix DataImpulse residential IP handshake failures 2026-07-10 10:48:56 +00:00
auth.py
database.py
Dockerfile Revert Firefox: root cause was broken DataImpulse nodes not fingerprinting 2026-07-10 09:54:50 +00:00
main.py
migrate_direct_data.py Restore guestline-monitor features: room stock/occupancy, rate history, room stats 2026-07-06 06:50:37 +00:00
requirements.txt
scheduler.py Scraper: force-reset endpoint + watchdog to prevent stuck lock 2026-07-09 16:56:35 +00:00
schema.sql Add hotel-page scraper backend with full room/rate plan extraction 2026-07-09 23:08:03 +00:00