Stubbing requests via cy.intercept doesnt work the same way as cy.route

Current behavior

The request I want to stub looks like so with the old cy.route

cy.route({
			method: 'POST',
			url: '**/sessions',
			status: 200,
			response: {
				success: true,
			},
			headers: {
				'x-token': "token",
			},
		})

With this, I get the “x-token” returned as a header back to the client. alongside other headers.

connection: "keep-alive"
content-length: "16"
content-type: "application/json; charset=utf-8"
date: "Thu, 11 Feb 2021 12:58:34 GMT"
vary: "Accept-Encoding",
x-token: "token"

Trying out the new cy.intercept API,

cy.intercept('**/sessions', {
			body: { success: true },
			headers: {
				x-token: "token"
			},
		})

This is what I get back

content-type: "application/json"

Desired behavior

I expect the x-token to be part of the headers returned in the response. If Im missing anything, please let me know, thanks

Test code to reproduce

https://github.com/Tevinthuku/cypress-test-tiny https://codesandbox.io/s/modest-hofstadter-gl5xj?file=/src/App.js

Versions

Cypress v 6.4.0

[flotwig]

@sainthkh of the 3 options you’ve listed, I think it would make sense to modify (1) slightly and go with it:

Automatically append 'Access-Control-Expose-Headers': '*' to all stubbed requests. It can sometimes cause false positive.

If we only apply it to stubbed requests, like we do with the other CORS headers, it should help avoid unnecessary modification of the header.

Another issue was opened about this same confusion, so it’s probably worth fixing: https://github.com/cypress-io/cypress/issues/14654

[cypress-bot[bot]]

Released in 7.3.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to Cypress v7.3.0, please open a new issue.