Hi,
Context path of POST request URLs of APIs get dropped at the gateway when
invoked with the content-type 'text/xml'.
I have reported the issue under [1].
Please look into this.
[1] - https://wso2.org/jira/browse/APIMANAGER-2256
Regards
*Asanthi Kulasinghe*
WSO2 Inc; http://www.wso2.com/.
Its not that it alters request urls, it drops the request parameters from
the outgoing request when the Content-Type is text/xml.
If the API context is: /stockquote/1.0.0
Endpoint is: http://host:port/StockQuoteService
Request url is: /stockquote/1.0.0/getQuote
In the case of applcation/xml,
Hi Nuwan,
Isn't this a bug? When we tested this we used a RESTful service (starbucks
sample) as the back end. And you can't expect the client would always send
application/xml as the Content-Type when calling a rest backend. Sending a
text/xml is totally valid when calling a RESTful backend.
I'm sure this has been done deliberately in synapse. If so we need to know
why exactly. Will it break proxying SOAP 1.1 services if we allow these to
be passed to the back-end?
The defined standards for the Content-Type are as follows
SOAP 1.1 - text/xml
SOAP 1.2 - application/soap+xml
POX -
