Error Unsupported Encoding "br" apigee

red13
New Member

Hi, I'm testing my API Proxies configuration but i have a encoding issue.

Error:
Unsupported Encoding "br"

ErrorCode:

protocol.http.UnsupportedEncoding

Header:
Accept-Encoding = gzip,deflate,br.

If I only use gzip and deflate i dont have problems, but with br is the issue.

The target endpoint of api proxy is https://$url.com

Solved Solved
0 6 1,517
1 ACCEPTED SOLUTION

I think your question has been asked before.

try searching the community.

BTW I think the Brotli encoding is primarily used for fonts.

If that's true, it means if you are experiencing this error, you are probably trying to use Apigee as a proxy in front of a website, rather than a proxy in front of an API. That's not what Apigee is intended to be used for. If you're trying that, you may experience other problems as well.

View solution in original post

6 REPLIES 6

I think your question has been asked before.

try searching the community.

BTW I think the Brotli encoding is primarily used for fonts.

If that's true, it means if you are experiencing this error, you are probably trying to use Apigee as a proxy in front of a website, rather than a proxy in front of an API. That's not what Apigee is intended to be used for. If you're trying that, you may experience other problems as well.

Thanks, but i use the apigee proxy to my APIS (backend) that is deployed on GKE. So, i have this configuration:

Target Endpoint: URL of BACKEND

Proxy Endpoints: All the Methods and Paths of my APIS

The only solution that i found is create a policy to that... but is not the idea.

ok that's clear.

you can set the accept header within the proxy. Have you tried that?

Something in the backend (in GKE) is generating br. See if you can negotiate that to stop.

I have the same problem when I hit the api end point directly I am fine. When I set up as a target for an Apigee proxy I get the same error. Why?

tried to create a new post but got errors statement with no visible error

red13
New Member

I finded that the Postman use header encoding br, so if you delete that value on the header, the request pass without problem.


Other solution is use a Target Endpoint in your proxy configuracion without https connection.