I set browser.opaqueResponseBlocking and browser.opaqueResponseBlocking.javascriptValidator to true, but it will cause comments in comment.tie.163.com couldn't load, for example, https://comment.tie.163.com/I8TK8BRP0552BNOQ.html. It even happens when only set browser.opaqueResponseBlocking to true.

Dear reporter, thank you for the report.

I couldn't reproduce this issue with the Nightly 117.0a1 or Release 115.0 on Windows. To help us move on, we appreciate your answers to the questions below.

Can you please let us know which Firefox build were you testing with? If you were testing with the build older than Release 115, Beta 116 or Nightly 117, can you kindly upgrade and test again?

Also, can you confirm if you see the same values of these preferences in your about:config page as below?

• browser.opaqueResponseBlocking: true
• browser.opaqueResponseBlocking.filterFetchResponse: 2
• browser.opaqueResponseBlocking.javascriptValidator: true
• browser.opaqueResponseBlocking.mediaExceptionsStrategy: 1

Thank you very much.

Sorry, I refresh Firefox in about:support, then only set browser.opaqueResponseBlocking and browser.opaqueResponseBlocking.javascriptValidator to true, restart Firefox, https://comment.tie.163.com/I8TK8BRP0552BNOQ.html seems works well without problem. I suppose here are something in about:config, refresh Firefox reslove it. Closing this bug.

I found a very interesting phenomenon: Set network.http.network_access_on_socket_process.enabled and browser.opaqueResponseBlocking = true will triggering this bug. It I disable network.http.network_access_on_socket_process.enabled, this bug disappear.

Hi Kershaw, can you share if there's any plan for enabling network.http.network_access_on_socket_process.enabled by default? Thank you.

(In reply to Hsin-Yi Tsai (she/her) [:hsinyi] from comment #6)

Hi Kershaw, can you share if there's any plan for enabling network.http.network_access_on_socket_process.enabled by default? Thank you.

Unfortunately, we don't have a timeline for this.
I'll put this in our backlog and investigate later.

Thank you Kershaw!