diff --git a/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx b/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx
index f18647165d..cc28f5dcff 100644
--- a/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx
+++ b/src/content/docs/en/pages/main-menu/reference/services/support/http-error-status-codes.mdx
@@ -144,6 +144,26 @@ This status code is a generic error message that often indicates issues with ser
 
 A 500 Internal Server Error usually requires action on the server's end to be fixed. In this case, you can refresh the page, clear browser cache and cookies, wait for a while, and check for updates from the website’s support or status page as options while the server is able to process your requests adequately.
 
+If your application is configured to redirect HTTP requests to HTTPS via **Rules Engine**, but the origin is also redirecting HTTPS back to HTTP, this creates a redirect loop that results in a 500 error. To resolve this, apply one or both of the following fixes:
+
+**To enforce HTTP between the edge and your origin:**
+
+1. Access [Azion Console](https://console.azion.com) > **Applications**.
+2. Select your application.
+3. Navigate to the **Origins** tab.
+4. Select the origin you want to configure.
+5. Under **Protocol Policy**, select **Enforce HTTP**.
+6. Click **Save**.
+
+**To remove the Redirect HTTP to HTTPS behavior from Rules Engine:**
+
+1. Access [Azion Console](https://console.azion.com) > **Applications**.
+2. Select your application.
+3. Navigate to the **Rules Engine** tab.
+4. Locate the rule that contains the **Redirect HTTP to HTTPS** behavior and click it to edit.
+5. In the **Behaviors** section, remove the **Redirect HTTP to HTTPS** behavior.
+6. Click **Save**.
+
 If the issue persists, contact the site owner to confirm that the system is stable or lacking exception handling.
 
 ### 502 Bad Gateway
@@ -183,4 +203,4 @@ Some ways to troubleshoot this error:
 - Clear your browser cookies and cached data.
 - Use a different browser or device. Browser-specific issues or device configurations can lead to unexpected errors.
 - Wait and retry. Occasionally, the server might be temporarily unable to fulfill requests due to maintenance or other issues.
-- If the issue persists, contact the site owner.
+- If the issue persists, contact the site owner.
\ No newline at end of file