1927594 - CORP headers error is hard to understand and reuses a policy message

Status: NEW

(Core :: Networking, defect, P2)

Description

[Mike Kaply [:mkaply]]

Attachment: image.png

I encountered a CORP error today and this is what I got (see attachment):

---

Blocked Page

An error occurred during a connection to www.google.com.

---

It was only by inspecting the page and looking at network errors that I saw:

NS_ERROR_DOM_COOP_FAILED

There are two problems here.

1. This should not be reusing the enterprise policy blocked page message.
2. The message should provide more information about what is actually going on.

Comment 1

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

:valentin, since you are the author of the regressor, bug 1730494, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 2

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

Set release status flags based on info from the regressing bug 1730494

Comment 3

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

Hi Sean,
Would you have time to take this? It would be similar to bug 1890028.
We need a different error when COOP and COEP failures here and to make changes to aboutNetError.mjs and the ftl to explain the error.

Comment 4

[Sean Kim]

Attachment: Bug 1927594 - Introduce better CORP headers aboutNetError error messages r=flod,#necko

Comment 5

[Sean Kim]

Hello Valentin,

Is there a way to test NS_ERROR_DOM_COOP_FAILED? I don't see any existing tests covering this.

Comment 6

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

I think this is tested by ./mach test testing/web-platform/tests/html/cross-origin-opener-policy/coop-coep-sandbox.https.html