Skip to content

Necko classes and properties

Honza Bambas edited this page Oct 3, 2019 · 2 revisions

nsHttpChannel

properties:

  • state, logan state with additional transitioning as: created (ctor) > open (AsyncOpen()) > connected (Connect()) > started (OnStartRequest()) > data (OnDataAvailable()) > on-stop (OnStopRequest()) > finished (calling mListener->OnStopRequest) > released; other possible states: redirected (OnRedirectVerifyCallback(NS_OK)), cancelled (Cancel())
  • url, full url of the request, as passed to Init method, immutable
  • proxy-resolve-time, [ms] the time proxy resolution took
  • has-proxy, set true if the resolved proxyInfo object is non-null (but there is no check if it states only ["direct"]!)
  • sts-found, present and true if the host is a HSTS host; doesn't mean we will upgrade
  • revalidates-cache, present only when a cache entry was found, true if we go to the server to validate, false if we don't
  • cos-before-trans-open, decimal value of ClassOfService flags at the time we are creating the transaction
  • priority-before-trans-open, priority decimal value at the time we are creating the transaction
  • from-cache, present and true when we are satisfying the response from the cache (ReadFromCache())
  • start-time, [ms] relative time since opening of the channel to the last nsHttpChannel::OnStartRequest call
  • first-data-time, [ms] relative time since opening of the channel to the first nsHttpChannel::OnDataAvailable call
  • last-data-time, [ms] relative time since opening of the channel to the last nsHttpChannel::OnDataAvailable call
  • stop-time, [ms] relative time since opening the channel and last call to nsHttpChannel::OnStopRequest
  • status, hex nsresult status argument as seen in all calls to nsHttpChannel::OnStopRequest, merged
  • suspendcount, counter of "Suspend() - Resume()" calls; this is normally "0" for a channel that have finished, useful to find out if channels are stuck because of missing Resume() calls
  • classify-time, [ms] an estimation of how long the classification took
  • cancel-status, hex nsresult status as passed to the last call of nsHttpChannel::Cancel
  • late-cancel, present after nsHttpChannel::Cancel call, true if Cancel() is called after we have already called OnStopRequest on the listener, false otherwise
  • http-status, the HTTP response code (e.g. "200"), both server and cached, merged (e.g. "401,401,200" for NTML)
  • tracker, true if the resource is a tracker, false otherwise
  • tail-blocked, present if the channel was tailed, true while it waits for unblock, false after unblocking
  • tail-block-time, [ms] how long the channel has been tail-blocked
  • tail-blocking, true when the channel is considered a 'head' request, aka makes requests that are tailing-eligible to wait for finishing this one
  • rc-id, hex id of the request content object assigned to this channel
Clone this wiki locally