1825717 - NS_BINDING_ABORTED on nicovideo.jp

Status: RESOLVED INCOMPLETE

(Core :: Networking: DNS, defect)

Description

[qsjt0nvb05it]

Attachment: F12 network

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/111.0

Steps to reproduce:

I'm using a socks5 proxy and DNS over HTTPS. I opened https://www.nicovideo.jp/watch/sm42010625 the video won't load. At F12 I see NS_BINDING_ABORTED when the video player trying to retry.

Log of the procedure https://share.firefox.dev/40TzfQN

Actual results:

the video won't load

Expected results:

The video should play. It plays normally on Chromium with socks5 proxy and DNS over HTTPS set.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Networking: DNS' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Valentin Gosu [:valentin] (he/him)]

HttpChannelParent::RecvCancel: [this=7feb9a715800] cancelled call in child process from script: https://nicovideo.cdn.nimg.jp/web/scripts/pages/watch/modern/watch_app_df189357feb3ea419740.js:1:813973

The channel seems to be cancelled by the script - probably due to a timeout.

In any case, are you using DNS over HTTPS in mode 3? (network.trr.mode = 3?) - it appears so from the logs.
If that's the case, then this is the same as bug 1825538.

Comment 3

[qsjt0nvb05it]

(In reply to Valentin Gosu [:valentin] (he/him) from comment #2)

HttpChannelParent::RecvCancel: [this=7feb9a715800] cancelled call in child process from script: https://nicovideo.cdn.nimg.jp/web/scripts/pages/watch/modern/watch_app_df189357feb3ea419740.js:1:813973

The channel seems to be cancelled by the script - probably due to a timeout.

In any case, are you using DNS over HTTPS in mode 3? (network.trr.mode = 3?) - it appears so from the logs.
If that's the case, then this is the same as bug 1825538.

Yes I'm using mode 3. But different from that bug, my socks5 proxy server is on localhost.
If it is cancelled by the script, I believe it is not Firefox's fault? Or does Firefox API makes the timeout shorter than Chromium?

Comment 4

[Sunil Mayya]

Valentin, as the reporter has confirmed the trr mode settings (network.trr.mode = 3), does it make really make any difference if the sock5 proxy is running on local host or remotely?
If it does then we might have to treat it as a different bug?

Comment 5

[Kershaw Chang [:kershaw]]

Hi reporter,

Since bug 1825538 was fixed, could you try again to see if you can still reproduce this?
If you still see this issue, could you try to record a http log and send the log to [e-mail]?

Thanks.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:smayya, since the bug doesn't have a severity set, could you please set the severity or close the bug?

For more information, please visit BugBot documentation.

Comment 7

[Sunil Mayya]

Closing this bug as there is no response from the reporter.
Kindly re-open the bug if you still see this issue.