Cypress test: Infinitely appended iframe and HTTP error 414 - Request URL too long when Microsoft login, and page load timeout #25679
Replies: 7 comments 1 reply
-
Try setting |
Beta Was this translation helpful? Give feedback.
-
I'm also having this issue, I've tried setting I setup a new project and tried visiting the Microsoft Login page. This is where the error seems to be. Also, there is a discrepency in the documentation about where to put the
https://docs.cypress.io/guides/guides/web-security#Modifying-Obstructive-Third-Party-Code
|
Beta Was this translation helpful? Give feedback.
-
@semics-tech @dphoenix @jahunsbe-sj did you guys find solution to it ? I am facing same issues... |
Beta Was this translation helpful? Give feedback.
-
I had the same problem but was able to solve it like this: |
Beta Was this translation helpful? Give feedback.
-
I have the same issue, but using SAML and not Oauth2.. if anyone has the solution, let me know :/ |
Beta Was this translation helpful? Give feedback.
-
Same error here |
Beta Was this translation helpful? Give feedback.
-
Can anyone please help in resolving this issue? |
Beta Was this translation helpful? Give feedback.
-
Hello,
I am testing login for a site. The login button redirects to a Microsoft login page when clicked.
Originally I had a frame busting problem, where the test would redirect outside of the Cypress framework, but solved that with the
experimentalSessionAndOrigin
attribute.However, now I am facing two new errors.
First, I get an HTTP 414 error, with the URL being too long when Cypress clicks on the button. I noticed that when I looked at the URL in the failure message, it seems that the url seems to have an
iframe-request-id
query parameter infinitely appended to the URL string, so I see why the URL is too long. I just don't know why that string is appended like that.I should also note that the URL in the code is generated as an anchor tag, with the href element being a Vue a property.
Also, and I noticed this in a few other tests as well when clicking to a new page, I get a page load timeout error. I can understand that for the infinitely long URL, but my issue is that I set the pageLoadTimeout configuration setting to something insanely big (like 9e+67ms, just to make sure there's enough time). And the timeout error happens after only a second or so. I get this error with another page as well, which is a Vue route, and which does eventually load.
Also, the web portal I am testing is on my local computer, it's a Vue application that is dockerized.
Any ideas about where I start looking? I can't really share a lot of the actual code because it's not mine and kind of private, but I can try to maybe mask some of it.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions