| || || |
The load flags of this request. Bits 0-15 are reserved.When added to a load group, this request's load flags are merged with the load flags of the load group.
| || ||The load group of this request. While pending, the request is a member of the load group. It is the responsibility of the request to implement this policy.|
| || ||The |
| || ||The error |
Various load flags which may be or'd together.
| || ||No special load flags.|
| || ||Do not deliver |
The following flags control the flow of data into the cache.
| || ||This flag prevents caching of any kind. It does not, however, prevent cached content from being used to satisfy this request.|
| || ||This flag prevents caching on disk (or other persistent media), which may be needed to preserve privacy. For HTTPS, this flag is set automatically.|
The following flags control what happens when the cache contains data that could perhaps satisfy this request. They are listed in descending order of precedence.
| || ||Force an end-to-end download of content data from the origin server. This flag is used for a shift-reload.|
| || ||Load from the cache, bypassing protocol specific validation logic. This flag is used when browsing via history. It is not recommended for normal browsing as it may likely violate reasonable assumptions made by the server and confuse users.|
The following flags control the frequency of cached content validation when neither
LOAD_FROM_CACHE are set. By default, cached content is automatically validated if necessary before reuse.
| || ||Forces validation of any cached content independent of its expiration time.|
| || ||Disables validation of expired content.|
| || ||Disables validation of expired content, provided it has already been validated (at least once) since the start of this session.|
| || || |
When set, this flag indicates that no user-specific data should be added to the request when opened. This means that things like authorization tokens or cookie headers should not be added.
Note: This will prevent proxy authentications from working, so use this flag with caution.
Cancels the current request. This will close any open input or output streams and terminate any async requests. Users should normally pass NS_BINDING_ABORTED, although other errors may also be passed. The error passed in will become the value of the
Implementations must not send any notifications (for example via
nsIRequestObserver) synchronously from this function. Similarly, removal from the load group (if any) must also happen asynchronously.
Requests that use
nsIStreamListener must not call onDataAvailable anymore after
cancel has been called.
nsIRequestimplementations expect aStatus to be a failure code; however, some implementations may allow aStatus to be a success code such as NS_OK. In general, aStatus should be a failure code.
void cancel( in nsresult aStatus );
- The reason for canceling this request.
Indicates whether the request is pending.
true when there is an outstanding asynchronous event that will make the request no longer be pending. Requests do not necessarily start out pending; in some cases, requests have to be explicitly initiated (for example
nsIChannel implementations are only pending once asyncOpen returns successfully).
Requests can become pending multiple times during their lifetime.
true if the request has yet to reach completion.
Resumes the current request. This may have the effect of re-opening any underlying transport and will
resume the delivery of data to any open streams.
Suspends the current request. This may have the effect of closing any underlying transport (in order to free up resources), although any open streams remain logically opened and will continue delivering data when the transport is resumed.
cancel() on a suspended request must not send any notifications (such as onstopRequest) until the request is resumed.