Using Named target server without SSL

I have a proxy that checks the AccessToken and passes through the request to the backend server. It works well when the `<TargetEndpoint>`uses the URL of a GCP internal load balancer. 

```

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TargetEndpoint name="default">
<Flows/>
<PostFlow name="PostFlow">
<Request/>
<Response/>
</PostFlow>
<HTTPTargetConnection>
</HTTPTargetConnection>
</TargetEndpoint>
```

I want to use the same proxy in multiple environments, so I setup a named target server that uses the same GCP internal load balancer IP as the host and has SSL disabled. 
```
{
host: 10.x.x.x,
ssl: disabled,
protocol: http,
port: 80,
name: named-target-1
}
```

When I this named target server in my proxy using a load balancer, it fails with the following error
```
Unrecognized SSL message, plaintext connection?
```

Here's the proxy config with named server
```

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TargetEndpoint name="default">
<Flows/>
<PostFlow name="PostFlow">
<Request/>
<Response/>
</PostFlow>
<HTTPTargetConnection>
<SSLInfo>
    <ClientAuthEnabled>false</ClientAuthEnabled>
    <Enabled>false</Enabled>
    <IgnoreValidationErrors>true</IgnoreValidationErrors>
</SSLInfo>
<LoadBalancer>
    <Server name="named-target-1"/
    </LoadBalancer>
    </HTTPTargetConnection>
</TargetEndpoint>
```

As shown above, I've disabled SSL in the HTTPTargetConnection config too. 

Aim is to pass the request over insecure (HTTP) connection to the internal load balancer that runs a K8s service behind it. 

 

3 0 125
0 REPLIES 0