-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Invalid header content crashes Cypress #1420
Comments
Just I'm not sure what the correct behavior should be. Setting invalid header content is not something "you can just force" but it's possible the user agent handles this by stripping it, ignoring it, etc. I'd have to see what chrome does. |
Issue is with a request to 3rd party endpoint, so I'm isolating that first. Will post HAR when I can. |
Hi @ScottMaclure, do you have an update on this? Will have to close otherwise. |
Apologies, no longer active, closing. |
I'll update the below with more information when I can.
Is this a Feature or Bug?
Bug
Current behavior:
Testing a site, Cypress crashes with the following express error:
Desired behavior:
Cypress deals with this gracefully and alerts the dev there was a problem with malformed header content (i.e. "go fix the app" moment).
Check version of express bundled with Cypress and upgrade?
How to reproduce:
TODO - reproduce outside of client site and post here.
Test code:
// was a form submit off a click()
Additional Info (images, stack traces, etc)
The text was updated successfully, but these errors were encountered: