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 » Search

 Search found 6 matches
Author Message
  Topic: "Content-Encoding=gzip" not enough to make WSReply
AntonBricina

Replies: 13
Views: 9230

PostForum: WebSphere Message Broker (ACE) Support   Posted: Wed Jan 25, 2017 6:54 am   Subject: Re: Http Reply not compressing response
Post the link, so people who agree with you (and can't / won't use the solution outlined by @Craog B can vote for it.

Votes mean upgrades.

with the account that I created the RFE with
  Topic: "Content-Encoding=gzip" not enough to make WSReply
AntonBricina

Replies: 13
Views: 9230

PostForum: WebSphere Message Broker (ACE) Support   Posted: Tue Jan 24, 2017 8:52 am   Subject: Re: Http Reply not compressing response
Did you raise PMR for this? was there any outcome?
The result of the PMR was that "this feature is not part of the product" and the product "works as designed"

Problem Summary: ...
  Topic: Multiple execution groups or multiple MQInput ndoes ?
AntonBricina

Replies: 15
Views: 14280

PostForum: WebSphere Message Broker (ACE) Support   Posted: Fri Oct 14, 2016 1:35 am   Subject: Re: Multiple execution groups or multiple MQInput nodes
kernel threads can exploit more than one CPU, while user threads (within a single process) cannot.
kernel threads can exploit more than one CPU, while user threads (within one kernel thread) cannot
...
  Topic: "Content-Encoding=gzip" not enough to make WSReply
AntonBricina

Replies: 13
Views: 9230

PostForum: WebSphere Message Broker (ACE) Support   Posted: Mon Nov 30, 2015 12:25 am   Subject: "Content-Encoding=gzip" not enough to make WSReply
The HTTP reply node should handle the necessary instructions in the message it's given. For those things the documentation says it does.

compression or gzip

We will open a PMR to clarify with I ...
  Topic: "Content-Encoding=gzip" not enough to make WSReply
AntonBricina

Replies: 13
Views: 9230

PostForum: WebSphere Message Broker (ACE) Support   Posted: Fri Oct 30, 2015 12:34 am   Subject: "Content-Encoding=gzip" not enough to make WSReply
What's the WSReply-Node?

Sorry, my bad... I rechecked here,... we use the can send a HTTP-Request (and put in the 'flag' to request a compressed reply)

2. We can receive (and decompress) compres ...
  Topic: "Content-Encoding=gzip" not enough to make WSReply
AntonBricina

Replies: 13
Views: 9230

PostForum: WebSphere Message Broker (ACE) Support   Posted: Thu Oct 29, 2015 7:25 am   Subject: "Content-Encoding=gzip" not enough to make WSReply
Dear IIB-Experts,

we have a requirement, where we need to send a compressed payload in a response to a SOAP-request. I have set a HTTP-Header "Content-Encoding=gzip" and in SOAP-UI I can ...
Page 1 of 1

Jump to:  
Protected by Anti-Spam ACP
 
 


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

Copyright © MQSeries.net. All rights reserved.