Latest updates and improvements to FourA
Your Dashboard's Usage table has a new Routes view: see your requests split across Single, Proxy Finder, Browser and Auto, per API key, client IP or domain. For Auto calls it shows what ran behind each one and which step answered, so you can tell where your credits go.
Send several Browser requests to the same site at once and any that arrive while every slot is busy now wait up to 10 seconds for one to open. Auto's browser steps queue the same way, so concurrent bursts to the same page get served in turn.
When a site rate-limits one of the proxies behind your request, Auto now rests that proxy for that site alone and keeps using it everywhere else. A single site under pressure no longer holds up your requests to it, and Auto keeps looking for a working path instead of waiting.
Auto now accepts exitClass, as Proxy Finder does: premium lets a page the standard pool can't reach open in a browser through a premium exit, counted against your plan's premium traffic, and standard keeps it off them. meta.exitClass and the X-FourA-Exit-Class header name the class that delivered. The Playground and MCP foura_auto have it too.
When several calls start on a site Auto has no session for, one of them builds it and the others wait to reuse it. That wait now happens only among your own calls, never on another customer's call.
When a site answers with DataDome's device check, Browser now waits for the check to finish and the page to reload itself, and returns the page it leads to. If the check does not let the browser through, Browser returns the check page after the wait.
Some exits sit behind a company network gateway that answers every request with its own login redirect. Single, Proxy Finder and Auto now treat that page as a failed attempt and move on, as they already did for two other gateways.
When Amazon answers with its one-button "Continue shopping" page, Single and Browser now press the button on the same exit and return the product page. Proxy Finder and Auto calls get the same.
When a site turns away every exit Auto tries, Browser included, the call now ends after a few attempts. On a site Proxy Finder has served before, Auto asks Proxy Finder for the page first, and that search costs nothing if it comes back empty.
When a site answers with an AWS WAF challenge page, Browser now waits for the page to reload itself and returns what it leads to. Auto hands such pages to Browser on the same exit, so the call ends with the site's content.
On a phone or a narrow window, the Playground now scrolls the response into view as soon as it arrives. You see the result of Send without scrolling past the request options.
Send cookies named __Secure- or __Host- back to Browser, say from an earlier call, and it now sets them with the attributes their prefix requires, so the page sees your whole saved session.
If you pass your own proxy URL to Single or Browser and its hostname doesn't resolve, the answer is now status 0 with an error naming the host, the same as for a target. A proxy on a private address still gets the 400 refusal.
When a page sends itself to another address after loading, Browser follows it and returns the page it lands on instead of waiting out your timeout. It also waits through Google's short JavaScript check and returns the page it leads to.
An invoice we issue by hand for your account now shows up in Invoices beside the automatic ones. It's addressed from your Billing details and gets the same VAT treatment as every other invoice.
