Reload Chrome's PAC or Clear Bad Proxies?
Re-apply settings refreshes configuration; Clear bad proxies removes remembered endpoint failures influencing fallback.
Open chrome://net-internals/#proxy and choose the action matching the problem:
| Action | State affected |
|---|---|
| Re-apply settings | Requests reloading proxy configuration, including the PAC source |
| Clear bad proxies | Clears remembered proxy failures affecting fallback order |
After reapplying, make a new request and inspect its route. Another tab alone does not guarantee a fresh PAC fetch, and page-cache state is separate.
Keep the controlling source in view: system settings, explicit PAC URL, policy or extension. Reapplying cannot correct a mistaken assumption about that source.
For unclear results, capture chrome://net-export/ events for PAC fetch/evaluation, resolved candidates and fallback. A button succeeding proves neither valid script nor reachable endpoint; reuse can also avoid a new route decision.