React web socket not working when using Yarp resource on HTTPS profile

[Kralizek]

I have a AppHost that uses the Yarp resource, a React application for the frontend and some backend applications. If I use the HTTPS profile, the changes are not reflected automatically in the browser. Everything works fine when working with the HTTP profile.

Here is a screenshot of the resource view of my repro

Here is my AppHost Program.cs

using Aspirant.Hosting;

var builder = DistributedApplication.CreateBuilder(args);

var web = builder.AddNpmApp("web", "../../web")
    .WithHttpEndpoint(env: "PORT")
    .RunWithEnvironment("BROWSER", "none");

var isHttps = builder.Configuration["DOTNET_LAUNCH_PROFILE"] == "https";

builder.AddYarp("ingress")
    .WithEndpoint(scheme: isHttps ? "https": "http", port: 11400)
    .WithReference(web)
    .LoadFromConfiguration("ReverseProxy");

builder.Build().Run();

And appsettings.json

{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.AspNetCore": "Warning",
      "Aspire.Hosting.Dcp": "Warning"
    }
  },
  "ReverseProxy": {
    "Routes": {
      "web": {
        "ClusterId": "web",
        "Order": 1,
        "Match": {
          "Path": "{**catchall}"
        }
      }
    },
    "Clusters": {
      "web": {
        "Destinations": {
          "web": {
            "Address": "http://web"
          }
        }
      }
    }
  }
}

PS: I'm perfectly fine working on the HTTP profile. I'm reporting this because it could have effects somewhere else.

[DamianEdwards]

Node.js doesn't honor the hosts OS's certificate trust settings as it embeds its own copy of OpenSSL so you have to configure the client HTTP stack in your Node.js apps to either trust the ASP.NET Core developer certificate or disable cert verification.

See examples from the samples repo:

• https://github.com/dotnet/aspire-samples/blob/3c2a1724b7e2d028e30d560e713d674cbb681331/samples/AspireWithJavaScript/AspireJavaScript.React/webpack.config.js#L16
• https://github.com/dotnet/aspire-samples/blob/3c2a1724b7e2d028e30d560e713d674cbb681331/samples/AspireWithJavaScript/AspireJavaScript.Angular/proxy.conf.js#L6
• https://github.com/dotnet/aspire-samples/blob/3c2a1724b7e2d028e30d560e713d674cbb681331/samples/AspireWithJavaScript/AspireJavaScript.Vue/vite.config.ts#L24
• https://github.com/dotnet/aspire-samples/blob/3c2a1724b7e2d028e30d560e713d674cbb681331/samples/AspireWithNode/AspireWithNode.AppHost/Program.cs#L18-L19

[Kralizek]

Oh nice! Thanks!

The weird thing is that the web socket from the first screenshot uses a port that is not listed anywhere.