There are a lot of optional to the WithHttpEndpoint (and related) method which can be used to control various aspects of the networking stack.
Recently, I was attempting to host an external executable (the Azure SWA CLI) as an Aspire component, and it runs its own proxy which checks for the port availability before binding, but this failed as DCP already had the port bound. Upon discussions with an engineer from Aspire I learnt that we can set the isProxied property to false, then DCP doesn't proxy, and that worked.
This starts getting into the areas of advanced networking, how to configure multiple endpoints, how to read endpoint configurations, how to disable the DCP proxy feature,
Describe the issue or suggestion
There are a lot of optional to the
WithHttpEndpoint
(and related) method which can be used to control various aspects of the networking stack.Recently, I was attempting to host an external executable (the Azure SWA CLI) as an Aspire component, and it runs its own proxy which checks for the port availability before binding, but this failed as DCP already had the port bound. Upon discussions with an engineer from Aspire I learnt that we can set the
isProxied
property tofalse
, then DCP doesn't proxy, and that worked.This starts getting into the areas of advanced networking, how to configure multiple endpoints, how to read endpoint configurations, how to disable the DCP proxy feature,
Associated WorkItem - 288509