HttpSendRequest in my ActiveX control stops IE sending further HTTP requests

[b***@googlemail.com]

Hi,

I have a weird problem.... (technical... not personal).

I have an ActiveX control that starts up 2 HTTP streams from the same
web server, one is video, one is metadata. It works great. The ActiveX
control lives inside a web page with a few other links that allow the
user to control things like video format, etc.

My problem is this:

If I have more than 1 stream running (i.e. 2 calls to HttpSendRequest,
2 threads looping round InternetReadFile) then any attempt from the
user side to click on any of the other links has no effect..... until
one of the HTTP streams is stopped. At which point IE sends the
request out and then toddles off to the right place.

I have verified this behavior by sniffing with wireshark.

The server is not bouncing the request - it's that IE never sends it
in the first place. It's almost like IE has serialised its request
behind the 2 I already have outstanding.

Any ideas?

Cheers,
Ben

[Volodymyr M. Shcherbyna]

This sounds like a simular behaviour in recent problems of "mike". Read
converstation "HttpSendRequest timeout recovery in ocx" below in this NG.
--
V.
This posting is provided "AS IS" with no warranties, and confers no
rights.

Post by b***@googlemail.com
Hi,
I have a weird problem.... (technical... not personal).
I have an ActiveX control that starts up 2 HTTP streams from the same
web server, one is video, one is metadata. It works great. The ActiveX
control lives inside a web page with a few other links that allow the
user to control things like video format, etc.
If I have more than 1 stream running (i.e. 2 calls to HttpSendRequest,
2 threads looping round InternetReadFile) then any attempt from the
user side to click on any of the other links has no effect..... until
one of the HTTP streams is stopped. At which point IE sends the
request out and then toddles off to the right place.
I have verified this behavior by sniffing with wireshark.
The server is not bouncing the request - it's that IE never sends it
in the first place. It's almost like IE has serialised its request
behind the 2 I already have outstanding.
Any ideas?
Cheers,
Ben

[b***@googlemail.com]

On Mar 25, 5:03 pm, "Volodymyr M. Shcherbyna"

Post by Volodymyr M. Shcherbyna
This sounds like a simular behaviour in recent problems of "mike". Read
converstation "HttpSendRequest timeout recovery in ocx" below in this NG.
--
V.

Hi

Thanks for the response. After reading through the topic I think the
solution is to hop over to WinHTTP?

That could also be a problem. Since we are using HTTPS and the
certificate that the server sends back is not validated. We tried to
use WinHTTP in the first place but due to the fact that it didn't work
with unsigned HTTPS certificates we had to ditch it.

Any more ideas?
Cheers,
Ben