chrome/common/extensions/docs/webRequest.html - Issue 10386172: Implemented declarative redirects to transparent image and empty document.

Side by Side Diff: chrome/common/extensions/docs/webRequest.html

Issue 10386172: Implemented declarative redirects to transparent image and empty document. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Fixed nits Created 8 years, 7 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« chrome/browser/extensions/api/declarative_webrequest/webrequest_action.cc ('K') | « chrome/common/extensions/docs/static/webRequest.html ('k') | chrome/renderer/resources/extensions/declarative_webrequest_custom_bindings.js » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:	1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:

2 1) The <head> information in this page is significant, should be uniform	2 1) The <head> information in this page is significant, should be uniform

3 across api docs and should be edited only with knowledge of the	3 across api docs and should be edited only with knowledge of the

4 templating mechanism.	4 templating mechanism.

5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a	5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a

6 browser, it will be re-generated from the template, json schema and	6 browser, it will be re-generated from the template, json schema and

7 authored overview content.	7 authored overview content.

8 4) The <body>.innerHTML is also generated by an offline step so that this	8 4) The <body>.innerHTML is also generated by an offline step so that this

9 page may easily be indexed by search engines.	9 page may easily be indexed by search engines.

10 --><html xmlns="http://www.w3.org/1999/xhtml"><head>	10 --><html xmlns="http://www.w3.org/1999/xhtml"><head>

(...skipping 345 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
356 requests, this means that the status line and response headers are	356 requests, this means that the status line and response headers are

357 available. This event is informational and handled asynchronously. It does not	357 available. This event is informational and handled asynchronously. It does not

358 allow modifying or cancelling the request.</dd>	358 allow modifying or cancelling the request.</dd>

359 <dt><code>onCompleted</code></dt>	359 <dt><code>onCompleted</code></dt>

360 <dd>Fires when a request has been processed successfully.</dd>	360 <dd>Fires when a request has been processed successfully.</dd>

361 <dt><code>onErrorOccurred</code></dt>	361 <dt><code>onErrorOccurred</code></dt>

362 <dd>Fires when a request could not be processed successfully.</dd>	362 <dd>Fires when a request could not be processed successfully.</dd>

363 </dl>	363 </dl>

364 The web request API guarantees that for each request either	364 The web request API guarantees that for each request either

365 <code>onCompleted</code> or <code>onErrorOccurred</code> is fired as the final	365 <code>onCompleted</code> or <code>onErrorOccurred</code> is fired as the final

366 event.	366 event with one exception: If a request is redirected to a <code>data://</code>

	367 URL, <code>onBeforeRedirect</code> is the last reported event.

367 <p></p>	368 <p></p>

368 <p id="life_cycle_footnote">(*) Note that the web request API presents an	369 <p id="life_cycle_footnote">(*) Note that the web request API presents an

369 abstraction of the network stack to the extension. Internally, one URL request	370 abstraction of the network stack to the extension. Internally, one URL request

370 can be split into several HTTP requests (for example to fetch individual byte	371 can be split into several HTTP requests (for example to fetch individual byte

371 ranges from a large file) or can be handled by the network stack without	372 ranges from a large file) or can be handled by the network stack without

372 communicating with the network. For this reason, the API does not provide the	373 communicating with the network. For this reason, the API does not provide the

373 final HTTP headers that are sent to the network. For example, all headers that	374 final HTTP headers that are sent to the network. For example, all headers that

374 are related to caching are invisible to the extension.</p>	375 are related to caching are invisible to the extension.</p>

375 <p>The following headers are currently <b>not provided</b> to the	376 <p>The following headers are currently <b>not provided</b> to the

376 <code>onBeforeSendHeaders</code> event. This list is not guaranteed to be	377 <code>onBeforeSendHeaders</code> event. This list is not guaranteed to be

(...skipping 4256 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
4633 _uff=0;	4634 _uff=0;

4634 urchinTracker();	4635 urchinTracker();

4635 }	4636 }

4636 catch(e) {/* urchinTracker not available. */}	4637 catch(e) {/* urchinTracker not available. */}

4637 </script>	4638 </script>

4638 <!-- end analytics -->	4639 <!-- end analytics -->

4639 </div>	4640 </div>

4640 </div> <!-- /gc-footer -->	4641 </div> <!-- /gc-footer -->

4641 </div> <!-- /gc-container -->	4642 </div> <!-- /gc-container -->

4642 </body></html>	4643 </body></html>

OLD	NEW