The maximum number of times that handlerBehaviorChanged can be called
per 10 minute sustained interval. handlerBehaviorChanged is an expensive
function call that shouldn't be called often.
Fired when an authentication failure is received. The listener has three
options: it can provide authentication credentials, it can cancel the
request and display the error page, or it can take no action on the
challenge. If bad user credentials are provided, this may be called
multiple times for the same request. Note, only one of 'blocking' or
'asyncBlocking' modes must be specified in the extraInfoSpec
parameter.
Fired before sending an HTTP request, once the request headers are
available. This may occur after a TCP connection is made to the server,
but before any HTTP data is sent.
Fired just before a request is going to be sent to the server
(modifications of previous onBeforeSendHeaders callbacks are visible by
the time onSendHeaders is fired).
Needs to be called when the behavior of the webRequest handlers has
changed to prevent incorrect handling due to caching. This function call
is expensive. Don't call it often.