Trace logs shows HTTP when Target server with HTTPS endpoint is used

[snehal_chakrabo]

Hi All,

I saw that this was an existing bug. I still see a http url in the trace even though target server has https endpoint. Is it still open?

Regards

Snehal

[Feroz_Mahammad]

@snehal chakraborty, check the port used while creating Target Server. It should be 443 for HTTPS.

[snehal_chakrabo]

Yes port is 443 and enabled attribute in sSSLInfo object of the target server is also true. More over the endpoint works only and https, and the call outs work fine. I saw an old post that there was a bug on the Edge UI on cloud where the https endpoint would show up as http in the trace log. Hence was interested to know if its still a bug.

[sreenivas_sp]

hi There,

Am also facing the same issue and am getting target server callout failure due to SSL failure.

Is this still a bug in the Cloud version ??

Regards,

Sreenivas S P

[mark_hammelman]

I found this post because I'm seeing this problem, so yes, still a bug as of May 14,2018

[#6]

Hi,

i've got the same problem. It is resolved ?

Regards,

[#7]

Same issue here, https only configured targetserver shows up as http in Edge UI traces. This issue is years old. Is a security related issue not worth fixing?

[mark_hammelman]

For what it's worth, after I saw the problem, I verified that the connection does in fact use "https", so I don't see it as a "security related issue." The trace just shows you that it used "http" instead of "https", so its more of a user-interface issue specific to trace output.

[#9]

Maybe it is fine when one or two people run a gateway but for larger deployments we cannot assume that everyone is intimately familiar with every bug in Apigee. I just had to look at some traces and got really worried that someone stuffed up the target server. Started to check configuration, make screenshots and description to file a bug with support just to then come across this old issue again. Stole 20 minutes of my time 😞 ... N

[anuprai]

Is this issue resolved? I can still see http in trace log even though https is configured in target server.