IE sends incorrect requests to the site root

[b***@hotmail.com]

We've got an ASP.NET application which is hosted on a https site. One
of our customers experiences a strange behavior. When his browser
downloads a page, it sends a new http request to the web root. We've
used a debug build of WinInet to make a log of the behavior. There are
number of wininet asserts in the log:

*** Wininet Assertion failed: UnlimitedConnections() ? TRUE :
(KeepAliveConnections() <= ConnectionLimit())
*** Source file: g:\n2\inetcore\wininet\common\servinfo.cxx
*** Source line: 3540
*** Thread 00000480

*** Wininet Assertion failed: cbUserPass < sizeof(cbMaxUserPathLen)
*** Source file: g:\n2\inetcore\wininet\auth\basic.cxx
*** Source line: 84
*** Thread 00000114

*** Wininet Assertion failed: m_ConnectionsAvailable <=
m_ConnectionLimit
*** Source file: g:\n2\inetcore\wininet\common\servinfo.cxx
*** Source line: 2992
*** Thread 00000114

We can also see the incorrect requests to the web root in the log but
couldn't find the reason why they are initiated.

Could someone help us to resolve the problem?

Thanks,
Boyan

[Vladimir Scherbina]

Report this issue to connect.microsoft.com
--
Vladimir (Windows SDK MVP)
http://msmvps.com/blogs/v_scherbina/

Post by b***@hotmail.com
We've got an ASP.NET application which is hosted on a https site. One
of our customers experiences a strange behavior. When his browser
downloads a page, it sends a new http request to the web root. We've
used a debug build of WinInet to make a log of the behavior. There are
(KeepAliveConnections() <= ConnectionLimit())
*** Source file: g:\n2\inetcore\wininet\common\servinfo.cxx
*** Source line: 3540
*** Thread 00000480
*** Wininet Assertion failed: cbUserPass < sizeof(cbMaxUserPathLen)
*** Source file: g:\n2\inetcore\wininet\auth\basic.cxx
*** Source line: 84
*** Thread 00000114
*** Wininet Assertion failed: m_ConnectionsAvailable <=
m_ConnectionLimit
*** Source file: g:\n2\inetcore\wininet\common\servinfo.cxx
*** Source line: 2992
*** Thread 00000114
We can also see the incorrect requests to the web root in the log but
couldn't find the reason why they are initiated.
Could someone help us to resolve the problem?
Thanks,
Boyan