Discussion:
InternetSetOption, timeout, IE7
(too old to reply)
Cosmin
2007-06-25 15:58:57 UTC
Permalink
Hello.

I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).

I tried to set several flags, as in the following lines:

DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));

Does anybody know anything more on this topic ?

Thank you.
Cosmin
Scherbina Vladimir
2007-07-03 10:02:39 UTC
Permalink
I think this bug (http://support.microsoft.com/kb/176420) also migrated to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
Sam Boman
2007-07-05 13:16:02 UTC
Permalink
Hi!

I have also been running into this problem.
We use WinInet.dll in a VBA project in Access, and we want to take the
connection timeout down to i.e. 5 seconds, so the application would not wait
for 50 seconds every time the web-server does not respond.

We make a HTTP-Request:
hOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
hOpenUrl = InternetOpenUrl(hOpen, url, vbNullString, 0,
INTERNET_FLAG_RELOAD, 0)

We are using Internet Explorer 6 SP2, does anyone know if the bug is
resolved or not? The Kb176420 just tell us that its a bug in IE 6 sp1...

//Sam
Post by Scherbina Vladimir
I think this bug (http://support.microsoft.com/kb/176420) also migrated to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
Scherbina Vladimir
2007-07-05 21:15:59 UTC
Permalink
Why not to use wininet in asynchronous mode?
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Hi!
I have also been running into this problem.
We use WinInet.dll in a VBA project in Access, and we want to take the
connection timeout down to i.e. 5 seconds, so the application would not wait
for 50 seconds every time the web-server does not respond.
hOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
hOpenUrl = InternetOpenUrl(hOpen, url, vbNullString, 0,
INTERNET_FLAG_RELOAD, 0)
We are using Internet Explorer 6 SP2, does anyone know if the bug is
resolved or not? The Kb176420 just tell us that its a bug in IE 6 sp1...
//Sam
Post by Scherbina Vladimir
I think this bug (http://support.microsoft.com/kb/176420) also migrated to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
Sam Boman
2007-07-06 06:22:00 UTC
Permalink
We cant do it because, Access. Access is not multi threaded... So we have to
do it synchronous.

We are doint big data-transfer-jobs, with oracle, sqlserver and some http.
And if the webserver does not respond the application will wait i.e. 1000
http-requests * 50 seconds timeout ~ 14 hours... not good at all. would be
better if we could force the application to just wait a few seconds (~1
hour...).

Do you know where we can find if its still a bug in IE6 sp2 or IE7?...
Thanks!

Sam
Post by Scherbina Vladimir
Why not to use wininet in asynchronous mode?
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Hi!
I have also been running into this problem.
We use WinInet.dll in a VBA project in Access, and we want to take the
connection timeout down to i.e. 5 seconds, so the application would not wait
for 50 seconds every time the web-server does not respond.
hOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
hOpenUrl = InternetOpenUrl(hOpen, url, vbNullString, 0,
INTERNET_FLAG_RELOAD, 0)
We are using Internet Explorer 6 SP2, does anyone know if the bug is
resolved or not? The Kb176420 just tell us that its a bug in IE 6 sp1...
//Sam
Post by Scherbina Vladimir
I think this bug (http://support.microsoft.com/kb/176420) also migrated to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
Scherbina Vladimir
2007-07-06 06:33:18 UTC
Permalink
I see. But I believe, there is still a solution. For example, to create a
DLL that will wrap all HTTP communications (in sync or async Wininet mode,
it does not matter) and exports functions that will be used in Access.
Anyway, I will direct your problem to WNDP team, they will let us know more
information concerning this issue.
--
Vladimir, Windows SDK MVP
Post by Sam Boman
We cant do it because, Access. Access is not multi threaded... So we have to
do it synchronous.
We are doint big data-transfer-jobs, with oracle, sqlserver and some http.
And if the webserver does not respond the application will wait i.e. 1000
http-requests * 50 seconds timeout ~ 14 hours... not good at all. would be
better if we could force the application to just wait a few seconds (~1
hour...).
Do you know where we can find if its still a bug in IE6 sp2 or IE7?...
Thanks!
Sam
Post by Scherbina Vladimir
Why not to use wininet in asynchronous mode?
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Hi!
I have also been running into this problem.
We use WinInet.dll in a VBA project in Access, and we want to take the
connection timeout down to i.e. 5 seconds, so the application would not wait
for 50 seconds every time the web-server does not respond.
hOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
hOpenUrl = InternetOpenUrl(hOpen, url, vbNullString, 0,
INTERNET_FLAG_RELOAD, 0)
We are using Internet Explorer 6 SP2, does anyone know if the bug is
resolved or not? The Kb176420 just tell us that its a bug in IE 6 sp1...
//Sam
Post by Scherbina Vladimir
I think this bug (http://support.microsoft.com/kb/176420) also
migrated
to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession,
INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
Sam Boman
2007-07-06 09:16:00 UTC
Permalink
Thanks for your support!
But were do I find the WNDP team?
Post by Scherbina Vladimir
I see. But I believe, there is still a solution. For example, to create a
DLL that will wrap all HTTP communications (in sync or async Wininet mode,
it does not matter) and exports functions that will be used in Access.
Anyway, I will direct your problem to WNDP team, they will let us know more
information concerning this issue.
--
Vladimir, Windows SDK MVP
Post by Sam Boman
We cant do it because, Access. Access is not multi threaded... So we have to
do it synchronous.
We are doint big data-transfer-jobs, with oracle, sqlserver and some http.
And if the webserver does not respond the application will wait i.e. 1000
http-requests * 50 seconds timeout ~ 14 hours... not good at all. would be
better if we could force the application to just wait a few seconds (~1
hour...).
Do you know where we can find if its still a bug in IE6 sp2 or IE7?...
Thanks!
Sam
Post by Scherbina Vladimir
Why not to use wininet in asynchronous mode?
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Hi!
I have also been running into this problem.
We use WinInet.dll in a VBA project in Access, and we want to take the
connection timeout down to i.e. 5 seconds, so the application would not wait
for 50 seconds every time the web-server does not respond.
hOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
hOpenUrl = InternetOpenUrl(hOpen, url, vbNullString, 0,
INTERNET_FLAG_RELOAD, 0)
We are using Internet Explorer 6 SP2, does anyone know if the bug is
resolved or not? The Kb176420 just tell us that its a bug in IE 6 sp1...
//Sam
Post by Scherbina Vladimir
I think this bug (http://support.microsoft.com/kb/176420) also
migrated
to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession,
INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
Scherbina Vladimir
2007-07-06 11:19:41 UTC
Permalink
I already contacted them. They should answer within the reasonable period of
time.
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Thanks for your support!
But were do I find the WNDP team?
Post by Scherbina Vladimir
I see. But I believe, there is still a solution. For example, to create a
DLL that will wrap all HTTP communications (in sync or async Wininet mode,
it does not matter) and exports functions that will be used in Access.
Anyway, I will direct your problem to WNDP team, they will let us know more
information concerning this issue.
--
Vladimir, Windows SDK MVP
Post by Sam Boman
We cant do it because, Access. Access is not multi threaded... So we
have
to
do it synchronous.
We are doint big data-transfer-jobs, with oracle, sqlserver and some http.
And if the webserver does not respond the application will wait i.e. 1000
http-requests * 50 seconds timeout ~ 14 hours... not good at all.
would
be
better if we could force the application to just wait a few seconds (~1
hour...).
Do you know where we can find if its still a bug in IE6 sp2 or IE7?...
Thanks!
Sam
Post by Scherbina Vladimir
Why not to use wininet in asynchronous mode?
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Hi!
I have also been running into this problem.
We use WinInet.dll in a VBA project in Access, and we want to take the
connection timeout down to i.e. 5 seconds, so the application would
not
wait
for 50 seconds every time the web-server does not respond.
hOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
hOpenUrl = InternetOpenUrl(hOpen, url, vbNullString, 0,
INTERNET_FLAG_RELOAD, 0)
We are using Internet Explorer 6 SP2, does anyone know if the bug is
resolved or not? The Kb176420 just tell us that its a bug in IE 6 sp1...
//Sam
Post by Scherbina Vladimir
I think this bug (http://support.microsoft.com/kb/176420) also
migrated
to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession,
INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession,
INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession,
INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
Vladimir Scherbina [MVP]
2007-08-24 23:49:38 UTC
Permalink
Sam,

Here is what I recieved from WNDP team,

I'm sorry for the delay but this ongoing project we're on should be worth
it.

I've done some more digging around this. I did not reproduce the issue as
reported by the customer.

I verified 2 of the mentioned timeout options (CONNECT_TIMEOUT and
RECEIVE_TIMEOUT) and:

- when setting the new timeout values globally, they are properly
applied to subsequent created objects (session, connection, request
respectively). Note that the object created before changing the global
timeout still have the default timeout set.

- when overwriting the timeout for a given object, the new value
was properly picked up and by its derived objects as well

At this point, the way to go should be to investigate how exactly the
customer is calling the API (particularly how the newly set timeouts values
are exercised) but the issue is not reproducible currently on my IE7
binaries.
--
Vladimir, Windows SDK MVP
http://msmvps.com/blogs/v_scherbina/
Post by Scherbina Vladimir
I already contacted them. They should answer within the reasonable period
of time.
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Thanks for your support!
But were do I find the WNDP team?
Post by Scherbina Vladimir
I see. But I believe, there is still a solution. For example, to create a
DLL that will wrap all HTTP communications (in sync or async Wininet mode,
it does not matter) and exports functions that will be used in Access.
Anyway, I will direct your problem to WNDP team, they will let us know more
information concerning this issue.
--
Vladimir, Windows SDK MVP
Post by Sam Boman
We cant do it because, Access. Access is not multi threaded... So we
have
to
do it synchronous.
We are doint big data-transfer-jobs, with oracle, sqlserver and some http.
And if the webserver does not respond the application will wait i.e. 1000
http-requests * 50 seconds timeout ~ 14 hours... not good at all.
would
be
better if we could force the application to just wait a few seconds (~1
hour...).
Do you know where we can find if its still a bug in IE6 sp2 or IE7?...
Thanks!
Sam
Post by Scherbina Vladimir
Why not to use wininet in asynchronous mode?
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Hi!
I have also been running into this problem.
We use WinInet.dll in a VBA project in Access, and we want to take the
connection timeout down to i.e. 5 seconds, so the application would
not
wait
for 50 seconds every time the web-server does not respond.
hOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
hOpenUrl = InternetOpenUrl(hOpen, url, vbNullString, 0,
INTERNET_FLAG_RELOAD, 0)
We are using Internet Explorer 6 SP2, does anyone know if the bug is
resolved or not? The Kb176420 just tell us that its a bug in IE 6 sp1...
//Sam
Post by Scherbina Vladimir
I think this bug (http://support.microsoft.com/kb/176420) also
migrated
to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession,
INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession,
INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession,
INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
g***@gmail.com
2007-09-27 13:40:11 UTC
Permalink
Hello,

I have read your problem which looks like mine. However, the context
is a bit different. My project is about a Java J2EE application under
IE 6.
We are using asynchronous http transfers throught the ActiveX Object
"Microsoft.XMLHTTP" (client side call with javascript). One of these
call takes a long time ( ~80 min ) because of the million datas to
insert into the Oracle Database. After ~60 min of activity, the state
of the ActiveX Object switch from 3 to 4 (complete state) with a "12
002" http status code. On the other hand, the server proccess is still
running and still inserting datas. I concluded this is about some
client (IE) bad configuration.

After searching information, i found that "12002" is a WinInet error
code. One solution could be to set a higher value for the Time Out
parameter. I found the "InternetSetOption" function but i have no idea
how to use it with Java or Javascript.

I have also tryied to modify a key in the windows registry
(ReceiveTimeout key in HKEY_CURRENT_USER\Software\Microsoft\Windows
\CurrentVersion\Internet Settings\) and set the parameter to a new
higher value with no effect on IE 6. (I found that information on
microsoft websites).

Sam Boman
2007-07-06 09:16:01 UTC
Permalink
Post by Scherbina Vladimir
I see. But I believe, there is still a solution. For example, to create a
DLL that will wrap all HTTP communications (in sync or async Wininet mode,
it does not matter) and exports functions that will be used in Access.
Anyway, I will direct your problem to WNDP team, they will let us know more
information concerning this issue.
--
Vladimir, Windows SDK MVP
Post by Sam Boman
We cant do it because, Access. Access is not multi threaded... So we have to
do it synchronous.
We are doint big data-transfer-jobs, with oracle, sqlserver and some http.
And if the webserver does not respond the application will wait i.e. 1000
http-requests * 50 seconds timeout ~ 14 hours... not good at all. would be
better if we could force the application to just wait a few seconds (~1
hour...).
Do you know where we can find if its still a bug in IE6 sp2 or IE7?...
Thanks!
Sam
Post by Scherbina Vladimir
Why not to use wininet in asynchronous mode?
--
Vladimir, Windows SDK MVP
Post by Sam Boman
Hi!
I have also been running into this problem.
We use WinInet.dll in a VBA project in Access, and we want to take the
connection timeout down to i.e. 5 seconds, so the application would not wait
for 50 seconds every time the web-server does not respond.
hOpen = InternetOpen(scUserAgent, INTERNET_OPEN_TYPE_PRECONFIG,
vbNullString, vbNullString, 0)
hOpenUrl = InternetOpenUrl(hOpen, url, vbNullString, 0,
INTERNET_FLAG_RELOAD, 0)
We are using Internet Explorer 6 SP2, does anyone know if the bug is
resolved or not? The Kb176420 just tell us that its a bug in IE 6 sp1...
//Sam
Post by Scherbina Vladimir
I think this bug (http://support.microsoft.com/kb/176420) also
migrated
to
IE7.
--
Vladimir, Windows SDK MVP
Post by Cosmin
Hello.
I am trying to set a timeout value smaller than the default 30
seconds, without any success. MSDN does not mention this bug (http://
support.microsoft.com/kb/176420) in IE 7 (I'm using IE7 on XP).
DWORD var = 4000L; // millisec
int b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession,
INTERNET_OPTION_DATA_RECEIVE_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_DATA_SEND_TIMEOUT,
(void *)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_SEND_TIMEOUT, (void
*)&var, sizeof(var));
b = InternetSetOption(fSession, INTERNET_OPTION_RECEIVE_TIMEOUT, (void
*)&var, sizeof(var));
var = 4; // Retries
b = InternetSetOption(fSession, INTERNET_OPTION_CONNECT_RETRIES, (void
*)&var, sizeof(var));
Does anybody know anything more on this topic ?
Thank you.
Cosmin
Loading...