You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like harmon depends on the assumption that writeHead() gets called before write()
For whatever reason, there are situations where res.writeHead() doesn't get called until after one (or all!) res.write() calls.
So if the content is gzipped, then harmon doesn't set res.isGziped until after some of the data has already been written to the output, and either the gzip'd content gets sent to the output, or gzip fails because it gets only part of the data.
A possible solution would be to check content encoding on the first write() call, and store that.
The text was updated successfully, but these errors were encountered:
running into a similar issue, in which isHtml isn't getting set. It seems this change over at node-http-proxy has invalidated the assumption that writeHead always gets called first.
It seems like harmon depends on the assumption that
writeHead()
gets called beforewrite()
For whatever reason, there are situations where
res.writeHead()
doesn't get called until after one (or all!)res.write()
calls.So if the content is gzipped, then harmon doesn't set
res.isGziped
until after some of the data has already been written to the output, and either the gzip'd content gets sent to the output, or gzip fails because it gets only part of the data.A possible solution would be to check content encoding on the first
write()
call, and store that.The text was updated successfully, but these errors were encountered: