Latest updates and improvements to FourA
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.
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.
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.
Pick a new period on Overview while the cards are still loading, and they now show that period's numbers, Auto attempts included. The period dialog also opens on the period you're viewing.
Auto now hands back a JSON page in data as text, whichever route fetched it, so the same parsing code works on every call.
The Chrome extension re-applies your proxy user's credentials after a browser restart or an update, so pages through the tunnel keep loading without a password prompt from Chrome.
Your organization page lists its pending invitations as soon as it opens, so a reload shows everyone you've invited who hasn't accepted yet.
Ask Browser for a URL with #reviews on the end and the page comes back at normal speed. If anchored links were coming back as timeouts on you, that's gone.
Browser now solves Cloudflare's checkbox challenge on concurrent requests to the same page, and a press only counts once the challenge is really gone. Three requests at once clear in 5 to 9 seconds.
Playground now renders the response from your target, including on sites that set large cookies, and API endpoints always answer in JSON.
If your target redirected to a different URL path, Browser used to return 'No response received' even though the page arrived. That's fixed; the request follows the navigation wherever it lands. eBay, redirect-heavy shops, and anything with a 3xx to a challenge page all work now.
A service now counts as down only when it has lost every instance, the one state where your request has nowhere to land. Routine rolling deploys no longer show up as incidents on the status page.
When your bank asked for 3D Secure on a plan upgrade, the request would poll for a change that never arrived (nobody had prompted you to authenticate). The change-plan flow now handles the extra step like the first subscribe does, so the upgrade goes through.
Browser now handles a challenge page that redirects before its body can be read, so requests to protected sites come back with content instead of an empty response.
When you send a header on Single or Proxy requests with the unblocker on (default), your value now reaches the origin as sent. Common headers like Accept and User-Agent could go out twice, and some upstreams picked the wrong one. If you noticed Accept: application/json coming back as XML, or a pinned User-Agent not being honored, that's fixed.
