Make use of ports in SPN optional

[karelz]

5.0 started including ports in SPN, which caused troubles to customers -- see #51701 and #51701 (total: 5 customers impacted).

Port solution from 6.0 PR #57159 to 5.0 servicing. Make the option turned on by default there to avoid breaking customers who adapted to 5.0 behavior.

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

5.0 started including ports in SPN, which caused troubles to customers -- see #51701 and #51701 (total: 5 customers impacted).

Port solution from 6.0 PR #57159 to 5.0 servicing. Make the option turned on by default there to avoid breaking customers who adapted to 5.0 behavior.

Author:	karelz
Assignees:	-
Labels:	bug, area-System.Net.Http, tenet-compatibility
Milestone:	5.0.x

[karelz]

Looks like there is not strong demand to port the fix to 5.0 servicing just yet. Closing for now.
If anyone has reasons to need it in 5.0, please reply here or on the other issue #51701. Thanks!

[MIVerTFT]

Hi.
We have a need for this port to .net 5. We started migrating to .net 5 from netcore3.1. But this Issue has made it impossible to use Linux OS.

[karelz]

@MIVerTFT can you tell us more about your deployment size?
Is it option for you to migrate directly to 6.0?

[MIVerTFT]

We do not plan to deploy to .net 5, this is a one step. The main goal is migrate to .net 6.0, but until .net 6.0 and VS 2022 are not released, we cannot start migrate to it.

[karelz]

@MIVerTFT why cannot you start migration (without deployment to production) on .NET 6 prior its release? Is it some internal limitation?
Also, note that 6.0 RC1 is around the corner (around mid-September) and it will have go-live license, making it easier to use for migrations.

[MIVerTFT]

Hmm. Yes, we can really start the migration to .net 6 rc1. For now, we will use Windows servers with .net 5.
Thanks.