Use a specialized error when avoiding speculative connections
Categories
(Core :: Networking: Proxy, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox145 | --- | fixed |
People
(Reporter: pierov, Assigned: pierov)
Details
Attachments
(1 file)
Speculative connections in some cases won't be performed to avoid DNS lookups: https://searchfox.org/firefox-main/rev/6cd61ea1ff39887da8f4dc1080a96c01f0c70ef8/netwerk/base/nsIOService.cpp#2214-2222.
However, that error might be reported in the console when the speculative connect is started by tab hovering: https://searchfox.org/firefox-main/rev/6cd61ea1ff39887da8f4dc1080a96c01f0c70ef8/browser/components/sessionstore/SessionStore.sys.mjs#5935-5942
Downstream in Tor Browser we might catch it quite more often (as we use a proxy filter to change SOCKS authentication on the fly and use the tor's daemon SOCKS auth isolation), so we'd like to silence it.
We thought about replacing the generic NS_ERROR_FAILURE with a new NS_ERROR_SPECULATIVE_CONNECT_DISABLED error code.
| Assignee | ||
Comment 1•2 months ago
|
||
As per the Matrix thread, that console.error could be removed instead.
| Assignee | ||
Comment 2•2 months ago
|
||
Updated•2 months ago
|
Comment 4•2 months ago
|
||
| bugherder | ||
Updated•1 month ago
|
Description
•