jtricerolph b44e688b3e Retry page load timeouts: treat as blocks, bump max retries to 4 ... DataImpulse endpoints are intermittently broken — some return EOF after CONNECT immediately, others work fine. DNS round-robins between them so the same request can fail 3× then succeed on the 4th. Timeouts were returning blocked=False and silently failing with no retry. Now treated as retryable blocks (with context rotation) so a fresh endpoint is tried. Max retries 2→4 (5 total attempts) to give enough chances to land a working DataImpulse endpoint. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-07-10 02:19:16 +00:00
..
direct_profiles	Add Rate Monitor app — Booking.com + direct booking engine competitor rates	2026-07-05 12:06:30 +00:00
scraper_backends	Retry page load timeouts: treat as blocks, bump max retries to 4	2026-07-10 02:19:16 +00:00
__init__.py	Add Rate Monitor app — Booking.com + direct booking engine competitor rates	2026-07-05 12:06:30 +00:00
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	Add Rate Monitor app — Booking.com + direct booking engine competitor rates	2026-07-05 12:06:30 +00:00
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	Port occupancy sync + category ordering from the forecasting version	2026-07-05 14:18:03 +00:00
proxy.py	Revert proxy auth change — URL-embedded credentials are correct	2026-07-10 02:16:04 +00:00