Rick Marvin wrote: > I am using the necko engine in a custom application. When I attempt to > retrieve HTTP urls through a HttpChannel::AsynchRead, I successfully receive > the > nsHttpServerListener OnStartRequestEvents, OnDataAvailableRequestEvents, and > OnStopRequestEvents. Through the nsHttpServerListener, the are routed to my > consumer(listener) which I used when I envoked the asyncRead. > > However, when I attempt to retrieve HTTPS urls through a > HttpChannel::AsynchRead, I receive the nsHttpServerListener::OnStartRequest > call, however, that's were it stops. I don't receive the OnDataRequestEvent > as expected. Does anyone have any ideas where I might start looking for > answers? look to see if the socket transport layer is sending out the proper events (breakpoints in nsAsyncStreamListener would do). > > Here is a little more background > Trying to track this down, I have been tracing how mozilla loads HTTPS urls. > Differences are that I do not use a load group. By using a Load group, > mozilla seems to get a lot more events (nsFileChannel::OnStart, OnDataAvail, > OnStop as well as nsStreamIOChannel::OnStart, OnDataAvail, OnStop). But > finally mozilla also receives the nsHttpServerListener OnStartRequestEvent, > OnDataAvailableRequestEvent, and OnStopRequestEvents. The > nsHttpServerListener, as I experienced with my HTTP requests, also routes > the request to the consumer which was used when the asyncRead was invoked. this is very strange... it sounds like something low-level is blocking all the events from being triggered. the firing of events should not require a load group... arrggh! darin
