Proxy Auto-Config files, universally abbreviated to PAC files, and the browser support for them were first created by Netscape sometime between 1995 and 1996 to provide greater flexibility for forwarding web browser traffic through an upstream proxy server.
The capabilities of the era powered a user or IT administrator to configure a web browser to forward traffic through a proxy, explicitly defining a single proxy host, port, and a list of explicit exceptions or bypasses. While this was quite useful, such a configuration did not and still does not support failover between proxies and lacked any kind of intelligent traffic management, e.g. if a bypass contains an IP address of a server and a user entered a Fully-Qualified Domain Name (FQDN) that pointed to said IP address, there would be no match and the traffic would still go through the proxy.
Netscape implemented functions that provided the ability to build rules around the destination FQDN, URL, and IP address being accessed, as well as supporting functions for resolving an FQDN to an IP address, determining if an IP address falls with a specific subnet, as well as less-commonly used capabilities that supported rules based on date and time and device IP address. In addition, multiple proxy servers could be configured for redundancy and failover.
With these capabilities, a user or administrator could easily forward traffic to an upstream proxy, automatically bypass local network traffic, and implement failover between proxy servers.