Web Security On-prem | PAC File Best Practices
  1. Home
  2. PAC File Best Practices
  3. PAC file best practices

  4. JavaScript functions most commonly used in a PAC file
  • PAC File Best Practices
    • Introduction
    • What is a PAC file?
    • How is a PAC file consumed?
    • Using a PAC file with Content Gateway
    • Using a PAC file with Forcepoint Web Security and the Forcepoint Web Security Hybrid Module
    • Sample PAC file
    • PAC file best practices

      • JavaScript best practices for PAC files
      • JavaScript functions most commonly used in a PAC file
        • isPlainHostName()
        • dnsDomainIs()
        • localHostOrDomainIs()
        • isResolvable()
        • isInNet()
        • dnsResolve()
        • myIpAddress()
        • dnsDomainLevels()
        • shExpMatch()
        • weekdayRange()
        • dateRange()
        • timeRange()
      • Potential PAC function issues

      • How do I restrict the browsers allowed in my network to only those that can be configured with a PAC or WPAD file?
      • How do I configure a Group Policy so that Internet Explorer uses the PAC file?
      • What is Internet Explorer Automatic Proxy Result Cache?
      • How do I specify a URL in a PAC file to bypass Content Gateway?

JavaScript functions most commonly used in a PAC file

From “PAC Functions Explained” (http://findproxyforurl.com/pac- functions)

  • isPlainHostName()
  • dnsDomainIs()
  • localHostOrDomainIs()
  • isResolvable()
  • isInNet()
  • dnsResolve()
  • myIpAddress()
  • dnsDomainLevels()
  • shExpMatch()
  • weekdayRange()
  • dateRange()
  • timeRange()

Copyright © 2024 Forcepoint LLC