Ignore port when using UpstreamHost option

[grssmnn]

Fixes

I wanted to use the UpstreamHost option and found out that Ocelot is handling the port as part of the hostname (when running on a different port than :80/:443). For my understanding this is not the expected behaviour since any other software like nginx or traefik ignore the port when talking about the hostname.

[raman-m]

Hi Kevin!

What issue is this PR related to?

[raman-m]

@grssmnn
https://ocelot.readthedocs.io/en/latest/features/routing.html#upstream-host
#209
The links above are the context.

I cannot get your proposal!.. You compare nginx & traefik but they are different networking tools than Ocelot.
If you want to ignore the port for Ocelot deploying scenario then just use fix from #209 via specifying pure domain name in Upstream Host property of the route.
If your Ocelot hosting scenario uses a port, just do not specify Upstream Host property.
If your Ocelot hosting scenario doesn't use a port, just specify the host value of registered domain name. If you have localhost scenario, just register extra domain via OS functionality and web server.
But I cannot imagine multiple Ocelot gateways at one web hosting without special domain name registration.

Could you describe your user scenario please?
It seems it can be a new feature of Ocelot, but with rare usage.

[raman-m]

@grssmnn commented on Aug 19, 2021

Specifying different ports for Upstream of routes will be completely different Ocelot's feature. Would you like to open new discussion as an issue? 😉

But your small fix cares about the hostname...
Is it the problem?
How does it influence to your user scenario?