Open
Bug 1572215
Opened 5 years ago
Updated 2 years ago
Allow nsIProtocolHandler to return nsIHTTPChannel (or alike) channel with headers and status code support
Categories
(Core :: Networking, enhancement, P3)
Core
Networking
Tracking
()
NEW
People
(Reporter: irakli, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [necko-triaged])
As part of dweb effort we're adding experimental web-extension API to register custom network protocol implementations (see Bug libdweb-protocol for details).
However right channels returned by custom nsIProtocolHandler
are not queried for nsIHttpChannel
nor there is another type of channel that supports headers & status codes. Given that many web APIs depends on HTTP headers (e.g. video element will issue range requests) we need some way to allow passing headers to requests and responses.
Reporter | ||
Updated•5 years ago
|
See Also: → libdweb-protocol
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
See Also: → https://github.com/mozilla/libdweb/issues/37
Reporter | ||
Updated•5 years ago
|
Blocks: libdweb-protocol
See Also: libdweb-protocol →
Comment 1•5 years ago
|
||
Put this to P3 for now, since I think necko team has not enough resource to support this.
Please talk to Nhi if you need our support. Thanks.
Priority: -- → P3
Whiteboard: [necko-triaged]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•