From a9e4efd448c34d3ee14e636a6ff510ddfbc878fe Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Thu, 26 Jun 2025 23:18:46 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/FAQ.md b/FAQ.md
index d0c6d5c..174b29c 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -1012,6 +1012,12 @@ The custom client is not built on your server—it’s compiled on our build ser
 - Case 3: 
 The build job remains in a `waiting` status. I verified that all background build tasks have completed successfully, but the web console does not reflect this. The issue appears to be related to the proxy configuration once again. While the build job is triggered via a `POST` request, the status is polled using a `GET` request that includes an `Authorization` header. However, the proxy is stripping the `Authorization` header from `GET` requests, preventing the status from being retrieved correctly.
 
+> User: Can we arrange an appointment for tomorrow so you can log on to the server and check it?
+>
+> RustDesk: We can do nothing even we log on to your server. It is your proxy strip the 'GET' request header. I have no way to modify your proxy. I think you do not have the permission either.
+>
+> User: I figured it out. I added the proxy information to the YAML file for each image, so that it doesn't take it from the .env file. This works perfectly for us.
+
 # Showing multiple remote minotors as individual windows
 https://x.com/rustdesk/status/1714199082640581039