ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » REST Request node can use gzip compression / encoding?

Post new topic  Reply to topic
 REST Request node can use gzip compression / encoding? « View previous topic :: View next topic » 
Author Message
ghoshly
PostPosted: Mon Dec 12, 2022 9:43 am    Post subject: REST Request node can use gzip compression / encoding? Reply with quote

Partisan

Joined: 10 Jan 2008
Posts: 325

Hello,

I am currently using IIB v10.0.0.25 in AIX 7.2 environment where I have to perform a REST API call to an API hosted din MS Azure environment.

I am able to perform HTTP GET operation to fetch data, however in case of HTTP PUT, I am getting different errors while using HTTP Request node or REST Request node. The external API mandates to use gzip encoding and compression.

Code:

      SET OutputRoot.HTTPRequestHeader."Content-Type"             = 'application/json'; -- 'application/json;charset=UTF-8';
      SET OutputRoot.HTTPRequestHeader."Content-Encoding"          = 'gzip';
      
      SET OutputRoot.HTTPRequestHeader."Accept"                = 'application/json';      
      SET OutputRoot.HTTPRequestHeader."Accept-Encoding"         = 'gzip,deflate';



When I am using HTTP Request node, Azure Gateway doesn’t have an entry for "host_s" for PUT request so it doesn’t know how to route it. We are getting HTTP 400 as Bad Request.
When I am using REST Request node to perform the same HTTP PUT operation, it does register "host_s", but we are getting HTTP 500. Error detail shows "ERROR: The archive entry was compressed using an unsupported compression method."
I am able to send request successfully using REST request node, if the API disables the gzip requirement temporarily, but that is not the expectation for Production environment.

Though URL below mentions about HTTP and SOAP nodes, I believe REST nodes also do support gzip compression as the options are available in the node. Would anyone with similar experience can help me to move forward? Which way we can take trace to show IIB is sending the data correctly.
https://www.ibm.com/docs/en/integration-bus/10.0?topic=flows-using-compression-http-soap-nodes
Back to top
View user's profile Send private message
ghoshly
PostPosted: Mon Dec 12, 2022 10:58 am    Post subject: cURL command works with gzip Reply with quote

Partisan

Joined: 10 Jan 2008
Posts: 325

We can send data (HTTP PUT) successfully using cURL along with gzip which shows the API working as intended, but I am unable to make it work via HTTP Request node or REST request node. Is there a way to check which gzip version being used in IIB v10?
Back to top
View user's profile Send private message
ghoshly
PostPosted: Fri Dec 16, 2022 9:56 pm    Post subject: resolved... Reply with quote

Partisan

Joined: 10 Jan 2008
Posts: 325

What we found, the second line of code where we are setting the Content encoding with "gzip" value is causing the issue. Instead if we comment that line, we are able to invoke the API successfully.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » REST Request node can use gzip compression / encoding?
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.