This component implements the following interfaces:
|No special load flags:
|Don't deliver status notifications to the nsIProgressEventSink, or keep
this load from completing the nsILoadGroup it may belong to.
|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 auto-
|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_BYPASS_CACHE or LOAD_FROM_CACHE are set. By default,
cached content is automatically validated if necessary before reuse.
VALIDATE_ALWAYS forces validation of any cached content independent of
its expiration time.
VALIDATE_NEVER disables validation of expired content.
VALIDATE_ONCE_PER_SESSION disables validation of expired content,
provided it has already been validated (at least once) since the start
of this session.
NOTE TO IMPLEMENTORS:
These flags are intended for normal browsing, and they should therefore
not apply to content that must be validated before each use. Consider,
for example, a HTTP response with a "Cache-control: no-cache" header.
According to RFC2616, this response must be validated before it can
be taken from a cache. Breaking this requirement could result in
incorrect and potentially undesirable side-effects.
When added to a load group, this request's load flags are merged with
the load flags of the load group.
readonly AUTF8String nsIRequest.name
readonly nsresult nsIRequest.status
Reference documentation is generated from Mozilla's source.