on 2013 Jun 24 11:35 AM
Hy to all,
we've registered a service from a backend system via the transaction /IWFND/MAINT_SERVICE.
We are able to call the service on the gateway, but something is strange:
When i call the service-definition-document via HTTP, for example: http://mygateway/sap/opu/odata/sap/ZDEMO1_SRV/
we noticed that the WSDL-file contains always the HTTPS ports instead of the HTTP ports,
<?xml version="1.0" encoding="utf-8" ?>
<app:service xml:lang="en" xml:base="https://mygateway:8002/sap/opu/odata/sap/ZDEMO1_SRV/" xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:sap="http://www.sap.com/Protocols/SAPData">
<app:workspace>
<atom:title type="text">Data</atom:title>
<app:collection sap:pageable="false" sap:addressable="false" sap:content-version="1" href="Flights">
<atom:title type="text">Flights</atom:title>
<sap:member-title>Flight</sap:member-title>
</app:collection>
</app:workspace>
<atom:link rel="self" href="https://mygateway:8002/sap/opu/odata/sap/ZDEMO1_SRV/" />
<atom:link rel="latest-version" href="https://mygateway:8002/sap/opu/odata/sap/ZDEMO1_SRV/" />
</app:service>
During the remote service registration there was never a popup or something which asked us which port we
want to use for this specific service.
Has anyone an idea why the HTTPS ports are used here?
Request clarification before answering.
Check the tab "logon data" -> "security requirements" in transaction SICF.
But in my opinion the question has to be: why do you prefer HTTP? If the HTTPS request works all is fine (and secure!)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is getting redirected by the server. Eventhough you make a http call, server redirects them to https port.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
thanks for your input - do you know if there's a way to disable this redirect to HTTPS? Or does this redirect always occour if HTTPS port is configured on the system?
We found out one more thing: this behaviour does occour just for services registered from an remote system - local services provide the HTTP protocol and ports...
best regards,
andreas
| User | Count |
|---|---|
| 13 | |
| 8 | |
| 6 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.