Apigee HTTPTargetConnection not able to change from https to http .

[lintu_cherian]

Hello Everyone , 

 We faced SSL hand shake issue after changing target server pointing from port 443 to 80 . Backend server has published there API's on both port 80 and 443 . Curl is working fine on both port from edge Message processor . After changing from port 80 to 443 in target server configuration we started getting SSL hand shake error . On TCP dump we have observed that apigee is sending https packages to port 80 which caused a reset from target LB. We tried to print the final target URL and confirmed that the changes from http to https are not happening . Tried redeploying API and restarting message processor  , which didn't resolved issue.  Would like to know if this is a bug or expected behaviour of apigee .

We are able to point to other https port and hosts , but not to http port . Please guide.

Thank you 

@dchiesa1

[lokesh090297]

I am also facing same issue.

@dchiesa1  Can you please support!

[dchiesa1]

If I had to guess, I would say what you are observing sounds like expected behavior.  Also, it's a little strange to swap from 443 to 80. What is the business requirement for that? 

Please contact Apigee support if you would like to investigate further.

[lintu_cherian]

Hello @dchiesa1   

Thank you for the response . We were upgrading backend service's and 80 to 443 also . 

Due to some issues on upgraded server we had to roll back to old server were services where on port 80 . And then we started getting SSL handshake issue .