Fix Waze address lookup and routing 403s - #108
Merged
Merged
Conversation
Use Waze mobile autocomplete for address resolution and retry routing HTTP 403 responses with a Chrome-impersonating curl-cffi session. Amp-Thread-ID: https://ampcode.com/threads/T-01a0f41c-a1da-7482-af06-5d28aa7bfe6c Co-authored-by: Kevin Stillhammer <kevin.stillhammer@tado.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolve addresses directly through Waze’s mobile autocomplete endpoint using the configured region and coordinate bias. Keep HTTPX as the first routing transport and retry HTTP 403 responses once with a Chrome-impersonating curl-cffi session, preserving routing parameters and full segment responses.
Public method signatures and result types remain unchanged. Autocomplete uses ranked coordinate-bearing predictions and returns no endpoint bounds, so address matches may differ and stop_at_bounds cannot exclude segments around autocomplete-resolved endpoints. The fallback session does not inherit injected HTTPX transport, proxy, cookie, or certificate settings.
Amp thread: https://ampcode.com/threads/T-01a0f41c-a1da-7482-af06-5d28aa7bfe6c