Replies: 2 comments 1 reply
-
What version are you using? I wonder if this is a CORS issue, there have been some changes that automatically set CORS responses recently that may help if so. Try updating if you're not on the latest. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm having the same issue. For some reason the request is triggering the basic auth prompt. I've tried using both the "auth" object and adding the Authorization header.
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using cy.intercept to set Authorization header on my requests.
The GET works fine but for some reason the POST does not. Cypress is intercepting it properly, but the Authorization header does not seem to be getting set in the POST case.
As you can see in the screenshot, the POST intercept is getting used but the
Authorization
does not seem to be getting set. I'm getting an error from the server complaining of an empty token. If I remove the setting of the header, then I still get the same error on the server. So the error I get when I set the header is the same as when I don't. So it's as if the header is not being set.Anyone else having issues with cy.intercept and POST?
Beta Was this translation helpful? Give feedback.
All reactions