Create secure named target

Google Cloud Apigee
1

Hi,

When creating a named target server, I noticed that when sending the content in application/json, the SSLInfo → “enabled” : true was not taken into account.

When I do the same action using text/xml as content-type it does work (i.e. set the SSLInfo attrbute named “enabled” to true. Did I do something wrong or is this an issue?

EDIT: Even though SSLInfo is set to true on the target server entry, I see the call to the backend is made towards http instead of https on the Trace tool.

EDIT2: Basically the same issue as the edit here above, but also when the API call to the backend is displayed as http when the backend even doesnt work with http (but only https). Is that a Trace tool issue?

thanks,

Guy

2

@GuyH

First, it works with both application/json and text/xml.

Second, it is an Apigee trace tool issue. If you have configured your named target server with an IP and Port, the trace tool would not also show the port number but only the IP.

Disclaimer: This is my personal experience with working on Apigee Platform for more than a year now and i am not an Apigee employee.

1 Like