tracker issue : CF-4195486

select a category, or use search below
(searches all categories and all time range)

Content encoding is not passed in response header.

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): / ext-user (Poonam Jain)

Created: 10/06/2016

Components: API Manager, Response Compression

Versions: 2016

Failure Type: Non Functioning

Found In Build/Fixed In Build: 300452 / 300740

Priority/Frequency: Critical / All users will encounter

Locale/System: English / Linux All,Mac 10 All,Solaris All,Win XP All

Vote Count: 0

Content encoding is not passed in response header. For a resource publisher can specify request encoding parameter. While trying out the API, the provided request encoding should be sent to browser by API manager.
PFA the snapshot for this.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4195486

External Customer Info:
External Company:  
External Customer Name:  
External Customer Email:



Test this fix for newly created APIs
Comment by Uday O.
1669 | October 26, 2016 04:28:09 AM GMT
This is fixed in latest build. 300740. Marking the bug as closed->fixed.
Comment by Poonam J.
1670 | October 26, 2016 11:28:41 PM GMT