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
Right now logger gets called after response body has been compressed, which means it is logged in a non-human-readable format
Wouldn't it be better to log request before encoding the response body?
The text was updated successfully, but these errors were encountered:
@TimaFrolov thanks for the suggestion. It would be nice to do it, there are some difficulties. The easiest way to do this is to keep the original uncompressed text as well, but I don't prefer this approach since it may cause much more memory usage. Another way we may think is to log a response object right before compressing text. But it can't be done since the server will add more HTTP header values to the response object afterward...
I don't have a solution for it at this point, but I'll leave it as 'enhancement'.
maybe this can be moved into a helper method on the Response. Something like getUncompressedBody() or so.
Btw. is there a way to disable the compression in the server at runtime?
Right now logger gets called after response body has been compressed, which means it is logged in a non-human-readable format
Wouldn't it be better to log request before encoding the response body?
The text was updated successfully, but these errors were encountered: