{"json_modified": "2016-07-09T04:04:40.492233", "uuid": "17c8e3f3-4847-4c25-bfd4-750cc21f247e", "title": "nsIChannel", "url": "/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIChannel", "tags": ["XPCOM Interface Reference", "Interfaces:Scriptable", "XPCOM", "Interfaces", "XPCOM API Reference"], "translations": [{"uuid": "0a4ef958-deba-48c3-865a-dc1fbaeaa1d9", "title": "nsIChannel", "url": "/es/docs/nsIChannel", "tags": ["p\u00e1ginas_a_traducir"], "summary": "", "localization_tags": [], "locale": "es", "last_edit": "2014-05-19T06:00:57", "review_tags": []}], "modified": "2016-07-09T04:04:05", "label": "nsIChannel", "localization_tags": [], "locale": "en-US", "id": 3359, "last_edit": "2015-04-01T00:23:28", "summary": "Once a channel is created (via nsIIOService.newChannel()
), parameters for that request may be set by using the channel attributes, or by calling QueryInterface() to retrieve a subclass of nsIChannel
for protocol-specific parameters. Then, the URI
can be fetched by calling open()
or asyncOpen()
. After a request has been completed, the channel is still valid for accessing protocol-specific results. For example, QueryInterfacing to nsIHttpChannel
allows response headers to be retrieved for the corresponding http transaction.", "sections": [{"id": "Method_overview", "title": "Method overview"}, {"id": "Attributes", "title": "Attributes"}, {"id": "Constants", "title": "Constants"}, {"id": "Methods", "title": "Methods"}, {"id": "asyncOpen()", "title": "asyncOpen()"}, {"id": "Parameters", "title": "Parameters"}, {"id": "Exceptions_thrown", "title": "Exceptions thrown"}, {"id": "open()", "title": "open()"}, {"id": "Parameters", "title": "Parameters"}, {"id": "Return_value", "title": "Return value"}, {"id": "Exceptions_thrown", "title": "Exceptions thrown"}, {"id": "See_also", "title": "See also"}], "slug": "Mozilla/Tech/XPCOM/Reference/Interface/nsIChannel", "review_tags": []}