,Even after removing "content-Encoding header " from apigee response using assign message policy .We are getting the same header in postman/sopui ,but couldnot be seen in apigee trace .Due to this source team is unable to proccess response from apigee.

[cjking]

Removing the Content-Encoding header won't magically change the encoding of the HTTP body.

If your client has requirements about the response encoding, I would suggest setting a Accept-Encoding: header on the request.

[davidwallen]

As CJ says, removing the content-encoding header does not change the response, in fact the underlying server infrastructure will reinject the header as you are experiencing. I am curious what it is about the specific encoding that is causing your consumer to not be able to process the response. Typically the underlying http client handles the decompression (assuming gzip, deflate, etc). What encoding does your client require? Are they including an accepts header on the request?

[Ajitav]

This by default goes from the rest client. Can you try the curl request from a terminal instead of postman/soap UI?