Stubing response headers with cy.intercept doesn't work

Current behavior

I recently upgraded to 6.3 and tried to use the cy.intercept API. So I followed this article for stubbing a response

According to the test runner and the network tab, the fetch request get caught and is stubbed but in my app code the header is not there in the code.

I’ve created a repo to reproduce the bug but here is a quick piece of code of how I’m intercepting the request :

// index.spec.js
  it("", () => {
    cy.intercept("/toto", {
      statusCode: 200,
      body: "Toto",
      headers: {
        foo: "bar",
      },
    }).as("fetchToto");

    cy.visit("/");

    cy.wait("@fetchToto");

    cy.contains("The header was found");
  });

// index.js
const testFetching = async () => {
  const response = await fetch("https://adomainthatdoesntexist.com/toto");
  const text = await response.text();

  const expectedHeader = response.headers.get("foo");

  console.log("expectedHeader", expectedHeader, text);

  if (expectedHeader === "bar") {
    const div = document.createElement("div");
    div.innerText = "The header was found";

    document.body.appendChild(div);
  }
};

testFetching();

Desired behavior

I expect to be able to stub the response headers.

Test code to reproduce

I created a repo to reproduce the bug : https://github.com/TomPradat/cypress-response-stub-headers-not-working

To run the test:

• yarn install && yarn start
• yarn cypress:open

Versions

I’m using Chrome 88, cypress 6.3.0 (latest right now), OSX 10.15.7

[flotwig]

@TomPradat this looks like it will not work, since foo is not in access-control-expose-headers, it will not exist in Response.headers: https://stackoverflow.com/a/54928828/3474615

How’s this work for you?

// index.spec.js
  it("", () => {
    cy.intercept("/toto", {
      statusCode: 200,
      body: "Toto",
      headers: {
        foo: "bar",
        'access-control-expose-headers': 'foo'
      },
    }).as("fetchToto");

    cy.visit("/");

    cy.wait("@fetchToto");

    cy.contains("The header was found");
  });

[TomPradat]

Yeap I’m confirming it works with the access-control-expose-headers, I totally missed that 👍

I’m closing this issue as a consequence