nsISupports
Last changed in Gecko 1.7 Implemented by: @mozilla.org/network/protocol-proxy-service;1
. To access the service use:
var pps = Components.classes["@mozilla.org/network/protocol-proxy-service;1"] .getService(Components.interfaces.nsIProtocolProxyService);
Deprecated since Gecko 18 |
|
|
|
void registerFilter(in |
void unregisterFilter(in |
Constant | Value | Description |
RESOLVE_NON_BLOCKING |
1<<0 |
This flag may be passed to the resolve method to request that it fail instead of block the calling thread. Proxy Auto Config (PAC) may perform a synchronous DNS query, which may not return immediately. So, calling resolve without this flag may result in locking up the calling thread for a lengthy period of time. By passing this flag to resolve, one can failover to asyncResolve to avoid locking up the calling thread if a PAC query is required. When this flag is passed to resolve, resolve may throw the exception NS_BASE_STREAM_WOULD_BLOCK to indicate that it failed due to this flag being present. |
Deprecated since Gecko 18
This method has been removed in Firefox 18. Use resolveAsync
instead
This method returns a nsIProxyInfo
instance that identifies a proxy to be used for loading the given URI. Otherwise, this method returns null indicating that a direct connection should be used.
If this proxy is unavailable, getFailoverForProxy()
may be called to determine the correct secondary proxy to be used.
If the protocol handler for the given URI supports nsIProxiedProtocolHandler
, then the nsIProxyInfo
instance returned from resolve may be passed to the nsIProxiedProtocolHandler.newProxiedChannel()
method to create a nsIChannel
to the given URI that uses the specified proxy.
However, if the nsIProxyInfo
type is "http", then it means that the given URI should be loaded using the HTTP protocol handler, which also supports nsIProxiedProtocolHandler
.
nsIProxyInfo resolve( in nsIURI aURI, in unsigned long aFlags );
aURI
aFlags
An nsIProxyInfo
object or null for a direct connection.
nsIProxyInfo
instance with a type of "unknown" to indicate to the consumer that asyncResolve should be used to wait for the PAC file to finish loading. Otherwise, the consumer may choose to treat the result as type "direct" if desired. See nsIProxiedProtocolHandler.newProxiedChannel()
. This method is an asychronous version of the resolve method. Unlike resolve, this method is guaranteed not to block the calling thread waiting for DNS queries to complete. This method is intended as a substitute for resolve when the result is not needed immediately.
nsICancelable asyncResolve( in nsIURI aURI, in unsigned long aFlags, in nsIProtocolProxyCallback aCallback );
aURI
aFlags
aCallback
An nsICancelableobject
that can be used to cancel the asynchronous operation. If canceled, the cancellation status (aReason) will be forwarded to the callback's nsIProtocolProxyCallback.onProxyAvailable()
method via the aStatus parameter.
This method may be called to construct a nsIProxyInfo
instance from the given parameters. This method may be useful in conjunction with nsISocketTransportService.createTransport()
for creating, for example, a SOCKS connection.
nsIProxyInfo newProxyInfo( in ACString aType, in AUTF8String aHost, in long aPort, in unsigned long aFlags, in unsigned long aFailoverTimeout, in nsIProxyInfo aFailoverProxy );
aType
aHost
aPort
aFlags
nsIProxyInfo
for currently defined flags.aFailoverTimeout
aFailoverProxy
An nsIProxyInfo
object.
If the proxy identified by aProxyInfo is unavailable for some reason, this method may be called to access an alternate proxy that may be used instead. As a side-effect, this method may affect future result values from resolve/asyncResolve as well as from getFailoverForProxy.
nsIProxyInfo getFailoverForProxy( in nsIProxyInfo aProxyInfo, in nsIURI aURI, in nsresult aReason );
aProxyInfo
aURI
aReason
An nsIProxyInfo
object or null for a direct connection.
NS_ERROR_NOT_AVAILABLE
This method may be used to register a proxy filter instance. Each proxy filter is registered with an associated position that determines the order in which the filters are applied (starting from position 0). When resolve/asyncResolve is called, it generates a list of proxies for the given URI, and then it applies the proxy filters. The filters have the opportunity to modify the list of proxies.
If two filters register for the same position, then the filters will be visited in the order in which they were registered. If the filter is already registered, then its position will be updated.
After filters have been run, any disabled or disallowed proxies will be removed from the list. A proxy is disabled if it had previously failed-over to another proxy (see getFailoverForProxy()
). A proxy is disallowed, for example, if it is a HTTP proxy and the nsIProtocolHandler
for the queried URI does not permit proxying via HTTP.
If a nsIProtocolHandler
disallows all proxying, then filters will never have a chance to intercept proxy requests for such URLs.
void registerFilter( in nsIProtocolProxyFilter aFilter, in unsigned long aPosition );
aFilter
nsIProtocolProxyFilter
instance to be registered.aPosition
This method may be used to unregister a proxy filter instance. All filters will be automatically unregistered at XPCOM shutdown.
void unregisterFilter( in nsIProtocolProxyFilter aFilter );
aFilter
nsIProtocolProxyFilter
instance to be unregistered.