Skip to content

fix: use fresh Chrome sessions for Waze fallback requests - #111

Merged
eifinger merged 1 commit into
mainfrom
fix/waze-fresh-sessions
Oct 7, 2026
Merged

eifinger merged 1 commit into
mainfrom
fix/waze-fresh-sessions

Conversation

@eifinger

@eifinger eifinger commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Fixes #110.

Use a fresh AsyncSession(impersonate="chrome") for each HTTPX 403 fallback request instead of retaining a session with the pinned chrome136 fingerprint. Apply the same fallback to address lookup, close sessions after each request, and preserve injected HTTPX client ownership.

Add regression coverage for session freshness, request options, fallback conditions, and cleanup/error handling.

Amp thread: https://ampcode.com/threads/T-01a11536-7b47-725c-b2d9-c8e44184c3ba

Use floating Chrome impersonation and a request-scoped curl session for routing and address lookup fallbacks.

Fixes #110

Amp-Thread-ID: https://ampcode.com/threads/T-01a11536-7b47-725c-b2d9-c8e44184c3ba
Co-authored-by: Kevin Stillhammer <kevin.stillhammer@tado.com>
@eifinger eifinger added the bugfix Fix for an existing bug label Oct 7, 2026
@eifinger
eifinger merged commit e115e00 into main Oct 7, 2026
4 checks passed
@eifinger
eifinger deleted the fix/waze-fresh-sessions branch October 7, 2026 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Fix for an existing bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Routing 403 again: Waze now rejects the pinned impersonate="chrome136" fingerprint (1.2.3)

2 participants