-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues trying to adapt the rest2soap-json example to HTTPS #779
Comments
Try:
See: https://www.membrane-soa.org/api-gateway-doc/current/configuration/reference/ssl.htm |
Unfortunately, that also doesn't work. CURL also responds with a 301 here:
Judging by the logs, it sends the request to http://www.dataaccess.com:443/webservicesserver/NumberConversion.wso:
For completeness sake, here's the full log:
One thing I noticed is that this line
contains "https" but that information seemingly gets lost later on. Uneducated guess/questionLooking at what I believe to be a relevant file in the source code most code was written almost 9 years ago (or even earlier given the "CRLF -> LF" commit message). Is it possible that the REST2SOAP interceptor simply doesn't handle HTTPS correctly yet and no one noticed or at least didn't submit an issue? To me, line 293 looks especially suspicious effectively hard coding "http://". |
Hi, |
Fix is merged into main branch. |
I'm trying to get something akin to the rest2soap-json example to work.
Since the SOAP service used in that example doesn't seem to be available anymore I tried switching to another public SOAP service.
My first attempt looked like this:
proxies.xml:
request.xml:
Trying to call the API using CURL returns a 301:
Here is an excerpt from the logs:
It seems like the transformation was applied successfully as the SOAP service returns the expected response when called with the XML output:
However, api-gateway sends the request to http://www.dataaccess.com:80/webservicesserver/NumberConversion.wso rather than https://www.dataaccess.com/webservicesserver/NumberConversion.wso.
I tried several other configurations like
<target host="dataaccess.com" port="443" />
for proxies.xml with no success.Interestingly enough, even using
<target url="https://www.dataaccess.com" />
, which according to documentation should effectively overridehost
andport
attributes, didn't solve this.Apparently, it isn't even read properly when determining the request destination:
In a last attempt to get it working, I modified the source code:
If I understand the logs correctly, I believe I got to the response transformation part which then failed because my transformation is somehow
null
(the file exists in the same directory, I checked several times):I'm a bit out of ideas on how to further debug this and get the example working.
Let me know if you need any more information.
The text was updated successfully, but these errors were encountered: