MSW fails bypassing to remote server using self-signed SSL certificate #1652
Labels
bug
Something isn't working
needs:triage
Issues that have not been investigated yet.
scope:browser
Related to MSW running in a browser
Prerequisites
Environment check
msw
versionBrowsers
Chromium (Chrome, Brave, etc.)
Reproduction repository
not possible, read reproduction steps
Reproduction steps
I theoretically could provide a reproduction repository, but I cannot provide a server with a self-signed and therefore insecure SSL certificate which is not localhost.
{ onUnhandledRequest: 'bypass' }
Current behavior
As long as I haven't opened the insecure url in the same browser and used the advanced option "Proceed to [domain] (unsafe)" the request should fail with an informative error message, without as well as with MSW enabled.
Without MSW, after I've clicked "Proceed (unsafe)", the request is executed correctly.
With MSW, after I've clicked "Proceed (unsafe)", MSW fails to execute the request producing the following log output:
(Blurred url parts contain customer and product names, but basically that is a docker instance running the backend on a specific branch via CI. That url is internal/behind a VPN.)
Expected behavior
✅ Without MSW, after I've clicked "Proceed (unsafe)", the request is executed correctly.
❌ With MSW, after I've clicked "Proceed (unsafe)", the request is executed correctly.
The text was updated successfully, but these errors were encountered: