Don't show the Cypress error page on network errors #4101
Labels
pkg/server
This is due to an issue in the packages/server directory
topic: network
type: unexpected behavior
User expected result, but got another
When a request is proxied through Cypress and there is a network error, currently we send a valid HTML response with a 500 status code:
This causes issues when users expect their applications to behave like the real world.
Current issues include:
Can't set headers after they are sent.
error thrown #957 - Cypress tries to inject the HTML mid-response-streamIf we don't send that error anymore, then there's no issue. We should just kill the browser-facing socket and let users handle the network error in application code.
We should still retain the old error for failed file requests, since we stand up a web server for them and can serve 404's or what have you:
The text was updated successfully, but these errors were encountered: