Closed GuyPaddock closed 9 years ago
Okay, it looks like the content-encoding isn't the problem. It's that Harmon causes the binary response to be mangled somehow.
Just solved this in my own fork: https://github.com/GuyPaddock/harmon-binary
The fork distinguishes between HTML and non-HTML responses, and invokes Trumpet accordingly.
Hi @GuyPaddock
Harmon is open open source always happy to add significant contributers to the repo.
Please consider adding your modification as a pull request
Thanks
I have prepared a PR. Good advice -- I had not run the tests and discovered a subtle, fatal flaw in the way the new code was working.
It doesn't seem like Harmon works correctly when the proxy is serving up image content and the server is sending back the data using "chunked" content-encoding.
I would guess that the logic that determines whether or not to act on HTML only should base the decision on the mime type rather than the file extension.