Wininet Timeout work around

[Leonard Chaney]

It seems there is a problem with the timeout value in Wininet. You can set
one but it will not do anything and default to 300 seconds. MS's knowledge
base said there was a work around. I'm wondering if anyone can save me
some time and frustration and has or knows of any source code to implement
this error in Wininet timeout.

TIA,

Len

[Derek Watt]

I need some help with this as well,

I'm using the inet control in vb6. I monitor for incoming data and
if nothing arrives within a given time (say 45 seconds) I use the
inet.cancel method to abort the connection. Unfortunately that doesn't
seem to always work immediately, and the inet control is not released
for some time. I'm thinking of going back to using the socket tools
package for an http activeX control now that a new version is out.
The older version seemed to stop working with some web servers all of
a sudden ?? (Even with the sample program that was provided.)
Socketools(when used for HTTP) was not as user friendly as the
microsoft internet transfer control but at least the .abort method
seemed to work.

[khi...@my-dejanews.com]

Hi!

It depends on what kind of timeout you want. Both SEND_TIMEOUT and
RECEIVE_TIMEOUT should work, as they have been fixed for IE5.

For IE4 workarounds you can consult the knowledge base.

feroze.

In article <#4DU$N#S#GA....@uppssnewspub04.moswest.msn.net>,

"Leonard Chaney" <leon...@intelisys.net> wrote:
> It seems there is a problem with the timeout value in Wininet. You can set
> one but it will not do anything and default to 300 seconds. MS's knowledge
> base said there was a work around. I'm wondering if anyone can save me
> some time and frustration and has or knows of any source code to implement
> this error in Wininet timeout.
>
> TIA,
>
> Len
>
>

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

[Adam Meyerowitz]

Len,

I am using the dll directly from a c++/MFC application. I am able to set
the timeouts using InternetSetOption and they work fine. Most of the
options default to 300 seconds but that seems a little lengthy to me
so I changed them. All is well.

Adam Meyerowitz
Video Data Systems

In article <36b37912...@news.xtra.co.nz>, D...@xtra.co.nz says...

> I need some help with this as well,
>
> I'm using the inet control in vb6. I monitor for incoming data and
> if nothing arrives within a given time (say 45 seconds) I use the
> inet.cancel method to abort the connection. Unfortunately that doesn't
> seem to always work immediately, and the inet control is not released
> for some time. I'm thinking of going back to using the socket tools
> package for an http activeX control now that a new version is out.
> The older version seemed to stop working with some web servers all of
> a sudden ?? (Even with the sample program that was provided.)
> Socketools(when used for HTTP) was not as user friendly as the
> microsoft internet transfer control but at least the .abort method
> seemed to work.
>
>

> On Fri, 29 Jan 1999 19:00:34 -0500, "Leonard Chaney"

[Steve Boyduy]

Microsoft's support Article ID: Q176420...BUG: InternetSetOption Does Not
Set Timeout Values.

I tried setting INTERNET_OPTION_CONNECT_TIMEOUT unsuccessfully from
VB5...did I give up too early?

Is there a workaround?

Thanks,

Steve

Adam Meyerowitz wrote in message ...

[Igor Pronin]

Adam Meyerowitz kirjoitti viestissä ...

>Len,
>
>I am using the dll directly from a c++/MFC application. I am able to
set
>the timeouts using InternetSetOption and they work fine. Most of the
>options default to 300 seconds but that seems a little lengthy to me
>so I changed them. All is well.
>
>Adam Meyerowitz
>Video Data Systems

Really - which version of wininet.dll do you use?

Igor Pronin

[Sugeet Shah]

I tried till cows come home and still no luck. Maybe, I don't know
the right way to set it... maybe MFC has some workaround to it?
I don't use MFC.

[Igor Pronin]

>>I am using the dll directly from a c++/MFC application. I am able to
>set
>>the timeouts using InternetSetOption and they work fine. Most of the
>>options default to 300 seconds but that seems a little lengthy to me
>>so I changed them. All is well.
>>
>>Adam Meyerowitz
>>Video Data Systems

The version used is: wininet.dll that has a date/time stamp 5-11-98
8:01p that
came with windows 98

Sio it seems that the timeout-bug has been corrected there. Hurrah.

Igor Pronin

[Jeff Young]

Has this been tested? I mean, have these timeouts been set to say, 1
second, and then used against a mock-up request that is forced to take five
seconds? I'd be *real* interested to see that in action...

Igor Pronin wrote in message ...

[Adam Meyerowitz]

I have tested it in one situation. I made a sample app that listens on
port 21 (the ftp port). The sample app simply accepts the incoming
connection instead of sending back the welcome header info that is
required for a ftp connection. The new wininet.dll times out
appropriately with the value I set when it attempts to connect to this
bogus ftp server.

In article <OGl2S#rW#GA....@uppssnewspub05.moswest.msn.net>,
pens...@hotmail.com says...

[ben...@my-dejanews.com]

This is a know bug, see article Q176420 from the Microsoft Knowledge based,
they are giving work arounds.

Benoit Lapointe

In article <eIN8rIMY#GA....@uppssnewspub05.moswest.msn.net>,
"Tim Hawkins" <TimHa...@email.msn.com> wrote:
> Does anybody know if there is a solution for this on NT, I have NT 4 and IE
> 4 SP1 and NT 4 SP4 loaded, but the system is ignoring my timeout settings.
>
> Adam Meyerowitz wrote in message ...