N
Nathan
We are encountering strange errors using IE 6 with a specified
automatic configuration script and an internal ASP.NET application.
The application performs very oddly throwing JavaScript errors all
over the place. The JS errors are all in the built in .NET
JavaScripts: wwwroot\aspnet_client\system_web\1_0_3705_288\WebUIValidation.js
and
wwwroot\aspnet_client\system_web\1_0_3705_288\SmartNav.js
most of them are "Permission denied" errors.
If you disable the automatic configuration script in IE>Connections no
problems AND if you use the automatic configuration script in a
mozilla.org browser ... no problems (ain't that irony). The goal of
the automatic configuration script is to attach users to actual usage
instead of just an IP address. Our IS networking group specify in the
script that internal servers should not be sent through the cache
server including the dotnet server in question.
Specified automatic configuration script (declassified)
http://cache-server.company.name:port_number/proxy.pac
script contents of proxy.pac (also declassified):
function FindProxyForURL(url, host)
{
if (isPlainHostName(host) ||
dnsDomainIs(host,".company.name.stuff") ||
dnsDomainIs(host,"dotnet_server_name.company.name.stuff")
||
isInNet(host,"127.0.0.0","255.255.255.0") ||
isInNet(host,"10.0.0.0","255.0.0.0") ||
isInNet(host,"172.16.0.0","255.240.0.0") ||
isInNet(host,"192.168.0.0","255.255.0.0")
) {
return "DIRECT";
}
else if (url.substring(0,5) == "http:" ||
url.substring(0,6) == "https:" ||
url.substring(0,4) == "ftp:") {
return "PROXY cache-server.company.nameort_number";
}
else {
return "DIRECT";
}
}
This appears to be a dotnet/IE bug? any suggestions? The automatic
configuration script must ultimately be used.
automatic configuration script and an internal ASP.NET application.
The application performs very oddly throwing JavaScript errors all
over the place. The JS errors are all in the built in .NET
JavaScripts: wwwroot\aspnet_client\system_web\1_0_3705_288\WebUIValidation.js
and
wwwroot\aspnet_client\system_web\1_0_3705_288\SmartNav.js
most of them are "Permission denied" errors.
If you disable the automatic configuration script in IE>Connections no
problems AND if you use the automatic configuration script in a
mozilla.org browser ... no problems (ain't that irony). The goal of
the automatic configuration script is to attach users to actual usage
instead of just an IP address. Our IS networking group specify in the
script that internal servers should not be sent through the cache
server including the dotnet server in question.
Specified automatic configuration script (declassified)
http://cache-server.company.name:port_number/proxy.pac
script contents of proxy.pac (also declassified):
function FindProxyForURL(url, host)
{
if (isPlainHostName(host) ||
dnsDomainIs(host,".company.name.stuff") ||
dnsDomainIs(host,"dotnet_server_name.company.name.stuff")
||
isInNet(host,"127.0.0.0","255.255.255.0") ||
isInNet(host,"10.0.0.0","255.0.0.0") ||
isInNet(host,"172.16.0.0","255.240.0.0") ||
isInNet(host,"192.168.0.0","255.255.0.0")
) {
return "DIRECT";
}
else if (url.substring(0,5) == "http:" ||
url.substring(0,6) == "https:" ||
url.substring(0,4) == "ftp:") {
return "PROXY cache-server.company.nameort_number";
}
else {
return "DIRECT";
}
}
This appears to be a dotnet/IE bug? any suggestions? The automatic
configuration script must ultimately be used.