You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "juzhiyuan (via GitHub)" <gi...@apache.org> on 2023/03/01 02:35:59 UTC

[GitHub] [apisix] juzhiyuan commented on a diff in pull request #8921: docs: update file-logger garbled faq

juzhiyuan commented on code in PR #8921:
URL: https://github.com/apache/apisix/pull/8921#discussion_r1121061095


##########
docs/en/latest/FAQ.md:
##########
@@ -704,6 +704,10 @@ Another solution is to switch to an experimental gRPC-based configuration synchr
     prefix: "/apisix"
 ```
 
+## Why is the file-logger logging garbled?
+
+If you are using the `file-logger` plugin and you are getting garbled log files, it may be because your upstream response is returning a compressed response body. You can fix this by bringing the request header with no compressed response parameters.

Review Comment:
   ```suggestion
   If you are using the `file-logger` plugin but getting garbled logs, one possible reason is your upstream response has returned a compressed response body. You can fix this by setting the request header with no compressed response parameters.
   ```



##########
docs/zh/latest/FAQ.md:
##########
@@ -707,6 +707,10 @@ make GOOS=linux GOARCH=amd64
     prefix: "/apisix"
 ```
 
+## 为什么 file-logger 记录日志会出现乱码?
+
+如果你使用的是 `file-logger` 插件,但是在日志文件中出现了乱码,那么可能是因为你的上游的响应返回是压缩格式的响应主体。你可以将请求头带上不接收压缩响应参数以解决这个问题。

Review Comment:
   How to do "你可以将请求头带上不接收压缩响应参数以解决这个问题。"?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org