Smarter Routing and Proxy Safety
This release introduces smarter network routing to bypass poor IP reputations and ensures reliable in-place challenge handling. We have also corrected key proxy behaviors across our SDKs and batch endpoints to prevent accidental direct routing.
The platform now uses real-time network reputation data to select the cleanest connection routes. By avoiding failing network paths, your scrapers will experience higher reliability and fewer IP blocks.
The scraper now handles verification challenges that resolve in-place via dynamic page updates. This ensures successful data extraction from highly protected sites without requiring full-page reloads.
Improvements
4Smarter IP Network Routing
The platform now uses real-time network reputation data to select the cleanest connection routes. By avoiding failing network paths, your scrapers will experience higher reliability and fewer IP blocks.
In-Place Security Challenge Solving
The scraper now handles verification challenges that resolve in-place via dynamic page updates. This ensures successful data extraction from highly protected sites without requiring full-page reloads.
Smarter Scrape Result Caching
The cache engine now records your exact proxy choices when saving successful results. This prevents cached proxied responses from being mistakenly returned to subsequent direct requests.
General bug fixes and improvements
Plus 4 internal improvements for better reliability and performance.
Bug Fixes
4Consistent Proxy Intent in SDKs
The SDKs and batch endpoints now correctly distinguish between omitting proxy options and setting them to false. This restores full control, letting you safely utilize automatic system proxies.
Automatic Proxy Escalation Fixed
We resolved a routing bug where omitting the proxy option was treated as a direct request. This allows the API to automatically escalate and route requests through system proxies when facing page blocks.
Forced JavaScript Rendering Preserved
Explicit requests for JavaScript rendering are now strictly honored and will not be overridden. This guarantees that your dynamic pages are always fully rendered using a browser engine when specified.
Accurate Challenge Solving Metrics
We resolved an issue where the API could occasionally report success while a verification challenge was still active. The system now verifies that the target content has fully loaded before returning success.
Security
1Proxy Safety for Dedicated Paths
Geotargeting and sticky session settings are now strictly preserved across specialized rendering tasks. The API will also fail closed if a secure route lacks a configured proxy to prevent data leaks.
Plus 4 internal changes for stability and performance.