Conventions used
There are a number of text conventions used throughout this book.
Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “The first if statement contains all the things that should not be sent to the proxy, indicated by return "DIRECT" at the end. “
A block of code is set as follows:
function FindProxyForURL(url, host) {/* Bypass localhost and Private IPs */var resolved_ip = dnsResolve(host);if (isPlainHostName(host) ||shExpMatch(host, "*.local") ||isInNet(resolved_ip, "10.0.0.0", "255.0.0.0") ||isInNet(resolved_ip, "172.16.0.0", "255.240.0.0" ||isInNet(resolved_ip, "192.168.0.0", "255.255.0.0") ||isInNet(resolved_ip, "127.0.0.0", "255.255.255.0"))return "DIRECT";/* Bypass FTP */if (url.substring(0,4) == "ftp:")return "DIRECT";/* Bypass SAML, e.g. Okta */if (shExpMatch(host, "*.okta.com") || shExpMatch(host, "*.oktacdn.com"))return "DIRECT";/* Bypass ACS */if (shExpMatch(host, "*.acs.prismaaccess.com"))return "DIRECT";/* Forward to Prisma Access */return "PROXY pangurus.proxy.prismaaccess.com:8080";}
Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “Our first step is to enable the explicit proxy in Workflows | Prisma Access Setup | Mobile Users. Click the Enable button next to Explicit Proxy.”
Tips or important notes
Appear like this.
