Response content-encoding forces to "br", causing failed response on Chrome/Edge but not Firefox

[joshuachongwdc97]

As the title suggests, I'm having trouble when i hit a cached response. But when I set "disable cache" in DevTools console it starts to work again.

Only difference i see is when its not disabled on the browser, content-encoding header returns "br". But when I disabled cached on browser (ie sending cache-control to no-cache it returns "gzip"

DId i miss something?

[joshuachongwdc97]

Just noticed chrome will not accept "br" aka Brotli as the enconding method if the API is served over HTTP.

Any workarounds for this if i do not plan on implementing HTTPS?

[tomasmck]

Seeing this also @joshuachongwdc97 - I just switched to apicache-plus from apicache. Let me know if you found a workaround.

[joshuachongwdc97]

@tomasmck, apologies on the late response. Unfortunately, the only workaround would be running your application with SSL enabled (HTTPS)