![]() ![]() Take care not to enter an infinite loop by repeatedly providing invalid credentials. Note that extensions may provide invalid credentials. This event can be handled synchronously to provide authentication credentials. onAuthRequired (optionally synchronous) Fires when a request requires authentication of the user. It also allows you to cancel or redirect the request. The caching directives are processed before this event is triggered, so modifying headers such as Cache-Control has no influence on the browser's cache. This event is intended to allow extensions to add, modify, and delete response headers, such as incoming Content-Type headers. Due to redirects and authentication requests this can happen multiple times per request. onHeadersReceived (optionally synchronous) Fires each time that an HTTP(S) response header is received. It does not allow modifying or cancelling the request. This event is informational and handled asynchronously. The event is triggered before the headers are sent to the network. onSendHeaders Fires after all extensions have had a chance to modify the request headers, and presents the final (*) version. This event can be used to cancel the request. The onBeforeSendHeaders event is passed to all subscribers, so different subscribers may attempt to modify the request see the Implementation details section for how this is handled. ![]() The event is intended to allow extensions to add, modify, and delete request headers (*). onBeforeSendHeaders (optionally synchronous) Fires when a request is about to occur and the initial headers have been prepared. This event is sent before any TCP connection is made and can be used to cancel or redirect requests. OnBeforeRequest (optionally synchronous) Fires when a request is about to occur. The event life cycle for successful requests is illustrated here, followed by event definitions: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |