Url Pac Proxy Wifi - BilderUpload

How to set an Android proxy server for Wi-Fi: All you need to …

Do you have to use a Wi-Fi proxy server for Android to access the Internet at school or work? Or maybe you decided to configure an Android proxy server to protect your online privacy. Proxy servers are practical tools that act as intermediaries between you and the rest of the Internet, and it’s easy to configure using one. This tutorial illustrates how to set a Wi-Fi proxy server for Android smartphones and tablets:
NOTE: This guide applies to Android 10, and it was created using Nokia 5. 3 and Samsung Galaxy A51. If you do not know your Android version, read How to check the Android version on your smartphone or tablet. The procedures are similar on most Android-powered devices, although you might come across some small differences, depending on your device’s manufacturer. If you’re using a Samsung smartphone, the Android proxy settings are somewhat different, so don’t miss the dedicated chapter towards the end of this guide.
First things first: About Android proxy settings for Wi-Fi networks
You can use a Wi-Fi proxy server to protect your identity online or access the Internet when you are in a business network. While using the Android proxy, websites don’t identify your specific device, but rather the proxy server you have set for the Wi-Fi connection. If you want to learn more, we already explained, in great detail, what a proxy server is.
Even if you need to use the same Android proxy settings for different Wi-Fi networks, you must set them up one by one. To configure the Wi-Fi proxy settings, Android requires slightly different steps, depending on whether you’re setting the proxy server for an existing connection or a new one. Don’t worry, though; your Android smartphone or tablet remembers the proxy server associated with every Wi-Fi connection, so you only have to do this once. Your network administrator or proxy provider should give you the necessary details to connect.
Wi-Fi proxy settings on Android
If you’re wondering how to run Android apps on proxy Wi-Fi, the answer is a bit more complicated, and it all comes down to how each app was designed. Some apps are programmed to use the Android proxy settings, some, like browsers, can have their individual proxy settings, while others ignore Wi-Fi proxy settings altogether. That is why you could encounter certain apps that don’t work with your proxies. Unfortunately, if an app is not designed to use the Android proxy settings, there is no way to force it.
TIP: If you’re concerned about online privacy and security, you might also be interested to know When to use a proxy and when to use a VPN?.
How to set an Android proxy server for your Wi-Fi network
You can change the Wi-Fi proxy settings on Android to use a specific proxy server each time you connect to a network. As you’re about to see, the steps are similar, whether you’re setting up the proxy for the network you’re currently using or configuring a new connection. To begin, open the Settings app and tap on Network & Internet.
Access Network & Internet from Android Settings
Next, access Wi-Fi to see available wireless networks.
NOTE: To continue from this point, Wi-Fi must be active on your Android device.
Tap on Wi-Fi
You are shown a list of all the Wi-Fi networks that are available in your area. Depending on whether you’re setting the proxy server for an existing connection or a new one, accessing a network’s Advanced options is slightly different. Press the name of the network whose Wi-Fi proxy settings you want to change.
Tap on any network to change its Wi-Fi proxy settings on Android
If it’s a new network, you can now see the Advanced options in the pop-up window requesting a password. Skip the next paragraph and scroll down to the image matching the screen you see.
However, if you’re already connected to that network and tapped on the first entry during the previous step, the next screen shows your Wi-Fi connection’s Network details. Tap on the Edit button in the top-right corner. Its icon looks like a pencil.
Press the pencil button to Edit details about your Wi-Fi network
Either way, in the pop-up window showing your network’s name on top and requesting a password, tap on Advanced options to open a dropdown menu.
TIP: If this is a new Wi-Fi network, you also have to insert a password for it on this screen. Otherwise, the password field shows (unchanged), as seen below.
Access Advanced options to set a Wi-Fi proxy server for Android
The Advanced options expand, revealing the Proxy setting, which displays its default, None, and a down arrow. Tap on it to open the options for configuring the Android proxy server.
In the Proxy section, use the arrow to open a dropdown menu
The resulting menu has three options: None, Manual, and Proxy Auto-Config. Choose whether you want to manually enter the Wi-Fi proxy server or use a proxy auto-configuration address.
Select the configuration type you want
If you choose Manual, the pop-up window reveals three additional fields. Under Proxy hostname, enter either the hostname of the proxy server that you want to use (in the suggested format:) or its IP address.
Enter a proxy hostname
Then, you need to enter the port (the default used by most HTTP proxy servers is 8080). You can also “Bypass proxy for” certain websites if you insert their addresses.
When you’re done setting everything up, tap the option in the bottom-right corner of the pop-up to apply your changes. For existing networks, you must tap on Save, as seen above. For new networks, press Connect, as shown in the next image.
Press Connect or Save to apply your changes
If you choose Proxy Auto-Config, you get access to the PAC URL field. The value that you enter should follow the format:
Proxy Auto-Config only shows the PAC URL option
Enter the URL (web address) for that proxy or its configuration script (PAC file) and tap the button in the lower-right corner of the pop-up. For new networks, tap on Connect, as shown in the screenshot above. Press Save for an existing network, as seen below.
Press Save or Connect to apply your changes
From now on, each time it’s connected to the selected Wi-Fi network, your Android smartphone or tablet uses the proxy server you configured.
How to set a Wi-Fi proxy server for Android on Samsung devices
Samsung has slightly different Wi-Fi proxy settings on their Android devices. Open Settings and tap on Connections.
Access Connections on Samsung Galaxy
Tap the first option on the screen, Wi-Fi.
NOTE: The Wi-Fi option has to be enabled on your Samsung Android if you want to continue.
Access Wi-Fi to see available networks
You are shown a list of all the available Wi-Fi networks. The Current network is displayed on top. Depending on whether you’re setting the proxy server for an existing connection or a new one, accessing a network’s Advanced settings is slightly different. Press on the gear icon next to your Current network or on any of the available connections from the list underneath.
Select a network or use the gear icon next to the Current network
Depending on what you chose, the following screen has different settings, but, in both cases, you should press the Advanced option at the bottom. You can finally see the Proxy setting for the selected network on the next screen. Tap on its default value, None, to reveal other options for configuring the Android proxy server.
Press None to open a dropdown menu
Choose whether you want to manually enter the Wi-Fi proxy server or use a proxy auto-configuration address.
Select a configuration type from the available options
The Manual option reveals five additional fields, but only the first two are required to set up the Android proxy server: under “Proxy host name, ” enter either the hostname of the server you want to use (in the suggested format:) or its IP address; enter a port under Proxy port – the default used by most proxy servers is 8080). Optionally, you can specify web pages to bypass the proxy and establish a direct connection to the web page. Fill in the User name and Password fields if these details are required.
Insert the proxy details and our credentials for it, if required
When you’re done setting everything up, press Save to apply your changes, as seen below.
Tap on Save to use the new Wi-Fi proxy settings
If you choose the Auto-Config setting for your proxy server, you are required to insert the “PAC web address. ” Enter the URL for that proxy or its configuration script, and then tap on Save.
Insert the PAC URL and Save
You are returned to the previous screen. If you’re setting a proxy for a new Wi-Fi network on your Samsung Android, don’t forget to insert a password and press Connect, as seen below.
Finish connecting to a new Wi-Fi network to use the proxy
That was it! Your Android smartphone or tablet should use the proxy server you configured each time it’s connected to the Wi-Fi network.
Why do you use a Wi-Fi proxy server on your Android smartphone or tablet?
Most Android owners only use a Wi-Fi proxy server on their devices if it’s required to access the internet on a business or school network. However, there are users who think of it as a good way to protect their online identity and avoid giving away their location. What about you? Why did you decide to use a Wi-Fi proxy server? Let us know in the comments.

Proxy auto-config – Wikipedia

This article is about the browser file. For other uses, see PAC.
A proxy auto-config (PAC) file defines how web browsers and other user agents can automatically choose the appropriate proxy server (access method) for fetching a given URL.
A PAC file contains a JavaScript function FindProxyForURL(url, host). This function returns a string with one or more access method specifications. These specifications cause the user agent to use a particular proxy server or to connect directly.
Multiple specifications provide a fall-back when a proxy fails to respond. The browser fetches this PAC file before requesting other URLs. The URL of the PAC file is either configured manually or determined automatically by the Web Proxy Auto-Discovery Protocol.
Context[edit]
Modern web browsers implement several levels of automation; users can choose the level that is appropriate to their needs. The following methods are commonly implemented:
Automatic proxy selection: Specify a host-name and a port number to be used for all URLs. Most browsers allow you to specify a list of domains (such as localhost) that will bypass this proxy.
Proxy auto-configuration (PAC): Specify the URL for a PAC file with a JavaScript function that determines the appropriate proxy for each URL. This method is more suitable for laptop users who need several different proxy configurations, or complex corporate setups with many different proxies.
Web Proxy Auto-Discovery Protocol (WPAD): Let the browser guess the location of the PAC file through DHCP and DNS lookups.
History[edit]
The Proxy auto-config file format was originally designed by Netscape in 1996 for the Netscape Navigator 2. 0[1] and is a text file that defines at least one JavaScript function.
The PAC File[edit]
By convention, the PAC file is normally named The WPAD standard uses The file is expected to contain at least one function:
FindProxyForURL(url, host), with two arguments and return value in specific format:
* url is the URL of the object
* host is the host-name derived from that URL. Syntactically it is the same string as between and the first: or / after that. [2]
* return “… ” is a string of signatures in the following format (EBNF notation, see examples below):
returnValue = type host, “:”, port, [{ “;”, returnValue}];
type = “DIRECT” | “PROXY” | “SOCKS” | “HTTP” | “HTTPS” | “SOCKS4” | “SOCKS5″
host = UTF16String (* ECMA262-compatible UTF16 string *)
port = UTF16String (* Digits *)
To use it, a PAC file is published to a HTTP server, and client user agents are instructed to use it, either by entering the URL in the proxy connection settings of the browser or through the use of the WPAD protocol. The URL may also reference a local file as for example: file/etc/
Even though most clients will process the script regardless of the MIME type returned in the HTTP reply, for the sake of completeness and to maximize compatibility, the HTTP server should be configured to declare the MIME type of this file to be either application/x-ns-proxy-autoconfig or application/x-javascript-config.
There is little evidence to favor the use of one MIME type over the other. It would be, however, reasonable to assume that application/x-ns-proxy-autoconfig will be supported in more clients than application/x-javascript-config as it was defined in the original Netscape specification, the latter type coming into use more recently.
Example[edit]
A very simple example of a PAC file is:
function FindProxyForURL (url, host) {
return ‘PROXY; DIRECT’;}
This function instructs the browser to retrieve all pages through the proxy on port 8080 of the server Should this proxy fail to respond, the browser contacts the Web-site directly, without using a proxy. The latter may fail if firewalls, or other intermediary network devices, reject requests from sources other than the proxy—a common configuration in corporate networks.
A more complicated example demonstrates some available JavaScript functions to be used in the FindProxyForURL function:
// our local URLs from the domains below don’t need a proxy:
if (shExpMatch(host, ‘*. ‘)) {
return ‘DIRECT’;}
// URLs within this network are accessed through
// port 8080 on
if (isInNet(host, ’10. 0. 0′, ‘255. 255. 248. 0’)) {
return ‘PROXY ‘;}
// All other requests go through port 8080 of
// should that fail to respond, go directly to the WWW:
By default, the PROXY keyword means that a proxy corresponding to the protocol of the original request, be it,, or ftp, is used. Other supported keyword and proxy types include:
SOCKS
Use a SOCKS proxy.
HTTP, HTTPS
Introduced in more recent versions of Firefox. Specifies an HTTP(S) proxy.
SOCKS4, SOCKS5
Introduced in more recent versions of Firefox. Specifies the SOCKS protocol version.
Limitations[edit]
PAC Character-Encoding[edit]
The encoding of PAC scripts is generally unspecified, and different browsers and network stacks have different rules for how PAC scripts may be encoded. In general, wholly ASCII PAC scripts will work with any browser or network stack. Mozilla Firefox 66 and later additionally supports PAC scripts encoded as UTF-8. [3]
DnsResolve[edit]
The function dnsResolve (and similar other functions) performs a DNS lookup that can block the browser for a long time if the DNS server does not respond.
myIpAddress[edit]
The myIpAddress function has often been reported to give incorrect or unusable results, e. g. 192. 168. 1. 128, the IP address of the localhost.
It may help to remove on the system’s host file (e. /etc/hosts on Linux) any lines referring to the machine host-name, while the line 192. 1 localhost can, and should, stay. [citation needed]
Security[edit]
In 2013, researchers began warning about the security risks of proxy auto-config. [4] The threat involves using a PAC, discovered automatically by the system, to redirect the victim’s browser traffic to an attacker-controlled server instead.
Another issues about pac file is the typical implementation involve clear text retrieval, which does not include any security features such as code signing or web certificates. Attacker can perform man-in-middle spoofing attack easily.
Old Microsoft problems[edit]
Caching of proxy auto-configuration results by domain name in Microsoft’s Internet Explorer 5. 5 or newer limits the flexibility of the PAC standard. In effect, you can choose the proxy based on the domain name, but not on the path of the URL. Alternatively, you need to disable caching of proxy auto-configuration results by editing the registry, a process described by de Boyne Pollard (listed in further reading).
It is recommended to always use IP addresses instead of host domain names in the isInNet function for compatibility with other Windows components which make use of the Internet Explorer PAC configuration, such as 2. 0 Framework. For example,
if (isInNet(host, dnsResolve(sampledomain), ‘255. 0’)) {} // 2. 0 will resolve proxy properly
if (isInNet(host, sampledomain, ‘255. 0 will not resolve proxy properly
The current convention is to fail over to direct connection when a PAC file is unavailable.
Shortly after switching between network configurations (e. when entering or leaving a VPN), dnsResolve may give outdated results due to DNS caching.
For instance, Firefox usually keeps 20 domain entries cached for 60 seconds. This may be configured via the network. dnsCacheEntries and network. dnsCacheExpiration configuration variables. Flushing the system’s DNS cache may also help, which can be achieved e. in Linux with sudo service dns-clean start or in Windows with ipconfig /flushdns.
On Internet Explorer 9, isInNet(‘localHostName’, ”, ‘255. 255’) returns true and can be used as a workaround.
The myIpAddress function assumes that the device has a single IPv4 address. The results are undefined if the device has more than one IPv4 address or has IPv6 addresses.
Others[edit]
Further limitations are related to the JavaScript engine on the local machine.
Advanced functionality[edit]
More advanced PAC files can reduce load on proxies, perform load balancing, fail over, or even deny/allow listing before the request is sent through the network.
One can return multiple proxies:
return ‘PROXY; PROXY ‘;
The above will try proxy1 first and if unavailable it will then try proxy2.
References[edit]
^ “Navigator Proxy Auto-Config File Format”. Netscape Navigator Documentation. March 1996. Archived from the original on 2007-06-02. Retrieved 2013-07-05.
^ “Proxy Auto-Configuration (PAC) file – HTTP | MDN”.
^ “Bug 1492938 – Proxy autoconfig scripts should be loaded as UTF-8 if they are valid UTF-8, otherwise as Latin-1 (a byte is a code point)”. Retrieved 2019-04-10.
^ Lemos, Robert (2013-03-06). “Cybercriminals Likely To Expand Use Of Browser Proxies”. Retrieved 2016-04-20.
Further reading[edit]
de Boyne Pollard, Jonathan (2004). “Automatic proxy HTTP server configuration in web browsers”. Frequently Given Answers. Retrieved 2013-07-05.
External links[edit]
“Proxy Auto-Configuration (PAC) file”. 2019-01-27.
“Using the Client Autoconfiguration File”. Netscape Proxy Server Administrator’s Guide: Chapter 11. 1998-02-25. Archived from the original on 2004-08-10.
“Chapter 26 – Using Automatic Configuration, Automatic Proxy, and Automatic Detection”. Microsoft TechNet. Retrieved 2013-07-05.
“Proxy Auto Config for Firefox (PAC). Fully working examples including anti-ad and anti-adult filter rules”. 2012-05-12. Archived from the original on 2015-07-01. Retrieved 2009-05-24.

Proxy Auto-Configuration (PAC) file – HTTP – MDN Web Docs

A Proxy Auto-Configuration (PAC) file is a JavaScript function that determines whether web browser requests (HTTP, HTTPS, and FTP) go directly to the destination or are forwarded to a web proxy server. The JavaScript function contained in the PAC file defines the function:
function FindProxyForURL(url, host) {
//… }
Syntaxfunction FindProxyForURL(url, host)
Parameters
url
The URL being accessed. The path and query components of URLs are stripped. In Chrome (versions 52 to 73), you can disable this by setting PacHttpsUrlStrippingEnabled to false in policy or by launching with the –unsafe-pac-url command-line flag (in Chrome 74, only the flag works, and from 75 onward, there is no way to disable path-stripping; as of Chrome 81, path-stripping does not apply to HTTP URLs, but there is interest in changing this behavior to match HTTPS); in Firefox, the preference is
host
The hostname extracted from the URL. This is only for convenience; it is the same string as between and the first: or / after that. The port number is not included in this parameter. It can be extracted from the URL when necessary.
DescriptionReturns a string describing the configuration. The format of this string is defined in return value format value format
The JavaScript function returns a single string
If the string is null, no proxies should be used
The string can contain any number of the following building blocks, separated by a semicolon:
DIRECT
Connections should be made directly, without any proxies
PROXY host:port
The specified proxy should be used
SOCKS host:port
The specified SOCKS server should be used
Recent versions of Firefox support as well:
HTTP host:port
HTTPS host:port
The specified HTTPS proxy should be used
SOCKS4 host:port, SOCKS5 host:port
The specified SOCKS server (with the specified SOCK version) should be used
If there are multiple semicolon-separated settings, the left-most setting will be used, until Firefox fails to establish the connection to the proxy. In that case, the next value will be used, etc.
The browser will automatically retry a previously unresponsive proxy after 30 minutes. Additional attempts will continue beginning at one hour, always adding 30 minutes to the elapsed time between attempts.
If all proxies are down, and there was no DIRECT option specified, the browser will ask if proxies should be temporarily ignored, and direct connections attempted. After 20 minutes, the browser will ask if proxies should be retried, asking again after an additional 40 minutes. Queries will continue, always adding 20 minutes to the elapsed time between queries.
Examples
PROXY; PROXY
Primary proxy is w3proxy:8080; if that goes down start using mozilla:8081 until the primary proxy comes up again.
PROXY; PROXY; DIRECT
Same as above, but if both proxies go down, automatically start making direct connections. (In the first example above, Netscape will ask user confirmation about making direct connections; in this case, there is no user intervention. )
PROXY; SOCKS socks:1080
Use SOCKS if the primary proxy goes down.
The auto-config file should be saved to a file with a filename extension:
And the MIME type should be set to:
application/x-ns-proxy-autoconfig
Next, you should configure your server to map the filename extension to the MIME type.
Note:
The JavaScript function should always be saved to a file by itself but not be embedded in a HTML file or any other file.
The examples at the end of this document are complete. There is no additional syntax needed to save it into a file and use it. (Of course, the JavaScripts must be edited to reflect your site’s domain name and/or subnets. )
Predefined functions and environmentThese functions can be used in building the PAC file:
Hostname based conditions
isPlainHostName()
dnsDomainIs()
localHostOrDomainIs()
isResolvable()
isInNet()
Related utility functions
dnsResolve()
convert_addr()
myIpAddress()
dnsDomainLevels()
URL/hostname based conditions
shExpMatch()
Time based conditions
weekdayRange()
dateRange()
timeRange()
Logging utility
alert()
There was one associative array (object) already defined, because at the time JavaScript code was unable to define it by itself:
ndings
Note: pactester (part of the pacparser package) was used to test the following syntax examples.
The PAC file is named
Command line: pactester -p ~/pacparser-master/tests/ -u (passes the host parameter and the url parameter)
isPlainHostName()Syntax
The hostname from the URL (excluding port number).
Description
True if and only if there is no domain name in the hostname (no dots).
isPlainHostName(“) // false
isPlainHostName(“www”) // true
dnsDomainIs()Syntax
dnsDomainIs(host, domain)
Is the hostname from the URL.
domain
Is the domain name to test the hostname against.
Returns true if and only if the domain of hostname matches.
dnsDomainIs(“, “. “) // true
dnsDomainIs(“www”, “. “) // false
localHostOrDomainIs()Syntax
localHostOrDomainIs(host, hostdom)
The hostname from the URL.
hostdom
Fully qualified hostname to match against.
Is true if the hostname matches exactly the specified hostname, or if there is no domain name part in the hostname, but the unqualified hostname matches.
localHostOrDomainIs(“, “) // true (exact match)
localHostOrDomainIs(“www”, “) // true (hostname match, domain not specified)
localHostOrDomainIs(“, “) // false (domain name mismatch)
localHostOrDomainIs(“”, “) // false (hostname mismatch)
isResolvable()Syntax
is the hostname from the URL.
Tries to resolve the hostname. Returns true if succeeds.
isResolvable(“) // true
isInNet()Syntax
isInNet(host, pattern, mask)
a DNS hostname, or IP address. If a hostname is passed, it will be resolved into an IP address by this function.
pattern
an IP address pattern in the dot-separated format.
mask
mask for the IP address pattern informing which parts of the IP address should be matched against. 0 means ignore, 255 means match.
True if and only if the IP address of the host matches the specified IP address pattern.
Pattern and mask specification is done the same way as for SOCKS configuration.
function alert_eval(str) { alert(str + ‘ is ‘ + eval(str))}
alert_eval(‘isInNet(host, “63. 245. 213. 24”, “255. 255. 255”)’)
// “PAC-alert: isInNet(host, “63. 255″) is true”}
hostname to resolve.
Resolves the given DNS hostname into an IP address, and returns it in the dot-separated format as a string.
Example
dnsResolve(“); // returns the string “104. 16. 41. 2”
convert_addr()Syntax
ipaddr
Any dotted address such as an IP address or mask.
Concatenates the four dot-separated bytes into one 4-byte word and converts it to decimal.
convert_addr(“104. 2”); // returns the decimal number 1745889538
myIpAddress()Syntax
(none)
Return value
Returns the server IP address of the machine Firefox is running on, as a string in the dot-separated integer format.
Warning: myIpAddress() returns the same IP address as the server address returned by nslookup localhost on a Linux machine. It does not return the public IP address.
myIpAddress() //returns the string “127. 0. 1. 1” if you were running Firefox on that localhost
dnsDomainLevels()Syntax
Returns the number (integer) of DNS domain levels (number of dots) in the hostname.
dnsDomainLevels(“www”); // 0
dnsDomainLevels(“”); // 1
dnsDomainLevels(“); // 2
shExpMatch()Syntax
str
is any string to compare (e. g. the URL, or the hostname).
shexp
is a shell expression to compare against.
Returns true if the string matches the specified shell glob expression.
Support for particular glob expression syntax varies across browsers:
* (match any number of characters) and? (match one character) are always supported,
while [characters] and [^characters] are additionally supported by some implementations (including Firefox).
Note: If supported by the client, JavaScript regular expressions typically provide a more powerful and consistent way to pattern-match URLs (and other strings).
shExpMatch(“, “*/ari/*”); // returns true
shExpMatch(“, “*/ari/*”); // returns false
weekdayRange()Syntax
weekdayRange(wd1, wd2, [gmt])
Note: (Before Firefox 49) wd1 must be less than wd2 if you want the function to evaluate these parameters as a range. See the warning below.
wd1 and wd2
One of the ordered weekday strings: “SUN”, “MON”, “TUE”, “WED”, “THU”, “FRI”, “SAT”
gmt
Is either the string “GMT” or is left out.
Only the first parameter is mandatory. Either the second, the third, or both may be left out.
If only one parameter is present, the function returns a value of true on the weekday that the parameter represents. If the string “GMT” is specified as a second parameter, times are taken to be in GMT. Otherwise, they are assumed to be in the local timezone.
If both wd1 and wd1 are defined, the condition is true if the current weekday is in between those two ordered weekdays. Bounds are inclusive, but the bounds are ordered. If the “GMT” parameter is specified, times are taken to be in GMT. Otherwise, the local timezone is used.
Warning: The order of the days matters.
Before Firefox 49, weekdayRange(“SUN”, “SAT”) will always evaluate to true.
Now weekdayRange(“WED”, “SUN”) will only evaluate to true
if the current day is Wednesday or Sunday.
weekdayRange(“MON”, “FRI”); // returns true Monday through Friday (local timezone)
weekdayRange(“MON”, “FRI”, “GMT”); // returns true Monday through Friday (GMT timezone)
weekdayRange(“SAT”); // returns true on Saturdays local time
weekdayRange(“SAT”, “GMT”); // returns true on Saturdays GMT time
weekdayRange(“FRI”, “MON”); // returns true Friday and Monday only (note, order does matter! )
dateRange()Syntax
dateRange( | | , [gmt]) // ambiguity is resolved by assuming year is greater than 31
dateRange(, , [gmt])
dateRange(, , [gmt])
dateRange(, , [gmt])
dateRange(, , , , [gmt])
dateRange(, , , , [gmt])
dateRange(, , , , , , [gmt])
Note: (Before Firefox 49) day1 must be less than day2, month1 must be less than month2, and year1 must be less than year2 if you want the function to evaluate these parameters as a range. See the warning below.
day
Is the ordered day of the month between 1 and 31 (as an integer).
1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24|25|26|27|28|29|30|31
month
Is one of the ordered month strings below.
“JAN”|”FEB”|”MAR”|”APR”|”MAY”|”JUN”|”JUL”|”AUG”|”SEP”|”OCT”|”NOV”|”DEC”
year
Is the ordered full year integer number. For example, 2016 (not 16).
Is either the string “GMT”, which makes time comparison occur in GMT timezone, or is left out. If left unspecified, times are taken to be in the local timezone.
If only a single value is specified (from each category: day, month, year), the function returns a true value only on days that match that specification. If both values are specified, the result is true between those times, including bounds, but the bounds are ordered.
Warning: The order of the days, months, and years matter; Before Firefox 49, dateRange(“JAN”, “DEC”) will always evaluate to true. Now dateRange(“DEC”, “JAN”) will only evaluate true if the current month is December or January.
dateRange(1); // returns true on the first day of each month, local timezone
dateRange(1, “GMT”) // returns true on the first day of each month, GMT timezone
dateRange(1, 15); // returns true on the first half of each month
dateRange(24, “DEC”); // returns true on 24th of December each year
dateRange(“JAN”, “MAR”); // returns true on the first quarter of the year
dateRange(1, “JUN”, 15, “AUG”);
// returns true from June 1st until August 15th, each year
// (including June 1st and August 15th)
dateRange(1, “JUN”, 1995, 15, “AUG”, 1995);
// returns true from June 1st, 1995, until August 15th, same year
dateRange(“OCT”, 1995, “MAR”, 1996);
// returns true from October 1995 until March 1996
// (including the entire month of October 1995 and March 1996)
dateRange(1995);
// returns true during the entire year of 1995
dateRange(1995, 1997);
// returns true from beginning of year 1995 until the end of year 1997
timeRange()Syntax
// The full range of expansions is analogous to dateRange.
timeRange(, , , , , , [gmt])
Note: (Before Firefox 49) the category hour1, min1, sec1 must be less than the category hour2, min2, sec2 if you want the function to evaluate these parameters as a range. See the warning below.
hour
Is the hour from 0 to 23. (0 is midnight, 23 is 11 pm. )
min
Minutes from 0 to 59.
sec
Seconds from 0 to 59.
Either the string “GMT” for GMT timezone, or not specified, for local timezone.
If only a single value is specified (from each category: hour, minute, second), the function returns a true value only at times that match that specification. If both values are specified, the result is true between those times, including bounds, but the bounds are ordered.
Warning: The order of the hour, minute, second matter; Before Firefox 49, timeRange(0, 23) will always evaluate to true. Now timeRange(23, 0) will only evaluate true if the current hour is 23:00 or midnight.
timerange(12); // returns true from noon to 1pm
timerange(12, 13); // returns true from noon to 1pm
timerange(12, “GMT”); // returns true from noon to 1pm, in GMT timezone
timerange(9, 17); // returns true from 9am to 5pm
timerange(8, 30, 17, 00); // returns true from 8:30am to 5:00pm
timerange(0, 0, 0, 0, 0, 30); // returns true between midnight and 30 seconds past midnight
alert()Syntax
message
The string to log
Logs the message in the browser console.
alert(host + ” = ” + dnsResolve(host)); // logs the host name and its IP address
alert(“Error: shouldn’t reach this clause. “); // log a simple message
Example 1Use proxy for everything except local hostsNote: Since all of the examples that follow are very specific, they have not been tested.
All hosts which aren’t fully qualified, or the ones that are in local domain, will be connected to directly. Everything else will go through If the proxy goes down, connections become direct automatically:
if (isPlainHostName(host) || dnsDomainIs(host, “. “)) {
return “DIRECT”;} else {
return “PROXY; DIRECT”;}}
Note: This is the simplest and most efficient autoconfig file for cases where there’s only one proxy. Example 2As above, but use proxy for local servers which are outside the firewallIf there are hosts (such as the main Web server) that belong to the local domain but are outside the firewall and are only reachable through the proxy server, those exceptions can be handled using the localHostOrDomainIs() function:
if (
(isPlainHostName(host) || dnsDomainIs(host, “. “)) &&! localHostOrDomainIs(host, “) &&! localHostOrDomainIs(host, “”)) {
The above example will use the proxy for everything except local hosts in the domain, with the further exception that hosts and will go through the proxy.
Note: The order of the above exceptions for efficiency: localHostOrDomainIs() functions only get executed for URLs that are in local domain, not for every URL. Be careful to note the parentheses around the or expression before the and expression to achieve the above-mentioned efficient behavior. Example 3Use proxy only if cannot resolve hostThis example will work in an environment where the internal DNS server is set up so that it can only resolve internal host names, and the goal is to use a proxy only for hosts that aren’t resolvable:
if (isResolvable(host))
return “DIRECT”;
else
return “PROXY “;}
The above requires consulting the DNS every time; it can be grouped intelligently with other rules so that DNS is consulted only if other rules do not yield a result:
isPlainHostName(host) ||
dnsDomainIs(host, “. “) ||
isResolvable(host)) {
return “PROXY “;}}
Example 4Subnet based decisionsIn this example all of the hosts in a given subnet are connected-to directly, others are connected through the proxy:
if (isInNet(host, “198. 95. 0”, “255. 0”))
Again, use of the DNS server in the above can be minimized by adding redundant rules in the beginning:
isInNet(host, “198. 0”)) {
Example 5Load balancing/routing based on URL patternsThis example is more sophisticated. There are four (4) proxy servers; one of them is a hot stand-by for all of the other ones, so if any of the remaining three goes down the fourth one will take over. Furthermore, the three remaining proxy servers share the load based on URL patterns, which makes their caching more effective (there is only one copy of any document on the three servers – as opposed to one copy on each of them). The load is distributed like this:
Proxy
Purpose
#1
#2
#3
all other domains
#4
hot stand-by
All local accesses are desired to be direct. All proxy servers run on the port 8080 (they don’t need to, you can just change your port but remember to modify your configuations on both side). Note how strings can be concatenated with the + operator in JavaScript.
if (isPlainHostName(host) || dnsDomainIs(host, “. “))
else if (shExpMatch(host, “*”))
return “PROXY; ” +
“PROXY “;
“PROXY “;}
Example 6Setting a proxy for a specific protocolMost of the standard JavaScript functionality is available for use in the FindProxyForURL() function. As an example, to set different proxies based on the protocol the startsWith() function can be used:
if (artsWith(“:”))
return “PROXY “;
else if (artsWith(“ftp:”))
else if (artsWith(“gopher:”))
else if (artsWith(“:”) || artsWith(“snews:”))
return “DIRECT”;}
Note: The same can be accomplished using the shExpMatch() function described earlier.
For example:
//…
if (shExpMatch(url, “:*”)) {
Note: The autoconfig file can be output by a CGI script. This is useful, for example, when making the autoconfig file act differently based on the client IP address (the REMOTE_ADDR environment variable in CGI).
Usage of isInNet(), isResolvable() and dnsResolve() functions should be carefully considered, as they require the DNS server to be consulted. All the other autoconfig-related functions are mere string-matching functions that don’t require the use of a DNS server. If a proxy is used, the proxy will perform its DNS lookup which would double the impact on the DNS server. Most of the time these functions are not necessary to achieve the desired result.
History and implementationProxy auto-config was introduced into Netscape Navigator 2. 0 in the late 1990s, at the same time when JavaScript was introduced. Open-sourcing Netscape eventually lead to Firefox itself.
The most “original” implementation of PAC and its JavaScript libraries is, therefore, found in early versions of Firefox. These utilities are found in many other open-source systems including Chromium. Firefox later integrated the file into as a C++ string literal. To extract it into its own file, it suffices to copy the chunk into JavaScript with a directive to print it.
Microsoft in general made its own implementation. There used to be some problems with their libraries, but most are resolved by now. They have defined some new “Ex” suffixed functions around the address handling parts to support IPv6. The feature is supported by Chromium, but not yet by Firefox (bugzilla #558253).

Frequently Asked Questions about url pac proxy wifi

What is PAC URL in WiFi?

A proxy auto-config (PAC) file defines how web browsers and other user agents can automatically choose the appropriate proxy server (access method) for fetching a given URL. … The URL of the PAC file is either configured manually or determined automatically by the Web Proxy Auto-Discovery Protocol.

What is a proxy PAC URL?

How do I get a PAC URL?

PAC file addresses can be located on the Web > General page and on the General tab of a policy. In both locations, a default and alternate address is listed. Default PAC file address: the PAC file is retrieved over port 8082 by default, or 8087 for HTTPS.