Re: How to set Timeout with URL Moniker?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Brian Birtle (brian_birtle_at_hotmail.com)
Date: 09/20/04 

Date: 20 Sep 2004 02:17:15 -0700

Ama,
Thanks for the post. To clarify my problem - everything works fine
unless the script takes more than about 60 seconds to return any HTTP
response. Furthermore, the long-running script definitely does get
executed as well as completes successfully and returns the text "ok"
as a response. I just thought it would be good to just call
IsClientConnected to verify, but I believe what is happening is
Internet Explorer times out after x secs, stops waits, terminates the
HTTP connection, and thus never receives the "ok" from the server.

An interesting side note, but if both the client and server is
localhost, the problem does not occur. (So this has made testing more
complicated)

Other ideas?

Thanks,
- Brian

"ama" <a.m.a@videotron.ca> wrote in message news:<puj3d.8457$ir6.255092@wagner.videotron.net>...
> "Brian Birtle" <brian_birtle@hotmail.com> wrote in message
> news:b5e821b2.0409190455.5639711@posting.google.com...
> > We use a URL Moniker to make an HTTP/S request to a script which can
> > take sometimes several minutes to execute. It seems like what happens
> > is Internet Explorer gives up waiting at some point and terminates the
> > request.
> >
> > It's a silly stupid question, but how can I set the timeout to
> > unlimited to avoid this problem? I've been combing the docs and can
> > figure out no way to do it. (get pointers to IWinINet, IBindInfo,
> > IBindStatusCallback, etc... nope)
> >
> > Or does someone have another idea about why the problem could be
> > occuring? I've tested and our script executes successfully and returns
> > a simple "ok" as the HTTP response. The ActiveX control *should* get
> > this, but never does. IIS logs indicate success, application state is
> > correct, etc... the client just never receives the completion
> > notification.
> >
> > It's an ActiveX control hosted in Internet Explorer and written using
> > VC++.NET 2003, ATL COM (no .NET use) However I think the priciple is
> > the same if using VB6.
> >
> > Thanks much,
> > - Brian
>
> So if im getting this right, the problem has nothing to do with the
> execution of the script
> but rather with the http request ? If that's the case then forget about the
> script for now and
> I suggest 2 test cases:
> First, clear the cached files, Wininet uses internet explorer 's cache
> system at some level
> and since you are trying to test response time, you dont need the cache
> settings to interfere.
> Then make a request for a new file , of diffrent type like a GIF. This will
> test the Moniker.
> IF this test results in similar problems, then store another file (any file)
> on a new Server,
> this time not the IIS, but rather a remote server and try again. Obviously
> at this point if you get
> again a similar behavior, then we both know the problem is with the
> implementation of your
> Moniker and not the WinInet APIs themselves. It may be certain FLAGS you
> used wrong etc..
>
> cya

Relevant Pages