Hi, Ge van Geldorp wrote: > There is a large amount of proxy configurations possible on Windows (WPAD, > proxy.pac, fixed proxy values), which might behave differently on a second > run of the protocol test compared to the first run. These configurations > influence when/how IInternetProtocolSink methods are called. For example, > with a standard, direct connection you'll get the following ReportProgress > notifications during the https test: > BINDSTATUS_FINDINGRESOURCE > BINDSTATUS_CONNECTING > BINDSTATUS_SENDINGREQUEST > BINDSTATUS_ACCEPTRANGES > BINDSTATUS_MIMETYPEAVAILABLE > However, when you run the protocol test for the second time on a machine > with a fixed proxy server configured, you'll only get these notifications: > BINDSTATUS_SENDINGREQUEST > BINDSTATUS_ACCEPTRANGES > BINDSTATUS_MIMETYPEAVAILABLE > > When a proxy is used, the BINDSTATUS_FINDINGRESOURCE and > BINDSTATUS_CONNECTING notifications report the hostname/ip address of the > proxy server, not the end destination. > >
I can't see this behavior in tests results, where do you see them? Which IE version is it? Also, you have to make sure that each SET_EXPECT is followed by CHECK_CALLED (or CLEAR_CALLED if you want to ignore that function was not called). Jacek
