HTTP 502 errors occurring

danielhoenig
Participant III

We are seeing 502 response codes with the message of messaging.adaptors.http.flow.DecompressionFailureAtResponse. This is a new proxy we setup and it's not doing anything except routing the call to the backend URL. There are no policies or anything else setup on it right now.

My question is, what's causing this error? Is it Apigee failing when the response comes back or is it in a downstream API?

Solved Solved
0 3 402
1 ACCEPTED SOLUTION

sidd-harth
Participant V

Apigee Edge takes care of all compression automatically. I guess the downstream API is giving the error. Did you check the trace session? Did you test the API through Postman?

If you are sending the request with a Content-Encoding gzip header and with unzipped data as payload then Apigee is going to throw DecompressionFailure error.

https://docs.apigee.com/api-platform/reference/endpoint-properties-reference#targetendpointtransport...

View solution in original post

3 REPLIES 3

sidd-harth
Participant V

Apigee Edge takes care of all compression automatically. I guess the downstream API is giving the error. Did you check the trace session? Did you test the API through Postman?

If you are sending the request with a Content-Encoding gzip header and with unzipped data as payload then Apigee is going to throw DecompressionFailure error.

https://docs.apigee.com/api-platform/reference/endpoint-properties-reference#targetendpointtransport...

Thanks for the info! I'm meeting with the dev team to review this error so I'll have them check the header and see if that's the case.

It looks likes it was the Content-Encoding header was set to gzip but no data was being passed.