Dynamic Forward Proxy: No endpoint added to cluster with same IP but different port

[Coconut105]

Hi,

I have configured a cluster that uses dynamic forward proxy and also EDS. If I send requests to envoy with the same FQDN but different ports, only the first resolved IP and port are added in the endpoints of the cluster. Eg:

1. Request: google.com:80 -> Endpoint: 10.0.0.1:80 added to cluster
2. Request: google.com:8081 -> 503 Service unavailable

In the envoy logs I can see a cache hit for the second request and then request is sent to endpoint with port 80 instead of 8081. The second endpoint is not added to the cluster. I believe this is a bug.

[ntgsx92]

I encountered similar situation while trying out DynamicForwardProxy filter. The underlying DNS cache used by the filter will only use either port 80 or 443 depends on whether TLS connection is needed.

I think the reason why this was implemented this way is that Envoy currently doesn't support SRV record lookup from the DNS server which means no port number will be returned. Once this issue is resolved, we should be able to use IP address plus the port returned from the DNS server and establish connection with the clusters.

[Coconut105]

Hi again,

I still see the same problem though when, for example, first request uses port 80 and second request uses port 443.

[Sooryaa-A]

Any update on this. It seen in 1.16.1 envoy version that, though url is http , the default port getting sed is 443 some times.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.