Incorrect redirect to malformed url within AUT - adding `_/` in url

[hhudson]

Current behavior:

When I instruct cypress to login to an Oracle APEX application, the authentication re-directs cypress to a '404 not found' page because the authenticated URL is malformed. The malformed URL is the only issue and can simply corrected programmatically (with a find and replace command).

However - it is very important to note that the cypress login correctly returns:

1. a valid cookie
2. a valid session

which is everything you need for authentication.

Desired behavior:

Cypress, ideally, should be able to follow the same authentication redirect that a user would in a regular browser.

Steps to reproduce: (app code and test code)

I created a dummy application with dummy credentials hosted by apex.oracle.com to demonstrate:

it('Login demo', function() {
    cy.visit('https://apex.oracle.com/pls/apex/f?p=54707:LOGIN_DESKTOP')
    cy.get('#P9999_USERNAME').type('ApexUser')
    cy.get('#P9999_PASSWORD').type('Oradoc_db1')
    cy.get('.t-Button').click()
  })

The above code (which should work until the application expires in many months) will redirect to a 404 not found page with a url in the format:
https://apex.oracle.com/__/f?p=54707:1:[session_id]:::::
Outside of cypress the url will have the format:
https://apex.oracle.com/pls/apex/f?p=54707:1:[session_id]:::::

Versions

I have tested this across 4 instances of Oracle APEX (APEX 5.0, 5.1, 18.1 and 19) and this behavior is consistent.

[MaikMichel]

I face the same problem. But only when using chromium. If I use elektron, it works.

[hhudson]

I face the same problem. But only when using chromium. If I use elektron, it works.

That is very good to know. Just teste on Electron 59 to confirm that this works for my case as well. Thank you, @MaikMichel

[jennifer-shehane]

Another issue where 404 is returned due to malformed url containing /_/ #4472

[jennifer-shehane]

I can recreate this issue from the original code provided in the main comment. This is still happening in 3.3.2 pre-release version.

[jennifer-shehane]

Since this issue only exhibits itself within Chrome - we figure it is a change in Chrome that caused this issue to happen in Cypress. I also assume it is not a bug, as the issue still persists in version 77. It may be an intended change in behavior.

Narrowing down the version of Chrome that it was introduced, it was introduce in version 71.0.3572.0, specifically between commits 7e3da6dc3d7cd7eb8a55ef301026fe1ab737f814 and 56dd83c9005f68d55ddbf85c551759526b4e37cd:

• Chrome 61.0.3163.100 - PASSES
• Chrome 69.0.3452.0 - PASSES
• Chrome 71.0.3572.0 - PASSES = Base = 597039 7e3da6dc3d7cd7eb8a55ef301026fe1ab737f814
• Chrome 71.0.3572.0 - FAILS = Base = 597057 56dd83c9005f68d55ddbf85c551759526b4e37cd
• Chrome 72.0.3583.0 - FAILS
• Chrome 73.0.3683.0 - FAILS
• Chrome 74.0.3729.0 - FAILS
• Chrome 77.0.3833.0 - FAILS

⭐️ Changelog where issue was introduced

@flotwig good luck 😅