Can't intercept html in response body about express-http-proxy HOT 3 CLOSED

I also ran into this. It turned out gzip was the culprit for me.
I added this:

decorateRequest: function ( req ) {
    req.headers[ 'Accept-Encoding' ] = 'utf8';
    return req;
}

and data.toString( 'utf8' ) stopped giving me jumbled poo-poo

from express-http-proxy.

Hi Tophe,
As the first problem, I tried it, you should try res.text in test case. It works, I comments on your commit.

For api.github.com, it's very wired, I thought there might be a https relative problem, but I tried https://httpbin.org, everything works fine. I doubt it's somehow relative to how the code to decode the buffer. I'll keep it in the issues list to when I can finally take time to figure it out.

PS: in the final response, resp.body contains the correct json object =.=

from express-http-proxy.

Not sure if this is related: I faced a similar issue where I couldn't access any data from the response in the intercept hook (also when proxying to Github), yet I saw the response in the browser. It turned out to be a caching-related issue.
I added this to solve the problem.

decorateRequest: function(req) {
  delete req.headers['if-modified-since'];
  delete req.headers['if-none-match'];
  return req;
}

from express-http-proxy.