Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Extend the 'RequestMock: CORS validation failed for a request specified as <filter rule>' warning #5854

Open
miherlosev opened this issue Jan 8, 2021 · 2 comments
Labels
AREA: docs An issue related to the product documentation. TYPE: enhancement The accepted proposal for future implementation.

Comments

@miherlosev
Copy link
Collaborator

At present:
image

Need to add a phrase how to fix this warning.
For example such a phrase:
To fix this warning specify the necessary CORS headers in respond method. For more detail see https://devexpress.github.io/testcafe/documentation/reference/test-api/requestmock/respond.html URL.

@miherlosev miherlosev added the AREA: docs An issue related to the product documentation. label Jan 8, 2021
@AndreyBelym AndreyBelym added the TYPE: enhancement The accepted proposal for future implementation. label Jun 7, 2021
@lonely-caat
Copy link

@miherlosev what are actually the right headers to use when this error pops up?

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Jun 9, 2021
@VasilyStrelyaev
Copy link
Collaborator

The server response should have the Access-Control-Allow-Origin header that indicates that cross-origin access is permitted. You can find other headers that can be included in the server's response in the HTTP response headers section.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Jun 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AREA: docs An issue related to the product documentation. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

4 participants