The proxy server address may not be detected when you run an autoproxy script that contains the isInNet function in the .NET Framework 2.0 (922778)
The information in this article applies to:
- Microsoft .NET Framework 2
SYMPTOMSWhen you run an autoproxy script that contains the isInNet function, the proxy server address may not be
detected. This behavior occurs if the following conditions are
true: - You pass a string instead of a number as a parameter to the isInNet() function.
- You use multiple IP addresses for the host parameter.
- You use a Microsoft Internet Protocol version 6 (IPv6) for
the host parameter.
When you run an autoproxy script that contains
the isInNet function in the Microsoft .NET Framework 2.0, and the function
receives the host parameter as either a host name or as multiple IP addresses, it
does not resolve the IP address. Note In Microsoft Internet Explorer, both the host name and the IP address can be
used in the isInNet function in an autoproxy script to detect the proxy
server. WORKAROUND To work around this behavior, use the dnsResolve function to return an IP address that the isInNet function can use. For example, the following code does
not return the proxy server address if the host parameter is not an IP address. if(isInNet(host, "207.0.0.0", "255.0.0.0")) By using the dnsResolve function, the isInNet function always receives an IP address, as required. The
following code illustrates this method. if(isInNet(dnsResolve(host), "207.0.0.0", "255.0.0.0")) STATUS This
behavior is by design.
| Modification Type: | Major | Last Reviewed: | 9/22/2006 |
|---|
| Keywords: | kbProxyDev kbIP kbWebClasses kbScript kbRouting kbCodeSnippet kbtshoot kbprb KB922778 kbAudDeveloper kbAudITPRO |
|---|
|