Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
New DevConnect members must have forum permissions in order to post messages.
If the Reply and New Post buttons are not available to you, please request access using a General Support request ticket.
Forum Index » Avaya Orchestration Designer » REST API test is not returning proper result but error   XML
 
Author Message
WilsonYu



Joined: 06/11/2013 14:29:24
Messages: 3878
Offline

I realized you are using 8.0.22. There is a patch. Please try to download it here:

https://www.devconnectprogram.com/forums/posts/list/24511.page#p162769

Look for ws08.00.22.01.p1.zip

This message was edited 1 time. Last update was at 28/09/2021 17:47:12

rajanip.instruments.com



Joined: 18/02/2021 03:42:25
Messages: 16
Offline

Hi Wilson,

This patch "ws08.00.22.01.p1" is already deployed which has the fix for the issue with "content not allowed". So now we are running into an issue where we are getting the error as "transport 415 error. content type not allowed"

We did some debugging on API end and noticed that server is receiving the content-type as "application/x-www-form-urlencoded; charset=UTF-8" instead of "application/json" what we are passing from OD end.

We even tested from SOAP UI and POSTMAN, the get request is working fine. So issue we are seeing happening when requested from OD.


Looks like OD is not passing the content-type properly as set up. We are noticing the same issue on AOD8 and AOD7.2.


Thanks ,
Rajani

WilsonYu



Joined: 06/11/2013 14:29:24
Messages: 3878
Offline

So for the Get method, this is the automatic content type we set. I thought you were using POST to send the body of json data.
rajanip.instruments.com



Joined: 18/02/2021 03:42:25
Messages: 16
Offline

Hi Wilson,

Oh ok. How can be correct this then? Can you please advise as are struck with these GET requests working?

Thanks,
Rajani
rajanip.instruments.com



Joined: 18/02/2021 03:42:25
Messages: 16
Offline

Hi Wilson,

Could you please help us on this?

You mentioned that GET is automatically sending that content type instead of what's being passed. If there is a way that this can be corrected? PLease advise.


Thanks,
Rajani
WilsonYu



Joined: 06/11/2013 14:29:24
Messages: 3878
Offline

It does not make sense that the Get request needed to be "application/json" as the content type since it does not send json data. According to Web API spec, only the Accept header is needed so that the server can send back json data.
Right now there is no way to change the content type for the Get method.

This message was edited 1 time. Last update was at 04/10/2021 14:20:52

rajanip.instruments.com



Joined: 18/02/2021 03:42:25
Messages: 16
Offline

Hi WIlson,

Now the issue is even without the content-type included in header in case of GET request, the other end is receiving the content type as "application/x-www-form-urlencoded".


Thanks,
Rajani
rajanip.instruments.com



Joined: 18/02/2021 03:42:25
Messages: 16
Offline

Hi WIlson,

Now the issue is even without the content-type included in header in case of GET request, the other end is receiving the content type as "application/x-www-form-urlencoded". PLease find attached a screenshot of the same.


Thanks,
Rajani
[Thumb - scr.png]
 Filename scr.png [Disk] Download
 Description screenshot of content type received at the other end
 Filesize 38 Kbytes
 Downloaded:  47 time(s)

This message was edited 1 time. Last update was at 05/10/2021 03:31:48

WilsonYu



Joined: 06/11/2013 14:29:24
Messages: 3878
Offline

I had mentioned that is by design. The content-type is supposed to be "application/x-www-form-urlencoded" for the GET method. Not sure why the web service has issue with it. We haven't had this problem reported before.
 
 
Go to: