Proxies for dynamic remotes do not support SSL

[sknoslo]

Current Behavior

I have an application that uses dynamic federation, and loading remotes does not work with SSL enabled during development.

#26782 introduced this new proxy for remotes to static servers, which works great, but it just doesn't take into account SSL at all.

Expected Behavior

An application that uses dynamic federation can use SSL during development.

GitHub Repo

https://github.com/sknoslo/ng-mf-ssl

Steps to Reproduce

1. Start the app with nx serve host
2. Navigate to https://localhost:4200/todo to load the todo app, you'll see the connection refused in the network devtools

Nx Report

Node           : 20.16.0
OS             : win32-x64
Native Target  : x86_64-windows
npm            : 10.8.1

nx                 : 19.5.7
@nx/js             : 19.5.7
@nx/jest           : 19.5.7
@nx/linter         : 19.5.7
@nx/eslint         : 19.5.7
@nx/workspace      : 19.5.7
@nx/angular        : 19.5.7
@nx/devkit         : 19.5.7
@nx/eslint-plugin  : 19.5.7
@nrwl/tao          : 19.5.7
@nx/web            : 19.5.7
@nx/webpack        : 19.5.7
typescript         : 5.5.4

Failure Logs

No response

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

I was able to patch startRemoteProxies to start an https server if SSL is configured for a remote, and this solves the issue. I also attempted to only serve the host with SSL, and not the remotes, but the static server itself is still started with SSL and the proxies fail to verify the secure connection because it is a self signed certificate. In the http-proxy-middleware config, I had to set secure: false to get around that.

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.