The purpose of https+http when using service discovery..

[dozer75]

In the documentation an example is used of https+http, what's the purpose of that?

I was under the impression that if the endpoint had this, it should first check for a https endpoint and then a http in the configuration if there is no configured https and then generate a URL based on that? But whenever I try this it always resolves the scheme to https (even if the configuration contains http only). I debugged myself down and here it seems that it just takes the first entry (in my example https), so as far as I can see, the statement https+http doesn't have any effect? It's always the first of the schemes defined?

I feel that there is something I'm missing around this, so if anyone can explain this it would be nice. I can't really find anything in documentation.

Here is the configuration I'm using and an example code:

appsettings.json

{
  "Services": {
    "pvlib": {
      "http": [
        "localhost:18080"
      ]
    }
  }
}

Code:

builder.Services.AddHttpClient("MyClient").ConfigureHttpClient(static client =>
{
    client.BaseAddress = new("https+http://pvlib");
});

I thought this should result in using http://localhost:18080 as it found a http entry but no https entry, but it uses https://localhost:18080...

[PaulKlein]

I ran into this as well. I found that it does work if you put an explicit scheme in the config file, e.g.

{
  "Services": {
    "pvlib": {
      "http": [
        "http://localhost:18080"
      ]
    }
  }
}

[dozer75]

Yes, I found that as well later on, but IMHO it feels a bit strange doing that and I felt it was a bit unnecessary, but I am using the protocol now...