Contracts should be serializable/deserializable using System.Text.Json

[chandramouleswaran]

Describe the bug

Contracts should be serializable/deserializable using System.Text.Json
public ProxyMatch Match { get; private set; } = new ProxyMatch();

Private setters are not supported by System.Text.Json

To Reproduce

Try to read the ReverseProxy configuration with System.Text.Json - Match object is created but has null values for all properties.

Further technical details

• Include the version of the packages you are using - 1.0.0-preview.4.20373.1
• The platform (Linux/macOS/Windows) - Windows

[samsp-msft]

Why are you trying to serialize the configuration? If what you are trying to do is to dynamically manage the routes, then that will be handled by a new API that is being built as part of #8.

[Tratcher]

Though serialization may come in handy even in the #8 scenario. You've got to store the data in some format.

[chandramouleswaran]

Having the feature you have pointed to is useful - in the meantime, we are serializing the dynamically discovered route and updating a JSON which is part of the config management system.

[samsp-msft]

We should revisit after we have completed #8. Object Model is likely to change as part of design of #8, so we should reassess after design and see whether they are suitable for serialization.

[Tratcher]

@jkotalik and @davidni, you are both successfully serializing and deserializing the models using System.Text.Json as part of your providers, correct?

The only values I'm aware of that wouldn't be serializable are:
X509Certificate2 ProxyHttpClientOptions.ClientCertificate
Encoding ProxyHttpClientOptions.RequestHeaderEncoding

We should add a regression test for this scenario, and decide what to do about the two properties above.

[Tratcher]

Other unsupported types I found in testing:

• TimeSpan - Used by health checks, request timeouts - Added JSON converter for TimeSpan dotnet/runtime#51492
• Version - Use for protocol version - Added VersionConverter dotnet/runtime#41384