Discussion:
InternetGetProxyInfo fails on IE7-machine, but works on IE6-machine
(too old to reply)
Johannes Passing
2006-10-28 11:41:54 UTC
Permalink
Hi,

I am using Wininet Autoproxy Support in an application. On a machine
with IE6, evth seems to work well and jsproxy!InternetGetProxyInfo
returns the correct information.

However, on my machine, on which IE7 (RTM) is installed,
InternetGetProxyInfo always fails with error code 1003.

I tried to verify this behaviour by compiling and running the MSDN
sample for autoproxy support
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/autoproxy_support_in_wininet.asp)
on both machines and again, the same problem appears - it works fine on
the IE6 machine, but jsproxy!InternetGetProxyInfo fails on the IE7
machine with error code 1003.

Has anyone else experienced this problem? I am wondering if this might
be due to a breaking change whicht has not (yet?) been documentented...

Unfortunately, switching to WinHTTP is not an option for me.

Thanks in advance,
Johannes
Vladimir Scherbina
2006-10-29 09:38:55 UTC
Permalink
Johannes,

The following statement from MSDN explains everything:
"InternetGetProxyInfo. Retrieves proxy data for accessing specified
resources. This function can only be called by dynamically linking to
"JSProxy.dll", *and may not be supported in future versions of Windows*".
Anyway I asked the guys from WNDP team to explain this wierd behavour ...
--
Vladimir
Hi,
I am using Wininet Autoproxy Support in an application. On a machine with
IE6, evth seems to work well and jsproxy!InternetGetProxyInfo returns the
correct information.
However, on my machine, on which IE7 (RTM) is installed,
InternetGetProxyInfo always fails with error code 1003.
I tried to verify this behaviour by compiling and running the MSDN sample
for autoproxy support
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/autoproxy_support_in_wininet.asp)
on both machines and again, the same problem appears - it works fine on
the IE6 machine, but jsproxy!InternetGetProxyInfo fails on the IE7 machine
with error code 1003.
Has anyone else experienced this problem? I am wondering if this might be
due to a breaking change whicht has not (yet?) been documentented...
Unfortunately, switching to WinHTTP is not an option for me.
Thanks in advance,
Johannes
Johannes Passing
2006-10-29 13:11:30 UTC
Permalink
Hi Vladimir,

you are right and I am aware of this limitation. However, some of the
jsproxy-related pages on MSDN (e.g.
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/wininet/wininet/autoproxyhelpervtbl.asp) have even
been updated to reflect changes introduced by IE 7. Plus, the
requirements section lists XP (and also Vista) as being supported OS. So
it seems that until now, these functions are supported and thus, it is
weird that MSDN's own sample does not seem to work any more.

Thanks for you answer,
Johannes
Post by Vladimir Scherbina
Johannes,
"InternetGetProxyInfo. Retrieves proxy data for accessing specified
resources. This function can only be called by dynamically linking to
"JSProxy.dll", *and may not be supported in future versions of Windows*".
Anyway I asked the guys from WNDP team to explain this wierd behavour ...
d***@orange-ftgroup.com
2006-12-12 18:45:48 UTC
Permalink
I have the same problem with IE7. When "URLDownloadToFile" is call,
"InternetGetProxyInfo" always fails with error code 1003. When you dont
call "URLDownloadToFile" and use the file (proxy.pac for example) on
the disk, "InternetGetProxyInfo" works.

Dominique
Post by Vladimir Scherbina
Johannes,
"InternetGetProxyInfo. Retrieves proxy data for accessing specified
resources. This function can only be called by dynamically linking to
"JSProxy.dll", *and may not be supported in future versions of Windows*".
Anyway I asked the guys from WNDP team to explain this wierd behavour ...
--
Vladimir
Hi,
I am using Wininet Autoproxy Support in an application. On a machine with
IE6, evth seems to work well and jsproxy!InternetGetProxyInfo returns the
correct information.
However, on my machine, on which IE7 (RTM) is installed,
InternetGetProxyInfo always fails with error code 1003.
I tried to verify this behaviour by compiling and running the MSDN sample
for autoproxy support
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/autoproxy_support_in_wininet.asp)
on both machines and again, the same problem appears - it works fine on
the IE6 machine, but jsproxy!InternetGetProxyInfo fails on the IE7 machine
with error code 1003.
Has anyone else experienced this problem? I am wondering if this might be
due to a breaking change whicht has not (yet?) been documentented...
Unfortunately, switching to WinHTTP is not an option for me.
Thanks in advance,
Johannes
Damian Manning
2006-12-14 09:35:37 UTC
Permalink
Guys, I'm seeing the same behavior on my end with IE7. Any word from
the folks at msft?

Cheers,
Damian
Post by d***@orange-ftgroup.com
I have the same problem with IE7. When "URLDownloadToFile" is call,
"InternetGetProxyInfo" always fails with error code 1003. When you dont
call "URLDownloadToFile" and use the file (proxy.pac for example) on
the disk, "InternetGetProxyInfo" works.
Dominique
Post by Vladimir Scherbina
Johannes,
"InternetGetProxyInfo. Retrieves proxy data for accessing specified
resources. This function can only be called by dynamically linking to
"JSProxy.dll", *and may not be supported in future versions of Windows*".
Anyway I asked the guys from WNDP team to explain this wierd behavour ...
--
Vladimir
Hi,
I am using Wininet Autoproxy Support in an application. On a machine with
IE6, evth seems to work well and jsproxy!InternetGetProxyInfo returns the
correct information.
However, on my machine, on which IE7 (RTM) is installed,
InternetGetProxyInfo always fails with error code 1003.
I tried to verify this behaviour by compiling and running the MSDN sample
for autoproxy support
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/autoproxy_support_in_wininet.asp)
on both machines and again, the same problem appears - it works fine on
the IE6 machine, but jsproxy!InternetGetProxyInfo fails on the IE7 machine
with error code 1003.
Has anyone else experienced this problem? I am wondering if this might be
due to a breaking change whicht has not (yet?) been documentented...
Unfortunately, switching to WinHTTP is not an option for me.
Thanks in advance,
Johannes
Vladimir Scherbina
2006-12-14 15:42:17 UTC
Permalink
I was some kind of a middle point between the OP and MSFT, and here is what
Post by Vladimir Scherbina
Our development team is aware of the bug and is working on it.
--
Vladimir (Windows SDK MVP)
http://msmvps.com/blogs/v_scherbina/

<***@orange-ftgroup.com> wrote in message news:***@f1g2000cwa.googlegroups.com...
I have the same problem with IE7. When "URLDownloadToFile" is call,
"InternetGetProxyInfo" always fails with error code 1003. When you dont
call "URLDownloadToFile" and use the file (proxy.pac for example) on
the disk, "InternetGetProxyInfo" works.

Dominique
Post by Vladimir Scherbina
Johannes,
"InternetGetProxyInfo. Retrieves proxy data for accessing specified
resources. This function can only be called by dynamically linking to
"JSProxy.dll", *and may not be supported in future versions of Windows*".
Anyway I asked the guys from WNDP team to explain this wierd behavour ...
--
Vladimir
Hi,
I am using Wininet Autoproxy Support in an application. On a machine with
IE6, evth seems to work well and jsproxy!InternetGetProxyInfo returns the
correct information.
However, on my machine, on which IE7 (RTM) is installed,
InternetGetProxyInfo always fails with error code 1003.
I tried to verify this behaviour by compiling and running the MSDN sample
for autoproxy support
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/autoproxy_support_in_wininet.asp)
on both machines and again, the same problem appears - it works fine on
the IE6 machine, but jsproxy!InternetGetProxyInfo fails on the IE7 machine
with error code 1003.
Has anyone else experienced this problem? I am wondering if this might be
due to a breaking change whicht has not (yet?) been documentented...
Unfortunately, switching to WinHTTP is not an option for me.
Thanks in advance,
Johannes
Damian Manning
2006-12-14 20:12:31 UTC
Permalink
Thanks Vladimir!

So, no ETA on a fix or suggestion for a workaround, eh? This bug is
wreaking some serious havoc with one of our largest customers.. it has
rendered out software unusable on a large percentage of their desktops.
Ack.

Cheers,
Damian
Post by Vladimir Scherbina
I was some kind of a middle point between the OP and MSFT, and here is what
Post by Vladimir Scherbina
Our development team is aware of the bug and is working on it.
--
Vladimir (Windows SDK MVP)
http://msmvps.com/blogs/v_scherbina/
I have the same problem with IE7. When "URLDownloadToFile" is call,
"InternetGetProxyInfo" always fails with error code 1003. When you dont
call "URLDownloadToFile" and use the file (proxy.pac for example) on
the disk, "InternetGetProxyInfo" works.
Dominique
Post by Vladimir Scherbina
Johannes,
"InternetGetProxyInfo. Retrieves proxy data for accessing specified
resources. This function can only be called by dynamically linking to
"JSProxy.dll", *and may not be supported in future versions of Windows*".
Anyway I asked the guys from WNDP team to explain this wierd behavour ...
--
Vladimir
Hi,
I am using Wininet Autoproxy Support in an application. On a machine with
IE6, evth seems to work well and jsproxy!InternetGetProxyInfo returns the
correct information.
However, on my machine, on which IE7 (RTM) is installed,
InternetGetProxyInfo always fails with error code 1003.
I tried to verify this behaviour by compiling and running the MSDN sample
for autoproxy support
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/autoproxy_support_in_wininet.asp)
on both machines and again, the same problem appears - it works fine on
the IE6 machine, but jsproxy!InternetGetProxyInfo fails on the IE7 machine
with error code 1003.
Has anyone else experienced this problem? I am wondering if this might be
due to a breaking change whicht has not (yet?) been documentented...
Unfortunately, switching to WinHTTP is not an option for me.
Thanks in advance,
Johannes
Vladimir Scherbina
2006-12-15 10:57:12 UTC
Permalink
As I wrote you in the email, there is no workaround yet ...
--
Vladimir (Windows SDK MVP)
http://msmvps.com/blogs/v_scherbina/

"Damian Manning" <***@gmail.com> wrote in message news:***@79g2000cws.googlegroups.com...
Thanks Vladimir!

So, no ETA on a fix or suggestion for a workaround, eh? This bug is
wreaking some serious havoc with one of our largest customers.. it has
rendered out software unusable on a large percentage of their desktops.
Ack.

Cheers,
Damian
Post by Vladimir Scherbina
I was some kind of a middle point between the OP and MSFT, and here is what
Post by Vladimir Scherbina
Our development team is aware of the bug and is working on it.
--
Vladimir (Windows SDK MVP)
http://msmvps.com/blogs/v_scherbina/
I have the same problem with IE7. When "URLDownloadToFile" is call,
"InternetGetProxyInfo" always fails with error code 1003. When you dont
call "URLDownloadToFile" and use the file (proxy.pac for example) on
the disk, "InternetGetProxyInfo" works.
Dominique
Post by Vladimir Scherbina
Johannes,
"InternetGetProxyInfo. Retrieves proxy data for accessing specified
resources. This function can only be called by dynamically linking to
"JSProxy.dll", *and may not be supported in future versions of Windows*".
Anyway I asked the guys from WNDP team to explain this wierd behavour ...
--
Vladimir
Hi,
I am using Wininet Autoproxy Support in an application. On a machine with
IE6, evth seems to work well and jsproxy!InternetGetProxyInfo returns the
correct information.
However, on my machine, on which IE7 (RTM) is installed,
InternetGetProxyInfo always fails with error code 1003.
I tried to verify this behaviour by compiling and running the MSDN sample
for autoproxy support
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wininet/wininet/autoproxy_support_in_wininet.asp)
on both machines and again, the same problem appears - it works fine on
the IE6 machine, but jsproxy!InternetGetProxyInfo fails on the IE7 machine
with error code 1003.
Has anyone else experienced this problem? I am wondering if this might be
due to a breaking change whicht has not (yet?) been documentented...
Unfortunately, switching to WinHTTP is not an option for me.
Thanks in advance,
Johannes
Loading...