-
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
Content-Type and other headers missing in gRPC requests in Cypress with Connect-ES #28849
Comments
Does it worked in previous cypress version ??? |
seems not related to previous version. this was cleared by either:
In the end we changed to WebTransport and disabled the experimentalFetchPolyfill as well. |
Hey @jennifer-shehane any opportunity to get some attention from Cypress? I am trying my best to figure out the situation but I am not sure what else to try. The changes suggested by @robertwenquan didn't work me |
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided. |
This issue has been closed due to inactivity. |
Current behavior
In Cypress E2E test, a few HTTP headers are not set.
Specifically,
Content-Type
header is not set along with other headers with running with cypress that lead to 415 Content not supported error returned from the API gateway.The request doesn't reach the API server bacause of this.
Desired behavior
Content-Type
and other headers are set just like it behaves in a normal Chrome browser.Test code to reproduce
Cypress Version
13.6.3
Node version
v20.10.0
Operating System
macOS 14.2.1 (23C71)
Debug Logs
No response
Other
Browser console
Running console
Business Logic code
Expected Good Behavior on a regular browser
The behavior with cypress:open
missing headers with cypress
The text was updated successfully, but these errors were encountered: