• jan.nijtmans logicacmg.com Nov 11 2005
• Dan <Dan_member pathlink.com> Nov 11 2005
• jan.nijtmans logicacmg.com Nov 14 2005

jan.nijtmans logicacmg.com writes:

After installing DMDscript using the instructions at
http://www.digitalmars.com/dscript/cppscript.html
IE6.0.2800.1106CO (Windows2000, fully up to date with the
latest patches) couldn't connect through the proxy any more.
The message is "Cannot connect through server". IE was set up
to use automatic proxy configuration through a file named
"proxy.pac", which contains something like:

function FindProxyForURL(url, host) {
if (isPlainHostName(host) ||
isInNet(host, "10.0.0.0", "255.0.0.0"))
return "DIRECT";
if (isInNet(myIpAddress(), "10.0.0.0", "255.0.0.0"))
return "PROXY myproxy:80";
return "DIRECT";
}

When manually setting the proxy to myproxy:80, IE could
connect through the proxy again. (workaround)

Because proxy.pac uses javascript, I assume that this file
is now handled by DMDscript as well, which - for some reason -
doesn't work. No error message is shown, except that any
attempt to connect to a site through the proxy gives a
"Cannot connect to server" error message.

Regards,
Jan Nijtmans

Dan <Dan_member pathlink.com> writes:

function FindProxyForURL(url, host) {
if (isPlainHostName(host) ||
isInNet(host, "10.0.0.0", "255.0.0.0"))
return "DIRECT";
if (isInNet(myIpAddress(), "10.0.0.0", "255.0.0.0"))
return "PROXY myproxy:80";
return "DIRECT";
}


I'm honestly not sure and I'm definitely not on the DMDScript payroll, but this
may have to do with the ActiveXObject support?  My understanding is that
Microsoft is changing their support for some COM objects because of their switch
to the "Firewall" API in order to feign greater security so they may have
introduced the bug themselves.  Or it may use some weird JScript bug in one of
the functions being called in FindProxyForURL.  If you wanted to dig into it
yourself, you could test types for isInNet(), myIpAddress() and you might just
find the problem.

My understanding is that Walter (the author) is otherwise indisposed and not
paying any attention to DMDScript so you're probably out of luck on getting
help.  I'm working on getting the ds.exe arguments working in some fashion.  

I made real progress and understand the problem and could explain it in detail,
but I can't get the freakin' thing to compile because it chokes on the first
file with changes (it doesn't recognize changed function signatures/symbols etc
because it hasn't parsed all the files yet)  I'm reading the dmd.exe
documentation now.  :p

jan.nijtmans logicacmg.com writes:

In article <dl2d0n$n53$1 digitaldaemon.com>, Dan says...
I'm honestly not sure and I'm definitely not on the DMDScript payroll, but
this may have to do with the ActiveXObject support?  My understanding is
that Microsoft is changing their support for some COM objects because of
their switch to the "Firewall" API in order to feign greater security so
they may have introduced the bug themselves.


Or it may use some weird JScript bug in one of the functions being called
in FindProxyForURL.  If you wanted to dig into it yourself, you could test
types for isInNet(), myIpAddress() and you might just find the problem.


function FindProxyForURL(url, host) {
return "PROXY myproxy:80";
}
but that didn't help. So the named functions are surely not the problem.

Regards,
Jan Nijtmans