2477965 - Seeing a FATAL error in the SMP server log when connecting to a Odata service

• An application tries to connect to an external OData endpoint using the SMP 3.0 server.
  The system proxy is enabled and verified to be working correctly for this application.
  After a successful registration, when attempting to retrieve the service document a 500 internal server error appears on the client side.
•  The SMP server log shows:  
  #2.0#2017-05-17 11:59:27 AM#WARNING#RequestResponse###Proxy#1495036767450254#f4dad3d6-3e46-4fb4-8127-215b5f0de15b#com.cintas.dynamics.test#com.sap.mobile.platform.server.proxy.core.handler.DirectProxy:handleException#xxxxxxxxxxxx#######800#####----------Caught the exception in GWProxy Handle---------#
  #2.0#2017-05-17 11:59:27 AM#FATAL#Proxy####1495036767465000#f4dad3d6-3e46-4fb4-8127-215b5f0de15b#com.cintas.dynamics.test#DirectProxy:handle#xxxxxxxxxxxx#######800#####Error occurred while forwarding the request to Gateway Cannot cast class com.sap.mobile.platform.server.online.common.connectivity.http.base.HeaderImpl to class java.lang.String : {"endPoint":"https://xxxxxxxxxxxx.crm.powerobjects.net/api/discovery/v8.2/","requestURL":
  "http://xxxxxxxxx.xx.xxxxxxx.com:8000/com.xxxxxx.xxxxxxxxx.test/","miscInfo":"Proxy Request Response","source":"SMP Server : Proxy","version":"1.0","responseCode":"500"}#

•  SMP 3.0 SDK SP13 PL07

HTTP Auth Header 500 Internal , KBA , MOB-ONP , SAP Mobile Platform on Premise , Problem