From 9e2b6325f3d5fecbe66ddae59a145a03e6a91cb7 Mon Sep 17 00:00:00 2001
From: "autofix-ci[bot]" <114827586+autofix-ci[bot]@users.noreply.github.com>
Date: Sat, 23 Aug 2025 19:42:56 +0000
Subject: [PATCH] [autofix.ci] apply automated fixes

---
 docker/ssrf_proxy/README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docker/ssrf_proxy/README.md b/docker/ssrf_proxy/README.md
index ad7eb3c8c1..5a91bd047a 100644
--- a/docker/ssrf_proxy/README.md
+++ b/docker/ssrf_proxy/README.md
@@ -17,8 +17,8 @@ The default configuration (`squid.conf.template`) is **strict by default** to pr
 To allow additional domains or relax restrictions for your local environment:
 
 1. Create a `conf.d` directory in your deployment
-2. Copy example configurations from `conf.d.example/` and modify as needed
-3. Mount the config files to `/etc/squid/conf.d/` in the container
+1. Copy example configurations from `conf.d.example/` and modify as needed
+1. Mount the config files to `/etc/squid/conf.d/` in the container
 
 ### Example: Docker Compose
 
@@ -95,9 +95,9 @@ The following networks are blocked by default to prevent SSRF:
 If your application needs to access a service that's being blocked:
 
 1. Check the Squid logs to identify what's being blocked
-2. Create a custom configuration in `/etc/squid/conf.d/`
-3. Only allow the minimum necessary access
-4. Test thoroughly to ensure security is maintained
+1. Create a custom configuration in `/etc/squid/conf.d/`
+1. Only allow the minimum necessary access
+1. Test thoroughly to ensure security is maintained
 
 ## File Structure
 
@@ -111,4 +111,4 @@ docker/ssrf_proxy/
 │   ├── 30-allow-external-domains.conf.example
 │   └── 40-allow-additional-ports.conf.example
 └── README.md                 # This file
-```
\ No newline at end of file
+```